diff --git a/marked/Rel-16/23_series/23278/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23278/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53b71e586fc21539bf11c59b6b0ff1f0f43f2300 --- /dev/null +++ b/marked/Rel-16/23_series/23278/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2ba21246b23e336cffd5d76bb33814ef2cc4c50f225b64f4852dff2785a8c2e +size 80022 diff --git a/marked/Rel-16/23_series/23278/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Rel-16/23_series/23278/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93fdee0349bdd4b4b91d84a3a542845b192f549e --- /dev/null +++ b/marked/Rel-16/23_series/23278/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6dcef21413b28f7ac0d33f203954b8f65dd4f0c96b827c3d7bb5ff9cc89b8c8 +size 73087 diff --git a/marked/Rel-16/23_series/23278/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23278/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4603bf49b3108bba385d5b12684114a047f133e7 --- /dev/null +++ b/marked/Rel-16/23_series/23278/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb2370b3a8674f8d3092d9a98549261f5469452b90b548eb75b2c4e16b8e98ff +size 94891 diff --git a/marked/Rel-16/23_series/23278/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/23_series/23278/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dad57ab2b0849413428f6047bba26cad6576a60c --- /dev/null +++ b/marked/Rel-16/23_series/23278/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0923f5c71e99d5a16bff8cd8edd47895ced8e5e1ff81ac88f0c86df8064d9e3f +size 157862 diff --git a/marked/Rel-16/23_series/23278/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/23_series/23278/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f8abfbf6bdd6ad34121918dff3b83bde9c5ebce --- /dev/null +++ b/marked/Rel-16/23_series/23278/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0296e8c9188fcb1e397df57cb78e352a0530a7bd83b06574efd6f7552a1270c8 +size 225971 diff --git a/marked/Rel-16/23_series/23278/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/23_series/23278/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c28c9cdc07765ca7a041c80126a221044f54304 --- /dev/null +++ b/marked/Rel-16/23_series/23278/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a69b019c2793a19098dbd0f2ca9cc51250c07b3dc11f436ede7c4e0d7931a347 +size 100374 diff --git a/marked/Rel-16/23_series/23278/10b0dda884baae493ad958422d11b552_img.jpg b/marked/Rel-16/23_series/23278/10b0dda884baae493ad958422d11b552_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff4047a468fd3c76b2d488491bb9b6e7ede2c0cd --- /dev/null +++ b/marked/Rel-16/23_series/23278/10b0dda884baae493ad958422d11b552_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8338b419e999fbcc880ce5fd67f0fe5d2e78e448a8943328e2793b0bb2bc4f30 +size 134679 diff --git a/marked/Rel-16/23_series/23278/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/23_series/23278/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77be403e355e43e4bf2ea8293e3ed8d5475a0e47 --- /dev/null +++ b/marked/Rel-16/23_series/23278/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12ae91587394c2816987bf5139de965985c8c55118559b99f9b223daae89c4a0 +size 97601 diff --git a/marked/Rel-16/23_series/23278/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Rel-16/23_series/23278/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc3d12f2833c2ee36daa2fd8acb21f890ae7f8b9 --- /dev/null +++ b/marked/Rel-16/23_series/23278/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e63d372a9a74f357f1dfb833e80ec88b910d335ee51734bf003d98f66e000520 +size 40836 diff --git a/marked/Rel-16/23_series/23278/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-16/23_series/23278/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46fc9a9ea0156773baa9b99904ffa67b30ae76b4 --- /dev/null +++ b/marked/Rel-16/23_series/23278/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4f94d7da36983a79b19d82766a575b6125a0aea807c9fe769d4ad3cca811d38 +size 71208 diff --git a/marked/Rel-16/23_series/23278/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-16/23_series/23278/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15be28322d65d37fae86b5548416403fcb37c157 --- /dev/null +++ b/marked/Rel-16/23_series/23278/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad37a33d77a72cca906547e4f6a17f0dbd4d31828ce6aae0ce5c43547669c676 +size 136873 diff --git a/marked/Rel-16/23_series/23278/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/23_series/23278/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae6f3117a2858ca61b4b4f7bdc69bf187a43f10a --- /dev/null +++ b/marked/Rel-16/23_series/23278/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4f9a08718c1a0763bf29008653af64d78600654db71039208924b2322e929e6 +size 34448 diff --git a/marked/Rel-16/23_series/23278/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg b/marked/Rel-16/23_series/23278/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4444e9c3cca9fa8af39020801bcf57d11d843f54 --- /dev/null +++ b/marked/Rel-16/23_series/23278/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c89936f413857a7127193e595a677b16fe1f2b78ece60d5e70cca1fece8042d +size 52836 diff --git a/marked/Rel-16/23_series/23278/24a89bcaba787f2bc1721356480a4a01_img.jpg b/marked/Rel-16/23_series/23278/24a89bcaba787f2bc1721356480a4a01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fff82d6c167adb1200a78c528700ed7f8493494 --- /dev/null +++ b/marked/Rel-16/23_series/23278/24a89bcaba787f2bc1721356480a4a01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fff462949739900c392c9d35aa83d9bcac23386ed346c151dc7c1b7bc659a219 +size 58264 diff --git a/marked/Rel-16/23_series/23278/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-16/23_series/23278/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..840ecc8e72ccfdbb5c0fcdf6c7af6a14e047decb --- /dev/null +++ b/marked/Rel-16/23_series/23278/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:879de03e952bfc3f06b6df40035809a38b9bdc9c1c770c518b4a99e9dc5a7dde +size 125426 diff --git a/marked/Rel-16/23_series/23278/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23278/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5d54141ba33c0963350eebf8ccb9aaaa6373031 --- /dev/null +++ b/marked/Rel-16/23_series/23278/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e66c41c2f037deb36083ba4472f6e2b9a1881238304d3472a09ccb5bb462f38d +size 74571 diff --git a/marked/Rel-16/23_series/23278/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23278/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4a5cea1e59bc2a34d47f7ae257309dfb2dd0f6a --- /dev/null +++ b/marked/Rel-16/23_series/23278/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8513f39c1b45a916953cbeb2176ff861a67505128112de4daf1d987d215a35e7 +size 103924 diff --git a/marked/Rel-16/23_series/23278/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23278/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47a565367496502f52b0098253e723619b3a6f67 --- /dev/null +++ b/marked/Rel-16/23_series/23278/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c80cf6724b02b9556197ddcd985850b3221d0630ef418d69a1e2105d3c76d93 +size 79693 diff --git a/marked/Rel-16/23_series/23278/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-16/23_series/23278/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ae6e786ceff34f4e8434fbda9197c5a0e48f062 --- /dev/null +++ b/marked/Rel-16/23_series/23278/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6ada59524e96faa677579809a3dc20f94f6ecf9dc521b078b4411aea479bb77 +size 86772 diff --git a/marked/Rel-16/23_series/23278/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23278/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ccfb51d1f5131f664bfeb95b9543def2bb7be29 --- /dev/null +++ b/marked/Rel-16/23_series/23278/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8f308f4a2f1b07d1b1196f939af55fa75935178376b2b98c8f88c76d861c773 +size 152095 diff --git a/marked/Rel-16/23_series/23278/2fc2e531b3b3c695cca497516ec79f20_img.jpg b/marked/Rel-16/23_series/23278/2fc2e531b3b3c695cca497516ec79f20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0ca4b4ed2a65237075e67ec9a24d7b1b49dc0aa --- /dev/null +++ b/marked/Rel-16/23_series/23278/2fc2e531b3b3c695cca497516ec79f20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1f86efc8a70c6bb5e7046754d84db6bfdeafb810973fb424525a92fbda2f9c8 +size 38329 diff --git a/marked/Rel-16/23_series/23278/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/23_series/23278/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..659496e1e0da125f333a562b5bb5e08f7efa9982 --- /dev/null +++ b/marked/Rel-16/23_series/23278/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bddfd94036295af8d5d28f35d75ff688bd12d41acb47e562641a7eee64d73846 +size 93619 diff --git a/marked/Rel-16/23_series/23278/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23278/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0632cab7f507abd1a98a0847a46b0764347adbd --- /dev/null +++ b/marked/Rel-16/23_series/23278/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11595f703e8c2253d7e3a224e35b4195292ec0e5b492b249d7a8f1c33ec2a2d0 +size 123950 diff --git a/marked/Rel-16/23_series/23278/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-16/23_series/23278/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c489d33a84a8573491b02a2c28669e41cbd1a01 --- /dev/null +++ b/marked/Rel-16/23_series/23278/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1979509c19939212eab9777063855604c542a61371796ff890f20b93c3b5872 +size 102112 diff --git a/marked/Rel-16/23_series/23278/396197257cf9437b526bb6585b6a9c8a_img.jpg b/marked/Rel-16/23_series/23278/396197257cf9437b526bb6585b6a9c8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..478cd35ac6642dedd3644dc1e74fcb1517bbffbf --- /dev/null +++ b/marked/Rel-16/23_series/23278/396197257cf9437b526bb6585b6a9c8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:039b80ddaa3b8a4fc8304e106c1478173afdbb2d60a107b304059a6f99df6866 +size 72987 diff --git a/marked/Rel-16/23_series/23278/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/Rel-16/23_series/23278/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca8ff4023cd6921b758aec56db3362121db4d370 --- /dev/null +++ b/marked/Rel-16/23_series/23278/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ad19ea4d76027db6a73ae2a43dc09510a472c7340b7e11109cf4a9c86e8b7c4 +size 90540 diff --git a/marked/Rel-16/23_series/23278/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23278/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..932f118ae7b3ef300378c896f74e0651a63635c2 --- /dev/null +++ b/marked/Rel-16/23_series/23278/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d0860d23b513be79996fa9f473a7185c05cf4fdfe009ae289fa01842ac6f911 +size 128143 diff --git a/marked/Rel-16/23_series/23278/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-16/23_series/23278/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e4ca15ec2d6231f55f2e3524afd0a86fcdf7877 --- /dev/null +++ b/marked/Rel-16/23_series/23278/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f992c4e7a99ae975cc2234753397afdc7c6848890cdd69ac41f4d5feac2a913 +size 5995 diff --git a/marked/Rel-16/23_series/23278/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-16/23_series/23278/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e5bf4efaa70405d10a52bcf316068979b973a48 --- /dev/null +++ b/marked/Rel-16/23_series/23278/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18bb1303ed8700046f3b832af24e109bfae3dd9c35d95bdf6cca68e6477280bd +size 52498 diff --git a/marked/Rel-16/23_series/23278/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-16/23_series/23278/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c5ce02199a043fd89591e054e8d9307ec88b33a --- /dev/null +++ b/marked/Rel-16/23_series/23278/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61310c9d3228ae9cc61f55bf777a44d33339b2683ed73f360f61ddc95fdca710 +size 132033 diff --git a/marked/Rel-16/23_series/23278/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/marked/Rel-16/23_series/23278/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcfa6c95f0cd79cbb0c165475ed1f8950a3347e --- /dev/null +++ b/marked/Rel-16/23_series/23278/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c01e8fae06c6f080d5e9e797b91d0ea82106f1f2158510252b4ec2748e24d8e8 +size 57885 diff --git a/marked/Rel-16/23_series/23278/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23278/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..845c3ea30bdbfd1e4346fdbd180b60089c2bf9d1 --- /dev/null +++ b/marked/Rel-16/23_series/23278/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d9606ecc7d3003b5ff78625c845c9cb56b95f2c0f0daa85f4ec99deec21f6db +size 100255 diff --git a/marked/Rel-16/23_series/23278/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23278/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e72a028db80dba40f29d34578f89bcf52436b87 --- /dev/null +++ b/marked/Rel-16/23_series/23278/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98a16a87c8d8a6860a2661eabff7b3df6570d80b9d786cda92a22dae15a6a2f9 +size 140467 diff --git a/marked/Rel-16/23_series/23278/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23278/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98429021e99088b3f4c8ee604ddbc507c1352dac --- /dev/null +++ b/marked/Rel-16/23_series/23278/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:941a21a37b6772ec2fa9020d4be53a642607c61aee22ef9add034546c7ef62f3 +size 35116 diff --git a/marked/Rel-16/23_series/23278/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/23_series/23278/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b146d734bcdc6e35759ced6eee1227ffdfce5fa --- /dev/null +++ b/marked/Rel-16/23_series/23278/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7340a72145826491b71b0b82fcad3d77a9696eada773a5f8687dc468f4228328 +size 64958 diff --git a/marked/Rel-16/23_series/23278/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23278/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a88b48cfda8cff39fa5dedb8c0b92e9c96a46a3 --- /dev/null +++ b/marked/Rel-16/23_series/23278/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c514ed3160750d57813acf72fc33d47a13ecf9b833d25c7465d264083c0eb57 +size 98535 diff --git a/marked/Rel-16/23_series/23278/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/marked/Rel-16/23_series/23278/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28b6968defd7b3f0fab8e3ffe279e4e453e0c233 --- /dev/null +++ b/marked/Rel-16/23_series/23278/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:029ef8fa9b7c466b9614988c23844cf30048eba79eb5702ea604a82d3caa7355 +size 166684 diff --git a/marked/Rel-16/23_series/23278/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23278/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1396ca8da064a9b2990389e76d338016dc6b4da5 --- /dev/null +++ b/marked/Rel-16/23_series/23278/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d72653a82815e06381d60e97f36797b6c6daf55d154aa9a7773d7d5f50a36ae3 +size 110565 diff --git a/marked/Rel-16/23_series/23278/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23278/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c190ab95b59be48853a4ec1df3bac2e0b96a1f88 --- /dev/null +++ b/marked/Rel-16/23_series/23278/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9374dcdfc317ee78067ad830bb2ad0ed1cea7f1649f326b22699775aed434e7 +size 123902 diff --git a/marked/Rel-16/23_series/23278/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/Rel-16/23_series/23278/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a067b3f090d65ec156a1f3a7c93c1e267adae4b --- /dev/null +++ b/marked/Rel-16/23_series/23278/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36508a2763d4ed9881da6eb0e3e3844930871f64558e9f84658529a3b86a8b05 +size 115868 diff --git a/marked/Rel-16/23_series/23278/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/marked/Rel-16/23_series/23278/708e4c9a044ef61f586126676eb2eeb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddfe9a634381ec5c58bd14aab4f597dbd9fd0d70 --- /dev/null +++ b/marked/Rel-16/23_series/23278/708e4c9a044ef61f586126676eb2eeb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:478bbb1580374ce124254d0a7c2ecea16ddb25258226c4d0d5eecbf75b8ee126 +size 58085 diff --git a/marked/Rel-16/23_series/23278/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-16/23_series/23278/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7d1efab5e758ef88c9f4a48415e09449b45eb5e --- /dev/null +++ b/marked/Rel-16/23_series/23278/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49d4b004aa34c7153b44e666b9b77924d93f6f9777fa2a40440eae0c17481d28 +size 76762 diff --git a/marked/Rel-16/23_series/23278/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/23_series/23278/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..435b6b519f190ab6581a3718e7147d77741b2abe --- /dev/null +++ b/marked/Rel-16/23_series/23278/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ffad16b7eef276ad8a2d80343d580f6d9e2ea1af26bdc88c1760bc118dc92aa +size 176149 diff --git a/marked/Rel-16/23_series/23278/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23278/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba798db4c6adcd8f4278a056871e2af0042adb0d --- /dev/null +++ b/marked/Rel-16/23_series/23278/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d16aea97df8550f0c4975c2f712b699895b59227207674de56dc95f25ac4dd37 +size 149212 diff --git a/marked/Rel-16/23_series/23278/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23278/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86d3d3334043a9f3a3bbec0fa8ff90842adc954b --- /dev/null +++ b/marked/Rel-16/23_series/23278/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1d6beaa103dee4dae3686280b833fb35bf81902b45f9455136a694ee6429674 +size 115689 diff --git a/marked/Rel-16/23_series/23278/869c547c11ac7e123c51aba22289f2cd_img.jpg b/marked/Rel-16/23_series/23278/869c547c11ac7e123c51aba22289f2cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5aec8fb672192f6f68838979a9ab6e4fd24d2c4b --- /dev/null +++ b/marked/Rel-16/23_series/23278/869c547c11ac7e123c51aba22289f2cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:627cf70e2436b8ddf8005e951f4142039441b0120e58aed180c6f3f99a41c391 +size 56229 diff --git a/marked/Rel-16/23_series/23278/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/23_series/23278/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..885436025f0531e33d629d4ca4596af090b27e64 --- /dev/null +++ b/marked/Rel-16/23_series/23278/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c1bbf2aa35176c79c09dcd6d6a16a0c9a0cd9f69adaa641e36c2ae2811435f0 +size 54470 diff --git a/marked/Rel-16/23_series/23278/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23278/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4170eeca2cfbe541e07fafb5c8fd8fed48285712 --- /dev/null +++ b/marked/Rel-16/23_series/23278/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:685ebbca166d6306abc07a54fa333e4670cdbf14810806eb835e0be8ea494a2b +size 101520 diff --git a/marked/Rel-16/23_series/23278/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23278/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..975cda949c6c0c9fb9cb2a0b14be473b39506093 --- /dev/null +++ b/marked/Rel-16/23_series/23278/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6bf973874e77dd475772cc7acdcff8b5f01a81f767beed9c290dd5d93dcd8aa +size 54883 diff --git a/marked/Rel-16/23_series/23278/91c33f8e1713989e8192322ec2d1212b_img.jpg b/marked/Rel-16/23_series/23278/91c33f8e1713989e8192322ec2d1212b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac73eeb3c59f62ef256740acc8af16b31c2361fd --- /dev/null +++ b/marked/Rel-16/23_series/23278/91c33f8e1713989e8192322ec2d1212b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c32252def78366e197502804210af2985569b4247efa6f3608069c0fe8dab74 +size 60133 diff --git a/marked/Rel-16/23_series/23278/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23278/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638729709eab9ae7771a6a0538245fa96dace675 --- /dev/null +++ b/marked/Rel-16/23_series/23278/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77fff3924439e4fd68e43aa131212d43887a9fe8ac43101419972653b68d2911 +size 139497 diff --git a/marked/Rel-16/23_series/23278/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-16/23_series/23278/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d92faf798d8a190a3306aa78539667cce4f4d91b --- /dev/null +++ b/marked/Rel-16/23_series/23278/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82f5af387edd7ccb9f03859f7b41efa68d0db82ed9bdd12686793a3fb33a4a17 +size 102886 diff --git a/marked/Rel-16/23_series/23278/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23278/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3281083afc1188f5e3427bf88e247f346f7af8e9 --- /dev/null +++ b/marked/Rel-16/23_series/23278/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cffe7adb7b493b9600612e72f151f26fe71181e39ae0d4052995dbe503407a58 +size 134350 diff --git a/marked/Rel-16/23_series/23278/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-16/23_series/23278/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94e0af704ea226cd34dee62cb665dd437ac3ee91 --- /dev/null +++ b/marked/Rel-16/23_series/23278/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b54b49b2cdbdc1c8d2dd0549ca37fc5180df51b1500d8ec4116db4c9ba9c975c +size 91706 diff --git a/marked/Rel-16/23_series/23278/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-16/23_series/23278/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ee6b4e12cde4c7e970c6a71040f5a50fd3b6590 --- /dev/null +++ b/marked/Rel-16/23_series/23278/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66726f8244968d9ee398151152021ee45c3acfd7b69e5ef632b81a503fc76ce0 +size 184484 diff --git a/marked/Rel-16/23_series/23278/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23278/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb61b297c0cc1d1b272a49f06901e72ff0f4c68b --- /dev/null +++ b/marked/Rel-16/23_series/23278/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:902cdd6e75c44a6b00f3c174ead94c72325cce1334306a9fc982e4ee74502a0d +size 103810 diff --git a/marked/Rel-16/23_series/23278/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/23_series/23278/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a450867b0b0cc03dba5150fb5fbbbd6bea84e1d0 --- /dev/null +++ b/marked/Rel-16/23_series/23278/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffef429210c6d6c96413802d8cd535edeb8e620ef45ec82b20d50e4a424d3071 +size 54303 diff --git a/marked/Rel-16/23_series/23278/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23278/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad91f279c8fa73e83946003fe3a1706ae7c03aa0 --- /dev/null +++ b/marked/Rel-16/23_series/23278/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b44a0024ace1a70e281e8c4418ee382a6f50b4d4a5c57c29c7353c27b3f3e88c +size 125753 diff --git a/marked/Rel-16/23_series/23278/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-16/23_series/23278/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73814cd19d92f524bfcedb854183bbebf6bfc456 --- /dev/null +++ b/marked/Rel-16/23_series/23278/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7678bc39781bd8e33ea65e1f5f6ee271332afc1f77d0c5883e0b77f2efa50b01 +size 180623 diff --git a/marked/Rel-16/23_series/23278/a93de4c3f80bd4a972ab65510b09b68d_img.jpg b/marked/Rel-16/23_series/23278/a93de4c3f80bd4a972ab65510b09b68d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b2ac391484341c2c6bd798b091a68c0b0a48f8c --- /dev/null +++ b/marked/Rel-16/23_series/23278/a93de4c3f80bd4a972ab65510b09b68d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fd540ca1eb714abcc8dac77a0e95d1c0b9fffc406ac3024b5d5485c69be3118 +size 21004 diff --git a/marked/Rel-16/23_series/23278/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/23_series/23278/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed9af610d03cd966d67f26f9f4b38dbf0662222d --- /dev/null +++ b/marked/Rel-16/23_series/23278/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09cae7bbb1aa73948f21cd7d3f251e8628f7729f5842921bd65fa9864f7bb4fa +size 108952 diff --git a/marked/Rel-16/23_series/23278/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Rel-16/23_series/23278/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a37d6aec51276f819c97b2d9911d2d38c0d745b --- /dev/null +++ b/marked/Rel-16/23_series/23278/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d22acc01b1bcaa4a3cda07c96bedbb6b68a11d5b1200d7151c8b6d04206def65 +size 67204 diff --git a/marked/Rel-16/23_series/23278/b13465efdac63129aef9b6f1787d0d00_img.jpg b/marked/Rel-16/23_series/23278/b13465efdac63129aef9b6f1787d0d00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9e6c314cf8b782dd99f78065131e788bb21a83b --- /dev/null +++ b/marked/Rel-16/23_series/23278/b13465efdac63129aef9b6f1787d0d00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d16d878fa79a910311082fbbbce79f95ce02abd2a5ad9c136d81c0c8069b8b6 +size 110351 diff --git a/marked/Rel-16/23_series/23278/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23278/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d179a7f34149e257e0a6c41600f7e9796e10572 --- /dev/null +++ b/marked/Rel-16/23_series/23278/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ba5b279c501ef0f90688513c8b676790a1a00ea04f8d407ef1d6b9c0b875355 +size 100500 diff --git a/marked/Rel-16/23_series/23278/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/Rel-16/23_series/23278/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d46c9f7024fadeb116962ebffb2b1f79238ed1c6 --- /dev/null +++ b/marked/Rel-16/23_series/23278/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd22575eee2a4c6b4796f37e7dd54c4aa57abe17ca6d03584778c836db96d46f +size 46072 diff --git a/marked/Rel-16/23_series/23278/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Rel-16/23_series/23278/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72010ecea83ca96337f3986471b973a1450f02a2 --- /dev/null +++ b/marked/Rel-16/23_series/23278/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07b7188cc845be351287313c0d3a898277e617c80d4960d741cd36973d164c84 +size 130210 diff --git a/marked/Rel-16/23_series/23278/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-16/23_series/23278/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1eed11d369b4f71ee615151109a016e51b13391 --- /dev/null +++ b/marked/Rel-16/23_series/23278/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbc73a087c1c3b4538f6deacc54b65b4b823e7cc29c673e074c67edec9c143f7 +size 164765 diff --git a/marked/Rel-16/23_series/23278/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/Rel-16/23_series/23278/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec244a9bfed2d0e806e37a324d8b40fcb1ee4e1e --- /dev/null +++ b/marked/Rel-16/23_series/23278/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cf0f9789411c5458a722b3dd917cb7eac2d18c7d685208e2c08caee19a1940a +size 78154 diff --git a/marked/Rel-16/23_series/23278/beefc2239bc009e7b97963ac4f166db1_img.jpg b/marked/Rel-16/23_series/23278/beefc2239bc009e7b97963ac4f166db1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..356ca1d13fb8c16dd4bd12479b74b3499dd904cc --- /dev/null +++ b/marked/Rel-16/23_series/23278/beefc2239bc009e7b97963ac4f166db1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:047054ab11d23b938bff046aa6ea1a9954dac16f8d5ceaaeb3c11abdd88ec5e0 +size 29109 diff --git a/marked/Rel-16/23_series/23278/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/23_series/23278/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd291a176292bb8cebb8f75bebbb2500844954c9 --- /dev/null +++ b/marked/Rel-16/23_series/23278/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ec1198eff6cf1577f0a3707c44d24bb07f45b6fce539b59faadad340823c412 +size 156097 diff --git a/marked/Rel-16/23_series/23278/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-16/23_series/23278/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6f775dfb0e64dea6853e0e407565308755b674f --- /dev/null +++ b/marked/Rel-16/23_series/23278/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcab9bfc3bd54a102fcbc350efab60fb293a55a54911c4613d2b950c17ec31d5 +size 159803 diff --git a/marked/Rel-16/23_series/23278/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-16/23_series/23278/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c694cf58401948ae42e0e89443ca59b881e68fa9 --- /dev/null +++ b/marked/Rel-16/23_series/23278/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c64e985e79968d28a21e80302240e5a71b28c2a06c3bcb6861b3eadeacd487b +size 141738 diff --git a/marked/Rel-16/23_series/23278/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/marked/Rel-16/23_series/23278/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8831ce2a2b499012426679ace2938c2c677c998e --- /dev/null +++ b/marked/Rel-16/23_series/23278/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:683b93dad8c2f02cb0170c53cd79ec8b377598596810cc1224904973a998f1e1 +size 66620 diff --git a/marked/Rel-16/23_series/23278/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-16/23_series/23278/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa52102ed4e2e38ed97e331da28f84688c8ef63d --- /dev/null +++ b/marked/Rel-16/23_series/23278/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fbce64f874ee335d0ce68469f0b5f10a39e52b2b7974bd7891676bb546d6674 +size 106153 diff --git a/marked/Rel-16/23_series/23278/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-16/23_series/23278/d7948c38a18636aefecdd95388196460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39394de4cb3025a12af555b25fa613775dec7b86 --- /dev/null +++ b/marked/Rel-16/23_series/23278/d7948c38a18636aefecdd95388196460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8fa1e225b6fdd885f0e535ef56793ae9fcb9cee39652f8531348e2684a8afc6 +size 29612 diff --git a/marked/Rel-16/23_series/23278/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-16/23_series/23278/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46b1b312a46717cd95a4f0eb33d8b8038f87ed43 --- /dev/null +++ b/marked/Rel-16/23_series/23278/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:655090449d8243cc233b778c2765f2480a97ddce1c9e02bd74c194cb902cb138 +size 80045 diff --git a/marked/Rel-16/23_series/23278/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23278/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..717ea7851435e6050fa07ea3488245eea1cef11c --- /dev/null +++ b/marked/Rel-16/23_series/23278/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:993e7fff90e406e2f0e4994bc7076c39711d87f05a24fe4b545f696fdff3fb28 +size 150648 diff --git a/marked/Rel-16/23_series/23278/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-16/23_series/23278/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ed87b9ae6063867c32b97c5eeee036bfc0a8a78 --- /dev/null +++ b/marked/Rel-16/23_series/23278/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22ed17664c341dca949b62ada36e7b40d62870d49a7fff08c361dbafa7633b3b +size 48834 diff --git a/marked/Rel-16/23_series/23278/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-16/23_series/23278/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daa95ed43bb1f6c31e402040c3a6d2762aade874 --- /dev/null +++ b/marked/Rel-16/23_series/23278/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96e34241e62d608d8fd025d940a3361977310194be739f25067f83918be4daa7 +size 83222 diff --git a/marked/Rel-16/23_series/23278/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-16/23_series/23278/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04483cce87d4d122f38b9986b41ada768556f5eb --- /dev/null +++ b/marked/Rel-16/23_series/23278/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:982bcb8379ff8c437b3ebe028c408906ecc91af0b3962a876ecf1504b3523eb7 +size 243101 diff --git a/marked/Rel-16/23_series/23278/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23278/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90915da8e17b4c628cb2be8b3f35041640dbd3fa --- /dev/null +++ b/marked/Rel-16/23_series/23278/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3f886dbe74183e6ca5bdcd374dcfbfd28929489b7aff62cabbec4bca4bf48da +size 55868 diff --git a/marked/Rel-16/23_series/23278/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-16/23_series/23278/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1750946fc4c7f44e5e5e6cae2f0a721301f3704d --- /dev/null +++ b/marked/Rel-16/23_series/23278/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3ab0521fa7fc5a4c15cf0c6ec792009819cda2fcbdabbf5b792951bb97a13cd +size 187253 diff --git a/marked/Rel-16/23_series/23278/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23278/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63a124a872fbd1fc845112e11737678ed80bb2ba --- /dev/null +++ b/marked/Rel-16/23_series/23278/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87bf2fd3eb552b4209429cb0a5ac0301ed9466d408c5c0004a022b5a23dcb6f2 +size 137566 diff --git a/marked/Rel-16/23_series/23278/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23278/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43b56945baeaa719fddcdf84fe2381439786ac1b --- /dev/null +++ b/marked/Rel-16/23_series/23278/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a857dafb1ed48ab8174f761eef2d1355e35fa2ddb1720d8adf4438d6fab0cd1e +size 134251 diff --git a/marked/Rel-16/23_series/23278/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-16/23_series/23278/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfba354314c9b938e24fe4cb0994cf2a627b58dd --- /dev/null +++ b/marked/Rel-16/23_series/23278/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3cd951f05f030d23d09c958ba8fc337076e4a2fd92a57047d7dbf545d76a2dc +size 103479 diff --git a/marked/Rel-16/23_series/23278/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg b/marked/Rel-16/23_series/23278/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b54c9a162cbbd3ff803310bced4790ae3486cf70 --- /dev/null +++ b/marked/Rel-16/23_series/23278/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e008af4cbd9b21b485039a2f37aeae9aaa424e56aeeb0e1d10d7d2d7912196c +size 40770 diff --git a/marked/Rel-16/23_series/23278/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-16/23_series/23278/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c7a639034c4153ef6bd5b32fd248da063c002f --- /dev/null +++ b/marked/Rel-16/23_series/23278/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8d0d722e7805e19b6f788c886704930ab34fd7c3fee59f110b26dd1d4b0c4e2 +size 146515 diff --git a/marked/Rel-16/23_series/23278/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg b/marked/Rel-16/23_series/23278/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbc541d669e5a6173994c37765ebd69a8a71b156 --- /dev/null +++ b/marked/Rel-16/23_series/23278/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e42fcd47acaa647720d678e6a2ce6dc3dabbba6b6ef8f958d4955dd1814a10d +size 63229 diff --git a/marked/Rel-16/23_series/23278/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-16/23_series/23278/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91eda5b18976689cd7b1fc3102884ea952da508a --- /dev/null +++ b/marked/Rel-16/23_series/23278/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed9ba67225164975262ffc51eb8da9975bce93c0c7ceb0c34bc58b7ea0131865 +size 125639 diff --git a/marked/Rel-16/23_series/23278/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/23_series/23278/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7978fd82968c4df393d0317fa3484fd3acf261d --- /dev/null +++ b/marked/Rel-16/23_series/23278/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62d55057a3098cf519e6f9044eec498cd313dd478554436edff23a9785b13092 +size 123661 diff --git a/marked/Rel-16/23_series/23278/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-16/23_series/23278/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..441dcd5d17679c77e5488e85f843e148389273ca --- /dev/null +++ b/marked/Rel-16/23_series/23278/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a00bcb99dff0d8a4de05b01ae9319bf4c5c4244d4661d0e032f5545bd603046 +size 72839 diff --git a/marked/Rel-16/23_series/23278/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-16/23_series/23278/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42f2ee79ce8c9df3a7891eec19aa5ae04d0fabd1 --- /dev/null +++ b/marked/Rel-16/23_series/23278/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75c16d493cbec533c79ac6be7e524531853a370d79271afa9fde431f9ba17ef3 +size 118640 diff --git a/marked/Rel-16/23_series/23278/raw.md b/marked/Rel-16/23_series/23278/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4524adb17e4879c4d9b3bc97e054e83e22c737c6 --- /dev/null +++ b/marked/Rel-16/23_series/23278/raw.md @@ -0,0 +1,5167 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 CAMEL/IP Multimedia Core Network Interworking..... | 10 | +| 4.1 Architecture..... | 10 | +| 4.1.1 Functional Entities used for CAMEL at IP Multimedia Registration ..... | 10 | +| 4.1.2 Functional Entities used for CAMEL for MO and MT IP Multimedia session ..... | 11 | +| 4.2 Interfaces defined for an IM-SSF based Application Server ..... | 11 | +| 4.2.1 CSCF – IM-SSF interface ..... | 11 | +| 4.2.2 IM-SSF - gsmSCF interface ..... | 11 | +| 4.2.3 HSS – IM-SSF interface..... | 11 | +| 4.3 Detection Points (DPs)..... | 11 | +| 4.3.1 Arming/Disarming mechanism ..... | 12 | +| 4.3.2 Criteria ..... | 12 | +| 4.3.2.1 Criteria at Collected_Info ..... | 13 | +| 4.3.2.2 Criteria at DP Analysed_Information ..... | 13 | +| 4.3.2.2.1 General ..... | 13 | +| 4.3.2.2.2 Number comparison ..... | 14 | +| 4.3.2.3 Criteria at DP Route_Select_Failure..... | 14 | +| 4.3.2.4 Criteria at DP T_Busy and T_No_Answer ..... | 15 | +| 4.4 Description of CAMEL Subscriber Data ..... | 15 | +| 4.4.1 IP Multimedia CAMEL Subscription Information (IM-CSI) ..... | 15 | +| 4.4.1.1 Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI) ..... | 15 | +| 4.4.1.1.1 gsmSCF Address..... | 15 | +| 4.4.1.1.2 Service Key ..... | 15 | +| 4.4.1.1.3 Default Call Handling ..... | 15 | +| 4.4.1.1.4 TDP List..... | 15 | +| 4.4.1.1.5 CAMEL Capability Handling ..... | 15 | +| 4.4.1.1.6 CSI Status..... | 15 | +| 4.4.1.1.7 Notification Flag ..... | 15 | +| 4.4.1.1.8 DP Criteria..... | 16 | +| 4.4.1.2 Dialled Services IP Multimedia CAMEL Subscription Information (D-IM-CSI) ..... | 16 | +| 4.4.1.2.1 gsmSCF Address..... | 16 | +| 4.4.1.2.2 Service Key ..... | 16 | +| 4.4.1.2.3 Default Call Handling ..... | 16 | +| 4.4.1.2.4 CAMEL Capability Handling ..... | 16 | +| 4.4.1.2.5 CSI Status..... | 16 | +| 4.4.1.2.6 Notification Flag ..... | 16 | +| 4.4.1.2.7 DP Criteria..... | 16 | +| 4.4.1.3 Terminating IP Multimedia CAMEL Subscription Information (VT-IM-CSI) ..... | 16 | +| 4.4.1.3.1 gsmSCF Address..... | 16 | +| 4.4.1.3.2 Service Key ..... | 16 | +| 4.4.1.3.3 Default Call Handling ..... | 16 | +| 4.4.1.3.4 TDP List..... | 16 | +| 4.4.1.3.5 CAMEL Capability Handling ..... | 17 | +| 4.4.1.3.6 CSI Status..... | 17 | +| 4.4.1.3.7 Notification Flag ..... | 17 | +| 4.4.1.3.8 DP Criteria..... | 17 | +| 4.4.1.4 Other CAMEL Data..... | 17 | +| 4.4.1.4.1 gsmSCF address list for CSI ..... | 17 | +| 4.5 Description of CAMEL State Models..... | 17 | +| 4.5.1 General Handling..... | 17 | +| 4.5.2 Originating CAMEL Basic Call State Model (O-IM-BCSM) ..... | 18 | + +| | | | +|-----------|---------------------------------------------------------------------------------------|-----| +| 4.5.2.1 | Description of the O-IM-BCSM ..... | 18 | +| 4.5.2.2 | Description of Points In Call ..... | 19 | +| 4.5.2.2.1 | O_Null & Authorise_Origination_Attempt_Collect_Info ..... | 19 | +| 4.5.2.2.2 | Analyse_Information..... | 20 | +| 4.5.2.2.3 | Routing and Alerting..... | 20 | +| 4.5.2.2.4 | O_Active ..... | 20 | +| 4.5.2.2.5 | O_Exception..... | 21 | +| 4.5.3 | Mapping of SIP Method/Response to O-IM-BCSM Detection Points ..... | 21 | +| 4.5.4 | Terminating CAMEL Basic Call State Model (T-IM-BCSM)..... | 22 | +| 4.5.4.1 | Description of the T-IM-BCSM ..... | 22 | +| 4.5.4.2 | Description of Points In Call ..... | 23 | +| 4.5.4.2.1 | T_Null ..... | 23 | +| 4.5.4.2.2 | Terminating Call Handling..... | 23 | +| 4.5.4.2.3 | T_Active..... | 24 | +| 4.5.4.2.4 | T_Exception ..... | 24 | +| 4.5.5 | Mapping of SIP Method/Response to T-IM-BCSM Detection Points ..... | 25 | +| 4.6 | Procedures for IM-SSF Application Server ..... | 25 | +| 4.6.1 | Overall SDL Architecture..... | 26 | +| 4.6.1.1 | Handling of Registration and De-registration in the IM-SSF ..... | 27 | +| 4.6.1.1.1 | Procedure CAMEL_IMCN_Register..... | 27 | +| 4.6.1.2 | Handling of Notify Subscriber Data Change ..... | 30 | +| 4.6.1.3 | Handling of Mobile Originated Calls in the IM-SSF ..... | 33 | +| 4.6.1.3.1 | Actions of the IM-SSF on receipt of Int_Error ..... | 33 | +| 4.6.1.3.2 | Actions of the IM-SSF on receipt of Int_Continue ..... | 33 | +| 4.6.1.3.3 | Actions of the IM-SSF on receipt of Int_Continue_With_Argument..... | 33 | +| 4.6.1.3.4 | Actions of the IM-SSF on receipt of Int_Connect ..... | 33 | +| 4.6.1.3.5 | Actions of the IM-SSF on receipt of Int_Release_Call..... | 33 | +| 4.6.1.3.6 | Handling of procedure CAMEL_OCH_CTR, sheet 1 ..... | 33 | +| 4.6.1.3.7 | Handling of procedure CAMEL_OCH_CTR, sheet 5 ..... | 34 | +| 4.6.1.3.8 | Receipt of 100 Trying Provisional Response (Process MO_IM_SSF) ..... | 34 | +| 4.6.1.3.9 | Handling of internal timers in Process MO_IM_SSF ..... | 34 | +| 4.6.1.4 | Handling of Mobile Terminated IP Multimedia sessions in the IM-SSF ..... | 64 | +| 4.6.1.4.1 | Actions of the IM-SSF on receipt of Int_Error ..... | 64 | +| 4.6.1.4.2 | Actions of the IM-SSF on receipt of Int_Release_Call..... | 64 | +| 4.6.1.4.3 | Actions of the IM-SSF on receipt of Int_Continue_With_Argument..... | 64 | +| 4.6.1.4.4 | Actions of IM-SSF in procedure CAMEL_IMCN_MT_INVITE for Unregistered Subscriber ..... | 64 | +| 4.6.1.4.5 | Handling of procedure CAMEL_MT_CTR, sheet 1 ..... | 64 | +| 4.6.1.4.6 | Handling of procedure CAMEL_MT_CTR, sheet 5..... | 65 | +| 4.6.1.4.7 | Receipt of 100 Trying Provisional Response (Process MT_IM_SSF) ..... | 65 | +| 4.6.1.4.8 | Handling of internal timers in Process MT_IM_SSF..... | 65 | +| 4.6.1.5 | Handling of call in the imcnSSF ..... | 95 | +| 4.6.1.5.1 | Process imcnSSF ..... | 95 | +| 4.6.1.6 | Process imcn_SSME_SSF and procedures..... | 126 | +| 4.7 | Descriptions of information Flows..... | 129 | +| 4.7.1 | IM-SSF to gsmSCF information flows..... | 129 | +| 4.7.1.1 | Activity Test ack..... | 129 | +| 4.7.1.1.1 | Description ..... | 129 | +| 4.7.1.1.2 | Information Elements..... | 129 | +| 4.7.1.2 | Apply Charging Report..... | 129 | +| 4.7.1.2.1 | Description ..... | 129 | +| 4.7.1.2.2 | Information Elements..... | 129 | +| 4.7.1.3 | Call Gap ..... | 131 | +| 4.7.1.3.1 | Description ..... | 131 | +| 4.7.1.3.2 | Information Elements..... | 131 | +| 4.7.1.4 | Call Information Report..... | 133 | +| 4.7.1.4.1 | Description ..... | 133 | +| 4.7.1.4.2 | Information Elements..... | 133 | +| 4.7.1.5 | Event Report BCSM ..... | 133 | +| 4.7.1.5.1 | Description ..... | 133 | +| 4.7.1.5.2 | Information Elements..... | 133 | +| 4.7.1.6 | Initial DP..... | 134 | +| 4.7.1.6.1 | Description ..... | 134 | + +| | | | +|------------|---------------------------------------------------------------------|-----| +| 4.7.1.6.2 | Information Elements..... | 135 | +| 4.7.1.7 | Specialized Resource Report..... | 136 | +| 4.7.1.7.1 | Description..... | 136 | +| 4.7.1.7.2 | Information Elements..... | 136 | +| 4.7.2 | gsmSCF to IM-SSF information flows..... | 137 | +| 4.7.2.1 | Activity Test..... | 137 | +| 4.7.2.1.1 | Description..... | 137 | +| 4.7.2.1.2 | Information Elements..... | 137 | +| 4.7.2.2 | Apply Charging..... | 137 | +| 4.7.2.2.1 | Description..... | 137 | +| 4.7.2.2.2 | Information Elements..... | 137 | +| 4.7.2.3 | Call Information Request..... | 138 | +| 4.7.2.3.1 | Description..... | 138 | +| 4.7.2.3.2 | Information Elements..... | 138 | +| 4.7.2.4 | Cancel..... | 138 | +| 4.7.2.4.1 | Description..... | 138 | +| 4.7.2.4.2 | Information Elements..... | 138 | +| 4.7.2.5 | Connect..... | 139 | +| 4.7.2.5.1 | Description..... | 139 | +| 4.7.2.5.2 | Information Elements..... | 139 | +| 4.7.2.6 | Connect To Resource..... | 139 | +| 4.7.2.6.1 | Description..... | 139 | +| 4.7.2.6.2 | Information Elements..... | 139 | +| 4.7.2.7 | Continue..... | 139 | +| 4.7.2.7.1 | Description..... | 139 | +| 4.7.2.7.2 | Information Elements..... | 139 | +| 4.7.2.8 | Continue With Argument..... | 140 | +| 4.7.2.8.1 | Description..... | 140 | +| 4.7.2.8.2 | Information Elements..... | 140 | +| 4.7.2.9 | Disconnect Forward Connection..... | 140 | +| 4.7.2.9.1 | Description..... | 140 | +| 4.7.2.9.2 | Information Elements..... | 140 | +| 4.7.2.10 | Furnish Charging Information..... | 140 | +| 4.7.2.10.1 | Description..... | 140 | +| 4.7.2.10.2 | Information Elements..... | 140 | +| 4.7.2.11 | Release Call..... | 141 | +| 4.7.2.11.1 | Description..... | 141 | +| 4.7.2.11.2 | Information Elements..... | 141 | +| 4.7.2.12 | Request Report BCSM Event..... | 141 | +| 4.7.2.12.1 | Description..... | 141 | +| 4.7.2.12.2 | Information Elements..... | 141 | +| 4.7.2.13 | Reset Timer..... | 142 | +| 4.7.2.13.1 | Description..... | 142 | +| 4.7.2.13.2 | Information Elements..... | 142 | +| 4.7.3 | gsmSCF – IM-SSF information flows for MRFC related operations..... | 142 | +| 4.7.3.1 | Cancel..... | 142 | +| 4.7.3.1.1 | Description..... | 142 | +| 4.7.3.1.2 | Information Elements..... | 143 | +| 4.7.3.2 | Play Announcement..... | 143 | +| 4.7.3.2.1 | Description..... | 143 | +| 4.7.3.2.2 | Information Elements..... | 143 | +| 4.7.3.3 | Prompt And Collect User Information (received information)..... | 144 | +| 4.7.3.3.1 | Description..... | 144 | +| 4.7.3.3.2 | Information Elements..... | 144 | +| 4.7.3.4 | Prompt And Collect User Information ack (received information)..... | 145 | +| 4.7.3.4.1 | Description..... | 145 | +| 4.7.3.4.2 | Information Elements..... | 145 | +| 4.7.3.5 | Specialized Resource Report..... | 146 | +| 4.7.3.5.1 | Description..... | 146 | +| 4.7.3.5.2 | Information Elements..... | 146 | +| 4.7.4 | IM-SSF to HSS information flows..... | 146 | +| 4.7.4.1 | Any Time Subscription Interrogation request..... | 146 | + +| | | | +|------------------------|------------------------------------------------------|-----| +| 4.7.4.1.1 | Description ..... | 146 | +| 4.7.4.1.2 | Information Elements ..... | 146 | +| 4.7.4.2 | Notify Subscriber Data Change ack..... | 146 | +| 4.7.4.2.1 | Description ..... | 146 | +| 4.7.4.2.2 | Information Elements ..... | 146 | +| 4.7.5 | HSS to IM-SSF information flows ..... | 146 | +| 4.7.5.1 | Any Time Subscription Interrogation ack ..... | 146 | +| 4.7.5.1.1 | Description ..... | 146 | +| 4.7.5.1.2 | Information Elements ..... | 147 | +| 4.7.5.2 | Notify Subscriber Data Change ..... | 147 | +| 4.7.5.2.1 | Description ..... | 147 | +| 4.7.5.2.2 | Information Elements ..... | 147 | +| 5 | Control and interrogation of subscription data ..... | 148 | +| 5.1 | Architecture ..... | 148 | +| 5.2 | Procedures for CAMEL ..... | 148 | +| 5.2.1 | Any Time Subscription Interrogation..... | 148 | +| 5.2.2 | Any Time Modification..... | 148 | +| 5.2.3 | Notify Subscriber Data Change..... | 148 | +| 5.3 | Description of information flows ..... | 148 | +| 5.3.1 | gsmSCF to HSS information flows ..... | 149 | +| 5.3.1.1 | Any Time Modification Request ..... | 149 | +| 5.3.1.1.1 | Description ..... | 149 | +| 5.3.1.2 | Any Time Subscription Interrogation Request ..... | 149 | +| 5.3.1.2.1 | Description ..... | 149 | +| 5.3.1.2.2 | Information Elements ..... | 149 | +| 5.3.1.3 | Notify Subscriber Data Change response ..... | 149 | +| 5.3.1.3.1 | Description ..... | 149 | +| 5.3.2 | HSS to gsmSCF information flows ..... | 149 | +| 5.3.2.1 | Any Time Modification ack..... | 149 | +| 5.3.2.1.1 | Description ..... | 149 | +| 5.3.2.1.2 | Information Elements ..... | 149 | +| 5.3.2.2 | Any Time Subscription Interrogation ack ..... | 150 | +| 5.3.2.2.1 | Description ..... | 150 | +| 5.3.2.2.2 | Information Elements ..... | 150 | +| 5.3.2.3 | Notify Subscriber Data Change ..... | 150 | +| 5.3.2.3.1 | Description ..... | 150 | +| 5.3.2.3.2 | Information Elements ..... | 150 | +| 6 | Subscriber Location and State retrieval ..... | 150 | +| 6.1 | Architecture ..... | 150 | +| 6.2 | Procedures for CAMEL ..... | 150 | +| 6.2.1 | Any Time Interrogation..... | 150 | +| 6.3 | Description of information flows ..... | 151 | +| 6.3.1 | gsmSCF to HSS information flows ..... | 151 | +| 6.3.1.1 | Any Time Interrogation Request ..... | 151 | +| 6.3.1.1.1 | Description ..... | 151 | +| 6.3.2 | HSS to gsmSCF information flows ..... | 151 | +| 6.3.2.1 | Any Time Interrogation ack..... | 151 | +| 6.3.2.1.1 | Description ..... | 151 | +| Annex A (informative): | Change history..... | 152 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the stage 2 description for the fourth phase (see 3GPP TS 22.078 [2]) of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the stage 2 description for the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services for the IP Multimedia Core Network (IM CN) Subsystem. + +# --- 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: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.078: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1". +- [3] 3GPP TS 22.228: "3rd Generation Partnership Project; Technical Specification Group Systems Aspects; IP Multimedia (IM) Subsystem –Stage 1". +- [4] 3GPP TS 23.078: "3rd Generation Partnership Project; Technical Specification Group Core Networks; Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 Stage 2 specification (Release 99)". +- [5] 3GPP TS 23.218: "3rd Generation Partnership Project; Technical Specification Group Core Networks; IP Multimedia (IM) Session Handling; IP Multimedia Call Model. +- [6] 3GPP TS 23.228: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) Stage 2". +- [7] Void +- [8] 3GPP TS 24.229: "3rd Generation Partnership Project; Technical Specification Group Core Networks; IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3". +- [9] 3GPP TS 29.002: "3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification". +- [10] 3GPP TS 29.229: "3rd Generation Partnership Project; Technical Specification Group Core Networks; Cx and Dx Interfaces Based on the Diameter Protocol; Protocol details". +- [11] 3GPP TS 29.278: "3rd Generation Partnership Project; Technical Specification Group Core Network; Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4 CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +**Home Subscriber Server (HSS):** Functional entity containing the subscription related information to support the network entities actually handling calls/sessions. For subscribers requiring CAMEL support, the HSS includes some + +functionality that was present in the HLR in previous 3GPP releases for storing the information relevant to the current subscription regarding CAMEL Subscription Information for IMS. The HSS sends IM CAMEL Subscription Information data to the IM-SSF and CSE using a MAP interface. + +**IP Multimedia Service Switching Function (IM-SSF):** CAMEL functional entity that provides the interworking between SIP session control and the CAMEL state models. The IM-SSF also provides the CAMEL interface to HSS for downloading the subscriber's CAMEL Subscription Information data for IMS. + +**IP Multimedia Basic Call State Model (IM-BCSM):** IM-BCSM provides a high-level model of CSCF activities required to establish and maintain communication paths for users. As such, it identifies a set of basic call activities in a CSCF and shows how these activities are joined together to process a basic call. + +**IP Multimedia CAMEL Subscription Information (IM-CSI):** IM-CSI identifies the subscriber as having IP Multimedia CAMEL services. + +**IP Multimedia session:** IP Multimedia session and IP Multimedia call are treated as equivalent in this specification. + +**Originating IP Multimedia Basic Call State Model (O-IM-BCSM):** originating half of the IM-BCSM. The O-IM-BCSM corresponds to that portion of the IM-BCSM associated with the originating party. + +**Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI):** O-IM-CSI identifies the subscriber as having originating IP Multimedia CAMEL services. + +**Terminating IP Multimedia Basic Call State Model (T-IM-BCSM):** terminating half of the IM-BCSM. The T-IM-BCSM corresponds to that portion of the IM-BCSM associated with the terminating party. + +**Terminating IP Multimedia CAMEL Subscription Information (T-IM-CSI):** T-IM-CSI identifies the subscriber as having terminating IP Multimedia CAMEL services. + +## 3.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 21.905 [1]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|--------------------------------------------------------------| +| BCSM | Basic Call State Model | +| CAMEL | Customized Applications for Mobile network Enhanced Logic | +| CAP | CAMEL Application Part | +| CSCF | Call State Control Function | +| DP | Detection Point | +| D-IM-CSI | Dialled Service IP Multimedia CAMEL Subscription Information | +| EDP | Event Detection Point | +| FTN | Forwarded To Number | +| GPRS | General Packet Radio Service | +| gsmSCF | GSM Service Control Function | +| gsmSRF | GSM Specialised Resource Function | +| gsmSSF | GSM Service Switching Function | +| HPLMN | Home PLMN | +| HSS | Home Subscriber Server | +| IE | Information Element | +| IF | Information Flow | +| IP | Internet Protocol | +| ISC | IM-CN Service Control | +| I-CSCF | Interrogating CSCF | +| IM | IP Multimedia | +| IM-BCSM | IP Multimedia Basic Call State Model | +| IMCN | IP Multimedia Core Network | +| imenSSF | IM CN Service Switching Function | +| IM-CSI | IP Multimedia CAMEL Subscription Information | +| IM-SSF | IP Multimedia Service Switching Function | +| IPLMN | Interrogating PLMN | +| MGCF | Media Gateway Control Function | +| MO | Mobile Originating | +| MT | Mobile Terminating | + +| | | +|-----------|----------------------------------------------------------| +| NNI | Network Node Interface | +| O-IM-BCSM | Originating IP Multimedia Basic Call State Model | +| O-IM-CSI | Originating IP Multimedia CAMEL Subscription Information | +| PIC | Point In Call | +| PLMN | Public Land Mobile Network | +| P-CSCF | Proxy CSCF | +| SIP | Session Initiation Protocol | +| S-CSCF | Serving CSCF | +| SSME | Service Switching Function Management Entity | +| T-IM-BCSM | Terminating IP Multimedia Basic Call State Model | +| VT-IM-CSI | Terminating IP Multimedia CAMEL Subscription Information | +| TDP | Trigger Detection Point | +| UNI | User Network Interface | +| VPLMN | Visited PLMN | + +# 4 CAMEL/IP Multimedia Core Network Interworking + +## 4.1 Architecture + +This subclause describes the functional architecture needed to support CAMEL interactions with the S-CSCF in the IP Multimedia Subsystem. The IM-SSF is a SIP Application Server that interfaces SIP to CAP. The generic SIP Application Server behaviour of the IM-SSF is specified in 3GPP TS 23.218 [5]. + +### 4.1.1 Functional Entities used for CAMEL at IP Multimedia Registration + +Figure 4.1 shows the functional entities involved when an MS registers for IP Multimedia session requiring CAMEL support. General registration procedure is detailed in 3GPP TS 23.228 [6]. Upon notification of a UE's registration, the IM-SSF requests O-IM-CSI, D-IM-CSI, VT-IM-CSI data from the HSS over the Si interface. + +![Figure 4.1: Functional architecture for support of CAMEL when mobile registers for IP Multimedia session. The diagram shows the Home Network containing HSS, IM-SSF, and S-CSCF, and the Interrogating Network containing the MS. The HSS is connected to the IM-SSF via the Si Interface. The IM-SSF is connected to the S-CSCF via the ISC Interface. The S-CSCF is connected to the MS via the Cx Interface. The HSS is also connected to the S-CSCF via the Cx Interface.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +``` + +graph TD + subgraph Home_Network [Home Network] + HSS((HSS)) + IM_SSF((IM-SSF)) + S_CSCF((S-CSCF)) + end + subgraph Interrogating_Network [Interrogating Network] + MS[MS] + end + HSS -- Si Interface --> IM_SSF + IM_SSF -- ISC Interface --> S_CSCF + S_CSCF -- Cx Interface --> MS + HSS -- Cx Interface --> S_CSCF + +``` + +Figure 4.1: Functional architecture for support of CAMEL when mobile registers for IP Multimedia session. The diagram shows the Home Network containing HSS, IM-SSF, and S-CSCF, and the Interrogating Network containing the MS. The HSS is connected to the IM-SSF via the Si Interface. The IM-SSF is connected to the S-CSCF via the ISC Interface. The S-CSCF is connected to the MS via the Cx Interface. The HSS is also connected to the S-CSCF via the Cx Interface. + +Figure 4.1: Functional architecture for support of CAMEL when mobile registers for IP Multimedia session + +### 4.1.2 Functional Entities used for CAMEL for MO and MT IP Multimedia session + +Figure 4.2 shows the functional entities involved in a Mobile Originated IP Multimedia session requiring CAMEL support. The same functional architecture applies in a Mobile Terminated IP Multimedia session for CAMEL. + +![Figure 4.2: Functional architecture for support of CAMEL control of a MO IP Multimedia session. The diagram shows a 'Home Network' containing HSS, gsmSCF, and IM-SSF. The HSS is connected to the gsmSCF via a MAP interface. The gsmSCF is connected to the IM-SSF via a CAP interface. The IM-SSF is connected to the HSS via a Si interface. The IM-SSF is connected to the S-CSCF via an ISC Interface. The S-CSCF is connected to the MS (Mobile Station) via an ISC Interface. The S-CSCF is located in the 'Interrogating Network'.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +graph TD + subgraph Home_Network [Home Network] + HSS((HSS)) + gsmSCF((gsmSCF)) + IM_SSF((IM-SSF)) + S_CSCF((S-CSCF)) + end + subgraph Interrogating_Network [Interrogating Network] + MS((MS)) + end + HSS -- MAP --> gsmSCF + gsmSCF -- CAP --> IM_SSF + IM_SSF -- Si --> HSS + IM_SSF -- ISC Interface --> S_CSCF + S_CSCF -- ISC Interface --> MS + +``` + +Figure 4.2: Functional architecture for support of CAMEL control of a MO IP Multimedia session. The diagram shows a 'Home Network' containing HSS, gsmSCF, and IM-SSF. The HSS is connected to the gsmSCF via a MAP interface. The gsmSCF is connected to the IM-SSF via a CAP interface. The IM-SSF is connected to the HSS via a Si interface. The IM-SSF is connected to the S-CSCF via an ISC Interface. The S-CSCF is connected to the MS (Mobile Station) via an ISC Interface. The S-CSCF is located in the 'Interrogating Network'. + +Figure 4.2: Functional architecture for support of CAMEL control of a MO IP Multimedia session + +## 4.2 Interfaces defined for an IM-SSF based Application Server + +### 4.2.1 CSCF – IM-SSF interface + +This interface is the IP Multimedia Service Control interface (ISC). This interface shall be based on SIP as detailed in 3GPP TS 24.229 [8]. + +### 4.2.2 IM-SSF - gsmSCF interface + +This interface is used by the gsmSCF to control an IP Multimedia session in a certain IM-SSF. Relationships between the IM-SSF and the gsmSCF on this interface are opened as a result of the IM-SSF sending a request for instructions to the gsmSCF. This interface shall be based on 3GPP TS 29.278 [11]. + +### 4.2.3 HSS – IM-SSF interface + +This interface is the Si interface and is used to send CAMEL related subscriber data to the IM-SSF, e.g. IM-CSI. This interface shall be a MAP interface as described in 3GPP TS 29.002 [9]. + +## 4.3 Detection Points (DPs) + +Certain basic call events may be visible to the GSM Service Control Function (gsmSCF). The DPs are the points in call at which these events are detected. + +A DP can be armed in order to notify the gsmSCF that the DP was encountered, and potentially to allow the gsmSCF to influence subsequent handling of the call. If the DP is not armed, the processing entity continues the processing without gsmSCF involvement. + +Three different types of DPs are identified: + +- Trigger Detection Point - Request (TDP-R). + +This detection point is statically armed and initiates a CAMEL control relationship when encountered and there is no existing relationship due to the same CSI. Processing is suspended when the DP is encountered. + +- Event Detection Point - Request (EDP-R). + +This detection point is dynamically armed within the context of a CAMEL control relationship. Processing is suspended when encountering the DP and the IM-SSF waits for instructions from the gsmSCF. + +- Event Detection Point - Notification (EDP-N). + +This detection point is dynamically armed within the context of a CAMEL control relationship. Processing is not suspended when encountering the DP. + +The DPs are characterized in the following clauses. + +### 4.3.1 Arming/Disarming mechanism + +A DP may be statically armed or dynamically armed. + +The following arming rules apply: + +- DP for a mobile originating call handling is statically armed in the IM-SSF as a result of O-IM-CSI and D-IM-CSI data delivery from the HSS. Likewise, DP for mobile terminating call handling is statically armed in the IM-SSF as a result of VT-IM-CSI data delivery from the HSS. Static arming of DPs in the IM-SSF occurs during the UE's registration in the IMS CN. Basically, when the IM-SSF is notified of the UE's initial registration, the IM-SSF queries the HSS for the subscriber's CAMEL Subscription Information via the Si interface. +- A DP is dynamically armed by the gsmSCF within the context of a CAMEL control relationship as a result of IM-SSF receiving the RequestReportBCSMEVENT operation. +- A Request Report BCSM Event information flow for a detection point for a leg overwrites any previous Request Report BCSM Event information flow for that detection point for that leg. + +The following disarming rules apply: + +- A statically armed DP is disarmed when the IP Multimedia CSI data is withdrawn in the HSS. Only TDP-Rs can be disarmed using this mechanism. +- If an armed EDP is met, then it is disarmed. +- If an EDP is met that causes the release of the related leg, then all EDPs related to that leg are disarmed. +- If a call session is released, then all EDPs related to that call session are disarmed. +- If an EDP is met, then other EDPs are disarmed, in accordance with the implicit disarming rule table specified in TS 23.078 Rel-99 4 (refer to the section for "Rules for Implicit Disarming of Event Detection Points"). + +If an EDP is armed, it can be explicitly disarmed by the gsmSCF by means of the RequestReportBCSMEVENT information flow. + +### 4.3.2 Criteria + +Criteria are the conditions that must be met in order for the IM-SSF to request instructions from the gsmSCF. + +DP criteria are checked in the IM-SSF. Criteria for originating DPs (i.e. Collected\_Info, Analysed\_Information, and Route\_Select\_Failure TDPs) are checked in the IM-SSF associated with the originating UE's S-CSCF. Criteria for terminating DPs (i.e. T\_Busy and T\_No\_Answer) are checked in the IM-SSF associated with the terminating UE's S-CSCF. + +Based on the Initial Filter Criteria information, the S-CSCF forwards the SIP message to the IM-SSF. The DP encountered is identified based on the SIP message received from the S-CSCF. Refer to table 4.2 and table 4.4 for mapping of SIP messages to CAMEL IM-BCSM Detection Points. + +#### 4.3.2.1 Criteria at Collected\_Info + +The following criteria are applicable for DP Collected\_Info: + +- Destination number triggering criterion: The HSS may store a list of up to 10 destination numbers and/or up to 3 number lengths. There is no restriction on the nature of address. There is no restriction on the numbering plan indicator. This criterion may be defined to be either "enabling" or "inhibiting". This criterion does not match when the destination number received from the S-CSCF is not an ISDN number. In this case, a dialogue with the gsmSCF may or may not be established depending on whether the criterion is inhibiting or enabling respectively. + +Triggering at DP Collected\_Info shall be strictly based on the destination number received from the S-CSCF. + +The destination number received from the S-CSCF shall not be modified before conditional triggering check takes place. + +If the destination number triggering criterion is enabling, then the IM-SSF may establish a dialogue with the gsmSCF if: + +- the destination number matches one of the destination number strings defined in the list; or +- the length of the destination number matches one of the destination number lengths defined in the list. + +In this test the destination number matches one of the destination number strings in the list if: + +- the nature of address of destination number is the same as the nature of address of the destination number string; +- the destination number is at least as long as the destination number string in the list; and +- all the digits in the destination number string in the list match the leading digits of the destination number. + +If the destination number triggering criterion is inhibiting, then the IM-SSF may establish a dialogue with the gsmSCF if: + +- the destination number does not match any of the destination number strings defined in the list; and +- the length of the destination number does not match any of the destination number lengths defined in the list. + +In this test the destination number matches one of the destination number strings in the list if: + +- the nature of address of destination number is the same as the nature of address of the destination number string; +- the destination number is at least as long as the destination number string in the list; and +- all the digits in the destination number string in the list match the leading digits of the destination number. + +#### 4.3.2.2 Criteria at DP Analysed\_Information + +##### 4.3.2.2.1 General + +The following criteria are applicable for DP Analysed\_Information: + +- Destination number triggering criterion: The HSS may store a list of up to 10 destination numbers. There is no restriction on the nature of address. There is no restriction on the numbering plan indicator. This criterion does not match when the destination number received from the S-CSCF or the gsmSCF is not an ISDN number. + +NOTE: The order in which the destination number criteria are checked in the IM-SSF is not determined. Hence, overlapping destination number criteria (e.g. use of "0800" and "0800123" for two different services) should be avoided, because they lead to unpredictable behaviour (i.e. either service might be triggered). + +Triggering at DP Analysed\_Info shall be based on the destination number received in the Connect operation from the gsmSCF during a Mobile Originating CAMEL Service. + +##### 4.3.2.2.2 Number comparison + +The following procedure shall be performed for the comparison of the destination number triggering criterion and the address information in the given order. + +1. The numbering plan indicators of both numbers are ignored. +2. The type of number/nature of address indicators of both numbers are compared. If there is a match of the type of number indicator, then the check shall be performed by comparing the digits as defined in step 6. If there is no match of the type of number the comparison procedure shall continue as follows. +3. If either or both of the address information and destination number triggering criterion includes a type of number/nature of address indicator other than "unknown", "national (significant) number" or "international number" then the destination number does not match the destination number triggering criterion. Otherwise the comparison procedure shall continue as follows. + +4. If there is a number (address information or destination number triggering criterion) with type of number/nature of address "unknown" this number shall be translated based on the numbering plan of the serving entity in either of the following ways: + - if the leading digits refer to an international prefix, those digits shall be removed and the type of number/nature of address shall be set to "international number". + - if the leading digits refer to a national (trunk) prefix, those digits shall be removed and the type of number/nature of address shall be set to "national (significant) number". + +If the leading digits refer neither to an international prefix nor to a national (trunk) prefix, then the destination number does not match the destination number triggering criterion. + +If there is a match of the type of number/nature of address indicator after this number modification, then the check shall be performed by comparing the digits as defined in step 6, otherwise the comparison procedure shall continue as follows. + +5. If the type of number/nature of address of the address information or of the destination number triggering criterion is "national (significant) number" this number shall be translated based on the numbering plan of the serving entity to international format by adding the country code of the serving entity to the number string. After this modification both numbers shall be in international format and shall be checked by comparing the digits as defined in step 6. +- 6 If the number digits of the address information are compared with the number digits of the destination number triggering criterion, then there is a match if: + - the destination number is at least as long as the destination number string of the destination number triggering criterion; and + - all the digits in the destination number string of the destination number triggering criterion match the leading digits of the destination number. + +The check described in this clause shall be repeated for every number contained in the destination number triggering criterion of the D-IM-CSI until a match is recognised and DP Analysed\_Info is triggered, or until all the destination numbers have been checked without a match being recognised. In the latter case DP Analysed\_Info is not triggered. + +#### 4.3.2.3 Criteria at DP Route\_Select\_Failure + +The HSS may store a list of up to 5 cause values. + +The following criteria are applicable for DP Route\_Select\_Failure: + +- Release cause code. + +The trigger criteria is met if the cause code received from the terminating party's network (could be a PSTN or an IMS network) is equal to at least one of the cause codes in the trigger criteria list. + +If a O-IM-BCSM was already invoked and there is a relationship with the gsmSCF at that moment, then no additional relationship shall be initiated. + +#### 4.3.2.4 Criteria at DP T\_Busy and T\_No\_Answer + +The HSS may store a list of up to 5 cause values. + +The triggering is based on the release cause code received from terminating UE's P-CSCF. + +The following criteria are applicable for DP T\_Busy and T\_No\_Answer: + +- Release cause code. + +The trigger criteria are met if the cause code received from the terminating UE's P-CSCF is equal to at least one of the cause codes in the trigger criteria list. + +If trigger criteria are satisfied, then the corresponding Service Logic shall be invoked. + +## 4.4 Description of CAMEL Subscriber Data + +### 4.4.1 IP Multimedia CAMEL Subscription Information (IM-CSI) + +This subclause defines the contents of the IP Multimedia CAMEL Subscription Information. IM-CSI data are provisioned in the HSS for subscribers having originating and/or terminating IP Multimedia CAMEL services. This information shall be sent by the HSS to the IM-SSF via the Si Interface. The IM-CSI data contains the O-IM-CSI, D-IM-CSI, and VT-IM-CSI. + +#### 4.4.1.1 Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI) + +##### 4.4.1.1.1 gsmSCF Address + +Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routing. + +##### 4.4.1.1.2 Service Key + +The Service Key identifies to the gsmSCF the service logic that shall apply. + +##### 4.4.1.1.3 Default Call Handling + +The Default Call Handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. + +##### 4.4.1.1.4 TDP List + +The TDP List indicates on which detection point triggering shall take place. The following trigger detection points are possible: DP Collected\_Info and DP Route\_Select\_Failure. + +##### 4.4.1.1.5 CAMEL Capability Handling + +CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. + +##### 4.4.1.1.6 CSI Status + +The CSI state indicates whether the O-IM-CSI is active or not. + +##### 4.4.1.1.7 Notification Flag + +The notification flag indicates whether changes of the O-IM-CSI shall trigger the Notification on Change of Subscriber Data. In order to update the IM-SSF of IM CSI changes, this flag shall be set to yes. + +##### 4.4.1.1.8 DP Criteria + +The DP criteria indicate whether the IM-SSF shall request the gsmSCF for instructions. + +#### 4.4.1.2 Dialled Services IP Multimedia CAMEL Subscription Information (D-IM-CSI) + +##### 4.4.1.2.1 gsmSCF Address + +Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routing. + +##### 4.4.1.2.2 Service Key + +The Service Key identifies to the gsmSCF the service logic that shall apply. + +##### 4.4.1.2.3 Default Call Handling + +The Default Call Handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. + +##### 4.4.1.2.4 CAMEL Capability Handling + +CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. + +##### 4.4.1.2.5 CSI Status + +The CSI state indicates whether the D-IM-CSI is active or not. + +##### 4.4.1.2.6 Notification Flag + +The notification flag indicates whether changes of the D-IM-CSI shall trigger the Notification on Change of Subscriber Data. In order to update the IM-SSF of IM CSI changes, this flag shall be set to yes. + +##### 4.4.1.2.7 DP Criteria + +The DP criteria indicate whether the IM-SSF shall request the gsmSCF for instructions. + +#### 4.4.1.3 Terminating IP Multimedia CAMEL Subscription Information (VT-IM-CSI) + +##### 4.4.1.3.1 gsmSCF Address + +Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routing. + +##### 4.4.1.3.2 Service Key + +The Service Key identifies to the gsmSCF the service logic that shall apply. + +##### 4.4.1.3.3 Default Call Handling + +The Default Call Handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. + +##### 4.4.1.3.4 TDP List + +The TDP List indicates on which detection point triggering shall take place. The following trigger detection points are allowed: DP Terminating\_Attempt\_Authorised, DP T\_Busy, and DP T\_No\_Answer. + +##### 4.4.1.3.5 CAMEL Capability Handling + +CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. + +##### 4.4.1.3.6 CSI Status + +The CSI state indicates whether the VT-IM-CSI is active or not. + +##### 4.4.1.3.7 Notification Flag + +The notification flag indicates whether changes of the VT-IM-CSI shall trigger the Notification on Change of Subscriber Data. In order to update the IM-SSF of IM CSI changes, this flag shall be set to yes. + +##### 4.4.1.3.8 DP Criteria + +The DP criteria indicate whether the IM-SSF shall request the gsmSCF for instructions. + +#### 4.4.1.4 Other CAMEL Data + +##### 4.4.1.4.1 gsmSCF address list for CSI + +The gsmSCF address list for CSI indicates a list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent. In order to provide Notification on Change of Subscriber Data to the IM-SSF, the IM-SSF address shall be included in the gsmSCF address list. + +The IM-SSF address is added to the address list for notification in the HSS as described in subclause 4.6.1.2. + +The IM-SSF shall handle the receipt of the Notification on Change of Subscriber Data using the same procedure as that of a gsmSCF. + +## 4.5 Description of CAMEL State Models + +In the IM Subsystem, calls are controlled by the Serving CSCF (S-CSCF) where a subscriber is registered. A state model describes the call control behaviour of an IM-SSF. + +### 4.5.1 General Handling + +The Basic Call State Model (BCSM) is used to describe the handling of originating and terminating calls. It identifies the points in a call where gsmSCF based service applications is permitted to interact with the call control capabilities of an IM-SSF. Figure 4.3 illustrates how transitions between states, Detection Points and Points In Call components are shown in the BCSM diagrams. + +![Diagram of BCSM Components showing a Transition arrow pointing to a DP box, which is part of a Point In Call (PIC) box.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates the components of a Basic Call State Model (BCSM). It features a vertical arrow labeled "Transition" pointing downwards to a small square box labeled "DP" (Detection Point). This "DP" box is situated above a larger rectangular box labeled "Point In Call (PIC)". The "DP" box is partially overlaid on the top edge of the "PIC" box, indicating that a detection point is a specific location within a point in the call. + +Diagram of BCSM Components showing a Transition arrow pointing to a DP box, which is part of a Point In Call (PIC) box. + +Figure 4.3: BCSM Components + +### 4.5.2 Originating CAMEL Basic Call State Model (O-IM-BCSM) + +#### 4.5.2.1 Description of the O-IM-BCSM + +The O-IM-BCSM is used to model the behaviour of an IM-SSF for an originating call. When an armed DP is encountered, O-IM-BCSM processing is suspended at the DP and the IM-SSF indicates this to the gsmSCF if appropriate. + +![State transition diagram for Originating CAMEL Basic Call State Model (O-IM-BCSM).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the Originating CAMEL Basic Call State Model (O-IM-BCSM) as a state transition graph. It consists of five main states represented by rectangular boxes: **O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info** (top), **Analyse\_Information** (middle), **Routing & Alerting** (middle), **O\_Active** (bottom), and **O\_Exception** (top right). Transitions between these states are labeled with specific call events or data. **Basic Call transitions** (indicated by a solid arrow in the legend) lead from **O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info** to **Analyse\_Information** (labeled *Collected\_Info*), from **Analyse\_Information** to **Routing & Alerting** (labeled *Analysed\_Information*), and from **Routing & Alerting** to **O\_Active** (labeled *O\_Answer*). From **O\_Active**, a transition labeled *O\_Disconnect* leads to an unlabeled state on the left, which then loops back to the initial state. From **Routing & Alerting**, several failure transitions lead to **O\_Exception**: *Route\_Select\_Failure*, *O\_Busy*, *O\_No\_Answer*, and *O\_routing\_and\_alerting\_failure*. Additionally, **Analyse\_Information** has a transition labeled *invalid\_information* to **O\_Exception**, and **O\_Active** has a transition labeled *O\_active\_failure* to **O\_Exception**. Finally, an *O\_Abandon* transition leads from an unlabeled state on the left back to the initial **O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info** state. + +State transition diagram for Originating CAMEL Basic Call State Model (O-IM-BCSM). + +**Figure 4.4: Originating CAMEL Basic Call State Model (O-IM-BCSM)** + +The following table 4.1 defines the DPs that apply to originating calls. + +**Table 4.1: Description of the O-IM-BCSM DPs in an IM-SSF** + +| CAMEL Detection Point: | DP Type | Description: | +|-------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| DP Collected_Info | TDP-R | Indication that the O-IM-CSI is analysed | +| DP Analysed_Information | TDP-R | Availability of routeing address and nature of address. | +| DP Route_Select_Failure | TDP-R, EDP-N, EDP-R | Indication that the session establishment failed. | +| DP O_Busy | EDP-N, EDP-R | Indication that:
- a busy indication is received from the terminating party,
- a not reachable event is determined upon a SIP error response. | +| DP O_No_Answer | EDP-N, EDP-R | Indication that:
- an application timer associated with the O_No_Answer DP expires,
- a no answer event is determined upon SIP a error response | +| DP O_Answer | EDP-N, EDP-R | Indication that the session is accepted and answered by the terminating party. | +| DP O_Disconnect | EDP-N, EDP-R | A disconnect indication is received from the originating party or from the terminating party. | +| DP O_Abandon | EDP-N, EDP-R | Indication that a disconnect indication is received from the originating party during the session establishment procedure. | + +#### 4.5.2.2 Description of Points In Call + +This subclause describes the Points In Call for originating calls. The entry events, actions and exit events are described for each Point in Call. + +##### 4.5.2.2.1 O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info + +Entry events: + +- Disconnection and clearing of a previous call (DP O\_Disconnect) or default handling of exceptions by IM-SSF completed. +- Abandon event is reported from Analyse\_Information or Routing and Alerting PIC. +- Exception event is reported. + +Actions: + +- Interface is idled. +- Originating call: SIP INVITE request message containing the dialled number is received from MS. +- Information being analysed e.g., O-IM-CSI is analysed. + +Exit events: + +- Originating CSI is analysed. +- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during the PIC processing, the exception event is not visible because there is no corresponding DP. Example exception condition: Calling party abandons call. + +##### 4.5.2.2.2 Analyse\_Information + +Entry events: + +- Originating CSI is analysed. (DP Collected Info). +- New routeing information is received when Busy event (DP O\_Busy), Route Select Failure event (DP Route\_Select\_Failure), Not Reachable event (DP O\_Busy) or No Answer event (DP O\_No\_Answer) is reported from Routing and Alerting PIC. +- New routeing information is received when Disconnect event is reported from O\_Active PIC. + +###### Actions: + +- Compare the called party number with the dialled services information. + +###### Exit events: + +- Availability of routeing address and nature of address. (DP Analysed\_Information). +- An exception condition is encountered (e.g. wrong number)- this leads to the O\_Exception PIC. +- Calling party abandons the call- this leads to the O\_Abandon DP. + +##### 4.5.2.2.3            Routing and Alerting + +###### Entry events: + +- Availability of routeing address and nature of address. (DP Analysed\_Information). + +###### Actions: + +- Information is being analysed and/or translated according to dialling plan to determine routeing address. +- Routeing address being interpreted. +- Call is being processed by the terminating half BCSM. Continued processing of SIP call session setup (e.g., ringing) is taking place. Waiting for indication from terminating half BCSM that the call has been answered by terminating party. + +###### Exit events: + +- Indication from the terminating half BCSM that the call is accepted and answered by terminating party (DP O\_Answer). +- An exception condition is encountered - this leads to the O\_Exception PIC. +- Calling party abandons the call- this leads to the O\_Abandon DP. +- A busy indication is received from the terminating party - this leads to the O\_Busy DP. +- A not reachable indication is received from the terminating party - this leads to the O\_Busy DP. +- Attempt to select the route for the call fails - this leads to the Route\_Select\_Failure DP. + +If the no reply timer expires and DP O\_No\_Answer is armed - this leads to the O\_No\_Answer DP. + +##### 4.5.2.2.4            O\_Active + +###### Entry events: + +- Indication from the terminating half BCSM that the call is accepted and answered by the terminating party (DP O\_Answer). + +###### Actions: + +- SIP session established between originating party and terminating party. - Call release is awaited. + +###### Exit events: + +- A disconnection indication is received from the originating party, or received from the terminating party via the terminating half BCSM. (DP - O\_Disconnect). + +- An exception condition is encountered. + +##### 4.5.2.2.5 O\_Exception + +Entry events: + +- An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for a PIC can not be met. + +Actions: + +- Default handling of the exception condition is being provided. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as: +- If any relationship exists between the IM-SSF and the gsmSCF, the IM-SSF shall send an error information flow closing the relationships and indicating that any outstanding call handling instructions will not run to completion. +- Resources made available for setting up the SIP call session are released. + +Exit events: + +- Default handling of the exception condition by IM-SSF completed. + +### 4.5.3 Mapping of SIP Method/Response to O-IM-BCSM Detection Points + +This subclause describes mapping of SIP methods and responses to CAMEL Detection Points. + +**Table 4.2: Mapping of SIP Method/Response to CAMEL O-IM-BCSM DPs** + +| CAMEL O-IM-BCSM DP: | SIP Method/Response | +|-------------------------|-------------------------------------------------------------------------| +| DP Collected_Info | INVITE | +| DP Analysed_Information | N/A | +| DP Route_Select_Failure | 4XX (except 401, 407, 408, 480, 486),
5xx, and 6xx (except 600, 603) | +| DP O_Busy | 486 Busy Here
600 Busy Everywhere | +| DP O_No_Answer | 603 Decline
408 Request Timeout
480 Temp Unavailable | +| DP O_Answer | 200 OK | +| DP O_Disconnect | BYE | +| DP O_Abandon | CANCEL | + +### 4.5.4 Terminating CAMEL Basic Call State Model (T-IM-BCSM) + +#### 4.5.4.1 Description of the T-IM-BCSM + +The T-IM-BCSM is used to model the behaviour of an IM-SSF for a terminating call. When a DP is encountered, T-IM-BCSM processing is suspended at the DP and IM-SSF indicates this to the gsmSCF if appropriate. + +![Figure 4.5: Terminating CAMEL Basic Call State Model (T-IM-BCSM) state transition diagram. The diagram shows three main states: T_Null, Terminating Call Handling, and T_Active. Transitions are labeled with events like T_Abandon, Terminating_Attempt_Authorised, T_Busy, T_No_Answer, T_call_handling_failure, T_Disconnect, T_Answer, and T_active_failure. A legend indicates that solid arrows represent 'Basic Call transition'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +stateDiagram-v2 + [*] --> T_Null + T_Null --> Terminating_Call_Handling : Terminating_Attempt_Authorised + Terminating_Call_Handling --> T_Active : T_Answer + Terminating_Call_Handling --> [*] : T_Abandon + Terminating_Call_Handling --> T_Null : T_call_handling_failure + Terminating_Call_Handling --> T_Exception : T_Busy + Terminating_Call_Handling --> T_Exception : T_No_Answer + T_Active --> T_Null : T_Disconnect + T_Active --> [*] : T_Abandon + T_Active --> T_Exception : T_active_failure + T_Exception --> T_Null + +``` + +→ Basic Call transition + +Figure 4.5: Terminating CAMEL Basic Call State Model (T-IM-BCSM) state transition diagram. The diagram shows three main states: T\_Null, Terminating Call Handling, and T\_Active. Transitions are labeled with events like T\_Abandon, Terminating\_Attempt\_Authorised, T\_Busy, T\_No\_Answer, T\_call\_handling\_failure, T\_Disconnect, T\_Answer, and T\_active\_failure. A legend indicates that solid arrows represent 'Basic Call transition'. + +**Figure 4.5: Terminating CAMEL Basic Call State Model (T-IM-BCSM)** + +The following table 4.3 defines the DPs that apply to terminating calls. + +**Table 4.3: Description of T-IM-BCSM DPs in the S-CSCF** + +| CAMEL DP: | DP Type | Description: | +|-----------------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DP Terminating_Attempt_Authorised | TDP-R | Indication that the VT-IM-CSI is analysed. | +| DP T_Busy | TDP-R, EDP-N, EDP-R | Indication that:
- a busy indication is received from the terminating party,
- a not reachable event is determined (e.g. terminating party is not currently registered). | +| DP T_No_Answer | TDP-R, EDP-N, EDP-R | Indication that an application timer associated with the T_No_Answer DP expires. | +| DP T_Answer | EDP-N, EDP-R | Session is accepted and answered by terminating party. | +| DP T_Disconnect | EDP-N, EDP-R | A disconnect indication is received from the terminating party or from the originating party. | +| DP T_Abandon | EDP-N, EDP-R | A disconnect indication is received from the originating party during the session establishment procedure. | + +#### 4.5.4.2 Description of Points In Call + +This subclause describes the Points In Call for terminating calls. The entry events, actions and exit events are described for each Point in Call. + +##### 4.5.4.2.1 T\_Null + +Entry events: + +- Disconnection and clearing of a previous call (DP T\_Disconnect) or default handling of exceptions by IM-SSF completed. +- Abandon event is reported from Terminating Call Handling PIC. +- Exception event is reported. + +Actions: + +- Interface is idled. +- SIP INVITE message for terminating call request is received, the appropriate information is analysed. +- VT-IM-CSI is analysed. + +Exit events: + +- Terminating CSI is analysed. +- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during the PIC processing, the exception event is not visible because there is no corresponding DP. + +Example exception condition is: + +- Calling party abandons call. + +##### 4.5.4.2.2 Terminating Call Handling + +Entry events: + +- Terminating CSI (if available) is analysed. (DP Terminating\_Attempt\_Authorised). +- New routeing information is received when Busy event (DP T\_Busy) or No Answer event (DP T\_No\_Answer) is reported from Terminating Call Handling PIC. +- New routeing information is received when Disconnect event is reported from T\_Active PIC. +- New routeing information is received when the terminating party not reachable is reported from Terminating Call Handling PIC. + +Actions: + +- Routeing address and call type being interpreted. The next route or terminating access is being selected. +- The terminating party is being alerted. Waiting for the call to be answered by terminating party. + +Exit events: + +- Call is accepted and answered by terminating party. +- An exception condition is encountered - this leads to the T\_Exception PIC. Example exception conditions: the SIP call session request was not successful. +- Calling party abandons the call - this leads to the T\_Abandon DP. +- A busy indication is received from the terminating party's P-CSCF - this leads to the T\_Busy DP. +- Not reachable event detected from the terminating party's P-CSCF - this leads to the T\_Busy DP. +- If no reply timer expires and DP T\_No\_Answer is armed - this leads to the T\_No\_Answer DP. + +##### 4.5.4.2.3 T\_Active + +Entry events: + +- Indication that the call is accepted and answered by the terminating party. (DP T\_Answer). + +###### Actions: + +- SIP session established between originating party and terminating party. +- Call release is awaited. + +###### Exit events: + +- A disconnection indication is received from the terminating party, or received from the originating party via the originating half BCSM. (DP T\_Disconnect). +- An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure that means that the normal exit events for a PIC can not be met. + +##### 4.5.4.2.4 T\_Exception + +###### Entry events: + +- An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for PIC cannot be met. + +###### Actions: + +- Default handling of the exception condition is being provided. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as: + - If any relationship exists between the IM-SSF and the gsmSCF, the IM-SSF shall send an error information flow closing the relationships and indicating that any outstanding call handling instructions will not run to completion. + - Resources made available for setting up the SIP call session are released. + +###### Exit events: + +- Default handling of the exception condition by IM-SSF completed. + +### 4.5.5 Mapping of SIP Method/Response to T-IM-BCSM Detection Points + +This subclause describes mapping of SIP methods and responses to CAMEL Detection Points. + +**Table 4.4: Mapping of SIP Method/Response to CAMEL T-IM-BCSM DPs** + +| CAMEL T-IM-BCSM DP: | SIP Method/Response | +|----------------------------------------|---------------------------------------------------------------| +| DP Terminating_Attempt_
_Authorised | INVITE | +| DP T_Busy | 4XX (except 401, 407, 408, 480),
5xx, and 6xx (except 603) | +| DP T_No_Answer | 603 Decline
408 Request Timeout
480 Temp Unavailable | +| DP T_Answer | 200 OK | +| DP T_Disconnect | BYE | +| DP T_Abandon | CANCEL | + +## 4.6 Procedures for IM-SSF Application Server + +The SDLs in this specification illustrate how CAMEL modifies the normal multimedia call. They do not attempt to show all the details of multimedia handling in all the modes that support CAMEL. + +The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. + +### 4.6.1 Overall SDL Architecture + +![Diagram of SIP Registration into IM-SSF architecture](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +This diagram illustrates the architecture for SIP registration into the IM-SSF. At the top, a yellow box labeled 'gsmSCF' is shown with a note: 'The gsmSCF is not involved in this procedure.' Below it, a dashed box labeled 'IM-SSF' contains two white boxes: 'imcnSSF' and 'Register\_IM\_SSF'. To the left, a yellow box labeled 'HSS' is connected to the 'Register\_IM\_SSF' box via a dashed line labeled 'Si interface (MAP)'. Below the HSS, a yellow box labeled 'Mobile Station' is connected to a white box labeled 'S-CSCF' via a dashed line labeled 'SIP'. The 'S-CSCF' is also connected to the 'Register\_IM\_SSF' box via a dashed line labeled 'ISC interface'. A diagonal dashed line labeled 'Cx interface (DIAMETER)' connects the 'HSS' and the 'S-CSCF'. + +Diagram of SIP Registration into IM-SSF architecture + +Figure 4.6: SIP Registration into IM-SSF + +![Diagram of Originating Case architecture](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +This diagram illustrates the architecture for the Originating Case. At the top, a yellow box labeled 'gsmSCF' is connected to a dashed box labeled 'IM-SSF' via a dashed line labeled 'CAP interface'. The 'IM-SSF' box contains two white boxes: 'imcnSSF' and 'MO\_IM\_SSF', connected by a dashed line labeled 'Internal interface'. Below the 'IM-SSF', a white box labeled 'S-CSCF' is connected to the 'MO\_IM\_SSF' box via a dashed line labeled 'ISC interface'. To the left, a yellow box labeled 'MRFC' is connected to the 'S-CSCF' via a dashed line labeled 'Mr interface (SIP)'. Below the MRFC, a yellow box labeled 'Mobile Station' is connected to the 'S-CSCF' via a dashed line labeled 'SIP'. To the right, a yellow box labeled 'Destination CSCF' is connected to the 'S-CSCF' via a dashed line labeled 'SIP'. + +Diagram of Originating Case architecture + +Figure 4.7: Originating Case + +![Figure 4.8: Terminating Case. A network architecture diagram showing the flow of a terminating call. At the top, a yellow box labeled 'gsmSCF' is connected via a dashed line labeled 'CAP interface' to a dashed box labeled 'IM-SSF'. Inside the 'IM-SSF' box, there are two white boxes: 'imcnSSF' and 'MT_IM_SSF', connected by a dashed line labeled 'Internal interface'. Below the 'IM-SSF' box, a dashed line labeled 'ISC interface' connects to a white box labeled 'S-CSCF'. To the left of the 'S-CSCF', a yellow box labeled 'Mobile Station' is connected via a dashed line labeled 'SIP'. To the right of the 'S-CSCF', a yellow box labeled 'Originating CSCF' is connected via a dashed line labeled 'SIP'. A yellow box labeled 'MRFC' is located on the left, with a dashed line labeled 'Mr interface (SIP)' connecting it to the 'S-CSCF'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Figure 4.8: Terminating Case. A network architecture diagram showing the flow of a terminating call. At the top, a yellow box labeled 'gsmSCF' is connected via a dashed line labeled 'CAP interface' to a dashed box labeled 'IM-SSF'. Inside the 'IM-SSF' box, there are two white boxes: 'imcnSSF' and 'MT\_IM\_SSF', connected by a dashed line labeled 'Internal interface'. Below the 'IM-SSF' box, a dashed line labeled 'ISC interface' connects to a white box labeled 'S-CSCF'. To the left of the 'S-CSCF', a yellow box labeled 'Mobile Station' is connected via a dashed line labeled 'SIP'. To the right of the 'S-CSCF', a yellow box labeled 'Originating CSCF' is connected via a dashed line labeled 'SIP'. A yellow box labeled 'MRFC' is located on the left, with a dashed line labeled 'Mr interface (SIP)' connecting it to the 'S-CSCF'. + +**Figure 4.8: Terminating Case** + +#### 4.6.1.1 Handling of Registration and De-registration in the IM-SSF + +During the UE registration, the HSS shall send the filter criteria for the IM-SSF to the S-CSCF if the subscriber is provisioned with IP Multimedia CAMEL Subscription Information data at the HSS. + +- The HSS shall include the IMSI data for the subscriber within the Service Information element of the filter criteria for IM-SSF. The IMSI shall be used for querying the HSS for CAMEL Subscription Information data via a MAP interface. + +The CAMEL service provider determines the actual format of the data sent within the Service Information element of the filter criteria (e.g. IMSI). The actual format is transparent to the S-CSCF i.e. CAMEL service information is not processed, analysed, or evaluated by the S-CSCF. It is, however, known to the IM-SSF, gsmSCF, and the HSS (for provisioning of the service information data). + +If a registration/de-registration request matches the filter criteria of the IM-SSF, the S-CSCF informs the IM-SSF of the request by performing a third party registration/de-registration i.e. a SIP REGISTER message is sent from the S-CSCF to the IM-SSF. + +General handling of IP Multimedia registration, re-registration, de-registration and receipt of initial filter criteria at the S-CSCF is specified in 3GPP TS 23.228 [6] and 23.218 [5]. + +The process and the procedures specific to CAMEL are specified in this subclause: + +- Process Register\_IM\_SSF; +- Procedure CAMEL\_IMCN\_Register; +- Procedure CAMEL\_IMCN\_DeRegister. + +##### 4.6.1.1.1 Procedure CAMEL\_IMCN\_Register + +When querying the HSS for the subscriber's IM CSI data, the IM-SSF does not have to wait for the HSS's response on the first query before the subsequent queries are done. i.e. Sending of multiple Any Time Interrogation operations can be done in parallel. However, the IM-SSF shall wait for all the responses from the HSS before it shall send a SIP response message to the S-CSCF. + +![Flowchart for Process Register_IM_SSF](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +### Process Register\_IM\_SSF 1(1) + +Process in IM-SSF for handling receipt of a SIP REGISTER method from the S-CSCF. + +Signals to/from the left are to/from the S-CSCF. + +``` +graph TD; Start([ ]) --> idle([idle]); idle --> REGISTER[/REGISTER/]; REGISTER --> Expires{Expires > 0}; Expires -- No --> DeRegister[CAMEL_IMCN DeRegister]; Expires -- Yes --> Register[CAMEL_IMCN Register]; DeRegister --> Idle([Idle]); Register --> Idle; +``` + +The flowchart illustrates the process for handling a SIP REGISTER method in the IM-SSF. It begins with an oval start symbol, leading to an 'idle' state. A 'REGISTER' input signal is received, leading to a decision diamond 'Expires > 0'. If 'No', the 'CAMEL\_IMCN DeRegister' process is executed. If 'Yes', the 'CAMEL\_IMCN Register' process is executed. Both processes lead to an 'Idle' state. + +Flowchart for Process Register\_IM\_SSF + +Figure 4.9: Process Register\_IM\_SSF (sheet 1) + +![Flowchart for procedure CAMEL_IMCN_Register. It starts with a decision 'Subscriber profile downloaded?'. If 'Yes', it sends a '200 OK' response. If 'No', it sends an 'ATSI_query' with requested IM CSI (O-IM-CSI, VT-IM-CSI, D-IM-CSI) and waits for a response. The response can be 'ATSI_Ack' or 'ATSI negative Response'. 'ATSI_Ack' leads to 'Store Subscriber info' and then a decision 'More IM CSI to be requested?'. If 'Yes', it loops back to the start. If 'No', it checks 'Atleast one IM CSI is received?'. If 'Yes', it sends '200 OK'. If 'No', it sends '606 Not Acceptable'. 'ATSI negative Response' leads to a decision 'Information Not Available?'. If 'Yes', it sends an error. If 'No', it loops back to the start.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +### procedure CAMEL\_IMCN\_Register + +Procedure in IM-SSF when notified of a UE's registration in the IM CN. + +Signals to/from the left are to/from the S-CSCF, and signals to/from the right are to/from the HSS. + +1(1) + +``` +graph TD; Start([ ]) --> Q1{Subscriber profile downloaded?}; Q1 -- Yes --> R1{{200 OK}}; R1 --> End1(( )); Q1 -- No --> Q2{{ATSI_query}}; Q2 --> Info[Requested IM CSI: +O-IM-CSI +VT-IM-CSI +D-IM-CSI]; Info --> W[Wait for response]; W --> Q3{ }; Q3 -- ATSI_Ack --> S[Store Subscriber info]; S --> Q4{More IM CSI to be requested?}; Q4 -- Yes --> End2((1)); Q4 -- No --> Q5{Atleast one IM CSI is received?}; Q5 -- Yes --> R2{{200 OK}}; R2 --> End3(( )); Q5 -- No --> R3{{606 Not Acceptable}}; R3 --> End4(( )); Q3 -- ATSI_negative_Response[ATSI negative Response] --> Q6{ }; Q6 -- Yes --> Error["Error = 'Information Not Available?'"]; Q6 -- No --> End5((1)); +``` + +Flowchart for procedure CAMEL\_IMCN\_Register. It starts with a decision 'Subscriber profile downloaded?'. If 'Yes', it sends a '200 OK' response. If 'No', it sends an 'ATSI\_query' with requested IM CSI (O-IM-CSI, VT-IM-CSI, D-IM-CSI) and waits for a response. The response can be 'ATSI\_Ack' or 'ATSI negative Response'. 'ATSI\_Ack' leads to 'Store Subscriber info' and then a decision 'More IM CSI to be requested?'. If 'Yes', it loops back to the start. If 'No', it checks 'Atleast one IM CSI is received?'. If 'Yes', it sends '200 OK'. If 'No', it sends '606 Not Acceptable'. 'ATSI negative Response' leads to a decision 'Information Not Available?'. If 'Yes', it sends an error. If 'No', it loops back to the start. + +Figure 4.10: Procedure CAMEL\_IMCN\_Register (sheet 1) + +![Flowchart for procedure CAMEL_IMCN_DeRegister. The flow starts at a top connector, proceeds to a decision 'Subscriber IM-CSI data available'. If 'No', it goes to a '200 OK' connector. If 'Yes', it goes to 'Delete Subscriber IM-CSI data', which then leads to the '200 OK' connector. The flowchart ends at a bottom connector.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +procedure CAMEL\_IMCN\_DeRegister + +1(1) + +Procedure in IM-SSF when notified of a UE's de-Registration. + +Signals to/from the left are to /from the S-CSCF. + +``` +graph TD; Start([ ]) --> Decision{Subscriber IM-CSI data available}; Decision -- No --> OK{{200 OK}}; Decision -- Yes --> Delete[Delete Subscriber IM-CSI data]; Delete --> OK; OK --> End(( )) +``` + +Flowchart for procedure CAMEL\_IMCN\_DeRegister. The flow starts at a top connector, proceeds to a decision 'Subscriber IM-CSI data available'. If 'No', it goes to a '200 OK' connector. If 'Yes', it goes to 'Delete Subscriber IM-CSI data', which then leads to the '200 OK' connector. The flowchart ends at a bottom connector. + +Figure 4.11: Procedure CAMEL\_IMCN\_DeRegister (sheet 1) + +#### 4.6.1.2 Handling of Notify Subscriber Data Change + +When the HSS updates the CSI for a subscriber in the IP Multimedia CN subsystem, the HSS shall send a Notify Subscriber Data Change to the IM-SSF if all of the following conditions are true: + +- The IM CSI data is marked with the Notification Flag +- The IM-SSF address is included in the gsmSCF address list + +The IM-SSF address shall be added in the gsmSCF address list at the HSS for notification of IM-CSI updates if one of the following conditions occurs: + +- a. The HSS is notified of the subscriber's registration at the S-CSCF (via Cx interface), and the subscriber is provisioned with IM CSI data. +- b. Operator provisions HSS subscriber data with IMS CAMEL service while the subscriber is currently registered in the IMS network i.e. one or more IM CSI data is added to the subscriber's profile in the HSS. +- c. The HSS is notified of mobile termination for an unregistered subscriber (via Cx interface), and the subscriber is provisioned with IM CSI data + +The IM-SSF address shall be deleted from the gsmSCF address list when the HSS initiates, or is notified of, the UE's deregistration. + +The IM-SSF address in the gsmSCF address list may be changed when the HSS receives a notification of a registration for a UE with a S-CSCF name different from the previously assigned S-CSCF name (i.e. re-registration from HSS point of view). The HSS shall overwrite the existing IM-SSF address with the IM-SSF address associated with the new S-CSCF name. + +The HSS procedure for sending the Notify Subscriber Data Change to the IM-SSF is the same procedure used for notifying the gsmSCFs in the Circuit Switched CN. This procedure is described in Procedure CAMEL\_NSDC\_HLR specified in 3GPP TS 23.078 Rel-99[4]. + +The process specific to IM-SSF's handling of the Notify Subscriber Data Change is specified in this subclause: + +- Process Update\_CSI + +![Flowchart of Process Update_CSI](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +### Process Update\_CSI + +1(1) + +Process in IM-SSF when notified of a change of subscriber IM CSI data from the HSS. + +Signals signals to/from the right are to/from the HSS. + +``` +graph TD; Start([ ]) --> idle1([idle]); idle1 --> Step1[/NOTIFY SUBSCRIBER DATA CHANGE/]; Step1 --> Step2[Update/Delete Subscriber Data]; Step2 --> Step3[/NOTIFY SUBSCRIBER DATA CHANGE ACK/]; Step3 --> Idle2([Idle]); +``` + +The flowchart illustrates the 'Process Update\_CSI' sequence. It begins with an oval connector, leading to a state labeled 'idle'. The process then enters a loop: a parallelogram labeled 'NOTIFY SUBSCRIBER DATA CHANGE' is followed by a rectangle 'Update/Delete Subscriber Data', and then another parallelogram 'NOTIFY SUBSCRIBER DATA CHANGE ACK'. The sequence concludes with an oval connector labeled 'Idle'. + +Flowchart of Process Update\_CSI + +Figure 4.12: Process Update\_CSI (sheet 1) + +#### 4.6.1.3 Handling of Mobile Originated Calls in the IM-SSF + +The functional behaviour of the S-CSCF is specified in 3GPP TS 23.218 [5]. The process and the procedures specific to CAMEL are specified in this subclause: + +- Process MO\_IM\_SSF; +- Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT; +- Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT; +- Procedure CAMEL\_IMCN\_MO\_CANCEL; +- Procedure CAMEL\_IMCN\_MO\_ANSWER; +- Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL; +- Procedure CAMEL\_IMCN\_MO\_DISC1; +- Procedure CAMEL\_IMCN\_MO\_DISC2; +- Procedure CAMEL\_OCH\_CTR. + +Internal interface indicated with the "Int\_SRF\_" prefix within this subclause indicates internal interface with the MRFC. + +##### 4.6.1.3.1 Actions of the IM-SSF on receipt of Int\_Error + +The IM-SSF checks the default Call Handling parameter in the relevant CSI. + +If the default call handling is release, a BYE indication is sent to the MS. The IM-SSF then releases all resources and the invoked CAMEL procedure ends. + +If the call handling is continue, the IM-SSF continues processing without CAMEL support. + +##### 4.6.1.3.2 Actions of the IM-SSF on receipt of Int\_Continue + +The IM-SSF continues processing without any modification of call parameters. + +##### 4.6.1.3.3 Actions of the IM-SSF on receipt of Int\_Continue\_With\_Argument + +The IM-SSF continues processing with modified call parameters. The IM-SSF shall modify the call parameters by the information received in the Int\_Continue\_With\_Argument message. Call parameters that are not included in the Int\_Continue\_With\_Argument\_Message are unchanged. + +##### 4.6.1.3.4 Actions of the IM-SSF on receipt of Int\_Connect + +The IM-SSF continues processing with modified call parameters. The IM-SSF shall transparently modify the call parameters with the received information. Call parameters, which are not included in the Int\_Connect message, are unchanged. + +##### 4.6.1.3.5 Actions of the IM-SSF on receipt of Int\_Release\_Call + +A BYE is sent to the MS, and a BYE is sent to the destination CSCF. The release cause received in the Int\_Release\_Call is used. The IM-SSF then releases all call resources and all CAMEL processing ends. + +##### 4.6.1.3.6 Handling of procedure CAMEL\_OCH\_CTR, sheet 1 + +The IM-SSF behaves as a B2BUA (Back-2-Back User Agent) when a SIP INVITE is received for an outgoing call and SIP INVITE is sent to the MRFC (via S-CSCF) as a result of a CAP ConnectToResource request received from the SCF. + +A SIP response 100 Trying is sent after each INVITE but is not shown in the SDLs. + +The IM-SSF shall handle the 200 OK response from the MRFC as specified in 3GPP TS 23.218 [5]. + +#### 4.6.1.3.7 Handling of procedure CAMEL\_OCH\_CTR, sheet 5 + +The specifics on transporting information between the MRFC and the Application Server such as the IM-SSF, has not been standardised in 3GPP Rel-5 specifications for IMS. i.e. the SIP method to return the Prompt\_and\_Collect result from the MRFC to the IM-SSF, the SIP method for sending notification of play announcement completion to the IM-SSF when a request for a Specialised Resource Report was received, the SIP method to request the MRFC to play announcement and the SIP method to request the MRFC to prompt and collect user information, are not standardised. + +#### 4.6.1.3.8 Receipt of 100 Trying Provisional Response (Process MO\_IM\_SSF) + +The IM-SSF (acting as B2BUA) uses the S-CSCF as the next-hop server when sending the SIP INVITE to the destination S-CSCF. The 100 Trying provisional response received in the IM-SSF is actually generated and sent from the S-CSCF to indicate that the INVITE request has been received by the next-hop server (i.e. the S-CSCF) and is currently being processed. + +#### 4.6.1.3.9 Handling of internal timers in Process MO\_IM\_SSF + +The SIP B timer defined in 3GPP TS 24.229 [8] is used for IM-SSF handling of no response condition for an INVITE request, similar to the Circuit Switched handling of TNRy Timer for No Reply. The use of B timer in the IM-SSF is indicated in the SDL Process MO\_IM\_SSF. There are other SIP timers defined in 3GPP TS 24.229 [8] that are not specified in the SDLs for IM-SSF processing. The usage of these timers is based on the network's implementation of the IM-SSF (e.g. choice of UDP or TCP for transport of SIP, and how IM-SSF operates as both a UAS and a UAC - i.e. back-to-back UA). + +The following sub-clauses provide additional information on Process MO\_IM\_SSF's handling of the internal timers: + +Sheets 1-2: The inclusion of Expires header field in the INVITE method is optional and is used to indicate the duration of the invitation in seconds. When the timer fires before a final response is generated by the IM-SSF, the INVITE message is considered to be "expired". The IM-SSF shall report a call abandon event to the gsmSCF if requested and return a 487 Request Terminated to the originating S-CSCF. + +When the IM-SSF (taking the role of a UAC) sends out the INVITE request, the B timer (i.e. Tb timer) shall be used for the INVITE transaction timeout timer. Refer to 3GPP TS 24.229 [8] for the recommended B timer value. + +Sheet 3: When the IM-SSF (taking the role of a UAS) sends the 200 OK final response to the S-CSCF that sent the INVITE request, the IM-SSF shall start the Tack timer to monitor the receipt of the ACK request. Refer to 3GPP TS 24.229 [8] for the recommended ACK timer value. + +Sheet 4: The expiration of Tb timer shall be reported as a no answer event to the gsmSCF if requested. If the Tinvite timer expires, the IM-SSF shall report a call abandon event to the gsmSCF if requested. + +Sheet 5: The expiration of the Tack shall be reported to the gsmSCF as a call disconnect from the originating party if requested. + +![Flowchart for Process MO_IM_SSF. The flow starts with an oval connector, followed by an 'Idle' state, an 'INVITE' message, and a '100 Trying' response. It then enters an 'Initialise values' block with a side note setting various flags to False. A decision diamond asks 'INVITE Expires received?'. If 'Yes', it sets 'Tinvite := INVITE Expires received' and starts 'Tinvite'. If 'No', it skips to connector '3'. Both paths lead to connector '3'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +### Process MO\_IM\_SSF 1(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Idle([Idle]); Idle --> INVITE[/INVITE/]; INVITE --> 100Trying{100 Trying}; 100Trying --> Init[Initialise values]; Init -.-> InitNote["CAMEL_Invocation := False; +Provisional_Response_Received := False; +Final_Response_Received := False; +Cancel_Received := False;"]; Init --> Decision{INVITE Expires received?}; Decision -- Yes --> Tset[Tinvite := INVITE Expires received]; Tset --> Tstart[Start Tinvite]; Decision -- No --> Connector3((3)); Tstart --> Connector3; style Start fill:none,stroke:none; style Idle fill:none,stroke:none; style INVITE fill:none,stroke:none; style 100Trying fill:none,stroke:none; style Init fill:none,stroke:none; style InitNote fill:none,stroke:none; style Decision fill:none,stroke:none; style Tset fill:none,stroke:none; style Tstart fill:none,stroke:none; style Connector3 fill:none,stroke:none; +``` + +Flowchart for Process MO\_IM\_SSF. The flow starts with an oval connector, followed by an 'Idle' state, an 'INVITE' message, and a '100 Trying' response. It then enters an 'Initialise values' block with a side note setting various flags to False. A decision diamond asks 'INVITE Expires received?'. If 'Yes', it sets 'Tinvite := INVITE Expires received' and starts 'Tinvite'. If 'No', it skips to connector '3'. Both paths lead to connector '3'. + +Figure 4.13-1: Process MO\_IM\_SSF (sheet 1) + +![Flowchart for Process MO_IM_SSF (sheet 2). The process starts at connector 3, calls CAMEL_IMCN MO_O_IM_CSI_INIT, then checks the result. If 'Pass', it calls CAMEL_IMCN MO_D_IM_CSI_INIT and checks the result again. If 'Pass', it checks if CAMEL_Invocation is true. If true, it sends an INVITE, starts timer Tb, and waits for an answer. If false, it checks if 606 Not Acceptable. If 'Fail', it checks if 606 Not Acceptable. If 'Abort', it checks if 487 Request Terminated. If 'INVITE Expires', it sets Event := 'Timer expired', calls CAMEL_IMCN MO_CANCEL, and checks if 487 Request Terminated. All successful paths lead to connector 2, then Release Call Resources, and finally Idle. All failure/abort paths lead to connector 1.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +### Process MO\_IM\_SSF 2(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; 3((3)) --> C1[CAMEL_IMCN MO_O_IM_CSI_INIT]; C1 --> R1{Result ?}; R1 -- Pass --> C2[CAMEL_IMCN MO_D_IM_CSI_INIT]; R1 -- Fail --> 1((1)); R1 -- Abort --> 1; R1 -- "INVITE Expires" --> E1[Event := "Timer expired"]; C2 --> R2{Result ?}; R2 -- Pass --> C3{CAMEL_Invocation ?}; R2 -- Fail --> 1; R2 -- Abort --> 1; R2 -- "INVITE Expires" --> E2[Event := "Timer expired"]; C3 -- True --> INVITE[INVITE]; C3 -- False --> NA1{606 Not Acceptable}; INVITE --> STb[Start Tb]; STb --> WFA[Wait_For_Answer]; NA1 --> 1; NA1 --> NA2{606 Not Acceptable}; NA2 -- Fail --> 1; NA2 -- Abort --> 1; NA2 -- "INVITE Expires" --> E3[Event := "Timer expired"]; E1 --> C4[CAMEL_IMCN MO_CANCEL]; E2 --> C4; C4 --> RT1{487 Request Terminated}; RT1 --> 2((2)); RT1 --> 1; RT1 --> RCR[Release Call Resources]; RCR --> Idle([Idle]); +``` + +Flowchart for Process MO\_IM\_SSF (sheet 2). The process starts at connector 3, calls CAMEL\_IMCN MO\_O\_IM\_CSI\_INIT, then checks the result. If 'Pass', it calls CAMEL\_IMCN MO\_D\_IM\_CSI\_INIT and checks the result again. If 'Pass', it checks if CAMEL\_Invocation is true. If true, it sends an INVITE, starts timer Tb, and waits for an answer. If false, it checks if 606 Not Acceptable. If 'Fail', it checks if 606 Not Acceptable. If 'Abort', it checks if 487 Request Terminated. If 'INVITE Expires', it sets Event := 'Timer expired', calls CAMEL\_IMCN MO\_CANCEL, and checks if 487 Request Terminated. All successful paths lead to connector 2, then Release Call Resources, and finally Idle. All failure/abort paths lead to connector 1. + +Figure 4.13-2: Process MO\_IM\_SSF (sheet 2) + +![Flowchart for Process MO_IM_SSF. It starts with 'Wait_For_Answer' and branches based on responses: '100 Trying' leads to 'Cancel_Received?'; '1xx except 100' leads to '1xx' and then 'Cancel_Received?'; '200 OK' leads to 'Final_Response_Received := True', 'Stop Tb', and 'CAMEL_IMCN MO_ANSWER'. From 'Cancel_Received?', 'False' leads to 'Provisional_Response_Received := True' and 'Wait_For_Answer'; 'True' leads to 'CANCEL', 'CAMEL_IMCN MO_CANCEL', '487 Request Terminated', '200 OK', and connector '2'. From 'Final_Response_Received := True', it goes to 'Stop Tb', 'CAMEL_IMCN MO_ANSWER', and 'Result?'. 'Result?' has 'Pass' leading to '200 OK', 'Stop Tininvite', 'Start Tack', and 'Wait_For_ACK'; 'Reconnect' leads to connector '1'; 'Fail' leads to connector '2'.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +### Process MO\_IM\_SSF 3(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([Wait_For_Answer]) --> J1(( )); J1 --> T1{100 Trying}; J1 --> T2{1xx except 100}; J1 --> T3{200 OK}; T1 --> CR{Cancel_Received?}; T2 --> T2_1{1xx}; T2_1 --> CR; CR -- True --> C[CANCEL]; C --> CIMC[|CAMEL_IMCN MO_CANCEL|]; CIMC --> RT{487 Request Terminated}; RT --> OK1{200 OK}; OK1 --> C2((2)); CR -- False --> PR[Provisional_Response_Received := True]; PR --> WFA1([Wait_For_Answer]); T3 --> FR[Final_Response_Received := True]; FR --> ST[Stop Tb]; ST --> CIMA[|CAMEL_IMCN MO_ANSWER|]; CIMA --> Res{Result?}; Res -- Pass --> OK2{200 OK}; OK2 --> STI[Stop Tininvite]; STI --> STK[Start Tack]; STK --> WFA2([Wait_For_ACK]); Res -- Reconnect --> C1((1)); Res -- Fail --> C2; style J1 fill:none,stroke:none; style T1 fill:none,stroke:none; style T2 fill:none,stroke:none; style T3 fill:none,stroke:none; style T2_1 fill:none,stroke:none; style CR fill:none,stroke:none; style C fill:none,stroke:none; style CIMC fill:none,stroke:none; style RT fill:none,stroke:none; style OK1 fill:none,stroke:none; style PR fill:none,stroke:none; style FR fill:none,stroke:none; style ST fill:none,stroke:none; style CIMA fill:none,stroke:none; style Res fill:none,stroke:none; style OK2 fill:none,stroke:none; style STI fill:none,stroke:none; style STK fill:none,stroke:none; style WFA2 fill:none,stroke:none; style C1 fill:none,stroke:none; style C2 fill:none,stroke:none; +``` + +Flowchart for Process MO\_IM\_SSF. It starts with 'Wait\_For\_Answer' and branches based on responses: '100 Trying' leads to 'Cancel\_Received?'; '1xx except 100' leads to '1xx' and then 'Cancel\_Received?'; '200 OK' leads to 'Final\_Response\_Received := True', 'Stop Tb', and 'CAMEL\_IMCN MO\_ANSWER'. From 'Cancel\_Received?', 'False' leads to 'Provisional\_Response\_Received := True' and 'Wait\_For\_Answer'; 'True' leads to 'CANCEL', 'CAMEL\_IMCN MO\_CANCEL', '487 Request Terminated', '200 OK', and connector '2'. From 'Final\_Response\_Received := True', it goes to 'Stop Tb', 'CAMEL\_IMCN MO\_ANSWER', and 'Result?'. 'Result?' has 'Pass' leading to '200 OK', 'Stop Tininvite', 'Start Tack', and 'Wait\_For\_ACK'; 'Reconnect' leads to connector '1'; 'Fail' leads to connector '2'. + +Figure 4.13-3: Process MO\_IM\_SSF (sheet 3) + +![SDL diagram for Process MO_IM_SSF sheet 4. It shows state transitions from 'Wait_For_Answer' based on four inputs: CANCEL, 4xx/5xx/6xx responses, Tb expiry, and Tinvite expiry. Each path leads to various actions including CAMEL service calls, signal sending, and state transitions to connectors 1, 2, or 4.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +## Process MO\_IM\_SSF + +4(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` + + stateDiagram-v2 + state "Wait_For_Answer" as Wait_For_Answer + + [*] --> Wait_For_Answer + + Wait_For_Answer --> CANCEL_Input + Wait_For_Answer --> Error_Response + Wait_For_Answer --> Tb_expiry + Wait_For_Answer --> Tinvite_expiry + + state "CANCEL" as CANCEL_Input + CANCEL_Input --> Prov_Resp_Rec_1 + state "Provisional Response Received?" as Prov_Resp_Rec_1 + Prov_Resp_Rec_1 --> Cancel_Rec_True : False + Prov_Resp_Rec_1 --> CAMEL_CANCEL : True + state "Cancel_Received := True" as Cancel_Rec_True + Cancel_Rec_True --> Wait_For_Answer + state "CAMEL_IMCN_MO_CANCEL" as CAMEL_CANCEL + CAMEL_CANCEL --> CANCEL_Output + state "CANCEL" as CANCEL_Output + CANCEL_Output --> Req_Terminated + state "487 Request Terminated" as Req_Terminated + Req_Terminated --> OK_200 + state "200 OK" as OK_200 + OK_200 --> Exit_2 + + state "4xx, 5xx, 6xx" as Error_Response + Error_Response --> ACK + state "ACK" as ACK + ACK --> Set_Event_Code + state "Event := (Response Code)" as Set_Event_Code + Set_Event_Code --> Exit_2 + + state "Tb expiry" as Tb_expiry + Tb_expiry --> Prov_Resp_Rec_2 + state "Provisional Response Received?" as Prov_Resp_Rec_2 + Prov_Resp_Rec_2 --> Exit_2 : No + Prov_Resp_Rec_2 --> CANCEL_Tb : Yes + state "CANCEL" as CANCEL_Tb + CANCEL_Tb --> Set_Timer_Exp + state "Event := \"Timer expired\"" as Set_Timer_Exp + Set_Timer_Exp --> CAMEL_UNSUCCESSFUL + state "CAMEL_IMCN_MO_UNSUCCESSFUL" as CAMEL_UNSUCCESSFUL + CAMEL_UNSUCCESSFUL --> Result_Reconnect + state "Result = Reconnect?" as Result_Reconnect + Result_Reconnect --> Exit_1 : Yes + Result_Reconnect --> Exit_2 : No + + state "Tinvite expiry" as Tinvite_expiry + Tinvite_expiry --> Prov_Resp_Rec_3 + state "Provisional Response Received?" as Prov_Resp_Rec_3 + Prov_Resp_Rec_3 --> Exit_2 : No + Prov_Resp_Rec_3 --> CANCEL_Tinvite : Yes + state "CANCEL" as CANCEL_Tinvite + CANCEL_Tinvite --> Exit_4 + + state "1" as Exit_1 + state "2" as Exit_2 + state "4" as Exit_4 + +``` + +SDL diagram for Process MO\_IM\_SSF sheet 4. It shows state transitions from 'Wait\_For\_Answer' based on four inputs: CANCEL, 4xx/5xx/6xx responses, Tb expiry, and Tinvite expiry. Each path leads to various actions including CAMEL service calls, signal sending, and state transitions to connectors 1, 2, or 4. + +**Figure 4.13-4: Process MO\_IM\_SSF (sheet 4)** + +![SDL state transition diagram for Process MO_IM_SSF starting at state 'Wait_For_ACK'. Four branches exist: 1. Input 'ACK' leads to task 'Stop Tack', then decision 'Bye_Received?'. If True, it joins a common path to connector 1. If False, task 'Ack_Received := True', output 'ACK', and state 'Wait_For_Clear'. 2. Input 'BYE' leads to decision 'Ack_Received?'. If True, joins common path to connector 1. If False, task 'Bye_Received := True' and returns to state 'Wait_For_ACK'. 3. Input 'BYE' leads to procedure call 'CAMEL_IMCN MO_DISC1' and then to connector 2. 4. Internal signal 'Tack expiry' leads to output 'BYE', then decision 'Bye_Received?'. If True, joins common path to connector 1. If False, output 'ACK', output 'BYE', procedure call 'CAMEL_IMCN MO_DISC1', and then to connector 2. The common path to connector 1 includes a procedure call 'CAMEL_IMCN MO_DISC2' and a decision 'Result = Reconnect?'. If Yes, it goes to connector 1; if No, it goes to connector 2.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +### Process MO\_IM\_SSF + +5(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` + +stateDiagram-v2 + state "Wait_For_ACK" as Wait_For_ACK + state "Wait_For_Clear" as Wait_For_Clear + state "Wait_For_ACK" as Wait_For_ACK_Loop + + [*] --> Wait_For_ACK + + Wait_For_ACK --> ACK_In : ACK + Wait_For_ACK --> BYE_In1 : BYE + Wait_For_ACK --> BYE_In2 : BYE + Wait_For_ACK --> Tack_Exp : Tack expiry (Internal) + + ACK_In --> Stop_Tack : Stop Tack + Stop_Tack --> Bye_Rec_Dec1 : Bye_Received? + Bye_Rec_Dec1 --> Ack_Rec_True : False + Ack_Rec_True --> ACK_Out : Ack_Received := True + ACK_Out --> Wait_For_Clear : ACK + + BYE_In1 --> Ack_Rec_Dec : Ack_Received? + Ack_Rec_Dec --> Bye_Rec_True : False + Bye_Rec_True --> Wait_For_ACK_Loop : Bye_Received := True + + BYE_In2 --> MO_DISC1_1 : CAMEL_IMCN MO_DISC1 + MO_DISC1_1 --> Conn2 + + Tack_Exp --> BYE_Out1 : BYE + BYE_Out1 --> Bye_Rec_Dec2 : Bye_Received? + Bye_Rec_Dec2 --> ACK_Out2 : False + ACK_Out2 --> BYE_Out2 : ACK + BYE_Out2 --> MO_DISC1_2 : BYE + MO_DISC1_2 --> MO_DISC1_Task : CAMEL_IMCN MO_DISC1 + MO_DISC1_Task --> Conn2 + + Bye_Rec_Dec1 --> Common_Path : True + Ack_Rec_Dec --> Common_Path : True + Bye_Rec_Dec2 --> Common_Path : True + + Common_Path --> MO_DISC2 : CAMEL_IMCN MO_DISC2 + MO_DISC2 --> Reconnect_Dec : Result = Reconnect? + Reconnect_Dec --> Conn1 : Yes + Reconnect_Dec --> Conn2 : No + + state "1" as Conn1 + state "2" as Conn2 + +``` + +SDL state transition diagram for Process MO\_IM\_SSF starting at state 'Wait\_For\_ACK'. Four branches exist: 1. Input 'ACK' leads to task 'Stop Tack', then decision 'Bye\_Received?'. If True, it joins a common path to connector 1. If False, task 'Ack\_Received := True', output 'ACK', and state 'Wait\_For\_Clear'. 2. Input 'BYE' leads to decision 'Ack\_Received?'. If True, joins common path to connector 1. If False, task 'Bye\_Received := True' and returns to state 'Wait\_For\_ACK'. 3. Input 'BYE' leads to procedure call 'CAMEL\_IMCN MO\_DISC1' and then to connector 2. 4. Internal signal 'Tack expiry' leads to output 'BYE', then decision 'Bye\_Received?'. If True, joins common path to connector 1. If False, output 'ACK', output 'BYE', procedure call 'CAMEL\_IMCN MO\_DISC1', and then to connector 2. The common path to connector 1 includes a procedure call 'CAMEL\_IMCN MO\_DISC2' and a decision 'Result = Reconnect?'. If Yes, it goes to connector 1; if No, it goes to connector 2. + +Figure 4.13-5: Process MO\_IM\_SSF (sheet 5) + +![Flowchart for Process MO_IM_SSF. It starts with 'Wait_For_Clear', then branches into three paths: 1) BYE -> CAMEL_IMCN_MO_DISC1 -> connector 2; 2) BYE -> CAMEL_IMCN_MO_DISC2 -> Result = Reconnect? (Yes -> connector 1, No -> connector 2); 3) Int_Release Call (From imcnSSF) -> BYE -> BYE -> connector 2.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +### Process MO\_IM\_SSF + +6(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([Wait_For_Clear]) --> BYE1[/BYE/]; Start --> BYE2[/BYE/]; Start --> Int_Release[Int_Release Call]; Int_Release --- From_imcnSSF[From imcnSSF]; BYE1 --> CAMEL_IMCN_MO_DISC1[CAMEL_IMCN_MO_DISC1]; BYE2 --> CAMEL_IMCN_MO_DISC2[CAMEL_IMCN_MO_DISC2]; CAMEL_IMCN_MO_DISC1 --> J1(( )); CAMEL_IMCN_MO_DISC2 --> Reconnect{Result = Reconnect?}; Reconnect -- No --> J1; Reconnect -- Yes --> J2(( )); Int_Release --> BYE3[/BYE/]; BYE3 --> BYE4[/BYE/]; BYE4 --> J1; +``` + +Flowchart for Process MO\_IM\_SSF. It starts with 'Wait\_For\_Clear', then branches into three paths: 1) BYE -> CAMEL\_IMCN\_MO\_DISC1 -> connector 2; 2) BYE -> CAMEL\_IMCN\_MO\_DISC2 -> Result = Reconnect? (Yes -> connector 1, No -> connector 2); 3) Int\_Release Call (From imcnSSF) -> BYE -> BYE -> connector 2. + +Figure 4.13-6: Process MO\_IM\_SSF (sheet 6) + +![Flowchart for Procedure CAMEL_IMCN_MO_O_IM_CSI_INIT. The process starts with a decision 'O-IM-CSI invocation?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sets 'CAMEL_Invocation := True', stores original call parameters, and invokes 'Int_Invoke_imcnSSF (O-IM-CSI)'. It then waits for 'imcnSSF_Invoked'. From there, three paths are possible: 'Int_Error' leads to 'Result:= Fail' and ends; 'Int_imcnSSF_Invoked' leads to 'Int_DP_Collected_Info', then 'DP_Collected_Info', and ends; 'CANCEL' leads to 'CAMEL_IMCN_MO_CANCEL', then 'Result:= Abort' and ends.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +**Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT** 1(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for an outgoing call INVITE request \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Decision{O-IM-CSI invocation?}; Decision -- No --> Pass[Result:= Pass]; Pass --> End1(( )); Decision -- Yes --> True[CAMEL_Invocation := True]; True --> Store[Store original call parameters]; Store --> Invoke[Int_Invoke_imcnSSF O-IM-CSI]; Invoke --> Wait[Wait for imcnSSF_Invoked]; Wait --> Error{Int_Error}; Wait --> Invoked{Int_imcnSSF_Invoked}; Wait --> Cancel{CANCEL}; Error --> Fail[Result:= Fail]; Fail --> End2(( )); Invoked --> Info[Int_DP_Collected_Info]; Info --> DP[DP_Collected_Info]; DP --> End3(( )); Cancel --> CancelMsg[CAMEL_IMCN_MO_CANCEL]; CancelMsg --> Abort[Result:= Abort]; Abort --> End4(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT. The process starts with a decision 'O-IM-CSI invocation?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sets 'CAMEL\_Invocation := True', stores original call parameters, and invokes 'Int\_Invoke\_imcnSSF (O-IM-CSI)'. It then waits for 'imcnSSF\_Invoked'. From there, three paths are possible: 'Int\_Error' leads to 'Result:= Fail' and ends; 'Int\_imcnSSF\_Invoked' leads to 'Int\_DP\_Collected\_Info', then 'DP\_Collected\_Info', and ends; 'CANCEL' leads to 'CAMEL\_IMCN\_MO\_CANCEL', then 'Result:= Abort' and ends. + +Figure 4.14-1: Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT + +2(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for an outgoing call INVITE request \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_O_IM_CSI_INIT. It starts with 'DP Collected_Info', leading to a horizontal line with five options: Int_Release_Call, Int_Error, Int_Connect, Int_Continue_With_Argument, and Int_Continue. Int_Continue_With_Argument leads to a box 'Modify call parameters with received information', which then leads to Int_Continue. All five options lead to a decision diamond 'Default call handling = continue call?'. 'No' leads to 'Result:= Fail'. 'Yes' leads to 'Result:= Pass', which then leads to a circle with an X (exit).](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +``` +graph TD; A[DP Collected_Info] --> B[ ]; B --> C1[Int_Release_Call]; B --> C2[Int_Error]; B --> C3[Int_Connect]; B --> C4[Int_Continue_With_Argument]; B --> C5[Int_Continue]; C4 --> D[Modify call parameters with received information]; D --> C5; C1 --> E{Default call handling = continue call?}; C2 --> E; C3 --> E; C5 --> E; E -- No --> F[Result:= Fail]; E -- Yes --> G[Result:= Pass]; F --> G; G --> H((X)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT. It starts with 'DP Collected\_Info', leading to a horizontal line with five options: Int\_Release\_Call, Int\_Error, Int\_Connect, Int\_Continue\_With\_Argument, and Int\_Continue. Int\_Continue\_With\_Argument leads to a box 'Modify call parameters with received information', which then leads to Int\_Continue. All five options lead to a decision diamond 'Default call handling = continue call?'. 'No' leads to 'Result:= Fail'. 'Yes' leads to 'Result:= Pass', which then leads to a circle with an X (exit). + +Figure 4.14-2: Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT (sheet 2) + +### Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT + +3(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for an outgoing call INVITE request \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_O_IM_CSI_INIT. It starts with 'Internal' and 'DP_Collected_Info' leading to a parallel sequence of 'Tinvite expiry', 'Int_Connect_To_Resource', and 'CANCEL'. 'Tinvite expiry' leads to 'Result := INVITE Expires' and an exit. 'Int_Connect_To_Resource' leads to 'CAMEL_OCH_CTR' and a decision 'Result = Fail?'. 'CANCEL' leads to 'CAMEL_IMCN_MO_CANCEL' and 'Result := Abort'. If 'Result = Fail?' is 'No', it leads to 'DP_Collected_Info' and an exit. If 'Result = Fail?' is 'Yes', it leads to 'Result := Fail' and an exit. 'Result := Abort' also leads to an exit.](43979979715bb3304389a0cb18f34444_img.jpg) + +``` +graph TD; Internal[Internal] --- DP_Collected_Info1((DP_Collected_Info)); DP_Collected_Info1 --- Tinvite_expiry[/Tinvite expiry/]; DP_Collected_Info1 --- Int_Connect_To_Resource[/Int_Connect_To_Resource/]; DP_Collected_Info1 --- CANCEL[/CANCEL/]; Tinvite_expiry --- Result_Inv[Result := INVITE Expires]; Result_Inv --- Exit1(( )); Int_Connect_To_Resource --- CAMEL_OCH_CTR[CAMEL_OCH_CTR]; CAMEL_OCH_CTR --- Result_Fail{Result = Fail?}; Result_Fail -- No --> DP_Collected_Info2((DP_Collected_Info)); DP_Collected_Info2 --- Exit2(( )); Result_Fail -- Yes --> Result_Fail2[Result := Fail]; Result_Fail2 --- Exit3(( )); CANCEL --- CAMEL_IMCN_MO_CANCEL[CAMEL_IMCN_MO_CANCEL]; CAMEL_IMCN_MO_CANCEL --- Result_Abort[Result := Abort]; Result_Abort --- Exit3 +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT. It starts with 'Internal' and 'DP\_Collected\_Info' leading to a parallel sequence of 'Tinvite expiry', 'Int\_Connect\_To\_Resource', and 'CANCEL'. 'Tinvite expiry' leads to 'Result := INVITE Expires' and an exit. 'Int\_Connect\_To\_Resource' leads to 'CAMEL\_OCH\_CTR' and a decision 'Result = Fail?'. 'CANCEL' leads to 'CAMEL\_IMCN\_MO\_CANCEL' and 'Result := Abort'. If 'Result = Fail?' is 'No', it leads to 'DP\_Collected\_Info' and an exit. If 'Result = Fail?' is 'Yes', it leads to 'Result := Fail' and an exit. 'Result := Abort' also leads to an exit. + +Figure 4.14-3: Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT (sheet 3) + +![Flowchart for Procedure CAMEL_IMCN_MO_D_IM_CSI_INIT. The process starts with a connector, leading to a decision 'D-IM-CSI invocation?'. If 'No', it goes to 'Result := Pass' and ends. If 'Yes', it sets 'CAMEL_Invocation := True', stores original call parameters, invokes 'Int_Invoke_imcnSSF (D-IM-CSI)', and waits for 'imcnSSF_Invoked'. From there, it branches: 'Int_imcnSSF_Invoked' leads to 'Int_DP_Analysed_Info' and 'DP_Analysed_Info'; 'CANCEL' leads to 'CAMEL_IMCN MO_CANCEL', 'Result := Abort', and ends.](8269648391c59363ea61243864a2adf7_img.jpg) + +**Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT** 1(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a subscribed Dialled Service \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Decision{D-IM-CSI invocation?}; Decision -- No --> ResultPass[Result := Pass]; ResultPass --> EndPass(( )); Decision -- Yes --> SetTrue[CAMEL_Invocation := True]; SetTrue --> StoreParams[Store Original Call Parameters]; StoreParams --> InvokeSSF[Int_Invoke_imcnSSF (D-IM-CSI)]; InvokeSSF --> WaitSSF[Wait_for_imcnSSF_Invoked]; WaitSSF --> Branch1[Int_imcnSSF_Invoked]; WaitSSF --> Branch2[CANCEL]; Branch1 --> DPInfo[Int_DP_Analysed_Info]; DPInfo --> DPInfoObj[DP_Analysed_Info]; Branch2 --> IMCNCancel[CAMEL_IMCN MO_CANCEL]; IMCNCancel --> ResultAbort[Result := Abort]; ResultAbort --> EndAbort(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT. The process starts with a connector, leading to a decision 'D-IM-CSI invocation?'. If 'No', it goes to 'Result := Pass' and ends. If 'Yes', it sets 'CAMEL\_Invocation := True', stores original call parameters, invokes 'Int\_Invoke\_imcnSSF (D-IM-CSI)', and waits for 'imcnSSF\_Invoked'. From there, it branches: 'Int\_imcnSSF\_Invoked' leads to 'Int\_DP\_Analysed\_Info' and 'DP\_Analysed\_Info'; 'CANCEL' leads to 'CAMEL\_IMCN MO\_CANCEL', 'Result := Abort', and ends. + +Figure 4.15-1: Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT + +2(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a subscribed Dialled Service \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_D_IM_CSI_INIT. It starts with DP_Analysed_Info, leading to a decision 'Default call handling = continue call?'. If 'No', it goes to Int_Release_Call and Result:= Fail. If 'Yes', it goes to Int_Continue and Result:= Pass. Other paths include Int_Error, Int_Connect, and Int_Continue_With_Argument (which leads to 'Modify call parameters with received information' and then to the decision). All paths eventually lead to a common exit point.](24a89bcaba787f2bc1721356480a4a01_img.jpg) + +``` +graph TD; DP[DP_Analysed_Info] --> D{Default call handling = continue call?}; D -- No --> I1[Int_Release_Call]; I1 --> R1[Result:= Fail]; D -- Yes --> I5[Int_Continue]; I5 --> R2[Result:= Pass]; D --> I2[Int_Error]; D --> I3[Int_Connect]; D --> I4[Int_Continue_With_Argument]; I4 --> M[Modify call parameters with received information]; M --> D; R1 --> E(( )); R2 --> E; I2 --> E; I3 --> E; I4 --> E; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT. It starts with DP\_Analysed\_Info, leading to a decision 'Default call handling = continue call?'. If 'No', it goes to Int\_Release\_Call and Result:= Fail. If 'Yes', it goes to Int\_Continue and Result:= Pass. Other paths include Int\_Error, Int\_Connect, and Int\_Continue\_With\_Argument (which leads to 'Modify call parameters with received information' and then to the decision). All paths eventually lead to a common exit point. + +Figure 4.15-2: Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT (sheet 2) + +Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT + +3(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a subscribed Dialled Service \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_D_IM_CSI_INIT. It starts with 'Internal' and 'DP_Analysed_Info'. It branches into three paths: 'Tinvite expiry' leading to 'Result := INVITE Expires', 'Int_Connect_To_Resource' leading to 'CAMEL_OCH_CTR', and 'CANCEL' leading to 'CAMEL_IMCN_MO_CANCEL'. The 'CAMEL_OCH_CTR' path leads to a decision 'Result = Fail?'. If 'No', it leads to 'DP_Analysed_Info'. If 'Yes', it leads to 'Result := Fail'. Both 'Result := Fail' and 'Result := Abort' (from 'CAMEL_IMCN_MO_CANCEL') lead to a common exit point.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +``` +graph TD; Internal[Internal] --- DP_Analysed_Info_1((DP_Analysed_Info)); DP_Analysed_Info_1 --- Tinvite_expiry[/Tinvite expiry/]; DP_Analysed_Info_1 --- Int_Connect_To_Resource[/Int_Connect_To_Resource/]; DP_Analysed_Info_1 --- CANCEL[/CANCEL/]; Tinvite_expiry --- Result_Inv[Result := INVITE Expires]; Result_Inv --- Exit1(( )); Int_Connect_To_Resource --- CAMEL_OCH_CTR[CAMEL_OCH_CTR]; CAMEL_OCH_CTR --- Result_Fail_Dec{Result = Fail?}; Result_Fail_Dec -- No --> DP_Analysed_Info_2((DP_Analysed_Info)); Result_Fail_Dec -- Yes --> Result_Fail[Result := Fail]; CANCEL --- CAMEL_IMCN_MO_CANCEL[CAMEL_IMCN_MO_CANCEL]; CAMEL_IMCN_MO_CANCEL --- Result_Abort[Result := Abort]; Result_Fail --- Exit2(( )); Result_Abort --- Exit2 +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT. It starts with 'Internal' and 'DP\_Analysed\_Info'. It branches into three paths: 'Tinvite expiry' leading to 'Result := INVITE Expires', 'Int\_Connect\_To\_Resource' leading to 'CAMEL\_OCH\_CTR', and 'CANCEL' leading to 'CAMEL\_IMCN\_MO\_CANCEL'. The 'CAMEL\_OCH\_CTR' path leads to a decision 'Result = Fail?'. If 'No', it leads to 'DP\_Analysed\_Info'. If 'Yes', it leads to 'Result := Fail'. Both 'Result := Fail' and 'Result := Abort' (from 'CAMEL\_IMCN\_MO\_CANCEL') lead to a common exit point. + +Figure 4.15-3: Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT (sheet 3) + +# Procedure CAMEL\_IMCN\_MO\_CANCEL + +1(1) + +/\* Procedure in IM-SSF to perform CAMEL handling for an outgoing call CANCEL request. \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_CANCEL. It starts with a connector symbol, followed by a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a connector symbol. If 'Yes', it goes through 'Int_DP_O_Abandon', 'DP_O_Abandon', and 'Int_Continue' to a connector symbol.](a93de4c3f80bd4a972ab65510b09b68d_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{imcnSSF Invoked?}; Decision -- No --> End([ ]); Decision -- Yes --> Int_DP_O_Abandon[Int_DP_O_Abandon]; Int_DP_O_Abandon --> DP_O_Abandon[DP_O_Abandon]; DP_O_Abandon --> Int_Continue[Int_Continue]; Int_Continue --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_CANCEL. It starts with a connector symbol, followed by a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a connector symbol. If 'Yes', it goes through 'Int\_DP\_O\_Abandon', 'DP\_O\_Abandon', and 'Int\_Continue' to a connector symbol. + +Figure 4.16: Procedure CAMEL\_IMCN\_MO\_CANCEL (sheet 1) + +# Procedure CAMEL\_IMCN\_MO\_ANSWER + +1(2) + +/\* Procedure in the IM-SSF to handle an outgoing call Answer (200 OK) response from the terminating subscriber \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_ANSWER. It starts with a decision 'imcnSSF invoked?'. If 'No', it sets 'Result := Pass' and ends. If 'Yes', it sends 'Int_DP_O_Answer' and receives 'DP_O_Answer'. It then branches into 'Int_Continue', 'Int_Release_Call', or 'Int_Error'. 'Int_Continue' leads to 'Result := Pass'. 'Int_Release_Call' leads to a '606 Not Acceptable' decision. If 'No', it checks 'Default call handling = continue call?'. If 'Yes', it sends 'BYE' to the destination S-CSCF and sets 'Result := Fail'. If 'No', it leads to 'Int_Continue'. 'Int_Error' leads to 'Result := Pass'. All three paths ('Int_Continue', 'Result := Fail', 'Result := Pass') converge to an end connector.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +``` +graph TD; Start([ ]) --> Decision1{imcnSSF invoked?}; Decision1 -- No --> Result1[Result := Pass]; Result1 --> End1(( )); Decision1 -- Yes --> Int_DP_O_Answer[Int_DP_O_Answer]; Int_DP_O_Answer --> DP_O_Answer[DP_O_Answer]; DP_O_Answer --> Int_Continue[Int_Continue]; DP_O_Answer --> Int_Release_Call[Int_Release_Call]; DP_O_Answer --> Int_Error[Int_Error]; Int_Continue --> Result2[Result := Pass]; Int_Release_Call --> Decision2{606 Not Acceptable}; Decision2 -- No --> Decision3{Default call handling = continue call?}; Decision3 -- Yes --> BYE[BYE]; BYE --> ToDest[To the destination S-CSCF]; Decision3 -- No --> Int_Continue; Decision2 -- Yes --> Result3[Result := Fail]; Int_Error --> Result4[Result := Pass]; Result2 --> End2(( )); Result3 --> End2; Result4 --> End2; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_ANSWER. It starts with a decision 'imcnSSF invoked?'. If 'No', it sets 'Result := Pass' and ends. If 'Yes', it sends 'Int\_DP\_O\_Answer' and receives 'DP\_O\_Answer'. It then branches into 'Int\_Continue', 'Int\_Release\_Call', or 'Int\_Error'. 'Int\_Continue' leads to 'Result := Pass'. 'Int\_Release\_Call' leads to a '606 Not Acceptable' decision. If 'No', it checks 'Default call handling = continue call?'. If 'Yes', it sends 'BYE' to the destination S-CSCF and sets 'Result := Fail'. If 'No', it leads to 'Int\_Continue'. 'Int\_Error' leads to 'Result := Pass'. All three paths ('Int\_Continue', 'Result := Fail', 'Result := Pass') converge to an end connector. + +Figure 4.17-1: Procedure CAMEL\_IMCN\_MO\_ANSWER (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_ANSWER + +2(2) + +/\* Procedure in the IM-SSF to handle an outgoing call Answer (200 OK) response from the terminating subscriber \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_ANSWER. It starts with DP_O_Answer, branches into two BYE messages, then CAMEL_IMCN_MO_DISC1 and CAMEL_IMCN_MO_DISC2. A decision diamond 'Result = Reconnect?' follows. If 'No', Result := Fail. If 'Yes', Result := Reconnect. Both paths lead to a connector circle.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +``` +graph TD; DP_O_Answer([DP_O_Answer]) --> BYE1[/BYE/]; DP_O_Answer --> BYE2[/BYE/]; BYE2 --- Note[From the destination S-CSCF]; BYE1 --> DISC1[CAMEL_IMCN MO_DISC1]; BYE2 --> DISC2[CAMEL_IMCN MO_DISC2]; DISC1 --> Decision{Result = Reconnect?}; DISC2 --> Decision; Decision -- No --> Fail[Result := Fail]; Decision -- Yes --> Reconnect[Result := Reconnect]; Fail --> Connector(( )); Reconnect --> Connector +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_ANSWER. It starts with DP\_O\_Answer, branches into two BYE messages, then CAMEL\_IMCN\_MO\_DISC1 and CAMEL\_IMCN\_MO\_DISC2. A decision diamond 'Result = Reconnect?' follows. If 'No', Result := Fail. If 'Yes', Result := Reconnect. Both paths lead to a connector circle. + +Figure 4.17-2: Procedure CAMEL\_IMCN\_MO\_ANSWER (sheet 2) + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts with a connector symbol leading to an 'Event ?' decision diamond. From the diamond, four paths lead to numbered circles 1, 2, 3, and 4. Path 1 is labeled with error codes: 4xx except 401, 407, 408, 413, 420, 480, 486; or 5xx; or 6xx except 600, 603. Path 2 is labeled 486 and 600. Path 3 is labeled 480, 408, 603. Path 4 is labeled 'Timer expiry'.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL 1(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Event{Event ?}; Event -- "4xx except 401, 407, 408, 413, 420, 480, 486; or 5xx; or 6xx except 600, 603." --> 1((1)); Event -- "486 600" --> 2((2)); Event -- "480 408 603" --> 3((3)); Event -- "Timer expiry" --> 4((4)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts with a connector symbol leading to an 'Event ?' decision diamond. From the diamond, four paths lead to numbered circles 1, 2, 3, and 4. Path 1 is labeled with error codes: 4xx except 401, 407, 408, 413, 420, 480, 486; or 5xx; or 6xx except 600, 603. Path 2 is labeled 486 and 600. Path 3 is labeled 480, 408, 603. Path 4 is labeled 'Timer expiry'. + +Figure 4.18-1: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL + +2(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts with a connector '1', followed by a decision 'imcnSSF invoked?'. If 'Yes', it goes through 'Int_DP_Route_Select_Failure' (input) and 'DP_Route_Select_Failure' (output). If 'No', it bypasses these. The flow then splits into four parallel paths: 'Int_Connect', 'Int_Continue', 'Int_Release_Call', and 'Int_Error'. 'Int_Connect' leads to 'Modify call parameters with received information' and 'Result := Reconnect'. 'Int_Continue', 'Int_Release_Call', and 'Int_Error' merge at a junction. 'Int_Error' also leads to a box 'Same SIP 4XX, 5XX, or 6XX response received'. The merged path leads to an unlabeled parallelogram, then 'Wait_For_ACK_For_Error', 'ACK', and 'Result := Continue'. Both 'Result := Reconnect' and 'Result := Continue' lead to a final connector symbol.](fd76efce549d3713543bb5ed9b023c2e_img.jpg) + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts with a connector '1', followed by a decision 'imcnSSF invoked?'. If 'Yes', it goes through 'Int\_DP\_Route\_Select\_Failure' (input) and 'DP\_Route\_Select\_Failure' (output). If 'No', it bypasses these. The flow then splits into four parallel paths: 'Int\_Connect', 'Int\_Continue', 'Int\_Release\_Call', and 'Int\_Error'. 'Int\_Connect' leads to 'Modify call parameters with received information' and 'Result := Reconnect'. 'Int\_Continue', 'Int\_Release\_Call', and 'Int\_Error' merge at a junction. 'Int\_Error' also leads to a box 'Same SIP 4XX, 5XX, or 6XX response received'. The merged path leads to an unlabeled parallelogram, then 'Wait\_For\_ACK\_For\_Error', 'ACK', and 'Result := Continue'. Both 'Result := Reconnect' and 'Result := Continue' lead to a final connector symbol. + +Figure 4.18-2: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 2) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL + +3(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts at connector '2', checks if 'imcnSSF invoked?'. If 'No', it goes to the right and down to the exit. If 'Yes', it goes to 'Int_DP_O_Busy' and then 'DP_O_Busy'. From 'DP_O_Busy', it branches into four options: 'Int_Connect', 'Int_Continue', 'Int_Error', and 'Int_Release_Call'. 'Int_Connect' leads to 'Modify call parameters with received information' and then 'Result := Reconnect'. 'Int_Continue', 'Int_Error', and 'Int_Release_Call' all lead to a junction point. From this junction, 'Int_Continue' and 'Int_Release_Call' lead to the exit. 'Int_Error' leads to a decision diamond (empty box) which has a note 'Same SIP 4XX, or 6XX response received'. This leads to 'Wait_For_ACK_For_Error', then 'ACK', then 'Result := Continue', which then leads to the exit.](396197257cf9437b526bb6585b6a9c8a_img.jpg) + +``` +graph TD; Start((2)) --> Decision{imcnSSF invoked?}; Decision -- No --> Exit(( )); Decision -- Yes --> Int_DP_O_Busy{{Int_DP_O_Busy}}; Int_DP_O_Busy --> DP_O_Busy{{DP_O_Busy}}; DP_O_Busy --> Int_Connect[/Int_Connect/]; DP_O_Busy --> Int_Continue[/Int_Continue/]; DP_O_Busy --> Int_Error[/Int_Error/]; DP_O_Busy --> Int_Release_Call[/Int_Release_Call/]; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> Junction(( )); Int_Error --> Junction; Int_Release_Call --> Junction; Junction -- Int_Continue --> Exit; Junction -- Int_Release_Call --> Exit; Junction -- Int_Error --> Decision2{ }; Decision2 -- "Same SIP 4XX, or 6XX response received" --> Wait_For_ACK[Wait_For_ACK_For_Error]; Wait_For_ACK --> ACK[/ACK/]; ACK --> Result_Continue[Result := Continue]; Result_Continue --> Exit; Result_Reconnect --> Exit; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts at connector '2', checks if 'imcnSSF invoked?'. If 'No', it goes to the right and down to the exit. If 'Yes', it goes to 'Int\_DP\_O\_Busy' and then 'DP\_O\_Busy'. From 'DP\_O\_Busy', it branches into four options: 'Int\_Connect', 'Int\_Continue', 'Int\_Error', and 'Int\_Release\_Call'. 'Int\_Connect' leads to 'Modify call parameters with received information' and then 'Result := Reconnect'. 'Int\_Continue', 'Int\_Error', and 'Int\_Release\_Call' all lead to a junction point. From this junction, 'Int\_Continue' and 'Int\_Release\_Call' lead to the exit. 'Int\_Error' leads to a decision diamond (empty box) which has a note 'Same SIP 4XX, or 6XX response received'. This leads to 'Wait\_For\_ACK\_For\_Error', then 'ACK', then 'Result := Continue', which then leads to the exit. + +Figure 4.18-3: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 3) + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts at connector 3, checks if imcnSSF is invoked. If No, it goes to Int_Release_Call. If Yes, it sends Int_DP_O_No_Answer, then DP_O_No_Answer. It then branches into Int_Connect, Int_Continue, Int_Error, and Int_Release_Call. Int_Continue leads to Int_O_Exception. Int_Error leads to a merge point. Int_Release_Call leads to 'Same SIP 4XX response received' and then to the merge point. Int_Connect leads to 'Modify call parameters with received information', then 'Result := Reconnect', which then leads to the exit connector. The merge point leads to Wait_For_ACK_For_Error, then ACK, then Result := Continue, which leads to the exit connector.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL 4(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; 3((3)) --> imcnSSF{imcnSSF invoked?}; imcnSSF -- No --> Int_Release_Call[/Int_Release_Call/]; imcnSSF -- Yes --> Int_DP_O_No_Answer[/Int_DP_O_No_Answer/]; Int_DP_O_No_Answer --> DP_O_No_Answer([DP_O_No_Answer]); DP_O_No_Answer --> Int_Connect[/Int_Connect/]; DP_O_No_Answer --> Int_Continue[/Int_Continue/]; DP_O_No_Answer --> Int_Error[/Int_Error/]; DP_O_No_Answer --> Int_Release_Call; Int_Continue --> Int_O_Exception[/Int_O_Exception/]; Int_O_Exception --> Merge{ }; Int_Error --> Merge; Int_Release_Call --> SameSIP[Same SIP 4XX response received]; SameSIP --> Merge; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> ResultReconnect[Result := Reconnect]; ResultReconnect --> Exit((X)); Merge --> WaitForACK[Wait_For_ACK_For_Error]; WaitForACK --> ACK[/ACK/]; ACK --> ResultContinue[Result := Continue]; ResultContinue --> Exit; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts at connector 3, checks if imcnSSF is invoked. If No, it goes to Int\_Release\_Call. If Yes, it sends Int\_DP\_O\_No\_Answer, then DP\_O\_No\_Answer. It then branches into Int\_Connect, Int\_Continue, Int\_Error, and Int\_Release\_Call. Int\_Continue leads to Int\_O\_Exception. Int\_Error leads to a merge point. Int\_Release\_Call leads to 'Same SIP 4XX response received' and then to the merge point. Int\_Connect leads to 'Modify call parameters with received information', then 'Result := Reconnect', which then leads to the exit connector. The merge point leads to Wait\_For\_ACK\_For\_Error, then ACK, then Result := Continue, which leads to the exit connector. + +Figure 4.18-4: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 4) + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts at connector 4, checks if imcnSSF is invoked. If No, it goes to Int_Release_Call. If Yes, it sends Int_DP_O_No_Answer, then DP_O_No_Answer. From DP_O_No_Answer, it branches to Int_Connect, Int_Continue, Int_Error, or Int_Release_Call. Int_Connect leads to Modify call parameters and Result := Reconnect. Int_Continue leads to Int_O_Exception. Int_Error and Int_Release_Call both lead to 487 Request Terminated. From 487 Request Terminated, it goes to Wait_For_ACK_For_Error, then ACK, then Result := Continue. All three results (Reconnect, Continue, and the path from Int_O_Exception) lead to the end connector.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL 5(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; 4((4)) --> imcnSSF{imcnSSF invoked?}; imcnSSF -- No --> Int_Release_Call[/Int_Release_Call/]; imcnSSF -- Yes --> Int_DP_O_No_Answer[/Int_DP_O_No_Answer/]; Int_DP_O_No_Answer --> DP_O_No_Answer([DP_O_No_Answer]); DP_O_No_Answer --> Int_Connect[/Int_Connect/]; DP_O_No_Answer --> Int_Continue[/Int_Continue/]; DP_O_No_Answer --> Int_Error[/Int_Error/]; DP_O_No_Answer --> Int_Release_Call; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> Int_O_Exception[/Int_O_Exception/]; Int_Error --> 487{487 Request Terminated}; Int_Release_Call --> 487; Int_O_Exception --> 487; 487 --> Wait_For_ACK[Wait_For_ACK_For_Error]; Wait_For_ACK --> ACK[/ACK/]; ACK --> Result_Continue[Result := Continue]; Result_Reconnect --> End((X)); Result_Continue --> End; Int_O_Exception --> End +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts at connector 4, checks if imcnSSF is invoked. If No, it goes to Int\_Release\_Call. If Yes, it sends Int\_DP\_O\_No\_Answer, then DP\_O\_No\_Answer. From DP\_O\_No\_Answer, it branches to Int\_Connect, Int\_Continue, Int\_Error, or Int\_Release\_Call. Int\_Connect leads to Modify call parameters and Result := Reconnect. Int\_Continue leads to Int\_O\_Exception. Int\_Error and Int\_Release\_Call both lead to 487 Request Terminated. From 487 Request Terminated, it goes to Wait\_For\_ACK\_For\_Error, then ACK, then Result := Continue. All three results (Reconnect, Continue, and the path from Int\_O\_Exception) lead to the end connector. + +Figure 4.18-5: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 5) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL + +6(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts with a merge point receiving DP_O_Busy, DP_O_No_Answer, and DP_Route_Select_Failure. It branches into CANCEL and Int_Connect_To_Resource. CANCEL leads to CAMEL_IMCN_MO_CANCEL, which leads to a 'Result ?' decision. If 'Fail', it goes to 487 Request Terminated, then 200 OK, then Result := Fail, and finally an exit circle. If 'Pass', it goes to CAMEL_OCH_CTR, then to the 'Result ?' decision. If 'Pass' from CAMEL_OCH_CTR, it goes to an exit circle with a dash.](db5deafdae53dbc7d5972957f708c691_img.jpg) + +``` +graph TD; Start([ ]) --> DP["DP_O_Busy
DP_O_No_Answer
DP_Route_Select_Failure"]; DP --> CANCEL[/CANCEL/]; DP --> Int_Connect_To_Resource[/Int_Connect_To_Resource/]; CANCEL --> CAMEL_IMCN_MO_CANCEL[CAMEL_IMCN_MO_CANCEL]; Int_Connect_To_Resource --> CAMEL_OCH_CTR[CAMEL_OCH_CTR]; CAMEL_IMCN_MO_CANCEL --> Result{Result ?}; CAMEL_OCH_CTR --> Result; Result -- Fail --> 487{487 Request Terminated}; 487 --> 200{200 OK}; 200 --> Result_Fail[Result := Fail]; Result_Fail --> Exit(( )); Result -- Pass --> Exit2([ - ]); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts with a merge point receiving DP\_O\_Busy, DP\_O\_No\_Answer, and DP\_Route\_Select\_Failure. It branches into CANCEL and Int\_Connect\_To\_Resource. CANCEL leads to CAMEL\_IMCN\_MO\_CANCEL, which leads to a 'Result ?' decision. If 'Fail', it goes to 487 Request Terminated, then 200 OK, then Result := Fail, and finally an exit circle. If 'Pass', it goes to CAMEL\_OCH\_CTR, then to the 'Result ?' decision. If 'Pass' from CAMEL\_OCH\_CTR, it goes to an exit circle with a dash. + +Figure 4.18-6: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 6) + +# Procedure CAMEL\_IMCN\_MO\_DISC1 + +1(1) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from caller\*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_DISC1. It starts with a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue'. If 'Yes', it sends 'Int_DP_O_Disconnect' (legId=1) to 'DP_O_Disconnect_1'. From there, it branches into 'Int_Error', 'Int_Release_Call', 'Int_Continue', and 'BYE' (from destination S-CSCF). 'Int_Error', 'Int_Release_Call', and 'Int_Continue' lead to a 'BYE' message to the destination S-CSCF, which then leads to '200 OK'. 'BYE' (from destination S-CSCF) leads to 'Int_DP_O_Disconnect' (legId=2) to 'DP_O_Disconnect_2'. From 'DP_O_Disconnect_2', it branches into 'Int_Continue', 'Int_Error', and 'Int_ReleaseCall', which all lead to a '200 OK' message to the destination S-CSCF. Both '200 OK' messages lead to 'Result := Continue'.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{imcnSSF invoked?}; Decision -- No --> Continue1[Result := Continue]; Decision -- Yes --> Int_DP_O_Disconnect_1[Int_DP_O_Disconnect
/* legId = 1 */]; Int_DP_O_Disconnect_1 --> DP_O_Disconnect_1((DP_O_Disconnect_1)); DP_O_Disconnect_1 --> Int_Error1[Int_Error]; DP_O_Disconnect_1 --> Int_Release_Call1[Int_Release_Call]; DP_O_Disconnect_1 --> Int_Continue1[Int_Continue]; DP_O_Disconnect_1 --> BYE1[BYE]; BYE1 --> BYE1_note[From the destination S-CSCF]; Int_Error1 --> BYE2[BYE]; Int_Release_Call1 --> BYE2; Int_Continue1 --> BYE2; BYE2 --> BYE2_note[To the destination S-CSCF]; BYE2 --> OK1{200 OK}; OK1 --> Continue2[Result := Continue]; BYE1 --> Int_DP_O_Disconnect_2[Int_DP_O_Disconnect
/* legId = 2 */]; Int_DP_O_Disconnect_2 --> DP_O_Disconnect_2((DP_O_Disconnect_2)); DP_O_Disconnect_2 --> Int_Continue2[Int_Continue]; DP_O_Disconnect_2 --> Int_Error2[Int_Error]; DP_O_Disconnect_2 --> Int_ReleaseCall[Int_ReleaseCall]; Int_Continue2 --> OK2{200 OK}; Int_Error2 --> OK2; Int_ReleaseCall --> OK2; OK2 --> OK2_note[To the destination S-CSCF]; OK2 --> Continue2; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_DISC1. It starts with a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue'. If 'Yes', it sends 'Int\_DP\_O\_Disconnect' (legId=1) to 'DP\_O\_Disconnect\_1'. From there, it branches into 'Int\_Error', 'Int\_Release\_Call', 'Int\_Continue', and 'BYE' (from destination S-CSCF). 'Int\_Error', 'Int\_Release\_Call', and 'Int\_Continue' lead to a 'BYE' message to the destination S-CSCF, which then leads to '200 OK'. 'BYE' (from destination S-CSCF) leads to 'Int\_DP\_O\_Disconnect' (legId=2) to 'DP\_O\_Disconnect\_2'. From 'DP\_O\_Disconnect\_2', it branches into 'Int\_Continue', 'Int\_Error', and 'Int\_ReleaseCall', which all lead to a '200 OK' message to the destination S-CSCF. Both '200 OK' messages lead to 'Result := Continue'. + +Figure 4.19: Procedure CAMEL\_IMCN\_MO\_DISC1 (sheet 1) + +![Flowchart for Procedure CAMEL_IMCN_MO_DISC2. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and then to a connector. If 'Yes', it goes to 'Int_DP_O_Disconnect' (legId = 2), then to 'DP_O_Disconnect_2'. From there, it branches into five paths: 1) 'BYE' -> 'Int_DP_O_Disconnect' (legId = 1) -> 'DP_O_Disconnect_1' -> a merge of 'Int_Error', 'Int_Continue', and 'Int_Release_Call' -> '200 OK'. 2) 'Int_Continue' -> a merge. 3) 'Int_Release_Call' -> a merge. 4) 'Int_Error' -> a merge. 5) 'Int_Connect' -> 'Modify call parameters with received information' -> 'Final Response Received := False' -> 'Result := Reconnect'. All five paths merge at a 'Result := Continue' block, which then leads to '200 OK' -> 'To the destination S-CSCF' -> a connector.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_DISC2 1(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee\*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start(( )) --> Decision{imcnSSF invoked?}; Decision -- No --> Result1[Result := Continue]; Result1 --> Connector1(( )); Decision -- Yes --> Int_DP_O_Disconnect2[Int_DP_O_Disconnect +/* legId = 2 */]; Int_DP_O_Disconnect2 --> DP_O_Disconnect2[DP_O_Disconnect_2]; DP_O_Disconnect2 --> BYE1[BYE]; DP_O_Disconnect2 --> Int_Continue1[Int_Continue]; DP_O_Disconnect2 --> Int_Release_Call1[Int_Release_Call]; DP_O_Disconnect2 --> Int_Error1[Int_Error]; DP_O_Disconnect2 --> Int_Connect1[Int_Connect]; BYE1 --> Int_DP_O_Disconnect1[Int_DP_O_Disconnect +/* legId = 1 */]; Int_DP_O_Disconnect1 --> DP_O_Disconnect1[DP_O_Disconnect_1]; DP_O_Disconnect1 --> Int_Error2[Int_Error]; DP_O_Disconnect1 --> Int_Continue2[Int_Continue]; DP_O_Disconnect1 --> Int_Release_Call2[Int_Release_Call]; Int_Error2 --> Merge1(( )); Int_Continue2 --> Merge1; Int_Release_Call2 --> Merge1; Merge1 --> OK1[200 OK]; Int_Continue1 --> Merge2(( )); Int_Release_Call1 --> Merge2; Int_Error1 --> Merge2; Int_Connect1 --> Modify[Modify call parameters with received information]; Modify --> Final[Final Response Received := False]; Final --> Result2[Result := Reconnect]; OK1 --> Merge3(( )); Int_Continue1 --> Merge3; Int_Release_Call1 --> Merge3; Int_Error1 --> Merge3; Int_Connect1 --> Merge3; Merge3 --> Result3[Result := Continue]; Result3 --> OK2[200 OK]; OK2 --> ToS-CSCF[To the destination S-CSCF]; ToS-CSCF --> Connector2(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_DISC2. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and then to a connector. If 'Yes', it goes to 'Int\_DP\_O\_Disconnect' (legId = 2), then to 'DP\_O\_Disconnect\_2'. From there, it branches into five paths: 1) 'BYE' -> 'Int\_DP\_O\_Disconnect' (legId = 1) -> 'DP\_O\_Disconnect\_1' -> a merge of 'Int\_Error', 'Int\_Continue', and 'Int\_Release\_Call' -> '200 OK'. 2) 'Int\_Continue' -> a merge. 3) 'Int\_Release\_Call' -> a merge. 4) 'Int\_Error' -> a merge. 5) 'Int\_Connect' -> 'Modify call parameters with received information' -> 'Final Response Received := False' -> 'Result := Reconnect'. All five paths merge at a 'Result := Continue' block, which then leads to '200 OK' -> 'To the destination S-CSCF' -> a connector. + +Figure 4.20-1: Procedure CAMEL\_IMCN\_MO\_DISC2 (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_DISC2 + +2(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee\*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_DISC2. The flow starts with DP_O_Disconnect_2, followed by Int_Connect_To_Resource, then CAMEL_OCH_CTR. A decision diamond 'Result = Fail?' follows. If 'No', it goes to DP_O_Disconnect_2. If 'Yes', it goes to Result := Continue, which then leads to a connector symbol.](d7948c38a18636aefecdd95388196460_img.jpg) + +``` +graph TD; A[DP_O_Disconnect_2] --> B[/Int_Connect_To_Resource/]; B --> C[CAMEL_OCH_CTR]; C --> D{Result = Fail?}; D -- No --> E[DP_O_Disconnect_2]; D -- Yes --> F[Result := Continue]; F --> G((X)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_DISC2. The flow starts with DP\_O\_Disconnect\_2, followed by Int\_Connect\_To\_Resource, then CAMEL\_OCH\_CTR. A decision diamond 'Result = Fail?' follows. If 'No', it goes to DP\_O\_Disconnect\_2. If 'Yes', it goes to Result := Continue, which then leads to a connector symbol. + +Figure 4.20-2: Procedure CAMEL\_IMCN\_MO\_DISC2 (sheet 2) + +# Procedure CAMEL\_OCH\_CTR + +1(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +![Flowchart for Procedure CAMEL_OCH_CTR. It starts with a wait for PlayAnnc or Prompt_And_Collect request, then branches based on CAP_Play_Announcement, CAP_Prompt_And_Collect_User_Information, or Int_Disconnect_Forward_Connection. It handles 200 OK, Error response, BYE, and CANCEL signals from the MRFC, leading to states like Int_SRF_Connected, Int_CTR_Failed, or Await_SRF_Disconnection_Fail.](10b0dda884baae493ad958422d11b552_img.jpg) + +``` + +graph TD + Start([Start]) --> Wait1[Wait for PlayAnnc or Prompt_And_Collect request] + Wait1 --> CAP1[CAP_Play_Announcement] + Wait1 --> CAP2[CAP_Prompt_And_Collect_User_Information] + Wait1 --> Int1[Int_Disconnect_Forward_Connection] + CAP1 --> INVITE1[INVITE] + INVITE1 --> ToMRFC1[To MRFC] + CAP2 --> INVITE2[INVITE] + INVITE2 --> ToMRFC2[To MRFC] + Int1 --> Result1[Result:= pass] + ToMRFC1 --> Wait2[Wait for 200 OK] + ToMRFC2 --> Wait2 + Result1 --> Exit1(( )) + Wait2 --> OK1[200 OK] + OK1 --> FromMRFC1[From MRFC] + OK1 --> OK2[200 OK] + OK2 --> FromMRFC2[From MRFC] + OK2 --> ACK[ACK] + ACK --> ToMRFC3[To MRFC] + ToMRFC3 --> Int_SRF_Connected[Int_SRF_Connected] + Int_SRF_Connected --> Relay[Relay] + Wait2 --> Error[Error response] + Error --> Int_CTR_Failed[Int_CTR_Failed] + Int_CTR_Failed --> Result2[Result:= pass] + Result2 --> Exit2(( )) + Result2 --> ToMRFC4[To MRFC] + Wait2 --> BYE[BYE] + BYE --> OK3[200 OK] + OK3 --> Int_DP_O_Disconnect[Int_DP_O_Disconnect /* legID */] + Int_DP_O_Disconnect --> BYE2[BYE] + BYE2 --> Await_SRF_Active[Await_SRF_Disconnection_Active] + Await_SRF_Active --> ToMRFC5[To MRFC] + Wait2 --> CANCEL[CANCEL] + CANCEL --> OK4[200 OK] + OK4 --> ReqTerminated[487 Request Terminated] + ReqTerminated --> Int_DP_O_Abandon[Int_DP_O_Abandon /* legID */] + Int_DP_O_Abandon --> DP_O_Abandon_DFC[DP_O_Abandon_DFC] + DP_O_Abandon_DFC --> Int_Continue[Int_Continue] + Int_Continue --> CANCEL2[CANCEL] + CANCEL2 --> ToMRFC6[To MRFC] + ToMRFC6 --> Await_SRF_Fail[Await_SRF_Disconnection_Fail] + +``` + +Flowchart for Procedure CAMEL\_OCH\_CTR. It starts with a wait for PlayAnnc or Prompt\_And\_Collect request, then branches based on CAP\_Play\_Announcement, CAP\_Prompt\_And\_Collect\_User\_Information, or Int\_Disconnect\_Forward\_Connection. It handles 200 OK, Error response, BYE, and CANCEL signals from the MRFC, leading to states like Int\_SRF\_Connected, Int\_CTR\_Failed, or Await\_SRF\_Disconnection\_Fail. + +Figure 4.21-1: Procedure CAMEL\_OCH\_CTR (sheet 1) + +![SDL Diagram for Procedure CAMEL_OCH_CTR (sheet 2)](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +### Procedure CAMEL\_OCH\_CTR 2(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. + Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` + + graph TD + Relay([Relay]) --> BYE_In[/BYE/] + BYE_In -.-> FromMRFC[From MRFC] + BYE_In --> OK_Out[200 OK] + OK_Out -.-> ToMRFC[To MRFC] + OK_Out --> Int_SRF_Rel[Int_SRF_Released] + Int_SRF_Rel --> Res_Pass[Result:= pass] + Res_Pass --> End1((X)) + + Relay --> Int_Disc[Int_Disconnect_Forward_Connection] + Int_Disc --> BYE_Out[BYE] + BYE_Out -.-> ToMRFC2[To MRFC] + BYE_Out --> Await_SRF([Await_SRF_Disconnection_Continue]) + + Await_SRF --> BYE_In2[/BYE/] + BYE_In2 --> OK_Out2[200 OK] + OK_Out2 --> Int_DP_Disc[Int_DP_O_Disconnect +/* legID */] + Int_DP_Disc --> Res_Pass2[Result:= pass] + Res_Pass2 --> End2((X)) + + Await_SRF --> CANCEL_In[/CANCEL/] + CANCEL_In --> OK_Out3[200 OK] + OK_Out3 --> Int_DP_Aban[Int_DP_O_Abandon +/* legID */] + Int_DP_Aban --> DP_Fail[DP_O_Abandon_Fail] + DP_Fail --> Int_Cont[Int_continue] + Int_Cont --> Res_Fail[Result:= fail] + Res_Fail --> End3((X)) + + Await_SRF --> OK_In2[/200 OK/] + OK_In2 -.-> FromMRFC2[From MRFC] + OK_In2 --> Int_SRF_Rel2[Int_SRF_Released] + Int_SRF_Rel2 --> Res_Pass3[Result:= pass] + Res_Pass3 --> End4((X)) + +``` + +SDL Diagram for Procedure CAMEL\_OCH\_CTR (sheet 2) + +**Figure 4.21-2: Procedure CAMEL\_OCH\_CTR (sheet 2)** + +![Sequence diagram for Procedure CAMEL_OCH_CTR. The process starts with a relay and wait for PlayAnnc or Prompt_And_Collect_request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int_DP_O_Disconnect, then Wait_For_Disconnect_Forward_Connection. The CANCEL path leads to 200 OK, then Int_DP_O_Abandon, then DP_O_Abandon_DFC, then Int_Continue, then Wait_For_Disconnect_Forward_Connection. The ACK path leads to a terminal state.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +### Procedure CAMEL\_OCH\_CTR + +3(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` +sequenceDiagram + participant MS + participant IM-SSF + Note right of IM-SSF: Relay, Wait for PlayAnnc or Prompt_And_Collect_request + IM-SSF->>MS: BYE + MS-->>IM-SSF: 200 OK + IM-SSF->>MS: Int_DP_O_Disconnect /* legID */ + MS-->>IM-SSF: Wait_For_Disconnect_Forward_Connection + IM-SSF->>MS: CANCEL + MS-->>IM-SSF: 200 OK + IM-SSF->>MS: Int_DP_O_Abandon /* legID */ + MS-->>IM-SSF: DP_O_Abandon_DFC + IM-SSF->>MS: Int_Continue + MS-->>IM-SSF: Wait_For_Disconnect_Forward_Connection + IM-SSF->>MS: ACK + MS-->>IM-SSF: - +``` + +Sequence diagram for Procedure CAMEL\_OCH\_CTR. The process starts with a relay and wait for PlayAnnc or Prompt\_And\_Collect\_request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int\_DP\_O\_Disconnect, then Wait\_For\_Disconnect\_Forward\_Connection. The CANCEL path leads to 200 OK, then Int\_DP\_O\_Abandon, then DP\_O\_Abandon\_DFC, then Int\_Continue, then Wait\_For\_Disconnect\_Forward\_Connection. The ACK path leads to a terminal state. + +Figure 4.21-3: Procedure CAMEL\_OCH\_CTR (sheet 3) + +# Procedure CAMEL\_OCH\_CTR + +4(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +![Flowchart for Procedure CAMEL_OCH_CTR. The process starts with 'Wait_For_Disconnect_Forward_Connection', followed by 'Int_Disconnect_Forward_Connection', then a 'BYE' signal 'To MRFC'. A decision 'Answer Received?' follows. If 'True', it goes to 'Await_SRF_Disconnection_Active', then '200 OK From MRFC', then 'Result:= pass', ending at a circle with an X. If 'False', it goes to 'Await_SRF_Disconnection_Fail', then '200 OK From MRFC', then 'Result:= fail', ending at a circle with an X.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +``` +graph TD; A[Wait_For_Disconnect_Forward_Connection] --> B[Int_Disconnect_Forward_Connection]; B --> C[BYE]; C --> D[To MRFC]; C --> E{Answer Received?}; E -- True --> F[Await_SRF_Disconnection_Active]; E -- False --> G[Await_SRF_Disconnection_Fail]; F --> H[200 OK]; H --> I[From MRFC]; H --> J[Result:= pass]; J --> K((X)); G --> L[200 OK]; L --> M[From MRFC]; L --> N[Result:= fail]; N --> O((X)); +``` + +Flowchart for Procedure CAMEL\_OCH\_CTR. The process starts with 'Wait\_For\_Disconnect\_Forward\_Connection', followed by 'Int\_Disconnect\_Forward\_Connection', then a 'BYE' signal 'To MRFC'. A decision 'Answer Received?' follows. If 'True', it goes to 'Await\_SRF\_Disconnection\_Active', then '200 OK From MRFC', then 'Result:= pass', ending at a circle with an X. If 'False', it goes to 'Await\_SRF\_Disconnection\_Fail', then '200 OK From MRFC', then 'Result:= fail', ending at a circle with an X. + +Figure 4.21-4: Procedure CAMEL\_OCH\_CTR (sheet 4) + +![Sequence diagram for Procedure CAMEL_OCH_CTR. The diagram shows four parallel lifelines starting from a top 'Relay' node. From left to right: 1. A chevron '(Notification of PlayAnnc Completed)' followed by a box 'CAP_Specialised ResourceReport'. 2. A chevron '(Return of Prompt & Collect Result)' followed by a box 'CAP_Prompt And_Collect User_Information ack'. 3. A box 'CAP_Play_Announcement' followed by a chevron '(Play_Announcement)'. 4. A box 'CAP_Prompt_ And_Collect_ User_Information' followed by a chevron '(Prompt_ And_Collect_ User_Information)'. All four paths converge to a single bottom 'Relay' node.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +### Procedure CAMEL\_OCH\_CTR + +5(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MRFC. +Signals to/from the right are to/from the imcnSSF. + +``` +sequenceDiagram + participant TopRelay as Relay + participant MRFC + participant IMCNSSF + Note right of MRFC: Signals to/from the left are to/from the MRFC. + Note right of IMCNSSF: Signals to/from the right are to/from the imcnSSF. + + TopRelay->>MRFC: (Notification of PlayAnnc Completed) + MRFC-->>IMCNSSF: CAP_Specialised ResourceReport + TopRelay->>MRFC: (Return of Prompt & Collect Result) + MRFC-->>IMCNSSF: CAP_Prompt And_Collect User_Information ack + TopRelay->>IMCNSSF: CAP_Play_Announcement + IMCNSSF-->>MRFC: (Play_Announcement) + TopRelay->>IMCNSSF: CAP_Prompt_ And_Collect_ User_Information + IMCNSSF-->>MRFC: (Prompt_ And_Collect_ User_Information) + + MRFC->>BottomRelay as + IMCNSSF->>BottomRelay as + BottomRelay +``` + +Sequence diagram for Procedure CAMEL\_OCH\_CTR. The diagram shows four parallel lifelines starting from a top 'Relay' node. From left to right: 1. A chevron '(Notification of PlayAnnc Completed)' followed by a box 'CAP\_Specialised ResourceReport'. 2. A chevron '(Return of Prompt & Collect Result)' followed by a box 'CAP\_Prompt And\_Collect User\_Information ack'. 3. A box 'CAP\_Play\_Announcement' followed by a chevron '(Play\_Announcement)'. 4. A box 'CAP\_Prompt\_ And\_Collect\_ User\_Information' followed by a chevron '(Prompt\_ And\_Collect\_ User\_Information)'. All four paths converge to a single bottom 'Relay' node. + +Figure 4.21-5: Procedure CAMEL\_OCH\_CTR (sheet 5) + +#### 4.6.1.4 Handling of Mobile Terminated IP Multimedia sessions in the IM-SSF + +The functional behaviour of the S-CSCF for handling terminating calls is specified in 3GPP TS 23.218[5]. The process and the procedures specific to CAMEL are specified in this subclause: + +- Process MT\_IM\_SSF; +- Procedure Check\_Registration; +- Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT; +- Procedure CAMEL\_IMCN\_MT\_RECONNECT; +- Procedure CAMEL\_IMCN\_MT\_CANCEL; +- Procedure CAMEL\_IMCN\_MT\_ANSWER; +- Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL; +- Procedure CAMEL\_IMCN\_MT\_DISC1; +- Procedure CAMEL\_IMCN\_MT\_DISC2; +- Procedure CAMEL\_CAMEL\_MT\_CTR. + +Internal interface indicated with the "Int\_SRF\_" prefix within this subclause indicates internal interface with the MRFC. + +##### 4.6.1.4.1 Actions of the IM-SSF on receipt of Int\_Error + +The IM-SSF checks the default Call Handling parameter in the relevant CSI. + +If the default call handling is release, a BYE indication is sent to the originating CSCF. The IM-SSF then releases all resources and the invoked CAMEL procedure ends. + +If the call handling is continue, the IM-SSF continues processing without CAMEL support. + +##### 4.6.1.4.2 Actions of the IM-SSF on receipt of Int\_Release\_Call + +The IM-SSF BYE message is sent to the originating CSCF and resources are released. + +##### 4.6.1.4.3 Actions of the IM-SSF on receipt of Int\_Continue\_With\_Argument + +The IM-SSF shall replace the call parameters by the information received in the Int\_Continue\_With\_Argument message. Call parameters that are not included in the Int\_Continue\_With\_Argument\_Message are unchanged. + +##### 4.6.1.4.4 Actions of IM-SSF in procedure CAMEL\_IMCN\_MT\_INVITE for Unregistered Subscriber + +When querying the HSS for the subscriber's IM CSI data, the IM-SSF does not have to wait for the HSS's response on the first query before the subsequent queries are done. i.e. Sending of multiple Any Time Interrogation operations can be done in parallel. However, the IM-SSF shall wait for all the responses from the HSS before it shall continue with the handling of the terminating IP multimedia session. + +##### 4.6.1.4.5 Handling of procedure CAMEL\_MT\_CTR, sheet 1 + +The IM-SSF behaves as a B2BUA (Back-2-Back User Agent) when a SIP INVITE is received for an terminating call and SIP INVITE is sent to the MRFC (via S-CSCF) as a result of a CAP ConnectToResource request received from the SCF. + +A SIP response 100 Trying is sent after each INVITE but is not shown in the SDLs. + +The IM-SSF shall handle the 200 OK response from the MRFC as specified in 3GPP TS 23.218 [5]. + +##### 4.6.1.4.6 Handling of procedure CAMEL\_MT\_CTR, sheet 5 + +The specifics on transporting information between the MRFC and the Application Server such as the IM-SSF, has not been standardised in 3GPP Rel-5 specifications for IMS. i.e. the SIP method to return Prompt\_And\_Collect result from + +the MRFC to the IM-SSF, the SIP method for sending notification of play announcement completion to the IM-SSF when a request for a Specialised Resource Report was received, the SIP method to request the MRFC to play announcement and the SIP method to request the MRFC to prompt and collect user information, are not standardised. + +#### 4.6.1.4.7 Receipt of 100 Trying Provisional Response (Process MT\_IM\_SSF) + +The IM-SSF (acting as a B2BUA) uses the S-CSCF as a next-hop server when sending the SIP INVITE to the terminating subscriber. The 100 Trying provisional response received in the IM-SSF is actually generated and sent from the S-CSCF to indicate that the INVITE request has been received by the next-hop server (i.e. the S-CSCF) and is currently being processed. + +#### 4.6.1.4.8 Handling of internal timers in Process MT\_IM\_SSF + +For additional description on usage of internal timers in Process MT\_IM\_SSF, please refer to the description in clause 4.6.1.3.9. + +![Flowchart for Process MT_IM_SSF. The flow starts with an oval, followed by 'Idle', 'INVITE', '100 Trying', and 'Initialise values'. A callout box for 'Initialise values' lists: CAMEL_Invocation := False; Provisional_Response_Received := False; Final_Response_Received := False; Ack_Received := False; Cancel_Received := False; Bye_Received := False. Next is a decision 'INVITE Expires received?'. 'Yes' leads to 'Tinvite := INVITE Expires received' and 'Start Tinvite'. 'No' bypasses these. Both paths lead to a circle with the number '3'.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +**Process MT\_IM\_SSF** 1(6) + +Process in IM-SSF to perform +Mobile Terminating Call +in IMS. + +/\* Signals to/from the left are to/from the MS +via S-CSCF; signals to/from right are to/from the +originating S-CSCF via S-CSCF, +unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Idle[Idle]; Idle --> INVITE[INVITE]; INVITE --> 100[100 Trying]; 100 --> Init[Initialise values]; Init --> Decision{INVITE Expires received?}; Init -.-> InitCallout[CAMEL_Invocation := False; Provisional_Response_Received := False; Final_Response_Received := False; Ack_Received := False; Cancel_Received := False; Bye_Received := False]; Decision -- Yes --> T[ +Tinvite := +INVITE Expires +received +]; T --> StartT[Start Tinvite]; Decision -- No --> Join(( )); T --> Join; StartT --> Join; Join --> End((3)); +``` + +Flowchart for Process MT\_IM\_SSF. The flow starts with an oval, followed by 'Idle', 'INVITE', '100 Trying', and 'Initialise values'. A callout box for 'Initialise values' lists: CAMEL\_Invocation := False; Provisional\_Response\_Received := False; Final\_Response\_Received := False; Ack\_Received := False; Cancel\_Received := False; Bye\_Received := False. Next is a decision 'INVITE Expires received?'. 'Yes' leads to 'Tinvite := INVITE Expires received' and 'Start Tinvite'. 'No' bypasses these. Both paths lead to a circle with the number '3'. + +Figure 4.22-1: Process MT\_IM\_SSF (sheet 1) + +![Flowchart for Process MT_IM_SSF (sheet 2). The process starts at connector 3, proceeds to Check Registration, then a Result? decision. If Fail, it goes to connector 1. If Pass, it sends CAMEL_IMCN_MT_VT_IM_CSI_INIT, then another Result? decision. If Pass, it sends INVITE, Start Tb, and Wait_For_MT_Answer. If Reconnect, it sends CAMEL_IMCN_MT_RECONNECT, then a Result? decision. If Fail, it goes to 606 Not Acceptable. If Pass, it goes to Establish Through Connection. If Fail, it goes to Release Call Resources. If INVITE Expires (from connector 4), it sets Event := 'Timer expired', sends CAMEL_IMCN_MT_CANCEL, and goes to 487 Request Terminated. Both 606 Not Acceptable and 487 Request Terminated lead to connector 2 and Release Call Resources. Both Establish Through Connection and Release Call Resources lead to Idle.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +**Process MT\_IM\_SSF** 2(6) + +Process in IM-SSF to perform +Mobile Terminating Call +in IMS. + +/\* Signals to/from the left are to/from the MS +via S-CSCF; signals to/from right are to/from the +originating S-CSCF via S-CSCF, +unless otherwise stated. \*/ + +``` +graph TD + 3((3)) --> Check[Check Registration] + Check --> Result1{Result ?} + Result1 -- Fail --> 1((1)) + Result1 -- Pass --> Init[CAMEL_IMCN
MT_VT_IM
CSI_INIT] + Init --> Result2{Result ?} + Result2 -- Pass --> INVITE[/INVITE/] + Result2 -- Reconnect --> ReconnectMsg[CAMEL_IMCN
MT_RECONNECT] + Result2 -- Fail --> 606[/606 Not Acceptable/] + INVITE --> Start[Start Tb] + Start --> Wait[Wait_For
MT_Answer] + ReconnectMsg --> Result3{Result ?} + Result3 -- Fail --> 606 + Result3 -- Pass --> Establish[Establish
Through
Connection] + 4((4)) -- INVITE Expires --> Event[Event :=
"Timer
expired"] + Event --> Cancel[CAMEL_IMCN
MT_CANCEL] + Cancel --> 487[/487 Request
Terminated/] + 606 --> 2((2)) + 606 --> Release[Release
Call
Resources] + 487 --> 2 + 487 --> Release + Establish --> Idle([Idle]) + Release --> Idle +``` + +Flowchart for Process MT\_IM\_SSF (sheet 2). The process starts at connector 3, proceeds to Check Registration, then a Result? decision. If Fail, it goes to connector 1. If Pass, it sends CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT, then another Result? decision. If Pass, it sends INVITE, Start Tb, and Wait\_For\_MT\_Answer. If Reconnect, it sends CAMEL\_IMCN\_MT\_RECONNECT, then a Result? decision. If Fail, it goes to 606 Not Acceptable. If Pass, it goes to Establish Through Connection. If Fail, it goes to Release Call Resources. If INVITE Expires (from connector 4), it sets Event := 'Timer expired', sends CAMEL\_IMCN\_MT\_CANCEL, and goes to 487 Request Terminated. Both 606 Not Acceptable and 487 Request Terminated lead to connector 2 and Release Call Resources. Both Establish Through Connection and Release Call Resources lead to Idle. + +Figure 4.22-2: Process MT\_IM\_SSF (sheet 2) + +![Flowchart for Process MT_IM_SSF. It starts with 'Wait_For_MT_Answer' and branches based on responses: 100 Trying, 1xx (except 100), and 200 OK. The 100 Trying path leads to 'Cancel Received?' which branches to 'Provisional_Response_Received := True' (leading to 'Wait_For_MT_Answer') or 'CANCEL' (leading to 'CAMEL_IMCN_MT_CANCEL' then '487 Request Terminated' then '200 OK' then '2'). The 1xx (except 100) path leads to '1xx' then 'Same Response Code' then back to the initial merge point. The 200 OK path leads to 'Final_Response_Received := True' then 'Stop Tb' then 'CAMEL_IMCN_MT_ANSWER' then 'Result?'. 'Result?' branches to 'Pass' (leading to '200 OK' then 'Stop Tininvite' then 'Start Tack' then 'Wait_For_ACK'), 'Reconnect' (leading to '1'), and 'Fail' (leading to '606 Not Acceptable' then '2').](5801c19431e76330430e92a598cc7a16_img.jpg) + +### Process MT\_IM\_SSF 3(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([Wait_For_MT_Answer]) --> Merge(( )); Merge --> 100[100 Trying]; Merge --> 1xx[1xx except 100]; Merge --> 200[200 OK]; 100 --> CancelRec{Cancel Received?}; CancelRec -- True --> CANCEL{{CANCEL}}; CancelRec -- False --> Provisional[Provisional_Response_Received := True]; Provisional --> Start; CANCEL --> CAMEL_CANCEL[CAMEL_IMCN_MT_CANCEL]; CAMEL_CANCEL --> 487[487 Request Terminated]; 487 --> 200OK1[200 OK]; 200OK1 --> 2_1((2)); 1xx --> 1xxOut[1xx]; 1xxOut --> SameCode[Same Response Code]; SameCode --> Merge; 200 --> Final[Final_Response_Received := True]; Final --> StopTb[Stop Tb]; StopTb --> CAMEL_ANSWER[CAMEL_IMCN_MT_ANSWER]; CAMEL_ANSWER --> Result{Result?}; Result -- Pass --> 200OK2[200 OK]; 200OK2 --> StopTin[Stop Tininvite]; StopTin --> StartTack[Start Tack]; StartTack --> WaitACK([Wait_For_ACK]); Result -- Reconnect --> 1((1)); Result -- Fail --> 606[606 Not Acceptable]; 606 --> 2_2((2)); +``` + +Flowchart for Process MT\_IM\_SSF. It starts with 'Wait\_For\_MT\_Answer' and branches based on responses: 100 Trying, 1xx (except 100), and 200 OK. The 100 Trying path leads to 'Cancel Received?' which branches to 'Provisional\_Response\_Received := True' (leading to 'Wait\_For\_MT\_Answer') or 'CANCEL' (leading to 'CAMEL\_IMCN\_MT\_CANCEL' then '487 Request Terminated' then '200 OK' then '2'). The 1xx (except 100) path leads to '1xx' then 'Same Response Code' then back to the initial merge point. The 200 OK path leads to 'Final\_Response\_Received := True' then 'Stop Tb' then 'CAMEL\_IMCN\_MT\_ANSWER' then 'Result?'. 'Result?' branches to 'Pass' (leading to '200 OK' then 'Stop Tininvite' then 'Start Tack' then 'Wait\_For\_ACK'), 'Reconnect' (leading to '1'), and 'Fail' (leading to '606 Not Acceptable' then '2'). + +Figure 4.22-3: Process MT\_IM\_SSF (sheet 3) + +![Flowchart for Process MT_IM_SSF. It starts with 'Wait_For_MT_Answer' and branches into four main paths: 1. CANCEL path: CANCEL -> Provisional_Response_Received? (True leads to CAMEL_IMCN_MT_CANCEL, 487 Request Terminated, 200 OK; False leads to Cancel_Received := True -> Wait_For_MT_Answer). 2. 4xx, 5xx, 6xx path: 4xx, 5xx, 6xx -> ACK -> Event := (Response Code) -> CAMEL_IMCN_MT_CANCEL. 3. Tb expiry path: Tb expiry -> Provisional_Response_Recvd? (Yes leads to CANCEL -> Event := 'Timer expired' -> CAMEL_IMCN_MT_UNSUCCESSFUL; No leads to CAMEL_IMCN_MT_UNSUCCESSFUL). 4. Tinvite expiry path: Tinvite expiry -> Provisional_Response_Received? (Yes leads to CANCEL -> 4; No leads to 4). All paths eventually lead to connector 2, except for the CAMEL_IMCN_MT_UNSUCCESSFUL path which leads to connector 1 if 'Result = Reconnect?' is Yes, otherwise to connector 2.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +### Process MT\_IM\_SSF + +4(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([Wait_For_MT_Answer]) --> CANCEL{CANCEL}; Start --> 4xx[4xx, 5xx, 6xx]; Start --> Tb[Tb expiry]; Start --> Tinvite[Tinvite expiry]; CANCEL --> PR{Provisional_Response_Received?}; PR -- True --> CAMEL_IMCN_MT_CANCEL[CAMEL_IMCN_MT_CANCEL]; PR -- False --> Cancel_Received[Cancel_Received := True]; Cancel_Received --> Start; 4xx --> ACK{ACK}; ACK --> Event1[Event := (Response Code)]; Event1 --> CAMEL_IMCN_MT_CANCEL; Tb --> PR2{Provisional_Response_Recvd?}; PR2 -- Yes --> CANCEL2{CANCEL}; PR2 -- No --> CAMEL_IMCN_MT_UNSUCCESSFUL[CAMEL_IMCN_MT_UNSUCCESSFUL]; CANCEL2 --> Event2[Event := "Timer expired"]; Event2 --> CAMEL_IMCN_MT_UNSUCCESSFUL; Tinvite --> PR3{Provisional_Response_Received?}; PR3 -- Yes --> CANCEL3{CANCEL}; PR3 -- No --> 4((4)); CAMEL_IMCN_MT_CANCEL --> 487[487 Request Terminated]; 487 --> 200[200 OK]; 200 --> 2((2)); CAMEL_IMCN_MT_UNSUCCESSFUL --> Reconnect{Result = Reconnect?}; Reconnect -- Yes --> 1((1)); Reconnect -- No --> 2; +``` + +Flowchart for Process MT\_IM\_SSF. It starts with 'Wait\_For\_MT\_Answer' and branches into four main paths: 1. CANCEL path: CANCEL -> Provisional\_Response\_Received? (True leads to CAMEL\_IMCN\_MT\_CANCEL, 487 Request Terminated, 200 OK; False leads to Cancel\_Received := True -> Wait\_For\_MT\_Answer). 2. 4xx, 5xx, 6xx path: 4xx, 5xx, 6xx -> ACK -> Event := (Response Code) -> CAMEL\_IMCN\_MT\_CANCEL. 3. Tb expiry path: Tb expiry -> Provisional\_Response\_Recvd? (Yes leads to CANCEL -> Event := 'Timer expired' -> CAMEL\_IMCN\_MT\_UNSUCCESSFUL; No leads to CAMEL\_IMCN\_MT\_UNSUCCESSFUL). 4. Tinvite expiry path: Tinvite expiry -> Provisional\_Response\_Received? (Yes leads to CANCEL -> 4; No leads to 4). All paths eventually lead to connector 2, except for the CAMEL\_IMCN\_MT\_UNSUCCESSFUL path which leads to connector 1 if 'Result = Reconnect?' is Yes, otherwise to connector 2. + +Figure 4.22-4: Process MT\_IM\_SSF (sheet 4) + +![SDL Diagram for Process MT_IM_SSF sheet 5](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +### Process MT\_IM\_SSF + +5(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +*/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/* + +``` + +stateDiagram-v2 + state "Wait_For_ACK" as Wait_For_ACK + state "Stop Tack" as Stop_Tack + state "Bye_Received?" as Bye_Received_Check1 <> + state "Ack_Received := True" as Set_Ack_True + state "Wait_For_Clear" as Wait_For_Clear + + state "Ack_Received?" as Ack_Received_Check <> + state "CAMEL_IMCN\nMT_DISC2" as MT_DISC2 + state "Result =\nReconnect?" as Reconnect_Check <> + state "Bye_Received := True" as Set_Bye_True + + state "CAMEL_IMCN\nMT_DISC1" as MT_DISC1_A + state "CAMEL_IMCN\nMT_DISC1" as MT_DISC1_B + state "Bye_Received?" as Bye_Received_Check2 <> + + [*] --> Wait_For_ACK + + %% Branch 1: ACK + Wait_For_ACK --> ACK_Signal + state "ACK" as ACK_Signal + ACK_Signal --> Stop_Tack + Stop_Tack --> Bye_Received_Check1 + Bye_Received_Check1 --> ACK_Out : True + Bye_Received_Check1 --> Set_Ack_True : False + Set_Ack_True --> ACK_Out + state "ACK" as ACK_Out + ACK_Out --> Wait_For_Clear + + %% Branch 2: BYE + Wait_For_ACK --> BYE_Signal1 + state "BYE" as BYE_Signal1 + BYE_Signal1 --> Ack_Received_Check + Ack_Received_Check --> MT_DISC2 : True + MT_DISC2 --> Reconnect_Check + Reconnect_Check --> Connector1 : Yes + Reconnect_Check --> Connector2 : No + Ack_Received_Check --> Set_Bye_True : False + Set_Bye_True --> Wait_For_ACK + + %% Branch 3: BYE + Wait_For_ACK --> BYE_Signal2 + state "BYE" as BYE_Signal2 + BYE_Signal2 --> MT_DISC1_A + MT_DISC1_A --> Connector2 + + %% Branch 4: Tack expiry + Wait_For_ACK --> Tack_expiry + state "Tack\nexpiry" as Tack_expiry + note right of Tack_expiry : Internal + Tack_expiry --> BYE_Out + state "BYE" as BYE_Out + BYE_Out --> Bye_Received_Check2 + Bye_Received_Check2 --> ACK_Internal : True + state "ACK" as ACK_Internal + ACK_Internal --> BYE_Internal + state "BYE" as BYE_Internal + BYE_Internal --> MT_DISC1_B + Bye_Received_Check2 --> MT_DISC1_B : False + MT_DISC1_B --> Connector2_B + + state "1" as Connector1 + state "2" as Connector2 + state "2" as Connector2_B + +``` + +SDL Diagram for Process MT\_IM\_SSF sheet 5 + +**Figure 4.22-5: Process MT\_IM\_SSF (sheet 5)** + +![State transition diagram for Process MT_IM_SSF. It starts with 'Wait_For_Clear' leading to three parallel paths: 1) BYE (left) -> CAMEL_IMCN MT_DISC2 -> Result = Reconnect? (Yes leads to 1, No leads to 2); 2) BYE (right) -> CAMEL_IMCN MT_DISC1 -> 2; 3) Int_Release Call (From imcnSSF) -> BYE (right) -> BYE (left) -> 2.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +### Process MT\_IM\_SSF 6(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Wait_For_Clear + state "Wait_For_Clear" as Wait_For_Clear + state "BYE (left)" as BYE_L + state "BYE (right)" as BYE_R + state "Int_Release Call (From imcnSSF)" as Int_Release + state "CAMEL_IMCN MT_DISC2" as CAMEL_IMCN_2 + state "CAMEL_IMCN MT_DISC1" as CAMEL_IMCN_1 + state "Result = Reconnect?" as Result_Reconnect + state "1" as 1 + state "2" as 2 + state "BYE (right)" as BYE_R2 + state "BYE (left)" as BYE_L2 + + Wait_For_Clear --> BYE_L + Wait_For_Clear --> BYE_R + Wait_For_Clear --> Int_Release + BYE_L --> CAMEL_IMCN_2 + CAMEL_IMCN_2 --> Result_Reconnect + Result_Reconnect -- Yes --> 1 + Result_Reconnect -- No --> 2 + BYE_R --> CAMEL_IMCN_1 + CAMEL_IMCN_1 --> 2 + Int_Release --> BYE_R2 + BYE_R2 --> BYE_L2 + BYE_L2 --> 2 +``` + +State transition diagram for Process MT\_IM\_SSF. It starts with 'Wait\_For\_Clear' leading to three parallel paths: 1) BYE (left) -> CAMEL\_IMCN MT\_DISC2 -> Result = Reconnect? (Yes leads to 1, No leads to 2); 2) BYE (right) -> CAMEL\_IMCN MT\_DISC1 -> 2; 3) Int\_Release Call (From imcnSSF) -> BYE (right) -> BYE (left) -> 2. + +Figure 4.22-6: Process MT\_IM\_SSF (sheet 6) + +### Procedure Check\_Registration + +1(1) + +Procedure in IM-SSF to check and obtain +CSI for a terminating unregistered subscriber + +/\* Signals to/from the right are +to/from the HSS. \*/ + +![Flowchart for Procedure Check_Registration. It starts with a start connector, followed by a decision 'VT-IM-CSI present?'. If 'Yes', it goes to 'Result := Pass'. If 'No', it goes to 'ATSI_query' which sends 'Requested CSI: VT-IM-CSI', then enters 'Wait for response' state. From there, 'ATSI_Ack' leads to 'Store Subscriber info' and then 'Result := Pass'. Alternatively, 'ATSI Negative Response' leads to 'Result := Fail'. Both results terminate at an end connector.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +``` + +graph TD + Start([ ]) --> Decision{VT-IM-CSI +present?} + Decision -- Yes --> ResultPass[Result := +Pass] + Decision -- No --> ATSI_query{{ATSI_query}} + ATSI_query --- RequestedCSI[Requested CSI: +VT-IM-CSI] + ATSI_query --> Wait[Wait for response] + Wait --> ATSI_Ack>ATSI_Ack] + Wait --> ATSI_Neg>ATSI Negative +Response] + ATSI_Ack --> Store[Store +Subscriber info] + Store --> ResultPass + ATSI_Neg --> ResultFail[Result := +Fail] + ResultPass --> End((X)) + ResultFail --> End + +``` + +Flowchart for Procedure Check\_Registration. It starts with a start connector, followed by a decision 'VT-IM-CSI present?'. If 'Yes', it goes to 'Result := Pass'. If 'No', it goes to 'ATSI\_query' which sends 'Requested CSI: VT-IM-CSI', then enters 'Wait for response' state. From there, 'ATSI\_Ack' leads to 'Store Subscriber info' and then 'Result := Pass'. Alternatively, 'ATSI Negative Response' leads to 'Result := Fail'. Both results terminate at an end connector. + +Figure 4.23: Procedure Check\_Registration (sheet 1) + +# Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +1(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call INVITE request \*/ + +/\* Signals to/from the left are to/from the originating S-CSCF via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_VT_IM_CSI_INIT. The process starts with a decision 'VT-IM-CSI invocation?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sets 'CAMEL_Invocation := True', stores original call parameters, and invokes 'Int_Invoke_imcnSSF (VT-IM-CSI)'. It then waits for 'imcnSSF_Invoked'. From there, it branches: one path goes to 'Int_imcnSSF_Invoked' -> 'Int_DP_Termination_Attempt_Autorised' -> 'DP_Termination_Attempt_Autorised' -> End; the other path goes to 'CANCEL' -> 'CAMEL_IMCN MT_CANCEL' -> 'Result := Abort' -> End.](f06d7a2fad72d80fe12fca1b65fc805b_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{VT-IM-CSI invocation?}; Decision -- No --> ResultPass[Result:= Pass]; ResultPass --> End1(( )); Decision -- Yes --> CAMELTrue[CAMEL_Invocation := True]; CAMELTrue --> StoreParams[Store original call parameters]; StoreParams --> InvokeImcnSSF[Int_Invoke_imcnSSF (VT-IM-CSI)]; InvokeImcnSSF --> WaitImcnSSF[wait_for_imcnSSF_Invoked]; WaitImcnSSF --> ImcnSSFInvoked[Int_imcnSSF_Invoked]; ImcnSSFInvoked --> DPAttemptAuth[Int_DP_Termination_Attempt_Autorised]; DPAttemptAuth --> DPAuthorised[DP_Termination_Attempt_Autorised]; DPAuthorised --> End2(( )); WaitImcnSSF --> CANCEL{CANCEL}; CANCEL --> MT_CANCEL[CAMEL_IMCN MT_CANCEL]; MT_CANCEL --> ResultAbort[Result := Abort]; ResultAbort --> End3(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT. The process starts with a decision 'VT-IM-CSI invocation?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sets 'CAMEL\_Invocation := True', stores original call parameters, and invokes 'Int\_Invoke\_imcnSSF (VT-IM-CSI)'. It then waits for 'imcnSSF\_Invoked'. From there, it branches: one path goes to 'Int\_imcnSSF\_Invoked' -> 'Int\_DP\_Termination\_Attempt\_Autorised' -> 'DP\_Termination\_Attempt\_Autorised' -> End; the other path goes to 'CANCEL' -> 'CAMEL\_IMCN MT\_CANCEL' -> 'Result := Abort' -> End. + +Figure 4.24-1: Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT (sheet 1) + +## Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +2(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call INVITE request \*/ + +/\* Signals to/from the left are to/from the originating S-CSCF via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_VT_IM_CSI_INIT](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) + +``` +graph TD; Start([DP_Termination_Attempt_Authorised]) --> Int_Connect[/Int_Connect/]; Start --> Int_Continue_With_Argument[/Int_Continue_With_Argument/]; Start --> Int_Continue[/Int_Continue/]; Start --> Int_Error[/Int_Error/]; Start --> Int_Release_Call[/Int_Release_Call/]; Int_Connect --> 181[181 Call Is Being Forwarded]; 181 --> Modify1[Modify call parameters with received information]; Int_Continue_With_Argument --> Modify2[Modify call parameters with received information]; Int_Continue --> Decision{Default Call Handling = Continue Call?}; Int_Error --> Decision; Int_Release_Call --> Decision; Decision -- Yes --> INVITE[/INVITE/]; INVITE --> ToTerminatingMS[To the terminating MS]; ToTerminatingMS --> ResultPass[Result := Pass]; ResultPass --> EndPass(( )); Decision -- No --> ResultFail[Result := Fail]; ResultFail --> EndFail(( )); Modify1 --> Decision; Modify2 --> Decision; +``` + +The flowchart illustrates the procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT. It begins with a decision node 'DP\_Termination\_Attempt\_Authorised'. From this node, five paths emerge: 'Int\_Connect', 'Int\_Continue\_With\_Argument', 'Int\_Continue', 'Int\_Error', and 'Int\_Release\_Call'. The 'Int\_Connect' path leads to '181 Call Is Being Forwarded', which then leads to 'Modify call parameters with received information'. The 'Int\_Continue\_With\_Argument' path also leads to 'Modify call parameters with received information'. Both 'Int\_Continue' and 'Int\_Error' paths lead to a decision node 'Default Call Handling = Continue Call?'. The 'Int\_Release\_Call' path also leads to this decision node. If the decision is 'Yes', the flow proceeds to 'INVITE', which then leads to 'To the terminating MS', then 'Result := Pass', and finally an end symbol. If the decision is 'No', the flow proceeds to 'Result := Fail', and finally an end symbol. Both 'Modify call parameters with received information' blocks lead to the 'Default Call Handling = Continue Call?' decision node. + +Flowchart for Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +Figure 4.24-2: Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT (sheet 2) + +### Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +3(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call INVITE request \*/ + +/\* Signals to/from the left are to/from the originating S-CSCF via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_VT_IM_CSI_INIT. It starts with DP_Termination_Attempt_Authorised, branching into Internal (Tinvite expirry), CANCEL, and Int_Connect_To_Resource paths. The CANCEL path leads to CAMEL_IMCN_MT_CANCEL and then to a decision diamond 'Result= Fail?'. The Int_Connect_To_Resource path leads to CAMEL_MT_CTR and then to the same decision diamond. The Tinvite expirry path leads to Result := INVITE Expires. The decision diamond 'Result= Fail?' has 'No' and 'Yes' branches. The 'No' branch leads to DP_Termination_Attempt_Authorised. The 'Yes' branch leads to Result := Fail. All three main paths end at a circle with an X.](708e4c9a044ef61f586126676eb2eeb8_img.jpg) + +``` +graph TD; Start([DP_Termination_Attempt_Authorised]) --> Internal[Internal]; Start --> Tinvite[Tinvite expirry]; Start --> CANCEL[CANCEL]; Start --> Int_Connect[Int_Connect_To_Resource]; Tinvite --> R1[Result := INVITE Expires]; R1 --> End1((X)); CANCEL --> CAMEL_CANCEL[CAMEL_IMCN_MT_CANCEL]; CAMEL_CANCEL --> R2[Result := Abort]; R2 --> End2((X)); Int_Connect --> CAMEL_CTR[CAMEL_MT_CTR]; CAMEL_CTR --> Decision{Result= Fail?}; Decision -- No --> Start; Decision -- Yes --> R3[Result := Fail]; R3 --> End3((X)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT. It starts with DP\_Termination\_Attempt\_Authorised, branching into Internal (Tinvite expirry), CANCEL, and Int\_Connect\_To\_Resource paths. The CANCEL path leads to CAMEL\_IMCN\_MT\_CANCEL and then to a decision diamond 'Result= Fail?'. The Int\_Connect\_To\_Resource path leads to CAMEL\_MT\_CTR and then to the same decision diamond. The Tinvite expirry path leads to Result := INVITE Expires. The decision diamond 'Result= Fail?' has 'No' and 'Yes' branches. The 'No' branch leads to DP\_Termination\_Attempt\_Authorised. The 'Yes' branch leads to Result := Fail. All three main paths end at a circle with an X. + +Figure 4.24-3: Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT (sheet 3) + +![Flowchart for Procedure CAMEL_IMCN_MT_RECONNECT. It starts with an INVITE message, followed by a Wait_For_Response state. From there, it branches based on the response: 1xx Provisional Response leads back to Wait_For_Response; 200 OK leads to Result := Pass; an empty response box leads to a note about other response codes; and Timer expiry leads to Internal and Result := Fail.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_RECONNECT 1(1) + +Procedure in IM-SSF to handle MT call to redirect the call. + +/\* Signals to/from the right are to/from the process MO\_IM\_SSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> INVITE{{INVITE}}; INVITE --> Wait_For_Response([Wait_For_Response]); Wait_For_Response --> Branch(( )); Branch --> Provisional[1xx Provisional Response]; Provisional --> Wait_For_Response; Branch --> OK[200 OK]; OK --> Pass[Result := Pass]; Pass --> End1(( )); Branch --> Other[ ]; Other --> Note[Any response codes other than listed in this state]; Branch --> Timer[Timer expiry]; Timer --> Internal[Internal]; Timer --> Fail[Result := Fail]; Fail --> End2(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_RECONNECT. It starts with an INVITE message, followed by a Wait\_For\_Response state. From there, it branches based on the response: 1xx Provisional Response leads back to Wait\_For\_Response; 200 OK leads to Result := Pass; an empty response box leads to a note about other response codes; and Timer expiry leads to Internal and Result := Fail. + +Figure 4.25: Procedure CAMEL\_IMCN\_MT\_RECONNECT (sheet 1) + +# Procedure CAMEL\_IMCN\_MT\_CANCEL + +1(1) + +/\* Procedure in IM-SSF to perform CAMEL handling for an incoming call CANCEL request. \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_CANCEL. It starts with an oval connector, leading to a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a circular connector at the bottom. If 'Yes', it goes to a parallelogram 'Int_DP_T_Abandon', then a rounded rectangle 'DP_T_Abandon', then a parallelogram 'Int_Continue', and finally to the circular connector at the bottom.](b8efedb73292a798b3f2050f9335cae6_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{imcnSSF Invoked?}; Decision -- No --> End(( )); Decision -- Yes --> Int_DP_T_Abandon[/Int_DP_T_Abandon/]; Int_DP_T_Abandon --> DP_T_Abandon(DP_T_Abandon); DP_T_Abandon --> Int_Continue[/Int_Continue/]; Int_Continue --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_CANCEL. It starts with an oval connector, leading to a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a circular connector at the bottom. If 'Yes', it goes to a parallelogram 'Int\_DP\_T\_Abandon', then a rounded rectangle 'DP\_T\_Abandon', then a parallelogram 'Int\_Continue', and finally to the circular connector at the bottom. + +Figure 4.26: Procedure CAMEL\_IMCN\_MT\_CANCEL (sheet 1) + +# Procedure CAMEL\_IMCN\_MT\_ANSWER + +1(2) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call upon 200 OK message \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_ANSWER. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it goes to 'Int_DP_T_Answer' (outlet), then 'DP_T_Answer' (inlet). From 'DP_T_Answer', it branches into three outlets: 'Int_Continue', 'Int_Release', and 'Int_Error'. 'Int_Continue' leads to 'Result:= Pass'. 'Int_Release' leads to a decision 'Default call handling = continue call ?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it goes to 'Result:= Pass'. 'Int_Error' leads to 'Result:= Pass'. All three 'Result' blocks lead to a final connector.](91c33f8e1713989e8192322ec2d1212b_img.jpg) + +Flowchart for Procedure CAMEL\_IMCN\_MT\_ANSWER. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it goes to 'Int\_DP\_T\_Answer' (outlet), then 'DP\_T\_Answer' (inlet). From 'DP\_T\_Answer', it branches into three outlets: 'Int\_Continue', 'Int\_Release', and 'Int\_Error'. 'Int\_Continue' leads to 'Result:= Pass'. 'Int\_Release' leads to a decision 'Default call handling = continue call ?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it goes to 'Result:= Pass'. 'Int\_Error' leads to 'Result:= Pass'. All three 'Result' blocks lead to a final connector. + +Figure 4.27-1: Procedure CAMEL\_IMCN\_MT\_ANSWER (sheet 1) + +### Procedure CAMEL\_IMCN\_MT\_ANSWER + +2(2) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call upon 200 OK message \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_ANSWER. It starts with DP_T_Answer, branches into two BYE message paths (one to the left, one from the originating S-CSCF), followed by CAMEL_IMCN MT_DISC2 and MT_DISC1 respectively. Both lead to a 'Result = Reconnect?' decision. If 'Yes', Result := Reconnect. If 'No', Result := Fail. Both paths then merge to a common exit point.](ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg) + +``` +graph TD; DP_T_Answer([DP_T_Answer]) --> BYE_L[/BYE/]; DP_T_Answer --> BYE_R[/BYE/]; BYE_R -.-> Note1[From the originating S-CSCF]; BYE_L --> MT_DISC2[CAMEL_IMCN MT_DISC2]; BYE_R --> MT_DISC1[CAMEL_IMCN MT_DISC1]; MT_DISC2 --> Decision{Result = Reconnect?}; MT_DISC1 --> Decision; Decision -- Yes --> Result_Reconnect[Result := Reconnect]; Decision -- No --> Result_Fail[Result := Fail]; Result_Reconnect --> Exit(( )); Result_Fail --> Exit +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_ANSWER. It starts with DP\_T\_Answer, branches into two BYE message paths (one to the left, one from the originating S-CSCF), followed by CAMEL\_IMCN MT\_DISC2 and MT\_DISC1 respectively. Both lead to a 'Result = Reconnect?' decision. If 'Yes', Result := Reconnect. If 'No', Result := Fail. Both paths then merge to a common exit point. + +Figure 4.27-2: Procedure CAMEL\_IMCN\_MT\_ANSWER (sheet 2) + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts with a connector symbol leading to an 'Event?' decision diamond. Three paths emerge: 1) Left path for error codes (4xx except 401, 407, 408, 413, 420, 480; or 5xx; or 6xx except 603) leading to circle 1. 2) Middle path for error codes (408, 480, 603) leading to circle 2. 3) Right path for 'Timer expiry' leading to circle 3.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL 1(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Event{Event?}; Event -- "4xx except 401, 407, 408, 413, 420, 480; or 5xx; or 6xx except 603." --> 1((1)); Event -- "408, 480, 603" --> 2((2)); Event -- "Timer expiry" --> 3((3)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts with a connector symbol leading to an 'Event?' decision diamond. Three paths emerge: 1) Left path for error codes (4xx except 401, 407, 408, 413, 420, 480; or 5xx; or 6xx except 603) leading to circle 1. 2) Middle path for error codes (408, 480, 603) leading to circle 2. 3) Right path for 'Timer expiry' leading to circle 3. + +Figure 4.28-1: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 1) + +## Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL + +2(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) + +``` +graph TD; Start((1)) --> Decision{imcnSSF invoked?}; Decision -- No --> End(( )); Decision -- Yes --> Int_DP_T_Busy[Int_DP_T_Busy]; Int_DP_T_Busy --> DP_T_Busy([DP_T_Busy]); DP_T_Busy --> Int_Connect[/Int_Connect/]; DP_T_Busy --> Int_Continue[/Int_Continue/]; DP_T_Busy --> Int_Error[/Int_Error/]; DP_T_Busy --> Int_Release_Call[/Int_Release_Call/]; Int_Release_Call --> End; Int_Continue --> SIP_Response[Same SIP 4XX, 5XX, or 6XX response received]; Int_Error --> SIP_Response; SIP_Response --> Wait_For_ACK[Wait_For_ACK For_Error]; Wait_For_ACK --> ACK[ACK]; ACK -- From originating S-CSCF --> ACK; ACK --> Result_Continue[Result := Continue]; Int_Connect --> Modify_Param[Modify call parameters with received information]; Modify_Param --> Result_Reconnect[Result := Reconnect]; Result_Continue --> End; Result_Reconnect --> End; +``` + +The flowchart illustrates the procedure for handling an unsuccessful Mobile Terminating Call (MT) in IMS. It begins at connector 1 and checks if 'imcnSSF invoked?'. If 'No', it ends at connector 2. If 'Yes', it proceeds to 'Int\_DP\_T\_Busy' and then 'DP\_T\_Busy'. From 'DP\_T\_Busy', four paths are available: 'Int\_Connect', 'Int\_Continue', 'Int\_Error', and 'Int\_Release\_Call'. 'Int\_Release\_Call' leads directly to connector 2. 'Int\_Continue' and 'Int\_Error' both lead to a common block 'Same SIP 4XX, 5XX, or 6XX response received', which then leads to 'Wait\_For\_ACK For\_Error'. 'Wait\_For\_ACK For\_Error' leads to 'ACK', which receives input 'From originating S-CSCF' and leads to 'Result := Continue'. 'Int\_Connect' leads to 'Modify call parameters with received information', which leads to 'Result := Reconnect'. Both 'Result := Continue' and 'Result := Reconnect' lead to connector 2. + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL + +Figure 4.28-2: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 2) + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts at connector 2, checks if imcnSSF is invoked. If No, it goes to 'To originating S-CSCF'. If Yes, it sends 'Int_DP_T_No_Answer', then 'DP_T_No_Answer'. It then branches into four options: Int_Connect, Int_Continue, Int_Error, and Int_Release_Call. Int_Connect leads to 'Modify call parameters with received information' and 'Result := Reconnect'. Int_Continue leads to 'Int_T_Exception'. Int_Error and Int_Release_Call lead to a merge point. From the merge point, it checks 'Same SIP 4XX response received'. If Yes, it goes to 'To originating S-CSCF'. If No, it goes to 'Wait_For_ACK_For_Error', then 'ACK' (From originating S-CSCF), then 'Result := Continue'. All three final results (Reconnect, Continue, and the path from Int_Release_Call) lead to the end connector.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL + +3(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start((2)) --> Decision{imcnSSF invoked?}; Decision -- No --> ToS-CSCF1[To originating S-CSCF]; Decision -- Yes --> Int_DP_T_No_Answer{{Int_DP_T_No_Answer}}; Int_DP_T_No_Answer --> DP_T_No_Answer{{DP_T_No_Answer}}; DP_T_No_Answer --> Int_Connect{{Int_Connect}}; DP_T_No_Answer --> Int_Continue{{Int_Continue}}; DP_T_No_Answer --> Int_Error{{Int_Error}}; DP_T_No_Answer --> Int_Release_Call{{Int_Release_Call}}; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> Int_T_Exception{{Int_T_Exception}}; Int_Error --> Merge(( )); Int_Release_Call --> Merge; Merge --> SameSIP{Same SIP 4XX response received}; SameSIP -- Yes --> ToS-CSCF2[To originating S-CSCF]; SameSIP -- No --> Wait[Wait_For_ACK_For_Error]; Wait --> ACK{{ACK}}; ACK -- From originating S-CSCF --> Result_Continue[Result := Continue]; Result_Reconnect --> End(( )); Result_Continue --> End; ToS-CSCF1 --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts at connector 2, checks if imcnSSF is invoked. If No, it goes to 'To originating S-CSCF'. If Yes, it sends 'Int\_DP\_T\_No\_Answer', then 'DP\_T\_No\_Answer'. It then branches into four options: Int\_Connect, Int\_Continue, Int\_Error, and Int\_Release\_Call. Int\_Connect leads to 'Modify call parameters with received information' and 'Result := Reconnect'. Int\_Continue leads to 'Int\_T\_Exception'. Int\_Error and Int\_Release\_Call lead to a merge point. From the merge point, it checks 'Same SIP 4XX response received'. If Yes, it goes to 'To originating S-CSCF'. If No, it goes to 'Wait\_For\_ACK\_For\_Error', then 'ACK' (From originating S-CSCF), then 'Result := Continue'. All three final results (Reconnect, Continue, and the path from Int\_Release\_Call) lead to the end connector. + +Figure 4.28-3: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 3) + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts at connector '3', checks if 'imcnSSF invoked?'. If 'No', it goes to the end connector. If 'Yes', it sends 'Int_DP_T_No_Answer' to 'DP_T_No_Answer'. From there, it branches into four options: 'Int_Connect' (leading to 'Modify call parameters with received information' then 'Result := Reconnect'), 'Int_Continue' (leading to 'Int_T_Exception'), 'Int_Error' (leading to '487 Request Terminated' then 'To originating S-CSCF'), and 'Int_Release_Call'. All four paths merge at a junction. From the junction, the flow goes to 'Wait_For_ACK_For_Error', then 'ACK' (from originating S-CSCF), then 'Result := Continue', and finally to the end connector.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL 4(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start((3)) --> Decision{imcnSSF invoked?}; Decision -- No --> End((X)); Decision -- Yes --> Int_DP_T_No_Answer{{Int_DP_T_No_Answer}}; Int_DP_T_No_Answer --> DP_T_No_Answer([DP_T_No_Answer]); DP_T_No_Answer --> Int_Connect{{Int_Connect}}; DP_T_No_Answer --> Int_Continue{{Int_Continue}}; DP_T_No_Answer --> Int_Error{{Int_Error}}; DP_T_No_Answer --> Int_Release_Call{{Int_Release_Call}}; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> Int_T_Exception{{Int_T_Exception}}; Int_Error --> 487[487 Request Terminated]; 487 --> To_S_CSCF[To originating S-CSCF]; Int_Release_Call --> Junction(( )); Int_T_Exception --> Junction; Result_Reconnect --> Junction; Junction --> Wait_For_ACK[Wait_For_ACK_For_Error]; Wait_For_ACK --> ACK[ACK]; ACK --> From_S_CSCF[From originating S-CSCF]; ACK --> Result_Continue[Result := Continue]; Result_Continue --> Junction; Junction --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts at connector '3', checks if 'imcnSSF invoked?'. If 'No', it goes to the end connector. If 'Yes', it sends 'Int\_DP\_T\_No\_Answer' to 'DP\_T\_No\_Answer'. From there, it branches into four options: 'Int\_Connect' (leading to 'Modify call parameters with received information' then 'Result := Reconnect'), 'Int\_Continue' (leading to 'Int\_T\_Exception'), 'Int\_Error' (leading to '487 Request Terminated' then 'To originating S-CSCF'), and 'Int\_Release\_Call'. All four paths merge at a junction. From the junction, the flow goes to 'Wait\_For\_ACK\_For\_Error', then 'ACK' (from originating S-CSCF), then 'Result := Continue', and finally to the end connector. + +Figure 4.28-4: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 4) + +## Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL + +5(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL](20809e79dee38f3d6e03e1ad565a9cf5_img.jpg) + +``` +graph TD; Start([ ]) --> DP["DP_T_Busy
DP_T_No_Answer"]; DP --> CANCEL{CANCEL}; CANCEL --> FromS["From the originating
S-CSCF"]; CANCEL --> IMCN["CAMEL_IMCN
MT_CANCEL"]; IMCN --> Result{"Result ?"}; IntConnect{Int_Connect_To
Resource} --> IMCTR["CAMEL
MT_CTR"]; IMCTR --> Result; Result -- Fail --> Terminate{487 Request
Terminated}; Terminate --> ToS["To the originating
S-CSCF"]; Terminate --> OK{200 OK}; OK --> ResultFail["Result :=
Fail"]; ResultFail --> End((X)); Result -- Pass --> End +``` + +The flowchart illustrates the procedure for handling an unsuccessful Mobile Terminating Call (MT) in IMS. It begins with an entry point leading to a decision based on **DP\_T\_Busy** or **DP\_T\_No\_Answer**. If a **CANCEL** signal is received from the originating S-CSCF, the procedure calls **CAMEL\_IMCN MT\_CANCEL**. If an **Int\_Connect\_To Resource** signal is received, it calls **CAMEL MT\_CTR**. Both calls lead to a **Result ?** decision. If the result is **Fail**, a **487 Request Terminated** message is sent to the originating S-CSCF, followed by a **200 OK** response, and the result is set to **Fail**. If the result is **Pass**, the procedure ends. + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL + +Figure 4.28-5: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 5) + +![Flowchart for Procedure CAMEL_IMCN_MT_DISC1. It starts with a connector, checks if imcnSSF is invoked. If No, it goes to Result:= Continue. If Yes, it sends Int_DP_T_Disconnect (legId=1) and DP_T_Disconnect_1. It then branches into Int_Error, Int_Release_Call, Int_Continue, and BYE. The first three lead to a BYE, 200 OK, and To the originating S-CSCF. The BYE branch sends Int_DP_T_Disconnect (legId=2) and DP_T_Disconnect_2, then branches into Int_Continue, Int_Error, and Int_ReleaseCall, which lead to a 200 OK and To the originating S-CSCF.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_DISC1 1(1) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from caller \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Decision{imcnSSF invoked?}; Decision -- No --> Result[Result:= Continue]; Result --> End(( )); Decision -- Yes --> Int_DP_T_Disconnect_1[/Int_DP_T_Disconnect +/* legId = 1 *//]; Int_DP_T_Disconnect_1 --> DP_T_Disconnect_1(DP_T_Disconnect_1); DP_T_Disconnect_1 --> Int_Error_1[Int_Error]; DP_T_Disconnect_1 --> Int_Release_Call_1[Int_Release_Call]; DP_T_Disconnect_1 --> Int_Continue_1[Int_Continue]; DP_T_Disconnect_1 --> BYE_1[BYE]; Int_Error_1 --> BYE_1; Int_Release_Call_1 --> BYE_1; Int_Continue_1 --> BYE_1; BYE_1 --> BYE_2[BYE]; BYE_2 --> 200_OK_1[200 OK]; 200_OK_1 --> To_S_CSCF_1[To the originating S-CSCF]; BYE_1 --> Int_DP_T_Disconnect_2[/Int_DP_T_Disconnect +/* legId = 2 *//]; Int_DP_T_Disconnect_2 --> DP_T_Disconnect_2(DP_T_Disconnect_2); DP_T_Disconnect_2 --> Int_Continue_2[Int_Continue]; DP_T_Disconnect_2 --> Int_Error_2[Int_Error]; DP_T_Disconnect_2 --> Int_ReleaseCall_2[Int_ReleaseCall]; Int_Continue_2 --> 200_OK_2[200 OK]; Int_Error_2 --> 200_OK_2; Int_ReleaseCall_2 --> 200_OK_2; 200_OK_2 --> To_S_CSCF_2[To the originating S-CSCF]; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_DISC1. It starts with a connector, checks if imcnSSF is invoked. If No, it goes to Result:= Continue. If Yes, it sends Int\_DP\_T\_Disconnect (legId=1) and DP\_T\_Disconnect\_1. It then branches into Int\_Error, Int\_Release\_Call, Int\_Continue, and BYE. The first three lead to a BYE, 200 OK, and To the originating S-CSCF. The BYE branch sends Int\_DP\_T\_Disconnect (legId=2) and DP\_T\_Disconnect\_2, then branches into Int\_Continue, Int\_Error, and Int\_ReleaseCall, which lead to a 200 OK and To the originating S-CSCF. + +Figure 4.29: Procedure CAMEL\_IMCN\_MT\_DISC1 (sheet 1) + +![Flowchart for Procedure CAMEL_IMCN_MT_DISC2. The process starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and ends. If 'Yes', it sends 'Int_DP_T_Disconnect' (legId=2) to the imcnSSF, then 'DP_T_Disconnect_2' to the S-CSCF. From the S-CSCF, it receives 'BYE', 'Int_Continue', 'Int_Release_Call', 'Int_error', or 'Int_Connect'. The 'BYE' path leads to 'Int_DP_T_Disconnect' (legId=1), then 'DP_T_Disconnect_1', then a choice of 'Int_Error', 'Int_Continue', or 'Int_Release_Call', which leads to '200 OK' and back to the S-CSCF. The 'Int_Continue' and 'Int_Release_Call' paths lead to a 'BYE' message to the S-CSCF. The 'Int_Connect' path leads to 'Modify call parameters with received information', 'Final_Response_Received := False', and 'Result := Reconnect'. All three paths ('200 OK', 'Result := Continue', and 'Result := Reconnect') lead to a final '200 OK' and the end connector.](c07e21a8d65991db04263322f859c94f_img.jpg) + +**Procedure CAMEL\_IMCN\_MT\_DISC2** 1(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` + +graph TD + Start(( )) --> Decision{imcnSSF invoked?} + Decision -- No --> ResultContinue1[Result := Continue] + ResultContinue1 --> End1(( )) + Decision -- Yes --> IntDP_T_Disconnect2[Int_DP_T_Disconnect +/* legId = 2 */] + IntDP_T_Disconnect2 --> DP_T_Disconnect2[DP_T_Disconnect_2] + DP_T_Disconnect2 --> BYE1[BYE] + DP_T_Disconnect2 --> Int_Continue1[Int_Continue] + DP_T_Disconnect2 --> Int_Release_Call1[Int_Release_Call] + DP_T_Disconnect2 --> Int_error1[Int_error] + DP_T_Disconnect2 --> Int_Connect1[Int_Connect] + BYE1 --> IntDP_T_Disconnect1[Int_DP_T_Disconnect +/* legId = 1 */] + IntDP_T_Disconnect1 --> DP_T_Disconnect1[DP_T_Disconnect_1] + DP_T_Disconnect1 --> Int_Error1[Int_Error] + DP_T_Disconnect1 --> Int_Continue2[Int_Continue] + DP_T_Disconnect1 --> Int_Release_Call2[Int_Release_Call] + Int_Error1 --> OK1[200 OK] + Int_Continue2 --> OK1 + Int_Release_Call2 --> OK1 + OK1 --> ToS-CSCF1[To the originating S-CSCF] + ToS-CSCF1 --> ResultContinue2[Result := Continue] + Int_Continue1 --> BYE2[BYE] + BYE2 --> ToS-CSCF2[To the originating S-CSCF] + Int_Connect1 --> Modify[Modify call parameters with received information] + Modify --> FinalResponse[Final_Response_Received := False] + FinalResponse --> ResultReconnect[Result := Reconnect] + ResultContinue2 --> OK2[200 OK] + ResultReconnect --> OK2 + OK2 --> End2(( )) + +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_DISC2. The process starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and ends. If 'Yes', it sends 'Int\_DP\_T\_Disconnect' (legId=2) to the imcnSSF, then 'DP\_T\_Disconnect\_2' to the S-CSCF. From the S-CSCF, it receives 'BYE', 'Int\_Continue', 'Int\_Release\_Call', 'Int\_error', or 'Int\_Connect'. The 'BYE' path leads to 'Int\_DP\_T\_Disconnect' (legId=1), then 'DP\_T\_Disconnect\_1', then a choice of 'Int\_Error', 'Int\_Continue', or 'Int\_Release\_Call', which leads to '200 OK' and back to the S-CSCF. The 'Int\_Continue' and 'Int\_Release\_Call' paths lead to a 'BYE' message to the S-CSCF. The 'Int\_Connect' path leads to 'Modify call parameters with received information', 'Final\_Response\_Received := False', and 'Result := Reconnect'. All three paths ('200 OK', 'Result := Continue', and 'Result := Reconnect') lead to a final '200 OK' and the end connector. + +Figure 4.30-1: Procedure CAMEL\_IMCN\_MT\_DISC2 (sheet 1) + +### Procedure CAMEL\_IMCN\_MT\_DISC2 + +2(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_DISC2. The flow starts with DP_T_Disconnect_2, followed by Int_Connect_To_Resource, then CAMEL_MT_CTR. A decision diamond asks 'Result = Fail?'. If 'No', it loops back to DP_T_Disconnect_2. If 'Yes', it goes to Result := Continue, which then leads to a connector symbol (circle with X).](beefc2239bc009e7b97963ac4f166db1_img.jpg) + +``` +graph TD; A[DP_T_Disconnect_2] --> B[Int_Connect_To_Resource]; B --> C[CAMEL_MT_CTR]; C --> D{Result = Fail?}; D -- No --> A; D -- Yes --> E[Result := Continue]; E --> F((X)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_DISC2. The flow starts with DP\_T\_Disconnect\_2, followed by Int\_Connect\_To\_Resource, then CAMEL\_MT\_CTR. A decision diamond asks 'Result = Fail?'. If 'No', it loops back to DP\_T\_Disconnect\_2. If 'Yes', it goes to Result := Continue, which then leads to a connector symbol (circle with X). + +Figure 4.30-2: Procedure CAMEL\_IMCN\_MT\_DISC2 (sheet 2) + +# Procedure CAMEL\_Start\_TNRy + +1(1) + +Procedure in IM-SSF to start the timer TNRy + +![Flowchart for Procedure CAMEL_Start_TNRy](2fc2e531b3b3c695cca497516ec79f20_img.jpg) + +``` +graph TD; Start([Start]) --> imcnSSF{imcnSSF invoked?}; imcnSSF -- No --> Join(( )); imcnSSF -- Yes --> DP6{DP6 or DP14 armed?}; DP6 -- No --> Join; DP6 -- Yes --> TNRyRec{TNRy received?}; TNRyRec -- Yes --> StartTNRy1[Start TNRy with received time value]; TNRyRec -- No --> DefaultVal{TNRy default value available?}; DefaultVal -- No --> Join; DefaultVal -- Yes --> StartTNRy2[Start TNRy with default value]; StartTNRy1 --> Join; StartTNRy2 --> Join; +``` + +The flowchart illustrates the procedure CAMEL\_Start\_TNRy. It begins with a start symbol leading to a decision diamond 'imcnSSF invoked?'. If 'No', it proceeds to a join symbol. If 'Yes', it proceeds to another decision diamond 'DP6 or DP14 armed?'. If 'No', it proceeds to the join symbol. If 'Yes', it proceeds to a decision diamond 'TNRy received?'. If 'Yes', it proceeds to a process box 'Start TNRy with received time value'. If 'No', it proceeds to a decision diamond 'TNRy default value available?'. If 'No', it proceeds to the join symbol. If 'Yes', it proceeds to a process box 'Start TNRy with default value'. Both process boxes lead to the join symbol. + +Flowchart for Procedure CAMEL\_Start\_TNRy + +Figure 4.31: Procedure CAMEL\_Start\_TNRy (sheet 1) + +![Flowchart for Procedure CAMEL_Stop_TNRy. It starts with a start symbol, followed by a decision 'imcnSSF invoked?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to another decision 'TNRy running?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to a process 'Stop TNRy', which then leads to an exit symbol.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +### Procedure CAMEL\_Stop\_TNRy + +1(1) + +Procedure in the IM-SSF +to stop the timer TNRy + +``` +graph TD; Start([ ]) --> D1{imcnSSF invoked?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{TNRy running?}; D2 -- No --> Exit2(( )); D2 -- Yes --> Process[Stop TNRy]; Process --> Exit3(( )); +``` + +Flowchart for Procedure CAMEL\_Stop\_TNRy. It starts with a start symbol, followed by a decision 'imcnSSF invoked?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to another decision 'TNRy running?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to a process 'Stop TNRy', which then leads to an exit symbol. + +Figure 4.32: Procedure CAMEL\_Stop\_TNRy (sheet 1) + +![Flowchart for Procedure CAMEL_MT_CTR (sheet 1). The process starts with a wait for PlayAnnc_or_Prompt_And_Collect_request. It then branches into three main paths: CAP_Play_Announcement, CAP_Prompt_And_Collect_User_Information, and Int_Disconnect_Forward_Connection. The first two paths lead to INVITE messages to MRFC, followed by a wait for 200_OK. The third path leads to a Result:=pass and an exit. Upon receiving 200_OK, the first path leads to ACK and Int_SRF_Connected, then Relay. The second path leads to Int_CTR_Failed and Result:=pass. The third path leads to BYE, 200_OK, Int_DP_T_Disconnect, BYE, Await_SRF_Disconnection_Active, and To MRFC. The fourth path leads to CANCEL, 200_OK, 487 Request Terminated, Int_DP_T_Abandon, DP_T_Abandon_DFC, Int_Continue, CANCEL, To MRFC, and Await_SRF_Disconnection_Fail.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +**Procedure CAMEL\_MT\_CTR** 1(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the originating party. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` + +graph TD + Start([Start]) --> Wait1[Wait_for_PlayAnnc_or_Prompt_And_Collect_request] + Wait1 --> CAP_Play_Announcement[CAP_Play_Announcement] + Wait1 --> CAP_Prompt_And_Collect_User_Information[CAP_Prompt_And_Collect_User_Information] + Wait1 --> Int_Disconnect_Forward_Connection[Int_Disconnect_Forward_Connection] + CAP_Play_Announcement --> INVITE1[INVITE] + INVITE1 --> ToMRFC1[To MRFC] + CAP_Prompt_And_Collect_User_Information --> INVITE2[INVITE] + INVITE2 --> ToMRFC2[To MRFC] + Int_Disconnect_Forward_Connection --> ResultPass1[Result:=pass] + ResultPass1 --> Exit1(( )) + INVITE1 --> Wait2[Wait_for_200_OK] + INVITE2 --> Wait2 + Wait2 --> FromMRFC1[From MRFC] + Wait2 --> FromMRFC2[From MRFC] + Wait2 --> BYE1[BYE] + Wait2 --> CANCEL1[CANCEL] + FromMRFC1 --> OK1[200 OK] + OK1 --> ACK[ACK] + ACK --> ToMRFC3[To MRFC] + ToMRFC3 --> Int_SRF_Connected[Int_SRF_Connected] + Int_SRF_Connected --> Relay[Relay] + FromMRFC2 --> ErrorResponse[Error response] + ErrorResponse --> Int_CTR_Failed[Int_CTR_Failed] + Int_CTR_Failed --> ResultPass2[Result:=pass] + ResultPass2 --> Exit2(( )) + BYE1 --> OK2[200 OK] + OK2 --> Int_DP_T_Disconnect[Int_DP_T_Disconnect +/* legID */] + Int_DP_T_Disconnect --> BYE2[BYE] + BYE2 --> Await_SRF_Disconnection_Active[Await_SRF_Disconnection_Active] + Await_SRF_Disconnection_Active --> ToMRFC4[To MRFC] + CANCEL1 --> OK3[200 OK] + OK3 --> RequestTerminated[487 Request Terminated] + RequestTerminated --> Int_DP_T_Abandon[Int_DP_T_Abandon +/* legID */] + Int_DP_T_Abandon --> DP_T_Abandon_DFC[DP_T_Abandon_DFC] + DP_T_Abandon_DFC --> Int_Continue[Int_Continue] + Int_Continue --> CANCEL2[CANCEL] + CANCEL2 --> ToMRFC5[To MRFC] + ToMRFC5 --> Await_SRF_Disconnection_Fail[Await_SRF_Disconnection_Fail] + +``` + +Flowchart for Procedure CAMEL\_MT\_CTR (sheet 1). The process starts with a wait for PlayAnnc\_or\_Prompt\_And\_Collect\_request. It then branches into three main paths: CAP\_Play\_Announcement, CAP\_Prompt\_And\_Collect\_User\_Information, and Int\_Disconnect\_Forward\_Connection. The first two paths lead to INVITE messages to MRFC, followed by a wait for 200\_OK. The third path leads to a Result:=pass and an exit. Upon receiving 200\_OK, the first path leads to ACK and Int\_SRF\_Connected, then Relay. The second path leads to Int\_CTR\_Failed and Result:=pass. The third path leads to BYE, 200\_OK, Int\_DP\_T\_Disconnect, BYE, Await\_SRF\_Disconnection\_Active, and To MRFC. The fourth path leads to CANCEL, 200\_OK, 487 Request Terminated, Int\_DP\_T\_Abandon, DP\_T\_Abandon\_DFC, Int\_Continue, CANCEL, To MRFC, and Await\_SRF\_Disconnection\_Fail. + +Figure 4.33-1: Procedure CAMEL\_MT\_CTR (sheet 1) + +![Flowchart for Procedure CAMEL_MT_CTR (sheet 2). The process starts with 'Relay', which branches into two main paths. The left path involves receiving a 'BYE' from MRFC, sending a '200 OK' to MRFC, releasing the internal SRF, and returning a 'Result:= pass'. The right path involves sending an 'Int_Disconnect_Forward_Connection' to MRFC, receiving a 'BYE' from MRFC, and then entering an 'Await_SRF_Disconnection_Continue' state. From this state, three outcomes are possible: 1) Receiving a 'BYE' from MRFC, sending a '200 OK' to MRFC, performing an 'Int_DP_T_Disconnect' (with a comment /* legID */), returning a 'Result:= pass'. 2) Receiving a 'CANCEL' from MRFC, sending a '200 OK' to MRFC, performing an 'Int_DP_T_Abandon' (with a comment /* legID */), encountering a 'DP_T_Abandon_Fail', continuing internally ('Int_continue'), and returning a 'Result:= fail'. 3) Receiving a '200 OK' from MRFC, releasing the internal SRF, and returning a 'Result:= pass'. All terminal states are marked with a circle containing an 'X'.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +### Procedure CAMEL\_MT\_CTR + +2(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the originating party. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` +graph TD; Relay([Relay]) --> BYE_L{BYE}; BYE_L --> From_MRFC_L[From MRFC]; BYE_L --> 200_OK_L{200 OK}; 200_OK_L --> To_MRFC_L[To MRFC]; 200_OK_L --> Int_SRF_Released_L[Int_SRF_Released]; Int_SRF_Released_L --> Result_Pass_L[Result:= pass]; Result_Pass_L --> End_L((X)); Relay --> Int_Disconnect_Forward_Connection[Int_Disconnect_Forward_Connection]; Int_Disconnect_Forward_Connection --> BYE_R{BYE}; BYE_R --> To_MRFC_R[To MRFC]; BYE_R --> Await_SRF_Disconnection_Continue[Await_SRF_Disconnection_Continue]; Await_SRF_Disconnection_Continue --> BYE_RR{BYE}; BYE_RR --> 200_OK_RR{200 OK}; 200_OK_RR --> Int_DP_T_Disconnect_RR["Int_DP_T_Disconnect +/* legID */"]; Int_DP_T_Disconnect_RR --> Result_Pass_RR[Result:= pass]; Result_Pass_RR --> End_RR((X)); Await_SRF_Disconnection_Continue --> CANCEL_RR{CANCEL}; CANCEL_RR --> 200_OK_RR2{200 OK}; 200_OK_RR2 --> Int_DP_T_Abandon_RR["Int_DP_T_Abandon +/* legID */"]; Int_DP_T_Abandon_RR --> DP_T_Abandon_Fail[DP_T_Abandon_Fail]; DP_T_Abandon_Fail --> Int_continue_RR[Int_continue]; Int_continue_RR --> Result_Fail_RR[Result:= fail]; Result_Fail_RR --> End_RR2((X)); Await_SRF_Disconnection_Continue --> 200_OK_RR3{200 OK}; 200_OK_RR3 --> From_MRFC_RR3[From MRFC]; 200_OK_RR3 --> Int_SRF_Released_RR3[Int_SRF_Released]; Int_SRF_Released_RR3 --> Result_Pass_RR3[Result:= pass]; Result_Pass_RR3 --> End_RR3((X)); +``` + +Flowchart for Procedure CAMEL\_MT\_CTR (sheet 2). The process starts with 'Relay', which branches into two main paths. The left path involves receiving a 'BYE' from MRFC, sending a '200 OK' to MRFC, releasing the internal SRF, and returning a 'Result:= pass'. The right path involves sending an 'Int\_Disconnect\_Forward\_Connection' to MRFC, receiving a 'BYE' from MRFC, and then entering an 'Await\_SRF\_Disconnection\_Continue' state. From this state, three outcomes are possible: 1) Receiving a 'BYE' from MRFC, sending a '200 OK' to MRFC, performing an 'Int\_DP\_T\_Disconnect' (with a comment /\* legID \*/), returning a 'Result:= pass'. 2) Receiving a 'CANCEL' from MRFC, sending a '200 OK' to MRFC, performing an 'Int\_DP\_T\_Abandon' (with a comment /\* legID \*/), encountering a 'DP\_T\_Abandon\_Fail', continuing internally ('Int\_continue'), and returning a 'Result:= fail'. 3) Receiving a '200 OK' from MRFC, releasing the internal SRF, and returning a 'Result:= pass'. All terminal states are marked with a circle containing an 'X'. + +Figure 4.33-2: Procedure CAMEL\_MT\_CTR (sheet 2) + +![Flowchart for Procedure CAMEL_MT_CTR. It starts with a relay and wait for PlayAnnc or Prompt And Collect request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int_DP_T_Disconnect, then Wait_For_Disconnect_Forward_Connection. The CANCEL path leads to 200 OK, then Int_DP_T_Abandon, then DP_T_Abandon_DFC, then Int_Continue, then Wait_For_Disconnect_Forward_Connection. The ACK path leads to a dash.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +### Procedure CAMEL\_MT\_CTR 3(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the originating party. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` +graph TD; Start([Relay, Wait_for_PlayAnnc_or_Prompt_And_Collect_request]) --> BYE{BYE}; Start --> CANCEL{CANCEL}; Start --> ACK{ACK}; BYE --> OK1{200 OK}; OK1 --> Disconnect[Int_DP_T_Disconnect /* legID */]; Disconnect --> Wait1[Wait_For_Disconnect_Forward_Connection]; CANCEL --> OK2{200 OK}; OK2 --> Abandon[Int_DP_T_Abandon /* legID */]; Abandon --> DFC[DP_T_Abandon_DFC]; DFC --> Continue[Int_Continue]; Continue --> Wait2[Wait_For_Disconnect_Forward_Connection]; ACK --> Dash[-]; +``` + +Flowchart for Procedure CAMEL\_MT\_CTR. It starts with a relay and wait for PlayAnnc or Prompt And Collect request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int\_DP\_T\_Disconnect, then Wait\_For\_Disconnect\_Forward\_Connection. The CANCEL path leads to 200 OK, then Int\_DP\_T\_Abandon, then DP\_T\_Abandon\_DFC, then Int\_Continue, then Wait\_For\_Disconnect\_Forward\_Connection. The ACK path leads to a dash. + +Figure 4.33-3: Procedure CAMEL\_MT\_CTR (sheet 3) + +### Procedure CAMEL\_MT\_CTR + +4(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the originating party. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +![Flowchart for Procedure CAMEL_MT_CTR](869c547c11ac7e123c51aba22289f2cd_img.jpg) + +``` +graph TD; Start([Wait_For_Disconnect_Forward_Connection]) --> Int_Disconnect[Int_Disconnect_Forward_Connection]; Int_Disconnect --> BYE{BYE}; BYE --> To_MRFC[To MRFC]; BYE --> Answer_Received{Answer Received?}; Answer_Received -- True --> Await_SRF_Active1([Await_SRF_Disconnection_Active]); Answer_Received -- False --> Await_SRF_Fail1([Await_SRF_Disconnection_Fail]); Await_SRF_Active1 --> OK1{200 OK}; From_MRFC1[From MRFC] --> OK1; OK1 --> Result_Pass[Result:= pass]; Result_Pass --> End1(( )); Await_SRF_Fail1 --> OK2{200 OK}; From_MRFC2[From MRFC] --> OK2; OK2 --> Result_Fail[Result:= fail]; Result_Fail --> End2(( )); +``` + +The flowchart illustrates the procedure CAMEL\_MT\_CTR. It begins with a start symbol 'Wait\_For\_Disconnect\_Forward\_Connection', followed by an internal disconnect action 'Int\_Disconnect\_Forward\_Connection'. A decision diamond 'BYE' follows, with one path leading to 'To MRFC' and the other to a decision 'Answer Received?'. If 'True', it leads to 'Await\_SRF\_Disconnection\_Active', then '200 OK' (receiving from MRFC), then 'Result:= pass', and finally an end symbol. If 'False', it leads to 'Await\_SRF\_Disconnection\_Fail', then '200 OK' (receiving from MRFC), then 'Result:= fail', and finally an end symbol. + +Flowchart for Procedure CAMEL\_MT\_CTR + +Figure 4.33-4: Procedure CAMEL\_MT\_CTR (sheet 4) + +![Sequence diagram for Procedure CAMEL_MT_CTR. It shows a 'Relay' node at the top branching into four parallel paths. Path 1: (Notification of PlayAnnc completed) -> CAP_Specialised ResourceReport. Path 2: (Return of Prompt & Collect Result) -> CAP_Prompt And Collect User_Information. Path 3: CAP_Play_Announcement -> (Play_Announcement). Path 4: CAP_Prompt_ And Collect_ User_Information -> (Prompt_ And Collect_ User_Information). All four paths converge to a single 'Relay' node at the bottom. A horizontal line labeled 'ack' is positioned between the top and bottom 'Relay' nodes.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +### Procedure CAMEL\_MT\_CTR + +5(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MRFC. Signals to/from the right are to/from the imcnSSF. + +``` +sequenceDiagram + participant MRFC + participant IM_SSF + Note left of MRFC: Procedure in the IM-SSF to handle a Connect To Resource operation. + Note right of IM_SSF: Signals to/from the left are to/from the MRFC. Signals to/from the right are to/from the imcnSSF. + + MRFC->>IM_SSF: CAP_Specialised ResourceReport + MRFC->>IM_SSF: CAP_Prompt And Collect User_Information + MRFC->>IM_SSF: CAP_Play_Announcement + MRFC->>IM_SSF: CAP_Prompt_ And Collect_ User_Information + + Note right of IM_SSF: (Notification of PlayAnnc completed) + Note right of IM_SSF: (Return of Prompt & Collect Result) + Note right of IM_SSF: (Play_Announcement) + Note right of IM_SSF: (Prompt_ And Collect_ User_Information) + + IM_SSF-->>MRFC: ack +``` + +Sequence diagram for Procedure CAMEL\_MT\_CTR. It shows a 'Relay' node at the top branching into four parallel paths. Path 1: (Notification of PlayAnnc completed) -> CAP\_Specialised ResourceReport. Path 2: (Return of Prompt & Collect Result) -> CAP\_Prompt And Collect User\_Information. Path 3: CAP\_Play\_Announcement -> (Play\_Announcement). Path 4: CAP\_Prompt\_ And Collect\_ User\_Information -> (Prompt\_ And Collect\_ User\_Information). All four paths converge to a single 'Relay' node at the bottom. A horizontal line labeled 'ack' is positioned between the top and bottom 'Relay' nodes. + +Figure 4.33-5: Procedure CAMEL\_MT\_CTR (sheet 5) + +#### 4.6.1.5 Handling of call in the imcnSSF + +Handling of mobile calls in the imcnSSF may involve the following process and procedures: + +- Process imcnSSF; + +Note that the following procedures are specified in 3GPP TS 23.078 Rel-99 [4]. For these procedures, the imcnSSF shall take the role of the gsmSSF. + +- Procedure Check\_Criteria\_Collected\_Info; +- Procedure Check\_Criteria\_Analysed\_Info; +- Procedure Check\_Criteria\_Unsuccessful; +- Procedure Connect\_To\_Resource; +- Procedure Handle\_AC; +- Procedure Handle\_ACR; +- Procedure Handle\_CIR; +- Procedure Handle\_CIR\_leg; +- Procedure Complete\_FCI\_record; +- Procedure Complete\_all\_FCI\_records; +- Procedure Handle\_O\_Answer; +- Procedure Handle\_T\_Answer. + +The detailed error handling for the process imcnSSF and the associated procedures is specified in 3GPP TS 29.278 [11]. + +##### 4.6.1.5.1 Process imcnSSF + +**Process imcnSSF** + +1(30) + +``` +/* Invocation of imcnSSF in MO, +MT call case. */ +``` + +``` +/* Timers used in the imcnSSF process: +``` + +``` +Tssf: Application timer in the ssf. +``` + +``` +Tcp: Timer for call period. +``` + +``` +This timer measures the duration of a call period. +``` + +``` +Tsw: Timer for tariff switch. +``` + +``` +At the expiration of this timer, a new tariff switch shall be started. +``` + +``` +Tw: Warning timer. +``` + +``` +At the expiration of this timer, a warning tone shall be played to the calling party. +``` + +``` +DELTA: time, measured in the imcnSSF, elapsed between the time an +``` + +``` +ApplyChargingReport operation is sent to the gsmSCF and an +``` + +``` +ApplyCharging operation is received from the gsmSCF. +``` + +``` +Tccd: Control of call duration timer. +``` + +``` +This timer supervises if after sending of ACR a new AC is received. +``` + +``` +Tccd has a value range of 1 to 20 seconds. +``` + +``` +Ranges for the default values for Tssf. +``` + +``` +- non user interaction Tssf timer value: 1 second to 20 seconds +``` + +``` +- user interaction Tssf timer value: 1 minute to 30 minutes +``` + +``` +*/ +``` + +``` +/* TASK definition: +``` + +``` +The sending of an Application_Begin signal opens a new relationship to the gsmSCF. +``` + +``` +The sending of an Application_End or Abort signal terminates the relationship to the gsmSCF. +``` + +``` +*/ +``` + +``` +/* Decision box definitions (1) +``` + +``` +'armed TDPs for this CSI?' +``` + +``` +It is questioned whether or not the ongoing call can encounter further TDPs which are indicated in the current CSI. +``` + +``` +'Call to be released?' +``` + +``` +It is questioned whether or not the ongoing call will be released immediately after imcnSSF has responded; that is the ongoing call will not send any signals further on to the imcnSSF. +NOTE: In this case the imcnSSF shall also go to idle. +``` + +``` +*/ +``` + +``` +/* Decision box definitions (2) +``` + +``` +The following decisions are used by procedures in CCF. +``` + +``` +'imcnSSF invoked?' +``` + +``` +Is the imcnSSF process in any state other than Idle? +``` + +``` +*/ +``` + +**Figure 4.34-1: Process imcnSSF (sheet 1)** + +![State transition diagram for Process imcnSSF. It starts at a Start_State, leading to an Idle state. From Idle, three parallel transitions for Int_Invoke imcnSSF (O-IM-CSI), (VT-IM-CSI), and (D-IM-CSI) lead to an Arm DP state, which then leads to Int_imcnSSF Invoked and Wait_For_Request. Another transition from Idle for Int_O_Exception, Int_T_Exception leads to another Idle state. A third transition from Idle leads to an Int_Continue state, which loops back to the Idle state.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +### Process imcnSSF + +2(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +The received CSI states whether DP Collected\_Info or DP Analysed\_Information or DP Route\_Select\_Failure or DP T\_Busy or DP T\_No\_Answer or DP Terminating\_Attempt\_Authorised shall be armed as TDP. + +Int\_DP\_O\_Answer, +Int\_DP\_T\_Answer, +Int\_DP\_O\_Abandon, +Int\_DP\_T\_Abandon, +Int\_DP\_Route\_Select\_Failure, +Int\_DP\_O\_No\_Answer, +Int\_DP\_T\_No\_Answer, +Int\_DP\_O\_Busy, +Int\_DP\_T\_Busy, +Int\_DP\_O\_Disconnect, +Int\_DP\_T\_Disconnect, +Int\_DP\_Analysed\_Info + +``` +stateDiagram-v2 + [*] --> Start_State + Start_State --> Idle + Idle --> Arm_DP : Int_Invoke imcnSSF (O-IM-CSI) + Idle --> Arm_DP : Int_Invoke imcnSSF (VT-IM-CSI) + Idle --> Arm_DP : Int_Invoke imcnSSF (D-IM-CSI) + Arm_DP --> Int_imcnSSF_Invoked : Arm DP + Int_imcnSSF_Invoked --> Wait_For_Request + Idle --> Idle : Int_O_Exception, Int_T_Exception + Idle --> Int_Continue + Int_Continue --> Idle +``` + +State transition diagram for Process imcnSSF. It starts at a Start\_State, leading to an Idle state. From Idle, three parallel transitions for Int\_Invoke imcnSSF (O-IM-CSI), (VT-IM-CSI), and (D-IM-CSI) lead to an Arm DP state, which then leads to Int\_imcnSSF Invoked and Wait\_For\_Request. Another transition from Idle for Int\_O\_Exception, Int\_T\_Exception leads to another Idle state. A third transition from Idle leads to an Int\_Continue state, which loops back to the Idle state. + +Figure 4.34-2: Process imcnSSF (sheet 2) + +![](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +## Process imcnSSF + +3(30) + +*/\* Invocation of imcnSSF in MO, +MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. \*/* + +``` + + graph TD + %% States and Inputs + Wait_For_Request([Wait_For_Request]) + Idle([Idle]) + + Input1[Int_DP_Route_Select_Failure, +Int_DP_T_Busy, +Int_DP_T_No_Answer] + Input2[Int_T_Exception, +Int_O_Exception] + Input3[Int_DP_O_Abandon, +Int_DP_T_Abandon, +Int_DP_O_Disconnect, +Int_DP_T_Disconnect, +Int_DP_O_Answer, +Int_DP_T_Answer, +Int_DP_O_Busy, +Int_DP_O_No_Answer] + + %% Flow 1: Terminating Attempt + Input1 --> DP_Term_Att[Int_DP_Terminating_Attempt_Authorized] + DP_Term_Att --> DP_Armed{DP_Terminating_Attempt_Authorized armed?} + DP_Armed --|No|--> Check_Unsuccess[Check_Criteria_Unsuccessful] + DP_Armed --|Yes|--> Check_Gap[Check_Gap_Criteria] + + Check_Unsuccess --> Result_Pass1{Result= pass?} + Result_Pass1 --|Yes|--> Check_Gap + Result_Pass1 --|No|--> Int_Cont1[Int_Continue] + Int_Cont1 --> Idle + + %% Flow 2: Collected Info + Wait_For_Request --> DP_Coll[Int_DP_Collected_Information] + DP_Coll --> Check_Coll[Check_Criteria_Collected_Info] + Check_Coll --> Result_Pass2{Result= pass?} + Result_Pass2 --|Yes|--> Armed_TDPs1{armed TDPs for this CSI?} + Result_Pass2 --|No|--> Int_Cont2[Int_Continue] + Int_Cont2 --> Idle + + Armed_TDPs1 --|Yes|--> Wait_For_Request + Armed_TDPs1 --|No|--> Idle + + %% Flow 3: Exception + Input2 --> Idle + + %% Flow 4: Analysed Info + Input3 --> DP_Analysed[Int_DP_Analysed_Information] + DP_Analysed --> Check_Analysed[Check_Criteria_Analysed_Info] + Check_Analysed --> Result_Pass3{Result= pass?} + Result_Pass3 --|No|--> Int_Cont3[Int_Continue] + Int_Cont3 --> Idle + Result_Pass3 --|Yes|--> Check_Gap2[Check_Gap_Criteria] + + Check_Gap2 --> Result_Pass4{Result= pass?} + Result_Pass4 --|No|--> Conn2((2)) + Result_Pass4 --|Yes|--> Conn2 + + %% Bottom Logic + Check_Gap --> Result_Pass5{Result= pass?} + Result_Pass5 --|Yes|--> Conn1((1)) + Result_Pass5 --|No|--> Def_Call{Default Call Handling = Continue Call?} + + Def_Call --|Yes|--> Int_Cont4[Int_Continue] + Def_Call --|No|--> Apply_Gap[Apply Gap treatment if present] + + Int_Cont4 --> Armed_TDPs2{armed TDPs for this CSI?} + Armed_TDPs2 --|Yes|--> Wait_For_Request + Armed_TDPs2 --|No|--> Idle + + Apply_Gap --> Int_Rel[Int_ReleaseCall] + Int_Rel --> Idle + +``` + +Gap treatment depends on the info received in the Call Gap message (i.e. tone/announce, cause, etc.) + +Figure 4.34-3: Process imcnSSF (sheet 3) + +![State transition diagram for Process imcnSSF. It consists of two parallel vertical flows labeled 1 and 2. Flow 1 starts with 'Set Tssf to default non user interaction Tssf timer interval and restart Tssf', followed by 'Application_Begin', 'Set Control Relationship', 'CAP_InitialDB', an empty box, and 'Waiting_for_Instructions'. Flow 2 starts with the same 'Set Tssf...' step, followed by 'Application_Begin', 'Set Control Relationship', 'CAP_InitialDB', and 'Waiting_for_Instructions_for_DS'. A horizontal line connects the empty box in Flow 1 to a box containing initialization variables: ACR sent:=false, AC pending:=false, Outstanding requests = 1, and Outstanding Call Information Report = 0.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +### Process imcnSSF 4(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; subgraph Flow1 [Flow 1]; S1((1)) --> T1['Set Tssf to default non user interaction Tssf timer interval and restart Tssf']; T1 --> A1{{Application_Begin}}; A1 --> C1['Set Control Relationship']; C1 --> I1{{CAP_InitialDB}}; I1 --> E1[ ]; E1 --> W1([Waiting_for_Instructions]); E1 --> V1[ACR sent:=false
AC pending:=false
Outstanding requests = 1
Outstanding Call Information Report = 0]; subgraph Flow2 [Flow 2]; S2((2)) --> T2['Set Tssf to default non user interaction Tssf timer interval and restart Tssf']; T2 --> A2{{Application_Begin}}; A2 --> C2['Set Control Relationship']; C2 --> I2{{CAP_InitialDB}}; I2 --> W2([Waiting_for_Instructions_for_DS]); end; +``` + +State transition diagram for Process imcnSSF. It consists of two parallel vertical flows labeled 1 and 2. Flow 1 starts with 'Set Tssf to default non user interaction Tssf timer interval and restart Tssf', followed by 'Application\_Begin', 'Set Control Relationship', 'CAP\_InitialDB', an empty box, and 'Waiting\_for\_Instructions'. Flow 2 starts with the same 'Set Tssf...' step, followed by 'Application\_Begin', 'Set Control Relationship', 'CAP\_InitialDB', and 'Waiting\_for\_Instructions\_for\_DS'. A horizontal line connects the empty box in Flow 1 to a box containing initialization variables: ACR sent:=false, AC pending:=false, Outstanding requests = 1, and Outstanding Call Information Report = 0. + +Figure 4.34-4: Process imcnSSF (sheet 4) + +![State transition diagram for Process imcnSSF. It starts at 'Waiting_for_Instructions', branches into 'CAP_Apply_Charging' and 'Timer expiry Tssf'. The 'CAP_Apply_Charging' path leads to 'Handle_AC', then 'Set Tssf to CAP_Reset_Timer time interval and restart Tssf', and back to 'Waiting_For_Instructions'. The 'Timer expiry Tssf' path leads to 'Internal', 'Abort', 'Int_Error', 'Complete_all_FCI_records', and then a decision 'Default call handling = continue call?'. If 'Yes', it goes to 'armed TDPs for this CSI?'. If 'Yes' there, it goes to 'Wait_For_Request'; if 'No', it goes to 'Idle'. If 'No' to the first decision, it also goes to 'Idle'.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +### Process imcnSSF 5(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_Instructions + Waiting_for_Instructions --> CAP_Apply_Charging + Waiting_for_Instructions --> Timer_expiry_Tssf + CAP_Apply_Charging --> Handle_AC + Handle_AC --> Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf + Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf --> Waiting_For_Instructions + Timer_expiry_Tssf --> Internal + Timer_expiry_Tssf --> Abort + Abort --> Int_Error + Int_Error --> Complete_all_FCI_records + Complete_all_FCI_records --> Default_call_handling_continue_call + Default_call_handling_continue_call --> armed_TDPs_for_this_CSI + Default_call_handling_continue_call --> Idle + armed_TDPs_for_this_CSI --> Wait_For_Request + armed_TDPs_for_this_CSI --> Idle +``` + +State transition diagram for Process imcnSSF. It starts at 'Waiting\_for\_Instructions', branches into 'CAP\_Apply\_Charging' and 'Timer expiry Tssf'. The 'CAP\_Apply\_Charging' path leads to 'Handle\_AC', then 'Set Tssf to CAP\_Reset\_Timer time interval and restart Tssf', and back to 'Waiting\_For\_Instructions'. The 'Timer expiry Tssf' path leads to 'Internal', 'Abort', 'Int\_Error', 'Complete\_all\_FCI\_records', and then a decision 'Default call handling = continue call?'. If 'Yes', it goes to 'armed TDPs for this CSI?'. If 'Yes' there, it goes to 'Wait\_For\_Request'; if 'No', it goes to 'Idle'. If 'No' to the first decision, it also goes to 'Idle'. + +Figure 4.34-5: Process imcnSSF (sheet 5) + +![Flowchart for Process imcnSSF. It starts with an initial node labeled 'Waiting_for_Instructions, Waiting_for_Instructions_for_DS'. This leads to a 'CAP_Reset_Timer' process block. Below that is a decision diamond with the condition ''Not Waiting for first response after IDP OR first reset Timer in this dialogue' ?'. The 'Yes' path leads to a 'Set Tssf to CAP_Reset_Timer time interval and restart Tssf' process block. The 'No' path bypasses this block. Both paths lead to a final node labeled '-'.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +### Process imcnSSF 6(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Start([Waiting_for_Instructions, Waiting_for_Instructions_for_DS]) --> CAP_Reset_Timer[CAP_Reset_Timer]; CAP_Reset_Timer --> Decision{''Not Waiting for first response after IDP OR first reset Timer in this dialogue' ?}; Decision -- Yes --> Set_Tssf[Set Tssf to CAP_Reset_Timer time interval and restart Tssf]; Decision -- No --> End([-]); Set_Tssf --> End; +``` + +Flowchart for Process imcnSSF. It starts with an initial node labeled 'Waiting\_for\_Instructions, Waiting\_for\_Instructions\_for\_DS'. This leads to a 'CAP\_Reset\_Timer' process block. Below that is a decision diamond with the condition ''Not Waiting for first response after IDP OR first reset Timer in this dialogue' ?'. The 'Yes' path leads to a 'Set Tssf to CAP\_Reset\_Timer time interval and restart Tssf' process block. The 'No' path bypasses this block. Both paths lead to a final node labeled '-'. + +Figure 4.34-6: Process imcnSSF (sheet 6) + +![](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +**Process imcnSSF** 7(30) + +*/\* Invocation of imcnSSF in MO, MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/* + +``` + + graph TD + Start([Waiting_for_Instructions]) --> CAP_Cont[CAP_Continue] + Start --> CAP_Cont_Arg[CAP_Continue_WithArgument] + Start --> CAP_Conn[CAP_Connect] + + CAP_Cont --> StopTssf1[Stop Tssf] + CAP_Cont_Arg --> StopTssf2[Stop Tssf] + CAP_Conn --> StopTssf3[Stop Tssf] + + StopTssf1 --> DP_Check1{Message was received due to DP of Leg ID} + StopTssf2 --> Int_Cont_Arg[Int_Continue_WithArgument] + StopTssf3 --> Leg1_Avail{Leg 1 is available} + + DP_Check1 -- "DP_O_No_answer of leg2 +DP_T_No_answer of leg2 +DP_O_Busy of leg2 +DP_T_Busy of leg2 +DP_Route_Select_Failure of leg2 +DP_O_Disconnect of leg2 +DP_T_Disconnect of leg2" --> CompFCI2[Complete_FCI_record (leg2)] + DP_Check1 -- "ELSE" --> CompFCI1[Complete_FCI_record (leg1)] + + CompFCI2 --> DP_Forward{DP was due to Call Forwarding} + CompFCI1 --> HandleCIR2[Handle_CIR_leg(leg2)] + HandleCIR2 --> DP_Forward + + DP_Forward -- "No" --> HandleCIR1[Handle_CIR_leg(leg1)] + DP_Forward -- "Yes" --> Join1 + HandleCIR1 --> Join1(( )) + + Join1 --> CurrDP{Current DP is O_Disconnect or T_Disconnect?} + CurrDP -- "Yes" --> DecrReq[Outstanding_Requests := Outstanding_Requests - 1] + CurrDP -- "No" --> IntCont1[Int_Continue] + + DecrReq --> ReqGT0{Outstanding_Requests > 0?} + ReqGT0 -- "Yes" --> SetTssf[Set Tssf to last used time interval and restart Tssf] --> Start + ReqGT0 -- "No" --> IntCont2[Int_Continue] + + IntCont1 --> Join2(( )) + IntCont2 --> Join2 + Int_Cont_Arg --> DP_Check2{Message was received due to DP of Leg ID} + DP_Check2 -- "ELSE" --> CompFCI2_2[Complete_FCI_record (leg2)] + DP_Check2 -- "DP_O_No_answer of leg2..." --> Join2 + CompFCI2_2 --> Join2 + + Join2 --> RemEDP{Any remaining armed EDP-Rs?} + RemEDP -- "Yes" --> Monitoring([Monitoring]) + RemEDP -- "No" --> OutReq0[Outstanding_Requests := 0] + + Leg1_Avail -- "Yes" --> IntConn[Int_Connect] + Leg1_Avail -- "No" --> IntCont3[Int_Continue] + IntConn --> Join3(( )) + IntCont3 --> Join3 + + Join3 --> AppEnd[Application_End] + AppEnd --> CompAllFCI[Complete_all_FCI_records] + CompAllFCI --> CallRel{Call to be released?} + CallRel -- "Yes" --> Idle([Idle]) + CallRel -- "No" --> ArmedTDP{armed TDPs for this CSI?} + ArmedTDP -- "No" --> Idle + ArmedTDP -- "Yes" --> WaitReq([Wait_For_Request]) + + OutReq0 --> RemEDP_Rep{Any remaining armed EDP or report pending?} + RemEDP_Rep -- "No" --> WaitReq + RemEDP_Rep -- "Yes" --> SetMon['Set Monitor Relationship'] --> WaitReq + +``` + +**DP\_O\_No\_answer of leg2** +**DP\_T\_No\_answer of leg2** +**DP\_O\_Busy of leg2** +**DP\_T\_Busy of leg2** +**DP\_Route\_Select\_Failure of leg2** +**DP\_O\_Disconnect of leg2** +**DP\_T\_Disconnect of leg2** + +**DP\_O\_Disconnect of leg1** +**DP\_T\_Disconnect of leg1** + +Figure 4.34-7: Process imcnSSF (sheet 7) + +![](c0ca823603794512478906b302176bca_img.jpg) + +## Process imcnSSF + +8(30) + +/\* Invocation of imcnSSF in MO, +MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. \*/ + +``` + + stateDiagram-v2 + state "Waiting_for_Instructions" as WFI + state "Waiting_For_Instructions" as WFI_Return + state "CAP_Request_ReportBCSM_Event" as ReqEvent + state "Set Tssf to last used time interval and restart Tssf" as SetTssf + state "Arming rules fulfilled?" as Rules <> + state "Arm EDP and/or disarm EDP" as ArmEDP + state "Error Unexpected Data Value" as ErrorVal + + state "CAP_ReleaseCall" as Release + state "AC pending?" as ACP1 <> + state "CallActive := FALSE" as CallActiveFalse + state "CAP_Apply_Charging_Report" as ApplyCharge1 + state "Handle_CIR" as Handle1 + state "Complete_all_FCI_records" as Complete1 + + state "Int_T_Exception,\nInt_O_Exception" as Exception + state "AC pending?" as ACP2 <> + state "CAP_Apply_Charging_Report" as ApplyCharge2 + state "Handle_CIR" as Handle2 + state "Complete_all_FCI_records" as Complete2 + state "Abort" as Abort + + state "Application_End" as AppEnd + state "Int_Release Call" as IntRelease + state "Stop Tssf" as StopTssf + state "Idle" as Idle + + [*] --> WFI + WFI --> ReqEvent + WFI --> Release + WFI --> Exception + + ReqEvent --> SetTssf + SetTssf --> Rules + Rules --> ArmEDP : Yes + Rules --> ErrorVal : No + ArmEDP --> WFI_Return + ErrorVal --> WFI_Return + + Release --> ACP1 + ACP1 --> CallActiveFalse : False + ACP1 --> ApplyCharge1 : True + CallActiveFalse --> ApplyCharge1 + ApplyCharge1 --> Handle1 + Handle1 --> Complete1 + Complete1 --> AppEnd + + Exception --> ACP2 + ACP2 --> ApplyCharge2 : False + ACP2 --> ApplyCharge2 : True + ApplyCharge2 --> Handle2 + Handle2 --> Complete2 + Complete2 --> Abort + Abort --> AppEnd + + AppEnd --> IntRelease + IntRelease --> StopTssf + StopTssf --> Idle + +``` + +Depending on the Monitoring parameter received for the indicated detection point. For DP O/T Disconnect a DP is only disarmed for the leg for which the event was received. + +Figure 4.34-8: Process imcnSSF (sheet 8) + +![Flowchart for Process imcnSSF. The sequence starts with 'Waiting_For_Instructions', followed by 'CAP_Cancel_(All)', 'Disarm all EDPs', 'Cancel all reports', 'Set Tssf to last used time interval and restart Tssf', and ends with 'Waiting_For_Instructions'.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +**Process imcnSSF** **9(30)** + +``` +/* Invocation of imcnSSF in MO, +MT call case. */ +``` + +``` +/* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. */ +``` + +``` +graph TD; A([Waiting_For_Instructions]) --> B[/CAP_Cancel_(All)/]; B --> C[Disarm all EDPs]; C --> D[Cancel all reports]; D --> E[Set Tssf to last used time interval and restart Tssf]; E --> F([Waiting_For_Instructions]); +``` + +Flowchart for Process imcnSSF. The sequence starts with 'Waiting\_For\_Instructions', followed by 'CAP\_Cancel\_(All)', 'Disarm all EDPs', 'Cancel all reports', 'Set Tssf to last used time interval and restart Tssf', and ends with 'Waiting\_For\_Instructions'. + +**Figure 4.34-9: Process imcnSSF (sheet 9)** + +![Flowchart for Process imcnSSF. The process starts with 'Waiting_for_Instructions', followed by 'CAP_ConnectToResource', 'Stop Tssf', and 'Connect_To_Resource'. A decision 'result' follows. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the imcnSCF', and back to 'Waiting_For_Instructions'. If 'pass', it goes to 'AC pending?'. If 'Yes', it goes to 'Start Tcp'. If 'No', it goes to 'Tw>0'. Both 'Start Tcp' and 'Tw>0' lead to 'Tw>0'. If 'Yes' to 'Tw>0', it goes to 'Start Tw'. Both 'Start Tw' and 'No' to 'Tw>0' lead to 'Set Tssf to user interaction timer value and restart Tssf', which then leads to 'Waiting_For_End_Of_User_Interaction'.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +**Process imcnSSF** 10(30) + +``` +/* Invocation of imcnSSF in MO, +MT call case. */ +``` + +``` +/* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. */ +``` + +``` +graph TD; A([Waiting_for_Instructions]) --> B[/CAP_ConnectToResource/]; B --> C[Stop Tssf]; C --> D[Connect_To_Resource]; D --> E{result}; E -- fail --> F[Set Tssf to last used time interval and restart Tssf]; F --> G[/Return appropriate error to the imcnSCF/]; G --> H([Waiting_For_Instructions]); E -- pass --> I{AC pending?}; I -- Yes --> J[Start Tcp]; I -- No --> K{Tw>0}; J --> K; K -- Yes --> L[Start Tw]; K -- No --> M[Set Tssf to user interaction timer value and restart Tssf]; L --> M; M --> N([Waiting_For_End_Of_User_Interaction]); +``` + +Flowchart for Process imcnSSF. The process starts with 'Waiting\_for\_Instructions', followed by 'CAP\_ConnectToResource', 'Stop Tssf', and 'Connect\_To\_Resource'. A decision 'result' follows. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the imcnSCF', and back to 'Waiting\_For\_Instructions'. If 'pass', it goes to 'AC pending?'. If 'Yes', it goes to 'Start Tcp'. If 'No', it goes to 'Tw>0'. Both 'Start Tcp' and 'Tw>0' lead to 'Tw>0'. If 'Yes' to 'Tw>0', it goes to 'Start Tw'. Both 'Start Tw' and 'No' to 'Tw>0' lead to 'Set Tssf to user interaction timer value and restart Tssf', which then leads to 'Waiting\_For\_End\_Of\_User\_Interaction'. + +Figure 4.34-10: Process imcnSSF (sheet 10) + +![Flowchart for Process imcnSSF. It starts in 'Monitoring' state, receives 'CAP_Request_Report_BCSM_Event', checks 'Arming rules fulfilled?'. If 'No', it goes to 'Error: Unexpected Data Value' then back to 'Monitoring'. If 'Yes', it performs 'Arm DP and/or disarm DP', then checks 'Any armed EDP or report pending'. If 'Yes', it goes back to 'Monitoring'. If 'No', it performs 'Complete_all_FCI_records', then 'Application_End', then checks ''armed TDPs for this CSI?'. If 'Yes', it goes to 'Wait_For_Request'. If 'No', it goes to 'Idle'. A note indicates that in 'Monitoring' state, only requests to disarm DPs or to sent notifications are allowed.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +### Process imcnSSF + +11(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Monitoring1([Monitoring]) --> Event[/CAP_Request_Report_BCSM_Event/]; Event --> Arming{Arming rules fulfilled?}; Arming -- No --> Error[/Error: Unexpected Data Value/]; Error --> Monitoring2([Monitoring]); Arming -- Yes --> Arm[Arm DP and/or disarm DP]; Arm --> Pending{Any armed EDP or report pending}; Pending -- Yes --> Monitoring3([Monitoring]); Pending -- No --> Complete[Complete_all_FCI_records]; Complete --> AppEnd[/Application_End/]; AppEnd --> Armed{''armed TDPs for this CSI?}; Armed -- Yes --> Wait[Wait_For_Request]; Armed -- No --> Idle[Idle]; +``` + +In state 'Monitoring', only requests to disarm DPs or to sent notifications are allowed + +Flowchart for Process imcnSSF. It starts in 'Monitoring' state, receives 'CAP\_Request\_Report\_BCSM\_Event', checks 'Arming rules fulfilled?'. If 'No', it goes to 'Error: Unexpected Data Value' then back to 'Monitoring'. If 'Yes', it performs 'Arm DP and/or disarm DP', then checks 'Any armed EDP or report pending'. If 'Yes', it goes back to 'Monitoring'. If 'No', it performs 'Complete\_all\_FCI\_records', then 'Application\_End', then checks ''armed TDPs for this CSI?'. If 'Yes', it goes to 'Wait\_For\_Request'. If 'No', it goes to 'Idle'. A note indicates that in 'Monitoring' state, only requests to disarm DPs or to sent notifications are allowed. + +Figure 4.34-11: Process imcnSSF (sheet 11) + +![Flowchart for Process imcnSSF (sheet 12). The process starts from an initial state, leading to four parallel signal inputs: Int_DP_O_Disconnect, Int_DP_T_Disconnect, Int_DP_O_Abandon, and Int_DP_T_Abandon. A decision diamond 'DP armed for legID?' follows. If 'No', it goes to 'Perform implicit disarming of DPs', then 'Stop Tssf', then 'Int_Continue', then 'Handle_ACR', 'Handle_CIR', 'Complete_all_FCI_records', 'Application_End', and finally 'Idle'. If 'Yes', it goes to another decision 'DP armed as EDP-R?'. If 'Yes' to this, it goes to 'Perform implicit disarming of DPs', 'Handle_ACR', 'Handle_CIR leg (legID)', 'CAP_Event_Report_BCSM (Interrupted)', 'Set Tssf to default non user interaction timer value and restart Tssf', 'Outstanding_Requests := Outstanding_Requests + 1', and finally 'Waiting_for_Instructions'. If 'No' to the second decision, it goes to 'Perform implicit disarming of DPs', then to a common path where 'CallActive := FALSE' is set, then to 'Set Tssf to default non user interaction timer value and restart Tssf', 'Outstanding_Requests := Outstanding_Requests + 1', and finally 'Waiting_for_Instructions'. A third path from the first decision leads to 'CAP_Event_Report_BCSM (Notify & Continue)', 'Handle_ACR', 'Handle_CIR', 'Stop Tssf', 'Int_Continue', 'Complete_all_FCI_records', 'Application_End', and 'Idle'. A note indicates that signals to/from the left are to/from the IM-SSF and to/from the right are to/from the gsmSCF.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +**Process imcnSSF** 12(30) + +*/\* Invocation of imcnSSF in MO, MT call case. \*/* + +*Waiting\_for\_Instructions, Monitoring, Waiting\_for\_End\_Of\_User\_Interaction* + +``` + +graph TD + Start([ ]) --> In1[Int_DP_O_Disconnect +/* legID */] + Start --> In2[Int_DP_T_Disconnect +/* legID */] + Start --> In3[Int_DP_O_Abandon] + Start --> In4[Int_DP_T_Abandon] + In1 --> D1{DP armed for legID?} + In2 --> D1 + In3 --> D1 + In4 --> D1 + D1 -- No --> P1[Perform implicit disarming of DPs] + P1 --> S1[Stop Tssf] + S1 --> I1{Int_Continue} + I1 --> H1[Handle_ACR] + H1 --> C1[Handle_CIR] + C1 --> F1[Complete_all_FCI_records] + F1 --> E1[Application_End] + E1 --> Idle1([Idle]) + D1 -- Yes --> D2{DP armed as EDP-R?} + D2 -- Yes --> P2[Perform implicit disarming of DPs] + P2 --> H2[Handle_ACR] + H2 --> C2[Handle_CIR leg (legID)] + C2 --> B2[CAP_Event_Report_BCSM (Interrupted)] + B2 --> T2[Set Tssf to default non user interaction timer value and restart Tssf] + T2 --> O2[Outstanding_Requests := Outstanding_Requests + 1] + O2 --> W2([Waiting_for_Instructions]) + D2 -- No --> P3[Perform implicit disarming of DPs] + P3 --> C3[CallActive := FALSE] + C3 --> T3[Set Tssf to default non user interaction timer value and restart Tssf] + T3 --> O3[Outstanding_Requests := Outstanding_Requests + 1] + O3 --> W3([Waiting_for_Instructions]) + D1 --> B1[CAP_Event_Report_BCSM (Notify & Continue)] + B1 --> H3[Handle_ACR] + H3 --> C3[Handle_CIR] + C3 --> S3[Stop Tssf] + S3 --> I3{Int_Continue} + I3 --> F3[Complete_all_FCI_records] + F3 --> E3[Application_End] + E3 --> Idle3([Idle]) + Note1[/* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. */] + +``` + +*/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/* + +Flowchart for Process imcnSSF (sheet 12). The process starts from an initial state, leading to four parallel signal inputs: Int\_DP\_O\_Disconnect, Int\_DP\_T\_Disconnect, Int\_DP\_O\_Abandon, and Int\_DP\_T\_Abandon. A decision diamond 'DP armed for legID?' follows. If 'No', it goes to 'Perform implicit disarming of DPs', then 'Stop Tssf', then 'Int\_Continue', then 'Handle\_ACR', 'Handle\_CIR', 'Complete\_all\_FCI\_records', 'Application\_End', and finally 'Idle'. If 'Yes', it goes to another decision 'DP armed as EDP-R?'. If 'Yes' to this, it goes to 'Perform implicit disarming of DPs', 'Handle\_ACR', 'Handle\_CIR leg (legID)', 'CAP\_Event\_Report\_BCSM (Interrupted)', 'Set Tssf to default non user interaction timer value and restart Tssf', 'Outstanding\_Requests := Outstanding\_Requests + 1', and finally 'Waiting\_for\_Instructions'. If 'No' to the second decision, it goes to 'Perform implicit disarming of DPs', then to a common path where 'CallActive := FALSE' is set, then to 'Set Tssf to default non user interaction timer value and restart Tssf', 'Outstanding\_Requests := Outstanding\_Requests + 1', and finally 'Waiting\_for\_Instructions'. A third path from the first decision leads to 'CAP\_Event\_Report\_BCSM (Notify & Continue)', 'Handle\_ACR', 'Handle\_CIR', 'Stop Tssf', 'Int\_Continue', 'Complete\_all\_FCI\_records', 'Application\_End', and 'Idle'. A note indicates that signals to/from the left are to/from the IM-SSF and to/from the right are to/from the gsmSCF. + +Figure 4.34-12: Process imcnSSF (sheet 12) + +![SDL diagram for Process imcnSSF sheet 13. It shows transitions from the state 'Waiting_for_End_Of_User_Interaction' based on various timers expiring (Tw, Tsw, Tcp, Tccd).](0b998e3ad8f9d104768642612605cb35_img.jpg) + +### Process imcnSSF + +13(30) + +/\* Invocation of imcnSSF in MO, +MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. \*/ + +``` + +stateDiagram-v2 + state "Waiting_for_End_Of_User_Interaction" as State1 + state "-" as DashState + state "Idle" as IdleState + + [*] --> State1 + State1 --> Tw_expired + State1 --> Tsw_expired + State1 --> Tcp_expired + State1 --> Tccd_expired + + Tw_expired --> Int_Apply_Warning_Tone + Int_Apply_Warning_Tone --> DashState + + Tsw_expired --> Store_curent_value_of_Tcp + Store_curent_value_of_Tcp --> DashState + + Tcp_expired --> Release_Decision + Release_Decision --> No: Release? + No --> Handle_ACR + Handle_ACR --> Set_Tssf + Set_Tssf --> Start_Tccd + Start_Tccd --> DashState + + Release_Decision --> Yes: Release? + Yes --> CAP_Apply_Charging_Report + CAP_Apply_Charging_Report --> Int_Disconnect_Forward_Connections + Int_Disconnect_Forward_Connections --> Handle_CIR + Handle_CIR --> Complete_all_FCI_record + Complete_all_FCI_record --> Int_Release + Int_Release --> Stop_Tssf + Stop_Tssf --> Application_End + Application_End --> IdleState + + note right of Start_Tccd : CallActive := TRUE + note left of IdleState : CallActive := FALSE;\n'CallReleasedAtTcpExpiry' present; + +``` + +**Tw expired** (Internal) + +**Int\_Apply\_Warning\_Tone** (Internal) + +*This provokes the IM-SSF to play a tone to the party for whom the BCSM is operating* + +**Tsw expired** + +Store curent value of Tcp + +**Tcp expired** (Internal) + +**Release?** + +- No** + - Handle\_ACR + - Set Tssf to last used time interval and restart Tssf + - Start Tccd + - CallActive := TRUE* +- Yes** + - CAP\_Apply\_Charging\_Report + - Int\_Disconnect\_Forward\_Connections + - Handle\_CIR + - Complete\_all\_FCI\_record + - Int\_Release + - Stop Tssf + - Application\_End + - Idle** + +**Tccd expired** (Internal) + +*CallActive := FALSE; 'CallReleasedAtTcpExpiry' present;* + +SDL diagram for Process imcnSSF sheet 13. It shows transitions from the state 'Waiting\_for\_End\_Of\_User\_Interaction' based on various timers expiring (Tw, Tsw, Tcp, Tccd). + +Figure 4.34-13: Process imcnSSF (sheet 13) + +![State transition diagram for Process imcnSSF. The process starts in 'Monitoring' state. Transitions are triggered by 'Tw expired', 'Tsw expired', 'Tcp expired', and 'Tccd expired'. 'Tw expired' leads to 'Int_Apply_Warning_Tone' (note: provokes IM-SSF to play a tone) and then to a merge point. 'Tsw expired' leads to 'Store current value of Tcp' and then to the same merge point. 'Tcp expired' leads to a 'Release?' decision. If 'Yes', it goes to 'CAP_Apply_Charging_Report', 'Handle_CIR', 'Complete_all_FCI_record', 'Int_Release', 'Application_End', and 'Idle'. If 'No', it checks 'Any EDP or reports outstanding?'. If 'Yes', it goes to 'Handle_ACR', 'Set Tssf to last used time interval and restart Tssf', 'Start Tccd', and then to the merge point. If 'No', it goes to 'CAP_Apply_Charging_Report', 'Complete_all_FCI_record', 'Application_End', and 'Idle'. A note indicates that after 'Start Tccd', 'CallActive := TRUE' and 'CallReleasedAtTcpExpiry' is present. The merge point leads to a state with a dash '-'.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +**Process imcnSSF** 14(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` + +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> Tw_expired: Tw expired + Monitoring --> Tsw_expired: Tsw expired + Monitoring --> Tcp_expired: Tcp expired + Monitoring --> Tccd_expired: Tccd expired + + Tw_expired --> Int_Apply_Warning_Tone + Int_Apply_Warning_Tone --> MergePoint + + Tsw_expired --> Store_current_value_of_Tcp: Store current value of Tcp + Store_current_value_of_Tcp --> MergePoint + + Tcp_expired --> Release_Q: Release? + Release_Q -- Yes --> CAP_Apply_Charging_Report_R + Release_Q -- No --> Any_EDP_outstanding_Q: 'Any EDP or reports outstanding?' + + Any_EDP_outstanding_Q -- Yes --> Handle_ACR + Handle_ACR --> Set_Tssf_to_last_used_time_interval_and_restart_Tssf: Set Tssf to last used time interval and restart Tssf + Set_Tssf_to_last_used_time_interval_and_restart_Tssf --> Start_Tccd: Start Tccd + Start_Tccd --> MergePoint + + Any_EDP_outstanding_Q -- No --> CAP_Apply_Charging_Report_L + CAP_Apply_Charging_Report_L --> Complete_all_FCI_record_L + Complete_all_FCI_record_L --> Application_End_L + Application_End_L --> Idle_L + + CAP_Apply_Charging_Report_R --> Handle_CIR + Handle_CIR --> Complete_all_FCI_record_R + Complete_all_FCI_record_R --> Int_Release + Int_Release --> Application_End_R + Application_End_R --> Idle_R + + MergePoint --> DashState: - + + Note right of DashState: CallActive := TRUE; 'CallReleasedAtTcpExpiry' present + +``` + +This provokes the IM-SSF to play a tone to the party for whom the BCSM is operating + +CallActive := TRUE; +'CallReleasedAtTcpExpiry' present + +State transition diagram for Process imcnSSF. The process starts in 'Monitoring' state. Transitions are triggered by 'Tw expired', 'Tsw expired', 'Tcp expired', and 'Tccd expired'. 'Tw expired' leads to 'Int\_Apply\_Warning\_Tone' (note: provokes IM-SSF to play a tone) and then to a merge point. 'Tsw expired' leads to 'Store current value of Tcp' and then to the same merge point. 'Tcp expired' leads to a 'Release?' decision. If 'Yes', it goes to 'CAP\_Apply\_Charging\_Report', 'Handle\_CIR', 'Complete\_all\_FCI\_record', 'Int\_Release', 'Application\_End', and 'Idle'. If 'No', it checks 'Any EDP or reports outstanding?'. If 'Yes', it goes to 'Handle\_ACR', 'Set Tssf to last used time interval and restart Tssf', 'Start Tccd', and then to the merge point. If 'No', it goes to 'CAP\_Apply\_Charging\_Report', 'Complete\_all\_FCI\_record', 'Application\_End', and 'Idle'. A note indicates that after 'Start Tccd', 'CallActive := TRUE' and 'CallReleasedAtTcpExpiry' is present. The merge point leads to a state with a dash '-'. + +Figure 4.34-14: Process imcnSSF (sheet 14) + +![State transition diagram for Process imcnSSF. The diagram shows various states and transitions between them, including CAP operations and timer handling.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +**Process imcnSSF** 15(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` + +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction + Waiting_for_End_Of_User_Interaction --> CAP_Apply_Charging + Waiting_for_End_Of_User_Interaction --> CAP_Disconnect_ForwardConnection + Waiting_for_End_Of_User_Interaction --> Int_SRF_Released + Waiting_for_End_Of_User_Interaction --> CAP_Reset_Timer + Waiting_for_End_Of_User_Interaction --> CAP_Play_Announcement + Waiting_for_End_Of_User_Interaction --> CAP_Prompt_and_Collect_User_Information + CAP_Prompt_and_Collect_User_Information --> CAP_Cancel_(Invoke_ID) + CAP_Cancel_(Invoke_ID) --> CAP_Play_Announcement + CAP_Play_Announcement --> To_SRF + CAP_Play_Announcement --> Relay_the_operation_to_the_SRF + Relay_the_operation_to_the_SRF --> Set_Tssf_to_last_used_time_interval_and_restart_Tssf + Set_Tssf_to_last_used_time_interval_and_restart_Tssf --> Waiting_for_End_Of_User_Interaction + CAP_Reset_Timer --> CallActive := FALSE + CallActive := FALSE --> Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf + Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf --> Waiting_for_End_Of_User_Interaction + Int_SRF_Released --> Handle_ACR + Handle_ACR --> Set_Tssf_to_default_on_user_interaction_time_interval_and_restart_Tssf + Set_Tssf_to_default_on_user_interaction_time_interval_and_restart_Tssf --> Waiting_For_Instructions + Waiting_For_Instructions --> Set_Tssf_to_default_on_user_interaction_time_interval_and_restart_Tssf + CAP_Disconnect_ForwardConnection --> Handle_ACR + Handle_ACR --> Int_Disconnect_Forward_Connection + Int_Disconnect_Forward_Connection --> Set_Tssf_to_default_on_user_interaction_time_interval_and_restart_Tssf + Set_Tssf_to_default_on_user_interaction_time_interval_and_restart_Tssf --> Waiting_For_Instructions + CAP_Apply_Charging --> Handle_AC + Handle_AC --> Set_Tssf_to_last_used_time_interval_and_restart_Tssf + Set_Tssf_to_last_used_time_interval_and_restart_Tssf --> Waiting_For_End_Of_User_Interaction + +``` + +**States:** + +- Waiting\_for\_End\_Of\_User\_Interaction +- Waiting\_For\_Instructions +- Waiting\_For\_End\_Of\_User\_Interaction + +**Transitions:** + +- CAP\_Apply\_Charging +- CAP\_Disconnect\_ForwardConnection +- Int\_SRF\_Released +- CAP\_Reset\_Timer +- CAP\_Play\_Announcement +- CAP\_Prompt\_and\_Collect\_User\_Information +- CAP\_Cancel\_(Invoke\_ID) +- To\_SRF +- Relay\_the\_operation\_to\_the\_SRF +- Set\_Tssf\_to\_last\_used\_time\_interval\_and\_restart\_Tssf +- CallActive := FALSE +- Set\_Tssf\_to\_CAP\_Reset\_Timer\_time\_interval\_and\_restart\_Tssf +- Handle\_ACR +- Set\_Tssf\_to\_default\_on\_user\_interaction\_time\_interval\_and\_restart\_Tssf +- Int\_Disconnect\_Forward\_Connection +- Handle\_AC + +State transition diagram for Process imcnSSF. The diagram shows various states and transitions between them, including CAP operations and timer handling. + +Figure 4.34-15: Process imcnSSF (sheet 15) + +![State transition diagram for Process imcnSSF. The process starts in 'Waiting for End_Of_User_Interaction'. It receives signals 'CAP_Cancelled_error' and 'CAP_Cancel_Failed_error' from SRF, which lead to 'Relay the operation/result/error to the gsmSCF'. It also receives 'CAP_Prompt & Collect_User_Information_Result' from SRF, which leads to 'Relay the operation/result/error to the gsmSCF'. From 'Relay the operation/result/error to the gsmSCF', it goes to another 'Waiting for End_Of_User_Interaction' state. From this state, it receives 'CAP_Specialised_Resource_Report' from SRF, which loops back to the first waiting state. It also receives an 'Internal' signal 'Timer expiry Tssf', which leads to 'Abort', then 'Int_Disconnect_Forward_Connection', then 'SRF_Release_Pending', and finally loops back to the first waiting state. From the second 'Waiting for End_Of_User_Interaction' state, it sends 'Int_SRF_Released' and 'Int_Error' signals. It then performs 'Complete_all_FCI_record'. A decision 'Default call handling = continue call?' follows. If 'No', it goes to 'Idle'. If 'Yes', it checks 'armed TDPs for this CSI?'. If 'No', it goes to 'Idle'. If 'Yes', it goes to 'Wait_For_Request'.](a5404b7275b06497eecf9b5883604753_img.jpg) + +### Process imcnSSF + +16(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the process Generic\_SRF; signals to/from the right are to/from the gsmSCF unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction_1 : Waiting for End_Of_User_Interaction + state "Waiting for End_Of_User_Interaction" as Waiting_for_End_Of_User_Interaction_1 + state "Waiting for End_Of_User_Interaction" as Waiting_for_End_Of_User_Interaction_2 + state "Relay the operation/result/error to the gsmSCF" as Relay + state "Abort" as Abort + state "Int_Disconnect_Forward_Connection" as Int_Disconnect_Forward_Connection + state "SRF_Release_Pending" as SRF_Release_Pending + state "Int_SRF_Released" as Int_SRF_Released + state "Int_Error" as Int_Error + state "Complete_all_FCI_record" as Complete_FCI + state "'Default call handling = continue call?'" as Default_Call_Handling + state "'armed TDPs for this CSI?'" as Armed_TDPs + state "Wait_For_Request" as Wait_For_Request + state "Idle" as Idle + + Waiting_for_End_Of_User_Interaction_1 --> CAP_Cancelled_error : From SRF + Waiting_for_End_Of_User_Interaction_1 --> CAP_Cancel_Failed_error : From SRF + Waiting_for_End_Of_User_Interaction_1 --> CAP_Prompt_Collect_User_Information_Result : From SRF + CAP_Cancelled_error --> Relay + CAP_Cancel_Failed_error --> Relay + CAP_Prompt_Collect_User_Information_Result --> Relay + Relay --> Waiting_for_End_Of_User_Interaction_2 + Waiting_for_End_Of_User_Interaction_2 --> CAP_Specialised_Resource_Report : From SRF + CAP_Specialised_Resource_Report --> Waiting_for_End_Of_User_Interaction_1 + Waiting_for_End_Of_User_Interaction_2 --> Internal : Internal + Internal --> Timer_expiry_Tssf : Timer expiry Tssf + Timer_expiry_Tssf --> Abort + Abort --> Int_Disconnect_Forward_Connection + Int_Disconnect_Forward_Connection --> SRF_Release_Pending + SRF_Release_Pending --> Waiting_for_End_Of_User_Interaction_1 + Waiting_for_End_Of_User_Interaction_2 --> Int_SRF_Released + Waiting_for_End_Of_User_Interaction_2 --> Int_Error + Int_SRF_Released --> Complete_FCI + Int_Error --> Complete_FCI + Complete_FCI --> Default_Call_Handling + Default_Call_Handling --> Idle : No + Default_Call_Handling --> Armed_TDPs : Yes + Armed_TDPs --> Idle : No + Armed_TDPs --> Wait_For_Request : Yes +``` + +State transition diagram for Process imcnSSF. The process starts in 'Waiting for End\_Of\_User\_Interaction'. It receives signals 'CAP\_Cancelled\_error' and 'CAP\_Cancel\_Failed\_error' from SRF, which lead to 'Relay the operation/result/error to the gsmSCF'. It also receives 'CAP\_Prompt & Collect\_User\_Information\_Result' from SRF, which leads to 'Relay the operation/result/error to the gsmSCF'. From 'Relay the operation/result/error to the gsmSCF', it goes to another 'Waiting for End\_Of\_User\_Interaction' state. From this state, it receives 'CAP\_Specialised\_Resource\_Report' from SRF, which loops back to the first waiting state. It also receives an 'Internal' signal 'Timer expiry Tssf', which leads to 'Abort', then 'Int\_Disconnect\_Forward\_Connection', then 'SRF\_Release\_Pending', and finally loops back to the first waiting state. From the second 'Waiting for End\_Of\_User\_Interaction' state, it sends 'Int\_SRF\_Released' and 'Int\_Error' signals. It then performs 'Complete\_all\_FCI\_record'. A decision 'Default call handling = continue call?' follows. If 'No', it goes to 'Idle'. If 'Yes', it checks 'armed TDPs for this CSI?'. If 'No', it goes to 'Idle'. If 'Yes', it goes to 'Wait\_For\_Request'. + +Figure 4.34-16: Process imcnSSF (sheet 16) + +![State transition diagram for Process imcnSSF. It starts at 'Monitoring' and branches based on 'CAP_Cancel_(All)', 'Int_DP_O_Answer', and 'Int_DP_T_Answer'. The 'CAP_Cancel_(All)' path leads to 'Disarm all EDPs', 'Cancel all reports', and then to a decision diamond. The 'Int_DP_O_Answer' and 'Int_DP_T_Answer' paths lead to 'Handle_O_Answer' and 'Handle_T_Answer' respectively, which both lead to a decision diamond 'DP armed for legID'. From 'DP armed for legID', the 'Yes' path leads to 'DP armed as EDP-R?'. If 'Yes', it goes to 'CAP_Event_Report_BCSM (Interrupted)', 'Disarm this DP; Perform implicit disarming of DPs.', 'Outstanding_Requests := 1', 'Set Tssf to default non user interaction Tssf timer value and restart Tssf', and 'Waiting_For_Instructions'. If 'No' from 'DP armed for legID', it leads to 'Perform implicit disarming of DPs.'. From 'DP armed as EDP-R?', the 'Yes' path leads to the same sequence as the 'Yes' from 'DP armed for legID'. The 'No' path leads to 'CAP_Event_Report_BCSM (Notify & Continue)', 'Disarm this DP; Perform implicit disarming of DPs.', and then to a decision diamond 'Any remaining armed EDPs or outstanding report?'. From 'Any remaining armed EDPs or outstanding report?', the 'Yes' path leads to 'Int_Continue' and 'Monitoring'. The 'No' path leads to 'Application_End', 'Complete_all_FCI_record', 'Int_Continue', and then to a decision diamond 'armed TDPs for this CSI?'. If 'Yes', it goes to 'Wait_For_Request'. If 'No', it goes to 'Idle'. A note indicates that for DP O/T, the DP is only disarmed for the leg for which the event was received.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +**Process imcnSSF** 17(30) + +*/\* Invocation of imcnSSF in MO, MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/* + +``` + +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> CAP_Cancel_(All) + Monitoring --> Int_DP_O_Answer + Monitoring --> Int_DP_T_Answer + CAP_Cancel_(All) --> Disarm_all_EDPs : Disarm all EDPs + Disarm_all_EDPs --> Cancel_all_reports : Cancel all reports + Cancel_all_reports --> Decision1{ } + Int_DP_O_Answer --> Handle_O_Answer : Handle_O_Answer + Int_DP_T_Answer --> Handle_T_Answer : Handle_T_Answer + Handle_O_Answer --> Decision2{DP armed for legID} + Handle_T_Answer --> Decision2 + Decision2 -- No --> Perform_implicit_disarming_of_DPs1 : Perform implicit disarming of DPs. + Decision2 -- Yes --> Decision3{DP armed as EDP-R?} + Decision3 -- Yes --> CAP_Event_Report_BCSM_Interrupted : CAP_Event_Report_BCSM (Interrupted) + CAP_Event_Report_BCSM_Interrupted --> Disarm_this_DP_Interrupted : Disarm this DP; Perform implicit disarming of DPs. + Disarm_this_DP_Interrupted --> Outstanding_Requests := 1 : Outstanding_Requests := 1 + Outstanding_Requests := 1 --> Set_Tssf : Set Tssf to default non user interaction Tssf timer value and restart Tssf + Set_Tssf --> Waiting_For_Instructions : Waiting_For_Instructions + Decision3 -- No --> CAP_Event_Report_BCSM_Notify_Continue : CAP_Event_Report_BCSM (Notify & Continue) + CAP_Event_Report_BCSM_Notify_Continue --> Disarm_this_DP_Notify_Continue : Disarm this DP; Perform implicit disarming of DPs. + Disarm_this_DP_Notify_Continue --> Decision4{Any remaining armed EDPs or outstanding report?} + Decision4 -- Yes --> Int_Continue1 : Int_Continue + Int_Continue1 --> Monitoring1 : Monitoring + Decision4 -- No --> Application_End : Application_End + Application_End --> Complete_all_FCI_record : Complete_all_FCI_record + Complete_all_FCI_record --> Int_Continue2 : Int_Continue + Int_Continue2 --> Decision5{armed TDPs for this CSI?} + Decision5 -- Yes --> Wait_For_Request : Wait_For_Request + Decision5 -- No --> Idle : Idle + Perform_implicit_disarming_of_DPs1 --> Decision4 + Disarm_this_DP_Interrupted --> Decision4 + Disarm_this_DP_Notify_Continue --> Decision4 + Note right of Perform_implicit_disarming_of_DPs1 : For DP O/T Disconnect the DP is only disarmed for the leg for which the event was received. + +``` + +State transition diagram for Process imcnSSF. It starts at 'Monitoring' and branches based on 'CAP\_Cancel\_(All)', 'Int\_DP\_O\_Answer', and 'Int\_DP\_T\_Answer'. The 'CAP\_Cancel\_(All)' path leads to 'Disarm all EDPs', 'Cancel all reports', and then to a decision diamond. The 'Int\_DP\_O\_Answer' and 'Int\_DP\_T\_Answer' paths lead to 'Handle\_O\_Answer' and 'Handle\_T\_Answer' respectively, which both lead to a decision diamond 'DP armed for legID'. From 'DP armed for legID', the 'Yes' path leads to 'DP armed as EDP-R?'. If 'Yes', it goes to 'CAP\_Event\_Report\_BCSM (Interrupted)', 'Disarm this DP; Perform implicit disarming of DPs.', 'Outstanding\_Requests := 1', 'Set Tssf to default non user interaction Tssf timer value and restart Tssf', and 'Waiting\_For\_Instructions'. If 'No' from 'DP armed for legID', it leads to 'Perform implicit disarming of DPs.'. From 'DP armed as EDP-R?', the 'Yes' path leads to the same sequence as the 'Yes' from 'DP armed for legID'. The 'No' path leads to 'CAP\_Event\_Report\_BCSM (Notify & Continue)', 'Disarm this DP; Perform implicit disarming of DPs.', and then to a decision diamond 'Any remaining armed EDPs or outstanding report?'. From 'Any remaining armed EDPs or outstanding report?', the 'Yes' path leads to 'Int\_Continue' and 'Monitoring'. The 'No' path leads to 'Application\_End', 'Complete\_all\_FCI\_record', 'Int\_Continue', and then to a decision diamond 'armed TDPs for this CSI?'. If 'Yes', it goes to 'Wait\_For\_Request'. If 'No', it goes to 'Idle'. A note indicates that for DP O/T, the DP is only disarmed for the leg for which the event was received. + +Figure 4.34-17: Process imcnSSF (sheet 17) + +![Flowchart for Process imcnSSF (sheet 18). The process starts in Monitoring, receives an event (Int_DP_O_No_Answer, etc.), and checks the EDP type. If EDP_N, it reports via CAP_Event_Report_BCSM (Notify & Continue), handles ACR, stops Delta, and performs implicit disarming of DPs. Then it checks if call forwarding is pending. If no, it handles CIR and completes all FCI records, ending in Idle. If yes, it handles CIR leg (leg2), checks for remaining armed EDPs, and if none, completes FCI record (leg2) and returns to Monitoring. If EDP_R, it handles ACR, stops Delta, handles CIR leg (leg2), reports via CAP_Event_Report_BCSM (Interrupted), disarms the DP, sets Outstanding_Requests to 1, resets Tssf timer, and goes to Waiting_For_Instructions. A note indicates signals to/from the left are to/from the IM-SSF, and to/from the right are to/from the gsmSCF. Another note states that for DP O/T Disconnect, the DP is only disarmed for the leg for which the event was received.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +**Process imcnSSF** 18(30) + +*/\* Invocation of imcnSSF in MO, MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/* + +Monitoring + +Int\_DP\_O\_No\_Answer, +Int\_DP\_T\_No\_Answer, +Int\_DP\_O\_Busy, +Int\_DP\_T\_Busy, +Int\_DP\_Route\_Select\_Failure + +EDP type? + +EDP\_N + +CAP\_Event\_Report\_BCSM (Notify & Continue) + +Handle\_ACR + +Stop Delta + +Perform implicit disarming of DPs. + +Not armed for LegID + +EDP\_R + +Handle\_ACR + +Stop Delta + +Handle\_CIR leg (leg2) + +CallActive := FALSE + +For DP O/T Disconnect the DP is only disarmed for the leg for which the event was received. + +CAP\_Event\_Report\_BCSM (Interrupted) + +Disarm this DP. Perform implicit disarming of DPs. + +Outstanding\_Requests := 1 + +Set Tssf to default non user interaction Tssf timer value and restart Tssf + +Waiting\_For\_Instructions + +Call Forwarding pending? + +No + +Handle\_CIR + +Yes + +Handle\_CIR leg (leg2) + +Complete\_all\_FCI\_records + +Any remaining armed EDPs or outstanding report? + +No + +Yes + +Complete\_FCI\_record (leg2) + +Application\_End + +Int\_Continue + +Idle + +Monitoring + +Flowchart for Process imcnSSF (sheet 18). The process starts in Monitoring, receives an event (Int\_DP\_O\_No\_Answer, etc.), and checks the EDP type. If EDP\_N, it reports via CAP\_Event\_Report\_BCSM (Notify & Continue), handles ACR, stops Delta, and performs implicit disarming of DPs. Then it checks if call forwarding is pending. If no, it handles CIR and completes all FCI records, ending in Idle. If yes, it handles CIR leg (leg2), checks for remaining armed EDPs, and if none, completes FCI record (leg2) and returns to Monitoring. If EDP\_R, it handles ACR, stops Delta, handles CIR leg (leg2), reports via CAP\_Event\_Report\_BCSM (Interrupted), disarms the DP, sets Outstanding\_Requests to 1, resets Tssf timer, and goes to Waiting\_For\_Instructions. A note indicates signals to/from the left are to/from the IM-SSF, and to/from the right are to/from the gsmSCF. Another note states that for DP O/T Disconnect, the DP is only disarmed for the leg for which the event was received. + +Figure 4.34-18: Process imcnSSF (sheet 18) + +![Flowchart for Process imcnSSF. It starts with 'Monitoring'. A horizontal line branches into three paths. The left path: CAP_ReleaseCall -> AC pending (True) -> CAP_Apply_Charging_Report -> Handle_CIR -> Complete_all_FCI_records -> Application_End -> Int_Release_Call -> Idle. The middle path: Handling of CAP_Release_Call (note: only specified in a control relationship) -> Int_O_Exception, Int_T_Exception -> AC pending (True) -> CAP_Apply_Charging_Report -> Handle_CIR -> Complete_all_FCI_records -> Abort -> Idle. A decision 'CallActive := FALSE' is shown near the middle path. The right path: CAP_Apply_Charging -> Handle_AC -> Monitoring.](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +### Process imcnSSF + +19(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Monitoring([Monitoring]) --> CAP_ReleaseCall{{CAP_ReleaseCall}}; Monitoring --> CAP_Apply_Charging{{CAP_Apply_Charging}}; CAP_ReleaseCall --> AC_pending_1{AC pending}; AC_pending_1 -- True --> CAP_Apply_Charging_Report_1{{CAP_Apply_Charging_Report}}; CAP_Apply_Charging_Report_1 --> Handle_CIR_1[Handle_CIR]; Handle_CIR_1 --> Complete_all_FCI_records_1[Complete_all_FCI_records]; Complete_all_FCI_records_1 --> Application_End{{Application_End}}; Application_End --> Int_Release_Call{{Int_Release_Call}}; Int_Release_Call --> Idle_1([Idle]); CAP_Apply_Charging --> Handle_AC[Handle_AC]; Handle_AC --> Monitoring_2([Monitoring]); CAP_ReleaseCall --> Note1[Handling of CAP_Release_Call is only specified in a control relationship. The gsmSCF shall not send a CAP_Release_Call in a monitor relationship]; Note1 --> Int_O_Exception[Int_O_Exception, Int_T_Exception]; Int_O_Exception --> AC_pending_2{AC pending}; AC_pending_2 -- True --> CAP_Apply_Charging_Report_2{{CAP_Apply_Charging_Report}}; CAP_Apply_Charging_Report_2 --> Handle_CIR_2[Handle_CIR]; Handle_CIR_2 --> Complete_all_FCI_records_2[Complete_all_FCI_records]; Complete_all_FCI_records_2 --> Abort{{Abort}}; Abort --> Idle_2([Idle]); CallActive[CallActive := FALSE] -.-> Int_O_Exception; +``` + +Flowchart for Process imcnSSF. It starts with 'Monitoring'. A horizontal line branches into three paths. The left path: CAP\_ReleaseCall -> AC pending (True) -> CAP\_Apply\_Charging\_Report -> Handle\_CIR -> Complete\_all\_FCI\_records -> Application\_End -> Int\_Release\_Call -> Idle. The middle path: Handling of CAP\_Release\_Call (note: only specified in a control relationship) -> Int\_O\_Exception, Int\_T\_Exception -> AC pending (True) -> CAP\_Apply\_Charging\_Report -> Handle\_CIR -> Complete\_all\_FCI\_records -> Abort -> Idle. A decision 'CallActive := FALSE' is shown near the middle path. The right path: CAP\_Apply\_Charging -> Handle\_AC -> Monitoring. + +Figure 4.34-19: Process imcnSSF (sheet 19) + +![Flowchart for Process imcnSSF. It starts with an initial state 'Waiting_For_Instructions, Waiting_For_End_Of_User_Interaction', followed by a CAP message 'CAP_Furnish_Charging_Information'. Then, 'Set Tssf to last used time interval and restart Tssf'. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'Yes', it goes to 'AppendFree FormatData in FCI?'. If 'No', it goes to 'Create CAMEL logical call record'. From 'AppendFree FormatData in FCI?', three paths emerge: 'Append' leads to 'Append free format data to existing logical call record', 'Not present, Overwrite' leads to 'Overwrite all CAMEL logical call record data with this FCI data', and an unlabeled path leads to 'Write FCI data in CAMEL logical call record'. All three paths merge at a final state marked with a cross and leading to a terminal state labeled '-'.](6e9d059430baba0c363e33749f68b107_img.jpg) + +**Process imcnSSF** 20(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Start([Waiting_For_Instructions, Waiting_For_End_Of_User_Interaction]) --> CAP{CAP_Furnish_Charging_Information}; CAP --> SetTssf[Set Tssf to last used time interval and restart Tssf]; SetTssf --> Decision1{Non-completed CAMEL logical call record exists for this legID?}; Decision1 -- Yes --> Decision2{AppendFree FormatData in FCI?}; Decision1 -- No --> CreateRecord[Create CAMEL logical call record]; Decision2 -- "Append" --> AppendData[Append free format data to existing logical call record]; Decision2 -- "Not present, Overwrite" --> OverwriteData[Overwrite all CAMEL logical call record data with this FCI data]; Decision2 --> WriteFCI[Write FCI data in CAMEL logical call record]; AppendData --> Merge(( )); OverwriteData --> Merge; WriteFCI --> Merge; Merge --> End([-]) +``` + +Flowchart for Process imcnSSF. It starts with an initial state 'Waiting\_For\_Instructions, Waiting\_For\_End\_Of\_User\_Interaction', followed by a CAP message 'CAP\_Furnish\_Charging\_Information'. Then, 'Set Tssf to last used time interval and restart Tssf'. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'Yes', it goes to 'AppendFree FormatData in FCI?'. If 'No', it goes to 'Create CAMEL logical call record'. From 'AppendFree FormatData in FCI?', three paths emerge: 'Append' leads to 'Append free format data to existing logical call record', 'Not present, Overwrite' leads to 'Overwrite all CAMEL logical call record data with this FCI data', and an unlabeled path leads to 'Write FCI data in CAMEL logical call record'. All three paths merge at a final state marked with a cross and leading to a terminal state labeled '-'. + +Figure 4.34-20: Process imcnSSF (sheet 20) + +![Flowchart for Process imcnSSF. It starts with 'Monitoring', followed by 'CAP_Furnish_Charging_Information'. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'No', it goes to 'Create CAMEL logical call record' then 'Write FCI data in CAMEL logical call record'. If 'Yes', it goes to another decision 'AppendFreeFormatData in FCI?'. From this second decision, 'Append' leads to 'Append free format data to existing logical call record', 'Not present, Overwrite' leads to 'Overwrite all CAMEL logical call record data with this FCI data', and an unlabeled path leads to the same 'Write FCI data in CAMEL logical call record' block. All three paths converge to a final 'Monitoring' state.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +### Process imcnSSF + +21(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Monitoring1([Monitoring]) --> CAP[CAP_Furnish_Charging_Information]; CAP --> D1{Non-completed CAMEL logical call record exists for this legID?}; D1 -- No --> Create[Create CAMEL logical call record]; Create --> Write[Write FCI data in CAMEL logical call record]; D1 -- Yes --> D2{AppendFreeFormatData in FCI?}; D2 -- "Append" --> Append[Append free format data to existing logical call record]; D2 -- "Not present, Overwrite" --> Overwrite[Overwrite all CAMEL logical call record data with this FCI data]; D2 --> Write; Append --> Write; Overwrite --> Write; Write --> Monitoring2([Monitoring]); +``` + +Flowchart for Process imcnSSF. It starts with 'Monitoring', followed by 'CAP\_Furnish\_Charging\_Information'. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'No', it goes to 'Create CAMEL logical call record' then 'Write FCI data in CAMEL logical call record'. If 'Yes', it goes to another decision 'AppendFreeFormatData in FCI?'. From this second decision, 'Append' leads to 'Append free format data to existing logical call record', 'Not present, Overwrite' leads to 'Overwrite all CAMEL logical call record data with this FCI data', and an unlabeled path leads to the same 'Write FCI data in CAMEL logical call record' block. All three paths converge to a final 'Monitoring' state. + +Figure 4.34-21: Process imcnSSF (sheet 21) + +![State transition diagram for Process imcnSSF. It starts at 'Waiting_For_Instructions', receives a 'CAP Call_Information_Request', sets Tssf, stores the request, increments the Outstanding Call Information Report, and returns to 'Waiting_For_Instructions'.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +### Process imcnSSF 22(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_For_Instructions + Waiting_For_Instructions --> CAP_Call_Information_Request : CAP Call_Information_Request + CAP_Call_Information_Request --> Set_Tssf : Set Tssf to last used time interval and restart Tssf + Set_Tssf --> store_request : store request + store_request --> Increment_Report : Outstanding Call Information Report := Outstanding Call Information Report + 1 + Increment_Report --> Waiting_For_Instructions +``` + +The diagram illustrates the state transitions for the imcnSSF process. It begins in the 'Waiting\_For\_Instructions' state, which is an initial state. Upon receiving a 'CAP Call\_Information\_Request', the process moves to a state where it 'Set Tssf to last used time interval and restart Tssf'. This is followed by a 'store request' state. From there, it transitions to a state where 'Outstanding Call Information Report := Outstanding Call Information Report + 1'. Finally, it returns to the 'Waiting\_For\_Instructions' state. + +State transition diagram for Process imcnSSF. It starts at 'Waiting\_For\_Instructions', receives a 'CAP Call\_Information\_Request', sets Tssf, stores the request, increments the Outstanding Call Information Report, and returns to 'Waiting\_For\_Instructions'. + +Figure 4.34-22: Process imcnSSF (sheet 22) + +![Sequence diagram for Process imcnSSF showing a vertical flow: Monitoring -> Int_DP_Analysed_Information -> Int_Continue -> Monitoring.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +**Process imcnSSF** **23(30)** + +*/\* Invocation of imcnSSF in MO, +MT call case. \*/* + +*/\* Signals to/from the left are +to/from the IM-SSF. \*/* + +``` +graph TD; A[Monitoring] --> B[Int_DP_Analysed_Information]; B --> C[Int_Continue]; C --> D[Monitoring]; +``` + +Sequence diagram for Process imcnSSF showing a vertical flow: Monitoring -> Int\_DP\_Analysed\_Information -> Int\_Continue -> Monitoring. + +**Figure 4.34-23: Process imcnSSF (sheet 23)** + +![State transition diagram for Process imcnSSF. The process starts in 'Waiting_for_Instructions_for_DS'. It branches based on incoming CAP messages: CAP_Furnish_Charging_Information, CAP_Continue_With_Argument, CAP_Continue, CAP_Connect, and CAP_ReleaseCall. CAP_Furnish_Charging_Information leads to 'Set Tssf to last used time interval and restart Tssf', which then checks if a CAMEL logical call record exists. If 'Yes', it returns to the initial waiting state. If 'No', it creates a CAMEL logical call record, writes FCI data, and returns to the initial waiting state. A note indicates that if a non-completed CAMEL logical call record exists for this legID, it should be overwritten. The other CAP messages (CAP_Continue_With_Argument, CAP_Continue, CAP_Connect, CAP_ReleaseCall) each lead to 'Stop Tssf', which then leads to internal signals (Int_Continue_With_Argument, Int_Continue, Int_Connect, Int_ReleaseCall). These internal signals lead to 'Application_End', which leads to 'Complete_all_FCI_Records' and finally 'Idle'.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +**Process imcnSSF** 24(30) + +``` +/* Invocation of imcnSSF in MO, +MT call case. */ +``` + +``` +/* Signals to/from the left are to/from the +IM-SSF; +signals to/from the right are +to/from the gsmSCF. */ +``` + +``` + +stateDiagram-v2 + [*] --> Waiting_for_Instructions_for_DS + Waiting_for_Instructions_for_DS --> CAP_Furnish_Charging_Information + Waiting_for_Instructions_for_DS --> CAP_Continue_With_Argument + Waiting_for_Instructions_for_DS --> CAP_Continue + Waiting_for_Instructions_for_DS --> CAP_Connect + Waiting_for_Instructions_for_DS --> CAP_ReleaseCall + + CAP_Furnish_Charging_Information --> Set_Tssf [Set Tssf to last used time interval and restart Tssf] + Set_Tssf --> CAMEL_Record_Exists {CAMEL logical call record exists?} + CAMEL_Record_Exists -- Yes --> Waiting_for_Instructions_for_DS + CAMEL_Record_Exists -- No --> Create_CAMEL_Record [Create CAMEL logical call record] + Create_CAMEL_Record --> Write_FCI_Data [Write FCI data in CAMEL logical call record] + Write_FCI_Data --> Overwrite_CAMEL_Record [Overwrite CAMEL logical call record with FCI data] + Overwrite_CAMEL_Record --> Waiting_for_Instructions_for_DS + + Note right of Overwrite_CAMEL_Record: Non-completed CAMEL logical call record exists for this legID? + + CAP_Continue_With_Argument --> Stop_Tssf_1 [Stop Tssf] + CAP_Continue --> Stop_Tssf_2 [Stop Tssf] + CAP_Connect --> Stop_Tssf_3 [Stop Tssf] + CAP_ReleaseCall --> Stop_Tssf_4 [Stop Tssf] + + Stop_Tssf_1 --> Int_Continue_With_Argument + Stop_Tssf_2 --> Int_Continue + Stop_Tssf_3 --> Int_Connect + Stop_Tssf_4 --> Int_ReleaseCall + + Int_Continue_With_Argument --> Application_End + Int_Continue --> Application_End + Int_Connect --> Application_End + Int_ReleaseCall --> Application_End + + Application_End --> Complete_FCI_Records [Complete_all_FCI_Records] + Complete_FCI_Records --> Idle + +``` + +State transition diagram for Process imcnSSF. The process starts in 'Waiting\_for\_Instructions\_for\_DS'. It branches based on incoming CAP messages: CAP\_Furnish\_Charging\_Information, CAP\_Continue\_With\_Argument, CAP\_Continue, CAP\_Connect, and CAP\_ReleaseCall. CAP\_Furnish\_Charging\_Information leads to 'Set Tssf to last used time interval and restart Tssf', which then checks if a CAMEL logical call record exists. If 'Yes', it returns to the initial waiting state. If 'No', it creates a CAMEL logical call record, writes FCI data, and returns to the initial waiting state. A note indicates that if a non-completed CAMEL logical call record exists for this legID, it should be overwritten. The other CAP messages (CAP\_Continue\_With\_Argument, CAP\_Continue, CAP\_Connect, CAP\_ReleaseCall) each lead to 'Stop Tssf', which then leads to internal signals (Int\_Continue\_With\_Argument, Int\_Continue, Int\_Connect, Int\_ReleaseCall). These internal signals lead to 'Application\_End', which leads to 'Complete\_all\_FCI\_Records' and finally 'Idle'. + +Figure 4.34-24: Process imcnSSF (sheet 24) + +![State transition diagram for Process imcnSSF. The process starts in 'Waiting_for_Instructions_For_DS'. It has two main branches: one for 'Internal' events leading to 'Timer expiry Tssf' and then 'Abort', and another for 'Int_DP_O Abandon' leading to 'Stop Tssf'. Both branches lead to 'Complete_all_FCI_records' and then to 'Idle' state. An 'Int_Error' state is also shown between 'Abort' and 'Complete_all_FCI_records'.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +### Process imcnSSF + +25(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_Instructions_For_DS + state "Waiting_for_Instructions_For_DS" as Waiting_for_Instructions_For_DS + state "Timer expiry Tssf" as Timer_expiry_Tssf + state "Int_DP_O Abandon" as Int_DP_O_Abandon + state "Abort" as Abort + state "Stop Tssf" as Stop_Tssf + state "Int_Error" as Int_Error + state "Complete_all_FCI_records" as Complete_all_FCI_records + state "Application_End" as Application_End + state "Idle" as Idle + + Waiting_for_Instructions_For_DS --> Timer_expiry_Tssf + Waiting_for_Instructions_For_DS --> Int_DP_O_Abandon + Timer_expiry_Tssf --> Abort + Int_DP_O_Abandon --> Stop_Tssf + Abort --> Int_Error + Int_Error --> Complete_all_FCI_records + Stop_Tssf --> Complete_all_FCI_records + Complete_all_FCI_records --> Application_End + Application_End --> Idle + Complete_all_FCI_records --> Idle +``` + +State transition diagram for Process imcnSSF. The process starts in 'Waiting\_for\_Instructions\_For\_DS'. It has two main branches: one for 'Internal' events leading to 'Timer expiry Tssf' and then 'Abort', and another for 'Int\_DP\_O Abandon' leading to 'Stop Tssf'. Both branches lead to 'Complete\_all\_FCI\_records' and then to 'Idle' state. An 'Int\_Error' state is also shown between 'Abort' and 'Complete\_all\_FCI\_records'. + +Figure 4.34-25: Process imcnSSF (sheet 25) + +![Flowchart for Process imcnSSF. The process starts with 'Waiting_for_Instructions_For_DS', followed by 'CAP_ConnectToResource', 'Stop Tssf', and 'Connect_To_Resource'. A 'result' decision diamond follows. If 'pass', it goes to 'Set Tssf to user interaction timer value and restart Tssf' and then 'Waiting_For_End_Of_User_Interaction_For_DS'. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the gsmSCF', and finally 'Waiting_For_Instructions_For_DS'.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +### Process imcnSSF 26(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; A[Waiting_for_Instructions_For_DS] --> B[/CAP_ConnectToResource/]; B --> C[Stop Tssf]; C --> D[Connect_To_Resource]; D --> E{result}; E -- pass --> F[Set Tssf to user interaction timer value and restart Tssf]; F --> G[Waiting_For_End_Of_User_Interaction_For_DS]; E -- fail --> H[Set Tssf to last used time interval and restart Tssf]; H --> I[/Return appropriate error to the gsmSCF/]; I --> J[Waiting_For_Instructions_For_DS]; +``` + +Flowchart for Process imcnSSF. The process starts with 'Waiting\_for\_Instructions\_For\_DS', followed by 'CAP\_ConnectToResource', 'Stop Tssf', and 'Connect\_To\_Resource'. A 'result' decision diamond follows. If 'pass', it goes to 'Set Tssf to user interaction timer value and restart Tssf' and then 'Waiting\_For\_End\_Of\_User\_Interaction\_For\_DS'. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the gsmSCF', and finally 'Waiting\_For\_Instructions\_For\_DS'. + +Figure 4.34-26: Process imcnSSF (sheet 26) + +![State transition diagram for Process imcnSSF. The sequence of states is: Waiting_for_End_Of_User_Interaction_For_DS (Initial state), Int_DP_O_Abandon, Stop Tssf, Complete_all_FCI_records, Application_End, and Idle (Final state). Transitions are vertical downward arrows between consecutive states.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +### Process imcnSSF + +27(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction_For_DS + Waiting_for_End_Of_User_Interaction_For_DS --> Int_DP_O_Abandon + Int_DP_O_Abandon --> Stop Tssf + Stop Tssf --> Complete_all_FCI_records + Complete_all_FCI_records --> Application_End + Application_End --> Idle +``` + +State transition diagram for Process imcnSSF. The sequence of states is: Waiting\_for\_End\_Of\_User\_Interaction\_For\_DS (Initial state), Int\_DP\_O\_Abandon, Stop Tssf, Complete\_all\_FCI\_records, Application\_End, and Idle (Final state). Transitions are vertical downward arrows between consecutive states. + +Figure 4.34-27: Process imcnSSF (sheet 27) + +![State transition diagram for Process imcnSSF. The diagram shows transitions between states 'Waiting_for_End_Of_User_Interaction_For_DS' and 'Waiting_For_Instructions_For_DS' based on various CAP and Int_SRF signals. Transitions include actions like 'Set Tssf to default non user interaction time interval and restart Tssf', 'Set Tssf to CAP_Reset_Timer time interval and restart Tssf', and 'Set Tssf to last used time interval and restart Tssf'. Some transitions involve relaying operations to the SRF.](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +### Process imcnSSF + +28(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction_For_DS + state "Waiting_for_End_Of_User_Interaction_For_DS" as Waiting_for_End_Of_User_Interaction_For_DS + state "Waiting_For_Instructions_For_DS" as Waiting_For_Instructions_For_DS + + Waiting_for_End_Of_User_Interaction_For_DS --> Waiting_For_Instructions_For_DS : CAP_Disconnect_ForwardConnection / Int_Disconnect_Forward_Connection; Set Tssf to default non user interaction time interval and restart Tssf + Waiting_for_End_Of_User_Interaction_For_DS --> Waiting_for_End_Of_User_Interaction_For_DS : Int_SRF_Released / Set Tssf to default non user interaction time interval and restart Tssf + Waiting_for_End_Of_User_Interaction_For_DS --> Waiting_for_End_Of_User_Interaction_For_DS : CAP_Reset_Timer / Set Tssf to CAP_Reset_Timer time interval and restart Tssf + Waiting_for_End_Of_User_Interaction_For_DS --> Waiting_for_End_Of_User_Interaction_For_DS : CAP_Play_Announcement + Waiting_for_End_Of_User_Interaction_For_DS --> Waiting_for_End_Of_User_Interaction_For_DS : CAP_Prompt_&Collect_User_Information / Relay the operation to the SRF; Set Tssf to last used time interval and restart Tssf + Waiting_for_End_Of_User_Interaction_For_DS --> Waiting_for_End_Of_User_Interaction_For_DS : CAP_Cancel_(Invoke_ID) + Waiting_for_End_Of_User_Interaction_For_DS --> Waiting_For_Instructions_For_DS : CAP_Cancel_(Invoke_ID) / Set Tssf to default non user interaction time interval and restart Tssf +``` + +State transition diagram for Process imcnSSF. The diagram shows transitions between states 'Waiting\_for\_End\_Of\_User\_Interaction\_For\_DS' and 'Waiting\_For\_Instructions\_For\_DS' based on various CAP and Int\_SRF signals. Transitions include actions like 'Set Tssf to default non user interaction time interval and restart Tssf', 'Set Tssf to CAP\_Reset\_Timer time interval and restart Tssf', and 'Set Tssf to last used time interval and restart Tssf'. Some transitions involve relaying operations to the SRF. + +Figure 4.34-28: Process imcnSSF (sheet 28) + +![State transition diagram for Process imcnSSF. It shows various states and transitions between them, including CAP messages, timer expiries, and internal operations.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +### Process imcnSSF 29(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the process Generic\_SRF; signals to/from the right are to/from the imcnSCF unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_End_Interaction_For_DS + Waiting_for_End_Interaction_For_DS --> CAP_Prompt_Collect_User_Information_Result + CAP_Prompt_Collect_User_Information_Result --> Waiting_for_End_Interaction_For_DS + CAP_Prompt_Collect_User_Information_Result --> CAP_Specialised_Resource_Report + CAP_Specialised_Resource_Report --> Waiting_for_End_Interaction_For_DS + CAP_Specialised_Resource_Report --> CAP_Cancel_Failed_error + CAP_Specialised_Resource_Report --> CAP_Cancelled_error + CAP_Cancel_Failed_error --> CAP_Prompt_Collect_User_Information_Result + CAP_Cancel_Failed_error --> CAP_Specialised_Resource_Report + CAP_Cancel_Failed_error --> CAP_Cancelled_error + CAP_Cancelled_error --> CAP_Prompt_Collect_User_Information_Result + CAP_Cancelled_error --> CAP_Specialised_Resource_Report + CAP_Cancelled_error --> CAP_Cancel_Failed_error + CAP_Cancelled_error --> Relay_the_operation_result_error_to_the_gsmSCF + CAP_Cancelled_error --> Waiting_for_End_Interaction_For_DS + CAP_Specialised_Resource_Report --> Timer_expiry_Tssf + Timer_expiry_Tssf --> Abort + Timer_expiry_Tssf --> Internal + Abort --> Int_Disconnect_Forward_Connection + Int_Disconnect_Forward_Connection --> SRF_Release_Pending_DS + SRF_Release_Pending_DS --> Int_SRF_Released + Int_SRF_Released --> Int_Error + Int_Error --> Complete_all_FCI_record + Complete_all_FCI_record --> Idle +``` + +**States:** + +- Waiting\_for\_End\_Interaction\_For\_DS +- CAP\_Prompt\_Collect\_User\_Information\_Result +- CAP\_Specialised\_Resource\_Report +- CAP\_Cancel\_Failed\_error +- CAP\_Cancelled\_error +- Relay\_the\_operation\_result\_error\_to\_the\_gsmSCF +- Timer\_expiry\_Tssf +- Abort +- Internal +- Int\_Disconnect\_Forward\_Connection +- SRF\_Release\_Pending\_DS +- Int\_SRF\_Released +- Int\_Error +- Complete\_all\_FCI\_record +- Idle + +**Transitions:** + +- from SRF to CAP\_Prompt\_Collect\_User\_Information\_Result +- from SRF to CAP\_Specialised\_Resource\_Report +- from SRF to CAP\_Cancel\_Failed\_error +- from SRF to CAP\_Cancelled\_error +- from CAP\_Prompt\_Collect\_User\_Information\_Result to Waiting\_for\_End\_Interaction\_For\_DS +- from CAP\_Specialised\_Resource\_Report to Waiting\_for\_End\_Interaction\_For\_DS +- from CAP\_Specialised\_Resource\_Report to CAP\_Cancel\_Failed\_error +- from CAP\_Specialised\_Resource\_Report to CAP\_Cancelled\_error +- from CAP\_Cancel\_Failed\_error to CAP\_Prompt\_Collect\_User\_Information\_Result +- from CAP\_Cancel\_Failed\_error to CAP\_Specialised\_Resource\_Report +- from CAP\_Cancel\_Failed\_error to CAP\_Cancelled\_error +- from CAP\_Cancelled\_error to CAP\_Prompt\_Collect\_User\_Information\_Result +- from CAP\_Cancelled\_error to CAP\_Specialised\_Resource\_Report +- from CAP\_Cancelled\_error to CAP\_Cancel\_Failed\_error +- from CAP\_Cancelled\_error to Relay\_the\_operation\_result\_error\_to\_the\_gsmSCF +- from CAP\_Cancelled\_error to Waiting\_for\_End\_Interaction\_For\_DS +- from CAP\_Specialised\_Resource\_Report to Timer\_expiry\_Tssf +- from Timer\_expiry\_Tssf to Abort +- from Timer\_expiry\_Tssf to Internal +- from Abort to Int\_Disconnect\_Forward\_Connection +- from Int\_Disconnect\_Forward\_Connection to SRF\_Release\_Pending\_DS +- from SRF\_Release\_Pending\_DS to Int\_SRF\_Released +- from Int\_SRF\_Released to Int\_Error +- from Int\_Error to Complete\_all\_FCI\_record +- from Complete\_all\_FCI\_record to Idle + +State transition diagram for Process imcnSSF. It shows various states and transitions between them, including CAP messages, timer expiries, and internal operations. + +Figure 4.34-29: Process imcnSSF (sheet 29) + +![State transition diagram for Process imcnSSF. It starts with an initial state labeled '*(Idle, Wait_For_Request)'. A transition arrow points down to a state labeled 'CAP_CallGap'. From 'CAP_CallGap', a transition arrow points down to a state labeled 'Int_CallGap'. From 'Int_CallGap', a transition arrow points down to a state labeled '-'. A note box to the right of the 'Int_CallGap' state contains the text 'to a new imcn_SSME_SSF process'.](72d448a65347c51989171748789c7d4b_img.jpg) + +### Process imcnSSF + +30(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Idle + state "*(Idle, Wait_For_Request)" as Idle + Idle --> CAP_CallGap + state "CAP_CallGap" as CAP_CallGap + CAP_CallGap --> Int_CallGap + state "Int_CallGap" as Int_CallGap + Int_CallGap --> End + state "-" as End + note right of Int_CallGap: to a new imcn_SSME_SSF process +``` + +State transition diagram for Process imcnSSF. It starts with an initial state labeled '\*(Idle, Wait\_For\_Request)'. A transition arrow points down to a state labeled 'CAP\_CallGap'. From 'CAP\_CallGap', a transition arrow points down to a state labeled 'Int\_CallGap'. From 'Int\_CallGap', a transition arrow points down to a state labeled '-'. A note box to the right of the 'Int\_CallGap' state contains the text 'to a new imcn\_SSME\_SSF process'. + +Figure 4.34-30: Process imcnSSF (sheet 30) + +#### 4.6.1.6 Process imcn\_SSME\_SSF and procedures + +One process is instantiated at the IM-SSF for each Call Gap message received from a gsmSCF. + +This subclause contains the SDL process for IM-SSF handling of the CallGap operation received from a gsmSCF. + +The following Call Gap procedures specified in 3GPP TS 23.078 Rel-99 [4] shall also be applicable for IM-SSF. The IM-SSF shall take the role of the gsmSSF in the following: + +- Procedure Store\_Call\_Gap\_Criteria; +- Procedure Check\_Gap\_Criteria. + +![Flowchart for Process imcn_SSME_SSF. The process starts at an unlabeled oval, goes to 'Idle', then 'Int_CallGap'. A decision diamond asks 'Gap context with same criteria and gsmSCF address (if available) already exists ?'. If 'Yes', it goes to 'Remove CallGap' then 'To imcn_SSME_SSF process that handles the old Call Gapping context'. If 'No', it goes to 'Store_Call_Gap_Criteria', then a decision diamond 'Result = pass?'. If 'Yes', it goes to 'Active'. If 'No', it goes to 'Idle'.](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +**Process imcn\_SSME\_SSF** 1(2) + +IM-SSF handling of SCF requests for Call Gapping. + +/\* Signals to/from the left are to/from the imcnSSF ; signals to/from the right are to/from internal processes \*/ + +/\* Timers used in the imcnSSF process: +Tcgd : Timer for call gapping duration (set with the Gap duration parameter) +Tcgi : Timer for call gapping interval (set with the Gap interval parameter) +\*/ + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Int_CallGap[/Int_CallGap/]; Int_CallGap --> Decision1{Gap context with same criteria and gsmSCF address (if available) already exists ?}; Decision1 -- Yes --> RemoveCallGap{{Remove CallGap}}; RemoveCallGap --> ToImcnSSF[To imcn_SSME_SSF process that handles the old Call Gapping context]; ToImcnSSF --> StoreCallGapCriteria[Store_Call_Gap_Criteria]; Decision1 -- No --> StoreCallGapCriteria; StoreCallGapCriteria --> Decision2{Result = pass?}; Decision2 -- Yes --> Active([Active]); Decision2 -- No --> Idle2([Idle]); +``` + +Flowchart for Process imcn\_SSME\_SSF. The process starts at an unlabeled oval, goes to 'Idle', then 'Int\_CallGap'. A decision diamond asks 'Gap context with same criteria and gsmSCF address (if available) already exists ?'. If 'Yes', it goes to 'Remove CallGap' then 'To imcn\_SSME\_SSF process that handles the old Call Gapping context'. If 'No', it goes to 'Store\_Call\_Gap\_Criteria', then a decision diamond 'Result = pass?'. If 'Yes', it goes to 'Active'. If 'No', it goes to 'Idle'. + +Figure 4.35-1: Process imcn\_SSME\_SSF (sheet 1) + +![State transition diagram for Process imcn_SSME_SSF. It starts at an 'Active' state. Transitions include: 1) 'Tcgi expiry' leads to 'CG Reject := False' which loops back to 'Active'. 2) 'Trigger Tcgi' leads to 'Start Tcgi' then 'CG Reject := True' which loops back to 'Active'. 3) 'Tcgd expiry' leads to 'Clear Call Gapping Context (i.e. remove timers and criteria)' which leads to an 'Idle' state. 4) 'Remove CallGap' is a self-loop on the 'Active' state. A note indicates that the Tcgi timer is started for the first time after the first call encountering the call gapping criteria is met.](b13465efdac63129aef9b6f1787d0d00_img.jpg) + +### Process imcn\_SSME\_SSF 2(2) + +IM-SSF handling of SCF requests for Call Gapping. + +/\* Signals to/from the left are to/from the imcnSSF ; signals to/from the right are to/from internal processes \*/ + +``` +stateDiagram-v2 + [*] --> Active + state "Active" as Active + state "Idle" as Idle + Active --> Tcgi_expiry : Tcgi expiry + Tcgi_expiry --> CGRejectFalse : CG Reject := False + CGRejectFalse --> Active + Active --> TriggerTcgi : Trigger Tcgi + TriggerTcgi --> StartTcgi : Start Tcgi + StartTcgi --> CGRejectTrue : CG Reject := True + CGRejectTrue --> Active + Active --> Tcgd_expiry : Tcgd expiry + Tcgd_expiry --> ClearCallGappingContext : Clear Call Gapping Context (i.e. remove timers and criteria) + ClearCallGappingContext --> Idle + Active --> RemoveCallGap : Remove CallGap + RemoveCallGap --> Active +``` + +NOTE: The timer Tcgi is started for the first time after the first call encountering the call gapping criteria is met. + +State transition diagram for Process imcn\_SSME\_SSF. It starts at an 'Active' state. Transitions include: 1) 'Tcgi expiry' leads to 'CG Reject := False' which loops back to 'Active'. 2) 'Trigger Tcgi' leads to 'Start Tcgi' then 'CG Reject := True' which loops back to 'Active'. 3) 'Tcgd expiry' leads to 'Clear Call Gapping Context (i.e. remove timers and criteria)' which leads to an 'Idle' state. 4) 'Remove CallGap' is a self-loop on the 'Active' state. A note indicates that the Tcgi timer is started for the first time after the first call encountering the call gapping criteria is met. + +Figure 4.35-2: Process imcn\_SSME\_SSF (sheet 2) + +## 4.7 Descriptions of information Flows + +This clause contains the detailed description of the information flows used by CAMEL for IP Multimedia Subsystems call control. + +Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Specific conditions (S), mutually Exclusive (E), Optional (O) or not applicable (-) for each different traffic case: IP Multimedia Origination (IM\_Orig), IP Multimedia Termination (IM\_Term). The distinction between IM\_Orig and IM\_Term calls is not applicable to all Information Flows. + +An 'M' IE shall always be included for the corresponding traffic case. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. When a set of 'E' IEs is shown in the definition of an Information Flow or compound IE, only one of those IEs may be included. An 'O' IE may be included or omitted as required by the service logic. A '-' IE shall always be omitted for the corresponding traffic case. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol. + +Details of errors and exceptions to these rules are specified in 3GPP TS 29.278 [11]. + +### 4.7.1 IM-SSF to gsmSCF information flows + +#### 4.7.1.1 Activity Test ack + +##### 4.7.1.1.1 Description + +This IF is the response to the Activity Test. + +##### 4.7.1.1.2 Information Elements + +This IF contains no information elements. + +#### 4.7.1.2 Apply Charging Report + +##### 4.7.1.2.1 Description + +This IF is used by the IM-SSF to report to the gsmSCF the information requested in the Apply Charging IF. + +##### 4.7.1.2.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------| +| Call Result | M | This IE contains the charging information to be provided by the IM-SSF. | + +Call Result contains the following information: + +| Information element name | Status | Description | +|-------------------------------|--------|----------------------------------------------| +| Time Duration Charging Result | M | This IE is a list defined in the next table. | + +Time Duration Charging Result contains the following information: + +| Information element name | Status | Description | +|-----------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Time Information | M | This IE is a choice between Time if No Tariff Switch and Time if Tariff Switch. This IE is described in the next table. | +| Party To Charge | M | This IE is received in the related ApplyCharging operation to correlate the result to the request. This IE shall be a copy of the corresponding IE received in the Apply Charging operation. | +| Call Active | M | This IE indicates whether the call is active or not. | +| Call Released at Tcp Expiry | C | This element is an indication that the IM-SSF has released the call and terminated the dialogue, due to Tcp expiry.
It shall be present when ACR is sent due to Tcp expiry and the IM-SSF has released the call (because "ReleaseIfExceeded" was present in ACH operation).
In all other circumstances, this element shall be absent. | + +Time Information contains one of the following information: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Time If No Tariff Switch | C | This IE will be present if no tariff switch has occurred since the reception of the first Apply Charging IF for the connection to the Called Party or the MRFC connection, otherwise it will be absent.
If Answer was detected for the connection to the Called Party or the MRFC connection, then the elapsed time since detection of Answer shall be reported.
If answer was not detected, it shall be set to "0". | +| Time If Tariff Switch | C | This IE will be present if a tariff switch has occurred since the reception of the first Apply Charging IF for the connection to the Called Party or the MRFC connection, otherwise it will be absent. | + +## 4.7.1.3 Call Gap + +### 4.7.1.3.1 Description + +This IF is used to activate/modify/remove a call gap mechanism in the IM-SSF. The call gap mechanism is used to reduce the rate at which specific service requests are sent to a gsmSCF. + +A Call Gap operation can only be sent on an opened dialogue between a gsmSCF and the IM-SSF. + +It is possible to have several call gapping conditions applicable to the same IM-SSF (i.e. each conditions were activated for a defined Service (identified by the serviceKey) by a defined gsmSCF (identified by the gsmSCFAddress)). + +### 4.7.1.3.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Gap Criteria | M | This IE specifies the criteria for a call to be subject to call gapping. | +| Gap Indicators | M | This parameter indicates the gapping characteristics. | +| Control Type | O | This parameter indicates the reason for activating call gapping.
The value "sCPOverloaded" indicates that an automatic congestion detection and control mechanism in the SCP has detected a congestion situation.
The value "manuallyInitiated" indicates that the service and or network/service management centre has detected a congestion situation, or any other situation that requires manually initiated controls.
The controlType "manuallyInitiated" will have priority over "sCPOverloaded" call gap. | +| Gap Treatment | O | This parameter indicates how calls that were rejected due to the call gapping condition and for which the Default Call Handling was set to "Release Call" shall be treated. | +| M | Mandatory (The IE shall always be sent). | | +| O | Optional (Service logic dependent). | | + +Gap Criteria contains one of the following (Choice): + +| Information element name | Status | Description | +|--------------------------|-------------------------------------|-------------------------------------------------------------| +| Basic Gap Criteria | O | This IE is a choice of various basic criteria. | +| Compound Gap Criteria | O | This IE is a choice of various criteria including an ScfID. | +| O | Optional (Service logic dependent). | | + +Compound Gap Criteria contains the following Information: + +| Information element name | Status | Description | +|--------------------------|------------------------------------------|-----------------------------------------------------------------------------| +| Basic Gap Criteria | M | This IE is a choice of various criteria. | +| ScfID | O | This IE contains the address of the gsmSCF which initiated the CallGapping. | +| M | Mandatory (The IE shall always be sent). | | +| O | Optional (Service logic dependent). | | + +Basic Gap Criteria contains one of the following (Choice): + +| Information element name | Status | Description | +|---------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Called Address | O | This parameter contains a string of digits. At each call attempt, when the leading digits of the dialled number match this specific value, the call gapping treatment shall be applied to this call. | +| Service | O | This parameter contains a service key value. At each call attempt, when the service key matches this specific value, the call gapping treatment shall be applied to this call. | +| Called Address and Service | O | This parameter contains a specific string of digits and a service key value. At each call attempt, when the leading digits of the dialled number and the service key of a call match these specific values, the call gapping treatment shall be applied to this call. | +| Calling Address and Service | O | This parameter contains a specific string of digits and a service key value. At each call attempt, when the leading digits of the calling party number and the service key match these specific values, the call gapping treatment shall be applied to this call. | +| O Optional (Service logic dependent). | | | + +Gap Indicators contains the following information: + +| Information element name | Status | Description | +|--------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Duration | M | Duration specifies the total time interval during which call gapping for the specified gap criteria will be active.
A duration of 0 indicates that gapping is to be removed.
A duration of -2 indicates a network specific duration.
Other values indicate duration in seconds. | +| Interval | M | This parameter specifies the minimum time between calls being allowed through.
An interval of 0 indicates that calls meeting the gap criteria are not to be rejected.
An interval of -1 indicates that all calls meeting the gap criteria are to be rejected.
Other values indicate interval in milliseconds. | +| M Mandatory (The IE shall always be sent). | | | + +Gap Treatment contains one of the following (choice): + +| Information element name | Status | Description | +|---------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| Information To Send | O | This parameter indicates an announcement or a tone to be sent to the calling party. At the end of information sending, the call shall be released. | +| Release Cause | O | If the call is to be released, this IE indicates a specific cause value to be sent in the release message. See ETSI EN 300 356-1 [20] for the coding. | +| O Optional (Service logic dependent). | | | + +Information To Send contains one of the following (choice): + +| Information element name | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------| +| In-band Info | O | This parameter specifies the in-band information to be sent. | +| Tone | O | This parameter specifies a tone to be sent to the end-user. | +| O Optional (Service logic dependent). | | | + +In-band Info contains the following information: + +| Information element name | Status | Description | +|--------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Message Id | M | This parameter indicates the message(s) to be sent, it can be one of the following. | +| Message Duration | O | This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. ZERO indicates endless repetition. | +| M Mandatory (The IE shall always be sent). | | | +| O Optional (Service logic dependent). | | | + +Message Id contains one of the following (choice): + +| Information element name | Status | Description | +|--------------------------|-------------------------------------|-------------------------------------------------| +| Elementary Message Id | O | This parameter indicates a single announcement. | +| O | Optional (Service logic dependent). | | + +#### 4.7.1.4 Call Information Report + +##### 4.7.1.4.1 Description + +This IF is used to send specific call information for a single call to the gsmSCF as requested from the gsmSCF in a previous Call Information Request. + +##### 4.7.1.4.2 Information Elements + +| Information element name | Status | Description | +|----------------------------|--------|-----------------------------------------------------------------------------------| +| Requested Information List | M | This IE specifies a list of Requested information Values which are requested. | +| Leg ID | M | This IE indicates the party in the call for which information shall be collected. | + +#### 4.7.1.5 Event Report BCSM + +##### 4.7.1.5.1 Description + +This IF is used to notify the gsmSCF of a call-related event (i.e. BCSM events as answer and disconnect) previously requested by the gsmSCF in a Request Report BCSM Event IF. + +##### 4.7.1.5.2 Information Elements + +| Information element name | Status | Description | +|---------------------------------|--------|--------------------------------------------------------------------------| +| Event type BCSM | M | This IE specifies the type of event that is reported. | +| Event Specific Information BCSM | C | This IE indicates the call related information specific to the event. | +| Leg ID | M | This IE indicates the party in the call for which the event is reported. | +| Misc Call Info | M | This IE indicates the DP type. | + +If the Event Type BCSM IE contains either O\_Answer or T\_Answer, then the Event Specific Information BCSM IE contains the following information elements: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Destination address | M | This IE specifies the destination address for the call leg.
The NatureOfAddress indicator may contain a national-specific value. For some national-specific NatureOfAddress indicator values the length of the digit part of destination address may be zero. | + +If the Event Type BCSM IE contains one of Route\_Select\_Failure, O\_Called\_Party\_Busy, O\_Disconnect, T\_Busy, or T\_Disconnect, then the Event Specific Information BCSM IE contains the following information element: + +| Information element name | Status | Description | +|--------------------------|--------|------------------------------| +| Cause | C | This IE indicates the cause. | + +If the Event Type BCSM IE contains O\_No\_Answer then the Event Specific Information BCSM IE is not included. + +#### 4.7.1.6 Initial DP + +##### 4.7.1.6.1 Description + +This IF is generated by the IM-SSF when a trigger is detected at a DP in the BCSM, to request instructions from the gsmSCF. + +## **4.7.1.6.2 Information Elements** + +| Information element name | IM_Orig | IM_Term | Description | +|--------------------------|---------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Media Type Info List | M | M | This IE indicates the media types associated with the SIP call session. This IE shall contain the media description(s) received from the S-CSCF. | +| Called Party Number | C | C |

This IE contains the ISDN number used to identify the called party in the forward direction.

The ISDN called party number is received from the gsmSCF due to the previous CAMEL processing or is derived from the SIP URL received from the S-CSCF for the destination address.

For all IM terminating call scenarios, at least one of the following IEs shall be present:

| +| Called Party URL | C | C |

This IE contains the SIP URL used to identify the called party in the forward direction.

For all IM terminating call scenarios, at least one of the following IEs shall be present:

| +| Calling Party Number | C | C |

This IE carries the ISDN calling party number to identify the calling party or the origin of the call.

For all IM originating call scenarios, at least one of the following IEs shall be present:

| +| Calling Party URL | C | C |

This IE contains the SIP URL used to identify the calling party or the origin of the call.

For all IM originating call scenarios, at least one of the following IEs shall be present:

| +| Calling Party Category | C | C | Indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). | +| CallGap Encountered | C | C |

This parameter indicates the type of gapping the related call has been subjected to.

This parameter shall be present only if a call gapping context is applicable to the initialDP operation.

| +| SIP Call ID | M | M |

This IE represents a globally unique identifier for the SIP call. This IE may be used by the gsmSCF for inclusion in a network optional gsmSCF call record.

This IE is received from the SIP request message from S-CSCF.

| +| Cause | C | C |

This IE indicates the cause specific to the armed BCSM DP event. This IE is applicable to DP Route_Select_Failure and DP T_Busy. The cause may be used by the SCF to decide about the further handling of the call.

For IM Termination for an unregistered subscriber, the Cause IE shall be set to indicate Subscriber Absent.

| +| Event Type BCSM | M | M |

This IE indicates the armed BCSM DP event, resulting in the Initial DP IF.

This IE shall be set to indicate DP T_Busy if a not reachable event is detected (e.g. IM termination to a subscriber not currently registered).

| + +| Information element name | IM_Orig | IM_Term | Description | +|---------------------------|---------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | M | This IE identifies the mobile subscriber.

This IE shall contain the IMSI value received from the S-CSCF during notification of a SIP registration. | +| IP SSP Capabilities | C | C | This IE indicates which MRFC resources are supported within the IM-SSF and are available. If this IE is absent, this indicates that no MRFC is attached and available. | +| IM-SSF Address | M | M | This IE represents the E.164 address of the IM-SSF from which the InitialDP operation is sent from. | +| Original Called Party ID | C | C | This contains the ISDN number used to identify the original destination number if the call has been forwarded on route to the IM-SSF or is forwarded by the gsmSCF due to the previous CAMEL processing. | +| Original Called Party URL | C | C | This IE contains the SIP URL identifying the original destination number if the call has been forwarded on route to the IM—SSF or is forwarded by the gsmSCF due to the previous CAMEL processing. | +| Redirecting Party ID | C | C | This IE indicates the ISDN number identifying the directory number the call was redirected from. This IE shall also be sent if it was received from the gsmSCF due to the previous CAMEL processing. | +| Redirecting Party URL | C | C | This IE indicates the SIP URL identifying the directory number the call was redirected from. This IE shall also be sent if it was received from the gsmSCF due to the previous CAMEL processing. | +| Redirection Information | C | C | This IE contains forwarding related information, such as redirection reason. This IE shall also be sent if it was received from the gsmSCF due to the previous CAMEL processing. | +| Service Key | M | M | This IE indicates to the gsmSCF the requested CAMEL Service. It is used to address the required application/SLP within the gsmSCF. | +| Subscriber State | - | C | This IE indicates the status of the IMS Subscriber. The states are:
- CAMELBusy: The IMS subscriber is engaged on a transaction for an originating or terminating IM call session.
- NetworkDeterminedNotReachable: The network can determine from its internal data that the IMS subscriber is not reachable.
- AssumedIdle: The state of the IMS subscriber is neither "CAMELBusy" nor "NetworkDeterminedNotReachable". | +| Time And Timezone | M | M | This IE contains the time that the IM-SSF was triggered, and the time zone the IM-SSF resides in. | + +#### 4.7.1.7 Specialized Resource Report + +##### 4.7.1.7.1 Description + +This IF is used to response to a PlayAnnouncement IF when the announcement complete indication is set. + +##### 4.7.1.7.2 Information Elements + +This IF contains no information elements. + +## 4.7.2 gsmSCF to IM-SSF information flows + +### 4.7.2.1 Activity Test + +#### 4.7.2.1.1 Description + +This IF is used to check for the continued existence of a relationship between the gsmSCF and IM-SSF. If the relationship is still in existence, then the IM-SSF will respond. If no reply is received, then the gsmSCF will assume that the IM-SSF has failed in some way and will take the appropriate action. + +#### 4.7.2.1.2 Information Elements + +This IF contains no information elements. + +### 4.7.2.2 Apply Charging + +#### 4.7.2.2.1 Description + +This IF is used for interacting from the gsmSCF with the IM-SSF charging mechanisms to control the call duration. + +#### 4.7.2.2.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACh Billing Charging Characteristics | M | This IE specifies the charging related information to be provided by the IM-SSF and the conditions on which this information has to be provided back to the gsmSCF. | +| Party To Charge | M | This IE shall be reflected in the corresponding IE of the Apply Charging Report operation. This IE has no effect on the charging procedures in the MSC. | + +ACh Billing Charging Characteristics contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------| +| Time Duration Charging | M | This IE is described in the next table. | + +Time Duration Charging contains the following information: + +| Information element name | Status | Description | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Max Call Period Duration | M | This IE indicates the maximum call period duration timer. | +| Tariff Switch Interval | O | This IE indicates the tariff switch time until the next tariff switch applies. | +| Release If Duration Exceeded | O | This IE indicates that the call shall be released when the Max call Period Duration expires, with a warning tone if the Play Tone IE is present. The cause used in the release message shall be "normal unspecified".
Default is to continue the call. | +| Play Tone | O | This IE is set if a tone has to be played to the party for whom the BCSM is operating. If present, this IE indicates that 30 seconds before the Max Call Period Duration timer expires, a triple tone of 900 Hz (200 milliseconds tone, 200 milliseconds pause) shall be played. | + +### 4.7.2.3 Call Information Request + +#### 4.7.2.3.1 Description + +This IF is used to request the IM-SSF to record specific information about a single call and report it to the gsmSCF (with a CallInformationReport). + +#### 4.7.2.3.2 Information Elements + +| Information element name | Status | Description | +|---------------------------------|--------|-----------------------------------------------------------------------------------| +| Requested Information Type List | M | This IE specifies a list of specific items of information which are requested. | +| Leg ID | M | This IE indicates the party in the call for which information shall be collected. | + +Requested Information Type List contains the following information: + +| Information element name | Status | Description | +|-----------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call Attempt Elapsed Time | O | This IE indicates that the Call Attempt Elapsed Time is requested in the Call Information Report.
Call Attempt Elapsed Time is the duration between the end of the CAMEL processing initiating call setup (Connect, Continue or Continue With Argument IF) and the received answer indication from the called party side.
For the Calling Party, the value of Call Attempt Elapsed Time in the Call Information Report shall be set to 0. | +| Call Stop Time | O | This IE indicates that the Call Stop Time is requested in the Call Information Report.
Call Stop Time is the time stamp when the connection is released. | +| Call Connected Elapsed Time | O | This IE indicates that the Call Connected Elapsed Time is requested in the Call Information Report.
Call Connected Elapsed Time is the duration between the received answer indication from the called party side and the release of the connection.
For a Calling Party, it indicates the duration between the sending of IDP and the release of that party | +| Release Cause | O | This IE indicates that the Release Cause is requested in the Call Information Report.
Release Cause is the release cause for the call. | + +#### 4.7.2.4 Cancel + +##### 4.7.2.4.1 Description + +This IF is used by the gsmSCF to request the IM-SSF to cancel all EDPs and reports. + +##### 4.7.2.4.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------| +| All Requests | M | This IE indicates that all active requests for EventReportBCSM, ApplyChargingReport and CallInformationReport shall be cancelled. | + +#### 4.7.2.5 Connect + +##### 4.7.2.5.1 Description + +This IF is used to request the IM-SSF to perform the call processing actions to route a call to a specific destination. To do so, the IM-SSF may use destination information from the calling party and existing call set-up information depending on the information provided by the gsmSCF. + +#### 4.7.2.5.2 Information Elements + +| Information element name | Status | Description | +|---------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Calling Party Category | O | This IE indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). | +| Destination Routing Address | E1 | This IE contains the called party number towards which the call is to be routed using an ISDN value. | +| Destination Routing Address URL | E1 | This IE contains the called party number towards which the call is to be routed using a SIP URL. | +| Original Called Party ID | O,E2 | This contains the original destination number if the call has been forwarded on route to the IM-SSF or is forwarded by the gsmSCF.

This IE shall use an ISDN value to identify the original destination number. | +| Original Called Party URL | O,E2 | This contains the original destination number if the call has been forwarded on route to the IM-SSF or is forwarded by the gsmSCF.

This IE shall use a SIP URL to identify the original destination number. | +| Redirecting Party ID | O,E3 | This IE indicates the directory number the call was redirected from. This IE shall use an ISDN value to identify the redirecting party. | +| Redirecting Party URL | O,E3 | This IE indicates the directory number the call was redirected from. This IE shall use a SIP URL to identify the redirecting party. | + +#### 4.7.2.6 Connect To Resource + +##### 4.7.2.6.1 Description + +This IF is used to connect a call from the IM-SSF to MRFC via S-CSCF. + +##### 4.7.2.6.2 Information Elements + +This IF requires no information elements for IMS. + +#### 4.7.2.7 Continue + +##### 4.7.2.7.1 Description + +This IF requests the IM-SSF to proceed with call processing at the DP at which it previously suspended call processing to await gsmSCF instructions. The IM-SSF completes DP processing, and continues basic call processing (i.e. proceeds to the next point in call in the BCSM) without substituting new data from the gsmSCF. + +##### 4.7.2.7.2 Information Elements + +This IF contains no information elements. + +#### 4.7.2.8 Continue With Argument + +##### 4.7.2.8.1 Description + +This information flow requests the IM-SSF to proceed the call processing with modified information at the DP at which it previously suspended call processing to await gsmSCF instructions. The IM-SSF completes DP processing, and continues basic call processing (i.e. proceeds to the next point in call in the BCSM) with the modified call setup information as received from the gsmSCF. + +##### 4.7.2.8.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------------------| +| Calling Party Category | O | This IE indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). | + +#### 4.7.2.9 Disconnect Forward Connection + +##### 4.7.2.9.1 Description + +This IF is used to disconnect a connection with a MRFC previously established with a Connect To Resource IF. + +##### 4.7.2.9.2 Information Elements + +This IF contains no information elements. + +#### 4.7.2.10 Furnish Charging Information + +##### 4.7.2.10.1 Description + +This IF is used to request the IM-SSF to include call related information in the CAMEL specific logical call record. The logical call record is created when FCI is received and a logical call record for that leg does not exist. For modelling purposes the logical call record is buffered in the IM-SSF. The IM-SSF completes logical call records as defined in the SDLs. Once the logical call record is completed, then its free format data is moved to the corresponding CDR and the logical call record is deleted. + +The CSE can send multiple concatenated FCIs per leg for completion. The total maximum of free format data is 160 octets per leg. The 160 octets may be sent in one or more FCI operations. If there is non-completed free format data and new FCI operation(s) is/are received to overwrite the non-completed data, then the non-completed data is discarded and the gsmSCF can send another 160 octets per leg. The SDLs of 3GPP TS 23.078 Rel-99 [4] define when Logical CDRs are completed. After the completion the gsmSCF can send another 160 octets of free format data in one or more FCI operations for the called leg. + +##### 4.7.2.10.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------------|--------|-----------------------------------------| +| FCI Billing Charging Characteristics | M | This IE is described in the next table. | + +FCI Billing Charging Characteristics contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------| +| FCIBCCCAMEL Sequence 1 | M | This IE is described in the next table. | + +FCIBCCCAMEL Sequence 1 contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Free Format Data | M | This IE is a free format data to be inserted in the CAMEL logical call record. | +| Party To Charge | M | This IE indicates the party for whom a CAMEL logical call record will be created. | +| Append Free Format Data | O | This IE indicates that the IM-SSF shall append the free format data to the Logical call record. | + +#### 4.7.2.11 Release Call + +##### 4.7.2.11.1 Description + +This IF is used to tear down by the gsmSCF an existing call at any phase of the call for all parties involved in the call. + +#### 4.7.2.11.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Release Cause | M | A number giving an indication to the IM-SSF about the reason of releasing this specific call. This may be used by MSC/GMSC for generating specific tones to the different parties in the call or to fill in the "cause" in the release message. | + +#### 4.7.2.12 Request Report BCSM Event + +##### 4.7.2.12.1 Description + +This IF is used to request the IM-SSF to monitor for a call-related event, then send a notification back to the gsmSCF when the event is detected (see Event Report BCSM). + +##### 4.7.2.12.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------| +| BCSM Event | M | This IE specifies the event or events of which a report is requested. | + +BCSM Event contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event type | M | This IE specifies the type of event of which a report is requested. | +| Leg ID | C | This IE indicates the party in the call for which the event shall be reported. | +| Monitor Mode | M | When this IE is "interrupted", the event shall be reported as a request, if it is "notifyAndContinue", the event shall be reported as a notification, if the IE is "transparent", the event shall not be reported. | +| DP Specific Criteria | O | This IE is described in the next table. | + +DP Specific Criteria is defined as: + +| Information element name | Status | Description | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Application Timer | O | This IE carries additional timer duration information (timer values for No Answer event) required for arming No_Answer EDPs in the IM-SSF. The TNRY timer (value defined between 10 s and 40 s) shall be shorter than the network no answer timer. | +| NOTE | If a Request Report BCSM Event information flow overwrites previous Request Report BCSM Event information flow which contained Application Timer IE for No_Answer DP, the behaviour of the IM-SSF is unpredictable. | | + +#### 4.7.2.13 Reset Timer + +##### 4.7.2.13.1 Description + +This IF is used to refresh a timer. + +#### 4.7.2.13.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------| +| Timer Value | M | This IE specifies the value to which the indicated timer shall be set. | +| Timer ID | O | This IE indicates which timer shall be reset. It shall be set to "Tssf". | + +### 4.7.3 gsmSCF – IM-SSF information flows for MRFC related operations + +In an IMS Core Network, the Multimedia Resource Function Controller (MRFC) is used for providing specialised resource functions like playing announcements and tones. Requests from the gsmSCF that requires a specialised resource function are sent to the MRFC via the IM-SSF and S-CSCF using SIP signalling as specified in the functional requirements of the MRFC found in 3GPP TS 23.218 [5]. + +This subclause contains the information flows descriptions between the gsmSCF and the IM-SSF for MRFC-related operations. + +#### 4.7.3.1 Cancel + +##### 4.7.3.1.1 Description + +This IF is used by the gsmSCF to request the IM-SSF to cancel a correlated previous operation in the MRFC. + +##### 4.7.3.1.2 Information Elements + +The following information elements are used: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------| +| Invoke ID | M | This IE specifies the operation to be cancelled. | + +#### 4.7.3.2 Play Announcement + +##### 4.7.3.2.1 Description + +This IF is sent from the gsmSCF to the IM-SSF and is used to specify information for playing announcements or tones in the MRFC. + +##### 4.7.3.2.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------| +| Information To Send | M | This IE indicates an announcement or a tone to be sent to the end user by the MRFC. | +| Disconnect From IP Forbidden | M | This IE indicates whether or not the MRFC may be disconnected from the user when all information has been sent. | +| Request Announcement Complete | M | This IE indicates whether or not a SpecializedResourceReport shall be sent to the gsmSCF when all information has been sent. | + +Information To Send contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Inband Info | C | This IE indicates the inband information to be sent. | +| Tone | C | This IE indicates the tone to be sent. The mapping from the code points of this IE to tones is a matter for agreement between the gsmSCF operator and the MRFC operator. | + +Inband Info contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| Message ID | M | This IE is described in the next table. | +| Number Of Repetitions | M | This IE indicates the maximum number of times the message shall be sent to the end-user. | +| Duration | O | This IE indicates the maximum duration time in seconds that the message shall be played/repeated. Zero indicates endless repetition. | +| Interval | O | This IE indicates the time interval in seconds between two repetitions. | + +Message ID contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------------------------------------------------------| +| Elementary Message ID | C | This IE indicates a single announcement | +| Text | C | This IE indicates a text to be sent. The text shall be transformed to inband information (speech) by the MRFC. | +| Elementary Message IDs | C | This IE indicates a sequence of announcements | +| Variable Message | C | This IE indicates an announcement with one or more variable parts. | + +Tone contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| Tone ID | M | This IE indicates the tone to be sent. | +| Duration | O | This IE indicates the maximum duration time in seconds that the message shall be played/repeated. Zero indicates endless repetition. | + +#### 4.7.3.3 Prompt And Collect User Information (received information) + +##### 4.7.3.3.1 Description + +This IF is sent from the gsmSCF to the IM-SSF and is used to interact with a call party in order to collect information. + +##### 4.7.3.3.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------| +| Collected Info | M | This IE is described in the next table. | +| Information To Send | O | This IE indicates an announcement or a tone to be sent to the end user by the MRFC. | +| Disconnect From IP Forbidden | M | This IE indicates whether the MRFC may be disconnected from the user when all information has been sent. | + +Collected Info contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------| +| Collected Digits | M | This IE is described in the next table. | + +Collected Digits contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Minimum Number Of Digits | M | This IE indicates the minimum number of valid digits to be collected. | +| Maximum Number Of Digits | M | This IE specifies the maximum number of valid digits to be collected | +| End Of Reply Digit | O | This IE indicates the digit(s) used to signal the end of input. | +| Cancel Digit | O | If this IE is present, the cancel digit can be entered by the user to request a possible retry | +| Start Digit | O | If this IE is present, the start digit(s) indicates the start of the valid digits to be collected. | +| First Digit Time Out | O | If this IE is present, the first digit shall be received before the expiration of the first digit timer expiration | +| Inter Digit Time Out | O | If this IE is present, any subsequent valid or invalid digit shall be received by the MRFC before the inter digit timer expires. | +| Error Treatment | O | This IE indicates what specific action shall be taken by the MRFC in the event of error conditions occurring. | +| Interruptable Ann Ind | O | If this IE is set to TRUE (default value) the announcement is interrupted after the first valid or invalid digit received by the MRFC. If this IE is present and explicitly set to FALSE, the announcement will not be interrupted after the first digit is received by the MRFC | +| Voice Information | O | This IE is optional, where the default value is specified being FALSE. If the VoiceInformation IE is set to FALSE, all valid or invalid digits are entered by DTMF If this IE is present and explicitly set to TRUE, calling user is required to provide all valid or invalid information by speech | +| Voice Back | O | This IE is optional, where the default value is specified being FALSE. If the VoiceBack IE is set to FALSE, no voice back information is given by the MRFC If this IE is present and explicitly set to TRUE, the valid input digits received by the MRFC will be announced back to the calling user immediately after the end of input is received | + +InformationToSend is defined in subclause 4.7.3.2.2. + +#### 4.7.3.4 Prompt And Collect User Information ack (received information) + +##### 4.7.3.4.1 Description + +This IF is used by the IM-SSF to indicate the result a Prompt And Collect User Information IF to the gsmSCF. + +##### 4.7.3.4.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------| +| Digits Response | C | This IE indicates the digit sequence received from the end user | + +#### 4.7.3.5 Specialized Resource Report + +##### 4.7.3.5.1 Description + +This IF is used by the IM-SSF to response to a PlayAnnouncement IF when the announcement complete indication is set. + +#### 4.7.3.5.2 Information Elements + +This IF contains no information elements. + +### 4.7.4 IM-SSF to HSS information flows + +#### 4.7.4.1 Any Time Subscription Interrogation request + +##### 4.7.4.1.1 Description + +This IF is used by the IM-SSF to request subscription information from the HSS. For example, the IM-SSF shall send this as a result of receiving a third party SIP registration from the S-CSCF (over the ISC interface). The IM-SSF shall also send the MAP ATSI request when a SIP INVITE message on a MT session for an unregistered subscriber is received. + +##### 4.7.4.1.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gsmSCF Address | M | This IE shall indicate the address of the interrogating IM-SSF. The address shall be in international E.164 format. | +| Requested Info | M | This IE indicates the type of subscriber information being requested. This shall consist of the CAMEL Subscription Information; the CAMEL Subscription Information is described in a table below. | +| Subscriber Identity | M | This IE identifies the subscriber for which the information is requested. The identity shall be an IMSI. | + +CAMEL subscription information contains the following information elements: + +| Information element name | Status | Description | +|----------------------------------------------|--------|-------------------------------------------------------------------------| +| Additional Requested CAMEL Subscription Info | M | This IE shall contain one of the following: O-IM-CSI/VT-IM-CSI/D-IM-CSI | + +#### 4.7.4.2 Notify Subscriber Data Change ack + +##### 4.7.4.2.1 Description + +This IF is used to respond to the HSS's notification of the change of subscriber data. + +##### 4.7.4.2.2 Information Elements + +This IF contains no information elements. + +### 4.7.5 HSS to IM-SSF information flows + +#### 4.7.5.1 Any Time Subscription Interrogation ack + +##### 4.7.5.1.1 Description + +This IF is used by the HSS to provide the requested subscriber's IM-CSI data to the IM-SSF. + +##### 4.7.5.1.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CAMEL Subscription Information | C | This IE shall be present if the subscriber is provisioned with a CAMEL Subscription Information for IM CN. This IE is described in a table below. | + +CAMEL Subscription Information contains the following information elements: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------| +| O-IM-CSI | C | See subclause 4.4.1.1 | +| D-IM-CSI | C | See subclause 4.4.1.2 | +| VT-IM-CSI | C | See subclause 4.4.1.3 | + +#### 4.7.5.2 Notify Subscriber Data Change + +##### 4.7.5.2.1 Description + +This IF is used by the HSS to notify to the IM-SSF of the change of subscriber IM CSI data. This IF is sent at each time subscriber IM CSI data is changed. + +##### 4.7.5.2.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | The IMSI is used to identify the subscriber. | +| MSISDN | C | This shall consist of the subscriber's MSISDN if available. If no MSISDN is available, the parameter shall be set with a dummy MSISDN value. | +| CAMEL Subscription Information | M | The CAMEL Subscription Information IE is used to indicate the modified or deleted CAMEL Subscription Information data. This IE is described in a table below. | + +CAMEL Subscription Information Modified contains the following information elements: + +| Information element name | Status | Description | +|---------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| O-IM-CSI | S | See subclause 4.4.1.1. It shall be present if it was modified. | +| D-IM-CSI | S | See subclause 4.4.1.2. It shall be present if it was modified. | +| VT-IM-CSI | S | See subclause 4.4.1.3. It shall be present if it was modified. | +| Specific CSI Deleted List | S | This IE indicates that one or more specific elements of IMS CAMEL Subscription Information have been deleted from the HSS. It shall indicate any of the following; This IE shall be present if IM CSI is/are deleted. | + +## 5 Control and interrogation of subscription data + +Support of the procedures described in this clause in CAMEL Phase 4 is a network operator option. + +### 5.1 Architecture + +The architecture for the control and the interrogation of subscription data described in the clause 10 in 3GPP TS 23.078 Rel-99 [4] for the HLR and the gsmSCF also applies for the HSS and the gsmSCF. + +### 5.2 Procedures for CAMEL + +#### 5.2.1 Any Time Subscription Interrogation + +The following process in the HLR described in 3GPP TS 23.078 Rel-99 [4] applies for the handling of Any Time Interrogation for Subscription Information Retrieval in the HSS: + +- CAMEL\_ATSI\_HLR. + +#### 5.2.2 Any Time Modification + +The following process in the HLR described in 3GPP TS 23.078 Rel-99 [4] applies for the handling of Any Time Modification in the HSS: + +- CAMEL\_ATM\_HLR. + +## 5.2.3 Notify Subscriber Data Change + +The description of the procedure in 3GPP TS 23.078 Rel-99 [4] applies for the handling of Notify Subscriber Data Change in the HSS. + +## 5.3 Description of information flows + +This subclause contains the detailed description of the information flows used by CAMEL for control and interrogation of subscription data. + +Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Specific conditions (S), mutually Exclusive (E) or Optional (O). + +An 'M' IE shall always be included. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. An 'O' IE may be included or omitted as required by the service logic. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol. + +The following principles apply for the handling of the IEs by the receiving entity: + +- The gsmSCF may silently discard any IE which it does not functionally support. +- The HSS shall return an error if it does not functionally support an IE which it receives. + +Details of errors and exceptions to these rules are specified in 3GPP TS 29.002 [9]. + +### 5.3.1 gsmSCF to HSS information flows + +#### 5.3.1.1 Any Time Modification Request + +##### 5.3.1.1.1 Description + +This IF is used to modify information in the HSS at any time. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.1.2 Any Time Subscription Interrogation Request + +##### 5.3.1.2.1 Description + +This IF is used to request subscription information from the HSS at any time. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +##### 5.3.1.2.2 Information Elements + +Any Time Subscription Interrogation Request is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------| +| Requested Info | M | This IE may indicate supported CAMEL phases in HSS. | + +| | | | +|------------------------------------|-----|-----------------------------------------------------------------------------------| +| Additional CAMEL Subscription Info | S,E | This IE may be one of the following elements:
O-IM-CSI / VT-IM-CSI / D-IM-CSI. | +|------------------------------------|-----|-----------------------------------------------------------------------------------| + +#### 5.3.1.3 Notify Subscriber Data Change response + +##### 5.3.1.3.1 Description + +This IF is used by the gsmSCF to respond to the HSS of the change of subscriber data notify. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +## 5.3.2 HSS to gsmSCF information flows + +### 5.3.2.1 Any Time Modification ack + +#### 5.3.2.1.1 Description + +This IF is used by the HSS to provide the modified information to the gsmSCF. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.2.1.2 Information Elements + +Any Time Modification ack is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------| +| O-IM-CSI | S | See subclause 4.4.1.1. It shall be present if it was modified. | +| VT-IM-CSI | S | See subclause 4.4.1.3. It shall be present if it was modified. | +| D-IM-CSI | S | See subclause 4.4.1.2. It shall be present if it was modified. | + +### 5.3.2.2 Any Time Subscription Interrogation ack + +#### 5.3.2.2.1 Description + +This IF is used by the HSS to provide the requested subscription information to the gsmSCF. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.2.2.2 Information Elements + +Any Time Subscription Interrogation ack is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|-------------------------------|--------|---------------------------------------------------------| +| Supported CAMEL Phases In HSS | C | This IE indicates the CAMEL phase supported in the HSS. | +| O-IM-CSI | C | See subclause 4.4.1.1. | +| VT-IM-CSI | C | See subclause 4.4.1.3. | +| D-IM-CSI | C | See subclause 4.4.1.2. | + +### 5.3.2.3 Notify Subscriber Data Change + +#### 5.3.2.3.1 Description + +This IF is used by the HSS to notify to the gsmSCF of the change of subscriber data. This IF is sent at each time subscriber data is changed. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.2.3.2 Information Elements + +Notify Subscriber Data Change is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|---------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Specific CSI Deleted List | S | This IE shall indicate any of the following;
- O-IM-CSI (with TDP criteria for O-IM-CSI); -
- D-IM-CSI (with TDP criteria for D-IM-CSI);
- VT-IM-CSI with TDP criteria for VT-IM-CSI; | + +## 6 Subscriber Location and State retrieval + +Support of the procedures described in this clause in CAMEL Phase 4 is a network operator option. + +### 6.1 Architecture + +The architecture for the subscriber location and state retrieval described in the clause 11 in 3GPP TS 23.078 Rel-99 [4] for the HLR and the gsmSCF applies for the HSS and the gsmSCF. + +### 6.2 Procedures for CAMEL + +#### 6.2.1 Any Time Interrogation + +The description of the procedure in 3GPP TS 23.078 Rel-99 [4] applies for the Any Time Interrogation in the HSS. + +### 6.3 Description of information flows + +This subclause contains the detailed description of the information flows used by CAMEL for the retrieval of information about the location and state of a subscriber. + +Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Specific conditions (S), mutually Exclusive (E) or not applicable (-). + +An 'M' IE shall always be included. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. When a set of 'E' IEs is shown in the definition of an Information Flow or compound IE, only one of those IEs may be included. A '-' IE shall always be omitted. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol. + +The following principles apply for the handling of the IEs by the receiving entity: + +- The gsmSCF may silently discard any IE which it does not functionally support. +- The GMLC shall return an error if it does not functionally support an IE which it receives. + +Details of errors and exceptions to these rules are specified in 3GPP TS 29.002 [9]. + +#### 6.3.1 gsmSCF to HSS information flows + +##### 6.3.1.1 Any Time Interrogation Request + +###### 6.3.1.1.1 Description + +This IF is used to request information (any one or more of subscriber state, subscriber location, IMEI & software version, MS classmark information for the CS domain and GPRS MS classmark information) from the HSS at any time. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 6.3.2 HSS to gsmSCF information flows + +##### 6.3.2.1 Any Time Interrogation ack + +###### 6.3.2.1.1 Description + +This IF is used by the HSS to provide the requested subscriber location and/or subscriber state information to the gsmSCF. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +--- + +## Annex A (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Re
v | Subject/Comment | New | +|---------|-------|-----------|-----|---------|------------------------------------------------------------------|-------| +| 09/2002 | CN#17 | NP-020348 | | | Creation of version 5.0.0 | 5.0.0 | +| 12/2002 | CN#18 | NP-020530 | 001 | 2 | Correction and improvement in the overall SDL structure | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 002 | | Correction and improvement in the registration procedures | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 003 | 2 | Correction and improvement in MO procedures | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 004 | 3 | Correction and improvement in MT procedures | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 005 | | Correction and improvement in CSI update | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 006 | | Clarification in the case multiple RRBs are sent for a DP | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 007 | 1 | Inconsistent description on ACR: time information | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 008 | | Remove support of SCI operation from imcnSSF SDL process | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 009 | | Removal of ETC processing from IM-SSF SDL Procedures | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 010 | 1 | Correction of InitialDP MediaType parameter | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 012 | 1 | IF Description for gsmSRF-related operations for IMS | 5.1.0 | +| 12/2002 | CN#18 | NP-020529 | 014 | | Figure and table numbers editorial changes | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 015 | | For better document structure - editorial | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 016 | | Editorial improvement - clause 2 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 017 | | Editorial improvement - clause 3 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 018 | | Editorial improvement - clause 4 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 019 | | Editorial improvement - clause 5 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 020 | | Editorial improvement - clause 6 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 021 | | Editorial improvement - clause 7 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 022 | | SDL Procedure for Connect To Resource | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 023 | 1 | Stage 2 specifications for Call Gap for IMS | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 024 | 2 | Clarification of DP destination number trigger criteria for IMS | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 025 | | Number comparison for D-CSI | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 026 | | Correction to Dialled Services criteria | 5.1.0 | +| 03/2003 | CN#19 | NP-030090 | 027 | 1 | Implementing of Connect to Resource handling in CAMEL for IMS | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 028 | 1 | Introduction of ResetTimer input in state WFI-DS (IMS) | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 029 | | Correction of imcnSSF procedure names | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 030 | | Incorrect procedure names used for CAMEL_MT_CTR and CAMEL_MO_CTR | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 031 | | Incorrect procedures called in CAMEL_IMCN_MT_ANSWER | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 032 | | Sending of provisional response for the INVITE | 5.2.0 | + +| | | | | | | | +|---------|--------|-----------|------|---|----------------------------------------------------------------------------|--------| +| 03/2003 | CN#19 | NP-030091 | 033 | | Incorrect SIP response when no CAMEL is invoked | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 035 | 1 | Corrections in CAMEL_IMCN_MO_ANSWER | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 036 | | Corrections in the procedures for handling failure SIP response | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 039 | | Inconsistency in Call Information Report in Re-Connect Case | 5.2.0 | +| 06/2003 | CN#20 | NP-030191 | 040 | 1 | Incorrect list of TDPs listed for O-IM-CSI | 5.3.0 | +| 06/2003 | CN#20 | NP-030191 | 041 | | Corrections to process IM-SSF | 5.3.0 | +| 06/2003 | CN#20 | NP-030191 | 042 | | Redundant check for Final_Response_Received in Disconnect procedures | 5.3.0 | +| 09/2003 | CN#21 | NP-030374 | 043 | 2 | Incorrect handling of failure SIP response for MT | 5.4.0 | +| 09/2003 | CN#21 | NP-030374 | 044 | 2 | Setting of Timers not specified for IM-SSF process | 5.4.0 | +| 09/2003 | CN#21 | NP-030374 | 045 | 1 | Incorrect handling of failure SIP response for MO | 5.4.0 | +| 12/2003 | CN#22 | NP-030525 | 046 | 1 | Correction to the definition of interfaces for the IM-SSF | 5.5.0 | +| 09/2004 | CN#25 | NP-040397 | 047 | | Correction of Check_Criteria Procedure names referenced in Process imcnSSF | 5.6.0 | +| 12/2004 | CN#26 | | | | Rel-6 created after CN#26 | 6.0.0 | +| 06/2005 | CT#28 | CP-050097 | 0048 | | Removal of references to HLR for CAMEL control of IMS | 6.1.0 | +| 12/2005 | CT#30 | CP-050665 | 0049 | | Incorrect References | 6.2.0 | +| 12/2005 | CT#30 | | | | Rel-7 version was created because of ETSI TISPAN references. | 7.0.0 | +| 03/2006 | CT#31 | CP-060082 | 0050 | | Specification of gsmSCF Address format in AnyTime request messages | 7.1.0 | +| 12/2008 | CT#42 | | | | Upgraded unchanged from Rel-7 | 8.0.0 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 10.0.0 | +| 2012-09 | CT#57 | CP-120467 | 0052 | 1 | Mapping of SIP Responses code and Camel Detection Points | 11.0.0 | +| 2012-10 | | | | | Missing SDLs related to CR 0052 added. | 11.0.1 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 | +| 2015-12 | CT#70 | - | - | - | Update to Rel-13 version (MCC) | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | CT#88e | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/27_series/27001/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-16/27_series/27001/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2a03125f5626ca6ee2188abf24cacc364653882 --- /dev/null +++ b/marked/Rel-16/27_series/27001/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8226685629d54ac8c28cc424bea85dfc490865197275af29146fec4abc828f8f +size 14928 diff --git a/marked/Rel-16/27_series/27001/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/27_series/27001/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47555c23d2d5e8b1afb3483c99a5990a89a6ce70 --- /dev/null +++ b/marked/Rel-16/27_series/27001/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d027f9e60c955e6436129e033233c4913d814119d16c89e735bc62d16402535b +size 38865 diff --git a/marked/Rel-16/27_series/27001/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/27_series/27001/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37896f5ded6cc9f9d43ab68aa08795a0265eed67 --- /dev/null +++ b/marked/Rel-16/27_series/27001/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71091e5543b955c83ebba3e24bce91fff48e3021f8dac51a2e287e7ee5c2b125 +size 31173 diff --git a/marked/Rel-16/27_series/27001/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Rel-16/27_series/27001/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b432086f639888568cc73e3be3b42f759c123c1c --- /dev/null +++ b/marked/Rel-16/27_series/27001/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f093f3b5bba355d63512e0d7d20af768c96098af5d60022bd14eb9f27f80e6d +size 44192 diff --git a/marked/Rel-16/27_series/27001/raw.md b/marked/Rel-16/27_series/27001/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..128bbbe383823400253e383ee22f648dbe4d7399 --- /dev/null +++ b/marked/Rel-16/27_series/27001/raw.md @@ -0,0 +1,2775 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Abbreviations ..... | 11 | +| 4 Access reference configuration..... | 12 | +| 5 Functions to support data services ..... | 13 | +| 6 Support of non transparent Bearer Services..... | 13 | +| 6.1 Functions of the Layer 2 Relay ..... | 13 | +| 6.1.1 Layer 2 Relay in Frame Tunneling Mode ..... | 14 | +| 6.2 Radio Link Services Used..... | 15 | +| 6.3 Flow Control - General Description..... | 15 | +| 6.3.1 End to End Flow Control..... | 15 | +| 6.3.2 Back Pressure ..... | 15 | +| 6.3.3 Receive not Ready..... | 15 | +| 6.4 User initiated service level up and down grading (applies to A/Gb and GERAN Iu mode only) ..... | 15 | +| 6.5 Asymmetry preference indication (applies to A/Gb and GERAN Iu mode only) ..... | 16 | +| 7 Structure of the 3GPP TS 27-series of Specifications ..... | 16 | +| 8 Functions common to all interfaces ..... | 17 | +| 8.1 Synchronization of the Traffic Channel..... | 17 | +| 8.1.1 Transparent services ..... | 17 | +| 8.1.1.1 Initial procedure for traffic channel types TCH/F4.8 and TCH/F9.6 ..... | 17 | +| 8.1.1.2 Initial procedure for traffic channel types TCH/F14.4 and TCH/F28.8 ..... | 18 | +| 8.1.1.3 Subsequent procedures for traffic channel types TCH/F4.8, TCH/F9.6, TCH/F14.4, and TCH/F28.8 ..... | 18 | +| 8.1.1.3.1 V-series interface..... | 18 | +| 8.1.1.3.2 X-series interface..... | 18 | +| 8.1.1.3.3 S interface (I.420)..... | 18 | +| 8.1.1.4 Procedures for RLC..... | 18 | +| 8.1.1.4.1 V-series interface..... | 18 | +| 8.1.2 Non-transparent services ..... | 19 | +| 8.1.2.1 V-series interface ..... | 19 | +| 8.1.2.2 X-series interface ..... | 19 | +| 8.1.2.3 S interface (I.420) (does not apply to UTRAN Iu mode) ..... | 19 | +| 8.1.3 Action on loss of synchronization ..... | 19 | +| 8.1.3.1 Loss at the TAF-radio interface ..... | 19 | +| 8.1.3.2 Loss at the TAF-terminal interface..... | 19 | +| 8.2 Filtering of Channel Control Information (A/Gb or GERAN Iu mode transparent mode only) ..... | 19 | +| 8.2.1 General ..... | 19 | +| 8.2.2 Filtering process to be applied..... | 20 | +| 8.2.2.1 V-series interface ..... | 20 | +| 8.2.2.2 X-series interface ..... | 20 | +| 8.2.2.3 Filtering mechanism ..... | 21 | +| 8.2.2.3.1 Traffic channel types TCH/F4.8 and TCH/F9.6 ..... | 21 | +| 8.2.2.3.2 Traffic channel type TCH/F14.4 ..... | 21 | +| 8.3 Terminal Compatibility Decision..... | 21 | +| 8.3.1 Compatibility Check..... | 21 | +| 8.3.2 Selection of Appropriate Terminal Function..... | 21 | +| 8.3.3 Indication of Compatibility Requirements to the PLMN ..... | 21 | +| 8.3.3.1 Indication in case of Mobile terminating calls..... | 21 | +| 8.3.3.2 Indication in case of Mobile originating calls ..... | 24 | +| 8.3.3.3 Differences in validity of BC parameter values in A/Gb mode, GERAN Iu mode and UTRAN Iu mode..... | 26 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| 8.4 | Test Loops..... | 26 | +| 8.5 | Alternate speech/facsimile group 3 ..... | 26 | +| 8.5.1 | In case of A/Gb mode..... | 26 | +| 8.5.2 | In case of UTRAN Iu mode..... | 26 | +| 8.6 | Multislot configuration split/combine function..... | 27 | +| 8.6.1 | Non-transparent data ..... | 27 | +| 8.6.2 | Transparent data ..... | 27 | +| 8.7 | EDGE multiplexing function ..... | 27 | +| 8.8 | Seamless data rate change..... | 27 | +| Annex A (informative): | List of Bearer Capability Elements ..... | 28 | +| Annex B (normative): | Setting of Bearer Capability, Low Layer Compatibility and High Layer Compatibility Information Element for PLMN Bearer Services and PLMN TeleServices ..... | 35 | +| B.0 | Scope..... | 35 | +| B.1 | Bearer Capability Information Element..... | 35 | +| B.1.1 | Introduction ..... | 35 | +| B.1.1.1 | General Consideration ..... | 35 | +| B.1.1.2 | Interpretation of the Diagrams..... | 36 | +| B.1.2 | Bearer Service 20, Data Circuit Duplex Asynchronous..... | 48 | +| B.1.2.1 | Unrestricted / restricted digital information transfer capability ..... | 48 | +| B.1.2.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 50 | +| B.1.2.3 | Frame Tunnelling Mode..... | 52 | +| B.1.2.4 | PIAFS ..... | 53 | +| B.1.3 | Bearer Service 30, Data Circuit Duplex Synchronous..... | 54 | +| B.1.3.1 | Unrestricted/restricted digital information transfer capability ..... | 54 | +| B.1.3.1.1 | Transparent FNUR <= 48 kbit/s (TCH/F4.8, TCH/F9.6, TCH/14.4, TCH/F28.8) ..... | 54 | +| B.1.3.1.2 | X.32 Case..... | 55 | +| B.1.3.1.3 | Transparent FNUR=56 kbit/s, including 3G-H.324/M, (TCH/F9.6, TCH/F32.0, UTRAN Iu mode) ..... | 56 | +| B.1.3.1.4 | Transparent FNUR = 56kbit/s, including 3G-H.324/M (TCH/F14.4)..... | 58 | +| B.1.3.1.5 | Transparent FNUR = 64kbit/s, including 3G-H.324/M (TCH/F9.6, TCH/F14.4, TCH/F32.0, UTRAN Iu mode))..... | 59 | +| B.1.3.1.6 | 3G-H.324/M, FNUR=32.0 kbit/s (TCH/F32.0, UTRAN Iu mode)..... | 61 | +| B.1.3.1.7 | Synchronous transparent 56 kbit/s (RDI) and 64kbit/s (UDI) (UTRAN Iu mode) ..... | 63 | +| B.1.3.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 64 | +| B.1.3.2.1 | Non-X.32 Cases ..... | 64 | +| B.1.3.2.2 | X.32 Case..... | 65 | +| B.1.3.2.3 | 3G-H.324/M Case..... | 66 | +| B.1.4 | Bearer Service 40 ... 46, PAD Access Asynchronous..... | 67 | +| B.1.5 | Bearer Service 50 ... 53 ,Data Packet Duplex Synchronous, Unrestricted digital information transfer capability ..... | 67 | +| B.1.6 | Bearer Service 61, Alternate Speech/Data ..... | 67 | +| B.1.7 | Bearer Service 81, Speech followed by Data..... | 67 | +| B.1.8 | Teleservice 11 ... 12, Speech..... | 68 | +| B.1.9 | Teleservice 21 ... 23, Short Message..... | 69 | +| B.1.10 | Teleservice 61, Alternate Speech and Facsimile group 3 ..... | 69 | +| B.1.10.1 | Teleservice 61, Speech ..... | 69 | +| B.1.10.2 | Teleservice 61, Facsimile group 3 in A/Gb mode..... | 70 | +| B.1.10.3 | Teleservice 61, Facsimile group 3 in UTRAN Iu mode..... | 71 | +| B.1.11 | Teleservice 62, Automatic Facsimile group 3..... | 72 | +| B.1.12 | Valid combinations of FNUR, WAIUR, ACC, mTCH..... | 72 | +| B.1.12.1 | Transparent Services ..... | 72 | +| B.1.12.2 | Non-transparent services ..... | 74 | +| B.1.13 | Assignment of radio access bearer parameters depending on FNUR and WAIUR..... | 75 | +| B.1.13.1 | Transparent Services ..... | 75 | +| B.1.13.2 | Non-transparent services for UTRAN Iu mode..... | 76 | +| B.1.13.3 | Non-transparent services for GERAN Iu mode..... | 76 | + +| | | | +|------------------------|-------------------------------------------------------------------------|----| +| B.2 | Low Layer/High Layer Compatibility Information Element ..... | 78 | +| B.2.1 | Introduction ..... | 78 | +| B.2.1.1 | General Consideration ..... | 78 | +| B.2.1.2 | Interpretation of the Tables..... | 79 | +| B.2.2 | LLC Bearer Service 20..... | 79 | +| B.2.2.1 | Unrestricted / restricted digital information transfer capability ..... | 79 | +| B.2.2.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 79 | +| B.2.3 | LLC Bearer Service 30..... | 80 | +| B.2.3.1 | Unrestricted / restricted digital information transfer capability ..... | 80 | +| B.2.3.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 80 | +| B.2.4 | LLC Bearer Services 41 ... 46 ..... | 81 | +| B.2.5 | LLC Bearer Services 51 ... 53 ..... | 81 | +| B.2.6 | LLC Bearer Service 61 ..... | 81 | +| B.2.7 | LLC Bearer Service 81 ..... | 81 | +| B.2.8 | HLC Teleservices 11 ... 12..... | 81 | +| B.2.9 | HLC Teleservices 21 ... 23..... | 81 | +| B.2.10 | HLC Teleservice 61 ..... | 81 | +| B.2.11 | HLC Teleservice 62 ..... | 82 | +| Annex C (informative): | Change history..... | 83 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the functions needed for terminal adaptation within the 3GPP 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 is based on the principles of terminal adaptor functions presented in the ITU-T I-series of Recommendations (I.460 to I.463). + +The PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN there is a need to connect various kinds of terminal equipment to the Mobile Termination (MT). The target of the present document is to outline the functions needed for the terminal adaptation. + +The bearer services are described in 3GPP TS 22.002 and the general network configuration is described in 3GPP TS 23.002. The PLMN access reference configuration is defined in 3GPP TS 24.002. The various connection types used in the A/Gb mode or GERAN Iu mode PLMN are presented in 3GPP TS 43.010. Terminology used in the present document is presented in 3GPP TR 21.905 and 3GPP TS 29.990. For support of data services between a PLMN and other networks see 3GPP TS 29.007. + +The present document is valid for a 2nd generation PLMN (A/Gb mode) as well as for a 3rd generation PLMN (Iu mode). If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "UTRAN Iu mode". If text applies to both of the systems, but a distinction between the ISDN/PSTN and the PLMN is necessary, the term "PLMN" is used. + +NOTE 1: From R99 onwards the following services are no longer required by a PLMN: + +- the dual Bearer Services "alternate speech/data" and "speech followed by data"; +- the dedicated services for PAD and Packet access; +- BS 21 ... 26 and BS 31 ... 34. + +From REL-4 onwards the following service is no longer required by a PLMN: + +- the synchronous Bearer Service non-transparent (BS 30 NT). +- non-transparent facsimile (TS 61/62 NT) for the A/Gb mode and GERAN Iu mode. + +The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to former releases. + +NOTE2 : The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is 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] Void. +- [2] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [3] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". +- [4] 3GPP TS 23.002: "Network architecture". +- [5] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types". + +- [6] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [7] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols -Stage 3". +- [8] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [9] 3GPP TS 24.022: "Radio Link Protocol (RLP) for circuit switched bearer and teleservices". +- [10] 3GPP TS 45.005: "Radio transmission and reception". +- [11] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using Asynchronous bearer capabilities". +- [12] 3GPP TS 27.003: "Terminal Adaptation Functions (TAF) for services using Synchronous bearer capabilities". +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. +- [18] Void. +- [19] Void. +- [20] Void. +- [21] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [22] Void. +- [23] Void. +- [24] Void. +- [25] Void. +- [26] ITU-T V-series Recommendations: "Data communication over the telephone network". +- [27] Void. +- [28] ITU-T X-series Recommendations: "Data networks and open system communication". +- [29] Void +- [30] ITU-T Recommendation X.150 (11/88): "Data Communication Networks: Transmission, Signalling and Switching, Network Aspects, Maintenance and Administrative Arrangements". +- [31] Void. +- [32] ITU-T Recommendation V.250 (05/99): "Serial asynchronous automatic dialling and control". +- [33] ITU-T Recommendation V.54 (11/88): "Loop test devices for modems". +- [34] ITU-T Recommendation V.110 (10/96): "Support by an ISDN of data terminal equipments with V-Series type interfaces". + +- [35] ITU-T Recommendation I.460 (02/99), ITU-T Recommendation I.461 (also published as ITU-T Recommendation X.30 [70] ), ITU-T Recommendation I.462 (also published as ITU-T Recommendation X.31 (11/95)), ITU-T Recommendation I.463 (also published as ITU-T Recommendation V.110 [34]): "ISDN Overall Network Aspects and Functions, User Network Interfaces". +- [36] ITU-T Recommendation Q.931 (1998): "ISDN user network interface layer 3 specification for basic call control". +- [37] ETSI ETR 018 ed.4 (1995-11): "Integrated Services Digital Network (ISDN), Application of the Bearer Capability (BC), High Layer Compatibility (HLC) and Low Layer Compatibility (LLC) information elements by terminals supporting ISDN services". +- [38] ISO/IEC 6429: 1992: "Information technology - Control functions for coded character sets". +- [39] Void. +- [40] Void. +- [41] Void. +- [42] ITU-T Recommendation V.120 (10/96): "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". +- [43] 3GPP TS 23.034: "High Speed Circuit Switched Data (HSCSD) - Stage 2". +- [44] ISO/IEC 13239 (1997) Information Technology: "Telecommunications and information exchange between systems - High-level data link control (HDLC) procedures" +- [45] Void. +- [46] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [47] 3GPP TR 25.990: "Vocabulary for UTRAN". +- [48] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification". +- [49] Void. +- [50] Mobile Internet Access Forum: "PIAFS Specification Ver. 1.1, 2.1". +- [51] ITU-T Recommendation V.80 (08/96): "In-band DCE control and synchronous data modes for asynchronous DTE". +- [52] 3GPP TS 43.045: "Technical realization of facsimile group 3 service - transparent". +- [53] 3GPP TS 45.001: "Physical layer on the radio path; General description". +- [54] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD); Stage 1". +- [55] 3GPP TS 23.107: "Quality of Service QoS concept and architecture". +- [56] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [57] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)". +- [58] ITU-T Recommendation I.440 (also published as ITU-T Recommendation Q.920 [71]). +- [59] ITU-T Recommendation I.450 (also published as ITU-T Recommendation Q.930 [72]). +- [60] ITU-T Recommendation H.223 (07/01): "Multiplexing protocol for low bit rate multimedia communication". +- [61] ITU-T Recommendation H.245: "Control protocol for multimedia communication". + +- [62] ITU-T Recommendation V.21 (11/88): "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [63] ITU-T Recommendation V.22 (11/88): "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [64] ITU-T Recommendation V.22bis (11/88): "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits ". +- [65] ITU-T Recommendation V.26ter (11/88): "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [66] ITU-T Recommendation V.31 (11/88): "Electrical characteristics for single-current interchange circuits using optocouplers". +- [67] ITU-T Recommendation V.32 (03/93): "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits". +- [68] ITU-T Recommendation V.34 (02/98): "A modem operating at data signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits". +- [69] ITU-T Recommendation V.42 (03/02): "Error-correcting procedures for DCEs using asynchronous-to-synchronous conversion". +- [70] ITU-T Recommendation X.30 (03/93): "Support of X.21, X.21 bis and X.20 bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN) ". +- [71] ITU-T Recommendation Q.920 (03/93): "ISDN user-network interface data link layer - General aspects". +- [72] ITU-T Recommendation Q.930 (03/93): "ISDN user-network interface layer 3 - General aspects". +- [74] 3GPP TS 23.146: "Technical realisation of facsimile Group 3 service - non-transparent". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +The term 'Mobile Station' ( MS ) in the present document is synonymous with the term 'User Equipment' ( UE ) as defined in 3GPP TR 21.905. + +The term 'TE2' in the present document is synonymous with the term 'TE' as defined in 3GPP TR 21.905. + +The term 'MT2' in the present document is synonymous with the term 'MT' as defined in 3GPP TR 21.905. + +For the purposes of the present document the following terms and definitions given in 3GPP TS 21.905 and the following apply: + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and 3GPP TR 25.990 and the following apply: + +| | | +|--------------|----------------------------------------------------------------------------------------------------------| +| CALL PROC | CALL PROCEEDING | +| CALL CONF | CALL CONFIRMED | +| CONNACK | CONNECT ACKNOWLEDGEMENT | +| EDGE channel | A general term referring to channels based on 8PSK modulation; i.e. TCH/F28.8, TCH/F32.0, and TCH/F43.2. | +| FTM | Frame Tunnelling Mode | +| PIAFS | PHS Internet Access Forum Standard | +| PHS | Personal Handyphone System | + +# 4 Access reference configuration + +Figure 1 presents the reference configuration for access to an A/Gb mode PLMN and GERAN Iu mode (see 3GPP TS 24.002). + +![Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode). The diagram shows a Mobile Station (MS) containing MT0 and MT2 (with TA). MT0 connects to a BSS/MSC. MT2 connects to a TE2 via reference point R and to a BSS/MSC via reference point Um.](7f17c430b9598e4d748a8041457810b3_img.jpg) + ++ : reference point. + TE2: V-type terminal. + TA: Terminal Adaptor. + GERAN: GSM/EDGE Radio Access Network. + CN: Core Network. + +Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode). The diagram shows a Mobile Station (MS) containing MT0 and MT2 (with TA). MT0 connects to a BSS/MSC. MT2 connects to a TE2 via reference point R and to a BSS/MSC via reference point Um. + +**Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode)** + +Within the scope of the present document the Mobile Termination MT0 means a fully integrated MS including data terminal and its adaptation functions. MT2 includes ITU-T V-series terminal adaptation functions among other MT functions. + +Figure 2 presents the access reference configuration for UTRAN Iu mode. There is no reference point identified for the TAF. The TAF is considered as a part of the Mobile Termination. + +![Figure 2: UTRAN Iu mode PLMN Access Reference Configuration. The diagram shows a User Equipment (UE) containing Mobile Equipment (ME) and USIM. ME contains Terminal Equipment (TE), Mobile Termination (MT), and TAF. TE connects to MT via reference point R. MT connects to an Access Network via reference point Uu. USIM connects to ME via reference point Cu.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +Figure 2: UTRAN Iu mode PLMN Access Reference Configuration. The diagram shows a User Equipment (UE) containing Mobile Equipment (ME) and USIM. ME contains Terminal Equipment (TE), Mobile Termination (MT), and TAF. TE connects to MT via reference point R. MT connects to an Access Network via reference point Uu. USIM connects to ME via reference point Cu. + +**Figure 2: UTRAN Iu mode PLMN Access Reference Configuration** + +# --- 5 Functions to support data services + +The main functions of the MT to support data services are: + +- functions to ensure conformity of terminal service requests to network capability; +- physical connection of the R reference point; +- flow control of signalling and mapping of user signalling to/from the PLMN access signalling; +- rate adaptation of user data (see 3GPP TS 44.021) and data formatting for the transmission SAP (3GPP TS 25.322); +- flow control of non-transparent user data and mapping of flow control for asynchronous data services; +- support of data integrity between the MS and the interworking function in the PLMN; +- end-to-end synchronization between terminals; +- filtering of status information; +- functions to support non-transparent bearer services e.g. termination of the Radio Link Protocol (RLP) and the Layer 2 Relay function (L2R) including optional data compression function (where applicable); +- terminal compatibility checking; +- optional support of local test loops. + +In addition, functions to support autocalling and autoanswering are optionally specified in accordance with ITU-T Recommendation V.250 (although the use of other autocalling/auto-answering procedures are not prohibited provided that mapping in a functionally equivalent way to 3GPP TS 24.008 call control is also provided). + +Other functional entities may be envisaged apart from the TAF. One of the physical interface to all these functions is the DTE/DCE interface to the MT. Normally, this DTE/DCE interface is associated with the TAF, if available. Therefore the access to any of these other functional entities, if implemented, via the DCE/DTE interface, are triggered by appropriate command sequences which are described in the applicable specifications (although the use of other procedures is not prohibited provided that mapping in a functionally equivalent way is also provided). These command sequences shall be issued by the DTE only when the MT is in the appropriate command status and there is no data connection pending. They are interpreted by an MT internal control function and result in an association of the DTE/DCE interface with the addressed function, if available. + +# --- 6 Support of non transparent Bearer Services + +In order to support asynchronous non transparent bearer services a Layer 2 Relay (L2R) function is included in the mobile termination. The details of the particular L2R function for the different asynchronous non transparent bearer services are contained in the appropriate 3GPP 27-series Specification. This clause describes the general aspects of the L2R function. + +The Layer 2 Relay (L2R) function provides for the reliable transportation of known, i.e. asynchronous non transparent, user protocols across the radio interface of a PLMN. The L2R functions are located in the Mobile Termination (MT) and the Interworking Function (IWF) associated with a Mobile Switching Centre (MSC). The L2R uses the services provided by the Radio Link Protocol (RLP) to transport the asynchronous non transparent protocol information between the MS and the IWF. + +## 6.1 Functions of the Layer 2 Relay + +The complete protocol reference models for data and telematic services are described in 3GPP TS 43.010. The subset of those protocol reference models relating to the L2R function is reproduced in figure 2A. + +![Figure 2A: Protocol stack diagram showing MS and IWF entities connected by a transparent higher layer protocol. The MS side has NTP and IFP protocols connected to an L2R entity. The IWF side has an L2R entity connected to the Radio Link Protocol. The L2R Protocol is shown between the two L2R entities.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +MS IWF + +\_\_\_\_\_ Transparent higher layer protocol \_\_\_\_\_ + +- NTP [ L2R ] — L2R Protocol — [ L2R ] - NTP — + +- IFP [ ] — Radio Link Protocol — [ ] - IFP — + +NTP Non Transparent Protocol +IFP Interface Protocol + +Figure 2A: Protocol stack diagram showing MS and IWF entities connected by a transparent higher layer protocol. The MS side has NTP and IFP protocols connected to an L2R entity. The IWF side has an L2R entity connected to the Radio Link Protocol. The L2R Protocol is shown between the two L2R entities. + +Figure 2A + +The Non Transparent Protocol (NTP) is normally a layer 2 protocol for OSI conformant protocols or an equivalent in the case of non OSI protocols. The Interface Protocol (IFP) is normally a layer 1 protocol for OSI conformant systems or equivalent for non OSI systems. + +The L2R can be considered to consist of 3 sub-functions, see figure 3. + +![Figure 3: Diagram of the L2R sub-functions. A large box labeled 'Relay Entity' contains three sub-entities: 'NTP Entity', 'L2RP Entity', and 'RLP Entity'. The NTP Entity is on the left, the L2RP Entity is on the top right, and the RLP Entity is on the bottom right. Lines connect the NTP Entity to the L2RP Entity and the RLP Entity, and the L2RP Entity to the RLP Entity.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +Relay Entity + +NTP Entity L2RP Entity + +RLP Entity + +Figure 3: Diagram of the L2R sub-functions. A large box labeled 'Relay Entity' contains three sub-entities: 'NTP Entity', 'L2RP Entity', and 'RLP Entity'. The NTP Entity is on the left, the L2RP Entity is on the top right, and the RLP Entity is on the bottom right. Lines connect the NTP Entity to the L2RP Entity and the RLP Entity, and the L2RP Entity to the RLP Entity. + +Figure 3 + +The 3 sub-functions are: + +- a Non Transparent Protocol Entity; +- a L2R Protocol Entity; +- a Relay Entity. + +The NTP-entity interfaces the L2R to the IFP-entity and provides an interface to the particular NTP. + +The L2RP-entity interfaces the L2R to the RLP-entity and provides an interface to the appropriate L2R protocol. + +The Relay-entity provides the mapping between the NTP-entity and the L2R-entity. If applicable, it contains the data compression function. The negotiable parameters are exchanged with the remote Relay-entity by means of the RLP XID frame. + +It should be noted that the inter-layer interfaces within the MS and the IWF and within the L2R is not specified by 3GPP. The description given is for explanatory purposes only and is not intended to indicate a method of implementation. Therefore, the specification of the L2R is in terms of the peer-peer protocols. Generally, the non transparent and interface protocols are specified elsewhere, e.g. ITU-T Recommendations V.110 or V.120. Thus the main specification for the L2R consists of the L2R peer-peer protocols. + +### 6.1.1 Layer 2 Relay in Frame Tunneling Mode + +L2R is used in FTM to transport asynchronous HDLC (see [44]) frames between the MS and the IWF. In this case there is no NTP entity on the IWF side. Instead, the L2R entity interfaces a conversion function that performs a mapping between asynchronous and synchronous HDLC frames, which are transported on a UDI or RDI bearer with X.31 flag stuffing as rate adaptation. Consequently there is no error correction or flow control on the fixed network leg. (The HDLC FCS is used by the higher layer protocol, and error correction and flow control are performed end-to-end between the two DTEs.) + +## 6.2 Radio Link Services Used + +The L2R function uses services defined in 3GPP TS 24.022. + +## 6.3 Flow Control - General Description + +A flow control active condition may take place under a number of circumstances: + +- end-to-end flow control (DTE to DTE matter); +- backpressure (buffers filling); +- receive not ready (RLP condition). + +It is possible that there may be an interaction between flow control active and inactive conditions in each circumstance. + +### 6.3.1 End to End Flow Control + +A DTE may wish to send a flow control active condition to another DTE. + +Provisions exist in the L2R entity to transfer a flow control active condition (sent by its associated DTE) to the other L2R entity as soon as possible. This mechanism in the L2R entities allows such a flow control condition to be put ahead of any queuing which exists in the L2R entities. + +Such a mechanism avoids undesirable build up of data buffers. + +The L2R entity, receiving a flow control active condition from its associated DTE, stops sending data to that associated DTE immediately. + +### 6.3.2 Back Pressure + +The L2R and RLP entities have buffers which may become full to a predetermined threshold for a number of reasons, e.g. severe radio fading, failure or slowness of DTE to react to end to end flow control, certain RNR conditions. When this predetermined threshold is reached, a flow control active condition is sent to the associated DTE which is then prevented from sending any data. Subsequently, the flow control inactive condition is sent to the associated DTE when the L2R or RLP entities have indicated that there is sufficient free capacity in their buffers for data flow from the associated DTE to proceed. + +The corresponding peer-layer procedure to assess the respective buffer conditions is a layer management matter and is not dealt with here. It is also considered an implementation matter to ensure that such procedure do not result in loss of data or considerable reduction in throughput. + +In FTM, back pressure is not applicable towards the DTE on the fixed network side, because there is no flow control mechanism on the fixed network leg. Consequently buffer overflow may occur leading to loss of data, which is left to the higher layer protocol to handle. + +### 6.3.3 Receive not Ready + +When the RNR condition arises, an RLP indication is sent to the other RLP entity which in turn shall send a flow control active condition to its associated L2R entity. That L2R entity shall then send a flow control active condition to its associated DTE. + +An RNR condition may result in the Execution of "back pressure" as mentioned under subclause 6.3.2. + +## 6.4 User initiated service level up and down grading (applies to A/Gb and GERAN Iu mode only) + +When the value of the negotiated UIMI parameter is greater than 0, the MS may at any time during the call, control, to some extent, the number of traffic channels to be used. This is done by signalling a higher or lower value for the Wanted Air Interface User Rate (WAIUR) and maximum number of traffic channels (mTCH). The network may assign an AIUR matching the WAIUR using up to mTCH traffic channels, provided that the resources are available (3GPP TS 22.034, 3GPP TS 23.034 and 3GPP TS 24.008). + +If the value of the RLP optional feature 'Up signalling' is negotiated to 1, the MS may receive a suggestion from the network to initiate an upgrading. This occurs when the following condition holds: + +The IWF: + +- 1) is receiving user data from the fixed network side at a higher rate than the current AIUR; or +- 2) in symmetrical calls only, can send user data towards the fixed network side at a higher rate than the current AIUR. + +The MS can detect the condition stated in 1) and 2) above by examining the value of the UP bit in the received RLP S and I+S frames. When the condition does not hold, the value of the UP bit is continuously 0. If the condition does hold, the number of 1s between two consecutive 0s indicates the number of traffic channels to upgrade by. There is no need to repeat this indication since the FCS protects it. For instance, if the UP bit sequence is ...01100... and the current number of assigned traffic channels is 2, then an upgrading 4 traffic channels is suggested. + +NOTE: From MSC/IWF's perspective a TCH/F28.8 or TCH/F43.2 EDGE configuration is identical to a multislot 2×TCH/F14.4 or 3×TCH/F14.4 configuration. Therefore, a factor of 1/2 or 1/3 has to be applied to the suggested increase when the assigned up link channel is TCH/F28.8 or TCH/F43.2 respectively. + +The MS may use the information signalled in the UP bit to find out when a service level upgrading may increase the data throughput. In order to initiate a service level upgrading, the value of UIMI shall be greater than the number of currently assigned channels. + +In order to determine when to downgrade, the MS may compare the rate of received and sent information in the RLP frames to the AIUR. If the rate of received and sent information is less than the current AIUR the MS may initiate a downgrading. + +User initiated service level up and down grading mechanism may also be used to modify the asymmetry preference, see subclause 6.5. This is achieved by sending a new value of the asymmetry preference in the BC-IE. + +## 6.5 Asymmetry preference indication (applies to A/Gb and GERAN Iu mode only) + +The MS's classmark may restrict the possible number of channels or modulation that may be assigned by the network in one of the directions. This may result in an asymmetric transmission, i.e., different numbers of channels or modulations are assigned in each direction. + +Asymmetric transmission may also result from a preference indication. At call set up, the MS may send an asymmetry preference indication in the BC-IE (see 3GPP TS 24.008). There are three options: + +- 1) no preference; +- 2) up link biased asymmetry preferred; +- 3) down link biased asymmetry preferred. + +If down or up link asymmetry preference is indicated, the network shall not assign EDGE channels on the unbiased link. If the network assigns EDGE channels on the biased link, it shall assign TCH/F14.4 on the unbiased link. The WAIUR shall then apply to the biased link. + +# --- 7 Structure of the 3GPP TS 27-series of Specifications + +The structure of the Specifications is as follows: + +3GPP TS 27.001 General on Terminal Adaptation Functions for Mobile Stations. + +3GPP TS 27.002 Terminal Adaptation Functions for Services using Asynchronous Bearer Capabilities. + +This document defines the interfaces and terminal adaption functions integral to a MT which enable the attachment of Asynchronous Terminals to a MT. + +3GPP TS 27.003 Terminal Adaptation Functions for Services using Synchronous Bearer Capabilities. + +This document defines the interfaces and terminal adaptation functions integral to a MT which enable the attachment of Synchronous Terminals to a MT. + +# 8 Functions common to all interfaces + +## 8.1 Synchronization of the Traffic Channel + +As long as there is no connection between the traffic channel and the interface to the TE this interface shall be terminated in the appropriate way. + +Prior to exposing the traffic channel of a PLMN connection to transmission of user data, the controlling entities of the connection shall assure the availability of the traffic channel(s). This is done by the so called synchronization process: + +- starting on the indication of "physical connection established" resulting from the PLMN inherent outband signalling procedure. This indication is given: + - for MO calls: on reception of the CONNECT message; + - for MT calls: on reception of the CONNECT ACKNOWLEDGE message; + - for mobile initiated in-call modification: on reception of the MODIFY COMPLETE message; and + - for network initiated in-call modification: on sending the RR/RRC message confirming the reconfiguration of the traffic channel (in A/Gb mode: ASSIGNMENT COMPLETE, HANDOVER COMPLETE, or CHANNEL MODE MODIFY ACKNOWLEDGE; in Iu mode: RADIO BEARER RECONFIGURATION COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, or PHYSICAL CHANNEL RECONFIGURATION COMPLETE); +- ending by indicating the successful execution of this process to the controlling entity, which then takes care of the further use of the inband information (data, status). + +During the call control phases (set-up and clear), the procedures at the V.-series DTE interfaces may be mapped completely to the out-of-band signalling procedure. The state of the S-bits and X-bits during the call control phases are in this case irrelevant to the DTE interface procedures. However, the "ready for data" condition (i.e. CTs 106 and 109) is derived from the status bits received by the TAF once synchronization is complete. Since half duplex operation is not supported by a PLMN, status bit SB is not needed to signal the turn around of the connection. + +### 8.1.1 Transparent services + +#### 8.1.1.1 Initial procedure for traffic channel types TCH/F4.8 and TCH/F9.6 + +With respect to the TAF, for the transparent bearer capability support the synchronization procedure with the channel codings 2.4 kbit/s, 4.8 kbit/s and 9.6 kbit/s is as follows: + +- sending of synchronization pattern 1/OFF (all data bits "1" / all status bits "OFF", all E-bits "1") to the IWF. In multislot transparent operation, the synchronisation pattern sent is 1/OFF with the exception of the bit positions S1, first X, S3, and S4 which contain the substream number and multiframe alignment pattern (see 3GPP TS 44.021); +- searching for detection of the synchronization pattern received from the IWF, and in multislot operation, also searching for the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" (see 3GPP TS 44.021) in bit position S4 and substream numbers in bit positions S1, first X, and S3. The value of the bits E4-E7 shall not be checked. + +#### 8.1.1.2 Initial procedure for traffic channel types TCH/F14.4 and TCH/F28.8 + +With respect to the TAF, for the transparent bearer capability support, the procedure with the TCH/F14.4 or TCH/F28.8 is as follows: + +- sending of synchronization pattern 1/OFF (all data bits "1" / status bits in M2 "OFF") to the network in the multiframe structure with the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" in the M1 (see 3GPP TS 44.021) and, in a multislot or TCH/F28.8 case, sending substream numbers in the bit M2; +- searching for the detection of the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" (see 3GPP TS 44.021) in the bit M1 originating from the network, and, in a multislot or TCH/F28.8 case, searching for substream numbers in the bit M2. (Any 5 bits sequence in the multiframe alignment pattern is unique, i.e. the multiframe alignment can take place by the recognition of five successive S1 bits). + +#### 8.1.1.3 Subsequent procedures for traffic channel types TCH/F4.8, TCH/F9.6, TCH/F14.4, and TCH/F28.8 + +When the synchronisation pattern and, in case of multislot, TCH/F14.4 or TCH/F28.8 operation the multiframe alignment pattern from the IWF have been recognized as a steady state (see note) the TAF continues sending the synchronization patterns to the IWF until a timer T (= 500 ms) expires. + +NOTE: An idle frame sent by the BSS and received by the MS has the same pattern as the synchronization pattern 1/OFF. + +At the moment when the message CONNECT (MO) or CONNACK (MT) is received at the MS, it is guaranteed that this pattern is received from the MSC/IWF with the exception of a loss of frame synchronization on the Abis interface. + +The handling of frame stealing in case of 2400 bit/s full rate data channels is implementation dependent. + +##### 8.1.1.3.1 V.-series interface + +During the synchronization process described above, i.e. while the synchronization pattern is being sent by the MT, CT106, 107 and 109 remain in the OFF condition. + +After the expiration of the timer T of each allocated traffic channel for the call, the X and SB bits received from the IWF are mapped on to CT 106 and CT 109, respectively, at the MT/DTE interface according to the filtering process described in subclause 8.2. The received SA bit, if available, is ignored. The condition on CT107 is changed from "OFF" to "ON", the data bits received from the IWF are mapped to CT104, and CT103 is mapped to the data bits sent towards the IWF. The transmitted SA (if available), SB and X bits shall be set to "ON". + +##### 8.1.1.3.2 X.-series interface + +Void. + +##### 8.1.1.3.3 S interface (I.420) + +Void. + +#### 8.1.1.4 Procedures for RLC + +With respect to the TAF for T bearer support, the procedure is as follows: + +- no access stratum SDUs are transmitted until an access stratum SDU is received. + +##### 8.1.1.4.1 V.-series interface + +Until the first access stratum SDU is received at the transmission SAP, CT 106, 107 and 109 remain in the OFF condition. At the reception of the first SDU, CT 106, CT 107 and CT 109 are changed from OFF to ON at the DCE/DTE (TE/TAF) interface. The data received in each SDU are mapped to CT 104 and data on CT 103 are mapped to SDUs sent toward the RNC. + +### 8.1.2 Non-transparent services + +With respect to the TAF, for non-transparent bearer capability support, the synchronization procedure in A/Gb and GERAN Iu mode is as follows: + +- firstly, receiving frames on all allocated traffic channels for the call; +- secondly, initiating the RLP link establishment by sending a RLP-SABM across the radio interface. + +In UTRAN Iu mode, the TAF shall initiate the RLP after the physical connection has been established. + +#### 8.1.2.1 V.-series interface + +During the synchronization process described above, i.e. while the synchronization pattern is being sent by the MT, CT106, 107 and 109 remain in the OFF condition. + +When the RLP link has been established, CT107 shall be changed from "OFF" to "ON". From this time the information from/to the RLP, including status changes, shall be mapped by the L2R entity applicable to the particular bearer capability (3GPP TS 27.002 "L2R functionality"). + +#### 8.1.2.2 X.-series interface + +Void. + +#### 8.1.2.3 S interface (I.420) (does not apply to UTRAN Iu mode) + +Void. + +### 8.1.3 Action on loss of synchronization + +#### 8.1.3.1 Loss at the TAF-radio interface + +In A/Gb and GERAN Iu mode, if the TAF detects a loss of synchronisation on one or more channels, it initiates the re-synchronisation process. The TAF searches for the data frame structure in those channels in which the synchronisation has been lost according to the initial procedures described in subclauses 8.1.1 and 8.1.2. The information received from the channels shall continue to be processed as if the synchronisation had not been lost, i.e. corrupted data is forwarded towards RLP entity or TE during the re-synchronisation process. No action shall be taken on the frames being transmitted towards the MSC, other than to continue sending them normally. + +In UTRAN Iu mode, no action shall be taken. + +#### 8.1.3.2 Loss at the TAF-terminal interface + +Void. + +## 8.2 Filtering of Channel Control Information (A/Gb or GERAN Iu mode transparent mode only) + +### 8.2.1 General + +The DTEs used at the MS side of the PLMN conforms to ITU-T's DTE/DCE interface specifications, which assume basically an error-free environment, i.e.: + +- limited distance, point-to-point local interconnection of the interface circuits for data and status; +- steady state signalling. + +The envisaged use of these DTEs in the PLMN environment leads to the exposure of these "interconnections" to the PLMN radio channel. To assure proper operation even under these conditions appropriate measures have to be taken. In the non transparent case the RLP satisfies the requirement for both data and status lines. + +In the transparent case the: + +- data line aspects have to be dealt with end-to-end by the users; while +- status line aspects are of concern to the network, and are dealt with in the following. + +### 8.2.2 Filtering process to be applied + +Filtering of channel control information is relevant only at the MS side and in the transparent mode of operation. By applying filtering measures the condition of a DTE/DCE control interchange circuit, for which the DTE constitutes the + +information sink, is preserved until another condition is signalled for an "integration time" period by the channel control information (status bits) of the rate adaptation scheme. + +The filtering mechanism is understood to reside between the rate adaptation function (information source) and the DTE (information sink). It receives the unfiltered condition of the respective control interchange circuit set according to the actual sequential appearance of the individual associated status bits and forwards the filtered condition to the DTE. + +The filtering process starts when the traffic channel synchronization ends with the expiry of timer T. + +#### 8.2.2.1 V.-series interface + +##### CT 106 + +In the transparent mode the remote inband control of this circuit is needed to support a modem retrain procedure. + +OFF-ON transition at the MS authorizes the DTE to send data; if wrongly set, loss of data may occur. + +ON-OFF transition at the MS causes the DTE to cease transmitting data; set wrongly may impair the performance in connection usage. + +##### CT 109 + +In the transparent mode the remote inband control of this circuit is needed to: + +- trigger the interpretation of received data; +- indicate to the DTE the state of the connection. + +OFF-ON transition at the MS authorizes the DTE to rely on the condition of the received data interchange circuit, set wrongly may cause receipt of wrong data, while setting late may cause loss of data. + +ON-OFF transition at the MS: + +- causes the DTE to cease receiving data; +- may initiate release of the connection during a data phase by the DTE giving an ON-OFF transition on circuit 108/2. + +Setting this condition wrongly may cause loss of data and potentially release the connection. + +#### 8.2.2.2 X.-series interface + +Void. + +#### 8.2.2.3 Filtering mechanism + +##### 8.2.2.3.1 Traffic channel types TCH/F4.8 and TCH/F9.6 + +A filtering mechanism shall be provided by an integration process on those SB and X bits carrying status information in the V.110 frame or in the multiframe structure. The integration periods applied are: + +| V-series | Transition | Integration period | Status stream | +|----------|------------|--------------------|---------------| +| CT 106 | Off-On | 1 s | X | +| CT 106 | On-Off | 1 s | X | +| CT 109 | Off-On | 200 ms | SB | +| CT 109 | On-Off | 5 s | SB | + +The integration process shall ensure that the interchange circuits do not change state in response to spurious transitions of the status bits during the integration period. + +The integration process shall operate reliably with error characteristics as specified in 3GPP TS 45.005. + +##### 8.2.2.3.2 Traffic channel type TCH/F14.4 + +To change the state of CT 109 or CT 106, it is required that at least two consecutive SB-bits or X-bits, respectively, carry the same value. + +## 8.3 Terminal Compatibility Decision + +The establishment of a mobile terminated connection depends on a positive decision on the terminal compatibility. The Mobile Station (MS) contributes to this process by performing (depending on the individual call set-up condition): + +- a compatibility check; +- the selection of the appropriate terminal function; and +- the indication of compatibility requirements to the PLMN; + +initiated by a call set-up request from the PLMN. The aforementioned functions shall be carried out as follows. + +### 8.3.1 Compatibility Check + +Annex B of 3GPP TS 24.008 applies, particularly clause B.3, subclauses B.3.1 and B.3.2. As regards the therein mentioned user-to-user compatibility checking the following applies: + +When the calling user requests a service with user-to-user compatibility significance indicated by the presence of HLC and LLC information element in the call set-up request, the MS shall check that the service supported by the called user matches concerning the contents of the HLC/LLC information element. If a mismatch is detected, then the MS shall reject the offered call using the cause No.88 "Incompatible Destination". + +### 8.3.2 Selection of Appropriate Terminal Function + +The MS shall select the appropriate terminal functions following a positive result of the compatibility check and/or forwarding the indication of compatibility requirements to the PLMN. + +### 8.3.3 Indication of Compatibility Requirements to the PLMN + +#### 8.3.3.1 Indication in case of Mobile terminating calls + +In support of: + +- PSTN originated calls; and +- ISDN originated calls using 3,1 kHz audio Bearer Capability (BC); as well as +- ISDN originated calls using unrestricted digital Bearer Capability but not specifying all parameters for deducing a Bearer Service. + +Mobile specific requirements to be dealt with in the Bearer Capability information element the call confirmed message has been introduced in the call control protocol (3GPP TS 24.008). This also allows for re-negotiation of specific parameters at the beginning of the connection set-up process. The specific parameters are: + +- a) mobile specific requirements: + - Connection element (transparent/non transparent); + - Structure (note 1); + - Synchronous/Asynchronous (note 8); + - Rate adaptation/other rate adaptation (note 9); + - User information layer 2 protocol (note 1); + - Intermediate rate (note 2), (note 3); + - Modem Type (note 1), (note 3); + +- User Rate (note 3); +- Compression , +- Fixed network user rate, (note 3) (note 4); +- Other modem type, (note 3) (note 4); +- User initiated modification indication (note 4). + +The following parameters are indicated by the MS to the network, only: + +- Radio Channel Requirement; +- Acceptable channel codings (note 5); +- Maximum number of traffic channels, (note 5); +- Wanted air interface user rate (note 6) (note 7); +- Asymmetry preference indication (note 7). + +NOTE 1: This parameter is correlated with the value of the parameter connection element. + +NOTE 2: For non-transparent services this parameter is correlated with the value of the parameter negotiation of intermediate rate requested. + +NOTE 3: Modification of these parameters may be proposed by the MS. The Network may accept it or not. + +NOTE 4: This parameter shall be included by the MS only if it was received from the network. + +NOTE 5: This parameter shall be included only if the parameter 'fixed network user rate' is included. + +NOTE 6: This parameter shall be included only for non-transparent services and if the parameter 'fixed network user rate' is included. + +NOTE 7: This parameter has to be included if EDGE channel coding(s) are included in Acceptable channel codings. In cases where this parameter would not otherwise be included, the value is set to 'Air interface user rate not applicable' or 'User initiated modification not requested' or "No preference". + +NOTE 8: For FTM and PIAFS, this parameter may be negotiated as in table B.4e. How the subscription for BS20 is assured, is an operator matter. + +NOTE 9: For FTM, PIAFS or Multimedia, this parameter may be negotiated as in table B.4f. + +b) requirements with effects at the partner terminal: + +- Number of data bits; +- Number of stop bits; +- Parity. + +The MS indicates the radio channel requirement in the call confirmed message. If the MS indicates the support of "dual" (HR and FR channels) the final decision, which radio channel is chosen, is done by the network in an RR message. The radio channel requirement is ignored in UTRAN Iu mode, see table B.5a in Annex B. + +If the network proposes optional support of both transparent and non transparent connection elements, but does not indicate a user information layer 2 protocol, the MS shall set the appropriate value, if choosing non transparent in the call confirmed message and out-band flow control is not requested, see B.1.1.2. + +Additionally the values of the parameters structure, modem type and intermediate rate have to be set in conformance with the values of the parameters radio channel requirements, negotiation of intermediate rate requested and connection element. + +Subclause B.1.1.2 and table B.1 in the annex B describe the negotiation procedure. Annex B table B.4 describes the selection of the modem type and the dependence on the value of the parameter connection element. Annex B table B.4 + +describes the selection of the intermediate rate and user rate and their dependence upon the value of the NIRR parameter and the equipment capabilities. + +The following MT cases can be deduced from the individual call set-up request conditions: + +- a) If the set-up does not contain a BC information element, the MS in the call confirmed message shall include any BC information (single or multiple BC-IE). The MS may use the information provided in the BACKUP BC information element (see 3GPP TS 29.007 and 3GPP TS 24.008) to deduce the requested service. Note, that the presence of the BACKUP BC-IE does not change the condition of "no BC-IE received", that means in particular that the MS shall include any BC-IE (as mentioned before) and shall not negotiate parameter values where the MSC has to offer a value in the BC-IE first, as e.g., for the parameter "compression". If multiple BC-IEs are present, one BC-IE shall indicate the information transfer capability "speech". A 3,1 kHz multimedia BC-IE together with a speech BC-IE indicates the support of a fallback to speech. A UDI/RDI multimedia BC-IE together with a speech BC-IE indicates the support of service change and fallback (see 3GPP TS 29.007 and 3GPP TS 24.008). +- b) If the set-up message contains a single BC-IE, the MS in the call confirmed message shall use either a single BC-IE, if it wants to negotiate mobile specific parameter values or, unless otherwise specified, no BC-IE, if it agrees with the requested ones. +- c) If the set-up contains a multiple BC-IE, the MS in the call confirmed message shall use either a multiple BC-IE, if it wants to negotiate mobile specific parameter values or, unless otherwise specified, no BC-IE, if it agrees with the requested ones. + - For a 3,1kHz multimedia setup the MS may either accept the possibility of a fallback to speech by responding with two BC-IEs, or turn the call to a speech call by sending only a speech BC-IE in the call confirmed message or turn the call to a multimedia only call (i.e. no fallback to speech allowed) by sending only a multimedia BC-IE, in the call confirmed message. + - For a UDI/RDI multimedia setup, the MS may either accept the possibility of service change by responding with two BC-IEs , or turn the call to a speech call by sending only a speech BC-IE in the call confirmed message, or turn the call to a multimedia call by sending only a multimedia BC-IE in the call confirmed message. + - For facsimile, a single BC-IE, containing fax group 3 only, shall be used if a multiple BC-IE requesting speech alternate fax group 3 is received and the MS is not able to support the speech capability. Annex B, table B.7, describes the negotiation rules. + +If the BC-IE contains 3,1 kHz ex PLMN, the MS is allowed to negotiate all mobile specific parameter values listed above. If the BC-IE contains facsimile group 3, the MS is not allowed to negotiate any mobile specific parameter value. In any case, if the set-up message requests a "single service", the MS shall not answer in the call confirmed message requesting a "dual service". + +However, for dual services with repeat indicator set to "circular (alternate)" or to "service change and fallback" the MS may change the sequence of dual BC-IEs within the call confirmed message (preceded by the same value of the repeat indicator), if it wants to start with a different Bearer Capability than proposed by the network as the initial one. + +In addition, the MS may propose to the network to modify User Rate, Modem Type and Intermediate Rate in the CALL CONFIRMED message. The network may accept or release the call. + +If the BC-IE received from the network contains the parameters 'fixed network user rate', 'other modem type' and possibly the 'user initiated modification', the MS shall either: + +- a) include no BC-IE or a BC-IE without these parameters in the call confirmed message, i.e. the MS discards these parameters (only allowed in A/Gb mode); or +- b) include the possibly modified values for the 'fixed network user rate' and 'other modem type' in the BC-IE of the call confirmed message. The network might accept or reject the modified values. In this case the MS shall also include the parameters 'maximum number of traffic channels' and 'acceptable channel codings'. Additionally for non-transparent services, the MS shall also include the parameters 'wanted air interface user rate' and the 'user initiated modification indication'. The parameters 'acceptable channel codings extended' and 'asymmetry indication' may also be included. + +In case a), the MS shall use the fall-back bearer service indicated by the remaining parameters of the BC-IE on a single slot configuration (reference 3GPP TS 44.021). + +In case b), the MS shall use in A/Gb or GERAN Iu mode a singleslot or multislot configuration according to the rules defined in 3GPP TS 44.021, 3GPP TS 48.020 and 3GPP TS 24.022. + +If the 'acceptable channel codings' is indicated by the MS, the decision which channel coding is used is done by the network and indicated to the mobile station with a RR message. This RR message may also assign an asymmetric channel coding. The 'acceptable channel codings' parameter takes precedence over the 'negotiation of intermediate rate requested' parameter for non-transparent services. Also the intermediate rate and user rate per traffic channel in a multislot configuration are not indicated by the 'intermediate rate' and 'user rate' parameters of the BC-IE, but depend on the chosen channel coding only. + +If no BC-IE is received in the SETUP message, the MS may include the parameters 'fixed network user rate', 'other modem type' etc. (i.e. octets 6d, 6e, 6f, and 6g, see 3GPP TS 24.008) in the BC-IE of the CALL CONFIRMED message. However, in this case, the network may release the call if it does not support these parameters. + +If FNUR = 33.6 kbit/s is agreed on in the setup of a 3.1 kHz multimedia call, the modems may handshake to 31.2 kbit/s or 28.8 kbit/s. In this case the MS receives a MODIFY message from the MSC to indicate the new data rate, and shall respond with a MODIFY COMPLETE message (see 3GPP TS 24.008), if it supports the requested modification. If the MS does not support the requested modification, it shall respond with a MODIFY REJECT message. The MT shall indicate the new data rate to the TE (e.g. using the ITU-T Recommendation V.80 inband signalling) in order to cause the TE to use stuffing to adapt the 31.2 or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the TE and IWF. + +#### 8.3.3.2 Indication in case of Mobile originating calls + +In support of mobile originating calls the values of BC-IE parameters are requested in the set-up message from the MS. If the MS indicates the support of both transparent and non transparent connection elements the network shall return its choice in the call proceeding message. The MS is not allowed to indicate support of both transparent and non transparent, if the MS also requests out-band flow control, i.e. it does not indicate a layer 2 protocol. + +Additionally the value of the parameter modem type has to be set depending on the value of the parameter connection element as described in annex B, table B.4a. + +The set-up message contains a single or multiple BC-IE. If multiple BC-IEs are present, one BC-IE shall indicate the information transfer capability "speech". + +For a 3,1 kHz multimedia call, the setup message contains either a multimedia BC-IE indicating a multimedia only call request (i.e. no fallback to speech allowed) or both a 3,1 kHz multimedia BC-IE and a speech BC-IE to indicate the support of a fallback to speech (see 3GPP TS 29.007 and 3GPP TS 24.008). + +For a UDI/RDI multimedia call, the setup message contains either a multimedia BC-IE indicating a multimedia only call request, or both a multimedia BC-IE and a speech BC-IE (in any order) to indicate the support of service change and fallback (see 3GPP TS 29.007 and 3GPP TS 24.008). The latter is not applicable to multimedia calls with FNUR=32.0 kbit/s. + +If the set-up message requests a "single service", the network shall not answer in the call proceeding message requesting a "dual service". Alternatively the network shall answer with a single BC-IE containing fax group 3 if a multiple BC-IE requesting speech alternate fax group 3 is received but the network does not allow the use of this alternate service. Annex B, table B.7, describes the negotiation rules. + +If the MS requests a "dual service" the network is not allowed to change the sequence of the service, a change may however occur due to the called user and this may then be relayed back to the originating MS by the network. + +If the setup message requests a 3.1 kHz multimedia service with fallback, the network may return both BC-IEs in the same order to accept the request, or a single BC-IE if fallback or one of the requested services are not allowed. + +If the setup message requests a UDI/RDI multimedia service with fallback, the network may return both BC-IEs in the same order to accept the request, both BC-IEs in the reverse order (relayed from terminating User), or a single BC-IE if fallback, service change or one of the requested services are not allowed. + +If the set-up message indicates that negotiation of intermediate rate is requested then the network shall behave as described in annex B, table B.4b. + +Unless otherwise specified, if no BC-IE parameter needs negotiation it is up to the network if it sends a CALL PROCEEDING message (with or without a BC-IE) towards the MS or not. + +For MS to network direction, octet 6e shall be included whenever octet 6d is included (see 3GPP TS 24.008). + +For multislot, TCH/F14.4, and EDGE operations and in Iu mode the MS shall include an appropriate set of the parameters 'fixed network user rate', 'other modem type', 'maximum number of TCH' and 'acceptable channel codings' in the BC-IE of the SETUP message. If EDGE channel coding(s) are included in ACC for transparent calls, the 'Wanted air interface user rate'-parameter shall be set to 'Air interface user rate not applicable' and the 'User initiated modification indication'-parameter to 'User initiated modification not requested'. In a non-transparent multislot operation, the MS shall also include the parameters 'wanted air interface user rate' and 'user initiated modification indication' in the BC-IE of the SETUP message. In a non-transparent TCH/F14.4 or EDGE operation or in Iu mode the MS shall also include the parameter 'wanted air interface user rate'. In non-transparent EDGE operation the MS shall also include the parameter 'asymmetry preference indication'. It shall also set the other parameters of the BC-IE (i.e. 'user rate') to values identifying fall-back values. Depending on the network two situations can be distinguished: + +a) The network supports the requested operation: + +- in this case the network shall include the parameter 'fixed network user rate', 'other modem type' and possibly 'user initiated modification' in the BC-IE(s) of the CALL PROCEEDING message, irrespective whether or not they contain modified values or just a copy of the received ones; +- the 'acceptable channel codings' indicated by the MS in the SETUP message takes precedence over the 'negotiation of intermediate rate requested' parameter for non-transparent services. The intermediate rate per traffic channel and the user rate per traffic channel is dependent on the chosen channel coding only. The chosen channel coding is indicated to the mobile station by the network with an RR message. + +b) The network does not support the requested operation: + +- in this case, in A/Gb mode, the BC-IE of the CALL PROCEEDING message does not contain the parameters 'fixed network user rate' and 'other modem type' or no BC-IE is included in the CALL PROCEEDING message at all. The mobile station shall then discard the parameters 'fixed network user rate', 'other modem type', 'maximum number of TCH', 'acceptable channel codings' 'wanted air interface user rate' and 'user initiated modification indication' sent with the SETUP message and apply the fall-back bearer service; +- in Iu mode the network shall release the call. + +In case a), the MS shall use in A/Gb and GERAN Iu mode a singleslot or multislot configuration according to the rules defined in 3GPP TS 44.021, 3GPP TS 48.020 and 3GPP TS 24.022. + +In case b), the MS shall use in A/Gb mode the fall-back bearer service indicated by the remaining parameters of the BC-IE on a single slot configuration (reference 3GPP TS 44.021). + +If FNUR = 33.6 kbit/s is agreed on in the setup of a 3.1 kHz multimedia call, the modems may handshake to 31.2 kbit/s or 28.8 kbit/s. In this case the MS receives a MODIFY message from the MSC to indicate the new data rate, and shall respond with a MODIFY COMPLETE message (see 3GPP TS 24.008), if it supports the requested modification. If the MS does not support the requested modification, it shall respond with a MODIFY REJECT message. The MT shall indicate the new data rate to the TE (e.g. using the ITU-T Recommendation V.80 inband signalling) in order to cause the TE to use stuffing to adapt the 31.2 kbit/s or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the TE and IWF. + +#### 8.3.3.3 Differences in validity of BC parameter values in A/Gb mode, GERAN Iu mode and UTRAN Iu mode + +The validity of a BC parameter value, either in the SETUP or CALL CONFIRMED message, may differ from A/Gb mode to GERAN Iu mode and to UTRAN Iu mode. Certain parameters are irrelevant in UTRAN or GERAN Iu mode and any value given is valid and ignored. These parameters may be available in the BC IE. For those parameters that are relevant in UTRAN Iu mode, GERAN Iu mode and A/Gb mode, certain values may be invalid in one of the systems. Invalid parameter values may cause rejection of the BC and subsequent release of the call. + +Parameters that are ignored in UTRAN or GERAN Iu mode may be set to default values, or to specific values in view of an eventual handover to A/Gb mode. They may also be set to values that make call setup in current system impossible. This indicates the need for a handover to another radio access technology. Parameter values that are invalid in one system may also result in unsuccessful handover from the other system. + +Table B.5a in annex B lists parameters that are ignored in UTRAN or GERAN Iu mode and parameter values which validity is different in A/Gb mode, GERAN Iu mode and UTRAN Iu mode. + +## 8.4 Test Loops + +In principle, both V-series and X-series interfaces allow for an activation of local or remote test loops by the terminal (see ITU-T Recommendations V.54/X.150). A comprehensive solution of such test loops in a PLMN system has to consider the special conditions of the interface between the terminal (part of the MS) and the transmission equipment (part of the modem pool of a particular IWF within the MSC). In addition, the impact of the radiolink is to be taken into account with respect to the test objectives. Due to those special conditions a PLMN system is not capable to support remote test loops. It is an implementation choice to what extent the activation of local test loops by the terminal is supported in the MT. + +## 8.5 Alternate speech/facsimile group 3 + +### 8.5.1 In case of A/Gb mode + +This alternate service may be initiated by a manual procedure where CT106, CT107, CT108.2 and CT109 are set in the OFF condition. + +Selection of the data phase (from the speech phase) may be by manual intervention via the MS causing ICM by means of CT108.2 going to ON condition, refer to 3GPP TS 03.45. The ensuing data phase shall follow all the operational procedures as described in 3GPP 27-series. + +Selection of the speech phase (from the data phase) may be by manual intervention via the MS causing ICM (phone off-hook condition at the MT and data call end condition at the TE). + +During the ensuing speech phases, CT107, CT106 and CT109 shall be maintained in the OFF condition. + +Subsequent re-selection of the data phase may be by manual intervention via the MS causing CT108.2 going to ON condition initiating ICM. At this point, re-synchronization shall take place as described in subclause 8.1. + +### 8.5.2 In case of UTRAN Iu mode + +Refer to subclauses 9.2.1.1 and 9.2.2.1 in 3GPP TS 23.146. + +## 8.6 Multislot configuration split/combine function + +In multislot configurations using multiple parallel channels the data flow is split into substreams between the Split/Combine-function in the TAF and the network. + +### 8.6.1 Non-transparent data + +In non-transparent data operations the N(S)-numbering in the RLP-header is used for controlling the order of the data in the substreams (reference 3GPP TS 24.022). + +### 8.6.2 Transparent data + +In transparent multislot configurations (TCH/F9.6 or TCH/F4.8) status bits S1, S3 and the X-bit between the D12 and D13 are used for transferring substream numbering information. This S4-bit is used for frame synchronization between the parallel substreams (reference 3GPP TS 44.021). + +In case of a transparent multislot configuration using TCH/F14.4 channel coding, bit M1 in the 290-bit radio interface block is used for frame synchronization between the parallel substreams, whereas bit M2 carries status information, NIC codes and substream numbering as described in 3GPP TS 44.021. + +In transparent TCH/F28.8 channels, bits M1 and M2 are used as described above for transparent TCH/F14.4 channels. + +## 8.7 EDGE multiplexing function + +In EDGE configurations the number of channels across the air interface and that of substreams between BTS and MSC do not necessarily match. In such cases a multiplexing function is included at MS and BTS (3GPP TS 44.021 and 3GPP TS 48.020). These functions distribute data between the substreams and radio channels. + +## 8.8 Seamless data rate change + +If the modems change the data rate during an ongoing multimedia call (using the ITU-T Recommendation V.34 seamless data rate change mechanism), the MSC initiates a MODIFY message (see 3GPP TS 24.008) to indicate the new data rate to the MS. The MT shall indicate the new data rate to the TE (e.g. using the ITU-T Recommendation V.80 inband signaling) in order to cause the TE to use stuffing to adapt the 31.2 kbit/s or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the TE and IWF. + +# --- Annex A (informative): List of Bearer Capability Elements + +This annex lists the PLMN Bearer Capability Elements which need to be provided to support Terminal adaptation function to Interworking control procedures. Some parameters are ignored in GERAN or UTRAN Iu mode although present in the BC-IE. The validity of parameter values may also differ from A/Gb mode to GERAN Iu mode and to UTRAN Iu mode. The ignored parameters and the difference of parameter value validity in A/Gb mode, GERAN Iu mode and UTRAN Iu mode are listed in table B.5a in annex B. + +## Elements and their Values: + +### Information Transfer Capability: + +This element is relevant between the IWF and the fixed network. + +Values: + +- Speech: +- Unrestricted Digital: +- Group 3 Facsimile (note 1): +- 3,1 kHz Ex PLMN (note 2): +- Restricted Digital (note 3): + +NOTE 1: Used for facsimile transmission, unrestricted digital between MT and IWF and 3,1 kHz audio from IWF towards the fixed network. + +NOTE 2: Unrestricted digital between MT and IWF and 3,1 kHz audio from IWF towards the fixed network. + +NOTE 3: Unrestricted digital between MT and IWF and restricted digital information from IWF towards the fixed network; this value is signalled in the "Other ITC" element, due to a lack of further code points in the "ITC" element. + +### Transfer Mode: + +This element is relevant between MT and IWF + +Values: - Circuit + +### Structure: + +This element is relevant between MT and IWF. + +Values: - Service Data Unit Integrity (note 4) +- Unstructured (note 5) + +NOTE 4: Applicable for connection element "non transparent". + +NOTE 5: Applicable for connection element "transparent". + +### Configuration: + +This element is relevant for a PLMN connection. + +Values: - Point to point + +### Establishment: + +This element is relevant for a PLMN connection. + +Values: - Demand + +### **Sync/Async:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network. + +Values: + +- Synchronous +- Asynchronous + +### **Negotiation:** + +This element is relevant between MT and IWF. + +Values: + +- In band negotiation not possible + +### **User Rate:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network, except in case the parameter FNUR is present. + +Values: + +- 0.3 kbit/s +- 1.2 kbit/s +- 2.4 kbit/s +- 4.8 kbit/s +- 9.6 kbit/s +- 19.2 kbit/s (see note 6) + +NOTE 6: This value cannot be signalled between MT and IWF, but it can be used according to the rules in 3GPP TS 29.007 (tables 7A and 7B) for such connections. + +### **Intermediate Rate:** + +This element is relevant between MT and BSS and BSS and IWF + +Values: + +- 8 kbit/s +- 16 kbit/s + +### **Network Independent Clock on Tx:** + +This element is relevant between TE/TA and MT in the transmit direction. + +Values: + +- Not required +- Required + +#### **Network Independent Clock on Rx:** + +This element is relevant between TE/TA and MT in the receive direction. + +Values: + +- Not accepted +- accepted + +#### **Number of Stop Bits:** + +This element is relevant between the TE/TA and MT and between IWF and fixed network in case of asynchronous transmission. + +Values: + +- 1 bit +- 2 bit + +#### **Number of Data Bits Excluding Parity If Present:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network in case of a character oriented mode of transmission. + +Values: + +- 7 bit +- 8 bit + +### **Parity Information:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network for a character oriented mode of transmission. + +Values: + +- Odd +- Even +- None +- Forced to 0 +- Forced to 1 + +### **Duplex Mode:** + +This element is relevant between MT and IWF. + +Values: + +- Full Duplex + +### **Modem Type:** + +This element is relevant between the IWF and the fixed network in case of 3,1 kHz audio ex-PLMN information transfer capability. + +Values: + +- V.21 +- V.22 +- V.22 bis +- V.26 ter +- V.32 +- autobauding type 1 +- none + +### **Radio Channel Requirement:** + +This element is relevant between MT and BSS + +Values: + +- Full Rate support only Mobile Station +- Dual Rate support Mobile Station/Half Rate preferred +- Dual Rate support Mobile Station/Full Rate preferred + +### **Connection Element:** + +This element is relevant between MT and IWF + +Values: + +- Transparent +- Non Transparent +- both, Transparent preferred +- both, Non transparent preferred + +### **User Information Layer 2 Protocol:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network. + +Values: + +- ISO/IEC 6429 +- Character oriented Protocol with no Flow Control mechanism + +### **Signalling Access Protocol:** + +This element is relevant between TE/TA and MT. + +Values: - I.440/450 + +#### **Rate Adaptation:** + +This element is relevant between IWF and the fixed network. + +Values: - V.110/X.30 +- X.31 flagstuffing +- no rate adaptation +- V.120 (note 7) +- PIAFS (note 7) +- H.223 and H.245 (note 7) + +NOTE 7: This value is signalled in the "Other Rate Adaption" element, due to a lack of further code points in the "Rate Adaption" element. + +#### **Coding Standard:** + +This element refers to the structure of the BC-IE defined in 3GPP TS 24.008. + +Values: - GSM + +### **User Information Layer 1 Protocol:** + +This element characterizes the layer 1 protocol to be used between MT and BSS (Um interface) according to 3GPP TS 45.001, or between the MT and the RNC (Uu interface). + +Values: - default + +#### **Negotiation of Intermediate Rate requested:** + +This element is relevant between MT and BSS and BSS and IWF. + +Values: - no meaning associated +- 6 kbit/s radio interface is requested for a full rate channel with a user rate up to and including 4,8 kbit/s, non transparent service + +#### **Compression:** + +This element is relevant between MT and IWF. + +Values: - compression possible/allowed +- compression not possible/allowed + +#### **Rate adaption header / no header:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: - Rate adaption header not included +- Rate adaption header included + +#### **Multiple frame establishment support in data link:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: - Multiple frame establishment not supported. Only UI frames allowed. +- Multiple frame establishment supported. + +#### **Mode of operation:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: - Bit transparent mode of operation +- Protocol sensitive mode of operation + +#### **Logical link identifier negotiation:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: + +- Default, LLI=256 only +- Full protocol negotiation (note 8) + +NOTE 8: A connection over which protocol negotiation is executed as indicated in the "In-band / out-band negotiation" parameter. + +#### **Assignor / assignee:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: + +- Message originator is „default assignee" +- Message originator is „assignor only" + +#### **In-band / out-band negotiation:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T Recommendation V.120 rate adaptation. + +Values: + +- Negotiation is done with USER INFORMATION messages on a temporary signalling connection +- Negotiation is done in-band using logical link zero. + +#### **Fixed network user rate, FNUR (note 12)** + +This element is relevant between the IWF and the fixed network. + +Values + +- Fixed network user rate not applicable (note 9) +- 9,6 kbit/s +- 14,4 kbit/s +- 19,2 kbit/s +- 28,8 kbit/s +- 32,0 kbit/s +- 38,4 kbit/s +- 48,0 kbit/s +- 56,0 kbit/s +- 64,0 kbit/s + +NOTE 9: Not used by currently specified services. + +#### **Wanted air interface user rate, WAIUR (note 12)** + +This element is relevant between the MT and the IWF + +Values + +- Air interface user rate not applicable +- 9,6 kbit/s +- 14,4 kbit/s +- 19,2 kbit/s +- 28,8 kbit/s +- 38,4 kbit/s +- 43,2 kbit/s +- 57,6 kbit/s +- interpreted by the network as 38,4 kbit/s (note 10) + +NOTE 10: Certain code points, if used, are interpreted by the network as 38.4 kbit/s in this version of the protocol, ref 3GPP TS 24.008. + +#### **Acceptable channel codings, ACC (note 12)** + +This element is relevant between the MT and the IWF. + +Value: + +- TCH/F4.8 acceptable +- TCH/F9.6 acceptable +- TCH/F14.4 acceptable +- TCH/F28.8 acceptable +- TCH/F32.0 acceptable (Applicable to multimedia 32 kbit/s, 56 kbit/s and 64 kbit/s and synchronous transparent 56 kbit/s and 64 kbit/s services only) +- TCH/F43.2 acceptable (Applicable to non-transparent services only.) +- none (note 10a) + +NOTE10a: No channel coding (defined by selecting none of the above). + +#### **Maximum number of traffic channels, MaxNumTCH (note 12)** + +This element is relevant between the MT and the IWF. + +Value: + +- 1 TCH +- 2 TCH +- 3 TCH +- 4 TCH +- 5 TCH +- 6 TCH +- 7 TCH (note 11) +- 8 TCH (note 11) + +NOTE11: Not used by currently specified services. + +#### **Other modem type, OMT (Note 12)** + +This element is relevant between the IWF and the fixed network in case of 3,1 kHz audio ex-PLMN + +Values: + +- no other modem type specified in this field +- V.34 + +### **User initiated modification indication, UIMI (Note 12)** + +This element is relevant between the MT and the IWF. + +Values: + +- user initiated modification not requested +- user initiated modification upto 1 TCH requested +- user initiated modification upto 2 TCH requested +- user initiated modification upto 3 TCH requested +- user initiated modification upto 4 TCH requested + +### **Asymmetry preference indication (note 12)** + +This element is relevant between the MT and the BSS. + +Value: + +- no preference +- up link biased asymmetry preference +- down link biased asymmetry preference + +NOTE 12:These GBS-related parameters are optional. + +For a configuration with data rates 9.6kbit/s or higher, the following applies to the parameters contained in the BC-IE: + +- Half rate channels are not supported. The MS shall code the radio channel requirement as "Full rate support only MS" or "Dual rate support MS, full rate preferred". In the second case, the network shall assign full rate channel(s) only. +- The 'fixed network user rate' and 'other modem type' takes precedence over the 'user rate' and 'modem type', unless the 'modem type' indicates "autobauding". +- The ACC indicates which channel coding is acceptable and supported by the MS. In case of CE:NT the TCH/F4.8 and TCH/F9.6 acceptable is equivalent to the support of NIRR. If TCH/F4.8 acceptable only or + +TCH/F9.6 acceptable only or TCH/F14.4 acceptable only is indicated, the assigned channel type which can be chosen by the network is TCH/F4.8 or TCH/F9.6 or TCH/F14.4, respectively. + +- The 'intermediate rate' parameter is overridden. The intermediate rate used per each TCH/F is derived from the chosen channel type: + +| channel type | IR per TCH/F | +|---------------------|------------------------------------| +| TCH/F4.8 | 8 kbit/s | +| TCH/F9.6 | 16 kbit/s | +| TCH/F14.4 | intermediate rate is to be defined | + +- The user rate per TCH is derived from the chosen channel type: + +| channel type | user rate per TCH | +|---------------------|--------------------------| +| TCH/F4.8 | 4.8 kbit/s | +| TCH/F9.6 | 9.6 kbit/s | + +For CE:T, the padding procedure described in 3GPP TS 44.021 can be applied. + +# --- Annex B (normative): Setting of Bearer Capability, Low Layer Compatibility and High Layer Compatibility Information Element for PLMN Bearer Services and PLMN TeleServices + +## B.0 Scope + +This annex describes the relationship between the various parameters of the PLMN Bearer Capability Information Element (BC-IE), their validity and the possible settings with reference to each PLMN Bearer service/Teleservice defined in 3GPP TS 22.002 and 3GPP TS 22.003 and various occurrences during the connection control (clause B.1). Furthermore, the contents of the Low Layer (LLC) and the High Layer (HLC) Compatibility Information Elements are described (clause B.2). + +## --- B.1 Bearer Capability Information Element + +### B.1.1 Introduction + +#### B.1.1.1 General Consideration + +In general, the purpose of the Bearer Capability Information Element (BC-IE) is to request a particular bearer service to be provided by the network. This indication is carried by certain connection control messages which for the subject matter of the present document may be categorized into those messages: + +- related to the call set-up phase; and +- those used during the established connection. + +During the call set-up phase the PLMN BC-IE (single or multiple) is included in: + +- the SETUP message generated by the requesting entity (either MS or MSC) to establish a mobile-originated or mobile-terminated call, respectively, and in + - the CALL CONFIRMED or CALL PROCEEDING messages, respectively, generated by the responding entity (either MS or MSC) in order to negotiate certain parameter values. If no BC-IE is contained in the SETUP message (a mobile terminated call with the single-numbering scheme) the CALL CONFIRMED message indicates the complete applicable BC-IE. The network may release the call if it does not support the service indicated by the BC-IE. Also, if the service does not match with the service requested from the fixed network terminal the MSC/IWF may release the call. + +NOTE: In the latter case also the fixed network terminal may release the call. + +During the established connection the PLMN BC-IE is included in the MODIFY, MODIFY COMPLETE, and MODIFY REJECT messages in order to change the service (bearer capability) or to change the maximum number of traffic channels and/or wanted air interface user rate when a non-transparent multislot data service is in use. + +If the maximum number of traffic channels and/or wanted air interface user rate is to be changed, the BC-IE included in the MODIFY message shall not indicate a different bearer service than the one used at this stage of the connection - the values of the parameters 'maximum number of traffic channels' and/or 'wanted air interface user rate' may be changed, only. + +The subsequent tables and subclauses of clause B.1 deal with the representation of the individual contents of the PLMN BC-IE during the call set-up phase. For the use during the established connection refer to 3GPP TS 24.008. + +With respect to the individual parameter settings at the MS the following cases may be distinguished (see 3GPP TS 27.002 and 3GPP TS 27.003): + +- Mobile-originated call set up by a MS: + +- The setting results from respective MMI actions and/or MT internal settings. +- Mobile-terminated call set up to a MS: + - The BC related part of the compatibility check is carried out according to the knowledge of the MT concerning its implemented functions (i.e. answering the call). The requested field values of the non-negotiable parameters and the selected field values of the negotiable parameters determine the selection of the terminal function to be used for the intended connection. + +#### B.1.1.2 Interpretation of the Diagrams + +The purpose of the subsequent diagrams is to achieve unambiguous representation of the individual contents of the PLMN BC-IE for the various occurrences during the call set-up phase, covering all bearer services and teleservices according to 3GPP TS 22.002 and 3GPP TS 22.003. + +The basic principle adopted is a graphic scheme, or mask, wherein the ordinate designates the individual parameters of the PLMN BC-IE and the abscissa gives the possible field values of these parameters. The abbreviations used in these sections are defined in table B.5. The allowed content of any PLMN BC-IE is represented by a number of graphs connecting parameter values (abscissa points) of all parameters (ordinate points). Each graphic scheme is subdivided into two independent parts: + +- "Layer/Protocol related" part; and +- "Radio Channel related" part. + +The generation of all PLMN BC-IEs in all call set-up messages shall be in accordance with these graphs. + +Subclauses B.1.2 through B.1.11 show individual sets of graphs for each service group (BS/TS) and for each type of applicable Information Transfer Capability. + +In addition, the following rules apply: + +- Those parameters which have only one possible field value for all recognized services are shown in table B.5, where they are marked accordingly in the column "common setting of field values". They are not represented in the graphic scheme. +- Not all parameters of the PLMN BC-IE are relevant for each service (BS/TS). This is represented by specific abscissa points with a value of "NA" (Not Applicable) allocated to these parameters. The graphs pass through these points for each such parameter. The actual field value to be used in the PLMN BC-IE is marked in the column "default setting of field values (NA)" of table B.5. An abscissa point with a value of "NAV" (Not Available) indicates that the entire octet carrying this parameter (see table B.2 "General Structure of the PLMN BC-Information Element") shall be omitted. +- Unless FTM is applied, there is a particular dependency of the parameters "User Information Layer 2 Protocol (UIL2P)" and "Connection Element (CE)": + - If the MS sends a PLMN BC-IE with a CE value other than "Transparent (T)", the parameter UIL2P is essential. Its field value must be set as indicated in the applicable graph. + - If the MSC sends a PLMN BC-IE in the SETUP message, the parameter UIL2P may also be absent in the case of the CE parameter value being other than "Transparent (T)". +- In case FTM is applied, the PLMN BC-IE shows a CE value "non-transparent", SA value "asynchronous", and RA value X.31 flag stuffing. The UIL2P is not available. +- Certain parameters of the PLMN BC-IE may be negotiated during the connection establishment phase. Table B.1 shows these parameters and the relations of their values in the SETUP message and in the CALL CONFIRMED/CALL PROCEEDING message, respectively, both for the mobile-originated and mobile-terminated case. A parameter may indicate a field value of one of the following types: + - "requested value" indicating a request which cannot be changed by the responding entity; + - "offered value" indicating a proposal which may be changed by the responding entity; + - a particular choice value leaving it up to the responding entity which value ultimately applies; + - "as requested" indicating that the requested value applies and is confirmed (by returning it); + +- "selected value" indicating that a particular value applies either out of the offered set or as a free choice out of the defined set of values; +- "supported value" indicating a value supported by the responding entity. + +**Table B.1: BC-Parameters subject to negotiation procedure** + +Mobile Originated Call: + +| BC-parameter | Message | | +|--------------|---------------------------------------------------------------------------------------|---------------------------------------| +| | SETUP | CALL PROC | +| NDB | Requested value | as requested | +| NPB | Requested value | as requested | +| NSB | Requested value | as requested | +| CE | Requested value (T/NT)
"both" with the preferred value indicated
(e.g. both NT) | as requested
selected value (T/NT) | +| UIL2P | Requested value 9) or NAV 1) | as requested or NAV 4) | +| User Rate | Requested value | as requested | +| DC | Requested value 2) | as requested or "NO" 7) | +| FNUR | Requested value | supported value | +| Other MT | Requested value | supported value | +| UIMI | Requested value | supported value | + +Mobile Terminated Call: + +| BC-parameter | Message | | +|---------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------| +| | SETUP | CALL CONF | +| NDB | Offered value | selected value (free choice) | +| NPB | offered value | selected value (free choice) | +| NSB | offered value | selected value (free choice) | +| CE | requested value (T/NT) | as requested or selected value (T/NT) (free choice) 3) | +| | "both" with the preferred value indicated (e.g. both NT) | selected value (T/NT) | +| Sync/Asynchronous | requested value | as requested or selected value 10) | +| Rate adaptation/Other rate adaptation | requested value | as requested or selected value 11) | +| UIL2P | offered value 2) or NAV 4) | selected or NAV 1) | +| User Rate | offered value | selected value 5) | +| DC | requested value 2) | as requested or "NO" 7) | +| FNUR | offered value | selected value 6) | +| Other MT | offered value | selected value 6) | +| UIMI | offered value | selected value 8) | + +- 1) For CE:T only, out-band flow control, or RA:X.31 flag stuffing requested by the MS. +- 2) Not for CE:T. +- 3) When the SETUP message contains no BC-IE (single numbering scheme). +- 4) "NAV" shall not be interpreted as an out-band flow control request by the MS. +- 5) The modification of User Rate shall be in conjunction with Modem Type and Intermediate Rate. +- 6) The modification of the Fixed Network User Rate shall be in conjunction with the Modem Type and/or Other Modem Type. +- 7) In case of a Mobile Terminated Call, if the SETUP message does not contain a BC-IE, the MS shall behave as if the DC is set to "data compression not possible". +If a sending entity, based on an earlier version of the protocol, sends a SETUP message containing "DC.. compression possible/ allowed" instead of the default value "NO.. compression not possible/allowed" as defined in Table B.5 then the receiving MS or the receiving network may ignore the DC value and may return either "NO.. compression not possible/allowed" or "DC.. compression possible/allowed" in the CALL CONF/CALL PROC message. +In case of a MO CALL or a MT CALL where no BC-IE is included in the CALL PROCEEDING or CALL CONFIRMED message, respectively, the MS or the network shall behave as if the DC was set to "data compression not possible" or "data compression not allowed", respectively. +- 8) Less or equal to the offered value. +- 9) Not for CT:T or FTM (i.e., CE:NT, SA:A, RA:X.31 flag stuffing). +- 10) For FTM and PIAFS, this parameter may be negotiated. See Table B.4e for details. +- 11) For FTM, PIAFS and Multimedia, this parameter may be negotiated. See Table B.4f for details. + +**Table B.2: General Structure of the BC-Information Element** + +| OCTET | INFORMATION ELEMENT FIELD | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3 | Radio channel requirements
Coding standard
Transfer mode
Information Transfer Capability | +| 4 | Structure 2)
Duplex mode
Configuration
Establishment
Negotiation of Intermediate Rate Requested
Compression | +| 5 | Rate adaption 2)
Signalling access protocol | +| 5a | Other ITC 2) 7)
Other rate adaption | +| 5b | Rate adaption header / no header 2) 3)
Multiple frame establishment support in data link
Mode of operation
Logical link identifier negotiation
Assignor / assignee
In-band / out-band negotiation | +| 6 | User information layer 1 protocol 2)
Synchronous / asynchronous | +| 6a | Number of stop bits 2)
Negotiation
Number of data bits
User rate | +| 6b | Intermediate rate 2)
NIC on transmission
NIC on reception
Parity information | +| 6c | Connection element 2)
Modem type | +| 6d | Fixed network user rate 4)
Other modem type | +| 6e | Maximum number of traffic channels 4)
Acceptable channel codings | +| 6f | Wanted air interface user rate 4)
User initiated modification indication | +| 6g | Acceptable Channel codings 5)
Asymmetry preference indication 6) | +| 7 | User information layer 2 protocol 1) 2) | +| 1) | Octets optional. | +| 2) | Octets only available if the parameter "Information Transfer Capability" does not indicate "Speech". | +| 3) | For ITU-T V.120 rate adaption only. | +| 4) | Optional octets available only if the parameter "Information Transfer Capability" does not indicate "Speech". | +| 5) | Extension of the 'Acceptable channel codings' field in octet 6e in case EDGE channel codings are supported. | +| 6) | Only used if EDGE channels are among the 'Acceptable channel codings'. The value shall be set to 'no preference' in case the connection element is T. | +| 7) | For ITC=RDI or UIL1P=V.120, PIAFS, and 'H.223 and H.245' only. | + +**Table B.3a: Selection of flow control method (for CE:NT with SA:A only)** + +| information element | flow control method | | | +|-----------------------------------|---------------------|--------------|---------------| +| | in-band | out-band (3) | none | +| number of data bits | 7 or 8 | 7 or 8 | 7 or 8 | +| user information layer 2 protocol | ISO 6429 (1) | NAV | COPnoFICt (2) | + +1) ISO6429 stands for "ISO 6429, codeset 0, DC1/DC3" and is applicable for 7 and 8 bit codes. + +2) COPnoFICt stands for a character oriented protocol with no flow control mechanism (no reserved characters for flow control). + +3) "out-band" flow control requires ITU-T V.42 in case of PSTN or ITU-T V.110 in case of ISDN. +If the ITU-T V.110 flow control mechanism is not supported, where required, the call pending shall be terminated. +If the ITU-T V.42 functionality is not supported by the modem in the IWF or in the fixed network, the call shall be supported with a fallback to the non- ITU-T V.42 mode. In this case the IWF shall release the call if due to temporary throughput problems on the radio interface or initiation of flow control by the MS and the inability to flow control the fixed network modem an overflow of the L2R buffers occurs. +Note that a phase 1 network may release the call, if the ITU-T V.42 functionality is not provided by the IWF or the fixed network modem. As ITU-T V.42 does not apply to ITU-T V.21 modems, outband flow control can not be supported for these modem types. + +**Table B.4a: Modem Type subject to negotiation procedure** + +Mobile Originated Call: + +| BC-parameter CE | BC-parameter MT and OMT 6) | | +|--------------------|----------------------------|----------------------------------------| +| | Message SETUP | Message CALL PROC | +| T | V-series | V-series | +| NT | V-series | V-series | +| | autobauding type 1 | autobauding type 1 or
V-series 1) | +| bothT or
bothNT | V-series | V-series | +| | autobauding type 1 | autobauding type 1 or
V-series 1)2) | + +Mobile Terminated Call: + +| BC-parameter CE | BC-parameter MT and OMT 6) | | +|--------------------|----------------------------|----------------------------------------------| +| | Message SETUP | Message CALL CONF | +| T | V-series | V-series | +| NT | V-series | V-series or autobauding type 1 3) | +| | autobauding type 1 | autobauding type 1 or
V-series 4) | +| bothT or
bothNT | V-series | V-series | +| | autobauding type 1 | autobauding type 1 or
V-series 4)5) | + +- 1) No autobauding capability in the IWF:MSC. +- 2) CE:T selected by IWF/MSC. +- 3) Free choice if the SETUP contains no BC-IE (single numbering scheme). +If the IWF/MSC has no autobauding capability, a V-series modem type is used. +- 4) When the MS does not allow the use of autobauding capability. +- 5) CE:T selected by the MS. +- 6) When the MT indicates "autobauding" , "modem for undefined interface" or "none", the OMT shall be set to "no other modem type". Any other values of the MT is overridden by the OMT value. + +**Table B.4b: Intermediate Rate negotiation procedure** + +If the user rate is 9.6 kbit/s the intermediate rate negotiation procedure is not applicable and NIRR shall be set to "No meaning". + +Recipient of SETUP supports full rate, non transparent, 6 kbit/s radio interface rate and the user rate is up to/equal 4,8 kbit/s: + +| BC-parameter | Message SETUP | Message CALL CONF or CALL PROC | +|--------------|------------------------|--------------------------------| +| NIRR | 6 kbit/s | 6 kbit/s | +| IR | 16 kbit/s | 8 kbit/s | +| User Rate | up to/equal 4,8 kbit/s | as requested | + +NOTE 1: In case of a Mobile Terminated Call, if the SETUP message does not contain a BC-IE, the MS shall behave as if NIRR set to "No meaning". + +In case of a MO CALL or a MT CALL where no BC-IE is included in the CALL PROCEEDING or CALL CONFIRMED message, respectively, the MS or the network shall behave as if the NIRR was set to "No meaning". + +Recipient of SETUP does support full rate, non transparent, but not in connection with 6 kbit/s radio interface rate: + +| BC-parameter | Message SETUP | Message CALL CONF or CALL PROC | +|--------------|------------------------|--------------------------------| +| NIRR | 6 kbit/s | No meaning | +| IR | 16 kbit/s | 16 kbit/s | +| User Rate | up to/equal 4,8 kbit/s | as requested | + +NOTE 2: If no other parameter needs negotiation, the CALL CONF/PROC message need not contain any BC-IE. + +In case of a MO CALL or a MT CALL where no BC-IE is included in the CALL PROCEEDING or CALL CONFIRMED message, respectively, the MS or the network shall behave as if the NIRR was set to "No meaning". + +NOTE 3: In case a GBS-operation is requested and acknowledged, the MS indicates the acceptable channel codings. The indicated acceptance of TCH/F4.8 is equivalent to the support of 6 kbit/s radio interface rate per TCH/F and therefore overrides the NIRR parameter. + +**Table B.4c Negotiation of fixed network user rate** + +| BC-parameter | Message SETUP | Message CALL PROC/CONFIRMED | +|--------------|-----------------|-----------------------------------------| +| FNUR | requested value | equal or lower than the requested value | + +The network might accept the modified value or reject the call. + +**Table B.4d Negotiation of user initiated modification indication** + +| BC-parameter | Message SETUP | Message CALL PROC/CONFIRMED | +|--------------|---------------|--------------------------------------------------------------------------------------------------------------| +| UIMI | offered value | equal to or a value indicating a request for modification to a lower number of traffic channels than offered | + +**Table B.4e: Negotiation of Synchronous/Asynchronous** + +Mobile Terminated Call: + +| | BC-parameter Synchronous/Asynchronous | | +|---------------------|---------------------------------------|-------------------| +| Bearer type | Message SETUP | Message CALL CONF | +| FTM 1) | Synchronous | Asynchronous | +| PIAFS 2) | Synchronous | Asynchronous | + +- 1) This negotiation is possible, only if ITC=UDI or RDI, FNUR=64 or 56 kbit/s and CE=NT or "both" is signalled in the SETUP message. The MS shall signal FTM as specified in B.1.2.3 . +- 2) This negotiation is possible, only if ITC=UDI, FNUR=32 kbit/s and CE= "both" is signalled in the SETUP message. The UE shall signal PIAFS as specified in B.1.2.4 + +**Table B.4f: Negotiation of Rate adaptation/Other rate adaptation** + +Mobile Terminated Call: + +| | BC-parameter Rate adaptation/Other rate adaptation | | +|---------------------|----------------------------------------------------|--------------------| +| Bearer type | Message SETUP | Message CALL CONF | +| FTM 1) | V.110, I.460 and X.30 | X.31 flag stuffing | +| PIAFS 2) | V.110, I.460 and X.30 | PIAFS | +| Multimedia | V.110, I.460 and X.30 3) | H.223 and H.245 | +| | No rate adaptation 5) 6) | H.223 and H.245 | + +- 1) This negotiation is possible, only if ITC=UDI or RDI, FNUR=64 or 56 kbit/s and CE=NT or "both" is signalled in the SETUP message. The MS shall signal FTM as specified in B.1.2.3. +- 2) This negotiation is possible, only if ITC=UDI, FNUR=32 kbit/s and CE= "both" is signalled in the SETUP message. The UE shall signal PIAFS as specified in B.1.2.4. + +- 3) This negotiation is possible, only if ITC=UDI or RDI, FNUR=32 or 56 kbit/s and CE=T or "both" is signalled in the SETUP message. The MS shall signal 3G-H.324/M as specified in B.1.3.1.3, B.1.3.1.4 and B.1.3.1.6. +- 4) Void. +- 5) This negotiation is possible, if ITC=3,1 kHz, FNUR=28.8 kbit/s, MT=V.34 and CE=T or "both" is signalled in the SETUP message. The MS shall signal 3G-H.324/M as specified in B.1.3.2.3. +- 6) This negotiation is possible, if ITC=UDI or RDI, FNUR=64 or 56 kbit/s and CE=T is signalled in the SETUP message. The MS shall signal 3G-H.324/M as specified in B.1.3.1.3, B.1.3.1.4, and B.1.3.1.5 + +**Table B.5: BC parameter setting (part 1)** + +| Abbreviations for Parameters and Values: | common setting of field values | | +|--------------------------------------------------------|--------------------------------------|---| +| | default setting of field values (NA) | | +| ITC...Information Transfer Capability: | | | +| - Speech | | | +| - UDI..Unrestricted Digital | | | +| - FAX3..Group 3 Facsimile | | | +| - 3,1 kHz..3,1 kHz Ex PLMN | | | +| - RDI..Restricted Digital | | | +| TM....Transfer Mode: | | | +| - ci..Circuit | X | X | +| S.....Structure: | | | +| - SDU..Service Data Unit Integrity | | | +| - Unstructured | X | | +| C.....Configuration: | | | +| - pp..Point to point | X | X | +| E.....Establishment: | | | +| - de..Demand | X | X | +| SA....Sync/Async: | | | +| - S..Synchronous | | | +| - A..Asynchronous | | | +| N.....Negotiation | | | +| - ibn..in band negotiation not possible | X | X | +| UR....User Rate: | | | +| - 0.3..0.3 kbit/s | | | +| - 1.2..1.2 kbit/s | | | +| - 2.4..2.4 kbit/s | | | +| - 4.8..4.8 kbit/s | | | +| - 9.6..9.6 kbit/s | X | | +| IR....Intermediate Rate: | | | +| - 8.. 8 kbit/s | | | +| - 16.. 16 kbit/s | X | | +| NICT..Network Independent Clock on Tx: | | | +| - not_required.. Not required | X | X | +| - required | | | +| NICR..Network Independent Clock on Rx: | | | +| - not_accepted..not accepted | X | X | +| - accepted | | | +| NSB...Number of Stop Bits: | | | +| - 1..1 bit | X | | +| - 2..2 bit | | | +| NDB...Number of Data Bits Excluding Parity If Present: | | | +| - 7.. 7 bit | | | +| - 8.. 8 bit | X | | +| NPB...Parity Information: | | | +| - Odd | | | +| - Even | | | +| - None | X | | +| - 0.. Forced to 0 | | | +| - 1.. Forced to 1 | | | +| UIL1P.User Information Layer 1 Protocol | | | +| - def..default layer 1 protocol | X | X | + +**Table B.5: BC parameter setting (part 2)** + +| Abbreviations for Parameters and Values | | common setting of field values | | +|------------------------------------------------------|----------------------------------------------------------------------------------------------|--------------------------------------|---| +| | | default setting of field values (NA) | | +| | | v | v | +| DM....Duplex Mode: | - | | | +| | - fd.. Full Duplex | X | X | +| MT....Modem Type: | - V.21 | | | +| | - V.22 | | | +| | - V.22 bis | | | +| | - V.26 ter | | | +| | - V.32 | | | +| | - autol.. autobauding type 1 | | | +| | - none | X | | +| RCR...Radio Channel Requirement: | - FR Full Rate support only Mobile Station | | | +| | - dual HR Dual Rate support Mobile Station/
Half Rate preferred | | | +| | - dual FR Dual Rate support Mobile Station/
Full Rate preferred | | | +| CE....Connection Element: | - T.. Transparent | | | +| | - NT.. Non Transparent | | | +| | - bothT both transparent preferred | | | +| | - bothNT both non Transparent preferred | | | +| UIL2P.User Information Layer 2
Protocol: | - ISO6429..ISO6429,codeset 0,DC1/DC3 | | | +| | - COPnoFlCt..Character oriented protocol with
no flow control mechanism | | | +| SAP...Signalling Access Protocol: | - I.440.. I.440/450 | X | | +| RA....Rate Adaptation: | - V.110.. V.110/X.30 | | | +| | - X.31Flag.. X.31 flagstuffing | | | +| | - NO.. no rate adaptation | X | | +| | - V.120 | | | +| | - PIAFS | | | +| | - H.223 and H.245 | | | +| CS....Coding Standard: | - GSM | X | X | +| NIRR..Negotiation of Intermediate
Rate Requested: | NM..No Meaning associated with this value
6kbit/s..6kbit/s radio interface rate requested | X | | +| DC....Data Compression | - DC.. compression possible/allowed | | | +| | - NO.. compression not possible/allowed | X | | + +**Table B.5: BC parameter setting (part 3)** + +| Abbreviations for Parameters and Values | | common setting of field values | | | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|---|---| +| | | default setting of field values (NA) | v | v | +| FNUR...Fixed Network User Rate | | | | | +| WAIUR...Wanted Air Interface User Rate | | | X | | +| ACC.....Acceptable channel codings | | | | | +| MaxNumTCH...Maximum Number of Traffic Channels | | | | | +| OMT...Other modem type | | | | | +| User initiated modification indication | | | X | | +| Asymmetry preference indication | | | | | + +**Table B.5a: Differences in parameter value validity in A/Gb mode and UTRAN Iu mode** + +| Parameter / value | A/Gb mode | GERAN Iu mode | UTRAN Iu mode | +|-----------------------------------------------------|---------------------|-----------------------------------------|-----------------------------------------| +| Radio Channel Requirements / any | valid | valid | ignored | +| User rate / any | valid | ignored | ignored | +| Intermediate Rate / any | valid | valid | ignored | +| NIC on transmission / any | valid | ignored | ignored | +| NIC on reception / any | valid | ignored | ignored | +| Negotiation of IR requested / any | valid | ignored | ignored | +| Acceptable Channel Codings / any | valid (note 2) | valid (note 2) | ignored | +| Maximum number of traffic channels / any | valid (note 2) | valid (note 2) | ignored (Note 1) | +| User initiated modification indication / any | valid | valid | ignored (Note 1) | +| Asymmetry preference indication/ any | valid | valid | ignored | +| Modem type / | | | | +| V.21, V.22, V.22bis, V.26ter | valid | invalid | invalid | +| V.32 | valid | valid | invalid for CE=T | +| Fixed Network User Rate / | | | | +| 32 kbit/s | Invalid for CE = NT | Invalid for CE = NT | valid | +| 33.6 kbit/s | invalid | invalid | valid | +| 9.6, 14.4, 19.2, 38.4, 48.0 | valid | invalid for CE=T | invalid for CE=T | +| 28.8 | valid | invalid for CE=T in the case of ITC=UDI | invalid for CE=T in the case of ITC=UDI | +| Other Rate adaptation / | | | | +| PIAFS | invalid | invalid | valid | + +NOTE: Although a parameter value is marked as "valid", the validity may be restricted by rules given elsewhere in the present document. + +NOTE 1: This parameter is relevant in UTRAN Iu mode for NT calls, in conjunction with WAIUR, for deciding which RLP version to negotiate in order to avoid renegotiation of RLP version in case of handover, see 3GPP TS 24.022 [9]. It is otherwise irrelevant for specifying the UTRAN Iu mode radio access bearer. + +NOTE 2: The MS can indicate that the requested service is not supported in A/Gb or GERAN Iu mode by setting all Acceptable Channel Codings to "none" (all zeros) and the Maximum Number of Traffic Channels parameter to the value "one TCH" (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed before the call setup can proceed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +**Table B.6: Channel combinations** + +Single Bearer and Teleservices + +| MS indication
BC | Network selection CT
CT | +|---------------------|----------------------------| +| FR | FR | +| dual FR | FR or HR | +| dual HR | HR or FR | + +Alternate services + +| MS indication | | Network selection | | | | | +|---------------|-----------|-------------------|-------|----|-------|-------| +| BC(1) | BC(2) | CT(1) | CT(2) | Or | CT(1) | CT(2) | +| FR | FR | FR | FR | | | | +| FR | dual Rate | FR | FR | | | | +| dual Rate | dual Rate | FR | FR | Or | HR | HR | +| dual Rate | FR | FR | FR | | | | + +Followed-by services + +| MS indication | | Network selection | | | | | | | | +|---------------|-----------|-------------------|-------|----|-------|-------|----|-------|-------| +| BC(1) | BC(2) | CT(1) | CT(2) | or | CT(1) | CT(2) | or | CT(1) | CT(2) | +| FR | FR | FR | FR | | | | | | | +| FR | dual Rate | FR | FR | | | | | | | +| dual Rate | dual Rate | FR | FR | or | HR | HR | or | FR | HR | +| dual Rate | FR | FR | FR | | | | | | | + +BC Bearer Capability + +CT Channel Type + +dual Rate {dual FR | dual HR} + +**Table B.7: TS61/TS62 Negotiation rules** + +Mobile Originating Call + +| Subscription | SETUP | CALL PROCEED | +|--------------|----------|------------------| +| TS61 | TS61 s/f | TS61 s/f or TS62 | +| | TS61 f/s | TS61 f/s or TS62 | +| | TS62 | TS62 | +| TS62 | TS61 s/f | TS62 | +| | TS61 f/s | TS62 | +| | TS62 | TS62 | + +Mobile Terminating Call + +| Subscription | SETUP | CALL CONFIRMED | +|--------------|----------|------------------------------| +| TS61 | TS61 s/f | TS61 s/f or TS61 f/s or TS62 | +| | TS61 f/s | TS61 s/f or TS61 f/s or TS62 | +| | TS62 | TS62 | +| | no BC | TS61 s/f or TS61 f/s or TS62 | +| TS62 | TS62 | TS62 | +| | no BC | TS62 (note) | + +s/f = speech then fax + +f/s = fax then speech + +NOTE: TS61 is also accepted if the VMSC supports TS61 and does not perform subscription checking on a CALL CONFIRMED message (see 3GPP TS 22.001 and 3GPP TS 29.007). + +### B.1.2 Bearer Service 20, Data Circuit Duplex Asynchronous + +#### B.1.2.1 Unrestricted / restricted digital information transfer capability + +| | | | | | | | | | | | +|------------------------|------|-------------|----------|---------------------|------------------|-------------------------|-------------------|-----------|--------------------|-----| +| | Oct. | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | +| Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 7) | V.110 | H.223 & H.245 | X.31 Flag | No | | | +| SA | 6 | | | A | | S | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct 5) | NAV 4) | | | | +| DC | 4 | NA | | | DC 1) | | NO 1) | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | +| Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | +| UR 8) | 6a | NA | | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | +| IR 8) | 6b | NA | | 8 | | 16 | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | NAV | +| FNUR | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | NAV | +| ACC 9) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | NAV | +| WAIUR 1) | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | NAV | +| UIMI 1) | 6f | NA | not req. | upto 1 | upto 2 | | upto 3 | | upto 4 | NAV | +| ACC ext. 9) | 6g | | | | | 28.8 | 32.0 | | 43.2 1) | NAV | +| ASYM 1) | 6g | no. pref. | | | | u1 biased | | d1 biased | | NAV | + +1) for CE:NT or "both"; + +2) for CE:T only or CE:NT and NIRR:6kb/s (not for the SETUP message); + +3) Void; + +4) for MT CALLS in the SETUP message or MO/MT CALLS with "out-band" flow control requested; + +5) for MO/MT CALLS with no flow control requested; + +6) Void; + +- 7) the V.120 relevant BC parameters (octet 5b) shall be set according to the LLC (see clause B.2); +- 8) IR and UR are overridden by FNUR, ACC and MaxNumTCH; +- 9) ACC may have several values simultaneously (bit map coding). + +#### B.1.2.2 3,1 kHz audio ex-PLMN information transfer capability + +| Oct. | 3/5a | UDI | 3.1 kHz | FAX3 | Speech | RDI | | | | +|------------------------|------|-------------|----------|------------------|-------------------------|-------------------|-----------|--------------------|-----| +| Layer/protocol related | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | +| SA | 6 | | | A | S | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | +| S | 4 | NA | | SDU | | unstructured | | | | +| U1L2P | 7 | | | ISO6429 | COPnoFlct 5) | NAV 4) | | | | +| DC | 4 | NA | | DC 1) | | NO 1) | | | | +| NDB | 6a | NA | | 7 | | 8 | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | +| NSB | 6a | NA | | 1 | | 2 | | | | +| Radio channel related | | | | | | | | | | +| RCR | 3 | dualHR | | dualFR | | FR | | | | +| UR 7) | 6a | NA | | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | +| IR 7) | 6b | NA | | 8 2) | | 16 | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | auto 1 | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | NAV | +| FNUR 9) | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | NAV | +| ACC 8) | 6e | none | | 4.8 | | 9.6 | | 14.4 | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | NAV | +| WAIUR 1) | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | NAV | +| UIMI 1) | 6f | NA | not.req. | upto 1 | upto 2 | | upto 3 | upto 4 | NAV | +| ACC ext. 8) | 6g | | | | | 28.8 | 32.0 | 43.2 1) | NAV | +| ASYM 1) | 6g | no. pref. | | | | u1 biased | | d1 biased | NAV | + +1) for CE:NT or "both"; + +2) for CE:T only or CE:NT and NIRR:6kb/s (not for the SETUP message); + +3) Void; + +4) for MT CALLS in the SETUP message or MO/MT CALLS with "out-band" flow control requested (not for V.21 modem type); + +- 5) for MO/MT CALLS with no flow control requested; +- 6) Void; +- 7) IR and UR are overridden by FNUR, ACC and MaxNumTCH. +- 8) ACC may have several values simultaneously (bit map coding). +- 9) in case of MT = auto1 the value of FNUR has no meaning. + +#### B.1.2.3 Frame Tunnelling Mode + +| | | | | | | | | | | | | +|------------------------|------------------------|-------------|----------|---------|---------|---------------|--------------|-----------|--------|----|-----| +| ITC | Oct.
3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| | Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | NAV | +| ACC 1) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | ul biased | | dl biased | | | NAV | + +1) ACC may have several values simultaneously (bit map coding). + +#### B.1.2.4 PIAFS + +| | | | | | | | | | | | | +|------------------------|------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|----|--------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +### B.1.3 Bearer Service 30, Data Circuit Duplex Synchronous + +#### B.1.3.1 Unrestricted/restricted digital information transfer capability + +##### B.1.3.1.1 Transparent FNUR <= 48 kbit/s (TCH/F4.8, TCH/F9.6, TCH/14.4, TCH/F28.8) + +Applies to A/Gb mode only. No HO to/from UTRAN Iu mode. + +| ITC | Oct.
3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +|--------------------------|------------------------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|---------|-----------| +| | Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | | | dualFR | | FR | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR 1) | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 64 NAV | +| ACC 1,2) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH 1) | 6e | | | 1 | 2 | 3 | 4 | 5 | 6 | 7 8 NAV | | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1,2) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM 1) | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. + +2) ACC may have several values simultaneously (bit map coding). + +##### B.1.3.1.2 X.32 Case + +Void. + +##### **B.1.3.1.3 Transparent FNUR=56 kbit/s, including 3G-H.324/M, (TCH/F9.6, TCH/F32.0, UTRAN Iu mode)** + +| | | | | | | | | | | | | | +|-----------------------------|------|------------------------|-----------|---------|---------------------|-----------------------------|--------------|--------------------|--------|----|----|-------------------| +| | Oct. | | | | | | | | | | | | +| ITC | 3/5a | UDI 3) | 3.1 kHz | | FAX3 | Speech | | | | | | RDI 3) | +| | | Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | | +| RA 3) | 5/5a | NA | PIAFS | V.120 | V.110 3) | H.223 & H.245 3) | X.31 Flag | No 3) | | | | | +| SA | 6 | | | A | | S | | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | | +| | | Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | | NAV | +| OMT 5) | 6d | no other MT | | | | V.34 | | | | | | NAV | +| FNUR 1,5) | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 | NAV | +| ACC 1,2,4,6) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | | NAV | +| MaxNumTCH 1,4,6) | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | NAV | +| WAIUR 1) | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 1) | 57.6 | | | NAV | +| UIMI 1,4) | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | | NAV | +| ACC ext. 1,2,4) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | | NAV | + +- 1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. IR and UR are not applicable to UTRAN Iu mode. +- 2) ACC may have several values simultaneously (bit map coding). However, handover to/from UTRAN is not possible if the network assigns other traffic channels than TCH/F9.6 or TCH/F32.0. +- 3) In case ITC=UDI, RA shall be set to V.110. In case ITC=RDI, RA shall be set to H.223 & H.245 or No. + +- 4) An MS not supporting GERAN A/Gb and GERAN Iu mode sets ACC to "none" and MaxNumTCH is set to "1 TCH". An MS not supporting GERAN A/Gb and GERAN Iu mode also sets ACCext (i.e. the extension bits of ACC parameter, see 3GPP TS 24.008 for its definition and values) and UIMI to zero if they are included in the PLMN BC-IE, i.e. UIMI is set to "NA" and the ACC parameter (including the ACCext bits) is set to the value "none" (all zeros). +- 5) The parameters FNUR and OMT are mandatory for this service. +- 6) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero) and the network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +##### B.1.3.1.4 Transparent FNUR = 56kbit/s, including 3G-H.324/M (TCH/F14.4) + +Applies to A/Gb mode only, no HO to/from UTRAN Iu mode + +| | | | | | | | | | | | | +|---------------------------|------------------------|-------------------|-----------|---------|---------------------|-----------------------------|--------------|-------------------|--------|----|--------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI 3) | 3.1 kHz | | FAX3 | Speech | | RDI 3) | | | | +| | Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA 3) | 5/5a | NA | PIAFS | V.120 | V.110 3) | H.223 & H.245 3) | X.31 Flag | No 3) | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT 4) | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR 1,4) | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC 1,2,4) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH 1,4) | 6e | | 1 | 2 | 3 | 4 1) | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +- 1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. +- 2) ACC may have several values simultaneously (bit map coding). +- 3) In case ITC=UDI, RA shall be set to V.110. In case ITC=RDI, RA shall be set to H.223 & H.245 or No. +- 4) The parameters FNUR, OMT, ACC and MaxNumTCH are mandatory for this service. + +##### **B.1.3.1.5 Transparent FNUR = 64kbit/s, including 3G-H.324/M (TCH/F9.6, TCH/F14.4, TCH/F32.0, UTRAN Iu mode))** + +| | | | | | | | | | | | | +|-----------------------------|------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|----|-----------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT 4) | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR 1,4) | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 64 NAV | +| ACC 1,2,3,5) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | NAV | +| MaxNumTCH 1,3,5) | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI 3) | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1,2,3) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +- 1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. IR and UR are not applicable to UTRAN Iu mode. +- 2) ACC may have several values simultaneously (bit map coding). + +- 3) An MS not supporting GERAN A/Gb and GERAN Iu mode sets ACC to "none" and MaxNumTCH is set to "1 TCH". An MS not supporting GERAN A/Gb and GERAN Iu mode also sets ACCext (i.e. the extension bits of ACC parameter, see 3GPP TS 24.008 for its definition and values) and UIMI to zero if they are included in the PLMN BC-IE, i.e. UIMI is set to "NA" and the ACC parameter (including the ACCext bits) is set to the value "none" (all zeros). +- 4) The parameters FNUR and OMT are mandatory for this service. +- 5) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +##### B.1.3.1.6 3G-H.324/M, FNUR=32.0 kbit/s (TCH/F32.0, UTRAN Iu mode) + +| | | | | | | | | | | | | +|---------------------------|------|-------------|-----------|---------|---------|---------------|--------------|------|--------|----|-------------------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR 3) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 3) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC 1,2,4) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | NAV 2) | +| MaxNumTCH 2,4) | 6e | NA | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV 2) | +| WAUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI 2) | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV 2) | +| ACC ext. 1,2) | 6g | not accept. | | | | 28.8 | 32.0 | | 43.2 | | NAV 2) | + +- 1) ACC may have several values simultaneously (bit map coding). +- 2) If ACC, UIMI, MaxNumTCH and ASYM are not available operation is restricted to UTRAN. +- 3) IR and UR are overridden by FNUR, ACC and MaxNumTCH. IR and UR are not applicable to UTRAN Iu mode. + +- 4) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to “none” (all zeros) and MaxNumTCH parameter to the value “one TCH” (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +##### **B.1.3.1.7** Synchronous transparent 56 kbit/s (RDI) and 64kbit/s (UDI) (UTRAN Iu mode) + +See B.1.3.1.3 and B.1.3.1.5. + +#### B.1.3.2 3,1 kHz audio ex-PLMN information transfer capability + +##### B.1.3.2.1 Non-X.32 Cases + +| | Oct. | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +|------------------------|------|-------------------|--------------------|--------------------|--------------------|---------------|--------------|-----------|--------|----|-----| +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | auto 1 | | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 2) | 14.4 2) | 19.2 2) | 28.8 2) | 32 | 33.6 | 38.4 | 48 | 56 | NAV | +| ACC 1) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) ACC may have several values simultaneously (bit map coding). + +##### B.1.3.2.2 X.32 Case + +Void. + +##### B.1.3.2.3 3G-H.324/M Case + +| | | | | | | | | | | | | +|-------------------------|------|-------------|-----------|---------|--------|---------------|--------------|------|--------|--------|--------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | NA | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC 1,3) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH 3) | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | + +- 1) ACC may have several values simultaneously (bit map coding). +- 2) FNUR 33.6 kbit/s applies to UTRAN Iu mode only. +- 3) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +### B.1.4 Bearer Service 40 ... 46, PAD Access Asynchronous + +Void. + +### B.1.5 Bearer Service 50 ... 53 ,Data Packet Duplex Synchronous, Unrestricted digital information transfer capability + +Void. + +### B.1.6 Bearer Service 61, Alternate Speech/Data + +Void. + +### B.1.7 Bearer Service 81, Speech followed by Data + +Void. + +### B.1.8 Teleservice 11 ... 12, Speech + +| | Oct. | | | | | | | | | | | +|------------------------|------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|----|-----| +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | 1.440 | | | | | | | NAV | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | NAV | +| SA | 6 | NA | | A | | S | | | | | NAV | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | NAV | +| S | 4 | NA | | SDU | | | unstructured | | | | NAV | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | | | | | NAV | +| DC | 4 | NA | | | DC | | NO | | | | NAV | +| NDB | 6a | NA | | 7 | | | 8 | | | | NAV | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | NAV | +| NSB | 6a | NA | | 1 | | 2 | | | | | NAV | +| Radio channel related | | | | | | | | | | | | +| | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| | | | | | | | | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | NAV | +| IR | 6b | NA | 8 | | | 16 | | | | | NAV | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 33.6 | 38.4 | 48 | 56 | 64 | NAV | +| ACC | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +### **B.1.9 Teleservice 21 ... 23, Short Message** + +Not applicable. + +### **B.1.10 Teleservice 61, Alternate Speech and Facsimile group 3** + +The information element of the "repeat indicator" is set to the value "circular for successive selection (alternate)". + +#### **B.1.10.1 Teleservice 61, Speech** + +See subclause B.1.8. + +#### B.1.10.2 Teleservice 61, Facsimile group 3 in A/Gb mode + +| ITC | Oct.
3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +|------------------------|--------------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|--------|-----| +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | NAV | +| ACC 1) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAUR | 6f | NA | 9.6 | 14.4 | 19.2 | | 28.8 | 38.4 | 43.2 | 57.6 | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | | upto 3 | | upto 4 | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | | 43.2 | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) ACC may have several values simultaneously (bit map coding). + +#### B.1.10.3 Teleservice 61, Facsimile group 3 in UTRAN Iu mode + +| | | | | | | | | | | | | +|-----------|------|------------------------|-----------|---------|---------|-------------------------|--------------|-----------|--------|----|--------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| | | Layer/protocol related | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet 3) | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | | Radio channel related | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | NAV | +| IR | 6b | NA | 8 | | | 16 | | | | | NAV | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +### B.1.11 Teleservice 62, Automatic Facsimile group 3 + +Ref. subclause B.1.10, the information element "repeat indicator" is not available/valid. + +### B.1.12 Valid combinations of FNUR, WAIUR, ACC, mTCH + +#### B.1.12.1 Transparent Services + +The MS is allowed to signal any combination of FNUR, ACC and mTCH compliant to the following table. The network is allowed to assign any Channel Mode compliant to the following table. + +| FNUR | mTCH (Note 7, 9) | ACC (Note 1,6,9) | | | | | Channel Mode (Note 4,5) | | | | | +|-------------|------------------|------------------|----------|-----------|-----------|-----------|-------------------------|----------|-----------|-----------|-----------| +| | | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F32.0 | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F32.0 | +| 9.6 kbit/s | 1 | * | + | * | * | * | - | 1 | - | - | - | +| | 2 | + | * | * | * | * | 2 | 1 | - | - | - | +| 14.4 kbit/s | 1 | * | * | + | * | * | - | - | 1 | - | - | +| | 2 | * | + | * | * | * | - | 2 (N2) | 1 | - | - | +| | 3 | + | * | * | * | * | 3 | 2 (N2) | 1 | - | - | +| 19.2 kbit/s | 2 | * | + | * | * | * | - | 2 | - | - | - | +| | 4 | + | * | * | * | * | 4 | 2 | - | - | - | +| 28.8 kbit/s | 1 | * | * | * | + | * | - | - | - | 1 | - | +| | 2 | * | * | + | * | * | - | - | 2 | 1 | - | +| | 3 | * | + | * | * | * | - | 3 | 2 | 1 | - | +| 32.0 kbit/s | 1 | * | * | * | * | + | - | - | - | - | 1 | +| 38.4 kbit/s | 3 | * | * | + | * | * | - | - | 3 (N2) | - | - | +| | 4 | * | + | * | * | * | - | 4 | 3 (N2) | - | - | +| 48.0 kbit/s | 4 | * | * | + | * | * | - | - | 4 (N2) | - | - | +| | 5 | * | + | * | * | * | - | 5 | 4 (N2) | - | - | +| 56.0 kbit/s | 2 | * | * | * | * | + | - | - | - | - | 2(N8) | +| | 4 | * | * | + | * | * | - | - | 4 (N2) | - | 2(N8) | +| | 5 | * | + | * | * | * | - | 5 (N3) | 4 (N2) | - | 2(N8) | +| 64.0 kbit/s | 2 | * | * | * | * | + | - | - | - | - | 2(N8) | +| | 5 | * | * | + | * | * | - | - | 5 (N2) | - | 2(N8) | +| | 6 | * | + | * | * | * | - | 6 (N2,3) | 5 (N2) | - | 2(N8) | + +**NB: N in the table stands for NOTE.** + +NOTE 1: A '+' indicates that a certain channel coding shall be included in the ACC and a '\*' indicates that it may or may not be included. + +NOTE 2: Padding Required, ref 3GPP TS 44.021. + +NOTE 3: Air interface user rate 11,2 kbit/s, ref. 3GPP TS 44.021. + +NOTE 4: A '-' indicates that this channel coding cannot be assigned for this FNUR. + +NOTE 5: A certain channel coding may only be assigned if indicated as acceptable in the ACC. + +NOTE 6: In case the MS signals an ACC containing TCH/F4.8 only and the network does not support TCH/F4.8 channel coding, then the network may act as if TCH/F9.6 were included in the ACC. + +NOTE 7: The MS is allowed to signal higher values for mTCH than indicated in the table for the signalled FNUR and ACC. Before initiating the assignment procedure, the MSC, if necessary, shall lower the value of the mTCH to the highest value applicable for the signalled FNUR and ACC. + +NOTE 8: Can only be used for bit transparent 56 (RDI) and 64 (UDI) kbit/s connections in 56 kbit/s and 64 kbit/s environments, respectively. + +NOTE 9: The MS can request a transparent data call by setting all ACC bits to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero). The MSC will interpret these values as an indication that an intersystem handover from A/Gb or GERAN Iu mode to another (e.g. UTRAN Iu) mode is required before the call setup is completed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +The final decision about the radio interface configuration is taken by the BSS during the Assignment procedure subject to the restrictions that the number of assigned TCH/F may not exceed the mTCH, that the channel coding is among the ACC and that the AIUR equals the FNUR. + +The radio interface configuration may be changed by the BSS during the call as long as the channel coding used is among the ACC, the mTCH is not exceeded and the AIUR is kept constant (ref. 3GPP TS 22.034). + +#### B.1.12.2 Non-transparent services + +The MS is allowed to signal any combination of WAIUR, ACC and mTCH compliant to the following table. A combination is compliant to the table, if there exists at least one row that it is compliant to. A combination is compliant to a row if each parameter value meets the conditions given in that row. When a WAIUR, ACC, mTCH combination is compliant to a row, the network is allowed to assign any Channel Mode compliant to that row. The notes of the table provide further details on the compliance conditions. + +| WAIUR (Note 7) | mTCH (Note 5) | ACC (Note 1,4) | | | | | Channel Mode (Note 2,3,6) | | | | | +|----------------|---------------|----------------|----------|-----------|-----------|-----------|---------------------------|----------|-----------|-----------|-----------| +| | | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F43.2 | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F43.2 | +| 9.6 kbit/s | 1 | * | + | * | * | * | 1 | 1 | - | - | - | +| | 2 | + | * | * | * | * | 1 - 2 | 1 | - | - | - | +| 14.4 kbit/s | 1 | * | * | + | * | * | 1 | 1 | 1 | - | - | +| | 3 | + | * | * | * | * | 1 - 3 | 1 - 2 | 1 | - | - | +| 19.2 kbit/s | 2 | * | + | * | * | * | 1 - 2 | 1 - 2 | 1 | 1 | - | +| | 4 | + | * | * | * | * | 1 - 4 | 1 - 2 | 1 | 1 | - | +| 28.8 kbit/s | 1 | * | * | * | + | * | 1 | 1 | 1 | 1 | - | +| | 2 | * | * | + | * | * | 1 - 2 | 1 - 2 | 1 - 2 | 1 | - | +| | 3 | * | + | * | * | * | 1 - 3 | 1 - 3 | 1 - 2 | 1 | - | +| 38.4 kbit/s | 4 | * | + | * | * | * | 1 - 4 | 1 - 4 | 1 - 3 | 1 - 2 | 1 | +| 43.2 kbit/s | 1 | * | * | * | * | + | 1 | 1 | 1 | 1 | 1 | +| | 3 | * | * | + | * | * | 1 - 3 | 1 - 3 | 1 - 3 | 1 - 2 | 1 | +| 57.6 kbit/s | 2 | * | * | * | + | * | 1 - 2 | 1 - 2 | 1 - 2 | 1 - 2 | 1 | +| | 4 | * | * | + | * | * | 1 - 4 | 1 - 4 | 1 - 4 | 1 - 2 | 1 | + +NOTE 1: A '+' indicates that a certain channel coding shall be included in the ACC and a '\*' indicates that it may or may not be included. + +NOTE 2: A '-' indicates that this channel coding cannot be used for this WAIUR. + +NOTE 3: A certain channel coding may only be assigned if indicated as acceptable in the ACC. + +NOTE 4: In case the MS signals an ACC containing TCH/F4.8 only and the network does not support TCH/F4.8 channel coding, then the network may act as if TCH/F9.6 were included in the ACC. + +NOTE 5: The MS is allowed to signal higher values for mTCH than indicated in the table for the signalled WAIUR and ACC. Before initiating the assignment procedure, the MSC, if necessary, shall lower the value of the mTCH to the highest value applicable for the signalled WAIUR and ACC. + +NOTE 6: Unless an EDGE channel is assigned in one direction at least, the same channel coding is assigned in both directions, and an equal or lesser number of channels is assigned in the up link direction than in the down link direction. If an EDGE channel is assigned in one direction, TCH/F14.4 or an EDGE channel is assigned in the other direction. If the user has indicated up or down link biased asymmetry preference, TCH/F14.4 is assigned in the unbiased direction. The number of channels assigned is the same in each direction unless restricted by the mobile classmark, and is always within the limits given in the corresponding column. + +NOTE 7: The MS is allowed to signal higher values for WAIUR than indicated in the table for the signalled mTCH and ACC. Before initiating the assignment procedure, the MSC, if necessary, shall lower the value of the WAIUR to the highest value applicable for the signalled mTCH and ACC. + +The final decision about the radio interface configuration is taken by the BSS during the Assignment procedure. The BSS may assign any number of TCH/F ranging from 1 to mTCH and use any of the channel codings among the ACC. The BSS shall try to reach the WAIUR if the resource situation allows it. The maximum possible AIUR shall not exceed the WAIUR unless the higher AIUR can be reached with a smaller number of TCH/F (ref. 3GPP TS 22.034). + +The radio interface configuration may be changed by the BSS during the call as long as the channel coding used is among the ACC and the mTCH is not exceeded. + +### B.1.13 Assignment of radio access bearer parameters depending on FNUR and WAIUR + +#### B.1.13.1 Transparent Services + +Depending on the FNUR negotiated between the network and the MS, the network is allowed to assign any radio resources with a radio access bearer parameter indicating a Quality of Service specifying + +| QoS Parameter | Value | Comments | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | +| Traffic Class | Conversational | Subject to operator tuning (Note 2) | +| RAB Asymmetry Indicator | Symmetric | | +| Maximum bit rate | = guaranteed bit rate | | +| Guaranteed bit rate | FNUR = 64 .. 28,8 kbit/s | GBR for FNUR=56 kbit/s is 64 kbit/s (Note 1) | +| Delivery Order | Yes | | +| Maximum SDU size | 640bits for FNUR = 32, 56 and 64 kbit/s
576 bits for FNUR = 28.8 kbit/s
672 bits for FNUR = 33.6 kbit/s | | +| Transfer Delay | < 200 ms | Subject to operator tuning | +| Traffic Handling Priority | - | Not applicable for the conversational traffic class | +| Source statistics descriptor | Unknown | | +| SDU Parameters | | | +| SDU error ratio | - | Not applicable | +| Residual bit error ratio | $10^{-4}$ | Subject to operator tuning according to 3GPP TS 23.107.
Operator may also choose different value for Multimedia and other transparent data services. | +| Delivery of erroneous SDUs | - | No error detection in the core network | + +NOTE 1: In case the FNUR = 56 kbit/s, the GBR is set to 64 kbit/s. Last bit in each data octet is set to 1 + +NOTE 2: Only traffic Classes "Streaming" and "Conversational" shall be used for Cs data service RABs. The operator tuning is restricted to a choice between them. + +The final decision about the radio interface configuration is taken by the RNC during the Assignment procedure. + +#### B.1.13.2 Non-transparent services for UTRAN Iu mode + +Depending on the WAIUR signalled by the MS, the network is allowed to assign any radio resources with a radio access bearer parameter indicating a Quality of Service specifying + +| QoS Parameter | | Value | Comments | +|-------------------------------------|-----------------------------------------|----------------------------------|----------------------------------------------------------------------------------| +| | | | | +| Traffic Class | | Streaming | Subject to operator tuning (Note 3) | +| RAB Asymmetry Indicator | | Symmetric | | +| Maximum bit rate | | 14.4, 28.8, 57.6 kbit/s | Maximum bit rate is set to the highest value $\leq$ WAIUR (Note 1) | +| Guaranteed bit rate | | 14.4, 28.8, 57.6 kbit/s | Operator may choose any of the possible values less or equal to WAIUR. (Note 1). | +| Delivery Order | | Yes | | +| Maximum SDU size | | 576 bits | | +| Transfer Delay | | 250 ms | Subject to operator tuning | +| Traffic Handling Priority | | - | Not applicable to the streaming traffic class | +| Source statistics descriptor | | Unknown | | +| SDU Parameters | | | | +| | Residual bit error ratio | $10^{-3}$ | Subject to operator tuning. | +| | Delivery of erroneous SDUs | No error detection consideration | | +| SDU format information | | | | +| | RAB Subflow Combination bit rate | 57.6 kbit/s | (Note 2) | +| | RAB Subflow Combination bit rate | 28.8 kbit/s | (Note 2) | +| | RAB Subflow Combination bit rate | 14.4 kbit/s | | +| | RAB Subflow Combination bit rate | 0 kbit/s | indicates DTX, RFCI is not assigned | + +NOTE 1: If WAIUR is less or equal to 14.4 kbit/s then GBR and MBR shall be set to 14.4 kbit/s. + +NOTE 2: Only RAB subflow combination bit rates $\leq$ maximum bit rate shall be specified. + +NOTE 3: Only traffic Classes "Streaming" and "Conversational" shall be used for Cs data service RABs. The operator tuning is restricted to a choice between them. + +The final decision about the radio interface configuration is taken by the RNC during the Assignment procedure. + +#### B.1.13.3 Non-transparent services for GERAN Iu mode + +Depending on the WAIUR signalled by the MS, the network is allowed to assign any radio resources with a radio access bearer parameter indicating a Quality of Service specifying + +| QoS Parameter | Value | Comments | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| Traffic Class | Streaming | Subject to operator tuning (Note 8) | +| RAB Asymmetry Indicator | Symmetric | | +| Maximum bit rate | 12 kbit/s, 14,4 kbit/s, 24 kbit/s, 28,8 kbit/s, 36 kbit/s, 43,2 kbit/s, 48 kbit/s, 57.6 kbit/s | Maximum bit rate is set to the highest value $\leq$ WAIUR (Note 1, 3, 4, 5 and 6) | +| Guaranteed bit rate | 12 kbit/s, 14,4 kbit/s, 24 kbit/s, 28,8 kbit/s, 36 kbit/s, 43,2 kbit/s, 48 kbit/s, 57.6 kbit/s | Operator may choose any of the possible values less or equal to WAIUR. (Note 1) | +| Delivery Order | Yes | | +| Maximum SDU size | 480 bits if only RAB Subflow
Combination bit rates of multiples of 12 kbit/s are possible, 576 bits in all other cases | | +| Transfer Delay | 230 ms if only RAB Subflow
Combination bit rates of multiples of 12 kbit/s are possible, 250 ms in all other cases | Subject to operator tuning | +| Traffic Handling Priority | - | Not applicable to the streaming traffic class | +| Source statistics descriptor | Unknown | | +| SDU Parameters | | | +| Residual bit error ratio | $10^{-3}$ | Subject to operator tuning. | +| Delivery of erroneous SDUs | No error detection consideration | | +| SDU format information | | | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 57,6 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 48 kbit/s | (Note 2 and 3) | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 43,2 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 36 kbit/s | (Note 2 and 4) | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 28,8 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 24 kbit/s | (Note 2 and 5) | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 14,4 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 12 kbit/s | (Note 2 and 6) | +| RAB Subflow Combination bit rate | 0 kbit/s | indicates DTX, RFCI is not assigned | + +- NOTE 1: If WAIUR is less or equal to 14.4 kbit/s then GBR and MBR shall be set to 14.4 kbit/s for TCH/F14.4. If WAIUR is less or equal to 9.6 kbit/s then GBR and MBR shall be set to 12 kbit/s for TCH/F9.6. The maximum values for GBR and MBR shall not exceed the WAIUR unless the higher GBR and MBR can be reached with a smaller number of TCH/F (ref. subclause B.1.12.2). This means, that e.g., a GBR and MBR of 24 kbit/s (2 x TCH/F9.6) can be selected for a WAIUR of 19,2 kbit/s. +- NOTE 2: Only RAB subflow combination bit rates $\leq$ maximum bit rate shall be specified. +- NOTE 3: If the WAIUR is 38,4 kbit/s, a GBR and MBR of 48 kbit/s is possible for 4 x TCH/F9.6. +- NOTE 4: If the WAIUR is 28,8 kbit/s, a GBR and MBR of 36 kbit/s is possible for 3 x TCH/F9.6. +- NOTE 5: If the WAIUR is 19,2 kbit/s, a GBR and MBR of 24 kbit/s is possible for 2 x TCH/F9.6. +- NOTE 6: If the WAIUR is 9,6 kbit/s, a GBR and MBR of 12 kbit/s is possible for 1 x TCH/F9.6. +- NOTE 7: The Subflow SDU size should only be present when the individual Subflows have different sizes. +- NOTE 8: Only traffic Classes "Streaming" and "Conversational" shall be used for Cs data service RABs. The operator tuning is restricted to a choice between them. + +The final decision about the radio interface configuration is taken by the BSS during the Assignment procedure. + +## B.2 Low Layer/High Layer Compatibility Information Element + +### B.2.1 Introduction + +#### B.2.1.1 General Consideration + +The purpose of the Low Layer/High Layer Compatibility Information Element (LLC/HLC-IE) is to provide a means for additional end-to-end compatibility checking by an addressed entity (e.g. a remote user, an interworking unit or a high layer function network node). The LLC/HLC-IE may be manipulated by the PLMN to maintain consistency with the setup parameter negotiation between the mobile station and the network (ref. to 3GPP TS 29.007). The LLC/HLC-IE is transferred transparently by the ISDN between the call originating PLMN and the addressed entity. + +With respect to the individual parameter settings at the MS the following cases may be distinguished (see 3GPP TS 27.002 and 3GPP TS 27.003): + +- Mobile-originated call set up by a MS consisting of a MT with R interface: + - The setting results from respective MMI actions and/or MT internal settings. +- Mobile-terminated call set up to a MS consisting of a MT with R interface: + - The LLC/HLC related part of the compatibility check is carried out according to the knowledge of the MT concerning its implemented functions (i.e. answering the call). The offered field values determine the selection of the terminal function for the intended connection. + +Where applicable, the same settings and rules concerning LLC and/or HLC apply as for ISDN use (ref. ITU-T Recommendation Q.931 and ETR 018). However, considering that PLMN data transmission is based on ITU-T V.110 rate adaptation, the MS shall provide the LLC-IE for mobile-originated calls when using unrestricted or restricted digital information transfer capability. This is to assure the conveyance of the e.g. "ITU-T V.110" indication towards the called entity, as the comparable indication in the ISDN BC-IE may be lost. It shall also be possible to choose whether or not the LLC-IE is provided for the case of an information transfer capability "3,1 kHz audio ex PLMN". + +There shall be no contradiction of the information between the BC-IE and LLC-IE at the originating side. However, as some parts of the bearer capability may be modified during the transport of the call, there should be minimum duplication of this information between the BC-IE and the LLC-IE. + +If as a result of duplication, a contradiction occurs between the BC-IE and the LLC-IE at the terminating side, the receiving entity shall ignore the conflicting information in the LLC-IE. + +#### B.2.1.2 Interpretation of the Tables + +The individual contents of the LLC/HLC-IE are represented in the following tables. The indication of the applicable service group defines the link between the PLMN BC-IE and its associated LLC/HLC-IEs. + +If the appropriate message includes multiple BC-IEs and if LLC and/or HLC information is available, multiple LLCs and HLCs shall be included in the message. The LLC/HLC associated with the BC-IE indicating speech shall be marked as "not applicable" (3GPP TS 24.008). + +Legend:                    { xxxx | yyyy }            choice of values +                               ----                            not relevant for this service (set to appropriate value) +                               [ zzzz ]                        optional + +### B.2.2 LLC Bearer Service 20 + +#### B.2.2.1 Unrestricted / restricted digital information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
{ unrestricted digital restricted digital } | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | { V.110/X.30 V.120 } | +| 5a | Synchronous / asynchronous
Negotiation
User rate | asynchronous
in-band not possible
{ 0.3 1.2 2.4 4.8 9.6
14.4 19.2 28.8 38.4 48 56 } kbit/s | +| 5b
2) | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | { 8 16 } kbit/s
-----
{ not required 1) required }
{ not accepted 1) accepted } | +| 5b
3) | Rate adaption header / no header
Multiple frame establishment support
Mode of operation
Assignor / assignee
In-band / out-band negotiation | Rate adaption header included
Multiple frame establishment supported
Protocol sensitive mode of operation
----- | +| 5c | Number of stop bits
Number of data bits
Parity | { 1 2 } bits
{ 7 8 } bits
{ odd even none forced to 0 forced to 1 } | +| 5d | Duplex mode
Modem type | á[ duplex ]
----- | + +- 1) only these values are applicable to Mobile Originated Calls. +- 2) octet 5b for V.110/X.30. +- 3) octet 5b for V.120. + +#### B.2.2.2 3,1 kHz audio ex-PLMN information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|-------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
3.1kHz audio | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | {G.711 A-law G.711 u-law (PCS-1900)} | +| 5a | Synchronous / asynchronous
Negotiation
User rate | (may be set depending on user's requirement) | +| 5b | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | not relevant
but cannot be omitted
in order to have octet 5d | +| 5c | Number of stop bits
Number of data bits
Parity | (may be set depending on the user's requirement) | +| 5d | Duplex mode
Modem type | [ duplex ]
[{V.21 V.22 V.22bis V.26ter V.32 V.34}] | + +NOTE: If octet 5d is not specified, the whole LLC is not required. + +### B.2.3 LLC Bearer Service 30 + +#### B.2.3.1 Unrestricted / restricted digital information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
{ digital unrestricted restricted digital } | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | { V.110/X.30 X.31 flag stuffing V.120 H.223 and H.245 } | +| 5a | Synchronous / asynchronous
Negotiation
User rate | synchronous
in-band not possible
{ 0.3 1.2 2.4 4.8 9.6 1.2/0.075 14.4 19.2 28.8 32.0 38.4 48 56 } kbit/s | +| 5b
2) | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | { 8 16 } kbit/s
{ not required required }
{ not accepted accepted }
----- | +| 5b
3) | Rate adaption header / no header
Multiple frame establishment support
Mode of operation
Assignor / assignee
In-band / out-band negotiation | Rate adaption header included
Multiple frame establishment supported
Protocol sensitive mode of operation
----- | +| 5c
1) | Number of stop bits
Number of data bits
Parity | not relevant
but cannot be omitted
in order to have octet 5d | +| 5d
1) | Duplex mode
Modem type | [ duplex ]
----- | + +- 1) If octet 5d is not specified, octet 5c may be omitted. +- 2) octet 5b for V.110/X.30. +- 3) octet 5b for V.120. + +#### B.2.3.2 3,1 kHz audio ex-PLMN information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|-------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
3.1kHz audio | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | {G.711 A-law G.711 u-law (PCS-1900)} | +| 5a | Synchronous / asynchronous
Negotiation
User rate | (may be set depending on the user's requirement) | +| 5b | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | not relevant
but cannot be omitted
in order to have octet 5d | +| 5c | Number of stop bits
Number of data bits
Parity | (may be set depending on the user's requirement) | +| 5d | Duplex mode
Modem type | [ duplex ]
[ { V.22 V.22bis V.26ter V.32 V.34 } ] | + +NOTE: If octet 5d is not specified, octets 5a..5d may be omitted. + +### B.2.4 LLC Bearer Services 41 ... 46 + +Void. + +### B.2.5 LLC Bearer Services 51 ... 53 + +Void. + +### B.2.6 LLC Bearer Service 61 + +Void. + +### B.2.7 LLC Bearer Service 81 + +Void. + +### B.2.8 HLC Teleservices 11 ... 12 + +High layer compatibility information element: + +| Octet | Information element field | Field value | +|-------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Interpretation
Presentation method of protocol profile | ITU-T
first high layer characteristic identification to be used in the call
high layer protocol profile | +| 4 | High layer characteristics identific. | Telephony | + +### B.2.9 HLC Teleservices 21 ... 23 + +Not applicable. + +### B.2.10 HLC Teleservice 61 + +High layer compatibility information element: + +| Octet | Information element field | Field value | +|-------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Interpretation
Presentation method of protocol profile | ITU-T
first high layer characteristic identification to be used in the call
high layer protocol profile | +| 4 | High layer characteristics identific. | Facsimile G2/G3 | + +### B.2.11 HLC Teleservice 62 + +High layer compatibility information element: + +| Octet | Information element field | Field value | +|-------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Interpretation

Presentation method of protocol profile | ITU-T
first high layer characteristic identification to be
used in the call
high layer protocol profile | +| 4 | High layer characteristics identific. | Facsimile G2/G3 | + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|----------|-----|-----|--------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | Apr 1999 | | | | Transferred to 3GPP CN1 | 7.1.0 | | +| 03-1999 | CN#03 | | | | Approved at CN#03 | | 3.0.0 | +| 06-1999 | CN#04 | | 001 | | Introduction of EDGE channel codings into the specifications | 3.0.0 | 3.1.0 | +| 09-1999 | CN#05 | | 002 | | Asymmetry in EDGE | 3.1.0 | 3.2.0 | +| 09-1999 | CN#05 | | 003 | | EDGE related correction | 3.1.0 | 3.2.0 | +| 12-1999 | CN#06 | | 004 | | Introduction of FTM | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 005 | | Introduction of UMTS | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 006 | | Introduction of PIAFS and enhancement of processing at mobile terminated call | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 007 | | Introduction of multi media | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 008 | | Service clean-up for Release 99 | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 009 | | BC-IE setting for Real-time non-transparent FAX | 3.2.0 | 3.3.0 | +| 03-2000 | CN#07 | | 010 | | FALLBACK TO SPEECH IN A CS MULTIMEDIA CALL SETUP | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 011 | | Bit transparent services RDI and UDI | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 012 | | FTM corrections | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 013 | | Alignment to RANAP and other clarifications | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 014 | | Corrections related to MULTIMEDIA | 3.3.0 | 3.4.0 | +| 06-2000 | CN#08 | | 015 | | Missing Asymmetry preference indication in Table B. 5.a | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 016 | | Residual bit error ratio in Transparent Data | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 017 | | Adding the value of GBR of NT services | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 018 | | Application of multi media in GSM | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 019 | | Removal of packet access service | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 020 | | WAIUR in case of HO between UMTS and GSM | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 021 | | Adaptations for UMTS | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 022 | | Indication of discontinuous transfer for NT data | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 022 | | Indication of discontinuous transfer for NT data | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 023 | 1 | Indication of WAIUR 14.4kbit/s in case of UMTS FAX | 3.4.0 | 4.0.0 | +| 09-2000 | CN#09 | | 024 | 1 | UMTS clean-up | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 027 | | Cleanup of RAB parameter setting | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 028 | | Relevance of GSM specific BC-IE parameters for negotiating RLP version in UMTS | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 032 | | 32 kbit/s UDI/RDI multimedia in GSM | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 034 | | 3.1 kHz multimedia calls at 33.6 kbit/s data rate | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 036 | | RCR is not indicated from the network to the MS | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 038 | | Modification from V.25bis to V.250 | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 040 | | Delivery of erroneous SDUs parameter value | 4.0.0 | 4.1.0 | +| 12-2000 | CN#10 | | 042 | | Correction for 32 kbit/s UDI/RDI | 4.1.0 | 4.2.0 | +| 12-2000 | CN#10 | | 043 | | Removal of Bearer Service 30 Non-transparent | 4.1.0 | 4.2.0 | + +| | | | | | | | | +|---------|-------|-----------|-----|---|----------------------------------------------------------------------------------------------------------|-------|-------| +| 12-2000 | CN#10 | | 044 | | Handover for 56 kbit/s | 4.1.0 | 4.2.0 | +| 03-2001 | CN#11 | NP-010042 | 047 | 1 | Removal of blocking of higher modem speeds | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010046 | 048 | 1 | Deletion of NT Fax in GSM from Release 4. | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010042 | 050 | | RAB- assignment request (RAB parameter) | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010042 | 052 | | Handover for 56 kbit/s [Removal of flow diagram B.1.3.1.7] | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010047 | 053 | | Editorial modifications of flow diagrams | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010043 | 055 | | Correction of service's scope | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010202 | 057 | 2 | Corrections for a mobile terminated call using the single numbering scheme | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010047 | 058 | | Clarification of allowed combinations of FNUR and ACC values for the V.34 modem based 3G-H.324/M service | 4.2.0 | 4.3.0 | +| 06-2001 | CN#12 | NP-010255 | 060 | | Corrections of PLMN BC attributes | 4.3.0 | 4.4.0 | +| 09-2001 | CN#13 | NP-010438 | 062 | 1 | Removal of erroneous IR value | 4.4.0 | 4.5.0 | +| 09-2001 | CN#13 | NP-010438 | 063 | 1 | Removal of erroneous information in B.1.3.1.6. | 4.4.0 | 4.5.0 | +| 09-2001 | CN#13 | NP-010438 | 066 | 1 | Negotiation of Rate adaptation/Other rate adaptation | 4.4.0 | 4.5.0 | +| 12-2001 | CN#14 | NP-010574 | 069 | | SDU size for transparent data at 33.6 kbit/s | 4.5.0 | 4.6.0 | +| 12-2001 | CN#14 | NP-010604 | 070 | 3 | Terminology clarifications as requested by TSG GERAN | 4.6.0 | 5.0.0 | +| 03-2002 | CN#15 | NP-020081 | 074 | 1 | Negotiation of parameter values for facsimile | 5.0.0 | 5.1.0 | +| 03-2002 | CN#15 | NP-020084 | 075 | 1 | Mobile terminated call with single numbering scheme | 5.0.0 | 5.1.0 | +| 06-2002 | CN#16 | NP-020169 | 071 | 7 | Service change and fallback for UDI/RDI multimedia calls | 5.1.0 | 5.2.0 | +| 06-2002 | CN#16 | NP-020172 | 077 | 1 | Multislot clarification | 5.1.0 | 5.2.0 | +| 09-2002 | CN#17 | NP-020404 | 080 | - | Removal of SDU error ratio for NT services | 5.2.0 | 5.3.0 | +| 12-2002 | CN#18 | NP-020617 | 081 | 1 | CS Data Services (including HSCSD and EDGE) for GERAN lu mode | 5.3.0 | 5.4.0 | +| 12-2002 | CN#18 | NP-020619 | 082 | 4 | Mobile originating BC handling for SCUDIF calls | 5.3.0 | 5.4.0 | +| 03-2003 | CN#19 | NP-030075 | 084 | 1 | Removal of S reference point within the MS and introduction of GERAN lu mode | 5.4.0 | 5.5.0 | +| 06-2003 | CN#20 | NP-030201 | 088 | | Negotiation of fixed network user rate (FNUR) | 5.5.0 | 5.6.0 | +| 06-2003 | CN#20 | NP-030202 | 091 | 1 | Removal of S interface in the MS | 5.5.0 | 5.6.0 | +| 06-2003 | CN#20 | NP-030260 | 096 | 1 | BC-IE alignment with 24.008. | 5.5.0 | 5.6.0 | +| 06-2003 | CN#20 | NP-030201 | 099 | 1 | Use of single or multislot configurations | 5.5.0 | 5.6.0 | +| 09-2003 | CN#21 | NP-030327 | 100 | 3 | Interpretation of "no BC-IE in CALL PROC/CONF messages" | 5.6.0 | 5.7.0 | +| 06-2004 | CN#24 | NP-040239 | 107 | 1 | Interpretation of "no BC-IE in CALL PROC/CONF messages" | 5.7.0 | 5.8.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.8.0 | 6.0.0 | +| 06-2005 | CP#28 | CP-050209 | 110 | 4 | Transparent data call request in dual mode case | 6.0.0 | 6.1.0 | +| 06-2005 | CP#28 | CP-050243 | 114 | 3 | Alignment to R99 correction of NA value for Data Compression | 6.0.0 | 6.1.0 | +| 09-2005 | CP#29 | CP-050379 | 115 | | Removal of "S" reference point within MS | 6.1.0 | 6.2.0 | +| 12-2006 | CT#34 | CP-060618 | 118 | | RAB traffic class | 6.2.0 | 6.3.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.3.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | + +| 12-2010 | CT#50 | CP-100779 | 120 | 1 | Correcting non-specific external references | 9.0.0 | 9.1.0 | +|----------------|---------|-----------|-----|-----|--------------------------------------------------------|-----------------------------------------|--------| +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.1.0 | 9.1.0 | 10.0.0 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.0 | 10.0.0 | 11.0.0 | +| 10-2014 | | | | | Automatic upgrade from previous Release | 11.0.0 | 12.0.0 | +| 12-2015 | | | | | Automatic upgrade from previous Release | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | - | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | CT#88e- | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/27_series/27002/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/27_series/27002/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d35e9928054e0bd57e44fe2fcc61c584775b9138 --- /dev/null +++ b/marked/Rel-16/27_series/27002/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3867a9ea761f276ded20ef31d9badfbe83167db40d93a5b331186d64f7296b93 +size 21679 diff --git a/marked/Rel-16/27_series/27002/raw.md b/marked/Rel-16/27_series/27002/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..975dc973efd430da5b81aaed28c0ccc249095d71 --- /dev/null +++ b/marked/Rel-16/27_series/27002/raw.md @@ -0,0 +1,785 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 1.1 References ..... | 6 | +| 1.2 Abbreviations ..... | 8 | +| 1.3 Definitions..... | 8 | +| 2 Reference Configuration..... | 8 | +| 2.1 Customer Access Configuration..... | 8 | +| 2.2 Terminal Adaptation Function (TAF)..... | 8 | +| 3 Terminal Adaptation Functions for transparent services ..... | 9 | +| 3.1 Rate Adaptation in A/Gb mode..... | 9 | +| 3.1.1 Rate Adaptation - R interface..... | 9 | +| 3.1.2 Rate Adaptation - S Interface (ITU-T I.420 [14]) ..... | 9 | +| 3.2 Interchange Circuit Signalling Mapping - ITU-T V-series interface..... | 9 | +| 3.2.1 Mapping of V.24 [19] circuits to status bits ..... | 9 | +| 3.2.2 Single slot configurations (TCH/F9.6 or TCH/F4.8) ..... | 10 | +| 3.2.3 Multislot configurations (TCH/F9.6 or TCH/F4.8)..... | 10 | +| 3.2.4 Channel codings TCH/F14.4, TCH/F28.8..... | 10 | +| 3.3 Interface Signal Levels - R interface..... | 10 | +| 3.4 Call Establishment and Clearing Signalling Mapping ..... | 11 | +| 3.4.1 V-series interface Autocalling/answering ..... | 11 | +| 3.4.2 S Interface (I.420) Signalling Mapping..... | 11 | +| 3.4.3 Call Establishment Manual Operation - Utilizing the Unrestricted Digital Capability..... | 11 | +| 3.4.4 V-series interface Call Clearing ..... | 11 | +| 4 Terminal Adaptation Functions for non-transparent services..... | 11 | +| 4.1 Data Structure..... | 11 | +| 4.1.1 Data Structure on S Interface..... | 11 | +| 4.1.2 Data Structure on R Interface ..... | 12 | +| 4.1.3 Data Structure Provided by the L2R Function to the RLP Function..... | 12 | +| 4.2 Signalling Mapping ..... | 12 | +| 4.2.1 Interchange Circuit Signalling Mapping - ITU-T V-series interface ..... | 12 | +| 4.2.2 Call Establishment and Clearing Signalling Mapping ..... | 13 | +| 4.3 Flow Control ..... | 13 | +| 4.3.1 Conditions Requiring Flow Control towards the Network..... | 13 | +| 4.3.2 Conditions Requiring Flow Control towards TE2..... | 13 | +| 4.3.3 Local Flow Control..... | 13 | +| 4.3.4 Character Orientated Protocol with No Flow Control..... | 14 | +| 4.4 Buffers..... | 14 | +| 4.4.1 TX Buffers..... | 14 | +| 4.4.2 RX Buffers..... | 14 | +| 4.5 Bit Transparency ..... | 14 | +| 4.6 Transportation of "BREAK" condition ..... | 14 | +| 4.7 Data Compression ..... | 14 | +| 5 Terminal interfacing to 3GPP TS 24.008 [8] Mapping ..... | 15 | +| 5.1 Mobile Originated Calls..... | 16 | +| 5.2 Mobile Terminated Calls..... | 16 | +| 5.3 Call Clearing ..... | 17 | +| 5.3.1 Mobile initiated ..... | 17 | +| 5.3.2 Network initiated..... | 17 | +| Annex A (normative): L2R Functionality ..... | 18 | +| A.1 Introduction..... | 18 | +| A.2 The L2RCOP..... | 18 | +| A.3 Use of the L2RCOP ..... | 21 | +| A.3.1 Radio Link Connection Control ..... | 21 | + +A.3.2 Data Transfer.....21 +A.3.3 Status Transfer.....21 +A.3.4 Flow Control .....21 +A.3.5 Break .....21 +A.3.5.1 Normal Realization.....21 +A.3.5.2 Realization in case of Data Compression is used.....22 +**Annex B (informative): Use of a 9 pin connector as an MT2 type interface .....23** +**Annex C (informative): General mapping of ITU-T V.24 [19] circuits to channel status bits 24** +Annex D (informative): Change history.....25 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the interfaces and Terminal Adaptation Functions (TAF) integral to a Mobile Termination (MT) which enable the use of asynchronous bearer services in the PLMN and the attachment of asynchronous terminals to a MT (see 3GPP TS 24.002 [3] and 3GPP TS 23.101 [6]). + +The general aspects of Terminal Adaptation Functions are contained in 3GPP TS 27.001 [10]. + +The present document covers support of these services for the following interfaces and procedures: + +- (i) ITU-T V.14 [16] procedures. +- (ii) ITU-T V.21 [17] DTE/DCE interface. +- (iii) ITU-T V.22bis [18] DTE/DCE interface. +- (iv) ITU-T V.32 [24] DTE/DCE procedures. +- (v) ITU-T I.420 [14] S interface. +- (vi) ITU-T V.250 [22] signalling procedures. + +The asynchronous data rates between the MT and the IWF are defined in 3GPP TS 22.002 [5]. + +NOTE: From GSM R99 onwards the following services are no longer required in a PLMN: + +- the dual Bearer Services "alternate speech/data" and "speech followed by data"; +- the dedicated services for PAD and Packet access; +- the BS 21 ... 26 and BS 31 ... 34. + +The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to GSM Release 98. + +NOTE: Please note that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. GERAN Iu mode is for further study. + +## 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. + +- [1] Void. +- [2] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types". +- [3] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [4] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [5] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [6] 3GPP TS 23.101: "General UMTS Architecture". +- [7] 3GPP TR 23.910: "Circuit Switched Data Bearer Services". +- [8] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3". + +- [9] 3GPP TS 24.022: "Radio Link Protocol (RLP) for Circuit Switched Bearer and Teleservices". +- [10] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [11] 3GPP TS 27.007: "AT command set for 3G User Equipment (UE)". +- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [13] 3GPP TS 29.007: "General requirements on Interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [14] ITU-T Recommendation I.420 (1998):"Basic user-network interface". +- [15] ITU-T Recommendation V.4 (1988): "General structure of signals of international alphabet No.5 code for character oriented data transmission over public telephone networks". +- [16] ITU-T Recommendation V.14 (1993): "Transmission of start-stop characters over synchronous bearer channels". +- [17] ITU-T Recommendation V.21 (1988): "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [18] ITU-T Recommendation V.22bis (1988): "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [19] ITU-T Recommendation V.24 (1996): "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [20] ITU-T Recommendation V.25 (1996): "Automatic answering equipment and general procedures for automatic calling equipment on the general switched telephone network including procedures for disabling of echo control devices for both manually and automatically established calls". +- [21] Void. +- [22] ITU-T Recommendation V.250 (1999): "Serial asynchronous automatic dialling and control". +- [23] ITU-T Recommendation V.28 (1993): "Electrical characteristics for unbalanced double-current interchange circuits". +- [24] ITU-T Recommendation V.32 (1993): "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use in the general switched telephone network and on leased telephone-type circuits". +- [25] ITU-T Recommendation V.42 (1996): "Error-correcting procedures for DCEs using asynchronous-to-synchronous conversion". +- [26] ITU-T Recommendation V.42 bis (1990): "Data compression procedures for data circuit-terminating equipment (DCE) using error correction procedures". +- [27] ITU-T Recommendation V.110 (1996): "Support of data terminal equipments with V-Series interfaces by an integrated services digital network". +- [28] ITU-T Recommendation X.28 (1997): "DTE/DCE interface for a start-stop mode Data Terminal Equipment accessing the Packet Assembly/Disassembly facility (PAD) in a public data network situated in the same country". +- [29] Personal Computer Memory Card Association: "PCMCIA 2.1 or PC-Card 3.0 electrical specification or later revisions". + +- [30] Infrared Data Association IrDA "IrPHY Physical layer signalling standard". +- [31] ISO 2110 (1989): "Data communication - 25-pole DTE/DCE interface connector and contact number assignments". +- [32] ITU-T Recommendation Q.931 (1998): "ISDN user-network interface layer 3 specification for basic call control". + +## 1.2 Abbreviations + +In addition to the abbreviations used in the present document that are listed in TR 21.905 [12] the following internal abbreviations are used: + +| | | +|-------|----------------------------------------------| +| CFI | Call Failure Indication | +| CRN | Call Request with Number | +| DIC | Disregard Incoming Call | +| IA5 | International Alphabet no. 5 | +| INC | INcoming Call | +| INV | INVALID | +| ITU-T | ITU-Telecommunication Standardization Sector | +| VAL | VALID | + +## 1.3 Definitions + +The term 'mobile station' (MS) in the present document is synonymous with the term 'user equipment' (UE) as defined in 3GPP TR 21.905 [12]. + +The term 'TE2' in the present document is synonymous with the term 'TE' as defined in 3GPP TR 21.905 [12]. + +The term 'MT2' in the present document is synonymous with the term 'MT' as defined in 3GPP TR 21.905 [12]. + +In addition to the definitions used in the present document that are listed in TR 21.905 [12] the following internal definitions are used: + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +# --- 2 Reference Configuration + +3GPP TS 27.001 [10], 3GPP TS 23.101 [6] and 3GPP TS 24.002 [3] describe the basic reference configurations. + +## 2.1 Customer Access Configuration + +This configuration is as shown in figure 1 of 3GPP TS 24.002 [3]. The present document specifically refers to the Mobile Terminations (MTs) which support terminals of the type TE1 and TE2 with asynchronous capabilities. The TAF is functionally a part of an MT1, MT2 or MT0 with an integral asynchronous data capability. + +## 2.2 Terminal Adaptation Function (TAF) + +The TAF provides facilities to allow manual or automatic call control functions associated with circuit switched services. The following functions are also included: + +- Conversion of electrical, mechanical, functional and procedural characteristics of the ITU-T V series and ISDN type interfaces to those required by the PLMN. +- Bit rate adaptation of the ITU-T V series data signalling rates and the ISDN 64 kbit/s to that provided in the PLMN. + +- The mapping functions necessary to convert automatic calling and/or automatic answering procedures of the ITU-T recommendation V.250 [22] and parameters for asynchronous operation. +- The mapping functions necessary to convert S interface signalling to the PLMN Dm channel signalling. +- Flow control (in some cases resulting in non-transparency of data as described in 4.3). +- Layer 2 Relaying (see annex A). +- In-call modification function. +- Synchronization procedure, which means the task of synchronizing the entry to and the exit from the data transfer phase between two user terminals. This is described in 3GPP TS 27.001 [10]. +- Filtering of channel control information as described in 3GPP TS 27.001 [10]. +- Terminal compatibility checking. +- Splitting and combining of the data flow in case of multiple substream data configurations. + +# --- 3 Terminal Adaptation Functions for transparent services + +3GPP TS 43.010 [2] defines connection types for the support of transparent services in A/Gb mode whilst 3GPP TR 23.910 [7] defines connection types for transparent services in UTRAN Iu mode. + +## 3.1 Rate Adaptation in A/Gb mode + +3GPP TS 44.021 [4] describes the rate adaptation scheme to be utilized over the Base Station (BS) to Mobile Station (MS) link. 3GPP TS 43.010 [2] refers to the rate adaptation elements to be provided in the MS. + +### 3.1.1 Rate Adaptation - R interface + +This is provided as indicated in 3GPP TS 44.021 [4]. + +### 3.1.2 Rate Adaptation - S Interface (ITU-T I.420 [14]) + +VOID + +## 3.2 Interchange Circuit Signalling Mapping - ITU-T V-series interface + +The interchange circuit signalling at the interface between the TE2 and the MT shall conform to ITU-T Recommendation V.24 [19]. The signals required at this interface are shown in table 3. + +The mapping of these signals to the pins of a 25 pin D-type connector is given in ISO 2110 [31]. The mapping for a commonly used 9 pin connector is given in annex B. + +### 3.2.1 Mapping of V.24 [19] circuits to status bits + +Status bits SA, SB and X are used to convey channel control information associated with the data bits in the data transfer state. Table 1 shows the mapping scheme between the ITU-T V.24 [19] circuit numbers and the status bits for the transparent mode. It also shows how the unused status bits should be handled. It is derived from the general mapping scheme described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of these status bits by the various channel codings is described in subsequent sections. + +**Table 1: Mapping scheme at the MT for the transparent mode** + +| Signal at TE2/MT interface or condition within the MT | Mapping direction: MT to IWF | Mapping direction: IWF to MT | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------| +| CT 105 | not mapped (note 1) | | +| CT 106 | | from status bit X (note 7) | +| CT 107 | | not mapped (note 5) | +| CT 108/2 | not mapped (note 6) | | +| CT 109 | | from status bit SB (note 7) | +| CT 133 | not mapped (note 2) | | +| always ON | to status bit SA (note 3) | | +| always ON | to status bit SB (note 1) | | +| always ON | to status bit X (note 4) | | +| ignored by MT | | from status bit SA (note 3) | +| NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex C), could be used to carry CT 105. However, CT 105 should always be ON in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. No interchange circuit shall be mapped to the SB bit, which shall always be set to ON in the data transfer state. | | | +| NOTE 2: CT 133 is not mapped since there is no flow control in transparent mode. | | | +| NOTE 3: The SA bits in both directions are available only with certain channel codings. Therefore, for maximum compatibility, they should not be mapped. | | | +| NOTE 4: The X bit towards the IWF is not mapped and shall always be set to ON in the data transfer state since there is no flow control in transparent mode. | | | +| NOTE 5: CT 107 is controlled by the channel synchronisation process (07.01). | | | +| NOTE 6: CT 108/2 may be used in the call setup and answering processes. | | | +| NOTE 7: The status bits are filtered before being mapped to the ITU-T V.24 [19] circuits (3GPP TS 27.001 [10]). | | | + +### 3.2.2 Single slot configurations (TCH/F9.6 or TCH/F4.8) + +3GPP TS 44.021 [4] refers to the frame structure and identifies the use of the status bits for the carriage of signalling information in transparent mode. The S bits are put into two groups. SA is carried by bits S1, S3, S6, S8 and SB by bits S4, S9 in the ITU-T Recommendation V.110 [27] 80-bit intermediate rate frame. + +### 3.2.3 Multislot configurations (TCH/F9.6 or TCH/F4.8) + +In transparent multislot configurations, status bits S1, S3 and the X-bit between the D12 and D13 - in the ITU-T Recommendation V.110 [27] 80-bit intermediate rate frame - are used for transferring substream numbering information. The S4-bit is used for frame synchronization between the parallel substreams (reference 3GPP TS 44.021 [4]). The remaining S bits are put into two groups. SA is carried by bits S6, S8 and SB by bit S9. The remaining X bits can be used as described in subclause 3.2.1. + +### 3.2.4 Channel codings TCH/F14.4, TCH/F28.8 + +For information on the mapping of the interchange circuit signalling bits in the 14,5 kbit/s multiframe structure, refer to 3GPP TS 44.021 [4]. There is no SA bit in this channel coding. Only the SB and X bits are carried. + +## 3.3 Interface Signal Levels - R interface + +The signal levels at the interface between the TE2 and the MT shall conform to ITU-T V.28 [23], or to IrDA IrPHY physical signalling standard specification [30], or to PCMCIA 2.1 [29], or to PC-Card 3.0 [29] electrical specification or to later revisions. + +## 3.4 Call Establishment and Clearing Signalling Mapping + +### 3.4.1 V-series interface Autocalling/answering + +- These procedures are provided according to ITU-T Recommendation V.250 [22] and 3GPP TS 27.007 [11]. +- For autocalling, during the call establishment phase, i.e. after signalling, calling tone according to ITU-T Recommendation V.25 [20] shall be generated in the IWF (3GPP TS 29.007 [13]). + +During the call establishment phase: + +- the states of the ITU-T Recommendation V.24 [19] interchange circuits shall be according to 3GPP TS 27.001 [10]; +- the data and status bits from the IWF shall not be mapped; +- the data and status bits towards the IWF shall be according to 3GPP TS 27.001 [10]. + +### 3.4.2 S Interface (I.420) Signalling Mapping + +Void. + +### 3.4.3 Call Establishment Manual Operation - Utilizing the Unrestricted Digital Capability + +In this case the user shall not hear network supervisory tones or answer tone. The data transfer phase shall be entered automatically. + +### 3.4.4 V-series interface Call Clearing + +This procedure is provided according to ITU-T Recommendation V.250 [22] and 3GPP TS 27.007 [11]. + +During the call clearing phase: + +- the states of the ITU-T Recommendation V.24 [19] interchange circuits shall be according to ITU-T Recommendation V.24 [19]; +- the data and status bits from the IWF shall not be mapped or used by the MT in any way; +- the data and status bits towards the IWF have no significance and may be set to 1 and OFF respectively. + +# --- 4 Terminal Adaptation Functions for non-transparent services + +3GPP TS 43.010 [2] defines connection types for the support of non-transparent services in A/Gb mode whilst 3GPP TR 23.910 [7] defines connection types for non-transparent services in UTRAN Iu mode. + +## 4.1 Data Structure + +### 4.1.1 Data Structure on S Interface + +Void. + +### 4.1.2 Data Structure on R Interface + +The protocol models for this are described in 3GPP TS 43.010 [2]. The data consists of 7 or 8 bit characters with additional start and stop elements. The 7 bit data can additionally have an associated parity bit, 8 bit data cannot have an additional parity bit. + +The interchange circuit signalling at the interface between the TE2 and the MT shall conform to ITU-T Recommendation V.24 [19]. The signals required at this interface are shown in table 3. + +The interface shall provide inband (XON/XOFF) and out of band (CT106) flow control. The use of CT133 for out of band flow control shall be implemented according to ITU-T Recommendation V.42 [25]. + +### 4.1.3 Data Structure Provided by the L2R Function to the RLP Function + +See annex A. + +## 4.2 Signalling Mapping + +### 4.2.1 Interchange Circuit Signalling Mapping - ITU-T V-series interface + +Status bits SA, SB and X are used to convey channel control information associated with the data bits in the data transfer state. Table 2 shows the mapping scheme between the ITU-T Recommendation V.24 [19] circuit numbers and the status bits for the non-transparent mode. It also shows how the unused status bits should be handled. It is derived from the general mapping scheme described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of the status bits by the L2RCOP is described in annex A. + +**Table 2: Mapping scheme at the MT for the non-transparent mode** + +| Signal at TE2/MT interface or condition within the MT | Mapping direction: MT to IWF | Mapping direction: IWF to MT | +|-------------------------------------------------------|------------------------------|------------------------------| +| CT 105 | not mapped (note 1) | | +| CT 106 (note 4) | | from status bit X (note 7) | +| CT 107 | | not mapped (note 5) | +| CT 108/2 | not mapped (note 6) | | +| CT 109 | | from status bit SB | +| CT 133 (note 8) | to status bit X (notes 3,8) | | +| always ON | to status bit SA (note 2) | | +| always ON | to status bit SB (note 1) | | +| ignored by MT | | from status bit SA (note 2) | + +NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex C), could be used to carry CT 105. However, CT 105 should always be ON in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. No interchange circuit shall be mapped to the SB bit which shall always be set to ON in the data transfer state. + +NOTE 2: The SA bits (both directions) are not mapped since CTs 107 and 108/2 are handled locally (notes 5 and 6). + +NOTE 3: The condition of status bit X towards the IWF may also be affected by the state of the receive buffer in the MT. + +NOTE 4: The state of CT 106 (or other local flow control mechanism) may also be affected by the state of the transmit buffer in the MT and the state of the RLP (RR/RNR). + +NOTE 5: CT 107 is controlled by the channel synchronisation process (3GPP TS 27.001 [10]). + +NOTE 6: CT 108/2 may be used in the call setup and answering processes. + +NOTE 7: For inband local flow control, changes in the condition of the status bit X from the IWF also result in the sending of XON or XOFF to the DTE. + +NOTE 8: For inband local flow control, CT 133 is not mapped and the status bit X towards the IWF is controlled by the reception of XON and XOFF characters from the DTE. + +### 4.2.2 Call Establishment and Clearing Signalling Mapping + +This is identical to the transparent case with the exception of the transparent/non-transparent element, see clause 5. + +In addition, the L2R/RLP shall give an explicit indication when the link into the connected network is established. If the link fails, an explicit "link lost" indication shall be given. + +## 4.3 Flow Control + +The passage of flow control information between L2Rs is described in annex A. subclauses 4.3.1, 4.3.2 and 4.3.3 describe the operation of the flow control mechanisms. These mechanisms apply for all the non-transparent services covered by the present document, with the exception of Character Orientated Protocol with No Flow Control which is treated in subclause 4.3.4. + +### 4.3.1 Conditions Requiring Flow Control towards the Network + +The L2R function shall send immediately a "flow control active" indication in the following circumstances: + +- (i) If the receive buffer from the radio side reaches a preset threshold (BACKPRESSURE). + +- (ii) If local flow control is initiated by the TE2 (see 4.3.3 a) or c)). On receipt of this flow control indication transmission of data from the receive buffer towards the TE2 is halted. + +On removal of the buffer congestion or local flow control the L2R shall send a "flow control inactive" indication. + +In addition, for the local flow control condition, transmission of data from the receive buffers shall be restarted. + +### 4.3.2 Conditions Requiring Flow Control towards TE2 + +The L2R functions shall immediately activate local flow control (see 4.3.3 b) or d)) under the following circumstances: + +- (i) The transmit buffer reaches a pre-set threshold (BACKPRESSURE). +- (ii) The L2R receives a "flow control active" indication. + +On removal of buffer congestion or receipt of L2R/RLP "flow control inactive" the local flow control shall be removed. + +### 4.3.3 Local Flow Control + +Two methods of local flow control are allowed: + +Outband: + +- a) From TE2: CT133 shall be turned OFF to indicate flow control active, and ON to indicate flow control inactive. +- b) From TAF: CT106 shall be turned OFF to indicate flow control active, and ON to indicate flow control inactive. + +Inband: + +- c) From TE2: XOFF (DC3) is sent to indicate flow control active. XON (DC1) is sent to indicate flow control inactive. The XON/XOFF characters received from the TE2 are extracted by the L2R from the data stream and are not sent across the radio interface. Where XON/XOFF is utilized then the TAF shall generate flow control active/inactive immediately, i.e. the XON/XOFF characters do not enter the transmit buffer. +- d) From TAF: As from TE2. + +If the outband method is used, the L2R shall pass the DC1/DC3 characters as data, i.e. no flow control indications shall be generated on receipt of DC1/DC3. + +### 4.3.4 Character Orientated Protocol with No Flow Control + +If the users layer 2 indicates Character Orientated Protocol with no flow control then no flow control is used, i.e. the X-bit is not set to OFF and DC1/DC3 characters are passed through as data. + +## 4.4 Buffers + +### 4.4.1 TX Buffers + +Data received on CT103 from the TE2 shall be buffered such that if the MT is unable to transfer the data over the radio path then data is not lost. + +The buffer shall be capable of holding the data. Its size is up to the implementers. + +When the buffer is half full, TE2 shall be flow controlled as per 4.3.2, unless Character Orientated Protocol with No Flow Control is being used (see 4.3.4). + +### 4.4.2 RX Buffers + +Data for transfer to the TE2 on CT104 shall be buffered such that if the TE2 is unable to accept data then data transferred from the MT is not lost. + +The buffer size should be up to the implementers. + +When the buffer becomes half full, the L2R shall send a "flow control active" indication, unless Character Orientated Protocol with No Flow Control is being used. + +## 4.5 Bit Transparency + +Void. + +## 4.6 Transportation of "BREAK" condition + +The "BREAK" condition must be recognized by the L2R function and passed immediately to the IWF. The L2R shall generate a "BREAK" condition to the TE2 on receipt of a "BREAK" indication from the IWF. + +Annex A describes how the L2R shall transport the "BREAK" indication. + +## 4.7 Data Compression + +L2R optionally includes a data compression function according to ITU-T V.42bis [26] that spans from the MS to the IWF in the MSC. The error correction function is provided by RLP instead of ITU-T Recommendation V.42 [25]. RLP XID is used to negotiate compression parameters. L2R includes the ITU-T V.42bis [26] control function especially for reinitializing in case of break recognition or RLP reset and error indication by the data compression function respectively. + +**Table 3: Minimum set of Interchange Circuits** + +| Circuit Number | Circuit Name | Ground | Data | | Control | | +|----------------|--------------------------------------------|--------|--------|----------|---------|----------| +| | | | To TE2 | From TE2 | To TE2 | From TE2 | +| CT102 | Common return | x | | | | | +| CT103 | Transmitted data | | | x | | | +| CT104 | Received data return | | x | | | | +| CT105 | Request to send (note 2) | | | | | x | +| CT106 | Ready for sending | | | | x | | +| CT107 | Data set ready | | | | x | | +| CT108/2 | Data terminal ready | | | | | x | +| CT109 | Data channel received line signal detector | | | | x | | +| CT125 | Calling indicator (note 1) | | | | x | | +| CT133 | Ready for Receiving (note 2) | | | | | x | + +NOTE 1: CT125 is used with the automatic answering function of the TAF. + +NOTE 2: CT105 and CT133 are assigned to the same connector pin on both the standard 25 pin connector (ISO 2110) and the commonly used 9 pin connector (annex B). When this pin is used for CT133 then on the DCE (MT) side of the interface CT 105 is treated as being always in the ON condition. Similarly, when this pin is being used for CT105 then on the DCE (MT) side of the interface CT 133 is treated as being always in the ON condition. As circuit 133 is used only in duplex operation and circuit 105 is used only in half duplex operation (which is not supported by GSM or UMTS) there should be no conflict. + +# 5 Terminal interfacing to 3GPP TS 24.008 [8] Mapping + +Only those elements/messages that are of particular relevance are considered. + +Interface procedures not directly mappable to 3GPP TS 24.008 [8] are not considered. Mobile management procedures of 3GPP TS 24.008 [8] are not considered applicable. + +Mapping of other call establishment or clearing messages to the S interface e.g. "Call proceeding" etc. has not been included. It is assumed these can be mapped directly and as such are of no relevance to the manual interfaces. + +For the Alternate speech/group 3 facsimile service the TAF shall be able to generate a "Modify" message according to the defined procedure in 3GPP TS 24.008 [8]. + +## 5.1 Mobile Originated Calls + +Call establishment is initiated by the keypad or DTE action: + +a) Setup + +| Element | Derived from | +|--------------------|------------------------------------------------------| +| | MMI | +| Called Address | Keypad | +| Called Sub Address | Keypad | +| HLC | Derived from internal settings or MMI information. | +| LLC | Same as HLC | +| BC | Same as HLC 3GPP TS 27.001 [10] gives allowed values | + +b) Release Complete + +| Element | Derived from | +|---------|--------------------| +| | MMI | +| Cause | Display (optional) | + +## 5.2 Mobile Terminated Calls + +Call establishment is initiated by receipt of Setup at the MS: + +a) Setup + +| Element | Mapped on to | +|--------------------|--------------------| +| | MMI | +| Called Address | Display (optional) | +| Called Sub Address | Display (optional) | +| HLC | Display (optional) | +| LLC | Display (optional) | +| BC | Display (optional) | + +### b) Call Confirm + +Information for the BC element in the call confirm shall be derived from e.g. MMI or by internal settings. + +### c) Connect + +Connect is sent in response to connect from MMI. + +## 5.3 Call Clearing + +### 5.3.1 Mobile initiated + +Call clearing is initiated by the keypad or DTE action: + +Disconnect + +| Element | Derived from | | +|---------|--------------|-------------------| +| | MMI | ITU-T V.250 [22] | +| Cause | Keypad | See section 3.4.4 | + +### 5.3.2 Network initiated + +Call clearing is initiated by receipt of Disconnect at the MS: + +Disconnect + +| Element | Mapped on to | | +|---------|--------------------|--------------------------| +| | MMI | ITU-T V.250 [22] | +| Cause | Display (optional) | Unsolicited result codes | + +# Annex A (normative): L2R Functionality + +## A.1 Introduction + +This annex describes the L2R functionality for non-transparent character oriented protocols. The general aspects of L2Rs are described in 3GPP TS 27.001 [10]. Figure 1 shows the 3 sub-functions of a character oriented L2R. + +![Figure 1: Diagram of a Character Oriented Relay Entity (CORE) showing its internal components and interfaces. The diagram shows a central box labeled 'CORE'. Inside this box, on the left, is a 'CONTPT Entity' and on the right is an 'L2RCOP Entity'. A horizontal line labeled 'CONTPT' enters the box from the left and connects to the CONTPT Entity. Another horizontal line labeled 'L2RCOP' exits the box from the right and connects to the L2RCOP Entity. The top and bottom boundaries of the CORE box are represented by diagonal lines meeting at the center, forming a trapezoidal shape.](21ad58fee90f2be50708ff541d225507_img.jpg) + +Figure 1: Diagram of a Character Oriented Relay Entity (CORE) showing its internal components and interfaces. The diagram shows a central box labeled 'CORE'. Inside this box, on the left, is a 'CONTPT Entity' and on the right is an 'L2RCOP Entity'. A horizontal line labeled 'CONTPT' enters the box from the left and connects to the CONTPT Entity. Another horizontal line labeled 'L2RCOP' exits the box from the right and connects to the L2RCOP Entity. The top and bottom boundaries of the CORE box are represented by diagonal lines meeting at the center, forming a trapezoidal shape. + +CONTPT Character Oriented Non-Transparent Protocol. +CORE Character Oriented Relay Entity. +L2RCOP L2R Character Oriented Protocol. + +**Figure 1** + +Section 2 describes the L2R Character Oriented Protocol (L2RCOP) and section 3 the use of the L2RCOP. + +## A.2 The L2RCOP + +Information is transferred between L2Rs in fixed length n octet Protocol Data Units (PDUs). This corresponds to the fixed length of the RLP frame information field. The octets within the L2RCOP-PDU are numbered 0 to n-1; octet 0 is transmitted first. The value of n depends on the negotiated RLP version and frame type ( 3GPP TS 24.022[9]). The bits within the octets are numbered 1 to 8; bit 1 is transmitted first. + +The RLP version value 2 indicates RLP multi-link operation. The RLP version value 0 or 1 indicates RLP single-link operation. + +- Each octet contains a status octet, an information octet or fill. + +Octet 0 contains either a status octet or a user information octet. + +- Octet 0 shall always contain a status octet in case at least one status octet is transported in the L2RCOP PDU. In RLP-versions 0 and 1 a PDU always carries at least one status octet. In RLP version 2 a PDU carries status octet(s) only if actual status change(s) has taken place within the period represented by the PDU. Here the L2R status flag in the RLP version 2 header is set to 1 when status octet(s) is carried in the PDU. +- Status octets contain 3 status bits and 5 address bits. In cases where two status octets within the PDU are separated by more than 23 octets, the first status octet in octet m is followed by a pointer octet in octet m+1 forming a two-octet status field. The pointer octet contains one reserved bit and seven address bits indicating the number of characters between the status field and the second status octet. +- The 3 status bits correspond to SA, SB and X in ITU-T Recommendation V.110 [27]. The SA, SB and X bits use bit positions 8, 7 and 6 in the status octets. When a status bit changes the current state of all three bits shall be transmitted. +- Information octets are character octets or encoded character octets. +- Character octets are coded in the following way: + +- The first bit of the character received/transmitted corresponds to bit position 1 in the octet and the seventh bit corresponds to bit 7. For order of transmission of IA5 characters see ITU-T Recommendation V.4 [15]. +- 7 bit characters are padded with a 0 in bit position 8. Received parity (if used) is inserted in bit position 8, if parity is not used bit 8 is set to 0. +- Any start/stop bits are removed by the L2R. +- Encoded character octets are provided by the compression function. They are encoded according to ITU-T Recommendation V.42bis [26]. +- Information octets are inserted into L2RCOP-PDUs in order of transmission in octets 1 to n-1 for RLP single-link operation, in octets 1 to n-1 for RLP multi-link operation with status octet transportation, and in octets 0 to n-1 for multi-link operation with no status octet transportation. +- The address field in the status octets indicates the position of next status octet within the L2RCOP-PDU. This indicates the number of characters between status octets. Thus if two status octets are inserted into L2RCOP-PDU at offsets l and m the address value shall be defined by m-l-1. Address bit $2^0$ corresponds to bit 1 in the status octets. Address bit $2^1$ to bit 2 etc. +- Status octets are inserted in the character stream whenever a status change needs to be transmitted. +- Only address values 1 to n-2 ( $n-2 \leq 23$ ) in the address field of status octets are used for addressing purposes. The implication of not allowing address value 0 to be used for addressing is that two status octets cannot be sent after each other. The remaining codes are used to indicate: + - Last status change, remainder of L2RCOP-PDU empty. Address field value 31. + - Last status change, remainder of L2RCOP-PDU full of characters. Address field value 30. + - Destructive break signal, remainder of L2RCOP-PDU empty. Address field value 29. + - Destructive break acknowledge, remainder of L2RCOP-PDU empty. Address field value 28. + - L2RCOP-PDU contains at least two status octets which are separated by more than 23 characters; the address-field value in the first octet of the two-octet status field is 27 and the address bits in the pointer octet of the status field indicate the number of characters between the two-octet status field and the next status octet. + - Address field values from n-1 to 26 are reserved. In case of a PDU more than 25 octets in length, address field values from 24 to 26 are reserved. +- When it is necessary to insert a status octet into the character stream when no status change has occurred, e.g. to indicate that the remainder of a L2RCOP-PDU is empty or to indicate a break signal, the current status shall be repeated. +- In case when 64 data octets are carried by a 66-octet PDU, a status octet is carried in octet 0 and another status octet within the first 24 data octets. (The first status octet gives the address of the second status octet, which carries value 30 in its address field). + +Three examples of an L2RCOP PDU are shown in figure 2. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|----|----|---|---|---|---|---|---|-----------------------------------------| +| 0 | SA | SB | x | 0 | 0 | 0 | 1 | 1 | | +| 1 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | IA5 "G" (odd parity) | +| 2 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | IA5 "S" (odd parity) | +| 3 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | +| 4 | SA | SB | x | 1 | 1 | 1 | 1 | 1 | (last status change, rest of PDU empty) | +| . | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| n-1 | | | | | | | | | | + +Figure 2a: Single-link RLP and multi-link RLP with status octet transfer in PDU + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|---|---|---|---|---|---|---|---|----------------------| +| 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | IA5 "S" (odd parity) | +| 1 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | IA5 "G" (odd parity) | +| 2 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | IA5 "S" (odd parity) | +| 3 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | +| 4 | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| n-1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | + +Figure 2b: Multi-link RLP L2RCOP PDU with no status octet transfer + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----|----|----|---|---|---|---|---|---|----------------------| +| 0 | SA | SB | X | 0 | 0 | 0 | 1 | 1 | | +| 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | +| 2 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | IA5 "A" (odd parity) | +| 3 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | IA5 "R" (odd parity) | +| 4 | SA | SB | X | 1 | 1 | 0 | 1 | 1 | | +| 5 | R | 0 | 1 | 0 | 0 | 0 | 1 | 1 | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| 41 | SA | SB | X | 0 | 0 | 0 | 0 | 1 | | +| 42 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "K" (odd parity) | +| 43 | SA | SB | X | 1 | 1 | 1 | 1 | 0 | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| 65 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | IA5 "O" (odd parity) | + +Figure 2c: A 66-octet RLP L2RCOP PDU with status octets separated by more than 23 octets + +## --- A.3 Use of the L2RCOP + +The CORE relays status changes, break conditions and characters in both directions between the CONTP entity and the L2RCOP entity. + +The L2RCOP entity performs the following functions. + +### A.3.1 Radio Link Connection Control + +Given appropriate indications from the signalling mechanisms the L2RCOP entity uses the services of the radio link to establish and release the connection to its peer L2RCOP entity in the IWF. + +### A.3.2 Data Transfer + +The L2RCOP entity shall assemble and disassemble L2RCOP-PDUs. Data characters are assembled into L2RCOP-PDUs until either: + +- the PDU is full; +- the Radio Link service can accept another Radio Link service Data Unit. + +L2RCOP-PDUs are transferred to the peer L2RCOP entity using the data transfer services of the radio link. + +### A.3.3 Status Transfer + +The L2RCOP entity transfers interface status information between L2Rs using bits SA, SB and X in the status octets in L2RCOP-PDUs. Status changes are inserted in the L2RCOP-PDU in the position corresponding to the position in the character stream that the interface status change occurred. When the RLP is established or reset a L2RCOP-PDU with the current status values shall be sent. + +The general mapping between ITU-T V.24 [19] interface circuit numbers and status bits is described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. The specific mapping at the MT for the non-transparent bearer service is given in subclause 4.2.1. The mapping schemes used at the IWF are given in 3GPP TS 29.007 [13]. + +### A.3.4 Flow Control + +Flow control information is transferred between L2Rs in 2 ways, these are: + +- back pressure caused by L2R buffer conditions. +- use of the X-bit in status octets: + - flow control active, X-bit = ONE. + - flow control inactive, X-bit = ZERO. + +### A.3.5 Break + +The transfer of break conditions between L2Rs is via the status octets with appropriate coding of the address field. Where the "Break Signal" is generated it shall conform to the definition shown in ITU-T Recommendation X.28 [28]. + +#### A.3.5.1 Normal Realization + +The L2RCOP-PDU contains the mandatory status octet coded as the Destructive Break. + +Upon the receipt of the "Break Signal", the L2R shall destroy any existing data in front of the Break Signal in the same direction, and all the buffered data in the other direction. The L2R shall then pass the Break Signal immediately on. + +The termination of a break condition is indicated by sending an L2RCOP-PDU containing characters. + +#### A.3.5.2 Realization in case of Data Compression is used + +If the data compression function is used L2RCOP has to ensure the synchronization of the encoder and decoder according to ITU-T Recommendation V.42bis [26]. + +Upon receipt of a L2RCOP-PDU containing a status octet that signals a Destructive Break L2R destroys all data in the TX and RX buffer and re-initializes the compression function. Then L2R shall transmit an L2RCOP-PDU that contains the mandatory status octet coded as the Destructive Break Acknowledge. After that L2R shall restart the data transfer. + +Upon an receipt of the "Break Signal" by the CONTP, the L2R destroys any existing data in the TX and RX buffer and shall then pass the Break Signal immediately by using L2RCOP-PDU containing a status octet coded as the Destructive Break. L2R shall wait for a L2RCOP-PDU containing a mandatory status octet coded as Destructive Break Acknowledge. Following data received by the CONTP shall be stored in the TX buffer. Data received in L2RCOP-PDUs shall be discarded. After reception of the L2RCOP-PDU containing a mandatory status octet coded as Destructive Break Acknowledge L2R shall re-initialize the data compression function and restart the data transfer. + +# Annex B (informative): Use of a 9 pin connector as an MT2 type interface + +For asynchronous data communications many of the physical pins on a standard 25 pin D-type connector (ISO 2110 [31]) are not used. As a result many communication devices have only a 9 pin connector to allow them to be made smaller. This interface is a MT2 type providing the correct ITU-T Recommendation V.24 [19] signals are supported. + +Table B1 gives the pin assignments for a 9 pin connector. Two variants are permitted: + +## 1. Outband flow control + +When outband (CT 133) flow control is required, pin number 7 carries CT 133 (Ready for Receiving). In this case CT 105 is not mapped to any physical pin. On the MT2 side of the interface, CT 105 is treated as being always in the ON condition. + +## 2. No outband flow control + +When no outband (CT 133) flow control is required, pin number 7 may carry CT 105 (Request to Send). In this case CT 133 is not mapped to any physical pin. On the MT2 side of the interface, CT 133 is treated as being always in the ON condition. + +**Table B1: Interchange circuit mappings** + +| ITU-T V.24 [19] Circuit Number | Circuit Name | Pin Number | +|-------------------------------------------------------------|---------------|------------| +| CT 102 | Common ground | 5 | +| CT 103 | TxD | 3 | +| CT 104 | RxD | 2 | +| CT 105 | RTS | 7 (note) | +| CT 106 | RFS (CTS) | 8 | +| CT 107 | DSR | 6 | +| CT 108/2 | DTR | 4 | +| CT 109 | DCD | 1 | +| CT 125 | CI | 9 | +| CT 133 | RFR | 7 (note) | +| NOTE: Only one of these mappings may exist at any one time. | | | + +# Annex C (informative): General mapping of ITU-T V.24 [19] circuits to channel status bits + +In the data transfer state, status bits SA, SB and X can be used to convey channel control information associated with the data bits. Table C1 shows the general mapping scheme between the ITU-T V.24 [19] circuit numbers and the status bits. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. The specific mappings for the various PLMN bearer types are given elsewhere in the present document. + +**Table C1: General mapping scheme at the MT** + +| Signal at TE2/MT interface | Status bit direction: MT to IWF | Status bit direction: IWF to MT | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------| +| CT 105 (note 3) | SB | | +| CT 106 (note 1) | | X | +| CT 107 | | SA | +| CT 108/2 | SA | | +| CT 109 | | SB | +| CT 133 (note 3) | X (note 2) | | +| NOTE 1: The condition of CT 106 may also be affected by the state of any transmit buffer in the MT. | | | +| NOTE 2: The condition of Status bit X towards the IWF may also be affected by the state of any receive buffer in the MT. | | | +| NOTE 3: CT105 and CT133 are assigned to the same connector pin on both the standard 25 pin connector (ISO 2110) and the commonly used 9 pin connector (annex B). When this pin is used for CT133 then on the MT side of the interface CT 105 is treated as being always in the ON condition. SB towards the IWF shall therefore also always be ON. Similarly, when this pin is being used for CT105 then on the MT side of the interface CT 133 is treated as being always in the ON condition. X towards the IWF shall therefore also always be ON. As circuit 133 is used only in duplex operation and circuit 105 is used only in half duplex operation (which is not supported by GSM or UMTS) there should be no conflict. | | | + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|--------------------------------------------------------------------------------|-----------------------------------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | Apr 1999 | | | | Transferred to 3GPP CN1 | 7.0.0 | | +| | CN#03 | | | | Approved at CN#03 | | 3.0.0 | +| | CN#04 | | 001 | | Introduction of EDGE channel codings into the specifications [E-mail approval] | 3.0.0 | 3.1.0 | +| | CN#06 | | 002 | | Service clean-up for Release 99 | 3.1.0 | 3.2.0 | +| | CN#07 | | 003 | | UMTS Clean Up | 3.2.0 | 3.3.0 | +| | CN#08 | | 004 | | Adaptations for UMTS | 3.3.0 | 3.4.0 | +| | CN#09 | | 007 | | Modification from V.25bis to V.250 | 3.4.0 | 4.0.0 | +| 12-2001 | CN#14 | NP-010604 | 008 | 3 | Terminology Clarifications requested by TSG GERAN | 4.0.0 | 5.0.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.0.0 | 6.0.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.0.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 12-2010 | CT#50 | CP-100779 | 010 | 1 | Correcting non-specific external references | 9.0.0 | 9.1.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.1.0 | 9.1.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | +| 10-2014 | | | | | Automatic upgrade from previous Release | 11.0.0 | 12.0.0 | +| 12-2015 | | | | | Automatic upgrade from previous Release | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | CT#80 | | | | | Automatic upgrade from previous Release | 15.0.0 | +| 2020-06 | CT#88e | | | | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/27_series/27003/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-16/27_series/27003/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8935b9f684c064536ded7869864e7aea7ae6e393 --- /dev/null +++ b/marked/Rel-16/27_series/27003/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76f9f1094e2908cbf8f43242af2a1ebfa598f7d3a51748164b928018984b7685 +size 15400 diff --git a/marked/Rel-16/27_series/27003/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Rel-16/27_series/27003/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32c88df7658e237ad25fa7eedf847f4a5b863170 --- /dev/null +++ b/marked/Rel-16/27_series/27003/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9e8777fcec80ff4f02d9b481ba7e3828780194ca80d26efb6294e786d418aa9 +size 26819 diff --git a/marked/Rel-16/27_series/27003/raw.md b/marked/Rel-16/27_series/27003/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bfde88058c5181586dbdb772c0a9381033dd1efb --- /dev/null +++ b/marked/Rel-16/27_series/27003/raw.md @@ -0,0 +1,500 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 2.1 Abbreviations ..... | 7 | +| 2.2 Definitions..... | 7 | +| 3 General..... | 7 | +| 3.1 Customer access configuration..... | 7 | +| 3.2 Terminal Adaptation Function ..... | 8 | +| 3.3 TAF Interfacing to other MT functions..... | 8 | +| 4 Terminal Adaptation Functions for synchronous transparent services..... | 8 | +| 4.1 Rate Adaptation in A/Gb mode..... | 9 | +| 4.1.1 Rate adaptation - ITU-T V-series ..... | 9 | +| 4.1.2 Rate adaptation - ITU-T X.21 ..... | 9 | +| 4.1.3 Rate adaptation - ITU-T S-interface..... | 9 | +| 4.2 Interchange Circuit Signalling Mapping ..... | 9 | +| 4.2.1 ITU-T V-series interchange circuit mapping..... | 9 | +| 4.2.1.1 Multislot configurations (Channel coding TCH/F9.6 or TCH/F4.8 kbit/s)..... | 11 | +| 4.2.1.2 Channel coding TCH/F14.4 and TCH/F28.8 ..... | 12 | +| 4.2.2 ITU-T X.21 [23] Interchange circuit mapping ..... | 12 | +| 4.2.3 Case of ITU-T S-interface ..... | 12 | +| 4.3 Call establishment signalling mapping at TE/MT interface..... | 12 | +| 4.3.1 ITU-T V-series interfaces..... | 12 | +| 4.3.1.1 Call establishment manual operation - utilizing Alternate Speech/Data or Speech followed by Data Capabilities..... | 12 | +| 4.3.1.2 Call establishment manual operation - utilizing the Unrestricted Digital Capability ..... | 12 | +| 4.3.1.3 ITU-T V.25bis [18] auto call/auto answer..... | 12 | +| 4.3.2 ITU-T X-series interfaces..... | 13 | +| 4.3.3 ITU-T S-interface (ITU-T I.420 [11]) signalling mapping ..... | 13 | +| 4.3.4 X.25 Procedures Mapping..... | 13 | +| 5 Terminal Adaptation Functions for synchronous non-transparent services..... | 13 | +| 6 V-series interface procedures to 3GPP TS 24.008 [7] mapping ..... | 14 | +| 6.1 Mobile Originated calls..... | 14 | +| 6.2 Mobile Terminated calls..... | 14 | +| 7 ITU-T X.21 [23] interface procedures to 3GPP TS 24.008 [7] mapping ..... | 15 | +| 8 Support for packet service..... | 15 | +| Annex A (normative): L2R Functionality ..... | 16 | +| Annex B (informative): Change history..... | 17 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines the interfaces and Terminal Adaptation Functions (TAF) integral to a Mobile Termination (MT) which enables the attachment of synchronous terminals to a MT within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines Terminal Adaptation Functions (TAF) which are integrated in a Mobile Termination (MT) and which enable the use of synchronous bearer services in the PLMN and the attachment of Synchronous terminals to an MT (see 3GPP TS 24.002 [3]). For the case where asynchronous terminals are attached to the TAF when using synchronous bearer services in the PLMN, the reader is referred to 3GPP TS 27.002 [36] for the asynchronous MT-TAF interface specifics and to the present document for synchronous bearer service specifics on the TAF-IWF interface. The general aspects of Terminal Adaptation Functions are contained in specification 3GPP TS 27.001 [9]. The present document covers support of synchronous data services (see 3GPP TS 22.002 [6]) for the following interfaces and procedures: + +- V.22 [15] DTE/DCE Interface; +- V.22 bis [16] DTE/DCE Interface; +- V.26 ter [19] DTE/DCE Interface; +- X.21 bis [24] DTE/DCE Interface; +- X.32 [30] Procedure; +- V.25 bis [18] Procedure; + +NOTE: From R99 onwards the support of the following services are no longer required by a PLMN: + +- the dual Bearer Services "alternate speech/data" and "speech followed by data"; +- the dedicated services for PAD and Packet access; +- BS 21 ... 26 and BS 31 ... 34. + +From REL-4 onwards the support of the following service is no longer required by a PLMN: + +- the synchronous Bearer Service non-transparent (BS 30 NT). +- the Teleservice Facsimile non-transparent (TS 61/62 NT) for A/Gb mode. + +The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to GSM R98 or R99 respectively. + +NOTE: Please note that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. GERAN Iu mode is for further study. + +# --- 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 43.010: "GSM Public Land Mobile Network (PLMN) connection types". +- [3] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration " + +- [4] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [5] 3GPP TS 08.20: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [6] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by Public Land Mobile Network (PLMN)". +- [7] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3". +- [8] Void. +- [9] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [10] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications ". +- [11] ITU-T Recommendation I.420 (1998): "Basic user-network interface". +- [12] Void. +- [13] Void. +- [14] Void. +- [15] ITU-T Recommendation V.22 (1988): "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [16] ITU-T Recommendation V.22 bis (1988): "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [17] ITU-T Recommendation V.24 (1996):"List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [18] ITU-T Recommendation V.25 bis (1996): "Synchronous and asynchronous automatic dialling procedures on switched networks". +- [19] ITU-T Recommendation V.26 ter (1988): "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [20] ITU-T Recommendation V.28 (1993): "Electrical characteristics for unbalanced double-current interchange circuits". +- [21] Void. +- [22] ITU-T Recommendation V.110 (1996): "Support of data terminal equipments with V-Series interfaces by an integrated services digital network". +- [23] Void. +- [24] Void. +- [25] Void. +- [26] Void. +- [27] Void. +- [28] Void. +- [29] Void. + +- [30] ITU-T Recommendation X.32 (1996): "Interface between Data terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in packet mode and accessing a Packet-Switched Public Data Network through a public switched telephone network or an Integrated Services Digital Network or a Circuit-Switched Public Data Network". +- [31] Void. +- [32] Void. +- [33] Personal Computer Memory Card Association: "PCMCIA 2.1 or PC-Card 3.0 electrical specification or later revisions". +- [34] Infrared Data Association IrDA: "IrPHY Physical layer signalling standard". +- [35] Void. +- [36] 3GPP TS 27.002: "Terminal adaptation functions (TAF) for services using asynchronous bearer capabilities". + +## 2.1 Abbreviations + +In addition to the abbreviations listed below, the present document also uses terms listed in 3GPP TR 21.905 [10]. + +| | | +|-------|----------------------------------------------| +| IrDA | Infrared Data Association | +| IrPHY | Infrared Physical layer | +| ITU-T | ITU-Telecommunication Standardization Sector | +| MUX | Multiplexer | + +## 2.2 Definitions + +The term 'mobile station' (MS) in the present document is synonymous with the term 'user equipment' (UE) as defined in 3GPP TR 21.905[10]. + +The term 'TE2' in the present document is synonymous with the term 'TE' as defined in 3GPP TR 21.905[10]. + +The term 'MT2' in the present document is synonymous with the term 'MT' as defined in 3GPP TR 21.905[10]. + +For the purposes of the present document the following internal definitions apply in addition to those given in 3GPP TS 21.905[10]. + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +# --- 3 General + +## 3.1 Customer access configuration + +The PLMN access reference configuration is described in figure 1 of 3GPP TS 24.002 [3] and 3GPP TS 27.001 [9]. The present document specifically refers to the MTs which support terminal equipments (TE1 or TE2) that use synchronous bearer capabilities. + +## 3.2 Terminal Adaptation Function + +The TAF is functionally part of an MT0, MT1 or MT2 (see 3GPP TS 24.002 [3]). The terminal adaptation provides facilities to allow manual or automatic call control functions associated with circuit switched data services, in case of ITU-T V series interfaces. The following functions are included: + +- conversion of electrical, mechanical, functional and procedural characteristics of the ITU-T V-series, type interfaces to those required by a PLMN; +- bit rate adaptation of ITU-T V-series and ITU-T X-series data signalling rates and the ISDN 64 kbit/s to that provided in an A/Gb mode PLMN; +- the mapping of ITU-T V.25 bis [18] AUTO CALL/AUTO ANSWER procedures to the PLMN Layer 3 signalling; +- the mapping functions necessary to convert ITU-T S-interface signalling to PLMN Layer 3 signalling; +- synchronization procedure, which means the task of synchronizing the entry to and the exit from the data transfer phase between two subscriber terminals. This is described in the specification 3GPP TS 27.001 [9]; +- filtering of channel control information. This is described in the specification 3GPP TS 27.001 [9]; +- compatibility checking (see 3GPP TS 27.001 [9]); +- flow control; +- in Call Modification function (see clause 4); +- splitting and combining of the data flow in case of multi substream data configurations. + +## 3.3 TAF Interfacing to other MT functions + +TAF interfacing is shown in figure 1. + +![Diagram showing TAF interfacing to other MT functions. The central TAF block is connected to Mobility Management, RR Management, and Channel Codec (with FEC) on the right, and to MMI and Call Control on the bottom.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +``` +graph TD; TAF[TAF] --- MM[Mobility Management]; TAF --- RR[RR Management]; TAF --- CC[Channel Codec]; CC --- FEC[FEC]; TAF --- MMI[MMI]; TAF --- CallControl[Call Control]; +``` + +Diagram showing TAF interfacing to other MT functions. The central TAF block is connected to Mobility Management, RR Management, and Channel Codec (with FEC) on the right, and to MMI and Call Control on the bottom. + +Figure 1: TAF interfacing to other MT functions + +# 4 Terminal Adaptation Functions for synchronous transparent services + +Specification 3GPP TS 43.010 [2] refers to the models for connection types supporting synchronous transparent services. + +## 4.1 Rate Adaptation in A/Gb mode + +Rate adaptation on the MS-BS interface is described in 3GPP TS 44.021[4]. The synchronous data services make use of the following rate adaptation functions: RA1, RA2, RA1/RA1', RA1' and in case of TCH/F28.8 usage, EDGE-MUX. See also figures 6, 7 and 8 in 3GPP TS 43.010 [2]. The D-bits of the rate adaptation frames are used to convey user data. The S- and X-bits are used to convey channel status information associated with the data bits in the data transfer + +state, or to carry substream numbering between the Split/Combine functions in case of mult substream operation. For the S- and X-bits, a ZERO corresponds to the ON condition, a ONE to the OFF condition. + +### 4.1.1 Rate adaptation - ITU-T V-series + +This is provided as indicated in specification 3GPP TS 44.021 [4]. The functions applied in this case are shown in figure 2 (see model 2b in figures 6, 7 and 8 of 3GPP TS 43.010 [2]). + +![Diagram showing the connection between TE2 V-series and MT2. A line connects the two, labeled 'Interface circuits (data and control)' above and 'R' below. Inside the MT2 box is a smaller box labeled 'RA1\''.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +``` + ++-------------+ +-----------------+ +| TE2 | Interface circuits | MT2 | +| V-series |-------------------------------| +-------+ | +| | (data and control) | | RA1' | | ++-------------+ | | +-------+ | + R +-----------------+ + +``` + +Diagram showing the connection between TE2 V-series and MT2. A line connects the two, labeled 'Interface circuits (data and control)' above and 'R' below. Inside the MT2 box is a smaller box labeled 'RA1\''. + +**Figure 2: Rate adaptation for V-series terminals** + +### 4.1.2 Rate adaptation - ITU-T X.21 + +Void. + +### 4.1.3 Rate adaptation - ITU-T S-interface + +Void. + +## 4.2 Interchange Circuit Signalling Mapping + +### 4.2.1 ITU-T V-series interchange circuit mapping + +The interchange circuit signalling mapping at the interface between the TE2 and the MT shall conform to ITU-T recommendation V.24 [17]. The signal levels at the interface shall conform either to ITU-T recommendation V.28 [20], or to IrDA IrPHY Physical signalling standard specification [34], or to PCMCIA 2.1 [33], or to PC-Card 3.0 [33] electrical specifications or to later revisions. + +The signals required at this interface are shown in table 2. + +- Specification 3GPP TS 44.021 [4] refers to the frame structure and identifies the use of status bits for the carriage of signalling information. + +Status bits SA, SB and X are used to convey channel control information associated with the data bits in the data transfer state. Table 1 shows the mapping scheme between the ITU-T V.24 [17] circuit numbers and the status bits for the transparent mode. It also shows how the unused status bits should be handled. It is derived from the general mapping scheme described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of these status bits by the various channel codings is described in subsequent sections. + +**Table 1: Mapping scheme at the MT for the transparent mode** + +| Signal at TE2/MT interface or condition within the MT | Mapping direction: MT to IWF | Mapping direction: IWF to MT | +|-------------------------------------------------------|------------------------------|------------------------------| +| CT 105 | not mapped (note 1) | | +| CT 106 | | from status bit X (note 7) | +| CT 107 | | not mapped (note 5) | +| CT 108/2 | not mapped (note 6) | | +| CT 109 | | from status bit SB (note 7) | +| CT 133 | not mapped (note 2) | | +| always ON | to status bit SA (note 3) | | +| always ON | to status bit SB (note 1) | | +| always ON | to status bit X (note 4) | | +| ignored by MT | | from status bit SA (note 3) | + +NOTE 1: The SB bit towards the IWF, according to the General Mapping (3GPP TS 27.002, annex C), could be used to carry CT 105. However, CT 105 should always be ON in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. No interchange circuit shall be mapped to the SB bit which shall always be set to ON in the data transfer state. + +NOTE 2: CT 133 is not mapped since there is no flow control in transparent mode. + +NOTE 3: The SA bits in both directions are available only with certain channel codings. Therefore, for maximum compatibility, they should not be mapped. + +NOTE 4: The X bit towards the IWF is not mapped and shall always be set to ON in the data transfer state since there is no flow control in transparent mode. + +NOTE 5: CT 107 is controlled by the channel synchronization process (3GPP TS 27.001 [9]). + +NOTE 6: CT 108/2 may be used in the call setup and answering processes. + +NOTE 7: The status bits are filtered before being mapped to the ITU-T V.24 [17] circuits (3GPP TS 27.001 [9]). + +**Table 2: Minimum set of V-series interchange circuits** + +| Circuit Number | Circuit Name | Ground | Data | | Control | | +|----------------|--------------------------------------------|--------|--------|----------|---------|----------| +| | | | to TE2 | from TE2 | to TE2 | from TE2 | +| CT102 | Common Return | X | | | | | +| CT103 | Transmitted data | | | X | | | +| CT104 | Received data | | X | | | | +| CT105 | Request to send | | | | | X | +| CT106 | Ready for sending | | | | X | | +| CT107 | Data set ready | | | | X | | +| CT108.2 | Data terminal ready | | | | | X | +| CT109 | Data channel received line signal detector | | | | X | | +| CT114 | Transmitter signal element timing | | | | X | | +| CT115 | Receiver signal element timing | | | | X | | +| CT125 | Calling indicator (note) | | | | X | | + +NOTE: CT125 is used with the AUTO ANSWER function of the TAF. + +#### **Use of Network Independent Clocking (applicable to A/Gb mode PLMN only):** + +Network Independent Clocking is only applicable to calls using ITC value "3.1 kHz audio ex PLMN". + +Within the **A/Gb mode PLMN** the coding of the values for bits associated with NIC is specified in 3GPP TS 44.021 [4] and 3GPP TS 08.20 [5]. In the forward (transmitting) direction the multiframes shall be coded in exact accordance with that specified in those specifications. Bit E6 is set to "1" in alternate modified ITU-T V.110 [22] frames at the transmitter. However, the use of this bit at the receiver for monitoring frame Synchronization, or any other purpose, is not specified and is left to the discretion of the implementor. + +A "perfect linear block Code" is used in C1-C5, whose error correction properties may be utilized in the receiver, in order to ensure reliable operation of NIC. + +The NIC sending function has to recognize when the difference between the applicable clock speed of the **A/Gb mode PLMN** and the interface speed generates a positive or negative whole bit requirement. When this positive or negative condition occurs, the NIC codewords specified in specification 3GPP TS 44.021 [4] are used to transport this condition to the receiving NIC function. Transmission of the codeword shall clear the positive or negative condition related to that codeword at the sending function. The sending function shall not send more than one positive or negative compensation within a contiguous period of time corresponding to 10 000 user data bits minus the number of user data bits necessary to make up an even number of ITU-T V.110 [22] frames. Between compensations (NIC compensation is coded in two ITU-T V.110 [22] frames). This results from the requirements to compensate for maximum clock differences of $\pm 100$ parts per million. If the receiving function receives NIC compensations more often than a contiguous period of time corresponding to 10 000 user data bits, there is no guarantee that data will not be lost. + +The NIC receiving function has to provide the capability to support the compensation requirements of the sending function. This compensation is managed by manipulating the clock speed of the interface, within the standard constraints of that interface. + +Overall, the compensation functions have to be capable of managing clock tolerances of $\pm 100$ parts per million. + +The NIC function has to recognize and manage the conversion of the NIC information received incoming from an ISDN terminal Interface. The conversion has to be made to the NIC format used within the **A/Gb mode PLMN** System as defined in specifications 3GPP TS 44.021 [4] and 3GPP TS 08.20 [5]). The NIC function has to manage the conversion of the PLMN NIC format into that used within the ISDN in the traffic direction towards the ISDN terminal interface. + +Due to the incompatibility between the ISDN and the **A/Gb mode PLMN** requirements NIC interworking is nor provided between these two formats. as such no NIC function is required in providing interworking to the ISDN for unrestricted digital. + +#### **Action on loss of synchronization:** + +If five consecutive NIC multiframes have incorrect framing bit values in E7, the receiver shall stop applying clocking compensation to the received data. Resynchronization shall be attempted and compensation shall resume when synchronization is achieved. + +#### **Signal element timing:** + +Receiver signal element timing (CT115) is generated by MT2. In the **A/Gb mode PLMN** transparent case, this shall be synchronized to the output of RA1' function. In the UTRAN Iu mode transparent case, this shall be synchronized to output of the RLC. A transition from ON to OFF condition shall nominally indicate the centre of each signal element on CT104. + +Transmitter signal element timing is generated by MT2 (CT114), this may be synchronized to CT115. + +In the case of alternate Speech/Group 3 Facsimile, there may be a Channel Mode Modify during the course of the facsimile portion of the call. If this occurs, the user data rate changes and this is reflected to the ITU-T V.24 [17] interface as a change in the clock speed on CT 114 and CT 115. + +#### 4.2.1.1 Multislot configurations (Channel coding TCH/F9.6 or TCH/F4.8 kbit/s) + +In transparent multislot configurations status bits S1, S3 and the X-bit between the D12 and D13 in the ITU-T V.110 [22] 80-bit intermediate rate frame - are used for transferring substream numbering information. The S4-bit is used for frame synchronization between the parallel substreams (ref 3GPP TS 44.021[4]). + +#### 4.2.1.2 Channel coding TCH/F14.4 and TCH/F28.8 + +For information on the mapping of the interchange circuit signalling bits in the 14,5 multiframe structure, refer to 3GPP TS 44.021 [4]. + +### 4.2.2 ITU-T X.21 [23] Interchange circuit mapping + +Void. + +### 4.2.3 Case of ITU-T S-interface + +Void. + +## 4.3 Call establishment signalling mapping at TE/MT interface + +### 4.3.1 ITU-T V-series interfaces + +#### 4.3.1.1 Call establishment manual operation - utilizing Alternate Speech/Data or Speech followed by Data Capabilities + +Void. + +#### 4.3.1.2 Call establishment manual operation - utilizing the Unrestricted Digital Capability + +In this case the user shall not hear network supervisory tones or answer tone. The data transfer phase shall be entered automatically. + +#### 4.3.1.3 ITU-T V.25bis [18] auto call/auto answer + +The mapping of the ITU-T V.25bis [18] procedures to the messages of the PLMN Layer 3 signalling (3GPP TS 24.008 [7]) is defined in clause 4. + +##### **Auto Call:** + +This procedure is provided according to ITU-T V.25bis [18] using only circuit 108/2. A subset of ITU-T V.25bis [18] is shown in table 4. This subset gives minimum level of control and indication. + +During the call establishment phase, i.e. after signalling, call tone according to ITU-T V.25 bis [18] shall be generated in the IWF, where appropriate. + +##### **Auto Answer:** + +This procedure is provided according to ITU-T V.25bis [18]. + +**Table 4: Minimum set of ITU-T V.25bis [18] Call Set-up Commands and Indications** + +| | Description | IA5Characters | +|-----------------------|-----------------------------------------------------------------------|---------------| +| Commands
from TE2 | Call Request with Number
provided 0,1..9,*,#,A,B,C,D | CRN | +| | Disregard Incoming Call | DIC | +| | Connect Incoming Call | CIC | +| Indications
to TE2 | Call Failure Indication
XX = CB,AB,NT,FC (Note) | CFI XX | +| | INcoming Call | INC | +| | VALid | VAL | +| | INVAlid | INV | + +NOTE to table 4: CB = Local MT busy +AB = Abort call +NT = No answer +FC = Forbidden call (\*) + +(\*) Forbidden call indication results from contravention of rules for repeat call attempts as defined by the appropriate national approval administration. It is recommended that this is the responsibility of the MT, not the TE2. + +### 4.3.2 ITU-T X-series interfaces + +Void. + +### 4.3.3 ITU-T S-interface (ITU-T I.420 [11]) signalling mapping + +Void. + +### 4.3.4 X.25 Procedures Mapping + +Void. + +# --- 5 Terminal Adaptation Functions for synchronous non-transparent services. + +Void. + +# 6 V-series interface procedures to 3GPP TS 24.008 [7] mapping + +Interface procedures not directly mappable to 3GPP TS 24.008 [7] (ie. ITU-T V.25 bis [18] VAL/INV) are not considered. Mobile management procedures of 3GPP TS 24.008 [7] are not considered applicable. + +Mapping of other call establishment or clearing messages to the S interface e.g. "Call proceeding", etc. have not been included. It is assumed that these may be mapped directly and thus are of no relevance to the ITU-T V.25 bis [18] or manual interface. + +## 6.1 Mobile Originated calls + +a) SET-UP. + +| Element | Derived from | | +|----------------|--------------------------------------------------------|-----------------------------| +| | MMI | ITU-T V.25 bis [18] message | +| Called Address | Keypad | CRN/CRI/CRS | +| Called | Keypad | CRI | +| Sub Address | | | +| HLC | Derived from internal settings or MMI information. | | +| LLC | Same as HLC | | +| BC | Same as HSC
3GPP TS 27.001 [9] gives allowed values | | + +b) RELEASE COMPLETE. + +| Element | Derived from | | +|---------|--------------------|-----------------------------| +| | MMI | ITU-T V.25 bis [18] message | +| Cause | Display (optional) | CFI | + +## 6.2 Mobile Terminated calls + +Call establishment is initiated by receipt of Setup at the MS: + +a) SET-UP. + +| Element | Mapped on to | | +|----------------|--------------------|-----------------------------| +| | MMI | ITU-T V.25 bis [18] message | +| Called Address | Display (optional) | INC | +| Called | Display (optional) | Not applicable | +| Sub Address | | | +| HLC | Display (optional) | Not applicable | +| LLC | Display (optional) | Not applicable | +| BC | Display (optional) | Not applicable | + +b) CALL CONFIRM. + +Information for the BC element in the call confirm is derived from e.g. MMI or by internal settings. + +c) CONNECT. + +Connect is sent in response, CIC from ITU-T V.25 bis [18] or in response from MMI. + +# 7 ITU-T X.21 [23] interface procedures to 3GPP TS 24.008 [7] mapping + +Void. + +# --- 8 Support for packet service + +Void. + +# --- Annex A (normative): L2R Functionality + +Void + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|--------------------------------------------------------------------------|-----------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 04-1999 | | | | | Transferred to 3GPP CN1 | 6.0.0 | | +| | CN#03 | | | | Approved at CN#03 | | 3.0.0 | +| | CN#04 | | 001 | | Introduction of EDGE | 3.0.0 | 3.1.0 | +| | CN#06 | | 002 | | Introduction of Asynchronous interface for Real-time non-transparent FAX | 3.1.0 | 3.2.0 | +| | CN#06 | | 003 | | R99 service clean-up (also subclause 8.3 removed) | 3.1.0 | 3.2.0 | +| | CN#07 | | 004 | | UMTS clean up | 3.2.0 | 3.3.0 | +| | CN#08 | | 005 | | Adaptations for UMTS | 3.3.0 | 3.4.0 | +| | CN#09 | | 006 | | Modification from V.25bis to V.250 | 3.4.0 | 3.5.0 | +| | CN#10 | | 007 | | Removal of BS 30 NT | 3.5.0 | 4.0.0 | +| 03-2001 | TSG#11 | NP-010046 | 008 | | Removal of Fax NT in GSM from Rel-4 | 4.0.0 | 4.1.0 | +| 12-2001 | TSG#14 | NP-010604 | 009 | | Terminology clarifications as requested by TSG GERAN | 4.1.0 | 5.0.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.0.0 | 6.0.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.0.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.0.0 | 9.0.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | +| 10-2014 | | | | | Automatic upgrade from previous Release | 11.0.0 | 12.0.0 | +| 12-2015 | | | | | Automatic upgrade from previous Release | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | CT#80 | | | | | Automatic upgrade from previous Release | 15.0.0 | +| 2020-06 | CT#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/27_series/27005/34f788b0e5bc8af774fa5561c22e6d01_img.jpg b/marked/Rel-16/27_series/27005/34f788b0e5bc8af774fa5561c22e6d01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa12a3fdfcfb4a68fce485363ca4b6d7af703f7d --- /dev/null +++ b/marked/Rel-16/27_series/27005/34f788b0e5bc8af774fa5561c22e6d01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:263a79b648175ec22c105f9718f0bc3bbeeba88628eeafb58a5c8e69931ac997 +size 28713 diff --git a/marked/Rel-16/27_series/27005/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-16/27_series/27005/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e6e9fded3898cb5e583b2cb8e9e89dc6c162dc8 --- /dev/null +++ b/marked/Rel-16/27_series/27005/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fabce19dad6962601d5d99bd9c16eb30198b23a8128319b9f106490174f44e5 +size 137409 diff --git a/marked/Rel-16/27_series/27005/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/27_series/27005/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d373f53f95ae7322d0e721a8a8f5f5bb083db900 --- /dev/null +++ b/marked/Rel-16/27_series/27005/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93964ae4fa79430c171ef8e8dd5e595a7d612e1649158c0fddc26754b35611a2 +size 54521 diff --git a/marked/Rel-16/27_series/27005/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg b/marked/Rel-16/27_series/27005/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bd486711e618f37b5616725c23dbeedfeb69621 --- /dev/null +++ b/marked/Rel-16/27_series/27005/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f67b5b8d13a845224f955bbb914693f9d1d5d6bd0fad5eae958849bd3364260 +size 51146 diff --git a/marked/Rel-16/27_series/27005/536951b2bbd94325ae266d8d1363df8f_img.jpg b/marked/Rel-16/27_series/27005/536951b2bbd94325ae266d8d1363df8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1d67745b2bcc1946a3e35dac97b27a862737f8a --- /dev/null +++ b/marked/Rel-16/27_series/27005/536951b2bbd94325ae266d8d1363df8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48af61929bf7f2b34c48b427eac07edb7d582833742b1acc2b3f83763fe2c78c +size 17092 diff --git a/marked/Rel-16/27_series/27005/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/27_series/27005/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..460ecf9308967d2fa7b635ff417288c73a33c255 --- /dev/null +++ b/marked/Rel-16/27_series/27005/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2677f7be014a751372a0211b68352163170e807bd740a8043e61d63f97b3f6e8 +size 104832 diff --git a/marked/Rel-16/27_series/27005/583e14835ddabad1d8b92a07b82fc31b_img.jpg b/marked/Rel-16/27_series/27005/583e14835ddabad1d8b92a07b82fc31b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55686aa33a49fbaf67d3a8874a32cc0b4ab9b920 --- /dev/null +++ b/marked/Rel-16/27_series/27005/583e14835ddabad1d8b92a07b82fc31b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4901014fcf68b3b8c37f44c5fc999a01904c595d51a8998b838d89dc86160373 +size 60845 diff --git a/marked/Rel-16/27_series/27005/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-16/27_series/27005/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2194f31c5682a1ab2f7390d41864956b56918b9c --- /dev/null +++ b/marked/Rel-16/27_series/27005/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b9d5cf1aabc77a7c18f68c40cfb6430b49ec29e7f5ed6496da0126c94d3dbda +size 6573 diff --git a/marked/Rel-16/27_series/27005/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/27_series/27005/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..460ecf9308967d2fa7b635ff417288c73a33c255 --- /dev/null +++ b/marked/Rel-16/27_series/27005/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2677f7be014a751372a0211b68352163170e807bd740a8043e61d63f97b3f6e8 +size 104832 diff --git a/marked/Rel-16/27_series/27005/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-16/27_series/27005/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd526e1e8e1d87573e0aea40cc712cc64cfc21d4 --- /dev/null +++ b/marked/Rel-16/27_series/27005/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b5fca6055f92e9dab7776cd31b285f7c0336a1094c505af042deea5364ff146 +size 26888 diff --git a/marked/Rel-16/27_series/27005/6a555cff11e140861ce08db72b01a6a2_img.jpg b/marked/Rel-16/27_series/27005/6a555cff11e140861ce08db72b01a6a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b37231c9515cb1b8c3019fe53f5ffd566260d11 --- /dev/null +++ b/marked/Rel-16/27_series/27005/6a555cff11e140861ce08db72b01a6a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b0dbd9d7e60cc7c7d4c468f90878cec25a567b3748f7f980f6462b1104b8f54 +size 17322 diff --git a/marked/Rel-16/27_series/27005/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-16/27_series/27005/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8be7bebcd10373e43fc50678917036e0acb71de --- /dev/null +++ b/marked/Rel-16/27_series/27005/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46b95a4675accf931929a7f9c96d98056b72daa75dda92cb786f730419e9dc95 +size 138007 diff --git a/marked/Rel-16/27_series/27005/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-16/27_series/27005/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61ecf614b4d528476d11be969146e99011a2b183 --- /dev/null +++ b/marked/Rel-16/27_series/27005/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c97decbb6a5c44ae8b889b155a8367f345b29fa83817e2a5a83fa85e1c442c30 +size 19767 diff --git a/marked/Rel-16/27_series/27005/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-16/27_series/27005/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd526e1e8e1d87573e0aea40cc712cc64cfc21d4 --- /dev/null +++ b/marked/Rel-16/27_series/27005/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b5fca6055f92e9dab7776cd31b285f7c0336a1094c505af042deea5364ff146 +size 26888 diff --git a/marked/Rel-16/27_series/27005/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/marked/Rel-16/27_series/27005/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcc89922d2264a1bc69628becbcaf69ebb1b07e7 --- /dev/null +++ b/marked/Rel-16/27_series/27005/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b5e519c805e5c4f6bdac11399aea9b9257445808ffbfc7efc446222f519dbce +size 76751 diff --git a/marked/Rel-16/27_series/27005/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Rel-16/27_series/27005/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..168e470ed5dbabc3ac304720b4df3f72ec765978 --- /dev/null +++ b/marked/Rel-16/27_series/27005/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc2656a9c804c6889ae2bdad493a17d1c185c15bd1ab30b118178f6345d21016 +size 51145 diff --git a/marked/Rel-16/27_series/27005/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-16/27_series/27005/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46e2c59810774a9f4589f9856bf58cf3bf2a6a12 --- /dev/null +++ b/marked/Rel-16/27_series/27005/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c5e76bf6ebee491146d15e6ce83554059068e2d3be0735ea1d41e391fd2bc24 +size 32444 diff --git a/marked/Rel-16/27_series/27005/raw.md b/marked/Rel-16/27_series/27005/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..42fac1df96aae1b26da634245f15f322c25d959a --- /dev/null +++ b/marked/Rel-16/27_series/27005/raw.md @@ -0,0 +1,2810 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 0 Scope..... | 7 | +| 0.1 References ..... | 8 | +| 0.2 Abbreviations ..... | 8 | +| 1 Reference configuration..... | 9 | +| 1.1 V.24 Interface Circuits ..... | 9 | +| 1.1.1 Circuit definitions for the SMS Block mode ..... | 9 | +| 1.1.2 Circuit definitions for the SMS Text and PDU modes..... | 10 | +| 2 SMS Block Mode..... | 10 | +| 2.1 Beginning and ending of SMS/CBS Block Mode..... | 10 | +| 2.1.1 Beginning SMS/CBS Block Mode..... | 10 | +| 2.1.2 Returning from SMS/CBS Block Mode To Default Mode ..... | 11 | +| 2.2 Protocol description..... | 11 | +| 2.3 Requesting messages already held in the Mobile Termination..... | 12 | +| 2.3.1 Requesting List Of Messages ..... | 13 | +| 2.3.2 Requesting Transfer Of Messages..... | 13 | +| 2.3.2.1 Requesting Transfer Of A Specific Message..... | 13 | +| 2.3.2.2 Requesting Transfer Of All Messages ..... | 13 | +| 2.3.3 Requesting Diversion Of Incoming Messages ..... | 14 | +| 2.3.3.1 Requesting SMS Messages..... | 14 | +| 2.3.3.2 Requesting CBS Messages ..... | 14 | +| 2.3.3.3 Requesting indication of message arrival ..... | 14 | +| 2.3.4 Requesting Transfer Into Mobile Termination..... | 15 | +| 2.3.5 Requesting Deletion Of Messages..... | 15 | +| 2.4 Message functional definitions and contents ..... | 16 | +| 2.4.1 Commands Issued By The Terminal Equipment..... | 16 | +| 2.4.1.1 List Request ..... | 17 | +| 2.4.1.2 Get Message..... | 17 | +| 2.4.1.3 Get First Message ..... | 17 | +| 2.4.1.4 Get Next Message..... | 17 | +| 2.4.1.5 Transfer Inc SMS..... | 17 | +| 2.4.1.6 Indicate Inc SMS ..... | 17 | +| 2.4.1.7 Transfer Inc CBS ..... | 18 | +| 2.4.1.8 Insert SMS ..... | 18 | +| 2.4.1.9 Delete message ..... | 18 | +| 2.4.1.10 Unable to process..... | 18 | +| 2.4.1.11 End SMS Mode..... | 18 | +| 2.4.1.12 Acknowledge Message ..... | 19 | +| 2.4.2 Responses/Indications Issued By The MT ..... | 19 | +| 2.4.2.1 Message List ..... | 19 | +| 2.4.2.2 Message ..... | 19 | +| 2.4.2.3 Get Message Failure ..... | 20 | +| 2.4.2.4 Inc Message ..... | 20 | +| 2.4.2.5 Message Arrived..... | 20 | +| 2.4.2.6 Insert SMS Complete..... | 20 | +| 2.4.2.7 Insert SMS Failure ..... | 20 | +| 2.4.2.8 Delete Message Complete ..... | 21 | +| 2.4.2.9 Delete Message Failure..... | 21 | +| 2.4.2.10 Unable To Process ..... | 21 | +| 2.4.2.11 End SMS Mode..... | 21 | +| 2.4.2.12 Request Confirmed ..... | 21 | +| 2.5 General message format and information elements coding ..... | 21 | +| 2.5.1 Message Type..... | 21 | +| 2.5.2 Other Information Elements ..... | 22 | +| 2.5.2.1 Short Message Reference..... | 22 | +| 2.5.2.2 SMS Transfer Type..... | 23 | +| 2.5.2.3 Indication Type..... | 23 | + +| | | | +|-------------------------------|---------------------------------------------------------|-----------| +| 2.5.2.4 | Insert Type ..... | 24 | +| 2.5.2.5 | Short Message Index..... | 25 | +| 2.5.2.6 | Short Message Data ..... | 26 | +| 2.5.2.7 | Cause..... | 28 | +| 2.5.2.8 | Index Count..... | 29 | +| 2.5.2.9 | CBS Transfer Type ..... | 29 | +| 2.5.2.10 | Page Index..... | 29 | +| 2.5.2.11 | Last Short Message..... | 30 | +| 2.5.2.12 | Confirm Type..... | 30 | +| 2.5.2.13 | TP-Failure Cause ..... | 31 | +| 2.5.2.14 | SM-Deliver-Ack ..... | 31 | +| 2.5.2.15 | SM-Submit-Ack..... | 32 | +| 3 | Text Mode..... | 32 | +| 3.1 | Parameter Definitions..... | 32 | +| 3.2 | General Configuration Commands..... | 35 | +| 3.2.1 | Select Message Service +CSMS ..... | 35 | +| 3.2.2 | Preferred Message Storage +CPMS ..... | 36 | +| 3.2.3 | Message Format +CMGF ..... | 36 | +| 3.2.4 | Enter SMS Block Mode Protocol +CESP ..... | 37 | +| 3.2.5 | Message Service Failure Result Code +CMS ERROR ..... | 37 | +| 3.2.6 | Informative Examples ..... | 38 | +| 3.3 | Message Configuration Commands ..... | 38 | +| 3.3.1 | Service Centre Address +CSCA..... | 38 | +| 3.3.2 | Set Text Mode Parameters +CSMP..... | 38 | +| 3.3.3 | Show Text Mode Parameters +CSDH..... | 39 | +| 3.3.4 | Select Cell Broadcast Message Types +CSCB ..... | 39 | +| 3.3.5 | Save Settings +CSAS ..... | 40 | +| 3.3.6 | Restore Settings +CRES..... | 40 | +| 3.3.7 | Informative Examples ..... | 41 | +| 3.4 | Message Receiving and Reading Commands ..... | 41 | +| 3.4.1 | New Message Indications to TE +CNMI ..... | 41 | +| 3.4.2 | List Messages +CMGL..... | 46 | +| 3.4.3 | Read Message +CMGR..... | 47 | +| 3.4.4 | New Message Acknowledgement to ME/TA +CNMA..... | 47 | +| 3.4.5 | Informative Examples ..... | 48 | +| 3.5 | Message Sending and Writing Commands ..... | 49 | +| 3.5.1 | Send Message +CMGS..... | 49 | +| 3.5.2 | Send Message from Storage +CMSS ..... | 50 | +| 3.5.3 | Write Message to Memory +CMGW ..... | 50 | +| 3.5.4 | Delete Message +CMGD ..... | 51 | +| 3.5.5 | Send Command +CMGC ..... | 52 | +| 3.5.6 | More Messages to Send +CMMS..... | 52 | +| 3.5.7 | Informative Examples ..... | 53 | +| 4 | PDU Mode ..... | 53 | +| 4.0 | General ..... | 53 | +| 4.1 | List Messages +CMGL ..... | 54 | +| 4.2 | Read Message +CMGR..... | 54 | +| 4.3 | Send Message +CMGS ..... | 54 | +| 4.4 | Write Message to Memory +CMGW..... | 55 | +| 4.5 | Send Command +CMGC ..... | 56 | +| 4.6 | New Message Acknowledgement to ME/TA +CNMA ..... | 56 | +| 4.7 | Send Message from Storage +CMSS..... | 57 | +| Annex A (normative): | Character Set Conversions for SMS Text Mode..... | 58 | +| Annex B (informative): | Example of processing a data block..... | 61 | +| B.1 | Example state diagrams for the block receiver ..... | 61 | +| B.2 | Example of coding and decoding a data block ..... | 61 | + +Annex C (informative):           Change History..................................................................................................68 + +# --- 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 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 specification; + +# 0 Scope + +The present document defines three interface protocols for control of SMS functions within a GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface. + +Clause 2 defines a binary protocol ("Block Mode"). The protocol includes error protection and is suitable for use where the link may not be completely reliable. It will be of particular use where control of remote devices is required. Efficient transfer of binary encoded user data is possible. + +Clause 3 defines a character-based interface based on "AT" commands ("Text Mode"). This mode is suitable for unintelligent terminals or terminal emulators, and for application software built on command structures like those defined in V.25ter. Some of the commands defined in clause 3 will also be useful for implementations of clause 2 and/or clause 4, for example enabling an indication of incoming SMS messages. + +Clause 4 defines a character-based interface with hex-encoded binary transfer of message blocks ("PDU Mode"). This mode is suitable for software drivers based on AT command structures which do not understand the content of the message blocks and can only pass them between the MT and "upper level" software resident in the TE. + +In all three modes, the terminal is considered to be in control for SMS/CBS transactions. + +The present document considers the mobile termination to be a single entity. Other 3GPP/GSM Technical Specifications describe the split of functionality between the mobile equipment and (U)SIM. + +The three "modes" referred to above, are represented in figure 0.1. + +The "Block mode" is a self contained mode in its own right, and when entered, control will remain within that mode until the procedures to exit the mode are executed, after which control is returned to the V.25ter "command" state or "on-line command" state. + +The "Text" and "PDU" modes are not in themselves V.25ter states but are simply sets of commands which will operate in either the V.25ter "command" state or "on-line command" state. The "Text" and "PDU" modes are transitory states and after each operation, control is automatically returned to the V.25ter "command" state or "on-line command" state. Whilst in the V.25ter command state, the MS is available to handle incoming and outgoing calls such as Data or Facsimile. + +![Diagram illustrating the relationship between V.25ter states and SMS modes. A large circle represents the 'V.25ter "command" state and "on-line command" state'. Inside this circle are two smaller circles labeled 'SMS Text Mode' and 'SMS PDU Mode'. Below the large circle, a rectangle labeled 'SMS Block Mode' is connected to the bottom of the circle by a vertical line.](34f788b0e5bc8af774fa5561c22e6d01_img.jpg) + +``` +graph TD; subgraph V25ter ["V.25ter 'command' state and 'on-line command' state"]; SMS_Text["SMS Text Mode"]; SMS_PDU["SMS PDU Mode"]; end; SMS_Block["SMS Block Mode"] --- V25ter; +``` + +Diagram illustrating the relationship between V.25ter states and SMS modes. A large circle represents the 'V.25ter "command" state and "on-line command" state'. Inside this circle are two smaller circles labeled 'SMS Text Mode' and 'SMS PDU Mode'. Below the large circle, a rectangle labeled 'SMS Block Mode' is connected to the bottom of the circle by a vertical line. + +**Figure 0.1: Block, Text and PDU modes** + +In the "Block mode" and "PDU" mode a mobile is not permitted to modify any component of an SMS/CBS message received from the air interface or an SMS message received from a TE, before passing it on, except where 3GPP TS 23.040 [3] or 3GPP TS 23.041 [4] defines a "component modification facility" and where this "component modification facility" is supported by the mobile. In the Text Mode the mobile may be unable to display characters coded in particular coding schemes. In this case, the mobile shall behave as described in 3GPP TS 23.038 [2] and assume the coding scheme to be the GSM 7 bit default alphabet. + +## 0.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] Void. +- [2] 3GPP TS 23.038: "Alphabets and language-specific information". +- [3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) ". +- [4] 3GPP TS 23.041: "Technical realization of the Cell Broadcast Service (CBS)". +- [5] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". +- [6] 3GPP TS 24.011: "Short Message Service (SMS) support on mobile radio interface". +- [7] 3GPP TS 24.012: "Cell Broadcast Service (CBS) support on the mobile radio interface". +- [8] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [9] 3GPP TS 27.007: "AT command set for User Equipment (UE)". +- [10] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". +- [11] ITU-T Recommendation V.25ter: "Serial asynchronous automatic dialling and control". +- [12] ITU-T Recommendation V.24: "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [13] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [14] ITU-T Recommendation E.163: "Numbering plan for the international telephone service". +- [15] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [16] 3GPP TS 31.102: "Characteristics of the USIM application". + +## 0.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [15] and the following] apply. + +| | | +|------|---------------------------------| +| EVPF | Enhanced Validity Period Format | +|------|---------------------------------| + +# 1 Reference configuration + +![Figure 1: Reference configuration diagram. A large rectangle labeled 'UE' contains two main components: a 'USIM' card on the left and a 'ME' (Mobile Equipment) block on the right. The 'ME' block contains two sub-components: 'MT' (Mobile Terminal) on top and 'TE' (Terminal Equipment) on the bottom.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +Figure 1: Reference configuration diagram. A large rectangle labeled 'UE' contains two main components: a 'USIM' card on the left and a 'ME' (Mobile Equipment) block on the right. The 'ME' block contains two sub-components: 'MT' (Mobile Terminal) on top and 'TE' (Terminal Equipment) on the bottom. + +**Figure 1: Reference configuration** + +The User Equipment (UE) consists of the mobile equipment (ME) and the (U)SIM. Messages may be stored in either, but the present document does not distinguish between messages stored in the (U)SIM or in the ME. The management of message storage in the two parts of the UE is a matter for the UE implementation. + +## 1.1 V.24 Interface Circuits + +The operation of the ITU-T Recommendation V.24 blue book interface circuits for SMS is shown in table 1.1. + +**Table 1.1: Use of V.24 interface circuits** + +| V.24 CIRCUIT | DESCRIPTION | TE to MT | MT to TE | +|--------------|---------------|----------|----------| +| CT102 | signal ground | x | x | +| CT103 | TXD | x | | +| CT104 | RXD | | x | +| CT105 | RTS | x | | +| CT106 | CTS | | x | +| CT107 | DSR | | x | +| CT108.2 | DTR | x | | +| CT109 | DCD | | x | + +NOTE: CT105 at the TE is connected to CT133 at the MT. + +### 1.1.1 Circuit definitions for the SMS Block mode + +#### CT103 + +All commands from the TE to the MT are transferred across this circuit. Inband flow control is not permitted during Block Mode. + +#### CT104 + +All responses/indications from the MT to the TE are transferred across this circuit. Inband flow control is not permitted during Block Mode. + +#### CT105 + +This circuit allows the TE to flow control the MT when in the Block Mode and at other times if hardware flow control is enabled. + +#### CT106 + +This circuit allows the MT to flow control the TE when in the Block Mode and at other times if hardware flow control is enabled. + +#### CT107 + +This circuit shall be set to the ON condition before entry into the Block Mode, and shall remain in the ON condition during Block Mode. If the TE detects that this circuit returns to the OFF condition during the block mode then the TE shall return CT108.2 to the OFF condition and exit the Block Mode. + +#### CT108.2 + +This circuit shall be set in the ON condition before the AT+CESP command is sent from the TE to begin the Block Mode, and shall be maintained in the ON condition during the Block Mode. It shall be returned to the OFF condition after the command 'END SMS MODE' has been accepted and acknowledged by the MT. If the MT detects that this circuit returns to the OFF condition during the Block Mode then the MT shall exit the Block Mode. + +#### CT109 + +This circuit shall be set to the ON condition before entry into the Block Mode and remain in the ON condition during the Block Mode. If the TE detects that this circuit returns to the OFF condition during the Block Mode then the TE shall return CT108.2 to the OFF condition and shall exit the Block Mode. + +### 1.1.2 Circuit definitions for the SMS Text and PDU modes + +Only circuits CT102, CT103 and CT104 are mandatory for the Text and PDU modes. The functionality and operation of other circuits shall be in accordance with V.25ter. + +# --- 2 SMS Block Mode + +## 2.1 Beginning and ending of SMS/CBS Block Mode + +### 2.1.1 Beginning SMS/CBS Block Mode + +As described in 3GPP TS 27.001 [8], the DTE/DCE interface is normally associated with the terminal adaptation function (TAF), if such a function is available. When no data connection is in progress, and the terminal equipment wishes to enter SMS/CBS mode, the command 'AT+CESP' shall be issued by the TE through the DTE/DCE interface requesting that the Block mode protocol described in the present document is to be used. The syntax of this command is further described in clause 3.2.4 later. The syntax for these commands is derived from ITU-T Recommendation V.25ter, i.e. the command is encoded as an IA5 character string together with delimiters as described in ITU-T Recommendation V.25ter. + +Upon receipt of this command, the mobile termination shall respond as follows: + +- If the mobile termination supports SMS/CBS block mode commands, responses and indications as described in the present document, it shall respond with 'OK' (or 0) and enter the SMS/CBS mode. +- If the mobile termination does not support SMS/CBS block mode commands, responses and indications as described in the present document, it shall respond with 'ERROR' (or 4) and remain in the current mode. +- Terminal software shall wait a short time (e.g. 5 seconds) for the 'OK' (0) or 'ERROR' (4) response. If neither response is received before the timeout then the terminal software shall assume that the block mode has been entered. The terminal software may then submit its first block mode command. If no response is received to this command then the terminal software shall proceed as described below in clause 2.2 (i.e. repeat the command 3 times and then exit the block mode). + +If the SMS/CBS block mode command is accepted by the mobile termination, then all further commands, responses and indications shall be as defined in clause 2 of the present document. These SMS/CBS mode commands, responses and indications use 8-bit encoded data and not IA5 characters. + +### 2.1.2 Returning from SMS/CBS Block Mode To Default Mode + +When the terminal equipment wishes to return to default mode from SMS/CBS mode, it shall issue the command 'END SMS MODE', described in clause 2.4.1.11. The mobile termination shall respond with 'OK' (or 0) to indicate that the DTE/DCE interface has returned to default mode. The TE shall change back to default mode whether or not such a response is received. + +The TE may also indicate that it has exit from the SMS/CBS mode through the use of CT 108/2 (see clause 1.1) + +If an incoming data call arrives while the DTE/DCE interface is set to SMS/CBS mode, then the mobile termination may autonomously issue the 'END SMS MODE' indication (clause 2.4.2.11) and revert to default mode in order to connect the data call through the TAF. + +The MT may exit from SMS/CBS mode autonomously if the power to the MT is switched off and then on again. In addition, the MT manufacturer may provide MMI to change the mode back to the default mode. In the latter case, the MT shall issue the 'END SMS MODE' indication (clause 2.4.2.11) and exit the SMS/CBS mode immediately. + +The MT may also indicate that it has exit from the SMS/CBS mode through the use of CT 107 and CT 109 (see clause 1.1). + +A BREAK condition in either direction at the DTE/DCE interface shall cause the TE and the MT to exit from the SMS/CBS block mode and return to the default mode. + +In the event where the TE or the MT find themselves unable to recover from a protocol error then either entity may exit the SMS/CBS mode using any of the mechanisms described above. Confirmation of default mode operation will be achieved through the use of AT commands and responses. + +## 2.2 Protocol description + +The communication path between the MT and the TE across the DTE/DCE interface should be quite reliable if it uses a short wire link. However, to ensure that the low error rate does not cause malfunction, the following error protection scheme is provided. + +Each message sent from the MT to the TE or vice-versa consists of a data block (DATA) and block check sum (BCS, see figure 2.2.1). In the following description the notation DLE, STX, NUL and ETX refer to control characters having the values 10 02 00 and 03 hexadecimal respectively. + +![](536951b2bbd94325ae266d8d1363df8f_img.jpg) + +<-----DATA-----> <- BCS -> + +| | | | | | | | +|-----|-----|-----------------|-----|-----|-----|-----| +| DLE | STX | Message content | DLE | ETX | BCS | BCS | +| 10H | 02H | | 10H | 03H | MSB | LSB | + +**Figure 2.2.1: Format of DTE/DCE interface messages** + +The data block consists of a start transmission sequence, set to 00010000 00000010 (10 02 hex), the message content as defined below and an end transmission sequence, set to 00010000 00000011 (10 03 hex). The least significant bit of each octet is always transmitted first. + +The block check sum is calculated at the transmitter by adding all of the octets in the message content modulo 65536. Each bit of the 16-bit result is then inverted, and 1 is added to the answer. + +During transmission of the message content and the BCS octets, any occurrence of the value 10 hex (DLE) shall result in an additional 'stuffing' octet of value 00 hex (NUL) being transmitted immediately following the octet containing 10 hex. This is to ensure that the start and end markers are unambiguous. The receiver shall remove stuffing octets by discarding any octet of value 00 hex (NUL) which immediately follows an octet of value 10 hex (DLE). + +After removal of any stuffing octets, the receiver can check the BCS by adding all of the octets in the message content and the 16-bit BCS modulo 65536. The correct result is 0000 hex. If any message is received with an incorrect BCS, then the message is discarded. No response is sent over the DTE/DCE interface, but an indication may be provided to higher layers within the receiving entity. + +The transmitter shall only send DLE when it is followed by STX, NUL or ETX. Therefore, if the receiver sees a DLE followed by anything else then the receiver shall assume that some data has been lost, and shall start to search for the + +start marker. An unexpected end marker at the receiver shall also result in a search for a start marker. A start marker shall always be treated as the start of a new block, regardless of which state the receiver is in. + +Examples of state diagrams for a block receiver to implement this procedure are given in Annex B, together with an example of coding and decoding a message. + +Only one Command/Response transaction shall be permitted at any one time from any sending or receiving entity. It shall however be possible for a Command/Response transaction from one entity to be initiated even if there is a Command/Response transaction in progress from the other entity. + +If an immediate response is expected to a message sent over the DTE/DCE interface, then the sending entity shall wait 10 s. If no response is received within this time, the sending entity shall repeat the message. The message shall be repeated a maximum of 3 times, after which the sending entity shall exit from the SMS/CBS mode and provide an error indication to the user. + +If a message cannot be understood by the receiving entity even though it has a correct BCS, then it shall return an UNABLE TO PROCESS message with cause value 'Command not understood'. The receipt of an UNABLE TO PROCESS message should not in itself initiate re-transmission although re-transmission may take place due to the timeout mechanism described earlier since an UNABLE TO PROCESS is deemed to be an invalid response. The 'Cause' may however be referred to a higher layer. An UNABLE TO PROCESS shall not be sent as the result of an incorrect BCS. + +## 2.3 Requesting messages already held in the Mobile Termination + +The TE may request the MT to provide SMS or CBS messages already stored. The TE will either request all messages, or request a list of messages and subsequently ask for specific messages. + +At the start of the SMS/CBS mode session, the MT shall number all messages contiguously, starting with message number 1. These "Short Message References" are only valid for a single SMS/CBS MODE session and should not be confused with the 3GPP TS 23.040 [3] TP-Message-Reference. Each message retains its Short Message Reference for the duration of the SMS/CBS mode session. New messages will normally be given the lowest previously-unused Short Message Reference. However, if all Short Message References have been used then the MT may reallocate Short Message References previously allocated to now-deleted messages. + +Short Message Reference 0 signifies that there are no messages in the MT. The value of 0 is used under the following conditions: + +- When an INSERT SMS command is used to transfer an SM over the air interface and not store it in the MT then the MT will return a Short Message Reference of 0 in the REQUEST CONFIRMED response and the ensuing INSERT SMS COMPLETE / INSERT SMS FAILURE indications. +- For Class 0 SM's which are not stored in the MT. +- For TE specific SM's which are not stored in the MT. + +If Message number 0 is requested by the TE, the MT will always return an error cause, but will also include the highest valid Short Message Reference (see clause 2.3.2.1). + +### 2.3.1 Requesting List Of Messages + +The TE may request the MT to provide a list of SMS and CBS messages currently stored in the mobile termination. This is achieved by the LIST REQUEST command (clause 2.4.1.1). The MT divides the messages stored into groups of 5 (called pages) and transfers the first 5 in a MESSAGE LIST response (clause 2.4.2.1) containing message references allocated by the MT, plus the relevant header information described in 3GPP TS 23.040 [3] and 3GPP TS 24.011 [6] and 3GPP TS 23.041 [4] and 3GPP TS 24.012 [7]. + +If there are no messages stored in the MT, then the MESSAGE LIST response shall be empty. + +The TE may then request further groups of up to 5 messages by repeating the LIST REQUEST command for pages 2, 3, and so on. The MT will indicate that there are no more pages by responding with an empty MESSAGE LIST response. + +### 2.3.2 Requesting Transfer Of Messages + +The TE may request the transfer of one or more messages by means of the commands described below. The MT does not delete messages which have been transferred. Messages can only be deleted by the DELETE MESSAGE command (clause 2.4.1.9). + +#### 2.3.2.1 Requesting Transfer Of A Specific Message + +The TE may request the MT to transfer a specific message by sending the GET MESSAGE command (clause 2.4.1.2), including the appropriate message reference. The MT will provide the full message including header in a MESSAGE response (clause 2.4.2.2). If the message reference is unallocated, then the GET MESSAGE FAILURE response is returned with cause 'No such message' and the highest valid Message Reference (clause 2.4.2.3). + +#### 2.3.2.2 Requesting Transfer Of All Messages + +The TE may request the MT to transfer all messages by sending the GET FIRST MESSAGE command (clause 2.4.1.3), followed by the appropriate number of GET NEXT MESSAGE commands (clause 2.4.1.4). + +The MT shall be able to transfer all messages one-by-one, starting with the 'first' and continuing with the 'next'. The precise ordering of the messages is left to the MT implementation. + +If the MT exits from SMS/CBS mode for any reason, then this information need not be retained. + +On receipt of the GET FIRST MESSAGE command, the MT shall set a pointer to the first message, and transfer this message using the MESSAGE response as described in clause 2.3.2.1. + +On receipt of the GET NEXT MESSAGE command, the MT shall move the pointer to the first available message after the last message transferred (using either GET FIRST MESSAGE, GET MESSAGE or GET NEXT MESSAGE), and transfer this message using the MESSAGE response as described in clause 2.3.2.1. + +If the MT receives a GET NEXT MESSAGE command when all messages have been transferred to the TE, or there are no messages stored in the MT, then the GET MESSAGE FAILURE response shall be provided with the cause 'No such message' (see clause 2.4.2.3). + +If the TE receives an out of sequence message then it shall attempt to transfer the missing message using the GET MESSAGE command before continuing with GET NEXT MESSAGE. If this attempt fails with the cause 'no such message', it means that the message has been deleted, or it has been lost due to a failure at the MT. + +The MT includes a LAST SHORT MESSAGE REFERENCE in the GET MESSAGE FAILURE response. This is so that the TE can detect whether or not the last short message was received in error. + +If the MT receives a GET NEXT MESSAGE command prior to receiving a GET FIRST MESSAGE or GET MESSAGE command, then it shall continue as if the command had been GET FIRST MESSAGE (i.e. provide the 'first' message and continue with the 'next' on receipt of the subsequent GET NEXT MESSAGE command). + +### 2.3.3 Requesting Diversion Of Incoming Messages + +The TE may request the MT to transfer SMS or CBS messages directly from the air interface to the DTE/DCE interface, by the following procedures. If messages are diverted then they are not stored in the MT. If messages are diverted and there is no communication path to the TE (e.g. because it has been disconnected), the diversion shall be cancelled. + +#### 2.3.3.1 Requesting SMS Messages + +The TE may request an indication of arrival of incoming SMS messages, or the direct transfer of incoming SMS messages. + +The TE requests new SMS messages by the TRANSFER INC SMS command (clause 2.4.1.5). This command will be sent with parameters indicating whether all incoming SMS messages are to be transferred, or only those indicated as being for the TE. + +The MT shall confirm receipt of this command with a REQUEST CONFIRMED message provided there is memory available to store SM's in the ME or the (U)SIM. If there is no memory available, the MT shall respond with 'unable to process' with a cause value No memory. + +The MT shall transfer incoming messages by the INC MESSAGE indication (clause 2.4.2.4). + +For an INC MESSAGE which contains a Short Message (SMS) info element id, the TE shall acknowledge receipt of the INC MESSAGE with an ACKNOWLEDGE MESSAGE (clause 2.4.1.12). The MT should not send another INC MESSAGE which contains a Short Message (SMS) info element id to the TE whilst it is waiting for an ACKNOWLEDGE MESSAGE. + +In the event of the MT not receiving an ACKNOWLEDGE MESSAGE within a time specified by the MT manufacturer the MT shall exit the SMS mode automatically after 'n' attempts to send the INC MESSAGE (where n is a number specified by the MT manufacturer). The MT should attempt to store the unacknowledged SM or Status Report (contained in the INC MESSAGE) in the MT or on the (U)SIM as appropriate. + +The ACKNOWLEDGE MESSAGE sent from the TE to the MT must not delay the MT sending the RP-ACK defined in 3GPP TS 23.040 [3] (to the SC) for longer than the RP-ACK timeout specified in 3GPP TS 24.011 [6]. + +The TE requests the cessation of incoming message transfer by the same command, indicating no incoming messages. The transfer of messages will automatically cease on exit of the SMS/CBS mode. Transfer shall not recommence until a new request is issued by the TE. + +#### 2.3.3.2 Requesting CBS Messages + +The TE may request the transfer of all cell broadcast messages directly from the air interface to the DTE/DCE interface. This is achieved by the use of the TRANSFER INC CBS message (clause 2.4.1.7). + +The MT shall confirm receipt of this command with a REQUEST CONFIRMED message. + +After receipt of this command, the MT shall transfer all CBS pages as they arrive on the air interface, using the INC MESSAGE indication (clause 2.4.2.4). + +While the CBS pages are being transferred, any other indication or response required to be sent to the TE will take precedence over the CBS pages. However, the MT shall not interrupt the transfer of a page to send other information within the SMS/CBS mode (ie. the MT shall wait until a page boundary). + +The transfer of messages will automatically cease on exit of the SMS/CBS mode. Transfer shall not recommence until a new request is issued by the TE. + +#### 2.3.3.3 Requesting indication of message arrival + +If the TE requires an indication of incoming message arrival, the INDICATE INC SMS command (clause 2.4.1.6) shall be used. + +The MT shall confirm receipt of this command with a REQUEST CONFIRMED message. + +After receipt of this command, the MT shall indicate all incoming messages in the specified categories (unless they are directly transferred) with the MESSAGE ARRIVED indication (clause 2.4.2.5). This indication shall be of the same format as the MESSAGE LIST response described in clause 2.3.1. + +The TE shall acknowledge receipt of the MESSAGE ARRIVED with an ACKNOWLEDGE MESSAGE. (clause 2.4.1.12). The MT should not send another MESSAGE ARRIVED to the TE whilst it is waiting for an ACKNOWLEDGE MESSAGE. + +In the event of the MT not receiving an ACKNOWLEDGE MESSAGE within a time specified by the MT manufacturer the MT shall exit the SMS mode automatically after 'n' attempts to send the MESSAGE ARRIVED (where n is a number specified by the MT manufacturer). The MT should attempt to store the unacknowledged SM or Status Report in the MT or on the (U)SIM as appropriate. + +The ACKNOWLEDGE MESSAGE sent from the TE to the MT must not delay the MT sending the RP-ACK defined in 3GPP TS 23.040 [3] (to the SC) for longer than the RP-ACK timeout specified in the 3GPP TS 24.011 [6]. + +The TE requests the cessation of incoming message indication by the INDICATE INC SMS command, with the 'no incoming messages' parameter. + +### 2.3.4 Requesting Transfer Into Mobile Termination + +The TE may request transfer of SMS messages into the mobile termination. Cell broadcast messages cannot be transferred in this direction. + +The TE shall use the INSERT SMS command (clause 2.4.1.8) to transfer the message. This command shall indicate whether the message is to be stored in the MT, sent over the air interface or both. The command shall include the full SMS message and header as described in 3GPP TS 23.040 [3], except for the message reference and message type indication (which are allocated by the MT). + +Only one INSERT SMS command may be outstanding at any given instant. An INSERT SMS is deemed complete when an INSERT SMS COMPLETE or an INSERT SMS FAILURE indication has been received irrespective of whether an intermediate REQUEST CONFIRMED has been received. + +Upon receipt of an INSERT SMS command, the MT shall act in the following way: + +If the TE requested the MT to store the message, the MT shall attempt to store the message. If the attempt is successful, the MT shall return an INSERT SMS COMPLETE indication (clause 2.4.2.6), including the message reference allocated by the MT. If the attempt fails (eg. due to lack of memory), the MT shall return an INSERT SMS FAILURE indication (clause 2.4.2.7), providing a cause for the failure. + +If the TE requested the MT to send the message, the MT shall respond immediately with a REQUEST CONFIRMED message, and attempt to send the message. If the send attempt subsequently succeeds, the MT shall send an INSERT SMS COMPLETE indication, including the message references allocated by the MT. If the send attempt subsequently fails, the MT shall return an INSERT SMS FAILURE indication, providing a cause for the failure. + +If the TE requested the MT to store and send the message, the MT shall first attempt to store the message. If no storage is available, the MT shall return an INSERT SMS FAILURE indication (clause 2.4.2.7) and shall not attempt to send the message. If storage is available, the MT shall store the message and then respond with a REQUEST CONFIRMED message. If the send attempt is successful, the MT shall return an INSERT SMS COMPLETE indication (clause 2.4.2.6), including the message references allocated by the MT. If the transmission of the message fails, then the MT shall return an INSERT SMS FAILURE indication (clause 2.4.2.7). This will show that the send attempt failed and provide a cause. After that the MT shall delete the stored message. + +### 2.3.5 Requesting Deletion Of Messages + +The TE may request deletion of SMS or CBS messages from the store in the MT. This is achieved by the DELETE MESSAGE command (clause 2.4.1.9). The command will include a message reference, as defined by the MT and provided in the message list. + +Upon receipt of this command, the MT shall attempt to delete the message. If successful, the MT shall return a DELETE MESSAGE COMPLETE indication (clause 2.4.2.8). If not successful, the MT shall return a DELETE MESSAGE FAILURE indication (clause 2.4.2.9). + +On successful deletion of an SM or CBS message the Page Index (see clause 2.5.2.10) and the Index Count (see clause 2.5.2.8) shall be re-assigned so that their values are contiguous (i.e. there are no gaps in either parameter). The original short message Reference values remain unchanged. + +## 2.4 Message functional definitions and contents + +This clause provides an overview of the message structure to be used over the DTE/DCE interface in SMS/CBS block mode. Each message definition includes a brief description of the use of the message, and a table showing all the information elements which may be included in the message. If an entity receives a message containing more information elements than expected then the receiving entity shall ignore the additional information elements. For each information element the following data are provided. + +Reference - this indicates where the detailed description of each element can be found. + +### **Presence:** + +| | | | +|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M | Mandatory | must always be present
receiver: If not present, consider message erroneous | +| C | Conditional | presence depending on e.g.
a) value of other element
b) presence of optional element
receiver: If not present when condition met, consider message erroneous | +| O | Optional | presence is a choice of the sender
receiver: present or not, accept message | + +### **Format:** + +| | | +|-----|----------------------------------------------------------------------------------| +| T | Type only, fixed length, only IEI | +| V | Value only, fixed length, no IEI included | +| TV | Type and value, fixed length, IEI included | +| LV | Length and value, variable length, no IEI included and Length indicator included | +| TLV | Type, Length and Value, variable length, IEI and length indicator included | + +Length - this indicates the length of the information element in octets. + +### 2.4.1 Commands Issued By The Terminal Equipment + +Table 2.4.1 summarises the commands which may be issued by the TE. + +**Table 2.4.1: Commands which may be issued by the TE** + +| | Reference | +|---------------------|-----------| +| LIST REQUEST | 2.4.1.1 | +| GET MESSAGE | 2.4.1.2 | +| GET FIRST MESSAGE | 2.4.1.3 | +| GET NEXT MESSAGE | 2.4.1.4 | +| TRANSFER INC SMS | 2.4.1.5 | +| INDICATE INC SMS | 2.4.1.6 | +| TRANSFER INC CBS | 2.4.1.7 | +| INSERT SMS | 2.4.1.8 | +| DELETE MESSAGE | 2.4.1.9 | +| UNABLE TO PROCESS | 2.4.1.10 | +| END SMS MODE | 2.4.1.11 | +| ACKNOWLEDGE MESSAGE | 2.4.1.12 | + +#### 2.4.1.1 List Request + +This message is sent by the TE to the MT to request a list of messages stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Page Index | 2.5.2.10 | M | V | 1 | + +#### 2.4.1.2 Get Message + +This message is sent by the TE to the MT to request transfer of a specific SMS or CBS message stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | + +#### 2.4.1.3 Get First Message + +This message is sent by the TE to the MT to request transfer of the first available SMS or CBS message stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | + +#### 2.4.1.4 Get Next Message + +This message is sent by the TE to the MT to request transfer of the next available SMS or CBS message stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | + +#### 2.4.1.5 Transfer Inc SMS + +This message is sent by the TE to the MT to request the direct transfer of incoming messages from the air interface to the TE. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| SMS Transfer Type | 2.5.2.2 | M | V | 1 | + +#### 2.4.1.6 Indicate Inc SMS + +This message is sent by the TE to the MT to request that the MT indicates when an incoming message arrives. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Indication Type | 2.5.2.3 | M | V | 1 | + +#### 2.4.1.7 Transfer Inc CBS + +This message is sent by the TE to the MT to request transfer of all cell broadcast messages directly from the air interface to the DTE/DCE interface. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| CBS Transfer Type | 2.5.2.9 | M | V | 1 | + +#### 2.4.1.8 Insert SMS + +This message is sent by the TE to the MT to request the transfer of an SMS TPU to the MT memory or across the air interface. The TPDU is formatted in exactly the same way as described in 3GPP TS 23.040 [3]. Where the TPDU includes a TP-Message-Reference which is to be incremented by the MT for every outgoing message, the TP-Message-Reference provided by the TE will be overwritten by the MT before transmission of the message. The value provided by the TE is discarded by the MT and has no significance. + +| Information element | Reference | Presence | Format | Length | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------|----------|--------|---------| +| Message Type | 2.5.1 | M | V | 1 | +| Insert Type | 2.5.2.4 | M | V | 1 | +| RP-Destination-Address | 3GPP TS 24.011 [6] | M | LV | 1-12 a) | +| SMS-TPDU | 3GPP TS 23.040 [3] | M | V | max 164 | +| a) | If no RP-Destination-Address is to be transferred then the length is set to 0. In this case, the MT inserts the default SC address. | | | | + +#### 2.4.1.9 Delete message + +This message is sent from the TE to the MT to request deletion of a specific SMS or CBS message held in the MT. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | + +#### 2.4.1.10 Unable to process + +This response is sent from the TE to the MT to indicate that the MT's message could not be processed. + +| Information element | Preference | Presence | Format | Length | +|---------------------|------------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.1.11 End SMS Mode + +This message is sent from the TE to the MT to terminate the SMS/CBS mode of the DTE/DCE interface. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | + +#### 2.4.1.12 Acknowledge Message + +This message is sent from the TE to the MT to acknowledge receipt of a INC MESSAGE or MESSAGE ARRIVED which contains a Short Message (SMS) info element id, (e.g. a Short Message or a Status Report but not a CBS message). + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|----------| +| Message Type | 2.5.1 | M | V | 1 | +| SM-Deliver-Ack | 2.5.2.14 | O | TLV | 2 to 160 | + +### 2.4.2 Responses/Indications Issued By The MT + +Table 2.4.2 summarises the responses/indications which may be issued by the MT. + +**Table 2.4.2: Responses/Indications which may be issued by the MT** + +| | Reference | +|-------------------------|-----------| +| MESSAGE LIST | 2.4.2.1 | +| MESSAGE | 2.4.2.2 | +| GET MESSAGE FAILURE | 2.4.2.3 | +| INC MESSAGE | 2.4.2.4 | +| MESSAGE ARRIVED | 2.4.2.5 | +| INSERT SMS COMPLETE | 2.4.2.6 | +| INSERT SMS FAILURE | 2.4.2.7 | +| DELETE MESSAGE COMPLETE | 2.4.2.8 | +| DELETE MESSAGE FAILURE | 2.4.2.9 | +| UNABLE TO PROCESS | 2.4.2.10 | +| END SMS MODE | 2.4.2.11 | +| REQUEST CONFIRMED | 2.4.2.12 | + +#### 2.4.2.1 Message List + +This response is sent from the MT to the TE on receipt of a LIST REQUEST from the TE. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Page Index | 2.5.2.10 | M | V | 1 | +| Index Count | 2.5.2.8 | M | V | 1 | +| Short Message Index (1) | 2.5.2.5 | O | TLV | 8-48 | +| Short Message Index (2) | 2.5.2.5 | O | TLV | 8-48 | +| : | : | : | : | : | +| Short Message Index (n) | 2.5.2.5 | O | TLV | 8-48 | + +The number of Short Message Indices included in the message may be 0, 1, 2, 3, 4 or 5. + +#### 2.4.2.2 Message + +This response is sent from the MT to the TE when a short message has been requested. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Data | 2.5.2.6 | M | TLV | 28-181 | + +#### 2.4.2.3 Get Message Failure + +This response is sent from the MT to the TE when a request for a short message cannot be fulfilled. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Last Short Message | 2.5.2.11 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.4 Inc Message + +This indication is sent from the MT to the TE after the MT has been requested to transfer messages of certain categories immediately upon receipt. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Data | 2.5.2.6 | M | TLV | 28-181 | + +#### 2.4.2.5 Message Arrived + +This indication is sent from the MT to the TE after the MT has been requested to provide an indication of the receipt of certain categories of incoming message. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Index | 2.5.2.5 | M | TLV | 8-48 | + +#### 2.4.2.6 Insert SMS Complete + +This response is sent by the MT to the TE to indicate that the TE's request to insert a message has been completed. + +| Information element | Reference | Presence | Format | Length | +|--------------------------------------------------------------------------------------------------------------------------|--------------------|----------|--------|----------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | +| TP-Message Reference | 3GPP TS 23.040 [3] | C a) | V | 1 | +| SM-Submit-Ack | 2.5.2.15 | O | TLV | 2 to 160 | +| a) The TP-Message Reference is only included if the message had been requested to be transferred over the air interface. | | | | | + +#### 2.4.2.7 Insert SMS Failure + +This response is sent from the MT to the TE to indicate that the attempt to insert an SMS message failed. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1-2 | +| TP-Failure Cause | 2.5.2.13 | O | TLV | 4 | +| Short Message Reference | 2.5.2.1 | O | TV | 2 | + +#### 2.4.2.8 Delete Message Complete + +This response is sent from the MT to the TE to indicate that the request to delete a message from the MT store has been completed. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | + +#### 2.4.2.9 Delete Message Failure + +This response is sent from the MT to the TE to indicate that the request to delete a message from the MT store failed. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.10 Unable To Process + +This response is sent from the MT to the TE to indicate that the TE's request could not be processed. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.11 End SMS Mode + +This indication is sent from the MT to the TE when the MT autonomously exits from SMS/CBS mode. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.12 Request Confirmed + +This indication is sent from the MT to the TE to indicate that the MT has received the request from the TE and will perform the requested function. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Confirm Type | 2.5.2.12 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | O | TV | 2 | + +## 2.5 General message format and information elements coding + +This clause describes the content of messages for the SMS/CBS mode of the DTE/DCE interface. Within the figures in this clause, the bit designated "bit 1" is transmitted first, followed by bits 2, 3, 4, etc. Similarly, the octet shown at the top of each figure is sent first. + +### 2.5.1 Message Type + +The purpose of the message type is to identify the function of the message being sent. The message type is coded as shown in figure 2.5.1 and table 2.5.1. + +Bit 8 is reserved for possible future use as an extension bit. + +![](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +| | | | | | | | | | +|---|--------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | Message Type | | | | | | | octet 1 | + +Figure 2.5.1: Message Type + +Table 2.5.1: Message Types + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|------------------------------------| +| 0 | 0 | 0 | - | - | - | - | - | Commands/ Responses issued by TE | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | LIST REQUEST | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | GET MESSAGE | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | GET FIRST MESSAGE | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | GET NEXT MESSAGE | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | TRANSFER INC SMS | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | INDICATE INC SMS | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | TRANSFER INC CBS | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | INSERT SMS | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | DELETE MESSAGE | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | UNABLE TO PROCESS | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | END SMS MODE | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | ACKNOWLEDGE MESSAGE | +| 0 | 0 | 1 | - | - | - | - | - | Responses/Indications issued by MT | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | MESSAGE LIST | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | MESSAGE | +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | GET MESSAGE FAILURE | +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | INC MESSAGE | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | MESSAGE ARRIVED | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | INSERT SMS COMPLETE | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | INSERT SMS FAILURE | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | DELETE MESSAGE COMPLETE | +| 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | DELETE MESSAGE FAILURE | +| 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | UNABLE TO PROCESS | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | REQUEST CONFIRMED | +| 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | END SMS MODE | + +All other values are reserved. If a reserved Message Type is received then the receiving entity shall return "Unable to Process" with Cause "Command not understood". + +### 2.5.2 Other Information Elements + +Other information elements follow the general coding principles specified in 3GPP TS 24.008 [5], and are described in the following clauses. + +#### 2.5.2.1 Short Message Reference + +The Short Message Reference uniquely identifies a short message stored in the MT. It is an 8 bit number and is allocated by the MT. + +The Short Message Reference information element is coded as shown in figure 2.5.2 and table 2.5.2. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | octet 1 | +| Short Message Reference info element id | | | | | | | | octet 2 | + +**Figure 2.5.2: Short Message Reference information element** + +**Table 2.5.2: Short Message Reference information element** + +Short Message Reference value (octet 2). + +In the Short Message Reference value field bit 8 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. + +Short Message Reference values are allocated by the MT. + +#### 2.5.2.2 SMS Transfer Type + +The SMS Transfer Type indicates to the MT which SMS messages are required to be transferred to the TE. + +The SMS Transfer Type information element is coded as shown in figure 2.5.3 and table 2.5.3. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|------------------------|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | octet 1 | +| SMS Transfer Type info element ident | | | | | | | | octet 2 | +| 0 | 0 | 0 | 0 | 0 | SMS Txfr
Type value | | | | +| Reserved | | | | | | | | | + +**Figure 2.5.3: SMS Transfer Type information element** + +**Table 2.5.3: SMS Transfer Type information element** + +SMS Txfr Type value (octet 2). + +The SMS txfr type is coded as follows: + +| bit 2 | bit 1 | | +|-------|-------|------------------------------------------------| +| 0 | 0 | Transfer no SMS messages | +| 0 | 1 | Transfer SMS messages marked as
TE-specific | +| 1 | 0 | Reserved | +| 1 | 1 | Transfer all SMS messages | + +Bit 3 shows whether to transfer SMS-STATUS-REPORTS + +| Bit 3 | | +|-------|------------------------------------| +| 0 | Do not transfer SMS-STATUS-REPORTS | +| 1 | Transfer SMS-STATUS-REPORTS | + +A receiving entity shall ignore the setting of bits 8-4. If bit 2 is set to 1 and bit 1 is set to 0 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.3 Indication Type + +The Indication Type tells the MT when to notify the TE that an incoming message has been received. + +The Indication Type information element is coded as shown in figure 2.5.4 and table 2.5.4. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------|---|---|---|-----------------------|---|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | octet 1 | +| Indication Type info element identifier | | | | | | | | | +| 0 | 0 | 0 | 0 | Indication Type value | | | | octet 2 | +| Reserved | | | | | | | | | + +**Figure 2.5.4: Indication Type information element** + +**Table 2.5.4: Indication Type information element** + +Indication Type value (octet 2). + +The indication type is coded as follows: + +| bit 3 | bit 2 | bit 1 | | +|-------|-------|-------|--------------------------------------------------------| +| 0 | 0 | 0 | Indicate no messages | +| 0 | 0 | 1 | Reserved | +| 0 | 1 | 0 | Indicate all SMS messages | +| 0 | 1 | 1 | Indicate SMS messages marked as
TE-specific | +| 1 | 0 | 0 | Indicate all CBS messages | +| 1 | 0 | 1 | Indicate CBS messages marked as
TE-specific | +| 1 | 1 | 0 | Indicate all CBS and SMS messages | +| 1 | 1 | 1 | Indicate SMS and CBS messages marked
as TE-specific | + +Bit 4 shows whether or not to indicate SMS reports: + +| bit 4 | | +|-------|-----------------------------| +| 0 | Do not indicate SMS reports | +| 1 | Indicate SMS reports | + +A receiving entity shall ignore the setting of bits 8-5. If bits 3 and 2 are set to 0 and bit 1 is set to 1 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood". + +#### 2.5.2.4 Insert Type + +The Insert Type tells the MT what to do with the short message arriving from the TE. + +The Insert Type information element is coded as shown in figure 2.5.5 and table 2.5.5 + +![](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +| | | | | | | | | | +|-------------------------------------|----------|----------|----------|----------|----------|-------------------|----------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | octet 1 | +| Insert Type info element identifier | | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | 0 | Insert Type value | | octet 2 | +| Reserved | | | | | | | | | + +**Figure 2.5.5: Insert Type information element****Table 2.5.5: Insert Type information element** + +Insert Type value (octet 2). + +The insert type is coded as follows: + +| bit 2 | bit 1 | | +|-------|-------|------------------------------------------------------------| +| 0 | 0 | Reserved | +| 0 | 1 | Store the short message in the MT | +| 1 | 0 | Send the short message over the air | +| 1 | 1 | Store the short message in the MT and send it over the air | + +A receiving entity shall ignore the setting of bits 8-3. If bits 2 and 1 are set to 0 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.5 Short Message Index + +The Short Message Index provides information about each individual short message currently stored in the MT. Two types of Short Message index are provided; one for SMS and one for CBS. + +The Short Message Index (SMS) information element is coded as shown in figure 2.5.6 and table 2.5.6. A Short Message Index may be an SMS-SUBMIT, an SMS-DELIVER or an SMS-STATUS-REPORT. + +The Short Message Index (CBS) information element is coded as shown in figure 2.5.7 and table 2.5.7. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------|---|---|---|---|---|---|---|----------------------| +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | octet 1 | +| Short Message Index (SMS) info element id | | | | | | | | | +| Length of Short Message Index | | | | | | | | octet 2 | +| Short Message Reference value | | | | | | | | octet 3 | +| Short Message Status | | | | | | | | octet 4 | +| Service Centre Address | | | | | | | | octets
5-n | +| Short Message Header (SMS) | | | | | | | | octets
n+1 - n+31 | + +**Figure 2.5.6: Short Message Index (SMS) information element** + +NOTE: n can take a value between 5 and 18 (inclusive). + +**Table 2.5.6: Short Message Index (SMS) information element** + +Short Message Reference value (octet 3). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message Status (octet 4). + +The Short Message Status is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|-------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Not read/not sent | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Read/Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Not Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | Not Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Sent | + +All other values are reserved. + +The receiving entity shall ignore the setting of bits 8-4. + +In addition, if bit 3 is set to 0 then a receiving entity shall ignore the setting of bit 2. Where bit 3 is set to 0, if the message is mobile originated then bit 1 indicates whether the message has been sent to the network. If the message is mobile terminated then bit 1 indicates whether the message has been read. + +Service Centre Address (Octets 5-n). + +The Service Centre Address is coded as the RP-Origination or RP-Destination address specified in 3 TS 24.011 [6]. If the short message is mobile originated, the address will be the RP-Destination address. If the short message is mobile terminated, the address will be the RP-Origination address. The address is of variable length, 1-12 octets. + +Short Message Header (SMS) (Octets n+1 - n+31). + +The Short Message Header (SMS) is coded as a TPDU as described in 3GPP TS 23.040 [3]. In the case of SMS-DELIVER or SMS-SUBMIT, the TP-User-Data is not included, but the TP-User-Data-Length is included. The Short Message Header is of variable length, 6-31 octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------|---|---|---|---|---|---|---|------------| +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | octet 1 | +| Short Message Index (CBS) info element id | | | | | | | | octet 2 | +| Short Message Reference value | | | | | | | | octets 3-8 | +| Short Message Header (CBS) | | | | | | | | | + +**Figure 2.5.7: Short Message Index (CBS) information element** + +**Table 2.5.7: Short Message Index (CBS) information element** + +Short Message Reference value (octet 2). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message Header (CBS) (Octets 3-8). + +The Short Message Header (CBS) is coded as described in 3GPP TS 23.041. [4], including SEQUENCE NUMBER, MESSAGE IDENTIFIER, ALPHABET IDENTIFIER and PAGE PARAMETER, but excluding the characters of the message. + +#### 2.5.2.6 Short Message Data + +The Short Message Data information element is a copy of a short message currently stored in the MT. Two types of Short Message Data information element are provided; one for SMS and one for CBS. + +The Short Message Data (SMS) information element is coded as shown in figure 2.5.8 and table 2.5.8. Short Message Data may be an SMS-SUBMIT, an SMS-DELIVER or an SMS-STATUS-REPORT. + +The Short Message Data (CBS) information element is coded as shown in figure 2.5.9 and table 2.5.9. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|------------------| +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | octet 1 | +| Short Message Data (SMS) info element id | | | | | | | | octet 2 | +| Length of Short Message Data | | | | | | | | octet 3 | +| Short Message Reference value | | | | | | | | octet 4 | +| Short Message Status | | | | | | | | octets 5-n | +| Service Centre Address | | | | | | | | octets n+1-n+164 | +| Short Message (SMS) | | | | | | | | | + +**Figure 2.5.8: Short Message Data (SMS) information element** + +NOTE: n can take a value between 5 and 18 (inclusive). + +**Table 2.5.8: Short Message (SMS) information element** + +Short Message Reference value (octet 3). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message Status (octet 4). + +The Short Message Status is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|-------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Not read/not sent | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Read/Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Not Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | Not Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Sent | + +All other values are reserved. + +The receiving entity shall ignore the setting of bits 8-4. + +In addition, if bit 3 is set to 0 then a receiving entity shall ignore the setting of bit 2. + +Where bit 3 is set to 0, if the message is mobile originated then bit 1 indicates whether the message has been sent to the network. If the message is mobile terminated then bit 1 indicates whether the message has been read. + +Service Centre Address (Octets 5-n). + +The Service Centre Address is coded as the RP-Origination-Address or RP-Destination Address specified in 3GPP TS 23.040 [3]. + +If the short message is mobile originated, the address will be the RP-Destination address. If the short message is mobile terminated, the address will be the RP-Origination Address. The address is of variable length, 1-12 octets. + +Short Message (SMS) (Octets n+1 - n+164). + +The Short Message (SMS) is coded as a TPDU as described in 3GPP TS 23.040 [3]. + +The Short Message is of variable length, 6-164 octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | octet 1 | +| Short Message Data (CBS) info element id | | | | | | | | octet 2 | +| Short Message Reference value | | | | | | | | octets | +| Short Message (CBS) | | | | | | | | 3-90 | + +**Figure 2.5.9: Short Message Data (CBS) information element****Table 2.5.9: Short Message Data (CBS) information element** + +Short Message Reference value (octet 2). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message (CBS) (Octets 3-90). + +The Short Message (CBS) is coded as described in 3GPP TS 23.041 [4], including SEQUENCE NUMBER, MESSAGE IDENTIFIER, ALPHABET IDENTIFIER, PAGE PARAMETER and CHARACTERS OF THE MESSAGE. + +#### 2.5.2.7 Cause + +The Cause information element provides more detail as to why an error has occurred. The Cause information element is coded as shown in figure 2.5.10 and table 2.5.10. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|-------------|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | octet 1 | +| Cause information element identifier | | | | | | | | octet 2 | +| 0
ext | Cause value | | | | | | | octet 3 | +| 3GPP TS 24.011 [6] RP-Cause value | | | | | | | | | + +Figure 2.5.10: Cause information element + +Table 2.5.10: Cause information element + +Cause value (octet 2). + +The cause is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|--------------------------------------------------------------------------------------------------------------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | No such message | +| | | | | | | | - | - no short message exists with the provided shortmessage reference | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | No memory | +| | | | | | | | - | - the short message cannot be stored due to lack of memory | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | No air interface | +| | | | | | | | - | - submission of the short message cannot be attempted because the mobile is out of coverage | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | Receiving entity busy | +| | | | | | | | - | - the request was not fulfilled because the Receiving entity is busy on another task | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Command not understood | +| | | | | | | | - | - error in the coding of the command, or command belongs to higher version of protocol of protocol than that implemented | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Incoming data call | +| | | | | | | | - | - Incoming data call forces MT to exit from SMS mode | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | User-invoked exit | +| | | | | | | | - | - User has taken MT out of SMS by MMI | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Other error | +| | | | | | | | - | - Any other error not covered here | +| 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Message Transfer failed | +| | | | | | | | - | - The SMS transfer to the SC failed and the 3GPP TS 24.011 [6] error cause is provided in octet 3 | + +All other values are reserved. + +A receiving entity shall treat any reserved codings as "other error". + +3GPP TS 24.011 [6] RP-Cause value (octet 3) + +If this element is included then bit 8 of octet 2 is set to '1'. The error cause included in the RP-Cause over the air interface is directly mapped into this element. This element is only included if the MT attempts to send a short message to the network and that send attempt fails. + +#### 2.5.2.8 Index Count + +The Index Count identifies the number of short message indices contained in a MESSAGE LIST response from the MT to the TE. It is an 8 bit number. + +The Index Count information element is coded as shown in figure 2.5.11 and table 2.5.11. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | octet 1 | +| Index Count information element ident | | | | | | | | octet 2 | + +**Figure 2.5.11: Index Count information element** + +**Table 2.5.11: Index Count information element** + +Index Count value (octet 2). + +In the Index Count field bit 8 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. + +#### 2.5.2.9 CBS Transfer Type + +The CBS Transfer Type indicates to the MT which CBS messages are required to be transferred to the TE. + +The CBS Transfer Type information element is coded as shown in figure 2.5.12 and table 2.5.12. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|----------|------------|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | octet 1 | +| CBS Transfer Type info element ident | | | | | | | | octet 2 | +| 0 | 0 | 0 | 0 | 0 | 0 | CBS Txfr | Type value | | +| Reserved | | | | | | | | | + +**Figure 2.5.12: CBS Transfer Type information element** + +**Table 2.5.12: CBS Transfer Type information element** + +CBS Txfr Type value (octet 2). + +The CBS txfr type is coded as follows: + +bit 2 bit 1 + +| | | | +|---|---|---------------------------------------------| +| 0 | 0 | Transfer no CBS messages | +| 0 | 1 | Transfer CBS messages marked as TE-specific | +| 1 | 0 | Reserved | +| 1 | 1 | Transfer all CBS messages | + +A receiving entity shall ignore the setting of bits 8-3. If bit 2 is set to 1 and bit 1 is set to 0 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.10 Page Index + +The Page Index indicates to the MT which Page of SMS Indices is required to be transferred. It also indicates to the TE which Page of SMS Indices is being transferred. + +The Page Index information element is coded as shown in figure 2.5.13 and table 2.5.13. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------|---|------------------|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | octet 1 | +| 0 0
Reserved | | Page Index value | | | | | | octet 2 | + +Figure 2.5.13: Page Index information element + +Table 2.5.13: Page Index information element + +Page Index value (octet 2). + +In the Page Index field bit 6 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. The Page Index can have a value from 1 to 51. + +A receiving entity shall ignore the setting of bits 8 and 7. If the Page Index field has a value of 0 or a value greater than 51 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.11 Last Short Message + +The Last Short Message field indicates to the TE the highest value of Short Message Reference which points to a valid message stored in the MT. The value 0 signifies that there are no short messages stored in the MT. + +The Last Short Message information element is coded as shown in figure 2.5.14 and table 2.5.14. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | octet 1 | +| Last Short Message value | | | | | | | | octet 2 | + +Figure 2.5.14: Last Short Message information element + +Table 2.5.14: Last Short Message information element + +Last Short Message value (octet 2). + +In the Last Short Message field bit 8 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. The Last Short Message can have a value from 0 to 255. + +#### 2.5.2.12 Confirm Type + +The Confirm Type field indicates the message to which the REQUEST CONFIRM is a response. + +The Confirm Type information element is coded as shown in figure 2.5.15 and table 2.5.15. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | octet 1 | +| Confirm Type value | | | | | | | | octet 2 | + +Figure 2.5.15: Confirm Type information element + +**Table 2.5.15: Confirm Type information element** + +| | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---------------------------------------------------------------------------------------------------| +| Confirm Type value (octet 2). | | | | | | | | | +| The Confirm Type is coded as follows: | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Reserved | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Confirm request to transfer incoming SMS messages | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | Confirm request to transfer incoming CBS messages | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | Confirm request to indicate arrival of messages in MT | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Confirm request to attempt to send short message (actual send is confirmed later; see clause 3.3) | +| All other values are reserved. If any reserved value is received then the receiving entity shall return "Unable to Process" with cause value "Command Not Understood". | | | | | | | | | + +#### 2.5.2.13 TP-Failure Cause + +This optional field is present if provided by the Relay Layer. The TP-Failure Cause is provided from the Service Centre and indicates to the TE the reason why the delivery of the message was unsuccessful. The TP-Failure cause information element is coded as shown in figure 2.5.16 and table 2.5.16. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|---|---|------------| +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | octet 1 | +| Cause information element identifier | | | | | | | | | +| Length of Failure cause field | | | | | | | | octet 2 | +| Failure cause | | | | | | | | octets 3-4 | + +**Figure 2.5.16: TP-Failure Cause information element****Table 2.5.16: TP-Failure Cause information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Failure cause (octet 3-4) | +| The failure cause contained in this field is directly mapped from the TP-Failure Cause (TP-FCS) field of the SMS-SUBMIT-REPORT message defined in 3GPP TS 23.040 [3]. | + +#### 2.5.2.14 SM-Deliver-Ack + +This optional field is sent from the TE to the MT to convey the information to be inserted into the SMS-DELIVER-REPORT RP-ACK TPDU sent by the MT to the SC as defined in 3GPP TS 23.040 [3]. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------|---|---|---|---|---|---|---|--------------| +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | octet 1 | +| SM-DELIVER-ACK information element identifier | | | | | | | | | +| Length of SMS-DELIVER-REPORT RP-ACK Field | | | | | | | | octet 2 | +| 03.40 SMS-DELIVER-REPORT RP-ACK | | | | | | | | octets 3-166 | + +#### 2.5.2.15 SM-Submit-Ack + +This optional field is sent from the MT to the TE to convey the information to be inserted into the SMS-SUBMIT-REPORT RP-ACK TPDU sent by the SC to the MT as defined in 3GPP TS 23.040 [3]. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|--------------|---------| +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | octet 1 | +| SM-SUBMIT-ACK information element identifier | | | | | | | octet 2 | | +| Length of SMS-SUBMIT-REPORT RP-ACK Field | | | | | | | octets 3-166 | | + +# 3 Text Mode + +## 3.1 Parameter Definitions + +The following parameters are used in the subsequent clauses which describe all commands. The formats of integer and string types referenced here are defined in V.25ter. The default values are for command parameters, not for result code parameters. + +### Message Storage Parameters + + integer type; value in the range of location numbers supported by the associated memory + + string type; memory from which messages are read and deleted (commands List Messages +CMGL, Read Message +CMGR and Delete Message +CMGD); defined values (others are manufacturer specific): + +"BM" broadcast message storage + +"ME" ME message storage + +"MT" any of the storages associated with ME + +"SM" (U)SIM message storage + +"TA" TA message storage + +"SR" status report storage + + string type; memory to which writing and sending operations are made (commands Send Message from Storage +CMSS and Write Message to Memory +CMGW ); refer for defined values + + string type; memory to which received SMs are preferred to be stored (unless forwarded directly to TE; refer command New Message Indications +CNMI); refer for defined values; received CBMs are always stored in "BM" (or some manufacturer specific storage) unless directly forwarded to TE; received status reports are always stored in "SR" (or some manufacturer specific storage) unless directly forwarded to TE + + integer type in PDU mode (default 0), or string type in text mode (default "REC UNREAD"); indicates the status of message in memory; defined values: + +0 "REC UNREAD" received unread message (i.e. new message) + +1 "REC READ" received read message + +2 "STO UNSENT" stored unsent message (only applicable to SMs) + +3 "STO SENT" stored sent message (only applicable to SMs) + +4 "ALL" all messages (only applicable to +CMGL command) + + integer type; total number of message locations in + + integer type; total number of message locations in + + integer type; total number of message locations in + + integer type; number of messages currently in + + integer type; number of messages currently in + + integer type; number of messages currently in + +### Message Data Parameters + + 3GPP TS 23.040 [3] RP-User-Data element of RP-ACK PDU; format is same as for in case of SMS, but without 3GPP TS 24.011 [6] SC address field and parameter shall be bounded by double quote characters like a normal string type parameter + + string type alphanumeric representation of or corresponding to the entry found in MT phonebook; implementation of this feature is manufacturer specific; used character set should be the one selected with command Select TE Character Set +CSCS (see definition of this command in 3GPP TS 27.007 [9]) + + 3GPP TS 23.040 [3] TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) + + 3GPP TS 23.040 [3] TP-Command-Type in integer format (default 0) + + 3GPP TS 23.040 [3] TP-Destination-Address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in 3GPP TS 27.007 [9]); type of address given by + + In the case of SMS: 3GPP TS 23.040 [3] TP-User-Data in text mode responses; format: + +- if indicates that 3GPP TS 23.038 [2] GSM 7 bit default alphabet is used and indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is not set: + - if TE character set other than "HEX" (refer command Select TE Character Set +CSCS in 3GPP TS 27.007 [9]): ME/TA converts GSM alphabet into current TE character set according to rules of Annex A + - if TE character set is "HEX": ME/TA converts each 7-bit character of GSM 7 bit default alphabet into two IRA character long hexadecimal number (e.g. character Ψ (GSM 7 bit default alphabet decimal 23) is presented as 17 (IRA 49 and 55)) +- if indicates that 8-bit or UCS2 data coding scheme is used, or indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is set: ME/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) + +In the case of CBS: 3GPP TS 23.041 [4] CBM Content of Message in text mode responses; format: + +- if indicates that 3GPP TS 23.038 [2] GSM 7 bit default alphabet is used: + - if TE character set other than "HEX" (refer command +CSCS in 3GPP TS 27.007 [9]): ME/TA converts GSM alphabet into current TE character set according to rules of Annex A + - if TE character set is "HEX": ME/TA converts each 7-bit character of the GSM 7 bit default alphabet into two IRA character long hexadecimal number +- if indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each 8-bit octet into two IRA character long hexadecimal number + + depending on the command or result code: 3GPP TS 23.038 [2] SMS Data Coding Scheme (default 0), or Cell Broadcast Data Coding Scheme in integer format + +-
3GPP TS 23.040 [3] TP-Discharge-Time in time-string format: "yy/MM/dd,hh:mm:ss±zz", where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone. E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to "94/05/06,22:10:00+08" +- depending on the command or result code: first octet of 3GPP TS 23.040 [3] SMS-DELIVER, SMS-SUBMIT (default 17), SMS-STATUS-REPORT, or SMS-COMMAND (default 2) in integer format +- integer type value indicating in the text mode (+CMGF=1) the length of the message body (or ) in characters; or in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length) +- 3GPP TS 23.041 [4] CBM Message Identifier in integer format +- 3GPP TS 23.040 [3] TP-Message-Number in integer format +- 3GPP TS 23.040 [3] TP-Message-Reference in integer format +- 3GPP TS 23.040 [3] TP-Originating-Address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in TS 07.07); type of address given by +- 3GPP TS 23.041 [4] CBM Page Parameter bits 4-7 in integer format +- 3GPP TS 23.041 [4] CBM Page Parameter bits 0-3 in integer format +- In the case of SMS: 3GPP TS 24.011 [6] SC address followed by 3GPP TS 23.040 [3] TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) +- In the case of CBS: 3GPP TS 23.041 [4] TPDU in hexadecimal format +- 3GPP TS 23.040 [3] TP-Protocol-Identifier in integer format (default 0) +- 3GPP TS 23.040 [3] TP-Recipient-Address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in 3GPP TS 27.007 [9]); type of address given by +- 3GPP TS 24.011 [6] RP SC address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in 3GPP TS 27.007 [9]); type of address given by +- 3GPP TS 23.040 [3] TP-Service-Centre-Time-Stamp in time-string format (refer
) +- 3GPP TS 23.041 [4] CBM Serial Number in integer format +- 3GPP TS 23.040 [3] TP-Status in integer format +- 3GPP TS 24.011 [6] TP-Destination-Address Type-of-Address octet in integer format (when first character of is + (IRA 43) default is 145, otherwise default is 129) +- 3GPP TS 24.011 [6] TP-Originating-Address Type-of-Address octet in integer format (default refer ) +- 3GPP TS 24.011 [6] TP-Recipient-Address Type-of-Address octet in integer format (default refer ) +- 3GPP TS 24.011 [6] RP SC address Type-of-Address octet in integer format (default refer ) +- depending on SMS-SUBMIT setting: 3GPP TS 23.040 [3] TP-Validity-Period either in integer format (default 167) or in time-string format (refer
) +- depending on SMS-SUBMIT setting: 3GPP TS 23.040 [3] TP-Validity-Period either in integer format (default 167), in time-string format (refer
), or if EVPF is supported, in enhanced format (hexadecimal coded string with double quotes) + +## 3.2 General Configuration Commands + +### 3.2.1 Select Message Service +CSMS + +**Table 3.2.1-1: +CSMS Parameter Command Syntax** + +| Command | Possible response(s) | +|-----------------|----------------------------------------------| +| +CSMS= | +CSMS: , ,
+CMS ERROR: | +| +CSMS? | +CSMS: , , , | +| +CSMS=? | +CSMS: (list of supported s) | + +#### Description + +Set command selects messaging service . It returns the types of messages supported by the ME: for mobile terminated messages, for mobile originated messages and for broadcast type messages. If chosen service is not supported by the ME (but is supported by the TA), final result code +CMS ERROR: shall be returned. See chapter Message Service Failure Result Code for a list of values. + +Also read command returns supported message types along the current service setting. + +Test command returns a list of all services supported by the TA. + +#### Defined Values + +: integer type + +- 0 3GPP TS 23.040 [3] and 3GPP TS 23.041 [4] +- 1 3GPP TS 23.040 [3] and 3GPP TS 23.041 [4] (the requirement of setting 1 is mentioned under corresponding command descriptions) +- 2...127 reserved +- 128... manufacturer specific + +, , : integer type + +- 0 type not supported +- 1 type supported + +#### Implementation + +Mandatory if SMS is supported. + +### 3.2.2 Preferred Message Storage +CPMS + +**Table 3.2.2-1: +CPMS Parameter Command Syntax** + +| Command | Possible response(s) | +|----------------------------------|-------------------------------------------------------------------------------------------------------------| +| +CPMS=[, [, ]] | +CPMS: , , , , ,
+CMS ERROR: | +| +CPMS? | +CPMS: , , , , , , , ,
+CMS ERROR: | +| +CPMS=? | +CPMS: (list of supported s) , (list of supported s) ,
(list of supported s) | + +#### Description + +Set command selects memory storages , and to be used for reading, writing, etc. If chosen storage is not appropriate for the ME (but is supported by the TA), final result code +CMS ERROR: shall be returned. See chapter Message Service Failure Result Code for a list of possible values. + +Test command returns lists of memory storages supported by the TA. + +#### Implementation + +Mandatory if SMS is supported. + +### 3.2.3 Message Format +CMGF + +**Table 3.2.3-1: +CMGF Parameter Command Syntax** + +| Command | Possible response(s) | +|----------------|------------------------------------| +| +CMGF=[] | | +| +CMGF? | +CMGF: | +| +CMGF=? | +CMGF: (list of supported s) | + +#### Description + +Set command tells the TA, which input and output format of messages to use. indicates the format of messages used with send, list, read and write commands and unsolicited result codes resulting from received messages. Mode can be either PDU mode (entire TP data units used) or text mode (headers and body of the messages given as separate parameters). Text mode uses the value of parameter specified by command Select TE Character Set +CSCS to inform the character set to be used in the message body in the TA-TE interface. + +Test command returns supported modes as a compound value. + +#### Defined Values + +: integer type + +- 0 PDU mode +- 1 text mode + +#### Implementation + +Mandatory if SMS is supported also when only one mode implemented. + +### 3.2.4 Enter SMS Block Mode Protocol +CESP + +**Table 3.2.4-1: +CESP Action Command Syntax** + +| Command | Possible response(s) | +|---------|----------------------| +| +CESP | | +| +CESP=? | | + +#### Description + +Execution command sets the TA in SMS block protocol mode. The TA shall return OK (or 0) to confirm acceptance of the command prior to entering the block mode (see clause 2.1.1). The final result code OK (or 0) shall be returned when the block mode is exited. + +NOTE: Commands following +CESP in the AT command line must not be processed by the TA. + +#### Implementation + +Mandatory when block mode implemented. + +### 3.2.5 Message Service Failure Result Code +CMS ERROR + +Final result code +CMS ERROR: indicates an error related to mobile equipment or network. The operation is similar to ERROR final result code. None of the following commands in the same command line is executed. Neither ERROR nor OK final result code shall be returned. ERROR is returned normally when error is related to syntax or invalid parameters. + +#### Defined Values + + values used by common messaging commands: + +| | | +|-----------|----------------------------------------------| +| 0...127 | 3GPP TS 24.011 [6] clause E.2 values | +| 128...255 | 3GPP TS 23.040 [3] clause 9.2.3.22 values. | +| 300 | ME failure | +| 301 | SMS service of ME reserved | +| 302 | operation not allowed | +| 303 | operation not supported | +| 304 | invalid PDU mode parameter | +| 305 | invalid text mode parameter | +| 310 | (U)SIM not inserted | +| 311 | (U)SIM PIN required | +| 312 | PH-(U)SIM PIN required | +| 313 | (U)SIM failure | +| 314 | (U)SIM busy | +| 315 | (U)SIM wrong | +| 316 | (U)SIM PUK required | +| 317 | (U)SIM PIN2 required | +| 318 | (U)SIM PUK2 required | +| 320 | memory failure | +| 321 | invalid memory index | +| 322 | memory full | +| 330 | SMSC address unknown | +| 331 | no network service | +| 332 | network timeout | +| 340 | no +CNMA acknowledgement expected | +| 500 | unknown error | +| ...511 | other values in range 256...511 are reserved | +| 512... | manufacturer specific | + +#### Implementation + +Mandatory if SMS is supported. + +### 3.2.6 Informative Examples + +Setting up a TA supporting SMS: + +``` + +AT+CSMS=? (inquiry of available services in TA) ++CSMS: (0) +OK +AT+CSMS=0;+CPMS=? (set SMS; query available memories) ++CSMS: 1,1,1 (all MT, MO and CBM supported) ++CPMS: ("BM","ME","SM"), ("ME","SM"), ("ME","SM") (CBM, ME and (U)SIM memories for reading,) +OK ME and (U)SIM memories for writing) +AT+CPMS="ME","ME","ME";+CMGF=? (set ME memory; query available message formats) ++CPMS: "ME",5,99,"ME",5,99,"ME",5,99 (five messages in ME, 99 total space) ++CMGF: (0,1) (both text and PDU mode implemented) +OK +AT+CMGF=1;+CSCS=? (select text mode; query available TE character sets) ++CSCS: ("IRA","PCCP437","8859-1") +OK +AT+CSCS="PCCP437" (select PC code page 437) +OK + +``` + +## 3.3 Message Configuration Commands + +### 3.3.1 Service Centre Address +CSCA + +**Table 3.3.1-1: +CSCA Parameter Command Syntax** + +| Command | Possible response(s) | +|------------------------|-----------------------| +| +CSCA=[, ] | | +| +CSCA? | +CSCA: , | +| +CSCA=? | | + +#### Description + +Set command updates the SMSC address, through which mobile originated SMs are transmitted. In text mode, setting is used by send and write commands. In PDU mode, setting is used by the same commands, but only when the length of the SMSC address coded into parameter equals zero. + +#### Implementation + +Mandatory if SMS is supported. + +### 3.3.2 Set Text Mode Parameters +CSMP + +**Table 3.3.2-1: +CSMP Parameter Command Syntax** + +| Command | Possible response(s) | +|----------------------------------------|---------------------------------| +| +CSMP=[[, [, [, ]]]] | | +| +CSMP? | +CSMP: , , , | +| +CSMP=? | | + +#### Description + +Set command is used to select values for additional parameters needed when SM is sent to the network or placed in a storage when text format message mode is selected. It is possible to set the validity period starting from when the SM is received by the SMSC ( is in range 0... 255) or define the absolute time of the validity period termination ( is a string). The format of is given by . If TA supports the EVPF, see 3GPP TS 23.040 [3], it shall be given as a hexadecimal coded string (refer e.g. ) with double quotes. + +NOTE: When storing a SMS-DELIVER from the TE to the preferred memory storage in text mode (refer command Write Message to Memory +CMGW), field can be used for . + +#### Implementation + +Mandatory when text mode implemented. + +### 3.3.3 Show Text Mode Parameters +CSDH + +**Table 3.3.3-1: +CSDH Parameter Command Syntax** + +| Command | Possible response(s) | +|----------------|------------------------------------| +| +CSDH=[] | | +| +CSDH? | +CSDH: | +| +CSDH=? | +CSDH: (list of supported s) | + +#### Description + +Set command controls whether detailed header information is shown in text mode result codes. + +Test command returns supported values as a compound value. + +#### Defined Values + +: integer type + +- 0 do not show header values defined in commands +CSCA and +CSMP (, , , , and ) nor , or in +CMT, +CMGL, +CMGR result codes for SMS-DELIVERs and SMS-SUBMITs in text mode; for SMS-COMMANDs in +CMGR result code, do not show , , , , or +- 1 show the values in result codes + +#### Implementation + +Mandatory when text mode implemented. + +### 3.3.4 Select Cell Broadcast Message Types +CSCB + +**Table 3.3.4-1: +CSCB Parameter Command Syntax** + +| Command | Possible response(s) | +|------------------------------------|------------------------------------| +| +CSCB=[[, [, ]]] | | +| +CSCB? | +CSCB: , , | +| +CSCB=? | +CSCB: (list of supported s) | + +#### Description + +Set command selects which types of CBMs are to be received by the ME. + +Test command returns supported modes as a compound value. + +#### Defined Values + +: integer type + +- 0 message types specified in and are accepted +- 1 message types specified in and are not accepted + +: string type; all different possible combinations of CBM message identifiers (refer ) (default is empty string); e.g. "0,1,5,320-478,922" + +: string type; all different possible combinations of CBM data coding schemes (refer ) (default is empty string); e.g. "0-3,5" + +#### Implementation + +Optional. + +### 3.3.5 Save Settings +CSAS + +**Table 3.3.5-1: +CSAS Action Command Syntax** + +| Command | Possible response(s) | +|-------------------|---------------------------------------| +| +CSAS[=] | +CMS ERROR: | +| +CSAS=? | +CSAS: (list of supported s) | + +#### Description + +Execution command saves active message service settings to a non-volatile memory. A TA can contain several profiles of settings. Settings specified in commands Service Centre Address +CSCA, Set Message Parameters +CSMP and Select Cell Broadcast Message Types +CSCB (if implemented) are saved. Certain settings may not be supported by the storage (e.g. (U)SIM SMS parameters) and therefore can not be saved. See chapter Message Service Failure Result Code for values. + +Test command shall display the supported profile numbers for reading and writing of settings. + +#### Defined Values + +: integer type + +0..255 manufacturer specific profile number where settings are to be stored + +#### Implementation + +Optional. + +### 3.3.6 Restore Settings +CRES + +Table 3.3.6-1: +CRES Action Command Syntax + +| Command | Possible response(s) | +|-------------------|---------------------------------------| +| +CRES[=] | +CMS ERROR: | +| +CRES=? | +CRES: (list of supported s) | + +#### Description + +Execution command restores message service settings from non-volatile memory to active memory. A TA can contain several profiles of settings. Settings specified in commands Service Centre Address +CSCA, Set Message Parameters +CSMP and Select Cell Broadcast Message Types +CSCB (if implemented) are restored. Certain settings may not be supported by the storage (e.g. (U)SIM SMS parameters) and therefore can not be restored. See chapter Message Service Failure Result Code for values. + +#### Defined Values + +: integer type + +0..255 manufacturer specific profile number from where settings are to be restored + +#### Implementation + +Optional. + +### 3.3.7 Informative Examples + +Figure 3.3.7-1 illustrates an example setup of a TE-TA-ME system for SMS. Location of volatile and non-volatile parameter memories, and the operations to change the parameter values are shown. +CSMP is used to set the text mode header values of SMS-SUBMIT (or SMS-DELIVER when received message is written from TE to a storage). The volatile memory may as well be in the ME, or when no volatile memory is used, +CSMP, +CSCA and +CSCB settings are stored directly to non-volatile memory of ME. + +![Diagram illustrating message service parameter procedures between ME, TA, and TE. The diagram shows three main components: ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The ME contains two storage areas: 'SMI STORAGES' and 'CBM STORAGES'. 'SMI STORAGES' contains 'text mode parameters for send and write, SMSC address; non-volatile memory'. 'CBM STORAGES' contains 'cell broadcast types to be stored; non-volatile and volatile memories'. The TA contains 'text mode parameters for send and write, SMSC address; volatile memory'. Arrows indicate data flow: from TE to TA for 'set SMSC address +CSCA and set text mode parameters +CSMP'; from TA to ME for 'save +CSAS' and 'power-up and restore +CRES'; from ME to TA for 'save to non-volatile or restore to volatile'; and from TA to ME for 'select cell broadcast message types +CSCB'.](583e14835ddabad1d8b92a07b82fc31b_img.jpg) + +Diagram illustrating message service parameter procedures between ME, TA, and TE. The diagram shows three main components: ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The ME contains two storage areas: 'SMI STORAGES' and 'CBM STORAGES'. 'SMI STORAGES' contains 'text mode parameters for send and write, SMSC address; non-volatile memory'. 'CBM STORAGES' contains 'cell broadcast types to be stored; non-volatile and volatile memories'. The TA contains 'text mode parameters for send and write, SMSC address; volatile memory'. Arrows indicate data flow: from TE to TA for 'set SMSC address +CSCA and set text mode parameters +CSMP'; from TA to ME for 'save +CSAS' and 'power-up and restore +CRES'; from ME to TA for 'save to non-volatile or restore to volatile'; and from TA to ME for 'select cell broadcast message types +CSCB'. + +Figure 3.3.7-1: Message service parameter procedures + +In this example, the volatile parameter settings of TA are used to construct messages in text mode. SMSC address setting is used also in PDU mode. The next example illustrates a session to restore the message parameters from the ME to the TA, and to set up the CBM identifiers (and languages) which are wanted to be received: + +``` +AT+CRES (restore settings from non-volatile memory to volatile memory) +OK +AT+CSMP?;+CSCA? (query SM parameters) ++CSMP: 17,167,0,0 (default values for SMS-SUBMIT) ++CSCA: "+358501234567",145 (SMSC address) +OK +AT+CSDH=1 (show all headers in text mode) +OK +AT+CSCB=1 (all CBMs are accepted) +OK +``` + +## 3.4 Message Receiving and Reading Commands + +### 3.4.1 New Message Indications to TE +CNMI + +**Table 3.4.1-1: +CNMI Parameter Command Syntax** + +| Command | Possible response(s) | +|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| +CNMI=[[, [, [, [, ]]]]] | +CMS ERROR: | +| +CNMI? | +CNMI: , , , , | +| +CNMI=? | +CNMI: (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) | + +#### Description + +Set command selects the procedure, how receiving of new messages from the network is indicated to the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receiving should be done as specified in 3GPP TS 23.038 [2]. + +NOTE 1: When DTR signal is not available or the state of the signal is ignored (V.25ter command &D0), reliable message transfer can be assured by using +CNMA acknowledgement procedure. + + controls the processing of unsolicited result codes specified within this command, sets the result code indication routing for SMS-DELIVERs, for CBMs and for SMS-STATUS-REPORTs. defines the handling method for buffered result codes when 1, 2 or 3 is enabled. If ME does not support requested item (although TA does), final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. + +Test command gives the settings supported by the TA as compound values. + +NOTE 2: Command Select Message Service +CSMS should be used to detect ME support of mobile terminated SMs and CBMs, and to define whether a message routed directly to TE should be acknowledged or not (refer command +CNMA). + +#### Defined Values + +: integer type (refer figure 3.4.1-1) + +NOTE 3: The buffering mechanism may as well be located in the ME; the setting affects only to unsolicited result codes specified within this command): + +- 0 Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or the oldest indications may be discarded and replaced with the new received indications. +- 1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to the TE. + +- 2 Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line data mode) and flush them to the TE after reservation. Otherwise forward them directly to the TE. +- 3 Forward unsolicited result codes directly to the TE. TA-TE link specific inband technique used to embed result codes and data when TA is in on-line data mode. + +NOTE 4: It is possible that ME/TA result code buffer is in volatile memory. In this case messages may get lost if the power of ME/TA is switched off before codes are sent to TE. Thus, it is not recommended to use direct message routing (=2 or 3, =2 or 3, or =1) with value 0 or 2. + +![Diagram illustrating the parameter for message routing between ME, TA, and TE. The diagram shows the flow of messages and indications from the ME through the TA to the TE, categorized by values 0, 1, 2, and 3. For mode 0, all messages go through a Buffer. For mode 1, COMMAND MODE messages go through a Buffer, while DATA MODE messages go directly to the TE. For mode 2, all messages go directly to the TE. For mode 3, all messages go directly to the TE. Unsolicited result codes are also shown being sent to the TE.](e05122559f56af5699789b7118d8fe87_img.jpg) + +The diagram shows the following components and flows: + +- ME (Mobile Equipment):** Sends "received messages and indications" to the TA. +- TA (Terminal Adapter):** Contains two sub-sections: **COMMAND MODE** and **DATA MODE**. + - In **COMMAND MODE**, there is a **Buffer**. + - In **DATA MODE**, there is a direct path to the TE. +- TE (Terminal Equipment):** Receives messages and indications from the TA. +- parameter:** Has four values: 0, 1, 2, and 3. + - Mode 0:** All messages from ME pass through the Buffer in the TA before reaching the TE. + - Mode 1:** COMMAND MODE messages pass through the Buffer, while DATA MODE messages go directly to the TE. + - Mode 2:** All messages from ME go directly to the TE, bypassing the Buffer. + - Mode 3:** All messages from ME go directly to the TE, bypassing the Buffer. +- Unsolicited result codes:** Indicated by arrows labeled "+CMTI, +CMT, +CBMI, +CBM, +CDSI, +CDS" pointing from the TA to the TE. + +Diagram illustrating the parameter for message routing between ME, TA, and TE. The diagram shows the flow of messages and indications from the ME through the TA to the TE, categorized by values 0, 1, 2, and 3. For mode 0, all messages go through a Buffer. For mode 1, COMMAND MODE messages go through a Buffer, while DATA MODE messages go directly to the TE. For mode 2, all messages go directly to the TE. For mode 3, all messages go directly to the TE. Unsolicited result codes are also shown being sent to the TE. + +Figure 3.4.1-1: parameter + +: integer type (the rules for storing received SMs depend on its data coding scheme (refer 3GPP TS 23.038 [2]), preferred memory storage (+CPMS) setting and this value; refer table 3.4.1-2; + +NOTE 5: If AT command interface is acting as the only display device, the ME must support storing of class 0 messages and messages in the message waiting indication group (discard message); refer table 3.4.1-3): + +- 0 No SMS-DELIVER indications are routed to the TE. +- 1 If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: + ++CMTI: , + +- 2 SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store message)) are routed directly to the TE using unsolicited result code: + ++CMT: [], (PDU mode enabled); or + ++CMT: , [], , , , , , , , (text mode enabled; about parameters in italics, refer command Show Text Mode Parameters +CSDH) + +If ME has its own display device then class 0 messages and messages in the message waiting indication group (discard message) may be copied to both ME display and to TE. In this case, ME shall send the acknowledgement to the network (refer table 2). + +Class 2 messages and messages in the message waiting indication group (store message) result in indication as defined in =1. + +- 3 Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in =2. Messages of other data coding schemes result in indication as defined in =1. + +**Table 3.4.1-2: parameter** + +| | Receiving procedure for different message data coding schemes (refer 3GPP TS 23.038 [2]) | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | no class: as in 3GPP TS 23.038 [2], but use as preferred memory
class 0: as in 3GPP TS 23.038 [2], but use as preferred memory if message is tried to be stored
class 1: as in 3GPP TS 23.038 [2], but use as preferred memory
class 2: as in 3GPP TS 23.038 [2]
class 3: as in 3GPP TS 23.038 [2], but use as preferred memory
message waiting indication group (discard message): as in 3GPP TS 23.038 [2], but use as preferred memory if message is tried to be stored
message waiting indication group (store message): as in 3GPP TS 23.038 [2], but use as preferred memory | +| 1 | as =0 but send indication if message stored successfully | +| 2 | no class: route message to TE
class 0: as in 3GPP TS 23.038 [2], but also route message to TE and do not try to store it in memory
class 1: route message to TE
class 2: as =1
class 3: route message to TE
message waiting indication group (discard message): as in 3GPP TS 23.038 [2], but also route message to TE and do not try to store it in memory
message waiting indication group (store message): as =1 | +| 3 | class 3: route message to TE
others: as =1 | + +**Table 3.4.1-3: SMS-DELIVER result code and acknowledgement summary** + +| | no class or class 1 | class 0 or message waiting indication group (discard) | class 2 or message waiting indication group (store) | class 3 | +|------|---------------------------|-------------------------------------------------------|-----------------------------------------------------|---------------------------| +| 1 | +CMTI | [+CMTI 1 ] | +CMTI | +CMTI | +| 2 | +CMT & +CNMA 3 | +CMT [& +CNMA 2 ] | +CMTI | +CMT & +CNMA 3 | +| 3 | +CMTI | [+CMTI 1 ] | +CMTI | +CMT & +CNMA 3 | + +1) result code is sent when ME does not have other display device than AT interface. +2) acknowledgement command must be sent when +CSMS value equals 1 and ME does not have other display device than AT interface. +3) acknowledgement command must be sent when +CSMS value equals 1. + + integer type (the rules for storing received CBMs depend on its data coding scheme (refer 3GPP TS 23.038 [2]), the setting of Select CBM Types (+CSCB) and this value; refer table 3.4.1-4): + +0 No CBM indications are routed to the TE. + +1 If CBM is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: + ++CBMI: , + +2 New CBMs are routed directly to the TE using unsolicited result code: + ++CBM: (PDU mode enabled); or + ++CBM: , , , , (text mode enabled) + +If ME supports data coding groups which define special routing also for messages other than class 3 (e.g. (U)SIM specific messages), ME may choose not to route messages of such data coding schemes into TE (indication of a stored CBM may be given as defined in =1). + +3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in =2. If CBM storage is supported, messages of other classes result in indication as defined in =1. + +**Table 3.4.1-4: parameter** + +| | | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Receiving procedure for different message data coding schemes (refer 3GPP TS 23.038 [2]) | +| 0 | all schemes: as in 3GPP TS 23.038 [2]; if CBM storage is supported, store message to "BM" (or some manufacturer or data coding scheme specific memory) | +| 1 | all schemes: as =0 but send indication if message stored successfully | +| 2 | all schemes: route message to TE unless ME has detected a special routing to somewhere else (e.g. to (U)SIM; an indication may be sent if message stored successfully) | +| 3 | class 3: route message to TE
others: as =1 (if CBM memory storage is supported) | + +: integer type + +- 0 No SMS-STATUS-REPORTs are routed to the TE. +- 1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code: + - +CDS: (PDU mode enabled); or + - +CDS: ,,[],[],[,
,] (text mode enabled) +- 2 If SMS-STATUS-REPORT is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: + - +CDSI: , + +**Table 3.4.1-5: SMS-STATUS-REPORT result code and acknowledgement summary** + +| | result codes and commands | +|------|--------------------------------------------------------------------------| +| 1 | +CDS & +CNMA 1) | +| 2 | +CDSI | +| 1) | acknowledgement command must be sent when +CSMS value equals 1 | + +: integer type + +- 0 TA buffer of unsolicited result codes defined within this command is flushed to the TE when 1...3 is entered (OK response shall be given before flushing the codes). +- 1 TA buffer of unsolicited result codes defined within this command is cleared when 1...3 is entered. + +#### Implementation + +Mandatory when any of the new message indications implemented. + +### 3.4.2 List Messages +CMGL + +**Table 3.4.2-1: +CMGL Action Command Syntax** + +| Command | Possible response(s) | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGL[=] | if text mode (+CMGF=1), command successful and SMS-SUBMITs and/or SMS-DELIVERs:
+CMGL: , , , [], [] [, , ][
+CMGL: , , , [], [] [, , ][...]
if text mode (+CMGF=1), command successful and SMS-STATUS-REPORTs:
+CMGL: , , , , [], [], ,
, [
+CMGL: , , , , [], [], ,
, [...]
if text mode (+CMGF=1), command successful and SMS-COMMANDs:
+CMGL: , , , [
+CMGL: , , , [...]
if text mode (+CMGF=1), command successful and CBM storage:
+CMGL: , , , , , [
+CMGL: , , , , , [...]
otherwise:
+CMS ERROR: | +| +CMGL=? | +CMGL: (list of supported s) | + +#### Description + +Execution command returns messages with status value from message storage to the TE. About text mode parameters in italics, refer command Show Text Mode Parameters +CSDH. If status of the message is 'received unread', status in the storage changes to 'received read'. If listing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +NOTE: If the selected can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STATUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types. TE application can recognize the response format by examining the third response parameter. + +Test command shall give a list of all status values supported by the TA. + +#### Implementation + +Optional. + +### 3.4.3 Read Message +CMGR + +**Table 3.4.3-1: +CMGR Action Command Syntax** + +| Command | Possible response(s) | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGR= | if text mode (+CMGF=1), command successful and SMS-DELIVER:
+CMGR: , , [], [[/, , , , , , ]]
if text mode (+CMGF=1), command successful and SMS-SUBMIT:
+CMGR: , , [] [, , , , , [, , , ]]
if text mode (+CMGF=1), command successful and SMS-STATUS-REPORT:
+CMGR: , , , [], [], [,
, ]]
if text mode (+CMGF=1), command successful and SMS-COMMAND:
+CMGR: , , [, , [], [], [], ]]]
if text mode (+CMGF=1), command successful and CBM storage:
+CMGR: , , , , ,
otherwise:
+CMS ERROR: | +| +CMGR=? | | + +#### Description + +Execution command returns message with location value from message storage to the TE. About text mode parameters in italics, refer command Show Text Mode Parameters +CSDH. If status of the message is 'received unread', status in the storage changes to 'received read'. If reading fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +#### Implementation + +Optional. + +### 3.4.4 New Message Acknowledgement to ME/TA +CNMA + +**Table 3.4.4-1: +CNMA Action Command Syntax** + +| Command | Possible response(s) | +|-----------------------------------------|----------------------| +| if text mode (+CMGF=1):
+CNMA | +CMS ERROR: | +| +CNMA=? | | + +#### Description + +Execution command confirms correct reception of a new message (SMS-DELIVER or SMS-STATUS-REPORT) which is routed directly to the TE (refer command +CNMI table 3.4.1-3 and table 3.4.1-5). This acknowledgement command (causing ME to send RP-ACK to the network) shall be used when +CSMS parameter equals 1. TA shall not send another +CMT or +CDS result code to TE before previous one is acknowledged. + +If ME does not get acknowledgement within required time (network timeout), ME should respond as specified in 3GPP TS 24.011 [6] to the network. ME/TA shall automatically disable routing to TE by setting both and values of +CNMI to zero. + +If command is executed, but no acknowledgement is expected, or some other ME related error occurs, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. + +NOTE: In case that a directly routed message must be buffered in ME/TA (possible when +CNMI parameter equals 0 or 2) or AT interpreter remains too long in a state where result codes cannot be sent to TE (e.g. user is entering a message using +CMGS), acknowledgement (RP-ACK) must be sent to the network without waiting +CNMA command from TE. Later, when buffered result codes are flushed to TE, TE must send +CNMA acknowledgement for each result code. In this way, ME/TA can determine if message should be placed in non-volatile memory and routing to TE disabled (+CNMA not received). Refer command +CNMI for more details how to use parameter reliably. + +#### Implementation + +Mandatory when value 1 of command Select Message Service +CSMS is supported. + +### 3.4.5 Informative Examples + +Message forwarding is done as illustrated in figure 3.4.5-1. Optional +CNMA acknowledgement procedure is not presented. In this example, there is no TA memory for messages and result code buffer is situated in TA. The routing of message waiting indication group (discard message) SMS-DELIVERs equal to class 0 messages, and the routing of message waiting indication group (store message) SMS-DELIVERs equal to class 2 messages. + +![Figure 3.4.5-1: Message receiving procedures. A sequence diagram showing the interaction between ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The diagram illustrates the flow of messages and result codes for different message types and storage locations.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) + +The diagram illustrates the message receiving procedures between ME, TA, and TE. The ME contains 'SM STORAGES' and 'CBM STORAGES'. The TA contains a 'BUFFER'. The TE receives various indications and reports. + +- SMS-DELIVER:** + - If =2, the ME sends a 'new status report indication +CDSI' to the TE. + - If =1 or =2 (class 2) or =3 (class not 3), the ME sends a 'new MT SM indication +CMTI' to the TE. + - If =0 or =1 or =2 (class 2) or =3 (class not 3), the message is stored in SM STORAGES. + - If =2 (class not 2) or =3 (class 3), the message is buffered in the TA. +- SMS-STATUS-REPORT:** + - If =0 or =2, the message is stored in SM STORAGES. + - If =1, the message is buffered in the TA and a 'status report +CDS' is sent to the TE. +- CBM with allowed message identifier and data coding scheme (refer +CSCB):** + - If =2 or =3 (class 3), the message is buffered in the TA and a 'new CBM +CBM' is sent to the TE. + - If =0 or =1 or =3 (class not 3), the message is stored in CBM STORAGES. + - If =1 or =3 (class not 3), the message is buffered in the TA and a 'new CBM indication +CBM' is sent to the TE. + +Figure 3.4.5-1: Message receiving procedures. A sequence diagram showing the interaction between ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The diagram illustrates the flow of messages and result codes for different message types and storage locations. + +Figure 3.4.5-1: Message receiving procedures + +Setting new message indications: + +``` +AT+CNMI=? (query new message unsolicited result code modes) ++CNMI: (0-2), (0-3), (0-3), (0,1), (0,1) +OK +AT+CNMI=2,1,0,1,0 (send SM and status report indications to TE when TA in command mode, otherwise buffer) +OK +``` + +In this example, the TA is set so that it should send an unsolicited result code +CMTI: , to the TE when a new SMS-DELIVER is received from the network and stored successfully to storage , and an unsolicited result code +CDS: . . . when a SMS-STATUS-REPORT is received. These result codes are routed to the TE when TA is in command mode, but buffered when in on-line data mode. Now, if new SM is received, it can be read as follows (text mode with no detailed header information; GSM 7 bit default alphabet used in message body): + +``` ++CMTI: "ME", 2 (new message received in index 2) +AT+CMGR=2 (read the message) ++CMGR: "REC UNREAD", "+358507654321", "Mr. Jones", "95/07/03, 17:38:15+04" +This is the Mr. Jones testing +OK +``` + +In the next example all messages of storage are listed (text mode with no detailed header information; GSM 7 bit default alphabet used in message bodies): + +``` + +AT+CMGL="ALL" (read all SMs) ++CMGL: 1,"REC READ","+358501234567","Mr. Smith","95/07/03,17:45:03+04" +This is the body of the message. ++CMGL: 2,"STO UNSENT","+358501234567","Mr. Smith", +This is the body of the reply. +OK + +``` + +The next example shows a method to read new CBMs received from the network (text mode; GSM 7 bit default alphabet used in message bodies): + +``` + +AT+CNMI=2,,2,,0 (CBMs will be sent to the TE) +OK +AT+CPMS="BM";+CMGL (select CBM memory for reading; list all unread CBMs) ++CMGL: 1,"REC UNREAD",100,40,1,3 (first page of three page weather information) +Weather in Finland 3rd of July 1995 ++CMGL: 2,"REC UNREAD",100,40,2,3 (second page of three page weather information) +Helsinki: cloudy, snow storms, -20 degrees Celsius, wind -14 m/s NE ++CMGL: 3,"REC UNREAD",100,40,3,3 (third page of three page weather information) +Tampere: sunny, 40 degrees Celsius, wind 1 m/s SW +OK + +``` + +## 3.5 Message Sending and Writing Commands + +### 3.5.1 Send Message +CMGS + +**Table 3.5.1-1: +CMGS Action Command Syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| if text mode (+CMGF=1):
+CMGS=[, ]
text is entered | if text mode (+CMGF=1) and sending successful:
+CMGS: [, ]
if sending fails:
+CMS ERROR: | +| +CMGS=? | | + +#### Description + +Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +#### Description + +Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value is returned to the TE on successful message delivery. Value can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +- entered text (3GPP TS 23.040 [3] TP-Data-Unit) is sent to address and all current settings (refer Set Text Mode Parameters +CSMP and Service Centre Address +CSCA) are used to construct the actual PDU in ME/TA. +- the TA shall send a four character sequence (IRA 13, 10, 62, 32) after command line is terminated with ; after that text can be entered from TE to ME/TA. +- the DCD signal shall be in ON state while text is entered. +- the echoing of entered characters back from the TA is controlled by V.25ter echo command E. +- the entered text should be formatted as follows: + - if (set with +CSMP) indicates that 3GPP TS 23.038 [2] GSM 7 bit default alphabet is used and indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is not set: + +- if TE character set other than "HEX" (refer command Select TE Character Set +CSCS in 3GPP TS 27.007 [9]): ME/TA converts the entered text into the GSM 7 bit default alphabet according to rules of Annex A; backspace can be used to delete last character and carriage returns can be used (previously mentioned four character sequence shall be sent to the TE after every carriage return entered by the user); +- if TE character set is "HEX": the entered text should consist of two IRA character long hexadecimal numbers which ME/TA converts into the GSM 7 bit default alphabet characters. (e.g. 17 (IRA 49 and 55) will be converted to character II (GSM 7 bit default alphabet 23)). +- if indicates that 8-bit or UCS2 data coding scheme is used or indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is set: the entered text should consist of two IRA character long hexadecimal numbers which ME/TA converts into 8-bit octet (e.g. two characters 2A (IRA 50 and 65) will be converted to an octet with integer value 42). +- sending can be cancelled by giving character (IRA 27). +- (IRA 26) must be used to indicate the ending of the message body. + +#### Implementation + +Optional. + +### 3.5.2 Send Message from Storage +CMSS + +**Table 3.5.2-1: +CMSS Action Command Syntax** + +| Command | Possible response(s) | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| +CMSS=[, [, ]] | if text mode (+CMGF=1) and sending successful:
+CMSS: [, ]
if sending fails:
+CMS ERROR: | +| +CMSS=? | | + +#### Description + +Execution command sends message with location value from preferred message storage to the network (SMS-SUBMIT or SMS-COMMAND). If new recipient address is given for SMS-SUBMIT, it shall be used instead of the one stored with the message. Reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +#### Implementation + +Optional. + +### 3.5.3 Write Message to Memory +CMGW + +**Table 3.5.3-1: +CMGW Action Command Syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| if text mode (+CMGF=1):
+CMGW[=[, [, ]]]
text is entered | +CMGW:
+CMS ERROR: | +| +CMGW=? | | + +#### Description + +Execution command stores message (either SMS-DELIVER or SMS-SUBMIT) to memory storage . Memory location of the stored message is returned. By default message status will be set to 'stored unsent', but parameter allows also other status values to be given. The entering of text is done similarly as specified in command Send Message +CMGS. If writing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +NOTE: SMS-COMMANDs and SMS-STATUS-REPORTs can not be stored in text mode. + +#### Implementation + +Optional. + +### 3.5.4 Delete Message +CMGD + +**Table 3.5.4-1: +CMGD Action Command Syntax** + +| Command | Possible response(s) | +|--------------------------------|-------------------------------------------------------------------------------| +| +CMGD=
[, ] | +CMS ERROR: | +| +CMGD=? | +CMGD: (list of supported
s) [, (list of
supported s) ] | + +#### Description + +Execution command deletes message from preferred message storage location . If is present and not set to 0 then the ME shall ignore and follow the rules for shown below. If deleting fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +Test command shows the valid memory locations and optionally the supported values of . + +: integer type, indicating multiple message deletion request as follows: + +- 0 Delete the message specified in +- 1 Delete all read messages from preferred message storage, leaving unread messages and stored mobile originated messages (whether sent or not) untouched +- 2 Delete all read messages from preferred message storage and sent mobile originated messages, leaving unread messages and unsent mobile originated messages untouched +- 3 Delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving unread messages untouched. +- 4 Delete all messages from preferred message storage including unread messages. + +#### Implementation + +Optional. + +### 3.5.5 Send Command +CMGC + +**Table 3.5.5-1: +CMGC Action Command Syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| if text mode (+CMGF=1):
+CMGC=, [, [, [, [, ] ] ] ]
text is entered | if text mode (+CMGF=1) and
sending successful:
+CMGC: [, ]
if sending fails:
+CMS ERROR: | + +| | | +|---------|--| +| +CMGC=? | | +|---------|--| + +#### Description + +Execution command sends a command message from a TE to the network (SMS-COMMAND). The entering of text (3GPP TS 23.040 [3] TP-Command-Data) is done similarly as specified in command Send Message +CMGS, but the format is fixed to be a sequence of two IRA character long hexadecimal numbers which ME/TA converts into 8-bit octets (refer +CMGS). Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +#### Implementation + +Optional. + +### 3.5.6 More Messages to Send +CMMS + +**Table 3.5.6-1: +CMMS Parameter Command Syntax** + +| Command | Possible response(s) | +|-------------|---------------------------------| +| +CMMS=[] | | +| +CMMS? | +CMMS: | +| +CMMS=? | +CMMS: (list of supported s) | + +#### Description + +Set command controls the continuity of SMS relay protocol link. When feature is enabled (and supported by network) multiple messages can be sent much faster as link is kept open. + +Test command returns supported values as a compound value. + +#### Defined Values + +: integer type + +- 0 disable +- 1 keep enabled until the time between the response of the latest message send command (+CMGS, +CMSS, etc.) and the next send command exceeds 1-5 seconds (the exact value is up to ME implementation), then ME shall close the link and TA switches automatically back to 0 +- 2 enable (if the time between the response of the latest message send command and the next send command exceeds 1-5 seconds (the exact value is up to ME implementation), ME shall close the link but TA shall not switch automatically back to =0) + +#### Implementation + +Optional. + +### 3.5.7 Informative Examples + +Figure 3.5.7-1 is an example of a TE-TA-ME setup when messages are sent to network or stored to ME. The volatile memory may as well be in the ME, or a non-volatile memory may be used instead when constructing messages. + +![Sequence diagram illustrating Message service send and write procedures between ME, TA, and TE. The diagram shows four message types: SMS-SUBMIT, SMS-SUBMIT, SMS-SUBMIT, and SMS-COMMAND. The ME sends these to the TA. The TA interacts with SM STORAGES and volatile memory. SM STORAGES sends write +CMGW to the TA. Volatile memory adds text mode parameters (+CSMP) and SMSC address (optionally add SMSC address) in text mode, or add SMSC address (optional in PDU mode) in PDU mode. The TA then sends the message to the TE: send from storage +CMSS, text mode send +CMGS and write +CMGW, PDU mode send +CMGS and write +CMGW, or send command +CMGC.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Sequence diagram illustrating Message service send and write procedures between ME, TA, and TE. The diagram shows four message types: SMS-SUBMIT, SMS-SUBMIT, SMS-SUBMIT, and SMS-COMMAND. The ME sends these to the TA. The TA interacts with SM STORAGES and volatile memory. SM STORAGES sends write +CMGW to the TA. Volatile memory adds text mode parameters (+CSMP) and SMSC address (optionally add SMSC address) in text mode, or add SMSC address (optional in PDU mode) in PDU mode. The TA then sends the message to the TE: send from storage +CMSS, text mode send +CMGS and write +CMGW, PDU mode send +CMGS and write +CMGW, or send command +CMGC. + +Figure 3.5.7-1: Message service send and write procedures + +An example of sending a GSM 7 bit default alphabet message in text mode and a SMS-STATUS-REPORT is wanted: + +``` +AT+CNMI? (check that status reports are routed to TE) ++CNMI: 2,1,0,1,0 +OK +AT+CSMP=49,167,0,0 (status report wanted; otherwise default settings) +OK +AT+CMGS="+358501234567" (start editing a message) +> This the first line. (edit first line and press carriage return) +> This is the last line.^Z (edit second line and send message by pressing control-Z) ++CMGS: 10 (success: message reference 10 returned from SMSC) +OK ++CDS: 2,10,"+358501234567",145,"95/07/04/13:12:14+04", +"95/07/04/13:12:20+04",0 (status report of successful message delivery received) +``` + +Storing an unsent message in memory, sending it from there, and deleting it: + +``` +AT+CPMS? (check memory settings) ++CPMS: "ME",4,10,"ME",4,10,"ME",4,10 +OK +AT+CMGW="9501231234" (write message) +> This is the message body^Z ++CMGW: 7 (index number in storage returned) +OK +AT+CMSS=7 (send from storage) ++CMSS: 12 (success: reference value 12 sent from SC) +OK +AT+CMGD=7 (delete message) +OK +``` + +# 4 PDU Mode + +## 4.0 General + +The PDU mode uses the same commands and responses as the Text Mode described in clause 3. However, the following commands and responses have a different format. In the PDU mode, a complete SMS Message including all header information is passed as a binary string. This binary string is composed of hexadecimal IA5 characters as defined in clause 3 above under "Message Data Parameters". + +## 4.1 List Messages +CMGL + +Table 4.1-1: +CMGL Action Command Syntax + +| Command | Possible response(s) | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGL[=] | if PDU mode (+CMGF=0) and command successful:
+CMGL: , , [],
[+CMGL:, , [],
[...]]
otherwise:
+CMS ERROR: | +| +CMGL=? | +CMGL: (list of supported s) | + +### Description + +Execution command returns messages with status value from preferred message storage to the TE. Entire data units are returned. If status of the message is 'received unread', status in the storage changes to 'received read'. If listing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +Test command shall give a list of all status values supported by the TA. + +### Implementation + +Optional. + +## 4.2 Read Message +CMGR + +Table 4.2-1: +CMGR Action Command Syntax + +| Command | Possible response(s) | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGR= | if PDU mode (+CMGF=0) and command successful:
+CMGR: , [],
otherwise:
+CMS ERROR: | +| +CMGR=? | | + +### Description + +Execution command returns message with location value from preferred message storage to the TE. Status of the message and entire message data unit is returned. If status of the message is 'received unread', status in the storage changes to 'received read'. If reading fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +### Implementation + +Optional. + +## 4.3 Send Message +CMGS + +Table 4.3-1: +CMGS Action Command Syntax + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| if PDU mode (+CMGF=0):
+CMGS=
PDU is given | if PDU mode (+CMGF=0) and sending successful:
+CMGS: [, ]
if sending fails:
+CMS ERROR: | +| +CMGS=? | | + +### Description + +Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +- must indicate the number of octets coded in the TP layer data unit to be given (i.e. SMSC address octets are excluded). +- the TA shall send a four character sequence (IRA 13, 10, 62, 32) after command line is terminated with ; after that PDU can be given from TE to ME/TA. +- the DCD signal shall be in ON state while PDU is given. +- the echoing of given characters back from the TA is controlled by V.25ter echo command E. +- the PDU shall be hexadecimal format (similarly as specified for ) and given in one line; ME/TA converts this coding into the actual octets of PDU. +- when the length octet of the SMSC address (given in the PDU) equals zero, the SMSC address set with command Service Centre Address +CSCA is used; in this case the SMSC Type-of-Address octet shall not be present in the PDU, i.e. TPDU starts right after SMSC length octet. +- sending can be cancelled by giving character (IRA 27). +- (IRA 26) must be used to indicate the ending of PDU. + +### Implementation + +Optional. + +## 4.4 Write Message to Memory +CMGW + +Table 4.4-1: +CMGW Action Command Syntax + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------|-------------------------------------| +| if PDU mode (+CMGF=0):
+CMGW=[, ] PDU is given | +CMGW:
+CMS ERROR: | +| +CMGW=? | | + +### Description + +Execution command stores a message to memory storage . Memory location of the stored message is returned. By default message status will be set to 'stored unsent', but parameter allows also other status values to be given. (ME/TA manufacturer may choose to use different default values for different message types.) The entering of PDU is done similarly as specified in command Send Message +CMGS. If writing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +### Implementation + +Optional. + +## 4.5 Send Command +CMGC + +Table 4.5-1: +CMGC Action Command Syntax + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| if PDU mode (+CMGF=0):
+CMGC=
PDU is given | if PDU mode (+CMGF=0) and sending successful:
+CMGC: [, ]
if sending fails:
+CMS ERROR: | +| +CMGC=? | | + +### Description + +Execution command sends a command message from a TE to the network (SMS-COMMAND). The entering of PDU is done similarly as specified in command Send Message +CMGS. Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +### Implementation + +Optional. + +## 4.6 New Message Acknowledgement to ME/TA +CNMA + +**Table 4.6-1: +CNMA Action Command Syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| if PDU mode (+CMGF=0):
+CNMA[=[, [
PDU is given ]]] | +CMS ERROR: | +| +CNMA=? | if PDU mode (+CMGF=0):
+CNMA: (list of supported s) | + +### Description + +Execution command confirms reception of a new message (SMS-DELIVER or SMS-STATUS-REPORT) which is routed directly to the TE (refer command +CNMI table 3.4.1-3 and table 3.4.1-5). This acknowledgement command shall be used when +CSMS parameter equals 1. In PDU mode, it is possible to send either positive (RP-ACK) or negative (RP-ERROR) acknowledgement to the network. Parameter defines which one will be sent. Optionally (when is greater than zero) an acknowledgement TPDU (SMS-DELIVER-REPORT for RP-ACK or RP-ERROR) may be sent to the network. The entering of PDU is done similarly as specified in command Send Message +CMGS, except that the format of is used instead of (i.e. SMSC address field is not present). PDU shall not be bounded by double quotes. TA shall not send another +CMT or +CDS result code to TE before previous one is acknowledged. + +If ME does not get acknowledgement within required time (network timeout), ME should respond as specified in 3GPP TS 24.011 [6] to the network. ME/TA shall automatically disable routing to TE by setting both and values of +CNMI to zero. + +If command is executed, but no acknowledgement is expected, or some other ME related error occurs, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. + +**NOTE:** In case that a directly routed message must be buffered in ME/TA (possible when +CNMI parameter equals 0 or 2) or AT interpreter remains too long in a state where result codes cannot be sent to TE (e.g. user is entering a message using +CMGS), acknowledgement (RP-ACK) must be sent to the network without waiting +CNMA command from TE. Later, when buffered result codes are flushed to TE, TE must send +CNMA[=0] acknowledgement for each result code. In this way, ME/TA can determine if message should be placed in non-volatile memory and routing to TE disabled (+CNMA[=0] not received). Refer command +CNMI for more details how to use parameter reliably. + +Test command returns a list of supported values. If the only value supported is 0, the device does not support sending of TPDU. + +### Defined Values + +: integer type + +0 command operates similarly as defined for the text mode + +- 1 send RP-ACK (or buffered result code received correctly) +- 2 send RP-ERROR (if PDU is not given, ME/TA shall send SMS-DELIVER-REPORT with 3GPP TS 23.040 [3] TP-FCS value set to 'FF' (unspecified error cause)) + +### Implementation + +Mandatory when value 1 of command Select Message Service +CSMS is supported. + +## 4.7 Send Message from Storage +CMSS + +**Table 4.7-1: +CMSS Action Command Syntax** + +| Command | Possible response(s) | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| +CMSS=[, [, ]] | if PDU mode (+CMGF=0) and sending successful:
+CMSS: [, ]
if sending fails:
+CMS ERROR: | +| +CMSS=? | | + +### Description + +Execution command sends message with location value from message storage to the network (SMS-SUBMIT or SMS-COMMAND). If new recipient address is given for SMS-SUBMIT, it shall be used instead of the one stored with the message. Reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +### Implementation + +Optional. + +# Annex A (normative): Character Set Conversions for SMS Text Mode + +The following conversions to and from 3GPP TS 23.038 [2] GSM 7 bit default alphabet are defined: + +| TE char set | bits/char | Commands | +|----------------------------|-----------|-------------------------| +| PC Code Page 437 | 8 | +CMGF=1;+CSCS="PCCP437" | +| PC Danish/Norwegian | 8 | +CMGF=1;+CSCS="PCDN" | +| ISO 8859 Latin 1 | 8 | +CMGF=1;+CSCS="8859-1" | +| IRA | 7 | +CMGF=1;+CSCS="IRA" | +| GSM 7 bit default alphabet | 7 | +CMGF=1;+CSCS="GSM" | + +The tables below show which GSM 7 bit default alphabet value corresponds to the 7 or 8 bit value of external character set. The TE character set value is computed by adding column value, 00H through F0H (70H for 7 bits/char), with the row value (00H through 0FH). All values are in hexadecimal, but the H suffix is not used. When text mode is implemented, it is mandatory for a TA to have at least one conversion which include the conversion table of IRA (e.g. PC Code Page 437 does). Additional conversions can be defined by manufacturers. It is manufacturer specific if the TE set is actually converted to GSM 7 bit default alphabet set in the TA or in the ME, and if the TE set is converted to a ME specific set in the TA before converting it to GSM 7 bit default alphabet set when message is sent to the network. It is recommended that characters which cannot be converted to GSM 7 bit default alphabet set are deleted. + +Conversion from IRA to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | +|----|-----|----|----|----|----|----|----|----| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | +| 05 | - | - | 25 | 35 | 45 | 55 | 65 | 75 | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | +| 0D | CR- | - | 2D | 3D | 4D | - | 6D | - | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | + +Conversion from PCCP437 (PC-8 Code Page 437) to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | A0 | B0 | C0 | D0 | E0 | F0 | +|----|----|----|----|----|----|----|----|----|-----------------|-----------------|------------------|----|----|----|----|----| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | 09 | 1F | 61 10 | - | - | - | - | - | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | 7E | 1D | 69 11 | - | - | - | 1E | - | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | 05 | 1C | 6F 12 | - | - | - | 13 | - | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | 61 1 | 6F 7 | 75 13 | - | - | - | - | - | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | 7B | 7C | 7D | - | - | - | 18 | - | +| 05 | - | 5F | 25 | 35 | 45 | 55 | 65 | 75 | 7F | 08 | 5D | - | - | - | - | - | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | 0F | 75 8 | - | - | - | - | - | - | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | 09 2 | 06 | - | - | - | - | - | - | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | 65 3 | 79 9 | 60 | - | - | - | 12 | - | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | 65 4 | 5C | - | - | - | - | 19 | - | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | 04 | 5E | - | - | - | - | 15 | - | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | 69 5 | - | - | - | - | - | - | - | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | 69 6 | 01 | - | - | - | - | - | - | +| 0D | CR | - | 2D | 3D | 4D | - | 6D | - | 07 | 03 | 40 | - | - | - | - | - | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | 5B | - | - | - | - | - | - | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | 0E | - | - | - | - | - | - | - | + +1 : â ⇒ a    2 : ç ⇒ Ç    3 : ê ⇒ e    4 : ë ⇒ e    5 : ï ⇒ i +6 : î ⇒ i    7 : ô ⇒ o    8 : û ⇒ u    9 : ÿ ⇒ y    10 : á ⇒ a +11 : í ⇒ i    12 : ó ⇒ o    13 : ú ⇒ u + +Conversion from PCDN (PC-8 Danish/ Norwegian) to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | A0 | B0 | C0 | D0 | E0 | F0 | +|----|----|----|----|----|----|----|----|----|-----------------|-----------------|------------------|----|----|----|----|----| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | 09 | 1F | 61 10 | - | - | - | - | - | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | 7E | 1D | 69 11 | - | - | - | 1E | - | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | 05 | 1C | 6F 12 | - | - | - | 13 | - | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | 61 1 | 6F 7 | 75 13 | - | - | - | - | - | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | 7B | 7C | 7D | - | - | - | 18 | - | +| 05 | - | 5F | 25 | 35 | 45 | 55 | 65 | 75 | 7F | 08 | 5D | - | - | - | - | - | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | 0F | 75 8 | - | - | - | - | - | - | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | 09 2 | 06 | - | - | - | - | - | - | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | 65 3 | 79 9 | 60 | - | - | - | 12 | - | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | 65 4 | 5C | - | - | - | - | 19 | - | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | 04 | 5E | - | - | - | - | 15 | - | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | 69 5 | 0C | - | - | - | - | - | - | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | 69 6 | 01 | - | - | - | - | - | - | +| 0D | CR | - | 2D | 3D | 4D | - | 6D | - | 07 | 0B | 40 | - | - | - | - | - | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | 5B | - | - | - | - | - | - | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | 0E | - | - | - | - | - | - | - | + +1 : â ⇒ a    2 : ç ⇒ Ç    3 : ê ⇒ e    4 : ë ⇒ e    5 : ï ⇒ i +6 : î ⇒ i    7 : ô ⇒ o    8 : û ⇒ u    9 : ÿ ⇒ y    10 : á ⇒ a +11 : í ⇒ i    12 : ó ⇒ o    13 : ú ⇒ u + +Conversion from 8859-1 (ISO 8859 Latin 1) to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | A0 | B0 | C0 | D0 | E0 | F0 | +|----|----|----|----|----|----|----|----|----|----|----|----|----|------------------|------------------|------------------|------------------| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | - | - | - | - | 41 1 | - | 7F | - | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | - | - | 40 | - | 41 2 | 5D | 61 20 | 7D | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | - | - | - | - | 41 3 | 4F 12 | 61 21 | 08 | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | - | - | 01 | - | 41 4 | 4F 13 | 61 22 | 6F 29 | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | - | - | 24 | - | 5B | 4F 14 | 7B | 6F 30 | +| 05 | - | - | 25 | 35 | 45 | 55 | 65 | 75 | - | - | 03 | - | 0E | 4F 15 | 0F | 6F 31 | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | - | - | - | - | 1C | 5C | 1D | 7C | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | - | - | 5F | - | 09 | - | 09 23 | - | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | - | - | - | - | 45 5 | 0B | 04 | 0C | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | - | - | - | - | 1F | 55 16 | 05 | 06 | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | - | - | - | - | 45 6 | 55 17 | 65 24 | 75 32 | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | - | - | - | - | 45 7 | 55 18 | 65 25 | 75 33 | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | - | - | - | - | 49 8 | 5E | 07 | 7E | +| 0D | CR | - | 2D | 3D | 4D | - | 6D | - | - | - | - | - | 49 9 | 59 19 | 69 26 | 79 34 | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | - | - | - | - | 49 10 | - | 69 27 | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | - | - | - | 60 | 49 11 | 1E | 69 28 | 79 35 | + +1 : À ⇒ A    2 : Á ⇒ A    3 : Â ⇒ A    4 : Ã ⇒ A    5 : È ⇒ E +6 : Ê ⇒ E    7 : Ë ⇒ E    8 : Ì ⇒ I    9 : Í ⇒ I    10 : Î ⇒ I +11 : Ï ⇒ I    12 : Ò ⇒ O    13 : Ó ⇒ O    14 : Ô ⇒ O    15 : Õ ⇒ O +16 : Ù ⇒ U    17 : Ú ⇒ U    18 : Û ⇒ U    19 : Ý ⇒ Y    20 : á ⇒ a +21 : â ⇒ a    22 : ã ⇒ a    23 : ç ⇒ Ç    24 : ê ⇒ e    25 : ë ⇒ e +26 : í ⇒ i    27 : î ⇒ i    28 : ï ⇒ i    29 : ó ⇒ o    30 : ô ⇒ o +31 : õ ⇒ o    32 : ú ⇒ u    33 : û ⇒ u    34 : ý ⇒ y    35 : ÿ ⇒ y + +Conversions from GSM 7 bit default alphabet to above character sets are otherwise straightforward, but no conversions of the characters listed below tables are applied. + +Character conversion when a national language locking shift table as defined in 3GPP TS 23.038 [2] is used, is outside the scope of this specification. + +# --- Annex B (informative): Example of processing a data block + +## B.1 Example state diagrams for the block receiver + +The state diagrams on the following two pages show how the receiver component at the block level could work. In this example the received octets are processed in two stages. + +Stage 1 is a low level function which detects the unique start and end markers, and removes any stuffing octets. The results of this stage are passed to stage 2. Any unexpected octet value after a DLE will be indicated as 'abort'. + +Stage 2 assembles the message content and the BCS octets, using octets passed from stage 1 and the 'start' and 'end' indications. A 'start' will always reset the process to state 1 from any state. An 'abort' will always cause a return to state 0 where a 'start' will be awaited. When an 'end' is received in state 1, the following two octets are checked as the BCS. If the BCS is correct, the message content is passed to another stage of the receiver for processing of the message content. + +## --- B.2 Example of coding and decoding a data block + +The last page of this annex shows the coding of an example message at a transmitter, and the decoding stages at a receiver which has the two stages of processing as described above. + +In this example, the message content and the BCS both contain an octet with a value of 10 hex. Therefore the message as transmitted over the interface has additional stuffing octets (00 hex) inserted after these octets. The receiver first detects the start and end markers, and removes the stuffing octets. Finally the BCS is checked. + +### EXAMPLE STATE DIAGRAMS FOR THE BLOCK RECEIVER + +The block receiver can be considered as two stages. Stage 1 detects start and end markers, and removes stuffing characters. Stage 2 assembles the received message and checks the BCS. + +![Block diagram showing the flow from Octets from the DTE/DCE interface through STAGE 1 and STAGE 2 to produce Message blocks. STAGE 1 output is 'Octets, with separate Start, End and Abort indications.'](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +``` +graph LR; Input[Octets from the DTE/DCE interface] --> S1[STAGE 1]; S1 -- "Octets, with separate Start, End and Abort indications." --> S2[STAGE 2]; S2 --> Output[Message blocks]; +``` + +Block diagram showing the flow from Octets from the DTE/DCE interface through STAGE 1 and STAGE 2 to produce Message blocks. STAGE 1 output is 'Octets, with separate Start, End and Abort indications.' + +### STATE TRANSITIONS IN STAGE 1 + +![State transition diagram for Stage 1. States: 0 Idle, 1 Wait for STX, ETX or NUL. Transitions from Idle: DLE to state 1, any other octet n to state 0 via octet = n. Transitions from state 1: STX to state 0 via 'Start', NUL to state 0 via octet = DLE, ETX to state 0 via 'End', any other octet to state 0 via 'Abort'. State 1 also has a self-loop for DLE.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +``` +stateDiagram-v2; [*] --> 0 : Idle; 0 --> 1 : DLE; 0 --> 0 : any other octet n, octet = n; 1 --> 1 : DLE; 1 --> 0 : STX, 'Start'; 1 --> 0 : NUL, octet = DLE; 1 --> 0 : ETX, 'End'; 1 --> 0 : any other octet, 'Abort'; +``` + +State transition diagram for Stage 1. States: 0 Idle, 1 Wait for STX, ETX or NUL. Transitions from Idle: DLE to state 1, any other octet n to state 0 via octet = n. Transitions from state 1: STX to state 0 via 'Start', NUL to state 0 via octet = DLE, ETX to state 0 via 'End', any other octet to state 0 via 'Abort'. State 1 also has a self-loop for DLE. + +Figure B.1 + +![A complex flowchart diagram showing a sequence of operations with circular nodes labeled C, 1, 2, 3, and a diamond decision node labeled R. Rectangular boxes represent processes between nodes. Side branches lead to nodes labeled 7 or C. The text is heavily distorted.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + + graph TD + Start((C)) --> P1[...] + P1 --> N1((1)) + N1 --> P2[...] + N1 --> S1((7)) + P2 --> N2((2)) + N2 --> P3[...] + N2 --> S2((7)) + P3 --> N3((3)) + N3 --> P4[...] + N3 --> S3((7)) + P4 --> D1{R} + D1 --> P5[...] + P5 --> End((C)) + +``` + +The diagram is a flowchart representing a technical procedure, likely a signaling flow in a telecommunications network (3GPP). It features: + +- Top Node:** A circle labeled 'C' with 'HLR' below it. +- Sequential Nodes:** Circular nodes numbered '1', '2', and '3' representing stages in the process. +- Process Boxes:** Rectangular boxes between the numbered nodes containing distorted text. +- Side Branches:** Several branches lead to circular nodes containing the number '7' or the letter 'C'. +- Decision Point:** A diamond-shaped node near the bottom containing 'R' and other distorted characters. +- Terminal Node:** A final circle labeled 'C' at the bottom. + +A complex flowchart diagram showing a sequence of operations with circular nodes labeled C, 1, 2, 3, and a diamond decision node labeled R. Rectangular boxes represent processes between nodes. Side branches lead to nodes labeled 7 or C. The text is heavily distorted. + +**Figure B.2** + +### **Example of coding / decoding a message at the DTE/DCE interface** + +![](376f80eb8a41369e87da63a0210d173e_img.jpg) + +Example message to be sent + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +↓ +Calculate BCS + +BCS prepared + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +| | | +|-----|-----| +| BCS | | +| MSB | LSB | +| FFH | 10H | + +↓ +Insert stuffing octets, and add start & end markers + +Message as transmitted + +| | | | | | | | | | | | | | | +|--------------|-----|-------------------|-----|-----|-----|-----|-----|-----|------------|-----|-----|-----|-----| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE | STX | 00H | 10H | NUL | 20H | 30H | 40H | 50H | DLE | ETX | FFH | 10H | NUL | +| 10H | 02H | | | 00H | | | | | 10H | 03H | | | 00H | + +↓ +Message transferred over DTE/DCE interface + +\* = stuffing octet + +Message as received (no errors) + +| | | | | | | | | | | | | | | +|--------------|-----|-------------------|-----|-----|-----|-----|-----|-----|------------|-----|-----|-----|-----| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE | STX | 00H | 10H | NUL | 20H | 30H | 40H | 50H | DLE | ETX | FFH | 10H | NUL | +| 10H | 02H | | | 00H | | | | | 10H | 03H | | | 00H | + +↓ +Detect start & end markers, and remove stuffing octets + +Output from receiver stage 1 + +| | | | | | | | | +|---------|-----|-----|-----|-----|-----|-----|-------| +| 'Start' | 00H | 10H | 20H | 30H | 40H | 50H | 'End' | +|---------|-----|-----|-----|-----|-----|-----|-------| + +| | | +|-----|-----| +| BCS | | +| MSB | LSB | +| FFH | 10H | + +↓ +Check BCS + +Output from receiver stage 2 + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +Figure B.3 + +### EXAMPLE STATE DIAGRAMS FOR THE BLOCK RECEIVER + +The block receiver can be considered as two stages. Stage 1 detects start and end markers, and removes stuffing characters. Stage 2 assembles the received message and checks the BCS. + +![Block diagram of the block receiver stages.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +A block diagram showing the flow of data through two stages. An arrow labeled "Octets from the DTE/DCE interface" points to a box labeled "STAGE 1". An arrow labeled "Octets, with separate Start, End and Abort indications." points from "STAGE 1" to a box labeled "STAGE 2". An arrow labeled "Message blocks" points out from "STAGE 2". + +Block diagram of the block receiver stages. + +### STATE TRANSITIONS IN STAGE 1 + +![State transition diagram for Stage 1 of the block receiver.](4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg) + +A state transition diagram for Stage 1. It starts with an initial state "0 Idle" (oval). A transition labeled "DLE" leads to state "1 Wait for STX, ETX or NUL" (oval). From state "1", a transition labeled "any other octet n" leads to a decision box "octet = n", which then leads to state "0" (oval). From state "1", four transitions lead to output boxes: "STX" leads to "'Start'", "NUL" leads to "octet = DLE", "ETX" leads to "'End'", and "any other octet" leads to "'Abort'". Each output box then leads to state "0" (oval). A self-loop labeled "DLE" is shown on state "1". + +State transition diagram for Stage 1 of the block receiver. + +Figure B.4 + +![A complex flowchart diagram with multiple decision nodes and process steps, heavily obscured by black redaction bars. The diagram includes oval nodes, rectangular process boxes, and a diamond decision node at the bottom.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +The diagram is a flowchart that has been almost entirely redacted with black bars. The visible structure is as follows: + +- Start Node:** An oval node at the top containing a 'C' and 'H'. +- Process Node:** A rectangular box below the start node, containing two redacted lines of text. +- Decision Node 1:** An oval node below the first process box, containing a '1' and 'and'. It has three outgoing paths: + - A left path leading to a rectangular box with two redacted lines, which then leads to a small circle containing a '7'. + - A middle path leading down to the next node. + - A right path leading to a rectangular box containing two redacted lines, which then leads to another rectangular box containing two redacted lines, which finally leads to a small circle containing a '7'. +- Decision Node 2:** An oval node below the middle path of Decision Node 1, containing '2' and 'value'. It has three outgoing paths: + - A left path leading to a rectangular box with two redacted lines, which then leads to a small circle containing a '7'. + - A middle path leading down to a rectangular box containing two redacted lines. + - A right path leading to a small circle containing a 'C'. +- Decision Node 3:** An oval node below the middle path of Decision Node 2, containing '3' and 'value'. It has three outgoing paths: + - A left path leading to a rectangular box with two redacted lines, which then leads to a small circle containing a '7'. + - A middle path leading down to a rectangular box containing two redacted lines. + - A right path leading to a small circle containing a 'C'. +- Decision Node 4:** A diamond-shaped node below the middle path of Decision Node 3, containing 'value' and 'R'. It has two outgoing paths: + - A right path leading to a small circle containing a 'C'. + - A bottom path leading to a rectangular box containing two redacted lines, which then leads to a small circle containing a 'C'. + +A complex flowchart diagram with multiple decision nodes and process steps, heavily obscured by black redaction bars. The diagram includes oval nodes, rectangular process boxes, and a diamond decision node at the bottom. + +Figure B.5 + +### **Example of coding / decoding a message at the DTE/DCE interface** + +![](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +Example message to be sent + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +↓ +Calculate BCS + +BCS prepared + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +| | | +|------------|-----| +| BCS
MSB | LSB | +| FFH | 10H | + +↓ +Insert stuffing octets, and add start & end markers + +Message as transmitted + +| | | | | | | | | | | | | | | +|--------------|------------|-------------------|-----|------------|-----|-----|-----|-----|------------|------------|-----|-----|------------| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE
10H | STX
02H | 00H | 10H | NUL
00H | 20H | 30H | 40H | 50H | DLE
10H | ETX
03H | FFH | 10H | NUL
00H | + +↓ +Message transferred over DTE/DCE interface + +\* = stuffing octet + +Message as received (no errors) + +| | | | | | | | | | | | | | | +|--------------|------------|-------------------|-----|------------|-----|-----|-----|-----|------------|------------|-----|-----|------------| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE
10H | STX
02H | 00H | 10H | NUL
00H | 20H | 30H | 40H | 50H | DLE
10H | ETX
03H | FFH | 10H | NUL
00H | + +↓ +Detect start & end markers, and remove stuffing octets + +Output from receiver stage 1 + +| | | | | | | | | +|---------|-----|-----|-----|-----|-----|-----|-------| +| 'Start' | 00H | 10H | 20H | 30H | 40H | 50H | 'End' | +|---------|-----|-----|-----|-----|-----|-----|-------| + +| | | +|------------|-----| +| BCS
MSB | LSB | +| FFH | 10H | + +↓ +Check BCS + +Output from receiver stage 2 + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +**Figure B.6** + +# Annex C (informative): Change History + +| TSG-T# | TDoc | VER | CR | REV | REL | CAT | WORKITEM | SUBJECT | NEW_VER_ | +|--------|-----------|--------|------|-----|--------|-----|----------|--------------------------------------------------------------------|----------| +| T#3 | | | New | | | | | Creation of 3GPP 27.005 v1.0.0 out of GSM 07.05 v7.0.0 | 3.0.0 | +| T#6 | TP-99237 | 3.0.0 | 001 | | R99 | F | TEI | Adaptations for UMTS | 3.1.0 | +| T#11 | - | 3.1.0 | - | | Rel-4 | | | Upgrade to Rel-4 | 4.0.0 | +| T#13 | TP-010221 | 4.0.0 | 002 | | Rel-4 | F | TEI4 | Conversion of GSM to 3GPP references | 4.1.0 | +| T#16 | TP-020103 | 4.1.0 | 004 | | Rel-4 | F | TI-ATC | Correction in description of +CNMA | 4.2.0 | +| T#16 | - | 4.2.0 | - | | Rel-5 | | | Upgrade to Rel-5 | 5.0.0 | +| T#26 | - | 5.0.0 | - | | Rel-6 | | | Upgrade to Rel-6 | 6.0.0 | +| | | 6.0.0 | | | | | | Make figure 0.1 visible | 6.0.1 | +| CT#31 | CP-060126 | 6.0.1 | 005 | | Rel-7 | F | TEI7 | Correction to and in examples | 7.0.0 | +| CT#39 | CP-080137 | 7.0.0 | 006 | | Rel-8 | | TEI8 | Language specific extension of GSM7 alphabet | 8.0.0 | +| CT#46 | | 8.0.0 | | | Rel-9 | | | Upgrade to Rel-9 | 9.0.0 | +| CT#51 | CP-110197 | 9.0.0 | 0007 | | Rel-10 | F | TEI10 | Conditions for supporting SMS related AT commands | 10.0.0 | +| | | 10.0.0 | | | Rel-10 | | | Make invisible figures visible | 10.0.1 | +| CT#54 | CP-110882 | 10.0.1 | 0008 | | Rel-11 | F | TEI11 | Specification of integer type definitions of AT-command parameters | 11.0.0 | +| CT#65 | | 11.0.0 | | | Rel-12 | | | Upgrade to Rel-12 | 12.0.0 | +| CT#70 | | 12.0.0 | | | Rel-13 | | | Upgrade to Rel-13 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | SA#88e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/27_series/27010/006703eeefc59300c0e22d4c70a38e8d_img.jpg b/marked/Rel-16/27_series/27010/006703eeefc59300c0e22d4c70a38e8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb95810dc3b041942eaefaffd8b7d7fc538d71e5 --- /dev/null +++ b/marked/Rel-16/27_series/27010/006703eeefc59300c0e22d4c70a38e8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02cbc126664d54a33e3475a1606e734d3da8bdfd706e3a14ff01a3143f73ba22 +size 2449 diff --git a/marked/Rel-16/27_series/27010/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/27_series/27010/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1125706d109b05bd1f792429bcb331d1cd2521a --- /dev/null +++ b/marked/Rel-16/27_series/27010/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50f9799c996c7778471927d023e23f122460fbf5546d15090bf524c490ad9b5c +size 39493 diff --git a/marked/Rel-16/27_series/27010/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-16/27_series/27010/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fc0444f9a4c8e043d4d2cb39cec1bf01fdbf55c --- /dev/null +++ b/marked/Rel-16/27_series/27010/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c462ab114df166a7759d6c35f633524fe14d43721e839879098cec4fd3c73cc +size 9872 diff --git a/marked/Rel-16/27_series/27010/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/marked/Rel-16/27_series/27010/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a7221cfc776aab795314212cac482baf9d9e96b --- /dev/null +++ b/marked/Rel-16/27_series/27010/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05dd5f4c41796cf252601748d40a055243563e964080fef57ed5a2a7e7f9dcca +size 12155 diff --git a/marked/Rel-16/27_series/27010/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/27_series/27010/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..032210112fd2e68ed34cea7f7106ea5f9d0d0816 --- /dev/null +++ b/marked/Rel-16/27_series/27010/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40462cb0d1249471af70d284c459466e34cb6da373664712dd0901d3aeb9e49b +size 42417 diff --git a/marked/Rel-16/27_series/27010/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/27_series/27010/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c5f09dd3ea2e4438974578e5f594645b5d2a46b --- /dev/null +++ b/marked/Rel-16/27_series/27010/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcdd851a5387a808ef865c055303204a2992625d37e4c5d0023043fd6d526a48 +size 94080 diff --git a/marked/Rel-16/27_series/27010/raw.md b/marked/Rel-16/27_series/27010/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..814cd84b2556bc1d42ad3f5f40431e0f58d87f3e --- /dev/null +++ b/marked/Rel-16/27_series/27010/raw.md @@ -0,0 +1,2247 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Abbreviations..... | 7 | +| 4 Overview of Multiplexing System..... | 8 | +| 5 Non Error Recovery mode Options ..... | 9 | +| 5.1 Service Interface Definition ..... | 9 | +| 5.1.1 Service Definition Model ..... | 9 | +| 5.1.2 Start up services..... | 10 | +| 5.1.3 DLC establishment services ..... | 11 | +| 5.1.4 Data services..... | 12 | +| 5.1.5 Power Control services..... | 12 | +| 5.1.5.1 Sleep services..... | 12 | +| 5.1.5.2 Wakeup services ..... | 12 | +| 5.1.6 DLC Release services..... | 12 | +| 5.1.7 Close down services ..... | 13 | +| 5.1.8 Control Services ..... | 13 | +| 5.1.8.1 27.010 Services..... | 13 | +| 5.1.8.1.1 DLC parameter negotiation..... | 13 | +| 5.1.8.1.2 DLC Service Negotiation service..... | 14 | +| 5.1.8.1.3 Test service..... | 14 | +| 5.1.8.1.4 Flow control services ..... | 14 | +| 5.1.8.2 Port Emulation Services..... | 15 | +| 5.1.8.2.1 Remote DLC parameter negotiation service..... | 15 | +| 5.1.8.2.2 DLC Control Parameter service..... | 15 | +| 5.1.8.2.3 DLC Line status indication service..... | 16 | +| 5.2 Frame Structure ..... | 16 | +| 5.2.1 Frame Fields ..... | 16 | +| 5.2.1.1 Flag Sequence Field..... | 16 | +| 5.2.1.2 Address Field..... | 16 | +| 5.2.1.3 Control Field..... | 17 | +| 5.2.1.4 Information Field ..... | 17 | +| 5.2.1.5 Length Indicator..... | 17 | +| 5.2.1.6 Frame Checking Sequence Field (FCS)..... | 18 | +| 5.2.2 Format Conventions ..... | 18 | +| 5.2.3 Frame Validity..... | 19 | +| 5.2.4 Frame Abort..... | 19 | +| 5.2.5 Inter-frame Fill ..... | 19 | +| 5.2.6 Basic Option ..... | 19 | +| 5.2.6.1 Constraint..... | 19 | +| 5.2.7 Advanced Option..... | 20 | +| 5.2.7.1 Control-octet transparency..... | 20 | +| 5.2.7.2 Start/stop transmission - extended transparency..... | 20 | +| 5.2.7.3 Flow-control transparency ..... | 20 | +| 5.2.7.4 Frame Structure..... | 20 | +| 5.3 Frame Types..... | 21 | +| 5.3.1 Set Asynchronous Balanced Mode (SABM) command..... | 21 | +| 5.3.2 Unnumbered Acknowledgement (UA) response..... | 21 | +| 5.3.3 Disconnected Mode (DM) response..... | 21 | +| 5.3.4 Disconnect (DISC) command..... | 21 | +| 5.3.5 Unnumbered information with header check (UIH) command and response..... | 21 | +| 5.3.6 Unnumbered Information (UI) command and response..... | 22 | +| 5.4 Procedures and States..... | 22 | +| 5.4.1 DLC Establishment ..... | 22 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------|----| +| 5.4.2 | DLC Release..... | 22 | +| 5.4.3 | Information Transfer ..... | 22 | +| 5.4.3.1 | Information Data..... | 22 | +| 5.4.3.2 | Priority ..... | 23 | +| 5.4.4 | Frame Variables..... | 23 | +| 5.4.4.1 | Functions of the poll bit..... | 23 | +| 5.4.4.2 | Functions of the final bit..... | 24 | +| 5.4.5 | Time-out considerations ..... | 24 | +| 5.4.6 | Multiplexer Control Channel..... | 24 | +| 5.4.6.1 | Message format..... | 24 | +| 5.4.6.2 | Operating procedures..... | 25 | +| 5.4.6.3 | Message Type and Actions ..... | 25 | +| 5.4.6.3.1 | DLC parameter negotiation (PN) ..... | 25 | +| 5.4.6.3.2 | Power Saving Control (PSC)..... | 27 | +| 5.4.6.3.3 | Multiplexer close down (CLD) ..... | 27 | +| 5.4.6.3.4 | Test Command (Test)..... | 28 | +| 5.4.6.3.5 | Flow Control On Command (FCon) ..... | 28 | +| 5.4.6.3.6 | Flow Control Off Command (FCoff) ..... | 28 | +| 5.4.6.3.7 | Modem Status Command (MSC)..... | 28 | +| 5.4.6.3.8 | Non Supported Command Response (NSC)..... | 30 | +| 5.4.6.3.9 | Remote Port Negotiation Command (RPN)..... | 31 | +| 5.4.6.3.10 | Remote Line Status Command(RLS)..... | 34 | +| 5.4.6.3.11 | Service Negotiation Command (SNC)..... | 34 | +| 5.4.7 | Power Control and Wake-up Mechanisms..... | 36 | +| 5.4.8 | Flow Control..... | 37 | +| 5.4.8.1 | RTR Flow Control ..... | 37 | +| 5.4.8.2 | XON/XOFF Flow Control ..... | 37 | +| 5.5 | Convergence Layers..... | 38 | +| 5.5.1 | Type 1 - Unstructured Octet Stream..... | 38 | +| 5.5.2 | Type 2 - Unstructured Octet Stream with flow control, break signal handling and transmission of V.24 signal states..... | 39 | +| 5.5.3 | Type 3 - Uninterruptible Framed Data ..... | 40 | +| 5.5.4 | Type 4 - Interruptible Framed Data..... | 41 | +| 5.6 | DLCI Values ..... | 41 | +| 5.7 | System Parameters ..... | 42 | +| 5.7.1 | Acknowledgement Timer (T1)..... | 42 | +| 5.7.2 | Maximum Frame Size (N1)..... | 42 | +| 5.7.3 | Maximum number of retransmissions (N2) ..... | 42 | +| 5.7.4 | Window Size (k)..... | 42 | +| 5.7.5 | Response Timer for multiplexer control channel (T2) ..... | 42 | +| 5.7.6 | Response Timer for wake-up procedure(T3)..... | 42 | +| 5.8 | Start-up and close-down of multiplexer ..... | 43 | +| 5.8.1 | Start-up procedure ..... | 43 | +| 5.8.2 | Close-down procedure..... | 43 | +| 6 | Error Recovery Mode Option ..... | 43 | +| 6.1 | Frame Types..... | 43 | +| 6.1.1 | Information transfer, I, command and response..... | 43 | +| 6.1.2 | Receive ready, RR, command and response..... | 44 | +| 6.1.3 | Receive not ready, RNR, command and response..... | 44 | +| 6.1.4 | Reject, REJ, command and response..... | 44 | +| 6.2 | Procedure and State ..... | 44 | +| 6.2.1 | Frame state variables and sequence numbers ..... | 44 | +| 6.2.1.1 | General..... | 44 | +| 6.2.1.2 | Send state variable V(S) ..... | 44 | +| 6.2.1.3 | Send sequence number N(S)..... | 44 | +| 6.2.1.4 | Receive state variable V(R)..... | 45 | +| 6.2.1.5 | Receive sequence number N(R) ..... | 45 | +| 6.2.1.6 | Use of the P/F bit to assist in error recovery..... | 45 | +| 6.2.2 | Exchange of information (I) frames ..... | 45 | +| 6.2.2.1 | Sending I frames ..... | 45 | +| 6.2.2.2 | Receiving I frames ..... | 45 | + +| | | | +|-------------------------------|------------------------------------------------------|-----------| +| 6.2.2.3 | Reception of incorrect frames..... | 46 | +| 6.2.2.4 | Station receiving acknowledgements..... | 46 | +| 6.2.2.5 | Exception conditions and recovery..... | 46 | +| 6.2.2.5.1 | Busy..... | 46 | +| 6.2.2.5.2 | N(S) sequence error..... | 46 | +| 6.2.2.5.3 | Poll/final (P/F) bit (checkpoint) recovery ..... | 47 | +| 6.2.2.5.4 | REJ recovery ..... | 47 | +| 6.2.2.5.5 | SABM Command..... | 47 | +| 6.2.2.5.6 | DISC Command ..... | 47 | +| Annex A (informative): | Advice to TE software implementers ..... | 48 | +| Annex B (informative): | Explanatory notes on the CRC Calculation..... | 49 | +| B.1 | Example ..... | 49 | +| B.2 | Reflected bits..... | 49 | +| B.3 | Implementation ..... | 50 | +| B.3.1 | Calculate FCS for the example given earlier ..... | 50 | +| B.3.2 | Check FCS for the example given earlier ..... | 50 | +| B.3.3 | The transmitter code..... | 50 | +| B.3.4 | The receiver code ..... | 50 | +| B.3.5 | Reversed CRC table ..... | 51 | +| Annex C (informative): | Change History..... | 52 | + +# --- 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. + +# --- Introduction + +The multiplexer protocol described in the present document operates between an UE and a TE and allows a number of simultaneous sessions over a normal serial asynchronous interface. Each session consists of a stream of bytes transferring various kinds of data; for instance, voice, fax, data, SMS, CBS, phonebook maintenance, battery status, GPRS, USSD etc. This permits, for example, SMS and CBS to be transferred to a TE when a data connection is in progress. Many other combinations are possible including digital voice. It is, for instance, possible to transfer digital voice in combination with SMS. The multiplexer allows a complete system to be partitioned in a flexible way between a UE and TE. + +The design of the multiplexer is flexible and independent of UE/TE platforms, and allows existing applications to work without any modifications. + +The multiplexer is designed, with special care for battery-powered devices, to include very important functionality such as power saving control and priorities. It is also specially designed to require minimum processing power and memory consumption. + +The multiplexer is defined as a single mode with different options based on the ISO HDLC standard (ISO/IEC 13239) although the basic option is not in accordance with HDLC. + +In the basic option, the multiplexer does not make use of any transparency mechanism or error recovery method. The advanced option uses the ISO HDLC standard transparency mechanism and gives the multiplexer an easy re-synchronisation method and the ability to operate over links which use DC1/DC3 (XON/XOFF) flow control. The advanced option also may include error-recovery for links subject to errors. + +In its basic option, the multiplexer is intended for use in situations where the link between UE and TE is of a very good quality and where the HDLC transparency mechanism (byte stuffing) can not be implemented in the UE. If an UE supports the HDLC transparency mechanism, it shall be used by the multiplexer. The ISO HDLC transparency mechanism must be used if loss of synchronisation may occur caused by, for example, data over-runs or under-runs. The error-recovery option should be used in situations where the link is subject to errors. + +The multiplexer is based on a control channel. On this channel, management information is exchanged, such as parameter negotiation, power saving control information, testing, flow control, close down etc. + +The multiplexer is optional, but when supported, it is activated with the AT+CMUX command described in 3GPP TS 27.007 [4]. + +# --- 1 Scope + +The scope of the present document is to define a multiplexing protocol between a UE and a TE. The multiplexing protocol can be used to send any data, for instance voice, SMS, USSD, fax etc. + +The present document describes the protocol, but not the commands or data transported with it. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void. +- [2] ISO/IEC 13239 (1997): "Information technology - Telecommunications and information exchange between systems - High-level data link control (HDLC) procedures". +- [3] 3GPP TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". +- [4] 3GPP TS 27.007: "AT command set for User Equipment (UE)". +- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [6] 3GPP TS 46.021: "Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- [7] ISO/IEC 646 (1991): "Information technology - ISO 7-bit coded character set for information interchange". + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|------------------------------------------| +| ABM | Asynchronous Balanced Mode | +| DLC | Data Link Connection | +| DM | Disconnected Mode | +| ERM | Error-Recovery Mode | +| FCS | Frame Check Sequence | +| MSC | Modem Status Command | +| PSC | Power Saving Control | +| SABM | Set Asynchronous Balanced Mode | +| UAU | Unnumbered Acknowledgement | +| UIH | Unnumbered Information with header Check | +| UI | Unnumbered Information | + +Additional abbreviations can be found in 3GPP TR 21.905 [5]. + +# 4 Overview of Multiplexing System + +The multiplexer provides mechanisms for conveying streams of data between TE and UE over a single start-stop framed, serial link. Figure 1 shows the arrangement of the various protocol levels and functions. The multiplexer layer provides multiplexing of data arranged in octet streams with no other framing; if the structure of the data has to be conveyed, a convergence layer may be necessary. The present document defines some convergence layers, others may be added later. + +![Figure 1: Protocol Stacks. The diagram shows two protocol stacks, TE (Terminal Equipment) and UE (User Equipment), connected by a single Physical Layer - serial link. Both stacks have four layers: TE Processes (four shown), Convergence Layers (four shown), Multiplexer Layer, and Physical Layer - serial link. The TE and UE stacks are connected at the Physical Layer.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +The diagram illustrates the protocol stacks for a Terminal Equipment (TE) and a User Equipment (UE). Both stacks consist of four layers: + + +- TE Processes (four shown)** / **UE Processes (four shown)**: The top layer, represented by a 4x1 grid of boxes. +- Convergence Layers (four shown)**: The second layer, also represented by a 4x1 grid of boxes. +- Multiplexer Layer**: The third layer, represented by a single wide box. +- Physical Layer - serial link**: The bottom layer, represented by a single wide box. + + The TE and UE stacks are connected at their Physical Layer boxes by a single horizontal line, indicating a shared serial link. + +Figure 1: Protocol Stacks. The diagram shows two protocol stacks, TE (Terminal Equipment) and UE (User Equipment), connected by a single Physical Layer - serial link. Both stacks have four layers: TE Processes (four shown), Convergence Layers (four shown), Multiplexer Layer, and Physical Layer - serial link. The TE and UE stacks are connected at the Physical Layer. + +**Figure 1: Protocol Stacks** + +The multiplexer provides a virtual connection between a process in the TE and a similar process in the UE. For example, a PC application supporting SMS functions could be connected to the SMS handler in the UE via a multiplexer channel. + +The present document uses start-stop transmission with eight-bit characters. Communication between the two multiplexing entities takes place using frames constructed as defined below. + +Each channel between TE and UE is called a Data Link Connection (DLC) and is established separately and sequentially. + +Each DLC may have individual flow control procedures for buffer management purposes and the aggregate link also has overall flow control mechanisms. + +DLCs have two modes of operation; Error-Recovery Mode (ERM) and non-error-recovery mode (non-ERM), the choice of mode is made when a DLC is established. DLCs using error recovery mode may exist on the same link as DLCs using non-error recovery mode. If the error-recovery mode (ERM) is to be used at least on one DLC, then the multiplexer must be configured with the ISO HDLC transparency mechanism. The use of error recovery mode is optional. Non-error recovery mode uses the UI frame or UIH frame to carry user data; error recovery mode uses the I frame. + +The multiplexer has three operating options, basic, advanced without error recovery and advanced with error recovery. The characteristics of the options are: + +### **Basic:** + +- length indicator used instead of the HDLC transparency mechanism; +- different flag octet from that used by HDLC; +- can not be used on links which use XON/XOFF flow control; +- may have longer recovery procedure from loss of synchronisation. + +### **Advanced without error recovery:** + +- asynchronous HDLC procedures in accordance with ISO/IEC 13239; +- can be used on links which use XON/XOFF flow control; + +- recovers quickly from loss of synchronisation. + +Advanced with error recovery: + +- Uses HDLC error-recovery procedures. + +# --- 5 Non Error Recovery mode Options + +This clause describes the non-error-recovery options (basic and advanced) of the multiplexer. The main are given below: + +- a simple set of procedures with no error recovery mechanism, for use on reliable connections; +- data transparency is provided by the HDLC mechanism (advanced option only); +- a multiplexer control channel which conveys management and control information between the UE and TE; +- a mechanism that permits either UE or TE to enter power-saving modes without compromising the integrity of the multiplexer; +- a comprehensive set of convergence layers which enables many types of data to be carried while preserving the structure of the original data. + +The use of the transparency mechanism must be set up at the beginning of the multiplexing session. It is a characteristic for the entire multiplexing session. + +The simple set of procedures uses UIH frames to transmit information; these frames are easy to process because their structure permits the HDLC Frame Check Sequence (FCS) to be pre-calculated rather than being constructed on a character-by character basis. The procedures used are very straightforward and it is not necessary to implement the usual HDLC state machines. + +UI frames or UIH frames may be used for those channels where the timely delivery of the information is more important than its reliability because erroneous frames will be discarded. UI frames would be used in those cases where it is important that the data delivered is accurate. + +## 5.1 Service Interface Definition + +This clause describes the services provided by the 3GPP TS 27.010 data link layer to the upper layer. The interface is specified in terms of primitives and parameters. + +NOTE: This clause is only for information, detailed description of the parameters is found in the following clauses. + +### 5.1.1 Service Definition Model + +The present document is intended to define a protocol that can be used to emulate a serial port. In most systems the 27.010 will be a part of a port driver which includes a port emulation entity that must support existing communication APIs. The communication APIs vary from operating system to operating system and from device to device. The present document does not specify how 27.010 is used by a port driver to emulate an existing API but instead focus on a set of services that can be used by all port drivers. Port drivers are not required to use all the services of 27.010. + +The figure below shows a model of how 27.010 fits into a typical system. + +![Two diagrams illustrating the architecture of a Port Emulation Entity. The left diagram shows a Legacy Application connected to a Port Emulation Entity via a Port interface (e.g., VCOMM). The Port Emulation Entity is connected to an 07.10 service IF. The right diagram shows a Legacy Application connected to a Port Emulation Entity via a Driver. The Port Emulation Entity is connected to an 07.10 service IF. Both diagrams show the flow of data and control signals between the application, the port emulation entity, and the 07.10 service IF.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates two architectural models for connecting a Legacy Application to an 07.10 service IF through a Port Emulation Entity. + +**Left Diagram:** A Legacy Application is connected to a Port Emulation Entity via a Port interface (e.g., VCOMM). The Port Emulation Entity is connected to an 07.10 service IF. The Legacy Application sends 'Write' and 'Control' signals to the Port Emulation Entity, which in turn sends 'Request' and 'Control Parameters' to the 07.10 service IF. The 07.10 service IF responds with 'Confirm' and 'Parameter Setting' to the Port Emulation Entity, which then sends 'Read' and 'Control' signals back to the Legacy Application. + +**Right Diagram:** A Legacy Application is connected to a Port Emulation Entity via a Driver. The Port Emulation Entity is connected to an 07.10 service IF. The Legacy Application sends 'Write' and 'Control' signals to the Port Emulation Entity, which in turn sends 'Response' and 'Control Parameters' to the 07.10 service IF. The 07.10 service IF responds with 'Indication' and 'Parameter Setting' to the Port Emulation Entity, which then sends 'Read' and 'Control' signals back to the Legacy Application. + +Two diagrams illustrating the architecture of a Port Emulation Entity. The left diagram shows a Legacy Application connected to a Port Emulation Entity via a Port interface (e.g., VCOMM). The Port Emulation Entity is connected to an 07.10 service IF. The right diagram shows a Legacy Application connected to a Port Emulation Entity via a Driver. The Port Emulation Entity is connected to an 07.10 service IF. Both diagrams show the flow of data and control signals between the application, the port emulation entity, and the 07.10 service IF. + +The legacy application utilises a conventional serial port communication interface. The port emulation entity maps a system specific communication interface to 27.010 services. The 27.010 provides several transparent data stream channels and a control channel. The port interface is the application programmers interface for communication. It varies from system to system and one example is Virtual comm ports in windows. + +### 5.1.2 Start up services + +These services are used to start the TS 27.010 multiplexer operation over a serial channel. The following services are provided: + +TS0710\_START.request (*mode, system\_parameters*); + +TS0710\_START.indication (*mode, system\_parameters*); + +TS0710\_START.response (*mode, system\_parameters, accept*); + +TS0710\_START.confirm (*mode, system\_parameters, accept*). + +**Description:** the *request* primitive is used to request that the multiplexer mode to be turned on in the desired mode and system parameters. The *indication* primitive transfers the request to start multiplexer operation along with the desired mode and system parameters to the upper layer of the target device. If the target device accepts the request by issuing an affirmative *response* primitive, the suggested mode and system parameters will become valid. The *confirm* primitive is returned to the upper layer of the requesting device. A successful establishment of the multiplexer mode is indicated by the *accept* parameter being set to “true”. If the *accept* parameter is set to “false” the returned values for the other parameters are those suggested by the responding device. + +Parameters: + +*mode* = [Basic | HDLC - UIH frames | HDLC - UI frames | HDLC - frames]. (Note that the frame type for HDLC mode refers to the multiplexer control channel. For subsequently opened DLCs this parameter can be negotiated.) + +*system\_parameters* = Port speed [9,6 | 19,2 | 38,4 | 57,6 | 115,2 | 230,4 kBit/s], + +Maximum Frame Size [1 – 128 in Basic mode, +1 – 512 in HDLC modes +default: 31 for the basic +option and 64 for the +advanced option] +Acknowledgement Timer [0,01s-2,55s, +default: 0,1s] +Maximum number of retransmissions [0 – 100, +default : 3] +Response timer for the multiplexer control +channel [0,01s-2,55s, default: 0,3s] +Wake up response timer [1s – 255s, default 10s] +Window size for error recovery mode [1 – 7, +default : 2] + +*accept* = [true | false] + +Support of the mode parameter is optional. If the mode parameter is omitted, Basic mode is implied. Note that some of the above system parameters can be redefined for the individual DLCs, see below under DLC establishment services. + +### 5.1.3 DLC establishment services + +The DLC establishment services are used to open DLC's on the multiplexer channel. The following services are provided: + +TS\_0710\_DLC\_ESTABLISHMENT.request(DLCI, system\_parameters); +TS\_0710\_DLC\_ESTABLISHMENT.indication(DLCI, system\_parameters); +TS\_0710\_DLC\_ESTABLISHMENT.response(DLCI, system\_parameters, accept); +TS\_0710\_DLC\_ESTABLISHMENT.confirm(DLCI, system\_parameters, accept). + +**Description:** The transmitting device uses the *request* primitive to initiate the establishment of a new DLC with a desired set of system parameters on the multiplexer channel. The *indication* primitive is passed to the upper layer by the TS 27.010 layer of the receiving device on reception of the DLC establishment request. The receiving device uses the *response* primitive to either accept or reject the proposed DLCI with its system parameters. On rejection, it is possible to suggest a modified set of system parameters. The *confirm* primitive is passed to the upper layer of the transmitting device on reception of the response from the receiving device. + +#### Parameters: + +*DLCI* = 1-63 (DLCI number) + +*System parameters* = Type of frame [UIH | UI | I, default: UIH], +Convergence layer [1 - 4, default: 1] +Priority [0-63] +Acknowledgement Timer [0,01s-2,55s, +default: 0,1s] +Maximum Frame Size [1 – 32768, +default: 31 for the basic option and +64 for the advanced option] +Maximum number of retransmissions [0 – 255, +default : 3] +Window size for error recovery mode [1 – 7, +default : 2] + +*Accept* = [true | false] + +All entries in the system parameters parameter are optional. The entries not implemented assume the default values. + +### 5.1.4 Data services + +The data services provided are: + +TS\_0710\_DATA.request(DLCI, User\_data); + +TS\_0710\_DATA.indication(DLCI, User\_data). + +**Description:** the transmitting unit initiates transmission of data using the frame type specified for the chosen DLCI by means of the request primitive. The transmitted data is delivered to the upper layer of the receiving by the *indication* primitive. No confirmation primitive exists even for the error recovery mode. In this mode TS 27.010 will take care of all mechanisms involved in the error checking and thus deliver data error free. + +#### Parameters: + +*DLCI* = [1 – 63] DLC over which the data is to be transmitted. + +*User\_data*= Data to be transferred organised in accordance with the convergence layer of the DLC + +### 5.1.5 Power Control services + +In some application it might be desirable for either the DTE or the DCE to enter a power saving mode with a minimum of communication activities taking place. Services that support this functionality are the Sleep services and the Wakeup services. + +#### 5.1.5.1 Sleep services + +TS\_0710\_SLEEP.request; + +TS\_0710\_SLEEP.indication; + +TS\_0710\_SLEEP.confirm. + +**Description:** the *request* primitive is used to advise the receiving device that the transmitter wishes to enter a low power state. The TS 27.010 layer of the receiving unit sends an *indication* primitive to the upper layer in order to inform that the transmitting unit has entered the power saving state. The TS 27.010 layer will automatically transmit an acknowledge message to the transmitting device, thus no *response* primitive is required. The *confirm* primitive is sent to the upper layer of the transmitting device when the low power request has been received, and indicates that the TS 27.010 layer has entered the low power mode. Note that the Receiving device is not required to enter a low power mode, but it will be considered to have done so by the TS 27.010 layer. + +#### 5.1.5.2 Wakeup services + +TS\_0710\_WAKEUP.indication; + +TS\_0710\_WAKEUP.response. + +**Description:** the *indication* primitive is sent to the upper layer when the TS 27.010 layer of the receiving unit receives a request to wake up from the power saving state. When the receiving device is ready to resume operation on the multiplexer channel this is indicated to the TS 27.010 layer in the receiving unit by means of the *response* primitive. Since the wakeup routine is initiated by the transmitting device attempting to communicate, neither *request* nor *confirm* primitives are provided for the wakeup service. The transmitting device instead uses the Data services described below. + +### 5.1.6 DLC Release services + +The DLC release services are used to disconnect a DLC. The following services are provided: + +TS\_0710\_DLC\_RELEASE.request(DLCI); + +TS\_0710\_DLC\_RELEASE.indication(DLCI). + +**Description:** The *request* primitive is used by the upper layer in the transmitting device to initiate close down of the selected DLC in TS 27.010. The TS 27.010 layer of the receiving device uses the *indication* primitive to inform the upper layer that the DLC has been closed down. + +#### Parameters: + +*DLCI* = [1 – 63] Number of the DLC to be released. + +### 5.1.7 Close down services + +The Close down services are used to terminate multiplexer operation on the serial channel and resume AT mode. The services provided are: + +TS\_0710\_CLOSE.request; + +TS\_0710\_CLOSE.indication. + +**Description:** when the request primitive is passed to the TS 27.010 layer of the transmitting device close down of the multiplexer mode is initiated and a close down command is sent to the receiving device. On reception of the close down command the TS 27.010 layer of the receiving device sends the indication primitive to the upper layer and the multiplexer mode is terminated. + +### 5.1.8 Control Services + +#### 5.1.8.1 27.010 Services + +##### 5.1.8.1.1 DLC parameter negotiation + +These services are used to negotiate and set parameters for a specific DLC. The following services are provided: + +TS0710\_PARNEG.request (DLC, *DLC parameters*); + +TS0710\_PARNEG.indication (DLC, *DLC parameters*); + +TS0710\_PARNEG.response (DLC, *DLC parameters*, *accept*); + +TS0710\_PARNEG.confirm (DLC, *DLC parameters*, *accept*). + +**Description:** the *request* primitive is used to request that the remote 27.010 entity changes a specific DLC connection parameters. An indication is sent to the remote port emulation entity. The remote emulation entity replies with a response which is forwarded as an confirmation to the originating port emulating entity. + +*DLC\_parameters* = frame type [ UIH | UI | I , +                           default: UIH ] +                   Convergence Layer Type [ Type 1 | Type 2 | Type 3 | Type 4, +                           default: Type 1 ] +                   Priority [1-63, +                           default: according to table in clause 5.6] +                   Acknowledgement timer [10 ms - 25.5 sec, +                           default: 100 ms] +                   Maximum Frame Size [1 – 32768, +                           default: 31 for the basic option and +                           64 for the advanced option] +                   Maximum number of retransmissions [0 – 100, +                           default : 3] +                   Response timer for the multiplexor control +                           channel [0,01s-2,55s, default: 0,3s] +                   Wake up response timer [1s – 255s, default 10s] +                   Window size for error recovery mode [1 – 7, +                           default : 2] + +*accept* = [true | false] + +##### 5.1.8.1.2 DLC Service Negotiation service + +These services are used to negotiate and set a specific service on a DLC. The following services are provided: + +TS0710\_SERVNEG.request (DLC, *Service parameters*); + +TS0710\_SERVNEG.indication (DLC, *Service parameters*); + +TS0710\_SERVNEG.response (DLC, *Service parameters*, *accept*); + +TS0710\_SERVNEG.confirm (*DLC, Service\_parameters, accept*). + +**Description:** the *request* primitive is used to request a specific service on a DLC. The indication is sent to the other port emulation. The remote port emulation entity replies with a response containing accepted or possible services. The originating port emulation entity receives a confirm on the request with either an accept or a possible service list. + +*service\_parameters* = Service [ data | voice 64kbit/s A-law PCM | reserved 1 | reserved 2 ], +voice codec [ 3GPP TS 46.021 | 64kbit/s u-law PCM | coded ADPCM 32kbit/s | coded half rate +128 kbit/s PCM | reserved ] + +##### 5.1.8.1.3 Test service + +These services are used to test the communication link between two 27.010 entities. The following services are provided: + +TS0710\_TEST.request (*Test data*); + +TS0710\_TEST.confirm (*Test data*). + +**Description:** the *request* primitive is used to request a test of the communication link. The data is sent to the remote entity, which loops it back. The confirmation is sent to the originating port emulation entity containing the looped data. + +*Test Data* = Data to be transferred as a test pattern, organised in accordance with the convergence layer of the 27.010 control channel. + +##### 5.1.8.1.4 Flow control services + +The flow control services provided are: + +TS\_0710\_FLOW.request(DLCI, State); + +TS\_0710\_FLOW.indication(DLCI, State). + +###### **Description:** + +The request primitive with *State* = *disable* disables the issuing of TS\_0710\_DATA.*indications* by the 27.010 entity. The request primitive with *State* = *enable* enables the issuing of TS\_0710\_DATA.*indications* by the 27.010 entity. These requests may or may not result in the remote 27.010 entity issuing a TS\_0710\_FLOW.*indication* to the remote service user, depending on the states of the buffers in the 27.010 entities. + +The indication primitive with *State* = *disable* disables the issuing of TS\_0710\_DATA.*requests* by the service user. The indication primitive with *State* = *enable* enables the issuing of TS\_0710\_DATA.*requests* by the service user. These indications may or may not have resulted from the receipt by the remote 27.010 entity of a TS\_0710\_FLOW.*request* from the remote service user. They may have been issued by the local 27.010 entity as a result of its buffer state. + +The initial state of the 27.010 entity is with data flow enabled. + +###### **Parameters:** + +*DLCI* = [1 – 63] DLC over which the data is to be transmitted. + +*State* = *enabled* (data may be transferred), *disabled* (data may not be transferred) + +#### 5.1.8.2 Port Emulation Services + +##### 5.1.8.2.1 Remote DLC parameter negotiation service + +These services are used to negotiate and set of parameters for a remote communication port. The following services are provided: + +TS0710\_PORTNEG.request (*DLC, Port\_parameters*); + +TS0710\_PORTNEG.indication (*DLC, Port\_parameters*); + +TS0710\_PORTNEG.response (*DLC, Port parameters, accept*); + +TS0710\_PORTNEG.confirm (*DLC, Port\_parameters, accept*). + +**Description:** The *request* primitive is used to request that the remote port changes its parameters. The indication is sent to the other port emulation entity. The remote port emulation entity replies with a response. A confirm is sent to the originating port entity. + +*port\_parameters* = Port speed [2,4 | 4,8 | 7,2 | 9,6 | 19,2 | 38,4 | 57,6 | 115,2 | 230,4 kBit/s], +*Data bits* [ 5 | 6 | 7 | 8, default: 8 bits | + Stop bits [ 1 | 1,5, default: 1 bit | + Parity [ no parity | parity, default: no parity | + Parity Type [ odd | even | mark | space] + +*accept* = [true | false] + +##### 5.1.8.2.2 DLC Control Parameter service + +The DLC Control Parameter service is used to convey control parameters between Port Emulation Entities. Default values should be assumed if no control parameter has been designated since the DLC has been made. This service is to control a specific DLC. It includes such as flow control, Modem signals, Break. The following services are provided: + +TS0710\_CONTROL.request (*DLC, Control\_parameters*); + TS0710\_CONTROL.indication (*DLC, Control\_parameters*); + TS0710\_CONTROL.response (*DLC, Control\_parameters*); + TS0710\_CONTROL.confirm (*DLC, Control\_parameters*). + +**Description:** the *request* primitive is used to convey control information to the remote port. The indication is sent to the other port emulation entity. The remote port emulation entity replies with a response which is sent to the originating 27.010 entity. A confirm is sent back to the port emulation entity. + +*system\_parameters* = Modem Signal [DTR/DSR | RTS/CTS | RI | DCD ], + Break Signal [0—3 s in steps of 200 ms, default 0ms ], + Buffers [do not discard buffers, discard buffer default: do not discard buffers], + Break signal sequence [ as soon as possible | in sequence, default: in sequence] + +##### 5.1.8.2.3 DLC Line status indication service + +These services are used to indicate a DLC line status to a remote port emulation entity.. The following services are provided: + +TS0710\_PORTNEG.request (*DLC, Line Status parameter*); + TS0710\_PORTNEG.indication (*DLC, Line Status parameter*). + +**Description:** the *request* primitive is used to send the line status to the remote device. The indication is sent to the other port emulation entity. The remote port emulation does not reply. + +*Line status parameter* = Port speed [no errors, overrun error, parity error, framing error] + +## 5.2 Frame Structure + +All information transmitted between the TE and UE is conveyed in frames. + +### 5.2.1 Frame Fields + +The frame structure is composed of an opening and a closing flag, an Address field, a Control field, an Information field and FCS field. A length indication field is present in each frame if no transparency mechanism is used for the multiplexing session. + +#### 5.2.1.1 Flag Sequence Field + +Each frame begins and ends with a flag sequence octet which is defined as a constant bit pattern. + +#### 5.2.1.2 Address Field + +The address field consists of a single octet. It contains the Data Link Connection Identifier (DLCI), the C/R bit and the address field extension bit as shown in figure 2. + +| | | | | | | | | | +|---------|----|-----|---|---|---|---|---|---| +| Bit No. | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | | D | L | C | I | | + +**Figure 2: Format of Address Field** + +The DLCI is used to identify an individual user information stream as well as to identify connections between TE and UE. Multiple DLCIs shall be supported but the number is implementation-specific. The DLCIs are dynamically assigned. The values used for specific DLCIs are given in clause 5.6. + +The C/R (command/response) bit identifies the frame as either a command or a response. In conformance with HDLC rules, a command frame contains the address of the data link connection entity to which it is transmitted while a response frame contains the address of the data link connection entity transmitting the frame. For a given DLC, the DLCI value of the address field remains the same but the C/R bit changes, as shown in table 1. + +**Table 1: Command/response bit usage** + +| Command/response | Direction | | C/R value | +|------------------|-----------|-------------|-----------| +| Command | Initiator | → Responder | 1 | +| | Responder | → Initiator | 0 | +| Response | Initiator | → Responder | 0 | +| | Responder | → Initiator | 1 | + +Initiator is the station that take the initiative to initialize the multiplexer (i.e. sends the SABM command at DLCI 0 ) and the responder is the station that accepts the initialization of the multiplexer (i.e. sends the UA response at DLCI 0) + +See clause 5.4.3.1 for more details about C/R bit. + +According to the rules of ISO/IEC 13239, the range of the address field may be extended by use of the EA bit. When the EA bit is set to 1 in an octet, it signifies that this octet is the last octet of the address field. When the EA bit is set to 0, it signifies that another octet of the address field follows. In the present document there is only one address octet so the EA bit is always set to 1. Note that future amendments to the present document may extend the address field and use the EA bit. + +#### 5.2.1.3 Control Field + +The content of the control field defines the type of frame. The control fields of the frames used in the present document are described in table 2. + +**Table 2: Coding of Control Field** + +| Frame Type | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | Notes | +|------------------------------------------------|---|---|---|---|-----|---|---|---|----------| +| SABM (Set Asynchronous Balanced Mode) | 1 | 1 | 1 | 1 | P/F | 1 | 0 | 0 | | +| UA (Unnumbered Acknowledgement) | 1 | 1 | 0 | 0 | P/F | 1 | 1 | 0 | | +| DM (Disconnected Mode) | 1 | 1 | 1 | 1 | P/F | 0 | 0 | 0 | | +| DISC (Disconnect) | 1 | 1 | 0 | 0 | P/F | 0 | 1 | 0 | | +| UIH (Unnumbered Information with Header check) | 1 | 1 | 1 | 1 | P/F | 1 | 1 | 1 | | +| UI (Unnumbered Information) | 1 | 1 | 0 | 0 | P/F | 0 | 0 | 0 | Optional | + +In table 2, P/F is the Poll/Final bit. The functions of these bits are described later. + +#### 5.2.1.4 Information Field + +The information field is the payload of the frame and carries the user data and any convergence layer information. The field is octet structured. The information field is only present in I frames, UI frames and UIH frames. + +#### 5.2.1.5 Length Indicator + +This field is present only in case when basic option is activated. + +It has the following format: + +| | | | | | | | | | +|-----|-----|----|----|----|----|----|----|----| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | E/A | L1 | L2 | L3 | L4 | L5 | L6 | L7 | + +**Figure 3: Length field, first byte** + +The L1 to L7 bits indicates the length of the following data field. The default length is 31 bytes. + +According to the rule of ISO/IEC 13239, the range of the length field may be extended by use of the EA bit. When the EA bit is set to 1 in an octet, it signifies that this octet is the last octet of the length field. When the EA bit is set to 0, it signifies that a second octet of the length field follows. The total length of the length field is in that case 15bits, L1-L15. + +The second octet of the length field (only present when the EA field in the first byte is set to 0) format: + +| | | | | | | | | | +|-----|----|----|-----|-----|-----|-----|-----|-----| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | L8 | L9 | L10 | L11 | L12 | L13 | L14 | L15 | + +**Figure 4: Length field, second byte** + +The length field shall always be present, even if the data field is empty. + +#### 5.2.1.6 Frame Checking Sequence Field (FCS) + +The FCS shall be the ones complement of the sum (modulo 2) of: + +- a) the remainder of + +$$x^k (x^7 + x^6 + x^5 + x^4 + x^3 + x^2 + x^1 + 1)$$ + +divided (modulo 2) by the generator polynomial + +$$x^8 + x^2 + x + 1,$$ + +where $k$ is the number of bits in the frame existing between, but not including, the final bit of the opening flag and the first bit of the FCS, excluding start and stop elements (start/stop transmission), and bits (synchronous transmission) and octets (start/stop transmission) inserted for transparency, and + +- b) the remainder of the division (modulo 2) by the generator polynomial + +$$x^8 + x^2 + x + 1$$ + +of the product of $x^8$ by the content of the frame existing between, but not including, the final bit of the opening flag and the first bit of the FCS, excluding start and stop elements (start/stop transmission), and bits (synchronous transmission) and octets (start/stop transmission) inserted for transparency. + +As a typical implementation, at the transmitter, the initial content of the register of the device computing the remainder of the division is preset to all ones and is then modified by division by the generator polynomial (as described above) of the address, control and information fields; the ones complement of the resulting remainder is transmitted as the 8-bit FCS. + +At the receiver, the initial content of the register of the device computing the remainder is preset to all ones. The final remainder after multiplication by $x^8$ and then division (modulo 2) by the generator polynomial + +$$x^8 + x^2 + x + 1$$ + +of the serial incoming protected bits and the FCS, will be 1111 0011 ( $x^7$ through $x^0$ , respectively) in the absence of transmission errors. + +In the case of the UIH frame, the contents of the I-field shall not be included in the FCS calculation. FCS is calculated on the contents of the address, control and length fields only. This means that only the delivery to the correct DLCI is protected, but not the information. The FCS is calculated in the normal manner for all other frames in Table 2. + +### 5.2.2 Format Conventions + +All transmitted characters will be sent using one start bit, eight data bits, no parity bit and one stop bit. + +In the field descriptions, bit 1 is transmitted first. + +Addresses, commands, responses and sequence numbers shall be transmitted low-order bit first (for example, the first bit of the sequence number that is transmitted shall have the weight $2^0$ ). + +The FCS shall be transmitted to the line commencing with the coefficient of the highest term. + +NOTE: The use of these conventions in the present document means that octet values are often expressed in the reverse bit order from conventions used in many other standards. The conventions are used here because of the importance of the correct order of bit transmission; care should be taken during implementation. + +### 5.2.3 Frame Validity + +An invalid frame in the frame format is one which meets any one (or more) of the following conditions: + +- is not properly bounded by two flags; +- does not have at least three octets between flags after removal of characters inserted for transparency; +- indicates presence of a transmission error in that the FCS check fails; +- contains an address field with more than one octet. + +Invalid frames shall be discarded without notification to the sender. Actions taken by the multiplexer to indicate reception of an invalid frame to the UE or TE are left to implementers. However, an indication that a frame with an FCS error has been received may be of use when supporting DLCs for voice/audio. + +As an optional procedure in response to an invalid frame in error recovery mode, a receiver may transmit an REJ frame. + +### 5.2.4 Frame Abort + +Aborting a frame is not supported. + +### 5.2.5 Inter-frame Fill + +The time between frames shall be filled by sending continuous stop-polarity except in the case of the wake-up procedure (see clause 5.4.7). The receiver shall also operate correctly if the time between frames is filled with flag characters. If a receiver receives more than three consecutive flags it shall begin to transmit continuous flags at the first available time (see clause 5.4.7). + +### 5.2.6 Basic Option + +In this case, opening flag and closing flags may appear in the Information field of the frame. The flags cannot be used to determine beginning and end of a frame. A length indication for the frame must be given instead. The frame structure is then as follows: + +| Flag | Address | Control | Length Indicator | Information | FCS | Flag | +|---------|---------|---------|------------------|--------------------------------------------------|---------|---------| +| 1 octet | 1 octet | 1 octet | 1 or 2 octets | Unspecified length but integral number of octets | 1 octet | 1 octet | + +**Figure 5: Frame Structure for Basic option** + +The flag field in basic option has the following format. + +| | | | | | | | | | +|-----|---|---|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | + +**Figure 6: Flag field in basic option** + +#### 5.2.6.1 Constraint + +The closing flag may also be the opening flag of the following frame. + +The flag value is different from the one used when the advanced option is activated. + +Operation on link using DC1/XON and DC3/XOFF control characters defined in ISO/IEC 646 is not supported. + +### 5.2.7 Advanced Option + +If the advanced option is activated at the beginning of the multiplexing session, then it is used for all frames. This mechanism is based on a control octet transparency. It is based on a unique appearance of the opening and the closing flag in each frame. These flags will never appear in the information field of the frame. This mechanism allows a very quick synchronisation if a loss of synchronisation has occurred on the TE-UE link. + +#### 5.2.7.1 Control-octet transparency + +The following transparency mechanism shall be applied to each frame from address field to FCS field inclusive. + +The control escape octet is a transparency identifier that identifies an octet occurring within a frame to which the following transparency procedure is applied. The encoding of the control escape octet is: + +| | | | | | | | | | | +|--|---|---|---|---|---|---|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | Bit position in octet | +| | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | Diagram showing an arrow pointing from the text 'Low-order bit, first bit transmitted/received' to the bit '1' at position 1.
Low-order bit, first bit transmitted/received | + +The transmitter shall examine the frame between the opening and closing flag sequences including the address, control, and FCS fields and, following completion of the FCS calculation, shall: + +- Upon the occurrence of the flag or a control escape octet, complement the 6th bit of the octet; and +- Insert a control escape octet immediately preceding the octet resulting from the above prior to transmission. + +The receiver shall examine the frame between the two flag octets and shall, upon receipt of a control escape octet and prior to FCS calculation: + +- Discard the control escape octet; and +- Restore the immediately following octet by complementing its 6th bit. + +Other octet values may optionally be included in the transparency procedure by the transmitter. Such inclusion shall be subject to prior system/application agreement. + +#### 5.2.7.2 Start/stop transmission - extended transparency + +The transmitter may apply the above transparency procedure to other octets in addition to the flag and control escape octets. At present, the only other octets are flow-control characters. The procedure is described in clause 5.2.6.3. + +#### 5.2.7.3 Flow-control transparency + +The flow-control transparency option provides transparency processing for the DC1/XON and DC3/XOFF control characters defined in ISO/IEC 646 (i.e., 1000100x and 1100100x, respectively, where x may be either 0 or 1). This has the effect of assuring that the octet stream does not contain values which could be interpreted by intermediate equipment as flow control characters (regardless of parity). + +#### 5.2.7.4 Frame Structure + +The frame structure is shown in figure 7. Note that this structure does not include information added for synchronisation (i.e. Start and stop bits) or transparency purposes. The order of transmission is from left to right. + +In case the Transparency mechanism is activated, the frame structure is as follows. + +| Flag | Address | Control | Information | FCS | Flag | +|---------|---------|---------|--------------------------------------------------|---------|---------| +| 1 octet | 1 octet | 1 octet | Unspecified length but integral number of octets | 1 octet | 1 octet | + +**Figure 7: Frame Structure for Advanced option** + +The flag field in advanced option has the following format. + +| | | | | | | | | | +|-----|---|---|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | + +**Figure 8: Flag field in advanced option** + +NOTE: The closing flag may also be the opening flag of the following frame. + +## 5.3 Frame Types + +### 5.3.1 Set Asynchronous Balanced Mode (SABM) command + +The SABM command shall be used to place the addressed station in the Asynchronous Balanced Mode (ABM) where all control fields shall be one octet in length. The station shall confirm acceptance of the SABM command by transmission of a UA response at the first opportunity. Upon acceptance of this command, the DLC send and receive state variables shall be set to zero. + +### 5.3.2 Unnumbered Acknowledgement (UA) response + +The UA response shall be used by the station to acknowledge the receipt and acceptance of SABM and DISC commands. + +### 5.3.3 Disconnected Mode (DM) response + +The DM response shall be used to report a status where the station is logically disconnected from the data link. When in disconnected mode no commands are accepted until the disconnected mode is terminated by the receipt of a SABM command. If a DISC command is received while in disconnected mode a DM response should be sent. + +### 5.3.4 Disconnect (DISC) command + +The DISC command shall be used to terminate an operational or initialization mode previously set by a command. It shall be used to inform one station that the other station is suspending operation and that the station should assume a logically disconnected mode. Prior to actioning the command, the receiving station shall confirm the acceptance of the DISC command by the transmission of a UA response. + +DISC command sent at DLCI 0 have the same meaning as the Multiplexer Close Down command (see clause 5.4.6.3.3). See also clause 5.8.2 for more information about the Close-down procedure. + +### 5.3.5 Unnumbered information with header check (UIH) command and response + +The UIH command/response shall be used to send information without affecting the V(S) or V(R) variables at either station. UIH is used where the integrity of the information being transferred is of lesser importance than its delivery to the correct DLCI. For the UIH frame, the FCS shall be calculated over only the address, control and length fields. + +Reception of the UIH command/response is not sequence number verified by the data link procedures; therefore, the UIH frame may be lost if a data link exception occurs during transmission of the protected portion of the command, or duplicated if an exception condition occurs during any reply to the command. There is no specified response to the UIH command/response. + +### 5.3.6 Unnumbered Information (UI) command and response + +The UI command/response shall be used to send information without affecting the V(S) or V(R) variables at either station. Reception of the UI command/response is not sequence number verified by the data link procedures; therefore, the UI frame may be lost if a data link exception occurs during transmission of the protected portion of the command, or duplicated if an exception condition occurs during any reply to the command. There is no specified response to the UI command/response. + +For the UI frame, the FCS shall be calculated over all fields (Address, Control, Length Indicator, Information). + +Support of UI frames is optional. + +## 5.4 Procedures and States + +### 5.4.1 DLC Establishment + +In most cases the establishment of a DLC will be initiated by the TE, however, the protocol is balanced and the initiation may come from the UE. The action taken by the higher layers of the TE upon the initiation of the establishment of a DLC from the UE is outside the scope of the present document. + +The station wishing to establish a DLC transmits a SABM frame with the P-bit set to 1. The address field contains the DLCI value associated with the desired connection. If the responding station is ready to establish the connection it will reply with a UA frame with the F-bit set to 1. If the responding station is not ready or unwilling to establish the particular DLC it will reply with a DM frame with the F-bit set to 1. + +Once a DLC has been established the stations are both said to be in a connected mode, for the particular DLC, and transfer of information may commence. + +If no UA or DM response has been received after T1 the initiating station may retransmit the SABM. This action may be repeated until a response is obtained or action is taken by a higher layer. + +If no negotiation procedure is used, DLC parameters are the default one. + +### 5.4.2 DLC Release + +The release of a DLC may be initiated by either station by the transmission of a DISC frame with the P-bit set to one. Confirmation of the DLC release is signalled by the other station sending a UA frame with the F-bit set to 1. Once the DLC has been released the stations enter disconnected mode for that particular DLC. + +If the station receiving the DISC command is already in a disconnected mode it will send a DM response. + +If no UA or DM response has been received after T1 the initiating station may retransmit the DISC. This action may be repeated until a response is obtained or action is taken by a higher layer. + +### 5.4.3 Information Transfer + +#### 5.4.3.1 Information Data + +Information is conveyed using UI or UIH frames. Support of UIH frames is mandatory and support of UI frames is optional. UI frames are used when it is important to know that data received is correct. An example of the use of UI frames is in carrying IP (Internet Protocol) traffic where error recovery procedures are performed, if necessary, by a + +higher layer. The use of UIH frames is appropriate if the link is not subject to errors. UI or UIH frames may also be used for data in situations where the delays inherent in error-recovery procedures are unacceptable, such as transmission of voice data. + +The transmitter takes information from the convergence layer for the particular DLC and places it in the I-field of the transmitted frame. Once a UI or UIH frame has been correctly received, the contents of its I-field is passed to the convergence layer. + +The frames sent by the initiating station have the C/R bit set to 1 and those sent by the responding station have the C/R bit set to 0. Both stations set the P-bit to 0. + +See clause 5.2.1.2 for more details about C/R bit. + +The maximum length of the information field in UI or UIH frames shall be parameter N1 (see clause 5.7.2). + +#### 5.4.3.2 Priority + +Each data stream has a priority associated with it. The priority is a number in the range 0-63 with lower numbers having higher priority. The TE assigns a priority to each DLC and informs the UE of the priority by means of the multiplexer control channel (see clause 5.4.6.3.1). In the absence of a message assigning priorities DLCs shall be given the priority according to the DLCI Assignment table in clause 5.6. The transmitter is in control of which frames are transmitted and how they are constructed and it is not intended to specify precisely how this task is performed. If data of higher priority than that currently being transmitted is waiting the transmitter has several options available: + +- a) complete the transmission of the current frame; or +- b) terminate the assembly of the current frame by sending the current FCS and terminating flag (only for Advanced option); + +and start sending the frame of higher-priority data. + +Handling of DLC with equal priorities should not favour one over the others. The DLC with the highest priority shall not block any of the lower priorities DLC. Interleaving of higher priority and lower priority frames is necessary in order to avoid permanent blocking of lower priority channels. Optimization of this interleaving for a specific implementation may have a significant impact on the application in use and therefore implementers are encouraged to consider this carefully. + +### 5.4.4 Frame Variables + +The poll (P) bit set to 1 shall be used by a station to solicit (poll) a response or sequence of responses from the other station. + +The final (F) bit set to 1 shall be used by a station to indicate the response frame transmitted as the result of a soliciting (poll) command. + +The poll/final (P/F) bit shall serve a function in both command frames and response frames. (In command frames, the P/F bit is referred to as the P bit. In response frames, it is referred to as the F bit). + +#### 5.4.4.1 Functions of the poll bit + +The P bit set to 1 shall be used to solicit a response frame with the F bit set to 1 from the other station at the earliest opportunity. + +On a particular DLCI, only one frame with a P bit set to 1 shall be outstanding in a given direction at a given time. + +In the case where a SABM or DISC command with the P bit set to 0 is received then the received frame shall be discarded. + +If a unsolicited DM response is received then the frame shall be processed irrespective of the P/F setting. + +Before a station issues another frame with the P bit set to 1, it shall have received a response frame from the other station with the F bit set to 1. If no valid response frame is obtained within a system-defined time-out period, the retransmission of a command with the P bit set to 1 for error recovery purposes shall be permitted. + +#### 5.4.4.2 Functions of the final bit + +A response frame with the F bit set to 1 shall be used by a station to acknowledge the receipt of a command frame with the P bit set to 1. The response shall be made at the earliest opportunity. + +The station may transmit response frames with the F bit set to 0 at any opportunity on an asynchronous basis. However, in the case where a UA response is received with the F bit set to 0 then the received frame shall be discarded. + +If an unsolicited DM response is received then the frame shall be processed irrespective of the P/F setting. + +If a station receives a command with the P bit set to 1, transmission of a response with the F bit set to 1 shall take precedence over transmission of other commands, with the exception of the mode setting commands (SABM or DISC). + +### 5.4.5 Time-out considerations + +In order to detect a no-reply or lost-reply condition, each station shall provide a response time-out function (T1). The expiry of the time-out function shall be used to initiate appropriate error recovery procedures. + +The duration of the time-out function in the two stations shall be unequal in order to resolve contention situations. + +The time-out function shall be started whenever a station has transmitted a frame for which a reply is required. When the expected reply is received, the time-out function shall be stopped. If, during the interval that the time-out function is running, other frames are sent for which acknowledgements are required, the time-out function may have to be restarted. + +If the response time-out function runs out, a command with the P bit set to 1 may be (re)transmitted, and the response time-out function restarted. + +### 5.4.6 Multiplexer Control Channel + +At the initiation of communication between the TE and UE a control channel is set up with DLCI 0 using the procedures of clause 5.8.1. This channel is used to convey information between the two multiplexers. The control channel may use either error recovery mode or non-error recovery mode procedures as defined by the +CMUX command (3GPP TS 27.007 [4]). If error recovery mode procedures are available they should be used. + +#### 5.4.6.1 Message format + +All messages sent between the multiplexers conform to the following type, length, value format: + +| Type | Length | Value 1 | Value2 | ... | Value n | +|------|--------|---------|--------|-----|---------| +|------|--------|---------|--------|-----|---------| + +Each box in the diagram represents a field of minimum size one octet. The type and length octets have extension bits so those fields may contain more than one octet. + +The first type field octet has the following format: + +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-----|----|-----|----|----|----|----|----|----| +| | EA | C/R | T1 | T2 | T3 | T4 | T5 | T6 | + +Subsequent type field octets have the following format: + +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-----|----|----|----|----|-----|-----|-----|-----| +| | EA | T7 | T8 | T9 | T10 | T11 | T12 | T13 | + +The EA bit is an extension bit. The EA bit is set to 1 in the last octet of the sequence; in other octets EA is set to 0. If only one octet is transmitted EA is set to 1. + +The C/R bit indicates whether the message is a command or a response. + +The T bits indicate the type coding. Each command has a unique pattern of bits. This means that a single-octet type field can encode 63 different message types. Only single octet message types are defined in the present document. + +The first length field octet has the following structure: + +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-----|----|----|----|----|----|----|----|----| +| | EA | L1 | L2 | L3 | L4 | L5 | L6 | L7 | + +Subsequent length field octets have the same structure. + +The EA bit is an extension bit. The EA bit is set to 1 in the last octet of the sequence; in other octets EA is set to 0. If only one octet is transmitted EA is set to 1. + +The L bits define the number of value octets that follow. In the case of a single-octet length field L1 is the LSB and L7 is the MSB; this permits messages with up to 127 value octets to be constructed. + +The contents of the value octets are defined for each message type in clause 5.4.6.3. + +Multiple messages may be included in the same frame (as long as the maximum frame size is not exceeded). Messages may not be split over more than one frame. + +#### 5.4.6.2 Operating procedures + +Messages always exist in pairs; a command message and a corresponding response message. If the C/R bit is set to 1 the message is a command, if it is set to 0 the message is a response. A response message has the same T bits as the command that provoked it. + +If a command does not produce a response within a time T2 the command may be sent again up to N2 times. If no response is received on the N2 transmissions, the multiplexer control channel should be considered faulty and an alarm raised. Resolution of the error situation is implementation dependent. + +NOTE: Notice that when UIH frames are used to convey information on DLCI 0 there are at least two different fields that contain a C/R bit, and the bits are set of different form. The C/R bit in the Type field shall be set as it is stated above, while the C/R bit in the Address field (see clause 5.2.1.2) shall be set as it is described in clause 5.4.3.1. + +#### 5.4.6.3 Message Type and Actions + +##### 5.4.6.3.1 DLC parameter negotiation (PN) + +This procedure is optional. If this command is not supported, default values are applied to each DLC. + +Before a DLC is set up using the mechanism in clause 5.4.1, the TE and UE must agree on the parameters to be used for that DLC. These parameters are determined by parameter negotiation. + +The parameter negotiation uses the following type field octet: + +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-----|----|-----|---|---|---|---|---|---| +| | EA | C/R | 0 | 0 | 0 | 0 | 0 | 1 | + +The length field octet contains the value 8 and there follow eight value octets. The value octets contain the information in table 3. + +**Table 3: Parameter Negotiation** + +| Value Octet | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | +|-------------|-------|-------|-------|-------|-------|-------|-------|-------| +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | 0 | 0 | +| 2 | I1 | I2 | I3 | I4 | CL1 | CL2 | CL3 | CL4 | +| 3 | P1 | P2 | P3 | P4 | P5 | P6 | 0 | 0 | +| 4 | T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | +| 5 | N1 | N2 | N3 | N4 | N5 | N6 | N7 | N8 | +| 6 | N9 | N10 | N11 | N12 | N13 | N14 | N15 | N16 | +| 7 | NA1 | NA2 | NA3 | NA4 | NA5 | NA6 | NA7 | NA8 | +| 8 | K1 | K2 | K3 | 0 | 0 | 0 | 0 | 0 | + +The various fields are coded as follows: + +- the D-bits define the DLCI that the other information refers to; Bit D1 is the least significant; +- the I-bits define the type of frames used for carrying information in the particular DLC - See table 4. + +**Table 4: Meaning of I-bits** + +| Meaning | I1 | I2 | I3 | I4 | +|--------------------------|----|----|----|----| +| Use UIH frames | 0 | 0 | 0 | 0 | +| Use UI frames | 1 | 0 | 0 | 0 | +| Use I frames (note) | 0 | 1 | 0 | 0 | +| NOTE: Refer to clause 6. | | | | | + +Other values are reserved. Default value is 0000. + +In the absence of negotiation the frame type used (for DLCI>0) is the same as used by the multiplexer control channel. + +The CL-bits define the type of convergence layer to be used on the particular DLCI - see table 5. + +**Table 5: Meaning of CL-bits** + +| Meaning | CL1 | CL2 | CL3 | CL4 | +|---------|-----|-----|-----|-----| +| Type 1 | 0 | 0 | 0 | 0 | +| Type 2 | 1 | 0 | 0 | 0 | +| Type 3 | 0 | 1 | 0 | 0 | +| Type 4 | 1 | 1 | 0 | 0 | + +Other values are reserved. Default value is 0000. + +The P-bits define the priority to be assigned to the particular DLC. The range of values is 0 to 63 with 0 being the lowest priority. P1 is the least significant bit. Default value for P-bits are given by the DLCI values. See clause 5.6. + +The T-bits define the value of the acknowledgement timer (T1) - see clause 5.7.1. The units are hundredths of a second and T1 is the least significant bit. + +The N-bits define the maximum frame size (N1) - see clause 5.7.2. The parameter is a sixteen-bit number with N1 as the least significant bit. + +The NA-bits define the maximum number of retransmissions (N2) - see clause 5.7.3. The parameter is an eight-bit number with NA1 as the least significant bit. + +The K-bits define the window size for error recovery mode (k) - see clause 5.7.4. The parameter is a three-bit number with K1 as the least significant bit. + +The TE transmits a parameter negotiation command to the UE with the fields set to the values that the TE intends to use for the particular DLCI. The UE replies with a parameter negotiation response with its proposed set of values. The following rules must be observed by the UE in constructing its response: + +- The DLCI value may not be changed. +- The use of I frames or UI frames is optional so an UE may respond with a UIH choice if it does not implement UI frames or I frames. +- The UE may not change the convergence layer proposed by the TE. +- The UE may not change the priority proposed by the TE. +- The T1 value is the one that the TE will use and is not negotiable; the UE will insert its own T1 value. It is advisable that different T1s are used in each direction. +- The UE may propose a smaller value for maximum frame size (N1) if it has insufficient memory to handle the size proposed. + +- The N2 value is the one that the TE will use and is not negotiable; the UE will insert its own N2 value. +- The UE may propose a smaller value for window size (k) if it has insufficient memory to handle the size proposed. + +If the TE considers the response from the UE to be acceptable the TE will start to establish the DLC in accordance with the procedures of clause 5.3.1. If the response is not acceptable the TE may initiate another parameter negotiation command with revised parameters or pass the failure information to a higher layer. + +If an incoming call arrives at the UE from the network for which no DLC has been set up, the UE may initiate the parameter negotiation procedure and set up a DLC. This situation should not occur in practice since a TE will generally set up DLCs for all the functions it shares with the UE after the capabilities exchange. The indication of an incoming call will be through an 07.07 or 07.05 result code. + +##### 5.4.6.3.2 Power Saving Control (PSC) + +(see also clause 5.4.7). + +The power saving control messages use the following type field octet: + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 0 | 0 | 1 | 0 | + +The length byte contains the value 0 and there are no value octets. + +If a station wishes to enter a low-power state it transmits a power saving control command; the other station replies with a power saving control response. + +If a station wishes to request that the other station enter a low-power state it sends a power saving control command; the other station replies with a power saving control response. The responding station may enter a low-power state but need not do so. + +##### 5.4.6.3.3 Multiplexer close down (CLD) + +(see also clause 5.8.2). + +The multiplexer close down command is used to reset the link into normal AT command mode without multiplexing. + +The multiplexer close down messages use the following type field octet: + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 0 | 0 | 1 | 1 | + +The length byte contains the value 0 and there are no value octets. + +##### 5.4.6.3.4 Test Command (Test) + +The test command is used to test the connection between UE and the TE. The length byte describes the number of value bytes, which are used as a verification pattern. The opposite entity shall respond with exactly the same value bytes. + +The type field octet has the following format: + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 0 | 1 | 0 | 0 | + +##### 5.4.6.3.5 Flow Control On Command (FCon) + +The flow control command is used to handle the aggregate flow. When either entity is able to receive new information it transmits this command. + +The length byte contains the value 0 and there are no value octets. + +The type field octet has the following format: + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 0 | 1 | 0 | 1 | + +##### 5.4.6.3.6 Flow Control Off Command (FCoff) + +The flow control command is used to handle the aggregate flow. When either entity is not able to receive information it transmits the FCoff command. The opposite entity is not allowed to transmit frames except on the control channel (DLC=0). + +The length byte contains the value 0 and there are no value octets. + +The type field octet has the following format: + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 0 | 1 | 1 | 0 | + +##### 5.4.6.3.7 Modem Status Command (MSC) + +It is desired to convey virtual V.24 control signals to a data stream, this is done by sending the MSC command. The MSC command has one mandatory control signal byte and an optional break signal byte. This command is only relevant when the basic option is chosen. + +This command shall be sent prior to any user data after a creation of a DLC. + +| Command | Length | DLCI | V.24 signals | Break Signals (optional) | +|---------|--------|------|--------------|--------------------------| +|---------|--------|------|--------------|--------------------------| + +The length byte contains the value 2 or 3 and there are 2 or 3 value octets. + +Both the DTE and DCE uses this command to notify each other of the status of their own V.24 control signals. The length of the Modem Status Command is either 4 or 5 bytes depending on the break signal. + +The command field octet has the following format: + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 0 | 1 | 1 | 1 | + +The C/R bit is used to indicate if it is a Modem Status Command or Modem Status Response. + +Every time the signals change, the DTE or DCE sends this command to indicate the current status of each signal. When a DTE or DCE receives a Modem Command it always sends a Response back. The mappings of the V.24 signals to the bits in the control signal octet for the receiver and sender are given in tables 6 and 7, respectively. + +In a Modem Status Command it is the status of the sender's own V.24 signals that shall be sent, but in a Response it is copy of the V.24 signals that are received from the Command frame that shall be returned. + +The DLCI field identifies the specific DLC to which the command applies. Bit 2 is always set to 1 and the EA bit is set according to the description in clause 5.2.1.2. + +| | | | | | | | | | +|---------|----|---|-------|---|---|---|---|---| +| Bit No. | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | 1 | D L C | | | I | | | + +**Figure 9: Format of Address Field** + +The DLCI field is followed by the control signals field which contains a representation of the state of the signals in accordance with figure 10. The use of the extension bit allows other octets to be added to cater for other circumstances. At present, an optional second octet is defined for handling the transmission of break signals. + +| Bit No | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|--------|----|----|-----|-----|------------|------------|----|----| +| Signal | EA | FC | RTC | RTR | reserved 0 | reserved 0 | IC | DV | + +**Figure 10: Format of control signal octet** + +Description of the control signal byte: + +Bit 1. The EA bit is set to 1 in the last octet of the sequence; in other octets EA is set to 0. If only one octet is transmitted EA is set to 1. + +Bit 2. Flow Control (FC). The bit is set to 1 (one) when the device is unable to accept frames. + +Bit 3. Ready To Communicate (RTC). The bit is set to 1 when the device is ready to communicate. + +Bit 4. Ready To Receive (RTR). The bit is set to 1 when the device is ready to receive data. + +Bit 5. Reserved for future use. Set to zero by the sender, ignored by the receiver. + +Bit 6. Reserved for future use. Set to zero by the sender, ignored by the receiver. + +Bit 7. Incoming call indicator (IC). The bit is set to 1 to indicate an incoming call. + +Bit 8. Data Valid (DV). The bit is set to 1 to indicate that valid data is being sent. + +The control byte is mapped to V.24 signals according to the tables below: + +**Table 6: Mapping from the control signal octet by a receiving entity** + +| Control Signal Byte
bit number, name | DTE receiving | | DCE receiving | | +|-----------------------------------------|---------------|--------------|---------------|--------------| +| | signal | V.24 circuit | signal | V.24 circuit | +| 3, RTC | DSR | 107 | DTR | 108/2 | +| 4, RTR | CTS | 106 | RFR (note) | 133 | +| 7, IC | RI | 125 | -ignored | - | +| 8, DV | DCD | 109 | -ignored | - | + +NOTE: Circuit 133, RFR (Ready for Receiving) is commonly assigned to the connector pin that is alternatively used for circuit 105, RTS. It is sometimes referred to by that name. + +**Table 7: Mapping to the control signal octet by a sending entity** + +| Control Signal Byte
bit number, name | DTE sending | | DCE sending | | +|-----------------------------------------|-------------|--------------|-------------|--------------| +| | signal | V.24 circuit | signal | V.24 circuit | +| 3, RTC | DTR | 108/2 | DSR | 107 | +| 4, RTR | RFR (note) | 133 | CTS | 106 | +| 7, IC | always 0- | - | RI | 125 | +| 8, DV | always 1- | - | DCD | 109 | + +NOTE: Circuit 133, RFR (Ready for Receiving) is commonly assigned to the connector pin that is alternatively used for circuit 105, RTS. It is sometimes referred to by that name. + +If a station is unable to transmit frames because of flow control but wishes to stop accepting further frames itself, it may still send frames containing no user data (i.e. Only the control signal octet and, optionally, the break signal octet) in order to signal flow control. + +The EA bit is set to 1 in the last octet of the sequence; in other octets EA is set to 0. If only one octet is transmitted EA is set to 1. + +| Bit No | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|--------|----|----|----|----|----|----|----|----| +| Signal | EA | B1 | B2 | B3 | L1 | L2 | L3 | L4 | + +**Figure 11: Format of Break signal octet (Optional)** + +The break signal octet carries information about a break signal detected in the data stream for the DLC. The meanings of the bits are shown in table 8. + +**Table 8: Break signal octet meanings** + +| Bit | Value | Meaning | +|-------|-------------|---------------------------------------------------| +| B1 | 1 | Octet encodes a break signal | +| | 0 | Octet does not encode a break signal | +| B2 | 0 | reserved: set to 0 by sender, ignored by receiver | +| B3 | 0 | reserved: set to 0 by sender, ignored by receiver | +| L1-L4 | 4-bit value | Length of break in units of 200ms | + +L1 is the least significant bit and L4 is the most significant bit of the break length. + +When a station receives a break octet it shall process the information and pass it on in an appropriate way. This is outside the scope of the present document. + +##### 5.4.6.3.8 Non Supported Command Response (NSC) + +This response is sent whenever a command type is not supported by the receiving entity. + +The length byte contains the value 1 and there is one value octets. + +The type field octet has the following format: + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 1 | 0 | 0 | 0 | + +The value octet contains the Command Type of the non supported command. + +The value octet has the following format: + +| | | | | | | | | | +|-----|----|-----|--------------|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | Command Type | | | | | | + +The C/R bit (in the value octet above) shall be set to the same value as the C/R bit in the type field octet of the not supported command frame. + +##### 5.4.6.3.9 Remote Port Negotiation Command (RPN) + +This command is optional. + +This command is used for set the remote port communication settings. + +All devices must assure that the communication settings are correctly set, prior sending data. There are default values assigned on all parameters, if no negotiation is performed, the default value is chosen. + +During a connection, a device must send the RPN whenever the communication settings are changed. The same applies for the Port Line Status. + +| | | | | | | | | | | +|-------------|---------------|------------------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------| +| Command RPN | Length 1 or 8 | Value octet1 optional (DLCI) | Value octet2 optional | Value octet3 optional | Value octet4 optional | Value octet5 optional | Value octet6 optional | Value octet7 optional | Value octet8 optional | +|-------------|---------------|------------------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------|-----------------------| + +The Remote Port Negotiation Command use the following type field octet: + +**Table 9: Type field octet** + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 1 | 0 | 0 | 1 | + +The length byte contains the value 1 or 8 and there are one or eight value octets. + +**Table 10: DLCI octet** + +| | | | | | | | | | +|---------|----|---|---|---|---|---|---|---| +| Bit No. | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | 1 | | D | L | C | I | | + +Bit 2 in the DLCI octet is not used and always set to 1, the EA bit is according to the description in clause 5.2.1.2. The DLCI field indicated which DLC the command is applied to. + +**Table 11: Port Value Octets** + +| Value Octet | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | +|-------------|-------|-------|-------|-------|-------|-------|-------|-------| +| 2 | B1 | B2 | B3 | B4 | B5 | B6 | B7 | B8 | +| 3 | D1 | D2 | S | P | PT1 | PT2 | res | res | +| 4 | FLC1 | FLC2 | FLC3 | FLC4 | FLC5 | FLC6 | res | res | +| 5 | XON1 | XON2 | XON3 | XON4 | XON5 | XON6 | XON7 | XON8 | +| 6 | XOF1 | XOF2 | XOF3 | XOF4 | XOF5 | XOF6 | XOF7 | XOF8 | +| 7 | PM1 | PM2 | PM3 | PM4 | PM5 | PM6 | PM7 | PM8 | +| 8 | PM9 | PM10 | PM11 | PM12 | PM13 | PM14 | PM15 | PM16 | + +A device transmits a remote port negotiation command to the other device with the fields set to the desired values with the parameter mask indicating which parameters are set. + +When the remote port negotiation command is received, the responding station replies according to the following rules: + +The DLCI value may not be changed. + +The receiver may accept the Port Value Octet bits proposed by the sender, and reply with a response with the parameter mask set to 1 for all the parameters accepted. If the receiver does not support any of the proposed values, it replies with the parameter mask set to zero for the parameters not supported. For those parameters with the parameter mask set to 1, the new value is accepted and used. + +If the receiver does not support any of the proposed values indicated by the parameter mask, the receiver replies with the Remote Parameter Negotiation response with the parameter mask set to zero. + +If only one value byte is included in the command, it is interpreted as a request, and the receiver shall respond with the current Port Values setting. + +If the sender considers the response to be acceptable, that is, the bits match, the sender will start to use the DLC according to the Port Value Octets. If the response is not acceptable the sender may initiate another remote port negotiation command with revised parameters until a final agreement is reached or pass the failure information to a higher layer. + +The B1-B8 indicates the baudrate, see table 12. + +**Table 12: Meaning of B-bits** + +| Meaning | B1 | B2 | B3 | B4 | B5 | B6 | B7 | B8 | +|---------------|----|----|----|----|----|----|----|----| +| 2 400 bit/s | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 4 800 bit/s | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 7 200 bit/s | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | +| 9 600 bit/s | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | +| 19 200 bit/s | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | +| 38 400 bit/s | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | +| 57 600 bit/s | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | +| 115 200 bit/s | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | +| 230 400 bit/s | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | + +All other values of the B-bits are reserved. + +The default value is 1100 0000 (9600). + +The D1-D2 indicates the number of data bits: + +D1, D2 + +00 5 bits + +01 6 bits + +10 7 bits + +11 8 bits - default + +The S bit indicate number of stop bits: S=0: 1 stop bit, S=1: 1,5 stop bits. Default value = 0 (1 stop bit). + +The P bit indicate the parity. P=0: no parity, P=1: parity. Default value = 0 (no parity). + +The PT1 - PT2 indicates the parity type: + +PT1,PT2 + +00 odd parity + +01 even parity + +10 mark parity + +11 space parity + +FLC1-FLC6: (Default value=0, no flow control) + +Bit1 XON/XOFF on input + +Bit2 XON/XOFF on output + +Bit3 RTR on input + +Bit4 RTR on output + +Bit5 RTC on input + +Bit6 RTC on output + +NOTE: The RTR is mapped to either CTS (circuit 106) or RFR (circuit 133). The RTC is mapped to either DTR (circuit 108/2) or DSR (circuit 107). (Circuit 133, RFR(Ready for Receiving) is commonly assigned to the connector pin that is alternatively used for circuit 105, RTS. It is sometimes referred to by that name). + +XON1-XON8: XON character (default DC1) + +XOF1-XOF8: XOFF character.(default DC3) + +PM1-PM8: Parameter mask + +The parameter mask is used to indicate which parameters in the Remote Port Negotiation command are negotiated. For a command, the parameter mask shall be interpreted as follows: + +0=no change + +1= change. + +For a response the following values applies: + +0=not accepted proposal + +1= accepted proposal, and the new values are used. + +The bit mask for the value octets 7 and 8 are shown below: + +Bit1 bit rate + +Bit2 data bits + +Bit3 stop bits + +Bit4 Parity + +Bit5 parity type + +Bit6 XON character + +Bit7 XOF character + +Bit8 reserved + +PM9-PM16: Parameter mask continued + +Bit1 XON/XOFF on input + +Bit2 XON/XOFF on output + +Bit3 RTR on input + +Bit4 RTR on output + +Bit5 RTC on input + +Bit6 RTC on output + +All reserved values are set to 0 (zero) by the sender and ignored by the receiver. + +##### 5.4.6.3.10 Remote Line Status Command(RLS) + +This command is optional. + +This command is used for indicate remote port line status. + +During a connection, a device must send the RLS whenever the Remote Port Line Status are changed. + +The Remote Line Status command use the following type field octet. + +**Table 13: Type field octet** + +| | | | | | | | | | +|-----|----|-----|---|---|---|---|---|---| +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | 0 | 0 | 1 | 0 | 1 | 0 | + +The length byte contains the value 2 and there are two value octets. + +**Table 14: DLCI octet** + +| | | | | | | | | | +|---------|----|-----|---|---|---|---|---|---| +| Bit No. | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | EA | C/R | | D | L | C | I | | + +The C/R bit in the DLCI octet is not used and always set to 1, the EA bit is according to the description in clause 5.2.1.2. + +**Table 15: Remote Line Status Octets** + +| Value Octet | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | +|-------------|-------|-------|-------|-------|-------|-------|-------|-------| +| 1 | L1 | L2 | L3 | L4 | res | res | res | res | + +A device transmits a remote line status command to the other device with the fields set to the desired value. When the remote line status command is received, the remote device must respond with a Remote Line Status Response containing the values that it received. + +The L1-L4 bits indicates the Line Status. If L1 is set to 0, no error have occurred. L1 = 1 indicates the following errors: + +L2-L4: + +- 100 Overrun Error - Received character overwrote an unread character +- 010 Parity Error - Received character's parity was incorrect +- 001 Framing Error - a character did not terminate with a stop bit + +The res bits are set to zero for the sender and ignored by the receiver. + +##### 5.4.6.3.11 Service Negotiation Command (SNC) + +This command is used to query and set a specific service on a specific DLC. It is for instance used to set specific digital voice types. + +In some situations it is not very suitable to mix AT commands and raw data on the same DLC. For those situations, special DLCs can be established and converted to carry a specific data type. Examples of situation where this is especially useful is for voice transportation, where the AT commands controlling the connection (for instance for multiparty) are transported on one DLC and voice data carried by another DLC. This mechanism can be seen as an alternative to sending escape sequences with AT commands in the data flow. If this command is not used, the DLC is by default set to normal AT command mode. If this command is used, the DLC indicated in the DLCI octet, is converted to carry the specific data type. The originator of this command may also query the specific service on each DLCI. + +The service negotiation messages use the following format. + +**Table 16: Service Negotiation Command format** + +| Byte No. | 1 | 2 | 3 | 4 | 5 | +|----------|-----------------|--------|------|--------------------------------|------------------------------------| +| | Type field code | Length | DLCI | Service Value octet (optional) | Voice Codec Value octet (optional) | + +The type field octet: + +**Table 17: Type field octet** + +| Bit | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-----|----|-----|---|---|---|---|---|---| +| | EA | C/R | 0 | 0 | 1 | 0 | 1 | 1 | + +The length byte contains the value 1 or 3 and there are one or three value octets. + +**Table 18: DLCI octet** + +| Bit No. | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|---------|----|-----|---|---|---|---|---|---| +| | EA | C/R | | D | L | C | I | | + +The C/R bit in the DLCI octet is always set to 1 and the EA bit is according to the description in clause 5.2.1.2. + +**Table 19: Service Value Octets** + +| Value Octet | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | +|-------------|-------|-------|-------|-------|-------|-------|-------|-------| +| 1 | EA | S1 | S2 | S3 | S4 | S5 | S6 | S7 | + +The EA bit is according to the description in clause 5.2.1.2. + +**Table 20: Voice Codec Value Octets** + +| Value Octet | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | +|-------------|-------|-------|-------|-------|-------|-------|-------|-------| +| 1 | EA | V1 | V2 | V3 | V4 | V5 | V6 | V7 | + +The EA bit is according to the description in clause 5.2.1.2. + +**Table 21: Service Value Bits** + +| Value Bit | Service | +|-----------|----------| +| S1 | Data | +| S2 | Voice | +| S3 | Reserved | +| S4 | Reserved | +| S5 | Reserved | +| S6 | Reserved | +| S7 | Reserved | + +**Table 22: Voice Codec Value Bits** + +| Value Bit | Service | +|-----------|---------------------------------------------| +| V1 | Voice (coded – 3GPP TS 46.021) | +| V2 | Voice (coded - PCM 64 kbit/s U-law) | +| V3 | Voice (coded ADPCM 32kbit/s)
ITU-T G.726 | +| V4 | Voice (coded halfrate) | +| V5 | Voice (coded - PCM 64kbit/s A-law) | +| V6 | Voice (coded PCM 128kbit/s) | +| V7 | Reserved | + +The sender transmits a service negotiation command with the fields set to the values for all possible services it may use for the particular DLC. The receiver replies with a service negotiation response with its selected set of values. The following rules must be observed by the receiver in constructing its response: + +- the DLCI value may not be changed; +- the receiver may select a subset of the services proposed by the sender, but not a superset. It is the receiver's selection that is the valid one. If the receiver does not support any of the proposed services, it replies with the service byte set to zero; +- The Voice Codec Value Octet is always present even though data service is chosen. In this case, the Voice Codec Value Octet V1-V7 bits are set to zero. + +A zero value means standard AT command mode. + +If no value bytes are included in the command, it is interpreted as a request, and the receiver shall respond with all possible services. + +If the sender considers the response to be acceptable, that is, the service bits match, the sender will start to use the DLC according to the services. If the response is not acceptable the sender may initiate another parameter negotiation command with revised parameters until a final agreement is reached or pass the failure information to a higher layer. + +If no service negotiation has been performed on the DLCs, it operates in standard AT mode. In this case, an incoming call is indicated on that DLC. + +The sender shall set a reserved bit to value 0. The receiver shall ignore a reserved bit. + +### 5.4.7 Power Control and Wake-up Mechanisms + +It is very important in many types of UE and some TE that the power consumed by the equipment is minimised. This aim is often achieved by entering various power-saving states under conditions of inactivity, for example. The multiplexer system must be able to close down cleanly if either TE or UE wish to enter a low-power state. This is achieved by the use of the multiplexer control channel. + +If either TE or UE wishes to enter a low-power state a power saving control command message is sent to the other station on the multiplexer control channel. The station receiving the message will complete the transmission of any frames in progress, report a busy or power-down condition to higher layers, freeze all timers and transmit the power saving control response message. When the station that initiated the power saving control message receives the acknowledgement it is then free to enter the reduced-power state. + +Either station may send a power saving control command requesting that the other station enters a low power state. The responding station must acknowledge this command with a power saving control response message but need not obey the command to enter a low-power state. If no response is received the commanding station may repeat the command but must first use the wake-up procedure. + +Either station may initiate a wake-up from the reduced power state by the transmission of the wake-up signal which consists of continuous flag characters. When the other station receives the flag characters it will wake-up (if necessary) and start sending flag characters. When the first station receives these flag characters it will stop sending flags and start transmitting the first frame. When the second station detects a valid frame it stops sending flags. The stations unfreeze their timers and continue operation as before. + +If no response (continuous flags) is received to the wake-up procedure within time T3, an alarm should be raised to the higher layers and transmission of flags stops. + +### 5.4.8 Flow Control + +#### 5.4.8.1 RTR Flow Control + +Figure 12 shows a DTE connection to a DCE. The flow control scheme defined in this clause also applies to DTE - DTE connections. Both 27.010 entities are configured to use RTR (RFR/CTS) flow control. The flow control signal to the local application is a combination of the RTR signal from the opposite device together with three other flow control signals. The flow control signals labelled FCS1 - FCS3 are defined below: + +| | | +|------|------------------------------------------------------------------------------------------------------------------------------------| +| FCS1 | Bit 2 in the Modem Status Command or in the control signal octet in convergence layer type 2. Flow control per DLCI | +| FCS2 | Aggregate flow control in 27.010 via the control channel commands Fcon and Fcoff (basic option) or XON/XOFF in the advance option. | +| FCS3 | 27.010 internal buffer management (implementation specific) | + +The flow control signals FCS1-3 are combined with the RTR signal from the opposite 27.010 instance to create the local RTR input signal. E.g. the expression for the CTS signal for the emulated DTE serial port is: + +DTE.CTS=DCE.RTR AND FCS1 AND FCS2 AND FCS3 + +The flow control emulator duplicates the outgoing RTR signal in bit 2 (FC) and bit 4 (RTR) in the modem status command (when convergence layer 1,3 and 4 is used) or in bit 2 (FC) and bit 4 (RTR) in the control signal octet (when the convergence layer 2 is used). + +![Figure 12: RTR Flow Control diagram showing DTE and DCE components and their interactions.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates the RTR Flow Control mechanism between a DTE (Data Terminal Equipment) and a DCE (Data Circuit-terminating Equipment). The DTE contains an AND gate (&) and a Flow control emulation block. The DCE also contains a Flow control emulation block and an AND gate (&). The connections are as follows: + +- The DTE's Flow control emulation block receives DTE.RTS and DTE.CTS signals and outputs FCS2 and FCS3 signals. +- The DTE's AND gate (&) receives FCS1 and FCS2 signals and outputs the RTR signal. +- The DCE's Flow control emulation block receives the RTR signal and outputs DCE.RTS and DCE.CTS signals. +- The DCE's AND gate (&) receives FCS1 and FCS3 signals and outputs the RTR signal. + +Figure 12: RTR Flow Control diagram showing DTE and DCE components and their interactions. + +Figure 12: RTR Flow Control + +#### 5.4.8.2 XON/XOFF Flow Control + +Some 27.010 instance may detect XON/OFF characters coming from the local application when XON/XOFF is enabled. In this case the characters are acted upon, but not forwarded to the opposite 27.010 instance i.e. the XON/XOFF characters are filtered out and the flow control signal is transferred as a 27.010 flow signal, see figure 13. + +![Figure 13: XON/XOFF Flow Control on input diagram showing a DTE component.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +The diagram shows a DTE (Data Terminal Equipment) block. It contains a Flow control emulation block that receives the DTE.TxD signal and outputs the Tx.D signal and the FCS1 signal. + +Figure 13: XON/XOFF Flow Control on input diagram showing a DTE component. + +Figure 13: XON/XOFF Flow Control on input + +if XON/XOFF flow control is enabled on output then the 27.010 should use XON/XOFF characters to exercise flow control to the local application i.e XON/XOFF characters are inserted into the data stream depending on the 27.010 flow control signals, see figure 14. + +![Figure 14: XON/XOFF Flow Control on output diagram showing a DTE component.](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +The diagram shows a DTE (Data Terminal Equipment) block. It contains a Flow control emulation block that receives the Rx.D signal and outputs the DTE.RxD signal. Below the Flow control emulation block is an AND gate (&) that receives FCS1, FCS2, and FCS3 signals and outputs the FCS1 signal to the Flow control emulation block. + +Figure 14: XON/XOFF Flow Control on output diagram showing a DTE component. + +Figure 14: XON/XOFF Flow Control on output + +## 5.5 Convergence Layers + +Convergence layers are defined to permit data which has implied structure to be conveyed through the multiplexer without losing the structure or other parameters which are associated with the data stream. Common uses of convergence layers are to carry the state of V.24 control signals through a DLC or to ensure that the boundaries of a coded voice frame are preserved. + +Convergence layers apply to data whether it is carried by error recovery mode or non-error recovery mode procedures. + +The use of particular convergence layers is implicitly linked to the DLCIs used but may be negotiated away from these defaults by the use of the multiplexer control channel. + +### 5.5.1 Type 1 - Unstructured Octet Stream + +Data which consists of an unstructured sequence of octets, for example, 64 kbit/s uncoded voice or normal asynchronous data without V.24 control signals, is inserted directly into the I-field. In this case, it could be said that the convergence layer is null. + +Type 1 is the default convergence layer for each DLC. + +### 5.5.2 Type 2 - Unstructured Octet Stream with flow control, break signal handling and transmission of V.24 signal states + +If it is desired to convey virtual V.24 control signals associated with a data stream the first octet of each I-field contains a representation of the state of the signals in accordance with figure 15. The use of the extension bit allows other octets to be added to cater for other circumstances. At present, an optional second octet is defined for handling the transmission of break signals. + +The mappings of the V.24 signals to the bits in the control signal octet for the receiver and sender are given in tables 23 and 24, respectively. + +| Bit No | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|--------|----|----|-----|-----|---------------|---------------|----|----| +| Signal | EA | FC | RTC | RTR | reserved
0 | reserved
0 | IC | DV | + +**Figure 15: Format of control signal octet** + +Description of the control signal byte: + +Bit 1. The EA bit is set to 1 in the last octet of the sequence; in other octets EA is set to 0. If only one octet is transmitted EA is set to 1. + +Bit 2. DLC (frame) Flow Control (FC). In non-ERM, it is set to 1 when the device is unable to accept frames . In ERM, it is always set to 0 by the sender and ignored by the receiver. + +Bit 3. Ready To Communicate (RTC). The bit is set to 1 when the device is ready to communicate. + +Bit 4. Ready To Receive (RTR). The bit is set to 1 when the device is ready to receive data. + +Bit 5. Reserved for future use. Set to zero by the sender, ignored by the receiver. + +Bit 6. Reserved for future use. Set to zero by the sender, ignored by the receiver. + +Bit 7. Incoming call indicator (IC). The bit is set to 1 to indicate an incoming call. + +Bit 8. Data valid (DV). The bit is set to 1 to indicate that valid data is being sent. + +The control byte is mapped to V.24 signals according to the tables below: + +**Table 23: Mapping from the control signal octet by a receiving entity** + +| Control Signal Byte | DTE receiving | | DCE receiving | | +|---------------------|------------------|--------------|------------------|--------------| +| | signal | V.24 circuit | signal | V.24 circuit | +| bit number, name | | | | | +| 2, FC | DLC flow control | - | DLC flow control | - | +| 3, RTC | DSR | 107 | DTR | 108/2 | +| 4, RTR | CTS | 106 | RFR (note) | 133 | +| 7, IC | RI | 125 | ignored | - | +| 8, DV | DCD | 109 | ignored | - | + +NOTE: Circuit 133, RFR (Ready for Receiving) is commonly assigned to the connector pin that is alternatively used for circuit 105, RTS. It is sometimes referred to by that name. + +**Table 24: Mapping to the control signal octet by a sending entity** + +| Control Signal Byte | DTE sending | | DCE sending | | +|---------------------|--------------------|--------------|--------------------|--------------| +| | signal | V.24 circuit | signal | V.24 circuit | +| bit number, name | | | | | +| 2, FC | frame flow control | - | frame flow control | - | +| 3, RTC | DTR | 108/2 | DSR | 107 | +| 4, RTR | RFR (note) | 133 | CTS | 106 | +| 7, IC | always 0 | - | RI | 125 | +| 8, DV | always 1 | - | DCD | 109 | + +NOTE: Circuit 133, RFR (Ready for Receiving) is commonly assigned to the connector pin that is alternatively used for circuit 105, RTS. It is sometimes referred to by that name. + +In non-error recovery mode, the FC bit provides frame flow control for the DLC. If a station is unable to accept further frames, for example, because of buffer management issues, it shall set FC to 1. When the station is again able to receive frames it shall set FC to 0. If a station receives a frame with FC set to 1 it shall cease transmitting frames until it receives a frame with FC set to 0. + +If a station is unable to transmit frames because of flow control but wishes to stop accepting further frames itself, or to signal a change in the control signals or a break condition it may still send frames containing no user data (i.e. containing only the control signal octet and, optionally, the break signal octet). + +In error recovery mode the FC bit is not used and shall be set to 0 by the sender and ignored by the receiver. If a station has been prevented from sending I frames, for example, by receiving a RNR frame, it may still send a UI or UIH frame containing no user data if it wishes to signal a change in the control signals or a break condition. + +The EA bit is set to 1 in the last octet of the sequence; in other octets EA is set to 0. If only one octet is transmitted EA is set to 1. + +| Bit No | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|--------|----|----|----|----|----|----|----|----| +| Signal | EA | B1 | B2 | B3 | L1 | L2 | L3 | L4 | + +**Figure 16: Format of Break signal octet** + +The break signal octet carries information about a break signal detected in the data stream for the DLC. The meanings of the bits are shown in table 25. + +**Table 25: Break signal octet meanings** + +| Bit | Value | Meaning | +|-------|-------------|---------------------------------------------------| +| B1 | 1 | Octet encodes a break signal | +| | 0 | Octet does not encode a break signal | +| B2 | 1 | Discard data in buffers | +| | 0 | Do not discard data in buffers | +| B3 | 1 | Transmit break signal onwards as soon as possible | +| | 0 | Transmit break signal onwards in sequence | +| L1-L4 | 4-bit value | Length of break in units of 200ms | + +L1 is the least significant bit and L4 is the most significant bit of the break length. + +When a station receives a break octet it shall process the information and pass it on in an appropriate way. This is outside the scope of the present document. + +The remaining octets of the I-field contain data for that DLC. + +### 5.5.3 Type 3 - Uninterruptible Framed Data + +An example of uninterruptible framed data is coded voice data made up of a sequence of voice frames. It is important that coded voice frames reach the voice decoder with the frame structure intact and with the shortest possible delay. The simplest way of ensuring this is to map one complete voice frame into one I-field. This frame shall not be shortened during transmission even if data of higher priority is waiting. + +At the transmitter each frame of data is inserted into the I field of an I frame, UI frame or UIH frame. The data shall not be spread over more than one frame and data from other frames must not be included in the I field. The receiver handles the data as a complete frame and passes it on as a complete frame. + +Coded voice data should be transmitted using UI frames or UIH frames because the delays associated with re-transmissions are usually unacceptable. + +### 5.5.4 Type 4 - Interruptible Framed Data + +This type of convergence layer is used might be used to convey data which has an implied structure but where the delay is not as important as Type 3. The structured data may be segmented across several frames and re-assembled at the other station. PPP-framed IP data is an example of the type of data that could be carried over a Type 4 convergence layer. + +The first octet of every Type 4 frame is a control octet and is defined in figure 17. + +| Bit No | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|--------|----|---|---|---|---|---|---|---| +| Signal | EA | - | - | - | - | - | B | F | + +**Figure 17: Format of Type 4 octet** + +The EA bit is for future expansion if more than one octet is needed. It is set to 1 in the case described here. + +The B and F bits are used to indicate whether the frame is the first frame in a sequence, a middle frame or the last frame. The meanings of the bits are as shown in table 26. + +**Table 26: Meaning of B and F bits** + +| B | F | Meaning | +|---|---|---------------------------------------------| +| 1 | 0 | First frame of a sequence | +| 0 | 0 | Middle frame of a sequence | +| 0 | 1 | Last frame of a sequence | +| 1 | 1 | Data is contained entirely within one frame | + +NOTE 1: PPP-framed IP data can be carried using a Type 1 convergence layer if other framing structures, such as a layer 2 protocol, have already been included in the data stream. + +NOTE 2: If a frame is coded as being the last frame or that all the data is contained within one frame, that frame may then not be shortened because shortening would make the meaning of the header incorrect. It may be advisable to construct the last frame of a sequence such that it contains no data and avoid the use of the 11 code if frame shortening is desired. + +## 5.6 DLCI Values + +All DLCs use a type 1 convergence layer by default; the use of other layers may be negotiated using the multiplexer control channel. + +**Table 27: DLCI Assignments** + +| Usage | DLCI number (decimal) | Priority | +|-------------------------------|-----------------------|----------| +| Multiplexer control channel | 0 | 0 | +| AT commands (07.07 and 07.05) | 1-7 | 7 | +| AT commands (07.07 and 07.05) | 8-15 | 15 | +| AT commands (07.07 and 07.05) | 16-23 | 23 | +| AT commands (07.07 and 07.05) | 24-31 | 31 | +| AT commands (07.07 and 07.05) | 32-39 | 39 | +| AT commands (07.07 and 07.05) | 40-47 | 47 | +| AT commands (07.07 and 07.05) | 48-55 | 55 | +| AT commands (07.07 and 07.05) | 56-61 | 61 | +| Reserved | 62-63 | | + +DLCI value 62 is reserved and must be allocated for ETSI purposes of the BOFC and the EOFC in Basic option. + +DLCI value 63 is reserved and must not be allocated for ETSI purposes because of the special meaning in HDLC. + +DLCI value 0 is reserved for the control channel. + +The priority values in Table 27 apply in the absence of an explicit DLC priority assignment message. + +## 5.7 System Parameters + +The following system parameters are defined for the multiplexer. T1, N1, N2 and k may be negotiated by use of the multiplexer control channel or the default values given here should be used. T2 and T3 are set with the AT+CMUX command. + +### 5.7.1 Acknowledgement Timer (T1) + +The acknowledgement timer governs the amount of time that a station will wait for an acknowledgement before resorting to other action (e.g. transmitting a frame). The two stations may operate with different values of T1. + +The units are hundredths of a second. Times of up to 2,55 s may be used. + +The default value is 100 ms and the minimum is 10 ms. + +### 5.7.2 Maximum Frame Size (N1) + +N1 defines the maximum number of octets that may be contained in an information field. It does not include octets added for transparency purposes. + +The default value is 64 octets when the advanced option activated and 31 octets when it is not activated. The range is 1 to 32 768 octets. + +NOTE: The maximum frame size should be chosen carefully particularly if a Type 2 convergence layer is being used. The frame must be large enough to contain a complete protocol frame. + +### 5.7.3 Maximum number of retransmissions (N2) + +N2 defines the maximum number of times that a station re-attempt a procedure requiring a response. The two stations may operate with a different value of N2. + +The default value is 3 and the range is 0-255. + +### 5.7.4 Window Size (k) + +The window size parameter (k) defines the maximum number of I frames that a DLC can have outstanding (i.e. unacknowledged). Identical values need not be used for each direction. The window size may not be larger than 7. + +This parameter is only applicable when Error Recovery Option is activated. See clause 6. + +The default value is 2 and the range is 1-7. + +### 5.7.5 Response Timer for multiplexer control channel (T2) + +The T2 timer is the amount of time the multiplexer control channel waits before re-transmitting a command. + +T2 must be greater than T1. The units are hundredths of a second. Times of up to 2,55 s may be used. + +The default value is 300 ms and minimum 20 ms. + +### 5.7.6 Response Timer for wake-up procedure(T3) + +The T3 timer is the amount of time the transmitting station of a power wake-up command waits before raising an alarm when no response is received. The units are seconds. Times of up to 255 seconds may be used. + +The default value is 10 s and minimum 1 s. + +## 5.8 Start-up and close-down of multiplexer + +### 5.8.1 Start-up procedure + +Multiplexer operation is started by the use of the +CMUX command (see 3GPP TS 27.007 [4]). This command instructs the multiplexer to start up the multiplexer control channel (see clause 5.8.1) using either error recovery mode or non-error recovery mode. The TE multiplexer initiates the establishment of the multiplexer control channel by sending a SABM frame on DLCI 0 using the procedures of clause 5.4.1. + +Once the multiplexer channel is established other DLCs may be established using the procedures of clause 5.4.1. The multiplexers may negotiate the parameters associated with each DLC prior to establishment of a DLC or may use the defaults. + +### 5.8.2 Close-down procedure + +Initiation of the close-down will come from higher layers in either the TE or UE and is outside the scope of the present document. Once the command to close down is received the multiplexer will close down each DLC in turn using the procedures of clause 5.4.2. When all DLCs (except the multiplexer control channel - DLCI 0) are closed down (disconnected mode) the multiplexer that initiated close-down procedure will send a close-down message on the multiplexer control channel. When this message is acknowledged both stations will revert to the non-multiplexed mode. If no response is received to the close-down command within time T2, the initiating station may retransmit it but must close down if no response message is received in time T3. + +After closing of the multiplexer protocol, the UE and TE should revert to normal AT mode. + +# --- 6 Error Recovery Mode Option + +When the Advanced option is selected an error recovery mechanism may be used for better security. The error-recovery mode is optional and is intended for those cases where the quality of the TE-UE link can not be guaranteed and/or when the integrity of the data to be transmitted is critical. Some DLCs may use error recovery mode and some use non-error recovery mode on the same link. + +error recovery mode uses I frames to carry the data; the procedures used are defined below. + +New frames types and procedures are added. + +## 6.1 Frame Types + +**Table 28: Coding of Control Field** + +| Frame Type | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-------------------------|---|------|---|---|-----|-----|------|---| +| I (Information) | 0 | N(S) | | | | P/F | N(R) | | +| RR (Receive Ready) | 1 | 0 | 0 | 0 | P/F | | N(R) | | +| RNR (Receive Not Ready) | 1 | 0 | 1 | 0 | P/F | | N(R) | | +| REJ (Reject) | 1 | 0 | 0 | 1 | P/F | | N(R) | | + +N(R) and N(S) are receive and send sequence numbers, respectively. They are described later in the present document. + +### 6.1.1 Information transfer, I, command and response + +The function of the information, I, command and response shall be to transfer sequentially numbered frames, each containing an information field, across a data link. + +The encoding of the I command/response control field shall be as shown in table 28. + +The I frame control field shall contain two sequence numbers: + +- N(S), send sequence number, which shall indicate the sequence number associated with the I frame; and +- N(R), receive sequence number, which shall indicate the sequence number (as of the time of transmission) of the next expected I frame to be received, and consequently shall indicate that the I frames numbered up to N(R) - 1 inclusive have been received correctly. + +### 6.1.2 Receive ready, RR, command and response + +The receive ready, RR, frame shall be used by a station to: + +- a) indicate that it is ready to receive an I frame; and +- b) acknowledge previously received I frames numbered up to N(R) - 1 inclusive. + +When transmitted, the RR frame shall indicate the clearance of any busy condition that was initiated by the earlier transmission of an RNR frame by the same data station. See clause 6.2.2.5.1. + +### 6.1.3 Receive not ready, RNR, command and response + +The receive not ready, RNR, frame shall be used by a station to indicate a busy condition; i.e., temporary inability to accept subsequent I frames. I frames numbered up to N(R) - 1 inclusive shall be considered as acknowledged. The I frame numbered N(R) and any subsequent I frames received, if any, shall not be considered as acknowledged; the acceptance status of these frames shall be indicated in subsequent exchanges. + +### 6.1.4 Reject, REJ, command and response + +The reject, REJ, frame shall be used by a station to request retransmission of I frames starting with the frame numbered N(R). I frames numbered N(R) - 1 and below shall be considered as acknowledged. Additional I frames awaiting initial transmission may be transmitted following the retransmitted I frame(s). + +With respect to each direction of transmission on the data link, only one REJ exception condition from a given station to another station shall be established at any given time. A REJ frame shall not be transmitted until an earlier REJ exception condition has been cleared as indicated in clause 6.3.3.5.2.2. + +The REJ exception condition shall be cleared (reset) upon the receipt of an I frame with an N(S) equal to the N(R) of the REJ frame. + +## 6.2 Procedure and State + +### 6.2.1 Frame state variables and sequence numbers + +#### 6.2.1.1 General + +Each station shall maintain an independent send state variable V(S) for the frames it transmits and an independent receive state variable V(R) for the I frames it sends to and receives from another station. + +#### 6.2.1.2 Send state variable V(S) + +The send state variable denotes the sequence number of the next in-sequence I frame to be transmitted. The send state variable can take the value 0 to 7 inclusive. The value of the send state variable shall be incremented by one with each successive I frame transmission, but shall not exceed N(R) of the last received frame by more than 7. + +#### 6.2.1.3 Send sequence number N(S) + +Only I frames shall contain N(S), the send sequence number of transmitted frames. Prior to transmission of an I frame, N(S) shall be set equal to the value of the send state variable. + +#### 6.2.1.4 Receive state variable V(R) + +The receive state variable denotes the sequence number of the next I frame expected to be received. The receive state variable can take the value 0 to 7 inclusive. The value of the receive state variable shall be incremented by one on receipt of an error-free I frame whose send sequence number N(S) equals the receive state variable. + +#### 6.2.1.5 Receive sequence number N(R) + +All frames which contain N(R) (see table 28) shall indicate the N(R) sequence number of the next expected I frame. Prior to transmission of a frame containing N(R), the N(R) shall be set equal to the current value of the receive state variable. The N(R) indicates that the station transmitting the N(R) has correctly received all I frames numbered up to N(R) - 1 inclusive. + +#### 6.2.1.6 Use of the P/F bit to assist in error recovery + +As the P and F bits set to 1 are always exchanged as a pair (for every P bit there shall be one F bit, and another P bit shall not be issued until the previous P bit has been matched with an F bit, and, similarly, another F bit shall not be issued until another P bit is received), the N(R) contained in a received frame with a P bit or F bit set to 1 can be used to detect that I frame retransmission is required. This capability provides early detection of I frames not received by the remote data station and indicates the frame sequence number where retransmission shall begin. This capability is referred to as checkpointing. The N(R) of a correctly received frame shall acknowledge previously transmitted I frames to N(R) - 1 inclusive. + +The N(R) of a received I, RR or RNR response frame which has the F bit set to 1 shall cause the receiving station to initiate appropriate error recovery if the N(R) does not acknowledge at least all I frames transmitted by the receiving station previous to, and concurrent with, the last frame which was transmitted by the receiving station with the P bit set to 1. + +### 6.2.2 Exchange of information (I) frames + +#### 6.2.2.1 Sending I frames + +The control field format shall be as defined in clause 6.1 for an I frame, with N(S) set to the value of the send state variable V(S) and with N(R) set to the value of the receive state variable V(R). Following data link set-up, both V(S) and V(R) shall be set to zero. The maximum length of the information field in I frames shall be parameter N1 (see clause 5.7.2). The default value of N1 is 256 octets; other values may be negotiated by use of the multiplexer control channel. + +If a station is ready to send an I frame numbered N(S), where N(S) is equal to the last received acknowledgement plus 7, the station shall not send the I frame but shall follow the procedures described in clause 5.4.5. + +The decision whether to send an I frame as a command or as a response, i.e., to use the C/R bit to indicate a P or an F bit, respectively, shall depend on the need to acknowledge a received P bit set to 1 by transmitting a response with the F bit set to 1. + +#### 6.2.2.2 Receiving I frames + +After a station receives correctly an I frame [i.e., N(S) equals the value of the receive state variable V(R)] that it can accept, the station shall increment its receive state variable V(R), and, at its next opportunity to send, take one of the following actions: + +- if information is available for transmission and the other station is ready to receive, it shall act as described in clause 6.2.2.1 and acknowledge the received I frame(s) by setting $N(R)$ in the control field of the next transmitted I frame to the value of $V(R)$ ; or +- if information is not available for transmission, but the station is ready to receive I frames, the station shall send an RR frame and acknowledge the received I frame(s) by setting $N(R)$ to the value of $V(R)$ ; or +- if the station is not ready to receive further I frames, the station may send an RNR frame and acknowledge the received I frame(s) by setting the $N(R)$ to the value of $V(R)$ . + +If the station is unable to accept the correctly received I frame(s), $V(R)$ shall not be incremented. The station may send an RNR frame with the $N(R)$ set to the value of $V(R)$ . + +The I or supervisory frame transmitted will be either a command or a response depending on whether a P bit set to 1 or an F bit set to 1 transmission, respectively, is required. If the transmission of a P bit or F bit set to 1 is not required, the acknowledgement frames may be either commands or responses. + +#### 6.2.2.3 Reception of incorrect frames + +If a frame is received with an incorrect FCS, it shall be discarded. + +If an I frame is received with a correct FCS but with an incorrect $N(S)$ , the receiving station shall ignore the $N(S)$ field and discard the information field in that frame. This shall continue until the expected I frame is received correctly. The receiving station shall, however, use the $P/F$ and $N(R)$ indications in the discarded I frames. The station shall then acknowledge the expected I frame, when received correctly, as described in clause 5.4.4.2. + +The $P/F$ recovery (checkpointing) shall cause the retransmission of the I frames received incorrectly, as described in clause 6.2.1.6. + +#### 6.2.2.4 Station receiving acknowledgements + +A station receiving an I, RR, or RNR frame with a valid $N(R) = x$ shall treat as acknowledged all previously transmitted I frames up to and including the I frame transmitted with $N(S)$ equal to $x - 1$ . + +#### 6.2.2.5 Exception conditions and recovery + +The following procedures are available to effect recovery following the detection/occurrence of an exception condition at the data link layer. The exception conditions described are those situations which may occur as the result of transmission errors, data station malfunction or operational situations. + +##### 6.2.2.5.1 Busy + +The busy condition shall result when a station is temporarily unable to receive, or unable to continue to receive, I frames due to internal constraints; for example, receive buffering limitations. In this case, an RNR frame shall be transmitted with the $N(R)$ number of the next I frame that is expected. Traffic awaiting transmission may be transmitted from the busy data station prior to, or following, the RNR frame. The continued existence of a busy condition shall be reported by retransmission of an RNR frame at each $P/F$ frame exchange. + +A data station receiving an RNR frame, when in the process of transmitting, shall stop transmitting I frames at the earliest possible time. The station shall wait for a duration of T2 before resuming transmission. + +Indication that a busy condition has cleared and that I frames will now be acceptable shall be reported by the transmission of an RR, REJ, SABM, or UA frame with or without the $P/F$ bit set to 1. Clearance of a busy condition at a station shall also be indicated by the transmission of an I frame with the F bit set to 1. + +##### 6.2.2.5.2 N(S) sequence error + +An $N(S)$ sequence error exception condition shall occur in the receiver when an I frame that is received error free (no FCS error) contains an $N(S)$ that is not equal to the receive state variable at the receiver. The receiver shall not acknowledge (i.e., not increment its receive state variable) the frame causing the sequence error or any I frames which may follow until an I frame with the correct $N(S)$ is received. + +A station which receives one or more I frames having sequence errors, but which are otherwise error free, shall accept the control information contained in the $N(R)$ field and the $P/F$ bit to perform data link control functions; for example, to receive acknowledgement of previously transmitted I frames, or to cause a station to respond (P bit set to 1). + +Therefore, the retransmitted I frame may contain an N(R) field and/or P/F bit information that are updated and different from those contained in the originally transmitted I frame. + +Following the occurrence of a sequence error, the following means are available for initiating the retransmission of lost I frames or those with errors. + +##### 6.2.2.5.3 Poll/final (P/F) bit (checkpoint) recovery + +When a data station receives a frame with the P/F bit set to 1, it shall initiate retransmission of unacknowledged I frames previously transmitted with sequence numbers that are less than the V(S), send state variable, value that was current at the time of transmission of the last frame with the P/F bit, respectively, set to 1. Retransmission shall start with the oldest numbered unacknowledged I frame. I frames shall be retransmitted sequentially. New I frames may be transmitted if they become available. Such retransmission of I frames as a result of an exchange of P/F bits set to 1 is known as checkpoint retransmission. + +Checkpoint retransmission shall not be initiated under the following conditions: + +If a REJ command with the P bit set to 0 or 1, or a REJ response with the F bit set to 0, has been received and actioned while a P bit set to 1 was unanswered, checkpoint retransmission shall be inhibited on the next frame received with the F bit set to 1, if it would cause retransmission of the same particular I frame; i.e., same N(R) in same numbering cycle. + +If a P/F bit set to 1 is received in an unnumbered format frame (SABM, UA, DISC, DM, UI or UIH), checkpoint retransmission shall be inhibited. + +If, after sending a frame with the P/F bit set to 1, a data station receives an acknowledgement to that frame before receiving the corresponding frame with the P/F bit set to 1, checkpoint retransmission on the frame with the P/F bit set to 1 shall be inhibited. + +If any frame with the P bit set to 1 is received, checkpoint retransmission shall be inhibited. + +##### 6.2.2.5.4 REJ recovery + +The REJ command/response shall be used primarily to initiate an exception recovery (retransmission), following the detection of a sequence error, earlier than is possible by checkpoint (P/F bit) recovery; for example, if a REJ frame is immediately transmitted upon detection of a sequence error, then there is no requirement to wait for a frame with the P/F bit set to 1 in order to update V(R). + +With respect to each direction of transmission on the data link, only one "sent REJ" exception condition from one station to another data station shall be established at a time. A "sent REJ" exception condition shall be cleared when the requested I frame is received or when the response/command time-out function runs out. When the data station perceives by time-out that the requested I frame has not been received, because either the requested I frame or the REJ frame was in error or lost, the REJ frame may be repeated. + +A station receiving a REJ frame shall initiate sequential transmission (or retransmission) of I frames starting with the I frame indicated by the N(R) contained in the REJ frame. New I frames may be transmitted subsequently if they become available. + +If retransmission beginning with a particular frame occurs due to checkpointing (see clause 6.2.2.5.3), and a REJ frame is received which would also start retransmission with the same particular I frame [as identified by the N(R) in the REJ frame], the retransmission resulting from the REJ frame shall be inhibited. + +##### 6.2.2.5.5 SABM Command + +When this command is actioned, the responsibility for all unacknowledged I frames assigned to data link control reverts to a higher layer. Whether the content of the information field of such unacknowledged I frames is reassigned to data link control for transmission or not is decided at a higher layer. + +##### 6.2.2.5.6 DISC Command + +When this command is actioned, the responsibility for all unacknowledged I frames assigned to data link control reverts to a higher layer. Whether the content of the information field of such unacknowledged I frames is reassigned to data link control for transmission or not is decided at a higher layer. + +# --- Annex A (informative): Advice to TE software implementers + +The multiplexing protocol allows a number of virtual channels to be established between a TE and an MT. The TE is normally responsible for establishing and clearing down each virtual channel, although the MT may autonomously clear the entire multiplexing session. + +Each channel will start life as an instance of 3GPP TS 27.007 [4], and will allow the normal AT command procedures for both 3GPP TS 27.007 [4] and 3GPP TS 27.005 [3]. Any changes made to the AT register settings will be valid within the virtual channel only. If registers are saved to non-volatile memory then the changes will apply to the defaults for the AT registers and will affect new channels from that point on. Such changes will only affect other active channels if they are reset with ATZ. Changes to the phonebook or to SMS messages will, of course, be on a global basis. + +The software in the TE sitting above the multiplexing protocol is recommended to establish a virtual channel and leave it “idle” for the reception of incoming calls according to responses as defined in 3GPP TS 27.007 [4]. When an incoming call arrives the software may then cause an appropriate application to become active in order to receive the incoming call. The previously “idle” channel will then be occupied with this call and so the TE software is recommended to establish an additional channel to take over from the previously-idle channel in preparation for other incoming calls or indications. + +Because the ISO HDLC transparency mechanism must be used if it is supported by the UE, the TE shall always try to configure the multiplexer with this transparency mechanism. If it is not supported by the UE, the TE shall configure the multiplexer in the basic option. + +# Annex B (informative): Explanatory notes on the CRC Calculation + +R(p)= remainder of p. + +Message is k bits long. + +$$\text{FCS} = \text{OnesComplement} \left( R \left( \frac{(x^7 + x^6 + x^5 + x^4 + x^3 + x^2 + x^1 + 1)x^k}{x^8 + x^2 + x^1 + 1} \right) \oplus R \left( \frac{(\text{message})x^8}{x^8 + x^2 + x^1 + 1} \right) \right)$$ + +## B.1 Example + +A SABM frame on DLCI 1. Note that bits are written as they are sent on the serial port, LSB bit first and MSB bit last. No start stop bits, transparency bytes, BOFC or EOFC are included in the message. (The length octet is only included in the FCS for UI frames). + +| BOFC | DLC | Ctrl | FCS | EOFC | +|----------|----------|----------|------------------|----------| +| 10011111 | 11100000 | 11111100 | To be calculated | 10011111 | + +k=8\*2=16 + +message=11100000 11111100 + +$$\begin{aligned} \text{FCS} &= \text{OnesComplement} \left( R \left( \frac{11111111/00000000/00000000}{100000111} \right) \right. \\ &\quad \left. \oplus R \left( \frac{11100000/11111100/00000000}{100000111} \right) \right) = \\ &\text{OnesComplement}(11010111 \oplus 10111001) = \text{OnesComplement}(01101110) = 10010001 \end{aligned}$$ + +## B.2 Reflected bits + +In the example the bits where shown as they was sent on the serial line, this is however not they way the application sees the octets, it will see MSB first and LSB last, so before calculating the FCS the octets bit order must be reversed. + +| BOFC | DLC | Ctrl | FCS | EOFC | +|----------|----------|----------|------------------|----------| +| 0xF9 | 0x07 | 0x3F | | 0xF9 | +| 11111001 | 00000111 | 00111111 | To be calculated | 11111001 | + +- 1 Reverse all bit in octets. +- 2 Calculate FCS. +- 3 Reverse all bits in FCS. +- 4 Send the reversed FCS. + +Fortunately there is an easier way of doing the reversing of the bits, when implementing the CRC calculation using table lookup the table can be reversed. + +## B.3 Implementation + +Implementation is very simple because the FCS will be as wide as the lookup table (8 bits). To avoid having to reverse all bits in the octets all the octets in the crc table is reversed instead. + +The term $R \left( \frac{(x^7 + x^6 + x^5 + x^4 + x^3 + x^2 + x^1 + 1)x^k}{x^8 + x^2 + x^1 + 1} \right)$ corresponds to initialising the FCS with 0xFF. + +### B.3.1 Calculate FCS for the example given earlier + +First initialize the crc: FCS=0xFF + Add first byte: FCS=table[0xFF^0x07]=table[0xF8]=0xBA + Add second byte: FCS=table[0xBA^0x3F]=table[0x85]=0x76 + Ones complement the FCS: FCS=0xFF-FCS=0xFF-0x76=0x89 (10001001) + Transmit this FCS, this will be the same as the one calculated previous after the uart has reversed the bits. + +### B.3.2 Check FCS for the example given earlier + +First initialize the crc: FCS=0xFF + Add first byte: FCS=table[0xFF^0x07]=table[0xF8]=0xBA + Add second byte: FCS=table[0xBA^0x3F]=table[0x85]=0x76 + Add FCS: FCS=table[0x76^0x89]=table[0xFF]=0xCF + 0xCF is the reversed order of 11110011, the checksum is valid + +### B.3.3 The transmitter code + +``` +/*Init*/ +unsigned char FCS=0xFF; +unsigned char len; +unsigned char p; +/*len is the number of bytes in the message, p points to message*/ +while (len--) { +FCS=crc_table[FCS^*p++]; +} +/*Ones complement*/ +FCS=0xFF-FCS; +``` + +### B.3.4 The receiver code + +``` +/*Init*/ +unsigned char FCS=0xFF; +unsigned char len; +unsigned char p; +/*len is the number of bytes in the message, p points to message*/ +while (len--) { +FCS=crc_table[FCS^*p++]; +} +/*Ones complement*/ +FCS=crc_table[FCS^"received FCS"]; +/*0xCF is the reversed order of 11110011.*/ +if (FCS==0xCF) { +/*FCS is OK*/ +} +else { +/*FCS is not OK*/ +} +``` + +### B.3.5 Reversed CRC table + +``` +const unsigned char crctable[256] = { //reversed, 8-bit, poly=0x07 + 0x00, 0x91, 0xE3, 0x72, 0x07, 0x96, 0xE4, 0x75, 0x0E, 0x9F, 0xED, 0x7C, 0x09, 0x98, 0xEA, 0x7B, + 0x1C, 0x8D, 0xFF, 0x6E, 0x1B, 0x8A, 0xF8, 0x69, 0x12, 0x83, 0xF1, 0x60, 0x15, 0x84, 0xF6, 0x67, + 0x38, 0xA9, 0xDB, 0x4A, 0x3F, 0xAE, 0xDC, 0x4D, 0x36, 0xA7, 0xD5, 0x44, 0x31, 0xA0, 0xD2, 0x43, + 0x24, 0xB5, 0xC7, 0x56, 0x23, 0xB2, 0xC0, 0x51, 0x2A, 0xBB, 0xC9, 0x58, 0x2D, 0xBC, 0xCE, 0x5F, + + 0x70, 0xE1, 0x93, 0x02, 0x77, 0xE6, 0x94, 0x05, 0x7E, 0xEF, 0x9D, 0x0C, 0x79, 0xE8, 0x9A, 0x0B, + 0x6C, 0xFD, 0x8F, 0x1E, 0x6B, 0xFA, 0x88, 0x19, 0x62, 0xF3, 0x81, 0x10, 0x65, 0xF4, 0x86, 0x17, + 0x48, 0xD9, 0xAB, 0x3A, 0x4F, 0xDE, 0xAC, 0x3D, 0x46, 0xD7, 0xA5, 0x34, 0x41, 0xD0, 0xA2, 0x33, + 0x54, 0xC5, 0xB7, 0x26, 0x53, 0xC2, 0xB0, 0x21, 0x5A, 0xCB, 0xB9, 0x28, 0x5D, 0xCC, 0xBE, 0x2F, + + 0xE0, 0x71, 0x03, 0x92, 0xE7, 0x76, 0x04, 0x95, 0xEE, 0x7F, 0x0D, 0x9C, 0xE9, 0x78, 0x0A, 0x9B, + 0xFC, 0x6D, 0x1F, 0x8E, 0xFB, 0x6A, 0x18, 0x89, 0xF2, 0x63, 0x11, 0x80, 0xF5, 0x64, 0x16, 0x87, + 0xD8, 0x49, 0x3B, 0xAA, 0xDF, 0x4E, 0x3C, 0xAD, 0xD6, 0x47, 0x35, 0xA4, 0xD1, 0x40, 0x32, 0xA3, + 0xC4, 0x55, 0x27, 0xB6, 0xC3, 0x52, 0x20, 0xB1, 0xCA, 0x5B, 0x29, 0xB8, 0xCD, 0x5C, 0x2E, 0xBF, + + 0x90, 0x01, 0x73, 0xE2, 0x97, 0x06, 0x74, 0xE5, 0x9E, 0x0F, 0x7D, 0xEC, 0x99, 0x08, 0x7A, 0xEB, + 0x8C, 0x1D, 0x6F, 0xFE, 0x8B, 0x1A, 0x68, 0xF9, 0x82, 0x13, 0x61, 0xF0, 0x85, 0x14, 0x66, 0xF7, + 0xA8, 0x39, 0x4B, 0xDA, 0xAF, 0x3E, 0x4C, 0xDD, 0xA6, 0x37, 0x45, 0xD4, 0xA1, 0x30, 0x42, 0xD3, + 0xB4, 0x25, 0x57, 0xC6, 0xB3, 0x22, 0x50, 0xC1, 0xBA, 0x2B, 0x59, 0xC8, 0xBD, 0x2C, 0x5E, 0xCF +}; +``` + +# Annex C (informative): Change History + +| TSG | TDoc | VERS | NEW_VERS | CR | REV | REL | CAT | WORKITEM | SUBJECT | +|----------------|-----------|----------|----------|-----|-----|-----------------------------------------|-----|-----------|--------------------------------------------------------------------------------------------| +| T#4 | TP-99119 | 2.0.0 | 3.0.0 | New | | R99 | | | Creation of 3GPP 27.010 v3.0.0 out of GSM 07.10 v6.3.0 | +| T#4 | TP-99124 | 3.0.0 | 3.1.0 | 001 | | R99 | A | MUX MS-TE | Clarification of how to handle the length field in basic mode | +| T#4 | TP-99146 | 3.0.0 | 3.1.0 | 002 | | R99 | A | MUX MS-TE | Editorial corrections | +| T#5 | TP-99177 | 3.1.0 | 3.2.0 | 003 | | R99 | A | TEI | Clarification of CR bit | +| T#5 | TP-99177 | 3.1.0 | 3.2.0 | 004 | | R99 | A | TEI | Correction of the bits in the start and close flags of the frame in the example on Annex B | +| T#7 | TP-000024 | 3.2.0 | 3.3.0 | 005 | | R99 | F | TEI | Adaptations for UMTS | +| T#11 | - | 3.3.0 | 4.0.0 | | | Rel4 | | | Upgrade to Rel-4 | +| T#13 | TP-010212 | 4.0.0 | 4.1.0 | 006 | | Rel4 | F | TEI4 | Conversion of GSM to 3GPP references | +| T#15 | TP-020014 | 4.1.0 | 4.2.0 | 008 | | Rel4 | A | TEI | Incorrect explanation of length indicator bit | +| T#16 | - | 4.2.0 | 5.0.0 | - | | Rel5 | | | Upgrade to Rel-5 | +| T#26 | - | 5.0.0 | 6.0.0 | - | | Rel6 | | | Upgrade to Rel-6 | +| CT#36 | - | 6.0.0 | 7.0.0 | - | | Rel7 | | | Upgrade to Rel-7 | +| CT#42 | | 7.0.0 | 8.0.0 | | | Rel8 | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | +| CT#46 | | 8.0.0 | 9.0.0 | | | Rel9 | | | Automatic upgrade from previous Release | +| CT#50 | CP-100779 | 9.0.0 | 9.1.0 | 010 | | Rel9 | A | TEI8 | Correcting non-specific external references | +| CT#51 | | 9.1.0 | 10.0.0 | | | | | | Automatic upgrade from previous Release version 9.1.0 | +| CT#57 | | 10.0.0 | 11.0.0 | | | | | | Automatic upgrade from previous Release version 10.0.0 | +| | | 11.0.0 | 12.0.0 | | | | | | Automatic upgrade from previous Release | +| | | 12.0.0 | 13.0.0 | | | | | | Automatic upgrade from previous Release | +| Change history | | | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | | | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | | | 14.0.0 | +| 2018-06 | CT#80 | | | | | Automatic upgrade from previous Release | | | 15.0.0 | +| 2020-06 | CT#88e | - | - | - | | Update to Rel-16 version (MCC) | | | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/27_series/27060/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/27_series/27060/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5179e06dfd36d23a2c52a3884db91f0e2ae0e44a --- /dev/null +++ b/marked/Rel-16/27_series/27060/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47d4c8f0e372a618fa8779a64d9d44789e30d870e2bb7753d0092b6e70fe25f4 +size 34107 diff --git a/marked/Rel-16/27_series/27060/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/27_series/27060/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42cd47fba55a891cf987eb0762304aeeea75a111 --- /dev/null +++ b/marked/Rel-16/27_series/27060/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28d8ebf5696c362f0e2cf80eb7bef6ae118c1bca86cd07b8051d801b9db62e3c +size 60188 diff --git a/marked/Rel-16/27_series/27060/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-16/27_series/27060/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7be04c9b6e591f31b8768914535e9f0b3a56689 --- /dev/null +++ b/marked/Rel-16/27_series/27060/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc308484215b175c215c010b6f63722e723cd6feb78f3f8f43bf21417e514d27 +size 24930 diff --git a/marked/Rel-16/27_series/27060/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/27_series/27060/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc371a4623e50a8b9439454ee8e6943f9ad17c08 --- /dev/null +++ b/marked/Rel-16/27_series/27060/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f130d301e51280541bab58526478f47d3a191edecc28f37be811f6e510beb36 +size 63047 diff --git a/marked/Rel-16/27_series/27060/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/27_series/27060/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fa2950098d1179ee04ffb0cb9506ecbecf74411 --- /dev/null +++ b/marked/Rel-16/27_series/27060/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2a5562d26372bf1d1b88b78b546fc8fa4c01744a0502dcbf597536e81c2a74a +size 58756 diff --git a/marked/Rel-16/27_series/27060/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/27_series/27060/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1cb80cf321a3ee2fc2d623dc05d64e9066fd546 --- /dev/null +++ b/marked/Rel-16/27_series/27060/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d822d507f76f3501644939c01acf9120e907a5ea169f1111ebdadc0a0356c993 +size 54174 diff --git a/marked/Rel-16/27_series/27060/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-16/27_series/27060/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e8b7756b19aeb484cfa3430df93bd7f84262343 --- /dev/null +++ b/marked/Rel-16/27_series/27060/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2240b63fcb1dea7b0eebacacef46f69031ca3b538e9f43fdc651a517a6b1816 +size 34482 diff --git a/marked/Rel-16/27_series/27060/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-16/27_series/27060/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..661770290461a163f108d33a5cca0e2e93be0aca --- /dev/null +++ b/marked/Rel-16/27_series/27060/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac08db5dbac0e79d424d558fedfeb4a23bc1e044ec1b514f67411b3a69d45343 +size 91364 diff --git a/marked/Rel-16/27_series/27060/b10763be31553f31cbb795653b731a43_img.jpg b/marked/Rel-16/27_series/27060/b10763be31553f31cbb795653b731a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92d0d20963de99fdf24b72d500942fce6cab9d27 --- /dev/null +++ b/marked/Rel-16/27_series/27060/b10763be31553f31cbb795653b731a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4474057c9ae77031303cbec21505b2095674ff114181aae405b6b3f840a8e56 +size 51238 diff --git a/marked/Rel-16/27_series/27060/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/27_series/27060/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05b03455bebec5130efe5c20dbdc9376916c71ba --- /dev/null +++ b/marked/Rel-16/27_series/27060/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5795e051df8dde4edf52c27c4488e13c78f166d406c70cb108f77ffcc033ef42 +size 37207 diff --git a/marked/Rel-16/27_series/27060/raw.md b/marked/Rel-16/27_series/27060/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f812d582dc3a7bb2dc9ae4319f44a87e5d809d08 --- /dev/null +++ b/marked/Rel-16/27_series/27060/raw.md @@ -0,0 +1,1010 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions abbreviations and symbols ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 3.3 Symbols..... | 9 | +| 4 Access reference configuration..... | 9 | +| 5 Functions to support data services ..... | 10 | +| 6 Interface to Packet Domain Bearer Services..... | 10 | +| 6.1 A/Gb mode ..... | 10 | +| 6.2 Iu mode..... | 11 | +| 7 Functions common to all configurations of a MS supporting Packet Switched Services..... | 11 | +| 7.1 Mobile Station Modes of Operation..... | 11 | +| 7.2 Physical Interface ..... | 11 | +| 7.3 Terminal context procedures..... | 11 | +| 7.3.1 PS Attach ..... | 11 | +| 7.3.2 PS Detach ..... | 12 | +| 7.3.3 MS Originated PDP Context Activation ..... | 12 | +| 7.3.4 MS Originated Secondary PDP Context Activation ..... | 12 | +| 7.3.5 Network Requested PDP Context Activation..... | 12 | +| 7.3.6 MS-Initiated PDP Context Modification..... | 12 | +| 7.3.7 PDP Context Deactivation..... | 12 | +| 7.3.8 PDP context related parameters..... | 12 | +| 7.3.8.1 MS in A/Gb mode..... | 12 | +| 7.3.8.2 MS in Iu mode ..... | 13 | +| 8 ..... | 13 | +| 9 IP Based Services..... | 13 | +| 9.1 Example mapping of functions between the R reference point and the Packet Domain bearer for IP over PPP ..... | 14 | +| 9.1.1 IPv4 over PPP ..... | 15 | +| 9.1.2 IPv6 over PPP ..... | 17 | +| 9.2 Example mapping of functions between the R reference point and the Packet Domain bearer for IP over MCML PPP ..... | 19 | +| 10 PPP Based Services..... | 20 | +| 10.1 Example mapping of functions between the R reference point and the Packet Domain bearer (transparent PPP negotiation)..... | 21 | +| 10.2 Example mapping of functions between the R reference point and the Packet Domain bearer (relayed PPP negotiation)..... | 22 | +| 11 Internet Hosted Octet Stream Service (IHOSS)..... | 23 | +| 12 AT commands..... | 23 | +| 12.1 General on AT commands..... | 24 | +| 12.1.1 Interaction of AT commands, Packet Domain management and PDPs ..... | 24 | +| 12.1.1.1 AT commands and responses ..... | 24 | +| 12.1.1.2 PDP and layer 2 protocol operation..... | 24 | +| 12.1.1.3 Management of Packet Switched services..... | 24 | +| 12.1.1.3.1 PS attachment..... | 24 | +| 12.1.1.3.2 PDP context activation..... | 25 | +| 12.1.2 Use of default context parameter values..... | 25 | +| 12.1.2.1 PDP type ..... | 25 | + +| | | | +|-------------------------------|-------------------------------------------------------------|-----------| +| 12.1.2.2 | PDP address (of the MS) ..... | 25 | +| 12.1.2.3 | Access Point Name ..... | 25 | +| 12.1.2.4 | QoS Requested..... | 25 | +| 12.1.2.5 | PDP Configuration Options ..... | 26 | +| 12.2 | Example command sequences for dial-compatibility mode ..... | 26 | +| 12.2.1 | PPP in dial compatibility mode ..... | 26 | +| 12.2.1.1 | Mobile initiated IP context activation..... | 26 | +| 12.2.1.2 | Network requested IP context activation ..... | 27 | +| 13 | IMS related functions..... | 29 | +| 13.1 | General ..... | 29 | +| 13.2 | DNS Server Discovery ..... | 29 | +| 13.3 | P-CSCF Server Discovery..... | 29 | +| 13.4 | PDP Context used for IMS Signalling ..... | 29 | +| 13.5 | Binding Information..... | 29 | +| 13.6 | Mapping of SDP to QoS Attributes..... | 30 | +| 13.7 | Authorization of QoS Attributes ..... | 30 | +| 13.8 | Support for forking..... | 30 | +| 13.9 | Multiplexing of IMS media components to PDP contexts..... | 30 | +| 13.10 | Policy control rejection of PDP context..... | 30 | +| Annex A (informative): | Summary of AT commands for the Packet Domain ..... | 31 | +| Annex B (informative): | Octet Stream Protocol (OSP) PDP type ..... | 32 | +| Annex C (informative): | Change history..... | 33 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines the requirements for TE-MT interworking over the R-reference point for the Packet Domain, within the 3GPP systems. + +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 + +The present document defines the requirements for TE-MT interworking over the R-reference point for the Packet Domain, within the 3GPP systems. It is up to the manufacturer how to implement the various functions but the present document and existing 3GPP TS 27.001, 27.002, and 27.003 shall be followed where applicable. + +It is the intention that the present document shall remain as the specification to develop a MS for support of Packet Switched services and its text includes references to 3GPP standards. + +# --- 1 Scope + +The (A/Gb and Iu mode) PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN there is a need to connect various kinds of terminal equipments to the Mobile Station (MS). The present document defines the requirements for TE-MT interworking over the R-reference point for the Packet Domain , including the protocols and signalling needed to support Packet Switched services, as defined in 3GPP TS 22.060 and 3GPP TS 23.060. + +The present document is valid for PLMN in A/Gb mode as well as for PLMN in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". Please note, that the A interface does not play any role in the scope of this document although the term "A/Gb mode" is 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. + +- [1] Void. +- [2] Void. +- [3] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service Description Stage 1". +- [4] Void. +- [5] Void. +- [6] Void. +- [7] Void. +- [8] Void. +- [9] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service Description Stage 2". +- [10] Void. +- [11] Void. +- [12] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network protocols; Stage 3". +- [13] Void. +- [14] Void. +- [15] Void. +- [16] 3GPP TS 27.007: "AT command set for 3GPP User Equipment (UE)". +- [17] 3GPP TS 29.061: "Packet Domain; Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN)". +- [18] ITU-T Recommendation E.164 (02/05): "Numbering plan for the ISDN era". +- [19] ITU-T Recommendation V.42 bis (01/90): "Data communication over the telephone network – Data compression procedures for data circuit-terminating equipment (DCE) using error correction procedures". + +- [20] Void. +- [21] Void. +- [22] Void. +- [23] Void. +- [24] Void. +- [25] Void. +- [26] IETF RFC 768 (1980): "User Datagram Protocol" (STD 6). +- [27] IETF RFC 791 (1981): "Internet Protocol" (STD 5). +- [28] IETF RFC 792 (1981): "Internet Control Message Protocol" (STD 5). +- [29] IETF RFC 793 (1981): "Transmission Control Protocol" (STD 7). +- [30] ITU-T Recommendation V.250 (ex V.25ter) (05/99): "Serial asynchronous automatic dialling and control". +- [31] ITU-T Recommendation V.24 (10/96): "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [32] ITU-T Recommendation V.28 (03/93): "Electrical Characteristics for unbalanced double-current interchange circuits". +- [33] ITU-T Recommendation V.80 (08/96): "In-band DCE control and synchronous data modes for asynchronous DTE". +- [34] IETF RFC 1661 (1994): "The Point-to-Point Protocol (PPP)" (STD 51). +- [35] IETF RFC 1662 (1994): "PPP in HDLC-like framing" (STD 51). +- [36] IETF RFC 1700 (1994): "Assigned Numbers" (STD 2). +- [37] IETF RFC 1570 (1994): "PPP LCP Extensions". +- [38] IETF RFC 1989 (1996): "PPP Link Quality Monitoring". +- [39] IETF RFC 1332 (1992): "The PPP Internet Protocol Control Protocol (IPCP)". +- [40] IETF RFC 1877 (1995): "PPP IPCP Extensions for Name Server Addresses ". +- [41] IETF RFC 2153 (1997): "PPP Vendor Extensions". +- [42] IETF RFC 1334 (1992): "PPP Authentication Protocols". +- [43] IETF RFC 1994 (1996): "PPP Challenge Handshake Authentication Protocol". +- [44] IETF RFC 2686 (1999): "The Multi-Class Extension to Multi-Link PPP". +- [45] IETF RFC 1990 (1996): "The PPP Multilink Protocol (MP)". +- [46] IETF RFC 2472 (1998): "IP Version 6 over PPP". +- [47] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [48] 3GPP TS 23.221: "Architectural requirements". +- [49] IETF RFC 2373 (1998): "IP version 6 Addressing Architecture". +- [50] 3GPP TS 24.228: "Signalling flows for the IP multimedia call control based on SIP and SDP; Stage 3" +- [51] 3GPP TS 24.229: " IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3". + +- [52] 3GPP TS 29.207: "Policy control over Go interface". +- [53] 3GPP TS 29.208: "End-to-end QoS signalling flows". +- [54] IETF RFC 3261 (March 2002): "SIP: Session Initiation Protocol". +- [55] IETF RFC 3315 (2003): "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)" R. Droms, J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney. +- [56] IETF RFC 1034 (1987): "Domain Names - Concepts and Facilities" (STD 13). +- [57] IETF RFC 1035 (1987): "Domain Names - Implementation and Specification" (STD 13). +- [58] IETF RFC 1886 (1995): "DNS Extensions to support IP version 6". + +# --- 3 Definitions abbreviations and symbols + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.060 and 3GPP TS 23.060 and the following apply: + +**2G- / 3G-:** prefixes 2G- and 3G- refers to functionality that supports only A/Gb mode or Iu mode, respectively, e.g., 2G-SGSN refers only to the A/Gb mode functionality of an SGSN. When the prefix is omitted, reference is made independently from the A/Gb mode or Iu mode functionality. + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|------------------------------------------| +| APN | Access Point Name | +| DHCPv6 | Dynamic Host Configuration Protocol Ipv6 | +| DNS | Domain Name System | +| GGSN | Gateway GPRS Support Node | +| GPRS | General Packet Radio Service | +| GSN | GPRS Support Node | +| GTP-U | GPRS Tunnelling Protocol for user plane | +| HDLC | High Level Data Link Control | +| ICMP | Internet Control Message Protocol | +| IETF | Internet Engineering Task Force | +| IMS | IP Multimedia Core Network Subsystem | +| IP | Internet Protocol | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| IPv6CP | IPv6 Control Protocol | +| LA | Location Area | +| LCP | Link Control Protocol | +| LLC | Logical Link Control | +| MAC | Medium Access Control | +| MCML | Multi-Class Multi-Link PPP | +| ME | Mobile Equipment | +| MP | Multilink PPP | +| MS | Mobile Station | +| MT | Mobile Termination | + +| | | +|--------|-------------------------------------------| +| NCP | Network Control Protocol | +| PCF | Policy Control Function | +| P-CSCF | Proxy Call Session Control Function | +| PDCP | Packet Data Convergence Protocol | +| PDN | Packet Data Network | +| PDP | Packet Data Protocol , e.g., IP or PPP | +| PDU | Protocol Data Unit | +| PPP | Point-to-Point Protocol | +| PS | Packet Switched | +| PTM | Point To Multipoint | +| PTP | Point To Point | +| PVC | Permanent Virtual Circuit | +| QoS | Quality of Service | +| RA | Routing Area | +| SDP | Session Description Protocol | +| SGSN | Serving GPRS Support Node | +| SIP | Session Initiation Protocol | +| SNDPCP | SubNetwork Dependent Convergence Protocol | +| TCP | Transmission Control Protocol | +| TE | Terminal Equipment | +| TFT | Traffic Flow Template | +| UDP | User Datagram Protocol | + +## 3.3 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Gb | Interface between a SGSN and a BSC. | +| Gi | Reference point between the Packet Domain and an external packet data network. | +| Gn | Interface between two GSNs within the same PLMN. | +| Gp | Interface between two GSNs in different PLMNs. The Gp interface allows support of Packet Domain network services across areas served by the co-operating PLMNs. | +| Gs | Interface between an SGSN and MSC. | +| Iu | Interface between the RNS and the core network. It is also considered as a reference point. | +| R | The reference point between a non-ISDN compatible TE and MT. Typically this reference point supports a standard serial interface. | +| Um | The interface between the MS and the fixed network part in A/Gb mode. The Um interface is the in A/Gb mode network interface for providing packet data services over the radio to the MS. The MT part of the MS is used to access the GSM services through this interface. | +| Uu | Interface between the mobile station (MS) and the fixed network part in Iu mode. The Uu interface is the Iu mode network interface for providing packet data services over the radio to the MS. The MT part of the MS is used to access the UMTS services through this interface. | + +# --- 4 Access reference configuration + +Figure 1 shows the relationship between the MS, its terminal equipment and the PLMN in the overall Packet Domain environment. + +![Figure 1: Packet Domain Access Interfaces and Reference Points. The diagram shows a Mobile Station (MS) consisting of Terminal Equipment (TE) and a Mobile Terminal (MT) connected at reference point R. The MT connects to Packet Domain network 1 via the Um or Uu interface. Packet Domain network 1 is connected to Packet Domain network 2 via the Gp interface. Packet Domain network 1 connects to a PDN or other network via the Gi reference point.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 1: Packet Domain Access Interfaces and Reference Points. The diagram shows a Mobile Station (MS) consisting of Terminal Equipment (TE) and a Mobile Terminal (MT) connected at reference point R. The MT connects to Packet Domain network 1 via the Um or Uu interface. Packet Domain network 1 is connected to Packet Domain network 2 via the Gp interface. Packet Domain network 1 connects to a PDN or other network via the Gi reference point. + +Figure 1: Packet Domain Access Interfaces and Reference Points + +# 5 Functions to support data services + +The main functions of the MT to support data services are: + +- physical connection at the reference point R; +- flow control between TE and MT; +- mapping of user signalling to/from the Packet Domain bearer; +- mapping of packets belonging to different flows to appropriate PDP contexts; +- support of data integrity between the terminal equipment and the Packet Domain bearer; +- functions to support packet based data. + +# 6 Interface to Packet Domain Bearer Services + +## 6.1 A/Gb mode + +The following figure 2 shows the relationship of the Packet Domain Bearer in A/Gb mode, terminating at the SNDPCP layer, to the rest of the Packet Domain environment in A/Gb mode. It is shown for reference purposes only and detailed information can be found in 3GPP TS 23.060. + +![Figure 2: User Plane for Packet Domain services in A/Gb mode. This diagram illustrates the protocol stack across five entities: MS, BSS, SGSN, GGSN, and an external Access point. The MS stack includes SNDPCP, LLC, RLC, MAC, and GSM RF. The BSS stack includes a Relay (RLC, BSSGP), MAC, Network Service, GSM RF, and L1bis. The SGSN stack includes a Relay (SNDPCP, GTP-U), LLC, UDP, BSSGP, IP, Network Service, L2, L1bis, and L1. The GGSN stack includes GTP-U, UDP, IP, L2, and L1. Interfaces are labeled: Um (MS-BSS), Gb (BSS-SGSN), Gn (SGSN-GGSN), and Gi (GGSN-External).](b10763be31553f31cbb795653b731a43_img.jpg) + +Figure 2: User Plane for Packet Domain services in A/Gb mode. This diagram illustrates the protocol stack across five entities: MS, BSS, SGSN, GGSN, and an external Access point. The MS stack includes SNDPCP, LLC, RLC, MAC, and GSM RF. The BSS stack includes a Relay (RLC, BSSGP), MAC, Network Service, GSM RF, and L1bis. The SGSN stack includes a Relay (SNDPCP, GTP-U), LLC, UDP, BSSGP, IP, Network Service, L2, L1bis, and L1. The GGSN stack includes GTP-U, UDP, IP, L2, and L1. Interfaces are labeled: Um (MS-BSS), Gb (BSS-SGSN), Gn (SGSN-GGSN), and Gi (GGSN-External). + +Figure 2: User Plane for Packet Domain services in A/Gb mode + +## 6.2 Iu mode + +The following figure 2a shows the relationship of the Packet Domain Bearer in Iu mode, terminating at the PDCP layer, to the rest of the Packet Domain environment in Iu mode. It is shown for reference purposes only and detailed information can be found in 3GPP TS 23.060. + +![Figure 2a: User Plane for Packet Domain services in Iu mode. The diagram shows the protocol stack for the user plane across four entities: MS (Mobile Station), RNS (Radio Network Subsystem), 3G SGSN, and GGSN. The MS contains PDCP, RLC, MAC, and L1 layers. The RNS contains two 'Relay' blocks; the first Relay block contains PDCP and GTP-U, and the second contains GTP-U, UDP/IP, AAL5, and ATM. The 3G SGSN contains GTP-U, UDP/IP, AAL5, and ATM layers. The GGSN contains GTP-U, UDP/IP, L2, and L1 layers. Interfaces are labeled: Uu between MS and RNS, Iu-PS between RNS and 3G SGSN, Gn between 3G SGSN and GGSN, and Gi at the GGSN. Access points are indicated at the top of the MS and GGSN.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Figure 2a: User Plane for Packet Domain services in Iu mode. The diagram shows the protocol stack for the user plane across four entities: MS (Mobile Station), RNS (Radio Network Subsystem), 3G SGSN, and GGSN. The MS contains PDCP, RLC, MAC, and L1 layers. The RNS contains two 'Relay' blocks; the first Relay block contains PDCP and GTP-U, and the second contains GTP-U, UDP/IP, AAL5, and ATM. The 3G SGSN contains GTP-U, UDP/IP, AAL5, and ATM layers. The GGSN contains GTP-U, UDP/IP, L2, and L1 layers. Interfaces are labeled: Uu between MS and RNS, Iu-PS between RNS and 3G SGSN, Gn between 3G SGSN and GGSN, and Gi at the GGSN. Access points are indicated at the top of the MS and GGSN. + +**Figure 2a: User Plane for Packet Domain services in Iu mode** + +# 7 Functions common to all configurations of a MS supporting Packet Switched Services + +## 7.1 Mobile Station Modes of Operation + +Three MS modes of operation are identified for A/Gb mode: Class A, B, and C. These modes of operation are described in 3GPP TS 23.060. + +Three MS modes of operation are supported for Iu mode: A PS/CS mode of operation corresponds to class-A mode of operation in A/Gb mode. A PS mode of operation corresponds to class-C mode of operation in A/Gb mode. A CS mode of operation is out of scope in the present document. + +## 7.2 Physical Interface + +The physical interface between the TE and the MT may conform to ITU-T V.24/V.28, or to IrDA IrPHY physical standard specification, or to PCMCIA PC-Card electrical specification. All signal levels and their operation shall be as specified in 3GPP TS 27.001, 27.002, and 27.003. + +## 7.3 Terminal context procedures + +This subclause describes the relationships for PS Attach and Detach, and PDP Context Activation, Modification and Deactivation. The procedures for these functions are described in 3GPP TS 23.060. + +### 7.3.1 PS Attach + +The PS Attach shall be performed prior to activating a PDP context. The PS Attach may be performed automatically or manually depending on the manufacturer's implementation and configuration. + +### 7.3.2 PS Detach + +The PS Detach may be performed automatically or manually depending on the manufacturer's implementation and configuration. The following cases are valid: + +- if the connection between the TE and MT is broken then the MT may perform the PS Detach procedure; +- if the network originates a PS Detach the MT may inform the TE; + +- if the radio connection is broken then the MT may inform the TE; +- if the TE deactivates the last PDP context then the MT may perform the PS Detach procedure. + +### 7.3.3 MS Originated PDP Context Activation + +The PDP Context Activation procedure may be performed automatically or manually depending on the manufacturer's implementation and configuration. Depending on the manufacturer's implementation and configuration, 0, 1, or more PDP contexts can be active simultaneously. + +### 7.3.4 MS Originated Secondary PDP Context Activation + +The Secondary PDP Context Activation procedure may be performed automatically or manually depending on the manufacturer's implementation and configuration. Depending on the manufacturer's implementation and configuration, 0, 1, or more PDP contexts can be active simultaneously for the same PDP address. + +### 7.3.5 Network Requested PDP Context Activation. + +The network can request a PS attached MS to activate a specific PDP context. + +### 7.3.6 MS-Initiated PDP Context Modification + +The MS-Initiated PDP Context Modification procedure may be performed automatically or manually depending on the manufacturer's implementation and configuration. + +### 7.3.7 PDP Context Deactivation + +The PDP Deactivation may be performed automatically or manually depending on the manufacturer's implementation and configuration. The following cases are valid: + +- if the connection between the MT and the TE is broken then the MT may perform the PDP Context Deactivation procedure; +- if the radio connection is broken then the MT may inform the TE; +- if the DHCP lease expires or the renewal is rejected by the DHCP server or the IP Address is changed during DHCP lease renewal, the TE may deactivate the PDP context. +- if the TE deactivates the last PDP context then the MT may perform the PS Detach procedure. + +### 7.3.8 PDP context related parameters + +#### 7.3.8.1 MS in A/Gb mode + +It shall be possible to enquire and/or set the following parameters: + +- requested quality of service; +- traffic flow template; +- compression on or off; +- TCP/IP header compression on or off; +- PDP address; +- PDP type; +- Access Point Name (APN); +- protocol configuration options (if required by the PDP type). + +#### 7.3.8.2 MS in Iu mode + +It shall be possible to enquire and/or set the following parameters: + +- requested quality of service; +- traffic flow template; +- protocol control information compression, on or off; +- PDP address; +- PDP type; +- Access Point Name (APN); +- protocol configuration options (if required by the PDP type). + +# 8 + +# 9 IP Based Services + +All protocols that are supported by the underlying IP protocol are applicable in the Packet Domain environment. However there may be some limitations due to the RF environment. + +The IP protocol can be run over various underlying protocols as shown in the figure 6. + +![Figure 6: IP Based Services. A diagram showing protocol layers for TE, R ref, and MT. The TE has layers: Applic., IP, L2/PPP, and L1. The MT has layers: IP RELAY, L2/PPP, and L1. A dashed arrow points from the MT's IP RELAY layer back to the TE's IP layer. The MT's L1 layer is connected to a 'Packet Domain Bearer' block. A vertical dashed line separates the TE and R ref from the MT.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +Figure 6: IP Based Services. A diagram showing protocol layers for TE, R ref, and MT. The TE has layers: Applic., IP, L2/PPP, and L1. The MT has layers: IP RELAY, L2/PPP, and L1. A dashed arrow points from the MT's IP RELAY layer back to the TE's IP layer. The MT's L1 layer is connected to a 'Packet Domain Bearer' block. A vertical dashed line separates the TE and R ref from the MT. + +**Figure 6: IP Based Services** + +PPP is a widely supported protocol in numerous operating systems and this alleviates the need for any Packet Domain specific protocol at the TE. PPP at the MT shall comply with the following specifications IETF STD 51 (RFC 1661, RFC 1662), RFC 1570, RFC 1989, RFC 1332 for IPv4, and optionally RFC 2472 for IPv6. Additionally for IPv4 any Domain Name Server information shall be delivered as defined in RFC 1877, and the delivery of any vendor-specific packets and options shall conform to RFC 2153. + +As an alternative to PPP, an L2 protocol can be used which is defined as a manufacturer's operating system dependent protocol capable of carrying IP frames over the R reference point. An example for such an L2 protocol is the Multi-Class Multi-Link (MCML) PPP. The MCML is defined in RFC 2686 and is based on Multi-Link (MP) PPP which is defined in RFC 1990. For IPv6 the L2 protocol shall support negotiation of the IPv6 Interface-Identifier between the TE and the MT. + +With IPv6, the process of setting up the IP connectivity is somewhat different than with IPv4 as it involves two distinct signalling phases. The first signalling phase is done in the control plane, followed by a second signalling phase done in the user plane. The control plane signalling phase, in the case of IPv6 over PPP, is described in section 9.1.2. The user plane signalling phase can be either stateless or stateful and is described in 3GPP TS 29.061 [17]. Support of the stateful address autoconfiguration procedure in the MS is optional. + +Stateful and Stateless Autoconfiguration may also co-exist. In that case, the MS shall use Stateless to configure the address and Stateful to configure additional parameters only. The MS shall not use Stateless and Stateful Address Autoconfiguration simultaneously since GPRS only supports one prefix per PDP Context (see 3GPP TS 29.061 [17]). + +Besides what is specified in the present document and in 3GPP TS 29.061, an MS supporting IPv6 shall comply with the guidelines specified in 3GPP TS 23.221 [48], subclause "UE support of IPv6". + +## 9.1 Example mapping of functions between the R reference point and the Packet Domain bearer for IP over PPP + +The following examples illustrate the case when the IP over PPP functionality is used in the MT. The example does not include all the details of PPP, but only describes the logical operation of PPP connection establishment, host authentication and IP configuration. + +Each interface at the R reference point can support only one PPP connection and each PPP connection can support only one IP session. Therefore, in PPP mode only one IP PDP context can be activated per interface at the R reference point. However, it is possible for a PCMCIA card (or other multiplexed interfaces) to support multiple virtual interfaces (communications ports) at the R reference point. Multiple PPP connections and IP contexts are possible in this case. + +### 9.1.1 IPv4 over PPP + +![Sequence diagram for IPv4 Over PPP Based Service showing interactions between TE, R, MT, and Um/Uu.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + +sequenceDiagram + participant TE + participant R + participant MT + participant Um/Uu + + Note left of TE: 1. AT command + TE->>MT: 1. AT command + Note right of MT: 2. AT response + MT-->>TE: 2. AT response + Note left of TE: 3. LCP Configure-Request + TE->>MT: 3. LCP Configure-Request + Note right of MT: 4. LCP Configure Ack + MT-->>TE: 4. LCP Configure Ack + Note left of TE: 5. LCP Configure-Request + TE->>MT: 5. LCP Configure-Request + Note right of MT: 6. LCP Configure Ack + MT-->>TE: 6. LCP Configure Ack + Note left of TE: 7. Host authentication + TE->>MT: 7. Host authentication + Note right of MT: 8. NCP Configure-Request + MT-->>TE: 8. NCP Configure-Request + Note right of MT: 9. PS Attach + MT->>Um/Uu: 9. PS Attach + Note right of Um/Uu: 10. PDP context Activation + Um/Uu-->>MT: 10. PDP context Activation + Note left of TE: 11. NCP Configure Ack + MT-->>TE: 11. NCP Configure Ack + +``` + +Sequence diagram for IPv4 Over PPP Based Service showing interactions between TE, R, MT, and Um/Uu. + +**Figure 7a: IPv4 Over PPP Based Service** + +- 1) The TE issues AT commands to set up parameters and enter PPP mode (refer to subclause on AT commands for further details). +- 2) The MT sends AT responses to the TE. +- 3) The PPP protocol in the TE sends a LCP Configure-Request. This command is to establish a PPP link between the TE and the MT. +- 4) The MT returns LCP Configure-Ack to the TE to confirm that the PPP link has been established. The MT might previously have sent a LCP Configure-Nak in order to reject some options proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 5) The PPP protocol in the MT sends a LCP Configure-Request in order to negotiate for the authentication protocol used for authentication of the host TE towards the MT. The MT shall initially negotiate for CHAP, and if this is unsuccessful, for PAP. +- 6) The TE returns a LCP Configure-Ack to the MT to confirm the use of the specified authentication protocol. The MT might previously have sent a LCP Configure-Nak in order to reject the protocol proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 7) If the negotiated authentication protocol is either of CHAP or PAP, the TE authenticates itself towards the MT by means of that protocol. The MT stores the necessary authentication data and sends a locally generated positive acknowledgement of the authentication to the TE. If none of the protocols is supported by the host TE no authentication shall be performed. Refer to 3GPP TS 29.061 for further details on the authentication. +- 8) The PPP protocol in the TE sends to the MT a NCP Configure-Request. This command activates the IP protocol. +- 9) If the MS is not yet PS attached, the MT performs the PS Attach procedure as described in 3GPP TS 23.060. + +- 10) The MT performs a PDP Context Activation as described in 3GPP TS 23.60. IP configuration parameters may be carried between the MT and the network in the Protocol Configuration Options IE in PDP Context Activation messages. The Protocol Configuration Options IE sent to the network may contain zero or one NCP Configure-Request packet (in addition to any LCP and authentication packets). The Protocol Configuration Options IE received from the network may contain zero or one NCP Configure-Ack, zero or one Configure-Nak and/or zero or one Configure-Reject packets (in addition to any LCP and authentication packets). + +- 11) Based on the information received in the Protocol Configuration Options IE, the MT acknowledges to the PPP protocol in the TE that the IP protocol is now activated by sending a NCP Configure-Ack command. Before sending a NCP Configure-Ack, the MT might previously have sent a NCP Configure-Nak and/or Configure-Reject in order to reject some IP parameters proposed by the TE. This in turn might have triggered a retransmission of the NCP Configure-Request with different parameter values. The decision to reject a specific parameter or parameter value may be based on the information received from the network in the Protocol Configuration Options IE. NCP Configure-Ack may also carry IP protocol related parameters such as dynamic IP address to the TE. The MT shall also pass name server information to the TE if the TE has requested for it and if this information is provided by the GGSN. Other packet types and options may optionally be delivered. The MT may choose to immediately deactivate the PDP context due to the information received from the network in the Protocol Configurations Options IE. + +### 9.1.2 IPv6 over PPP + +![Sequence diagram showing PDP Context Activation for IPv6 over PPP. It involves TE, R (reference point), MT, and Um/Uu interface. Steps include AT commands, LCP configuration, host authentication, IPV6CP configuration, PS Attach, and PDP context activation with parameters like Interface Id, Compression, PDP Type, and PCO.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant TE + participant R + participant MT + participant Um/Uu + + TE->>MT: 1. AT command + MT->>TE: 2. AT response + TE->>MT: 3. LCP Configure-Request + MT->>TE: 4. LCP Configure Ack + MT->>TE: 5. LCP Configure-Request + TE->>MT: 6. LCP Configure Ack + TE->>MT: 7. Host authentication + MT->>TE: 8. IPV6CP Configure-request + Note over TE,MT: [Interface Id, Compression] + MT->>Um/Uu: 9. PS Attach + Um/Uu->>MT: 10. PDP context Activation + Note over MT,Um/Uu: [PDP Type, PDP Addr, PCO] + MT->>TE: 11. IPV6CP Configure-Ack + Note over TE,MT: [Interface Id, Compression] + TE->>MT: IPV6CP Configure-Nak + Note over TE,MT: [Interface Id] + MT->>TE: IPV6CP Configure-request + Note over TE,MT: [Interface Id, Compression] + TE->>MT: IPV6CP Configure-Ack + Note over TE,MT: [Interface Id, Compression] + +``` + +Sequence diagram showing PDP Context Activation for IPv6 over PPP. It involves TE, R (reference point), MT, and Um/Uu interface. Steps include AT commands, LCP configuration, host authentication, IPV6CP configuration, PS Attach, and PDP context activation with parameters like Interface Id, Compression, PDP Type, and PCO. + +**Figure 7b: PDP Context Activation for the IPv6 over PPP based services** + +- 1) The TE issues AT commands to set up parameters and enter PPP mode (refer to subclause on AT commands for further details). +- 2) The MT sends AT responses to the TE. +- 3) The PPP protocol in the TE sends a LCP Configure-Request. This command is to establish a PPP link between the TE and the MT. +- 4) The MT returns LCP Configure-Ack to the TE to confirm that the PPP link has been established. The MT might previously have sent a LCP Configure-Nak in order to reject some options proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 5) The PPP protocol in the MT sends a LCP Configure-Request in order to negotiate for the authentication protocol used for authentication of the host TE towards the MT. The MT shall initially negotiate for CHAP, and if this is unsuccessful, for PAP. +- 6) The TE returns a LCP Configure-Ack to the MT to confirm the use of the specified authentication protocol. The MT might previously have sent a LCP Configure-Nak in order to reject the protocol proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 7) If the negotiated authentication protocol is either of CHAP or PAP, the TE authenticates itself towards the MT by means of that protocol. The MT stores the necessary authentication data and sends a locally generated positive acknowledgement of the authentication to the TE. If none of the protocols is supported by the host TE no authentication shall be performed. Refer to 3GPP TS 29.061 for further details on the authentication. +- 8) The TE requests IPv6 Interface-Identifier negotiation by sending the IPV6CP Configure-Request message to the MT indicating the tentative Interface-Identifier chosen by the TE. The tentative Interface-Identifier has only local significance in the MT and shall not forwarded to the GGSN. +- 9) If the MS is not yet PS attached, the MT performs the PS Attach procedure as described in 3GPP TS 23.060. +- 10) The MT sends the Activate PDP context request message to the network, including the PDP Type, PDP Address and Protocol Configuration Options. The Protocol Configuration Options IE may contain negotiated LCP options such as negotiated Authentication Protocol as well as any authentication data previously stored in the MT. It may also contain a request for dynamic configuration of DNS server IPv6 addresses as described in 3GPP TS 29.061 [17]. The MS shall leave PDP Address empty and set PDP Type to 'IPv6'. + +Note: The protocol between the TE and MT may not support the same set of information as the interface from the MT to the network (e.g. DNS). + +The network responds with an Activate PDP Context Accept or an Activate PDP Context Reject, to the MS. The Protocol Configuration Options IE may contain configuration data such as a list of DNS server IPv6 addresses as described in 3GPP TS 29.061 [17]. In cases where the MS receives more than one server address, the MS shall adhere to the explicit prioritisation order of the list. The PDP Address shall contain an IPv6 address composed of a Prefix and an Interface-Identifier. The size of the Prefix shall be according to the maximum prefix length for a global IPv6 address as specified in the IPv6 Addressing Architecture, see RFC 2373 [49]. The Interface-Identifier shall be used to create a link-local IPv6 address, to be used in continued MS – GGSN user-plane signalling. The Prefix in the PDP Address shall be ignored by the MS. + +- 11) In case a PDP Context Accept was sent to the MS, the MT extracts the Interface-Identifier from the address received in the PDP Address IE and ignores the Prefix part. If this Interface-Identifier is identical to the tentative Interface-Identifier indicated in the IPV6CP Configure-Request message sent from the TE, the MT sends an IPV6CP Configure Ack packet, indicating this Interface-Identifier, to the TE. + +If the Interface-Identifier extracted from the address contained in the PDP Address IE is not identical to the tentative Interface-Identifier indicated in the IPV6CP Configure-Request message sent from the TE, the MT sends an IPV6CP Configure Nak packet, indicating the Interface-Identifier extracted from the address contained in the PDP Address IE, to the TE. The TE then sends a new IPV6CP Configure-Request message to the MT, indicating the same Interface-Identifier as was indicated in the received IPV6CP Configure Nak. Finally the MT responds with an IPV6CP Configure Ack packet. The negotiated Interface-Identifier shall be used in the TE to create a link-local address. + +After finalisation of the IPV6CP negotiations between TE and MT, the user plane link is established. Before the MS can communicate with other hosts on the Intranet/ISP it shall obtain an IPv6 Global or a Site-Local Unicast + +address. Given that exactly one Prefix is included in the Router Advertisement, depending upon whether the advertised Prefix is globally unique or Site-local unique, the MS can only generate either IPv6 Global address(es) or Site-local address(es) using this Prefix during the lifetime of a particular PDP Context. This is done using either Stateless or Stateful Address Autoconfiguration as described in 3GPP TS 29.061 [17]. + +When creating a Global or Site-Local Unicast Address, the MS may use the Interface-Identifier received during the PDP Context Activation phase or it may generate a new Interface-Identifier. There is no restriction on the uniqueness of the Interface-Identifier of the Global or Site-Local Unicast Address, since the Prefix itself is unique. Interface-Identifiers shall in any case be 64-bit long and follow standard interface-identifier guidelines as per IETF RFC 2373 [49] and RFC 2472 [46]. + +In case a PDP Context Reject was sent to the MS the MT sends an LCP Terminate-Request to the TE, the TE and MT negotiate for link termination. The MT may then send a final AT-response to inform the TE about the rejected PDP Context activation. + +## 9.2 Example mapping of functions between the R reference point and the Packet Domain bearer for IP over MCML PPP + +When MCML is used instead of standard PPP [34] at the R-reference point, it is possible to support multiple IP sessions on one MCML connection. This is achieved by using an additional MP header after the standard PPP header. MCML provides two different MP headers, a 2-byte header to have four IP sessions and a 4-byte header to have sixteen IP sessions multiplexed over the MCML connection. + +Since both MP and MCML closely follow the PPP connection establishment and negotiation model described in subclause 9.1, it is not replicated in this subclause. The major difference is the additional negotiation capabilities used during the LCP configuration negotiation [44], [45]. + +# 10 PPP Based Services + +By means of the PDP type 'PPP' the Packet Domain may support interworking with networks based on the point-to-point protocol (PPP), as well as with networks based on any protocol supported by PPP through one of its Network Control Protocols (NCPs). It may also support interworking by means of tunnelled PPP, by e.g. the Layer Two Tunnelling Protocol (L2TP). The protocol configurations are depicted in figures 8a and 8b. + +![Figure 8a: PPP Based Services (transparent PPP negotiation). This diagram shows the protocol stack for transparent PPP negotiation. On the left, the TE (Terminal Equipment) stack consists of Application, L3, PPP, L2, and L1 layers. The MT (Mobile Terminal) stack consists of L1, L2, and a 'Packet Domain Bearer' layer. The GGSN (PDG) stack consists of a 'Packet Domain Bearer' layer and a PPP layer. Dashed arrows indicate the flow of PPP negotiation messages: from the TE's PPP layer, through the MT's L2 layer, to the GGSN's PPP layer, and back. Vertical dashed lines mark the R ref (between TE and MT) and Gi ref (after GGSN) points.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +Figure 8a: PPP Based Services (transparent PPP negotiation). This diagram shows the protocol stack for transparent PPP negotiation. On the left, the TE (Terminal Equipment) stack consists of Application, L3, PPP, L2, and L1 layers. The MT (Mobile Terminal) stack consists of L1, L2, and a 'Packet Domain Bearer' layer. The GGSN (PDG) stack consists of a 'Packet Domain Bearer' layer and a PPP layer. Dashed arrows indicate the flow of PPP negotiation messages: from the TE's PPP layer, through the MT's L2 layer, to the GGSN's PPP layer, and back. Vertical dashed lines mark the R ref (between TE and MT) and Gi ref (after GGSN) points. + +Figure 8a: PPP Based Services (transparent PPP negotiation) + +![Figure 8b: PPP Based Services (relayed PPP negotiation). This diagram shows the protocol stack for relayed PPP negotiation. The TE stack is identical to Figure 8a. The MT stack now includes a PPP layer between the L2 and Packet Domain Bearer layers. The GGSN stack also includes a PPP layer. Dashed arrows show the relayed negotiation: from the TE's PPP layer to the MT's PPP layer, then from the MT's PPP layer through the Packet Domain Bearer to the GGSN's PPP layer, and back. The L2 layer in the MT is shown without a direct connection to the GGSN's PPP layer in this configuration.](12de9b926df0384ec07702671827c9cd_img.jpg) + +Figure 8b: PPP Based Services (relayed PPP negotiation). This diagram shows the protocol stack for relayed PPP negotiation. The TE stack is identical to Figure 8a. The MT stack now includes a PPP layer between the L2 and Packet Domain Bearer layers. The GGSN stack also includes a PPP layer. Dashed arrows show the relayed negotiation: from the TE's PPP layer to the MT's PPP layer, then from the MT's PPP layer through the Packet Domain Bearer to the GGSN's PPP layer, and back. The L2 layer in the MT is shown without a direct connection to the GGSN's PPP layer in this configuration. + +Figure 8b: PPP Based Services (relayed PPP negotiation) + +NOTE. In the above case the 'L2' protocol is compliant with [35]. + +The 'L3' protocol is a network layer protocol supported by one of the PPP NCP's. All protocols currently supported by NCP's are listed in [36]. + +The PPP is a widely supported protocol in numerous operating systems and this alleviates the need for any Packet Domain specific protocol at the TE. PPP at the GGSN shall comply with [34]. The Domain Name Server information shall be delivered as defined in [40]. The delivery of any vendor-specific packets and options shall conform to [41]. + +The 'L2' protocol may be the link layer protocol defined for the PPP suite [35]. As an alternative an 'L2' protocol can be used which is defined as a manufacturer's operating system dependent protocol capable of carrying PPP frames over the R reference point. In case the link layer protocol defined for the PPP suite [35] is used as 'L2' protocol, the MT may negotiate LCP options related to the 'L2' framing (e.g. 'ACCM' [35], 'ACFC' [34] and 'FCS-Alternatives' [37]), with the TE. The MT shall remove the 'L1' and 'L2' specific framing from PPP frames in the uplink direction and add it in the downlink direction (see figure 8b). + +## 10.1 Example mapping of functions between the R reference point and the Packet Domain bearer (transparent PPP negotiation) + +The following example illustrates the case when the PPP negotiation is carried out transparently between the TE and the GGSN. The example does not include all the details of PPP, but only describes the logical operation of PPP LCP, host authentication and PPP NCP negotiations. + +![Sequence diagram illustrating transparent PPP negotiation between TE, R, MT, and GGSN.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` +sequenceDiagram + participant TE + participant R + participant MT + participant GGSN + Note right of R: (R is a dashed line) + TE->>MT: 1. AT command + MT->>GGSN: 2. PDP context Activation + MT-->>TE: 3. AT response + Note right of R: (MT and GGSN interaction continues) + TE->>GGSN: 4. LCP Configure-Request + GGSN-->>TE: 5. LCP Configure Ack + GGSN->>TE: 6. LCP Configure-Request + TE-->>GGSN: 7. LCP Configure Ack + TE->>GGSN: 8. Host authentication + GGSN->>TE: 9. NCP Configure-Request + TE-->>GGSN: 10. NCP Configure Ack +``` + +The diagram is a sequence diagram showing the interaction between four entities: TE (Terminal Equipment), R (Reference point, represented by a dashed line), MT (Mobile Terminal), and GGSN (Gateway GPRS Support Node). The sequence of messages is as follows: 1. AT command from TE to MT; 2. PDP context Activation from MT to GGSN; 3. AT response from MT to TE; 4. LCP Configure-Request from TE to GGSN; 5. LCP Configure Ack from GGSN to TE; 6. LCP Configure-Request from GGSN to TE; 7. LCP Configure Ack from TE to GGSN; 8. Host authentication from TE to GGSN; 9. NCP Configure-Request from GGSN to TE; 10. NCP Configure Ack from TE to GGSN. + +Sequence diagram illustrating transparent PPP negotiation between TE, R, MT, and GGSN. + +**Figure 9a: PPP Based Service (transparent PPP negotiation)** + +- 1) The TE issues AT commands to set up parameters and activate a PDP Context (refer to sub-clause on AT commands for further details). +- 2) The MT performs a PDP Context Activation as described in 3GPP TS 23.060. +- 3) The MT sends AT responses to the TE. +- 4) The PPP protocol in the TE sends an LCP Configure-Request. This command establishes a PPP link between the TE and the GGSN. +- 5) The GGSN returns an LCP Configure-Ack to the TE to confirm that the PPP link has been established. The GGSN might previously have sent an LCP Configure-Nak in order to reject some options proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 6) The PPP protocol in the GGSN sends an LCP Configure-Request in order to negotiate for the authentication protocol used for authentication of the host TE towards the GGSN. +- 7) The TE returns an LCP Configure-Ack to the GGSN to confirm the use of the specified authentication protocol. The GGSN might previously have sent an LCP Configure-Nak in order to reject the protocol proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 8) The TE authenticates itself towards the GGSN by means of the negotiated protocol. If no authentication protocol can be negotiated the GGSN may reject the PPP connection. Refer to 3GPP TS 09.61 for further details on the authentication. + +- 9) The PPP protocol in the TE sends to the GGSN an NCP Configure-Request. This command activates the network layer protocol. +- 10) The GGSN acknowledges to the PPP protocol in the TE that the network layer protocol is now activated by sending an NCP Configure-Ack command. Before sending an NCP Configure-Ack, the GGSN might previously have sent an NCP Configure-Nak in order to reject some parameters proposed by the TE. This in turn might have triggered a retransmission of the NCP Configure-Request with different parameter values. + +## 10.2 Example mapping of functions between the R reference point and the Packet Domain bearer (relayed PPP negotiation) + +The following example illustrates the case where the link layer protocol defined for the PPP suite [35] is used as 'L2' protocol. The LCP options related to the 'L2' framing (e.g. 'ACCM', 'ACFC' and 'FCS-Alternatives') are negotiated between the TE and the MT. All other PPP negotiation is relayed transparently between the TE and the GGSN. The example does not include all the details of PPP, but only describes the logical operation of PPP LCP, host authentication and PPP NCP negotiations. + +![Sequence diagram showing PPP negotiation between TE, R, MT, and GGSN. The diagram illustrates the flow of messages for AT commands, PDP context activation, LCP negotiation, host authentication, and NCP negotiation.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` + +sequenceDiagram + participant TE + participant R + participant MT + participant GGSN + Note right of R: --- + TE->>MT: 1. AT command + MT->>GGSN: 2. PDP context Activation + MT->>TE: 3. AT response + Note right of R: --- + TE->>MT: 4. LCP Configure-Request + MT->>GGSN: 5. LCP Configure Ack + GGSN->>MT: 6. LCP Configure-Request + MT->>TE: 7. LCP Configure Ack + TE->>GGSN: 8. Host authentication + GGSN->>MT: 9. NCP Configure-Request + MT->>TE: 10. NCP Configure Ack + +``` + +Sequence diagram showing PPP negotiation between TE, R, MT, and GGSN. The diagram illustrates the flow of messages for AT commands, PDP context activation, LCP negotiation, host authentication, and NCP negotiation. + +**Figure 9b: PPP Based Service (relayed PPP negotiation)** + +- 1) The TE issues AT commands to set up parameters and activate a PDP Context (refer to sub-clause on AT commands for further details). +- 2) The MT performs a PDP Context Activation as described in 3GPP TS 23.060. +- 3) The MT sends AT responses to the TE. +- 4) The PPP protocol in the TE sends an LCP Configure-Request. If the request contains options related to the 'L2' framing these are negotiated by the MT. The LCP Configure-Request shall subsequently be relayed to the GGSN. + +- 5) The GGSN returns an LCP Configure-Ack to the MT. The MT may change the value(s) of any options related to 'L2' framing and thereafter return an LCP Configure-Ack to the TE to confirm that the PPP link has been established. The MT might previously have sent an LCP Configure-Nak to the TE in order to reject some options proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 6) The PPP protocol in the GGSN sends an LCP Configure-Request in order to negotiate for e.g. the authentication protocol used for authentication of the host TE towards the GGSN. The request is relayed to the TE. +- 7) The TE returns an LCP Configure-Ack to the MT to confirm the use of e.g. the specified authentication protocol. The acknowledgement is relayed to the GGSN. The GGSN might previously have sent an LCP Configure-Nak in order to reject the protocol proposed by the TE. This in turn might have triggered a retransmission of the LCP Configure-Request with different options. +- 8) The TE authenticates itself towards the GGSN by means of the negotiated protocol. The messages are relayed transparently by the MT. If no authentication protocol can be negotiated the GGSN may reject the PPP connection. Refer to 3GPP TS 29.061 for further details on the authentication. +- 9) The PPP protocol in the TE sends an NCP Configure-Request to the MT, which relays it transparently to the GGSN. +- 10) The GGSN acknowledges to the PPP protocol in the TE that the network layer protocol is now activated, by sending an NCP Configure-Ack command, transparently relayed by the MT. Before sending an NCP Configure-Ack, the GGSN might previously have sent an NCP Configure-Nak in order to reject some parameters proposed by the TE. This in turn might have triggered a retransmission of the NCP Configure-Request with different parameter values. + +# --- 11 Internet Hosted Octet Stream Service (IHOSS) + +Void. + +# --- 12 AT commands + +3GPP TS 27.007 defines commands that a TE may use to control a MT supporting Packet Switched services, via either a non-multiplexed character-stream interface or a multiplexed character stream interface (27.010). A non-multiplexed character stream interface places certain limitations on the functionality of the interface. For example, it is not possible for the MT to send control information to the TE or for the TE to send commands to the MT whilst the interface is in the V.250 online data state unless the layer 2 protocol itself supports this feature. However, a manufacturer-specific escape mechanism may be provided to enable the TE to switch the MT into the V.250 online command state. It is anticipated that MTs will vary widely in functionality. At one extreme, a class A or PS/CS MT might support multiple PDP types as well as circuit switched data, and use multiple external networks and QoS profiles. At the other extreme a class C or PS MT might support only a single PDP type using a single external network, and rely on the HLR to contain the context definition. + +A comprehensive set of Packet Domain -specific AT commands is defined in 3GPP TS 27.007 to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new PDP types and interface protocols, merely by defining new values for many of the parameters. Multiple contexts may be activated if the interface link-layer protocol is able to support them. The commands use the extended information and error message capabilities described in 3GPP TS 27.007. + +For MTs of intermediate complexity, most commands have simplified forms where certain parameters may be omitted. + +For the simplest MTs, and for backwards compatibility with existing communications software, it is possible to control access to the Packet Domain using existing modem-compatible commands. A special dial-string syntax is defined for use with the D command. This "modem compatible" mode of operation is described in 3GPP TS 27.007. + +Subclause 12.2 contains examples of command sequences for a number of applications. + +Annex A of the present document lists the AT commands for the Packet Domain. They are fully defined in 3GPP TS 27.007. + +## 12.1 General on AT commands + +The following subclauses describe how the AT commands are used for the Packet Domain. The AT commands themselves are fully described in 3GPP TS 27.007. Reference to the particular AT command names are shown only for clarity. In all case refer to 3GPP TS 27.007 for the latest descriptions. + +### 12.1.1 Interaction of AT commands, Packet Domain management and PDPs + +State machines may be used to describe the behaviour of: + +- AT commands (ITU-T V.250); +- PDP context management (3GPP TS 23.060); +- PDP startup, data transfer and termination (Packet Data Protocol specifications); +- the layer 2 protocol (if any) used across the TE-MT interface (layer 2 protocol specifications). + +This subclause does not attempt to describe in detail how these state machines interact but rather to give some general guidance on their relationships. + +#### 12.1.1.1 AT commands and responses + +AT commands may be issued and responses received by the TE only when the TE and MT are in V.250 command state. + +The possibility of suspending the PDP and/or layer 2 protocol and entering V.250 online command state is not considered here; neither is the use of a multiplexed interface where the PDP and the AT commands use separate logical channels. + +#### 12.1.1.2 PDP and layer 2 protocol operation + +The PDP (across the TE-MT interface) may startup, transfer data and terminate only when the TE and MT are in V.250 online data state. It may be necessary to startup a layer 2 protocol across the interface before starting the PDP. The PDP startup procedure may provide information needed for the PDP context activation procedure (see subclause 10.1.1.3.2). + +#### 12.1.1.3 Management of Packet Switched services + +A particular PDP may be used to transfer data only when a context is active for that PDP. Before a context can be activated, the MT must be attached to the Packet Domain network. + +In order to provide flexibility and support a variety of types of MT and PDP, AT commands are provided which give the TE explicit control over attachment and detachment (+CGATT), and context activation and deactivation (+CGACT) procedures. These commands allow the TE to retain control of the MT, and receive status information from the MT, after these actions have been performed. + +##### 12.1.1.3.1 PS attachment + +The MT may be attached and detached using the +CGATT command. However, it may not be necessary to use the command since attachment may occur: + +- on power up or reset; +- when an attempt is made to activate a context either explicitly (+CGACT) or as a result of a PDP startup procedure; +- when the mobile class is changed (+CGCLASS). + +Similarly, detachment may occur: + +- as a result of a PDP termination procedure (if no other Packet Switched services are active); +- when the mobile class is changed (+CGCLASS). + +##### 12.1.1.3.2 PDP context activation + +Certain information must be provided to the network in order for a context activation attempt to be successful. The TE may provide some of this information to the MT during the PDP startup procedure rather than through AT command procedures. In this case the context activation cannot be initiated by the +CGACT command but rather on receipt of the appropriate information during the PDP startup. + +### 12.1.2 Use of default context parameter values + +The activate context request message sent by the MT to the network contains a number of parameters whose values can usefully be set by the TE. Under certain circumstances the values for some or all of the parameters need not be provided by the TE, either via AT commands or the PDP startup procedure. The storage of context information in the SIM is not considered in the present document. Rules concerning what values shall be sent by the MT to the network under various circumstances are given in 3GPP TS 23.060. + +One particular rule that is designed to simplify operation in modem compatibility mode is that if there is only one PDP context subscription in the HLR then all of PDP type, PDP address and APN may be omitted. + +#### 12.1.2.1 PDP type + +This may be omitted: + +- when the MT supports only one PDP type (it will be provided by the MT); or +- according to the rules given in 3GPP TS 23.060. + +#### 12.1.2.2 PDP address (of the MS) + +This shall be omitted when: + +- a dynamic address is required; or +- according to the rules given in 3GPP TS 23.060. + +#### 12.1.2.3 Access Point Name + +This may be omitted: + +- according to the rules given in 3GPP TS 23.060. + +#### 12.1.2.4 QoS Requested + +This may be omitted when: + +- the default subscribed QoS is acceptable. + +When the application in the TE requires streaming or conversational QoS, then the MS shall at least explicitly request the traffic class and should explicitly request the guaranteed bit rate and the maximum bit rate. + +#### 12.1.2.5 PDP Configuration Options + +These shall be omitted: + +- when none are required for the PDP concerned; or +- according to the rules given for the PDP. + +## 12.2 Example command sequences for dial-compatibility mode + +### 12.2.1 PPP in dial compatibility mode + +#### 12.2.1.1 Mobile initiated IP context activation + +In this mode of operation, the MT behaves like an originating modem and accepts the normal V.250 commands associated with placing and clearing a call to a dial-up PPP server. Although the procedures for setting up the IP context + +are initiated from the mobile end, IP-based sessions, for example the File Transfer Protocol (FTP), may be initiated from either end once the context is active. + +For this example it is assumed that: + +- the user has subscribed to only one PDP context (of type IP) and therefore no context parameter values are needed; +- the MT supports only PPP at the MT-TE interface and therefore no layer 2 protocol need be specified. + +A possible sequence of events is: + +- the MT begins in V.25 command state: + - TE -> MT: AT; + - MT -> TE: OK. +- the TE sends a dial command requesting the Packet Switched service: + - TE -> MT: ATD\*99#; + - MT -> TE CONNECT. +- the MT enters V.250 online data state: + - TE starts up PPP (LCP exchange); + - TE -> MT: LCP Configure-request; + - MT -> TE: LCP Configure-ack: + - PPP Authentication may take place (optional); + - TE starts up IP (NCP for IP exchange): + - TE -> MT: NCP(IP) Configure-request; + - MT <-> network: MT performs the PS-attach procedure if the MT is not currently attached; + - MT <-> network: MT performs the IP context activation procedure; + - MT -> TE: NCP(IP) Configure-ack; + - TE <-> MT <-> network: IP packets may now be transferred. + - TE stops IP (optional): + - TE-> MT: NCP(IP) Terminate-Request ); this + - MT<-> network: MT performs the IP context deactivation procedure); is + - MT -> TE: NCP(IP) Terminate-Ack ) optional. + - TE stops PPP: + - TE-> MT:LCP Terminate-Request; + - MT <-> network: MT performs the IP context deactivation procedure if it has not already done so; + - MT <-> network: MT may perform the PS-detach procedure if no other Packet Switched services are active; + - MT -> TE: LCP Terminate-Ack. +- *the MT returns to V.250 command state and issues the final result code :* + - MT -> TE NO CARRIER. + +*The TE may recognise this as a return to V.250 command state. However, if it is using procedures intended for controlling modems, it may attempt to force a disconnect since in the modem case it cannot rely on the remote modem dropping the carrier. It will use some combination of:* + +- TE -> MT: TE drops circuit 108/2 (Data Terminal Ready); +- TE -> MT: escape sequence (e.g. +++); +- TE -> MT: ATH. + +*The MT should respond according to V.250 even if it is already in command state.* + +*If the connection is lost at any time, the MT shuts down PPP, returns to V.250 command state and issues the final result code:* + +- MT -> TE NO CARRIER. + +#### 12.2.1.2 Network requested IP context activation + +In this mode of operation, the MT behaves like an answering modem and accepts the normal V.250 commands associated with answering a call to a PPP server. Although the procedures for setting up the IP context are initiated from the network end, IP-based sessions, for example the File Transfer Protocol (FTP), may be initiated from either end once the context is active. + +Two example sequences of events are given, for the cases of automatic and manual answering: + +##### Case 1: automatic answering + +*The MT begins in V.250 command state:* + +- TE -> MT: AT. + +*The TE sets automatic answering mode:* + +- TE -> MT: ATS0=1; +- MT <-> network: MT performs the PS-attach procedure if the MT is not currently attached. + +*Subsequently:* + +- network -> MT: Request PDP Context Activation message; +- MT -> TE: RING. + +*The MT returns the intermediate result code:* + +- MT -> TE CONNECT, + +*and enters V.250 online data state.* + +*The TE and MT perform the PPP and IP startup procedures which include the MT requesting the network to activate the IP context.* + +##### Case 2: manual answering + +*The MT begins in V.250 command state:* + +- TE -> MT: AT. + +*The TE sets manual answering mode and requests a PS-attach (if necessary):* + +- TE -> MT: ATS0=0; +- TE -> MT: AT+CGATT=1; +- MT <-> network: MT performs the PS-attach procedure if the MT is not currently attached; +- network -> MT: Request PDP Context Activation message; + +- MT -> TE: RING. + +*The TE answers manually:* + +- TE -> MT: ATA; +- MT -> TE CONNECT, + +*and enters V.250 online data state.* + +*The TE and MT perform the PPP and IP startup procedures which include the MT requesting the network to activate the IP context:* + +*or the TE rejects the connection:* + +- TE -> MT: ATH. + +*and remains in V.250 command state.* + +# --- 13 IMS related functions + +## 13.1 General + +IP Multimedia Core Network Subsystem (IMS) related functions affects the way the MS sets up some Session Management information elements when activating or modifying PDP context(s). + +IMS is based on IETF protocols with SIP as described in RFC 3261 [54] as the framework. Example signalling flows can be found in 3GPP TS 24.228 [50], while differences between standard SIP and IMS are specified in 3GPP TS 24.229 [51]. + +GPRS aspects within the MS when connected to IMS are specified in 3GPP TS 24.229 [51], while the corresponding functionality within the GGSN, PCF and P-CSCF is specified in 3GPP TS 29.061 [17] and 3GPP TS 29.207 [52]. Encoding of the session management information elements relevant for IMS are specified in 3GPP TS 24.008 [12]. + +Mapping of SDP to QoS attributes and authorisation of QoS attributes is specified in 3GPP TS 29.208 [53]. + +## 13.2 DNS Server Discovery + +In the IMS the MS can request a DNS Server IPv6 address(es) via normal IETF DHCPv6 [55] request/response signalling or by using the Protocol Configuration Option information element when requesting PDP context activation. The corresponding procedure is specified in 3GPP TS 29.061 [17] + +## 13.3 P-CSCF Server Discovery + +In the IMS the MS can request a P-CSCF IPv6 address(es) for SIP signalling via normal IETF DHCPv6 request/response signalling in combination with normal IETF DNS request/response signalling or by using the Protocol Configuration Option information element when requesting PDP context activation. The P-CSCF discovery procedure is specified in 3GPP TS 24.229 [51]. + +## 13.4 PDP Context used for IMS Signalling + +Before the MS can request IMS services, a PDP context is activated to carry the IMS signalling. This PDP context can be for IMS signalling only or a general-purpose PDP context (i.e. may also carry the media). The MS can request that a PDP context is for IMS signalling only by setting the IM CN subsystem signalling flag in the Protocol Configuration Option information element when activating a PDP context. Whether or not a PDP context is activated to be used for general purpose or for IMS signalling only, the MS can request that a PDP context will be prioritised by setting the QoS attribute Signalling Indication. The encoding of the IM CN subsystem signalling flag and the Signalling Indication information elements are specified in 3GPP TS 24.008 [12]. The corresponding procedures are specified in 3GPP TS 24.229 [51] and 3GPP TS 29.061 [17]. + +## 13.5 Binding Information + +The MS supports the binding mechanism for service-based local policy control. When an authorization token is included in an IMS SIP message, the MS will include binding information in the Traffic Flow Template information element when activating or modifying a PDP context intended to carry certain IMS IP flow(s). The binding information consists of the authorization token and the flow identifier(s) of the IMS IP flow(s) the MS puts on the same PDP context, e.g. due to the same QoS requirements for those IMS IP flows. The authorization token and the flow identifier are specified in 3GPP TS 29.207 [52]. + +If the MS multiplexes media flows from different IMS sessions in the same PDP Context, the MS shall include the binding information of all multiplexed sessions, i.e. the media authorization tokens of all multiplexed IMS sessions and the flow identifiers of all multiplexed IP flows, in the PDP Context Activation/Modification request. + +If the MS includes binding information, it shall populate the TFT filters with wildcard values. + +## 13.6 Mapping of SDP to QoS Attributes + +The type of application and the users choice of perceived quality are often fully enough information to set the requested QoS attributes when activating or modifying the PDP context(s) carrying the applications IMS IP flow(s). However, if the application receives SDP parameters, the MS can take guidance and map some of the SDP parameters, e.g. + +b=AS:, to the corresponding requested QoS attributes, e.g. Maximum and Guaranteed Bitrate for uplink and downlink. The rules for mapping SDP parameters to QoS attributes are specified in 3GPP TS 29.208 [53]. + +## 13.7 Authorization of QoS Attributes + +When the PDP context is activated or modified, for an IMS session where service-based local policy is applied, the MS can check that the values of some requested QoS attributes, e.g. Guaranteed or Maximum Bitrate uplink and downlink, do not exceed the values of the corresponding Maximum Authorized QoS attributes, e.g. Maximum Authorized Bandwidth uplink and downlink. The values of the Maximum Authorized QoS attributes are derived from the SDP parameters of the IMS media components identified. The rules for deriving the Maximum Authorized QoS attributes per flow identifier and per PDP context are specified in 3GPP TS 29.208 [53]. + +## 13.8 Support for forking + +A MS originating a SIP session is able to handle several forked responses. Forking can occur in a downstream SIP proxy outside the 3GPP network. In case of service-based local policy, the same authorization token is received for all the forked responses for that session. + +Detailed call control procedures for forking are specified in 3GPP TS 24.229 [51]. Specific procedures for setting the Maximum Authorized QoS attributes in relation to several forked responses are specified in 3GPP TS 29.207 [52] and 3GPP TS 29.208 [53]. + +## 13.9 Multiplexing of IMS media components to PDP contexts + +The IMS network may use the SDP attribute "a=group:SRF" to order the MS to multiplex certain IMS media components within the same session on the same PDP context. If this attribute is not present then multiplexing the media components on PDP contexts is entirely MS specific. The rules for multiplexing IMS media components to PDP contexts are specified in 3GPP TS 24.229 [51]. + +## 13.10 Policy control rejection of PDP context + +The GGSN rejects a PDP context activation or modification if service-based local policy cannot be exercised, e.g. erroneous binding information, or will not be exercised, e.g. binding information available although the current APN is not subject for policy control. The GGSN puts the actual Policy Control rejection code in the Protocol Configuration Option information element in the rejection message. An MS receiving a rejection message shall check the Protocol Configuration Option information element and take proper action. + +The rejection cases as well as the Policy Control rejection codes are specified in 3GPP TS 29.207 [52]. Rules for the MS when receiving policy control rejections of a PDP context activation or modification are specified in 3GPP TS 24.229 [51]. + +# Annex A (informative): Summary of AT commands for the Packet Domain + +This informative annex lists the AT commands for the Packet Domain that are fully described in 3GPP TS 27.007. + +**Table A.1: Summary of AT commands for the packet domain** + +| Command | Description | +|----------|--------------------------------------------------------------------| +| +CGACT | PDP context activate or deactivate | +| +CGANS | Manual response to a network request for PDP context activation | +| +CGATT | PS attach or detach | +| +CGAUTO | Automatic response to a network request for PDP context activation | +| +CGCLASS | PS mobile station class | +| +CGCLOSP | | +| +CGCLPAD | | +| +CGDATA | Enter data state | +| +CGDCONT | Define PDP context | +| +CGEREP | Control unsolicited PS event reporting | +| +CGPADDR | Show PDP address | +| +CGREG | Packet Domain network registration status | +| +CGQMIN | Quality of service profile (minimum acceptable) | +| +CGQREQ | Quality of service profile (requested) | +| +CGSMS | Select service for MO SMS messages | + +**Table A.2: Summary of Packet Domain Extensions to existing A/Gb mode AT commands** + +| Command | Description | +|---------|-------------------------------------------------| +| +CEER | Extended error report (refer to 27.007) | +| +CMEE | Report mobile equipment error (refer to 27.007) | +| +CR | Service reporting control (refer to 27.007) | +| +CRC | Cellular result codes (refer to 27.007) | + +**Table A.3: Summary of AT commands for Packet Domain modem compatibility mode** + +| Command | Description | +|---------|----------------------------------------------------------------------------------------------------| +| A | Answer – manual acceptance of a network request for PDP context activation | +| D | Dial – request Packet Domain service | +| H | On-hook - manual rejection of a network request for PDP context activation | +| S0 | Automatic answering control - automatic acceptance of a network request for PDP context activation | + +# --- Annex B (informative): Octet Stream Protocol (OSP) PDP type + +Void + +# Annex C (informative): Change history + +| Change history | | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|----------------------------------------------------------------------|-----------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | | Old | New | +| 06-2004 | TSG#24 | NP-040247 | 089 | 2 | Multiple IMS sessions using the same PDP context | | 5.6.0 | 6.0.0 | +| 06-2007 | TSG#36 | | | | Upgraded to v7.0.0 | | 6.0.0 | 7.0.0 | +| 12-2008 | TSG#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | | 7.0.0 | 8.0.0 | +| 12-2009 | TSG#46 | | | | Automatic upgrade from previous Release | | 8.0.0 | 9.0.0 | +| 12-2010 | TSG#50 | CP-100779 | 91 | 1 | Correcting non-specific external references | | 9.0.0 | 9.1.0 | +| 03-2011 | TSG#51 | | | | Automatic upgrade from previous Release version 9.0.0 | | 9.0.0 | 10.0.0 | +| 03-2011 | TSG#51 | | | | Correction of heading and numbering made by MCC | | 10.0.0 | 10.0.1 | +| 09-2012 | TSG#57 | | | | Automatic upgrade from previous Release version 10.0.1 | | 10.0.1 | 11.0.0 | +| 10-2014 | | | | | Automatic upgrade from previous Release | | 11.0.0 | 12.0.0 | +| 12-2015 | | | | | Automatic upgrade from previous Release | | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | | +| 2018-06 | CT#80 | | | | | Automatic upgrade from previous Release | 15.0.0 | | +| 2020-06 | CT#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29168/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-16/29_series/29168/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7483b1fad91000c708540c5a92a486f873dc48d --- /dev/null +++ b/marked/Rel-16/29_series/29168/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bb8ff1c079619d8af229cf7901a59adffb92a51c33d95d844af63f170ccbb17 +size 24137 diff --git a/marked/Rel-16/29_series/29168/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-16/29_series/29168/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd6ea0efe1b19dbd0071f1a0c49e147437a2dac6 --- /dev/null +++ b/marked/Rel-16/29_series/29168/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:392fcc6d8b479c63e390e2f0f191ee74f123e3a56aa4295fb2c444c4b1d53acc +size 9791 diff --git a/marked/Rel-16/29_series/29168/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-16/29_series/29168/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..813d2a64ea57637b1b9e1eba2ab95191d4c1889b --- /dev/null +++ b/marked/Rel-16/29_series/29168/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38b8118f30bd3becb6a8f9596fd30515f7ebc3de3bff4f6c9419a774ea47cacd +size 11789 diff --git a/marked/Rel-16/29_series/29168/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29168/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a979b74c775a73dc04b0b29e8be86314afa629c --- /dev/null +++ b/marked/Rel-16/29_series/29168/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdb37624b0f68dacccb1e1bf5a4778315aa868b715a1fc3836cae2c76abb50a6 +size 9734 diff --git a/marked/Rel-16/29_series/29168/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29168/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482b48dee82332dca5b54780df2dba47d13cdd24 --- /dev/null +++ b/marked/Rel-16/29_series/29168/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dc2f752dda068a1ab7418ca1ee0fb54658d918439d42a1a2a1c8202d6cf34aa +size 5816 diff --git a/marked/Rel-16/29_series/29168/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/29_series/29168/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6ce8a2760d87833d45b819195e351e1f0daadc4 --- /dev/null +++ b/marked/Rel-16/29_series/29168/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74f2e473d069535eef8b0d23f399df81168e7df52b4d44a758cd803943773762 +size 10248 diff --git a/marked/Rel-16/29_series/29168/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/29_series/29168/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e6440e9ddfb8161db1a8576e0bc6611e1f1d519 --- /dev/null +++ b/marked/Rel-16/29_series/29168/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde51b67195952f32949789b7ef1354c6b56b9004f167f1b2a6db8e5e15d94c6 +size 13911 diff --git a/marked/Rel-16/29_series/29168/94d3fdcc244924326f02533aeb2d93fc_img.jpg b/marked/Rel-16/29_series/29168/94d3fdcc244924326f02533aeb2d93fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45dff5d5381e8da9fdbba14968afd92d9a610652 --- /dev/null +++ b/marked/Rel-16/29_series/29168/94d3fdcc244924326f02533aeb2d93fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62337aaece807d7e64f10741f825d19a82177d1c20a2c4a9f3600e285470fa13 +size 21749 diff --git a/marked/Rel-16/29_series/29168/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/29_series/29168/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2d16a46238c9ac4d639dbc788278145699116f5 --- /dev/null +++ b/marked/Rel-16/29_series/29168/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b6ba6642747574991010aa53938fc66bf5050ff214a4dc0dd07e5ad49467fb8 +size 14110 diff --git a/marked/Rel-16/29_series/29168/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-16/29_series/29168/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52bf9af20ad03034972c2c3de280cd47060030dd --- /dev/null +++ b/marked/Rel-16/29_series/29168/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa83926ae05527299aa386944b427477715a9f17e598d17b9bdc4a4855178c18 +size 20262 diff --git a/marked/Rel-16/29_series/29168/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/marked/Rel-16/29_series/29168/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d446b7e86e87596b1b0ef76174c6fa0c1dff7ab --- /dev/null +++ b/marked/Rel-16/29_series/29168/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f7eff655a47ffffe376852ad81a226a0f54a86e88dd8bc8e314f3b37bf11b71 +size 22299 diff --git a/marked/Rel-16/29_series/29168/e58a867750e4ae01604318506b79df7a_img.jpg b/marked/Rel-16/29_series/29168/e58a867750e4ae01604318506b79df7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6136009b40a0c07ee4b265165bf638cf848614a --- /dev/null +++ b/marked/Rel-16/29_series/29168/e58a867750e4ae01604318506b79df7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8acb30982f9bf05b72c17a2714b6e1164bad95f452f504f46fd74d33fc4bde1 +size 19855 diff --git a/marked/Rel-16/29_series/29168/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/29_series/29168/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c993ccef602f813e63291c30a10036f97c5a0c8 --- /dev/null +++ b/marked/Rel-16/29_series/29168/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:291457258bfaa50ee46dfdd568b8b51aa953fb348949a13144b9a5d4713e5512 +size 13326 diff --git a/marked/Rel-16/29_series/29168/raw.md b/marked/Rel-16/29_series/29168/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0885142365c1ac5552b77e4bac5e4fdc588a95c4 --- /dev/null +++ b/marked/Rel-16/29_series/29168/raw.md @@ -0,0 +1,3048 @@ + + +# 3GPP TS 29.168 V16.0.0 (2020-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3 (Release 16)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" is a green graphic element consisting of three curved lines of increasing height, resembling a signal strength indicator or a stylized wave. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. Below the "P" is a red graphic element consisting of three curved lines of increasing height, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 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 +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 SBc description ..... | 8 | +| 4.1 Transport ..... | 8 | +| 4.1.1 General ..... | 8 | +| 4.1.2 Network layer ..... | 8 | +| 4.1.3 Transport layer..... | 8 | +| 4.1.4 Services expected from signalling transport..... | 9 | +| 4.2. SBc-AP functions ..... | 9 | +| 4.2.1 Function of SBc-AP ..... | 9 | +| 4.3 SBc-AP procedure ..... | 9 | +| 4.3.1 General ..... | 9 | +| 4.3.2 List of SBc-AP elementary procedure..... | 9 | +| 4.3.3 Write Replace Warning Procedure ..... | 10 | +| 4.3.3.1 General ..... | 10 | +| 4.3.3.2 Successful Operation..... | 10 | +| 4.3.3.3 Unsuccessful Operation..... | 10 | +| 4.3.3A Stop Warning Procedure..... | 11 | +| 4.3.3A.1 General..... | 11 | +| 4.3.3A.2 Successful Operation ..... | 11 | +| 4.3.3A.3 Unsuccessful Operation..... | 11 | +| 4.3.3B Error Indication ..... | 12 | +| 4.3.3B.1 General..... | 12 | +| 4.3.3B.2 Successful Operation ..... | 12 | +| 4.3.3B.3 Abnormal Conditions..... | 12 | +| 4.3.3C Write Replace Warning Indication ..... | 12 | +| 4.3.3C.1 General..... | 12 | +| 4.3.3C.2 Successful Operation ..... | 13 | +| 4.3.3C.3 Abnormal Conditions..... | 13 | +| 4.3.3D Stop Warning Indication..... | 13 | +| 4.3.3D.1 General..... | 13 | +| 4.3.3D.2 Successful Operation ..... | 13 | +| 4.3.3D.3 Abnormal Conditions..... | 13 | +| 4.3.3E PWS Restart Indication ..... | 13 | +| 4.3.3E.1 General..... | 13 | +| 4.3.3E.2 Successful Operation ..... | 14 | +| 4.3.3E.3 Abnormal Conditions..... | 14 | +| 4.3.3F PWS Failure Indication ..... | 14 | +| 4.3.3F.1 General..... | 14 | +| 4.3.3F.2 Successful Operation ..... | 15 | +| 4.3.3F.3 Abnormal Conditions..... | 15 | +| 4.3.4 Message functional definition and content ..... | 15 | +| 4.3.4.1 Message contents ..... | 15 | +| 4.3.4.1.1 Presence..... | 15 | +| 4.3.4.1.2 Criticality..... | 15 | +| 4.3.4.1.3 Range..... | 16 | +| 4.3.4.1.4 Assigned Criticality..... | 16 | +| 4.3.4.2 Warning Message Transmission Messages ..... | 16 | +| 4.3.4.2.1 WRITE-REPLACE WARNING REQUEST ..... | 16 | +| 4.3.4.2.2 WRITE-REPLACE WARNING RESPONSE..... | 17 | +| 4.3.4.2.3 STOP WARNING REQUEST ..... | 18 | + +| | | | +|-----------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------| +| 4.3.4.2.4 | STOP WARNING RESPONSE..... | 19 | +| 4.3.4.2.5 | WRITE REPLACE WARNING INDICATION..... | 19 | +| 4.3.4.2.6 | STOP WARNING INDICATION ..... | 19 | +| 4.3.4.2.7 | PWS RESTART INDICATION ..... | 20 | +| 4.3.4.2.8 | PWS FAILURE INDICATION ..... | 21 | +| 4.3.4.2A | Management Messages ..... | 22 | +| 4.3.4.2A.1 | ERROR INDICATION..... | 22 | +| 4.3.4.3 | Information element definition ..... | 22 | +| 4.3.4.3.1 | Message Type..... | 22 | +| 4.3.4.3.2 | Cause ..... | 23 | +| 4.3.4.3.3 | Criticality Diagnostics..... | 23 | +| 4.3.4.3.4 | OMC ID..... | 24 | +| 4.3.4.3.5 | Send Write-Replace-Warning-Indication..... | 24 | +| 4.3.4.3.6 | Unknown Tracking Area List..... | 25 | +| 4.3.4.3.7 | Send Stop Warning Indication ..... | 25 | +| 4.3.4.3.8 | Stop-All Indicator..... | 25 | +| 4.3.4.3.9 | Broadcast Empty Area List ..... | 25 | +| 4.3.4.3.10 | RAT Selector 5GS..... | 26 | +| 4.3.4.3.11 | Unknown 5GS Tracking Area List..... | 26 | +| 4.3.4.3.12 | Broadcast Scheduled Area List 5GS ..... | 26 | +| 4.3.4.3.13 | Broadcast Cancelled Area List 5GS..... | 26 | +| 4.3.4.3.14 | Broadcast Empty Area List 5GS ..... | 27 | +| 4.4 | Message and information element abstract syntax..... | 27 | +| 4.4.1 | General ..... | 27 | +| 4.4.2 | Usage of protocol extension mechanism for non-standard use ..... | 27 | +| 4.4.3 | Elementary procedure definitions..... | 28 | +| 4.4.4 | PDU definitions ..... | 30 | +| 4.4.5 | Information element definitions ..... | 35 | +| 4.4.6 | Common definitions ..... | 44 | +| 4.4.7 | Constant definitions..... | 44 | +| 4.4.8 | Container Definitions ..... | 46 | +| 4.4.9 | Message transfer syntax ..... | 48 | +| 4.5 | Handling of unknown, unforeseen or erroneous protocol data ..... | 48 | +| 4.5.1 | General ..... | 48 | +| 4.5.2 | Transfer Syntax Error..... | 48 | +| 4.5.3 | Abstract Syntax Error..... | 48 | +| 4.5.3.1 | General ..... | 48 | +| 4.5.3.2 | Criticality information ..... | 49 | +| 4.5.3.3 | Presence information ..... | 49 | +| 4.5.3.4 | Not comprehended IE/IE group..... | 50 | +| 4.5.3.4.1 | Procedure code..... | 50 | +| 4.5.3.4.2 | Type of Message..... | 50 | +| 4.5.3.4.3 | IEs other than the Procedure Code and Type of Message ..... | 50 | +| 4.5.3.5 | Missing IE or IE group ..... | 51 | +| 4.5.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present ..... | 52 | +| 4.5.4 | Logical Error ..... | 53 | +| 4.5.5 | Exceptions ..... | 53 | +| Annex A (informative): Change history: ..... | | 54 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document specifies the procedures and the SBc Application Part (SBc-AP) messages used on the SBc-AP interface between the Mobility Management Entity (MME) and the Cell Broadcast Centre (CBC), and between the Public Warning System – Inter Working Function (PWS-IWF) and the CBC. + +The present document supports the following functions: + +- Warning Message Transmission function in the EPS, +- Warning Message Transmission function in the 5GS via the PWS-IWF (see 3GPP TS 23.041 [14]). + +NOTE: The SBc-AP interface is a logical interface between the MME and the CBC and also between the PWS-IWF and the CBC, when connected to 5GC. The PWS-IWF may not be always explicitly mentioned in the remainder of the present document. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] IETF RFC 2460 (December 1998): "Internet Protocol, Version 6 (IPv6) Specification". +- [3] IETF RFC 791 (September 1981): "Internet Protocol". +- [4] IETF RFC 4960 (September 2007): "Stream Control Transmission Protocol". +- [5] Void +- [6] Void +- [7] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (SIAP)" +- [8] ITU-T Recommendation X.680 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [9] ITU-T Recommendation X.681 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification". + +- [10] ITU-T Recommendation X.691 (07/2002): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [11] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [12] Void +- [13] 3GPP TS 22.268: "Public Warning System (PWS) requirements". +- [14] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [15] Void +- [16] 3GPP TS 23.007: "Restoration procedures". +- [17] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [18] 3GPP TS 23.527: "5G System; Restoration procedures". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Elementary Procedure:** SBc-AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between MME and CBC. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures, which can be active in parallel. Examples on using several SBc-APs together with each other and EPs from other interfaces can be found in reference [FFS]. + +An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success and/or failure). +- **Class 2:** Elementary Procedures without response. + +For Class 1 EPs, the types of responses can be as follows: + +Successful: + +- A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. + +Unsuccessful: + +- A signalling message explicitly indicates that the EP failed. +- On time supervision expiry (i.e. absence of expected response). + +Successful and Unsuccessful: + +- One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome. + +Class 2 EPs are considered always successful. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|---------|---------------------------------------| +| 5GC | 5G Core | +| CMAS | Commercial Mobile Alert System | +| CBC | Cell Broadcast Center | +| CBS | Cell Broadcast Service | +| EPC | Evolved Packet Core | +| EPS | Evolved Packet System | +| ETWS | Earthquake and Tsunami Warning System | +| MME | Mobility Management Entity | +| PWS | Public Warning System | +| PWS-IWF | PWS – Inter Working Function | +| SCTP | Stream Control Transmission Protocol | + +# --- 4 SBc description + +## 4.1 Transport + +### 4.1.1 General + +This clause specifies the standards for signalling transport to be used across SBc-AP interface. SBc-AP interface is a logical interface between the MME and the CBC. All the SBc-AP messages described in the present document require an SCTP association between the MME and the CBC. + +### 4.1.2 Network layer + +The MME and the CBC shall support IPv6 (see IETF RFC 2460 [2]) and/or IPv4 (see IETF RFC 791 [3]). + +The IP layer of SBc-AP only supports point-to-point transmission for delivering SBc-AP messages. + +### 4.1.3 Transport layer + +SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of SBc-AP messages. + +Semi-permanent SCTP associations shall be established between MME and CBC, i.e. the SCTP associations shall remain up under normal circumstances. + +Local multi-homing should be supported. Remote multi-homing shall be supported. + +Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between MME and CBC. + +Checksum calculation for SCTP shall be supported as specified in RFC 4960 [4]. + +The CBC shall establish the SCTP association. + +The registered port number for SBc-AP is 29168. + +The registered payload protocol identifier for SBc-AP is 24. + +### 4.1.4 Services expected from signalling transport + +The signalling connection shall provide in-sequence delivery of SBc-AP messages. SBc-AP shall be notified if the signalling connection breaks. + +## 4.2. SBc-AP functions + +### 4.2.1 Function of SBc-AP + +SBc-AP has the following function: + +- Warning Message Transmission function: +This functionality provides the means to start, overwrite and stop the broadcasting of warning message in support of the Public Warning System (PWS) messages as defined in 3GPP TS 22.268 [13] which include Commercial Mobile Warning System (CMAS) and Earthquake and Tsunami (ETWS) messages. + +## 4.3 SBc-AP procedure + +### 4.3.1 General + +This clause describes the parameters and detailed behaviors of different procedures. + +### 4.3.2 List of SBc-AP elementary procedure + +Table 4.3.2-1 lists the SBc-AP Elementary Procedures defined as class 1 procedures. + +**Table 4.3.2-1: SBc-AP class 1 elementary procedures** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|---------------------------------|-------------------------------|--------------------------------|----------------------| +| | | Response message | Response message | +| Write-Replace Warning procedure | WRITE-REPLACE WARNING REQUEST | WRITE-REPLACE WARNING RESPONSE | | +| Stop Warning Procedure | STOP WARNING REQUEST | STOP WARNING RESPONSE | | + +Table 4.3.2-2 lists the SBc-AP Elementary Procedures defined as class 2 procedures. + +**Table 4.3.2-2: SBc-AP class 2 elementary procedures** + +| Elementary Procedure | Initiating Message | +|--------------------------------------------|----------------------------------| +| Error Indication procedure | ERROR INDICATION | +| Write Replace Warning Indication procedure | WRITE REPLACE WARNING INDICATION | +| Stop Warning Indication procedure | STOP WARNING INDICATION | +| PWS Restart Indication | PWS RESTART INDICATION | +| PWS Failure Indication | PWS FAILURE INDICATION | + +### 4.3.3 Write Replace Warning Procedure + +#### 4.3.3.1 General + +The purpose of Write-Replace Warning procedure is to start, overwrite the broadcasting of warning message, as defined in 3GPP TS 23.041 [14]. + +#### 4.3.3.2 Successful Operation + +![Sequence diagram for Successful Operation of Write-Replace Warning procedure. The diagram shows two lifelines: MME and CBC. The CBC sends a WRITE-REPLACE WARNING REQUEST message to the MME. The MME then sends a WRITE-REPLACE WARNING RESPONSE message back to the CBC. Both lifelines have a solid black bar at the bottom, indicating the end of the sequence.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +``` +sequenceDiagram + participant CBC + participant MME + Note left of MME: + Note right of CBC: + CBC->>MME: WRITE-REPLACE WARNING REQUEST + MME-->>CBC: WRITE-REPLACE WARNING RESPONSE +``` + +Sequence diagram for Successful Operation of Write-Replace Warning procedure. The diagram shows two lifelines: MME and CBC. The CBC sends a WRITE-REPLACE WARNING REQUEST message to the MME. The MME then sends a WRITE-REPLACE WARNING RESPONSE message back to the CBC. Both lifelines have a solid black bar at the bottom, indicating the end of the sequence. + +**Figure 4.3.3.2-1: Write-Replace Warning procedure. Successful operation.** + +The CBC initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the MME. + +Upon reception of WRITE-REPLACE WARNING REQUEST message, the MME shall forward the message towards the eNBs which belong to the tracking area indicated in List of TAIs IE, if this list is present. + +If a Global eNB ID IE is present in the WRITE-REPLACE WARNING REQUEST message, the MME shall forward the message only towards the eNB identified by the Global eNB ID if this IE is supported by the MME. If the Global eNB ID IE is not supported by the MME, the MME shall forward the WRITE-REPLACE WARNING REQUEST message using the List of TAIs IE, if this list is present, otherwise the MME shall send the message towards all connected (H)eNBs. An MME and a CBC which support the PWS Restoration procedures as specified in 3GPP TS 23.007 [16] clause 15A.1 shall support the Global eNB ID IE. + +If neither the List of TAIs IE, nor the Global eNB ID IE (if this is supported) are present in WRITE-REPLACE WARNING REQUEST message, the MME shall forward the message towards all connected eNBs. + +The MME shall return a WRITE-REPLACE WARNING RESPONSE to the CBC immediately after the reception of the WRITE-REPLACE WARNING REQUEST message without waiting responses from eNBs. + +The MME shall set the cause IE to 'Message accepted' in the WRITE-REPLACE WARNING RESPONSE message. + +#### 4.3.3.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Write-Replace Warning procedure. The diagram shows two lifelines: MME and CBC. The CBC sends a WRITE-REPLACE WARNING REQUEST message to the MME. The MME then sends a WRITE-REPLACE WARNING RESPONSE message back to the CBC. Both lifelines have a solid black bar at the bottom, indicating the end of the sequence.](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +``` +sequenceDiagram + participant CBC + participant MME + Note left of MME: + Note right of CBC: + CBC->>MME: WRITE-REPLACE WARNING REQUEST + MME-->>CBC: WRITE-REPLACE WARNING RESPONSE +``` + +Sequence diagram for Unsuccessful Operation of Write-Replace Warning procedure. The diagram shows two lifelines: MME and CBC. The CBC sends a WRITE-REPLACE WARNING REQUEST message to the MME. The MME then sends a WRITE-REPLACE WARNING RESPONSE message back to the CBC. Both lifelines have a solid black bar at the bottom, indicating the end of the sequence. + +**Figure 4.3.3.3-1: Write-Replace Warning procedure. Unsuccessful operation.** + +The CBC initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the MME. + +If MME cannot process the received WRITE-REPLACE WARNING REQUEST message, the MME shall return a WRITE-REPLACE WARNING RESPONSE message towards the CBC and the MME shall not forward the message towards the eNBs belonged to the tracking area as indicated in List of TAIs IE. + +The MME shall indicate a reason of failure in the cause IE. + +NOTE: An Unsuccessful Operation is reported as a Successful Outcome in the Response message. See clause 3.1. + +### 4.3.3A Stop Warning Procedure + +#### 4.3.3A.1 General + +The purpose of Stop Warning Procedure is to stop the broadcasting of warning message. + +#### 4.3.3A.2 Successful Operation + +![Sequence diagram for Stop Warning Procedure, Successful Operation. The diagram shows two lifelines: MME and CBC. The CBC sends a STOP WARNING REQUEST message to the MME. The MME then sends a STOP WARNING RESPONSE message back to the CBC.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +``` +sequenceDiagram + participant CBC + participant MME + Note left of MME: + Note right of CBC: + CBC->>MME: STOP WARNING REQUEST + MME-->>CBC: STOP WARNING RESPONSE +``` + +Sequence diagram for Stop Warning Procedure, Successful Operation. The diagram shows two lifelines: MME and CBC. The CBC sends a STOP WARNING REQUEST message to the MME. The MME then sends a STOP WARNING RESPONSE message back to the CBC. + +Figure 4.3.3A.2-1: Stop Warning Procedure, Successful Operation. + +The CBC initiates the Stop Warning Procedure by sending a STOP WARNING REQUEST message to the MME. + +Upon reception of STOP WARNING REQUEST message, the MME shall forward the message towards the eNBs belonged to the tracking area as indicated in List of TAIs IE. + +If none of List of TAIs IE is present in STOP WARNING REQUEST message, the MME shall forward the message towards all connected eNBs. + +The MME shall return a STOP WARNING RESPONSE to the CBC immediately after the reception of the STOP WARNING REQUEST message without waiting responses from eNBs. + +The MME shall set the cause IE to 'Message accepted' in the STOP WARNING RESPONSE message. + +#### 4.3.3A.3 Unsuccessful Operation + +![Sequence diagram for Stop Warning procedure, Unsuccessful operation. The diagram shows two lifelines: MME and CBC. The CBC sends a STOP WARNING REQUEST message to the MME. The MME then sends a STOP WARNING RESPONSE message back to the CBC.](e58a867750e4ae01604318506b79df7a_img.jpg) + +``` +sequenceDiagram + participant CBC + participant MME + Note left of MME: + Note right of CBC: + CBC->>MME: STOP WARNING REQUEST + MME-->>CBC: STOP WARNING RESPONSE +``` + +Sequence diagram for Stop Warning procedure, Unsuccessful operation. The diagram shows two lifelines: MME and CBC. The CBC sends a STOP WARNING REQUEST message to the MME. The MME then sends a STOP WARNING RESPONSE message back to the CBC. + +Figure 4.3.3A.3-1: Stop Warning procedure, Unsuccessful operation. + +The CBC initiates the Stop Warning Procedure by sending a STOP WARNING REQUEST message to the MME. + +If MME cannot process the received STOP WARNING REQUEST message, the MME shall return a STOP WARNING RESPONSE message towards the CBC and the MME shall not forward the message towards the eNBs belonged to the tracking area as indicated in List of TAIs IE. + +The MME shall indicate a reason of failure in the cause IE. + +NOTE: An Unsuccessful Operation is reported as a Successful Outcome in the Response message. See clause 3.1. + +### 4.3.3B Error Indication + +#### 4.3.3B.1 General + +The Error Indication procedure is initiated by a node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. + +#### 4.3.3B.2 Successful Operation + +![Sequence diagram showing the Error Indication procedure initiated by the CBC. The CBC sends an ERROR INDICATION message to the MME.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` +sequenceDiagram + participant MME + participant CBC + Note left of MME: + Note right of CBC: + CBC->>MME: ERROR INDICATION + Note left of MME: + Note right of CBC: +``` + +Sequence diagram showing the Error Indication procedure initiated by the CBC. The CBC sends an ERROR INDICATION message to the MME. + +Figure 4.3.3B.2-1: Error Indication procedure, CBC originated. Successful operation. + +![Sequence diagram showing the Error Indication procedure initiated by the MME. The MME sends an ERROR INDICATION message to the CBC.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` +sequenceDiagram + participant MME + participant CBC + Note left of MME: + Note right of CBC: + MME->>CBC: ERROR INDICATION + Note left of MME: + Note right of CBC: +``` + +Sequence diagram showing the Error Indication procedure initiated by the MME. The MME sends an ERROR INDICATION message to the CBC. + +Figure 4.3.3B.2-2: Error Indication procedure, MME originated. Successful operation. + +When the conditions defined in clause 4.5 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* as indicated in clause 4.5. + +#### 4.3.3B.3 Abnormal Conditions + +Not applicable. + +### 4.3.3C Write Replace Warning Indication + +#### 4.3.3C.1 General + +If supported by the MME, the Write-Replace-Warning-Indication message(s) shall be sent by the MME to report to the CBC with the Broadcast Scheduled Area List IE if the Send Write-Replace-Warning-Indication parameter was present in the corresponding Write-Replace-Warning-Request. The Broadcast Scheduled Area List IE shall contain the Broadcast Completed Area List the MME has received from the eNodeB(s) (see 3GPP TS 36.413 [7]). + +#### 4.3.3C.2 Successful Operation + +![Sequence diagram for Figure 4.3.3C.2-1: Write Replace Warning Indication procedure, MME originated. Successful operation. The diagram shows two vertical lifelines: MME on the left and CBC on the right. A horizontal arrow points from the MME lifeline to the CBC lifeline, labeled 'WRITE REPLACE WARNING INDICATION'. Both lifelines end with a thick horizontal bar at the bottom.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Sequence diagram for Figure 4.3.3C.2-1: Write Replace Warning Indication procedure, MME originated. Successful operation. The diagram shows two vertical lifelines: MME on the left and CBC on the right. A horizontal arrow points from the MME lifeline to the CBC lifeline, labeled 'WRITE REPLACE WARNING INDICATION'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 4.3.3C.2-1: Write Replace Warning Indication procedure, MME originated. Successful operation.** + +The MME initiates the Write Replace Warning Indication procedure by sending a WRITE REPLACE WARNING INDICATION message(s) to the CBC after it has previously received a Broadcast Completed Area List from eNodeB(s) in a WRITE-REPLACE WARNING MESSAGE (see 3GPP TS 36.413 [7]). The MME may aggregate Broadcast Completed Area Lists it receives from the eNodeBs. + +#### 4.3.3C.3 Abnormal Conditions + +Not applicable. + +### 4.3.3D Stop Warning Indication + +#### 4.3.3D.1 General + +If supported by the MME, the Stop Warning Indication message(s) shall be sent by the MME to report to the CBC with the Broadcast Cancelled Area List IE if the Send Stop Warning Indication parameter was present in the corresponding Stop Warning Request. The Broadcast Cancelled Area List IE shall contain the Broadcast Cancelled Area List the MME has received from the eNodeB(s) (see 3GPP TS 36.413 [7]). + +#### 4.3.3D.2 Successful Operation + +![Sequence diagram for Figure 4.3.3D.2-1: Stop Warning Indication procedure, MME originated. Successful operation. The diagram shows two vertical lifelines: MME on the left and CBC on the right. A horizontal arrow points from the MME lifeline to the CBC lifeline, labeled 'STOP WARNING INDICATION'. Both lifelines end with a thick horizontal bar at the bottom.](5dfc130b129ace4df375839020a5700d_img.jpg) + +Sequence diagram for Figure 4.3.3D.2-1: Stop Warning Indication procedure, MME originated. Successful operation. The diagram shows two vertical lifelines: MME on the left and CBC on the right. A horizontal arrow points from the MME lifeline to the CBC lifeline, labeled 'STOP WARNING INDICATION'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 4.3.3D.2-1: Stop Warning Indication procedure, MME originated. Successful operation.** + +The MME initiates the Stop Warning Indication procedure by sending a STOP WARNING INDICATION message to the CBC after it has previously received a Broadcast Cancelled Area List from an eNodeB. The MME may aggregate Broadcast Cancelled Area Lists it receives from the eNodeBs. + +#### 4.3.3D.3 Abnormal Conditions + +Not applicable. + +### 4.3.3E PWS Restart Indication + +#### 4.3.3E.1 General + +The PWS Restart Indication is sent by the MME to the CBC upon receipt of a PWS Restart Indication from an (H)eNB, to indicate that the PWS service is restarted in one or more or all cells served by an (H)eNB, i.e. the service has become operational and no warning message data is available for these cell(s). The CBC shall reload the cells if required. + +#### 4.3.3E.2 Successful Operation + +![Sequence diagram showing the PWS Restart Indication procedure. The MME sends a PWS RESTART INDICATION message to the CBC.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant MME + participant CBC + Note left of MME: + MME->>CBC: PWS RESTART INDICATION + Note right of CBC: + +``` + +Sequence diagram showing the PWS Restart Indication procedure. The MME sends a PWS RESTART INDICATION message to the CBC. + +**Figure 4.3.3E.2-1: PWS Restart Indication, Successful Operation.** + +The MME initiates the PWS Restart Indication procedure by sending a PWS RESTART INDICATION message to the CBC upon receiving a PWS Restart Indication message from an (H)eNB (see 3GPP TS 36.413 [7]). + +The MME shall copy the following parameters from the PWS Restart Indication received from the (H)eNB into the corresponding parameters in the PWS-RESTART-INDICATION towards the CBC: + +- Global eNB ID of the (H)eNB; +- E-CGI List for Restart into the Restarted-Cell-List; +- TAI List for Restart into List of TAIs for Restart; +- Emergency Area ID List for Restart (if received from the (H)eNB, i.e. if the restarted cell(s) are configured with Emergency Area ID(s)) into List of EAIs for Restart. + +Upon receipt of a PWS Restart Indication message, the CBC shall consider that the PWS service is restarted in the reported cell(s), i.e. the service is operational and no warning messages are being broadcast in these cell(s). The CBC shall then reload the warning message data to the (H)eNB for these cells, if any. + +The CBC shall consider a PWS Restart Indication message received shortly after a preceding one for the same cell identity as a duplicate restart indication for that cell which it shall ignore. + +NOTE: The CBC can receive the same PWS Restart Indication message via two MMEs of the MME pool for redundancy reasons (see clause 15A.1 of 3GPP TS 23.007 [16]), or via two AMFs of the AMF Region for redundancy reasons (see clause 7.3 of 3GPP TS 23.527 [18]). + +The CBC shall reload the warning message data (with the same Message Identifier and Serial Number) to the (H)eNB by initiating Write Replace Warning procedure(s) as specified in clause 4.3.3.2 with the following additions: + +- the CBC should set the Warning Area List IE in the Write-Replace Warning Request message to the identities of the cell(s) received in the Restarted-Cell-List which are relevant to the warning message data being reloaded; +- the CBC shall copy the Global eNB ID into the Write-Replace Warning Request message; and +- the CBC may update the Number of Broadcast Requested, if necessary. + +#### 4.3.3E.3 Abnormal Conditions + +Not applicable. + +### 4.3.3F PWS Failure Indication + +#### 4.3.3F.1 General + +The PWS Failure Indication is sent by the MME to the CBC upon receipt of a PWS Failure Indication from an (H)eNB, to indicate that ongoing PWS operation in one or more or all cells served by an (H)eNB has failed. + +#### 4.3.3F.2 Successful Operation + +![Sequence diagram showing the PWS Failure Indication procedure. The MME sends a PWS FAILURE INDICATION message to the CBC.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant MME + participant CBC + Note left of MME: + MME->>CBC: PWS FAILURE INDICATION + Note right of CBC: + +``` + +Sequence diagram showing the PWS Failure Indication procedure. The MME sends a PWS FAILURE INDICATION message to the CBC. + +**Figure 4.3.3F.2-1: PWS Failure Indication, Successful Operation.** + +The MME initiates the PWS Failure Indication procedure by sending a PWS FAILURE INDICATION message to the CBC upon receiving a PWS Failure Indication message from an (H)eNB (see 3GPP TS 36.413 [7]). + +The MME shall copy the following parameters from the PWS Failure Indication received from the (H)eNB into the corresponding parameters in the PWS-FAILURE-INDICATION towards the CBC: + +- Global eNB ID of the (H)eNB; +- E-CGI List Failed for PWS into the Failed-Cell-List; +- PWS Failed E-CGI List into Failed-Cell-List. + +#### 4.3.3F.3 Abnormal Conditions + +Not applicable. + +### 4.3.4 Message functional definition and content + +#### 4.3.4.1 Message contents + +##### 4.3.4.1.1 Presence + +All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 4.3.4.1.1-1. + +**Table 4.3.4.1.1-1: Meaning of abbreviations used in SBc-AP messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------| +| M | IEs marked as Mandatory (M) shall always be included in the message. | +| O | IEs marked as Optional (O) may or may not be included in the message. | +| C | IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. | + +##### 4.3.4.1.2 Criticality + +Each Information Element or Group of Information Elements may have criticality information applied to it. Following cases are possible: + +**Table 4.3.4.1.2-1: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +##### 4.3.4.1.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +##### 4.3.4.1.4 Assigned Criticality + +This column provides the actual criticality information as defined in clause 4.5.3.2, if applicable. + +#### 4.3.4.2 Warning Message Transmission Messages + +##### 4.3.4.2.1 WRITE-REPLACE WARNING REQUEST + +This message is sent by the CBC to request start or overwrite of a warning message broadcast. + +If the message is sent to the MME, then: + +- the List of TAIs IE, the Warning Area List IE and the Global eNB ID IE may be used; and +- the List of 5GS TAIs IE, the Warning Area List 5GS IE, the Global RAN Node ID IE and the RAT Selector 5GS IE shall not be used. + +If the message is sent to the PWS-IWF, then: + +- the List of 5GS TAIs IE, the Warning Area List 5GS IE, the Global RAN Node ID IE may be used; +- the List of TAIs IE, the Warning Area List IE and the Global eNB ID IE shall not be used; and the message shall address a Warning Area in E-UTRA or in NR, but not both simultaneously; the RAT Selector 5GS IE shall be used if the message is for the NR RAT. + +Direction: CBC → MME, PWS-IWF + +**Table 4.3.4.2.1-1: WRITE-REPLACE WARNING REQUEST message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-----------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| List of TAIs | O | | | | YES | reject | +| >TAI List Item | | 1 to | | | | | +| >>TAI | M | | [7] | | | | +| Warning Area List | O | | [7] | | YES | ignore | +| Repetition Period | M | | [7] | | YES | reject | +| Extended Repetition Period | O | | [7] | | YES | reject | +| Number of Broadcast Requested | M | | [7] | | YES | reject | +| Warning Type | O | | [7] | | YES | ignore | +| Warning Security Information | O | | [7] | | YES | ignore | +| Data Coding Scheme | O | | [7] | | YES | ignore | +| Warning Message Contents | O | | [7] | | YES | ignore | +| OMC ID | O | | 4.3.4.3.4 | | YES | ignore | +| Concurrent Warning Message Indicator | O | | [7] | | YES | reject | +| Send Write-Replace-Warning-Indication | O | | 4.3.4.3.5 | | YES | ignore | +| Global eNB ID | O | | [7] | | YES | ignore | +| List of 5GS TAIs | O | | | | YES | ignore | +| >5GS TAI List Item | | 1 to | | | | | +| >>5GS TAI | M | | [17] | | | | +| Warning Area List 5GS | O | | [17] | | YES | ignore | +| Global RAN Node ID | O | | [17] | | YES | ignore | +| RAT Selector 5GS | C | | 4.3.4.3.10 | | YES | ignore | +| Warning Area Coordinates | O | | [7] | | YES | ignore | + +**Table 4.3.4.2.1-2: RANGE explanation** + +| Range bound | Explanation | +|----------------|--------------------------------------------------------------------------------------| +| maxnoofTAI | Maximum no. of TAI subject for warning message broadcast in E-UTRAN. Value is 65535. | +| Maxnoof5GSTAIs | Maximum no. of TAI subject for warning message broadcast in 5GS. | + +Editor's Note: the Maxnoof5GSTAIs value is FFS in RAN3 (assumption for ASN1 is 65535). + +##### 4.3.4.2.2 WRITE-REPLACE WARNING RESPONSE + +This message is sent by the MME or PWS-IWF to acknowledge the CBC on the start or overwrite request of a warning message. + +If the message is received from an MME then the Unknown Tracking Area IE may be present. If the message is received from a PWS-IWF then the Unknown 5GS Tracking Area List may be present. + +Direction: MME, PWS-IWF → CBC + +**Table 4.3.4.2.2-1: WRITE-REPLACE WARNING RESPONSE message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| Cause | M | | 4.3.4.3.2 | | YES | reject | +| Criticality Diagnostics | O | | 4.3.4.3.3 | | YES | ignore | +| Unknown Tracking Area List | O | | 4.3.4.3.6 | | YES | ignore | +| Unknown 5GS Tracking Area List | O | | 4.3.4.3.11 | | YES | ignore | + +##### 4.3.4.2.3 STOP WARNING REQUEST + +This message is sent by the CBC to stop a warning message broadcast. + +If the message is sent to an MME, then: + +- the List of TAIs IE and the Warning Area List IE may be used; and +- the List of 5GS TAIs IE, the Warning Area List 5GS IE and the RAT Selector 5GS IE shall not be used. + +If the message is sent to the PWS-IWF, then: + +- the List of 5GS TAIs IE, the Warning Area List 5GS IE may be used; +- the List of TAIs IE and the Warning Area List IE shall not be used; and +- the message shall address a Warning Area in E-UTRA or in NR, but not both simultaneously; the RAT Selector 5GS IE shall be used if the message is for the NR RAT. + +Direction: CBC → MME, PWS-IWF + +**Table 4.3.4.2.3-1: STOP WARNING REQUEST message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------|----------|------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| List of TAIs | O | | | | YES | reject | +| >TAI List Item | | 1 to | | | | | +| >>TAI | M | | [7] | | | | +| Warning Area List | O | | [7] | | YES | ignore | +| OMC ID | O | | 4.3.4.3.4 | | YES | ignore | +| Send Stop Warning Indication | O | | 4.3.4.3.7 | | YES | ignore | +| Stop-All Indicator | O | | 4.3.4.3.8 | | YES | reject | +| List of 5GS TAIs | O | | | | YES | ignore | +| >5GS TAI List Item | | 1 to | | | | | +| >>5GS TAI | M | | [17] | | | | +| Warning Area List 5GS | O | | [17] | | YES | ignore | +| RAT Selector 5GS | C | | 4.3.4.3.10 | | YES | ignore | + +**Table 4.3.4.2.3-2: RANGE explanation** + +| Range bound | Explanation | +|----------------|--------------------------------------------------------------------------------------| +| maxnoofTAI | Maximum no. of TAI subject for warning message broadcast in E-UTRAN. Value is 65535. | +| Maxnoof5GSTAls | Maximum no. of TAI subject for warning message broadcast in 5GS. | + +Editor's Note: the Maxnoof5GSTAls value is FFS in RAN3 (assumption for ASN1 is 65535). + +##### 4.3.4.2.4 STOP WARNING RESPONSE + +This message is sent by the MME or PWS-IWF to acknowledge the CBC on the stop request of a warning message. + +If the message is received from an MME then the Unknown Tracking Area IE may be present, but if the message is received from a PWS-IWF then the Unknown 5GS Tracking Area List may be present. Direction: MME, PWS-IWF → CBC + +**Table 4.3.4.2.2-1: STOP WARNING RESPONSE message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | reject | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| Cause | M | | 4.3.4.3.2 | | YES | reject | +| Criticality Diagnostics | O | | 4.3.4.3.3 | | YES | ignore | +| Unknown Tracking Area List | O | | 4.3.4.3.6 | | YES | ignore | +| Unknown 5GS Tracking Area List | O | | 4.3.4.3.11 | | YES | ignore | + +##### 4.3.4.2.5 WRITE REPLACE WARNING INDICATION + +This message is sent by the MME to report to the CBC the Broadcast Scheduled Area List(s) the MME has received from the eNodeB(s) as Broadcast Completed Area List in a WRITE-REPLACE WARNING RESPONSE [7]. Multiple responses from eNodeBs may be combined in a Broadcast Scheduled Area List. + +The Broadcast Scheduled Area List IE is only included in the WRITE-REPLACE WARNING INDICATION when the broadcast is successful in at least one cell within the eNodeBs. + +If the message is received from an MME then the Broadcast Scheduled Area List IE may be present, but if the message is received from a PWS-IWF then the Broadcast Scheduled Area List 5GS IE may be present. + +Direction: MME, PWS-IWF → CBC + +**Table 4.3.4.2.5-1: WRITE REPLACE WARNING INDICATION message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | ignore | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| Broadcast Scheduled Area List | O | | [7] | | YES | reject | +| Broadcast Scheduled Area List 5GS | O | | 4.3.4.3.12 | | YES | ignore | + +##### 4.3.4.2.6 STOP WARNING INDICATION + +This message is sent by the MME to report to the CBC the Broadcast Cancelled Area List the MME has received from the eNodeB in a KILL RESPONSE [7]. If the MME has received a KILL RESPONSE without a Broadcast Cancelled Area List IE, then the eNodeB ID shall be included in the Broadcast Empty Area List instead. Multiple responses from eNodeBs may be aggregated into a combined Broadcast Cancelled Area List. + +NOTE: The CBC is able to derive the list of cell IDs that are served by the eNodeB, because the eNodeB ID is contained in the cell ID. The Broadcast Cancelled Area List IE is only included in the STOP WARNING INDICATION when the broadcast is successfully stopped in at least one cell within the eNodeBs. + +The Broadcast Empty Area List IE shall be included in the STOP-WARNING-INDICATION when the MME has received at least one KILL RESPONSE without Broadcast Cancelled Area List IE. + +If the message is received from an MME then the Broadcast Cancelled Area List IE may be present, but if the message is received from a PWS-IWF then the Broadcast Cancelled Area List 5GS IE may be present. + +Direction: MME, PWS-IWF → CBC + +**Table 4.3.4.2.6-1: STOP WARNING INDICATION message contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | ignore | +| Message Identifier | M | | [7] | | YES | reject | +| Serial Number | M | | [7] | | YES | reject | +| Broadcast Cancelled Area List | O | | [7] | | YES | reject | +| Broadcast Empty Area List | O | | 4.3.4.3.9 | | YES | ignore | +| Broadcast Cancelled Area List 5GS | O | | 4.3.4.3.13 | | YES | ignore | +| Broadcast Empty Area List 5GS | O | | 4.3.4.3.14 | | YES | ignore | + +##### 4.3.4.2.7 PWS RESTART INDICATION + +This Indication is sent by the MME, or the PWS-IWF to report to the CBC the List of cells that have become available for PWS and have no warning message data. + +If the indication is received from a PWS-IWF and the restarted cells are NR cells then: + +- the Restarted-Cell-List IE, the Global eNB ID IE and List of TAIs for Restart IE shall be populated with a dummy value (all zeros); and +- the Restarted-Cell-List-NR IE, Global gNB ID IE and List of 5GS TAIs for Restart IE shall be populated. + +If the indication is received from a PWS-IWF and the restarted cells are E-UTRA cells then: + +- the Restarted-Cell-List-NR IE and the Global gNB ID IE shall not be present; +- the List of TAIs for Restart IE shall be populated with a dummy value (all zeros); and +- the List of 5GS TAI for Restart IE shall be populated. + +Direction: MME, PWS-IWF → CBC + +Table 4.3.4.2.7-1: PWS RESTART INDICATION message contents + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|---------------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | ignore | +| Restarted-Cell-List | M | | [7] | | YES | reject | +| >Restarted Cell List Item | | 1 to | | | | | +| >>E-CGI | M | | [7] | | | | +| Global eNB ID | M | | [7] | | YES | reject | +| List of TAIs for Restart | M | | | | YES | reject | +| >TAI for Restart List Item | | 1 to | | | | | +| >>TAI | M | | [7] | | | | +| List of EAI for Restart | O | | | | YES | reject | +| >EAI for Restart List Item | | 1 to | | | | | +| >>Emergency Area ID | M | | [7] | | | | +| Restarted-Cell-List-NR | O | | | | YES | ignore | +| >Restarted Cell List NR Item | | 1 to | | | | | +| >>NR CGI | O | | [17] | | | | +| Global gNB ID | O | | [17] | | YES | ignore | +| List of 5GS TAI for Restart | O | | | | YES | ignore | +| >5GS TAI for Restart List Item | | 1 to | | | | | +| >>5GS TAI | O | | [17] | | | | + +Table 4.3.4.2.7-2: RANGE explanation + +| Range bound | Explanation | +|--------------------------|------------------------------------------------------------------------------------------| +| maxnoofRestartedCells | Maximum no. of restarted E-UTRA cells. Value is 256. | +| maxnoofRestartTAIs | Maximum no. of Tracking Area IDs configured in the restarted cells. Value is 2048. | +| maxnoofRestartEAIs | Maximum no. of Emergency Area ID configured in the restarted cells. Value is 256. | +| maxnoofCellsforRestartNR | Maximum no. of NR cells subject for reloading warning message broadcast. Value is 16384. | +| maxnoofTRestart5GSTAIs | Maximum no. of 5GS TAIs subject for reloading warning message broadcast. Value is 2048. | + +##### 4.3.4.2.8 PWS FAILURE INDICATION + +This Indication is sent by the MME or PWS-IWF to report to the CBC the List of cells that are no longer available for PWS. + +If the indication is received from a PWS-IWF and the failed cells are NR cells then the Failed-Cell-List IE and the Global eNB ID IE shall be populated with a dummy value (all zeros). + +Direction: MME, PWS-IWF → CBC + +Table 4.3.4.2.8-1: PWS FAILURE INDICATION message contents + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|---------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | ignore | +| Failed-Cell-List | M | | [7] | | YES | reject | +| >Failed Cell List Item | | 1 to | | | | | +| >>E-CGI | M | | [7] | | | | +| Global eNB ID | M | | [7] | | YES | reject | +| Failed Cell List NR | O | | | | YES | ignore | +| >Failed Cell List NR Item | | 1 to | | | | | +| >>NR CGI | O | | [17] | | | | +| Global gNB ID | O | | [17] | | YES | ignore | + +Table 4.3.4.2.8-2: RANGE explanation + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------| +| maxnoofFailedCells | Maximum number of failed cells. Value is 256. | +| maxnoofCellsingNB | Maximum no. of cells that can be served by a gNB. Value is 16384. | + +#### 4.3.4.2A Management Messages + +##### 4.3.4.2A.1 ERROR INDICATION + +This message is sent by both the MME and the CBC and is used to indicate that some error has been detected in the node. + +Direction : MME, PWS-IWF → CBC and CBC → MME, PWS-IWF + +Table 4.3.4.2A.1-1: ERROR INDICATION message contents + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 4.3.4.3.1 | | YES | ignore | +| Cause | O | | 4.3.4.3.2 | | YES | ignore | +| Criticality Diagnostics | O | | 4.3.4.3.3 | | YES | ignore | + +#### 4.3.4.3 Information element definition + +##### 4.3.4.3.1 Message Type + +The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages + +**Table 4.3.4.3.1-1: Message Type information element** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Message Type | | | | Assumed max no of messages is 256. | +| >Procedure Code | M | | (Write-Replace Warning, Stop Warning, Write-Replace Warning Indication, Stop Warning Indication, PWS Restart Indication, ...) | | +| >Type of Message | M | | CHOICE
(Initiating Message, Successful Outcome, Unsuccessful Outcome, PWS Failure Indication, ...) | | + +##### 4.3.4.3.2 Cause + +The purpose of the Cause IE is to indicate the reason for a particular event for the SBc-AP protocol. + +**Table 4.3.4.3.2-1: Cause information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Cause | M | | INTEGER (Message accepted, Parameter not recognised, Parameter value invalid, Valid message not identified, Tracking area not valid, Unrecognised message, Missing mandatory element, MME capacity exceeded, MME memory exceeded, Warning broadcast not supported, Warning broadcast not operational, Message reference already used, Unspecified error, Transfer syntax error, Semantic error, Message not compatible with receiver state, Abstract syntax error reject, Abstract syntax error ignore and notify, Abstract syntax error falsely constructed message, ...) | | + +##### 4.3.4.3.3 Criticality Diagnostics + +The Criticality Diagnostics IE is sent by the MME 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. + +**Table 4.3.4.3.3-1: Criticality Diagnostics information element** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-----------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error | +| Triggering Message | O | | ENUMERATED( initiating message, successful outcome, unsuccessful outcome, 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, ...) | | + +**Table 4.3.4.3.3-2: RANGE explanation** + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------------------------------------| +| maxnooferrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxnooferrors is 256. | + +##### 4.3.4.3.4 OMC ID + +The OMC ID IE indicates the identity of an Operation and Maintenance Centre to which Trace records shall be sent. + +**Table 4.3.4.3.4-1: OMC ID information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------------------------------------------------------------|-----------------------| +| OMC ID | O | | OCTET STRING (SIZE (1..20))
Octets are coded according to 3GPP TS 29.002 [11]. | | + +##### 4.3.4.3.5 Send Write-Replace-Warning-Indication + +The Send Write-Replace-Warning-Indication IE indicates to the MME that the MME shall send the WRITE-REPLACE WARNING INDICATION to the CBC for the warning message. + +**Table 4.3.4.3.5-1: Send Write-Replace-Warning-Indication information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-----------------------|-----------------------| +| Send Write-Replace-Warning-Indication | O | | ENUMERATED(true) | | + +##### 4.3.4.3.6 Unknown Tracking Area List + +The Unknown Tracking Area List IE identifies the Tracking Areas that are unknown to the MME and where the Request cannot be delivered. + +This IE shall only be included if the Cause IE indicates Message accepted, which means the MME will proceed with the request for Tracking Areas that are known to the MME. The Cause IE indicating Tracking area not valid is used when all Tracking Areas in the Request are invalid. + +**Table 4.3.4.3.5-1: Failure List information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------------------------------------------------|-----------------------| +| Unknown Tracking Area List | O | | The Unknown Tracking Area List is of type List of TAIs . | | + +##### 4.3.4.3.7 Send Stop Warning Indication + +The Send Stop Warning Indication IE indicates to the MME that the MME shall send the STOP WARNING INDICATION to the CBC for the warning message. + +**Table 4.3.4.3.7-1: Send Stop-Warning-Indication information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-----------------------|-----------------------| +| Send Stop Warning Indication | O | | ENUMERATED(true) | | + +##### 4.3.4.3.8 Stop-All Indicator + +The Stop-All Indicator IE indicates that the Message Identifier IE and the Serial Number IE do not refer to a specific message that needs to be stopped, but that all messages in the area are referred to and to force the cells in the area into their Warning Message Delivery initial state. + +**Table 4.3.4.3.8-1: Stop-All Indicator information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-----------------------| +| Stop-All Indicator | O | | ENUMERATED(true) | | + +##### 4.3.4.3.9 Broadcast Empty Area List + +The Broadcast Empty Area List IE contains the eNodeB IDs of the eNodeBs which have responded with a KILL RESPONSE message which did not contain a Broadcast Cancelled Area List IE [7]. + +**Table 4.3.4.3.9-1: Broadcast Empty Area List information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|---------------------------------------------------------------|-----------------------| +| Broadcast Empty Area List | O | | The Broadcast Empty Area List is a list of Global eNB IDs [7] | | + +##### 4.3.4.3.10 RAT Selector 5GS + +The RAT Selector 5GS IE shall be present in a WRITE-REPLACE WARNING REQUEST and a STOP WARNING REQUEST message sent to a PWS-IWF, to indicate to the AMF that the request shall be distributed to gNodeBs (i.e. NR RAT). If the IE is not present, the AMF shall distribute the request to ng-eNodeBs (i.e. E-UTRA RAT). + +**Table 4.3.4.3.10-1: RAT Selector 5GS contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| RAT Selector 5GS | O | | Enumerated(true) | | YES | ignore | + +##### 4.3.4.3.11 Unknown 5GS Tracking Area List + +The Unknown 5GS Tracking Area List IE identifies the Tracking Areas that are unknown to the AMF and where the Request cannot be delivered. + +This IE shall only be included if the Cause IE indicates Message accepted, which means the AMF will proceed with the request for Tracking Areas that are known to the AMF. The Cause IE indicating Tracking area not valid is used when all Tracking Areas in the Request are invalid. + +**Table 4.3.4.3.11-1: Failure List information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-----------------------|-----------------------|-----------------------| +| Unknown 5GS Tracking Area List | | | | | +| >Unknown 5GS TAI List Item | | 1 to | | | +| >>5GS TAI | M | | [17] | | + +**Table 4.3.4.3.11-2: RANGE explanation** + +| Range bound | Explanation | +|----------------|------------------------------------------------------------------| +| Maxnoof5GSTAIs | Maximum no. of TAI subject for warning message broadcast in 5GS. | + +*Editor's Note: the Maxnoof5GSTAIs value is FFS (assumption for ASN1 is 65535).* + +##### 4.3.4.3.12 Broadcast Scheduled Area List 5GS + +This IE is used to identify a Broadcast Scheduled Area List in 5GS. + +**Table 4.3.4.3.12-1: Broadcast Scheduled Area List 5GS contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Broadcast Completed Area List 5GS | M | | [17] | | YES | reject | + +The Broadcast Scheduled Area List 5GS shall contain the Broadcast Completed Area List IE as specified in clause 9.3.1.43 in 3GPP TS 38.413 [17]. + +##### 4.3.4.3.13 Broadcast Cancelled Area List 5GS + +This IE is used to identify a Broadcast Cancelled Area List in 5GS. + +**Table 4.3.4.3.13-1: Broadcast Cancelled Area List 5GS contents** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Broadcast Cancelled Area List 5GS | M | | [17] | | YES | reject | + +The Broadcast Cancelled Area List 5GS shall contain the Broadcast Cancelled Area List IE as specified in clause 9.3.1.44 in 3GPP TS 38.413 [17]. + +##### 4.3.4.3.14 Broadcast Empty Area List 5GS + +The Broadcast Empty Area List 5GS IE contains the RAN Node IDs of the RAN nodes which have responded with a PWS CANCEL RESPONSE message which did not contain a Broadcast Cancelled Area List IE. + +**Table 4.3.4.3.14-1: Broadcast Empty Area List 5GS information element** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------|----------|------------------------|-----------------------|-----------------------| +| Broadcast Empty Area List 5GS | | | | | +| >Broadcast Empty Area List 5GS List Item | | 1 to | | | +| >>RAN Node ID | M | | [17] | | + +**Table 4.3.4.3.14-2: RANGE explanation** + +| Range bound | Explanation | +|-----------------|---------------------------| +| MaxnoofRANNodes | Maximum no. of RAN Nodes. | + +*Editor's Note: the MaxnoofRANNodes value is FFS (assumption for ASN1 is 65535).* + +## 4.4 Message and information element abstract syntax + +### 4.4.1 General + +SBC-AP ASN.1 definition conforms with [8] and [9]. + +The ASN.1 definition specifies the structure and content of SBC-AP messages. SBC-AP 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 SBC-AP 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 SBC-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in clause 4.5.3.6. + +### 4.4.2 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. + +### 4.4.3 Elementary procedure definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +SBC-AP-PDU-Descriptions { + itu-t (0) identified-organization (4) etai (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM SBC-AP-CommonDataTypes + + Write-Replace-Warning-Request, + Write-Replace-Warning-Response, + Stop-Warning-Request, + Stop-Warning-Response, + Error-Indication, + Write-Replace-Warning-Indication, + Stop-Warning-Indication, + PWS-Restart-Indication, + PWS-Failure-Indication +FROM SBC-AP-PDU-Contents + + id-Write-Replace-Warning, + id-Stop-Warning, + id-Error-Indication, + id-Write-Replace-Warning-Indication, + id-Stop-Warning-Indication, + id-PWS-Restart-Indication, + id-PWS-Failure-Indication +FROM SBC-AP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +SBC-AP-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 +-- +-- ***** + +SBC-AP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}), + criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SBC-AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}), + criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SBC-AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode SBC-AP-ELEMENTARY-PROCEDURE.&procedureCode ({SBC-AP-ELEMENTARY-PROCEDURES}), + criticality SBC-AP-ELEMENTARY-PROCEDURE.&criticality ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value SBC-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({SBC-AP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +SBC-AP-ELEMENTARY-PROCEDURES SBC-AP-ELEMENTARY-PROCEDURE ::= { + SBC-AP-ELEMENTARY-PROCEDURES-CLASS-1 | + SBC-AP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +SBC-AP-ELEMENTARY-PROCEDURES-CLASS-1 SBC-AP-ELEMENTARY-PROCEDURE ::= { + write-Replace-Warning | + stop-Warning , + ... +} + +SBC-AP-ELEMENTARY-PROCEDURES-CLASS-2 SBC-AP-ELEMENTARY-PROCEDURE ::= { + error-Indication | + write-Replace-Warning-Indication | + stop-Warning-Indication | + pws-Restart-Indication | + pws-Failure-Indication, + ... +} + +write-Replace-Warning SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Write-Replace-Warning-Request + SUCCESSFUL OUTCOME Write-Replace-Warning-Response + + PROCEDURE CODE id-Write-Replace-Warning + CRITICALITY reject +} + +stop-Warning SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Stop-Warning-Request + SUCCESSFUL OUTCOME Stop-Warning-Response +} + +``` + +``` + + PROCEDURE CODE id-Stop-Warning + CRITICALITY reject + } + + error-Indication SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Error-Indication + PROCEDURE CODE id-Error-Indication + CRITICALITY ignore + } + + write-Replace-Warning-Indication SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Write-Replace-Warning-Indication + PROCEDURE CODE id-Write-Replace-Warning-Indication + CRITICALITY ignore + } + + stop-Warning-Indication SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Stop-Warning-Indication + PROCEDURE CODE id-Stop-Warning-Indication + CRITICALITY ignore + } + + pws-Restart-Indication SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWS-Restart-Indication + PROCEDURE CODE id-PWS-Restart-Indication + CRITICALITY ignore + } + + pws-Failure-Indication SBC-AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWS-Failure-Indication + PROCEDURE CODE id-PWS-Failure-Indication + CRITICALITY ignore + } + +END + +``` + +### 4.4.4 PDU definitions + +``` + +-- ***** +-- +-- PDU definitions for SBC-AP. +-- +-- ***** + +SBC-AP-PDU-Contents { + itu-t (0) identified-organization (4) ettsi (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + + Cause, + Concurrent-Warning-Message-Indicator, + Criticality-Diagnostics, + Data-Coding-Scheme, + Message-Identifier, + Serial-Number, + List-of-TAIs, + Warning-Area-List, + Omc-Id, + Repetition-Period, + Extended-Repetition-Period, + Number-of-Broadcasts-Requested, + Warning-Type, + Warning-Security-Information, + Warning-Message-Content, + Warning-Area-Coordinates, + Send-Write-Replace-Warning-Indication, + +``` + +``` + +Broadcast-Scheduled-Area-List, +Unknown-Tracking-Area-List, +Send-Stop-Warning-Indication, +Broadcast-Cancelled-Area-List, +Stop-All-Indicator, +Broadcast-Empty-Area-List, +Restarted-Cell-List, +Global-ENB-ID, +List-of-TAIs-Restart, +List-of-EAIs-Restart, +Failed-Cell-List, +List-of-5GS-TAIs, +Warning-Area-List-5GS, +Global-RAN-Node-ID, +Global-GNB-ID, +RAT-Selector-5GS, +Unknown-5GS-Tracking-Area-List, +Broadcast-Scheduled-Area-List-5GS, +Broadcast-Cancelled-Area-List-5GS, +Broadcast-Empty-Area-List-5GS, +Restarted-Cell-List-NR, +Failed-Cell-List-NR, +List-of-5GS-TAI-for-Restart + +``` + +FROM SBC-AP-IEs + +``` + +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +SBC-AP-PROTOCOL-EXTENSION, +SBC-AP-PROTOCOL-IES + +``` + +FROM SBC-AP-Containers + +``` + +id-Concurrent-Warning-Message-Indicator, +id-Criticality-Diagnostics, +id-Cause, +id-Data-Coding-Scheme, +id-List-of-TAIs, +id-Message-Identifier, +id-Serial-Number, +id-Number-of-Broadcasts-Requested, +id-Omc-Id, +id-Radio-Resource-Loading-List, +id-Recovery-Indication, +id-Repetition-Period, +id-Extended-Repetition-Period, +id-Warning-Area-List, +id-Warning-Message-Content, +id-Warning-Area-Coordinates, +id-Warning-Security-Information, +id-Warning-Type, +id-Send-Write-Replace-Warning-Indication, +id-Broadcast-Scheduled-Area-List, +id-Unknown-Tracking-Area-List, +id-Send-Stop-Warning-Indication, +id-Broadcast-Cancelled-Area-List, +id-Stop-All-Indicator, +id-Broadcast-Empty-Area-List, +id-Global-ENB-ID, +id-Restarted-Cell-List, +id-List-of-TAIs-Restart, +id-List-of-EAIs-Restart, +id-Failed-Cell-List, +id-List-of-5GS-TAIs, +id-Warning-Area-List-5GS, +id-Global-RAN-Node-ID, +id-Global-GNB-ID, +id-RAT-Selector-5GS, +id-Unknown-5GS-Tracking-Area-List, +id-Broadcast-Scheduled-Area-List-5GS, +id-Broadcast-Cancelled-Area-List-5GS, +id-Broadcast-Empty-Area-List-5GS, +id-Restarted-Cell-List-NR, +id-Failed-Cell-List-NR, +id-List-of-5GS-TAI-for-Restart + +``` + +FROM SBC-AP-Constants; + +-- \*\*\*\*\* + +``` + +-- +-- Write-Replace-Warning-Request +-- +-- ***** + +Write-Replace-Warning-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Warning-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Warning-Request-Extensions} } + OPTIONAL, + ... +} + +Write-Replace-Warning-Request-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-List-of-TAIs CRITICALITY reject TYPE List-of-TAIs PRESENCE optional } | + { ID id-Warning-Area-List CRITICALITY ignore TYPE Warning-Area-List PRESENCE optional } | + { ID id-Repetition-Period CRITICALITY reject TYPE Repetition-Period PRESENCE mandatory } | + { ID id-Extended-Repetition-Period CRITICALITY reject TYPE Extended-Repetition-Period PRESENCE + optional } | + + { ID id-Number-of-Broadcasts-Requested + CRITICALITY reject TYPE Number-of-Broadcasts-Requested PRESENCE mandatory } | + { ID id-Warning-Type CRITICALITY ignore TYPE Warning-Type PRESENCE optional } | + { ID id-Warning-Security-Information CRITICALITY ignore TYPE Warning-Security-Information + PRESENCE optional } | + { ID id-Data-Coding-Scheme CRITICALITY ignore TYPE Data-Coding-Scheme PRESENCE optional } | + { ID id-Warning-Message-Content + CRITICALITY ignore TYPE Warning-Message-Content PRESENCE optional } | + { ID id-Omc-Id CRITICALITY ignore TYPE Omc-Id PRESENCE optional } | + { ID id-Concurrent-Warning-Message-Indicator CRITICALITY reject TYPE Concurrent-Warning- + Message-Indicator PRESENCE optional } | + { ID id-Send-Write-Replace-Warning-Indication CRITICALITY ignore TYPE Send-Write-Replace- + Warning-Indication PRESENCE optional } | + { ID id-Global-ENB-ID CRITICALITY ignore TYPE Global-ENB-ID PRESENCE optional }, + ... / + {ID id-Warning-Area-Coordinates CRITICALITY ignore TYPE Warning-Area-Coordinates PRESENCE + optional} +} + +Write-Replace-Warning-Request-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-List-of-5GS-TAIs CRITICALITY ignore EXTENSION List-of-5GS-TAIs PRESENCE optional } | + { ID id-Warning-Area-List-5GS CRITICALITY ignore EXTENSION Warning-Area-List-5GS PRESENCE + optional } | + { ID id-Global-RAN-Node-ID CRITICALITY ignore EXTENSION Global-RAN-Node-ID PRESENCE + optional } | + { ID id-RAT-Selector-5GS CRITICALITY ignore EXTENSION RAT-Selector-5GS PRESENCE optional }, + ... +} + +-- ***** +-- +-- Write-Replace-Warning-Response +-- +-- ***** + +Write-Replace-Warning-Response ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Warning-Response-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Warning-Response-Extensions} } + OPTIONAL, + ... +} + +Write-Replace-Warning-Response-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory } | + { ID id-Criticality-Diagnostics CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE + optional } | + { ID id-Unknown-Tracking-Area-List CRITICALITY ignore TYPE List-of-TAIs PRESENCE optional }, + ... +} + +Write-Replace-Warning-Response-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-Unknown-5GS-Tracking-Area-List CRITICALITY ignore EXTENSION Unknown-5GS-Tracking-Area- + List PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Stop-Warning-Request +-- +-- ***** + +Stop-Warning-Request ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Stop-Warning-Request-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Stop-Warning-Request-Extensions} } OPTIONAL, + ... +} + +Stop-Warning-Request-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-List-of-TAIs CRITICALITY reject TYPE List-of-TAIs PRESENCE optional } | + { ID id-Warning-Area-List CRITICALITY ignore TYPE Warning-Area-List PRESENCE optional } | + { ID id-Omc-Id CRITICALITY ignore TYPE Omc-Id PRESENCE optional } | + { ID id-Send-Stop-Warning-Indication CRITICALITY ignore TYPE Send-Stop-Warning-Indication + PRESENCE optional } | + { ID id-Stop-All-Indicator CRITICALITY reject TYPE Stop-All-Indicator PRESENCE optional }, + ... +} + +Stop-Warning-Request-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-List-of-5GS-TAIs CRITICALITY ignore EXTENSION List-of-5GS-TAIs PRESENCE optional } | + { ID id-Warning-Area-List-5GS CRITICALITY ignore EXTENSION Warning-Area-List-5GS PRESENCE + optional } | + { ID id-RAT-Selector-5GS CRITICALITY ignore EXTENSION RAT-Selector-5GS PRESENCE + optional }, + ... +} + +-- ***** +-- +-- Stop-Warning-Response +-- +-- ***** + +Stop-Warning-Response ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Stop-Warning-Response-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Stop-Warning-Response-Extensions} } OPTIONAL, + ... +} + +Stop-Warning-Response-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory } | + { ID id-Criticality-Diagnostics CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE + optional } | + { ID id-Unknown-Tracking-Area-List CRITICALITY ignore TYPE List-of-TAIs PRESENCE optional }, + ... +} + +Stop-Warning-Response-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-Unknown-5GS-Tracking-Area-List CRITICALITY ignore EXTENSION Unknown-5GS-Tracking-Area- + List PRESENCE optional }, + ... +} + +-- ***** +-- +-- Write-Replace-Warning-Indication +-- +-- ***** + +Write-Replace-Warning-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Write-Replace-Warning-Indication-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Write-Replace-Warning-Indication-Extensions} } + OPTIONAL, + ... +} + +Write-Replace-Warning-Indication-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + +``` + +``` + + { ID id-Broadcast-Scheduled-Area-List CRITICALITY reject TYPE Broadcast-Scheduled-Area-List + PRESENCE optional }, + ... + } + + Write-Replace-Warning-Indication-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-Broadcast-Scheduled-Area-List-5GS CRITICALITY ignore EXTENSION Broadcast-Scheduled- + Area-List-5GS PRESENCE optional }, + ... + } + + -- ***** + -- + -- Stop-Warning-Indication + -- + -- ***** + + Stop-Warning-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {Stop-Warning-Indication-IEs} }, + protocolExtensions ProtocolExtensionContainer { {Stop-Warning-Indication-Extensions} } OPTIONAL, + ... + } + + Stop-Warning-Indication-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Message-Identifier CRITICALITY reject TYPE Message-Identifier PRESENCE mandatory } | + { ID id-Serial-Number CRITICALITY reject TYPE Serial-Number PRESENCE mandatory } | + { ID id-Broadcast-Cancelled-Area-List CRITICALITY reject TYPE Broadcast-Cancelled-Area-List + PRESENCE optional } | + { ID id-Broadcast-Empty-Area-List CRITICALITY ignore TYPE Broadcast-Empty-Area-List PRESENCE + optional }, + ... + } + + Stop-Warning-Indication-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-Broadcast-Cancelled-Area-List-5GS CRITICALITY ignore EXTENSION Broadcast-Cancelled- + Area-List-5GS PRESENCE optional } | + { ID id-Broadcast-Empty-Area-List-5GS CRITICALITY ignore EXTENSION Broadcast-Empty-Area-List- + 5GS PRESENCE optional }, + ... + } + + -- ***** + -- + -- PWS-Restart-Indication + -- + -- ***** + + PWS-Restart-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PWS-Restart-Indication-IEs} }, + protocolExtensions ProtocolExtensionContainer { {PWS-Restart-Indication-Extensions} } OPTIONAL, + ... + } + + PWS-Restart-Indication-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Restarted-Cell-List CRITICALITY reject TYPE Restarted-Cell-List PRESENCE mandatory + } | + { ID id-Global-ENB-ID CRITICALITY reject TYPE Global-ENB-ID PRESENCE mandatory } | + { ID id-List-of-TAIs-Restart CRITICALITY reject TYPE List-of-TAIs-Restart PRESENCE + mandatory } | + { ID id-List-of-EAIs-Restart CRITICALITY reject TYPE List-of-EAIs-Restart PRESENCE + optional }, + ... + } + + PWS-Restart-Indication-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-Restarted-Cell-List-NR CRITICALITY ignore EXTENSION Restarted-Cell-List-NR PRESENCE + optional } | + { ID id-List-of-5GS-TAI-for-Restart CRITICALITY ignore EXTENSION List-of-5GS-TAI-for-Restart + PRESENCE optional } | + { ID id-Global-GNB-ID CRITICALITY ignore EXTENSION Global-GNB-ID PRESENCE optional }, + ... + } + + -- ***** + -- + -- PWS-Failure-Indication + +``` + +``` + +-- +-- ****************************************************************************** + +PWS-Failure-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PWS-Failure-Indication-IEs} }, + protocolExtensions ProtocolExtensionContainer { {PWS-Failure-Indication-Extensions} } OPTIONAL, + ... +} + +PWS-Failure-Indication-IEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Failed-Cell-List CRITICALITY reject TYPE Failed-Cell-List PRESENCE mandatory } | + { ID id-Global-ENB-ID CRITICALITY reject TYPE Global-ENB-ID PRESENCE mandatory }, + ... +} + +PWS-Failure-Indication-Extensions SBC-AP-PROTOCOL-EXTENSION ::= { + { ID id-Failed-Cell-List-NR CRITICALITY ignore EXTENSION Failed-Cell-List-NR PRESENCE optional } | + { ID id-Global-GNB-ID CRITICALITY ignore EXTENSION Global-GNB-ID PRESENCE optional }, + ... +} + +-- ****************************************************************************** +-- +-- ERROR INDICATION ELEMENTARY PROCEDURE +-- +-- ****************************************************************************** + +-- ****************************************************************************** +-- +-- Error Indication +-- +-- ****************************************************************************** + +Error-Indication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ErrorIndicationIEs} }, + ... +} + +ErrorIndicationIEs SBC-AP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } | + { ID id-Criticality-Diagnostics CRITICALITY ignore TYPE Criticality-Diagnostics PRESENCE optional }, + ... +} + +END + +``` + +### 4.4.5 Information element definitions + +``` + +-- ****************************************************************************** +-- +-- Information Element Definitions +-- +-- ****************************************************************************** + +SBC-AP-IEs { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-IEs (2)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + maxNrOfErrors, + maxNrOfTAIs, + maxnoofTAIforWarning, + maxnoofCellID, + maxnoofEmergencyAreaID, + + id-TypeOfError, + maxnoofCellinEAI, + maxnoofCellinTAI, + +``` + +``` + +maxnoofeNBIds, +maxnoofRestartTAIs, +maxnoofRestartEAIs, +maxnoofRestartedCells, +maxnoofFailedCells, +maxnoof5GSTAIs, +maxnoofCellsingNB, +maxnoofCellsIn5GS, +maxnoofCellsforRestartNR, +maxnoofRANNodes, +maxnoofRestart5GSTAIs, +maxnoofCellsIn5GSTAI + +FROM SBC-AP-Constants + + Criticality, + ProcedureCode, + TriggeringMessage, + ProtocolIE-ID +FROM SBC-AP-CommonDataTypes + + ProtocolExtensionContainer{}, + + SBC-AP-PROTOCOL-EXTENSION +FROM SBC-AP-Containers; + +-- A + +-- B + +Broadcast-Scheduled-Area-List ::= SEQUENCE { + cellId-Broadcast-List CellId-Broadcast-List OPTIONAL, + tAI-Broadcast-List TAI-Broadcast-List OPTIONAL, + emergencyAreaID-Broadcast-List EmergencyAreaID-Broadcast-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{Broadcast-Scheduled-Area-List-ExtIEs}} OPTIONAL, + ... +} + +Broadcast-Scheduled-Area-List-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Broadcast-Scheduled-Area-List-5GS ::= SEQUENCE { + cellId-Broadcast-List-5GS CellId-Broadcast-List-5GS OPTIONAL, + tAI-Broadcast-List-5GS TAI-Broadcast-List-5GS OPTIONAL, + emergencyAreaID-Broadcast-List EmergencyAreaID-Broadcast-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{Broadcast-Scheduled-Area-List-5GS-ExtIEs}} +OPTIONAL, + ... +} + +Broadcast-Scheduled-Area-List-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Broadcast-Cancelled-Area-List ::= SEQUENCE { + cellID-Cancelled-List CellID-Cancelled-List OPTIONAL, + tAI-Cancelled-List TAI-Cancelled-List OPTIONAL, + emergencyAreaID-Cancelled-List EmergencyAreaID-Cancelled-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{Broadcast-Cancelled-Area-List-ExtIEs}} OPTIONAL, + ... +} + +Broadcast-Cancelled-Area-List-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Broadcast-Cancelled-Area-List-5GS ::= SEQUENCE { + cellID-Cancelled-List-5GS CellID-Cancelled-List-5GS OPTIONAL, + tAI-Cancelled-List-5GS TAI-Cancelled-List-5GS OPTIONAL, + emergencyAreaID-Cancelled-List EmergencyAreaID-Cancelled-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{Broadcast-Cancelled-Area-List-5GS-ExtIEs}} +OPTIONAL, + ... +} + +Broadcast-Cancelled-Area-List-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + ... + } + + Broadcast-Empty-Area-List := SEQUENCE (SIZE (1.. maxnoofENBIds)) OF Global-ENB-ID + + Broadcast-Empty-Area-List-5GS := SEQUENCE (SIZE (1.. maxnoofRANNodes)) OF Global-RAN-Node-ID + + -- C + + CancelledCellinEAI := SEQUENCE (SIZE(1..maxnoofCellinEAI)) OF CancelledCellinEAI-Item + + CancelledCellinEAI-Item := SEQUENCE { + eCGI EUTRAN-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CancelledCellinEAI-Item-ExtIEs} } OPTIONAL, + ... + } + + CancelledCellinEAI-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION := { + ... + } + + CancelledCellinTAI := SEQUENCE (SIZE(1..maxnoofCellinTAI)) OF CancelledCellinTAI-Item + + CancelledCellinTAI-Item := SEQUENCE{ + eCGI EUTRAN-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CancelledCellinTAI-Item-ExtIEs} } OPTIONAL, + ... + } + + CancelledCellinTAI-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION := { + ... + } + + CancelledCellinTAI-5GS := SEQUENCE (SIZE(1..maxnoofCellsin5GSTAI)) OF + SEQUENCE{ + nR-CGI NR-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CancelledCellinTAI-5GS-ExtIEs} } OPTIONAL, + ... + } + + CancelledCellinTAI-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION := { + ... + } + + Cause := INTEGER { + message-accepted (0), + parameter-not-recognised (1), + parameter-value-invalid (2), + valid-message-not-identified (3), + tracking-area-not-valid (4), + unrecognised-message (5), + missing-mandatory-element (6), + mME-capacity-exceeded (7), + mME-memory-exceeded (8), + warning-broadcast-not-supported (9), + warning-broadcast-not-operational (10), + message-reference-already-used (11), + unspecified-error (12), + transfer-syntax-error (13), + semantic-error (14), + message-not-compatible-with-receiver-state (15), + abstract-syntax-error-reject (16), + abstract-syntax-error-ignore-and-notify (17), + abstract-syntax-error-falsely-constructed-message (18) + } (0..255) + + CellId-Broadcast-List := SEQUENCE (SIZE(1..maxnoofCellID)) OF CellId-Broadcast-List-Item + + CellId-Broadcast-List-Item := SEQUENCE { + eCGI EUTRAN-CGI, + iE-Extensions ProtocolExtensionContainer { {CellId-Broadcast-List-Item-ExtIEs} } OPTIONAL, + ... + } + +``` + +``` + +CellId-Broadcast-List-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +CellId-Broadcast-List-5GS ::= SEQUENCE (SIZE(1..maxnoofCellsIn5GS)) OF + SEQUENCE { + nR-CGI NR-CGI, + iE-Extensions ProtocolExtensionContainer { {CellId-Broadcast-List-5GS-ExtIEs} } OPTIONAL, + ... + } + +CellId-Broadcast-List-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +CellID-Cancelled-List ::= SEQUENCE (SIZE(1..maxnoofCellID)) OF CellID-Cancelled-Item + +CellID-Cancelled-Item ::= SEQUENCE { + eCGI EUTRAN-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CellID-Cancelled-Item-ExtIEs} } OPTIONAL, + ... +} + +CellID-Cancelled-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +CellID-Cancelled-List-5GS ::= SEQUENCE (SIZE(1..maxnoofCellsIn5GS)) OF + SEQUENCE { + nR-CGI NR-CGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { {CellID-Cancelled-5GS-ExtIEs} } OPTIONAL, + ... + } + +CellID-Cancelled-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +CellIdentity ::= BIT STRING (SIZE (28)) + +Concurrent-Warning-Message-Indicator ::= ENUMERATED {true} + +Criticality-Diagnostics ::= SEQUENCE { + procedureCode ProcedureCode OPTIONAL, + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + iE-CriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, + ... +} + +CriticalityDiagnostics-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF + SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + typeOfError TypeOfError, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-Item-ExtIEs} } OPTIONAL, + ... + } + +CriticalityDiagnostics-IE-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- D + +Data-Coding-Scheme ::= BIT STRING (SIZE (8)) + +``` + +``` + +-- E + +ECGIList ::= SEQUENCE (SIZE(1..maxnoofCellID)) OF EUTRAN-CGI + +Emergency-Area-ID-List ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF Emergency-Area-ID + +Emergency-Area-ID ::= OCTET STRING (SIZE (3)) + +EmergencyAreaID-Broadcast-List ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF EmergencyAreaID- +Broadcast-List-Item + +EmergencyAreaID-Broadcast-List-Item ::= SEQUENCE { + emergencyAreaID Emergency-Area-ID, + scheduledCellinEAI ScheduledCellinEAI, + iE-Extensions ProtocolExtensionContainer { {EmergencyAreaID-Broadcast-List-Item-ExtIEs} } + OPTIONAL, + ... +} + +EmergencyAreaID-Broadcast-List-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +EmergencyAreaID-Cancelled-List ::= SEQUENCE (SIZE(1..maxnoofEmergencyAreaID)) OF EmergencyAreaID- +Cancelled-Item + +EmergencyAreaID-Cancelled-Item ::= SEQUENCE { + emergencyAreaID Emergency-Area-ID, + cancelledCellinEAI CancelledCellinEAI, + iE-Extensions ProtocolExtensionContainer { {EmergencyAreaID-Cancelled-Item-ExtIEs} } OPTIONAL, + ... +} + +EmergencyAreaID-Cancelled-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRAN-CGI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + cell-ID CellIdentity, + iE-Extensions ProtocolExtensionContainer { {EUTRAN-CGI-ExtIEs} } OPTIONAL, + ... +} + +EUTRAN-CGI-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Extended-Repetition-Period ::= INTEGER (4096..131071) + +ENB-ID ::= CHOICE { + macroENB-ID BIT STRING (SIZE(20)), + homeENB-ID BIT STRING (SIZE(28)), + .../ + short-macroENB-ID BIT STRING (SIZE(18)), + long-macroENB-ID BIT STRING (SIZE(21)) +} + +-- F + +Failed-Cell-List ::= SEQUENCE (SIZE(1..maxnoofFailedCells)) OF EUTRAN-CGI + +Failed-Cell-List-NR ::= SEQUENCE (SIZE(1..maxnoofCellsingNB)) OF NR-CGI + +-- G + +Global-ENB-ID ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + eNB-ID ENB-ID, + iE-Extensions ProtocolExtensionContainer { {GlobalENB-ID-ExtIEs} } OPTIONAL, + ... +} + +GlobalENB-ID-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +Global-RAN-Node-ID ::= CHOICE { + global-GNB-ID Global-GNB-ID, + global-NgENB-ID Global-NgENB-ID, + ... +} + +Global-GNB-ID ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + gNB-ID GNB-ID, + iE-Extensions ProtocolExtensionContainer { {Global-GNB-ID-ExtIEs} } OPTIONAL, + ... +} + +Global-GNB-ID-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-ID ::= CHOICE { + gNB-ID BIT STRING (SIZE(22..32)), + ... +} + +Global-NgENB-ID ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + ngENB-ID ENB-ID, + iE-Extensions ProtocolExtensionContainer { {Global-NgENB-ID-ExtIEs} } OPTIONAL, + ... +} + +Global-NgENB-ID-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +-- H + +-- I + +-- J + +-- K + +-- L + +List-of-TAIs ::= SEQUENCE (SIZE (1..maxNrOfTAIs)) OF + SEQUENCE { + tai TAI + } + +List-of-TAIs-Restart ::= SEQUENCE (SIZE (1..maxnoofRestartTAIs)) OF + SEQUENCE { + tai TAI + } + +List-of-EAIs-Restart ::= SEQUENCE (SIZE (1..maxnoofRestartEAIs)) OF Emergency-Area-ID + +List-of-5GS-TAIs ::= SEQUENCE (SIZE (1..maxnoof5GSTAIs)) OF TAI-5GS + +List-of-5GS-Cells-for-Failure ::= SEQUENCE ( SIZE (1..maxnoofCellsingNB)) OF NR-CGI + +List-of-5GS-TAI-for-Restart ::= SEQUENCE (SIZE (1..maxnoofRestart5GSTAIs)) OF TAI-5GS + +-- M + +Message-Identifier ::= BIT STRING (SIZE (16)) + +-- N + +Number-of-Broadcasts-Requested ::= INTEGER (0..65535) + +-- For Number-of-Broadcasts-Requested = 0 and Repetition-Period = 0, then eNB action is no broadcast +-- for ETWS Secondary and CMAS. +-- +-- For Number-of-Broadcasts-Requested = 1 and Repetition-Period = 0, then eNB action is broadcast +-- only once for ETWS and CMAS. +-- + +``` + +``` + +-- For Number-of-Broadcasts-Requested = 0 and Repetition-Period > 0, then eNB action is no broadcast +-- for the ETWS Secondary, and broadcast until further notice for the CMAS. +-- +-- For Number-of-Broadcasts-Requested > 0 and Repetition-Period > 0, then eNB action is normal +-- broadcast. +-- All other combinations of Number-of-Broadcasts-Requested and Repetition-Period are considered +-- invalid. + +NumberOfBroadcasts ::= INTEGER (0..65535) + +NR-CGIList ::= SEQUENCE (SIZE(1..maxnoofCellsingNB)) OF NR-CGI + +NR-CGI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + nRCellIdentity NRCellIdentity, + iE-Extensions ProtocolExtensionContainer { {NR-CGI-ExtIEs} } OPTIONAL, + ... +} + +NR-CGI-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +NRCellIdentity ::= BIT STRING (SIZE(36)) + +NgENB-ID ::= CHOICE { + macroNgENB-ID BIT STRING (SIZE(20)), + shortMacroNgENB-ID BIT STRING (SIZE(18)), + longMacroNgENB-ID BIT STRING (SIZE(21)), + ... +} + +-- O +Omc-Id ::= OCTET STRING (SIZE (1..20)) + +-- P +PLMNIdentity ::= TBCD-STRING + +-- Q + +-- R + +Repetition-Period ::= INTEGER (0..4096) +-- 1 to 4096: Each unit represents a repetition of one second to a maximum of +-- once per 4096 seconds (~1 hour). +-- 0: no repetition +-- A CBC compliant to this version or later of this specification shall not send a repetition period +-- greater than 4095. +-- For backwards compatibility with a CBC compliant to an earlier version of this specification the +-- maximum value of the repetition period defined in ASN.1 remains at 4096. +-- If the value of the Repetition Period IE received in the WRITE-REPLACE WARNING REQUEST message is +-- set to 4096, the MME shall set the Repetition Period IE to the maximum value 4095 supported on +-- the S1-MME interface as defined in [7] before forwarding to the selected eNBs. + +Restarted-Cell-List ::= SEQUENCE (SIZE(1.. maxnoofRestartedCells)) OF EUTRAN-CGI + +RAT-Selector-5GS ::= ENUMERATED {true} + +Restarted-Cell-List-NR ::= SEQUENCE (SIZE(1.. maxnoofCellsforRestartNR)) OF NR-CGI + +-- S + +ScheduledCellinEAI ::= SEQUENCE (SIZE(1..maxnoofCellinEAI)) OF ScheduledCellinEAI-Item + +ScheduledCellinEAI-Item ::= SEQUENCE { + eCGI EUTRAN-CGI, + iE-Extensions ProtocolExtensionContainer { {ScheduledCellinEAI-Item-ExtIEs} } OPTIONAL, + ... +} + +ScheduledCellinEAI-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +ScheduledCellinTAI ::= SEQUENCE (SIZE(1..maxnoofCellinTAI)) OF ScheduledCellinTAI-Item + +``` + +``` + +ScheduledCellinTAI-Item ::= SEQUENCE{ + eCGI EUTRAN-CGI, + iE-Extensions ProtocolExtensionContainer { {ScheduledCellinTAI-Item-ExtIEs} } OPTIONAL, + ... +} + +ScheduledCellinTAI-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +ScheduledCellinTAI-5GS ::= SEQUENCE (SIZE(1..maxnoofCellsin5GSTAI)) OF + SEQUENCE{ + nR-CGI NR-CGI, + iE-Extensions ProtocolExtensionContainer { {ScheduledCellinTAI-5GS-ExtIEs} } OPTIONAL, + ... + } + +ScheduledCellinTAI-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +Send-Write-Replace-Warning-Indication ::= ENUMERATED {true} + +Send-Stop-Warning-Indication ::= ENUMERATED {true} + +Serial-Number ::= BIT STRING (SIZE (16)) + +Stop-All-Indicator ::= ENUMERATED {true} + +-- T + +TAC ::= OCTET STRING (SIZE (2)) + +TAC-5GS ::= OCTET STRING (SIZE (3)) + +TAI-Broadcast-List ::= SEQUENCE (SIZE(1..maxnoofTAIforWarning)) OF TAI-Broadcast-List-Item + +TAI-Broadcast-List-Item ::= SEQUENCE { + tAI TAI, + scheduledCellinTAI ScheduledCellinTAI, + iE-Extensions ProtocolExtensionContainer { {TAI-Broadcast-List-Item-ExtIEs} } OPTIONAL, + ... +} + +TAI-Broadcast-List-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +TAI-Broadcast-List-5GS ::= SEQUENCE (SIZE(1..maxnoof5GSTAIs)) OF + SEQUENCE { + tAI-5GS TAI-5GS, + scheduledCellinTAI-5GS ScheduledCellinTAI-5GS, + iE-Extensions ProtocolExtensionContainer { {TAI-Broadcast-List-5GS-ExtIEs} } OPTIONAL, + ... + } + +TAI-Broadcast-List-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +TAI-Cancelled-List ::= SEQUENCE (SIZE(1..maxnoofTAIforWarning)) OF TAI-Cancelled-List-Item + +TAI-Cancelled-List-Item ::= SEQUENCE { + tAI TAI, + cancelledCellinTAI CancelledCellinTAI, + iE-Extensions ProtocolExtensionContainer { {TAI-Cancelled-List-Item-ExtIEs} } OPTIONAL, + ... +} + +TAI-Cancelled-List-Item-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... +} + +TAI-Cancelled-List-5GS ::= SEQUENCE (SIZE(1..maxnoof5GSTAIs)) OF + SEQUENCE { + tAI-5GS TAI-5GS, + } + +``` + +``` + + cancelledCellinTAI-5GS CancelledCellinTAI-5GS, + iE-Extensions ProtocolExtensionContainer { {TAI-Cancelled-List-5GS-ExtIEs} } OPTIONAL, + ... + } + + TAI-Cancelled-List-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... + } + + TAI-List-for-Warning ::= SEQUENCE (SIZE(1.. maxnoofTAIforWarning)) OF TAI + + TAI ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + tAC TAC, + iE-Extensions ProtocolExtensionContainer { {TAI-ExtIEs} } OPTIONAL + } + + TAI-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... + } + + TBCD-STRING ::= OCTET STRING (SIZE (3)) + + TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... + } + + TAI-5GS ::= SEQUENCE { + pLMNIdentity PLMNIdentity, + tAC-5GS TAC-5GS, + iE-Extensions ProtocolExtensionContainer { {TAI-5GS-ExtIEs} } OPTIONAL + } + + TAI-5GS-ExtIEs SBC-AP-PROTOCOL-EXTENSION ::= { + ... + } + + -- U + + Unknown-Tracking-Area-List ::= SEQUENCE (SIZE(1.. maxNrOfTAIs)) OF TAI + + Unknown-5GS-Tracking-Area-List ::= SEQUENCE (SIZE(1.. maxnoof5GSTAIs)) OF TAI-5GS + + -- V + + -- W + + Warning-Area-List ::= CHOICE { + cell-ID-List ECGIList, + tracking-Area-List-for-Warning TAI-List-for-Warning, + emergency-Area-ID-List Emergency-Area-ID-List, + ... + } + + Warning-Message-Content ::= OCTET STRING (SIZE (1..9600)) + Warning-Area-Coordinates ::= OCTET STRING (SIZE (1..1024)) + Warning-Security-Information ::= OCTET STRING (SIZE (50)) + Warning-Type ::= OCTET STRING (SIZE (2)) + + Warning-Area-List-5GS ::= CHOICE { + cell-ID-List ECGIList, + nR-CGIList NR-CGIList, + tAIList-5GS TAI-5GS, + emergencyAreaIDList Emergency-Area-ID-List, + ... + } + + -- X + + -- Y + +END + +``` + +### 4.4.6 Common definitions + +``` + +-- ***** +-- +-- Common definitions +-- +-- ***** + +SBC-AP-CommonDataTypes { + itu-t (0) identified-organization (4) etai (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-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 + +``` + +### 4.4.7 Constant definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +SBC-AP-Constants { + itu-t (0) identified-organization (4) etai (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-Constants (4)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- Elementary Procedures +-- +-- ***** + + id-Write-Replace-Warning INTEGER ::= 0 + id-Stop-Warning INTEGER ::= 1 + id-Error-Indication INTEGER ::= 2 + id-Write-Replace-Warning-Indication INTEGER ::= 3 + id-Stop-Warning-Indication INTEGER ::= 4 + id-PWS-Restart-Indication INTEGER ::= 5 + id-PWS-Failure-Indication INTEGER ::= 6 + +-- ***** +-- +-- IEs +-- +-- ***** + + id-Broadcast-Message-Content INTEGER ::= 0 + id-Cause INTEGER ::= 1 + id-Criticality-Diagnostics INTEGER ::= 2 + id-Data-Coding-Scheme INTEGER ::= 3 + id-Failure-List INTEGER ::= 4 + id-Message-Identifier INTEGER ::= 5 + id-Number-of-Broadcasts-Completed-List INTEGER ::= 6 + id-Number-of-Broadcasts-Requested INTEGER ::= 7 + id-Radio-Resource-Loading-List INTEGER ::= 8 + +``` + +``` + +id-Recovery-Indication INTEGER := 9 +id-Repetition-Period INTEGER := 10 +id-Serial-Number INTEGER := 11 +id-Service-Areas-List INTEGER := 12 +id-TypeOfError INTEGER := 13 +id-List-of-TAIs INTEGER := 14 +id-Warning-Area-List INTEGER := 15 +id-Warning-Message-Content INTEGER := 16 +id-Warning-Security-Information INTEGER := 17 +id-Warning-Type INTEGER := 18 +id-Omc-Id INTEGER := 19 +id-Concurrent-Warning-Message-Indicator INTEGER := 20 +id-Extended-Repetition-Period INTEGER := 21 +id-Unknown-Tracking-Area-List INTEGER := 22 +id-Broadcast-Scheduled-Area-List INTEGER := 23 +id-Send-Write-Replace-Warning-Indication INTEGER := 24 +id-Broadcast-Cancelled-Area-List INTEGER := 25 +id-Send-Stop-Warning-Indication INTEGER := 26 +id-Stop-All-Indicator INTEGER := 27 +id-Global-ENB-ID INTEGER := 28 +id-Broadcast-Empty-Area-List INTEGER := 29 +id-Restarted-Cell-List INTEGER := 30 +id-List-of-TAIs-Restart INTEGER := 31 +id-List-of-EAIs-Restart INTEGER := 32 +id-Failed-Cell-List INTEGER := 33 +id-List-of-5GS-TAIs INTEGER := 34 +id-Warning-Area-List-5GS INTEGER := 35 +id-Global-RAN-Node-ID INTEGER := 36 +id-Global-GNB-ID INTEGER := 37 +id-RAT-Selector-5GS INTEGER := 38 +id-Unknown-5GS-Tracking-Area-List INTEGER := 39 +id-Broadcast-Scheduled-Area-List-5GS INTEGER := 40 +id-Broadcast-Cancelled-Area-List-5GS INTEGER := 41 +id-Broadcast-Empty-Area-List-5GS INTEGER := 42 +id-Restarted-Cell-List-NR INTEGER := 43 +id-Failed-Cell-List-NR INTEGER := 44 +id-List-of-5GS-TAI-for-Restart INTEGER := 45 +id-Warning-Area-Coordinates INTEGER := 46 + +-- ***** +-- +-- Extension constants +-- +-- ***** + +-- ***** +-- +-- Lists +-- +-- ***** + +maxNrOfErrors INTEGER := 256 +maxnoofCellID INTEGER := 65535 +maxnoofCellinEAI INTEGER := 65535 +maxnoofCellinTAI INTEGER := 65535 +maxNrOfTAIs INTEGER := 65535 +maxnoofEmergencyAreaID INTEGER := 65535 +maxnoofTAIforWarning INTEGER := 65535 + +maxProtocolExtensions INTEGER := 65535 +maxProtocolIEs INTEGER := 65535 +maxnoofENBIDs INTEGER := 256 +maxnoofRestartedCells INTEGER := 256 +maxnoofRestartTAIs INTEGER := 2048 +maxnoofRestartEAIs INTEGER := 256 +maxnoofFailedCells INTEGER := 256 +maxnoof5GSTAIs INTEGER := 2048 +maxnoofCellsingNB INTEGER := 16384 +maxnoofCellsin5GS INTEGER := 16776960 +maxnoofCellsin5GSTAI INTEGER := 65535 +maxnoofRANNodes INTEGER := 65535 +maxnoofRestart5GSTAIs INTEGER := 2048maxnoofCellsforRestartNR INTEGER := 16384 + +END + +``` + +### 4.4.8 Container Definitions + +``` + +-- ***** +-- +-- Container definitions +-- +-- ***** + +SBC-AP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + eps-Access (21) modules (3) sbc-AP (3) version1 (1) sbc-AP-Containers (5)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + Presence, + ProtocolExtensionID, + ProtocolIE-ID +FROM SBC-AP-CommonDataTypes + + maxProtocolExtensions, + maxProtocolIEs +FROM SBC-AP-Constants; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +SBC-AP-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 +-- +-- ***** + +SBC-AP-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 {SBC-AP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {SBC-AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id SBC-AP-PROTOCOL-IES.&id ({IEsSetParam}), + criticality SBC-AP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), + value SBC-AP-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, SBC-AP-PROTOCOL-IES : + IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {SBC-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {SBC-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id SBC-AP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality SBC-AP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue SBC-AP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) +} + +END + +``` + +### 4.4.9 Message transfer syntax + +SBC-AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. [10]. + +## 4.5 Handling of unknown, unforeseen or erroneous protocol data + +### 4.5.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 SBc-AP. It shows two functional blocks: 'SBc-AP 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 top block point to 'Logical Errors' and 'Abstract Syntax Errors'. A bracket on the right side of the bottom block points to 'Transfer Syntax Errors'. A large upward-pointing arrow on the far right indicates the flow of errors from the bottom block to the top block.](94d3fdcc244924326f02533aeb2d93fc_img.jpg) + +``` + +graph TD + subgraph SBc-AP [SBc-AP functional entity] + LE[Logical Errors] + ASE[Abstract Syntax Errors] + end + subgraph ASN1 [ASN.1 Decoding] + TSE[Transfer Syntax Errors] + end + ASN1 <--> SBc-AP + TSE --> SBc-AP + +``` + +Diagram illustrating Protocol Errors in SBc-AP. It shows two functional blocks: 'SBc-AP 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 top block point to 'Logical Errors' and 'Abstract Syntax Errors'. A bracket on the right side of the bottom block points to 'Transfer Syntax Errors'. A large upward-pointing arrow on the far right indicates the flow of errors from the bottom block to the top block. + +**Figure 4.5.1-1: Protocol Errors in SBc-AP** + +The information stated in clauses 4.5.2, 4.5.3 and 4.5.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. + +### 4.5.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. + +### 4.5.3 Abstract Syntax Error + +#### 4.5.3.1 General + +An Abstract Syntax Error occurs when the receiving functional SBc-AP 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 clauses 4.5.3.4 and 4.5.3.5. The handling of cases 4 and 5 is specified in clause 4.5.3.6. + +#### 4.5.3.2 Criticality information + +In the SBc-AP 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 clause 4.5.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see clause 4.5.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. + +#### 4.5.3.3 Presence information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, SBc-AP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to MME/CBC application. + +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. + +#### 4.5.3.4 Not comprehended IE/IE group + +##### 4.5.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. + +##### 4.5.3.4.2 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. + +##### 4.5.3.4.3 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. + +#### 4.5.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. + +#### 4.5.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. + +### 4.5.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. + +### 4.5.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other clauses of clause 4.5. + +- 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: + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-------|-----------|------|-----|----------------------------------------------------------------------------|--------| +| 2008-12 | CT#42 | CP-080972 | | | V1.0.2 approved in CT#42 | 8.0.0 | +| 2009-03 | CT#43 | CP-090101 | 0001 | 3 | General clean-up to make an alignment with RAN specifications | 8.1.0 | +| | | CP-090022 | 0002 | - | General clean-up to make an alignment with RAN specifications | | +| 2009-09 | CT#45 | CP-090543 | 0003 | 1 | Correct ASN.1 misalignment between S1AP and SB-AP | 8.2.0 | +| | | | 0004 | 1 | Fix the ASN.1 Object Identifiers (OID) descriptions for SBc-AP | | +| | | | 0005 | 1 | Update port number and payload protocol identifier for SBc-AP | | +| | | | 0006 | - | Fix incorrect IETF reference | | +| 2009-12 | CT#46 | CP-090780 | 0008 | 1 | Missing OMC-ID and other corrections | 8.3.0 | +| | | | 0009 | - | Correction of Warning Message Transmission procedure | | +| 2009-12 | CT#46 | CP-090799 | 0007 | 4 | Enhancements to Warning Notifications to support PWS/CMAS Requirements | 9.0.0 | +| 2010-06 | CT#48 | CP-100288 | 0011 | 2 | Number of Broadcasts | 9.1.0 | +| 2010-09 | CT#49 | CP-100446 | 0013 | - | Correction of the SCTP Payload Protocol value for the SBc-AP | 9.2.0 | +| 2010-12 | CT#50 | CP-100708 | 0014 | 3 | Correct WRITE-REPLACE-WARNING REQUEST misalignment between S1AP and SBc-AP | 9.3.0 | +| 2011-03 | CT#51 | CP-110080 | 0015 | 2 | SBc-AP Error Indication | 10.0.0 | +| 2011-09 | CT#53 | CP-110579 | 0016 | - | Error Indication procedure | 11.0.0 | +| 2011-12 | CT#54 | CP-110797 | 0018 | - | Error Indication | 11.1.0 | +| | | CP-110783 | 0020 | - | Extended Repetition Period | | +| 2012-03 | CT#55 | CP-120021 | 0024 | - | Correction to Assigned Criticality | 11.2.0 | +| 2012-06 | CT#56 | CP-120246 | 0025 | - | Corrections to ASN.1 code | 11.3.0 | +| 2012-09 | CT#57 | CP-120460 | 0026 | - | Correction to ASN1 syntax | 11.4.0 | +| | | CP-120460 | 0027 | - | Editorial updates of references | | +| | | CP-120463 | 0031 | - | ETWS Secondary Notification | | +| 2012-12 | CT#58 | CP-120886 | 0029 | 4 | Report to CBC on Warning Message Delivery | 12.0.0 | +| | | CP-120886 | 0030 | 4 | Failure List in WRITE-REPLACE RESPONSE and STOP WARNING RESPONSE | | +| 2013-03 | CT#59 | CP-130031 | 0034 | - | Corrections to ASN.1 encoding | 12.1.0 | + +| | | | | | | | +|---------|--------|-----------|------|---|-----------------------------------------------------------------------------------------|--------| +| 2013-06 | CT#60 | CP-130308 | 0036 | - | Editorial Corrections | 12.2.0 | +| 2013-09 | CT#61 | CP-130455 | 0033 | 1 | Report to CBC on Stop Warning Message Delivery | 12.3.0 | +| | | | 0038 | 1 | Stop-all Warning Messages | | +| 2013-09 | | | | | The header 4.3.4.3.8 style corrected | 12.3.1 | +| 2013-12 | CT#62 | CP-130622 | 0044 | 2 | eNodeB ID List | 12.4.0 | +| | | | 0045 | 1 | Correction of references to clauses | | +| | | | 0048 | 1 | Unsuccessful Outcome | | +| 2014-03 | CT#63 | CP-140154 | 0042 | 7 | PWS Restart Indication | 12.5.0 | +| 2014-06 | CT#64 | CP-140255 | 0050 | 2 | Routing of PWS messages to HeNBs | 12.6.0 | +| 2014-12 | CT#66 | CP-140782 | 0051 | - | Warning Area List in Write-Replace Warning Request during PWS restoration | 12.7.0 | +| | | | 0052 | 1 | Serial Number in Write-Replace Warning Request during PWS restoration | | +| | | | 0054 | - | Message Type for PWS Restart Indication | | +| 2015-03 | CT#67 | CP-150029 | 0055 | 1 | Incorrect reference in STOP WARNING REQUEST | 12.8.0 | +| 2015-06 | CT#68 | CP-150262 | 0056 | 1 | Criticality of the Cause IE in Write-Replace Warning Response and Stop Warning Response | 13.0.0 | +| 2015-09 | CT#69 | CP-150438 | 0057 | 1 | Inconsistent Criticality information | 13.1.0 | +| 2015-12 | CT#70 | CP-150741 | 0065 | - | ASN.1 Corrections | 13.2.0 | +| | | | 0058 | 2 | Failure Indication | 13.2.0 | +| | | | 0059 | 3 | Style fixes and resolution of editor's note | 13.2.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2017-09 | CT#77 | CP-172012 | 0068 | 1 | Restarted Cell List in PWS RESTART INDICATION | 14.1.0 | +| 2017-12 | CT#78 | CP-1730 | 0069 | - | Introduction of New types of eNB ID | 14.2.0 | +| 2018-06 | CT#80 | CP-181132 | 0070 | 2 | Modifications needed to address 5GS over SBc | 15.0.0 | +| 2018-09 | CT#81 | CP-182077 | 0071 | 1 | New field Warning Area Coordinates in WRITE-REPLACE WARNING REQUEST | 15.1.0 | +| 2020-06 | CT#88e | CP-201065 | 0074 | 1 | Essential Corrections on PWS Procedures for 5GC | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29336/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29336/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d71ca36e7ff66963cd121f01962d1e4c5988d8e --- /dev/null +++ b/marked/Rel-16/29_series/29336/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e753d9b8df95c1a3dbfd6ee05383dd32f4b2ef2934256c0b99eb63dae2ecf18 +size 9496 diff --git a/marked/Rel-16/29_series/29336/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29336/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..166992d523b0feb65738c8978316629228121d16 --- /dev/null +++ b/marked/Rel-16/29_series/29336/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a081b6d8f23b82b04d33ac75617b7baedcc54e4ce1f98c3171eddae052031b83 +size 6450 diff --git a/marked/Rel-16/29_series/29336/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/29_series/29336/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7275167ac542198ff3be58717733d90bbe7d0259 --- /dev/null +++ b/marked/Rel-16/29_series/29336/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7037514dde6dfd2e2f95e7a7af05e2dc6822b69c520d406cd5f1c134fc77b973 +size 66865 diff --git a/marked/Rel-16/29_series/29336/raw.md b/marked/Rel-16/29_series/29336/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7d5b8fd6a85ef9940a140730283c22354d5f38fc --- /dev/null +++ b/marked/Rel-16/29_series/29336/raw.md @@ -0,0 +1,3239 @@ + + +# 3GPP TS 29.336 V16.4.0 (2023-09) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications (Release 16)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 'e' is the text 'Advanced Pro' in a smaller font. To the right of the 'e' is a green signal icon consisting of three curved lines. + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. Below the 'P' is a red signal icon consisting of three curved lines. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, uppercase font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +Postal address + +--- + +3GPP support office address + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + + + +--- + +## ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations ..... | 9 | +| 3.1 Abbreviations ..... | 9 | +| 4 General Description ..... | 9 | +| 4.1 Introduction ..... | 9 | +| 5 Diameter-based S6m/S6n Interface ..... | 11 | +| 5.1 Introduction ..... | 11 | +| 5.2 Procedure Descriptions ..... | 11 | +| 5.2.1 Subscriber Information Retrieval ..... | 11 | +| 5.2.1.1 General..... | 11 | +| 5.2.1.2 Detailed Behaviour of the HSS..... | 13 | +| 5.2.1.3 Detailed Behaviour of the MTC-IWF..... | 14 | +| 5.2.1.4 Detailed Behaviour of the MTC-AAA ..... | 14 | +| 6 Protocol Specification ..... | 15 | +| 6.1 Introduction ..... | 15 | +| 6.1.1 Use of Diameter Base Protocol ..... | 15 | +| 6.1.2 Securing Diameter Messages ..... | 15 | +| 6.1.3 Accounting Functionality ..... | 15 | +| 6.1.4 Use of Sessions..... | 15 | +| 6.1.5 Transport Protocol..... | 15 | +| 6.1.6 Routing Considerations ..... | 15 | +| 6.1.7 Advertising Application Support..... | 16 | +| 6.1.8 Diameter Application Identifier..... | 16 | +| 6.1.9 Use of the Supported-Features AVP ..... | 16 | +| 6.1.10 User Identity to HSS resolution..... | 16 | +| 6.2 Commands..... | 17 | +| 6.2.1 Introduction ..... | 17 | +| 6.2.2 Command-Code values ..... | 17 | +| 6.2.3 Subscriber-Information-Request (SIR) Command..... | 17 | +| 6.2.4 Subscriber-Information-Answer (SIA) Command ..... | 18 | +| 6.3 Result-Code AVP and Experimental-Result AVP Values..... | 18 | +| 6.3.1 General ..... | 18 | +| 6.3.2 Success ..... | 18 | +| 6.3.3 Permanent Failures ..... | 18 | +| 6.3.3.1 DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 18 | +| 6.3.3.2 DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_ENTITY (5510)..... | 18 | +| 6.3.3.3 DIAMETER_ERROR_UNAUTHORIZED_SERVICE (5511)..... | 19 | +| 6.4 AVPs ..... | 19 | +| 6.4.1 General ..... | 19 | +| 6.4.2 User-Identifier ..... | 20 | +| 6.4.3 Service-ID..... | 20 | +| 6.4.4 SCS-Identity ..... | 20 | +| 6.4.5 Service-Parameters ..... | 21 | +| 6.4.6 T4-Parameters..... | 21 | +| 6.4.7 Service-Data ..... | 21 | +| 6.4.8 T4-Data..... | 21 | +| 6.4.9 HSS-Cause..... | 22 | +| 6.4.10 SIR-Flags ..... | 22 | +| 6.4.11 External-Identifier ..... | 22 | +| 6.4.12 Serving-Node..... | 22 | +| 6.4.13 Additional-Serving-Node ..... | 23 | + +| | | | +|---------|--------------------------------------------------------------------------|----| +| 6.4.14 | IP-SM-GW-Number ..... | 24 | +| 6.4.15 | IP-SM-GW-Name..... | 24 | +| 6.4.16 | OC-Supported-Features ..... | 24 | +| 6.4.17 | OC-OLR ..... | 24 | +| 6.4.18 | IP-SM-GW-Realm..... | 24 | +| 6.4.19 | DRMP..... | 24 | +| 6.4.20 | Load..... | 24 | +| 7 | Diameter-based S6t Interface..... | 24 | +| 7.1 | Introduction ..... | 24 | +| 7.2 | Procedure Descriptions ..... | 25 | +| 7.2.1 | Configuration Information on S6t ..... | 25 | +| 7.2.1.1 | General..... | 25 | +| 7.2.1.2 | Detailed Behaviour of the HSS..... | 28 | +| 7.2.1.3 | Detailed Behaviour of the SCEF ..... | 31 | +| 7.2.2 | Reporting on S6t..... | 32 | +| 7.2.2.1 | General..... | 32 | +| 7.2.2.2 | Detailed Behaviour of the HSS..... | 34 | +| 7.2.2.3 | Detailed Behaviour of the SCEF ..... | 35 | +| 7.2.3 | NIDD Information on S6t..... | 36 | +| 7.2.3.1 | General..... | 36 | +| 7.2.3.2 | Detailed Behaviour of the HSS..... | 38 | +| 7.2.3.3 | Detailed Behaviour of the SCEF ..... | 38 | +| 8 | Protocol Specification for S6t..... | 39 | +| 8.1 | Introduction ..... | 39 | +| 8.1.1 | Use of Diameter Base Protocol ..... | 39 | +| 8.1.2 | Securing Diameter Messages ..... | 39 | +| 8.1.3 | Accounting Functionality ..... | 39 | +| 8.1.4 | Use of Sessions..... | 39 | +| 8.1.5 | Transport Protocol..... | 39 | +| 8.1.6 | Routing Considerations ..... | 39 | +| 8.1.7 | Advertising Application Support..... | 40 | +| 8.1.8 | Diameter Application Identifier..... | 40 | +| 8.1.9 | Use of the Supported-Features AVP ..... | 40 | +| 8.1.10 | User Identity to HSS resolution..... | 40 | +| 8.2 | Commands..... | 41 | +| 8.2.1 | Introduction ..... | 41 | +| 8.2.2 | Command-Code values ..... | 41 | +| 8.2.3 | Configuration Information Request (CIR) Command..... | 41 | +| 8.2.4 | Configuration-Information-Answer (CIA) Command ..... | 42 | +| 8.2.5 | Reporting-Information-Request (RIR) Command ..... | 42 | +| 8.2.6 | Reporting-Information-Answer (RIA) Command..... | 43 | +| 8.2.7 | NIDD Information Request (NIR) Command..... | 43 | +| 8.2.8 | NIDD-Information-Answer (NIA) Command..... | 43 | +| 8.3 | Result-Code AVP and Experimental-Result AVP Values..... | 44 | +| 8.3.1 | General ..... | 44 | +| 8.3.2 | Success ..... | 44 | +| 8.3.3 | Permanent Failures ..... | 44 | +| 8.3.3.1 | DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 44 | +| 8.3.3.2 | DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_ENTITY (5510)..... | 44 | +| 8.3.3.3 | DIAMETER_ERROR_UNAUTHORIZED_SERVICE (5511)..... | 44 | +| 8.3.3.4 | DIAMETER_ERROR_REQUESTED_RANGE_IS_NOT_ALLOWED (5512) ..... | 44 | +| 8.3.3.5 | DIAMETER_ERROR_CONFIGURATION_EVENT_STORAGE_NOT_SUCCESSFUL
(5513)..... | 45 | +| 8.3.3.6 | DIAMETER_ERROR_CONFIGURATION_EVENT_NON_EXISTANT (5514)..... | 45 | +| 8.3.3.7 | DIAMETER_ERROR_USER_NO_APN_SUBSCRIPTION (5451)..... | 45 | +| 8.3.3.8 | DIAMETER_ERROR_UNAUTHORIZED_MTC_PROVIDER (5516)..... | 45 | +| 8.4 | AVPs ..... | 45 | +| 8.4.1 | General ..... | 45 | +| 8.4.2 | Monitoring-Event-Configuration ..... | 49 | +| 8.4.3 | Monitoring-Event-Report ..... | 50 | + +| | | | +|----------|------------------------------------------------|----| +| 8.4.4 | SCEF-Reference-ID ..... | 51 | +| 8.4.5 | SCEF-ID ..... | 51 | +| 8.4.6 | SCEF-Reference-ID-for-Deletion ..... | 51 | +| 8.4.7 | Monitoring-Type ..... | 51 | +| 8.4.8 | Maximum-Number-of-Reports ..... | 51 | +| 8.4.9 | UE-Reachability-Configuration ..... | 51 | +| 8.4.10 | Monitoring-Duration ..... | 52 | +| 8.4.11 | Maximum-Detection-Time ..... | 52 | +| 8.4.12 | Reachability-Type ..... | 52 | +| 8.4.13 | Maximum-Latency ..... | 52 | +| 8.4.14 | Maximum-Response-Time ..... | 52 | +| 8.4.15 | Location-Information-Configuration ..... | 52 | +| 8.4.16 | MONTE-Location-Type ..... | 53 | +| 8.4.17 | Accuracy ..... | 53 | +| 8.4.18 | Association-Type ..... | 53 | +| 8.4.19 | Roaming-Information ..... | 53 | +| 8.4.20 | Reachability-Information ..... | 53 | +| 8.4.21 | EPS-Location-Information ..... | 54 | +| 8.4.22 | IMEI-Change ..... | 54 | +| 8.4.23 | Feature-List AVP ..... | 54 | +| 8.4.23.1 | Feature-List AVP for the S6t application ..... | 54 | +| 8.4.24 | Monitoring-Event-Config-Status ..... | 56 | +| 8.4.25 | AESE-Communication-Pattern ..... | 56 | +| 8.4.26 | Communication-Pattern-Set ..... | 57 | +| 8.4.27 | Periodic-Communication-Indicator ..... | 57 | +| 8.4.28 | Communication-duration-time ..... | 57 | +| 8.4.29 | Periodic-time ..... | 57 | +| 8.4.30 | Scheduled-communication-time ..... | 58 | +| 8.4.31 | Stationary indication ..... | 58 | +| 8.4.32 | AESE-Communication-Pattern-Config-Status ..... | 58 | +| 8.4.33 | AESE-Error-Report ..... | 58 | +| 8.4.34 | MME-Location-Information ..... | 59 | +| 8.4.35 | SGSN-Location-Information ..... | 59 | +| 8.4.36 | User-Identifier ..... | 59 | +| 8.4.37 | Service-Result ..... | 60 | +| 8.4.38 | Service-Result-Code ..... | 60 | +| 8.4.39 | CIR-Flags ..... | 60 | +| 8.4.40 | Supported-Services ..... | 61 | +| 8.4.41 | Supported-Monitoring-Events ..... | 61 | +| 8.4.42 | Reference-ID-Validity-Time ..... | 61 | +| 8.4.43 | Event-Handling ..... | 62 | +| 8.4.44 | NIDD-Authorization-Request ..... | 62 | +| 8.4.45 | NIDD-Authorization-Response ..... | 62 | +| 8.4.46 | DRMP ..... | 62 | +| 8.4.47 | Service-Report ..... | 62 | +| 8.4.48 | Node-Type ..... | 63 | +| 8.4.49 | Service-Selection ..... | 63 | +| 8.4.50 | S6t-HSS-Cause ..... | 63 | +| 8.4.51 | Enhanced-Coverage-Restriction ..... | 63 | +| 8.4.52 | Enhanced-Coverage-Restriction-Data ..... | 63 | +| 8.4.53 | Restricted-PLMN-List ..... | 64 | +| 8.4.54 | Allowed-PLMN-List ..... | 64 | +| 8.4.55 | Requested-Validity-Time ..... | 64 | +| 8.4.56 | Granted-Validity-Time ..... | 64 | +| 8.4.57 | NIDD-Authorization-Update ..... | 64 | +| 8.4.58 | Loss-Of-Connectivity-Reason ..... | 65 | +| 8.4.59 | Group-Reporting-Guard-Timer ..... | 65 | +| 8.4.60 | CIA-Flags ..... | 65 | +| 8.4.61 | Group-Report ..... | 65 | +| 8.4.62 | Group-Report-Item ..... | 66 | +| 8.4.63 | RIR-Flags ..... | 66 | +| 8.4.64 | Type-Of-External-Identifier ..... | 67 | + +| | | | +|------------------------------------------------------------------------------|---------------------------------------------|-----------| +| 8.4.65 | APN-Validity-Time ..... | 67 | +| 8.4.66 | Suggested-Network-Configuration ..... | 67 | +| 8.4.67 | Monitoring-Event-Report-Status ..... | 68 | +| 8.4.68 | PLMN-ID-Requested ..... | 68 | +| 8.4.69 | AdditionalIdentifiers ..... | 69 | +| 8.4.70 | NIR-Flags ..... | 69 | +| 8.4.71 | Reporting-Time-Stamp ..... | 69 | +| 8.4.72 | NIA-Flags ..... | 69 | +| 8.4.73 | Group-User-Identifier ..... | 69 | +| 8.4.74 | MTC-Provider-Info ..... | 70 | +| 8.4.75 | MTC-Provider-ID ..... | 70 | +| 8.4.76 | PDN-Connectivity-Status-Configuration ..... | 70 | +| 8.4.77 | PDN-Connectivity-Status-Report ..... | 70 | +| 8.4.78 | PDN-Connectivity-Status-Type ..... | 71 | +| 8.4.79 | Traffic-Profile ..... | 71 | +| 8.4.80 | Updated-Network-Configuration ..... | 72 | +| 8.4.81 | Battery-Indicator ..... | 72 | +| 8.4.82 | SCEF-Reference-ID-Ext ..... | 73 | +| 8.4.83 | SCEF-Reference-ID-for-Deletion-Ext ..... | 73 | +| Annex A (normative): Diameter overload control mechanism ..... | | 73 | +| A.1 | General ..... | 73 | +| A.2 | S6m interface ..... | 73 | +| A.2.1 | General ..... | 73 | +| A.2.2 | HSS behaviour ..... | 73 | +| A.2.3 | MTC-IWF behaviour ..... | 74 | +| A.3 | S6t interface ..... | 74 | +| A.3.1 | General ..... | 74 | +| A.3.2 | HSS behaviour ..... | 74 | +| A.3.3 | SCEF behaviour ..... | 74 | +| Annex B (Informative): Diameter overload control node behaviour ..... | | 74 | +| B.1 | Introduction ..... | 74 | +| B.2 | Message prioritisation over S6m ..... | 74 | +| B.3 | Message prioritisation over S6t ..... | 75 | +| Annex C (normative): Diameter message priority mechanism ..... | | 75 | +| C.1 | General ..... | 75 | +| C.2 | S6m, S6n, S6t interfaces ..... | 75 | +| Annex D (normative): Diameter load control mechanism ..... | | 76 | +| D.1 | General ..... | 76 | +| D.2 | S6m interface ..... | 76 | +| D.2.1 | General ..... | 76 | +| D.2.2 | HSS behaviour ..... | 76 | +| D.2.3 | MTC-IWF behaviour ..... | 77 | +| D.3 | S6t interface ..... | 77 | +| D.3.1 | General ..... | 77 | +| D.3.2 | HSS behaviour ..... | 77 | +| D.3.3 | SCEF behaviour ..... | 77 | +| Annex E (informative): Change history ..... | | 78 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document describes the Diameter-based interfaces between the HSS and other network elements involved in the architecture for interworking with packet data networks and applications, such as Machine-Type Communications (MTC). + +In particular, this document specifies the S6m interface between the Home Subscriber Server (HSS) and the MTC Interworking Function (MTC-IWF), the S6n interface between the HSS and the MTC-AAA and the S6t interface between the HSS and the Service Capability Exposure Function (SCEF). The procedures over those interfaces are defined in 3GPP TS 23.682 [2]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [3] Void. +- [4] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security". +- [5] IETF RFC 4960: "Stream Control Transport Protocol". +- [6] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message Elements". +- [7] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; protocol details ". +- [8] 3GPP TS 29.173: "Diameter-based SLh interface for Control Plane LCS". +- [9] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF". +- [10] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol". +- [11] 3GPP TS 23.003: "Numbering, addressing and identification". +- [12] 3GPP TS 29.338: "Diameter based protocols to support SMS capable MMEs". + +- [13] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)". +- [14] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [15] IETF RFC 7683 : "Diameter Overload Indication Conveyance". +- [16] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". +- [17] 3GPP TS 29.217: "Congestion Reporting Over Np Reference Point". +- [18] IETF RFC 5777: "Traffic Classification and Quality of Service (QoS) Attributes for Diameter". +- [19] 3GPP TS 23.007: "Restoration procedures". +- [20] IETF RFC 7944: "Diameter Routing Message Priority". +- [21] IETF RFC 5778: "Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction". +- [22] IETF RFC 8583: "Diameter Load Information Conveyance". +- [23] IETF RFC 6733: "Diameter Base Protocol". +- [24] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications". +- [25] 3GPP TS 29.154: "Service capability exposure functionality over Nt Reference point". +- [26] 3GPP TS 29.122: "T8 reference point for Northbound APIs". + +# 3 Definitions, symbols and abbreviations + +## 3.1 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]. + +| | | +|---------|----------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| ABNF | Augmented Backus-Naur Form | +| AVP | Attribute-Value Pair | +| DRMP | Diameter Routing Message Priority | +| DSCP | Differentiated Services Code Point | +| IANA | Internet Assigned Numbers Authority | +| MTC | Machine-Type Communications | +| MTC-IWF | MTC Interworking Function | +| NIDD | Non-IP Data Delivery | +| SCS | Services Capability Server | +| SCEF | Service Capability Exposure Function | + +# 4 General Description + +## 4.1 Introduction + +The S6m reference point between the MTC-IWF and the HSS, the S6n reference point between the MTC-AAA and the HSS, and the S6t reference point between the SCEF and the HSS, are defined in the 3GPP TS 23.682 [2]. + +This document describes the Diameter-based S6m, S6n and S6t related procedures, message parameters and protocol specification. + +An excerpt of the architecture for Machine-Type Communication, as defined in 3GPP TS 23.682 [2] is shown in Figure 4.1-1, where the relevant interfaces towards the HSS are highlighted. + +![Figure 4.1-1: 3GPP Architecture for Machine-Type Communication. The diagram shows the network architecture for Machine-Type Communication (MTC) across Home (HPLMN) and Visited (VPLMN) networks. Key components include MTC-AAA, HSS, MME/SGSN, SCEF, IWK-SCEF, MTC-IWF, SMS-SC/GMSC/IWMSC, and Services Capability Server (SCS). Interfaces S6m, S6n, S6t, S6a/d, T6a/b, T6ai/T6bi, T7, T4, T5a/b/c, and Tsp are shown. The S6m, S6n, and S6t interfaces are highlighted with dashed lines.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +The diagram illustrates the 3GPP architecture for Machine-Type Communication (MTC). It is divided into two main network areas: HPLMN (Home PLMN) and VPLMN (Visited PLMN), separated by a dashed orange line. + +In the HPLMN, the HSS (Home Subscriber Server) is central. It connects to the MTC-AAA via the S6n interface (dashed line). It also connects to the SCEF via the S6t interface (dashed line). The SCEF connects to the MME/SGSN via the T6a/b interface. + +In the VPLMN, the MME/SGSN connects to the IWK-SCEF via the T6ai/T6bi interface. The IWK-SCEF connects to the SCEF via the T7 interface. + +The MTC-IWF (MTC Interworking Function) connects to the HSS via the S6m interface (dashed line). The MTC-IWF also connects to the SMS-SC/GMSC/IWMSC via the T4 interface and to the Services Capability Server (SCS) via the Tsp interface. + +The MSC/MME/SGSN connects to the MTC-IWF via the T5a/b/c interface. + +The diagram highlights the S6m, S6n, and S6t interfaces with dashed lines, indicating their importance in the architecture. + +Figure 4.1-1: 3GPP Architecture for Machine-Type Communication. The diagram shows the network architecture for Machine-Type Communication (MTC) across Home (HPLMN) and Visited (VPLMN) networks. Key components include MTC-AAA, HSS, MME/SGSN, SCEF, IWK-SCEF, MTC-IWF, SMS-SC/GMSC/IWMSC, and Services Capability Server (SCS). Interfaces S6m, S6n, S6t, S6a/d, T6a/b, T6ai/T6bi, T7, T4, T5a/b/c, and Tsp are shown. The S6m, S6n, and S6t interfaces are highlighted with dashed lines. + +**Figure 4.1-1: 3GPP Architecture for Machine-Type Communication** + +In this architecture, the S6m reference point connects the MTC-IWF with the HSS, where the subscription information of the UE (e.g., an MTC device) is stored. This reference point allows the MTC-IWF to retrieve subscription data and to do any necessary mapping between different identities associated to the UE. + +The S6m interface shall allow the MTC-IWF to: + +- retrieve subscription information of the UE from the HSS, +- request routing information from the HSS, i.e. the address of the UE's serving nodes supporting SMS for the UE ; in this context serving nodes of the UE are the MSC or MME but not both, the SGSN, and the IP-SM-GW, +- retrieve the IMSI of the UE, +- retrieve the External Identifier of the UE associated to an Application Port Identifier, +- perform authorization of the Service Capability Server that is requesting to send a device trigger to the UE. + +Additionally, the S6n reference point connects the MTC-AAA with the HSS, and it allows the MTC-AAA to do the mapping of the UE IMSI to the external identifier(s) of the UE. + +The S6t reference point connects the SCEF with the HSS to perform configuration and reporting of Monitoring events, and configuration of AESE Communication Pattern. + +The S6t interface shall allow the SCEF to: + +- configure UE related Monitoring events +- receive reporting of the configured Monitoring events from the HSS +- configure UE related AESE Communication Pattern + +- Authorize the UE for NIDD. + +# --- 5 Diameter-based S6m/S6n Interface + +## 5.1 Introduction + +This clause describes the Diameter-based S6m and S6n interface related procedures and Information elements exchanged between functional entities. + +In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [6]. + +## 5.2 Procedure Descriptions + +### 5.2.1 Subscriber Information Retrieval + +#### 5.2.1.1 General + +This procedure is used between the MTC-IWF and the HSS and between the MTC-AAA and the HSS. + +When the procedure is invoked by the MTC-IWF, it is used: + +- To translate an external identifier, or MSISDN, to the IMSI of the user, +- To retrieve information about the serving entities currently serving a certain user, +- To authorize a certain SCS to request a specific service (e.g. device triggering), +- To retrieve subscription data of the user, associated to the specific service requested by the SCS, +- To retrieve an External Identifier based on IMSI and application port identifier. + +When the procedure is invoked by the MTC-AAA, it is used: + +- To translate an IMSI to one or more external identifiers of the user. + +This procedure is mapped to the commands Subscriber-Information-Request/Answer in the Diameter application specified in chapter 6. Tables 5.2.1.1/1 and 5.2.1.1/2 detail the involved information elements. + +Table 5.2.1.1/1: Subscriber Information Retrieval (Request) + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (see 6.4.2) | User-Identifier | M | This Information Element shall contain the identity of the UE. This is a grouped AVP containing either an External Identifier, an MSISDN or an IMSI (exactly one, and only one, of those identifiers shall be included in the request). | +| Requested Service (see 6.4.3) | Service-ID | O | This Information Element shall contain the service requested by the SCS. In this release, only the Device Triggering and SMS_MO services are supported.

For S6n (i.e., when the procedure is invoked by the MTC-AAA), this IE is not applicable, and shall be absent. | +| SCS Identity (see 6.4.4) | SCS-Identity | O | This Information Element shall contain the identity of the Service Capability Server that is requesting a service to be applied to a certain UE. When the Service-ID indicates DEVICE_TRIGGER (0) or SMS_MO (1), the SCS-Identity shall be formatted as an E.164 address as described in clause 6.4.4.

For S6n (i.e., when the procedure is invoked by the MTC-AAA), this IE is not applicable, and shall be absent. | +| Service Parameters (see 6.4.5) | Service-Parameters | O | This Information Element shall contain the parameters associated to the requested service by the SCS (identified by the Service-ID AVP). In this release, only parameters associated to Device Triggering via SMS-MT (T4) and parameters associated to SMS_MO are supported.

For Device Triggering via SMS-MT, this AVP may contain: Priority-Indication, SM-RP-SMEA...
For SMS_MO, this parameter may contain: Application-Port Identifier.

For S6n (i.e., when the procedure is invoked by the MTC-AAA), this IE is not applicable, and shall be absent. | +| SIR Flags (see 6.4.10) | SIR-Flags | M | This Information Element shall contain a bit mask. See clause 6.4.10 for the meaning of the bits. | +| Supported Features (See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this Information Element shall contain the list of features supported by the origin host. | + +**Table 5.2.1.1/2: Subscriber Information Retrieval (Response)** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|--------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code /
Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [23]).
Experimental-Result AVP shall be used for S6m/S6n errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| User Identity
(see 6.4.2) | User-Identifier | C | This information element shall contain the User Identity of the UE. This is a grouped AVP containing an External Identifier, an MSISDN, an IMSI, or other service-specific identities (such as an LMSI...).

There may be multiple instances of this IE in the response provided by the HSS.

This IE shall be present only when the Result- Code is DIAMETER_SUCCESS. | +| Service Data
(see 6.4.7) | Service-Data | C | This information element shall contain data related to the requested service and additional data specific to each triggering method.

In this release, only data associated to trigger delivery via SMS-MT (T4) is supported.

This IE shall be present only when the Requested Service IE was included in the request, and the Result- Code is DIAMETER_SUCCESS. | +| Supported Features
(See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 5.2.1.2 Detailed Behaviour of the HSS + +When the Subscriber Information Retrieval request is received from the MTC-IWF, indicated by the S6m/S6n indicator, which shall be set, the HSS shall, in the following order: + +1. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Subscriber Information Retrieval Response. +2. Check whether the requesting/receiving SCS is authorized to request/receive the specified service for the UE. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) in the Subscriber Information Retrieval Response. +3. Check that the requested service (e.g., device trigger) is present and authorized. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE (5511) in the Subscriber Information Retrieval Response. +4. If the requested service is DEVICE\_TRIGGER, check whether the UE is currently registered in any serving node supporting SMS for the UE (MSC or MME which has registered as MSC but not both, SGSN, IP-SM-GW). If the user is not registered in any serving node, the HSS shall answer successfully, but it shall not include any Serving Node or Additional Serving Node(s) in the response; also, it shall indicate to the MTC-IWF that the user is absent, in the Subscriber Information Retrieval Response, by setting the relevant bit in the HSS-Cause IE. + +The HSS shall also check if the UE is known to be not reachable in the registered serving nodes (i.e. check MNRF, MNRG, and UNRF) and if the trigger delivery is requested with "non-priority"; if both are true, the HSS shall answer successfully, but it shall not include any Serving Node or Additional Serving Node(s) in the response, and it shall set the "Absent Subscriber" flag in the HSS-Cause IE. + +5. If the requested service is DEVICE\_TRIGGER, check whether the requested service cannot be delivered according to the user's provisioned teleservices and the user's active barring conditions. If so, the HSS shall answer successfully, but it should not include any Serving Node or Additional Serving Node(s) in the response, and it shall set accordingly the corresponding bits in the HSS-Cause IE (see clause 6.4.9). +6. If the requested service is SMS\_MO, check whether IMSI and Application Port Identifier are present in the request within User-Identifier and Service- Parameters AVPs. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_MISSING\_APPLICATION\_DATA (5598) in the Subscriber Information Retrieval Response. + +If there is an error in any of the above steps then the HSS shall stop processing and shall return the error code specified in the respective step. + +If the HSS cannot fulfil the received request for reasons not stated in the above steps (e.g. due to a database error), it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS. If the requested service is DEVICE\_TRIGGER, the HSS returns the network addresses of the registered serving nodes supporting SMS for the UE (MSC or MME that has registered as MSC but not both and/or SGSN and/or IP-SM-GW), if available (and not marked "not reachable" by MNRF, MNRG, or UNRI, unless priority was indicated) in the HSS, and the IMSI of the subscriber, and the corresponding data needed by the service requested by the SCS; if available, the MSISDN of the user shall also be returned by the HSS, along with the user's IMSI. If the requested service is SMS\_MO, the HSS returns the External-Identifier associated to the Application Port Identifier. + +When the Subscriber Information Retrieval request is received from the MTC-AAA, indicated by the S6m/S6n indicator, which shall be cleared, the HSS shall check: + +- That the User Identity IE is included in the request, and that it contains an IMSI; if other IEs are included in the request, they may be ignored by the HSS. +- Whether the user identified by that IMSI is known in the HSS. + +If it is known, the HSS shall answer successfully and return in the response one or several instances of the User Identity IE, each one containing either an External-Identifier or an MSISDN (if any of these identities are present in the subscriber profile in HSS), or the subscriber's IMSI (if the subscriber does not have any External Identifiers or MSISDNs assigned). + +If it is not known, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Subscriber Information Retrieval Response. + +#### 5.2.1.3 Detailed Behaviour of the MTC-IWF + +When the MTC-IWF sends a Subscriber Information Retrieval request to the HSS, it shall set the S6m/S6n indicator bit in the SIR Flags IE. + +Upon receipt of a successful Subscriber Information Retrieval response for the DEVICE\_TRIGGER service, when multiple serving nodes are returned from HSS, the MTC-IWF should give a higher preference to the serving node included in the "Serving Node" IE, than to those serving nodes included in the list of "Additional Serving Node" IEs. + +Upon receipt of a successful Subscriber Information Retrieval response for the SMS\_MO service, the MTC-IWF shall use the retrieved External-Identifier for communication with the SCS via Tsp. + +#### 5.2.1.4 Detailed Behaviour of the MTC-AAA + +When the MTC-AAA sends a Subscriber Information Retrieval request to the HSS, it shall clear the S6m/S6n indicator bit in the SIR Flags IE. + +The MTC-AAA shall only include the User Identifier IE in the request, and it shall contain only the IMSI of the UE. + +# 6 Protocol Specification + +## 6.1 Introduction + +### 6.1.1 Use of Diameter Base Protocol + +The Diameter base protocol as specified in IETF RFC 6733 [23] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +### 6.1.2 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [4]. + +### 6.1.3 Accounting Functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the S6m interface. + +### 6.1.4 Use of Sessions + +Between the MTC-IWF and the HSS, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol as specified in IETF RFC 6733 [23] includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [23]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +### 6.1.5 Transport Protocol + +Diameter messages over the S6m interface shall make use of SCTP IETF RFC 4960 [5] as transport protocol. + +### 6.1.6 Routing Considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +The S6m reference point is defined as an intra-operator interface so, both MTC-IWF and HSS shall be located in the same network domain/realm. + +If the MTC-IWF knows the address/name of the HSS for a certain user, both the Destination-Realm AVP and the Destination-Host AVP shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by the MTC-IWF. + +Destination-Realm AVP is declared as mandatory in the ABNF for all requests. + +I If the Vendor-Specific-Application-ID AVP is received in any of the commands, it shall be ignored by the receiving node, and it shall not be used for routing purposes. + +### 6.1.7 Advertising Application Support + +The HSS and the MTC-IWF shall advertise support of the Diameter S6m Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [23]. + +### 6.1.8 Diameter Application Identifier + +The S6m/S6n interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the S6m interface application is 16777310 (allocated by IANA). + +### 6.1.9 Use of the Supported-Features AVP + +When new functionality is introduced on the S6m application, it should be defined as optional. If backwards incompatible changes can not be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the S6m application is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [7]. + +When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [7], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +### 6.1.10 User Identity to HSS resolution + +The User identity to HSS resolution mechanism enables the MTC-IWF to find the identity of the HSS that holds the subscription data for the target user when multiple and separately addressable HSSs have been deployed in the home network. The resolution mechanism is not required in networks that utilise a single HSS. + +This User identity to HSS resolution mechanism may rely on routing capabilities provided by Diameter and be implemented in the home operator network within dedicated Diameter Agents (Redirect Agents or Proxy Agents) responsible for determining the HSS identity based on the provided user identity (e.g., external identifiers provided by the MTC-IWF). + +When the Diameter Load Control mechanism is supported (see IETF RFC 8583 [22]), load values from previously received Load AVPs of type HOST may be taken into account when determining the HSS identity. + +NOTE: Alternatives to the user identity to HSS resolution Diameter based implementation are outside the scope of this specification. + +## 6.2 Commands + +### 6.2.1 Introduction + +This clause defines the Command code values and related ABNF for each command described in this specification. + +### 6.2.2 Command-Code values + +This clause defines Command-Code values for the S6m/S6n interface application as allocated by IANA. + +Every command is defined by means of the ABNF syntax IETF RFC 5234 [9], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [23]. When the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [23] shall apply. + +The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node. + +NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with the IETF RFC 6733 [23]. + +The following Command Codes are defined in this specification: + +**Table 6.2.2/1: Command-Code values for S6m/S6n** + +| Command-Name | Abbreviation | Code | Clause | +|--------------------------------|--------------|---------|--------| +| Subscriber-Information-Request | SIR | 8388641 | 6.2.3 | +| Subscriber-Information-Answer | SIA | 8388641 | 6.2.4 | + +For these commands, the Application-ID field shall be set to 16777310 (application identifier of the S6m/S6n interface application, allocated by IANA). + +### 6.2.3 Subscriber-Information-Request (SIR) Command + +The Subscriber-Information-Request (SIR) command, indicated by the Command-Code field set to 8388641 and the "R" bit set in the Command Flags field, is sent from the MTC-IWF to the HSS or from the MTC-AAA to the HSS. + +Message Format: + +``` +< Subscriber-Information-Request > ::= < Diameter Header: 8388641, REQ, PXY, 16777310 > +< Session-Id > +[ DRMP ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +{ User-Identifier } +[ Service-ID ] +[ SCS-Identity ] +[ Service-Parameters ] +{ SIR-Flags } +[ OC-Supported-Features ] +*[ Supported-Features ] +*[ Proxy-Info ] +*[ Route-Record ] +*[ AVP ] +``` + +### 6.2.4 Subscriber-Information-Answer (SIA) Command + +The Subscriber-Information-Answer (SIA) command, indicated by the Command-Code field set to 8388641 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the MTC-IWF or from the HSS to the MTC-AAA. + +Message Format: + +``` +< Subscriber-Information-Answer > ::= < Diameter Header: 8388641, PXY, 16777310 > + < Session-Id > + [ DRMP ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ OC-Supported-Features ] + [ OC-OLR ] + *[ Load ] + *[ Supported-Features ] + *[ User-Identifier ] + [ Service-Data ] + [ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + *[ AVP ] +``` + +## 6.3 Result-Code AVP and Experimental-Result AVP Values + +### 6.3.1 General + +This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification. + +### 6.3.2 Success + +Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter base protocol as specified in IETF RFC 6733 [23] shall be applied. + +### 6.3.3 Permanent Failures + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in Diameter base protocol as specified in IETF RFC 6733 [23] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent. + +#### 6.3.3.1 DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +This result code shall be sent by the HSS to indicate that the user identified by the IMSI, MSISDN, or External-Identifier is unknown. This error code is defined in 3GPP TS 29.229 [7]. + +#### 6.3.3.2 DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) + +This result code shall be sent by the HSS to indicate that the SCS is not allowed to request control plane services for an UE, to the MTC-IWF. + +#### 6.3.3.3 DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE (5511) + +This result code shall be sent by the HSS to indicate that the specific service requested by the SCS is not allowed for an UE, or that it cannot be delivered according to the current subscribed services of the UE. + +## 6.4 AVPs + +### 6.4.1 General + +The following table specifies the Diameter AVPs defined for the S6m/S6n interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415). + +For all AVPs which contain bit masks and are of the type Unsigned32, bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x00000001 should be used. + +**Table 6.4.1/1: S6m/S6n specific Diameter AVPs** + +| Attribute Name | AVP Code | Clause defined | Value Type | AVP Flag rules | | | | May Encr. | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|------------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | | +| IP-SM-GW-Number | 3100 | 6.4.14 | OctetString | M,V | | | | No | +| IP-SM-GW-Name | 3101 | 6.4.15 | DiameterIdentity | M,V | | | | No | +| User-Identifier | 3102 | 6.4.2 | Grouped | M,V | | | | No | +| Service-ID | 3103 | 6.4.3 | Enumerated | M,V | | | | No | +| SCS-Identity | 3104 | 6.4.4 | OctetString | M,V | | | | No | +| Service-Parameters | 3105 | 6.4.5 | Grouped | M,V | | | | No | +| T4-Parameters | 3106 | 6.4.6 | Grouped | M,V | | | | No | +| Service-Data | 3107 | 6.4.7 | Grouped | M,V | | | | No | +| T4-Data | 3108 | 6.4.8 | Grouped | M,V | | | | No | +| HSS-Cause | 3109 | 6.4.9 | Unsigned32 | M,V | | | | No | +| SIR-Flags | 3110 | 6.4.10 | Unsigned32 | M,V | | | | No | +| External-Identifier | 3111 | 6.4.11 | UTF8String | M,V | | | | No | +| IP-SM-GW-Realm | 3112 | 6.4.18 | DiameterIdentity | M,V | | | | No | +| NOTE 1: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [23]. | | | | | | | | | +| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. | | | | | | | | | + +The following table specifies the Diameter AVPs re-used by the S6m/S6n interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within S6m/S6n. + +Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol as specified in IETF RFC 6733 [23], do not need to be supported. The AVPs from Diameter base protocol as specified in IETF RFC 6733 [23] are not included in table 6.4.1/2, but they may be re-used for the S6m/S6n protocol. + +Table 6.4.1/2: S6m/S6n re-used Diameter AVPs + +| Attribute Name | Reference | Comments | +|-----------------------------|---------------------|------------------------------------------------------------------------| +| User-Name | IETF RFC 6733 [23] | This AVP shall contain the IMSI of the UE, in the User-Identifier AVP. | +| MSISDN | 3GPP TS 29.329 [10] | | +| LMSI | 3GPP TS 29.173 [8] | | +| Serving-Node | 3GPP TS 29.173 [8] | see 6.4.12 | +| Additional-Serving-Node | 3GPP TS 29.173 [8] | see 6.4.13 | +| Supported-Features | 3GPP TS 29.229 [7] | | +| Feature-List-ID | 3GPP TS 29.229 [7] | | +| Feature-List | 3GPP TS 29.229 [7] | | +| SM-RP-SMEA | 3GPP TS 29.338 [12] | | +| Priority-Indication | 3GPP TS 29.368 [13] | | +| MME-Number-for-MT-SMS | 3GPP TS 29.272 [14] | | +| OC-Supported-Features | IETF RFC 7683 [15] | See 6.4.16 | +| OC-OLR | IETF RFC 7683 [15] | See 6.4.17 | +| DRMP | IETF RFC 7944 [20] | see clause 6.4.19 | +| Application-Port-Identifier | 3GPP TS 29.368 [13] | | +| Load | IETF RFC 8583 [22] | See 6.4.20 | + +### 6.4.2 User-Identifier + +The User-Identifier AVP is of type Grouped and it contains the different identifiers used by the UE. + +AVP format: + +User-Identifier ::= + +[ User-Name ] + +[ MSISDN ] + +[ External-Identifier ] + +[ LMSI ] + +\*[AVP] + +This AVP shall contain at least one of the identifiers used by the UE, i.e., it shall not be empty. The IMSI of the UE shall be included (when applicable) in the User-Name AVP. + +### 6.4.3 Service-ID + +The Service-ID AVP is of type Enumerated and it shall identify the service requested by the SCS. The following values are defined: + +DEVICE\_TRIGGER (0) + +The SCS requests a control plane device triggering to the UE. . + +SMS\_MO (1) + +The UE (identified by IMSI and application port identifier) requests SMS\_MO to be delivered to the SCS. + +### 6.4.4 SCS-Identity + +The SCS-Identity AVP is of type OctetString and it shall contain the identity of the SCS or UE which originated the service request towards the MTC-IWF, over the Tsp reference point. + +The encoding of the SCS-Identity AVP is defined per SCS service. + +For the device triggering service, the SCS-Identity AVP shall contain the ISDN number of the SCS in international ISDN number format as described in ITU-T Rec E.164 [41]. It shall be encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan. + +### 6.4.5 Service-Parameters + +The Service-Parameters AVP is of type Grouped, and it contains the service-specific parameters related to the requested service. + +AVP format: + +``` +Service-Parameters ::= + [ T4-Parameters ] + [ Application-Port-Identifier ] + *[AVP] +``` + +### 6.4.6 T4-Parameters + +The T4-Parameters AVP is of type Grouped. + +AVP format: + +``` +T4-Parameters ::= + [ Priority-Indication ] + [ SM-RP-SMEA ] + *[AVP] +``` + +### 6.4.7 Service-Data + +The Service-Data AVP is of type Grouped, and it contains the service-specific data related to the device triggering request handled by the MTC-IWF. + +``` +Service-Data ::= + [ T4-Data ] + *[AVP] +``` + +### 6.4.8 T4-Data + +The T4-Data AVP is of type Grouped and it shall contain information about the network node(s) serving the targeted user for SMS, i.e. the names/numbers of the serving nodes (MSC or MME, SGSN, IP-SM-GW) which allow the trigger delivery. AVP format: + +``` +T4-Data ::= + [ HSS-Cause ] + [ Serving-Node ] + *[ Additional-Serving-Node ] + *[AVP] +``` + +When the HSS-Cause indicates Absent Subscriber, via the corresponding flag in the bit mask, the Serving-Node and Additional-Serving-Node AVPs shall not be present. When the HSS-Cause indicates Teleservice Not Provisioned or + +Call Barred, via the corresponding flag in the bit mask, the Serving-Node and Additional-Serving-Node AVPs should not be present. Additional-Serving-Node AVP shall be absent if Serving-Node AVP is absent. + +### 6.4.9 HSS-Cause + +The HSS-Cause AVP is of type Unsigned32 and it contains a bit mask. The meaning of the bits is defined in table 6.4.9/1: + +**Table 6.4.9/1: HSS-Cause** + +| Bit | Name | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Absent Subscriber | This bit, when set, indicates that there is no serving node registered in the HSS over which the corresponding triggering method should be immediately attempted for the user. NOTE 1. | +| 1 | Teleservice Not Provisioned | This bit, when set, indicates that the required teleservice(s) for the corresponding triggering method are not provisioned in the HSS/HLR for the user. | +| 2 | Call Barred | This bit, when set, indicates that the user has an active barring condition which makes it impossible to deliver the corresponding triggering method. | +| NOTE 1: This may be caused because there is not any serving node currently registered in HSS for the user, or because the user is known to be absent in all suitable registered serving nodes (based on MNRF, MNRG and UNRI flags) and the trigger delivery is requested with "non-priority". | | | +| NOTE 2: Bits not defined in this table shall be cleared by the HSS and discarded by the receiving node, MTC-IWF. | | | + +### 6.4.10 SIR-Flags + +The SIR-Flags AVP is of type Unsigned32 and it contains a bit mask. The meaning of the bits is defined in table 6.4.10/1: + +**Table 6.4.10/1: SIR-Flags** + +| bit | name | Description | +|------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | S6m/S6n Indicator | This bit, when set, indicates that the SIR message is sent on the S6m interface, i.e. the source node is an MTC-IWF.
This bit, when cleared, indicates that the SIR message is sent on the S6n interface, i.e. the source node is an MTC-AAA. | +| Note: Bits not defined in this table shall be cleared by the sending node, MTC-IWF or MTC-AAA, and discarded by the receiving HSS. | | | + +### 6.4.11 External-Identifier + +The External-Identifier AVP is of type UTF8String. For S6m/S6n interface it shall contain an external identifier of the UE. See 3GPP TS 23.003 [11] for the definition and formatting of the External Identifier. For S6t interface, it shall contain an external identifier for an individual UE or a group of UEs, as indicated by Type-Of-External-Identifier AVP. See 3GPP TS 23.003 [11] for the definition and formatting of the External Group Identifier. + +### 6.4.12 Serving-Node + +The Serving-Node AVP is of type Grouped and it shall contain the name/number of the serving node to be used for T4-triggering. It is originally defined in 3GPP TS 29.173 [8]. + +Serving-Node ::= + +[ SGSN-Name ] + +[ SGSN-Realm ] + +[ SGSN-Number ] + +[ MME-Name ] + [ MME-Realm ] + [ MME-Number-for-MT-SMS ] + [ MSC-Number ] + [ IP-SM-GW-Number ] + [ IP-SM-GW-Name ] + [ IP-SM-GW-Realm ] + \*[AVP] + +The following combinations are allowed: + +- a) SGSN-Number +- b) SGSN-Name & SGSN-Realm & SGSN-Number if the HSS supports the "Gdd in SGSN" feature and has received the "Gdd in SGSN" indication over S6a or Gr interface from the SGSN (cf. 3GPP TS 29.272 [4] and 3GPP TS 29.002 [9]) +- c) MME-Name & MME-Realm & MME-Number-for-MT-SMS +- d) MSC-Number +- e) MSC-Number & MME-Name & MME-Realm +- f) IP-SM-GW-Number +- g) IP-SM-GW-Number & IP-SM-GW-Name & IP-SM-GW-Realm + +### 6.4.13 Additional-Serving-Node + +The Additional-Serving-Node AVP is of type Grouped and when present it shall contain the name/number of an additional serving node to be used for T4-triggering. It is originally defined in 3GPP TS 29.173 [8], + +Additional-Serving-Node ::= + +[ SGSN-Name ] + [ SGSN-Realm ] + [ SGSN-Number ] + [ MME-Name ] + [ MME-Realm ] + [ MME-Number-for-MT-SMS ] + [ MSC-Number ] + \*[AVP] + +The following combinations are allowed: + +- a) SGSN-Number +- b) SGSN-Name & SGSN-Realm & SGSN-Number if the HSS supports the "Gdd in SGSN" feature and has received the "Gdd in SGSN" indication over S6a or Gr interface from the SGSN (cf. 3GPP TS 29.272 [4] and 3GPP TS 29.002 [9]) +- c) MME-Name & MME-Realm & MME-Number-for-MT-SMS + +d) MSC-Number + +e) MSC-Number & MME-Name & MME-Realm + +### 6.4.14 IP-SM-GW-Number + +The IP-SM-GW-Number AVP is of type OctetString and it shall contain the ISDN number of the IP-SM-GW in international number format as described in ITU-T Rec E.164 [41]. It shall be encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan. + +### 6.4.15 IP-SM-GW-Name + +The IP-SM-GW-Name AVP is of type DiameterIdentity and it shall contain the Diameter identity of the registered IP-SM-GW. For further details on the encoding of this AVP, see IETF RFC 3588 [5]. + +### 6.4.16 OC-Supported-Features + +The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [15]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information. + +### 6.4.17 OC-OLR + +The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [15]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information. + +### 6.4.18 IP-SM-GW-Realm + +The IP-SM-GW-Realm AVP is of type DiameterIdentity and it shall contain the Diameter identity of the registered IP-SM-GW's realm. For further details on the encoding of this AVP, see IETF RFC 3588 [5]. + +### 6.4.19 DRMP + +The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [20]. This AVP allows the HSS and the MTC-IWF over the S6m interface and the HSS and the MTC-AAA over the S6n interface to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message. + +### 6.4.20 Load + +The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [22]. This AVP is used to support the Diameter load control mechanism. + +# --- 7 Diameter-based S6t Interface + +## 7.1 Introduction + +This clause describes the Diameter-based S6t interface related procedures and Information elements exchanged between functional entities. + +In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [6]. + +## 7.2 Procedure Descriptions + +### 7.2.1 Configuration Information on S6t + +#### 7.2.1.1 General + +This procedure is used between the SCEF and the HSS for: + +- the configuration/deletion of Monitoring events for a UE or a Group of UEs; +- the configuration/deletion of Communication Patterns; +- the configuration/query of Enhanced Coverage Restrictions; +- the configuration of Network Configuration parameters; +- the translation of an External Group Identifier(s) to IMSI Group Id(s). + +The following events may be configured for monitoring: + +- Association of the UE and UICC and/or new IMSI-IMEI-SV association; +- UE reachability; +- Location of the UE, and change in location of the UE; +- Loss of connectivity; +- Communication failure; +- Roaming status (i.e. Roaming or No Roaming, identity of the PLMN serving the UE) of the UE, and change in roaming status of the UE; +- Availability after DDN failure; +- Idle Status Indication in addition to UE reachability or Availability after DDN failure; +- PDN Connectivity Status. + +This procedure is mapped to the commands Configuration-Information-Request/Answer in the Diameter application specified in clause 8. The tables 7.2.1.1-1 and 7.2.1.1-2 detail the involved information elements. + +Table 7.2.1.1-1: Configuration Information Request + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------------|---------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity
(see 6.4.2) | User-Identifier | M | This Information Element shall contain the identity of the UE or the identity of a group of UEs. This is a grouped AVP containing either an External Identifier or an MSISDN (exactly one, and only one, of those identifiers shall be included in the request).
When requesting event monitoring configuration for a group of UEs, and when requesting translation from External Group Identifier to IMSI Group ID, the SCEF shall include the External Group Identifier (see 3GPP TS 23.003 [11]) in the External-Identifier AVP. | +| Group Reporting Guard Timer (See 8.4.59) | Group-Reporting-Guard-Timer | C | If present, this Information Element indicates that the collected Status Indications and/or reports for UEs belonging to a group shall be reported no later than at the interval indicated by the Group Reporting Guard Timer.
Shall be present if the User-Identifier contains an External Group Identifier. | +| Supported Features
(See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this Information Element shall contain the list of features supported by the origin host. | +| Monitoring Event Configuration
(see 8.4.2) | Monitoring-Event-Configuration | O | If present, this Information Element shall contain the details of Monitoring event(s). Multiple instances covering different monitoring events may be present. | +| AESE Communication Pattern
(see 8.4.25) | AESE-Communication-Pattern | O | If present, this Information Element shall contain the details of Communication Pattern(s). Multiple instances covering different communication patterns may be present. | +| CIR-Flags
(see 8.4.39) | CIR-Flags | O | If present, this Information Element shall contain a bit mask. See 8.4.39 for the meaning of the bits. | +| Enhanced Coverage Restriction
(see 8.4.51) | Enhanced-Coverage-Restriction | O | If present, this Information Element shall contain the updates of the Enhanced Coverage Restriction. | +| Suggested Network Configuration
(see 8.4.66) | Suggested-Network-Configuration | O | If present, this Information Element shall contain the suggested network configuration. | +| Additional Identifiers
(see 8.4.69) | AdditionalIdentifiers | C | If the request is used to retrieve multiple IMSI Group IDs for multiple External Group Identifiers, this information element shall be present and shall contain all the External Group Identifiers for which the IMSI Group IDs are requested, except the one conveyed in the User-Identifier AVP. | + +Table 7.2.1.1-2: Configuration Information Answer + +| Information Element Name | Mapping to Diameter AVP | Cat | Description | +|----------------------------------------------------------|------------------------------------------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code /
Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [23]).
Experimental-Result AVP shall only be used for S6t errors which are applicable regardless of the services requested (e.g. DIAMETER_ERROR_USER_UNKNOWN). This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
Otherwise, this IE shall reflect the outcome of the procedure at Diameter base protocol level and Result-Code AVP shall be used. | +| User Identity
(see 6.4.2) | User-Identifier | C | This information element shall contain the User Identity of the UE. This is a grouped AVP containing an External Identifier or an MSISDN for a UE.
This IE shall not be present if the External-Identifier of User-Identifier in CIR message contains the identity of a Group of UEs (i.e. External Group Identifier).
This IE shall be present only when the Result-Code is DIAMETER_SUCCESS. | +| Number of UEs
(See 3GPP TS 29.154 [25]) | Number-of-UEs | C | This IE shall contain the number of UEs belonging to the group of UEs.
This IE shall be present if the External-Identifier of User-Identifier in CIR message contains the identity of a Group of UEs (i.e. External Group Identifier). | +| Supported Features
(See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Monitoring Event Report
(see 8.4.3) | Monitoring-Event-Report | O | If an immediate report is available this information element shall contain the requested data available in the HSS. | +| AESE Communication Pattern Config Status
(see 8.4.32) | AESE-Communication-Pattern-Config-Status | O | If present, this Information Element shall contain the details of Communication Pattern-Config-Status (s). Multiple instances covering different communication patterns configuration statuses may be present. | +| Monitoring Event-Config Status
(see 8.4.24) | Monitoring-Event-Config-Status | C | This IE shall be present if Monitoring Event Configuration IE is included in CIR and if the Result-Code AVP in Configuration Information Answer is DIAMETER_SUCCESS. Multiple instances of this IE may be present; they shall contain the configuration status for all monitoring event configurations that were requested. | +| Supported Services
(see 8.4.40) | Supported-Services | O | If present, this Information Element shall contain AVPs indicating details of the services supported by the HSS and authorized for the requesting SCEF.

This Information Element may additionally contain AVPs with the services supported by the serving node(s), if they are known to the HSS. | +| S6t-HSS Cause
(see 8.4.50) | S6t-HSS-Cause | C | This information element shall contain an indication of Absent Subscriber. It shall be present if the user is not registered in any serving node. | +| Enhanced Coverage Restriction Data
(see 8.4.52) | Enhanced-Coverage-Restriction-Data | C | This information element shall contain the result of a status query for Enhanced Coverage restriction control. It shall be present if the request contained a CIR-Flag AVP with the bit for Enhanced-Coverage-Query set. | +| CIA-Flags
(see 8.4.60) | CIA-Flags | O | If present, this Information Element shall contain a bit mask. See 8.4.60 for the meaning of the bits. | + +| | | | | +|-------------------------------------------|---------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Active Network Configuration (see 8.4.66) | Suggested-Network-Configuration | O | If present, this Information Element shall contain the parameters which are active in the HSS. | +| IMSI Group Id (See 3GPP TS 29.272 [14]) | IMSI-Group-Id | C | This information element shall be present if the CIR-Flag for IMSI Group Retrieval was set in the request and the Result-Code is DIAMETER_SUCCESS. | + +In the following clauses (7.2.1.2 and 7.2.1.3), if the feature "Extended Reference IDs" (see clause 8.4.23.1) is supported by the SCEF and the HSS, the term "SCEF Reference ID" shall refer to the content of the 64-bit long "SCEF-Reference-ID-Ext" AVP, and the term "SCEF Reference ID for Deletion" shall refer to the content of the 64-bit long "SCEF-Reference-ID-for-Deletion-Ext" AVP. + +#### 7.2.1.2 Detailed Behaviour of the HSS + +When the Configuration Information Request is received from the SCEF, the HSS shall, in the following order: + +1. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN (5001) in the Configuration Information Answer. +2. Check whether the requesting SCEF is authorized to request the specified service (e.g. presence of Monitoring Event Configuration AVPs indicates the MONTE service). If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) in the Configuration Information Answer. +- 2a. If the MTC Provider Information is received, check if the MTC Provider ID is authorized for the UE or the group of UEs. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_MTC\_PROVIDER (5516) in the Configuration Information Answer. +3. Check that the requested service (e.g. MONTE, indicated by the presence of Monitoring-Event-Configuration AVPs, or Communication Pattern, indicated by the presence of AESE-Communication-Pattern AVP) is authorized for the UE or the group of UEs. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE (5511) in the Configuration Information Answer. +- 3a. If the request is IMSI Group Id Retrieval (as indicated by the CIR-Flags AVP), the HSS shall return the IMSI Group Id(s) in the order of sequence that corresponds to the order of sequence of the received External Group Identifier(s) received in the User-Identifier AVP and AdditionalIdentifiers AVP. The Result Code shall be set to DIAMETER\_SUCCESS. Stop processing. + +Otherwise, continue to step 4. + +NOTE: Applicable steps 4-8 are performed for each monitoring event type or communication pattern requested. + +4. Check whether the limits on number of monitoring events that can be requested per monitoring type and SCEF-ID is reached. If so, Result-Code in Monitoring-Event-Config-Status for the affected service(s) shall be set to DIAMETER\_RESOURCES\_EXCEEDED (5006). The Result-Code shall be set to DIAMETER\_SUCCESS in the Configuration Information Answer. +- 4a. Check whether the requesting SCEF is authorized to request the specific service configuration(s) (e.g. Monitoring Event Type indicates a specific monitoring event configuration). If not, Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service configuration(s) shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510). The Result-Code shall be set to DIAMETER\_SUCCESS in the Configuration Information Answer. +- 4b. Check that the requested specific service configuration(s) (e.g. Monitoring Event Type) is authorized for the UE or the group of UEs. If not, Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service(s) shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE (5511). The Result-Code shall be set to DIAMETER\_SUCCESS in the Configuration Information Answer. +5. When the request is for a group, i.e. because the External-Identifier AVP of the User-Identifier AVP contain an External Group Identifier, the HSS applies the Monitoring-Event-Configuration AVP to each UE of the Group and includes the CIA-Flags AVP with the Group-Configuration-In-Progress bit set in the Configuration + +Information Answer. The Result-Code shall be set to DIAMETER\_SUCCESS in the Configuration Information Answer. + +6. If a serving node is registered and is involved in the reporting of the configured monitoring event, the HSS shall forward the monitoring event configuration to the serving node and wait for the answer before sending the Configuration Information Answer to the SCEF. The monitoring event configuration status from the serving node for each event shall be conveyed by the HSS to the SCEF. The Result-Code shall be set to DIAMETER\_SUCCESS in the Configuration Information Answer. +7. If the user is not registered in any serving node or the user is purged in the registered serving node(s), the HSS shall store the configuration data related to the service; also, it shall indicate to the SCEF that the user is absent, in the Configuration Information Answer, by setting the relevant bit in the S6t-HSS-Cause IE. The Result-Code shall be set to DIAMETER\_SUCCESS in the Configuration Information Answer. +8. For Monitoring, if the data related to an immediate reporting is available in the HSS, the HSS (e.g. as being received from the MME/SGSN in the Insert Subscriber Data answer) shall include this data in the Configuration Information Answer. For Monitoring events that can be answered by the HSS without requiring interaction with the serving node (e.g. roaming status, IMEI-Change), the HSS shall respond immediately, either in the CIA or in an immediate RIR. + +If the HSS is aware that the UE is registered in an MME and an SGSN and the services supported by the MME and SGSN are different, the HSS shall additionally report the capabilities of the different nodes to the SCEF by including Supported-Services AVP(s) with the subset of services supported by the serving node(s) among those supported by the HSS, as indicated by the Node-Type AVP (e.g. HSS, MME). If the capabilities are the same reported from the MME, the SGSN and the HSS, the HSS shall report the service capabilities without Node-Type to the SCEF. If the Supported-Services of the SGSN and MME are different and the UE is purged in SGSN or MME the HSS shall report the Supported-Services to the SCEF excluding the Supported-Services from the purged node. + +If the HSS receives CIR command from SCEF and has sent IDR commands over S6a/S6d to an MME and an SGSN, the HSS shall check the Result-Codes in Monitoring-Event-Config-Status AVPs reported by the MME and the SGSN: + +- if they are different, the HSS shall include both Service-Report AVPs with the respective Node-Type (indicating the type of serving node) in the Monitoring-Event-Config-Status AVP to the SCEF in the CIA command; +- otherwise, the HSS shall include one Service-Report AVP without Node-Type in the Monitoring-Event-Config-Status AVP to the SCEF in the CIA command. + +If the configuration data in the CIR command are out of the allowed range, the HSS shall set the Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service(s) to DIAMETER\_ERROR\_REQUESTED\_RANGE\_IS\_NOT\_ALLOWED (5512). + +If the received SCEF Reference ID for Deletion does not exist, the HSS shall set the Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service(s) to DIAMETER\_ERROR\_CONFIGURATION\_EVENT\_NON\_EXISTANT (5514). + +If the SCEF Reference ID exists and the old configuration data could not be replaced by new Configuration event data, the HSS shall set the Experimental-Result-Code in Monitoring-Event-Config-Status for the affected service(s) to DIAMETER\_ERROR\_CONFIGURATION\_EVENT\_STORAGE\_NOT\_SUCCESSFUL (5513). + +If the HSS cannot fulfil the received request for reasons not stated in the above steps (e.g. due to a database error), it shall stop processing the request and set Result-Code in Configuration Information Answer to DIAMETER\_UNABLE\_TO\_COMPLY. + +If the HSS detects that configuration data provided by a Monitoring-Event-Configuration are overwritten by a CIR command and both configurations were initiated by the same SCEF, the HSS shall include in the CIA command the Monitoring Event Report AVP including the SCEF Reference ID and SCEF Reference ID for Deletion of the overwritten configuration data. + +If the HSS needs to report loss of connectivity it shall include the Monitoring-Type AVP set to "LOSS\_OF\_CONNECTIVITY" in the Monitoring Event Report. In addition, the HSS may also include the Loss-Of-Connectivity-Reason AVP in the Monitoring Event Report. + +For the "CHANGE\_OF\_IMSI\_IMEI(SV)\_ASSOCIATION" event type, if there was no previous IMEI(SV) information stored in the HSS, and a new IMEI(SV) is received from the MME/SGSN, this is equivalent to a change of IMEI(SV) and the corresponding event shall be reported, by setting the "IMEI" flag (bit 0) in the IMEI-Change AVP, as described in clause 8.4.22. + +For the "ROAMING\_STATUS" event type, if there was no previous roaming status information stored in the HSS, and a certain PLMN ID value is received from the MME/SGSN, this is equivalent to a change of roaming status and the corresponding event shall be reported. + +If the SCEF indicates the support of Monitoring event feature to the HSS and the HSS supports Monitoring. The HSS shall include the Supported-Services AVP with the Supported-Monitoring-Events AVP indicating the authorized monitoring events for the requesting SCEF in the CIA command. + +If CIR message includes multiple SCEF Reference ID and one, several or all SCEF Reference ID Monitoring events cannot be handled, or fail to be configured at the registered serving node(s), the HSS shall report all SCEF Reference ID requested to the SCEF with an appropriate Experimental-Result-Code or Result-Code in the Monitoring-Event-Config-Status AVP(s). + +NOTE: In order to avoid reattempts from the SCS/AS when some configuration failed at the serving node(s), based on operator's choice, the HSS can still store the configuration data, return a successful response to SCEF and report the SCEF with monitoring event(s) suspended. The configuration data can then be forwarded whenever traffic is received from MME/SGSN and event(s) can be reported to SCEF as resumed, as described in chapter 7.2.2. + +If a CIR message includes multiple SCEF Reference ID and for a SCEF Reference ID at least one CP parameter set cannot be handled, the HSS shall reply within the AESE-Communication-Pattern-Config-Status all SCEF Reference ID requested to the SCEF with an appropriate Experimental-Result-Code or Result-Code. + +If an SCEF Reference ID received in a CIR command match with an SCEF Reference ID stored in the HSS and both SCEF Reference ID are provided by the same SCEF ID, the HSS shall delete the stored CP sets associated with the SCEF reference Id and store the new CP set(s). + +If the CIR message contains combinations of monitoring events and CP parameter set it shall handle each set belonging to an SCEF Reference ID separately and shall send a combined answer to the SCEF with all SCEF Reference IDs requested. + +If the SCEF Reference ID for Deletion is present, the receiving node shall delete the corresponding configuration, if stored. + +If the SCEF Reference ID is present, the receiving node shall store the configuration event. + +IF the CIR message contains the CIR-Flags with delete all monitoring events, the HSS shall delete all Monitoring events configured by the SCEF for the subscriber. This includes forwarding the deletion to involved serving nodes. In this case the CIR message shall not contain new monitoring events. + +If the CIR message contains the CIR-Flags with delete all communication pattern, and the feature Config-Eff-CP is supported, the HSS shall delete all Communication Pattern configured by the SCEF for the subscriber. This includes forwarding the deletion to involved serving nodes. In this case the CIR message shall not contain new communication pattern. + +If the CIR message contains the CIR-Flags with delete all network parameter configurations, and the feature Config-Eff-NP is supported, the HSS shall delete all Suggested Network Configurations configured by the SCEF for the subscriber. This includes the updating of involved serving nodes. In this case the CIR message shall not contain new network parameter configurations. + +If the CIR command contains the CIR-Flags AVP with the bit for Enhanced Coverage Query set, the HSS shall return the current settings of Enhanced Coverage together with the current Serving PLMN-ID (if any) in the CIA command. + +If the CIR command contains Enhanced-Coverage-Restriction AVP, the HSS shall update the subscription data for Enhanced Coverage; the update shall be a complete replacement of any stored information with the received information. This may result in the need to update the MME/SGSN via S6a/d/MAP-Gr with the new value for access restriction; there is however no need for the HSS to delay sending of CIA until updates of serving nodes are confirmed. + +If the CIR command contains Suggested-Network-Configuration AVP to update a previous Suggested Network Configuration (i.e. the SCEF Reference ID matches with an SCEF Reference ID stored in the HSS and both SCEF Reference IDs are provided by the same SCEF ID), the HSS shall check whether the suggested parameters are acceptable, and if so, update the stored UE's subscription parameters accordingly. The update shall be a complete replacement of any stored information with the received information. This may result in Insert Subscriber Data Signalling towards the UE's serving node. If the HSS modifies parameters received in Suggested-Network-Configuration AVP, the HSS shall inform the SCEF about the active parameters. When the HSS did not modify + +parameters received in the Suggested-Network-Configuration AVP, the HSS shall return a Suggested-Network-Configuration AVP to the SCEF in CIA containing only SCEF Reference ID and SCEF-ID. + +If a Monitoring-Event-Report is included in a CIA command and the Monitoring-Event-Report is related to a One-time Monitoring event request, the HSS shall delete the related Monitoring event for the UE or the individual group member UE locally after sending the Monitoring-Event-Report. + +If the subscribed periodic RAU/TAU Timer, Active Time, Suggested number of downlink packets, or any combination was previously set by a different SCEF requests including the Monitoring-Event-Configuration AVP(s) or Suggested-Network-Configuration AVP identified by a different SCEF Reference ID for the same UE, the HSS shall accept the request as follows: + +- If the newly received the value of the Maximum-Detection-Time AVP or the Maximum-Latency AVP within the Monitoring-Event-Configuration AVP(s) or the value of the Subscribed-Periodic-RAU-TAU-Timer AVP within the Suggested-Network-Configuration AVP is lower than the provided subscribed periodic RAU/TAU timer, the HSS shall set the subscribed periodic RAU/TAU timer using the newly received value. +- If the newly received the value of Maximum-Response-Time AVP within the Monitoring-Event-Configuration AVP(s) or the value of the Active-Time AVP within the Suggested-Network-Configuration AVP is higher than the provided subscribed Active Time (i.e. previously provided Maximum Response Time), the HSS shall set the subscribed Active Time using the newly received value. +- If the DL-Buffering-Suggested-Packet-Count AVP is newly received within the Monitoring-Event-Configuration AVP(s) or Suggested-Network-Configuration AVP, the HSS shall set the subscribed Suggested number of downlink packets by adding the newly received value to the currently used value of Suggested number of downlink packets if the aggregated value is within the operator defined range. If the aggregated value is not within the operator defined range, the HSS shall set the subscribed Suggested number of downlink packets according to operator defined range. + +#### 7.2.1.3 Detailed Behaviour of the SCEF + +When the SCEF receives Monitoring-Event-Report AVP from the HSS in CIA command, it shall handle it according to the procedures defined in 3GPP TS 23.682 [2]. + +When the SCEF receives an AESE-Communication-Pattern-Config-Status AVP from the HSS in a CIA command, it shall handle it according to the procedures defined in 3GPP TS 23.682 [2]. If the SCEF has included a number of CP pattern sets with several SCEF reference IDs in the request, it shall handle each AESE-Communication-Pattern-Config-Status AVP separately according to the procedures defined in 3GPP TS 23.682 [2]. + +If the SCEF receives Supported-Services AVP(s), it shall only trigger those services which are supported and authorized by the HSS and the MME/SGSN. + +The SCEF shall store the Supported-Services received from the HSS and modify them, if the HSS reports change of capabilities. + +NOTE: It depends on SCEF implementation, if the SCEF triggers only those services which are supported in both nodes when the UE is registered in both the MME and the SGSN. + +When the SCEF needs to query the current settings of Enhanced Coverage Restriction, it shall send a CIR command to the HSS with the corresponding bit in the CIR-Flags AVP set, unless the SCEF knows that Enhanced Coverage Restriction Control is not supported by the HSS. + +When the SCEF needs to update the current settings of Enhanced Coverage Restriction, it shall send a CIR command to the HSS with the new values for Enhanced Coverage Restriction within the Enhanced-Coverage-Restriction AVP. + +The SCEF shall not query and update the current settings of Enhanced Coverage Restriction by means of a single CIR command. + +When the SCEF receives Suggested-Network-Configuration AVP from the HSS in CIA command, it shall handle it according to the procedures defined in 3GPP TS 23.682 [2]. Absence of Suggested-Network-Configuration AVP from CIA - while it was present in CIR - indicates that the HSS does not support and has ignored the Suggested-Network-Configuration received in CIR. + +### 7.2.2 Reporting on S6t + +#### 7.2.2.1 General + +This procedure is used between the HSS and the SCEF. + +When the procedure is invoked by the HSS, it is used for reporting: + +- The change of association of the UE and UICC and/or new IMSI-IMEI-SV; +- The UE reachability for SMS; +- The Roaming status (Roaming or No Roaming) of the UE, and change in roaming status of the UE. + +It is also used: + +- To update the SCEF with the suspend/resume/cancel status of an ongoing monitoring. +- To update the SCEF with information about removal of Communication Pattern. +- To convey reports and/or status indications and/or network parameter configurations for all or some UEs belonging to a group. +- To update the SCEF about changes in previously accepted Network Parameter Configuration(s) due to a new CIR command. + +This procedure is mapped to the commands Reporting-Information-Request/Answer in the Diameter application specified in clause 8. The tables 7.2.2.1-1 and 7.2.2.1-2 detail the involved information elements. + +Table 7.2.2.1-1: Reporting Information Request + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (see 8.4.36) | User-Identifier | C |

If present, this information element shall contain the User Identity of the UE. This is a grouped AVP containing an External Identifier and/or an MSISDN. This AVP shall not carry the IMSI towards the SCEF.

For group based configuration processing, the External-Identifier shall be present and contain an External Group Identifier (see 3GPP TS 23.003 [11]).

For reports associated to individual UEs (i.e. not associated to a group member UE), this information element may be absent.

For individual UE reports and/or status indications, if the Monitoring-Event-Report(s) with the pertaining SCEF-Reference-Id(s) are present, they uniquely identify the monitoring event(s) reported, regardless of the presence of the User-Identifier.

| +| Supported Features (See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Monitoring Event Report (see 8.4.3) | Monitoring-Event-Report | O | If a report is available in the HSS this information element shall contain the requested data available in the HSS. | +| Group Report (see 8.4.61) | Group-Report | C |

If present, this information element shall contain reports and/or status indications and/or Network Parameter Configurations for all UEs or a subset of UEs belonging to a group.

Shall be present if User-Identifier contains an External Group Identifier

| +| RIR-Flags (see 8.4.63) | RIR-Flags | O | If present, this Information Element shall contain a bit mask. See 8.4.63 for the meaning of the bits. | +| Supported Services (see 8.4.40) | Supported-Services | C |

If present, this Information Element shall contain AVPs indicating details of the services supported by the HSS and authorized for the SCEF.

This Information Element may additionally contain AVPs with the services supported by the serving node(s), if there has been a change of capabilities in MME/SGSN.

If RIR-flags indicates a change of SCEF authorization for one or more monitoring events, this information element shall be present.

| + +Table 7.2.2.1-2: Reporting Information Answer + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 6.3) | Result-Code / Experimental-Result | M |

Result of the request.

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

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

| +| Supported Features (See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Monitoring Event Report Status | Monitoring-Event-Report-Status | O | If present, this information element shall contain the status of each individual monitoring event report received by the SCEF from the HSS. | + +In the following clauses (7.2.2.2 and 7.2.2.3), if the feature "Extended Reference IDs" (see clause 8.4.23.1) is supported by the SCEF and the HSS, the term "SCEF Reference ID" shall refer to the content of the 64-bit long "SCEF-Reference- + +ID-Ext" AVP, and the term "SCEF Reference ID for Deletion" shall refer to the content of the 64-bit long "SCEF-Reference-ID-for-Deletion-Ext" AVP. + +#### 7.2.2.2 Detailed Behaviour of the HSS + +For group-based configuration processing, if the Group Guard Timer was included in the CIR command, the HSS shall send the RIR command before the Group Guard Timer expires and shall include several reports and/or status indications in one or more Group Report AVPs. + +NOTE: The HSS may divide the accumulated Monitoring Configuration Indications/immediate reports into multiple messages. + +The HSS shall send immediate reports and/or status indications (for Monitoring Event Configurations) and/or Network Parameter Configurations (for Suggested Network Configurations) for group-based configuration processing using the Group-Report. + +If the HSS knows that it has additional RIR commands to send for the same group, the HSS shall include the RIR-Flags AVP with the Group-Configuration-In-Progress bit set and restart the Group Guard Timer to the value it originally received in the CIR. + +For group based configuration processing, if the MME/SGSN previously indicated that it does not support the External-Identifier in the ULR command and the UE does not have an MSISDN configured as part of its subscription data, the HSS shall indicate that the UE is absent by setting the relevant bit in the S6t-HSS-Cause IE of the Group Report-Item AVP. + +If the HSS detects that configuration data provided by a Monitoring-Event-Configuration are overwritten by a new CIR command and the configurations were initiated by different SCEFs, the HSS shall initiate an RIR command and include a Monitoring-Event-Report AVP including the SCEF Reference ID and SCEF Reference ID for Deletion of the overwritten configuration data. + +If the HSS updates a previously accepted Network Parameter Configuration(s), e.g. Active Time is updated due to several SCS/AS suggesting different values for the same network parameter(s) for the same UE (see 3GPP TS 23.682 [2], clause 5.6.1.4), the HSS may initiate a RIR command providing the SCEF Reference ID of the previous Network Parameter Configurations and include the Updated-Network-Configuration AVP including only those parameter configuration(s) which have been updated and are being applied in the network. + +If the HSS detects that suggested network configuration data provided by a Configuration Information Request are overwritten by a new CIR command and the configurations were initiated by different SCEFs, the HSS shall initiate an RIR command and include a Monitoring-Event-Report AVP including the SCEF Reference ID and SCEF Reference ID for Deletion of the overwritten configuration data. + +If the Monitoring-Event-Report is related to a One-time Monitoring event request, the HSS shall delete the related Monitoring event for the UE or the individual group member UE locally after sending the Monitoring-Event-Report. This HSS response will be performed immediately when the event does not involve direct interaction with the serving node. If UE Reachability is reported, a Maximum-UE-Availability-Time AVP may also be present in the report. + +If the HSS detects that the serving node does not support or does not activate (as indicated in IDA or NOR commands) a Monitoring event, or if the UE is part of a group and requires the External-Identifier to be supported by the serving node when it does not, it shall send to the SCEF, an RIR command with the Event-Handling AVP with the value SUSPEND. + +If an HSS detects that in the new serving node an event to be activated is supported which was not supported in the old serving node or if the HSS detects that the new serving node supports the External-Identifier for a UE that is part of a group and requires the External-Identifier which was not supported in the old serving node, it shall send an RIR command with the Event-handling AVP with the value RESUME to the SCEF. + +If the HSS receives a Notify Request from the MME/SGSN to inform the Monitoring-Event-Config-Status at the IWK-SCEF, the HSS shall send an RIR command to the SCEF, for the monitoring event configurations not accepted by the IWK-SCEF, with the Event-Handling AVP set to the value CANCEL. + +If the HSS receives a Notify Request from the MME/SGSN to inform that monitoring event configuration(s) no longer exist in the SCEF (DIAMETER\_ERROR\_SCEF\_REFERENCE\_ID\_UNKNOWN in Monitoring-Event-Config-Status), the HSS shall locally delete the monitoring event configuration(s) and shall skip the sending of a RIR command to the SCEF. + +If the HSS receives the DIAMETER\_ERROR\_SCEF\_REFERENCE\_ID\_UNKNOWN within an RIA command, it shall delete the event stored for the indicated SCEF Reference ID (see 3GPP TS 23.007 [19]). + +If the Supported-Services of the SGSN and/or MME have been previously reported to the SCEF, and the HSS detects that they have changed from a previous report, the HSS shall report all the Supported-Services AVP(s) to the SCEF with the corresponding Node-Type AVP (e.g. HSS, MME). If the services supported and authorized by the HSS are the same than those supported by the serving node(s), the Node-Type AVP shall be absent. + +If a subscriber is barred/un-barred for services relevant to an active monitoring, the HSS shall send an RIR command to the SCEF with the Event-Handling AVP set to the value SUSPEND/RESUME. + +NOTE: When there is an HSS-initiated detach (e.g. due to MM interaction) or when the subscriber is purged in registered serving node(s) while monitoring is active, the sending of a RIR command to the SCEF is not needed since it is assumed that any SCS/AS requiring to be notified when this event is detected has configured monitoring event Loss of connectivity as specified in 3GPP TS 23.682 [2], clause 5.6.8.2. + +If authorization for one or more events is granted or revoked for an SCEF and the Report-Eff-MONTE is supported by HSS and SCEF, the HSS shall send RIR command with RIR-flags indicating that authorization has changed for one or more events. The Supported-Monitoring-Events AVP shall indicate the authorized or revoked authorization for each event. + +When a subscriber is deleted from the HSS while monitoring is active or the authorization for monitoring is revoked, if Report-Eff-MONTE feature is not supported by SCEF or HSS, the HSS shall send an RIR command to the SCEF with the Event-Handling AVP set to the value CANCEL. If the HSS and SCEF support the Report-Eff-MONTE feature, the HSS shall make use of RIR-flags AVP for a given User-Identity and no Monitoring-Event-Report AVP(s) shall be included. + +When a subscriber is deleted from the HSS or the authorization for communication pattern is revoked while communication pattern are configured, and the Config-Eff-CP feature is supported by SCEF and HSS, the HSS shall make use of the RIR-flag "All-Communication-Pattern-Cancelled" to indicate removal of Communication Pattern for a given User-Identity. + +#### 7.2.2.3 Detailed Behaviour of the SCEF + +When the SCEF receives a Reporting Information Request from the HSS, and at least one of the received Monitoring Event Reports has a SCEF-Reference-ID not known by the SCEF, it shall reply with DIAMETER\_ERROR\_SCEF\_REFERENCE\_ID\_UNKNOWN (see 3GPP TS 23.007 [19]). In that case, if the HSS had included multiple Monitoring Event Reports in the RIR command, the SCEF shall include in the Reporting Information Answer command a list of Monitoring-Event-Report-Status AVPs where the status of multiple monitoring event reports is detailed. In that AVP list, the AVPs corresponding to event reports with a successful status may be omitted by the SCEF, for efficiency. + +Otherwise when the SCEF receives a Reporting Information Request from the HSS, the SCEF shall set Experimental-Result to DIAMETER\_SUCCESS in the Reporting Information Answer and shall handle it according to the procedures defined in 3GPP TS 23.682 [2]. + +If the SCEF receives RIR command with the Event-Handling AVP set to SUSPEND it shall either notify the SCS/AS that the event is not active or initiate deletion of the event depending on operator configuration. + +If the SCEF receives a RIR command with the Event-Handling AVP set to CANCEL it shall delete the event. + +If the SCEF supports Report-Eff-MONTE feature and receives a RIR command with RIR-flags indicating that its authorization has changed for one or more events, it shall consider all events indicated in Supported-Monitoring-Events AVP as cancelled and shall delete the events for all associated UEs. + +**Editor's Note:** The usage of Retry-After timer is FFS. + +If the SCEF receives RIR command with the Event-Handling AVP set to RESUME it shall notify the SCS/AS that the event is activated in serving node. + +If the SCEF receives a Reporting Information Request from the HSS with the Monitoring-Type AVP set to LOSS\_OF\_CONNECTIVITY, it shall interpret this as the reporting of loss of connectivity of the UE. + +If the monitoring is not for One-time monitoring request (i.e. Maximum Number of Reports was configured with a value higher than one), on receiving Monitoring event reports for a Continuous Monitoring Request for an individual UE, the SCEF shall check whether the number of reports for this Monitoring event type reaches the configured maximum number of reports. When the reports reach the configured maximum number, the SCEF shall send CIR message to the HSS to delete the corresponding Monitoring Event Configuration for an individual UE, with the SCEF Reference ID for Deletion set to the related SCEF Reference ID. + +NOTE: For One-Time report, the HSS/MME/SGSN/SCEF will locally delete the event after the first report is received at the SCEF. For continuous monitoring, the HSS/MME/SGSN, as an implementation option, can delete the monitoring event if it is ensured that the SCEF has received the configured maximum number of reports (if present) for the associated event type, regardless of the Monitoring Duration. However, the CIR message to delete the corresponding Monitoring Event Configuration is always required to ensure network consistency. + +On receiving Monitoring event reports for a One-Time event for a group of UEs (i.e. External Group Identifier), the SCEF shall check whether it has received the reports for all individual group member UEs for this Monitoring event by using the total number of individual group member UE(s) (e.g. External Identifier or MSISDN) received in the reports and the number of UEs originally received within the Number-of-UEs AVP from the HSS. When the reports for all individual group member UEs have been received, the SCEF shall determine that reporting for this group is complete and send the CIR message to the HSS to delete the corresponding Monitoring Event Configuration, with the SCEF Reference ID for Deletion set to the related SCEF Reference ID. + +On receiving Monitoring event reports for a Continuous Monitoring Request for a group of UEs (i.e. External Group Identifier), the SCEF shall check whether the reports of each individual group member UE have reached the configured maximum number of reports by using the total number of individual group member UE(s) (e.g. External Identifier or MSISDN) received in the reports and the number of UEs originally within the Number-of-UEs AVP from the HSS. When reports of each individual group member UE have reached the configured maximum number of reports, the SCEF shall determine that reporting for this group is complete and send the CIR message to the HSS to delete the corresponding Monitoring Event Configuration, with the SCEF Reference ID for Deletion set to the related SCEF Reference ID. + +If the HSS reports change of Supported-Services, the SCEF shall replace the stored Supported-Service by the received ones. The SCEF shall only trigger those services which are supported and authorized by the HSS and the MME/SGSN. + +If the SCEF receives the RIR command with the Group-Configuration-In-Progress bit of the RIR-Flags AVP set, the SCEF shall restart the associated Group Reporting Guard Timer. + +NOTE: The SCEF needs to be prepared to receive RIR for Group based configuration processing before the Group Reporting Group Timer expires. + +If the SCEF receives a Monitoring Event Report AVP with the SCEF Reference ID for Deletion, it shall initiate cancellation of the Monitoring event identified by the SCEF Reference ID for Deletion in the Monitoring Event Report AVP. + +### 7.2.3 NIDD Information on S6t + +#### 7.2.3.1 General + +This procedure is used between the SCEF and the HSS for: + +- the authorization of the UE or group of UEs for NIDD. + +This procedure is used between the HSS and the SCEF for: + +- the update/revocation of a UE's authorization for NIDD, +- sending of group user identifier list segments. + +This procedure is mapped to the commands NIDD-Information-Request/Answer in the Diameter application specified in clause 8. The tables 7.2.3.1-1 and 7.2.3.1-2 detail the involved information elements. + +Table 7.2.3.1-1: NIDD Information Request + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|----------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (see 8.4.36) | User-Identifier | M | This Information Element shall contain the identity of the UE or the identity of a group of UEs. This is a grouped AVP containing either an IMSI, External Identifier or an MSISDN (exactly one, and only one, of those identifiers shall be included in the request).
When the request is for a group of UEs, the SCEF shall include the External Group Identifier (see 3GPP TS 23.003 [11]) in the External-Identifier AVP. | +| Supported Features (See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this Information Element shall contain the list of features supported by the origin host. | +| NIDD Authorization Request (see 8.4.44) | NIDD-Authorization-Request | O | If present, this Information Element shall contain the details of Authorization for NIDD.
When sent by the SCEF, the Service-Selection AVP inside NIDD-Authorization-Request shall be present, and it shall contain the APN for which NIDD authorization is requested.
Shall be absent when sent by the HSS. | +| NIDD Authorization Update (see 8.4.57) | NIDD-Authorization-Update | O | If present, this Information Element shall contain the details of the updated NIDD Authorization.
Shall be absent when sent by the SCEF. | +| NIR Flags | NIR-Flags | O | If present, this Information Element shall contain a bit mask. See 8.4.70 for the meaning of the bits. | +| Group User Identifier List | Group-User-Identifier | C | This information element shall be present if the request is sent from HSS to SCEF following a previous NIA with an incomplete Group User Identifier List. | +| MTC Provider Info | MTC-Provider-Info | O | If present, it contains the identity of the MTC Service Provider and/or MTC Application (see 3GPP TS 23.682 [2], clause 5.6). | + +Table 7.2.3.1-2: NIDD Information Answer + +| Information Element Name | Mapping to Diameter AVP | Cat | Description | +|---------------------------------------------|-----------------------------------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 6.3) | Result-Code / Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [23]).
Experimental-Result AVP shall be used for S6t errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
This AVP reflects the outcome of the procedure on Diameter level. | +| Supported Features (See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| NIDD-Authorization-Response (see 8.4.45) | NIDD-Authorization-Response | C | If present, this Information Element shall contain the details of NIDD Authorization. When sent by the HSS the IE shall only be present when the Result Code is DIAMETER_SUCCESS.
Shall be absent when sent by the SCEF. | +| Group User Identifier List | Group-User-Identifier | C | This information element shall be present if the request was for a group of UEs and the Result-Code is DIAMETER_SUCCESS.
It shall contain for each UE of the group the External-Identifier/MSISDN and IMSI. | +| NIA Flags | NIA-Flags | O | If present, this Information Element shall contain a bit mask. See 8.4.72 for the meaning of the bits. | + +#### 7.2.3.2 Detailed Behaviour of the HSS + +When the NIDD Information Request is received from the SCEF, the HSS shall, in the following order: + +1. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the NIDD Information Answer. +2. Check that the requested service is authorized for the UE. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE (5511) in the NIDD Information Answer. +- 2a. If the MTC Provider Information is received, check if the MTC Provider ID is authorized for the UE or the group of UEs. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_MTC\_PROVIDER (5516) in the NIDD Information Answer. +3. Check that the APN sent in the Service-Selection AVP of the NIDD-Authorization-Request AVP is subscribed for the subscriber identified by the given MSISDN or the External Identifier. If it is not subscribed, then the Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_NO\_APN\_SUBSCRIPTION (5451) in the NIDD Information Answer. +4. If the User-Identifier contains an External Identifier, the HSS shall include the IMSI and if available the MSISDN associated with the appropriate External Identifier in the NIDD-Authorization-Response. +5. If the User-Identifier contains an MSISDN, the HSS shall include the IMSI and if available, the appropriate External Identifier associated with the MSISDN in the NIDD-Authorization-Response. +6. If the User-Identifier contains an IMSI the HSS shall include the MSISDN and the appropriate External Identifier assigned to the IMSI in the NIDD-Authorization-Response. +- 6a. If the User-Identifier contains an External Group Identifier, the HSS shall include the IMSI and the MSISDN or External-Identifier assigned to each member of the group in the Group-User-Identifier. If due to message size constraints or timing constraints (NIA timeout) the complete list of group user identifier cannot be sent, the HSS shall segment the list, include the first segment in NIA and set the NIA-Flag "Incomplete Group User Identifier List", and send subsequent segments with separate NIR commands to the SCEF. +7. If the requested service is NIDD Authorization request and the feature "NIDD Authorization Update" is commonly supported by HSS and SCEF, the HSS shall store the granted NIDD Authorization in order to being able to update/revoke the Authorization towards the SCEF when so needed. The HSS may indicate within the NIDD-Authorization-Response AVP a granted validity time which shall not be later than the requested validity time as received within the NIDD-Authorization-Request AVP (if any). If so the HSS shall delete the stored Authorization at the indicated point in time. + +NOTE 1: If several External Identifiers are mapped to one IMSI, some functions might not work in this release of the specification. + +NOTE 2: Step 6 above is applicable for the case where the SCEF receives a T6a/b-CMR (see 3GPP TS 29.128 [24]) command while a valid NIDD configuration does not exist for the UE at the SCEF. + +If there is an error in any of the above steps then the HSS shall stop processing and return the error code specified in the respective step. + +If the HSS cannot fulfil the received request for reasons not stated in the above steps (e.g. due to a database error), it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. Otherwise the Result-Code shall be set to DIAMETER\_SUCCESS. + +When the need to update/revoke one or several stored granted NIDD Authorizations for a user is detected in the HSS, and the feature "NIDD Authorization Update" is commonly supported by the HSS and the SCEF, the HSS shall issue an NIDD-Information Request command containing a NIDD-Authorization-Update AVP towards the SCEF. The NIDD-Authorization-Update AVP may identify several granted NIDD Authorizations for the user to be updated. + +#### 7.2.3.3 Detailed Behaviour of the SCEF + +When the SCEF receives an NIDD-Authorization-Response AVP from the HSS in a NIA command, it shall handle it according to the procedures defined in 3GPP TS 23.682 [2]. If the feature "NIDD Authorization Update" is commonly + +supported by the HSS and the SCEF, and a granted validity time was received within the NIDD-Authorization-Response, the SCEF shall consider the authorization being implicitly revoked at the indicated time, and may issue a new NIDD Authorization request towards the HSS. + +# --- 8 Protocol Specification for S6t + +## 8.1 Introduction + +### 8.1.1 Use of Diameter Base Protocol + +The Diameter base protocol as specified in IETF RFC 6733 [23] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +### 8.1.2 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [4]. + +### 8.1.3 Accounting Functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the S6t interface. + +### 8.1.4 Use of Sessions + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [23]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +### 8.1.5 Transport Protocol + +Diameter messages over the S6t interface shall make use of SCTP IETF RFC 4960 [5] as transport protocol. + +### 8.1.6 Routing Considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +If the SCEF knows the address/name of the HSS for a certain user, both the Destination-Realm AVP and the Destination-Host AVP shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by the SCEF. + +As the HSS knows the address/name and the associated home network domain name of the SCEF to which it sends RIR and NIR commands from a previously received CIR command, both the Destination-Realm and Destination-Host AVPs shall be present in request commands sent by the HSS to the SCEF. + +Destination-Realm AVP is declared as mandatory in the ABNF for all requests. + +If the Vendor-Specific-Application-ID AVP is received in any of the commands, it may be ignored by the receiving node, and it shall not be used for routing purposes. + +### 8.1.7 Advertising Application Support + +The HSS and the SCEF shall advertise support of the Diameter S6t Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [23]. + +### 8.1.8 Diameter Application Identifier + +The S6t interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the S6t interface application is 16777345 (allocated by IANA). + +### 8.1.9 Use of the Supported-Features AVP + +When new functionality is introduced on the S6t application, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the S6t application is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [7]. + +When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [7], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +### 8.1.10 User Identity to HSS resolution + +The User identity to HSS resolution mechanism enables the SCEF to find the identity of the HSS that holds the subscription data for the target user when multiple and separately addressable HSSs have been deployed in the home network. The resolution mechanism is not required in networks that utilise a single HSS. + +This User identity to HSS resolution mechanism may rely on routing capabilities provided by Diameter and be implemented in the home operator network within dedicated Diameter Agents (Redirect Agents or Proxy Agents) responsible for determining the HSS identity based on the provided user identity (e.g. external identifiers provided by the SCEF). + +When the Diameter Load Control mechanism is supported (see IETF RFC 8583 [22]), load values from previously received Load AVPs of type HOST may be taken into account when determining the HSS identity. + +NOTE: Alternatives to the user identity to HSS resolution Diameter based implementation are outside the scope of this specification. + +## 8.2 Commands + +### 8.2.1 Introduction + +This clause defines the Command code values and related ABNF for each command described in this specification. + +### 8.2.2 Command-Code values + +This clause defines Command-Code values for the S6t interface application as allocated by IANA. + +Every command is defined by means of the ABNF syntax IETF RFC 5234 [9], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [23]. When the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [23] shall apply. + +The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node. + +NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with the IETF RFC 6733 [23]. + +The following Command Codes are defined in this specification for S6t: + +**Table 8.2.2-1: Command-Code values for S6t** + +| Command-Name | Abbreviation | Code | Clause | +|-----------------------------------|--------------|---------|--------| +| Configuration-Information-Request | CIR | 8388718 | 8.2.3 | +| Configuration-Information-Answer | CIA | 8388718 | 8.2.4 | +| Reporting-Information-Request | RIR | 8388719 | 8.2.5 | +| Reporting-Information-Answer | RIA | 8388719 | 8.2.6 | +| NIDD-Information-Request | NIR | 8388726 | 8.2.7 | +| NIDD-Information-Answer | NIA | 8388726 | 8.2.8 | + +For these commands, the Application-ID field shall be set to 16777345 (application identifier of the S6t interface application, allocated by IANA). + +### 8.2.3 Configuration Information Request (CIR) Command + +The Configuration Information Request (CIR) command, indicated by the Command-Code field set to 8388718 and the "R" bit set in the Command Flags field, is sent from the SCEF to the HSS. + +Message Format: + +``` +< Configuration-Information-Request > ::= < Diameter Header: 8388718, REQ, PXY, 16777345 > +< Session-Id > +[ DRMP ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +{ User-Identifier } +[ OC-Supported-Features ] +*[ Supported-Features ] +*[ Monitoring-Event-Configuration ] +[ CIR-Flags ] +*[ AESE-Communication-Pattern ] +[ Enhanced-Coverage-Restriction ] +``` + +``` + +[ Group-Reporting-Guard-Timer ] +[ AdditionalIdentifiers ] +*[ Proxy-Info ] +*[ Route-Record ] +[ Suggested-Network-Configuration ] +*[AVP] + +``` + +### 8.2.4 Configuration-Information-Answer (CIA) Command + +The Configuration-Information-Answer (CIA) command, indicated by the Command-Code field set to 8388718 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the SCEF. + +Message Format: + +``` + +< Configuration-Information-Answer > ::= < Diameter Header: 8388718, PXY, 16777345 > +< Session-Id > +[ DRMP ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ OC-Supported-Features ] +[ OC-OLR ] +*[ Load ] +*[ Supported-Features ] +[ User-Identifier ] +[ Number-of-UEs ] +*[ Monitoring-Event-Report ] +*[ Monitoring-Event-Config-Status ] +*[ AESE-Communication-Pattern-Config-Status ] +*[ Supported-Services ] +[ S6t-HSS-Cause ] +[ Enhanced-Coverage-Restriction-Data ] +[ CIA-Flags ] +*[ IMSI-Group-Id ] +[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +[ Suggested-Network-Configuration ] +*[AVP] + +``` + +### 8.2.5 Reporting-Information-Request (RIR) Command + +The Reporting-Information-Request (RIR) command, indicated by the Command-Code field set to 8388719 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the SCEF. + +Message Format: + +``` + +< Reporting-Information-Request > ::= < Diameter Header: 8388719, PXY, 16777345 > +< Session-Id > +[ DRMP ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +{ Destination-Host } +{ Destination-Realm } +*[ Supported-Features ] +[ User-Identifier ] +*[ Monitoring-Event-Report ] +*[ Group-Report ] +[ Updated-Network-Configuration ] +[ RIR-Flags ] + +``` + +``` + +*[ Supported-Services ] +*[ Proxy-Info ] +*[ Route-Record ] +*[AVP] + +``` + +### 8.2.6 Reporting-Information-Answer (RIA) Command + +The Reporting-Information-Answer (RIA) command, indicated by the Command-Code field set to 8388719 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the SCEF. + +Message Format: + +``` + +< Reporting-Information-Answer > ::= < Diameter Header: 8388719, PXY, 16777345 > +< Session-Id > +[ DRMP ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +*[ Supported-Features ] +*[ Monitoring-Event-Report-Status ] +[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +*[AVP] + +``` + +### 8.2.7 NIDD Information Request (NIR) Command + +The NIDD Information Request (NIR) command, indicated by the Command-Code field set to 8388726 and the "R" bit set in the Command Flags field, is sent from the SCEF to the HSS. It may also be sent from the HSS to the SCEF when the feature "NIDD Authorization Update" is commonly supported by the HSS and the SCEF. + +Message Format: + +``` + +< NIDD-Information-Request > ::= < Diameter Header: 8388726, REQ, PXY, 16777345 > +< Session-Id > +[ DRMP ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +{ User-Identifier } +[ OC-Supported-Features ] +*[ Supported-Features ] +[ NIDD-Authorization-Request ] +[ NIDD-Authorization-Update ] +[ NIR-Flags ] +*[ Group-User-Identifier ] +[ MTC-Provider-Info ] +*[ Proxy-Info ] +*[ Route-Record ] +*[AVP] + +``` + +### 8.2.8 NIDD-Information-Answer (NIA) Command + +The NIDD-Information-Answer (NIA) command, indicated by the Command-Code field set to 8388726 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the SCEF. It may also be sent from the SCEF to the HSS when the feature "NIDD Authorization Update" is commonly supported by the HSS and the SCEF. + +Message Format: + +``` + +< NIDD-Information-Answer > ::= < Diameter Header: 8388726, PXY, 16777345 > + < Session-Id > + [ DRMP ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ OC-Supported-Features ] + [ OC-OLR ] + *[ Load ] + *[ Supported-Features ] + [ NIDD-Authorization-Response ] + *[ Group-User-Identifier ] + [ NIA-Flags ] + [ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + *[AVP] + +``` + +## 8.3 Result-Code AVP and Experimental-Result AVP Values + +### 8.3.1 General + +This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification. + +### 8.3.2 Success + +Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [23] shall be applied. + +### 8.3.3 Permanent Failures + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [23] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent. + +#### 8.3.3.1 DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +This result code shall be sent by the HSS to indicate that the user identified by the IMSI, MSISDN, or External-Identifier is unknown. This error code is defined in 3GPP TS 29.229 [7]. + +#### 8.3.3.2 DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) + +This result code shall be sent by the HSS to indicate that the SCEF is not allowed to request the service. + +#### 8.3.3.3 DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE (5511) + +This result code shall be sent by the HSS to indicate that the specific service requested by the SCEF is not allowed for an UE, or that it cannot be delivered according to the current subscribed services of the UE. + +#### 8.3.3.4 DIAMETER\_ERROR\_REQUESTED\_RANGE\_IS\_NOT\_ALLOWED (5512) + +This result code shall be sent by the HSS to indicate that the specific service requested by the SCEF is not allowed for an UE, or that it cannot be delivered according to the current subscribed services of the UE. + +#### 8.3.3.5 DIAMETER\_ERROR\_CONFIGURATION\_EVENT\_STORAGE\_NOT\_SUCCESSFUL (5513) + +This result code shall be sent by the HSS to indicate that the specific service requested by the SCEF could not be stored for an UE. + +#### 8.3.3.6 DIAMETER\_ERROR\_CONFIGURATION\_EVENT\_NON\_EXISTANT (5514) + +This result code shall be sent by the HSS to indicate that the requested deletion by the SCEF could not be performed for an UE because the event does not exist. + +#### 8.3.3.7 DIAMETER\_ERROR\_USER\_NO\_APN\_SUBSCRIPTION (5451) + +This result code shall be sent by the HSS to indicate that the APN is not authorized for an UE. + +#### 8.3.3.8 DIAMETER\_ERROR\_UNAUTHORIZED\_MTC\_PROVIDER (5516) + +This result code shall be sent by the HSS to indicate that the MTC provider is not allowed to request the service. + +## 8.4 AVPs + +### 8.4.1 General + +The following table specifies the Diameter AVPs defined for the S6t interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415). + +For all AVPs which contain bit masks and are of the type Unsigned32, bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x00000001 should be used. + +Table 8.4.1-1: S6t specific Diameter AVPs + +| Attribute Name | AVP Code | Clause defined | Value Type | AVP Flag rules | | | | | +|------------------------------------------|----------|----------------|------------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| AESE-Communication-Pattern | 3113 | 8.4.25 | Grouped | M,V | | | | No | +| Communication-Pattern-Set | 3114 | 8.4.26 | Grouped | M,V | | | | No | +| Periodic-Communication-Indicator | 3115 | 8.4.27 | Unsigned32 | M,V | | | | No | +| Communication-Duration-Time | 3116 | 8.4.28 | Unsigned32 | M,V | | | | No | +| Periodic-time | 3117 | 8.4.29 | Unsigned32 | M,V | | | | No | +| Scheduled-Communication-Time | 3118 | 8.4.30 | Grouped | M,V | | | | No | +| Stationary-Indication | 3119 | 8.4.31 | Unsigned32 | M,V | | | | No | +| AESE-Communication-Pattern-Config-Status | 3120 | 8.4.32 | Grouped | M,V | | | | No | +| AESE-Error-Report | 3121 | 8.4.33 | Grouped | M,V | | | | No | +| Monitoring-Event-Configuration | 3122 | 8.4.2 | Grouped | M,V | | | | No | +| Monitoring-Event-Report | 3123 | 8.4.3 | Grouped | M,V | | | | No | +| SCEF-Reference-ID | 3124 | 8.4.4 | Unsigned32 | M,V | | | | No | +| SCEF-ID | 3125 | 8.4.5 | DiameterIdentity | M,V | | | | No | +| SCEF-Reference-ID-for-Deletion | 3126 | 8.4.6 | Unsigned32 | M,V | | | | No | +| Monitoring-Type | 3127 | 8.4.7 | Unsigned32 | M,V | | | | No | +| Maximum-Number-of-Reports | 3128 | 8.4.8 | Unsigned32 | M,V | | | | No | +| UE-Reachability-Configuration | 3129 | 8.4.9 | Grouped | M,V | | | | No | +| Monitoring-Duration | 3130 | 8.4.10 | Time | M,V | | | | No | +| Maximum-Detection-Time | 3131 | 8.4.11 | Unsigned32 | M,V | | | | No | +| Reachability-Type | 3132 | 8.4.12 | Unsigned32 | M,V | | | | No | +| Maximum Latency | 3133 | 8.4.13 | Unsigned32 | M,V | | | | No | +| Maximum Response Time | 3134 | 8.4.14 | Unsigned32 | M,V | | | | No | +| Location-Information-Configuration | 3135 | 8.4.15 | Grouped | M,V | | | | No | +| MONTE-Location-Type | 3136 | 8.4.16 | Unsigned32 | M,V | | | | No | +| Accuracy | 3137 | 8.4.17 | Unsigned32 | M,V | | | | No | +| Association-Type | 3138 | 8.4.18 | Unsigned32 | M,V | | | | No | +| Roaming-Information | 3139 | 8.4.19 | Unsigned32 | M,V | | | | No | +| Reachability-Information | 3140 | 8.4.20 | Unsigned32 | M,V | | | | No | +| IMEI-Change | 3141 | 8.4.22 | Unsigned32 | M,V | | | | No | +| Monitoring-Event-Config-Status | 3142 | 8.4.24 | Grouped | M,V | | | | No | +| Supported-Services | 3143 | 8.4.40 | Grouped | M,V | | | | No | +| Supported-Monitoring-Events | 3144 | 8.4.41 | Unsigned64 | M,V | | | | No | +| CIR-Flags | 3145 | 8.4.39 | Unsigned32 | M,V | | | | No | +| Service-Result | 3146 | 8.4.37 | Grouped | M,V | | | | No | +| Service-Result-Code | 3147 | 8.4.38 | Unsigned32 | M,V | | | | No | +| Reference-ID-Validity-Time | 3148 | 8.4.42 | Time | M,V | | | | No | +| Event-Handling | 3149 | 8.4.43 | Unsigned32 | M,V | | | | No | +| NIDD-Authorization-Request | 3150 | 8.4.44 | Grouped | M,V | | | | No | +| NIDD-Authorization-Response | 3151 | 8.4.45 | Grouped | M,V | | | | No | +| Service-Report | 3152 | 8.4.47 | Grouped | M,V | | | | No | +| Node-Type | 3153 | 8.4.48 | Unsigned32 | M,V | | | | No | +| S6t-HSS-Cause | 3154 | 8.4.50 | Unsigned32 | M,V | | | | No | +| Enhanced-Coverage-Restriction | 3155 | 8.4.51 | Grouped | V | | | M | No | +| Enhanced-Coverage-Restriction-Data | 3156 | 8.4.52 | Grouped | V | | | M | No | +| Restricted-PLMN-List | 3157 | 8.4.53 | Grouped | V | | | M | No | +| Allowed-PLMN-List | 3158 | 8.4.54 | Grouped | V | | | M | No | +| Requested-Validity-Time | 3159 | 8.4.55 | Time | V | | | M | No | +| Granted-Validity-Time | 3160 | 8.4.56 | Time | V | | | M | No | + +| | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|------------|---|--|--|---|----| +| NIDD-Authorization-Update | 3161 | 8.4.57 | Grouped | V | | | M | No | +| Loss-Of-Connectivity-Reason | 3162 | 8.4.58 | Unsigned32 | V | | | M | No | +| Group-Reporting-Guard-Timer | 3163 | 8.4.59 | Unsigned32 | V | | | M | No | +| CIA-Flags | 3164 | 8.4.60 | Unsigned32 | V | | | M | No | +| Group-Report | 3165 | 8.4.61 | Grouped | V | | | M | No | +| Group-Report-Item | 3166 | 8.4.62 | Grouped | V | | | M | No | +| RIR-Flags | 3167 | 8.4.63 | Unsigned32 | V | | | M | No | +| Type-Of-External-Identifier | 3168 | 8.4.64 | Unsigned32 | V | | | M | No | +| APN-Validity-Time | 3169 | 8.4.65 | Grouped | V | | | M | No | +| Suggested-Network-Configuration | 3170 | 8.4.66 | Grouped | V | | | M | No | +| Monitoring-Event-Report-Status | 3171 | 8.4.67 | Grouped | V | | | M | No | +| PLMN-ID-Requested | 3172 | 8.4.68 | Enumerated | V | | | M | No | +| AdditionalIdentifiers | 3173 | 8.4.69 | Grouped | V | | | M | No | +| NIR-Flags | 3174 | 8.4.70 | Unsigned32 | V | | | M | No | +| Reporting-Time-Stamp | 3175 | 8.4.71 | Time | V | | | M | No | +| NIA-Flags | 3176 | 8.4.72 | Unsigned32 | V | | | M | No | +| Group-User-Identifier | 3177 | 8.4.73 | Grouped | V | | | M | No | +| MTC-Provider-Info | 3178 | 8.4.74 | Grouped | V | | | M | No | +| MTC-Provider-ID | 3179 | 8.4.75 | UTF8String | V | | | M | No | +| PDN-Connectivity-Status-Configuration | 3180 | 8.4.76 | Grouped | V | | | M | No | +| PDN-Connectivity-Status-Report | 3181 | 8.4.77 | Grouped | V | | | M | No | +| PDN-Connectivity-Status-Type | 3182 | 8.4.78 | Unsigned32 | V | | | M | No | +| Traffic-Profile | 3183 | 8.4.79 | Unsigned32 | V | | | M | No | +| Updated-Network-Configuration | 3184 | 8.4.80 | Grouped | V | | | M | No | +| Battery-Indicator | 3185 | 8.4.81 | Unsigned32 | V | | | M | No | +| SCEF-Reference-ID-Ext | 3186 | 8.4.82 | Unsigned64 | V | | | M | No | +| SCEF-Reference-ID-for-Deletion-Ext | 3187 | 8.4.83 | Unsigned64 | V | | | M | No | +| NOTE 1: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [23]. | | | | | | | | | +| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. | | | | | | | | | + +The following table specifies the Diameter AVPs re-used by the S6t interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within S6t. + +Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol specified in IETF RFC 6733 [23], do not need to be supported. The AVPs from Diameter base protocol specified in IETF RFC 6733 [23] are not included in table 8.4.1-2, but they may be re-used for the S6t protocol. + +Table 8.4.1-2: S6t re-used Diameter AVPs + +| Attribute Name | Reference | Comments | M-bit | +|-------------------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| User-Identifier | 6.4.2 | see 8.4.36 | | +| External-Identifier | 6.4.11 | | | +| MSISDN | 3GPP TS 29.329 [10] | | | +| User-Name | IETF RFC 6733 [23] | This AVP shall contain the IMSI of the UE | | +| Supported-Features | 3GPP TS 29.229 [7] | see 8.4.23 | | +| Feature-List-ID | 3GPP TS 29.229 [7] | | | +| Feature-List | 3GPP TS 29.229 [7] | | | +| OC-Supported-Features | IETF RFC 7683 [15] | See 6.4.16 | Must not set | +| OC-OLR | IETF RFC 7683 [15] | See 6.4.17 | Must not set | +| Visited PLMN Id | 3GPP TS 29.272 [14] | This Information Element shall contain the identity (MCC and MNC) of the serving PLMN, either the VPLMN or the HPLMN. | | +| Charged-Party | 3GPP TS 32.299 [16] | | | +| EPS-Location-Information | 3GPP TS 29.272 [14] | see 8.4.21 | | +| MME-Location-Information | 3GPP TS 29.272 [14] | see 8.4.34 | | +| SGSN-Location-Information | 3GPP TS 29.272 [14] | see 8.4.35 | | +| E-UTRAN-Cell-Global-Identity | 3GPP TS 29.272 [14] | | | +| Tracking-Area-Identity | 3GPP TS 29.272 [14] | | | +| Current-Location-Retrieved | 3GPP TS 29.272 [14] | | | +| Age-Of-Location-Information | 3GPP TS 29.272 [14] | | | +| User-CSG-Information | 3GPP TS 29.272 [14] | | | +| Cell-Global-Identity | 3GPP TS 29.272 [14] | | | +| Service-Area-Identity | 3GPP TS 29.272 [14] | | | +| Routing-Area-Identity | 3GPP TS 29.272 [14] | | | +| eNodeB-ID | 3GPP TS 29.217 [17] | | | +| Day-Of-Week-Mask | IETF RFC 5777 [18] | | | +| Time-Of-Day-Start | IETF RFC 5777 [18] | | | +| Time-Of-Day-End | IETF RFC 5777 [18] | | | +| DRMP | IETF RFC 7944 [20] | see 8.4.46 | Must not set | +| Service-Selection | IETF RFC 5778 [21] | See 8.4.49 | | +| Load | IETF RFC 8583 [22] | See 6.4.20 | Must not set | +| DL-Buffering-Suggested-Packet-Count | 3GPP TS 29.272 [14] | | | +| Extended-eNodeB-ID | 3GPP TS 29.217 [17] | | Must not set | +| Maximum-UE-Availability-Time | 3GPP TS 29.338 [12] | | | +| Idle-Status-Indication | 3GPP TS 29.128 [24] | | Must not set | +| Active-Time | 3GPP TS 29.128 [24] | When used over S6t, this AVP contains the value of Maximum Response Time (see 3GPP TS 29.122 [26], clause 5.13.2.1.2) which is used to calculate the value of subscribed Active Time as described in 3GPP TS 23.682 [2], clause 4.5.21. | Must not set | +| DL-Buffering-Suggested-Packet-Count | 3GPP TS 29.272 [14] | | Must not set | +| Subscribed-Periodic-RAU-TAU-Timer | 3GPP TS 29.272 [14] | When used over S6t, this AVP contains the value of Maximum Latency (see 3GPP TS 29.122 [26], clause 5.13.2.1.2) which is used to calculate the value of subscribed periodic RAU/TAU timer as described in 3GPP TS 23.682 [2], clause 4.5.21. | Must not set | + +| Attribute Name | Reference | Comments | M-bit | +|--------------------------------|---------------------|----------|--------------| +| IMSI-Group-Id | 3GPP TS 29.272 [14] | | Must not set | +| Number-of-UEs | 3GPP TS 29.154 [25] | | Must not set | +| Terminal-Information | 3GPP TS 29.272 [14] | | Must not set | +| PDN-Type | 3GPP TS 29.272 [14] | | Must not set | +| Non-IP-PDN-Type-Indicator | 3GPP TS 29.272 [14] | | Must not set | +| Non-IP-Data-Delivery-Mechanism | 3GPP TS 29.272 [14] | | Must not set | +| Served-Party-IP-Address | 3GPP TS 32.299 [16] | | Must not set | + +### 8.4.2 Monitoring-Event-Configuration + +The Monitoring-Event-Configuration AVP is of type Grouped, and it contains the details of the monitoring event from the SCEF. At least SCEF-Reference-ID or one SCEF-Reference-ID-for-Deletion shall be present. + +AVP format: + +``` +Monitoring-Event-Configuration ::= + [ SCEF-Reference-ID ] + [ SCEF-Reference-ID-Ext ] + { SCEF-ID } + { Monitoring-Type } + *[ SCEF-Reference-ID-for-Deletion ] + *[ SCEF-Reference-ID-for-Deletion-Ext ] + [ Maximum-Number-of-Reports ] + [ Monitoring-Duration ] + [ Charged-Party ] + [ Maximum-Detection-Time ] + [ UE-Reachability-Configuration ] + [ Location-Information-Configuration ] + [ Association-Type ] + [ DL-Buffering-Suggested-Packet-Count ] + [ PLMN-ID-Requested ] + [ MTC-Provider-Info ] + [ PDN-Connectivity-Status-Configuration ] + *[AVP] +``` + +At least one of the SCEF-Reference-ID or SCEF-Reference-ID-for-Deletion shall be present. + +The Maximum-Number-of-Reports AVP, if present, shall contain the maximum number of event reports to be generated by the HSS, MME, or SGSN until the monitoring event configuration is considered to expire. + +The Monitoring-Duration AVP, if present, shall contain the absolute time at which the monitoring event configuration is considered to expire. + +If both Maximum-Number-of-Reports and Monitoring-Duration AVPs are present, the monitoring event configuration shall be considered to expire as soon as one of the conditions is met. + +If both Maximum-Number-of-Reports and Monitoring-Duration AVPs are absent, the monitoring event configuration shall be considered as a one-time monitoring request (same behaviour as setting Maximum-Number-of-Reports to 1). + +Monitoring-Type shall only be taken into account in combination with SCEF-Reference-ID; Monitoring-Type AVP shall be ignored for deletion of an event (in combination with SCEF-Reference-ID-for-Deletion). + +The details of how to handle expiration of Monitoring events is described in 3GPP TS 23.682 [2]. + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used insted of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively. + +### 8.4.3 Monitoring-Event-Report + +The Monitoring-Event-Report AVP is of type Grouped, and it contains the information to be reported as requested by Monitoring-Event-Configuration. + +AVP format: + +``` +Monitoring-Event-Report ::= + { SCEF-Reference-ID } + [ SCEF-Reference-ID-Ext ] + [ SCEF-ID ] + [ SCEF-Reference-ID-for-Deletion ] + [ SCEF-Reference-ID-for-Deletion-Ext ] + [ Visited-PLMN-Id ] + [ Roaming-Information ] + [ IMEI-Change ] + [ Terminal-Information ] + [ Reachability-Information ] + [ Maximum-UE-Availability-Time ] + [ EPS-Location-Information ] + [ Monitoring-Type ] + [ Event-Handling ] + *[ Service-Report ] + [ Loss-Of-Connectivity-Reason ] + [ Idle-Status-Indication ] + *[ PDN-Connectivity-Status-Report ] + *[AVP] +``` + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used insted of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver. + +### 8.4.4 SCEF-Reference-ID + +The SCEF-Reference-ID AVP is of type Unsigned32 and it shall contain the identifier provided by the SCEF. + +### 8.4.5 SCEF-ID + +The SCEF- ID AVP is of type DiameterIdentity and it shall contain the identity of the SCEF which has originated the service request towards the HSS, i.e. when sent within a Monitoring-Event-Configuration AVP in S6t-CIR, SCEF-ID AVP and Origin-Host AVP shall have the same value. + +### 8.4.6 SCEF-Reference-ID-for-Deletion + +The SCEF-Reference-ID-for-Deletion AVP is of type Unsigned32 and it shall contain the SCEF-Reference-ID (in combination with the SCEF identified by the SCEF-ID) for the event to be deleted. + +### 8.4.7 Monitoring-Type + +The Monitoring-Type AVP is of type Unsigned32 and shall identify the type of event to be monitored. The following values are defined: + +LOSS\_OF\_CONNECTIVITY (0) + +UE\_REACHABILITY (1) + +LOCATION\_REPORTING (2) + +CHANGE\_OF\_IMSI\_IMEI(SV)\_ASSOCIATION (3) + +ROAMING\_STATUS (4) + +COMMUNICATION\_FAILURE (5) + +AVAILABILITY\_AFTER\_DDN\_FAILURE (6) + +NUMBER\_OF\_UES\_PRESENT\_IN\_A\_GEOGRAPHICAL\_AREA (7) + +UE\_REACHABILITY\_AND\_IDLE\_STATUS\_INDICATION (8) + +AVAILABILITY\_AFTER\_DDN\_FAILURE\_AND\_IDLE\_STATUS\_INDICATION (9) + +PDN\_CONNECTIVITY\_STATUS (10) + +### 8.4.8 Maximum-Number-of-Reports + +The Maximum-Number-of-Reports AVP is of type Unsigned32. It shall contain the number of reports to be generated and sent to the SCEF. + +This AVP shall not be present when Monitoring-Type is AVAILABILITY\_AFTER\_DDN\_FAILURE (6). + +This AVP shall not be greater than one if: + +- Monitoring-Type is UE\_REACHABILITY (1) and Reachability-Type is "Reachability for SMS" or +- Monitoring-Type is LOCATION\_REPORTING (2) and MONTE-Location-Type is LAST\_KNOWN\_LOCATION (1). + +### 8.4.9 UE-Reachability-Configuration + +The UE-Reachability-Configuration AVP is of type Grouped, and it shall contain the details for configuration for UE reachability. + +AVP format: + +``` +UE-Reachability-Configuration ::= + [ Reachability-Type ] + [ Maximum-Latency ] + [ Maximum-Response-Time ] + [ DL-Buffering-Suggested-Packet-Count ] + *[AVP] +``` + +### 8.4.10 Monitoring-Duration + +The Monitoring-Duration AVP is of type Time. It shall contain the absolute time at which the related monitoring event request is considered to expire. + +### 8.4.11 Maximum-Detection-Time + +The Maximum-Detection-Time AVP is of type Unsigned32. It shall contain the maximum number of seconds without any communication with the UE after which the SCEF is to be informed that the UE is considered to be unreachable. It is used to set the subscribed periodic RAU/TAU timer by the HSS. + +### 8.4.12 Reachability-Type + +The Reachability-Type AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.12-1: + +**Table 8.4.12-1: Reachability-Type** + +| Bit | Name | Description | +|---------------------------------------------------------------------------------------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------| +| 0 | Reachability for SMS | This bit, when set, indicates that the monitoring for reachability for SMS of the UE is to be configured | +| 1 | Reachability for Data | This bit, when set, indicates that the monitoring for reachability for data of the UE is to be configured | +| NOTE 1: Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | | +| NOTE 2: Bit 0 and 1 shall not be set simultaneously. | | | + +The default value, when this AVP is not included, is Reachability for SMS (bit 0 set). + +### 8.4.13 Maximum-Latency + +The Maximum-Latency AVP is of type Unsigned32. It shall contain the maximum acceptable delay time for downlink data transfer in seconds. It is used to set the subscribed periodic RAU/TAU timer by the HSS. + +### 8.4.14 Maximum-Response-Time + +The Maximum-Response-Time AVP is of type Unsigned32. It shall contain the maximum time in seconds for which the UE stays reachable. It is used to set the active time by the HSS. + +### 8.4.15 Location-Information-Configuration + +The Location-Information-Configuration AVP is of type Grouped, and it contains the details for location reporting. + +AVP format: + +``` +Location-Information-Configuration ::= +``` + +[ MONTE-Location-Type ] +[ Accuracy ] +[ Periodic-Time ] +\*[AVP] + +If present, Periodic-Time contains the minimum periodic location reporting time. + +### 8.4.16 MONTE-Location-Type + +The MONTE-Location-Type AVP is of type Unsigned32. It indicates the type of location information to be provided. The following values are defined: + +CURRENT\_LOCATION (0) +LAST\_KNOWN\_LOCATION (1) + +The default value, when this AVP is not included, is LAST\_KNOWN\_LOCATION (1). + +### 8.4.17 Accuracy + +The Accuracy AVP is of type Unsigned32. It shall indicate the requested accuracy. The following values are defined: + +CGI-ECGI (0) +eNB (1) +LA-TA-RA (2) +PRA(3) +PLMN-ID (4) + +### 8.4.18 Association-Type + +The Association-Type AVP is of type Unsigned32. It shall indicate the details of the event configuration related to the change of IMEI(SV)-IMSI association. The following values are defined: + +IMEI-CHANGE (0) + +The event shall be reported if the association between IMSI and IMEI has changed; if only the Software Version (SV) has changed, no event shall be reported. + +IMEISV-CHANGE (1) + +The event shall be reported if the association between IMSI and IMEI, or SV, or both, has changed (this includes the case where only the SV has changed). + +### 8.4.19 Roaming-Information + +The Roaming-Information AVP is of type Unsigned32. It shall indicate the roaming status of the subscriber. The following values are defined: + +SUBSCRIBER\_ROAMING (0) +SUBSCRIBER\_NOT\_ROAMING (1) + +### 8.4.20 Reachability-Information + +The Reachability-Information AVP is of type Unsigned32. It shall indicate the reachability of the subscriber. The following values are defined: + +REACHABLE\_FOR\_SMS (0) + +REACHABLE\_FOR\_DATA (1) + +### 8.4.21 EPS-Location-Information + +The EPS-Location-Information AVP is of type Grouped. It shall contain the information related to the user location relevant for EPS. It was originally defined in 3GPP TS 29.272 [49]. + +AVP format: + +``` +EPS-Location-Information ::= + [ MME-Location-Information ] + [ SGSN-Location-Information ] + *[AVP] +``` + +### 8.4.22 IMEI-Change + +The IMEI-Change AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.22-1: + +**Table 8.4.22-1: IMEI-Change** + +| Bit | Name | Description | +|---------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| 0 | IMEI | This bit, when set, indicates that the IMEI has changed (regardless of whether the IMEI Software Version has changed or not). | +| 1 | IMEISV | This bit, when set, indicates that only the IMEI Software Version has changed but the IMEI has not changed. | +| NOTE 1: Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | | +| NOTE 2: Bits 0 and 1 shall not be set simultaneously. | | | + +When a change of IMEI(SV) is reported, the new IMEI(SV) values may be reported to the SCEF in the Terminal-Information AVP inside the Monitoring-Event-Report AVP (see clause 8.4.3). + +### 8.4.23 Feature-List AVP + +#### 8.4.23.1 Feature-List AVP for the S6t application + +The syntax of this AVP is defined in 3GPP TS 29.229 [7]. + +For the S6t application, the meaning of the bits shall be as defined in table 8.4.23-1 for the Feature-List-ID. + +Table 8.4.23-1: Features of Feature-List-ID used in S6t + +| Feature bit | Feature | M/O | Description | +|-------------|---------------------------------------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | MONTE | O |

Configuration and reporting of monitoring events

This feature is applicable to from an SCEF with CIR/CIA command pair and the reporting of events to the SCEF with RIR/RIA command pair.

If the HSS does not support this feature, the SCEF shall not send monitoring event configurations to the HSS within CIR.

| +| 1 | AESE-Communication-Pattern | O |

Configuration of CP parameter sets

This feature is applicable to from an SCEF with CIR/CIA command pair.

If the HSS does not support this feature, the SCEF shall not send CP parameter set to the HSS within CIR.

| +| 2 | NIDD-Authorization | O |

Authorization of NIDD

This feature is applicable to from an SCEF with NIR/NIA command pair.

If the HSS indicates in the NIA command that it does not support Authorization of NIDD, the SCEF shall not send NIDD Authorizations requests to the HSS in subsequent NIR commands towards that HSS.

| +| 3 | Enhanced-Coverage-Restriction-Control | O |

Control Of Enhanced Coverage Restriction

This feature is applicable for the CIR/CIA command pair.

If the SCEF detects that the HSS does not support this feature, it may refrain from sending further CIR commands containing an Enhanced-Coverage-Restriction AVP or a CIR-Flags AVP with the bit for Enhanced-Coverage-Query set.

| +| 4 | NIDD Authorization Update | O |

Update/Revocation of NIDD Authorization

This feature is applicable for the NIR/NIA command pair. It shall not be supported when NIDD-Authorization is not supported.

If the SCEF indicates in the NIR command that it does not support NIDD Authorization Update, the HSS shall not send subsequent NIR commands to update or revoke a granted NIDD Authorization. The HSS may decide not to grant NIDD Authorization when Update/Revocation is not supported by the SCEF.

| +| 5 | Report-Eff-MONTE | O |

Reporting Efficiency for MONTE

This feature is applicable for the RIR/RIA command pair.

If the SCEF indicates in the CIR command that it does not support Reporting Efficiency for MONTE, the HSS shall not make use of RIR-flags to indicate the cancellation/removal of all monitoring events nor a change of SCEF authorization for one or more monitoring events.

| +| 6 | Event Cancellation Report | O |

Event Cancellation Report

This feature is applicable to from an SCEF for the CIR/CIA and RIR/RIA command pairs.

If the SCEF does not indicate in the CIR command that it does support Event Cancellation Report, the HSS shall not send a report indicating the cancellation of a report in the CIA or subsequent RIR commands towards that SCEF.

| +| 7 | Config-Eff-CP | O |

Configuration Efficiency for Communication Pattern

This feature is applicable for the CIR/CIA and RIR/RIA command pairs.

If the SCEF indicates in the CIR command that it does not support this feature, the HSS shall not make use of RIR-flags to indicate the removal of all communication pattern.

If the HSS indicates in the CIA command that it does not support this feature, the SCEF shall not set the CIR-flag "Delete All Communication Pattern" in a subsequent CIR command.

| + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8 | Config-Eff-NP | O | Configuration Efficiency for Network Parameter Configuration
This feature is applicable for the CIR/CIA and RIR/RIA command pairs.
If the SCEF indicates in the CIR command that it does not support this feature, the HSS shall not make use of RIR-flags to indicate the removal of all Suggested Network Configuration.
If the HSS indicates in the CIA command that it does not support this feature, the SCEF shall not set the CIR-flag "Delete All Suggested Network Configurations" in a subsequent CIR command. | +| 9 | Extended Reference IDs | O | Extended Reference IDs

This feature is applicable for the CIR/CIA command pair.

If the SCEF detects that the HSS does not support this feature, it shall refrain from sending CIR commands containing 64-bit long SCEF Reference IDs. | +| Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "MONTE".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature. | | | | + +### 8.4.24 Monitoring-Event-Config-Status + +The Monitoring-Event-Config-Status AVP is of type Grouped, and it contains the details of the result of the handling of the Requested action for the Monitoring event. + +AVP format: + +``` +Monitoring-Event-Config-Status ::= + *[ Service-Report ] + { SCEF-Reference-ID } + [ SCEF-Reference-ID-Ext ] + [ SCEF-ID ] + *[AVP] +``` + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext AVP shall be used instead of SCEF-Reference-ID; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver. + +### 8.4.25 AESE-Communication-Pattern + +The AESE-Communication-Pattern AVP is of type Grouped, and it shall contain the details of the Communication-Pattern from the SCEF. + +AVP format + +``` +AESE-Communication-Pattern ::= + [ SCEF-Reference-ID ] + [ SCEF-Reference-ID-Ext ] + { SCEF-ID } + *[ SCEF-Reference-ID-for-Deletion ] + *[ SCEF-Reference-ID-for-Deletion-Ext ] + *[ Communication-Pattern-Set ] +``` + +[ MTC-Provider-Info ] + \*[ AVP ] + +At least one reference ID (either in SCEF-Reference-ID or in SCEF-Reference-ID-Ext) or a reference ID for deletion (either in SCEF-Reference-ID-for-Deletion or in SCEF-Reference-ID-for-Deletion-Ext) shall be present. + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used instead of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively. + +### 8.4.26 Communication-Pattern-Set + +The Communication-Pattern-Set AVP is of type Grouped, and it shall contain a set of Communication-Pattern. + +AVP format + +Communication-Pattern-Set ::= + +[ Periodic-Communication-Indicator ] + [ Communication-Duration-Time ] + [ Periodic-Time ] + \*[ Scheduled-Communication-Time ] + [ Stationary-Indication ] + [ Reference-ID-Validity-Time ] + [ Traffic-Profile ] + [ Battery-Indicator ] + \*[ AVP ] + +Communication-duration-time and Periodic-Time shall be only provided when the Periodic-Communication-Indicator is set to PERIODICALLY. + +If the Reference-ID-Validity-Time AVP is absent, it indicates that there is no expiration time defined for the Communication-Pattern-Set. + +### 8.4.27 Periodic-Communication-Indicator + +The Periodic-communication-indicator AVP is of type Unsigned32. The following values are defined: + +PERIODICALLY (0) + ON\_DEMAND (1) + +### 8.4.28 Communication-duration-time + +The Communication-duration-time AVP is of type Unsigned32 and shall provide the time in seconds of the duration of the periodic communication. + +### 8.4.29 Periodic-time + +Periodic-time AVP is of type Unsigned32 and shall provide the time in seconds of the interval for periodic communication. + +### 8.4.30 Scheduled-communication-time + +The Scheduled-communication-time AVP is of type Grouped. + +AVP format + +``` +Scheduled-communication-time ::= + [ Day-Of-Week-Mask ] + [ Time-Of-Day-Start ] + [ Time-Of-Day-End ] + *[AVP] +``` + +If Day-Of-Week-Mask is not provided this shall be interpreted as every day of the week. + +If Time-Of-Day-Start is not provided, starting time shall be set to start of the day(s) indicated by Day-Of-Week-Mask. + +If Time-Of-Day-End is not provided, ending time is end of the day(s) indicated by Day-Of-Week-Mask. + +### 8.4.31 Stationary indication + +The Stationary-indication AVP are of type Unsigned32. + +``` +STATIONARY_UE (0) +MOBILE_UE (1) +``` + +### 8.4.32 AESE-Communication-Pattern-Config-Status + +The AESE-Communication-Pattern-Config-Status AVP is of type Grouped, and it shall contain the details of the outcome of Communication-Pattern handling from the HSS. + +AVP format + +``` +AESE-Communication-Pattern-Config-Status ::= + { SCEF-Reference-ID } + [ SCEF-Reference-ID-Ext ] + [ SCEF-ID ] + [ AESE-Error-Report ] + *[AVP] +``` + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext AVP shall be used insted of SCEF-Reference-ID; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver. + +### 8.4.33 AESE-Error-Report + +The AESE-Error-Report AVP is of type Grouped, and it contains the details of the Error occurred during handling of the Requested action for the Communication-Pattern-Set. + +AVP format + +``` +AESE-Error-Report ::= +``` + +[ Service-Result ] +\*[AVP] + +### 8.4.34 MME-Location-Information + +The MME-Location-Information AVP is of type Grouped. It shall contain the information related to the user location relevant for the MME. It was originally defined in 3GPP TS 29.272 [49]. + +AVP format + +MME-Location-Information ::= + +[ E-UTRAN-Cell-Global-Identity ] +[ Tracking-Area-Identity ] +[ Current-Location-Retrieved ] +[ Age-Of-Location-Information ] +[ User-CSG-Information ] +[ eNodeB-ID ] +[ Extended-eNodeB-ID ] +\*[AVP] + +### 8.4.35 SGSN-Location-Information + +The SGSN-Location-Information AVP is of type Grouped. It shall contain the information related to the user location relevant for the SGSN. It was originally defined in 3GPP TS 29.272 [49]. + +AVP format + +SGSN-Location-Information ::= + +[ Cell-Global-Identity ] +[ Service-Area-Identity ] +[ Routing-Area-Identity ] +[ Current-Location-Retrieved ] +[ Age-Of-Location-Information ] +[ User-CSG-Information ] +\*[AVP] + +### 8.4.36 User-Identifier + +The User-Identifier AVP is of type Grouped and it contains the different identifiers used by the UE. This AVP is defined in clause 6.4.2. The AVP format for the S6t interface shall be as given below. + +AVP format: + +User-Identifier ::= + +[ User-Name ] +[ MSISDN ] +[ External-Identifier ] + +[ Type-Of-External-Identifier ] + \*[AVP] + +This AVP shall contain one of the identifiers (IMSI, MSISDN or External-Identifier). The IMSI of the UE shall be included (when applicable) in the User-Name AVP. + +The External-Identifier AVP may either contain the identity of an individual UE or the identity of a Group of UEs. The Type-Of-External-Identifier is used to indicate which type of identity is carried in the External-Identifier. When the Type-Of-External-Identifier is not present, it means the External-Identifier AVP contains the identity of an individual UE. + +### 8.4.37 Service-Result + +The Service-Result AVP is of type Grouped, and it contains the Error code identified during the handling of the Requested action for the Monitoring event. + +AVP format: + +Service-Result ::= + [ Vendor-Id ] + [ Service-Result-Code ] + \*[AVP] + +If the Service-Result-Code contains an Experimental-Result-Code value defined by 3GPP, then the Vendor-Id shall be set to the value 10415. If the Service-Result-Code contains a Result-Code value defined in the Diameter base protocol by IETF (see IETF RFC 6733 [23]), then the Vendor-Id shall be absent or set to the value 0. + +### 8.4.38 Service-Result-Code + +The Service-Result-Code AVP is of type Unsigned32. This AVP shall contain either the value of an Experimental-Result-Code defined by 3GPP or the value of a Result-Code defined in Diameter base protocol by IETF (see IETF RFC 6733 [23]). + +### 8.4.39 CIR-Flags + +The CIR-Flags AVP is of type AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.39-1: + +**Table 8.4.39-1: CIR-Flags** + +| Bit | Name | Description | +|-------|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| 0 | Delete all Monitoring events | This bit shall be set if the SCEF wants to delete all Monitoring events for a subscriber stored in the HSS. | +| 1 | Enhanced Coverage Query | This bit shall be set if the SCEF wants to query the current settings of the Enhanced-Coverage-Restriction. | +| 2 | IMSI Group Id retrieval | This bit shall be set if the SCEF wants to retrieve the IMSI Group Id that corresponds to the provided External Group Identifier. | +| 3 | Delete all Communication Pattern | This bit shall be set if the SCEF wants to delete all Communication Pattern for a subscriber stored in the HSS. | +| 4 | Delete all Network Parameter Configurations | This bit shall be set if the SCEF wants to delete all Suggested Network Configuration for a subscriber stored in the HSS. | +| NOTE: | Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | + +### 8.4.40 Supported-Services + +The Supported-Services AVP is of type Grouped and it shall contain the different bit masks representing the services supported by the HSS: + +AVP format + +``` +Supported-Services ::= + [ Supported-Monitoring-Events ] + [ Node-Type ] + *[AVP] +``` + +### 8.4.41 Supported-Monitoring-Events + +The Supported-Monitoring-Events AVP is of type Unsigned64 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.41-1: + +**Table 8.4.41-1: Supported-Monitoring-Events** + +| Bit | Name | Description | +|-------|-------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | UE and UICC and/or new IMSI-IMEI-SV association | This bit shall be set if Monitoring the association of the UE and UICC and/or new IMSI-IMEI-SV association monitoring event is supported in the HSS | +| 1 | UE-reachability | This bit shall be set if UE reachability monitoring event is supported in the HSS/MME/SGSN | +| 2 | Location-of-the-UE | This bit shall be set if Location of the UE and change in location of the UE monitoring event is supported in the HSS/MME/SGSN | +| 3 | Loss-of-connectivity | This bit shall be set if Loss of connectivity monitoring event is supported in the HSS/MME/SGSN | +| 4 | Communication-failure | This bit shall be set if Communication failure monitoring event is supported in the HSS/MME/SGSN | +| 5 | Roaming-status | This bit shall be set if Roaming status (i.e. Roaming or No Roaming) of the UE, and change in roaming status of the UE monitoring event is supported in the HSS | +| 6 | Availability after DDN failure | This bit shall be set if Availability after DDN failure monitoring event is supported in the HSS/MME/SGSN | +| 7 | Idle Status Indication | This bit shall be set if Idle Status Indication monitoring event is supported in the HSS/MME/SGSN in addition to Availability after DDN failure and UE reachability | +| 8 | PDN Connectivity Status | This bit shall be set if PDN Connectivity Status monitoring event is supported in the HSS/MME/SGSN | +| NOTE: | Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | + +Absence of this AVP shall have the same meaning as all bits cleared (i.e. serving node does not support MONTE). + +If RIR-flags is included in Reporting-Information-Request to indicate a change of authorized monitoring events, each bit in Supported-Monitoring-Events AVP, if cleared, shall indicate the SCEF that associated monitoring event is not authorized. + +### 8.4.42 Reference-ID-Validity-Time + +The Reference-ID-Validity-Time AVP is of type Time (see IETF RFC 6733 [23]), and contains the point of time when the CP sets associated to an SCEF-Reference-ID (in combination with an SCEF-ID) becoming invalid and shall be deleted. + +### 8.4.43 Event-Handling + +The Event-handling AVP is of type Unsigned32. The following Values are defined: + +SUSPEND (0) + +RESUME (1) + +CANCEL (2) + +### 8.4.44 NIDD-Authorization-Request + +The NIDD-Authorization-Request AVP is of type Grouped, and it contains the details for the Authorisation of NIDD via the SCEF. + +AVP format: + +``` +NIDD-Authorization-Request ::= + [ Service-Selection ] + [ Requested-Validity-Time ] + *[AVP] +``` + +### 8.4.45 NIDD-Authorization-Response + +The NIDD-Authorization-Response AVP is of type Grouped, and it contains the information to be provided triggered by NIDD-Authorization-Request. + +AVP format: + +``` +NIDD-Authorization-Response ::= + [ MSISDN ] + [ User-Name ] + [ External-Identifier ] + [ Granted-Validity-Time ] + *[AVP] +``` + +The User-Name AVP, when present, shall contain the IMSI. + +### 8.4.46 DRMP + +The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [20]. This AVP allows the HSS and the SCEF over the S6t interface to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message. + +### 8.4.47 Service-Report + +The Service-Report AVP is of type Grouped, and it contains the result of the handling of the Requested action for the Monitoring event, the type of node and the services it supports. + +AVP format: + +``` +Service-Report ::= + [ Service-Result ] + [ Node-Type ] +``` + +\*[AVP] + +### 8.4.48 Node-Type + +The Node-Type AVP is of type Unsigned32 and shall identify the type of node sending the information. The following values are defined: + +- HSS (0) +- MME (1) +- SGSN (2) + +### 8.4.49 Service-Selection + +The Service-Selection AVP is of type of UTF8String. This AVP shall contain the APN Network Identifier (i.e. an APN without the Operator Identifier) per 3GPP TS 23.003 [11], clauses 9.1 & 9.1.1.). + +The contents of the Service-Selection AVP shall be formatted as a character string composed of one or more labels separated by dots ("."). + +This AVP is defined in IETF RFC 5778 [21]. + +### 8.4.50 S6t-HSS-Cause + +The S6t-HSS-Cause AVP is of type Unsigned32 and it contains a bitmask. The meaning of the bits is defined in table 8.4.50-1: + +**Table 8.4.50-1: S6t-HSS-Cause** + +| Bit | Name | Description | +|----------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Absent Subscriber | This bit, when set, indicates that the configuration could not be forwarded and/or the UE is not reachable at the serving node, either because there is no serving node registered in the HSS or because the subscriber is purged in the registered serving node(s). | +| NOTE: Bits not defined in this table shall be cleared by the sending node and discarded by the receiving node. | | | + +### 8.4.51 Enhanced-Coverage-Restriction + +The Enhanced-Coverage-Restriction AVP is of type Grouped and shall identify either a complete (and possibly empty) list of serving PLMNs where Enhanced Coverage shall be restricted or a complete (and possibly empty) list of serving PLMNs where Enhanced Coverage shall not be restricted. + +AVP format: + +``` +Enhanced-Coverage-Restriction ::= + [ Restricted-PLMN-List ] + [ Allowed-PLMN-List ] + *[AVP] +``` + +### 8.4.52 Enhanced-Coverage-Restriction-Data + +The Enhanced-Coverage-Restriction-Data AVP is of type Grouped and shall identify the current visited PLMN (if any) and the current settings of Enhanced-Coverage-Restriction. + +AVP format: + +``` +Enhanced-Coverage-Restriction-Data ::= + { Enhanced-Coverage-Restriction } + [ Visited-PLMN-Id ] + *[AVP] +``` + +### 8.4.53 Restricted-PLMN-List + +The Restricted-PLMN-List AVP is of type Grouped and shall identify the complete set of serving PLMNs where Enhanced Coverage is restricted. + +AVP format: + +``` +Restricted-PLMN-List ::= + *[ Visited-PLMN-Id ] + *[AVP] +``` + +Absence of Visited-PLMN-Id AVPs indicates that Enhanced Coverage is allowed in all serving PLMNs. + +### 8.4.54 Allowed-PLMN-List + +The Allowed-PLMN-List AVP is of type Grouped and shall identify the complete set of serving PLMNs where Enhanced Coverage is allowed. + +AVP format: + +``` +Allowed-PLMN-List ::= + *[ Visited-PLMN-Id ] + *[AVP] +``` + +Absence of Visited-PLMN-Id AVPs indicates that Enhanced Coverage is restricted in all serving PLMNs. + +### 8.4.55 Requested-Validity-Time + +The Requested-Validity-Time AVP is of type Time (see IETF RFC 6733 [23]), and contains the point of time after which the SCEF is willing to consider a granted NIDD authorization as being implicitly revoked. + +### 8.4.56 Granted-Validity-Time + +The Granted-Validity-Time AVP is of type Time (see IETF RFC 6733 [23]), and contains the point of time after which the HSS removes a stored NIDD Authorization and after which the SCEF shall consider a granted NIDD authorization as being implicitly revoked. + +A value in the past indicates that the NIDD Authorization is explicitly revoked. + +### 8.4.57 NIDD-Authorization-Update + +The NIDD-Authorization-Update AVP is of type Grouped, and it contains the information to be provided triggered by an update or revocation of the NIDD-Authorization. + +AVP format: + +``` +NIDD-Authorization-Update ::= + *[ APN-Validity-Time ] + *[AVP] +``` + +### 8.4.58 Loss-Of-Connectivity-Reason + +The Loss-Of Connectivity-Reason AVP is of type Unsigned32 and shall identify the reason why loss of connectivity is reported. The following values are defined: + +UE\_DETACHED\_MME (0) + +UE\_DETACHED\_SGSN (1) + +MAX\_DETECTION\_TIME\_EXPIRED\_MME (2) + +MAX\_DETECTION\_TIME\_EXPIRED\_SGSN (3) + +UE\_PURGED\_MME (4) + +UE\_PURGED\_SGSN (5) + +### 8.4.59 Group-Reporting-Guard-Timer + +The Group-Reporting-Guard-Timer AVP is of type Unsigned32. The Group Reporting Guard Timer indicates an interval in seconds after which time the HSS (at the latest) shall send aggregated Status Indications and/or event report(s) which have been detected for UEs that are part of a group. + +### 8.4.60 CIA-Flags + +The CIA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.60-1: + +**Table 8.4.60-1: CIA-Flags** + +| Bit | Name | Description | +|-------|-------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Group-Configuration-In-Progress | This bit is set when the HSS indicates that the HSS is processing the Group Monitoring configuration(s) and will report further status using the RIR command. | +| NOTE: | Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | + +### 8.4.61 Group-Report + +The Group-Report AVP is of type Grouped, and it contains the information to be reported as requested by Monitoring-Event-Configuration or Suggested-Network-Configuration for a group. + +VP format: + +``` + +Group-Report ::= + { SCEF-Reference-ID } + [ SCEF-Reference-ID-Ext ] + [ SCEF-ID ] + *[ Group-Report-Item ] + *[AVP] + +``` + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext AVP shall be used instead of SCEF-Reference-ID; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver. + +### 8.4.62 Group-Report-Item + +The Group-Report-Item AVP is of type Grouped, and it contains the information to be reported as requested by Monitoring-Event-Configuration or Suggested-Network-Configuration for a specific UE as part of group processing. + +AVP format: + +``` +Group-Report-Item ::= + { User-Identifier } + [ Visited-PLMN-Id ] + [ Roaming-Information ] + [ IMEI-Change ] + [ Reachability-Information ] + [ Maximum-UE-Availability-Time ] + [ EPS-Location-Information ] + [ Monitoring-Type ] + *[ Service-Report ] + [ S6t-HSS-Cause ] + [ Idle-Status-Indication ] + [ Reporting-Time-Stamp ] + [ Updated-Network-Configuration ] + *[ SCEF-Reference-ID-for-Deletion ] + *[ SCEF-Reference-ID-for-Deletion-Ext ] + [ Event-Handling ] + *[AVP] +``` + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-for-Deletion-Ext AVP shall be used instead of SCEF-Reference-ID-for-Deletion. + +### 8.4.63 RIR-Flags + +The RIR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.63-1: + +**Table 8.4.63-1: RIR-Flags** + +| Bit | Name | Description | +|-------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Group-Configuration-In-Progress | This bit is set when the HSS indicates that the HSS is processing the Group Monitoring configuration and will report further status/reports for the group using additional RIR command(s). | +| 1 | All-Monitoring-Events-Cancelled | This bit is set when the HSS indicates that all existing events (if any) are cancelled, e.g. due to subscription removal | +| 2 | Change-Of-Authorized-Monitoring-Events | This bit is set when the HSS indicates that the SCEF authorization for one or more monitoring events has changed. | +| 3 | All-Communication-Pattern-Cancelled | This bit is set when the HSS indicates that all existing communication pattern (if any) are cancelled, e.g. due to subscription removal | +| 4 | All-Suggested-Network-Configuration-Cancelled | This bit is set when the HSS indicates that all existing Network Parameter Configurations (if any) are cancelled, e.g. due to subscription removal | +| NOTE: | Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | + +### 8.4.64 Type-Of-External-Identifier + +The Type-Of-External-Identifier AVP is of type Unsigned32 and it shall indicate which type of identity is carried in the External-Identifier AVP. The following values are defined: + +EXTERNAL-UE-IDENTIFIER-TYPE (0) + +The value 0 indicates the External-Identifier AVP carries the identity of an individual UE. + +EXTERNAL-GROUP-IDENTIFIER-TYPE (1) + +The value 1 indicates the External-Identifier AVP carries the identity of a Group of UEs. + +### 8.4.65 APN-Validity-Time + +The APN-Validity-Time AVP is of type Grouped, and it contains the APN (within the Service-Selection AVP) and the updated validity time for the granted NIDD authorization associated to the APN. + +AVP format: + +``` +APN-Validity-Time ::= + { Granted-Validity-Time } + [ Service-Selection ] + *[AVP] +``` + +Absence of Service-Selection AVP indicates that the Granted-Validity-Time applies to all granted NIDD Authorizations for the user. In this case only one APN-Validity-Time AVP shall be present within the NIDD-Authorization-Update AVP. + +## 8.4.66 Suggested-Network-Configuration + +The Suggested-Network-Configuration AVP is of type Grouped, and it shall contain the details for configuration for Suggested Network configuration. + +AVP format: + +``` +Suggested-Network-Configuration ::= + { SCEF-Reference-ID } +``` + +``` + +[ SCEF-Reference-ID-Ext ] +{ SCEF-ID } +[ Subscribed-Periodic-RAU-TAU-Timer ] +[ Active-Time ] +[ DL-Buffering-Suggested-Packet-Count ] +[ MTC-Provider-Info ] +*[ SCEF-Reference-ID-for-Deletion ] +*[ SCEF-Reference-ID-for-Deletion-Ext ] +*[AVP] + +``` + +If the values of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion are the same, no Network Parameter Configurations AVP(s) shall be present, that is, SCEF-Reference-ID-for-Deletion takes precedence. If the values of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion are not the same, Network Parameter Configurations AVP(s) are related to SCEF-Reference-ID. + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used instead of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver. + +## 8.4.67 Monitoring-Event-Report-Status + +The Monitoring-Event-Report-Status AVP is of type Grouped, and it contains the result of a specific event report (identified by the pair SCEF-ID and SCEF-Reference-ID) received by the SCEF. + +AVP format: + +``` + +Monitoring-Event-Report-Status ::= + +{ SCEF-Reference-ID } +[ SCEF-Reference-ID-Ext ] +{ SCEF-ID } +[ Result-Code ] +[ Experimental-Result-Code ] +*[AVP] + +``` + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext AVP shall be used instead of SCEF-Reference-ID; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver. + +## 8.4.68 PLMN-ID-Requested + +The PLMN-ID-Requested AVP is of type Enumerated and it shall indicate whether the PLMN-ID value needs to be returned in the event report associated to the monitoring type "ROAMING\_STATUS". The following values are defined: + +TRUE (0) + +The value TRUE (0) indicates that the PLMN-ID value shall be returned in the corresponding event report for "ROAMING\_STATUS". + +FALSE (1) + +The value FALSE (1) indicates that the PLMN-ID value shall not be returned in the corresponding event report for "ROAMING\_STATUS". + +The default value, when this AVP is not included, is TRUE (0). + +## 8.4.69 AdditionalIdentifiers + +The AdditionalIdentifiers AVP is of type Grouped, and it shall contain External Group Identifiers. + +AVP format: + +``` +AdditionalIdentifiers ::= + *[ External-Identifier ] + *[AVP] +``` + +## 8.4.70 NIR-Flags + +The NIR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.70-1: + +**Table 8.4.70-1: NIR-Flags** + +| Bit | Name | Description | +|-------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Incomplete Group-User-Identifier-List | This bit is set when the SCEF indicates that the union of the Group User Identifier Lists sent in this and in previous messages is still incomplete and more segments of the list will follow within subsequent NIR commands. The bit is not set when NIR contains the last segment of the list. | +| NOTE: | Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | + +## 8.4.71 Reporting-Time-Stamp + +The Reporting-Time-Stamp AVP is of type Time (see IETF RFC 6733 [23]), and contains the point of time when the report was generated. + +## 8.4.72 NIA-Flags + +The NIA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 8.4.72-1: + +**Table 8.4.72-1: NIA-Flags** + +| Bit | Name | Description | +|-------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Incomplete Group-User-Identifier-List | This bit is set when the HSS indicates that the sent Group User Identifier List is incomplete and more segments of the list will follow within subsequent NIR commands. | +| NOTE: | Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | + +## 8.4.73 Group-User-Identifier + +The Group-User-Identifier AVP is of type Grouped and it contains the External-Identifier or MSISDN and the IMSI of a user belonging to a group. + +AVP format: + +``` +Group-User-Identifier ::= +``` + +[ User-Name ] +[ MSISDN ] +[ External-Identifier ] +\*[AVP] + +## 8.4.74 MTC-Provider-Info + +The MTC-Provider-Info AVP is of type Grouped and it contains the information associated to the MTC Service Provider and/or MTC Application (see 3GPP TS 23.682 [2], clause 5.6). + +AVP format: + +MTC-Provider-Info ::= +[ MTC-Provider-ID ] +\*[AVP] + +## 8.4.75 MTC-Provider-ID + +The MTC-Provider-ID AVP is of type UTF8String and it contains a character string representing the identity of the MTC Service Provider and/or MTC Application. + +## 8.4.76 PDN-Connectivity-Status-Configuration + +The PDN-Connectivity-Status-Configuration AVP is of type Grouped and it indicates the APN(s) for which the PDN Connectivity Status is to be monitored. If the Service-Selection AVP is included, then the monitoring applies to that specific APN; if the Service-Selection is absent, the monitoring request applies to all APNs. + +AVP format: + +PDN-Connectivity-Status-Configuration ::= +[ Service-Selection ] +\*[AVP] + +## 8.4.77 PDN-Connectivity-Status-Report + +The PDN-Connectivity-Status-Report AVP is of type Grouped and it contains the different parameters associated to the reporting of the PDN Connectivity Status event type. + +AVP format: + +PDN-Connectivity-Status-Report ::= +{ Service-Selection } +{ PDN-Connectivity-Status-Type } +[ PDN-Type ] +[ Non-IP-PDN-Type-Indicator ] +[ Non-IP-Data-Delivery-Mechanism ] +\*2 [ Served-Party-IP-Address ] +\*[AVP] + +Absence of PDN-Connectivity-Status-Report in Monitoring-Event-Report AVP including Monitoring-Type AVP with value PDN\_CONNECTIVITY\_STATUS (10) in responses (immediate report) shall indicate that none of the requested APNs are active. The AVP shall always be present in RIR command if Monitoring-Event-Report AVP includes Monitoring-Type AVP with value PDN\_CONNECTIVITY\_STATUS (10). + +The PDN-Type AVP is defined in 3GPP TS 29.272 [14] and it shall be present when the PDN Connection is an IP connection, and it may contain the value IPv4, IPv6 or IPv4v6. The value IPv4\_OR\_IPv6 shall not be used for this event reporting. If PDN-Type AVP is present, then the Non-IP-PDN-Type-Indicator and Non-IP-Data-Delivery-Mechanism AVPs shall be absent. + +The Non-IP-PDN-Type-Indicator AVP is defined in 3GPP TS 29.272 [14] and it indicates whether the PDN Connection is of type "Non-IP". If this AVP is present, it shall be set to TRUE and the PDN-Type AVP shall be absent. + +The Non-IP-Data-Delivery-Mechanism AVP is defined in 3GPP TS 29.272 [14] and it shall be present if the Non-IP-PDN-Type-Indicator AVP is present and set to TRUE. It shall indicate whether the Non-IP data delivery is done via Point-To-Point tunnelling over the SGi interface, or via the SCEF. + +NOTE: In 3GPP TS 23.682 [2], clause 5.6.3.9, the reporting of the data delivery mechanism is described in terms of a parameter called "3GPP Interface Indication"; however, the conveyance of such information inside the PDN-Connectivity-Status-Report AVP is done in the present specification in terms of the same set of AVPs used for the definition of the subscription data in 3GPP TS 29.272 [14]. The correspondence of the values of the parameter "3GPP Interface Indication" from 3GPP TS 23.682 [2] is as follows: + +- "API-Connectivity" corresponds to the presence of Non-IP-Data-Delivery-Mechanism set to value SCEF-BASED-DATA-DELIVERY; +- "IP-connectivity" corresponds to the presence of PDN-Type AVP, and the absence of Non-IP-PDN-Type-Indicator and Non-IP-Data-Delivery-Mechanism AVPs; +- "Other" corresponds to the presence of Non-IP-Data-Delivery-Mechanism set to value SGi-BASED-DATA-DELIVERY. + +The Served-Party-IP-Address AVP may be present 0, 1 or 2 times, and contain the IP address(es) used by the UE (if available) and, if present, they shall contain either of: + +- an IPv4 address, or +- an IPv6 address/prefix, or +- both, an IPv4 address and an IPv6 address/prefix (for dual-stack UEs with PDN-Type set to "IPv4v6"). + +For the IPv6 prefix, the lower 64 bits of the address shall be set to zero. + +## 8.4.78 PDN-Connectivity-Status-Type + +The PDN-Connectivity-Status-Type AVP is of type Unsigned32 and it shall indicate the status of the PDN Connection being monitored. The following values are defined: + +### CREATED (0) + +The value CREATED (0) indicates that the event corresponds to the creation of a new PDN Connection on the monitored APN. + +### DELETED (1) + +The value DELETED (1) indicates that the event corresponds to the deletion of a PDN Connection on the monitored APN. + +## 8.4.79 Traffic-Profile + +The Traffic-Profile AVP is of type Unsigned32. The following values are defined: + +SINGLE\_TRANSMISSION\_UL (0) + SINGLE\_TRANSMISSION\_DL (1) + DUAL\_TRANSMISSION\_UL\_WITH\_SUBSEQUENT\_DL (2) + DUAL\_TRANSMISSION\_DL\_WITH\_SUBSEQUENT\_UL (3) + MULTI\_TRANSMISSION (4) + +## 8.4.80 Updated-Network-Configuration + +The Updated-Network-Configuration AVP is of type Grouped. If not included inside Group-Report-Item AVP, it shall contain only the Network Parameter Configurations which were received in a previous CIR command and have been updated due to a new CIR command. If included inside Group-Report-Item AVP, it shall contain the current values applied in the network for each group member. + +AVP format: + +``` +Updated-Network-Configuration ::= + { SCEF-ID } + [ SCEF-Reference-ID ] + [ SCEF-Reference-ID-Ext ] + *[ SCEF-Reference-ID-for-Deletion ] + *[ SCEF-Reference-ID-for-Deletion-Ext ] + [ Subscribed-Periodic-RAU-TAU-Timer ] + [ Active-Time ] + [ DL-Buffering-Suggested-Packet-Count ] + *[AVP] +``` + +At least one reference ID (either in SCEF-Reference-ID or in SCEF-Reference-ID-Ext) or a reference ID for deletion (either in SCEF-Reference-ID-for-Deletion or in SCEF-Reference-ID-for-Deletion-Ext) shall be present. + +When the "Extended Reference IDs" feature is supported by the HSS and SCEF, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used instead of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively. + +## 8.4.81 Battery-Indicator + +The Battery-Indicator AVP is of type Unsigned32 and it shall contain a bitmask. The meaning of the bits shall be as defined in table 8.4.81-1: + +**Table 8.4.81-1: Battery-Indicator** + +| Bit | Name | Description | +|--------------------------------------------------------------------------------------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | NO_BATTERY | When this bit is set it indicates that UE is not battery powered. | +| 1 | BATTERY_REPLACEABLE_INDICATION | When this bit is set it indicates that battery of the UE is replaceable, when this bit is not set it indicates that battery of UE is not replaceable. | +| 2 | BATTERY_RECHARGEABLE_INDICATION | When this bit is set it indicates that the battery of the UE is rechargeable, when this bit is not set it indicates that battery of the UE is not rechargeable. | +| NOTE1: Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command. | | | +| NOTE2: If bit 0 is set, bit 1 and bit 2 shall be cleared. | | | + +## 8.4.82 SCEF-Reference-ID-Ext + +The SCEF-Reference-ID-Ext AVP is of type Unsigned64 and it shall contain a 64-bit identifier provided by the SCEF, which shall be used instead of the 32-bit identifier SCEF-Reference-ID, when supported by both SCEF and HSS. + +## 8.4.83 SCEF-Reference-ID-for-Deletion-Ext + +The SCEF-Reference-ID-for-Deletion-Ext AVP is of type Unsigned64 and it shall contain a 64-bit identifier provided by the SCEF, which shall be used instead of the 32-bit identifier SCEF-Reference-ID-for-Deletion, when supported by both SCEF and HSS. + +# Annex A (normative): Diameter overload control mechanism + +## A.1 General + +IETF RFC 7683 [15] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes. + +## A.2 S6m interface + +### A.2.1 General + +The Diameter overload control mechanism is an optional feature over the S6m interface. + +It is recommended to make use of the IETF RFC 7683 [15] on the S6m interface where, when applied, the MTC-IWF shall behave as a reacting node and the HSS as a reporting node. + +NOTE: There is no need to support this mechanism in the other way (overload of the MTC-IWF) as no Diameter request commands are sent by the HSS to the MTC-IWF. + +### A.2.2 HSS behaviour + +The HSS requests traffic reduction from the MTC-IWF when it is in an overload situation, by including OC-OLR AVP in answer commands as described in IETF RFC 7683 [15]. + +The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the S6m interfaces or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources etc. + +The HSS determines the specific contents of the OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means. + +## A.2.3 MTC-IWF behaviour + +The MTC-IWF applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [15]. + +Requested traffic reduction is achieved by the MTC-IWF by implementation specific means. For example, it may implement message throttling with prioritization. + +Annex B gives guidance on message prioritisation over the S6m interface. + +--- + +## A.3 S6t interface + +### A.3.1 General + +The Diameter overload control mechanism is an optional feature over the S6t interface. + +It is recommended to make use of the IETF RFC 7683 [15] on the S6t interface where, when applied, the SCEF shall behave as a reacting node and the HSS as a reporting node. + +NOTE: With the current services used on this interface there is no need to support this mechanism in the other direction (overload of the SCEF) as the number of Diameter request commands sent by the HSS to the SCEF is determined by the SCEF in one earlier command of the SCEF and they corresponds to non-frequent events. + +### A.3.2 HSS behaviour + +The HSS requests traffic reduction from the SCEF when it is in an overload situation, by including OC-OLR AVP in answer commands as described in IETF RFC 7683 [15]. + +The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the S6t interfaces or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources etc. + +The HSS determines the specific contents of the OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means. + +### A.3.3 SCEF behaviour + +The SCEF applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [15]. + +Requested traffic reduction is achieved by the SCEF by implementation specific means. For example, it may implement monitoring event activation throttling with prioritization. + +--- + +## Annex B (Informative): Diameter overload control node behaviour + +### B.1 Introduction + +Annex B gives guidance on the Diameter overload control node behaviours regarding message prioritisation over the S6m and S6t interface. + +--- + +### B.2 Message prioritisation over S6m + +This clause gives an analysis of possible behaviours of the MTC-IWF regarding message prioritisation as guidance and for an informative purpose. + +When the HSS is overloaded, the MTC-IWF will receive overload reports from the HSS requesting a reduction of requests sent by the MTC-IWF. This will apply to the SIR request commands. + +The MTC-IWF can consider some messages with a lower or a higher priority; lower priority messages will be candidates for throttling before higher priority messages. + +Following considerations can be taken into account: + +- SIR messages for a given SCS can have a lower priority according to operator policies; +- If a SCS node generates a peak signalling over the Tsp interface, SIR messages over S6m related to this SCS can have a lower priority; +- The SIR messages over S6m related to a recall procedure or a replace procedure over the Tsp interface (see 3GPP TS 29.368 [13]) may have a lower priority according to operator policies. + +--- + +### B.3 Message prioritisation over S6t + +This clause gives an analysis of possible behaviours of the SCEF regarding message prioritisation as guidance and for an informative purpose. + +When the HSS is overloaded, the SCEF will receive overload reports from the HSS requesting a reduction of requests sent by the SCEF. This will apply to the CIR request commands. + +The SCEF can consider some messages with a lower or a higher priority; lower priority messages will be candidates for throttling before higher priority messages. + +Following considerations can be taken into account: + +- CIR messages for a given SCEF can have a lower priority according to operator policies; +- If a SCEF node generates a peak signalling over the S6t interface, CIR messages from this SCEF can have a lower priority; + +--- + +## Annex C (normative): Diameter message priority mechanism + +### C.1 General + +IETF 7944 [20] specifies a Diameter routing message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied. + +It is recommended to make use of IETF 7944 [20] over the S6m, S6n and S6t interfaces of an operator network when the overload control defined in Annex A is applied on these interfaces. + +--- + +### C.2 S6m, S6n, S6t interfaces + +The Diameter message priority mechanism is an optional feature which may apply on one or several of the S6m, S6n, S6t interfaces. + +A 3GPP functional entity supporting the Diameter message priority mechanism over one or several of the S6m, S6n, S6t interfaces shall comply with IETF RFC 7944 [20]. + +A 3GPP functional entity sending a request shall determine the required priority according to its policies. When priority is required, it shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level. + +When the 3GPP functional entity receives the corresponding response, it shall prioritise received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When a 3GPP functional entity receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response. + +The decisions of the 3GPP functional entity for a required priority and for the priority level value are implementation specific. + +If: + +- a 3GPP functional entity supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the 3GPP functional entity shall set the DSCP marking for transport of the request or response according to the required priority level. + +Diameter requests related to high priority traffic should contain a DRMP AVP with a high priority of which the level value is operator dependent. + +--- + +## Annex D (normative): Diameter load control mechanism + +### D.1 General + +IETF RFC 8583 [22] specifies a mechanism for sharing of Diameter load information. It includes the definition and the transfer of related AVPs between Diameter nodes. + +--- + +### D.2 S6m interface + +#### D.2.1 General + +The Diameter load control mechanism is an optional feature over the S6m interface. + +It is recommended to make use of IETF RFC 8583 [22] on the S6m interface where, when applied, the MTC-IWF shall behave as reacting nodes and the HSS as a reporting node. + +#### D.2.2 HSS behaviour + +The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [22]. + +The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the S6m interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc. + +The HSS determines when to send Load AVPs of type HOST by implementation specific means. + +#### D.2.3 MTC-IWF behaviour + +When performing next hop Diameter Agent selection for requests that are routed based on realm, the MTC-IWF may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [22]. + +--- + +### D.3 S6t interface + +#### D.3.1 General + +The Diameter load control mechanism is an optional feature over the S6t interface. + +It is recommended to make use of IETF RFC 8583 [22] on the S6t interface where, when applied, the SCEF shall behave as reacting nodes and the HSS as a reporting node. + +#### D.3.2 HSS behaviour + +The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [22]. + +The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the S6t interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc. + +The HSS determines when to send Load AVPs of type HOST by implementation specific means. + +### D.3.3 SCEF behaviour + +When performing next hop Diameter Agent selection for requests that are routed based on realm, the SCEF may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [22]. + +## Annex E (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-------|-----------|------|-----|---------------------------------------------------------------------------------------|--------| +| 2012-09 | CT#57 | CP-120485 | | | V.1.0.0 presented for information and approval | 11.0.0 | +| 2012-12 | CT#58 | CP-120731 | 0001 | 3 | T4 device triggering via IMS | 11.1.0 | +| 2012-12 | CT#58 | CP-120731 | 0002 | 1 | MWD and SMS-SC address | | +| 2012-12 | CT#58 | CP-120731 | 0003 | - | Application ID and Command Codes | | +| 2013-06 | CT#60 | CP-130300 | 0004 | 2 | S6m complements related to Diameter for SMS with SGSN | 12.0.0 | +| 2013-09 | CT#61 | CP-130456 | 0005 | 2 | SGSN Diameter address with Gdd support | 12.1.0 | +| 2014-06 | CT#64 | CP-140243 | 0007 | 3 | Diameter overload over S6m | 12.2.0 | +| 2014-12 | CT#66 | CP-140775 | 0008 | 1 | Absent Subscriber detection | 12.3.0 | +| 2015-06 | CT#68 | CP-150248 | 0012 | 1 | IP-SM-GW-Realm | 12.4.0 | +| 2015-06 | CT#68 | CP-150265 | 0009 | 1 | Unsuccessful Triggering due to MT-SMS barring | 13.0.0 | +| 2015-06 | CT#68 | CP-150271 | 0013 | 3 | Introducing S6t reference point | 13.0.0 | +| 2015-09 | CT#69 | CP-150456 | 0019 | 3 | New Monitoring configuration commands on S6t | 13.1.0 | +| 2015-09 | CT#69 | CP-150456 | 0020 | 2 | Update S6t description to support AESE Communication Pattern provision | 13.1.0 | +| 2015-09 | CT#69 | CP-150456 | 0022 | 3 | Introducing CP parameter to commands on S6t | 13.1.0 | +| 2015-12 | CT#70 | CP-150778 | 0023 | - | S6t Application ID and Command Codes | 13.2.0 | +| 2015-12 | CT#70 | CP-150778 | 0024 | 3 | Enhancements to St6 on MONTE | 13.2.0 | +| 2015-12 | CT#70 | CP-150778 | 0026 | 1 | Diameter Overload on S6t | 13.2.0 | +| 2015-12 | CT#70 | CP-150778 | 0028 | 1 | Corrections to some MONTE AVPs, references and procedures | 13.2.0 | +| 2015-12 | CT#70 | CP-150778 | 0030 | 3 | Multiple instances in a configuration request command | 13.2.0 | +| 2015-12 | CT#70 | CP-150778 | 0031 | 2 | Enhancements and clarification on MONTE | 13.2.0 | +| 2015-12 | CT#70 | CP-150778 | 0033 | 3 | Deletion of all Monitoring events assigned to a subscriber (UE) | 13.2.0 | +| 2015-12 | CT#70 | CP-150785 | 0025 | 3 | Introducing a Bitmask to inform the SCEF of the Monitoring capabilities of the HSS | 13.2.0 | +| 2015-12 | CT#70 | CP-150771 | 0027 | 3 | Introducing CP parameter to CIR/CIA commands on S6t | 13.2.0 | +| 2015-12 | CT#70 | CP-150759 | 0032 | 1 | Reference to DOIC updated with IETF RFC 7683 | 13.2.0 | +| 2016-03 | CT#71 | CP-160029 | 0037 | 2 | Clarification on LOSS_OF_CONNECTIVITY reporting | 13.3.0 | +| 2016-03 | CT#71 | CP-160029 | 0039 | 2 | SCEF Restart | 13.3.0 | +| 2016-03 | CT#71 | CP-160029 | 0040 | 2 | Reporting of the start and stop of the reporting of monitoring events | 13.3.0 | +| 2016-03 | CT#71 | CP-160029 | 0044 | 1 | Count and Stop Monitoring Event Reports at SCEF | 13.3.0 | +| 2016-03 | CT#71 | CP-160029 | 0045 | 1 | Change of type of Monitoring-Duration AVP to represent an absolute time | 13.3.0 | +| 2016-03 | CT#71 | CP-160033 | 0046 | 4 | Authorization for NIDD procedure over S6t | 13.3.0 | +| 2016-03 | CT#71 | CP-160023 | 0047 | 1 | Diameter message priority over S6m, S6n, S6t | 13.3.0 | +| 2016-03 | CT#71 | CP-160129 | 0048 | 4 | Definition of Monitoring-Type and clarifications on UE in MME and SGSN for MONTE | 13.3.0 | +| 2016-06 | CT#72 | CP-160225 | 0049 | 1 | Cleanup on MONTE | 13.4.0 | +| 2016-06 | CT#72 | CP-160225 | 0056 | - | Address editor's note on retry-after when sending cancel monitoring event to the SCEF | 13.4.0 | +| 2016-06 | CT#72 | CP-160228 | 0050 | 7 | NIDD authorisation update | 13.4.0 | +| 2016-06 | CT#72 | CP-160228 | 0051 | - | IANA Command Code Registration | 13.4.0 | +| 2016-06 | CT#72 | CP-160228 | 0052 | - | Type of SCEF-ID AVP | 13.4.0 | +| 2016-06 | CT#72 | CP-160233 | 0053 | - | Renaming of Validity-Time AVP | 13.4.0 | +| 2016-06 | CT#72 | CP-160233 | 0057 | 1 | Missing reference to SIR-flags | 13.4.0 | +| 2016-09 | CT#73 | CP-160416 | 0043 | 2 | SCS identity format | 13.5.0 | +| 2016-12 | CT#74 | CP-160650 | 0059 | 1 | AVP code alignment with 29.230 | 13.6.0 | +| 2016-12 | CT#74 | CP-160657 | 0060 | 1 | User Identity correction on NIDD configuration procedure | 13.6.0 | +| 2016-12 | CT#74 | CP-160657 | 0061 | 1 | IMSI in NIR | 13.6.0 | +| 2016-12 | CT#74 | CP-160657 | 0063 | 2 | External-Identifier Retrieval when no NIDD configuration exists | 13.6.0 | +| 2016-12 | CT#74 | CP-160664 | 0065 | - | Correction to change IETF drmp draft version to | 13.6.0 | + +| | | | | | | | +|---------|-------|-----------|------|---|---------------------------------------------------------------------------|--------| +| | | | | | official RFC 7944 | | +| 2016-12 | CT#74 | CP-160660 | 0066 | 2 | HSS-Cause in CIA | 13.6.0 | +| 2016-12 | CT#74 | CP-160660 | 0067 | 1 | Maximum Detection Time | 13.6.0 | +| 2016-12 | CT#74 | CP-160673 | 0062 | 1 | MO SMS over T4 | 14.0.0 | +| 2016-12 | CT#74 | CP-160681 | 0064 | 1 | Load Control | 14.0.0 | +| 2017-03 | CT#75 | CP-170031 | 0081 | 1 | S6t Update to Provide the Suggested Buffering Packet Count to the HSS | 14.1.0 | +| 2017-03 | CT#75 | CP-170039 | 0068 | 2 | Enhanced Coverage | 14.1.0 | +| 2017-03 | CT#75 | CP-170039 | 0070 | 2 | NIDD Authorization revocation | 14.1.0 | +| 2017-03 | CT#75 | CP-170036 | 0069 | 2 | Loss Of Connectivity Reason | 14.1.0 | +| 2017-03 | CT#75 | CP-170036 | 0072 | 1 | Monitoring Status Update | 14.1.0 | +| 2017-03 | CT#75 | CP-170036 | 0073 | 1 | Recources Exceeded | 14.1.0 | +| 2017-03 | CT#75 | CP-170036 | 0076 | - | Failed-AVP AVP in Request Commands | 14.1.0 | +| 2017-03 | CT#75 | CP-170036 | 0077 | 1 | Bit ordering in Diameter AVPs used as bit-masks | 14.1.0 | +| 2017-03 | CT#75 | CP-170036 | 0078 | - | Support of long and short Macro eNodeB IDs | 14.1.0 | +| 2017-03 | CT#75 | CP-170036 | 0079 | - | Service-ID in SIR | 14.1.0 | +| 2017-03 | CT#75 | CP-170029 | 0083 | 1 | Maximum UE Availability Time | 14.1.0 | +| 2017-03 | CT#75 | CP-170048 | 0084 | - | Update of reference for the Diameter base protocol | 14.1.0 | +| 2017-03 | CT#75 | CP-170048 | 0085 | - | Handling of the Vendor-Specific-Application-Id AVP | 14.1.0 | +| 2017-03 | CT#75 | CP-170048 | 0086 | - | Cardinality of the Failed-AVP AVP in answer | 14.1.0 | +| 2017-06 | CT#76 | CP-171029 | 0087 | 3 | Support for group based reporting and status indication for MONTE | 14.2.0 | +| 2017-06 | CT#76 | CP-171030 | 0088 | - | NIDD Authorization revocation | 14.2.0 | +| 2017-06 | CT#76 | CP-171030 | 0089 | 1 | NIDD Authorization update per APN | 14.2.0 | +| 2017-06 | CT#76 | CP-171038 | 0090 | 1 | MO-SMS | 14.2.0 | +| 2017-06 | CT#76 | CP-171184 | 0092 | 1 | Communication Patterns without Expiry Time | 14.2.0 | +| 2017-06 | CT#76 | CP-171021 | 0094 | 1 | Remove User-Identifier from NIA | 14.2.0 | +| 2017-06 | CT#76 | CP-171029 | 0095 | 1 | Unauthorized Requesting Entity on S6t | 14.2.0 | +| 2017-06 | CT#76 | CP-171018 | 0097 | 1 | Support for signaling transport level packet marking | 14.2.0 | +| 2017-09 | CT#77 | CP-172013 | 0104 | - | Correction of DRMP Procedures | 14.3.0 | +| 2017-09 | CT#77 | CP-172026 | 0101 | 2 | Enhancements for NAPS on Idle Status Indication | 15.0.0 | +| 2017-09 | CT#77 | CP-172026 | 0105 | 1 | Enhancements for NAPS on Accuracy | 15.0.0 | +| 2017-12 | CT#78 | CP-173029 | 0100 | 2 | Reachability Type | 15.1.0 | +| 2017-12 | CT#78 | CP-173033 | 0106 | 2 | Enable minimum time interval for Continuous Location Reporting | 15.1.0 | +| 2017-12 | CT#78 | CP-173033 | 0107 | 2 | Suggested Network Configuration Request | 15.1.0 | +| 2017-12 | CT#78 | CP-173028 | 0108 | 3 | Monitoring Event Report Status | 15.1.0 | +| 2017-12 | CT#78 | CP-173028 | 0113 | 1 | Corrections to S6t procedures | 15.1.0 | +| 2018-03 | CT#79 | CP-180025 | 0116 | 3 | Reporting of Suggested Network Configuration changes by HSS | 15.2.0 | +| 2018-03 | CT#79 | CP-180025 | 0117 | 2 | IMSI-Group-Id retrieval | 15.2.0 | +| 2018-06 | CT#80 | CP-181116 | 0126 | 1 | Presence of Monitoring-type AVP in Monitoring event configuration | 15.3.0 | +| 2018-06 | CT#80 | CP-181117 | 0121 | 1 | Monitoring Event configuration removal for a group | 15.3.0 | +| 2018-06 | CT#80 | CP-181126 | 0124 | 1 | Conditional User-Identity clarification in Reporting Information Request | 15.3.0 | +| 2018-06 | CT#80 | CP-181126 | 0125 | - | Optimization of the MONTE reporting procedure in S6t | 15.3.0 | +| 2018-06 | CT#80 | CP-181127 | 0123 | - | Group Message Delivery via Unicast MT NIDD | 15.3.0 | +| 2018-06 | CT#80 | CP-181130 | 0118 | 2 | Overwriting of configuration data triggers deletion of a monitoring event | 15.3.0 | +| 2018-06 | CT#80 | CP-181130 | 0119 | 2 | Suggested-Network-Configuration parameter content | 15.3.0 | +| 2018-06 | CT#80 | CP-181130 | 0122 | 2 | Deletion of Network Parameter Configuration | 15.3.0 | +| 2018-09 | CT#81 | CP-182075 | 0127 | 1 | Multiple instances in a configuration request command clarifications | 15.4.0 | +| 2018-09 | CT#81 | CP-182075 | 0128 | 1 | One time report handling | 15.4.0 | +| 2018-09 | CT#81 | CP-182075 | 0129 | 1 | Configuration of MONTE when user is purged | 15.4.0 | +| 2018-09 | CT#81 | CP-182075 | 0130 | - | No default value for Supported-Monitoring-Events AVP | 15.4.0 | +| 2018-09 | CT#81 | CP-182075 | 0131 | 1 | Supported Services AVP handling | 15.4.0 | +| 2018-09 | CT#81 | CP-182081 | 0133 | 1 | Completion of Monitoring Event configuration removal for a group | 15.4.0 | +| 2018-12 | CT#82 | CP-183097 | 0140 | 1 | Reporting corrections for IMEI change and idle status indication | 15.5.0 | +| 2018-12 | CT#82 | CP-182095 | 0135 | 3 | Monitoring event report | 15.5.0 | + +| | | | | | | | +|---------|--------|-----------|------|---|-----------------------------------------------------------------------------------------|--------| +| 2018-12 | CT#82 | CP-182095 | 0142 | 3 | Fixing Group NIDD | 15.5.0 | +| 2018-12 | CT#82 | CP-182098 | 0134 | 1 | Location reporting details for MONTE | 15.5.0 | +| 2018-12 | CT#82 | CP-182098 | 0136 | 1 | Default Values in Reachability Type and Location Type | 15.5.0 | +| 2018-12 | CT#82 | CP-182098 | 0137 | - | Deletion of monitoring events when unknown in SCEF | 15.5.0 | +| 2018-12 | CT#82 | CP-182098 | 0138 | - | Event configuration failure in S6a/ULA | 15.5.0 | +| 2018-12 | CT#82 | CP-182098 | 0139 | 1 | External Identifier AVP definition is not correct | 15.5.0 | +| 2018-12 | CT#82 | CP-182098 | 0141 | - | Applicability of Maximum Number of Reports | 15.5.0 | +| 2018-12 | CT#82 | CP-182098 | 0144 | 1 | IMEI Change Event Type | 15.5.0 | +| 2019-03 | CT#83 | CP-190061 | 0146 | 1 | Absence of MSISDN in S6n | 15.6.0 | +| 2019-03 | CT#83 | CP-190038 | 0147 | 1 | MONTE Corrections | 15.6.0 | +| 2019-03 | CT#83 | CP-190037 | 0148 | 1 | Handling of multiple external IDs for the same UE | 15.6.0 | +| 2019-03 | CT#83 | CP-190038 | 0149 | 1 | SCEF-ID clarification | 15.6.0 | +| 2019-03 | CT#83 | CP-190038 | 0150 | 1 | Communication Pattern Deletion | 15.6.0 | +| 2019-09 | CT#85 | CP-192094 | 0155 | 2 | draft-ietf-dime-load published as RFC 8583 | 15.7.0 | +| 2019-09 | CT#85 | CP-192121 | 0153 | 2 | Communication pattern enhancement | 16.0.0 | +| 2019-09 | CT#85 | CP-192121 | 0152 | 1 | Event type PDN Connectivity Status | 16.0.0 | +| 2019-12 | CT#86 | CP-193038 | 0156 | - | Suggested Network Configuration overwrite | 16.1.0 | +| 2019-12 | CT#86 | CP-193038 | 0158 | - | Enhancement of Monitoring Event configuration and Network Parameter Configuration | 16.1.0 | +| 2019-12 | CT#86 | CP-193038 | 0159 | - | MTC Provider Info authorization | 16.1.0 | +| 2019-12 | CT#86 | CP-193038 | 0160 | 1 | Network Parameter Configuration Reporting | 16.1.0 | +| 2019-12 | CT#86 | CP-193038 | 0161 | - | PDN connectivity status event correction | 16.1.0 | +| 2019-12 | CT#86 | CP-193052 | 0157 | 2 | Battery Indication for Communication pattern enhancement | 16.1.0 | +| 2020-06 | CT#88e | CP-201028 | 0165 | 2 | Update of Suggested Network Configuration | 16.2.0 | +| 2020-06 | CT#88e | CP-201028 | 0170 | - | Wrong name of Network Configuration parameters | 16.2.0 | +| 2020-06 | CT#88e | CP-201028 | 0172 | - | Removal of Editor's Note in References | 16.2.0 | +| 2020-06 | CT#88e | CP-201027 | 0168 | - | Suggested-Network-Configuration | 16.2.0 | +| 2020-06 | CT#88e | CP-201053 | 0162 | - | CIR-Flags | 16.2.0 | +| 2020-06 | CT#88e | CP-201053 | 0163 | - | User-Name in NIDD-Authorization-Update | 16.2.0 | +| 2020-06 | CT#88e | CP-201053 | 0166 | - | Event-Handling in Group-Report-Item | 16.2.0 | +| 2020-12 | CT#90e | CP-203024 | 0173 | - | Extended Reference ID | 16.3.0 | +| 2023-09 | CT#90e | CP-232079 | 0184 | 2 | Misalignment between Stage 2 and Stage 3 when Roaming Status request is received by HSS | 16.4.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29338/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29338/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dd840fd4954ee3804dec736c6dfaccf9e39660a --- /dev/null +++ b/marked/Rel-16/29_series/29338/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc07ebe50e37e471b40468b34d492146632995de2a9ed8619536bd467237f18f +size 10081 diff --git a/marked/Rel-16/29_series/29338/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29338/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cd7146c8984c1e91132ffd277eccc3e2fa7cb1b --- /dev/null +++ b/marked/Rel-16/29_series/29338/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14bf0d1be04507e4d1b9ffb6d92e65ea1f45a660c5b39082a23b974731613286 +size 5825 diff --git a/marked/Rel-16/29_series/29338/raw.md b/marked/Rel-16/29_series/29338/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f0030bdb86c7cb4c72141820d91e5301839b789c --- /dev/null +++ b/marked/Rel-16/29_series/29338/raw.md @@ -0,0 +1,2052 @@ + + +# 3GPP TS 29.338 V16.3.0 (2023-09) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) (Release 16)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text are three red, curved lines representing signal waves. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 General ..... | 9 | +| 4.1 Introduction ..... | 9 | +| 4.2 Use of Diameter Base protocol ..... | 9 | +| 4.3 Securing Diameter messages..... | 9 | +| 4.4 Accounting functionality..... | 9 | +| 4.5 Use of sessions ..... | 9 | +| 4.6 Transport protocol..... | 9 | +| 4.7 Advertising application support ..... | 9 | +| 4.8 Diameter Application Identifier ..... | 10 | +| 4.9 Use of the Supported-Features AVP ..... | 10 | +| 5 Diameter based S6c interface between HSS and central SMS functions ..... | 10 | +| 5.1 Introduction ..... | 10 | +| 5.2 Procedures description ..... | 11 | +| 5.2.1 Send Routing Info for SM procedure ..... | 11 | +| 5.2.1.1 General..... | 11 | +| 5.2.1.2 Detailed behaviour of the SMS-GMSC ..... | 14 | +| 5.2.1.3 Detailed behaviour of the HSS ..... | 15 | +| 5.2.1.4 Detailed behaviour of the SMS Router..... | 15 | +| 5.2.2 Alert Service Centre procedure ..... | 16 | +| 5.2.2.1 General..... | 16 | +| 5.2.2.2 Detailed behaviour of the HSS ..... | 17 | +| 5.2.2.3 Detailed behaviour of the SMS-IWMSC..... | 17 | +| 5.2.3 Report SM Delivery Status procedure..... | 17 | +| 5.2.3.1 General..... | 17 | +| 5.2.3.2 Detailed behaviour of the SMS-GMSC ..... | 19 | +| 5.2.3.3 Detailed behaviour of IP-SM-GW ..... | 19 | +| 5.2.3.4 Detailed behaviour of the HSS ..... | 19 | +| 5.3 Protocol specification..... | 19 | +| 5.3.1 Routing considerations ..... | 19 | +| 5.3.1.1 Requests from the SMS-GMSC or the SMS router ..... | 19 | +| 5.3.1.1.1 Introduction ..... | 19 | +| 5.3.1.1.2 Routing from the originating PLMN..... | 20 | +| 5.3.1.1.3 Routing in the HPLMN ..... | 20 | +| 5.3.1.2 Requests from the HSS ..... | 21 | +| 5.3.2 Commands ..... | 21 | +| 5.3.2.1 Introduction..... | 21 | +| 5.3.2.2 Command-Code values..... | 21 | +| 5.3.2.3 Send-Routing-Info-for-SM-Request (SRR) Command ..... | 22 | +| 5.3.2.4 Send-Routing-info-for-SM-Answer (SRA) Command ..... | 22 | +| 5.3.2.5 Alert-Service-Centre-Request (ALR) Command ..... | 23 | +| 5.3.2.6 Alert-Service-Centre-Answer (ALA) Command..... | 23 | +| 5.3.2.7 Report-SM-Delivery-Status-Request (RDR) Command ..... | 23 | +| 5.3.2.8 Report-SM-Delivery-Status-Answer (RDA) Command ..... | 24 | +| 5.3.3 AVPs..... | 24 | +| 5.3.3.1 General..... | 24 | +| 5.3.3.2 SM-RP-MTI..... | 26 | +| 5.3.3.3 SM-RP-SMEA ..... | 26 | +| 5.3.3.4 SRR-Flags..... | 26 | + +| | | | +|----------|------------------------------------------------------------------------------------|----| +| 5.3.3.5 | SM-Delivery-Not-Intended..... | 27 | +| 5.3.3.6 | Serving-Node ..... | 27 | +| 5.3.3.7 | Additional-Serving-Node..... | 28 | +| 5.3.3.8 | MWD-Status ..... | 28 | +| 5.3.3.9 | MME-Absent-User-Diagnostic-SM..... | 29 | +| 5.3.3.10 | MSC-Absent-User-Diagnostic-SM..... | 29 | +| 5.3.3.11 | SGSN-Absent-Subscriber-Diagnostic-SM ..... | 29 | +| 5.3.3.12 | Feature-List-ID AVP ..... | 29 | +| 5.3.3.13 | Feature-List AVP ..... | 29 | +| 5.3.3.14 | SM-Delivery-Outcome ..... | 29 | +| 5.3.3.15 | MME-SM-Delivery-Outcome ..... | 30 | +| 5.3.3.16 | MSC-SM-Delivery-Outcome..... | 30 | +| 5.3.3.17 | SGSN-SM-Delivery-Outcome..... | 30 | +| 5.3.3.18 | IP-SM-GW-SM-Delivery-Outcome ..... | 30 | +| 5.3.3.19 | SM-Delivery-Cause ..... | 30 | +| 5.3.3.20 | Absent-User-Diagnostic-SM ..... | 31 | +| 5.3.3.21 | RDR-Flags ..... | 31 | +| 5.3.3.22 | Maximum-UE-Availability-Time ..... | 31 | +| 5.3.3.23 | SMS-GMSC-Alert-Event..... | 31 | +| 5.3.3.24 | DRMP ..... | 31 | +| 5.3.3.25 | SMSF-3GPP-Absent-User-Diagnostic-SM ..... | 31 | +| 5.3.3.26 | SMSF-Non-3GPP-Absent-User-Diagnostic-SM ..... | 31 | +| 5.3.3.27 | SMSF-3GPP-SM-Delivery-Outcome ..... | 32 | +| 5.3.3.28 | SMSF-Non-3GPP-SM-Delivery-Outcome ..... | 32 | +| 5.3.3.29 | SMSF-3GPP-Number ..... | 32 | +| 5.3.3.30 | SMSF-Non-3GPP-Number ..... | 32 | +| 5.3.3.31 | SMSF-3GPP-Name..... | 32 | +| 5.3.3.32 | SMSF-Non-3GPP-Name ..... | 32 | +| 5.3.3.33 | SMSF-3GPP-Realm..... | 32 | +| 5.3.3.34 | SMSF-Non-3GPP-Realm..... | 33 | +| 5.3.3.35 | SMSF-3GPP-Address ..... | 33 | +| 5.3.3.36 | SMSF-Non-3GPP-Address ..... | 33 | +| 5.4 | User identity to HSS resolution..... | 33 | +| 6 | Diameter based SGd/Gdd interfaces between MME/SGSN and central SMS functions ..... | 34 | +| 6.1 | Introduction ..... | 34 | +| 6.2 | Procedures description ..... | 34 | +| 6.2.1 | MO Forward Short Message procedure ..... | 34 | +| 6.2.1.1 | General..... | 34 | +| 6.2.1.2 | Detailed behaviour of the MME, the SGSN and the IP-SM-GW ..... | 36 | +| 6.2.1.3 | Detailed behaviour of the SMS-IWMSC..... | 36 | +| 6.2.2 | MT Forward Short Message procedure..... | 37 | +| 6.2.2.1 | General..... | 37 | +| 6.2.2.2 | Detailed behaviour of the MME and the SGSN ..... | 38 | +| 6.2.2.3 | Detailed behaviour of the SMS-GMSC ..... | 39 | +| 6.2.3 | Alert Service Centre procedure ..... | 40 | +| 6.2.3.1 | General..... | 40 | +| 6.2.3.2 | Detailed behaviour of the MME and the SGSN ..... | 41 | +| 6.2.3.3 | Detailed behaviour of the SMS-GMSC ..... | 42 | +| 6.2.3.4 | Detailed behaviour of the SMS-Router ..... | 42 | +| 6.3 | Protocol specification..... | 42 | +| 6.3.1 | Routing considerations ..... | 42 | +| 6.3.1.1 | Routing for MO Forward SM messages:..... | 42 | +| 6.3.1.2 | Routing for MT Forward SM messages: ..... | 43 | +| 6.3.2 | Commands ..... | 43 | +| 6.3.2.1 | Introduction..... | 43 | +| 6.3.2.2 | Command-Code values..... | 43 | +| 6.3.2.3 | MO-Forward-Short-Message-Request (OFR) Command ..... | 44 | +| 6.3.2.4 | MO-Forward-Short-Message-Answer (OFA) Command..... | 44 | +| 6.3.2.5 | MT-Forward-Short-Message-Request (TFR) Command ..... | 45 | +| 6.3.2.6 | MT-Forward-Short-Message-Answer (TFA) Command..... | 45 | +| 6.3.3 | AVPs..... | 46 | + +| | | | +|-----------------------------------------------------------------------|----------------------------------------------------|-----------| +| 6.3.3.1 | General ..... | 46 | +| 6.3.3.2 | SC-Address ..... | 47 | +| 6.3.3.3 | SM-RP-UI ..... | 47 | +| 6.3.3.4 | TFR-Flags ..... | 47 | +| 6.3.3.5 | SM-Delivery-Failure-Cause ..... | 47 | +| 6.3.3.6 | SM-Enumerated-Delivery-Failure-Cause ..... | 48 | +| 6.3.3.7 | SM-Diagnostic-Info ..... | 48 | +| 6.3.3.8 | Feature-List-ID AVP ..... | 48 | +| 6.3.3.9 | Feature-List AVP ..... | 48 | +| 6.3.3.10 | SM-Delivery-Timer ..... | 48 | +| 6.3.3.11 | SM-Delivery-Start-Time ..... | 48 | +| 6.3.3.12 | OFR-Flags ..... | 48 | +| 6.3.3.13 | SMSMI-Correlation-ID ..... | 49 | +| 6.3.3.14 | HSS-ID ..... | 49 | +| 6.3.3.15 | Originating-SIP-URI ..... | 49 | +| 6.3.3.16 | Destination-SIP-URI ..... | 49 | +| 6.3.3.17 | Maximum-Retransmission-Time ..... | 49 | +| 6.3.3.18 | Requested-Retransmission-Time ..... | 49 | +| 6.3.3.19 | SMS-GMSC-Address ..... | 49 | +| 6.3.3.20 | DRMP ..... | 50 | +| 7 | Result Codes and Experimental-Result values ..... | 50 | +| 7.1 | General ..... | 50 | +| 7.2 | Success ..... | 50 | +| 7.3 | Permanent Failures ..... | 50 | +| 7.3.1 | General ..... | 50 | +| 7.3.2 | DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 50 | +| 7.3.3 | DIAMETER_ERROR_ABSENT_USER (5550) ..... | 50 | +| 7.3.4 | DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS (5551) ..... | 50 | +| 7.3.5 | DIAMETER_ERROR_FACILITY_NOT_SUPPORTED (5552) ..... | 50 | +| 7.3.6 | DIAMETER_ERROR_ILLEGAL_USER (5553) ..... | 51 | +| 7.3.7 | DIAMETER_ERROR_ILLEGAL_EQUIPMENT (5554) ..... | 51 | +| 7.3.8 | DIAMETER_ERROR_SM_DELIVERY_FAILURE (5555) ..... | 51 | +| 7.3.9 | DIAMETER_ERROR_SERVICE_NOT_SUBSCRIBED (5556) ..... | 51 | +| 7.3.10 | DIAMETER_ERROR_SERVICE_BARRED (5557) ..... | 51 | +| 7.3.11 | DIAMETER_ERROR_MWD_LIST_FULL (5558) ..... | 51 | +| 7.4 | Transient Failures ..... | 51 | +| 7.4.1 | General ..... | 51 | +| Annex A (normative): Diameter message priority mechanism ..... | | 52 | +| A.1 | General ..... | 52 | +| A.2 | S6c, SGd, Gdd interfaces ..... | 52 | +| Annex B (informative): Change history ..... | | 52 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document defines the Diameter-based interfaces specific to SMS when they are used in conjunction with the "SMS in MME" architecture specified in 3GPP TS 23.272 [2] or for SGSN supporting EPS interfaces, or the "SMS in 5GS" architecture specified in 3GPP TS 23.501 [21]. It comprises: + +- the Diameter application for the S6c interface between the HSS/UDM and the central SMS functions (SMS-GMSC, SMS Router) ; +- the Diameter application + - for the SGd interface between the MME/SMSF, the SMS-IWMSC, the SMS-GMSC and the SMS Router. + - for the Gdd interface between the SGSN, the SMS-IWMSC, the SMS-GMSC and the SMS Router. + +For the purpose of supporting SMS in 5GS, the UDM may implement the requirements specified in the present specification for HSS, with the following modification: + +- "HSS" is to be replaced with "UDM". + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". +- [3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [4] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [5] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details". +- [6] IETF RFC 2234: "Augmented BNF for Syntax Specifications: ABNF". +- [7] Void. +- [8] IETF RFC 5516: "Diameter Command Code Registration for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)". + +- [9] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [10] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane LCS". +- [11] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security ". +- [12] IETF RFC 4960: "Stream Control Transport Protocol". +- [13] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [14] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; Protocol details". +- [15] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications". +- [16] 3GPP TS 23.003: "Numbering, addressing and identification". +- [17] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2". +- [18] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [19] IETF RFC 7944: "Diameter Routing Message Priority". +- [20] IETF RFC 6733: "Diameter Base Protocol". +- [21] 3GPP TS 23.501:"System Architecture for the 5G System". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 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]. + +| | | +|-----------|-------------------------------------| +| ABNF | Augmented Backus-Naur Form | +| DRMP | Diameter Routing Message Priority | +| DSCP | Differentiated Services Code Point | +| IANA | Internet Assigned Numbers Authority | +| IP-SM-GW | IP Short Message Gateway | +| MWD | Message Waiting Data | +| RP | Relay layer Protocol | +| RP-MTI | RP Message Type Indicator | +| RP-SMEA | RP SME-Address | +| RP-UI | RP User Information | +| SM RL | Short Message Relay Layer | +| SMS-GMSC | Gateway MSC for SMS | +| SMS-IWMSC | Interworking MSC for SMS | +| SMSMI | SMS without MSISDN in IMS | + +# 4 General + +## 4.1 Introduction + +The SMS in MME architecture is described in 3GPP TS 23.272 [2] and the SMS in 5GS architecture is described in 3GPP TS 23.501 [21], have specified the reference points S6c and SGd. + +The clause 4 addresses Diameter aspects which are common to S6c, SGd and Gdd. + +## 4.2 Use of Diameter Base protocol + +The Diameter base protocol as specified in IETF RFC 6733 [20] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +## 4.3 Securing Diameter messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [11]. + +## 4.4 Accounting functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the S6c, SGd and Gdd interfaces. + +## 4.5 Use of sessions + +Diameter sessions shall be implicitly terminated over the S6c, SGd and Gdd interfaces. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol specified in IETF RFC 6733 [20] includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [20]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +## 4.6 Transport protocol + +Diameter messages over the S6c, SGd and Gdd interfaces shall make use of SCTP as specified in IETF RFC 4960 [12] as transport protocol. + +## 4.7 Advertising application support + +The MME, HSS, SMS-IWMSC, SMS-GMSC and SMS Router shall advertise support of the Diameter S6c Application over the S6c interface and of the Diameter SGd Application over the SGd interface by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The MME, SMS-GMSC and SMS Router shall additionally advertise support of the Diameter S6c Application over the SGd interface if they support the Alert Service Centre procedure between the MME, SMS-GMSC and SMS Router. + +The SGSN, SMS-IWMSC, SMS-GMSC and SMS Router shall advertise support of the Diameter SGd Application over the Gdd interface by including the value of the application identifier in the Auth-Application-Id AVP within the + +Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The SGSN, SMS-GMSC and SMS Router shall additionally advertise support of the Diameter S6c Application over the Gdd interface if they support the Alert Service Centre procedure between the SGSN, SMS-GMSC and SMS Router. + +The MTC-IWF and SMS-IWMSC shall advertise support of the Diameter SGd Application over the T4 interface if they support the MO-Forward-Short-Message procedure between the SMS-IWMSC and the MTC-IWF. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [20]. + +## 4.8 Diameter Application Identifier + +The S6c and the SGd/Gdd interface protocols shall be defined, each, as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP () is 10415. + +The Diameter application identifier assigned to the S6c Diameter application is 16777312 (allocated by IANA). + +The Diameter application identifier assigned to the SGd Diameter application, which is also applicable to the Gdd and T4 interfaces is 16777313 (allocated by IANA). + +## 4.9 Use of the Supported-Features AVP + +When new functionality is introduced on the S6c or SGd Diameter applications, it should be defined as optional. If backwards incompatible changes can not be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the S6c or SGd applications is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [5]. + +When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [5], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +The Table 5.3.3.13/1 defines the features applicable to the S6c interface for the feature list with a Feature-List-ID of 1. + +# --- 5 Diameter based S6c interface between HSS and central SMS functions + +## 5.1 Introduction + +The S6c interface enables the retrieval of routing information for the transfer of short messages, the report of status of the delivery status of a short message and the alerting of the SMS-SC between the HSS, the SMS-GMSC and the SMS Router as described in 3GPP TS 23.040 [3]. + +## 5.2 Procedures description + +### 5.2.1 Send Routing Info for SM procedure + +#### 5.2.1.1 General + +This procedure shall be used between the SMS-GMSC or the IP-SM-GW and the HSS to retrieve the routing information needed for routing the short message to the serving MSC or MME or SGSN or SMSF. This procedure is also used between the SMS-GMSC and the SMS Router or the IP-SM-GW, and between the HSS and the SMS Router or the IP-SM-GW in order to enforce routing of the SM delivery via the HPLMN of the receiving MS. + +This procedure is applicable to an IP-SM-GW for its SMS Router function when using the S6c interface. + +This procedure is used according to the call flows described in 3GPP TS 23.040 [2] clause 10. + +Table 5.2.1.1-1 specifies the involved information elements for the request. + +Table 5.2.1.1-2 specifies the involved information elements for the answer. + +This procedure is mapped to the commands Send-Routing-Info-for-SM-Request/Answer (SRR/SRA) in the Diameter application specified in clause 5.3.2. + +Table 5.2.1.1-1: Send Routing Info for SM Request + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|---------------------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MSISDN | MSISDN | C | This information element shall be present when the MSISDN exists and shall contain the MSISDN of the user. | +| IMSI | User-Name (See IETF RFC 6733 [20]) | C | This information element shall be present when the MSISDN does not exist and shall contain
- the IMSI of the user in the context of T4 device triggering (see 3GPP TS 23.682 [18]);
- or the HSS ID value in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]),. | +| SMSMI Correlation ID | SMSMI-Correlation-ID | C | This information element indicates by its presence that the request is sent in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]).
This information element shall contain the SIP-URI of the (MSISDN-less) destination user. The SIP-URI of the originating user and the HSS-ID shall be absent from this information element. | +| Service Centre Address | SC-Address | M | This information element shall contain the Service Centre address. | +| SM-RP-MTI | SM-RP-MTI | C | This information element shall contain the RP-Message Type Indicator of the Short Message. It is used to distinguish a SM sent to the mobile station in order to acknowledge an MO-SM initiated by the mobile from a normal MT-SM. | +| SM-RP-SMEA | SM-RP-SMEA | C | This information element shall contain the RP-Originating SME-address of the Short Message Entity that has originated the SM. This information element shall be present if the SMS-GMSC supports receiving of the two numbers from the HSS. Used by the short message service relay sub-layer protocol it shall be formatted according to the formatting rules of address fields as described in 3GPP TS 23 040 [2]. | +| SRR Flags | SRR-Flags | C | This Information Element contains a bit mask. See 5.3.3.4 for the meaning of the bits and the condition for each bit to be set or not. | +| SM-Delivery Not Intended | SM-Delivery-Not-Intended | O | This information element, when present, shall indicate that delivery of a short message is not intended. It further indicates whether only IMSI or only MCC+MNC are requested.
This information element may be set by entities that request the service without intending to deliver a short message, and shall be evaluated by the SMS Router and may be evaluated by the HSS. | +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this Information Element shall contain the list of features supported by the origin host. | + +Table 5.2.1.1-2: Send Routing Info for SM Answer + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M |

Result of the request.

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

Experimental-Result AVP shall be used for S6c errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. This information element shall contain the result of the operation with an indication of the success / errors.

The following errors are applicable in this case:

  • - Unknown User;
  • - Service Barred;
  • - Teleservice Not Provisioned;
  • - Absent User;
  • - Facility Not Supported.
| +| IMSI | User-Name (See IETF RFC 6733 [20]) | C |

This information element:

  • - either shall contain the IMSI of the user.
  • - or, if enforcement of routing an SM via the HPLMN of the receiving MS or UE is deployed, shall contain an MT Correlation ID instead of an IMSI when the service is used between SMS-GMSC and SMS Router (see 3GPP TS 23.040 [2] for more information).
  • - or, if the "SM-Delivery-Not-Intended" Information Element was present in the request with a value of "only MCC+MNC requested", may contain MCC+MNC+dummy MSIN.

This information element shall be present in a successful answer. This information element shall be present in an answer from the HSS to the IP-SM-GW, if an Absent User result is returned and the UNRI is not set.

| +| Serving-Node | Serving-Node | C |

If the "SM-Delivery-Not-Intended" Information Element was not present in the request, this information element shall contain the identity of one serving node on which the user is registered. This identity shall either be:

  • - the Diameter identity and the Diameter realm of the MME registered for MT SMS plus the E.164 number of the MME for MT SMS;
  • - or the ISDN number of the MSC;
  • - or the Diameter identity and the Diameter realm of the SGSN, if they are available, and the ISDN number of the SGSN,
  • - or the Diameter identity and the Diameter realm of the IP-SM-GW, if they are available, and the ISDN number of the IP-SM-GW;
  • - or the Diameter identity and the Diameter realm of the SMSF registered for 3GPP access, if they are available, and the E.164 number of the SMSF registered for 3GPP access;
  • - or the Diameter identity and the Diameter realm of the SMSF registered for non 3GPP access, if they are available, and the E.164 number of the SMSF registered for non 3GPP access.

If the "SM-Delivery-Not-Intended" Information Element was present in the request, this information element may be absent. This information element shall be present in a successful answer. See NOTE.

| +| LMSI | LMSI | C |

The HSS shall include the LMSI in a successful response, if the VLR has used the LMSI and if there is the ISDN number of an MSC in the answer.

| +| Additional Serving Node | Additional-Serving-Node | C |

This information element, when present shall either contain:

  • - the Diameter identity and the Diameter realm of the MME registered for MT SMS plus the E.164 number of the MME for MT SMS.
  • - or the ISDN number of the MSC
  • - or the Diameter identity and the Diameter realm of the SGSN, if they are available, and the ISDN number of the SGSN;
  • - or the Diameter identity and the Diameter realm of the SMSF registered for 3GPP access, if they are available, and the E.164 number of the SMSF registered for 3GPP access;
  • - or the Diameter identity and the Diameter realm of the SMSF
| + +| | | | | +|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | registered for non 3GPP access, if they are available, and the E.164 number of the SMSF registered for non 3GPP access.
It shall not contain information delivered in the Serving Node information element.
See NOTE. | +| User Identifier Alert | User-Identifier | C | This information element shall contain the MSISDN stored in the HSS, when available. | +| MWD Status | MWD-Status | C | This Information Element is sent when appropriate and shall contain a bit mask. See 5.3.3.8 for the meaning of the bits. | +| MME Absent User Diagnostic SM | MME-Absent-User-Diagnostic-SM | C | This information element shall contain the reason of the absence of the user when given by the MME and stored in the HSS | +| MSC Absent User Diagnostic SM | MSC-Absent-User-Diagnostic-SM | C | This information element shall contain the reason of the absence of the user when given by the MSC and stored in the HSS | +| SGSN Absent User Diagnostic SM | SGSN-Absent-User-Diagnostic-SM | C | This information element shall contain the reason of the absence of the user when given by the SGSN and stored in the HSS | +| Supported Features | Supported-Features
(See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | +| SMSF 3GPP Address | SMSF-3GPP-Address | C | If the "SM-Delivery-Not-Intended" Information Element was not present in the request, this information element shall contain the identity of the registered SMSF for 3GPP access.
If the "SM-Delivery-Not-Intended" Information Element was present in the request, this information element may be absent.
See NOTE. | +| SMSF Non 3GPP Address | SMSF-Non-3GPP-Address | C | If the "SM-Delivery-Not-Intended" Information Element was not present in the request, this information element shall contain the identity of the registered SMSF or Non-3GPP access.
If the "SM-Delivery-Not-Intended" Information Element was present in the request, this information element may be absent.
See NOTE. | +| SMSF 3GPP Absent User Diagnostic SM | SMSF-3GPP-Absent-User-Diagnostic-SM | C | This information element shall contain the reason of the absence of the user when given by the SMSF registered for 3GPP access.
See NOTE | +| SMSF Non 3GPP Absent User Diagnostic SM | SMSF-Non-3GPP-Absent-User-Diagnostic-SM | C | This information element shall contain the reason of the absence of the user when given by the SMSF registered for Non-3GPP access.
See NOTE | +| NOTE: | If the feature "SMSF-Support" is not supported by the SMS-GMSC, IP-SM-GW, or SMS Router, the AVPs SMSF-3GPP-Address, SMSF-Non-3GPP-Address, SMSF-3GPP-Absent-User-Diagnostic and SMSF-Non-3GPP-Absent-User-Diagnostic shall not be present. In this case the SMSF 3GPP Address and/or the SMSF Non 3GPP Address may be populated in the existing Serving-Node and Additional-Serving-Node AVPs as applicable. | | | + +#### 5.2.1.2 Detailed behaviour of the SMS-GMSC + +The SMS-GMSC shall make use of this procedure to retrieve the routing information needed for routing the short message to the serving MSC or MME or SGSN or SMSF registered for 3GPP access or SMSF registered for non-3GPP access for enforcing routing of the SM delivery via the SMS Router of HPLMN. + +It shall populate the information elements in the Send Routing Info for SM request according to the table 5.2.1.1-1. + +When the Send Routing Info for SM Request is sent by the SMS-GMSC to the HSS in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]), IMSI may not be available. In this case the IMSI information element shall be populated with the HSS-ID value. + +When receiving the Send Routing Info for-SM Answer, the SMS-GMSC or the SMS Router shall use the received Diameter address if the SMS-GMSC or the SMS Router transfers the terminating short message over the SGd or the Gdd interface. + +#### 5.2.1.3 Detailed behaviour of the HSS + +This clause describes the HSS behaviour when the HSS receives a Send Routing Info for SM request which is not forwarded to an SMS Router or an IP-SM-GW. + +The HSS shall check if the user identified by the MSISDN is known; otherwise, the HSS shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_USER\_UNKNOWN. + +The HSS shall check if a MT SMS Teleservice subscription exists; otherwise, the HSS shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_SERVICE\_NOT\_SUBSCRIBED. + +The HSS shall check if the user is not barred for receiving MT short messages; otherwise, the HSS shall return an Experimental-Result-Code set to DIAMETER\_SERVICE\_ERROR\_BARRED. + +The HSS shall check if one or more serving nodes are registered for MT SMS; otherwise, the HSS shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_ABSENT\_USER. If there is no serving node being registered for MT SMS and the Single-Attempt-Delivery flag in SRR-Flags AVP is set, the HSS shall not add the SC address into the MWD list. + +The HSS shall then return a Send Routing Info for SM answer with a Result-Code set to DIAMETER\_SUCCESSFUL that shall contain the addresses of the serving nodes that are registered for MT SMS according the following rules: + +- if the GPRS indicator is not set, only one serving node address shall be returned according to the SM transfer option where MME is considered as a MSC. The address of the MME, if returned, shall comprise the MME Diameter address and the MME Number for MT SMS. The address of the SMSF, if returned, shall comprise the SMSF Diameter address and the SMSF Number. +- if the GPRS indicator is set, two serving node addresses may be returned of which + - the Diameter address of the SGSN if available and the SGSN number, + - either the number of the MSC or the Diameter address and the number of the MME for MT SMS. +- when two serving g nodes addresses are returned, the HSS selects which serving node it will populate in the Serving Node information element and in the Additional Serving Node information elements. +- if the feature SMSF-Support is commonly supported, the HSS includes addresses of the registered SMSFs (if any) in the response, regardless of the GPRS indicator. + +NOTE: MSC and MME cannot be both registered as serving nodes for MT SMS at a given time (cf 3GPP TS 23.272 [2]) + +If the stored MSISDN number is not the same as the one received in the Send Routing Info for SM request service, the stored MSISDN number shall be included in the message. + +In the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]), if the HSS receives an SMSMI correlation ID, the HSS shall return the IP-SM-GW number and shall not forward the request to an IP-SM-GW. + +#### 5.2.1.4 Detailed behaviour of the SMS Router + +When receiving a Send Routing Info for SM request, the SMS Router shall: + +- send a Send Routing Info for SM request to the HSS to retrieve the routing information needed for routing the short message to the serving MSC or MME or SGSN or SMSF; +- if the Send Routing Info for SM answer received from HSS is successful, the SMS Router shall send a Send Routing Info for SM answer to the SMS-GMSC where + - the SMS router shall populate the same Serving Node and Additional Serving Node fields (i.e AVPs) as the ones it received in the Send Routing Info for SM answer from HSS, but with its own SMS Router number and its own SMS Router Diameter address; + +- if the Send Routing Info for SM answer received from HSS is not successful, the SMS Router shall send a Send Routing Info for SM answer to the SMS-GMSC with the same Diameter error result code. + +If the SMS Router receives some of the following information elements, User Identifier Alert, MWD Status, MSC Absent User Diagnostic SM, MME Absent User Diagnostic SM, SGSN Absent User Diagnostic SM, it shall transfer them in the Send-Routing Info for SM answer to the SMS-GMSC. + +### 5.2.2 Alert Service Centre procedure + +#### 5.2.2.1 General + +This procedure shall be used between the HSS and the SMS-IWMSC to indicate that the MS is now recognized by the PLMN to have recovered its operation to allow for an MT SMS delivery. This procedure is used according to the call flows described in 3GPP TS 23.040 [2] clause 10. + +Table 5.2.2.1-1 specifies the involved information elements for the request. + +Table 5.2.2.1-2 specifies the involved information elements for the answer. + +This procedure is mapped to the commands Alert-Service-Centre-Request/Answer (ALR/ALA) in the Diameter application specified in clause 5.3.2. + +**Table 5.2.2.1-1: Alert Service Centre Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------|---------------------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service Centre Address | SC-Address | M | This information element shall contain the Service Centre address received from the mobile station. | +| User Identifier Alert | User-Identifier | M | This information element shall contain:
  • - either the Alert MSISDN when it exists;
  • - or the IMSI in the context of T4 device triggering (see 3GPP TS 23.682 [18] if MSISDN is not available;
  • - or a dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [16]) if no MSISDN in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]).
| +| SMSMI Correlation ID | SMSMI-Correlation-ID | C | This information shall contain the SIP-URI of the destination user which is stored in the Message Waiting Data list in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]). The HSS-ID and the Originating SIP-URI shall be absent. | +| Maximum UE Availability Time | Maximum-UE-Availability-Time | C | This information element shall be included, if available. When present, it shall indicate the timestamp (in UTC) until which a UE using a power saving mechanism (such as extended idle mode DRX) is expected to be reachable for SM Delivery.
This information may be used by the SMS Center to prioritize the retransmission of Short Message to UEs using a power saving mechanism. | +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | + +Table 5.2.2.1-2: Alert Service Centre Answer + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|---------------------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This information element shall contain the result of the request. The Result-Code AVP shall be used for errors defined in the Diameter base protocol see IETF RFC 6733 [20]). The Experimental-Result AVP shall be used for S6c errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. This information element shall contain the result of the operation with an indication of the success / errors. No errors are defined for this case. | +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 5.2.2.2 Detailed behaviour of the HSS + +The HSS shall make use of this procedure to alert the service centre when the mobile user is active after a short message transfer has failed because the mobile user is not reachable, or when the UE has indicated that it has memory capacity to accept a short message. + +It is an operator option to resend an Alert Service Centre request to the SMS-IWMSC if the alert is unsuccessful. The number of repeat attempts and the interval between them is also an operator option. The service centre address should be purged from the MWD list if the alert is consistently unsuccessful. + +#### 5.2.2.3 Detailed behaviour of the SMS-IWMSC + +When receiving an Alert Service Centre request the SMS-IWMSC shall check whether the service centre address is known. If the service centre address is not valid, then no further action shall be taken. + +If the service centre address is valid, the SMS-IW-MSC generates an Alert Service Centre message towards the SMS Centre. + +### 5.2.3 Report SM Delivery Status procedure + +#### 5.2.3.1 General + +This procedure shall be used between the SMS-GMSC or the IP-SM-GW and the HSS to update the Message Waiting Data in the HSS or to inform the HSS of a successful SM transfer after polling. This procedure is invoked by the SMS-GMSC or the IP-SM-GW. + +This procedure is applicable to an IP-SM-GW for its SMS Router function when using the S6c interface. + +This procedure is used according to the call flows described in 3GPP TS 23.040 [2] clause 10. + +Table 5.2.3.1-1 specifies the involved information elements for the request. + +Table 5.2.3.1-2 specifies the involved information elements for the answer. + +This procedure is mapped to the commands Report-SM-Delivery-Status-Request/Answer (RDR/RDA) in the Diameter application specified in clause 5.3.2. + +Table 5.2.3.1-1: Report SM Delivery Status Request + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|---------------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identifier | User-Identifier | M | This information element shall contain:
  • - the MSISDN of the user when it exists.
  • - or the IMSI of the UE if MSISDN is not available in the context of a SM delivery status report following a T4 Submit Trigger (see 3GPP TS 23.682 [18]) .
  • - or the value of the HSS ID within the User-Name AVP in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]).
| +| SMSMI-Correlation ID | SMSMI-Correlation-ID | C | In a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]), this information element shall contain the SIP-URI of the (MSISDN-less) destination user. The originating SIP-URI and the HSS-ID shall be absent from this information element. | +| Service Centre Address | SC-Address | M | This information element shall contain the Service Centre address. | +| SM Delivery Outcome | SM-Delivery-Outcome | M | This information element shall contain the causes for setting the message waiting data in the HSS according to the network node(s) used for the SM delivery:
  • - MSC
  • - MME
  • - SGSN
  • - IP-SM-GW
  • - SMSF-3GPP
  • - SMSF-Non3GPP.
At least one cause shall be present. A cause originated from a MSC and a cause originated from a MME shall not be both present. When the cause is Absent User, the Absent User Diagnostic, if available, shall be associated to the cause. | +| RDR Flags | RDR-Flags | O | This Information Element contains a bit mask. See 5.3.3.21 for the meaning of the bits and the condition for each bit to be set or not. | +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this Information Element shall contain the list of features supported by the origin host. | + +Table 5.2.3.1-2: Report SM Delivery Status Answer + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|---------------------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This information element shall contain the Result of the request. The Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [20]). The Experimental-Result AVP shall be used for S6c errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. This information element shall contain the result of the operation with an indication of the success / errors. The following errors are applicable:
  • - Unknown User;
  • - Message Waiting List Full.
| +| MSISDN-Alert | User-Identifier | C | This information element shall contain the Alert MSISDN of the user if it is different from the MSISDN received in the request. | +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 5.2.3.2 Detailed behaviour of the SMS-GMSC + +The SMS-GMSC shall make use of this procedure if: + +- the reason received from the serving node for failure to deliver the message is absent user, unidentified user or SM delivery failure with error cause "UE memory capacity exceeded", and the SC address is not yet included in the MWD set, and the serving node did not request the SMS-GMSC to retransmit the Short Message at a later requested retransmission time, or +- the reason received from the serving node for failure to deliver the message is absent user, unidentified user or SM delivery failure with error cause "UE memory capacity exceeded", and the corresponding flag in the HSS (as indicated in the information received from HSS) is not set, or +- the reason received from the serving node (MSC/MME, SGSN or SMSF) for failure to deliver the message is absent user and the absent user diagnostic is different from the absent user diagnostic received from the HSS. + +If absent user diagnostic information (see 3GPP TS 23.040 [3]) is received with the absent user error indication then the SMS-GMSC shall relay this information to the HSS. + +#### 5.2.3.3 Detailed behaviour of IP-SM-GW + +The IP-SM-GW shall make use of this procedure if: + +- the reason for failure to deliver the message is absent user, unidentified user or SM delivery failure with error cause "UE memory capacity exceeded", and the SC address is not yet included in the MWD set, or +- the reason for failure to deliver the message is absent user, unidentified user or SM delivery failure with error cause "UE memory capacity exceeded", and the corresponding flag in the HSS (as indicated in the information received in the MAP\_INFORM\_SERVICE\_CENTRE) is not set, or +- the reason for failure to deliver the message is absent user and the absent user diagnostic is different from the absent user diagnostic received from the HSS. + +#### 5.2.3.4 Detailed behaviour of the HSS + +When receiving a Report SM Delivery Status request the HSS shall check if the user is known. + +If the user is not known, the HSS shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_USER\_UNKNOWN. + +If it is known, the HSS shall update the Message Waiting data as described in 3GPP TS 23.040 [3]. If the Single-Attempt-Delivery flag in RDR-Flags AVP is set, the HSS shall not add the SC address into the MWD list. + +If the message waiting data is full, the HSS shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_MWD\_LIST\_FULL. + +If the received MSISDN is different from the stored MSISDN, the HSS shall return the Alert MSISDN. + +## 5.3 Protocol specification + +### 5.3.1 Routing considerations + +#### 5.3.1.1 Requests from the SMS-GMSC or the SMS router + +##### 5.3.1.1.1 Introduction + +The clauses in 5.3.1.1 specify the use of the Diameter routing AVPs Destination-Realm and Destination-Host over the S6c interface for Diameter command requests from the SMS-GMSC or the SMS router or the IP-SM-GW (i.e. for the Send Routing Info for SM and the Report SM Delivery Status procedures). The clause 5.3.1.1 also applies for the Report SM Delivery Status request generated by a SMS-SC in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]). + +##### 5.3.1.1.2 Routing from the originating PLMN + +If the SMS-GMSC or the SMS router has stored or can obtain the address/name and the home network domain name of the HSS identified by the MSISDN or the IMSI, both the Destination-Realm and Destination-Host AVPs shall be present in the request. + +The SMS Router shall use the MCC/MNC values of the PLMN to which it belongs, to build the MCC/MNC based network domain as described in clause 19.2 of 3GPP TS 23.003 [16] and include it in the Destination-Realm AVP of the request. The request shall then be routed to the next Diameter node. + +If the SMS-GMSC can only obtain the MCC/MNC values from the MSISDN or the IMSI, the SMS-GMSC shall use them to build the MCC/MNC based network domain as described in clause 19.2 of 3GPP TS 23.003 [16] and include it in the Destination-Realm AVP of the request. The request shall then be routed to the next Diameter node. + +If the SMS-GMSC cannot obtain the MCC/MNC values from the MSISDN of the user, the SMS-GMSC may forward the request to a Diameter node within the same PLMN, the Destination Realm content being left to the PLMN operator choice. Then: + +- if a Diameter node in the routing path insides the PLMN of the SMS-GMSC can obtain the MCC/MNC values of the PLMN to which the user is subscribed to (i.e. when the number portability is resolved in the network of the SMS-GMSC), or +- if, otherwise, the Diameter node can obtain the MCC/MNC values of the PLMN associated to the CC and NDC codes of the MSISDN of the user, then +- the Diameter node shall use them to build the MCC/MNC based network domain as described in clause 19.2 of 3GPP TS 23.003 [16] and include it in the Destination-Realm AVP of the request. The request shall then be routed to the next Diameter node. + +If the MCC/MNC values of the PLMN associated to the CC and NDC codes of the MSISDN or the MCC/MNC values of the PLMN to which the user is subscribed to cannot be obtained in the PLMN of the SMS-GMSC, the request shall be replaced in the PLMN of the SMS-GMSC by an equivalent request routed through a MAP interface (e.g. via an IWF). + +NOTE 1: The inter PLMN routing principle is to reuse the routing based on a MCC/MNC based domain name as used by other Diameter applications such as S6a/d. It is assumed that obtaining the relevant MCC/MNC values from the MSISDN can be achieved in the PLMN to which the SMS-GMSC belongs. Otherwise MAP based routing is used. This routing principle may be completed with other routing solutions in the future. + +NOTE 2: The Number portability resolution in the PLMN of the SMS-GMSC can be handled by an intermediate Diameter agent consulting a Number Portability Database of the Network Portability domain to which the PLMN of the SMS-GMSC belongs. + +If the SMS-SC or the SMS-GMSC, in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]), has stored or can obtain the address/name and the home network domain name of the HSS identified by the HSS ID, both the Destination-Realm and Destination-Host AVPs shall be present in the request. + +If the SMS-SC or the SMS-GMSC, in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]), can only obtain the MCC/MNC values from the HSS ID, the SMS-SC shall use them to build the MCC/MNC based network domain as described in clause 19.2 of 3GPP TS 23.003 [16] and include it in the Destination-Realm AVP of the request. The request shall then be routed to the next Diameter node. + +NOTE: In a retry context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]), the SMS-SC gets the HSS-ID from the MO Forward Short Message request as described in clause 6.2.1. + +##### 5.3.1.1.3 Routing in the HPLMN + +When the request reaches a Diameter node in the home PLMN of the user and when multiple and separately addressable HSSs have been deployed in the home PLMN, the identity of the HSS that holds the subscriber data for a given user identified by its MSISDN may be retrieved by a user identity to HSS resolution mechanism as described in clause 5.4. + +When the request (i.e Send Routing Info for SM or Report SM Delivery Status) for SM occurs in the retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]), the Diameter identity of the HSS that holds + +the subscriber data for a given user may be retrieved by a user identity to HSS resolution mechanism as described in clause 5.4, where the HSS ID conveyed in the request is considered as a user identity. + +Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by an SMS-GMSC or a SMS Router. + +The HSS, when receiving a Send Routing Info for SM request, checks if an SMS Router is configured in the home network or if an IP-SM-GW has been registered for the user. If yes, the HSS shall act as a Diameter proxy and forward the request to the SMS Router or to the IP-SM-GW, by inserting the Diameter address of the SMS Router or of the IP-SM-GW as the Diameter destination address. If the Send Routing Info for SM request occurs in the retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]), the HSS shall return the IP-SM-GW address and shall not forward the request to an IP-SM-GW. + +If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes. + +#### 5.3.1.2 Requests from the HSS + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host over the S6c interface for Diameter command requests from the HSS (i.e. for the Alert SC procedure). + +If the HSS has stored the address/name of the SMS-SC and the associated home network domain name in the Message Waiting Data of the user, both the Destination-Realm and Destination-Host AVPs shall be present in the Diameter request. Otherwise the routing shall use MAP. + +### 5.3.2 Commands + +#### 5.3.2.1 Introduction + +This clause defines the Command code values and related ABNF for each command described for the S6c interface. + +#### 5.3.2.2 Command-Code values + +This clause defines the Command-Code values for the S6c interface application as allocated by IANA in the IETF RFC 5516 [8]. + +Every command is defined by means of the ABNF syntax IETF RFC 2234 [6], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [20]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [20] shall apply. + +The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node. + +NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with IETF RFC 6733 [20]. + +The following Command Codes are defined in this specification: + +**Table 5.3.2.2/1: Command-Code values for S6c** + +| Command-Name | Abbreviation | Code | Clause | +|-----------------------------------|--------------|---------|---------| +| Send-Routing-Info-for-SM-Request | SRR | 8388647 | 5.3.2.3 | +| Send-Routing-Info-for-SM-Answer | SRA | 8388647 | 5.3.2.4 | +| Alert-Service-Centre-Request | ALR | 8388648 | 5.3.2.5 | +| Alert-Service-Centre-Answer | ALA | 8388648 | 5.3.2.6 | +| Report-SM-Delivery-Status-Request | RDR | 8388649 | 5.3.2.7 | +| Report-SM-Delivery-Status-Answer | RDA | 8388649 | 5.3.2.8 | + +For these commands, the Application-ID field shall be set to 16777312 (application identifier of the S6c interface application allocated by IANA). + +#### 5.3.2.3 Send-Routing-Info-for-SM-Request (SRR) Command + +The Send-Routing-Info-for-SM-Request (SRR) command, indicated by the Command-Code field set to 8388647 and the "R" bit set in the Command Flags field, is sent from SMS-GMSC to HSS or SMS Router or from SMS Router to HSS. + +Message Format: + +``` +< Send-Routing-Info-for-SM-Request > ::= < Diameter Header: 8388647, REQ, PXY, 16777312 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +[ MSISDN ] +[ User-Name ] +[ SMSMI-Correlation-ID ] +*[ Supported-Features ] +[ SC-Address ] +[ SM-RP-MTI ] +[ SM-RP-SMEA ] +[ SRR-Flags ] +[ SM-Delivery-Not-Intended ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +#### 5.3.2.4 Send-Routing-info-for-SM-Answer (SRA) Command + +The Send-Routing-Info-for-SM-Answer (SRA) command, indicated by the Command-Code field set to 8388647 and the 'R' bit cleared in the Command Flags field, is sent from HSS to SMS-GMSC or SMS Router or from SMS Router to SMS-GMSC. + +Message Format: + +``` +< Send-Routing-info-for-SM-Answer > ::= < Diameter Header: 8388647, PXY, 16777312 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ User-Name ] +*[ Supported-Features ] +[ Serving-Node ] +[ Additional-Serving-Node ] +[ SMSF-3GPP-Address ] +[ SMSF-Non-3GPP-Address ] +[ LMSI ] +[ User-Identifier ] +[ MWD-Status ] +[ MME-Absent-User-Diagnostic-SM ] +[ MSC-Absent-User-Diagnostic-SM ] +[ SGSN-Absent-User-Diagnostic-SM ] +[ SMSF-3GPP-Absent-User-Diagnostic-SM ] +[ SMSF-Non-3GPP-Absent-User-Diagnostic-SM ] +*[ AVP ] +``` + +``` +[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +#### 5.3.2.5 Alert-Service-Centre-Request (ALR) Command + +The Alert-Service-Centre-Request (ALR) command, indicated by the Command-Code field set to 8388648 and the "R" bit set in the Command Flags field, is sent from the HSS to the SMS-IWMSC and from the MME or SGSN to the SMS-GMSC (possibly via an SMS Router). + +Message Format: + +``` +< Alert-Service-Centre-Request > ::= < Diameter Header: 8388648, REQ, PXY, 16777312 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +[ Destination-Host ] +{ Destination-Realm } +{ SC-Address } +{ User-Identifier } +[ SMSMI-Correlation-ID ] +[ Maximum-UE-Availability-Time ] +[ SMS-GMSC-Alert-Event ] +[ Serving-Node ] +*[ Supported-Features ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +#### 5.3.2.6 Alert-Service-Centre-Answer (ALA) Command + +The Alert-Service-Centre-Answer (ALA) command, indicated by the Command-Code field set to 8388648 and the 'R' bit cleared in the Command Flags field, is sent from the SMS-IWMSC to the HSS and from the SMS-GMSC to the MME or SGSN (possibly via an SMS Router). + +Message Format + +``` +< Alert-Service-Centre-Answer > ::= < Diameter Header: 8388648, PXY, 16777312 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +*[ Supported-Features ] +*[ AVP ] +[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +#### 5.3.2.7 Report-SM-Delivery-Status-Request (RDR) Command + +The Report-SM-Delivery-Status-Request (RDR) command, indicated by the Command-Code field set to 8388649 and the "R" bit set in the Command Flags field, is sent from SMS-GMSC or IP-SM-GW to HSS. + +Message Format: + +``` + +< Report-SM-Delivery-Status-Request > ::= < Diameter Header: 8388649, REQ, PXY, 16777312 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + *[ Supported-Features ] + { User-Identifier } + [ SMSMI-Correlation-ID ] + { SC-Address } + { SM-Delivery-Outcome } + [ RDR-Flags ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +#### 5.3.2.8 Report-SM-Delivery-Status-Answer (RDA) Command + +The Report-SM-Delivery-Status-Answer (RDA) command, indicated by the Command-Code field set to 8388649 and the 'R' bit cleared in the Command Flags field, is sent from HSS to SMS-GMSC or IP-SM-GW. + +Message Format + +``` + +< Report-SM-Delivery-Status-Answer > ::= < Diameter Header: 8388649, PXY, 16777312 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + *[ Supported-Features ] + [ User-Identifier ] + *[ AVP ] + [ Failed-AVP ] + *[ Proxy-Info ] + *[ Route-Record ] + +``` + +### 5.3.3 AVPs + +#### 5.3.3.1 General + +The following table specifies the Diameter AVPs defined for the S6c interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415). + +For all AVPs which contain bit masks and are of the type Unsigned32, e.g. TFR-Flags, bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used. + +Table 5.3.3.1/1: S6c specific Diameter AVPs + +| Attribute Name | AVP Code | Clause defined | Value Type | AVP Flag rules | | | | | +|-----------------------------------------|----------|----------------|------------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| SM-RP-MTI | 3308 | 5.3.3.2 | Enumerated | M, V | | | | No | +| SM-RP-SMEA | 3309 | 5.3.3.3 | OctetString | M, V | | | | No | +| SRR-Flags | 3310 | 5.3.3.4 | Unsigned32 | M, V | | | | No | +| SM-Delivery-Not-Intended | 3311 | 5.3.3.5 | Enumerated | M, V | | | | No | +| MWD-Status | 3312 | 5.3.3.8 | Unsigned32 | M, V | | | | No | +| MME-Absent-User-Diagnostic-SM | 3313 | 5.3.3.9 | Unsigned32 | M, V | | | | No | +| MSC-Absent-User-Diagnostic-SM | 3314 | 5.3.3.10 | Unsigned32 | M, V | | | | No | +| SGSN-Absent-User-Diagnostic SM | 3315 | 5.3.3.11 | Unsigned32 | M, V | | | | No | +| SM-Delivery-Outcome | 3316 | 5.3.3.14 | Grouped | M, V | | | | No | +| MME-SM-Delivery-Outcome | 3317 | 5.3.3.15 | Grouped | M, V | | | | No | +| MSC-SM-Delivery-Outcome | 3318 | 5.3.3.16 | Grouped | M, V | | | | No | +| SGSN-SM-Delivery-Outcome | 3319 | 5.3.3.17 | Grouped | M, V | | | | No | +| IP-SM-GW-SM-Delivery-Outcome | 3320 | 5.3.3.18 | Grouped | M, V | | | | No | +| SM-Delivery-Cause | 3321 | 5.3.3.19 | Enumerated | M, V | | | | No | +| Absent-User-Diagnostic-SM | 3322 | 5.3.3.20 | Unsigned32 | M, V | | | | No | +| RDR-Flags | 3323 | 5.3.3.21 | Unsigned32 | V | | | M | No | +| Maximum-UE-Availability-Time | 3329 | 5.3.3.22 | Time | V | | | M | No | +| SMS-GMSC-Alert-Event | 3333 | 5.3.3.23 | Unsigned32 | V | | | M | No | +| SMSF-3GPP-Absent-User-Diagnostic-SM | 3334 | 5.3.3.25 | Unsigned32 | V | | | M | No | +| SMSF-Non-3GPP-Absent-User-Diagnostic-SM | 3335 | 5.3.3.26 | Unsigned32 | V | | | M | No | +| SMSF-3GPP-SM-Delivery-Outcome | 3336 | 5.3.3.27 | Grouped | V | | | M | No | +| SMSF-Non-3GPP-SM-Delivery-Outcome | 3337 | 5.3.3.28 | Grouped | V | | | M | No | +| SMSF-3GPP-Number | 3338 | 5.3.3.29 | OctetString | V | | | M | No | +| SMSF-Non-3GPP-Number | 3339 | 5.3.3.30 | OctetString | V | | | M | No | +| SMSF-3GPP-Name | 3340 | 5.3.3.31 | DiameterIdentity | V | | | M | No | +| SMSF-Non-3GPP-Name | 3341 | 5.3.3.32 | DiameterIdentity | V | | | M | No | +| SMSF-3GPP-Realm | 3342 | 5.3.3.33 | DiameterIdentity | V | | | M | No | +| SMSF-Non-3GPP-Realm | 3343 | 5.3.3.34 | DiameterIdentity | V | | | M | No | +| SMSF-3GPP-Address | 3344 | 5.3.3.35 | Grouped | V | | | M | No | +| SMSF-Non-3GPP-Address | 3345 | 5.3.3.36 | Grouped | V | | | M | No | + +NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [20]. + +NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. + +The following table specifies the Diameter AVPs re-used from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within this interface. + +Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter Base Protocol specified in IETF RFC 6733 [20], do not need to be supported. The AVPs from Diameter base protocol specified in IETF RFC 6733 [20] are not included in table 5.3.3.1/2, but they may be re-used for this interface. + +Table 5.3.3.1/2: S6c re-used Diameter AVPs + +| Attribute Name | Reference | Comments | M-bit | +|---------------------------|---------------------|-------------------------------------------------------------|--------------| +| User-Name | IETF RFC 6733 [20] | | Must | +| MSISDN | 3GPP TS 23.329 [14] | | | +| SC-Address | 3GPP TS 29.338 | It is defined for the SGd/Gdd interface, see clause 6.3.3.2 | | +| LMSI | 3GPP TS 29.173 [10] | | | +| Serving-Node | 3GPP TS 29.173 [10] | See clause 5.3.3.6 | | +| MSC-Number | 3GPP TS 29.173 [10] | | | +| MME-Name | 3GPP TS 29.173 [10] | | | +| MME-Realm | 3GPP TS 29.173 [10] | | Must | +| MME-Number-for-MT-SMS | 3GPP TS 29.272 [4] | | Must | +| SGSN-Number | 3GPP TS 29.272 [4] | | | +| SGSN-Name | 3GPP TS 29.173 [10] | | | +| SGSN-Realm | 3GPP TS 29.173 [10] | | | +| Additional-Serving-Node | 3GPP TS 29.173 [10] | See clause 5.3.3.7 | | +| User-Identifier | 3GPP TS 29.336 [15] | | | +| SM-Delivery-Failure-Cause | 3GPP TS 29.338 | It is defined for the SGd/Gdd interface, see clause 6.3.3.5 | | +| IP-SM-GW-Name | 3GPP TS 29.336 [15] | | | +| IP-SM-GW-Number | 3GPP TS 29.336 [15] | | | +| SMSMI-Correlation-ID | 3GPP TS 29.338 | It is defined for the SGd/Gdd interface, see clause 6.3.3.2 | | +| Destination-SIP-URI | 3GPP TS 29.338 | It is defined for the SGd/Gdd interface, see clause 6.3.3.2 | | +| Supported-Features | 3GPP TS 29.229 [5] | | | +| Feature-List-ID | 3GPP TS 29.229 [5] | See clause 5.3.3.12 | | +| Feature-List | 3GPP TS 29.229 [5] | See clause 5.3.3.13 | | +| DRMP | IETF RFC 7944 [19] | see clause 5.3.3.24 | Must not set | + +NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies. + +NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. + +#### 5.3.3.2 SM-RP-MTI + +The SM-RP-MTI AVP is of type Enumerated and shall contain the RP-Message Type Indicator of the Short Message. The following values are defined: + +- SM\_DELIVER (0) +- SM\_STATUS\_REPORT (1) + +#### 5.3.3.3 SM-RP-SMEA + +The SM-RP-SMEA AVP is of type OctetString and shall contain the RP-Originating SME-address of the Short Message Entity that has originated the SM. It shall be formatted according to the formatting rules of the address fields described in 3GPP TS 23.040 [3]. + +#### 5.3.3.4 SRR-Flags + +The SRR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 5.3.3.4/1: + +**Table 5.3.3.4/1: SRR-Flags** + +| Bit | Name | Description | +|-----|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | GPRS-Indicator | This bit shall be set if the SMS-GMSC supports receiving of two serving nodes addresses from the HSS. | +| 1 | SM-RP-PRI | This bit shall be set if the delivery of the short message shall be attempted when a service centre address is already contained in the Message Waiting Data file | +| 2 | Single-Attempt-Delivery | This bit if set indicates that only one delivery attempt shall be performed for this particular SM. | + +NOTE 1: Bits not defined in this table shall be cleared by the sending entity and discarded by the receiving entity. + +#### 5.3.3.5 SM-Delivery-Not-Intended + +The SM-Delivery-Not-Intended AVP is of type Enumerated and shall indicate by its presence that delivery of a short message is not intended. It further indicates whether only IMSI or only MCC+MNC with the following values: + +- ONLY\_IMSI\_REQUESTED (0), +- ONLY\_MCC\_MNC\_REQUESTED (1). + +#### 5.3.3.6 Serving-Node + +The Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the targeted SMS user. It is originally defined in 3GPP TS 29.173 [10]. + +AVP format + +``` +Serving-Node ::= + [ SGSN-Name ] + [ SGSN-Realm ] + [ SGSN-Number ] + [ MME-Name ] + [ MME-Realm ] + [ MME-Number-for-MT-SMS ] + [ MSC-Number ] + [ IP-SM-GW-Number ] + [ IP-SM-GW-Name ] + [ IP-SM-GW-Realm ] + *[AVP] +``` + +The following combinations are allowed: + +- a) SGSN-Number +- b) SGSN-Name & SGSN-Realm & SGSN-Number if the HSS supports the "Gdd in SGSN" feature and has received the "Gdd in SGSN" indication over S6a or Gr interface from the SGSN (cf. 3GPP TS 29.272 [4] and 3GPP TS 29.002 [9]) +- c) MME-Name & MME-Realm & MME-Number-for-MT-SMS +- d) MSC-Number +- e) MSC-Number & MME-Name & MME-Realm + +- f) IP-SM-GW-Number +- g) IP-SM-GW-Number & IP-SM-GW-Name. + +#### 5.3.3.7 Additional-Serving-Node + +The Additional-Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the targeted user. It is originally defined in 3GPP TS 29.173 [10]. + +AVP format + +``` +Additional-Serving-Node ::= + [ SGSN-Name ] + [ SGSN-Realm ] + [ SGSN-Number ] + [ MME-Name ] + [ MME-Realm ] + [ MME-Number-for-MT-SMS ] + [ MSC-Number ] + *[AVP] +``` + +The following combinations are allowed: + +- a) SGSN-Number +- b) SGSN-Name & SGSN-Realm & SGSN-Number if the HSS supports the "Gdd in SGSN" feature and has received the "Gdd in SGSN" indication over S6a or Gr interface from the SGSN (cf. 3GPP TS 29.272 [4] and 3GPP TS 29.002 [9]) +- c) MME-Name & MME-Realm & MME-Number-for-MT-SMS +- d) MSC-Number +- e) MSC-Number & MME-Name & MME-Realm + +#### 5.3.3.8 MWD-Status + +The MWD-Status AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 5.3.3.8/1: + +**Table 5.3.3.8/1: MWD Status** + +| bit | name | Description | +|-------|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 0 | SC-Address Not included | This bit when set shall indicate that the SC Address has not been added to the Message Waiting Data in the HSS. | +| 1 | MNRF-Set | This bit, when set, shall indicate that the MNRF flag is set in the HSS | +| 2 | MCEF-Set | This bit, when set, shall indicate that the MCEF flag is set in the HSS. | +| 3 | MNRG-Set | This bit, when set, shall indicate that the MNRG flag is set in the HSS | +| 4 | MNR5G-Set | This bit, when set, shall indicate that the HSS/UDM is waiting for a reachability notification / registration from 5G serving nodes. | +| NOTE: | Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME. | | + +#### 5.3.3.9 MME-Absent-User-Diagnostic-SM + +The MME-Absent-User-Diagnostic-SM AVP is of type Unsigned32 and shall indicate the diagnostic explaining the absence of the user given by the MME. The values are defined in 3GPP TS 23.040 [3] clause 3.3.2. + +#### 5.3.3.10 MSC-Absent-User-Diagnostic-SM + +The MSC-Absent-User-Diagnostic-SM AVP is of type Unsigned32 and shall indicate the diagnostic explaining the absence of the user given by the MSC. The values are defined in 3GPP TS 23.040 [3] clause 3.3.2. + +#### 5.3.3.11 SGSN-Absent-Subscriber-Diagnostic-SM + +The SGSN-Absent-User-Diagnostic-SM AVP is of type Unsigned32 and shall indicate the diagnostic explaining the absence of the user given by the SGSN. The values are defined in 3GPP TS 23.040 [3] clause 3.3.2. + +#### 5.3.3.12 Feature-List-ID AVP + +The syntax of this AVP is defined in 3GPP TS 29.229 [5]. For this release, the Feature-List-ID AVP value shall be set to 1. + +#### 5.3.3.13 Feature-List AVP + +The syntax of this AVP is defined in 3GPP TS 29.229 [5]. A null value indicates that there is no feature used by the application. + +For the S6c application, the meaning of the bits shall be as defined in table 5.3.3.13/1 for the Feature-List-ID 1. + +**Table 5.3.3.13/1: Features of Feature-List-ID 1 used in S6c** + +| Feature bit | Feature | M/O | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | SMSF-Support | O |

SMSF-Support

This feature is applicable for the SRR/SRA command pair.
If the SMS-GMSC or IP-SM-GW or SMS-Router does not support this feature, the HSS shall not return SMSF related AVPs (SMSF-3GPP-Address, SMSF-Non-3GPP-Address, SMSF-3GPP-Absent-User-Diagnostic-SM, SMSF-Non-3GPP-Absent-User-Diagnostic-SM) in SRA, and when the UE is known not to be reachable for SMS via MSC/MME and/or SGSN, the HSS may populate AVPs within the Serving-Node AVP and within the Additional-Serving-Node AVP with available SMSF address information.

| +|

Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "SMSF-Support".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature.

| | | | + +#### 5.3.3.14 SM-Delivery-Outcome + +The SM-Delivery-Outcome AVP is of type Grouped. This AVP contains the result of the SM delivery. + +AVP format: + +SM-Delivery-Outcome ::= + +[ MME-SM-Delivery-Outcome ] + +[ MSC-SM-Delivery-Outcome ] + +[ SGSN-SM-Delivery-Outcome ] + +[ IP-SM-GW-SM-Delivery-Outcome ] + +[ SMSF-3GPP-SM-Delivery-Outcome ] + +[ SMSF-Non-3GPP-SM-Delivery-Outcome ] +\*[AVP] + +#### 5.3.3.15 MME-SM-Delivery-Outcome + +The MME-Delivery-Outcome AVP is of type grouped and shall indicate the outcome of the SM delivery for setting the message waiting data in the HSS when the SM delivery is with an MME. + +AVP format: + +MME-SM-Delivery-Outcome ::= > +[ SM-Delivery-Cause ] +[ Absent-User-Diagnostic-SM ] + +#### 5.3.3.16 MSC-SM-Delivery-Outcome + +The MSC-Delivery-Outcome AVP is of type grouped and shall indicate the outcome of the SM delivery for setting the message waiting data in the HSS when the SM delivery is with an MSC. + +AVP format: + +MSC-SM-Delivery-Outcome ::= +[ SM-Delivery-Cause ] +[ Absent-User-Diagnostic-SM ] + +#### 5.3.3.17 SGSN-SM-Delivery-Outcome + +The SGSN-Delivery-Outcome AVP is of type grouped and shall indicate the outcome of the SM delivery for setting the message waiting data in the HSS when the SM delivery is with an SGSN. + +AVP format: + +SGSN-SM-Delivery-Outcome ::= +[ SM-Delivery-Cause ] +[ Absent-User-Diagnostic-SM ] + +#### 5.3.3.18 IP-SM-GW-SM-Delivery-Outcome + +The IP-SM-GW-SM-Delivery-Outcome AVP is of type grouped and shall indicate the outcome of the SM delivery for setting the message waiting data when the SM delivery is with an IP-SM-GW. The following values are defined. + +AVP format: + +IP-SM-GW-SM-Delivery-Outcome ::= +[ SM-Delivery-Cause ] +[ Absent-User-Diagnostic-SM ] + +#### 5.3.3.19 SM-Delivery-Cause + +The SM-Delivery-Cause AVP is of type Enumerated and shall indicate the cause of the SMP delivery result. The following values are defined: + +- UE\_MEMORY\_CAPACITY\_EXCEEDED (0) +- ABSENT\_USER (1) + +- SUCCESSFUL\_TRANSFER (2) + +#### 5.3.3.20 Absent-User-Diagnostic-SM + +The Absent-User-Diagnostic-SM AVP is of type Unsigned32 and shall indicate the diagnostic explaining the absence of the subscriber. The values are defined in 3GPP TS 23.040 [3] clause 3.3.2. + +#### 5.3.3.21 RDR-Flags + +The RDR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 5.3.3.21/1: + +**Table 5.3.3.21/1: RDR-Flags** + +| Bit | Name | Description | +|----------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------------------------------------------------------------------------| +| 0 | Single-Attempt-Delivery | This bit if set indicates that only one delivery attempt shall be performed for this particular SM. | +| NOTE 1: Bits not defined in this table shall be cleared by the sending entity and discarded by the receiving entity. | | | + +#### 5.3.3.22 Maximum-UE-Availability-Time + +The Maximum-UE-Availability-Time is of type Time and in shall contain the timestamp (in UTC) until which a UE using a power saving mechanism (such as extended idle mode DRX) is expected to be reachable for SM Delivery. + +#### 5.3.3.23 SMS-GMSC-Alert-Event + +The SMS-GMSC-Alert-Event AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 5.3.3.23/1: + +**Table 5.3.3.23/1: SMS-GMSC-Alert-Event** + +| Bit | Name | Description | +|----------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------------------------------------------------------------------------------------------| +| 0 | UE-Available-For-MT-SMS | This bit, when set, shall indicate that the UE is now available for MT SMS | +| 1 | UE-Under-New-Serving-Node | This bit, when set, shall indicate that the UE has moved under the coverage of another MME or SGSN. | +| NOTE 1: Bits not defined in this table shall be cleared by the sending entity and discarded by the receiving entity. | | | + +#### 5.3.3.24 DRMP + +The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [19]. This AVP allows the HSS, the SMS-GMSC, the SMS-Router and the IP-SM-GW to indicate the relative priority of Diameter messages over the S6c interface. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message. + +#### 5.3.3.25 SMSF-3GPP-Absent-User-Diagnostic-SM + +The SMSF-3GPP-Absent-User-Diagnostic-SM AVP is of type Unsigned32 and shall indicate the diagnostic explaining the absence of the user given by the SMSF registered for 3GPP access. The values are defined in 3GPP TS 23.040 [3] clause 3.3.2. + +#### 5.3.3.26 SMSF-Non-3GPP-Absent-User-Diagnostic-SM + +The SMSF-Non-3GPP-Absent-User-Diagnostic-SM AVP is of type Unsigned32 and shall indicate the diagnostic explaining the absence of the user given by the SMSF registered for Non-3GPP access. The values are defined in 3GPP TS 23.040 [3] clause 3.3.2. + +#### 5.3.3.27 SMSF-3GPP-SM-Delivery-Outcome + +The SMSF-3GPP-SM-Delivery-Outcome AVP is of type grouped and shall indicate the outcome of the SM delivery for setting the message waiting data in the HSS when the SM delivery is with an SMSF registered for 3GPP access. + +AVP format: + +SMSF-3GPP-SM-Delivery-Outcome ::= > + +[ SM-Delivery-Cause ] + +[ Absent-User-Diagnostic-SM ] + +#### 5.3.3.28 SMSF-Non-3GPP-SM-Delivery-Outcome + +The SMSF-Non-3GPP-SM-Delivery-Outcome AVP is of type grouped and shall indicate the outcome of the SM delivery for setting the message waiting data in the HSS when the SM delivery is with an SMSF registered for Non-3GPP access. + +AVP format: + +SMSF-Non-3GPP-SM-Delivery-Outcome ::= > + +[ SM-Delivery-Cause ] + +[ Absent-User-Diagnostic-SM ] + +#### 5.3.3.29 SMSF-3GPP-Number + +The SMSF-3GPP-Number AVP is of type OctetString and it shall contain the ISDN number of the SMSF registered for 3GPP access. For further details on the definition of this AVP, see 3GPP TS 23.003 [3]. This AVP contains an SMSF-3GPP-Number in international number format as described in ITU-T Rec E.164 [13] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [9] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address. + +#### 5.3.3.30 SMSF-Non-3GPP-Number + +The SMSF-Non-3GPP-Number AVP is of type OctetString and it shall contain the ISDN number of the SMSF registered for Non-3GPP access. For further details on the definition of this AVP, see 3GPP TS 23.003 [3]. This AVP contains an SMSF-Non-3GPP-Number in international number format as described in ITU-T Rec E.164 [13] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [9] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address. + +#### 5.3.3.31 SMSF-3GPP-Name + +The SMSF-3GPP-Name AVP is of type DiameterIdentity and it shall contain the Diameter identity of the serving SMSF registered for 3GPP access. For further details on the encoding of this AVP, see IETF RFC 6733 [20]. + +#### 5.3.3.32 SMSF-Non-3GPP-Name + +The SMSF-Non-3GPP-Name AVP is of type DiameterIdentity and it shall contain the Diameter identity of the serving SMSF registered for Non-3GPP access. For further details on the encoding of this AVP, see IETF RFC 6733 [20]. + +#### 5.3.3.33 SMSF-3GPP-Realm + +The SMSF-3GPP-Realm AVP is of type DiameterIdentity and it shall contain the Diameter Realm Identity of the serving SMSF registered for 3GPP access. For further details on the encoding of this AVP, see IETF RFC 6733 [20]. + +#### 5.3.3.34 SMSF-Non-3GPP-Realm + +The SMSF-Non-3GPP-Realm AVP is of type DiameterIdentity and it shall contain the Diameter Realm Identity of the serving SMSF registered for Non-3GPP access. For further details on the encoding of this AVP, see IETF RFC 6733 [20]. + +#### 5.3.3.35 SMSF-3GPP-Address + +The SMSF-3GPP-Address AVP is of type Grouped. This AVP shall contain the information about the SMSF serving the targeted user for 3GPP access. + +AVP format + +``` +SMSF-3GPP-Address ::= + [ SMSF-3GPP-Number ] + [ SMSF-3GPP-Name ] + [ SMSF-3GPP-Realm ] + *[AVP] +``` + +#### 5.3.3.36 SMSF-Non-3GPP-Address + +The SMSF-Non-3GPP-Address AVP is of type Grouped. This AVP shall contain the information about the SMSF serving the targeted user for Non-3GPP access. + +AVP format + +``` +SMSF-Non-3GPP-Address ::= + [ SMSF-Non-3GPP-Number ] + [ SMSF-Non-3GPP-Name ] + [ SMSF-Non-3GPP-Realm ] + *[AVP] +``` + +## 5.4 User identity to HSS resolution + +The User identity to HSS resolution mechanism enables the SMS-GMSC or SMS Router in the home PLMN or Diameter proxy agents in the home PLMN to find the identity of the HSS that holds the subscriber data for a given user identified by its MSISDN or by its IMSI when multiple and separately addressable HSSs have been deployed in the home PLMN. The resolution mechanism is not required in PLMNs that utilise a single HSS. + +This User identity to HSS resolution mechanism may rely on routing capabilities provided by Diameter and be implemented in the home PLMN within dedicated Diameter Agents (Proxy Agents) responsible for determining the HSS identity based on the provided user identity. If this Diameter based implementation is selected by the home PLMN operator, the principles described below shall apply. + +When more than one independently addressable HSS are deployed in the home PLMN, each SMS-GMSC or SMS-Router network of the home PLMN shall be configured with the address/identity of a Diameter Agent (Proxy Agent) implementing this resolution mechanism. + +Diameter Relay agents and/or Diameter Proxy agents in the home PLMN receiving the Diameter signalling from SMS-GMSC located in other PLMNs shall be configured with the address/identity of a Diameter Agent (Proxy Agent) implementing this resolution mechanism. + +To get the HSS identity that holds the subscriber data for a given user identity in the home network, the Diameter request normally destined to the HSS shall be sent to the pre-configured address/identity of a Diameter Proxy agent supporting the User identity to HSS resolution mechanism. + +- If this Diameter request is received by a Diameter Redirect Agent, the Diameter Redirect Agent shall determine the HSS identity based on the provided user identity (i.e. MSISDN or IMSI) and shall return a notification of redirection towards the HSS identity, in response to the Diameter request. Multiple HSS identities may be included in the response, as specified in IETF RFC 6733 [20]. In such a case, the requesting Diameter entity shall send the Diameter request to the first HSS identity in the ordered list received in the Diameter response from the Diameter Redirect Agent. If no successful response to the Diameter request is received, the requesting Diameter entity shall send a Diameter request to the next HSS identity in the ordered list. This procedure shall be repeated until a successful response from an HSS is received. After the user identity to HSS resolution, the MME or the SGSN shall store the determined HSS identity/name/Realm and shall use it in further Diameter requests to the same user identity. +- If this Diameter request is received by a Diameter Proxy Agent, the Diameter Proxy Agent shall determine the HSS identity based on the provided user identity (i.e. MSISDN or IMSI) and shall forward the Diameter request directly to the HSS. In this case, the user identity to HSS resolution decision is communicated to the SMS-GMSC in the Origin-Host/Origin-Realm AVPs of the response. + +NOTE: Alternatives to the user identity to HSS resolution Diameter based implementation are outside the scope of this specification. + +The User identity to HSS resolution mechanism, in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]), applies as described in this clause for requests issued by the SMS-SC to a HSS and where the IMSI of the user is replaced by the HSS ID of the HSS storing the subscription data of the user. + +# --- 6 Diameter based SGd/Gdd interfaces between MME/SGSN and central SMS functions + +## 6.1 Introduction + +The SGd interface enables the transfer of short messages between the MME, the SMS-IWMSC, the SMS-GMSC and the SMS Router, and the alerting of the SMS-GMSC by the MME (possibly via an SMS Router), as described in 3GPP TS 23.040 [3]. + +The Gdd interface enables the transfer of short messages between the SGSN, the SMS-IWMSC, the SMS-GMSC and the SMS Router, and the alerting of the SMS-GMSC by the SGSN (possibly via an SMS Router) as described in 3GPP TS 23.040 [3]. + +## 6.2 Procedures description + +### 6.2.1 MO Forward Short Message procedure + +#### 6.2.1.1 General + +This procedure shall be used between the serving MME or SGSN or IP-SM-GW and the SMS-IWMSC to forward mobile originated short messages from a mobile user to a Service Centre. + +This procedure is used according to the call flows described in 3GPP TS 23.040 [3] clause 10. + +This procedure may also be used between the SMS-IWMSC and the MTC-IWF to forward mobile originated short messages from a mobile user to an MTC-IWF; see 3GPP TS 23.682 [18]. + +Table 6.2.1.1/1 specifies the involved information elements for the request. + +Table 6.2.1.1/2 specifies the involved information elements for the answer. + +This procedure is mapped to the commands MO-Forward-Short-Message-Request/Answer (OFR/OFA) in the Diameter application specified in clause 6.3.2. + +Table 6.2.1.1/1: MO Forward Short Message Request + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SM RP DA | SC-Address | M | When used between MME or SGSN or IP-SM-GW and SMS-IWMSC, this information element shall contain the Service Centre address received from the mobile station.
When used between SMS-IWMSC and MTC-IWF, this information element shall contain the MTC-IWF address as pre-configured in the SMS-SC. | +| SM RP OA | User-Identifier | M | This information element shall contain:
- the IMSI if it is available;
- the MSISDN of the user when it exists.
- a dummy MSISDN value in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]), if IMSI is not available. In this case the originating user is identified by the Originating SIP-URI (see SMSMI-Correlation ID). | +| SM RP UI | SM-RP-UI | M | This information element shall contain the short message transfer protocol data unit | +| SMSMI-Correlation ID | SMSMI-Correlation-ID | C | This information element indicates by its presence that the request is sent in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]).
When present, this information element shall contain an HSS-ID identifying the destination user's HSS, a Destination SIP-URI identifying the MSISDN-less destination user, and an Originating SIP-URI identifying the MSISDN-less originating user. | +| OFR Flags | OFR-Flags | C | This information element shall contain a bit mask. See 6.3.3.12 for the meaning of the bits. | +| SM Delivery Outcome | SM-Delivery-Outcome | C | This information element shall be present if the SMSMI Correlation ID is present and shall contain the IP-SM-GW SM Delivery Outcome with the causes for setting the message waiting data in the HSS. | +| Supported Features | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +NOTE: In the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]), the IP-SM-GW gets the HSS-ID and the SM Delivery Outcome from the SIP message coming from the IMS network of the destination user and indicating a temporary SMS delivery failure. + +Table 6.2.1.1/2: MO-Forward Short Message Answer + +| Information element name | Mapping to Diameter AVP | Cat | Description | +|---------------------------|-----------------------------------|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This information element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [20]). The Experimental-Result AVP shall be used for SGd/Gdd/T4 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. The following errors are applicable:
- Facility Not Supported;
- SM Delivery Failure. | +| SM Delivery Failure Cause | SM-Delivery-Failure-Cause | C | If the Experimental-Result-Code is set to DIAMETER_ERROR_SM_DELIVERY_FAILURE, this information element shall be present and indicate one of the following:
- unknown Service Centre/MTC-IWF address;
- Service Centre/MTC-IWF congestion;
- invalid Short Message Entity address;
- user not Service Centre/SCS-AS user.
It may be completed with a Diagnostic information element. | +| SM RP UI | SM-RP-UI | O | If present, this information element shall contain a short message transfer protocol data unit in the message delivery acknowledgement from the SMS-IWMSC to the MME or SGSN | +| Supported Features | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| External-Identifier | External-Identifier | C | This information element shall contain the External Identifier identifying the sender of the short message. Shall be present when the answer is sent over T4 to the SMS-IWMSC for charging. | + +#### 6.2.1.2 Detailed behaviour of the MME, the SGSN and the IP-SM-GW + +When the "SMS in MME" feature is applied for the UE, the MME shall make use of this procedure to forward mobile originated short messages received from the UE to the SMS-IWMSC associated to the SMS-SC indicated by the UE. + +When the SGSN supports the SMS service for the UE, the SGSN shall make use of this procedure to forward mobile originated short messages received from the UE to the SMS-IWMSC associated to the SMS-SC indicated by the UE. + +The IP-SM-GW shall make use of this procedure to forward mobile originated short messages received from the UE to the SMS-IWMSC associated to the SMS-SC indicated by the UE. This procedure shall be also used in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]), when the direct SMS delivery has failed, + +The MME or the SGSN shall check if the SMS related subscription data (e.g. ODB data and Call Barring) allows forwarding the short message. + +#### 6.2.1.3 Detailed behaviour of the SMS-IWMSC + +When receiving the MO Forward Short Message Request, the SMS-IWMSC shall check if the SMS-SC is known, if it is not, an Experimental-Result-Code set to DIAMETER\_ERROR\_SM\_DELIVERY\_FAILURE and a SM Delivery Failure Cause indicating "unknown Service Centre address" shall be returned to the MME or the SGSN. + +The SMS IWMSC shall then pass the short message to the addressed SMS-SC, or, if the destination user identity maps to an MTC-IWF based on a pre-configured mapping table, forward it to the appropriate MTC-IWF. + +If the SMS-SC or MTC-IWF returns a negative acknowledgement, an Experimental-Result-Code set to DIAMETER\_ERROR\_SM\_DELIVERY\_FAILURE and a SM Delivery Failure Cause indicating the cause given by the SMC-SC or MTC-IWF shall be returned to the MME or the SGSN. + +If the SMS-SC or MTC-IWF returns a positive acknowledgement to the SMS IWMSC, a Result-Code set to DIAMETER\_SUCCESS shall be returned to the MME or the SGSN. + +If a requested facility is not supported, an Experimental-Result-Code set to DIAMETER\_ERROR\_FACILITY\_NOT\_SUPPORTED shall be returned. + +### 6.2.2 MT Forward Short Message procedure + +#### 6.2.2.1 General + +This procedure shall be used between the SMS-GMSC and the serving MME or SGSN (transiting an SMS Router, if present) or IP-SM-GW to forward mobile terminated short messages. + +This procedure is used according to the call flows described in 3GPP TS 23.040 [3] clause 10. + +Table 6.2.2.1/1 specifies the involved information elements for the request. + +Table 6.2.2.1/2 specifies the involved information elements for the answer. + +This procedure is mapped to the commands MT-Forward-Short-Message-Request/Answer (TFR/TFA) in the Diameter application specified in clause 6.3.2. + +**Table 6.2.2.1/1: MT Forward Short Message Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-----------------------------|------------------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SM RP DA | User-Name
(See IETF RFC 6733 [20]) | M | This information element shall contain
- either an IMSI
- or a HSS ID value if an SMSMI-Correlation ID is present, the destination user being identified by the Destination SIP-URI within the SMSMI Correlation ID. | +| SM RP OA | SC-Address | M | This information element shall contain the Service Centre address. | +| SMSMI Correlation ID | SMSMI-Correlation-ID | C | This information element indicates by its presence that the request is sent in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]).
When present, this information element shall contain the Destination SIP-URI identifying the (MSISDN-less) destination user and the Originating SIP-URI identifying the (MSISDN-less) originating user. The HSS-ID shall be absent from this information element. | +| SM RP UI | SM-RP-UI | M | This information element shall contain the short message transfer protocol data unit. | +| MME Number for MT SMS | MME-Number-for-MT-SMS | C | This Information Element contains the ISDN number of the MME (see 3GPP TS 23.003 [3]) and shall be present when the request is sent to a MME. | +| SGSN Number | SGSN-Number | C | This Information Element contains the ISDN number of the SGSN (see 3GPP TS 23.003 [3]) and shall be present when the request is sent to a SGSN. | +| TFR-Flags | TFR-Flags | C | This information element shall contain a bit mask. Bit 0 indicates when set if the Service Centre has more messages to send | +| SM Delivery Timer | SM-Delivery-Timer | C | This information element should be included. When present, it shall indicate the SM Delivery Timer value set in the SMS-GMSC to the IP-SM-GW, MME or S4-SGSN. | +| SM Delivery Start Time | SM-Delivery-Start-Time | C | This information element should be included. When present, it shall indicate the timestamp (in UTC) at which the SM Delivery Supervision Timer was started in the SMS-GMSC. | +| Maximum Retransmission Time | Maximum-Retransmission-Time | O | This information element, when present, shall indicate the maximum retransmission time (in UTC) until which the SMS-GMSC is capable to retransmit the MT Short Message. | +| SMS-GMSC Address | SMS-GMSC-Address | C | This IE shall be present if the Maximum Retransmission Time IE is present in the message.
When present, this IE shall contain the E.164 number of the SMS-GMSC in the request sent by the SMS-GMSC or the E.164 number of the SMS Router in the request sent by the SMS Router. | +| Supported Features | Supported-Features
(See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | + +Table 6.2.2.1/2: MT Forward Short Message Answer + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------|---------------------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This information element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [20]). The Experimental-Result AVP shall be used for SGd/Gdd errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. The following errors are applicable:
  • - Unknown User;
  • - Absent User;
  • - User busy for MT SMS;
  • - Illegal User;
  • - Illegal Equipment;
  • - SM Delivery Failure.
| +| Absent User Diagnostic SM | Absent-User-Diagnostic-SM | O | This information element may be present when Experimental-Result-Code is set to DIAMETER_ERROR_ABSENT_USER and it shall contain the reason of the absence of the user given by the MME or the SGSN. | +| SM Delivery Failure Cause | SM-Delivery-Failure-Cause | C | If Experimental-Result-Code is set to DIAMETER_ERROR_SM_DELIVERY_FAILURE, this information element shall be present and indicate one of the following:
  • - memory capacity exceeded in the mobile equipment;
  • - UE error;
  • - mobile equipment not equipped to support the mobile terminated short message service.
It may be completed with a Diagnostic information element | +| SM RP UI | SM-RP-UI | O | If present, this information element shall contain a short message transfer protocol data unit in the message delivery acknowledgement from the MME to the Service Centre. | +| Requested Retransmission Time | Requested-Retransmission-Time | O | This information element may only be present if the Experimental-Result-Code is set to DIAMETER_ERROR_ABSENT_USER and if the Maximum Retransmission Time information element is present in the MT Forward Short Message Request. It may be included if the UE is using a power saving mechanism (such as extended idle mode DRX) and the UE is currently not reachable.

When present, this shall indicate the retransmission time (in UTC) at which the SMS-GMSC is requested to retransmit the MT Short Message. The Requested Retransmission Time shall not exceed the Maximum Retransmission Time received from the SMS-GMSC. | +| User Identifier Alert | User-Identifier | C | This IE shall be present in the message from the SMS Router to the SMS-GMSC, if the Requested Retransmission Time IE is present in the message. When present, this information shall contain an MT Correlation ID (encoded in the User-Name AVP). | +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 6.2.2.2 Detailed behaviour of the MME and the SGSN + +When receiving a MT Forward Short Message Request, the MME or the SGSN shall check if the IMSI is known, + +If it is not known, an Experimental-Result-Code set to DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +The MME or the SGSN shall attempt to deliver the short message to the UE. + +If the delivery of the short message to the UE is successful, the MME or the SGSN shall return a Result-Code set to DIAMETER\_SUCCESS. + +If the UE is not reachable via the MME, the MME shall set the MNRF flag and shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_ABSENT\_USER. + +If the UE is not reachable via the SGSN, the SGSN shall set the MNRG flag and shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_ABSENT\_USER. + +If the UE is using extended idle mode DRX (as defined in 3GPP TS 23.682 [18]) and the UE is expected to not respond to paging shortly or within the time frame indicated by the SM-Delivery-Timer and SM-Delivery-Start-Time IEs, the MME or SGSN may behave as specified above for a UE that is not reachable, while still paging the UE. + +NOTE 1: This mechanism is not intended for UEs which are known to wake up shortly (e.g. within the next 10 seconds) as enough time needs to elapse, between the sending of the MT Forward Short Message Answer and the subsequent Notification procedure towards the HSS when the UE becomes reachable, to enable the Report SM Delivery Status procedure to take place beforehand from the SMS-GMSC to the HSS. + +If the UE is using extended idle mode DRX (as defined in 3GPP TS 23.682 [18]) and the UE is expected to respond to paging shortly or within the time frame indicated by the SM-Delivery-Timer and SM-Delivery-Start-Time IEs, the MME or SGSN should page the UE and attempt to deliver the short message to the UE. + +If the UE is using a power saving mechanism such as extended idle mode DRX (see 3GPP TS 23.682 [18]), and if the MT Forward Short Message Request includes the Maximum-Retransmission-Time AVP, the MME or SGSN may return an MT Forward Short Message Answer with the Experimental-Result-Code set to DIAMETER\_ERROR\_ABSENT\_USER and with the Requested-Retransmission-Time AVP requesting the SMS-GMSC to retransmit the Short Message at a later time prior to the Maximum-Retransmission-Time. In that case, the MME or SGSN shall store (if not already done) the Origin-Host, the Origin-Realm and the SMS-GMSC address received in request and shall not set the MNRF or MNRG flag. + +NOTE 2: This mechanism does not cause additional signalling at the HSS to retransmit the Short Message. + +If the delivery of the mobile terminated short message failed because of memory capacity exceeded or UE error or UE not SM equipped, the MME or the SGSN shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_SM\_DELIVERY\_FAILURE complemented with a SM Delivery Failure Cause indication. + +If a requested facility is not supported, the MME or the SGSN shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_FACILITY\_NOT\_SUPPORTED. + +If the user is busy for MT SMS, i.e. the mobile terminated short message transfer cannot be completed because: + +- another mobile terminated short message transfer is going on and the delivery node does not support message buffering; or +- another mobile terminated short message transfer is going on and it is not possible to buffer the message for later delivery; or +- the message was buffered but it is not possible to deliver the message before the expiry of the buffering time defined in 3GPP TS 23.040 [3], + +the MME or the SGSN shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_USER\_BUSY\_FOR\_MT\_SMS. + +If the delivery of the mobile terminated short message failed because the mobile station failed authentication, the MME or the SGSN shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_ILLEGAL\_USER. + +If the delivery of the mobile terminated short message failed because an IMEI check failed, i.e. the IMEI was blacklisted or not white-listed, the MME or the SGSN shall return an Experimental-Result-Code set to DIAMETER\_ERROR\_ILLEGAL\_EQUIPMENT. + +#### 6.2.2.3 Detailed behaviour of the SMS-GMSC + +The SMS-GMSC shall make use of this procedure over the SGd interface or over the Gdd interface for the delivery of a MT short message when it has selected the serving node of which it obtained the Diameter Identity from the answer of the Send Routing Info for SM procedure. + +NOTE: The SMS-GMSC is not aware that the MT Forward Short Message Request may be routed to a SMS router. + +The SMS-GMSC may include the Maximum-Retransmission-Time AVP in the MT Forward Short Request to indicate that it is capable to retransmit the Short Message until the indicated maximum retransmission time, if the following conditions are fulfilled: + +- the destination user pertains to the PLMN of the SMS-GMSC; and +- if an SMS Router is used for MT SMS sent to destination users pertaining to the PLMN of the SMS-GMSC, the SMS Router is known to support the Alert Service Centre procedure specified in clause 6.2.3. + +The SMS-GMSC shall include its E.164 number in the SMS-GMSC address in the request if it also includes the Maximum-Retransmission-Time AVP. + +When the SMS router has received a MT Forward Short Message from the SMS-GMSC and the SMS Router has selected the MME or the SGSN for delivery, the SMS Router shall forward it to the MME or the SGSN. + +If the MT Forward Short Message Request includes the Maximum-Retransmission-Time AVP, the SMS Router shall store the SMS-GMSC Diameter Identity (received in the Origin-Host and Origin-Realm AVPs) and the SMS-GMSC address received in the request and replace them by its SMS Router Diameter Identity (in the Origin-Host and Origin-Realm AVPs) and SMS Router address (E.164 number) when forwarding the request to the MME or SGSN. + +When a MT Forward Short Message Answer is received from the MME, the SMS Router shall forward it to the SMS-GMSC. + +If the MT Forward Short Message Answer includes the Requested-Retransmission-Time AVP, the SMS Router shall include a User Identifier Alert AVP when forwarding the answer to the SMS-GMSC. + +NOTE: The User Identifier Alert is further used in the Alert Service Centre procedure specified in clause 6.2.3 to enable the SMS-GMSC to identify and retransmit all pending MT SMS messages towards the destination user. + +### 6.2.3 Alert Service Centre procedure + +#### 6.2.3.1 General + +This procedure shall be used between the MME or SGSN and the SMS-GMSC, possibly via an SMS Router, to indicate that a UE, for which one or more MT SMS have been requested to be retransmitted at a later time, is now available for MT SMS delivery or that it has moved under the coverage of another MME or SGSN. This procedure is used according to the call flows described in 3GPP TS 23.040 [2] clause 10. + +Table 6.2.3.1-1 specifies the involved information elements for the request. + +Table 6.2.3.1-2 specifies the involved information elements for the answer. + +This procedure is mapped to the commands Alert-Service-Centre-Request/Answer (ALR/ALA) in the Diameter application specified in clause 5.3.2. + +Table 6.2.3.1-1: Alert Service Centre Request + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------|---------------------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service Centre Address | SC-Address | M | This IE shall contain the E.164 number of the SMS-GMSC (or SMS Router) previously received in the SMS-GMSC Address IE in the MT Forward Short Message Request. | +| User Identifier Alert | User-Identifier | M | This IE shall contain:
  • - the IMSI when the request is sent from the MME or SGSN,
  • - the User Identifier Alert previously sent in the MT Forward Short Message Answer, when the request is sent from the SMS Router to the SMS-GMSC,
encoded in the User-Name AVP. | +| SMS-GMSC Alert Event | SMS-GMSC-Alert-Event | M | This IE shall contain the type of event that caused the Alert Service Centre Request to the SMS-GMSC:
  • - UE is available for MT SMS;
  • - UE has moved under the coverage of another MME or SGSN.
| +| New Serving Node Identity | Serving-Node | C | This IE shall be present if available and if the SMS-GMSC Alert Event indicates that the UE has moved under the coverage of another MME or SGSN.
When present, this IE shall contain the Diameter Identity and/or the E.164 number of the new serving node of the UE.
It shall be encoded as:
  • - an MME-Name, MME Realm and MME-Number-for-MT-SMS, if the new serving node is an MME;
  • - an SGSN-Number and, an SGSN-Name and SGSN Realm if available, if the new serving node is an SGSN.
| +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | + +Table 6.2.3.1-2: Alert Service Centre Answer + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|---------------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This information element shall contain the result of the request.
The Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [20]).
The Experimental-Result AVP shall be used for S6c errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. This information element shall contain the result of the operation with an indication of the success / errors. No errors are defined for this case. | +| Supported Features | Supported-Features (See 3GPP TS 29.229 [5]) | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 6.2.3.2 Detailed behaviour of the MME and the SGSN + +The MME or SGSN shall make use of this procedure to alert the SMS-GMSC when the UE, for which one or more MT SMS have been requested to be retransmitted at a later time, becomes available for MT SMS delivery or moves under the coverage of another MME or SGSN prior to the requested SM retransmission time. + +The MME or SGSN shall delete the stored SMS-GMSC Diameter Identity (i.e. Origin-Host and Origin-Realm) and address after the Alert Service Centre procedure is completed. + +#### 6.2.3.3 Detailed behaviour of the SMS-GMSC + +When receiving an Alert Service Centre request, the SMS-GMSC shall retransmit pending MT SMS(s) for the destination user identified by the User Identifier Alert, to the same serving node if the SMS-GMSC Alert Event indicates that the UE is available for MT SMS, or to the new serving node if the SMS-GMSC Alert Event indicates that the UE has moved under the coverage of another MME or SGSN. In the latter case, if no New Serving Node Identity is received in the Alert Service Centre request, the SMS-GMSC shall initiate a Send Routing Info for SM procedure to retrieve the new serving node 's address from the HSS. + +#### 6.2.3.4 Detailed behaviour of the SMS-Router + +When receiving an Alert Service Centre request, the SMS-Router shall replace the IMSI received in the User Identifier Alert by the User Identifier Alert previously sent in the MT Forward Short Message Answer, and forward that request to the SMS-GMSC. + +## 6.3 Protocol specification + +### 6.3.1 Routing considerations + +#### 6.3.1.1 Routing for MO Forward SM messages: + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host over the SGd or Gdd interfaces for the Diameter command requests from the MME or from the SGSN (i.e. for the MO forward SM procedure). + +Also, this clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host over the T4 interface for the Diameter command requests from the SMS-IWMSC (i.e. for the MO forward SM procedure). + +This clause also applies for the Diameter command MO forward SM request from the IP-SM-GW towards an SMS-SC/SMS-IWMSC, including the case where the MO forward SM request occurs in the retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [17]). MME or SGSN is replaced by IP-SM-GW in the text of this clause. + +If the MME or the SGSN, from the SMS-SC E.164 number received from the UE, can obtain the address/name of the SMS-IWMSC and the associated home network domain name (e.g. by local configuration), both the Destination-Realm and Destination-Host AVPs shall be present in the request. + +If the MME or the SGSN, from the SMS-SC E.164 number received from the UE, can only obtain the MCC/MNC values of the PLMN to which the SMS-SC belongs, the MME or the SGSN shall use them to build the MCC/MNC based network domain as described in clause 19.2 of 3GPP TS 23.003 [16] and include it in the Destination-Realm AVP of the request. The request shall then be routed to the next Diameter node. + +If the MME or the SGSN cannot obtain the MCC/MNC values from the SMS-SC E.164 number, the MME or the SGSN shall forward the request to a Diameter node within the same PLMN, the Destination Realm content being left to the PLMN operator choice. Then: + +- if a Diameter node in the routing path insides the PLMN of the MME can obtain the MCC/MNC values of the PLMN to which the SMS-SC belongs, +- it shall use them to build the MCC/MNC based network domain as described in clause 19.2 of 3GPP TS 23.003 [16] and include it in the Destination-Realm AVP of the request. The request shall then be routed to the next Diameter node. + +If the MCC/MNC values of the PLMN to which the SMS-SC belongs cannot be obtained in the PLMN of the MME or the SGSN, the request shall be replaced in the PLMN of the MME or the SGSN by an equivalent request routed through a MAP interface (e.g. via an IWF). + +NOTE 1: The inter PLMN routing principle is to reuse the routing based on a MCC/MNC based domain name as used by other Diameter applications such as S6a/d. It is assumed that obtaining the relevant MCC/MNC values from the E.164 number of the SMS-SC can be achieved in the PLMN which the MME belongs to. Otherwise a MAP based routing is used. This routing principle may be completed with other routing solutions in the future. + +Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by an MME or a SGSN. + +The SMS-IWMSC shall be able to obtain the address/name of the MTC-IWF and the associated home network domain name from the destination SME address included in the MO TPDU (e.g. by local configuration); therefore both the Destination-Realm and Destination-Host AVPs shall be present in the request. + +#### 6.3.1.2 Routing for MT Forward SM messages: + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host for the Diameter command requests from the SMS-GMSC or the SMS Router (i.e. for the MT forward SM procedure). + +- if the SMS-GMSC has received the Diameter address/name of an MME or of the SGSN in the answer to its interrogation to the HSS/HLR for retrieving routing information and if it selects this serving node, it shall use it to populate the Destination-Realm and Destination-Host AVPs. +- If the SMS Router has received the Diameter address/name of the MME or of the SGSN in the answer to its interrogation to the HSS/HLR for retrieving routing information and if it selects this serving node, it shall use this Diameter address/name to populate the Destination-Realm and Destination-Host AVPs. + +Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by an SMS-GMSC or a SMS router. + +### 6.3.2 Commands + +#### 6.3.2.1 Introduction + +This clause defines the Command code values and related ABNF for each command described for the SGd interface. + +#### 6.3.2.2 Command-Code values + +This clause defines the Command-Code values for the SGd interface application as allocated by IANA in the IETF RFC 5516 [8], the SGd interface application being used over the SGd and Gdd interfaces. The Alert Service Centre procedure used over the SGd and Gdd interfaces also uses commands of the S6c interface application. + +Every command is defined by means of the ABNF syntax IETF RFC 2234 [6], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [20]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [20] shall apply. + +The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node. + +NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to ensure potential interoperability issues with Diameter agents non-compliant with IETF RFC 6733 [20]. + +The following Command Codes are defined in this specification: + +**Table 6.3.2.2/1: Command-Code values for SGd/Gdd** + +| Command-Name | Abbreviation | Code | Clause | +|----------------------------------|--------------|---------|---------| +| MO-Forward-Short-Message Request | OFR | 8388645 | 6.3.2.3 | +| MO-Forward-Short-Message Answer | OFA | 8388645 | 6.3.2.4 | +| MT-Forward-Short-Message Request | TFR | 8388646 | 6.3.2.5 | +| MT-Forward-Short-Message Answer | TFA | 8388646 | 6.3.2.6 | +| Alert-Service-Centre-Request | ALR | 8388648 | 5.3.2.5 | +| Alert-Service-Centre-Answer | ALA | 8388648 | 5.3.2.6 | + +For these commands, the Application-ID field shall be set to 16777313 (application identifier of the SGd interface application, allocated by IANA), except for the ALR/ALA commands for which the Application-ID field shall be set to 16777312 (application identifier of the S6c interface application, allocated by IANA). + +#### 6.3.2.3 MO-Forward-Short-Message-Request (OFR) Command + +The MO-Forward-Short-Message-Request (OFR) command, indicated by the Command-Code field set to 8388645 and the "R" bit set in the Command Flags field, is sent from the MME / SGSN to the SMS-IWMSC and it is also sent from the SMS-IWMSC to the MTC-IWF. + +Message Format + +``` +< MO-Forward-Short-Message-Request > ::= < Diameter Header: 8388645, REQ, PXY, 16777313 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + [ Destination-Host ] + { Destination-Realm } + { SC-Address } + [ OFR-Flags ] + *[ Supported-Features ] + { User-Identifier } + { SM-RP-UI } + [ SMSMI-Correlation-ID ] + [ SM-Delivery-Outcome ] + *[ AVP ] + *[ Proxy-Info ] + *[ Route-Record ] +``` + +#### 6.3.2.4 MO-Forward-Short-Message-Answer (OFA) Command + +The MO-Forward-Short-Message-Answer Command (OFA) command, indicated by the Command-Code field set to 8388645 and the 'R' bit cleared in the Command Flags field, is sent from the SMS-IWMSC to the MME / SGSN and it is also sent from the MTC-IWF to the SMS-IWMSC. + +Message Format + +``` +< MO-Forward-Short-Message-Answer > ::= < Diameter Header: 8388645, PXY, 16777313 > + < Session-Id > + [ DRMP ] + [ Vendor-Specific-Application-Id ] + [ Result-Code ] + [ Experimental-Result ] + { Auth-Session-State } + { Origin-Host } + { Origin-Realm } + *[ Supported-Features ] + [ SM-Delivery-Failure-Cause ] + [ SM-RP-UI ] +``` + +``` +[ External-Identifier ] +*[ AVP ] +[ Failed-AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +#### 6.3.2.5 MT-Forward-Short-Message-Request (TFR) Command + +The MT-Forward-Short-Message-Request (TFR) command, indicated by the Command-Code field set to 8388646 and the "R" bit set in the Command Flags field, is sent from the SMS-GMSC to the MME / SGSN (transiting an SMS Router, if present). + +Message Format + +``` +< MT-Forward-Short-Message-Request > ::= < Diameter Header: 8388646, REQ, PXY, 16777313 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +{ Destination-Host } +{ Destination-Realm } +{ User-Name } +*[ Supported-Features ] +[ SMSMI-Correlation-ID ] +{ SC-Address } +{ SM-RP-UI } +[ MME-Number-for-MT-SMS ] +[ SGSN-Number ] +[ TFR-Flags ] +[ SM-Delivery-Timer ] +[ SM-Delivery-Start-Time ] +[ Maximum-Retransmission-Time ] +[ SMS-GMSC-Address ] +*[ AVP ] +*[ Proxy-Info ] +*[ Route-Record ] +``` + +#### 6.3.2.6 MT-Forward-Short-Message-Answer (TFA) Command + +The MT-Forward-Short-Message-Answer Command (TFA) command, indicated by the Command-Code field set to 8388646 and the 'R' bit cleared in the Command Flags field, is sent from the MME / SGSN to the SMS-GMSC (transiting an SMS Router, if present). + +Message Format + +``` +< MT-Forward-Short-Message-Answer > ::= < Diameter Header: 8388646, PXY, 16777313 > +< Session-Id > +[ DRMP ] +[ Vendor-Specific-Application-Id ] +[ Result-Code ] +[ Experimental-Result ] +{ Auth-Session-State } +{ Origin-Host } +{ Origin-Realm } +*[ Supported-Features ] +[ Absent-User-Diagnostic-SM ] +[ SM-Delivery-Failure-Cause ] +[ SM-RP-UI ] +[ Requested-Retransmission-Time ] +[ User-Identifier ] +``` + +\*[ AVP ] + [ Failed-AVP ] + \*[ Proxy-Info ] + \*[ Route-Record ] + +### 6.3.3 AVPs + +#### 6.3.3.1 General + +The following table specifies the Diameter AVPs defined for the SGd/Gdd interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415). + +For all AVPs which contain bit masks and are of the type Unsigned32, e.g., TFR-Flags, bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used. + +**Table 6.3.3.1/1: SGd/Gdd specific Diameter AVPs** + +| Attribute Name | AVP Code | Clause defined | Value Type | AVP Flag rules | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|-------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| SC-Address | 3300 | 6.3.3.2 | OctetString | M, V | | | | No | +| SM-RP-UI | 3301 | 6.3.3.3 | OctetString | M, V | | | | No | +| TFR-Flags | 3302 | 6.3.3.4 | Unsigned32 | M, V | | | | No | +| SM-Delivery-Failure-Cause | 3303 | 6.3.3.5 | Grouped | M, V | | | | No | +| SM-Enumerated-Delivery-Failure-Cause | 3304 | 6.3.3.6 | Enumerated | M, V | | | | No | +| SM-Diagnostic-Info | 3305 | 6.3.3.7 | OctetString | M, V | | | | No | +| SM-Delivery-Timer | 3306 | 6.3.3.10 | Unsigned32 | M, V | | | | No | +| SM-Delivery-Start-Time | 3307 | 6.3.3.11 | Time | M, V | | | | No | +| SMSMI-Correlation-ID | 3324 | 6.3.3.13 | Grouped | V | | | M | No | +| HSS-ID | 3325 | 6.3.3.14 | UTF8String | V | | | M | No | +| Originating-SIP-URI | 3326 | 6.3.3.15 | UTF8String | V | | | M | No | +| Destination-SIP-URI | 3327 | 6.3.3.16 | UTF8String | V | | | M | No | +| OFR-Flags | 3328 | 6.3.3.12 | Unsigned32 | V | | | M | No | +| Maximum-Retransmission-Time | 3330 | 6.3.3.17 | Time | V | | | M | No | +| Requested-Retransmission-Time | 3331 | 6.3.3.18 | Time | V | | | M | No | +| SMS-GMSC-Address | 3332 | 6.3.3.19 | OctetString | V | | | M | No | +| NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [20]. | | | | | | | | | +| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. | | | | | | | | | + +The following table specifies the Diameter AVPs re-used from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within this interface. + +Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol specified in IETF RFC 6733 [20], do not need to be supported. The AVPs from Diameter base protocol specified in IETF RFC 6733 [20] are not included in table 6.3.3.1/2, but they may be re-used for this interface. + +Table 6.3.3.1/2: SGd/Gdd re-used Diameter AVPs + +| Attribute Name | Reference | Comments | M-bit | +|---------------------------|---------------------|----------------------------------------------------------|--------------| +| User-Name | IETF RFC 6733 [20] | | Must | +| User-Identifier | 3GPP TS 29.336 [15] | | | +| MME-Number-for-MT-SMS | 3GPP TS 29.272 [4] | | | +| SGSN-Number | 3GPP TS 29.272 [4] | | Must not | +| Absent-User-Diagnostic-SM | 3GPP TS 29.338 | It is defined for the S6c interface, see clause 5.3.3.20 | | +| Supported-Features | 3GPP TS 29.229 [5] | | | +| Feature-List-ID | 3GPP TS 29.229 [5] | See clause 6.3.3.8 | | +| Feature-List | 3GPP TS 29.229 [5] | See clause 6.3.3.9 | | +| DRMP | IETF RFC 7944 [19] | see clause 6.3.3.20 | Must not set | +| External-Identifier | 3GPP TS 29.336 [15] | | Must not | + +NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies. + +NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. + +#### 6.3.3.2 SC-Address + +The SC-Address AVP is of type OctetString and it shall contain the E.164 number of the SMS-SC or MTC-IWF, in international number format as described in ITU-T Recommendation E.164 [13] and encoded as a TBCD-string. See 3GPP TS 29.002 [9] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address. + +#### 6.3.3.3 SM-RP-UI + +The SM-RP-UI is of type OctetString and it shall contain a short message transfer protocol data unit (TPDU) which is defined in 3GPP TS 23.040 [3] and represents the user data field carried by the short message service relay sub-layer protocol. Its maximum length is of 200 octets. + +#### 6.3.3.4 TFR-Flags + +The TFR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.3.4/1: + +Table 6.3.3.4/1: TFR-Flags + +| Bit | Name | Description | +|----------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------------------| +| 0 | More-Messages-To-Send | This bit, when set, shall indicate that the service centre has more short messages to send. | +| NOTE 1: Bits not defined in this table shall be cleared by the sending entity and discarded by the receiving entity. | | | + +#### 6.3.3.5 SM-Delivery-Failure-Cause + +The SM-Delivery-Failure-Cause AVP is of type Grouped. It shall contain information about the cause of the failure of a SM delivery with an optional Diagnostic information. + +The AVP format shall conform to: + +``` +SM-Delivery-Failure-Cause ::= + { SM-Enumerated-Delivery-Failure-Cause } + [ SM-Diagnostic-Info ] + *[ AVP ] +``` + +#### 6.3.3.6 SM-Enumerated-Delivery-Failure-Cause + +The SM-Enumerated-Delivery-Failure-Cause AVP is of type enumerated and it shall contain the cause of the failure of a SM delivery. The following values are defined: + +``` +MEMORY_CAPACITY_EXCEEDED (0), +EQUIPMENT_PROTOCOL_ERROR (1), +EQUIPMENT_NOT_SM-EQUIPPED (2), +UNKNOWN_SERVICE_CENTRE (3), +SC-CONGESTION (4), +INVALID_SME-ADDRESS (5), +USER_NOT_SC-USER (6). +``` + +NOTE: The values of the SM-Enumerated-Delivery-Failure-Cause AVP correspond to the ones for the SM-EnumeratedDeliveryFailureCause parameter in MAP as described in 3GPP TS 29.002[9]. + +#### 6.3.3.7 SM-Diagnostic-Info + +The SM-Diagnostic-Info AVP is of type OctetString and it shall contain a complementary information associated to the SM Delivery Failure cause. + +#### 6.3.3.8 Feature-List-ID AVP + +The syntax of this AVP is defined in 3GPP TS 29.229 [5]. For this release, the Feature-List-ID AVP value shall be set to 1. + +#### 6.3.3.9 Feature-List AVP + +The syntax of this AVP is defined in 3GPP TS 29.229 [5]. A null value indicates that there is no feature used by the application. + +NOTE: There is no feature defined for this release. + +#### 6.3.3.10 SM-Delivery-Timer + +The SM-Delivery-Timer is of type Integer and it shall contain the value in seconds of the timer for SM Delivery. + +#### 6.3.3.11 SM-Delivery-Start-Time + +The SM-Delivery-Start-Time is of type Time and it shall contain the timestamp (in UTC) at which the SM Delivery Supervision Timer was started. + +#### 6.3.3.12 OFR-Flags + +The OFR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.3.12/1: + +**Table 6.3.3.12/1: OFR-Flags** + +| Bit | Name | Description | +|-----|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | S6a/S6d-Indicator | This bit, when set, indicates that the OFR message is sent on the Gdd interface, i.e. the source node is an SGSN (or a combined MME/SGSN to which the UE is attached via UTRAN). This bit, when cleared, indicates that the OFR message is sent on the SGd interface, i.e. the source node is an MME (or a combined MME/SGSN to which the UE is attached via UTRAN or GERAN). | + +#### 6.3.3.13 SMSMI-Correlation-ID + +The SMSMI-Correlation-ID AVP is of type Grouped. It shall contain information identities used in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]). + +The AVP format shall conform to: + +SMS-MI-Correlation-ID ::= + +[ HSS-ID ] + +[ Originating-SIP-URI ] + +[ Destination-SIP-URI ] + +\*[ AVP ] + +#### 6.3.3.14 HSS-ID + +The HSS-ID AVP is of type UTF8String. The definition and the composition of the HSS-ID are specified in 3GPP TS 23.003 [16]. + +#### 6.3.3.15 Originating-SIP-URI + +The Originating-SIP-URI AVP is of type UTF8String. It shall contain the Public identity of the IMS UE without MSISDN which is the sender of a short message, in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]). + +#### 6.3.3.16 Destination-SIP-URI + +The Destination-SIP-URI AVP is of type UTF8String. It shall contain the Public identity of the IMS UE without MSISDN which is the recipient of a short message, in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [17]). + +#### 6.3.3.17 Maximum-Retransmission-Time + +The Maximum-Retransmission-Time is of type Time and in shall contain the maximum retransmission time (in UTC) until which the SMS-GMSC is capable to retransmit the MT Short Message. + +#### 6.3.3.18 Requested-Retransmission-Time + +The Requested-Retransmission-Time is of type Time and in shall contain the timestamp (in UTC) at which the SMS-GMSC is requested to retransmit the MT Short Message. + +#### 6.3.3.19 SMS-GMSC-Address + +The SMS-GMSC-Address AVP is of type OctetString and it shall contain the E.164 number of the SMS-GMSC or SMS Router, in international number format as described in ITU-T Recommendation E.164 [13] and encoded as a TBCD-string. See 3GPP TS 29.002 [9] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address. + +#### 6.3.3.20 DRMP + +The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [19]. This AVP allows the MME, the SGSN, the SMS-IWMSC, the SMS-GMSC, the SMS Router and the IP-SM-GW to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message. + +# --- 7 Result Codes and Experimental-Result values + +## 7.1 General + +This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification. + +## 7.2 Success + +Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [20] shall be applied. + +## 7.3 Permanent Failures + +### 7.3.1 General + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [20] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent. + +### 7.3.2 DIAMETER\_ERROR\_USER\_UNKNOWN (5001) + +This result code shall be sent by the MME over the SGd interface or by the SGSN over the Gdd interface to indicate that the user identified by the IMSI is unknown. + +This result code shall be sent by the SMS-IWMSC over the SGd interface to indicate that the user identified by the MSISDN is unknown. + +This result code shall be sent by the HSS or the SMS Router over the S6c interface to indicate that the user identified by the MSISDN is unknown. + +### 7.3.3 DIAMETER\_ERROR\_ABSENT\_USER (5550) + +This result code shall be sent by the MME over the SGd interface or by the SGSN over the Gdd interface to indicate that the UE is not reachable. + +This result code shall be sent by the HSS or the SMS Router over the S6c interface to indicate that the UE is not reachable. + +### 7.3.4 DIAMETER\_ERROR\_USER\_BUSY\_FOR\_MT\_SMS (5551) + +This result code shall be sent by the MME or the SGSN when the user is busy for MT SMS. + +### 7.3.5 DIAMETER\_ERROR\_FACILITY\_NOT\_SUPPORTED (5552) + +This result code shall be sent to indicate a requested facility is not supported. + +NOTE: This code corresponds to the Facility Not Supported MAP error and may be used by an IWF. + +### 7.3.6 DIAMETER\_ERROR\_ILLEGAL\_USER (5553) + +This result code shall be sent by the MME or the SGSN to indicate that the delivery of the mobile terminated short message failed because the mobile station failed authentication. + +### 7.3.7 DIAMETER\_ERROR\_ILLEGAL\_EQUIPMENT (5554) + +This result code shall be sent by the MME or the SGSN to indicate that the delivery of the mobile terminated short message failed because an IMEI check failed, i.e. the IMEI was blacklisted or not white-listed. + +### 7.3.8 DIAMETER\_ERROR\_SM\_DELIVERY\_FAILURE (5555) + +This result code shall be sent by the MME or the SGSN or the SMS-IWMSC to indicate that the delivery of the mobile terminated short message failed. + +### 7.3.9 DIAMETER\_ERROR\_SERVICE\_NOT\_SUBSCRIBED (5556) + +This result code shall be sent by the HSS or the SMS Router over the S6c interface to indicate that the MT SMS Teleservice is not part of the subscription. + +### 7.3.10 DIAMETER\_ERROR\_SERVICE\_BARRED (5557) + +This result code shall be sent by the HSS or the SMS Router over the S6c interface to indicate that the MT SMS Teleservice is barred. + +This result code shall be sent by the MME to indicate that the delivery of the mobile terminated short message failed because of the barring of the SMS service. + +### 7.3.11 DIAMETER\_ERROR\_MWD\_LIST\_FULL (5558) + +This result code shall be sent by the HSS over the S6c interface to indicate that the Message Waiting List is full. + +## 7.4 Transient Failures + +### 7.4.1 General + +Result codes that fall within the transient failures category shall be used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [20] shall be applied. + +# Annex A (normative): Diameter message priority mechanism + +## A.1 General + +IETF RFC 7944 [19] specifies a Diameter routing message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied. + +## A.2 S6c, SGd, Gdd interfaces + +The Diameter message priority mechanism is an optional feature which may apply on one or several of the S6c,SGd,Gdd interfaces. + +A 3GPP functional entity supporting the Diameter message priority mechanism over one or several of the S6c,SGd,Gdd interfaces shall comply with IETF RFC 7944 [19]. + +A 3GPP functional entity sending a request shall determine the required priority according to its policies. When priority is required, it shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level. + +When a 3GPP functional entity receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When a 3GPP functional entity receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response. + +The decisions of the 3GPP functional entity for a required priority and for the priority level value are implementation specific. + +If: + +- a 3GPP functional entity supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the 3GPP functional entity shall set the DSCP marking for transport of the request or response according to the required priority level. + +Diameter requests related to high priority traffic shall contain a DRMP AVP with a high priority of which the level value is operator dependent. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|---------|-----|----------------------|----------------| +| Date | Meeting | TDoc | CR | R
ev | Cat | Subject/Comment | New
version | +| 2012 | CT#58 | CP-120762 | | | F | TS sent for approval | | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------|--------| +| 2013-03 | CT#59 | CP-130030 | 0003 | 2 | F | Validity Time of Short Message | | +| 2013-06 | CT#60 | CP-130300 | 0001 | 2 | F | Diameter for SMS with SGSN General | | +| 2013-06 | CT#60 | CP-130300 | 0002 | 2 | F | Diameter for SMS with SGSN Complements | | +| 2013-06 | CT#60 | CP-130300 | 0004 | 1 | F | S6c complements related to Diameter for SMS with SGSN | | +| 2013-09 | CT#61 | CP-130450 | 0007 | 1 | F | Correction on Routing for MO SM | | +| 2013-0 | CT#61 | CP-130456 | 0008 | 2 | F | SGSN Diameter address with Gdd support | | +| 2013-12 | CT#62 | CP-130800 | 0009 | 3 | F | Diameter based protocols with SMS for IMS UE without MSISDN | | +| 2014-09 | CT#65 | CP-140513 | 0010 | 2 | F | Identification of the HSS | | +| 2014-12 | CT#66 | CP-140767 | 0013 | 1 | F | Corrections for some AVPs | | +| 2014-12 | CT#66 | CP-140767 | 0011 | 1 | F | SC-Address in SRR | | +| 2014-12 | CT#66 | CP-140767 | 0014 | - | F | AVP codes corrections for SMSMI | | +| 2014-12 | CT#66 | CP-140767 | 0016 | | F | OFR-Flags AVP correction | | +| 2015-12 | CT#70 | CP-150776 | 0017 | 3 | F | Mobile Terminating SMS handling for extended Idle mode DRX | 13.0.0 | +| 2015-12 | CT#70 | CP-150776 | 0018 | 1 | F | Mobile Terminating SMS handling for extended Idle mode DRX – Additional Option | | +| 2016-03 | CT#71 | CP-160030 | 0019 | - | F | Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX | 13.1.0 | +| 2016-03 | CT#71 | CP-160023 | 0020 | 1 | F | Diameter message priority over S6c, SGd, Gdd | | +| 2016-06 | CT#72 | CP-160226 | 0021 | - | F | Missing Requested-Retransmission-Time AVP in TFA Command | 13.2.0 | +| 2016-12 | CT#74 | CP-160664 | 0023 | | F | Correction to change IETF drmp draft version to official RFC 7944 | 13.3.0 | +| 2016-12 | CT#74 | CP-160673 | 0022 | 1 | F | MO SMS over T4 | 14.0.0 | +| 2017-03 | CT#75 | CP-170036 | 0024 | | F | SMS-MO over T4 | 14.1.0 | +| 2017-03 | CT#75 | CP-170048 | 0025 | 1 | F | Update of reference for the Diameter base protocol | 14.1.0 | +| 2017-03 | CT#75 | CP-170048 | 0026 | 1 | F | Handling of the Vendor-Specific-Application-Id AVP | 14.1.0 | +| 2017-03 | CT#75 | CP-170048 | 0027 | 1 | F | Cardinality of the Failed-AVP AVP in answer | 14.1.0 | +| 2017-06 | CT#76 | CP-171018 | 0029 | 1 | F | Support for signaling transport level packet marking | 14.2.0 | +| 2017-09 | CT#77 | CP-172013 | 0032 | - | F | Correction of DRMP Procedures | 14.3.0 | +| 2017-09 | CT#77 | CP-172022 | 0030 | 2 | F | Correction of the data type used for SC-Address and SMS-GMSC-Address | 15.0.0 | +| 2018-12 | CT#82 | CP-183100 | 0033 | 2 | F | Clarification on presence of SC-Address in SRR and on MWD Status | 15.1.0 | +| 2020-06 | CT#88e | CP-201016 | 0034 | 1 | F | SMSF Address | 15.2.0 | +| 2020-06 | CT#88e | CP-201016 | 0035 | 1 | F | Support of SMS in 5G | 15.2.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2020-09 | CT#89e | CP-202043 | 0037 | - | A | SMSF Address Corrections | 16.1.0 | +| 2021-03 | CT#91e | CP-210053 | 0039 | 1 | F | Corrections on SM-Delivery-Not-Intended | 16.2.0 | +| 2023-09 | CT#101 | CP-232077 | 0056 | - | A | SM-Delivery-Failure-Cause AVP code correction | 16.3.0 | +| 2023-09 | CT#101 | CP-232076 | 0048 | - | A | HSS-ID AVP type correction | 16.3.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29364/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/29_series/29364/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9afdb7539e56e22373e2152dc899097ccb74fd7 --- /dev/null +++ b/marked/Rel-16/29_series/29364/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07f31ed50881b8b2148e96332de6ce7335317b94919b54886dc103926b06b930 +size 17074 diff --git a/marked/Rel-16/29_series/29364/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/marked/Rel-16/29_series/29364/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f464b2db5c454d7e023b35f03cef52445f8aadd --- /dev/null +++ b/marked/Rel-16/29_series/29364/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0979808151b4e86523309ec8f995334260949e0f25a62871b637428417b7be41 +size 34186 diff --git a/marked/Rel-16/29_series/29594/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Rel-16/29_series/29594/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..301914acb1b6ff8ad5689c7c38bec41654dc3454 --- /dev/null +++ b/marked/Rel-16/29_series/29594/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed00c5e8d3c1352d39dddef1f490721404b3f799bd245fa849eb0545e688446 +size 18228 diff --git a/marked/Rel-16/29_series/29594/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/Rel-16/29_series/29594/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..530b443b15fe635393ea8fc597dcf202618e97d7 --- /dev/null +++ b/marked/Rel-16/29_series/29594/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52c973d81f6db9eef7f144b7c55263cd159c6c6268ed44259c045a46f44f143b +size 20897 diff --git a/marked/Rel-16/29_series/29594/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-16/29_series/29594/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99c3183159685e5d0ad9dffe7a784463cbf88b8c --- /dev/null +++ b/marked/Rel-16/29_series/29594/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:587673a66f8af44454f4bee876500c652403e5751ffd7231ec18f418c3483257 +size 18907 diff --git a/marked/Rel-16/29_series/29594/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/Rel-16/29_series/29594/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8903b20cfc96cda273ecc4754e9b498e4e6281d4 --- /dev/null +++ b/marked/Rel-16/29_series/29594/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f558198e74eb3ac147ab34400a6dd93a2e6c1236af8e32e53ac836d481527116 +size 23648 diff --git a/marked/Rel-16/29_series/29594/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/Rel-16/29_series/29594/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e867c67876deb0246bed548d0faa752c8d3ee83 --- /dev/null +++ b/marked/Rel-16/29_series/29594/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3df3d41ff42319d7504de0c00b62a486fcff4035ee213c1ef5061d90db348bc5 +size 16678 diff --git a/marked/Rel-16/29_series/29594/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/29_series/29594/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c64212885048225f59b4644449d562e5d27f961e --- /dev/null +++ b/marked/Rel-16/29_series/29594/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c8769d093cae0ed93aec4cf44d9ed5fec94872142ada9746ee5fb2131be27a6 +size 6270 diff --git a/marked/Rel-16/29_series/29594/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/29_series/29594/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9e80d1a0d25d0ec810710ccf9b452f962b14271 --- /dev/null +++ b/marked/Rel-16/29_series/29594/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c9957c114599e863dfc2bb8add03aec8c9a1c66808b2667942507ccaba675ea +size 11334 diff --git a/marked/Rel-16/29_series/29594/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-16/29_series/29594/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af81e797a5396079cdb1593354f563cf59789f32 --- /dev/null +++ b/marked/Rel-16/29_series/29594/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cd4ad700c83a2a8af284722d73d59b015d16c270ce0e690af9d66fdf62e111c +size 19158 diff --git a/marked/Rel-16/29_series/29594/raw.md b/marked/Rel-16/29_series/29594/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a1ca4299183338a91085bdfbd9d29785208aefdc --- /dev/null +++ b/marked/Rel-16/29_series/29594/raw.md @@ -0,0 +1,1624 @@ + + + + +# ***Copyright Notification*** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Nchf_SpendingLimitControl Service ..... | 8 | +| 4.1 Service Description ..... | 8 | +| 4.1.1 Overview ..... | 8 | +| 4.1.2 Service Architecture ..... | 9 | +| 4.1.3 Network Functions ..... | 9 | +| 4.1.3.1 Charging Function (CHF)..... | 9 | +| 4.1.3.2 NF Service Consumers ..... | 9 | +| 4.2 Service Operations ..... | 9 | +| 4.2.1 Introduction ..... | 9 | +| 4.2.2 Nchf_SpendingLimitControl_Subscribe service operation..... | 10 | +| 4.2.2.1 General..... | 10 | +| 4.2.2.2 Initial spending limit retrieval..... | 10 | +| 4.2.2.3 Intermediate spending limit report retrieval ..... | 12 | +| 4.2.3 Nchf_SpendingLimitControl_Unsubscribe service operation..... | 14 | +| 4.2.3.1 General..... | 14 | +| 4.2.3.2 Unsubscribe from spending limit reporting ..... | 14 | +| 4.2.4 Nchf_SpendingLimitControl_Notify service operation..... | 15 | +| 4.2.4.1 General..... | 15 | +| 4.2.4.2 Spending limit report ..... | 15 | +| 4.2.4.3 Subscription termination request by CHF ..... | 16 | +| 5 Nchf_SpendingLimitControl Service API..... | 17 | +| 5.1 Introduction ..... | 17 | +| 5.2 Usage of HTTP..... | 18 | +| 5.2.1 General ..... | 18 | +| 5.2.2 HTTP standard headers ..... | 18 | +| 5.2.2.1 General..... | 18 | +| 5.2.2.2 Content type..... | 18 | +| 5.2.3 HTTP custom headers ..... | 18 | +| 5.2.3.1 General..... | 18 | +| 5.3 Resources ..... | 18 | +| 5.3.1 Resource Structure..... | 18 | +| 5.3.2 Resource: Spending Limit Retrieval Subscriptions (Collection) ..... | 19 | +| 5.3.2.1 Description..... | 19 | +| 5.3.2.2 Resource definition..... | 19 | +| 5.3.2.3 Resource Standard Methods ..... | 19 | +| 5.3.2.3.1 POST ..... | 19 | +| 5.3.2.4 Resource Custom Operations..... | 20 | +| 5.3.3 Resource: Individual Spending Limit Retrieval Subscription (Document)..... | 20 | +| 5.3.3.1 Description..... | 20 | +| 5.3.3.2 Resource definition..... | 20 | +| 5.3.3.3 Resource Standard Methods ..... | 20 | +| 5.3.3.3.1 PUT ..... | 20 | +| 5.3.3.3.2 DELETE..... | 21 | +| 5.4 Custom Operations without associated resources ..... | 22 | +| 5.5 Notifications ..... | 22 | +| 5.5.1 General ..... | 22 | +| 5.5.2 Spending limit notification ..... | 23 | +| 5.5.2.1 Description..... | 23 | +| 5.5.2.2 Target URI ..... | 23 | +| 5.5.2.3 Standard Methods ..... | 23 | + +| | | | +|-----------------------------|---------------------------------------------------------------|-----------| +| 5.5.2.3.1 | POST ..... | 23 | +| 5.5.3 | Subscription Termination ..... | 24 | +| 5.5.3.1 | Description..... | 24 | +| 5.5.3.2 | Target URI ..... | 24 | +| 5.5.3.3 | Standard Methods ..... | 24 | +| 5.5.3.3.1 | POST ..... | 24 | +| 5.6 | Data Model..... | 25 | +| 5.6.1 | General ..... | 25 | +| 5.6.2 | Structured data types ..... | 26 | +| 5.6.2.1 | Introduction..... | 26 | +| 5.6.2.2 | Type SpendingLimitContext..... | 27 | +| 5.6.2.3 | Type SpendingLimitStatus ..... | 28 | +| 5.6.2.4 | Type PolicyCounterInfo ..... | 29 | +| 5.6.2.5 | Type PendingPolicyCounterStatus ..... | 29 | +| 5.6.2.6 | Type SubscriptionTerminationInfo..... | 29 | +| 5.6.3 | Simple data types and enumerations ..... | 30 | +| 5.6.3.1 | Introduction..... | 30 | +| 5.6.3.2 | Simple data types ..... | 30 | +| 5.6.3.3 | Enumeration: TerminationCause ..... | 30 | +| 5.7 | Error handling ..... | 30 | +| 5.7.1 | General ..... | 30 | +| 5.7.2 | Protocol Errors..... | 30 | +| 5.7.3 | Application Errors ..... | 30 | +| 5.8 | Feature negotiation..... | 31 | +| 5.9 | Security..... | 31 | +| Annex A (normative): | OpenAPI specification ..... | 32 | +| A.1 | General..... | 32 | +| A.2 | Nchf_SpendingLimitControl Service API..... | 32 | +| Annex B (normative): | 5GC and EPC interworking scenario support ..... | 36 | +| B.1 | Scope..... | 36 | +| B.2 | Nchf_SpendingLimitControl Service ..... | 36 | +| B.2.1 | Service Description ..... | 36 | +| B.2.1.1 | Overview ..... | 36 | +| B.2.1.2 | Service Architecture ..... | 36 | +| B.3 | Service Operation..... | 37 | +| B.3.1 | Introduction ..... | 37 | +| B.3.2 | Nchf_SpendingLimitControl_Subscribe Service Operation ..... | 37 | +| B.3.3 | Nchf_SpendingLimitControl_Unsubscribe Service Operation..... | 37 | +| B.3.4 | Nchf_SpendingLimitControl_Notify Service Operation ..... | 37 | +| Annex C (normative): | Wireless and wireline convergence access support ..... | 37 | +| C.1 | Scope..... | 37 | +| C.2 | Nchf_SpendingLimitControl Service ..... | 37 | +| C.2.1 | Service Description ..... | 37 | +| C.2.1.1 | Overview ..... | 37 | +| C.2.1.2 | Service Architecture ..... | 37 | +| C.3 | Service Operation..... | 38 | +| C.3.1 | Introduction ..... | 38 | +| C.3.2 | Nchf_SpendingLimitControl_Subscribe Service Operation ..... | 38 | +| C.3.2.1 | General ..... | 38 | +| C.3.3 | Nchf_SpendingLimitControl_Unsubscribe Service Operation..... | 38 | +| C.3.4 | Nchf_SpendingLimitControl_Notify Service Operation ..... | 38 | +| Annex D (informative): | Change history..... | 39 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present specification provides the stage 3 definition of the Spending Limit Control Service of the 5G System. + +The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for the Spending Limit Control Service are specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6]. + +The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [12]. + +The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. + +The Spending Limit Control Service is provided by the Charging Function (CHF) and enables the NF service consumer to retrieve policy counter status information. The internal CHF functionality for policy counter management provisioning is specified in 3GPP TS 32.240 [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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [6] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [7] 3GPP TS 32.240: "Charging architecture and principles; Stage 2". +- [8] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)". +- [9] OpenAPI: "OpenAPI 3.0.0 Specification", . +- [10] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [11] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces". +- [12] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3". +- [13] IETF RFC 7807: "Problem Details for HTTP APIs". +- [14] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [15] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". +- [16] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [17] 3GPP TR 21.900: "Technical Specification Group working methods". + +- [18] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3". +- [19] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Nchf:** Service-based interface exhibited by Charging Function. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|----------------------------------------| +| 5G-RG | 5G Residential Gateway | +| CCS | Converged Charging System | +| CHF | Charging Function | +| FN-RG | Fixed Network Residential Gateway | +| GCI | Global Cable Identifier | +| GLI | Global Line Identifier | +| CTS | Charging Trigger Function | +| GPSI | Generic Public Subscription Identifier | +| NF | Network Function | +| NRF | Network Repository Function | +| PCF | Policy Control Function | +| SUPI | Subscription Permanent Identifier | +| W-AGF | Wireline Access Gateway Function | + +# --- 4 Nchf\_SpendingLimitControl Service + +## 4.1 Service Description + +### 4.1.1 Overview + +The Nchf\_SpendingLimitControl service, as defined in 3GPP TS23.502 [3] and 3GPP TS23.503 [6], is provided by the Charging Function (CHF). + +The Nchf\_SpendingLimitControl service enables the NF service consumer (i.e. PCF) to retrieve policy counter status information and spending limit reporting per UE from the CHF. + +If the spending limit reporting is no more required the Nchf\_SpendingLimitControl service enables the NF service consumer to unsubscribe from the reporting. + +Nchf\_SpendingLimitControl Service applies to the cases where the PCF interacts with the CHF in the non-roaming scenario, and the H-PCF interacts with the H-CHF in the home-routed scenario. + +### 4.1.2 Service Architecture + +The Nchf\_SpendingLimitControl service is provided by the CHF and consumed by the PCF, as shown in figure 4.1.2-1 for the SBI representation model and in figure 4.1.2-2 for the reference point representation model. + +![Nchf_SpendingLimitControl service architecture, SBI representation diagram](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram shows a Charging Function (CHF) at the top and a Policy Control Function (PCF) at the bottom. The CHF contains an oval labeled 'Nchf' which represents the service interface. A vertical line connects the 'Nchf' oval to the PCF, and this line is labeled 'Nchf\_SpendingLimitControl'. + +Nchf\_SpendingLimitControl service architecture, SBI representation diagram + +**Figure 4.1.2-1: Nchf\_SpendingLimitControl service architecture, SBI representation** + +![Nchf_SpendingLimitControl service architecture, reference point representation diagram](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +The diagram shows a Charging Function (CHF) at the top and a Policy Control Function (PCF) at the bottom. A vertical line connects the CHF and the PCF, with a small horizontal tick mark on the line. This line is labeled 'N28'. + +Nchf\_SpendingLimitControl service architecture, reference point representation diagram + +**Figure 4.1.2-2: Nchf\_SpendingLimitControl service architecture, reference point representation** + +### 4.1.3 Network Functions + +#### 4.1.3.1 Charging Function (CHF) + +The Charging Function (CHF) is part of the Converged Charging System (CCS). The CHF provides the Nchf\_SpendingLimitControl service and is specified in 3GPP TS 32.240 [7]. + +#### 4.1.3.2 NF Service Consumers + +The PCF is the known NF service consumer, as defined in 3GPP TS 23.502 [3]. The NF service consumer accesses policy counter status information relating to the subscriber spending from the CHF and uses the status of each relevant policy counter as input to its policy decision as required by the decision logic. + +## 4.2 Service Operations + +### 4.2.1 Introduction + +The service operations defined for the Nchf\_SpendingLimitControl service are shown in table 4.2.1-1. + +**Table 4.2.1-1: Nchf\_SpendingLimitControl Service Operations** + +| Service operation name | Description | Initiated by | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| Nchf_SpendingLimitControl_Subscribe | This service operation is used by an NF service consumer to subscribe to notification of changes in the status of the policy counters available and retrieval of the status of the policy counters for which subscription is accepted. | NF service consumer (PCF) | +| Nchf_SpendingLimitControl_Unsubscribe | This service operation is used by an NF service consumer to unsubscribe from notification of changes in the status of all policy counters. | NF service consumer (PCF) | +| Nchf_SpendingLimitControl_Notify | This service operation is used by the CHF to notify the NF service consumers about the change of the status of the subscribed policy counters. Alternatively, it can be used by the CHF to notify that the status for one or multiple subscribed policy counter will change in the future, indicating the time when this change shall be applied. Alternatively, it is also used to notify the NF service consumer of the removal of a subscriber from the CHF system for the purpose that the NF service consumer can terminate the subscriptions of all policy counters of the subscriber. | CHF | + +### 4.2.2 Nchf\_SpendingLimitControl\_Subscribe service operation + +#### 4.2.2.1 General + +The Nchf\_SpendingLimitControl\_Subscribe service operation is used by the NF service consumer to subscribe to notification of changes in the status of the policy counters available and to retrieve the status of the policy counters for which the subscription is accepted. The following procedures are related to the subscribe service operation: + +- initial spending limit retrieval; and +- intermediate spending limit report retrieval. + +#### 4.2.2.2 Initial spending limit retrieval + +Figure 4.2.2.2-1 shows the scenario where the NF service consumer sends a request to the CHF to retrieve the status of policy counters available at the CHF and to subscribe to spending limit reporting (see also 3GPP TS 23.502 [3], figure 4.16.8.2.1). + +![Sequence diagram showing the interaction between an NF service consumer and a CHF. The NF service consumer sends a POST request to the CHF, and the CHF responds with a 201 Created status.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +``` + +sequenceDiagram + participant NF service consumer + participant CHF + Note left of NF service consumer: + NF service consumer->>CHF: 1. POST.../subscriptions + Note right of CHF: + CHF-->>NF service consumer: 2. 201 Created + +``` + +Sequence diagram showing the interaction between an NF service consumer and a CHF. The NF service consumer sends a POST request to the CHF, and the CHF responds with a 201 Created status. + +**Figure 4.2.2.2-1: NF service consumer subscribes to retrieve policy counter status and spending limit reporting** + +The NF service consumer shall send an HTTP POST request to the resource "{apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions" representing the "Spending Limit Retrieval Subscriptions", as shown in figure 4.2.2.2-1, step 1, to create a subscription for retrieval of the policy counter status and spending limit reporting. + +The "SpendingLimitContext" data structure provided in the request body shall include: + +- the Subscription Permanent Identifier (SUPI) encoded in the "supi" attribute; +- the notification correlation target address encoded in the "notifUri" attribute; and +- If the feature "NotificationCorrelation" is supported, a Notification Correlation Identifier assigned by the NF service consumer for the requested notifications encoded in the "notifId" attribute, if the "notifUri" does not encode within the provided URI the notification correlation Id. + +NOTE: NF service consumer (i.e. PCF) ensures the combination of notifUri and notifId is unique per subscription in the whole network, including multiple network slices scenario. + +The "SpendingLimitContext" data structure provided in the request body may include: + +- the General Public Subscription Identifier (GPSI) encoded in the "gpsi" attribute; +- Event Filter information "list of policy counter identifier(s)" encoded in the "policyCounterIds" attribute. The "policyCounterIds" attribute shall contain the list of policy counter identifiers to be subscribed to. If the "policyCounterIds" attribute is omitted, the subscription is to all available policy counters; and +- when the feature "SubscriptionExpirationTimeControl" is supported by the NF service consumer, the NF service consumer may include an expiry time encoded in the "expiry" attribute, representing the time up to which the subscription is desired to be kept active. When the "expiry" attribute is omitted in the request, it represents the NF service consumer does not have any time constraint in the duration of the subscription. + +If the CHF cannot successfully fulfil the received HTTP POST request due to an internal CHF error or due to the error in the HTTP POST request, the CHF shall send the HTTP error response as specified in subclause 5.7. + +If the subscriber specified in the request is unknown to the CHF, the CHF shall indicate in an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "USER\_UNKNOWN". + +If the CHF has no available policy counters specified for the subscriber, the CHF shall indicate in an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "NO\_AVAILABLE\_POLICY\_COUNTERS". + +If one or more policy counters specified in the request in the "policyCounterIds" attribute are unknown to the CHF, and the CHF is configured to reject request, the CHF shall indicate in an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "UNKNOWN\_POLICY\_COUNTERS" and the unknown policy counter identifiers within the "invalidParams" attribute. + +Otherwise, upon the reception of an HTTP POST request the CHF shall: + +- create a new subscription resource, which contains the list of the policy counters included in the "policyCounterIds" attribute, or if the "policyCounterIds" attribute is omitted, all the policy counters of the subscriber; +- assign a subscriptionId; and +- store the subscription resource. + +After the CHF created an "Individual Spending Limit Retrieval Subscription" resource, the CHF shall respond with "201 Created" response with a Location header field containing the URI of the created subscription resource and the message body containing a representation of the created subscription, as shown in figure 4.2.2.2-1, step 2. + +The SpendingLimitStatus data structure provided in the response body shall include the status of the requested subscribed policy counters in the "statusInfos" map, where every PolicyCounterInfo entry shall contain: + +- the policy counter identifier in the "policyCounterId" attribute; and +- the policy counter status in the "currentStatus" attribute. + +When a requested policy counter identifier is known by the CHF, but it is not applicable to the subscriber (e.g. not provisioned), the CHF may include it in the "statusInfos" map, and set the "currentStatus" attribute to an operator configured policy counter status to indicate this to the NF service consumer. + +When one or more policy counters specified in the request in the "policyCounterIds" attribute are unknown to the CHF, and the CHF is configured to accept the request, the CHF may include the unknown policy counters in the "statusInfos" map, and set the "currentStatus" attribute to an operator configured policy counter status to indicate this to the NF service consumer. + +A PolicyCounterInfo data structure may include the list of the pending policy counter statuses and their activation times within the attribute "penPolCounterStatuses". + +When the feature "SubscriptionExpirationTimeControl" is supported, the CHF may include the "expiry" attribute, representing the time up to which the subscription shall be kept active. If an expiry time was included in the subscription request, then the expiry time shall be returned in the response, and the value shall be less than or equal to the requested value. When the "expiry" attribute is omitted in the request and in the response, it represents neither the CHF or the NF service consumer have time constrains in the duration of the subscription and shall be kept active till the explicit subscription termination as described in subclause 4.2.3.2 and subclause 4.2.4.3. + +NOTE 1: If the NF Service Consumer does not include a expiry time in the request, the CHF can include a expiry time in the response that represents the time after which the subscription becomes invalid. + +NOTE 2: Once the subscription expires, if the NF service consumer wants to keep receiving notifications, it needs to create a new subscription in the CHF, as specified in this subclause. + +#### 4.2.2.3 Intermediate spending limit report retrieval + +Figure 4.2.2.3-1 shows the scenario where the NF service consumer sends a request to the CHF to modify the existing subscription to the retrieval of spending limit reports (see also 3GPP TS 23.502 [3], figure 4.16.8.3.1). The NF service consumer can add or remove policy counters to retrieve the status of the counters. + +![Sequence diagram showing the interaction between an NF service consumer and a CHF. The NF service consumer sends a PUT request to the CHF for a subscription resource. The CHF responds with a 200 OK status.](18442e4e239480f0c3c95b547aa8fde2_img.jpg) + +``` + +sequenceDiagram + participant NF as NF service consumer + participant CHF as CHF + NF->>CHF: 1. PUT.../subscriptions/{subscriptionId} + CHF-->>NF: 2. 200 OK + +``` + +Sequence diagram showing the interaction between an NF service consumer and a CHF. The NF service consumer sends a PUT request to the CHF for a subscription resource. The CHF responds with a 200 OK status. + +**Figure 4.2.2.3-1: NF service consumer modifies the subscription to retrieve policy counter status and spending limit reporting** + +The NF service consumer shall send an HTTP PUT request to the resource "{apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions/{subscriptionId}" representing an existing "Individual Spending Limit Subscription" resource, as shown in figure 4.2.2.3-1, step 1, to modify the subscription for retrieval of the policy counter status and spending limit reporting. + +The "SpendingLimitContext" data structure provided in the request body: + +- shall include the Subscription Permanent Identifier (SUPI) encoded in the "supi" attribute; +- shall include the notification correlation target address encoded in the "notifUri" attribute; +- if the feature "NotificationCorrelation" is supported, a Notification Correlation Identifier assigned by the NF service consumer for the requested notifications encoded in the "notifId" attribute, if the "notifUri" does not encode within the provided URI the notification correlation Id. + +NOTE 1: If the notification correlation target address is not changed the previously provided notification correlation target address is included in the "notifUri" attribute. If the Notification Correlation Id is not changed the previously provided Notification Correlation Id is included in the "notifId" attribute. + +- if the General Public Subscription Identifier (GPSI) was provided within the initial spending limit retrieval procedure, described in subclause 4.2.2.2, shall include the GPSI encoded in the "gpsi" attribute; and + +- may include Event Filter information as a "list of policy counter identifier(s)" encoded in the "policyCounterIds" attribute. The "policyCounterIds" attribute shall contain the updated list of policy counter identifiers to be subscribed to. If the "policyCounterIds" attribute is omitted, the subscription is updated to all available policy counters; and +- when the feature "SubscriptionExpirationTimeControl" is supported, may include an updated expiry time encoded in the "expiry" attribute to update the duration of the subscription, representing the updated time up to which the subscription is desired to be kept active. When the "expiry" attribute is omitted in the request, it represents the NF service consumer update does not have any time constraint from this moment on in the duration of the subscription. + +NOTE 2: The "notifUri" attribute within the SpendingLimitContext data structure can be modified to request that subsequent notifications are sent to a new NF service consumer. + +When the "policyCounterIds" attribute is present in the subscription request, this list of policy counters overrides a previously provisioned list. + +After the CHF modified an "Individual Spending Limit Retrieval Subscription" resource, the CHF shall respond with "200 OK" response with the message body containing a representation of the modified subscription, as shown in figure 4.2.2.3-1, step 2. + +The SpendingLimitStatus data structure provided in the response body, when the feature "SubscriptionExpirationTimeControl" is not supported, shall include the status of the requested subscribed policy counters in the "statusInfos" map, where every PolicyCounterInfo entry shall contain: + +- the policy counter identifier in the "policyCounterId" attribute; and +- the policy counter status in the "currentStatus" attribute. + +When a requested policy counter identifier is known by the CHF, but it is not applicable to the subscriber (e.g. not provisioned), the CHF may include it in the "statusInfos" map, and set the "currentStatus" attribute to an operator configured policy counter status to indicate this to the NF service consumer. + +When one or more policy counters specified in the request in the "policyCounterIds" attribute are unknown to the CHF, and the CHF is configured to accept the request, the CHF may include the unknown policy counters in the "statusInfos" map, and set the "currentStatus" attribute to an operator configured policy counter status to indicate this to the NF service consumer. + +A PolicyCounterInfo data structure may include the list of the pending policy counter statuses and their activation times within the attribute "penPolCounterStatuses". + +When the feature "SubscriptionExpirationTimeControl" is supported, the CHF may include the "expiry" attribute, representing the time up to which the subscription shall be kept active. If an expiry time was included in the subscription update request, then the expiry time shall be returned in the response, and the value returned should be less than or equal to the value in the request. When the "expiry" attribute is omitted in the request and in the response, it represents that the subscription shall be considered valid without an expiry time. + +NOTE 3: When the NF service consumer does not include an expiry time in the request, the CHF can include an expiry time in the response that represents an update of the previously provided duration of the subscription. + +NOTE 4: Once the subscription expires, if the NF service consumer wants to keep receiving notifications, it needs to create a new subscription in the CHF, as specified in subclause 4.2.2.2. + +If errors occur when processing the HTTP PUT request, the CHF shall send an HTTP error response as specified in subclause 5.7. + +If the feature "ES3XX" is supported, and the CHF determines the received HTTP PUT request needs to be redirected, the CHF shall send an HTTP redirect response as specified in subclause 6.10.9 of 3GPP TS 29.500 [4]. + +If the CHF has no available policy counters specified for the subscriber, the CHF shall indicate in an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "NO\_AVAILABLE\_POLICY\_COUNTERS". + +If one or more policy counters specified in the PUT request in the "policyCounterIds" attribute are unknown to the CHF, and the CHF is configured to reject request, the CHF shall indicate in an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "UNKNOWN\_POLICY\_COUNTERS" and the unknown policy counter identifiers within the "invalidParams" attribute. The PUT request shall not take effect, and the CHF shall maintain the Individual Spending Limit Retrieval resource. + +NOTE 5: In order to avoid misbehaviors due to the policy counters status maintained in the CHF and the NF service consumer, the NF service consumer can terminate the subscription invoking the Nchf\_SpendingLimitControl\_Unsubscribe service operation in subclause 4.2.3.2. + +NOTE 6: The NF service consumer can terminate the subscription invoking the Nchf\_SpendingLimitControl\_Unsubscribe service operation in subclause 4.2.3.2, or maintain subscription assuming that further available policy counters will be notified. + +### 4.2.3 Nchf\_SpendingLimitControl\_Unsubscribe service operation + +#### 4.2.3.1 General + +The Nchf\_SpendingLimitControl\_Unsubscribe service operation is used by the NF service consumer to cancel the subscription of status changes for all the policy counters available at the CHF. That means the complete cancellation of the spending limit reporting procedure. + +#### 4.2.3.2 Unsubscribe from spending limit reporting + +Figure 4.2.3.2-1 shows the scenario where the NF service consumer sends a request to the CHF to unsubscribe from spending limit reporting (see also 3GPP TS 23.502 [3] figure 4.16.8.4.1). + +![Sequence diagram showing the NF service consumer sending a DELETE request to the CHF to unsubscribe from spending limit reporting. The diagram consists of two lifelines: 'NF service consumer' on the left and 'CHF' on the right. Step 1: A solid arrow points from the NF service consumer to the CHF with the text '1. DELETE.../subscriptions/{subscriptionId}'. Step 2: A solid arrow points from the CHF back to the NF service consumer with the text '2. 204 No Content'.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant CHF + Note left of NF service consumer: Unsubscribe from spending limit reporting + NF service consumer->>CHF: 1. DELETE.../subscriptions/{subscriptionId} + CHF-->>NF service consumer: 2. 204 No Content +``` + +Sequence diagram showing the NF service consumer sending a DELETE request to the CHF to unsubscribe from spending limit reporting. The diagram consists of two lifelines: 'NF service consumer' on the left and 'CHF' on the right. Step 1: A solid arrow points from the NF service consumer to the CHF with the text '1. DELETE.../subscriptions/{subscriptionId}'. Step 2: A solid arrow points from the CHF back to the NF service consumer with the text '2. 204 No Content'. + +**Figure 4.2.3.2-1: NF service consumer unsubscribes from spending limit reporting** + +The NF service consumer shall invoke the Nchf\_SpendingLimitControl\_Unsubscribe service operation to unsubscribe from the spending limit reporting (status change for all policy counters available is no more required). The NF service consumer shall send an HTTP DELETE request to the resource "{apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions/{subscriptionId}", whereby the "{subscriptionId}" is the identification of the existing subscription to be deleted. Upon the reception of an HTTP DELETE request the CHF removes the corresponding subscription. + +If the HTTP DELETE request is accepted by the CHF, it shall respond with "204 No Content" as shown in figure 4.2.3.2-1, step 2. + +If the HTTP DELETE request is not accepted by the CHF (e.g. the HTTP DELETE request is for a non-existent subscription), it shall indicate the appropriate cause for the rejection in the HTTP response code or, if the feature "ES3XX" is supported, an HTTP redirect response to the NF service consumer. + +### 4.2.4 Nchf\_SpendingLimitControl\_Notify service operation + +#### 4.2.4.1 General + +The Nchf\_SpendingLimitControl\_Notify service operation is used by the CHF: + +- to notify the change of the status of the subscribed policy counters available at the CHF for that subscriber; and/or + +- to provide one or more pending statuses for a subscribed policy counter together with the time they shall be applied; and/or +- to request the termination of the subscription of status changes for all policy counters for a subscriber (e.g. the subscriber is removed from the CHF system). + +#### 4.2.4.2 Spending limit report + +Figure 4.2.4.2-1 shows the scenario where the CHF sends a notification to the NF service consumer, when it detects that the status of a policy counter(s) has changed and the NF service consumer has subscribed to notifications of changes in the status of this policy counter(s). The CHF can also notify the NF service consumer that the status for one or multiple subscribed policy counter will change and indicate this by providing the time when this change shall be applied (see also 3GPP TS 23.502 [3], figure 4.16.8.5.1). + +![Sequence diagram showing Spending limit reporting between NF service consumer and CHF.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` + +sequenceDiagram + participant NF service consumer + participant CHF + Note left of NF service consumer: (Subscription already established) + CHF->>NF service consumer: 1. POST.../{notifUri}/notify + NF service consumer-->>CHF: 2. 204 No Content + +``` + +The diagram illustrates the interaction for spending limit reporting. It features two lifelines: 'NF service consumer' on the left and 'CHF' on the right. The sequence of messages is as follows: + + +- The CHF sends a '1. POST.../{notifUri}/notify' message to the NF service consumer. +- The NF service consumer responds with a '2. 204 No Content' message back to the CHF. + +Sequence diagram showing Spending limit reporting between NF service consumer and CHF. + +**Figure 4.2.4.2-1: Spending limit reporting** + +The CHF shall send an HTTP POST request to the resource notification target address (notifUri) of the NF service consumer received in the subscription creation or modification, and shall append the "notify" segment path at the end of the URI, to indicate the NF service consumer the notification of a policy counter status change. + +The SpendingLimitStatus data structure provided in the request body: + +- shall include the Subscriber Identity in the "supi" attribute; +- shall include, if the feature "NotificationCorrelation" is supported, the notification correlation ID in the "notifId" attribute if received in the SpendingLimitContext data structure provided in the creation or update of the subscription; and +- shall include, when the feature "SubscriptionExpirationTimeControl" is not supported, Policy counters status in the "statusInfos" map, where every PolicyCounterInfo entry shall include: + - the "policyCounterId" attribute with the policy counter identifier; and + - the "currentStatus" attribute with the new policy counter status when the notification is triggered by a change in the policy counter status, or the current policy counter status when the notification is triggered by a change in the pending policy counter status(es); and +- may include, when the feature "SubscriptionExpirationTimeControl" is supported, the Policy counters status in the "statusInfos" map if at this time there is change of policy counter status and/or the update of the expiry time in the "expiry". + +NOTE 1: When the feature "SubscriptionExpirationTimeControl" is supported, and the CHF includes the update of the expiry time, if at this time there is no change of policy counter status, the CHF does not include the "statusInfos" attribute. + +When a policy counter identifier is no longer applicable to the subscriber (e.g. becomes not provisioned), but still exists in the Individual Spending Control Retrieval resource, the CHF may include it in the "statusInfos" map, and set the "currentStatus" attribute to an operator configured policy counter status to indicate this to the NF service consumer. + +A PolicyCounterInfo data structure may include the list of pending policy counter statuses and their activation times within the attribute "penPolCounterStatuses". + +When the feature "SubscriptionExpirationTimeControl" is supported, the CHF may include the "expiry" attribute, representing an update in the time up to which the subscription shall be kept active. When the "expiry" attribute is omitted, it represents that the previously agreed duration of the subscription remains valid. + +NOTE 2: Once the subscription expires, if the NF Service Consumer wants to keep receiving notifications, it needs to create a new subscription in the CHF, as specified in subclause 4.2.2.2. + +The CHF shall not send the policy counter status for the same policy counter until it received the response of the previous status report of the policy counter. + +If the HTTP POST notification request message is accepted by the NF service consumer, it shall acknowledge the receipt of the event notification with a "204 No Content" response, as shown in figure 4.2.4.2-1, step 2. + +If errors occur when processing the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in subclause 5.7. + +If the feature "ES3XX" is supported, and the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in subclause 6.10.9 of 3GPP TS 29.500 [4]. + +If the NF service consumer receives an HTTP POST notification request message for an intermediate spending limit report transaction from the CHF in which no pending policy counter statuses and their activation times are included for a policy counter, i.e., the "penPolCounterStatuses" attribute is not included, the NF service consumer shall cancel all previously provided pending policy counter statuses and their activation times for this policy counter. If the NF service consumer receives an HTTP POST notification request message for an intermediate spending limit report transaction from the CHF containing pending policy counter statuses and their activation times for a previously provided policy counter, the NF service consumer shall replace the existing pending policy counter statuses and their activation times if any. + +If the NF service consumer receives an HTTP POST request for spending limit report initiated by the CHF while it has an ongoing intermediate spending limit report retrieval transaction with the CHF, the NF service consumer shall update the policy counter information based on the HTTP POST request for spending limit report. When the corresponding response for the ongoing intermediate spending limit report retrieval transaction is eventually received, the NF service consumer shall only update policy counter information for counters that were not provided in the previously received HTTP POST request for spending limit report. + +#### 4.2.4.3 Subscription termination request by CHF + +Figure 4.2.4.3-1 shows the scenario where the CHF sends a notification to the NF service consumer, when it requests the termination of the subscription of status changes for all policy counters for a subscriber. + +![Sequence diagram showing the subscription termination request by CHF. The NF service consumer sends a POST request to the CHF, and the CHF responds with a 204 No Content.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +``` +sequenceDiagram + participant NF service consumer + participant CHF + Note left of NF service consumer: NF service consumer + Note right of CHF: CHF + CHF->>NF service consumer: 1. POST.../{notifUri}/terminate + NF service consumer-->>CHF: 2. 204 No Content +``` + +Sequence diagram showing the subscription termination request by CHF. The NF service consumer sends a POST request to the CHF, and the CHF responds with a 204 No Content. + +Figure 4.2.4.3-1: Subscription termination request by CHF + +The CHF shall send an HTTP POST request to the resource notification target address (notifUri) of the NF service consumer received in the subscription creation or modification and shall append the "terminate" segment path at the end of the URI, to indicate the subscription termination and the removal of the Individual Spending Limit Retrieval Subscription resource to the NF service consumer. + +The SubscriptionTerminationInfo data structure provided in the request body shall include the subscriber identification encoded in the "supi" attribute, if the feature "NotificationCorrelation" is supported, the Notification Correlation Id in the "notifId" attribute if received and may include subscription termination information in the "termCause" attribute. + +When the termination request is because the subscriber identified by the SUPI has been removed from the CHF, the CHF shall set the "termCause" attribute to "REMOVED\_SUBSCRIBER". + +If the HTTP POST notification request message is accepted by the NF service consumer, it shall remove the subscription to notifications of all policy counters for a subscriber and shall acknowledge the receipt of the event notification with a "204 No Content" response, as shown in figure 4.2.4.3-1, step 2. + +If errors occur when processing the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in subclause 5.7. + +If the feature "ES3XX" is supported, and the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in subclause 6.10.9 of 3GPP TS 29.500 [4]. + +# --- 5 Nchf\_SpendingLimitControl Service API + +## 5.1 Introduction + +The Nchf\_SpendingLimitControl service shall use the Nchf\_SpendingLimitControl API. + +The API URI of the Nchf\_SpendingLimitControl API shall be: + +**{apiRoot}/** + +The request URIs used in HTTP requests from the NF service consumer towards the CHF shall have the Resource URI structure defined in subclause 4.4.1 of 3GPP TS 29.501 [5], i.e.: + +**{apiRoot}** + +with the following components: + +- The {apiRoot} shall be set as described in 3GPP TS29.501 [5]. +- The shall be "nchf-spendinglimitcontrol". +- The shall be "v1". +- The shall be set as described in subclause 5.3. + +## 5.2 Usage of HTTP + +### 5.2.1 General + +HTTP/2, IETF RFC 7540 [8], shall be used as specified in subclause 5.2 of 3GPP TS 29.500 [4]. + +HTTP/2 shall be transported as specified in subclause 5.3 of 3GPP TS 29.500 [4]. + +The OpenAPI [9] specification of HTTP messages and content bodies for the Nchf\_SpendingLimitControl service is contained in Annex A. + +### 5.2.2 HTTP standard headers + +#### 5.2.2.1 General + +See subclause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers. + +#### 5.2.2.2 Content type + +JSON, IETF RFC 8259 [10], shall be used as content type of the HTTP bodies specified in the present specification, as specified in subclause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json". + +"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [13]. + +### 5.2.3 HTTP custom headers + +#### 5.2.3.1 General + +The Nchf\_SpendingLimitControl API shall support HTTP custom header fields specified in subclause 5.2.3.2 of 3GPP TS 29.500 [4]. + +In this Release of the specification, no specific custom headers are defined for the Nchf\_SpendingLimitControl API. + +## 5.3 Resources + +### 5.3.1 Resource Structure + +Figure 5.3.1-1 shows the resource structure of the Nchf\_SpendingLimitControl API. + +![A hierarchical diagram showing the resource URI structure. It starts with {apiRoot}/nchf-spendinglimitcontrol/v1, which branches to /subscriptions, which in turn branches to/{subscriptionId}.](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) + +``` + +graph TD + Root["{apiRoot}/nchf-spendinglimitcontrol/v1"] --> Subscriptions["/subscriptions"] + Subscriptions --> SubscriptionId["/{subscriptionId}"] + +``` + +A hierarchical diagram showing the resource URI structure. It starts with {apiRoot}/nchf-spendinglimitcontrol/v1, which branches to /subscriptions, which in turn branches to/{subscriptionId}. + +**Figure 5.3.1-1: Resource URI structure of the Nchf\_SpendingLimitControl API** + +Table 5.3.1-1 provides an overview of the resources and applicable HTTP methods. + +**Table 5.3.1-1: Resources and methods overview** + +| Resource name | Resource URI | HTTP method or custom operation | Description | +|--------------------------------------------------|---------------------------------|---------------------------------|----------------------------------------------------------------------------------| +| Spending Limit Retrieval Subscriptions | /subscriptions | POST | Creates a new individual spending limit retrieval subscription. | +| Individual Spending Limit Retrieval Subscription | /subscriptions/{subscriptionId} | PUT | Modifies an existing subscription (e.g. addition of additional policy counters). | +| | | DELETE | Deletes an individual subscription. | + +### 5.3.2 Resource: Spending Limit Retrieval Subscriptions (Collection) + +#### 5.3.2.1 Description + +This resource represents the collection of Nchf\_SpendingLimitControl service subscriptions at a given CHF. + +#### 5.3.2.2 Resource definition + +Resource URI: {apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions + +This resource shall support the resource URI variables defined in table 5.3.2.2-1. + +**Table 5.3.2.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|---------|-----------|-------------------| +| apiRoot | string | See subclause 5.1 | + +#### 5.3.2.3 Resource Standard Methods + +##### 5.3.2.3.1 POST + +This method shall support the URI query parameters specified in table 5.3.2.3.1-1. + +**Table 5.3.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 5.3.2.3.1-2 and the response data structures and response codes specified in table 5.3.2.3.1-3. + +**Table 5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|------------------------------------------------------------------------------------------------------| +| SpendingLimitContext | M | 1 | Contains the information for the creation of a new individual spending limit retrieval subscription. | + +**Table 5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|---------------------|---|-------------|-----------------|--------------------------------------------------------------------------------------| +| SpendingLimitStatus | M | 1 | 201 Created | The spending limit subscription was created and spending limit reports are provided. | +| ProblemDetails | O | 0..1 | 400 Bad Request | (NOTE 2) | + +NOTE 1: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [4] for the POST method shall also apply. +NOTE 2: In addition to protocol and application errors which are specified in subclause 5.2.7.2 of 3GPP TS 29.500 [4], specific errors are described in subclause 5.7. + +**Table 5.3.2.3.1-4: Headers supported by the 201 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure: {apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions/{subscriptionId} | + +#### 5.3.2.4 Resource Custom Operations + +None. + +### 5.3.3 Resource: Individual Spending Limit Retrieval Subscription (Document) + +#### 5.3.3.1 Description + +This resource represents an individual Nchf\_SpendingLimitControl service subscription at a given CHF. + +#### 5.3.3.2 Resource definition + +Resource URI: {apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions/{subscriptionId} + +This resource shall support the resource URI variables defined in table 5.3.3.2-1. + +**Table 5.3.3.2-1: Resource URI variables for this resource** + +| Name | Data type | Definition | +|----------------|-----------|--------------------------------------------------------------------------------| +| apiRoot | string | See subclause 5.1 | +| subscriptionId | string | Identifies a subscription to the CHF spending limit control retrieval service. | + +#### 5.3.3.3 Resource Standard Methods + +##### 5.3.3.3.1 PUT + +This method shall support the URI query parameters specified in table 5.3.3.3.1-1. + +**Table 5.3.3.3.1-1: URI query parameters supported by the PUT method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 5.3.3.3.1-2 and the response data structures and response codes specified in table 5.3.3.3.1-3. + +**Table 5.3.3.3.1-2: Data structures supported by the PUT Request Body on this resource** + +| Data type | P | Cardinality | Description | +|----------------------|---|-------------|-------------------------------------------------------------------------| +| SpendingLimitContext | M | 1 | Modifies the existing individual spending limit retrieval subscription. | + +**Table 5.3.3.3.1-3: Data structures supported by the PUT Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SpendingLimitStatus | M | 1 | 200 OK | Successful case: The individual spending limit subscription was modified and spending limit reports are provided. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during Individual Spending Limit Retrieval Subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CHF (service) instance. Applicable if the feature "ES3XX" is supported. | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during Individual Spending Limit Retrieval Subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CHF (service) instance. Applicable if the feature "ES3XX" is supported. | +| ProblemDetails | O | 0..1 | 400 Bad Request | (NOTE 2) | +| NOTE 1: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [4] for the PUT method shall also apply. | | | | | +| NOTE 2: In addition to protocol and application errors which are specified in subclause 5.2.7.2 of 3GPP TS 29.500 [4], specific errors are described in subclause 5.7. | | | | | + +**Table 5.3.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CHF (service) instance. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the request is redirected | + +**Table 5.3.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CHF (service) instance. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the request is redirected | + +##### 5.3.3.3.2 DELETE + +This method shall support the URI query parameters specified in table 5.3.3.3.2-1. + +**Table 5.3.3.3.3-1: URI query parameters supported by the DELETE method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 5.3.3.3.2-2 and the response data structures and response codes specified in table 5.3.3.3.2-3. + +**Table 5.3.3.3.2-2: Data structures supported by the DELETE Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------|---|-------------|-------------| +| n/a | | | | + +**Table 5.3.3.3.2-3: Data structures supported by the DELETE Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | Successful case: The individual spending limit subscription matching the subscriptionId was deleted. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during Individual Spending Limit Retrieval Subscription deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CHF (service) instance.
Applicable if the feature "ES3XX" is supported. | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during Individual Spending Limit Retrieval Subscription deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative CHF (service) instance.
Applicable if the feature "ES3XX" is supported. | + +NOTE: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [4] for the DELETE method shall also apply. + +**Table 5.3.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CHF (service) instance. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the request is redirected | + +**Table 5.3.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI of the resource located in an alternative CHF (service) instance. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the request is redirected | + +## 5.4 Custom Operations without associated resources + +None. + +## 5.5 Notifications + +### 5.5.1 General + +Notification shall comply with subclause 6.2 of 3GPP TS 29.500 [4] and subclause 4.6.2.3 of 3GPP TS 29.501 [5]. + +**Table 5.5.1-1: Notifications overview** + +| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | +|-----------------------------|----------------------|---------------------------------|-----------------------------------------| +| Spending limit notification | {notifUri}/notify | notify (POST) | Counter Status changes notification. | +| Subscription Termination | {notifUri}/terminate | terminate (POST) | Indication of subscription termination. | + +### 5.5.2 Spending limit notification + +#### 5.5.2.1 Description + +The spending limit notification is used by the CHF to notify the change of the status of the subscribed policy counters for a subscriber and/or to provide one or more pending statuses for a subscribed policy counter together with the time they shall be applied. + +#### 5.5.2.2 Target URI + +The Callback URI {notifUri}/notify shall be used with the callback URI variables defined in table 5.5.2.2-1. + +**Table 5.5.2.2-1: Callback URI variables** + +| Name | Data type | Definition | +|----------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notifUri | Uri | The Notification Uri as assigned by the NF service consumer during the subscription service operation and described within the SpendingLimitContext data type (see table 5.6.2.2-1). | + +#### 5.5.2.3 Standard Methods + +##### 5.5.2.3.1 POST + +This method shall support the URI query parameters specified in table 5.5.2.3.1-1. + +**Table 5.5.2.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 5.5.2.3.1-2 and the response data structures and response codes specified in table 5.5.2.3.1-3. + +**Table 5.5.2.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|---------------------|---|-------------|-------------------------------------------------------------| +| SpendingLimitStatus | M | 1 | Provides information about the statuses of policy counters. | + +**Table 5.5.2.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The receipt of the notification is acknowledged. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during Spending limit report. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent. Applicable if the feature "ES3XX" is supported. | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during Spending limit report. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent. Applicable if the feature "ES3XX" is supported. | + +NOTE: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [4] for the POST method shall also apply. + +**Table 5.3.3.2-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +**Table 5.3.3.2-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +### 5.5.3 Subscription Termination + +#### 5.5.3.1 Description + +The Subscription Termination request is used by the CHF to request the NF service consumer the termination of the subscription to policy counter status changes. + +#### 5.5.3.2 Target URI + +The Callback URI {notifUri}/terminate shall be used with the callback URI variables defined in table 5.5.3.2-1. + +**Table 5.5.3.2-1: Callback URI variables** + +| Name | Data type | Definition | +|----------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notifUri | Uri | The Notification Uri as assigned by the NF service consumer during the subscription service operation and described within the SpendingLimitContext data type (see table 5.6.2.2-1). | + +#### 5.5.3.3 Standard Methods + +##### 5.5.3.3.1 POST + +This method shall support the URI query parameters specified in table 5.5.3.3.1-1. + +**Table 5.5.3.3.1-1: URI query parameters supported by the POST method on this resource** + +| Name | Data type | P | Cardinality | Description | +|------|-----------|---|-------------|-------------| +| n/a | | | | | + +This method shall support the request data structures specified in table 5.5.3.3.1-2 and the response data structures and response codes specified in table 5.5.3.3.1-3. + +**Table 5.5.3.3.1-2: Data structures supported by the POST Request Body on this resource** + +| Data type | P | Cardinality | Description | +|-----------------------------|---|-------------|----------------------------------------------------------| +| SubscriptionTerminationInfo | M | 1 | Provides information about the deletion of the resource. | + +**Table 5.5.3.3.1-3: Data structures supported by the POST Response Body on this resource** + +| Data type | P | Cardinality | Response codes | Description | +|------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n/a | | | 204 No Content | The receipt of the Notification is acknowledged. | +| RedirectResponse | O | 0..1 | 307 Temporary Redirect | Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.
Applicable if the feature "ES3XX" is supported. | +| RedirectResponse | O | 0..1 | 308 Permanent Redirect | Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.
Applicable if the feature "ES3XX" is supported. | + +NOTE: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [4] for the POST method shall also apply. + +**Table 5.5.3.3.1-4: Headers supported by the 307 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +**Table 5.5.3.3.1-5: Headers supported by the 308 Response Code on this resource** + +| Name | Data type | P | Cardinality | Description | +|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Location | string | M | 1 | An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. | +| 3gpp-Sbi-Target-Nf-Id | string | O | 0..1 | Identifier of the target NF (service) instance towards which the notification request is redirected | + +## 5.6 Data Model + +### 5.6.1 General + +This subclause specifies the application data model supported by the API. + +Table 5.6.1-1 specifies the data types defined for the Nchf\_SpendingLimitControl service based interface protocol. + +**Table 5.6.1-1: Nchf\_SpendingLimitControl specific Data Types** + +| Data type | Section defined | Description | Applicability | +|------------------------------|------------------------|-------------------------------------------------------------------------------------------------------|----------------------| +| SpendingLimitContext | 5.6.2.2 | Describes the subscription data structure required for an individual CHF spending limit subscription. | | +| SpendingLimitStatus | 5.6.2.3 | Describes the data structure presenting the statuses of policy counters. | | +| PolicyCounterInfo | 5.6.2.4 | Describes the data structure presenting the policy counter status. | | +| PendingPolicyCounterStatuses | 5.6.2.5 | Describes the data structure presenting the pending policy counter status. | | +| PolicyCounterId | 5.6.3.2 | Identifies a policy counter. | | +| SubscriptionTerminationInfo | 5.6.2.6 | Describes the data structure presenting the indication of the termination of the subscription. | | +| TerminationCause | 5.6.3.3 | Represents the types of causes for requesting the termination of the subscription. | | + +Table 5.6.1-2 specifies data types re-used by the Nchf\_SpendingLimitControl service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Nchf\_SpendingLimitControl service based interface. + +**Table 5.6.1-2: Nchf\_SpendingLimitControl re-used Data Types** + +| Data type | Reference | Comments | Applicability | +|-------------------|---------------------|--------------------------------------------------------------------------------------|----------------------| +| DateTime | 3GPP TS 29.571 [11] | String with format "date-time" as defined in OpenAPI Specification [9]. | | +| Uri | 3GPP TS 29.571 [11] | | | +| Supi | 3GPP TS 29.571 [11] | | | +| Gpsi | 3GPP TS 29.571 [11] | | | +| RedirectResponse | 3GPP TS 29.571 [11] | Contains redirection related information. | ES3XX | +| SupportedFeatures | 3GPP TS 29.571 [11] | Used to negotiate the applicability of the optional features defined in table 5.8-1. | | + +### 5.6.2 Structured data types + +#### 5.6.2.1 Introduction + +This subclause defines the structures to be used in resource representations. + +#### 5.6.2.2 Type SpendingLimitContext + +**Table 5.6.2.2-1: Definition of type SpendingLimitContext** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|------------------|------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| supi | Supi | C | 0..1 | The Subscription Permanent Identifier (Supi) shall be present within the initial spending limit retrieval procedure (creation of a new individual subscription) and intermediate spending limit retrieval procedure (modification of an existing subscription). | | +| gpsi | Gpsi | O | 0..1 | The Generic Public Subscription Identifier (Gpsi) shall contain either an External Id or an MSISDN. It may be present within the initial spending limit retrieval procedure (creation of a new individual subscription) and intermediate spending limit retrieval procedure (modification of an existing subscription). | | +| policyCounterIds | array(PolicyCounterId) | O | 1..N | This is a list of policy counter identifier(s), which identifies policy counters maintained per subscriber within the CHF. | | +| notifUri | Uri | C | 0..1 | This attribute identifies the recipient of spending limit notifications sent to the NF service consumer by the CHF. The notifUri shall be present within the initial spending limit retrieval procedure (creation of a new individual subscription) and within the intermediate spending limit retrieval procedure (modification of an existing subscription). | | +| notifId | string | C | 0..1 | Notification Correlation ID assigned by the NF service consumer. It shall be included if the NotificationCorrelation feature is supported, the notifUri does not encode the notification correlation Id, and the PCF(s) requires multiple subscriptions for the same SUPI, e.g. UE accesses multiple network slices. | NotificationCorrelation | +| expiry | DateTime | O | 0..1 | The expiry time may be included in a subscription request. When present, this IE shall represent the longest duration time after which the subscription shall become invalid. | SubscriptionExpirationTimeControl | + +| | | | | | | +|-------------------|-------------------|---|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| supportedFeatures | SupportedFeatures | C | 0..1 | The list of supported features as described in subclause 5.8 shall be supplied by the NF service consumer in the POST request that request the creation of a spending limit report resource and intermediate spending limit retrieval procedure (modification of an existing subscription). | | +|-------------------|-------------------|---|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +#### 5.6.2.3 Type SpendingLimitStatus + +**Table 5.6.2.3-1: Definition of type SpendingLimitStatus** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-------------------|------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| supi | Supi | O | 0..1 | The Subscription Permanent Identifier (Supi) shall be present within the callback notify service operation (notification of the status of subscribed policy counters). | | +| notifId | string | C | 0..1 | Notification Correlation ID assigned by the NF service consumer. It shall be included if provided during the subscription within the SpendingLimitContext data type. | NotificationCorrelation | +| statusInfos | map(PolicyCounterInfo) | C | 1..N | Status of the requested policy counters. The key of the map is the attribute "policyCounterId". It may be omitted when the feature SubscriptionExpirationTimeControl is supported and the CHF only requires to update the "expiry" attribute. | | +| expiry | DateTime | C | 0..1 | This expiry time shall be included in a subscription response, if the expiry time was included in the request. It may be included in a subscription response and notification request based on operator policies for the control in the CHF of the subscription duration. | SubscriptionExpirationTimeControl | +| supportedFeatures | SupportedFeatures | C | 0..1 | If the supportedFeatures is included in the request by the NF service consumer, it shall be supplied in the reply of the corresponding request by the CHF. | | + +#### 5.6.2.4 Type PolicyCounterInfo + +**Table 5.6.2.4-1: Definition of type PolicyCounterInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|-----------------------|-----------------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| policyCounterId | PolicyCounterId | M | 1 | Identifies the requested policy counter. | | +| currentStatus | string | M | 1 | Identifies the policy counter status applicable for a specific policy counter identified by the policyCounterId. The values (e.g. valid, invalid or any other status) are not specified. The interpretation and actions related to the defined values are out of scope of 3GPP. | | +| penPolCounterStatuses | array(PendingPolicyCounterStatus) | O | 1..N | Provides the pending policy counter status. | | + +#### 5.6.2.5 Type PendingPolicyCounterStatus + +**Table 5.6.2.5-1: Definition of type PendingPolicyCounterStatus** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|---------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| policyCounterStatus | string | M | 1 | Identifies the policy counter status applicable for a specific policy counter identified by the PolicyCounterId. The values (e.g. valid, invalid or any other status) are not specified. The interpretation and actions related to the defined values are out of scope of 3GPP. | | +| activationTime | DateTime | M | 1 | Indicates the time at which the pending policy counter status becomes the current status of a policy counter. | | + +#### 5.6.2.6 Type SubscriptionTerminationInfo + +**Table 5.6.2.6-1: Definition of type SubscriptionTerminationInfo** + +| Attribute name | Data type | P | Cardinality | Description | Applicability | +|----------------|------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| supi | Supi | M | 1 | Subscription Permanent Identifier. | | +| notifId | string | C | 0..1 | Notification Correlation ID assigned by the NF service consumer. It shall be included if provided during the subscription within the SpendingLimitContext data type. | NotificationCorrelation | +| termCause | TerminationCause | O | 0..1 | Indicates the cause for requesting the termination of the subscription to policy counter status changes. | | + +### 5.6.3 Simple data types and enumerations + +#### 5.6.3.1 Introduction + +This subclause defines simple data types and enumerations that can be referenced from data structures defined in the previous subclauses. + +#### 5.6.3.2 Simple data types + +The simple data types defined in table 5.6.3.2-1 shall be supported. + +**Table 5.6.3.2-1: Simple data types** + +| Type Name | Type Definition | Description | Applicability | +|-----------------|-----------------|------------------------------|---------------| +| PolicyCounterId | string | Identifies a policy counter. | | + +#### 5.6.3.3 Enumeration: TerminationCause + +The enumeration "TerminationCause" represents the types of causes the CHF can report when requesting the termination of the subscription. + +**Table 5.6.3.3-1: Enumeration TerminationCause** + +| Enumeration value | Description | Applicability | +|--------------------|----------------------------------------------------------------------|---------------| +| REMOVED_SUBSCRIBER | The subscriber identified by the SUPI has been removed from the CHF. | | + +## 5.7 Error handling + +### 5.7.1 General + +HTTP error handling shall be supported as specified in subclause 5.2.4 of 3GPP TS 29.500 [4]. + +For the Nchf\_SpendingLimitControl service API, HTTP error responses shall be supported as specified in subclause 4.8 of 3GPP TS 29.501 [5]. + +Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4]. + +In addition, the requirements in the following subclauses shall apply. + +### 5.7.2 Protocol Errors + +In this Release of the specification, there are no additional protocol errors applicable for the Nchf\_SpendingLimitControl service API. + +### 5.7.3 Application Errors + +The application errors defined for the Nchf\_SpendingLimitControl service API are listed in table 5.7.3-1. + +**Table 5.7.3-1: Application errors** + +| Application Error | HTTP status code | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------------------------------------------------------------------------------------------------------| +| USER_UNKNOWN | 400 Bad Request | The subscriber specified in the request is not known at the CHF and the subscription cannot be created. | +| NO_AVAILABLE_POLICY_COUNTERS | 400 Bad Request | There are no policy counters available for the subscriber at the CHF | +| UNKNOWN_POLICY_COUNTERS | 400 Bad Request | The policy counter identifiers in the request are not known at the CHF. | +| NOTE: Including a "ProblemDetails" data structure with the "cause" attribute in the HTTP response is optional unless explicitly mandated in the service operation subclauses. | | | + +## 5.8 Feature negotiation + +The optional features in table 5.8-1 are defined for the Nchf\_SpendingLimitControl Service API. They shall be negotiated using the extensibility mechanism defined in subclause 6.6.2 of 3GPP TS 29.500 [4]. + +**Table 5.8-1: Supported Features** + +| Feature number | Feature Name | Description | +|----------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | SubscriptionExpirationTime Control | Indicates the support of a expiry time to control the time duration of the subscription to changes of policy counters status. | +| 2 | NotificationCorrelation | Indicates the support of the explicit indication of the notification correlation id | +| 3 | ES3XX | Extended Support for 3xx redirections. This feature indicates the support of redirection for any service operation, according to Stateless NF procedures as specified in subclauses 6.5.3.2 and 6.5.3.3 of 3GPP TS 29.500 [4] and according to HTTP redirection principles for indirect communication, as specified in subclause 6.10.9 of 3GPP TS 29.500 [4]. | + +## 5.9 Security + +As indicated in 3GPP TS 33.501 [14] and 3GPP TS 29.500 [4], the access to the Nchf\_SpendingLimitControl API, based on local configuration, may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [15]), using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [16]) plays the role of the authorization server. + +If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nchf\_SpendingLimitControl API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [16], subclause 5.4.2.2. + +NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nchf\_SpendingLimitControl service. + +The Nchf\_SpendingLimitControl API defines a single scope "nchf-spendinglimitcontrol" for OAuth2 authorization (as specified in 3GPP TS 33.501 [14]) for the entire API, and it does not define any additional scopes at resource or operation level. + +# Annex A (normative): OpenAPI specification + +## A.1 General + +The present Annex contains an OpenAPI [9] specification of HTTP messages and content bodies used by the Nchf\_SpendingLimitControl Service API. + +This Annex shall take precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API. + +NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply. + +Informative copies of the OpenAPI specification file contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5B of the 3GPP TR 21.900 [17] and subclause 5.3.1 of the 3GPP TS 29.501 [5] for further information). + +## A.2 Nchf\_SpendingLimitControl Service API + +``` + +openapi: 3.0.0 +info: + version: 1.1.3 + title: Nchf_SpendingLimitControl + description: | + Nchf Spending Limit Control Service. + © 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). + All rights reserved. +externalDocs: + description: 3GPP TS 29.594 V16.6.0; 5G System; Spending Limit Control Service. + url: 'http://www.3gpp.org/ftp/Specs/archive/29_series/29.594/' +servers: + - url: '{apiRoot}/nchf-spendinglimitcontrol/v1' + variables: + apiRoot: + default: https://example.com + description: apiRoot as defined in subclause subclause 4.4 of 3GPP TS 29.501 +security: + - {} + - oAuth2ClientCredentials: + - nchf-spendinglimitcontrol +paths: + /subscriptions: + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SpendingLimitContext' + responses: + '201': + description: Success + content: + application/json: + schema: + $ref: '#/components/schemas/SpendingLimitStatus' + headers: + Location: + description: 'Contains the URI of the created individual spending limit resource, + according to the structure: {apiRoot}/nchf-spendinglimitcontrol/v1/subscriptions/{subscriptionId}' + required: true + schema: + type: string + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + +``` + +``` +'403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' +'404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' +'411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' +'413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' +'415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' +'429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' +'500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' +'503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' +default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +callbacks: + statusNotification: + '{ $request.body#/notifUri }/notify': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SpendingLimitStatus' +responses: + '204': + description: No Content, Notification was successful + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +subscriptionTermination: + '{ $request.body#/notifUri }/terminate': + post: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SubscriptionTerminationInfo' +responses: + '204': + description: No Content, Notification was successful + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': +``` + +``` + + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + /subscriptions/{subscriptionId}: + parameters: + - in: path + name: subscriptionId + description: Identifies an individual spending limit retrieval subscription. + required: true + schema: + type: string + put: + requestBody: + required: true + content: + application/json: + schema: + $ref: '#/components/schemas/SpendingLimitContext' + responses: + '200': + description: OK. Resource was successfully modified and representation is returned + content: + application/json: + schema: + $ref: '#/components/schemas/SpendingLimitStatus' + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '411': + $ref: 'TS29571_CommonData.yaml#/components/responses/411' + '413': + $ref: 'TS29571_CommonData.yaml#/components/responses/413' + '415': + $ref: 'TS29571_CommonData.yaml#/components/responses/415' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' + delete: + responses: + '204': + description: No Content. Resource was successfully deleted + '307': + $ref: 'TS29571_CommonData.yaml#/components/responses/307' + '308': + $ref: 'TS29571_CommonData.yaml#/components/responses/308' + '400': + $ref: 'TS29571_CommonData.yaml#/components/responses/400' + '401': + $ref: 'TS29571_CommonData.yaml#/components/responses/401' + '403': + +``` + +``` + $ref: 'TS29571_CommonData.yaml#/components/responses/403' + '404': + $ref: 'TS29571_CommonData.yaml#/components/responses/404' + '429': + $ref: 'TS29571_CommonData.yaml#/components/responses/429' + '500': + $ref: 'TS29571_CommonData.yaml#/components/responses/500' + '503': + $ref: 'TS29571_CommonData.yaml#/components/responses/503' + default: + $ref: 'TS29571_CommonData.yaml#/components/responses/default' +components: + securitySchemes: + oAuth2ClientCredentials: + type: oauth2 + flows: + clientCredentials: + tokenUrl: '{nrfApiRoot}/oauth2/token' + scopes: + nchf-spendinglimitcontrol: Access to the Nchf_SpendingLimitControl API +schemas: + SpendingLimitContext: + type: object + properties: + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + gpsi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' + policyCounterIds: + type: array + items: + $ref: '#/components/schemas/PolicyCounterId' + minItems: 1 + description: This is a list of policy counter identifier(s), which identifies policy +counters maintained per subscriber within the CHF. + notifUri: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' + expiry: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + notifId: + type: string + SpendingLimitStatus: + type: object + properties: + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + notifId: + type: string + statusInfos: + type: object + additionalProperties: + $ref: '#/components/schemas/PolicyCounterInfo' + minProperties: 1 + description: Status of the requested policy counters. The key of the map is the attribute +"policyCounterId". + expiry: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + supportedFeatures: + $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' + PolicyCounterInfo: + type: object + properties: + policyCounterId: + $ref: '#/components/schemas/PolicyCounterId' + currentStatus: + type: string + description: Identifies the policy counter status applicable for a specific policy counter +identified by the policyCounterId. The values (e.g. valid, invalid or any other status) are not +specified. The interpretation and actions related to the defined values are out of scope of 3GPP. + penPolCounterStatuses: + type: array + items: + $ref: '#/components/schemas/PendingPolicyCounterStatus' + minItems: 1 + description: Provides the pending policy counter status. +required: +``` + +``` + + - policyCounterId + - currentStatus +PendingPolicyCounterStatus: + type: object + properties: + policyCounterStatus: + type: string + description: Identifies the policy counter status applicable for a specific policy counter identified by the policyCounterId. The values (e.g. valid, invalid or any other status) are not specified. The interpretation and actions related to the defined values are out of scope of 3GPP. + activationTime: + $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' + required: + - policyCounterStatus + - activationTime +PolicyCounterId: + type: string + description: Identifies a policy counter. +SubscriptionTerminationInfo: + type: object + properties: + supi: + $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' + notifId: + type: string + termCause: + $ref: '#/components/schemas/TerminationCause' + required: + - supi +TerminationCause: + anyOf: + - type: string + enum: + - REMOVED_SUBSCRIBER + - type: string + +``` + +# --- Annex B (normative): 5GC and EPC interworking scenario support + +## B.1 Scope + +This annex defines procedures for the Nchf\_SpendingLimitControl service for 5GC and EPC interworking scenarios specified in clause B.1 of 3GPP TS 29.512 [18]. + +## --- B.2 Nchf\_SpendingLimitControl Service + +### B.2.1 Service Description + +#### B.2.1.1 Overview + +The overview in subclause 4.1.1 applies. + +#### B.2.1.2 Service Architecture + +The architecture in subclause 4.1.2 applies. + +## --- B.3 Service Operation + +### B.3.1 Introduction + +The service operations defined in subclause 4.2 shall be applicable. + +### B.3.2 Nchf\_SpendingLimitControl\_Subscribe Service Operation + +Subclause 4.2.2.2 and subclause 4.2.2.3 are applied with the differences that the PCF shall include (if available) in SpendingLimitContext data structure: + +- the IMSI of the user within the "supi" attribute; +- the MSISDN of the user within the "gpsi" attribute; + +### B.3.3 Nchf\_SpendingLimitControl\_Unsubscribe Service Operation + +Subclause 4.2.3 applies. + +### B.3.4 Nchf\_SpendingLimitControl\_Notify Service Operation + +Subclause 4.2.4 applies. + +# --- Annex C (normative): Wireless and wireline convergence access support + +## C.1 Scope + +This annex defines procedures for wireless and wireline convergence access support for 5GS. The specific stage 2 definition and related procedures are contained in 3GPP TS 23.316 [19]. The System Architecture for wireless and wireline convergence access is defined in 3GPP TS 23.501 [2]. + +## --- C.2 Nchf\_SpendingLimitControl Service + +### C.2.1 Service Description + +#### C.2.1.1 Overview + +Subclause 4.1.1 applies with the following exceptions: + +- the UE is replaced by the 5G-RG and the W-AGF, which is acting as a UE towards the 5GC on behalf of the FN-RG; and +- roaming is only applicable to a 5G-RG connecting to the 5GC via NG RAN, i.e., the H-PCF interaction with the H-CHF for the home-routed scenario only applies to a 5G-RG connecting to the 5GC via NG RAN. + +#### C.2.1.2 Service Architecture + +The architecture in subclause 4.1.2 applies. + +## --- C.3 Service Operation + +### C.3.1 Introduction + +The service operations defined in subclause 4.2.1 apply. + +### C.3.2 Nchf\_SpendingLimitControl\_Subscribe Service Operation + +#### C.3.2.1 General + +Subclauses 4.2.2.2 and 4.2.2.3 are applied with the differences that the NF service consumer shall include (if available) in SpendingLimitContext data structure: + +- a IMSI or a Global Cable Identifier (GCI) or a Global Line Identifier (GLI) as specified in 3GPP TS 23.316 [19] subclause 4.7, encoded as specified in 3GPP TS 29.571[11], subclause 5.3.2, within the "supi" attribute. + +### C.3.3 Nchf\_SpendingLimitControl\_Unsubscribe Service Operation + +Subclause 4.2.3 applies. + +### C.3.4 Nchf\_SpendingLimitControl\_Notify Service Operation + +Subclause 4.2.4 applies. + +# --- Annex D (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|--------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2018-04 | | | | | | TS skeleton of Spending Limit Control Service specification | 0.0.0 | +| 2018-04 | CT3#96 | | | | | Inclusion of documents agreed in CT3#96: C3-182160, C3-182161, C3-182167, C3-182432, C3-182433, C3-182434, C3-182435, C3-182436, C3-182437, C3-182479 | 0.1.0 | +| 2018-05 | CT3#97 | | | | | Inclusion of documents agreed in CT3#97: C3-183138, C3-183288, C3-183538, C3-183539, C3-183541, C3-183543, C3-183544, C3-183545, C3-183546, C3-183547, C3-183548, C3-183550, C3-183552, C3-183780, C3-183782, C3-183830, C3-183831 | 0.2.0 | +| 2018-06 | CT#80 | CP-181026 | | | | TS sent for approval to TSG | 1.0.0 | +| 2018-06 | CT#80 | CP-181026 | | | | TS approved by plenary | 15.0.0 | +| 2018-09 | CT#81 | CP-182015 | 0001 | 1 | F | Removal of possibility of confusion related to 3GPP TS 29.513, custom headers, verbal forms and OpenAPI corrections | 15.1.0 | +| 2018-09 | CT#81 | CP-182221 | 0002 | 4 | F | Introduction of the simple data type "policyCounterId" | 15.1.0 | +| 2018-09 | CT#81 | CP-182098 | 0003 | 3 | F | Update and corrections of the data model | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0004 | 2 | F | Integration of error handling | 15.1.0 | +| 2018-09 | CT#81 | CP-182015 | 0007 | | F | ED – Continuous reporting and policy counter status change | 15.1.0 | +| 2018-09 | CT#81 | CP-182099 | 0008 | 3 | F | Termination of the subscription of status changes for all policy counters by CHF | 15.1.0 | +| 2018-12 | CT#82 | CP-183205 | 0009 | | F | Application of resource illustration rule | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0010 | | F | Consolidation of the term "notificationUri" | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0011 | | F | Clarification of "intermediate spending limit report retrieval" usage | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0012 | | F | Correction of wrong reference for supi in OpenAPI doc | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0013 | | F | Correction of the originator for application error responses | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0014 | 1 | F | Application of externalDocs field in OpenAPI doc | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0015 | 1 | F | Application of version pattern rule in OpenAPI doc | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0016 | 1 | F | Corrections to OpenAPI file | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0017 | | F | Default value for apiRoot | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0018 | | F | Cardinality | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0019 | 2 | F | Sending of GPSI (MSISDN) in Initial Spending Limit retrieval | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0020 | 1 | F | Update of content types | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0021 | 1 | F | Authorization of NF service access by OAuth 2.0 | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0022 | 1 | F | Introduction of status code 404 Not Found as mandatory status code and missing ones | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0023 | 1 | F | Location Header | 15.2.0 | +| 2018-12 | CT#82 | CP-183205 | 0024 | 2 | F | Correcting application error | 15.2.0 | +| 2019-03 | CT#83 | CP-190113 | 0025 | 1 | F | Correction of Resource URI | 15.3.0 | +| 2019-03 | CT#83 | CP-190113 | 0026 | 1 | F | Correction relating to the introduction of the General Public Subscription Identifier | 15.3.0 | +| 2019-03 | CT#83 | CP-190068 | 0027 | 2 | F | OpenAPI info version update | 15.3.0 | +| 2019-03 | CT#83 | CP-190067 | 0028 | | F | Correction of wrong usage of key word "items" | 15.3.0 | +| 2019-06 | CT#84 | CP-191189 | 0030 | 3 | F | Precedence of OpenAPI file | 15.4.0 | +| 2019-06 | CT#84 | CP-191189 | 0031 | 1 | F | Copyright Note in YAML file | 15.4.0 | +| 2019-06 | CT#84 | CP-191189 | 0033 | | F | OpenAPI version number update | 15.4.0 | +| 2019-06 | CT#84 | CP-191089 | 0032 | 1 | B | Race Condition handling | 16.0.0 | +| 2019-09 | CT#85 | CP-192151 | 0035 | | A | NF service consumer pending policy counter handling | 16.1.0 | +| 2019-09 | CT#85 | CP-192156 | 0036 | 1 | B | Support of Expiry Time | 16.1.0 | +| 2019-09 | CT#85 | CP-192151 | 0038 | | A | Correction to Subscription Termination service operation | 16.1.0 | +| 2019-09 | CT#85 | CP-192151 | 0040 | | A | Correction to subscription creation/update response | 16.1.0 | +| 2019-09 | CT#85 | CP-192151 | 0042 | | A | Corrections to subscription request descriptions | 16.1.0 | +| 2019-09 | CT#85 | CP-192151 | 0044 | | A | Handling of unknown policy counters | 16.1.0 | +| 2019-09 | CT#85 | CP-192173 | 0045 | | F | OpenAPI version update for TS 29.594 Rel-16 | 16.1.0 | +| 2020-06 | CT#88e | CP-201233 | 0046 | | F | Description of "activationTime" attribute | 16.2.0 | +| 2020-06 | CT#88e | CP-201233 | 0047 | | F | Miscellaneous corrections | 16.2.0 | +| 2020-06 | CT#88e | CP-201244 | 0048 | 1 | F | Storage of YAML files in ETSI Forge | 16.2.0 | +| 2020-06 | CT#88e | CP-201256 | 0049 | 1 | F | URI of the Nchf_SpendingLimitControl service | 16.2.0 | +| 2020-06 | CT#88e | CP-201244 | 0050 | 1 | F | Optionality of ProblemDetails | 16.2.0 | +| 2020-06 | CT#88e | CP-201244 | 0052 | 1 | F | Supported headers, Resource Data type | 16.2.0 | +| 2020-06 | CT#88e | CP-201255 | 0053 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.2.0 | +| 2020-09 | CT#89e | CP-202058 | 0056 | 1 | A | Correction to spending limit subscribe and unsubscribe procedures | 16.3.0 | +| 2020-09 | CT#89e | CP-202058 | 0058 | 1 | A | Nchf_SpendingLimitControl Service support of interworking | 16.3.0 | +| 2020-12 | CT#90e | CP-203139 | 0061 | 1 | F | Essential corrections and alignments | 16.4.0 | +| 2020-12 | CT#90e | CP-203139 | 0062 | 1 | F | Storage of YAML files in 3GPP Forge | 16.4.0 | +| 2020-12 | CT#90e | CP-203122 | 0064 | 1 | A | Correction to Intermediate spending limit report retrieval | 16.4.0 | +| 2020-12 | CT#90e | CP-203128 | 0065 | | F | Correction to subscription's expiry time | 16.4.0 | +| 2020-12 | CT#90e | CP-203128 | 0066 | 1 | F | Correction to subscription create service operation | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------|--------| +| 2020-12 | CT#90e | CP-203152 | 0068 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.4.0 | +| 2021-03 | CT#91e | CP-210191 | 0070 | 2 | F | Support of stateless NFs | 16.5.0 | +| 2021-03 | CT#91e | CP-210202 | 0071 | 2 | F | Correction to Wireline Access information | 16.5.0 | +| 2021-03 | CT#91e | CP-210239 | 0078 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.5.0 | +| 2021-06 | CT#92e | CP-211210 | 0081 | 1 | A | Correction to policyCounterId | 16.6.0 | +| 2021-06 | CT#92e | CP-211219 | 0083 | 1 | F | Correction to expiry time | 16.6.0 | +| 2021-06 | CT#92e | CP-211219 | 0085 | 1 | F | Correction to notification correlation id | 16.6.0 | +| 2021-06 | CT#92e | CP-211219 | 0089 | 1 | F | Correction to the termination procedure | 16.6.0 | +| 2021-06 | CT#92e | CP-211200 | 0091 | 1 | F | Temporary and Permanent Redirection | 16.6.0 | +| 2021-06 | CT#92e | CP-211264 | 0093 | | F | Update of OpenAPI version and TS version in externalDocs field | 16.6.0 | +| 2022-03 | CT#95e | CP-220176 | 0097 | 1 | F | Alignment of "Application Errors" clause with SBI TS template | 16.7.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29909/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-16/29_series/29909/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2183935c27337b738858abe7f9bc7eb3d8b59aa --- /dev/null +++ b/marked/Rel-16/29_series/29909/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b96186fed27bfd70c8f9fc5b0208c8e373e91389cd74e9dc9317a27cd4970494 +size 20945 diff --git a/marked/Rel-16/29_series/29909/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-16/29_series/29909/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3ab6604e22cbc7ac2dbe048739d36a9c1c090f0 --- /dev/null +++ b/marked/Rel-16/29_series/29909/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cf735cab63f93218c549558fd5fb49a303d12977b2d89eee620ebd1045a5582 +size 63205 diff --git a/marked/Rel-16/29_series/29909/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/29_series/29909/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6cf727336daac867354b2255f76ae8d3f01797f --- /dev/null +++ b/marked/Rel-16/29_series/29909/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f12f08d295ae0cba56f8698f03ec55e13ba0a88f76397d18bec464f5149982e +size 38443 diff --git a/marked/Rel-16/29_series/29909/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/29_series/29909/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b13d4424e2ea0749498c9b50aa03ab37d96db42a --- /dev/null +++ b/marked/Rel-16/29_series/29909/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ac309b4b218a39388cd6cfec4cac600e74a5f2f054ce10166dc6a60895b08ae +size 30543 diff --git a/marked/Rel-16/29_series/29909/raw.md b/marked/Rel-16/29_series/29909/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b932e18feb10383dfa60c40646a6681c1e5e3216 --- /dev/null +++ b/marked/Rel-16/29_series/29909/raw.md @@ -0,0 +1,755 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 The status of Diameter in 3GPP..... | 7 | +| 4.1 General ..... | 7 | +| 4.2 Diameter-based applications before Release 8..... | 7 | +| 4.3 Problem description..... | 8 | +| 4.4 Existing and ongoing effort..... | 9 | +| 5 Proposed alternatives rules for identified problems..... | 9 | +| 5.1 General ..... | 9 | +| 5.2 Item 1: Setting of "M" bit on 3GPP defined AVPs..... | 10 | +| 5.2.0 General ..... | 10 | +| 5.2.1 Proposal 1 (IETF) ..... | 10 | +| 5.2.2 Proposal 2 ..... | 10 | +| 5.2.3 3GPP evaluation ..... | 10 | +| 5.3 Item 2: Re-use of AVPs ..... | 10 | +| 5.3.1 General ..... | 10 | +| 5.3.2 Proposal 1 ..... | 10 | +| 5.3.3 Proposal 2 (IETF) ..... | 10 | +| 5.3.4 3GPP evaluation ..... | 11 | +| 5.4 Item 3: Version handling..... | 11 | +| 5.4.0 General ..... | 11 | +| 5.4.1 Proposal 1 ..... | 11 | +| 5.4.2 Proposal 2 ..... | 11 | +| 5.4.3 Proposal 3 - IETF ..... | 11 | +| 5.4.4 Proposal 4 ..... | 11 | +| 5.4.5 Proposal 5 ..... | 12 | +| 5.4.5.1 General..... | 12 | +| 5.4.5.2 Defining new functionality ..... | 12 | +| 5.4.5.2.1 General ..... | 12 | +| 5.4.5.2.2 Changing the version of the interface ..... | 12 | +| 5.4.5.2.3 Capabilities Exchange Request..... | 12 | +| 5.4.5.2.4 Capabilities Exchange Answer..... | 13 | +| 5.4.5.2.5 AVPs ..... | 13 | +| 5.4.5.2.5.1 Supported-Application-Variant AVP..... | 13 | +| 5.4.5.2.5.2 Vendor-Specific-Application-Variant AVP ..... | 14 | +| 5.4.6 3GPP evaluation ..... | 14 | +| 5.5 Item 4: Setting of a new Application-Id..... | 14 | +| 5.5.0 General ..... | 14 | +| 5.5.1 Proposal 1 - IETF ..... | 15 | +| 5.5.2 Proposal 2 ..... | 15 | +| 5.5.3 Proposal 3 ..... | 16 | +| 5.5.4 3GPP evaluation ..... | 16 | +| 5.6 Item 5: New Values to an existing enumerated AVP..... | 16 | +| 5.6.1 Proposal 1 ..... | 16 | +| 5.6.2 Proposal 2 ..... | 16 | +| 5.6.3 Proposal 3 ..... | 16 | +| 5.6.4 Proposal 4 ..... | 17 | +| 5.6.5 Proposal 5 ..... | 17 | +| 5.6.6 3GPP evaluation ..... | 17 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------|-----------| +| 5.7 | Item 6: Re-use of commands in new applications..... | 17 | +| 5.7.0 | General ..... | 17 | +| 5.7.1 | Proposal 1 ..... | 17 | +| 5.7.2 | 3GPP evaluation ..... | 17 | +| 6 | Conclusion ..... | 18 | +| Annex A (Informative): | Roaming Infrastructure..... | 19 | +| A.0 | General..... | 19 | +| A.1 | Deployment of S6a-Diameter Relay Pools ..... | 19 | +| A.2 | Deployment of S9 and Wd*-Diameter Relay Pools..... | 21 | +| A.3 | Guidelines for connecting to the inter-operator Diameter infrastructure ..... | 21 | +| A.4 | Void..... | 22 | +| Annex B (Normative): | Diameter routing extensions..... | 23 | +| B.0 | General ..... | 23 | +| B.1 | Realm-based routing ..... | 23 | +| B.2 | NAI decoration..... | 23 | +| B.3 | Explicit routing..... | 23 | +| B.4 | Preserving the User-Name AVP ..... | 23 | +| Annex C: | Change history..... | 24 | + +# --- 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 + +As a new generation AAA (Authentication, Authorization and Accounting) protocol, Diameter has been used widely and will be used more and more widely in 3GPP. Since several 3GPP WGs are developing Diameter based interfaces, e.g. CT3, CT4, etc, so in order to ensure correctness and consistency of using Diameter within all 3GPP WGs, a common set of principles, rules and recommendations across 3GPP WGs are necessary to be given clearly and followed. The present is to describe existing status of Diameter usage within 3GPP, find existing inconsistency of rules used for Diameter based interfaces which were specified in 3GPP and propose common recommendations of using Diameter to all 3GPP WGs to follow. + +With more and more Diameter deployment, an inter-operator Diameter signalling network infrastructure will become necessary, so the present document will also study Diameter inter-operator considerations with brief guidelines on how to deploy & realize the inter-operator Diameter-based roaming infrastructure. + +# --- 1 Scope + +The present document contains a common set of principles, rules and recommendations across 3GPP WGs to ensure Diameter-based interfaces have the same treatment for release control and generating new applications-id. Also to address in a unified manner the use/re-use of AVPs, and other Diameter BASE (see IETF RFC 3588 [x]) related decisions. + +The present document covers all aspects of Diameter usage within 3GPP, including description of the current situation of Diameter usage in different 3GPP WGs (CT3, CT4, SA5) in Release 6/7, describe recommendations and conditions to re-use existing Diameter applications (3GPP or IETF application-id), commands, AVPs and/or AVP values, describe recommendations and conditions to define new Diameter applications, commands, AVPs and/or AVP values, and any other related issues, e.g. the cross-release issue, whether to apply proposed guideline back to existing Diameter applications or not, or only new SAE Diameter interfaces, etc. + +To achieve maximum benefit from this work it is strongly recommended that all 3GPP Diameter-based protocols follow the recommendations in the present document. + +The present document also serves a placeholder for Diameter inter-operator considerations with brief guidelines on how to deploy & realize the inter-operator Diameter-based roaming infrastructure. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] IETF RFC 3588 (September 2003): "Diameter Base Protocol". +- [3] IETF RFC 4005 (August 2005): "Diameter Network Access Server Application". +- [4] IETF RFC 4006 (August 2005): "Diameter Credit-Control Application". +- [5] 3GPP TS 29.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3". +- [6] IETF RFC 4072 (August 2005): "Diameter Extensible Authentication Protocol (EAP) Application". +- [7] 3GPP TS 32.299: "Diameter charging applications ". +- [8] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details". +- [9] 3GPP TS 29.230: "Diameter applications; 3GPP specific codes and identifiers". +- [10] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)" +- [11] IETF Draft, "Diameter Base Protocol", draft-ietf-dime-rfc3588bis-08.txt, working in progress. +- [12] IETF Draft, "Diameter Applications Design Guidelines", draft-ietf-dime-app-design-guide-03.txt, working in progress. +- [13] GSMA PRD IR.34 v4.1, "Inter-Service Provider IP Backbone Guidelines" +- [14] GSMA PRD IR.67 v2.1.0, "DNS Guidelines for Operators" + +- [15] GSMA PRD IR.40 v4.0, "[Guidelines for IPv4 Addressing and AS Numbering for GPRS Network Infrastructure and Mobile Terminals](#)" +- [16] Void +- [17] 3GPP TS 23.003: "Numbering, addressing and identification; Stage 3" +- [18] IETF RFC 4282, "The Network Access Identifier" +- [19] 3GPP TS 24.234: "3GPP System to WLAN Interworking; UE to Network protocols; Stage 3" +- [20] IETF Draft, "Diameter User-Name and Realm Based Request Routing Clarifications", draft-korhonen-dime-nai-routing-02.txt, Work in progress. + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +(none) + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +(none) + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-----|-----------------------------------| +| SAE | System Architecture Evolution | +| SDO | Standard Development Organization | + +# --- 4 The status of Diameter in 3GPP + +## 4.1 General + +This subclause describes current status of Diameter usage before Release 8 and summarizes some problems of using Diameter protocol to satisfy 3GPP-specific requirements in the past. This subclause is a basis for further discussion to give proposed rules in subclause 5. + +## 4.2 Diameter-based applications before Release 8 + +Diameter Base Protocol (see IETF RFC 3588 [2]) provides a set of messages and parameters to support AAA-related functionality with built-in protocol management mechanism, e.g. peer discovery, message routing, error handling, etc. Based on Diameter Base Protocol, IETF also defines many Diameter applications to support more specific requirements in different scenarios, e.g. NASREQ (see IETF RFC 4284 [3]), Diameter Credit Control (see IETF RFC 4006 [4]), etc. Another important feature of Diameter Base Protocol [2] is that it also provides a set of principles and rules for extensibility to support more functionality in the future. That allows other SDOs like 3GPP to define more specific applications, messages, parameters (AVPs) and values to fulfil SDO-specific requirements. + +Because of powerful functions and good extensibility, since Release 5, Diameter has been used widely in 3GPP systems, e.g. IMS, GBA, Interworking WLAN, Charging systems, PCC, etc. + +The Diameter protocol is designed to be extensible, using several mechanisms, including defining new AVP values, creating new AVPs, creating new Diameter applications, in addition to reuse of existing AVP values, AVPs and Diameter applications (see IETF RFC 3588 [2] for more details). + +Based on different principles and requirements, 3GPP WGs, i.e. CT3, CT4 and SA5, develop their Diameter-based interfaces with different approach. Some interfaces are based on existing IETF-defined Diameter applications, for example Wa interface (see 3GPP TS 29.234 [5]) is based on Diameter base protocol (IETF RFC 3588 [2]), NASREQ (IETF RFC 4005 [3]) and Diameter EAP application (IETF RFC 4072 [6]). Some interfaces are based on existing IETF-defined Diameter applications with 3GPP-specific AVPs/Values, for example Ro interfaces (see 3GPP TS 32.299 [7]) is based on Diameter Credit-Control Application (IETF RFC 4006 [4]) with some new 3GPP-specific AVPs. And some interfaces are new 3GPP-specific Diameter applications, e.g. Cx interface specified in 3GPP TS 29.229 [8] which includes 3GPP-specific commands, AVP codes and results codes. 3GPP TS 29.230 [9] serves as a placeholder for all 3GPP-specific Diameter applications, commands, AVP codes and result codes. + +## 4.3 Problem description + +During developing Diameter based interfaces, some inconsistent rules are found about how to using Diameter protocol to satisfy 3GPP-specific requirements in different 3GPP WGs. This subclause describes some examples of this issue. + +Wx interface, between a 3GPP AAA Server and a HSS, is specified in 3GPP TS 29.234 [5] by CT4. A new application ID is allocated to it as some new AVPs with "M" bit set are added to existing commands, e.g. 3GPP-AAA-Server-Name AVP, WLAN-User-Data AVP, etc. + +Wm interface, between a PDG and a 3GPP AAA Server/Proxy, is specified in 3GPP TS 29.234 [5] by CT4. For example, the 3GPP-WLAN-APN-Id AVP, with "M" bit set (see table 10.1.1 in section 10.1, 3GPP TS 29.234 [5]), is a 3GPP-defined AVP and added to AAR command for authorization purpose, but no new application is applied for Wm interface. + +Gmb interface, between a GGSN and a BM-SC, is specified in 3GPP TS 29.061 [10] by CT3. A new application ID is allocated to it as some new AVPs with "M" bit set are added to existing commands, e.g. TMGI AVP, Required-MBMS-Bearer-Capabilities AVP, etc. + +So it is seen that cross CT WGs there are some inconsistent principles or rules of usage of application IDs and 3GPP-specific AVPs with "M" bit set. + +There is another 3GPP-specific issue when Diameter is used in 3GPP, i.e. so-called cross-release issue. New AVPs may be added to the same interface (Diameter Application) in different Releases. If all these AVPs are "M" bit set and added to the same Diameter Application (the same Application ID), inter-operability may occur when equipments following different releases are connected. For the issue, different principles are applied to different interfaces. + +One case is AVPs which are added to new release are "M" bit clear. For example, for Release 7 Wm interface, QoS-Auth-Resources AVP is added with "M" bit clear to avoid inter-operability problems. This is similar with Gmb interface. For Gmb interface, a new application ID is allocated to it in Release 6. In Release 7, no new application ID is applied with some new AVPs with "M" bit set, e.g. MBMS-User-Data-Mode-Indication AVP, MBMS-GGSN-Address AVP, etc. In this case the same Application-ID is kept cross releases. + +In other cases different application IDs are applied to different releases if there are different AVPs with "M" bit set. For Gx interface, different Application IDs are applied to Release 6 and Release 7 variants due to some new commands and AVPs. + +So it is seen that cross CT WGs there are some inconsistent principles or rules for cross-release Diameter applications. And no consensus about how to use "M" bit is reached in the past. + +Different principles or rules of Diameter usage across 3GPP WGs may lead to unexpected inter-operability problems as well as confuse developers. From protocol level, Diameter Base protocol has a set of error check and handling mechanism, that is useful to keep Diameter protocol and applications work correctly and consistently. However some cases above can not utilise these mechanisms, e.g. protocol level error check. + +Inconsistent usage of Diameter across WGs may also cause some difficulties for developing a common Diameter software platform to support different applications from development point of view. + +So it is necessary to have a common principles or rules of how to use Diameter within 3GPP WGs in CT/SA WGs to satisfy 3GPP-specific requirements, including: + +- Conditions to re-use existing Diameter applications, commands, AVPs and/or AVP values; + +- Conditions to define new Diameter applications, commands, AVPs and/or AVP values; +- The way to resolve cross-release issue; +- Whether to apply proposed guideline back to existing Diameter applications or not, or only new SAE Diameter interfaces and afterwards. +- Etc. + +## 4.4 Existing and ongoing effort + +3GPP tried to define some principles of Diameter usage in the past when Cx interface was developed (see subclause 7 of 3GPP TS 29.229 [8]). This can be one input to work of the present technical report. + +IETF is also aware of the current limitations of Diameter Base Protocol (see IETF RFC3588 [2]) and is working in a new version of Diameter based protocol (RFC 3588bis, IETF draft, draft-ietf-dime-rfc3588bis [11]). The DIME WG (Diameter Maintenance and Extensions) is working on Diameter application design guidelines [12]. The IETF draft discusses problems about Diameter application design, contradictions and ambiguity when Diameter applications were designed and some guidelines are proposed about reusing existing and/or defining new Diameter applications, commands, AVPs or AVP values. + +The outputs of the present TR is expected to be inputs to IETF-related work to work out more accurate guidelines of Diameter usage. 3GPP may also develop more detailed 3GPP-specific rules for Diameter usage based on the guidelines, rules and principles from IETF if needed. + +# --- 5 Proposed alternatives rules for identified problems + +## 5.1 General + +The alternative proposals given in this subclause takes several aspects into account: + +- Ongoing work on Diameter application design guidelines in IETF DIME WG [12]; +- Ongoing work on Diameter Base Protocol improvement – IETF RFC 3588bis [11]; +- Solutions provided in 3GPP R6/R7 to the listed Items about Diameter usage as described in subclause 4. +- New proposals different from the above + +In principle, when a proposal to address any of the listed Items is coming by IETF ongoing work it should be the preferred solution to be documented in the conclusion section 6. + +NOTE: Any identified problem will have a corresponding sub-clause, which will be introduced as an "Item". For each Item all possible solutions identified will be documented. Therefore clause 5 only contains the list of all alternatives and proposed solutions during the elaboration of the present TR. The final agreed recommendation for 3GPP are listed in clause 6. + +## 5.2 Item 1: Setting of "M" bit on 3GPP defined AVPs + +### 5.2.0 General + +This item is about how to set "M" bit in new 3GPP-defined AVPs. + +### 5.2.1 Proposal 1 (IETF) + +Follow IETF RFC 3588 procedures on the setting of the M-bit. The Diameter base RFC defines that M-bit shall be set only when it is required to be understood by the receiving peer Diameter node. A Diameter client, server, proxy or translation agent receiving such AVP shall behave according to clause 4.1 of IETF RFC 3588 [2]. + +NOTE: IETF does not preclude to define the M-bit in the "MAY use" column in the AVP definition. + +### 5.2.2 Proposal 2 + +"M" bit shall be set in all 3GPP-specific AVPs unless there are necessary reasons to clear the "M" bit in some new defined 3GPP-specific AVPs and it is guaranteed that this will not cause interoperability problems. + +NOTE: It is left to the application specification team to define in what kind of necessary reasons the "M" bit can be cleared in a 3GPP-specific AVP. + +### 5.2.3 3GPP evaluation + +"M" bit set means: "Support of this AVP is mandatory" (i.e. the entity which receives that AVP must be able to recognize it, parse it, have it defined in its own library of AVPs). "M" bit DOES NOT mean "the AVP is Mandatory in the command or Grouped AVP" (that a frequent mistake/misinterpretation). Adding an AVP to an application (at a command level or nested within a Grouped AVP) with the "M" bit set will create a backward compatibility problem. + +This is a generic DIAMETER Rule, 3GPP or any SDO is NOT ALLOWED to change this rule, unless this is discussed at the IETF first. + +## 5.3 Item 2: Re-use of AVPs + +### 5.3.1 General + +This item discusses how the already existing AVPs can be used in 3GPP applications. Three points are taken into account here: configuration of the M-bit and whether to use or not the original Vendor-Id and AVP code. + +### 5.3.2 Proposal 1 + +New or existing Diameter applications incorporate AVPs defined in different Diameter applications. In such a case, the re-used AVPs shall not be modified and shall be configured with the original Vendor-Id, AVP code and M-bit status. In order to support the re-used AVP, during capability negotiation the Supported-Vendor-Id shall be configured to include the vendor-id of the re-used AVPs. + +### 5.3.3 Proposal 2 (IETF) + +Vendor-Id and AVP code shall not be modified and shall be used as defined in the AVP's original document. Whether the "M" bit is set or not is based on actual requirements, e.g. support for end-to-end applications capabilities exchange in Diameter application design guidelines [12]. M-bit use is defined by application. + +The RFC 3588, Diameter Base Protocol, permits different 'M' bit settings for different situations. The 'M' bit setting is **not** tied to the AVP as such. The purpose of the 'M' bit is to ensure that the receiver must really understand the AVP. RFC 3588 also includes the possibility for the originator to resend the command with failing AVPs omitted if the receiver rejects any AVP with the M-bit set. + +### 5.3.4 3GPP evaluation + +Proposal 2 is recommended. + +Vendor-Id and AVP code shall not be modified and shall be the same as defined in the original AVP's Application specification. The 'M' bit setting is not tied to the AVP but can be defined on a per-application and per-command basis. + +For a re-used AVP, the "M" bit setting in the current application and command shall be considered the same as in the AVP's original specification document, as a default, if there is no specific specification for this shown in the re-used AVP table. For those re-used AVPs which have different "M" bit settings against the originally defined AVPs, a description shall be added in the re-used AVP table to specify the new "M" bit settings. + +## 5.4 Item 3: Version handling + +### 5.4.0 General + +This item evaluates the different proposals that 3GPP applications can take in order to use a 3GPP defined protocol (e.g. Gx or Cx protocols) in more than one release. In those cross-Release scenarios, a version handling mechanisms is normally needed. + +### 5.4.1 Proposal 1 + +Use a new application id for each release as a fixed rule. + +For cross-release Diameter applications, at most one new Diameter application id for each 3GPP release may be defined. + +### 5.4.2 Proposal 2 + +If one or more conditions listed in subclause 5.5.2 about the creation of new applications are true, a new application id shall be defined for an interface in a new release. All of the application identifiers allocated to different releases of the same interface shall be contained in the Vendor-Specific-Application-Id AVP in the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +### 5.4.3 Proposal 3 - IETF + +Follow IETF extensibility rules to assign a new Application Id. (See subclause 5.5.1) + +### 5.4.4 Proposal 4 + +A proposal that has been followed so far in CT4 based on the definition of a new AVP called Supported-Features AVP (see Cx and Sh applications, subclause 7.2 in 3GPP TS 29.229 [8]). This AVP is complementary to the CER/CEA process and avoids the definition of a new Application Id per release. This AVP was added with the M bit set to Release 6, without changing the Application Id for Cx or Sh, however the handling of the corresponding error (DIAMETER\_AVP\_UNSUPPORTED) is specified and does not cause interoperability issues. + +NOTE: IETF RFC3588 [2] and the current revised version in IETF DRAFT draft-ietf-dime-rfc3588bis [11] do not preclude this possibility. It is true that adding an AVP with the M bit set is indicated as one of the reasons that may lead to change the Diameter Application Id in this paragraph: *"Should a new Diameter usage scenario find itself unable to fit within an existing application without requiring major changes to the specification, it may be desirable to create a new Diameter application. Major changes to an application include: - Adding new AVPs to the command, which have the "M" bit set."*, but the change of application id is only indicated as something that "may be desirable". The first sentence in those two IETF specifications on the other hand indicates that: *"Creation of a new application should be viewed as a last resort."*, and a similar handling of new AVPs with the M bit set within a Diameter application is considered later in the same documents: *"If a message is rejected because it contains a Mandatory AVP which is neither defined in the base Diameter standard nor in any of the Diameter Application specifications governing the message in which it appears, the implementation may resend the message without the AVP, possibly inserting additional standard AVPs instead."* + +### 5.4.5 Proposal 5 + +#### 5.4.5.1 General + +The AVP use in this proposal extends ideas from the CT4's current handling. It introduces a new Supported – Application-Variant AVP to be negotiated during the Diameter peer connection establishment procedure. The Supported-Application-Variant AVP can only be used for optional extra Releases; new mandatory features will have to be supported with an Application ID upgrade. + +The following proposal solves the issue of identifying Application-Ids and releases supported on a hop-by-hop basis as CER/CEA is negotiated with the next hop. Therefore end-to-end negotiation is not covered by this proposal. + +New functionality, i.e., functionality beyond the Rel-7 standard, shall be introduced by post-Rel-7 versions of this specification to the Diameter applications as follows: + +- 1) If possible, the new functionality shall be defined optional. +- 2) If backwards incompatible changes can not be avoided, the new functionality should be introduced as with a new Supported-Application-Variant AVP. +- 3) If the change would be backwards incompatible, even as if it was defined as a feature, a new version of the interface shall be created by changing the application identifier of the Diameter application per release. + +#### 5.4.5.2 Defining new functionality + +##### 5.4.5.2.1 General + +An application will agree to a base functionality at a Standard level and a release extension will be an extension to that functionality. A new feature is a functional entity that has a significant meaning to the operation of a Diameter application, i.e., defining new optional capabilities. A new Supported-ApplicationVariant AVP will be defined for each version post the frozen versions of the specification. + +##### 5.4.5.2.2 Changing the version of the interface + +The version of an interface shall be changed by a future release of this specification only if there is no technically feasible means to avoid backwards incompatible changes to the current release of the interface. The versioning of an interface shall be implemented by assigning a new application identifier for the interface. This procedure is in line with the Diameter base protocol (see IETF RFC 3588) which states that if an incompatible change is made to a Diameter application, a new application identifier shall be assigned for the Diameter application. + +The following table shall apply to the PCC interfaces. The Application identifier column lists the current application identifiers assigned on 3GPP PCC. + +**Table 5.2.2.1: Application identifiers used** + +| PCC Interface | Application identifier | First applied | +|---------------|------------------------|---------------| +| Rx | 16777236 | 3GPP Rel-7 | +| Gx | 16777238 | 3GPP Rel-7 | + +##### 5.4.5.2.3 Capabilities Exchange Request + +Message Format + +``` + ::= < Diameter Header : 257, REQ > + { Origin-Host } + { Origin-Realm } + 1* { Host-IP-Address } + { Vendor-Id } + { Product-Name } + [ Origin-State-Id ] + * [ Supported-Vendor-Id ] + * [ Supported-Application-Variant ] + * [ Vendor-Specific-Application-Variant ] + * [ Auth-Application-Id ] + * [ Inband-Security-Id ] + * [ Acct-Application-Id ] + * [ Vendor-Specific-Application-Id ] + [ Firmware-Revision ] + * [ AVP ] +``` + +##### 5.4.5.2.4 Capabilities Exchange Answer + +Message Format + +``` + ::= < Diameter Header: 257 > + { Result-Code } + { Origin-Host } + { Origin-Realm } + 1* { Host-IP-Address } + { Vendor-Id } + { Product-Name } + [ Origin-State-Id ] + [ Error-Message ] + * [ Failed-AVP ] + * [ Supported-Vendor-Id ] + * [ Supported-Application-Variant ] + * [ Vendor-Specific-Application-Variant ] + * [ Auth-Application-Id ] +``` + +``` + +* [ Inband-Security-Id ] +* [ Acct-Application-Id ] +* [ Vendor-Specific-Application-Id ] +[ Firmware-Revision ] +* [ AVP ] + +``` + +##### 5.4.5.2.5 AVPs + +**Table 5.2.5.1.1: Diameter Application AVPs** + +| Attribute Name | AVP Code | Section defined | Value Type | AVP Flag rules | | | | | +|--------------------------------------------|------------|-----------------|-------------------|----------------|-----|------------|----------|-----------| +| | | | | Must | May | Should not | Must not | May Encr. | +| Supported-Application-Variant | XXX | 5.4.5 | Unsigned32 | V | | | M | No | +| Vendor-Specific-Application-Variant | XXX | 5.4.5 | Grouped | V | | | M | No | + +###### 5.4.5.2.5.1 Supported-Application-Variant AVP + +The Vendor-ID header of the AVPs defined in this specification shall be set to 3GPP (10415). + +The Supported-Application-Variant AVP is of type Unsigned32. If this AVP is present it may inform the destination host about the releases that the origin host supports. + +Where a Supported-Application-Variant AVP is used to identify variant that have been defined by 3GPP, the Vendor-Id AVP shall contain the vendor ID of 3GPP. Vendors may define proprietary variant, but it is strongly recommended that the possibility is used only as the last resort. Where the Supported-Application-Variant AVP is used to identify variant that have been defined by a vendor other than 3GPP, it shall contain the vendor ID of the specific vendor in question. + +Following values are defined: + +- Rx interface –R8 (0) +- Gxa interface – R8 (1) +- Gxb interface – R8 (2) +- Gxc interface – R8 (3) + +###### 5.4.5.2.5.2 Vendor-Specific-Application-Variant AVP + +The Vendor-Specific-Application-Variant is of type Grouped. This AVP provides a list of features supported on a per vendor basis allowing for the vendors to define vendor specific features. + +Vendor-Specific-Application-Variant::= Grouped + +[ Vendor ID ] + +1 \*[ Supported-Application-Variant] + +### 5.4.6 3GPP evaluation + +The decision to change or not change Diameter application id in each release or even within the same release should be left for the 3GPP WG defining the application. Diameter protocol requirements in the corresponding IETF RFCs shall be followed when taking this decisions and IETF guidance in the corresponding IETF RFCs should be considered as well. + +There are two aspects of version handling covered in the proposals to address this item: + +- Hop-by-hop version handling: Communicating the supported version to a directly connected Diameter peer at connection time in a CER/CEA exchange. + +- End-to-end version handling: Communicating the supported version to a Diameter peer through one or more Diameter agents during an application message exchange. + +Proposals 1, 2, 3 and 5 address hop-by-hop version handling and proposal 4 addresses end-to-end version handling. + +With respect to hop-by-hop version handling: + +- Proposal 1 is discarded, since it creates an unnecessary restriction for new applications and releases. +- Proposal 2 creates unnecessary restriction for new application and releases which shall not be considered as strict requirements for the definition of new applications but left to application specification team to evaluate on different situations. However, the part about including all supported applications in the CER/CEA exchanged in proposal 2 shall be followed. +- Proposal 3 is recommended to be considered as guidelines which provide more flexibility and it is left to the application specification team to evaluate the need of defining new Application Id or creating alternative means to avoid interoperability problems when changes are performed across 3GPP Releases. +- Proposal 5 is useful for application version negotiation on a hop by hop basis in the CER/CEA message exchange. + +With respect to end-to-end version handling: + +- Proposal 4 is also highly recommended for ease of extensibility of a Diameter Application. Note that the Supported-Feature AVP should be included into every new application where a need for end-to-end version handling has been identified. This method avoids continual updating of the application ID from 3GPP Release to Release. However its drawback is that the features supported are only discovered on the first command pair exchange and not at connection time during the CER/CEA exchange. + +## 5.5 Item 4: Setting of a new Application-Id + +## 5.5.0 General + +This item covers the conditions under which a new application-id shall be assigned to an existing protocol. + +### 5.5.1 Proposal 1 - IETF + +Follow IETF RFC 3588 guidelines on defining new application id. + +According to the IETF draft in [11] defining a new Application Id MAY be desirable when : + +- Adding new AVPs to the command which have the "M" bit set +- Requiring a command that has a different number of round trips to satisfy the request +- Adding support for an authentication method requiring definition of new AVPs for use with the application + +Additionally a new Application Id MUST be created when + +- New commands are added to an existing application + +The related excerpts from [11] follow for further reference: + +- a) Excerpt from section 1.2.4. + +Every Diameter application specification MUST have an IANA assigned Application Id (see Section 2.4 and Section 11.3). Should a new Diameter usage scenario find itself unable to fit within an existing application without requiring major changes to the specification, it **may be desirable** to create a new Diameter application. Major changes to an application include: + +- o Adding new AVPs to the command, which have the "M" bit set. +- o Requiring a command that has a different number of round trips to satisfy a request (e.g., application foo has a command that requires one round trip, but new application bar has a command that requires two round trips to complete). + +- o Adding support for an authentication method requiring definition of new AVPs for use with the application. Since a new EAP authentication method can be supported within Diameter without requiring new AVPs, addition of EAP methods does not require the creation of a new authentication application. + +Creation of a new application should be viewed as a last resort. An implementation MAY add arbitrary non-mandatory AVPs to a command defined in an application, including vendor-specific AVPs without needing to define a new application. This can be done if the commands ABNF allows for it. Please refer to Section 11.1.1 for details. + +- b) Excerpt from section 1.2.3. + +A new command should only be created when no suitable command can be reused from an existing application. A new command MUST result in the definition of a new application. + +### 5.5.2 Proposal 2 + +A new Application-Id shall be defined when one or more of the conditions below are true: + +- New AVPs with "M" bit set are defined in a Diameter application; +- New commands are used; +- Existing AVPs are re-used with "M" bit set in a Diameter application; +- New values are added to an existing AVP with "M" bit set in a Diameter application; + +NOTE: It is left to the application specification team to define that in the case of no confusion or inter-operability problems caused, whether creation of a new application identifier can be avoided when one or more conditions above are true. + +### 5.5.3 Proposal 3 + +This proposal mandates the change of the application id whenever any of the bullets in Proposal 1 (IETF one) are fulfilled. I.e. a new Application Id SHALL be created when one or more of the following conditions occur: + +- Adding new AVPs to the command which have the "M" bit set +- Requiring a command that has a different number of round trips to satisfy the request +- Adding support for an authentication method requiring definition of new AVPs for use with the application +- New commands are added to an existing application + +### 5.5.4 3GPP evaluation + +The decision to change or not change Diameter application id in each release or even within the same release should be left for the 3GPP WG defining the application. Diameter protocol requirements in the corresponding IETF RFCs shall be followed when taking this decisions and IETF guidance in the corresponding IETF RFCs should be considered as well. + +Proposal 1 shows some cases where new Application Id might be desirable and just put the requirement to change the Application Id whenever new commands are needed. + +Proposal 2 is stricter and additionally requires a change of application whenever any change is made that implies anything with the "M" bit set + +Proposal 3 is the "stricter edition" of proposal 1 which shows all cases appeared in proposal 1 and requires changing of Application-Id whenever one or more of those cases happen. + +Proposal 1 is preferred and it is left to the application specification team to evaluate the need of defining new Application Id or creating alternative means to avoid interoperability problems when these changes are performed across 3GPP Releases. Additionally cases shown in proposal 2 but not mentioned in proposal 1 should be considered as conditions that new Application-Id might be desirable as well. + +NOTE: Hop by hop version negotiation needs further study. There are ongoing discussions in DIME group on this subject. + +## 5.6 Item 5: New Values to an existing enumerated AVP + +### 5.6.1 Proposal 1 + +Adding new values to an existing AVP with "M" bit set shall lead to creation of a new application identifier. + +### 5.6.2 Proposal 2 + +If a Diameter peer receives a supported enumerated AVP with some values unknown, the Diameter peer could ignore these unknown values. If the "M" bit is set for the AVP, this might be to indicate that some existing values need to be understood. If some new values are added, a new application identifier is only required if all receivers shall understand them. . + +### 5.6.3 Proposal 3 + +If a Diameter peer receives a supported enumerated AVP with some values unknown, the Diameter peer could ignore these unknown values. If the "M" bit is set for the AVP, this might be to indicate that some existing values need to be understood. A new application identifier and new AVP code are required only if all receivers shall understand the values that are added. + +### 5.6.4 Proposal 4 + +New values can be added to an existing AVP that is defined with the M-bit set to "MUST" in earlier releases without having to change the application Id. + +If a Diameter node supporting a specific application receives an AVP with the M-bit set with a value that it cannot recognize, the receiving node shall reject the command since it cannot understand a mandatory-to-understand AVP. Moreover the specification where this AVP is used with the new value(s) shall specify the behaviour for the originator when this situation occurs, e.g. by specifying that the originator shall issue the command again but according to an earlier release of the application. + +NOTE: It is left to the application specification team to define What happens when the AVP is received in the answer instead of the request. However, in that case the receiver shall find a way to inform the sender. + +### 5.6.5 Proposal 5 + +If a new value is added to an AVP such that it changes the semantics of the application using it, the application specification team shall increase the application version using the appropriate version handling procedure described in section 5.4.6 (Item 3: Version Handling). For example, a new AVP value can be considered to have changed the semantics if the application specification has normative statements that refer to the new value. + +### 5.6.6 3GPP evaluation + +The RFC 3588, Diameter Base Protocol, does not preclude adding new enumerated values to be defined for an AVP that has the "M" bit set if it is justified in certain specific situations (see e.g. Data-Reference AVP in 3GPP TS 29.328). + +Proposal 1 and proposal 2 are discarded, since proposal 1 creates an unnecessary restriction for adding new values to an existing AVP with "M" bit set and proposal 2 is covered by proposal 3 + +Proposal 3 and proposal 4 document the preferred methods for how the receiving node deals with the unknown values in the AVPs with "M" bit set and flexibility is left to the protocol specification team to evaluate these. Proposal 3 is a restricted proposal and proposal 4 is more flexible but needs more handling at application level to specify the behaviours in the case of unknown values. + +Proposal 5 is the recommended method for evaluating the impact of the new AVP value on the application version. + +## 5.7 Item 6: Re-use of commands in new applications + +### 5.7.0 General + +This item is to discuss how to use the application identifier AVPs (Auth-Application-Id AVP, Vendor-Specific-Application-Id AVP, Acct-Application-Id AVP) in commands from pre-existing applications that are re-used in new 3GPP-specific applications. + +### 5.7.1 Proposal 1 + +When a new 3GPP specific application has been allocated with a new application id and it also reuses existing commands with or without modifications, it shall use the newly allocated application id in the message header and in all relevant application id AVPs (Auth-Application-Id, Acct-Application-Id or Vendor-Specific-Application-Id AVP) present in the message body of the re-used command. + +### 5.7.2 3GPP evaluation + +Proposal 1 is recommended. + +# --- 6 Conclusion + +This TR has studied alternative solutions for some inconsistent rules used by different 3GPP WGs during development of Diameter based interfaces and has proposed a common set of principles, rules and recommendations across 3GPP WGs to ensure Diameter-based interfaces have the similar treatment for release control and generation of new application Ids. It also addresses common ways for the use/reuse of AVPs and other Diameter BASE related decisions. + +The setting of the 'M' bit in new 3GPP-defined AVPs shall follow the generic Diameter Rule described in the 3GPP evaluation (see clause 5.2.3). + +Three points are taken into account on how to reuse the existing AVPs in 3GPP applications for the configuration of the M-bit and whether to use or not, the original Vendor-Id and AVP code. The IETF proposal is adopted that Vendor-Id and AVP code shall not be modified and shall be the same as defined in the AVP's Application specification. The 'M' bit setting is not tied to the AVP but can be defined on a per-application and per-command basis (see clause 5.3.4). + +For the version handling issue, the decision to change or not to change Diameter application id in each release or even within the same release is finally agreed to be left for the 3GPP WGs, defining the application, in order to be flexible. However, to ensure the decisions made by different 3GPP WGs are consistent, Diameter protocol requirements and IETF guidance in the corresponding IETF RFCs shall be followed when making these decisions. (Details see clause 5.4.6). + +The consideration of conditions under which a new Application Id shall be assigned to an existing protocol provides an agreement to follow the mechanism that IETF uses (see clause 5.5.1). + +For the item of New Values being applied to an existing enumerated AVP, The IETF does not preclude adding new enumerated values for an AVP that has the 'M' bit set. Hence, proposals are made on how the Diameter nodes should deal with the unknown value in a received pre-existing enumerated AVP with 'M' bit set. The recommendation is made by balancing flexibility and inter-operability (see clause 5.6.6). + +For re-use of commands in new applications, it is agreed to use the newly allocated Application-Id in the message header and all the relevant Application-Id AVPs present in the message body of the re-used command no matter if the command is re-used, with or without modification. + +To achieve maximum benefit from this work, this report recommends all 3GPP Diameter-based protocols to apply the evaluated guidelines for new Diameter interfaces and future releases. It also serves as a placeholder for Diameter multi-vendor considerations with brief guidelines on how to deploy and realize the inter-operator Diameter-based roaming infrastructure. + +# Annex A (Informative): Roaming Infrastructure + +## A.0 General + +The subclause proposes brief guidelines on how to deploy & realize the inter-operator Diameter-based roaming infrastructure. + +## A.1 Deployment of S6a-Diameter Relay Pools + +This annex provides an example of a deployment of S6a-Diameter relay pools to be used between a visited and home operator. This deployment may also be applied to the intra-operator scenario as well. + +At a high level, the Diameter infrastructure needed for a multi-operator scenario comprises the intra-operator infrastructure of each involved network operator, and an inter-operator infrastructure shared by the involved network operators. The inter-operator infrastructure could be the evolution of the existing GPRS Roaming Exchange i.e. the IPX [13]. This is depicted below. + +![Diagram of High-level Diameter Infrastructure showing four network operators (A, B, C, D) connected to a central Inter-Operator Diameter Infrastructure.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +``` +graph TD; A((Network Operator A +Intra-Operator +Diameter +Infrastructure)) --- I((Inter-Operator Diameter +Infrastructure)); B((Network Operator B +Intra-Operator +Diameter +Infrastructure)) --- I; C((Network Operator C +Intra-Operator +Diameter +Infrastructure)) --- I; D((Network Operator D +Intra-Operator +Diameter +Infrastructure)) --- I; +``` + +The diagram illustrates a central light blue oval labeled 'Inter-Operator Diameter Infrastructure'. Four colored circles are connected to this central node: 'Network Operator A Intra-Operator Diameter Infrastructure' (orange, top-left), 'Network Operator C Intra-Operator Diameter Infrastructure' (purple, top-right), 'Network Operator B Intra-Operator Diameter Infrastructure' (green, bottom-left), and 'Network Operator D Intra-Operator Diameter Infrastructure' (yellow, bottom-right). Each operator's infrastructure is connected to the central inter-operator infrastructure via a single line. + +Diagram of High-level Diameter Infrastructure showing four network operators (A, B, C, D) connected to a central Inter-Operator Diameter Infrastructure. + +**Figure A.1.1: High-level Diameter Infrastructure** + +For the intra-operator infrastructure it is suggested to make use of: + +- An inner pool of relay agents to provide service within the operator network: The inner pool of relay agents has Diameter connections to HSS. A plain pool where each relay has a connection to HSS is possible. Alternatively, a hierarchical pool is also possible, with a first level of relays that have connections to the MMEs and a second level of relays with connection to HSS, where each relay in the second level groups connections from the first level relays, so that the number of connections to HSS can be reduced. The inner pool of relay agents has Diameter connections to a border pool of relay agents. +- A border pool of relay agents to interface with the inter-operator Diameter infrastructure: The border pool of relay agents has Diameter connections to an inner pool of relay agents. The border pool of relay agents has Diameter connections to the inter-operator Diameter infrastructure. + +This is exemplified in the following figure A.1.2. + +![Diagram of Intra-Operator Diameter Infrastructure and its connectivity to inter-operator Diameter roaming infrastructure.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` +graph TD; HSS[HSS] --- IDRP[Inner Diameter Relay Pool]; IDRP --- BDRP[Border Diameter Relay Pool]; BDRP --- IOI((Inter-Operator Diameter Infrastructure)); IDRP --- MME1[MME]; IDRP --- MME2[MME]; IDRP -.-> MME3[MME]; +``` + +The diagram illustrates the connectivity of an intra-operator diameter infrastructure. At the top, an HSS (Home Subscriber Server) is connected to an Inner Diameter Relay Pool. This pool is connected to a Border Diameter Relay Pool, which in turn is connected to the Inter-Operator Diameter Infrastructure. Below the Inner Diameter Relay Pool, three MME (Mobility Management Entity) units are shown, with the first two connected directly and the third indicated by an ellipsis, showing multiple MMEs connected to the inner relay pool. + +Diagram of Intra-Operator Diameter Infrastructure and its connectivity to inter-operator Diameter roaming infrastructure. + +**Figure A.1.2: Example Intra-Operator Diameter Infrastructure and its connectivity to inter-operator Diameter roaming infrastructure** + +Observe that several variations over the example presented here are possible. For example, the functions of the inner and the border pools of relay agents could be combined in a single pool, or different relay pools could be used for separate geographical areas. + +For the inter-operator infrastructure it is proposed to use a hierarchical deployment of relay pools, so that: + +- First level relay pools have Diameter connections to the different intra-operator infrastructures. Each first level relay pool provides service to a number of intra-operator infrastructures, e.g. based on geographical location. +- Each intra-operator infrastructure obtains service from at least one relay pool, and at least two separate relay agents. +- Groups of interconnected first level relay pools are possible. +- When a first level relay pool receives a request: + - If the destination realm corresponds to a network operator for which the pool has a Diameter connection, then the request can be directly forwarded to the corresponding intra-operator infrastructure. + - If not, then if the destination realm corresponds to a network operator for which an interconnected first level relay pool has a Diameter connection, the request can be forwarded to that interconnected first level relay pool. + - Otherwise, the request is forwarded to a higher order relay pool. +- As many hierarchical levels as needed are possible. +- Similar principles to the ones described above are applied at all levels of the hierarchy, in order to find the optimum route to the destination intra-operator infrastructure. + +This is exemplified in the following figure A.1.3. + +![Figure A.1.3: Example Inter-Operator Diameter Infrastructure for S6a, S9 and Wd* interfaces. The diagram shows multiple Network Operators (A, B, C, D, ..., Z) connected to their respective 1st Level Diameter Relay Pools. These pools are then connected to a single 2nd Level Diameter Relay Pool. A bracket on the left labeled 'Intra-Operator Diameter Infrastructures' groups the operators and their first-level pools.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Figure A.1.3: Example Inter-Operator Diameter Infrastructure for S6a, S9 and Wd\* interfaces. The diagram shows multiple Network Operators (A, B, C, D, ..., Z) connected to their respective 1st Level Diameter Relay Pools. These pools are then connected to a single 2nd Level Diameter Relay Pool. A bracket on the left labeled 'Intra-Operator Diameter Infrastructures' groups the operators and their first-level pools. + +Figure A.1.3: Example Inter-Operator Diameter Infrastructure for S6a, S9 and Wd\* interfaces + +## A.2 Deployment of S9 and Wd\*-Diameter Relay Pools + +This annex provides a short description of a deployment of S9 and Wd\*-Diameter relay pools to be used between a visited and home operator. S9 (for PCC) and Wd\* (for I-WLAN) interfaces can reuse the Diameter infrastructure deployed for S6a purposes. + +S9 and Wd\* Diameter usage differs from S6a usage only on two aspects. First both S9 and Wd\* Diameter interfaces are only used for inter-operator roaming purposes. Second within the operator internal Diameter infrastructure peer nodes are different than the HSS. In case of S9 Diameter infrastructure connects to a PCRF and in case of Wd\* to a 3GPP AAA Server/Proxy. However, the Diameter infrastructure needed for S9 and Wd\* intra- and especially inter-operator purposes can be exactly the same than described in sub-clause A.1 for S6a. An example deployment is shown below. + +![Figure A.2.1: Example of PCRF and AAA Server/Proxy connecting to inter-operator Diameter roaming infrastructure. The diagram shows a PCRF and an AAA Server/Proxy connected to an Inner Diameter Relay Pool. This pool is connected to a Border Diameter Relay Pool, which in turn connects to the Inter-Operator Diameter Infrastructure.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Figure A.2.1: Example of PCRF and AAA Server/Proxy connecting to inter-operator Diameter roaming infrastructure. The diagram shows a PCRF and an AAA Server/Proxy connected to an Inner Diameter Relay Pool. This pool is connected to a Border Diameter Relay Pool, which in turn connects to the Inter-Operator Diameter Infrastructure. + +Figure A.2.1: Example of PCRF and AAA Server/Proxy connecting to inter-operator Diameter roaming infrastructure + +## A.3 Guidelines for connecting to the inter-operator Diameter infrastructure + +This annex provides guidelines on connecting operator's internal Diameter infrastructure to the inter-operator Diameter infrastructure. + +Past work on Diameter and various identities in 3GPP assume that the inter-operator IP backbone for roaming is the evolution of GPRS Roaming Exchange i.e. the IPX [3]. When connecting to the inter-operator IP backbone the rules defined in IR.34 [13], IR.67 [14] and IR.40 [15] shall be followed. From Diameter point of view this concerns addressing of the border relay agents and DNS naming of Diameter agents. + +## A.4 Void + +# --- Annex B (Normative): Diameter routing extensions + +## B.0 General + +This sub-clause gives additional guidance to the Diameter Base Protocol [11] on the Diameter request routing. + +## B.1 Realm-based routing + +The use of the Destination-realm AVP is specified in RFC 3588 as the valid realm the message is to be routed to. The realm field is used as primary key in lookups in the realm-based routing table. Diameter peers shall make use of the realm field in order to route Diameter requests. A Diameter peer obtains the valid realm to send requests to from the realm field in the User-Name AVP if this is a NAI. + +## B.2 NAI decoration + +The User-Name AVP in a Diameter request message may contain a decorated NAI. The NAI decoration mechanism is defined in IETF RFC 4282 [18], further clarified in IETF Draft draft-korhonen-dime-nai-routing [20] and in 3GPP scope defined in 3GPP TS 23.003 [17]. All Diameter agents that participate in the message request routing should support decorated NAIs in the User-Name AVP and modifications to the Destination-Realm AVP as described in IETF Draft draft-korhonen-dime-nai-routing [20]. However, the decorated NAI routing mechanism may be overruled by local configuration/policy. + +## B.3 Explicit routing + +If the network architecture requires a deployment of stateful Diameter agents, then the actual network deployment shall ensure that all Diameter messages belonging to the same user session traverse through the same stateful agents. Such explicit routing requirement may, for example, be satisfied by a network configuration. + +### B.4 Preserving the User-Name AVP + +It is strongly recommended that the User-Name AVP is present in every request message for 3GPP applications, for example, due to possible request routing related reasons as described in sub-clauses B.1 and B.2. Unless there is a strong reason otherwise, for example, due to identity hiding, the User-Name AVP should also be used as the primary information element for the subscriber look-ups by the Diameter agents. + +In specific cases, Diameter agents perform subscriber look-ups based on AVPs other than the User-Name AVP, such as the Subscription-Id AVP for instance. However in these scenarios it may be desirable to keep the User-Name AVP when the request is likely to traverse basic Diameter agents that make realm-based routing decisions based on User-Name AVP. + +# Annex C: Change history + +| Change history | | | | | | | | | | +|----------------|--------|-----------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | | | Old | New | +| 2007-09 | | | | | The initial draft v0.0.0 | | | | 0.0.0 | +| 2007-10 | | | | | Contents of subclause introduction, 1, 2, 3, and 4 are incorporated based on e-mail discussion. | | | 0.0.0 | 0.1.0 | +| 2007-11 | | | | | The approved tdoc C3-070963, C3-071001, C3-071159 at CT3 #46 are incorporated into v0.1.0. | | | 0.1.0 | 0.2.0 | +| 2008-01 | | | | | The approved tdoc C3-080167, C3-080215, C3-080216 at CT3 #47 are incorporated into v0.2.0. | | | 0.2.0 | 1.0.0 | +| 2008-04 | | | | | The approved tdoc C3-080390, C3-080394, C3-080400, C3-080401, C3-080402, C3-080456, C3-080457 at CT3 #47bis are incorporated into v1.0.0. | | | 1.0.0 | 1.1.0 | +| 2008-05 | | | | | The approved tdoc C3-080829 at CT3#48 are incorporated into v1.1.0 | | | 1.1.0 | 1.2.0 | +| 2008-06 | | | | | The approved tdoc C3-081189(C4-081971), C3-081190(C4-081972), C3-081191(C4-081993), C3-081243(C4-081970) at CT#48bis are incorporated into v1.2.0 | | | 1.2.0 | 1.3.0 | +| 2008-08 | | | | | The agreed tdoc C3-081325, C3-081552 at CT3#49 are incorporated into v1.3.0 | | | 1.3.0 | 1.4.0 | +| 2008-09 | | | | | Version 2.0.0 created for presentation to TSG by MCC | | | 1.4.0 | 2.0.0 | +| 2008-09 | TSG#41 | | | | Version 8.0.0 created by MCC | | | 2.0.0 | 8.0.0 | +| 2008-12 | TSG#42 | CP-080755 | 001 | 2 | Clean up of TR 29.909 | | | 8.0.0 | 8.1.0 | +| 2008-12 | TSG#42 | CP-080755 | 002 | 1 | Routing and preserving the User-Name | | | 8.0.0 | 8.1.0 | +| 2008-12 | TSG#42 | CP-080755 | 003 | | Principle for the "M" bit setting in re-used AVP tables | | | 8.0.0 | 8.1.0 | +| 2009-01 | | | | | Version 8.1.1 created by MCC due to editorial correction | | | 8.1.0 | 8.1.1 | +| 2009-01 | | | | | Minor cosmetic corrections | | | 8.1.1 | 8.1.2 | +| 2009-12 | TSG#46 | | | | Automatic upgrade from previous Release | | | 8.1.2 | 9.0.0 | +| 2011-03 | TSG#51 | | | | Automatic upgrade from previous Release version 9.0.0 | | | 9.0.0 | 10.0.0 | +| 2011-03 | TSG#51 | | | | Correction of heading and numbering made by MCC | | | 10.0.0 | 10.0.1 | +| 2012-09 | TSG#57 | | | | Automatic upgrade from previous Release version 10.0.1 | | | 10.0.1 | 11.0.0 | +| 2014-10 | | | | | Automatic upgrade from previous Release | | | 11.0.0 | 12.0.0 | +| 2015-12 | | | | | Automatic upgrade from previous Release | | | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | | New | | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | | 14.0.0 | | +| 2018-06 | SA#80 | - | - | - | | Automatic upgrade from previous Release | | 15.0.0 | | +| 2020-07 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35201/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/35_series/35201/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..695ff98a978c38159088e9fc904aa52cdefa3729 --- /dev/null +++ b/marked/Rel-16/35_series/35201/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4df72abf2f933458fb5ebf9091f0203f27c2adf7085dcab0fcd899e1053c87b5 +size 63264 diff --git a/marked/Rel-16/35_series/35201/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/35_series/35201/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ba237b1c67ea4205ec425aa31d7d108a4943186 --- /dev/null +++ b/marked/Rel-16/35_series/35201/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f34b5a20213a6e7e94ecbb4d558710a8cf11f35779462fdb17ccd2d793744d44 +size 63295 diff --git a/marked/Rel-16/35_series/35201/raw.md b/marked/Rel-16/35_series/35201/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3bb5144320c8038eb484f615bcf5e9e69e43b5a2 --- /dev/null +++ b/marked/Rel-16/35_series/35201/raw.md @@ -0,0 +1,708 @@ + + + + + + +# --- Contents + +| | | +|--------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 0 Scope..... | 6 | +| NORMATIVE SECTION ..... | 7 | +| 1 Outline of the normative part..... | 8 | +| 1.1 References ..... | 8 | +| 2 Introductory information..... | 9 | +| 2.1 Introduction ..... | 9 | +| 2.2 Notation..... | 9 | +| 2.2.1 Radix..... | 9 | +| 2.2.2 Conventions..... | 9 | +| 2.2.3 Bit/Byte ordering..... | 9 | +| 2.2.4 List of Symbols..... | 10 | +| 2.3 List of Variables ..... | 10 | +| 3 Confidentiality algorithm f8 ..... | 11 | +| 3.1 Introduction ..... | 11 | +| 3.2 Inputs and Outputs ..... | 11 | +| 3.3 Components and Architecture..... | 11 | +| 3.4 Initialisation..... | 11 | +| 3.5 Keystream Generation..... | 12 | +| 3.6 Encryption/Decryption ..... | 12 | +| 4 Integrity algorithm f9 ..... | 12 | +| 4.1 Introduction ..... | 12 | +| 4.2 Inputs and Outputs ..... | 12 | +| 4.3 Components and Architecture..... | 13 | +| 4.4 Initialisation..... | 13 | +| 4.5 Calculation ..... | 13 | +| INFORMATIVE SECTION ..... | 15 | +| Annex 1 (informative): Figures of the f8 and f9 Algorithms..... | 16 | +| Annex 2 (informative): Simulation Program Listing..... | 18 | +| Annex 3 (informative): Change history..... | 22 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The 3GPP Confidentiality and Integrity Algorithms f8 & f9 have been developed through the collaborative efforts of the European Telecommunications Standards Institute (ETSI), the Association of Radio Industries and Businesses (ARIB), the Telecommunications Technology Association (TTA), the T1 Committee. + +The f8 & f9 Algorithms Specifications may be used only for the development and operation of 3G Mobile Communications and services. Every Beneficiary must sign a Restricted Usage Undertaking with the Custodian and demonstrate that he fulfills the approval criteria specified in the Restricted Usage Undertaking. + +Furthermore, Mitsubishi Electric Corporation holds essential patents on the Algorithms. The Beneficiary must get a separate IPR License Agreement from Mitsubishi Electronic Corporation Japan. + +For details of licensing procedures, contact ETSI, ARIB, TTA or T1. + +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 + +This specification has been prepared by the 3GPP Task Force, and gives a detailed specification of the 3GPP confidentiality algorithm *f8*, and the 3GPP integrity algorithm *f9*. + +This document is the first of four, which between them form the entire specification of the 3GPP Confidentiality and Integrity Algorithms: + +- **3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: *f8* and *f9* Specification".** +- **3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification".** +- **3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data".** +- **3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data".** + +The normative part of the specification of the *f8* (confidentiality) and *f9* (integrity) algorithms is in the main body of this document. The annexes to this document are purely informative. Annex 1 contains illustrations of functional + +elements of the algorithm, while Annex 2 contains an implementation program listing of the cryptographic algorithm specified in the main body of this document, written in the programming language C. + +The normative part of the specification of the block cipher (**KASUMI**) on which they are based is in the main body of Document 2. The annexes of that document, and Documents 3 and 4 above, are purely informative. + +## --- 0 Scope + +This specification gives a detailed specification of the 3GPP confidentiality algorithm *f8*, and the 3GPP integrity algorithm *f9*. + +# --- NORMATIVE SECTION + +This part of the document contains the normative specification of the Confidentiality and Integrity algorithms. + +## --- 1 Outline of the normative part + +Section 1 introduces the algorithms and describes the notation used in the subsequent sections. + +Section 3 specifies the confidentiality algorithm *f8*. + +Section 4 specifies the integrity algorithm *f9*. + +### 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] 3GPP TS 33.102 version 3.2.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 version 3.1.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 Specification". +- [4] 3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification". +- [5] 3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data". +- [6] 3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data". +- [7] ISO/IEC 9797-1:1999: "Information technology – Security techniques – Message Authentication Codes (MACs)". + +## --- 2 Introductory information + +### 2.1 Introduction + +Within the security architecture of the 3GPP system there are two standardised algorithms: A confidentiality algorithm *f8*, and an integrity algorithm *f9*. These algorithms are fully specified here. Each of these algorithms is based on the **KASUMI** algorithm that is specified in a companion document[4]. **KASUMI** is a block cipher that produces a 64-bit output from a 64-bit input under the control of a 128-bit key. + +The confidentiality algorithm *f8* is a stream cipher that is used to encrypt/decrypt blocks of data under a confidentiality key **CK**. The block of data may be between 1 and 20000 bits long. The algorithm uses **KASUMI** in a form of output-feedback mode as a keystream generator. + +The integrity algorithm *f9* computes a 32-bit MAC (Message Authentication Code) of a given input message using an integrity key **IK**. The approach adopted uses **KASUMI** in a form of CBC-MAC mode. + +### 2.2 Notation + +#### 2.2.1 Radix + +We use the prefix **0x** to indicate **hexadecimal** numbers. + +#### 2.2.2 Conventions + +We use the assignment operator ‘=’, as used in several programming languages. When we write + + = + +we mean that ** assumes the value that ** had before the assignment took place. For instance, + +$$x = x + y + 3$$ + +means + +(new value of *x*) becomes (old value of *x*) + (old value of *y*) + 3. + +#### 2.2.3 Bit/Byte ordering + +All data variables in this specification are presented with the most significant bit (or byte) on the left hand side and the least significant bit (or byte) on the right hand side. Where a variable is broken down into a number of sub-strings, the left most (most significant) sub-string is numbered 0, the next most significant is numbered 1 and so on through to the least significant. + +For example an n-bit **MESSAGE** is subdivided into 64-bit substrings **MB0, MB1...MBi** so if we have a message: + +0x0123456789ABCDEFEDCBA987654321086545381AB594FC28786404C50A37... + +we have: + +**MB**0 = 0x0123456789ABCDEF +**MB**1 = 0xFEDCBA9876543210 +**MB**2 = 0x86545381AB594FC2 +**MB**3 = 0x8786404C50A37... + +In binary this would be: + +00000001001000110100010101100111100010011010101111001101111011110... + +with + +$$\begin{aligned} +\mathbf{MB}_0 &= 0000000100100011010001010110011110001001101010111100110111101111 \\ +\mathbf{MB}_1 &= 1111111011011100101110101001100001110110010101000011001000010000 \\ +\mathbf{MB}_2 &= 1000011001010100010100111000000110101011010110010100111111000010 \\ +\mathbf{MB}_3 &= 10000111100001100100000001001100010100001010001101111 \dots +\end{aligned}$$ + +#### 2.2.4 List of Symbols + +- | | | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| = | The assignment operator. | +| ⊕ | The bitwise exclusive-OR operation. | +| | The concatenation of the two operands. | +| KASUMI[x] k | The output of the KASUMI algorithm applied to input value x using the key k . | +| X[i] | The i th bit of the variable X . ( X = X [0] X [1] X [2] ..... ). | +| Y i | The i th block of the variable Y . ( Y = Y 0 Y 1 Y 2 .... ). | + +### 2.3 List of Variables + +A, B are 64-bit registers that are used within the *f8* and *f9* functions to hold intermediate values. + +| | | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BEARER | a 5-bit input to the f8 function. | +| BLKCNT | a 64-bit counter used in the f8 function. | +| BLOCKS | an integer variable indicating the number of successive applications of KASUMI that need to be performed, for both the f8 and f9 functions. | +| CK | a 128-bit confidentiality key. | +| COUNT | a 32-bit time variant input to both the f8 and f9 functions. | +| DIRECTION | a 1-bit input to both the f8 and f9 functions indicating the direction of transmission (uplink or downlink). | +| FRESH | a 32-bit random input to the f9 function. | +| IBS | the input bit stream to the f8 function. | +| IK | a 128-bit integrity key. | +| KM | a 128-bit constant that is used to modify a key. This is used in both the f8 and f9 functions. (It takes a different value in each function). | +| KS[i] | is the i th bit of keystream produced by the keystream generator. | +| KS Bi | is the i th block of keystream produced by the keystream generator. Each block of keystream comprises 64 bits. | +| LENGTH | is an input to the f8 and f9 functions. It specifies the number of bits in the input bitstream. | +| MAC-I | is the 32-bit message authentication code (MAC) produced by the integrity function f9 . | +| MESSAGE | is the input bitstream of LENGTH bits that is to be processed by the f9 function. | +| OBS | the output bit streams from the f8 function. | +| PS | is the input padded string processed by the f9 function. | +| REGISTER | is a 64-bit value that is used within the f8 function. | + +## 3 Confidentiality algorithm *f8* + +### 3.1 Introduction + +The confidentiality algorithm *f8* is a stream cipher that encrypts/decrypts blocks of data between 1 and 20000 bits in length. + +### 3.2 Inputs and Outputs + +The inputs to the algorithm are given in table 1, the output in table 2: + +**Table 1: *f8* inputs** + +| Parameter | Size (bits) | Comment | +|-----------|------------------|-----------------------------------------------------------| +| COUNT | 32 | Frame dependent input
COUNT[0]...COUNT[31] | +| BEARER | 5 | Bearer identity BEARER[0]...BEARER[4] | +| DIRECTION | 1 | Direction of transmission DIRECTION[0] | +| CK | 128 | Confidentiality key CK[0]....CK[127] | +| LENGTH | X18 1 | The number of bits to be encrypted/decrypted
(1-20000) | +| IBS | 1-20000 | Input bit stream IBS[0]....IBS[LENGTH-1] | + +1 In the sample C-code we treat LENGTH as a 32-bit integer. + +**Table 2: f8 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-------------------------------------------| +| OBS | 1-20000 | Output bit stream OBS[0]....OBS[LENGTH-1] | + +### 3.3 Components and Architecture + +(See fig 1 Annex A) + +The keystream generator is based on the block cipher **KASUMI** that is specified in [4]. **KASUMI** is used in a form of output-feedback mode and generates the output keystream in multiples of 64-bits. + +The feedback data is modified by static data held in a 64-bit register **A**, and an (incrementing) 64-bit counter **BLKCNT**. + +### 3.4 Initialisation + +In this section we define how the keystream generator is initialised with the key variables before the generation of keystream bits. + +We set the 64-bit register **A** to **COUNT || BEARER || DIRECTION || 0...0** + +(left justified with the right most 26 bits set to 0). + +i.e. **A = COUNT[0]...COUNT[31] BEARER[0]...BEARER[4] DIRECTION[0] 0...0** + +We set counter **BLKCNT** to zero. + +We set the key modifier **KM** to 0x55555555555555555555555555555555 + +We set **KSB0** to zero. + +One operation of **KASUMI** is then applied to the register **A**, using a modified version of the confidentiality key. + +$$A = \text{KASUMI}[A]_{CK \oplus KM}$$ + +### 3.5 Keystream Generation + +Once the keystream generator has been initialised in the manner defined in section 3.4, it is ready to be used to generate keystream bits. The plaintext/ciphertext to be encrypted/decrypted consists of **LENGTH** bits (1-20000) whilst the keystream generator produces keystream bits in multiples of 64 bits. Between 0 and 63 of the least significant bits are discarded from the last block depending on the total number of bits required by **LENGTH**. + +So let **BLOCKS** be equal to (**LENGTH/64**) rounded up to the nearest integer. (For instance, if **LENGTH** = 128 then **BLOCKS** = 2; if **LENGTH** = 129 then **BLOCKS** = 3.) + +To generate each keystream block (**KSB**) we perform the following operation: + +For each integer **n** with $1 \leq n \leq \text{BLOCKS}$ we define: + +$$\text{KSB}_n = \text{KASUMI}[A \oplus \text{BLKCNT} \oplus \text{KSB}_{n-1}]_{CK}$$ + +where **BLKCNT** = **n-1** + +The individual bits of the keystream are extracted from **KSB1** to **KSBBLOCKS** in turn, most significant bit first, by applying the operation: + +For **n** = 1 to **BLOCKS**, and for each integer **i** with $0 \leq i \leq 63$ we define: + +$$\text{KS}[(n-1)*64+i] = \text{KSB}_n[i]$$ + +### 3.6 Encryption/Decryption + +Encryption/decryption operations are identical and are performed by the exclusive-OR of the input data (**IBS**) with the generated keystream (**KS**). + +For each integer $i$ with $0 \leq i \leq \text{LENGTH}-1$ we define: + +$$\text{OBS}[i] = \text{IBS}[i] \oplus \text{KS}[i]$$ + +## 4 Integrity algorithm $f9$ + +### 4.1 Introduction + +The integrity algorithm $f9$ computes a Message Authentication Code (MAC) on an input message under an integrity key **IK**. There is no limitation on the input message length of the $f9$ algorithm. + +For ease of implementation the algorithm is based on the same block cipher (**KASUMI**) as is used by the confidentiality algorithm $f8$ . + +### 4.2 Inputs and Outputs + +The inputs to the algorithm are given in table 3, the output in table 4: + +**Table 3: $f9$ inputs** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------------------------| +| COUNT-I | 32 | Frame dependent input COUNT-I[0]...COUNT-I[31] | +| FRESH | 32 | Random number FRESH[0]...FRESH[31] | +| DIRECTION | 1 | Direction of transmission DIRECTION[0] | +| IK | 128 | Integrity key IK[0]...IK[127] | +| LENGTH | $X19^2$ | The number of bits to be 'MAC'd | +| MESSAGE | LENGTH | Input bit stream | + +**Table 4: $f9$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| MAC-I | 32 | Message authentication code MAC-I[0]...MAC-I[31] | + +### 4.3 Components and Architecture + +(See fig 2 Annex A) + +The integrity function is based on the block cipher **KASUMI** that is specified in [4]. **KASUMI** is used in a chained mode to generate a 64-bit digest of the message input. Finally the leftmost 32-bits of the digest are taken as the output value **MAC-I**. + +### 4.4 Initialisation + +In this section we define how the integrity function is initialised with the key variables before the calculation commences. + +We set the working variables: **A** = 0 +and **B** = 0 + +We set the key modifier **KM** to 0xA...A + +We concatenate **COUNT**, **FRESH**, **MESSAGE** and **DIRECTION**. We then append a single '1' bit, followed by between 0 and 63 '0' bits so that the total length of the resulting string **PS** (padded string) is an integral multiple of 64 bits, i.e.: + +$$\text{PS} = \text{COUNT}[0] \dots \text{COUNT}[31] \text{ FRESH}[0] \dots \text{FRESH}[31] \text{ MESSAGE}[0] \dots \text{MESSAGE}[\text{LENGTH}-1] \text{ DIRECTION}[0] \text{ 1 } 0^*$$ + +2 In the sample C-code we treat LENGTH as a 32-bit integer. + +Where 0\* indicates between 0 and 63 '0' bits. + +### 4.5 Calculation + +We split the padded string **PS** into 64-bit blocks **PSi** where: + +$$\mathbf{PS} = \mathbf{PS}_0 \parallel \mathbf{PS}_1 \parallel \mathbf{PS}_2 \parallel \dots \parallel \mathbf{PS}_{\text{BLOCKS}-1}$$ + +We perform the following operations for each integer **n** with $0 \leq n \leq \text{BLOCKS}-1$ : + +$$\begin{aligned} \mathbf{A} &= \text{KASUMI}[\mathbf{A} \oplus \mathbf{PS}_n]_{\mathbf{IK}} \\ \mathbf{B} &= \mathbf{B} \oplus \mathbf{A} \end{aligned}$$ + +Finally we perform one more application of **KASUMI** using a modified form of the integrity key **IK**. + +$$\mathbf{B} = \text{KASUMI}[\mathbf{B}]_{\mathbf{IK} \oplus \mathbf{KM}}$$ + +The 32-bit **MAC-I** comprises the left-most 32 bits of the result. + +$$\mathbf{MAC-I} = \text{lefthalf}[\mathbf{B}]$$ + +i.e. For each integer **i** with $0 \leq i \leq 31$ we define: + +$$\mathbf{MAC-I}[i] = \mathbf{B}[i].$$ + +Bits **B[32]...B[63]** are discarded. + +# --- INFORMATIVE SECTION + +This part of the document is purely informative and does not form part of the normative specification of KASUMI. + +## Annex 1 (informative): Figures of the *f8* and *f9* Algorithms + +![Diagram of the f8 Keystream Generator showing the flow from COUNT || BEARER || DIRECTION || 0...0 through KASUMI and XOR operations to produce keystream blocks KS[0]...KS[63], KS[64]...KS[127], KS[128]...KS[191], and so on.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram illustrates the f8 Keystream Generator process. At the top, the input $COUNT \parallel BEARER \parallel DIRECTION \parallel 0 \dots 0$ is fed into a KASUMI block. The KASUMI block also receives $CK \oplus KM$ as input. The output of this KASUMI block is stored in a register labeled 'A'. Below 'A', a series of XOR gates (represented by circles with a cross) are shown. The first XOR gate takes the output of 'A' and the input $BLKCNT=0$ and produces an output that is fed into a KASUMI block. This KASUMI block also receives $CK$ as input and produces the keystream block $KS[0] \dots KS[63]$ . The output of this KASUMI block is also fed back into the second XOR gate. The second XOR gate takes the output of 'A' and the input $BLKCNT=1$ and produces an output that is fed into another KASUMI block. This KASUMI block also receives $CK$ as input and produces the keystream block $KS[64] \dots KS[127]$ . The output of this KASUMI block is also fed back into the third XOR gate. The third XOR gate takes the output of 'A' and the input $BLKCNT=2$ and produces an output that is fed into a third KASUMI block. This KASUMI block also receives $CK$ as input and produces the keystream block $KS[128] \dots KS[191]$ . The output of this KASUMI block is also fed back into the fourth XOR gate. The fourth XOR gate takes the output of 'A' and the input $BLKCNT=BLOCKS-1$ and produces an output that is fed into a fourth KASUMI block. This KASUMI block also receives $CK$ as input and produces the final keystream block shown. Dashed lines indicate that the process repeats for intermediate block counts. + +Diagram of the f8 Keystream Generator showing the flow from COUNT || BEARER || DIRECTION || 0...0 through KASUMI and XOR operations to produce keystream blocks KS[0]...KS[63], KS[64]...KS[127], KS[128]...KS[191], and so on. + +**Figure 1: f8 Keystream Generator** + +Note: **BLKCNT** is specified as a 64-bit counter so there is no ambiguity in the expression $A \oplus BLKCNT \oplus KSB_{n-1}$ where all operands are of the same size. In a practical implementation where the key stream generator is required to produce no more than 5114 bits (80 keystream blocks) only the least significant 7 bits of the counter need to be realised. + +![Diagram of the f9 Integrity function showing the flow from input data through multiple KASUMI blocks and XOR operations to produce the MAC-I output.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the f9 Integrity function. At the top, a long horizontal bar represents the input data, divided into four segments: **COUNT || FRESH**, **M E S S A G E**, **|| DIRECTION || 1 || 0 ... 0**, and an unlabeled segment. Below this input bar, four vertical arrows point down to labels **PS0**, **PS1**, **PS2**, and **PSBLOCKS-1**. Each of these labels has a vertical arrow pointing down to a rectangular block labeled **KASUMI**. Each **KASUMI** block also has a horizontal arrow labeled **IK** pointing into it from the left. The output of the first **KASUMI** block (PS0) is connected to an XOR symbol (a circle with a cross). The output of the second **KASUMI** block (PS1) is also connected to this XOR symbol. The output of this XOR symbol is connected to the third **KASUMI** block (PS2). The output of the third **KASUMI** block is connected to another XOR symbol. The output of the fourth **KASUMI** block (PSBLOCKS-1) is also connected to this second XOR symbol. The output of the second XOR symbol is connected to a final **KASUMI** block. This final block has a horizontal arrow labeled **IK ⊕ KM** pointing into it from the left. The output of this final **KASUMI** block is labeled **MAC-I (left 32-bits)**. + +Diagram of the f9 Integrity function showing the flow from input data through multiple KASUMI blocks and XOR operations to produce the MAC-I output. + +Figure 2: f9 Integrity function + +## Annex 2 (informative): Simulation Program Listing + +### Header file + +``` + +/*----- + * Kasumi.h + *-----*/ + +typedef unsigned char u8; +typedef unsigned short u16; +typedef unsigned long u32; + +/*----- a 64-bit structure to help with endian issues -----*/ + +typedef union { + u32 b32[2]; + u16 b16[4]; + u8 b8[8]; +} REGISTER64; + +/*----- prototypes -----*/ + +void KeySchedule( u8 *key ); +void Kasumi( u8 *data ); +u8 * f9( u8 *key,int count,int fresh, int dir,u8 *data,int length ); +void f8( u8 *key,int count,int bearer,int dir,u8 *data,int length ); + +``` + +#### Function f8 + +``` + +/*----- + * F8 - Confidentiality Algorithm + *----- + * + * A sample implementation of f8, the 3GPP Confidentiality algorithm. + * + * This has been coded for clarity, not necessarily for efficiency. + * + * This will compile and run correctly on both Intel (little endian) + * and Sparc (big endian) machines. (Compilers used supported 32-bit ints) + * + * Version 1.0 05 November 1999 + * + *-----*/ + +#include "kasumi.h" +#include + +/*----- + * f8() + * Given key, count, bearer, direction, data, + * and bit length encrypt the bit stream + *-----*/ + +void f8( u8 *key, int count, int bearer, int dir, u8 *data, int length ) +{ + REGISTER64 A; /* the modifier */ + REGISTER64 temp; /* The working register */ + int i, n; + u8 ModKey[16]; /* Modified key */ + u16 blkcnt; /* The block counter */ + + /* Start by building our global modifier */ + + temp.b32[0] = temp.b32[1] = 0; + A.b32[0] = A.b32[1] = 0; + + /* initialise register in an endian correct manner*/ + + A.b8[0] = (u8) (count>>24); + A.b8[1] = (u8) (count>>16); + A.b8[2] = (u8) (count>>8); + A.b8[3] = (u8) (count); + A.b8[4] = (u8) (bearer<<3); + A.b8[4] |= (u8) (dir<<2); + +``` + +``` + + /* Construct the modified key and then "kasumi" A */ + + for( n=0; n<16; ++n ) + ModKey[n] = (u8)(key[n] ^ 0x55); + KeySchedule( ModKey ); + + Kasumi( A.b8 ); /* First encryption to create modifier */ + + /* Final initialisation steps */ + + blkcnt = 0; + KeySchedule( key ); + + /* Now run the block cipher */ + + while( length > 0 ) + { + /* First we calculate the next 64-bits of keystream */ + + /* XOR in A and BLKCNT to last value */ + + temp.b32[0] ^= A.b32[0]; + temp.b32[1] ^= A.b32[1]; + temp.b8[7] ^= (u8) blkcnt; + temp.b8[6] ^= (u8) (blkcnt>>8); + + /* KASUMI it to produce the next block of keystream */ + + Kasumi( temp.b8 ); + + /* Set to the number of bytes of input data * + * we have to modify. (=8 if length <= 64) */ + + if( length >= 64 ) + n = 8; + else + n = (length+7)/8; + + /* XOR the keystream with the input data stream */ + + for( i=0; i + +/*------------------------------------------------------------------- + * f9() + * Given key, count, fresh, direction, data, + * and message length, calculate the hash value + *-------------------------------------------------------------------*/ +u8 *f9( u8 *key, int count, int fresh, int dir, u8 *data, int length ) + +``` + +``` + +{ + REGISTER64 A; /* Holds the CBC chained data */ + REGISTER64 B; /* Holds the XOR of all KASUMI outputs */ + u8 FinalBit[8] = {0x80, 0x40, 0x20, 0x10, 8,4,2,1}; + u8 ModKey[16]; + static u8 mac_i[4]; /* static memory for the result */ + int i, n; + + /* Start by initialising the block cipher */ + + KeySchedule( key ); + + /* Next initialise the MAC chain. Make sure we * + * have the data in the right byte order. * + * holds our chaining value... * + * is the running XOR of all KASUMI o/ps */ + + for( n=0; n<4; ++n ) + { + A.b8[n] = (u8) (count>>(24-(n*8))); + A.b8[n+4] = (u8) (fresh>>(24-(n*8))); + } + Kasumi( A.b8 ); + B.b32[0] = A.b32[0]; + B.b32[1] = A.b32[1]; + + /* Now run the blocks until we reach the last block */ + + while( length >= 64 ) + { + for( n=0; n<8; ++n ) + A.b8[n] ^= *data++; + Kasumi( A.b8 ); + length -= 64; + B.b32[0] ^= A.b32[0]; /* running XOR across */ + B.b32[1] ^= A.b32[1]; /* the block outputs */ + } + + /* Process whole bytes in the last block */ + + n = 0; + while( length >=8 ) + { + A.b8[n++] ^= *data++; + length -= 8; + } + + /* Now add the direction bit to the input bit stream * + * If length (which holds the # of data bits in the * + * last byte) is non-zero we add it in, otherwise * + * it has to start a new byte. */ + + if( length ) + { + i = *data; + if( dir ) + i |= FinalBit[length]; + } + else + i = dir ? 0x80 : 0; + + A.b8[n++] ^= (u8)i; + + /* Now add in the final '1' bit. The problem here * + * is if the message length happens to be n*64-1. * + * If so we need to process this block and then * + * create a new input block of 0x8000000000000000. */ + + if( (length==7) && (n==8) ) /* then we've filled the block */ + { + Kasumi( A.b8 ); + B.b32[0] ^= A.b32[0]; /* running XOR across */ + B.b32[1] ^= A.b32[1]; /* the block outputs */ + + A.b8[0] ^= 0x80; /* toggle first bit */ + i = 0x80; + n = 1; + } +} + +``` + +``` + } + else + { + if( length == 7 ) /* we finished off the last byte */ + A.b8[n] ^= 0x80; /* so start a new one..... */ + else + A.b8[n-1] ^= FinalBit[length+1]; + } + + Kasumi( A.b8 ); + B.b32[0] ^= A.b32[0]; /* running XOR across */ + B.b32[1] ^= A.b32[1]; /* the block outputs */ + + /* Final step is to KASUMI what we have using the */ + * key XORd with 0xAAAA..... */ + + for( n=0; n<16; ++n ) + ModKey[n] = (u8)*key++ ^ 0xAA; + KeySchedule( ModKey ); + Kasumi( B.b8 ); + + /* We return the left-most 32-bits of the result */ + + for( n=0; n<4; ++n ) + mac_i[n] = B.b8[n]; + + return( mac_i ); +} + +/*----- + * e n d o f f 9 . c + *-----*/ +``` + +## Annex 3 (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------------------|-----------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12-1999 | - | - | - | - | ETSI SAGE Publication (restricted) | - | SAGE v1.0 | +| 05-2000 | - | - | - | - | ETSI SAGE update: Small change to sample code (16-bit portability issue) | SAGE v1.0 | SAGE v1.1 | +| 09-2000 | - | - | - | - | ETSI SAGE update: Small change to sample f9 code (boundary condition) | SAGE v1.1 | SAGE v1.2 | +| 09-2000 | SA_07 | | | | Approved by TSG SA and placed under change control | SAGE v1.2 | 3.1.0 | +| 07-2001 | - | - | - | - | Word version received: Re-formatted into 3GPP TS format (MCC)
No technical change from version 3.1.0. | 3.1.0 | 3.1.1 | +| 08-2001 | - | | | | Addition of Mitsubishi IPR information in Foreword and correction of reference titles. No technical change from version 3.1.0. | 3.1.1 | 3.1.2 | +| 08-2001 | - | - | - | - | Release 4 version created. | 3.1.2 | 4.0.0 | +| 12-2001 | SP-14 | SP-010620 | 002 | | Correct the maximum input message length for f8 and f9 | 4.0.0 | 4.1.0 | +| 06-2002 | SP-16 | - | - | - | Upgrade to Release 5 | 4.1.0 | 5.0.0 | +| 12-2004 | SP-26 | - | - | - | Upgrade to Release 6 | 5.0.0 | 6.0.0 | +| 2005-09 | SP-29 | SP-050563 | 0003 | - | Correction of sample code | 6.0.0 | 6.1.0 | +| 06-2007 | SP-36 | - | - | - | Upgrade to Release 7 | 6.1.0 | 7.0.0 | +| 12-2008 | SP-42 | -- | - | - | Upgrade to Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Upgrade to Release 9 | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35202/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/35_series/35202/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9994e744ffb1562a77eda2e39751f88f39420c0a --- /dev/null +++ b/marked/Rel-16/35_series/35202/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f078104648e6231ccad7b88c41bca38d87da9d9b8c64ef492d6e4d8ecd60399 +size 23359 diff --git a/marked/Rel-16/35_series/35202/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-16/35_series/35202/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad27fd45ac7daa81eb5651484ab0a3cab5021ee3 --- /dev/null +++ b/marked/Rel-16/35_series/35202/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e6a13ab7fea29fc84bd7571b4d3bab4e41a8fc6c5ad39ec0a5ab93e89ffd235 +size 28355 diff --git a/marked/Rel-16/35_series/35202/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-16/35_series/35202/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f725a48936016ab08c854ac77aff13863d403f48 --- /dev/null +++ b/marked/Rel-16/35_series/35202/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6678b5197c939c075b7ab3d2379636a9f2602faa809a73e81c24112877a84db1 +size 20926 diff --git a/marked/Rel-16/35_series/35202/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/Rel-16/35_series/35202/90ee16ccc0ad16aeca48087797d7b07f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c65b90d86ca3b1e1c7c5c53b647b95090c339396 --- /dev/null +++ b/marked/Rel-16/35_series/35202/90ee16ccc0ad16aeca48087797d7b07f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38c199e41ea29d7189307cc710f3ac885fe0eb49a9df9e4c86c43ba7d06bd9ef +size 21718 diff --git a/marked/Rel-16/35_series/35202/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Rel-16/35_series/35202/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e236c1f197c885b5db67166b9e9e709ebb4b44f --- /dev/null +++ b/marked/Rel-16/35_series/35202/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2659331ebe3b09584405b295939c37556c83951e29ba51ff85b6fe9fb0bf27d +size 22549 diff --git a/marked/Rel-16/35_series/35202/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/35_series/35202/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10b09cb9b7c70be124efd2ccdc140d77abcd59f5 --- /dev/null +++ b/marked/Rel-16/35_series/35202/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:232a92b78e83a9738719e81c1044854acc4b0d2fbb0e084f2596e3ab0e85c6f2 +size 81004 diff --git a/marked/Rel-16/35_series/35202/raw.md b/marked/Rel-16/35_series/35202/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bc656208f398781a3379c9c0efff2d459c5050a3 --- /dev/null +++ b/marked/Rel-16/35_series/35202/raw.md @@ -0,0 +1,859 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 0 Scope..... | 6 | +| NORMATIVE SECTION ..... | 7 | +| 1 Outline of the normative part..... | 8 | +| 1.1 References ..... | 8 | +| 2 Introductory information..... | 8 | +| 2.1 Introduction ..... | 8 | +| 2.2 Notation..... | 9 | +| 2.2.1 Radix..... | 9 | +| 2.2.2 Bit/Byte ordering..... | 9 | +| 2.2.3 Conventions..... | 9 | +| 2.2.4 Subfunctions ..... | 9 | +| 2.2.5 List of Symbols..... | 10 | +| 2.3 List of Functions and Variables ..... | 10 | +| 3 KASUMI operation..... | 10 | +| 3.1 Introduction ..... | 10 | +| 3.2 Encryption ..... | 11 | +| 4 Components of KASUMI ..... | 11 | +| 4.1 Function $f_i$ ..... | 11 | +| 4.2 Function $FL$ ..... | 11 | +| 4.3 Function $FO$ ..... | 12 | +| 4.4 Function $FI$ ..... | 12 | +| 4.5 S-boxes ..... | 13 | +| 4.5.1 S7..... | 13 | +| 4.5.2 S9..... | 14 | +| 4.6 Key Schedule..... | 15 | +| INFORMATIVE SECTION ..... | 17 | +| Annex 1 (informative): Figures of the KASUMI Algorithm ..... | 18 | +| Annex 2 (informative): Simulation Program Listing..... | 20 | +| Annex 3 (informative): Change history..... | 24 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The 3GPP Confidentiality and Integrity Algorithms f8 & f9 have been developed through the collaborative efforts of the European Telecommunications Standards Institute (ETSI), the Association of Radio Industries and Businesses (ARIB), the Telecommunications Technology Association (TTA), the T1 Committee. + +The f8 & f9 Algorithms Specifications may be used only for the development and operation of 3G Mobile Communications and services. Every Beneficiary must sign a Restricted Usage Undertaking with the Custodian and demonstrate that he fulfills the approval criteria specified in the Restricted Usage Undertaking. + +Furthermore, Mitsubishi Electric Corporation holds essential patents on the Algorithms. The Beneficiary must get a separate IPR License Agreement from Mitsubishi Electronic Corporation Japan. + +For details of licensing procedures, contact ETSI, ARIB, TTA or T1. + +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 + +This specification has been prepared by the 3GPP Task Force, and gives a detailed specification of the 3GPP Algorithm KASUMI. KASUMI is a block cipher that forms the heart of the 3GPP confidentiality algorithm *f8*, and the 3GPP integrity algorithm *f9*. + +This document is the second of four, which between them form the entire specification of the 3GPP Confidentiality and Integrity Algorithms: + +- 3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: *f8* and *f9* Specification". +- **3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification".** +- 3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data". +- 3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data". + +The normative part of the specification of **KASUMI** is in the main body of this document. The annexes to this document are purely informative. Annex 1 contains illustrations of functional elements of the algorithm, while Annex 2 contains an implementation program listing of the cryptographic algorithm specified in the main body of this document, written in the programming language C. + +Similarly the normative part of the specification of the **f8** (confidentiality) and the **f9** (integrity) algorithms is in the main body of Document 1. The annexes of those documents, and Documents 3 and 4 above, are purely informative. + +## --- 0 Scope + +This specification gives a detailed specification of the 3GPP Algorithm KASUMI. KASUMI is a block cipher that forms the heart of the 3GPP confidentiality algorithm *f8*, and the 3GPP integrity algorithm *f9*. + +# --- NORMATIVE SECTION + +This part of the document contains the normative specification of the KASUMI algorithm. + +## --- 1 Outline of the normative part + +Section 2 introduces the algorithm and describes the notation used in the subsequent sections. + +Section 3 defines the algorithm structure and its operation. + +Section 4 defines the basic components of the algorithm. + +### 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] 3GPP TS 33.102 version 3.2.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 version 3.1.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 Specification". +- [4] 3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification". +- [5] 3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data". +- [6] 3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data". +- [7] ISO/IEC 9797-1:1999: "Information technology – Security techniques – Message Authentication Codes (MACs)". + +## --- 2 Introductory information + +### 2.1 Introduction + +Within the security architecture of the 3GPP system there are two standardised algorithms: A confidentiality algorithm *f8*, and an integrity algorithm *f9*. These algorithms are fully specified in a companion document[3]. Each of these algorithms is based on the **KASUMI** algorithm that is specified here. + +**KASUMI** is a block cipher that produces a 64-bit output from a 64-bit input under the control of a 128-bit key. + +### 2.2 Notation + +#### 2.2.1 Radix + +We use the prefix **0x** to indicate **hexadecimal** numbers. + +#### 2.2.2 Bit/Byte ordering + +All data variables in this specification are presented with the most significant bit (or byte) on the left hand side and the least significant bit (or byte) on the right hand side. Where a variable is broken down into a number of sub-strings, the left most (most significant) sub-string consists of the most significant part of the original string and so on through to the least significant. + +For example if a 64-bit value $X$ is subdivided into four 16-bit substrings $P, Q, R, S$ we have: + +$$X = 0x0123456789ABCDEF$$ + +we have: + +$$P = 0x0123, Q = 0x4567, R = 0x89AB, S = 0xCDEF.$$ + +In binary this would be: + +$$X = 0000000100100011010001010110011110001001101010111100110111101111$$ + +$$\begin{aligned} \text{with } P &= 0000000100100011 \\ Q &= 0100010101100111 \\ R &= 1000100110101011 \\ S &= 1100110111101111 \end{aligned}$$ + +#### 2.2.3 Conventions + +We use the assignment operator '=', as used in several programming languages. When we write + +$$\langle \text{variable} \rangle = \langle \text{expression} \rangle$$ + +we mean that $\langle \text{variable} \rangle$ assumes the value that $\langle \text{expression} \rangle$ had before the assignment took place. For instance, + +$$x = x + y + 3$$ + +means + +$$(\text{new value of } x) \text{ becomes } (\text{old value of } x) + (\text{old value of } y) + 3.$$ + +#### 2.2.4 Subfunctions + +KASUMI decomposes into a number of subfunctions (**FL**, **FO**, **FI**) which are used in conjunction with associated sub-keys (**KL**, **KO**, **KI**) in a Feistel structure comprising a number of rounds (and rounds within rounds for some subfunctions). Specific instances of the function and/or keys are represented by $XX_{ij}$ where $i$ is the outer round number of KASUMI and $j$ is the inner round number. + +For example the function **FO** comprises three rounds of the function **FI**, so we designate the third round of **FI** in the fifth round of KASUMI as **FI**5,3. + +#### 2.2.5 List of Symbols + +| | | +|--------|-------------------------------------------------------| +| = | The assignment operator. | +| ⊕ | The bitwise exclusive-OR operation. | +| | The concatenation of the two operands. | +| <<KASUMI | +| $FI()$ | A subfunction within KASUMI that translates a 16-bit input to a 16-bit output using a 16-bit subkey. | +| $FL()$ | A subfunction within KASUMI that translates a 32-bit input to a 32-bit output using a 32-bit subkey. | +| $FO()$ | A subfunction within KASUMI that translates a 32-bit input to a 32-bit output using two 48-bit subkeys. | +| $K$ | A 128-bit key. | +| $KL_i, KO_i, KI_i$ | subkeys used within the $i^{\text{th}}$ round of KASUMI . | +| $S7[]$ | An S-Box translating a 7-bit input to a 7-bit output. | +| $S9[]$ | An S-Box translating a 9-bit input to a 9-bit output. | + +## 3 KASUMI operation + +### 3.1 Introduction + +(See figure 1 in Annex 1) + +**KASUMI** is a Feistel cipher with eight rounds. It operates on a 64-bit data block and uses a 128-bit key. In this section we define the basic eight-round operation. In section 4 we define in detail the make-up of the round function $f_i()$ . + +### 3.2 Encryption + +**KASUMI** operates on a 64-bit input $I$ using a 128-bit key $K$ to produce a 64-bit output **OUTPUT**, as follows: + +The input $I$ is divided into two 32-bit strings $L_0$ and $R_0$ , where + +$$I = L_0 \parallel R_0$$ + +Then for each integer $i$ with $1 \leq i \leq 8$ we define: + +$$R_i = L_{i-1}, \quad L_i = R_{i-1} \oplus f_i(L_{i-1}, RK_i)$$ + +This constitutes the $i^{\text{th}}$ round function of **KASUMI**, where $f_i$ denotes the round function with $L_{i-1}$ and round key $RK_i$ as inputs (see section 4 below). + +The result **OUTPUT** is equal to the 64-bit string $(L_8 \parallel R_8)$ offered at the end of the eighth round. See figure 1 of Annex 1. + +In the specifications for the $f_8$ and $f_9$ functions we represent this transformation by the term: + +$$\text{OUTPUT} = \text{KASUMI}[I]_K$$ + +## 4 Components of KASUMI + +### 4.1 Function $f_i$ + +(See figure 1 in Annex 1) + +The function $f_i()$ takes a 32-bit input $I$ and returns a 32-bit output $O$ under the control of a round key $RK_i$ , where the round key comprises the subkey triplet of $(KL_i, KO_i, KI_i)$ . The function itself is constructed from two subfunctions; **FL** and **FO** with associated subkeys $KL_i$ (used with **FL**) and subkeys $KO_i$ and $KI_i$ (used with **FO**). + +The $f_i()$ function has two different forms depending on whether it is an even round or an odd round. + +For rounds 1,3,5 and 7 we define: + +$$f_i(I, RK_i) = FO( FL(I, KL_i), KO_i, KI_i )$$ + +and for rounds 2,4,6 and 8 we define: + +$$f_i(I, RK_i) = FL( FO(I, KO_i, KI_i), KL_i )$$ + +i.e. For odd rounds the round data is passed through $FL()$ and then $FO()$ , whilst for even rounds it is passed through $FO()$ and then $FL()$ . + +### 4.2 Function $FL$ + +(See figure 4 in Annex 1) + +The input to the function $FL$ comprises a 32-bit data input $I$ and a 32-bit subkey $KL_i$ . The subkey is split into two 16-bit subkeys, $KL_{i,1}$ and $KL_{i,2}$ where + +$$KL_i = KL_{i,1} \parallel KL_{i,2}.$$ + +The input data $I$ is split into two 16-bit halves, $L$ and $R$ where $I = L \parallel R$ . + +We define: + +$$\begin{aligned} R' &= R \oplus ROL(L \circ KL_{i,1}) \\ L' &= L \oplus ROL(R' \circ KL_{i,2}) \end{aligned}$$ + +The 32-bit output value is $(L' \parallel R')$ . + +### 4.3 Function $FO$ + +(See figure 2 in Annex 1) + +The input to the function $FO$ comprises a 32-bit data input $I$ and two sets of subkeys, a 48-bit subkey $KO_i$ and 48-bit subkey $KI_i$ . + +The 32-bit data input is split into two halves, $L_0$ and $R_0$ where $I = L_0 \parallel R_0$ . + +The 48-bit subkeys are subdivided into three 16-bit subkeys where + +$$KO_i = KO_{i,1} \parallel KO_{i,2} \parallel KO_{i,3} \text{ and } KI_i = KI_{i,1} \parallel KI_{i,2} \parallel KI_{i,3}.$$ + +Then for each integer $j$ with $1 \leq j \leq 3$ we define: + +$$\begin{aligned} R_j &= FI(L_{j-1} \oplus KO_{i,j}, KI_{i,j}) \oplus R_{j-1} \\ L_j &= R_{j-1} \end{aligned}$$ + +Finally we return the 32-bit value $(L_3 \parallel R_3)$ . + +### 4.4 Function $FI$ + +(See figure 3 in Annex 1. The thick and thin lines in this diagram are used to emphasise the difference between the 9-bit and 7-bit data paths respectively). + +The function $FI$ takes a 16-bit data input $I$ and 16-bit subkey $KI_{i,j}$ . The input $I$ is split into two unequal components, a 9-bit left half $L_0$ and a 7-bit right half $R_0$ where $I = L_0 \parallel R_0$ . + +Similarly the key $KI_{i,j}$ is split into a 7-bit component $KI_{i,j,1}$ and a 9-bit component $KI_{i,j,2}$ where $KI_{i,j} = KI_{i,j,1} \parallel KI_{i,j,2}$ . + +The function uses two S-boxes, $S7$ which maps a 7-bit input to a 7-bit output, and $S9$ which maps a 9-bit input to a 9-bit output. These are fully defined in section 4.5. It also uses two additional functions which we designate $ZE()$ and $TR()$ . We define these as: + +$ZE(x)$ takes the 7-bit value $x$ and converts it to a 9-bit value by adding two zero bits to the most-significant end. + +**TR(x)** takes the 9-bit value **x** and converts it to a 7-bit value by discarding the two most-significant bits. + +We define the following series of operations: + +$$\begin{aligned} L_1 &= R_0 & R_1 &= S9[L_0] \oplus ZE(R_0) \\ L_2 &= R_1 \oplus KI_{ij,2} & R_2 &= S7[L_1] \oplus TR(R_1) \oplus KI_{ij,1} \\ L_3 &= R_2 & R_3 &= S9[L_2] \oplus ZE(R_2) \\ L_4 &= S7[L_3] \oplus TR(R_3) & R_4 &= R_3 \end{aligned}$$ + +The function returns the 16-bit value $(L_4 \parallel R_4)$ . + +### 4.5 S-boxes + +The two S-boxes have been designed so that they may be easily implemented in combinational logic as well as by a look-up table. Both forms are given for each table. + +The input **x** comprises either seven or nine bits with a corresponding number of bits in the output **y**. We therefore have: + +$$x = x8 \parallel x7 \parallel x6 \parallel x5 \parallel x4 \parallel x3 \parallel x2 \parallel x1 \parallel x0$$ + +and + +$$y = y8 \parallel y7 \parallel y6 \parallel y5 \parallel y4 \parallel y3 \parallel y2 \parallel y1 \parallel y0$$ + +where the **x8, y8** and **x7, y7** bits only apply to S9, and the **x0** and **y0** bits are the least significant bits. + +In the logic equations: + +**x0x1x2** implies $x0 \cap x1 \cap x2$ where $\cap$ is the AND operator. + $\oplus$ is the exclusive-OR operator. + +Following the presentation of the logic equations and the equivalent look-up table an example is given of the use of each. + +#### 4.5.1 S7 + +##### Gate Logic : + +$$\begin{aligned} y0 &= x1x3 \oplus x4 \oplus x0x1x4 \oplus x5 \oplus x2x5 \oplus x3x4x5 \oplus x6 \oplus x0x6 \oplus x1x6 \oplus x3x6 \oplus x2x4x6 \oplus x1x5x6 \\ &\quad \oplus x4x5x6 \\ y1 &= x0x1 \oplus x0x4 \oplus x2x4 \oplus x5 \oplus x1x2x5 \oplus x0x3x5 \oplus x6 \oplus x0x2x6 \oplus x3x6 \oplus x4x5x6 \oplus 1 \\ y2 &= x0 \oplus x0x3 \oplus x2x3 \oplus x1x2x4 \oplus x0x3x4 \oplus x1x5 \oplus x0x2x5 \oplus x0x6 \oplus x0x1x6 \oplus x2x6 \oplus x4x6 \oplus 1 \\ y3 &= x1 \oplus x0x1x2 \oplus x1x4 \oplus x3x4 \oplus x0x5 \oplus x0x1x5 \oplus x2x3x5 \oplus x1x4x5 \oplus x2x6 \oplus x1x3x6 \\ y4 &= x0x2 \oplus x3 \oplus x1x3 \oplus x1x4 \oplus x0x1x4 \oplus x2x3x4 \oplus x0x5 \oplus x1x3x5 \oplus x0x4x5 \oplus x1x6 \oplus x3x6 \\ &\quad \oplus x0x3x6 \oplus x5x6 \oplus 1 \\ y5 &= x2 \oplus x0x2 \oplus x0x3 \oplus x1x2x3 \oplus x0x2x4 \oplus x0x5 \oplus x2x5 \oplus x4x5 \oplus x1x6 \oplus x1x2x6 \oplus x0x3x6 \\ &\quad \oplus x3x4x6 \oplus x2x5x6 \oplus 1 \\ y6 &= x1x2 \oplus x0x1x3 \oplus x0x4 \oplus x1x5 \oplus x3x5 \oplus x6 \oplus x0x1x6 \oplus x2x3x6 \oplus x1x4x6 \oplus x0x5x6 \end{aligned}$$ + +##### Decimal Table : + +54, 50, 62, 56, 22, 34, 94, 96, 38, 6, 63, 93, 2, 18, 123, 33, +55, 113, 39, 114, 21, 67, 65, 12, 47, 73, 46, 27, 25, 111, 124, 81, +53, 9, 121, 79, 52, 60, 58, 48, 101, 127, 40, 120, 104, 70, 71, 43, +20, 122, 72, 61, 23, 109, 13, 100, 77, 1, 16, 7, 82, 10, 105, 98, +117, 116, 76, 11, 89, 106, 0, 125, 118, 99, 86, 69, 30, 57, 126, 87, +112, 51, 17, 5, 95, 14, 90, 84, 91, 8, 35, 103, 32, 97, 28, 66, +102, 31, 26, 45, 75, 4, 85, 92, 37, 74, 80, 49, 68, 29, 115, 44, +64, 107, 108, 24, 110, 83, 36, 78, 42, 19, 15, 41, 88, 119, 59, 3 + +##### **Example:** + +If we have an input value = 38, then using the decimal table S7[38] = 58. + +For the combinational logic we have: + +$$38 = 0100110_2 \Rightarrow x6 = 0, x5=1, x4=0, x3=0, x2=1, x1=1, x0=0$$ + +which gives us: + +$$\begin{aligned} +y0 &= 0\oplus 0\oplus 0\oplus 1\oplus 1\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0 = 0 \\ +y1 &= 0\oplus 0\oplus 0\oplus 1\oplus 1\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 1 = 1 \\ +y2 &= 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 1\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 1 = 0 \\ +y3 &= 1\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0 = 1 \\ +y4 &= 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 1 = 1 \\ +y5 &= 1\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 1 = 1 \\ +y6 &= 1\oplus 0\oplus 0\oplus 0\oplus 1\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0\oplus 0 = 0 +\end{aligned}$$ + +Thus y = 01110102 = 58 + +#### 4.5.2 S9 + +##### Gate Logic : + +$$\begin{aligned} +y0 &= x0\oplus 2\oplus 3\oplus x2\oplus 5\oplus x5\oplus 6\oplus x0\oplus 7\oplus x1\oplus 7\oplus x2\oplus 7\oplus x4\oplus 8\oplus x5\oplus 8\oplus x7\oplus 8\oplus 1 \\ +y1 &= x1\oplus x0\oplus 1\oplus x2\oplus 3\oplus x0\oplus 4\oplus x1\oplus 4\oplus x0\oplus 5\oplus x3\oplus 5\oplus x6\oplus x1\oplus 7\oplus x2\oplus 7\oplus x5\oplus 8\oplus 1 \\ +y2 &= x1\oplus x0\oplus 3\oplus x3\oplus 4\oplus x0\oplus 5\oplus x2\oplus 6\oplus x3\oplus 6\oplus x5\oplus 6\oplus x4\oplus 7\oplus x5\oplus 7\oplus x6\oplus 7\oplus x8\oplus x0\oplus 8\oplus 1 \\ +y3 &= x0\oplus x1\oplus 2\oplus x0\oplus 3\oplus x2\oplus 4\oplus x5\oplus x0\oplus 6\oplus x1\oplus 6\oplus x4\oplus 7\oplus x0\oplus 8\oplus x1\oplus 8\oplus x7\oplus 8 \\ +y4 &= x0\oplus 1\oplus x1\oplus 3\oplus x4\oplus x0\oplus 5\oplus x3\oplus 6\oplus x0\oplus 7\oplus x6\oplus 7\oplus x1\oplus 8\oplus x2\oplus 8\oplus x3\oplus 8 \\ +y5 &= x2\oplus x1\oplus 4\oplus x4\oplus 5\oplus x0\oplus 6\oplus x1\oplus 6\oplus x3\oplus 7\oplus x4\oplus 7\oplus x6\oplus 7\oplus x5\oplus 8\oplus x6\oplus 8\oplus x7\oplus 8\oplus 1 \\ +y6 &= x0\oplus x2\oplus 3\oplus x1\oplus 5\oplus x2\oplus 5\oplus x4\oplus 5\oplus x3\oplus 6\oplus x4\oplus 6\oplus x5\oplus 6\oplus x7\oplus x1\oplus 8\oplus x3\oplus 8\oplus x5\oplus 8\oplus x7\oplus 8 \\ +y7 &= x0\oplus 1\oplus x0\oplus 2\oplus x1\oplus 2\oplus x3\oplus x0\oplus 3\oplus x2\oplus 3\oplus x4\oplus 5\oplus x2\oplus 6\oplus x3\oplus 6\oplus x2\oplus 7\oplus x5\oplus 7\oplus x8\oplus 1 \\ +y8 &= x0\oplus 1\oplus x2\oplus x1\oplus 2\oplus x3\oplus 4\oplus x1\oplus 5\oplus x2\oplus 5\oplus x1\oplus 6\oplus x4\oplus 6\oplus x7\oplus x2\oplus 8\oplus x3\oplus 8 +\end{aligned}$$ + +##### Decimal Table : + +167, 239, 161, 379, 391, 334, 9, 338, 38, 226, 48, 358, 452, 385, 90, 397, +183, 253, 147, 331, 415, 340, 51, 362, 306, 500, 262, 82, 216, 159, 356, 177, +175, 241, 489, 37, 206, 17, 0, 333, 44, 254, 378, 58, 143, 220, 81, 400, +95, 3, 315, 245, 54, 235, 218, 405, 472, 264, 172, 494, 371, 290, 399, 76, +165, 197, 395, 121, 257, 480, 423, 212, 240, 28, 462, 176, 406, 507, 288, 223, +501, 407, 249, 265, 89, 186, 221, 428, 164, 74, 440, 196, 458, 421, 350, 163, +232, 158, 134, 354, 13, 250, 491, 142, 191, 69, 193, 425, 152, 227, 366, 135, +344, 300, 276, 242, 437, 320, 113, 278, 11, 243, 87, 317, 36, 93, 496, 27, +487, 446, 482, 41, 68, 156, 457, 131, 326, 403, 339, 20, 39, 115, 442, 124, +475, 384, 508, 53, 112, 170, 479, 151, 126, 169, 73, 268, 279, 321, 168, 364, +363, 292, 46, 499, 393, 327, 324, 24, 456, 267, 157, 460, 488, 426, 309, 229, +439, 506, 208, 271, 349, 401, 434, 236, 16, 209, 359, 52, 56, 120, 199, 277, +465, 416, 252, 287, 246, 6, 83, 305, 420, 345, 153, 502, 65, 61, 244, 282, +173, 222, 418, 67, 386, 368, 261, 101, 476, 291, 195, 430, 49, 79, 166, 330, +280, 383, 373, 128, 382, 408, 155, 495, 367, 388, 274, 107, 459, 417, 62, 454, +132, 225, 203, 316, 234, 14, 301, 91, 503, 286, 424, 211, 347, 307, 140, 374, +35, 103, 125, 427, 19, 214, 453, 146, 498, 314, 444, 230, 256, 329, 198, 285, +50, 116, 78, 410, 10, 205, 510, 171, 231, 45, 139, 467, 29, 86, 505, 32, +72, 26, 342, 150, 313, 490, 431, 238, 411, 325, 149, 473, 40, 119, 174, 355, +185, 233, 389, 71, 448, 273, 372, 55, 110, 178, 322, 12, 469, 392, 369, 190, +1, 109, 375, 137, 181, 88, 75, 308, 260, 484, 98, 272, 370, 275, 412, 111, +336, 318, 4, 504, 492, 259, 304, 77, 337, 435, 21, 357, 303, 332, 483, 18, +47, 85, 25, 497, 474, 289, 100, 269, 296, 478, 270, 106, 31, 104, 433, 84, +414, 486, 394, 96, 99, 154, 511, 148, 413, 361, 409, 255, 162, 215, 302, 201, +266, 351, 343, 144, 441, 365, 108, 298, 251, 34, 182, 509, 138, 210, 335, 133, +311, 352, 328, 141, 396, 346, 123, 319, 450, 281, 429, 228, 443, 481, 92, 404, +485, 422, 248, 297, 23, 213, 130, 466, 22, 217, 283, 70, 294, 360, 419, 127, +312, 377, 7, 468, 194, 2, 117, 295, 463, 258, 224, 447, 247, 187, 80, 398, +284, 353, 105, 390, 299, 471, 470, 184, 57, 200, 348, 63, 204, 188, 33, 451, +97, 30, 310, 219, 94, 160, 129, 493, 64, 179, 263, 102, 189, 207, 114, 402, +438, 477, 387, 122, 192, 42, 381, 5, 145, 118, 180, 449, 293, 323, 136, 380, +43, 66, 60, 455, 341, 445, 202, 432, 8, 237, 15, 376, 436, 464, 59, 461 + +##### **Example:** + +If we have an input value = 138, then using the decimal table $S9[138] = 339$ . + +For the combinational logic we have: + +$$138 = 010001010_2 \Rightarrow x_8 = 0, x_7 = 1, x_6 = 0, x_5=0, x_4=0, x_3=1, x_2=0, x_1=1, x_0=0$$ + +which gives us: + +$$\begin{aligned} y_0 &= 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 &= 1 \\ y_1 &= 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 \oplus 1 &= 1 \\ y_2 &= 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 &= 0 \\ y_3 &= 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 &= 0 \\ y_4 &= 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 &= 1 \\ y_5 &= 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 &= 0 \\ y_6 &= 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 &= 1 \\ y_7 &= 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 &= 0 \\ y_8 &= 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 0 \oplus 1 \oplus 0 \oplus 0 \oplus 0 &= 1 \end{aligned}$$ + +Thus $y = 101010011_2 = 339$ + +### 4.6 Key Schedule + +KASUMI has a 128-bit key $K$ . Each round of KASUMI uses 128 bits of key that are derived from $K$ . Before the round keys can be calculated two 16-bit arrays $K_j$ and $K_j'$ ( $j=1$ to 8) are derived in the following manner: + +The 128-bit key $K$ is subdivided into eight 16-bit values $K_1 \dots K_8$ where + +$$K = K_1 \parallel K_2 \parallel K_3 \parallel \dots \parallel K_8.$$ + +A second array of subkeys, $K_j'$ is derived from $K_j$ by applying: + +For each integer $j$ with $1 \leq j \leq 8$ + +$$K_j' = K_j \oplus C_j$$ + +Where $C_j$ is the constant value defined in table 2. + +The round subkeys are then derived from $K_j$ and $K_j'$ in the manner defined in table 1. + +**Table 1: Round subkeys** + +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------| +| $KL_{i,1}$ | $K1 \lll 1$ | $K2 \lll 1$ | $K3 \lll 1$ | $K4 \lll 1$ | $K5 \lll 1$ | $K6 \lll 1$ | $K7 \lll 1$ | $K8 \lll 1$ | +| $KL_{i,2}$ | $K3'$ | $K4'$ | $K5'$ | $K6'$ | $K7'$ | $K8'$ | $K1'$ | $K2'$ | +| $KO_{i,1}$ | $K2 \lll 5$ | $K3 \lll 5$ | $K4 \lll 5$ | $K5 \lll 5$ | $K6 \lll 5$ | $K7 \lll 5$ | $K8 \lll 5$ | $K1 \lll 5$ | +| $KO_{i,2}$ | $K6 \lll 8$ | $K7 \lll 8$ | $K8 \lll 8$ | $K1 \lll 8$ | $K2 \lll 8$ | $K3 \lll 8$ | $K4 \lll 8$ | $K5 \lll 8$ | +| $KO_{i,3}$ | $K7 \lll 13$ | $K8 \lll 13$ | $K1 \lll 13$ | $K2 \lll 13$ | $K3 \lll 13$ | $K4 \lll 13$ | $K5 \lll 13$ | $K6 \lll 13$ | +| $KL_{i,1}$ | $K5'$ | $K6'$ | $K7'$ | $K8'$ | $K1'$ | $K2'$ | $K3'$ | $K4'$ | +| $KL_{i,2}$ | $K4'$ | $K5'$ | $K6'$ | $K7'$ | $K8'$ | $K1'$ | $K2'$ | $K3'$ | +| $KL_{i,3}$ | $K8'$ | $K1'$ | $K2'$ | $K3'$ | $K4'$ | $K5'$ | $K6'$ | $K7'$ | + +**Table 2: Constants** + +| | | +|----|--------| +| C1 | 0x0123 | +| C2 | 0x4567 | +| C3 | 0x89AB | +| C4 | 0xCDEF | +| C5 | 0xFEDC | +| C6 | 0xBA98 | +| C7 | 0x7654 | +| C8 | 0x3210 | + +# --- INFORMATIVE SECTION + +This part of the document is purely informative and does not form part of the normative specification of KASUMI. + +## Annex 1 (informative): Figures of the KASUMI Algorithm + +![Diagram of the KASUMI algorithm structure showing 8 rounds of FL and FO functions with key inputs KL and KO.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +The diagram illustrates the KASUMI algorithm's structure. It starts with a 64-bit input split into two 32-bit halves, $L_0$ and $R_0$ . The algorithm consists of 8 rounds. Each round $i$ (for $i = 1, 2, \dots, 8$ ) involves an FO function followed by an FL function. The FO function takes a 32-bit input and produces a 32-bit output, which is then XORed with the current 32-bit state. The FL function takes a 32-bit input and produces a 32-bit output, which is also XORed with the current 32-bit state. The FO function is composed of 8 sub-functions, $FO_1$ through $FO_8$ , each taking a 32-bit input and producing a 32-bit output. The FL function is composed of 8 sub-functions, $FL_1$ through $FL_8$ , each taking a 32-bit input and producing a 32-bit output. The FO functions are followed by the FL functions in each round. The final output is a 64-bit block $C$ , split into $L_8$ and $R_8$ . + +Diagram of the KASUMI algorithm structure showing 8 rounds of FL and FO functions with key inputs KL and KO. + +Fig. 1: KASUMI + +![Diagram of the FO function structure showing 3 rounds of FI functions with key inputs KO and KI.](21ad58fee90f2be50708ff541d225507_img.jpg) + +The diagram illustrates the FO function structure. It takes a 32-bit input and produces a 32-bit output. The FO function is composed of 3 rounds of FI functions. Each round $i$ (for $i = 1, 2, 3$ ) involves an FI function followed by an XOR operation with a key input $KO_{i,1}$ and $KI_{i,1}$ . The FI function takes a 16-bit input and produces a 16-bit output. The XOR operation is performed on the 16-bit output of the FI function and the 16-bit key input. The final output of the FO function is the 32-bit result of the XOR operations. + +Diagram of the FO function structure showing 3 rounds of FI functions with key inputs KO and KI. + +Fig.2: FO Function + +![Diagram of the FI function structure showing 4 rounds of S-boxes and truncation operations with key inputs KI.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates the FI function structure. It takes a 16-bit input and produces a 16-bit output. The FI function is composed of 4 rounds. The first round involves an S9 S-box followed by a zero-extension operation. The second round involves an S7 S-box followed by a truncation operation. The third round involves an S9 S-box followed by a zero-extension operation. The fourth round involves an S7 S-box followed by a truncation operation. The output of each round is XORed with a key input $KI_{i,j,1}$ and $KI_{i,j,2}$ . The final output of the FI function is the 16-bit result of the XOR operations. + +Diagram of the FI function structure showing 4 rounds of S-boxes and truncation operations with key inputs KI. + +Fig.3: FI Function + +![Diagram of the FL function structure showing bitwise AND, OR, and rotation operations with key inputs KL.](90ee16ccc0ad16aeca48087797d7b07f_img.jpg) + +The diagram illustrates the FL function structure. It takes a 32-bit input and produces a 32-bit output. The FL function is composed of two main operations. The first operation is a bitwise AND operation between the 32-bit input and a key input $KL_{i,1}$ , followed by a one-bit left rotation. The second operation is a bitwise OR operation between the result of the first operation and another key input $KL_{i,2}$ , followed by a one-bit left rotation. The final output of the FL function is the 32-bit result of the OR operation. + +$\cap$ bitwise AND operation + $\cup$ bitwise OR operation + $\lll$ one bit left rotation + +Diagram of the FL function structure showing bitwise AND, OR, and rotation operations with key inputs KL. + +Fig.4: FL Function + +KASUMI has a number of characteristics that may be exploited in a hardware implementation and these are highlighted here. + +- The simple key schedule is easy to implement in hardware. +- The S-Boxes have been designed so that they may be implemented by a small amount of combinational logic rather than by large look-up tables. +- The S7-Box and S9-Box operations in the FI function may be carried out in parallel (see alternative presentation in figure 5). +- The $FI_{i,1}$ and $FI_{i,2}$ operations may be carried out in parallel (see alternative presentation in figure 6). + +![Diagram of the FI Function](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +Detailed description of Fig. 5: FI Function. The input is 16 bits, split into a 9-bit left branch and a 7-bit right branch. + 1. The 9-bit branch enters an S9 box. + 2. The output of S9 is XORed with the 7-bit branch (zero-extended). + 3. The 7-bit branch enters an S7 box. + 4. The output of S7 is XORed with the 7 least significant bits of the 9-bit branch. + 5. This process repeats with another layer of S9 and S7 boxes and XORs. + 6. There are cross-connections between the branches. + 7. The final stage involves a trapezoidal mixing block before the 16-bit output. + +Diagram of the FI Function + +Fig.5: FI Function + +![Diagram of the FO Function](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Detailed description of Fig. 6: FO Function. The input is 32 bits, split into two 16-bit halves (left and right). + 1. The left 16 bits are XORed with a subkey and enter the $FI_{i,1}$ block. + 2. The output of $FI_{i,1}$ is XORed into the right 16-bit path. + 3. The right 16 bits (after XOR) are XORed with a subkey and enter the $FI_{i,2}$ block. + 4. The output of $FI_{i,2}$ is XORed back into the left path. + 5. The left path then enters the $FI_{i,3}$ block after another subkey XOR. + 6. The output of $FI_{i,3}$ is XORed into the right path. + 7. Finally, the two 16-bit halves are swapped/mixed through a trapezoidal structure to produce the 32-bit output. + +Diagram of the FO Function + +Fig.6: FO Function + +## Annex 2 (informative): Simulation Program Listing + +### Header file + +``` +/*----- + * Kasumi.h + *-----*/ + +typedef unsigned char u8; +typedef unsigned short u16; +typedef unsigned long u32; + +void KeySchedule( u8 *key ); +void Kasumi( u8 *data ); +``` + +### C Code + +``` +/*----- + * Kasumi.c + *----- + * + * A sample implementation of KASUMI, the core algorithm for the + * 3GPP Confidentiality and Integrity algorithms. + * + * This has been coded for clarity, not necessarily for efficiency. + * + * This will compile and run correctly on both Intel (little endian) + * and Sparc (big endian) machines. (Compilers used supported 32-bit ints). + * + * Version 1.1 08 May 2000 + * + *-----*/ + +#include "Kasumi.h" + +/*----- 16 bit rotate left -----*/ + +#define ROL16(a,b) (u16) ((a<>(16-b))) + +/*----- unions: used to remove "endian" issues -----*/ + +typedef union { + u32 b32; + u16 b16[2]; + u8 b8[4]; +} DWORD; + +typedef union { + u16 b16; + u8 b8[2]; +} WORD; + +/*----- globals: The subkey arrays -----*/ + +static u16 KLi1[8], KLi2[8]; +static u16 KOi1[8], KOi2[8], KOi3[8]; +static u16 Kii1[8], Kii2[8], Kii3[8]; + +/*----- + * FI() + * The FI function (fig 3). It includes the S7 and S9 tables. + * Transforms a 16-bit value. + *-----*/ + +static u16 FI( u16 in, u16 subkey ) +{ + u16 nine, seven; + static u16 S7[] = { + 54, 50, 62, 56, 22, 34, 94, 96, 38, 6, 63, 93, 2, 18, 123, 33, + 55, 113, 39, 114, 21, 67, 65, 12, 47, 73, 46, 27, 25, 111, 124, 81, + 53, 9, 121, 79, 52, 60, 58, 48, 101, 127, 40, 120, 104, 70, 71, 43, + 20, 122, 72, 61, 23, 109, 13, 100, 77, 1, 16, 7, 82, 10, 105, 98, + 117, 116, 76, 11, 89, 106, 0, 125, 118, 99, 86, 69, 30, 57, 126, 87, + 112, 51, 17, 5, 95, 14, 90, 84, 91, 8, 35, 103, 32, 97, 28, 66, + }; + +``` + +``` + + 102, 31, 26, 45, 75, 4, 85, 92, 37, 74, 80, 49, 68, 29, 115, 44, + 64, 107, 108, 24, 110, 83, 36, 78, 42, 19, 15, 41, 88, 119, 59, 3}; +static u16 S9[] = { + 167, 239, 161, 379, 391, 334, 9, 338, 38, 226, 48, 358, 452, 385, 90, 397, + 183, 253, 147, 331, 415, 340, 51, 362, 306, 500, 262, 82, 216, 159, 356, 177, + 175, 241, 489, 37, 206, 17, 0, 333, 44, 254, 378, 58, 143, 220, 81, 400, + 95, 3, 315, 245, 54, 235, 218, 405, 472, 264, 172, 494, 371, 290, 399, 76, + 165, 197, 395, 121, 257, 480, 423, 212, 240, 28, 462, 176, 406, 507, 288, 223, + 501, 407, 249, 265, 89, 186, 221, 428, 164, 74, 440, 196, 458, 421, 350, 163, + 232, 158, 134, 354, 13, 250, 491, 142, 191, 69, 193, 425, 152, 227, 366, 135, + 344, 300, 276, 242, 437, 320, 113, 278, 11, 243, 87, 317, 36, 93, 496, 27, + 487, 446, 482, 41, 68, 156, 457, 131, 326, 403, 339, 20, 39, 115, 442, 124, + 475, 384, 508, 53, 112, 170, 479, 151, 126, 169, 73, 268, 279, 321, 168, 364, + 363, 292, 46, 499, 393, 327, 324, 24, 456, 267, 157, 460, 488, 426, 309, 229, + 439, 506, 208, 271, 349, 401, 434, 236, 16, 209, 359, 52, 56, 120, 199, 277, + 465, 416, 252, 287, 246, 6, 83, 305, 420, 345, 153, 502, 65, 61, 244, 282, + 173, 222, 418, 67, 386, 368, 261, 101, 476, 291, 195, 430, 49, 79, 166, 330, + 280, 383, 373, 128, 382, 408, 155, 495, 367, 388, 274, 107, 459, 417, 62, 454, + 132, 225, 203, 316, 294, 14, 301, 91, 503, 286, 424, 211, 347, 307, 140, 374, + 35, 103, 125, 427, 19, 214, 453, 146, 498, 314, 444, 230, 256, 329, 198, 285, + 50, 116, 78, 410, 10, 205, 510, 171, 231, 45, 139, 467, 29, 86, 505, 32, + 72, 26, 342, 150, 313, 490, 431, 238, 411, 325, 149, 473, 40, 119, 174, 355, + 185, 233, 389, 71, 448, 273, 372, 55, 110, 178, 322, 12, 469, 392, 369, 190, + 1, 109, 375, 137, 181, 88, 75, 308, 260, 484, 98, 272, 370, 275, 412, 111, + 336, 318, 4, 504, 492, 259, 304, 77, 337, 435, 21, 357, 303, 332, 483, 18, + 47, 85, 25, 497, 474, 289, 100, 269, 296, 478, 270, 106, 31, 104, 433, 84, + 414, 486, 394, 96, 99, 154, 511, 148, 413, 361, 409, 255, 162, 215, 302, 201, + 266, 351, 343, 144, 441, 365, 108, 298, 251, 34, 182, 509, 138, 210, 335, 133, + 311, 352, 328, 141, 396, 346, 123, 319, 450, 281, 429, 228, 443, 481, 92, 404, + 485, 422, 248, 297, 23, 213, 130, 466, 22, 217, 283, 70, 294, 360, 419, 127, + 312, 377, 7, 468, 194, 2, 117, 295, 463, 258, 224, 447, 247, 187, 80, 398, + 284, 353, 105, 390, 299, 471, 470, 184, 57, 200, 348, 63, 204, 188, 33, 451, + 97, 30, 310, 219, 94, 160, 129, 493, 64, 179, 263, 102, 189, 207, 114, 402, + 438, 477, 387, 122, 192, 42, 381, 5, 145, 118, 180, 449, 293, 323, 136, 380, + 43, 66, 60, 455, 341, 445, 202, 432, 8, 237, 15, 376, 436, 464, 59, 461}; + + /* The sixteen bit input is split into two unequal halves, * + * nine bits and seven bits - as is the subkey */ + + nine = (u16)(in>>7); + seven = (u16)(in&0x7F); + + /* Now run the various operations */ + + nine = (u16)(S9[nine] ^ seven); + seven = (u16)(S7[seven] ^ (nine & 0x7F)); + + seven ^= (subkey>>9); + nine ^= (subkey&0x1FF); + + nine = (u16)(S9[nine] ^ seven); + seven = (u16)(S7[seven] ^ (nine & 0x7F)); + + in = (u16)((seven<<9) + nine); + + return( in ); +} + +/*----- + * FO() + * The FO() function. + * Transforms a 32-bit value. Uses to identify the + * appropriate subkeys to use. + *-----*/ +static u32 FO( u32 in, int index ) +{ + u16 left, right; + + /* Split the input into two 16-bit words */ + + left = (u16)(in>>16); + right = (u16) in; + + /* Now apply the same basic transformation three times */ + + left ^= KOi1[index]; + left = FI( left, KIi1[index] ); +} + +``` + +``` + + left ^= right; + + right ^= KOi2[index]; + right = FI( right, Ki2[index] ); + right ^= left; + + left ^= KOi3[index]; + left = FI( left, Ki3[index] ); + left ^= right; + + in = (((u32)right)<<16)+left; + + return( in ); +} + +/*----- + * FL() + * The FL() function. + * Transforms a 32-bit value. Uses to identify the + * appropriate subkeys to use. + *-----*/ +static u32 FL( u32 in, int index ) +{ + u16 l, r, a, b; + + /* split out the left and right halves */ + + l = (u16) (in>>16); + r = (u16) (in); + + /* do the FL() operations */ + + a = (u16) (l & KLi1[index]); + r ^= ROL16(a,1); + + b = (u16) (r | KLi2[index]); + l ^= ROL16(b,1); + + /* put the two halves back together */ + + in = (((u32)l)<<16) + r; + + return( in ); +} + +/*----- + * Kasumi() + * the Main algorithm (fig 1). Apply the same pair of operations + * four times. Transforms the 64-bit input. + *-----*/ +void Kasumi( u8 *data ) +{ + u32 left, right, temp; + DWORD *d; + int n; + + /* Start by getting the data into two 32-bit words (endian correct) */ + + d = (DWORD*)data; + left = (((u32)d[0].b8[0])<<24)+(((u32)d[0].b8[1])<<16) + +(d[0].b8[2]<<8)+(d[0].b8[3])); + right = (((u32)d[1].b8[0])<<24)+(((u32)d[1].b8[1])<<16) + +(d[1].b8[2]<<8)+(d[1].b8[3])); + n = 0; + do{ + temp = FL( left, n ); + temp = FO( temp, n++ ); + right ^= temp; + temp = FO( right, n ); + temp = FL( temp, n++ ); + left ^= temp; + }while( n<=7 ); + + /* return the correct endian result */ + d[0].b8[0] = (u8) (left>>24); d[1].b8[0] = (u8) (right>>24); + d[0].b8[1] = (u8) (left>>16); d[1].b8[1] = (u8) (right>>16); + d[0].b8[2] = (u8) (left>>8); d[1].b8[2] = (u8) (right>>8); + d[0].b8[3] = (u8) (left); d[1].b8[3] = (u8) (right); +} + +``` + +``` + } + + /*----- + * KeySchedule() + * Build the key schedule. Most "key" operations use 16-bit + * subkeys so we build u16-sized arrays that are "endian" correct. + *-----*/ + void KeySchedule( u8 *k ) + { + static u16 C[] = { + 0x0123,0x4567,0x89AB,0xCDEF, 0xFEDC,0xBA98,0x7654,0x3210 }; + u16 key[8], Kprime[8]; + WORD *k16; + int n; + + /* Start by ensuring the subkeys are endian correct on a 16-bit basis */ + + k16 = (WORD *)k; + for( n=0; n<8; ++n ) + key[n] = (u16)((k16[n].b8[0]<<8) + (k16[n].b8[1])); + + /* Now build the K'[] keys */ + + for( n=0; n<8; ++n ) + Kprime[n] = (u16)(key[n] ^ C[n]); + + /* Finally construct the various sub keys */ + + for( n=0; n<8; ++n ) + { + KL11[n] = ROL16(key[n],1); + KL12[n] = Kprime[(n+2)&0x7]; + KO11[n] = ROL16(key[(n+1)&0x7],5); + KO12[n] = ROL16(key[(n+5)&0x7],8); + KO13[n] = ROL16(key[(n+6)&0x7],13); + KI11[n] = Kprime[(n+4)&0x7]; + KI12[n] = Kprime[(n+3)&0x7]; + KI13[n] = Kprime[(n+7)&0x7]; + } + } + + /*----- + * e n d o f k a s u m i . c + *-----*/ +``` + +## Annex 3 (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------------------|-----------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12-1999 | - | - | - | - | ETSI SAGE Publication (restricted) | - | SAGE v1.0 | +| 05-2000 | - | - | - | - | ETSI SAGE update: Small change to sample code (portability issue) | SAGE v1.0 | SAGE v1.1 | +| 09-2000 | SA_07 | | | | Approved by TSG SA and placed under change control | SAGE v1.1 | 3.1.0 | +| 07-2001 | - | - | - | - | Word version received: Re-formatted into 3GPP TS format (MCC)
No technical change from version 3.1.0. | 3.1.0 | 3.1.1 | +| 08-2001 | - | | | | Addition of Mitsubishi IPR information in Foreword and correction of reference titles. No technical change from version 3.1.0. | 3.1.1 | 3.1.2 | +| 08-2001 | - | - | - | - | Release 4 version created. | 3.1.2 | 4.0.0 | +| 06-2002 | - | - | - | - | Release 5 version created. | 4.0.0 | 5.0.0 | +| 12-2004 | SP-26 | - | - | - | Release 6 version created. | 5.0.0 | 6.0.0 | +| 2005-09 | SP-29 | SP-050564 | 0001 | - | Kasumi roundfunction, correction of formula | 6.0.0 | 6.1.0 | +| 06-2007 | SP-36 | - | - | - | Release 7 version created. | 6.1.0 | 7.0.0 | +| 12-2008 | SP-32 | - | - | - | Release 8 version created. | 7.0.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Rel-9 version created | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35203/raw.md b/marked/Rel-16/35_series/35203/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..407cd6aa05f1bd6907fd96f463546a809cd92eb7 --- /dev/null +++ b/marked/Rel-16/35_series/35203/raw.md @@ -0,0 +1,961 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 0 Scope..... | 5 | +| 1 Outline of the implementors' test data ..... | 5 | +| 1.1 References ..... | 5 | +| 2 Introductory information..... | 6 | +| 2.1 Introduction ..... | 6 | +| 2.2 Radix ..... | 6 | +| 2.3 Bit/Byte ordering..... | 6 | +| 2.4 Presentation of input/output data..... | 6 | +| 3 KASUMI..... | 6 | +| 3.1 Overview ..... | 6 | +| 3.2 Format ..... | 6 | +| 3.3 Test Set 1..... | 7 | +| 3.4 Test Set 2..... | 9 | +| 3.5 Test Set 3..... | 10 | +| 3.6 Test Set 4..... | 12 | +| 4 Confidentiality algorithm $f_8$ ..... | 12 | +| 4.1 Overview ..... | 12 | +| 4.2 Format ..... | 12 | +| 4.3 Test Set 1..... | 13 | +| 4.4 Test Set 2..... | 13 | +| 4.5 Test Set 3..... | 14 | +| 4.6 Test Set 4..... | 14 | +| 4.7 Test Set 5..... | 15 | +| 5 Integrity algorithm $f_9$ ..... | 15 | +| 5.1 Overview ..... | 15 | +| 5.2 Format ..... | 15 | +| 5.3 Test Set 1..... | 16 | +| 5.4 Test Set 2..... | 16 | +| 5.5 Test Set 3..... | 16 | +| 5.6 Test Set 4..... | 17 | +| 5.7 Test Set 5..... | 17 | +| Annex A (informative): Change history..... | 18 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The 3GPP Confidentiality and Integrity Algorithms f8 & f9 have been developed through the collaborative efforts of the European Telecommunications Standards Institute (ETSI), the Association of Radio Industries and Businesses (ARIB), the Telecommunications Technology Association (TTA), the T1 Committee. + +The f8 & f9 Algorithms Specifications may be used only for the development and operation of 3G Mobile Communications and services. Every Beneficiary must sign a Restricted Usage Undertaking with the Custodian and demonstrate that he fulfils the approval criteria specified in the Restricted Usage Undertaking. + +Furthermore, Mitsubishi Electric Corporation holds essential patents on the Algorithms. The Beneficiary must get a separate IPR License Agreement from Mitsubishi Electronic Corporation Japan. + +For details of licensing procedures, contact ETSI, ARIB, TTA or T1. + +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 + +This specification has been prepared by the 3GPP Task Force, and gives detailed test data for implementors of the algorithm set. It provides visibility of the internal state of the algorithm to aid in the realisation of the algorithms. + +This document is the third of four, which between them form the entire specification of the 3GPP Confidentiality and Integrity Algorithms: + +- 3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 Specification". +- 3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification". +- **3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data".** +- 3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data". + +This document is purely informative. The normative part of the specification of the f8 (confidentiality) and the f9 (integrity) algorithms is in the main body of Document 1. The normative part of the specification of KASUMI is found in document 2. + +# --- 0 Scope + +This specification gives detailed test data for implementors of the algorithm set. It provides visibility of the internal state of the algorithm to aid in the realisation of the algorithms. + +# --- 1 Outline of the implementors' test data + +Clause 2 introduces the algorithms and describes the notation used in the subsequent Clauses. + +Clause 3 provides test data for **KASUMI**. + +Clause 4 provides test data for the Confidentiality Algorithm F8. + +Clause 5 provides test data for the Integrity Algorithm F9. + +## 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] 3GPP TS 33.102 version 3.2.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 version 3.1.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 Specification". +- [4] 3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification". +- [5] 3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data". +- [6] 3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data". +- [7] ISO/IEC 9797-1:1999: "Information technology – Security techniques – Message Authentication Codes (MACs)". + +# --- 2 Introductory information + +## 2.1 Introduction + +Within the security architecture of the 3GPP system there are two standardised algorithms; a confidentiality algorithm *f8*, and an integrity algorithm *f9*. These algorithms are specified in a companion document [3]. Each of these algorithms is based on the **KASUMI** algorithm that is specified in [4]. + +To assist implementors with their realisation of the algorithm set this document provides test data for these algorithms along with extensive detail of the internal states of the algorithms as they process the given input data. + +Final testing of the algorithms should be performed using the test data sets given in the "Design Conformance" companion document [6]. + +## 2.2 Radix + +Unless stated otherwise, all test data values presented in this document are in hexadecimal. + +## 2.3 Bit/Byte ordering + +All data variables in this specification are presented with the most significant bit (or byte) on the left hand side and the least significant bit (or byte) on the right hand side. Where a variable is broken down into a number of sub-strings, the left most (most significant) sub-string is numbered 1, the next most significant is numbered 2 and so on through to the least significant. + +For example the 128-bit key **K** is subdivided into eight 16-bit substrings **K1...K8** so if we have a key +**K** = 0123456789ABCDEFEDCBA9876543210 + +we have: + +$$K1 = 0123, K2 = 5678, K3 = 9ABC, \dots, K8 = 3210.$$ + +## 2.4 Presentation of input/output data + +The basic data processed by the **f8** and **f9** algorithms are bit streams. In general in this document the data is presented in hexadecimal format as bytes, thus the last byte shown as part of an input or output data stream may include between 0 and 7 bits that are ignored once the **LENGTH** parameter is taken into account. (The least significant bits of the byte are ignored). + +# 3 KASUMI + +## 3.1 Overview + +The test data sets presented here are for the **KASUMI** block cipher algorithm. + +## 3.2 Format + +Each test set starts by showing the input and output data values. This is followed by a table showing the internal sub-keys that are derived from the 128-bit key. + +For each round the inputs and outputs are shown for the **FL**, **FO** and **FI** functions in the form: + +``` +Round i + FLi( input, KL1i, KL2i )->output + FOi( input )->output + FIi1( input, KIi1 ) -> output + FIi2( input, KIi2 ) -> output + FIi3( input, KIi3 ) -> output +``` + +In addition, for the first two rounds, the internal states of the 7-bit and 9-bit data paths within the **FI** function are shown in the form: + +``` +seven 17-> 0C-> 47-> 72-> 6C-> 21 +nine 19E->05C->04B->1BB->1BF->1CD +``` + +where the first value shown is the value derived from the 16-bit input, and the subsequent values are the changes that occur as the data passes through the function down the respective 7-bit or 9-bit data paths. i.e. The values shown following the input value are: + +result of S-box lookup, +XOR with other half, +XOR with key, +S-box lookup, +XOR with other half. + +## 3.3 Test Set 1 + +Key: 2B D6 45 9F 82 C5 B3 00 95 2C 49 10 48 81 FF 48 +input: EA 02 47 14 AD 5C 4D 84 +output: DF 1F 9B 25 1C 0B F4 5F + +Key schedule: + +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-------------|------|------|------|------|------|------|------|------| +| KL1 | 57AC | 8B3E | 058B | 6601 | 2A59 | 9220 | 9102 | FE91 | +| KL2 | 0B6E | 7EEF | 6BF0 | F388 | 3ED5 | CD58 | 2AF5 | 00F8 | +| KO1 | B3E8 | 58B0 | 6016 | A592 | 2209 | 1029 | E91F | 7AC5 | +| KO2 | 1049 | 8148 | 48FF | D62B | 9F45 | C582 | 00B3 | 2C95 | +| KO3 | 2910 | 1FE9 | C57A | E8B3 | B058 | 1660 | 92A5 | 0922 | +| Kli1 | 6BF0 | F388 | 3ED5 | CD58 | 2AF5 | 00F8 | 0B6E | 7EEF | +| Kli2 | 7EEF | 6BF0 | F388 | 3ED5 | CD58 | 2AF5 | 00F8 | 0B6E | +| Kli3 | CD58 | 2AF5 | 00F8 | 0B6E | 7EEF | 6BF0 | F388 | 3ED5 | + +Input: EA024714 AD5C4D84 + +Round 1 + +FL1 (EA024714, 57AC, 0B6E) ->7CFFC314 +FO1 (7CFFC314) ->58871737 +FI11 (CF17, 6BF0) ->43CD +seven 17-> 0C-> 47-> 72-> 6C-> 21 +nine 19E->05C->04B->1BB->1BF->1CD +FI12 (D35D, 7EEF) ->D85E +seven 5D-> 61-> 3E-> 01-> 32-> 6C +nine 1A6->082->0DF->030->05F->05E +FI13 (A9C9, CD58) ->4FB0 +seven 49-> 63-> 52-> 34-> 17-> 27 +nine 153->1F8->1B1->0E9->184->1B0 + +Round 2 + +FO2 (F5DB5AB3) ->03E715B9 +FI21 (AD6B, F388) ->E2FC +seven 6B-> 31-> 4F-> 36-> 0D-> 71 +nine 15A->015->07E->1F6->0CA->0FC +FI22 (DBFB, 6BF0) ->BBA8 +seven 7B-> 29-> 75-> 40-> 75-> 5D +nine 1B7->127->15C->0AC->1E8->1A8 +FI23 (A7A6, 2AF5) ->165E +seven 26-> 3A-> 73-> 66-> 55-> 0B +nine 14F->06F->049->0BC->038->05E +FL2 (03E715B9, 8B3E, 7EEF) ->FC1913F5 + +Round 3 + +FL3 (161B54E1, 058B, 6BF0) ->E9F55CF7 +FO3 (E9F55CF7) ->F9C9DB3F +FI31 (89E3, 3ED5) ->4C63 +seven 63-> 2D-> 54-> 4B-> 45-> 26 +nine 113->19A->1F9->12C->028->063 +FI32 (1408, F388) ->E95D +seven 08-> 26-> 02-> 7B-> 29-> 74 +nine 028->02C->024->1AC->126->15D +FI33 (D5EE, 00F8) ->22F6 +seven 6E-> 73-> 5B-> 5B-> 67-> 11 +nine 1AB->046->028->0D0->0AD->0F6 + +Round 4 + +FO4 (0C12818C) ->F9C83A1A +FI41 (A980, CD58) ->4D43 +seven 00-> 36-> 4E-> 28-> 65-> 26 +nine 153->1F8->1F8->0A0->16B->143 +FI42 (57A7, 3ED5) ->3507 +seven 27-> 30-> 72-> 6D-> 1D-> 1A +nine 0AF->0E5->0C2->017->16A->107 +FI43 (247C, 0B6E) ->C3D2 + +``` + + seven 7C-> 58-> 54-> 51-> 33-> 61 + nine 048->0F0->08C->1E2->183->1D2 +FL4 (F9C83A1A, 6601, F388) ->0EFDFA1A + +Round 5 +FL5 (18E6AEFB, 2A59, 3ED5) ->6519BE7B +FO5 (6519BE7B) ->D1FAD9E0 +FI51 (4710, 2AF5) ->781A + seven 10-> 37-> 1D-> 08-> 26-> 3C + nine 08E->1BA->1AA->15F->012->01A +FI52 (213E, CD58) ->179B + seven 3E-> 69-> 5C-> 3A-> 10-> 0B + nine 042->18B->1B5->0ED->1A1->19B +FI53 (7639, 7EEF) ->081A + seven 39-> 01-> 73-> 4C-> 1E-> 04 + nine 0EC->1CB->1F2->11D->056->01A + +Round 6 +FO6 (DDE8586C) ->DD0B619B +FI61 (CDC1, 00F8) ->8FF4 + seven 41-> 74-> 51-> 51-> 33-> 47 + nine 19B->0E4->0A5->05D->1A5->1F4 +FI62 (9DEE, 2AF5) ->0A93 + seven 6E-> 73-> 11-> 04-> 16-> 05 + nine 13B->00C->062->097->097->093 +FI63 (C1F8, 6BF0) ->BC90 + seven 78-> 2A-> 42-> 77-> 4E-> 5E + nine 183->090->0E8->118->0E7->090 +FL6 (DD0B619B, 9220, CD58) ->46BE419A + +Round 7 +FL7 (5E58EF61, 9102, 2AF5) ->81B3CF61 +FO7 (81B3CF61) ->C1E3AC33 +FI71 (68AC, 0B6E) ->EBBA + seven 2C-> 68-> 1A-> 1F-> 51-> 75 + nine 0D1->0DE->0F2->19C->1BB->1A4 +FI72 (CFD2, 00F8) ->E526 + seven 52-> 11-> 57-> 57-> 54-> 72 + nine 19F->194->1C6->13E->171->126 +FI73 (B660, F388) ->6DD0 + seven 60-> 66-> 19-> 60-> 66-> 36 + nine 16C->01F->07F->1F7->1B0->1D0 + +Round 8 +FO8 (1C0BF45F) ->68BFA566 +FI81 (66CE, 7EEF) ->DB25 + seven 4E-> 7E-> 0D-> 32-> 48-> 6D + nine 0CD->03D->073->09C->117->125 +FI82 (D8CA, 0B6E) ->47C5 + seven 4A-> 56-> 65-> 60-> 66-> 23 + nine 1B1->179->133->05D->1A5->1C5 +FI83 (2658, 3ED5) ->CDD9 + seven 58-> 5B-> 15-> 0A-> 3F-> 66 + nine 04C->196->1CE->11B->1D3->1D9 +FL8 (68BFA566, FE91, 00F8) ->81477444 +Output: DF1F9B25 1C0BF45F + +``` + +## 3.4 Test Set 2 + +``` + +Key: 8C E3 3E 2C C3 C0 B5 FC 1F 3D E8 A6 DC 66 B1 F3 +input: D3 C5 D5 92 32 7F B1 1C +output: DE 55 19 88 CE B2 F9 B7 + +``` + +Key schedule: + +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-------------|------|------|------|------|------|------|------|------| +| KLI1 | 19C7 | 7C58 | 8781 | 6BF9 | 3E7A | D14D | B8CD | 63E7 | +| KLI2 | 4A6B | 7813 | E1E1 | 523E | AA32 | 83E3 | 8DC0 | 7B4B | +| KOI1 | C587 | 7818 | BF96 | E7A3 | 14DD | 8CDB | 3E76 | 9C71 | +| KOI2 | A6E8 | 66DC | F3B1 | E38C | 2C3E | C0C3 | FCB5 | 3D1F | +| KOI3 | DB8C | 763E | 719C | 87C5 | 1878 | 96BF | A3E7 | DD14 | +| KLI1 | E1E1 | 523E | AA32 | 83E3 | 8DC0 | 7B4B | 4A6B | 7813 | +| KLI2 | 7813 | E1E1 | 523E | AA32 | 83E3 | 8DC0 | 7B4B | 4A6B | +| KLI3 | 83E3 | 8DC0 | 7B4B | 4A6B | 7813 | E1E1 | 523E | AA32 | + +Input: D3C5D592 327FB11C + +Round 1 + +FL1(D3C5D592,19C7,4A6B)->2F32F618 +FO1(2F32F618)->9F6FAB3F +FI11(EAB5,E1E1)->9A6B +seven 35-> 6D-> 78-> 08-> 26-> 4D +nine 1D5->0A0->095->174->063->06B +FI12(50F0,7813)->F31C +seven 70-> 40-> 14-> 28-> 65-> 79 +nine 0A1->124->154->147->134->11C +FI13(B7FF,83E3)->3450 +seven 7F-> 03-> 28-> 69-> 4A-> 1A +nine 16F->054->02B->1C8->039->050 + +Round 2 + +FO2(AD101A23)->5BBD1022 +FI21(D508,523E)->E46B +seven 08-> 26-> 35-> 1C-> 19-> 72 +nine 1AA->11B->113->12D->077->06B +FI22(7CFF,E1E1)->A5F5 +seven 7F-> 03-> 62-> 12-> 27-> 52 +nine 0F9->11E->161->080->1E7->1F5 +FI23(8876,8DC0)->4B9F +seven 76-> 24-> 60-> 26-> 3A-> 25 +nine 110->032->044->184->1B9->19F +FL2(5BBD1022,7C58,7813)->AB9AA012 + +Round 3 + +FL3(785F7580,8781,E1E1)->93987582 +FO3(93987582)->109659D3 +FI31(2C0E,AA32)->D87A +seven 0E-> 7B-> 51-> 04-> 16-> 6C +nine 058->0A4->0AA->098->07E->07A +FI32(8633,523E)->BD6E +seven 33-> 3D-> 0E-> 27-> 30-> 5E +nine 10C->100->133->10D->149->16E +FI33(DC64,7B4B)->4945 +seven 64-> 4B-> 60-> 5D-> 61-> 24 +nine 1B8->1CF->1AB->0E0->118->145 + +Round 4 + +FO4(BD8643F0)->CA56843A +FI41(5A25,83E3)->5709 +seven 25-> 3C-> 44-> 05-> 22-> 2B +nine 0B4->15D->178->09B->10C->109 +FI42(A07C,AA32)->DEAF +seven 7C-> 58-> 25-> 70-> 40-> 6F +nine 140->001->07D->04F->0DF->0AF +FI43(933C,4A6B)->4E6C +seven 3C-> 52-> 41-> 64-> 4B-> 27 +nine 126->1AF->193->1F8->008->06C +FL4(CA56843A,6BF9,523E)->6F2A109A + +Round 5 + +FL5(1775651A,3E7A,AA32)->C08049FA +FO5(C08049FA)->C9D692DD +FI51(D45D,8DC0)->AB91 +seven 5D-> 61-> 2A-> 6C-> 44-> 55 +nine 1A8->016->04B->18B->1FD->191 +FI52(65C4,83E3)->2BBD +seven 44-> 59-> 6B-> 2A-> 28-> 15 +nine 0CB->1F6->1B2->051->197->1BD +FI53(FA13,7813)->5B0B +seven 13-> 72-> 34-> 08-> 26-> 2D +nine 1F4->155->146->155->103->10B + +``` + +Round 6 +FO6(7450D12D)->F6FA9BBE +FI61(F88B,7B4B)->5654 +seven 0B-> 5D-> 14-> 29-> 7F-> 2B +nine 1F1->042->049->102->07D->054 +FI62(11EE,8DC0)->7183 +seven 6E-> 73-> 38-> 7E-> 3B-> 38 +nine 023->025->04B->18B->1FD->183 +FI63(11C6,E1E1)->6D44 +seven 46-> 00-> 63-> 13-> 72-> 36 +nine 023->025->063->182->157->144 +FL6(F6FA9BBE,D14D,83E3)->81253B2F +Round 7 +FL7(96505E35,B8CD,8DC0)->69B97EB4 +FO7(69B97EB4)->BAE2289A +FI71(57CF,4A6B)->47F8 +seven 4F-> 57-> 7D-> 58-> 5B-> 23 +nine 0AF->0E5->0AA->0C1->1A0->1F8 +FI72(8201,7B4B)->83AE +seven 01-> 32-> 20-> 1D-> 6F-> 41 +nine 104->013->012->159->1B3->1AE +FI73(9AAB,523E)->9278 +seven 2B-> 78-> 42-> 6B-> 31-> 49 +nine 135->111->13A->104->013->078 +Round 8 +FO8(CEB2F9B7)->B7FB007B +FI81(52C3,7813)->4A98 +seven 43-> 0B-> 0F-> 33-> 3D-> 25 +nine 0A5->147->104->117->0AB->098 +FI82(C4A8,4A6B)->04D4 +seven 28-> 65-> 6F-> 4A-> 56-> 02 +nine 189->022->00A->061->09E->0D4 +FI83(6E3B,AA32)->B780 +seven 3B-> 07-> 0D-> 58-> 5B-> 5B +nine 0DC->031->00A->038->1D8->180 +FL8(B7FB007B,63E7,7B4B)->480547BD +Output: DE551988 CEB2F9B7 + +``` + +## 3.5 Test Set 3 + +``` + +Key: 40 35 C6 68 0A F8 C6 D1 A8 FF 86 67 B1 71 40 13 +input: 62 A5 40 98 1B A6 F9 B7 +output: 45 92 B0 E7 86 90 F7 1B + +``` + +Key schedule: + +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|-------------|------|------|------|------|------|------|------|------| +| KL1 | 806A | 8CD1 | 15F0 | 8DA3 | 51FF | 0CCF | 62E3 | 8026 | +| KL2 | 8353 | 0B3E | 5623 | 3CFF | C725 | 7203 | 4116 | 830F | +| KO1 | CD18 | 5F01 | DA38 | 1FF5 | CCF0 | 2E36 | 0268 | 06A8 | +| KO2 | 6786 | 71B1 | 1340 | 3540 | 68C6 | F80A | D1C6 | FFA8 | +| KO3 | 362E | 6802 | A806 | 18CD | 015F | 38DA | F51F | F0CC | +| Kli1 | 5623 | 3CFF | C725 | 7203 | 4116 | 830F | 8353 | 0B3E | +| Kli2 | 0B3E | 5623 | 3CFF | C725 | 7203 | 4116 | 830F | 8353 | +| Kli3 | 7203 | 4116 | 830F | 8353 | 0B3E | 5623 | 3CFF | C725 | + +Input: 62A54098 1BA6F9B7 + +``` + +Round 1 +FL1(62A54098,806A,8353)->E51240D8 +FO1(E51240D8)->B2CC3045 +FI11(280A,5623)->CED6 +seven 0A-> 3F-> 40-> 6B-> 31-> 67 +nine 050->1F5->1FF->1DC->0BD->0D6 +FI12(275E,0B3E)->3CC2 +seven 5E-> 1C-> 62-> 67-> 5C-> 1E +nine 04E->120->17E->040->0A5->0C2 +FI13(B820,7203)->8289 +seven 20-> 35-> 0B-> 32-> 48-> 41 +nine 170->19E->1BE->1BD->0BB->089 +Round 2 +FO2(A96AC9F2)->A4AC83B6 +FI21(F66B,3CFF)->0F18 + +``` + +``` + + seven 6B-> 31-> 7F-> 61-> 1F-> 07 + nine 1EC->125->14E->1B1->179->118 + FI22 (B843, 5623) ->6246 + seven 43-> 0B-> 56-> 7D-> 77-> 31 + nine 170->19E->1DD->1FE->03B->046 + FI23 (AEE8, 4116) ->271A + seven 68-> 25-> 01-> 21-> 09-> 13 + nine 15D->14C->124->032->13B->11A + FL2 (A4AC83B6, 8CD1, 0B3E) ->B3D38AB7 + +Round 3 +FL3 (D176CA2F, 15F0, 5623) ->2CA9E8CF +FO3 (2CA9E8CF) ->C1983ADB +FI31 (F691, C725) ->4756 + seven 11-> 71-> 23-> 40-> 75-> 23 + nine 1ED->143->152->077->116->156 + FI32 (FB8F, 3CFF) ->6E01 + seven 0F-> 21-> 1E-> 00-> 36-> 37 + nine 1F7->1B0->1BF->140->001->001 + FI33 (079F, 830F) ->FB43 + seven 1F-> 51-> 43-> 02-> 3E-> 7D + nine 00F->18D->192->09D->141->143 + +Round 4 +FO4 (68F2F329) ->3279F0E1 +FI41 (7707, 7203) ->54CC + seven 07-> 60-> 59-> 60-> 66-> 2A + nine 0EE->03E->039->03A->0AC->0CC + FI42 (C669, C725) ->959C + seven 69-> 4A-> 29-> 4A-> 56-> 4A + nine 18C->08A->0E3->1C6->1D6->19C + FI43 (BF28, 8353) ->C298 + seven 28-> 65-> 63-> 22-> 79-> 61 + nine 17E->12E->106->055->0BA->098 + FL4 (3279F0E1, 8DA3, 3CFF) ->CB86F0A3 + +Round 5 +FL5 (1AF03A8C, 51FF, C725) ->A42B1B6C +FO5 (A42B1B6C) ->A62197C6 +FI51 (68DB, 4116) ->06CF + seven 5B-> 67-> 62-> 42-> 4C-> 03 + nine 0D1->0DE->085->193->08D->0CF + FI52 (73AA, 7203) ->BB82 + seven 2A-> 28-> 6D-> 54-> 5F-> 5D + nine 0E7->1EF->1C5->1C6->1D6->182 + FI53 (1CFC, 0B3E) ->31E7 + seven 7C-> 58-> 2C-> 29-> 7F-> 18 + nine 039->108->174->04A->1CE->1E7 + +Round 6 +FO6 (CED364EF) ->D6DA665D +FI61 (E0E5, 830F) ->A727 + seven 65-> 04-> 00-> 41-> 74-> 53 + nine 1C1->161->104->00B->166->127 + FI62 (9CE5, 4116) ->1512 + seven 65-> 04-> 53-> 73-> 18-> 0A + nine 139->0B2->0D7->1C1->161->112 + FI63 (FB12, 5623) ->B087 + seven 12-> 27-> 7F-> 54-> 5F-> 58 + nine 1F6->0CA->0D8->0FB->0D3->087 + FL6 (D6DA665D, 0CCF, 7203) ->294C6FC9 + +Round 7 +FL7 (33BC5545, 62E3, 4116) ->91921005 +FO7 (91921005) ->484393F4 +FI71 (93FA, 8353) ->82E2 + seven 7A-> 0F-> 1B-> 5A-> 23-> 41 + nine 127->0EE->094->1C7->0B8->0E2 + FI72 (C1C3, 830F) ->DAA4 + seven 43-> 0B-> 58-> 19-> 49-> 6D + nine 183->090->0D3->1DC->0BD->0A4 + FI73 (67F8, 3CFF) ->DBB7 + seven 78-> 2A-> 48-> 56-> 5A-> 6D + nine 0CF->11A->162->19D->1E1->1B7 + +Round 8 +FO8 (8690F71B) ->B971E5E3 +FI81 (8038, 0B3E) ->79B9 + seven 38-> 4D-> 56-> 53-> 05-> 3C + nine 100->023->01B->125->1EA->1B9 + FI82 (08B3, 8353) ->37D3 + seven 33-> 3D-> 73-> 32-> 48-> 1B + +``` + +``` + +nine 011->0FD->0CE->19D->1E1->1D3 +FI83 (7E6E, C725) ->5C92 +seven 6E-> 73-> 46-> 25-> 3C-> 2E +nine 0FC->15B->135->010->0B7->092 +FL8 (B971E5E3, 8026, 830F) ->762EE5A2 +Output: 4592B0E7 8690F71B + +``` + +## 3.6 Test Set 4 + +This test ensures that all entries in the two S-boxes are correct. It does this by ensuring that every S-box entry is used at least once during the running of the test set. + +For a fixed key an initial input value, the algorithm is executed 50 times. The first encryption operates on the given input data. Each subsequent encryption takes the output of the previous encryption as its input data. After 50 operations the output should be as shown below. + +``` + +Iterated test for full S-box coverage +Key = 3A 3B 39 B5 C3 F2 37 6D 69 F7 D5 46 E5 F8 5D 43 +Input = CA 49 C1 C7 57 71 AB 0B + +After 50 repeated encryptions +Output = 73 8B AD 4C 4A 69 08 02 + +``` + +# 4 Confidentiality algorithm *f8* + +## 4.1 Overview + +The test data sets presented here are for the *f8* confidentiality algorithm. No detailed data is presented for the internal states of **KASUMI** as that is covered in Clause 3. + +## 4.2 Format + +Each test set starts by showing the various inputs to the algorithm including the data stream to be encrypted/decrypted. (The length field is in decimal). This is followed by: + +the initial value of the variable **A**. + +the modified key used in the calculation **KASUMI[ A ]CK ⊕ MK** + +the result of the above operation. + +Thereafter four columns of data are shown. + +**Column 1** shows the value of the block counter **BLKCNT**. + +**KASUMI Input** shows the input to the **KASUMI** block cipher. i.e. it is the bit-wise exclusive-or of the data in column 1 with the previous block of keystream and with the modified value of **A**. + +**Keystream** shows the 64-bit output from **KASUMI**. + +**Enc/dec data** shows the modified input data, i.e. it is the bit-wise exclusive-or of the corresponding keystream and the input data to the algorithm. As this is a stream cipher it is purely a matter of context whether the operation is regarded as "encryption" or "decryption". + +## 4.3 Test Set 1 + +Key = 2BD6459F82C5B300952C49104881FF48 + Count = 72A4F20F + Bearer = 0C + Direction = 1 + Length = 798 bits + Plaintext: + 7EC61272743BF161 4726446A6C38CED1 66F6CA76EB543004 4286346CEF130F92 + 922B03450D3A9975 E5BD2EA0EB55AD8E 1B199E3EC4316020 E9A1B285E7627953 + 59B7BDFD39BEF4B2 484583D5AFE082AE E638BF5FD5A60619 3901A08F4AB41AAB + 9B134880 + +Initial A = 72A4F20F64000000 + Key used = 7E8310CAD790E655C0791C451DD4AA1D + Modified A = 34222BC8F7C39416 + Key now = 2BD6459F82C5B300952C49104881FF48 + +| BLKCNT | Kasumi input | Keystream | enc/dec data | +|--------|------------------|-------------------|------------------| +| 0 | 34222BC8F7C39416 | AF24CC029AC39D08 | D1E2DE70EEF86C69 | +| 1 | 9B06E7CA6D00091F | 23DD1041AEECEAE7B | 64FB542BC2D460AA | +| 2 | 17FF3B89592F3A6F | D95CDAD24BC7162F | BFAA10A4A093262B | +| 3 | ED7EF11ABC04823A | 3F9FAA1C80D1DB1B | 7D199E706FC2D489 | +| 4 | 0BBD81D477124F09 | 87782A2C1DC93006 | 1553296910F3A973 | +| 5 | B35A01E4EA0AA415 | E49BAC44F71B868C | 012682E41C4E2B02 | +| 6 | D0B9878C00D8129C | A5398989E10ADFB3 | BE2017B7253BBF93 | +| 7 | 911BA24116C94BA2 | E07FEA9C2C20914A | 09DE5819CB42E819 | +| 8 | D45DC154DBE30554 | 0F437466F0C8A81D | 56F4C99BC9765CAF | +| 9 | 3B615FAE070B3C02 | 1BF4536E2D9900C4 | 53B1D0BB8279826A | +| 10 | 2FD678A6DA5A94D8 | 3D84EA7D3CB3C739 | DBBC5522E915C120 | +| 11 | 09A6C1B5CB705324 | 9F190528BF5C8DA3 | A618A5A7F5E89708 | +| 12 | AB3B2EE0489F19B9 | 082A2D8F25915EE3 | 9339650F | + +## 4.4 Test Set 2 + +Key = EFA8B2229E720C2A7C36EA55E9605695 + Count = E28BCF7B + Bearer = 18 + Direction = 0 + Length = 510 bits + Plaintext: + 10111231E060253A 43FD3F57E37607AB 2827B599B6B1BBDA 37A8ABCC5A8C550D + 1BFB2F494624FB50 367FA36CE3BC68F1 1CF93B1510376B02 130F812A9FA169D8 + +Initial A = E28BCF7BC0000000 + Key used = BAFDE777CB27597F2963BF00BC3503C0 + Modified A = 1C05EA5F90964036 + Key now = EFA8B2229E720C2A7C36EA55E9605695 + +| BLKCNT | Kasumi input | Keystream | enc/dec data | +|--------|------------------|------------------|------------------| +| 0 | 1C05EA5F90964036 | 2DFBDE4DF5E23990 | 3DEACC7C15821CAA | +| 1 | 31FE3412657479A7 | CA13F589782DD4CA | 89EECADE9B5BD361 | +| 2 | D6161FD6E8BB94FE | 63F77DD82BC0B85F | 4BD0C8419D710385 | +| 3 | 7FF29787BB56F86A | EA16F385B597F957 | DDBE5849EF1BAC5A | +| 4 | F61319DA2501B965 | F34A65124C43BA02 | E8B14A5B0A674152 | +| 5 | EF4F8F4DDCD5FA31 | 28CB43675A509B18 | 1EB4E00BB9ECF3E9 | +| 6 | 34CEA938CAC6DB28 | EB3582DFF77639D5 | F7CCB9CAE74152D7 | +| 7 | F730688067E079E4 | E7ED211E294B6934 | F4E2A034B6EA00EC | + +## 4.5 Test Set 3 + +Key = 5ACB1D644C0D51204EA5F1451010D852 + Count = FA556B26 + Bearer = 03 + Direction = 1 + Length = 120 bits + Plaintext: + AD9C441F890B38C4 57A49D421407E8 + +Initial A = FA556B261C000000 + Key used = 0F9E4831195804751BF0A41045458D07 + Modified A = 3E5A6D0A3D1C82A5 + Key now = 5ACB1D644C0D51204EA5F1451010D852 + +| BLK CNT | Kasumi input | Keystream | enc/dec data | +|---------|------------------|------------------|------------------| +| 0 | 3E5A6D0A3D1C82A5 | 365568B78ACD43EC | 9BC92CA803C67B28 | +| 1 | 080F05BDB7D1C148 | F6BED6AC4E0BCD5F | A11A4BEE5A0C25 | + +## 4.6 Test Set 4 + +Key = D3C5D592327FB11C4035C6680AF8C6D1 + Count = 398A59B4 + Bearer = 05 + Direction = 1 + Length = 253 bits + Plaintext: + 981BA6824C1BFB1A B485472029B71D80 8CE33E2CC3C0B5FC 1F3DE8A6DC66B1F0 + +Initial A = 398A59B42C000000 + Key used = 869080C7672AE4491560933D5FAD9384 + Modified A = F04B50A2A852469C + Key now = D3C5D592327FB11C4035C6680AF8C6D1 + +| BLK CNT | Kasumi input | Keystream | enc/dec data | +|---------|------------------|------------------|-------------------| +| 0 | F04B50A2A852469C | C3A2E599FDF270CB | 5BB9431BB1E98BD1 | +| 1 | 33E9B53B55A03656 | AF169C5C14F20EE5 | 1B93DB7C3D451365 | +| 2 | 5F5DCCFEBCA0487B | D558B88E566A95B2 | 59BB86A295AA204E | +| 3 | 2513E82CFE38D32D | D4D61E517976A4E2 | CBE BF6F7A5101512 | + +## 4.7 Test Set 5 + +``` + +Key = 6090EAE04C83706EECBF652BE8E36566 +Count = 72A4F20F +Bearer = 09 +Direction = 0 +Length = 837 bits +Plaintext: +40981BA6824C1BFB 4286B299783DAF44 2C099F7AB0F58D5C 8E46B104F08F01B4 +1AB485472029B71D 36BD1A3D90DC3A41 B46D51672AC4C966 3A2BE063DA4BC8D2 +808CE33E2CCCBFC6 34E1B259060876A0 FBB5A437EBCC8D31 C19E4454318745E3 +987645987A986F2C B0 + +``` + +``` + +Initial A = 72A4F20F48000000 +Key used = 35C5BFB519D6253BB9EA307EBDB63033 +Modified A = 1EDF994571692FEA +Key now = 6090EAE04C83706EECBF652BE8E36566 + +``` + +| BLKCNT | Kasumi input | Keystream | enc/dec data | +|--------|------------------|------------------|------------------| +| 0 | 1EDF994571692FEA | 9D2B7F7BA8E2D9B6 | DDB364DD2AAEC24D | +| 1 | 83F4E63ED98BF65D | BDAFABCECFB60242 | FF291957B78BAD06 | +| 2 | A370328BBEDF2DAA | 16CCE6B720B437E2 | 3AC579CD9041BABE | +| 3 | 08137FF251DD180B | 07BBA858F5F7CA2B | 89FD195C0578CB9F | +| 4 | 1964311D849EE5C5 | C4F692114151651F | DE4217566178D202 | +| 5 | DA290B5430384AF0 | 769D773A5F7A23AD | 40206D07CFA619EC | +| 6 | 6842EE7F2E130C41 | B1F232366E9D3576 | 059F63514459FC10 | +| 7 | AF2DAB731FF41A9B | EE0629F0941D2312 | D42DC9934E56EBC0 | +| 8 | F0D9B0B5E5740CF0 | 4B4AEE73013DCBB1 | CBC60D4D2DF17477 | +| 9 | 559577367054E452 | 785C7F04A2AB2691 | 4CBDCD5DA4A35031 | +| 10 | 6683E641D3C20971 | 81CAB6D67F58FCC9 | 7A7F12E1949471F8 | +| 11 | 9F152F930E31D328 | 630BB626D7088592 | A295F272E68FC071 | +| 12 | 7DD42F63A661AA74 | C1C6381657BE8B75 | 59B07D8E2D26E459 | +| 13 | DF19A15326D7A492 | 2E1EA0BF8D97DA88 | 9E | + +# 5 Integrity algorithm f9 + +## 5.1 Overview + +The test data sets presented here are for the *f9* integrity algorithm. No detailed data is presented for the internal states of **KASUMI** as that is covered in Clause 3. + +## 5.2 Format + +The test data set shows the input values to the algorithm. + +Following this it shows four columns of data; input, **KASUMI** input, **KASUMI** output and the cumulative exclusive-OR where: + +**Input** is the plain text input block that is being hashed. It commences with the value **COUNT || FRESH** and is followed by the **MESSAGE**. The final input block includes the **DIRECTION** bit and the padding. + +**KASUMI Input** is the input value to the block cipher. In the first line this is **COUNT || FRESH**, subsequently it is the XOR of the plain text block and the previous output from **KASUMI**. + +**KASUMI Output** is the output of the block cipher + +**Accumulated XOR** is the XOR of all the output of all the **KASUMI** operations performed up to that point. + +Finally the modified key is shown along with the input and output data from the last application of **KASUMI**. + +## 5.3 Test Set 1 + +Key = 2BD6459F82C5B300952C49104881FF48 + Count = 38A6F056 + Fresh = 05D2EC49 + Direction = 0 + Length = 189 bits + Message: + 6B227737296F393C 8079353EDC87E2E8 05D2EC49A4F2D8E0 + +| Input | Kasumi input | Kasumi Output | Accumulated XOR | +|------------------|------------------|------------------|------------------| +| 38A6F05605D2EC49 | 38A6F05605D2EC49 | 89E0A6D036C17090 | 89E0A6D036C17090 | +| 6B227737296F393C | E2C2D1E71FAE49AC | 45C16C0142460205 | CC21CAD174877295 | +| 8079353EDC87E2E8 | C5B8593F9EC1E0ED | E24CFA7D8471E4DD | 2E6D30ACF0F69648 | +| 05D2EC49A4F2D8E2 | E79E163420833C3F | DFD3DCB9499275BA | F1BEEC15B964E3F2 | + +New Key: 817CEF35286F19AA3F86E3BAE22B55E2 + final step: F1BEEC15B964E3F2 F63BD72C702EBC7A + +MAC-I: F63BD72C + +## 5.4 Test Set 2 + +Key = D42F682428201CAFCD9F97945E6DE7B7 + Count = 3EDC87E2 + Fresh = A4F2D8E2 + Direction = 1 + Length = 254 bits + Message: + B5924384328A4AE0 0B737109F8B6C8DD 2B4DB63DD533981C EB19AAD52A5B2BC0 + +| Input | Kasumi input | Kasumi Output | Accumulated XOR | +|------------------|------------------|------------------|------------------| +| 3EDC87E2A4F2D8E2 | 3EDC87E2A4F2D8E2 | 3541B47339DD4168 | 3541B47339DD4168 | +| B5924384328A4AE0 | 80D3F7F70B570B88 | 52EC81194ECEDDA0 | 67AD356A77139CC8 | +| 0B737109F8B6C8DD | 599FF010B678157D | 792BFE1F07A1A8B0 | 1E86CB7570B23478 | +| 2B4DB63DD533981C | 52664822D29230AC | C92F7E2C38D22B6D | D7A9B55948601F15 | +| EB19AAD52A5B2BC3 | 2236D4F9128900AE | 4C2BEF9C82233403 | 9B825AC5CA432B16 | + +New Key: 7E85C28E828AB60567353D3EF4C74D1D + final step: 9B825AC5CA432B16 A9DAF1FF12F71DE7 + +MAC-I: A9DAF1FF + +## 5.5 Test Set 3 + +Key = FDB9CFDF28936CC483A31869D81B8FAB + Count = 36AF6144 + Fresh = 9838F03A + Direction = 1 + Length = 319 bits + Message: + 5932BC0ACE2B0ABA 33D8AC188AC54F34 6FAD10BF9DEE2920 B43BD0C53A915CB7 + DF6CAA72053ABFF2 + +| Input | Kasumi input | Kasumi Output | Accumulated XOR | +|------------------|------------------|------------------|------------------| +| 36AF61449838F03A | 36AF61449838F03A | DDA7EAA292B010EC | DDA7EAA292B010EC | +| 5932BC0ACE2B0ABA | 849556A85C9B1A56 | 3D65F1EB61544622 | E0C21B49F3E456CE | +| 33D8AC188AC54F34 | 0EBD5DF3EB910916 | 1D62D61E5ED97431 | FDA0CD57AD3D22FF | +| 6FAD10BF9DEE2920 | 72CFC6A1C3375D11 | 14C968BAC4F8A2A5 | E969A5ED69C5805A | +| B43BD0C53A915CB7 | A0F2B87FFE69FE12 | 6D0132521C61A552 | 846897BF75A42508 | +| DF6CAA72053ABFF2 | B26D9820195B1AA1 | BF04729B5C03EA98 | 3B6CE52429A7CF90 | +| 8000000000000000 | 3F04729B5C03EA98 | 8B0C8BE27C74D17F | B0606EC655D31EEF | + +New Key: 571365758239C66E2909B2C372B12501 + final step: B0606EC655D31EEF 1537D316633A8831 + +MAC-I: 1537D316 + +## 5.6 Test Set 4 + +Key = C736C6AAB22BFFF91E2698D2E22AD57E + Count = 14793E41 + Fresh = 0397E8FD + Direction = 1 + Length = 384 bits + Message:: + D0A7D463DF9FB2B2 78833FA02E235AA1 72BD970C1473E129 07FB648B6599AAA0 + B24A038665422B20 A499276A50427009 + +| Input | Kasumi input | Kasumi Output | Accumulated XOR | +|------------------|------------------|------------------|------------------| +| 14793E410397E8FD | 14793E410397E8FD | FB6A5FB59EA91B57 | FB6A5FB59EA91B57 | +| D0A7D463DF9FB2B2 | 2BCD8BD64136A9E5 | DDF60F296850AE54 | 269C509CF6F9B503 | +| 78833FA02E235AA1 | A57530894673F4F5 | FAB7664A7F2447E7 | DC2B36D689DDF2E4 | +| 72BD970C1473E129 | 880AF1466B57A6CE | E6443647E1289007 | 3A6F009168F562E3 | +| 07FB648B6599AAA0 | E1BF52CC84B13AA7 | DA29900832EA4C7C | E04690995A1F2E9F | +| B24A038665422B20 | 6863938E57A8675C | 74C2F5B8172E361D | 948465214D311882 | +| A499276A50427009 | D05BD2D2476C4614 | 79AA12C36369E686 | ED2E77E22E58FE04 | +| C000000000000000 | B9AA12C36369E686 | A464F43DEE74E0C7 | 494A83DFC02C1EC3 | + +New Key: 6D9C6C0018815553B48C327848807FD4 + final step: 494A83DFC02C1EC3 DD7DFADDD68D1EC1 + +MAC-I: DD7DFADD + +## 5.7 Test Set 5 + +Key = F4EBEC69E73EAF2EB2CF6AF4B3120FFD + Count = 296F393C + Fresh = 6B227737 + Direction = 1 + Length = 1000 bits + Message:: + 10BFFF839E0C7165 8DBB2D1707E14572 4F41C16F48BF403C 3B18E38FD5D1663B + 6F6D900193E3CEA8 BB4F1B4F5BE82203 2232A78D7D75238D 5E6DAECD3B4322CF + 59BC7EA84AB18811 B5BFB7BC553F4FE4 4478CE287A148799 90D18D12CA79D2C8 + 55149021CD5CE8CA 0371CA04FCC143E 3D7CFEE94585B588 5CAC46068B + +| Input | Kasumi input | Kasumi Output | Accumulated XOR | +|------------------|-------------------|------------------|------------------| +| 296F393C6B227737 | 296F393C6B227737 | 47F6AA9B15F7A617 | 47F6AA9B15F7A617 | +| 10BFFF839E0C7165 | 574955188BFBFD772 | 6C7C71FDE9AA2B8D | 2B8ADB66FC5D8D9A | +| 8DBB2D1707E14572 | E1C75CEAEE4B6EFF | 690286906D3EBABE | 42885DF691633724 | +| 4F41C16F48BF403C | 264347FF2581FA82 | 942B65C8198AB936 | D6A3383E88E98E12 | +| 3B18E38FD5D1663B | AF338647CC5BDF0D | 5052A81A1A059BB0 | 86F1902492EC15A2 | +| 6F6D900193E3CEA8 | 3F3F381B89E65518 | E40F45A22B41B05F | 62FED586B9ADA5FD | +| BB4F1B4F5BE82203 | 5F405EED70A9925C | 91C00F497A1A8199 | F33EDACFC3B72464 | +| 2232A78D7D75238D | B3F2A8C4076FA214 | DEF053FB4EB23FEA | 2DCE89348D051B8E | +| 5E6DAECD3B4322CF | 809DFD3675F11D25 | BEC94AAFFE3723CC | 9307C39B73323842 | +| 59BC7EA84AB18811 | E7753407B486ABDD | 9BD4CB606985127E | 08D308FB1AB72A3C | +| B5BFB7BC553F4FE4 | 2E6B7CDC3CBA5D9A | D5D5A8EBCD518F4E | DD06A015D7E6A572 | +| 4478CE287A148799 | 91AD66C6B74508D7 | 17B9203FC35C9882 | CABF802A14BA3DF0 | +| 90D18D12CA79D2C8 | 8768AD2D09254A4A | 206A3693096F30E7 | EAD5B6B91DD50D17 | +| 55149021CD5CE8CA | 757EA6B2C433D82D | CF23D21C256066E9 | 25F664A538B56BFE | +| 0371CA04FCC143E | CC521818D9AE72D7 | C2D40AFABC92E2FE | E7226E5F84278900 | +| 3D7CFEE94585B588 | FFA8F413F9175776 | 699D61BDD036A7E5 | 8EBF0FE254112EE5 | +| 5CAC46068BC00000 | 353127BB5BF6A7E5 | E3D8AE061C3A3C87 | 6D67A1E4482B1262 | + +New Key: 5E4146C34D9405841865C05E19B8A557 + final step: 6D67A1E4482B1262 C383839D93FFC6D1 + +MAC-I: C383839D + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|--------------------------------------------------------------------------------------------------------------------------------|-----------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12-1999 | - | - | - | - | ETSI SAGE Publication (restricted) | - | SAGE v1.0 | +| 09-2000 | SA_07 | | | | Approved by TSG SA and placed under change control | SAGE v1.0 | 3.1.0 | +| 07-2001 | - | - | - | - | Word version received: Re-formatted into 3GPP TS format (MCC)
No technical change from version 3.1.0. | 3.1.0 | 3.1.1 | +| 08-2001 | - | - | - | - | Addition of Mitsubishi IPR information in Foreword and correction of reference titles. No technical change from version 3.1.0. | 3.1.1 | 3.1.2 | +| 08-2001 | - | - | - | - | Release 4 version created. | 3.1.2 | 4.0.0 | +| 06-2002 | - | - | - | - | Release 5 version created. | 4.0.0 | 5.0.0 | +| 12-2004 | SP-26 | - | - | - | Release 6 version created. | 5.0.0 | 6.0.0 | +| 06-2007 | SP-36 | - | - | - | Release 7 version created. | 6.0.0 | 7.0.0 | +| 12-2008 | SP-42 | - | - | - | Release 8 version created | 7.0.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Release 9 version created | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35204/raw.md b/marked/Rel-16/35_series/35204/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f498783c5c693610ff485676663a18d46deddb90 --- /dev/null +++ b/marked/Rel-16/35_series/35204/raw.md @@ -0,0 +1,526 @@ + + + + + + +# --- Contents + +| | | +|----------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 0 Scope..... | 5 | +| 1 Outline of the design conformance test data..... | 5 | +| 1.1 References ..... | 5 | +| 2 Introductory information..... | 6 | +| 2.1 Introduction ..... | 6 | +| 2.2 Radix ..... | 6 | +| 2.3 Bit/Byte ordering..... | 6 | +| 2.4 Presentation of input/output data..... | 6 | +| 2.5 Coverage..... | 6 | +| 3 Confidentiality algorithm $f_8$ ..... | 6 | +| 3.1 Overview ..... | 6 | +| 3.2 Format ..... | 6 | +| 3.3 Test Set 1..... | 7 | +| 3.3.1 Binary Representation ..... | 7 | +| 3.3.2 Hexadecimal Representation ..... | 7 | +| 3.4 Test Set 2..... | 8 | +| 3.5 Test Set 3..... | 8 | +| 3.6 Test Set 4..... | 8 | +| 3.7 Test Set 5..... | 9 | +| 3.8 Test Set 6..... | 9 | +| 4 Integrity algorithm $f_9$ ..... | 9 | +| 4.1 Overview ..... | 9 | +| 4.2 Test Set 1..... | 10 | +| 4.2.1 Binary Representation ..... | 10 | +| 4.2.2 Hexadecimal Representation ..... | 10 | +| 4.3 Test Set 2..... | 10 | +| 4.4 Test Set 3..... | 11 | +| 4.5 Test Set 4..... | 11 | +| 4.6 Test Set 5..... | 11 | +| 4.7 Test Set 6..... | 11 | +| Annex A (informative): Change history..... | 12 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The 3GPP Confidentiality and Integrity Algorithms f8 & f9 have been developed through the collaborative efforts of the European Telecommunications Standards Institute (ETSI), the Association of Radio Industries and Businesses (ARIB), the Telecommunications Technology Association (TTA), the T1 Committee. + +The f8 & f9 Algorithms Specifications may be used only for the development and operation of 3G Mobile Communications and services. Every Beneficiary must sign a Restricted Usage Undertaking with the Custodian and demonstrate that he fulfils the approval criteria specified in the Restricted Usage Undertaking. + +Furthermore, Mitsubishi Electric Corporation holds essential patents on the Algorithms. The Beneficiary must get a separate IPR License Agreement from Mitsubishi Electronic Corporation Japan. + +For details of licensing procedures, contact ETSI, ARIB, TTA or T1. + +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 + +This specification has been prepared by the 3GPP Task Force, and gives black-box test data for the algorithm set. The test data has been selected to give a high degree of confidence that the implementation is correct. However, no claim is made that conformance with this test data guarantees a correct implementation. + +This document is the last of four, which between them form the entire specification of the 3GPP Confidentiality and Integrity Algorithms: + +- 3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 Specification". +- 3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification". +- 3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data". +- **3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data".** + +This document is purely informative. The normative part of the specification of the f8 (confidentiality) and the f9 (integrity) algorithms is in the main body of Document 1. The normative part of the specification of KASUMI is found in document 2. + +# --- 0 Scope + +This specification gives black-box test data for the algorithm set. The test data has been selected to give a high degree of confidence that the implementation is correct. However, no claim is made that conformance with this test data guarantees a correct implementation. + +# --- 1 Outline of the design conformance test data + +Section 2 introduces the algorithms and describes the notation used in the subsequent sections. + +Section 3 provides test data for the Confidentiality Algorithm *f8*. + +Section 4 provides test data for the Integrity Algorithm *f9*. + +## 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] 3GPP TS 33.102 version 3.2.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 version 3.1.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.201: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 Specification". +- [4] 3GPP TS 35.202: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI Specification". +- [5] 3GPP TS 35.203: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' Test Data". +- [6] 3GPP TS 35.204: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design Conformance Test Data". +- [7] ISO/IEC 9797-1:1999: "Information technology – Security techniques – Message Authentication Codes (MACs)". + +# --- 2 Introductory information + +## 2.1 Introduction + +Within the security architecture of the 3GPP system there are two standardised algorithms; a confidentiality algorithm *f8*, and an integrity algorithm *f9*. These algorithms are specified in a companion document [3]. + +This document provides sets of input/output test data for 'black box' testing of physical realisations of the *f8* and *f9* algorithms. + +## 2.2 Radix + +Unless stated otherwise, all test data values presented in this document are in hexadecimal. + +## 2.3 Bit/Byte ordering + +All data variables in this specification are presented with the most significant bit (or byte) on the left hand side and the least significant bit (or byte) on the right hand side. + +## 2.4 Presentation of input/output data + +The basic data processed by the *f8* and *f9* algorithms are bit streams. In general in this document the data is presented in hexadecimal format as bytes, thus the last byte shown as part of an input or output data stream may include between 0 and 7 bits that are ignored once the **LENGTH** parameter is taken into account. (The least significant bits of the byte are ignored). + +## 2.5 Coverage + +For each of the algorithms the test data have been selected such that, provided the entire set of tests is run: + +- Each key bit will have been in both the '1' and the '0' states. +- Each bit of the initialisation fields (COUNT, FRESH, BEARER, DIRECTION) will have been in both the '1' and the '0' states. +- Every entry in the internal S-boxes will have been used. + +# 3 Confidentiality algorithm *f8* + +## 3.1 Overview + +The test data sets presented here are for the *f8* confidentiality algorithm. + +## 3.2 Format + +Each test set shows the various inputs to the algorithm including the plain text data stream to be encrypted/decrypted. (The length field is in decimal). + +The fields are: + +Key = CK[0]...CK[127] + Count = COUNT[0]...COUNT[31] + Bearer = BEARER[0]...BEARER[3] + Direction = DIRECTION[0] + Length = Length of data in **decimal** + Plaintext = PT[0] PT[1] ..... PT[Length-1] + +This is followed by the modified input data, i.e. it is the bit-wise exclusive-or of the corresponding keystream and the input data to the algorithm. + +Ciphertext = CT[0] CT[1]....CT[Length-1] + +As this is a stream cipher it is purely a matter of context whether the operation is regarded as "encryption" or "decryption". For the purposes of this document we regard the input as Plaintext and the output as Ciphertext. + +The first test set is shown twice, once in binary format, once in hexadecimal format. This is to explicitly show the relationship between the binary data and the hexadecimal presentation. + +The remainder of the test sets are presented in hexadecimal format only. + +## 3.3 Test Set 1 + +### 3.3.1 Binary Representation + +Key= 1101001111000101110101011001001000110010011111111011000100011100 +0100000000110101110001100110100000001010111110001100011011010001 + +Count = 00111001100010100101100110110100 + +Bearer = 10101 + +Direction = 1 + +Length = 253 bits + +Plaintext: + +100110000001101110100110100000010010011000000110111111101100011010 +10110100100001010100011100100000001010011011011100011101100000000 +1000110011100011001111100010110011000011110000001011010111111100 +00011111001111011110100010100110110111000110011010110001111110 + +Ciphertext: + +1100101000001010011000001011010000101001100111100110100101010100 +110110111111011101101000011011100100011011101000100000110010000 +1101110010000001101100000111010000000100010010000001001110110101 +00001010101100011111111100100011001011001011110111010001100111 + +### 3.3.2 Hexadecimal Representation + +Key = D3C5D592327FB11C4035C6680AF8C6D1 + +Count = 398A59B4 + +Bearer = 15 + +Direction = 1 + +Length = 253 bits + +Plaintext: + +981BA6824C1BFB1A B485472029B71D80 8CE33E2CC3C0B5FC 1F3DE8A6DC66B1F0 + +Ciphertext: + +CA0A60B4299E6954 DBF7686E46F44190 DC81B074044813B5 0AB1FE46597BA338 + +## 3.4 Test Set 2 + +Key = 2BD6459F82C440E0952C49104805FF48 + +Count = C675A64B + +Bearer = 0C + +Direction = 1 + +Length = 798 bits + +Plaintext: + +7EC61272743BF161 4726446A6C38CED1 66F6CA76EB543004 4286346CEF130F92 +922B03450D3A9975 E5BD2EA0EB55AD8E 1B199E3EC4316020 E9A1B285E7627953 +59B7BDFD39BEF4B2 484583D5AFE082AE E638BF5FD5A60619 3901A08F4AB41AAB +9B134880 + +Cipher text: + +1061793DAAACBE40 C9431E292B7FF494 96DB0D31CE24710C 01ACFF1B2C441FA9 +3BB3BD65DE18027A 14CCA571A42E8B12 74AE30AC411AB6AF D88F924E65F9812D +FA80EF8E9A7EA753 391D09F480D9147C B39C23A1ACB9AC9B 2A6B4709F7E6DD84 +D8FA59A4 + +## 3.5 Test Set 3 + +``` + +Key = 0A8B6BD8D9B08B08D64E32D1817777FB +Count = 544D49CD +Bearer = 04 +Direction = 0 +Length = 310 bits +Plaintext: +FD40A41D370A1F65 745095687D47BA1D 36D2349E23F64439 2C8EA9C49D40C132 +71AFF264D0F248 + +Cipher text: +22B707A481F264BE 691994C2A201354D 5741A2E6B4624EE9 DF30D8D94535165B +D439223EBBD074 + +``` + +## 3.6 Test Set 4 + +``` + +Key = AA1F95AEA533BCB32EB63BF52D8F831A +Count = 72D8C671 +Bearer = 10 +Direction = 1 +Length = 1022 bits +Plaintext: +FB1B96C5C8BADFB2 E8E8EDFDE78E57F2 AD81E74103FC430A 534DCC37AFCCE70E +1517BB06F27219DA E49022DDC47A068D E4C9496A951A6B09 EDBDC864C7ADBD74 +0AC50C022F3082BA FD22D78197C5D508 B977BCA13F32E652 E74BA728576077CE +628C535E87DC6077 BA07D29068590C8C B5F1088E082CFA0E C961302D69CF3D44 + +Ciphertext: +5C6FD2D34BE8B0F5 212600BD758881F7 6C4F11A5C3D42028 A9A029F2E0630454 +829AA0A69D58D023 02E8DB3D6E9FF350 09B3595984BEB400 31271BF78727270B +9608520036125AD6 8A28213513CBA08C 7BB9EA966C0713FD 2DFFE2BADC6287CF +79B244B7236124FB 51B863684C4D89D1 940541D356809022 12081FE694DC4594 + +``` + +## 3.7 Test Set 5 + +``` + +Key = 9618AE46891F86578EEBE90EF7A1202E +Count = C675A64B +Bearer = 0C +Direction = 1 +Length = 1245 bits +Plaintext: +8DAA17B1AE050529 C6827F28C0EF6A12 42E93F8B314FB18A 77F790AE049FEDD6 +12267FECAEFC4501 74D76D9F9AA7755A 30CD90A9A5874BF4 8EAF70EEA3A62A25 +0A8B6BD8D9B08B08 D64E32D1817777FB 544D49CD49720E21 9DBF8BBED33904E1 +FD40A41D370A1F65 745095687D47BA1D 36D2349E23F64439 2C8EA9C49D40C132 +71AFF264D0F24841 D6465F0996FF84E6 5FC517C53EFC3363 C38492A8 + +Ciphertext: +AAF8E8B349FBABB9 5C621DE6FB516744 6054AE7CFA946F99 6C26005345A1A2AF +44EEA688B759FFE3 E22D6E17BD9E7079 CC54E8D492DBFDE7 9E84043849821A24 +7A67D3509BA16B49 15FDDDD638E252F4 371E471D1B39B415 8B47F14D037BBD28 +37804134AD493BFC 140E437F5EBF9C29 D5D8A5816F926AA2 76E9A743A62141AD +EB653BD2963C9F54 1F5E1334B77592B1 ADED443672282801 32A747D8 + +``` + +## 3.8 Test Set 6 + +``` + +Key = 54F4E2E04C83786EEC8FB5ABE8E36566 +Count = ACA4F50F +Bearer = 0B +Direction = 0 +Length = 2837 bits +Plaintext: +40981BA6824C1BFB 4286B299783DAF44 2C099F7AB0F58D5C 8E46B104F08F01B4 +1AB485472029B71D 36BD1A3D90DC3A41 B46D51672AC4C966 3A2BE063DA4BC8D2 +808CE33E2CCCBFC6 34E1B259060876A0 FBB5A437EBCC8D31 C19E4454318745E3 +FA16BB11ADAE2488 79FE52DB2543E53C F445D3D828CE0BF5 C560593D97278A59 +762DD0C2C9CD68D4 496A792508614014 B13B6AA51128C18C D6A90B87978C2FF1 +CABE7D9F898A411B FDB84F68F6727B14 99CDD30DF0443AB4 A66653330BCBA110 +5E4CEC034C73E605 B4310EAAADCDFD5B0 CA27FFD89D144DF4 792759427C9CC1F8 +CD8C87202364B8A6 87954CB05A8D4E2D 99E73DB160DEB180 AD0841E96741A5D5 +9FE4189F15420026 FE4CD12104932FB3 8F735340438AAF7E CA6FD5CFD3A195CE +5ABE65272AF607AD A1BE65A6B4C9C069 3234092C4D018F17 56C6DB9DC8A6D80B +888138616B681262 F954D0E771174878 0D92291D86299972 DB741CFA4F37B8B5 +B09550 + +``` + +``` + +Ciphertext: +BFB39672186E62B7 7FB39F9278A8AEA6 0468E05A2BB57E8B 6D6AA1B05AE83147 +679207F035194553 DDF973E830C3E249 4EF6C9449FDC0735 1F8B453EEE70001D +8566B0F646394892 D443F394DA13DAC2 05D84B2628191A0C 574E974507A9A9F3 +408FCA9EC4A38869 1C513CFED22357B2 F7742FB8D5CE550E 03CAA9CFFF54100 +19590CA8D25F9AFD 5BB00FB081EAD4BD A0FAC5DC78F79771 8B6AE21BF9D0C443 +B1B7F1945AEA83FA C3B2208281B30883 E590196D6499B431 7EA97E080830C204 +6AFA95A3E9DB5C47 3CD054D2E0A7F080 CB5967C709DE78EC 8435CAE9B3617655 +69576AA958CE5909 3ACB8A5F72096A7F E671C3717B1B514A 0AE7D7792E44F17C +48E7BAE30D5BB21D CABD217CB55B899F A7D8EA0557F672E4 36BE18350D58C65F +B6D7530E3B85FA63 1C65C3402A87D98F 3B6FB971FCCB1AF1 A6592DF2CCFE6893 +A41F43ABEFD48D70 CCC9C21DDF02792B 8EE8A77988CDC317 1046C515401ABB13 +2261B0 + +``` + +# 4 Integrity algorithm f9 + +## 4.1 Overview + +The test data sets presented here are for the *f9* integrity algorithm. + +Each test set shows the various inputs to the algorithm including the plain text data stream to be 'MAC'd. The length field is in decimal. + +The fields are: + +``` + +Key = IK[0]...IK[127] +Count = COUNT-I[0]...COUNT-I[31] +Fresh = FRESH[0]...FRESH[31] +Direction = DIRECTION[0] +Length = Length of data in decimal +Message = MESSAGE[0]...MESSAGE[Length-1] + +``` + +This is followed by the calculated value for MAC-I. + +``` + +Output = MAC-I[0]...MAC-I[31] + +``` + +The first test set is shown twice, once in binary format, once in hexadecimal format. This is to explicitly show the relationship between the binary data and the hexadecimal presentation. + +The remainder of the test sets are presented in hexadecimal format only. + +## 4.2 Test Set 1 + +### 4.2.1 Binary Representation + +``` + +Key= 0010101111010110010001011001111110000010110001011011001100000000 + 10010101001011000100100100010000001001000100000001111111101001000 + +Count = 0011100001010011011110000001010110 +Fresh = 101110001010111011111010101001 +Direction = 0 +Length = 88 bits +Message: +0011001100110010001101000110001001100011001110001100001100001 +001101110011010001111001 + +Output: 010001101110000000000110101001011 + +``` + +### 4.2.2 Hexadecimal Representation + +``` + +Key = 2BD6459F82C5B300952C49104881FF48 +Count = 38A6F056 +Fresh = B8AEFDA9 +Direction = 0 +Length = 88 bits +Message: +3332346263393861 373479 + +Output: 46E00D4B + +``` + +## 4.3 Test Set 2 + +``` + +Key = 7E5E94431E11D73828D739CC6CED4573 +Count = 36AF6144 +Fresh = 9838F03A +Direction = 1 +Length = 254 bits +Message: +B3D3C9170A4E1632 F60F861013D22D84 B726B6A278D802D1 EEAF1321BA5929DC + +Output: 2BEEF3AC + +``` + +## 4.4 Test Set 3 + +``` + +Key = D3419BE821087ACD02123A9248033359 +Count = C7590EA9 +Fresh = 57D5DF7D +Direction = 0 +Length = 511 bits +Message: +BBB057038809496B CFF86D6FBC8CE5B1 35A06B166054F2D5 65BE8ACE75DC851E +0BCDD8F07141C495 872FB5D8C0C66A8B 6DA556663E4E4612 05D84580BEE5BC7E + +Output: 02158170 + +``` + +## 4.5 Test Set 4 + +``` + +Key = 83FD23A244A74CF358DA3019F1722635 +Count = 36AF6144 +Fresh = 4F302AD2 +Direction = 1 +Length = 768 bits +Message: +35C68716633C66FB 750C266865D53C11 EA05B1E9FA49C839 8D48E1EFA5909D39 +47902837F5AE96D5 A05BC8D61CA8DBEF 1B13A4B4ABFE4FB1 006045B674BB5472 +9304C382BE53A5AF 05556176F6EAA2EF 1D05E4B083181EE6 74CDA5A485F74D7A + +Output: 95AE41BA + +``` + +## 4.6 Test Set 5 + +Key = 6832A65CFF4473621EBDD4BA26A921FE +Count = 36AF6144 +Fresh = 9838F03A +Direction = 0 +Length = 383 bits +Message: +D3C5383962682071 7765667620323837 636240981BA6824C 1BFB1AB485472029 +B71D808CE33E2CC3 C0B5FC1F3DE8A6DC +Output: 8B2D570F + +## 4.7 Test Set 6 + +Key = 5D0A80D8134AE19677824B671E838AF4 +Count = 7827FAB2 +Fresh = A56C6CA2 +Direction = 1 +Length = 2558 bits +Message: +70DEDF2DC42C5CBD 3A96F8A0B11418B3 608D5733604A2CD3 6AABC70CE3193BB5 +153BE2D3C06DFDB2 D16E9C357158BE6A 41D6B861E491DB3F BFEB518EFCF048D7 +D58953730FF30C9E C470FFCD663DC342 01C36ADDC0111C35 B38AFEE7CFDB582E +3731F8B4BAA8D1A8 9C06E81199A97162 27BE344EFCB436DD D0F096C064C3B5E2 +C399993FC77394F9 E09720A811850EF2 3B2EE05D9E617360 9D86E1C0C18EA51A +012A00BB413B9CB8 188A703CD6BAE31C C67B34B1B00019E6 A2B2A690F02671FE +7C9EF8DEC0094E53 3763478D58D2C5F5 B827A0148C5948A9 6931ACF84F465A64 +E62CE74007E991E3 7EA823FA0FB21923 B79905B733B631E6 C7D6860A3831AC35 +1A9C730C52FF72D9 D308EEDBAB21FDE1 43A0EA17E23EDC1F 74CBB3638A2033AA +A15464EAA733385D BBE6FD73509B857 E6A419DCA1D8907A F977FBAC4DFA35EC +Output: 3AE4BFF3 + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|----------|----|-----|--------------------------------------------------------------------------------------------------------------------------------|-----------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12-1999 | - | - | - | - | ETSI SAGE Publication (restricted) | - | SAGE v1.0 | +| 09-2000 | SA_07 | | | | Approved by TSG SA and placed under change control | SAGE v1.0 | 3.1.0 | +| 07-2001 | - | - | - | - | Word version received: Re-formatted into 3GPP TS format (MCC)
No technical change from version 3.1.0. | 3.1.0 | 3.1.1 | +| 08-2001 | - | - | - | - | Addition of Mitsubishi IPR information in Foreword and correction of reference titles. No technical change from version 3.1.0. | 3.1.1 | 3.1.2 | +| 08-2001 | - | - | - | - | Release 4 version created. | 3.1.2 | 4.0.0 | +| 06-2002 | - | - | - | - | Release 5 version created. | 4.0.0 | 5.0.0 | +| 12-2004 | - | - | - | - | Release 6 version created. | 5.0.0 | 6.0.0 | +| 06-2007 | - | - | - | - | Release 7 version created. | 6.0.0 | 7.0.0 | +| 12-2008 | - | - | - | - | Release 8 version created | 7.0.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Release 9 version created. | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35205/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/35_series/35205/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..726ed320922fa1a6897916de0479e330dda0e2a1 --- /dev/null +++ b/marked/Rel-16/35_series/35205/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38e69343e4ea61e7ba9635c7db76539007a5faf6ec504e7f88924c190805665b +size 23946 diff --git a/marked/Rel-16/35_series/35205/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Rel-16/35_series/35205/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e2c7baa985890c3f7508c8434abb21bc6baaad0 --- /dev/null +++ b/marked/Rel-16/35_series/35205/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56e0ba46a39a3afb018830087b979175bf7bf0450848f005af5f53bccdae0b65 +size 29791 diff --git a/marked/Rel-16/35_series/35205/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/35_series/35205/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..769ebcfbb9699ff38dd80b7f3569a4385d2bb5e1 --- /dev/null +++ b/marked/Rel-16/35_series/35205/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fb629f45762814588f172d57cb49e33c5e896f939a4c17525d52d52879ed934 +size 68729 diff --git a/marked/Rel-16/35_series/35205/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-16/35_series/35205/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa98d19b6284c095457518e1d98ef761fed9b410 --- /dev/null +++ b/marked/Rel-16/35_series/35205/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ec09d41594469417ecfaabb4d69824c18ef56d7678b51153032eba7df81d084 +size 27311 diff --git a/marked/Rel-16/35_series/35205/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Rel-16/35_series/35205/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..085f341601d83c7a7b7a344207ee2c1e50764acf --- /dev/null +++ b/marked/Rel-16/35_series/35205/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c375dd01a71b3b630ab1b572225d39ff6e54d06987bed6b75ed00f586eec4a4 +size 44035 diff --git a/marked/Rel-16/35_series/35205/raw.md b/marked/Rel-16/35_series/35205/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4ce8a4467b2e9b977287a27b59040f9edc84d42c --- /dev/null +++ b/marked/Rel-16/35_series/35205/raw.md @@ -0,0 +1,437 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 6 | +| 4 Structure of this report ..... | 7 | +| 5 Background to the 3GPP Authentication and Key Generation algorithms..... | 7 | +| 6 SAGE 3GPP AF TF work plan ..... | 7 | +| 7 Outline of algorithm requirements specification ..... | 8 | +| 7.1 The authentication and key generation functions..... | 8 | +| 7.2 Use of the algorithms on the AuC side ..... | 8 | +| 7.3 Use of the algorithms in the USIM ..... | 9 | +| 7.4 Use of the algorithms for resynchronisation in the USIM ..... | 9 | +| 7.5 Use of the algorithms for resynchronisation in the HLR/AuC..... | 9 | +| 7.6 Implementation aspects..... | 9 | +| 7.7 Generic requirements for 3GPP cryptographic functions and algorithms ..... | 10 | +| 7.8 Subsequent requirements on the authentication and key generation functions..... | 10 | +| 8 Algorithms design ..... | 11 | +| 8.1 Design criteria ..... | 11 | +| 8.2 Chosen design for the framework ..... | 11 | +| 8.3 Analysis of the role of OP and OPc ..... | 12 | +| 8.4 Choice of kernel ..... | 12 | +| 8.5 Design methodology ..... | 12 | +| 8.6 Specification and test data..... | 13 | +| 9 Algorithm evaluation ..... | 13 | +| 9.1 Evaluation criteria ..... | 13 | +| 9.2 Mathematical Evaluation of the modes ..... | 13 | +| 9.3 Statistical Evaluation..... | 13 | +| 9.4 Side channel attacks evaluation..... | 14 | +| 9.5 Complexity evaluation ..... | 14 | +| 9.6 Evaluation report ..... | 14 | +| 10 Release of algorithm specification and test data by SAGE ..... | 14 | +| 10.1 SAGE 3GPP AF TF approval for release..... | 14 | +| 10.2 Publication of the algorithm set specification..... | 14 | +| 10.3 Export of the algorithm set specification ..... | 14 | +| Annex A (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. + +# --- Introduction + +This document has been prepared by the 3GPP Task Force, and contains an example set of algorithms which may be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\**. (It is not mandatory that the particular algorithms specified in this document are used — all seven functions are operator-specifiable rather than being fully standardised). This document is one five, which between them form the entire specification of the example algorithms, entitled: + +- 3GPP TS 35.205: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 1: General**". +- 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 2: Algorithm Specification**". +- 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 3: Implementors' Test Data**". +- 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 4: Design Conformance Test Data**". +- 3GPP TR 35.909: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 5: Summary and results of design and evaluation**". + +# --- 1 Scope + +This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions. + +The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced on request from 3GPP with the intent that it shall be offered to the UMTS operators, to utilise instead of developing their own. An ETSI SAGE Task Force has carried out this work. + +The requirement specification from 3GPP SA3 stated that operator personalisation of the example set must be possible and that the basic kernel must be possible to replace. + +The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the 7 algorithms used in 3GPP authentication and key generation are scheduled around this basic kernel. The specification and associated test data for the example algorithm set is documented in three documents: + +- A formal specification of both the modes and the example kernel [3] +- A detailed test data document, covering modes and the example kernel [4] +- A "black box" test data document [5] + +A detailed summary of the evaluation is provided in a public evaluation report [6] + +This report gives an overview of the overall work by the task force. + +# --- 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 33.102 v3.5.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 v3.4.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm Specification". +- [4] 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Implementors' Test Data". +- [5] 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 4: Design Conformance Test Data". +- [6] ETSI SAGE 3GPP AF TF: "Report on the design and evaluation of 3GPP Authentication and Key Generation Functions". + +[7] 3GPP TSG SA WG3 liaison statement to SAGE (S3-000089): "Authentication algorithm for 3GPP". + +# 3 Abbreviations + +For the purposes of the present report, the following abbreviations apply: + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 3GPP | 3 rd Generation Partnership Project | +| AES | Advanced Encryption Standard | +| AMF | Authentication Management Field | +| AK | Anonymity key | +| AuC | Authentication Centre | +| AUTS | Re-synchronisation Token | +| CK | Cipher Key | +| DPA | Differential Power Analysis | +| E(X) K | Encryption of X under key K | +| IK | Integrity Key | +| K | Subscriber key | +| MAC | Message Authentication Code | +| MAC-A | Network Authentication Code | +| MAC-S | Resynchronisation Authentication Code | +| OP | a 128-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1, f1*, f2, f3, f4, f5 and f5* | +| OP C | a 128-bit value derived from OP and K and used within the computations of the functions f1, f1*, f2, f3, f4, f5 and f5* . | +| OFB | Output Feedback | +| RAND | Random Challenge | +| RES | Response to Challenge | +| RNC | Radio Network Controller | +| SAGE | Security Algorithms Group of Experts | +| SAGE 3GPP AF TF | SAGE Task Force for the design of the 3GPP Authentication and Key Agreement Functions | +| SQN | Sequence Number | +| SPA | Simple Power Analysis | +| TA | Timing Attack | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| USIM | User Services Identity Module | + +# 4 Structure of this report + +The material presented in this report is organised in the subsequent clauses, as follows: + +- clause 5 provides background information on the Authentication and Key Generation algorithms; +- clause 6 provides an outline of the work plan adopted by the SAGE Task Force to design and evaluate the example algorithm set and to produce the associated test data for release to 3GPP; +- clause 7 consists of a summary of the main points in the algorithm requirements specification produced by 3GPP TSG SA ; +- clause 8 describes how the SAGE Task Force designed the algorithm and produced the specification and associated test data; +- clause 9 gives an overview of the evaluation work carried out by the SAGE Task Force and the conclusions of the evaluations; +- clause 10 gives statements on the task force procedure for approval and release of the specification and the considerations for publication and export control. + +# --- 5 Background to the 3GPP Authentication and Key Generation algorithms + +Within the mobile communication system UMTS specified by 3GPP there is a need to provide security features. These security features are realised with the use of cryptographic functions and algorithms. In total 3GPP identified the need for 9 cryptographic algorithms and functions (ref. [1]). Two of these, f8 and f9, for cipher and integrity protection of the 3GPP radio interface have already been developed and are now part of the 3GPP standard specifications. + +It was decided that the algorithms for authentication and key generation should not be standardised as they can well be proprietary to each operator and by his own choice (just like in GSM). The context for these algorithms, called f1, f1\*, f2, f3, f4, f5, f5\*, are described in ref. [1]. The generic requirements for these algorithms are specified in ref. [2]. + +It was discussed in 3GPP SA 3 if an example set of these algorithms should be produced and offered to the UMTS operators, to utilise instead of developing their own. A need for such an example set was identified with the additional requirement that operators should have a means to personalise their own algorithms. ETSI SAGE was asked to design the algorithms. To carry out this work SAGE set up a Task Force (SAGE 3GPP AF TF) based on SAGE and enlarged with cryptographers from UMTS manufacturers. + +# --- 6 SAGE 3GPP AF TF work plan + +The workplan for 3GPP authentication example algorithms was approved by 3GPP in July 2000. The SAGE 3GPP AF TF formally started work in August 2000 as an ETSI Task Force. This SAGE 3GPP AF TF consisted of the regular SAGE members, and three 3GPP manufacturers (Gemplus, Mitsubishi and Nokia). + +The work was funded by 3GPP. The total resource budget for the SAGE 3GPP AF TF work was 16.75 man months. + +The work was divided into five main tasks: + +- Project Management; +- Design ( approximately 14% of the budget) +- Evaluation (the major task, approximately 60% of the budget) +- Specification testing (approximately 20% of the budget) +- Liaison and publication activities + +The design of the algorithm example set and a complete set of specification documents should be finalised in November 2000. + +The work should be reported in 5 deliverables according to the requirements from 3GPP TSG SA. + +- a short public report on the design and evaluation work (*this document*). +- formal specification of both the modes and the example kernel [3] +- two test data reports, covering modes and the example kernel (detailed test results in [4]; black box test data in [5]) +- a summary of the evaluation results in a public report [6] + +The results of the evaluations was to be approved and agreed by the whole group before the final algorithms specifications were released to 3GPP. + +# --- 7 Outline of algorithm requirements specification + +The requirements for the authentication and key generation functions were specified by 3GPP TSG SA in: 3rd Generation Partnership Project: technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements (3G TS 33.105 version 3.4.0) [2] + +## 7.1 The authentication and key generation functions + +The mechanism for authentication and key agreement described in [1] requires the following cryptographic functions: + +| | | +|-----|---------------------------------------------------------------------------| +| f0 | the random challenge generating function; | +| f1 | the network authentication function; | +| f1* | the re-synchronisation message authentication function; | +| f2 | the user authentication function; | +| f3 | the cipher key derivation function; | +| f4 | the integrity key derivation function; | +| f5 | the anonymity key derivation function. | +| f5* | the anonymity key derivation function for the re-synchronisation message. | + +Regarding f0, the random generation function, it was agreed with 3GPP SA3 that an example for this function should not be proposed by the Task Force. + +For each of the algorithms f1 to f5\* there is a general requirement that it shall be computationally infeasible to derive K from knowledge of input(s) and output. + +## 7.2 Use of the algorithms on the AuC side + +![Diagram of AuC side authentication and key generation. RAND and K are primary inputs. f5 takes RAND and K to produce AK. AK is XORed with SQN to produce SQN ⊕ AK. f1 takes K, AMF, SQN, and RAND to produce MAC-A. f2, f3, and f4 take K and RAND to produce XRES, CK, and IK respectively.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +$$AUTN = SQN [\oplus AK] \parallel AMF \parallel MAC-A$$ + +$$Quintet = (RAND, XRES, CK, IK, AUTN)$$ + +Diagram of AuC side authentication and key generation. RAND and K are primary inputs. f5 takes RAND and K to produce AK. AK is XORed with SQN to produce SQN ⊕ AK. f1 takes K, AMF, SQN, and RAND to produce MAC-A. f2, f3, and f4 take K and RAND to produce XRES, CK, and IK respectively. + +This figure describes the generation of the authentication and key generation values in the HLR/AuC + +## 7.3 Use of the algorithms in the USIM + +![Diagram of USIM side authentication and key generation. Similar to AuC side, but SQN ⊕ AK is an input. AK is generated by f5 from RAND and K, then XORed with (SQN ⊕ AK) to recover SQN. f1 produces XMAC-A. f2 produces RES. f3 and f4 produce CK and IK.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +Diagram of USIM side authentication and key generation. Similar to AuC side, but SQN ⊕ AK is an input. AK is generated by f5 from RAND and K, then XORed with (SQN ⊕ AK) to recover SQN. f1 produces XMAC-A. f2 produces RES. f3 and f4 produce CK and IK. + +This figure describes the generation of the authentication and key generation values in the USIM + +## 7.4 Use of the algorithms for resynchronisation in the USIM + +![Diagram illustrating the generation of the re-synchronisation token, AUTS, in the USIM. The diagram shows three main components: f1*, f5*, and xor. Inputs include SQN_MS, RAND, AMF*, and K. f1* takes SQN_MS, RAND, and AMF* as inputs and produces MAC-S. f5* takes RAND and K as inputs and produces AK. The xor component takes AK and SQN_MS as inputs and produces SQN_MS ⊕ AK. The final output is AUTS = SQN_MS [⊕ AK] || MAC-S.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +The diagram illustrates the generation of the re-synchronisation token, AUTS, in the USIM. It consists of three main components: $f1^*$ , $f5^*$ , and $xor$ . The inputs are $SQN_{MS}$ , $RAND$ , $AMF^*$ , and $K$ . The $f1^*$ component takes $SQN_{MS}$ , $RAND$ , and $AMF^*$ as inputs and produces $MAC-S$ . The $f5^*$ component takes $RAND$ and $K$ as inputs and produces $AK$ . The $xor$ component takes $AK$ and $SQN_{MS}$ as inputs and produces $SQN_{MS} \oplus AK$ . The final output is $AUTS = SQN_{MS} [\oplus AK] \parallel MAC-S$ . + +Diagram illustrating the generation of the re-synchronisation token, AUTS, in the USIM. The diagram shows three main components: f1\*, f5\*, and xor. Inputs include SQN\_MS, RAND, AMF\*, and K. f1\* takes SQN\_MS, RAND, and AMF\* as inputs and produces MAC-S. f5\* takes RAND and K as inputs and produces AK. The xor component takes AK and SQN\_MS as inputs and produces SQN\_MS ⊕ AK. The final output is AUTS = SQN\_MS [⊕ AK] || MAC-S. + +This figure describes the generation of the re-synchronisation token, AUTS, in the USIM. + +## 7.5 Use of the algorithms for resynchronisation in the HLR/AuC + +![Diagram illustrating the control of the re-synchronisation token in the USIM. The diagram shows three main components: f5*, xor, and f1*. Inputs include SQN_MS ⊕ AK, RAND, AMF*, and K. f5* takes SQN_MS ⊕ AK and RAND as inputs and produces AK. The xor component takes AK and SQN_MS as inputs and produces SQN_MS ⊕ AK. The f1* component takes SQN_MS ⊕ AK, RAND, AMF*, and K as inputs and produces XMAC-S. The final output is MAC-S = XMAC-S ?.](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram illustrates the control of the re-synchronisation token in the USIM. It consists of three main components: $f5^*$ , $xor$ , and $f1^*$ . The inputs are $SQN_{MS} \oplus AK$ , $RAND$ , $AMF^*$ , and $K$ . The $f5^*$ component takes $SQN_{MS} \oplus AK$ and $RAND$ as inputs and produces $AK$ . The $xor$ component takes $AK$ and $SQN_{MS}$ as inputs and produces $SQN_{MS} \oplus AK$ . The $f1^*$ component takes $SQN_{MS} \oplus AK$ , $RAND$ , $AMF^*$ , and $K$ as inputs and produces $XMAC-S$ . The final output is $MAC-S = XMAC-S ?$ . + +Diagram illustrating the control of the re-synchronisation token in the USIM. The diagram shows three main components: f5\*, xor, and f1\*. Inputs include SQN\_MS ⊕ AK, RAND, AMF\*, and K. f5\* takes SQN\_MS ⊕ AK and RAND as inputs and produces AK. The xor component takes AK and SQN\_MS as inputs and produces SQN\_MS ⊕ AK. The f1\* component takes SQN\_MS ⊕ AK, RAND, AMF\*, and K as inputs and produces XMAC-S. The final output is MAC-S = XMAC-S ?. + +This figure describes the control of the re-synchronisation token in the USIM + +## 7.6 Implementation aspects + +All the functions $f1$ to $f5^*$ shall be designed so that they can be implemented on an IC card equipped with a 8-bit microprocessor running at 3.25 MHz with 8 kbyte ROM and 300byte RAM and produce AK, XMAC-A, RES, CK and IK in less than 500 ms execution time. + +## 7.7 Generic requirements for 3GPP cryptographic functions and algorithms + +In section 4 of [2] generic requirements are given for all 3GPP cryptographic functions and algorithms. These are summarized below (in Italics). + +### **Resilience** + +*The functions should be designed with a view to its continued use for a period of at least 20 years. Successful attacks with a workload significantly less than exhaustive key search through the effective key space should be impossible.* + +*The designers of above functions should design algorithms to a strength that reflects the above qualitative requirements.* + +### **World-wide availability and use** + +*Legal restrictions on the use or export of equipment containing cryptographic functions may prevent the use of such equipment in certain countries.* + +*It is the intention that UE and USIMs which embody such algorithms should be free from restrictions on export* + +*or use, in order to allow the free circulation of 3G terminals. Network equipment, including RNC and AuC, may be expected to come under more stringent restrictions. It is the intention that RNC and AuC which embody such algorithms should be exportable under the conditions of the Wassenaar Arrangement* + +## 7.8 Subsequent requirements on the authentication and key generation functions + +In a liaison statement to SAGE the 3GPP Security Group TSG SA WG3 presented some further requirements on the authentication functions [7]: + +"The basic principles of the algorithm design, as agreed by S3, are listed below: + +- It is required that the algorithm fulfil the requirements specified in 3G TS 33.105. +- It is required that controlled personalisation of the algorithm is possible based on an operator variant algorithm configuration field of at least 128 bits. +- It is desirable that the algorithm is designed around a replaceable kernel function to provide an additional degree of variety. +- If an algorithm is to be designed around a kernel function, then it is required that one specific kernel function be provided. +- If an algorithm is to be designed around a kernel function, then it is desirable that a list of suitable alternative kernel functions be provided. +- If an algorithm is to be designed around a kernel function, then it is desirable that standard / publicly available algorithms may be used to implement the kernel function. However, the type or types of kernel function that could be supported is left to SAGE. + +It is required that the algorithm lends itself to implementations which are resistant to Simple Power Analysis, Differential Power Analysis and other 'side-channel' attacks as appropriate when implemented on a USIM. It is acknowledged that SAGE may need to consult with smart card experts in order to be able to address this requirement." + +# --- 8 Algorithms design + +Based on the requirements and fixed starting points SAGE 3GPP AF TF established the following essential design criteria. + +## 8.1 Design criteria + +1. Without knowledge of secret keys, the functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ should be practically indistinguishable from independent random functions of their inputs (RAND||SQN||AMF) and RAND. +2. It should be practically impossible to determine any part of the secret key K, or the operator variant algorithm configuration field, OP, by manipulation of the inputs and examination of the outputs to the algorithm. +3. Events tending to violate criteria 1 and 2 should be regarded as insignificant if they occur with probability approximately $2^{-128}$ (or require approximately $2^{128}$ operations) or less. +4. Events tending to violate criteria 1 and 2 should be examined if they occur with probability approximately $2^{-64}$ (or require approximately $2^{64}$ operations) to ensure that they do not have serious consequences. Serious consequences would include recovery of a secret key or ability to emulate the algorithm on a large number of future inputs. +5. The design should build upon well-known structures and avoid unnecessary complexity. This will simplify analysis and avoid the need for a formal external evaluation. + +## 8.2 Chosen design for the framework + +The detailed specifications of the 3GPP algorithms are found in ref. [3]. The following diagram shows the framework for the functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ using the kernel function denoted $E_K$ . + +![Diagram of the RAND algorithm structure. At the top, RAND is input to an XOR gate with OPc. The output goes to an encryption block EK. The output of EK is split into five parallel paths. Each path starts with an XOR gate with OPc, followed by a 'rotate by ri' block (i=1 to 5). The output of each rotate block is XORed with a constant ci (c1 to c5). The result is then passed through an encryption block EK. The final outputs are: f1 and f1* from the first path, f5 and f2 from the second, f3 from the third, f4 from the fourth, and f5* from the fifth. A feedback line connects the output of the first path (after the first EK block) back to the input of the second path's XOR gate.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Diagram of the RAND algorithm structure. At the top, RAND is input to an XOR gate with OPc. The output goes to an encryption block EK. The output of EK is split into five parallel paths. Each path starts with an XOR gate with OPc, followed by a 'rotate by ri' block (i=1 to 5). The output of each rotate block is XORed with a constant ci (c1 to c5). The result is then passed through an encryption block EK. The final outputs are: f1 and f1\* from the first path, f5 and f2 from the second, f3 from the third, f4 from the fourth, and f5\* from the fifth. A feedback line connects the output of the first path (after the first EK block) back to the input of the second path's XOR gate. + +### Definition of f1, f1\*, f2, f3, f4, f5 and f5\* + +The value $OP_c$ is derived from the subscriber key $K$ and the operator dependent value $OP$ by + +$$OP_c = OP \oplus E(OP)_K$$ + +It is assumed and recommended in [3] that $OP_c$ is calculated outside the USIM cards and then stored in each card as an individual value. This will allow $OP$ to be better protected than if $OP$ had been stored in every card. + +$r_1, \dots, r_5$ are five fixed rotation constants and $c_1, \dots, c_5$ are five fixed addition constants defined in [2]. + +## 8.3 Analysis of the role of OP and OPc + +The 128-bit value $OP$ is the Operator Variant Algorithm Configuration Field, which the Task Force was asked to include to provide separation between the functionality of the algorithms when used by different operators. + +It is left to each operator to select a value for $OP$ . + +The algorithm set is designed to be secure whether or not $OP$ is publicly known; however, operators may see some advantage in keeping their value of $OP$ secret as a secret $OP$ is one more hurdle in the attacker's path. + +It should be difficult for someone who has discovered even a large number of $(OP_c, K)$ pairs to deduce $OP$ . That means that the $OP_c$ associated with any other value of $K$ will be unknown, which may make it (slightly) harder to mount some kinds of cryptanalytic and forgery attacks. + +It is more likely that $OP$ can be kept secret if $OP$ is not stored on the USIM, as it then only takes one USIM to be reverse engineered for $OP$ to be discovered and published. Hence the task force recommends that $OP_c$ is calculated off USIM. + +## 8.4 Choice of kernel + +Because of the short time scales it was decided to base the algorithm example set on an existing algorithm which had undergone sufficient analysis to serve as a kernel for the algorithm set so as to obviate the need for extensive cryptographic analyses and testing. A 128 bit input/output block cipher with a 128 bit key was chosen as kernel as this was considered to be a type of kernel which could easily be substituted if any operator wanted to use the framework with another algorithm. + +Document [3] describes the use of the Rijndael algorithm in encryption mode for the kernel function $E_K$ , but this choice could be replaced by any suitable 128-bit keyed function employing a 128 bit key. Rijndael was chosen as being then one of the five remaining AES candidates, was well studied, could be efficiently implemented in S/W or H/W and was available IPR-free. + +Ref [6] gives general requirements on the kernel which should be considered in case of replacement. + +## 8.5 Design methodology + +The algorithms were designed using a phased iterative and interactive approach. The design process is summarised below. + +- **Phase 1:** The starting points for the algorithms and design criteria were agreed. The design team then produced a first design proposal for a framework algorithm set including different options for the inclusion of OP. A block cipher was proposed as kernel with Rijndael as prime candidate +- **Phase 2:** The results of first evaluations were discussed. Choice of block cipher as kernel versus keyed hash was evaluated. Use of OP as protection against DPA was discussed. The counter mode was adopted instead of OFB. Based on these results, the design team revised the design to a second design proposal for the algorithm set. 3GPP SA3 agreed to limit RES to 64 bits in the example and to change input to the synchronization token. +- **Phase 3:** The results of the second evaluation were discussed. The use of Rijndael and the design for the algorithm set was confirmed, except for some small details. Considering the extensive analyses which have been made on Rijndael it was decided that the normal range of statistical testing need not be performed. Evaluation of complexity of implementation started. +- **Phase 4:** Details were fixed after mathematical evaluation of modes. The method for deriving OPc from OP was changed. Resistance against side channel attacks was decided to be left to implementers, with references to methods discussed in connection with Rijndael as candidate to AES. The specification documents were drafted and two parties independently carried out specification testing to check the correctness and completeness of the specification and the accompanying C-code. +- **Phase 5:** After the final review the specifications were confirmed. A summary report of the evaluation undertaken by the task force was produced and agreed [6], as well as this report. + +## 8.6 Specification and test data + +The algorithm specification and associated test data are documented in [3], [4] and [5]. An annex in [3] consists of example program listings of the algorithm set in 'C'. + +Document [4] provides design conformance test data designed to help verify implementations of the algorithms. The document identifies intermediate points in the algorithms where test data is provided. Then it gives input, internal and output parameters at these points, and provides different sets of test data listings. + +Document [5] is informative and provides test data designed to help verify the correct functioning of the algorithms seen as a 'black box'. The document identifies the input and output interfaces and provides a number of test sets for the different modes of operation of the algorithms. + +Two parties not directly involved in the design and evaluation teams also evaluated the adequacy of the specification. To this end, these parties made independent simulations of the algorithm from the specification and confirmed these against the test data. + +# 9 Algorithm evaluation + +## 9.1 Evaluation criteria + +The algorithm requirements as summarised in section 7 and design criteria as listed in section 8.1 leads to evaluation criteria for the mathematical evaluation and statistical evaluations. Due to the fact that the Rijndael block cipher has undergone an extensive analysis during the AES process, the task force performed no real cryptanalysis of Rijndael, but rather focused on the strength of the constructions for deriving the $f1$ to $f5^*$ modes from a strong 128-bit block cipher. + +## 9.2 Mathematical Evaluation of the modes + +The mathematical evaluation concentrated on verifying the strength of the f1-f5 construction, under the assumption that the underlying kernel is a strong block cipher. + +The main criteria investigated were: + +- The strength of each algorithm, considered individually (resilience of key and subsequent outputs) +- The independence between algorithms (one algorithm's strength is not harmed by knowledge of input/outputs for other algorithms) + +For further details on these investigations, see [6]. + +## 9.3 Statistical Evaluation + +No statistical tests were performed on the kernel, given Rijndael can be trusted to be sufficiently tested and secure through the AES process. Statistical tests on MILENAGE were considered to only yield results about the underlying kernel function. Since it was not the intention of the task force to evaluate Rijndael, statistical tests have not been performed as a consequence. + +## 9.4 Side channel attacks evaluation + +In the design process it was concluded not to be feasible to design a general algorithm framework that by itself would not be vulnerable to side channel attacks. Rijndael, as most other block ciphers, is potentially vulnerable to simple and differential power analysis (SPA and DPA) aiming to recover the secret key. It was also concluded that the use of operator constants, OPc, in the USIM cards can only play a limited role in protecting against these kinds of attacks. Hardware protection measures and masking techniques, as referenced in [6], need to be specifically implemented for protection. Also timing attacks (TA) may need implementation specific countermeasures. Rijndael as an AES candidate has been shown to readily lend itself to protection measures against side channel attacks. + +## 9.5 Complexity evaluation + +It is estimated that a non-optimized implementation of kernel and modes could be implemented with no more than 2kB ROM, 120B RAM and execute in less than 80ms. (One instance of the Rijndael cipher will execute in less than 10 ms at 3.25 MHz). Even with full protection measures against side channel attacks (SPA/DPA/TA) on Rijndael it is expected that performance will be well under the stated requirements [2]. + +## 9.6 Evaluation report + +The evaluation report [6] is a summary of all results of the complete design and evaluation process. It provides the main conclusions of the evaluation work carried out by the task force.. + +# --- 10 Release of algorithm specification and test data by SAGE + +## 10.1 SAGE 3GPP AF TF approval for release + +Prior to release of the specification of the algorithm set the following approvals were gained. + +All members of SAGE 3GPP AF TF stated that they were satisfied that the example algorithm set provides the high level of security for the authentication and key generation functions required by 3GPP. + +- All members of SAGE 3GPP AF TF approved release of the algorithm set specifications and the accompanying documents to 3GPP. + +## 10.2 Publication of the algorithm set specification + +The SAGE 3GPP AF TF does not see from a security point of view any obstacles that would prevent publication of the algorithm set specifications. + +## 10.3 Export of the algorithm set specification + +The SAGE 3GPP AF TF does not see any obstacles that would prevent export of the algorithm set specifications or corresponding implementations in congruence with the requirements as given in [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|------------|----|-----------|---------------|--------------------------------| +| TSG SA# | Version | CR | Tdoc SA | New Version | Subject/Comment | +| SP-10 | SAGE v 1.0 | - | SP-010630 | 3.0.0 | Approved as Release 1999 | +| SP-11 | 3.0.0 | - | - | 4.0.0 | Updated to Release 4 | +| SP-16 | 4.0.0 | - | - | 5.0.0 | Updated to Release 5 | +| SP-26 | 5.0.0 | - | - | 6.0.0 | Updated to Release 6 | +| SP-36 | 6.0.0 | - | - | 7.0.0 | Updated to Release 7 | +| SP-42 | 7.0.0 | - | - | 8.0.0 | Updated to Release 8 | +| SP-46 | 8.0.0 | - | - | 9.0.0 | Updated to Release 9 | +| SP-51 | 9.0.0 | - | - | 10.0.0 | Updated to Release 10 | +| 2012-09 | 10.0.0 | - | | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 11.0.0 | - | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2016-01 | 12.0.0 | - | | 13.0.0 | Update to Rel-13 version (MCC) | + +| 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-10 | - | - | - | - | - | Update to Rel-15 version (MCC) | 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/35_series/35206/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-16/35_series/35206/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bba41d274b62ec5c5af0d0fb20324c54550885ff --- /dev/null +++ b/marked/Rel-16/35_series/35206/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afe98e79cf82536b319b471d08db5c8b8aac34218a1feec23af87409f382abc4 +size 71526 diff --git a/marked/Rel-16/35_series/35206/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/35_series/35206/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09ffe6b8c70de9bca1273897ef1fdec54def7f62 --- /dev/null +++ b/marked/Rel-16/35_series/35206/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ed159a93ec777b9ace4660e28e4a573d94e8ad495edee2e91a978cd3ac9ba3c +size 53935 diff --git a/marked/Rel-16/35_series/35206/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-16/35_series/35206/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73df8b4e4792a04f48e74efcd0613fcfa31b5173 --- /dev/null +++ b/marked/Rel-16/35_series/35206/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5659b95a79520133a33b1ad652c885cf355d44d81cc8cf5cd0a13c16f6c21fff +size 53729 diff --git a/marked/Rel-16/35_series/35206/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-16/35_series/35206/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0d08c517467d021bf9e329d0f4fe3056cb7b570 --- /dev/null +++ b/marked/Rel-16/35_series/35206/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0db0a3880a4a3e62bb334827fb8c13a272ee8978193e5477b764ac0514faed8b +size 45291 diff --git a/marked/Rel-16/35_series/35206/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-16/35_series/35206/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10a52509afddc5a9e6a7b1f424899fdbe98ca104 --- /dev/null +++ b/marked/Rel-16/35_series/35206/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:097d7a6ad0589f2fc14fe60bb864b5bb9c92f3dab41540f78e725968556a03ec +size 44208 diff --git a/marked/Rel-16/35_series/35206/raw.md b/marked/Rel-16/35_series/35206/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5cfa72cb14a233e509574b1b4c464ead0478594a --- /dev/null +++ b/marked/Rel-16/35_series/35206/raw.md @@ -0,0 +1,1632 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 0 The name "MILENAGE" ..... | 5 | +| 1 Outline of the document..... | 5 | +| 1.1 References ..... | 5 | +| 2 INTRODUCTORY INFORMATION ..... | 6 | +| 2.1 Introduction ..... | 6 | +| 2.2 Notation..... | 6 | +| 2.2.1 Radix..... | 6 | +| 2.2.2 Conventions ..... | 6 | +| 2.2.3 Bit/Byte ordering ..... | 6 | +| 2.2.4 List of Symbols..... | 7 | +| 2.3 List of Variables ..... | 7 | +| 2.4 Algorithm Inputs and Outputs ..... | 7 | +| 3 The algorithm framework and the specific example algorithms..... | 8 | +| 4 Definition of the example algorithms ..... | 9 | +| 4.1 Algorithm Framework..... | 9 | +| 4.2 Specific Example Algorithms ..... | 9 | +| 5 Implementation considerations ..... | 10 | +| 5.1 OP C computed on or off the USIM?..... | 10 | +| 5.2 Customising the choice of block cipher ..... | 10 | +| 5.3 Further customisation..... | 11 | +| 5.4 Resistance to side channel attacks..... | 11 | +| Annex 1: Figure of the Algorithms..... | 12 | +| Annex 2: Specification of the Block Cipher Algorithm Rijndael ..... | 13 | +| A2.1 Introduction..... | 13 | +| A2.2 The State and External Interfaces of Rijndael ..... | 13 | +| A2.3 Internal Structure..... | 14 | +| A2.4 The Byte Substitution Transformation..... | 14 | +| A2.5 The Shift Row Transformation ..... | 15 | +| A2.6 The Mix Column Transformation ..... | 15 | +| A2.7 The Round Key addition ..... | 16 | +| A2.8 Key schedule ..... | 16 | +| A2.9 The Rijndael S-box ..... | 17 | +| Annex 3: Simulation Program Listing - Byte Oriented..... | 18 | +| Annex 4: Rijndael Listing - 32-Bit Word Oriented ..... | 25 | +| Annex A (informative): Change history..... | 31 | + +# --- 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. + +# --- Introduction + +This document has been prepared by the 3GPP Task Force, and contains an example set of algorithms which may be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\**. (It is not mandatory that the particular algorithms specified in this document are used — all seven functions are operator-specifiable rather than being fully standardised). This document is one five, which between them form the entire specification of the example algorithms, entitled: + +- 3GPP TS 35.205: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: General". +- 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; **Document 2: Algorithm Specification**". +- 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Implementors' Test Data". +- 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 4: Design Conformance Test Data". +- 3GPP TR 35.909: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 5: Summary and results of design and evaluation". + +# --- 0 The name "MILENAGE" + +The name of this algorithm set is "MILENAGE". It should be pronounced like a French word — something like "mi-le-nahj". + +--- + +# 1 Outline of the document + +Section 2 introduces the algorithms and describes the notation used in the subsequent sections. + +Section 3 explains how the algorithms are designed as a framework in such a way that various "customising components" can be selected in order to customise the algorithm for a particular operator. + +Section 4 defines the example algorithms. The algorithm framework is defined in section 4.1; in section 4.2, specific instances of the components are selected to define the specific example algorithm set. + +Section 5 explains various options and considerations for implementation of the algorithms, including considerations to be borne in mind when modifying the customising components. + +Illustrative pictures are given in Annex 1. Annex 2 gives a specification of the block cipher algorithm which is used as a cryptographic kernel in the definition of the example algorithms. Annexes 3 and 4 contain source code in the C programming language: Annex 3 gives a complete and straightforward implementation of the algorithm set, while Annex 4 gives an example of an alternative high-performance implementation just of the kernel function. + +## 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] 3GPP TS 33.102 v3.5.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 v3.4.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm Specification" (this document). +- [4] 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Implementors' Test Data". +- [5] 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 4: Design Conformance Test Data". +- [6] Joan Daemen and Vincent Rijmen: "AES Proposal: Rijndael", available at or +- [7] + +- [8] Thomas S. Messerges, "Securing the AES finalists against Power Analysis Attacks", in FSE 2000, Seventh Fast Software Encryption Workshop, ed. Schneier, Springer Verlag, 2000. +- [9] P. C. Kocher, "Timing Attacks on Implementations of Diffie-Hellman, RSA, DSS, and Other Systems", in CRYPTO'96, Lecture Notes in Computer Science #1109, Springer Verlag, 1996. +- [10] J. Kelsey, B. Schneier, D. Wagner, C. Hall, "Side Channel Cryptanalysis of Product Ciphers", in ESORICS'98, Lecture Notes in Computer Science #1485, Springer Verlag, 1998. +- [11] L. Goubin, J. Patarin, "DES and differential power analysis", in CHES'99, Lecture Notes in Computer Science #1717, Springer Verlag, 1999. +- [12] P. Kocher, J. Jaffe, B. Jun, "Differential Power Analysis", in CRYPTO'99, Lecture Notes in Computer Science #1666, Springer Verlag, 1999. +- [13] L. Goubin, J.-S. Coron, "On boolean and arithmetic masking against differential power analysis", in CHES'00, Lecture Notes in Computer Science series, Springer Verlag (to appear). + +# 2 INTRODUCTORY INFORMATION + +## 2.1 Introduction + +Within the security architecture of the 3GPP system there are seven security functions $f1, f1^*, f2, f3, f4, f5$ and $f5^*$ . The operation of these functions falls within the domain of one operator, and the functions are therefore to be specified by each operator rather than being fully standardised. The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own. + +The inputs and outputs of all seven algorithms are defined in section 2.4. + +## 2.2 Notation + +### 2.2.1 Radix + +We use the prefix **0x** to indicate **hexadecimal** numbers. + +### 2.2.2 Conventions + +We use the assignment operator '=', as used in several programming languages. When we write + +$$\langle \text{variable} \rangle = \langle \text{expression} \rangle$$ + +we mean that $\langle \text{variable} \rangle$ assumes the value that $\langle \text{expression} \rangle$ had before the assignment took place. For instance, + +$$x = x + y + 3$$ + +means + +$$(\text{new value of } x) \text{ becomes } (\text{old value of } x) + (\text{old value of } y) + 3.$$ + +### 2.2.3 Bit/Byte ordering + +All data variables in this specification are presented with the most significant bit (or byte) on the left hand side and the least significant bit (or byte) on the right hand side. Where a variable is broken down into a number of substrings, the leftmost (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant. + +### 2.2.4 List of Symbols + +| | | +|-------------|-------------------------------------------------------------------------------------------------------| +| = | The assignment operator. | +| $\oplus$ | The bitwise exclusive-OR operation | +| $\parallel$ | The concatenation of the two operands. | +| $E[x]_k$ | The result of applying a block cipher encryption to the input value x using the key k . | + +| | | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rot(x,r) | The result of cyclically rotating the 128-bit value x by r bit positions towards the most significant bit. If x = x [0] x [1] ... x [127], and y = rot( x , r ), then y = x [ r ] x [ r +1] ... x [127] x [0] x [1] x [ r -1]. | +| X[i] | The i th bit of the variable X . ( X = X [0] X [1] X [2] ..... ). | + +## 2.3 List of Variables + +| | | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AK | a 48-bit anonymity key that is the output of either of the functions f5 and f5* . | +| AMF | a 16-bit authentication management field that is an input to the functions f1 and f1* . | +| c1,c2,c3,c4,c5 | 128-bit constants, which are XORed onto intermediate variables. | +| CK | a 128-bit confidentiality key that is the output of the function f3 . | +| IK | a 128-bit integrity key that is the output of the function f4 . | +| IN1 | a 128-bit value constructed from SQN and AMF and used in the computation of the functions f1 and f1* . | +| K | a 128-bit subscriber key that is an input to the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| MAC-A | a 64-bit network authentication code that is the output of the function f1 . | +| MAC-S | a 64-bit resynchronisation authentication code that is the output of the function f1* . | +| OP | a 128-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| OPc | a 128-bit value derived from OP and K and used within the computation of the functions. | +| OUT1,OUT2,OUT3,OUT4,OUT5 | 128-bit computed values from which the outputs of the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* are obtained. | +| r1,r2,r3,r4,r5 | integers in the range 0–127 inclusive, which define amounts by which intermediate variables are cyclically rotated. | +| RAND | a 128-bit random challenge that is an input to the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| RES | a 64-bit signed response that is the output of the function f2 . | +| SQN | a 48-bit sequence number that is an input to either of the functions f1 and f1* . (For f1* this input is more precisely called SQNMS .) | +| TEMP | a 128-bit value used within the computation of the functions. | + +## 2.4 Algorithm Inputs and Outputs + +The inputs to the algorithms are given in tables 1 and 2, the outputs in tables 3–9 below. + +**Table 1: inputs to f1 and f1\*** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------------------------------------------------------------------------------------------| +| K | 128 | Subscriber key K[0]...K[127] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | +| SQN | 48 | Sequence number SQN[0]...SQN[47]. (For f1* this input is more precisely called SQNMS .) | +| AMF | 16 | Authentication management field AMF[0]...AMF[15] | + +Table 2: inputs to f2, f3, f4, f5 and f5\* + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------| +| K | 128 | Subscriber key K[0]...K[127] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | + +**Table 3: f1 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| MAC-A | 64 | Network authentication code MAC-A[0]...MAC-A[63] | + +**Table 4: $f1^*$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| MAC-S | 64 | Resynch authentication code MAC-S[0]...MAC-S[63] | + +**Table 5. $f2$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|---------------------------| +| RES | 64 | Response RES[0]...RES[63] | + +**Table 6. $f3$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-------------------------------------| +| CK | 128 | Confidentiality key CK[0]...CK[127] | + +**Table 7. $f4$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-------------------------------| +| IK | 128 | Integrity key IK[0]...IK[127] | + +**Table 8. $f5$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------| +| AK | 48 | Anonymity key AK[0]...AK[47] | + +**Table 9. $f5^*$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------| +| AK | 48 | Resynch anonymity key AK[0]...AK[47] | + +Note: Both $f5$ and $f5^*$ outputs are called AK according to reference [2]. In practice only one of them will be calculated in each instance of the authentication and key agreement procedure. + +# 3 The algorithm framework and the specific example algorithms + +The example algorithm set makes use of the following components: + +- A block cipher encryption function, which takes a 128-bit input and a 128-bit key and returns a 128-bit output. If the input is $x$ , the key is $k$ and the output is $y$ , we write $y = E[x]_k$ . +- A 128-bit value **OP**. This is an Operator Variant Algorithm Configuration Field, which the Task Force was asked to include as a simple means to provide separation between the functionality of the algorithms when used by different operators. It is left to each operator to select a value for **OP**. The algorithm set is designed to be secure whether or not **OP** is publicly known; however, operators may see some advantage in keeping their value of **OP** secret. This and other aspects of the use of **OP** are discussed further in section 5. + +In the specific example algorithm set, a particular block cipher is used. But the algorithms have been designed so that this component can be replaced by any operator who wishes to create his own customised algorithm set. In that sense this document defines an algorithm framework, and the example algorithm set is one that fits within the framework. This is how the algorithm set is defined in section 4: in section 4.1 the framework is defined in terms of the block cipher, and then in section 4.2 a block cipher is selected to give a fully specified algorithm set. + +# 4 Definition of the example algorithms + +## 4.1 Algorithm Framework + +A 128-bit value **OPC** is derived from **OP** and **K** as follows: + +$$\mathbf{OP}_C = \mathbf{OP} \oplus E[\mathbf{OP}]_K.$$ + +An intermediate 128-bit value **TEMP** is computed as follows: + +$$\mathbf{TEMP} = E[\mathbf{RAND} \oplus \mathbf{OP}_C]_K.$$ + +A 128-bit value **IN1** is constructed as follows: + +$$\mathbf{IN1}[0] .. \mathbf{IN1}[47] = \mathbf{SQN}[0] .. \mathbf{SQN}[47]$$ + +$$\mathbf{IN1}[48] .. \mathbf{IN1}[63] = \mathbf{AMF}[0] .. \mathbf{AMF}[15]$$ + +$$\mathbf{IN1}[64] .. \mathbf{IN1}[111] = \mathbf{SQN}[0] .. \mathbf{SQN}[47]$$ + +$$\mathbf{IN1}[112] .. \mathbf{IN1}[127] = \mathbf{AMF}[0] .. \mathbf{AMF}[15]$$ + +Five 128-bit constants **c1**, **c2**, **c3**, **c4**, **c5** are defined as follows: + +$$\mathbf{c1}[i] = 0 \text{ for } 0 \leq i \leq 127$$ + +$$\mathbf{c2}[i] = 0 \text{ for } 0 \leq i \leq 127, \text{ except that } \mathbf{c2}[127] = 1$$ + +$$\mathbf{c3}[i] = 0 \text{ for } 0 \leq i \leq 127, \text{ except that } \mathbf{c3}[126] = 1$$ + +$$\mathbf{c4}[i] = 0 \text{ for } 0 \leq i \leq 127, \text{ except that } \mathbf{c4}[125] = 1$$ + +$$\mathbf{c5}[i] = 0 \text{ for } 0 \leq i \leq 127, \text{ except that } \mathbf{c5}[124] = 1$$ + +Five integers **r1**, **r2**, **r3**, **r4**, **r5** are defined as follows: + +$$\mathbf{r1} = 64; \mathbf{r2} = 0; \mathbf{r3} = 32; \mathbf{r4} = 64; \mathbf{r5} = 96$$ + +Five 128-bit blocks **OUT1**, **OUT2**, **OUT3**, **OUT4**, **OUT5** are computed as follows: + +$$\mathbf{OUT1} = E[\mathbf{TEMP} \oplus \text{rot}(\mathbf{IN1} \oplus \mathbf{OP}_C, \mathbf{r1}) \oplus \mathbf{c1}]_K \oplus \mathbf{OP}_C$$ + +$$\mathbf{OUT2} = E[\text{rot}(\mathbf{TEMP} \oplus \mathbf{OP}_C, \mathbf{r2}) \oplus \mathbf{c2}]_K \oplus \mathbf{OP}_C$$ + +$$\mathbf{OUT3} = E[\text{rot}(\mathbf{TEMP} \oplus \mathbf{OP}_C, \mathbf{r3}) \oplus \mathbf{c3}]_K \oplus \mathbf{OP}_C$$ + +$$\mathbf{OUT4} = E[\text{rot}(\mathbf{TEMP} \oplus \mathbf{OP}_C, \mathbf{r4}) \oplus \mathbf{c4}]_K \oplus \mathbf{OP}_C$$ + +$$\mathbf{OUT5} = E[\text{rot}(\mathbf{TEMP} \oplus \mathbf{OP}_C, \mathbf{r5}) \oplus \mathbf{c5}]_K \oplus \mathbf{OP}_C$$ + +The outputs of the various functions are then defined as follows: + +$$\text{Output of } f1 = \text{MAC-A, where } \mathbf{MAC-A}[0] .. \mathbf{MAC-A}[63] = \mathbf{OUT1}[0] .. \mathbf{OUT1}[63]$$ + +$$\text{Output of } f1^* = \text{MAC-S, where } \mathbf{MAC-S}[0] .. \mathbf{MAC-S}[63] = \mathbf{OUT1}[64] .. \mathbf{OUT1}[127]$$ + +$$\text{Output of } f2 = \text{RES, where } \mathbf{RES}[0] .. \mathbf{RES}[63] = \mathbf{OUT2}[64] .. \mathbf{OUT2}[127]$$ + +$$\text{Output of } f3 = \text{CK, where } \mathbf{CK}[0] .. \mathbf{CK}[127] = \mathbf{OUT3}[0] .. \mathbf{OUT3}[127]$$ + +$$\text{Output of } f4 = \text{IK, where } \mathbf{IK}[0] .. \mathbf{IK}[127] = \mathbf{OUT4}[0] .. \mathbf{OUT4}[127]$$ + +$$\text{Output of } f5 = \text{AK, where } \mathbf{AK}[0] .. \mathbf{AK}[47] = \mathbf{OUT2}[0] .. \mathbf{OUT2}[47]$$ + +$$\text{Output of } f5^* = \text{AK, where } \mathbf{AK}[0] .. \mathbf{AK}[47] = \mathbf{OUT5}[0] .. \mathbf{OUT5}[47]$$ + +(The repeated reference to AK is not a mistake: AK is the name of the output of either *f5* or *f5\**, and these two functions will not in practice be computed simultaneously.) + +## 4.2 Specific Example Algorithms + +The specific example algorithm set is defined by specifying the block cipher encryption function *E[]*, which we do in this section. (It is left to each operator to specify the Operator Variant Algorithm Configuration Field **OP**.) + +The block cipher selected is Rijndael [6]. This is the algorithm proposed as the Advanced Encryption Standard [7]. More precisely, it is Rijndael with 128-bit key and 128-bit block size. + +$$E[\mathbf{x}]_K = \text{the result of applying the Rijndael encryption algorithm to the 128-bit value } \mathbf{x} \text{ under the 128-bit key } \mathbf{k}.$$ + +Although the definitive specification of Rijndael is in [6], a complete specification of Rijndael with 128-bit key and 128-bit block size is also given in Annex 2 of this document. + +The inputs to and output of Rijndael are defined as strings of bytes. The 128-bit string $x = x[0] \parallel x[1] \parallel \dots \parallel x[127]$ is treated as a string of bytes by taking $x[0] \parallel x[1] \parallel \dots \parallel x[7]$ as the first byte, $x[8] \parallel x[9] \parallel \dots \parallel x[15]$ as the second byte, and so on. The key and output string are converted in the same way. + +Note that the following patent statement has been made publicly (and included in [6]) by the authors of the Rijndael algorithm: "Rijndael or any of its implementations is not and will not be subject to patents." + +# 5 Implementation considerations + +## 5.1 $OP_C$ computed on or off the USIM? + +Recall that **OP** is an Operator Variant Algorithm Configuration Field. It is expected that each operator will define a value of **OP** which will then be used for all its subscribers. (It is up to operators to decide how to manage **OP**. The value of **OP** used for new batches of USIMs could be changed occasionally; or perhaps a different value could be given to each different USIM supplier. **OP** could even be given a different value for every subscriber if desired, but that is not really the intention.) + +It will be seen in section 4.1 that $OP_C$ is computed from **OP** and **K**, and that it is only $OP_C$ , not **OP**, that is ever used in subsequent computations. This gives two alternative options for implementation of the algorithms on the USIM: + +- (a) **$OP_C$ computed off the USIM:** $OP_C$ is computed as part of the USIM prepersonalisation process, and $OP_C$ is stored on the USIM. **OP** itself is not stored on the USIM. +- (b) **$OP_C$ computed on the USIM:** **OP** is stored on the USIM (it may be considered as a hard-coded part of the algorithm if preferred). $OP_C$ is recomputed each time the algorithms are called. + +The SAGE Task Force recommends that $OP_C$ be computed off the USIM if possible, since this gives the following benefits: + +- The complexity of the algorithms run on the USIM is reduced. +- It is more likely that **OP** can be kept secret. (If **OP** is stored on the USIM, it only takes one USIM to be reverse engineered for **OP** to be discovered and published. But it should be difficult for someone who has discovered even a large number of $(OP_C, K)$ pairs to deduce **OP**. That means that the $OP_C$ associated with any other value of **K** will be unknown, which may make it harder to mount some kinds of cryptanalytic and forgery attacks. The algorithms are designed to be secure whether or not **OP** is known to the attacker, but a secret **OP** is one more hurdle in the attacker's path.) + +## 5.2 Customising the choice of block cipher + +It was explained in section 3 that an operator may create a variant algorithm set by selecting a block cipher other than Rijndael. It is vitally important that whatever block cipher is chosen is one that has been extensively analysed and is still believed to be secure. The security of the authentication and key generation functions is crucially dependent on the strength of the block cipher. + +Strictly speaking, in fact, the kernel function does not have to be a block cipher; it just has to be a keyed function (with 128-bit input, key and output) satisfying the following cryptographic requirement: + +- Let the key be fixed. Without initial knowledge of the key, but with a large number of pairs of chosen input and resulting output, it must be infeasible to determine the key, and also infeasible to predict the output for any other chosen input with probability significantly greater than $2^{-128}$ . + +See also section 5.4 about protecting against side channel attacks; this will need to be borne in mind when selecting/implementing a replacement kernel function. + +## 5.3 Further customisation + +If an operator wishes to customise the algorithms still further, a simple approach is to select different values for the constants **c1–c5** and **r1–r5**. If this is done, the pairs $(c_i, r_i)$ must all be different. It must not be the case that both $c_i = c_j$ and $r_i = r_j$ for $i \neq j$ . For instance, it must not be the case that both **c2 = c4** and **r2 = r4**. Additionally it is + +recommended that the following restrictions are applied: + +- **c1** has even parity. (A 128-bit value has even parity if the number of '1's in its binary representation is even.) +- **c2–c5** all have odd parity. + +## 5.4 Resistance to side channel attacks + +When these algorithms are implemented on a USIM, consideration should be given to protecting them against side channel attacks such as differential power analysis (DPA). [8, 9, 10, 11, 12, 13] may be useful references. + +# Annex 1: Figure of the Algorithms + +![Cryptographic algorithm diagram showing the derivation of f1, f1*, f2, f3, f4, f5, and f5* from RAND, K, and OP.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +The diagram illustrates the MILENAGE algorithm set. At the top, a 128-bit random challenge **RAND** is XORed with $OP_c$ and then encrypted using the block cipher $E$ with key $K$ (denoted as $E_K$ ). The result is then processed through five parallel branches. An inset box shows that $OP_c = OP \oplus E_K(OP)$ . + +The first branch takes the input $SQN \parallel AMF \parallel SQN \parallel AMF$ , XORs it with $OP_c$ , performs a rotation by $r1$ , XORs with constant $c1$ , passes through $E_K$ , and finally XORs with $OP_c$ to produce outputs $f1$ and $f1^*$ . + +Branches 2 through 5 follow a similar pattern: the output of the initial $E_K$ stage is XORed with $OP_c$ , rotated by $r2$ through $r5$ , XORed with constants $c2$ through $c5$ , passed through $E_K$ , and XORed with $OP_c$ to produce $f5$ and $f2$ (from branch 2), $f3$ (from branch 3), $f4$ (from branch 4), and $f5^*$ (from branch 5). + +Cryptographic algorithm diagram showing the derivation of f1, f1\*, f2, f3, f4, f5, and f5\* from RAND, K, and OP. + +# Annex 2: Specification of the Block Cipher Algorithm Rijndael + +## A2.1 Introduction + +This section provides a specification for the example kernel function. The block cipher used is Rijndael. The complete specification of Rijndael is given elsewhere [6]. To quote from [6]: + +"Rijndael is an iterated block cipher with a variable block length and a variable key length. The block length and the key length can be independently specified to 128, 192 or 256 bits." + +For 3GPP purpose, Rijndael is used only in encryption mode and has the block and key length both set to 128 bits. For the rest of this section, when we refer to Rijndael we mean Rijndael with 128-bit block and key length. This document describes a simple byte oriented implementation of the encryption mode of Rijndael. Readers wishing more detail on the design of the cipher or implementation speed-ups are referred to the original document [6]. + +## A2.2 The State and External Interfaces of Rijndael + +Rijndael is composed of a series of rounds that transform the input into the output. An intermediate result is called the **State**. The **State** can be pictured as a 4x4 rectangular array of bytes (128 bits in total). The Cipher Key is similarly pictured as a 4x4 rectangular array. These representations are illustrated in Figure 1. + +| | | | | | | | | | +|------------------------|------------------------|------------------------|------------------------|--|------------------------|------------------------|------------------------|------------------------| +| a0,0 | a0,1 | a0,2 | a0,3 | | k0,0 | k0,1 | k0,2 | k0,3 | +| a1,0 | a1,1 | a1,2 | a1,3 | | k1,0 | k1,1 | k1,2 | k1,3 | +| a2,0 | a2,1 | a2,2 | a2,3 | | k2,0 | k2,1 | k2,2 | k2,3 | +| a3,0 | a3,1 | a3,2 | a3,3 | | k3,0 | k3,1 | k3,2 | k3,3 | + +Figure 1: Example of State and Cipher Key layout + +Rijndael takes plaintext bytes $P_0, P_1, \dots, P_{15}$ and key bytes $K_0, K_1, \dots, K_{15}$ as input and ciphertext bytes $C_0, C_1, \dots, C_{15}$ as output. The plaintext bytes are mapped onto the state bytes in the order $a_{0,0}, a_{1,0}, a_{2,0}, a_{3,0}, a_{0,1}, a_{1,1}, a_{2,1}, a_{3,1}, \dots$ and the key bytes in the order $k_{0,0}, k_{1,0}, k_{2,0}, k_{3,0}, k_{0,1}, k_{1,1}, k_{2,1}, k_{3,1}, \dots$ . At the end of the cipher operation, the ciphertext is extracted from the **State** by taking the **State** bytes in the same order. + +Hence if the one-dimensional index of a byte within a block is $n$ and the two dimensional index is $(i, j)$ , we have: + +$$i = n \bmod 4; \quad j = \lfloor n/4 \rfloor; \quad n = i + 4 * j$$ + +## A2.3 Internal Structure + +Rijndael consists of the following operations: + +- an initial Round Key addition +- 9 rounds, numbered 1-9, each consisting of + - a byte substitution transformation + - a shift row transformation + - a mix column transformation + - a Round Key addition +- A final round (round 10) consisting of + - a byte substitution transformation + - a shift row transformation + - a Round Key addition + +The component transformations and how the Round Keys are derived from the cipher keys are specified in the following subsections. + +## A2.4 The Byte Substitution Transformation + +The byte substitution transformation is a non-linear byte substitution, operating on each of the **State** bytes independently. The substitution table (S-box) is given in section A2.9. + +Figure 2 illustrates the effect of the byte substitution transformation on the **State**. + +![Diagram illustrating the Byte Substitution Transformation. It shows two 4x4 grids representing the State. The left grid contains elements a_{i,j} and the right grid contains elements b_{i,j}. An S-box is shown between them, with arrows indicating that each element a_{i,j} is transformed into b_{i,j} via the S-box.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +The diagram shows two 4x4 grids representing the State. The left grid contains elements $a_{i,j}$ and the right grid contains elements $b_{i,j}$ . An S-box is shown between them, with arrows indicating that each element $a_{i,j}$ is transformed into $b_{i,j}$ via the S-box. The grids are arranged as follows: + +| | | | | +|-----------|-----------|-----------|-----------| +| $a_{0,0}$ | $a_{0,1}$ | $a_{0,2}$ | $a_{0,3}$ | +| $a_{1,0}$ | $a_{1,1}$ | $a_{1,2}$ | $a_{1,3}$ | +| $a_{2,0}$ | $a_{2,1}$ | $a_{2,2}$ | $a_{2,3}$ | +| $a_{3,0}$ | $a_{3,1}$ | $a_{3,2}$ | $a_{3,3}$ | + +S-box + +| | | | | +|-----------|-----------|-----------|-----------| +| $b_{0,0}$ | $b_{0,1}$ | $b_{0,2}$ | $b_{0,3}$ | +| $b_{1,0}$ | $b_{1,1}$ | $b_{1,2}$ | $b_{1,3}$ | +| $b_{2,0}$ | $b_{2,1}$ | $b_{2,2}$ | $b_{2,3}$ | +| $b_{3,0}$ | $b_{3,1}$ | $b_{3,2}$ | $b_{3,3}$ | + +Diagram illustrating the Byte Substitution Transformation. It shows two 4x4 grids representing the State. The left grid contains elements a\_{i,j} and the right grid contains elements b\_{i,j}. An S-box is shown between them, with arrows indicating that each element a\_{i,j} is transformed into b\_{i,j} via the S-box. + +**Figure 2: Byte substitution acts on the individual bytes of the State** + +So, for every element of **State**, we apply the transformation: + +$$b_{i,j} = \text{S-box}[ a_{i,j} ]$$ + +Where $a_{i,j}$ is the initial value of the element in **State**, +and $b_{i,j}$ is the output value of the element in **State**. + +## A2.5 The Shift Row Transformation + +In the shift row transformation, the rows of the **State** are cyclically left shifted by different amounts. Row 0 is not shifted, row 1 is shifted by 1 byte, row 2 by 2 bytes and row 3 by 3 bytes. + +Figure 3 illustrates the effect of the shift row transformation on the **State**. + +![Diagram illustrating the Shift Row transformation. It shows two 4x4 grids representing the State. The left grid has elements a_{i,j} where i is the row index and j is the column index. The right grid shows the result after the transformation. Row 0 is unchanged. Row 1 is cyclically left shifted by 1. Row 2 is cyclically left shifted by 2. Row 3 is cyclically left shifted by 3. Arrows with labels indicate the shift amount for each row.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +| | | | | | | | | | +|-----------|-----------|-----------|-----------|------------------------|-----------|-----------|-----------|-----------| +| $a_{0,0}$ | $a_{0,1}$ | $a_{0,2}$ | $a_{0,3}$ | No shift | $a_{0,0}$ | $a_{0,1}$ | $a_{0,2}$ | $a_{0,3}$ | +| $a_{1,0}$ | $a_{1,1}$ | $a_{1,2}$ | $a_{1,3}$ | Cyclic left shift by 1 | $a_{1,1}$ | $a_{1,2}$ | $a_{1,3}$ | $a_{1,0}$ | +| $a_{2,0}$ | $a_{2,1}$ | $a_{2,2}$ | $a_{2,3}$ | Cyclic left shift by 2 | $a_{2,2}$ | $a_{2,3}$ | $a_{2,0}$ | $a_{2,1}$ | +| $a_{3,0}$ | $a_{3,1}$ | $a_{3,2}$ | $a_{3,3}$ | Cyclic left shift by 3 | $a_{3,3}$ | $a_{3,0}$ | $a_{3,1}$ | $a_{3,2}$ | + +Diagram illustrating the Shift Row transformation. It shows two 4x4 grids representing the State. The left grid has elements a\_{i,j} where i is the row index and j is the column index. The right grid shows the result after the transformation. Row 0 is unchanged. Row 1 is cyclically left shifted by 1. Row 2 is cyclically left shifted by 2. Row 3 is cyclically left shifted by 3. Arrows with labels indicate the shift amount for each row. + +Figure 3: Shift Row operates on the rows of the State + +## A2.6 The Mix Column Transformation + +The mix column transformation operates on each column of the **State** independently. For column $j$ , we have + +$$b_{0,j} = T_2(a_{0,j}) \oplus T_3(a_{1,j}) \oplus a_{2,j} \oplus a_{3,j}$$ + +$$b_{1,j} = a_{0,j} \oplus T_2(a_{1,j}) \oplus T_3(a_{2,j}) \oplus a_{3,j}$$ + +$$b_{2,j} = a_{0,j} \oplus a_{1,j} \oplus T_2(a_{2,j}) \oplus T_3(a_{3,j})$$ + +$$b_{3,j} = T_3(a_{0,j}) \oplus a_{1,j} \oplus a_{2,j} \oplus T_2(a_{3,j})$$ + +where: + +$$\begin{aligned} T_2(a) &= 2*a && \text{if } a < 128 \\ \text{or } T_2(a) &= (2*a) \oplus 283 && \text{if } a \geq 128 \\ \text{and } T_3(a) &= T_2(a) \oplus a. \end{aligned}$$ + +For example: + +If $a = 63$ then $T_2(63) = 126$ ; $T_3(63) = T_2(63) \oplus 63 = 65$ + +If $a = 143$ then $T_2(143) = 5$ ; $T_3(143) = T_2(143) \oplus 143 = 138$ . + +Figure 4 illustrates the effect of the mix column transformation on the **State**. + +![Diagram illustrating the Mix Column operation. It shows two 4x4 grids representing the State. The left grid has elements a_{i,j} and the right grid has elements b_{i,j}. A box labeled 'Mix Column' is between them. Arrows indicate that the operation is applied column-wise, specifically showing the mixing of elements in the second column (j=1) of both grids.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Diagram illustrating the Mix Column operation. It shows two 4x4 grids representing the State. The left grid has elements a\_{i,j} and the right grid has elements b\_{i,j}. A box labeled 'Mix Column' is between them. Arrows indicate that the operation is applied column-wise, specifically showing the mixing of elements in the second column (j=1) of both grids. + +Figure 4: Mix Column operates on the columns of the State + +## A2.7 The Round Key addition + +In this operation, a Round Key is applied to the **State** by a simple bitwise exclusive-or. The Round Key is derived from the Cipher Key by means of the key schedule. The Round Key length is equal to the block length. + +This transformation is illustrated in Figure 5. + +![Diagram illustrating the Round Key addition operation. It shows three 4x4 grids. The first grid contains elements a_{i,j} (State). The second grid contains elements rk_{i,j} (Round Key). The third grid contains elements b_{i,j} (Result). The operation is indicated by a circle with a plus sign (XOR) between the first and second grids, and an equals sign between the second and third grids.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +Diagram illustrating the Round Key addition operation. It shows three 4x4 grids. The first grid contains elements a\_{i,j} (State). The second grid contains elements rk\_{i,j} (Round Key). The third grid contains elements b\_{i,j} (Result). The operation is indicated by a circle with a plus sign (XOR) between the first and second grids, and an equals sign between the second and third grids. + +Figure 5: In the key addition the Round Key is bitwise XORed to the State + +So, for every element of **State**, we have: + +$$b_{i,j} = a_{i,j} \oplus rk_{i,j}$$ + +Where $a_{i,j}$ is the initial value of the element in **State**, + $b_{i,j}$ is the output value of the element in **State**, and + $rk_{i,j}$ is the round key byte. + +## A2.8 Key schedule + +Rijndael has 11 Round Keys, numbered 0-10, that are each 4x4 rectangular arrays of bytes. The Round Keys are derived from the Cipher Key by means of the key schedule. The initial Round Key (thought of as the zeroth Round Key) is formed directly from the cipher key. This zeroth Round Key is used unaltered for the initial key addition. The remaining Round Keys are used in the ten rounds. Each new round key is derived from the previous round key. Note: It is possible to run the key schedule round by round on an "as required" basis and so only use a total of 16 bytes to store the Round Key. + +Let $rk_{r,i,j}$ be the value of the $r^{\text{th}}$ Round Key at position $(i, j)$ in the array and $k_{i,j}$ be the cipher key loaded into a 4x4 array. + +Initialisation: $rk_{0,i,j} = k_{i,j}$ for all $i$ and $j$ . + +The other Round Keys ( $r=1$ to 10 inclusive) are calculated from the previous one as follows. First the 0th column is + +constructed: + +$$\begin{aligned} \text{rk}_{r,0,0} &= \text{rk}_{r-1,0,0} \oplus \text{S-box}[\text{rk}_{r-1,1,3}] \oplus \text{round\_const}[r] \\ \text{rk}_{r,1,0} &= \text{rk}_{r-1,1,0} \oplus \text{S-box}[\text{rk}_{r-1,2,3}] \\ \text{rk}_{r,2,0} &= \text{rk}_{r-1,2,0} \oplus \text{S-box}[\text{rk}_{r-1,3,3}] \\ \text{rk}_{r,3,0} &= \text{rk}_{r-1,3,0} \oplus \text{S-box}[\text{rk}_{r-1,0,3}] \end{aligned}$$ + +where $\text{round\_const}[1] = 1$ and $\text{round\_const}[r] = T_2(\text{round\_const}[r-1])$ , and S-box is the previously mentioned byte substitution. + +Then the remaining three columns are constructed in turn from the corresponding column of the previous Round Key and the previous column of the current Round Key: + +$$\text{rk}_{r,ij} = \text{rk}_{r-1,ij} \oplus \text{rk}_{r,ij-1} \text{ for } i=0,1,2,3 \text{ and } j=1,2,3.$$ + +Note: The ten round constants computed from the equations: + +$$\begin{aligned} \text{round\_const}[1] &= 1 \\ \text{round\_const}[r] &= T_2(\text{round\_const}[r-1]) \quad r=2,3,\dots,10 \end{aligned}$$ + +are: 1, 2, 4, 8, 16, 32, 64, 128, 27, 54. + +## A2.9 The Rijndael S-box + +``` +Sbox[256] = { + 99,124,119,123,242,107,111,197, 48, 1,103, 43,254,215,171,118, +202,130,201,125,250, 89, 71,240,173,212,162,175,156,164,114,192, +183,253,147, 38, 54, 63,247,204, 52,165,229,241,113,216, 49, 21, + 4,199, 35,195, 24,150, 5,154, 7, 18,128,226,235, 39,178,117, + 9,131, 44, 26, 27,110, 90,160, 82, 59,214,179, 41,227, 47,132, + 83,209, 0,237, 32,252,177, 91,106,203,190, 57, 74, 76, 88,207, +208,239,170,251, 67, 77, 51,133, 69,249, 2,127, 80, 60,159,168, + 81,163, 64,143,146,157, 56,245,188,182,218, 33, 16,255,243,210, +205, 12, 19,236, 95,151, 68, 23,196,167,126, 61,100, 93, 25,115, + 96,129, 79,220, 34, 42,144,136, 70,238,184, 20,222, 94, 11,219, +224, 50, 58, 10, 73, 6, 36, 92,194,211,172, 98,145,149,228,121, +231,200, 55,109,141,213, 78,169,108, 86,244,234,101,122,174, 8, +186,120, 37, 46, 28,166,180,198,232,221,116, 31, 75,189,139,138, +112, 62,181,102, 72, 3,246, 14, 97, 53, 87,185,134,193, 29,158, +225,248,152, 17,105,217,142,148,155, 30,135,233,206, 85, 40,223, +140,161,137, 13,191,230, 66,104, 65,153, 45, 15,176, 84,187, 22}; +``` + +# Annex 3: Simulation Program Listing - Byte Oriented + +``` + +/*----- + * Example algorithms f1, f1*, f2, f3, f4, f5, f5* + *----- + * + * A sample implementation of the example 3GPP authentication and + * key agreement functions f1, f1*, f2, f3, f4, f5 and f5*. This is + * a byte-oriented implementation of the functions, and of the block + * cipher kernel function Rijndael. + * + * This has been coded for clarity, not necessarily for efficiency. + * + * The functions f2, f3, f4 and f5 share the same inputs and have + * been coded together as a single function. f1, f1* and f5* are + * all coded separately. + *-----*/ + +typedef unsigned char u8; + +/*----- Operator Variant Algorithm Configuration Field -----*/ + + /*----- Insert your value of OP here -----*/ +u8 OP[16] = {0x63, 0xbf, 0xa5, 0x0e, 0xe6, 0x52, 0x33, 0x65, + 0xff, 0x14, 0xc1, 0xf4, 0x5f, 0x88, 0x73, 0x7d}; + /*----- Insert your value of OP here -----*/ + +/*----- prototypes -----*/ + +void f1 ( u8 k[16], u8 rand[16], u8 sqn[6], u8 amf[2], + u8 mac_a[8] ); +void f2345 ( u8 k[16], u8 rand[16], + u8 res[8], u8 ck[16], u8 ik[16], u8 ak[6] ); +void f1star( u8 k[16], u8 rand[16], u8 sqn[6], u8 amf[2], + u8 mac_s[8] ); +void f5star( u8 k[16], u8 rand[16], + u8 ak[6] ); +void ComputeOPc( u8 op_c[16] ); +void RijndaelKeySchedule( u8 key[16] ); +void RijndaelEncrypt( u8 input[16], u8 output[16] ); + +/*----- + * Algorithm f1 + *----- + * + * Computes network authentication code MAC-A from key K, random + * challenge RAND, sequence number SQN and authentication management + * field AMF. + *-----*/ + +void f1 ( u8 k[16], u8 rand[16], u8 sqn[6], u8 amf[2], + u8 mac_a[8] ) +{ + u8 op_c[16]; + u8 temp[16]; + u8 in1[16]; + u8 out1[16]; + u8 rijndaelInput[16]; + u8 i; + + RijndaelKeySchedule( k ); + + ComputeOPc( op_c ); + + for (i=0; i<16; i++) + rijndaelInput[i] = rand[i] ^ op_c[i]; + RijndaelEncrypt( rijndaelInput, temp ); + + for (i=0; i<6; i++) + +``` + +``` + + { + in1[i] = sqn[i]; + in1[i+8] = sqn[i]; + } + for (i=0; i<2; i++) + { + in1[i+6] = amf[i]; + in1[i+14] = amf[i]; + } + + /* XOR op_c and in1, rotate by r1=64, and XOR * + * on the constant c1 (which is all zeroes) */ + + for (i=0; i<16; i++) + rijndaelInput[(i+8) % 16] = in1[i] ^ op_c[i]; + + /* XOR on the value temp computed before */ + + for (i=0; i<16; i++) + rijndaelInput[i] ^= temp[i]; + + RijndaelEncrypt( rijndaelInput, out1 ); + for (i=0; i<16; i++) + out1[i] ^= op_c[i]; + + for (i=0; i<8; i++) + mac_a[i] = out1[i]; + + return; +} /* end of function f1 */ + +/*----- + * Algorithms f2-f5 + *----- + * + * Takes key K and random challenge RAND, and returns response RES, + * confidentiality key CK, integrity key IK and anonymity key AK. + * + *-----*/ + +void f2345 ( u8 k[16], u8 rand[16], + u8 res[8], u8 ck[16], u8 ik[16], u8 ak[6] ) +{ + u8 op_c[16]; + u8 temp[16]; + u8 out[16]; + u8 rijndaelInput[16]; + u8 i; + + RijndaelKeySchedule( k ); + + ComputeOPc( op_c ); + + for (i=0; i<16; i++) + rijndaelInput[i] = rand[i] ^ op_c[i]; + RijndaelEncrypt( rijndaelInput, temp ); + + /* To obtain output block OUT2: XOR OPc and TEMP, * + * rotate by r2=0, and XOR on the constant c2 (which * + * is all zeroes except that the last bit is 1). */ + + for (i=0; i<16; i++) + rijndaelInput[i] = temp[i] ^ op_c[i]; + rijndaelInput[15] ^= 1; + + RijndaelEncrypt( rijndaelInput, out ); + for (i=0; i<16; i++) + out[i] ^= op_c[i]; + + for (i=0; i<8; i++) + res[i] = out[i+8]; + for (i=0; i<6; i++) + ak[i] = out[i]; + + /* To obtain output block OUT3: XOR OPc and TEMP, * + * rotate by r3=32, and XOR on the constant c3 (which * + +``` + +``` + + * is all zeroes except that the next to last bit is 1). */ + + for (i=0; i<16; i++) + rijndaelInput[(i+12) % 16] = temp[i] ^ op_c[i]; + rijndaelInput[15] ^= 2; + + RijndaelEncrypt( rijndaelInput, out ); + for (i=0; i<16; i++) + out[i] ^= op_c[i]; + + for (i=0; i<16; i++) + ck[i] = out[i]; + + /* To obtain output block OUT4: XOR OPc and TEMP, * + * rotate by r4=64, and XOR on the constant c4 (which * + * is all zeroes except that the 2nd from last bit is 1). */ + + for (i=0; i<16; i++) + rijndaelInput[(i+8) % 16] = temp[i] ^ op_c[i]; + rijndaelInput[15] ^= 4; + + RijndaelEncrypt( rijndaelInput, out ); + for (i=0; i<16; i++) + out[i] ^= op_c[i]; + + for (i=0; i<16; i++) + ik[i] = out[i]; + + return; +} /* end of function f2345 */ + +/*----- + * Algorithm f1* + *----- + * + * Computes resynch authentication code MAC-S from key K, random + * challenge RAND, sequence number SQN and authentication management + * field AMF. + *-----*/ + +void f1star( u8 k[16], u8 rand[16], u8 sqn[6], u8 amf[2], + u8 mac_s[8] ) +{ + u8 op_c[16]; + u8 temp[16]; + u8 in1[16]; + u8 out1[16]; + u8 rijndaelInput[16]; + u8 i; + + RijndaelKeySchedule( k ); + + ComputeOPc( op_c ); + + for (i=0; i<16; i++) + rijndaelInput[i] = rand[i] ^ op_c[i]; + RijndaelEncrypt( rijndaelInput, temp ); + + for (i=0; i<6; i++) + { + in1[i] = sqn[i]; + in1[i+8] = sqn[i]; + } + for (i=0; i<2; i++) + { + in1[i+6] = amf[i]; + in1[i+14] = amf[i]; + } + + /* XOR op_c and in1, rotate by r1=64, and XOR * + * on the constant c1 (which is all zeroes) */ + + for (i=0; i<16; i++) + rijndaelInput[(i+8) % 16] = in1[i] ^ op_c[i]; + + /* XOR on the value temp computed before */ + +``` + +``` + + for (i=0; i<16; i++) + rijndaelInput[i] ^= temp[i]; + + RijndaelEncrypt( rijndaelInput, out1 ); + for (i=0; i<16; i++) + out1[i] ^= op_c[i]; + + for (i=0; i<8; i++) + mac_s[i] = out1[i+8]; + + return; +} /* end of function f1star */ + +/*----- + * Algorithm f5* + *----- + * + * Takes key K and random challenge RAND, and returns resynch + * anonymity key AK. + * + *-----*/ + +void f5star( u8 k[16], u8 rand[16], + u8 ak[6] ) +{ + u8 op_c[16]; + u8 temp[16]; + u8 out[16]; + u8 rijndaelInput[16]; + u8 i; + + RijndaelKeySchedule( k ); + + ComputeOPc( op_c ); + + for (i=0; i<16; i++) + rijndaelInput[i] = rand[i] ^ op_c[i]; + RijndaelEncrypt( rijndaelInput, temp ); + + /* To obtain output block OUT5: XOR OPc and TEMP, + * rotate by r5=96, and XOR on the constant c5 (which + * is all zeroes except that the 3rd from last bit is 1). */ + + for (i=0; i<16; i++) + rijndaelInput[(i+4) % 16] = temp[i] ^ op_c[i]; + rijndaelInput[15] ^= 8; + + RijndaelEncrypt( rijndaelInput, out ); + for (i=0; i<16; i++) + out[i] ^= op_c[i]; + + for (i=0; i<6; i++) + ak[i] = out[i]; + + return; +} /* end of function f5star */ + +/*----- + * Function to compute OPc from OP and K. Assumes key schedule has + * already been performed. + *-----*/ + +void ComputeOPc( u8 op_c[16] ) +{ + u8 i; + + RijndaelEncrypt( OP, op_c ); + for (i=0; i<16; i++) + op_c[i] ^= OP[i]; + + return; +} /* end of function ComputeOPc */ + +``` + +``` + +/*----- Rijndael round subkeys -----*/ +u8 roundKeys[11][4][4]; + +/*----- Rijndael S box table -----*/ +u8 S[256] = { + 99,124,119,123,242,107,111,197, 48, 1,103, 43,254,215,171,118, + 202,130,201,125,250, 89, 71,240,173,212,162,175,156,164,114,192, + 183,253,147, 38, 54, 63,247,204, 52,165,229,241,113,216, 49, 21, + 4,199, 35,195, 24,150, 5,154, 7, 18,128,226,235, 39,178,117, + 9,131, 44, 26, 27,110, 90,160, 82, 59,214,179, 41,227, 47,132, + 83,209, 0,237, 32,252,177, 91,106,203,190, 57, 74, 76, 88,207, + 208,239,170,251, 67, 77, 51,133, 69,249, 2,127, 80, 60,159,168, + 81,163, 64,143,146,157, 56,245,188,182,218, 33, 16,255,243,210, + 205, 12, 19,236, 95,151, 68, 23,196,167,126, 61,100, 93, 25,115, + 96,129, 79,220, 34, 42,144,136, 70,238,184, 20,222, 94, 11,219, + 224, 50, 58, 10, 73, 6, 36, 92,194,211,172, 98,145,149,228,121, + 231,200, 55,109,141,213, 78,169,108, 86,244,234,101,122,174, 8, + 186,120, 37, 46, 28,166,180,198,232,221,116, 31, 75,189,139,138, + 112, 62,181,102, 72, 3,246, 14, 97, 53, 87,185,134,193, 29,158, + 225,248,152, 17,105,217,142,148,155, 30,135,233,206, 85, 40,223, + 140,161,137, 13,191,230, 66,104, 65,153, 45, 15,176, 84,187, 22, +}; + +/*----- This array does the multiplication by x in GF(2^8) -----*/ +u8 Xtime[256] = { + 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, + 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, + 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, + 96, 98,100,102,104,106,108,110,112,114,116,118,120,122,124,126, + 128,130,132,134,136,138,140,142,144,146,148,150,152,154,156,158, + 160,162,164,166,168,170,172,174,176,178,180,182,184,186,188,190, + 192,194,196,198,200,202,204,206,208,210,212,214,216,218,220,222, + 224,226,228,230,232,234,236,238,240,242,244,246,248,250,252,254, + 27, 25, 31, 29, 19, 17, 23, 21, 11, 9, 15, 13, 3, 1, 7, 5, + 59, 57, 63, 61, 51, 49, 55, 53, 43, 41, 47, 45, 35, 33, 39, 37, + 91, 89, 95, 93, 83, 81, 87, 85, 75, 73, 79, 77, 67, 65, 71, 69, + 123,121,127,125,115,113,119,117,107,105,111,109, 99, 97,103,101, + 155,153,159,157,147,145,151,149,139,137,143,141,131,129,135,133, + 187,185,191,189,179,177,183,181,171,169,175,173,163,161,167,165, + 219,217,223,221,211,209,215,213,203,201,207,205,195,193,199,197, + 251,249,255,253,243,241,247,245,235,233,239,237,227,225,231,229 +}; + +/*----- + * Rijndael key schedule function. Takes 16-byte key and creates + * all Rijndael's internal subkeys ready for encryption. + *-----*/ + +void RijndaelKeySchedule( u8 key[16] ) +{ + u8 roundConst; + int i, j; + + /* first round key equals key */ + for (i=0; i<16; i++) + roundKeys[0][i & 0x03][i>>2] = key[i]; + + roundConst = 1; + + /* now calculate round keys */ + for (i=1; i<11; i++) + { + roundKeys[i][0][0] = S[roundKeys[i-1][1][3]] + ^ roundKeys[i-1][0][0] ^ roundConst; + roundKeys[i][1][0] = S[roundKeys[i-1][2][3]] + ^ roundKeys[i-1][1][0]; + roundKeys[i][2][0] = S[roundKeys[i-1][3][3]] + ^ roundKeys[i-1][2][0]; + roundKeys[i][3][0] = S[roundKeys[i-1][0][3]] + ^ roundKeys[i-1][3][0]; + + for (j=0; j<4; j++) + { + roundKeys[i][j][1] = roundKeys[i-1][j][1] ^ roundKeys[i][j][0]; + roundKeys[i][j][2] = roundKeys[i-1][j][2] ^ roundKeys[i][j][1]; + roundKeys[i][j][3] = roundKeys[i-1][j][3] ^ roundKeys[i][j][2]; + } + } +} + +``` + +``` + /* update round constant */ + roundConst = Xtime[roundConst]; + } + + return; +} /* end of function RijndaelKeySchedule */ + +/* Round key addition function */ +void KeyAdd(u8 state[4][4], u8 roundKeys[11][4][4], int round) +{ + int i, j; + + for (i=0; i<4; i++) + for (j=0; j<4; j++) + state[i][j] ^= roundKeys[round][i][j]; + + return; +} + +/* Byte substitution transformation */ +int ByteSub(u8 state[4][4]) +{ + int i, j; + + for (i=0; i<4; i++) + for (j=0; j<4; j++) + state[i][j] = S[state[i][j]]; + + return 0; +} + +/* Row shift transformation */ +void ShiftRow(u8 state[4][4]) +{ + u8 temp; + + /* left rotate row 1 by 1 */ + temp = state[1][0]; + state[1][0] = state[1][1]; + state[1][1] = state[1][2]; + state[1][2] = state[1][3]; + state[1][3] = temp; + + /* left rotate row 2 by 2 */ + temp = state[2][0]; + state[2][0] = state[2][2]; + state[2][2] = temp; + temp = state[2][1]; + state[2][1] = state[2][3]; + state[2][3] = temp; + + /* left rotate row 3 by 3 */ + temp = state[3][0]; + state[3][0] = state[3][3]; + state[3][3] = state[3][2]; + state[3][2] = state[3][1]; + state[3][1] = temp; + + return; +} + +/* MixColumn transformation*/ +void MixColumn(u8 state[4][4]) +{ + u8 temp, tmp, tmp0; + int i; + + /* do one column at a time */ + for (i=0; i<4;i++) + { + temp = state[0][i] ^ state[1][i] ^ state[2][i] ^ state[3][i]; + tmp0 = state[0][i]; +``` + +``` + + /* Xtime array does multiply by x in GF2^8 */ + tmp = Xtime[state[0][i] ^ state[1][i]]; + state[0][i] ^= temp ^ tmp; + + tmp = Xtime[state[1][i] ^ state[2][i]]; + state[1][i] ^= temp ^ tmp; + + tmp = Xtime[state[2][i] ^ state[3][i]]; + state[2][i] ^= temp ^ tmp; + + tmp = Xtime[state[3][i] ^ tmp0]; + state[3][i] ^= temp ^ tmp; + } + + return; +} + +/----- + * Rijndael encryption function. Takes 16-byte input and creates + * 16-byte output (using round keys already derived from 16-byte + * key). + *-----*/ + +void RijndaelEncrypt( u8 input[16], u8 output[16] ) +{ + u8 state[4][4]; + int i, r; + + /* initialise state array from input byte string */ + for (i=0; i<16; i++) + state[i & 0x3][i>>2] = input[i]; + + /* add first round key */ + KeyAdd(state, roundKeys, 0); + + /* do lots of full rounds */ + for (r=1; r<=9; r++) + { + ByteSub(state); + ShiftRow(state); + MixColumn(state); + KeyAdd(state, roundKeys, r); + } + + /* final round */ + ByteSub(state); + ShiftRow(state); + KeyAdd(state, roundKeys, r); + + /* produce output byte string from state array */ + for (i=0; i<16; i++) + { + output[i] = state[i & 0x3][i>>2]; + } + + return; +} /* end of function RijndaelEncrypt */ + +``` + +# Annex 4: Rijndael Listing - 32-Bit Word Oriented + +``` + +/*----- + * Rijndael Implementation + *----- + * + * A sample 32-bit orientated implementation of Rijndael, the + * suggested kernel for the example 3GPP authentication and key + * agreement functions. + * + * This implementation draws on the description in section 5.2 of + * the AES proposal and also on the implementation by + * Dr B. R. Gladman 9th October 2000. + * It uses a number of large (4k) lookup tables to implement the + * algorithm in an efficient manner. + * + * Note: in this implementation the State is stored in four 32-bit + * words, one per column of the State, with the top byte of the + * column being the _least_ significant byte of the word. + * + *-----*/ + +#define LITTLE_ENDIAN /* For INTEL architecture */ + +typedef unsigned char u8; +typedef unsigned int u32; + +/* Circular byte rotates of 32 bit values */ + +#define rot1(x) ((x << 8) | (x >> 24)) +#define rot2(x) ((x << 16) | (x >> 16)) +#define rot3(x) ((x << 24) | (x >> 8)) + +/* Extract a byte from a 32-bit u32 */ + +#define byte0(x) ((u8)(x)) +#define byte1(x) ((u8)(x >> 8)) +#define byte2(x) ((u8)(x >> 16)) +#define byte3(x) ((u8)(x >> 24)) + +/* Put or get a 32 bit u32 (v) in machine order from a byte * + * address in (x) */ + +#ifdef LITTLE_ENDIAN + +#define u32_in(x) (*(u32*)(x)) +#define u32_out(x,y) (*(u32*)(x) = y) + +#else + +/* Invert byte order in a 32 bit variable */ + +__inline u32 byte_swap(const u32 x) +{ + return rot1(x) & 0x00ff00ff | rot3(x) & 0xff00ff00; +} + +__inline u32 u32_in(const u8 x[]) +{ + return byte_swap(*(u32*)x); +}; + +__inline void u32_out(u8 x[], const u32 v) +{ + *(u32*)x = byte_swap(v); +}; + +#endif + +/*----- The lookup tables -----*/ + +static u32 rnd_con[10] = +{ + 0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0x80, 0x1B, 0x36 +}; + +``` + +``` + +static u32 ft_tab[4][256] = +{ +{ +0xA56363C6, 0x847C7CF8, 0x997777EE, 0x8D7B7BF6, 0x0DF2F2FF, 0xBD6B6BD6, 0xB16F6FDE, 0x54C5C591, +0x50303060, 0x03010102, 0xA96767CE, 0x7D2B2B56, 0x19FEFE7, 0x62D7D7B5, 0xE6ABAB4D, 0x9A7676EC, +0x45CACA8F, 0x9D82821F, 0x40C9C989, 0x877D7DFA, 0x15FAFAEF, 0xEB5959B2, 0xC947478E, 0x0BF0F0FB, +0xECADAD41, 0x67D4D4B3, 0xFDA2A25F, 0xEAFAFAF45, 0xBF9C9C23, 0xF7A4A453, 0x967272E4, 0x5BC0C09B, +0xC2B7B775, 0x1CFDDE1, 0xAE93933D, 0x6A26264C, 0x5A36366C, 0x413F3F7E, 0x02F7F7F5, 0x4FCCCC83, +0x5C343468, 0xF4A5A551, 0x34E5E5D1, 0x08F1F1F9, 0x937171E2, 0x73D8D8AB, 0x53313162, 0x3F15152A, +0x0C040408, 0x52C7C795, 0x65232346, 0x5EC3C39D, 0x28181830, 0xA1969637, 0x0F05050A, 0xB59A9A5F, +0x0907070E, 0x36121224, 0x9B80801B, 0x3DE2E2DF, 0x26EBEBCD, 0x6927274E, 0xCDB2B27F, 0x9F7575EA, +0x1B090912, 0x9E83831D, 0x742C2C58, 0x2E1A1A34, 0x2D1B1B36, 0xB26E6EDC, 0xEE5A5AB4, 0xFBA0A05B, +0xF65252A4, 0x4D3B3B76, 0x61D6D6B7, 0xCEB3B37D, 0x7B292952, 0x3EE3E3DD, 0x712F2F5E, 0x97848413, +0xFF5555A6, 0x68B1D1B9, 0x00000000, 0x2CEDEDCE, 0x60202040, 0x1FFCFCE3, 0xC8B1B179, 0xED5B5BB6, +0xEB6A6AD4, 0x46CBCB8D, 0xD9BEBE67, 0x4B393972, 0xDE4A4A94, 0xD44C4C98, 0xE85858B0, 0x4ACFCF85, +0x6BD0D0BB, 0x2AEFEFC5, 0xE5AAAA4F, 0x16FBFBED, 0xC5434386, 0xD74D4D9A, 0x55333366, 0x94858511, +0xFCF4545A, 0x10F9F9E9, 0x06020204, 0x817F7FFE, 0xF05050A0, 0x443C3C78, 0xBA9F9F25, 0xE3A8A84B, +0x3F35151A, 0xF8A3A35E, 0x0C404080, 0x8A8F8F05, 0x2D92923F, 0xBC9D9D21, 0x48383838, 0x04F5F5F1, +0xFDFCBC63, 0xC1B6B677, 0x75DADA8F, 0x63212142, 0x30101020, 0x1AFFFFE5, 0x0EF3F3FD, 0x6DD2D2BF, +0x4CCDCD81, 0x140C0C18, 0x35131326, 0x2FECECC3, 0xE15F5FBE, 0xA2979735, 0xCC444488, 0x3917172E, +0x57C4C493, 0xF2A7A755, 0x827E7EFC, 0x473D3D7A, 0xAC6464C8, 0xE75D5DBA, 0x2B191932, 0x957373E6, +0xA06060C0, 0x68B1D1B9, 0x00000000, 0x7FDCDC7F, 0x66222244, 0x7E2A2A54, 0x909090B0, 0x8B6868D0, +0xCA46468C, 0x29EEEEC7, 0xD3B8B8B6, 0x3C141428, 0x79DEDEA7, 0xE25E5EBC, 0x1D0B0B16, 0x76DBDBAD, +0x3B0E0E0D, 0x56323264, 0x4E3A3A74, 0x1E0A0A14, 0xDB494992, 0x0A06060C, 0x6C242448, 0xE45C5CB8, +0x5DC2C29F, 0x6ED3D3BD, 0xEFACAC43, 0xA66262C4, 0xA8919139, 0xA4959531, 0x37E4E4D3, 0x8B7979F2, +0x32E7E7D5, 0x4C8C8C8C, 0x5937376E, 0xB76D6DDB, 0x8C88D01, 0x64D5D5B1, 0xD24E4E9C, 0xE0A9A949, +0xB46C6CD8, 0xFA5656AC, 0x07F4F4F3, 0x25EAEACF, 0xAF6565CA, 0x8E7A7AF4, 0xE9AEAE47, 0x18080810, +0xD5BABA6F, 0x887878F0, 0x6F25254A, 0x722E2E5C, 0x241C1C38, 0xF1A6A657, 0xC7B4B473, 0x51C6C697, +0x23E8E8B8, 0x7CDDDDA1, 0x9C7474E8, 0x211F1F3E, 0xDD4B4B96, 0xDCDBDB61, 0x86B8B8B0, 0x858A8A0F, +0x907070E0, 0x423E3E5C, 0x0C404080, 0x8A6666C5, 0x2D848490, 0x05030306, 0x01F6F6F7, 0x120E0E1C, +0xA36161C2, 0x5F35356A, 0xF95757AE, 0xD0B9B969, 0x91868617, 0x58C1C199, 0x271D1D3A, 0xB99E9E27, +0x3E1E1E1D, 0x13F8F8EB, 0xB398982B, 0x33111122, 0xBB6969D2, 0x70D9D9A9, 0x898E8E07, 0xA7949433, +0xB69B9B2D, 0x221E1E3C, 0x92878715, 0x20E9E9C9, 0x49CECE87, 0xFF5555AA, 0x78282850, 0x7ADFDFA5, +0x08F8C03F, 0xF8A1A159, 0x80898909, 0x170D0D1A, 0xDABFBF65, 0x31E6E6D7, 0xC6424284, 0xB86868D0, +0xC3414182, 0xB0999929, 0x772D2D5A, 0x110F0F1E, 0xCBB0B07B, 0xFC5454A8, 0xD6BBBB6D, 0x3A16162C +}, +{ +0x6363C6A5, 0x7C7CF884, 0x7777EE99, 0x7B7BF68D, 0xF2F2FF0D, 0x6B6BD6BD, 0x6F6FDEB1, 0x5C5C59154, +0x30306050, 0x01010203, 0x6767CEA9, 0x2B2B567D, 0xFEFE719, 0xD7D7B562, 0xABAB4DE6, 0x7676EC9A, +0xCACA8F45, 0x82821F9D, 0xC9C98940, 0x7D7DFA87, 0xFAFAEF15, 0x5959B2EB, 0x47478EC9, 0xF0F0FB0B, +0xADAD41EC, 0xD4D4B367, 0x2A2A25FD, 0xFAFAF45E, 0x9C9C23BF, 0xA4A453F7, 0x7272E496, 0xC0C09B5B, +0xB7B775C2, 0xFDFDE11C, 0x93933DAE, 0x26264C6A, 0x36366C5A, 0x3F3F7E41, 0xF7F7F502, 0xCCCC834F, +0x3434685C, 0xA5A551F4, 0xE5E5D134, 0xF1F1F908, 0x7171E293, 0xD8D8AB73, 0x31316253, 0x15152A3F, +0x0404080C, 0xC7C79552, 0x23234665, 0xC3C39D5E, 0x18183028, 0x969637A1, 0x05050A0F, 0x9A9A2FB5, +0x07070E09, 0x12122436, 0x80801B9B, 0xE2E2DF3D, 0xEBEBCD26, 0x27274E69, 0xB2B27FCD, 0x7575EA9F, +0x0909121B, 0x83831D9E, 0x2C2C5874, 0x1A1A342E, 0x1B1B362D, 0x6E6EDCB2, 0x5A5A5AB4, 0xA0A05BFB, +0x5252A4F6, 0x3B3B764D, 0xD6D6B761, 0xB3B37DCE, 0x2929527B, 0x3E3E3DD3E, 0x2F2F5E7E, 0x84841397, +0x5353A6F5, 0xD1D1B968, 0x00000000, 0xEDEDCE12, 0x20204060, 0xFCFCE31F, 0xB1B179C8, 0x5B5B6ED, +0x6A6AD4BE, 0xCBCB8D46, 0xEBE67D9, 0x3939724B, 0x4A4A94DE, 0x4C4C98D4, 0x5858B0E8, 0xCFCF854A, +0xD0D04B6B, 0xEFEFC52A, 0xAAAA4FE5, 0xFBFBED16, 0x434386C5, 0x4D4D9AD7, 0x33336655, 0x85851194, +0x45455ACF, 0xF9F9E910, 0x02020406, 0x7F7FFE81, 0x5050A0F0, 0x3C3C7844, 0x9F9F25BA, 0xA8A84BE3, +0x5151A2F3, 0xA3A35DFE, 0x404080C0, 0x8F8F058A, 0x92923FAD, 0x9D9D21BC, 0x38387048, 0xF5F5F104, +0xBCBC63DF, 0xB6B677C1, 0xDADA8F75, 0x21214263, 0x10102030, 0xFFFFE51A, 0xF3F3FD0E, 0xD2D2BF6D, +0xCDCD814C, 0x0C0C1814, 0x13132635, 0xECECC32F, 0x5F5FBEE1, 0x979735A2, 0x444488CC, 0x171712E39, +0x0C404937, 0xA7A755F2, 0x7E7EFC82, 0x3D3D7A47, 0x6464C8AC, 0x5D5DBBA7, 0x1919322A, 0x7373E695, +0x6060C0A0, 0x81811998, 0x4F4F9ED1, 0xDCDC3A7F, 0x22224466, 0x2A2A547E, 0x90903BAB, 0x88880B83, +0x46468CCA, 0xEEEEC729, 0xB8B86BD3, 0x1414283C, 0xEDEDEA79, 0x5E5EBCE2, 0x0B0B161D, 0xDBDBAD76, +0xE0E0DB3B, 0x32326456, 0x3A3A744E, 0x0A0A141E, 0x494992DB, 0x06060C0A, 0x2424486C, 0x5C5CB8E4, +0xC2C29F5D, 0xD3D3BD6E, 0xACAC43EF, 0x6262C4A6, 0x919139A8, 0x959531A4, 0xE4E4D337, 0x7979F2B8, +0xE7E7D532, 0xC8C88B43, 0x37376E59, 0x6D6DDAB7, 0x8D8D018C, 0xD5D5B164, 0x4E4E9CD2, 0xA9A949E0, +0x6C6CD8B4, 0x5656ACFA, 0xF4F4F307, 0xEAEACF25, 0x6565CAAF, 0x7A7AF48E, 0xAEAE47E9, 0x08081018, +0xBABA6FD5, 0x7878F088, 0x25254A6F, 0x2E2E5C72, 0x1C1C3824, 0xA6A657F1, 0xB4B473C7, 0xC6C69751, +0xE8E8CB23, 0xDDDDA17C, 0x7474E89C, 0x1F1F3E21, 0x4B4B96DD, 0xBDBD61DC, 0x8B8B0D86, 0x8A8A0F85, +0x7070E090, 0x3E3E7C42, 0xB5B571C4, 0x6666CCAA, 0x484890D8, 0x03030605, 0xF6F6F701, 0xE0E0E1C12, +0x6161C2A3, 0x35356A5F, 0x5757AEF9, 0xB9B969D0, 0x86861791, 0xC1C19958, 0x1D1D3A27, 0x9E9E27B9, +0xE1E1D938, 0xF8F8EB13, 0x98982BB3, 0x11112233, 0x6969D2BB, 0xD9D9A970, 0x8E8E0789, 0x949433A7, +0x9B9B2D36, 0x1E1E3C22, 0x87871592, 0xE9E9C920, 0xCECE8749, 0x5555AAFF, 0x28285079, 0xDFDF0A57A, +0x8C8C038F, 0xA1A159F8, 0x89890980, 0x0D0D1A17, 0xBFBF65DA, 0xE6E6D731, 0x424284C6, 0x6868D0B8, +0x414182C3, 0x999929B0, 0x2D2D5A77, 0x0F0F1E11, 0xB0B07BCB, 0x5454A8FC, 0xBDBD6DD6, 0x16162C3A +}, +{ +0x6363A563, 0x7C7CF847C, 0x77EE9977, 0x7B7BF68D7B, 0xF2F2FF0DF2, 0x6B6BD6BD6B, 0x6F6FDEB16F, 0x5C59154C5, +0x3030605030, 0x0101020301, 0x6767CEA967, 0x2B2B567D2B, 0xFEFE719FE, 0xD7D7B562D7, 0xABAB4DE6AB, 0x7676EC9A76, +0xCACA8F45CA, 0x821F9D82, 0xC9C98940C9, 0x7D7DFA877D, 0xFAFAEF15FA, 0x5959B2EB59, 0x47478EC947, 0xF0F0FB0F0, +0xADAD1EAD, 0xD4D4B367D4, 0x2A2A25FD2A, 0x0A0A45EAE, 0x9C9C23BF9C, 0xA4A453F7A4, 0x7272E49672, 0xC0C09B5B0, +0xB775C2B7, 0xFDFDE11CFD, 0x93933DAE93, 0x26264C6A26, 0x36366C5A36, 0x3F3F7E413F, 0xF7F7F502F7, 0xCC834FCC, +0x3434685C34, 0xA551F4A5, 0xE5E5D134E5, 0xF1F1F908F1, 0x7171E29371, 0xD8D8AB73D8, 0x3131625331, 0x15152A3F15, + +``` + +``` + +0x04080C04, 0x079552C7, 0x23466523, 0xC39D5EC3, 0x18302818, 0x9637A196, 0x050A0F05, 0x9A2FB59A, +0x070E0907, 0x12243612, 0x801B9B80, 0xE2DF3DE2, 0xEBCD26EB, 0x274E6927, 0xB27FCDB2, 0x75EA9F75, +0x09121B09, 0x831D9E83, 0x2C58742C, 0x1A342E1A, 0x1B362D1B, 0x6EDCB26E, 0x5AB4EE5A, 0xA05BFA0, +0x52A4F652, 0x3B764D3B, 0xD6B761D6, 0xB37DCEB3, 0x29527B29, 0xE3DD3EE3, 0x2F5E712F, 0x84139784, +0x53A6F553, 0xD1B968D1, 0x00000000, 0xEDC12CED, 0x20406020, 0xFCE31FFC, 0xB179C8B1, 0x5BB6ED5B, +0x6AD4BE6A, 0xCB8D46CB, 0xEB67D9BE, 0x39724B39, 0x4A94DE4A, 0x4C98D44C, 0x58B0E858, 0xFCF854ACF, +0xD0BB6BD0, 0xEFC52AEF, 0xAA4FE5AA, 0xFBED16FB, 0x4386C543, 0x4D9AD74D, 0x33665533, 0x85119485, +0x458ACF45, 0xF9E910F9, 0x02040602, 0x7FFE817F, 0x50A0F050, 0x3C78443C, 0x9F25BA9F, 0xA84BE3A8, +0x51A2F351, 0xA35DFFEA3, 0x4080C040, 0x8F058A8F, 0x923FAD92, 0x9D21BC9D, 0x38704838, 0xF5F104F5, +0xBC63DFBC, 0xB677C1B6, 0xDAADF75A, 0x21426321, 0x10203010, 0xFFE51AFF, 0xF3FD0EF3, 0xD2BF6DD2, +0xCD814CCD, 0x0C18140C, 0x13263513, 0xECC32FEC, 0x5FBBE15F, 0x9735A297, 0x4488CC44, 0x17E39177, +0xC49357C4, 0xA755F2A7, 0x7EFC827E, 0x3D7A473D, 0x64C8AC64, 0x5DBAE75D, 0x19322B19, 0x73E69573, +0x60C0A060, 0x81199881, 0x4F9ED14F, 0xDCA37FDC, 0x22446622, 0x2A547E2A, 0x903BAB90, 0x880B8388, +0x468CCA46, 0xEEC729EE, 0xB86BD3B8, 0x14283C14, 0xDEA779DE, 0x5EBCE25E, 0x0B161D0B, 0xDBAD76DB, +0xE2645632, 0x32645632, 0x3A744E3A, 0x0A141E0A, 0x4992DB49, 0x060C0A06, 0x24486C24, 0x5C8E45C5, +0xC29F5DC2, 0xD3BD6ED3, 0xAC43EFAC, 0x62C4A662, 0x9139A891, 0x9531A495, 0xE4D337E4, 0x79F28B79, +0xE7D532E7, 0xC88B43C8, 0x376E5937, 0x6DDAB76D, 0x8D018C8D, 0xD5B164D5, 0x4E9CD24E, 0xA949E0A9, +0x6CD8B46C, 0x56ACFA56, 0xF4F307F4, 0xEACF25EA, 0x65CAAF65, 0x7AF48E7A, 0xAE47E9AE, 0x08101808, +0x1A1D93C8, 0x3F6B13F8, 0x9525A6F2, 0x11223311, 0x3C8241C1, 0xA657F1A6, 0xB473C7B4, 0x9751C6C6, +0xE8CB23E8, 0xDDA17CDD, 0x74E89C74, 0x1F3E211F, 0x4B96DD4B, 0xBD61DCBD, 0x8B0D868B, 0xA80F858A, +0x70E09070, 0x37C423E, 0xB571C4B5, 0x66CCAA66, 0x4890D848, 0x03060503, 0xF6F701F6, 0x0E1C120E, +0x61C2A361, 0x356A5F35, 0x57AEF957, 0xB969D0B9, 0x86179186, 0xC19958C1, 0x1D3A271D, 0x9E27B99E, +0x12E110F1, 0x0F1E110F, 0x07BCBB0B, 0x0D9A97D9, 0x8E07898E, 0x947B99E9, 0x9B2DB69B, 0x1E3C221E, +0x87159287, 0xE9C920E9, 0xCE8749CE, 0x55AAFF55, 0x28507828, 0xDFA57ADF, 0x8C038F8C, 0xA159F8A1, +0x89098089, 0x0D1A170D, 0xBF65DAF, 0xE6D731E6, 0x4284C642, 0x68D0B868, 0x4182C341, 0x9929B099, +0x2D5A772D, 0x0F1E110F, 0xB07BCBB0, 0x54A8FC54, 0xBB6DD6BB, 0x162C3A16 +}, +{ +0xC6A56363, 0xF8847C7C, 0xEE997777, 0xF68D7B7B, 0xFF0DF2F2, 0xD6BD6B6B, 0xEB16F6F6, 0x9154C5C5, +0x60503030, 0x02030101, 0xCEA96767, 0x567D2B2B, 0xE719FEFE, 0xB562D7D7, 0x4DE6ABAB, 0xEC9A7676, +0x8F45CACA, 0x1F9D8282, 0x8940C9C9, 0xFA877D7D, 0xEB15FAFA, 0xB2EB5959, 0x8E9C9477, 0xFB0B4F0F, +0x41ECADAD, 0xB367D4D4, 0x5FFDA2A2, 0x45EAAFAF, 0x23BF9C9C, 0x53F7A4A4, 0xE4967272, 0x9B5BC0C0, +0x75C2B7B7, 0xE11CFDFD, 0x3DAE9393, 0x4C6A2626, 0x6C5A3636, 0x7E413F3F, 0xF502F7F7, 0x834FCCCC, +0x685C3434, 0x51F4A5A5, 0xD134E5E5, 0xF908F1F1, 0xE2937171, 0xAB73D8D8, 0x62533131, 0x2A3F1515, +0x080C0404, 0x9525C7C7, 0x46652323, 0x9D5EC3C3, 0x362D1B1B, 0x37A19696, 0xA0F05050, 0x2E391919, +0x0E090707, 0x24361212, 0x1B9B8080, 0xDF3DE2E2, 0xCD26EBEB, 0x4E692727, 0x7FCDB2B2, 0xEA9F7575, +0x121B0909, 0x1D9E8383, 0x58742C2C, 0x342E1A1A, 0x362D1B1B, 0xDCB26E6E, 0xB4EE5A5A, 0x5BFA0A0, +0xA4F65252, 0x764D3B3B, 0xB761D6D6, 0x7DCEB3B3, 0x527B2929, 0xDD3EE3E3, 0x5E712F2F, 0x13978484, +0xA6F5553, 0xB968D1D1, 0x00000000, 0xC12CEDD, 0x40602020, 0xE31FFFC, 0x79C8B1B1, 0xB6ED5B5B, +0xD4BE6A6A, 0x8D46CBCB, 0x67D9BEBE, 0x724B3939, 0x94DE4A4A, 0x98D44C4C, 0xB0E85858, 0x854ACFCF, +0xBB6BD0D0, 0xC52AEFEF, 0x4FE5AAAA, 0xED16FBFB, 0x86C54343, 0x9AD74D4D, 0x66553333, 0x11948585, +0x8ACF4545, 0xE910F9F9, 0x04060202, 0xF817F7F7, 0xA0F05050, 0x78443C3C, 0x25BA9F9F, 0x4BE3A8A8, +0xA2F35151, 0x5DFFEA3A, 0x80C04040, 0x058A8F8F, 0x3FAD9292, 0x21BC9D9D, 0x70483838, 0xF104F5F5, +0x63DFBCBC, 0x77C1B6B6, 0xF8F75DAD, 0x42632121, 0x20301010, 0xE51AFFFF, 0xFDF0EF3F, 0xF6DD2D2D, +0x814CCDCD, 0x18140C0C, 0x26351313, 0xC32FECEC, 0xBEE15F5F, 0x35A29797, 0x88CC4444, 0x2E391717, +0x9357C4C4, 0x55F2A7A7, 0xFC827E7E, 0x7A473D3D, 0xC8AC6464, 0xBAE75D5D, 0x322B1919, 0xE6957373, +0xC0A06060, 0x01998181, 0x9ED14F4F, 0xA37FDCDC, 0x44662222, 0x547E2A2A, 0x3BAB9090, 0x0B838888, +0x8CCA4646, 0x0C729EEE, 0x6BD3B8B8, 0x283C1414, 0xA779DEDE, 0xBCE25E5E, 0x161D0B0B, 0xAD76DBDB, +0xDB3BE0E0, 0x64563232, 0x744E3A3A, 0x141E0A0A, 0x92DB4949, 0x0C0A0606, 0x486C2424, 0xB8E45C5C, +0x9F5DC2C2, 0xBD6ED3D3, 0x43EFACAC, 0xC4A66262, 0x39A89191, 0x31A49595, 0xD337E4E4, 0xF28B7979, +0xD532E7E7, 0xB843C8C8, 0x6E593737, 0xDAB76D6D, 0x018C8D8D, 0xB164D5D5, 0x9CD24E4E, 0x49E0A9A9, +0xD8B46C6C, 0xACFA5656, 0xF307F4F4, 0xFCF25EAE, 0xCAAF6565, 0xF48E7A7A, 0x47E9AEAE, 0x10180808, +0x6FD5BABA, 0xF0887878, 0x4A6F2525, 0x5C722E2E, 0x38241C1C, 0x57F1A6A6, 0x73C7B4B4, 0x9751C6C6, +0xCB23E8E8, 0xA17CDDDD, 0x89C74747, 0x3E211F1F, 0x96DD4B4B, 0x61DCBDBD, 0x0D868B8B, 0x0F858A8A, +0xE0907070, 0x7C423E3E, 0x71C4B5B5, 0xCCAA6666, 0x90D84848, 0x06050303, 0xF701F6F6, 0x1C120E0E, +0xC2A36161, 0x6A5F3535, 0xAEF95757, 0x69D0B9B9, 0x17918686, 0x9958C1C1, 0x3A271D1D, 0x27B99E9E, +0xD938E1E1, 0xEB13F8F8, 0x2BB39898, 0x22331111, 0xD2BB6969, 0xA970D9D9, 0x07898E8E, 0x33A79494, +0x2DB69B9B, 0x3C221E1E, 0x15928787, 0xC920E9E9, 0x8749CECE, 0xAAFF5555, 0x50782828, 0xA57ADFD, +0x038F8C8C, 0x59F8A1A1, 0x09808989, 0x1A170D0D, 0x65DAFBF, 0xD731E6E6, 0x84C64242, 0xD0B86868, +0x82C34141, 0x29B09999, 0x5A772D2D, 0x1E110F0F, 0x7BCBB0B0, 0xA8FC5454, 0x6DD6BBB, 0x2C3A1616 +} +}; + +static u32 fl_tab[4][256] = +{ +{ +0x00000063, 0x0000007C, 0x00000077, 0x0000007B, 0x000000F2, 0x0000006B, 0x0000006F, 0x000000C5, +0x00000030, 0x00000001, 0x00000067, 0x0000002B, 0x000000FE, 0x000000D7, 0x000000AB, 0x00000076, +0x000000CA, 0x00000082, 0x000000C9, 0x0000007D, 0x000000FA, 0x00000059, 0x00000047, 0x000000F0, +0x000000AD, 0x000000D4, 0x000000A2, 0x000000AF, 0x0000009C, 0x000000A4, 0x00000072, 0x000000C0, +0x000000B7, 0x000000FD, 0x00000093, 0x00000026, 0x00000036, 0x0000003F, 0x000000F7, 0x000000CC, +0x00000034, 0x000000A5, 0x000000E5, 0x000000F1, 0x00000071, 0x000000D8, 0x00000031, 0x00000015, +0x00000004, 0x000000C7, 0x00000023, 0x000000C3, 0x00000018, 0x00000096, 0x00000005, 0x0000009A, +0x00000007, 0x00000012, 0x00000080, 0x000000E2, 0x000000EB, 0x00000027, 0x000000B2, 0x00000075, +0x00000009, 0x00000083, 0x0000002C, 0x0000001A, 0x0000001B, 0x0000006E, 0x0000005A, 0x000000A0, +0x00000052, 0x0000003B, 0x000000D6, 0x000000B3, 0x00000029, 0x000000E3, 0x0000002F, 0x00000084, +0x00000053, 0x000000D1, 0x00000000, 0x000000ED, 0x00000020, 0x000000FC, 0x000000B1, 0x0000005B, +0x0000006A, 0x000000CB, 0x000000BE, 0x00000039, 0x0000004A, 0x0000004C, 0x00000058, 0x000000CF, + +``` + +``` +0x000000D0, 0x000000EF, 0x000000AA, 0x000000FB, 0x00000043, 0x0000004D, 0x00000033, 0x00000085, +0x00000045, 0x000000F9, 0x00000002, 0x0000007F, 0x00000050, 0x0000003C, 0x0000009F, 0x000000A8, +0x00000051, 0x000000A3, 0x00000040, 0x0000008F, 0x00000092, 0x0000009D, 0x00000038, 0x000000F5, +0x000000BC, 0x000000B6, 0x000000DA, 0x00000021, 0x00000010, 0x000000FF, 0x000000F3, 0x000000D2, +0x000000CD, 0x0000000C, 0x00000013, 0x000000EC, 0x0000005F, 0x00000097, 0x00000044, 0x00000017, +0x000000C4, 0x000000A7, 0x0000007E, 0x0000003D, 0x00000064, 0x0000005D, 0x00000019, 0x00000073, +0x00000060, 0x00000081, 0x0000004F, 0x000000DC, 0x00000022, 0x0000002A, 0x00000090, 0x00000088, +0x00000046, 0x000000EE, 0x000000B8, 0x00000014, 0x000000DE, 0x0000005E, 0x0000000B, 0x000000DB, +0x000000E0, 0x00000032, 0x0000003A, 0x0000000A, 0x00000049, 0x00000006, 0x00000024, 0x0000005C, +0x000000C2, 0x000000D3, 0x000000AC, 0x00000062, 0x00000091, 0x00000095, 0x000000E4, 0x00000079, +0x000000E7, 0x000000C8, 0x00000037, 0x0000006D, 0x0000008D, 0x000000D5, 0x0000004E, 0x000000A9, +0x0000006C, 0x00000056, 0x000000F4, 0x000000EA, 0x00000065, 0x0000007A, 0x000000AE, 0x00000008, +0x000000BA, 0x00000078, 0x00000025, 0x0000002E, 0x0000001C, 0x000000A6, 0x000000B4, 0x000000C6, +0x000000E8, 0x000000DD, 0x00000074, 0x0000001F, 0x0000004B, 0x000000BD, 0x0000008B, 0x0000008A, +0x00000070, 0x0000003E, 0x000000B5, 0x00000066, 0x00000048, 0x00000003, 0x000000F6, 0x000000E6, +0x00000061, 0x00000035, 0x00000057, 0x000000B9, 0x00000086, 0x000000C1, 0x0000001D, 0x0000009E, +0x000000E1, 0x000000F8, 0x00000098, 0x00000011, 0x00000069, 0x000000D9, 0x0000008E, 0x00000094, +0x0000009B, 0x0000001E, 0x00000087, 0x000000E9, 0x000000CE, 0x00000055, 0x00000028, 0x000000DF, +0x0000008C, 0x000000A1, 0x00000089, 0x000000D1, 0x000000BF, 0x000000E6, 0x00000042, 0x00000068, +0x00000041, 0x00000099, 0x0000002D, 0x0000000F, 0x000000B0, 0x00000054, 0x000000BB, 0x00000016 +}, +``` + +``` +{ +0x00006300, 0x00007C00, 0x00007700, 0x00007B00, 0x0000F200, 0x00006B00, 0x00006F00, 0x0000C500, +0x00003000, 0x00001000, 0x00006700, 0x00002B00, 0x0000FE00, 0x0000D700, 0x0000AB00, 0x00007600, +0x0000CA00, 0x00008200, 0x0000C900, 0x00007D00, 0x0000FA00, 0x00005900, 0x00004700, 0x0000F000, +0x0000AD00, 0x0000D400, 0x0000A200, 0x0000AF00, 0x00009C00, 0x0000A400, 0x00007200, 0x0000C000, +0x0000B700, 0x0000FD00, 0x00009300, 0x00002600, 0x00003600, 0x00003F00, 0x0000F700, 0x0000CC00, +0x00003400, 0x0000A500, 0x0000E500, 0x0000F100, 0x00007100, 0x0000D800, 0x00003100, 0x00001500, +0x00004000, 0x0000C700, 0x00002300, 0x0000C300, 0x00001800, 0x00009600, 0x00005000, 0x00009A00, +0x00000700, 0x00001200, 0x00008000, 0x0000E200, 0x0000EB00, 0x00002700, 0x0000B200, 0x00007500, +0x00000900, 0x00008300, 0x00002C00, 0x00001A00, 0x00001B00, 0x00006E00, 0x00005A00, 0x0000A000, +0x00005200, 0x00003B00, 0x0000D600, 0x0000B300, 0x00002900, 0x0000E300, 0x00002F00, 0x00008400, +0x00005300, 0x0000D100, 0x00000000, 0x0000ED00, 0x00002000, 0x0000FC00, 0x0000B100, 0x00005B00, +0x00006A00, 0x0000CB00, 0x0000BE00, 0x00003900, 0x00004A00, 0x00004C00, 0x00005800, 0x0000CF00, +0x0000D000, 0x0000EF00, 0x0000AA00, 0x0000FB00, 0x00004300, 0x00004D00, 0x00003300, 0x00008500, +0x00004500, 0x0000F900, 0x00000200, 0x00007F00, 0x00005000, 0x00003C00, 0x00009F00, 0x0000A800, +0x00005100, 0x0000A300, 0x00004000, 0x00008F00, 0x00009200, 0x00009D00, 0x00003800, 0x0000F500, +0x0000BC00, 0x0000B600, 0x0000DA00, 0x00000200, 0x00001000, 0x0000FF00, 0x0000F300, 0x0000D200, +0x0000CD00, 0x00000C00, 0x00001300, 0x0000EC00, 0x00005F00, 0x00009700, 0x00004400, 0x00001700, +0x0000C400, 0x0000A700, 0x00007E00, 0x00003D00, 0x00006400, 0x00005D00, 0x00001900, 0x00007300, +0x00006000, 0x00008100, 0x00004F00, 0x0000DC00, 0x00002200, 0x00002A00, 0x00009000, 0x00008800, +0x00004600, 0x0000EE00, 0x0000B800, 0x00001400, 0x0000DE00, 0x00005E00, 0x00000B00, 0x0000DB00, +0x0000E000, 0x00003200, 0x00003A00, 0x00000A00, 0x00004900, 0x00000600, 0x00002400, 0x00005C00, +0x0000C200, 0x0000D300, 0x0000AC00, 0x00006200, 0x00009100, 0x00009500, 0x0000E400, 0x00007900, +0x0000E700, 0x0000C800, 0x00003700, 0x00006D00, 0x00008D00, 0x0000D500, 0x00004E00, 0x0000A900, +0x00006C00, 0x00005600, 0x0000F400, 0x0000EA00, 0x00006500, 0x00007A00, 0x0000AE00, 0x00000800, +0x0000BA00, 0x00007800, 0x00002500, 0x00002E00, 0x00001C00, 0x0000A600, 0x0000B400, 0x0000C600, +0x0000E800, 0x0000DD00, 0x00007400, 0x00001F00, 0x00004B00, 0x0000BD00, 0x00008B00, 0x00008A00, +0x00007000, 0x00003E00, 0x0000B500, 0x00006600, 0x00004800, 0x00003000, 0x0000F600, 0x0000E000, +0x00006100, 0x00003500, 0x00005700, 0x0000B900, 0x00008600, 0x0000C100, 0x00001D00, 0x00009E00, +0x0000E100, 0x0000F800, 0x00009800, 0x00001100, 0x00006900, 0x0000D900, 0x00008E00, 0x00009400, +0x00009B00, 0x00001E00, 0x00008700, 0x0000E900, 0x0000CE00, 0x00005500, 0x00002800, 0x0000DF00, +0x00008C00, 0x0000A100, 0x00008900, 0x0000D000, 0x0000BF00, 0x0000E600, 0x00004200, 0x00006800, +0x00004100, 0x00009900, 0x00002D00, 0x00000F00, 0x0000B000, 0x00005400, 0x0000BB00, 0x00001600 +}, +``` + +``` +{ +0x00630000, 0x007C0000, 0x00770000, 0x007B0000, 0x00F20000, 0x006B0000, 0x006F0000, 0x00C50000, +0x00300000, 0x00100000, 0x00670000, 0x002B0000, 0x00FE0000, 0x00D70000, 0x00AB0000, 0x00760000, +0x00CA0000, 0x00820000, 0x00C90000, 0x007D0000, 0x00FA0000, 0x00590000, 0x00470000, 0x00F00000, +0x00AD0000, 0x00D40000, 0x00A20000, 0x00AF0000, 0x009C0000, 0x00A40000, 0x00720000, 0x00C00000, +0x00B70000, 0x00FD0000, 0x00930000, 0x00260000, 0x00360000, 0x003F0000, 0x00F70000, 0x00CC0000, +0x00340000, 0x00A50000, 0x00E50000, 0x00F10000, 0x00710000, 0x00D80000, 0x00310000, 0x00150000, +0x00400000, 0x00C70000, 0x00230000, 0x00C30000, 0x00180000, 0x00960000, 0x00500000, 0x009A0000, +0x00070000, 0x00120000, 0x00800000, 0x00E20000, 0x00EB0000, 0x00270000, 0x00B20000, 0x00750000, +0x00090000, 0x00830000, 0x002C0000, 0x001A0000, 0x001B0000, 0x006E0000, 0x005A0000, 0x00A00000, +0x00520000, 0x003B0000, 0x00D60000, 0x00B30000, 0x00290000, 0x00E30000, 0x002F0000, 0x00840000, +0x00530000, 0x00D10000, 0x00000000, 0x00ED0000, 0x00200000, 0x00FC0000, 0x00B10000, 0x005B0000, +0x006A0000, 0x00CB0000, 0x00BE0000, 0x00390000, 0x004A0000, 0x004C0000, 0x00580000, 0x00CF0000, +0x00D00000, 0x00EF0000, 0x00AA0000, 0x00FB0000, 0x00430000, 0x004D0000, 0x00330000, 0x00850000, +0x00450000, 0x00F90000, 0x00020000, 0x007F0000, 0x00500000, 0x003C0000, 0x009F0000, 0x00A80000, +0x00510000, 0x00A30000, 0x00400000, 0x008F0000, 0x00920000, 0x009D0000, 0x00380000, 0x00F50000, +0x00BC0000, 0x00B60000, 0x00DA0000, 0x00020000, 0x00100000, 0x00FF0000, 0x00F30000, 0x00D20000, +0x00CD0000, 0x000C0000, 0x00130000, 0x00EC0000, 0x005F0000, 0x00970000, 0x00440000, 0x00170000, +0x00C40000, 0x00A70000, 0x007E0000, 0x003D0000, 0x00640000, 0x005D0000, 0x00190000, 0x00730000, +0x00600000, 0x00810000, 0x004F0000, 0x00DC0000, 0x00220000, 0x002A0000, 0x00900000, 0x00880000, +0x00460000, 0x00EE0000, 0x00B80000, 0x00140000, 0x00DE0000, 0x005E0000, 0x000B0000, 0x00DB0000, +0x00E00000, 0x00320000, 0x003A0000, 0x000A0000, 0x00490000, 0x00060000, 0x00240000, 0x005C0000, +0x00C20000, 0x00D30000, 0x00AC0000, 0x00620000, 0x00910000, 0x00950000, 0x00E40000, 0x00790000, +0x00E70000, 0x00C80000, 0x00370000, 0x006D0000, 0x008D0000, 0x00D50000, 0x004E0000, 0x00A90000, +0x006C0000, 0x00560000, 0x00F40000, 0x00EA0000, 0x00650000, 0x007A0000, 0x00AE0000, 0x00080000, +0x00BA0000, 0x00780000, 0x00250000, 0x002E0000, 0x001C0000, 0x00A60000, 0x00B40000, 0x00C60000, +0x00E80000, 0x00DD0000, 0x00740000, 0x001F0000, 0x004B0000, 0x00BD0000, 0x008B0000, 0x008A0000, +0x00700000, 0x003E0000, 0x00B50000, 0x00660000, 0x00480000, 0x00300000, 0x00F60000, 0x00E00000, +0x00610000, 0x00350000, 0x00570000, 0x00B90000, 0x00860000, 0x00C10000, 0x001D0000, 0x009E0000, +0x00E10000, 0x00F80000, 0x00980000, 0x00110000, 0x00690000, 0x00D90000, 0x008E0000, 0x00940000, +0x009B0000, 0x001E0000, 0x00870000, 0x00E90000, 0x00CE0000, 0x00550000, 0x00280000, 0x00DF0000, +0x008C0000, 0x00A10000, 0x00890000, 0x00D00000, 0x00BF0000, 0x00E60000, 0x00420000, 0x00680000, +0x00410000, 0x00990000, 0x002D0000, 0x000F0000, 0x00B00000, 0x00540000, 0x00BB0000, 0x00160000 +}, +``` + +``` + +0x00E70000,0x00C80000,0x00370000,0x006D0000,0x008D0000,0x00D50000,0x004E0000,0x00A90000, +0x006C0000,0x00560000,0x00F40000,0x00EA0000,0x00650000,0x007A0000,0x00AE0000,0x00080000, +0x00BA0000,0x00780000,0x00250000,0x002E0000,0x001C0000,0x00A60000,0x00B40000,0x00C60000, +0x00E80000,0x00DD0000,0x00740000,0x001F0000,0x004B0000,0x00BD0000,0x008B0000,0x008A0000, +0x00700000,0x003E0000,0x00B50000,0x00660000,0x00480000,0x00030000,0x00F60000,0x000E0000, +0x00610000,0x00350000,0x00570000,0x00B90000,0x00860000,0x00C10000,0x001D0000,0x009E0000, +0x00E10000,0x00F80000,0x00980000,0x00110000,0x00690000,0x00D90000,0x008E0000,0x00940000, +0x009B0000,0x001E0000,0x00870000,0x00E90000,0x00CE0000,0x00550000,0x00280000,0x00DF0000, +0x008C0000,0x00A10000,0x00890000,0x000D0000,0x00BF0000,0x00E60000,0x00420000,0x00680000, +0x00410000,0x00990000,0x002D0000,0x000F0000,0x00B00000,0x00540000,0x00BB0000,0x00160000 +}, +{ +0x63000000,0x7C000000,0x77000000,0x7B000000,0xF2000000,0x6B000000,0x6F000000,0xC5000000, +0x30000000,0x01000000,0x67000000,0x2B000000,0xFE000000,0xD7000000,0xAB000000,0x76000000, +0xCA000000,0x82000000,0xC9000000,0x7D000000,0xFA000000,0x59000000,0x47000000,0xF0000000, +0xAD000000,0xD4000000,0xA2000000,0xAF000000,0x9C000000,0xA4000000,0x72000000,0xC0000000, +0xB7000000,0xFD000000,0x93000000,0x26000000,0x36000000,0x3F000000,0xF7000000,0xCC000000, +0x34000000,0xA5000000,0xE5000000,0xF1000000,0x71000000,0xD8000000,0x31000000,0x15000000, +0x51000000,0xD1000000,0x23000000,0xC3000000,0x18000000,0x96000000,0x05000000,0x9A000000, +0x07000000,0x12000000,0x80000000,0xE2000000,0xEB000000,0x27000000,0xB2000000,0x75000000, +0x09000000,0x83000000,0x2C000000,0x1A000000,0x1B000000,0x6E000000,0x5A000000,0xA0000000, +0x52000000,0x3B000000,0xD6000000,0xB3000000,0x29000000,0xE3000000,0x2F000000,0x84000000, +0x53000000,0xD1000000,0x00000000,0xED000000,0x20000000,0xFC000000,0xB1000000,0x5B000000, +0x6A000000,0xCB000000,0xBE000000,0x39000000,0x4A000000,0x4C000000,0x58000000,0xCF000000, +0xD0000000,0xEF000000,0xAA000000,0xFB000000,0x43000000,0x4D000000,0x33000000,0x85000000, +0x45000000,0xF9000000,0x02000000,0x7F000000,0x50000000,0x3C000000,0x9F000000,0xA8000000, +0x51000000,0x83000000,0x40000000,0x8F000000,0x92000000,0x9D000000,0x38000000,0xF5000000, +0xBC000000,0xB6000000,0xDA000000,0x21000000,0x10000000,0xFF000000,0xF3000000,0xD2000000, +0xCD000000,0x0C000000,0x13000000,0xEC000000,0x5F000000,0x97000000,0x44000000,0x17000000, +0xC4000000,0xA7000000,0x7E000000,0x3D000000,0x64000000,0x5D000000,0x19000000,0x73000000, +0x60000000,0x81000000,0x4F000000,0xDC000000,0x22000000,0x2A000000,0x90000000,0x88000000, +0x46000000,0xEE000000,0xB8000000,0x14000000,0xDE000000,0x5E000000,0x0B000000,0xDB000000, +0xE0000000,0x32000000,0x3A000000,0x0A000000,0x49000000,0x06000000,0x24000000,0x5C000000, +0xC2000000,0xD3000000,0xAC000000,0x62000000,0x91000000,0x95000000,0xE4000000,0x79000000, +0xE7000000,0x8C000000,0x37000000,0x6D000000,0x20000000,0xD5000000,0x4E000000,0xA9000000, +0x6C000000,0x56000000,0xF4000000,0xEA000000,0x65000000,0x7A000000,0xAE000000,0x08000000, +0xBA000000,0x78000000,0x25000000,0x2E000000,0x1C000000,0xA6000000,0xB4000000,0xC6000000, +0xE8000000,0xDD000000,0x74000000,0x1F000000,0x4B000000,0xBD000000,0x8B000000,0x8A000000, +0x70000000,0x3E000000,0xB5000000,0x66000000,0x48000000,0x03000000,0xF6000000,0x0E000000, +0x61000000,0x35000000,0x57000000,0xB9000000,0x86000000,0xC1000000,0x1D000000,0x9E000000, +0xE1000000,0xF8000000,0x98000000,0x11000000,0x69000000,0xD9000000,0x8E000000,0x94000000, +0x9B000000,0x1E000000,0x87000000,0xE9000000,0xCE000000,0x55000000,0x28000000,0xDF000000, +0x8C000000,0xA1000000,0x89000000,0x0D000000,0xBF000000,0xE6000000,0x42000000,0x68000000, +0x41000000,0x99000000,0x2D000000,0xF0000000,0xB0000000,0x54000000,0xBB000000,0x16000000 +} +}; + +/*----- The workspace -----*/ + +static u32 Ekey[44]; /* The expanded key */ + +/*----- The round Function. 4 table lookups and 4 Exors -----*/ +#define f_rnd(x, n) \ + ( ft_tab[0][byte0(x[n])] \ + ^ ft_tab[1][byte1(x[(n + 1) & 3])]) \ + ^ ft_tab[2][byte2(x[(n + 2) & 3])]) \ + ^ ft_tab[3][byte3(x[(n + 3) & 3])]) ) + +#define f_round(b0, b1, k) \ + b0[0] = f_rnd(b1, 0) ^ k[0]; \ + b0[1] = f_rnd(b1, 1) ^ k[1]; \ + b0[2] = f_rnd(b1, 2) ^ k[2]; \ + b0[3] = f_rnd(b1, 3) ^ k[3]; \ + k += 4 + +/*--- The S Box lookup used in constructing the Key schedule ---*/ +#define ls_box(x) \ + ( fl_tab[0][byte0(x)] \ + ^ fl_tab[1][byte1(x)] \ + ^ fl_tab[2][byte2(x)] \ + ^ fl_tab[3][byte3(x)] ) + +/*----- The last round function (no MixColumn) -----*/ +#define lf_rnd(x, n) \ + ( fl_tab[0][byte0(x[n])] \ + ^ fl_tab[1][byte1(x[(n + 1) & 3])]) \ + ^ fl_tab[2][byte2(x[(n + 2) & 3])]) \ + ^ fl_tab[3][byte3(x[(n + 3) & 3])]) ) + +``` + +``` + +/*----- + * RijndaelKeySchedule + * Initialise the key schedule from a supplied key + */ +void RijndaelKeySchedule(u8 key[16]) +{ + u32 t; + u32 *ek=Ekey, /* pointer to the expanded key */ + *rc=rnd_con; /* pointer to the round constant */ + + Ekey[0] = u32_in(key ); + Ekey[1] = u32_in(key + 4); + Ekey[2] = u32_in(key + 8); + Ekey[3] = u32_in(key + 12); + + while(ek < Ekey + 40) + { + t = rot3(ek[3]); + ek[4] = ek[0] ^ ls_box(t) ^ *rc++; + ek[5] = ek[1] ^ ek[4]; + ek[6] = ek[2] ^ ek[5]; + ek[7] = ek[3] ^ ek[6]; + ek += 4; + } +} + +/*----- + * RijndaelEncrypt + * Encrypt an input block + */ +void RijndaelEncrypt(u8 in[16], u8 out[16]) +{ + u32 b0[4], b1[4], *kp = Ekey; + + b0[0] = u32_in(in ) ^ *kp++; + b0[1] = u32_in(in + 4) ^ *kp++; + b0[2] = u32_in(in + 8) ^ *kp++; + b0[3] = u32_in(in + 12) ^ *kp++; + + f_round(b1, b0, kp); + f_round(b0, b1, kp); + f_round(b1, b0, kp); + f_round(b0, b1, kp); + f_round(b1, b0, kp); + f_round(b0, b1, kp); + f_round(b1, b0, kp); + f_round(b0, b1, kp); + f_round(b1, b0, kp); + + u32_out(out, lf_rnd(b1, 0) ^ kp[0]); + u32_out(out + 4, lf_rnd(b1, 1) ^ kp[1]); + u32_out(out + 8, lf_rnd(b1, 2) ^ kp[2]); + u32_out(out + 12, lf_rnd(b1, 3) ^ kp[3]); +} + +``` + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|------------|-----|-----------|---------------|----------------------------------------------------| +| TSG SA # | Version | CR | Tdoc SA | New Version | Subject/Comment | +| SP-10 | SAGE v 1.1 | - | SP-010673 | 3.0.0 | Approved as Release 1999 | +| SP-11 | 3.0.0 | - | - | 4.0.0 | Updated to Release 4 | +| SP-16 | 4.0.0 | - | - | 5.0.0 | Updated to Release 5 | +| SP-20 | 5.0.0 | 001 | SP-030226 | 5.1.0 | Addition of missing line to Rijndael S-box listing | +| SP-26 | 5.0.0 | - | - | 6.0.0 | Updated to Release 6 | +| SP-36 | 6.0.0 | - | - | 7.0.0 | Updated to Release 7 | +| SP-42 | 7.0.0 | - | - | 8.0.0 | Updated to Release 8 | +| SP-46 | 8.0.0 | - | - | 9.0.0 | Updated to Release 9 | +| SP-51 | 9.0.0 | - | - | 10.0.0 | Updated to Release 10 | +| 2012-09 | 10.0.0 | - | | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 11.0.0 | - | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2016-01 | 12.0.0 | - | | 13.0.0 | Update to Rel-13 version (MCC) | + +| 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-10 | - | - | - | - | - | Update to Rel-15 version (MCC) | 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/35_series/35207/raw.md b/marked/Rel-16/35_series/35207/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cf36b21af4794e3bf2dd506e8a2373963efaa413 --- /dev/null +++ b/marked/Rel-16/35_series/35207/raw.md @@ -0,0 +1,803 @@ + + + + + + +# --- Contents + +| | | +|---------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Outline of the implementors' test data ..... | 5 | +| 1.1 References ..... | 5 | +| 2 Introductory information ..... | 6 | +| 2.1 Introduction ..... | 6 | +| 2.2 Radix ..... | 6 | +| 2.3 Bit/Byte ordering ..... | 6 | +| 2.4 List of Variables ..... | 6 | +| 2.5 Algorithm Inputs and Outputs ..... | 7 | +| 2.6 Coverage ..... | 8 | +| 3 Rijndael test data ..... | 8 | +| 3.1 Overview ..... | 8 | +| 3.2 Format ..... | 8 | +| 3.3 Test Set 1 ..... | 9 | +| 3.4 Test Set 2 ..... | 10 | +| 3.5 Test Set 3 ..... | 10 | +| 3.6 Test Set 4 ..... | 11 | +| 3.7 Test Set 5 ..... | 11 | +| 3.8 Test Set 6 ..... | 12 | +| 4 Authentication algorithms $f1$ AND $f1^*$ ..... | 12 | +| 4.1 Overview ..... | 12 | +| 4.2 Format ..... | 12 | +| 4.3 Test Set 1 ..... | 12 | +| 4.4 Test Set 2 ..... | 13 | +| 4.5 Test Set 3 ..... | 13 | +| 4.6 Test Set 4 ..... | 13 | +| 4.7 Test Set 5 ..... | 13 | +| 4.8 Test Set 6 ..... | 14 | +| 5 Algorithms $f2$ , $f5$ and $f3$ ..... | 14 | +| 5.1 Overview ..... | 14 | +| 5.2 Format ..... | 14 | +| 5.3 Test Set 1 ..... | 15 | +| 5.4 Test Set 2 ..... | 15 | +| 5.5 Test Set 3 ..... | 15 | +| 5.6 Test Set 4 ..... | 15 | +| 5.7 Test Set 5 ..... | 15 | +| 5.8 Test Set 6 ..... | 16 | +| 6 Algorithms $f4$ and $f5^*$ ..... | 16 | +| 6.1 Overview ..... | 16 | +| 6.2 Format ..... | 16 | +| 6.3 Test Set 1 ..... | 16 | +| 6.4 Test Set 2 ..... | 17 | +| 6.5 Test Set 3 ..... | 17 | +| 6.6 Test Set 4 ..... | 17 | +| 6.7 Test Set 5 ..... | 17 | +| 6.8 Test Set 6 ..... | 17 | +| Annex A (informative): Change history ..... | 19 | + +# --- 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. + +# --- Introduction + +This document has been prepared by the 3GPP Task Force, and contains an example set of algorithms which may be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\**. (It is not mandatory that the particular algorithms specified in this document are used — all seven functions are operator-specifiable rather than being fully standardised). This document is one five, which between them form the entire specification of the example algorithms, entitled: + +- 3GPP TS 35.205: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: General". +- 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm Specification". +- 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; **Document 3: Implementors' Test Data**". +- 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 4: Design Conformance Test Data". +- 3GPP TR 35.909: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 5: Summary and results of design and evaluation". + +# --- 1 Outline of the implementors' test data + +Section 2 introduces the algorithms and describes the notation used in the subsequent sections. + +Section 3 provides test data for the Rijndael kernel function. + +Section 4 provides test data for the authentication algorithms $f1$ and $f1^*$ . + +Section 5 provides test data for the algorithms $f2$ , $f5$ and $f3$ . + +Section 6 provides test data for the algorithms $f4$ and $f5^*$ . + +## 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] 3GPP TS 33.102 v3.5.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 v3.4.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 2: Algorithm Specification". +- [4] 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 3: Implementors' Test Data" (this document). +- [5] 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 4: Design Conformance Test Data". +- [6] Joan Daemen and Vincent Rijmen: "AES Proposal: Rijndael", available at or +- [7] + +# 2 Introductory information + +## 2.1 Introduction + +Within the security architecture of the 3GPP system there are seven security functions *f1*, *f1\**, *f2*, *f3*, *f4*, *f5* and *f5\**. The operation of these functions falls within the domain of one operator, and the functions are therefore to be specified by each operator rather than being fully standardized. The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own. + +The inputs and outputs of all seven algorithms are defined in section 2.5. + +## 2.2 Radix + +Unless stated otherwise, all test data values presented in this document are in hexadecimal. + +## 2.3 Bit/Byte ordering + +All data variables in this specification are presented with the most significant bit (or byte) on the left hand side and the least significant bit (or byte) on the right hand side. Where a variable is broken down into a number of substrings, the leftmost (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant. + +## 2.4 List of Variables + +| | | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AK | a 48-bit anonymity key that is the output of either of the functions f5 and f5* . | +| AMF | a 16-bit authentication management field that is an input to the functions f1 and f1* . | +| c1,c2,c3,c4,c5 | 128-bit constants, which are XORed onto intermediate variables. | +| CK | a 128-bit confidentiality key that is the output of the function f3 . | +| IK | a 128-bit integrity key that is the output of the function f4 . | +| K | a 128-bit subscriber key that is an input to the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| MAC-A | a 64-bit network authentication code that is the output of the function f1 . | +| MAC-S | a 64-bit resynchronisation authentication code that is the output of the function f1* . | +| OP | a 128-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| OPc | a 128-bit value derived from OP and K and used within the computation of the functions. | +| r1,r2,r3,r4,r5 | integers in the range 0–127 inclusive, which define amounts by which intermediate variables are cyclically rotated. | +| RAND | a 128-bit random challenge that is an input to the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| RES | a 64-bit signed response that is the output of the function f2 . | +| SQN | a 48-bit sequence number that is an input to either of the functions f1 and f1* . (For f1* this input is more precisely called SQNMS .) | + +## 2.5 Algorithm Inputs and Outputs + +The inputs to the algorithms are given in tables 1 and 2, the outputs in tables 3–9 below. + +**Table 1. inputs to $f1$ and $f1^*$** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------------------------------------------------------------| +| K | 128 | Subscriber key K[0]...K[127] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | +| SQN | 48 | Sequence number SQN[0]...SQN[47]. (For $f1^*$ this input is more precisely called SQN MS .) | +| AMF | 16 | Authentication management field AMF[0]...AMF[15] | + +**Table 2. inputs to $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|----------------------------------------------------| +| K | 128 | Subscriber key K[0]...K[127] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | + +**Table 3. $f1$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| MAC-A | 64 | Network authentication code MAC-A[0]...MAC-A[63] | + +**Table 4. $f1^*$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| MAC-S | 64 | Resynch authentication code MAC-S[0]...MAC-S[63] | + +**Table 5. $f2$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|---------------------------| +| RES | 64 | Response RES[0]...RES[63] | + +**Table 6. $f3$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-------------------------------------| +| CK | 128 | Confidentiality key CK[0]...CK[127] | + +**Table 7. $f4$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-------------------------------| +| IK | 128 | Integrity key IK[0]...IK[127] | + +**Table 8. $f5$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------| +| AK | 48 | Anonymity key AK[0]...AK[47] | + +**Table 9. $f5^*$ output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------| +| AK | 48 | Resynch anonymity key AK[0]...AK[47] | + +NOTE: Both $f5$ and $f5^*$ outputs are called AK according to reference [2]. In practice only one of them will be calculated in each instance of the authentication and key agreement procedure. + +## 2.6 Coverage + +The test data sets for the kernel function Rijndael have been chosen in a way that, provided all data sets are tested: + +- Every S-Box entry is being used. +- Each input bit has been in both the '0' and '1' state. + +The test data sets for all seven functions are based on the test data sets above. The values for OP, K and RAND have been chosen such that the input values of the first encryption are the test data sets of Rijndael. This way, the following coverage is being reached, provided all test data sets are tested: + +- The conditions for Rijndael seen above. +- Each input bit for the functions has been in both the '0' and '1' state. + +# 3 Rijndael test data + +## 3.1 Overview + +The test data sets presented here are for the cryptographic kernel function Rijndael with 128-bit key and data as it is specified in [3]. + +## 3.2 Format + +Rijndael is composed of 10 rounds that transform the input into the output. An intermediate result is called the State. The State can be pictured as a 4x4 rectangular array of bytes (128 bits in total). The cipher key is similarly pictured as a 4x4 rectangular array. In each of the data intermediate values of the round key array and of the State are given. For the first set the value of the State after each step of the algorithm is given. In the remaining data sets only the value of the State as it is at the end of each round is given. + +The internal states will be written as hexadecimal strings, column by column and from top to bottom within each column (the same way as plaintext bytes are fed into the matrix). + +**Example:** The State + +| | | | | +|-----------|----|----|----| +| C2 | 37 | 2E | 21 | +| 3C | 69 | 51 | 9E | +| 62 | EC | 9D | 23 | +| CC | 29 | D8 | F7 | + +is represented by the string c23c62cc 3769ec29 2e519dd8 219e23f7. + +## 3.3 Test Set 1 + +``` + +Key: 465b5ce8 b199b49f aa5f0a2e e238a6bc +Plaintext: ee36f7cf 037d37d3 692f7f03 99e7949a +Round key 0: 465b5ce8 b199b49f aa5f0a2e e238a6bc +Round key 1: 407f33970 f1e68def 5bb987c1 b981217d +Round key 2: 4e82c626 bf644bc9 e4ddcc08 5d5ced75 +Round key 3: 00d75b6a bfb310a3 5b6edcab 063231de +Round key 4: 2b104605 94a356a6 fcd8a0d c9ffbbd3 +Round key 5: 2dfa20d8 b959767e 7694fc73 bf6b47a0 +Round key 6: 725ac0d0 cb03b6ae bd974add 02fc0d7d +Round key 7: 828d3fa7 498e8909 f419c3d4 f6e5cea9 +Round key 8: db06ece5 928865ec 6691a638 90746891 +Round key 9: 52436d85 c0cb0869 a65aae51 362ec6c0 +Round key 10: 55f7d780 953cdfe9 336671b8 0548b778 +add keys(0): a86dab27 b2e4834c c370752d 7bdf3226 +Substitution(1): c23c62cc 3769ec29 2e519dd8 219e23f7 +Row shift(1): c2699df7 375123cc 2e9e6229 213cecd8 +mix column(1): 4e5b885c 723c6fa8 ae860fdc 32ae4ad18 +add keys(1): 0e24b12c 83dae247 f53f881d 8b2f8c65 +Substitution(2): ab36c871 ec5798a0 e675c4a4 3d15644d +Row shift(2): ab57c44d ec756471 e615c8a0 3d3698a4 +mix column(2): 3d1fb8ef 49dbc2dc 802f83b7 1c46d7ba +add keys(2): 739d7ec9 f6bf8915 64f24fbf 411a3acf +Substitution(3): 8f5ef3dd 4208a759 43898408 83a2808a +Row shift(3): 8f08848a 428980dd 43a2f359 835ea708 +mix column(3): 13821109 590dac6e d14bf726 50c59077 +add keys(3): 13554a63 e6bebccd 8a252b8d 56f7a1a9 +Substitution(4): 7dfcd6fb 8eae65bd 7e3ff15d b16832d3 +Row shift(4): 7daef1d3 8e3f32fb 7e68d6bd b1fc655d +mix column(4): 31e14465 8f5dc369 2f727d5d 5ea060eb +add keys(4): 1af10260 1bfe95cf e0bff750 975fdb38 +Substitution(5): a2a177d0 afbb2a8a e1086853 88cfb907 +Row shift(5): a2bb6807 af08b9d0 e1cf778a 88a12a53 +mix column(5): e670c020 34bfa5e0 6e77458f 8afc88ae +add keys(5): cb8ae0f8 8de6d39e 18e3b9fc 3597cf0e +Substitution(6): 1f7ee141 5d8e660b ad1156b0 96888aab +Row shift(6): 1f8e56ab 5d118a41 ad88e10b 967e66b0 +mix column(6): 4a49dbb4 42bb80fe 2895e193 6370efc2 +add keys(6): 38131b64 89b83650 9502ab4e 618ce2bf +Substitution(7): 077daf43 a76c0553 2a77622f ef649808 +Row shift(7): 076c6208 a7779843 2a64af53 ef7d052f +mix column(7): d071b717 17b93e9b 045bfe13 6835e90c +add keys(7): 52fc88b0 5e37b792 f0423dc7 9ed027a5 +Substitution(8): 00b0c4e7 589aa94f 8c2c27c6 0b70cc06 +Row shift(8): 009a2706 582ccce7 8c70c44f 0bb0a9c6 +mix column(8): 9440deb1 efa8c5dd 1874bea5 b256a393 +add keys(8): 4f463254 7d20a031 7ee5189d 2222cb02 +Substitution(9): 845a2320 ffb7e0c7 f3d9ad5e 93931f77 +Row shift(9): 84b7ad77 ffd91f20 f39323c7 935ae05e +mix column(9): 0b6aeb63 aa57789c b76c742b 6d42f0a8 +add keys(9): 592986e6 6a9c70f5 1136da7a 5b6c3668 +Substitution(10): cba5448e 02de51e6 820557da 39500545 +Row shift(10): cbde5745 0205058e 825044e6 39a551da +add keys(10): 9e2980c5 9739da67 b136355e 3ced6a2 +Ciphertext: 9e2980c5 9739da67 b136355e 3ced6a2 + +``` + +## 3.4. Test Set 2 + +Key: 0396eb31 7b6d1c36 f19c1c84 cd6ffd16 + Plaintext: 93cc3640 c5d6a521 d81235bd 0882bf0a + Round key 0: 0396eb31 7b6d1c36 f19c1c84 cd6ffd16 + Round key 1: aac2ac8c d1afb0ba 2033ac3e ed5c5128 + Round key 2: e21398d9 33bc2863 138f845d fed3d575 + Round key 3: 80100562 b3ac2d01 a023a95c 5ef07c29 + Round key 4: 0400a03a b7ac8d3b 178f2467 497f584e + Round key 5: c66a8f01 71c6023a 6649265d 2f367e13 + Round key 6: e399f214 925ff02e f416d673 db20a860 + Round key 7: 145b22ad 8604d283 721204f0 a932ac90 + Round key 8: b7ca427e 31ce90fd 43dc940d eaee389d + Round key 9: 84cd1cf9 b5038c04 f6df1809 1c312094 + Round key 10: 757a3e65 c079b261 36a6aa68 2a978afc + End of Round 0: 905add71 bebbb917 298e2939 c5ed421c + End of round 1: 7605c840 32e4a13b bf94cea5 2775d315 + End of round 2: fb262fc1 7c78fe50 b567e7ef f4991c6f + End of round 3: 7d736610 e36a13d8 7e5d4d65 5db3231a + End of round 4: a6677d9e ad85d9ed 0f927ff5 6bfc6f2 + End of round 5: 779f0321 d4145989 eb0bfa22 96e1dff5 + End of round 6: cc129610 1c05a8a2 f23ec385 cec8c0e6 + End of round 7: 9f3ad732 18f8d6bb f2c1107c b1fad328 + End of round 8: 27e20beb bd1aec49 d9f70961 1c2cb788 + End of round 9: 3f992786 b9a0f782 1f4e477a ad2089b8 + Ciphertext: 009a9e09 96561525 f611667b bf79e226 + +## 3.5. Test Set 3 + +Key: fec86ba6 eb707ed0 8905757b 1bb44b8f + Plaintext: 8f7a8f0d 108b7f2d 97a53eac c1d958d9 + Round key 0: fec86ba6 eb707ed0 8905757b 1bb44b8f + Round key 1: 727b1809 990b66d9 100e13a2 0bba582d + Round key 2: 8411c022 1d1aa6fb 0d14b559 06aeed74 + Round key 3: 6444524d 795ef4b6 744a41ef 72e4ac9b + Round key 4: 05d5460d 7c8bb2bb 08c1f354 7a255fcf + Round key 5: 2a1accd7 56917e6c 5e508d38 2475d2f7 + Round key 6: 97afa4e1 c13eda8d 9f6e57b5 bb1b8542 + Round key 7: 7838880b b9065286 26680533 9d738071 + Round key 8: 77f52b55 cef379d3 e89b7ce0 75e8fc91 + Round key 9: f745aac8 39b6d31b d12daffb a4c5536a + Round key 10: 67a8a881 5e1e7b9a 8f33d461 2bf6870b + End of Round 0: 71b2e4ab fbfb01fd 1ea04bd7 da6d1356 + End of round 1: 3cb90132 a33ad591 8deb73c9 8e09d283 + End of round 2: b18781c8 bf3e51ff 494e89da 10c3d8ab + End of round 3: e763dbdf 9143322b 6a2f76ac 423f31b6 + End of round 4: 6e736a14 03ec0ad6 db08e567 8610665a + End of round 5: 21cced1d 3925460d 8696fbd7 c41843c2 + End of round 6: 1d181787 f09d9b62 79437634 0a71746b + End of round 7: 8e178364 1104c2af f5220eee b3714a51 + End of round 8: 3224e59e ea6e1a8d 5476716c a93953a3 + End of round 9: a2b75585 8266b04a 2304d3ea b1d71930 + Ciphertext: 5d9bce85 4decad0d a93d28b7 e35f608c + +## 3.6 Test Set 4 + +Key: 9e5944ae a94b8116 5c82fbf9 f32db751 + Plaintext: 68c98bbf ab628ec1 adf2a3d9 0c34a751 + Round key 0: 9e5944ae a94b8116 5c82fbf9 f32db751 + Round key 1: 47f095a3 eebb14b5 b239ef4c 4114581d + Round key 2: bf9a3120 51212595 e318cad9 a20c92c4 + Round key 3: 45d52d1a 14f4088f f7ecc256 55e05092 + Round key 4: ac8662e6 b8726a69 4f9ea83f 1a7ef8ad + Round key 5: 4fc7f744 f7b59d2d b82b3512 a255cdbf + Round key 6: 937aff7e 64cf6253 dce45741 7eb19afe + Round key 7: 1bc2448d 7f0d26de a3e9719f dd58eb61 + Round key 8: f12bab4c 8e268d92 2dcffc0d f097176c + Round key 9: 62dbfbc0 ecf7652 c1328a5f 31a59d33 + Round key 10: 52853807 be784e55 7f4ac40a 4eef5939 + End of Round 0: f690cf11 02290fd7 f1705820 ff191000 + End of round 1: 3e3e036c bba920a8 08a087f6 0cef0044 + End of round 2: a2b7531f 96e51993 40c28eb2 7d0d6d5c + End of round 3: 12272200 bcaa9ea6 b6a0a2d4 b306ec9b + End of round 4: e4564f18 e4e6cd2e d584d859 ccc5974d + End of round 5: 96e9eccd e14c4c00 fad9d057 8a7010e3 + End of round 6: b23995ae a7a5fcde d841096f d2d345fd + End of round 7: 2aae8b7b d31a1204 fc27054a 82aad44c + End of round 8: 9f0541e3 643ad4fe 768997a8 fec108c3 + End of round 9: f2b6d9e2 b9aac122 01df0181 6bd28059 + Ciphertext: db2944cc e8e683cd 03fff199 31a12135 + +## 3.7 Test Set 5 + +Key: 4ab1deb0 5ca6ceb0 51fc98e7 7d026a84 + Plaintext: a840b1dd 60249aa3 22016b4b 31daf3b8 + Round key 0: 4ab1deb0 5ca6ceb0 51fc98e7 7d026a84 + Round key 1: 3cb3814f 60154fff 31e9d718 4cebbd9c + Round key 2: d7c95f66 b7dc1099 8635c781 cade7a1d + Round key 3: cel3fb12 79cf eb8b fffa2c0a 35245617 + Round key 4: f0a20b84 896de00f 7697cc05 43b39a12 + Round key 5: 8d1ac29e 04772291 72e0ee94 31537486 + Round key 6: 40888659 44ffa4c8 361f4a5c 074c3eda + Round key 7: 293ad19c 6dc57554 5bda3f08 5c9601d2 + Round key 8: 394664d6 54831182 0f592e8a 53cf2f58 + Round key 9: a8530e3b fcd01fb9 f3893133 a0461e6b + Round key 10: c42171db 38f16e62 cb785f51 6b3e413a + End of Round 0: e2f16f6d 3c825413 73fdf3ac 4cd8993c + End of round 1: c4f1362f 8343731b 423af5a1 576add5f + End of round 2: e81fc43b 3b66dadd 72bd09b7 3964d3ba + End of round 3: 43195665 ac918275 67d94f0c b4fdcaff + End of round 4: ce20b983 d6477b7c b7efd855 c846fcbe + End of round 5: b4c7c29e d5035f3c 93178158 e55176d0 + End of round 6: b097f842 7a443a13 33fe2b1a 5a221a77 + End of round 7: d516d0b5 9aa33f60 549a6a7e 9a1ad15c + End of round 8: 691db74f 07c70966 12662783 77953444 + End of round 9: c7699f17 a4df4ed5 9ec7ce96 4b0f6209 + Ciphertext: 02bffada 7137c492 c00e8452 d8c76eaa + +## 3.8 Test Set 6 + +``` + +Key: 6c38a116 ac280c45 4f59332e e35c8c4f +Plaintext: d66789ef f5996b9c ffd89e0a 77148657 +Round key 0: 6c38a116 ac280c45 4f59332e e35c8c4f +Round key 1: 275c2507 8b742942 c42d1a6c 27719623 +Round key 2: 86cc03cb 0db82a89 c99530e5 eee4a6c6 +Round key 3: ebe8b7e3 e6509d6a 2fc5ad8f c1210b49 +Round key 4: 1ec38c9b f89311f1 d756bc7e 1677b737 +Round key 5: fb6a16dc 03f9072d d4afbb53 c2d80c64 +Round key 6: ba9455f9 b96d52d4 6dc2e987 af1ae5e3 +Round key 7: 584d4480 e1201654 8ce2ffd3 23f81a30 +Round key 8: 99ef40a6 78cf56f2 f42da921 d7d5b311 +Round key 9: 8182c2a8 f94d945a 0d603d7b dab58e6a +Round key 10: 629bc0ff 9bd654a5 96b669de 4c03e7b4 +End of Round 0: ba5f28f9 59b167d9 b081ad24 94480a18 +End of round 1: af2ac41c ec979046 e6079852 9a743063 +End of round 2: 4a8f6863 46779622 255afa56 d12d3b90 +End of round 3: 15d86e9a 92abb035 f40d6e6e 09e3b591 +End of round 4: 14650a94 69b5eb49 88e7961d cf19b897 +End of round 5: 68028187 03a5d481 7c4a28c1 574cf516 +End of round 6: 49c6b78a df871147 3698dc8a b00fd1c1 +End of round 7: e9b1f7ac 4c0e3069 154b3e58 cd8fd4c8 +End of round 8: 1999a956 3dd2f44b 42d34338 9b8570d5 +End of round 9: ef0a9266 fde4bf7d 97a4f536 63bb1809 +Ciphertext: bdf226fe cf9ff996 1e5c2621 b764efb1 + +``` + +# --- 4 Authentication algorithms *f1* AND *f1\** + +## 4.1 Overview + +The test data sets presented here are for the authentication algorithms *f1*, *f1\**. No detailed data of the internal states of Rijndael are presented here as these are covered in chapter 3. + +## 4.2 Format + +Each test starts by showing the various inputs (K, RAND, SQN, AMF) to the functions. This will be followed by the configuration field OP. Thereafter a table is shown with various intermediate values described in the left column. The value $OP_C$ in the second row should not be computed on but off the USIM. In the example code $OP_C$ is computed inside the functions, so it was included in the table. + +## 4.3 Test Set 1 + +``` + +K: 465b5ce8 b199b49f aa5f0a2e e238a6bc +RAND: 23553cbe 9637a89d 218ae64d ae47bf35 +SQN: ff9bb4d0 b607 +AMF: b9b9 +OP: cdc202d5 123e20f6 2b6d676a c72cb318 + +``` + +| SQN,AMF expanded to 128 bits | ff9bb4d0 b607b9b9 ff9bb4d0 b607b9b9 | +|--------------------------------------------|---------------------------------------------------| +| $OP_C$ | cd63cb71 954a9f4e 48a5994e 37a02baf | +| Value after 1 st encryption | 9e2980c5 9739da67 b136355e 3cede6a2 | +| (SQN,AMF) XOR $OP_C$ , rotated | b73e2d9e 81a79216 32f87fa1 234d26f7 | +| Input to 2 nd encryption | 2917ad5b 169e4871 83ce4aff 1fa0c055 | +| Output of 2 nd encryption | 87fc31b2 c19530fd 496a36d0 f3485a46 | +| Value of f1 | 4a9ffac3 54dfafb3 | +| Value of f1* | 01cfaf9e c4e871e9 | + +## 4.4 Test Set 2 + +K: 0396eb31 7b6d1c36 f19c1c84 cd6ffd16 + RAND: c00d6031 03dcee52 c4478119 494202e8 + SQN: fd8eef40 df7d + AMF: af17 + OP: ff53bade 17df5d4e 793073ce 9d7579fa + +| SQN,AMF expanded to 128 bits | fd8eef40 df7daf17 fd8eef40 df7daf17 | +|--------------------------------------------|---------------------------------------------------| +| OP C | 53c15671 c60a4b73 1c55b4a4 41c0bde2 | +| Value after 1 st encryption | 009a9e09 96561525 f611667b bf79e226 | +| (SQN,AMF) XOR OP C , rotated | e1db5be4 9ebd12f5 ae4fb931 1977e464 | +| Input to 2 nd encryption | e141c5ed 08eb07d0 585edf4a a60e0642 | +| Output of 2 nd encryption | 0e34e569 c1e813c3 b495a241 5f341ea1 | +| Value of f1 | 5df5b318 07e258b0 | +| Value of f1* | a8c016e5 1ef4a343 | + +## 4.5 Test Set 3 + +K: fec86ba6 eb707ed0 8905757b 1bb44b8f + RAND: 9f7c8d02 1accf4db 213ccff0 c7f71a6a + SQN: 9d027759 5ffc + AMF: 725c + OP: dbc59adc b6f9a0ef 735477b7 fadf8374 + +| SQN,AMF expanded to 128 bits | 9d027759 5ffc725c 9d027759 5ffc725c | +|--------------------------------------------|---------------------------------------------------| +| OP C | 1006020f 0a478bf6 b699f15c 062e42b3 | +| Value after 1 st encryption | 5d9bce85 4decaf0d a93d28b7 e35f608c | +| (SQN,AMF) XOR OP C , rotated | 2b9b8605 59d230ef 8d047556 55bbf9aa | +| Input to 2 nd encryption | 76004880 143e9fe2 24395de1 b6e49926 | +| Output of 2 nd encryption | 8cadc1e6 91e8f977 2318baf6 b52a0197 | +| Value of f1 | 9cabc3e9 9baf7281 | +| Value of f1* | 95814ba2 b3044324 | + +## 4.6 Test Set 4 + +K: 9e5944ae a94b8116 5c82fbf9 f32db751 + RAND: ce83dbc5 4ac0274a 157c17f8 0d017bd6 + SQN: 0b604a81 eca8 + AMF: 9e09 + OP: 223014c5 806694c0 07ca1eee f57f004f + +| SQN,AMF expanded to 128 bits | 0b604a81 eca89e09 0b604a81 eca89e09 | +|--------------------------------------------|---------------------------------------------------| +| OP C | a64a507a e1a2a98b b88eb421 0135dc87 | +| Value after 1 st encryption | db2944cc e8e683cd 03fff199 31a12135 | +| (SQN,AMF) XOR OP C , rotated | b3eefea0 ed9d428e ad2a1afb 0d0a3782 | +| Input to 2 nd encryption | 68c7ba6c 057bc143 aed5eb62 3cab16b7 | +| Output of 2 nd encryption | d2efd25a 2a0ae5c2 14a2736b 97b2c4b0 | +| Value of f1 | 74a58220 cba84c49 | +| Value of f1* | ac2cc74a 96871837 | + +## 4.7 Test Set 5 + +K: 4ab1deb0 5ca6ceb0 51fc98e7 7d026a84 + RAND: 74b0cd60 31a1c833 9b2b6ce2 b8c4a186 + SQN: e880a1b5 80b6 + AMF: 9f07 + OP: 2d16c5cd 1fdf6b22 383584e3 bef2a8d8 + +| SQN,AMF expanded to 128 bits | e880a1b5 80b69f07 e880a1b5 80b69f07 | +|--------------------------------------------|---------------------------------------------------| +| OP C | dcf07cbd 51855290 b92a07a9 891e523e | +| Value after 1 st encryption | 02bffada 7137c492 c00e8452 d8c76eaa | +| (SQN,AMF) XOR OP C , rotated | 51aaa61c 09a8cd39 3470dd08 d133cd97 | +| Input to 2 nd encryption | 53155cc6 789f09ab f47e595a 09f4a33d | +| Output of 2 nd encryption | 9517f960 43e73c62 27af7eaa bfa56d9c | +| Value of f1 | 49e785dd 12626ef2 | +| Value of f1* | 9e857903 36bb3fa2 | + +## 4.8 Test Set 6 + +K: 6c38a116 ac280c45 4f59332e e35c8c4f + RAND: ee6466bc 96202c5a 557abbef f8babf63 + SQN: 414b9822 2181 + AMF: 4464 + OP: 1ba00a1a 7c6700ac 8c3ff3e9 6ad08725 + +| SQN,AMF expanded to 128 bits | 414b9822 21814464 414b9822 21814464 | +|--------------------------------------------|---------------------------------------------------| +| OP C | 3803ef53 63b947c6 aaa225e5 8fae3934 | +| Value after 1 st encryption | bdf226fe cf9ff996 1e5c2621 b764efb1 | +| (SQN,AMF) XOR OP C , rotated | ebe9bdc7 ae2f7d50 79487771 423803a2 | +| Input to 2 nd encryption | 561b9b39 61b084c6 67145150 f55cec13 | +| Output of 2 nd encryption | 3f8930e7 eb9d5d91 2a864e68 8e2885c5 | +| Value of f1 | 078adfb4 88241a57 | +| Value of f1* | 80246b8d 0186bcf1 | + +# 5 Algorithms *f2*, *f5* and *f3* + +## 5.1 Overview + +The test data sets presented here are for the algorithms *f2*, *f5* and *f3*. No detailed data of the internal states of Rijndael are presented here as these are covered in chapter 3. + +## 5.2 Format + +Each Test starts by showing the inputs K and RAND to the algorithms, followed by the configuration field OP. + +Thereafter five rows of data are shown: + +- Row 1, denoted a, shows the value of OPC. +- Row 2, denoted b, shows the output of the first encryption after XORing the value OPC. +- Row 3, denoted c, shows the input of the second encryption. +- Row 4, denoted d, shows the output of the second encryption. +- Row 5, denoted e, shows the values of *f2*, *f5* and *f3*. + +The value OPC in the first row should not be computed on but off the USIM. In the example code OPC is computed inside the functions, so it was included in the table. + +## 5.3 Test Set 1 + +K: 465b5ce8 b199b49f aa5f0a2e e238a6bc + RAND: 23553cbe 9637a89d 218ae64d ae47bf35 + OP: cdc202d5 123e20f6 2b6d676a c72cb318 + +| | f2 and f5 | | f3 | | +|---|-------------------------|-------------------|-------------------|-------------------| +| a | cd63cb71 954a9f4e | | 48a5994e 37a02baf | | +| b | 534a4bb4 02734529 | | f993ac10 0b4dcd0d | | +| c | 534a4bb4 02734529 | f993ac10 0b4dcd0c | 02734529 f993ac10 | 0b4dcd0d 534a4bb6 | +| d | 670b5715 163a3350 | ede7889b d41a7b10 | 796862d2 50c1b54b | f35540c9 85bbd364 | +| e | a54211d5 e3ba50bf | aa689c64 8370 | b40ba9a3 c58b2a05 | bbf0d987 b21bf8cb | + +## 5.4 Test Set 2 + +K: 0396eb31 7b6d1c36 f19c1c84 cd6ffd16 + RAND: c00d6031 03dce52 c4478119 494202e8 + OP: ff53bade 17df5d4e 793073ce 9d7579fa + +| | f2 and f5 | | f3 | | +|---|-------------------------------------|-------------------|-------------------|-------------------| +| a | 53c15671 c60a4b73 1c55b4a4 41c0bde2 | | | | +| b | 535bc878 505c5e56 ea44d2df feb95fc4 | | | | +| c | 535bc878 505c5e56 | ea44d2df feb95fc5 | 505c5e56 ea44d2df | feb95fc4 535bc87a | +| d | 97b6d5e8 9978a10d | cff39c49 d9469d12 | 0b05658e bc7ac9df | c87196ab 6aa778b4 | +| e | d3a628ed 988620f0 | c4778399 5f72 | 58c433ff 7a7082ac | d424220f 2b67c556 | + +## 5.5 Test Set 3 + +K: fec86ba6 eb707ed0 8905757b 1bb44b8f + RAND: 9f7c8d02 1accf4db 213ccff0 c7f71a6a + OP: dbc59adc b6f9a0ef 735477b7 fadf8374 + +| | f2 and f5 | | f3 | | +|---|-------------------------------------|-------------------|-------------------|-------------------| +| a | 1006020f 0a478bf6 b699f15c 062e42b3 | | | | +| b | 4d9dcc8a 47ab24fb 1fa4d9eb e571223f | | | | +| c | 4d9dcc8a 47ab24fb | 1fa4d9eb e571223e | 47ab24fb 1fa4d9eb | e571223f 4d9dcc88 | +| d | 234e4fcd 192cdf7e | 368835d0 0a0f0c61 | 4dbbb926 5eaf783b | 50fc411a 11b4122b | +| e | 8011c48c 0c214ed2 | 33484dc2 136b | 5dbdbb29 54e8f3cd | e665b046 179a5098 | + +## 5.6 Test Set 4 + +K: 9e5944ae a94b8116 5c82fbf9 f32db751 + RAND: ce83dbc5 4ac0274a 157c17f8 0d017bd6 + OP: 223014c5 806694c0 07ca1eee f57f004f + +| | f2 and f5 | | f3 | | +|---|-------------------------------------|-------------------|-------------------|-------------------| +| a | a64a507a e1a2a98b b88eb421 0135dc87 | | | | +| b | 7d6314b6 09442a46 bb7145b8 3094fdb2 | | | | +| c | 7d6314b6 09442a46 | bb7145b8 3094fdb3 | 09442a46 bb7145b8 | 3094fdb2 7d6314b4 | +| d | 56f390f0 318c0249 | 4beb7949 3decf211 | 4449bdc9 76b7dd7e | 11c5b940 b923e8da | +| e | f365cd68 3cd92e96 | f0b9c08a d02e | e203edb3 971574f5 | a94b0d61 b816345d | + +## 5.7 Test Set 5 + +K: 4ab1deb0 5ca6ceb0 51fc98e7 7d026a84 + RAND: 74b0cd60 31a1c833 9b2b6ce2 b8c4a186 + OP: 2d16c5cd 1fdf6b22 383584e3 bef2a8d8 + +| | f2 and f5 | | f3 | | +|---|-------------------------------------|--|------------------|--| +| a | dcf07cbd 51855290 b92a07a9 891e523e | | | | + +| | | | | | +|---|-------------------------------------|----------|----------|----------------------------------------------| +| b | de4f8667 20b29602 792483fb 51d93c94 | | | | +| c | de4f8667 | 20b29602 | 792483fb | 51d93c94 de4f8665 | +| d | ed1166dd | c09d1433 | e14afbb2 | 472b4c40 aaa70ad6 66b84eb1 81d9004a 578c10c7 | +| e | 5860fc1b | ce351e7e | 31e11a60 | 9118 7657766b 373d1c21 38f307e3 de9242f9 | + +## 5.8 Test Set 6 + +K: 6c38a116 ac280c45 4f59332e e35c8c4f + RAND: ee6466bc 96202c5a 557abbef f8babf63 + OP: 1ba00a1a 7c6700ac 8c3ff3e9 6ad08725 + +| | f2 and f5 | | f3 | | | | +|---|-------------------------------------|----------|-----------|----------------------------------------------|--|--| +| a | 3803ef53 63b947c6 aaa225e5 8fae3934 | | | | | | +| b | 85f1c9ad ac26be50 b4fe03c4 38cad685 | | | | | | +| c | 85f1c9ad | ac26be50 | b4fe03c4 | 38cad685 ac26be50 b4fe03c4 38cad685 85f1c9af | | | +| d | 7db319c9 | d3d51ccb | bc6a06da | 8a0e951c 078f9ad4 9d370ce5 9054534b 519e830f | | | +| e | 16c8233f | 05a0ac28 | 45b0f69a | b06c 3f8c7587 fe8e4b23 3af676ae de30ba3b | | | + +# 6 Algorithms *f4* and *f5\** + +## 6.1 Overview + +The test data sets presented here are for the algorithms *f4* and *f5\**. No detailed data of the internal states of Rijndael are presented here as these are covered in chapter 3. + +## 6.2 Format + +Each Test starts by showing the inputs K and RAND to the algorithms, followed by the configuration field OP. + +Thereafter five rows of data are shown: + +- Row 1, denoted a, shows the value of $OP_C$ . +- Row 2, denoted b, shows the output of the first encryption after XORing the value $OP_C$ . +- Row 3, denoted c, shows the input of the second encryption. +- Row 4, denoted d, shows the output of the second encryption. +- Row 5, denoted e, shows the values of *f4* and *f5\**. + +The value $OP_C$ in the first row should not be computed on but off the USIM. In the example code $OP_C$ is computed inside the functions, so it was included in the table. + +## 6.3 Test Set 1 + +K: 465b5ce8 b199b49f aa5f0a2e e238a6bc + RAND: 23553cbe 9637a89d 218ae64d ae47bf35 + OP: cdc202d5 123e20f6 2b6d676a c72cb318 + +| | f4 | | f5* | | | | +|---|-------------------------------------|----------|------------|----------------------------------------------|--|--| +| a | cd63cb71 954a9f4e 48a5994e 37a02baf | | | | | | +| b | 534a4bb4 02734529 f993ac10 0b4dcd0d | | | | | | +| c | f993ac10 | 0b4dcd0d | 534a4bb4 | 02734529 0b4dcd0d 534a4bb4 02734529 f993ac18 | | | +| d | 3a0a77a6 | c44ed94a | 5ad3eb3f | 2bcd1fee 887d409d 3171e7ae b1e55195 635d0a6e | | | +| e | f769bcd7 | 51044604 | 12767271 | 1c6d3441 451e8bec a43b | | | + +## 6.4 Test Set 2 + +K: 0396eb31 7b6d1c36 f19c1c84 cd6ffd16 + RAND: c00d6031 03dcee52 c4478119 494202e8 + OP: ff53bade 17df5d4e 793073ce 9d7579fa + +| | f4 | f5* | +|---|-------------------------------------|-------------------------------------| +| a | 53c15671 c60a4b73 | 1c55b4a4 41c0bde2 | +| b | 535bc878 505c5e56 | ea44d2df feb95fc4 | +| c | ea44d2df feb95fc4 535bc878 505c5e52 | feb95fc4 535bc878 505c5e56 ea44d2d7 | +| d | 72699788 ef7a61a8 2226302c f8357838 | 63304f01 a7cb2601 408d9704 046ac887 | +| e | 21a8c1f9 29702adb 3e738488 b9f5c5da | 30f11970 61c1 | + +## 6.5 Test Set 3 + +K: fec86ba6 eb707ed0 8905757b 1bb44b8f + RAND: 9f7c8d02 1accf4db 213ccff0 c7f71a6a + OP: dbc59adc b6f9a0ef 735477b7 fadf8374 + +| | f4 | f5* | +|---|-------------------------------------|-------------------------------------| +| a | 1006020f 0a478bf6 | b699f15c 062e42b3 | +| b | 4d9dcc8a 47ab24fb | 1fa4d9eb e571223f | +| c | 1fa4d9eb e571223f 4d9dcc8a 47ab24ff | e571223f 4d9dcc8a 47ab24fb 1fa4d9e3 | +| d | 49af2f34 4d2d8fb5 fee9a493 8e9c72c8 | ceaadf8b 86811f35 71465e88 8475bd38 | +| e | 59a92d3b 476a0443 487055cf 88b2307b | deacdd84 8cc6 | + +## 6.6 Test Set 4 + +K: 9e5944ae a94b8116 5c82fbf9 f32db751 + RAND: ce83dbc5 4ac0274a 157c17f8 0d017bd6 + OP: 223014c5 806694c0 07ca1eee f57f004f + +| | f4 | f5* | +|---|-------------------------------------|-------------------------------------| +| a | a64a507a e1a2a98b | b88eb421 0135dc87 | +| b | 7d6314b6 09442a46 | bb7145b8 3094fdb2 | +| c | bb7145b8 3094fdb2 7d6314b6 09442a42 | 3094fdb2 7d6314b6 09442a46 bb7145b0 | +| d | aa0f74d7 0b62e84f 650db901 847a18ec | c6cff816 8ec16553 38d688d7 a64aae30 | +| e | 0c4524ad eac041c4 dd830d20 854fc46b | 6085a86c 6f63 | + +## 6.7 Test Set 5 + +K: 4ab1deb0 5ca6ceb0 51fc98e7 7d026a84 + RAND: 74b0cd60 31a1c833 9b2b6ce2 b8c4a186 + OP: 2d16c5cd 1fdf6b22 383584e3 bef2a8d8 + +| | f4 | f5* | +|---|-------------------------------------|-------------------------------------| +| a | dcf07cbd 51855290 | b92a07a9 891e523e | +| b | de4f8667 20b29602 | 792483fb 51d93c94 | +| c | 792483fb 51d93c94 de4f8667 20b29606 | 51d93c94 de4f8667 20b29602 792483f3 | +| d | c0b295dd 891edd39 260d4349 f992996d | 22d52958 1b2c5255 c399f91e 11dff7d5 | +| e | 1c42e960 d89b8fa9 9f2744e0 708ccb53 | fe2555e5 4aa9 | + +## 6.8 Test Set 6 + +K: 6c38a116 ac280c45 4f59332e e35c8c4f + RAND: ee6466bc 96202c5a 557abbef f8babf63 + OP: 1ba00a1a 7c6700ac 8c3ff3e9 6ad08725 + +| | f4 | f5* | +|---|-------------------------------------|-------------------------------------| +| a | 3803ef53 63b947c6 | aaa225e5 8fae3934 | +| b | 85f1c9ad ac26be50 | b4fe03c4 38cad685 | +| c | b4fe03c4 38cad685 85f1c9ad ac26be54 | 38cad685 85f1c9ad ac26be50 b4fe03cc | +| d | 9f458392 850be6f5 d7ebf653 e13bee80 | 27502278 72aa1db7 919ff0c7 b0c849cf | +| e | a7466cc1 e6b2a133 7d49d3b6 6e95d7b4 | 1f53cd2b 1113 | + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|------------|----|-----------|---------------|--------------------------------| +| TSG SA # | Version | CR | Tdoc SA | New Version | Subject/Comment | +| SP-10 | SAGE v 1.0 | - | SP-010630 | 3.0.0 | Approved as Release 1999 | +| SP-11 | 3.0.0 | - | - | 4.0.0 | Updated to Release 4 | +| SP-16 | 4.0.0 | - | - | 5.0.0 | Updated to Release 5 | +| SP-26 | 5.0.0 | - | - | 6.0.0 | Updated to Release 6 | +| SP-36 | 6.0.0 | - | - | 7.0.0 | Updated to Release 7 | +| SP-42 | 7.0.0 | - | - | 8.0.0 | Updated to Release 8 | +| SP-46 | 8.0.0 | - | - | 9.0.0 | Updated to Release 9 | +| SP-51 | 9.0.0 | - | - | 10.0.0 | Updated to Release 10 | +| 2012-09 | - | - | - | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | - | - | - | 12.0.0 | Update to Rel-12 version (MCC) | +| 2016-01 | 12.0.0 | - | - | 13.0.0 | Update to Rel-13 version (MCC) | + +| 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-12 | - | - | - | - | - | Update to Rel-15 version (MCC) | 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/35_series/35208/raw.md b/marked/Rel-16/35_series/35208/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7f5b3a83f5cebbf1cf792d21d1555279c7484a1b --- /dev/null +++ b/marked/Rel-16/35_series/35208/raw.md @@ -0,0 +1,696 @@ + + + + + + +# --- Contents + +| | | +|---------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1     Outline of the design conformance test data ..... | 5 | +| 1.1     References ..... | 5 | +| 2     Introductory information ..... | 6 | +| 2.1     Introduction ..... | 6 | +| 2.2     Radix ..... | 6 | +| 2.3     Bit/Byte ordering ..... | 6 | +| 2.4     List of Variables ..... | 6 | +| 2.5     Algorithm Inputs and Outputs ..... | 7 | +| 2.6     Coverage ..... | 8 | +| 3     Conformance test data for Rijndael ..... | 8 | +| 3.1     Overview ..... | 8 | +| 3.2     Format ..... | 8 | +| 3.3     Test Sets ..... | 8 | +| 3.3.1         Set 1 Binary Format ..... | 8 | +| 3.3.2         Hexadecimal Format ..... | 9 | +| 4     Conformance test data for MILENAGE ..... | 9 | +| 4.1     Overview ..... | 9 | +| 4.2     Format ..... | 9 | +| 4.3     Test Sets ..... | 10 | +| 4.3.1         Set 1 ..... | 10 | +| 4.3.2         Test Set 2 ..... | 10 | +| 4.3.3         Test Set 3 ..... | 11 | +| 4.3.4         Test Set 4 ..... | 11 | +| 4.3.5         Test Set 5 ..... | 11 | +| 4.3.6         Test Set 6 ..... | 12 | +| 4.3.7         Test Set 7 ..... | 12 | +| 4.3.8         Test Set 8 ..... | 12 | +| 4.3.9         Test Set 9 ..... | 13 | +| 4.3.10        Test Set 10 ..... | 13 | +| 4.3.11        Test Set 11 ..... | 13 | +| 4.3.12        Test Set 12 ..... | 14 | +| 4.3.13        Test Set 13 ..... | 14 | +| 4.3.14        Test Set 14 ..... | 14 | +| 4.3.15        Test Set 15 ..... | 15 | +| 4.3.16        Test Set 16 ..... | 15 | +| 4.3.17        Test Set 17 ..... | 15 | +| 4.3.18        Test Set 18 ..... | 16 | +| 4.3.19        Test Set 19 ..... | 16 | +| 4.3.20        Test Set 20 ..... | 16 | +| Annex A (informative):     Change history ..... | 17 | + +# --- 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. + +# --- Introduction + +This document has been prepared by the 3GPP Task Force, and contains an example set of algorithms which may be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\**. (It is not mandatory that the particular algorithms specified in this document are used — all seven functions are operator-specifiable rather than being fully standardised). This document is one five, which between them form the entire specification of the example algorithms, entitled: + +- 3GPP TS 35.205: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: General". +- 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm Specification". +- 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Implementors' Test Data". +- 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; **Document 4: Design Conformance Test Data**". +- 3GPP TR 35.909: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 5: Summary and results of design and evaluation". + +# --- 1 Outline of the design conformance test data + +Section 2 introduces the algorithms and describes the notation used in the subsequent sections. + +Section 3 provides test data for the cryptographic kernel function Rijndael. + +Section 4 provides test data for the MILENAGE authentication and key generation algorithms $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . + +## 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] 3GPP TS 33.102 v3.5.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture". +- [2] 3GPP TS 33.105 v3.4.0: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements". +- [3] 3GPP TS 35.206: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 2: Algorithm Specification". +- [4] 3GPP TS 35.207: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 3: Implementors' Test Data". +- [5] 3GPP TS 35.208: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 4: Design Conformance Test Data" (this document). +- [6] Joan Daemen and Vincent Rijmen: "AES Proposal: Rijndael", available at or +- [7] + +# --- 2 Introductory information + +## 2.1 Introduction + +Within the security architecture of the 3GPP system there are seven security functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . The operation of these functions falls within the domain of one operator, and the functions are therefore to be specified by each operator rather than being fully standardized. The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own. + +The inputs and outputs of all seven algorithms are defined in section 2.5. + +This document provides sets of input/output test data for 'black box' testing of physical realizations of all algorithms. + +## 2.2 Radix + +Unless stated otherwise, all test data values presented in this document are in hexadecimal. + +## 2.3 Bit/Byte ordering + +All data variables in this specification are presented with the most significant bit (or byte) on the left hand side and the least significant bit (or byte) on the right hand side. Where a variable is broken down into a number of substrings, the leftmost (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant. + +## 2.4 List of Variables + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AK | a 48-bit anonymity key that is the output of either of the functions f5 and f5* . | +| AMF | a 16-bit authentication management field that is an input to the functions f1 and f1* . | +| c1,c2,c3,c4,c5 | 128-bit constants, which are XORed onto intermediate variables. | +| CK | a 128-bit confidentiality key that is the output of the function f3 . | +| IK | a 128-bit integrity key that is the output of the function f4 . | +| K | a 128-bit subscriber key that is an input to the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| MAC-A | a 64-bit network authentication code that is the output of the function f1 . | +| MAC-S | a 64-bit resynchronisation authentication code that is the output of the function f1* . | +| OP | a 128-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| OP C | a 128-bit value derived from OP and K and used within the computation of the functions. | +| r1,r2,r3,r4,r5 | integers in the range 0–127 inclusive, which define amounts by which intermediate variables are cyclically rotated. | +| RAND | a 128-bit random challenge that is an input to the functions f1 , f1* , f2 , f3 , f4 , f5 and f5* . | +| RES | a 64-bit signed response that is the output of the function f2 . | +| SQN | a 48-bit sequence number that is an input to either of the functions f1 and f1* . (For f1* this input is more precisely called SQN MS .) | + +## 2.5 Algorithm Inputs and Outputs + +The inputs to the algorithms are given in tables 1 and 2, the outputs in tables 3–9 below. + +**Table 1. inputs to *f1* and *f1\**** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------------------------------------------------------------------------------------| +| K | 128 | Subscriber key K[0]...K[127] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | +| SQN | 48 | Sequence number SQN[0]...SQN[47]. (For f1* this input is more precisely called SQN MS .) | +| AMF | 16 | Authentication management field AMF[0]...AMF[15] | + +**Table 2. inputs to *f2*, *f3*, *f4*, *f5* and *f5\**** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------| +| K | 128 | Subscriber key K[0]...K[127] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | + +**Table 3. *f1* output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| MAC-A | 64 | Network authentication code MAC-A[0]...MAC-A[63] | + +**Table 4. *f1\** output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| MAC-S | 64 | Resynch authentication code MAC-S[0]...MAC-S[63] | + +**Table 5. *f2* output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|---------------------------| +| RES | 64 | Response RES[0]...RES[63] | + +**Table 6. *f3* output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-------------------------------------| +| CK | 128 | Confidentiality key CK[0]...CK[127] | + +**Table 7. *f4* output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-------------------------------| +| IK | 128 | Integrity key IK[0]...IK[127] | + +**Table 8. *f5* output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------| +| AK | 48 | Anonymity key AK[0]...AK[47] | + +**Table 9. *f5\** output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------| +| AK | 48 | Resynch anonymity key AK[0]...AK[47] | + +Note: Both *f5* and *f5\** outputs are called AK according to reference [2]. In practice only one of them will be calculated in each instance of the authentication and key agreement procedure. + +## 2.6 Coverage + +For each of the algorithms the test data sets have been selected such that, provided the entire set of tests is run: + +- Each input bit of the Rijndael kernel function will have been in both the '0' and '1' states. +- Each input bit of the modes (RAND, K, SQN, AMF) will have been in both the '0' and '1' states. +- Every S-Box entry of the Rijndael kernel function will have been used. + +# 3 Conformance test data for Rijndael + +## 3.1 Overview + +The test data sets presented here are for the cryptographic kernel function Rijndael. The first 6 test sets are the same as in document 3: implementors' test data. + +## 3.2 Format + +The first test set is shown twice, once in binary format, once in hexadecimal format. This is to explicitly show the relationship between the binary data and the hexadecimal representation. The remainder of the test sets are presented in + +hexadecimal format only. A hexadecimal number will be broken up in two rows of two 32-bit words. For example, the number `ee36f7cf037d37d3692f7f0399e7949a` will be written as + +`ee36f7cf 037d37d3` +`692f7f03 99e7949a.` + +## 3.3 Test Sets + +### 3.3.1 Set 1 Binary Format + +Plaintext: 11101110 00110110 11110111 11001111 00000011 01111101 00110111 11010011 01101001 +00101111 01111111 00000011 10011001 11100111 10010100 10011010 +Ciphertext: 10011110 00101001 10000000 11000101 10010111 00111001 11011010 01100111 10110001 +00110110 00110101 01011110 00111100 11101101 11100110 10100010 +Key: 01000110 01011011 01011100 11101000 10110001 10011001 10110100 10011111 10101010 +01011111 00001010 00101110 11100010 00111000 10100110 10111100 + +### 3.3.2 Hexadecimal Format + +| Set | Plaintext | Ciphertext | Key | +|-----|----------------------------------------|----------------------------------------|----------------------------------------| +| 1 | ee36f7cf 037d37d3
692f7f03 99e7949a | 9e2980c5 9739da67
b136355e 3ced6a2 | 465b5ce8 b199b49f
aa5f0a2e e238a6bc | +| 2 | 93cc3640 c5d6a521
d81235bd 0882bf0a | 009a9e09 96561525
f611667b bf79e226 | 0396eb31 7b6d1c36
f19c1c84 cd6ffd16 | +| 3 | 8f7a8f0d 108b7f2d
97a53eac c1d958d9 | 5d9bce85 4decfa0d
a93d28b7 e35f608c | fec86ba6 eb707ed0
8905757b 1bb44b8f | +| 4 | 68c98bbf ab628ec1
adf2a3d9 0c34a751 | db2944cc e8e683cd
03ff1199 31a12135 | 9e5944ae a94b8116
5c82fbf9 f32db751 | +| 5 | a840b1dd 60249aa3
22016b4b 31daf3b8 | 02bffada 7137c492
c00e8452 d8c76eaa | 4ab1deb0 5ca6ceb0
51fc98e7 7d026a84 | +| 6 | d66789ef f5996b9c
ffd89e0a 77148657 | bdf226fe cf9ff996
1e5c2621 b764efb1 | 6c38a116 ac280c45
4f59332e e35c8c4f | +| 7 | 8cbdb88c 620ffe88
f8ce0042 a5052568 | fe8d6888 b5a5c146
efea6660 f7b4e699 | 523ace48 994925ca
0495efd5 0c7c71e2 | +| 8 | 83a4dbcc f3f121e2
154dbf45 512b5a32 | 1c3aff64 cd717a6e
959c95c8 b9cd7d3f | e4aee4fa eeb2f93d
43604f5f 2e65ff25 | +| 9 | d117610c 04f5d3d6
1d8cb6bc 910a918b | 21bc0073 cc9aa7a3
81257774 43f8663f | b2c211ec 004d0323
022e49cc d363c8ff | +| 10 | 9d7cf334 be57ea4d
37f28c8f 8f0a7259 | 1591d87d 8fa69176
eae9fae9 02cd61a4 | 443c5a67 59e04dc2
c9c6e465 823dd5b6 | +| 11 | 0f3c382c 488efe2d
8ce7eaa7 7093a486 | c59e0669 76d92f8e
567b806f 94fb09d2 | 23e5c9b1 8034df64
21f22972 c3bd2d93 | +| 12 | 51c0d9dc cb03b860
43d378ea 5f0dd0f8 | ff00e5a1 a02f7594
3b4a5a1e 39bf5dc3 | d6856512 fd11bf4f
91781e3b 1ea9d8de | +| 13 | 886f7d2c 6f1dc0cc
851fdd41 82e09d99 | 3f65bc17 b47b645b
0fbfbfe8 da4269bf | e5e436d4 593ef7cb
a221cd07 1ccadfdf | +| 14 | dfb0cd05 5b43bd5b
7a31c294 0174b44f | 32976e2e d7fb97b2
bcaaba00 80faf1e5 | d9c9453e 1b858f22
dab53e20 44e849de | +| 15 | 7ced704d b8df58f4
4972cecc 0531bc04 | 53772447 4cf17c9b
105673b5 f37581c8 | 38fe9997 cbac8d9a
c4fc78cc 1fcb1e22 | +| 16 | 878d0fee ad58387e
1b4aaacf b6805e9f | e555cfb7 9663f0ea
fdcc9665 55d6498d | 8d493a28 f17cfb7d
e5be8354 333a66f4 | +| 17 | 29f852ce 631605e3
1722fd87 3bc74208 | d78106ad 6fdae41c
95dd2f7b 5b479a79 | 5d733139 16bde011
c7c26700 0bfe2a9c | +| 18 | 8995e0d7 0281690a
666070db bd6f0f27 | 70b059ad f647d183
a18512a3 72ae683c | 32448511 c137459f
f1d12c17 2cdf7262 | +| 19 | d1ce62ef b1010adb
2f6eabb2 63e16ee4 | ec7fc8b1 10246889
cff7293f e30c8465 | 93833efa 7bb1316e
ebb3dbe3 20a5448d | +| 20 | 260a7f00 98fe903e
9bb255f6 56840627 | 91747de6 7effaff8
578381ef 27e497ec | 09fa653a cbf5acc8
3e307caa 6e18aa67 | + +# 4 Conformance test data for MILENAGE + +## 4.1 Overview + +The test data sets presented here are for the seven functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . The first 6 test sets are the same as in document 2: implementors' test data. + +## 4.2 Format + +Each Test shows the various inputs to the algorithm. This is followed by the configuration field OP, the value $OP_c = OP \oplus E[OP]_k$ and finally by the function outputs. + +The first test set is shown twice, once in binary format, once in hexadecimal format. This is to explicitly show the relationship between the binary data and the hexadecimal representation. The remainder of the test sets are presented in hexadecimal format only. + +## 4.3 Test Sets + +### 4.3.1 Set 1 + +#### Binary Format + +K: 01000110 01011011 01011100 11101000 10110001 10011001 10110100 10011111 10101010 01011111 +00001010 00101110 11100010 00111000 10100110 10111100 + +RAND: 00100011 01010101 00111100 10111110 10010110 00110111 10101000 10011101 00100001 10001010 +11100110 01001101 10101110 01000111 10111111 00110101 + +SQN: 11111111 10011011 10110100 11010000 10110110 00000111 + +AMF: 10111001 10111001 + +OP: 11001101 11000010 00000010 11010101 00010010 00111110 00100000 11110110 00101011 01101101 +01100111 01101010 11000111 00101100 10110011 00011000 + +OPc: 11001101 01100011 11001011 01110001 10010101 01001010 10011111 01001110 01001000 10100101 +10011001 01001110 00110111 10100000 00101011 10101111 + +f1: 01001010 10011111 11111010 11000011 01010100 11011111 10101111 10110011 + +f1\*: 00000001 11001111 10101111 10011110 11000100 11101000 01110001 11101001 + +f2: 10100101 01000010 00010001 11010101 11100011 10111010 01010000 10111111 + +f5: 10101010 01101000 10011100 01100100 10000011 01110000 + +f3: 10110100 00001011 10101001 10100011 11000101 10001011 00101010 00000101 10111011 11110000 +11011001 10000111 10110010 00011011 11111000 11001011 + +f4: 11110111 01101001 10111100 11010111 01010001 00000100 01000110 00000100 00010010 01110110 +01110010 01110001 00011100 01101101 00110100 01000001 + +f5\*: 01000101 00011110 10001011 11101100 10100100 00111011 + +#### Hexadecimal Format + +| Variable | Value | +|-----------------|-------------------------------------| +| K | 465b5ce8 b199b49f aa5f0a2e e238a6bc | +| RAND | 23553cbe 9637a89d 218ae64d ae47bf35 | +| SQN | ff9bb4d0 b607 | +| AMF | b9b9 | +| OP | cdc202d5 123e20f6 2b6d676a c72cb318 | +| OP c | cd63cb71 954a9f4e 48a5994e 37a02baf | +| f1 | 4a9ffac3 54dfafb3 | +| f1* | 01cfaf9e c4e871e9 | +| f2 | a54211d5 e3ba50bf | +| f5 | aa689c64 8370 | +| f3 | b40ba9a3 c58b2a05 bbf0d987 b21bf8cb | +| f4 | f769bcd7 51044604 12767271 1c6d3441 | +| f5* | 451e8bec a43b | + +### 4.3.2 Test Set 2 + +| Variable | Value | +|----------|-------------------------------------| +| K | 465b5ce8 b199b49f aa5f0a2e e238a6bc | +| RAND | 23553cbe 9637a89d 218ae64d ae47bf35 | +| SQN | ff9bb4d0 b607 | +| AMF | b9b9 | +| OP | cdc202d5 123e20f6 2b6d676a c72cb318 | +| OPc | cd63cb71 954a9f4e 48a5994e 37a02baf | +| f1 | 4a9ffac3 54dfafb3 | +| f1* | 01cfaf9e c4e871e9 | +| f2 | a54211d5 e3ba50bf | +| f5 | aa689c64 8370 | +| f3 | b40ba9a3 c58b2a05 bbf0d987 b21bf8cb | +| f4 | f769bcd7 51044604 12767271 1c6d3441 | +| f5* | 451e8bec a43b | + +### 4.3.3 Test Set 3 + +| Variable | Value | +|----------|-------------------------------------| +| K | fec86ba6 eb707ed0 8905757b 1bb44b8f | +| RAND | 9f7c8d02 1accf4db 213ccff0 c7f71a6a | +| SQN | 9d027759 5ffc | +| AMF | 725c | +| OP | dbc59adc b6f9a0ef 735477b7 fadf8374 | +| OPc | 1006020f 0a478bf6 b699f15c 062e42b3 | +| f1 | 9cabc3e9 9baf7281 | +| f1* | 95814ba2 b3044324 | +| f2 | 8011c48c 0c214ed2 | +| f5 | 33484dc2 136b | +| f3 | 5dbdbb29 54e8f3cd e665b046 179a5098 | +| f4 | 59a92d3b 476a0443 487055cf 88b2307b | +| f5* | deacdd84 8cc6 | + +### 4.3.4 Test Set 4 + +| Variable | Value | +|----------|-------------------------------------| +| K | 9e5944ae a94b8116 5c82fbf9 f32db751 | +| RAND | ce83dbc5 4ac0274a 157c17f8 0d017bd6 | +| SQN | 0b604a81 eca8 | +| AMF | 9e09 | +| OP | 223014c5 806694c0 07ca1eee f57f004f | +| OPc | a64a507a e1a2a98b b88eb421 0135dc87 | +| f1 | 74a58220 cba84c49 | +| f1* | ac2cc74a 96871837 | +| f2 | f365cd68 3cd92e96 | +| f5 | f0b9c08a d02e | +| f3 | e203edb3 971574f5 a94b0d61 b816345d | +| f4 | 0c4524ad eac041c4 dd830d20 854fc46b | +| f5* | 6085a86c 6f63 | + +### 4.3.5 Test Set 5 + +| Variable | Value | +|----------|-------------------------------------| +| K | 4ab1deb0 5ca6ceb0 51fc98e7 7d026a84 | +| RAND | 74b0cd60 31a1c833 9b2b6ce2 b8c4a186 | +| SQN | e880a1b5 80b6 | +| AMF | 9f07 | +| OP | 2d16c5cd 1fdf6b22 383584e3 bef2a8d8 | +| OPc | dcf07cbd 51855290 b92a07a9 891e523e | +| f1 | 49e785dd 12626ef2 | +| f1* | 9e857903 36bb3fa2 | +| f2 | 5860fc1b ce351e7e | +| f5 | 31e11a60 9118 | +| f3 | 7657766b 373d1c21 38f307e3 de9242f9 | +| f4 | 1c42e960 d89b8fa9 9f2744e0 708ccb53 | +| f5* | fe2555e5 4aa9 | + +### 4.3.6 Test Set 6 + +| Variable | Value | +|----------|-------------------------------------| +| K | 6c38a116 ac280c45 4f59332e e35c8c4f | +| RAND | ee6466bc 96202c5a 557abbef f8babf63 | +| SQN | 414b9822 2181 | +| AMF | 4464 | +| OP | 1ba00a1a 7c6700ac 8c3ff3e9 6ad08725 | +| OPc | 3803ef53 63b947c6 aaa225e5 8fae3934 | +| f1 | 078adfb4 88241a57 | +| f1* | 80246b8d 0186bcf1 | +| f2 | 16c8233f 05a0ac28 | +| f5 | 45b0f69a b06c | +| f3 | 3f8c7587 fe8e4b23 3af676ae de30ba3b | +| f4 | a7466cc1 e6b2a133 7d49d3b6 6e95d7b4 | +| f5* | 1f53cd2b 1113 | + +### 4.3.7 Test Set 7 + +| Variable | Value | +|----------|-------------------------------------| +| K | 2d609d4d b0ac5bf0 d2c0de26 7014de0d | +| RAND | 194aa756 013896b7 4b4a2a3b 0af4539e | +| SQN | 6bf69438 c2e4 | +| AMF | 5f67 | +| OP | 460a4838 5427aa39 264aac8e fc9e73e8 | +| OPc | c35a0ab0 bcbfc925 2caff15f 24efbde0 | +| f1 | bd07d300 3b9e5cc3 | +| f1* | bcb6c2fc ad152250 | +| f2 | 8c25a16c d918a1df | +| f5 | 7e6455f3 4cf3 | +| f3 | 4cd08460 20f8fa07 31dd47cb dc6be411 | +| f4 | 88ab80a4 15f15c73 711254a1 d388f696 | +| f5* | dc6dd01e 8f15 | + +### 4.3.8 Test Set 8 + +| Variable | Value | +|----------|-------------------------------------| +| K | a530a7fe 428fad10 82c45edd fce13884 | +| RAND | 3a4c2b32 45c50eb5 c71d0863 9395764d | +| SQN | f63f5d76 8784 | +| AMF | b90e | +| OP | 511c6c4e 83e38c89 b1c5d8dd e62426fa | +| OPc | 27953e49 bc8af6dc c6e730eb 80286be3 | +| f1 | 53761fbd 679b0bad | +| f1* | 21adfd33 4a10e7ce | +| f2 | a63241e1 ffc3e5ab | +| f5 | 88196c47 986f | +| f3 | 10f05bab 75a99a5f bb98a9c2 87679c3b | +| f4 | f9ec0865 eb32f223 69cade40 c59c3a44 | +| f5* | c987a3d2 3115 | + +### 4.3.9 Test Set 9 + +| Variable | Value | +|----------|-------------------------------------| +| K | d9151cf0 4896e258 30bf2e08 267b8360 | +| RAND | f761e5e9 3d603feb 730e2755 6cb8a2ca | +| SQN | 47ee0199 820a | +| AMF | 9113 | +| OP | 75fc2233 a44294ee 8e6de25c 4353d26b | +| OPc | c4c93eff e8a08138 c203d4c2 7ce4e3d9 | +| f1 | 66cc4be4 4862af1f | +| f1* | 7a4b8d7a 8753f246 | +| f2 | 4a90b217 1ac83a76 | +| f5 | 82a0f528 7a71 | +| f3 | 71236b71 29f9b22a b77ea7a5 4c96da22 | +| f4 | 90527eba a5588968 db417273 25a04d9e | +| f5* | 527dbf41 f35f | + +### 4.3.10 Test Set 10 + +| Variable | Value | +|----------|-------------------------------------| +| K | a0e2971b 6822e8d3 54a18cc2 35624ecb | +| RAND | 08eff828 b13fdb56 2722c65c 7f30a9b2 | +| SQN | db5c0664 81e0 | +| AMF | 716b | +| OP | 323792fa ca21fb4d 5d6f13c1 45a9d2c1 | +| OPc | 82a26f22 bba9e948 8f949a10 d98e9cc4 | +| f1 | 9485fe24 621cb9f6 | +| f1* | bce325ce 03e2e9b9 | +| f2 | 4bc2212d 8624910a | +| f5 | a2f858aa 9e5d | +| f3 | 08cef6d0 04ec6147 1a3c3cda 048137fa | +| f4 | ed0318ca 5deb9206 272f6e8f a64ba411 | +| f5* | 74e76fbb ec38 | + +### 4.3.11 Test Set 11 + +| Variable | Value | +|----------|-------------------------------------| +| K | 0da6f7ba 86d5eac8 a19cf563 ac58642d | +| RAND | 679ac4db acd7d233 ff9d6806 f4149ce3 | +| SQN | 6e2331d6 92ad | +| AMF | 224a | +| OP | 4b9a26fa 459e3acb ff36f401 5de3bdcl | +| OPc | 0db1071f 8767562c a43a0a64 c41e8d08 | +| f1 | 2831d7ae 9088e492 | +| f1* | 9b2e1695 1135d523 | +| f2 | 6fc30fee 6d123523 | +| f5 | 4c539a26 e1fa | +| f3 | 69b1cae7 c7429d97 5e245cac b05a517c | +| f4 | 74f24e8c 26df58e1 b38d7dcd 4f1b7fbd | +| f5* | 07861e12 6928 | + +### 4.3.12 Test Set 12 + +| Variable | Value | +|----------|-------------------------------------| +| K | 77b45843 c88e58c1 0d202684 515ed430 | +| RAND | 4c47eb30 76dc55fe 5106cb20 34b8cd78 | +| SQN | fe1a8731 005d | +| AMF | ad25 | +| OP | bf3286c7 a51409ce 95724d50 3bfe6e70 | +| OPc | d483afae 562409a3 26b5bb0b 20c4d762 | +| f1 | 08332d7e 9f484570 | +| f1* | ed41b734 489d5207 | +| f2 | aefa357b eac2a87a | +| f5 | 30ff25cd adf6 | +| f3 | 908c43f0 569cb8f7 4bc971e7 06c36c5f | +| f4 | c251df0d 888dd932 9bcf4665 5b226e40 | +| f5* | e84ed0d4 677e | + +### 4.3.13 Test Set 13 + +| Variable | Value | +|----------|-------------------------------------| +| K | 729b1772 9270dd87 ccdf1bfe 29b4e9bb | +| RAND | 311c4c92 9744d675 b720f3b7 e9b1cbd0 | +| SQN | c85c4cf6 5916 | +| AMF | 5bb2 | +| OP | d04c9c35 bd2262fa 810d2924 d036fd13 | +| OPc | 228c2f2f 06ac3268 a9e616ee 16db4ba1 | +| f1 | ff794fe2 f827ebf8 | +| f1* | 24fe4dc6 1e874b52 | +| f2 | 98dbbd09 9b3b408d | +| f5 | 5380d158 cfe3 | +| f3 | 44c0f23c 5493cfd2 41e48f19 7e1d1012 | +| f4 | 0c9fb816 13884c25 35dd0eab f3b440d8 | +| f5* | 87ac3b55 9fb6 | + +### 4.3.14 Test Set 14 + +| Variable | Value | +|----------|-------------------------------------| +| K | d32dd23e 89dc6623 54ca12eb 79dd32fa | +| RAND | cf7d0ab1 d9430695 0bf12018 fbd46887 | +| SQN | 484107e5 6a43 | +| AMF | b5e6 | +| OP | fe75905b 9da47d35 6236d031 4e09c32e | +| OPc | d22a4b41 80a53257 08a5ff70 d9f67ec7 | +| f1 | cf19d62b 6a809866 | +| f1* | 5d269537 e45e2ce6 | +| f2 | af4a411e 1139f2c2 | +| f5 | 217af492 72ad | +| f3 | 5af86b80 edb70df5 292cc112 1cbad50c | +| f4 | 7f4d6ae7 440e1878 9a8b75ad 3f42f03a | +| f5* | 900e101c 677e | + +### 4.3.15 Test Set 15 + +| Variable | Value | +|----------|-------------------------------------| +| K | af7c65e1 927221de 591187a2 c5987a53 | +| RAND | 1f0f8578 464fd59b 64bed2d0 9436b57a | +| SQN | 3d627b01 418d | +| AMF | 84f6 | +| OP | 0c7acb8d 95b7d4a3 1c5aca6d 26345a88 | +| OPc | a4cf5c81 55c08a7e ff418e54 43b98e55 | +| f1 | c37cae78 05642032 | +| f1* | 68cd09a4 52d8db7c | +| f2 | 7bffa5c2 f41fbc05 | +| f5 | 837fd7b7 4419 | +| f3 | 3f8c3f3c cf7625bf 77fc94bc fd22fd26 | +| f4 | abcbae8f d46115e9 961a55d0 da5f2078 | +| f5* | 56e97a60 90b1 | + +### 4.3.16 Test Set 16 + +| Variable | Value | +|----------|-------------------------------------| +| K | 5bd7ecd3 d3127a41 d12539be d4e7cf71 | +| RAND | 59b75f14 251c7503 1d0bcbac 1c2c04c7 | +| SQN | a298ae89 29dc | +| AMF | d056 | +| OP | f967f760 38b920a9 cd25e10c 08b49924 | +| OPc | 76089d3c 0ff3efdc 6e36721d 4fceb747 | +| f1 | c3f25cd9 4309107e | +| f1* | b0c8ba34 3665afcc | +| f2 | 7e3f44c7 591f6f45 | +| f5 | 5be11495 525d | +| f3 | d42b2d61 5e49a03a c275a5ae f97af892 | +| f4 | 0b3f8d02 4fe6bfaf aa982b8f 82e319c2 | +| f5* | 4d6a34a1 e4eb | + +### 4.3.17 Test Set 17 + +| Variable | Value | +|----------|-------------------------------------| +| K | 6cd1c6ce b1e01e14 f1b82316 a90b7f3d | +| RAND | f69b78f3 00a0568b ce9f0cb9 3c4be4c9 | +| SQN | b4fce5fe b059 | +| AMF | e4bb | +| OP | 078bfca9 564659ec d8851e84 e6c59b48 | +| OPc | a219dc37 f1dc7d66 738b5843 c799f206 | +| f1 | 69a90869 c268cb7b | +| f1* | 2e0fdcf9 fd1cfa6a | +| f2 | 70f6bdb9 ad21525f | +| f5 | 1c408a85 8b3e | +| f3 | 6edaf99e 5bd9f85d 5f36d91c 1272fb4b | +| f4 | d61c853c 280dd9c4 6f297bae c386de17 | +| f5* | aa4ae52d aa30 | + +### 4.3.18 Test Set 18 + +| Variable | Value | +|----------|-------------------------------------| +| K | b73a90cb cf3afb62 2dba83c5 8a8415df | +| RAND | b120f1c1 a0102a2f 507dd543 de68281f | +| SQN | f1e8a523 a36d | +| AMF | 471b | +| OP | b672047e 003bb952 dca6cb8a f0e5b779 | +| OPc | df0c6786 8fa25f74 8b7044c6 e7c245b8 | +| f1 | ebd70341 bcd415b0 | +| f1* | 12359f5d 82220c14 | +| f2 | 479dd25c 20792d63 | +| f5 | aefdaa5d dd99 | +| f3 | 66195dbe d0313274 c5ca7766 615fa25e | +| f4 | 66bec707 eb2afc47 6d7408a8 f2927b36 | +| f5* | 12ec2b87 fbb1 | + +### 4.3.19 Test Set 19 + +| Variable | Value | +|----------|-------------------------------------| +| K | 51222502 14c33e72 3a5dd523 fc145fc0 | +| RAND | 81e92b6c 0ee0e12e bceba8d9 2a99dfa5 | +| SQN | 16f3b3f7 0fc2 | +| AMF | c3ab | +| OP | c9e87632 86b5b9ff bdf56e12 97d0887b | +| OPc | 981d464c 7c52eb6e 50362349 84ad0bcf | +| f1 | 2a5c23d1 5ee351d5 | +| f1* | 62dae385 3f3af9d2 | +| f2 | 28d7b0f2 a2ec3de5 | +| f5 | ada15aeb 7bb8 | +| f3 | 5349fbe0 98649f94 8f5d2e97 3a81c00f | +| f4 | 9744871a d32bf9bb d1dd5ce5 4e3e2e5a | +| f5* | d461bc15 475d | + +### 4.3.20 Test Set 20 + +| Variable | Value | +|----------|-------------------------------------| +| K | 90dca4ed a45b53cf 0f12d7c9 c3bc6a89 | +| RAND | 9fddc720 92c6ad03 6b6e4647 89315b78 | +| SQN | 20f813bd 4141 | +| AMF | 61df | +| OP | 3ffcfe5b 7b111158 9920d352 8e84e655 | +| OPc | cb9cccc4 b9258e6d ca476037 9fb82581 | +| f1 | 09db94ea b4f8149e | +| f1* | a29468aa 9775b527 | +| f2 | a95100e2 760952cd | +| f5 | 83cfd54d b913 | +| f3 | b5f2da03 883b69f9 6bf52e02 9ed9ac45 | +| f4 | b4721368 bc16ea67 875c5598 688bb0ef | +| f5* | 4f203939 2ddc | + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|------------|----|-----------|---------------|--------------------------------------| +| TSG SA # | Version | CR | Tdoc SA | New Version | Subject/Comment | +| SP-10 | SAGE v 1.0 | - | SP-010630 | 3.0.0 | Approved as Release 1999 | +| SP-11 | 3.0.0 | - | - | 4.0.0 | Updated to Release 4 | +| SP-16 | 4.0.0 | - | - | 5.0.0 | Updated to Release 5 | +| SP-26 | 5.0.0 | - | - | 6.0.0 | Updated to Release 6 | +| SP-36 | 6.0.0 | - | - | 7.0.0 | Updated to Release 7 | +| SP-42 | 7.0.0 | - | - | 8.0.0 | Updated to Release 8 | +| SP-46 | 8.0.0 | - | - | 9.0.0 | Updated to Release 9 | +| SP-51 | 9.0.0 | - | - | 10.0.0 | Updated to Release 10 | +| 2012-09 | - | - | - | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | - | - | - | 12.0.0 | Update to Rel-12 version (MCC) | +| 2016-01 | 12.0.0 | - | - | 13.0.0 | Update to Rel-13 version (MCC) | + +| 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-10 | - | - | - | - | - | Update to Rel-15 version (MCC) | 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/35_series/35215/raw.md b/marked/Rel-16/35_series/35215/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f08e9f77dd8824c11c997c7b30799cd7790d1580 --- /dev/null +++ b/marked/Rel-16/35_series/35215/raw.md @@ -0,0 +1,90 @@ + + + + + + +# --- Contents + +- Foreword ..... 5 +- 1 Scope..... 6 +- 2 References..... 6 +- 3 Definitions, symbols and abbreviations..... 6 + - 3.1 Definitions..... 6 + - 3.2 Symbols..... 6 + - 3.3 Abbreviations ..... 6 +- 4 Technical provisions ..... 6 +- Annex A (informative): Change history..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE Specification: "Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications" v2.1. + +Note: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|---------------------------------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2006-10 | | | | | Draft document from ETSI SAGE | | 0.1.0 | +| 2006-03 | SP-31 | | | | For information to TSG SA. Document not provided due to limitations arising from export controls. | 0.1.0 | 1.0.0 | +| 2006-03 | | | | | 3GPP Support Team recast of document to refer to SAGE Specification | 1.0.0 | 1.1.0 | +| 2006-06 | SP-32 | SP-060422 | - | - | Approved at SA #32 | 1.1.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | Upgrade to Release 8 | 7.0.0 | 8.0.0 | +| 2009-03 | SP-43 | SP-090140 | 0001 | | Improvement to sample C code, and removal of apparent keystream length limit | 8.0.0 | 8.1.0 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.1.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35216/raw.md b/marked/Rel-16/35_series/35216/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7c051c7083b6418d85395b69f247bc3961c3408f --- /dev/null +++ b/marked/Rel-16/35_series/35216/raw.md @@ -0,0 +1,90 @@ + + + + + + +# --- Contents + +- Foreword ..... 5 +- 1 Scope..... 6 +- 2 References..... 6 +- 3 Definitions, symbols and abbreviations..... 6 + - 3.1 Definitions..... 6 + - 3.2 Symbols..... 6 + - 3.3 Abbreviations ..... 6 +- 4 Technical provisions ..... 6 +- Annex A (informative): Change history..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE Specification: "Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification" version 1.1, 2006-09-06. + +NOTE: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|-----|-----|---------------------------------------------------------------------------------------------------|--------|---------------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 2006-10 | | | | | Draft document from ETSI SAGE | | 0.1.0 | | +| 2006-03 | SP-31 | | | | For information to TSG SA. Document not provided due to limitations arising from export controls. | 0.1.0 | 1.0.0 | | +| 2006-03 | | | | | 3GPP Support Team recast of document to refer to SAGE Specification | 1.0.0 | 1.1.0 | | +| 2006-06 | SP-32 | SP-060422 | - | - | Approved at SA #32 | 1.1.0 | 7.0.0 | | +| 2008-12 | SP-42 | - | - | - | Upgrade to Release 8 | 7.0.0 | 8.0.0 | | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | | +| 2010-12 | SP-50 | SP-100724 | 001 | 1 | Correction of reference | 9.0.0 | 9.1.0 | | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35217/raw.md b/marked/Rel-16/35_series/35217/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ee5b4734b09cd9deddf55aa198864c64cb1574e2 --- /dev/null +++ b/marked/Rel-16/35_series/35217/raw.md @@ -0,0 +1,90 @@ + + + + + + +# --- Contents + +- Foreword ..... 5 +- 1 Scope..... 6 +- 2 References..... 6 +- 3 Definitions, symbols and abbreviations..... 6 + - 3.1 Definitions..... 6 + - 3.2 Symbols..... 6 + - 3.3 Abbreviations ..... 6 +- 4 Technical provisions ..... 6 +- Annex A (informative): Change history..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE Specification: "Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data" version 1.1 + +Note: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|---------------------------------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2006-10 | | | | | Draft document from ETSI SAGE | | 0.1.0 | +| 2006-03 | SP-31 | | | | For information to TSG SA. Document not provided due to limitations arising from export controls. | 0.1.0 | 1.0.0 | +| 2006-03 | | | | | 3GPP Support Team recast of document to refer to SAGE Specification | 1.0.0 | 1.1.0 | +| 2006-06 | SP-32 | SP-060422 | - | - | Approved at SA #32 | 1.1.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | Upgrade to Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2012-12 | SP-58 | SP-120855 | 005 | -- | Correction to UIA2 test vector | 11.0.0 | 11.1.0 | +| 2012-12 | SP-58 | -- | -- | -- | Upgrade to Rel-12 | 11.1.0 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35218/raw.md b/marked/Rel-16/35_series/35218/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a02fc437b824b0ec1d7355976d2e41ec894eaec2 --- /dev/null +++ b/marked/Rel-16/35_series/35218/raw.md @@ -0,0 +1,90 @@ + + + + + + +# --- Contents + +- Foreword ..... 5 +- 1 Scope..... 6 +- 2 References..... 6 +- 3 Definitions, symbols and abbreviations..... 6 + - 3.1 Definitions..... 6 + - 3.2 Symbols..... 6 + - 3.3 Abbreviations ..... 6 +- 4 Technical provisions ..... 6 +- Annex A (informative): Change history..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE Specification: "Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data" version 1.0, 2006-01-10 + +Note: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|---------------------------------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2006-10 | | | | | Draft document from ETSI SAGE | | 0.1.0 | +| 2006-03 | SP-31 | | | | For information to TSG SA. Document not provided due to limitations arising from export controls. | 0.1.0 | 1.0.0 | +| 2006-03 | | | | | 3GPP Support Team recast of document to refer to SAGE Specification | 1.0.0 | 1.1.0 | +| 2006-06 | SP-32 | SP-060422 | - | - | Approved at SA #32 | 1.1.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | Upgrade to Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2012-12 | SP-58 | SP-120855 | 005 | -- | Update of URL to 3GPP algorithms page | 11.0.0 | 11.1.0 | +| 2014-10 | - | - | - | - | Update to Rel-12 version (MCC) (this does not include CR006) | 11.1.0 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35221/raw.md b/marked/Rel-16/35_series/35221/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7761ca3003eb28e0add346d618bc53afa4152542 --- /dev/null +++ b/marked/Rel-16/35_series/35221/raw.md @@ -0,0 +1,87 @@ + + + + + + +# --- 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 Technical provisions ..... | 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 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE "Specification of the 3GPP Confidentiality and Integrity Algorithms 128-EEA3 & 128-EIA3; Document 1: 128-EEA3 & 128-EIA3 Specification" version 1.7. + +NOTE: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|----|-----|--------------------------------------------------------------------------------------------------------------------|--|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | | Old | New | +| 2011-07 | SA-53 | SP-110500 | -- | -- | Submission for Information and Approval | | --- | 1.0.0 | +| 2011-09 | SA-53 | SP-110565 | -- | -- | Submission for Information and Approval - correction of cover sheet and update of TSG Doc. field in Change History | | 1.0.0 | 1.0.1 | +| 2012-01 | -- | -- | -- | -- | Publication | | 1.0.1 | 11.0.0 | +| 2012-05 | -- | -- | -- | -- | Reference 2 now to specific version | | 11.0.0 | 11.0.1 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | | 11.0.1 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35222/raw.md b/marked/Rel-16/35_series/35222/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d026e41e934352f895e85ef9542a4bf932457ea4 --- /dev/null +++ b/marked/Rel-16/35_series/35222/raw.md @@ -0,0 +1,87 @@ + + + + + + +# --- 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 Technical provisions ..... | 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 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE "Specification of the 3GPP Confidentiality and Integrity Algorithms 128-EEA3 & 128-EIA3; Document 2: ZUC Specification" version 1.6. + +NOTE: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|--------------------------------------------------------------------------------------------------------------------|------------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2011-07 | SA-53 | SP-110501 | -- | -- | Submission for Information and Approval | --- | 1.0.0 | +| 2011-09 | SA-53 | SP-110569 | -- | -- | Submission for Information and Approval - correction of cover sheet and update of TSG Doc. field in Change History | 1.0.0 | 1.0.1 | +| 2012-01 | -- | -- | -- | -- | Publication | 1.0.1 | 11.0.0 | +| 2012-05 | -- | -- | -- | -- | Reference 2 now to specific version | 11.0.0 | 11.0.1 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.1 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35223/raw.md b/marked/Rel-16/35_series/35223/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9b30d6e8528a08898d4106ee08959965d4870fe6 --- /dev/null +++ b/marked/Rel-16/35_series/35223/raw.md @@ -0,0 +1,87 @@ + + + + + + +# --- 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 Technical provisions ..... | 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 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE "Specification of the 3GPP Confidentiality and Integrity Algorithms 128-EEA3 & 128-EIA3; Document 3: Implementor's Test Data " version 1.1. + +NOTE: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|----|-----|--------------------------------------------------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2011-07 | SA-53 | SP-110502 | -- | -- | Submission for Information and Approval | --- | 1.0.0 | +| 2011-09 | SA-53 | SP-110566 | -- | -- | Submission for Information and Approval - correction of cover sheet and update of TSG Doc. field in Change History | 1.0.0 | 1.0.1 | +| 2012-01 | -- | -- | -- | -- | Publication | 1.0.1 | 11.0.0 | +| 2012-05 | -- | -- | -- | -- | Reference 2 now to specific version | 11.0.0 | 11.0.1 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.1 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35231/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-16/35_series/35231/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2eea15d89adc7361fadc4d4d40d3fce1d3a68d4 --- /dev/null +++ b/marked/Rel-16/35_series/35231/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46356adbee80f21084522e3d1f95fbe08336ea83307f68734ac231b88c815d14 +size 53979 diff --git a/marked/Rel-16/35_series/35231/raw.md b/marked/Rel-16/35_series/35231/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d9f6ae05ec3d4534b44c7068dce6a06c8a33377c --- /dev/null +++ b/marked/Rel-16/35_series/35231/raw.md @@ -0,0 +1,1219 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and symbols..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 6 | +| 4 Preliminary information..... | 7 | +| 4.1 Introduction ..... | 7 | +| 4.2 Notation..... | 7 | +| 4.2.1 Radix..... | 7 | +| 4.2.2 Bit-numbering for inputs and outputs..... | 7 | +| 4.2.3 Assignment operations ..... | 7 | +| 4.2.4 Void ..... | 8 | +| 4.3 Void..... | 8 | +| 5 Inputs and outputs ..... | 8 | +| 5.1 Tuak inputs and outputs ..... | 8 | +| 5.2 Keccak and its inputs and outputs..... | 9 | +| 5.3 Other inputs and substrings..... | 10 | +| 6 Definition of the example algorithms ..... | 10 | +| 6.1 Derivation of TOP C ..... | 10 | +| 6.2 Specification of the function f1 ..... | 11 | +| 6.3 Specification of the function f1* ..... | 12 | +| 6.4 Specification of the functions f2, f3, f4 and f5..... | 12 | +| 6.5 Specification of the function f5* ..... | 14 | +| 7 Implementation considerations ..... | 14 | +| 7.1 TOP C computed on or off the UIICC?..... | 14 | +| 7.2 Further customization..... | 15 | +| 7.3 Resistance to side channel attacks..... | 15 | +| Annex A (normative): Tuak diagrams..... | 16 | +| Annex B (informative): TuakApplication Programme Interface ( AP) in ANSI CI ..... | 18 | +| Annex C (normative): Specification of the Keccak permutation used within Tuak ..... | 19 | +| Annex D (informative): Example source code for Tuak (ANSI C)..... | 21 | +| Annex E (informative): Example source code for Keccak (ANSI C)..... | 23 | +| Annex F (informative): Change history..... | 28 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The present document is one of three, which between them form the entire specification of the example algorithms, entitled: + +- 3GPP TS 35.231: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 1: Algorithm specification "** +- 3GPP TS 35.232: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 2: Implementers' test data"** +- 3GPP TS 35.233: "Specification of the Tuak algorithm Set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; +**Document 3: Design conformance test data"** + +# 1 Scope + +The present document and the other Technical Specifications in the series, TS 35.232 [15] and 35.233 [16] contain an example set of algorithms which could be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\** for 3GPP systems. All seven functions are operator-specifiable rather than being fully standardised and other algorithms could be envisaged. + +# 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 33.102: "3G Security; Security Architecture 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm specification.[3] "The KECCAK Reference", version 3.0, 14 January 2011, G. Bertoni, J. Daemen, M. Peeters, G. van Aasche, (available at ). +- [4] "KECCAK Implementation Overview", version 3.2, 29 May 2012, G. Bertoni, J. Daemen, M. Peeters, G. van Aasche, R. van Keer (available at ). +- [5] "SAKURA: a flexible coding for tree hashing", 3 June 2013, G. Bertoni, J. Daemen, M. Peeters, G. van Aasche, (available at ). +- [6] "Securing the AES finalists against Power Analysis Attacks", in FSE 2000, Seventh Fast Software Encryption Workshop, Thomas S. Messerges, ed. Schneier, Springer Verlag, 2000. +- [7] "Timing Attacks on Implementations of Diffie-Hellman, RSA, DSS, and Other Systems", P. C. Kocher, in CRYPTO'96, Lecture Notes in Computer Science #1109, Springer Verlag, 1996. +- [8] "Side Channel Cryptanalysis of Product Ciphers", in ESORICS'98, Lecture Notes in Computer Science #1485, Springer Verlag, 1998, J. Kelsey, B. Schneier, D. Wagner, C. Hall. +- [9] "DES and differential power analysis", in CHES'99, Lecture Notes in Computer Science #1717, Springer Verlag, 1999, L. Goubin, J. Patarin. +- [10] "Differential Power Analysis", in CRYPTO'99, Lecture Notes in Computer Science #1666, Springer Verlag, 1999, P. Kocher, J. Jaffe, B. Jun. +- [11] "On Boolean and Arithmetic Masking against Differential Power Analysis", in CHES'00, Lecture Notes in Computer Science series, Springer Verlag, 2000, L. Goubin, J.-S. Coron. +- [12] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". +- [13] Void +- [14] 3GPP TR 21.905: "Vocabulary for 3GPP specifications". +- [15] 3GPP TS 35.232: "3G Security; Specification of the Tuak Algorithm Set: a Second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Implementers' test data". + +[16] 3GPP TS 35.233: "3G Security; Specification of the Tuak Algorithm Set: a second example algorithm set for the 3GPP authentication and key generation functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ ; Document 3: Design conformance test data". + +# 3 Definitions and symbols + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [14] 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 [14]. + +**Tuak:** The name of this algorithm set is "Tuak". It should be pronounced like "too-ack". + +## 3.2 Symbols + +| | | +|-------------|-----------------------------------------------------------------------------------------------------------------| +| = | The assignment operator | +| $\oplus$ | The bitwise exclusive-OR operation | +| $\parallel$ | The concatenation of the two operands | +| $X[i]$ | The $i^{\text{th}}$ bit of the variable X . ( $X = X[0] \parallel X[1] \parallel X[2] \parallel \dots$ ) | +| $\Pi$ | the permutation Keccak-f[1600] (See clause 5.2 and annex C) | + +The following represent variables used in the algorithm: + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AK | a 48-bit anonymity key that is the output of either of the functions $f5$ and $f5^*$ | +| AMF | a 16-bit authentication management field that is an input to the functions $f1$ and $f1^*$ | +| CK | a 128-bit or 256-bit confidentiality key that is the output of the function $f3$ | +| IK | a 128-bit or 256-bit integrity key that is the output of the function $f4$ | +| IN | a 1600-bit value that is used as the input to the permutation $\Pi$ when computing the functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ | +| INSTANCE | an 8-bit value that is used to specify different modes of operation and different parameter lengths within the algorithm set | +| K | a 128-bit or 256-bit subscriber key that is an input to the functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ | +| MAC-A | a 64-bit, 128-bit or 256-bit network authentication code that is the output of the function $f1$ | +| MAC-S | a 64-bit, 128-bit or 256-bit resynchronization authentication code that is the output of the function $f1^*$ | +| OP | Operator Variant Algorithm Configuration Field (used in MILENAGE) | +| OUT | a 1600-bit value that is taken as the output of the permutation $\Pi$ when computing the functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ | +| RAND | a 128-bit random challenge that is an input to the functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ | +| RES | a 32-bit, 64-bit, 128-bit or 256-bit signed response that is the output of the function $f2$ | +| SQN | a 48-bit sequence number that is an input to either of the functions $f1$ and $f1^*$ . (For $f1^*$ this input is more precisely called $SQN_{\text{MS}}$ .) See informative Annex C of [1] for methods of encoding sequence numbers | +| $SQN_{\text{MS}}$ | (See SQN) | +| TOP | a 256-bit Operator Variant Algorithm Configuration Field that is a component of the functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ | +| $TOP_C$ | a 256-bit value derived from TOP and K and used within the computation of the functions | + +# 4 Preliminary information + +## 4.1 Introduction + +Within the security architecture of the 3GPP system there are seven security functions related to authentication and key agreement: $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ . The operation of these functions falls within the domain of one operator, and the functions are therefore to be specified by each operator rather than being fully standardized. The algorithms specified in the present document are examples that may be used by an operator who does not wish to design his own. + +The algorithm specified is called Tuak (pronounced "too-ack"). + +It is not mandatory that the particular algorithms specified in the present document are used. + +The inputs and outputs of all seven algorithms are defined in clause 4.4. + +## 4.2 Notation + +### 4.2.1 Radix + +The prefix 0x is used to indicate hexadecimal numbers. + +### 4.2.2 Bit-numbering for inputs and outputs + +3GPP TS 33.102 [1] includes the following convention. (There is similar text in the specification of MILENAGE, as defined in 3GPP TS 35.206 [2]): + +All data variables in the present document are presented with the most significant substring on the left hand side and the least significant substring on the right hand side. A substring may be a bit, byte or other arbitrary length bit string. Where a variable is broken down into a number of substrings, the left-most (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant. + +So, for example, RAND[0] is the most-significant bit of RAND and RAND[127] is the least significant bit of RAND. + +This convention applies to all inputs and outputs to Tuak, as listed in tables 1 to 9 below. + +However, internally to the Tuak specification variables are simply treated as indexed bit strings, without a specific indication of bit, byte or word order. + +### 4.2.3 Assignment operations + +The assignment operator '=' is used in many programming languages. Thus: + +$$\langle \text{variable} \rangle = \langle \text{expression} \rangle$$ + +It means that $\langle \text{variable} \rangle$ assumes the value that $\langle \text{expression} \rangle$ had before the assignment took place. For instance, + +$$x = x + y + 3$$ + +means: + +$$(\text{new value of } x) \text{ becomes } (\text{old value of } x) + (\text{old value of } y) + 3.$$ + +Also + +$$\langle \text{variables} \rangle = \langle \text{expressions} \rangle$$ + +for lists of variables and expressions, then the left-most variable assumes the value the left-most expression had before the assignment took place, the next left-most variable assumes the value the next left-most expression had before the assignment took place, and so on. + +For instance, + +$$x[0]..x[2] = 3, 4, 5$$ + +means + +$$\begin{aligned} &(\text{new value of } x[0]) \text{ becomes } 3, \\ &(\text{new value of } x[1]) \text{ becomes } 4, \\ &(\text{new value of } x[2]) \text{ becomes } 5. \end{aligned}$$ + +Whereas: + +$$x[0]..x[2] = y[2]..y[0]$$ + +means + +$$\begin{aligned} &(\text{new value of } x[0]) \text{ becomes } (\text{old value of } y[2]), \\ &(\text{new value of } x[1]) \text{ becomes } (\text{old value of } y[1]), \end{aligned}$$ + +(new value of $x[2]$ ) becomes (old value of $y[0]$ ). + +### 4.2.4 Void + +## 4.3 Void + +# 5 Inputs and outputs + +## 5.1 Tuak inputs and outputs + +The inputs to Tuak are given in tables 1 and 2, the outputs in tables 3 to 9 below. + +There are a few differences from the inputs and outputs to MILENAGE [2]. + +We allow the key K may be 128 bits or 256 bits. MAC-A and MAC-S may be 64, 128 or 256 bits. RES may be 32, 64, 128 or 256 bits. CK and IK may be 128 or 256 bits. Existing 3GPP specifications (see [1] and [12]) do not support all these possibilities, but they are included in Tuak for future flexibility in case future releases of these specifications may want to support them. + +NOTE 1: The 3G security architecture specification [1] calls the output of the $f1$ function 'MAC' while the present document and [2] call it 'MAC-A'. + +Any sizes for the parameters K, MAC-A, MAC-S, RES, CK and IK mentioned in the present document shall not be supported nor used in entities defined in 3GPP specifications until these specifications explicitly allow their use. + +In any particular implementation, the parameters shall have a fixed length, chosen in advance. For example an operator may fix K at length 256 bits, RES at length 64 bits, CK and IK at length 128 bits. As the lengths do not vary with input, they are not specified as formal input parameters. + +**Table 1: Inputs to $f1$ and $f1^*$** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------------------------------------------------------------------------------| +| K | 128 or 256 | Subscriber key K[0]...K[127] or K[0]...K[255] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | +| SQN | 48 | Sequence number SQN[0]...SQN[47] (for $f1^*$ this input is more precisely called SQN ms ) | +| AMF | 16 | Authentication management field AMF[0]...AMF[15] | + +**Table 2: Inputs to $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-----------------------------------------------| +| K | 128 or 256 | Subscriber key K[0]...K[127] or K[0]...K[255] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | + +**Table 3: $f1$ output** + +| Parameter | Size (bits) | Comment | +|-----------|----------------|----------------------------------------------------------------------------------------------------| +| MAC-A | 64, 128 or 256 | Network authentication code MAC-A[0]...MAC-A[63] or MAC-A[0]...MAC-A[127] or MAC-A[0]...MAC-A[255] | + +**Table 4: $f1^*$ output** + +| Parameter | Size (bits) | Comment | +|-----------|----------------|----------------------------------------------------------------------------------------------------| +| MAC-S | 64, 128 or 256 | Resynch authentication code MAC-S[0]...MAC-S[63] or MAC-S[0]...MAC-S[127] or MAC-S[0]...MAC-S[255] | + +**Table 5: f2 output** + +| Parameter | Size (bits) | Comment | +|-----------|-----------------------|-----------------------------------------------------------------------------------------| +| RES | 32, 64, 128
or 256 | Response RES[0]...RES[31] or RES[0]...RES[63] or RES[0]...RES[127] or RES[0]...RES[255] | + +**Table 6: f3 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------------| +| CK | 128 or 256 | Confidentiality key CK[0]...CK[127] or CK[0]...CK[255] | + +**Table 7: f4 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| IK | 128 or 256 | Integrity key IK[0]...IK[127] or IK[0]...IK[255] | + +**Table 8: f5 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------| +| AK | 48 | Anonymity key AK[0]...AK[47] | + +**Table 9: f5\* output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------| +| AK | 48 | Resynch anonymity key AK[0]...AK[47] | + +NOTE 2: Both f5 and f5\* outputs are called AK according to [1]. In practice only one of them at a time will be calculated in any given call to the authentication and key agreement algorithms. + +## 5.2 Keccak and its inputs and outputs + +This clause refers to the Keccak reference specification [3]. Use is made of the permutation Keccak-f[1600], which is abbreviated to $\Pi$ , and defined formally in Annex C. + +We use Strings **IN**[0] .. **IN**[1599] and **OUT**[0] .. **OUT**[1599] are used to represent the input and output of $\Pi$ . As in [3], these are treated as simple bit strings. However, to support efficient implementations of Keccak (see [4]), inputs are mapped to **IN** and outputs are extracted from **OUT** in such a way that bits of input and output should not need to be reversed within bytes for such implementations. + +The Keccak specification includes the concept of a security parameter which the designers call "capacity". Based on the designers' recommendations, a formal capacity of 512 bits is used: all input strings to the Keccak permutation shall be padded to 1088 bits, and then have 512 zero bits appended. The padding used to extend the input string to 1088 bits is the "1 0\* 1" padding defined in [3], immediately preceded by "1 1 1 1" for consistency with Sakura coding and domain separation (see e.g. "SAKURA: a flexible coding for tree hashing" [5], start of section 6 for the Sakura coding, and Table 4 for the domain separation coding). Note that our input strings before padding are always shorter than 832 bits, with the remaining bits of **IN** always the same in all modes, and output is only ever extracted from the first 832 bits of **OUT** – so in practice the effective capacity of the construction is at least 1600 - 832 = 768 bits. + +## 5.3 Other inputs and substrings + +MILENAGE uses a 128-bit value **OP**, and derives a 128-bit value **OPC**. **OP** is an Operator Variant Algorithm Configuration Field. + +For Tuak a 256-bit Operator Variant Algorithm Configuration Field is specified, **TOP**; and a derived 256-bit value **TOPC**. + +The following internal variables are defined in the algorithm definition: + +- A 56-bit string **ALGONAME[0] .. ALGONAME[55]**, with an arbitrary fixed value. This is specified as the ASCII representation of the string "TUAK1.0": to be explicit, **ALGONAME[0] .. ALGONAME[55] =** 0,1,0,1,0,1,0,0, 0,1,0,1,0,1,0,1, 0,1,0,0,0,0,0,1, 0,1,0,0,1,0,1,1, 0,0,1,1,0,0,0,1, 0,0,1,0,1,1,1,0, 0,0,1,1,0,0,0,0 +- An 8-bit string **INSTANCE[0] .. INSTANCE[7]** which will be given different values for different algorithms within the set. + +The internal variable **INSTANCE** is coded using the following schema (sections 6 gives the exact details) : + +**INSTANCE[0] .. INSTANCE[1]** indicate which function is being implemented + +**INSTANCE[2]...INSTANCE[4]** indicate the length of the MAC-A/MAC-S or RES output, +or they are all set to zero when deriving **TOPC** + +**INSTANCE[5] .. INSTANCE[7]** indicate whether the CK/IK/K lengths are 256 bit. + +# 6 Definition of the example algorithms + +## 6.1 Derivation of TOPC + +The **INSTANCE** variable is constructed as follows: + +**INSTANCE[0] .. INSTANCE[6] =** 0,0,0,0,0,0,0 + +**INSTANCE[7] =** 0 if the length of K is 128 bits += 1 if the length of K is 256 bits + +The 1600-bit value **IN** is then constructed as follows: + +**IN[0] .. IN[255] = TOP[255] .. TOP[0]** + +**IN[256] .. IN[263] = INSTANCE[7] .. INSTANCE[0]** + +**IN[264] .. IN[319] = ALGONAME[55] .. ALGONAME[0]** + +**IN[i] = 0** for $320 \leq i \leq 511$ + +**IN[512] .. IN[767] = K[255] .. K[0]** if the length of K is 256 bits + +**IN[512] .. IN[639] = K[127] .. K[0]** if the length of K is 128 bits + +**IN[i] = 0** for $640 \leq i \leq 767$ if the length of K is 128 bits + +**IN[i] = 1** for $768 \leq i \leq 772$ + +**IN[i] = 0** for $773 \leq i \leq 1086$ + +**IN[1087] = 1** + +**IN[i] = 0** for $1088 \leq i \leq 1599$ + +Then apply the permutation: + +**OUT = $\Pi$ (IN)** + +And extract **TOPC** as follows: + +**TOPC[0] .. TOPC[255] = OUT[255] .. OUT[0]** + +## 6.2 Specification of the function f1 + +The internal **INSTANCE** variable is constructed as follows: + +**INSTANCE[0] .. INSTANCE[1] =** 0,0 + +**INSTANCE[2] .. INSTANCE[4] =** 0,0,1 if the MAC-A length is 64 bits + += 0,1,0 if the MAC-A length is 128 bits + += 1,0,0 if the MAC-A length is 256 bits + +INSTANCE[5] .. INSTANCE[6] = 0,0 + +INSTANCE[7] = 0 if the length of K is 128 bits + += 1 if the length of K is 256 bits + +The 1600-bit value **IN** is then constructed as follows: + +**IN**[0] .. **IN**[255] = **TOPc**[255] .. **TOPc**[0] + +**IN**[256] .. **IN**[263] = **INSTANCE**[7] .. **INSTANCE**[0] + +**IN**[264] .. **IN**[319] = **ALGONAME**[55] .. **ALGONAME**[0] + +**IN**[320] .. **IN**[447] = **RAND**[127] .. **RAND**[0] + +**IN**[448] .. **IN**[463] = **AMF**[15] .. **AMF**[0] + +**IN**[464] .. **IN**[511] = **SQN**[47] .. **SQN**[0] + +**IN**[512] .. **IN**[767] = **K**[255] .. **K**[0]   if the length of K is 256 bits + +**IN**[512] .. **IN**[639] = **K**[127] .. **K**[0]   if the length of K is 128 bits + +**IN**[i] = 0 for 640 ≤ i ≤ 767               if the length of K is 128 bits + +**IN**[i] = 1 for 768 ≤ i ≤ 772 + +**IN**[i] = 0 for 773 ≤ i ≤ 1086 + +**IN**[1087] = 1 + +**IN**[i] = 0 for 1088 ≤ i ≤ 1599 + +Then apply the permutation: + +**OUT** = Π(**IN**) + +And extract function output as follows. + +Output of *f1* = **MAC-A**, where + +**MAC-A**[0] .. **MAC-A**[63] = **OUT**[63] .. **OUT**[0]   if the MAC-A length is 64 bits + +**MAC-A**[0] .. **MAC-A**[127] = **OUT**[127] .. **OUT**[0]   if the MAC-A length is 128 bits + +[0] .. **MAC-A**[255] = **OUT**[255] .. **OUT**[0]   if the MAC-A length is 256 bits + +## 6.3. Specification of the function f1\* + +The internal **INSTANCE** variable is constructed as follows. The construction is very similar to *f1*, except that **INSTANCE**[0] is 1 rather than 0: + +**INSTANCE**[0] .. **INSTANCE**[1] = 1,0 + +**INSTANCE**[2] .. **INSTANCE**[4] = 0,0,1 if the MAC-S length is 64 bits + += 0,1,0 if the MAC-S length is 128 bits + += 1,0,0 if the MAC-S length is 256 bits + +**INSTANCE**[5] .. **INSTANCE**[6] = 0,0 + +**INSTANCE**[7] = 0 if the length of K is 128 bits + += 1 if the length of K is 256 bits + +The 1600-bit value **IN** is then constructed in exactly the same way as for *f1* (but note **IN**[263] will be 1 rather than 0). + +Then the permutation: + +**OUT** = $\Pi$ (**IN**) + +is applied and the function output is extracted as follows. + +Output of *f1\** = **MAC-S**, where + +**MAC-S**[0] .. **MAC-S**[63] = **OUT**[63] .. **OUT**[0] if the MAC-S length is 64 bits + +**MAC-S**[0] .. **MAC-S**[127] = **OUT**[127] .. **OUT**[0] if the MAC-S length is 128 bits + +**MAC-S**[0] .. **MAC-S**[255] = **OUT**[255] .. **OUT**[0] if the MAC-S length is 256 bits + +## 6.4 Specification of the functions f2, f3, f4 and f5 + +The internal **INSTANCE** variable is constructed as follows: + +**INSTANCE**[0] .. **INSTANCE**[1] = 0,1 + +**INSTANCE**[2] .. **INSTANCE**[4] = 0,0,0 if the length of RES is 32 bits + += 0,0,1 if the length of RES is 64 bits + += 0,1,0 if the length of RES is 128 bits + += 1,0,0 if the length of RES is 256 bits + +**INSTANCE**[5] = 0 if the length of CK is 128 bits + += 1 if the length of CK is 256 bits + +**INSTANCE**[6] = 0 if the length of IK is 128 bits + += 1 if the length of IK is 256 bits + +**INSTANCE**[7] = 0 if the length of K is 128 bits + += 1 if the length of K is 256 bits + +The 1600-bit value **IN** is then constructed as follows: + +$$\begin{aligned} \text{IN}[0] \dots \text{IN}[255] &= \text{TOP}_c[255] \dots \text{TOP}_c[0] \\ \text{IN}[256] \dots \text{IN}[263] &= \text{INSTANCE}[7] \dots \text{INSTANCE}[0] \\ \text{IN}[264] \dots \text{IN}[319] &= \text{ALGONAME}[55] \dots \text{ALGONAME}[0] \\ \text{IN}[320] \dots \text{IN}[447] &= \text{RAND}[127] \dots \text{RAND}[0] \\ \text{IN}[i] &= 0 \text{ for } 448 \leq i \leq 511 \\ \text{IN}[512] \dots \text{IN}[767] &= \text{K}[255] \dots \text{K}[0] \quad \text{if the length of K is 256 bits} \\ \text{IN}[512] \dots \text{IN}[639] &= \text{K}[127] \dots \text{K}[0] \quad \text{if the length of K is 128 bits} \\ \text{IN}[i] &= 0 \text{ for } 640 \leq i \leq 767 \quad \text{if the length of K is 128 bits} \\ \text{IN}[i] &= 1 \text{ for } 768 \leq i \leq 772 \\ \text{IN}[i] &= 0 \text{ for } 773 \leq i \leq 1086 \\ \text{IN}[1087] &= 1 \\ \text{IN}[i] &= 0 \text{ for } 1088 \leq i \leq 1599 \end{aligned}$$ + +Then the permutation: + +$$\text{OUT} = \Pi(\text{IN})$$ + +is applied and the function outputs are extracted as follows: + +Output of $f2 = \text{RES}$ , where: + +$$\begin{aligned} \text{RES}[0] \dots \text{RES}[31] &= \text{OUT}[31] \dots \text{OUT}[0] \quad \text{if the RES length is 32 bits} \\ \text{RES}[0] \dots \text{RES}[63] &= \text{OUT}[63] \dots \text{OUT}[0] \quad \text{if the RES length is 64 bits} \\ \text{RES}[0] \dots \text{RES}[127] &= \text{OUT}[127] \dots \text{OUT}[0] \quad \text{if the RES length is 128 bits} \\ \text{RES}[0] \dots \text{RES}[255] &= \text{OUT}[255] \dots \text{OUT}[0] \quad \text{if the RES length is 256 bits} \end{aligned}$$ + +Output of $f3 = \text{CK}$ , where: + +$$\begin{aligned} \text{CK}[0] \dots \text{CK}[127] &= \text{OUT}[383] \dots \text{OUT}[256] \quad \text{if the CK length is 128 bits} \\ \text{CK}[0] \dots \text{CK}[255] &= \text{OUT}[511] \dots \text{OUT}[256] \quad \text{if the CK length is 256 bits} \end{aligned}$$ + +Output of $f4 = \text{IK}$ , where: + +$$\begin{aligned} \text{IK}[0] \dots \text{IK}[127] &= \text{OUT}[639] \dots \text{OUT}[512] \quad \text{if the IK length is 128 bits} \\ \text{IK}[0] \dots \text{IK}[255] &= \text{OUT}[767] \dots \text{OUT}[512] \quad \text{if the IK length is 256 bits} \end{aligned}$$ + +Output of $f5 = \text{AK}$ , where: + +$$\text{AK}[0] \dots \text{AK}[47] = \text{OUT}[815] \dots \text{OUT}[768]$$ + +## 6.5 Specification of the function f5\* + +The internal **INSTANCE** variable is constructed as follows: + +$$\begin{aligned} \text{INSTANCE}[0] .. \text{INSTANCE}[1] &= 1,1 \\ \text{INSTANCE}[2] .. \text{INSTANCE}[4] &= 0,0,0 \\ \text{INSTANCE}[5] .. \text{INSTANCE}[6] &= 0,0 \\ \text{INSTANCE}[7] &= 0 \text{ if the length of K is 128 bits} \\ &= 1 \text{ if the length of K is 256 bits} \end{aligned}$$ + +The 1600-bit value **IN** is then constructed in exactly the same way as for **f2**, **f3**, **f4**, and **f5** (but note that **IN**[263] will be 1 rather than 0, and that **IN**[257], **IN**[258], **IN**[259], **IN**[260], **IN**[261] will all be 0). + +Then the permutation: + +$$\text{OUT} = \Pi(\text{IN})$$ + +is applied and the function output is extracted as follows: + +Output of **f5\*** = **AK**, where: + +$$\text{AK}[0] .. \text{AK}[47] = \text{OUT}[815] .. \text{OUT}[768]$$ + +# 7 Implementation considerations + +## 7.1 TOPC computed on or off the UICC? + +It will be seen in clause 6.1 that **TOPC** is computed from **OP** and **K**, and that it is only **TOPC**, not **TOP**, that is ever used in subsequent computations. + +As for **OPC** in MILENAGE, it is recommended that **TOPC** be computed off the UICC where possible, and that **TOPC** rather than **TOP** be loaded to the UICC for use in subsequent computations. This should also apply when updating an embedded UICC (eUICC) : the value of **TOPC** (and not **TOP**) should be loaded to the eUICC in conjunction with the new **K** and other operator customization parameters. + +This gives the following benefits: + +- The complexity of the algorithms run on the UICC is reduced. +- It is more likely that **TOP** can be kept secret. (If **TOP** is stored on the UICC, it only takes one UICC to be reverse engineered for **TOP** to be discovered and published. But it should be difficult for someone who has discovered even a large number of (**TOPC**, **K**) pairs to deduce **TOP**. That means that the **TOPC** associated with any other value of **K** will be unknown, which may make it harder to mount some kinds of cryptanalytic and forgery attacks. The algorithms are designed to be secure whether or not **TOP** is known to the attacker, but a secret **TOP** is one more hurdle in the attacker's path.) + +## 7.2 Further customization + +**TOP** obviously allows for some degree of operator customization. + +Further, as described in clause 5.1, the lengths of **K**, and of **MAC-A/MAC-S**, **RES**, **CK** and **IK** can be chosen by the operator, although they have to be fixed in each particular implementation of Tuak. In a flexible implementation (e.g. UICC), these operator-chosen parameter lengths could be loaded to the UICC in conjunction with the associated **K** and **TOPC**. + +Where compatibility is required with existing 3GPP specifications, the operator shall set the length of the **K** to 128 bits, the length of the **RES** to between 32 and 128 bits, the length of the **MAC-A/MAC-S** to 64 bits, the length of **CK** to 128 bits, and the length of **IK** to 128 bits. + +If an even more secure version of this algorithm is required, this could be done by adding extra applications of the Keccak permutation before extracting output. These would be used in the derivation of **TOPC** (clause 6.1), and each of the algorithms *f1*, *f1\**, *f2-f5*, *f5\** (clauses 6.2 to 6.5). In each case, instead of: + +Construct **IN** + +**OUT** = $\Pi(\text{IN})$ + +Extract outputs + +the approach could be + +Construct **IN** + +**OUT** = $\Pi(\Pi(\text{IN}))$ + +Extract outputs + +or + +Construct **IN** + +**OUT** = $\Pi(\Pi(\Pi(\text{IN})))$ + +Extract outputs + +or however many extra applications of the permutation are required. Again, in a flexible implementation (e.g. UICC), the number of iterations of $\Pi$ may be loaded to the UICC as an operator-chosen parameter. + +## 7.3 Resistance to side channel attacks + +When these algorithms are implemented on a UICC, consideration should be given to protecting them against side channel attacks such as differential power analysis (DPA). [4, 6, 7, 8, 9, 10, 11] may be useful references. + +# Annex A (normative): Tuak diagrams + +![Figure A.1: Tuak operation. Three diagrams showing the derivation of TOPc, MAC, and RES/CK/IK/AK using the Keccak permutation.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +The figure consists of three diagrams illustrating the Tuak operation using the Keccak permutation. Each diagram shows a horizontal bar representing the Keccak state, divided into a white 'rate' portion and a grey 'capacity' portion. Inputs are shown as arrows pointing into the rate portion, and outputs are shown as arrows pointing out from the rate portion. + +- Top Diagram:** Inputs include INSTANCE, TOP, ALGONAME, ZEROES, K, and PADDING. The output is $TOP_c$ . +- Middle Diagram:** Inputs include INSTANCE, TOPc, ALGONAME, RAND, AMF, SQN, K, PADDING, and 512 ZEROES. The output is MAC. +- Bottom Diagram:** Inputs include INSTANCE, TOPc, ALGONAME, RAND, ZEROES, K, PADDING, and 512 ZEROES. The outputs are RES, CK, IK, and AK. + +Figure A.1: Tuak operation. Three diagrams showing the derivation of TOPc, MAC, and RES/CK/IK/AK using the Keccak permutation. + +**Figure A.1** Tuak operation + +The first diagram illustrates the derivation of $TOP_c$ . + +The second diagram illustrates the derivation of either **MAC-A** (using the $f1$ function) or **MAC-S** (using the $f1^*$ function), with different values of the **INSTANCE** byte in each case. + +The third diagram illustrates the derivation of **RES** (using the $f2$ function), **CK** (using $f3$ ), **IK** (using $f4$ ) and **AK** (using $f5$ ) or alternatively the derivation of **AK** using $f5^*$ (in which case the other three outputs should be ignored). + +In all cases it is assumed that just one iteration of the Keccak permutation is used (see clause 7.2). + +Note the 512-bit "capacity" of Keccak: only zeroes are input to the rightmost 512 bits, and no outputs are extracted from the rightmost 512 bits. + +# Annex B (informative): TuakApplication Programme Interface ( AP) in ANSI CI + +``` + +/* ----- + Constants and Typedefs + ----- +*/ +typedef unsigned char uint8; +static const uint8 ALGONAME[] = "TUAK1.0"; + +uint8 TOP[32]; /* Operator's Configuration */ +uint8 KEY_sz; /* = 16/32 bytes */ +uint8 RES_sz; /* = 4/8/16/32 bytes */ +uint8 CK_sz; /* = 16/32 bytes */ +uint8 IK_sz; /* = 16/32 bytes */ +uint8 MAC_sz; /* = 8/16/32 bytes */ +uint8 KeccakIterations; /* >=1, number of iterations */ + +/* ----- + TUAK API Declaration + ----- +*/ +void TUAK_ComputeTOPC( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *TOPC /* out, uint8[32] */ + ); + +void TUAK_f1 ( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *rand, /* in, uint8[16] */ + uint8 *sqn, /* in, uint8[6] */ + uint8 *amf, /* in, uint8[2] */ + uint8 *mac /* out, uint8[MAC_sz] */ + ); + +void TUAK_f2345 ( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *rand, /* in, uint8[16] */ + uint8 *res, /* out, uint8[RES_sz] */ + uint8 *ck, /* out, uint8[CK_sz] */ + uint8 *ik, /* out, uint8[IK_sz] */ + uint8 *ak /* out, uint8[6] */ + ); + +void TUAK_f1s ( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *rand, /* in, uint8[16] */ + uint8 *sqn, /* in, uint8[6] */ + uint8 *amf, /* in, uint8[2] */ + uint8 *mac /* out, uint8[MAC_sz] */ + ); + +void TUAK_f5s ( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *rand, /* in, uint8[16] */ + uint8 *ak /* out, uint8[6] */ + ); + +``` + +# Annex C (normative): Specification of the Keccak permutation used within Tuak + +The following specification of the permutation $\Pi$ is extracted from the Keccak reference specification [3], section 1.2. + +The permutation $\Pi$ is described as a sequence of operations on a state $a$ that is a three-dimensional $5 \times 5 \times 64$ array of elements of $\text{GF}(2)$ . The expression $a[x][y][z]$ with $x, y \in \mathbb{Z}_5$ and $z \in \mathbb{Z}_{64}$ , denotes the bit in position $(x, y, z)$ , with the indices starting from zero. The array $a$ is mapped to the bits of an input and output string $s$ by $s[64.(5y + x) + z] = a[x][y][z]$ , so that $s$ is a 1600-bit string, indexed from bit 0 up to bit 1599. Note that expressions in the $x$ and $y$ coordinates should be taken modulo 5 and expressions in the $z$ coordinate modulo 64. It is possible to omit the $[z]$ index, both the $[y][z]$ indices, or all three indices, implying that the statement is valid for all values of the omitted indices. + +$\Pi$ is an iterated permutation, consisting of a sequence of 24 rounds $R$ , indexed by $i_r$ from 0 to 23. Each round consists of five steps, $R = \iota \circ \chi \circ \pi \circ \rho \circ \theta$ , performed in the following order: + +$$\theta : a[x][y][z] \leftarrow a[x][y][z] + \sum_{y'=0}^4 a[x-1][y'][z] + \sum_{y'=0}^4 a[x+1][y'][z-1],$$ + +$$\rho : a[x][y][z] \leftarrow a[x][y][z - (t+1)(t+2)/2],$$ + +with $t$ satisfying $0 \leq t < 24$ and + +$$\begin{matrix} 0 & 1 & t & 1 \\ 2 & 3 & & \end{matrix} \begin{pmatrix} & x \\ y & \end{pmatrix} \begin{pmatrix} & x \\ y & \end{pmatrix} = \begin{pmatrix} & x' \\ y' & \end{pmatrix} \text{ in } \text{GF}(5)_{2 \times 2}$$ + +or $t = -1$ if $x = y = 0$ , + +so that $t$ is given by the following table: + +| | | | | | | +|-----|----|----|----|----|----| +| x= | 0 | 1 | 2 | 3 | 4 | +| y=0 | -1 | 0 | 18 | 6 | 12 | +| y=1 | 7 | 23 | 2 | 9 | 22 | +| y=2 | 1 | 3 | 17 | 16 | 20 | +| y=3 | 13 | 8 | 4 | 5 | 15 | +| y=4 | 19 | 10 | 21 | 14 | 11 | + +and $(t+1)(t+2)/2 \in \mathbb{Z}_{64}$ is given by: + +| | | | | | | +|-----|----|----|----|----|----| +| x= | 0 | 1 | 2 | 3 | 4 | +| y=0 | 0 | 1 | 62 | 28 | 27 | +| y=1 | 36 | 44 | 6 | 55 | 20 | +| y=2 | 3 | 10 | 43 | 25 | 39 | +| y=3 | 41 | 45 | 15 | 21 | 8 | +| y=4 | 18 | 2 | 61 | 56 | 14 | + +$$\pi : a[x][y] \leftarrow a[x'][y'], \text{ with}$$ + +$$\begin{matrix} x & 0 & 1 & x' \\ y & 2 & 3 & y' \end{matrix},$$ + +$$\chi : a[x] \leftarrow a[x] + (a[x+1] + 1)a[x+2],$$ + +$$\iota : a \leftarrow a + \text{RC}[i_r].$$ + +$\text{GF}(2)$ . With the exception of the value of the round constants $\text{RC}[i_r]$ , these rounds are identical. + +The round constants are given by (with the first index denoting the round number): + +$$\begin{aligned} \text{RC}[i_r][0][0][2^j - 1] &= \text{rc}[j + 7i_r] \text{ for all } 0 \leq j \leq 6, \\ \text{RC}[i_r][x][y][z] &= 0 \text{ for all other values of } x, y, z \end{aligned}$$ + +The values $\text{rc}[t] \in \text{GF}(2)$ are defined as the output of a binary linear feedback shift register (LFSR): + +$$\text{rc}[t] = (x^t \bmod x^8 + x^6 + x^5 + x^4 + 1) \bmod x \text{ in } \text{GF}(2)[x],$$ + +so that $\text{rc}[j + 7i_r]$ is given by the following table: + +| | | | | | | | | +|-------------------|---|---|---|---|---|---|---| +| j= | 0 | 1 | 2 | 3 | 4 | 5 | 6 | +| i r =0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | + +| | | | | | | | | +|--------------------|---|---|---|---|---|---|---| +| j= | 0 | 1 | 2 | 3 | 4 | 5 | 6 | +| i r =12 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | + +Error! No + +----- + +| | | | | | | | | +|----------|---|---|---|---|---|---|---| +| $i_r=1$ | 0 | 1 | 0 | 1 | 1 | 0 | 0 | +| $i_r=2$ | 0 | 1 | 1 | 1 | 1 | 0 | 1 | +| $i_r=3$ | 0 | 0 | 0 | 0 | 1 | 1 | 1 | +| $i_r=4$ | 1 | 1 | 1 | 1 | 1 | 0 | 0 | +| $i_r=5$ | 1 | 0 | 0 | 0 | 0 | 1 | 0 | +| $i_r=6$ | 1 | 0 | 0 | 1 | 1 | 1 | 1 | +| $i_r=7$ | 1 | 0 | 1 | 0 | 1 | 0 | 1 | +| $i_r=8$ | 0 | 1 | 1 | 1 | 0 | 0 | 0 | +| $i_r=9$ | 0 | 0 | 1 | 1 | 0 | 0 | 0 | +| $i_r=10$ | 1 | 0 | 1 | 0 | 1 | 1 | 0 | +| $i_r=11$ | 0 | 1 | 1 | 0 | 0 | 1 | 0 | + +19 + +Error! No text of specified style in + +----- + +| | | | | | | | | +|----------|---|---|---|---|---|---|---| +| $i_r=13$ | 1 | 1 | 1 | 1 | 0 | 0 | 1 | +| $i_r=14$ | 1 | 0 | 1 | 1 | 1 | 0 | 1 | +| $i_r=15$ | 1 | 1 | 0 | 0 | 1 | 0 | 1 | +| $i_r=16$ | 0 | 1 | 0 | 0 | 1 | 0 | 1 | +| $i_r=17$ | 0 | 0 | 0 | 1 | 0 | 0 | 1 | +| $i_r=18$ | 0 | 1 | 1 | 0 | 1 | 0 | 0 | +| $i_r=19$ | 0 | 1 | 1 | 0 | 0 | 1 | 1 | +| $i_r=20$ | 1 | 0 | 0 | 1 | 1 | 1 | 1 | +| $i_r=21$ | 0 | 0 | 0 | 1 | 1 | 0 | 1 | +| $i_r=22$ | 1 | 0 | 0 | 0 | 0 | 1 | 0 | +| $i_r=23$ | 0 | 0 | 1 | 0 | 1 | 1 | 1 | + +# Annex D (informative): Example source code for Tuak (ANSI C) + +Tuak is built on top of the Keccak function, as described in annex C. In the following example code, a Tuak configuration is defined as a set of global variables, so that these can be initialized or modified at run-time, and there is no need to fix them in the code as static constants. The read/write data to the Keccak state, including the padding, will depend on the Keccak state representation. Included in this example are 8-bit, 32-bit and 64-bit implementations of the Keccak function, each having a different representation of the state. + +The Tuak f-functions do similar calculations in their core, therefore, it was possible to combine most of the computations in one function called TUAK\_Main(). Lengths are given in bytes, rather than bits, in order to support 8-bit environments (e.g., length=256 does not fit in type uint8). All the example codes are endianness-free, i.e. can be used on both big and little endian machines. + +``` + +/* This code may be freely used or adapted. + +This implementation of TUAK is endianness-free. +It supports 64-bit, 32-bit and 8-bit environments. +*/ + +/* ----- + Constants, typedefs, macros, compilation settings + ----- +*/ + +/* This macro selects Keccak_f implementation instance - 8/32/64-bit version */ +#define KECCAK_VERSION_BITS 32 + +/* Depending on the version of Keccak we do: + * - map KECCAK_F macro to relevant Keccak_f (8/32/64-bit) instance + * - declare Keccak's state INOUT[] as global, for simplicity + * - define method for TUAK padding TUAK_ADD_PADDING() + */ +#ifdef KECCAK_VERSION_BITS==64 + static uint64_t INOUT[25]; /* state to Keccak_f for 64-bit version */ + extern void Keccak_f_64(uint64_t *s); + #define KECCAK_F Keccak_f_64 + #define TUAK_ADD_PADDING() INOUT[12] = 0x1FULL, INOUT[16] = (0x01ULL<<63) +#elif KECCAK_VERSION_BITS==32 + static uint32_t INOUT[50]; /* state to Keccak_f for 32-bit version */ + extern void Keccak_f_32(uint32_t *s); + #define KECCAK_F Keccak_f_32 + #define TUAK_ADD_PADDING() INOUT[24] = 0x1FUL, INOUT[33] = 0x80000000 +#elif KECCAK_VERSION_BITS==8 + static uint8_t INOUT[200]; /* state to Keccak_f for 8-bit version */ + extern void Keccak_f_8(uint8_t s[200]); + #define KECCAK_F Keccak_f_8 + #define TUAK_ADD_PADDING() INOUT[96] = 0x1F, INOUT[135] = 0x80 +#else + #error The requested version of Keccak_f is not implemented! +#endif + +static const uint8_t ALGONAME[] = "TUAK1.0"; + +void TUAK_ComputeTOPC(uint8*, uint8*); + +/* ----- + TUAK Instance Configuration + if dynamic => can be set/modified on run-time + if constants => fixed instance of the algorithm + ----- +*/ + +uint8_t TOP[32]; /* Operator's Configuration */ +uint8_t KEY_sz = 16; /* = 16/32 bytes */ +uint8_t RES_sz = 8; /* = 4/8/16/32 bytes */ +uint8_t CK_sz = 32; /* = 16/32 bytes */ +uint8_t IK_sz = 32; /* = 16/32 bytes */ +uint8_t MAC_sz = 16; /* = 8/16/32 bytes */ +uint8_t KeccakIterations = 1; /* >=1, number of Keccak_f iterations */ + +/* ----- + PUSH_DATA / PULL_DATA, TUAK_Main() + ----- +*/ + +``` + +``` + +*/ +void PUSH_DATA(const uint8 * data, uint8 n, uint8 location) +{ + while(n--) + #if KECCAK_VERSION_BITS==64 + INOUT[location>>3] |= ((uint64)data[n]) << ((location++ & 7)<<3); + #elif KECCAK_VERSION_BITS==32 + INOUT[location>>2] |= ((uint32)data[n]) << ((location++ & 3)<<3); + #elif KECCAK_VERSION_BITS==8 + INOUT[location++] = data[n]; /* Note: reversed order of bytes */ + #endif +} + +void PULL_DATA(uint8 * data, uint8 n, uint8 location) +{ + while(n--) + #if KECCAK_VERSION_BITS==64 + data[n] = (uint8)(INOUT[location>>3] >> ((location++ & 7)<<3)); + #elif KECCAK_VERSION_BITS==32 + data[n] = (uint8)(INOUT[location>>2] >> ((location++ & 3)<<3)); + #elif KECCAK_VERSION_BITS==8 + data[n] = INOUT[location++]; /* Note: reversed order of bytes */ + #endif +} + +/* Universal function used by TUAK API functions */ +void TUAK_Main ( uint8 instance, /* in, uint8 */ + uint8 *rand, /* in, uint8[16] */ + uint8 *amf, /* in, uint8[2] */ + uint8 *sqn, /* in, uint8[6] */ + uint8 *key /* in, uint8[16/32] */ + ) +{ + uint8 i, TOPC[32]; + TUAK_ComputeTOPC(key, TOPC); /* compute TOPC */ + memset((uint8*)INOUT, 0, 200); /* clean INOUT */ + + PUSH_DATA(TOPC, 32, 0); /* TOPC */ + PUSH_DATA(&instance, 1, 32); /* INSTANCE */ + PUSH_DATA(ALGONAME, 7, 33); /* ALGONAME */ + PUSH_DATA(rand, 16, 40); /* RAND */ + if(amf) PUSH_DATA(amf, 2, 56); /* AMF, if !=NULL */ + if(sqn) PUSH_DATA(sqn, 6, 58); /* SQN, if !=NULL */ + PUSH_DATA(key, (instance & 1)?32:16, 64); /* KEY-128/256 bits */ + + TUAK_ADD_PADDING(); /* Padding bits 768-1087 */ + + for(i=0; i>5; + memset(INOUT, 0, 200); + PUSH_DATA(TOP, 32, 0); /* TOP */ + PUSH_DATA(&inst, 1, 32); /* INSTANCE for TOPC */ + PUSH_DATA(ALGONAME, 7, 33); /* ALGONAME */ + PUSH_DATA(key, KEY_sz, 64); /* KEY-128/256 */ + TUAK_ADD_PADDING(); /* Padding bits 768-1087 */ + + for(i=0; i>5) | MAC_sz, rand, amf, sqn, key); + PULL_DATA(mac, MAC_sz, 0); +} + +``` + +``` + +void TUAK_f2345 ( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *rand, /* in, uint8[16] */ + uint8 *res, /* out, uint8[RES_sz] */ + uint8 *ck, /* out, uint8[CK_sz] */ + uint8 *ik, /* out, uint8[IK_sz] */ + uint8 *ak /* out, uint8[6] */ + ) +{ + TUAK_Main( (KEY_sz>>5) | ((IK_sz>>4)&0x02) | ((CK_sz>>3)&0x04) + | (RES_sz&0x38) | 0x40, rand, 0, 0, key); + PULL_DATA(res, RES_sz, 0 ); + PULL_DATA(ck , CK_sz , 32); + PULL_DATA(ik , IK_sz , 64); + PULL_DATA(ak , 6 , 96); +} + +void TUAK_f1s ( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *rand, /* in, uint8[16] */ + uint8 *sqn, /* in, uint8[6] */ + uint8 *amf, /* in, uint8[2] */ + uint8 *mac /* out, uint8[MAC_sz] */ + ) +{ + TUAK_Main( (KEY_sz>>5) | MAC_sz | 0x80, rand, amf, sqn, key); + PULL_DATA(mac, MAC_sz, 0); +} + +void TUAK_f5s ( uint8 *key, /* in, uint8[KEY_sz] */ + uint8 *rand, /* in, uint8[16] */ + uint8 *ak /* out, uint8[6] */ + ) +{ + TUAK_Main( (KEY_sz>>5) | 0xc0, rand, 0, 0, key); + PULL_DATA(ak, 6, 96); +} + +``` + +# Annex E (informative): Example source code for Keccak (ANSI C) + +## Comments to the example code for a 64-bit implementation of Keccak + +This 64-bit implementation of the Keccak permutation follows the specification in annex C. It has 24 rounds of 5 basic steps in the order Theta, Rho, Pi, Chi, Iota. The state of Keccak is 1600 bits, represented as 25 blocks of 64 bits each (`uint64 s[25]`). Such a block is referred to as a "lane" in the Keccak reference specification [3]. + +In the example code, bit $n=0..1599$ of Keccak state is mapped to the state representation array as: + +$\text{bit}(n) = (s[n/64] \gg (n\%64)) \& 1$ . The mapping between $s[w]$ and $a[x][y][z]$ is: $a[x][y][z] = (s[5y+x] \gg z) \& 1$ , for any triple $x, y=0..4, z=0..63$ (and $w=5y+x$ ). + +An efficient way to implement Keccak is to code it as an update function. For the purpose of efficiency, there are three pre-computed constant tables `Rho[25]`, `Pi[25]`, `Iota[24]` (74 bytes in total). Run-time requires $43 + \text{sizeof}(\text{uint64}^*)$ bytes of stack, excluding possible alignment of input arguments. + +In the Theta function, it is necessary to perform the following computation: + +$$\theta : a[x][y][z] \leftarrow a[x][y][z] + \sum_{y'=0}^4 a[x-1][y'][z] + \sum_{y'=0}^4 a[x+1][y'][z-1].$$ + +To do this, first compute 5 sums $\sum_{y'=0}^4 a[x][y'][z]$ for each $x=0..4$ (and all $z=0..63$ ) and store them in five temporary 64-bit variables (`uint64 t[5]`). Such an operation as $a[x][y][z] \leftarrow a[x][y][z-1]$ is just a rotation of the corresponding 64-bit value of $s$ by 1 to the left, and $a[x][y][z] \leftarrow a[x][y][z]$ is a corresponding assignment $s[w] \leftarrow s[w]$ . This way, in the second loop of Theta, run over $y=0..4$ and update 25 words of $s$ based on pre-computed temporary sums. + +The Rho function is just a circular rotation of bits for each of 64-bit words individually of the state `s[25]`. The number of bits a word $s[n]$ is to be rotated by is `Rho[n]`. + +The Pi function is a full-cycle permutation of 24 words of $s$ , excluding $s[0]$ . To avoid duplicating the state for this operation, remember the first word in the permutation chain `s[1]` somewhere in a temporary variable `T`, then perform + +$s[1] \leftarrow s[\text{Pi}[1]]$ , where the value $\text{Pi}[1]$ is the index of the word that has to go to $s[1]$ . In the next step, assign $s[\text{Pi}[1]] \leftarrow s[\text{Pi}[\text{Pi}[1]]]$ , and so on. After 23 such steps the permutation is almost complete, except that the saved value should be located to the last referenced place $s[\text{Pi}^{23}[1]] \leftarrow T$ . + +In the Chi function, reuse 5 temporary 64-bit words to compute somewhat mixed Boolean expressions; the function is straightforward to implement. + +The Iota function updates 7 bits indexed by 0, 1, 3, 7, 15, 31, 63, of only one word $s[0]$ , by XORing them with some constant values that depend on the current round index ( $r=0..23$ ). Each cell of the pre-computed constant table $\text{Iota}[24]$ encodes those 7 bits in one byte (`uint8`) in the following way. + +Bits related to indices 0, 1, 3, 7 stay in their correct place of the byte $\text{Iota}[r]$ . Bits related to indices 15, 31, 63 are mapped to bits 4, 5, 6 of the byte $\text{Iota}[r]$ , correspondingly. When XORing, the lower bits 0-7 appear well mapped ( $\text{Iota}[\text{round}] \& 0x8B$ ), and the upper bits 31-63 are received by the relevant three shifts of that byte to the left to certain positions (note, the byte $\text{Iota}[r]$ is first converted to `uint64`). It is also possible to OR all the shifts first, and then to mask those 7 bits before XORing the result to $s[0]$ . This trick is possible since ORing does not overlap those 7 bits, but the result of ORing will, however, interfere some of the other 57 bits, and by the final masking with the constant `0x800000008000808BULL`, remove that unwanted influence. + +## Comments to the example code for an 8-bit implementation of Keccak + +The 8-bit implementation of Keccak is basically a step-by-step refactored version of the 64-bit version. The state of Keccak is now represented as 200 bytes of 8 bits each (`uint8 s[200]`). Each block of 8 bytes is a mapping of a relevant 64-bit word in the 64-bit version. The Keccak state is mapped to the state representation array as: `bit(n) = (s[n/8]>>(n%8))&1`, for `n=0..1599`. + +A 64-bit word (that is now represented as 8 bytes) can be rotated by 1-7 bits easily –just save the first byte of the 8-byte block, then shift and propagate 1-7 bits from one byte to the next, and, finally, complete the operation at the end by using the saved byte. + +However, in the Rho function, the rotation parameter - *r* bits - can be any value in the range 1..63. Then perform the following technique. Split *r* as *r=8\*A+B*, where *A* is the number of full bytes of a 64-bit word to be rotated, and *B* is the remaining number of bits of the rotation value *r*. In the first loop, rotate an 8-byte block of *s* by *A* bytes, and store the result in some other temporary 8-byte block (in `t[0..7]`). In the second step, copy that temporary block `t[0..7]` back to the relevant location of the state *s*, and, in parallel, perform the rotation of the block by *B* bits in the way mentioned earlier. + +## Comments to the example code for a 32-bit implementation of Keccak + +The 32-bit implementation of Keccak is yet another step-by-step refactoring of the 64-bit version. The state of Keccak is represented as `uint32[50]`, where each two 32-bit consecutive words are mapped to one 64-bit word. i.e., `state64[k] = (state32[2*k+1]<<32) | state32[2*k]`, for `k=0..24`. + +In the Rho function, every such pair of 32-bit words (*A*; *B*), where *A=state32[2\*k]* and *B=state32[2\*k+1]*, for some `k=0..24`, needs to be rotated by `n=0..63` bits. The resulting pair will be *(A'; B') = (A<>(32-n); B<>(32-n))*, if `n<32`. In case `n>=32` then take `n%32` as the shifting parameter for each of the 32-bit words, and the resulting *A'* and *B'* are swapped. The refactoring of other functions is straightforward. + +``` + +/* This code may be freely used or adapted. + */ +typedef unsigned char uint8; +typedef unsigned long uint32; +typedef unsigned long long uint64; + +const uint8 Rho[25] = {0,1,62,28,27,36,44,6,55,20,3,10,43,25,39,41,45, +15,21,8,18,2,61,56,14}; + +const uint8 Pi[25] = {0,6,12,18,24,3,9,10,16,22,1,7,13,19,20,4,5,11,17, +23,2,8,14,15,21}; + +const uint8 Iota[24] = {1,146,218,112,155,33,241,89,138,136,57,42,187,203, +217,83,82,192,26,106,241,208,33,120}; + +#define ROTATE64(value, n) \ +(((uint64) (value))<<(n) | ((uint64) (value))>>(64-(n)))) + +/* ----- +64-bit version of Keccak_f(1600) +----- + */ +void Keccak_f_64(uint64 *s) +{ + uint64 t[5]; + uint8 i, j, round; + + for(round=0; round<24; ++round) + { + /* Theta function */ + for(i=0; i<5; ++i) + t[i] = s[i] ^ s[5+i] ^ s[10+i] ^ s[15+i] ^ s[20+i]; + for(i=0; i<5; ++i, s+=5) + { + s[0] ^= t[4] ^ ROTATE64(t[1], 1); + s[1] ^= t[0] ^ ROTATE64(t[2], 1); + s[2] ^= t[1] ^ ROTATE64(t[3], 1); + s[3] ^= t[2] ^ ROTATE64(t[4], 1); + s[4] ^= t[3] ^ ROTATE64(t[0], 1); + } + s -= 25; + } +} + +``` + +``` + + /* Rho function */ + for(i=1; i<25; ++i) + s[i] = ROTATE64(s[i], Rho[i]); + + /* Pi function */ + for(t[1] = s[i=1]; (j=Pi[i]) > 1; s[i]=s[j], i=j); + s[i] = t[1]; + + /* Chi function */ + for(i=0; i<5; ++i, s += 5) + { + t[0] = (~s[1]) & s[2]; + t[1] = (~s[2]) & s[3]; + t[2] = (~s[3]) & s[4]; + t[3] = (~s[4]) & s[0]; + t[4] = (~s[0]) & s[1]; + for(j=0; j<5; ++j) s[j] ^= t[j]; + } + s -= 25; + + /* Iota function */ + t[0] = Iota[round]; + *s ^= (t[0] | (t[0]<<11) | (t[0]<<26) | (t[0]<<57)) + & 0x800000008000808BULL; /* set & mask bits 0,1,3,7,15,31,63 */ + } +} + +/* ----- + 8-bit version of Keccak_f(1600) + ----- +*/ +void Keccak_f_8(uint8 s[200]) +{ + uint8 t[40], i, j, k, round; + + for(round=0; round<24; ++round) + { + /* Theta function */ + for(i=0; i<40; ++i) + t[i]=s[i]^s[40+i]^s[80+i]^s[120+i]^s[160+i]; + for(i=0; i<200; i+=8) + for(j = (i+32)%40, k=0; k<8; ++k) + s[i+k] ^= t[j+k]; + for(i=0; i<40; t[i] = (t[i]<<1)|j, i+=8) + for(j = t[i+7]>>7, k=7; k; --k) + t[i+k] = (t[i+k]<<1)|(t[i+k-1]>>7); + for(i=0; i<200; i+=8) + for(j = (i+8)%40, k=0; k<8; ++k) + s[i+k] ^= t[j+k]; + + /* Rho function */ + for(i=8; i<200; i+=8) + { + for(j = Rho[i]>>3, k=0; k<8; ++k) /* j:=bytes to shift, s->t */ + t[(k+j)&7] = s[i+k]; + for(j = Rho[i]>>3)&7, k=7; k; --k) /* j:=bits to shift, t->s */ + s[i+k] = (t[k]<>(8-j)); + s[i] = (t[0]<>(8-j)); + } + + /* Pi function */ + for(k=8; k<16; ++k) t[k] = s[k]; /* =memcpy(t+8, s+8, 8) */ + for(i=1; (j=Pi[i])>1; i=j) + for(k=0; k<8; ++k) /* =memcpy(s+(i<<3), s+(j<<3), 8) */ + s[(i<<3)|k] = s[(j<<3)|k]; + for(k=0; k<8; ++k) /* =memcpy(s+(i<<3), t+8, 8) */ + s[(i<<3)|k] = t[k+8]; + + /* Chi function */ + for(i=0; i<200; i+=40) + { + for(j=0; j<40; ++j) + t[j]=(~s[i+(j+8)%40]) & s[i+(j+16)%40]; + for(j=0; j<40; ++j) s[i+j]^=t[j]; + } + + /* Iota function */ + k = Iota[round]; + s[0] ^= k & 0x8B; /* bits 0, 1, 3, 7 */ + s[1] ^= (k<<3)&0x80; /* bit 15 */ + s[3] ^= (k<<2)&0x80; /* bit 31 */ + s[7] ^= (k<<1)&0x80; /* bit 63 */ + } +} + +``` + +``` + + } +} + +/* ----- + 32-bit version of Keccak_f(1600) + ----- +*/ +void Keccak_f_32(uint32 *s) +{ + uint32 t[10]; + uint8 i, j, round, k; + + for(round=0; round<24; ++round) + { + /* Theta function */ + for(i=0; i<10; ++i) + t[i] = s[i] ^ s[10+i] ^ s[20+i] ^ s[30+i] ^ s[40+i]; + for(i=0; i<5; ++i) + for(j=8, k=2; ; j%=10, k=(k+2)%10) + { + *s++ ^= t[j++] ^ ((t[k]<<1) | (t[k+1]>>31)); + *s++ ^= t[j++] ^ ((t[k+1]<<1) | (t[k]>>31)); + if(j==8) break; + } + s -= 50; + + /* Rho function */ + for(i=2; i<50; i+=2) + { + k = Rho[i>>1] & 0x1f; + t[0] = (s[i+1] << k) | (s[i] >> (32-k)); + t[1] = (s[i] << k) | (s[i+1] >> (32-k)); + k = Rho[i>>1] >> 5; + s[i] = t[1-k], s[i+1] = t[k]; + } + + /* Pi function */ + for(i=2, t[0]=s[2], t[1]=s[3]; (j=(Pi[i>>1]<<1))>2; i=j) + s[i]=s[j], s[i+1]=s[j+1]; + s[i]=t[0], s[i+1]=t[1]; + + /* Chi function */ + for(i=0; i<5; ++i, s+=10) + { + for(j=0; j<10; ++j) + t[j] = (~s[(j+2)%10]) & s[(j+4)%10]; + for(j=0; j<10; ++j) + s[j] ^= t[j]; + } + s -= 50; + + /* Iota function */ + t[0] = Iota[round]; + s[0] ^= (t[0] | (t[0]<<11) | (t[0]<<26)) & 0x8000808B; + s[1] ^= (t[0]<<25) & 0x80000000; + } +} + +``` + +# --- Annex F (informative): Change history + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2013-12 | | | | | | Version after approval | 12.0.0 | +| 2013-12 | | | | | | Update in Introduction with the spec numbers | 12.0.1 | +| 2014-09 | SA#64 | SP-140316 | 0001 | 2 | | Overall editorial modification to the Tuak specification TS 35.231 | 12.1.0 | +| 2016-01 | | | 0002 | 1 | F | Update to Rel-13 version (MCC). | 13.0.0 | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-06 | | | | | | Update to Rel-15 version (MCC) | 15.0.0 | +| 2019-09 | SA#85 | SP-190683 | 0005 | 1 | A | Removing references of TS 103 383 in TS 35.231 | 15.1.0 | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35232/raw.md b/marked/Rel-16/35_series/35232/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..00fa972654b46879fdf1a8bbd72e9878dfe973f5 --- /dev/null +++ b/marked/Rel-16/35_series/35232/raw.md @@ -0,0 +1,1454 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 4 Preliminary information..... | 7 | +| 4.1 Introduction ..... | 7 | +| 4.2 Radix ..... | 7 | +| 4.3 Bit/Byte ordering for Tuak inputs and outputs..... | 7 | +| 4.4 Tuak inputs and outputs ..... | 8 | +| 5 KECCAK test data ..... | 10 | +| 5.1 Overview ..... | 10 | +| 5.2 Format ..... | 10 | +| 5.3 Test set 1..... | 10 | +| 5.4 Test set 2..... | 11 | +| 5.5 Test set 3..... | 11 | +| 5.6 Test set 4..... | 12 | +| 5.7 Test set 5..... | 12 | +| 5.8 Test set 6..... | 13 | +| 6 Authentication algorithms f1 and f1* ..... | 14 | +| 6.1 Overview ..... | 14 | +| 6.2 Format ..... | 14 | +| 6.3 Test set 1..... | 14 | +| 6.4 Test set 2..... | 16 | +| 6.5 Test set 3..... | 18 | +| 6.6 Test set 4..... | 18 | +| 6.7 Test set 5..... | 21 | +| 6.8 Test set 6..... | 23 | +| 7 Algorithms f2 , f3 , f4 , f5 and f5* ..... | 25 | +| 7.1 Overview ..... | 25 | +| 7.2 Format ..... | 25 | +| 7.3 Test set 1..... | 26 | +| 7.4 Test set 2..... | 28 | +| 7.5 Test set 3..... | 28 | +| 7.6 Test set 4..... | 30 | +| 7.7 Test set 5..... | 30 | +| 7.8 Test set 6..... | 31 | +| Annex A (informative): Change history..... | 33 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The present document is second of three, which between them form the entire specification of the example algorithms, entitled: + +- 3GPP TS 35.231: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation Functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: Algorithm specification ". +- **3GPP TS 35.232: " Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Implementers' test data".** +- 3GPP TS 35.233: "specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Design conformance test data". + +# --- 1 Scope + +The present document and the other Technical Specifications in the series, TS 35.231 [4] and TS 35.233 [6], contain an example set of algorithms which could be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\** for 3GPP systems. In particular, the present document defines the test data: + +- for the Keccak permutation used within Tuak, +- for the authentication algorithms *f1* and *f1\**, +- for the algorithms *f2, f3, f4, f5* and *f5\**. + +# --- 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 33.102: "3G Security; Security Architecture". +- [2] 3GPP TS 35.206: "3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm specification". +- [3] "The KECCAK Reference", version 3.0, 14 January 2011, G. Bertoni, J. Daemen, M. Peeters, G. van Assche, (available at ). +- [4] 3GPP TS 35.231: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: Algorithm specification". +- [5] 3GPP TS 33.401: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture". +- [6] 3GPP TS 35.233: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Design conformance test data". +- [7] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [7] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [7]. + +Tuak: The name of this algorithm set is "Tuak". It should be pronounced like "too-ack". + +## 3.2 Symbols + +| | | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AK | a 48-bit anonymity key that is the output of either of the functions f5 and f5* | +| AMF | a 16-bit authentication management field that is an input to the functions f1 and f1* | +| CK | a 128-bit or 256-bit confidentiality key that is the output of the function f3 | +| IK | a 128-bit or 256-bit integrity key that is the output of the function f4 | +| IN | a 1600-bit value that is used as the input to the permutation $\Pi$ when computing the functions f1, f1*, f2, f3, f4, f5 and f5* | +| K | a 128-bit or 256-bit subscriber key that is an input to the functions f1, f1*, f2, f3, f4, f5 and f5* | +| MAC-A | a 64-bit, 128-bit or 256-bit network authentication code that is the output of the function f1 | +| MAC-S | a 64-bit, 128-bit or 256-bit resynchronization authentication code that is the output of the function f1* | +| TOP | a 256-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1, f1*, f2, f3, f4, f5 and f5* | +| TOPC | a 256-bit value derived from TOP and K and used within the computation of the functions | +| OUT | a 1600-bit value that is taken as the output of the permutation $\Pi$ when computing the functions f1, f1*, f2, f3, f4, f5 and f5* | +| RAND | a 128-bit random challenge that is an input to the functions f1, f1*, f2, f3, f4, f5 and f5* | +| RES | a 32-bit, 64-bit, 128-bit or 256-bit signed response that is the output of the function f2 | +| SQN | a 48-bit sequence number that is an input to either of the functions f1 and f1* . (For f1* this input is more precisely called SQNMS .) See informative Annex C of [1] for methods of encoding sequence numbers. | + +# 4 Preliminary information + +## 4.1 Introduction + +Within the security architecture of the 3GPP system there are seven security functions *f1, f1\*, f2, f3, f4, f5 and f5\**. The operation of these functions falls within the domain of one operator, and the functions are therefore to be specified by each operator rather than being fully standardized. The algorithms specified in this document are examples that may be used by an operator who does not wish to design his own. + +The inputs and outputs of all seven algorithms are defined in clause 4.4. + +## 4.2 Radix + +Unless stated otherwise, all test data values presented in the present document are in hexadecimal. + +## 4.3 Bit/Byte ordering for Tuak inputs and outputs + +3GPP TS 33.102 [1] includes the following convention. (There is similar text in the specification of MILENAGE, as defined in 3GPP TS 35.206 [2]): + +All data variables in the present document are presented with the most significant substring on the left hand side and the least significant substring on the right hand side. A substring may be a bit, byte or other arbitrary length bit string. Where a variable is broken down into a number of substrings, the left-most (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant. + +So, for example, RAND[0] is the most-significant bit of RAND and RAND[127] is the least significant bit of RAND. + +This convention applies to all **inputs** and **outputs** to Tuak, as listed in tables 1 to 9 below. + +However, when describing intermediate states of Tuak (e.g. inputs and outputs for the Keccak permutation), variables are simply treated as indexed bit strings. These bit strings will be presented in hexadecimal notation, using a display convention described in clause 5.2. + +## 4.4 Tuak inputs and outputs + +The inputs to Tuak are given in tables 1 and 2, the outputs in tables 3 to 9 below. + +There are a few differences from the inputs and outputs to MILENAGE [2]. + +The key K may be 128 bits **or** 256 bits. MAC-A and MAC-S may be 64, 128 **or** 256 bits. RES may be 32, 64, 128 **or** 256 bits. CK and IK may be 128 **or** 256 bits. Existing 3GPP specifications (see [1] and [5]) do not support all these possibilities, but they are included in Tuak for future flexibility in case future releases of these specifications support them. + +NOTE 1: The 3G security architecture specification [1] calls the output of the f1 function 'MAC' while the present document and [2] call it 'MAC-A'. + +Any sizes for the parameters K, MAC-A, MAC-S, RES, CK and IK mentioned in the present document shall not be supported nor used in entities defined in 3GPP specifications until these specifications explicitly allow their use. + +In any particular implementation, the parameters shall have a fixed length, chosen in advance. For example an operator may fix K at length 256 bits, RES at length 64 bits, CK and IK at length 128 bits. As the lengths do not vary with input, they are not specified as formal input parameters. + +**Table 1: Inputs to f1 and f1\*** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|---------------------------------------------------------------------------------------------------| +| K | 128 or 256 | Subscriber key K[0]...K[127] or K[0]...K[255] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | +| SQN | 48 | Sequence number SQN[0]...SQN[47] (for f1* this input is more precisely called SQN ms ) | +| AMF | 16 | Authentication management field AMF[0]...AMF[15] | + +**Table 2: Inputs to f2, f3, f4, f5 and f5\*** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-----------------------------------------------| +| K | 128 or 256 | Subscriber key K[0]...K[127] or K[0]...K[255] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | + +**Table 3: f1 output** + +| Parameter | Size (bits) | Comment | +|-----------|----------------|----------------------------------------------------------------------------------------------------| +| MAC-A | 64, 128 or 256 | Network authentication code MAC-A[0]...MAC-A[63] or MAC-A[0]...MAC-A[127] or MAC-A[0]...MAC-A[255] | + +**Table 4: f1\* output** + +| Parameter | Size (bits) | Comment | +|-----------|----------------|----------------------------------------------------------------------------------------------------| +| MAC-S | 64, 128 or 256 | Resynch authentication code MAC-S[0]...MAC-S[63] or MAC-S[0]...MAC-S[127] or MAC-S[0]...MAC-S[255] | + +**Table 5: f2 output** + +| Parameter | Size (bits) | Comment | +|-----------|--------------------|-----------------------------------------------------------------------------------------| +| RES | 32, 64, 128 or 256 | Response RES[0]...RES[31] or RES[0]...RES[63] or RES[0]...RES[127] or RES[0]...RES[255] | + +**Table 6: f3 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------------| +| CK | 128 or 256 | Confidentiality key CK[0]...CK[127] or CK[0]...CK[255] | + +**Table 7: *f4* output** + +| Parameter | Size (bits) | Comment | +|------------------|--------------------|--------------------------------------------------| +| IK | 128 or 256 | Integrity key IK[0]...IK[127] or IK[0]...IK[255] | + +**Table 8: *f5* output** + +| Parameter | Size (bits) | Comment | +|------------------|--------------------|------------------------------| +| AK | 48 | Anonymity key AK[0]...AK[47] | + +**Table 9: *f5\** output** + +| Parameter | Size (bits) | Comment | +|------------------|--------------------|--------------------------------------| +| AK | 48 | Resynch anonymity key AK[0]...AK[47] | + +NOTE 2: Both *f5* and *f5\** outputs are called AK according to [1]. In practice only one of them at a time will be calculated in any given call to the authentication and key agreement algorithms. + +# 5 KECCAK test data + +## 5.1 Overview + +The test data sets presented here are for the cryptographic permutation Keccak-f[1600], as it is specified in [3], and used within [4]. This permutation is abbreviated as $\Pi$ , and use strings **IN**[0] .. **IN**[1599] and **OUT**[0] .. **OUT**[1599] to represent the input and output of $\Pi$ . + +## 5.2 Format + +For brevity, the **IN** and **OUT** strings are presented as lists of 200 bytes (octets), with each individual byte written separately in hexadecimal notation. The lists of bytes should be read from left to right, and then from top to bottom. + +For **IN**, the first byte of the list will denote the bits **IN**[0] to **IN**[7], with **IN**[0] equal to the *least* significant bit of the corresponding hexadecimal number equal to and **IN**[7] equal to the *most* significant bit of the same hexadecimal number. The final byte of the list will denote **IN**[1592] to **IN**[1599], with **IN**[1592] equal to the *least* significant bit of the corresponding hexadecimal number, and **IN**[1599] equal to the *most* significant bit of the same number. + +**OUT** strings will be presented in the same way. + +As an example, in Test Set 1 below: + +``` + +IN[0] = 0, IN[1] = 0, IN[2] = 1, IN[3] = 0, IN[4] = 0, IN[5] = 1, IN[6] = 0, IN[7] = 0, +IN[8] = 0, IN[9] = 1, IN[10]=1, IN[11]=0, IN[12]=1, IN[13]=1, IN[14]=1, IN[15]=0, ... , +IN[1584]=1, IN[1585]=1, IN[1586]=0, IN[1587]=1, IN[1588]=0, IN[1589]=0, IN[1590]=0, IN[1591]=0, +IN[1592]=0, IN[1593]=0, IN[1594]=0, IN[1595]=0, IN[1596]=1, IN[1597]=0, IN[1598]=1, IN[1599]=0. + +OUT[0] = 1, OUT[1] = 1, OUT[2] = 1, OUT[3] = 1, OUT[4] = 0, OUT[5] = 1, OUT[6] = 0, OUT[7] = 0, +OUT[8] = 0, OUT[9] = 0, OUT[10]=1, OUT[11]=1, OUT[12]=1, OUT[13]=0, OUT[14]=1, OUT[15]=1, ... , +OUT[1584]=0, OUT[1585]=1, OUT[1586]=1, OUT[1587]=1, OUT[1588]=1, OUT[1589]=0, OUT[1590]=0, +OUT[1591]=0, OUT[1592]=1, OUT[1593]=1, OUT[1594]=1, OUT[1595]=0, OUT[1596]=0, OUT[1597]=1, +OUT[1598]=0, OUT[1599]=1. + +``` + +## 5.3 Test set 1 + +``` + +IN: +24 76 d2 da c5 9e 2e 93 49 df 32 55 a9 da b1 b6 9e b5 c2 08 f1 51 c7 30 9e 8c 8f 17 db 45 6d 0b 5e +b0 af b6 c7 3e 37 ce 8c cc cf 20 b7 9d 8a 67 29 41 49 17 48 09 e4 29 70 93 30 c4 ad 23 1d 3e 52 11 +ae 0b d8 05 20 c4 3a d4 b4 36 62 57 92 a7 6c 52 08 9d 0f 73 92 71 15 1a 37 59 4d f6 6d e4 42 9f 3c +97 0a 34 56 b6 ce 2c 78 cd 11 28 71 7f 4b db 73 1a 4c 97 db e5 eb 73 53 fe 81 e3 7c 33 ac 60 b8 21 +22 ea c6 11 a9 8e 0e 74 42 b9 99 64 75 22 93 e4 f9 c6 96 ba 05 f0 7a 21 45 1f 90 73 0c 96 78 c6 45 +ad 4b e4 4c 4d 2d 98 1a 34 12 08 1c 9c 6b 05 c9 93 ff 1c 56 1a 0d 24 2b 47 06 d5 01 c3 47 65 b3 7a +0b 50 + +OUT: +2f dc 58 d4 d9 4a 88 4c 1c b0 3a 8e 63 ac ab 83 75 e8 56 b5 61 ba 3a 06 25 e8 30 ac db 55 73 42 86 +64 6f 87 18 9b 43 54 25 b5 d6 65 4e 22 82 28 b6 97 b8 1c be ad 65 5b 71 aa cc c2 5e 3d 7e 51 b5 cb +5a c2 27 f6 7f 2a d8 a0 62 97 67 82 b0 8a 7e c3 f1 b5 38 d6 00 8c 0b ab ef 83 da 64 36 6b 62 a5 3f +88 a3 dc 06 29 bd ed 79 5f 32 20 f3 c6 5c 76 bd d0 12 43 e8 8f 63 d6 91 2e 5f b5 cd a1 67 b7 1f 9b +aa a7 42 dc 19 3f f7 8c 17 67 a3 8a 1c 96 40 8c ce 16 92 39 b0 77 f2 90 3a 07 b8 c4 6a 04 8d 66 31 +8e 59 5e a4 bb 92 99 2c 7c 2d 3d cd 38 19 75 b6 e0 5f 85 ba 18 15 20 96 cc 30 ed 22 14 0f f3 b6 71 +1e a7 + +``` + +## 5.4 Test set 2 + +**IN:** + +``` +80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +**OUT:** + +``` +44 e0 e5 8c a9 68 97 5c 4c 25 92 a1 57 f5 3f 21 24 51 9b 01 0b 89 e1 5e 30 1e f5 8f 76 50 1d b5 9c +de 06 7f 1f de 09 c0 a4 b5 c2 10 a6 a1 9f 06 ba 4c 8f 0c 6f c8 68 f0 fc 80 a6 3b 25 53 79 1e 41 c8 +22 78 ad 11 5e 5c 70 f7 1d 64 1f f0 77 4a a5 d5 f6 d9 91 49 14 02 2c 51 4c 35 fc e8 a6 1c b6 6b +0f 03 13 e3 49 88 ae 0d 36 73 7e 2c 05 29 90 7f e6 53 fc 4e 18 5d 07 f3 96 1f 82 6b b8 80 31 af 84 +4d 9e 7d 98 76 17 03 63 fd e7 67 86 c5 8c cb cf 5c 3a 01 bb 91 4c 1b 02 08 a2 7c 7b e3 bb bb bb 99 +76 e0 40 31 7a fc 2a fb fa dc 7b a7 fc 23 72 35 c6 55 51 aa 31 39 64 1f a8 db 2e 64 83 f2 87 40 b3 +1b 61 +``` + +## 5.5 Test set 3 + +**IN:** + +``` +01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 +22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 +43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 +64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 +85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 +a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 +c7 c8 +``` + +**OUT:** + +``` +5d d0 e3 dd 9e 46 db 21 87 a9 e1 a4 44 42 7d 7a 83 2f ef 29 91 39 90 e0 15 ea 8d 1f 3f 1f a6 41 3f +fb bc 58 6f 5a 4d 69 4d d6 06 68 fb f3 b4 bb da 49 45 c9 ea 0c be e2 11 73 5e bf a8 39 9b 61 3a ff +34 d1 dd 47 fa 39 8c 78 f4 8a 91 a6 65 7d 29 03 6c 87 f7 73 5f 43 e2 ab b7 6a 13 50 45 b7 0e 42 c5 +9d 80 92 14 a4 cd 30 1f 18 57 30 0a 55 d0 1d 32 36 5b 6a bd a5 1e ad 75 41 db 7b ed dc 46 e4 85 72 +7c 3b 2b 5d 83 b5 9e 5a 7a 62 e0 13 16 14 ba 0d 7b fa cd 4e ba 71 62 32 80 88 59 f0 03 85 5f 5c 47 +01 0a 50 e1 26 2f 9e 9e 81 2e 6c b3 dd 52 d9 ad b7 be 19 10 42 76 34 02 52 31 96 8d e0 b4 3f a2 4b +4b 3e +``` + +## 5.6 Test set 4 + +IN: + +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab + +OUT: + +00 52 f0 0e b4 09 b5 ce 5f 78 e9 53 20 ee 6a 71 5f 5b 1a 0a 7e 5b ed 03 43 d6 91 13 30 ab e2 fc 57 +b6 6f b5 ba 9e f2 88 0b 05 75 ed 0a 98 70 c5 0c 66 57 83 8a 1d 32 f3 88 fd c3 a4 e7 32 46 dd d9 56 +58 74 77 c4 c8 d4 1a d4 19 14 04 52 cc 17 13 23 ae 1f f0 91 0c e1 c3 27 8b 62 c6 48 75 91 2b 7f 7c +21 cf a0 52 e0 b0 40 21 4c 5f 3b 81 c3 20 75 87 92 ce a0 c8 d1 e4 2e 92 e1 ef 3c f0 66 be 16 c6 1e +e4 4d dd 69 db 72 9a 82 5d 4d bb fd 9f 97 da 46 c6 10 3d 5a 5f 8c 8d 21 bd 42 7d 58 af 4b 41 11 78 +be 5a 1a 86 a0 c9 1d 38 c4 85 ee 2d 54 72 bd d0 a5 b9 fa ab f7 07 73 13 ca f9 f3 0a 1e 46 ac 8e +12 58 + +## 5.7 Test set 5 + +IN: + +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd + +OUT: + +c1 6c a0 6d ef 3a dd 45 b2 0c cf d6 7a a8 f9 12 15 c2 e8 75 1e dd 02 a5 10 3f 61 ba 6f 7b f3 bb b2 +59 5f 41 1b af 6a ab 16 53 f1 7e 95 1e 2d c8 8d fb f7 68 67 94 0a 63 38 60 82 18 f8 df f1 41 7b db +3c 6f 45 22 64 87 a9 a6 07 8b 65 6a 37 ff 86 1d fa 79 30 77 c0 88 03 a8 b9 62 da 67 24 dd c8 6d 10 +93 ff d0 05 88 a2 8e 6c 1b 80 1f 73 54 63 bc 05 58 1e d5 97 bd bf 37 a4 59 29 7f 65 05 39 98 9e fc +4a 7a 9c 8b 22 33 c0 20 de a3 00 34 c1 f2 c6 cf 5e 0c cc cc 53 55 40 87 18 03 ed 3d 20 b0 c5 10 13 +a3 02 4a c5 6b 33 af 5a 26 11 23 3d 53 7d 11 80 4e f0 2e b5 59 78 ff d4 3d 9a 7e 48 84 42 64 de ce +8f a8 + +## 5.8 Test set 6 + +IN: + +``` + +00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 04 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 00 +00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 02 00 00 +00 00 00 00 00 03 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 +00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 01 00 00 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 00 00 00 04 00 00 00 00 00 00 +00 00 + +``` + +OUT: + +``` + +56 0d be 41 f6 a7 5a 7d 33 e1 5d 6b fe 0b dc 64 7d e5 54 34 1c e0 d0 61 bb bd f1 be 75 76 49 de e7 +41 b1 fd 37 41 8d a6 f3 5a b7 0e 15 87 cc 36 8c 1b 89 ad cc ce 1d 07 ad 92 0d 4d 9d 08 a0 43 94 6c +2f 6f e1 a5 17 a2 49 ce 3c 8a 5f 83 4e cc fa 2f aa ad ec 32 e6 db 24 d4 2a 2b 04 a7 84 63 a9 b2 +df 6d 2f 02 fc 5c 29 73 2a 12 65 14 fb 15 eb 7a be 7f bf 57 18 91 66 91 c7 c2 f8 43 46 00 da 7e 2f +9b 76 65 a5 9c 61 41 11 55 05 c9 d9 e9 f8 05 af 6f 9e 6b c4 f1 9c 65 c6 0e a9 72 a6 e4 fa 01 85 7d +29 8a 09 26 83 90 d5 74 f6 3d 4f 76 fb 6d 6d fc d1 37 38 c4 98 48 ac d5 1e 4e d7 83 af a1 ba 52 0f +a3 37 + +``` + +# 6 Authentication algorithms $f1$ and $f1^*$ + +## 6.1 Overview + +The test data sets presented here are for the authentication algorithms $f1$ , $f1^*$ . Inputs and outputs to the permutation $\Pi$ are also presented here to assist with the implementation. + +## 6.2 Format + +Each test starts by showing the various inputs (K, RAND, SQN, AMF) to the functions. Next are shown the operator configuration field TOP, and other operator configuration parameters: the length of the K, the length of the output MAC, and the number of Keccak iterations. + +These are followed by the value of $TOP_C$ and then the output values of $f1$ and $f1^*$ are shown. The value $TOP_C$ should not be computed on but off the UICC. In the example code $TOP_C$ is computed inside the functions, so it was included in the test data. + +All the input, output and configuration parameters are presented using the bit/byte ordering convention described in clause 4.3. Intermediate inputs and outputs to the permutation $\Pi$ are also shown, as lists of 200 bytes, using the convention described in clause 5.2. + +## 6.3 Test set 1 + +### Input Parameters: + +``` + +K: ababababababababababababababababab +RAND: 42424242424242424242424242424242 +SQN: 1111111111111111 +AMF: ffff + +``` + +### Operator Configuration Parameters: + +``` + +TOP: 5555555555555555555555555555555555555555555555555555555555555555 +Klength = 128 bits, MACLength = 64 bits, KeccakIterations = 1 +TOPc: bd04d9530e87513c5d837ac2ad954623a8e2330c115305a73eb45d1f40cccbff + +``` + +### Output Parameters: + +``` + +f1: f9a54e6aea8618d +f1*: e94b4dc6c7297df3 + +``` + +Intermediate Values: + +**IN** when computing $TOP_C$ : + +``` + +55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 00 +30 2e 31 4b 41 55 54 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +``` + +**OUT** when computing $TOP_C$ : + +``` + +ff cb cc 40 1f 5d b4 3e a7 05 53 11 0c 33 e2 a8 23 46 95 ad c2 7a 83 5d 3c 51 87 0e 53 d9 04 bd de +03 f9 ad b1 49 08 91 49 1c 23 5c 3d 41 31 eb 8f 9a 84 b5 fe b1 84 d6 13 c1 c4 db 07 6d 19 ea ac df +d0 24 e8 8e e9 53 a0 6c 3d 13 31 ad 61 14 00 4f 62 b3 bc da 77 fd 10 58 05 50 06 40 9a 40 6d 84 ac +a3 b2 62 dd 7b c8 76 b7 36 43 df 2c 55 a3 f1 af 11 63 ba 79 da aa 4f ce 02 fc fe 7f d4 d8 b6 06 f1 +eb 71 e8 9f 92 46 4c 4a 24 e8 6a 29 72 78 6c 81 53 b4 ca 21 46 35 49 da 3a b3 e0 b7 19 5b be e4 e7 +7f 77 d1 29 05 0a 99 5f 61 bd 0b 2f 72 e0 8a ae 75 aa fe b4 1e ee b0 4f 8c 51 ff f1 91 27 a7 9b 2c +99 b7 + +``` + +**IN** when computing $f1$ : + +``` + +ff cb cc 40 1f 5d b4 3e a7 05 53 11 0c 33 e2 a8 23 46 95 ad c2 7a 83 5d 3c 51 87 0e 53 d9 04 bd 08 +30 2e 31 4b 41 55 54 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 ff ff 11 11 11 11 11 11 ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + +``` + +``` +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +**OUT** when computing f1: + +``` +8d 61 a8 ea 6a 4e a5 f9 61 5f 1e f1 ee 2b 9e 22 f6 f3 3b b0 c6 59 1c b2 ef ed f4 6b fe 15 b3 bf a4 +93 5c 6d 5d 52 af 2c 27 81 c7 6f 16 10 ee 84 8e 81 86 59 e8 c3 45 8f 78 b8 a4 a5 a9 66 11 6c ef 4a +1a 9e f1 e4 56 16 2e ef 18 c5 51 fd 9e 52 99 72 ca 01 51 67 0e 3f 04 c0 f7 08 ab 30 a9 be 52 31 26 +ad 2d 8d b2 43 9a 41 29 3e d9 27 4b fc 7e 30 e7 73 69 25 61 16 6c d3 e0 16 23 6a 61 5e 2d de df ff +92 36 3d 2a 38 f0 e1 12 d7 31 f5 14 ec 84 5c 26 c7 f9 a9 1f 17 a4 27 f5 e4 30 ec 28 19 94 b9 b4 4a +50 79 e4 08 52 ca 0b 66 67 a6 55 71 8e c3 34 8b 81 2e 83 f5 8b de 28 23 f3 b5 de 18 89 21 00 8f 1e +93 03 +``` + +**IN** when computing $f1^*$ : + +``` +ff cb cc 40 1f 5d b4 3e a7 05 53 11 0c 33 e2 a8 23 46 95 ad c2 7a 83 5d 3c 51 87 0e 53 d9 04 bd 88 +30 2e 31 4b 41 55 54 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 ff ff 11 11 11 11 11 11 ab ab +ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +OUT when computing $f_1^*$ : + +``` +f3 7d 29 c7 c6 4d 4b e9 08 40 73 fe c7 69 e9 b0 ca 72 71 ef e7 7b 16 1c 8e 9d 81 4d 4e 19 77 c0 8d +f0 52 cd 65 a7 1e 21 b2 6c 31 72 ae 3c c4 ea 93 a1 4f 98 17 18 3d 3a 22 6e ce f0 a9 f1 a6 9d ca 75 +2d fd ee 32 98 ce 01 55 ac 90 a6 df 92 51 c1 95 b6 1a 78 25 f0 48 ca de ee 77 5e e0 9b cb 14 4b f9 +58 bb cf de 3f da b2 7e 1a 1e 19 5c a3 19 02 de 39 94 24 d6 1b eb 57 17 df 4b d2 c7 f9 f4 57 84 7c +43 7e bb 4e 73 ca c1 18 61 8c 98 87 0a b9 60 40 3d 40 b4 40 61 ab db 81 1e 44 1c 62 0f 03 95 0f da +e3 c3 84 4c 08 b1 51 56 5a fe 60 0b ce ad 14 ca 09 b6 8a e2 d3 a5 f4 0c a4 d0 7e db 90 d4 c1 8a f7 +00 9f +``` + +## 6.4 Test set 2 + +### Input Parameters: + +K: fffefdfcfbfaf9f8f7f6f5f4f3f2f1f0efeedecebeae9e8e7e6e5e4e3e2e1e0 + RAND: 0123456789abcdef0123456789abcdef + SQN: 0123456789ab + AMF: abcd + +### Operator Configuration Parameters: + +TOP: 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f + Klength = 256 bits, MAClength = 128 bits, KeccakIterations = 1 + TOPc: 305425427e18c503c8a4b294ea72c95d0c36c6c6b29d0c65de5974d5977f8524 + +### Output Parameters: + +f1: c0b8c2d4148ec7aa5f1d78a97e4d1d58 + f1\*: ef81af7290f7842c6ceafa537fa0745b + +### Intermediate Values: + +#### IN when computing TOPc: + +9f 9e 9d 9c 9b 9a 99 98 97 96 95 94 93 92 91 90 8f 8e 8d 8c 8b 8a 89 88 87 86 85 84 83 82 81 80 01 + 30 2e 31 4b 41 55 54 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing TOPc: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 90 + db 97 25 30 c0 28 ed 2d 29 7e a9 37 bb 65 75 b6 06 03 b5 3d 24 25 bf 21 85 91 4c 29 83 a0 c0 22 7b + 8c 8e 29 1e 56 23 b9 87 fd e7 9c eb 91 82 38 96 7c e0 51 0e 15 dc 83 cd 84 20 b2 45 2a b8 5f b6 f5 + 2f af 79 d2 df 63 ac f1 bb e2 4a 7d 71 a3 4b 48 ca 88 28 1a 55 f5 e6 6f 61 0f 08 a0 b7 05 11 b8 1f + 1c fb 47 97 c0 48 d0 36 08 c0 10 10 0f 02 dd 81 95 06 b9 8e 0a 1f 28 14 a2 54 36 d2 0a 7f 27 82 24 + 13 f4 b7 2d 31 76 5a d2 19 4f 42 27 70 2c e1 98 50 4e 21 d3 15 8f a6 f1 9e e0 3a 87 90 f0 a2 9c 30 + 8c b5 + +#### IN when computing f1: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 11 + 30 2e 31 4b 41 55 54 ef cd ab 89 67 45 23 01 ef cd ab 89 67 45 23 01 cd ab ab 89 67 45 23 01 e0 e1 + e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing f1: + +58 1d 4d 7e a9 78 1d 5f aa c7 8e 14 d4 c2 b8 c0 11 fe 0e 69 e9 d9 72 c8 9a e9 c0 99 88 b6 2c 37 ea + 3f c3 e5 7f 18 63 d3 62 f9 fc 91 f9 92 b8 50 48 54 19 ed bf ee 23 79 4d 15 09 57 82 72 78 1a 1d 54 + 3d a6 ac 45 16 59 2c 0f b3 f5 ec 99 f1 5b 94 dc bc 7a 63 bc da 40 36 5f 9e a8 d6 e2 3a b2 9d b5 b7 + 1f 26 4e c3 61 95 b6 12 79 84 66 4f 3e 74 ba e0 9e b6 ce b0 66 94 22 14 8e e8 c9 12 dd dc bf f9 f9 + 30 e2 b3 8b 5c 8b 6b d8 90 b6 14 1c 02 7f 23 9c bf f4 f2 e2 3c 2d c4 89 f3 7a 61 38 18 cd 64 7a 27 + 56 05 5a 4e de 7e c4 66 74 37 24 6d 90 be 59 b6 ed f9 35 19 50 68 e6 d2 f1 82 60 80 3d 07 bd b7 ae + 59 4c + +#### **IN** when computing f1\*: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 91 +30 2e 31 4b 41 55 54 ef cd ab 89 67 45 23 01 ef cd ab 89 67 45 23 01 cd ab ab 89 67 45 23 01 e0 e1 +e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +#### **OUT** when computing f1\*: + +5b 74 a0 7f 53 fa ea 6c 2c 84 f7 90 72 af 81 ef 3c 41 02 e7 94 ab e0 40 1b ce a6 44 c2 c8 13 1f 54 +7d 3d 57 fc ac c4 9c 07 9d fd e2 ec ac e8 56 43 78 70 87 44 63 f5 6f 92 94 12 b1 6b 67 6d 67 d3 3a +f9 cc 1e bc 4f 8b 99 4c 3f 64 6a a5 f5 38 dc 83 64 16 bf 7d 32 e6 cf 72 41 46 63 2b df 11 a5 2a 96 +65 1e ef 55 3d b3 b0 0d f3 93 c2 d8 a4 29 cb 4c d4 b6 e9 3f 11 e1 f4 95 a4 a1 5f dd 50 e6 e9 67 6e +ab ba 56 49 24 e4 2b 89 fe 6a cd f8 23 c8 29 15 ad a3 39 37 c5 f2 c6 7a f3 c0 27 0f d8 49 1d 1d 22 +bc c3 ff a1 0e 8d 25 df c5 1d 72 ab 86 0a 8a e6 cc 43 e2 5e f7 0c 14 82 8c c9 3d e0 a7 26 ba f6 f4 +4b eb + +## 6.5 Test set 3 + +### Input Parameters: + +K: fffefdfcfbfaf9f8f7f6f5f4f3f2f1f0feeedecebeae9e8e7e6e5e4e3e2e1e0 + RAND: 0123456789abcdef0123456789abcdef + SQN: 0123456789ab + AMF: abcd + +### Operator Configuration Parameters: + +TOP: 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f + Klength = 256 bits, MAClength = 256 bits, KeccakIterations = 1 + TOPc: 305425427e18c503c8a4b294ea72c95d0c36c6c6b29d0c65de5974d5977f8524 + +### Output Parameters: + +f1: d97b75a1776065271b1e212bc3b1bf173f438b21e6c64a55a96c372e085e5cc5 + f1\*: 427bbf07c6e3a86c54f8c5216499f3909a6fd4a164c9fe235b1550258111b821 + +### Intermediate Values: + +As for Test Set 2 in clause 6.4, when computing TOPc. + +#### IN when computing f1: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 21 + 30 2e 31 4b 41 55 54 ef cd ab 89 67 45 23 01 ef cd ab 89 67 45 23 01 cd ab ab 89 67 45 23 01 e0 e1 + e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing f1: + +c5 5c 5e 08 2e 37 6c a9 55 4a c6 e6 21 8b 43 3f 17 bf b1 c3 2b 21 1e 1b 27 65 60 77 a1 75 7b d9 75 + 4e b1 85 f6 20 a8 57 a8 55 ce 33 ce b3 98 40 b3 06 ca 9c 15 6d 87 36 0d 3d e0 13 b0 41 c8 00 68 80 + 90 da 63 7c 2d 0a 80 79 02 a7 a3 b1 fd ce 8b f2 ac 0a 0f 17 04 e3 3c 28 37 ed c6 df 01 88 b9 5b b6 + 49 10 99 d1 62 e3 dd 92 03 fa bb f9 99 df 76 ca c8 4e d6 fb 8a da dd 1e cf 07 be 52 9e 74 6e 17 c9 + 22 a0 e5 4e e4 30 a1 76 5b bc bb cc b0 6d b0 b9 c3 95 26 4f 3b 4e b9 d7 6f d6 fc bc f9 4c 0e 4f 13 + c4 69 23 70 70 50 4f 9e 0a 16 b2 22 5b ad 56 58 ff 19 26 93 39 73 37 7a 5c 96 75 7f 38 eb a2 c0 8e + 00 1d + +#### IN when computing f1\*: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 a1 + 30 2e 31 4b 41 55 54 ef cd ab 89 67 45 23 01 ef cd ab 89 67 45 23 01 cd ab ab 89 67 45 23 01 e0 e1 + e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing f1\*: + +21 b8 11 81 25 50 15 5b 23 fe c9 64 a1 d4 6f 9a 90 f3 99 64 21 c5 f8 54 6c a8 e3 c6 07 bf 7b 42 d9 + 20 f9 d5 1e 28 2a a6 4f a7 ed 58 9b 93 f2 37 b9 0d d5 6f c7 fa 6d 05 a4 c9 b7 5d b4 28 1c 19 5b d7 + fb 1d 5f 56 98 4a a3 ec fe ef a6 7a 05 90 67 5a 67 5b 95 03 fb 05 59 6d a7 7b a7 0c 17 aa d6 2e c2 + 1d 24 5e 25 82 b1 b7 d2 bd 0a 38 6f 51 93 a6 b4 a3 b2 00 42 ab be 68 ad 2b 58 da 9d ac 7c 9b d5 82 + 8a fb 15 ad 25 e5 b0 49 14 54 ba 3a 32 bd f8 7d 14 f0 3d 24 61 a8 65 f1 5f 51 62 41 ec 3d 54 d5 4f + b4 16 4f dd db f4 c9 9e a3 74 40 96 32 ec 8d bd 00 1f c6 71 f3 31 ae 5e fd 3d 90 bb a5 7b 62 fb a6 + 46 d2 + +## 6.6 Test set 4 + +### Input Parameters: + +K: b8da837a50652d6ac7c97da14f6acc61 + RAND: 6887e55425a966bd86c9661a5fa72be8 + SQN: 0dea2ee2c5af + AMF: df1e + +### Operator Configuration Parameters: + +TOP: 0952be13556c32ebc58195d9dd930493e12a9003669988ffde5fa1f0fe35cc01 + +Klength = 128 bits, MAClength = 128 bits, KeccakIterations = 1 +TOPc: 2bc16eb657a68e1f446f08f57c0efb1d493527a2e652ce281eb6ca0e4487760a + +### Output Parameters: + +``` + +f1: 749214087958dd8f58bfcdf869d8ae3f +f1*: 619e865afe80e382aee13063f9dfb56d + +``` + +### Intermediate Values: + +#### **IN** when computing TOPc: + +``` + +01 cc 35 fe f0 a1 5f de ff 88 99 66 03 90 2a e1 93 04 93 dd d9 95 81 c5 eb 32 6c 55 13 be 52 09 00 +30 2e 31 4b 41 55 54 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 61 cc +6a 4f a1 7d c9 c7 6a 2d 65 50 7a 83 da b8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +``` + +#### **OUT** when computing TOPc: + +``` + +0a 76 87 44 0e ca b6 1e 28 ce 52 e6 a2 27 35 49 1d fb 0e 7c f5 08 6f 44 1f 8e a6 57 b6 6e c1 2b 6a +1d 66 b7 67 81 62 b7 4d 5a 55 3e 82 41 ec 7a e5 dd 89 25 12 a9 44 90 1a b6 e0 cb c9 ee a3 bd 86 ad +43 7f ae d3 2b 85 e1 38 af 04 03 66 1c 68 87 d9 e6 84 c7 ec 20 78 27 ea bd a3 63 22 2d f1 e6 f3 bb +5f 19 35 fc eb 75 2c 8e 86 30 68 1c fd 80 86 46 cd 31 dd 5a 65 8e de d4 68 40 d2 d7 7e 3d 6f 67 7b +14 e6 0d c1 43 ab 18 02 ee 4c 54 46 e5 a9 15 af 75 10 f5 b6 e4 03 c5 84 d3 d9 f5 9c 83 07 96 86 62 +0d 1a 1d 9c 48 f7 89 a4 6d 00 04 ef a7 f3 1c 7e 08 a1 d4 85 ae e1 4c 15 fa 3a 09 ac 62 00 5d c7 8e +13 42 + +``` + +**IN** when computing f1: + +``` + +0a 76 87 44 0e ca b6 1e 28 ce 52 e6 a2 27 35 49 1d fb 0e 7c f5 08 6f 44 1f 8e a6 57 b6 6e c1 2b 10 +30 2e 31 4b 41 55 54 e8 2b a7 5f 1a 66 c9 86 bd 66 a9 25 54 e5 87 68 1e df af c5 e2 2e ea 0d 61 cc +6a 4f a1 7d c9 c7 6a 2d 65 50 7a 83 da b8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +``` + +**OUT** when computing f1: + +``` + +3f ae d8 69 f8 cd bf 58 8f dd 58 79 08 14 92 74 cf f4 d0 cd c5 0f e0 23 26 0d 55 74 cf c5 a3 83 6a +58 31 c8 61 39 47 b8 65 77 5b 59 92 a5 6a 74 37 0e 9b eb fb 24 57 5a 04 ab 80 11 96 c3 9a de 74 62 +2c dc c3 e5 1d 00 e2 45 1c e2 cd 54 ea 44 d2 6b b9 c3 db 0b 3e da 55 d6 02 7e 87 63 4d 3a 7d 83 93 +07 ff da 7a 49 0d 3e c1 91 6d 5f aa 8c a9 92 43 d1 99 3f 72 ad 47 e2 a6 fa bb 68 1e c4 17 54 53 fe +54 fc 6f 31 45 1e 3c ed a3 39 17 44 87 a2 6e 6a 1d 58 77 76 86 8a e5 c9 02 d6 7c 07 ce 5b 79 e3 9e +8d cf 2e 29 fd 8c 6a 8d dd c8 07 a5 c5 e3 90 b7 09 38 df 54 ae a7 1e c9 9a 6c 34 5c 6a ae e8 04 5d +4a 13 + +``` + +**IN** when computing $f_1^*$ : + +``` + +0a 76 87 44 0e ca b6 1e 28 ce 52 e6 a2 27 35 49 1d fb 0e 7c f5 08 6f 44 1f 8e a6 57 b6 6e c1 2b 90 +30 2e 31 4b 41 55 54 e8 2b a7 5f 1a 66 c9 86 bd 66 a9 25 54 e5 87 68 1e df af c5 e2 2e ea 0d 61 cc +6a 4f a1 7d c9 c7 6a 2d 65 50 7a 83 da b8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +``` + +**OUT** when computing $f_1^*$ : + +``` + +6d b5 df f9 63 30 e1 ae 82 e3 80 fe 5a 86 9e 61 38 ad 67 63 c4 95 c9 d9 a6 36 e6 cb 97 a9 0b 9e 39 +a7 ea 5f bc b4 76 48 96 e8 07 e6 32 05 16 0d e8 ee f8 2e ed bb 95 c0 09 60 8c f7 ee ba 0c 08 b4 9c +76 31 3c ba dc fb 2b 18 b4 94 fa a4 e2 0a 68 e8 7a 35 73 41 bf d9 81 a9 69 18 0b 26 7d 11 fc be de 7a +04 85 a7 b3 05 b3 38 83 53 0e 9c c3 de 4b a5 c2 c7 1e 35 03 cc 19 0e 69 22 18 f7 b4 42 e4 be a7 06 +41 96 71 8a 8e 90 63 6b 03 60 30 80 95 93 12 4b df a7 22 6f ca 04 c8 64 77 e7 6e 12 51 88 0e 6e d9 +01 86 af b5 37 99 54 fc 19 18 55 09 85 73 c7 e9 22 60 c0 bd 07 e3 23 04 66 dd 3d 95 af 93 13 14 bf +5c b3 + +``` + +## 6.7 Test set 5 + +### Input Parameters: + +K: 1574ca56881d05c189c82880f789c9cd4244955f4426aa2b69c29f15770e5aa5 + RAND: c570aac68cde651fb1e3088322498bef + SQN: c89bb71f3a41 + AMF: 297d + +### Operator Configuration Parameters: + +TOP: e59f6eb10ea406813f4991b0b9e02f181edf4c7e17b480f66d34da35ee88c95e + Klength = 256 bits, MAClength = 64 bits, KeccakIterations = 1 + TOPc: 3c6052e41532a28a47aa3cbb89f223e8f3aaa976aeacd48bc3e7d6165a55eff62 + +### Output Parameters: + +``` + +f1: d7340dad02b4cb01 +f1*: c6021e2e66accb15 +``` + +### Intermediate Values: + +#### **IN** when computing TOPc: + +``` + +5e c9 88 ee 35 da 34 6d f6 80 b4 17 7e 4c df 1e 18 2f e0 b9 b0 91 49 3f 81 06 a4 0e b1 6e 9f e5 01 +30 2e 31 4b 41 55 54 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +#### **OUT** when computing TOPc: + +62 ff 5e a5 65 61 7d 3e bc 48 cd ae 76 a9 aa f3 e8 23 f2 89 bb 3c aa 47 8a a2 32 15 e4 52 60 3c 43 + f5 71 a5 ba 6c 9d 75 07 6f 91 9a b5 a5 4c d7 78 70 f9 b7 8d 11 f2 61 41 78 05 1e d8 ba a8 cd 6e 09 + df 81 0a 0a b1 1f 3d 73 47 e5 77 d9 b3 fc 93 75 6e ef 30 fd 3d 8a 38 9a 80 ad 11 97 2f 07 a8 fe f8 + 22 43 46 74 bd 13 f2 ef 33 54 45 2f 2e c9 b0 91 b3 1b 51 e3 11 29 ab 2a 70 54 96 ff c9 ce ee e8 7e + 08 ea 5a 75 44 fd ce 57 08 ea 7b 2d a1 c2 a9 15 bc 2a 48 cd a1 58 2d 05 6e 6e 25 c7 48 24 7a 6e 95 + 66 6d e3 24 de 09 24 72 4d 20 ae 2a ce d6 e0 5b ea 53 22 91 27 96 3f b9 4f 72 28 85 02 cb a6 94 95 + 1c 0f + +#### **IN** when computing f1: + +``` + +62 ff 5e a5 65 61 7d 3e bc 48 cd ae 76 a9 aa f3 e8 23 f2 89 bb 3c aa 47 8a a2 32 15 e4 52 60 3c 09 +30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 7d 29 41 3a 1f b7 9b c8 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +#### **OUT** when computing f1: + +01 cb b4 02 ad 0d 34 d7 dd 3d 1c 29 35 6f 0c 34 05 fb f6 00 94 91 47 ff 38 52 13 d1 10 a7 f5 4d 4e + ae 0c f2 e9 24 4b e1 37 2f 4d 42 18 ff e0 4e b0 4c 8d 83 3f 5b 5f 0a c6 b2 13 d5 7b 5f 1c b5 18 dc + d4 34 4b b0 b2 1c a6 84 ba 97 d3 4c 17 f8 92 cd 8d 92 44 64 37 c1 0f 54 af d1 54 b3 20 c1 06 0a de + a3 0f b0 97 33 53 70 57 7a 4c 3d 7f 7f b5 2d 06 d6 5d a8 0e 90 6c f5 a8 d9 0c c0 40 db c0 38 + d7 f8 22 52 05 97 76 b6 f2 65 90 cd b6 ae 5b 34 c8 08 86 ee da a4 18 e9 d6 60 1f 59 24 df 16 71 99 + 02 c7 e2 d4 56 4e 32 f7 57 8f cb 55 75 18 9a 97 44 2c 9a 36 cf 58 d9 e6 c8 66 cf a1 28 98 b0 46 f7 + 83 2c + +#### **IN** when computing $f_1^*$ : + +``` + +62 ff 5e a5 65 61 7d 3e bc 48 cd ae 76 a9 aa f3 e8 23 f2 89 bb 3c aa 47 8a a2 32 15 e4 52 60 3c 89 +30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 7d 29 41 3a 1f b7 9b c8 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +#### **OUT** when computing $f_1^*$ : + +15 cb ac 66 2e 1e 02 c6 a0 8d 88 13 f1 23 34 c7 bb f6 0e 14 55 9b d3 d6 73 a5 ea 4d c5 98 e9 63 dd + ec bf 5e c0 fb 55 7f 5f bd 41 ca 30 2b f7 31 0c 9b 35 64 ae 7b 48 86 69 fd 3a d8 5d 86 e4 e7 46 07 + 05 e3 8e 7d 0c 5f 56 4a 6a 5f ce 85 7b 1d 68 11 98 ab ca ed 76 72 e5 b6 4d 1b 3e 0b 36 51 73 d9 dc + 24 10 72 f5 a5 fb fa 49 1b 07 a8 3e d8 1f 8b b6 22 3d 29 d2 71 ce 91 01 e5 0c 34 0c e4 9e 65 ea 5f + ad d6 38 05 ba ba c3 e5 4c b4 34 46 93 6b 1e 17 3f c6 a9 f5 bc 38 5d 37 68 90 b8 6b 8c 2f 4a 66 a1 + 75 8f 17 a0 9c 2e d8 8d 79 0d 59 9a 03 15 27 6e 66 17 33 cf 33 7c d4 8d 22 b1 09 50 46 eb f0 73 a4 + 82 24 + +## 6.8 Test set 6 + +### Input Parameters: + +K: 1574ca56881d05c189c82880f789c9cd4244955f4426aa2b69c29f15770e5aa5 + RAND: c570aac68cde651fb1e3088322498bef + SQN: c89bb71f3a41 + AMF: 297d + +### Operator Configuration Parameters: + +TOP: e59f6eb10ea406813f4991b0b9e02f181edf4c7e17b480f66d34da35ee88c95e + Klength = 256 bits, MAClength = 256 bits, KeccakIterations = 2 + TOPc: b04a66f26c62fcd6c82de22a179ab65506ecf47f56245cd149966cfa9cec7a51 + +### Output Parameters: + +``` +f1: 90d2289ed1ca1c3dbc2247bb480d431ac71d2e4a7677f6e997cfddb0cbad88b7 +f1*: 427355dbac30e825063aba61b556e87583abac638e3ab01c4c884ad9d458dc2f +``` + +### Intermediate Values: + +#### **IN** when computing TOPc: + +``` +5e c9 88 ee 35 da 34 6d f6 80 b4 17 7e 4c df 1e 18 2f e0 b9 b0 91 49 3f 81 06 a4 0e b1 6e 9f e5 01 +30 2e 31 4b 41 55 54 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +#### **OUT/IN** after one Keccak iteration, when computing TOPc: + +``` +62 ff 5e a5 65 61 7d 3e bc 48 cd ae 76 a9 aa f3 e8 23 f2 89 bb 3c aa 47 8a a2 32 15 e4 52 60 3c 43 +f5 71 a5 ba 6c 9d 75 07 6f 91 9a b5 a5 4c d7 78 70 f9 b7 8d 11 f2 61 41 78 05 1e d8 ba a8 cd 6e 09 +df 81 0a 0a b1 1f 3d 73 47 e5 77 d9 b3 fc 93 75 6e ef 30 fd 3d 8a 38 9a 80 ad 11 97 2f 07 a8 fe f8 +22 43 46 74 bd 13 f2 ef 33 54 45 2f 2e c9 b0 91 b3 1b 51 e3 11 29 ab 2a 70 54 96 ff c9 ce ee e8 7e +08 ea 5a 75 44 fd ce 57 08 ea 7b 2d a1 c2 a9 15 bc 2a 48 cd a1 58 2d 05 6e 6e 25 c7 48 24 7a 6e 95 +66 6d e3 24 de 09 24 72 4d 20 ae 2a ce d6 e0 5b ea 53 22 91 27 96 3f b9 4f 72 28 85 02 cb a6 94 95 +1c 0f +``` + +#### **OUT** after second Keccak iteration, when computing TOPc: + +``` +51 7a ec 9c fa 6c 96 49 d1 5c 24 56 7f f4 ec 06 55 b6 9a 17 2a e2 2d c8 d6 fc 62 6c f2 66 4a b0 5f +93 fc cc 52 f0 45 26 53 4e 5f 33 9f ec 28 68 9d 6b 24 10 d4 ef 31 27 6d f1 28 30 88 bc 84 4d e3 18 +44 5b dc c3 f1 07 43 37 b8 b5 fd c5 e0 dd dd 91 04 aa 78 b3 38 64 72 7d 46 13 78 38 35 fa 09 61 77 +d8 db 1c 3b c3 4b 96 e9 23 ed 3f af 4a ec fc 8e f4 e0 a1 52 90 44 40 07 e4 1b 2d 53 47 11 e4 +79 c6 bd a0 1a 35 96 0f 03 a3 78 17 bf a6 85 ad 3a 43 d1 46 45 98 da b6 9a 54 e4 56 5d 0b 5b 71 3a +c8 f8 7c e7 d7 b6 2d a8 db 9c 87 72 e8 2c 07 12 2c 95 61 6c ee 1b 03 3f 2b 77 20 c1 2c 65 a7 4d 45 +67 ac +``` + +#### **IN** when computing f1: + +``` +51 7a ec 9c fa 6c 96 49 d1 5c 24 56 7f f4 ec 06 55 b6 9a 17 2a e2 2d c8 d6 fc 62 6c f2 66 4a b0 21 +30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 7d 29 41 3a 1f b7 9b c8 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +#### **OUT/IN** after one Keccak iteration, when computing f1: + +26 52 3f 89 99 46 a9 85 f3 76 19 e7 38 9b 7e 42 e7 ab ff ff 8c 82 cb 1b 0f 22 5f 1d 64 29 a3 36 e2 +22 63 bb 8b ee 5a c0 b4 b6 04 9d 77 54 69 a3 5c 21 42 a5 0d d6 28 4d 83 be 05 57 50 3c 5f 55 0d 18 +30 26 ef e3 4b c9 d7 c9 2f 62 8c 25 95 e3 00 61 3d c1 df db a7 1c 18 87 22 18 12 e4 53 27 1d 98 20 +eb a0 cb 01 34 59 18 58 b0 db ed 7f 54 f1 4f 5f 43 78 6c 44 38 9d a8 26 b6 34 41 1e 28 98 6f a6 7d +16 6d f2 84 90 b4 29 e9 06 b0 9f 3d 09 dc d6 d9 9f 8f 3d a8 b7 14 40 4e 7e 07 e9 dc d4 fd 36 a9 fa +76 4e bc a7 0f cd 6f 12 46 fe 82 67 23 ab 3f 17 94 e1 56 82 b9 48 b9 08 00 2c cc c1 7b ef 4d c9 70 +57 e9 + +#### **OUT** after second Keccak iteration, when computing f1: + +b7 88 ad cb b0 dd cf 97 e9 f6 77 76 4a 2e 1d c7 1a 43 0d 48 bb 47 22 bc 3d 1c ca d1 9e 28 d2 90 f3 +69 1a f6 7f 10 1f 51 d8 d6 91 9c 19 55 1d 80 28 97 a8 e1 d6 11 68 70 01 39 24 28 7e b8 b8 c4 54 0f +2e 02 c7 08 cd 6d 56 5a 2a 7f 42 77 c7 7b c5 dd cb 2d 8f f5 a2 02 76 d1 0b da 13 f0 ac 06 76 05 14 +fc 7a d5 b7 30 a7 76 22 6b d5 b0 e6 e5 b7 47 d5 03 af b3 a1 64 f9 b1 f0 b5 aa 13 99 8c fd a4 69 b0 +7a a6 0c 0c 1c 25 ed b1 d1 bb bb 15 40 3a bf fc 83 b5 c3 87 7a 2f 65 82 1f 41 97 06 8f 13 f1 7f fb +fa 92 72 3d 47 63 86 45 6c 61 4c c9 30 93 1c f7 73 52 24 7c 20 96 f8 95 aa 1c b1 63 44 74 db f4 0c +a1 47 + +#### **IN** when computing f1\*: + +51 7a ec 9c fa 6c 96 49 d1 5c 24 56 7f f4 ec 06 55 b6 9a 17 2a e2 2d c8 d6 fc 62 6c f2 66 4a b0 a1 +30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 7d 29 41 3a 1f b7 9b c8 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +#### **OUT/IN** after one Keccak iteration, when computing f1\*: + +24 76 d2 da c5 9e 2e 93 49 df 32 55 a9 da b1 b6 9e b5 c2 08 f1 51 c7 30 9e 8c 8f 17 db 45 6d 0b 5e +b0 af b6 c7 3e 37 ce 8c cc cf 20 b7 9d 8a 67 29 41 49 17 48 09 e4 29 70 93 30 c4 ad 23 1d 3e 52 11 +ae 0b d8 05 20 c4 3a d4 b4 36 62 57 92 a7 6c 52 08 9d 0f 73 92 71 15 1a 37 59 4d f6 6d e4 42 9f 3c +97 0a 34 56 b6 ce 2c 78 cd 11 28 71 7f 4b db 73 1a 4c 97 db e5 eb 73 53 fe 81 e3 7c 33 ac 60 b8 21 +22 ea c6 11 a9 8e 0e 74 42 b9 99 64 75 22 93 e4 f9 c6 96 ba 05 f0 7a 21 45 1f 90 73 0c 96 78 c6 45 +ad 4b e4 4c 4d 2d 98 1a 34 12 08 1c 9c 6b 05 c9 93 ff 1c 56 1a 0d 24 2b 47 06 d5 01 c3 47 65 b3 7a +0b 50 + +#### **OUT** after second Keccak iteration, when computing f1\*: + +2f dc 58 d4 d9 4a 88 4c 1c b0 3a 8e 63 ac ab 83 75 e8 56 b5 61 ba 3a 06 25 e8 30 ac db 55 73 42 86 +64 6f 87 18 9b 43 54 25 b5 d6 65 4e 22 82 28 b6 97 b8 1c be ad 65 5b 71 aa cc c2 5e 3d 7e 51 b5 cb +5a c2 27 f6 7f 2a d8 a0 62 97 67 82 b0 8a 7e c3 f1 b5 38 d6 00 8c 0b ab ef 83 da 64 36 6b 62 a5 3f +88 a3 dc 06 29 bd ed 79 5f 32 20 f3 c6 5c 76 bd d0 12 43 e8 8f 63 d6 91 2e 5f b5 cd a1 67 b7 1f 9b +aa a7 42 dc 19 3f f7 8c 17 67 a3 8a 1c 96 40 8c ce 16 92 39 b0 77 f2 90 3a 07 b8 c4 6a 04 8d 66 31 +8e 59 5e a4 bb 92 99 2c 7c 2d 3d cd 38 19 75 b6 e0 5f 85 ba 18 15 20 96 cc 30 ed 22 14 0f f3 b6 71 +1e a7 + +*Note that this final iteration corresponds to Test Set 1 for Keccak include 5.3.* + +# --- 7 Algorithms f2, f3, f4, f5 and f5\* + +## 7.1 Overview + +The test data sets presented here are for the algorithms *f2, f3, f4, f5, f5\**. Inputs and outputs to the permutation $\Pi$ are also presented here to assist with the implementation. + +## 7.2 Format + +Each test starts by showing the inputs K and RAND to the functions. Next are shown the operator configuration field TOP, and other operator configuration parameters: the length of the K, the length of the outputs CK, IK and RES, and the number of Keccak iterations. + +These are followed by the value of TOPC and then the output values of *f2-f5* and *f5\** are shown. The value TOPC should not be computed on but off the UICC. In the example code TOPC is computed inside the functions, so it was included in the test data. + +All the input, output and configuration parameters are presented using the bit/byte ordering convention described in clause 4.3. Intermediate inputs and outputs to the permutation $\Pi$ are also shown, as lists of 200 bytes, using the convention described in clause 5.2. + +## 7.3 Test set 1 + +### Input Parameters: + +K:            abababababababababababababababababab +RAND:       42424242424242424242424242424242 + +### Operator Configuration Parameters: + +``` +TOP: 5555555555555555555555555555555555555555555555555555555555555555 +Klength = 128 bits, CKlength = 128 bits, IKlength = 128 bits, +RESLength = 32 bits, KeccakIterations = 1 +TOPc: bd04d9530e87513c5d837ac2ad954623a8e2330c115305a73eb45d1f40cccbff +``` + +### Output Parameters: + +``` +f2: 657acd64 +f3: d71a1e5c6caffe986a26f783e5c78be1 +f4: be849fa2564f869aecee6f62d4337e72 +f5: 719f1e9b9054 +f5*: e7af6b3d0e38 +``` + +### Intermediate Values: + +As for Test Set 1 in clause 6.3, when computing TOPc. + +#### **IN** when computing f2-f5: + +``` +ff cb cc 40 1f 5d b4 3e a7 05 53 11 0c 33 e2 a8 23 46 95 ad c2 7a 83 5d 3c 51 87 0e 53 d9 04 bd 40 +30 2e 31 4b 41 55 54 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 00 00 00 00 00 00 00 ab ab +ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 +``` + +**OUT** when computing f2-f5: + +``` + +64 cd 7a 65 43 ac 5e 7a a6 f8 d1 82 ec 01 84 d9 16 97 5e 5e fc 3b 0b c7 87 80 f7 f0 94 db 05 1a e1 +8b c7 e5 83 f7 26 6a 98 fe af 6c 5c 1e 1a d7 13 32 e5 90 c7 72 8f 04 0e db e9 a9 8a 52 1c e2 72 7e +33 d4 62 6f ee ec 9a 86 4f 56 a2 9f 84 be f6 7b f6 1a 31 a8 cd 73 76 a5 40 02 bd ae f1 f0 54 90 9b +1e 9f 71 33 52 f1 8b e8 b5 f0 37 71 57 45 62 92 1a 4d 74 b5 76 12 8c d9 b3 53 ee 4b 9a 16 ff 6a aa +e8 09 5d 35 57 da cd ee 0b ad c1 99 b4 c5 ff 80 7f 77 61 5f b4 4a ce 33 d2 5e de 8e 19 44 39 f2 e5 +37 88 6c ad 0a cd 41 02 1e a0 61 7c 2c 6a 78 ff 46 b5 c9 68 28 0c bb 6a 29 52 2e 53 c2 99 16 9a 61 +73 8b + +``` + +**IN** when computing $f5^*$ : + +``` + +ff cb cc 40 1f 5d b4 3e a7 05 53 11 0c 33 e2 a8 23 46 95 ad c2 7a 83 5d 3c 51 87 0e 53 d9 04 bd c0 +30 2e 31 4b 41 55 54 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 42 00 00 00 00 00 00 00 ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +``` + +**OUT** when computing f5\*: + +``` + +46 6b 1d bd 30 d3 3e 41 a9 65 b0 17 b1 63 d5 aa 3f 75 7f 65 ec 81 5b e0 e1 f1 97 5b c9 a0 70 61 64 +00 8c 8c 02 08 71 70 e0 52 e8 bf ab d5 cf 67 b0 dc d0 cb 94 e7 a7 08 20 7d 40 f7 ef 2e 86 bf 81 99 +e2 8f 0e bd 1f a1 b8 48 97 a5 24 31 72 61 6f 4c 2c 69 18 66 76 78 92 e2 87 13 c1 9e 82 38 0e 3d +6b af e7 fb 66 1a 2e 97 4a bf f0 6d 7f 94 a5 ec 1b 8e ef 46 3e 11 b6 e0 59 77 19 ae 7d 27 f5 f9 5e +6b 38 5d 68 c2 2d 8a 60 32 2b de 04 0d 82 46 6e 39 cf ec ac 6c b7 cc cc 1e 8d fd 1b 87 9a ff 29 72 +67 b1 70 11 b7 44 9b eb 28 99 e9 7e 36 9f a6 17 13 a9 1f c7 d4 1e 91 fe 4a 46 a0 a3 e9 b9 38 5b c8 +56 9b + +``` + +## 7.4 Test set 2 + +### Input Parameters: + +K: fffefdfcfbfaf9f8f7f6f5f4f3f2f1f0feeedecebeae9e8e7e6e5e4e3e2e1e0 + RAND: 0123456789abcdef0123456789abcdef + +### Operator Configuration Parameters: + +TOP: 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f + Klength = 256 bits, CKlength = 128 bits, IKlength = 128 bits, + RESLength = 64 bits, KeccakIterations = 1 + TOPc: 305425427e18c503c8a4b294ea72c95d0c36c6c6b29d0c65de5974d5977f8524 + +### Output Parameters: + +f2: e9d749dc4eea0035 + f3: a4cb6f6529ab17f8337f27baa8234d47 + f4: 2274155ccf4199d5e2abcbf621907f90 + f5: 480a9345cc1e + f5\*: f84eb338848c + +### Intermediate Values: + +As for Test Set 2 in clause 6.4, when computing TOPc. + +#### IN when computing f2-f5: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 49 + 30 2e 31 4b 41 55 54 ef cd ab 89 67 45 23 01 ef cd ab 89 67 45 23 01 00 00 00 00 00 00 00 00 00 00 + e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing f2-f5: + +35 00 ea 4e dc 49 d7 e9 ec 66 ca 43 7c c7 37 70 f9 06 35 f0 2c f3 99 02 fa a5 f7 4d 38 c5 7f 84 47 + 4d 23 a8 ba 27 7f 33 f8 17 ab 29 65 6f cb a4 41 fd a2 ba f5 a3 45 0b b0 c5 0f 29 2b 3b ca 35 90 7f + 90 21 f6 cb ab e2 d5 99 41 cf 5c 15 74 22 5f 68 0a 9d 4e a5 e1 20 e5 8c 28 a2 fa ad 50 34 1e cc 45 + 93 0a 48 1b 99 ad 40 f6 06 d7 f4 12 47 88 d6 b6 fe 66 da 8c 9d 53 8a 21 ad 08 f7 c0 cc 61 34 1d 4c + 60 ff 16 af 27 d4 b3 89 ec b5 5c 0e 7e 1e 7f ed e7 b8 0b 37 e0 17 8f 86 8c eb b9 12 63 bc c1 72 6e + 8e 66 25 e4 5e 83 1e 79 35 9b f4 b8 c2 8e 88 26 f1 fb 5b 8b b4 82 1a 5e 76 13 fb 48 32 11 87 80 5a + 40 31 + +#### IN when computing f5\*: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 c1 + 30 2e 31 4b 41 55 54 ef cd ab 89 67 45 23 01 ef cd ab 89 67 45 23 01 00 00 00 00 00 00 00 00 00 00 + e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing f5\*: + +2b 8b b3 71 5f 6f 3d a7 0a 69 56 67 60 93 cd 86 85 2f b8 d1 69 c8 34 65 1d 0c 76 cd 31 7c de 24 be + 03 de e6 a0 0e 01 56 32 7c 8c 71 f4 e3 88 8d f6 a3 77 c8 00 aa 33 c5 29 5c bb e5 81 62 10 23 26 bd + 89 79 9c 69 96 3f ab e6 d0 76 16 06 0e 36 d1 09 9d a1 b7 69 c2 7e cd e5 7d 87 d6 a7 1f 01 8c 84 38 + b3 4e f8 e4 ad cd 1a a9 fe 7a 61 3c e6 ba 5e 0b 79 d7 0d 22 7f 33 9e 6a 3d fb 3d f5 fa 94 5e 98 10 + 36 b0 91 13 6f 96 90 e2 d4 79 d4 6d 31 d3 9b f4 10 75 08 e4 b5 8a 9b e6 e5 d0 0a 48 e4 c0 67 51 93 + 06 b7 3f 5b a3 dd 23 50 76 ac 1d 55 42 5e 6e f9 e3 f7 20 3c 47 0a 98 32 18 b1 2a c9 f4 d6 b9 05 9a + 02 5e + +## 7.5 Test set 3 + +### Input Parameters: + +K: fffefdfcfbfaf9f8f7f6f5f4f3f2f1f0feeedecebeae9e8e7e6e5e4e3e2e1e0 + RAND: 0123456789abcdef0123456789abcdef + +### Operator Configuration Parameters: + +TOP: 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f + Klength = 256 bits, CKlength = 128 bits, IKlength = 256 bits, + RESLength = 64 bits, KeccakIterations = 1 + +TOPc: 305425427e18c503c8a4b294ea72c95d0c36c6c6b29d0c65de5974d5977f8524 + +### Output Parameters: + +f2: 07021c73e7635c7d +f3: 4d59ac796834eb85d11fa148a5058c3c +f4: 126d47500136fdc5ddfd14f19ebf16749ce4b6435323fbb5715a3a796a6082bd +f5: 1d6622c4e59a +f5\*: f84eb338848c + +### Intermediate Values: + +As for Test Set 2 in clause6.4, when computing TOPc. + +#### IN when computing f2-f5: + +24 85 7f 97 d5 74 59 de 65 0c 9d b2 c6 c6 36 0c 5d c9 72 ea 94 b2 a4 c8 03 c5 18 7e 42 25 54 30 4b +30 2e 31 4b 41 55 54 ef cd ab 89 67 45 23 01 ef cd ab 89 67 45 23 01 00 00 00 00 00 00 00 00 e0 e1 +e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee ef f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +#### OUT when computing f2-f5: + +7d 5c 63 e7 73 1c 02 07 12 5c 5e fe bf 31 b4 c9 22 52 ed 1e 96 2a 98 3f 87 bf 79 3b 1a d0 93 43 3c +8c 05 a5 48 a1 1f d1 85 eb 34 68 79 ac 59 4d ac 21 e8 b7 cd 87 d5 57 a0 b4 19 c4 67 2c 74 ef bd 82 +60 6a 79 3a 5a 71 b5 fb 23 53 43 b6 e4 9c 74 16 bf 9e f1 14 fd dd c5 fd 36 01 50 47 6d 12 9a e5 c4 +22 66 1d 2c 03 c8 d4 c3 e9 59 a9 6e a8 cb d2 8a 81 4a 18 8b 2f a6 c1 c6 f1 44 2f 96 5e af ab 93 11 +03 74 83 39 1f 3c 39 2f 3a 05 a9 43 3c 11 de 27 eb 6f 67 4d 98 7a 90 ad f1 74 8c 26 f3 65 fc 69 75 +e3 b8 8b d2 33 48 f2 20 3b 60 f7 f6 82 78 e6 7a 35 d2 e7 28 fb 2f 7d 52 08 ce 11 9e 40 44 30 6e e7 +24 3e + +As for Test Set 2 in clause7.4, when computing f5\*. + +## 7.6 Test set 4 + +### Input Parameters: + +K: b8da837a50652d6ac7c97da14f6acc61 +RAND: 6887e55425a966bd86c9661a5fa72be8 + +### Operator Configuration Parameters: + +TOP: 0952be13556c32ebc58195d9dd930493e12a9003669988ffde5fa1f0fe35cc01 +Klength = 128 bits, CKlength = 128 bits, IKlength = 128 bits, +RESLength = 128 bits, KeccakIterations = 1 +TOPc: 2bc16eb657a68elf446f08f57c0efb1d493527a2e652ce281eb6ca0e4487760a + +### Output Parameters: + +f2: 4041ce438e3e38e8aa96562eed83ac43 +f3: 3e3bc01bea0cd914c4c2c83ce2d92757 +f4: 666a8e6f577b1aa77b7fd53cebb8a3d6 +f5: 1f880d005119 +f5\*: 45e617d77fe5 + +### Intermediate Values: + +As for Test Set 4 in clause 6.6, when computing TOPc. + +#### IN when computing f2-f5: + +0a 76 87 44 0e ca b6 1e 28 ce 52 e6 a2 27 35 49 1d fb 0e 7c f5 08 6f 44 1f 8e a6 57 b6 6e c1 2b 50 +30 2e 31 4b 41 55 54 e8 2b a7 5f 1a 66 c9 86 bd 66 a9 25 54 e5 87 68 00 00 00 00 00 00 00 00 61 cc +6a 4f a1 7d c9 c7 6a 2d 65 50 7a 83 da b8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +#### OUT when computing f2-f5: + +43 ac 83 ed 2e 56 96 aa e8 38 3e 8e 43 ce 41 40 33 d3 16 49 0b ac 6f 15 ad 56 87 1e b8 d4 7b 3d 57 +27 d9 e2 3c c8 c2 c4 14 d9 0c ea 1b c0 3b 3e ee 84 85 d7 7f a4 c8 a2 c6 9b c1 37 79 b4 26 19 d6 a3 +b8 eb 3c d5 7f 7b a7 1a 7b 57 6f 8e 6a 66 5c 4c 99 c0 ad 5c 93 b3 ad d9 8f 5f 62 e6 eb 74 19 51 00 +0d 88 1f ed ff 87 53 22 88 56 a3 e5 3d 8b 03 5c a1 06 78 c8 9a 69 24 05 3a a9 87 67 72 19 a0 5f b3 +55 9a 72 66 b0 47 17 9d 7e 45 1a 78 a3 cf ed b7 4f 43 21 66 49 63 c4 62 ba c6 c3 61 78 88 c9 00 86 +e0 46 fb 17 f6 2f 8e 6d 97 09 2d f6 8e 93 a4 a0 d2 f4 c3 2b 8a 3d 73 d1 13 94 27 4b 2b 16 ae db db +bc 8d + +#### IN when computing f5\*: + +0a 76 87 44 0e ca b6 1e 28 ce 52 e6 a2 27 35 49 1d fb 0e 7c f5 08 6f 44 1f 8e a6 57 b6 6e c1 2b c0 +30 2e 31 4b 41 55 54 e8 2b a7 5f 1a 66 c9 86 bd 66 a9 25 54 e5 87 68 00 00 00 00 00 00 00 00 61 cc +6a 4f a1 7d c9 c7 6a 2d 65 50 7a 83 da b8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +#### OUT when computing f5\*: + +d1 72 29 2f 8e 08 be 5b 00 a2 ac d3 7f 51 00 0c e5 8d ad a9 84 9b 7f 76 94 0c 10 40 88 8b 64 d8 05 +7d 45 2e 0a e7 f8 0f 93 3a 79 13 f3 72 23 13 fc 24 b5 63 27 29 b9 b1 10 59 bf 17 e7 b9 38 ed cc bc +67 26 cd ea 48 3d 8a 69 01 49 1a b6 b3 c4 f0 a7 59 e6 fb ac e5 55 4b f9 ad 9e 8e 91 59 34 e5 7f d7 +17 e6 45 47 b6 2d fb 8c c6 af ac 46 76 2e 07 95 ba 5b c2 aa 9f bd 48 e2 e8 14 cb 7a 17 99 58 d3 ed +97 74 e9 ea be 89 82 83 c1 06 6d 34 d7 fc ee 51 75 66 4c aa 21 f1 16 d3 24 69 b2 3d 6c e1 7c f5 34 +9b 66 ac dd 64 ae 6c 25 1f 6a c6 a9 23 60 93 bd 59 97 1c 25 9f 87 1b 88 6a a1 b8 07 94 e2 a7 3f f2 +0b 21 + +## 7.7 Test set 5 + +### Input Parameters: + +K: 1574ca56881d05c189c82880f789c9cd4244955f4426aa2b69c29f15770e5aa5 +RAND: c570aac68cde651fb1e3088322498bef + +### Operator Configuration Parameters: + +TOP: e59f6eb10ea406813f4991b0b9e02f181edf4c7e17b480f66d34da35ee88c95e +Klength = 256 bits, CKlength = 256 bits, IKlength = 128 bits, +RESLength = 256 bits, KeccakIterations = 1 + +TOPc: 3c6052e41532a28a47aa3cbb89f223e8f3aaa976aeecd48bc3e7d6165a55eff62 + +### Output Parameters: + +f2: 84d89b41db1867ffd4c7ba1d82163f4d526a20fbae5418fbb526940b1eeb905c + f3: d419676afe5ab58c1d8bee0d43523a4d2f52ef0b31a4676a0c334427a988fe65 + f4: 205533e505661b61d05cc0eac87818f4 + f5: d7b3d2d4980a + f5\*: ca9655264986 + +### Intermediate Values: + +As for Test Set 5 in clause 6.7, when computing TOPc. + +#### IN when computing f2-f5: + +62 ff 5e a5 65 61 7d 3e bc 48 cd ae 76 a9 aa f3 e8 23 f2 89 bb 3c aa 47 8a a2 32 15 e4 52 60 3c 65 + 30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 00 00 00 00 00 00 00 00 a5 5a + 0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing f2-f5: + +5c 90 eb 1e 0b 94 26 b5 fb 18 54 ae fb 20 6a 52 4d 3f 16 82 1d ba c7 d4 ff 67 18 db 41 9b d8 84 65 + fe 88 a9 27 44 33 0c 6a 67 a4 31 0b ef 52 2f 4d 3a 52 43 0d ee 8b 1d 8c b5 5a fe 6a 67 19 d4 f4 18 + 78 c8 ea c0 5c d0 61 1b 66 05 e5 33 55 20 77 dc 33 69 95 08 62 22 b2 11 98 a1 ed d9 50 7c 0a 98 d4 + d2 b3 d7 c0 31 b7 7e 47 3c 45 8b 01 ed 35 bf 2a 3f 33 2f 94 e6 e0 46 7b 48 5e 51 e5 e5 d6 9b 28 + 62 dc a1 2f ac 4a 9a e3 e8 81 13 f1 d2 6e bd df b6 6f ae 2c 61 ca ca 17 0d a3 58 02 32 b4 e0 02 ba + 4a fe f8 42 f8 05 8b 2a eb 60 f0 74 52 92 13 2c b2 42 a0 c5 96 da c0 5f 68 d9 8f b0 f5 32 ee d5 eb + 5c a3 + +#### IN when computing f5\*: + +62 ff 5e a5 65 61 7d 3e bc 48 cd ae 76 a9 aa f3 e8 23 f2 89 bb 3c aa 47 8a a2 32 15 e4 52 60 3c c1 + 30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 00 00 00 00 00 00 00 00 a5 5a + 0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + 00 00 + +#### OUT when computing f5\*: + +b1 ef 6c a0 a5 a4 8b 08 fc c2 f1 84 39 77 3b f2 ee e8 f4 b8 95 25 8b 14 ce 08 2f cf 16 06 2b 76 09 + 8d 73 9e c2 68 3e c1 94 1d 61 bc 58 7c 8d f2 c2 b6 86 ef 05 d9 a3 8c d2 a2 6c fc e6 4e 81 3d cf e4 + 05 a5 5b 51 0c a8 a1 89 9f 63 4b c6 a3 89 a4 64 1a 93 9b 16 30 2e 17 06 86 02 6e a3 09 0a 86 49 26 + 55 96 ca 5f 7f e1 89 a7 06 c0 12 4d ae 0a 24 73 fc f3 d4 61 92 5a b4 a2 28 f4 22 ec b4 7c 24 5d b0 + 68 14 08 15 ba 72 96 de 53 07 cb f2 51 a5 34 80 bc c8 ae f5 1a 99 73 e6 75 51 bc 79 8f 78 1f f1 71 + 1d 65 01 6f e9 b3 6f 04 99 e5 cc 4c 86 fe a1 a8 bd 21 b9 fe 22 92 31 f4 18 8e fd fb 0f f4 04 18 0a + 88 f4 + +## 7.8 Test set 6 + +### Input Parameters: + +K: 1574ca56881d05c189c82880f789c9cd4244955f4426aa2b69c29f15770e5aa5 + RAND: c570aac68cde651fb1e3088322498bef + +### Operator Configuration Parameters: + +TOP: e59f6eb10ea406813f4991b0b9e02f181edf4c7e17b480f66d34da35ee88c95e + Klength = 256 bits, CKlength = 256 bits, IKlength = 256 bits, + RESLength = 256 bits, KeccakIterations = 2 + TOPc: b04a66f26c62fcd6c82de22a179ab65506ecf47f56245cd149966cfa9cec7a51 + +### Output Parameters: + +f2: d67e6e64590d22eeba7324afa4af4460c93f01b24506d6e12047d789a94c867 + f3: ede57edfc57cdffe1aae75066a1b7479bbc3837438e88d37a801cccc9f972b89 + f4: 48ed9299126e5057402fe01f9201cf25249f9c5c0ed2afcf084755daff1d3999 + f5: 6aae8d18c448 + f5\*: 8c5f33b61f4e + +### Intermediate Values: + +As for Test Set 6 in clause 6.8, when computing TOPc. + +#### **IN** when computing f2-f5: + +51 7a ec 9c fa 6c 96 49 d1 5c 24 56 7f f4 ec 06 55 b6 9a 17 2a e2 2d c8 d6 fc 62 6c f2 66 4a b0 67 +30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 00 00 00 00 00 00 00 00 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +#### **OUT/IN** after one Keccak iteration, when computing f2-f5: + +45 de 3d d1 50 4d 7c 3b b7 32 1a a8 2e c4 5a bc ed 2b b0 6d 4c 56 ef 84 7f 53 c3 95 2b 76 75 e9 6b +d8 d6 a6 f1 0f 25 83 65 cb c7 2d 71 f1 bf ae 8f 9f 1a b8 04 92 fb 03 50 db 45 d4 4c 16 c9 f3 4d 38 +d8 fa c1 3c 8a 92 4a bd 97 d1 79 fa 28 b6 04 1a ca 29 6b 86 03 bb af f8 ac a2 d5 4c fd f5 a9 80 b1 +7b 93 6f fe 6c 63 80 5a 8a c8 5f 07 e2 ba 9c 76 df 61 65 3c 1f ec 15 55 93 cd eb 05 61 73 7c ca b3 +86 d0 c0 5b 5a 2e b9 29 c9 d4 d3 9e fc 63 38 83 77 06 f4 8a ab ab a2 69 a1 d9 ff 42 d2 f3 ef 01 bd +7f 27 15 2c a2 a7 32 54 02 3b 99 d1 cb b6 6b 88 eb 6e 2a 36 93 fd 56 48 e1 3d 81 9b 5f 2a 00 65 ca +8b 13 + +#### **OUT** after second Keccak iteration, when computing f2-f5: + +67 c8 94 9a 78 7d 04 12 6e 6d 50 24 1b f0 93 0c 46 f4 4a fa 4a 32 a7 cb ee 22 0d 59 64 6e 7e d6 89 +2b 97 9f cc cc 01 a8 37 8d e8 38 74 83 c3 bb 79 74 1b 6a 06 75 ae 1a fe df 7c c5 df 7e e5 ed 99 39 +1d ff da 55 47 08 cf af d2 0e 5c 9c 9f 24 25 cf 01 92 1f e0 2f 40 57 50 6e 12 99 92 ed 48 48 c4 18 +8d ae 6a ae 10 c1 1d 8d 25 00 c7 d0 95 53 8b 9e dc 42 6b 7b 0b ba 58 d4 15 a2 01 62 d6 41 42 b9 eb +9e af 5b 40 0f 17 bd a3 3f a3 da f8 a2 b3 bf a3 a1 b4 b7 54 53 69 83 2e 0b 94 da 31 93 81 d1 26 9a +c1 3c 26 a1 fe d0 dd 0a 66 0f f8 96 31 29 04 7e 2f 63 cd 4a 94 81 79 38 2e 4e db 4d 52 35 90 c7 87 +46 28 + +#### **IN** when computing f5\*: + +51 7a ec 9c fa 6c 96 49 d1 5c 24 56 7f f4 ec 06 55 b6 9a 17 2a e2 2d c8 d6 fc 62 6c f2 66 4a b0 c1 +30 2e 31 4b 41 55 54 ef 8b 49 22 83 08 e3 b1 1f 65 de 8c c6 aa 70 c5 00 00 00 00 00 00 00 00 a5 5a +0e 77 15 9f c2 69 2b aa 26 44 5f 95 44 42 cd c9 89 f7 80 28 c8 89 c1 05 1d 88 56 ca 74 15 1f 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +#### **OUT/IN** after one Keccak iteration, when computing f5\*: + +bf 66 e2 27 5d d6 6e 1c 15 82 da 5b ab b8 d6 dd 33 46 ff ca e0 c5 95 d9 08 22 7d f9 ec 75 2a ac c2 +d5 ef c8 70 11 12 7c 72 32 d6 82 83 20 39 df e3 a9 8b 4f 63 2f 5f e4 6b af 34 4f 21 7f e8 68 be 5e +61 d3 41 be e4 05 12 e6 0f d3 c1 70 0b 5a 34 47 47 7d 5b b5 b5 f5 ba 5e e4 c0 2b f6 f8 38 8f 8c cc +35 bf 79 fb c0 31 db 27 b8 0f c1 b1 43 14 d7 99 f5 0e 01 28 e4 23 fa db 72 cd de c2 a8 ee 1c 74 69 +53 cc d6 5f 94 19 24 62 b2 fb d6 91 e2 e5 5c 35 b3 e5 d1 59 a4 04 20 de d5 16 12 c0 96 64 f4 9b ea +aa ba 4e 1d 57 a5 ec 8c 0f 30 e3 59 2e b7 38 56 2b f7 e3 f9 0f a0 41 dc b1 4e d1 5d 0b 6c 5d 34 05 +94 98 + +#### **OUT** after second Keccak iteration, when computing f5\*: + +3f cb 12 cc 5c aa aa 1f ea 8e 1c 14 8e 67 4a 6f ee e5 fc 38 88 9a a1 7a b4 d8 85 68 14 02 d0 9a 55 +62 72 a7 99 99 4b 3b 9d 21 de b6 c5 5a 14 14 e1 a3 27 4d 75 c2 81 f6 15 7a 19 a4 d0 07 14 0d 52 35 +3c 38 a5 89 27 39 24 5e 64 fa 6b 00 01 1b ec 63 10 b2 3f 3c 3f 02 0a cd b5 df fb af 92 7d 4e 1f b6 +33 5f 8c 4a ef e0 d6 30 0a 8f f0 f9 34 68 0d a7 cf 7e 53 90 4b af f9 e8 1f 09 fa 0a 1f c6 2f 39 d3 +7d da 64 b3 d1 c3 10 fe d3 fe 08 1b ad 8e 09 ef a6 c1 e2 7f 1b 11 3c 8a fd bc be b2 14 4f 31 4e 2c +09 1c d9 e5 27 92 07 90 0e 33 43 86 ed e9 79 4a 38 ec f9 ae 90 5f 72 e0 9b 76 84 79 24 78 b4 1a db +e6 25 + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| Dec 2013 | | | | | Version after approval | 1.1.0 | 12.0.0 | +| Dec 2013 | | | | | Update of Introduction with spec numbers | 12.0.0 | 12.0.1 | +| June 2014 | SP-64 | SP-140316 | 001 | 2 | Overall editorial modification to the Tuak specification TS 35.232 | 12.0.1 | 12.1.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.1.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35233/raw.md b/marked/Rel-16/35_series/35233/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..65658eff3e08972737c3b482f1769cc6c89f120f --- /dev/null +++ b/marked/Rel-16/35_series/35233/raw.md @@ -0,0 +1,653 @@ + + + + + + +# Contents + +- Foreword ................................................................................................................................................................... 4 +- Introduction ............................................................................................................................................................... 4 +- 1 Scope......................................................................................................................................................... 5 +- 2 References.................................................................................................................................................. 5 +- 3 PRELIMINARY INFORMATION .......................................................................................................... 6 + - 3.1 Introduction ....................................................................................................................................... 6 + - 3.2 Radix ................................................................................................................................................. 6 + - 3.3 Bit/Byte ordering for TUAK inputs and outputs................................................................................ 6 + - 3.4 List of Variables ................................................................................................................................ 6 + - 3.5 TUAK Inputs and Outputs ................................................................................................................. 7 +- 4 CONFORMANCE TEST DATA FOR KECCAK ................................................................................. 9 + - 4.1 Overview ........................................................................................................................................... 9 + - 4.2 Format ............................................................................................................................................... 9 + - 4.3 Test Set 1 ......................................................................................................................................... 10 + - 4.4 Test Set 2......................................................................................................................................... 10 + - 4.5 Test Set 3......................................................................................................................................... 11 + - 4.6 Test Set 4......................................................................................................................................... 11 + - 4.7 Test Set 5......................................................................................................................................... 12 + - 4.8 Test Set 6......................................................................................................................................... 12 +- 5 CONFORMANCE TEST DATA FOR TUAK .................................................................................... 13 + - 5.1 Overview ......................................................................................................................................... 13 + - 5.2 Format ............................................................................................................................................. 13 + - 5.3 Test Set 1 ......................................................................................................................................... 13 + - 5.4 Test Set 2......................................................................................................................................... 14 + - 5.5 Test Set 3......................................................................................................................................... 14 + - 5.6 Test Set 4......................................................................................................................................... 15 + - 5.7 Test Set 5......................................................................................................................................... 16 + - 4.8 Test Set 6......................................................................................................................................... 16 +- Annex A (informative): Change history.................................................................................................................. 17 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The present document is third of three, which between them form the entire specification of the example algorithms, entitled: + +- 3GPP TS 35.231: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation Functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: algorithm specification ". +- 3GPP TS 35.232: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation Functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Implementers' test data". +- **3GPP TS 35.233: " Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Design conformance test data".** + +# 1 Scope + +The present document and the other Technical Specifications in the series, TS 35.231 [4] and TS 35.232 [5], contain an example set of algorithms which could be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\** for 3GPP systems. The present document provides sets of input/output test data for 'black box' testing of physical realizations of all algorithms, and in particular: + +- Test data for the Keccak permutation used within Tuak. +- Test data for the MILENAGE authentication and key generation algorithms *f1, f1\*, f2, f3, f4, f5* and *f5\**. + +# 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 33.102: "3G Security; Security Architecture". +- [2] 3GPP TS 35.206: "3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm specification". +- [3] "The KECCAK Reference", version 3.0, 14 January 2011, G. Bertoni, J. Daemen, M. Peeters, G. van Assche. +- [4] 3GPP TS 35.231: "Specification of the Tuak Algorithm Set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: algorithm specification ". +- [5] 3GPP TS 35.232: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Implementers' test data" +- [6] 3GPP TS 33.401: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture". + +# 3 Definitions + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Tuak:** The name of this algorithm set is "Tuak". It should be pronounced like "too-ack". + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----|---------------------------------------------------------------------------------------| +| AK | a 48-bit anonymity key that is the output of either of the functions f5 and f5* | +| AMF | a 16-bit authentication management field that is an input to the functions f1 and f1* | + +| | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CK | a 128-bit or 256-bit confidentiality key that is the output of the function f3 | +| IK | a 128-bit or 256-bit integrity key that is the output of the function f4 | +| IN | a 1600-bit value that is used as the input to the permutation $\Pi$ when computing the functions f1, f1*, f2, f3, f4, f5 and f5* | +| K | a 128-bit or 256-bit subscriber key that is an input to the functions f1, f1*, f2, f3, f4, f5 and f5* | +| MAC-A | a 64-bit, 128-bit or 256-bit network authentication code that is the output of the function f1 | +| MAC-S | a 64-bit, 128-bit or 256-bit resynchronization authentication code that is the output of the function f1* | +| TOP | a 256-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1, f1*, f2, f3, f4, f5 and f5* | +| TOPC | a 256-bit value derived from TOP and K and used within the computation of the functions | +| OUT | a 1600-bit value that is taken as the output of the permutation $\Pi$ when computing the functions f1, f1*, f2, f3, f4, f5 and f5* | +| RAND | a 128-bit random challenge that is an input to the functions f1, f1*, f2, f3, f4, f5 and f5* | +| RES | a 32-bit, 64-bit, 128-bit or 256-bit signed response that is the output of the function f2 | +| SQN | a 48-bit sequence number that is an input to either of the functions f1 and f1*. (For f1* this input is more precisely called SQNMS) See informative Annex C of [1] for methods of encoding sequence numbers. | + +# 3 Definitions + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Tuak:** The name of this algorithm set is "Tuak". It should be pronounced like "too-ack". + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AK | a 48-bit anonymity key that is the output of either of the functions f5 and f5* | +| AMF | a 16-bit authentication management field that is an input to the functions f1 and f1* | +| CK | a 128-bit or 256-bit confidentiality key that is the output of the function f3 | +| IK | a 128-bit or 256-bit integrity key that is the output of the function f4 | +| IN | a 1600-bit value that is used as the input to the permutation $\Pi$ when computing the functions f1, f1*, f2, f3, f4, f5 and f5* | +| K | a 128-bit or 256-bit subscriber key that is an input to the functions f1, f1*, f2, f3, f4, f5 and f5* | +| MAC-A | a 64-bit, 128-bit or 256-bit network authentication code that is the output of the function f1 | +| MAC-S | a 64-bit, 128-bit or 256-bit resynchronization authentication code that is the output of the function f1* | +| TOP | a 256-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1, f1*, f2, f3, f4, f5 and f5* | +| TOPC | a 256-bit value derived from TOP and K and used within the computation of the functions | +| OUT | a 1600-bit value that is taken as the output of the permutation $\Pi$ when computing the functions f1, f1*, f2, f3, f4, f5 and f5* | +| RAND | a 128-bit random challenge that is an input to the functions f1, f1*, f2, f3, f4, f5 and f5* | +| RES | a 32-bit, 64-bit, 128-bit or 256-bit signed response that is the output of the function f2 | +| SQN | a 48-bit sequence number that is an input to either of the functions f1 and f1*. (For f1* this input is more precisely called SQNMS) See informative Annex C of [1] for methods of encoding sequence numbers. | + +# 4 Preliminary information + +## 4.1 Introduction + +Within the security architecture of the 3GPP system there are seven security functions *f1, f1\*, f2, f3, f4, f5* and *f5\**. The operation of these functions falls within the domain of one operator, and the functions are therefore to be specified by each operator rather than being fully standardized. The algorithms specified in the present document are examples that may be used by an operator who does not wish to design his own. + +The inputs and outputs of all seven algorithms are defined in clause 4.4. + +## 4.2 Radix + +Unless stated otherwise, all test data values presented in the present document are in hexadecimal. + +## 4.3 Bit/Byte ordering for Tuak inputs and outputs + +3GPP TS 33.102 [1] includes the following convention. (There is similar text in the specification of MILENAGE, as defined in 3GPP TS 35.206 [2]): + +All data variables in the present document are presented with the most significant substring on the left hand side and the least significant substring on the right hand side. A substring may be a bit, byte or other arbitrary length bit string. Where a variable is broken down into a number of substrings, the left-most (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant. + +So, for example, RAND[0] is the most-significant bit of RAND and RAND[127] is the least significant bit of RAND. + +This convention applies to all **inputs** and **outputs** to Tuak, as listed in tables 1-9 below. + +However, when describing intermediate states of Tuak (e.g. inputs and outputs for the Keccak permutation), variables are simply treated as indexed bit strings. These bit strings will be presented in hexadecimal notation, using a display convention described in clause 5.2 . + +## 4.4 Tuak inputs and outputs + +The inputs to Tuak are given in tables 1 and 2, the outputs in tables 3 to 9 below. + +There are a few differences from the inputs and outputs to MILENAGE [2]. + +The key K may be 128 bits **or** 256 bits. MAC-A and MAC-S may be 64, 128 **or** 256 bits. RES may be 32, 64, 128 **or** 256 bits. CK and IK may be 128 **or** 256 bits. Existing 3GPP specification (see [1] and [7]) do not support all these possibilities, but they are included in Tuak for future flexibility in case future releases of these specifications support them. + +NOTE 1: The 3G security architecture specification [1] calls the output of the f1 function 'MAC' while the present document and [2] call it 'MAC-A'. + +Any sizes for the parameters K, MAC-A, MAC-S, RES, CK and IK mentioned in the present document shall not be supported nor used in entities defined in 3GPP specifications until these specifications explicitly allow their use. + +In any particular implementation, the parameters shall have a fixed length, chosen in advance. For example an operator may fix K at length 256 bits, RES at length 64 bits, CK and IK at length 128 bits. As the lengths do not vary with input, they are not specified as formal input parameters. + +**Table 1: Inputs to f1 and f1\*** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|---------------------------------------------------------------------------------------------------| +| K | 128 or 256 | Subscriber key K[0]...K[127] or K[0]...K[255] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | +| SQN | 48 | Sequence number SQN[0]...SQN[47] (for f1* this input is more precisely called SQN MS ) | +| AMF | 16 | Authentication management field AMF[0]...AMF[15] | + +**Table 2: Inputs to f2, f3, f4, f5 and f5\*** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|-----------------------------------------------| +| K | 128 or 256 | Subscriber key K[0]...K[127] or K[0]...K[255] | +| RAND | 128 | Random challenge RAND[0]...RAND[127] | + +**Table 3: f1 output** + +| Parameter | Size (bits) | Comment | +|-----------|----------------|----------------------------------------------------------------------------------------------------| +| MAC-A | 64, 128 or 256 | Network authentication code MAC-A[0]...MAC-A[63] or MAC-A[0]...MAC-A[127] or MAC-A[0]...MAC-A[255] | + +**Table 4: f1\* output** + +| Parameter | Size (bits) | Comment | +|-----------|----------------|----------------------------------------------------------------------------------------------------| +| MAC-S | 64, 128 or 256 | Resynch authentication code MAC-S[0]...MAC-S[63] or MAC-S[0]...MAC-S[127] or MAC-S[0]...MAC-S[255] | + +**Table 5: f2 output** + +| Parameter | Size (bits) | Comment | +|-----------|--------------------|-----------------------------------------------------------------------------------------| +| RES | 32, 64, 128 or 256 | Response RES[0]...RES[31] or RES[0]...RES[63] or RES[0]...RES[127] or RES[0]...RES[255] | + +**Table 6: f3 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------------| +| CK | 128 or 256 | Confidentiality key CK[0]...CK[127] or CK[0]...CK[255] | + +**Table 7: f4 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------------------| +| IK | 128 or 256 | Integrity key IK[0]...IK[127] or IK[0]...IK[255] | + +**Table 8: f5 output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|------------------------------| +| AK | 48 | Anonymity key AK[0]...AK[47] | + +**Table 9: f5\* output** + +| Parameter | Size (bits) | Comment | +|-----------|-------------|--------------------------------------| +| AK | 48 | Resynch anonymity key AK[0]...AK[47] | + +NOTE 2: Both f5 and f5\* outputs are called AK according to [1]. In practice only one of them at a time will be calculated in any given call to the authentication and key agreement algorithms. + +# 5 Conformance test data for KECCAK + +## 5.1 Overview + +The test data sets presented here are for the cryptographic permutation Keccak-f[1600], as it is specified in [3], and used within [4]. This permutation is abbreviated as $\Pi$ , and use strings **IN**[0] .. **IN**[1599] and **OUT**[0] .. **OUT**[1599] to represent the input and output of $\Pi$ . + +The following test sets are the same as in [5]. + +## 5.2 Format + +For brevity, the **IN** and **OUT** strings will be presented as lists of 200 bytes (octets), with each individual byte written separately in hexadecimal notation. The lists of bytes should be read from left to right, and then from top to bottom. + +For **IN**, the first byte of the list will denote the bits **IN**[0] to **IN**[7], with **IN**[0] equal to the *least* significant bit of the corresponding hexadecimal number equal to and **IN**[7] equal to the *most* significant bit of the same hexadecimal number. The final byte of the list will denote **IN**[1592] to **IN**[1599], with **IN**[1592] equal to the *least* significant bit of the corresponding hexadecimal number, and **IN**[1599] equal to the *most* significant bit of the same number. + +**OUT** strings will be presented in the same way. + +As an example, in Test Set 1 below: + +``` +IN[0] = 0, IN[1] = 0, IN[2] = 1, IN[3] = 0, IN[4] = 0, IN[5] = 1, IN[6] = 0, IN[7] = 0, +IN[8] = 0, IN[9] = 1, IN[10]=1, IN[11]=0, IN[12]=1, IN[13]=1, IN[14]=1, IN[15]=0, ... , +IN[1584]=1, IN[1585]=1, IN[1586]=0, IN[1587]=1, IN[1588]=0, IN[1589]=0, IN[1590]=0, IN[1591]=0, +IN[1592]=0, IN[1593]=0, IN[1594]=0, IN[1595]=0, IN[1596]=1, IN[1597]=0, IN[1598]=1, IN[1599]=0. +``` + +``` +OUT[0] = 1, OUT[1] = 1, OUT[2] = 1, OUT[3] = 1, OUT[4] = 0, OUT[5] = 1, OUT[6] = 0, OUT[7] = 0, +OUT[8] = 0, OUT[9] = 0, OUT[10]=1, OUT[11]=1, OUT[12]=1, OUT[13]=0, OUT[14]=1, OUT[15]=1, ... , +OUT[1584]=0, OUT[1585]=1, OUT[1586]=1, OUT[1587]=1, OUT[1588]=1, OUT[1589]=0, OUT[1590]=0, +OUT[1591]=0, OUT[1592]=1, OUT[1593]=1, OUT[1594]=1, OUT[1595]=0, OUT[1596]=0, OUT[1597]=1, +OUT[1598]=0, OUT[1599]=1. +``` + +## 5.3 Test set 1 + +IN: + +24 76 d2 da c5 9e 2e 93 49 df 32 55 a9 da b1 b6 9e b5 c2 08 f1 51 c7 30 9e 8c 8f 17 db 45 6d 0b 5e +b0 af b6 c7 3e 37 ce 8c cc cf 20 b7 9d 8a 67 29 41 49 c17 48 09 e4 29 70 93 30 c4 ad 23 1d 3e 52 11 +ae 0b d8 05 20 c4 3a d4 b4 36 62 57 92 a7 6c 52 08 9d 0f 73 92 71 15 1a 37 59 4d f6 6d e4 42 9f 3c +97 0a 34 56 b6 ce 2c 78 cd 11 28 71 7f 4b db 73 1a 4c 97 db e5 eb 73 53 fe 81 e3 7c 33 ac 60 b8 21 +22 ea c6 11 a9 8e 0e 74 42 b9 99 64 75 22 93 e4 f9 c6 96 ba 05 f0 7a 21 45 1f 90 73 0c 96 78 c6 45 +ad 4b e4 4c 4d 2d 98 1a 34 12 08 1c 9c 6b 05 c9 93 ff 1c 56 1a 0d 24 2b 47 06 d5 01 c3 47 65 b3 7a +0b 50 + +OUT: + +2f dc 58 d4 d9 4a 88 4c 1c b0 3a 8e 63 ac ab 83 75 e8 56 b5 61 ba 3a 06 25 e8 30 ac db 55 73 42 86 +64 6f 87 18 9b 43 54 25 b5 d6 4e 22 82 28 76 97 b8 1c be ad 65 5b 0a aa cc c2 5e 3d 7e 51 b5 cb +5a c2 27 f6 7f 2a d8 a0 62 97 67 82 b0 8a 7e c3 f1 b5 38 d6 00 8c 0b ab ef 83 da 64 36 6b 62 a5 3f +88 a3 dc 06 29 bd ed 79 5f 32 20 f3 c6 5c 76 bd d0 12 43 e8 8f 63 d6 91 2e 5f b5 cd a1 67 b7 1f 9b +aa a7 42 dc 19 3f f7 8c 17 67 a3 8a 1c 96 40 8c ce 16 92 39 b0 77 f2 90 3a 07 b8 c4 6a 04 8d 66 31 +8e 59 5e a4 bb 92 99 2c 7c 2d 3d cd 38 19 75 b6 e0 5f 85 ba 18 15 20 96 cc 30 ed 22 14 0f f3 b6 71 +1e a7 + +## 5.4 Test set 2 + +IN: + +80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 + +OUT: + +44 e0 e5 8c a9 68 97 5c 4c 25 92 a1 57 f5 3f 21 24 51 9b 01 0b 89 e1 5e 30 1e f5 8f 76 50 1d b5 9c +de 06 7f 1f de 09 c0 a4 b5 c2 10 a6 a1 9f 06 ba 4c 8f 0c 6f c8 68 f0 fc 80 a6 3b 25 53 79 1e 41 c8 +22 78 ad 11 5e fc 70 f7 1d 64 1f f0 77 4a a5 d5 47 b6 d9 91 49 14 02 2c 51 4c 45 fc ec a6 1c b6 6b +0f 03 13 e3 49 88 ae 0d 36 73 7e 2c 05 29 90 7f e6 53 fc 4e 18 5d 07 f3 96 1f 82 6b b8 80 31 af 84 +4d 9e 7d 98 76 17 03 63 fd e7 67 86 c5 8c cb cf 5c 3a 01 bb 91 4c 1b 02 08 a2 7c 7b e3 bb bb bb 99 +76 e0 40 31 7a fc 2a fb fa dc 7b a7 fc 23 72 35 c6 55 51 aa 31 39 64 1f a8 db 2e 64 83 f2 87 40 b3 +1b 61 + +## 5.5 Test set 3 + +IN: + +01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 +22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40 41 42 +43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60 61 62 63 +64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 82 83 84 +85 86 87 88 89 8a 8b 8c 8d 8e 8f 90 91 92 93 94 95 96 97 98 99 9a 9b 9c 9d 9e 9f a0 a1 a2 a3 a4 a5 +a6 a7 a8 a9 aa ab ac ad ae af b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 ba bb bc bd be bf c0 c1 c2 c3 c4 c5 c6 +c7 c8 + +OUT: + +5d d0 e3 dd 9e 46 db 21 87 a9 e1 a4 44 42 7d 7a 83 2f ef 29 91 39 90 e0 15 ea 8d 1f 3f 1f a6 41 3f +fb bc 58 6f 5a 4d 69 4d d6 06 68 fb f3 b4 bb da 49 45 c9 ea 0c be e2 11 73 5e bf a8 39 9b 61 3a ff +34 d1 dd 47 fa 39 8c 78 f4 8a 91 a6 65 7d 29 03 6c 87 f7 73 5f 43 e2 ab b7 6a 13 50 45 b7 0e 42 c5 +9d 80 92 14 a4 cd 30 1f 18 57 30 0a 55 d0 1d 32 36 5b 6a bd a5 1e ad 75 41 db 7b ed dc 46 e4 85 72 +7c 3b 2b 5d 83 b5 9e 5a 7a 62 e0 13 16 14 ba 0d 7b fa cd 4e ba 71 62 32 80 88 59 f0 03 85 5f 5c 47 +01 0a 50 e1 26 2f 9e 9e 81 2e 6c b3 dd 52 d9 ad b7 be 19 10 42 76 34 02 52 31 96 8d e0 b4 3f a2 4b +4b 3e + +## 5.6 Test set 4 + +IN: + +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab +ab ab + +OUT: + +00 52 f0 0e b4 09 b5 ce 5f 78 e9 53 20 ee 6a 71 5f 5b 1a 0a 7e 5b ed 03 43 d6 91 13 30 ab e2 fc 57 +b6 6f b5 ba 9e f2 88 0b 05 75 ed 0a 98 70 c5 0c 66 57 83 8a 1d 32 f3 88 fd c3 a4 e7 32 46 dd d9 56 +58 74 77 c4 c8 d4 1a d4 19 14 04 52 cc 17 13 23 ae 1f f0 91 0c e1 c3 27 8b 62 c6 48 75 91 2b 7f 7c +21 cf a0 52 e0 b0 40 21 4c 5f 3b 81 c3 20 75 87 92 ce a0 c8 d1 e4 2e 92 e1 ef 3c f0 66 be 16 c6 1e +e4 4d dd 69 db 72 9a 82 5d 4d bb fd 9f 97 da 46 c6 10 3d 5a 5f 8c 8d 21 bd 42 7d 58 af 4b 41 11 78 +be de 5a 19 86 a0 c9 1d 38 c4 85 ee 2d 54 72 bd d0 a5 b9 fa ab f7 07 73 13 ca f9 f3 0a 1e 46 ac 8e +12 58 + +## 5.7 Test set 5 + +IN: + +``` +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd cd +cd cd +``` + +OUT: + +``` +c1 6c a0 6d ef 3a dd 45 b2 0c cf d6 7a a8 f9 12 15 c2 e8 75 1e dd 02 a5 10 3f 61 ba 6f 7b f3 bb b2 +59 5f 41 1b af 6a ab 16 53 f1 7e 95 1e 2d c8 8d fb f7 68 67 94 0a 63 38 60 82 18 f8 df f1 41 7b db +3c 6f 45 22 64 87 a9 a6 07 8b 65 3a 67 ff 86 1d fa 79 30 77 c0 88 03 a8 b9 62 da 67 24 dd c8 6d 10 +93 ff d0 05 88 a2 8e 6c 1b 80 1f 73 54 63 bc 05 58 1e d5 97 bd bf 37 a4 59 29 7f 65 05 39 98 9e fc +4a 7a 9c 8b 22 33 c0 20 de a3 00 34 c1 f2 c6 cf 5e 0c cc cc 53 55 40 87 18 03 ed 3d 20 b0 c5 10 13 +a3 02 4a c5 6b 33 af 5a 26 11 23 3d 53 7d 11 80 4e f0 2e b5 59 78 ff d4 3d 9a 7e 48 84 42 64 de ce +8f a8 +``` + +## 5.8 Test set 6 + +IN: + +``` +00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 04 +00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 03 00 +00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 02 00 00 +00 00 00 00 00 03 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 +00 00 00 00 02 00 00 00 00 00 00 03 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 +00 00 00 01 00 00 00 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 00 00 00 04 00 00 00 00 00 +00 00 +``` + +OUT: + +``` +56 0d be 41 f6 a7 5a 7d 33 e1 5d 6b fe 0b dc 64 7d e5 54 34 1c e0 d0 61 bb bd f1 be 75 76 49 de e7 +41 b1 fd 37 41 8d a6 f3 5a b7 0e 15 87 cc 36 8c 1b 89 ad cc ce 1d 07 ad 92 0d 4d 9d 08 a0 43 94 6c +2f 6f e1 a5 17 a2 49 ce 3c 8a 7f 83 4e ec fa 2f aa ad de 32 e6 0b 24 d4 2a 2b 04 a7 84 63 a9 b2 +df 6d 2f 02 fc 5c 29 73 2a 12 65 14 fb 15 eb 7a be 7f bf 57 18 91 66 91 c7 c2 f8 43 46 00 da 7e 2f +9b 76 65 a5 9c 61 41 11 55 05 c9 d9 e9 f8 05 af 6f 9e 6b c4 f1 9c 65 c6 0e a9 72 a6 e4 fa 01 85 7d +29 8a 09 26 83 90 d5 74 f6 3d 4f 76 fb 6d 6d fc d1 37 38 c4 98 48 ac d5 1e 4e d7 83 af a1 ba 52 0f +a3 37 +``` + +# 6 Conformance test data for Tuak + +## 6.1 Overview + +The test data sets presented here are for the seven functions *f1*, *f1\**, *f2*, *f3*, *f4*, *f5* and *f5\**. The test sets are the same as in [5]. + +## 6.2 Format + +Each Test shows the various inputs to the algorithms. This is followed by the configuration field TOP and other operator configuration parameters: the length of the K, the length of the outputs MAC, CK, IK and RES, and the number of Keccak iterations. These are followed by the value of TOPC and finally by the function outputs. + +One of the test sets (set 4) is shown twice: once in hexadecimal format, and then again in binary format. This is to explicitly show the relationship between the binary data and the hexadecimal representation. + +For brevity, the remainder of the test sets are presented in hexadecimal format only. + +## 6.3 Test set 1 + +Input Parameters: + +``` + +K: abababababababababababababababab +RAND: 42424242424242424242424242424242 +SQN: 111111111111 +AMF: ffff + +``` + +Operator Configuration Parameters: + +``` + +TOP: 5555555555555555555555555555555555555555555555555555555555555555 +Klength = 128 bits, MAClength = 64 bits, CKlength = 128 bits, +IKlength = 128 bits, RESlength = 32 bits, KeccakIterations = 1 +TOPc: bd04d9530e87513c5d837ac2ad954623a8e2330c115305a73eb45d1f40cccbff + +``` + +Output Parameters: + +``` + +f1: f9a54e6aeaa8618d +f1*: e94b4dc6c7297df3 +f2: 657acd64 +f3: d71a1e5c6caffe986a26f783e5c78be1 +f4: be849fa2564f869aecee6f62d4337e72 +f5: 719f1e9b9054 +f5*: e7af6b3d0e38 + +``` + +## 6.4 Test set 2 + +### Input Parameters: + +K: fffefdfcfbfaf9f8f7f6f5f4f3f2f1f0feeedecebeae9e8e7e6e5e4e3e2e1e0 + RAND: 0123456789abcdef0123456789abcdef + SQN: 0123456789ab + AMF: abcd + +### Operator Configuration Parameters: + +TOP: 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f + Klength = 256 bits, MAClength = 128 bits, CKlength = 128 bits, + IKlength = 128 bits, RESLength = 64 bits, KeccakIterations = 1 + TOPc: 305425427e18c503c8a4b294ea72c95d0c36c6c6b29d0c65de5974d5977f8524 + +### Output Parameters: + +f1: c0b8c2d4148ec7aa5f1d78a97e4d1d58 + f1\*: ef81af7290f7842c6ceafa537fa0745b + f2: e9d749dc4eea0035 + f3: a4cb6f6529ab17f8337f27baa8234d47 + f4: 2274155ccf4199d5e2abcbf621907f90 + f5: 480a9345cc1e + f5\*: f84eb338848c + +## 6.5 Test set 3 + +### Input Parameters: + +K: fffefdfcfbfaf9f8f7f6f5f4f3f2f1f0feeedecebeae9e8e7e6e5e4e3e2e1e0 + RAND: 0123456789abcdef0123456789abcdef + SQN: 0123456789ab + AMF: abcd + +### Operator Configuration Parameters: + +TOP: 808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f + Klength = 256 bits, MAClength = 256 bits, CKlength = 128 bits, + IKlength = 256 bits, RESLength = 64 bits, KeccakIterations = 1 + TOPc: 305425427e18c503c8a4b294ea72c95d0c36c6c6b29d0c65de5974d5977f8524 + +### Output Parameters: + +f1: d97b75a1776065271b1e212bc3b1bf173f438b21e6c64a55a96c372e085e5cc5 + f1\*: 427bbf07c6e3a86c54f8c5216499f3909a6fd4a164c9fe235b1550258111b821 + f2: 07021c73e7635c7d + f3: 4d59ac796834eb85d11fa148a5058c3c + f4: 126d47500136fdc5ddfd14f19ebf16749ce4b6435323fbb5715a3a796a6082bd + f5: 1d6622c4e59a + f5\*: f84eb338848c + +## 6.6 Test set 4 + +### Hexadecimal Format + +#### Input Parameters: + +K: b8da837a50652d6ac7c97da14f6acc61 + RAND: 6887e55425a966bd86c9661a5fa72be8 + SQN: 0dea2ee2c5af + AMF: df1e + +#### Operator Configuration Parameters: + +TOP: 0952be13556c32ebc58195d9dd930493e12a9003669988ffde5fa1f0fe35cc01 + Klength = 128 bits, MAClength = 128 bits, CKlength = 128 bits, + IKlength = 128 bits, RESLength = 128 bits, KeccakIterations = 1 + TOPc: 2bc16eb657a68e1f446f08f57c0efb1d493527a2e652ce281eb6ca0e4487760a + +#### Output Parameters: + +f1: 749214087958dd8f58bfcdf869d8ae3f + f1\*: 619e865afe80e382ae13063f9dfb56d + f2: 4041ce438e3e38e8aa96562eed83ac43 + f3: 3e3bc01bea0cd914c4c2c83ce2d92757 + f4: 666a8e6f577b1aa77b7fd53cebb8a3d6 + f5: 1f880d005119 + f5\*: 45e617d77fe5 + +### Binary Format + +K: 10111000 11011010 10000011 01111010 01010000 01100101 00101101 01101010 11000111 11001001 + 01111101 10100001 01001111 01101010 11001100 01100001 + +RAND: 01101000 10000111 11100101 01010100 00100101 10101001 01100110 10111101 10000110 11001001 + 01100110 00011010 01011111 10100111 00101011 11101000 + +SQN: 00001101 11101010 00101110 11100010 11000101 10101111 + +AMF: 11011111 00011110 + +TOP: 00001001 01010010 10111110 00010011 01010101 01101100 00110010 11101011 11000101 10000001 + 10010101 11011001 11011101 10010011 00000100 10010011 11100001 00101010 10010000 00000011 01100110 + 10011001 10001000 11111111 11011110 01011111 10100001 11110000 11111110 00110101 11001100 00000001 + +TOPc: 00101011 11000001 01101110 10110110 01010111 10100110 10001110 00011111 01000100 01101111 + 00001000 11110101 01111100 00001110 11111011 00011101 01001001 00110101 00100111 10100010 11100110 + 01010010 11001110 00101000 00011110 10110110 11001010 00001110 01000100 10000111 01110110 00001010 + +f1: 01110100 10010010 00010100 00001000 01111001 01011000 11011101 10001111 01011000 10111111 + 11001101 11111000 01101001 11011000 10101110 00111111 + +f1\*: 01100001 10011110 10000110 01011010 11111110 10000000 11100011 10000010 10101110 11100001 + 00110000 01100011 11111001 11011111 10110101 01101101 + +f2: 01000000 01000001 11001110 01000011 10001110 00111110 00111000 11101000 10101010 10010110 + 01010110 00101110 11101101 10000011 10101100 01000011 + +f3: 00111110 00111011 11000000 00011011 11101010 00001100 11011001 00010100 11000100 11000010 + 11001000 00111100 11100010 11011001 00100111 01010111 + +f4: 01100110 01101010 10001110 01101111 01010111 01111011 00011010 10100111 01111011 01111111 + 11010101 00111100 11101011 10111000 10100011 11010110 + +f5: 00011111 10001000 00001101 00000000 01010001 00011001 + +f5\*: 01000101 11100110 00010111 11010111 01111111 11100101 + +## 6.7 Test set 5 + +### Input Parameters: + +K: 1574ca56881d05c189c82880f789c9cd4244955f4426aa2b69c29f15770e5aa5 + RAND: c570aac68cde651fb1e3088322498bef + SQN: c89bb71f3a41 + +AMF: 297d + +### Operator Configuration Parameters: + +TOP: e59f6eb10ea406813f4991b0b9e02f181edf4c7e17b480f66d34da35ee88c95e +Klength = 256 bits, MAClength = 64 bits, CKlength = 256 bits, +IKlength = 128 bits, RESLength = 256 bits, KeccakIterations = 1 +TOPc: 3c6052e41532a28a47aa3cbb89f223e8f3aaa976ae48bc3e7d6165a55eff62 + +### Output Parameters: + +f1: d7340dad02b4cb01 +f1\*: c6021e2e66accb15 +f2: 84d89b41db1867ffd4c7ba1d82163f4d526a20fbae5418fbb526940b1eeb905c +f3: d419676afe5ab58c1d8bee0d43523a4d2f52ef0b31a4676a0c334427a988fe65 +f4: 205533e505661b61d05cc0eac87818f4 +f5: d7b3d2d4980a +f5\*: ca9655264986 + +## 6.8 Test set 6 + +### Input Parameters: + +K: 1574ca56881d05c189c82880f789c9cd4244955f4426aa2b69c29f15770e5aa5 +RAND: c570aac68cde651fb1e3088322498bef +SQN: c89bb71f3a41 +AMF: 297d + +### Operator Configuration Parameters: + +TOP: e59f6eb10ea406813f4991b0b9e02f181edf4c7e17b480f66d34da35ee88c95e +Klength = 256 bits, MAClength = 256 bits, CKlength = 256 bits, +IKlength = 256 bits, RESLength = 256 bits, KeccakIterations = 2 +TOPc: b04a66f26c62fcd6c82de22a179ab65506ecf47f56245cd149966cfa9cec7a51 + +### Output Parameters: + +f1: 90d2289ed1ca1c3dbc2247bb480d431ac71d2e4a7677f6e997cfddb0cbad88b7 +f1\*: 427355dbac30e825063aba61b556e87583abac638e3ab01c4c884ad9d458dc2f +f2: d67e6e64590d22eecba7324afa4af4460c93f01b24506d6e12047d789a94c867 +f3: ede57edfc57cdffe1aae75066a1b7479bbc3837438e88d37a801cccc9f972b89 +f4: 48ed9299126e5057402fe01f9201cf25249f9c5c0ed2afcf084755daff1d3999 +f5: 6aae8d18c448 +f5\*: 8c5f33b61f4e + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| Dec 2013 | | | | | Version after approval | 1.1.0 | 12.0.0 | +| Dec 2013 | | | | | Update of Introduction with spec numbers | 12.0.0 | 12.0.1 | +| June 2014 | SP-64 | SP-140316 | 001 | 2 | Overall editorial modification to the Tuak specification TS 35.233 | 12.0.1 | 12.1.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.1.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35909/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-16/35_series/35909/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e03d5444b8e83eaeb937742f22787be542ab3cc --- /dev/null +++ b/marked/Rel-16/35_series/35909/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d6c9d8abd0fe8def325aadc0cf8368c09837efd1aee3bfe79361a18427dcedf +size 71621 diff --git a/marked/Rel-16/35_series/35909/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-16/35_series/35909/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea53185d1815a3d1747e5e0c6436b6f9cc467908 --- /dev/null +++ b/marked/Rel-16/35_series/35909/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2140872472bce86c9b338d5b4917dc2fcd162db7132b27f4b10a7342ccc4002b +size 27805 diff --git a/marked/Rel-16/35_series/35909/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-16/35_series/35909/df1d0e45191302de72176e4390224c16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89a1c7538400f4b1cc65951be113516fed2212c0 --- /dev/null +++ b/marked/Rel-16/35_series/35909/df1d0e45191302de72176e4390224c16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13928c723adf2c7828f4234cf8e733e5f4ddad036cc8d3ab223e7ed8aa80573d +size 23699 diff --git a/marked/Rel-16/35_series/35909/raw.md b/marked/Rel-16/35_series/35909/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b5b29a6f01dc6eba8e52cc889371dfe4847c5baf --- /dev/null +++ b/marked/Rel-16/35_series/35909/raw.md @@ -0,0 +1,928 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Abbreviations ..... | 7 | +| 4 Structure of this report ..... | 8 | +| 5 Background to the design and evaluation work ..... | 8 | +| 6 Summary of algorithm requirements ..... | 9 | +| 6.1 General requirements for 3GPP cryptographic functions and algorithms ..... | 9 | +| 6.2 Authentication and key agreement functions..... | 9 | +| 6.2.1 Implementation and operational considerations ..... | 9 | +| 6.2.2 Type of algorithm ..... | 9 | +| 6.2.2.1 f1 ..... | 9 | +| 6.2.2.2 f1* ..... | 10 | +| 6.2.2.3 f2 ..... | 10 | +| 6.2.2.4 f3 ..... | 10 | +| 6.2.2.5 f4 ..... | 10 | +| 6.2.2.6 f5 ..... | 10 | +| 6.2.2.7 f5* ..... | 10 | +| 7 Design criteria ..... | 11 | +| 7.1 Cryptographic Criteria..... | 11 | +| 7.2 Implementation Criteria ..... | 11 | +| 7.3 The need for an Operator Variant Algorithm Configuration Field ..... | 11 | +| 7.4 Criteria for the cryptographic kernel..... | 11 | +| 7.4.1 Implementation and operational considerations ..... | 12 | +| 7.4.2 Functional requirements ..... | 12 | +| 7.4.3 Types and parameters for the kernel..... | 12 | +| 8 The 3GPP MILENAGE algorithms ..... | 13 | +| 9 Rationale for the chosen design ..... | 13 | +| 9.1 Block ciphers vs. hash functions ..... | 13 | +| 9.2 The choice of Rijndael ..... | 14 | +| 9.3 The MILENAGE architecture ..... | 15 | +| 9.3.1 Use of OP ..... | 15 | +| 9.3.2 Rotations and constants ..... | 15 | +| 9.3.3 Protection against side-channel attacks ..... | 15 | +| 9.3.4 The number of kernel operations..... | 15 | +| 9.3.5 Mode of operation ..... | 15 | +| 10 Evaluation ..... | 16 | +| 10.1 Evaluation criteria ..... | 16 | +| 10.2 Operational Context ..... | 17 | +| 10.3 Analysis..... | 17 | +| 10.3.1 A formal proof of the soundness of the f2-f5* construction ..... | 17 | +| 10.3.2 On the f1-f1* construction and its separation from f2-f5* ..... | 19 | +| 10.3.2.1 Soundness of the f1-f1* construction ..... | 19 | +| 10.3.2.2 Separation between f1-f1* and f2-f5* ..... | 19 | +| 10.3.3 Investigation of forgery or distinguishing attacks with $2^{64}$ queries..... | 20 | +| 10.3.3.1 An internal collision attack against f1 (or f1*) ..... | 20 | +| 10.3.3.2 Forgery or distinguishing attacks against combinations of several modes..... | 20 | +| 10.3.3.2.1 Attacks against combinations of f2-f5 ..... | 21 | +| 10.3.3.2.2 Attacks against combinations of f1-f1* and f2-f5* ..... | 21 | +| 10.3.3.3 Conclusion about the identified forgery or distinguishing attacks ..... | 21 | +| 10.4 Statistical evaluation ..... | 22 | + +| | | | +|------------------------|---------------------------------------------------|----| +| 10.5 | Published attacks on Rijndael ..... | 22 | +| 10.6 | Complexity evaluation ..... | 23 | +| 10.6.1 | Complexity of draft Rijndael implementation ..... | 23 | +| 10.6.2 | Estimate complexity of modes ..... | 23 | +| 10.6.3 | Estimate of total MILENAGE ..... | 23 | +| 10.6.4 | SPA/DPA, Timing attack countermeasures ..... | 23 | +| 10.6.5 | Conclusion on algorithm complexity ..... | 24 | +| 10.7 | External complexity evaluations ..... | 24 | +| 10.8 | Evaluation of side channel attacks ..... | 25 | +| 10.8.1 | Evaluation of the kernel algorithm ..... | 25 | +| 10.8.1.1 | Timing Attacks ..... | 25 | +| 10.8.1.2 | Simple Power Analysis ..... | 25 | +| 10.8.1.3 | Differential Power Analysis ..... | 25 | +| 10.8.1.4 | Other side channels ..... | 26 | +| 10.8.2 | Evaluation of the f1-f5 modes ..... | 26 | +| 10.8.2.1 | Operator Constants (OP or OPc) ..... | 26 | +| 10.8.2.2 | Rotations and constants ..... | 26 | +| 10.8.3 | Conclusion on side channel attacks ..... | 26 | +| 11 | Conclusions ..... | 27 | +| Annex A (informative): | Change history ..... | 28 | + +# --- 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. + +# --- Introduction + +This Report has been produced by ETSI SAGE Task Force 172 on the design of an example set for 3GPP Authentication and Key Generation Algorithms. + +The work described in this report was undertaken in response to a request made by 3GPP TSG SA. + +SAGE Version 1.0 of this report was submitted to the 3GPP SA WG3 group in December 2000. Version 1.1 (with updated C-code in Annex 4) was approved by TSG SA#10 in December 2000. + +# --- 1 Scope + +This report contains a detailed summary of the work performed during the design and evaluation of the 3GPP Authentication Functions denoted as the MILENAGE algorithm set. It contains all results and findings from this work and should be read as a supplement to the specifications of the algorithms in ref. [3] and the general project report, ref. [4]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. +- [1] 3G TS 33. 102 V 3.5.0 (2000-07) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security Architecture. +- [2] 3G TS 33. 105 V 3.4.0 (2000-07) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Cryptographic Algorithm Requirements. (Release 1999) +- [3] ETSI/SAGE Specification. Specification of the MILENAGE Algorithm Set: an Example Algorithm Set for the 3GPP Authentication and Key generation Functions, *f1, f1\*, f2, f3, f4, f5 and f5\**; Document 1: Algorithm Specification. Version: 1.0; Date: 22nd November 2000. +- [4] ETSI/SAGE Report. Report on the Design and Evaluation of the 3GPP Authentication and Key generation Functions; Version: 1.0; Date: 22nd November 2000. +- [5] Wassenaar Arrangement, December 1998. . +- [6] P. C. Kocher, 'Timing Attacks on Implementations of Diffie-Hellman, RSA, DSS, and Other Systems', *CRYPTO'96, LNCS 1109*, Springer-Verlag, 1996, pp. 104-113. +- [7] J. Kelsey, B. Schneier, D. Wagner, C. Hall, 'Side Channel Cryptanalysis of Product Ciphers', *ESORICS'98, LNCS 1485*, Springer-Verlag, 1998, pp. 97-110. +- [8] L. Goubin, J. Patarin, 'DES and differential power analysis', *CHES'99, LNCS 1717*, Springer-Verlag, 1999, pp. 158-172 +- [9] P. Kocher, J. Jaffe, B. Jun, 'Differential Power Analysis', *CRYPTO'99, LNCS 1666*, Springer-Verlag, 1999, pp. 388-397. +- [10] T. S. Messerges, 'Securing the AES finalists against Power Analysis Attacks', *FSE'00, LNCS*, Springer-Verlag, to appear. +- [11] L. Goubin, J.-S. Coron, 'On boolean and arithmetic masking against differential power analysis,' *CHES'00, LNCS*, Springer-Verlag, to appear. +- [12] Nechvatal, Barker, Bassham, Burr, Dworkin, Foti and Roback, 'Report on the Development of the Advanced Encryption Standard (AES)', NIST, October 2, 2000. +- [13] F. Sano, M. Koike, S. Kawamura and M. Shiba, 'Performance evaluation of AES Finalists on the High-End Smart Card', The Third AES Candidate Conference, New York, April 2000. +- [14] M. Bellare, J. Kilian, P. Rogaway, The Security of Cipher Block Chaining, proceedings of Crypto'94, Springer Verlag, pp341-358. + +- [15] J. Daemen and V. Rijmen, *AES Proposal: Rijndael*, AES algorithm submission. September 3, 1999, available at . +- [16] H. Gilbert and M. Minier, *A collision attack on 7 rounds of Rijndael*, in The Third AES Candidate Conference, printed by the National Institute of Standards and Technology, April 13-14, 2000, pp. 230-241. +- [17] S. Lucks, *Attacking Seven Rounds of Rijndael Under 192-bit and 256-bit Keys*, in The Third AES Candidate Conference, printed by the National Institute of Standards and Technology, April 13-14, 2000, pp. 215-229. +- [18] N. Ferguson, et al., *Improved Cryptanalysis of Rijndael*, in the preproceedings of the Fast Software Encryption Workshop 2000, April 10-12, 2000. + +# 3 Abbreviations + +For the purposes of the present report, the following abbreviations apply: + +| | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------| +| AES | Advanced Encryption Standard | +| AMF | Authentication Management Field | +| AK | Anonymity Key | +| AuC | Authentication Centre | +| CBC | Cipher Block Chaining | +| CK | Cipher Key | +| DES | Data Encryption Standard | +| DPA | Differential Power Analysis | +| EEPROM | Electronically Erasable Programmable Read-Only Memory | +| GF(q) | The finite field of q elements | +| 3GPP | 3 rd Generation Partnership Project | +| IPA | Inferential Power Analysis | +| IK | Integrity Key | +| IV | Initialisation Vector | +| K | Subscriber Key | +| MAC | Message Authentication Code | +| MAC-A | Network Authentication Code | +| MAC-S | Resynchronisation Authentication Code | +| OFB | Output feedback mode | +| OP | a 128-bit Operator Variant Algorithm Configuration Field that is a component of the functions f1, f1*, f2, f3, f4, f5 and f5* | +| OP C | a 128-bit value derived from OP and K and used within the computations of the functions f1, f1*, f2, f3, f4, f5 and f5* . | +| RAM | Random Access Memory | +| RES | Response to Challenge | +| RNC | Radio Network Controller | +| ROM | Read Only Memory | +| SAGE | Security Algorithms Group of Experts | +| SPA | Simple Power Analysis | +| SQN | Sequence Number | +| TA | Timing Attack | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| USIM | User Services Identity Module | +| XRAM | Extended RAM | +| XRES | Expected User Response | + +# 4 Structure of this report + +The material presented in this report is organised in the subsequent clauses, as follows: + +- Clause 5 provides background information to the design work of the example set for 3GPP Authentication and + +Key generation Functions; + +- Clause 6 provides a summary of the algorithm requirements; +- Clause 7 describes the design criteria used for the work; +- Clause 8 consists of a brief presentation of the actual designs; +- Clause 9 provides some background information on the chosen design; +- Clause 10 gives an overview of the evaluation work carried out by SAGE 3GPP TF and other parties; +- Clause 11 contains the conclusions from the work. + +# --- 5 Background to the design and evaluation work + +The 3rd Generation Partnership Project (3GPP) is a global initiative dedicated to the development of specifications for the next generations of cellular mobile systems. Integration of strong security services is an important feature of this system and the general security architecture is defined in ref. [1]. The implementation of these security services must be based on a variety of cryptographic functions/algorithms and the requirements for these functions are provided in ref. [2]. Out of the full algorithm suite, only the UMTS encryption algorithm (*f8*) and the UMTS integrity algorithm (*f9*) are fully standardized. This work was conducted by a dedicated task force based on ETSI SAGE and external experts from 3G manufacturers. + +The remaining cryptographic functions for authentication and key agreement (*f0* – *f5\**) are allocated to the Authentication Centre (AuC) and the USIM. This means that the functions are proprietary to the home environment and there is no need for formal standardization of these algorithms. However, the 3G Security Group agreed to develop an example set of functions that could be offered to operators that chose not to develop their own solutions. Again a task force was set up based on ETSI SAGE enlarged with cryptographers from 3G manufacturers. + +Note that the random challenge generating function *f0* is not included in the example set of functions provided by this work. The implementation of this function is completely determined by the operator. + +The major design goal for the task force was to design a framework for the authentication and key generation functions that was secure and flexible. This goal was achieved through the development of a well-analysed construction using a 128-bit encryption algorithm as a kernel function and including an additional configuration field parameter selected by the operator. The example design recommends the use of the AES algorithm Rijndael as the kernel function, but an operator could change this to any block cipher meeting the interface parameters. The list of candidates for the AES standard includes a large set of suitable algorithms to choose from. + +The defined set of algorithms is commonly denoted as the MILENAGE algorithms. + +# --- 6 Summary of algorithm requirements + +The requirements for the cryptographic algorithms used in the 3G Security are found in ref. [2]. We include the requirements that are essential for the reading of this report. + +## 6.1 General requirements for 3GPP cryptographic functions and algorithms + +The functions should be designed with a view to their continued use for a period of at least 20 years. Successful attacks with a workload significantly less than exhaustive key search through the effective key space should be impossible. + +The designers of above functions should design algorithms to a strength that reflects the above qualitative requirements. + +Legal restrictions on the use or export of equipment containing cryptographic functions may prevent the use of such equipment in certain countries. + +It is the intention that UE and USIMs that embody such algorithms should be free from restrictions on export or use, in order to allow the free circulation of 3G terminals. Network equipment, including RNC and AuC, may be expected to come under more stringent restrictions. It is the intention that RNC and AuC that embody such algorithms should be exportable under the conditions of the Wassenaar Arrangement, ref.[5]. + +## 6.2 Authentication and key agreement functions + +The mechanisms for authentication and key agreement described in clause 6.3 of [1] require the following cryptographic functions: + +- f1* The network authentication function; +- f1\** The re-synchronisation message authentication function; +- f2* The user authentication function; +- f3* The cipher key derivation function; +- f4* The integrity key derivation function; +- f5* The anonymity key derivation function; +- f5\** The anonymity key derivation function for re-synchronisation + +### 6.2.1 Implementation and operational considerations + +The functions *f1—f5\** shall be designed so that they can be implemented on an IC card equipped with an 8-bit microprocessor running at 3.25 MHz with 8 kbyte ROM and 300byte RAM and produce AK, XMAC-A, RES, CK and IK in less than 500 ms execution time. + +### 6.2.2 Type of algorithm + +#### 6.2.2.1 *f1* + +*f1*: the network authentication function + +*f1*: (K; SQN, RAND, AMF) $\boxminus$ MAC-A (or XMAC-A) + +*f1* should be a MAC function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND, SQN, AMF and MAC-A (or XMAC-A). + +#### 6.2.2.2 *f1\** + +*f1\**: the re-synchronisation message authentication function + +*f1\**: (K; SQN, RAND, AMF) $\boxminus$ MAC-S (or XMAC-S) + +*f1\** should be a MAC function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND, SQN, AMF and MAC-S (or XMAC-S). + +#### 6.2.2.3 *f2* + +*f2*: the user authentication function + +*f2*: (K; RAND) $\boxminus$ RES (or XRES) + +*f2* should be a MAC function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND and RES (or XRES). + +#### 6.2.2.4 *f3* + +*f3*: the cipher key derivation function + +*f3*: (K; RAND) $\boxminus$ CK + +*f3* should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND and CK. + +#### 6.2.2.5 f4 + +*f4*: the integrity key derivation function + +*f4*: (K; RAND) $\boxrightarrow$ IK + +*f4* should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND and IK. + +#### 6.2.2.6 f5 + +*f5*: the anonymity key derivation function + +*f5*: (K; RAND) $\boxrightarrow$ AK + +*f5* should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND and AK. + +The use of *f5* is optional. + +#### 6.2.2.7 f5\* + +*f5\**: the anonymity key derivation function for re-synchronisation + +*f5\**: (K; RAND) $\boxrightarrow$ AK + +*f5\** should be a key derivation function. In particular, it shall be computationally infeasible to derive K from knowledge of RAND and AK. + +The use of *f5\** is optional. + +# 7 Design criteria + +Based upon the general requirements, the task force developed a set of design criteria for the work. + +## 7.1 Cryptographic Criteria + +- Without knowledge of secret keys, the functions *f1*, *f1\**, *f2*, *f3*, *f4*, *f5* and *f5\** should be practically indistinguishable from independent random functions of their inputs (RAND||SQN||AMF) and RAND. + +Examples: Knowledge of the values of one function on a fairly large number of given inputs should not enable its values to be predicted on other inputs. The outputs from any one function should not be predictable from the values of the other functions (on the same or other inputs). + +- It should be infeasible to determine any part of the secret key K, or the operator variant configuration field, OP, by manipulation of the inputs and examination of the outputs to the algorithm. +- Events tending to violate criteria 1 and 2 should be regarded as insignificant if they occur with probability approximately $2^{-128}$ or less (or require approximately $2^{128}$ operations). +- Events tending to violate criteria 1 and 2 should be examined if they occur with probability approximately $2^{-64}$ (or require approximately $2^{64}$ operations) to ensure that they do not have serious consequences. Serious consequences would include recovery of a secret key, or ability to emulate the algorithm on a large number of future inputs. +- The design should build upon well-known structures and avoid unnecessary complexity. This will simplify analysis and avoid the need for a formal external evaluation. + +## 7.2 Implementation Criteria + +In addition to the performance requirements listed in 6.2.1, the task force agreed to ensure that the listed requirements would be met even after implementation of protection mechanisms against side channel attacks like differential power analysis (DPA). + +## 7.3 The need for an Operator Variant Algorithm Configuration Field + +In response to a request from SA3 the task force decided to include the use of the Operator variant field, OP. This configuration field is used for adding operator dependent information to the design even if the choice of the kernel function is the same. + +The roles of OP are: + +1. To make each operator's implementation different. +2. To prevent USIMs for operators being interchangeable, either through trivial modification of inputs and outputs or by reprogramming of a blank USIM. +3. To keep some algorithm details secret. +4. To provide some protection against a poorly chosen kernel. + +## 7.4 Criteria for the cryptographic kernel + +The kernel function is used by MILENAGE ("the framework") to produce a 128 bit output value from a 128 bit input value from which the output of the specific mode (one of the functions **f1** – **f5**, **f1\*** or **f5\***) is derived. These output values are produced under the control of a 128 bit user specific key K. It should be noted that K is a long term secret which must be protected under any circumstances. + +### 7.4.1 Implementation and operational considerations + +The performance requirements for the full 3GPP algorithm set are given in 6.2.1. From this budget we allocate at most 6Kbytes ROM and about 200 bytes RAM to the kernel function. The kernel function shall produce a 128 bit output value in less than 50 ms execution time. + +### 7.4.2 Functional requirements + +The purpose of the kernel function is to map an input value $p$ (the plaintext) to an output value $c$ (the ciphertext) under the control of a key K. The key shall be hidden, i.e. it shall be (computationally) infeasible to derive K if an arbitrary amount of pairs $(p,c)$ are known and K is fixed. It shall also be infeasible to compute K by repeatedly choosing $p$ , applying the kernel function and observing the resulting $c$ several times. The latter chosen plaintext attack shall even be impossible if the attacker has access to side channel information, e.g. power consumption or execution timings of an IC card which holds an implementation of the kernel function (see also ref. [3], section 5.2). + +Furthermore, it shall be infeasible to compute $c$ given $p$ if K is not known but an arbitrary amount of plaintext/ciphertext pairs are known which were produced using the same K. + +There is no need for the kernel function to be invertible. However, since the input and output values have the same size and collisions should be avoided, a bijective function would be a good choice. + +### 7.4.3 Types and parameters for the kernel + +The kernel is to be a keyed function from $n$ bit blocks to $n$ bit blocks. An example of such a keyed function is a symmetric block cipher with a blocksize of $n$ . + +The parameters of the kernel are as follows: + +block length: 128 bits + +key length: 128 bits. + +Both the key and the input/output blocks are unstructured data (at least from the kernel function's view). + +The AES candidates are good examples for kernels, which meet these requirements. + +Interfaces to the kernel: + +The following interfaces to the kernel function are defined: + +data input: $X[0], X[1], \dots, X[127]$ where $X[i]$ is the data input bit with label $i$ ; + data output: $Y[0], Y[1], \dots, Y[127]$ where $Y[i]$ is the data output bit with label $i$ ; + key input: $K[0], K[1], \dots, K[127]$ where $K[i]$ is the key bit with label $i$ . + +# 8 The 3GPP MILNAGE algorithms + +The detailed specifications of the 3GPP MILNAGE algorithms are found in ref. [3]. The following diagram shows the design of the functions $f1, f1*, f2, f3, f4, f5$ and $f5*$ using the kernel function denoted $E_K$ . + +![Diagram illustrating the design of the 3GPP MILNAGE algorithms. The diagram shows five parallel processing paths. Each path starts with a common input 'RAND' which is XORed with 'OP_C' and then passed through a kernel function 'E_K'. The output of 'E_K' is split: one branch goes through a 'rotate by r_i' block, then XORed with a constant 'c_i', then through another 'E_K' block, and finally XORed with 'OP_C' to produce an output (f1, f1*, f2, f3, f4, f5, or f5*). The other branch from the first 'E_K' block in each path is XORed with the output of the previous path's final 'OP_C' XOR block. The constants are labeled c1, c2, c3, c4, c5. The outputs are labeled f1, f1*, f5, f2, f3, f4, f5*.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +Diagram illustrating the design of the 3GPP MILNAGE algorithms. The diagram shows five parallel processing paths. Each path starts with a common input 'RAND' which is XORed with 'OP\_C' and then passed through a kernel function 'E\_K'. The output of 'E\_K' is split: one branch goes through a 'rotate by r\_i' block, then XORed with a constant 'c\_i', then through another 'E\_K' block, and finally XORed with 'OP\_C' to produce an output (f1, f1\*, f2, f3, f4, f5, or f5\*). The other branch from the first 'E\_K' block in each path is XORed with the output of the previous path's final 'OP\_C' XOR block. The constants are labeled c1, c2, c3, c4, c5. The outputs are labeled f1, f1\*, f5, f2, f3, f4, f5\*. + +Figure 1: Definition of $f1, f1*, f2, f3, f4, f5$ and $f5*$ + +Document [3] recommends use of the AES algorithm Rijndael for the kernel function $E_K$ , but this choice could be replaced by any 128-bit encryption algorithm employing a 128 bit key or keyed function fulfilling the requirements of section 7.4. The value $OP_C$ is derived from the subscriber key $K$ and the operator dependent value $OP$ by encrypting $OP$ using $K$ as the secret key, i.e. + +$$OP_C = OP \oplus E[OP]_K$$ + +$r1, \dots, r5$ are five fixed rotation constants and $c1, \dots, c5$ are five fixed addition constants defined in ref. [3]. These values will ensure that the inputs to the different functions will be different. Finally, ref. [3] defines which part of the outputs that are used for the different functions. + +# 9 Rationale for the chosen design + +## 9.1 Block ciphers vs. hash functions + +It was decided to design MILNAGE around a cryptographic kernel function with strong one-wayness properties. To be realistic such an approach requires that well scrutinized examples of suitable kernel functions are publicly available and preferably on royalty-free basis. Among the cryptographic functions that would offer the required one-wayness properties two different types can be identified, block ciphers and hash-functions. The pros and cons offered by these two alternatives were weighed up against the specific requirements of the use and the implementation environment. The decision of selecting a 128-bit block cipher as a cryptographic kernel was justified by the following aspects. + +1. Efficiency of the smart card implementation. + +It is required that the kernel function can be efficiently implemented on smart cards with eight-bit processors. + +The known and commonly used hash-functions are all optimised for larger word-size, typically 32 bits. + +### 2. Security of the smart card implementation. + +The DPA and other side channel attacks are better understood and analysed in the open literature for certain block ciphers than for any hash-functions. Also protection measures are better developed for certain block cipher structures. + +### 3. Fixed input length. + +The inputs to the kernel function are parameters of fixed length less than or equal to 128 bits. New block ciphers with 128-bit block size are suitable for handling such inputs. + +### 4. Secret key input. + +Block ciphers are designed to take a secret key input. For hash-functions such a functionality must be constructed artificially. Special keyed modes of operation have been designed for hash functions in the Internet and ISO standards. In ISO 9797 Part 2 three MAC algorithms for dedicated hash functions have been specified. Two of them take at least two applications of the round function of the hash function, which adds extra complexity. One of them, MAC Algorithm 3 is specially designed to take a short maximum 256 bits input and only one application of the round function of the hash-function. Of these three MAC algorithms only the Internet HMAC standard is freely available + +### 5. Availability of block ciphers. + +There have been many block ciphers around for many years and knowledge about their designs and implementations are well understood and widely known. Even if published 128-bit block ciphers using a 128-bit key have not been around for that many years, the AES process has provided a suite of good candidates for the kernel. On the other hand, there are only a handful candidates of hash functions that are considered secure today. + +## 9.2 The choice of Rijndael + +The task force agreed to propose the block cipher Rijndael for use as the kernel in the *f1-f5\** constructions. There were several arguments to support this choice: + +- It was a strong encryption algorithm. At that time it was one of the five AES finalists. +- It was effective and fast on several platforms. +- It was highly suitable for smart card implementation. +- It was freely available without any kind of IPR limitations. +- It could be protected against side channel attacks. +- It had the required input/output interface. +- It had been published and studied for some time and was built upon the design of a previous algorithm called SQUARE. + +In October 2000 Rijndael was chosen as the winner of the AES contest and this should be seen as a strong qualifier for its suitability in the 3GPP environment. We refer to ref. [12] for a detailed description on the evaluation and merits of Rijndael and the other AES finalists. To quote from the conclusions of this report: + +*Rijndael appears to be consistently a very good performer in both hardware and software across a wide range of computing environment regardless of its use in feedback or non-feedback modes. Its key setup time is excellent, and its key agility is good. Rijndael's very low memory requirements make it well suited for restricted-space environments, in which it also demonstrates excellent performance. Rijndael's operations are among the easiest to defend against power and timing attacks. Additionally, it appears that some defence can be provided against such attacks without significantly impacting Rijndael's performance.* + +Note that the kernel function of *f1-f5\** will only use Rijndael in encryption directions and the concerns related to complexity of both encryption and decryption mode will not apply to its use in MILENAGE. + +## 9.3 The MILENAGE architecture + +### 9.3.1 Use of OP + +OP is a 128-bit Operator Variant Algorithm Configuration Field used to provide unique variants of MILENAGE. + +It was discussed if OP should be used directly in the algorithms or rather a derived value should be involved. The task force decided to derive a subscriber dependant value $OP_c$ from OP and the secret key K in a non-invertible way as defined in Section 8. This construction is non-invertible in both variables even if one of them is known. In this case there is no need for storage of OP in each USIM. This means that even if the USIM is compromised, the value of OP could still be kept secret. + +The value $OP_c$ is exclusive ored to input and output of the kernel functions. This will provide additional protection against attacks. + +The task force recommends to compute $OP_c$ off the USIM as part of the pre-personalisation process. This will simplify the algorithms in the card and avoid the storage of OP on the card. + +An operator could also select different values of OP for different subscribers or subscriber groups. + +It is recommended that OP is kept secret, but MILENAGE is designed to be secure even if the value of OP is known to the cryptanalyst. + +### 9.3.2 Rotations and constants + +The rotations $r1, r2, \dots, r5$ and the addition constants $c1, c2, \dots, c5$ are carefully selected to ensure separation between all the cryptographic functions involved. It is shown in Section 10.3.2 that the selected values will protect against collisions in the input (and thus the output) of the final $E_k$ computations. If an operator decides to implement other values for these constants, it is strongly advised that the requirements of Section 5.3 in ref. [3] are taken into account. + +### 9.3.3 Protection against side-channel attacks + +The protection against side-channel attacks is achieved through the selection of a kernel that allows for a protected implementation within the time constraints given by the requirements in Section 6.2.1. No attempts were given to provide such protection by the surrounding architecture. + +### 9.3.4 The number of kernel operations + +For each of the seven functions the input value RAND passes through two complete rounds of the kernel function before the output values are produced. The encryption of OP in the pre-personalisation procedure provides an extra level of security. The other inputs to **f1/f1\*** are obfuscated by xor with a random value $(E[OP_c \oplus RAND]_K)$ and an unknown constant ( $OP_c$ ) before they enter the kernel function. + +As discussed in Section 10.3.3 there are certain forgery attacks against the proposed architecture that involve $2^{64}$ computations. These attacks are not considered feasible within the operational context of 3GPP and would not justify the computational overhead of adding another operation of the kernel function. + +### 9.3.5 Mode of operation + +The **f1** and **f1\*** constructions are essentially equivalent to the standard CBC MAC mode applied to the input blocks RAND and SQN || AMF || SQN || AMF. The soundness of this construction is theoretically justified by the results in ref. [14]. + +The functions **f2**, **f3**, **f4** and **f5** are defined as a kind of double encryption with a "counter-mode" construction caused by rotations and constant additions before the second encryption. The soundness of this construction is therefore a direct consequence of the use of a strong kernel function. See Section 10.3.1 for more details. + +Section 10.3.2 provides analysis about the necessary separation between the different cryptographic functions involved. + +# 10 Evaluation + +## 10.1 Evaluation criteria + +Due to the fact that the Rijndael (key length =128, block length =128 and number of rounds =10) block cipher has undergone an extensive analysis during the AES process [12], the mathematical evaluation to be done by the 3GPP AF task force will not duplicate that work and perform extra research on the cryptanalysis of Rijndael, but rather focus upon assessing the strength of the construction for deriving the **f1** to **f5\*** modes of [2] from a strong 128-bit oriented block cipher E. + +The main purpose of the mathematical evaluation is to check that the **f1-f5\*** construction does satisfy the two following requirements : + +**Under the assumption** that the underlying 128-bit block cipher $E_K$ is a strong block cipher, i.e. that there is no efficient test allowing to distinguish the $E_K$ permutation generator from a randomly drawn permutation of $\{0,1\}^{128}$ with substantially less than $2^{128}$ encryption or decryption results and significantly less than $2^{128}$ $E_K$ operations, + +- (1) **There must be no attack** of complexity substantially less than $2^{128}$ $E_K$ computations allowing to recover any information on the value of K key or to forge outputs of the algorithm for a large set of arbitrary RAND inputs, based on the knowledge of **f1-f5\*** outputs corresponding to any chosen RAND, SQN, AMF inputs, even if the OP, $c_i$ and $r_i$ values are known. +- (2) **There must be no other attack** enabling to distinguish the 7 function generators $K \mapsto f1, f1*, f2, f3, f4, f5, f5*$ from independent random functions of the 192-bit input RAND||SQN||AMF (**f1** and **f1\*** modes) or the 128-bit input RAND (other modes) with substantially less than $2^{64}$ queries, even if the OP, $c_i$ and $r_i$ values are known. Thus in particular given any combination of $n \leq 2^{64}$ **f1-f5\*** outputs related to any chosen inputs, it must be computationally infeasible to predict any additional output for any of the $f_i$ or $f_i^*$ function – even if outputs corresponding to the same RAND value are known for the other modes. + +For that purpose, the mathematical evaluation needs to consider: + +- the strength of each of the **f1-f5\*** modes considered individually ; +- the independence between the **f1-f5\*** modes. + +Given the operational context of use of the algorithm, related key attacks do not need to be considered. + +The mathematical evaluation approach will combine: + +- formal proofs allowing to validate some aspects of the modes construction ; +- informal security arguments on aspects of the modes construction not covered by formal proofs ; +- an investigation of "certificational attacks", in particular forgery or distinguishing attacks of complexity close to the $2^{64}$ bound of requirement 2. + +The following particular issues need to be taken into account in the analysis: + +- role of the $c_i$ and $r_i$ constants and security conditions on their values; +- protection of $OP_C$ . + +## 10.2 Operational Context + +The evaluation criteria discussed in Section 10.1 are basis for the mathematical analysis conducted below. Besides the theoretical work related to the security of MILENAGE, it is also important to consider the operational context in which + +the algorithms are used. It should be borne in mind that in practice the following operational factors exist: + +The prime point of attack is directly on the USIM. In this environment: + +- an attacker has full control over what he can choose for RAND, SQN, AMF. +- The output of **f1** (MAC-A) is checked within the USIM and is not directly available to an attacker. +- The input/output bandwidth of the USIM is limited (as is its processing power). As a result the practical rate at which input/output pairs can be collected is severely limited (~10 pairs or less per second?). + +## 10.3 Analysis + +As explained in Section 10.1, the main purpose of the mathematical evaluation is to analyse the construction for the **f1** to **f5\*** functions under the assumption that the 128-bit block cipher used in the construction (e.g. Rijndael) is strong. The analysis do not only want to investigate the strength of each of the **f1** to **f5\*** functions considered individually, but also their cryptographic separation. + +The evaluation results presented here cover the following complementary aspects of the **f1-f5\*** construction : + +- Section 10.3.1 considers the **f2** to **f5\*** functions and provides a formal proof (in a certain security model) of the soundness of the individual functions and their separation; +- Section 10.3.2 considers the **f1-f1\*** construction and its separation from **f2-f5\***, and provides informal arguments supporting that part of the design; +- finally, Section 10.3.3 investigates certificational forgery or distinguishing attacks, and checks that none of the "attacks" identified is stronger than the attacks requiring $2^{64}$ queries anticipated in the design criteria. + +### 10.3.1 A formal proof of the soundness of the **f2-f5\*** construction + +This section contains an investigation of the pseudorandomness of the simplified scheme of Figure 2, which keeps the most distinctive features of the actual **f2-f5\*** construction. In Figure 2 $a_1$ to $a_t$ are assumed to be any $t$ fixed known distinct constants. The $t$ parameter denotes the number of distinct output blocks used in the construction. In practice, for the **f2** to **f5\*** functions, $t$ is equal to 4. + +![Figure 2: A simplified counter mode construction diagram. An input X is processed by an encryption block E_K to produce an output Y. This output Y is then split into multiple parallel paths. In each path, the output Y is XORed with a constant a_i (a_1, a_2, ..., a_t) and then processed by another encryption block E_K to produce an output Z_i (Z_1, Z_2, ..., Z_t).](df1d0e45191302de72176e4390224c16_img.jpg) + +``` + +graph TD + X[X] --> EK1[E_K] + EK1 --> Y[Y] + Y --> XOR1((⊕)) + a1[a1] --> XOR1 + XOR1 --> EK2[E_K] + EK2 --> Z1[Z1] + Y --> XOR2((⊕)) + a2[a2] --> XOR2 + XOR2 --> EK3[E_K] + EK3 --> Z2[Z2] + Y -.-> XORt((⊕)) + at[at] --> XORt + XORt --> EKt[E_K] + EKt --> Zt[Zt] + +``` + +Figure 2: A simplified counter mode construction diagram. An input X is processed by an encryption block E\_K to produce an output Y. This output Y is then split into multiple parallel paths. In each path, the output Y is XORed with a constant a\_i (a\_1, a\_2, ..., a\_t) and then processed by another encryption block E\_K to produce an output Z\_i (Z\_1, Z\_2, ..., Z\_t). + +**Figure 2: A simplified counter mode construction** + +The aim is to give some evidence that there is no way to use any combination of significantly less than $2^{64}$ output values $z_1$ to $z_t$ to predict any new $z_i$ output value. More generally, it will be shown that if $E_K$ behaves as a random permutation of the $\{0,1\}^n$ set (where $n = 128$ ), then the $x \mapsto (z_1, z_2, \dots, z_t)$ function behaves as a random function from $\{0,1\}^n$ to $\{0,1\}^{n \cdot t}$ . + +For that purpose, let the occurrences of the $E_K$ function in Figure 2 be replaced by a perfect random permutation $c^*$ (i.e. a uniformly drawn element of the set of $\{0,1\}^n$ permutations). The construction then becomes a random function generator (or in other words a random function) $f$ from $\{0,1\}^n$ to $\{0,1\}^{n \cdot t}$ , that will be compared with a uniformly drawn + +random function $f^*$ from $\{0,1\}^n$ to $\{0,1\}^{n+t}$ (cf Figure 3). + +Let $A$ be any distinguishing algorithm of unlimited power that, when input with a $\varphi$ function from $\{0,1\}^n$ to $\{0,1\}^{n+t}$ (which can be modelled as an "oracle tape" of a Turing Machine) selects a fixed number $q$ of distinct chosen or adaptively chosen input values $x_1$ to $x_q$ (the queries), obtains the $q$ corresponding $\varphi$ output values $y_1$ to $y_q$ , and based on these results tries to determine whether $\varphi$ function is an instance of the $f$ or of the $f^*$ generator. Denote by $p$ the probability of $A$ to answer 1 when fed with a random instance of $f$ , and by $p^*$ the probability of $A$ to output 1 when fed with a random instance of $f^*$ . + +The following theorem, whose proof is given in a more comprehensive paper appended to this report, provides an upper bound on the advantage $Adv_A(f, f^*) = |p-p^*|$ of $A$ for distinguishing $f$ from $f^*$ in $q$ queries: + +**Theorem:** *Let $n$ be any fixed integer. Denote by $c^*$ any perfect random permutation of $\{0,1\}^n$ . Let $f = \Phi(c^*)$ denote the random function of $\{0,1\}^n$ to $\{0,1\}^{n+t}$ obtained by applying the counter mode construction of Figure 3 to $c^*$ , and let $f^*$ denote a perfect random function from $\{0,1\}^n$ to $\{0,1\}^{n+t}$ . For any distinguishing algorithm $A$ using a fixed number $q$ of queries we have* + +$$Adv_A(f, f^*) \leq 3 \cdot t \cdot q^2 / 2^{n+1}$$ + +![Diagram comparing two random function generators, f and f*. Generator f uses a counter mode construction with a perfect random permutation c* and a counter 'y' to produce outputs Z1 to Zt. Generator f* is a single block function that produces the same outputs Z1 to Zt from input X. The diagram includes a 'VS' label between the two generators.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates two random function generators, $f$ and $f^*$ , being compared. On the left, generator $f$ is shown. It takes an input $X$ into a block labeled $c^*$ , which outputs $y$ . This $y$ is then passed through a series of blocks, each labeled $c^*$ . Each block is preceded by an XOR gate (indicated by a circle with a cross) that also takes an input $a_i$ (where $i$ ranges from 1 to $t$ ). The outputs of these blocks are $Z_1, \dots, Z_t$ . On the right, generator $f^*$ is shown. It takes the same input $X$ into a single large block labeled $f^*$ , which directly outputs $Z_1, \dots, Z_t$ . The two generators are separated by the text "VS". + +Diagram comparing two random function generators, f and f\*. Generator f uses a counter mode construction with a perfect random permutation c\* and a counter 'y' to produce outputs Z1 to Zt. Generator f\* is a single block function that produces the same outputs Z1 to Zt from input X. The diagram includes a 'VS' label between the two generators. + +**Figure 3: The two random function generators $f$ and $f^*$ to be compared** + $c^*$ is a perfect random permutation of $\{0,1\}^n$ , + $f^*$ is a perfect random function from $\{0,1\}^n$ to $\{0,1\}^{n+t}$ + +The previous theorem gives some evidence that there is no attack requiring substantially less than $2^{64}$ queries against the slightly simplified version of $f_2$ to $f_5^*$ in which $OP_C$ is omitted (or replaced by a known constant) and the rotations are also omitted. It is trivial to adapt the proof of the theorem to accommodate the rotations; and the involvement of $OP_C$ does not seem to strongly degrade the security of $f_2$ to $f_5$ (it does not seem easy to derive $OP_C$ , and even if $OP$ was known, it will only provide a very slight information concerning $K$ , namely the $E_K$ input-output pair determined by the equation $E[OP]_K = OP_C \oplus OP$ ). + +Thus in summary, the design of the $f_2-f_5^*$ functions appears to be sound and to comply with the design criteria. + +### 10.3.2 On the $f_1-f_1^*$ construction and its separation from $f_2-f_5^*$ + +#### 10.3.2.1 Soundness of the $f_1-f_1^*$ construction + +The $f_1$ and $f_1^*$ constructions seem essentially equivalent to a standard CBC MAC applied to the 2-block message $M_1 || M_2$ , where $M_1 = RAND$ and $M_2 = SQN || AMF || SQN || AMF$ , with a final truncation of the CBC computation output. + +Moreover **f1** and **f1\*** use distinct output bits - so that the cryptographic separation between **f1** and **f1\*** appears to be sufficient. + +A formal proof of the soundness of the standard CBC MAC was first established by Bellare, Kilian and Rogaway, ref.[14]. Some results of [14] can be transposed to the actual **f1-f1\*** construction, using techniques similar to those applied in the previous section, to show that if we ignore $OP_C$ , but keep the $c1$ and $r1$ constants and replace $E_K$ by a perfect random permutation $c^*$ , then the 2-block to 1-block random function $f$ associated with the **f1-f1\*** construction is indistinguishable from a random function with substantially less than $2^{64}$ queries. + +Conversely, there exists a simple internal collision attack against the standard CBC MAC requiring about $2^{64}$ queries, so that the conjectured $2^{64}$ lower bound is also an upper bound. This internal collision "attack" (which has no practical significance in the context of use of **f1** and **f1\***) can be transposed to the **f1** and **f1\*** functions, as shown in Section 10.3.3. + +So in summary the **f1-f1\*** construction appears to be sound, and no stronger weakness than the impractical attacks with $2^{64}$ queries anticipated in the design criteria was identified. + +#### 10.3.2.2 Separation between **f1-f1\*** and **f2-f5\*** + +From now on and until the end of Section 10.2, the following short notation for the various input, output and intermediate variables involved in the **f1-f5\*** computations will be used (cf Figure 1) : + +- **x** denotes the RAND input ; +- **y** denotes the intermediate value $E[RAND \oplus OP_C]_K$ +- **t** denotes the SQN||AMF||SQN||AMF additional input; +- **z1, z1\*, z2, z3, z4, z5, z5\*** denote the **f1-f5\*** outputs; +- **zz1, zz2, zz3, zz4, zz5** denote the 128-bit $E_K$ outputs from which **z1** and **z1\***, **z2** and **z5**, **z3, z4, and z5\*** are respectively extracted; +- the $OP_C, r1$ to $r5, c1$ to $c5$ notations of the **f1-f5\*** specifications are kept. + +This section investigates the independence (as seen from an adversary's point of view) between the **f1-f1\*** functions and the **f2 to f5\*** functions. + +In practice it is of importance to look at the pairwise independence between **f1** or **f1\*** and any of the **f2 to f5\*** functions. A connection between the **zz1** 128-bit output block from which the **f1** or **f1\*** output is extracted and the **zzi = zz2, zz3, zz4, or zz5** 128-bit output blocks from which **f2 to f5\*** outputs are extracted could lead to attacks from an adversary who are able to predict events of the form $zz1(x,t) = zzi(x')$ . + +Express **zz1** and **zzi** as : $zz1(x,t) = OP_C \oplus E_K(y \oplus c1 \oplus rot(t \oplus OP_C, r1))$ and $zzi(x) = OP_C \oplus E_K(c_i \oplus rot(y \oplus OP_C, r_i))$ . Events of the form $zz1(x,t) = zzi(x)$ , i.e. collisions involving the same **x** random challenge value, have to be looked at with particular care because : + +- despite the fact that **y** is unknown, the equation $zz1(x,t) = zzi(x)$ , which can be rewritten $y \oplus rot(y, r_i) = c_1 \oplus c_i \oplus rot(t, r_1) \oplus rot(OP_C, r_1) \oplus rot(OP_C, r_i)$ provides some partial information on $OP_C$ because $y \oplus rot(y, r_i)$ is at least partially known, and even entirely known if $r_i = 0$ (it is then equal to 0). +- if an event of the form $zz1(x,t) = zzi(x)$ occurs for a particular $(x,t)$ value, then equation $zz1(x',t) = zzi(x')$ still holds for any $x'$ value such that the corresponding $y' = E_K(x' \oplus OP_C)$ satisfies equation $y' \oplus rot(y', r_i) = y \oplus rot(y, r_i)$ . Thus if $r_i = 0$ , equality $zz1(x,t) = zzi(x)$ for all **x** values and this particular **t** value. + +The $c1$ to $c5$ choices suggested in the **f1-f5\*** specification were made as to avoid any weakness that might result from events of the form $zz1(x,t) = zzi(x)$ . Due to the facts that: + +- **c1** is an even 128-bit word, +- **t** is obtained by repeating the 64-bit word SQN||AMF twice, so that **t** is an even word, +- all the other $c_i$ constants are odd, +- rotations do not affect the parity of any word, + +the parity of $E_K^{-1}(zz1 \oplus OP_C) = y \oplus c_1 \oplus \text{rot}(t \oplus OP_C, r_1)$ is equal to the parity of $y \oplus OP_C$ , whereas the parity of $E_K^{-1}(zzi \oplus OP_C) = c_i \oplus \text{rot}(y \oplus OP_C, r_i)$ is the inverse of the parity of $y \oplus OP_C$ , so that the event $zz1(x,t) = zzi(x)$ can never occur. + +So in summary the criteria on the $c_1$ to $c_5$ and $r_1$ to $r_5$ introduced in the **f1-f5\*** specification seem to ensure an effective separation of the **f1-f1\*** functions from the **f2-f5\*** functions. + +### 10.3.3 Investigation of forgery or distinguishing attacks with $2^{64}$ queries + +This section investigates properties allowing to distinguish the **f1-f5\*** functions from ideal independent random functions of their inputs. The trivial birthday based distinguishers allowing to guess that **f1-f5\*** are derived from permutations, not only functions, with about $2^{64}$ known input values is not considered here. + +Several "attacks" against one single function (namely **f1** or **f1\***) or against combinations of several functions requiring about $2^{64}$ queries are identified. Those "attacks" are described in this section. The presentation uses the abbreviated notation introduced in section 10.3.2. + +#### 10.3.3.1 An internal collision attack against **f1** (or **f1\***) + +Not surprisingly, the well-known CBC MAC internal collisions attack is applicable to **f1**: + +Consider a set of about $2^{64}$ $(x,t)$ pairs such that both the $x$ and $t$ values are pairwise distinct, and the corresponding **z1** 64-bit **f1** outputs. With a large probability, there exist two $(x,t)$ pairs $(x',t')$ and $(x'',t'')$ such that the two corresponding 128-bit output words $zz'1$ and $zz''1$ collide. + +Such a collision occurs iff + +$$y' \oplus c_1 \oplus \text{rot}(t' \oplus OP_C, r_1) = y'' \oplus c_1 \oplus \text{rot}(t'' \oplus OP_C, r_1), \text{ i.e. iff}$$ + +$$y' \oplus \text{rot}(t' \oplus OP_C, r_1) = y'' \oplus \text{rot}(t'' \oplus OP_C, r_1).$$ + +If we XOR each of the $t'$ and $t''$ values with any $\delta t = \delta \text{SQN} || \delta \text{AMF} || \delta \text{SQN} || \delta \text{AMF}$ difference value, the above condition still holds, so that + +$$f1(x', t' \oplus \delta t) = f1(x'', t'' \oplus \delta t) \quad (i)$$ + +This property can first be used to detect collisions, and then to actually forge new **z1** values. + +To detect a collision, one can test each of the approximately $2^{64} [(x',t');(x'',t'')]$ partial collisions such that $z'1=z''1$ (which can be efficiently enumerated), and then test whether property (i) holds for one or two randomly selected $\delta$ values. This allows to find a full collision on the entire **zz1** output in about $2^{64}$ operations. Once such a collision $[(x',t');(x'',t'')]$ has been detected, property (i) can be used, for any $\delta$ value, to forge $z1(x'', t'' \oplus \delta)$ based on $z1(x', t' \oplus \delta)$ . + +As said before, the above attack is only due to the fact that the **f1** function is essentially a standard CBC MAC. Since the attack requires about $2^{64}$ **f1** outputs corresponding to distinct RAND inputs, it has no practical significance: the use of a **f1** mode essentially equivalent to a standard CBC mode seems appropriate in the 3GPP context of operation. Moreover, we have not identified any simple modification of **f1** allowing to prevent the above internal collisions attack (or a variant) while avoiding the introduction of three invocations of $E_K$ (instead of two) in each **f1** computation. + +#### 10.3.3.2 Forgery or distinguishing attacks against combinations of several modes + +For some particular values of the $r_1$ to $r_5$ and $c_1$ to $c_5$ constants, there may also exist "attacks" against some combinations of several modes requiring about $2^{64}$ queries. + +##### 10.3.3.2.1 Attacks against combinations of **f2-f5** + +*Two of the one-block outputs **zz2** to **zz5** corresponding to two equal or distinct random challenges $x'$ and $x''$ , denoted by **zz'i** and **zz''j** (where $i$ and $j$ are distinct values of the set {2, 3, 4, 5}) are equal iff:* + +$$\text{rot}(y', r_i) \oplus \text{rot}(y'', r_j) = c_i \oplus c_j \oplus \text{rot}(OP_C, r_i) \oplus \text{rot}(OP_C, r_j) \quad (a)$$ + +In the two following particular cases, there exists a simple attack requiring about $2^{64}$ queries + +**Case 1 :** $r_i = r_j$ (i.e. two of the constant rotations are equal) + +The following forgery attack holds in case 1: given a set of $2^{64}$ x inputs and the corresponding $zzi$ and $zzj$ outputs. With a large probability there exist two input values $x'$ and $x''$ such that $zz'i = zz'j$ . It is easy to see, using equation (a) and the fact that $ri=rj$ , that one then also has $zz''i=zz''j$ . In other words, if an adversary finds two $x'$ and $x''$ inputs such that the $zz'i$ and $zz''j$ are equal and obtains the $zz''i$ value corresponding to the $x''$ input, she can forge the $zz'j$ value of $zzj$ corresponding to the $x'$ input. Such a phenomenon would be extremely unlikely to happen if $zzi$ and $zzj$ were the outputs of two independent permutations of x. + +**Case 2 :** $ri - rj = 64 \bmod 128$ and $ci \oplus cj$ belongs to the $\text{Im}[\text{rot}(\cdot, ri) \oplus \text{rot}(\cdot, rj)]$ 64-dimensional vector subspace of $\{0,1\}^{128}$ (for instance, $ri=0$ and $rj=64$ and $ci \oplus cj$ consists of two equal 64-bit halves). + +The following distinguishing attack holds in case 2 : given a set of $2^{64}$ x inputs and the corresponding $zzi$ and $zzj$ outputs. With a large probability, for one of these x values, one has: $zzi = zzj$ . As a matter of fact this equality occurs iff $\text{rot}(y \oplus \text{OP}_C, ri) \oplus \text{rot}(y \oplus \text{OP}_C, rj) = ci \oplus cj$ , and there are $2^{64}$ possible $y \oplus \text{OP}_C$ values satisfying that equation. Such an event would be extremely unlikely to occur if $zzi$ and $zzj$ were the outputs of two independent random permutations of x. + +##### 10.3.3.2.2 Attacks against combinations of f1-f1\* and f2-f5\* + +*A zz'1 value of the zz1 f1-f\*1 output corresponding to a $(x', t)$ input value is equal to a $zz''i$ ( $i \in \{2, 3, 4, 5\}$ ) one-block output of one of the f2-f5\* computations corresponding to a $x''$ input value iff* + +$$y' \oplus \text{rot}(y'', ri) = c1 \oplus ci \oplus \text{rot}(t, r1) \oplus \text{rot}(\text{OP}_C, r1) \oplus \text{rot}(\text{OP}_C, ri) \quad (b)$$ + +As said before, the parities of the c1 to c5 constants prevent equation (b) from being satisfied if $y'=y''$ . In some particular cases, there nevertheless remain simple "attacks", requiring about $2^{64}$ queries. + +**Case 3 :** $ri = 0$ + +The following forgery attack holds in case 3: given a set of $2^{64}$ $(x,t)$ inputs and the corresponding $zz1$ and $zzi$ outputs. With a large probability there exist $x', t'$ and $x''$ such that $zz'1(x',t') = zz''i(x'')$ . It is easy to see, using equation (b) and the fact that $ri=0$ , that one then also has $zz''1(x'',t') = zz''i(x'')$ . This allows to forge $zz''i(x'')$ based on $zz''1(x'',t')$ . If $zz1$ outputs are available instead of entire $zz1$ outputs, the above property still leads to a distinguishing "attack" requiring about $2^{64}$ queries. + +**Case 4 :** $r1 \in \{0, 64\}$ and there exist two distinct values $i, j \in \{2, 3, 4, 5\}$ such that $ci \oplus cj$ consists of two equal 64-bit halves and $ri = rj$ . + +The following forgery attack holds in case 4: given a set of $2^{64}$ $(x,t)$ inputs and the corresponding $zz1$ and $zzi$ outputs. With a large probability there exist $x', ti$ and $x''$ blocks such that $zz'1(x',ti) = zz''i(x'')$ . Let us now replace the $ti$ expanded SQN||AMF sequence by the $tj = ti \oplus ci \oplus cj$ sequence. It is easy to see, using equation (b), that equality $zz''i(x',tj) = zz''j(x'')$ also holds (in other words, a collision between a $zz1$ and a $zzi$ value allows to predict a collision between a $zz1$ value and a $zzj$ value). If $zz1$ outputs are available instead of entire $zz1$ outputs, the above property still leads to a distinguishing "attack" requiring about $2^{64}$ queries. + +#### 10.3.3.3 Conclusion about the identified forgery or distinguishing attacks + +All the attacks listed above require about $2^{64}$ queries, and can be considered highly impractical. None of these "attacks" is stronger than anticipated in the design criteria. It should also be noted that only the internal collision attack of section 10.3.3.1 and Case 3 of the previous section applies to the MILENAGE specifications. + +## 10.4 Statistical evaluation + +The algorithm "MILENAGE" has been designed such that the only cryptographically strong function used to process input depending on a key is the kernel function, which is the block cipher algorithm Rijndael for the example algorithm. All other operations used in the algorithm are XOR, cyclic rotation and splitting/concatenation of bit strings. These operations do not have any cryptographical properties such as confusion or diffusion. Both the designers and evaluators of MILENAGE were thus thoroughly convinced that all statistical tests which are to be performed on MILENAGE only yield results about the underlying kernel function. Since it was not the intention of the task force to evaluate Rijndael, statistical tests have not been performed as a consequence. Care has been taken on the design that the full entropy of the kernel function's outputs is mapped to the outputs of the algorithm (MAC, RES, keys). + +## 10.5 Published attacks on Rijndael + +This section gives a summary of known and published attacks against reduced variants of Rijndael as described in the AES report ref.[12]. + +The Rijndael specification describes a truncated differential attack on 4, 5, and 6 round variants of Rijndael [15], based on a 3 round distinguisher of Rijndael. This attack is called the "Square" attack, named after the cipher on which the attack was first mounted. + +In Ref. [16], truncated differentials are used to construct a different distinguisher on 4 rounds, based on the experimentally confirmed existence of collisions between some partial functions induced by the cipher. This distinguisher leads to a collision attack on 7 round variants of Rijndael. + +The other papers that present attacks on variants of Rijndael build directly on the Square attack. In Ref. [17], the Square attack is extended to 7 round variants of Rijndael by guessing an extra round of subkeys. Table 1 indicates the results for the 192 and 256-bit key sizes, where the total number of operations remains below those required for exhaustive search. Similar attacks are described in Ref. [18]. + +**Table 1: Summary of reported attacks related to Rijndael versions** + +| Reference | Round (Key size) | Type of attack | Texts | Memory | Operations | +|-----------|------------------|-----------------|---------------------|------------------|------------| +| [15] | 4 | Truncated Diff | $2^9$ | small | $2^9$ | +| | 5 | Truncated Diff | $2^{11}$ | small | $2^{40}$ | +| | 6 | Truncated Diff. | $2^{32}$ | $7 \cdot 2^{32}$ | $2^{72}$ | +| [18] | 6 | Truncated Diff. | $6 \cdot 2^{32}$ | $7 \cdot 2^{32}$ | $2^{44}$ | +| | 7 (192) | Truncated Diff. | $19 \cdot 2^{32}$ | $7 \cdot 2^{32}$ | $2^{155}$ | +| | 7 (256) | Truncated Diff | $21 \cdot 2^{32}$ | $7 \cdot 2^{32}$ | $2^{172}$ | +| | 7 | Truncated Diff | $2^{128} - 2^{119}$ | $2^{61}$ | $2^{120}$ | +| | 8 (256) | Truncated Diff | $2^{128} - 2^{119}$ | $2^{101}$ | $2^{204}$ | +| | 9 (256) | Related Key | $2^{77}$ | NA | $2^{224}$ | +| [17] | 7 (192) | Truncated Diff | $2^{32}$ | $7 \cdot 2^{32}$ | $2^{184}$ | +| | 7 (256) | Truncated Diff | $2^{32}$ | $7 \cdot 2^{32}$ | $2^{200}$ | +| | | | $2^{32}$ | $7 \cdot 2^{32}$ | $2^{140}$ | +| [16] | 7 (192, 256) | Truncated Diff | | | | + +It should be noted that many of the reported attacks shown in table 1 are related to versions of Rijndael with larger keylength than used in MILENAGE. + +The attacks reported in ref. [18] are improved by a partial summing technique that reduces the number of operations. The partial summing technique is also combined with a technique for trading off operations for information, yielding attacks on 7 and 8 round variants that require almost the entire codebook. The same paper also presents a related key attack on a 9 round variant with 256-bit keys. This attack requires not only encryptions of chosen plaintexts under the secret key, but also encryptions under 255 other keys that are related to the secret key in a manner chosen by the adversary. + +## 10.6 Complexity evaluation + +### 10.6.1 Complexity of draft Rijndael implementation + +A straightforward implementation result in 8051 assembly language (no optimisations made) without taking advantage of Rijndael's rather particular linear component achieves the following results: + +**RAM:** 48 bytes + +**ROM:** about 1k + +**Cycles:** 30.000 + +Max 6 applications ( $5 + 1$ if OPc is computed on the card at each authentication) of Rijndael are considered: 180.000 + +cycles, which takes 55,38 ms @ 3.25 Mhz. + +### 10.6.2 Estimate complexity of modes + +Once Rijndael is implemented, considering the **f1-f5** construction of the modes, we obtain: + +RAM: + +RAND/E\_K(RAND xor OPc)/IK 16 bytes + +OPc: 16 bytes + +SQN xor AK || AMF || MAC-A / CK / SQN\_MS xor AK\* || AMF\* || MAC-S: 16 bytes + +RES: 8 bytes + +K: 16 bytes + +Total: 72 bytes + +ROM: 5\*200 bytes = 1k + +Cycles: overhead of 5\*15.000 cycles = 75.000 cycles, which gives 23,07 ms overhead @ 3.25 Mhz. + +### 10.6.3 Estimate of total MILENAGE + +RAM: 120 bytes + +ROM: 2k + +Cycles: 255.000, which represents 78,46 ms @ 3.25 Mhz. + +### 10.6.4 SPA/DPA, Timing attack countermeasures + +See Section 10.8 for a wider discussion on these implementation attacks and the possibility for protection against such attacks. + +RAM: additional 280 bytes XRAM + +ROM: no significant change + +Cycles: (180.000 + 75.000)\*3 = 765.000 cycles, which takes 235 ms @ 3.25 Mhz. + +### 10.6.5 Conclusion on algorithm complexity + +The figures given in this section are rough estimates on complexity for a Rijndael kernel with and without full DPA/SPA/TA protections. + +For an unmasked kernel and unmasked modes, the total estimate for the **f1 – f5\*** functions fits into 2k of ROM, using 120 bytes of RAM and executing under 80 ms @ 3.25 Mhz for our draft implementation. This lies well within the required 8k of ROM, 300 bytes of RAM and 500 ms execution time. + +For a masked version of the kernel and modes, the total estimate for the **f1-f5** functions still meets the requirement of 8k of ROM, furthermore executing in less than 235 ms @ 3.25 Mhz for our draft implementation. However, masking techniques such as those described later on in this evaluation report require at least 256 additional bytes of XRAM, which sums up to slightly under 400 bytes of RAM for the kernel and modes." + +Additional comment: The Task Force's expertise is in the design of the specified cryptographic functions. It is not familiar with (and doesn't really want to know) the fine detail of the wider context within the USIM. For example the Task Force do not know the USIM command set; the time involved in getting parameters into and out of the USIM; exactly how the cryptographic functions will be called in an operational environment; whether all results will be calculated at once or whether some results (e.g. CK) will be retrieved before others (e.g. IK) are calculated. + +The Task Force have ensured to the best of its ability that the example algorithm set can be implemented efficiently, and + +that the size and performance parameters lie well within the requirements given in ref [2] to allow for other operational constraints that lie outside of its control. + +## 10.7 External complexity evaluations + +As part of the AES process there have been a number of investigations into physical realisations of Rijndael and these have included implementations for smartcards and protection against DPA. The results of three of these investigations are reproduced here. + +Ref. [10] reports the following results for evaluating the Rijndael algorithm against DPA. The algorithm was implemented on a 32-bit ARM processor, both unmasked and masked against DPA. Security Cost is the ratio of Masked to Unmasked. + +| | Cycle count | RAM (bytes) | ROM (bytes) | +|-----------------------|-------------|-------------|-------------| +| Unmasked | 7.086 | 52 | 1.756 | +| Masked | 13.867 | 326 | 2.393 | +| Security Costs | 1.96 | 6.27 | 1.36 | + +The following results are given in ref. [13] and show the complexity and the performance of Rijndael implemented on a Toshiba T6N55 chip that contains a Z80 microprocessor and a coprocessor on a smart card. Internal means the size of required CRAM for the coprocessor's operations. External means the other work area. + +| | Total RAM | Internal RAM | External RAM | ROM (bytes) | Time (clocks) | +|-----------------|-----------|--------------|--------------|-------------|---------------| +| Encrypt | 34 | 32 | 2 | 700 | 25.494 | +| Schedule | 32 | 32 | 0 | 280 | 10.318 | +| Total | 66 | 64 | 2 | 980 | 35.812 | + +The Rijndael Specification itself, ref. [15], gives the following table for three different implementations on the Intel 8051 microprocessor: + +| Number of Cycles | Code Length (bytes) | +|------------------|---------------------| +| 4065 | 768 | +| 3744 | 826 | +| 3168 | 1016 | + +Ref. [15] also provides the following results for an implementation on a Motorola 68HC08 microprocessor: + +| Number of Cycles | Required RAM(bytes) | Code Length (bytes) | +|------------------|---------------------|---------------------| +| 8390 | 36 | 919 | + +## 10.8 Evaluation of side channel attacks + +In this section we will focus on the resistance of MILENAGE against side-channel attacks, or 'implementation attacks', i.e. attacks which make use of an additional (physical) information channel [7] through which secrets might leak. These additional channels include, but are not limited to, timing measurements [6], power consumption [8], [9], [10], [11] electromagnetic radiation, etc. + +### 10.8.1 Evaluation of the kernel algorithm + +Rijndael has been chosen as a kernel function for the 3GPP authentication algorithm. As most block ciphers, it uses simple linear operations such as bit shifts and rotations, exclusive or operations, as well as substitutions through a non linear 8 by 8 bit S-box. + +Similarly to DES, Rijndael is vulnerable to SPA (Simple Power Analysis), DPA (Differential Power Analysis) and timing attacks. These attacks may however be thwarted by using adequate software and hardware protections on the mobile station. Note however that some techniques and/or methods for such protections might be subject to pending patents. + +#### 10.8.1.1 Timing Attacks + +We refer to [6] for a complete description of timing attacks. In the case of Rijndael, the most vulnerable operation is the polynomial remaindering over $GF(2^8)$ . In practice, this operation is implemented either by a 1-bit shift to the left, followed by a conditional exclusive-or with the modulus, or by a conditional table look-up. In both cases, the 'if' operation may leak information on intermediate results, and thus reveal parts of the secret key. + +Therefore, care should be taken to ensure that this operation is implemented in constant time using operations that are the same, whatever the intermediate result. In particular, no 'if', 'case' or otherwise conditional 'jump' and 'call' instructions should be used. The MixColumn routine shall be implemented in an 'operation constant' way. + +In this way, efficient protection against timing attacks is easily achieved. + +#### 10.8.1.2 Simple Power Analysis + +Every block cipher is vulnerable to Simple Power Analysis. We refer to [9] and [10] for a complete description of this attack. In a very simple approach, an attacker monitors the power consumption curves of the device while executing cryptographic operations on different input data. The overall form of the curve reveals which actual data are being manipulated, thus leaking information on the secret key. This kind of attack may be thwarted by appropriate hardware countermeasures such as random noise generators or current scramblers on the device. Ad-hoc wait states or dummy instruction routines may be added in order to confuse the 'visual' analysis as much as possible. + +It is a simple matter to provide good resistance against Simple Power Analysis. + +#### 10.8.1.3 Differential Power Analysis + +We refer to [8], [9], [10] and [11] for a detailed description of Differential Power Analysis. Rijndael, as many other block ciphers is vulnerable to DPA. In particular, bytewise key-addition followed by a non-linear substitution table is generally enough to attack a block cipher successfully, meaning that the entire secret key may be recovered using a few hundred power curves. The attacker defines a selection function, which consists for example in one output bit of the non-linear S-box. The differential attack proceeds as follows: + +- Guess the value of a given secret key byte. +- Using knowledge of the input (or output) data, compute the estimated one-bit result of the substitution of the input byte exclusive-ored with the key byte, according to the selection function. +- Sort the power curves according to the one-bit result and compute the mean of all curves in each of the two resulting sets. +- Subtract the two means and visualise the resulting curve. +- Repeat for all key guesses. +- For at most a few key guesses, the resulting curve will show a DPA 'peak' (whereas all other curves will be completely flat). These key guesses comprise the right key byte. +- Iterate on other key bytes and complete the whole secret key by exhaustive search as appropriate. + +In the case of Rijndael, the secret key may be found byte by byte using a few hundred curves. Thus Rijndael is as vulnerable to DPA as DES. + +We refer to [8], [10] and [11] for protections and countermeasures against this attack. All input data as well as the secret key may be masked by a random value throughout the cryptographic computations. Special care should be taken when handling the S-box, as this component is non-linear. Following [10], a boolean masked table $S'$ can be defined in terms of $S$ , and of the input and output masks $r\_in$ and $r\_out$ , such that $S'[x] = S[x \oplus r\_in] \oplus r\_out$ . This masked table $S'$ takes inputs that are masked with $r\_in$ and produces outputs that are masked with $r\_out$ . Thus the look-up operation is convertible into an operation which can 'handle' random boolean masks. All other components in Rijndael are linear and are thus not affected by the random masks. + +The masks should be refreshed at every execution on different input data, in order to decorrelate every cryptographic operation from the actual value of the manipulated bytes. Together with hardware countermeasures against SPA, these protections should achieve a reasonable level of security against first order power attacks. + +#### 10.8.1.4 Other side channels + +Other side channels such as carry bit propagation analysis or differential electromagnetic radiation or IPA (Inferential Power Analysis) are still under investigation in the open literature and are thus not addressed in this evaluation report. + +### 10.8.2 Evaluation of the f1-f5 modes + +The authentication and key derivation modes use Rijndael as the kernel function. As such, these modes are equally vulnerable to the different power and timing attacks. They can be efficiently protected by the same methods as for the kernel function itself. In particular, random boolean masking should also be applied to each function individually, not only to the underlying kernel. + +#### 10.8.2.1 Operator Constants (OP or OPc) + +The use of secret operator constants enables to mask the real inputs to the kernel function, but side-channel attacks may still be applied to recover the exclusive or between these constants and the first round-key of the kernel. Subsequently, the second round-key may be derived and finally the original key may be recovered. + +Thus, the operator constants have the effect of transforming a straightforward known plaintext attack into a slightly but not significantly more complex attack. Care should be taken to protect the operator constants as well as the secret key of the block cipher itself. This is achieved using above mentioned masking techniques. + +#### 10.8.2.2 Rotations and constants + +These values are meant to be publicly defined and need not be protected in any way. However, if an operator chooses to diversify them, computations involving the rotations and constants should also be protected against timing and power attacks using previously mentioned techniques. + +### 10.8.3 Conclusion on side channel attacks + +Rijndael as a kernel function is vulnerable to side-channel attacks but may be efficiently protected against these attacks on the USIM. The modes do not add any security with respect to this kind of attacks and in case secret values such as an operator constant, rotations and other constants are used, it is strongly advised to protect them by random boolean masking together with the kernel function. + +# --- 11 Conclusions + +The MILENAGE algorithm set forms a complete set of cryptographic functions suitable for use in the 3GPP authentication framework. It constitutes a well-founded architecture based upon a highly trusted kernel and achieves all goals related to efficiency and security. The design supports the possibility for operator specific modifications by introduction of dedicated parameters and interchangeable modules. + +The combination of the mathematical analysis carried out by the ETSI SAGE Task Force and related external evaluation results support the soundness of the design. This report includes a description of certain forgery attacks with complexity lower than the security level set by the 128 bits subscriber key, but it is explained that these attacks have been considered during the design process and are not considered to be feasible within the operational context of 3GPP. + +The Task Force has specifically considered the threat of different side channel attacks and the report provides references to several techniques that can be used to ensure that MILENAGE can be implemented in a way that protect the USIM. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|------------|----|-----------|---------------|-------------------------------------------| +| TSG SA # | Version | CR | Tdoc SA | New Version | Subject/Comment | +| SP-11 | SAGE v 1.0 | - | SP-010144 | 4.0.0 | Approved as Release 4 | +| SP-16 | 4.0.0 | - | - | 5.0.0 | Release 5 version created | +| SP-26 | 5.0.0 | - | - | 6.0.0 | Release 6 version created | +| SP-36 | 6.0.0 | - | - | 7.0.0 | Release 7 version created | +| SP-42 | 7.0.0 | - | - | 8.0.0 | Release 8 version created | +| SP-46 | 8.0.0 | - | - | 9.0.0 | Release 9 version created | +| SP-51 | 9.0.0 | - | - | 10.0.0 | Updated to Release 10 | +| 2012-09 | - | - | - | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | - | - | - | 12.0.0 | Update to Rel-12 version (MCC) | +| 2016-01 | 12.0.0 | - | - | 13.0.0 | Update to Rel-13 version (MCC) | + +| 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 | - | - | - | - | - | Update to Rel-15 version (MCC) | 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/35_series/35919/raw.md b/marked/Rel-16/35_series/35919/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6f0a78d66322d420dd8797fe4885e0d2b3afe213 --- /dev/null +++ b/marked/Rel-16/35_series/35919/raw.md @@ -0,0 +1,91 @@ + + + + + + +# --- Contents + +- Foreword ..... 5 +- 1 Scope..... 6 +- 2 References..... 6 +- 3 Definitions, symbols and abbreviations..... 6 + - 3.1 Definitions..... 6 + - 3.2 Symbols..... 6 + - 3.3 Abbreviations ..... 6 +- 4 Technical provisions ..... 6 +- Annex A: Change history..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the 3GPP confidentiality and integrity algorithms known as UEA2 and UIA2. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE Specification: "Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 5: Design and evaluation report" version 1.1, 2006-09-06 + +NOTE: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A: Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|-----|-----|---------------------------------------------------------------------|--------|---------------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 2006-10 | | | | | Draft document from ETSI SAGE | | 0.1.0 | | +| 2006-03 | SP-31 | | | | For information to TSG SA. | 0.1.0 | 1.0.0 | | +| 2006-03 | | | | | 3GPP Support Team recast of document to refer to SAGE Specification | 1.0.0 | 1.1.0 | | +| 2006-06 | | | | | Correction of typographical error. | 1.1.0 | 1.1.1 | | +| 2006-06 | SP-32 | SP-060422 | - | - | Approved at SA #32 | 1.1.1 | 7.0.0 | | +| 2008-12 | SP-42 | - | - | - | Upgrade to Release 8 | 7.0.0 | 8.0.0 | | +| 2010-03 | -- | -- | -- | -- | Upgrade to Release 9 | 8.0.0 | 9.0.0 | | +| 2010-12 | SP-50 | SP-100724 | 001 | 1 | Correction of reference | 9.0.0 | 9.1.0 | | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.1.0 | 10.0.0 | | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35924/raw.md b/marked/Rel-16/35_series/35924/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d326eb90ded1e11a32b74cf9e72bc8f95909dc60 --- /dev/null +++ b/marked/Rel-16/35_series/35924/raw.md @@ -0,0 +1,86 @@ + + + + + + +# --- 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 Technical provisions ..... | 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 3GPP confidentiality and integrity algorithms known as EEA3 and EIA3. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +[2] ETSI TC SAGE: "Specification of the 3GPP Confidentiality and Integrity Algorithms 128-EEA3 & 128-EIA3; Document 4; Design and Evaluation Report" version 2.0. + +NOTE: Reference [2] is available via and is subject to licensing conditions described at this site. + +# --- 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 in the SAGE Specification [2] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Symbols + +For the purposes of the present document, the symbols defined in the SAGE Specification [2] apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the SAGE Specification [2] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +# --- 4 Technical provisions + +The technical provisions of the current document are contained in the SAGE Specification [2]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|----|-----|--------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2011-11 | SA-54 | SP-110689 | -- | -- | Submission for Information and Approval | --- | 1.0.0 | +| 2012-01 | -- | -- | -- | -- | Publication | 1.0.1 | 11.0.0 | +| 2012-05 | -- | -- | -- | -- | Reference 2 now to specific version | 11.0.0 | 11.0.1 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.1 | 12.0.0 | +| 2016-01 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | SA#75 | - | - | - | Promotion to Release 14 without technical change | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35934/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/35_series/35934/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a260d07cbe59b912d8a23b5f4462d263f11c75d3 --- /dev/null +++ b/marked/Rel-16/35_series/35934/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd05420cf138bef3bd602d5c363e5974417b133d4dbbbc9e724952274d53057d +size 51580 diff --git a/marked/Rel-16/35_series/35934/raw.md b/marked/Rel-16/35_series/35934/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d34dcacacdc4bfc9bccc229826c3106009a5716d --- /dev/null +++ b/marked/Rel-16/35_series/35934/raw.md @@ -0,0 +1,535 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Structure of this report ..... | 8 | +| 5 Background to the design and evaluation work ..... | 8 | +| 6 Summary of algorithm requirements ..... | 9 | +| 6.0 Introduction ..... | 9 | +| 6.1 General requirements for 3GPP cryptographic functions and algorithms (as stated for MILENAGE) ..... | 9 | +| 6.2 Authentication and key agreement functions (as stated for MILENAGE) ..... | 9 | +| 6.2.0 Introduction ..... | 9 | +| 6.2.1 Implementation and operational considerations ..... | 10 | +| 6.2.2 Type of algorithm ..... | 10 | +| 6.2.2.1 $f1$ ..... | 10 | +| 6.2.2.2 $f1^*$ ..... | 10 | +| 6.2.2.3 $f2$ ..... | 10 | +| 6.2.2.4 $f3$ ..... | 10 | +| 6.2.2.5 $f4$ ..... | 10 | +| 6.2.2.6 $f5$ ..... | 11 | +| 6.2.2.7 $f5^*$ ..... | 11 | +| 6.3 Tuak-specific requirements ..... | 11 | +| 6.3.1 Difference from MILENAGE ..... | 11 | +| 6.3.2 256-bit key support..... | 11 | +| 6.3.3 Operator customization ..... | 11 | +| 6.3.4 Implementation and operational considerations ..... | 12 | +| 7 Overview of the Tuak design ..... | 12 | +| 8 Design rationale ..... | 13 | +| 8.0 Introduction ..... | 13 | +| 8.1 Brand new design, or design based on an existing public algorithm? ..... | 13 | +| 8.2 Block cipher, stream cipher, MAC or hash function?..... | 13 | +| 8.3 Which hash function?..... | 13 | +| 8.4 What sort of Keccak function to use ..... | 14 | +| 8.5 Keccak parameter selection..... | 14 | +| 8.6 Security evaluation of Keccak..... | 15 | +| 8.6.0 Introduction ..... | 15 | +| 8.6.1 What about the internet stories about NIST weakening SHA-3?..... | 15 | +| 8.7 A note on IPR..... | 16 | +| 8.7.1 Keccak IPR..... | 16 | +| 8.7.2 Tuak IPR..... | 16 | +| 8.8 Padding bits ..... | 16 | +| 8.9 Flexible input and output sizes..... | 16 | +| 8.10 Operator customization ..... | 16 | +| 9 Independent security and performance evaluation..... | 17 | +| 9.0 Introduction ..... | 17 | +| 9.1 Independent security evaluation..... | 17 | +| 9.2 Independent SIM card performance evaluation ..... | 17 | +| 10 More notes on implementation and side channel attacks..... | 18 | +| 10.1 Protecting implementations against side channel attacks ..... | 18 | +| 10.2 Software implementation and the NIST SHA-3 standard..... | 18 | + +11 Conclusions..... 18 + +Annex A: Change history..... 19 + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document (together with three accompanying documents, [8], [9] and [10] describes the design rationale, and presents evaluation results, on the Tuak algorithm set [5] – a second example set of algorithms which may be used as the authentication and key generation functions *f1, f1\*, f2, f3, f4, f5* and *f5\**, e.g. as an alternative to MILENAGE. + +# 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 33.102: "3G Security; Security Architecture", (available at ). +- [3] 3G TS 33.105 (V 3.4.0) (2000-07): "3G Security; Cryptographic Algorithm Requirements (Release 1999)". +- [4] 3GPP TS 35.206: "3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm specification", (available at ). +- [5] 3GPP TS 35.231: "3G Security; Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: Algorithm specification", (available at ). +- [6] 3GPP TS 35.232: "3G Security; Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Implementers' Test Data", (available at ). +- [7] 3GPP TS 35.233: "3G Security; Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 3: Design Conformance Test Data", (available at ). +- [8] "Security Assessment of Tuak Algorithm Set", Guang Gong, Kalikinkar Mandal, Yin Tan and Teng Wu, included as an accompanying document to the present report (available at [http://www.3gpp.org/ftp/Specs/archive/35\\_series/35.935/SAGE\\_report/Secassessment.zip](http://www.3gpp.org/ftp/Specs/archive/35_series/35.935/SAGE_report/Secassessment.zip)). +- [9] "Performance Evaluation of the Tuak algorithm in support of the ETSI SAGE standardisation group", Keith Mayes, included as an accompanying document to the present report (available at [http://www.3gpp.org/ftp/Specs/archive/35\\_series/35.936/SAGE\\_report/Perfevaluation.zip](http://www.3gpp.org/ftp/Specs/archive/35_series/35.936/SAGE_report/Perfevaluation.zip)). +- [10] "Performance Evaluation of the Tuak algorithm in support of the ETSI SAGE standardisation group – extension report", Keith Mayes, included as an accompanying document to the present report (available at [http://www.3gpp.org/ftp/Specs/archive/35\\_series/35.936/SAGE\\_report/Perfevaluationext.zip](http://www.3gpp.org/ftp/Specs/archive/35_series/35.936/SAGE_report/Perfevaluationext.zip)). +- [11] "Note on side-channel attacks and their countermeasures", G. Bertoni, J. Daemen, M. Peeters, G. van Assche (available at ). + +- [12] "Building power analysis resistant implementations of Keccak", G. Bertoni, J. Daemen, M. Peeters, G. van Assche (available at [http://csrc.nist.gov/groups/ST/hash/sha-3/Round2/Aug2010/documents/papers/BERTONI\\_KeccakAntiDPA.pdf](http://csrc.nist.gov/groups/ST/hash/sha-3/Round2/Aug2010/documents/papers/BERTONI_KeccakAntiDPA.pdf)). +- [13] Wassenaar Arrangement on Export Controls for Conventional Arms and Dual-Use Goods and Technologies, . +- [14] "Announcing Draft Federal Information Processing Standard (FIPS) 202, SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions, and Draft Revision of the Applicability Clause of FIPS 180-4, Secure Hash Standard, and Request for Comments", NIST, 28th May 2014, available at . +- [15] "Early Symmetric Crypto (ESC) seminar 2013" (available at [https://www.cryptolux.org/mediawiki-esc2013/index.php/ESC\\_2013](https://www.cryptolux.org/mediawiki-esc2013/index.php/ESC_2013) ) +- [16] "The KECCAK sponge function family" (available at ) +- [17] +- [18] +- [19] [https://www.schneier.com/blog/archives/2013/10/will\\_keccak\\_sha-3.html](https://www.schneier.com/blog/archives/2013/10/will_keccak_sha-3.html) +- [20] [http://keccak.noekeon.org/yes\\_this\\_is\\_keccak.html](http://keccak.noekeon.org/yes_this_is_keccak.html) + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Keccak:** algorithm selected as the winner of the SHA-3 competition + +**MILENAGE:** previously designed example algorithm set for the 3GPP Authentication and Key Generation Functions + +**TOPC:** value derived from TOP and K and used within the computations of the functions $f1$ , $f1^*$ , $f2$ , $f3$ , $f4$ , $f5$ and $f5^*$ + +**Tuak:** newly designed example algorithm set for the 3GPP Authentication and Key Generation Functions. It should be pronounced like "too-ack" + +## 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]. + +| | | +|-------|-------------------------------------------| +| AES | Advanced Encryption Standard block cipher | +| AK | Anonymity Key | +| AMF | Algorithm Management Field | +| AuC | Authentication Centre | +| CK | Cipher Key | +| CPU | Central Processing Unit | +| DEMA | Differential Electromagnetic Analysis | +| DPA | Differential Power Analysis | +| IC | Integrated Circuit | +| IK | Integrity Key | +| K | Long lived subscriber unique key | +| MAC | Message Authentication Code | +| MAC-A | MAC for normal authentication vectors | +| MAC-S | MAC for resynchronization vectors | + +| | | +|--------|-----------------------------------------------------------------------| +| MULTOS | Multi-application smart card operating system | +| NIST | National Institute of Standards and Technology | +| NSA | National Security Agency | +| NVM | Non-Volatile Memory | +| RAM | Random Access Memory | +| RAND | Random input parameter to authentication and key generation functions | +| RES | Response value | +| RNC | Radio Network Controller | +| ROM | Read-Only Memory | +| SAGE | Security Algorithms Group of Experts | + +NOTE: This is an ETSI Technical Committee. + +| | | +|-------|-------------------------------------------------------| +| SHA-2 | Secure Hash Algorithm already standardized by NIST | +| SHA-3 | Secure Hash Algorithm soon to be standardized by NIST | +| TOP | Tuak Operator Variant Algorithm Configuration Field | +| SEMA | Simple Electromagnetic Analysis | +| SIM | Subscriber Identity Module | +| SPA | Simple Power Analysis | +| SQN | Sequence Number | +| UICC | Universal Integrated Circuit Card | +| USIM | Universal Subscriber Identity Module | +| XMAC | Expected MAC value | + +# 4 Structure of this report + +The main content of the present document is organized as follows: + +- Clause 5 and 6 give the requirements and background that were considered during the design of Tuak – first recalling the functional and performance requirements that were used for MILENAGE, then noting some differences and additional points that apply for Tuak. +- Clause 7 gives a brief overview of the Tuak design. +- Clause 8 runs through choices made during the design of Tuak, and the reasons behind those choices. +- Clause 9 introduces independent assessments that have been carried out on the security and performance of Tuak. The full independent assessment reports are included as companion documents to this one. +- Clause 10 gives some further observations on software implementation and protection against side channel attacks. +- Clause 11 concludes with an overall assessment of Tuak's fitness for purpose. + +Three further documents [8], [9] and [10] complete the present document, as explained in clause 9. + +# 5 Background to the design and evaluation work + +The 3rd Generation Partnership Project (3GPP) is a global initiative dedicated to the development of specifications for the next generations of cellular mobile systems. Integration of strong security services is an important feature of this system and the general security architecture is defined in ref. [2]. The implementation of these security services should be based on a variety of cryptographic functions/algorithms. + +Out of the full algorithm suite, only the UMTS encryption algorithms (*f8*) and the UMTS integrity algorithms (*f9*) are fully standardized. *f10* represents a random number generation algorithm, and has no standardization or interoperability requirements at all. The remaining cryptographic functions for authentication and key agreement (*f1* – *f5\**) are allocated to the Authentication Centre (AuC) and the USIM; this means that the functions are proprietary to the home environment, and there is no need for formal standardization of these algorithms. However, there are good reasons to have a well trusted example set of functions available for this purpose, for use by operators that choose not to develop their own solutions. The MILENAGE algorithm set [4] was created to meet this need. + +There are also good reasons to have a second trusted example set of (*f1* – *f5\**) algorithms available: + +- To have a fallback already in place in case MILENAGE is ever compromised. +- In particular, for the embedded UICC, where it may be sensible to have two strong algorithms installed on the platform and available for selection by subsequently loaded USIM applications. This provides choice to operators; it also provides resilience against future cryptanalysis of either algorithm, in devices that may have a long lifetime in the field. + +The Tuak algorithm set [5], [6] and [7] has been created to serve as this second trusted example algorithm set. + +# --- 6 Summary of algorithm requirements + +## 6.0 Introduction + +When MILENAGE was created, the requirements specification was taken from [3]. Clauses 6.1 and 6.2 below reproduce the main requirements necessary to understand the present document. Clause 6.3 describes some new requirements that came into play when designing Tuak. + +## 6.1 General requirements for 3GPP cryptographic functions and algorithms (as stated for MILENAGE) + +The functions should be designed with a view to their continued use for a period of at least 20 years. Successful attacks with a workload significantly less than exhaustive key search through the effective key space should be impossible. + +The designers of above functions should design algorithms to a strength that reflects the above qualitative requirements. + +Legal restrictions on the use or export of equipment containing cryptographic functions may prevent the use of such equipment in certain countries. + +It is the intention that UE and USIMs that embody such algorithms should be free from restrictions on export or use, in order to allow the free circulation of 3G terminals. Network equipment, including RNC and AuC, may be expected to come under more stringent restrictions. It is the intention that RNC and AuC that embody such algorithms should be exportable under the conditions of the Wassenaar Arrangement, see reference [13]. + +## 6.2 Authentication and key agreement functions (as stated for MILENAGE) + +### 6.2.0 Introduction + +The mechanisms for authentication and key agreement described in clause 6.3 of [2] require the following cryptographic functions: + +- f1* The network authentication function; +- f1\** The re-synchronization message authentication function; +- f2* The user authentication function; +- f3* The cipher key derivation function; +- f4* The integrity key derivation function; +- f5* The anonymity key derivation function; +- f5\** The anonymity key derivation function for re-synchronization. + +### 6.2.1 Implementation and operational considerations + +The functions $f1-f5^*$ should be designed so that they can be implemented on an IC card equipped with an 8-bit microprocessor running at 3,25 MHz with 8 kbyte ROM and 300 byte RAM and produce AK, XMAC-A, RES, CK and IK in less than 500 ms execution time. + +#### 6.2.2 Type of algorithm + +##### 6.2.2.1 $f1$ + +$f1$ : the network authentication function + +$f1: (K; SQN, RAND, AMF) \rightarrow \text{MAC-A (or XMAC-A)}$ + +$f1$ should be a MAC function. In particular, it should be computationally infeasible to derive K from knowledge of RAND, SQN, AMF and MAC-A (or XMAC-A). + +##### 6.2.2.2 $f1^*$ + +$f1^*$ : the re-synchronization message authentication function + +$f1^*: (K; SQN, RAND, AMF) \rightarrow \text{MAC-S (or XMAC-S)}$ + +$f1^*$ should be a MAC function. In particular, it should be computationally infeasible to derive K from knowledge of RAND, SQN, AMF and MAC-S (or XMAC-S). + +##### 6.2.2.3 $f2$ + +$f2$ : the user authentication function + +$f2: (K; RAND) \rightarrow \text{RES (or XRES)}$ + +$f2$ should be a MAC function. In particular, it should be computationally infeasible to derive K from knowledge of RAND and RES (or XRES). + +##### 6.2.2.4 $f3$ + +$f3$ : the cipher key derivation function + +$f3: (K; RAND) \rightarrow \text{CK}$ + +$f3$ should be a key derivation function. In particular, it should be computationally infeasible to derive K from knowledge of RAND and CK. + +##### 6.2.2.5 $f4$ + +$f4$ : the integrity key derivation function + +$f4: (K; RAND) \rightarrow \text{IK}$ + +$f4$ should be a key derivation function. In particular, it should be computationally infeasible to derive K from knowledge of RAND and IK. + +##### 6.2.2.6 $f5$ + +$f5$ : the anonymity key derivation function + +$f5: (K; RAND) \rightarrow \text{AK}$ + +$f5$ should be a key derivation function. In particular, it should be computationally infeasible to derive K from knowledge of RAND and AK. + +The use of $f5$ is optional. + +##### 6.2.2.7 $f5^*$ + +$f5^*$ : the anonymity key derivation function for re-synchronization + +$f5^*$ : $(K; RAND) \rightarrow AK$ + +$f5^*$ should be a key derivation function. In particular, it should be computationally infeasible to derive $K$ from knowledge of $RAND$ and $AK$ . + +The use of $f5^*$ is optional. + +## 6.3 Tuak-specific requirements + +### 6.3.1 Difference from MILENAGE + +It is important that this new algorithm should be fundamentally different from MILENAGE, in such a way that any advance in cryptanalysis that impact the security of one algorithm set should be unlikely to impact the security of the other. + +### 6.3.2 256-bit key support + +MILENAGE was designed for UMTS, before LTE had been standardized. UMTS supports only a 128-bit $K$ value, but LTE allows $K$ to be either 128 or 256 bits long. It was therefore felt highly desirable for Tuak to accommodate either a 128-bit or a 256-bit $K$ . + +### 6.3.3 Operator customization + +MILENAGE allows some customization by each mobile operator. In particular, each operator needs to choose its own value of an "Operator Variant Algorithm Configuration Field" called OP. There are also other constants within the MILENAGE algorithm that can be varied if required. This operator customization serves two main purposes: + +- It means that USIMs for different operators are not interchangeable, either through trivial modification of inputs and outputs or by reprogramming of a blank USIM. +- By keeping some algorithm details secret, some attacks (such as side channel attacks like power analysis) become a little harder to carry out. + +This operator customization was not a required feature when MILENAGE was being design, but it has been well received by operators. It was therefore felt desirable to include a similar operator customization feature in Tuak. + +### 6.3.4 Implementation and operational considerations + +The performance and complexity requirements stated at the time of the MILENAGE design stipulate a maximum run time of 500 ms on "an IC card equipped with an 8-bit microprocessor running at 3,25 MHz with 8 kbyte ROM and 300 byte RAM". As noted in [9], however: + +Technology has moved on quite significantly and it might be quite hard to even find a SIM chip that has these minimal capabilities, and indeed many do not have ROM any more. Furthermore the target is a little ambiguous and could be interpreted that if you ran all the functions in sequence each could take 500 ms. It is also not clear how much of the ROM and RAM can be used. A more appropriate and modern target could be: + +*"The functions $f1$ – $f5$ and $f1^*$ should be designed so that they can be implemented on a midrange microprocessor IC card (typically 16-bit CPU), occupying no more than 8kbytes nonvolatile-memory (NVM), reserving no more than 300 bytes of RAM and producing $AK$ , $XMACA$ , $RES$ , $CK$ and $IK$ in less than 500 ms total execution time."* + +# --- 7 Overview of the Tuak design + +The detailed specifications of the 3GPP Tuak algorithms can be found in [5]. The following diagram illustrates the design of the Tuak algorithms. See clause 8.10 for an explanation of TOP and TOPC. + +![Figure 1: Three diagrams showing the input and output of a Keccak function. The first diagram shows inputs: INSTANCE (TOP, ALGONAME), ZEROES, K, PADDING, and 512 ZEROES entering a Keccak block, with TOP_C as output. The second diagram shows inputs: INSTANCE (TOP_C, ALGONAME), RAND (AMF, SQN), K, PADDING, and 512 ZEROES entering a Keccak block, with MAC as output. The third diagram shows inputs: INSTANCE (TOP_C, ALGONAME), RAND (ZEROES), K, PADDING, and 512 ZEROES entering a Keccak block, with RES, CK, IK, and AK as outputs.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The figure consists of three vertically stacked diagrams, each showing a 'Keccak' processing block. Each block is a horizontal rectangle divided into two parts: a white left part and a grey right part. Arrows from labels above point into the white part, and arrows from the bottom point out of it. + +- Top Diagram:** Inputs are 'INSTANCE' (split into 'TOP' and 'ALGONAME'), 'ZEROES', 'K', 'PADDING', and '512 ZEROES'. The output is 'TOPC'. +- Middle Diagram:** Inputs are 'INSTANCE' (split into 'TOPC' and 'ALGONAME'), 'RAND' (split into 'AMF' and 'SQN'), 'K', 'PADDING', and '512 ZEROES'. The output is 'MAC'. +- Bottom Diagram:** Inputs are 'INSTANCE' (split into 'TOPC' and 'ALGONAME'), 'RAND' (split into 'ZEROES'), 'K', 'PADDING', and '512 ZEROES'. The outputs are 'RES', 'CK', 'IK', and 'AK'. + +Figure 1: Three diagrams showing the input and output of a Keccak function. The first diagram shows inputs: INSTANCE (TOP, ALGONAME), ZEROES, K, PADDING, and 512 ZEROES entering a Keccak block, with TOP\_C as output. The second diagram shows inputs: INSTANCE (TOP\_C, ALGONAME), RAND (AMF, SQN), K, PADDING, and 512 ZEROES entering a Keccak block, with MAC as output. The third diagram shows inputs: INSTANCE (TOP\_C, ALGONAME), RAND (ZEROES), K, PADDING, and 512 ZEROES entering a Keccak block, with RES, CK, IK, and AK as outputs. + +Figure 1 + +# 8 Design rationale + +## 8.0 Introduction + +This clause outlines the decision process that led to the Tuak design. + +## 8.1 Brand new design, or design based on an existing public algorithm? + +For obvious reasons of confidence in the design – both SAGE's confidence and the public's confidence – it was preferable to base the new authentication and key agreement algorithm on a well studied existing public algorithm. + +## 8.2 Block cipher, stream cipher, MAC or hash function? + +While it is possible in principle to use a public key algorithm as a building block, this would intuitively be a strange choice in a naturally symmetric key context, and a brief analysis indicated only disadvantages. So in practice it makes sense to take a symmetric key or keyless algorithm as the starting point. + +Stream ciphers would be a poor fit here – they typically need a pre-run before output can be extracted, making them expensive for short data sizes, even though they may be very efficient for large quantities of data. And there are no dedicated MAC functions (as opposed to e.g. block ciphers in a MAC mode) with enough public trust. So, realistically, the candidate building blocks are block ciphers or hash functions. + +At first glance, block ciphers might seem a more natural starting point, since it might be possible to slot them directly into the MILENAGE framework, in place of AES. But after looking at the obvious choices of well established public domain block ciphers, it appeared that they all had limitations: + +- CAMELLIA, SERPENT and ARIA all seem too close to AES – if an advance in cryptanalytic theory threatens AES, it was thought too likely that it would threaten these algorithms too. One of SAGE's fundamental design goals was to avoid this. +- IDEA, SEED and TEA / XTEA don't support a 256-bit key. Accommodating a 256-bit key was considered desirable, since LTE allows that. +- CAST, CLEFIA and RC6 seemed to be encumbered with IPR. SAGE preferred to choose a building block that was open for public use without IPR considerations. +- BLOWFISH and TWOFISH use key dependent S-boxes, which SAGE felt were likely to add implementation or computational overheads. +- MARS was felt by many commentators during the AES competition not to be well suited for smart card implementation. + +Note that there is no need for any decryption process as part of the authentication and key agreement algorithm. A one-way function, such as a hash function, is fine for this purpose. + +So SAGE determined on a hash function as the best type of building block to use. + +## 8.3 Which hash function? + +The ideal starting point would be a hash function that was well studied, reasonably efficient, and appeared to have a good security margin. When SAGE began the design process, the SHA-3 competition was still under way, with five finalists selected (BLAKE, Grøstl, JH, Keccak and Skein); the other natural candidate was SHA-2. Grøstl was quickly dismissed as being too close to AES. Once Keccak was selected as the SHA-3 winner, however, it would have been perverse to choose any of the other SHA-3 finalists without a clear reason to do so, and there was no such clear reason – Keccak seemed an excellent candidate for our purposes. So, SAGE's choice was between Keccak and SHA-2. + +Either of Keccak or SHA-2 would have been a good choice for the core building block. Referring back to the reasons above for rejecting various block ciphers, it was noted that both Keccak and SHA-2 are very different from AES in their designs; can easily accommodate a 256-bit key; are believed to be free of restrictive IPR; and could be reasonably compact and efficient on smartcard platforms. There were arguments in favour of each: + +- SHA-2 had been in the public eye for longer. However, Keccak was more intensively scrutinised during the SHA-3 competition. +- More implementations were available for SHA-2. +- Keccak could become a particular focus for attack after being announced as the SHA-3 winner. +- Keccak's recommended MAC construction is simpler and more efficient than the HMAC construction that would normally be used to create a MAC from SHA-2. (Simpler MAC constructions are possible for SHA-2, and would in practice be fine for our purposes ... but would be less well trusted than HMAC.) +- There were already publications showing how to realize Keccak in a way that protects against side channel attacks, with a modest implementation overhead. Protecting SHA-2 against side channel attacks seemed less straightforward, and the complexity of doing so less clear. Side channel attacks are of course very important for USIM-based authentication and key agreement algorithms. Clause 9 gives more information about this subject. +- Although both SHA-2 and Keccak currently seem to have a good security margin, the design philosophy and security arguments for Keccak are significantly clearer. +- The large input and output size of the Keccak permutation allow a very simple, one-round construction. + +The SAGE chairman took the opportunity to canvas the opinion of a number of eminent symmetric cryptography specialists, at the Early Symmetric Crypto conference [15]. A substantial majority expressed a preference for Keccak as the more robust choice with the sounder security justification (and that is true even excluding the Keccak designers who were there.). + +## 8.4 What sort of Keccak function to use + +Keccak is a family of "cryptographic sponge functions" [16]. Each instance of Keccak has a particular permutation at its core. The SHA-3 submission takes a particular permutation from this family, and proposes a hash function based on the sponge paradigm. + +SAGE could have waited for the SHA-3 standard to be published, and used SHA-3 in its entirety as a building block for Tuak. There might have been some advantage in doing so, in terms of public trust in the design. This would have entailed a long delay, however: NIST did not publish their draft SHA-3 standard until May 2014 [14], with public comments invited until August 2014, and the final standard to appear some time later. Moreover, using the exact input/output interface of SHA-3 would probably make the design significantly more complicated than it needed to be. SAGE decided instead to base our design on the Keccak sponge function, which in practice is what provides all the security assurance for SHA-3. + +## 8.5 Keccak parameter selection + +Keccak permutations are available in seven different sizes, operating on blocks of 25, 50, 100, 200, 400, 800 or 1600 bits. For the sizes of input and output parameters needed for Tuak, 800-bit or 1600-bit block sizes were the only two worthy of consideration. + +Once a block size $B$ is chosen, there are two further parameters in the choice of Keccak function, called the rate $R$ and the capacity $C$ , with the constraint that $R + C = B$ . The capacity $C$ is a security parameter: to achieve 256-bit security against all attacks (reflecting the maximum subscriber key size of 256 bits in LTE), it is necessary to choose a capacity of at least $2 \times 256 = 512$ . The rate $R$ indicates how many bits of input can be fed into each instance of the permutation, and how many bits of output can be extracted from each instance of the permutation. + +With a 1600-bit block size $B$ , the rate $R$ can be up to $1600 - 512 = 1088$ bits; this is easily enough to accommodate all the inputs and outputs of each Tuak function in a single Keccak permutation instance. With an 800-bit block size $B$ , however, the rate $R$ can be at most $800 - 512 = 288$ bits; this would mean that several Keccak permutation iterations would be needed to accommodate all the required inputs and outputs. So, while the 800-bit block size might naïvely seem more efficient than the 1600-bit size, in practice this would not be the case. + +Another clear argument in favour of the 1600-bit permutation block size is that this is what will be used in SHA-3. Choosing a smaller block size would risk unfavourable comparison with SHA-3, and a public impression that Tuak was not as secure as it could have been. It is also true that using the same block size as SHA-3 makes it more likely that implementations developed for the NIST standards can be largely reused for Tuak. + +For these reasons SAGE selected the 1600-bit permutation size for Keccak. Being able to accommodate all inputs and outputs in a single Keccak permutation allows a rather simpler construction than was necessary for MILENAGE, where the basic building block was a 128-bit block cipher. + +The largest set of inputs or outputs that one might want to deal with in a single Tuak function was 816 bits in total, implying that a rate $R \geq 816$ should be chosen for greatest efficiency. SAGE could, therefore, have chosen $C$ up to 784. After a brief discussion with the Keccak design team (who were very helpful and responsive throughout our design process), SAGE decided to choose $C = 512$ , for close alignment with the forthcoming NIST standards. Setting $C = 512$ means that the "rightmost" 512 input bits of each 1600-bit Keccak input block are always set to zero, and that no Tuak output bits are ever extracted from the "rightmost" 512 bits of the 1600-bit Keccak permutation output. (See figure 1 in clause 7.) + +However, it can be argued that in practice Tuak has an effective capacity of at least 768 bits – see clause 3.2 of the Tuak algorithm specification [5]. + +## 8.6 Security evaluation of Keccak + +### 8.6.0 Introduction + +Obviously, a very intensive public expert evaluation of Keccak took place during the SHA-3 competition – there is no need to quote from this in detail here. SAGE's job as Tuak designers was to make sure that Tuak benefited from the security of Keccak, and the expert and general public confidence in Keccak, with good efficiency and to provide the required functionality. + +### 8.6.1 What about the internet stories about NIST weakening SHA-3? + +There were suggestions from some quarters in 2013 that NIST (maybe under influence from NSA) were deliberately weakening SHA-3 (or, as some people carelessly wrote, deliberately weakened Keccak). See for example [17], [18] and [19]. + +SAGE always felt that these "reduced security" concerns were unjustified. One may refer also to the Keccak team's own response in [20]. Here they made it clear: + +- Firstly, that NIST have made no changes at all to Keccak itself, which remains exactly as the Keccak team designed it. +- Secondly, that what NIST were doing was to propose choices of the parameters $C$ and $R$ (capacity and rate, as mentioned above) that give either a very strong or an extremely strong level of security, while not unnecessarily hampering performance; and that these proposed choices are all part of the original Keccak family proposal, again with no changes at all. +- Thirdly: although it's true that the original SHA-3 submission used a larger value for the capacity $C$ , this was done to meet an originally stated but frankly rather meaningless security target – namely, the target of 512-bit pre-image resistance for the 512-bit hash function. Conventional 512-bit hash function designs like SHA-512 do naturally achieve this target (unless "broken") – which is probably why it was stated as a requirement in the original NIST call for submissions – but the sponge function design approach used by Keccak does not. Instead, a capacity of $C$ bits leads to a security level of $C/2$ bits against all attacks, so $C=512$ implies a security level of 256 bits against all attacks, including 256-bit pre-image resistance. NIST recognized – and the Keccak team themselves repeatedly argued – that 256-bit pre-image resistance is strong enough for all purposes, and that setting $C$ any higher than 512 just reduces performance without serving any real purpose. + +However, public confidence is very important. And as it turned out, NIST decided in the end that in the interests of public confidence it was necessary to revert to the original (less efficient but ostensibly more secure) capacity value. So the draft SHA-3 standard [14] uses the original higher capacity value, exactly as in the original Keccak proposal for SHA-3, and there is no longer any plausible reason to suspect any intentional weakness. + +## 8.7 A note on IPR + +### 8.7.1 Keccak IPR + +Submitters to the SHA-3 competition signed a statement that, amongst other text, promised: *"Should my submission be selected for SHA-3, I hereby agree not to place any restrictions on the use of the algorithm, intending it to be available on a worldwide, non-exclusive, royalty-free basis."* + +### 8.7.2 Tuak IPR + +SAGE is not aware of any IPR relating to the construction of Tuak from the Keccak sponge function core. + +## 8.8 Padding bits + +As well as the 3GPP-specified input fields, and the 512 zero bits dictated by the choice of capacity explained in clause 8.5, it is necessary to make up the 1600-bit input block to the Keccak permutation by including padding bits. (Note that these should be fixed padding bits, the same at the Authentication Centre end and the USIM end – one cannot use random padding bits here.) The choice of padding bits has little effect on security in this context. Again following discussion with the Keccak designers, SAGE chose padding bits that were expected to align with NIST's, to give the best possible chance that implementations developed for the NIST standards could be reused as much as possible for Tuak. + +The publication by NIST of the draft SHA-3 standard [14] is encouraging in this regard – see clause 10.2. + +## 8.9 Flexible input and output sizes + +As already mentioned, it was desirable to accommodate the 256-bit subscriber key option in LTE (which is not yet widely used, but could become more popular in future). But also, bearing this 256-bit security level in mind, it was felt that it was prudent also to allow for some possible future increases in the sizes of other 3GPP security parameters, such as the cipher key CK, the integrity key IK and the Message Authentication Codes. This was a nice-to-have, not a hard + +requirement on the Tuak design, but since 1600-bit Keccak can accommodate these extensions with no loss of efficiency, they were included as options in Tuak. There is no immediate expectation that other 3GPP standards will incorporate these extended security parameter sizes, and indeed it may never happen – but the option is there if required. + +## 8.10 Operator customization + +Clause 6.3.3 explains how MILENAGE allows some customization by each mobile operator, and the benefits that this brings. In MILENAGE, each operator needs to choose its own value of an "Operator Variant Algorithm Configuration Field" called OP. In similar vein, Tuak includes an Operator Variant Algorithm Configuration Field, this time called TOP. + +MILENAGE also included a feature whereby an intermediate value $OP_C$ is derived from OP and the secret key K, and it is sufficient for the SIM card to be programmed with $OP_C$ rather than with OP itself. This means that an attacker who is able to extract $OP_C$ from one card does not learn OP or $OP_C$ for other cards. An equivalent feature was included for Tuak, with a value (called $TOP_C$ in the case of Tuak) being derived from TOP and K, in such a way that a SIM card can include only $TOP_C$ , and TOP itself need never appear on a SIM. + +The algorithm specification [5] also describes a very straightforward way in which Tuak could be modified to provide a higher security margin if ever required (if, say, some unexpected cryptanalysis emerged against Keccak), by performing multiple iterations of the Keccak sponge function instead of just one. At the moment, though, Keccak is widely agreed to have a very high security margin, and it is considered unlikely that this further-strengthened version will be needed. + +# --- 9 Independent security and performance evaluation + +## 9.0 Introduction + +Independent expert analysis has been carried out on both the security and the SIM card performance of Tuak. + +## 9.1 Independent security evaluation + +A team at the University of Waterloo, led by Professor Guang Gong, carried out an independent assessment of the security of Tuak. Their extensive report [8] is included as an accompanying document to this one. + +This report considers known cryptanalytic attacks, as well as a new type of attack, and concludes that the Tuak algorithms appear to resist each of these attacks. It also provides a security proof, showing that any weakness in Tuak would translate to a weakness in Keccak. + +The conclusion is that "the algorithms in Tuak perfectly inherit the good security performance from Keccak and it can be used with confidence as message authentication functions and key derivation function". + +## 9.2 Independent SIM card performance evaluation + +An independent assessment of Tuak's performance and implementation complexity on SIM card platforms was carried out by the Smart Card Centre at Royal Holloway University of London. The resulting report [9] is again included as an accompanying document to this one. + +The report concludes that: + +- If Tuak is implemented as native code, the speed and performance goals can be met very comfortably, without the need for a crypto coprocessor, including on a low-end platform (16-bit or even 8-bit). +- Native code implementation does appear to be necessary to achieve the performance targets – an implementation on MULTOS cards was a lot slower. +- Although the study could not include a deep assessment of side channel attack resistance, there appears to be plenty of performance overhead available to allow for software protection measures to be included, if the platform itself does not give enough protection. Some brief notes are included about timing attacks, and it seems that a careful native code implementation should be able to protect against timing attacks without too much trouble (side channel attacks are explored a bit further in clause 9). + +An extension to the above report was also produced by the same author. The extension report [10] is again included as an accompanying document to this one. The extension report: + +- Confirms that, using older, more resource limited smart card platforms than were used in the study for [9], it is still possible to meet the Tuak speed and performance goals in native code, without the need for a crypto coprocessor. +- Describes initial investigations into possible side channel data leakage from an implementation with no software protection. +- Indicates (tentatively) that, with the possible exception of cards using certain chips that claim innovative hardware defences against side-channel and fault attacks, it is likely that smart card/chips will require some protection against side channel data leakage in the software implementation of Tuak. +- Confirms that there should be a performance overhead available to accommodate such software protection measures, with an efficient implementation of Tuak. + +# --- 10 More notes on implementation and side channel attacks + +## 10.1 Protecting implementations against side channel attacks + +Some consideration of side channel attacks was given in [9] and [10] – see clause 9.2. + +Research results also exist concerning how Keccak implementations can be protected against side channel attacks, and these results are directly useful for Tuak implementations too. + +[11] considers power attacks – Simple Power Analysis (SPA) and Differential Power Analysis (DPA), including higher order DPA – and electromagnetic radiation attacks – Simple Electromagnetic Analysis (SEMA) and Differential Electromagnetic Analysis (DEMA), including higher order DEMA. Although the paper isn't exclusively about Keccak, Keccak is given particular attention, and the indications are that protecting an implementation, particularly in software, can be reasonably straightforward and efficient. + +[12] gives further consideration to power analysis, and shows how implementations of Keccak in either hardware or software can be efficiently protected. + +It was already noted in clause 9.2 that protection against "standard" timing attacks seems fairly straightforward. Keccak implementations do not naturally make use of large table lookups, so cache timing attacks should not be a concern. + +## 10.2 Software implementation and the NIST SHA-3 standard + +When the Tuak design was finalized, NIST had selected Keccak as the winner of the SHA-3 competition, but the SHA-3 standard had not been published. SAGE liaised closely with the Keccak design team, to understand what the forthcoming NIST standard was likely to include, and to align the Tuak specification with the anticipated SHA-3 standard as far as possible. + +At the time of writing this design and evaluation report, NIST has now published a *draft* SHA-3 standard, together with a request for comments. If this draft standard remains unchanged, then the alignment of Tuak will be very good. In particular, as well as drop-in replacements for the current SHA-2 hash family, the draft NIST standard includes two "Extendable-Output Functions" SHAKE-128 and SHAKE-256, which allow for variable-size outputs. All of the padding and formatting lines up perfectly for us, so that the Tuak functions can all be defined very straightforwardly in terms of SHAKE-256; thus a Tuak implementation could directly and quickly be built from a SHAKE-256 implementation. + +# 11 Conclusions + +Keccak was selected as the winner of the SHA-3 computation after several years of intense scrutiny by the world's cryptographic community. It is widely agreed by this expert community to have a very clear and well thought out security design, and a very high margin of security. The Tuak design makes direct and straightforward use of Keccak, and clearly inherits Keccak's security benefits. Tuak uses a very strong choice of parameters from the Keccak function family, in line with what is now expected to be standardized by NIST. SAGE consulted with the Keccak design team several times, including sharing its proposed final design with them, giving extra assurance that Tuak (a) in no way fail to capture the security benefits of Keccak and (b) aligns with likely SHA-3-related implementations of Keccak as far as possible. Independent security assessment reinforces this position. + +Implementation and performance aspects (including side channel attack resistance) seem comfortable too, based on independent assessment of Tuak and published research on Keccak. + +In summary, SAGE believes that Tuak meets its targets of security, performance, and resilience as a complement to MILENAGE. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|----|-----|--------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| Nov 2014 | | | | | First TR version | | 0.1.0 | +| Dec 2014 | SA#66 | SP-140816 | | | Version for information and approval | 0.1.0 | 1.0.0 | +| | | | | | Version after approval | 1.0.0 | 12.0.0 | +| Jan 2016 | SA#70 | | | | Upgrade to Rel-13 (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 | 14.0.0 | | +| 2018-06 | - | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | | +| 2018-07 | | | | | | Correction on cover from "TS" to "TR" | 15.0.1 | | +| 2020-07 | - | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/35_series/35935/raw.md b/marked/Rel-16/35_series/35935/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..62c1485fcac85f50cb71c844b0fe68c5ec311f14 --- /dev/null +++ b/marked/Rel-16/35_series/35935/raw.md @@ -0,0 +1,78 @@ + + + + + + +# --- Contents + +| | | +|----------------------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 4 Performance evaluation of the Tuak algorithm set ..... | 5 | +| Annex A: Change history ..... | 6 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides a reference to an independent performance evaluation report of the Tuak algorithm set carried out by the ISG Smart Card Centre of the Royal Holloway University of London. + +# --- 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 35.231: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: Algorithm specification ". +- [2] "Performance Evaluation of the TUAK algorithm in support of the ETSI Sage standardisation group"; Keith Mayes; ISG Smart Card Centre, Royal Holloway University of London; (available at [http://www.3gpp.org/ftp/Specs/archive/35\\_series/35.936/SAGE\\_report/Perfevaluation.zip](http://www.3gpp.org/ftp/Specs/archive/35_series/35.936/SAGE_report/Perfevaluation.zip)) +- [3] "Performance Evaluation of the TUAK algorithm in support of the GSMA and ETSI SAGE standardisation group""; Keith Mayes; ISG Smart Card Centre, Royal Holloway University of London; Crisp Telecom Limited; (available at [http://www.3gpp.org/ftp/Specs/archive/35\\_series/35.936/SAGE\\_report/Perfevaluationnext.zip](http://www.3gpp.org/ftp/Specs/archive/35_series/35.936/SAGE_report/Perfevaluationnext.zip)) + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 35.231 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TS 35.231 [1]. + +# --- 4 Performance evaluation of the Tuak algorithm set + +The performance evaluation report of the Tuak algorithm set [1] can be found here: [2]. + +An extension to the performance evaluation report can be found here: [3]. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|----|-----|--------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| Nov 2014 | | | | | First TR version | | 0.1.0 | +| Dec 2014 | SA#66 | SP-140817 | | | Version for information and approval | 0.1.0 | 1.0.0 | +| | | | | | Version after approval | 1.0.0 | 12.0.0 | +| Jan 2016 | SA#70 | | | | Upgrade to Rel-13 (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 | 14.0.0 | +| 2018-06 | - | - | - | - | - | Update to Rel-15 version (MCC) | 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/35_series/35936/raw.md b/marked/Rel-16/35_series/35936/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..855f5d788a144f4bc845b0f27c69ba197563ee1c --- /dev/null +++ b/marked/Rel-16/35_series/35936/raw.md @@ -0,0 +1,77 @@ + + + + + + +# --- Contents + +| | | +|-------------------------------------------------------|---| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 6 | +| 3.1 Definitions..... | 6 | +| 4 Security assessment of the Tuak algorithm set ..... | 6 | +| Annex A: Change history..... | 7 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides a reference to an independent security assessment of the Tuak algorithm set carried out by the University of Waterloo, Canada. + +# --- 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 35. 231: "Specification of the Tuak algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: Algorithm specification ". +- [2] "Security Assessment of TUAK Algorithm Set"; Guang Gong, Kalikinkar Mandal, Yin Tan, TengWu; Department of Electrical and Computer Engineering University of Waterloo, Canada (available at [http://www.3gpp.org/ftp/Specs/archive/35\\_series/35.935/SAGE\\_report/Secassessment.zip](http://www.3gpp.org/ftp/Specs/archive/35_series/35.935/SAGE_report/Secassessment.zip)) + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 35.231 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TS 35.231 [1]. + +# --- 4 Security assessment of the Tuak algorithm set + +The security assessment of the Tuak algorithm set [1] can be found here: [2]. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|----------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| Nov 2014 | | | | | First TR version | | 0.1.0 | +| Dec 2014 | SA#66 | SP-140818 | | | Version for information and approval | 0.1.0 | 1.0.0 | +| | | | | | Version after approval | 1.0.0 | 12.0.0 | +| Jun 2015 | SA#68 | SP-150302 | 001 | - | Correction of clause title and text referring to wrong subject | 12.0.0 | 12.1.0 | +| Jan 2016 | SA#70 | | | | Upgrade to Rel-13 (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-06 | - | - | - | - | - | Update to Rel-15 version (MCC) | 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/44_series/44001/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/44_series/44001/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58a8c09b01fbeda22d69f5a7f0458c437271a45e --- /dev/null +++ b/marked/Rel-16/44_series/44001/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:150b3a3ce41f1c59d7dd481f0c86977dcf60fab2f224c15b823be3bc553f9640 +size 11753 diff --git a/marked/Rel-16/44_series/44001/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg b/marked/Rel-16/44_series/44001/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08de8a507fde2804dcb288df4ea4128cdb378314 --- /dev/null +++ b/marked/Rel-16/44_series/44001/6df5629bc2fc6d82f1a1edf9d7340113_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ba1ab6958500e3269ff9d90fcd8ddb5e2621e1bb5721fa14cfbe33a01f68c37 +size 18028 diff --git a/marked/Rel-16/44_series/44001/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg b/marked/Rel-16/44_series/44001/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a35e821d0209c55017073cd23c97e18990727a6 --- /dev/null +++ b/marked/Rel-16/44_series/44001/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ddf65e9324bb8091515b98f587414a5c2afeb0b0b26228b541fb808971a8674 +size 40473 diff --git a/marked/Rel-16/44_series/44001/98a45dd7d474e067b7533cc966c11e95_img.jpg b/marked/Rel-16/44_series/44001/98a45dd7d474e067b7533cc966c11e95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ec9a357158e41b50e90faf2c51bed15e453a989 --- /dev/null +++ b/marked/Rel-16/44_series/44001/98a45dd7d474e067b7533cc966c11e95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8133d4dd56827b34f10bc1bf25854816bdbaee20b1a61281dc21d47bc4b9531 +size 20460 diff --git a/marked/Rel-16/44_series/44001/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/44_series/44001/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae6cf698bfcd00efb29953129a4d26d29e6ed1f3 --- /dev/null +++ b/marked/Rel-16/44_series/44001/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:341235b51ac4a990d1d7e5dbecaeab49292f5c14adaeaf5e37798b8d167184f6 +size 50051 diff --git a/marked/Rel-16/44_series/44001/raw.md b/marked/Rel-16/44_series/44001/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b05b47ee1ca546bfea441e8632933c705f3a677b --- /dev/null +++ b/marked/Rel-16/44_series/44001/raw.md @@ -0,0 +1,268 @@ + + + + + + +# --- Contents + +| | | +|----------------------------------------------------------|----| +| Foreword ..... | 4 | +| 0a Scope..... | 5 | +| 0b References..... | 5 | +| 0c Definitions and abbreviations ..... | 6 | +| 1 General..... | 6 | +| 2 Interface applications ..... | 6 | +| 3 Interface technical specification objectives ..... | 7 | +| 4 Interface characteristics..... | 7 | +| 5 Interface capabilities ..... | 8 | +| 6 Technical Specifications on GSM MS-BSS interfaces..... | 8 | +| 7 Protocol modelling principles ..... | 8 | +| Annex A (informative): Change History..... | 11 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 0a Scope + +The present document describes the general aspects and principles relating to the Technical Specifications for the GSM MS-BSS interface. + +# --- 0b 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. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)". +- [3] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [4] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". +- [5] 3GPP TS 44.004: "Layer 1; General requirements". +- [6] 3GPP TS 44.005: "Data Link (DL) layer; General aspects". +- [7] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". +- [8] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [9] 3GPP TS 24.008: "Mobile radio interface; Layer 3 specification; Core network protocols; Stage 3". +- [10] 3GPP TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General aspects". +- [11] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [12] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [13] ITU-T Recommendation X.200: "Information technology - Open Systems Interconnection - Basic Reference Model: The basic model". +- [14] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic Reference Model: Conventions for the definition of OSI services". + +# --- 0c Definitions and abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 21.905. + +# 1 General + +## 1.1 + +A GSM PLMN supports a wide range of services which a user accesses by a standard set of interfaces at a mobile station (MS). The mobile station is connected to the PLMN fixed infrastructure via a radio path to a base station, as shown in figure 1. + +## 1.2 + +The MS-BSS interface on this radio path is specified in the 24- and 44-series of Technical Specifications in such a way as to permit user and network technologies and configurations to evolve separately. + +![Diagram of basic interfaces for user access for a GSM PLMN](6df5629bc2fc6d82f1a1edf9d7340113_img.jpg) + +The diagram illustrates the basic interfaces for user access for a GSM PLMN. It shows a flow from left to right: MMI (Man Machine Interface) connected to an MS (Mobile Station), which is connected via a radio path (MS-BSS interface (24-/44-series)) to a BSS (Base Station System), which is connected to the PLMN fixed infrastructure. The MS and BSS are represented by dashed rectangular boxes, and the radio path is represented by a dashed line with a '+' sign at each end. + +Diagram of basic interfaces for user access for a GSM PLMN + +**Figure 1: Basic interfaces for user access for a GSM PLMN** + +## 1.3 + +The principles and procedures for the man-machine interface (MMI) to the MS are described in Technical Specification 3GPP TS 22.030. The user may also use standard terminal interfaces within the MS. The reference configuration for the access is described in Technical Specification 3GPP TS 24.002. + +# 2 Interface applications + +Figure 2 shows some examples of the application of GSM MS-BSS interfaces. The following cases are shown: + +- i) access of simple handportable or vehicle mounted MSs; +- ii) access of an MS with multiple terminal equipment installation; +- iii) access of a mobile PBX or LAN; + +In addition, the figure identifies internetwork interfaces for connections to: + +- iv) land-line ISDN networks; +- v) dedicated service networks. + +![Diagram illustrating various GSM interfaces. A central 'GSM' box is connected to three types of mobile stations (MS) on the left: 'Simple MS', 'MS with multiple terminal equipment', and 'Mobile PBX * or LAN'. The 'Simple MS' and 'MS with multiple terminal equipment' are connected via an 'MS-BSS interface' (dashed line). The 'Mobile PBX * or LAN' is connected via a 'Fixed network - GSM network interface' (dashed line with double arrowheads). On the right, the 'GSM' box is connected to a 'Dedicated service network' and an 'ISDN network' via 'Fixed network - GSM network interfaces' (dashed lines with double arrowheads). A legend below the diagram defines the interface types: a dashed line for 'MS-BSS interface' and a dashed line with double arrowheads for 'Fixed network - GSM network interface'. A note indicates that the Mobile PBX * or LAN case has not been specified yet.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +``` + +----+ ++---+ MS-BSS interface + +--><--- Fixed network - GSM network interface + +* This case has not been specified yet. + +``` + +Diagram illustrating various GSM interfaces. A central 'GSM' box is connected to three types of mobile stations (MS) on the left: 'Simple MS', 'MS with multiple terminal equipment', and 'Mobile PBX \* or LAN'. The 'Simple MS' and 'MS with multiple terminal equipment' are connected via an 'MS-BSS interface' (dashed line). The 'Mobile PBX \* or LAN' is connected via a 'Fixed network - GSM network interface' (dashed line with double arrowheads). On the right, the 'GSM' box is connected to a 'Dedicated service network' and an 'ISDN network' via 'Fixed network - GSM network interfaces' (dashed lines with double arrowheads). A legend below the diagram defines the interface types: a dashed line for 'MS-BSS interface' and a dashed line with double arrowheads for 'Fixed network - GSM network interface'. A note indicates that the Mobile PBX \* or LAN case has not been specified yet. + +**Figure 2: Examples of GSM interfaces** + +# 3 Interface technical specification objectives + +MS-BSS interface Technical Specifications should allow: + +- i) different types of mobile stations and terminal equipment to use the same standard interface; +- ii) portability of MSs within the system area of the GSM system; +- iii) separate evolution of both mobile stations and network equipment technologies and configurations; +- iv) calls to a terminal using the same code (call number) no matter in what country it is actually located; +- v) connections of an MS to the ISDN network so that only the radio channel capacity and the ISDN protocol are limiting factors. + +# 4 Interface characteristics + +The MS-BSS interface is specified by a comprehensive set of characteristics, including: + +- i) channel structures and access capabilities; +- ii) user-network (MS-BSS) protocols; +- iii) maintenance and operation characteristics; +- iv) performance characteristics; +- v) service characteristics. + +# 5 Interface capabilities + +In addition to the multiservice capability, the GSM MS-BSS interface may allow for capabilities such as the following: + +- i) multidrop and other multiple terminal arrangements; +- ii) choice of information bit rate, circuit or packet switching mode, layer 2 coding method, etc., on a call-by-call or other basis (e.g. semipermanent, or subscription time option), over the same interface according to the user's need; +- iii) capability for compatibility checking in order to check whether calling and called terminals can communicate with each other. + +# 6 Technical Specifications on GSM MS-BSS interfaces + +## 6.1 + +The reference configurations for the GSM MS-BSS interface define the terminology for various reference points. Technical Specification 3GPP TS 24.002 contains the GSM PLMN access reference configuration. + +## 6.2 + +Technical Specification 3GPP TS 44.003 defines the channel structures and access capabilities for the MS-BSS interface. A distinction is necessary between the logical channel structure supported by the interface and the access capability supported by the radio path of the system. + +## 6.3 + +The MS-BSS interface as defined in Technical Specifications 3GPP TS 44.004, 3GPP TS 44.005, 3GPP TS 44.006, 3GPP TS 24.007, 3GPP TS 24.008, 3GPP TS 24.010, 3GPP TS 24.011 and 3GPP TS 44.012 is applicable to a wide range of situations. + +# 7 Protocol modelling principles + +## 7.1 + +The signalling protocols on the MS-BSS Interface are specified using the concepts of the reference model of Open System Interconnection (OSI) given in ITU-T Recommendations X.200 and X.210. + +## 7.2 + +The basic structuring technique in the OSI reference model is layering. According to this technique, communication among application processes is viewed as being logically partitioned into an ordered set of layers represented in a vertical sequence as shown in figure 3. + +![Diagram illustrating the layering concept in the OSI reference model. It shows a vertical stack of layers, with the 'Highest layer' at the top and the 'Lowest layer' at the bottom. The layers are labeled from top to bottom: Highest layer, (N + 1)-layer, (N)-layer, (N - 1)-layer, and Lowest layer. The diagram is enclosed in a dashed rectangular box with '+' signs at the corners.](98a45dd7d474e067b7533cc966c11e95_img.jpg) + +``` + ++-----+ +| Highest layer | ++-----+ +| (N + 1)-layer | ++-----+ +| (N)-layer | ++-----+ +| (N - 1)-layer | ++-----+ +| Lowest layer | ++-----+ + +``` + +Diagram illustrating the layering concept in the OSI reference model. It shows a vertical stack of layers, with the 'Highest layer' at the top and the 'Lowest layer' at the bottom. The layers are labeled from top to bottom: Highest layer, (N + 1)-layer, (N)-layer, (N - 1)-layer, and Lowest layer. The diagram is enclosed in a dashed rectangular box with '+' signs at the corners. + +**Figure 3: Layering** + +Entities exist in each layer. Entities in the same layer, but in different systems which must exchange information to achieve a common objective are called "peer entities". Entities in adjacent layers interact through their common + +boundary. The services provided by the (N + 1)-layer are the combination of the services and functions provided by the (N)-layer and all layers below the (N)-layer. + +Management functions may also be required. They may include functions which are common for several layers and are not supported by the services provided by a specific layer. Examples of such functions are error reporting, status reporting and management of the operation of certain layers. Such management functions do not require that peer-to-peer messages are sent across the MS-BSS interface. + +## 7.3 + +For signalling on the MS-BSS interface three layers are required as shown in figure 4. + +![Figure 4: Layering on the MS-BSS interface. A diagram showing three stacked layers: Layer 3 at the top, Data link layer in the middle, and Physical layer at the bottom. Each layer is enclosed in a dashed rectangular box with '+' signs at the corners.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Figure 4: Layering on the MS-BSS interface. A diagram showing three stacked layers: Layer 3 at the top, Data link layer in the middle, and Physical layer at the bottom. Each layer is enclosed in a dashed rectangular box with '+' signs at the corners. + +**Figure 4: Layering on the MS-BSS interface** + +The layers are: + +- PHYSICAL LAYER which corresponds to the lowest layer. The functions and protocols of the physical layer are defined in Technical Specification 3GPP TS 44.004. +- DATA LINK LAYER. The functions and protocols of the data link layer are defined in Technical Specifications 3GPP TS 44.005 and 3GPP TS 44.006. +- LAYER 3. The functions and protocols of layer 3 are defined in Technical Specifications 3GPP TS 24.007, 3GPP TS 24.008, 3GPP TS 24.010, 3GPP TS 24.011 and 3GPP TS 44.012. + +## 7.4 + +Layer-to-layer interactions are specified in terms of service primitives. The primitives represent, in an abstract way, the logical exchange of information and control between adjacent layers. They do not specify or constrain implementation. + +Primitives are also used to describe information exchange between layers and the mobile management entity. + +The primitives that are exchanged between the (N + 1)-layer and the (N)-layer are of the following four types (see figure 5). + +![Figure 5: Primitive action sequence for peer-to-peer communication. A sequence diagram showing two (N+1)-layers and two (N)-layers. The first (N+1)-layer sends a 'Request' to its (N)-layer, which then sends a '>>' message to the second (N)-layer. The second (N)-layer sends a '<<' message back to the first (N)-layer, which then sends a 'Confirm' to its (N+1)-layer. The second (N+1)-layer sends a 'Response' to its (N)-layer, which receives an 'Indication' from the first (N)-layer. Both (N)-layers have a '*' symbol inside their boxes.](9283a3f6b39120df9dc9aee4712b3a0a_img.jpg) + +Figure 5: Primitive action sequence for peer-to-peer communication. A sequence diagram showing two (N+1)-layers and two (N)-layers. The first (N+1)-layer sends a 'Request' to its (N)-layer, which then sends a '>>' message to the second (N)-layer. The second (N)-layer sends a '<<' message back to the first (N)-layer, which then sends a 'Confirm' to its (N+1)-layer. The second (N+1)-layer sends a 'Response' to its (N)-layer, which receives an 'Indication' from the first (N)-layer. Both (N)-layers have a '\*' symbol inside their boxes. + +**Figure 5: Primitive action sequence for peer-to-peer communication** + +The REQUEST primitive type is used when a higher layer is requesting a service from the next lower layer. + +The INDICATION primitive type is used by a layer providing a service to notify the next higher layer of activities related to the primitive type REQUEST. + +The RESPONSE primitive type is used by a layer to acknowledge receipt, from a lower layer, of the primitive type INDICATION. + +The CONFIRM primitive type is used by the layer providing the requested service to confirm that the activity has been completed. + +# Annex A (informative): Change History + +| Meeting No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +|-------------|-----------|---------|------------------|-------------|---------------------------------------------------| +| SMG#07 | | | | 4.0.4 | Phase 2 version | +| SMG#20 | | | | 5.0.0 | 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 | +| CN#11 | | | | 4.0.0 | Release 4 version | +| NP-16 | NP-020224 | 001 | | 4.1.0 | Various clean-up of wrong references | +| NP-16 | | | | 5.0.0 | Plenary decision to make this TS also for Rel-5. | +| NP-26 | | | | 6.0.0 | Plenary decision to make this TS also for Rel-6. | +| | | | | 7.0.0 | Plenary decision to make this TS also for Rel-7. | +| CP-42 | | | | 8.0.0 | Plenary decision to make this TS also for Rel-8. | +| CP-46 | | | | 9.0.0 | Plenary decision to make this TS also for Rel-9. | +| CP-51 | | | | 10.0.0 | Plenary decision to make this TS also for Rel-10. | +| CP-57 | | | | 11.0.0 | Plenary decision to make this TS also for Rel-11. | +| CP-65 | | | | 12.0.0 | Plenary decision to make this TS also for Rel-12. | +| CP-70 | | | | 13.0.0 | Upgrade to Rel-13 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|-------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2018-06 | SA#80 | | | | | Upgrade to Rel-15 | 15.0.0 | +| 2020-06 | SA#88e | | | | | Upgrade to Rel-16 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44003/raw.md b/marked/Rel-16/44_series/44003/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..220bc94ce5747b7625edfdafbed264028cf7b2c8 --- /dev/null +++ b/marked/Rel-16/44_series/44003/raw.md @@ -0,0 +1,358 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 5 | +| 4 General definitions ..... | 5 | +| 5 Channel types and their use: Traffic channels and user channels..... | 6 | +| 5.1 User channels ..... | 6 | +| 5.2 Bm Channel..... | 6 | +| 5.3 Lm Channels ..... | 6 | +| 6 Channel types and their use: Packet data traffic channels ..... | 7 | +| 7 Channel types and their use: Control channels ..... | 7 | +| 7.1 Control channel types..... | 7 | +| 7.1.1 Broadcast Control Channel..... | 7 | +| 7.1.2 Common Control Channel..... | 8 | +| 7.1.3 Dedicated Control Channel (DCCH)..... | 8 | +| 8 BS access capability..... | 9 | +| 9 Channel configurations ..... | 10 | +| 9.1 Mandatory capabilities ..... | 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 defines limited sets of channel types, access capabilities and channel configurations at reference point Um (radio interface). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [3] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [4] 3GPP TS 45.002: "Multiplexing and Multiple Access on the Radio Path". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# --- 4 General definitions + +A channel represents a specified portion of the information-carrying capacity of an interface. + +Channels are classified by channel types, which have common characteristics. Channel types appearing on the radio interface are specified in clauses 3 and 4. + +At a given time, the complete interface between a Base Station and the set of Mobile Stations in relation corresponds to some interface structure. The interface structure may change in time. The number of possible different such interface structures can be large. The BS access capability is a description of all the possible interface structures of the considered BS. BS access capabilities are specified in sub-clause 8. + +At a given moment, the channel configuration of a Mobile Station is the interface structure this Mobile Station actually uses to transmit information to or receive information from the Base Station. The channel configuration may change in time. A limited number of channel configurations are identified, and are specified in sub-clause 9. + +A Mobile Station access capability is the description of the set of its possible channel configurations. MS access capabilities are specified in sub-clause 8. + +# --- 5 Channel types and their use: Traffic channels and user channels + +## 5.1 User channels + +User channels are intended to carry a wide variety of user information streams. A distinguishing characteristic is that user channels do not carry signalling information for Connection Management (CM), Mobility Management (MM) or + +Radio Resource (RR) management. This signalling information is carried over other types of channels, namely the control channels. + +User channels may be used to provide access to the PLMN and the networks it permits access to. + +Different types of user channels are distinguished by their rates. + +## 5.2 Bm Channel + +A Bm channel is a bi-directional or uni-directional user channel able to carry: + +- a 13 kbit/s rate bit stream with an error structure and a transmission delay compatible with some grade of service, intended to carry voice encoded according to Technical Specifications in 3GPP TS 06-series; or +- a bit stream at a rate of 14,5 kbit/s, 12 kbit/s, 6 kbit/s or 3,6 kbit/s, with an error structure and a transmission delay adapted to a wider range of services, including data transmission; or other kinds of bit stream adapted to a wider range of services (for further study). + +User information streams are carried on the Bm channel on a dedicated, alternate (within one call or as separate calls), or simultaneous basis, consistent with the Bm channel carrying capability. The following are samples of user information streams: + +- i) voice encoded at 13 kbit/s according to Technical Specifications in 3GPP TS 06-series; and +- ii) data information corresponding to circuit switching user classes of services at bit rates compatible with the channel capability. + +A Bi-directional Bm Channel uses the radio resources referred to as TCH/F. Bi-directional downlink Bm Channel uses the radio resources referred to as TCH/FD. The Uni-directional Bm Channel is only defined in downlink direction. Traffic channels (TCH) are fixed physical gross rate channels, accompanied with timing (see 3GPP TS 45.002). + +## 5.3 Lm Channels + +A Lm channel is a user channel with a carrying capability lower than a Bm channel. + +A Lm channel is a user channel able to carry: + +- some bit stream to be defined with an error structure and a transmission delay compatible with some grade of service, intended to carry voice encoded according to a method to be defined; +- a bit stream at a rate of 6 kbit/s or 3,6 kbit/s, with an error structure and a transmission delay adapted to a wider range of services, including data transmission; or +- other kinds of bit stream adapted to a wider range of services (for further study). + +User information streams are carried on a Lm channel on a dedicated, alternate (within one call or as separate calls), or simultaneous basis, consistent with the TCH/H channel carrying capability. The following are samples of user information streams: + +- i) voice encoded at some rate according to a method to be specified in the future; and +- ii) data information corresponding to circuit switching user classes of services at bit rates compatible with the channel capability. + +A Lm Channel uses the radio resources referred to as TCH/H. Traffic channels (TCH) are fixed physical gross rate channels, accompanied with timing (see 3GPP TS 45.002). + +# --- 6 Channel types and their use: Packet data traffic channels + +Packet data traffic channels are used to carry a wide variety of information streams, including user information and signalling information for, e.g. Session Management (SM) and Mobility Management (MM) in packet mode. A distinguishing characteristic is that a packet data traffic channel allows a plurality of information streams, associated + +with different users, to be multiplexed in a pre-emptive and dynamic fashion. Signalling functions between the MS and the BSS are carried out over other types of channels, namely the control channels. + +Uni-directional information streams are carried on the packet data traffic channel on an alternate, or simultaneous basis, consistent with the packet data traffic channel carrying capability. The packet data traffic channel uses the radio resources referred to as PDTCH or Extended Coverage PDTCH (EC-PDTCH) (see 3GPP TS 45.002). + +# --- 7 Channel types and their use: Control channels + +NOTE: The term "Dm channel" may be used to refer to the controls channels used by a Mobile Station at a given moment, independently of their type. (The term "Dm channel" in conjunction with the packet control channels shall be avoided.) + +Control channels are used to provide all active Mobile Stations with a continuous frame oriented means of communication across the MS-BS interface. + +A Mobile Station Channel Configuration contains one or more control channels. These control channels may change in time, with the channel configuration. Access management signalling functions are used to insure the continuity when a change in the control channels occurs. + +Control channels are classified by control channel types, which have common characteristics. These control channel types are specified in sub-clause 7.1. + +The control channels are primarily intended to carry signalling information for Connection Management (CM), Mobility Management (MM) and Radio Resource (RR) management. + +In addition to signalling information control channels may also be used to carry other data, including those relating to Short Message Services (SMS). + +## 7.1 Control channel types + +### 7.1.1 Broadcast Control Channel + +A broadcast control channel is a point-to-multipoint uni-directional control channel, from the fixed sub-system to the Mobile Stations. Broadcast control channels are physically sub-divided into the Broadcast Control CHannel (BCCH), Packet Broadcast Control CHannel (PBCCH), Compact Packet Broadcast cControl CHannel (CPBCCH), and Extended Coverage Broadcast Control CHannel (EC-BCCH). + +BCCH, PBCCH, CPBCCH and EC-BCCH are intended to broadcast a variety of information to MSs, including information necessary for MS to register in the system (e.g. synchronization data). + +BCCH, PBCCH, CPBCCH and EC-BCCH use a protocol specified in Technical Specifications in 3GPP TS 44-Series. + +### 7.1.2 Common Control Channel + +A common control channel is a point-to-multipoint bi-directional control channel. Common control channels are physically sub-divided into the Common Control CHannel (CCCH), the Packet Common Control CHannel (PCCCH), the Compact Packet Common Control CHannel (CPCCCH), and the Extended Coverage Common Control Channel (EC-CCCH). + +CCCH, PCCCH, CPCCCH and EC-CCCH are primarily intended to carry signalling information necessary for access management functions (e.g., allocation of dedicated channels or radio resource on a packet data traffic channel). The CCCH can be used for other signalling purposes. + +CCCH, PCCCH, CPCCCH and EC-CCCH use a layered protocol according to Technical Specifications in 3GPP TS 44-Series. In particular the multipoint to point management is achieved through random access techniques. + +The following terms may be used when the context requires it: + +- The RACH (Random Access CHannel) is the uplink (MS to network) part of the CCCH. +- The PRACH (Packet Random Access CHannel) is the uplink part of the PCCCH. + +- The CPRACH (Compact Packet Random Access CHannel) is the uplink part of the CPCCCH. +- The EC-RACH (Extended Coverage Random Access CHannel) is the uplink part of the EC-CCCH. +- The AGCH (Access Grant CHannel) is the part of the downlink (network to MS) part of the CCCH reserved for assignment messages. +- The PAGCH (Packet Access Grant CHannel) is the part of the downlink part of the PCCCH used for assignment messages. +- The CPAGCH (Compact Packet Access Grant CHannel) is the part of the downlink part of the CPCCCH used for assignment messages. +- The EC-AGCH (Extended Coverage Access Grant CHannel) is the downlink part of the EC-CCCH used for assignment messages. +- The NCH (Notification CHannel) is the part of the downlink part of the CCCH reserved for voice group and/or voice broadcast calls notification messages. +- PCH (Paging CHannel) is the remaining part of the downlink part of the CCCH. +- PPCH (Packet Paging CHannel) is the remaining part of the downlink part of the PCCCH. +- CPPCH (Compact Packet Paging CHannel) is the remaining part of the downlink part of the CPCCCH. +- EC-PCH (Extended Coverage Paging CHannel) is the downlink part of the EC-CCCH used for paging messages. + +### 7.1.3 Dedicated Control Channel (DCCH) + +A Dedicated Control CHannel (DCCH) is a point-to-point bi-directional or uni-directional control channel. + +DCCHs exist with a variety of bit rates. + +DCCHs are further classified as follows according to some technical particularities: + +A SDCCH (Stand-alone DCCH) is a bi-directional DCCH whose allocation is not linked to the allocation of a TCH. The bit rate of a SDCCH is 598/765 kbit/s. + +A FACCH (Fast Associated DCCH) is a bi-directional DCCH obtained by pre-emptive dynamic multiplexing on respectively a TCH/F or a TCH/H channel. The allocation of a FACCH is obviously linked to the allocation of a TCH. The bit rate of a FACCH is 9 200 bit/s or 4 600 bit/s. + +A SACCH (Slow Associated DCCH) is either a bi-directional or uni-directional DCCH of rate 115/300 kbit/s or a bi-directional DCCH of rate 299/765 kbit/s. An independent SACCH is always allocated together with a TCH or a SDCCH. The co-allocated TCH and SACCH shall be either both bi-directional or both uni-directional. + +NOTE 1: A Multislot Configuration (described in sub-clause 9) is an example of a case where uni-directional SACCHs may be used. + +The terms Bm, or Bm + ACCHs can be used to refer to a Bm channel together with the corresponding FACCH and the co-allocated SACCH when the context avoids any ambiguities. Similar remarks apply to the terms Lm, Lm + ACCHs, Lm + Lm, Lm + Lm + ACCHs. The term SDCCH can be used to refer specifically to a SDCCH together with the co-allocated SACCH when the context avoids any ambiguities. + +NOTE 2: TCH/F is sometimes used to designate Bm associated with its control channel (FACCH and SACCH). TCH/H is sometime used to designate Lm associated with its control channel (FACCH and SACCH). + +A PACCH (Packet Associated Control CHannel) is a bi-directional DCCH obtained by pre-emptive dynamic multiplexing on a PDTCH. + +An EC-PACCH (Extended Coverage Packet Associated Control CHannel) is a bi-directional DCCH obtained by multiplexing on an EC-PDTCH. + +A PTCCH (Packet Timing Control CHannel) is a bi-directional DCCH carrying synchronization data for a group of up to 16 MSs in packet transfer state (see 3GPP TS 44.060). + +The DCCHs use a layered protocol according to Technical Specifications in 3GPP TS 04- and 05-series. + +# 8 BS access capability + +The BS access capability is composed of: + +one BCCH; + +one CCCH physically related to the BCCH; + +{{0 to 3 additional CCCHs; and a global resource. + +OR: + +BCCH, CCCH plus 4 SDCCHs and a global resource.}} + +The global resource can be used to accommodate: + +- i) $n1$ ( $Bm + FACCH + SACCH$ ); +- ii) $2n2$ ( $Lm + FACCH + SACCH$ ); +- iii) $8n3$ (SDCCH of rate 598/765 kbit/s + SACCH); +- iv) $n4$ ( $Bm + SACCH$ ); +- v) $n5$ (PBCCH + PCCCH + PDTCH + PACCH + PTCCH); +- vi) $n6$ (PCCCH + PDTCH + PACCH + PTCCH); +- vii) $n7$ (PBCCH + PCCCH); and +- viii) $n8$ (PDTCH + PACCH + PTCCH); + +with the constraints: $n5 = 0$ or $1$ ; + +$n5 > 0$ implies that $n7 = 0$ ; + +$n7 > 0$ implies that $n5 = 0$ and $n6 = 0$ ; and + +$n1 + n2 + n3 + n4 + n5 + n6 + n7 + n8$ lower than some value characterizing the BS access capability. + +The exact use of the global resource may vary in time. + +For Compact, the BS access capability is composed of: + +CPBCCH; + +CPCCCH physically related to the CPBCCH; + +{{and a global resource.}} + +The global resource can be used to accommodate: + +- i) $n9$ (PDTCH + PACCH + PTCCH); + +$n9$ lower than some value characterizing the BS access capability. + +The exact use of the global resources may vary in time. + +For EC-EGPRS capable BS, the BS access capability is composed of: + +one BCCH and one EC-BCCH; + +CCCH physically related to the BCCH; + +EC-CCCH physically related to the EC-BCCH; + +{{0 to 3 additional CCCHs and/or EC-CCCHs; and a global resource.}} + +The global resource can be used to accommodate: + +i) n10 (EC-PDTCH + EC-PACCH); + +n10 lower than some value characterizing the BS access capability. + +The exact use of the global resources may vary in time. + +# 9 Channel configurations + +At a given moment, a Mobile Station accesses only a limited number of channels appearing on its radio interface. Different compositions for the accessed channels set are identified, and specified below. + +Different channel configurations are: + +i) BCCH; + +ii) CCCH; + +iii) CCCH + BCCH; + +iv) SDCCH + SACCH; + +v) Bm + FACCH + SACCH; + +vi) Lm + FACCH + SACCH; + +vii) Lm + Lm + FACCH + SACCH; + +viii) ( n + m ) Bm + FACCH + ( n + m ) SACCH; + +where n is the number of bi-directional channels and m is the number of uni-directional channels (n = 1..8, m = 0..7, n + m = 1..i); + +ix) PCCCH + PBCCH; + +x) ( n + m ) PDTCH + PACCH + PTCCH + +where n is the number of channel allowing information streams in both directions and m is the number of channels allowing information streams in one direction (n = 0..8, m = 0..8, n + m = 1..8). + +xi) CPBCCH; + +xii) CPCCCH; + +xiii) CPCCCH + CPBCCH + +xiv) EC-BCCH; + +xv) EC-CCCH; + +xvi) EC-CCCH + EC-BCCH + +Configurations i), xi) and xiv) are normally used only in the phase when the physical connection is not set (i.e. just after switch-on, or after a too long interruption of the physical connection due to poor propagation conditions). + +Configurations ii) or iii) are used by active but idle MS or MS in packet wait state (see GSM 44.060). + +Configurations iv) is used in phases when only a dedicated control channel is needed. + +Configurations v) to viii) are used in particular when a circuit-switched communication is in progress. + +Configuration viii) is a Multislot Configuration. Possible combinations of bi- and uni-directional channels are defined in 3GPP TS 45.002. + +Configurations ix), xii), and xiii) are used by MS in packet wait state. + +Configuration x) is a Multislot Configuration on packet data traffic channels. Possible combinations of bi- and uni-directional channels are defined in 3GPP TS 45.002. + +In addition, a MS of GPRS MS class A (see 3GPP TS 22.060) may combine one of the configurations i) to viii) (to support GSM circuit switched services and SMS) with one of the configurations ii), iii), ix), or x) (to support GSM GPRS services). + +Configurations xiv) or xv) are used by active but idle EC-EGPRS MS or an EC-EGPRS MS in packet wait state. + +## 9.1 Mandatory capabilities + +The following access capabilities are mandatory for all MSs. + +- All MSs supporting circuit-switched services shall support SDCCH. +- If a given service is supported by an MS on a TCH/H, this MS shall support this service on a TCH/F (but not necessarily vice versa). +- An MS supporting a service on TCH/F shall support the signalling only mode on TCH/F as well as the signalling modes associated with the TCH/F. +- An MS supporting a service on TCH/H shall support the signalling only mode on TCH/F as well as the signalling modes associated with the TCH/H. + +# --- Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------------|-----------------|-----------|------------|--------------------------------------------|------------| +| December 2015 | - | - | - | Release 13 version based on version 12.0.0 | 13.0.0 | +| GP-68 | GP-151170 | 0009 | 1 | Introduction of EC-EGPRS | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|------------|----------------------------------------------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44004/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/44_series/44004/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f16b53033f79b8b95fbccc24e593be418ab71b50 --- /dev/null +++ b/marked/Rel-16/44_series/44004/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde40365349b2e0dc6ec27607e386e126892342355f36035422c304de190922d +size 21096 diff --git a/marked/Rel-16/44_series/44004/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/44_series/44004/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cf6e2c13be46f4686181e5e827a31b3953c80d1 --- /dev/null +++ b/marked/Rel-16/44_series/44004/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:274970751a0a48244fcd627938fa049fd4d110b34f20684bbf26236ec5b1d6d4 +size 51057 diff --git a/marked/Rel-16/44_series/44004/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/marked/Rel-16/44_series/44004/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de4c1ebfea870ec978e178e65361cf6f6393bef9 --- /dev/null +++ b/marked/Rel-16/44_series/44004/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52445354e89dbcaac20b9551bca07734c8f2114a5df86a17491cef24f1fbf8db +size 44368 diff --git a/marked/Rel-16/44_series/44004/0a884282620b74ce60c04ab3400c4208_img.jpg b/marked/Rel-16/44_series/44004/0a884282620b74ce60c04ab3400c4208_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f9ac27127e70e8eaefa832241d5ccc5c664063b --- /dev/null +++ b/marked/Rel-16/44_series/44004/0a884282620b74ce60c04ab3400c4208_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25a2684bb4d666049f66b824dd2ffb6e3a3a3b1aa8de45bb9c5cecde47770b43 +size 17280 diff --git a/marked/Rel-16/44_series/44004/132cff7e872feb31f629703959beddd7_img.jpg b/marked/Rel-16/44_series/44004/132cff7e872feb31f629703959beddd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47a72894999ae3e605fce44023b9f171cf9b9c48 --- /dev/null +++ b/marked/Rel-16/44_series/44004/132cff7e872feb31f629703959beddd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c63210e16143ead5f1e302bcc4965652d1211f7c95ccdad0f3f26806f860311c +size 51293 diff --git a/marked/Rel-16/44_series/44004/14515d82ffeec9475b9add3036ff26ab_img.jpg b/marked/Rel-16/44_series/44004/14515d82ffeec9475b9add3036ff26ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3910b5bfaaa9820da0fb93b233b60c6def765e4a --- /dev/null +++ b/marked/Rel-16/44_series/44004/14515d82ffeec9475b9add3036ff26ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fb0d8a63355fca5042279235e6b5f0101bcc90528e6a197712895929d5de218 +size 30627 diff --git a/marked/Rel-16/44_series/44004/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/Rel-16/44_series/44004/18442e4e239480f0c3c95b547aa8fde2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..281211495958de2282df666e396e2a6a2f081082 --- /dev/null +++ b/marked/Rel-16/44_series/44004/18442e4e239480f0c3c95b547aa8fde2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d86eb1332d93e94eb3d6a7138bef738c94ef7ed2f4e0cf08e314b8ee54dad25 +size 30683 diff --git a/marked/Rel-16/44_series/44004/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/44_series/44004/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d265a1cf618e50c31d2fd071ed96e8452c5e767 --- /dev/null +++ b/marked/Rel-16/44_series/44004/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf2994afb5d96c49bd7fa6ae68e96308f8044715866b4dea07bcd409999ab32f +size 17047 diff --git a/marked/Rel-16/44_series/44004/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-16/44_series/44004/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1de16b442687912ca0a344a40ecb66772ab72620 --- /dev/null +++ b/marked/Rel-16/44_series/44004/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92ca8f93a281b8802b28bf162e98305cecd1fac78249de8b3199ea23c6d71723 +size 32193 diff --git a/marked/Rel-16/44_series/44004/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-16/44_series/44004/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efb7cbd08d2cfdec075df84bc14aac0c1151bb85 --- /dev/null +++ b/marked/Rel-16/44_series/44004/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af49f1fb7df90d73dd2d6495d4b90401384cdfc2e489d2e963fcb52757d32a85 +size 55757 diff --git a/marked/Rel-16/44_series/44004/1ad662a678c4f002de911d403f00de8e_img.jpg b/marked/Rel-16/44_series/44004/1ad662a678c4f002de911d403f00de8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a83b3f600242374d0e6f64a3b6c51865f43b77b --- /dev/null +++ b/marked/Rel-16/44_series/44004/1ad662a678c4f002de911d403f00de8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c6758ccbcff661b70213f761cdae40c9dbebe07fc0cefdadb8bd9c922e504d1 +size 47480 diff --git a/marked/Rel-16/44_series/44004/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-16/44_series/44004/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a034504a645ae6d48bb6b9a017ca67745ec8fb8 --- /dev/null +++ b/marked/Rel-16/44_series/44004/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:788f2b6b311545f5a8d37ff07130d3f5d6c3674a6e5e325bfd192a6e191fb1d4 +size 51948 diff --git a/marked/Rel-16/44_series/44004/1c29dadab94c3fa552d270434db09c81_img.jpg b/marked/Rel-16/44_series/44004/1c29dadab94c3fa552d270434db09c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45a86fc11fabca742a0d37e25be3db09310399a3 --- /dev/null +++ b/marked/Rel-16/44_series/44004/1c29dadab94c3fa552d270434db09c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2b1c31f8edf43fde51ec3e0f61614736062a7b694bd40aa1d6af0fd799d6c56 +size 38025 diff --git a/marked/Rel-16/44_series/44004/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-16/44_series/44004/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a49d10b2efa747f96289847a7d8e6c131d363d71 --- /dev/null +++ b/marked/Rel-16/44_series/44004/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15f63c0fb2c001dddb19a67aaab9a5e4dfae526e422055da463273a2461b1fbd +size 29007 diff --git a/marked/Rel-16/44_series/44004/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-16/44_series/44004/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..636fb3f8d86b064be87b186609491955453ab224 --- /dev/null +++ b/marked/Rel-16/44_series/44004/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ce750de7b1dc0c9521cc89ba88940b80039dd231fcd04eb4933fdc5415a52c8 +size 31129 diff --git a/marked/Rel-16/44_series/44004/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/44_series/44004/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..149a4239b63c449ea6aa25c369031d9f733d6fcd --- /dev/null +++ b/marked/Rel-16/44_series/44004/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3243fa07fb61f9c13f3864f8d2bc76272949df1d7250fb92d7a88beffda254d +size 30896 diff --git a/marked/Rel-16/44_series/44004/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/44_series/44004/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91ed127feeda9848c9dc776efa60b99f7e0eb126 --- /dev/null +++ b/marked/Rel-16/44_series/44004/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7faedf10b988938ff9cfae3bbde3170ed2632ca74732efaed0ca66795b2adaf6 +size 45029 diff --git a/marked/Rel-16/44_series/44004/298e7e2164a95d0d5bb8e5d1f7155094_img.jpg b/marked/Rel-16/44_series/44004/298e7e2164a95d0d5bb8e5d1f7155094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c91fada187d278a822d29891e9d245b8052b3bce --- /dev/null +++ b/marked/Rel-16/44_series/44004/298e7e2164a95d0d5bb8e5d1f7155094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a261c18dcd7f096427b14d232d87034d7d4e4752113977fba3069ad7bf7aa7d +size 17490 diff --git a/marked/Rel-16/44_series/44004/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/44_series/44004/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b5ec113f623744ff9516091440c10b6396ea6a5 --- /dev/null +++ b/marked/Rel-16/44_series/44004/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44af7ce2a1c2dccf4ffc646a735cd2126e696ff19233b87b150bb43e853b647c +size 22044 diff --git a/marked/Rel-16/44_series/44004/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-16/44_series/44004/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2e05388023bbe295757e1200ac013970b1cb04 --- /dev/null +++ b/marked/Rel-16/44_series/44004/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:051bccdd1b0662e905eb37b75bd193e1c525d369e4368eed946b71fdb89af903 +size 22914 diff --git a/marked/Rel-16/44_series/44004/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/44_series/44004/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57867b26bf9391bd8da07590fbbb569cf562f80c --- /dev/null +++ b/marked/Rel-16/44_series/44004/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e67e25fe9fc73bff7407c6618b23ce594f4ff406f4cf5f752dfb047a52e4bee +size 52408 diff --git a/marked/Rel-16/44_series/44004/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/44_series/44004/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e5c4f2446e3b90eb6f4ba2dd8d6b209e4cfee4a --- /dev/null +++ b/marked/Rel-16/44_series/44004/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a903138697fc6f34748b02c8839129a4bb05de8acd99676bd92260b4d0909de +size 46252 diff --git a/marked/Rel-16/44_series/44004/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/44_series/44004/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ade2e0cf6b8116d5d03fe1bf1827c78c6a3e19b --- /dev/null +++ b/marked/Rel-16/44_series/44004/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66e650ec59d303bb9b71255194840bc18d63f330dc9b40c0a6f36cdba3ee78ee +size 17393 diff --git a/marked/Rel-16/44_series/44004/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Rel-16/44_series/44004/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c290d10b9e70e271ed430d7e95be5eb3e7ea9f6 --- /dev/null +++ b/marked/Rel-16/44_series/44004/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a09f5173e8223654dbe6b3d231fc4f98b6c0e5a0550a7a97ba84e4f7619ef71 +size 39780 diff --git a/marked/Rel-16/44_series/44004/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/Rel-16/44_series/44004/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3f32dc1db1702cdeba9eab2a0a0ae18fcc09e61 --- /dev/null +++ b/marked/Rel-16/44_series/44004/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e95f4371c64bf58c2d86df98d450d95f90577acd45a3e61c65291b4d03a082e +size 46880 diff --git a/marked/Rel-16/44_series/44004/446100c084b94817a19c319fa776b412_img.jpg b/marked/Rel-16/44_series/44004/446100c084b94817a19c319fa776b412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2249670dba3a4bb5413d2a56bbfe8ea5d4f7c8c --- /dev/null +++ b/marked/Rel-16/44_series/44004/446100c084b94817a19c319fa776b412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:367ffe1f307f5acacdb541077d9f7158fec80353e2b2f9ca1fa2531c2b95e7bd +size 46032 diff --git a/marked/Rel-16/44_series/44004/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-16/44_series/44004/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ab676647f02c64c5b8c34d809deabdf4c184c2b --- /dev/null +++ b/marked/Rel-16/44_series/44004/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a9dfe76c31b2ee262de04f946e000b87a7ccee46928c78c3367ccf346f9890c +size 51979 diff --git a/marked/Rel-16/44_series/44004/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/44_series/44004/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..701183e5d13acca71f80d75f6c935b9909526060 --- /dev/null +++ b/marked/Rel-16/44_series/44004/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40d54a48a96e8ea91f7681b09ef5b60a810b8f9b1cd063c5fb2df1949f83ac08 +size 45718 diff --git a/marked/Rel-16/44_series/44004/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-16/44_series/44004/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92823180e9fa6dccf25fd1b6f210233c6521f067 --- /dev/null +++ b/marked/Rel-16/44_series/44004/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:096c3680bf4997368d65ce45d0e62d99eb977ba8b9c2681235b21dc847fa50c5 +size 33224 diff --git a/marked/Rel-16/44_series/44004/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/44_series/44004/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f298659d2f57c89481ab8ba1703a981bd6c00392 --- /dev/null +++ b/marked/Rel-16/44_series/44004/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd71cb3fa87edb4abcd6437bc7f2c4c0cfb7455bff619d8b06069def42ab2610 +size 52357 diff --git a/marked/Rel-16/44_series/44004/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg b/marked/Rel-16/44_series/44004/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f59d8af6af87abb9d77770abe7bf509b224847d0 --- /dev/null +++ b/marked/Rel-16/44_series/44004/4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae7f6504febc945e3c0a722c5fa33c0b79e50cb14eeb77ed7a3163cfba684a42 +size 23422 diff --git a/marked/Rel-16/44_series/44004/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/44_series/44004/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb96ff535806fe261c6cb888428ecd6f1f935360 --- /dev/null +++ b/marked/Rel-16/44_series/44004/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff5c2250f18be90bf02f5f7d9640c869b12fd66fa200bcadfe124c4cde9a575e +size 47701 diff --git a/marked/Rel-16/44_series/44004/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Rel-16/44_series/44004/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e28933d26efc917cb9d8dac8e11346acc7c2173c --- /dev/null +++ b/marked/Rel-16/44_series/44004/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c5634a1958e946a664141af6b59d76904b1f32af774ecb53317454101305f06 +size 49790 diff --git a/marked/Rel-16/44_series/44004/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg b/marked/Rel-16/44_series/44004/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a51ae2e2ab737ed706e2ddbf4ed52c40c8797bd0 --- /dev/null +++ b/marked/Rel-16/44_series/44004/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b936256758c01f2c79bcbd9aad5f31239427afaf1515ae53320fd34007f933b +size 36303 diff --git a/marked/Rel-16/44_series/44004/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/44_series/44004/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c58ee0c532457af11934e4f74ab41af30670b81 --- /dev/null +++ b/marked/Rel-16/44_series/44004/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66038f8917c2158a005e9e3190abc121242b705c63739ab3c37bbf4588c3c35d +size 8014 diff --git a/marked/Rel-16/44_series/44004/5cb74e3ca5034698d7eab12de06f8763_img.jpg b/marked/Rel-16/44_series/44004/5cb74e3ca5034698d7eab12de06f8763_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..732651e94f6d4d870694ffc43e96fc7090846bb8 --- /dev/null +++ b/marked/Rel-16/44_series/44004/5cb74e3ca5034698d7eab12de06f8763_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38c3cbb778be304a5fec2e82849b979accf1e828b5860d6a018782720fea5f8c +size 18495 diff --git a/marked/Rel-16/44_series/44004/5fbb4f0de01736f1293333e599410c99_img.jpg b/marked/Rel-16/44_series/44004/5fbb4f0de01736f1293333e599410c99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eef23356942f9135a7772b9ec6dae426cc2f810d --- /dev/null +++ b/marked/Rel-16/44_series/44004/5fbb4f0de01736f1293333e599410c99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6e9e84f295bc48ded49933b80626f95a7687c29fe599ce2f3e8f2cc23afdc45 +size 52759 diff --git a/marked/Rel-16/44_series/44004/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/Rel-16/44_series/44004/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ccc77aab4576b4f48223e8e863fcef8afd0ff58 --- /dev/null +++ b/marked/Rel-16/44_series/44004/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:374998a3ff7c13901d630d0c9e07d8759864eb1486a581d88417290fea63b77b +size 27909 diff --git a/marked/Rel-16/44_series/44004/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/44_series/44004/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5574d971698a599829ba247da5c5ec1def65609 --- /dev/null +++ b/marked/Rel-16/44_series/44004/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe7b0072944c810494a43ee2541a5d637aea7767a6e6f6b328c5c627c4bb5820 +size 46673 diff --git a/marked/Rel-16/44_series/44004/6a5c8326029e6290e69a5f43d6ed4548_img.jpg b/marked/Rel-16/44_series/44004/6a5c8326029e6290e69a5f43d6ed4548_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..025a96270f98af7e8704bd538e2e882c0ab852c6 --- /dev/null +++ b/marked/Rel-16/44_series/44004/6a5c8326029e6290e69a5f43d6ed4548_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72cd8c70edc6905d8acfc01b0a0e097aa698431fd89015d264f50eaed661d0e2 +size 11084 diff --git a/marked/Rel-16/44_series/44004/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-16/44_series/44004/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..405af2c27d95f3e1e1ca80c381ca832cb0090639 --- /dev/null +++ b/marked/Rel-16/44_series/44004/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c938aa99583369d19a6be25c46910e2c348c4a29d8a5a1ec86689b2c8933e1f +size 42231 diff --git a/marked/Rel-16/44_series/44004/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/44_series/44004/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..580c362e9b5b37f60a0ae92f50f35da70ab59233 --- /dev/null +++ b/marked/Rel-16/44_series/44004/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3139052eae5ee945cee7cd1eaf14e7cfeaf3f3d24a6d978ac748088a9ca93ef +size 48362 diff --git a/marked/Rel-16/44_series/44004/718be1eb075833deb7a3b80729a06264_img.jpg b/marked/Rel-16/44_series/44004/718be1eb075833deb7a3b80729a06264_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96d65531fdc5f2080b3955924362a17f6b4df2b9 --- /dev/null +++ b/marked/Rel-16/44_series/44004/718be1eb075833deb7a3b80729a06264_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cc78d89ac78d83fdea83e957bbe36bb76411ebf336f5d824ba451a56e02c936 +size 18839 diff --git a/marked/Rel-16/44_series/44004/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/44_series/44004/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fce0093127308e355e066cbe14da18e014aabeaa --- /dev/null +++ b/marked/Rel-16/44_series/44004/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2af411c7b02be73bbde5a43dd9017f921ec6c8c47f6f87604b792e19e812fa8 +size 46314 diff --git a/marked/Rel-16/44_series/44004/7d0416676d34c96ca27ecc0d38239fea_img.jpg b/marked/Rel-16/44_series/44004/7d0416676d34c96ca27ecc0d38239fea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..780d03670993a443047aef2e87c3632e8f25bb5e --- /dev/null +++ b/marked/Rel-16/44_series/44004/7d0416676d34c96ca27ecc0d38239fea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e6a8e256bb0da72416dde1f85ae160ad3511245ba330580d38e023e7691fbc2 +size 45399 diff --git a/marked/Rel-16/44_series/44004/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/44_series/44004/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9ccb7e02af3b617eec06e8aac22b51c07e11ec7 --- /dev/null +++ b/marked/Rel-16/44_series/44004/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5fb2edfd83bb0a4212c6a083825388402876c1cce11577ad5ce3f275e49d907 +size 13950 diff --git a/marked/Rel-16/44_series/44004/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/marked/Rel-16/44_series/44004/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60b7ca46d13c875242ecc6517f7022b64abec0cd --- /dev/null +++ b/marked/Rel-16/44_series/44004/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8c40c9862c775dacdba21e0c9a008e137399b3938b029cb2ad93bb08280f7be +size 38596 diff --git a/marked/Rel-16/44_series/44004/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Rel-16/44_series/44004/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9856343c489936d35280d61e0f71fa4614264ba --- /dev/null +++ b/marked/Rel-16/44_series/44004/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f24df51a5ba3935debf0779288c1dca4f3f85cc608f07c73c1fc808e871fbf4 +size 31906 diff --git a/marked/Rel-16/44_series/44004/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/44_series/44004/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a175149ccfa2f3a6a39c2aa8a681eb18d2aca33 --- /dev/null +++ b/marked/Rel-16/44_series/44004/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:766283a0b8f765bf2e33d4933fc6724d2cf9216926cb9365777a86555734e8d0 +size 12028 diff --git a/marked/Rel-16/44_series/44004/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/44_series/44004/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e7b18d96cef712d2d1102682c4da314ef43e399 --- /dev/null +++ b/marked/Rel-16/44_series/44004/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:746f0a78d4adb5be5d2328286416b6eee0af21ed410e4312241f4f7428e23190 +size 47123 diff --git a/marked/Rel-16/44_series/44004/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/44_series/44004/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa6f555656ed11770f1375badb976bade10067dd --- /dev/null +++ b/marked/Rel-16/44_series/44004/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:081512438ffa9156b8aedb33f9f4340252861afba35ccad5cdd534c0d7487dd2 +size 62003 diff --git a/marked/Rel-16/44_series/44004/836008eb3303ade9e269f93c04dc0a2e_img.jpg b/marked/Rel-16/44_series/44004/836008eb3303ade9e269f93c04dc0a2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2a1d37707cdf0afa70d730900700296b88a9228 --- /dev/null +++ b/marked/Rel-16/44_series/44004/836008eb3303ade9e269f93c04dc0a2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0670c73eafde46c1aaeb5ed49d4746dbbac41e304b928a3793827bc51aedc38 +size 18370 diff --git a/marked/Rel-16/44_series/44004/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/Rel-16/44_series/44004/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1df3df8ef30e8d13ffb2babeea52cdfcd3f2f8d --- /dev/null +++ b/marked/Rel-16/44_series/44004/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23a2198922f61367e179a13fbb47932fc959b03a05b87ab8f677585198b22eb9 +size 46608 diff --git a/marked/Rel-16/44_series/44004/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/Rel-16/44_series/44004/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5159c545b4adc75dd4e0b69b6df31aee3de95074 --- /dev/null +++ b/marked/Rel-16/44_series/44004/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:316b95a7f35341292f298c9e1ee20d26e77a9ba16f38028c4ff91698e7e4ed0b +size 24461 diff --git a/marked/Rel-16/44_series/44004/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/44_series/44004/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..130f67a32bf8caf520c993dbaaf8e7665a72d89f --- /dev/null +++ b/marked/Rel-16/44_series/44004/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d99ee3dd7ff7a39070cb53bcd9ef2b5a7dceca330fa70a1a62e2575680839d9 +size 30220 diff --git a/marked/Rel-16/44_series/44004/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/44_series/44004/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79415c6cf2d22f23795acf9efd8957215b55869d --- /dev/null +++ b/marked/Rel-16/44_series/44004/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:551554fab2f7af398e7a1664a058fae29ea39f9f400cf800358ce390b1f61ddf +size 47130 diff --git a/marked/Rel-16/44_series/44004/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/44_series/44004/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ce2c667d53ddd610cf6e1f6fecbc0f622de1d32 --- /dev/null +++ b/marked/Rel-16/44_series/44004/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4094c6d9259ed73615fecc3bea72ede4fb4e9489df39fa92502b51afce5a6cca +size 51435 diff --git a/marked/Rel-16/44_series/44004/94d3fdcc244924326f02533aeb2d93fc_img.jpg b/marked/Rel-16/44_series/44004/94d3fdcc244924326f02533aeb2d93fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf4fb57c698519a12a5f06ee9e8735d40a3aeeae --- /dev/null +++ b/marked/Rel-16/44_series/44004/94d3fdcc244924326f02533aeb2d93fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad008e030cfb13c3d678aeae63a8c00d7bd33ac1c712001c3dbb9524b62e9f45 +size 15603 diff --git a/marked/Rel-16/44_series/44004/9a159e2112eac7be06bdb97e84a0c49a_img.jpg b/marked/Rel-16/44_series/44004/9a159e2112eac7be06bdb97e84a0c49a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ea4f1614f6c9cdb40207c50a8de1a2ec77dda26 --- /dev/null +++ b/marked/Rel-16/44_series/44004/9a159e2112eac7be06bdb97e84a0c49a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bae987e61a3d60a2926e65666281b25ee3e2407c75425d921e75a97d71f0e368 +size 37820 diff --git a/marked/Rel-16/44_series/44004/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/44_series/44004/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..084319d3be8f7a88c4dd5fad4c810c32a3228c72 --- /dev/null +++ b/marked/Rel-16/44_series/44004/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27ea7ff4165f963cb6c5d2e0579053111395d57d2fa7d1d5f30d27b5d2cd7a6f +size 7597 diff --git a/marked/Rel-16/44_series/44004/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/44_series/44004/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5d64ab63f49e11206b1bab4a13061e7cae24d08 --- /dev/null +++ b/marked/Rel-16/44_series/44004/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef403c77664455ba03f323bd362fa7508825bba3ecdd6c63c0f86fcc9e443a26 +size 47172 diff --git a/marked/Rel-16/44_series/44004/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/44_series/44004/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14466088951942d913b817b66ac7a23ea1a4b35f --- /dev/null +++ b/marked/Rel-16/44_series/44004/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43bafc58381782a9954cc278c312f86295f0bf202d0eaf4222275d1b4c65da68 +size 51049 diff --git a/marked/Rel-16/44_series/44004/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/marked/Rel-16/44_series/44004/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..991279e1f44751a9cb51e8629e9f5ae04756451e --- /dev/null +++ b/marked/Rel-16/44_series/44004/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c51bfafda535a39601d0c0058f75d63c65e24cee311fa7b9b0ced2b9b39817e0 +size 15885 diff --git a/marked/Rel-16/44_series/44004/a89d151b67109378baed0c117830cf78_img.jpg b/marked/Rel-16/44_series/44004/a89d151b67109378baed0c117830cf78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638c9a21c422b891bfe6ad5e137f50de10ae9b22 --- /dev/null +++ b/marked/Rel-16/44_series/44004/a89d151b67109378baed0c117830cf78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98da7b81b71e44d804a91e35b39e3a66ee805d6d72963337b88a08d83adf6a4d +size 21325 diff --git a/marked/Rel-16/44_series/44004/a97518a839da75f8379c578562b01bc2_img.jpg b/marked/Rel-16/44_series/44004/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e10eff98b5539aab13cc80591893424ff20fc83 --- /dev/null +++ b/marked/Rel-16/44_series/44004/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb846a2354ed83aa012d886776e7ce7604b082cb314bbc5bffcbc49ac3bd9aa1 +size 45119 diff --git a/marked/Rel-16/44_series/44004/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-16/44_series/44004/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8123c5fa2525d0c46ce9c52a79c638f4e9f6cc7c --- /dev/null +++ b/marked/Rel-16/44_series/44004/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80761877ed405105a84ab9c8f28cb824e95c494911cdfd30aa76969989ee8655 +size 26655 diff --git a/marked/Rel-16/44_series/44004/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/44_series/44004/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfd20ccbf2c7f8915e70543009864ecd4bff2dc2 --- /dev/null +++ b/marked/Rel-16/44_series/44004/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:567b11bc4e8448fef2802a71d3b9649b51a722c94b9e1d7d856c795affb9a7cf +size 9371 diff --git a/marked/Rel-16/44_series/44004/b0211cee4b20034939d883ac0d70f696_img.jpg b/marked/Rel-16/44_series/44004/b0211cee4b20034939d883ac0d70f696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d626c586baaa64b5e3e3ef01e1b1f745437fb4b --- /dev/null +++ b/marked/Rel-16/44_series/44004/b0211cee4b20034939d883ac0d70f696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b16bb8f5f1670c361edd3f08782a11b499f292be76f9456ee842212ecf30ed3 +size 21195 diff --git a/marked/Rel-16/44_series/44004/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/44_series/44004/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ec74aee1fa0b6395ddb8c452d1007206033ee90 --- /dev/null +++ b/marked/Rel-16/44_series/44004/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f24407fa2315012d566ece8caa69c78107114f017a4363de841620399f7ce056 +size 41783 diff --git a/marked/Rel-16/44_series/44004/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-16/44_series/44004/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dec915461ad8d05693f96ab382d50440135b3a5 --- /dev/null +++ b/marked/Rel-16/44_series/44004/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc80a005428095ba31175521f0b9c06e9bdf3008f96cdba023bb678329b2b431 +size 26152 diff --git a/marked/Rel-16/44_series/44004/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/44_series/44004/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..074c6e5ab825b95fad61f5da64a320865e07c698 --- /dev/null +++ b/marked/Rel-16/44_series/44004/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01322518ec3efe84caffb6cf94d5e0af359063479ff7fd818d83b44aa3445de2 +size 52624 diff --git a/marked/Rel-16/44_series/44004/b81d1613e285a9353171cdc5ef97a1f0_img.jpg b/marked/Rel-16/44_series/44004/b81d1613e285a9353171cdc5ef97a1f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c01c73bd1265a620cf06e4ae2db11ad64bcfede --- /dev/null +++ b/marked/Rel-16/44_series/44004/b81d1613e285a9353171cdc5ef97a1f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b5df7ffa01a6b81eb0ea1fa4dcc79bf43a817342982ed2261f17511075564e5 +size 26418 diff --git a/marked/Rel-16/44_series/44004/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/marked/Rel-16/44_series/44004/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f569353a515d37e502c549d7f71335bf702e9db --- /dev/null +++ b/marked/Rel-16/44_series/44004/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18ea554b2364d3da01a1f702952dc5b78ed5dc1b1ad5e1a015c04cf3be8ccf3d +size 44656 diff --git a/marked/Rel-16/44_series/44004/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/44_series/44004/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5972dd87aef87899d6229c1e6a0ddefe3ba5776a --- /dev/null +++ b/marked/Rel-16/44_series/44004/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:363ae889893340dbbebb14088a50cceab90f8a23fffb276f5778041757839f13 +size 48032 diff --git a/marked/Rel-16/44_series/44004/c42e926097d01653b793c04b49e764b2_img.jpg b/marked/Rel-16/44_series/44004/c42e926097d01653b793c04b49e764b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e3e342af03bd5e2855f9217eaef35925d0c2537 --- /dev/null +++ b/marked/Rel-16/44_series/44004/c42e926097d01653b793c04b49e764b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fc1821c211c1baedd2e09ff7dac961b6115a76fba982d339e46ec5e75e1c8bd +size 7076 diff --git a/marked/Rel-16/44_series/44004/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-16/44_series/44004/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61055c8b1b907e40045283600a029c0f5cad34f7 --- /dev/null +++ b/marked/Rel-16/44_series/44004/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4660722477103d45db70fb4dcaf04334f447306818b7098692f7c230aa39022 +size 12992 diff --git a/marked/Rel-16/44_series/44004/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/44_series/44004/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea8ddcbd773cbea0f2bee826806018380480b709 --- /dev/null +++ b/marked/Rel-16/44_series/44004/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2d93e94d54b4b96fc7c26598dc6e823a493c0cc47af6081a9bd0edf4e196a9b +size 53620 diff --git a/marked/Rel-16/44_series/44004/ced309874aec0546651b0976d5030a42_img.jpg b/marked/Rel-16/44_series/44004/ced309874aec0546651b0976d5030a42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aae44ee3a2a8825564b8b2dc93cab326a1f2e4de --- /dev/null +++ b/marked/Rel-16/44_series/44004/ced309874aec0546651b0976d5030a42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89822f2159b5060a11c698c1ecb91cd1f63560af21688cec26979de9798ce6e6 +size 25965 diff --git a/marked/Rel-16/44_series/44004/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-16/44_series/44004/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b104cc4fb3b4a2eeec1b854dbb30cbce2c5b15c --- /dev/null +++ b/marked/Rel-16/44_series/44004/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0105cb4bd0e284d1fccc14822028922927a8121f65c2a132b2e289c2625af269 +size 47991 diff --git a/marked/Rel-16/44_series/44004/db7cb51aac8519daab50e2171cecae82_img.jpg b/marked/Rel-16/44_series/44004/db7cb51aac8519daab50e2171cecae82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dd01d91bc7228c6e61a715856bf142e90682ab0 --- /dev/null +++ b/marked/Rel-16/44_series/44004/db7cb51aac8519daab50e2171cecae82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c06ad7705afe20008f75f06015b20e93ccb56dfdce8cdf9ebcc535d6633a89f +size 25663 diff --git a/marked/Rel-16/44_series/44004/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/44_series/44004/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f5cc932c7c16f6e2287f2b47b1a742bc9efd0a5 --- /dev/null +++ b/marked/Rel-16/44_series/44004/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2034e3f0ba783dd3fbedcc29d44768b040496f243e2a969b0916855fec311a5e +size 28570 diff --git a/marked/Rel-16/44_series/44004/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/44_series/44004/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8babe96970bf8565ad2cd1123c761d45712e9367 --- /dev/null +++ b/marked/Rel-16/44_series/44004/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09bee101ba536e3f6b6a570e05849a8626cea4281746642bd72844a26c69985f +size 10749 diff --git a/marked/Rel-16/44_series/44004/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/marked/Rel-16/44_series/44004/e05c1a13b44ab41505609d82b00cf4df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13afe13be736387a44d247472d647044ec3b9b21 --- /dev/null +++ b/marked/Rel-16/44_series/44004/e05c1a13b44ab41505609d82b00cf4df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1176db9f09b0dc29116dba5f7bebe1c7ebaee76ec6a0da0b34657e1c23817e37 +size 25932 diff --git a/marked/Rel-16/44_series/44004/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/44_series/44004/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0289b291bae268c667af1d873d48e7f8973adba --- /dev/null +++ b/marked/Rel-16/44_series/44004/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bca938af1f17d92219abcec0c9951a26e47f74c3ca05fdd0cc7da4ddfa9e9c0 +size 21331 diff --git a/marked/Rel-16/44_series/44004/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-16/44_series/44004/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e66c1e901245148bf65db1d97a68e523f04e379a --- /dev/null +++ b/marked/Rel-16/44_series/44004/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b69fca30f3ea049f3f912d7a241e194e02457d47f37d5c9d8eaab29a4f5ba7cd +size 30480 diff --git a/marked/Rel-16/44_series/44004/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg b/marked/Rel-16/44_series/44004/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c551939704442dddce6bc4c2af42fcc470fb7cf9 --- /dev/null +++ b/marked/Rel-16/44_series/44004/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:840f1aa778666f1139f7a5b0a24ddaaae33c4d0953cbc01fcf6113e4fcd9bbcd +size 31130 diff --git a/marked/Rel-16/44_series/44004/f1091147d93cee4dfa88498610e395a7_img.jpg b/marked/Rel-16/44_series/44004/f1091147d93cee4dfa88498610e395a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41ba199958b75f62d3617e773274f2d531244745 --- /dev/null +++ b/marked/Rel-16/44_series/44004/f1091147d93cee4dfa88498610e395a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de57bdada9f87789d4d3dbd8df55cd90525eda9e0b0da3ce004c670a36f14324 +size 50172 diff --git a/marked/Rel-16/44_series/44004/f56ab8d50c10444a7043b7e30880cd0a_img.jpg b/marked/Rel-16/44_series/44004/f56ab8d50c10444a7043b7e30880cd0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e64eee6f07efe277807ac0f4fe57d62d45384ede --- /dev/null +++ b/marked/Rel-16/44_series/44004/f56ab8d50c10444a7043b7e30880cd0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32a84b80d451719f7ab2ee6fee9f3c69265fef65c6b41e8795439ee45b87e7df +size 20966 diff --git a/marked/Rel-16/44_series/44004/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg b/marked/Rel-16/44_series/44004/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..467cacbeb2ed76af3352ed8cc377a5f42ebe9724 --- /dev/null +++ b/marked/Rel-16/44_series/44004/f9528ea5b0d2cd0192b7242e5a6af969_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7986f325cbe83a29b7433c4919e7aa53185cab8dc7a624679d68da99fafa1ccf +size 17227 diff --git a/marked/Rel-16/44_series/44004/raw.md b/marked/Rel-16/44_series/44004/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1ff2176989b7e33ef1e90e23107ab7b73a312a01 --- /dev/null +++ b/marked/Rel-16/44_series/44004/raw.md @@ -0,0 +1,1887 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 1a References..... | 7 | +| 2 Interfaces to the physical layer..... | 8 | +| 2.1 Interface to the Data Link Layer ..... | 9 | +| 2.1a Interface to the Radio Link Control and Medium Access Control layer ..... | 9 | +| 2.1b Flexible Layer One Interface to the Radio Link Control and Medium Access Control layer ..... | 9 | +| 2.2 Interface to radio resource management ..... | 10 | +| 2.3 Interface to other functional units ..... | 10 | +| 3 Service of the physical layer ..... | 10 | +| 3.1 Service Access Point..... | 10 | +| 3.2 Service of the physical layer ..... | 12 | +| 3.2.1 Specific services of the physical layer in the MS..... | 13 | +| 4 Primitives of the physical layer..... | 14 | +| 4.1 Generic names of primitives between layers 1 and 2 for the transfer of layer 2 frames and RLC/MAC blocks ..... | 14 | +| 4.2 Generic names of primitives between layer 1 and the RR-management entity of layer 3 ..... | 14 | +| 4.3 Primitive types..... | 15 | +| 4.4 Parameter definition ..... | 15 | +| 5 Physical layer procedures..... | 17 | +| 5.0 General ..... | 17 | +| 5.1 States of the physical layer..... | 17 | +| 5.2 Control procedures ..... | 18 | +| 5.3 Physical layer interface procedures..... | 18 | +| 6 Physical layer protocol header ..... | 18 | +| 6.0 General ..... | 18 | +| 6.1 Physical layer protocol fields and procedures..... | 18 | +| 7 Block transmission..... | 19 | +| 7.0 General ..... | 19 | +| 7.1 SACCH downlink block format..... | 19 | +| 7.1.1 A/Gb mode ..... | 19 | +| 7.1.2 Iu mode ..... | 20 | +| 7.2 SACCH uplink block format..... | 21 | +| 7.2.1 A/Gb mode ..... | 21 | +| 7.2.2 Iu mode ..... | 21 | +| 7.3 FACCH/SDCCH/CCCH/BCCH/CBCH downlink block format ..... | 21 | +| 7.3.1 CCCH/BCCH/CBCH downlink block format..... | 21 | +| 7.3.2 FACCH/SDCCH downlink block format..... | 22 | +| 7.3.2.1 A/Gb mode ..... | 22 | +| 7.3.2.2 Iu mode ..... | 22 | +| 7.4 FACCH/SDCCH uplink block format ..... | 23 | +| 7.4.1 A/Gb mode ..... | 23 | +| 7.4.2 Iu mode ..... | 23 | +| 7.4a RACH uplink / Uplink access burst block format..... | 23 | +| 7.5 PBCCH/PCCCH downlink/PACCH block format ..... | 24 | +| 7.6 PDTCH block formats..... | 25 | +| 7.6.1 PDTCH block type 1 (CS-1) format..... | 25 | +| 7.6.2 PDTCH block type 2 (CS-2) format..... | 25 | +| 7.6.3 PDTCH block type 3 (CS-3) format..... | 26 | +| 7.6.4 PDTCH block type 4 (CS-4) format..... | 26 | +| 7.6.5 PDTCH block type 5 (MCS-1) format..... | 26 | +| 7.6.6 PDTCH block type 6 (MCS-2) format..... | 27 | +| 7.6.7 PDTCH block type 7 (MCS-3) format..... | 27 | +| 7.6.8 PDTCH block type 8 (MCS-4) format..... | 28 | + +| | | | +|----------|---------------------------------------------------------------------|----| +| 7.6.9 | PDTCH block type 9 (MCS-5) format ..... | 28 | +| 7.6.9.1 | Uplink ..... | 28 | +| 7.6.9.2 | Downlink ..... | 29 | +| 7.6.10 | PDTCH block type 10 (MCS-6) format ..... | 29 | +| 7.6.10.1 | Uplink ..... | 29 | +| 7.6.10.2 | Downlink ..... | 29 | +| 7.6.11 | PDTCH block type 11 (MCS-7) format ..... | 30 | +| 7.6.11.1 | Uplink ..... | 30 | +| 7.6.11.2 | Downlink ..... | 30 | +| 7.6.12 | PDTCH block type 12 (MCS-8) format ..... | 31 | +| 7.6.12.1 | Uplink ..... | 31 | +| 7.6.12.2 | Downlink ..... | 31 | +| 7.6.13 | PDTCH block type 13 (MCS-9) format ..... | 32 | +| 7.6.13.1 | Uplink ..... | 32 | +| 7.6.13.2 | Downlink ..... | 32 | +| 7.6.14 | PDTCH block type 14 (UAS-7) format (uplink only)..... | 33 | +| 7.6.15 | PDTCH block type 15 (UAS-8) format (uplink only)..... | 33 | +| 7.6.16 | PDTCH block type 16 (UAS-9) format (uplink only)..... | 34 | +| 7.6.17 | PDTCH block type 17 (UAS-10) format (uplink only)..... | 35 | +| 7.6.18 | PDTCH block type 18 (UAS-11) format (uplink only)..... | 35 | +| 7.6.19 | PDTCH block type 19 (UBS-5) format (uplink only)..... | 36 | +| 7.6.20 | PDTCH block type 20 (UBS-6) format (uplink only)..... | 36 | +| 7.6.21 | PDTCH block type 21 (UBS-7) format (uplink only)..... | 36 | +| 7.6.22 | PDTCH block type 22 (UBS-8) format (uplink only)..... | 37 | +| 7.6.23 | PDTCH block type 23 (UBS-9) format (uplink only)..... | 37 | +| 7.6.24 | PDTCH block type 24 (UBS-10) format (uplink only)..... | 38 | +| 7.6.25 | PDTCH block type 25 (UBS-11) format (uplink only)..... | 38 | +| 7.6.26 | PDTCH block type 26 (UBS-12) format (uplink only)..... | 39 | +| 7.6.27 | PDTCH block type 27 (DAS-5) format (downlink only)..... | 39 | +| 7.6.28 | PDTCH block type 28 (DAS-6) format (downlink only)..... | 40 | +| 7.6.29 | PDTCH block type 29 (DAS-7) format (downlink only)..... | 41 | +| 7.6.30 | PDTCH block type 30 (DAS-8) format (downlink only)..... | 41 | +| 7.6.31 | PDTCH block type 31 (DAS-9) format (downlink only)..... | 42 | +| 7.6.32 | PDTCH block type 32 (DAS-10) format (downlink only)..... | 42 | +| 7.6.33 | PDTCH block type 33 (DAS-11) format (downlink only)..... | 43 | +| 7.6.34 | PDTCH block type 34 (DAS-12) format (downlink only)..... | 43 | +| 7.6.35 | PDTCH block type 35 (DBS-5) format (downlink only)..... | 44 | +| 7.6.36 | PDTCH block type 36 (DBS-6) format (downlink only)..... | 44 | +| 7.6.37 | PDTCH block type 37 (DBS-7) format (downlink only)..... | 44 | +| 7.6.38 | PDTCH block type 38 (DBS-8) format (downlink only)..... | 45 | +| 7.6.39 | PDTCH block type 39 (DBS-9) format (downlink only)..... | 45 | +| 7.6.40 | PDTCH block type 40 (DBS-10) format (downlink only)..... | 46 | +| 7.6.41 | PDTCH block type 41 (DBS-11) format (downlink only)..... | 46 | +| 7.6.42 | PDTCH block type 42 (DBS-12) format (downlink only)..... | 47 | +| 7.7 | PRACH uplink/PACCH uplink short acknowledgement block formats ..... | 47 | +| 7.8 | PTCCH downlink block format ..... | 48 | +| 7.9 | PTCCH uplink block formats..... | 49 | +| 7.9a | Transport block formats ( Iu mode )..... | 49 | +| 7.9a.1 | Generic transport block format..... | 49 | +| 7.9a.2 | Transport block format for signalling TFC ..... | 49 | +| 7.9b | EC-BCCH/EC-CCCH/EC-PDTCH/EC-PACCH block formats ..... | 50 | +| 7.9b.1 | EC-BCCH..... | 50 | +| 7.9b.2 | EC-CCCH..... | 50 | +| 7.9b.2.1 | EC-PCH/EC-AGCH ..... | 50 | +| 7.9b.2.2 | EC-RACH..... | 50 | +| 7.9b.3 | EC-PDTCH..... | 50 | +| 7.9b.4 | EC-PACCH ..... | 51 | +| 7.9b.4.1 | Downlink ..... | 51 | +| 7.9b.4.2 | Uplink ..... | 51 | +| 7.10 | Order of bit transmission..... | 51 | + +8 Vocabulary........................................................................................................................................................... 52 + +Annex A (informative): Change History................................................................................................................ 54 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the service offered by the physical layer (3GPP TS 45-series of Technical Specifications) of the MS-BS interface (3GPP TS 45- and 44-series of Technical Specifications). Its main objective is to be a guidance for the interface between the 3GPP Technical Specifications in the 45-series and the 44-series. It also specifies the format of signalling channels and the order of bit transmission. + +As far as possible, the present document makes use of the layering principles of the Reference Model for Open System Interconnection (OSI) as contained in ITU-T Recommendations X.200 and X.210. + +# --- 1a 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.011: "Service accessibility". +- [3] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM System". +- [4] 3GPP TS 43.020: "Security-related network functions". +- [5] Void. +- [6] Void. +- [7] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". +- [8] 3GPP TS 44.005: "Data Link (DL) layer; General aspects". +- [9] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". +- [10] Void. +- [11] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [12] Void. +- [13] Void. +- [14] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [15] Void. +- [16] Void. +- [17] Void. +- [17a] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [18] Void. + +- [19] Void. +- [20] Void. +- [21] Void. +- [22] Void. +- [23] Void. +- [24] Void. +- [25] Void. +- [26] Void. +- [26a] Void. +- [26b] Void. +- [27] 3GPP TS 45.001: "Physical Layer on the Radio Path (General Description)". +- [28] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [29] 3GPP TS 45.003: "Channel coding". +- [30] Void. +- [31] 3GPP TS 45.005: "Radio transmission and reception". +- [32] 3GPP TS 45.008: "Radio subsystem link control". +- [33] 3GPP TS 45.010: "Radio subsystem synchronization". +- [34] Void. +- [35] ITU-T Recommendation X.200: "Information technology; Open Systems Interconnection; Basic Reference Model: The basic model". +- [36] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic Reference Model: Conventions for the definition of OSI services". +- [37] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification". +- [38] 3GPP TR 45.902: "Flexible Layer One". +- [39] 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2". + +# --- 2 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. These bit streams are transferred on traffic channels, packet data traffic channels and control channels as defined in 3GPP TS 44.003. + +NOTE: For GSM application the physical layer may also be referred to as the radio subsystem. However, the radio subsystem supports functions additional to those described in the present document. + +The physical layer interfaces the Data Link Layer, the Radio Link Control and Medium Access Control layer and the supported functional units of the application (figure 2). + +![Diagram showing the interfaces with the Physical Layer. The Physical Layer is at the bottom. Above it are the Data Link Layer and the RLC/MAC layer. The Data Link Layer interfaces with the Physical Layer via PH-primitives. The RLC/MAC layer interfaces with the Physical Layer via PH-primitives. Above the Data Link Layer and RLC/MAC layer are the RR (layer 3) and RRC (layer 3) entities. The RR (layer 3) entity interfaces with the Data Link Layer via MPH-primitives. The RRC (layer 3) entity interfaces with the RLC/MAC layer via MPH-primitives. Both RR (layer 3) and RRC (layer 3) entities have interfaces to upper layers. The RLC/MAC layer also has an interface to other functional units via TCH.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +graph TD + UL[to upper layers] + RR[RR layer 3] + RRC[RRC layer 3] + DDL[Data Link Layer] + RML[RLC/MAC layer] + PL[Physical Layer] + OFU[to other functional units] + + RR --- UL + RRC --- UL + RR --- DDL + RRC --- RML + DDL <--> PH1[PH-primitives] --- PL + RR <--> MPH1[MPH-primitives] --- PL + RRC <--> MPH2[MPH-primitives] --- PL + RML <--> PH2[PH-primitives] --- PL + RML <--> TCH --- OFU + +``` + +Diagram showing the interfaces with the Physical Layer. The Physical Layer is at the bottom. Above it are the Data Link Layer and the RLC/MAC layer. The Data Link Layer interfaces with the Physical Layer via PH-primitives. The RLC/MAC layer interfaces with the Physical Layer via PH-primitives. Above the Data Link Layer and RLC/MAC layer are the RR (layer 3) and RRC (layer 3) entities. The RR (layer 3) entity interfaces with the Data Link Layer via MPH-primitives. The RRC (layer 3) entity interfaces with the RLC/MAC layer via MPH-primitives. Both RR (layer 3) and RRC (layer 3) entities have interfaces to upper layers. The RLC/MAC layer also has an interface to other functional units via TCH. + +Figure 2: Interfaces with the Physical Layer + +## 2.1 Interface to the Data Link Layer + +The physical layer interfaces the data link layer. On this interface control channels are supported. The data link layer is specified in 3GPP TS 44.005 and 44.006. Communication between the Physical Layer and the Data Link Layer is in an abstract way performed by means of PH-primitives. They do not constrain implementations. + +NOTE: The terms physical layer and layer 1, and data link layer and layer 2, will be used synonymously in the present document. + +The PH-primitives exchanged between the physical layer and the data link layer are used for the transfer of layer 2 frames. They are also used to indicate the establishment of channels to layer 2. + +### 2.1a Interface to the Radio Link Control and Medium Access Control layer + +The physical layer interfaces the Radio Link Control and Medium Access Control (RLC/MAC) layer. On this interface packet data control channels and packet data traffic channels are supported when MS is operating in *A/Gb mode*; when MS is operating in *Iu mode*, traffic channels, dedicated control channels, packet data control channels and packet data traffic channels are supported. The RLC/MAC layer is specified in 3GPP TS 44.060 (*A/Gb mode*). Communication between the Physical Layer and the RLC/MAC layer is in an abstract way performed by means of PH-primitives. They do not constrain implementations. + +The PH-primitives exchanged between the physical layer and the RLC/MAC layer are used for the transfer of RLC/MAC blocks. They are also used to indicate the establishment of packet data physical channels (*A/Gb mode*) or shared basic physical subchannels (*Iu mode*) to the RLC/MAC layer. + +## 2.1b Flexible Layer One Interface to the Radio Link Control and Medium Access Control layer + +In *Iu mode*, when the Flexible Layer One is used the physical layer interfaces the Radio Link Control and Medium Access Control (RLC/MAC) layer (see 3GPP TR 45.902). On this interface transport channels are supported. Communication between the Physical Layer and the RLC/MAC layer is in an abstract way performed by means of PH-primitives. They do not constrain implementations. + +The PH-primitives exchanged between the physical layer and the RLC/MAC layer are used for the transfer of transport blocks. + +## 2.2 Interface to radio resource management + +The physical layer interfaces the radio resource management (RR or RRC) entity of layer 3 in the MS and in the network. When the MS is operating in *A/Gb mode* the radio resource management is provided by the RR entity whilst when operating in *Iu mode* the radio resource management is provided by the RRC entity. + +Communication is performed in an abstract way by means of MPH-primitives. They do not constrain implementations. The primitives exchanged with the RR-management entity are related to the assignment of channels, physical layer system information (including measurement results), etc. + +## 2.3 Interface to other functional units + +The physical layer interfaces other functional units in the MS and in the network for supporting traffic channels. These interfaces are described in the 26, 27 and 46 series of Technical Specifications. + +# 3 Service of the physical layer + +The physical layer supports transfer of bit streams on the radio medium according to the Technical Specifications of the 45-series. The scope of the 45-series of Technical Specifications is the definition of a framework for operation on the radio medium. The application of this framework on the radio medium results in a transmission service. General characteristics of the service obtained by applying the framework of the 45-series at the operation on the radio medium are described in this clause. + +## 3.1 Service Access Point + +In the Reference Model for Open System Interconnection, Service Access Points (SAPs) of a layer are defined as gates through which services are offered to an adjacent higher layer (figure 3.1.a). Through a SAP the physical layer offers a service to the data link layer. The SAP is used both for the control of the service providing entity (in case this is the physical layer; commands related to the establishment and release of channels) and the transfer of data (in case of the physical layer; the transfer of bits). The physical layer service access points defined in the present document differ from the OSI physical layer Service Access Points; the layer 3 RR-management instead of the data link layer controls the SAPs (establishment and release of channels). + +![Diagram illustrating the Service Access Point (SAP) principle. It shows two 'adjacent higher layer' blocks at the top, each connected to a hexagonal 'SAP' block. Both SAP blocks are connected to a single horizontal line representing the 'transmission medium' at the bottom.](b0211cee4b20034939d883ac0d70f696_img.jpg) + +Diagram illustrating the Service Access Point (SAP) principle. It shows two 'adjacent higher layer' blocks at the top, each connected to a hexagonal 'SAP' block. Both SAP blocks are connected to a single horizontal line representing the 'transmission medium' at the bottom. + +Figure 3.1.a: Service Access Point principle + +On the physical layer of the GSM system a SAP is defined between the physical layer and the data link layer for each control channel (figure 3.1.b, figure 3.1.b1 and figure 3.1.b2). The characteristics of SAPs (channels) are listed in 3GPP TS 44.003. + +![Diagram showing the SAPs between the physical layer and the data link layer. At the top is the 'Data Link Layer'. Below it are six hexagonal blocks representing different channels: BCCH, PCH+AGCH, RACH, SDCCH, SACCH, and FACCH. Each hexagon has a vertical line connecting it to the 'Physical layer' at the bottom. The hexagons are connected horizontally in a sequence.](4dadfd8b8240e9d83f974e3f0fdd18df_img.jpg) + +Diagram showing the SAPs between the physical layer and the data link layer. At the top is the 'Data Link Layer'. Below it are six hexagonal blocks representing different channels: BCCH, PCH+AGCH, RACH, SDCCH, SACCH, and FACCH. Each hexagon has a vertical line connecting it to the 'Physical layer' at the bottom. The hexagons are connected horizontally in a sequence. + +Figure 3.1.b: SAPs between the physical layer and the data link layer when the MS is operating in A/Gb mode + +![Diagram showing the SAP between the physical layer and the data link layer for BCCH in Iu mode. A single hexagonal SAP symbol is connected by vertical lines to 'Data Link layer' above and 'Physical layer' below.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Data Link layer +BCCH + +Physical layer + +Diagram showing the SAP between the physical layer and the data link layer for BCCH in Iu mode. A single hexagonal SAP symbol is connected by vertical lines to 'Data Link layer' above and 'Physical layer' below. + +**Figure 3.1.b.1: SAPs between the physical layer and the data link layer when the MS is capable of operating in *Iu mode*** + +![Diagram showing three SAPs between the physical layer and the data link layer for EC operation in A/Gb mode. The SAPs are labeled EC-BCCH, EC-PCH+(EC-)AGCH, and (EC-)RACH. They are positioned between the 'Data Link Layer' and 'Physical Layer'.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Data Link Layer + +EC-BCCH      EC-PCH+(EC-)AGCH      (EC-)RACH + +Physical Layer + +Diagram showing three SAPs between the physical layer and the data link layer for EC operation in A/Gb mode. The SAPs are labeled EC-BCCH, EC-PCH+(EC-)AGCH, and (EC-)RACH. They are positioned between the 'Data Link Layer' and 'Physical Layer'. + +**Figure 3.1.b.2: SAPs between the physical layer and the data link layer when the MS has enabled EC operation (see 3GPP TS 43.064) and is operating in *A/Gb mode*.** + +Moreover, on the physical layer of the GSM system a SAP is defined between the physical layer and the RLC/MAC layer for the packet data control channels, dedicated control channels (*Iu mode*), traffic channels (*Iu mode*) and the packet data traffic channel and the transport channels (FLO in *Iu mode*) (see figure 3.1.c, figure 3.1.d and figure 3.1.e). Multiplexing of these channels is controlled by the RLC/MAC layer, see 3GPP TS 44.060 (*A/Gb mode*). The characteristics of channels are listed in 3GPP TS 44.003. + +![Diagram showing the SAP between the physical layer and the RLC/MAC layer in A/Gb mode. A single hexagonal SAP symbol represents multiple channels: PBCCH + PPCH + PAGCH + PRACH + (EC-)PACCH + (EC-)PDTCH.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +RLC/MAC Layer + +PBCCH + PPCH + PAGCH + PRACH + (EC-)PACCH + (EC-)PDTCH + +Physical Layer + +Diagram showing the SAP between the physical layer and the RLC/MAC layer in A/Gb mode. A single hexagonal SAP symbol represents multiple channels: PBCCH + PPCH + PAGCH + PRACH + (EC-)PACCH + (EC-)PDTCH. + +**Figure 3.1.c: SAP between the physical layer and the RLC/MAC layer when the MS is operating in *A/Gb mode*** + +![Diagram showing multiple SAPs between the physical layer and the RLC/MAC layer in Iu mode. On the left is a combined SAP for packet channels, followed by individual SAPs for SDCCH, SACCH, TCH, and FACCH.](18442e4e239480f0c3c95b547aa8fde2_img.jpg) + +PBCCH+PPCH+ +PAGCH+PRACH+ +PDTCH+PACCH + +RLC/MAC layer + +SDCCH      SACCH      TCH      FACCH + +Physical layer + +Diagram showing multiple SAPs between the physical layer and the RLC/MAC layer in Iu mode. On the left is a combined SAP for packet channels, followed by individual SAPs for SDCCH, SACCH, TCH, and FACCH. + +**Figure 3.1.d: SAP between the physical layer and the RLC/MAC layer when the MS is operating in *Iu mode*** + +![Diagram illustrating the Service Access Point (SAP) between the physical layer and the RLC/MAC layer when the MS is operating in Iu mode with FLO. The diagram shows a horizontal sequence of six hexagonal nodes representing the SAPs. Above the first node are the logical channels: PBCCH+PPCH+, PAGCH+PRACH+, and PDTCH+PACCH. Above the subsequent nodes are: SDCCH, SACCH, TCH, FACCH, and TrCH. The label 'RLC/MAC layer' is centered above the sequence, and 'Physical layer' is centered below the sequence.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Diagram illustrating the Service Access Point (SAP) between the physical layer and the RLC/MAC layer when the MS is operating in Iu mode with FLO. The diagram shows a horizontal sequence of six hexagonal nodes representing the SAPs. Above the first node are the logical channels: PBCCH+PPCH+, PAGCH+PRACH+, and PDTCH+PACCH. Above the subsequent nodes are: SDCCH, SACCH, TCH, FACCH, and TrCH. The label 'RLC/MAC layer' is centered above the sequence, and 'Physical layer' is centered below the sequence. + +**Figure 3.1.e: SAP between the physical layer and the RLC/MAC layer when the MS is operating in *Iu mode* with FLO** + +## 3.2 Service of the physical layer + +The physical layer offers a transmission service on a limited set of logical channels. Additionally with FLO in *Iu mode*, the physical layer offers a transmission service on transport channels. The BS and MS access capabilities and the characteristics of logical channels (SAPs) are defined in 3GPP TS 44.003. + +**NOTE:** Between 3GPP TS 44.003 and the 3GPP TS 45.0xx series there is a slight difference in terminology. The "channels" mentioned in 3GPP TS 44.003 are "logical channels" according to the 3GPP TS 45.0xx series (especially 3GPP TS 45.002). The "CCCH", a channel name commonly used in the 3GPP TS 44.0xx series, covers the logical channels of the type RACH, PCH and AGCH. Similarly, the "PCCCH" covers the logical channels of the type PPCH, PAGCH and PRACH. + +For an MS operating in *A/Gb mode*, logical channels are multiplexed on physical channels. Physical channels are the units scheduled on the radio medium. Some are reserved by the network for common use (e.g. a combination of CCCH and BCCH), others are assigned to dedicated connections with MSs (dedicated physical channels), or are assigned to a shared usage between MSs for packet switched data traffic (packet data physical channels). In time, the combination of logical channels used on an assigned physical channel may change. Allowed combinations of logical channels on a physical channel are defined in 3GPP TS 44.003. Data on SAPs of control channels is exchanged in discrete blocks with a size of 23 or 21 (SACCH) octets. Data on a SAP of packet data traffic channels is exchanged in discrete blocks with a size dependent on the block type (see clause 7). + +For an MS operating in *Iu mode*, logical channels are multiplexed on basic physical subchannels. Basic physical subchannels are the units scheduled on the radio medium. Some basic physical channels are reserved by the network for common use (e.g. BCCH); dedicated basic physical subchannels are assigned to dedicated connections with MSs, shared basic physical subchannels are assigned to a shared usage between MSs for packet switched data traffic. In time, the combination of logical channels used on an assigned basic physical subchannel may change. Allowed combinations of logical channels on a basic physical subchannel are defined in 3GPP TS 44.003. Data on SAPs of control channels is exchanged in discrete blocks with a size of 23 or 21 (SACCH) octets. Data on a SAP of packet data traffic channels is exchanged in discrete blocks with a size dependent on the block type (see clause 7). + +For an MS operating in *Iu mode* with FLO, transport channels are multiplexed on dedicated basic physical subchannels. The combination of transport channels used on an assigned basic physical subchannel may change in time. Data on SAPs of transport channels is exchanged in discrete transport blocks. + +Synchronization between layer 1 and layer 2 (data link layer) is provided for piggy-backing of RR (receive ready) frames, and the starting of timers (T200). See also 3GPP TS 44.006. Synchronization between the physical layer and the RLC/MAC layer is provided for the handling of timers, and the multiplexing of logical channels. See also 3GPP TS 44.060 (*A/Gb mode*). + +### - Error detection: + +The physical layer offers an error protected transmission service, it includes error detection functions and to a lower level, error correction functions. Erroneous received frames are not offered to the data link layer or the RLC/MAC layer. The probability of one or more errors in a physical block transferred by the physical layer is defined in 3GPP TS 45.005. Due to not specified methods of quality detection, the probability of residual errors in transferred blocks may vary between implementations. + +### - Encryption: + +Security related functions implemented at the physical layer are described in 3GPP TS 43.020. + +An overview of the functions specified in the 45-series which create the service of the physical layer can be found in 3GPP TS 45.001. + +### 3.2.1 Specific services of the physical layer in the MS + +The access capability service of the physical layer in the MS differs depending on the nature of the channel (traffic, packet data traffic or broadcast/common channels). + +#### - **Establishment of dedicated physical channels (*A/Gb Mode*):** + +Establishment of dedicated physical channels on the physical layer is controlled by the radio resources management of layer 3 (3GPP TS 44.018). During operation on a dedicated physical channel, the physical layer measures the signals of neighbouring base stations and the signal quality of the used dedicated physical channel. Measurements are transferred to layer 3, measurement control information is offered by layer 3. + +#### - **Establishment of dedicated basic physical subchannels (*Iu mode*):** + +Establishment of dedicated basic physical subchannels on the physical layer is controlled by the radio resources management of layer 3 (3GPP TS 44.018). During operation on a dedicated basic physical subchannel, the physical layer measures the signals of neighbouring base stations and the signal quality of the used dedicated basic physical subchannel. Measurements are transferred to layer 3, measurement control information is offered by layer 3. + +#### - **Establishment of packet data physical channels (*A/Gb mode*):** + +Establishment of packet data physical channels on the physical layer is controlled by the radio resource management of layer 3. Packet access and the reservation of radio resource on packet data physical channels is controlled by the RLC/MAC layer in co-operation with layer 3 (3GPP TS 44.060). During operation on packet data physical channels, the physical layer measures the signals of neighbouring base stations and the signal quality of the used packet data physical channel. Measurements are transferred to layer 3, measurement control information is offered by layer 3. + +#### - **Establishment of shared basic physical subchannels (*Iu mode*):** + +Establishment of shared basic physical subchannels on the physical layer is controlled by the radio resource management of layer 3. Packet access and the reservation of radio resource on shared basic physical subchannels is controlled by the RLC/MAC layer in co-operation with layer 3. During operation on shared basic physical subchannels, the physical layer measures the signals of neighbouring base stations and the signal quality of the used shared basic physical subchannel. Measurements are transferred to layer 3, measurement control information is offered by layer 3. + +#### - **cell/PLMN selection in idle mode or in packet mode:** + +In idle mode or in packet mode, the physical layer selects the best cell with its BCCH/CCCH in close co-operation with layer 3, meeting requirements for PLMN selection specified in 3GPP TS 22.011. The idle mode procedures are not modelled within the present document. Examples of procedures for cell selection are described in 3GPP TS 45.008. The physical layer performs automatic crossover. + +# --- 4 Primitives of the physical layer + +The Physical layer interacts with other entities as illustrated in figure 2.1. The interactions with the data link layer of Dm channels and the interactions with the RLC/MAC layer of packet data physical channels (*A/Gb mode*), shared or dedicated basic physical subchannels (*Iu mode*) are shown in terms of primitives where the primitives represent the logical exchange of information and control between the physical layer and adjacent layers. They do not specify or constrain implementations. The interactions between the physical layer and layer 1 entities for Bm/Lm channels are for further study. For the physical layer two sets of primitives are defined: + +## - **Primitives between physical layer and data link layer and RLC/MAC layer respectively:** + +PH - Generic name - Type: Parameters. + +## - **Primitives between layer 1 and the RR-management layer 3 entity:** + +MPH - Generic name - Type: Parameters. + +## 4.1 Generic names of primitives between layers 1 and 2 for the transfer of layer 2 frames and RLC/MAC blocks + +The following primitive generic names are defined on the SAPs between the physical layer and the data link layer: + +### a) PH-DATA: + +The PH-DATA primitives are used on a SAP to pass message units containing frames used for data link layer and RLC/MAC layer respective peer-to-peer communications to and from the physical layer. + +### b) PH-RANDOM ACCESS: + +The PH-RANDOM ACCESS (PH-RA) primitives are used on the SAP of the RACH and the PRACH to request and confirm (in the MS) the sending of a random access frame and to indicate (in the network) the arrival of a random access frame. For MS operating in *A/Gb mode*, the random access protocols are specified in 3GPP TS 44.018 and 3GPP TS 44.060 respectively. + +### c) PH-CONNECT: + +The PH-CONNECT primitive is used on a SAP to indicate that the physical connection on the corresponding control channel or packet data physical channel (*A/Gb mode*) or shared basic physical subchannel (*Iu mode*) has been established. + +### d) PH-READY-TO-SEND: + +The PH-READY-TO-SEND primitive is used by the physical layer to trigger, if applicable, piggy backing, the start of timer for the data link layer or the RLC/MAC layer and the forwarding a data unit to the physical layer. It is passed to the upper layer just before a new physical block is transmitted. + +### e) PH-EMPTY-FRAME: + +The PH-EMPTY-FRAME primitive can be used by the data link layer and the RLC/MAC layer to indicate that no frame has to be transmitted after receiving the PH-READY-TO-SEND primitive. It enables polling of several upper layer entities by the physical layer and support DTX. + +## 4.2 Generic names of primitives between layer 1 and the RR-management entity of layer 3 + +The following primitive generic name is defined between layer 1 and the RR-management entity of layer 3: + +### - MPH-INFORMATION: + +MPH-INFORMATION (MPH-INFO) primitives are used for the control of the physical layer by the RR-management of layer 3. This information activates and deactivates, configures and deconfigures, through connects and disconnects physical, logical and transport channels. It is also used for the transfer of measurements and measurement control information from layer 1 to layer 3. + +## 4.3 Primitive types + +The primitive types defined in the present document are: + +### a) REQUEST: + +The REQUEST primitive type is used when a higher layer is requesting a service from a lower layer. + +### b) INDICATION: + +The INDICATION primitive type is used by a layer providing a service to notify the next higher layer of activities in the layer. This activities are directly related to the occurrence of a REQUEST primitive on the peer-protocol side. + +### c) RESPONSE: + +The RESPONSE primitive type is used by a layer to acknowledge receipt from the INDICATION primitive type. + +### d) CONFIRM: + +The CONFIRM primitive type is used by the layer providing the requested service to confirm that the activity has been completed. + +## 4.4 Parameter definition + +Primitives contain a variable amount of parameters. The primitives with included parameters are listed in table 4.1. + +**Table 4.1: Primitives of the physical layer** + +| primitive | MS/BS | entity | direction | | message unit | channel control parameters | system information | absolute frame No. | measurement | +|------------------|-------|-------------------|-------------------|---|--------------|----------------------------|--------------------|--------------------|-------------| +| | | | | | | | | | | +| | | | | | | | | | | +| | | | | | | | | | | +| | | | | | | | | | | +| MPH-INFO-REQ | MS/BS | RR(L3) | PH(L1) | | | x | x | | | +| MPH-INFO-CON | MS/BS | PH(L1) | RR(L3) | | | x | x | | | +| MPH-INFO-IND | MS/BS | PH(L1) | RR(L3) | | | x | x | | x | +| PH-CONNECT-IND | MS/BS | PH(L1) | DL(L2)
RLC/MAC | | | x | | | | +| PH-READY-TO-SEND | MS/BS | PH(L1) | DL(L2)
RLC/MAC | | | x | | x | | +| PH-EMPTY-FRAME | MS/BS | DL(L2)
RLC/MAC | PH(L1) | | | x | | | | +| PH-DATA-REQ | MS/BS | DL(L2)
RLC/MAC | PH(L1) | x | | x | | | | +| PH-DATA-IND | MS/BS | PH(L1) | DL(L2)
RLC/MAC | x | | x | | | x | +| PH-RA-REQ | MS | DL(L2)
RLC/MAC | PH(L1) | x | | | | | | +| PH-RA-IND | BS | PH(L1) | DL(L2)
RLC/MAC | x | | | | x | | +| PH-RA-CON | MS | PH(L1) | DL(L2)
RLC/MAC | x | | | | x | | + +Parameters involved in the primitive exchange with the physical layer are: + +### a) Message unit: + +The message unit contains peer-to-peer information of a layer. It is transferred by the physical layer to the peer layer. + +### b) Channel control parameters: + +These parameters contain information for channel control, specified in 3GPP TS 44.018 and 3GPP TS 44.060 for MS operating in *A/Gb mode*. + +### c) System information: + +This information is exchanged in the cell/PLMN selection procedures. It may also contain control information for DRX (sleep mode, see 3GPP TS 43.013). + +### d) Absolute Frame Number: + +The absolute frame number is used (in combination with a random access identifier) to uniquely identify a random access. + +### e) Measurements: + +This parameter is used to report the quality of a dedicated physical channel (MS and network) and to report the quality of surrounding BCCH carriers (MS only). + +# --- 5 Physical layer procedures + +## 5.0 General + +The main body of physical layer procedures is specified in 3GPP TS 44.018 and 3GPP TS 44.060 for MS operating in *A/Gb mode*, and 3GPP TS 45.008. + +## 5.1 States of the physical layer + +In the physical layer of the MS the following states are defined: + +NULL: the equipment is switched off; + +SEARCHING BCH: the physical layer tracks the best BCCH; + +BCH: the physical layer listens to a BCCH/CCCH, PBCCH/PCCCH or EC-BCCH/EC-CCCH and is able to do random access; + +TUNING DCH: For MS operating in *A/Gb mode* the physical layer seizes on a respective dedicated physical channel or packet data physical channel; for MS operating in *Iu mode* the physical layer seizes on a basic physical subchannel; + +DCH: For MS operating in *A/Gb mode* the physical layer has seized a respective dedicated physical channel or packet data physical channel and may establish and through connect logical channels; For MS operating in *Iu mode* the physical layer has seized a basic physical subchannel and may establish and through connect logical channels. + +NOTE: BCH = Bcch/ccch physical CHannel, pbcch/pcch or ec-bcch/ec-ccch physical channel; +DCH = Dedicated physical CHannel or packet data physical channel for MS operating in *A/Gb mode*; +Dedicated basic physical subCHannel or shared basic physical subchannel for MS operating in *Iu mode*. + +Figure 5.1 gives a general state diagram of the physical layer. All state transitions of the physical layer are controlled by MPH-INFORMATION primitives. + +![State transition diagram for physical layer states in the MS, showing transitions between NULL, BCH, SEARCHING BCH, TUNING DCH, and DCH states.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +stateDiagram-v2 + direction TB + + state "Idle mode, packet idle mode, MAC-Idle State" as Idle + state "dedicated mode, packet transfer mode, dual transfer mode, MAC-Shared state, MAC-DTM state, MAC-Dedicated state" as Dedicated + + state Idle { + NULL + BCH + SEARCHING_BCH: SEARCHING BCH + } + + state Dedicated { + TUNING_DCH: TUNING DCH + DCH + } + + NULL --> SEARCHING_BCH + SEARCHING_BCH --> NULL + SEARCHING_BCH --> BCH + BCH --> SEARCHING_BCH + BCH --> NULL + + %% Transitions across modes + BCH --> TUNING_DCH + SEARCHING_BCH --> DCH + TUNING_DCH --> SEARCHING_BCH + DCH --> SEARCHING_BCH + + TUNING_DCH --> DCH + DCH --> TUNING_DCH + TUNING_DCH --> NULL + DCH --> NULL + + %% Self loops/Return paths + DCH --> DCH + NULL --> NULL + +``` + +The diagram illustrates the state transitions for the physical layer in the MS. A horizontal dashed line separates the states into two main operational modes. + +**Upper Section (Idle Mode):** Contains states **NULL**, **BCH**, and **SEARCHING BCH**. This section is labeled: "Idle mode, packet idle mode, MAC-Idle State". + +**Lower Section (Dedicated Mode):** Contains states **TUNING DCH** and **DCH**. This section is labeled: "dedicated mode, packet transfer mode, dual transfer mode, MAC-Shared state, MAC-DTM state, MAC-Dedicated state". + +**Key Transitions:** Arrows indicate bidirectional and unidirectional paths between all states, including transitions that cross the boundary between Idle and Dedicated modes (e.g., BCH to TUNING DCH, SEARCHING BCH to DCH, and returns to NULL or SEARCHING BCH). + +State transition diagram for physical layer states in the MS, showing transitions between NULL, BCH, SEARCHING BCH, TUNING DCH, and DCH states. + +**Figure 5.1: States of the physical layer in the MS** + +The states of the physical layer in the network are not specified. The states in the network will reflect the other characteristics of operation on channels. + +## 5.2 Control procedures + +Requirements and examples of procedures for idle mode and for packet mode operation of the MS are specified in 3GPP TS 22.011 and 45.008. In the idle mode and packet mode procedures the physical layer tracks the best cell and may tune on their BCCH/PBCCH/EC-BCCH in order to enable layer 3 to read the system information of the BCCH/PBCCH/EC-BCCH. This system information of the BCCH/PBCCH/EC-BCCH is used in the selection process. + +## 5.3 Physical layer interface procedures + +Three types of primitives are defined for the communication between the physical layer and the data link layer both in the MS and the network. When a control channel, packet data physical channel (*A/Gb mode*), or a shared basic physical subchannel (*Iu mode*) is being established, a PH-CONNECT-INDICATION is offered to the data link layer or the RLC/MAC layer, the one which is applicable, on the corresponding SAP. On an established full duplex control channel (DCCHs) in both MS and network, on an established packet data physical channel (*A/Gb mode*), or a shared basic physical subchannel (*Iu mode*) or on the established BCCH/CCCH in the MS, physical blocks received correctly are offered on the corresponding SAP in PH-DATA-INDICATION primitives. On a full duplex control channel (DCCHs) or on the BCCH/CCCH in the network, the data link layer will offer physical blocks to be transmitted in PH-DATA-REQUEST primitives. On a packet data physical channel (*A/Gb mode*) or shared basic physical subchannel (*Iu mode*), the RLC/MAC layer will offer physical blocks to be transmitted in PH-DATA-REQUEST primitives. + +In the MS in idle mode or in packet idle mode, random accesses on RACH, on PRACH or on EC-RACH can be offered in PH-RANDOM ACCESS-REQUEST primitives. The physical layer of the MS will perform a random access as soon as possible. The physical layer of the MS will confirm the data link layer or the RLC/MAC layer, the one which is applicable, the transmission of the random access attempt in a PH-RANDOM ACCESS-CONFIRM. This confirmation contains the absolute frame number in which the random access is transmitted. The physical layer of the BS offers correctly received random accesses to the data link layer or the RLC/MAC layer, the one which is applicable, in a PH-RANDOM ACCESS-INDICATION. This indication contains the absolute frame number in which the random access is received. + +# --- 6 Physical layer protocol header + +## 6.0 General + +The physical layer implements a peer-to-peer protocol for the control of timing advance, power control and Repeated SACCH at the operation on dedicated physical channels (*A/Gb mode*) or dedicated basic physical subchannels (*Iu mode*), and further, for the control of timing advance at the operation on packet data physical channels (*A/Gb mode*) or shared basic physical subchannels (*Iu mode*). For this purpose a two octet physical header is defined on all blocks transferred via the SACCH, a logical channel always present on a dedicated physical channel (*A/Gb mode*) or dedicated basic physical subchannel (*Iu mode*). Further more, a 16 octet information field is defined on downlink blocks transferred via the PTCCH, a logical channel present on a packet data physical channel (*A/Gb mode*) or shared basic physical subchannel (*Iu mode*). + +## 6.1 Physical layer protocol fields and procedures + +Procedures for handling the ordered and actual power level fields are specified in 3GPP TS 45.005 and 45.008. The ordered MS power level field and the actual MS power level field are coded as the binary representation of the "power control level", see 3GPP TS 45.005. + +Procedures for handling the ordered and actual timing advance fields are specified in 3GPP TS 45.010. The numbers corresponding to the timing advance steps in 3GPP TS 45.010 are included binary coded in the 7 bit or in case of GSM 400 8 bit ordered and actual timing advance fields of the physical layer header. + +For all the bands except GSM 400, the values 0 to 63 are valid TA values. The bit pattern "1111111" indicates that the field does not contain a timing advance value. All other bit combinations (64 to 126 decimal) are reserved. For all bands except GSM 400 bit 8 is set to spare. + +For GSM 400, the values 0 to 219 decimal are valid TA values. The bit pattern "11111111" indicates that the field does not contain a timing advance value. The remaining values 220 to 254 are reserved. + +A MS in packet transfer mode (*A/Gb mode*) or MAC-shared state (*Iu mode*) which is assigned a TAI shall, when receiving a PTCCH downlink block on the packet data physical channel (*A/Gb mode*) or shared basic physical + +subchannel (*Iu mode*) containing PACCH, read the corresponding ordered timing advance field in that PTCCH block. The ordered timing advance fields corresponding to other TAI's than the assigned one shall be ignored. + +Procedures for handling the FPC\_EPC (Fast Power Control/Enhanced Power Control) field (bit 6 of octet 1 in the SACCH downlink block) are specified in 3GPP TS 45.008 and 3GPP TS 48.058. The FPC\_EPC field has different interpretation depending on the channel mode of the channel to which the SACCH is associated, and whether that channel is in EPC mode.. + +If the channel mode is such that FPC may be used, the FPC\_EPC field indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: + +Value: + +- 0 Fast Power Control not in use, +- 1 Fast Power Control in use. + +If the channel is in EPC mode, the FPC\_EPC field indicates whether EPC procedures are used for MS (uplink) power control. It is coded as follows: + +Value: + +- 0 EPC not in use for MS power control, +- 1 EPC in use for MS power control. + +If the channel mode is such that FPC may not be used and the channel is not in EPC mode, the MS shall ignore the value of the FPC\_EPC field. + +Procedures for handling the SRO (SACCH Repetition Order) and the SRR (SACCH Repetition Request) fields are specified in 3GPP TS 44.006. They are coded as follows: + +Value: + +- 0 Repeated SACCH not required +- 1 Repeated SACCH required + +# 7 Block transmission + +## 7.0 General + +The format of the blocks transmitted on the physical interface depends on the mode (*A/Gb* or *Iu mode*) in which the MS is connected to the network, as specified in this section. + +## 7.1 SACCH downlink block format + +### 7.1.1 *A/Gb mode* + +The 23 octets of SACCH blocks are used in the downlink in the following way: + +![](7d0416676d34c96ca27ecc0d38239fea_img.jpg) + +| | | | | | | | | | | | +|------------------------|-----|---------|------------------------|---|---|---|---|---------|---------|--------------------| +| bit numbering | | | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| Spare | SRO | FPC EPC | Ordered MS power level | | | | | | octet 1 | octet
numbering | +| Ordered timing advance | | | | | | | | octet 2 | | | +| 21
octets | | | | | | | | octet 3 | | | + +![Diagram of SACCH downlink block format for MS operating in A/Gb mode. It shows a 'layer 2 frame' with 'octet 23' indicated on the right side.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram shows a rectangular block representing a 'layer 2 frame'. The text 'layer 2' is on the first line, and 'frame' is on the second line, both centered. To the right of the block, 'octet 23' is written. Above the block, there are three vertical dotted lines on the left and right sides. + +Diagram of SACCH downlink block format for MS operating in A/Gb mode. It shows a 'layer 2 frame' with 'octet 23' indicated on the right side. + +NOTE: The numbering convention specified in 3GPP TS 44.006 applies. + +Figure 7.1.1: SACCH downlink block format for MS operating in A/Gb mode + +### 7.1.2 Iu mode + +The 23 octets of SACCH blocks are used in the downlink in the following way: + +![Diagram of SACCH downlink block format for MS operating in Iu mode. It shows a table with 8 columns (bit numbering 8 to 1) and 23 rows (octet numbering 1 to 23). The first row contains Spare, SRO, FPC EPC, and Ordered MS power level. Subsequent rows contain Ordered timing advance, 21 Octets, and RLC/MAC Block.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +The diagram is a table with 8 columns and 23 rows. Above the columns is a header 'bit numbering' with a dashed line and arrows pointing left and right. Below this header are the numbers 8, 7, 6, 5, 4, 3, 2, 1. The first row of the table contains four cells: 'Spare', 'SRO', 'FPC EPC', and 'Ordered MS power level'. The second row contains a single cell 'Ordered timing advance'. The third row contains a single cell '21 Octets'. The fourth row contains a single cell 'RLC/MAC Block'. To the right of the table, the rows are labeled 'octet 1', 'octet 2', 'octet 3', and 'octet 23'. Between 'octet 3' and 'octet 23', there are three vertical dotted lines. To the far right, there is a vertical label 'octet numbering' with a 'V' shape next to it. + +Diagram of SACCH downlink block format for MS operating in Iu mode. It shows a table with 8 columns (bit numbering 8 to 1) and 23 rows (octet numbering 1 to 23). The first row contains Spare, SRO, FPC EPC, and Ordered MS power level. Subsequent rows contain Ordered timing advance, 21 Octets, and RLC/MAC Block. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.1.2: SACCH downlink block format for MS operating in Iu mode + +## 7.2 SACCH uplink block format + +### 7.2.1 A/Gb mode + +The 23 octets of SACCH blocks are used in the uplink in the following way: + +![Diagram of SACCH uplink block format for MS operating in A/Gb mode. It shows a table with 8 columns (bit numbering 8 to 1) and 23 rows (octet numbering 1 to 23). Columns 8, 7, and 6 are Spare, SRR, and FPC respectively. Columns 5-1 are grouped as 'Actual MS power level' in octet 1, 'Actual timing advance' in octet 2, and '21 octets' in octet 3. Rows 4-22 are part of a 'layer 2 frame'. Octet 23 is the end of the frame.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +| bit numbering | | | | | | | | | | +|-----------------------|-----|-----|-----------------------|---|---|---|---|----------|--------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| Spare | SRR | FPC | Actual MS power level | | | | | octet 1 | octet
numbering | +| Actual timing advance | | | | | | | | octet 2 | | +| 21 octets | | | | | | | | octet 3 | | +| layer 2 frame | | | | | | | | ⋮ | V | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| ⋮ | | | | | | | | | | +| layer 2 frame | | | | | | | | octet 23 | | + +Diagram of SACCH uplink block format for MS operating in A/Gb mode. It shows a table with 8 columns (bit numbering 8 to 1) and 23 rows (octet numbering 1 to 23). Columns 8, 7, and 6 are Spare, SRR, and FPC respectively. Columns 5-1 are grouped as 'Actual MS power level' in octet 1, 'Actual timing advance' in octet 2, and '21 octets' in octet 3. Rows 4-22 are part of a 'layer 2 frame'. Octet 23 is the end of the frame. + +NOTE: The numbering convention specified in 3GPP TS 44.006 applies. + +Figure 7.2.1: SACCH uplink block format for MS operating in A/Gb mode + +### 7.2.2 Iu mode + +The 23 octets of SACCH blocks are used in the uplink in the following way: + +![Diagram of SACCH uplink block format for MS operating in Iu mode. It shows a table with 8 columns (bit numbering 8 to 1) and 23 rows (octet numbering 1 to 23). Columns 8, 7, and 6 are Spare, SRR, and FPC respectively. Columns 5-1 are grouped as 'Actual MS power level' in octet 1, 'Actual timing advance' in octet 2, and '21 octets' in octet 3. Rows 4-22 contain an 'RLC/MAC Block'. Octet 23 is the end of the block.](5fbb4f0de01736f1293333e599410c99_img.jpg) + +| bit numbering | | | | | | | | | | +|-----------------------|-----|-----|-----------------------|---|---|---|---|----------|--------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| Spare | SRR | FPC | Actual MS power level | | | | | octet 1 | octet
numbering | +| Actual timing advance | | | | | | | | octet 2 | | +| 21 octets | | | | | | | | octet 3 | | +| RLC/MAC Block | | | | | | | | ⋮ | V | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| | | | | | | | | ⋮ | | +| ⋮ | | | | | | | | | | +| RLC/MAC Block | | | | | | | | octet 23 | | + +Diagram of SACCH uplink block format for MS operating in Iu mode. It shows a table with 8 columns (bit numbering 8 to 1) and 23 rows (octet numbering 1 to 23). Columns 8, 7, and 6 are Spare, SRR, and FPC respectively. Columns 5-1 are grouped as 'Actual MS power level' in octet 1, 'Actual timing advance' in octet 2, and '21 octets' in octet 3. Rows 4-22 contain an 'RLC/MAC Block'. Octet 23 is the end of the block. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.2.2: SACCH uplink block format for MS operating in Iu mode + +## 7.3 FACCH/SDCCH/CCCH/BCCH/CBCH downlink block format + +### 7.3.1 CCCH/BCCH/CBCH downlink block format + +The 23 octets blocks are used in the downlink in the following way: + +![Bit numbering diagram for downlink blocks, showing bits 8 through 1 in descending order from left to right.](c42e926097d01653b793c04b49e764b2_img.jpg) + +←----- + +8       7       6       5       4       3       2       1 + +Bit numbering diagram for downlink blocks, showing bits 8 through 1 in descending order from left to right. + +![Diagram of BCCH/CCCH/CBCH downlink block format showing a 23 octet layer 2 frame with octet 1 at the top and octet 23 at the bottom.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram shows a rectangular block representing a downlink block. Inside the block, the text "23 octets" is centered in the upper half, and "layer 2 frame" is centered in the lower half. To the right of the block, "octet 1" is aligned with the top edge and "octet 23" is aligned with the bottom edge. Vertical ellipsis dots are placed on both the left and right sides of the block, indicating the continuation of the 23 octets. + +Diagram of BCCH/CCCH/CBCH downlink block format showing a 23 octet layer 2 frame with octet 1 at the top and octet 23 at the bottom. + +NOTE: The numbering convention specified in 3GPP TS 44.006 and 44.012 applies. + +Figure 7.3.1: BCCH/CCCH/CBCH downlink block format + +### 7.3.2 FACCH/SDCCH downlink block format + +#### 7.3.2.1 A/Gb mode + +The 23 octets blocks are used in the downlink in the following way: + +![Diagram of FACCH/SDCCH downlink block format for MS operating in A/Gb mode, showing 23 octets and a layer 2 frame with octet numbering 1 to 8 above.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +This diagram shows a rectangular block with a dashed line above it. Above the dashed line, the numbers 8, 7, 6, 5, 4, 3, 2, and 1 are placed from left to right, with a left-pointing arrow above the number 8. The rectangular block contains "23 Octets" in the upper half and "layer 2 Frame" in the lower half. To the right, "octet 1" is at the top and "octet 23" is at the bottom. Vertical ellipsis dots are on the left and right sides. + +Diagram of FACCH/SDCCH downlink block format for MS operating in A/Gb mode, showing 23 octets and a layer 2 frame with octet numbering 1 to 8 above. + +NOTE: The numbering convention specified in 3GPP TS 44.006 and 3GPP TS 44.012 applies. + +Figure 7.3.2.1: FACCH/SDCCH downlink block format for MS operating in A/Gb mode + +#### 7.3.2.2 Iu mode + +The 23 octets blocks are used in the downlink in the following way: + +![Diagram of FACCH/SDCCH downlink block format for MS operating in Iu mode, showing 23 octets and an RLC/MAC block with octet numbering 1 to 8 above.](db7cb51aac8519daab50e2171cecae82_img.jpg) + +This diagram shows a rectangular block with a dashed line above it. Above the dashed line, the numbers 8, 7, 6, 5, 4, 3, 2, and 1 are placed from left to right, with a left-pointing arrow above the number 8. The rectangular block contains "23 Octets" in the upper half and "RLC/MAC block" in the lower half. To the right, "octet 1" is at the top and "octet 23" is at the bottom. Vertical ellipsis dots are on the left and right sides. + +Diagram of FACCH/SDCCH downlink block format for MS operating in Iu mode, showing 23 octets and an RLC/MAC block with octet numbering 1 to 8 above. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.3.2.2: FACCH/SDCCH downlink block format for MS operating in Iu mode + +## 7.4 FACCH/SDCCH uplink block format + +### 7.4.1 A/Gb mode + +The 23 octets blocks are used in the uplink in the following way: + +![Diagram of FACCH/SDCCH uplink block format for MS operating in A/Gb mode. It shows a block of 23 octets, labeled 'octet 1' at the top and 'octet 23' at the bottom. The block is divided into 8 numbered segments (1-8) at the top. The content is labeled '23 octets' and 'layer 2 frame'.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +The diagram shows a rectangular block representing 23 octets. Above the block, a dashed line with a left-pointing arrow spans across, with numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. The block itself is divided into three horizontal sections by solid lines. The top section contains the text '23 octets'. The middle section contains the text 'layer 2 frame'. The right side of the block has labels 'octet 1' at the top and 'octet 23' at the bottom, with vertical ellipsis dots between them indicating the continuation of the 23 octets. + +Diagram of FACCH/SDCCH uplink block format for MS operating in A/Gb mode. It shows a block of 23 octets, labeled 'octet 1' at the top and 'octet 23' at the bottom. The block is divided into 8 numbered segments (1-8) at the top. The content is labeled '23 octets' and 'layer 2 frame'. + +NOTE: The numbering convention specified in 3GPP TS 44.006 applies. + +Figure 7.4.1: FACCH/SDCCH uplink block format for MS operating in A/Gb mode + +### 7.4.2 Iu mode + +The 23 octets blocks are used in the uplink in the following way: + +![Diagram of FACCH/SDCCH uplink block format for MS operating in Iu mode. It shows a block of 23 octets, labeled 'octet 1' at the top and 'octet 23' at the bottom. The block is divided into 8 numbered segments (1-8) at the top. The content is labeled '23 octets' and 'RLC/MAC block'.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +This diagram is similar to the previous one but represents the Iu mode. It shows a rectangular block for 23 octets. Above it, a dashed line with a left-pointing arrow spans across, with numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. The block is divided into three horizontal sections. The top section contains '23 octets'. The middle section contains 'RLC/MAC block'. The right side has 'octet 1' at the top and 'octet 23' at the bottom, with vertical ellipsis dots between them. + +Diagram of FACCH/SDCCH uplink block format for MS operating in Iu mode. It shows a block of 23 octets, labeled 'octet 1' at the top and 'octet 23' at the bottom. The block is divided into 8 numbered segments (1-8) at the top. The content is labeled '23 octets' and 'RLC/MAC block'. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.4.2: FACCH/SDCCH uplink block format for MS operating in Iu mode + +## 7.4a RACH uplink / Uplink access burst block format + +Two alternative RACH uplink / Uplink access burst block formats are specified. The 8 bit (1 octet) blocks are used in the uplink in the following way: + +![Diagram of 8 bit RACH uplink / Uplink access burst block format. It shows a block labeled '8 bit RACH uplink / Uplink access burst block' with 8 numbered segments (1-8) at the top. The label 'octet 1' is on the right.](836008eb3303ade9e269f93c04dc0a2e_img.jpg) + +The diagram shows a single horizontal rectangular block. Above it, a dashed line with a left-pointing arrow spans across, with numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. Inside the block, the text '8 bit RACH uplink / Uplink access burst block' is centered. To the right of the block, the label 'octet 1' is present. + +Diagram of 8 bit RACH uplink / Uplink access burst block format. It shows a block labeled '8 bit RACH uplink / Uplink access burst block' with 8 numbered segments (1-8) at the top. The label 'octet 1' is on the right. + +NOTE: The numbering convention specified in 3GPP TS 44.018 applies. + +Figure 7.4a.a: 8 bit RACH uplink / Uplink access burst block format + +The 11 bit blocks are used in the uplink in the following way: + +![Diagram of 11 bit RACH uplink / Uplink access burst block format. It shows a block labeled '11 bit RACH uplink / Uplink access burst block' with 8 numbered segments (1-8) at the top. The label 'octet 1' is on the right.](0a884282620b74ce60c04ab3400c4208_img.jpg) + +This diagram shows a single horizontal rectangular block. Above it, a dashed line with a left-pointing arrow spans across, with numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. Inside the block, the text '11 bit RACH uplink / Uplink access burst block' is centered. To the right of the block, the label 'octet 1' is present. + +Diagram of 11 bit RACH uplink / Uplink access burst block format. It shows a block labeled '11 bit RACH uplink / Uplink access burst block' with 8 numbered segments (1-8) at the top. The label 'octet 1' is on the right. + +![Diagram of 11 bit RACH uplink / Uplink access burst block format. It shows a rectangular block divided into two horizontal sections. The top section is wider and the bottom section is narrower, aligned to the right. To the right of the block, the label 'octet 2' is present.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Diagram of 11 bit RACH uplink / Uplink access burst block format. It shows a rectangular block divided into two horizontal sections. The top section is wider and the bottom section is narrower, aligned to the right. To the right of the block, the label 'octet 2' is present. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.4a.b: 11 bit RACH uplink / Uplink access burst block format + +## 7.5 PBCCH/PCCCH downlink/PACCH block format + +The 184 bit (23 octets) blocks, or 187 bit blocks in case an eTFI is included in a downlink PACCH block, are used in the following way: + +![Diagram of PBCCH/PCCCH downlink/PACCH block format. At the top, a dashed line with a left-pointing arrow spans over numbers 8, 7, 6, 5, 4, 3, 2, 1. Below this is a large rectangle. The top part of the rectangle is labeled '184 Or 187 bit' and 'octet 1'. The bottom part is labeled 'RLC/MAC block' and 'octet 23'. Below the rectangle, 'octet 24' is indicated. Vertical ellipsis dots are on the left and right sides of the main rectangle.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +Diagram of PBCCH/PCCCH downlink/PACCH block format. At the top, a dashed line with a left-pointing arrow spans over numbers 8, 7, 6, 5, 4, 3, 2, 1. Below this is a large rectangle. The top part of the rectangle is labeled '184 Or 187 bit' and 'octet 1'. The bottom part is labeled 'RLC/MAC block' and 'octet 23'. Below the rectangle, 'octet 24' is indicated. Vertical ellipsis dots are on the left and right sides of the main rectangle. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.5: PBCCH/PCCCH downlink/PACCH blockformat + +Messages transmitted on the downlink PACCH may use an alternative block format. This format applies to RTTI configuration, for messages encoded using MCS-0 (see 3GPP TS 44.060). In this case, the 207 bit blocks, or 210 bit blocks in case an eTFI is included in a downlink PACCH block, are used in the downlink in the following way: + +![Diagram of PACCH downlink block format for MCS-0. Similar to Figure 7.5, it has a dashed line with a left-pointing arrow over numbers 8, 7, 6, 5, 4, 3, 2, 1. The main rectangle is labeled '207 or 210 bit' and 'octet 1' at the top. The bottom part is labeled 'RLC/MAC block' and 'octet 26'. Below that, 'octet 27' is indicated. Vertical ellipsis dots are on the left and right sides of the main rectangle.](14515d82ffeec9475b9add3036ff26ab_img.jpg) + +Diagram of PACCH downlink block format for MCS-0. Similar to Figure 7.5, it has a dashed line with a left-pointing arrow over numbers 8, 7, 6, 5, 4, 3, 2, 1. The main rectangle is labeled '207 or 210 bit' and 'octet 1' at the top. The bottom part is labeled 'RLC/MAC block' and 'octet 26'. Below that, 'octet 27' is indicated. Vertical ellipsis dots are on the left and right sides of the main rectangle. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.5a: PACCH downlink block format for MCS-0 + +EGPRS Packet Downlink Ack/Nack DLMC messages transmitted on the uplink PACCH may use CS-3 as an alternative block format when commanded by the network for a DLMC configuration (see 3GPP TS 44.060). In this case, the 315 bit blocks are used in the uplink in following way: + +![Diagram of PACCH uplink block format for CS-3. It shows a block structure with 315 bits, divided into octets. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 39. The bottom section is labeled 'octet 40'.](e354b57563dae469c00b412b2abdf765_img.jpg) + +The diagram illustrates the PACCH uplink block format for CS-3. It consists of a 315-bit block. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 39. The bottom section is labeled 'octet 40'. + +Diagram of PACCH uplink block format for CS-3. It shows a block structure with 315 bits, divided into octets. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 39. The bottom section is labeled 'octet 40'. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.5b: PACCH uplink block format for CS-3 + +## 7.6 PDTCH block formats + +Unless explicitly stated otherwise, the block formats shown hereafter are valid for both uplink and downlink directions. + +### 7.6.1 PDTCH block type 1 (CS-1) format + +The 184 bit (23 octets) blocks are used in the following way: + +![Diagram of PDTCH block type 1 (CS-1) format. It shows a block structure with 184 bits, divided into octets. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 23.](303fadfb9def251d1575d6221199b158_img.jpg) + +The diagram illustrates the PDTCH block type 1 (CS-1) format. It consists of a 184-bit block. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 23. + +Diagram of PDTCH block type 1 (CS-1) format. It shows a block structure with 184 bits, divided into octets. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 23. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.1: PDTCH block type 1 (CS-1) format + +### 7.6.2 PDTCH block type 2 (CS-2) format + +The 271 bit blocks are used in the following way: + +![Diagram of PDTCH block type 2 (CS-2) format. It shows a block structure with 271 bits, divided into octets. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 34.](ced309874aec0546651b0976d5030a42_img.jpg) + +The diagram illustrates the PDTCH block type 2 (CS-2) format. It consists of a 271-bit block. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 34. + +Diagram of PDTCH block type 2 (CS-2) format. It shows a block structure with 271 bits, divided into octets. The top octet is labeled 'octet 1' and contains bits 8 through 1. The middle section is labeled 'RLC/MAC block' and spans from octet 1 to octet 34. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.2: PDTCH block type 2 (CS-2) format + +### 7.6.3 PDTCH block type 3 (CS-3) format + +The 315 bit blocks are used in the following way: + +![Diagram of PDTCH block type 3 (CS-3) format showing a 315-bit block structure across octets 1 to 40. The block is divided into RLC/MAC blocks. Bit numbering 1-8 is shown at the top with a right-pointing arrow.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 3 (CS-3) format. It shows a 315-bit block divided into RLC/MAC blocks. The block is organized into octets, with octet 1 at the top and octet 40 at the bottom. The RLC/MAC block is shown in the middle, spanning multiple octets. Bit numbering 1 through 8 is indicated at the top, with a right-pointing arrow above the numbers. + +Diagram of PDTCH block type 3 (CS-3) format showing a 315-bit block structure across octets 1 to 40. The block is divided into RLC/MAC blocks. Bit numbering 1-8 is shown at the top with a right-pointing arrow. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.3: PDTCH block type 3 (CS-3) format + +### 7.6.4 PDTCH block type 4 (CS-4) format + +The 431 bit blocks are used in the following way: + +![Diagram of PDTCH block type 4 (CS-4) format showing a 431-bit block structure across octets 1 to 54. The block is divided into RLC/MAC blocks. Bit numbering 1-8 is shown at the top with a right-pointing arrow.](e05c1a13b44ab41505609d82b00cf4df_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 4 (CS-4) format. It shows a 431-bit block divided into RLC/MAC blocks. The block is organized into octets, with octet 1 at the top and octet 54 at the bottom. The RLC/MAC block is shown in the middle, spanning multiple octets. Bit numbering 1 through 8 is indicated at the top, with a right-pointing arrow above the numbers. + +Diagram of PDTCH block type 4 (CS-4) format showing a 431-bit block structure across octets 1 to 54. The block is divided into RLC/MAC blocks. Bit numbering 1-8 is shown at the top with a right-pointing arrow. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.4: PDTCH block type 4 (CS-4) format + +### 7.6.5 PDTCH block type 5 (MCS-1) format + +The 209 bit blocks, or in case an eTFI is included in a downlink block, 212 bit blocks, or in case a PAN is included, 234 bit blocks, or in case both a PAN and an eTFI are included, 237 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 5 (MCS-1) format showing a 209 or 212 or 234 or 237 bit block structure across octet 1. Bit numbering 1-8 is shown at the top with a right-pointing arrow.](298e7e2164a95d0d5bb8e5d1f7155094_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 5 (MCS-1) format. It shows a block containing 209 or 212 or 234 or 237 bits, organized into octets, with octet 1 at the top. Bit numbering 1 through 8 is indicated at the top, with a right-pointing arrow above the numbers. + +Diagram of PDTCH block type 5 (MCS-1) format showing a 209 or 212 or 234 or 237 bit block structure across octet 1. Bit numbering 1-8 is shown at the top with a right-pointing arrow. + +![Diagram of PDTCH block type 5 (MCS-1) format showing RLC/MAC Block and octet numbering from 27 to 30.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 5 (MCS-1). It shows a large rectangular block labeled "RLC/MAC Block". Above this block, there are three vertical dots. To the right of the block, the label "octet 27" is positioned near the top right corner, and "octet 30" is positioned near the bottom right corner. A dashed line with a left-pointing arrow is shown above the block, spanning its width. + +Diagram of PDTCH block type 5 (MCS-1) format showing RLC/MAC Block and octet numbering from 27 to 30. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.5: PDTCH block type 5 (MCS-1) format + +### 7.6.6 PDTCH block type 6 (MCS-2) format + +The 257 bit blocks, or in case an eTFI is included in a downlink block, 260 bit blocks, or in case a PAN is included, 282 bit blocks, or in case both a PAN and an eTFI are included, 285 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 6 (MCS-2) format showing bit numbering 1-8, RLC/MAC Block, and octet numbering 1, 33, 36.](356eb99ab9489bbd647223390a913903_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 6 (MCS-2). At the top, there is a dashed line with a left-pointing arrow, above which are the numbers 8, 7, 6, 5, 4, 3, 2, 1. Below this, a large rectangular block contains the text "257 or 260 or 282 or 285 Bit". Below this block is another rectangular block labeled "RLC/MAC Block". To the right of the main block, the label "octet 1" is at the top, "octet 33" is near the bottom of the RLC/MAC block, and "octet 36" is at the bottom right corner. Vertical dots are shown on the left and right sides of the main block. + +Diagram of PDTCH block type 6 (MCS-2) format showing bit numbering 1-8, RLC/MAC Block, and octet numbering 1, 33, 36. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.6: PDTCH block type 6 (MCS-2) format + +### 7.6.7 PDTCH block type 7 (MCS-3) format + +The 329 bit blocks, or in case an eTFI is included in a downlink block, 332 bit blocks or in case a PAN is included, 354 bit blocks, or in case both a PAN and an eTFI are included, 357 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 7 (MCS-3) format showing bit numbering 1-8, RLC/MAC Block, and octet numbering 1, 42.](803776dff64331076ffc951fc95358ee_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 7 (MCS-3). At the top, there is a dashed line with a left-pointing arrow, above which are the numbers 8, 7, 6, 5, 4, 3, 2, 1. Below this, a large rectangular block contains the text "329 or 332 or 354 or 357 Bit". Below this block is another rectangular block labeled "RLC/MAC Block". To the right of the main block, the label "octet 1" is at the top, and "octet 42" is at the bottom right corner. Vertical dots are shown on the left and right sides of the main block. + +Diagram of PDTCH block type 7 (MCS-3) format showing bit numbering 1-8, RLC/MAC Block, and octet numbering 1, 42. + +![Diagram of PDTCH block type 7 (MCS-3) format showing octet 45.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram shows a single horizontal bar representing octet 45. It is divided into two parts: a larger left part and a smaller right part. Above the bar, there is a dashed line with a left-pointing arrow. To the right of the bar, the text 'octet 45' is displayed. + +Diagram of PDTCH block type 7 (MCS-3) format showing octet 45. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.7: PDTCH block type 7 (MCS-3) format + +### 7.6.8 PDTCH block type 8 (MCS-4) format + +The 385 bit blocks , or in case an eTFI is included in a downlink block, 388 bit blocks are used in the following way: + +![Diagram of PDTCH block type 8 (MCS-4) format showing 385 or 388 bits across octets 1 to 49.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +The diagram shows a large rectangular block divided into two main horizontal sections. Above the block, there is a dashed line with a left-pointing arrow, and below it, a solid line. The top section is labeled '385 or 388 Bit' and the bottom section is labeled 'RLC/MAC Block'. Above the block, there are numbers 8, 7, 6, 5, 4, 3, 2, 1. To the right of the block, the text 'octet 1' is at the top and 'octet 49' is at the bottom. + +Diagram of PDTCH block type 8 (MCS-4) format showing 385 or 388 bits across octets 1 to 49. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.8: PDTCH block type 8 (MCS-4) format + +### 7.6.9 PDTCH block type 9 (MCS-5) format + +#### 7.6.9.1 Uplink + +The 487 bit blocks, or in case a PAN is included, 512 bit blocks, or in case both a PAN and an eTFI are included, 515 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 9 (MCS-5) uplink format showing 487 or 512 or 515 bits across octets 1 to 65.](9a159e2112eac7be06bdb97e84a0c49a_img.jpg) + +The diagram shows a large rectangular block divided into two main horizontal sections. Above the block, there is a dashed line with a left-pointing arrow, and below it, a solid line. The top section is labeled '487 or 512 or 515 Bit' and the bottom section is labeled 'RLC/MAC Block'. Above the block, there are numbers 8, 7, 6, 5, 4, 3, 2, 1. To the right of the block, the text 'octet 1' is at the top, 'octet 61' is in the middle, and 'octet 64' and 'octet 65' are at the bottom. + +Diagram of PDTCH block type 9 (MCS-5) uplink format showing 487 or 512 or 515 bits across octets 1 to 65. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.9.1: PDTCH block type 9 (MCS-5) uplink format + +#### 7.6.9.2 Downlink + +The 478 bit blocks, or in case an eTFI is included, 481 bit blocks, or in case a PAN is included, 503 bit blocks, or in case both a PAN and an eTFI are included, 506 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 9 (MCS-5) downlink format showing bit numbering 1-8 and octet labels 1, 60, 63, 64.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +The diagram illustrates the downlink format for PDTCH block type 9 (MCS-5). It shows a rectangular block representing the data. Above the block, a dashed line with an arrow pointing left spans across, with numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. Inside the main rectangle, the text "478 or 481 or 503 or 506 Bit" is centered. Below this, the text "RLC/MAC Block" is also centered. To the right of the rectangle, the label "octet 1" is at the top, "octet 60" is aligned with a horizontal line inside the block, and "octet 63" and "octet 64" are at the bottom right corner. + +Diagram of PDTCH block type 9 (MCS-5) downlink format showing bit numbering 1-8 and octet labels 1, 60, 63, 64. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.9.2: PDTCH block type 9 (MCS-5) downlink format + +### 7.6.10 PDTCH block type 10 (MCS-6) format + +#### 7.6.10.1 Uplink + +The 631 bit blocks, or in case a PAN is included, 656 bit blocks, or in case both a PAN and an eTFI are included, 659 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 10 (MCS-6) uplink format showing bit numbering 1-8 and octet labels 1, 79, 82, 83.](1c29dadab94c3fa552d270434db09c81_img.jpg) + +The diagram illustrates the uplink format for PDTCH block type 10 (MCS-6). It shows a rectangular block representing the data. Above the block, a dashed line with an arrow pointing left spans across, with numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. Inside the main rectangle, the text "631 or 656 or 659 Bit" is centered. Below this, the text "RLC/MAC Block" is also centered. To the right of the rectangle, the label "octet 1" is at the top, "octet 79" is aligned with a horizontal line inside the block, and "octet 82" and "octet 83" are at the bottom right corner. + +Diagram of PDTCH block type 10 (MCS-6) uplink format showing bit numbering 1-8 and octet labels 1, 79, 82, 83. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.10.1: PDTCH block type 10 (MCS-6) uplink format + +#### 7.6.10.2 Downlink + +The 622 bit blocks, or in case an eTFI is included, 625 bit blocks, or in case a PAN is included, 647 bit blocks, or in case both a PAN and an eTFI are included, 650 bit blocks, are used in the following way: + +![Partial diagram of PDTCH block type 10 (MCS-6) downlink format showing bit numbering 1-8 and octet label 1.](6a5c8326029e6290e69a5f43d6ed4548_img.jpg) + +This diagram is a partial view of the downlink format for PDTCH block type 10 (MCS-6). It shows the top portion of a rectangular block. Above the block, a dashed line with an arrow pointing left spans across, with numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. To the right of the top edge of the rectangle, the label "octet 1" is present. + +Partial diagram of PDTCH block type 10 (MCS-6) downlink format showing bit numbering 1-8 and octet label 1. + +![Diagram of PDTCH block type 10 (MCS-6) downlink format. It shows a large block of 622 or 625 or 647 or 650 bits, with an RLC/MAC Block at the bottom. Octet markers 78, 81, and 82 are on the right side.](dd5771673aececa53d42ece89218299d_img.jpg) + +The diagram illustrates the downlink format for PDTCH block type 10 (MCS-6). It features a large rectangular block representing the data, labeled "622 or 625 or 647 or 650 Bit". At the bottom of this block is a smaller section labeled "RLC/MAC Block". To the right of the main block, there are three octet markers: "octet 78" aligned with the top of the RLC/MAC block, "octet 81" aligned with the bottom of the main block, and "octet 82" aligned with the bottom of the RLC/MAC block. Vertical ellipsis dots on the left and right sides of the main block indicate that it is a multi-octet structure. + +Diagram of PDTCH block type 10 (MCS-6) downlink format. It shows a large block of 622 or 625 or 647 or 650 bits, with an RLC/MAC Block at the bottom. Octet markers 78, 81, and 82 are on the right side. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.10.2: PDTCH block type 10 (MCS-6) downlink format + +### 7.6.11 PDTCH block type 11 (MCS-7) format + +#### 7.6.11.1 Uplink + +The 946 bit blocks, or in case both a PAN and an eTFI are included, 974 bit blocks, or in case a PAN is included, 971 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 11 (MCS-7) uplink format. It shows a large block of 946 or 971 or 974 bits, with an RLC/MAC Block at the bottom. Octet markers 1, 119, and 122 are on the right side. Above the block, there is a dashed line with arrows pointing left and numbers 8 through 1.](7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg) + +The diagram illustrates the uplink format for PDTCH block type 11 (MCS-7). Above the main block is a dashed line with arrows pointing left, labeled with numbers 8, 7, 6, 5, 4, 3, 2, and 1 from left to right. The main block is labeled "946 or 971 or 974 Bit". At the bottom of this block is a section labeled "RLC/MAC Block". To the right of the main block, there are three octet markers: "octet 1" aligned with the top, "octet 119" aligned with the bottom of the main block, and "octet 122" aligned with the bottom of the RLC/MAC block. Vertical ellipsis dots on the left and right sides of the main block indicate its multi-octet nature. + +Diagram of PDTCH block type 11 (MCS-7) uplink format. It shows a large block of 946 or 971 or 974 bits, with an RLC/MAC Block at the bottom. Octet markers 1, 119, and 122 are on the right side. Above the block, there is a dashed line with arrows pointing left and numbers 8 through 1. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.11.1: PDTCH block type 11(MCS-7) uplink format + +#### 7.6.11.2 Downlink + +The 940 bit blocks, or in case an eTFI is included, 943 bit blocks, or in case a PAN is included, 965 bit blocks, or in case both a PAN and an eTFI are included, 968 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 11 (MCS-7) downlink format. It shows a large block of 940 or 943 or 965 or 968 bits. Octet marker 1 is on the right side. Above the block, there is a dashed line with arrows pointing left and numbers 8 through 1.](718be1eb075833deb7a3b80729a06264_img.jpg) + +The diagram illustrates the downlink format for PDTCH block type 11 (MCS-7). Above the main block is a dashed line with arrows pointing left, labeled with numbers 8, 7, 6, 5, 4, 3, 2, and 1 from left to right. The main block is labeled "940 or 943 or 965 or 968 Bit". To the right of the main block, there is one octet marker: "octet 1" aligned with the top. Vertical ellipsis dots on the left and right sides of the main block indicate its multi-octet nature. + +Diagram of PDTCH block type 11 (MCS-7) downlink format. It shows a large block of 940 or 943 or 965 or 968 bits. Octet marker 1 is on the right side. Above the block, there is a dashed line with arrows pointing left and numbers 8 through 1. + +![Diagram of PDTCH block type 11 (MCS-7) downlink format. It shows a large rectangle labeled 'RLC/MAC Block'. Above the rectangle, there are three vertical dots. To the right of the rectangle, there are two labels: 'octet 118' and 'octet 121'. The 'octet 118' label is aligned with the top edge of the rectangle, and the 'octet 121' label is aligned with the bottom edge of the rectangle. The rectangle is divided into two horizontal sections by a dashed line.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Diagram of PDTCH block type 11 (MCS-7) downlink format. It shows a large rectangle labeled 'RLC/MAC Block'. Above the rectangle, there are three vertical dots. To the right of the rectangle, there are two labels: 'octet 118' and 'octet 121'. The 'octet 118' label is aligned with the top edge of the rectangle, and the 'octet 121' label is aligned with the bottom edge of the rectangle. The rectangle is divided into two horizontal sections by a dashed line. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.11.2: PDTCH block type 11 (MCS-7) downlink format + +### 7.6.12 PDTCH block type 12 (MCS-8) format + +#### 7.6.12.1 Uplink + +The 1138 bit blocks, or in case both a PAN and an eTFI are included, 1166 bit blocks, or in case a PAN is included, 1163 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 12 (MCS-8) uplink format. At the top, there is a dashed line with arrows pointing left and right, and numbers 8, 7, 6, 5, 4, 3, 2, 1 below it. Below this, there is a large rectangle containing the text '1138 or 1163 or 1166 Bit'. To the right of this rectangle is the label 'octet 1'. Below this rectangle is another large rectangle labeled 'RLC/MAC Block'. To the right of this rectangle are two labels: 'octet 143' and 'octet 146'. The 'octet 143' label is aligned with the top edge of the 'RLC/MAC Block' rectangle, and the 'octet 146' label is aligned with the bottom edge of the 'RLC/MAC Block' rectangle. The 'RLC/MAC Block' rectangle is divided into two horizontal sections by a dashed line.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +Diagram of PDTCH block type 12 (MCS-8) uplink format. At the top, there is a dashed line with arrows pointing left and right, and numbers 8, 7, 6, 5, 4, 3, 2, 1 below it. Below this, there is a large rectangle containing the text '1138 or 1163 or 1166 Bit'. To the right of this rectangle is the label 'octet 1'. Below this rectangle is another large rectangle labeled 'RLC/MAC Block'. To the right of this rectangle are two labels: 'octet 143' and 'octet 146'. The 'octet 143' label is aligned with the top edge of the 'RLC/MAC Block' rectangle, and the 'octet 146' label is aligned with the bottom edge of the 'RLC/MAC Block' rectangle. The 'RLC/MAC Block' rectangle is divided into two horizontal sections by a dashed line. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.12.1: PDTCH block type 12 (MCS-8) uplink format + +#### 7.6.12.2 Downlink + +The 1132 bit blocks, or in case an eTFI is included, 1135 bit blocks, or in case a PAN is included, 1157 bit blocks, or in case both a PAN and an eTFI are included, 1160 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 12 (MCS-8) downlink format. At the top, there is a dashed line with arrows pointing left and right, and numbers 8, 7, 6, 5, 4, 3, 2, 1 below it. Below this, there is a large rectangle containing the text '1132 or 1135 or 1157 or 1160 Bit'. To the right of this rectangle is the label 'octet 1'. Below this rectangle is another large rectangle labeled 'RLC/MAC Block'. The 'RLC/MAC Block' rectangle is divided into two horizontal sections by a dashed line.](b81d1613e285a9353171cdc5ef97a1f0_img.jpg) + +Diagram of PDTCH block type 12 (MCS-8) downlink format. At the top, there is a dashed line with arrows pointing left and right, and numbers 8, 7, 6, 5, 4, 3, 2, 1 below it. Below this, there is a large rectangle containing the text '1132 or 1135 or 1157 or 1160 Bit'. To the right of this rectangle is the label 'octet 1'. Below this rectangle is another large rectangle labeled 'RLC/MAC Block'. The 'RLC/MAC Block' rectangle is divided into two horizontal sections by a dashed line. + +![Diagram of PDTCH block type 12 (MCS-8) downlink format showing octets 142 and 145.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +The diagram shows a rectangular block representing a PDTCH block. It is divided into two main horizontal sections. The top section is labeled 'octet 142' on the right. The bottom section is labeled 'octet 145' on the right. There is a dashed line above the top section, and a dashed line to the left of the bottom section. + +Diagram of PDTCH block type 12 (MCS-8) downlink format showing octets 142 and 145. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.12.2: PDTCH block type 12 (MCS-8) downlink format + +### 7.6.13 PDTCH block type 13 (MCS-9) format + +#### 7.6.13.1 Uplink + +The 1234 bit blocks are used in the following way: + +![Diagram of PDTCH block type 13 (MCS-9) uplink format showing 1234 bits and RLC/MAC block structure across octets 1 to 155.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +The diagram shows a rectangular block representing a PDTCH block. Above the block, there is a dashed line with a left-pointing arrow, and below it, a row of numbers from 8 to 1. The main body of the block is divided into two horizontal sections. The top section is labeled '1234 Bit' in the center. The bottom section is labeled 'RLC/MAC Block' in the center. The left and right sides of the block are marked with vertical ellipsis dots. The top right corner is labeled 'octet 1' and the bottom right corner is labeled 'octet 155'. + +Diagram of PDTCH block type 13 (MCS-9) uplink format showing 1234 bits and RLC/MAC block structure across octets 1 to 155. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.13.1: PDTCH block type 13 (MCS-9) uplink format + +#### 7.6.13.2 Downlink + +The 1228 bit blocks, or in case an eTFI is included, 1231 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 13 (MCS-9) downlink format showing 1228 or 1231 bits and RLC/MAC block structure across octets 1 to 154.](e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg) + +The diagram shows a rectangular block representing a PDTCH block. Above the block, there is a dashed line with a left-pointing arrow, and below it, a row of numbers from 8 to 1. The main body of the block is divided into two horizontal sections. The top section is labeled '1228 or 1231 Bit' in the center. The bottom section is labeled 'RLC/MAC Block' in the center. The left and right sides of the block are marked with vertical ellipsis dots. The top right corner is labeled 'octet 1' and the bottom right corner is labeled 'octet 154'. + +Diagram of PDTCH block type 13 (MCS-9) downlink format showing 1228 or 1231 bits and RLC/MAC block structure across octets 1 to 154. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.13.2: PDTCH block type 13 (MCS-9) downlink format + +### 7.6.14 PDTCH block type 14 (UAS-7) format (uplink only) + +The blocks of 941 bits, or in case a PAN is included, 966 bits, or in case both a PAN and an eTFI are included, 969 bits, are used in the following way: + +![Diagram of PDTCH block type 14 (UAS-7) format showing bit and octet numbering.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 14 (UAS-7) format. At the top, a dashed line with arrows at both ends spans across the top of the block, with bit numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. The main body of the block is a large rectangle divided into several horizontal sections. The top section is labeled '941 or 966 or 969 Bit' and 'octet 1'. Below this, there are three vertical dots on the left and right sides. The next section is labeled 'RLC/MAC Block'. Below this, the block is divided into two rows. The first row is labeled 'octet 118' on the right. The second row is labeled 'octet 121' on the right. The third row is labeled 'octet 122' on the right. The block is further divided into several smaller rectangular sections by horizontal and vertical lines. + +Diagram of PDTCH block type 14 (UAS-7) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.14.1: PDTCH block type 14 (UAS-7) format + +### 7.6.15 PDTCH block type 15 (UAS-8) format (uplink only) + +The blocks of 1069 bits, or in case a PAN is included, 1094 bits, or in case both a PAN and an eTFI are included, 1097 bits, are used in the following way: + +![Diagram of PDTCH block type 15 (UAS-8) format showing bit and octet numbering.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 15 (UAS-8) format. At the top, a dashed line with arrows at both ends spans across the top of the block, with bit numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. The main body of the block is a large rectangle divided into several horizontal sections. The top section is labeled '1069 or 1094 or 1097 Bit' and 'octet 1'. Below this, there are three vertical dots on the left and right sides. The next section is labeled 'RLC/MAC Block'. Below this, the block is divided into two rows. The first row is labeled 'octet 134' on the right. The second row is labeled 'octet 137' on the right. The third row is labeled 'octet 138' on the right. The block is further divided into several smaller rectangular sections by horizontal and vertical lines. + +Diagram of PDTCH block type 15 (UAS-8) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.15.1: PDTCH block type 15 (UAS-8) format + +### 7.6.16 PDTCH block type 16 (UAS-9) format (uplink only) + +The blocks of 1229 bits, or in case a PAN is included, 1254 bits, or in case both a PAN and an eTFI are included, 1257 bits, are used in the following way: + +![Diagram of PDTCH block type 16 (UAS-9) format showing bit numbering 1-8, total bits (1229 or 1254 or 1257), RLC/MAC Block, and octet labels 1, 154, 157, 158.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 16 (UAS-9). At the top, a dashed line with arrows at both ends spans across the top of the block, with bit numbers 8, 7, 6, 5, 4, 3, 2, and 1 positioned below it. The main rectangular block contains the text "1229 or 1254 or 1257 Bit" in the upper half and "RLC/MAC Block" in the lower half. Vertical ellipsis dots are shown on the left and right sides of the main block. To the right of the block, the label "octet 1" is aligned with the top edge, "octet 154" is aligned with the horizontal line separating the RLC/MAC Block from the lower section, "octet 157" is aligned with a lower horizontal line, and "octet 158" is aligned with the bottom edge of the block. + +Diagram of PDTCH block type 16 (UAS-9) format showing bit numbering 1-8, total bits (1229 or 1254 or 1257), RLC/MAC Block, and octet labels 1, 154, 157, 158. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.16.1: PDTCH block type 16 (UAS-9) format + +### 7.6.17 PDTCH block type 17 (UAS-10) format (uplink only) + +The blocks of 1402 bits, or in case a PAN is included, 1427 bits, or in case both a PAN and an eTFI are included, 1430 bits, are used in the following way: + +![Diagram of PDTCH block type 17 (UAS-10) format showing bit numbering 1-8, total bits (1402 or 1427 or 1430), RLC/MAC Block, and octet labels 1, 176, 179.](836b0790cef5469a167fa8931df4e408_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 17 (UAS-10). Similar to the previous diagram, it features a top dashed line with bit numbers 8 through 1. The main block contains "1402 or 1427 or 1430 Bit" and "RLC/MAC Block". To the right, "octet 1" is at the top, "octet 176" is aligned with the line below the RLC/MAC Block, and "octet 179" is at the bottom edge. + +Diagram of PDTCH block type 17 (UAS-10) format showing bit numbering 1-8, total bits (1402 or 1427 or 1430), RLC/MAC Block, and octet labels 1, 176, 179. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.17.1: PDTCH block type 17 (UAS-10) format + +### 7.6.18 PDTCH block type 18 (UAS-11) format (uplink only) + +The blocks of 1594 bits, or in case a PAN is included, 1619 bits, or in case both a PAN and an eTFI are included, 1622 bits, are used in the following way: + +![Diagram of PDTCH block type 18 (UAS-11) format showing 8 bits numbered 8 to 1, containing 1594 or 1619 or 1622 Bit RLC/MAC Block, spanning from octet 1 to octet 203.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 18 (UAS-11). At the top, a dashed line with a left-pointing arrow spans over eight bits labeled 8, 7, 6, 5, 4, 3, 2, and 1. Below this, a large rectangular box represents the data payload, labeled "1594 or 1619 or 1622 Bit" and "RLC/MAC Block". The box is divided into several horizontal rows by dotted lines. The first row is labeled "octet 1" on the right. The fourth row is labeled "octet 200" on the right. The seventh row is labeled "octet 203" on the right. Vertical dotted lines divide the box into columns corresponding to the bit numbers 8 through 1. + +Diagram of PDTCH block type 18 (UAS-11) format showing 8 bits numbered 8 to 1, containing 1594 or 1619 or 1622 Bit RLC/MAC Block, spanning from octet 1 to octet 203. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.18.1: PDTCH block type 18 (UAS-11) format + +### 7.6.19 PDTCH block type 19 (UBS-5) format (uplink only) + +The blocks of 479 bits, or in case a PAN is included, 504 bits, are used in the following way: + +![Diagram of PDTCH block type 19 (UBS-5) format showing 8 bits numbered 8 to 1, containing 479 or 504 Bit RLC/MAC Block, spanning from octet 1 to octet 63.](446100c084b94817a19c319fa776b412_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 19 (UBS-5). At the top, a dashed line with a left-pointing arrow spans over eight bits labeled 8, 7, 6, 5, 4, 3, 2, and 1. Below this, a large rectangular box represents the data payload, labeled "479 or 504 Bit" and "RLC/MAC Block". The box is divided into several horizontal rows by dotted lines. The first row is labeled "octet 1" on the right. The fourth row is labeled "octet 60" on the right. The seventh row is labeled "octet 63" on the right. Vertical dotted lines divide the box into columns corresponding to the bit numbers 8 through 1. + +Diagram of PDTCH block type 19 (UBS-5) format showing 8 bits numbered 8 to 1, containing 479 or 504 Bit RLC/MAC Block, spanning from octet 1 to octet 63. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.19.1: PDTCH block type 19 (UBS-5) format + +### 7.6.20 PDTCH block type 20 (UBS-6) format (uplink only) + +The blocks of 623 bits, or in case a PAN is included, 648 bits, are used in the following way: + +![Diagram of PDTCH block type 20 (UBS-6) format showing bit and octet numbering.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 20 (UBS-6). At the top, a dashed line with a left-pointing arrow spans across the top of a grid. Below this line, the grid has 8 columns numbered 8, 7, 6, 5, 4, 3, 2, and 1 from left to right. The first row of the grid is labeled 'octet 1' on the right. This row contains the text '623 or 648 Bit' in the center. Below this row, there are three vertical dots on both the left and right sides, indicating more rows. The next row contains the text 'RLC/MAC Block' in the center. Below this row, the grid continues with several empty rows. The row immediately following the 'RLC/MAC Block' row is labeled 'octet 78' on the right. The bottom-most row of the grid is labeled 'octet 81' on the right. The grid is composed of horizontal and vertical lines, with some cells being empty or partially empty. + +Diagram of PDTCH block type 20 (UBS-6) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.20.1: PDTCH block type 20 (UBS-6) format + +### 7.6.21 PDTCH block type 21 (UBS-7) format (uplink only) + +The blocks of 940 bits, or in case a PAN is included, 965 bits, are used in the following way: + +![Diagram of PDTCH block type 21 (UBS-7) format showing bit and octet numbering.](409498e57b1f988b2b604d12cd997002_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 21 (UBS-7). It follows a similar layout to the previous diagram. At the top, a dashed line with a left-pointing arrow spans across the top of a grid. Below this line, the grid has 8 columns numbered 8, 7, 6, 5, 4, 3, 2, and 1 from left to right. The first row of the grid is labeled 'octet 1' on the right. This row contains the text '940 or 965 Bit' in the center. Below this row, there are three vertical dots on both the left and right sides, indicating more rows. The next row contains the text 'RLC/MAC Block' in the center. Below this row, the grid continues with several empty rows. The row immediately following the 'RLC/MAC Block' row is labeled 'octet 118' on the right. The bottom-most row of the grid is labeled 'octet 121' on the right. The grid is composed of horizontal and vertical lines, with some cells being empty or partially empty. + +Diagram of PDTCH block type 21 (UBS-7) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.21.1: PDTCH block type 21 (UBS-7) format + +### 7.6.22 PDTCH block type 22 (UBS-8) format (uplink only) + +The blocks of 1228 bits, or in case a PAN is included, 1253 bits, are used in the following way: + +![Diagram of PDTCH block type 22 (UBS-8) format showing 1228 or 1253 bits, RLC/MAC Block, and octet numbering from 1 to 157.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 22 (UBS-8). At the top, a dashed line with a left-pointing arrow spans across, with bit positions 8, 7, 6, 5, 4, 3, 2, and 1 labeled below it. The main block is a rectangle divided into several horizontal sections. The top section is labeled '1228 or 1253 Bit'. Below this, there are three small vertical dots on the left and right sides. The next section is labeled 'RLC/MAC Block'. Below this, the text 'octet 154' is on the right. The bottom section is labeled 'octet 157' on the right. The RLC/MAC Block is shown as a single row spanning most of the width, with a vertical line separating it from the octet 154 section. + +Diagram of PDTCH block type 22 (UBS-8) format showing 1228 or 1253 bits, RLC/MAC Block, and octet numbering from 1 to 157. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.22.1: PDTCH block type 22 (UBS-8) format + +### 7.6.23 PDTCH block type 23 (UBS-9) format (uplink only) + +The blocks of 1402 bits, or in case a PAN is included, 1427 bits, are used in the following way: + +![Diagram of PDTCH block type 23 (UBS-9) format showing 1402 or 1427 bits, RLC/MAC Block, and octet numbering from 1 to 179.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 23 (UBS-9). At the top, a dashed line with a left-pointing arrow spans across, with bit positions 8, 7, 6, 5, 4, 3, 2, and 1 labeled below it. The main block is a rectangle divided into several horizontal sections. The top section is labeled '1402 or 1427 Bit'. Below this, there are three small vertical dots on the left and right sides. The next section is labeled 'RLC/MAC Block'. Below this, the text 'octet 176' is on the right. The bottom section is labeled 'octet 179' on the right. The RLC/MAC Block is shown as a single row spanning most of the width, with a vertical line separating it from the octet 176 section. + +Diagram of PDTCH block type 23 (UBS-9) format showing 1402 or 1427 bits, RLC/MAC Block, and octet numbering from 1 to 179. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.23.1: PDTCH block type 23 (UBS-9) format + +### 7.6.24 PDTCH block type 24 (UBS-10) format (uplink only) + +The blocks of 1834 bits, or in case a PAN is included, 1859 bits, are used in the following way: + +![Diagram of PDTCH block type 24 (UBS-10) format showing bit and octet numbering.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 24 (UBS-10). At the top, a dashed line with a left-pointing arrow spans across the top of a grid. Below this line, the grid has 8 columns labeled 8, 7, 6, 5, 4, 3, 2, and 1 from left to right. The first row of the grid is labeled 'octet 1' on the right. This row contains the text '1834 or 1859 Bit' centered across the columns. Below this row, there are three vertical ellipsis dots on the left and right sides. The next row is labeled 'RLC/MAC Block' centered. Below this row, the grid continues with more rows. The row immediately below 'RLC/MAC Block' is labeled 'octet 230' on the right. The bottom-most row of the grid is labeled 'octet 233' on the right. + +Diagram of PDTCH block type 24 (UBS-10) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.24.1: PDTCH block type 24 (UBS-10) format + +### 7.6.25 PDTCH block type 25 (UBS-11) format (uplink only) + +The blocks of 2248 bits, or in case a PAN is included, 2273 bits, are used in the following way: + +![Diagram of PDTCH block type 25 (UBS-11) format showing bit and octet numbering.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 25 (UBS-11). It follows the same grid structure as the previous diagram, with 8 columns labeled 8, 7, 6, 5, 4, 3, 2, and 1. The first row is labeled 'octet 1' on the right and contains the text '2248 or 2273 Bit' centered. Below this row are three vertical ellipsis dots on the left and right. The next row is labeled 'RLC/MAC Block' centered. Below this row, the grid continues. The row immediately below 'RLC/MAC Block' is labeled 'octet 281' on the right. The bottom-most row of the grid is labeled 'octet 285' on the right. + +Diagram of PDTCH block type 25 (UBS-11) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.25.1: PDTCH block type 25 (UBS-11) format + +### 7.6.26 PDTCH block type 26 (UBS-12) format (uplink only) + +The blocks of 2440 bits, or in case a PAN is included, 2465 bits, are used in the following way: + +![Diagram of PDTCH block type 26 (UBS-12) format showing 8 bits per octet, with 2440 or 2465 bits total, containing an RLC/MAC Block. Octets are numbered 1 to 309.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 26 (UBS-12). At the top, a dashed line with a left-pointing arrow spans across 8 bits, labeled 8, 7, 6, 5, 4, 3, 2, and 1. Below this, a large rectangle represents the block, divided into sections. The top section is labeled "2440 or 2465 Bit" and "octet 1". Below this, a section is labeled "RLC/MAC Block" and "octet 305". The bottom of the block is labeled "octet 309". Vertical ellipsis dots on the left and right sides of the main block indicate intermediate octets. + +Diagram of PDTCH block type 26 (UBS-12) format showing 8 bits per octet, with 2440 or 2465 bits total, containing an RLC/MAC Block. Octets are numbered 1 to 309. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.26.1: PDTCH block type 26 (UBS-12) format + +### 7.6.27 PDTCH block type 27 (DAS-5) format (downlink only) + +The blocks of 478 bits, or in case an eTFI is included, 481 bit blocks, or in case a PAN is included, 503 bits, or in case both a PAN and an eTFI are included, 506 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 27 (DAS-5) format showing 8 bits per octet, with 478 or 481 or 503 or 506 bits total, containing an RLC/MAC Block. Octets are numbered 1 to 64.](f1091147d93cee4dfa88498610e395a7_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 27 (DAS-5). Similar to the previous diagram, it has a header with 8 bits (1-8) and a dashed line. The main block is labeled "478 or 481 or 503 or 506 Bit" and "octet 1". Below this is the "RLC/MAC Block" section, labeled "octet 60". Further down, "octet 63" and "octet 64" are indicated. Vertical ellipsis dots are present on the sides of the main block. + +Diagram of PDTCH block type 27 (DAS-5) format showing 8 bits per octet, with 478 or 481 or 503 or 506 bits total, containing an RLC/MAC Block. Octets are numbered 1 to 64. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.27.1: PDTCH block type 27 (DAS-5) format + +### 7.6.28 PDTCH block type 28 (DAS-6) format (downlink only) + +The blocks of 574 bits, or in case an eTFI is included, 577 bit blocks, or in case a PAN is included, 599 bits, or in case both a PAN and an eTFI are included, 602 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 28 (DAS-6) format showing bit and octet numbering.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 28 (DAS-6). At the top, a dashed line with a left-pointing arrow indicates bit numbering from 8 down to 1. Below this, a large rectangle represents the 'Bit' block, containing the text '574 or 577 or 599 or 602 Bit'. Below the Bit block is another rectangle labeled 'RLC/MAC Block'. To the right of the Bit block, the label 'octet 1' is present. Below the RLC/MAC Block, the label 'octet 72' is present. Further down, there are two more empty rectangular sections, labeled 'octet 75' and 'octet 76' on the right side respectively. + +Diagram of PDTCH block type 28 (DAS-6) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.28.1: PDTCH block type 28 (DAS-6) format + +### 7.6.29 PDTCH block type 29 (DAS-7) format (downlink only) + +The blocks of 686 bits, or in case an eTFI is included, 689 bit blocks, or in case a PAN is included, 711 bits, or in case both a PAN and an eTFI are included, 714 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 29 (DAS-7) format showing bit and octet numbering.](132cff7e872feb31f629703959beddd7_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 29 (DAS-7). At the top, a dashed line with a left-pointing arrow indicates bit numbering from 8 down to 1. Below this, a large rectangle represents the 'Bit' block, containing the text '686 or 689 or 711 or 714 Bit'. Below the Bit block is another rectangle labeled 'RLC/MAC Block'. To the right of the Bit block, the label 'octet 1' is present. Below the RLC/MAC Block, the label 'octet 86' is present. Further down, there are two more empty rectangular sections, labeled 'octet 89' and 'octet 90' on the right side respectively. + +Diagram of PDTCH block type 29 (DAS-7) format showing bit and octet numbering. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.29.1: PDTCH block type 29 (DAS-7) format + +### 7.6.30 PDTCH block type 30 (DAS-8) format (downlink only) + +The blocks of 941 bits, or in case an eTFI is included, 944 bit blocks, or in case a PAN is included, 966 bits, or in case both a PAN and an eTFI are included, 969 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 30 (DAS-8) format showing bit numbering 8 to 1, octet 1, RLC/MAC Block, octet 118, octet 121, and octet 122.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 30 (DAS-8). At the top, a dashed line with a left-pointing arrow spans across the top of a grid. Below this line, the numbers 8, 7, 6, 5, 4, 3, 2, and 1 are placed above the grid columns. The first row of the grid is labeled 'octet 1' on the right and contains the text '941 or 944 or 966 or 969 Bit' in the center. Below this row, there are three rows of vertical dots. The next row is labeled 'RLC/MAC Block' in the center. Below this row, the grid is divided into two main sections: the left section is wider and the right section is narrower. This row is labeled 'octet 118' on the right. Below this, there are two more rows of vertical dots. The next row is labeled 'octet 121' on the right. Below this, there is one more row of vertical dots. The final row is labeled 'octet 122' on the right. + +Diagram of PDTCH block type 30 (DAS-8) format showing bit numbering 8 to 1, octet 1, RLC/MAC Block, octet 118, octet 121, and octet 122. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.30.1: PDTCH block type 30 (DAS-8) format + +### 7.6.31 PDTCH block type 31 (DAS-9) format (downlink only) + +The blocks of 1133 bits, or in case an eTFI is included, 1136 bit blocks, or in case a PAN is included, 1158 bits, or in case both a PAN and an eTFI are included, 1161 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 31 (DAS-9) format showing bit numbering 8 to 1, octet 1, 1133 or 1136 or 1158 or 1161 Bit, RLC/MAC Block, octet 142, octet 145, and octet 146.](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 31 (DAS-9). At the top, a dashed line with a left-pointing arrow spans across the top of a grid. Below this line, the numbers 8, 7, 6, 5, 4, 3, 2, and 1 are placed above the grid columns. The first row of the grid is labeled 'octet 1' on the right and contains the text '1133 or 1136 or 1158 or 1161 Bit' in the center. Below this row, there are three rows of vertical dots. The next row is labeled 'RLC/MAC Block' in the center. Below this row, the grid is divided into two main sections: the left section is wider and the right section is narrower. This row is labeled 'octet 142' on the right. Below this, there are two more rows of vertical dots. The next row is labeled 'octet 145' on the right. Below this, there is one more row of vertical dots. The final row is labeled 'octet 146' on the right. + +Diagram of PDTCH block type 31 (DAS-9) format showing bit numbering 8 to 1, octet 1, 1133 or 1136 or 1158 or 1161 Bit, RLC/MAC Block, octet 142, octet 145, and octet 146. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.31.1: PDTCH block type 31 (DAS-9) format + +### 7.6.32 PDTCH block type 32 (DAS-10) format (downlink only) + +The blocks of 1355 bits, or in case an eTFI is included, 1358 bit blocks, or in case a PAN is included, 1380 bits, or in case both a PAN and an eTFI are included, 1383 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 32 (DAS-10) format showing bit numbering 1-8, total bits (1355 or 1358 or 1380 or 1383), and RLC/MAC block placement between octet 1 and octet 170.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 32 (DAS-10). At the top, a dashed line with an arrow pointing left spans across the top of a grid. Below this line, the numbers 8, 7, 6, 5, 4, 3, 2, and 1 are placed in individual cells. The main body of the diagram is a large rectangle divided into several horizontal sections. The top section is labeled 'octet 1' on the right and contains the text '1355 or 1358 or 1380 or 1383 Bit' centered. Below this, there are three vertical dots on both the left and right sides. The next section is labeled 'RLC/MAC Block' centered. Below this block, the text 'octet 170' is on the right. Further down, there are two more horizontal lines, and at the bottom, the text 'octet 173' is on the right. The RLC/MAC block is shown as a single row spanning across the width of the main rectangle. + +Diagram of PDTCH block type 32 (DAS-10) format showing bit numbering 1-8, total bits (1355 or 1358 or 1380 or 1383), and RLC/MAC block placement between octet 1 and octet 170. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.32.1: PDTCH block type 32 (DAS-10) format + +### 7.6.33 PDTCH block type 33 (DAS-11) format (downlink only) + +The blocks of 1691 bits, or in case an eTFI is included, 1694 bit blocks, or in case a PAN is included, 1716 bits, or in case both a PAN and an eTFI are included, 1719 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 33 (DAS-11) format showing bit numbering 1-8, total bits (1691 or 1694 or 1716 or 1719), and RLC/MAC block placement between octet 1 and octet 212.](50214d232017279410e9c9db8eb75119_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 33 (DAS-11). It follows a similar layout to the previous diagram. At the top, a dashed line with an arrow pointing left spans across the top of a grid. Below this line, the numbers 8, 7, 6, 5, 4, 3, 2, and 1 are placed in individual cells. The main body of the diagram is a large rectangle divided into several horizontal sections. The top section is labeled 'octet 1' on the right and contains the text '1691 or 1694 or 1716 or 1719 Bit' centered. Below this, there are three vertical dots on both the left and right sides. The next section is labeled 'RLC/MAC Block' centered. Below this block, the text 'octet 212' is on the right. Further down, there are two more horizontal lines, and at the bottom, the text 'octet 215' is on the right. The RLC/MAC block is shown as a single row spanning across the width of the main rectangle. + +Diagram of PDTCH block type 33 (DAS-11) format showing bit numbering 1-8, total bits (1691 or 1694 or 1716 or 1719), and RLC/MAC block placement between octet 1 and octet 212. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.33.1: PDTCH block type 33 (DAS-11) format + +### 7.6.34 PDTCH block type 34 (DAS-12) format (downlink only) + +The blocks of 2027 bits, or in case an eTFI is included, 2030 bit blocks, or in case a PAN is included, 2052 bits, or in case both a PAN and an eTFI are included, 2055 bit blocks, are used in the following way: + +![Diagram of PDTCH block type 34 (DAS-12) format showing 8 bits per octet, with a total size of 2027 or 2030 or 2052 or 2055 bits, containing an RLC/MAC Block. Octet numbering starts at 1 and ends at 257.](8269648391c59363ea61243864a2adf7_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 34 (DAS-12). At the top, a dashed line with a left-pointing arrow spans across 8 bits, labeled 8, 7, 6, 5, 4, 3, 2, and 1. Below this, a large rectangle represents the block. The top portion of the rectangle is labeled "2027 or 2030 or 2052 or 2055 Bit". Below this, the text "RLC/MAC Block" is centered. The right side of the diagram indicates octet boundaries: "octet 1" at the top, "octet 254" further down, and "octet 257" at the bottom. Vertical dotted lines are present within the block, and horizontal lines separate the top bit section from the RLC/MAC block section. + +Diagram of PDTCH block type 34 (DAS-12) format showing 8 bits per octet, with a total size of 2027 or 2030 or 2052 or 2055 bits, containing an RLC/MAC Block. Octet numbering starts at 1 and ends at 257. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.34.1: PDTCH block type 34 (DAS-12) format + +### 7.6.35 PDTCH block type 35 (DBS-5) format (downlink only) + +The blocks of 480 bits, or in case a PAN is included, 505 bits, are used in the following way: + +![Diagram of PDTCH block type 35 (DBS-5) format showing 8 bits per octet, with a total size of 480 or 505 bits, containing an RLC/MAC Block. Octet numbering starts at 1 and ends at 64.](bc9d0c0b02cbe628b1b6548cc1107734_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 35 (DBS-5). Similar to the previous diagram, it has a header with 8 bits (8 to 1) indicated by a dashed line and arrow. The main block is a rectangle labeled "480 or 505 Bit" at the top, with "RLC/MAC Block" centered below it. The right side shows octet boundaries: "octet 1" at the top, "octet 60" in the middle, and "octet 64" at the bottom. Vertical dotted lines and horizontal lines are used to delineate the structure. + +Diagram of PDTCH block type 35 (DBS-5) format showing 8 bits per octet, with a total size of 480 or 505 bits, containing an RLC/MAC Block. Octet numbering starts at 1 and ends at 64. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.35.1: PDTCH block type 35 (DBS-5) format + +### 7.6.36 PDTCH block type 36 (DBS-6) format (downlink only) + +The blocks of 624 bits, or in case a PAN is included, 649 bits, are used in the following way: + +![Diagram of PDTCH block type 36 (DBS-6) format showing octet structure from octet 1 to octet 82. The header bits are numbered 8 down to 1. The payload contains '624 or 649 Bit' and 'RLC/MAC Block'.](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 36 (DBS-6). At the top, a dashed line with a left-pointing arrow spans bits numbered 8, 7, 6, 5, 4, 3, 2, and 1. Below this, the block is divided into octets. Octet 1 starts the '624 or 649 Bit' section. Vertical ellipses indicate continuation. Octet 78 marks the start of the 'RLC/MAC Block'. The structure continues down to octet 82, which is partially filled. + +Diagram of PDTCH block type 36 (DBS-6) format showing octet structure from octet 1 to octet 82. The header bits are numbered 8 down to 1. The payload contains '624 or 649 Bit' and 'RLC/MAC Block'. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +**Figure 7.6.36.1: PDTCH block type 36 (DBS-6) format** + +### 7.6.37 PDTCH block type 37 (DBS-7) format (downlink only) + +The blocks of 941 bits, or in case a PAN is included, 966 bits, are used in the following way: + +![Diagram of PDTCH block type 37 (DBS-7) format showing octet structure from octet 1 to octet 121. The header bits are numbered 8 down to 1. The payload contains '941 or 966 Bit' and 'RLC/MAC Block'.](09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 37 (DBS-7). At the top, a dashed line with a left-pointing arrow spans bits numbered 8, 7, 6, 5, 4, 3, 2, and 1. Octet 1 contains the '941 or 966 Bit' label. Vertical ellipses indicate continuation. The 'RLC/MAC Block' section is shown, with octet 118 and octet 121 marked on the right side to indicate the boundaries of the data structure. + +Diagram of PDTCH block type 37 (DBS-7) format showing octet structure from octet 1 to octet 121. The header bits are numbered 8 down to 1. The payload contains '941 or 966 Bit' and 'RLC/MAC Block'. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +**Figure 7.6.37.1: PDTCH block type 37 (DBS-7) format** + +### 7.6.38 PDTCH block type 38 (DBS-8) format (downlink only) + +The blocks of 1229 bits, or in case a PAN is included, 1254 bits, are used in the following way: + +![Diagram of PDTCH block type 38 (DBS-8) format showing 1229 or 1254 bits, RLC/MAC Block, and octet numbering from 1 to 157.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 38 (DBS-8). At the top, a dashed line with a left-pointing arrow spans across the top of a grid. Below this line, the grid has 8 columns labeled 8, 7, 6, 5, 4, 3, 2, and 1 from left to right. The first row of the grid is labeled 'octet 1' on the right. This row contains the text '1229 or 1254 Bit' centered. Below this, there are three vertical dots on both the left and right sides, indicating more rows. The next labeled row is 'octet 154' on the right, which contains the text 'RLC/MAC Block' centered. Below this, there are two more rows of empty grid cells. The final labeled row is 'octet 157' on the right. The grid is composed of solid lines for the main sections and dotted lines for the individual bit cells. + +Diagram of PDTCH block type 38 (DBS-8) format showing 1229 or 1254 bits, RLC/MAC Block, and octet numbering from 1 to 157. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.38.1: PDTCH block type 38 (DBS-8) format + +### 7.6.39 PDTCH block type 39 (DBS-9) format (downlink only) + +The blocks of 1403 bits, or in case a PAN is included, 1428 bits, are used in the following way: + +![Diagram of PDTCH block type 39 (DBS-9) format showing 1403 or 1428 bits, RLC/MAC Block, and octet numbering from 1 to 179.](a97518a839da75f8379c578562b01bc2_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 39 (DBS-9). It follows a similar layout to the previous diagram. At the top, a dashed line with a left-pointing arrow spans across the top of a grid. Below this line, the grid has 8 columns labeled 8, 7, 6, 5, 4, 3, 2, and 1 from left to right. The first row of the grid is labeled 'octet 1' on the right. This row contains the text '1403 or 1428 Bit' centered. Below this, there are three vertical dots on both the left and right sides. The next labeled row is 'octet 176' on the right, which contains the text 'RLC/MAC Block' centered. Below this, there are two more rows of empty grid cells. The final labeled row is 'octet 179' on the right. The grid is composed of solid lines for the main sections and dotted lines for the individual bit cells. + +Diagram of PDTCH block type 39 (DBS-9) format showing 1403 or 1428 bits, RLC/MAC Block, and octet numbering from 1 to 179. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.39.1: PDTCH block type 39 (DBS-9) format + +### 7.6.40 PDTCH block type 40 (DBS-10) format (downlink only) + +The blocks of 1835 bits, or in case a PAN is included, 1860 bits, are used in the following way: + +![Diagram of PDTCH block type 40 (DBS-10) format showing 1835 or 1860 bits, RLC/MAC Block, and octet numbering from 1 to 233.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 40 (DBS-10). At the top, a dashed line with a left-pointing arrow spans across the width, with bit positions 8, 7, 6, 5, 4, 3, 2, and 1 labeled below it. The main block is a rectangle divided into several horizontal sections. The top section is labeled '1835 or 1860 Bit'. Below this, there are three small vertical dots on the left and right sides. The next section is labeled 'RLC/MAC Block'. Below this, the right side of the block is labeled 'octet 230'. Further down, there are two more horizontal lines, and the right side is labeled 'octet 233'. + +Diagram of PDTCH block type 40 (DBS-10) format showing 1835 or 1860 bits, RLC/MAC Block, and octet numbering from 1 to 233. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.40.1: PDTCH block type 40 (DBS-10) format + +### 7.6.41 PDTCH block type 41 (DBS-11) format (downlink only) + +The blocks of 2249 bits, or in case a PAN is included, 2274 bits, are used in the following way: + +![Diagram of PDTCH block type 41 (DBS-11) format showing 2249 or 2274 bits, RLC/MAC Block, and octet numbering from 1 to 285.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 41 (DBS-11). At the top, a dashed line with a left-pointing arrow spans across the width, with bit positions 8, 7, 6, 5, 4, 3, 2, and 1 labeled below it. The main block is a rectangle divided into several horizontal sections. The top section is labeled '2249 or 2274 Bit'. Below this, there are three small vertical dots on the left and right sides. The next section is labeled 'RLC/MAC Block'. Below this, the right side of the block is labeled 'octet 282'. Further down, there are two more horizontal lines, and the right side is labeled 'octet 285'. + +Diagram of PDTCH block type 41 (DBS-11) format showing 2249 or 2274 bits, RLC/MAC Block, and octet numbering from 1 to 285. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.41.1: PDTCH block type 41 (DBS-11) format + +### 7.6.42 PDTCH block type 42 (DBS-12) format (downlink only) + +The blocks of 2441 bits, or in case a PAN is included, 2466 bits, are used in the following way: + +![Diagram of PDTCH block type 42 (DBS-12) format showing 2441 or 2466 bits across octets 1 to 309.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +The diagram illustrates the structure of a PDTCH block type 42 (DBS-12). It shows a sequence of bits numbered 8 down to 1 at the top, indicated by a dashed line with an arrow pointing left. Below this, a large rectangular box represents the block, containing the text "2441 or 2466 Bit" and "RLC/MAC Block". The box is divided into horizontal sections by dotted lines. The first section is labeled "octet 1" on the right. The last section is labeled "octet 309" on the right. Vertical dotted lines divide the box into columns corresponding to the bit numbers 8 through 1. + +Diagram of PDTCH block type 42 (DBS-12) format showing 2441 or 2466 bits across octets 1 to 309. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.6.42.1: PDTCH block type 42 (DBS-12) format + +## 7.7 PRACH uplink/PACCH uplink short acknowledgement block formats + +Two alternative PRACH uplink/PACCH uplink short acknowledgement block formats are specified. The 8 bit (1 octet) blocks are used in the uplink in the following way: + +![Diagram of 8 bit RLC/MAC block format showing a single octet with 8 bits.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) + +The diagram shows an 8-bit RLC/MAC block. At the top, a dashed line with an arrow pointing left indicates bit numbering from 8 down to 1. Below this is a single rectangular box labeled "8 bit RLC/MAC block" in the center. To the right of the box is the label "octet 1". + +Diagram of 8 bit RLC/MAC block format showing a single octet with 8 bits. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.7.a: PRACH uplink/PACCH uplink short acknowledgement block format + +The 11 bit blocks are used in the uplink in the following way: + +![Diagram of 11 bit RLC/MAC block format showing bits spread across octet 1 and octet 2.](f56ab8d50c10444a7043b7e30880cd0a_img.jpg) + +The diagram shows an 11-bit RLC/MAC block. At the top, a dashed line with an arrow pointing left indicates bit numbering from 8 down to 1. Below this, the first part of the block is a rectangular box labeled "11 bit RLC/MAC block" in the center, with "octet 1" to its right. Below this box, a second rectangular box is shown, with "octet 2" to its right. The 11 bits are distributed across these two octets: the first 8 bits (numbered 8-1) are in the first octet, and the remaining 3 bits (numbered 11-9) are in the second octet. + +Diagram of 11 bit RLC/MAC block format showing bits spread across octet 1 and octet 2. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies. + +Figure 7.7.b: PRACH uplink/PACCH uplink short acknowledgement block format + +## 7.8 PTCCH downlink block format + +The 184 bit (23 octets) blocks are used in the downlink in the following way: + +![Diagram of PTCCH downlink block format showing 184 bits across 23 octets.](5cb74e3ca5034698d7eab12de06f8763_img.jpg) + +The diagram shows a PTCCH downlink block. At the top, a dashed line with an arrow pointing left indicates bit numbering from 8 down to 1. Below this is a rectangular box labeled "Ordered timing advance for MS assigned TAI = 0" in the center. To the right of the box is the label "octet 1". The box is divided into 23 equal segments by vertical dotted lines, representing the 23 octets of the 184-bit block. + +Diagram of PTCCH downlink block format showing 184 bits across 23 octets. + +![Figure 7.8: PTCCH downlink block format diagram showing octets 2 through 23. Octet 2 contains 'Ordered timing advance for MS assigned TAI = 1'. Octet 16 contains 'Ordered timing advance for MS assigned TAI = 15'. Octet 17 contains '7 octets'. Octet 23 contains 'fill octets: "00101011"'.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +| | | +|--------------------------------------------------------|----------| +| Ordered timing advance for MS assigned TAI = 1 | octet 2 | +| | | +| | | +| | | +| Ordered timing advance for MS assigned TAI = 15 | octet 16 | +| | octet 17 | +| 7 octets | | +| | | +| | | +| fill octets:
"00101011" | octet 23 | + +Figure 7.8: PTCCH downlink block format diagram showing octets 2 through 23. Octet 2 contains 'Ordered timing advance for MS assigned TAI = 1'. Octet 16 contains 'Ordered timing advance for MS assigned TAI = 15'. Octet 17 contains '7 octets'. Octet 23 contains 'fill octets: "00101011"'. + +Figure 7.8: PTCCH downlink block format + +The field mapping convention in this clause is that when a field is contained within a single octet, the highest bit number of the field represents the highest order value and lowest bit number of the field represents the lowest order value. + +Spare bits are encoded with the binary value "0". Fill octets are encoded with the binary value "00101011". + +## 7.9 PTCCH uplink block formats + +Two alternative PTCCH uplink block formats are specified. The 8 bit (1 octet) blocks are used in the uplink in the following way: + +![Figure 7.9.a: PTCCH uplink block format diagram showing octet 1 with 8 fixed bits: "01111111". Bits are numbered 8 to 1 from left to right.](94d3fdcc244924326f02533aeb2d93fc_img.jpg) + +| | | +|-----------------------------------------------------------|---------| +| 8      7      6      5      4      3      2      1 | | +| 8 fixed bits: "01111111" | octet 1 | + +Figure 7.9.a: PTCCH uplink block format diagram showing octet 1 with 8 fixed bits: "01111111". Bits are numbered 8 to 1 from left to right. + +Figure 7.9.a: PTCCH uplink block format + +The 11 bit blocks are used in the uplink in the following way: + +![Figure 7.9.b: PTCCH uplink block format diagram showing octet 1 with 11 fixed bits: "11111111111" and octet 2. Bits are numbered 8 to 1 from left to right.](a89d151b67109378baed0c117830cf78_img.jpg) + +| | | +|-----------------------------------------------------------|---------| +| 8      7      6      5      4      3      2      1 | | +| 11 fixed bits: "11111111111" | octet 1 | +| | octet 2 | + +Figure 7.9.b: PTCCH uplink block format diagram showing octet 1 with 11 fixed bits: "11111111111" and octet 2. Bits are numbered 8 to 1 from left to right. + +Figure 7.9.b: PTCCH uplink block format + +The field mapping convention of sub-clause 7.10 applies. In the addition, when a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of a field contained in a given octet the lowest bit number represents the lowest order value. + +## 7.9a Transport block formats (Iu mode) + +### 7.9a.1 Generic transport block format + +When FLO is used, a transport block may be of any size between 1 and 450 bits for GMSK channels, and between 1 and 1370 bits for 8PSK channels. Each transport block contains one RLC/MAC block. + +![Diagram of Transport block format showing octets 1 to N, with bits 1 to 8. It labels 'M Bits' and 'RLC/MAC Block'.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +The diagram illustrates the structure of a transport block. It is a rectangular grid with 8 columns (bits 8 to 1) and N rows (octets 1 to N). The top row is labeled 'octet 1' and the bottom row is labeled 'octet N'. Above the grid, a dashed line with a left-pointing arrow spans from bit 8 to bit 1. The grid is divided into two main sections by horizontal lines: the top section is labeled 'M Bits' and the bottom section is labeled 'RLC/MAC Block'. Vertical dashed lines separate the columns. + +Diagram of Transport block format showing octets 1 to N, with bits 1 to 8. It labels 'M Bits' and 'RLC/MAC Block'. + +NOTE 1: The N-th octet may contain fewer than 8 bits + +NOTE 2: The numbering convention specified in 3GPP TS 44.060 applies + +**Figure 7.9a.1 Transport block format** + +### 7.9a.2 Transport block format for signalling TFC + +A TFC is defined that shall be used for signalling. It may also be used for data. For this TFC, the transport block format contains 23 octets. + +![Diagram of Transport block format for signalling TFC showing octets 1 to 23, with bits 1 to 8. It labels 'M Bits' and 'RLC/MAC Block'.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +This diagram shows the transport block format for a signalling TFC. It consists of 23 octets, each with 8 bits. The top octet is labeled 'octet 1' and the bottom octet is labeled 'octet 23'. Above the grid, a dashed line with a left-pointing arrow spans from bit 8 to bit 1. The grid is divided into two main sections: the top section is labeled 'M Bits' and the bottom section is labeled 'RLC/MAC Block'. Vertical dashed lines separate the columns. + +Diagram of Transport block format for signalling TFC showing octets 1 to 23, with bits 1 to 8. It labels 'M Bits' and 'RLC/MAC Block'. + +NOTE: The numbering convention specified in 3GPP TS 44.060 applies + +**Figure 7.9a.2 Transport block format for TFC for signalling** + +## 7.9b EC-BCCH/EC-CCCH/EC-PDTCH/EC-PACCH block formats + +### 7.9b.1 EC-BCCH + +See subclause 7.3.1. + +### 7.9b.2 EC-CCCH + +#### 7.9b.2.1 EC-PCH/EC-AGCH + +The 11 octets blocks are used in the downlink in the way shown in figure 7.9b.1. + +![Figure 7.9b.1: EC-PCH/EC-AGCH downlink block format diagram. The diagram shows a rectangular block representing 11 octets. Above the block, a horizontal arrow points left, with numbers 8, 7, 6, 5, 4, 3, 2, 1 above it. The top of the block is labeled 'Octet 1' and the bottom is labeled 'Octet 11'. Inside the block, there are vertical dotted lines on the left and right sides, and the text '11 octets' and 'Layer 2 frame' is centered.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Figure 7.9b.1: EC-PCH/EC-AGCH downlink block format diagram. The diagram shows a rectangular block representing 11 octets. Above the block, a horizontal arrow points left, with numbers 8, 7, 6, 5, 4, 3, 2, 1 above it. The top of the block is labeled 'Octet 1' and the bottom is labeled 'Octet 11'. Inside the block, there are vertical dotted lines on the left and right sides, and the text '11 octets' and 'Layer 2 frame' is centered. + +**Figure 7.9b.1: EC-PCH/EC-AGCH downlink block format** + +#### 7.9b.2.2 EC-RACH + +See subclause 7.4a for the 11 bit RACH format. + +### 7.9b.3 EC-PDTCH + +See subclause 7.6.5 to 7.6.13 for MCS-1 to MCS-9 respectively for the case that no eTFI and no PAN is included in the block. + +In the downlink the first three bits in the first octet are carried by the USF and the value of this field may vary between different blind physical layer transmissions (i.e. for EC-PDTCH/D/4, EC-PDTCH/D/8, EC-PDTCH/D/16). + +### 7.9b.4 EC-PACCH + +#### 7.9b.4.1 Downlink + +The 10 octets block is used in the downlink in the way shown in figure 7.9b.2. + +![Figure 7.9b.2: EC-PACCH downlink block format diagram. The diagram shows a rectangular block representing 10 octets. Above the block, a horizontal arrow points left, with numbers 8, 7, 6, 5, 4, 3, 2, 1 above it. The top of the block is labeled 'Octet 1' and the bottom is labeled 'Octet 10'. Inside the block, there are vertical dotted lines on the left and right sides, and the text '10 octets' and 'Layer 2 frame' is centered.](f9528ea5b0d2cd0192b7242e5a6af969_img.jpg) + +Figure 7.9b.2: EC-PACCH downlink block format diagram. The diagram shows a rectangular block representing 10 octets. Above the block, a horizontal arrow points left, with numbers 8, 7, 6, 5, 4, 3, 2, 1 above it. The top of the block is labeled 'Octet 1' and the bottom is labeled 'Octet 10'. Inside the block, there are vertical dotted lines on the left and right sides, and the text '10 octets' and 'Layer 2 frame' is centered. + +**Figure 7.9b.2: EC-PACCH downlink block format** + +A 3-bit USF may optionally be added to the block. A different USF value may be included in each block when several blind physical layer transmissions are used in the downlink (i.e. for EC-PACCH/D/4, EC-PACCH/D/8 and EC-PACCH/D/16). + +#### 7.9b.4.2 Uplink + +The 8 octets block is used in the uplink in the way shown in figure 7.9b.3. + +![Diagram of EC-PACCH uplink block format showing 8 octets (Octet 1 to Octet 8) with a Layer 2 frame in the center. A horizontal arrow at the top points from right to left, indicating bit transmission order from bit 1 to bit 8.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram illustrates the EC-PACCH uplink block format. It consists of 8 octets, labeled Octet 1 at the top and Octet 8 at the bottom. A central box labeled 'Layer 2 frame' contains '8 octets'. Above the octets, a horizontal arrow points from right to left, with bits numbered 8, 7, 6, 5, 4, 3, 2, 1 from left to right, indicating the transmission order. + +Diagram of EC-PACCH uplink block format showing 8 octets (Octet 1 to Octet 8) with a Layer 2 frame in the center. A horizontal arrow at the top points from right to left, indicating bit transmission order from bit 1 to bit 8. + +**Figure 7.9b.3: EC-PACCH uplink block format** + +If the EC-PACCH is transmitted using Access Bursts, it is referred to as EC-PACCH short acknowledgement block format and follows the format described in subclause 7.7 for the 11-bit RLC/MAC block. + +## 7.10 Order of bit transmission + +On channels for normal burst transmission having a block format with an integer N number of octets, the N octets are mapped onto 8N bits, d(0) to d(8N-1), defined in 3GPP TS 45.003 clause 4 and 5 as follows: + +Bit m of octet n shall be transmitted as bit $d((n-1)*8+m-1)$ with $m=(1..8)$ and $n=(1..N)$ . + +On channels for normal burst transmission having a block format with a non-integer number of octets, or for transmission having a defined block format but which does not follow the normal burst transmission, the octets are mapped onto M bits, d(0) to d(M-1), defined in 3GPP TS 45.003 clause 5 as follows: + +Bit m of octet n shall be transmitted as bit $d(8(n-1) + m-1)$ with $n = (1 .. ((M-1) \text{ DIV } 8) + 1)$ and $m = (1 .. \min(8, (M - 8(n-1))))$ , and where 'DIV' is the integer division operator. + +# 8 Vocabulary + +The terminology used in the present document is as follows: + +states packet idle mode and packet transfer mode(see 3GPP TS 44.060). When the MS is operating in *Iu mode*, packet mode includes the sub-states MAC-Idle and MAC-Shared. + +### - **Packet Idle Mode:** + +In packet idle mode, the mobile station is prepared to transfer LLC PDUs on packet data physical channels. The mobile station is not allocated any radio resource on a packet data physical channel; it listens to the PBCCH and PCCCH or, if those are not provided by the network, to the BCCH and the CCCH. + +### - **Packet Transfer Mode:** + +In packet transfer mode, the mobile station is prepared to transfer LLC PDUs on packet data physical channels. The mobile station is allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs. + +### - **Dual Transfer Mode:** + +In dual transfer mode, the mobile station is allocated radio resources providing an RR connection (3GPP TS 44.018) and a Temporary Block Flow on one or more packet data physical channels. The allocation of radio resource for the RR connection and the Temporary Block Flow is co-ordinated by the network in agreement with the capabilities of the mobile station in dual transfer mode. + +### - **MAC-dedicated:** + +A MAC-control-entity state where a DBPSCH is assigned and no SBPSCH is assigned. This state only applies in *Iu mode*. + +### - **MAC-DTM:** + +A MAC-control-entity state where at least one DBPSCH and one SBPSCH are assigned. This state only applies in *Iu mode*. + +### - **MAC-Idle:** + +A MAC-control-entity state where no basic physical subchannel is assigned. + +### - **MAC-Shared:** + +A MAC-control-entity state where at least one shared basic physical subchannel is assigned. + +### - **Physical block:** + +The physical block is the minimal unit which can be transferred by the physical layer. + +### - **Dedicated physical channel:** + +The physical blocks scheduled on the radio medium assigned to a dedicated connection with a MS. + +### - **Packet data physical channel:** + +The physical blocks scheduled on the radio medium assigned to a shared usage between MSs for packet switched data traffic. + +### - **Physical channel:** + +A **physical channel** uses a combination of frequency and time division multiplexing and is defined in terms of a radio frequency channel sequence and a timeslot sequence. A physical channel uses the same timeslot number in every TDMA frame. The complete definition of a particular physical channel consists of a description in the frequency domain, and a description in the time domain (see 3GPP TS 45.002). + +### - **Basic physical channel:** + +A **basic physical channel** is defined as a physical channel for which the TDMA frame number sequence is 0,1,.. FN\_MAX, where FN\_MAX is the maximum TDMA frame number for a hyperframe (i.e. all TDMA frames on a timeslot). + +### - **Basic physical subchannel:** + +A **basic physical subchannel** is defined as a basic physical channel or a part of a basic physical channel and an associated multiframe structure. A basic physical subchannel can either be shared or dedicated. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|-----------|------|-----|------------------------------------------------|--------| +| January 2015 | - | - | - | Rel-13 version created based on version 12.0.0 | 13.0.0 | +| GP-70 | GP-160291 | 0019 | | Introduction of EC-GSM-IoT | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2017-09 | RP-77 | RP-171597 | 0022 | - | A | Removal of references to TS 44.118 and TS 44.160 | 14.1.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44005/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/44_series/44005/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77c5b25c5d9b4b147a4d597e2aed6b4770123ba4 --- /dev/null +++ b/marked/Rel-16/44_series/44005/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2b3ae805a018ab386b8bd8f1b61840bca1e853129f0ddf4ed8731f9839896fa +size 93744 diff --git a/marked/Rel-16/44_series/44005/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-16/44_series/44005/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f33e9001ac2d52ee16f074c09d2e610f65a1e01 --- /dev/null +++ b/marked/Rel-16/44_series/44005/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e738242e578981fc25148d6b0c11c632b04c9669a1a6137f1bef6248f6e13ca5 +size 33873 diff --git a/marked/Rel-16/44_series/44005/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/44_series/44005/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57704e821e886600f71bacde1c24ce5ce7d03a6e --- /dev/null +++ b/marked/Rel-16/44_series/44005/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59466f0b23c335b36ed4ce345c0ac29e6c0177a51e8c0ef667cf7cf6fc85abef +size 68745 diff --git a/marked/Rel-16/44_series/44005/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/44_series/44005/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..357c95f071e07db7bd7d894c0b7fa60c7ad0c96c --- /dev/null +++ b/marked/Rel-16/44_series/44005/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45021102f65fd54dafbb3c528083126735516b80f938966b829dad8b6085261e +size 47469 diff --git a/marked/Rel-16/44_series/44005/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-16/44_series/44005/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9f71f73fd51b4699faf90e85658d84963a6ab20 --- /dev/null +++ b/marked/Rel-16/44_series/44005/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e2876101eee976313e8e10b5efa06e5f4617a36402e13e0333de5d5ef74acd9 +size 24003 diff --git a/marked/Rel-16/44_series/44005/raw.md b/marked/Rel-16/44_series/44005/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9c844087b293bb96adc86894904d99b218dc741b --- /dev/null +++ b/marked/Rel-16/44_series/44005/raw.md @@ -0,0 +1,615 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|-----------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 6 | +| 2a Concepts and terminology ..... | 7 | +| 3 Overview description of LAPDm functions and procedures ..... | 9 | +| 3.1 General ..... | 9 | +| 3.2 Unacknowledged operation..... | 10 | +| 3.3 Acknowledged operation..... | 10 | +| 3.4 Information transfer mode..... | 11 | +| 3.4.1 Information transfer on the BCCH ..... | 11 | +| 3.4.2 Information transfer on the PCH + AGCH..... | 11 | +| 3.4.3 Information transfer on the DCCHs ..... | 11 | +| 3.5 Release of data links..... | 11 | +| 4 Service characteristics..... | 11 | +| 4.1 General ..... | 11 | +| 4.2 Services provided to layer 3 ..... | 11 | +| 4.2.1 General ..... | 11 | +| 4.2.2 Priority ..... | 12 | +| 4.2.3 Segmentation ..... | 12 | +| 4.2.4 Unacknowledged information transfer service..... | 12 | +| 4.2.5 Acknowledged information transfer services ..... | 12 | +| 4.2.6 Random access procedure ..... | 14 | +| 4.3 Services required from the physical layer..... | 14 | +| 4.4 Administrative services..... | 15 | +| 4.4.1 General description of administrative services..... | 15 | +| 4.4.2 Definition of primitives for administrative services..... | 15 | +| 5 Overview of data link layer structure..... | 15 | +| 5.1 Functional composition..... | 15 | +| 5.2 Identification of data link end points..... | 16 | +| 5.3 Data link procedure ..... | 16 | +| 5.4 Data link distribution procedure..... | 16 | +| 5.5 Random access procedures..... | 17 | +| 6 Specific requirements..... | 17 | +| 6.1 Mode of operation and allowed SAPIs ..... | 17 | +| 6.2 Acknowledged mode of operation ..... | 18 | +| 6.2.1 Window size ..... | 18 | +| 6.2.2 Processing capacity ..... | 18 | +| Annex A (informative): Change History..... | 19 | + +# --- 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 in general terms the Link Access Procedures on the Dm channel, LAPDm. The application of this protocol to other channel types is for further study. Details are provided in 3GPP TS 44.006. + +The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface (MS to network interface) using the Dm channel. + +NOTE 1: The term Dm channel is used for convenience to designate the collection of all the various signalling channels required in the GSM system. See also 3GPP TS 44.003. + +The definition of LAPDm is based on the principles and terminology of: + +- ITU-T Recommendations X.200 and X.210: the reference model for Open Systems Interconnection (OSI); +- ITU-T Recommendations Q.920 and Q.921: the specification of LAPD for the user-network interface in ISDN; +- ITU-T Recommendation X.25 LAPB: user-network interface for packet mode terminals; and +- ISO/IEC 3309 and ISO 4335: High-level Data Link Control (HDLC) standards for frame structure and elements of procedures. + +LAPDm is a protocol that operates at the data link layer of the OSI architecture. The relationship between the data link layer and other protocol layers is defined below. + +NOTE 2: The interface between the mobile station and external terminal equipment/terminal adapters is defined in the Technical Specifications of the GSM 07-series. + +NOTE 3: The physical layer on the radio interface is defined in 3GPP TS 44.004 and layer 3 is defined in 3GPP TS 24.007, 3GPP TS 44.018, 3GPP TS 24.010 and 3GPP TS 24.011. Reference should be made to these Technical Specifications for the complete definitions of the protocols and procedures across the GSM PLMN radio interface. + +NOTE 4: The term "data link layer" is used in the main text of the present document. However, mainly in figures and tables, the terms "layer 2" and "L2" are used abbreviations. Furthermore, in accordance with 3GPP TS 24.007 and 3GPP TS 44.018 the term "layer 3" is used to indicate the layer above the data link layer. + +LAPDm is independent of the transmission bit rate. It requires physical channels with characteristics as defined in 3GPP TS 44.003. + +Clause 2 below describes basic concepts used in the present document and 3GPP TS 44.006. + +Clause 3 gives an overview description of LAPDm functions and procedures. + +Clause 4 summarizes the services that the data link layer provides to layer 3 and the services that the data link layer requires from the physical layer. + +Clause 5 provides an overview of the data link layer structure. + +# --- 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 44.001: "Mobile Station - Base Station System (MS - BSS) Interface General Aspects and Principles". +- [3] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) Interface Channel Structures and Access Capabilities". +- [4] 3GPP TS 44.004: "Layer 1; General requirements". +- [5] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". +- [6] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [7] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [8] 3GPP TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General aspects". +- [9] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [10] (void). +- [11] (void). +- [12] (void). +- [13] (void). +- [14] (void). +- [15] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". +- [16] ITU-T Recommendation X.200: "Information technology - Open Systems Interconnection - Basic Reference Model: The basic model". +- [17] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic Reference Model: Conventions for the definition of OSI services". +- [18] ITU-T Recommendation Q.920: "ISDN user-network interface data link layer - General aspects". +- [19] ITU-T Recommendation Q.921: "ISDN user-network interface - Data link layer specification". +- [20] ISO/IEC 3309: "Information technology - Telecommunications and information exchange between systems - High-level Data Link Control (HDLC) procedures - Frame structure". +- [21] ISO/IEC 4335: "Information technology - Telecommunications and information exchange between systems - High-level Data Link Control (HDLC) procedures - Elements of procedures". + +# --- 2a Concepts and terminology + +The general layering principles used in the present document and other specifications in the 44 series are given in 3GPP TS 44.001. + +The data link layer is the next to lowest layer of the OSI reference model. The data link layer receives services from the physical layer and provides services to layer 3. + +The services provided by the data link layer are the combination of the services and functions provided by both the data link layer and the physical layer. + +A data link layer Service Access Point (SAP) is the point at which the data link layer provides services to layer 3. The Service Access Point is identified by a Service Access Point Identifier (SAPI). One or more data link connection + +endpoints can be associated with each data link layer SAP. See figure 1. A data link connection endpoint is identified by a data link connection endpoint identifier (as seen from layer 3) and by a Data Link Connection Identifier DLCI (as seen from the data link layer). + +SAPIs and DLCIs used by LAPDm are defined in subclause 5.2. + +![Figure 1: Entities, service access points and endpoints. This diagram shows a 'Layer 3 entity' box at the top connected by a vertical line to a horizontal line labeled 'Datalink layer service access point'. Below this line is an asterisk (*). Another vertical line descends from the asterisk to a horizontal line labeled 'Datalink connection endpoint'. Below this line is a 'Datalink layer entity' box. To the left of the 'Datalink layer entity' box is the text 'Datalink layer'.](d793cf7c174b89eb024d132f00679787_img.jpg) + +Figure 1: Entities, service access points and endpoints. This diagram shows a 'Layer 3 entity' box at the top connected by a vertical line to a horizontal line labeled 'Datalink layer service access point'. Below this line is an asterisk (\*). Another vertical line descends from the asterisk to a horizontal line labeled 'Datalink connection endpoint'. Below this line is a 'Datalink layer entity' box. To the left of the 'Datalink layer entity' box is the text 'Datalink layer'. + +**Figure 1: Entities, service access points and endpoints** + +Co-operation between data link layer entities is governed by a peer-to-peer protocol specific to the layer. For information exchange between two or more layer 3 entities, an association must be established between the layer 3 entities in the data link layer using a data link layer protocol. This association is called a data link connection. Data link connections are provided by the data link layer between two or more SAPs (see figure 2). + +![Figure 2: Peer-to-peer relationship. This diagram shows two 'Layer 3 entity' boxes, one on the left and one on the right. Each is connected by a vertical line to a horizontal line labeled 'Datalink layer service access point'. Below each SAP is a 'Datalink connection endpoint' (represented by a small box with an X). From each DCE, a series of small arrows point downwards. A horizontal line connects the two DCEs, labeled 'Datalink relationship'.](9791722d75115ddcc599b07d7bc35d73_img.jpg) + +Figure 2: Peer-to-peer relationship. This diagram shows two 'Layer 3 entity' boxes, one on the left and one on the right. Each is connected by a vertical line to a horizontal line labeled 'Datalink layer service access point'. Below each SAP is a 'Datalink connection endpoint' (represented by a small box with an X). From each DCE, a series of small arrows point downwards. A horizontal line connects the two DCEs, labeled 'Datalink relationship'. + +**Figure 2: Peer-to-peer relationship** + +Data link layer message units are conveyed between data link layer entities by means of physical connection. + +Layer 3 requests services from the data link layer via service primitives. The same applies for the interaction between the data link layer and the physical layer. The primitives represent, in an abstract way, the logical exchange of information and control between the data link layer and its adjacent layers. They do not specify or constrain implementations. + +The primitives that are exchanged between the data link layer and adjacent layers are of the following four types (see also figure 3). + +![Figure 3: Primitive action sequence diagram showing Layer 3, SAP, and Data link layer interactions.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the primitive action sequence between Layer 3 and the Data link layer. It consists of two vertical timelines representing the entities. The left timeline shows a 'Request' primitive from Layer 3 to the SAP, followed by a 'Confirm' primitive from the SAP back to Layer 3. The right timeline shows an 'Indication' primitive from the SAP to Layer 3, followed by a 'Response' primitive from Layer 3 back to the SAP. Both timelines pass through a central diamond-shaped SAP (Service Access Point) marked with an asterisk (\*). Below the SAP, the 'Data link layer' is shown as a box. A dashed line connects the Data link layer box on the left to a box on the right, labeled 'Layer 2 peer-to-peer protocol'. A callout line points to this dashed line. + +Figure 3: Primitive action sequence diagram showing Layer 3, SAP, and Data link layer interactions. + +NOTE: The same principle applies for data link layer-physical layer interactions. + +**Figure 3: Primitive action sequence** + +The REQUEST primitive type is used when a higher layer is requesting a service from the next lower layer. + +The INDICATION primitive type is used by a layer providing a service to notify the next higher layer of activities related to the primitive type REQUEST. + +The RESPONSE primitive type is used by a layer to acknowledge receipt, from a lower layer, of the primitive type INDICATION. + +The CONFIRM primitive type is used by the layer providing the requested service to confirm that the activity has been completed. + +The precise specification of Layer-to-layer interactions is given in 3GPP TS 44.006. + +Information between peer entities and between entities in adjacent layers attached to the same SAP is transferred in two different types of message units: + +- message units of a peer-to-peer protocol; and +- message units that contain layer-to-layer information concerning status and specialized service requests. + +The message units of the layer 3 peer-to-peer protocol are carried by the data link connection. The message units containing layer-to-layer information concerning status and specialized service requests are never conveyed over a data link connection or a physical connection. + +The present document introduces (see also figure 4): + +- a) the peer-to-peer protocol for the transfer of information and control between any pair of data link layer service access points; +- b) the interactions between the data link layer and layer 3, and between the data link layer and the physical layer. + +![Figure 4: Data link layer reference model diagram showing the interaction between Layer 3, Datalink layer, and Physical layer entities across a radio interface.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the Data link layer reference model across a radio interface. On the left (Network side), a 'Layer 3 entity' is connected to a 'Datalink layer entity' via 'Datalink layer/service access point' and 'Datalink layer/layer 3 primitives'. The 'Datalink layer entity' is connected to a 'Physical layer entity' via 'Datalink layer/service access point' and 'Datalink layer/physical layer primitives'. On the right (Mobile Station side), a 'Layer 3 entity' is connected to a 'Datalink layer entity' via 'Datalink layer/service access point'. The 'Datalink layer entity' is connected to a 'Physical layer entity' via 'Physical layer/service access point'. A dashed line between the two 'Datalink layer entities' represents the 'Datalink layer peer-to-peer protocol'. A solid line at the bottom between the two 'Physical layer entities' represents the 'Physical connection'. + +Figure 4: Data link layer reference model diagram showing the interaction between Layer 3, Datalink layer, and Physical layer entities across a radio interface. + +Figure 4: Data link layer reference model + +# 3 Overview description of LAPDm functions and procedures + +## 3.1 General + +The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface using the Dm channel. Specifically LAPDm will support: + +- multiple layer 3 entities; +- multiple physical layer entities; +- broadcast control channel (BCCH) signalling; +- paging channel (PCH) signalling; +- access grant channel (AGCH) signalling; +- dedicated control channel (DCCH) signalling. + +NOTE 1: The term "DCCH" designates a number of control channels (SDCCH, FACCH and SACCH) as defined in 3GPP TS 44.003. + +NOTE 2: The random access channel (RACH) does not utilise LAPDm. However, for the purpose of specification, the data link layer acts as a protocol interface between layer 3 and the physical layer also for random access. + +The frame structure of data link layer messages is defined in 3GPP TS 44.006. + +The Dm channel between a network and a specific MS may be distorted on several control channels, e.g. PCH, SDCCH and FACCH during a connection (See also 3GPP TS 44.003). Selection and activation of these channels is performed by layer 3. + +LAPDm includes functions for: + +- a) the provision of one or more data link connections on a Dm channel. Discrimination between the data link connections is by means of a Data Link Connection Identifier (DLCI); +- b) allowing recognition of frame types; +- c) allowing layer 3 message units to be passed transparently between layer 3 entities; +- d) sequence control, to maintain the sequential order of frames across a data link connections; +- e) detection of format and operational errors on a data link; +- f) notification to the layer 3 entity of unrecoverable errors; + +NOTE 3: It is in the responsibility of layer 3 entity to recover from these errors. + +- g) flow control; and +- h) contention resolution when establishing a data link after an access request has been made on the RACH. + +Two types of operation of the data link layer are defined for layer 3 information transfer: unacknowledged operation and acknowledged (multiple frame) operation. They may co-exist on a Dm channel. + +The BCCH and the (PCH + AGCH) will only support unacknowledged operation. The SDCCH, SACCH and FACCH will support both types of operation. + +## 3.2 Unacknowledged operation + +In unacknowledged operation, layer 3 information is transmitted in Unnumbered Information (UI) frames. + +At the data link layer, the UI frames are not acknowledged. Flow control mechanisms and error recovery mechanisms are not defined. + +Applicability of unacknowledged operation to different types of control channels is specified in subclause 6.1. + +## 3.3 Acknowledged operation + +In acknowledged operation, layer 3 information is transmitted in frames that are acknowledged by the receiving data link layer. + +Error recovery procedures based on retransmission of unacknowledged frames are specified. In case of errors which cannot be corrected by the data link layer, a report is issued to the layer 3 entity. Flow control procedures are also defined. + +Applicability of acknowledged operation to different types of control channels is specified in subclause 6.1. + +Only one form of acknowledged information transfer is defined, i.e. multiple frame operation. + +For multiple frame operation, layer 3 information is sent in numbered Information (I) frames. In principle, a number of I frames may be outstanding at the same time. However, for many applications (e.g. signalling) a window size of 1 is required. Multiple frame operation is initiated by a multiple frame establishment procedure using a Set Asynchronous Balanced Mode (SABM) command. + +If an access request has been made on the RACH, the establishment procedure also contains functions for resolving any ambiguity that may arise as a result of this access method. + +## 3.4 Information transfer mode + +### 3.4.1 Information transfer on the BCCH + +The BCCH exists only in the network to MS direction and is used for broadcasting radio sub-system information to MSs. Only UI frames are sent on the BCCH. + +### 3.4.2 Information transfer on the PCH + AGCH + +These channels exist only in the network to MS direction. On the PCH + AGCH only unacknowledged operation is possible. + +### 3.4.3 Information transfer on the DCCHs + +On the DCCHs both unacknowledged operation and multiple frame operation are possible (see subclause 6.1). The type of operation required at any time is determined by layer 3. + +## 3.5 Release of data links + +Multiple frame operation may be released in the following ways: + +- normal release by exchange of commands/responses. This type of release is initiated by layer 3; +- local end release, i.e. without exchange of commands/responses, initiated and controlled by layer 3; +- abnormal local end release, i.e. without exchange of commands/responses, commanded by layer 3. + +The release mode is indicated by layer 3. + +No release mechanism using exchange of commands/responses is defined for unacknowledged operation. + +# --- 4 Service characteristics + +## 4.1 General + +The data link layer provides services to layer 3 and utilizes the services provided by the physical layer. + +In the present document and 3GPP TS 44.006 the following general syntax is used for describing primitives. + +XX - Generic Name - Type (Parameters). + +where XX designates the layer providing the services. In the present document XX is DL and MDL for the data link layer and PH for the physical layer. + +## 4.2 Services provided to layer 3 + +### 4.2.1 General + +The specification of the interactions with layer 3 (primitives) provides a description of the services that the data link layer, plus the physical layer, offer to layer 3, as viewed from layer 3. + +Two forms of information transfer services are associated with layer 3. The first is based on unacknowledged information transfer at the data link layer and the second service is based on acknowledged information transfer at the data link layer using multiple frame operation. Different information transfer services may co-exist on the same data link subject to restrictions imposed by the type of channel being used (see subclause 3.4). + +In addition, the data link layer will pass primitives between the physical layer and layer 3 for random access operation on the RACH. + +### 4.2.2 Priority + +The priority between data links shall be as follows: + +On SDCCH: + +Highest priority: SAPI = 0; + +Lowest priority : SAPI = 3. + +On SACCH: + +The priority arrangement on the SACCH must ensure that if a SAPI = 3 frame is awaiting transmission, two SAPI = 0 frames are not sent in consecutive SACCH frames. An exception is when Repeated SACCH is supported, where a SACCH block containing a SAPI = 0 frame may be repeated in the next SACCH period (see 3GPP TS 44.006). In addition, for the mobile to network direction it must also be ensured that any SAPI = 3 frame is followed by at least one SAPI = 0 frame. + +### 4.2.3 Segmentation + +For the acknowledged mode of information transfer the data link layer offers segmentation at the transmitter of layer 3 message units if the message unit is longer than the information field of the data layer frames. At the receiver the segmented layer 3 message units are concatenated such that the integrity of the layer 3 message unit is restored. + +For unacknowledged operation the data link layer does not offer segmentation services. + +### 4.2.4 Unacknowledged information transfer service + +NOTE: In this case the information transfer is not acknowledged at the data link layer. Acknowledgement procedures may be provided at higher layers. + +The characteristics of the unacknowledged information transfer service are summarized in the following: + +- a) provision of a data link connection between layer 3 entities for unacknowledged information transfer of layer 3 message units; +- b) identification of data link connection endpoints to permit a layer 3 entity to identify another layer 3 entity; +- c) sending of frames in accordance with priority given to the message; +- d) no verification of message arrival within the data link layer. + +The primitives associated with the unacknowledged information transfer service are: + +DL-UNIT DATA-REQUEST/INDICATION + +The DL-UNIT DATA-REQUEST primitive is used to request that a message unit be sent using the procedures for unacknowledged information transfer service; DL-UNIT DATA-INDICATION indicates the arrival of a message unit received by means of unacknowledged information transfer. Parameters associated with these primitives are the message unit, priority and the type of channel being used (BCCH, PCH + AGCH or specific type of DCCH). + +### 4.2.5 Acknowledged information transfer services + +One mode of acknowledged operation is defined, i.e. multiple frame operation. + +The characteristics of this service are summarized in the following: + +- a) provision of a data link connection between layer 3 entities for acknowledged information transfer of layer 3 message units; +- b) identification of data link connection endpoints to permit a layer 3 entity to identify another layer 3 entity; +- c) sequence integrity of data link layer message units in the absence of machine malfunctions; +- d) notification to the peer entity in the case of errors, for example, loss of sequence; +- e) notification to the layer 3 entity of unrecoverable errors detected by the data link layer; +- f) flow control; +- g) sending of frames in accordance with the indicated SAPI value (see also subclause 4.2.2); +- h) segmentation and concatenation control functions; +- i) suspension of the service during change of dedicated channels and resumption of service on the new channel without message loss (SAPI = 0 only); duplication of messages which may occur are treated on layer 3 (SAPI = 0 only). + +- j) prioritization of messages by a layer 3 entity with preemption of low priority messages by high priority messages (SAPI = 0 only). + +The following list gives an overview of the primitives associated with the multiple frame acknowledged information transfer services (for detailed specification, see 3GPP TS 44.006): + +- a) Data transfer using I frames: + +#### **DL-DATA-REQUEST/INDICATION** + +The DL-DATA-REQUEST primitive is used to request that a message unit be sent using the procedures for multiframe acknowledged information transfer. The DL-DATA- INDICATION primitive indicates the arrival of a message unit received by means of acknowledged information transfer. The parameters associated with these primitives are the message unit, the type of channel being used and, for a DL-DATA-REQUEST primitive, the message priority. + +- b) Establishment of multiple frame operation using the SABM command: + +#### **DL-ESTABLISH-REQUEST/INDICATION/CONFIRM** + +These primitives are used to request, indicate and confirm the establishment of multiple frame operation between two data link layer entities. Possible parameters are the message unit, the establish mode and the type of channel being used. + +- c) Suspension of multiple frame operation: + +#### **DL-SUSPEND-REQUEST/CONFIRM** + +These primitives are used in a MS to request and confirm the suspension of multiple frame operation while changing a dedicated channel. A possible parameter is the type of channel to be affected. + +- d) Resumption of multiple frame operation: + +#### **DL-RESUME-REQUEST/CONFIRM** + +These primitives are used in a MS to request and confirm the resumption of multiple frame operation after it has been suspended (see paragraph c) above). Possible parameters are the message unit and the type of channel to be affected. + +- e) Restoration of multiple frame operation: + +#### **DL-RECONNECT-REQUEST/CONFIRM** + +These primitives are used in a MS to request and confirm the restoration of multiple frame operation on the old channel after failure of the channel change. Possible parameters are the message unit and the type of channel to be affected. + +- f) Termination of multiple frame operation: + +#### **DL-RELEASE-REQUEST/INDICATION/CONFIRM** + +These primitives are used to request, indicate and confirm an attempt to terminate multiple frame operation between two data link layer entities or an attempt to perform local end release. The parameters associated with this primitive are the type of channel and the release mode. + +### 4.2.6 Random access procedure + +The primitives associated with random access are: + +#### **DL-RANDOM ACCESS-REQUEST/INDICATION/CONFIRM** + +The DL-RANDOM ACCESS-REQUEST primitive is used in the MS to request the transmission of a random access burst. The DL- RANDOM ACCESS-CONFIRM primitive is used to notify layer 3 that the random access burst has been sent. The DL-RANDOM ACCESS-INDICATION primitive is used in the network to indicate the arrival of a random access burst. The parameter associated with the REQUEST primitives is the random access message unit. The parameters associated with the INDICATION primitive are the random access message unit and the time slot in which + +the random access burst was received. The parameter associated with the CONFIRM primitive is a message unit containing the number of the time slot in which the random access burst was sent. + +## 4.3 Services required from the physical layer + +The services provided by the physical layer are described in detail in 3GPP TS 44.004. They are summarized in the following: + +- a) physical layer connection for transparent transmission of frames. The bits of a frame are to be delivered to the peer data link entity in the same order in which they were submitted to the physical layer by the sender; +- b) indication of the physical status of the Dm channel; +- c) transmission of data link layer message units in the same order as they were issued by the data link layer; +- d) provision of frame synchronization; +- e) provision of error protection to ensure a low residual bit error rate at the data link layer; +- f) transmission (in the MS) and reception (in the network) of random access bursts. + +The primitives between the data link layer and the physical layer are: + +- a) Data transfer: + +#### PH-DATA-REQUEST/INDICATION + +These primitives are used to request that a message unit be sent and to indicate the arrival of message unit. Parameters associated with these primitives are the data link layer message unit, the priority and the type of channel being used. + +- b) Random access: + +#### PH-RANDOM ACCESS-REQUEST/INDICATION/CONFIRM + +The REQUEST primitive is used to request (in the MS) that a random access frame be sent and the INDICATION primitive is used to indicate (in the network) the arrival of a random access frame. A parameter associated with these primitives is the random access message unit. The CONFIRM primitive is used (in the MS) to confirm in which time slot the random access burst was sent. + +- c) Connection establishment: + +#### PH-CONNECT-INDICATION + +This primitive is used to indicate that a specific physical resource has been established on the physical layer. The parameter associated with this primitive is the type of channel. + +NOTE: Activation of a physical resource is usually initiated by the layer 3 entity without involving data link layer entities. + +- d) Transmission synchronization: + +#### PH-READY-TO-SEND-INDICATION + +This primitive is used to enable the data link layer to synchronize to the next instant of physical transmission. The parameter associated with this primitive is the type of channel. + +#### PH-EMPTY-FRAME-REQUEST + +This primitive is used by the data link layer instead of the PH-DATA-REQUEST primitive when no frame has to be sent after receiving the PH-READY-TO-SEND indication. The parameter associated with this primitive is the type of channel. + +## 4.4 Administrative services + +### 4.4.1 General description of administrative services + +The data link layer entity supports several internal functions of the MS or the network not requiring layer 3 peer-to-peer information transfer. The functions provided by the data link layer are: + +- error reporting between the data link layer and the layer 3 entity; +- abnormal release of the data link layer in case of protocol or other failures from which the data link layer cannot recover on its own. + +The administrative functions and the interactions between the data link layer and the layer 3 entities are described in terms of service primitives. + +### 4.4.2 Definition of primitives for administrative services + +The primitives between the layer 3 entity and the data link layer for supporting administrative services are: + +- a) Error handling: + +MDL-ERROR-INDICATION + +This primitive is used by the data link layer to indicate that there is an error in the data link layer procedures that cannot be resolved by normal exception handling procedures. Parameters associated with this primitive are the reason for error reporting and the type of channel. + +- b) Release: + +MDL-RELEASE-REQUEST + +This primitive is used by the layer 3 entity to initiate abnormal local end release of a data link. Parameters associated with this primitive are indications of which data links are to be released and the reason for abnormal release. + +# --- 5 Overview of data link layer structure + +## 5.1 Functional composition + +Figure 5 is an example of a functional block diagram of the data link layer in the MS. In the example the data link connection for all physical channels terminates at the SAP identified by SAPI = 0 and the data link connection for a SACCH when associated with a TCH, or a SDCCH otherwise, terminates at the SAP identified by SAPI = 3. Other arrangements are possible depending on the capabilities of the MS. + +The network will contain a similar arrangement with one (PCH + AGCH), SDCCH, SACCH, as required, for each active MS. + +Figure 5 illustrates three procedural types: the data link procedure, the data link distribution procedure and the random access procedure. + +## 5.2 Identification of data link end points + +The data link endpoints are identified by a Data Link Connection Identifier (DLCI). + +The DLCI consists of two elements: + +- the Service Access Point Identifier (SAPI) which is carried in the address field of each frame; +- the type of control channel on which the data link connection is or is to be established. This information is not carried in frames between data link layer peer entities but is managed locally in each end system and is carried in primitives between the layers. + +When a layer 3 message unit is to be sent, layer 3 will select the appropriate SAP and data link connection end point. Layer 3 will indicate to the data link layer which data link connection end point has been chosen. + +When receiving a frame containing a layer 3 message unit, the data link layer will receive from the physical layer an indication concerning the type of channel on which the frame was received. This information together with the SAPI contained in the frame enables the data link layer to deliver the layer 3 message unit to the required data link connection end point of the indicated SAP. + +The SAP takes a specific value for each of the following functions carried on the Dm channel: + +- call control signalling, mobility management signalling, supplementary services signalling and radio resource management signalling information as defined in 3GPP TS 44.018 and 3GPP TS 24.010: SAPI = 0; +- short message services as defined in 3GPP TS 24.011: SAPI = 3. + +Other functions requiring specific SAPI values may be defined in the future. + +## 5.3 Data link procedure + +There is at most one instance of the data link layer procedure for each SAPI on each type of channel supported on that SAPI. + +For some combinations of SAPI and type of channel only a subset (e.g. unacknowledged operation) of the overall data link layer procedure is required. + +The procedure analyses the control field and the length indicator field of the received frame (see 3GPP TS 44.006) and provides appropriate peer-to-peer responses and layer-to-layer indications. In addition, it analyses the data link layer service primitives and transmits the appropriate peer-to-peer commands and responses. + +The procedure also performs segmentation and concatenation of layer 3 message units. + +## 5.4 Data link distribution procedure + +This procedure is only required if there are more than one SAPI supported on a channel associated with a specific MS. + +The procedure analyses the address field of a received frame and the type of physical channel contained in the primitive received from the physical layer. It then distributes the frames to the appropriate data link procedure block. + +On frame transmission, the procedure delivers the frames to the required channel after layer 3 has established the respective association between the channel and its physical parameters. The procedure also provides for resolution of conflicts between the various data link procedure blocks on the same physical channel. The conflict resolution is based on the SAPI and the priority requested by layer 3 (see also note to subclause 4.2.2). + +## 5.5 Random access procedures + +This procedure is used for data links on the random access channel (RACH). The procedure in the MS formats the random access frames and initiates transmission of them. The procedure in the network receives the random access frames and provides the appropriate indication to layer 3. + +![Diagram of data link layer configuration in the MS showing SAPI 0 and SAPI 3 configurations.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates the data link layer configuration in the MS (Mobile Station). It shows two main configurations for SAPI (Service Access Point Identifier): SAPI = 0 and SAPI = 3. + +**SAPI = 0 Configuration:** This configuration includes six data link processing blocks: + + +- Data link proc. Random access +- Data link proc. (UI) +- Data link proc. (UI) +- Data link proc. (MF + UI) +- Data link proc. (MF + UI) +- Data link proc. (UI) + + The first four blocks are connected to physical channels: RACH, BCCH, PCH + AGCH, and FACCH respectively. The last two blocks are connected to a 'Data link Distribution procedure' block, which is then connected to the SACCH channel. + +**SAPI = 3 Configuration:** This configuration includes two data link processing blocks: + + +- Data link proc. (MF + UI) +- Data link proc. (MF) + + Both blocks are connected to a 'Data link Distribution procedure' block, which is then connected to the SDCCH channel. + +The diagram also shows the hierarchy of layers: layer 3 at the top, followed by the Data link layer, and the Physical layer at the bottom. The physical channels (RACH, BCCH, PCH + AGCH, FACCH, SACCH, SDCCH) are shown at the bottom, each connected to a physical layer interface (represented by a hexagon with an asterisk). + +Legend: + +- UI = unacknowledged +- MF = multiple frame + +Diagram of data link layer configuration in the MS showing SAPI 0 and SAPI 3 configurations. + +**Figure 5: Example of the data link layer configuration in the MS** + +# 6 Specific requirements + +## 6.1 Mode of operation and allowed SAPIs + +The various types of channels shall support SAPIs and modes of operation as follows. + +| Type of channel | SAPI = 0 | SAPI = 3 | +|-----------------------------|---------------------------------|---------------------------------| +| BCCH | Unacknowledged | Not supported | +| CCCH | Unacknowledged | Not supported | +| SDCCH | Unacknowledged and acknowledged | Acknowledged | +| SACCH associated with SDCCH | Unacknowledged | Not Supported | +| SACCH associated with TCH | Unacknowledged | Unacknowledged and Acknowledged | +| FACCH | Unacknowledged and acknowledged | Not supported | + +## 6.2 Acknowledged mode of operation + +### 6.2.1 Window size + +The window size, $k$ (see 3GPP TS 44.006), shall be: + +- for SAPI = 0, $k = 1$ ; + +- for SAPI = 3, k = 1. + +Other SAPIs, for further study. + +### 6.2.2 Processing capacity + +The processing capacity of the MS and the network shall be big enough to avoid that the data link layer entities enter the receiver busy state for SAPI = 0. + +# --- Annex A (informative): Change History + +| Date / Meeting | Doc | CR | Rev | Subject/Comment | New | +|----------------|-----|----|-----|------------------------------------|--------| +| January 2015 | - | - | - | Version 13 based on version 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|--------|----------|----|-----|-----|----------------------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | RP-75 | | | | | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | | | | | Release 15 version (frozen at TSG-80) | 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/44_series/44006/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/44_series/44006/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bba69f71b2075c31f865fb6e67c6708c919db44d --- /dev/null +++ b/marked/Rel-16/44_series/44006/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:421a840477354c43c7b35c0bdd05b1d3128aeb9a988d53f30a71b2cd676079ef +size 7043 diff --git a/marked/Rel-16/44_series/44006/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-16/44_series/44006/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1236de012c8a2745a26878d6f5f6859df3b827d1 --- /dev/null +++ b/marked/Rel-16/44_series/44006/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29b29f8e41dbec18ae6a1c24cd7b6018ec738841fc4c91e28f271416055818bc +size 13547 diff --git a/marked/Rel-16/44_series/44006/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/44_series/44006/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31ef3bc0e696958129a485fc3a941369825bb20a --- /dev/null +++ b/marked/Rel-16/44_series/44006/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e43f3f6bf8a3ab5cb24515382dca7d5f3b4bc250aa02e2f2b15a85fccebe07d4 +size 19972 diff --git a/marked/Rel-16/44_series/44006/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Rel-16/44_series/44006/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..508a08976a0dfa7cea247cab2bc414388c008acd --- /dev/null +++ b/marked/Rel-16/44_series/44006/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:900576c25a422cab288d10ef6986422bb9b091a0643f810d5eb09a83409c2c7f +size 23220 diff --git a/marked/Rel-16/44_series/44006/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/44_series/44006/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bb682aa9758cb885de67b1e0d6713bb42b716f1 --- /dev/null +++ b/marked/Rel-16/44_series/44006/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8448182d9cf7202fae049d5dc875d8f887004a0ec4df2a067f5be3732050d20d +size 33674 diff --git a/marked/Rel-16/44_series/44006/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/44_series/44006/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d449ad5ce0cedb9243acadd731142b8826313620 --- /dev/null +++ b/marked/Rel-16/44_series/44006/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:953ca5a22ba332f7ce918c3c7879541ff3b0a107b93d7299c0725f904764de4d +size 49990 diff --git a/marked/Rel-16/44_series/44006/b1296e107640b11ccb35d9c5fd989e2e_img.jpg b/marked/Rel-16/44_series/44006/b1296e107640b11ccb35d9c5fd989e2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..925906eeb1ac2d54e1360cb9975748a26fb2e346 --- /dev/null +++ b/marked/Rel-16/44_series/44006/b1296e107640b11ccb35d9c5fd989e2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f52c2248a3bb7c25cf2f22f07fc114cfcc68a67325ac65b26d21e1c98872f64 +size 16904 diff --git a/marked/Rel-16/44_series/44006/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/44_series/44006/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ae66191a923e5e43a0969698d229855772b1410 --- /dev/null +++ b/marked/Rel-16/44_series/44006/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cedb224305abf8e49195f3af6fddb37279844ce983e8e527fe2b4827e3fb54f5 +size 40833 diff --git a/marked/Rel-16/44_series/44006/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/44_series/44006/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf9f9307b48e54c50cc6b22a5c40ebe68b2be605 --- /dev/null +++ b/marked/Rel-16/44_series/44006/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eab0062b075122988d957c493343bf0da0aba72d91de306c15c9db68ef831d86 +size 45019 diff --git a/marked/Rel-16/44_series/44006/e76bcfd4d98252902daf991c9d26513b_img.jpg b/marked/Rel-16/44_series/44006/e76bcfd4d98252902daf991c9d26513b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14918afbcc74fd6e580fef830248d4b508fd2890 --- /dev/null +++ b/marked/Rel-16/44_series/44006/e76bcfd4d98252902daf991c9d26513b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc51334998edfda409106c160e8a3ec4b9f0a22c28c58218c338730efdd82d6f +size 8714 diff --git a/marked/Rel-16/44_series/44006/raw.md b/marked/Rel-16/44_series/44006/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..06a550156c6e9dc4b9cf4b9ea19fc19fb2d0c3c9 --- /dev/null +++ b/marked/Rel-16/44_series/44006/raw.md @@ -0,0 +1,2126 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Abbreviations ..... | 8 | +| 4 General ..... | 9 | +| 4.1 Options ..... | 9 | +| 5 Frame structure for peer-to-peer communication ..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Frame delimitation and fill bits ..... | 12 | +| 5.3 Address field ..... | 12 | +| 5.4 Control field ..... | 13 | +| 5.5 Length indicator field ..... | 13 | +| 5.5a Short L2 header type 1 ..... | 13 | +| 5.6 Information field ..... | 13 | +| 5.7 Transparency ..... | 13 | +| 5.8 Format convention..... | 13 | +| 5.8.1 Numbering convention ..... | 13 | +| 5.8.2 Order of bit transmission..... | 13 | +| 5.8.3 Field mapping convention ..... | 13 | +| 6 Elements of procedures and formats of fields for Data Link Layer peer-to-peer communication . | 14 | +| 6.1 General ..... | 14 | +| 6.2 Address field format..... | 14 | +| 6.3 Address field variables ..... | 15 | +| 6.3.1 Address field extension bit (EA) ..... | 15 | +| 6.3.2 Command/response field bit (C/R)..... | 15 | +| 6.3.3 Service access point identifier (SAPI)..... | 15 | +| 6.4 Control field formats ..... | 15 | +| 6.4.1 Information transfer format - I..... | 15 | +| 6.4.2 Supervisory format - S..... | 16 | +| 6.4.3 Unnumbered format - U ..... | 16 | +| 6.4a Short L2 header type 1 ..... | 16 | +| 6.5 Control field parameters and associated state variables..... | 16 | +| 6.5.1 Poll/Final bit ..... | 16 | +| 6.5.2 Multiple frame operation - variables and sequence numbers ..... | 17 | +| 6.5.2.1 Modulus ..... | 17 | +| 6.5.2.2 Send state variable V(S) ..... | 17 | +| 6.5.2.3 Acknowledge state variable V(A)..... | 17 | +| 6.5.2.4 Send sequence number N(S)..... | 17 | +| 6.5.2.5 Receive state variable V(R)..... | 17 | +| 6.5.2.6 Receive sequence number N(R) ..... | 17 | +| 6.5.2.7 Other parameters and variables..... | 18 | +| 6.5.3 Unacknowledged operation variables and parameters ..... | 18 | +| 6.6 Length indicator field format ..... | 18 | +| 6.7 Length indicator field variables..... | 18 | +| 6.7.1 Length indicator field extension bit (EL) ..... | 18 | +| 6.7.2 More data bit (M) ..... | 18 | +| 6.7.3 Length indicator (L) ..... | 18 | +| 6.8 Commands and responses ..... | 19 | +| 6.8.1 Information (I) commands..... | 19 | +| 6.8.2 Set asynchronous balanced mode (SABM) command ..... | 19 | +| 6.8.3 Disconnect (DISC) command..... | 20 | +| 6.8.4 Unnumbered information (UI) command..... | 20 | +| 6.8.5 Receive ready (RR) command/response..... | 20 | +| 6.8.6 Reject (REJ) command/response..... | 21 | +| 6.8.7 Receive not ready (RNR) command/response..... | 21 | + +| | | | +|-----------|----------------------------------------------------------------------------|----| +| 6.8.8 | Unnumbered acknowledgement (UA) response..... | 21 | +| 6.8.9 | Disconnected mode (DM) response ..... | 21 | +| 7 | Elements for layer-to-layer communication ..... | 22 | +| 7.1 | Definition of primitives and parameters..... | 22 | +| 7.1.1 | Generic names ..... | 22 | +| 7.1.1.1 | DL-ESTABLISH ..... | 22 | +| 7.1.1.2 | DL-RELEASE ..... | 22 | +| 7.1.1.3 | DL-DATA..... | 22 | +| 7.1.1.4 | DL-UNIT DATA ..... | 22 | +| 7.1.1.5 | DL-SUSPEND ..... | 22 | +| 7.1.1.6 | DL-RESUME..... | 22 | +| 7.1.1.7 | DL-RECONNECT ..... | 23 | +| 7.1.1.8 | DL-RANDOM ACCESS..... | 23 | +| 7.1.1.9 | MDL-RELEASE..... | 23 | +| 7.1.1.10 | MDL-ERROR..... | 23 | +| 7.1.1.11 | PH-DATA..... | 23 | +| 7.1.1.12 | PH-RANDOM ACCESS ..... | 23 | +| 7.1.1.13 | PH-CONNECT ..... | 23 | +| 7.1.1.14 | PH-READY-TO-SEND..... | 23 | +| 7.1.1.15 | PH-EMPTY-FRAME ..... | 23 | +| 7.1.2 | Primitives types ..... | 23 | +| 7.1.2.1 | REQUEST ..... | 24 | +| 7.1.2.2 | INDICATION ..... | 24 | +| 7.1.2.3 | RESPONSE ..... | 24 | +| 7.1.2.4 | CONFIRM ..... | 24 | +| 7.1.3 | Parameter definition ..... | 25 | +| 7.1.3.1 | Message unit ..... | 25 | +| 7.1.3.2 | Channel type ..... | 25 | +| 7.1.3.3 | Service Access Point..... | 25 | +| 7.1.3.4 | Release mode ..... | 25 | +| 7.1.3.5 | Error cause ..... | 25 | +| 7.1.3.6 | Establish mode..... | 26 | +| 7.1.3.7 | L2 header type ..... | 26 | +| 7.1.3.8 | Priority ..... | 26 | +| 7.2 | Primitive procedures ..... | 29 | +| 8 | Definition of the peer-to-peer protocol LAPDm..... | 29 | +| 8.1 | General ..... | 29 | +| 8.2 | General Protocol Procedures..... | 30 | +| 8.2.1 | Unacknowledged information transfer ..... | 30 | +| 8.2.2 | Acknowledged multiple frame information transfer ..... | 31 | +| 8.3 | Procedures for unacknowledged information transfer ..... | 31 | +| 8.3.1 | General ..... | 31 | +| 8.3.2 | Transmission of unacknowledged information ..... | 31 | +| 8.3.3 | Receipt of unacknowledged information..... | 31 | +| 8.4 | Procedures for establishment and release of multiple frame operation ..... | 32 | +| 8.4.1 | Establishment of multiple frame operation ..... | 32 | +| 8.4.1.1 | General..... | 32 | +| 8.4.1.2 | Normal establishment procedures..... | 32 | +| 8.4.1.3 | Procedure on expiry of timer T200: Normal establishment ..... | 33 | +| 8.4.1.4 | Contention resolution establishment procedure..... | 33 | +| 8.4.1.5 | Procedure on expiry of timer T200: contention resolution (MS only) ..... | 35 | +| 8.4.2 | Information transfer ..... | 35 | +| 8.4.2.1 | General requirements ..... | 35 | +| 8.4.2.2 | Error conditions ..... | 35 | +| 8.4.2.3 | Fill frames ..... | 36 | +| 8.4.3 | Suspension and resumption of multiple frame operation ..... | 37 | +| 8.4.3.1 | General..... | 37 | +| 8.4.3.2 | Suspension ..... | 37 | +| 8.4.3.3 | Resumption ..... | 38 | +| 8.4.3.3.1 | Procedure after channel change..... | 38 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------|----| +| 8.4.3.3.2 | Procedure after returning to the old channel (MS only)..... | 38 | +| 8.4.4 | Termination of multiple frame operation ..... | 39 | +| 8.4.4.1 | General..... | 39 | +| 8.4.4.2 | Normal release procedure ..... | 39 | +| 8.4.4.3 | Procedure on expiry of timer T200 for normal release..... | 39 | +| 8.4.4.4 | Local end release procedure ..... | 40 | +| 8.4.5 | Idle state..... | 40 | +| 8.4.6 | Collision of unnumbered commands and responses ..... | 40 | +| 8.4.6.1 | Identical transmitted and received commands..... | 40 | +| 8.4.6.2 | Different transmitted and received commands ..... | 41 | +| 8.4.6.3 | Unsolicited DM response and SABM or DISC command ..... | 41 | +| 8.5 | Procedures for information transfer in multiple frame operation ..... | 41 | +| 8.5.1 | Transmitting I frames ..... | 41 | +| 8.5.2 | Receiving I frames..... | 42 | +| 8.5.2.1 | P bit of the received I frame set to "1" ..... | 42 | +| 8.5.2.2 | P bit of the received I frame set to "0" ..... | 42 | +| 8.5.3 | Receiving acknowledgement..... | 43 | +| 8.5.3.1 | On receipt of a valid I frame..... | 43 | +| 8.5.3.2 | Receiving supervisory command frames with the P bit set to "1"..... | 43 | +| 8.5.4 | Receiving REJ frames ..... | 43 | +| 8.5.4.1 | Receipt of a valid REJ frame ..... | 43 | +| 8.5.4.2 | Transmitting frames..... | 44 | +| 8.5.5 | Receiving RNR frame ..... | 44 | +| 8.5.6 | Data link layer own receiver busy condition..... | 46 | +| 8.5.7 | Waiting acknowledgement..... | 46 | +| 8.5.8 | Preemption..... | 47 | +| 8.5.8.1 | Sender Requirements ..... | 47 | +| 8.5.8.2 | Receiver Requirements..... | 47 | +| 8.6 | Abnormal release and re-establishment of multiple frame operation ..... | 47 | +| 8.6.1 | Criteria for re-establishment..... | 47 | +| 8.6.2 | Criteria for abnormal release ..... | 47 | +| 8.6.3 | Procedures for re-establishment ..... | 48 | +| 8.6.4 | Procedures for abnormal release..... | 48 | +| 8.7 | Exception condition reporting and recovery for multiple frame operation..... | 48 | +| 8.7.1 | N(S) sequence error..... | 48 | +| 8.7.2 | Timer recovery ..... | 49 | +| 8.7.3 | Invalid frame condition ..... | 49 | +| 8.7.4 | N(R) sequence error ..... | 49 | +| 8.8 | List of system parameters..... | 50 | +| 8.8.1 | Timer T200..... | 50 | +| 8.8.1.1 | For SAPI=0 and SAPI=3 ..... | 50 | +| 8.8.1.2 | For SAPIs other than 0 or 3 ..... | 50 | +| 8.8.2 | Maximum number of retransmissions (N200) ..... | 50 | +| 8.8.2.1 | For SAPI=0 and 3 ..... | 50 | +| 8.8.2.2 | For SAPIs other than 0 or 3 ..... | 51 | +| 8.8.3 | Maximum number of octets in an I, UI, SABM and UA frame partially or entirely available for the information field (N201) ..... | 51 | +| 8.8.4 | Maximum number of outstanding I frames (k) ..... | 51 | +| 8.8.5 | Maximum number of octets in a Layer 3 message..... | 51 | +| 8.9 | System performance requirements ..... | 51 | +| 9 | Special protocol operation on SAPI=0 and SAPI=3 ..... | 52 | +| 10 | Repeated Downlink FACCH ..... | 53 | +| 10.1 | General ..... | 53 | +| 10.2 | The FACCH Repetition..... | 53 | +| 10.3 | BSS requirements..... | 53 | +| 10.4 | MS requirements ..... | 54 | +| 11 | Repeated SACCH ..... | 54 | +| 11.1 | General ..... | 54 | +| 11.2 | Procedure for Repeated SACCH on the downlink..... | 54 | +| 11.3 | Procedure for Repeated SACCH on the uplink..... | 54 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------|-----------| +| Annex A (normative): | Random access procedures..... | 56 | +| A.1 | Description of the procedure..... | 56 | +| A.1.1 | Procedure in the MS..... | 56 | +| A.1.2 | Procedure in the BS..... | 56 | +| A.2 | Format ..... | 56 | +| Annex G (normative): | Handling of frames with parameter errors in the address, control
and length indicator fields ..... | 57 | +| G.1 | General..... | 57 | +| G.2 | Parameter errors in the address field..... | 57 | +| G.2.1 | Unallocated SAPI..... | 57 | +| G.2.2 | Wrong value of the C/R bit ..... | 57 | +| G.2.3 | EA bit set to "0" ..... | 57 | +| G.3 | Parameter errors in the control field ..... | 58 | +| G.3.1 | Supervisory frames..... | 58 | +| G.3.2 | Unnumbered frames ..... | 58 | +| G.4 | Parameter errors in the length indicator field..... | 58 | +| G.4.1 | EL bit error ..... | 58 | +| G.4.2 | Information frames ..... | 58 | +| G.4.3 | Supervisory frames..... | 59 | +| G.4.4 | DISC and DM frames..... | 59 | +| G.4.5 | SABM UA and UI frames..... | 59 | +| Annex C (informative): | Change History..... | 60 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines a data link layer protocol to be used for signalling, and possibly also for other applications, on the MS-BS 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 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 44.001: "Mobile Station - Base Station System (MS - BSS) Interface General Aspects and Principles". +- [3] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface Channel structures and access capabilities". +- [4] 3GPP TS 44.004: "Layer 1 General requirements". +- [5] 3GPP TS 44.005: "Data Link (DL) layer General aspects". +- [6] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [7] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [8] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification; General aspects". +- [9] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [10] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [11] 3GPP TS 48.056: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification". +- [12] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification". +- [13] CCITT Recommendation Z.100: "Specification and description language (SDL)". + +# --- 3 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905. + +# --- 4 General + +The present document describes the frame structure, elements of procedure, format of fields and procedures for the proper operation of the Link Access Procedure on the Dm channel, LAPDm. + +NOTE 1: The term Dm channel is used for convenience to designate the collection of all the various signalling channels required in the GSM system. See also 3GPP TS 44.003. + +The concepts, terminology, overview description of LAPDm functions and procedures, and the relationship with other Technical Specifications are described in general terms in 3GPP TS 44.005. + +The frame formats defined for LAPDm are based on those defined for LAPD. However, there are important differences between LAPDm and LAPD, in particular with regard to frame delimitation methods and transparency mechanisms. These differences are necessary for operation within the constraints set by the radio path. + +LAPDm supports two modes of operation: + +- unacknowledged operation using UI frames; +- acknowledged operation using the multiple frame procedure. + +As a choice of implementation, the two modes of operation may be implemented independently of each other. This is possible since there is no interactions between the two modes, other than queuing at the transmitter, even when they coexist on the same physical channel. For BCCHs and CCCHs only the unacknowledged mode of operation needs to be implemented. + +LAPDm is used for information sent on the control channels BCCH, AGCH, NCH, PCH, FACCH, SACCH and SDCCH as defined in 3GPP TS 44.003. + +NOTE 2: AGCH, NCH and PCH are sometimes referred to by the collective name CCCH and FACCH, SACCH and SDCCH are, similarly, referred to by the collective name DCCH. + +LAPDm may also be used on other types of channel. + +NOTE 3: As stated in 3GPP TS 44.005, the term "data link layer" is used in the main text of this Technical Specification. However, mainly in figures and tables, the terms "layer 2" and "L2" are used as abbreviations. Furthermore, in accordance with 3GPP TS 24.007 and 3GPP TS 44.018, the term "layer 3" is used to indicate the layer above the data link layer. + +This Technical Specification is organized as follows: + +The frame structure for peer-to-peer communication is given in clause 5. The elements of procedure and formats of fields are given in clause 6. The elements of layer-to-layer communication are contained in clause 7. The details of the peer-to-peer procedures are given in clause 8. clause 6 summarizes the special protocol operations used mandatorily with SAPI=0 and SAPI = 3. + +The specification for the random access channel is contained in annex A, even though it is not a LAPDm function. The present document is descriptive and does not constrain the implementation of the random access function. The procedure is used for CHANNEL REQUEST on the RACH and HANDOVER ACCESS on the main DCCH. + +(Annexes B to F are deleted). + +Annex G gives an overview of actions taken on frames containing parameter errors. + +## 4.1 Options + +Support of short L2 header type 1 is an option in both the mobile station and the network; under certain conditions the support is mandatory, as specified in other Specifications. A layer 2 protocol entity not implementing short L2 header type 1 shall diagnose an E/A bit error and proceed as defined in annex G.2.3. + +# --- 5 Frame structure for peer-to-peer communication + +## 5.1 General + +All data link layer peer-to-peer exchanges are in frames conforming to one of the formats shown in figure 1. Several format types are shown in the figure: + +- Format A is used on DCCHs for frames where there is no information field. + +- Formats B, Bter and B4 are used on DCCHs for frames containing an information field: + - format Bter is used on request of higher layers if and only if short L2 header type 1 is supported and a UI command is to be transmitted on SAPI 0; + - format B4 is used for UI frames transmitted by the network on SACCH; + - format B is applied in all other cases. +- Format Bbis is used only on BCCH, PCH, NCH, and AGCH. +- In addition there is a Format C for transmission of random access signals. + +Format C frames are described in annex A. Format A, B, Bbis, Bter and B4 frames are described in the remainder of the present document. + +![Diagram of Format type A frame structure showing fields: Address field, Control field, Length indicator field, and Fill bits. Bit positions 8-1 are shown at the top. Octet numbers 1, k, k+1, k+2, n, n+1, and N201+n are shown on the right.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Format type A + +Diagram of Format type A frame structure showing fields: Address field, Control field, Length indicator field, and Fill bits. Bit positions 8-1 are shown at the top. Octet numbers 1, k, k+1, k+2, n, n+1, and N201+n are shown on the right. + +Figure 1 (sheet 1 of 3): General frame formats + +![Diagram of Format type B frame structure showing fields: Address field, Control field, Length indicator field, Information field, and Fill bits. Bit positions 8-1 are shown at the top. Octet numbers 1, k, k+1, k+2, n, n+1, N, N+1, and N201+n are shown on the right.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +Format type B + +Diagram of Format type B frame structure showing fields: Address field, Control field, Length indicator field, Information field, and Fill bits. Bit positions 8-1 are shown at the top. Octet numbers 1, k, k+1, k+2, n, n+1, N, N+1, and N201+n are shown on the right. + +![](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Bit      8      7      6      5      4      3      2      1 + +| | | | | | | | | | +|-------------------|--|--|--|--|--|--|--|---------------| +| Information field | | | | | | | | Octet No
1 | +| : | | | | | | | | : | +| : | | | | | | | | : | +| : | | | | | | | | N201 | + +**Format type Bbis** + +Figure 1 (sheet 2 of 3): General frame formats + +![](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Bit      8      7      6      5      4      3      2      1 + +| | | | | | | | | | +|-------------------|--|--|--|--|--|--|--|---------------| +| Address field | | | | | | | | Octet No
1 | +| : | | | | | | | | : | +| Control field | | | | | | | | k | +| Control field | | | | | | | | k+1 | +| Control field | | | | | | | | k+2 | +| Information field | | | | | | | | : | +| : | | | | | | | | N201 +
k+1 | + +**Format type B4** + +![](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +Bit      8      7      6      5      4      3      2      1 + +| | | | | | | | | | +|-------------------|--|--|--|--|--|---------------------------|--|---------------| +| | | | | | | short L2 header
type 1 | | Octet No
1 | +| Information field | | | | | | | | 2 | +| : | | | | | | | | : | +| : | | | | | | | | N201 | + +**Format type Bter** + +Figure 1 (sheet 3 of 3): General frame formats + +The parameter N201 is the maximum number of octets which are partially or entirely available for the information field of a frame. It depends on the type of channel and the format, see sub-clause 8.8.3. + +## 5.2 Frame delimitation and fill bits + +Frame delimitation is provided by the physical layer: + +- in format type A, B and B4 frames at the beginning of the frame for determining the start of the first octet in the address field, in format type Bter frames for determining the start of the octet containing the short L2 header type 1 (which is also the first octet used for the information field), and in format type Bbis frames for determining the start of the first octet for the information field; +- at the end of the frame for determining the last bit of the frame. + +The end of the useful part of the frame, i.e. the end of the length indicator field in type A frames and the end of the information field in type B frames, is determined by a length indicator contained in the length indicator field. The useful part of a Bbis frames takes all N201 octets of that frame. The useful part of a Bter frame takes all N201 octets of that frame except those bits of octet 1 which contain the short L2 header type 1. The useful part of a B4 frame takes all N201 octets of that frame except those octets which contain the address field and the control field. + +If a frame contains a length indicator that has a value less than N201, the frame contains fill bits. Each fill bit shall be set to a random value when sent by the mobile station. Except for the first octet containing fill bits which shall be set to the binary value "00101011", each fill bit should be set to a random value when sent by the network. Otherwise, the network shall set all octets containing fill bits to the binary value "00101011". + +## 5.3 Address field + +The address field may consist of a variable number of octets. However, for applications on control channels the field consists of only one octet. The address field identifies the SAP for which a command frame is intended and the SAP transmitting a response frame. The format of the address field is defined in sub-clause 6.2. + +## 5.4 Control field + +The control field consists of one octet. The format of the control field is defined in sub-clause 6.4. + +## 5.5 Length indicator field + +The length indicator field may consist of a variable number of octets. However, for applications on control channels the field consists of only one octet. The format of the field is defined in sub-clause 6.6. + +## 5.5a Short L2 header type 1 + +The short L2 header type 1 consists of two bits. Its contents are defined in sub-clause 6.4a. + +## 5.6 Information field + +The information field of a frame, when present, has the position in the frame defined in sub-clause 5.1. + +The maximum number of octets in the information field (N201) is defined in sub-clause 8.8.3. + +## 5.7 Transparency + +Because of the frame delimitation technique used (see sub-clause 5.2), the frame can include any possible sequence of bits without the need for additional transparency mechanisms. + +## 5.8 Format convention + +### 5.8.1 Numbering convention + +The basic convention used in this Technical Specification is illustrated in figure 2. The bits are grouped into octets. + +The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to n. + +![](b1296e107640b11ccb35d9c5fd989e2e_img.jpg) + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet no | +|-----|---|---|---|---|---|---|---|---|----------| +| | | | | | | | | | 1 | +| | | | | | | | | | 2 | +| | | | | | | | | | ; | +| | | | | | | | | | ; | +| | | | | | | | | | n | + +Figure 2: Format convention + +### 5.8.2 Order of bit transmission + +The order of bit transmission is defined in 3GPP TS 44.004. + +### 5.8.3 Field mapping convention + +When a field is contained within a single octet, the lowest bit number of the field represents the lowest order value. + +When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of the field contained in a given octet the lowest bit number represents the lowest order value. + +For example, a bit number can be identified as a couple (o, b) where o is the octet number and b is the relative bit number within the octet. Figure 3 illustrates a field that spans from bit (1, 3) to bit (2, 7). The high order bit of the field is mapped on bit (1, 3) and the low order bit is mapped on bit (2, 7). + +![](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|-----|---|---|---|---|---|---|---|---|-----------------|-----------------| +| | | | | | 4 | 3 | 2 | | 1st octet field | | +| | | | | | 2 | 2 | 2 | | | | +| | 1 | 0 | | | | | | | | 2nd octet field | +| | 2 | 2 | | | | | | | | | + +Figure 3: Field mapping convention + +# 6 Elements of procedures and formats of fields for Data Link Layer peer-to-peer communication + +## 6.1 General + +The elements of procedures define the commands and responses that are used on the data link connections carried on the Dm channel. + +Procedures are derived from these elements of procedures and are described in clause 8. + +If a bit position is marked as "spare", it shall be coded as "0". For future compatibility reasons, an entity receiving frames, where spare bit positions are coded otherwise, shall ignore those values without notification of any error. + +## 6.2 Address field format + +The field consists of: + +- the address field extension bit EA; +- the command/response bit C/R; +- the SAPI; +- and the Link Protocol Discriminator LPD. + +The format of the address field for control channels is shown in figure 4. + +The address field extension bit, EA, enables extension of the field to span more than one octet. The value "0" is used to indicate an extension, the value "1" shall be used for the final address field octet. + +The Link Protocol Discriminator (LPD) corresponding to the use in this Technical Specification shall take the value "0 0", all other values are reserved. + +NOTE: LPD = "0 1" corresponds to the data link protocol used for SMSCB (see 3GPP TS 44.012). + +![](e76bcfd4d98252902daf991c9d26513b_img.jpg) + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----|-------|---|-----|---|------|---|-----|----------| +| | Spare | | LPD | | SAPI | | C/R | EA
=1 | + +Figure 4: Address field format + +## 6.3 Address field variables + +### 6.3.1 Address field extension bit (EA) + +The address field range is extended by reserving the first transmitted bit of the address field octets to indicate the final octet of the address field. The presence of a "1" in the first bit of an address field octet signals that it is the final octet of the address field. Figure 4 shows the case where the field consists of one octet. + +### 6.3.2 Command/response field bit (C/R) + +The C/R bit identifies a frame as either a command or a response. The MS side shall send commands with the C/R bit set to "0", and responses with the C/R bit set to "1". The BS side shall do the opposite; that is commands are sent with C/R set to "1", and responses are sent with C/R set to "0". The combinations for the BS side and MS side are shown in table 1. + +**Table 1: C/R field bit usage** + +| Type | Direction | C/R value | +|----------|--------------------|-----------| +| Command | BS side to MS side | 1 | +| | MS side to BS side | 0 | +| Response | BS side to MS side | 0 | +| | MS side to BS side | 1 | + +### 6.3.3 Service access point identifier (SAPI) + +The service access point identifier (SAPI) identifies a point at which data link layer services are provided by the data link layer to a layer 3 entity (see 3GPP TS 44.005). The SAPI allows 8 service access points to be specified initially, where bit 3 of the address field octet containing the SAPI is the least significant binary digit and bit 5 is the most significant. + +The SAPI values are allocated as shown in table 2. + +**Table 2: Allocation of SAPI values** + +| SAPI value | Related entity | +|------------|----------------------------------------------------------------------------------------------------------------------------------| +| 0 | Call control signalling, mobility management signalling and radio resource management signalling (see 3GPP TS 44.018 and 24.010) | +| 3 | Short message service | +| All others | Reserved for future standardization | + +## 6.4 Control field formats + +The control field identifies the type of frame, which will be either a command or a response. The control field will contain sequence numbers, where applicable. + +Three types of control field formats are specified: numbered information transfer (I format), supervisory functions (S format), and unnumbered information transfer and control functions (U format). The control field formats for LAPDm are shown in table 3. + +### 6.4.1 Information transfer format - I + +The I format shall be used to perform an information transfer between layer 3 entities. The functions of N(S), N(R) and P are independent; that is, each I frame has an N(S) sequence number, an N(R) sequence number which may or may not acknowledge additional I frames received by the data link layer entity, and a P bit that may be set to "0" or "1". The use of N(S), N(R) and P is defined in sub-clause 8. + +### 6.4.2 Supervisory format - S + +The S format shall be used to perform data link supervisory control functions such as: acknowledge I frames, request retransmission of I frames, and request a temporary suspension of transmission of I frames. The functions of N(R) and P/F are independent; that is, each supervisory frame has an N(R) sequence number which may or may not acknowledge additional I frames received by the data link layer entity, and a P/F bit that may be set to "0" or "1". + +The use of N(R) and the P/F bit is described in sub-clause 8. + +### 6.4.3 Unnumbered format - U + +The U format shall be used to provide additional data link control functions and unacknowledged information transfer. + +This format does not contain sequence numbers. It does include a P/F bit that may be set to "0" or "1". + +**Table 3: Control field format** + +| Control field bits | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|---|------|---|-----|------|---|---|---| +| I format | | N(R) | | P | N(S) | | | 0 | +| S format | | N(R) | | P/F | S | S | 0 | | +| U format | U | U | U | P/F | U | U | 1 | 1 | + +N(S) Transmitter send sequence number. +N(R) Transmitter receive sequence number. +S Supervisory function bit. +U Unnumbered function bit. +P/F Poll bit, when issued as a command, final bit, when issued as a response. + +For definition of values for supervisory function bits and unnumbered function bits, see table 4. + +## 6.4a Short L2 header type 1 + +The short L2 header type 1 field is used in format Bter frames, see sub-clause 5.1. It consists of 2 bits, both shall take value 0. + +NOTE: Introduction of further short L2 header types (longer than 2 bits, setting bit 2 to "1" and bit 1 to "0") is for further study. + +The short L2 header type 1 implicitly defines a UI command frame belonging to SAPI=0, with length N201. All other parameters of a L2 frame header are irrelevant. + +## 6.5 Control field parameters and associated state variables + +The various parameters associated with the control field formats are described in this sub-clause. The coding of the bits within these parameters is such that the lowest numbered bit within the parameter field is the least significant bit. + +### 6.5.1 Poll/Final bit + +All frames contain P/F, the Poll/Final bit. The Poll/Final (P/F) bit serves a function in both command frames and response frames. In command frames the P/F bit is referred to as the P bit. In response frames it is referred to as the F bit. + +The P bit set to "1" is used by a data link layer entity to create (poll) a response frame from the peer data link layer entity. The F bit set to "1" is used by a data link layer entity to indicate the response frame transmitted as a result of a soliciting (poll) command. + +The use of the P/F bit is described in sub-clause 8. + +### 6.5.2 Multiple frame operation - variables and sequence numbers + +#### 6.5.2.1 Modulus + +Each I frame is sequentially numbered by a sequence number which may have the value 0 through 7. + +Arithmetics acting on variables which are related to such sequence numbers (i.e. N(S), N(R), V(S), V(R), V(A); see following sub-clauses) operate modulo 8. + +NOTE: Modulo 8 operation on negative numbers is performed by adding multiples of 8 to the negative number until the result becomes nonnegative. Then common modulo 8 operation is applied. + +#### 6.5.2.2 Send state variable V(S) + +Each point-to-point data link connection endpoint shall have an associated send state variable (V(S)) when using I frame commands. The send state variable denotes the sequence number of the next in-sequence I frame to be transmitted. + +The send state variable can take on the value 0 through 7. + +The value of the send state variable shall be incremented by 1 with each successive I frame transmission, and shall not exceed V(A) by more than the maximum number of outstanding I frames k (The window size k is defined in sub-clause 8.8.4.). The value of k may be in the range of $1 \leq k < 7$ . + +#### 6.5.2.3 Acknowledge state variable V(A) + +Each point-to-point data link connection endpoint shall have an associated acknowledge state variable (V(A)) when using I frame commands and supervisory frame commands/responses. + +The acknowledge state variable identifies the last frame that has been acknowledged by its peer (V(A) - 1 equals the N(S) of the last acknowledged I frame). The acknowledge state variable can take on the value 0 through 7. The value of the acknowledge state variable shall be updated by the valid N(R) values received from its peer (see 6.5.2.6). A valid N(R) value is one that is in the range $V(A) \leq N(R) \leq V(S)$ . + +NOTE: These inequalities shall be interpreted in the following way: + N(R) is called valid, if and only if $(N(R) - V(A)) \bmod 8 \leq (V(S) - V(A)) \bmod 8$ . + Furthermore, from sub-clause 6.5.2.2., it is obvious that $(V(S) - V(A)) \bmod 8 \leq k$ . + +#### 6.5.2.4 Send sequence number N(S) + +Only I frames contain N(S), the send sequence number of transmitted I frames. At the time that an in-sequence I frame is designated for transmission, the value of N(S) is set equal to the value of the send state variable V(S). + +#### 6.5.2.5 Receive state variable V(R) + +Each point-to-point data link connection endpoint shall have an associated receive state variable (V(R)) when using I frame commands and supervisory frame commands/responses. The receive state variable denotes the sequence number of the next in-sequence I frame expected to be received. The receive state variable can take on the value 0 through 7. + +The value of the receive state variable shall be incremented by one with the receipt of an error-free, in-sequence I frame whose send sequence number N(S) equals the receive state variable V(R). + +#### 6.5.2.6 Receive sequence number N(R) + +All I frames and supervisory frames contain N(R), the expected send sequence number of the next received I frame. + +At the time that a frame of the above types is designated for transmission, the value of N(R) is set equal to the current value of the receive state variable V(R). N(R) indicates that the data link layer entity transmitting the N(R) has correctly received all I frames numbered up to and including N(R) - 1. + +#### 6.5.2.7 Other parameters and variables + +For definition and values of parameters and variables such as timer T200, maximum number of retransmissions (N200), window size (k) and the maximum number of octets in an information field (N201), see sub-clause 8.8. + +### 6.5.3 Unacknowledged operation variables and parameters + +The only parameter defined for unacknowledged operation is the number of octets (N201) in the information field of the UI frame. See sub-clause 8.8.3. + +## 6.6 Length indicator field format + +The format of the length indicator field for control channels is shown in figure 5. + +The length indicator field extension bit, EL, enables extension of the field to span more than one octet. + +![](21ad58fee90f2be50708ff541d225507_img.jpg) + +| | | | | | | | | | +|-----|---|---|---|---|---|---|---|----------| +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| | L | | | | | | M | EL
=1 | + +Figure 5: Length indicator field format + +The field consists of the field extension bit, EL, the more data bit, M, and the length indicator, L. + +## 6.7 Length indicator field variables + +### 6.7.1 Length indicator field extension bit (EL) + +The length indicator field is extended by reserving the first transmitted bit of the length indicator field octets to indicate the final octet of the field. Presence of a "1" in the first bit of a length indicator field octet signals that it is the final octet of the field. Figure 5 shows the case where the field consists of one octet. + +### 6.7.2 More data bit (M) + +The more data bit, M, is used to indicate segmentation of layer 3 message units on data link layer frames. Layer 3 messages, which need to be segmented, shall only be transported by I-frames. + +When the M bit is set to "1", it indicates that the information field of the frame contains only a segment of the layer 3 message unit. + +The M bit set to "0" indicates: + +- that the information field contains a complete layer 3 message unit provided that the M bit of the previous frame was set to "0"; +- that the information field contains the last segment of a layer 3 message unit if the M bit of the previous frame was set to "1". + +When the M bit is set to "1", the information field shall contain the maximum number of octets, N201, that an information frame can contain, see sub-clause 8.8.3 for the value of N201. + +In frames other than information (I) frames the M bit shall be set to "0". + +### 6.7.3 Length indicator (L) + +The length indicator consists of 6 bits and is used to indicate the number of octets contained in the information field of UI, SABM, UA or I frames, i e any value from 0 to N201 inclusive. + +The L = 0 shall be used in frames not containing an information field. + +## 6.8 Commands and responses + +The following commands and responses are used by either the MS or the BS data link layer entities and are represented in table 4. Each data link connection supports the appropriate set of commands and responses for the type of operation desired (see sub-clause 8). + +For purposes of the LAPDm procedures, frames with the supervisory function bit encoding "11" and those encodings of the unnumbered function bits in table 3 not identified in table 4 are identified as "invalid or not implemented" command and response control fields and shall be treated as defined in sub-clause 8.7.3. + +The commands and responses in table 4 are defined as follows. + +### 6.8.1 Information (I) commands + +The function of the information (I) command is to transfer, across a data link connection, sequentially numbered frames containing information fields provided by layer 3. This command is used in the multiple frame operation. + +**Table 4: Commands and responses - unacknowledged and multiple frame acknowledged operation** + +| Format | Commands | Responses | 8 7 6 5 4 3 2 1 | | | | +|----------------------|---------------------------------------|------------------------------|-----------------|-----|---------|-----| +| | | | N ( R ) | P | N ( S ) | 0 | +| Information transfer | I (infor-mation) | | | | | | +| Supervisory | RR (receive ready) | RR (receive ready) | N ( R ) | P/F | 0 0 | 0 1 | +| | RNR (receive not ready) | RNR (receive not ready) | N ( R ) | P/F | 0 1 | 0 1 | +| | REJ (reject) | REJ (reject) | N ( R ) | P/F | 1 0 | 0 1 | +| Unnumbered | SABM (set asynchronous balanced mode) | | 0 0 1 | P | 1 1 | 1 1 | +| | | DM (disconnect mode) | 0 0 0 | F | 1 1 | 1 1 | +| | UI (un-numbered information) | | 0 0 0 | P | 0 0 | 1 1 | +| | DISC (disconnect) | | 0 1 0 | P | 0 0 | 1 1 | +| | | UA (un-numbered acknowledge) | 0 1 1 | F | 0 0 | 1 1 | + +### 6.8.2 Set asynchronous balanced mode (SABM) command + +The SABM unnumbered command is used to place the addressed user side or network side into the modulo 8 multiple frame acknowledged operation. + +An information field is permitted with the SABM command only if it is used in the MS to BSS direction in order to establish a SAPI 0 data link (for contention resolution after having transmitted a random access frame on the RACH or in response to a PACKET CS COMMAND message). Layer 3 will indicate when an information field is to be included (see sub-clause 8.4.1 for procedures). + +A data link layer entity confirms acceptance of a SABM command by the transmission at the first opportunity of a UA response. Upon acceptance of this command, the data link layer entity's send state variable V(S), acknowledge state variable V(A), and receive state variable V(R), are set to 0. The transmission of an SABM command indicates the clearance of any exception condition, in particular a busy condition that was reported by the earlier transmission of an RNR frame by that same data link layer entity. + +Previously transmitted I frames that are unacknowledged when this command is actioned remain unacknowledged and shall be discarded. It is the responsibility of a higher layer (for example, layer 3) to recover from the possible loss of the contents of such I frames. + +NOTE: SABM frames cannot contain layer 3 message units which have to be segmented. + +### 6.8.3 Disconnect (DISC) command + +The DISC unnumbered command is transmitted in order to terminate the multiple frame operation. + +NOTE: See sub-clause 8.4.4.4 for local end release where the multiple frame operation is terminated without transmitting a DISC command frame. + +No information field is permitted with the DISC command. + +Prior to actioning the command, the data link layer entity receiving the DISC command confirms the acceptance of a DISC command by the transmission of a UA response. The data link layer entity sending the DISC command terminates the multiple frame operation when it receives the acknowledging UA or DM response. + +Previously transmitted I frames that are unacknowledged when this command is actioned remain unacknowledged and shall be discarded. It is the responsibility of a higher layer (for example, layer 3) to recover from the possible loss of the contents of such I frames. + +### 6.8.4 Unnumbered information (UI) command + +When a layer 3 entity requests unacknowledged information transfer, the UI unnumbered command shall be used to send information to its peer without affecting data link layer variables. UI command frames do not carry a sequence number. Therefore, the UI frame may be lost without notification to the layer 3 entity if a data link exception occurs during transmission of the command. + +The request of unacknowledged information transfer may require short L2 header type 1. If the layer 2 entity does not support short L2 header type 1, it shall report an MDL-ERROR-INDICATION with error cause "short L2 header type 1 not supported". If short L2 header type 1 is not applicable for the intended information transfer, it shall report an MDL-ERROR-INDICATION with error cause "short L2 header type 1 not applicable". If the request is not erroneous, it shall transfer the information as specified in a format Bter frame. + +### 6.8.5 Receive ready (RR) command/response + +The receive ready (RR) supervisory frame is used by a data link layer entity to: + +- indicate it is ready to receive an I frame; +- acknowledge previously received I frames numbered up to and including N(R) - 1 (as defined in sub-clause 8); +- clear a busy condition that was indicated by the earlier transmission of an RNR frame by that same data link layer entity. + +In addition to indicating the status of a data link layer entity, the RR command with the P bit set to "1" may be used by the data link layer entity to ask for the status of its peer data link layer entity. + +No information field is permitted with the RR command/response. + +### 6.8.6 Reject (REJ) command/response + +The reject (REJ) supervisory frame is used by a data link layer entity to request retransmission of I frames starting with the frame numbered N(R). The value of N(R) in the REJ frame acknowledges I frames numbered up to and including N(R) - 1. New I frames pending initial transmission shall be transmitted following the retransmitted I frames. + +Only one REJ exception condition for a given direction of information transfer shall be established at a time. The REJ exception condition is cleared (reset) upon the receipt of an I frame with an N(S) equal to the N(R) of the REJ frame. + +The transmission of an REJ frame shall also indicate the clearance of any busy condition within the sending data link layer entity that was reported by the earlier transmission of an RNR frame by that same data link layer entity. + +In addition to indicating the status of a data link layer entity, the REJ command with the P bit set to "1" may be used by the data link layer entity to ask for the status of its peer data link layer entity. + +No information field is permitted with the REJ command/response. + +### 6.8.7 Receive not ready (RNR) command/response + +The receive not ready (RNR) supervisory frame shall be used by a data link layer entity to indicate a busy condition; that is, a temporary inability to accept additional incoming I frames. The value of N(R) in the RNR frame acknowledges I frames numbered up to and including N(R) - 1. + +Acknowledgement of subsequent I frames transmitted before the indication of the peer receiver busy is received, will be made in subsequent exchanges if they arrive after the peer receiver busy condition has been cleared. + +In addition to indicating the status of a data link layer entity, the RNR command with the P bit set to "1" may be used by the data link layer entity to ask for the status of its peer data link layer entity. + +No information field is permitted with the RNR command/ response. + +NOTE: The protocol operation used on control channels with SAPI=0 or SAPI=3 shall not utilize the RNR frame type and related procedures. Therefore RNR frames received in those cases can be ignored. + +### 6.8.8 Unnumbered acknowledgement (UA) response + +The UA unnumbered response is used by a data link layer entity to acknowledge the receipt and acceptance of the mode setting commands (SABM or DISC). Received mode setting commands are not actioned until the UA response is transmitted. + +An information field is permitted with the UA response, i e if an SABM command with an information field is received and the SABM is to be acknowledged, the UA response to that command shall contain the same information field as received in the SABM command. + +The transmission of the UA response indicates the clearance of any busy condition that was reported by the earlier transmission of an RNR frame by that same data link layer entity. + +### 6.8.9 Disconnected mode (DM) response + +The DM unnumbered response is used by a data link layer entity to report to its peer that the data link layer is in a state such that multiple frame operation cannot be performed. A data link layer entity shall transmit a DM response to any valid command received which it cannot action. + +No information field is permitted with the DM response. + +# --- 7 Elements for layer-to-layer communication + +## 7.1 Definition of primitives and parameters + +Communications between layers and between the data link layer and layer 3 are accomplished by means of primitives. + +Primitives represent, in an abstract way, the logical exchange of information and control between the data link layer and adjacent layers. They do not specify or constrain implementations. + +Primitives consist of commands and their respective responses associated with the services requested of a lower layer. The general syntax of a primitive is: + +XX - Generic name - Type (Parameters); + +where XX designates the layer providing the service. For the present document XX is DL for the data link layer, PH for the physical layer and MDL for administrative functions (e.g. error reporting and recovery). + +### 7.1.1 Generic names + +The generic name specifies the activity that the identified layer should perform. Table 5 illustrates the primitives defined in the present document. + +The primitive generic names that are defined in the present document are: + +#### 7.1.1.1 DL-ESTABLISH + +The DL-ESTABLISH primitives are used to request, confirm and indicate the outcome of the procedures for establishing multiple frame operation. + +#### 7.1.1.2 DL-RELEASE + +The DL-RELEASE primitives are used to request, confirm and indicate the outcome of the procedures for terminating a previously established multiple frame operation. + +In the case of a data link layer malfunction, layer 3 will be notified by a RELEASE indication. + +#### 7.1.1.3 DL-DATA + +The DL-DATA primitives are used to pass to and from the data link layer layer 3 message units which are to be transmitted, or have been received, using multiple frame acknowledged operation. + +#### 7.1.1.4 DL-UNIT DATA + +The DL-UNIT DATA primitives are used to pass to and from the data link layer, layer 3 message units which are to be transmitted, or have been received, using unacknowledged operation. + +#### 7.1.1.5 DL-SUSPEND + +The DL-SUSPEND primitive is used in the mobile station by the radio resource management entity to perform a local end release in such a way, that the layer 3 data units and the state of the transmit and receive counters are saved. + +#### 7.1.1.6 DL-RESUME + +The DL-RESUME primitive is used in the mobile station by the radio resource management entity to establish multiple frame operation and resume communication with the network without loss of layer 3 messages. The layer 3 data unit passed to layer 2 together with that primitive is sent with priority (e.g. ASSIGNMENT COMPLETE or HANDOVER COMPLETE). + +#### 7.1.1.7 DL-RECONNECT + +The DL-RECONNECT primitive is used in the mobile station by the radio resource management entity to restore multiple frame operation on the old channel after failure of the channel change. The layer 3 data unit passed to layer 2 with previous DL-RESUME-REQUEST (i.e. ASSIGNMENT COMPLETE or HANDOVER COMPLETE) is discarded and the layer 3 data unit passed together with that primitive is sent with priority (e.g. ASSIGNMENT FAILURE or HANDOVER FAILURE). + +#### 7.1.1.8 DL-RANDOM ACCESS + +The DL-RANDOM ACCESS primitives are used to request (in the MS) the sending of a random access message, to confirm (in the MS) the transmission of the random access message including the time slot in which it was sent, and to indicate (in the network) the arrival of a random access message. + +#### 7.1.1.9 MDL-RELEASE + +The MDL-RELEASE primitives are used by layer 3 entity to request local end termination of a previously established acknowledged mode operation. + +#### 7.1.1.10 MDL-ERROR + +The MDL-ERROR primitives are used to notify layer 3 that an error has occurred, detected as a result of communication with the data link peer entity, which cannot be corrected by the data link layer. + +#### 7.1.1.11 PH-DATA + +The PH-DATA primitives are used to pass message units containing frames used for data link layer peer-to-peer communications to and from the physical layer. + +#### 7.1.1.12 PH-RANDOM ACCESS + +The PH-RANDOM ACCESS primitives are used to request (in the MS) the sending of a random access frame, to confirm (in the MS) the transmission of the random access frame including the time slot in which it was sent, and to indicate (in the network) the arrival of a random access frame. + +#### 7.1.1.13 PH-CONNECT + +The PH-CONNECT primitive is used to indicate that a specific type of channel has been connected at the physical layer. + +#### 7.1.1.14 PH-READY-TO-SEND + +The PH-READY-TO-SEND primitive is generated by the physical layer to enable the data link layer to synchronize to the next instant of physical transmission. On receipt of this indication layer 2 may trigger piggy backing (if applicable), the start of T200 and the forwarding of data units to layer 1. + +#### 7.1.1.15 PH-EMPTY-FRAME + +The PH-EMPTY-FRAME primitive can be used by the data link layer instead of a PH-DATA-REQUEST primitive, when no frame has to be transmitted after receiving the PH-READY-TO-SEND indication. It enables handling of several layer 2 entities by layer 1 and transmission of fill frames, if necessary. + +### 7.1.2 Primitives types + +The primitives types defined in the present document are: + +NOTE: For the action sequence of these primitive types, see 3GPP TS 44.001. + +#### 7.1.2.1 REQUEST + +The REQUEST primitive type is used when a higher layer is requesting a service from the next lower layer. + +#### 7.1.2.2 INDICATION + +The INDICATION primitive type is used by a layer providing a service to notify the next higher layer of activities related to the REQUEST primitive type. + +#### 7.1.2.3 RESPONSE + +The RESPONSE primitive type is used by a layer to acknowledge receipt, from the next lower layer, of the INDICATION primitive type. + +#### 7.1.2.4 CONFIRM + +The CONFIRM primitive type is used by the layer providing the requested service to confirm that the activity has been completed. + +Figure 6 illustrates the relationship of the primitive types to the layer 3 and the data link layer. + +![Diagram illustrating the relationship of primitive types to Layer 3 and the Data link layer. The diagram shows two vertical stacks representing Layer 3 and the Data link layer. The left stack shows Layer 3 sending a 'Request' primitive to the Data link layer via a Service Access Point (SAP), and the Data link layer sending a 'Confirm' primitive back to Layer 3. The right stack shows the Data link layer sending an 'Indication' primitive to Layer 3 via the SAP, and Layer 3 sending a 'Response' primitive back to the Data link layer. A horizontal line with an arrow and an oval indicates a 'Layer 2 peer-to-peer protocol' connecting the two Data link layers.](844077b3034f0030b404207db0ad76b4_img.jpg) + +Diagram illustrating the relationship of primitive types to Layer 3 and the Data link layer. The diagram shows two vertical stacks representing Layer 3 and the Data link layer. The left stack shows Layer 3 sending a 'Request' primitive to the Data link layer via a Service Access Point (SAP), and the Data link layer sending a 'Confirm' primitive back to Layer 3. The right stack shows the Data link layer sending an 'Indication' primitive to Layer 3 via the SAP, and Layer 3 sending a 'Response' primitive back to the Data link layer. A horizontal line with an arrow and an oval indicates a 'Layer 2 peer-to-peer protocol' connecting the two Data link layers. + +**Figure 6: Relationship of the primitive types to the layer 3 and the data link layer** + +### 7.1.3 Parameter definition + +#### 7.1.3.1 Message unit + +The message unit contains additional layer-to-layer information concerning actions and results associated with requests. In the case of the DATA and UNIT DATA primitives, the message unit contains the requesting layer peer-to-peer messages. For example, the DL-DATA message unit contains the layer 3 message unit; the PH-DATA message unit contains the data link layer frame. + +**NOTE:** The operations across the data link layer/layer 3 boundary shall be such that the layer sending the DATA or UNIT DATA primitive can assume a temporal order of the bits within the message unit and that the layer receiving the primitive can reconstruct the message with its assumed temporal order. + +#### 7.1.3.2 Channel type + +Since the Dm channel procedures are distributed on several types of channel (CCCH, BCCH and various types of DCCH), a parameter will be needed in order to distribute the layer 3 message units correctly on the various types of channel. The control channel types to be used are defined in 3GPP TS 44.003. + +#### 7.1.3.3 Service Access Point + +Since data links on different SAPIs may be multiplexed, the SAPI parameter is used to indicate the respective association. + +#### 7.1.3.4 Release mode + +The release mode parameter is used to enable the data link layer to operate in different release modes depending on whether the data link is to be released in the normal way or that a local end release shall take place on command from the layer 3. The values of the parameter are: + +- normal; +- local end release. + +#### 7.1.3.5 Error cause + +This parameter is used by the data link layer to report procedure error to layer 3. The following causes may be reported: + +- timer T200 expired (N200 +1) times: perform abnormal release; +- re-establishment request; +- unsolicited UA response; +- unsolicited DM response; +- unsolicited DM response, multiple frame established state: perform abnormal release; +- unsolicited supervisory response; +- sequence error: perform abnormal release; +- U frame with incorrect parameters; +- short L2 header type 1 not supported; +- short L2 header type 1 not applicable; +- S frame with incorrect parameters; +- I frame with incorrect use of M bit; +- I frame with incorrect length; +- frame not implemented; +- SABM command, multiple frame established state; +- SABM command with information field not allowed in this state. + +#### 7.1.3.6 Establish mode + +This parameter is used in the MS to indicate to the data link layer the type of establishment that is required. The parameter takes the following values: + +- normal; +- contention resolution. + +#### 7.1.3.7 L2 header type + +This parameter is used by higher layers to ask for application of a specific L2 header type; as values for the parameter, only "short L2 header type 1" and "normal L2 header" are actually defined. + +#### 7.1.3.8 Priority + +This parameter is used by the higher layers to indicate the priority of a Layer 3 message on SAPI 0 with multiple frame operation. The parameter is not applicable to unacknowledged information transfer or to other SAPIs. The parameter takes the following values: + +- high; +- normal; +- low. + +The parameter need not be included if the higher layers do not support the sending of low priority messages as defined in 3GPP TS 44.018. If the parameter is not included, the data link layer shall assume a priority value of "normal". + +**Table 5: Data Link Service primitives** + +| Generic name

and type | Parameters | | | | | | | Message

unit

contents | +|------------------------------|------------|-------------------------------|-------------|--------------|----------------|-------------------------------------------|-------------------|-------------------------------------| +| | SAPI | Channel type | Error Cause | Release mode | Establish mode | L2 header type | Priority | | +| DL-ESTABLISH-REQUEST | 0 | DCCH | | | CoRes | | | Layer 3 message | +| | 0 | DCCH, SACCH | | | Norm | | | | +| | 3 | DCCH, SACCH | | | Norm | | | | +| DL-ESTABLISH-INDICATION | 0 | DCCH | | | CoRes | | | Layer 3 message | +| | 0 | DCCH, SACCH | | | Norm | | | | +| | 3 | DCCH, SACCH | | | Norm | | | | +| DL-ESTABLISH-CONFIRM | 0 | DCCH | | | CoRes | | | | +| | 0 | DCCH, SACCH | | | Norm | | | | +| | 3 | DCCH, SACCH | | | Norm | | | | +| DL-RELEASE-REQUEST | 0,3 | DCCH, SACCH | | any | | | | | +| DL-RELEASE-INDICATION | 0,3 | DCCH, SACCH | | any | | | | | +| DL-RELEASE-CONFIRM | 0,3 | DCCH, SACCH | | any | | | | | +| DL-SUSPEND-REQUEST | 0 | DCCH | | | | | | | +| DL-SUSPEND-CONFIRM | 0 | DCCH | | | | | | | +| DL-RESUME-REQUEST | 0 | DCCH | | | | | | Layer 3 peer-to-peer message | +| DL-RESUME-CONFIRM | 0 | DCCH | | | | | | | +| DL-RECONNECT-REQUEST | 0 | DCCH | | | | | | Layer 3 peer-to-peer message | +| DL-RECONNECT-CONFIRM | 0 | DCCH | | | | | | | +| DL-DATA-REQUEST | 0,3 | DCCH, SACCH | | | | | any (SAPI 0 only) | Layer 3 peer-to-peer message | +| DL-DATA-INDICATION | 0,3 | DCCH, SACCH | | | | | | Layer 3 peer-to-peer message | +| DL-UNIT DATA-REQUEST | 0 | BCCH
CCCH
DCCH
SACCH | | | | normal L2 header / short L2 header type 1 | | Layer 3 peer-to-peer message | +| | 3 | DCCH
SACCH | | | | | | Layer 3 peer-to-peer message | + +| Generic name

and type | Parameters | | | | | | | Message

unit

contents | +|------------------------------|------------|-------------------------------|-------------|--------------|----------------|----------------|----------|-----------------------------------------| +| | SAPI | Channel type | Error Cause | Release mode | Establish mode | L2 header type | Priority | | +| DL-UNIT DATA-INDICATION | 0 | BCCH
CCCH
DCCH
SACCH | | | | | | Layer 3 peer-to-peer message | +| | 3 | DCCH
SACCH | | | | | | Layer 3 peer-to-peer message | +| MDL-RELEASE-REQUEST | 0,3 | DCCH,
SACCH | | | | | | | +| MDL-ERROR-INDICATION | 0,3 | DCCH,
SACCH | any | | | | | | +| DL-RANDOM ACCESS-REQUEST | 0 | RACH | | | | | | Channel request (see 3GPP TS 44.018) | +| | 0 | DCCH | | | | | | Handover access (see 3GPP TS 44.018) | +| DL-RANDOM ACCESS-INDICATION | 0 | RACH | | | | | | Request reference (see 3GPP TS 48.058) | +| | 0 | DCCH | | | | | | Handover reference (see 3GPP TS 48.058) | +| DL-RANDOM ACCESS-CONFIRM | 0 | RACH | | | | | | Request reference (see 3GPP TS 44.018) | + +**Table 6: Physical Service primitives used** + +| Generic name and type | Parameters | | | | | Message unit contents | +|-----------------------------|------------|--------------|-------------|--------------|----------------|---------------------------------------------------------| +| | SAPI | Channel type | Error Cause | Release mode | Establish mode | | +| PH-DATA-REQUEST | any | | | | | Data link peer-to-peer message | +| PH-DATA-INDICATION | any | | | | | Data link peer-to-peer message | +| PH-RANDOM ACCESS-REQUEST | RACH, DCCH | | | | | Random access data link message unit | +| PH-RANDOM ACCESS-INDICATION | RACH, DCCH | | | | | Random access data link message unit and TDMA frame nr. | +| PH-RANDOM ACCESS- CONFIRM | RACH, DCCH | | | | | TDMA frame number | +| PH-CONNECT-INDICATION | any | | | | | | +| PH-READY-TO-SEND-INDICAT. | any | | | | | | +| PH-EMPTY-FRAME-REQUEST | any | | | | | | + +NOTE 1: Table 5 and table 6 do not contain a complete list of conditional dependencies of service primitive parameters. If a field is left blank, the respective parameter shall not be used or is not applicable. If a field is marked by "any", the respective parameter shall be used and shall be set to a valid value according its specification. + +NOTE 2: In table 5 and table 6, the term "DCCH" denotes the respective main DCCH (i.e. SDCCH or FACCH). + +## 7.2 Primitive procedures + +The procedures in the MS and the network are described by use of the primitives defined above. See also 3GPP TS 44.018. + +# 8 Definition of the peer-to-peer protocol LAPDm + +## 8.1 General + +In the following sub-clauses, a protocol for use by the data link layer on the radio interface is specified, referred to as "LAPDm". Beside this, there may be signalling and data transfer between layer 3 entities, which does not comply to the procedures described hereafter (e.g. for the random access procedure see annex A; for short message cell broadcast see 3GPP TS 44.012). + +The LAPDm elements of procedure (frame types) which apply are: + +- a) for unacknowledged information transfer (sub-clause 8.3): + +UI-command. + +- b) for multiple frame acknowledged information transfer (sub-clauses 8.4 to 8.8): + +SABM-command; + +UA-response; + +DM-response; + +DISC-command; + +RR-command/response; + +RNR-command/response; + +REJ-command/response; + +I-command. + +For the various channel types the following applies: + +- BCCH; unacknowledged operation only; +- CCCH; unacknowledged operation only; +- all types of DCCH; unacknowledged operation and multiple frame acknowledged operation. + +For acknowledged mode (multiple frame operation) on SAPI=0 and SAPI=3, a special protocol operation shall be used mandatorily, as specified in sub-clause 9. + +For handling of timers, the procedures and terminology of CCITT Recommendation Z.100 will be used, i.e. + +set means that: + +- a) if the timer is inactive, the timer becomes active, i.e. a timer value is associated with the timer and it starts running; +- b) if the timer is active, the timer is first reset, as in c) below and then set as in a) above; + +reset means that: + +- c) if the timer is active, the timer becomes inactive, i.e. the association with the timer value is lost and it stops running; +- d) if the timer is inactive, it remains inactive. + +NOTE: The task set T200 shall be performed at the instant right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer. + +## 8.2 General Protocol Procedures + +### 8.2.1 Unacknowledged information transfer + +Higher layers may ask for unacknowledged transmission transfer with normal L2 header; higher layers may also ask for unacknowledged transmission transfer on SAPI 0 using short L2 header type 1. + +When a protocol entity receives a valid UI frame, this requires no further response to the transmitting entity. + +For unacknowledged information transfer with normal L2 header, the P/F bit is not used and shall be set to "0". + +### 8.2.2 Acknowledged multiple frame information transfer + +A data link layer entity receiving an SABM, DISC, RR, REJ or I command, shall respond to the originating entity by an appropriate response frame (as specified in sub-clauses 8.4 through 8.7) within the time limits given in sub-clause 8.9. + +If the received command frame carries a P bit set to "1", the F bit in the corresponding response frame shall be set to "1", too. + +Frames containing SAPI values not used by the current version of the present document, shall be ignored without any notification. + +## 8.3 Procedures for unacknowledged information transfer + +### 8.3.1 General + +The procedures which apply to the transmission of information in unacknowledged operation are defined below. + +No data link layer error recovery procedures are defined for unacknowledged operation. + +### 8.3.2 Transmission of unacknowledged information + +NOTE 1: The term "transmission of a UI frame" refers to the delivery of a UI frame by the data link layer to the physical layer. + +Unacknowledged information is passed to the data link layer by layer 3 using the primitive DL-UNIT DATA-REQUEST. This DL-UNIT DATA-REQUEST specifies whether a short L2 header type 1 is to be used or not. The layer 3 message unit shall be transmitted in a UI command frame. + +Layer 2 shall construct a layer 2 message unit from the layer 3 message unit and pass it to layer 1 for transmission using the primitive PH-DATA-REQ. The layer 2 message unit uses the frame type as defined in sub-clause 5.1. + +If the layer 2 message unit contains a control field, the P bit shall be set to "0". + +NOTE 2: On a DCCH, UI frames with the length indicator set to "0" may be used as fill frames, see sub-clause 8.4.2.3. + +### 8.3.3 Receipt of unacknowledged information + +On receipt of a UI command frame with a SAPI which is supported by the receiver, the contents of the information field shall be passed to the layer 3 entity identified by the SAPI using the data link layer to layer 3 primitive DL-UNIT DATA-INDICATION. UI frames with invalid SAPI values shall be discarded. UI frames received with the length indicator set to "0" shall be ignored. + +## 8.4 Procedures for establishment and release of multiple frame operation + +### 8.4.1 Establishment of multiple frame operation + +#### 8.4.1.1 General + +These procedures shall be used to establish multiple frame operation between the BS and a designated MS entity. + +Layer 3 will initiate the establishment procedure after a physical channel supporting this type of operation (see sub-clause 8.1) has been allocated to the MS. + +NOTE: In order to avoid loss of layer 3 information if the SABM has to be retransmitted because the UA response message is lost, the data link layer should be established when needed by the entity that will send an I command frame. For SAPI 0 the data link is always established by the MS. + +Two establishment procedures are specified: + +- normal establishment where the SABM does not contain an information field. Layer 3 will indicate a request for this type of establishment by the use of the DL-ESTABLISH-REQUEST primitive (sub-clauses 8.4.1.2 and 8.4.1.3); +- contention resolution where the SABM contains an information field. The procedure is always initiated by the MS, i.e. the SABM is sent by the MS. Layer 3 will indicate a request for this type of establishment by the use of the DL-ESTABLISH-REQUEST primitive containing the layer 3 message unit (sub-clauses 8.4.1.4 and 8.4.1.5). This procedure is only applicable for SAPI 0. + +Re-establishment may be initiated, using the normal establishment procedure, as a result of the data link layer procedure defined in sub-clause 8.6. + +#### 8.4.1.2 Normal establishment procedures + +A data link layer entity shall initiate a request for the multiple frame operation to be set by transmitting the Set Asynchronous Balanced Mode (SABM) command with the P bit set to "1". Since the DL-ESTABLISH-REQUEST primitive does not contain a layer 3 message unit, the length indicator, L, is set to "0". + +All existing exception conditions shall be cleared, the retransmission counter shall be reset, and timer T200 shall be set right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer (timer T200 is defined in sub-clause 8.8.1). + +The establishment procedure implies the discard of any outstanding DL-DATA-REQUEST primitive which has been invoked prior to the DL-ESTABLISH-REQUEST. It also implies the discard of any segmented layer 3 message unit for which the last segment has not been received (see sub-clause 8.5.2 for the concatenation procedure). + +All frames other than unnumbered frame formats received during the establishment procedures shall be ignored. + +A data link layer entity receiving an SABM, if it is able to enter the multiple-frame-established state, shall: + +- respond with an Unnumbered Acknowledgement (UA) response with the F bit set to the same binary value as the P bit in the received SABM command, the same SAPI value as in the received SABM command, and with the length indicator, L, set to "0"; +- set the send state variable V(S), receive state variable V(R) and acknowledge state variable V(A) to 0; +- enter the multiple-frame-established state and inform the associated layer 3 entity using the primitive DL- ESTABLISH-INDICATION; +- clear all existing exception conditions; +- clear an existing peer receiver busy condition. + +If the data link layer entity is unable to enter the multiple-frame-established state, it shall respond to the SABM command with a DM response with the F bit set to the same binary value as the P bit in the received SABM command. + +Upon reception of the UA response with the F bit set to "1", the originator of the SABM command shall: + +- reset timer T200; +- set the send state variable V(S), the receive state variable V(R) and the acknowledge state variable V(A) to 0; +- enter the multiple-frame-established state and inform the associated layer 3 entity using the primitive DL- ESTABLISH-CONFIRM. + +A UA response with the F bit set to "0" shall be ignored. + +Upon reception of a DM response with F bit set to "1", the originator of the SABM command shall indicate this to the layer 3 entity by means of the primitive DL-RELEASE- INDICATION and reset timer T200. DM responses with the F bit set to "0" shall be ignored. + +#### 8.4.1.3 Procedure on expiry of timer T200: Normal establishment + +If timer T200 expires before the UA or DM response is received, the data link layer entity shall: + +- retransmit the SABM command as above; +- set timer T200 right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer; and +- increment the retransmission counter. + +After retransmission of the SABM command N200 times, the data link layer entity shall indicated this to the associated layer 3 entity by means of the primitive DL- RELEASE-INDICATION. Layer 3 shall also be notified by using the + +primitive MDL-ERROR-INDICATION with the cause "timer T200 expired N200 + 1 times: perform abnormal release". + +The value of N200 is defined in sub-clause 8.8.2. + +#### 8.4.1.4 Contention resolution establishment procedure + +This procedure is always initiated by the MS for establishing a data link in order to resolve contention after having accessed the BS on the RACH. The procedure may also be used by the MS for establishing a data link in response to a PACKET CS COMMAND message (see 3GPP TS 44.060). Layer 3 decides when this establishment procedure is to be used and will request the data link layer to initiate the procedure by a DL-ESTABLISH-REQUEST primitive containing the layer 3 message unit and with the parameter established mode set to contention resolution. + +The data link layer shall, however, ignore any such service request if it is not in the idle state when the request is received. + +The data link layer entity in the MS shall initiate the establishment by transmitting an SABM command with the P bit set to "1". The SABM command shall contain the layer 3 message unit received in the DL-ESTABLISH-REQUEST primitive and the length indicator, L, shall be set to the appropriate value. + +NOTE 1: According to sub-clause 9, the contention resolution procedure is only permitted with SAPI value 0. + +The information field of the SABM command shall be stored in the data link layer entity of the MS. The information field is removed when the data link layer enters the multiple frame established state or the idle state, see below. + +All existing exception conditions shall be cleared, the retransmission counter shall be reset, and timer T200 shall be set when right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer. + +The peer data link layer entity in the BS receiving the SABM shall, if the entity is in the idle state and an "establishment in progress" flag has not been set: + +- set the "establishment in progress" flag; +- store the information field received in the SABM command; +- respond, at the earliest possible opportunity, with a UA response with: + - the same SAPI value as received in the SABM command; + - the F bit set to the same binary value as the P bit received in the SABM command; + - the length indicator, L, set to the same value as that contained in the SABM command; + - the same information field as that contained in the SABM command; +- set the send state variable V(S), the receive state variable V(R) and the acknowledge state variable V(A) to 0; +- enter the "contention resolution receiver" state and inform the layer 3 entity using the DL-ESTABLISH- INDICATION primitive. The primitive shall contain the received layer 3 message unit; +- clear all existing exception conditions. + +If an SABM command with an information field is received when the "establishment in progress" flag has been set, the data link layer entity in the BS shall compare the stored information field with the information field received in the SABM command. If they are not identical, the SABM command shall be ignored without any notification. If they are identical, the data link entity shall respond, at the earliest possible opportunity, with a UA response with: + +- the same SAPI value as received in the SABM command; +- the F bit set to the same binary value as the P bit contained in the SABM command; +- the length indicator, L, set to the same value as that contained in the SABM command; +- the stored information field. + +NOTE 2: This case corresponds to a retransmission of the SABM command by the MS (see sub-clause 8.4.1.5). + +NOTE 3: The specification is very different from the normal establishment procedure: in the latter case the reception of a subsequent SABM frame triggers a re-establishment (see sub-clause 8.6). + +The data link layer entity in the BS shall remove the "establishment in progress" flag and delete the stored information field when: + +- an I frame or supervisory frame is received. If the frame is in sequence, the data link layer entity shall enter the multiple frame established state and process the frame as specified for operation in the multiple frame established state. If the frame is out of sequence, the BS shall initiate abnormal release using the procedure of sub-clause 8.6; +- a release request is received from layer 3. In this case the data link layer entity shall enter the idle state if the primitive received is DL-RELEASE-REQUEST or the null state if the primitive is MDL-RELEASE-REQUEST. + +The procedure when awaiting acknowledgement in the MS is as follows: + +Upon reception of a UA response containing an information field and with the F bit set to "1", the data link layer entity in the MS shall compare the stored information field with the information field received in the UA response. If the two fields are identical, the data link layer entity shall: + +- reset timer T200; +- set the send state variable V(S), the receive state variable V(R) and the acknowledge state variable V(A) to 0; +- delete the stored information field; +- enter the multiple-frame-established state and inform the layer 3 entity using the DL-ESTABLISH-CONFIRM primitive. + +If the two fields are different, the data link layer entity shall: + +- reset timer T200; +- delete the stored information field; +- enter the idle state and inform the layer 3 entity using the DL-RELEASE-INDICATION primitive. + +All frames other than unnumbered frame formats received for the SAPI in use during the establishment procedures shall be ignored. + +The reception of unnumbered frames other than UA is treated as specified for the normal establishment case. + +NOTE 4: In fact, there are no foreseen cases in which the network will send SABM, DISC or DM, but for sake of completeness these occurrences are specified and must be treated. + +#### 8.4.1.5 Procedure on expiry of timer T200: contention resolution (MS only) + +If timer T200 expires before a UA response has been received, the data link layer entity shall: + +- retransmit the SABM command as in sub-clause 8.4.1.4; +- set timer T200 right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer; and +- increment the retransmission counter by 1. + +After retransmission of the SABM command N200 times, the data link layer shall enter the idle state and issue a DL- RELEASE-INDICATION primitive to the layer 3 entity. Layer 3 shall also be notified by using the primitive MDL-ERROR- INDICATION with cause "timer T200 expired N200 + 1 times: perform abnormal release". + +### 8.4.2 Information transfer + +#### 8.4.2.1 General requirements + +Having either transmitted the UA response to a received SABM command or received the UA response to a transmitted SABM command, I frames and supervisory frames shall be transmitted and received according to the procedures described in sub-clause 8.5. + +If an SABM command is received while in the multiple-frame-established state, the data link layer entity shall proceed as follows: + +- if the SABM command carries no information field (i.e. L=0), then the data link layer entity shall conform to the re-establishment procedure described in sub-clause 8.6; +- if the SABM command carries an information field (i.e. L>0), and can be considered as a part of a contention resolution procedure, then the SABM command shall be ignored without any notification; +- otherwise, the SABM command shall be ignored, and the layer 3 shall be informed by issuing a MDL-ERROR-INDICATION indicating "SABM command with information field not allowed in this state" or "U frame with incorrect parameters". + +On receipt of a UI command, the procedures defined in sub-clause 8.3 shall be followed. + +#### 8.4.2.2 Error conditions + +Error conditions which will require abnormal release of the data link are given in sub-clause 8.6. + +Cases which do not lead to release but may cause the data link layer entity to issue an MDL-ERROR-INDICATION are summarized in table 7. + +**Table 7: Actions taken on response frames** + +| Response frame | Multiple frame established | Timer recovery | +|--------------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| UA F=1 | MDL-ERROR-INDICATION
(unsolicited UA response) | MDL-ERROR-INDICATION
(unsolicited UA response) | +| UA F=0 | MDL-ERROR-INDICATION
(unsolicited UA response) | MDL-ERROR-INDICATION
(unsolicited UA response) | +| DM F=1 | MDL-ERROR-INDICATION
(unsolicited DM response) | Normal | +| DM F=0 | MDL-ERROR-INDICATION
(unsolicited DM response, multiple frame established state: perform abnormal release) | MDL-ERROR-INDICATION
(unsolicited DM response, multiple frame established state: perform abnormal release) | +| Supervisory response F=1 | MDL-ERROR-INDICATION
(unsolicited supervisory response) | Normal | +| Supervisory response F=0 | Normal | Normal | + +#### 8.4.2.3 Fill frames + +In periods where no other frames are scheduled for transmission and something must be sent on the radio path, a fill frame as defined below shall be sent (3GPP TS 44.018 and 3GPP TS 45.002 prohibit such periods for PCH and BCCH). + +On a DCCH, a fill frame is a UI command frame for SAPI 0 with P=0 and with an information field of 0 octet length (hence, it is a frame of type A). It has the following structure: + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|-----|---|---|---|---|---|---|---|---|----------|----------| +| | 0 | 0 | 0 | 0 | 0 | 0 | C | 1 | 1 | (note 1) | +| | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 2 | | +| | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 3 | | +| | X | X | X | X | X | X | X | X | 4 | (note 2) | +| | | | | | | | | | | | +| | X | X | X | X | X | X | X | X | 21 or 23 | (note 2) | + +NOTE 1: Bit C is set to: + +0 if sent by MS + +1 if sent by network. + +NOTE 2: See sub-clause 5.2. + +Fill frame for a BCCH, PCH, AGCH, or NCH is the following: + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|-----|---|---|---|---|---|---|---|---|----|--------| +| | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | | +| | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 2 | (note) | +| | | | | | | | | | | | +| | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 23 | (note) | + +NOTE: The value "00101011" is chosen due to the modulation and interleaving scheme used in the GSM system. + +### 8.4.3 Suspension and resumption of multiple frame operation + +#### 8.4.3.1 General + +These procedures shall be used in a MS entity to suspend the uplink multiple frame operation for SAPI=0 during a change of dedicated channels (dedicated channel assignment or handover procedure on layer 3) and to resume the operation after the new physical channel has been connected. The purpose of these procedures is to provide a mechanism for reliably avoiding message loss during a change of dedicated channels. The procedures are only described for the case where the window size is one; it should, however, be obvious how to adapt them to larger window sizes. + +As the procedures may delay the actual channel change, they shall only be used to protect layer 3 messages pertaining to SAPI=0. Applications using the multiple frame established service on SAPIs other than 0 are expected to cope with message loss or duplication autonomously, i.e. on layers above layer 2. + +Both layer 3 procedures, dedicated channel assignment and handover, are initiated and controlled by a network entity (BSS or MSC). This entity therefore will suspend the flow of layer 3 messages towards the MS after the ASSIGNMENT or HANDOVER COMMAND message has been issued. When the data link on the new channel has been established, the message flow may resume. Obviously, no provisions in layer 2 are needed on the network side to prevent message loss or duplication on the downlink during channel change. + +In the following, the procedures in the MS are described. For the description of the procedures, a conceptual configuration of a send queue, a send buffer and a transmit buffer are assumed. + +In order to ease the description of the procedures in the MS, it is assumed that any layer 3 message passed to layer 2 via SAPI 0 in DL-DATA-REQUEST or DL-UNIT-DATA primitive is first placed in the send queue. The layer 2 entity will take out the messages "first in-first out" and put them into a send buffer. The send buffer can hold no more than one + +layer 3 message at a time. From the contents of the send buffer, an I frame or UI frame is constructed, only one at a time, and placed in a transmit buffer. (If the layer 3 message needs to be segmented, then this last step will be performed several times). The frame is then transmitted. + +Upon transmission and after it has been acknowledged if it has been an I frame, the transmit buffer is cleared and filled with the next frame. When the contents of the send buffer have been transmitted and acknowledged, the send buffer is cleared and filled with the next layer 3 message from the send queue. + +#### 8.4.3.2 Suspension + +A layer 3 entity in the MS shall indicate a request for the suspension of multiple frame operation by use of the DL-SUSPEND-REQUEST primitive. The layer 2 entity, upon receipt of this primitive, shall act as follows: + +No further layer 3 messages shall be taken from the send queue for SAPI=0. + +- If there is a layer 3 message in the send buffer which has not yet been transmitted, it shall not be transmitted. The contents of the send buffer shall be put back to the first position of the send queue. The send and transmit buffers shall be cleared. A layer 3 message is considered to be transmitted as soon as its final segment has been transmitted at least once; it need not yet have been acknowledged. (This ensures that all segments of a segmented and possibly partly transmitted layer 3 message will be transmitted on the new channel. Those segments already transmitted and received on the network side will be discarded by the network upon release of the old channel because the layer 3 message is not yet complete). +- If there is a layer 3 message in the send buffer, the last segment of which has been transmitted but is not yet fully acknowledged, i.e. the frame carrying the last segment of the message has been transmitted but is not yet acknowledged, then the contents of the send buffer shall be put back to the first position of the send queue and the send and transmit buffers shall be cleared. +- The layer 2 entity shall then return a DL-SUSPEND-CONFIRM primitive to layer 3. + +The data link layer entity is now in the suspended state. the only difference to the multiple frame established state is that no UI frames and no I frames are transmitted (all SAPIs). + +The MS may now change to the new channel. + +#### 8.4.3.3 Resumption + +##### 8.4.3.3.1 Procedure after channel change + +This procedure is initiated by the DL-RESUME primitive. A data link layer entity shall initiate a request for the multiple frame operation by transmitting the SABM command. + +All existing exception conditions shall be cleared and the retransmission counter shall be reset. All outstanding DL-DATA- REQUEST primitives and layer 3 message units, which are not fully acknowledged, shall be saved. Any segmented layer 3 message unit, for which the last segment has not been received shall be discarded. + +The send buffer is cleared. + +A layer 3 message included in the DL-RESUME-REQUEST primitive (in general, ASSIGNMENT COMPLETE or HANDOVER COMPLETE) is put into the send buffer for transmission in acknowledged mode. + +Upon reception of UA response the data link layer shall: + +- reset T200; +- set send variable V(S), the receive state variable V(R) and the acknowledge state variable V(A) to 0; +- enter the multiple established state; +- confirm establishment to layer 3 using DL-ESTABLISH-CONFIRM; +- send the layer 3 message unit passed together with the DL-RESUME primitive. + +The data link layer shall then continue normal operation. + +##### 8.4.3.3.2 Procedure after returning to the old channel (MS only) + +This procedure is initiated by the DL-RECONNECT primitive. A data link layer entity shall initiate a request for the multiple frame operation by transmitting the SABM command. All existing exception conditions shall be cleared and the retransmission counter shall be reset. All outstanding DL-DATA-REQUEST primitives and layer 3 message units, which are not fully acknowledged, shall be saved; this does not include a message carried by a possible previous DL-RESUME-REQUEST. Any segmented layer 3 message units, for which the last segment has not been received shall be discarded. + +The send buffer is cleared. + +A layer 3 message included in the DL-RECONNECT-REQUEST primitive (in general, ASSIGNMENT FAILURE or HANDOVER FAILURE) is put into the send buffer for transmission in acknowledge mode. + +Upon reception of a UA response the data link layer shall: + +- reset T200; +- set send state variable V(S), the receive state variable V(R) and the acknowledge state variable V(A) to 0; +- enter the multiple frame established state; +- confirm establishment to layer 3 using DL-ESTABLISH-CONFIRM; +- send the layer 3 message unit passed together with DL-RECONNECT-REQUEST primitive. + +The data link layer shall then continue normal operation. + +### 8.4.4 Termination of multiple frame operation + +#### 8.4.4.1 General + +These procedures shall be used to terminate the multiple frame operation between the BS and a designated MS entity. + +A layer 3 entity shall indicate a request for termination of the multiple frame operation by use of the DL-RELEASE-REQUEST primitive. The DL-RELEASE-REQUEST primitive will contain a parameter indicating whether normal release or local end release shall take place. In the first case the data link layer will initiate the release procedure of sub-clause 8.4.4.2. In the second case the data link layer shall follow the procedures of sub-clause 8.4.4.4. + +If a physical channel is disconnected at the physical layer, layer 3 will request release (i.e. local end release) by issuing an MDL-RELEASE-REQUEST primitive. The actions to be taken are defined in sub-clause 8.4.4.4. + +All frames other than unnumbered frames received during the release procedure shall be ignored. + +For normal release the release procedure implies the discard of any outstanding DL-DATA-REQUEST primitive which has been invoked prior to the DL-RELEASE-REQUEST. It also implies the discard of any segmented layer 3 data units for which the last segment has not been received (see sub-clause 8.5.2 for the concatenation procedure). + +#### 8.4.4.2 Normal release procedure + +A data link layer entity shall initiate a request for release of multiple frame operation by transmitting the Disconnect (DISC) command with the P bit set to "1". Timer T200 shall then be set right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer. The retransmission counter shall be set to "0" (RC=0). + +A data link layer entity receiving a DISC command while in the multiple-frame-established state or timer recovery state shall transmit a UA response with the F bit set to the same binary value as the P bit in the received DISC command. A DL-RELEASE-INDICATION shall be passed to layer 3, timer T200 shall be reset and the idle state shall be entered. + +If the originator of the DISC command receives either: + +- a UA response with the F bit set to "1"; or +- a DM response with F bit set to "1", indicating that the peer data link layer entity was in the idle state, it shall reset timer T200 and inform the layer 3 entity using the primitive DL-RELEASE-CONFIRM. + +The data link layer entity which issued the DISC command will now be in the idle state. The conditions relating to this state are defined in sub-clause 8.4.5. + +The DL-RELEASE-INDICATION or - CONFIRM primitives shall contain an indication whether or not there are outstanding acknowledgements or unserved DL-DATA-REQUEST primitives. + +#### 8.4.4.3 Procedure on expiry of timer T200 for normal release + +If timer T200 expires before a UA or DM response is received, the originator of the DISC command shall: + +- retransmit the DISC command as defined in sub-clause 8.4.4.2; +- set timer T200 right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer; and +- increment the retransmission counter. + +If the data link layer entity has not received the correct response as defined in sub-clause 8.4.4.2, after N200 attempts to recover, the data link layer entity shall enter the idle state and inform the layer 3 entity using the primitive DL- RELEASE-CONFIRM and MDL-ERROR-IND with cause "Timer T200 expired (N200+1) times: perform abnormal release". + +The value of N200 is defined in sub-clause 8.8.2. + +#### 8.4.4.4 Local end release procedure + +When receiving a DL-RELEASE-REQUEST primitive from layer 3 with the release mode parameter set to "local end release", the data link layer shall in all states: + +- return a DL-RELEASE-CONFIRM primitive; +- enter the idle state without issuing any commands to the peer entity. + +The DL-RELEASE-CONFIRM primitive shall contain an indication whether or not there are outstanding acknowledgements or unserved DL-DATA-REQUEST primitives. + +When receiving an MDL-RELEASE-REQUEST primitive, the data link layer entity, when in the idle state, shall enter the null state. In all other states the data link layer shall: + +- if there is no outstanding DL-RELEASE-REQUEST primitive, issue a DL-RELEASE-INDICATION primitive to layer 3; +- if there is an outstanding DL-RELEASE-REQUEST primitive, issue a DL-RELEASE-CONFIRM primitive to layer 3; +- enter the null state without issuing any commands to the peer entity. + +NOTE: The null state is the state, as viewed from the data link layer, where no physical resource exists for the specific data link layer entity. + +### 8.4.5 Idle state + +While in the idle state: + +- the receipt of a DISC command shall result in the transmission of a DM response with the F bit set to the value of the received P bit; +- the receipt of an I frame or supervisory frame with the P bit set to "1" shall result in the transmission of a DM response with the F bit set to "1" (as defined in sub-clause 8.2.2); +- the content of any received I frame shall be discarded; +- on receipt of an SABM command, the procedures defined in sub-clause 8.4.1 shall be followed; +- on receipt of UI commands, the procedures defined in sub-clause 8.3 shall be followed; + +- all other frame types shall be discarded. + +### 8.4.6 Collision of unnumbered commands and responses + +Collision situations shall be resolved in the following way: + +#### 8.4.6.1 Identical transmitted and received commands + +If the transmitted and received unnumbered commands (SABM or DISC) are the same, the data link layer entities shall send the UA response at the earliest possible opportunity. The indicated state shall be entered after receiving the UA response. The data link layer entities shall each notify its respective layer 3 entity by means of the appropriate confirm primitive, i.e. DL-ESTABLISH-CONFIRM or DL-RELEASE-CONFIRM. + +#### 8.4.6.2 Different transmitted and received commands + +If the transmitted and received unnumbered commands (SABM or DISC) are different, the data link layer entities shall issue a DM response at the earliest possible opportunity. Upon receipt of a DM response with the F bit set to 1, the data link layer shall enter the idle state and notify layer 3 by means of the appropriate primitive. The entity receiving the DISC command will issue a DL-RELEASE-INDICATION primitive, while the other entity will issue a DL-RELEASE-CONFIRM primitive. + +Timer T200 shall be reset. + +#### 8.4.6.3 Unsolicited DM response and SABM or DISC command + +In order to avoid misinterpretation of the DM response received, a data link layer entity shall always send its SABM or DISC command with the P bit set to "1". + +A DM response with the F bit set to "0" colliding with the SABM or DISC command shall be ignored. + +## 8.5 Procedures for information transfer in multiple frame operation + +The procedures which apply to the transmission of I frames are defined below. + +NOTE: The term "transmission of an I frame" refers to the delivery of an I frame by the data link layer to the physical layer. + +### 8.5.1 Transmitting I frames + +Information received by the data link layer entity from a layer 3 entity by means of a DL-DATA-REQUEST primitive shall be transmitted in one or more I frames. If the layer 3 message unit consists of N201 or fewer octets, the message unit is to be contained in one I frame. The M bit of 6.7.2 shall be set to "0" in such I frames. If the layer 3 message unit exceeds N201 octets, the data link layer shall segment the message unit in such a way that all segments, possibly except the last segment, consist of N201 octets. + +The M bit of sub-clause 6.7.2 shall be set to "1" for each segment except for the last segment for which the M bit shall be set to "0". + +The parameter N201 is defined in sub-clause 8.8.3. + +When transmitting an I frame, the control field parameters N(S) and N(R) shall be assigned the values of the send and receive state variables V(S) and V(R), respectively. The value of the send state variable V(S) shall be incremented by 1 at the end of the transmission of the I frame. + +If timer T200 is not running at the time right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer., it shall be set. If timer T200 expires, the procedures defined in sub-clause 8.5.7 shall be followed. + +If the send state variable V(S) is equal to V(A) plus k (where k is the maximum number of outstanding I frames - see sub-clause 8.8.4), the data link layer entity shall not transmit any new I frames, but shall retransmit an I frame as a result of the error recovery procedures as described in sub-clauses 8.5.4 and 8.5.7. + +When the BS side or MS side is in the own receiver busy (note 2) condition, it may still transmit I frames, provided that a peer receiver busy condition does not exist. + +NOTE 1: Any DL-DATA-REQUEST primitive received while in the timer recovery condition shall be stored and serviced on clearance of this condition. + +NOTE 2: In the following text in the present document, the term own/peer receiver busy refers to the peer-to-peer flow control state in the data link layer entities. + +### 8.5.2 Receiving I frames + +When a data link layer entity is not in an own receiver busy condition and receives a valid I frame whose send sequence number is equal to the current receive state variable V(R), the data link layer entity shall: + +- if the M bit is set to "0", concatenate it with previously received frames with the M bit set to "1", if any, and pass the complete layer 3 message unit to the layer 3 entity using the primitive DL-DATA-INDICATION; +- if the M bit is set to "1", store the information field of the frame and concatenate it with previously received frames with the M bit set to "1", if any (Note: no information is passed to the layer 3 entity); +- increment by 1 its receive state variable V(R), and act as indicated below. + +NOTE: The M bit is defined in sub-clause 6.7.2. + +#### 8.5.2.1 P bit of the received I frame set to "1" + +If the P bit of the received I frame was set to "1", the data link layer entity shall respond to its peer in one of the following ways: + +- if the data link layer entity receiving the I frame is still not in an own receiver busy condition, it shall send an RR response with the F bit set to "1"; +- if the data link layer entity receiving the I frame enters the own receiver busy condition upon the receipt of the I frame, it shall send an RNR response with the F bit set to "1". + +#### 8.5.2.2 P bit of the received I frame set to "0" + +If the P bit of the received I frame was set to "0" and: + +- a) if the data link layer entity is still not in an own receiver busy condition: + - if no I frame is available for transmission or if an I frame is available for transmission but a peer receiver busy condition exists, the data link layer entity shall transmit an RR response with the F bit set to "0"; or + - if an I frame is available for transmission and no peer receiver busy condition exists, the data link layer entity shall transmit the I frame with the value of N(R) set to the current value of V(R) as defined in sub-clause 8.5.1 (this I frame then acknowledges the receipt of an I frame); or +- b) if, on receipt of this I frame, the data link layer entity is now in an own receiver busy condition, it shall transmit an RNR response with the F bit set to "0". + +When the data link layer entity is in an own receiver busy condition, it shall process any received I frame according to sub-clause 8.5.6. + +NOTE 1: The term "available for transmission" should be interpreted to mean available for transmission at the instant when the physical layer is ready to transmit the next frame. Making this decision as close as possible to that instant, will ensure minimum delay in the transmission of I frames. + +NOTE 2: Any I frame received in the timer recovery condition shall be handled as stated above. + +### 8.5.3 Receiving acknowledgement + +#### 8.5.3.1 On receipt of a valid I frame + +On receipt of a valid I frame or supervisory frame (RR, RNR or REJ), even in the own receiver busy or timer recovery conditions, the data link layer entity shall treat the N(R) contained in this frame as an acknowledgement for all the I frames it has transmitted with an N(S) up to and including the received N(R) - 1. The value of the acknowledge state variable V(A) shall be set to the value of N(R). When not in the timer recovery condition, the data link layer entity shall reset the timer T200 on receipt of a valid I frame or supervisory frame with N(R) higher than V(A) (actually acknowledging some I frames), or an REJ with an N(R) equal to V(A). + +NOTE 1: If a supervisory command frame with P bit set to "1" or an I frame command with P bit set to "1" has been transmitted and not acknowledged, by a supervisory frame response with F bit set to "1" timer T200 shall not be reset. + +NOTE 2: Upon the receipt of a valid I frame, timer T200 shall not be reset if the data link layer entity is in the peer receiver busy condition. + +If timer T200 has been reset by the receipt of an I, RR or RNR frame, and if there are outstanding I frames still unacknowledged, the data link layer entity shall set timer T200. If timer T200 then expires, the data link layer entity shall follow the recovery procedure as defined in sub-clause 8.5.7 with respect to the unacknowledged I frames. + +If timer T200 has been reset by the receipt of an REJ frame, the data link layer entity shall follow the retransmission procedures in sub-clause 8.5.4. + +#### 8.5.3.2 Receiving supervisory command frames with the P bit set to "1" + +When receiving supervisory command frames with the P bit set to "1", the following responses with the F bit set to "1" shall be given: + +- if the data link layer entity is neither in an own receiver busy condition nor in an N(S) sequence error exception condition, the appropriate supervisory response is the RR response; +- if the data link layer entity is not in an own receiver busy condition, but is in an N(S) sequence error exception condition (i.e. an N(S) sequence error has been detected but a REJ frame has not yet been transmitted), the appropriate supervisory response is the REJ response; +- if the data link layer is in its own receiver busy condition, the appropriate supervisory response is the RNR response. + +### 8.5.4 Receiving REJ frames + +#### 8.5.4.1 Receipt of a valid REJ frame + +On receipt of a valid REJ frame the data link layer entity shall act as follows: + +- if it is not in the timer recovery condition: + - clear an existing peer receiver busy condition; + - set its send state variable V(S) and its acknowledge state variable V(A) to the value of the N(R) contained in the REJ frame control field; + - reset timer T200; + - if it was an REJ command frame with the P bit set to "1", transmit an appropriate supervisory frame with the F bit set to "1" (see sub-clause 8.5.3.2); + - transmit the corresponding I frame as soon as possible as defined in sub-clause 8.5.1 taking into account the conditions given in sub-clause 8.5.4.2; + - if it was an REJ response frame with the F bit set to "1", notify a protocol violation to layer 3 by means of the MDL-ERROR-INDICATION primitive (cause: unsolicited supervisory response); + +- ii) if it is in a timer recovery condition and it was an REJ response frame with the F bit set to "1": + - clear an existing peer receiver busy condition; + - clear the timer recovery condition; + - set its send state variable V(S) and its acknowledge state variable V(A) to the value of the N(R) contained in the REJ frame control field; + - reset timer T200; + - transmit the corresponding I frame as soon as possible as defined in sub-clause 8.5.1 taking into account the conditions given in sub-clause 8.5.4.2; +- iii) if it is in a timer recovery condition and it was an REJ frame other than an REJ response with the F bit set to "1": + - clear an existing peer receiver busy condition; + - set its acknowledge state variable V(A) to the value of the N(R) contained in the REJ frame control field; and + - if it was an REJ command frame with the P bit set to "1", transmit an appropriate supervisory response frame with the F bit set to "1" (see sub-clause 8.5.3.2). + +If the network receives a valid REJ frame following the application of the *Repeated Downlink FACCH* functionality (see sub-clause 10), and if it can be established that this frame is resulting from the reception of a repeated FACCH block by the Mobile Station, then this REJ frame may be ignored by the network. + +NOTE: This case could typically occur when *Repeated Downlink FACCH* is used toward a Mobile Station not supporting the functionality (i.e. a pre-Release 6 Mobile Station). + +#### 8.5.4.2 Transmitting frames + +When transmitting frames the following conditions are to be observed: + +- 1) if the data link layer entity is transmitting a supervisory frame when it receives the REJ frame, it shall complete that transmission before commencing transmission of the requested I frame; +- 2) if the data link layer entity is transmitting an SABM or DISC command or a UA or DM response when it receives the REJ frame, it shall ignore the request for retransmission; +- 3) if the data link layer entity is not transmitting a frame when the REJ is received, it shall immediately commence transmission of the requested I frame. + +All outstanding unacknowledged I frames, commencing with the I frame identified in the received REJ frame, shall be transmitted. Other I frames not yet transmitted may be transmitted following the transmitted I frames. + +### 8.5.5 Receiving RNR frame + +After receiving a valid RNR command or response, provided that the data link layer entity is not engaged in a mode setting operation, the data link layer entity shall set a peer receiver busy condition. + +For RNR commands/responses with the P/F bit set to 1, the following special conditions apply: + +- if it was an RNR command with the P bit set to "1", it shall respond with an RR response with the F bit set to "1" if the data link layer entity is not in an own receiver busy condition, and shall respond with an RNR response with the F bit set to "1" if the data link layer entity is in an own receiver busy condition; +- if it was an RNR response with the F bit set to "1" and timer recovery condition exists, the timer recovery condition shall be cleared and the N(R) contained in this RNR response shall be used to update the send state variable V(S). + +The data link layer entity shall take note of the peer receiver busy condition and not transmit any I frame towards the peer having indicated a busy condition. + +NOTE 1: This condition may not apply if the protocol operation on SAPI=0 and SAPI=3 is implemented (see sub-clause 9). + +NOTE 2: The N(R) in any received supervisory command, irrespective of the setting of the P bit, will not be used to update the send state variable V(S). + +The data link layer entity shall then: + +- treat the receive sequence number N(R) contained in the received RNR frame as an acknowledgement for all the I frames that have been transmitted or retransmitted with an N(S) up to and including N(R) -1, and set its acknowledge state variable V(A) to the value of the N(R) contained in the RNR frame; and +- set timer T200 unless a supervisory response frame with the F bit set to "1" is still expected. + +If timer T200 expires, the data link layer entity shall: + +- if it is not yet in a timer recovery condition, enter a timer recovery condition, and set the retransmission count variable to 0; +- if it is already in a timer recovery condition, add one to its retransmission count variable. + +The data link layer entity shall then: + +- if the value of the retransmission count variable is less than N200, transmit an appropriate supervisory command (see sub-clause 8.5.3.2) with the P bit set to "1", and set timer T200 right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer; or +- if the value of the retransmission count variable is equal to N200, it shall initiate the abnormal release procedure described in sub-clause 8.6. Layer 3 shall be notified via the MDL-ERROR-INDICATION primitive with cause "timer T200 expired N200 + 1 times: perform abnormal release". + +The peer data link layer entity receiving the supervisory frame with the P bit set to "1" shall respond, at the earliest opportunity, with the appropriate supervisory response frame (see sub-clause 8.5.3.2) with the F bit set to "1", to indicate whether or not its own receiver busy condition still exists. + +Upon receipt of the supervisory response with the F bit set to "1", the data link layer entity shall reset timer T200, and: + +- if the response is an RR or REJ response, the peer receiver busy condition is cleared and the data link layer entity may transmit new I frames or retransmit I frames as defined in sub-clauses 8.5.1 or 8.5.4, respectively; or +- if the response is an RNR response, the data link layer entity receiving the response shall proceed according to sub-clause 8.5.5, first paragraph. + +If a supervisory command (RR, RNR or REJ) with the P bit set to "0" or "1", or a supervisory response frame with the F bit set to "0" is received during the enquiry process, the data link layer entity shall: + +- if the supervisory frame is an RR or REJ command or response frame with the F bit set to "0", clear the peer receiver busy condition and if the supervisory frame was a command with the P bit set to "1", transmit the appropriate supervisory response (see sub-clause 8.5.3.2) frame with the F bit set to "1". However, the transmission or retransmission of I frames shall not be undertaken until the appropriate supervisory response frame with the F bit set to "1" is received or until the expiry of timer T200; or +- if the supervisory frame is an RNR command or an RNR response with the P/F bit set to "0", retain the peer receiver busy condition, and if the supervisory frame received was an RNR command with the P bit set to "1", transmit the appropriate supervisory response (see sub-clause 8.5.3.2) with the F bit set to "1". + +Receiving an SABM command, the data link layer entity shall clear the peer receiver busy condition. + +### 8.5.6 Data link layer own receiver busy condition + +When the data link layer entity enters an own receiver busy condition, it shall transmit an RNR frame at the earliest opportunity. The RNR frame may be either: + +- an RNR response with the F bit set to "0"; or +- if this condition is entered when receiving a command frame with the P bit set to "1", an RNR response frame with the F bit set to "1"; or +- if this condition is entered on expiry of timer T200, an RNR command with the P bit set to "1". + +All received I frames with the P bit set to "0" shall be discarded, after updating the acknowledge state variable V(A). + +All received supervisory frames with the P/F bit set to "0" shall be processed, including updating the acknowledge state variable V(A). + +All received I frames with the P bit set to "1" shall be discarded, after updating the acknowledge state variable V(A). However, an RNR response frame with the F bit set to "1" shall be transmitted. + +All received supervisory frames with the P bit set to "1" will be processed including updating the acknowledge state variable V(A). An RNR response with the F bit set to "1" shall be transmitted. + +To indicate to the peer data link layer entity the clearance of the own receiver busy condition, the data link layer entity shall transmit an RR frame, or, if a previously detected N(S) sequence error has not yet been reported, an REJ frame with the N(R) set to the current value of the receive state variable V(R). + +The transmission of an SABM command or a UA response (in reply to an SABM command) also indicates to the peer data link layer entity the clearance of the own receiver busy condition. + +### 8.5.7 Waiting acknowledgement + +The data link layer entity shall maintain an internal retransmission count variable. + +If timer T200 expires, the data link layer entity shall: + +- if it is not yet in the timer recovery condition, enter the timer recovery condition and set the retransmission count variable to 0; or +- if it is already in the timer recovery condition, add one to its retransmission count variable. + +The data link layer entity shall then: + +- a) if the value of the retransmission count variable is less than N200: + - retransmit the last transmitted I frame (V(S)-1) with the P bit set to "1"; or + - send the appropriate supervision frame, with the P bit set to "1"; + - set timer T200 right before transmitting a frame, when the PH-READY-TO-SEND primitive is received from the physical layer; or +- b) if the value of the retransmission count variable is equal to N200, indicate this by means of the primitive MDL-ERROR-INDICATION with cause "timer T200 expired N200 + 1 times: perform abnormal release" to layer 3. + +NOTE: It is then the responsibility of layer 3 to release or re-establish the data link. The data link layer remains in the timer recovery state until further actions are taken by layer 3. + +The following paragraph applies only for data link layer being in the timer recovery condition as the case of receiving acknowledgement in multiframe established state is described in sub-clause 8.5.3.1. + +The timer recovery condition is only cleared if the data link layer entity receives a valid supervisory frame response with the F bit set to "1". If the N(R) of this received supervisory frame is within the range from its current state variable V(A) to its current send state variable V(S) inclusive, it shall set its send state variable V(S) to the value of the received N(R). Timer T200 shall be reset if the received supervisory frame response is an RR or REJ response with F bit set to "1". The data link layer entity shall then resume with I frame transmission or retransmission, as appropriate. + +Timer T200 shall be set if the received supervisory response is an RNR response, and the data link layer shall proceed with the enquiry process in accordance with sub-clause 8.5.5. + +### 8.5.8 Preemption + +The preemption capability allows high priority layer 3 messages to avoid significant queuing delay at layer 2 due to the transmission of preceding low priority layer 3 messages. + +#### 8.5.8.1 Sender Requirements + +If higher layers do not send any message defined in 3GPP TS 44.018 to have a "low" priority, the data link layer may treat all layer 3 messages as having "normal" priority. This provides backward compatibility with previous versions of this standard. + +For multiple frame operation on SAPI 0, the Layer 3 shall indicate the priority of each message by providing a priority value in a DL-DATA-REQUEST primitive. Layer 3 messages with a priority value of "high" are allowed to preempt preceeding untransmitted and partially transmitted layer 3 messages with a priority value of "low". Layer 3 messages with a priority value of "normal" shall neither preempt not be preempted by other Layer 3 messages. + +On receiving a DL-DATA-REQUEST carrying a Layer 3 message with a "high" priority value, the data link layer entity shall discard all preceeding untransmitted Layer 3 messages using the same data link layer connection (i.e. same SAPI and channel) that have a "low" priority value. Layer 3 messages with a "low" priority value whose entire contents have been transmitted, but for which acknowledgements are still outstanding, shall not be affected. If there is any layer 3 message (at most one) with a "low" priority value for which some but not all octets were transmitted, the data link layer shall discard all untransmitted octets following the first N201 untransmitted octets if the total number of untransmitted octets exceeds N201. If there are N201 or fewer untransmitted octets, no data shall be discarded. When untransmitted octets are discarded, the remaining N201 untransmitted octets shall be transmitted when permitted by flow control in a single I frame with the M bit set to "0". + +Low priority data that is not discarded (i.e. previously transmitted but unacknowledged data and up to N201 octets of untransmitted data) shall be retransmitted if necessary until acknowledged by receiving data link layer entity. + +#### 8.5.8.2 Receiver Requirements + +The receiving data link layer entity is not affected by, nor aware of, preemption at a sender. Detection of and recovery from preemption is the responsibility of the higher layers. The procedures employed at the data link layer ensure that when a "low" priority message is truncated, at least the first 2\*N201 octets are delivered reliably to the receiving layer 3. + +## 8.6 Abnormal release and re-establishment of multiple frame operation + +### 8.6.1 Criteria for re-establishment + +The procedures for re-establishing the multiple frame operation are initiated by: + +- the receipt of a DL-ESTABLISH-REQUEST; +- the receipt, while in the multiple frame established or timer recovery state, of an SABM command. + +### 8.6.2 Criteria for abnormal release + +The procedures for abnormal release of the multiple frame operation are initiated by: + +- the receipt of a frame containing an invalid N(R) (see note); +- the receipt, while in the multiple-frame-established state, of an unsolicited DM response with the F bit set to "0". + +A valid N(R) is one that is in the range $V(A) \leq N(R) \leq V(S)$ . + +NOTE: These inequalities shall be interpreted in the following way: + $N(R)$ is called valid, if and only if $(N(R) - V(A)) \bmod 8 \leq (V(S) - V(A)) \bmod 8$ . + +### 8.6.3 Procedures for re-establishment + +When the data link layer receives in the multiple frame established state or timer recovery state a DL-ESTABLISH- REQUEST primitive from layer 3 or an SABM (with L=0), the normal establishment procedure of sub-clause 8.4.1.2 shall be initiated. Any information frames in the I queue (including I frames for DL-DATA-REQUEST primitives and any received segmented layer 3 message units for which the last segment has not been received) shall be discarded. + +A DL-ESTABLISH-INDICATION or -CONFIRM primitive sent to layer 3 shall contain an indication whether or not there are outstanding acknowledgements or unserved DL-DATA-REQUEST primitives. + +### 8.6.4 Procedures for abnormal release + +The data link layer shall inform layer 3 that an exception condition exists from which the data link layer cannot recover. The information is provided in an MDL-ERROR- INDICATION primitive with causes "sequence error: perform abnormal release" or "unsolicited DM response, multiple frame established state: perform abnormal release". + +The release of the data link shall then be performed by layer 3 by either of the following primitives: + +- DL-RELEASE-REQUEST (release mode=normal release). Then the data link layer shall follow the procedures of sub-clause 8.4.4.2. +- DL-RELEASE-REQUEST (release mode=local end release). Then the data link layer shall follow the procedure of sub-clause 8.4.4.4. +- MDL-RELEASE-REQUEST. Then the data link layer shall follow the procedure of sub-clause 8.4.4.4. + +The data link layer shall remain in the same state (i e multiple frame established or timer recovery) until the primitive is received. + +## 8.7 Exception condition reporting and recovery for multiple frame operation + +Exception conditions may occur as the result of physical layer errors or data link layer procedural errors. + +The error recovery procedures which are available to effect recovery following the detection of an exception condition at the data link layer are defined in this sub-clause. + +### 8.7.1 N(S) sequence error + +An N(S) sequence error exception condition occurs in the receiver when a valid I frame is received which contains an N(S) value which is not equal to the receive state variable V(R) at the receiver. The information field of all I frames whose N(S) does not equal the receive state variable V(R) shall be discarded. + +The receiver shall not acknowledge (nor increment its receive state variable) the I frame causing the sequence error, nor any I frames which may follow, until an I frame with the correct N(S) is received. + +A data link layer entity which receives one or more I frames having sequence errors but otherwise error-free, or subsequent supervisory frames (RR, RNR and REJ), shall use the control field information contained in the N(R) field and the P or F bit to perform data link control functions; for example, to receive acknowledgement of previously transmitted I frames and to cause the data link layer entity to respond if the P bit is set to "1". Therefore, a retransmitted I frame may contain an N(R) field value and P bit that are updated from, and therefore different from, the ones contained in the originally transmitted I frame. + +The REJ frame is used by a receiving data link layer entity to initiate an exception condition recovery (retransmission) following the detection of an N(S) sequence error. + +Only one REJ exception condition for a given direction of information transfer shall be established at a time. + +A data link layer entity receiving an REJ command or response shall initiate sequential transmission (retransmission) of I frames starting with the I frame indicated by the N(R) contained in the REJ frame. + +An REJ exception condition is cleared when the requested I frame is received or when an SABM or DISC command is received. + +### 8.7.2 Timer recovery + +If a data link layer entity, due to a transmission error, does not receive a single I frame or the last I frame(s) in a sequence of I frames, it will not detect an out-of-sequence exception condition and therefore will not transmit a REJ frame. + +The data link layer which transmitted the unacknowledged I frame(s) shall, on the expiry of timer T200, take appropriate recovery action as defined in sub-clause 8.5.7 to determine at which I frame retransmission must begin. + +### 8.7.3 Invalid frame condition + +Any frame received which satisfies one or more of the following conditions shall be discarded after notification to layer 3 by means of the primitive MDL-ERROR-INDICATION (with cause as indicated): + +- a supervisory or unnumbered frame with incorrect parameters (e.g. a length indicator $L > 0$ in frames where an information field is not permitted, an M bit set to "1", a length indicator set to $L > N201$ in frames permitted with an information field) (causes "S frame with incorrect parameters" and "U frame with incorrect parameters", respectively); +- an I frame with length indicator which indicates more than N201 octets in the frame (cause "I frame with incorrect length"); +- an I frame with the M bit set to "1" and the length indicator set to less than N201 octets (cause "I frame with incorrect use of M bit"); +- a command or response frame with a control field which is not implemented (cause "frame not implemented"). + +No other action shall be taken as a result of such frames, i.e. information fields shall be discarded and N(S) fields, N(R) fields and P/F bits shall be ignored. + +### 8.7.4 N(R) sequence error + +An N(R) sequence error exception condition occurs in the transmitter when a valid supervisory frame or I frame is received which contains an invalid N(R) value. + +A valid N(R) is one that is in the range $V(A) \leq N(R) \leq V(S)$ . + +NOTE: These inequalities shall be interpreted in the following way: + N(R) is called valid, if and only if $(N(R) - V(A)) \bmod 8 \leq (V(S) - V(A)) \bmod 8$ . + +The information field contained in an I frame which is correct in sequence and format but contains an invalid N(R) shall be delivered to layer 3 by means of the primitive DL- DATA-INDICATION (if it contains a complete layer 3 message unit or the last segment of a segmented layer 3 message unit; otherwise the information field is discarded) and a P bit set to "1" shall be processed before taking subsequent actions. + +The data link layer entity shall then inform layer 3 on this exception condition by means of the primitive MDL-ERROR- INDICATION with the cause "sequence error: perform abnormal release", as defined in 8.6.4. The data link shall remain in the current state until it is released by layer 3. + +## 8.8 List of system parameters + +The system parameters listed below are associated with each individual service access point and apply to both unacknowledged operation and multiple frame operation. + +NOTE 1: The only parameter required for unacknowledged operation is the maximum number of octets in the information field (sub-clause 8.8.3). + +NOTE 2: The values given below for the parameters may be changed as a result of optimization of the system performance. + +### 8.8.1 Timer T200 + +#### 8.8.1.1 For SAPI=0 and SAPI=3 + +The exact value of timer T200 for data links with SAPI=0 and SAPI=3 is implementation dependent. It depends on synchronization mechanisms and processing delays both in layer 1 and layer 2 entities. Generally, it shall be chosen such that a predictable behaviour at the Um reference point can be guaranteed. The general principles for choosing a value for timer T200 are: + +- a possible loss of frames on the radio path should be detected as soon as possible; +- a necessary retransmission of a frame should take place at the earliest possible opportunity; +- the use of Repeated Downlink FACCH (see sub-clause 10); +- T200 shall not time out before the next frame in the other direction is received and treated, assuming some reasonable response delays for the peer entities (see sub-clause 8.9); +- if T200 times out, provided no other frame takes priority, the repeated frame is sent in the block following immediately after the next PH-READY-TO-SEND indication. + +Values of T200 shall be chosen implementation dependent for the various types of channels according to the rules given above and the performance requirements of sub-clause 8.9. + +#### 8.8.1.2 For SAPIs other than 0 or 3 + +The value of timer T200 for data links with SAPIs other than 0 or 3 is for further study. + +### 8.8.2 Maximum number of retransmissions (N200) + +#### 8.8.2.1 For SAPI=0 and 3 + +For SAPI=0 and 3, the maximum number of retransmissions N200 depends on the state and on the channel used. This ensures a common time value for layer 2 link failure on all channels when multiple frame operation is established. The N200 value for layer 2 link establishment and release is 5. + +In the state "timer recovery", N200 is set to: + +- 5 for use on SACCH; +- 23 for use on SDCCH; +- 34 for use on FACCH/full rate (Note 1); +- 48 for use on E-FACCH/full rate; +- 29 for use on FACCH/half rate. + +NOTE 1: All types of FACCH/Full rate except E-FACCH/F. + +#### 8.8.2.2 For SAPIs other than 0 or 3 + +For SAPIs other than 0 or 3, the value of N200 is 5. + +### 8.8.3 Maximum number of octets in an I, UI, SABM and UA frame partially or entirely available for the information field (N201) + +The maximum number of octets partially or entirely available for the information field (N201) is: + +- for frames of format A and B: + - for the SACCH: N201 = 18; + - for the FACCH and SDCCH: N201 = 20. + +- for frames of format Bbis: + - for BCCH, AGCH, NCH and PCH: N201 = 23; +- for frames of format Bter: + - for the SACCH: N201 = 21; + - for the FACCH and SDCCH: N201 = 23; +- for frames of format B4: + - for the SACCH: N201 = 19. + +### 8.8.4 Maximum number of outstanding I frames (k) + +The maximum number (k) of sequentially numbered I frames that may be outstanding (that is, unacknowledged) at any given time is a system parameter which shall not exceed 7. + +For data links with SAPI=0 or 3 (see sub-clause 9), the value of k shall be k = 1. + +The value of k for other values of SAPI is for further study. + +### 8.8.5 Maximum number of octets in a Layer 3 message + +The number of octets in a L3-message passed to layer 2 for transmission in acknowledged mode shall not exceed 251, due to corresponding limits in 3GPP TS 48.056. + +The number of octets in a L3-message passed to layer 2 for transmission in unacknowledged mode is limited by the maximum number of octets in the information field of an UI-frame, as defined in sub-clause 8.8.3. + +## 8.9 System performance requirements + +An implementation of data link layer service for SAPI=0 and SAPI=3 consisting of a data link layer entity and an entity necessary for physical transmission on the GSM radio channels, shall have sufficient processing capacity to satisfy the following performance requirements. Those requirements are to be satisfied by a local implementation without reference to the (remote) peer implementation: + +- Available response delay: + +If a data link entity receives a data link command frame requesting response whose last burst has been physically transmitted in the TDMA frame number FNcomm, then the first burst carrying a segment of the corresponding data link response shall be physically transmitted in the TDMA frame number FNresp, where: + +$$FNresp \leq FNcomm + Tresp + 1;$$ + +and Tresp denotes the number of TDMA frames corresponding to the available response delay for the logical channel in use, as indicated in table 8. When Repeated Downlink FACCH is used (see clause 10) to send a command frame, FNcomm denotes the TDMA frame number of the last burst of the FACCH block used to recover the LAPDm frame. When Repeated Downlink FACCH is used to send a response frame (see clause 10), FNresp denotes the TDMA frame number of the first burst of the FACCH block used to send the first instance of the repeated LAPDm frame. + +- Observable repetition delay: + +if a data link entity transmits a data link command frame whose first burst is physically contained in the TDMA frame number FNcomm1, then in case of retransmission the first burst carrying a segment of the retransmitted data link command frame shall be contained in the TDMA frame number FNcomm2 satisfying; + +$$FNcomm1 + Trmin \leq FNcomm2 \leq FNcomm1 + Trmax;$$ + +where Trmin resp. Trmax denote the number of TDMA frames corresponding to the minimum resp. maximum observable repetition delay for the logical channel in use, as indicated in table 8. When Repeated Downlink FACCH is used (see clause 10) to send a command frame, FNcomm1 denotes the TDMA frame number of the first burst of the FACCH block used to send the repeated LAPDm frame. + +NOTE: Arithmetics on TDMA frame numbers as specified in 3GPP TS 45.002 operates modulo $(FN\_MAX+1) = 2715648$ . + +**Table 8: Performance Parameters** + +| SAPI | Type of channel | Available Response Delay Tresp | Minimum Repetition Delay Trmin | Maximum Repetition Delay Trmax (Note 3) | +|------|--------------------------|--------------------------------|--------------------------------|-----------------------------------------| +| 0 | SDCCH | MS: 11
BSS: 32 | 51 | 51 | +| 0 | FACCH/Full rate (Note 4) | 9 | 26 | 39 | +| 0 | E-FACCH/Full rate | 9 | 17 | 26 | +| 0 | FACCH/Half rate | 10 | 34 | 44 | +| 3 | SDCCH | MS: 11
BSS: 32 | 51 | 51 (Note 1) | +| 3 | SACCH (with TCH) | 25/129 (Note 2) | 312 | 416 (Note 2) | + +Values given in this table are measured in units of TDMA frame numbers, thus 1 unit corresponds to 120/26 ms (approx. 4.615 ms). + +NOTE 1: Only applicable if no SAPI 0 transmission is in progress. Otherwise no upper bound can be given due to the priority of SAPI 0 transmission. + +NOTE 2: This higher value is only applicable when the physical channel was not available for SAPI=3 due to the transmission of a SAPI=0 frame. + +NOTE 3: Only applicable if, when available for transmission, there is no supervisory frame with F=1 to send (see for example sub-clause 8.5.2.1). + +NOTE 4: All types of FACCH/Full rate except E-FACCH/F. + +# 9 Special protocol operation on SAPI=0 and SAPI=3 + +This sub-clause summarizes the specialities of the LAPDm protocol regarding the acknowledged mode operation on SAPI=0 and SAPI=3. + +The purpose is to adapt the multiple frame operation of LAPDm to the needs and the characteristics of the GSM system. + +The adaptations and simplifications specified in this sub-clause are mandatory for both entities, Mobile Station and Network for SAPI=0 and SAPI=3. + +As indicated in sub-clause 8, the protocol operates on SAPI=0 in the following way: + +- Data link establishment for SAPI=0 is always initiated by the Mobile Station. +- Data link establishment according to the contention resolution procedure (see sub-clause 8.4.1.4) is supported when initiated by the MS on the main DCCH immediately after "immediate assignment" of that radio channel. In other cases of link establishment contention resolution is not used. +- When changing the radio channel during assignment or handover procedures (layer 3 procedures), in acknowledged mode on SAPI=0, the MS supports continuous transmission of layer 3 messages without loss by offering the SUSPEND, RESUME and RECONNECT primitives, as specified in sub-clause 8.4.3. However, duplication of at most one layer 3 data unit (in the MS to network direction) is possible. + +For protocol operation on SAPI=0 as well as on SAPI=3 the following holds: + +- For multiple frame operation, the window size $k = 1$ shall be used. +- The data link layer entity is not allowed to transmit an RNR frame and therefore shall never enter the own-receiver busy state. The same applies to the peer-receiver-busy condition. This is applicable, because buffer capacities necessary for avoiding such exception conditions are limited. +- When receiving, the data link layer entity may ignore RNR frames without notification. +- The procedure of enquiring the peer entity status by spontaneous transmission of a RR or REJ command frame, as indicated in sub-clauses 6.8.5 and 6.8.7, need not be supported. However, reaction on receiving such frames shall be as specified throughout the present document. + +# --- 10 Repeated Downlink FACCH + +## 10.1 General + +The Repeated Downlink FACCH functionality is applicable when sending LAPDm frames on the TCH/F or TCH/H channel (excluding O-TCH and E-TCH channels). An MS supporting the TCH/F or TCH/H, as described above, shall support the Repeated Downlink FACCH functionality. The BSS may use the Repeated Downlink FACCH functionality when it considers it to be appropriate. + +## 10.2 The FACCH Repetition + +A repeated FACCH block shall be sent in such a way that, if the first burst of the downlink FACCH block containing the first instance of a LAPDm frame is sent in TDMA frame M, the first burst of the downlink FACCH block containing the repeated instance of the LAPDm frame is sent in TDMA frame M+8 or M+9 (the latter corresponding to the case where the two FACCH blocks are separated by either a SACCH frame or an idle frame, see 3GPP TS 45.002). + +NOTE: On a channel using Repeated Downlink FACCH the value of T200 should be increased to cope with the case where the receiving entity failed to decode the downlink FACCH block used to send the first instance of a repeated LAPDm frame. This applies to a BSS supporting Repeated Downlink FACCH and to an MS that has signalled the Repeated ACCH Capability bit as '1' (see 3GPP TS 24.008). + +## 10.3 BSS requirements + +The BSS may, based on implementation-dependent criteria (e.g. downlink measurements), decide to repeat any downlink LAPDm command frame sent in a FACCH block over the radio interface. If the MS has signalled the Repeated ACCH Capability bit as '1' (see 3GPP TS 24.008), the BSS may also, based on implementation-dependent criteria, decide to repeat any downlink LAPDm response frame sent in a FACCH block over the radio interface. In both cases, the repeated FACCH block shall be sent as specified in sub-clause 10.2. + +NOTE: If an MS has not signalled a Repeated ACCH Capability bit as '1' the BSS may only use Repeated Downlink FACCH to send command frames. + +## 10.4 MS requirements + +The MS shall, when receiving a downlink FACCH block, always attempt to decode it without combining with any previously received FACCH block. + +If the current FACCH block is successfully decoded and an identical FACCH block was previously received (successfully decoded and spaced in time from the current FACCH block as specified in sub-clause 10.2), the MS shall not send the LAPDm frame of the current FACCH block to the LAPDm entity. + +If the current FACCH block is successfully decoded and there was no such previously received identical FACCH block the LAPDm frame of the current FACCH block is sent to the LAPDm entity. + +If the current FACCH block is unsuccessfully decoded and there was an unsuccessfully decoded FACCH block spaced in time from the current FACCH block as specified in sub-clause 10.2, a new decoding using the information from both these FACCH blocks shall be performed. If this decoding is successful the LAPDm frame produced by the new decoding is sent to the LAPDm entity. + +# --- 11 Repeated SACCH + +## 11.1 General + +The Repeated SACCH functionality is applicable when a layer 3 message unit is to be sent or received in a SAPI=0 frame (i.e. in unacknowledged mode) on the SACCH channel. The MS shall support the Repeated SACCH functionality. The BSS may use the Repeated SACCH functionality when it considers it to be appropriate. + +## 11.2 Procedure for Repeated SACCH on the downlink + +If a downlink SACCH block is incorrectly decoded (prior to combining with any previously received SACCH block), and the next uplink SACCH block is not a repetition as per the Repeated SACCH procedure (see sub-clause 11.3), then the MS shall set the SACCH Repetition Request in the next uplink SACCH block to "Repeated SACCH required" (see 3GPP TS 44.004). If a downlink SACCH block is correctly decoded (prior to combining with any previously received SACCH block), and the next uplink SACCH block is not a repetition as per the Repeated SACCH procedure (see sub-clause 11.3), the MS shall set the SACCH Repetition Request in the next uplink SACCH block to "Repeated SACCH not required". + +At the BSS side, if a transmitted downlink SACCH block contains a SAPI 0 frame and is not already a repetition, then it is a repetition candidate. If a SACCH block is a repetition candidate then the BSS may, based on the value of the last correctly received SACCH Repetition Request from the MS, or based on implementation-dependent criteria, repeat this SACCH block at the next SACCH period. If a SAPI 3 frame was also scheduled to be sent at this next SACCH period, the BSS may delay the sending of the SAPI 3 frame by one SACCH period in order to make room for the repetition. + +When receiving a downlink SACCH block, the MS shall first attempt to decode it without combining with any previously received SACCH block. If this decoding fails, then a new decoding using the information from this SACCH block and from the SACCH block received at the previous SACCH block period shall be performed. + +## 11.3 Procedure for Repeated SACCH on the uplink + +The BSS may set the value of the SACCH Repetition Order (see 3GPP TS 44.004) of any downlink SACCH block based on implementation-dependent criteria. + +At the MS side, if a transmitted uplink SACCH block contains a SAPI 0 frame and is not already a repetition, then it is a repetition candidate. If a SACCH block is a repetition candidate and if the last correctly received SACCH Repetition Order was set to "Repeated SACCH required", then the MS shall repeat this SACCH block at the next SACCH block period. If a SAPI 3 frame was also scheduled to be sent at this next SACCH period, the MS shall delay the sending of the SAPI 3 frame by one SACCH period in order to make room for the repetition. + +When receiving an uplink SACCH block, the BSS may first attempt to decode it without combining with any previously received SACCH block. If this decoding fails, then a new decoding using the information from this SACCH block and from the SACCH block received at the previous SACCH block period may be performed. + +# --- Annex A (normative): Random access procedures + +## A.1 Description of the procedure + +### A.1.1 Procedure in the MS + +The random access procedure is initiated by layer 3. The data link layer will receive the 8 bit information content of the random access burst in a DL-RANDOM ACCESS-REQUEST primitive. The primitive will also contain an indication of the type of channel to be used. The data link layer will then pass the information field to the indicated physical layer entity in a PH-RANDOM ACCESS-REQUEST primitive. + +The physical layer will, upon sending the random access burst, send a PH-RANDOM ACCESS-CONFIRM primitive containing the time slot in which the burst was sent. This information is passed then to layer 3 in a DL-RANDOM ACCESS-CONFIRM primitive. + +### A.1.2 Procedure in the BS + +The physical layer will provide the random access information field and an indication of the time slot in which the random access burst was received to the data link layer in a PH-RANDOM ACCESS-INDICATION primitive. The primitive will also contain an indication of the type of channel on which the burst was received. The data link layer will pass the information to layer 3 in a DL-RANDOM-ACCESS-INDICATION primitive. + +## --- A.2 Format + +The format of the random access message at the data link layer consists of 8 bits. The order of bit transmission is defined in 3GPP TS 44.004. + +# --- Annex G (normative): Handling of frames with parameter errors in the address, control and length indicator fields + +## G.1 General + +The parameters contained in frames received with parameter errors in the address, control and length indicator fields shall be ignored and an information field shall be discarded. + +For some parameter errors an indication is given to the mobile management entity in an MDL-ERROR-INDICATION primitive. + +## --- G.2 Parameter errors in the address field + +### G.2.1 Unallocated SAPI + +No action shall be taken on frames containing an unallocated SAPI. + +### G.2.2 Wrong value of the C/R bit + +- I frame, C/R bit indicates response; +- SABM frame, C/R bit indicates response; +- UI frame, C/R bit indicates response; +- UA frame, C/R bit indicates command; +- DISC frame, C/R bit indicates response; +- DM frame, C/R bit indicates command. + +Actions: + +- An MDL-ERROR-INDICATION primitive with cause "frame not implemented" is sent to the mobile management entity. + +### G.2.3 EA bit set to "0" + +Frames with EA bit set to "0" are not allowed in the GSM system. + +Actions: + +- An MDL-ERROR-INDICATION primitive with cause "frame not implemented" is sent to the mobile management entity. + +## --- G.3 Parameter errors in the control field + +### G.3.1 Supervisory frames + +The control field coding: + +bit 8 7 6 5 4 3 2 1 + +N(R) P/F 1 1 0 1 + +is not allowed: + +Actions: + +- An MDL-ERROR-INDICATION primitive with cause "frame not implemented" is sent to the mobile management entity. + +### G.3.2 Unnumbered frames + +The control field coding. + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----|---|---|---|-----|---|---|---|---| +| | x | x | x | P/F | 1 | 0 | 1 | 1 | +| | x | x | x | P/F | 0 | 1 | 1 | 1 | +| | 0 | 1 | 0 | P/F | 1 | 1 | 1 | 1 | +| | 0 | 1 | 1 | P/F | 1 | 1 | 1 | 1 | +| | 1 | 0 | 0 | P/F | 1 | 1 | 1 | 1 | +| | 1 | 0 | 1 | P/F | 1 | 1 | 1 | 1 | +| | 1 | 1 | 0 | P/F | 1 | 1 | 1 | 1 | +| | 1 | 1 | 1 | P/F | 1 | 1 | 1 | 1 | +| | 0 | 0 | 1 | P/F | 0 | 1 | 1 | 1 | +| | 0 | 0 | 1 | P/F | 0 | 0 | 1 | 1 | +| | 1 | 0 | 0 | P/F | 0 | 0 | 1 | 1 | +| | 1 | 0 | 1 | P/F | 0 | 0 | 1 | 1 | +| | 1 | 1 | 0 | P/F | 0 | 0 | 1 | 1 | +| | 1 | 1 | 1 | P/F | 0 | 0 | 1 | 1 | + +are not allowed. + +Actions: + +- An MDL-ERROR-INDICATION primitive with cause "frame not implemented" is sent to the mobile management entity. + +## G.4 Parameter errors in the length indicator field + +### G.4.1 EL bit error + +If the EL bit is set to "0", an MDL-ERROR-INDICATION primitive with cause "frame not implemented" is sent to the mobile management entity. + +### G.4.2 Information frames + +If the length indicator of an I frame is set to a numerical value $L > N201$ or $L = 0$ , an MDL-ERROR-INDICATION primitive with cause "I frame with incorrect length" is sent to the mobile management entity. + +If the numerical value of $L$ is $L < N201$ and the M bit is set to "1", then an MDL-ERROR-INDICATION primitive with cause "I frame with incorrect use of M bit" is sent to the mobile management entity. + +### G.4.3 Supervisory frames + +If a supervisory frame is received with $L > 0$ or with the M bit set to "1", an MDL-ERROR-INDICATION primitive with cause "S frame with incorrect parameters" is sent to the mobile management entity. + +### G.4.4 DISC and DM frames + +If a DISC or DM frame is received with $L > 0$ or with the M bit set to "1", an MDL-ERROR-INDICATION primitive with cause "U frame with incorrect parameters" is sent to the mobile management entity. + +### G.4.5 SABM UA and UI frames + +If SABM, UA or UI frames are received with $L > N201$ or with the M bit set to "1" an MDL-ERROR-INDICATION primitive with cause "U frame with incorrect parameters" is sent to the mobile management entity. + +# --- Annex C (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|----------|----|-----|----------------------------------------|--------| +| January 2016 | - | - | - | Version 13.0.0 based on version 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|--------|----------|----|-----|-----|----------------------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44012/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-16/44_series/44012/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aafa1500af156fc017ecd67037fd59c1ca77c22e --- /dev/null +++ b/marked/Rel-16/44_series/44012/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac351e4a29f68f9f18b4a1752846af85a07a5026556dc0f4a92d5948238e8452 +size 17040 diff --git a/marked/Rel-16/44_series/44012/5a24ac755b962fd5f0183f13de0726de_img.jpg b/marked/Rel-16/44_series/44012/5a24ac755b962fd5f0183f13de0726de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbb2bf027b135a1643fffa0c200207f6bb8d180b --- /dev/null +++ b/marked/Rel-16/44_series/44012/5a24ac755b962fd5f0183f13de0726de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dfc8fd5ef0f4a9dfc14a6fb019958316789a2d38224ab6e42bbb0db78401854 +size 17914 diff --git a/marked/Rel-16/44_series/44012/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/44_series/44012/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fe10fe8a9b7aaf1425be811332889eb9a869107 --- /dev/null +++ b/marked/Rel-16/44_series/44012/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68e8705c523a7a4c46ffdccbb440989493d95a2feb12919deb14fa49bd491005 +size 10809 diff --git a/marked/Rel-16/44_series/44012/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/44_series/44012/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d20a882d2d957822cfe5a591db7f408d4665fdde --- /dev/null +++ b/marked/Rel-16/44_series/44012/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19d2e59b7c0935609702c36031b29408fd8dd37bff82427dca6eb8fd1a0379ff +size 18777 diff --git a/marked/Rel-16/44_series/44012/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg b/marked/Rel-16/44_series/44012/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4b40530f3b5e07f0681ed929d94c031b020c0e7 --- /dev/null +++ b/marked/Rel-16/44_series/44012/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a13d5e52c6007415e1a51af122f11764ff870c37f24dd33aff18acbd5690bc3f +size 12012 diff --git a/marked/Rel-16/44_series/44012/cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg b/marked/Rel-16/44_series/44012/cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c15c9a81138e327c7845963a803731ba213fa0d --- /dev/null +++ b/marked/Rel-16/44_series/44012/cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38ac587db4723237afc77f5b14905c381f2addaefce1974dc8c171a02a9ff331 +size 15791 diff --git a/marked/Rel-16/44_series/44012/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-16/44_series/44012/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5da385d91059b8b08b8dfd8ecbf7133d1e59aadf --- /dev/null +++ b/marked/Rel-16/44_series/44012/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4386484b3719aefbd72c6f4767c6885e111c2ada264fdae77b6b68fb644282a4 +size 12490 diff --git a/marked/Rel-16/44_series/44012/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/marked/Rel-16/44_series/44012/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7efed4cd1346386fa635a7a2db68fd84454253fa --- /dev/null +++ b/marked/Rel-16/44_series/44012/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8372f57eee8eced15f45828e708dccd0716c10b52f755aa8ccba57bd4b29d78 +size 13196 diff --git a/marked/Rel-16/44_series/44012/fe61ee8618403cf584b2e28c4bada03a_img.jpg b/marked/Rel-16/44_series/44012/fe61ee8618403cf584b2e28c4bada03a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b3d0e05d830903fc8b8b4a48c8d016f2d0e2ace --- /dev/null +++ b/marked/Rel-16/44_series/44012/fe61ee8618403cf584b2e28c4bada03a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53805eed0a73330b91d25bae89932a3284533c880b1fc3c26b3469bba848ccbd +size 10562 diff --git a/marked/Rel-16/44_series/44012/raw.md b/marked/Rel-16/44_series/44012/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..df57db0dbf7070663b1d129d91a52939a8be88ce --- /dev/null +++ b/marked/Rel-16/44_series/44012/raw.md @@ -0,0 +1,440 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +Foreword ..... 4 + +1 Scope..... 5 + +1.1 References ..... 5 + +1.2 Abbreviations ..... 5 + +2 General description ..... 5 + +2.1 Scheduling Information..... 6 + +3 Message format on BTS-MS Interface ..... 6 + +3.1 General ..... 6 + +3.2 Format convention..... 7 + +3.2.1 Numbering convention ..... 7 + +3.2.2 Order of bit transmission ..... 7 + +3.3 Block content..... 7 + +3.3.1 Block Type ..... 7 + +3.4 SMSCB Message..... 8 + +3.5 Schedule Message ..... 8 + +3.5.1 Header..... 9 + +3.5.2 New CBSMS Message Bitmap ..... 9 + +3.5.3 New CBSMS Message Description..... 9 + +3.5.4 Other Message Descriptions ..... 10 + +3.5.5 Message description encoding..... 10 + +3.5.5.1 First transmission of an SMSCB within the Schedule Period ..... 10 + +3.5.5.2 Retransmission indication..... 11 + +3.5.5.3 Free Message Slot, optional reading..... 11 + +3.5.5.4 Free Message Slot, reading advised..... 11 + +3.5.5.5 Reserved Codepoints ..... 11 + +**Annex A (informative): Sample Implementation of SMSCB DRX Mode ..... 12** + +Annex B (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 + +## 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] Void. +- [3] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [4] 3GPP TS 44.004: "Layer 1; General requirements". +- [5] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". +- [6] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". + +## 1.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# 2 General description + +SMSCB is a service in which short messages may be broadcast from a PLMN to Mobile Stations (MS)s. SMSCB messages come from different sources (e.g. traffic reports, weather reports). The source and subject of the SMSCB message is identified by a message identifier in the SMSCB message header. A sequence number in the SMSCB message header enables the MS to determine when a new message from a given source is available. + +SMSCB messages are not acknowledged by the MS. Reception of SMSCB messages by the MS is only possible in idle mode. The geographical area over which each SMSCB message is transmitted is selected by the PLMN operator, by agreement with the provider of the information. + +A SMSCB message is an end-to-end message that is formatted by/for the SMSCB application, and which is intended for customer viewing. Its format is described in detail in 3GPP TS 23.041. A CB message is any message sent on the basic or extended CBCH (see 3GPP TS 45.002). It can be an occurrence of a SMSCB message, or a schedule message. + +The SMS Cell Broadcast service is designed to minimize the battery usage requirements for a MS. A MS can read the first part of a CB message and then decide whether or not to read the rest of the message. In addition, the network may broadcast Schedule Messages, providing information in advance about the CB messages that will be sent immediately afterwards. The MS may use this scheduling information to restrict reception to those messages the customer is interested in receiving. This SMSCB DRX feature is optional in the network and the MS. + +## 2.1 Scheduling Information + +The network supporting the SMSCB DRX feature transmits Schedule Messages. A Schedule Message includes information about a number of immediately following consecutive CB messages, planned for that cell. The length of time covered by the CB messages referred to in a Schedule Message is called the Schedule Period of that message. For optimum DRX, a new Schedule Message should follow the last message of a Schedule Period. When no information is known about a CB message, e.g. because no Schedule Message has been received referring to that CB message, a MS + +shall read (at least) the first part of the CB message. Schedule Messages shall be sent on the basic and extended CBCH independently. + +The network may override the published schedule to transmit new high-priority SMSCB messages. However, after any schedule deviation, the network shall resume the schedule, by transmitting the scheduled CB messages at the scheduled times listed in the Schedule Message. + +The Schedule Message contains a Message Description for each CB message to be broadcast during the scheduling period, in order of transmission. The position of a CB message is called the "message slot number" of the CB message, and it indicates the position of the CB message within the schedule period. Each Message Description includes various information, including for SMSCB messages directly or indirectly all or part of their message identifier, and whether an occurrence is a repetition or not. + +Each Schedule Message includes a Begin Slot Number field and an End Slot Number field. The End Slot Number field indicates the length of the schedule period (i.e. specifically the number of CB message slots about which information is provided). In the case where the network uses Schedule Messages to describe all message slots in advance, the first Schedule Message of the next schedule period will be transmitted in the message slot pointed by End Slot Number plus 1. The Begin Slot Number is defined to allow the network to broadcast several Schedule Messages referring to the same schedule period. The Begin Slot Number field indicates the message slot number of the CB message following the received Schedule Message. + +The networks may send unscheduled Schedule Messages during empty message slots. The network need only update the Begin Slot Number in an unscheduled Schedule Message to reflect the current offset within the Schedule Message of the next message to be transmitted. + +# 3 Message format on BTS-MS Interface + +## 3.1 General + +A CB message consists of a 88 octets of information. The 88 octet block is segmented into four 22 octet blocks. A 1 octet Block type is added as a header to each 22 octet block. The overall blocks are thus 23 octets in length. + +The message blocks are sent on the channel allocated as CBCH by 3GPP TS 45.002. The timing of the messages is defined in 3GPP TS 45.002. If the network has no cell broadcast information to transmit, then it may choose to transmit a null message. + +## 3.2 Format convention + +### 3.2.1 Numbering convention + +The basic convention used in this technical specification is illustrated in figure 1. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to 23. + +![](cfbf0f2ddbc35370b0b8c6d043f25eb2_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet: | +|---|---|---|---|---|---|---|---|--------| +| | | | | | | | | 1 | +| | | | | | | | | 2 | +| | | | | | | | | 23 | + +Figure 1: Format convention + +### 3.2.2 Order of bit transmission + +The message blocks are sent on the CBCH as defined in 3GPP TS 45.002 using the coding defined for that channel. + +The order of bit transmission is defined in 3GPP TS 44.004. + +## 3.3 Block content + +The 23 octet blocks are coded as follows. + +![](d793cf7c174b89eb024d132f00679787_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet: | +|-------------|---|---|---|---|---|---|---|--------| +| Block type | | | | | | | | 1 | +| Information | | | | | | | | 2 | +| | | | | | | | | 23 | + +Figure 2: Block content + +### 3.3.1 Block Type + +The purpose of the Block Type is to identify the function of the block and message being sent. The block type is coded as shown in figure 3. + +![](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet: | +|-------|-----|---|----|-----------------|---|---|---|--------| +| Spare | LPD | | LB | Sequence Number | | | | 1 | +| 0 | 0 | 1 | | | | | | | + +Figure 3: Block type content + +Bits 8 is spare and set to zero by the sender. In order to allow compatibility with future modifications to this protocol, bits 8 shall be ignored by the receiver and messages shall not be rejected because it is set to one. + +The Link Protocol Discriminator (LPD) takes the value "0 1". Other values of LPD indicate other protocols which are outside the scope of the present document, and shall cause the message to be ignored when the Cell Broadcast LPD is expected instead. + +NOTE: LPD = "0 0" corresponds to the data link protocol used by LAPDm (see 3GPP TS 44.006). + +In an SMSCB message the last block containing SMSCB information is signalled by the Last Block (LB) bit. When the LB bit is set to "0", the next block may contain SMSCB information. When the LB bit is set to "1", the remaining block(s) do(es) not contain SMSCB information. + +Table 1: Sequence number coding + +| Bit No | 4 | 3 | 2 | 1 | | +|--------|---|---|---|---|---------------------------------------------------------------------------| +| 0 | 0 | 0 | 0 | 0 | First block | +| 0 | 0 | 0 | 1 | 1 | Second block | +| 0 | 0 | 1 | 0 | 0 | Third block | +| 0 | 0 | 1 | 1 | 1 | Fourth block | +| 1 | 0 | 0 | 0 | 0 | First schedule block:
Message contains SMSCB
scheduling information | +| 1 | 1 | 1 | 1 | 1 | Null message (does not contain
valid SMSCB information) | + +All other values of bits 4 to 1 are reserved for future use. + +The use of a reserved code point shall cause the message to be ignored. + +## 3.4 SMSCB Message + +The SMSCB message is a message with four consecutive blocks, with Block Types "first block", "second block", "third block" and "fourth block". + +A null message (which is indicated by the Sequence Number 1111 (binary)) shall have octets 2 to 23, inclusive, filled with the value 2B (hex). + +The SMSCB message coding is defined in 3GPP TS 23.041. + +## 3.5 Schedule Message + +The text of the Schedule Message provides information pertaining to the CB messages sent afterward. + +A Schedule Message consists of 4 consecutive blocks with Block Types "first schedule block", "second block", "third block" and "fourth block". + +A Schedule Message containing scheduling data which does not fill the 88 octets shall be padded with the hexadecimal value "2B" after the end of the used part of the message. + +The Schedule Message comprises a 2-octet header followed by three parts, the first of them of 6 octets, and the two others of variable length, as indicated in figure 4. + +| 8 7 6 5 4 3 2 1 | | Octet: | +|-------------------------------|-------------------|----------------------------------| +| Type
0 0 | Begin Slot Number | 1 | +| Spare
0 Spare
0 | End Slot Number | 2 | +| New CBSMS Message Bitmap | | 3 - 8 | +| New CBSMS Message Description | | 9 - 2 m | +| Other Message Descriptions | | ( m +1)- n | + +**Figure 4: Schedule Message coding** + +Octets following the last part (n+1 to 88 inclusive), if any, shall be ignored. + +In the following subclauses, when bits are indicated as spare, they shall be set to the indicated value (0 or 1) by the network, and their value shall be ignored by the MS. + +### 3.5.1 Header + +Type (Octet 1): Set to 00 for messages formatted as specified in subclause 3.5. Schedule messages with another "Type" value shall be ignored by the receiver. + +Begin Slot Number (octet 1): Message slot number, relative to the schedule period, of the message slot following the Schedule Message. The Begin Slot Number field is coded in binary. Value range: 1 to 48. + +End Slot Number (octet 2): Last message slot number described by this Schedule Message. The End Slot Number field shall be coded in binary, and must be greater than or equal to the value of Begin Slot Number. Value range 1 to 48. + +NOTE: For a scheduled Schedule message, the Begin Slot Number is set to "1". + +NOTE 2: For an unscheduled Schedule message, the Begin Slot Number is set in the range 2 to 48. + +If either of the two preceding fields are out of range, or if the value of the End Slot Number field is less than the value of the Begin Slot Number field, the Schedule Message shall be ignored by the receiver. + +### 3.5.2 New CBSMS Message Bitmap + +This 6-octet fields encodes one bit per message slot, with the following indextation. + +| 8 7 6 5 4 3 2 1 | | | | | | | | Octet: | +|-----------------|-------|-------|-------|-------|-------|-------|-------|--------| +| NM 1 | NM 2 | NM 3 | NM 4 | NM 5 | NM 6 | NM 7 | NM 8 | 1 | +| NM 9 | NM 10 | NM 11 | NM 12 | NM 13 | NM 14 | NM 15 | NM 16 | 2 | +| NM 17 | NM 18 | NM 19 | NM 20 | NM 21 | NM 22 | NM 23 | NM 24 | 3 | +| NM 25 | NM 26 | NM 27 | NM 28 | NM 29 | NM 30 | NM 31 | NM 32 | 4 | +| NM 33 | NM 34 | NM 35 | NM 36 | NM 37 | NM 38 | NM 39 | NM 40 | 5 | +| NM 41 | NM 42 | NM 43 | NM 44 | NM 45 | NM 46 | NM 47 | NM 48 | 6 | + +**Figure 5: New CBSMS Message Bitmap coding** + +NM i: The New Message bit i refers to the content of message slot i. Its meaning is as follows: + +- 1 The message slot contains an SMSCB message page which was either not sent during the previous schedule period, or sent unscheduled during the preceding schedule period; or, the message is indicated as of free usage, reading advised. The value is 1 both for the first transmission of a given SMSCB message page in the schedule period or a repetition of it within the schedule period. +- 0 The message slot is such that value 1 is not suitable. + +An SMSCB message fulfilling the criterion for bit value 1 is said in the following to be "new". It should be noted that the broadcasting is not necessarily the first one. The network can choose not to send a given SMSCB message in all schedule periods. In this case it will be "new" each time it has not been sent in the previous schedule period. Another case is when a message is scheduled but its first transmission in the schedule period is pre-empted ; the next time the SMSCB message is "new". + +### 3.5.3 New CBSMS Message Description + +This part contains as many Message Descriptions as there are bits set to 1 in the New Message Bitmap. This part can then be empty. A message description is 1 or 2 octets long. + +![Figure 6: New CBSMS Message Description coding diagram. It shows a bit map with bits 8 through 1. Below the bits are two message description boxes labeled 'Message Description 1' and 'Message Description p'. To the right of the boxes is the label 'Octet: 1'.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +| | | | | | | | | | +|-----------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Message Description 1 | | | | | | | | Octet:
1 | +| Message Description p | | | | | | | | | + +Figure 6: New CBSMS Message Description coding diagram. It shows a bit map with bits 8 through 1. Below the bits are two message description boxes labeled 'Message Description 1' and 'Message Description p'. To the right of the boxes is the label 'Octet: 1'. + +**Figure 6: New CBSMS Message Description coding** + +New Message Description j: This one or two octet long field contains information about what is sent in the jth message slot for which NM i is set to 1. The different possible encodings are specified in subclause 3.5.5. + +All descriptions pertaining to the first transmission of a new message shall be put at the beginning, so that mobile stations can determine rapidly where the new messages are. + +### 3.5.4 Other Message Descriptions + +This part contains a one or two octet message description for each of the remaining message slots in the schedule period, in the order of transmission. This part can be empty. + +![Figure 7: Other Messages Part coding diagram. It shows a bit map with bits 8 through 1. Below the bits are two message description boxes labeled 'Message Description 1' and 'Message Description p'. To the right of the boxes is the label 'Octet: 1'.](5a24ac755b962fd5f0183f13de0726de_img.jpg) + +| | | | | | | | | | +|-----------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Message Description 1 | | | | | | | | Octet:
1 | +| Message Description p | | | | | | | | | + +Figure 7: Other Messages Part coding diagram. It shows a bit map with bits 8 through 1. Below the bits are two message description boxes labeled 'Message Description 1' and 'Message Description p'. To the right of the boxes is the label 'Octet: 1'. + +**Figure 7: Other Messages Part coding** + +The Message Slot Number for each description must be derived from the New CBSMS Message Bitmap. + +The different cases are encoded as specified in subclause 3.5.5. + +### 3.5.5 Message description encoding + +Four different encoding formats are specified, respectively: + +- 1) for the first transmission of an SMSCB message in the schedule period; +- 2) for the repetition of an SMSCB message; +- 3) for a message slot of unindicated usage that MSs can skip; and +- 4) for a message slot of unindicated usage that MSs should not skip. + +The different encoding formats are identified by the Message Description Type (MDT) field. The MDT field is of variable length. + +The length of a description can be determined from the value of bit 8 of the first octet, which can then be understood as a "more" bit. Value 0 indicates a single-octet field, and value 1 a 2-octet field. + +#### 3.5.5.1 First transmission of an SMSCB within the Schedule Period + +This describes the content of a message slot which contains the first transmission of an SMSCB message page within the period. + +![](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet: | +|-------------------------------|--------------------------------|---|---|---|---|---|---|--------| +| MDT
1 | Message Identifier (high part) | | | | | | | 1 | +| Message Identifier (low part) | | | | | | | | 2 | + +**Figure 8: Message Description coding, First Transmission of an SMSCB** + +MDT, Message Description Type (octet 1 of Message Description, bit 8): 1-bit field set to 1 for the message description of a message slot containing the first transmission during the schedule period of a given SMSCB message page. + +MESSAGE IDENTIFIER (octet 1 bits 7 to 1 and octet 2 of Message Description): Consists of the low-order 15 bits of the corresponding field of the SMSCB message, as defined in 3GPP TS 23.041. + +#### 3.5.5.2 Retransmission indication + +When a message slot contains the repetition of a SMSCB message page within the schedule period, the corresponding message description is coded on one octet, as follows: + +![](fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg) + +| Bit 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet: | +|----------|---|------------------------------|---|---|---|---|---|--------| +| MDT
0 | 0 | Repeated Message Slot Number | | | | | | 1 | + +**Figure 9: Message Description coding, Retransmission of an SMSCB** + +MDT, Message Description Type (octet 1 of Message Description, bits 8 and 7): 2-bit field set to "00" for the message description of a message slot containing the repetition of a SMSCB message page. + +Repeated Message Slot Number (octet 1 of Message Description, bits 6 to 1): This field encodes the message slot number of the first transmission during the schedule period of the repeated SMSCB message page. The field is encoded in binary, range 1 to 47. + +#### 3.5.5.3 Free Message Slot, optional reading + +When no specific information about a message slot is provided, and MSs need not read its contents, the Message Description is coded as follows. + +![](fe61ee8618403cf584b2e28c4bada03a_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet: | +|-----|---|---|---|---|---|---|---|--------| +| MDT | | | | | | | | 1 | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | | + +**Figure 10: Message Description coding, Free Message Slot, optional reading** + +MDT, Message Description Type (octet 1 of Message Description): 8-bit field set to "01000000". The network can use such a message slot as needed, e.g. for unscheduled messages or for unscheduled Schedule Messages. + +#### 3.5.5.4 Free Message Slot, reading advised + +When no specific information about a message slot is provided, and MSs should read its contents, the Message Description is coded as follows. + +![](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet: | +|-----|---|---|---|---|---|---|---|--------| +| MDT | | | | | | | | 1 | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | | + +**Figure 11: Message Description coding, Free Message Slot, reading advised** + +MDT, Message Description Type (octet 1 of Message Description): 8-bit field set to "01000001". The network can use such a message slot as needed, e.g. for sending high-priority messages. + +#### 3.5.5.5 Reserved Codepoints + +The values of MDT other than those specified in the previous subclauses are reserved for future use. They shall be treated as encoding a one octet message description, and understood as specified in subclause 3.5.5.3. + +# Annex A (informative): Sample Implementation of SMSCB DRX Mode + +This annex describes an implementation of SMSCB DRX functions, both on the network side and on the MS side. + +The network includes Schedule Messages to provide the MSs with information about the contents of the message slots following the Schedule Messages. The simplest implementation consists in sending Schedule Messages regularly, in a way all message slots are part of the schedule period of some Schedule Message. + +For the MS, there may be 3 main reception modes for the CBCH: + +- 1) No DRX. The MS reads the first block of all message slots, and reads the remaining blocks when the message header indicates this is useful. A MS operates in this mode either when it does not support the other modes, or when it has not received a schedule message applicable to the next message slot. +- 2) First DRX mode. The MS has received a schedule message applicable to the next message slot, but either did not receive the first schedule message of the schedule period previous to the current one, or has not received all messages sent in that period (during that period or before). +- 3) Second DRX mode. The MS knows all the messages of interest sent in the schedule period previous to the current one, and has received the first schedule message of the current period. + +More information about these modes is given below. + +When a MS first enters a cell, or more generally when it knows no information pertaining to a message slot, it should read the first block of each message slot. According to the information found in this first block the MS can choose to read the rest of the message slot. Typically it will do so when it is a Schedule Message, or when it is an SMSCB message that it has not received before, in that cell or in a another. + +The complete reading of a first schedule message allows the MS to enter a first DRX mode for the rest of the schedule period. In this mode the MS reads the first block of each message slot for which the "message identifier", as indicated in the Schedule Message, is of interest to the user until the end of the schedule period, except that the MS may ignore retransmissions of messages it has already received during the same schedule period. + +When the MS has correctly read during a Schedule Period all messages of interest for its user, it can enter a second DRX mode. In this mode, it reads the first block of the CB message immediately after the end of the schedule period. If it is not a schedule message, or if the reception fails, it reads all first blocks until it receives a schedule message. In case of missed reception of the very first block, it enters the second DRX mode only if the first block of the next received schedule message shows that there is no gap between the corresponding schedule period and the previous one (it is the only way to be sure that there was no intervening schedule period). In the second DRX mode, the MS can understand from the first block of the schedule message how many new messages there are, when they will be transmitted, their message identifiers if there are less than 6 new messages, and possibly the positions of their repetitions. If the first block indicates that there are no new messages, or sufficiently few so that their message identifiers and the positions of their repetitions are known, the MS can refrain from reading the other blocks of the Schedule Message. Otherwise it reads the next block, and so on, until all the information pertaining to new messages is known. Then the MS reads only the new messages with a message identifier of interest for its user, and possibly corresponding repetitions in case of reception failures. + +Free message slots can be used for different purposes by the network. MSs wanting to save as much battery as possible at the expense of the delay for receiving messages can skip those message slots. As a trade-off, MSs can implement DRX with reception of the free messages slots with reading advised: this will speed up reception of new messages, with a higher battery consumption in proportion to the use of such messages slots by the network. Free message slots with optional reading should be used typically for unscheduled schedule messages, and can be skipped by mobile stations implementing DRX. + +The network can broadcast unscheduled SMSCB messages. The different possibilities are as follows: + +- The network can send a new message in a free-usage message slot with reading advised. MSs implementing DRX but reading the first block of message slots so indicated will receive the message. The message must still be indicated as "new" the first time it is sent scheduled in a schedule period. +- The network can pre-empt a "new" message with a more recent "new" message of the same message identifier if it happens that its first transmission has not yet happened; this is the only case where all MSs will read the unscheduled message. The network should repeat the pre-empting message instead of the pre-empted one in the messages slots scheduled for the repetitions of this message. If the pre-empted message is to be transmitted later, it has to be sent as "new" in the next schedule period within which it is sent. +- If a message has been sent in the previous schedule period, the network can pre-empt the first transmission in the schedule period with a more recent message of the same message identifier. In this case, the MSs in second DRX mode will not receive immediately the message, but will receive it in the next schedule period if the message is repeated afterward (the network will indicate it as a "new" message even if it has been sent in the previous schedule period, since it would not have been scheduled during that period). If the pre-empted message is to be transmitted again, it has to be sent as "new" in the next schedule period within which it is sent. +- If a message has been sent in the previous schedule period, the network can pre-empt the first transmission in the schedule period with a more recent message of a different message identifier. In this case, it is unlikely that a mobile station implementing DRX will immediately receive the message, it will receive it in the next schedule period if the message is repeated afterward (the network will indicate it as a "new" message even if it has been sent in the previous schedule period, since it would not have been scheduled during that period). The pre-empted message has to be sent as "new" in the next schedule period within which it is sent. +- The network can pre-empt a retransmission (of the same message identifier or not), or send the new message in a free message slot of optional reading. In these cases it is unlikely that a MS implementing DRX will receive it at that moment. + +In free message slots the network can broadcast for instance unscheduled Schedule Messages. These messages hasten the entry into DRX mode of fast-moving MSs. + +# Annex B (informative): Change History + +| Meeting/Date | Tdoc | CR | Subject/Comment | New Version | +|--------------|------|----|-----------------------------------------|-------------| +| January 2016 | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|--------|----------|----|-----|-----|----------------------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44013/raw.md b/marked/Rel-16/44_series/44013/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..035e1523029095fe1ed899c14570a240b98991a1 --- /dev/null +++ b/marked/Rel-16/44_series/44013/raw.md @@ -0,0 +1,402 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations and definitions ..... | 6 | +| 3.1 Abbreviations ..... | 6 | +| 3.2 Definitions..... | 6 | +| 4 Default conditions ..... | 6 | +| 5 Requirements ..... | 6 | +| 5.1 General requirements ..... | 6 | +| 5.1.1 Response to layer 3 message..... | 6 | +| 5.1.2 Response to an erroneous layer 3 message..... | 7 | +| 5.2 Layer 3 Radio Resource signalling ..... | 7 | +| 5.2.0 Paging..... | 7 | +| 5.2.1 Paging and cell reselection after channel release ..... | 7 | +| 5.2.2 Paging commands and immediate assignment rejection (Timer T3122) ..... | 7 | +| 5.2.3 Immediate assignment (Timer T3101) ..... | 7 | +| 5.2.4 Channel assignment..... | 7 | +| 5.2.5 Channel mode modify ..... | 7 | +| 5.2.6 Handover access ..... | 8 | +| 5.2.6.1 Finely, pseudo and pre synchronized cases ..... | 8 | +| 5.2.6.2 Non synchronized case ..... | 8 | +| 5.2.7 Encryption ..... | 9 | +| 5.2.8 Classmark change..... | 9 | +| 5.2.9 Classmark interrogation..... | 9 | +| 5.2.10 Release (Timer T3110)..... | 9 | +| 5.2.11 Early sending of the CLASSMARK CHANGE message ..... | 9 | +| 5.3 Layer 3 Mobility Management signalling..... | 9 | +| 5.3.1 Periodic location updating timer ..... | 9 | +| 5.3.2 Identification..... | 9 | +| 5.3.3 Authentication ..... | 10 | +| 5.3.4 T3240 expiry ..... | 10 | +| 5.3.5 TMSI reallocation..... | 10 | +| 5.3.6 IMSI detach ..... | 10 | +| 5.3.7 Location updating with random access failure ..... | 10 | +| 5.3.8 Follow on call ..... | 10 | +| 5.4 Layer 3 Call Control signalling..... | 10 | +| 5.4.1 Time to send SETUP message ..... | 10 | +| 5.4.2 Response times to CC messages..... | 11 | +| 5.4.3 User alerting ..... | 11 | +| 5.4.4 Call establishment ..... | 11 | +| 5.4.5 Call reestablishment ..... | 12 | +| 5.4.6 In call modification..... | 12 | +| 5.4.7 DTMF ..... | 12 | +| 5.5 Supplementary service signalling..... | 12 | +| 5.5.1 Advice of Charge Charging (AoCC)..... | 12 | +| 5.6 Short Message Services Point-to-Point..... | 12 | +| 5.6.1 CP-DATA..... | 12 | +| 5.6.2 RP-DATA..... | 13 | +| Annex A (informative): Change History ..... | 14 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies measurable performance requirements for signalling aspects of Mobile Stations (MS)s. To allow implementation flexibility it has been chosen to specify requirements on the whole Mobile Station rather than to specify requirements on each "OSI layer". As a consequence the performance requirements do not fit conveniently in specifications such as 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] (layer 3 only) or 3GPP TS 44.006 [3] (layer 2 only). + +The main aim of the present document is to provide the justification for testing of requirements that are not included in other GSM specifications. Where specific requirements are included in other GSM specifications they are not duplicated here. + +MSs have to perform a wide variety of functions. As a consequence most performance measurements have to be made under a set of defined conditions: where necessary, these are included in the present document. + +Where necessary certain assumptions are made about the interaction times between the mobile equipment and the SIM. If the (test) SIM does not respond within the assumed time then appropriate allowances shall be made. + +Additionally, it is intended that the present document should contain sufficient requirements to enable some undefined network timers in 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] to be calculated. + +# --- 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. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [3] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". +- [4] 3GPP TS 24.008: "Mobile radio interface; Layer 3 specification". +- [4a] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [5] 3GPP TS 24.086: "Advice of Charge (AoC) supplementary services; Stage 3". +- [6] 3GPP TS 45.002: Multiplexing and multiple access on the radio path". +- [7] 3GPP TS 45.008: "Radio subsystem link control". + +# --- 3 Abbreviations and definitions + +## 3.1 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1a] apply. + +## 3.2 Definitions + +For the purposes of the present document, the following definition applies: + +**ready to transmit:** in the present document the phrase "ready to transmit the message before time x" is defined to mean that the MS shall transmit part of that message no later than the first burst of the first TCH or control channel block that occurs after time x. + +# --- 4 Default conditions + +Unless otherwise stated, throughout the present document the following conditions are associated with the requirements: + +- ideal radio link with an insignificant bit error rate; +- no other signalling is in progress on the main DCCH; +- messages sent by the network are correctly formed; +- the only established data link (or the only data link to be established) is on SAPI 0; +- any Starting Time IE that is included in a message sent by the network does not require the action to be delayed; +- cells are not barred and all access classes are allowed; +- the layer 2 performance of the network shall satisfy the "System Performance Requirements" of subclause 5.9 of 3GPP TS 44.006 [3]; +- messages sent by the network may contain any set of optional IEs, and any permitted set of conditional IEs; +- the mobile has a valid SIM inserted, is powered on, and the SIM's update status is "updated"; and +- on the CCCH, the Page Mode IE is not set to "paging reorganization" or "same as before". + +# --- 5 Requirements + +## 5.1 General requirements + +### 5.1.1 Response to layer 3 message + +The requirements of subclause 5.1.1 apply if there are no specific requirements for a layer 3 message in other parts of clause 5. + +If the last timeslot of the message block containing a network command occurs at time T, then the MS shall be ready to transmit the response before time T + 500 ms. + +### 5.1.2 Response to an erroneous layer 3 message + +If the last timeslot of the message block containing an erroneous RR, MM or CC message occurs at time T and if 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] requires a status message to be returned to the network then the MS shall be ready to transmit the RR-STATUS or MM-STATUS or STATUS message before T + 500 ms. + +## 5.2 Layer 3 Radio Resource signalling + +### 5.2.0 Paging + +If access to the network is allowed and the MS has been camped on a suitable cell for at least 2 s and if the last timeslot of the message block containing a PAGING REQUEST message addressing the MS occurs at time T, then the MS shall be ready to transmit the CHANNEL REQUEST message before T + 0,7 s. + +### 5.2.1 Paging and cell reselection after channel release + +If the last timeslot of the message block containing a CHANNEL RELEASE message occurs at time T the MS shall respond to PAGING REQUEST messages sent later than $T + 1,0$ s. + +### 5.2.2 Paging commands and immediate assignment rejection (Timer T3122) + +If the last timeslot of the message block containing an IMMEDIATE ASSIGNMENT REJECT message is sent at time T and contains a Wait Indication of W seconds then the MS shall at least respond to PAGING REQUEST messages sent later than $T + (W + 1)$ s. + +### 5.2.3 Immediate assignment (Timer T3101) + +If the last timeslot of the message block containing an IMMEDIATE ASSIGNMENT (or IMMEDIATE ASSIGNMENT EXTENDED) message is transmitted at time T then, the MS shall be ready to transmit the SABM frame with its information field before $T + 25$ ms. This requirement shall apply for assignment to TCH/F, TCH/H and SDCCH. + +### 5.2.4 Channel assignment + +If the last timeslot of the message block containing an ASSIGNMENT COMMAND occurs at time T, then the MS shall be ready to transmit the ASSIGNMENT COMPLETE message before $T + 600$ ms. + +If the last timeslot of the message block containing an ASSIGNMENT COMMAND occurs at time T and this ASSIGNMENT COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the ASSIGNMENT FAILURE message on the old channel before $T + 2$ s. + +If the last timeslot of the message block containing an ASSIGNMENT COMMAND occurs at time T and this ASSIGNMENT COMMAND is such that the MS shall not attempt to establish a layer 2 link on the new channel, then the MS shall be ready to transmit any ASSIGNMENT FAILURE message on the old channel before $T + 500$ ms. + +### 5.2.5 Channel mode modify + +If the last timeslot of the message block containing a CHANNEL MODE MODIFY message occurs at time T, then the MS shall be ready to transmit the CHANNEL MODE MODIFY ACKNOWLEDGE message before $T + 300$ ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the CHANNEL MODE ACKNOWLEDGE message before $T + 50$ ms. + +### 5.2.6 Handover access + +#### 5.2.6.1 Finely, pseudo and pre synchronized cases + +If the last timeslot of the message block containing a HANDOVER COMMAND message to a full rate TCH occurs at time T, then the MS shall be ready to transmit the HANDOVER COMPLETE message before $T + 650$ ms. + +If the last timeslot of the message block containing a HANDOVER COMMAND message to a half rate TCH occurs at time T, then the MS shall be ready to transmit the HANDOVER COMPLETE message before $T + 900$ ms. + +If the last timeslot of the message block containing a HANDOVER COMMAND message to an SDCCH occurs at time T, then the MS shall be ready to transmit the HANDOVER COMPLETE message before $T + 1,5$ s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to a full rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old full rate TCH before $T + 2$ s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to a full rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old SDCCH before $T + 2,5$ s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to a half rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old half rate TCH before T + 3 s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to a half rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old SDCCH before T + 3 s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to an SDCCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old SDCCH before T + 5 s. + +If the last timeslot of the message block containing a HANDOVER COMMAND occurs at time T and this HANDOVER COMMAND is such that the MS shall not attempt to establish a layer 2 link on the new channel, then the MS shall be ready to transmit any HANDOVER FAILURE message on the old channel before T + 500 ms. + +#### 5.2.6.2 Non synchronized case + +If the last timeslot of the message block containing the (one and only) PHYSICAL INFORMATION message occurs at time T, then on a full rate TCH the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 500 ms. + +If the last timeslot of the message block containing the (one and only) PHYSICAL INFORMATION message occurs at time T, then on a half rate TCH the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 750 ms. + +If the last timeslot of the message block containing the (one and only) PHYSICAL INFORMATION message occurs at time T, then on an SDCCH the MS shall be ready to transmit the HANDOVER COMPLETE message before T + 1,5 s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to either a full rate or a half rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old TCH before T + 1,1 s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to an SDCCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old SDCCH before T + 2 s. + +If the last timeslot of the message block containing a HANDOVER COMMAND to either a full rate or a half rate TCH occurs at time T and this HANDOVER COMMAND is such that the MS tries but fails to establish a layer 2 link on the new channel and thus reverts to the old channel, then the MS shall be ready to transmit the HANDOVER FAILURE message on the old SDCCH before T + 1,7 s. + +If the last timeslot of the message block containing a HANDOVER COMMAND occurs at time T and this HANDOVER COMMAND is such that the MS shall not attempt to establish a layer 2 link on the new channel, then the MS shall be ready to transmit any HANDOVER FAILURE message on the old channel before T + 500 ms. + +### 5.2.7 Encryption + +If the last timeslot of the message block containing a CIPHERING MODE COMMAND message occurs at time T, then the MS shall be ready to transmit the CIPHERING MODE COMPLETE message before T + 500 ms. + +### 5.2.8 Classmark change + +While the MS has an active RR connection, any change in the MS's capabilities that are indicated in the Mobile Station Classmark 2 or 3 IEs shall cause a CLASSMARK CHANGE message to be sent to the network. The MS shall be ready to transmit the CLASSMARK CHANGE message not later than 1 second after the change in capabilities. + +### 5.2.9 Classmark interrogation + +If the last timeslot of the message block containing a CLASSMARK ENQUIRY message occurs at time T, then the MS shall be ready to transmit the CLASSMARK CHANGE message before T + 300 ms. + +### 5.2.10 Release (Timer T3110) + +If the last timeslot of the message block carrying the CHANNEL RELEASE message occurs at time T, then the MS shall cease transmissions on all channels before T + 500 ms. + +### 5.2.11 Early sending of the CLASSMARK CHANGE message + +During a contention resolution procedure, if the last timeslot of the block containing a Layer 2 UA frame, occurs at time T, then the MS shall be ready to transmit the CLASSMARK CHANGE message, if applicable (see 3GPP TS 44.006 [3] and 3GPP TS 44.018 [4a]), before T + 40 ms. + +## 5.3 Layer 3 Mobility Management signalling + +### 5.3.1 Periodic location updating timer + +When the T3212 time-out value is set to the non-zero value P and the last timeslot of the message block containing a CHANNEL RELEASE message is transmitted at time T then, assuming the next event shall be the periodic location update, the next CHANNEL REQUEST message shall be transmitted between time T + P decihours - 15 seconds and time T + P decihours + 15 s. + +### 5.3.2 Identification + +If the last timeslot of the message block containing an IDENTITY REQUEST message occurs at time T, then the MS shall be ready to transmit the IDENTITY RESPONSE message before T + 600 ms. This requirement assumes that the ME has to wait less than 100 ms to obtain any necessary responses from the SIM. + +### 5.3.3 Authentication + +If the last timeslot of the message block containing an AUTHENTICATION REQUEST message occurs at time T, then the MS shall be ready to transmit the AUTHENTICATION RESPONSE message before T + 1 s. This requirement assumes that the ME has to wait less than 500 ms to obtain any necessary responses from the SIM. + +### 5.3.4 T3240 expiry + +If the last timeslot of the message block containing an AUTHENTICATION REJECT message; or a LOCATION UPDATING ACCEPT message (without a Follow On Proceed IE); or a LOCATION UPDATING REJECT message; or a CM SERVICE REJECT message (and no other MM connection is active) occurs at time T, and the network does not send a CHANNEL RELEASE message but does maintain the RR connection, then the MS shall cease transmission on all channels before T + 12 s. + +### 5.3.5 TMSI reallocation + +If the last timeslot of the message block containing either a TMSI REALLOCATION COMMAND, or a LOCATION UPDATING ACCEPT with a TMSI in the Mobile Identity IE, occurs at time T, then the MS shall be ready to transmit the TMSI REALLOCATION COMPLETE message before T + 500 ms. + +### 5.3.6 IMSI detach + +The requirements of this subclause only apply if the network indicates on the BCCH that IMSI detach shall be used. + +If it is possible to switch the mobile off, or if it is possible to remove the SIM whilst the mobile is powered on, then when such an action is performed in idle mode at time T, the first CHANNEL REQUEST message for the IMSI Detach procedure shall be transmitted before T + 2 s. + +If it is possible to switch the mobile off, or if it is possible to remove the SIM whilst the mobile is powered on, then when such an action is performed in the Active (U10) state of a call at time T, the MS shall be ready to transmit the IMSI DETACH INDICATION message before T + 1 s. + +If the last timeslot in which the IMSI DETACH message is sent occurs at time T then the MS shall cease transmission on all channels before T + 6 s. + +### 5.3.7 Location updating with random access failure + +In an environment with only one suitable cell (see 3GPP TS 43.022 [2] for the definition of a "suitable cell"), if a location updating attempt suffers a random access failure (see 3GPP TS 44.018 [4a]) with the last CHANNEL REQUEST message being transmitted at time T, then the first re-attempt shall result in a CHANNEL REQUEST message being transmitted before T + 15 s. + +### 5.3.8 Follow on call + +If the last timeslot of the message block containing a LOCATION UPDATING ACCEPT message with a Follow on Proceed IE occurs at time T and the MS has a CM application request pending, then the MS shall be ready to the CM SERVICE REQUEST message before T + 500 ms. + +## 5.4 Layer 3 Call Control signalling + +### 5.4.1 Time to send SETUP message + +In the case of a MS originated call, if the last timeslot of the message block containing a CM SERVICE ACCEPT message occurs at time T then the MS shall be ready to transmit the SETUP message before T + 500 ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the SETUP message before T + 50 ms. + +In the case of a MS originated call, if the last timeslot of the message block containing a CIPHERING MODE COMMAND message occurs at time T, then the MS shall be ready to transmit the SETUP message before T + 750 ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the SETUP message before T + 50 ms. + +In the case of a MS originated call, if the last timeslot of the message block containing a MM GO ON message occurs at time T, then the MS shall be ready to transmit the SETUP message before T + 50 ms. In the case that the call is a voice group or voice broadcast call the MS shall be ready to transmit the SETUP message before T + 50 ms. + +### 5.4.2 Response times to CC messages + +For the commands and responses listed in table 1, the following shall apply: + +- if the last timeslot of the message block in which the "command" message is sent occurs at time T, then the MS shall be ready to transmit any one of the possible "responses" before time T + W. + +In table 1, the second figure, where provided, represents the time that must be achieved in the case of a voice group or voice broadcast call. + +**Table 1: Call Control message response times** + +| command
(network --> MS) | response(s)
(MS --> network) | W | +|----------------------------------------|---------------------------------------------------------------------------------------------------|----------------| +| CONNECT | CONNECT ACKNOWLEDGE | 500 ms, 50 ms | +| SETUP | (as first response message)
CALL CONFIRMED or
ALERTING or
CONNECT or
RELEASE COMPLETE | 1 s, 50 ms | +| SETUP | (as second response message)
ALERTING or
CONNECT or
DISCONNECT | 2 s | +| SETUP | (as third response message)
CONNECT | no requirement | +| DISCONNECT | RELEASE | 500 ms | +| RELEASE | RELEASE COMPLETE | 500 ms | +| STATUS ENQUIRY | STATUS | 500 ms | + +### 5.4.3 User alerting + +If the MS has some form of user alerting and if for a mobile terminating call the MS sends the ALERTING message before the CONNECT message then: + +- if the last timeslot carrying a SETUP message containing the Signal IE occurs at time T, the user alerting shall be initiated before time $T + 1$ s. + +### 5.4.4 Call establishment + +If the MS's service indication indicates that service is available (see 3GPP TS 43.022 [2]) and after the entry of suitable number digits, then if the "SEND" or "Emergency SEND" function on the MS is activated at time T, the first CHANNEL REQUEST message shall be transmitted before time $T + 2$ s. + +### 5.4.5 Call reestablishment + +The requirement of this subclause relates to the following environment and conditions: + +- the MS is the active (U10) state of a speech call on cell A; +- the NCC of cell B is indicated as permitted in the SYSTEM INFORMATION messages of cell A, but cell B may be in a different location area; +- cells A and B are the only cells which have $C1 > 0$ (see 3GPP TS 45.008 [7]); +- cell B is in at least the BA(SACCH) list of cell A; +- cell B allows call reestablishment. + +If the transmissions from cell A are disrupted such that the MS shall detect a radio link failure at time T then the MS shall transmit a CHANNEL REQUEST message to cell B before time $T + 3$ s. + +### 5.4.6 In call modification + +For network originated in call modification, if the MS transmits the last timeslot of the message block containing the MODIFY message at time T then the MS shall be ready to transmit the MODIFY COMPLETE message before time $T + 500$ ms. + +### 5.4.7 DTMF + +This requirement applies when the MS's DTMF function is not disabled. + +When the first number key is pressed on the MS during the Active (U10) state of a call at time T, then the MS shall be ready to transmit the START DTMF message before time $T + 500$ ms. + +## 5.5 Supplementary service signalling + +### 5.5.1 Advice of Charge Charging (AoCC) + +The following requirements only apply to mobile stations that support the Advice of Charge Charging supplementary service defined in 3GPP TS 24.086 [5]. + +If the last timeslot of the message block in which a Call Control message with a Facility information element containing the operation ForwardChargeAdvice with the SS code set to AoCC occurs at time T, then the MS shall be ready to transmit a message with a Facility information element containing a Return result with the same Invoke ID before time $T + 1$ s. + +## 5.6 Short Message Services Point-to-Point + +These requirements relate to signalling using SAPI 3. + +### 5.6.1 CP-DATA + +If the last timeslot of the message block containing a CP-DATA message occurs at time T, then the MS shall be ready to transmit the CP-ACK message before $T + 500$ ms. + +### 5.6.2 RP-DATA + +If the last timeslot of the message block containing a RP-DATA message which will be stored in the ME and for which the ME has storage room available occurs at time T, then the MS shall be ready to transmit the RP-ACK message before time $T + 1$ s. + +If the last timeslot of the message block containing a RP-DATA message whose destination is the SIM and for which the SIM has storage room available occurs at time T, then the ME shall start to send the short message on the ME - SIM interface before time $T + 250$ ms. + +If the last timeslot of the message block containing a RP-DATA message whose destination is the TE occurs at time T, then the ME shall start to send the short message on the ME - TE interface before time $T + 250$ ms. + +In the case of a short message supplied to the SIM, if the response from the SIM that triggers the sending of the RP-ACK message is completed on the SIM-ME interface at time T, then the MS shall be ready to transmit the RP-ACK message before time $T + 250$ ms. + +In the case of a short message supplied to the TE, if the response from the TE that triggers the sending of the RP-ACK message is completed on the TE-ME interface at time T, then the MS shall be ready to transmit the RP-ACK message before time $T + 250$ ms. + +# Annex A (informative): Change History + +| SMG No. | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments | +|---------|-----------|---------|------------------|-------------|--------------------------------------------------------------------------| +| SMG#14 | | | | 4.0.2 | ETSI Publication | +| SMG#15 | 414/95 | A002 | | 4.1.0 | Performance requirement on early sending of the CLASSMARK CHANGE message | +| | | A003 | | | Erroneous release time requirement | +| SMG#16 | 584/95 | 001 | | 4.2.0 | PE Comments | +| | | 002 | | | | +| | | 003 | | | | +| SMG#20 | | | | 5.0.2 | Release 1996 version | +| SMG#21 | 054/97 | A006 | | 5.1.1 | CR on GSM 04.13 on Time response to RP-DATA with an RP-ACK | +| SMG#27 | | | | 6.0.0 | Release 1997 version | +| SMG#28 | | | | 6.0.1 | ETSI Publication | +| SMG#29 | | | | 7.0.0 | Specification version 6.0.1 upgrade to Release 1998 version 7.0.0 | +| | | | | 7.0.1 | Version update to 7.0.1 for Publication | +| SMG#31 | | | | 8.0.0 | Specification upgrade to Release 1999 | +| | | | | 8.0.1 | Version update to 8.0.1 for Publication | +| CN#11 | | | 3GPP TS 44.013 | 4.0.0 | Release 4 version after CN#11 | +| NP-16 | NP-020224 | 001 | 3GPP TS 44.013 | 4.1.0 | Various clean-up of wrong references, eg towards 44.018 | +| NP-16 | | | 3GPP TS 44.013 | 5.0.0 | Plenary decision to make this TS also for Rel-5. | +| NP-26 | | | 3GPP TS 44.013 | 6.0.0 | Plenary decision to make this TS also for Rel-6. | +| | | | | 7.0.0 | Plenary decision to make this TS also for Rel-7. | +| CP-42 | | | | 8.0.0 | Plenary decision to make this TS also for Rel-8. | +| CP-46 | | | | 9.0.0 | Plenary decision to make this TS also for Rel-9. | +| CP-51 | | | | 10.0.0 | Plenary decision to make this TS also for Rel-10. | +| CP-57 | | | | 11.0.0 | Plenary decision to make this TS also for Rel-11. | +| CP-65 | | | | 12.0.0 | Plenary decision to make this TS also for Rel-12. | +| CP-70 | | | | 13.0.0 | Upgrade to Rel-13 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|-------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2018-06 | SA#80 | | | | | Upgrade to Rel-15 | 15.0.0 | +| 2020-06 | SA#88e | | | | | Upgrade to Rel-16 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44014/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-16/44_series/44014/0892c0cb3b8502a44c4fe4e786be912a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ae2f705bf57eda433d36e6e9aa0ba84ee794d84 --- /dev/null +++ b/marked/Rel-16/44_series/44014/0892c0cb3b8502a44c4fe4e786be912a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa0e1789f9fe65900ce02714570674b90a39c557278f1344d076835c5a909534 +size 39784 diff --git a/marked/Rel-16/44_series/44014/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/44_series/44014/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ba6b96e7e4094cb3ea58a6232b9d216068dda19 --- /dev/null +++ b/marked/Rel-16/44_series/44014/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e62cd34a133f38535de2fe423fd970233b4e4ad76932952f95e3bca6e89e39d9 +size 41184 diff --git a/marked/Rel-16/44_series/44014/4b00764d3c160ac6ade7502d9faeb615_img.jpg b/marked/Rel-16/44_series/44014/4b00764d3c160ac6ade7502d9faeb615_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14b8480e20fd852a5f11f7db964fde054733203f --- /dev/null +++ b/marked/Rel-16/44_series/44014/4b00764d3c160ac6ade7502d9faeb615_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a8c86b4eb885f9b122f238e430c8472bddc7c33e32472926456c3893f686464 +size 24747 diff --git a/marked/Rel-16/44_series/44014/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/44_series/44014/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcee4db7734964fba45ad41194903d976f088fc8 --- /dev/null +++ b/marked/Rel-16/44_series/44014/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea602b33776964b1b998de7051552f657e5ba4c883f8ee0be0ddd55798dcc950 +size 48392 diff --git a/marked/Rel-16/44_series/44014/8093331dcf2cec58ddacf15bc3622b2e_img.jpg b/marked/Rel-16/44_series/44014/8093331dcf2cec58ddacf15bc3622b2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd948d7e697f32ded0efced31f4d9b1b37d827a --- /dev/null +++ b/marked/Rel-16/44_series/44014/8093331dcf2cec58ddacf15bc3622b2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9061d342709b4af95d145def8da6dff95f6ed2f32c3c338ce3860df63e192736 +size 11196 diff --git a/marked/Rel-16/44_series/44014/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-16/44_series/44014/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86f727651458b65b38dff28491ab1e2f9862ca8b --- /dev/null +++ b/marked/Rel-16/44_series/44014/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9df01f8dc7277040b3a539b174ca8a68e456fc8f1de8e2fde8112e6324a5788 +size 39262 diff --git a/marked/Rel-16/44_series/44014/a97518a839da75f8379c578562b01bc2_img.jpg b/marked/Rel-16/44_series/44014/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bbf1857cdceb9df5f5895fe2de1449a127a3ef3 --- /dev/null +++ b/marked/Rel-16/44_series/44014/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d076a40294bed674656a695643cdcdb981fce0bcf8c82f2e6b40ddbd15593896 +size 11594 diff --git a/marked/Rel-16/44_series/44014/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-16/44_series/44014/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5aca4aafa582f9eee520432f51e05826ebb868a9 --- /dev/null +++ b/marked/Rel-16/44_series/44014/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e1a20f80a7426953d2b0e74716c3e1d71b203f33639a267afc2622258d1e276 +size 79820 diff --git a/marked/Rel-16/44_series/44014/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-16/44_series/44014/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b3fc2a53f1a7e05bc392e0987b4aa8d2132c269 --- /dev/null +++ b/marked/Rel-16/44_series/44014/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c62a14ad3402acf79a91ab5893bd4ba8f70b59e4821c85c702eea0d4640f625 +size 58436 diff --git a/marked/Rel-16/44_series/44014/ca1709650afeccbebb6eb9473796e5f5_img.jpg b/marked/Rel-16/44_series/44014/ca1709650afeccbebb6eb9473796e5f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc8ff6f2b388ecf7bb179fa5349151286aad2ac2 --- /dev/null +++ b/marked/Rel-16/44_series/44014/ca1709650afeccbebb6eb9473796e5f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f5ff411cf5778db00f10b296f658e56c0c57aff725777117e06a90c6ebe44e8 +size 7572 diff --git a/marked/Rel-16/44_series/44014/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/44_series/44014/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ebd0bc7db881787852100c5e670e91cfd7320d7 --- /dev/null +++ b/marked/Rel-16/44_series/44014/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9eb1efd08ac923398006b4dc24c783193b2b2f380bec283a0ced798245e299e +size 44645 diff --git a/marked/Rel-16/44_series/44014/raw.md b/marked/Rel-16/44_series/44014/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..86519836c6f26ba79c91871940f92066303652c0 --- /dev/null +++ b/marked/Rel-16/44_series/44014/raw.md @@ -0,0 +1,2021 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 1.1 Conventions..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, conventions, and applicability..... | 8 | +| 3.1 Mobile station definition and configurations ..... | 8 | +| 3.2 Applicability..... | 8 | +| 4 Activation and deactivation of special test functions in the MS..... | 8 | +| 5 Internal test loops ..... | 9 | +| 5.1 Single-slot TCH loops..... | 10 | +| 5.1.1 Purpose of Single-slot TCH loops..... | 10 | +| 5.1.2 TCH loop including signalling of erased frames (A) ..... | 10 | +| 5.1.2.1 Procedure ..... | 10 | +| 5.1.3 Speech TCH loop without signalling of erased frames (B)..... | 12 | +| 5.1.3.1 Procedure ..... | 12 | +| 5.1.4 TCH burst-by-burst loop (C)..... | 13 | +| 5.1.4.1 Applicability ..... | 13 | +| 5.1.4.2 Procedure ..... | 13 | +| 5.1.4.3 Establishment..... | 13 | +| 5.1.4.4 Operation ..... | 13 | +| 5.1.5 TCH loop including signalling of erased frames and unreliable frames (D)..... | 14 | +| 5.1.5.1 Procedure ..... | 14 | +| 5.1.6 TCH loop including signalling of erased SID frames (E) ..... | 14 | +| 5.1.6.1 Procedure ..... | 14 | +| 5.1.7 TCH loop including signalling of erased valid SID frames (F) ..... | 15 | +| 5.1.7.1 Procedure ..... | 15 | +| 5.1.7a TCH loop without signalling of erased frames for in-band channel error rate (I)..... | 15 | +| 5.1.7a.1 Procedure ..... | 15 | +| 5.1.8 Additional non-mandatory operating characteristics for single-slot loops..... | 16 | +| 5.2 Multi-slot TCH loops ..... | 16 | +| 5.2.1 Purpose of Multi-slot TCH loops ..... | 16 | +| 5.2.2 Multi-slot TCH burst-by-burst loop (G)..... | 17 | +| 5.2.2.1 Procedure ..... | 17 | +| 5.2.3 Multi-slot TCH loop including signalling of erased frames (H) ..... | 18 | +| 5.2.3.1 Procedure ..... | 18 | +| 5.3 Deactivating loops..... | 18 | +| 5.3.1 Deactivating Single-slot TCH loops..... | 18 | +| 5.3.2 Deactivating Multi-slot TCH loops..... | 18 | +| 5.4 Multi-slot test mode for GPRS & EGPRS ..... | 18 | +| 5.4.1 Initiation ..... | 19 | +| 5.4.1.1 MS Declaration ..... | 19 | +| 5.4.1.2 Establishment of uplink TBF ..... | 19 | +| 5.4.2 Operation ..... | 19 | +| 5.4.2.1 MS Operating in mode a)..... | 19 | +| 5.4.2.2 MS Operating in mode b) ..... | 20 | +| 5.4.2.3 Operational constraints applying to both modes..... | 20 | +| 5.4.3 Termination ..... | 20 | +| 5.4.4 PN Sequence Definition ..... | 21 | +| 5.4.5 Optional Multi-slot operation ..... | 21 | +| 5.5 EGPRS Switched Radio Block Loopback Mode ..... | 21 | +| 5.5.1 Initiation ..... | 22 | +| 5.5.2 Operation ..... | 22 | +| 5.5.3 Termination ..... | 24 | +| 5.5.4 Support of EGPRS MS without 8PSK modulation capability in uplink ..... | 24 | +| 5.5.5 Optional Multi-slot operation ..... | 24 | + +| | | | +|-----------|---------------------------------------------------------------|----| +| 5.5.6 | Support of EGPRS2-A MS..... | 24 | +| 6 | Activating and deactivating EMMI..... | 24 | +| 7 | Activating and deactivating DAI tests ..... | 25 | +| 8 | Message definitions and contents ..... | 25 | +| 8.1 | CLOSE_TCH_LOOP_CMD..... | 26 | +| 8.2 | CLOSE_TCH_LOOP_ACK ..... | 26 | +| 8.3 | OPEN_LOOP_CMD..... | 27 | +| 8.4 | CLOSE_Multi-slot_LOOP_CMD..... | 27 | +| 8.5 | CLOSE_Multi-slot_LOOP_ACK ..... | 28 | +| 8.6 | OPEN_Multi-slot_LOOP_CMD..... | 29 | +| 8.7 | OPEN_Multi-slot_LOOP_ACK..... | 29 | +| 8.8 | Command for the activation of the EMMI, ACT_EMMI_CMD..... | 29 | +| 8.9 | Acknowledge of the activation of the EMMI, ACT_EMMI_ACK ..... | 29 | +| 8.10 | Deactivation of the EMMI, DEACT_EMMI..... | 30 | +| 8.11 | Test_Interface..... | 30 | +| 8.12 | Timer values..... | 31 | +| 8.13 | GPRS_TEST_MODE_CMD ..... | 31 | +| 8.14 | EGPRS_START_RADIO_BLOCK_LOOPBACK_CMD..... | 32 | +| 8.15 | RESET MS POSITIONING STORED INFORMATION..... | 33 | +| 9 | Electrical Man Machine Interface (EMMI) ..... | 33 | +| 9.1 | Use of the EMMI..... | 33 | +| 9.2 | Formal aspects..... | 34 | +| 9.3 | Layered structure of the interface..... | 34 | +| 9.4 | Terminology ..... | 34 | +| 9.5 | Description of the EMMI..... | 34 | +| 9.5.1 | EMMI, Layer 1 ..... | 34 | +| 9.5.1.1 | Mechanical and electrical characteristics ..... | 34 | +| 9.5.1.2 | Transmission and reception characteristics ..... | 35 | +| 9.5.2 | EMMI, layer 2 ..... | 35 | +| 9.5.2.1 | General structure..... | 35 | +| 9.5.2.2 | Control frames ..... | 35 | +| 9.5.2.3 | Frame structure ..... | 35 | +| 9.5.2.4 | Flow of I-frames on layer 2 ..... | 36 | +| 9.5.2.4.1 | Transmission of frames ..... | 36 | +| 9.5.2.4.2 | Reception of frames ..... | 36 | +| 9.5.2.4.3 | Use of ACK and NAK on receiving side ..... | 36 | +| 9.5.2.4.4 | Use of XON and XOF..... | 37 | +| 9.5.2.4.5 | Parameters on layer 2 ..... | 37 | +| 9.5.3 | EMMI, layer 3 ..... | 37 | +| 9.5.3.1 | Message structure ..... | 37 | +| 9.5.3.2 | Definition of messages..... | 38 | +| 10 | Digital audio interface..... | 42 | +| 10.1 | General ..... | 42 | +| 10.2 | Formal aspects..... | 42 | +| 10.3 | Hardware aspect of the interface..... | 43 | +| 10.3.1 | Mechanical characteristics of the interface ..... | 43 | +| 10.3.2 | Electrical characteristics of the interface..... | 43 | +| 10.3.3 | Timing characteristics of the interface ..... | 43 | +| 10.4 | Logical interface..... | 44 | +| 10.5 | Functionality of the DAI ..... | 44 | +| 11 | SIM/ME test interface..... | 45 | +| 11.1 | General ..... | 45 | +| 11.2 | Formal aspects..... | 45 | +| 11.3 | Hardware and logical aspects of the interface..... | 45 | +| 11.4 | Mechanical characteristics of the interface ..... | 45 | +| 12 | Reset MS Positioning Stored Information ..... | 47 | +| 12.1 | General ..... | 47 | + +12.2 Procedure.....47 +13 GAN security certificate .....48 +13.1 General .....48 +13.2 Formal aspects.....48 +Annex A (informative): Change History.....49 + +# --- 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 for Mobile Stations (MS), for the digital cellular communications system and Personal Communication Systems (PCS) operating in the 900 MHz and 1800 MHz band (GSM900 and DCS1800), standardized by 3rd Generation Partnership Project (3GPP), those ME functions which are required for conformance testing purposes only. However, except for the Electrical Man Machine Interface (EMMI) and the Multi-slot TCH Loops, they are required for every mobile station. + +For conformance tests, functions are activated via the radio interface, test SIM or dedicated pins. These functions must be capable of being activated when a test SIM is present but must not function with any other (e.g. network) SIM present except where otherwise stated within the present document. In this state, the MS must be able to perform all functions specified in the present document; in addition however, the special conformance testing functions must be operational. + +The special conformance testing functions of the ME are enabled by use of a dedicated Subscriber Identity Module (test SIM, see 3GPP TS 51.010-1 Annex 4). SIM, in general, is described in 3GPP TS 51.011. The ME recognizes the test SIM by the Administrative Data Field. + +The present document applies to the public land mobile radio service in the GSM900 and DCS1800 systems, using constant envelope modulation and operating on radio frequencies in the 900 and 1800 MHz bands respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle. + +The present document is part of the 3GPP TS series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related TS, nor is it created to provide full understanding of (or parts of) the GSM900 and DCS1800 systems. + +The present document applies to the unit which includes the hardware to establish a connection across the radio interface. + +## 1.1 Conventions + +Unless explicitly stated otherwise, the following conventions apply: + +- "EGPRS" refers to "EGPRS and EGPRS2". +- "EGPRS2" refers to "EGPRS2-A and EGPRS2-B". + +# --- 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 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [3] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". + +- [4] 3GPP TS 51.010: "Mobile Station (MS) conformity specification". +- [5] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". +- [6] (void). +- [7] 3GPP TS 34.109: "Logical Test Interface (FDD) Special conformance testing functions". +- [8] 3GPP TS 22.101: "UMTS Service principles". +- [9] 3GPP TS 45.010: "Radio subsystem synchronization". +- [11] CCITT recommendation O.153 Fascicle IV.4, (Basic parameters for the measurement of error performance at bit rates below the primary rate, Melbourne 1988) +- [12] 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2". + +# --- 3 Definitions, conventions, and applicability + +For abbreviations and acronyms, see 3GPP TS 21.905. + +## 3.1 Mobile station definition and configurations + +In the present document, a MS can be: + +- a vehicle mounted station; +- a portable station; +- a handheld station; +- a vehicle mounted/portable station; +- a vehicle mounted/handheld station. + +For a more detailed description of MS-configurations, see 3GPP TS 22.101. + +## 3.2 Applicability + +The present document is applicable to all MSs. + +# --- 4 Activation and deactivation of special test functions in the MS + +The functions described in the present document can be activated and deactivated from a SS by sending appropriate layer 3 commands to the MS. The protocol discriminator to be used is defined in 3GPP TS 44.018, sub-clause 10.2. + +The layer 3 commands are sent on the DCCH. On layer 2, SAPI 0 is used in acknowledged mode. + +Apart from sending the appropriate deactivation command to the MS the functions can be deactivated by switching off the MS or removing the test SIM. + +The following test functions can be activated (and deactivated): + +- TCH Loop; +- TCH Burst-by-Burst Loop; +- Multi-slot Loop; +- Electrical MMI; + +- Test via DAI. +- Reset MS Positioning Stored Information (activation only) + +The TCH loops and the test via DAI are test functions which are mutually exclusive. + +# 5 Internal test loops + +A number of internal test loops are required providing access to isolated functions of the MS without introducing new physical interfaces just for the reason of type approval testing. Fig 5-1 shows a functional block diagram of a reference MS containing the different test loops. + +NOTE: It should be emphasized that these test loops only describe the functional behaviour of the MS with respect to its external interfaces; physical implementation of the loops is completely left open to the manufacturer. + +A particular loop is activated in an MS by transmitting the appropriate command message to the MS. + +![Figure 5: Test loops in the MS. This functional block diagram illustrates the internal test loops of a Mobile Station (MS). The diagram shows various signal paths and components: + - **Loop A/B/D/E/F/H (Data Loop)**: Located at the top, it includes a 'Channel decoder (data)' and a 'Channel encoder (data)' connected to a 'Terminal adapter'. The adapter has two external ports labeled 'S' and 'R'. + - **Loop C/G (Signal Loop)**: Located in the middle, it includes a 'Channel decoder (signal.)' and a 'Channel encoder (signal.)' connected to a 'Control part'. + - **Loop A/B/D/E/F/H (Speech Loop)**: Located at the bottom, it includes a 'Channel decoder (speech)' connected to a 'Speech decoder' and a 'Channel encoder (speech)' connected to a 'Speech encoder'. + - **External Interfaces**: + - On the left, there are input and output paths for 'Demodulator', 'Decryption', 'Modulator', and 'Encryption' blocks. + - On the right, the 'Speech decoder' is connected to a 'DAC' (Digital-to-Analog Converter) and the 'Speech encoder' is connected to an 'ADC' (Analog-to-Digital Converter). + - Both the 'DAC' and 'ADC' are connected to a 'System Simulator (Digital Audio Interface)' at the bottom right. + - **Internal Connections**: A central vertical bus connects the various decoders and encoders to the 'Control part' and the external interfaces.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +Figure 5: Test loops in the MS. This functional block diagram illustrates the internal test loops of a Mobile Station (MS). The diagram shows various signal paths and components: + - \*\*Loop A/B/D/E/F/H (Data Loop)\*\*: Located at the top, it includes a 'Channel decoder (data)' and a 'Channel encoder (data)' connected to a 'Terminal adapter'. The adapter has two external ports labeled 'S' and 'R'. + - \*\*Loop C/G (Signal Loop)\*\*: Located in the middle, it includes a 'Channel decoder (signal.)' and a 'Channel encoder (signal.)' connected to a 'Control part'. + - \*\*Loop A/B/D/E/F/H (Speech Loop)\*\*: Located at the bottom, it includes a 'Channel decoder (speech)' connected to a 'Speech decoder' and a 'Channel encoder (speech)' connected to a 'Speech encoder'. + - \*\*External Interfaces\*\*: + - On the left, there are input and output paths for 'Demodulator', 'Decryption', 'Modulator', and 'Encryption' blocks. + - On the right, the 'Speech decoder' is connected to a 'DAC' (Digital-to-Analog Converter) and the 'Speech encoder' is connected to an 'ADC' (Analog-to-Digital Converter). + - Both the 'DAC' and 'ADC' are connected to a 'System Simulator (Digital Audio Interface)' at the bottom right. + - \*\*Internal Connections\*\*: A central vertical bus connects the various decoders and encoders to the 'Control part' and the external interfaces. + +Figure 5: Test loops in the MS + +## 5.1 Single-slot TCH loops + +### 5.1.1 Purpose of Single-slot TCH loops + +To establish a transparent loop for TCH blocks a TCH must be active between the SS and MS. The TCH may be full or half rate, speech or data of any rate specified in the GSM system. + +Seven types of Single-slot TCH loop back are defined. + +- 1: The first (A) includes the signalling of erased frames and is used to determine Frame Erasure Ratio (FER) and Residual Bit Error Ratio (RBER) for speech TCH and Bit Error Ratio (BER) for any data TCH. + +In case of TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS and O-TCH/WH, it also includes the signalling of erased valid SID\_UPDATE and RATSCH frames and is used to determine Erased Valid SID\_UPDATE Frame Rate (EVSIDUR) and Erased Valid RATSCH Frame Rate (EVRFR). + +- 2: The second type (B) is required to determine Class II bit error ratio for the speech TCH. +- 3: With the third loop (C) the 114 information bits of each TCH burst (excluding stealing flags) prior to applying benefit of the channel decoder, but after decryption, shall be transmitted in an uplink burst. (Equivalent error rate to TCH/FS Class II). All that is received shall be re-transmitted regardless of the state of the received midamble. The midamble in the uplink bursts shall be the normal midamble used by the MS. SACCH and idle bursts are not looped back. +- 4: The fourth loop (D) includes the signalling of erased frames and unreliable frames and is used to determine Unreliable Frame Ratio (UFR) and Residual Bit Error Ratio (RBER) for TCH/HS. +- 5: The fifth loop (E) includes the signalling of erased SID frames and is used to determine Erased SID Frame Rate (ESIDR) and Residual Bit Error Ratio (RBER) for TCH/HS. +- 6: The sixth loop (F) includes the signalling of erased valid SID frames and is used to determine Erased Valid SID Frame Rate (EVSIDR) and Residual Bit Error Ratio (RBER) for TCH/HS. +- 7: The seventh loop (I) is required to determine frame error rate for the in-band channel.: + - TCH-AFS-INB FER + - TCH-AHS-INB FER + - TCH-WFS-INB FER + - O-TCH/WFS-INB FER + - O-TCH/WH-INB FER + +NOTE: Measurement of TCH/FS chip BER is approximately five times faster using loop C rather than loop B. + +### 5.1.2 TCH loop including signalling of erased frames (A) + +#### 5.1.2.1 Procedure + +The SS orders the MS to close its TCH loop by transmitting a CLOSE\_TCH\_LOOP\_CMD message, specifying the TCH to be looped and that erased frames are to be signalled by the MS. The SS then starts timer TT01. + +If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE\_TCH\_LOOP\_CMD message. + +If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE\_TCH\_LOOP\_ACK message. Upon reception of that message the SS stops timer TT01. + +After the MS has closed its TCH loop, every good speech frame or any user data frame received by the MS on the specified TCH (downlink) shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH (uplink). + +In the case where TCH is TCH/FS, the MS shall loop back the 260 bits after normal channel decoding. + +In the case where TCH is TCH/EFS, the MS shall loop back the 244 bits after normal and preliminary channel decoding. + +In the case where TCH is TCH/HS, the MS shall loop back the 112 bits after normal channel decoding. + +In the case where a TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WH is used, the MS shall loop back the number of bits carried by the downlink speech frame, after normal channel decoding. + +If the channel decoder detects a bad speech frame, then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH (uplink). + +For all TCH, except TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS, if the MS decodes stealing flags as indicating an FACCH frame, then there is no defined response for the MS to the channel encoder for transmission on the TCH (uplink). The FACCH channel shall operate as normal. + +The following requirements apply when TCH is TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS: + +- The Active Codec Set (ACS) may contain between one and four codec modes. +- When the ACS contains more than one codec mode then: + - The MS shall ignore the downlink codec mode commands received from the SS. + - The MS shall use for the uplink the codec mode used for the decoding of the DL speech frame being looped back. + - The MS shall not generate or send codec mode requests. All in band signalling fields (Uplink CMI and CMR) shall be used to indicate the codec mode of the looped back frame. In other words, all uplink in band signalling codewords carry a codec mode indication. + - The MS may change codec mode indication every uplink frame when consecutive frames are not decoded with the same decoder, even if those frames were associated with the same downlink CMI. + - When looping back any of the following frame types: NO\_DATA, RATSCCH, SID\_UPDATE, SID\_UPDATE\_INH, SID\_FIRST, SID\_FIRST\_P1, SID\_FIRST\_P2 or SID\_FIRST\_INH, the MS shall use the codec mode of the previous uplink frame. +- The number of bits that the MS loops back depends on the codec mode used by the MS to decode the downlink frame being looped back. The MS shall loop back the bits from interface 1 (See TS 45.003 figure 1b) of the downlink channel decoder to interface 1 of the uplink channel encoder, i.e. data delivered to the encoding unit: $d(k)$ for $k = 0, 1, \dots, K_d-1$ . (See TS 45.003 sub-clause 2.2). +- Frames in uplink are transmitted using TX\_TYPE = SPEECH\_GOOD, whatever RX\_TYPE decoded in downlink. + +NOTE: The definitions of TX\_TYPE and RX\_TYPE are as per TS 26.093. + +- After the MS has closed its TCH loop, the parameters of every valid SID\_UPDATE frame (RX\_TYPE = SID\_UPDATE and BFI = 0) received by the MS on the specified TCH (downlink), shall be taken from the output of the downlink channel decoder, input to the uplink channel encoder, using TX\_TYPE = SPEECH\_GOOD, and transmitted on the same TCH (uplink). The SID\_UPDATE parameters shall occupy the first 35 bits of the speech frame, all other bits of the speech frame shall be set to 0. +- For TCH/AHS or O-TCH/WHS, since a SID\_UPDATE occupies two speech frames, the expected uplink sequence shall be: + - SPEECH (data as all zeros) followed by SPEECH (parameters from SID\_UPDATE) +- If the channel decoder detects an erased valid SID\_UPDATE frame (RX\_TYPE = SID\_BAD, BFI = 1), then this shall be signalled to the SS by setting the input frame to the uplink channel encoder to zero's, using TX\_TYPE = SPEECH\_GOOD, and transmitting on the TCH (uplink). + - For TCH/AHS or O-TCH/WFS, each erased valid SID\_UPDATE shall result in 2 SPEECH frames with all zero data sent on the uplink. +- After the MS has closed its TCH loop, a RATSCCH message shall not be interpreted by the MS. RATSCCH protocol shall be de-activated and the MS shall not send any form of RATSCCH\_ACKnowledgment. +- RATSCCH data of every valid RATSCCH frame (RX\_TYPE = NO\_DATA (RATSCCH) and BFI = 0) received by the MS on the specified TCH (downlink), shall be taken from the output of the downlink channel decoder, input to the uplink channel encoder, using TX\_TYPE = SPEECH\_GOOD (for TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS), and transmitted on the same TCH (uplink). The bit content of the + +RATSCCH message for TCH/AFS or TCH/WFS or O-TCH/WFS, or RATSCCH\_DATA for TCH/AHS or O-TCH/WHS shall occupy the first 35 bits of the speech frame, all other bits of the speech frame shall be set to 0. + +- For TCH/AHS or O-TCH/WHS, since each RATSCCH\_DATA must be preceded by RATSCCH\_MARKER, where 2 downlink frames are fully populated by the RATSCCH\_MARKER and RATSCCH\_DATA, the expected uplink sequence shall be: + - SPEECH (data as all zeros) followed by SPEECH (data from RATSCCH\_DATA) +- If the channel decoder detects an erased valid RATSCCH frame (RX\_TYPE = NO\_DATA (RATSCCH) and BFI = 1), then this shall be signalled to the SS by setting the input frame to the uplink channel encoder to zero's, using TX\_TYPE = SPEECH\_GOOD (for TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS), and transmitting on the TCH (uplink). +- For TCH/AHS, each erased valid RATSCCH shall result in 2 SPEECH frames with all zero data sent on the uplink. +- If the channel decoder detects an ONSET frame (RX\_TYPE = ONSET) or SID\_FIRST frame (for TCH/AFS or TCH/WFS or O-TCH/WFS only, RX\_TYPE = SID\_FIRST) or a SID\_FIRST\_P1 frame (for TCH/AHS or O-TCH/WHS only, RX\_TYPE = SID\_FIRST) or a NO\_DATA frame (RX\_TYPE = NO\_DATA, not resulting from a RATSCCH) then this shall be signalled to the SS by setting the input frame to the uplink channel encoder to zero's, using TX\_TYPE = SPEECH\_GOOD (for TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS) and transmitting on the TCH (uplink). +- For TCH/AHS or O-TCH/WHS, if the channel decoder detects a SID\_FIRST\_P2 frame or a SID\_FIRST\_INH or SID\_UPDATE\_INH frame then this shall be signalled to the SS by setting the input frame to the uplink channel encoder to zero's, using TX\_TYPE = SPEECH\_GOOD (for TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS) and transmitting on the TCH (uplink). + +### 5.1.3 Speech TCH loop without signalling of erased frames (B) + +#### 5.1.3.1 Procedure + +The SS orders the MS to close its TCH loop by transmitting a CLOSE\_TCH\_LOOP\_CMD message, specifying the TCH to be looped. The SS then starts timer TT01. + +If no TCH is active or any test loop is already closed, the MS shall ignore any CLOSE\_TCH\_LOOP\_CMD message. + +If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE\_TCH\_LOOP\_ACK. Upon reception of that message the SS stops timer TT01. + +After the MS has closed its TCH loop, any speech frame received by the MS on the specified TCH (downlink) shall be taken from the output of the channel decoder, input to the channel encoder, and transmitted on the same TCH (uplink). + +In the case where TCH is TCH/FS, the MS shall loop back the 260 bits after normal channel decoding. + +In the case where TCH is TCH/EFS, the MS shall loop back the 244 bits after normal and preliminary channel decoding. + +In the case where TCH is TCH/HS, the MS shall loop back the 112 bits after normal channel decoding. + +In the case where a TCH/AFS or TCH/AHS is used, the MS shall loop back the number of bits carried by the downlink speech frame, after normal channel decoding. + +The SS should avoid using the FACCH downlink in this situation until the test is complete. + +All requirements defined for Loop A when TCH is TCH/AFS or TCH/AHS also apply to Loop B, except that: + +- The content of bad speech frame is looped back and not set to all zeros +- If the MS detects an erased valid SID\_UPDATE frame (RX\_TYPE = SID\_BAD, BFI = 1), on the specified TCH (downlink), the content of the received frame shall be taken from the output of the downlink channel decoder, input to the uplink channel encoder, using TX\_TYPE = SPEECH\_GOOD, and transmitted on the same TCH (uplink). The SID\_UPDATE parameters shall occupy the first 35 bits of the speech frame, all other bits of the speech frame shall be set to 0. + +- For TCH/AHS, since a SID\_UPDATE occupies two speech frames, the expected uplink sequence shall be: + - SPEECH (data as all zeros) followed by SPEECH (parameters from SID\_UPDATE) +- If the MS detects an erased valid RATSCCH frame (RX\_TYPE = NO\_DATA (RATSCCH) and BFI = 1) on the specified TCH (downlink), the content of the received frame shall be taken from the output of the downlink channel decoder, input to the uplink channel encoder, using TX\_TYPE = SPEECH\_GOOD (for TCH/AFS and TCH/AHS), and transmitted on the same TCH (uplink). The bit content of the RATSCCH message for TCH/AFS or RATSCCH\_DATA for TCH/AHS shall occupy the first 35 bits of the speech frame, all other bits of the speech frame shall be set to 0. +- For TCH/AHS, since each RATSCCH\_DATA must be preceded by RATSCCH\_MARKER, where 2 downlink frames are fully populated by the RATSCCH\_MARKER and RATSCCH\_DATA, the expected uplink sequence shall be: + - SPEECH (data as all zeros) followed by SPEECH (data from RATSCCH\_DATA) + +### 5.1.4 TCH burst-by-burst loop (C) + +#### 5.1.4.1 Applicability + +The test loop shall be implemented by all ME, supporting any TCH. + +#### 5.1.4.2 Procedure + +Establishment and clearing of the loop is performed at ideal radio conditions. + +#### 5.1.4.3 Establishment + +- The establishment shall be commanded by transmitting a CLOSE\_TCH\_LOOP\_CMD message. The SS then starts timer TT01. This command shall be acknowledged by the MS with a CLOSE\_TCH\_LOOP\_ACK message. Upon receipt of that message the SS stops timer TT01. The MS shall establish the loop within one reporting period [SACCH-block = 104 frames] from the sending of the CLOSE\_TCH\_LOOP\_ACK. +- If no TCH is active or any test loop is already closed, the MS shall ignore any CLOSE\_TCH\_LOOP\_CMD message. + +#### 5.1.4.4 Operation + +The round trip delay (RTD), which is the number of TCH frames between the reception of one burst at the MS, and the transmission of the same burst (on the uplink) shall be less than 26 TDMA frames. The actual value shall be declared for the implementation to be tested. + +NOTE 1: The RTD can be as long as required to receive the number of interleaved burst for the relevant TCH. + +NOTE 2: Example of RTD = 5 + +| TDMA
Frame No. | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | +|-------------------|----|----|----|----|-----|----|----|----|----|-----|-----|-----|----|-----|----|-----|-----|-----| +| Downlink | T1 | T2 | T3 | T4 | T5 | T6 | T7 | T8 | T9 | T10 | T11 | T12 | Sd | ... | | | | | +| Uplink | | | | | ... | T1 | T2 | T3 | T4 | T5 | T6 | T7 | Su | T8 | T9 | T10 | T11 | T12 | + +Sd = Downlink SACCH frame, Su = Uplink SACCH frame, Tn = TCH frame + +Note from the above that TCH frames looped back prior to the uplink SACCH (or Idle) frame are delayed on the air interface by 5 TDMA frames, but the TCN frames following the SACCH frame are delayed by 6 TDMA frames. The RTD is therefore not to be confused with the TDMA frame delay for a TCH burst, which varies depending on whether the TCH burst is before or after the uplink SACCH frame. The reason for the variable TDMA time delay is to preserve the uplink SACCH frame position in the multi-frame. Note also that the uplink SACCH data is not a looped back version of the downlink SACCH data. + +### 5.1.5 TCH loop including signalling of erased frames and unreliable frames (D) + +#### 5.1.5.1 Procedure + +The SS orders the MS to close its TCH loop by transmitting a CLOSE\_TCH\_LOOP\_CMD message, specifying the TCH to be looped and that erased frames and unreliable frames are to be signalled by the MS. The SS then starts timer TT01. + +If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE\_TCH\_LOOP\_CMD message. + +If a TCH different from a TCH/HS is active, the MS shall ignore a CLOSE\_TCH\_LOOP\_CMD message containing a request to close a Type D Loop. + +If a TCH/HS is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE\_TCH\_LOOP\_ACK. Upon reception of that message the SS stops timer TT01. + +After the MS has closed its TCH loop, every reliable speech frame (UFI = 0) received by the MS on the specified TCH/HS (downlink) shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH (uplink). + +If the channel decoder detects a bad speech frame or an unreliable frame (BFI = 1 or UFI = 1) or if the MS decodes the stealing flags as indicating an FACCH frame, then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink). The FACCH channel shall operate normally. + +### 5.1.6 TCH loop including signalling of erased SID frames (E) + +#### 5.1.6.1 Procedure + +The SS orders the MS to close its TCH loop by transmitting a CLOSE\_TCH\_LOOP\_CMD message, specifying the TCH to be looped and that erased SID frames are to be signalled by the MS. The SS then starts timer TT01. + +If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE\_TCH\_LOOP\_CMD message. + +If a TCH different from a TCH/HS is active, the MS shall ignore a CLOSE\_TCH\_LOOP\_CMD message containing a request to close a Type E Loop. + +If a TCH/HS is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE\_TCH\_LOOP\_ACK. Upon reception of that message the SS stops timer TT01. + +After the MS has closed its TCH loop, every valid SID frame (SID = 2) or invalid SID frame (SID = 1) received by the MS on the specified TCH/HS (downlink), shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH/HS (uplink). + +If the channel decoder detects an erased SID frame (SID = 0), then this shall be signalled to the SS, by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink). + +If the MS decodes the stealing flags as indicating an FACCH frame, then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink). The FACCH channel shall operate normally. + +### 5.1.7 TCH loop including signalling of erased valid SID frames (F) + +#### 5.1.7.1 Procedure + +The SS orders the MS to close its TCH loop by transmitting a CLOSE\_TCH\_LOOP\_CMD message, specifying the TCH to be looped and that erased valid SID frames are to be signalled by the MS. The SS then starts timer TT01. + +If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE\_TCH\_LOOP\_CMD message. + +If a TCH different from a TCH/HS is active, the MS shall ignore a CLOSE\_TCH\_LOOP\_CMD message containing a request to close a Type F Loop. + +If a TCH/HS is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE\_TCH\_LOOP\_ACK. Upon reception of that message the SS stops timer TT01. + +After the MS has closed its TCH loop, every valid SID frame (SID = 2 and BFI = 0) received by the MS on the specified TCH/HS (downlink), shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH/HS (uplink). + +If the channel decoder detects an erased valid SID frame (SID = 1) or (SID = 0) or ((BFI or UFI) = 1)), then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink). + +If the MS decodes the stealing flags as indicating an FACCH frame, then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH/HS (uplink). The FACCH channel shall operate normally. + +### 5.1.7a TCH loop without signalling of erased frames for in-band channel error rate (I) + +#### 5.1.7a.1 Procedure + +The SS orders the MS to close its TCH loop by transmitting a CLOSE\_TCH\_LOOP\_CMD message, specifying the TCH to be looped and that in-band channel is to be signalled by the MS. The SS then starts timer TT01. + +If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE\_TCH\_LOOP\_CMD message. + +If a TCH different from a TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS is active, the MS shall ignore a CLOSE\_TCH\_LOOP\_CMD message containing a request to close a Type I Loop. + +If a TCH/AFS, TCH/AHS, TCH/WFS, O-TCH/WFS or O-TCH/WHS is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE\_TCH\_LOOP\_ACK. Upon reception of that message the SS stops timer TT01. + +The Active Codec Set may contain between one and four codec modes. + +Once the MS has closed its loop, it shall continuously transmit in uplink the in-band bits that have been decoded in downlink. The decoded DL CMI shall be looped as UL CMR (no downlink adaptation), and the decoded DL CMC shall be looped as UL CMI. + +NOTE: While a Loop I is active, it is expected that the SS transmit a valid downlink signal including speech frames channel encoded according to the DL CMI. + +When the MS has closed its loop, it shall assume that the SS uses the default transmission phase ("odd") for Codec Mode Indication/Codec Mode Command (see TS 45.009), whatever the transmission phase before the loop was closed. + +The MS shall always use in the uplink the codec mode resulting from the decoding of the received Codec Mode Command. The MS shall always send a fixed pattern of alternating 0 and 1 in the uplink direction (bits d(k) of TS 45.003 sub-clause 2.2), with the first bit of the pattern equal to a binary "1" using TX\_TYPE = SPEECH\_GOOD, whatever RX\_TYPE was decoded in the downlink. + +NOTE: The definitions of TX\_TYPE and RX\_TYPE are as per TS 26.093. + +The RATSCCH protocol shall be de-activated when Loop I is activated. The MS shall not interpret the content of downlink RATSCCH messages. The MS shall not send any form of RATSCCH\_ACKnowledgment. + +Loop I is only required to operate when Downlink DTX is not in use. There is no requirement for in band signalling loop back when the MS decodes a SID\_FIRST, SID\_FIRST\_P1, SID\_FIRST\_P2, SID\_FIRST\_INH, SID\_UPDATE, SID\_UPDATE\_INH or ONSET frame. + +Loop I is not designed to measure the performances of in-band signalling over SID\_UPDATE or RATSCCH messages. + +The delays associated with Loop I remain constant for all of the following circumstances: + +- For a given MS implementation. +- For the duration of the MS being powered on. + +- For the duration of the activation of a TCH. The delays associated with a full rate TCH and a half rate TCH may be different. +- For the duration of the closure of Loop I. + +If the MS decodes another type of non-speech frame (FACCH for example), it shall send back an all zero pattern using the same codec mode as the previous uplink frame. If the in band signalling field is supposed to carry the uplink CMI, then this field shall indicate the uplink codec mode in use. If the in band signalling field is supposed to carry the CMR, then this field shall be equal to the previous uplink CMR. + +The SS should avoid using the FACCH downlink in this situation until the test is complete. + +### 5.1.8 Additional non-mandatory operating characteristics for single-slot loops + +In order to optimise the speed and flexibility of mobile manufacturing and repair, the following non-mandatory characteristics of the test loops are suggested: + +- The normal FACCH downlink and uplink functions should ideally be maintained when the test loop is closed. In particular, channel assignments or handovers, and call termination from either the mobile or the base station simulator. +- Following an assignment or handover, the loop should not open if it was closed prior to the handover. +- Following call dropping or deliberate call termination, the loop should be re-opened. +- The loopback functions should ideally operate with or without (i.e. no SIM) the test SIM present, but should not operate with a network SIM present. +- Audio muting should be enabled when the loop is closed. + +## 5.2 Multi-slot TCH loops + +### 5.2.1 Purpose of Multi-slot TCH loops + +To establish a transparent loop for TCH blocks, from multiple slots, a TCH must be active between the SS and MS. + +Two types of Multi-slot TCH loop back are defined: + +- G: With the first loop (G) the 114 information bits of each multi-slot TCH burst (excluding stealing flags) prior to applying benefit of the channel decoder, but after decryption (see Figure 1), shall be transmitted in an uplink burst. (Equivalent error rate to TCH/FS Class II). All that is received shall be re-transmitted regardless of the state of the received midamble. The midamble in the uplink bursts shall be the normal midamble used by the MS. SACCH and idle bursts are not looped back. +- H: The second loop (H) includes the signalling of erased frames and is used to determine Frame Erasure Ratio (FER), Residual Bit Error Ratio (RBER) and Bit Error Ratio (BER) for any multi-slot configuration TCH. + +Each of the two loops shall support the following mechanisms: + +- The first (Multi-slot mechanism 1) is used to loop the TCH data of slot X of the downlink onto the TCH of the main uplink slot (for HSCSD). This mechanism is needed to cover the case where there are more downlink slots than uplink slots. +- The second (Multi-slot mechanism 2) is used to loop as many downlink slots as possible to the corresponding uplink slots, based on the following rules for HSCSD: + - Loop back all bi-directional timeslots, and leave the unidirectional slots not looped back. This maintains the logical association with bi-directional timeslots. + +It should be further noted: + +- The order of the data on the downlink shall be preserved on the uplink. +- The OPEN\_Multi-slot\_LOOP\_CMD message shall open all Multi-slot loops. + +- Assignment to a new multi-slot configuration shall be preceded by an OPEN\_Multi-slot\_LOOP\_CMD message to open all loops. +- It is the responsibility of the System Simulator (SS) to ensure that the correct configuration is enabled for the test. Test loops will be opened by the receipt of a OPEN\_Multi-slot\_LOOP\_CMD or by disconnecting the call. Other behaviour, such as receiving a new TxLev or a channel assignment or handover to a new ARFCN will not affect the test loops. The SS should ensure that a new multislot configuration affecting an existing test loop is not included within channel assignment, handover or configuration change commands. +- If the Multi-slot mechanism 1 is used and a downlink slot that is not part of the current multi-slot configuration is specified, the MS shall ignore the command and send a negative acknowledgment. The loopback state should not change. +- Once a loop is closed, a further loopback command shall over-ride a previous command - multiple CLOSE\_Multi-slot\_LOOP\_CMD messages are not additive. +- Call disconnect for whatever reason shall open all loops. No OPEN\_Multi-slot\_LOOP\_ACK message shall be sent. +- The multi-slot loopback is restricted to the TCH logical channel only. The downlink and uplink FACCH and SACCH should work as if loopback did not exist. +- The Multi-slot TCH loops are in **addition** to any Single-slot TCH loops already specified for the type of MS. + +Support of the Multi-slot loops is mandatory for any MS supporting HSCSD. + +Any MS supporting the Multi-Slot loops shall activate the functions defined in this sub-clause of the specification regardless of the presence or not of a test SIM. + +### 5.2.2 Multi-slot TCH burst-by-burst loop (G) + +#### 5.2.2.1 Procedure + +The establishment shall be commanded by transmitting a CLOSE\_Multi-slot\_LOOP\_CMD message. The SS then starts timer TT01. This command shall be acknowledged by the MS with a CLOSE\_Multi-slot\_LOOP\_ACK message. Upon receipt of that message the SS stops timer TT01. The MS shall establish the loop within one reporting period [SACCH-block = 104 frames] from the sending of the CLOSE\_Multi-slot\_LOOP\_ACK. + +If no TCH is active or any test loop is already closed, the MS shall ignore any CLOSE\_Multi-slot\_LOOP\_CMD message + +RTD is as the same as sub-clause 5.1.4.4. + +### 5.2.3 Multi-slot TCH loop including signalling of erased frames (H) + +#### 5.2.3.1 Procedure + +The SS orders the MS to close its Multi-slot TCH loop by transmitting a CLOSE\_Multi-slot\_LOOP\_CMD message, specifying the TCH to be looped and that erased frames are to be signalled by the MS. The SS then starts timer TT01. + +If no TCH is active, or any test loop is already closed, the MS shall ignore any CLOSE\_Multi-slot\_LOOP\_CMD message. + +If a TCH is active, the MS shall close its TCH loop for the TCH specified and send back to the SS a CLOSE\_Multi-slot\_LOOP\_ACK message. Upon reception of that message the SS stops timer TT01. + +After the MS has closed its TCH loop, every good speech frame or any user data frame received by the MS on the specified TCH (downlink) shall be taken from the output of the channel decoder, input to the channel encoder and transmitted on the same TCH (uplink). + +If the channel decoder detects a bad speech frame , then this shall be signalled to the SS by setting the input frame to the channel encoder to zero's, and transmitting on the TCH (uplink). + +If the MS decodes stealing flags as indicating an FACCH frame, then there is no defined response for the MS to the channel encoder for transmission on the TCH (uplink). The FACCH channel shall operate as normal. + +## 5.3 Deactivating loops + +### 5.3.1 Deactivating Single-slot TCH loops + +The SS orders the MS to open any Single-slot TCH loop by transmitting an OPEN\_LOOP\_CMD message. + +If no loop is closed the MS shall ignore any OPEN\_LOOP\_CMD message. + +If a Single-slot TCH is looped, the MS shall open the loop. + +If the loop opened was type C, the MS shall send an OPEN\_LOOP\_CMD message to the SS with bit 0 of the optional acknowledgement element set to 1. + +All channels shall be open for normal use again. + +### 5.3.2 Deactivating Multi-slot TCH loops + +The SS orders the MS to open any Multi-slot TCH loop by transmitting an OPEN\_Multi-slot\_LOOP\_CMD message. + +If no loop is closed the MS shall ignore any OPEN\_Multi-slot\_LOOP\_CMD message. + +If a Multi-slot TCH is looped, the MS shall open the loop and send a OPEN\_Multi-slot\_LOOP\_ACK message to the SS. + +All channels shall be open for normal use again. + +## 5.4 Multi-slot test mode for GPRS & EGPRS + +The following test mode applies to GPRS, EGPRS and EGPRS2 + +### 5.4.1 Initiation + +#### 5.4.1.1 MS Declaration + +The manufacturer shall declare the MS test mode capability before test mode initiation. The possible declarations are as follows: + +- a) MS is capable of transmitting a pseudo-random data sequence in RLC data blocks +- b) MS is capable of transmitting looped-back RLC data blocks (Not applicable to an MS in EC operation) +- c) MS is capable of both a) and b). + +The specifics of test mode initiation and operation depend on what capability the MS has declared. In addition to options a), b) or c), an EGPRS MS shall also support the EGPRS Radio Block Loopback Mode defined in sub-clause 5.5. + +#### 5.4.1.2 Establishment of uplink TBF + +The MS is assumed to be GPRS attached, in packet idle mode. + +The SS establishes a downlink TBF on one timeslot, according to normal procedures as defined in 3GPP TS 44.060. + +The SS orders the MS into GPRS test mode by transmitting a GPRS\_TEST\_MODE\_CMD (Layer 3 message, SAPI 1) with parameter PDU Description set to define the number of PDUs and number of octets within the PDUs that the MS is to transmit in the uplink during the test. The SS then starts timer TT02. + +If the MS has declared c) capability in sub-clause 5.4.1.1, then the M bit in the GPRS\_TEST\_MODE\_CMD message shall determine whether the MS operates the test mode in mode a) or mode b). + +This commands the MS to request the establishment of an uplink TBF, in RLC unacknowledged mode, according to normal procedures as defined in 3GPP TS 44.060. Upon receipt of the MS request for uplink resources, the SS stops timer TT02 and proceeds with the establishment of the uplink TBF, by assigning a Dynamic Allocation uplink TBF or an Extended Dynamic Allocation uplink TBF. If the MS is operating in mode a), the SS releases the downlink TBF + +according to normal procedures as defined in 3GPP TS 44.060. If the MS is operating in mode b), the downlink TBF continues throughout test mode operation. + +An exception applies for an MS in EC operation (see 3GPP TS 43.064[12]) where this commands the MS to request the establishment of an uplink TBF, in RLC acknowledged mode, according to normal procedures as defined in 3GPP TS 44.060. Upon receipt of the MS request for uplink resources, the SS stops timer TT02 and proceeds with the establishment of the uplink TBF, by assigning a Fixed Uplink Allocation TBF. If the MS is operating in mode a), the SS releases the downlink TBF according to normal procedures as defined in 3GPP TS 44.060. + +The SS shall not send a new GPRS\_TEST\_MODE\_CMD to the MS unless the currently activated multi-slot test mode for GPRS is terminated. + +When the MS has activated the multi-slot test mode for GPRS, the received RLC data blocks (on the MS side) shall not be passed to LLC. + +### 5.4.2 Operation + +#### 5.4.2.1 MS Operating in mode a) + +The SS sets the USF field in blocks transmitted on the downlink to address the MS. The MS shall transmit RLC data blocks obeying USF, according to the normal rules for transmission, as defined in 3GPP TS 44.060. An exception case is where an MS has enabled EC operation (see 3GPP TS 43.064 [12]) in which case the MS is not allocated resources by USF. In this case the SS shall allocate resources through Fixed Uplink Allocation. The MS shall transmit RLC data blocks obeying the Fixed Uplink Allocation(s), according to 3GPP TS 44.018, and 3GPP TS 44.060. + +For the uplink the data payload of the RLC data blocks shall contain a pseudorandom data sequence, as specified in sub-clause 5.4.4. The blocks shall have valid MAC headers and may have valid RLC headers. The blocks shall be processed by Layer 1 in the normal manner. + +Where multiple transmit timeslots are active, the same data as is carried in the RLC data block in the first timeslot may be used in RLC data blocks carried in subsequent time-slots. The blocks shall have valid MAC headers and may have valid RLC headers. The blocks shall be processed by Layer 1 in the normal manner. + +#### 5.4.2.2 MS Operating in mode b) + +The SS shall transmit RLC data blocks on the downlink TBF containing a pseudorandom data sequence in the data payload of the block, as specified in sub-clause 5.4.4. The blocks shall have valid MAC and RLC headers. The SS shall apply the same channel coding scheme on the downlink data blocks as the commanded coding scheme on the uplink. The blocks shall be processed by Layer 1 in the normal manner. + +The SS sets the USF field in blocks transmitted on the downlink to address the MS. The MS shall transmit RLC data blocks obeying USF, according to the normal rules for transmission, as defined in 3GPP TS 44.060. + +For the uplink, the data payload of the RLC data blocks shall contain the data payload of the RLC data blocks transmitted on the downlink TBF. The blocks shall have valid MAC headers and may have valid RLC headers. The countdown procedure shall not be used for the uplink RLC data blocks (CV=15). + +When RLC/MAC control blocks are received on the downlink, the MS may repeat on the uplink the pseudorandom sequence carried in the previous uplink RLC data blocks. + +In the event where the USF field is correctly decoded but there is a CRC error on the payload data the MS shall, if required by the USF, transmit the received payload data. + +When RLC/MAC control blocks are sent on the uplink, the MS may discard the pseudorandom sequence that would otherwise have been transmitted at that time. Where multiple transmit timeslots are active, and only one downlink timeslot is active, the same data as is carried in the RLC data block in the first timeslot may be used in RLC data blocks carried in subsequent time-slots. The blocks shall have valid MAC headers and may have valid RLC headers. The blocks shall be processed by Layer 1 in the normal manner. + +#### 5.4.2.3 Operational constraints applying to both modes + +During test mode operation, the MS shall continue to receive RLC/MAC control blocks sent on the downlink, and shall respond normally. + +### 5.4.3 Termination + +Termination of the test mode occurs for test mode operating in mode a), either when the requested number of PDUs have been transmitted on the uplink TBF, or when the SS initiates the TBF release. For test mode operating in mode b), termination of test mode occurs when the SS terminates the downlink TBF, or when the SS initiates PDCH release for the uplink TBF. + +![Sequence diagram illustrating Test mode termination between SS and MS.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` + +sequenceDiagram + participant SS + participant MS + Note left of SS: SS starts transmitting PN sequence on 1 timeslot + SS->>MS: L3, SAPI 1: GPRS_TEST_MODE_CMD + MS-->>SS: PRACH: PACKET_CHANNEL_REQUEST + Note right of MS: MS starts transmitting PN sequence on n timeslots + MS-->>SS: PACKET_UPLINK_ASSIGNMENT ( n x TS ) + Note left of SS: Data = e.g. PN15 + SS->>MS: Data = e.g. PN15 + Note right of MS: Data = e.g. PN15 + MS->>SS: Data = e.g. PN15 + Note right of MS: OR... + SS->>MS: PACKET_TBF_RELEASE + Note left of SS: Countdown procedure to CV = 0 + SS-->>MS: + +``` + +The diagram shows the interaction between a Station (SS) and a Mobile Station (MS) for test mode termination. The sequence starts with the SS sending an 'L3, SAPI 1: GPRS\_TEST\_MODE\_CMD' to the MS. The MS responds with 'PRACH: PACKET\_CHANNEL\_REQUEST'. The SS then sends a 'PACKET\_UPLINK\_ASSIGNMENT ( n x TS )' to the MS. Both SS and MS start transmitting PN sequences (e.g., PN15) on timeslots. The SS starts on 1 timeslot, and the MS starts on n timeslots. After some data transmission, the SS sends a 'PACKET\_TBF\_RELEASE' to the MS, followed by a 'Countdown procedure to CV = 0'. The sequence ends with an 'OR...' indicating alternative termination paths. + +Sequence diagram illustrating Test mode termination between SS and MS. + +Figure 5.4.3: Test mode termination + +### 5.4.4 PN Sequence Definition + +The data to be inserted into the data part of the RLC/MAC data blocks is generated using any binary pseudorandom sequence generator with a cycle of 32,767 bits or greater (for example CCITT defined PN15, PN22 etc.). + +Example test patterns may be found in CCITT recommendation O.153 Fascicle IV.4, (Basic parameters for the measurement of error performance at bit rates below the primary rate, Melbourne 1988). + +### 5.4.5 Optional Multi-slot operation + +To facilitate production tests and for other purposes, the MS may optionally implement the following extension to this test mode. + +If the downlink TBF is established on more than one timeslot, the MS shall transmit in the second uplink timeslot (if present) RLC/MAC blocks received on the second downlink timeslot, and shall transmit in the third uplink timeslot (if present) RLC/MAC blocks received in the third downlink timeslot and so on. + +If more transmit timeslots are present than receive timeslots, then the contents of uplink timeslots that do not map to downlink timeslots shall be the same as in the last timeslot that maps to downlink. + +However, if the downlink TBF contains only a single timeslot the MS must fill all uplink timeslots as defined in sub-clause 5.4.2 above. + +In this description, downlink timeslots are counted from the "Downlink Timeslot Offset" in the mode flag of the GPRS\_TEST\_MODE\_CMD. For example, if the "Downlink Timeslot Offset" is set to 3, TN3 shall be treated as the first downlink timeslot if a TBF is established in TN3. If TN3 does not support a TBF, the first active timeslot after TN3 shall be treated as the first downlink timeslot. The counting sequence is continuous through TN7 and TN0. + +Uplink timeslots are always counted from TN0. + +## 5.5 EGPRS Switched Radio Block Loopback Mode + +The EGPRS Switched Radio Block Loopback mode must be supported by an EGPRS MS. It is a Physical RF layer loopback performed before channel decoding designed to support BER testing. + +The following loopback path is used: + +![Figure 5.5: Loopback Mode diagram showing the signal flow between a Demodulator, Decoder, Modulator, Coder, and various buffers and formatters.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +The diagram illustrates the signal flow for the EGPRS Switched Radio Block Loopback mode. It consists of two main paths: a downlink path (top) and an uplink path (bottom), connected by a central 'Radio Block Buffer' and 'Burst Formatter'. + +- Downlink Path:** An external signal enters the 'Demodulator', which outputs to the 'Radio Block Buffer'. From the buffer, the signal can be diverted to the 'Radio Block Loopback' block or proceed to the 'Decoder'. The 'Decoder' outputs to 'To RLC/MAC'. +- Uplink Path:** A signal from 'From RLC/MAC' enters the 'Coder', which outputs to the 'Radio Block Buffer'. From the buffer, the signal proceeds to the 'Burst Formatter', then to the 'Modulator', which outputs the final signal. +- Control:** A large curved arrow indicates the switching mechanism between the 'Radio Block Buffer' and the 'Radio Block Loopback' block. + +Figure 5.5: Loopback Mode diagram showing the signal flow between a Demodulator, Decoder, Modulator, Coder, and various buffers and formatters. + +Figure 5.5: Loopback Mode + +### 5.5.1 Initiation + +The MS is assumed to be GPRS attached, in packet idle mode. + +The SS establishes a downlink TBF on one timeslot, according to normal procedures as defined in 3GPP TS 44.060. + +The SS orders the MS into EGPRS Switched Radio Block Loopback Mode by transmitting a EGPRS\_START\_RADIO\_BLOCK\_LOOPBACK\_CMD (Layer 3 message, LLC SAPI 1). The SS then starts timer TT02. + +This will force the MS to request the establishment of an uplink TBF, in RLC unacknowledged mode, according to normal procedures as defined in 3GPP TS 44.060. Upon receipt of the MS request for uplink resources, the SS stops timer TT02 and proceeds with the establishment of the uplink TBF, by assigning a Dynamic Allocation uplink TBF or an Extended Dynamic Allocation uplink TBF. + +The downlink and uplink TBF continue throughout test mode operation, as described in 5.5.2. + +After the MS has been assigned a Dynamic Allocation uplink TBF or an Extended Dynamic Allocation uplink TBF, the SS shall start timer TT03. After this timer expires the SS shall start to transmit radio blocks to the MS using the same downlink resources as the existing downlink TBF. The radio blocks shall contain a valid RLC/MAC header (addressing the MS) and an RLC data block (or blocks) to be filled with pseudorandom data as specified in 5.4.4, or contain an RLC/MAC control message. + +When the MS has activated the EGPRS Switched Radio Block Loopback mode, any received RLC data blocks (on the MS side) shall not be passed to LLC. + +### 5.5.2 Operation + +The downlink and uplink TBFs shall remain open throughout switched radio block loopback mode operation. Timers T3180, T3182 and T3164 shall be disabled throughout switched radio block loopback mode operation to prevent the uplink TBF from expiring. + +EGPRS Switched Radio Block Loopback mode defines two Sub-modes of operation - Radio Block Loopback ON and Radio Block Loopback OFF. When the EGPRS Switched Radio Block Loopback mode is initiated, the MS shall enter the Radio Block Loopback ON sub-mode. + +![Figure 5.5.2: Loopback Sub-modes. A state transition diagram showing the flow between Packet Idle Mode, Establish DL TBF, Establish UL TBF, Loopback ON, and Loopback OFF. The top three states are grouped under 'Normal Operation', and the bottom two are under 'EGPRS Switched Radio Block Loopback Mode'. Transitions exist from Packet Idle Mode to Establish DL TBF, then to Establish UL TBF. From Establish UL TBF, there is a transition to Loopback ON. Both Loopback ON and Loopback OFF have transitions back to Packet Idle Mode. There is also a bidirectional transition between Loopback ON and Loopback OFF.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +graph TD + subgraph Normal_Operation [Normal Operation] + PIM[Packet Idle Mode] --> EDTBF[Establish DL TBF] + EDTBF --> EUTBF[Establish UL TBF] + end + EUTBF --> LO[Loopback ON] + LO --> PIM + LO <--> LOff[Loopback OFF] + LOff --> PIM + subgraph EGPRS_Switched_Radio_Block_Loopback_Mode [EGPRS Switched Radio Block Loopback Mode] + LO + LOff + end + +``` + +Figure 5.5.2: Loopback Sub-modes. A state transition diagram showing the flow between Packet Idle Mode, Establish DL TBF, Establish UL TBF, Loopback ON, and Loopback OFF. The top three states are grouped under 'Normal Operation', and the bottom two are under 'EGPRS Switched Radio Block Loopback Mode'. Transitions exist from Packet Idle Mode to Establish DL TBF, then to Establish UL TBF. From Establish UL TBF, there is a transition to Loopback ON. Both Loopback ON and Loopback OFF have transitions back to Packet Idle Mode. There is also a bidirectional transition between Loopback ON and Loopback OFF. + +**Figure 5.5.2: Loopback Sub-modes** + +Switching between the two Sub-modes is controlled by the use of the Payload Type field in the MAC header of RLC/MAC control messages. During EGPRS Switched Radio Block Loopback mode, the Payload Type field conveys two pieces of information - whether or not the optional octets of the RLC/MAC control header have been included (as for normal operation) and an instruction to change between Radio Block Loopback Sub-modes. If in Radio Block Loopback Sub-mode ON, an instruction to turn ON the Radio Block Loopback Sub-mode shall be ignored, similarly an instruction to turn OFF the Radio Block Loopback Sub-mode when in Radio Block Loopback Sub-mode OFF. The MS shall stay in EGPRS Switched Radio Block Loopback Mode whether in Radio Block Loopback Sub-mode ON or OFF until it is terminated by the procedure detailed in 5.5.3. + +**Table 5.5.2: Payload Type** + +| bit
8 7 | Payload Type meaning during
normal operation | Payload Type meaning in EGPRS Switched
Radio Block Loopback Mode | Loopback Sub-
Mode Control | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| +| 0 0 | RLC/MAC block contains an RLC data block | RLC/MAC block contains an RLC/MAC control block that does not include the optional octets of the RLC/MAC control header | Loopback Sub Mode ON | +| 0 1 | RLC/MAC block contains an RLC/MAC control block that does not include the optional octets of the RLC/MAC control header | | Loopback Sub Mode OFF | +| 1 0 | In the downlink direction, the RLC/MAC block contains an RLC/MAC control block that includes the optional first octet of the RLC/MAC control header.
In the uplink direction, this value is reserved. | In the downlink direction, the RLC/MAC block contains an RLC/MAC control block that includes the optional first octet of the RLC/MAC control header.
In the uplink direction, this value is reserved | Loopback Sub-Mode ON | +| 1 1 | Reserved. In this version of the protocol, the mobile station shall ignore all fields of the RLC/MAC block except for the USF field | | Loopback Sub-Mode OFF | + +If in Radio Block Loopback Sub-mode ON, the MS shall receive all radio blocks and, before they pass through the decoding process (see figure in sub-clause 5.5), shall send them to the SS using the same uplink resources as the existing uplink TBF. The radio blocks shall be resent on the very next block period regardless of USF or TFI decoding. The radio blocks shall also pass through the decoding process and if the RLC/MAC header is successfully decoded shall be sent to RLC/MAC. When in Radio Block Loopback Sub-mode ON, the MS should not send any control messages or data from RLC/MAC to its own Physical Link layer for transmission. + +If in Radio Block Loopback Sub-mode OFF, the MS shall not loopback any radio blocks received. It can send control messages or data to be transmitted, following the normal procedures in 3GPP TS 44.060 for a dynamic allocation. + +Whether in Radio Block Loopback Sub-mode ON or OFF, the MS must obey any RLC/MAC control messages referring to the uplink or downlink TBF. + +### 5.5.3 Termination + +The SS orders the MS to terminate EGPRS Switched Radio Block Loopback Mode by transmitting a Packet TBF release, releasing the uplink and downlink TBFs. If timer T3190 expires EGPRS Switched Radio Block Loopback Mode shall also be terminated. If EGPRS test mode is terminated, the MS shall stop transmitting on the uplink, discard any data associated with the uplink TBF and return to packet idle mode. + +### 5.5.4 Support of EGPRS MS without 8PSK modulation capability in uplink + +EGPRS Switched Radio Block Loopback Mode makes provision for EGPRS MS without 8PSK modulation capability in uplink in the following manner. If the uplink TBF was established using a GMSK modulation scheme, and the downlink is 8PSK modulated, a radio block sent by the SS on a downlink timeslot using 8PSK modulation should be followed by two radio blocks on the same timeslot where the SS transmits GSM dummy bursts. The MS shall retransmit the received 8PSK data over the following three radio blocks on the matching uplink timeslot. + +The EGPRS MS without 8PSK modulation capability in uplink shall not retransmit the last 16 encrypted bits received in an 8PSK radio block when retransmitting it using GMSK modulation. + +The stealing bits of the GMSK blocks shall be ignored by the SS. + +The SS shall select this mode by setting bit 1 of the Mode Flag in the EGPRS\_START\_RADIO\_BLOCK\_LOOPBACK\_CMD message. See sub-clause 8.14. + +### 5.5.5 Optional Multi-slot operation + +To facilitate production tests and for other purposes, the MS may optionally implement the following extension to this test mode. + +If the downlink TBF is established on more than one timeslot, the MS shall transmit in the second uplink timeslot (if present) radio blocks received on the second downlink timeslot, and shall transmit in the third uplink timeslot (if present) radio blocks received in the third downlink timeslot and so on. + +If more transmit timeslots are present than receive timeslots, then the contents of uplink timeslots that do not map to downlink timeslots shall be the same as in the last timeslot that maps to downlink. + +However, if the downlink TBF contains only a single timeslot the MS must fill all uplink timeslots as defined in sub-clause 5.5.2 above. + +In this description, downlink timeslots are counted from the "Downlink Timeslot Offset" in the mode flag of the EGPRS\_START\_RADIO\_BLOCK\_LOOPBACK\_MODE\_CMD. For example, if the "Downlink Timeslot Offset" is set to 3, TN3 shall be treated as the first downlink timeslot if a TBF is established in TN3. If TN3 does not support a TBF, the first active timeslot after TN3 shall be treated as the first downlink timeslot. The counting sequence is continuous through TN7 and TN0. + +Uplink timeslots are always counted from TN0. + +### 5.5.6 Support of EGPRS2-A MS + +If the uplink TBF was established using 16QAM modulation scheme and the downlink is 32QAM modulated, four radio blocks sent by the SS on a downlink timeslot shall be followed by one radioblock with a GSM dummy burst. The MS shall retransmit the received data over five consecutive radio blocks on the matching uplink timeslot. + +# --- 6 Activating and deactivating EMMI + +Activating EMMI requires the presence of a test SIM. EMMI shall be activated by any of the following: + +- switching on the MS; +- inserting a test SIM; +- layer 3 message on the radio interface (ACT\_EMMI\_CMD). + +When the MS is ready to receive frames, it shall send one XON message. + +EMMI shall be deactivated by any of the following: + +- switching off the MS; +- removing the test SIM; +- layer 3 message on the radio interface (DEACT\_EMMI). + +NOTE: No XOF shall be sent after deactivation. + +The L3 message used on the radio interface to activate the EMMI is the activation command ACT\_EMMI\_CMD (see sub-clause 8.4). This message has to be acknowledged by the message ACT\_EMMI\_ACK on the radio interface sent by the MS (see sub-clause 8.5). + +For deactivation of the EMMI in the MS through the radio interface, the message DEACT\_EMMI is defined in sub-clause 8.6. An acknowledgement of this message is not required. + +# --- 7 Activating and deactivating DAI tests + +Purpose: to determine the routing of speech data (DAI or internal, i.e. normal mode) and which device is being tested (speech transcoder / DTX functions or A/D & D/A). + +Prerequisites: a dedicated channel must be established if the manufacturer has stated that the DAI is activated by means of the layer 3 message. + +Procedure: the SS sends a TEST\_INTERFACE message if the manufacturer has stated that the DAI is activated by means of the layer 3 message or applies the appropriate control signal on the DAI if the manufacturer has declared that the DAI is activated this way. + +When the test mode is established i.e. speech data comes from test interface, each new test function overrides the previous one. + +# --- 8 Message definitions and contents + +NOTE 1: A message received with skip indicator different from 0 will be ignored. + +NOTE 2: For definition of "Presence" and "Format", see 3GPP TS 24.007. + +NOTE 3: GSM and UTRAN test messages use the same protocol discriminator value ("1111"). Following message type value series are reserved for GSM testing commands: 0000xxxx, 0001xxxx and 0010xxxx where x represent 0 or 1. For UTRAN test commands, as specified by 3GPP TS 34.109, the message type value series 0100xxxx is reserved. + +## 8.1 CLOSE\_TCH\_LOOP\_CMD + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | +| Sub-channel | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| | | | | | | | | octet 1 | + +and Sub-channel is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +|-------|-------|---|---|---|---|---|---|---------| +| 0 | 0 | C | B | A | Z | Y | X | | +| spare | spare | | | | | | | octet 1 | + +X = 0 If there is only one TCH active (so there is no choice) or if sub-channel 0 of two half rate channels is to be looped. + +X = 1 If sub-channel 1 of two half rate channels is to be used. + +Other bits of the Sub-channel are given by the following table: + +| Test Loop | Bits C to Y from Sub-channel | | | | | +|------------------------------------------------|------------------------------|---|---|---|---| +| | C | B | A | Z | Y | +| A | 0 | 0 | 0 | 0 | 0 | +| B | 0 | 0 | 0 | 0 | 1 | +| C | 0 | 0 | 0 | 1 | - | +| D | 0 | 0 | 1 | - | - | +| E | 0 | 1 | 0 | - | - | +| F | 0 | 1 | 1 | - | - | +| I | 1 | 1 | 1 | - | - | +| Where "-" means that the value is disregarded. | | | | | | + +## 8.2 CLOSE\_TCH\_LOOP\_ACK + +This message is only sent in the direction MS to SS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | | +| | | | | | | | | Octet 1 | + +## 8.3 OPEN\_LOOP\_CMD + +This message is only sent in the direction SS to MS + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | +| Acknowledge | | O | TV | 1 | + +where message type is: + +| | | | | | | | | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | | +| | | | | | | | | Octet 1 | + +where Acknowledge Information Element Identifier is: + +| | | | | | | | | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +| 1 | 0 | 0 | 0 | | | | | | +| | | | | | | | | Octet 1 | + +and the Acknowledge Information Element contents are: + +| | | | | | | | | | +|--|--|--|--|------------|------------|------------|----------|----------------| +| | | | | 4 | 3 | 2 | 1 | Bit no. | +| | | | | 0
spare | 0
spare | 0
spare | 1 | | +| | | | | | | | | Octet 1 | + +## 8.4 CLOSE\_Multi-slot\_LOOP\_CMD + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | +| Loop type | | M | V | 1 | + +where message type is: + +| | | | | | | | | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | | +| | | | | | | | | octet 1 | + +and Loop type is: + +| | | | | | | | | | +|----------|----------|----------|----------------|----------|----------|----------|----------|----------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| | TN | | Loop mechanism | | | CHC | | | +| | | | | | | | | octet 1 | + +CHC, Channel coding + +00 = channel coding not needed. The Burst-by-Burst loop is activated, type G + +01 = channel coding needed. Frame erasure is to be signalled, type H + +All other values reserved + +Loop mechanism + +000 = Multi-slot mechanism 1 + +001 = Multi-slot mechanism 2 + +All other values reserved + +TN, Timeslot number + +Timeslot number used only if Loop mechanism indicates Multi-slot mechanism 1 + +The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010. + +Range: 0 to 7 + +## 8.5 CLOSE\_Multi-slot\_LOOP\_ACK + +This message is only sent in the direction MS to SS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | +| Result | | M | V | 1 | + +where message type is: + +| | | | | | | | | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | | +| | | | | | | | | Octet 1 | + +and Result is: + +| | | | | | | | | | +|----------|----------|----------|----------|----------------|----------|----------|-----------|----------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | CHC | | Loop mechanism | | | Error Ind | octet 1 | +| spare | spare | | | | | | | | + +CHC, Channel coding + +00 = channel coding not needed. The Burst-by-Burst loop is activated, type G + +01 = channel coding needed. Frame erasure is to be signalled, type H + +All other values reserved + +Loop mechanism + +000 = Multi-slot mechanism 1 + +001 = Multi-slot mechanism 2 + +All other values reserved + +Error Ind, Error indication + +0 = Multi-slot TCH loop was closed successfully + +1 = Multi-slot TCH loop was not closed due to error + +## 8.6 OPEN\_Multi-slot\_LOOP\_CMD + +This message is only sent in the direction SS to MS + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | Octet 1 | + +## 8.7 OPEN\_Multi-slot\_LOOP\_ACK + +This message is only sent in the direction MS to SS + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | Octet 1 | + +## 8.8 Command for the activation of the EMMI, ACT\_EMMI\_CMD + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | Octet 1 | + +## 8.9 Acknowledge of the activation of the EMMI, ACT\_EMMI\_ACK + +This message is only sent in the direction MS to SS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | 1/2 | +| Skip indicator | 3GPP TS 24.007 | M | V | 1/2 | +| Message type | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | Octet 1 | + +## 8.10 Deactivation of the EMMI, DEACT\_EMMI + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | 1/2 | +| Skip indicator | 3GPP TS 24.007 | M | V | 1/2 | +| Message type | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | Octet 1 | + +## 8.11 Test\_Interface + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | 1/2 | +| Skip indicator | 3GPP TS 24.007 | M | V | 1/2 | +| Message type | | M | V | 1 | +| Tested device | | M | V | 1 | + +where message type is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +|---|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | Octet 1 | + +and Tested device is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bit no. | +|-------|-------|-------|-------|-------|----------------|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | Tested devices | | | | +| spare | spare | spare | spare | spare | | | | | + +Tested devices: + +000 = normal operation (no tested device via DAI) + +001 = test of speech decoder / DTX functions (downlink) + +010 = test of speech encoder / DTX functions (uplink) + +100 = test of acoustic devices and A/D & D/A. + +All other values are reserved. + +## 8.12 Timer values + +TT01: To be started when a CLOSE\_TCH\_LOOP\_CMD or CLOSE\_Multi-slot\_LOOP\_CMD is sent. To be stopped when the corresponding CLOSE\_TCH\_LOOP\_ACK or CLOSE\_Multi-slot\_LOOP\_ACK is received. + +Recommended value: [2.5 seconds]. + +TT02: To be started when a GPRS\_TEST\_MODE\_CMD is sent. To be stopped when the MS requests uplink resources. + +Recommended value: [2.5 seconds]. + +TT03: To be started when an MS has requested uplink resources following the transmission of an EGPRS\_START\_RADIO\_BLOCK\_LOOPBACK\_MODE\_CMD. + +Recommended value: [50 ms]. + +## 8.13 GPRS\_TEST\_MODE\_CMD + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | 1/2 | +| Skip indicator | 3GPP TS 24.007 | M | V | 1/2 | +| Message type | | M | V | 1 | +| PDU description | | M | V | 2 | +| Mode Flag | | M | V | 1 | + +where message type is: + +| | | | | | | | | | +|---------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | | +| Octet 1 | | | | | | | | | + +PDU Description is: + +| | | | | | | | | | +|---------|-------|-------|-------|-----|-----|----|----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| L | 0 | 0 | 0 | d11 | d10 | d9 | d8 | | +| | Spare | Spare | Spare | | | | | Octet 1 | +| d7 | d6 | d5 | d4 | d3 | d2 | d1 | d0 | | +| Octet 2 | | | | | | | | | + +PDU Description only applies if the MS is operating in mode a). The PDU consists of the pseudorandom data sequence only, ie, it shall not contain any header information or FCS field. + +L = 1 PDUs of constant length from 140 up to 1560 octets shall be transferred. The maximum length of the PDU is an implementation specific issue and shall be declared for the implementation to be tested. The number of PDUs to be transmitted is expressed by d11 - d0 as a binary representation. Range is 1 to 4095. + +| | | | | | | | | | | | | | +|-----|-----|----|----|----|----|----|----|----|----|----|----|------------| +| D11 | d10 | d9 | d8 | d7 | d6 | d5 | d4 | d3 | d2 | d1 | d0 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | = See Note | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | = 1 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | = 2 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | = 3 | +| ... | | | | | | | | | | | | | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | = 4095 | + +NOTE: When the number of PDUs is set to zero, it may optionally be interpreted by the MS as meaning an infinite number of PDUs to be transmitted in the TBF. Infinite duration TBFs are not supported through normal RLC/MAC operation. Therefore, implementation of this feature is left as optional. + +L = 0 Reserved + +Mode Flag is: + +| | | | | | | | | | +|-------|-------|-------|-------|--------------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | 0 | 0 | Downlink Timeslot Offset | | | | M | +| Spare | Spare | Spare | Spare | | | | | Octet 1 | + +M = 0 If the MS implements both looping the received data back to the transmitter and internally generating the pseudorandom data, then if this bit is set to '0' the MS shall itself generate the pseudorandom data. Otherwise the MS may ignore this bit. + +M = 1 If the MS implements both looping the received data back to the transmitter and internally generating the pseudorandom data, then if this bit is set to '1' the MS shall select the loop back option. Otherwise the MS may ignore this bit. + +Downlink Timeslot Offset -field shall be coded as binary representation of the timeslot number as follows: + +000 = TN0 + +001 = TN1 + 010 = TN2 + 011 = TN3 + 100 = TN4 + 101 = TN5 + 110 = TN6 + 111 = TN7 + +## 8.14 EGPRS\_START\_RADIO\_BLOCK\_LOOPBACK\_CMD + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | +| Mode Flag | | M | V | 1 | + +where message type is: + +| | | | | | | | | | +|---|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | | +| | | | | | | | | Octet 1 | + +Mode Flag is: + +| | | | | | | | | | +|-------|---|---|---|--------------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | 0 | 0 | Downlink Timeslot Offset | | | | M | +| Spare | | | | | | | | Octet 1 | + +Downlink Timeslot Offset -field shall be coded as binary representation of the timeslot number as follows: + +000 = TN0 + 001 = TN1 + 010 = TN2 + 011 = TN3 + 100 = TN4 + 101 = TN5 + 110 = TN6 + 111 = TN7 + +M = 0 The MS loops back blocks on the uplink using either GMSK or 8-PSK modulation following the detected received modulation. + +M = 1 The MS loops back blocks on the uplink using GMSK modulation only. + +Mobile stations capable of uplink 8PSK may ignore the contents of the M bit. + +## 8.15 RESET MS POSITIONING STORED INFORMATION + +This message is only sent in the direction SS to MS. + +| Information Element | Reference | Presence | Format | Length | +|---------------------------|----------------|----------|--------|--------| +| Protocol discriminator | 3GPP TS 24.007 | M | V | ½ | +| Skip indicator | 3GPP TS 24.007 | M | V | ½ | +| Message type | | M | V | 1 | +| MS Positioning Technology | | M | V | 1 | + +where message type is: + +| | | | | | | | | | +|---|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | Octet 1 | + +where MS Positioning Technology is a single octet IE: + +| | | | | | | | | | +|---------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit no. | +| MS Positioning Technology | | | | | | | | octet 1 | + +MS Positioning Technology value + +Bits + +**8 7 6 5 4 3 2 1** + +0 0 0 0 0 0 0 0    AGPS + +0 0 0 0 0 0 0 1    AGNSS + +All other cause values are reserved for future use + +# 9 Electrical Man Machine Interface (EMMI) + +## 9.1 Use of the EMMI + +Conformity tests of mobile stations are made using the system simulator specified in Annex 4. + +Test signals are sent on the Um interface, and actions of the MS are registered. The Electrical Man Machine Interface (EMMI) is a half duplex communication link between the SS and the MS by which it is possible to automatically register the status, indications and performance of the MS. + +It is also possible to simulate actions normally made by the user on the keyboard of the MS. + +## 9.2 Formal aspects + +- i) The EMMI is optional for the ME. +- ii) The EMMI is mandatory for the SS. +- iii) If the EMMI is to be used in conformance testing of an MS, it shall be possible to connect the SS to a connector on the MS, or to an adapter connected to the same MS. If an adapter is to be used, it shall be provided by the manufacturer. +- iv) If the MS fulfils the requirements performed with the use of an EMMI, the MS is regarded as having passed that test. +- v) If the MS is rejected in a test performed with EMMI, the test shall be repeated on the same mobile with the device carrying the EMMI to the MS removed. The MS shall be regarded as fulfilling the requirements, if it then passes the test. +- vi) When using the EMMI, the MS does not necessarily conform to the RF requirements. Therefore, tests concerning Rx and Tx parameters on MS with integral antenna and cabinet radiation tests for all types of MS will never be performed with the use of the EMMI. + +## 9.3 Layered structure of the interface + +The definition of the EMMI is divided into three different layers. On layer 1 the use of a 25-pole socket with standard electrical characteristics for serial communication is defined. On layer 2, an extremely simple frame oriented protocol is defined. On layer 3, messages for control and verification of functions and indications are defined. Each layer is defined independently of surrounding layers, and is therefore easy to replace. + +The EMMI protocol structure takes into account that the SS only sends and receives layer 3 frames when the corresponding step within a test case is to be performed. + +## 9.4 Terminology + +| | | +|---------|----------------------------------------------------------| +| EMMI | Electrical Man Machine Interface | +| MI | Message Identifier | +| ME | Mobile Equipment | +| MS | Mobile Station | +| SS | System Simulator | +| Frame | Used on layer 2 to transfer messages to and from layer 3 | +| Message | Information on layer 3 | + +## 9.5 Description of the EMMI + +### 9.5.1 EMMI, Layer 1 + +#### 9.5.1.1 Mechanical and electrical characteristics + +If implemented, the EMMI interface shall use the same connector as the Digital Audio Interface (DAI), described in sub-clause 10.3. + +The pin assignments for the EMMI shall be as follows: + +| Pin | Function | Source | +|-----|--------------------|--------| +| 2 | Transmitted data | SS | +| 3 | Received data | MS | +| 7 | EMMI signal ground | | + +The electrical characteristics of the interface shall be as given in sub-clause 10.3.2. + +#### 9.5.1.2 Transmission and reception characteristics + +The EMMI uses asynchronous serial data transmission with 1 start bit (S), 8 data bits (D1 to D8), no parity and 1 stop bit (E). + +**Table 3: Use of start and stop bits** + +| | | | | | | | | | | +|---|----|----|----|----|----|----|----|----|---| +| S | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | E | +|---|----|----|----|----|----|----|----|----|---| + +The conditions on start and stop characters are defined in REC CCITT V.1. + +The transmission rates are: 600, 1200, 2400, 4800, 9600 bits per second. The ME shall support at least one of these speeds. + +The SS will adapt its rate (manually or by MMI) to this ME rate. + +### 9.5.2 EMMI, layer 2 + +#### 9.5.2.1 General structure + +On layer 2, frames are used to carry data from higher layers. Frames consist of one or several octets. One frame with variable length is used to carry data from higher layers, and four other frames with the length of one character is used to control the flow of frames. + +#### 9.5.2.2 Control frames + +Special frames have been assigned to control the flow of frames on layer 2. They are only one octet long. + +**Table 4: Characters for flow control** + +| Abbr. | Meaning | Dec.value | Bit pattern | +|-------|---------------------|-----------|-------------| +| ACK | Acknowledge | 06 | 0000 0110 | +| NAK | Not Acknowledge | 21 | 0001 0101 | +| XON | Resume sending data | 17 | 0001 0001 | +| XOF | Stop sending data | 19 | 0001 0011 | + +#### 9.5.2.3 Frame structure + +Two octets, called characters, indicate start and stop of I-frames. + +**Table 5: Start and stop characters** + +| Abbr. | Meaning | Dec.value | Bit pattern | +|-------|---------------|-----------|-------------| +| STX | Start of data | 02 | 0000 0010 | +| ETX | End of data | 03 | 0000 0011 | + +Information from higher layers are transferred in I-frames with the following structure. + +**Table 6: Information structure in I-frames** + +| Field name | No of octet | Value | Start at octet no | Note | +|------------|-------------|-----------------|-------------------|------| +| Start | 1 | Character STX | 1 | - | +| Length | 1 | Length of data | 2 | a1) | +| Data | 0-255 | Content of data | 3 | a2) | +| Check | 1 | Error detection | Length+2 | a3) | +| End | 1 | Character ETX | Length+3 | | + +NOTE a1) Length: The total number of data octets in the data field of the frame is calculated. The value shall be in the range of (0..255 decimal). The corresponding binary value is put into the length field. + +NOTE a2) Data: Data to and from higher layers are in the form of octets (groups of 8 digital bits). + +NOTE a3) Check: Longitudinal checksum is created by exclusive OR on all characters starting with the Start field and ending with the last octet before the Check field. The value, one octet, is mapped into the Check field. + +#### 9.5.2.4 Flow of I-frames on layer 2 + +##### 9.5.2.4.1 Transmission of frames + +A multiple frame starts with the first octet being the character STX and stops with the last octet with content ETX. The time between the start bits of two consecutive octets shall not be longer than T22. + +![Diagram showing the time interval T22 between the start bits of two consecutive octets, labeled Octet n and octet n + 1.](ca1709650afeccbebb6eb9473796e5f5_img.jpg) + +The diagram shows two rectangular boxes representing octets. The first box is labeled "Octet n" and the second box is labeled "octet n + 1". A horizontal dashed line with arrows at both ends spans the gap between the start of the first box and the start of the second box, and is labeled "T22". + +Diagram showing the time interval T22 between the start bits of two consecutive octets, labeled Octet n and octet n + 1. + +The time between two frames is measured from the start bit of the last octet of the nth frame to the start bit of the first octet of the n+1st frame. The time between two consecutive frames shall not be less than T23. + +![Diagram showing the time interval T23 between the end of one frame and the start of the next frame.](8093331dcf2cec58ddacf15bc3622b2e_img.jpg) + +The diagram shows two frames, "Frame n" and "frame n+1". "Frame n" consists of a box containing "STX" and another box containing "ETX". "frame n+1" also consists of a box containing "STX" and another box containing "ETX". A horizontal dashed line with arrows at both ends spans the gap between the end of "Frame n" (the "ETX" box) and the start of "frame n+1" (the "STX" box), and is labeled "T23". + +Diagram showing the time interval T23 between the end of one frame and the start of the next frame. + +##### 9.5.2.4.2 Reception of frames + +Start of a frame is defined as (more than T22\*2 since previous reception of octet) AND (reception of STX). + +End of a frame is defined as (reception of ETX in octet number (length+2)) OR (more than T22\*2 since last reception of octet). + +##### 9.5.2.4.3 Use of ACK and NAK on receiving side + +ACK is used by the MS to acknowledge a frame on receiving side if all the following conditions are fulfilled. Otherwise NAK is used. + +- 1) The content of Start field is STX. +- 2) The content of Check field corresponds to the exclusive OR sum of previous octets in the frame. +- 3) The content of the last octet is ETX. + +NAK is used by the SS to request retransmission of a frame. Otherwise ACK is used. + +NOTE: NAK shall not be used for layer 3 errors, if the layer 2 frame is correct. If the meaning of a layer 3 message is undefined or not performable, then the problem is solved with layer 3 messages. + +##### 9.5.2.4.4 Use of XON and XOF + +XON and XOF are used for flow control of layer 2. + +XOF is sent if the unit (MS or SS) due to internal processing is not capable of receiving a following frame when a frame is being received. + +XON is sent if XOF has been sent previously, but the reason for that XOF-transmission no longer exists. + +##### 9.5.2.4.5 Parameters on layer 2 + +**Table 7: Timer values on layer 2** + +| Bit rate | Value of T22 | Value of T23 | +|----------|--------------|--------------| +| 600 | 25.0 ms | 58.3 ms | +| 1200 | 12.5 ms | 29.2 ms | +| 2400 | 6.3 ms | 14.6 ms | +| 4800 | 3.1 ms | 7.3 ms | +| 9600 | 1.6 ms | 3.6 ms | + +### 9.5.3 EMMI, layer 3 + +#### 9.5.3.1 Message structure + +Messages are used on layer 3. They are defined by Message Identifiers (MI) in the range of (0..255). The message identifier is always the first, and often the only, octet of the message. + +**Table 8: Use of message identifiers** + +| MI | Use | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0-49 | Not used. | +| 50-179 | General messages. All undefined values reserved for further evolution of the EMMI. | +| 180-209 | ME-type dependent blocks, may be used by the SS as a sender or receiver, if so requested by the manufacturer. Undefined values available for the manufacturer. | +| 210-239 | ME-type dependent blocks, never to be used by the SS in conformance testing. Undefined values available for the manufacturer. | +| 240-255 | Reserved for L3 error handling. All undefined values reserved for further evolution of the EMMI. | + +NOTE 1: Layer 2 is transparent, but to avoid unnecessary interference from layer 3, MI with the same value as control frames on layer 2 are not used. + +Most of the messages, especially in the direction SS - MS contain only one octet, the message indicator. Some of the messages, especially in the direction MS - SS are quite long. + +NOTE 2: If the interface is limited only to the minimum required for automatic conformity testing with the electrical man machine interface, then the included L3 messages should be RQTI, KEYS, BEL1, BEL0, HOK1, HOK0, BCAP and RSTI. + +**Table 9: Block types** + +| MI | | | Source | | +|-------|-------|-------------------------------------|--------|----| +| Value | Abbr. | Meaning | MS | SS | +| 051 | VOL1 | Increase volume (***) | | X | +| 052 | VOL0 | Decrease volume (***) | | X | +| 053 | RQTS | Request for table, status | | X | +| 054 | RQTI | Request for table, indication | | X | +| 055 | RQPL | Request for power level | | X | +| 056 | RQBE | Request for bell status | | X | +| 057 | RQSM | Request for short message | | X | +| 058 | KEYS | Perform keystroke sequence | | X | +| 060 | BEL1 | Indication user alert on | X | | +| 061 | BEL0 | Indication user alert off | X | | +| 064 | HOK1 | Hook on | | X | +| 065 | HOK0 | Hook off | | X | +| 070 | BCAP | Selection of bearer capability | | X | +| 080 | STPO | Set power level | | X | +| 091 | RSTS | Response table, status | X | | +| 092 | RSTI | Response table, indication | X | | +| 093 | RSPO | Response, power level | X | | +| 101 | RXSM | Received short message | X | | +| 102 | RXSN | No short message received | X | | +| 240 | ER00 | Internal malfunction detected | X | | +| 241 | ER01 | L3 message not recognized | X | X | +| 242 | ER02 | L3 message not performable | X | | +| 255 | RESE | Perform hardware and software reset | | X | + +NOTE 3: Functioning of this should be verified, as the volume control in the ME might be of another type (non-incremental). + +#### 9.5.3.2 Definition of messages + +Messages are defined in the order of the value of the message identifier. + +051 VOL1 Increase volume + +052 VOL0 Decrease volume + +Increase/decrease volume in the loudspeaker by one step. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +053 RQTS Request for table, status + +054 RQTI Request for table, indication + +055 RQPL Request for power level + +On receiving a request message RQxy, the corresponding table RSxy shall be sent. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +##### 056 RQBE Request for bell status + +On receiving a request message RQBE, the internal user alert status (BEL1 or BEL0) shall be sent. BEL1 and BEL0 will indicate whether the ringing or alert procedure has been activated or not. (See also the definition of BEL1 and BEL0). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +##### 057 RQSM Request for short message + +In response to the RQSM request the MS shall send either the short message type using the message RXSM or, in case of no short message received, the message RXSN. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +##### 058 KEYS Perform keystroke sequence + +Perform the MS function related to the received keystroke sequence. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | +| | | | | | | | | 2 | First key | +| | | | | | | | | .... | | +| | | | | | | | | N | Key Number N-1 | + +The possible keystroke sequences are based on the basic public man machine interface as defined in 3GPP TS 22.030. There exists a minimum set of key characters. + +The codes associated with these characters are defined as follows: + +| Key | Code (decimal) | +|-----------------|---------------------------| +| # | 35 | +| * | 42 | +| + | 43 | +| 0 | 48 | +| 1 | 49 | +| 2 | 50 | +| 3 | 51 | +| 4 | 52 | +| 5 | 53 | +| 6 | 54 | +| 7 | 55 | +| 8 | 56 | +| 9 | 57 | +| END (function) | 18 | +| SEND (function) | 20 | +| 060 BEL1 | Indication user alert on | +| 061 BEL0 | Indication user alert off | + +Indication user alert shall indicate, on request of the SS, the internal status of the alert or ringing procedure. For this purpose, the SS shall send the RQBE (request for bell status) message to the MS. + +BEL1 shall indicate that the alert procedure is active. + +BEL0 shall indicate that the alert procedure is not active. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +064 HOK1 Hook on + +065 HOK0 Hook off + +Control of the hook. The hook on/off command shall action the normal procedure associated with physically lifting the handset and replacing it whatever that maybe. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +070 BCAP Selection of bearer capability + +The EMMI BCAP message shall change the default bearer capability on all future calls made via the EMMI "perform keystroke sequence" message. The new default bearer capability shall be in effect until the ME is switched off or until the ME receives another EMMI BCAP message. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|---------------------------------| +| | | | | | | | | 1 | Message identifier | +| | | | | | | | | 2 | Bearer capability
(see note) | + +NOTE: The field "bearer capability" in the BCAP message is mandatory and is coded bit for bit exactly as the "bearer capability" information element as described in 3GPP TS 44.018, beginning with octet 2 (length of the bearer capability contents). Because the "bearer capability" is mandatory, the first byte of the field shall be the length of the bearer capability content and not the bearer capability information element identifier. + +080 STPO Set power level + +Used to control the Tx power level of the ME. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|---------------------------| +| | | | | | | | | 1 | Message identifier | +| | | | | | | | | 2 | Power level
(see note) | + +NOTE: The power level is defined as the 2nd octet of the power command information element in 3GPP TS 44.018. + +091 RSTS Response table, status + +Response table status is sent as an answer to the corresponding request. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|----|----|---|----|---|---|-------|----------------------------| +| | | | | | | | | 1 | Message identifier | +| | | F1 | | | F2 | | | 2 | Statis fiels
(see note) | +| | | | F3 | | | | | | | + +NOTE: F1 +0 0 0 0 Spare +F2 (1=yes, 0=no) +Bit 4 L2 link on SACCH established +Bit 3 Speech connection on TCH establ +Bit 2 Listening to BCCH +Bit 1 SDCCH established +F3 +Bit 8 Frequency hopping (yes/no) +Bit 7-1 ARFCN of BCCH of serving cell + +##### 092 RSTI Response table, indication + +Response table indication send as an answer to the corresponding request. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|-------------------------------------------------------------------------------------------|---|---|----|---|---|---|----|-------|--------------------------------| +| | | | | | | | | 1 | Message identifier | +| | | | F1 | | | | F2 | 2 | Indication field
(see note) | +| NOTE: F1
0000000 Spare

F2 (yes=1, no=0)
Bit 1 Service indication On (yes/no) | | | | | | | | | | + +##### 093 RSPO Response, power level + +Response power level is sent as an answer to the corresponding request. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|--------------------------------------------------------------------------------------------------------------------------|---|----|---|---|----|---|---|-------|---------------------------| +| | | | | | | | | 1 | Message identifier | +| | | F1 | | | F2 | | | 2 | Power Level
(see note) | +| NOTE: The power level is defined as the 2 nd octet of the power command information element in 3GPP TS 44.018 | | | | | | | | | | + +##### 101 RXSM Received short message + +The message RXSM has to be sent by the MS in response to the RQSM request if a short message has been received. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------|--------------------------------| +| | | | | | | | | 1 | Message identifier | +| | | | | | | | | 2 | SM field octet 1
(see note) | +| | | | | | | | | .... | | +| | | | | | | | | N | SM field octet N-1 | +| NOTE: The SM field is defined as the content of the data field short message storage defined in 3GPP TS 51.011, excluding byte 1, as follows:
1 byte NULL value
12 bytes TP Originating Address
12 bytes TS Service Centre Address
1 byte TP Protocol Identifier
1 byte TP Data Coding Scheme
7 bytes TP Service Centre Time Stamp
1 byte TP User Data Length
up to 140 bytes TP User Data.
If the length of the address for TP and for TS service centre is less than 12 bytes, the remaining bytes are filled with null values. | | | | | | | | | | + +##### 102 RXSN No short message received + +The message RXSN has to be sent by the MS in response to the RQSM request if no short message has been received. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +##### 240 ER00 Internal malfunction detected + +Used to indicate to the SS that the MS has discovered an internal error. This error message is to be handled in the same manner as the layer 3 error messages (only to be sent to the SS in response to a Layer 3 message received at the MS). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---------------------------------------------------------------------|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | +| | | | | | | | | 2 | Error indication | +| NOTE: The error indicator is defined by the manufacturer of the ME. | | | | | | | | | | + +##### 241 ER01 L3 message not recognized + +Used by the receiver to indicate to the sender that the message was correctly received, but ignored due to the fact that it was not understandable (e.g. a KEYS message with one or many values which are not part of the standard set of keys for the MSE). The message to the MS implies a request for re-sending the latest message sent. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +##### 242 ER02 L3 message not performable + +Used by the receiver to indicate to the sender that the message was understood, but not performable due to intentional lack of functionality in the MS (e.g. as answer to a CALL message containing a type of service which the MS is not able to use) or to a message requesting a change to a state already existent. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +##### 255 RESE Perform HW and SW reset + +The MS shall perform a total reset. The MS shall behave as if it has been switched "off" and "on". + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---|---|---|---|---|---|---|---|-------|--------------------| +| | | | | | | | | 1 | Message identifier | + +# 10 Digital audio interface + +## 10.1 General + +A special interface is required in order to perform the bit exact test of the speech coder/decoder and to test the SLR/RLR performance of the analogue and acoustic devices. It shall be possible to insert and extract speech data in both the transmit and receive directions. The interruption of the normal speech data paths can be commanded either by a layer 3 message over the air interface or by special control lines in the test interface. The MS need react to only one of these command methods. The manufacturer shall state which method is to be used. + +## 10.2 Formal aspects + +It shall be possible to connect the SS to the ME or to an adapter connected to the ME. If an adapter is to be used, it shall be provided by the manufacturer of the ME. + +When using the DAI, the MS does not necessarily conform to all RF requirements. + +When the DAI is connected the MS shall be able to correctly send and receive on a TCH and associated channels under ideal radio conditions. + +NOTE: Prior to tests of the speech coder, other functional entities involved in the tests, such as the channel codec or RF units must have been verified successfully. + +## 10.3 Hardware aspect of the interface + +The data exchanged on the interface are 13 bit linear PCM at 8000 samples per second, which, in order to keep the pin count low, are transferred on a duplex set of serial lines at 104 kbit/s. + +One additional line resets the speech transcoder and the speech A/D and D/A functions. Two lines control the data flow direction and working mode of the interface, one mode being normal operation of the MS. These lines are controlled by the SS. Another line, controlled by the MS, clocks the data as required or available. + +This is described in detail below. + +### 10.3.1 Mechanical characteristics of the interface + +The interface shall use a 25-pin DSUB socket, detailed in the ISO 2110 document. The ME shall use a female part. + +The manufacturer may provide this interface on an external test "adapter". + +The pin assignment of the connector shall be as follows: + +| Pin | Use | Function | Source | +|-------|----------|----------------------|--------| +| 1 | | Chassis ground | ME | +| 2-3 | EMMI | Signals | | +| 4-6 | Not used | | | +| 7 | EMMI | Signal ground | | +| 8-10 | Not used | | | +| 11 | DAI | Test control 1 | SS | +| 12 | DAI | Signal ground | | +| 13 | DAI | Test control 2 | SS | +| 14-21 | Not used | | | +| 22 | DAI | Reset | SS | +| 23 | DAI | Data | ME | +| 24 | DAI | Data clock (104 kHz) | ME | +| 25 | DAI | Data | SS | + +NOTE: The EMMI interface is optional and is described in sub-clause 9. + +### 10.3.2 Electrical characteristics of the interface + +The state of a signal pin is defined by the voltage (V) between the pin and its associated ground as follows: + +| Logical state | Voltage v | +|----------------------|---------------------------------------| +| 0 or "LOW" or "ON" | $0 \text{ V} < v < +0,8 \text{ V}$ | +| 1 or "HIGH" or "OFF" | $+3,5 \text{ V} < v < +5 \text{ V}$ | +| undefined | $+0,8 \text{ V} < v < +3,5 \text{ V}$ | +| forbidden | $v < 0 \text{ V}, v > +5 \text{ V}$ | + +### 10.3.3 Timing characteristics of the interface + +The following timing applies: + +| Parameter | Value | +|-------------------------|--------------------| +| Clock frequency | 104 kHz +/- 20 ppm | +| Duty cycle | 40 to 60 % | +| Clock rising edge time | < 1 microsecond | +| Clock falling edge time | < 1 microsecond | +| Reset pulse duration | >= 4 millisecond | + +![Timing characteristics diagram showing a clock signal waveform. The period is 9.6 µs. The high time is 4.8 µs +/- 1 µs. The falling edge and rising edge are both less than 1 µs. The signal levels are 90%, 50%, and 10%.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +The diagram illustrates the timing characteristics of a clock signal. It shows a periodic square wave with a period of 9.6 µs. The high time (duration of the logical state 1 or high) is 4.8 µs with a tolerance of +/- 1 µs. The falling edge and rising edge transition times are both less than 1 µs. The signal levels are indicated at 90%, 50% (50% level), and 10%. + +Timing characteristics diagram showing a clock signal waveform. The period is 9.6 µs. The high time is 4.8 µs +/- 1 µs. The falling edge and rising edge are both less than 1 µs. The signal levels are 90%, 50%, and 10%. + +Figure 10.3.3: Timing characteristics + +Data shall be stable during the period between 3 microseconds before and 1 microsecond after the rising edge of the clock (50% level). + +## 10.4 Logical interface + +The reset signal is active low. + +The data consists of 13 bit words in two's complement format, with the most significant bit transmitted first. + +Data are read in by the MS or SS at the rising edge and are output by the SS or MS at the falling edge of the clock, as defined in Figure 2. + +The clock signal is high when inactive. + +The two test control lines determine the routing of the speech data (DAI or internal, i.e. normal mode) and which device is being tested (speech transcoder/DTX functions or A/D & D/A) as follows: + +| Test control line | | Function | +|-------------------|------|---------------------------------------------------| +| 1 | 2 | | +| Low | Low | Normal operation | +| Low | High | Test of speech decoder / DTX functions (downlink) | +| High | Low | Test of speech encoder / DTX functions (uplink) | +| High | High | Test of acoustic devices and A/D & D/A | + +The same test setup may be achieved by the layer 3 TEST\_INTERFACE message (see 7 and 8.7). + +## 10.5 Functionality of the DAI + +To initiate a test, the SS shall apply the appropriate test control signals or send the appropriate layer 3 messages and then, more than 1 second later, apply a reset pulse. + +Upon release of the reset pulse, the MS subsequently starts the test by issuing clock pulses when data are required or are ready. + +When testing uplink speech transcoding or DTX functions, the first falling clock edge shall request from the SS the first bit of the speech samples to be encoded, the transmission of which shall start at the next earliest possible interleaved block TDMA frame (as defined in 3GPP TS 45.002) after the release of the reset pulse. + +When testing downlink speech transcoding or DTX functions, the first falling clock edge shall output to the SS the first bit of the speech samples decoded from the first interleaved block TDMA frames, the reception of which is completed subsequently to the release of the reset pulse. + +The MS speech transcoders shall be reset by the end of the reset pulse, whenever it occurs, whilst the DAI is in one of the active states (Test of speech decoder / DTX functions (downlink), Test of speech encoder / DTX functions (uplink), Test of acoustic devices and A/D and D/A). + +![Figure 10.5: DAI Timing diagram showing four signal lines over time. The 'Reset' line starts high, goes low for a short pulse, and then returns high. The 'Clock' line is a periodic square wave with arrows indicating rising and falling edges. The 'Data SS to MS' line shows a sequence of data blocks, with the first labeled 'Undefined' and the second labeled 'MSB'. The 'Data MS to SS' line shows a similar sequence of data blocks, also with the first labeled 'Undefined' and the second labeled 'MSB'.](a85105fd544c64ef624aa45c72378647_img.jpg) + +Figure 10.5: DAI Timing diagram showing four signal lines over time. The 'Reset' line starts high, goes low for a short pulse, and then returns high. The 'Clock' line is a periodic square wave with arrows indicating rising and falling edges. The 'Data SS to MS' line shows a sequence of data blocks, with the first labeled 'Undefined' and the second labeled 'MSB'. The 'Data MS to SS' line shows a similar sequence of data blocks, also with the first labeled 'Undefined' and the second labeled 'MSB'. + +Figure 10.5: DAI Timing + +# 11 SIM/ME test interface + +## 11.1 General + +A special interface is required in order to perform the tests of the SIM/ME interface. + +## 11.2 Formal aspects + +It shall be possible to connect the SIM simulator to the ME. If an adapter is to be used, it shall be provided by the manufacturer of the ME. + +When using the SIM simulator, the ME does not necessarily conform to all RF requirements. + +When the SIM simulator is connected the ME shall be able to correctly send and receive on a TCH and associated channels under ideal radio conditions (according to GC3 of Annex 1). + +## 11.3 Hardware and logical aspects of the interface + +The signals on this interface are specified in 3GPP TS 51.011. + +## 11.4 Mechanical characteristics of the interface + +The interface of the SIM-simulator offers two connection types : + +- i) a paddle which is inserted into the ME under test in place of an IC card SIM, and connects with wires to the measuring equipment. The dimensions of the full size paddle are shown in Figure 11.4a. The length of the plug in SIM paddle shown in Figure 11.4b shall not exceed 12cm. +- ii) a connector with leads of length 12cm, terminated directly at the contacting elements inside the ME under test. + +For ME where the paddle cannot be inserted due to constraints imposed by the ME design, then the ME manufacturer shall, for the purpose of testing the SIM/ME interface only, provide the ME with the connector of type ii) and the leads attached directly to the contacting elements. This connector with the flying leads shall be delivered by the test house. + +![Technical drawing of a full size paddle with dimensions.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +Technical drawing of a full size paddle showing dimensions and layout. The drawing includes a front view and a side view. + +**Front View Dimensions and Labels:** + +- Width: 52.98 mm +- Top Margin: 0.5 mm +- Side Margin: 0.5 mm +- Top Section Height: 53.88 mm +- Bottom Section Height: 88.0 mm +- Top Corner Radius: Radius 2.41 mm +- Bottom Corner Radius: Radius 3.12 mm + +**Side View Dimensions and Labels:** + +- Top Label: (TOP) +- Upper Thickness: 4.82 mm +- Lower Thickness: 3.43 mm +- Main Body Thickness: Thickness 0.8 mm + +Technical drawing of a full size paddle with dimensions. + +Figure 11.4a: Dimensions of full size paddle + +![Figure 11.4b: Dimensions of plug in SIM adapter. The figure shows four diagrams of SIM adapter plug shapes. Each diagram shows a plug with a set of contacts (represented by black rectangles) and a label 'TyI' or 'TyF' connected by a dashed line. The first diagram shows a plug with two vertical columns of three contacts each, labeled 'TyI'. The second diagram shows a plug with two horizontal rows of three contacts each, labeled 'TyI'. The third diagram shows a plug with two horizontal rows of four contacts each, labeled 'TyI'. The fourth diagram shows a plug with two vertical columns of three contacts each, labeled 'TyF'.](4b00764d3c160ac6ade7502d9faeb615_img.jpg) + +Figure 11.4b: Dimensions of plug in SIM adapter. The figure shows four diagrams of SIM adapter plug shapes. Each diagram shows a plug with a set of contacts (represented by black rectangles) and a label 'TyI' or 'TyF' connected by a dashed line. The first diagram shows a plug with two vertical columns of three contacts each, labeled 'TyI'. The second diagram shows a plug with two horizontal rows of three contacts each, labeled 'TyI'. The third diagram shows a plug with two horizontal rows of four contacts each, labeled 'TyI'. The fourth diagram shows a plug with two vertical columns of three contacts each, labeled 'TyF'. + +Figure 11.4b Dimensions of plug in SIM adapter + +# 12 Reset MS Positioning Stored Information + +## 12.1 General + +The SS uses the reset MS positioning stored information procedure to command the MS to reset the already acquired MS POSITIONING information in preparation for subsequent test procedures. + +![Figure 12: RESET MS POSITIONING STORED INFORMATION. This is a sequence diagram showing the interaction between a Mobile Station (MS) and a Station (SS). The MS is on the left and the SS is on the right. A horizontal arrow points from the SS to the MS, labeled 'RESET MS POSITIONING STORED INFORMATION'.](a97518a839da75f8379c578562b01bc2_img.jpg) + +Figure 12: RESET MS POSITIONING STORED INFORMATION. This is a sequence diagram showing the interaction between a Mobile Station (MS) and a Station (SS). The MS is on the left and the SS is on the right. A horizontal arrow points from the SS to the MS, labeled 'RESET MS POSITIONING STORED INFORMATION'. + +Figure 12: RESET MS POSITIONING STORED INFORMATION + +## 12.2 Procedure + +The SS requests the MS to reset the stored MS positioning information mode by transmitting a RESET MS POSITIONING STORED INFORMATION message. + +When MS receives RESET MS POSITIONING STORED INFORMATION message then the MS shall: + +- if the IE "MS Positioning Technology" has the value 'AGPS': discard any stored GPS reference time, reference position, and any other aiding data obtained or derived previously (e.g. expected ranges and Doppler). +- if the IE "MS Positioning Technology" has the value 'AGNSS': + - discard any stored GPS and GANSS reference time, reference position, and any other aiding data obtained or derived previously (e.g. expected ranges and Doppler); + - temporarily disable any sensor data (if applicable) that can aid the positioning for the duration of the subsequent positioning procedure. +- otherwise: ignore the message. + +# --- 13 GAN security certificate + +## 13.1 General + +When an MS uses the Generic Access Network, the use of IKEv2 with certificates for authentication is mandated. In order to perform testing, the SS shall use a SEGW certificate detailed in clause 80 of [4], and the MS must establish a trusted relationship with the SS using a CA root certificate. + +## 13.2 Formal aspects + +Whilst a test SIM is present the MS shall establish a trusted relationship with an SS utilising the test CA root certificate detailed in clause 80 of [4]. + +Whilst a test SIM is present, the MS may choose to establish a trust relationship with other CA root certificates. + +When a test SIM is not present the MS shall never trust the test CA root certificate detailed in [4]. + +# --- Annex A (informative): Change History + +| Date / Meeting | Tdoc | CR # | Rev | Remarks | New version | +|----------------|-----------|------|-----|-----------------------------------------|-------------| +| January 2016 | - | - | - | Version 13.0.0. based on version 12.0.0 | 13.0.0 | +| GP-70 | GP-160316 | 0024 | | Introduction to EC-GSM-IoT | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | RP-73 | RP-161392 | 0025 | 1 | F | Miscellaneous EC-GSM-IoT Changes | 13.2.0 | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44018/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg b/marked/Rel-16/44_series/44018/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb09328e33d1dd98b3cce787a17a1175dd9957e7 --- /dev/null +++ b/marked/Rel-16/44_series/44018/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7832e3c0dbe3ebb72306a0554321c9fca72ab016726f5df677bedbff947b8a0 +size 16148 diff --git a/marked/Rel-16/44_series/44018/06291c5328a7a4335d41a48850a3a207_img.jpg b/marked/Rel-16/44_series/44018/06291c5328a7a4335d41a48850a3a207_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85c8cdad65287f8daad2b1b2d75cff62a0cf6749 --- /dev/null +++ b/marked/Rel-16/44_series/44018/06291c5328a7a4335d41a48850a3a207_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79cfc41bf7fab7855caeb0d5b867eb188a954986712499090ed4d1846385e3fc +size 16803 diff --git a/marked/Rel-16/44_series/44018/08282b490d242bfa2043a339d2b9cdcc_img.jpg b/marked/Rel-16/44_series/44018/08282b490d242bfa2043a339d2b9cdcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48f58de668dd06638b4a4f7329e9edfb1bd03c20 --- /dev/null +++ b/marked/Rel-16/44_series/44018/08282b490d242bfa2043a339d2b9cdcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a1a41d7860dde061f1bbb78994b381a0e7780a40d05f4df09e3d4cef8559447 +size 50808 diff --git a/marked/Rel-16/44_series/44018/09b293b3a4cad7c80f5a38a935442fcf_img.jpg b/marked/Rel-16/44_series/44018/09b293b3a4cad7c80f5a38a935442fcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..240eeea6a30a21162d8892d3e3bd3a19a748596d --- /dev/null +++ b/marked/Rel-16/44_series/44018/09b293b3a4cad7c80f5a38a935442fcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c30af666fcdc496a5402e10d7e7c6672ab3440b4d15c34520cb4edd66704eb03 +size 26746 diff --git a/marked/Rel-16/44_series/44018/0ebd24d723abddc0387f7c549449c8e3_img.jpg b/marked/Rel-16/44_series/44018/0ebd24d723abddc0387f7c549449c8e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c71fd05485084f5a4b327392a5358eae4d0e61b --- /dev/null +++ b/marked/Rel-16/44_series/44018/0ebd24d723abddc0387f7c549449c8e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2d912ded38bd3ac80331158d09d1c0fd42240a6811c35487d21c47a67cebd7f +size 24288 diff --git a/marked/Rel-16/44_series/44018/13533a09243e784566d2227cb6ac60e5_img.jpg b/marked/Rel-16/44_series/44018/13533a09243e784566d2227cb6ac60e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c08b596541e11305f096e2a5d38ec64f2525495 --- /dev/null +++ b/marked/Rel-16/44_series/44018/13533a09243e784566d2227cb6ac60e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d576e98c116b24b9bb64cae450799ac8043e79b2baae3dbc89cc54056ef1a4c +size 17554 diff --git a/marked/Rel-16/44_series/44018/1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg b/marked/Rel-16/44_series/44018/1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fead087a1ee55317164f1848948275a1a673f654 --- /dev/null +++ b/marked/Rel-16/44_series/44018/1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10f9896bd3601919f8c3bfdc2da43f6fae343313fa38e1fbb22501aaa060b94c +size 13910 diff --git a/marked/Rel-16/44_series/44018/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-16/44_series/44018/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..438d865dfccdb38037ba350842dfa73213e5f7dc --- /dev/null +++ b/marked/Rel-16/44_series/44018/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c611a788ab694c589e9feea21b2c86f6597adeef362835b9edd9e3a55bb99b24 +size 23025 diff --git a/marked/Rel-16/44_series/44018/1fd763be1b7a05b52e554f0583617642_img.jpg b/marked/Rel-16/44_series/44018/1fd763be1b7a05b52e554f0583617642_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4d0012a34a87b485ae4b5802fca82d8846c77cb --- /dev/null +++ b/marked/Rel-16/44_series/44018/1fd763be1b7a05b52e554f0583617642_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c60cef3b9f8550d0b3065db66ea6d1f2dde9c2e3c8dc031f78feb8956d8c111 +size 73413 diff --git a/marked/Rel-16/44_series/44018/208fd2da57f31de2a5ddaa409300f7f6_img.jpg b/marked/Rel-16/44_series/44018/208fd2da57f31de2a5ddaa409300f7f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f160fb0819a851265f7953a540e97ff44f1a0b7b --- /dev/null +++ b/marked/Rel-16/44_series/44018/208fd2da57f31de2a5ddaa409300f7f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bca31168ced1e131e855738326ee48871e58c50134e58ba1c04eb056850ed66 +size 14344 diff --git a/marked/Rel-16/44_series/44018/210d8cabb9882dcd63f42b38f4f2a414_img.jpg b/marked/Rel-16/44_series/44018/210d8cabb9882dcd63f42b38f4f2a414_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c91074c07aea68ddd77c9e1fcba4d870f80fdf2 --- /dev/null +++ b/marked/Rel-16/44_series/44018/210d8cabb9882dcd63f42b38f4f2a414_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b4ba65dce47ae0e345ca0a4febf0becd4744ac0d2544eec03f77ad7e7e03ce6 +size 18745 diff --git a/marked/Rel-16/44_series/44018/21df39ef27b27dec52a36c0bedc53e6b_img.jpg b/marked/Rel-16/44_series/44018/21df39ef27b27dec52a36c0bedc53e6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ff919921b09bd1b14dcf7d5b5875495b866d2c0 --- /dev/null +++ b/marked/Rel-16/44_series/44018/21df39ef27b27dec52a36c0bedc53e6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f591e0f235ed4e1111f2bd21ea7ddae382b5d2d980fd7450190ffb6c33cc9a71 +size 9398 diff --git a/marked/Rel-16/44_series/44018/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg b/marked/Rel-16/44_series/44018/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..555600412aa3c5c14d61085ac33808cfd66266a9 --- /dev/null +++ b/marked/Rel-16/44_series/44018/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26b98d3d5d4c28edb2bac2d73e16cb2d6d962cd5f547c3f85ed4aa01eaa1cc12 +size 43858 diff --git a/marked/Rel-16/44_series/44018/274c9f072648ced2fb71212d6e30fea9_img.jpg b/marked/Rel-16/44_series/44018/274c9f072648ced2fb71212d6e30fea9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b050e3454bb90bfcaef74ce913bcbc515efdc86 --- /dev/null +++ b/marked/Rel-16/44_series/44018/274c9f072648ced2fb71212d6e30fea9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94e31407c06ff439dfd97212f1a02b89751063fa02e570b219852c7f82e68537 +size 67707 diff --git a/marked/Rel-16/44_series/44018/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg b/marked/Rel-16/44_series/44018/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aef639fad5c586325df6726b0c9c37fad4ebbb0a --- /dev/null +++ b/marked/Rel-16/44_series/44018/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f06660c4f5238a420a8498c99ecdd3098f97bc6047440d2749ae2b09ffddbd68 +size 11868 diff --git a/marked/Rel-16/44_series/44018/2f903f194dbf70f3aa6c281a6f96db03_img.jpg b/marked/Rel-16/44_series/44018/2f903f194dbf70f3aa6c281a6f96db03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d0e3369760827e0037c7208869412590077ce9c --- /dev/null +++ b/marked/Rel-16/44_series/44018/2f903f194dbf70f3aa6c281a6f96db03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1364ea56c85a93497286c1fcf57bc0c73841896635a04c746fa0358e35c38b9 +size 10169 diff --git a/marked/Rel-16/44_series/44018/3295c6ffe9f6d00c3811c37d327ac844_img.jpg b/marked/Rel-16/44_series/44018/3295c6ffe9f6d00c3811c37d327ac844_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d32688576d33090b61a44dc0ab981955f0562cb --- /dev/null +++ b/marked/Rel-16/44_series/44018/3295c6ffe9f6d00c3811c37d327ac844_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1c8fd63930244ad10547ec738f56f5ea667fe8bca36449800cd79a856e1edf9 +size 24815 diff --git a/marked/Rel-16/44_series/44018/357536e18f2ad306db16dc51ab0bb30b_img.jpg b/marked/Rel-16/44_series/44018/357536e18f2ad306db16dc51ab0bb30b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2dd3ee57241d2fca65567bf3f1b4a9d664d6a7c3 --- /dev/null +++ b/marked/Rel-16/44_series/44018/357536e18f2ad306db16dc51ab0bb30b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:361ff0967d22657d80afdc219f318cbc80caf73e55ffc9fe07981bd36111cb49 +size 30405 diff --git a/marked/Rel-16/44_series/44018/39fd984f11d728164f7aae746b428037_img.jpg b/marked/Rel-16/44_series/44018/39fd984f11d728164f7aae746b428037_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dedce05a5f774094cb8b043c88397a63c24d43c --- /dev/null +++ b/marked/Rel-16/44_series/44018/39fd984f11d728164f7aae746b428037_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:850f9563718daac463d0563387e3162efed8d7023a496264bd3ecf85499ffdca +size 34568 diff --git a/marked/Rel-16/44_series/44018/3c4b75cb7b7c07754e9dc980da012b8d_img.jpg b/marked/Rel-16/44_series/44018/3c4b75cb7b7c07754e9dc980da012b8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..600aa1335fa745422fabc2446b2b5118ce29b76c --- /dev/null +++ b/marked/Rel-16/44_series/44018/3c4b75cb7b7c07754e9dc980da012b8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfe156b337d73e8b70c25608b58f57da5137b4cd4dd1dbeb4ffa953a2b295766 +size 14297 diff --git a/marked/Rel-16/44_series/44018/4346a953799e5ce8ac5a8fe4433fe26d_img.jpg b/marked/Rel-16/44_series/44018/4346a953799e5ce8ac5a8fe4433fe26d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc04f0d7dbcdc27bd667a381a4221d9a7c05abf4 --- /dev/null +++ b/marked/Rel-16/44_series/44018/4346a953799e5ce8ac5a8fe4433fe26d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80baa133abd2f1b98360bf1d6c443fa3ad4643140c321a6d093ae8e69a8e7112 +size 10173 diff --git a/marked/Rel-16/44_series/44018/437a88375397eec8390174b5426e99b0_img.jpg b/marked/Rel-16/44_series/44018/437a88375397eec8390174b5426e99b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a52933858e3fc2c830591cba52840ddfc801ad28 --- /dev/null +++ b/marked/Rel-16/44_series/44018/437a88375397eec8390174b5426e99b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a6b4942e0ec1adbb99ff807e7c72e7fe3ded7196f69d982b3debba3a091a787 +size 56716 diff --git a/marked/Rel-16/44_series/44018/45580ccf627a95d8c2bb3f03bf9fa0dd_img.jpg b/marked/Rel-16/44_series/44018/45580ccf627a95d8c2bb3f03bf9fa0dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bffecf1ab9dbe3708f19ac75b0cd2e4264dbf63 --- /dev/null +++ b/marked/Rel-16/44_series/44018/45580ccf627a95d8c2bb3f03bf9fa0dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de6c58d0a0a7d08a6730e5f52ea56b8d2d9a5e48c9dd7e20091ffd23052ea1c9 +size 21925 diff --git a/marked/Rel-16/44_series/44018/4cb497b8657c6247d4faab7691cd93f2_img.jpg b/marked/Rel-16/44_series/44018/4cb497b8657c6247d4faab7691cd93f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4dd8cdc236d1affa419c8dcaae6ae0feaf61c40 --- /dev/null +++ b/marked/Rel-16/44_series/44018/4cb497b8657c6247d4faab7691cd93f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bcd00b4ee15a724eca8969f3531fd95ee5f90ffef427b986e85d818d96342b7 +size 12236 diff --git a/marked/Rel-16/44_series/44018/516174e327ed8fcb75cb3af20f110de8_img.jpg b/marked/Rel-16/44_series/44018/516174e327ed8fcb75cb3af20f110de8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea0184caa8771a4f27df27f1b3c4c8a5eb4d867c --- /dev/null +++ b/marked/Rel-16/44_series/44018/516174e327ed8fcb75cb3af20f110de8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02bfc2686b23f1ea38c416230919c6005a33b038ed4d8231bc43eb1a83422a2a +size 33069 diff --git a/marked/Rel-16/44_series/44018/5446143e3814eda7fa1049af15fc7683_img.jpg b/marked/Rel-16/44_series/44018/5446143e3814eda7fa1049af15fc7683_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec71f6b1d4fde8c207ed9f38a017d1442accdb89 --- /dev/null +++ b/marked/Rel-16/44_series/44018/5446143e3814eda7fa1049af15fc7683_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b70f8913fe97bea2403e731baf77beea78d63065804ad1191e62858918065be +size 20344 diff --git a/marked/Rel-16/44_series/44018/59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg b/marked/Rel-16/44_series/44018/59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..000fee45442c199f54beaf0b4bcb55e9cea21361 --- /dev/null +++ b/marked/Rel-16/44_series/44018/59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87c0fd63c12d0d719328a108d42cc05ca95977066bf3ab36536eadfd24903739 +size 12068 diff --git a/marked/Rel-16/44_series/44018/5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg b/marked/Rel-16/44_series/44018/5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..465e593928b823dcd1e8ff40efe668edbe005bd0 --- /dev/null +++ b/marked/Rel-16/44_series/44018/5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c950578185c2f547c0b59af8c0836ae7ba691c20f537bcd5408746ccb5086c63 +size 29050 diff --git a/marked/Rel-16/44_series/44018/5f1417c85a44ed9672c976606bcfeba8_img.jpg b/marked/Rel-16/44_series/44018/5f1417c85a44ed9672c976606bcfeba8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9fba254f7e256ce25dcaf9dfc76c8cec8f03229 --- /dev/null +++ b/marked/Rel-16/44_series/44018/5f1417c85a44ed9672c976606bcfeba8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bf141516709bbf8e5226fe9499675557aead1cc2f88fcf572b4e37b072b2e56 +size 40929 diff --git a/marked/Rel-16/44_series/44018/69733eeb3ef32197543f66f22a431771_img.jpg b/marked/Rel-16/44_series/44018/69733eeb3ef32197543f66f22a431771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb81af4fd6c899bbdbe7004abb679becd44fd030 --- /dev/null +++ b/marked/Rel-16/44_series/44018/69733eeb3ef32197543f66f22a431771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:600823b40b38d60f928eb81c42ed09fbaa0b842de3db445235dc0b17590e9f76 +size 28806 diff --git a/marked/Rel-16/44_series/44018/6a0568674e792609ca7e6c1533614862_img.jpg b/marked/Rel-16/44_series/44018/6a0568674e792609ca7e6c1533614862_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdd648d1ce002a326045646859e27988e7fcb376 --- /dev/null +++ b/marked/Rel-16/44_series/44018/6a0568674e792609ca7e6c1533614862_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d41a9ae18d3760691b8d79a0c752201d671c315d518e3adab9aaf16f0eb7319 +size 8822 diff --git a/marked/Rel-16/44_series/44018/6d49c8b8197834dbfb3ac14809ec84f3_img.jpg b/marked/Rel-16/44_series/44018/6d49c8b8197834dbfb3ac14809ec84f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..808804b6e33f561ffabe311bab5cfb2e45826c05 --- /dev/null +++ b/marked/Rel-16/44_series/44018/6d49c8b8197834dbfb3ac14809ec84f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f785e21fee0ebac6e0cc4fe786fc9f3e9f93a2d2d8ae148d05f1fd05a987fbb +size 8119 diff --git a/marked/Rel-16/44_series/44018/6df742a7ac8e019dbf9e8ecfa4497d85_img.jpg b/marked/Rel-16/44_series/44018/6df742a7ac8e019dbf9e8ecfa4497d85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e03a50a5390008dfc958e997b428beda39e9c04 --- /dev/null +++ b/marked/Rel-16/44_series/44018/6df742a7ac8e019dbf9e8ecfa4497d85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f468eb8faf7b76a66da1e6ba5218a6dc9e3ecf7ce831b878766ed5d01909526 +size 11952 diff --git a/marked/Rel-16/44_series/44018/6f97d19f0a9f27cb869c6e1af68e6e79_img.jpg b/marked/Rel-16/44_series/44018/6f97d19f0a9f27cb869c6e1af68e6e79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21335a781fe048623225d85f7df834ee0dc3d3b0 --- /dev/null +++ b/marked/Rel-16/44_series/44018/6f97d19f0a9f27cb869c6e1af68e6e79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e7499f17baf1df2752104a4ffa265226e5c50af2ed2ef03886da0c5f4467b79 +size 14876 diff --git a/marked/Rel-16/44_series/44018/6fd4c6c23098ef713797b9e98ec299e8_img.jpg b/marked/Rel-16/44_series/44018/6fd4c6c23098ef713797b9e98ec299e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e57d3d6bf717a6f8548c129be222418483b8e85 --- /dev/null +++ b/marked/Rel-16/44_series/44018/6fd4c6c23098ef713797b9e98ec299e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bbed89cf80106ccb7fdaaaaa744a417ada6fd7a3c8c6065744ee3b6a23d134a +size 14172 diff --git a/marked/Rel-16/44_series/44018/7474a6dfb4787da442d12dcaec98fd04_img.jpg b/marked/Rel-16/44_series/44018/7474a6dfb4787da442d12dcaec98fd04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd2a281497f2fb8a0bdd2cb4602e5c83f9f49f16 --- /dev/null +++ b/marked/Rel-16/44_series/44018/7474a6dfb4787da442d12dcaec98fd04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6db5043d035289f6f76ff1ba10698443d308b99f1f32c583e81eb720c49c5ca9 +size 14659 diff --git a/marked/Rel-16/44_series/44018/77f52cfcb91105c4eb89664aa75a2834_img.jpg b/marked/Rel-16/44_series/44018/77f52cfcb91105c4eb89664aa75a2834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9def1da4cf39d85cf606b0b7d69a75911a50de84 --- /dev/null +++ b/marked/Rel-16/44_series/44018/77f52cfcb91105c4eb89664aa75a2834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbc5861440e915fbe2c8f257ef270ea7b27c8771a04b6069c05a6463591c2894 +size 10023 diff --git a/marked/Rel-16/44_series/44018/790afbbc0b2f0aea6683499c6ef46e62_img.jpg b/marked/Rel-16/44_series/44018/790afbbc0b2f0aea6683499c6ef46e62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9014aa3c77ce26c9ca41f964f1fbcba4d10f3c7c --- /dev/null +++ b/marked/Rel-16/44_series/44018/790afbbc0b2f0aea6683499c6ef46e62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd1fadbdd90090be3fcf19769b991514d3bdb5e103f2643c466513cf3d8f3f18 +size 12632 diff --git a/marked/Rel-16/44_series/44018/7e512bcb2039006080b1ad65c7a398c9_img.jpg b/marked/Rel-16/44_series/44018/7e512bcb2039006080b1ad65c7a398c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d40b79b68025b5fed4e82e3e585c0de2f09003b1 --- /dev/null +++ b/marked/Rel-16/44_series/44018/7e512bcb2039006080b1ad65c7a398c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:725dfd0271a4065bc107d36edcd155017434eda583a170cf14d9c841067cd8c7 +size 30036 diff --git a/marked/Rel-16/44_series/44018/813ef40a14c7e2a52988a63e33c2b59f_img.jpg b/marked/Rel-16/44_series/44018/813ef40a14c7e2a52988a63e33c2b59f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..983d46613856c71998c11c7445384ab8823110ee --- /dev/null +++ b/marked/Rel-16/44_series/44018/813ef40a14c7e2a52988a63e33c2b59f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a02fe342b87e6a87e9d64c14b77c96b16d0067d116aa0d72bb535ae81c9947ed +size 10055 diff --git a/marked/Rel-16/44_series/44018/828dfe8c7048066217f2199b4a1fb1a6_img.jpg b/marked/Rel-16/44_series/44018/828dfe8c7048066217f2199b4a1fb1a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04eadc7f3a687fb5e10af6656c450b08aca3db21 --- /dev/null +++ b/marked/Rel-16/44_series/44018/828dfe8c7048066217f2199b4a1fb1a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33adabe0c62736456ef396dc7826b736356b6766fa87d53cb51949ec215c9327 +size 10740 diff --git a/marked/Rel-16/44_series/44018/82ebf1d055f86cd379f5f38b8e948e2a_img.jpg b/marked/Rel-16/44_series/44018/82ebf1d055f86cd379f5f38b8e948e2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13f6062b6caaee1aead3f94e2bb723097c47a318 --- /dev/null +++ b/marked/Rel-16/44_series/44018/82ebf1d055f86cd379f5f38b8e948e2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1cc8236f7ab63fb6077e7b7b2027b64a1edea4fb5a8b403c3943494c81213e0 +size 32139 diff --git a/marked/Rel-16/44_series/44018/832570a3a00d9064e8068d0bb5def3a9_img.jpg b/marked/Rel-16/44_series/44018/832570a3a00d9064e8068d0bb5def3a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5669def1c272feb16b2a4ab47db5ac109577c35d --- /dev/null +++ b/marked/Rel-16/44_series/44018/832570a3a00d9064e8068d0bb5def3a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:204bd1542f2992c244b359567a8fafb509dcb3c07fe43225bb9a61a6a05f8001 +size 11552 diff --git a/marked/Rel-16/44_series/44018/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg b/marked/Rel-16/44_series/44018/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bac5f02394041e9e93da36d5a3940a58e7ff5c7 --- /dev/null +++ b/marked/Rel-16/44_series/44018/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f236b6d8e6536f616e7172edb5efd980b0bcdcb477c29da4bf57eeb21c5e4cc5 +size 73410 diff --git a/marked/Rel-16/44_series/44018/8bdf315853992d21f389da554f3a8215_img.jpg b/marked/Rel-16/44_series/44018/8bdf315853992d21f389da554f3a8215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..160a86d7ac025347418b0b2f4043672efb8b3aba --- /dev/null +++ b/marked/Rel-16/44_series/44018/8bdf315853992d21f389da554f3a8215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d65586fb66788c987bdcc395c676d221d2e4909dc37814f975ecd23168c2d4ed +size 76672 diff --git a/marked/Rel-16/44_series/44018/8d6b56ea28d70ce527efde127103e045_img.jpg b/marked/Rel-16/44_series/44018/8d6b56ea28d70ce527efde127103e045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70599c87a5e1de1ad3548bf3b4d68ead05ddecef --- /dev/null +++ b/marked/Rel-16/44_series/44018/8d6b56ea28d70ce527efde127103e045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af63c51ca3521046d14eae35e0442607153b3cd70eebd577facea769b6859129 +size 18689 diff --git a/marked/Rel-16/44_series/44018/9286389dd21b67a29ab5bfb4efc2d336_img.jpg b/marked/Rel-16/44_series/44018/9286389dd21b67a29ab5bfb4efc2d336_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea983265dd68c8b913887371ce8f4caa61f36f2d --- /dev/null +++ b/marked/Rel-16/44_series/44018/9286389dd21b67a29ab5bfb4efc2d336_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac317503c798a79e25c392eaffe22ef8171d827adcb1cef44476796183c97149 +size 12417 diff --git a/marked/Rel-16/44_series/44018/9297c2df178fdaf3c88c9600b0d0b620_img.jpg b/marked/Rel-16/44_series/44018/9297c2df178fdaf3c88c9600b0d0b620_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52da895b73b78b04afc2faa3509d9de0a7940e1e --- /dev/null +++ b/marked/Rel-16/44_series/44018/9297c2df178fdaf3c88c9600b0d0b620_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36687e9ec0b037ee76b32aa4cbb621585392a856ea593af3fc6f08a830ac7442 +size 26017 diff --git a/marked/Rel-16/44_series/44018/93bd00a00fa28558486f0664550699b1_img.jpg b/marked/Rel-16/44_series/44018/93bd00a00fa28558486f0664550699b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..318b61cdc79d8a70ac275a663fd436f1fb6dbb16 --- /dev/null +++ b/marked/Rel-16/44_series/44018/93bd00a00fa28558486f0664550699b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b0ffb9cd4c18c93eea36da79309c3dd405f9beff2ecec6702e965af6935b810 +size 117596 diff --git a/marked/Rel-16/44_series/44018/9531814db23e3f45bf99c865df5ae152_img.jpg b/marked/Rel-16/44_series/44018/9531814db23e3f45bf99c865df5ae152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b55f0be53630676775f911f5aa6baa608785a4e --- /dev/null +++ b/marked/Rel-16/44_series/44018/9531814db23e3f45bf99c865df5ae152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12733b5f756ff23ac8dda0ea03ef086def7e35ba8c1a31efee6e767b63c8f3d9 +size 8603 diff --git a/marked/Rel-16/44_series/44018/992e26bbe1f16e8a6ad84f8988034477_img.jpg b/marked/Rel-16/44_series/44018/992e26bbe1f16e8a6ad84f8988034477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8932acb3c93679cbf265cd4183e17271c4895cc --- /dev/null +++ b/marked/Rel-16/44_series/44018/992e26bbe1f16e8a6ad84f8988034477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e74153c215c5f46d912b6254f9e038571f9b43116ab04f8e561586ff0e03e21 +size 18139 diff --git a/marked/Rel-16/44_series/44018/a2b2175c4ea64d37fa63b71f79d6d48b_img.jpg b/marked/Rel-16/44_series/44018/a2b2175c4ea64d37fa63b71f79d6d48b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..587740e57cbe535003342c55f9d7790fa9e398e8 --- /dev/null +++ b/marked/Rel-16/44_series/44018/a2b2175c4ea64d37fa63b71f79d6d48b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e674c5a1e4347377ddfd4027c553f0c441738c61ca38c0e732eefb4d9f718a7 +size 9848 diff --git a/marked/Rel-16/44_series/44018/a81a31cf6a84e0a1f2f26e6fcad50e92_img.jpg b/marked/Rel-16/44_series/44018/a81a31cf6a84e0a1f2f26e6fcad50e92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b7dd7750781ff1cb33227391840344bdfb5b201 --- /dev/null +++ b/marked/Rel-16/44_series/44018/a81a31cf6a84e0a1f2f26e6fcad50e92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac8af6fed42af041bb4700ace693ed7f880ac7358c1b4fc692abe35ab912cdf5 +size 24563 diff --git a/marked/Rel-16/44_series/44018/aed979c26976e0b8dc2b00653e2667bc_img.jpg b/marked/Rel-16/44_series/44018/aed979c26976e0b8dc2b00653e2667bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..556b9ef188736a7d3f04001495fa6f7c466f8dc4 --- /dev/null +++ b/marked/Rel-16/44_series/44018/aed979c26976e0b8dc2b00653e2667bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9060f0b08a50e3762c031eb0b9d000594a4bfe39125e95b537c676d23fed3082 +size 12589 diff --git a/marked/Rel-16/44_series/44018/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg b/marked/Rel-16/44_series/44018/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f9734d4bf0db9daaab550fe62fc66462f6fed24 --- /dev/null +++ b/marked/Rel-16/44_series/44018/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5be5e20b758313750cd65d79973dc67e8ae4a39471b27cbe985e9b3412b91cb +size 25688 diff --git a/marked/Rel-16/44_series/44018/b1a5e556856e7d7d0a4a97692c70247a_img.jpg b/marked/Rel-16/44_series/44018/b1a5e556856e7d7d0a4a97692c70247a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e6cef51702b19a484cd4388f0dfecb7458c5ec0 --- /dev/null +++ b/marked/Rel-16/44_series/44018/b1a5e556856e7d7d0a4a97692c70247a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6da25c967f5fd7232c4feb8133d7a551fea8da530da1994dfe1e9f99508e62c +size 10576 diff --git a/marked/Rel-16/44_series/44018/c0433bf641e79edba72eb47f584894cb_img.jpg b/marked/Rel-16/44_series/44018/c0433bf641e79edba72eb47f584894cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..346ec01b1e721cc2b1f5d949203cc3813a89f4c7 --- /dev/null +++ b/marked/Rel-16/44_series/44018/c0433bf641e79edba72eb47f584894cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0717e0acdcc7cd4cfa4c4d07ed2ec8d6661fcf5fd21d8db03ee514d8b63996fe +size 17019 diff --git a/marked/Rel-16/44_series/44018/c1b8d1a76c94ebabe6784f51473b317b_img.jpg b/marked/Rel-16/44_series/44018/c1b8d1a76c94ebabe6784f51473b317b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5fbddedf2f73d39dedc710119d6510f9af2414e --- /dev/null +++ b/marked/Rel-16/44_series/44018/c1b8d1a76c94ebabe6784f51473b317b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dafdc4efd280ed85aa38d37ecce45f303b2ba4942313827ae6f85bd139eebbf +size 55108 diff --git a/marked/Rel-16/44_series/44018/c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg b/marked/Rel-16/44_series/44018/c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4f1808936179e964fa30aa3238391ed0944e472 --- /dev/null +++ b/marked/Rel-16/44_series/44018/c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0542a69949ac24448e636bf4e5cdc8cc7d73f33956fd2c31ca74a4c8512044b +size 82520 diff --git a/marked/Rel-16/44_series/44018/cec58cb35e9803b6995668542162f534_img.jpg b/marked/Rel-16/44_series/44018/cec58cb35e9803b6995668542162f534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0febf2c5c0cab836992d3e49cea7847a8a4d8a8 --- /dev/null +++ b/marked/Rel-16/44_series/44018/cec58cb35e9803b6995668542162f534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7928d2c6caf02b0fd53bca288fc9329879e91ab512016bf68ac9959bddbcf3a6 +size 16192 diff --git a/marked/Rel-16/44_series/44018/d5918cee231b536f20789a18d861fae3_img.jpg b/marked/Rel-16/44_series/44018/d5918cee231b536f20789a18d861fae3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4cef756dd4047c2a035c5e1e68d79eb723fa2f6 --- /dev/null +++ b/marked/Rel-16/44_series/44018/d5918cee231b536f20789a18d861fae3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a998f9d464aeff2c987b0269bfe0bd29ed11f17bed4bcf5527b9662c075d9988 +size 37636 diff --git a/marked/Rel-16/44_series/44018/db7ae70402c81d140ae7df14b002e057_img.jpg b/marked/Rel-16/44_series/44018/db7ae70402c81d140ae7df14b002e057_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20eaf5804c5c9281ae67851e8a093a271ced0ef9 --- /dev/null +++ b/marked/Rel-16/44_series/44018/db7ae70402c81d140ae7df14b002e057_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f0d31dbc378e6171f01c2689d5646718d019d21904e02fecce0e1808933d798 +size 19995 diff --git a/marked/Rel-16/44_series/44018/e05434e963901d7e9c0bf5a6758200ed_img.jpg b/marked/Rel-16/44_series/44018/e05434e963901d7e9c0bf5a6758200ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cb621d8fe000f86f3b1679eeac14edca06f1e47 --- /dev/null +++ b/marked/Rel-16/44_series/44018/e05434e963901d7e9c0bf5a6758200ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db4ef9fee318ac8c6d05451b0db48cdc0a1cfe215894f529c2d3d8d6e0270904 +size 29464 diff --git a/marked/Rel-16/44_series/44018/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-16/44_series/44018/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c53655df274fc50236ab0528290a5d2f95abb8e3 --- /dev/null +++ b/marked/Rel-16/44_series/44018/ead623e6a8ec701df64567695a57d01c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2441a2615b4471043a697f92b482eb0a6f16e30a2ab45a35fc80a430290e0165 +size 45772 diff --git a/marked/Rel-16/44_series/44018/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-16/44_series/44018/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc98e2c82ebe89d1ceda2402a2ad25e560bfce2f --- /dev/null +++ b/marked/Rel-16/44_series/44018/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d8a80f5323ed3cdb8c248f60d6d5b52bdc8d7f2f039e5e106f9623cd365a694 +size 18258 diff --git a/marked/Rel-16/44_series/44018/ecc2b08e0d193ae74ff8a8241a83fb01_img.jpg b/marked/Rel-16/44_series/44018/ecc2b08e0d193ae74ff8a8241a83fb01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..965bb5b35be41c511c2624b36a9c04d2ea3dec18 --- /dev/null +++ b/marked/Rel-16/44_series/44018/ecc2b08e0d193ae74ff8a8241a83fb01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78b45fa5604c1cb08b090ba6fa200e84f496783d2785f26109366a3af558757f +size 13631 diff --git a/marked/Rel-16/44_series/44018/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg b/marked/Rel-16/44_series/44018/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c34fe930be5125146e9c7861194908df5e7e682d --- /dev/null +++ b/marked/Rel-16/44_series/44018/f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dffb0c8fe8ff0088fe64ef22eb505ffa3b8eb66bf59041f2c0f408e04ade3d3 +size 19634 diff --git a/marked/Rel-16/44_series/44018/f5dc5aa74ea5482955a1e8e161b5c549_img.jpg b/marked/Rel-16/44_series/44018/f5dc5aa74ea5482955a1e8e161b5c549_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..533ecb3570a87e9a0564797c88e3a3d620cef44d --- /dev/null +++ b/marked/Rel-16/44_series/44018/f5dc5aa74ea5482955a1e8e161b5c549_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47f9025c033478aecf1fe2c107c00b784fdb38398ca83a36031b3d756a70ad65 +size 23186 diff --git a/marked/Rel-16/44_series/44018/ff722ae9516b94709d721deaf5523d2e_img.jpg b/marked/Rel-16/44_series/44018/ff722ae9516b94709d721deaf5523d2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52359f4afa65ff945cb03e8e8f53b9dcca00729d --- /dev/null +++ b/marked/Rel-16/44_series/44018/ff722ae9516b94709d721deaf5523d2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24497286c541c025b3350ec48bdc48d31a0957fb91b4217ae74bcb7ca50e52cc +size 41794 diff --git a/marked/Rel-16/44_series/44018/raw.md b/marked/Rel-16/44_series/44018/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3107277c1057698cf1d246c3910a3d991752e624 --- /dev/null +++ b/marked/Rel-16/44_series/44018/raw.md @@ -0,0 +1,24601 @@ +**Error:** + +2 + +| + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------|----| +| Foreword..... | 19 | +| 1 Scope..... | 20 | +| 1.1 Scope of the Technical Specification..... | 20 | +| 1.2 Application to the interface structures..... | 20 | +| 1.3 Structure of layer 3 procedures..... | 20 | +| 1.4 Test procedures..... | 20 | +| 1.5 Use of logical channels..... | 21 | +| 1.6 Overview of control procedures..... | 21 | +| 1.6.1 List of procedures..... | 21 | +| 1.7 Applicability of implementations..... | 23 | +| 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS)..... | 23 | +| 1.7.2 General Packet Radio Service (GPRS)..... | 23 | +| 1.7.3 Multimedia Broadcast/Multicast Service (MBMS)..... | 23 | +| 1.8 Restrictions..... | 24 | +| 2 References..... | 24 | +| 2.1 Abbreviations..... | 28 | +| 2.1.1 Random values..... | 28 | +| 2.1.2 Vocabulary..... | 28 | +| 3 Radio Resource management procedures..... | 31 | +| 3.1 Overview/General..... | 31 | +| 3.1.1 General..... | 31 | +| 3.1.2 Services provided to upper layers..... | 31 | +| 3.1.2.1 Idle mode..... | 31 | +| 3.1.2.2 Dedicated mode..... | 32 | +| 3.1.2.3 Group receive mode..... | 32 | +| 3.1.2.4 Group transmit mode..... | 32 | +| 3.1.2.5 Packet idle mode..... | 33 | +| 3.1.2.6 Packet transfer mode..... | 33 | +| 3.1.2.7 Dual transfer mode (DTM)..... | 33 | +| 3.1.3 Services required from data link and physical layers..... | 33 | +| 3.1.4 Change of dedicated channels..... | 33 | +| 3.1.4.1 Change of dedicated channels using SAPI = 0..... | 33 | +| 3.1.4.2 Change of dedicated channels using other SAPIs than 0..... | 34 | +| 3.1.5 Procedure for Service Request and Contention Resolution..... | 34 | +| 3.1.6 Preemption..... | 35 | +| 3.2 Idle mode procedures and general procedures in packet idle and packet transfer modes..... | 36 | +| 3.2.1 Mobile Station side..... | 36 | +| 3.2.2 Network side..... | 38 | +| 3.2.2.1 System information broadcasting..... | 38 | +| 3.2.2.2 Paging..... | 40 | +| 3.2.2.3 Sending of ETWS Primary Notification..... | 40 | +| 3.2.3 Inter-RAT cell re-selection based on priority information..... | 41 | +| 3.2.3.1 General..... | 41 | +| 3.2.3.2 Common priorities information..... | 41 | +| 3.2.3.3 Provision of individual priorities information..... | 42 | +| 3.2.4 (void)..... | 42 | +| 3.3 RR connection establishment..... | 42 | +| 3.3.1 RR connection establishment initiated by the mobile station..... | 42 | +| 3.3.1.1 Entering the dedicated mode : immediate assignment procedure..... | 43 | +| 3.3.1.1.1 Permission to access the network..... | 43 | +| 3.3.1.1.1a Implicit reject indication from the network..... | 43 | +| 3.3.1.1.2 Initiation of the immediate assignment procedure..... | 44 | +| 3.3.1.1.3 Answer from the network..... | 45 | +| 3.3.1.1.3.1 On receipt of a CHANNEL REQUEST message..... | 45 | +| 3.3.1.1.3.2 Assignment rejection..... | 46 | +| 3.3.1.1.3.2a Implicit Reject procedure..... | 46 | + +| | | | +|----------------|------------------------------------------------------------------------------------------------------------|----| +| 3.3.1.1.4 | Assignment completion..... | 47 | +| 3.3.1.1.4.1 | Early classmark sending..... | 47 | +| 3.3.1.1.4.2 | Service information sending..... | 48 | +| 3.3.1.1.5 | Abnormal cases..... | 48 | +| 3.3.1.2 | Entering the group transmit mode: uplink access procedure..... | 49 | +| 3.3.1.2.1 | Mobile station side..... | 49 | +| 3.3.1.2.1.1 | Uplink investigation procedure - talker priority not supported by the network..... | 49 | +| 3.3.1.2.1.1a | Uplink investigation procedure - talker priority supported by the network..... | 50 | +| 3.3.1.2.1.2 | Uplink access procedure with talker priority not supported by the network..... | 50 | +| 3.3.1.2.1.2a | Uplink access procedure - with talker priority supported by the network using uplink access procedure..... | 51 | +| 3.3.1.2.1.2a.1 | Talker priority normal, privileged or emergency..... | 51 | +| 3.3.1.2.1.2a.2 | Emergency mode reset request..... | 52 | +| 3.3.1.2.1.2b | Priority uplink request procedure..... | 52 | +| 3.3.1.2.1.2b.1 | Talker priority privileged or emergency..... | 52 | +| 3.3.1.2.1.2b.2 | Emergency mode reset request..... | 53 | +| 3.3.1.2.1.2b.3 | Validation of priority uplink requests for ciphered voice group calls..... | 53 | +| 3.3.1.2.1.2c | Uplink access procedure for sending application-specific data..... | 53 | +| 3.3.1.2.1.2c.1 | General..... | 53 | +| 3.3.1.2.1.2c.2 | Using the Voice Group Call Channel..... | 54 | +| 3.3.1.2.1.2c.3 | Using the RACH..... | 54 | +| 3.3.1.2.2 | Network side - talker priority not supported by the network..... | 54 | +| 3.3.1.2.2a | Network side - network supports talker priority using uplink access procedure..... | 54 | +| 3.3.1.2.2a.1 | Uplink FREE..... | 54 | +| 3.3.1.2.2a.1.1 | Uplink Access cause - Normal, Privileged, or Emergency priority request..... | 54 | +| 3.3.1.2.2a.1.2 | Uplink Access cause - Emergency mode reset request..... | 55 | +| 3.3.1.2.2a.2 | Uplink BUSY..... | 55 | +| 3.3.1.2.2a.2.1 | Uplink Access with cause priority less than or equal to current talker priority..... | 55 | +| 3.3.1.2.2a.2.2 | Uplink Access with cause priority higher than current talker priority..... | 55 | +| 3.3.1.2.2a.2.3 | Uplink Access with cause Emergency mode reset request..... | 55 | +| 3.3.1.2.2b | Network side - network supports talker priority using priority uplink procedure..... | 55 | +| 3.3.1.2.2b.1 | Uplink FREE..... | 55 | +| 3.3.1.2.2b.1.1 | Uplink Access cause - Normal, Privileged, or Emergency priority request..... | 55 | +| 3.3.1.2.2b.1.2 | Uplink Access cause - Emergency mode reset request..... | 56 | +| 3.3.1.2.2b.2 | Uplink BUSY..... | 56 | +| 3.3.1.2.2b.2.1 | Priority Uplink Request with cause priority less than or equal to current talker priority..... | 56 | +| 3.3.1.2.2b.2.2 | Priority Uplink Request with cause priority higher than current talker priority..... | 56 | +| 3.3.1.2.2b.2.3 | Priority Uplink Request with cause Emergency mode reset request..... | 56 | +| 3.3.1.2.2b.2.4 | Validation of Priority Uplink Requests for ciphered voice group calls..... | 56 | +| 3.3.1.2.2c | Network side – network supports sending application-specific data by mobile station..... | 57 | +| 3.3.1.2.2c.1 | General..... | 57 | +| 3.3.1.2.2c.2 | Using the Voice Group Call Channel..... | 57 | +| 3.3.1.2.2c.3 | Using the RACH..... | 57 | +| 3.3.1.2.3 | Abnormal cases..... | 57 | +| 3.3.1.3 | Dedicated mode and GPRS..... | 57 | +| 3.3.1.4 | Preliminary Access Barring Check..... | 57 | +| 3.3.2 | Paging procedure for RR connection establishment..... | 58 | +| 3.3.2.1 | Paging initiation by the network..... | 58 | +| 3.3.2.1.1 | Paging initiation using paging subchannel on CCCH..... | 58 | +| 3.3.2.1.2 | Paging initiation using paging subchannel on PCCCH..... | 59 | +| 3.3.2.1.3 | Paging initiation using PACCH..... | 59 | +| 3.3.2.2 | Paging response..... | 60 | +| 3.3.2.3 | Abnormal cases..... | 60 | +| 3.3.3 | Notification procedure..... | 60 | +| 3.3.3.1 | Notification of a call..... | 60 | +| 3.3.3.2 | Joining a VGCS or VBS call..... | 61 | +| 3.3.3.2.1 | General..... | 61 | +| 3.3.3.2.2 | Segmentation of notifications..... | 62 | +| 3.3.3.2.2.1 | General..... | 62 | +| 3.3.3.2.2.2 | Segmentation of notifications on NCH..... | 62 | +| 3.3.3.2.2.3 | Segmentation of notifications on PCH..... | 64 | + +| | | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------|----| +| 3.3.3.3 | Reduced NCH monitoring mechanism..... | 65 | +| 3.3.3.4 | Notification response procedure..... | 66 | +| 3.4 | Procedures in dedicated mode and in group transmit mode..... | 66 | +| 3.4.1 | SACCH procedures..... | 66 | +| 3.4.1.1 | General..... | 66 | +| 3.4.1.2 | Measurement Report and Enhanced Measurement Report..... | 67 | +| 3.4.1.2.1 | Parameters for Measurements and Reporting..... | 68 | +| 3.4.1.2.1.1 | Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description sent on BCCH or on SACCH..... | 69 | +| 3.4.1.2.1.1a | Deriving the E-UTRAN Neighbour Cell list from the Repeated E-UTRAN Neighbour Cell information sent on BCCH or on SACCH..... | 70 | +| 3.4.1.2.1.1b | Deriving the E-UTRAN Neighbour Cell list from the Repeated E-UTRAN Neighbour Cell information sent on BCCH or on SACCH (abnormal cases)..... | 71 | +| 3.4.1.2.1.2 | Deriving the GSM Neighbour Cell list from the BSICs and the BA (list)..... | 72 | +| 3.4.1.2.1.3 | Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list..... | 72 | +| 3.4.1.2.1.4 | Real Time Differences..... | 72 | +| 3.4.1.2.1.5 | Report Priority Description..... | 72 | +| 3.4.1.2.1.6 | GPRS Parameters..... | 73 | +| 3.4.1.2.1.7 | The 3G Cell Reselection list..... | 73 | +| 3.4.1.2.1.7a | (void)..... | 73 | +| 3.4.1.2.1.7b | Closed Subscriber Group Information..... | 73 | +| 3.4.1.2.1.7c | The 3G Frequency list..... | 73 | +| 3.4.1.2.1.8 | CCN Support description..... | 74 | +| 3.4.1.2.1.9 | 3G_CCN_ACTIVE Description..... | 74 | +| 3.4.1.2.1.9a | E-UTRAN_CCN_ACTIVE Description..... | 74 | +| 3.4.1.2.1.10 | GSM Neighbour Cell Selection parameters..... | 74 | +| 3.4.1.2.1.11 | Fast Acquisition of System Information..... | 75 | +| 3.4.1.2.1.12 | Reporting of CSG Cells and Hybrid Cells..... | 76 | +| 3.4.1.3 | Extended measurement report \$(MAFA)\$..... | 76 | +| 3.4.2 | Transfer of messages and link layer service provision..... | 77 | +| 3.4.3 | Channel assignment procedure..... | 77 | +| 3.4.3.1 | Channel assignment initiation..... | 77 | +| 3.4.3.2 | Assignment completion..... | 79 | +| 3.4.3.3 | Abnormal cases..... | 79 | +| 3.4.4 | Handover procedure..... | 80 | +| 3.4.4.1 | Handover initiation..... | 81 | +| 3.4.4.2 | Physical channel establishment..... | 84 | +| 3.4.4.2.1 | Finely synchronized cell case..... | 84 | +| 3.4.4.2.2 | Non synchronized cell case..... | 84 | +| 3.4.4.2.3 | Pseudo-synchronized cell case..... | 85 | +| 3.4.4.2.4 | Pre-synchronized cell case..... | 85 | +| 3.4.4.3 | Handover completion..... | 86 | +| 3.4.4.4 | Abnormal cases..... | 86 | +| 3.4.4a | Handover to UTRAN procedure..... | 87 | +| 3.4.4a.1 | Handover to UTRAN initiation..... | 88 | +| 3.4.4a.2 | Handover to UTRAN completion..... | 88 | +| 3.4.4a.3 | Abnormal cases..... | 88 | +| 3.4.4b | Handover to CDMA2000 procedure..... | 89 | +| 3.4.4b.1 | Handover to CDMA2000 initiation..... | 89 | +| 3.4.4b.2 | Handover to CDMA2000 completion..... | 89 | +| 3.4.4b.3 | Abnormal cases..... | 89 | +| 3.4.4c | Intermode handover to GERAN Iu mode procedure..... | 90 | +| 3.4.4c.1 | General..... | 90 | +| 3.4.4c.2 | Initiation of the handover to GERAN Iu mode procedure..... | 90 | +| 3.4.4c.3 | Completion of the Handover to GERAN Iu Mode procedure..... | 90 | +| 3.4.4c.4 | Abnormal cases..... | 91 | +| 3.4.4d | CS to PS SRVCC procedure..... | 91 | +| 3.4.4d.1 | CS to PS SRVCC procedure initiation..... | 91 | +| 3.4.4d.2 | CS to PS SRVCC procedure completion..... | 92 | +| 3.4.4d.3 | Abnormal cases..... | 92 | + +| | | | +|----------------|----------------------------------------------------------------------------------------|-----| +| 3.4.5 | Frequency redefinition procedure..... | 92 | +| 3.4.5.1 | Abnormal cases..... | 93 | +| 3.4.6 | Channel mode modify procedure..... | 93 | +| 3.4.6.1 | Normal channel mode modify procedure..... | 93 | +| 3.4.6.1.1 | Initiation of the channel mode modify procedure..... | 93 | +| 3.4.6.1.2 | Completion of channel mode modify procedure..... | 94 | +| 3.4.6.1.3 | Abnormal cases..... | 94 | +| 3.4.6.2 | Channel mode modify procedure for a voice group call talker..... | 94 | +| 3.4.6.2.1 | Initiation of the channel mode modify procedure..... | 94 | +| 3.4.6.2.2 | Completion of mode change procedure..... | 95 | +| 3.4.6.2.3 | Abnormal cases..... | 95 | +| 3.4.7 | Ciphering mode setting procedure..... | 95 | +| 3.4.7.1 | Ciphering mode setting initiation..... | 95 | +| 3.4.7.2 | Ciphering mode setting completion..... | 95 | +| 3.4.7a | Selective Ciphering of Downlink SACCH..... | 96 | +| 3.4.8 | Additional channel assignment procedure..... | 96 | +| 3.4.8.1 | Additional assignment procedure initiation..... | 97 | +| 3.4.8.2 | Additional assignment procedure completion..... | 97 | +| 3.4.8.3 | Abnormal cases..... | 97 | +| 3.4.9 | Partial channel release procedure..... | 97 | +| 3.4.9.1 | Partial release procedure initiation..... | 97 | +| 3.4.9.2 | Abnormal cases..... | 97 | +| 3.4.10 | Classmark change procedure..... | 98 | +| 3.4.11 | Classmark interrogation procedure..... | 98 | +| 3.4.11.1 | Classmark interrogation initiation..... | 98 | +| 3.4.11.2 | Classmark interrogation completion..... | 98 | +| 3.4.12 | Indication of notifications and paging information..... | 99 | +| 3.4.13 | RR connection release procedure..... | 99 | +| 3.4.13.1 | Normal release procedure..... | 99 | +| 3.4.13.1.1 | Channel release procedure initiation in dedicated mode and in group transmit mode..... | 99 | +| 3.4.13.1.1a | Channel release procedure initiation in dual transfer mode..... | 101 | +| 3.4.13.1.2 | Abnormal cases..... | 101 | +| 3.4.13.2 | Radio link failure in dedicated mode or dual transfer mode..... | 101 | +| 3.4.13.2.1 | Mobile side..... | 102 | +| 3.4.13.2.2 | Network side..... | 102 | +| 3.4.13.3 | RR connection abortion in dedicated mode or dual transfer mode..... | 102 | +| 3.4.13.4 | Uplink release procedure..... | 103 | +| 3.4.13.5 | Radio link failure in group transmit mode..... | 103 | +| 3.4.13.5.1 | Mobile side..... | 103 | +| 3.4.13.5.2 | Network side..... | 103 | +| 3.4.13.6 | RR connection abortion requested by upper layers..... | 104 | +| 3.4.14 | Receiving a RR STATUS message by a RR entity..... | 104 | +| 3.4.15 | Group receive mode procedures..... | 104 | +| 3.4.15.1 | Mobile station side..... | 104 | +| 3.4.15.1.1 | Reception of the VGCS or VBS channel..... | 104 | +| 3.4.15.1.1.1 | General..... | 104 | +| 3.4.15.1.1.2 | Reception on ciphered VGCS or VBS channel..... | 104 | +| 3.4.15.1.2 | Monitoring of downlink messages and related procedures..... | 104 | +| 3.4.15.1.2.1 | (void)..... | 105 | +| 3.4.15.1.2.2 | (void)..... | 105 | +| 3.4.15.1.2.3 | Channel mode modify procedure..... | 105 | +| 3.4.15.1.2.4 | Notification and paging information..... | 105 | +| 3.4.15.1.2.4.1 | Use of Reduced NCH monitoring..... | 105 | +| 3.4.15.1.2.5 | Uplink status messages..... | 105 | +| 3.4.15.1.2.6 | Channel release message..... | 106 | +| 3.4.15.1.2.7 | Information on paging channel restructuring..... | 106 | +| 3.4.15.1.3 | Uplink reply procedure..... | 106 | +| 3.4.15.1.4 | Leaving the group receive mode..... | 106 | +| 3.4.15.1.4.1 | Returning to idle mode..... | 106 | +| 3.4.15.1.4.2 | Going to group transmit mode..... | 106 | +| 3.4.15.2 | Network side..... | 107 | + +| | | | +|----------------|---------------------------------------------------------------------------------------|-----| +| 3.4.15.2.1 | Provision of messages on the VGCS or VBS channel downlink..... | 107 | +| 3.4.15.2.1.1 | General..... | 107 | +| 3.4.15.2.1.2 | Provision of general information messages..... | 107 | +| 3.4.15.2.1.3 | Provision of messages related to the voice group call uplink channel..... | 108 | +| 3.4.15.2.1.4 | Provision of messages related to the voice broadcast uplink channel..... | 108 | +| 3.4.15.2.2 | Release of the VGCS or VBS Channels..... | 109 | +| 3.4.15.2a | VBS/VGCS reconfiguration procedure..... | 109 | +| 3.4.15.2a.1 | Normal behaviour..... | 109 | +| 3.4.15.2a.2 | Abnormal cases..... | 109 | +| 3.4.15.3 | Failure cases..... | 110 | +| 3.4.15.3a | Additional Information procedure..... | 110 | +| 3.4.15.3b | SMS to on going group call procedure..... | 110 | +| 3.4.16 | Configuration change procedure..... | 111 | +| 3.4.16.1 | Configuration change initiation..... | 111 | +| 3.4.16.2 | Configuration change completion..... | 111 | +| 3.4.16.3 | Abnormal cases..... | 112 | +| 3.4.17 | Mapping of user data substreams onto timeslots in a multislot configuration..... | 112 | +| 3.4.18 | Handling of classmark information at band change..... | 112 | +| 3.4.19 | (void)..... | 113 | +| 3.4.20 | (void)..... | 113 | +| 3.4.21 | Application Procedures..... | 113 | +| 3.4.21.1 | General..... | 113 | +| 3.4.21.2 | Location Services (LCS)..... | 113 | +| 3.4.21.2A | Earthquake and Tsunami Warning System (ETWS)..... | 113 | +| 3.4.21.3 | Application Information Transfer..... | 113 | +| 3.4.21.3.1 | Normal Procedure without Segmentation..... | 113 | +| 3.4.21.3.2 | Normal Procedure with Segmentation..... | 113 | +| 3.4.21.3.3 | Abnormal Cases..... | 114 | +| 3.4.22 | RR procedures related to packet resource establishment while in dedicated mode..... | 115 | +| 3.4.22.1 | Packet request procedure while in dedicated mode..... | 115 | +| 3.4.22.1.1 | Entering the dual transfer mode..... | 115 | +| 3.4.22.1.1.1 | Permission to access the network..... | 115 | +| 3.4.22.1.1.2 | Initiation of establishment of the packet request procedure..... | 116 | +| 3.4.22.1.1.3 | Answer from the network..... | 116 | +| 3.4.22.1.1.3.1 | Packet assignment..... | 116 | +| 3.4.22.1.1.3.2 | RR reallocation only..... | 117 | +| 3.4.22.1.1.3.3 | Packet request rejection..... | 117 | +| 3.4.22.1.1.4 | Packet request completion..... | 117 | +| 3.4.22.1.1.5 | Abnormal cases..... | 118 | +| 3.4.22.2 | Packet notification procedure in dedicated mode..... | 119 | +| 3.4.22.2.1 | Packet notification initiation by the network..... | 119 | +| 3.4.22.2.2 | Packet notification response..... | 119 | +| 3.4.22.3 | Packet downlink assignment in dedicated mode..... | 119 | +| 3.4.22.3.1 | Initiation of the packet downlink assignment procedure in dedicated mode..... | 120 | +| 3.4.22.3.2 | Packet downlink assignment completion..... | 120 | +| 3.4.22.3.3 | Abnormal cases..... | 120 | +| 3.4.22.4 | Modification of packet resources while in DTM..... | 122 | +| 3.4.23 | RR procedures related to packet resource maintenance while in dual transfer mode..... | 122 | +| 3.4.23.1 | General..... | 122 | +| 3.4.23.2 | RR and packet resource reallocation whilst in dual transfer mode..... | 122 | +| 3.4.23.2.1 | General..... | 122 | +| 3.4.23.2.2 | Normal resource reallocation case..... | 123 | +| 3.4.23.2.3 | Abnormal cases..... | 124 | +| 3.4.24 | RR procedures related to packet resource release while in dual transfer mode..... | 125 | +| 3.4.25 | GPRS suspension procedure..... | 126 | +| 3.4.25.1 | General..... | 126 | +| 3.4.25.2 | MS in class B mode of operation..... | 126 | +| 3.4.25.3 | Dual transfer mode not supported..... | 126 | +| 3.4.26 | GPRS Transparent Transport Procedure..... | 126 | +| 3.4.27 | RR procedures related to dedicated mode MBMS notification..... | 127 | +| 3.4.27.1 | General..... | 127 | + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 3.4.27.2 | MBMS announcement procedure in dedicated mode..... | 127 | +| 3.4.27.2.1 | General..... | 127 | +| 3.4.27.2.2 | MBMS announcement initiation by the network..... | 127 | +| 3.4.27.2.3 | MBMS notification response..... | 127 | +| 3.4.28 | Transmission of application-specific data by the talker..... | 128 | +| 3.4.28.1 | General..... | 128 | +| 3.5 | RR procedures on CCCH and EC-CCCH related to temporary block flow establishment..... | 128 | +| 3.5.0 | General..... | 128 | +| 3.5.1 | Packet paging procedure using CCCH..... | 128 | +| 3.5.1.1 | Packet paging initiation by the network..... | 129 | +| 3.5.1.2 | On receipt of a packet paging request..... | 130 | +| 3.5.1.3 | Packet Paging for MBMS notification on CCCH..... | 130 | +| 3.5.1.3.1 | General..... | 130 | +| 3.5.1.3.2 | MBMS pre-notification..... | 130 | +| 3.5.1.3.3 | MBMS notification..... | 131 | +| 3.5.1.3.4 | Response to MBMS notification..... | 132 | +| 3.5.1a | Packet paging procedure using EC-CCCH..... | 133 | +| 3.5.1a.1 | Packet paging initiation by the network..... | 133 | +| 3.5.2 | Packet access procedure using CCCH..... | 135 | +| 3.5.2.1 | Entering the packet transfer mode: packet access procedure..... | 135 | +| 3.5.2.1.1 | Permission to access the network..... | 135 | +| 3.5.2.1.2 | Initiation of the packet access procedure: channel request..... | 136 | +| 3.5.2.1.2a | EC Packet access procedure (EC-CCCH)..... | 142 | +| 3.5.2.1.3 | Packet immediate assignment..... | 146 | +| 3.5.2.1.3.1 | On receipt of a CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or
EC PACKET CHANNEL REQUEST message or EGPRS MULTILATERATION
REQUEST..... | 146 | +| 3.5.2.1.3.2 | One phase packet access..... | 149 | +| 3.5.2.1.3.3 | Single block packet access..... | 150 | +| 3.5.2.1.3.3a | Multiblock packet access..... | 151 | +| 3.5.2.1.3.4 | Packet access rejection..... | 152 | +| 3.5.2.1.3a | Packet immediate assignment (EC-CCCH)..... | 152 | +| 3.5.2.1.3a.1 | On receipt of an EC PACKET CHANNEL REQUEST or EC MULTILATERATION
REQUEST message..... | 152 | +| 3.5.2.1.3a.2 | Packet access rejection..... | 154 | +| 3.5.2.1.4 | Packet access completion..... | 155 | +| 3.5.2.1.4a | Packet access completion (EC-CCCH)..... | 155 | +| 3.5.2.1.5 | Abnormal cases..... | 155 | +| 3.5.2.1.5a | Abnormal cases (EC-CCCH)..... | 156 | +| 3.5.2.1.6 | (void)..... | 156 | +| 3.5.2.2 | Sending an RLC/MAC control message: single block packet access procedure..... | 156 | +| 3.5.2a | Packet access procedure using EC-CCCH..... | 156 | +| 3.5.2a.1 | EC-GSM-IoT Preliminary Access Barring Check..... | 157 | +| 3.5.2a.2 | EC-GSM-IoT Implicit Reject procedure..... | 158 | +| 3.5.3 | Packet downlink assignment procedure using CCCH..... | 158 | +| 3.5.3.1 | Entering the packet transfer mode: packet downlink assignment procedure..... | 158 | +| 3.5.3.1.2 | Initiation of the packet downlink assignment procedure..... | 158 | +| 3.5.3.1.3 | Packet downlink assignment completion..... | 161 | +| 3.5.3.1.4 | Abnormal cases..... | 161 | +| 3.5.3.2 | Sending an RLC/MAC control message: single block packet downlink assignment procedure..... | 161 | +| 3.5.3.2a | Sending an RLC/MAC control message: multiple blocks packet downlink assignment procedure..... | 162 | +| 3.5.4 | MBMS packet access procedure using CCCH..... | 162 | +| 3.5.4.1 | General..... | 162 | +| 3.5.4.2 | On receipt of a CHANNEL REQUEST message..... | 163 | +| 3.5.4.3 | On receipt of an IMMEDIATE ASSIGNMENT message..... | 163 | +| 3.5.4.4 | On receipt of an IMMEDIATE ASSIGNMENT REJECT message..... | 163 | +| 3.5.4.5 | On receipt of an MBMS ASSIGNMENT message..... | 163 | +| 3.5.4.6 | Abnormal cases..... | 163 | +| 3.5.5 | Packet downlink assignment procedure using EC-CCCH..... | 163 | +| 3.5.5.1 | Entering the packet transfer mode: packet downlink assignment procedure..... | 164 | +| 3.5.5.2 | Initiation of the packet downlink assignment procedure..... | 164 | + +| | | | +|---------|-------------------------------------------------------------------------------------------|-----| +| 3.5.5.3 | Packet downlink assignment completion..... | 165 | +| 3.5.5.4 | Abnormal cases..... | 165 | +| 3.6 | RR Procedures in packet transfer mode..... | 165 | +| 3.6.1 | RR Connection establishment using enhanced DTM CS establishment..... | 165 | +| 3.6.2 | Completion of RR Connection establishment..... | 165 | +| 3.6.2.1 | Connection established in response to an encapsulated IMMEDIATE ASSIGNMENT message..... | 165 | +| 3.6.2.2 | Connection established in response to an encapsulated DTM ASSIGNMENT COMMAND message..... | 166 | +| 3.7 | DTM Handover procedure..... | 166 | +| 3.7.1 | General..... | 166 | +| 3.7.2 | DTM Handover from GERAN A/Gb mode to GERAN A/Gb mode procedure..... | 166 | +| 3.7.2.1 | Abnormal cases..... | 167 | +| 3.7.3 | DTM Handover from GERAN A/Gb mode to UTRAN procedure..... | 168 | +| 3.8 | Network sharing..... | 168 | +| 3.8.1 | General..... | 168 | +| 3.8.2 | Network side..... | 168 | +| 3.8.2.1 | Provision of network sharing information..... | 168 | +| 3.8.2.2 | EC System information broadcasting..... | 169 | +| 3.8.3 | Mobile station side..... | 169 | +| 3.8.4 | Abnormal cases..... | 170 | +| 3.9 | Power Efficient Operation (PEO)..... | 171 | +| 3.9.1 | General..... | 171 | +| 3.9.2 | PEO Power Saving States..... | 171 | +| 3.9.3 | Extended DRX (eDRX)..... | 172 | +| 3.9.4 | BCCH Acquisition..... | 172 | +| 3.9.4.1 | Deferred System Information Acquisition for PEO..... | 173 | +| 3.10 | EC Operation..... | 174 | +| 3.10.1 | General..... | 174 | +| 3.10.2 | Power Saving States..... | 174 | +| 3.10.3 | Extended DRX (eDRX)..... | 175 | +| 3.10.4 | EC-BCCH Acquisition..... | 175 | +| 3.10.5 | Extended Coverage..... | 177 | +| 3.10.6 | EC-CCCH/D Operation..... | 177 | +| 3.11 | Multilateration Timing Advance..... | 178 | +| 3.11.1 | General..... | 178 | +| 3.11.2 | RLC Data Block Method..... | 179 | +| 3.11.3 | Access Burst Method..... | 179 | +| 3.11.4 | Extended Access Burst Method..... | 179 | +| 3.11.5 | BSS Support of Multilateration Timing Advance..... | 180 | +| 4 | Elementary procedures for Mobility Management..... | 180 | +| 5 | Elementary procedures for circuit-switched Call Control..... | 180 | +| 6 | Support for packet services..... | 180 | +| 7 | Examples of structured procedures..... | 181 | +| 8 | Handling of unknown, unforeseen, and erroneous protocol data..... | 181 | +| 8.1 | General..... | 181 | +| 8.2 | Message too short..... | 181 | +| 8.3 | (void)..... | 181 | +| 8.4 | Unknown or unforeseen message type..... | 181 | +| 8.5 | Non-semantical mandatory information element errors..... | 182 | +| 8.5.1 | Radio resource management..... | 183 | +| 8.6 | Unknown and unforeseen IEs in the non-imperative message part..... | 183 | +| 8.6.1 | IEIs unknown in the message..... | 183 | +| 8.6.2 | Out of sequence IEs..... | 183 | +| 8.6.3 | Repeated IEs..... | 183 | +| 8.7 | Non-imperative message part errors..... | 183 | +| 8.7.1 | Syntactically incorrect optional IEs..... | 183 | +| 8.7.2 | Conditional IE errors..... | 183 | +| 8.8 | Messages with semantically incorrect contents..... | 184 | + +| | | | +|-----------|--------------------------------------------------------------------------------------|-----| +| 8.9 | Incomplete rest octets..... | 184 | +| 9 | Message functional definitions and contents..... | 184 | +| 9.1 | Messages for Radio Resources management..... | 186 | +| 9.1.1 | Additional assignment..... | 188 | +| 9.1.1.1 | Mobile Allocation..... | 188 | +| 9.1.1.2 | Starting Time..... | 188 | +| 9.1.1.3 | Extended TSC Set..... | 188 | +| 9.1.2 | Assignment command..... | 188 | +| 9.1.2.1 | Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" (2<=X<=8)..... | 190 | +| 9.1.2.2 | Description of the Second Channel..... | 190 | +| 9.1.2.3 | Mode of the Second Channel..... | 190 | +| 9.1.2.4 | Mobile Allocation and Frequency List, after the starting time..... | 190 | +| 9.1.2.5 | Starting Time..... | 190 | +| 9.1.2.6 | Reference cell frequency list..... | 191 | +| 9.1.2.7 | Cell Channel Description..... | 191 | +| 9.1.2.8 | Cipher Mode Setting..... | 191 | +| 9.1.2.9 | VGCS target mode Indication..... | 191 | +| 9.1.2.10 | Description of the multislot allocation..... | 192 | +| 9.1.2.11 | Multi Rate configuration..... | 192 | +| 9.1.2.12 | VGCS Ciphering Parameters..... | 192 | +| 9.1.2.13 | Extended TSC Set, after time..... | 192 | +| 9.1.2.14 | Extended TSC Set, before time..... | 192 | +| 9.1.3 | Assignment complete..... | 192 | +| 9.1.4 | Assignment failure..... | 193 | +| 9.1.5 | Channel mode modify..... | 193 | +| 9.1.5.1 | Channel Description..... | 194 | +| 9.1.5.2 | VGCS target mode Indication..... | 194 | +| 9.1.5.3 | Multi Rate configuration..... | 194 | +| 9.1.5.4 | VGCS Ciphering Parameters..... | 194 | +| 9.1.5.5 | Extended TSC Set..... | 194 | +| 9.1.6 | Channel mode modify acknowledge..... | 195 | +| 9.1.6.1 | Extended TSC Set..... | 195 | +| 9.1.7 | Channel release..... | 195 | +| 9.1.7.1 | Group Channel Description / Group Channel Description 2..... | 196 | +| 9.1.7.2 | Group Cipher Key Number..... | 196 | +| 9.1.7.3 | UTRAN Freq List..... | 197 | +| 9.1.7.4 | Cell Channel Description..... | 197 | +| 9.1.7.5 | VGCS Ciphering Parameters..... | 197 | +| 9.1.7.6 | Talker Identity..... | 197 | +| 9.1.7.7 | Talker Priority Status..... | 197 | +| 9.1.7.8 | VGCS AMR Configuration..... | 197 | +| 9.1.7.9 | Individual priorities..... | 197 | +| 9.1.8 | Channel request..... | 197 | +| 9.1.9 | Ciphering mode command..... | 199 | +| 9.1.10 | Ciphering mode complete..... | 200 | +| 9.1.10.1 | Mobile Equipment Identity..... | 200 | +| 9.1.11 | Classmark change..... | 200 | +| 9.1.11.1 | Additional Mobile Station Classmark Information..... | 201 | +| 9.1.11.2 | Mobile Station Classmark..... | 201 | +| 9.1.11a | UTRAN Classmark Change..... | 201 | +| 9.1.11b | cdma2000 Classmark Change..... | 201 | +| 9.1.11c | (void)..... | 202 | +| 9.1.11d | GERAN IU Mode Classmark Change..... | 202 | +| 9.1.12 | Classmark enquiry..... | 203 | +| 9.1.12a | (void)..... | 204 | +| 9.1.12b | Configuration change command..... | 204 | +| 9.1.12b.1 | Description of the multislot allocation..... | 204 | +| 9.1.12b.2 | Mode of Channel Set "X" ( 1<=X<=8)..... | 204 | +| 9.1.12c | Configuration change acknowledge..... | 205 | +| 9.1.12d | Configuration change reject..... | 205 | +| 9.1.12e | DTM Assignment Command..... | 206 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------|-----| +| 9.1.12e.1 | (void)..... | 206 | +| 9.1.12e.2 | RR Packet Uplink Assignment and RR Packet Downlink Assignment IEs..... | 206 | +| 9.1.12e.3 | MultiRate configuration..... | 207 | +| 9.1.12e.4 | Ciphering Mode Setting..... | 207 | +| 9.1.12e.5 | (void)..... | 207 | +| 9.1.12e.6 | Mobile Allocation and Frequency List..... | 207 | +| 9.1.12e.7 | Mobile Allocation C2, Frequency List C2, Channel Description C2 and Description of the Downlink Packet Channel Assignment Type 2..... | 207 | +| 9.1.12e.8 | Extended TSC Set..... | 207 | +| 9.1.12f | DTM Assignment Failure..... | 208 | +| 9.1.12g | DTM Information..... | 208 | +| 9.1.12g.1 | Routeing Area Identification..... | 208 | +| 9.1.12h | DTM Reject..... | 209 | +| 9.1.12i | DTM Request..... | 209 | +| 9.1.13 | Frequency redefinition..... | 210 | +| 9.1.13.1 | Cell Channel Description..... | 210 | +| 9.1.13.2 | Carrier Indication..... | 210 | +| 9.1.13.3 | Mobile Allocation C2 and Channel Description C2..... | 210 | +| 9.1.13.4 | Extended TSC Set..... | 210 | +| 9.1.13a | (void)..... | 211 | +| 9.1.13b | GPRS suspension request..... | 211 | +| 9.1.13b.1 | General..... | 211 | +| 9.1.13b.2 | Routeing Area Identification..... | 211 | +| 9.1.13b.3 | Temporary Logical Link Identity..... | 211 | +| 9.1.14 | Handover access..... | 211 | +| 9.1.15 | Handover command..... | 212 | +| 9.1.15.1 | Synchronization Indication..... | 214 | +| 9.1.15.2 | Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" (2≤X≤8)..... | 214 | +| 9.1.15.3 | Description of the Second Channel..... | 214 | +| 9.1.15.4 | Mode of the Second Channel..... | 215 | +| 9.1.15.5 | Frequency Channel Sequence, Frequency List, Frequency short list and Mobile Allocation, after time..... | 215 | +| 9.1.15.6 | Starting Time..... | 215 | +| 9.1.15.7 | Reference cell frequency list..... | 216 | +| 9.1.15.8 | Real Time Difference..... | 216 | +| 9.1.15.9 | Timing Advance..... | 216 | +| 9.1.15.10 | Cipher Mode Setting..... | 216 | +| 9.1.15.11 | VGCS target mode indication..... | 216 | +| 9.1.15.12 | Description of the multislot allocation..... | 217 | +| 9.1.15.13 | MultiRateconfiguration..... | 217 | +| 9.1.15.14 | Dynamic ARFCN Mapping..... | 217 | +| 9.1.15.15 | VGCS Target cell Ciphering information..... | 217 | +| 9.1.15.16 | Dedicated Service Information..... | 217 | +| 9.1.15.17 | Extended TSC Set, after time..... | 217 | +| 9.1.15.18 | Extended TSC Set, before time..... | 218 | +| 9.1.15a | Inter System To UTRAN Handover Command..... | 218 | +| 9.1.15b | Inter System To cdma2000 Handover Command..... | 218 | +| 9.1.15c | HANDOVER TO GERAN Iu MODE Command..... | 219 | +| 9.1.15d | Inter System To E-UTRAN Handover Command..... | 219 | +| 9.1.16 | Handover complete..... | 219 | +| 9.1.16.1 | Mobile Observed Time Difference..... | 220 | +| 9.1.16.2 | Mobile Observed Time Difference on Hyperframe level..... | 220 | +| 9.1.17 | Handover failure..... | 220 | +| 9.1.17.1 | PS Cause..... | 220 | +| 9.1.18 | Immediate assignment..... | 220 | +| 9.1.18.0a | Dedicated mode or TBF..... | 222 | +| 9.1.18.0b | Channel Description..... | 222 | +| 9.1.18.0c | Packet Channel Description..... | 222 | +| 9.1.18.0d | Request Reference..... | 223 | +| 9.1.18.0e | Timing Advance..... | 223 | +| 9.1.18.1 | Mobile Allocation..... | 223 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------------------|-----| +| 9.1.18.2 | Starting Time..... | 223 | +| 9.1.18.3 | IA Rest Octets (Frequency parameters, before time)..... | 223 | +| 9.1.18.4 | IA Rest Octets (assignment of uplink or downlink TBF)..... | 224 | +| 9.1.18.5 | Extended TSC Set..... | 224 | +| 9.1.18.6 | Request Reference N..... | 224 | +| 9.1.18a | (void)..... | 224 | +| 9.1.18b | Immediate packet assignment..... | 224 | +| 9.1.19 | Immediate assignment extended..... | 225 | +| 9.1.19.1 | Unnecessary IEs..... | 226 | +| 9.1.19.2 | Mobile Allocation..... | 226 | +| 9.1.19.3 | Starting Time..... | 226 | +| 9.1.19.4 | Maximum message length..... | 226 | +| 9.1.19.5 | IAX Rest Octets..... | 226 | +| 9.1.20 | Immediate assignment reject..... | 226 | +| 9.1.20.1 | Use of the indexes..... | 227 | +| 9.1.20.2 | Filling of the message..... | 227 | +| 9.1.20.2a | Request Reference..... | 227 | +| 9.1.20.3 | Wait Indication..... | 228 | +| 9.1.20.4 | IAR Rest Octets..... | 228 | +| 9.1.21 | Measurement report..... | 228 | +| 9.1.21a | Notification/FACCH..... | 228 | +| 9.1.21a.1 | (void)..... | 231 | +| 9.1.21a.2 | (void)..... | 231 | +| 9.1.21a.3 | (void)..... | 231 | +| 9.1.21a.4 | (void)..... | 231 | +| 9.1.21b | Notification/NCH..... | 231 | +| 9.1.21b.1 | (void)..... | 232 | +| 9.1.21b.2 | (void)..... | 232 | +| 9.1.21c | (void)..... | 232 | +| 9.1.21d | Notification response..... | 232 | +| 9.1.21e | (void)..... | 233 | +| 9.1.21f | Packet Assignment..... | 233 | +| 9.1.21f.1 | RR Packet Uplink Assignment and RR Packet Downlink Assignment IEs..... | 233 | +| 9.1.21f.2 | (void)..... | 233 | +| 9.1.21f.3 | Frequency List C2, Mobile Allocation C2 and Description of the Downlink Packet Channel
Assignment Type 2..... | 233 | +| 9.1.21f.4 | Extended TSC Set..... | 234 | +| 9.1.21g | Packet Notification..... | 234 | +| 9.1.21g.1 | P-TMSI..... | 234 | +| 9.1.21g.2 | Mobile identity..... | 234 | +| 9.1.21h | VBS/VGCS reconfigure..... | 234 | +| 9.1.21i | VBS/VGCS reconfigure2..... | 235 | +| 9.1.21j | MBMS Announcement..... | 236 | +| 9.1.22 | Paging request type 1..... | 237 | +| 9.1.22.1 | Unnecessary IE..... | 237 | +| 9.1.22.2 | Channels needed for Mobiles 1 and 2..... | 237 | +| 9.1.22.3 | Mobile Identities..... | 238 | +| 9.1.22.4 | P1 Rest Octets..... | 238 | +| 9.1.23 | Paging request type 2..... | 238 | +| 9.1.23.1 | Channels needed for Mobiles 1 and 2..... | 238 | +| 9.1.23.2 | Mobile Identity 3..... | 239 | +| 9.1.23.3 | P2 Rest Octets..... | 239 | +| 9.1.24 | Paging request type 3..... | 239 | +| 9.1.24.1 | Channels needed for Mobiles 1 and 2..... | 239 | +| 9.1.24.2 | P3 Rest Octets..... | 240 | +| 9.1.25 | Paging response..... | 240 | +| 9.1.25.1 | Mobile Station Classmark..... | 240 | +| 9.1.25.2 | Additional Update Parameters..... | 240 | +| 9.1.26 | Partial release..... | 240 | +| 9.1.26.1 | Channel Description..... | 241 | +| 9.1.27 | Partial release complete..... | 241 | + +| | | | +|----------|--------------------------------------------------|-----| +| 9.1.28 | Physical information..... | 241 | +| 9.1.28a | (void)..... | 242 | +| 9.1.29 | RR Status..... | 242 | +| 9.1.30a | Synchronization channel information..... | 242 | +| 9.1.30b | COMPACT Synchronization channel information..... | 243 | +| 9.1.30c | EC-SCH INFORMATION..... | 243 | +| 9.1.31 | System information type 1..... | 246 | +| 9.1.32 | System information type 2..... | 246 | +| 9.1.33 | System information type 2bis..... | 247 | +| 9.1.34 | System information type 2ter..... | 247 | +| 9.1.35 | System information type 3..... | 249 | +| 9.1.36 | System information type 4..... | 249 | +| 9.1.36.1 | CBCH Channel description..... | 250 | +| 9.1.36.2 | CBCH Mobile Allocation..... | 250 | +| 9.1.36.3 | SI 4 Rest Octets..... | 250 | +| 9.1.37 | System information type 5..... | 250 | +| 9.1.38 | System information type 5bis..... | 251 | +| 9.1.39 | System information type 5ter..... | 251 | +| 9.1.40 | System information type 6..... | 252 | +| 9.1.40.1 | Cell Identity..... | 253 | +| 9.1.40.2 | Location Area Identification..... | 253 | +| 9.1.40.3 | Cell Options..... | 253 | +| 9.1.40.4 | NCC permitted..... | 253 | +| 9.1.41 | System information type 7..... | 253 | +| 9.1.42 | System information type 8..... | 253 | +| 9.1.43 | System information Type 9..... | 254 | +| 9.1.43a | System information Type 13..... | 254 | +| 9.1.43b | (void)..... | 255 | +| 9.1.43c | (void)..... | 255 | +| 9.1.43d | System information type 16..... | 255 | +| 9.1.43e | System information type 17..... | 255 | +| 9.1.43f | System information type 19..... | 256 | +| 9.1.43g | System information type 18..... | 256 | +| 9.1.43h | System information type 20..... | 257 | +| 9.1.43i | System information type 14..... | 257 | +| 9.1.43j | System information type 15..... | 258 | +| 9.1.43k | System information Type 13alt..... | 258 | +| 9.1.43p | EC System information type 1..... | 260 | +| 9.1.43q | EC System information type 2..... | 263 | +| 9.1.43r | EC System information type 3..... | 272 | +| 9.1.43s | EC System information type 4..... | 276 | +| 9.1.44 | Talker indication..... | 277 | +| 9.1.44a | Priority Uplink Request..... | 278 | +| 9.1.44b | Data Indication..... | 278 | +| 9.1.44c | Data Indication 2..... | 279 | +| 9.1.45 | Uplink access..... | 279 | +| 9.1.46 | Uplink busy..... | 280 | +| 9.1.46.1 | Talker Priority and Emergency Indication..... | 280 | +| 9.1.46.2 | Token..... | 280 | +| 9.1.46.3 | Talker Identity..... | 280 | +| 9.1.46.4 | Uplink Access Indication..... | 281 | +| 9.1.47 | Uplink free..... | 281 | +| 9.1.48 | Uplink release..... | 281 | +| 9.1.49 | VGCS uplink grant..... | 282 | +| 9.1.49a | VGCS Additional Information..... | 282 | +| 9.1.49b | VGCS SMS Information..... | 283 | +| 9.1.50 | System information type 10 \$(ASCII)\$..... | 284 | +| 9.1.50a | System information type 10bis \$(ASCII)\$..... | 285 | +| 9.1.50b | System information type 10ter \$(ASCII)\$..... | 285 | +| 9.1.51 | EXTENDED MEASUREMENT ORDER..... | 286 | +| 9.1.52 | Extended measurement report..... | 286 | + +| | | | +|-------------|-------------------------------------------------------------|-----| +| 9.1.53 | Application Information..... | 287 | +| 9.1.54 | MEASUREMENT INFORMATION..... | 287 | +| 9.1.55 | ENHANCED MEASUREMENT REPORT..... | 300 | +| 9.1.56 | Service Information message..... | 303 | +| 9.1.56.1 | Temporary Logical Link Identity..... | 303 | +| 9.1.56.2 | Routeing Area Identification..... | 304 | +| 9.1.57 | VGCS Neighbour Cell Information message..... | 304 | +| 9.1.58 | NOTIFY APPLICATION DATA..... | 305 | +| 9.1.59 | EC IMMEDIATE ASSIGNMENT TYPE 1..... | 306 | +| 9.1.59.0 | Request Reference..... | 306 | +| 9.1.59.1 | EC Packet Channel Description Type 1..... | 306 | +| 9.1.59.2 | EC Fixed Uplink Allocation..... | 306 | +| 9.1.60 | EC IMMEDIATE ASSIGNMENT TYPE 2..... | 306 | +| 9.1.61 | EC Immediate Assignment Reject..... | 314 | +| 9.1.62 | EC Dummy..... | 315 | +| 9.1.63 | EC PAGING REQUEST..... | 315 | +| 9.1.64 | EC DOWNLINK ASSIGNMENT..... | 317 | +| 9.1.65 | EC Packet Channel Request..... | 321 | +| 9.1.66 | EC IMMEDIATE ASSIGNMENT TYPE 4..... | 329 | +| 9.1.67 | EC DOWNLINK ASSIGNMENT TYPE 2..... | 332 | +| 9.1.68 | EC IMMEDIATE ASSIGNMENT TYPE 3..... | 334 | +| 9.1.69 | EC PAGING INDICATION..... | 336 | +| 9.2 | Messages for mobility management..... | 338 | +| 9.3 | Messages for circuit-switched call control..... | 338 | +| 9.4 | GPRS Mobility Management Messages..... | 338 | +| 9.5 | GPRS Session Management Messages..... | 338 | +| 9.6 | GTTP Messages..... | 338 | +| 9.6.1 | GPRS Information..... | 339 | +| 9.6.1.1 | TLLI..... | 339 | +| 9.6.1.2 | LLC PDU Container..... | 339 | +| 10 | General message format and information elements coding..... | 339 | +| 10.1 | Overview..... | 339 | +| 10.2 | Protocol Discriminator..... | 340 | +| 10.3 | Skip indicator..... | 340 | +| 10.3.1 | Skip indicator..... | 340 | +| 10.4 | Message Type..... | 341 | +| 10.5 | Other information elements..... | 343 | +| 10.5.1 | Common information elements..... | 345 | +| 10.5.1.0 | General..... | 345 | +| 10.5.1.1 | Cell identity..... | 345 | +| 10.5.1.2 | Ciphering Key Sequence Number..... | 345 | +| 10.5.1.3 | Location Area Identification..... | 345 | +| 10.5.1.4 | Mobile Identity..... | 345 | +| 10.5.1.5 | Mobile Station Classmark 1..... | 345 | +| 10.5.1.6 | Mobile Station Classmark 2..... | 345 | +| 10.5.1.7 | Mobile Station Classmark 3..... | 345 | +| 10.5.1.8 | Spare Half Octet..... | 345 | +| 10.5.1.9 | Descriptive group or broadcast call reference..... | 345 | +| 10.5.1.10 | Group Cipher Key Number..... | 346 | +| 10.5.1.10a | (void)..... | 346 | +| 10.5.1.11 | (void)..... | 346 | +| 10.5.1.12 | (void)..... | 346 | +| 10.5.1.13 | (void)..... | 346 | +| 10.5.2 | Radio Resource management information elements..... | 346 | +| 10.5.2.1a | BA Range..... | 346 | +| 10.5.2.1b | Cell Channel Description..... | 347 | +| 10.5.2.1b.1 | General description..... | 347 | +| 10.5.2.1b.2 | Bit map 0 format..... | 348 | +| 10.5.2.1b.3 | Range 1024 format..... | 349 | +| 10.5.2.1b.4 | Range 512 format..... | 350 | +| 10.5.2.1b.5 | Range 256 format..... | 351 | + +| | | | +|-------------|---------------------------------------------------------------------|-----| +| 10.5.2.1b.6 | Range 128 format..... | 352 | +| 10.5.2.1b.7 | Variable bit map format..... | 353 | +| 10.5.2.1c | BA List Pref..... | 353 | +| 10.5.2.1d | UTRAN Freq List..... | 354 | +| 10.5.2.1e | Cell selection indicator after release of all TCH and SDCCH IE..... | 354 | +| 10.5.2.2 | Cell Description..... | 356 | +| 10.5.2.3 | Cell Options (BCCH)..... | 356 | +| 10.5.2.3a | Cell Options (SACCH)..... | 357 | +| 10.5.2.4 | Cell Selection Parameters..... | 358 | +| 10.5.2.4a | (void)..... | 360 | +| 10.5.2.5 | Channel Description..... | 360 | +| 10.5.2.5a | Channel Description 2..... | 361 | +| 10.5.2.5c | Channel Description 3..... | 363 | +| 10.5.2.6 | Channel Mode..... | 363 | +| 10.5.2.7 | Channel Mode 2..... | 364 | +| 10.5.2.7a | UTRAN Classmark information element..... | 365 | +| 10.5.2.7b | (void)..... | 365 | +| 10.5.2.7c | Classmark Enquiry Mask..... | 365 | +| 10.5.2.7d | GERAN Iu Mode Classmark information element..... | 366 | +| 10.5.2.8 | Channel Needed..... | 366 | +| 10.5.2.8a | (void)..... | 367 | +| 10.5.2.8b | Channel Request Description 2..... | 367 | +| 10.5.2.9 | Cipher Mode Setting..... | 370 | +| 10.5.2.10 | Cipher Response..... | 370 | +| 10.5.2.11 | Control Channel Description..... | 371 | +| 10.5.2.11a | DTM Information Details..... | 373 | +| 10.5.2.11b | Dynamic ARFCN Mapping..... | 374 | +| 10.5.2.12 | Frequency Channel Sequence..... | 375 | +| 10.5.2.13 | Frequency List..... | 376 | +| 10.5.2.13.1 | General description..... | 376 | +| 10.5.2.13.2 | Bit map 0 format..... | 376 | +| 10.5.2.13.3 | Range 1024 format..... | 377 | +| 10.5.2.13.4 | Range 512 format..... | 379 | +| 10.5.2.13.5 | Range 256 format..... | 380 | +| 10.5.2.13.6 | Range 128 format..... | 383 | +| 10.5.2.13.7 | Variable bit map format..... | 385 | +| 10.5.2.14 | Frequency Short List..... | 385 | +| 10.5.2.14a | Frequency Short List 2..... | 385 | +| 10.5.2.14b | Group Channel Description..... | 385 | +| 10.5.2.14c | GPRS Resumption..... | 388 | +| 10.5.2.14d | GPRS broadcast information..... | 388 | +| 10.5.2.14e | Enhanced DTM CS Release Indication..... | 389 | +| 10.5.2.14f | Group Channel Description 2..... | 389 | +| 10.5.2.15 | Handover Reference..... | 390 | +| 10.5.2.16 | IA Rest Octets..... | 391 | +| 10.5.2.17 | IAR Rest Octets..... | 402 | +| 10.5.2.18 | IAX Rest Octets..... | 403 | +| 10.5.2.19 | L2 Pseudo Length..... | 404 | +| 10.5.2.20 | Measurement Results..... | 405 | +| 10.5.2.20a | (void)..... | 408 | +| 10.5.2.21 | Mobile Allocation..... | 408 | +| 10.5.2.21a | Mobile Time Difference..... | 409 | +| 10.5.2.21aa | MultiRate configuration..... | 409 | +| 10.5.2.21ab | Mobile Time Difference on Hyperframe level..... | 413 | +| 10.5.2.21b | Multislot Allocation..... | 414 | +| 10.5.2.21c | (void)..... | 415 | +| 10.5.2.22 | Neighbour Cell Description..... | 415 | +| 10.5.2.22a | Neighbour Cell Description 2..... | 416 | +| 10.5.2.22b | (void)..... | 417 | +| 10.5.2.22c | NT/N Rest Octets..... | 417 | +| 10.5.2.23 | P1 Rest Octets..... | 419 | + +| | | | +|------------|--------------------------------------------|-----| +| 10.5.2.24 | P2 Rest Octets..... | 425 | +| 10.5.2.25 | P3 Rest Octets..... | 428 | +| 10.5.2.25a | Packet Channel Description..... | 430 | +| 10.5.2.25b | Dedicated mode or TBF..... | 431 | +| 10.5.2.25c | RR Packet Uplink Assignment..... | 433 | +| 10.5.2.25d | RR Packet Downlink Assignment..... | 439 | +| 10.5.2.25e | RR Packet Downlink Assignment Type 2..... | 442 | +| 10.5.2.26 | Page Mode..... | 448 | +| 10.5.2.26a | (void)..... | 448 | +| 10.5.2.26b | (void)..... | 448 | +| 10.5.2.26c | (void)..... | 448 | +| 10.5.2.26d | (void)..... | 448 | +| 10.5.2.27 | NCC Permitted..... | 448 | +| 10.5.2.28 | Power Command..... | 449 | +| 10.5.2.28a | Power Command and access type..... | 450 | +| 10.5.2.29 | RACH Control Parameters..... | 451 | +| 10.5.2.30 | Request Reference..... | 452 | +| 10.5.2.30a | Random Reference/ Establishment Cause..... | 453 | +| 10.5.2.31 | RR Cause..... | 454 | +| 10.5.2.32 | SI 1 Rest Octets..... | 455 | +| 10.5.2.33 | SI 2bis Rest Octets..... | 456 | +| 10.5.2.33a | SI 2ter Rest Octets..... | 456 | +| 10.5.2.33b | SI 2quater Rest Octets..... | 458 | +| 10.5.2.33c | SI 2n Rest Octets..... | 472 | +| 10.5.2.34 | SI 3 Rest Octets..... | 474 | +| 10.5.2.35 | SI 4 Rest Octets..... | 477 | +| 10.5.2.35a | SI 6 Rest Octets..... | 480 | +| 10.5.2.36 | SI 7 Rest Octets..... | 482 | +| 10.5.2.37 | SI 8 Rest Octets..... | 483 | +| 10.5.2.37a | SI 9 Rest Octets..... | 483 | +| 10.5.2.37b | SI 13 Rest Octets..... | 484 | +| 10.5.2.37c | (void)..... | 492 | +| 10.5.2.37d | (void)..... | 492 | +| 10.5.2.37e | SI 16 Rest Octets..... | 492 | +| 10.5.2.37f | SI 17 Rest Octets..... | 493 | +| 10.5.2.37g | SI 19 Rest Octets..... | 493 | +| 10.5.2.37h | SI 18 Rest Octets..... | 495 | +| 10.5.2.37i | SI 20 Rest Octets..... | 497 | +| 10.5.2.37j | SI 14 Rest Octets..... | 497 | +| 10.5.2.37k | SI 15 Rest Octets..... | 498 | +| 10.5.2.37l | SI 13alt Rest Octets..... | 499 | +| 10.5.2.37m | SI 21 Rest Octets..... | 500 | +| 10.5.2.37n | SI 22 Rest Octets..... | 502 | +| 10.5.2.37o | SI 23 Rest Octets..... | 503 | +| 10.5.2.38 | Starting Time..... | 506 | +| 10.5.2.39 | Synchronization Indication..... | 507 | +| 10.5.2.40 | Timing Advance..... | 508 | +| 10.5.2.41 | Time Difference..... | 508 | +| 10.5.2.41a | TLLI..... | 508 | +| 10.5.2.42 | TMSI/P-TMSI..... | 509 | +| 10.5.2.42a | VGCS target mode Indication..... | 509 | +| 10.5.2.42b | VGCS Ciphering Parameters..... | 510 | +| 10.5.2.43 | Wait Indication..... | 511 | +| 10.5.2.44 | SI10 rest octets \$(ASCII)\$..... | 511 | +| 10.5.2.45 | EXTENDED MEASUREMENT RESULTS..... | 514 | +| 10.5.2.46 | Extended Measurement Frequency List..... | 516 | +| 10.5.2.47 | Suspension Cause..... | 516 | +| 10.5.2.48 | APDU ID..... | 517 | +| 10.5.2.49 | APDU Flags..... | 517 | +| 10.5.2.50 | APDU Data..... | 518 | +| 10.5.2.51 | Handover To UTRAN Command..... | 518 | + +| | | | +|------------|----------------------------------------------------|-----| +| 10.5.2.52 | Handover To cdma2000 Command..... | 519 | +| 10.5.2.53 | (void)..... | 519 | +| 10.5.2.54 | (void)..... | 519 | +| 10.5.2.55 | (void)..... | 519 | +| 10.5.2.56 | (void)..... | 519 | +| 10.5.2.57 | Service Support..... | 519 | +| 10.5.2.58 | MBMS p-t-m Channel Description..... | 520 | +| 10.5.2.58a | MBMS Session Parameters List..... | 520 | +| 10.5.2.59 | Dedicated Service Information..... | 521 | +| 10.5.2.60 | MPRACH Description..... | 521 | +| 10.5.2.61 | Restriction Timer..... | 522 | +| 10.5.2.62 | MBMS Session Identity..... | 523 | +| 10.5.2.63 | Reduced group or broadcast call reference..... | 523 | +| 10.5.2.64 | Talker Priority status..... | 524 | +| 10.5.2.65 | Talker Identity..... | 524 | +| 10.5.2.66 | Token..... | 525 | +| 10.5.2.67 | PS Cause..... | 525 | +| 10.5.2.68 | VGCS AMR Configuration..... | 526 | +| 10.5.2.69 | Carrier Indication..... | 526 | +| 10.5.2.70 | SI10bis Rest Octets..... | 527 | +| 10.5.2.71 | SI10ter Rest Octets..... | 528 | +| 10.5.2.72 | Application Data..... | 528 | +| 10.5.2.73 | Data Identity..... | 528 | +| 10.5.2.74 | Uplink Access Indication..... | 529 | +| 10.5.2.75 | Individual priorities..... | 529 | +| 10.5.2.76 | Feature Indicator..... | 531 | +| 10.5.2.77 | (void)..... | 532 | +| 10.5.2.79 | DL-DCCH-Message..... | 536 | +| 10.5.2.80 | CN to MS transparent information..... | 537 | +| 10.5.2.81 | PLMN Index..... | 537 | +| 10.5.2.82 | Extended TSC Set..... | 538 | +| 10.5.2.83 | EC Request Reference..... | 540 | +| 10.5.2.84 | EC Packet Channel Description Type 1..... | 540 | +| 10.5.2.85 | EC Packet Channel Description Type 2..... | 541 | +| 10.5.2.86 | EC Fixed Uplink Allocation..... | 542 | +| 10.5.2.87 | Request Reference Alt..... | 543 | +| 10.5.2.88 | EC Packet Channel Description Type 3..... | 544 | +| 10.5.3 | Void..... | 545 | +| 10.5.4 | Call control information elements..... | 545 | +| 10.5.5 | GPRS mobility management information elements..... | 545 | +| 10.5.5.0 | General..... | 545 | +| 10.5.5.1 | (void)..... | 545 | +| 10.5.5.2 | (void)..... | 545 | +| 10.5.5.3 | (void)..... | 545 | +| 10.5.5.4 | (void)..... | 545 | +| 10.5.5.5 | (void)..... | 545 | +| 10.5.5.6 | (void)..... | 545 | +| 10.5.5.7 | (void)..... | 545 | +| 10.5.5.8 | (void)..... | 545 | +| 10.5.5.8a | (void)..... | 545 | +| 10.5.5.9 | (void)..... | 545 | +| 10.5.5.10 | (void)..... | 545 | +| 10.5.5.11 | (void)..... | 545 | +| 10.5.5.12 | (void)..... | 545 | +| 10.5.5.12a | (void)..... | 545 | +| 10.5.5.13 | (void)..... | 545 | +| 10.5.5.14 | (void)..... | 545 | +| 10.5.5.15 | Routing area identification..... | 546 | +| 10.5.5.16 | (void)..... | 546 | +| 10.5.5.17 | (void)..... | 546 | +| 10.5.5.18 | (void)..... | 546 | + +| | | | +|-----------|--------------------------------------------------------|-----| +| 10.5.5.19 | (void)..... | 546 | +| 10.5.5.20 | (void)..... | 546 | +| 10.5.5.21 | (void)..... | 546 | +| 10.5.5.22 | (void)..... | 546 | +| 10.5.5.23 | (void)..... | 546 | +| 10.5.5.24 | (void)..... | 546 | +| 10.5.5.25 | (void)..... | 546 | +| 10.5.6 | Session management information elements..... | 546 | +| 10.5.7 | GPRS Common information elements..... | 546 | +| 10.5.8 | GTTP information elements..... | 546 | +| 10.5.8.1 | LLC PDU Container..... | 546 | +| 11 | List of system parameters..... | 547 | +| 11.1 | Timers and counters for radio resource management..... | 547 | +| 11.1.1 | Timers on the mobile station side..... | 547 | +| 11.1.2 | Timers on the network side..... | 552 | +| 11.1.3 | Other parameters..... | 554 | +| 11.2 | Timers of mobility management..... | 554 | +| 11.3 | Timers of circuit-switched call control..... | 554 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------|------------| +| Annex A (informative): | Example of subaddress information element coding..... | 555 | +| Annex B (normative): | Compatibility checking..... | 556 | +| Annex C (normative): | Low layer information coding principles..... | 557 | +| Annex D (informative): | Examples of bearer capability information element coding..... | 558 | +| Annex E (informative): | Comparison between call control procedures specified in 3GPP TS 24.008 and ITU-T Recommendation Q.931..... | 559 | +| Annex F (informative): | GSM specific cause values for radio resource management..... | 560 | +| Annex G (informative): | GSM specific cause values for mobility management..... | 562 | +| Annex H (informative): | GSM specific cause values for call control..... | 563 | +| Annex I (informative): | GSM specific cause values for session management..... | 564 | +| Annex J (informative): | Algorithm to encode frequency list information elements..... | 565 | +| J.1 | Introduction..... | 565 | +| J.2 | General principle..... | 565 | +| J.3 | Performances..... | 567 | +| J.4 | Encoding algorithm..... | 568 | +| J.5 | Decoding..... | 570 | +| J.6 | A detailed example..... | 571 | +| Annex K (informative): | Default Codings of Information Elements..... | 573 | +| K.1 | Common information elements..... | 573 | +| K.2 | Radio Resource management information elements..... | 574 | +| Annex L (normative): | Additional Requirements for backward compatibility with PCS 1900 for NA revision 0 ME..... | 575 | +| Annex M (informative): | Application of the "previously listed field" rule by mobile stations supporting network sharing..... | 575 | +| M.1 | Example for the Additional_ACC field..... | 575 | +| M.2 | Example for the PS_ACC field..... | 575 | +| M.2.1 | With Common_PLMN_PS_ACC field broadcast..... | 575 | +| M.2.2 | With Common_PLMN_PS_ACC field not broadcast..... | 576 | +| Annex N (informative): | Change History..... | 577 | + +--- + +--- + +## 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 procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002) for Radio Resource (RR) management. + +Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts. + +When the notations for "further study" or "FS" or "FFS" are present in this specification they mean that the indicated text is not a normative portion of this standard. + +These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPP TS 44.003. + +The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007. + +## 1.1 Scope of the Technical Specification + +The procedures currently described in the present document are for radio resource management for circuit-switched and GPRS services. + +3GPP TS 24.010 contains functional procedures for support of supplementary services. + +3GPP TS 24.011 contains functional procedures for support of point-to-point short message services. + +3GPP TS 44.012 contains functional description of short message - cell broadcast. + +3GPP TS 44.060 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels. + +3GPP TS 44.071 contains functional descriptions and procedures for support of location services. + +3GPP TS 24.008 contains the procedures for CN protocols. + +NOTE: "layer 3" includes the functions and protocols described in this Technical Specification. The terms "data link layer" and "layer 2" are used interchangeably to refer to the layer immediately below layer 3. + +## 1.2 Application to the interface structures + +The layer 3 procedures apply to the interface structures defined in 3GPP TS 44.003. They use the functions and services provided by layer 2 defined in 3GPP TS 44.005 and 3GPP TS 44.006. 3GPP TS 24.007 gives the general description of layer 3 including procedures, messages format and error handling. + +## 1.3 Structure of layer 3 procedures + +A building block method is used to describe the layer 3 procedures. + +The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer. + +Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences. + +## 1.4 Test procedures + +Test procedures of the GSM radio interface signalling are described in 3GPP TS 51.010 and 3GPP TS 51.02x series. + +## 1.5 Use of logical channels + +The logical control channels are defined in 3GPP TS 45.002. In the following those control channels are considered which carry signalling information or specific types of user packet information: + +- i) Broadcast Control CHannel (BCCH): downlink only, used to broadcast Cell specific information; +- ii) Synchronization CHannel (SCH): downlink only, used to broadcast synchronization and BSS identification information; +- iii) Paging CHannel (PCH): downlink only, used to send page requests to Mobile Stations (MSs); +- iv) Random Access CHannel (RACH): uplink only, used to request a Dedicated Control CHannel; +- v) Access Grant CHannel (AGCH): downlink only, used to allocate a Dedicated Control CHannel; +- vi) Standalone Dedicated Control CHannel (SDCCH): bi-directional; +- vii) Fast Associated Control CHannel (FACCH): bi-directional, associated with a Traffic CHannel; +- viii) Slow Associated Control CHannel (SACCH): bi-directional, associated with a SDCCH or a Traffic CHannel; +- ix) Cell Broadcast CHannel (CBCH): downlink only used for general (not point to point) short message information; +- x) Notification CHannel (NCH): downlink only, used to notify mobile stations of VBS (Voice Broadcast Service) calls or VGCS (Voice Group Call Service) calls. +- xi) Extended Coverage Broadcast Control CHannel (EC-BCCH): downlink only, used to broadcast Cell specific information in cells that support EC-GSM-IoT; +- xii) Extended Coverage Synchronization CHannel (EC-SCH): downlink only, used to broadcast synchronization, BSS identification, EC-BCCH CHANGE MARK, Implicit Reject Status and RACH Access Control in cells that support EC-GSM-IoT; +- xiii) Extended Coverage Paging CHannel (EC-PCH): downlink only, used to send page requests to EC capable Mobile Stations (MSs) in cells that support EC-GSM-IoT; +- xiv) Extended Coverage Access Grant CHannel (EC-AGCH): downlink only, used to allocate packet resources to EC capable Mobile Stations (MSs) in cells that support EC-GSM-IoT; +- xv) Extended Coverage Random Access CHannel (EC-RACH): uplink only, used to request uplink packet resources by EC capable Mobile Stations (MSs) in cells that support EC-GSM-IoT; + +Two service access points are defined on signalling layer 2 which are discriminated by their Service Access Point Identifiers (SAPI) (see 3GPP TS 44.006): + +- i) SAPI 0: supports the transfer of signalling information including user-user information; +- ii) SAPI 3: supports the transfer of user short messages. + +Layer 3 selects the service access point, the logical control channel and the mode of operation of layer 2 (acknowledged, unacknowledged or random access, see 3GPP TS 44.005 and 3GPP TS 44.006) as required for each individual message. + +## 1.6 Overview of control procedures + +### 1.6.1 List of procedures + +The following procedures are specified in this Technical Specification: + +- a) Clause 3 specifies elementary procedures for Radio Resource management: + - system information broadcasting (sub-clause 3.2.2); + - RR connection establishment (sub-clause 3.3): + - entering the dedicated mode: immediate assignment procedure (sub-clause 3.3.1.1); + - paging procedure for RR connection establishment (sub-clause 3.3.2); + +- notification procedure (sub-clause 3.3.3). +- Procedures in dedicated mode and in group transmit mode (sub-clause 3.4): + - measurement report procedure (sub-clause 3.4.1.2); + - intracell change of channels (sub-clause 3.4.3); + - intercell change of channels (sub-clause 3.4.4); + - frequency redefinition procedure (sub-clause 3.4.5); + - channel mode change procedure (sub-clause 3.4.6); + - ciphering mode setting procedure (sub-clause 3.4.7); + - additional channel assignment procedure (sub-clause 3.4.8); + - partial channel release procedure (sub-clause 3.4.9). +- radio resources connection release (sub-clause 3.4.13); +- specific RR procedures for voice broadcast channels and voice group call channels (sub-clause 3.4.15); +- application procedures (sub-clause 3.4.21); +- RR procedures on CCCH and EC-CCCH related to temporary block flow establishment (sub-clause 3.5): + - packet paging procedure using CCCH (sub-clause 3.5.1); + - packet paging procedure using EC-CCCH (sub-clause 3.5.1a); + - packet access procedure using CCCH (sub-clause 3.5.2); + - packet access procedure using EC-CCCH (see sub-clause 3.5.2a); + - packet downlink assignment procedure using CCCH (sub-clause 3.5.3); + - packet downlink assignment procedure using EC-CCCH (sub-clause 3.5.5 ). +- RR procedures on DCCH related to temporary block flow establishment: + - Assignment to Packet Data Channel procedure (sub-clause 3.4.19); + - Network controlled cell reselection (sub-clause 3.4.20). +- RR procedure on DCCH related to MBMS: + - packet paging procedure for MBMS related to dedicated MBMS notification (sub-clause 3.4.27). +- RR procedures on CCCH related to MBMS: + - packet paging procedure for MBMS notification using CCCH (sub-clause 3.5.1.3); + - packet access procedure for MBMS using CCCH (sub-clause 3.5.4). +- Procedures related to the simultaneous handover of dedicated and packet resources (sub-clause 3.7). + +Clause 8 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol. + +## 1.7 Applicability of implementations + +The applicability of procedures of this technical specification for the mobile station is dependent on the services and functions which are to be supported by a mobile station. For the MS, the Revision level indicating Release 1999 is linked to the full support of the RR protocol and procedures in 3GPP TS 44.018 Release 1999. + +### 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) + +For mobile stations supporting the Voice Group Call Service or the Voice Broadcast Service, it is explicitly mentioned throughout this technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave. + +For VGCS and VBS, the following possible mobile station implementations exist: + +- support of listening to voice broadcast calls (VBS listening); +- support of originating a voice broadcast call (VBS originating); +- support of listening to voice group calls (VGCS listening); +- support of talking in voice group calls (VGCS talking. This always includes the implementation for VGCS listening); +- support of originating a voice group call (VGCS originating. This always includes the implementation for VGCS talking). + +Apart from the explicitly mentioned combinations, all possible combinations are optional and supported by this technical specification. + +A VGCS capable mobile station shall support USIM-based VGCS ciphering. + +The related terms are used in this technical specification, if information on these implementation options is required. + +### 1.7.2 General Packet Radio Service (GPRS) + +For mobile stations supporting the General Packet Radio Service (GPRS), it is explicitly mentioned throughout the technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave. + +A GPRS MS may operate in one of the following MS operation modes, see 3GPP TS 23.060: + +- MS operation mode A; +- MS operation mode B; or +- MS operation mode C. + +The MS operation mode depends on the services that the MS is attached to, i.e., only GPRS or both GPRS and non-GPRS services, and upon the MS's capabilities to operate GPRS and other GSM services simultaneously. Mobile stations that are capable to operate GPRS services are referred to as GPRS MSs. + +NOTE: Other GSM technical specifications may refer to the MS operation modes A, B, and C as GPRS class-A MS, GPRS class-B MS, and GPRS class-C MS. + +It should be noted that it is possible that for a GPRS MS, the GMM procedures currently described in the present document do not support combinations of VGCS, VBS and GPRS. The possible interactions are not studied yet. + +### 1.7.3 Multimedia Broadcast/Multicast Service (MBMS) + +For mobile stations supporting the Multimedia Broadcast/Multicast Service (MBMS) feature, it is explicitly mentioned throughout the technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave. + +The support of dedicated mode MBMS notification is mandatory for mobile stations and optional for networks supporting the Multimedia Broadcast/Multicast Service (MBMS) feature. The dedicated mode MBMS notification consists of the Service Information Sending procedure and the MBMS announcement of mobile stations in dedicated mode. + +## 1.8 Restrictions + +Independently of what is stated elsewhere in this and other 3GPP specifications, mobile station support for PBCCH and PCCCH is optional for A/Gb-mode of operation. The network shall never enable PBCCH and PCCCH. + +--- + +## 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 TR 21.905: "Vocabulary for 3GPP Specifications". +- [3] (void) +- [4] (void) +- [5] (void) +- [6] 3GPP TS 22.011: "Technical Specification Group Services and System Aspects; Service accessibility". +- [7] (void) +- [8] (void) +- [9] (void) +- [10] 3GPP TS 23.003: "Numbering, addressing and identification". +- [11] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM system". +- [12] (void) +- [12a] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services in GERAN". +- [13] (void) +- [14] 3GPP TS 23.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [15] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [16] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". +- [17] 3GPP TS 44.004: "Layer 1; General requirements". +- [18] 3GPP TS 44.005: "Data Link (DL) layer; General aspects". +- [19] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". +- [20] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". + +- [21] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification; General aspects". +- [22] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [23] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [23a] 3GPP TS 44.071: "Location Services (LCS); Mobile radio interface layer 3 Location Services (LCS) specification". +- [23b] 3GPP TS 44.031 "Location Services; Mobile Station (MS) - Serving Mobile Location Centre (SMLC); Radio Resource LCS Protocol (RRLP)". +- [24] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification - Formats and coding". +- [25] (void) +- [26] (void) +- [27] (void) +- [28] (void) +- [29] (void) +- [30] (void) +- [31] (void) +- [32] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [33] 3GPP TS 45.005: "Radio transmission and reception". +- [34] 3GPP TS 45.008: "Radio subsystem link control". +- [35] 3GPP TS 45.010: "Radio subsystem synchronization". +- [36] (void) +- [37] (void) +- [38] (void) +- [39] 3GPP TS 51.010: "Mobile Station (MS) conformance specification". +- [40] (void) +- [41] (void) +- [42] (void) +- [43] (void) +- [44] (void) +- [45] (void) +- [46] (void) +- [47] (void) +- [48] (void) +- [49] (void) + +[50] (void) + +[51] (void) + +[52] (void) + +[53] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic control". + +[54] (void) + +[55] (void) + +[56] (void) + +[57] (void) + +[58] (void) + +[59] (void) + +[60] (void) + +[61] (void) + +[62] (void) + +[63] (void) + +[64] (void) + +[65] (void) + +[66] (void) + +[67] (void) + +[68] (void) + +[69] (void) + +[70] (void) + +[71] (void) + +[72] (void) + +[73] (void) + +[74] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". + +[75] (void) + +[76] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol". + +[77] (void) + +[78] (void) + +[79] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3". + +[80] TIA/EIA/IS-2000-5-A: "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems". + +[81] TIA/EIA/IS-833: "G3G CDMA-MC to GSM-MAP". + +- [88] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification". +- [89] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)". +- [82] TIA/EIA/IS-2000-4-A: "Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems". +- [83] 3GPP TS 45.009: "Link Adaptation". +- [84] 3GPP TS 26.103: "Speech Codec List for GSM and UMTS". +- [85] Michel MOULY, "CSN.1 Specification, Version 2.0", Cell & Sys, ISBN: 2-9510062-0-9. +Web: . +- [86] 3GPP TS 45.003: "Channel Coding". +- [87] 3GPP TS 31.102: "Characteristics of the USIM application". +- [91] 3GPP TS 25.224: "Physical Layer Procedures (TDD)". +- [92] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of speech codecs; stage 3". +- [93] 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2". +- [94] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [95] 3GPP TS 29.280: "3GPP EPS Sv interface (MME to MSC) for SRVCC". +- [96] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [97] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation". +- [98] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [99] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [100] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". +- [101] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [102] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [103] 3GPP TS 23.251: "Network Sharing; Architecture and functional description". +- [104] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [105] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [106] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)". +- [107] 3GPP TS 48.018: "BSS GPRS Protocol (BSSGP)". +- [108] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [109] 3GPP TS 43.064: "Overall description of the GPRS Radio Interface; Stage 2". +- [110] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". + +## 2.1 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. In addition to abbreviations in 3GPP TR 21.905 the following abbreviations apply: + +| | | +|------|---------------------------------------| +| ESAB | Extended Synchronization Access Burst | +| EDAB | Extended Dual slot Access Burst | + +### 2.1.1 Random values + +In a number of places in the present document, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. Such cases interest only the Mobile Station. + +It is required that there is a low probability that two MSs in the same conditions (including the case of two MSs of the same type from the same manufacturer) will choose the same value. Moreover, it is required that, if it happens that two MSs in similar conditions choose the same value, the probability of their choices being identical at the next occasion is the same as if their first choices had been different. + +The meaning of such a specification is that any statistical test for these values, done on a series of similar events, will obtain a result statistically compatible with the specified distribution. This shall hold even in the cases where the tests are conducted with a subset of possible events, with some common parameters. Moreover, basic tests of independence of the values within the series shall pass. + +Data against which correlation with the values shall not be found are the protocol state, or the IMSI, or identities or other unrelated information broadcast by the network, or the current TDMA frame number. + +### 2.1.2 Vocabulary + +The following terms are used in this Technical Specification: + +- idle mode: In this mode, the mobile station is not allocated any dedicated channel; it listens to the CCCH and the BCCH. +- group receive mode: (only applicable for mobile stations supporting VGCS listening or VBS listening) In this mode, the mobile station is not allocated a dedicated channel with the network; it listens to the downlink of a voice broadcast channel or voice group call channel allocated to the cell. Occasionally, the mobile station has to listen to the BCCH of the serving cell as defined in 3GPP TS 23.022 and 3GPP TS 45.008. When talker priority is supported, and the network requires priority talker requests to be signalled on the RACH, the mobile station may temporarily leave the group receive mode, and establish a SDCCH, in order to initiate a priority uplink request. Once the priority uplink request has been sent, the SDCCH is released and the mobile returns to group receive mode. +- dedicated mode: In this mode, the mobile station is allocated at least two dedicated channels, only one of them being a SACCH. +- group transmit mode: (only applicable for mobile stations supporting VGCS talking) In this mode, one mobile station of a voice group call is allocated two dedicated channels, one of them being a SACCH. These channels can be allocated to one mobile station at a time but to different mobile stations during the voice group call. Additionally, when talker priority is supported by the network, further mobile stations may establish RR connections on the group channel in order to initiate an uplink access. +- packet idle mode: (only applicable for mobile stations supporting GPRS services – see 3GPP TS 23.060 [74]) In this mode, mobile station is not allocated any radio resource on a packet data physical channel; it listens to the PBCCH and PCCCH or, if those are not provided by the network, to the BCCH and the CCCH (see 3GPP TS 44.060) or, if the mobile station has enabled EC operation, to the EC-BCCH and the EC-CCCH, see sub-clause 3.10 and 3.5.1a. +- packet transfer mode: (only applicable for mobile stations supporting GPRS services – see 3GPP TS 23.060 [74]) In this mode, the mobile station is allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs. +- dual transfer mode: (only applicable for mobile stations supporting GPRS and DTM) In this mode, the mobile station is allocated radio resources providing an RR connection and one or more Temporary Block Flow + +(3GPP TS 44.060) on one or more physical channels. The allocation of radio resource for the RR connection and the Temporary Block Flows is co-ordinated by the network to comply with the capabilities of the mobile station in dual transfer mode. + +- main DCCH: In Dedicated mode and group transmit mode, only two channels are used as DCCH, one being a SACCH, the other being a SDCCH or a FACCH; the SDCCH or FACCH is called here "the main DCCH". +- A channel is activated if it can be used for transmission, in particular for signalling, at least with UI frames. On the SACCH, whenever activated, it must be ensured that a contiguous stream of layer 2 frames is sent. +- A TCH is connected if circuit mode user data can be transferred. A TCH cannot be connected if it is not activated. A TCH which is activated but not connected is used only for signalling, i.e. as a DCCH. +- The data link of SAPI 0 on the main DCCH is called the main signalling link. Any message specified to be sent on the main signalling link is sent in acknowledged mode except when otherwise specified. +- The term "to establish" a link is a short form for "to establish the multiframe mode" on that data link. It is possible to send UI frames on a data link even if it is not established as soon as the corresponding channel is activated. Except when otherwise indicated, a data link layer establishment is done without an information field. +- "channel set" is used to identify TCHs that carry related user information flows, e.g., in a multislot configuration used to support circuit switched connection(s), which therefore need to be handled together. +- A temporary block flow (TBF) is a physical connection used by the two RR peer entities to support the unidirectional transfer of LLC PDUs on packet data physical channels, see 3GPP TS 44.060. +- RLC/MAC block: A RLC/MAC block is the protocol data unit exchanged between RLC/MAC entities, see 3GPP TS 44.060. + +- A GMM context is established when a GPRS attach procedure is successfully completed. + +- Network operation mode + +The three different network operation modes I, II, and III are defined in 3GPP TS 23.060. + +The network operation mode shall be indicated as system information. For proper operation, the network operation mode should be the same in each cell of one routing area. + +- GPRS MS operation mode + +The three different GPRS MS operation modes A, B, and C are defined in 3GPP TS 23.060. + +- DTM handover is a feature used by the network to command a mobile station to move from its old (source) cell to a new (target) cell while operating in dual transfer mode and continue the operation of its ongoing circuit switched service and one or more of its ongoing packet switched services in the new cell. The mobile station is allocated one circuit switched radio resource and packet switched radio resources applicable to the new cell within a DTM HANDOVER COMMAND message. +- Downlink Dual Carrier is a capability of the mobile station to receive on two radio frequency channels simultaneously. It is only applicable for mobiles which support EGPRS. +- Downlink Multi Carrier is a feature allowing resources for a downlink TBF (and optionally an uplink TBF) to be assigned to a mobile station on two or more radio frequency channels in the same or different frequency bands using EGPRS or EGPRS2-A. +- CSG Cells Reporting + +Refers to the ability of the mobile station to report measurements, CSG-ID and routing parameters of CSG cells in dedicated mode and dual transfer mode. For UTRAN cells, routing parameters include Cell Identity and optionally the PLMN-ID. + +- Extended Access Barring (EAB) is an optional feature used by the network to control whether or not mobile stations configured for EAB are allowed to attempt system access (see 3GPP TS 22.011). When EAB is in use within a given cell a mobile station configured for EAB reads system information to acquire EAB related information which it uses in conjunction with its Access Class (i.e. a single value in the range 0,1, ...9) to determine if it can attempt a system access. + +- Selective Ciphering of Downlink SACCH, when ciphering is started between the network and the mobile station, refers to: + - the mechanism used by the network in downlink to cipher or not to cipher any given individual SACCH block selectively according to its content; and accordingly the ability of the mobile station to decode any given individual SACCH block whether it is ciphered or not. See sub-clause 3.4.7a. +- **Network sharing:** network sharing is an optional feature that allows different core network operators to connect to the same shared radio access network (see 3GPP TS 23.251). When network sharing is in use within a given cell, the network broadcasts within system information the PLMN identities of the PLMNs sharing the cell. A mobile station supporting network sharing uses this information for its PLMN (re)selection processes and indicates the selected PLMN to the BSS. +- **Common PLMN:** when network sharing is in use within a given cell, the Common PLMN refers to the PLMN of which the PLMN ID is broadcast in the SYSTEM INFORMATION TYPE 3 and SYSTEM INFORMATION TYPE 4 messages (as part of the Location Area Identification) and, when EC-GSM-IoT is supported in the cell (see 3GPP TS 43.064 [109], in the EC SYSTEM INFORMATION TYPE 2 message. See sub-clauses 9.1.35, 9.1.36, 9.1.43q and 3GPP TS 23.251, 3GPP TS 24.008. +- **Additional PLMN:** when network sharing is in use within a given cell, an Additional PLMN refers to a PLMN of which the PLMN ID is broadcast in the SYSTEM INFORMATION TYPE 22 message (see sub-clause 10.5.2.37n) and, when EC-GSM-IoT is supported in the cell, in the EC SYSTEM INFORMATION TYPE 4 message (see sub-clause 9.1.43s). +- **Domain-specific access control:** domain-specific access control is an optional feature that allows the network to send, on a PLMN specific basis, different access control information for the CS and PS domains (see 3GPP TS 22.011). A mobile station supporting domain-specific access control uses this information for its access control check process. Support of domain-specific access control is possible only if network sharing is supported. +- IP Multimedia Subsystem (IMS) + - The IP Multimedia Subsystem comprises all CN elements for provision of IP multimedia services, see 3GPP TS 23.228 [104]. +- Single Radio Voice Call Continuity (SRVCC) + - refers to voice call continuity between IMS over PS access and CS access for calls that are anchored in IMS when the MS is capable of transmitting/receiving on only one of those access networks at a given time; a mobile station supporting SRVCC is enhanced for IMS Service Continuity with the additional MS capabilities described in 3GPP TS 23.216 for SRVCC from E-UTRAN to UTRAN (HSPA) or GERAN or from UTRAN (HSPA) to E-UTRAN or GERAN or from GERAN to E-UTRAN or UTRAN (HSPA). SRVCC from GERAN to E-UTRAN or UTRAN (HSPA) is known also as CS to PS SRVCC. +- Extended EARFCNs + - refers to extended EARFCN value range (0 ...262143) with EARFCNs coded over 18 bits. Mobile station and network support of extended EARFCNs is mandatory when network sharing is supported; support of extended EARFCNs is optional otherwise. +When network sharing is in use within a given cell, the network shall provide extended EARFCNs within the SYSTEM INFORMATION TYPE 23 message, if broadcasted in the cell; additionally when extended EARFCNs is in use within a given cell, the network may provide at least one EARFCN value > 65535 within the SYSTEM INFORMATION TYPE 2quater message. +- **Power Efficient Operation (PEO):** See 3GPP TS 43.064 [109] +- **Coverage Class:** See 3GPP TS 43.064 [109] +- **EC operation:** See 3GPP TS 43.064 [109] +- **1TS EC-RACH:** Mapping of the EC-RACH logical channel using one timeslot where EC PACKET CHANNEL REQUEST messages are sent by mobile stations, see 3GPP TS 45.002 [32] +- **2TS EC-RACH:** Mapping of the EC-RACH logical channel using two timeslots where EC PACKET CHANNEL REQUEST messages are sent by mobile stations, see 3GPP TS 45.002 [32] + +- **Multilateration Timing Advance (MTA)**: See 3GPP TS 43.059 [12a] +- **Multilateration Observed Time Difference (MOTD)**: See 3GPP TS 43.059 [12a] + +--- + +## 3 Radio Resource management procedures + +### 3.1 Overview/General + +#### 3.1.1 General + +Radio Resource management procedures include the functions related to the management of the common transmission resources, e.g. the physical channels and the data link connections on control channels. + +The general purpose of Radio Resource procedures is to establish, maintain and release RR connections that allow a point-to-point dialogue between the network and a mobile station. This includes the cell selection/reselection and the handover procedures. Moreover, Radio Resource management procedures include the reception of the uni-directional BCCH and CCCH when no RR connection is established. This permits automatic cell selection/reselection. + +If VGCS listening or VBS listening are supported, the radio resource management also includes the functions for the reception of the voice group call channel or the voice broadcast channel, respectively, and the automatic cell reselection of the mobile station in Group receive mode. + +If VGCS talking is supported, the radio resource management also includes the functions for the seizure and release of the voice group call channel. + +If GPRS point-to-point services are supported, the radio resource management procedures includes functions related to the management of transmission resources on packet data physical channels. This includes the broadcast of system information to support a mobile station in packet idle and packet transfer modes, see also 3GPP TS 44.060. + +NOTE 1: This chapter includes some procedures used for multislot operation and for the TCH/H + TCH/H configuration which need not be supported by simple mobile stations. + +NOTE 2: The procedures and the information content relating to the TCH/H + TCH/H configuration in RR messages is for further study. + +If dedicated mode MBMS Notification is supported, the radio resource management procedures includes functions to allow the announcement of the starting MBMS services. + +#### 3.1.2 Services provided to upper layers + +A RR connection is a physical connection used by the two peer entities to support the upper layers' exchange of information flows. + +##### 3.1.2.1 Idle mode + +In idle mode no RR connection exists. + +The RR procedures include (on the mobile station side) those for automatic cell selection/reselection. The RR entity indicates to upper layers the unavailability of a BCCH/CCCH and the cell change when decided by the RR entity. Upper layers are advised of the BCCH broadcast information when a new cell has been selected, or when a relevant part of this information changes. + +For cell-reselection the BA (list), together with the 3G Cell Reselection list and/or the E-UTRAN Neighbour Cell list for a multi-RAT MS, shall be used. + +In Idle mode, upper layers can require the establishment of an RR connection. + +### 3.1.2.2 Dedicated mode + +In dedicated mode, the RR connection is a physical point-to-point bi-directional connection, and includes a SAPI 0 data link connection operating in multiframe mode on the main DCCH. If dedicated mode is established, RR procedures provide the following services: + +- establishment/release of multiframe mode on data link layer connections other than SAPI 0, on the main DCCH or on the SACCH associated with the channel carrying the main signalling link; +- transfer of messages on any data link layer connection; +- indication of temporary unavailability of transmission (suspension, resuming); +- indication of loss of RR connection; +- automatic cell reselection and handover to maintain the RR connection; +- setting/change of the transmission mode on the physical channels, including change of type of channel, change of the coding/decoding/transcoding mode and setting of ciphering; +- allocation/release of an additional channel (for the TCH/H + TCH/H configuration); +- allocation/release of additional channels for multislot operation; +- release of an RR connection. + +### 3.1.2.3 Group receive mode + +Only applicable for mobile stations supporting VGCS listening or VBS listening. + +In this mode, the RR procedures on the mobile station side provide the services: + +- local connection to the voice broadcast channel or voice group call channel; +- reception of messages in unacknowledged mode; +- automatic cell reselection for the mobile station in Group receive mode; +- uplink reply procedure to indicate that the mobile station is listening to the voice group call or voice broadcast call; +- local disconnection from the received voice group call or broadcast call channels. + +For mobile stations supporting both VGCS listening and VGCS transmit, in addition, the RR procedures on the mobile station side provide the service: + +- uplink access procedures to establish the RR connection; +- priority uplink request procedures to establish the RR connection, if talker priority is supported by the mobile station. +- Uplink access procedures to establish the RR connection for sending application-specific data to the network + +### 3.1.2.4 Group transmit mode + +Only applicable for mobile stations supporting VGCS talking. + +In group transmit mode, the RR connection is a physical point-to-point bi-directional connection, and includes a SAPI 0 and possibly a SAPI 3 data link connection(s) operating in multiframe mode on the main DCCH. If the group transmit mode is established, RR procedures provide the following services: + +- transfer of messages on the SAPI 0 and optionally on the SAPI 3 of the data link layer connection; +- indication of loss of RR connection; +- automatic cell reselection and handover to maintain the RR connection; + +- setting of the transmission mode on the physical channels, change of type of channel and setting of ciphering; +- release of the RR connection. + +### 3.1.2.5 Packet idle mode + +Only applicable for mobile stations supporting GPRS. + +In packet idle mode, no temporary block flow exists (see 3GPP TS 44.060). Upper layers may require the transfer of a LLC PDU, which implicitly triggers the establishment of a temporary block flow. + +### 3.1.2.6 Packet transfer mode + +Only applicable for mobile stations supporting GPRS. + +In packet transfer mode, the mobile station is allocated radio resources providing a temporary block flow on one or more packet data physical channels. If the mobile station supports Downlink Dual Carrier, these physical channels may be on different radio frequency channels for a DLMC configuration (see 3GPP TS 24.008). If the mobile station supports Downlink Multi Carrier, these physical channels may be on different radio frequency channels in the same or in different frequency bands for a DLMC configuration (see 3GPP TS 24.008). The RR sublayer provides the following services, see also 3GPP TS 44.060: + +- transfer of LLC PDUs in acknowledged mode; +- transfer of LLC PDUs in unacknowledged mode. + +Depending on the GPRS mode of operation (class A or B), the mobile station may leave both packet idle mode and packet transfer mode before entering dedicated mode, group receive mode or group transmit mode. + +Cell reselection in packet idle and packet transfer modes is specified in 3GPP TS 45.008. The RR entity on the mobile station side indicates to the upper layers the availability of a cell and a cell change when decided by the RR sublayer. Upper layers are advised of system information broadcast in the cell when a new cell has been selected, or when a relevant part of this information changes. + +### 3.1.2.7 Dual transfer mode (DTM) + +In dual transfer mode, the mobile station is simultaneously in dedicated mode and in packet transfer mode. This feature is optional for the mobile station and the network. It is only applicable for a mobile station supporting GPRS, EGPRS or EGPRS2. Dual transfer mode is a subset of class A mode of operation, only possible if there is radio resource allocation co-ordination in the network. Simultaneous handover of resources to maintain the RR connection and the temporary block flows (see 3GPP TS 44.060) may occur in dual transfer mode if both the mobile station and the network support DTM handover (see sub-clause 3.7). DLMC configuration is not supported in DTM. + +## 3.1.3 Services required from data link and physical layers + +The RR sublayer uses the services provided by the data link layer as defined in 3GPP TS 44.005. + +Moreover, the RR sublayer directly uses services provided by the physical layer such as BCCH searching and transfer of RLC/MAC blocks, as defined in 3GPP TS 44.004. + +## 3.1.4 Change of dedicated channels + +### 3.1.4.1 Change of dedicated channels using SAPI = 0 + +In case a change of dedicated channels is required using a dedicated assignment and handover procedure, respectively, the RR sublayer will request the data link layer to suspend multiple frame operation before the mobile station leaves the old channel. When the channel change has been completed, layer 3 will request the data link layer to resume multiple frame operation again. The layer 2 suspend/resume procedures are described in 3GPP TS 44.005 and 3GPP TS 44.006. + +These procedures are specified in such a way that a loss of a layer 3 message cannot occur on the radio interface. However, messages sent from the mobile station to the network may be duplicated by the data link layer if a message has been transmitted but not yet completely acknowledged before the mobile station leaves the old channel (see 3GPP TS 44.006). + +As the RR sublayer is controlling the channel change, a duplication of RR messages does not occur. However, there are some procedures for which a duplication is possible, e.g. DTMF procedures. For all upper layer procedures using the transport service of the GSM RR sub-layer (e.g., MM and CM procedures but not GMM or Session Management procedures), the request messages sent by the mobile station contain a sequence number in order to allow the network to detect duplicated messages, which are then ignored by the network. The same sequence number is used to protect against message duplication caused by channel changes between GSM and UTRAN and also by other UTRAN procedures (e.g. hard handover). The procedures for sequenced transmission on layer 3 are described in 3GPP TS 24.007. + +### 3.1.4.2 Change of dedicated channels using other SAPIs than 0 + +For SAPIs other than 0, the data link procedures described in 3GPP TS 44.006 do not provide any guarantee against message loss or duplication. + +Therefore, if an application uses a SAPI other than 0 and if this application is sensitive to message loss or duplication, then it has to define its own protection mechanism. No general protection mechanism is provided by the protocol defined in this Technical Specification. + +### 3.1.5 Procedure for Service Request and Contention Resolution + +Upon seizure of the assigned dedicated channel or group channel, the mobile station establishes the main signalling link on this channel by sending a layer 2 SABM frame containing a layer 3 service request message. The data link layer will store this message to perform the contention resolution. The service request message will be returned by the network in the UA frame. + +The data link layer in the mobile station compares the content of the information field (i.e. the layer 3 service request message) received in the UA frame with the stored message and leaves the channel in case they do not match. This procedure resolves contentions in the case where several mobile stations have accessed at the same random access slot and with the same random reference and one has succeeded due to capture. The full description of the procedure is given in 3GPP TS 44.006. + +NOTE: When this procedure is used to respond to an encapsulated IMMEDIATE ASSIGNMENT message or an encapsulated DTM ASSIGNMENT message (see sub-clause 3.6), random access and contention resolution are not used. + +The purpose of the service request message is to indicate to the network which service the mobile station is requesting. This then allows the network to decide how to proceed (e.g. to authenticate or not). + +The service request message must contain the identity of the mobile station and may include further information which can be sent without encryption. + +The layer 3 service request message is typically one of the following: + +- CM SERVICE REQUEST; +- LOCATION UPDATING REQUEST; +- IMSI DETACH; +- PAGING RESPONSE; +- CM RE-ESTABLISHMENT REQUEST; +- NOTIFICATION RESPONSE; +- IMMEDIATE SETUP. + +If talker priority is supported, the layer 3 service request message may be: + +- PRIORITY UPLINK REQUEST. + +If VGCS talking is supported, the layer 3 service request message may be: + +- TALKER INDICATION (applicable only to seizure of a group channel) + +If sending application-specific data is supported, the layer 3 service request message may be: + +- DATA INDICATION +- DATA INDICATION 2 + +![Diagram illustrating Service request and contention resolution between a mobile station and a network. The mobile station sends a SABM ('layer 3 service request message') to the network. The network responds with a UA ('layer 3 service request message') back to the mobile station.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +``` + + graph LR + subgraph mobile_station [mobile station] + SABM[SABM ("layer 3 service request message")] + end + subgraph network [network] + UA[UA ("layer 3 service request message")] + end + SABM --> UA + +``` + +Diagram illustrating Service request and contention resolution between a mobile station and a network. The mobile station sends a SABM ('layer 3 service request message') to the network. The network responds with a UA ('layer 3 service request message') back to the mobile station. + +**Figure 3.1.5.1: Service request and contention resolution** + +### 3.1.6 Preemption + +The datalink layer provides the capability to assign a priority to any message transferred in dedicated mode on SAPI 0 with multiframe operation. The available message priorities defined in 3GPP TS 44.006 are "high", "normal" and "low". Messages assigned a "high" priority are enabled to preempt, in the data link layer, all preceeding untransmitted and partially transmitted messages assigned a "low" priority that are using the same data link connection (same SAPI and logical channel). Messages or message portions that are preempted are discarded without notification to higher layers except that the first $2^N \cdot N_{201}$ octets of any partially transmitted message are not discarded. The following priority assignments are defined for those Radio Resource, Mobility Management and Connection Management messages that use SAPI 0. + +**Table 3.1.6.1: Priority Values of Layer 3 Messages** + +| Priority | Messages | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Low | RR Application Information message (see NOTE 1) | +| Normal | All MM messages
All CM messages
All GTTP messages
All other RR messages using SAPI 0 not listed here | +| High | ETWS Primary Notification:
APPLICATION INFORMATION message containing an APDU
ID of type ETWS (see sub-clause 10.5.2.48).

RR Channel Establishment:
ADDITIONAL ASSIGNMENT

RR Configuration Change:
CONFIGURATION CHANGE COMMAND

RR Handover related
ASSIGNMENT COMMAND
HANDOVER COMMAND

RR Channel release
CHANNEL RELEASE
PARTIAL RELEASE | + +NOTE 1: An Application Information message conveying an ETWS Primary Notification message (see sub-clause 10.5.2.48) is treated as a "high" priority message. + +Use of the preemption capability by layer 3 is not required in a BSS or MS that does not send any "low" priority message. In this case, all messages may be treated as having "normal" priority. + +Preemption capabilities in Layer 3 is not applicable to the Uplink messages, hence all Uplink messages are treated with "normal" priority. Note that the "Suspension and Resumption of Multiple frame operation" (See 3GPP TS 44.006) will affect the order in which the layer 3 messages are delivered on the Uplink. + +## 3.2 Idle mode procedures and general procedures in packet idle and packet transfer modes + +### 3.2.1 Mobile Station side + +In idle mode, the MS listens to the BCCH or EC-BCCH and to the paging sub-channel for the paging group the MS belongs to in idle mode (cf. 3GPP TS 43.013); it measures the radio propagation for connection with other cells. + +In packet idle and packet transfer modes (applicable only to a GPRS mobile station) the mobile station listens to either the PBCCH, if that is present in the cell, or BCCH. The requirements for the monitoring of system information is further specified in 3GPP TS 45.008 [34]. An exception case is where a mobile station has enabled PEO or EC operation in which case the following applies: + +- A MS that has enabled PEO shall monitor system information on the BCCH, when in packet idle mode, as described in sub-clause 3.9. +- A MS that has enabled EC operation shall monitor system information on the EC-BCCH, when in packet idle mode, as described in sub-clause 3.10. + +Moreover, the mobile station measures the radio propagation for connection with other cells. A MS that has enabled PEO or EC operation shall only measure the radio propagation for connection with other cells when the serving cell is no longer determined to be suitable (see 3GPP TS 45.008 [34]). + +A mobile station camping on the cell as a result of a cell change order or redirection from E-UTRAN to GERAN is not required to perform the complete acquisition of the system information of the cell on BCCH before proceeding with a RR connection establishment (see sub-clause 3.3). + +The mobile station shall perform the acquisition on the BCCH of the cell of the following messages if not provided in the *MobilityFromEUTRACommand* or, respectively, in the E-UTRA *RRConnectionRelease* message and the mobile station is not performing CS fallback (see 3GPP TS 36.331): + +- SYSTEM INFORMATION TYPE 3, +- for a GPRS capable mobile station in a cell supporting GPRS, SYSTEM INFORMATION TYPE 13, and +- SYSTEM INFORMATION TYPE 1 if broadcast in the cell (see 3GPP TS 45.002). + +The mobile station shall perform the acquisition on the BCCH of the cell of the following messages if not provided in the E-UTRA *RRConnectionRelease* message and the mobile station is performing CS fallback (see 3GPP TS 36.331): + +- SYSTEM INFORMATION TYPE 3, +- SYSTEM INFORMATION TYPE 1 if broadcast in the cell (see 3GPP TS 45.002). + +If SYSTEM INFORMATION TYPE 3 and, for a GPRS capable mobile station in a cell supporting GPRS, SYSTEM INFORMATION TYPE 13 were received in the *MobilityFromEUTRACommand* message or in the E-UTRA *RRConnectionRelease* message but SYSTEM INFORMATION TYPE 1 was not included, the mobile station shall assume that SYSTEM INFORMATION TYPE 1 is not broadcast in the cell. + +In packet idle mode (applicable only to a GPRS mobile station ), a mobile station listens to the paging sub-channels on the PCCCH or CCCH. An exception case is where a mobile station has enabled PEO or EC operation in which case the following applies: + +- A MS that has enabled PEO listens to its paging sub-channel (nominal paging group) on the CCCH as described in sub-clause 3.9. +- A mobile station that has enabled EC operation listens to its paging sub-channel (nominal paging group) on the EC-CCCH as described in sub-clause 3.10. + +Paging sub-channels are monitored according to the paging group determined for the mobile station, its current discontinuous reception (DRX) mode and in case EC operation has been enabled, its current downlink Coverage Class. The determination of paging group for the mobile station is defined in 3GPP TS 45.002. The DRX procedures are defined in 3GPP TS 44.060 and 3GPP TS 45.002. + +Mobile station support for reception of Earthquake and Tsunami Warning System (ETWS) Primary Notification messages is optional. In idle mode or in packet idle mode (applicable only to a GPRS mobile station), the mobile station may determine that an ETWS event has occurred (see sub-clause 3.2.2.3 and 9.1.22) in which case it shall leave DRX mode, start timer T3232, start reading all paging groups and attempt to acquire an ETWS Primary Notification message. The mobile station shall attempt to assemble all segments of the ETWS Primary Notification message, having the same Primary Notification Identifier (PNI) value, before delivering the complete message to the upper layers. + +While attempting to acquire the ETWS Primary Notification message a mobile station shall continue to follow (packet) idle mode and connection establishment procedures. Upon initiating cell reselection or connection establishment procedures while attempting to acquire an ETWS Primary Notification message, a mobile station shall discard any partially received ETWS Primary Notification message and stop timer T3232. The mobile station shall not attempt to acquire an ETWS Primary Notification message while performing a connection establishment procedure or while performing cell reselection. + +If the mobile station detects a change in the PNI value prior to acquiring a complete ETWS Primary Notification message, it shall abort the current message, restart timer T3232 and attempt to acquire the new message. + +When the mobile station successfully acquires a complete ETWS Primary Notification message it shall stop timer T3232 and enter DRX mode. If timer T3232 expires the mobile station shall abort the current message and enter DRX mode. + +A UTRAN capable mobile station in idle mode or packet idle mode attempts to read predefined configuration information from UTRAN Channels, as specified in 3GPP TS 45.008. This is only applicable to a mobile station supporting circuit-switched services. + +Measurements are treated to assess the need of a cell change as specified in 3GPP TS 45.008. When the decision to change cells is made, the mobile station switches to the BCCH, PBCCH or EC-BCCH of the new cell. The broadcast information is then checked to verify the allowance to camp on this cell (cf. sub-clause 3.2.2). Dependent on the mobile station type and configuration, the mobile station may be required to try to read further BCCH or PBCCH or EC-BCCH information. If allowed, the cell change is confirmed, and the broadcast information is then treated for Mobility Management actions (cf. clause 4). Similarly, physical contexts are updated (list of neighbouring cells frequencies, thresholds for some actions, etc. (cf. 3GPP TS 45.008 and sub-clause 3.2.2)). + +A mobile station configured for Extended Access Barring (EAB) shall read the SI3 Rest Octets IE in an attempt to determine if the SYSTEM INFORMATION TYPE 21 message is sent in the cell. If the SI3 Rest Octets IE does not provide this information the mobile station shall read the SI9 Rest Octets IE to make this determination (If SI 9 is sent): + +- If the SYSTEM INFORMATION TYPE 21 message is sent the mobile station shall read it in an attempt to acquire EAB information (see sub-clause 10.5.2.37m). +- If the SYSTEM INFORMATION TYPE 21 message is not sent or is sent but does not include EAB information the mobile station shall consider EAB information it may have previously received to be invalid. + +A mobile station that has enabled EC operation is not subject to Extended Access Barring (EAB) and shall instead use information sent in the EC SYSTEM INFORMATION TYPE 2 message and in the EC-SYSTEM INFORMATION type 4 message (if network sharing is supported in the cell) to determine the PLMN specific barring in effect for the serving cell. When attempting packet access it uses the PLMN specific barring and potentially the Implicit Reject Status (IRS) information sent using the EC-SCH INFORMATION message (see sub-clause 9.1.30c) to determine if packet access is allowed (see sub-clause 3.5.2a). + +A mobile station supporting network sharing that has not enabled EC operation shall read the SYSTEM INFORMATION TYPE 3 message in an attempt to determine if the SYSTEM INFORMATION TYPE 22 message is sent in the cell: + +- If the SYSTEM INFORMATION TYPE 22 message is sent the mobile station shall read it in an attempt to acquire network sharing information (see sub-clause 10.5.2.37n). +- If the SYSTEM INFORMATION TYPE 22 message is not sent or is sent but does not include network sharing information the mobile station shall consider network sharing as not supported in the cell and the network sharing information it may have previously received to be invalid. + +A UTRAN and/or E-UTRAN capable mobile station supporting network sharing shall read the SYSTEM INFORMATION TYPE 22 message in an attempt to determine if the SYSTEM INFORMATION TYPE 23 message is sent in the cell: + +- If the SYSTEM INFORMATION TYPE 23 message is sent the mobile station shall read it in an attempt to acquire UTRAN and/or E-UTRAN information for cell-reselection (as applicable) as described in sub-clause 10.5.2.37o. +- If the SYSTEM INFORMATION TYPE 23 message is sent but does not include UTRAN and/or E-UTRAN information for cell-reselection the mobile station shall consider UTRAN and/or E-UTRAN information for cell-reselection as not available in the cell and the previous information it may have received to be invalid. +- If the SYSTEM INFORMATION TYPE 23 message is not sent the mobile station shall acquire UTRAN and/or E-UTRAN information for cell-reselection from the SI2ter/SI2quater messages. + +A mobile station that has enabled EC operation shall read the EC SYSTEM INFORMATION TYPE 3 message in an attempt to determine if the EC SYSTEM INFORMATION TYPE 4 message is sent in the cell: + +- If the EC SYSTEM INFORMATION TYPE 4 message is sent the mobile station shall read it in an attempt to acquire network sharing information (see sub-clause 9.1.43s). +- If the EC SYSTEM INFORMATION TYPE 4 message is not sent or is sent but does not include network sharing information the mobile station shall consider network sharing as not supported in the cell and the network sharing information it may have previously received to be invalid. + +## 3.2.2 Network side + +### 3.2.2.1 System information broadcasting + +SYSTEM INFORMATION TYPE 2 to 4 messages, and optionally TYPE 1, 2bis, 2ter, 7, 8, 13, 16 and 17 and further types are regularly broadcast by the network on the BCCH. Based on this information the mobile station is able to decide whether and how it may gain access to the system via the current cell. The SYSTEM INFORMATION TYPE 2bis message shall be sent if and only if the EXT-IND bit in the Neighbour Cell Description IE in both the TYPE 2 and TYPE 2bis messages indicates that each IE only carries part of the BA. SYSTEM INFORMATION TYPE 2ter message shall be sent if and only if this is indicated in SYSTEM INFORMATION TYPE 3 message. + +A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may consider the EXT-IND bit in the Neighbour Cell Description IE in the SYSTEM INFORMATION TYPE 2 message as a spare bit. If it does so it shall assume that the information element carries the complete BA and it shall ignore any SYSTEM INFORMATION TYPE 2bis and 2ter messages. + +SYSTEM INFORMATION TYPE 2quater messages may be sent to provide further information for Enhanced Measurement Report. It may also include UTRAN and/or E-UTRAN information for cell-reselection, measurement and reporting. A mobile station with no UTRAN capability should ignore 3G related information in this message. A mobile station with no E-UTRAN capability should ignore E-UTRAN related information in this message. SYSTEM INFORMATION TYPE 2quater message shall be sent if and only if this is indicated in SYSTEM INFORMATION TYPE 3 message. + +The SI2ter Rest Octet information element in the SI2ter message may provide information on UTRAN Cells and 3G Measurement Parameters. Information received in this message is only used for cell reselection in idle mode. The SYSTEM INFORMATION TYPE 2ter messages shall contain at least one 2G neighbouring cell description the ARFCN of which does not belong to the frequency band of the 2G neighbouring cells described in the SYSTEM INFORMATION TYPE 2 message. + +When the SI2ter\_MP\_CHANGE\_MARK parameter is changed in this information element, the MS shall re-read 3G Measurement parameters in all instances of SI2ter (by using SI2ter\_INDEX and SI2ter\_COUNT). When the SI2ter\_3G\_CHANGE\_MARK is changed in this information element, the MS shall re-read UTRAN FDD Description and UTRAN TDD Description in all instances of SI2ter (by using SI2ter\_INDEX and SI2ter\_COUNT). + +SYSTEM INFORMATION TYPE 2n messages may be sent to provide parameters affecting cell reselection for the neighbouring cells. SYSTEM INFORMATION TYPE 2n message shall be sent on BCCH (Ext) if and only if this is indicated in SYSTEM INFORMATION TYPE 13 message. + +When the SI2n\_CHANGE\_MARK parameter is changed in this message, the MS shall re-read all the parameters in SI2n Rest Octets IE in a full set of SYSTEM INFORMATION 2n messages. + +If the additional cell reselection parameters are broadcast then SYSTEM INFORMATION TYPE 3 message shall always contain these parameters. In addition to SYSTEM INFORMATION TYPE 3 at least either SYSTEM + +INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages shall contain these parameters too. SYSTEM INFORMATION TYPE 7 and 8 messages shall be sent if and only if this is indicated in SYSTEM INFORMATION TYPE 4 message. + +SYSTEM INFORMATION TYPE 15 message is broadcast if dynamic ARFCN mapping is used in the PLMN. In this case ARFCN values are allocated and dynamically mapped to physical frequencies, see 3GPP TS 45.005. The presence of dynamic ARFCN mapping shall be indicated in Cell Options (BCCH) IE. When the value of the parameter DM\_CHANGE\_MARK is changed in the SYSTEM INFORMATION TYPE 15 message, the mobile station shall re-read information on dynamic mapping in a full set of SYSTEM INFORMATION 15 messages. + +After the release of a dedicated connection, when returning to idle mode or packet idle mode, the mobile station may keep the dynamic ARFCN mapping information for the PLMN of the chosen cell under the following conditions: + +- there has not been any handover during the connection; or +- the mobile station chooses the last cell (identified by the BCCH carrier and BSIC) that was used during the connection and there has not been any handover including dynamic ARFCN mapping information after reception of the dynamic ARFCN mapping information. + +Otherwise, the mobile station shall acquire new dynamic ARFCN mapping information. + +If additional SoLSA specific parameters are broadcast then SYSTEM INFORMATION TYPE 16 and 17 messages, shall always contain these parameters. In addition to SYSTEM INFORMATION TYPE 16 and 17 messages at least either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages shall contain these SoLSA specific parameters too. SYSTEM INFORMATION TYPE 16 and 17 messages shall be sent if and only if this is indicated in SYSTEM INFORMATION TYPE 3 message. The SoLSA information of any SYSTEM INFORMATION message shall be the same. + +The SYSTEM INFORMATION TYPE 18 and 20 messages are sent when non-GSM broadcast information must be transmitted. The scheduling and repetition rate of these messages is determined by the system operator and is indicated in SYSTEM INFORMATION TYPE 9 message. Mobile stations without non-GSM capabilities defined for SI 18 and SI 20 should ignore these messages. An MS with non-GSM capabilities shall decode and identify information related to the respective Non-GSM protocol by reading the Non-GSM Protocol Discriminator field. + +The SYSTEM INFORMATION TYPE 21 message is broadcast by the network if Extended Access Barring is in use in the cell. + +The SYSTEM INFORMATION TYPE 22 message shall be broadcast by the network if network sharing (with or without domain-specific access control) is in use in the cell. The presence of SI 22 messages shall be indicated in SI 3 message. Additionally, in this case, the network may broadcast the SYSTEM INFORMATION TYPE 23 message to provide PLMN-specific UTRAN and/or E-UTRAN information for cell re-selection. The presence of SI 23 messages shall be indicated in SI 22 message. + +SYSTEM INFORMATION TYPE 19 messages shall be provided if COMPACT neighbour cells exist (see 3GPP TS 45.008). The presence of SI 19 messages shall be indicated in SI 9 message. + +The support of GPRS shall be indicated in SYSTEM INFORMATION TYPE 3 message. In addition, the support of GPRS shall be indicated in either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages. If GPRS is supported, SYSTEM INFORMATION TYPE 13 message shall be sent. SI 13 message shall not be sent if GPRS is not supported. Additional requirements for the broadcast of system information in a cell supporting GPRS are specified in 3GPP TS 44.060. + +If EC-GSM-IoT is supported in the cell then EC SYSTEM INFORMATION TYPE 1, 2 and 3 messages are regularly broadcast by the network on the EC-BCCH. Based on this information a mobile station that has enabled EC operation able to decide whether and how it may gain access to the system via the current cell. + +EC SYSTEM INFORMATION TYPE 4 message is optionally broadcast by the network if EC-GSM-IoT and network sharing is supported in the cell. The presence of EC SYSTEM INFORMATION TYPE 4 message shall be indicated in the EC SYSTEM INFORMATION TYPE 3 message. + +NOTE 1: The allowed scheduling of SYSTEM INFORMATION messages on the BCCH and EC SYSTEM INFORMATION messages on the EC-BCCH are specified in 3GPP TS 45.002. + +NOTE 2: The network should take into account limitations of certain mobile stations to understand SYSTEM INFORMATION TYPE 2bis, TYPE 2ter, the EXT-IND bit in the Neighbour Cell Description, the indication of 2ter in SYSTEM INFORMATION TYPE 3 and formats used in the Neighbour Cell Description IE and Cell Channel Description IE used in SYSTEM INFORMATION messages, see this sub-clause, sub-clause 10.5.2.1b, and sub-clause 10.5.2.22. + +NOTE 3: The network should take into account the limitations of earlier versions of mobile equipment to understand the 3-digit MNC format of the location area identification, see sub-clause 10.5.1.3. + +The information broadcast may be grouped in the following classes: + +- information giving unique identification of the current network, location area and cell; +- information used for candidate cell measurements for handover and cell selection procedures; +- information describing the current control channel structure; +- information controlling the random access channel utilization; +- information defining different options supported within the cell; and +- information about the length of the part of the message belonging to the phase 1 protocol. + +The network may send to the mobile station BCCH scheduling information as specified below: + +- 1) The BCCH scheduling information may be contained in the SYSTEM INFORMATION TYPE 9 messages. If so, SYSTEM INFORMATION TYPE 3 specifies where to find SYSTEM INFORMATION TYPE 9 messages carrying BCCH scheduling information. +- 2) If the mobile station has received BCCH scheduling information, it shall assume that this BCCH scheduling information is valid in the location area until new scheduling information is received. It may store the information in the ME and assume its validity after switch on in the same location area. +- 3) The network need not indicate the schedule of all SYSTEM INFORMATION messages in SYSTEM INFORMATION 9. For any System Information message, the MS shall monitor all blocks specified in 3GPP TS 45.002 for that System Information message and all blocks specified in the SYSTEM INFORMATION TYPE 9 message for that System Information message. +- 4) When the mobile station detects that the BCCH information is not scheduled as defined in the last received SI 9 message, it shall read the SYSTEM INFORMATION TYPE 3 message. If presence of BCCH scheduling information in SYSTEM INFORMATION TYPE 9 message is indicated, it shall try to read the information and continue as in 2 above. If presence of BCCH scheduling information in SYSTEM INFORMATION TYPE 9 message is not indicated, it shall assume that there is no valid BCCH scheduling information. + +### 3.2.2.2 Paging + +The network is required to send valid layer 3 messages continuously on all paging subchannels on CCCH. + +### 3.2.2.3 Sending of ETWS Primary Notification + +The network initiates the delivery of an ETWS Primary Notification message (see 3GPP TS 23.041) by broadcasting the PAGING REQUEST TYPE 1 message on all paging subchannels on CCCH with the ETWS Primary Notification field present within the P1 Rest Octets IE. These paging messages are sent continuously during the ETWS warning period. + +Each paging message carries a segment of the actual ETWS Primary Notification message, i.e. segmentation is applicable if an ETWS Primary Notification message is too large to fit into the P1 Rest Octets of a single PAGING REQUEST TYPE 1 message. In order to allow a mobile station to receive the segments in any order, the size of a specific segment (retransmitted during the ETWS warning period) shall not be altered. Segments belonging to the same ETWS Primary Notification message shall be given the same Primary Notification Identifier (PNI) value. + +### 3.2.3 Inter-RAT cell re-selection based on priority information + +#### 3.2.3.1 General + +The network may provide priority information to enable priority-based cell reselection (see 3GPP TS 45.008). Inter-RAT cell reselection based on priority information applies only in case of autonomous cell reselection. + +Two sets of priorities are defined for inter-RAT cell re-selection based on priority information: common priorities (see sub-clause 3.2.3.2) and individual priorities (see sub-clause 3.2.3.3). The mobile station shall delete all priorities when switched off. + +While providing common or individual priorities, the network shall ensure that the GERAN priority value is different from all E-UTRAN priority values and from all UTRAN priority values, and that all UTRAN priority values are different from all E-UTRAN priority values. In addition, if for some E-UTRAN frequencies THRESH\_E-UTRAN\_high\_Q is provided in the *Enhanced Cell Reselection Parameters Description* IE in the SI2quater message or, if network sharing is supported by the network (see sub-clause 3.8), in the SI23 message, the network shall ensure that the priority value for any frequency for which THRESH\_E-UTRAN\_high\_Q is provided is different from the priority value for all frequencies for which THRESH\_E-UTRAN\_high\_Q is not provided. + +The mobile station shall determine each set, considering only individual priorities (respectively common priorities) when building the set of individual (respectively common) priorities. The mobile station shall perform the following steps, in the specified order: + +- If the same priority value is assigned to GERAN and to one or more UTRAN or E-UTRAN frequencies then all such UTRAN and E-UTRAN priority values are considered as not in the set of priorities. +- If the same priority value is assigned to one or more UTRAN frequencies and one or more E-UTRAN frequencies, then all such priority values are considered as not in the set of priorities. +- If the same priority value is assigned to one or more E-UTRAN frequencies for which THRESH\_E-UTRAN\_high\_Q is provided and one or more E-UTRAN frequencies for which THRESH\_E-UTRAN\_high\_Q is not provided then all such priority values are considered as not in the set of priorities. + +NOTE 1: These steps mean that if, for example, there are two UTRAN priority values, one E-UTRAN priority value (for a frequency for which THRESH\_E-UTRAN\_high\_Q is provided) and one E-UTRAN priority value (for a frequency for which THRESH\_E-UTRAN\_high\_Q is not provided) that are all the same, then all four priority values are considered as not in the set of priorities. + +A set of individual priorities is valid if it contains at least one priority. + +A set of common priorities is valid if both of the following conditions are met: + +- The set of priorities includes a priority for GERAN; +- The mobile station does not have a valid set of individual priorities. + +If the mobile station has a valid set of priorities, the priorities in this set shall be used for priority-based reselection as specified in 3GPP TS 45.008. + +NOTE 2: It is possible that individual priorities inherited from UTRAN or E-UTRAN (see sub-clause 3.2.3.3) do not contain a priority for GERAN. + +#### 3.2.3.2 Common priorities information + +A mobile station may receive common priorities information in the *Priority and E-UTRAN Parameters Description* IE in the SYSTEM INFORMATION TYPE 2quater message. + +A mobile station supporting network sharing may receive PLMN specific UTRAN and E-UTRAN common priorities in the SYSTEM INFORMATION TYPE 23 message. If the SYSTEM INFORMATION TYPE 23 message is broadcast in the cell, a mobile station supporting network sharing shall use only UTRAN and E-UTRAN common priorities if provided in this message. + +### 3.2.3.3 Provision of individual priorities information + +A mobile station shall store individual priorities information if received in the *Individual Priorities* IE in the CHANNEL RELEASE message, PACKET MEASUREMENT ORDER message or in the PACKET CELL CHANGE ORDER message (see 3GPP TS 44.060). If received in a PACKET CELL CHANGE ORDER message, the mobile station shall use the parameters provided in the *Individual Priorities* IE only upon successful completion of the network controlled cell reselection procedure as described in 3GPP TS 44.060. + +If the T3230 timeout value is provided the mobile station shall set timer T3230 to the value received and start timer T3230 (or restart timer T3230 with the timeout value provided if already running). + +If the *Individual Priorities* IE contains priorities for more than 16 UTRAN FDD frequencies, more than 16 UTRAN TDD frequencies, or more than 8 E-UTRAN frequencies, then the mobile station may ignore the contents of the *Individual Priorities* IE and, in this case, shall delete any stored individual priorities. + +NOTE: Each signalled frequency is counted whether or not the mobile station supports that frequency. + +Stored individual priorities shall be deleted by the mobile station when any of the following occurs: + +- a PLMN selection is performed and results in a change of PLMN and the new PLMN is not an equivalent PLMN, see 3GPP TS 23.122; or +- the mobile station is switched off; or +- a CHANNEL RELEASE message, PACKET MEASUREMENT ORDER message or PACKET CELL CHANGE ORDER is received with an indication that the individual priorities shall be deleted; or +- new individual priorities are received ; or +- timer T3230 expires. + +At inter-RAT cell reselection from UTRAN or E-UTRAN to GERAN or cell selection or handover that results in a change of RAT from UTRAN or E-UTRAN to GERAN, the MS shall inherit individual priority information if the corresponding timer (T320 if the last serving RAT was E-UTRA; T322 if the last serving RAT was UTRA) has not expired. In this case the mobile station shall start timer T3230 with the timeout value set to the remaining validity time of the corresponding timer from the source RAT. If this inherited individual priority information includes more than one individual priority for GERAN frequencies, then the mobile station shall apply only the one applicable to the BCCH carrier of the first serving GERAN cell after the change of RAT as the individual priority for all GERAN cells for as long as the mobile station remains in GERAN. In this case the mobile station shall not apply the other GERAN individual priority(ies) until the MS leaves GERAN (see 3GPP TS 25.331, 3GPP TS 36.331). + +NOTE: The network may provide individual priorities information for inter-RAT frequencies not configured by system information. + +### 3.2.4 (void) + +## 3.3 RR connection establishment + +### 3.3.1 RR connection establishment initiated by the mobile station + +The purpose of the immediate assignment procedure is to establish an RR connection between the mobile station and the network. + +A MS that has enabled PEO or EC operation may optionally support mobile originated RR connection establishment for GSM services (see 3GPP TS 23.060 [74]). If it establishes a RR connection for GSM services then it shall disable GPRS services (see 3GPP TS 23.060 [74]) until the RR connection is released. + +### 3.3.1.1 Entering the dedicated mode : immediate assignment procedure + +The immediate assignment procedure can only be initiated by the RR entity of the mobile station. Initiation is triggered by request from the MM sublayer or LLC layer to enter the dedicated mode or by the RR entity in response to a PAGING REQUEST message, to initiate a notification response procedure or to initiate a priority uplink request procedure. Upon such a request: + +- if access to the network is allowed (as defined in sub-clause 3.3.1.1.1), the RR entity of the mobile station initiates the immediate assignment procedure as defined in sub-clause 3.3.1.1.2; +- otherwise, it rejects the request. + +The request from the MM sublayer to establish an RR connection specifies an establishment cause. Similarly, the request from the RR entity to establish a RR connection in response to a PAGING REQUEST 1, 2 or 3 message specifies one of the establishment causes "answer to paging"; the request from the RR entity to establish an RR connection in order to initiate a notification response procedure or a priority uplink request procedure specifies one of the establishment causes "procedures that can be completed with a SDCCH". + +#### 3.3.1.1.1 Permission to access the network + +All mobile stations with an inserted SIM are members of one out of 10 access classes numbered 0 to 9. The access class number is stored in the SIM. In addition, mobile stations may be members of one or more out of 5 special access classes (access classes 11 to 15) (see 3GPP TS 22.011), this is also held on the SIM card. + +The system information messages on the BCCH broadcast the list of authorized access classes and authorized special access classes, and whether emergency calls are allowed in the cell to all mobile stations or only to the members of authorized special access classes. When network sharing is in use in the cell (see sub-clause 3.8), this information may be broadcast individually for each of the PLMN sharing the cell, and may include different domain-specific access control information for the CS and PS domains. + +A mobile station supporting network sharing shall determine whether or not access to the network is allowed using the applicable access control information corresponding to the selected PLMN. In addition, if domain-specific access control is used, a mobile station supporting domain-specific access control shall determine whether or not access to the network is allowed for the domain originating the access attempt, using the access control information corresponding to this domain. + +A mobile station configured for EAB and has enabled EAB (i.e. it has received EAB Authorization Mask and EAB Subcategory information for its selected PLMN from SYSTEM INFORMATION TYPE 21) shall, prior to proceeding with a mobile originated access attempt, re-read SI21 if more than 30 seconds have expired since the last time it read SI21. + +For a mobile originated access attempt, a mobile station configured for EAB and that has enabled EAB shall perform a preliminary access barring check (see sub-clause 3.3.1.4). If the preliminary access barring check indicates network access is barred then access to the network is not allowed. Otherwise, the mobile station shall proceed according to the remainder of this sub-clause. + +If the establishment cause for the request of the MM sublayer is not "emergency call", access to the network is allowed if and only if the mobile station is a member of at least one authorized: + +- access class; or +- special access class. + +If the establishment cause for the request of the MM sublayer is "emergency call", access to the network is allowed if and only if: + +- emergency calls are allowed to all mobile stations in the cell; or +- the mobile station is a member of at least one authorized special access class. + +#### 3.3.1.1.1a Implicit reject indication from the network + +The network may at any time include an implicit reject indication for the PS domain or the CS domain within an IMMEDIATE ASSIGNMENT message using the *LA Rest Octets* IE (see sub-clause 10.5.2.16) or within an IMMEDIATE ASSIGNMENT REJECT or an IMMEDIATE ASSIGNMENT EXTENDED or an IMMEDIATE + +PACKET ASSIGNMENT message using the *Feature Indicator* IE (see sub-clause 10.5.2.76) or within a PAGING REQUEST TYPE 1 message using the *P1 Rest Octets* IE (see sub-clause 10.5.2.23) or within a PAGING REQUEST TYPE 2 message using the *P2 Rest Octets* IE (see sub-clause 10.5.2.24) or within a PAGING REQUEST TYPE 3 message using the *P3 Rest Octets* IE (see sub-clause 10.5.2.25). + +In addition, the network may at any time include an implicit reject indication for the PS domain or the CS domain within an EC IMMEDIATE ASSIGNMENT TYPE 1 message using the *Feature Indicator* IE (see sub-clause 10.5.2.76). + +### 3.3.1.1.2 Initiation of the immediate assignment procedure + +The RR entity of a mobile station, when attempting to establish a CS connection other than for an emergency call or for sending a paging response, and accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) shall, while ignoring MS identities included within PAGING REQUEST messages, start listening to the downlink CCCH until successfully decoding one of the RR messages listed in sub-clause 3.3.1.1.1a. If the RR message indicates an implicit reject for the CS domain (see sub-clause 3.3.1.1.1a) the mobile station shall abort the immediate assignment procedure and initiate the Implicit Reject procedure (see sub-clause 3.3.1.1.3.2a). + +The RR entity of a mobile station initiates the immediate assignment procedure by scheduling the sending of CHANNEL REQUEST (or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST) messages on the RACH and leaving idle mode (in particular, the mobile station shall ignore PAGING REQUEST messages). + +The mobile station then sends maximally $M + 1$ CHANNEL REQUEST (or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST) messages on the RACH in a way such that: + +- when requesting resources for a PS connection other than in the case of sending a paging response, the mobile station shall send the first CHANNEL REQUEST (or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST) message in the first available TDMA frame belonging to the mobile station's RACH. +- in all other cases, the number of slots belonging to the mobile station's RACH between initiation of the immediate assignment procedure and the first CHANNEL REQUEST (or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST message) (excluding the slot containing the message itself) is a random value drawn randomly for each new initial assignment initiation with uniform probability distribution in the set $\{0, 1, \dots, \max(T, 8) - 1\}$ ; +- the number of slots belonging to the mobile station's RACH between two successive CHANNEL REQUEST (or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST) messages (excluding the slots containing the messages themselves) is a random value drawn randomly for each new transmission with uniform probability distribution in the set $\{S, S + 1, \dots, S + T - 1\}$ ; + +Here, $T$ is the value of the parameter "Tx-integer" broadcast on the BCCH; + +$M$ is the value of the parameter "max retrans" broadcast on the BCCH; + +$S$ is a parameter depending on the CCCH configuration and on the value of Tx-integer as defined in table 3.3.1.1.2.1. + +The CHANNEL REQUEST messages are sent on the RACH (cf. sub-clause 1.5) and contain as parameters: + +- an establishment cause which corresponds to the establishment cause given by the MM sublayer and the broadcast NECI value, or which corresponds to one of the establishment causes "answer to paging" given by the RR entity in response to a PAGING REQUEST message including the Channel Needed information, or which corresponds to one of the establishment causes "procedures that can be completed with a SDCCH" given by the RR entity in order to initiate a notification response procedure or a priority uplink request procedure; +- a random reference which is drawn randomly from a uniform probability distribution for every new transmission. + +After sending the first CHANNEL REQUEST message, the mobile station shall start listening to the BCCH; it shall also listen to the full downlink CCCH timeslot corresponding to its CCCH group. + +A mobile station that has initiated the immediate assignment procedure other than for an emergency call or for sending a paging response, and that is accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008), and has sent one or more CHANNEL REQUEST messages shall proceed as follows: + +- If the mobile station receives an IMMEDIATE ASSIGNMENT, an IMMEDIATE ASSIGNMENT EXTENDED or an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its last 3 transmitted CHANNEL REQUEST messages it shall act on that message as described in sub-clause 3.3.1.1.3. +- If the mobile station successfully decodes an RR message, which is not a response corresponding to one of its last 3 transmitted CHANNEL REQUEST, that indicates an implicit reject for the CS domain (see sub-clause 3.3.1.1.1a) it shall start timer T3126 (if not already running) and initiate the implicit reject procedure as described in sub-clause 3.3.1.1.3.2a. + +Having sent M + 1 CHANNEL REQUEST messages, the RR entity of the mobile station starts timer T3126. At expiry of timer T3126, the immediate assignment procedure is aborted; if the immediate assignment procedure was triggered by a request from the MM sublayer, a random access failure is indicated to the MM sublayer. + +**Table 3.3.1.1.2.1: Values of parameter S** + +| TX-integer | non combined CCCH | combined CCH/SDCCH | +|------------|-------------------|--------------------| +| 3,8,14,50 | 55 | 41 | +| 4,9,16 | 76 | 52 | +| 5,10,20 | 109 | 58 | +| 6,11,25 | 163 | 86 | +| 7,12,32 | 217 | 115 | + +### 3.3.1.1.3 Answer from the network + +#### 3.3.1.1.3.1 On receipt of a CHANNEL REQUEST message + +The network may allocate a dedicated channel to the mobile station by sending an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT EXTENDED message in unacknowledged mode on the same CCCH timeslot on which it has received the CHANNEL REQUEST. There is no further restriction on what part of the downlink CCCH an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT EXTENDED message can be sent. The type of channel allocated (SDCCH or TCH; the channel mode shall be set to signalling only) is a network operator decision. Timer T3101 is then started on the network side. + +NOTE: There are two types of immediate assignment messages: + +- IMMEDIATE ASSIGNMENT message, containing assignment information for one mobile station only; +- IMMEDIATE ASSIGNMENT EXTENDED message, containing assignment information for two mobile stations at the same time. + +The IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message contains: + +- the description of the assigned channel; +- the information field of the CHANNEL REQUEST message and the frame number of the frame in which the CHANNEL REQUEST message was received; +- the initial timing advance (cf. 3GPP TS 44.004); +- optionally, a starting time indication. + +If frequency hopping is applied, the mobile station uses the last CA received on the BCCH to decode the Mobile Allocation. + +On receipt of an IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message corresponding to one of its 3 last CHANNEL REQUEST messages, the mobile station stops T3126 (if running), stops sending CHANNEL REQUEST messages, switches to the assigned channels, sets the channel mode to signalling only and activates the assigned channels. It then establishes the main signalling link with an SABM containing an information field (see sub-clause 3.1.5). + +An IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions. + +In the case of the reception of an IMMEDIATE ASSIGNMENT EXTENDED message, or of an IMMEDIATE ASSIGNMENT message which contains only the description of a channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the reception of the message (see 3GPP TS 45.010 for the timing constraints). + +If the message contains both the description of a channel to be used after the indicated time and of a channel to be used before, the mobile station accesses a channel as an immediate reaction to the reception of the message. If the moment the mobile station is ready to access is before the indicated time, the mobile station accesses the channels described for before the starting time. The mobile station then changes to the channel described for after the starting time at the indicated time. New parameters can be the mobile allocation and MAIO. Other parameters describing the channel to be used before the starting time are taken from the description of the channel defined for use after the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described for after the starting time. + +If frequency hopping is applied, the mobile station uses the last CA received on the BCCH. + +#### 3.3.1.1.3.2 Assignment rejection + +If no channel is available for assignment, the network may send to the mobile station an IMMEDIATE ASSIGNMENT REJECT message in unacknowledged mode on the same CCCH timeslot on which the channel request message was received. There is no further restriction on what part of the downlink CCCH timeslot an IMMEDIATE ASSIGNMENT REJECT message can be sent. This message contains the request reference and a wait indication. + +On receipt of an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its 3 last CHANNEL REQUEST messages, the mobile station, stops sending CHANNEL REQUEST messages, starts timer T3122 with the indicated value, ("wait indication" information element), starts T3126 if it has not already been started, and listens to the downlink CCCH until T3126 expires. During this time, additional IMMEDIATE ASSIGNMENT REJECT messages are ignored, but any immediate assignment corresponding to any other of its 3 last CHANNEL REQUEST messages make the mobile station follow the procedure in sub-clause 3.3.1.1.3.1. If no such immediate assignment is received, the mobile station returns to CCCH idle mode (listening to its paging channel). + +As an option the mobile station may return to CCCH idle mode as soon as it has received responses from the network on all, or in case more than 3 were sent the last 3, of its CHANNEL REQUEST messages. + +The mobile station is not allowed to make a new attempt to establish a non emergency RR connection in the same cell until T3122 expires. Provided that an IMMEDIATE ASSIGNMENT REJECT message has not been received for an emergency RR connection attempt, the mobile station may attempt to enter the dedicated mode for an emergency call in the same cell before T3122 has expired. + +The Wait Indication IE (i.e. T3122) relates to the cell from which it was received. + +The mobile station in packet idle mode (only applicable to mobile station supporting GPRS) may initiate packet access in the same cell before T3122 has expired, see 3GPP TS 44.060 and sub-clause 3.5.2.1.3.4. + +After T3122 expiry, no CHANNEL REQUEST message shall be sent as a response to a page until a PAGING REQUEST message for the mobile station is received. + +#### 3.3.1.1.3.2a Implicit Reject procedure + +A mobile station for which timer T3126 or T3146 is running shall proceed as follows: + +- While T3126 or T3146 is running, the mobile station listens to the downlink CCCH for a response from the network and is not allowed to make a new access attempt. +- If a response corresponding to any of the last 3 transmitted CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST messages is received the mobile station shall stop T3126 or T3146 and act on that message as described in sub-clause 3.3.1.1.3 (if attempting a CS domain access) or as described in sub-clause 3.5.2.1.3 (if attempting a PS domain access). +- If T3126 or T3146 expires the mobile station proceeds according to the remainder of this sub-clause. + +If the mobile station initiates this procedure due to implicit reject indication received for the CS domain (respectively PS domain) it starts timer T3234 (respectively timer T3236), returns to idle mode and monitors the CCCH. An exception case is where EC operation is enabled in which case the mobile station shall proceed as described in sub-clause 3.5.2.a.2 when T3146 expires. The mobile station is not allowed to make a mobile originated access attempt when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) for the CS domain (respectively PS domain) in the same cell until T3234 (respectively T3236) expires or is stopped. + +If the mobile station receives a PAGING REQUEST message while T3234/T3236 is running it shall stop T3234/T3236 and respond to the PAGING REQUEST message. + +### 3.3.1.1.4 Assignment completion + +The immediate assignment procedure is terminated on the network side when the main signalling link is established. Timer T3101 is stopped and the MM sublayer on the network side is informed that the RR entity has entered the dedicated mode. + +On the mobile station side, the procedure is terminated when the establishment of the main signalling link is confirmed. The MM sublayer is informed that the RR entity has entered the dedicated mode. + +A DTM capable mobile station in GMM READY state shall perform a Cell Update procedure when it enters dedicated mode from packet idle mode in a cell that supports dual transfer mode. This can be done as early as possible after access but shall be done after sending a CLASSMARK CHANGE message. + +#### 3.3.1.1.4.1 Early classmark sending + +Early classmark sending consists in the mobile station sending as early as possible after access a CLASSMARK CHANGE message to provide the network with additional classmark information. In addition an MS supporting UTRAN shall send a UTRAN CLASSMARK CHANGE message; an MS supporting CDMA2000 shall send a CDMA2000 CLASSMARK CHANGE message and an MS supporting GERAN *Iu mode* shall send a GERAN IU MODE CLASSMARK CHANGE message. When a CLASSMARK CHANGE message and one or more additional UTRAN CLASSMARK CHANGE or CDMA2000 CLASSMARK CHANGE or GERAN IU MODE CLASSMARK CHANGE messages are to be sent, the CLASSMARK CHANGE message shall be sent first. + +A mobile station which implements the "Controlled Early Classmark Sending" option shall perform the early classmark sending if and only if it is accepted by the network, as indicated in the last reception in the accessed cell of the SYSTEM INFORMATION TYPE 3 message or the PACKET SYSTEM INFORMATION TYPE 2 message (3GPP TS 44.060). If the PACKET SYSTEM INFORMATION TYPE 2 messages have been received, but the Early Classmark Sending Control flag is not included, the mobile station may either read the SYSTEM INFORMATION TYPE 3 message or it shall assume that the early classmark sending is allowed in the cell. + +A mobile station which implements support for multiple band shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the support of one or more 3G Radio Access Technology shall also implement the "Controlled Early Classmark Sending" option; in this case neither UTRAN CLASSMARK CHANGE, CDMA2000 CLASSMARK CHANGE nor GERAN IU MODE CLASSMARK CHANGE message shall be sent by the mobile if prohibited by the 3G Early Classmark Sending Restriction parameter in the last reception in the accessed cell of the SYSTEM INFORMATION TYPE 3 message or the PACKET SYSTEM INFORMATION TYPE 2 message (see 3GPP TS 44.060). If the PACKET SYSTEM INFORMATION TYPE 2 messages have been received, but the 3G Early Classmark Sending Restriction flag is not included, the mobile station shall assume neither UTRAN, CDMA2000 nor GERAN IU MODE CLASSMARK CHANGE message shall be sent with the Early Classmark Sending. + +A mobile station which implements the "multislot capability" option shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station that implements some form of treatment of UCS2 alphabet (see 3GPP TS 23.038) encoded character string (e.g., in short message, or in USSD string) may indicate so in the classmark. (An example is a Mobile Equipment able to display UCS2 encoded character string.) In such a case, it should also implement the "Controlled Early Classmark Sending" option. It is the mobile station responsibility to provide the UCS2 support information in due time. If the network needs this information and the mobile station did not provide it, the network may assume that the Mobile Equipment does not support UCS2. + +A mobile station which implements the R-GSM band (see 3GPP TS 45.005) shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the extended measurement function shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the "GPRS" option shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the "SoLSA" option shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the "EDGE" option shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the "LCS" option shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station that implements the GERAN Feature Package 2 (see 3GPP TS 24.008) shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the "VAMOS" option shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station that implements "Extended TSC sets" option (see 3GPP TS 24.008) shall also implement the "Controlled Early Classmark Sending" option. + +A mobile station which implements the "Controlled Early Classmark Sending" option shall indicate it in the classmark (ES IND bit). + +#### 3.3.1.1.4.2 Service information sending + +Service information sending consists in a mobile station in class A mode of operation sending a SERVICE INFORMATION message and in a mobile station in class B mode of operation sending a GPRS SUSPENSION REQUEST message, providing additional service information to the network. + +A mobile station in class A mode of operation which supports the MBMS feature and requires notification of commencing MBMS sessions during dedicated mode operation, shall perform the service information sending procedure: + +- at the earliest opportunity after the early Classmark sending procedure and any DTM related signalling, if and only if the dedicated mode MBMS notification feature is supported in the cell as indicated in the GPRS Cell Options (see 3GPP TS 44.060) or DTM INFORMATION message or System Information Type 6 message; or +- if the P-TMSI of the MS is reallocated during the CS connection and the dedicated mode MBMS notification feature is supported in the cell as indicated in the GPRS Cell Options (see 3GPP TS 44.060) or DTM INFORMATION message or System Information Type 6 message; or +- on the main DCCH of a target cell after successfully completing the handover procedure, if indicated to do so in the HANDOVER COMMAND message (see sub-clause 3.4.4.1) and the dedicated mode MBMS notification feature is supported in the target cell as indicated in the GPRS Cell Options (see 3GPP TS 44.060) or DTM INFORMATION message or System Information Type 6 message. + +#### 3.3.1.1.5 Abnormal cases + +If a lower layer failure occurs on the mobile station side on the new channel before the successful establishment of the main signalling link, the allocated channels are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the failure is due to information field mismatch in the contention resolution procedure, see sub-clause 3.1.5, and no repetition as described in this paragraph has been performed, the immediate assignment procedure shall be repeated. +- If the failure is due to any other reason or if a repetition triggered by a contention resolution failure has been performed. The mobile station returns to idle mode (RR connection establishment failure), transactions in progress are aborted and cell reselection then may take place. + +If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT message does not satisfactorily define a channel, an RR connection establishment failure has occurred. + +If the Mobile Allocation IE indexes frequencies in more than one frequency band then a RR connection establishment failure has occurred. + +If an IMMEDIATE ASSIGNMENT message indicates (a) channel(s) in a different frequency band to which the CHANNEL REQUEST message was sent then, if the frequency band is supported by the mobile station, the mobile station shall access the indicated channel(s) with the same power control level as used for the CHANNEL REQUEST message. + +If an IMMEDIATE ASSIGNMENT message indicates a channel in non-supported frequency band then a RR connection establishment failure has occurred. + +On the network side, if timer T3101 elapses before the main signalling link is established, the newly allocated channels are released and the request is forgotten. Note that the network has no means to distinguish repeated attempts from initial attempts from a mobile station. + +### 3.3.1.2 Entering the group transmit mode: uplink access procedure + +Only applicable for mobile stations supporting "VGCS transmit". + +The purpose of the uplink control procedure is to establish an RR connection on a VGCS channel between a mobile station which is in group receive mode on that channel and the network. + +The mobile station enters the group transmit mode when a successful establishment of the RR connection is indicated. The channel mode assumed by the mobile station is the one derived from the channel description. + +When the network supports talker priority or sending application-specific data, it shall provide on the NCH in combination with the UPLINK\_BUSY message on the group call channel downlink, the method that the MS shall use to issue priority talker requests. + +NOTE: The only indication of support of talker priority by the network is the presence of the Talker Priority and Emergency Indication IE in the UPLINK BUSY message (see sub-clause 9.1.46.1). + +#### 3.3.1.2.1 Mobile station side + +##### 3.3.1.2.1.1 Uplink investigation procedure - talker priority not supported by the network + +The mobile station in group receive mode shall consider the uplink as free if the last message indicating the uplink as being free was received less than 480 ms ago and if no UPLINK BUSY message has been received since the last message indicating the uplink as free. + +On receipt of a request from the upper layer to access the uplink and if the uplink is not free, the mobile station starts the timer T3128. + +If the uplink is free or becomes free before expiry of timer T3128, then the uplink investigation procedure is terminated, the mobile station shall stop T3128, and start the uplink access procedure. + +NOTE: The start of the uplink access procedure is not subject to the access class of the mobile station. + +If the uplink is not indicated free before the timer expires, the mobile station shall remain in the group receive mode and indicate a reject of the uplink request to the upper layer. + +##### 3.3.1.2.1.1a Uplink investigation procedure - talker priority supported by the network + +The mobile station in group receive mode shall consider the uplink as free if the last message indicating the uplink as being free was received less than 480 ms ago and if no UPLINK BUSY message has been received since the last message indicating the uplink as free. + +On receipt of a privilege, emergency priority or emergency reset request from the upper layer to access the uplink, the mobile station shall verify that the requested priority is permitted according to the SIM/USIM. If the mobile station is not permitted to use the requested talker priority then it shall indicate a rejection of the uplink request to the upper layers. + +On receipt of a request from the upper layer to access the uplink and if the uplink is busy with a priority equal or higher than the requested priority, the mobile station starts the timer T3128. + +If the uplink is free, becomes free before expiry of timer T3128 or the current talker priority is less than the priority of the request from the upper layer, then the uplink investigation procedure is terminated, the mobile station shall stop T3128 if running, and start the uplink access. If the uplink is busy, the MS shall determine whether to start the uplink access or priority uplink request procedure based on the priority uplink access parameter broadcast on the NCH and the uplink access indication in the latest UPLINK BUSY message received in the cell. + +If the priority uplink access parameter broadcast on the NCH indicates "RACH access" but the latest UPLINK BUSY message received in the cell indicates that the voice group call channel is available for uplink access requests, the MS shall start an uplink access procedure; otherwise the MS starts the priority uplink request procedure. + +If the priority uplink access parameter broadcast on the NCH indicates "Group Channel" then the MS always shall start an uplink access procedure. + +NOTE: The start of the uplink access procedure is not subject to the access class of the mobile station. + +If the mobile station is unable to start the uplink access or priority uplink request procedure before timer T3128 expires, the mobile station shall remain in the group receive mode and indicate a reject of the uplink request to the upper layer. + +#### 3.3.1.2.1.2 Uplink access procedure with talker priority not supported by the network + +The mobile station shall send UPLINK ACCESS messages on the voice group call channel with the appropriate establishment cause. These messages shall be sent unciphered. The first UPLINK ACCESS message shall be transmitted by the mobile station with a random delay between 0 and 20 ms. + +Having sent the first UPLINK ACCESS message, the mobile station starts timer T3130. The mobile station shall send the UPLINK ACCESS message repeatedly with an interval of 100ms plus a random delay between 0 and 20 ms up to five times. At expiry of timer T3130, the mobile station shall repeat the same procedure if the uplink is free. Timer T3130 may be started a maximum of 3 times. On expiry of timer T3130 for the third time a rejection of the uplink request is indicated to the upper layers. + +The UPLINK ACCESS messages contain a random reference which is drawn randomly from a uniform probability distribution. The UPLINK ACCESS messages repetitions shall contain the same random reference as the one contained in the first message. + +If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the mobile station shall use this UIC IE for the coding of the UPLINK ACCESS messages (see 3GPP TS 45.003). If no UIC is provided, the mobile station shall use the BSIC received from the current cell, for instance from the initial synchronization. + +If no VGCS UPLINK GRANT or UPLINK BUSY message is received by the mobile station 480 ms after having sent the first UPLINK ACCESS message, the mobile station shall stop sending UPLINK ACCESS messages and wait in order to receive a VGCS UPLINK GRANT or UPLINK BUSY message. + +On receipt of a VGCS UPLINK GRANT message corresponding to one of its UPLINK ACCESS messages, the mobile station stops T3130, stops sending UPLINK ACCESS messages, and establishes the main signalling link with an SABM containing the TALKER INDICATION message in the information field. The ciphering key sequence number shall be included in the TALKER INDICATION message if the group call is ciphered. Early classmark sending shall be performed if applicable. If a UA is received containing the message sent, the mobile station enters the group transmit mode and indicates the successful seizure of the uplink to the upper layer. If a UA is received with a message different from the message sent, the mobile station shall remain in the group receive mode and indicate the rejection of the uplink request to the upper layers. + +On receipt of a VGCS\_UPLINK\_GRANT message aimed to another mobile station (i.e. not corresponding to one of its UPLINK ACCESS messages sent for this uplink request), the mobile station shall stop timer T3130 and shall not send UPLINK ACCESS message and shall start timer T3224. If the mobile station receive an UPLINK BUSY message before timer T3224 expires, it shall stop timer T3224 and remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers. Otherwise it shall follow the same procedures as for expiry of timer T3130. + +When receiving an UPLINK BUSY message, the mobile station stops T3130 and stops sending UPLINK ACCESS messages. The mobile shall remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers. + +#### 3.3.1.2.1.2a Uplink access procedure - with talker priority supported by the network using uplink access procedure + +##### 3.3.1.2.1.2a.1 Talker priority normal, privileged or emergency + +The mobile station shall send UPLINK ACCESS messages on the voice group call channel with the appropriate establishment cause. These messages shall be sent unciphered. The first UPLINK ACCESS message shall be transmitted by the mobile station with a random delay between 0 and 20 ms. + +Having sent the first UPLINK ACCESS message, the mobile station starts timer T3130. The mobile station shall send the UPLINK ACCESS message repeatedly up to five times. The interval between two sequential messages shall be 100ms plus a random delay between 0 and 20ms if the priority of the current uplink access is normal, or 80ms plus a random delay between 0 and 20ms if the priority of the current uplink access is privileged or emergency. At expiry of timer T3130, the mobile station shall repeat the same procedure if the uplink is free or the current talker priority is less than that of this uplink request. Timer T3130 may be started a maximum of 3 times. On expiry of timer T3130 for the third time a rejection of the uplink request is indicated to the upper layers. + +The UPLINK ACCESS messages contain a random reference which is drawn randomly from a uniform probability distribution. The UPLINK ACCESS messages repetitions shall contain the same random reference as the one contained in the first message. + +If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the mobile station shall use this UIC IE for the coding of the UPLINK ACCESS messages (see 3GPP TS 45.003). If no UIC is provided, the mobile station shall use the BSIC received from the current cell, for instance from the initial synchronization. + +If no VGCS UPLINK GRANT or UPLINK BUSY message is received by the mobile station 480 ms after having sent the first UPLINK ACCESS message for this uplink request, the mobile station shall stop sending UPLINK ACCESS messages and wait in order to receive a VGCS UPLINK GRANT or UPLINK BUSY message. + +On receipt of a VGCS UPLINK GRANT message corresponding to one of its UPLINK ACCESS messages, the mobile station stops T3130, stops sending UPLINK ACCESS messages, and establishes the main signalling link with an SABM/UA exchange containing the TALKER INDICATION message in the information field, as described in sub-clause 3.3.1.2.1.2.2. + +On receipt of a VGCS\_UPLINK\_GRANT message aimed to another mobile station (i.e. not corresponding to one of its UPLINK ACCESS messages sent for this uplink request), the mobile station shall stop timer T3130 and shall not send UPLINK ACCESS message and shall start timer T3224. If an UPLINK BUSY message is received before timer T3224 expires, the mobile station shall stop the timer. If the UPLINK BUSY message indicates a priority lower than the priority of the current uplink access, the mobile station shall resend the UPLINK\_ACCESS message, otherwise, it shall remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers. If timer T3224 expires, the mobile station shall follow the same procedures as for expiry of timer T3130. + +When receiving an UPLINK BUSY message indicating a priority that is equal or higher than the priority of the current uplink access, the mobile station stops T3130 and stops sending UPLINK ACCESS messages for this uplink request. The mobile shall remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers. + +When receiving an UPLINK BUSY message indicating that the voice group call channel is not available for uplink access requests the mobile station stops T3130, stops sending UPLINK ACCESS messages and initiates the priority uplink request procedure. + +When receiving an UPLINK RELEASE message during RR connection establishment on the group channel, the mobile station shall remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers. + +##### 3.3.1.2.1.2a.2 Emergency mode reset request + +The mobile station shall send UPLINK ACCESS messages on the voice group call channel with the appropriate establishment cause. These messages shall be sent unciphered. The first UPLINK ACCESS message shall be transmitted by the mobile station with a random delay between 0 and 20 ms. + +Having sent the first UPLINK ACCESS message, the mobile station starts timer T3130. The mobile station shall send the UPLINK ACCESS message repeatedly up to five times. The interval between two sequential messages shall be 80ms plus a random delay between 0 and 20ms. At expiry of timer T3130, the mobile station shall repeat the same procedure if the emergency mode is still set. Timer T3130 may be started a maximum of 3 times. On expiry of timer T3130 for the third time a rejection of the uplink request is indicated to the upper layers. + +The UPLINK ACCESS messages contain a random reference which is drawn randomly from a uniform probability distribution. The UPLINK ACCESS messages repetitions shall contain the same random reference as the one contained in the first message. + +If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the mobile station shall use this UIC IE for the coding of the UPLINK ACCESS messages (see 3GPP TS 45.003). If no UIC is provided, the mobile station shall use the BSIC received from the current cell, for instance from the initial synchronization. + +When receiving an UPLINK BUSY message indicating that the voice group call channel is not available for uplink access requests the mobile station stops T3130, stops sending UPLINK ACCESS messages for this uplink request and initiates the priority uplink request procedure. + +On receipt of an VGCS UPLINK GRANT message corresponding to one of its UPLINK ACCESS messages for the current uplink access, the mobile station stops T3130, stops sending additional UPLINK ACCESS messages for this UPLINK REQUEST, and establishes the main signalling link with an SABM/UA exchange containing the TALKER INDICATION message in the information field, as described in 3.3.1.2.1.2.2. + +When receiving an UPLINK BUSY or UPLINK FREE message indicating that the emergency mode is not set or a VGCS UPLINK GRANT message aimed to another mobile station (i.e. not corresponding to one of its UPLINK ACCESS messages sent for this uplink request), the mobile station stops T3130 and stops sending additional UPLINK ACCESS messages for this uplink request. The mobile shall remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers if the emergency mode is still set. + +When receiving an UPLINK RELEASE message during RR connection establishment on the group channel, the mobile station shall remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers. + +#### 3.3.1.2.1.2b Priority uplink request procedure + +##### 3.3.1.2.1.2b.1 Talker priority privileged or emergency + +The mobile station shall temporarily leave group receive mode and initiate the immediate assignment procedure, as specified in 3.3.1.1. The mobile station shall store for comparison purposes the frame number of the frame in which the CHANNEL REQUEST message was sent to initiate the Priority Uplink access. The establishment of a signalling link is then initiated by use of a SABM, with information field containing the PRIORITY UPLINK REQUEST message (see subclause 3.1.5). The mobile identity, reduced group call reference, random reference and the type of request shall be included in the PRIORITY UPLINK REQUEST message. Once a UA is received from the network, containing the message sent, the mobile station waits for the signalling link to be released. On receipt of a CHANNEL RELEASE message (with the group channel description) the mobile station sends a DISCONNECT message to the network, returns to group receive mode, and starts T3130. + +On receipt of a VGCS UPLINK GRANT message with request reference corresponding to the random reference and frame number stored in the MS, the mobile station stops T3130, and establishes the main signalling link with a SABM/UA exchange containing the TALKER INDICATION message in the information field. The ciphering key sequence number shall be included in the TALKER INDICATION message. Early classmark sending shall be performed if applicable. If a UA is received containing the message sent, the mobile station enters the group transmit mode and indicates the successful seizure of the uplink to the upper layer. If a UA is received with a message different from the message sent, the mobile station shall remain in the group receive mode and indicate the rejection of the uplink request to the upper layers. + +On receipt of a VGCS\_UPLINK\_GRANT message aimed to another mobile station (i.e. not corresponding to the random reference and frame number stored in the MS), the mobile station shall stop timer T3130 and start timer T3224. If an UPLINK BUSY message is received before timer T3224 expires, the mobile station shall stop the timer. If the UPLINK BUSY message indicates a priority lower than the priority of the current priority uplink request, the mobile station shall resend the PRIORITY UPLINK REQUEST message, otherwise, it shall remain in the group receive mode and shall indicate a rejection of the priority uplink request to the upper layers. If timer T3224 expires, the mobile station shall follow the same procedures as for expiry of timer T3130. + +When receiving an UPLINK BUSY message indicating a priority that is equal or higher than the priority of the current priority uplink request, the mobile station stops T3130. The mobile shall remain in the group receive mode and shall indicate a rejection of the priority uplink request to the upper layers. + +At expiry of timer T3130, the mobile station shall repeat the same procedure if the current talker priority is less than that of the requested priority, use the uplink access procedure if the uplink is free or use the uplink access procedure if the latest UPLINK BUSY message received in the cell indicates that the voice group call channel is available for uplink access requests. A maximum of three attempts is allowed and after that a rejection of the priority uplink request is indicated to the upper layers. + +#### 3.3.1.2.1.2b.2 Emergency mode reset request + +The mobile station shall temporarily leave the group receive mode and initiate the immediate assignment procedure, as specified in 3.3.1.1. The establishment of a signalling link is then initiated by use of a SABM, with information field containing the PRIORITY UPLINK REQUEST message with cause Reset Emergency Talker Indication (see subclause 3.1.5). The mobile identity, reduced group call reference, and random reference shall be included in the PRIORITY UPLINK message. Once a UA is received from the network, containing the message sent, the mobile station waits for the signalling link to be released. On receipt of a CHANNEL RELEASE message (with the group channel description) the mobile station sends a DISCONNECT to the network and returns to group receive mode. + +#### 3.3.1.2.1.2b.3 Validation of priority uplink requests for ciphered voice group calls + +When validation of priority uplink requests is required by the operator, the MS shall store the token received from the network in UPLINK BUSY and periodic UPLINK BUSY messages on the main signalling link. When a listener sends a PRIORITY UPLINK REQUEST message, the MS shall include the token as a parameter and follow the procedures specified in 3.3.1.2.1.2b.1 and 3.3.1.2.1.2b.2. + +The MS shall always use the latest available token. + +If an UPLINK BUSY message is received with a new token and a priority that is less than that of a MSs outstanding priority uplink request, the mobile station shall stop T3130, temporarily leave the group receive mode in order to resend the PRIORITY UPLINK REQUEST with the new token and return to the group receive mode to wait for the VGCS UPLINK GRANT message. + +If at expiry of T3130 the uplink is still busy and the mobile station repeats the priority uplink request procedure, the MS shall use a different token, if available. + +#### 3.3.1.2.1.2c Uplink access procedure for sending application-specific data + +##### 3.3.1.2.1.2c.1 General + +The transmission of application-specific data by the mobile station in group receive mode to the network is carried out by the mobile temporarily leaving group receive mode, establishing a L2 connection and sending a L3 message containing the application-specific data in the SABM frame used to establish the main signalling link on a dedicated channel. The dedicated channel may be either the group call channel or another channel assigned by the network. + +##### 3.3.1.2.1.2c.2 Using the Voice Group Call Channel + +If an UPLINK FREE message has been received and no subsequent UPLINK BUSY message has been received, or the last UPLINK BUSY message received in the cell indicates that the group channel shall be used to send application-specific data, the mobile station shall send UPLINK ACCESS messages on the voice group call channel with the establishment cause "UL request for sending application-specific data" to request a L2 connection. The mobile station shall then wait for a VGCS UPLINK GRANT message. When the VGCS UPLINK GRANT message is received by the mobile station, it establishes the main signalling link by sending a SABM command containing a DATA INDICATION message in the information field (see sub-clause 3.1.5). + +Once contention resolution is complete, no further data shall be transmitted by the mobile station on the dedicated channel.. On receipt of an UPLINK RELEASE message, the MS returns to group receive mode. + +##### 3.3.1.2.1.2c.3 Using the RACH + +If the most recent UPLINK BUSY message received in the cell indicates that RACH Access shall be used (and no UPLINK FREE message has been received more recently), the mobile station shall temporarily leave group receive mode and send a CHANNEL REQUEST message on the RACH with the appropriate establishment cause (see sub- + +clause 9.1.8). On receipt of an IMMEDIATE ASSIGNMENT, the main signalling link is then established as specified in 3.1.5 by use of a SABM with information field containing the DATA INDICATION 2 message. + +Once contention resolution is complete, no further data shall be transmitted by the mobile station on the dedicated channel. On receipt of an CHANNEL RELEASE message, the mobile station returns to group receive mode. + +### 3.3.1.2.2 Network side - talker priority not supported by the network + +On receipt of an UPLINK ACCESS message the network shall perform, if necessary, contention resolution and grant the uplink to one mobile station by sending a VGCS UPLINK GRANT message to the mobile station in unacknowledged mode on the main signalling link. Furthermore, the network shall provide UPLINK BUSY messages on the main signalling link in all cells of the group call area. After having sent the first message, the network starts T3115. If the timer expires before the reception of a correctly decoded frame from the MS, the network repeats the VGCS UPLINK GRANT message to the mobile station, reset and restarts timer T3115. If the VGCS UPLINK GRANT message has been repeated Ny2 times without a correctly decoded frame being received from the MS, the network shall stop sending VGCS UPLINK GRANT messages and provide an UPLINK FREE message on the main signalling channel and wait for a new UPLINK ACCESS message. The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no error. + +After the data link layer is established, the RR entity of the network shall analyse the TALKER INDICATION message received from the mobile station, adapt the RR procedures to the new classmark if necessary and provide the mobile subscriber identity and ciphering key sequence number to the upper layer. + +### 3.3.1.2.2a Network side - network supports talker priority using uplink access procedure + +#### 3.3.1.2.2a.1 Uplink FREE + +##### 3.3.1.2.2a.1.1 Uplink Access cause - Normal, Privileged, or Emergency priority request + +As per sub-clause 3.3.1.2.2, with the following exceptions: + +- The UPLINK BUSY message shall contain the priority of the uplink request; +- The UPLINK BUSY message shall be transmitted every T3151 seconds; +- In the case of an uplink request with priority set to emergency that is accepted by the network (see 3GPP TS 48.008), the emergency indication shall be set in all UPLINK BUSY messages. +- The UPLINK BUSY message shall contain the Uplink Access Indication IE to inform the mobile station of the channel to be used in the cell for priority uplink access. If "RACH Access" is indicated on the NCH and the group call channel uplink in the cell is not used, the network shall indicate "Group Channel" in the UPLINK BUSY message; otherwise, the network shall indicate "RACH Access" in the UPLINK BUSY message. + +##### 3.3.1.2.2a.1.2 Uplink Access cause - Emergency mode reset request + +On receipt of an UPLINK ACCESS message with cause Emergency mode reset request when the emergency mode is set, the network shall perform, if necessary, contention resolution and grant the uplink to one mobile station by sending a VGCS UPLINK GRANT message to the mobile station in unacknowledged mode on the main signalling link. After having sent the first message, the network starts T3115. If the timer expires before the reception of a correctly decoded frame from the MS, the network repeats the VGCS UPLINK GRANT message to the mobile station, reset and restarts timer T3115. If the VGCS UPLINK GRANT message has been repeated Ny2 times without a correctly decoded frame being received from the MS, the network shall stop sending VGCS UPLINK GRANT messages and wait for a new UPLINK ACCESS message. The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no error. + +After the data link layer is established, the RR entity of the network shall analyse the TALKER INDICATION message received from the mobile station. The mobile subscriber identity is provided to the upper layer. The network shall then send an UPLINK RELEASE message to the mobile station. + +If emergency mode is not set within the network then the network discards the Emergency mode reset request. + +#### 3.3.1.2.2a.2 Uplink BUSY + +##### 3.3.1.2.2a.2.1 Uplink Access with cause priority less than or equal to current talker priority + +The Uplink Access request shall be discarded. + +##### 3.3.1.2.2a.2.2 Uplink Access with cause priority higher than current talker priority + +On receipt of an UPLINK ACCESS message the network shall perform, if necessary, contention resolution and grant the uplink of the voice group channel to one mobile station by sending a VGCS UPLINK GRANT message to the mobile station in unacknowledged mode on the main signalling link. + +After having sent the first message, the network starts T3115. If the timer expires before the reception of a correctly decoded frame from the MS, the network repeats the VGCS UPLINK GRANT message to the mobile station, reset and restarts timer T3115. If the VGCS UPLINK GRANT message has been repeated Ny2 times without a correctly decoded frame being received from the MS, the network shall stop sending VGCS UPLINK GRANT messages. The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no error. + +After the data link layer is established, the RR entity of the network shall analyse the TALKER INDICATION message received from the mobile station, adapt the RR procedures to the new classmark if necessary and provide the mobile subscriber identity and ciphering key sequence number to the upper layer. + +The network shall provide UPLINK BUSY messages on the main signalling link in all cells of the group call area, containing the latest validated priority. The UPLINK BUSY message shall be transmitted every T3151 seconds. + +##### 3.3.1.2.2a.2.3 Uplink Access with cause Emergency mode reset request + +As per sub-clause 3.3.1.2.2a.1.2, with the following exception: + +- If the emergency mode reset request is accepted by the network (see 3GPP TS 48.008), the network shall provide UPLINK BUSY messages, with the emergency mode not set and the priority set to normal, on the main signalling link in all of the cells of the group call area. These UPLINK BUSY messages shall be transmitted every T3151 seconds. + +#### 3.3.1.2.2b Network side - network supports talker priority using priority uplink procedure + +##### 3.3.1.2.2b.1 Uplink FREE + +##### 3.3.1.2.2b.1.1 Uplink Access cause - Normal, Privileged, or Emergency priority request + +As per sub-clause 3.3.1.2.2, with the exception that the UPLINK BUSY messages are transmitted every T3151 seconds. + +##### 3.3.1.2.2b.1.2 Uplink Access cause - Emergency mode reset request + +As per subclause 3.3.1.2.2a.1.2. + +### 3.3.1.2.2b.2 Uplink BUSY + +#### 3.3.1.2.2b.2.1 Priority Uplink Request with cause priority less than or equal to current talker priority + +The Priority Uplink Request shall be discarded. + +#### 3.3.1.2.2b.2.2 Priority Uplink Request with cause priority higher than current talker priority + +On receipt of a PRIORITY UPLINK REQUEST message the network stops timer T3101 and releases the dedicated signalling link established by the MS. The RR entity of the network shall analyse the message and provide the message parameters to the upper layer. The network shall perform contention resolution, if necessary. The network shall release the current talker and grant the uplink to one mobile station by sending a VGCS UPLINK GRANT message to the mobile station in unacknowledged mode on the main signalling link. The VGCS UPLINK GRANT shall contain the request reference parameter with the random reference set to the value received in the PRIORITY UPLINK REQUEST and the frame number of the frame in which the CHANNEL REQUEST message was sent to establish the dedicated signalling link. + +After having sent the first message, the network starts T3115. If the timer expires before the reception of a correctly decoded frame from the MS, the network repeats the VGCS UPLINK GRANT message to the mobile station, reset and restarts timer T3115. If the VGCS UPLINK GRANT message has been repeated Ny2 times without a correctly decoded frame being received from the MS, the network shall stop sending VGCS UPLINK GRANT messages. The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no error. + +After the data link layer is established, the RR entity of the network shall analyse the TALKER INDICATION message received from the mobile station, adapt the RR procedures to the new classmark if necessary and provide the mobile subscriber identity and ciphering key sequence number to the upper layer. + +The network shall provide UPLINK BUSY messages on the main signalling link in all cells of the group call area, containing the latest validated priority. The UPLINK BUSY message shall be transmitted every T3151 seconds. + +#### 3.3.1.2.2b.2.3 Priority Uplink Request with cause Emergency mode reset request + +On receipt of a PRIORITY UPLINK REQUEST message with cause Reset Emergency Talker Indication the network stops timer T3101 and releases the dedicated signalling link established by the MS. The RR entity of the network shall analyse the message and provide the message parameters to the upper layer. The network shall perform contention resolution, if necessary, and reset the Emergency Indication of the group call. The current talker is not released. + +#### 3.3.1.2.2b.2.4 Validation of Priority Uplink Requests for ciphered voice group calls + +When validation of priority uplink requests is required by the operator, the network shall broadcast a randomly generated 32bit token in an UPLINK BUSY message each time the uplink becomes busy after being free. The 32bit token is randomly generated on a per BSS basis. A new token shall subsequently be broadcast each time a periodic UPLINK BUSY message is sent (i.e. every T3151 seconds). If, on T3151 expiry, the old token has not been used it remains valid for a further T3157 seconds along with the new token. Once T3157 expires only the new token is valid. + +On receipt of a PRIORITY UPLINK REQUEST message the network stops timer T3101 and releases the dedicated signalling link established by the MS. The RR entity of the network shall analyse the message and if a token is received in the message and it matches that stored in the network, the network shall provide the message parameters to the upper layer and continue handling the request as defined in 3.3.1.2.2b.2.2 and 3.3.1.2.2b.2.3. In addition, a new token and the priority of the accepted request is broadcast in an UPLINK BUSY message on the main signalling link after T3155 seconds and T3151 is reset and restarted. If a token is not received in the message, or the token received does not match that stored in the network, the network shall ignore the request. + +The dedicated signalling link established by the MS is always acknowledged and released by sending UA (Priority Uplink Request) followed by Channel Release, whether or not the network accepts or ignores the request. + +### 3.3.1.2.2c Network side – network supports sending application-specific data by mobile station + +#### 3.3.1.2.2c.1 General + +The transmission of application-specific data by the mobile station in group receive mode to the network is carried out by the mobile temporarily leaving group receive mode, establishing a L2 connection and sending a L3 message containing the application-specific data in the SABM frame used to establish the main signalling link on a dedicated channel. The dedicated channel may be either the group call channel or another channel assigned by the network. + +The network shall send UPLINK BUSY messages every T3151 seconds in all cells in the group call area while the uplink for this group call is busy in any cell. + +The mobile station behaviour is described in sub-clause 3.3.1.2.1.2c. + +### 3.3.1.2.2c.2 Using the Voice Group Call Channel + +On receipt of an UPLINK ACCESS message on the voice group call channel indicating a cause "UL request for sending application-specific data" the network shall grant the uplink of the voice group channel by sending a VGCS UPLINK GRANT message to the mobile station in unacknowledged mode on the main signalling link. After the data link layer is established (see sub-clauses 3.3.1.2.1.2c.2 and 3.1.5) the BSS releases the uplink channel by sending an UPLINK RELEASE message. + +### 3.3.1.2.2c.3 Using the RACH + +On receipt of a CHANNEL REQUEST message with the appropriate establishment cause for sending application-specific data (see sub-clause 9.1.8), the BSS shall allocate a channel to the mobile station by sending an IMMEDIATE ASSIGNMENT message. As soon as contention resolution is completed (see sub-clause 3.1.5 and 3.3.1.2.1.2c.3) and the data link layer is established, the BSS sends an CHANNEL RELEASE message to the mobile. + +### 3.3.1.2.3 Abnormal cases + +If a lower link failure has occurred or an indication of the release of the data link layer was provided by the lower layer and no RR release request was previously received from the upper layer, the network shall provide an UPLINK FREE message on the main signalling channel and wait for a new UPLINK ACCESS message. + +The network shall discard an UPLINK ACCESS message or PRIORITY UPLINK REQUEST message that contains an unknown cause field. + +### 3.3.1.3 Dedicated mode and GPRS + +A mobile station whose Channel Request message contained a packet access establishment cause may receive an Immediate Assignment message to a Channel which is to be used in dedicated mode. A mobile station supporting the "GPRS" option shall not obey this command. + +### 3.3.1.4 Preliminary Access Barring Check + +The preliminary access barring check shall indicate network access is barred if all of the following conditions are satisfied: + +- the establishment cause for the request received from the MM sublayer is not "emergency call". +- the SYSTEM INFORMATION TYPE 21 message is broadcast in the cell and includes EAB information; +- the mobile station is a member of a subcategory of mobile stations targeted by the EAB information; +- the EAB Authorization Mask sent in the EAB information indicates the mobile station's access class is not authorized; +- the mobile station is not a member of any of the authorized special access classes (i.e. an Access Class in the range 11-15) permitted by the network; + +Otherwise, the preliminary access barring check shall indicate network access is not barred. + +When network sharing is in use in the cell, a mobile station supporting network sharing shall check the above conditions using the broadcast information corresponding to the selected PLMN. + +## 3.3.2 Paging procedure for RR connection establishment + +The network can initiate the establishment of an RR connection by the paging procedure for RR connection establishment. Such a procedure can only be initiated by the network. + +### 3.3.2.1 Paging initiation by the network + +The network initiates the paging procedure to trigger RR connection establishment by broadcasting a paging request message on the appropriate paging subchannel on CCCH or PCCCH, and starts timer T3113. The paging subchannels on CCCH and PCCCH are specified in 3GPP TS 45.002 and 3GPP TS 43.013. + +The network may also send paging related information on PACCH to a mobile station in packet transfer mode, see sub-clause 3.3.2.1.3. + +The network may also broadcast paging related information on any voice broadcast or voice group call channel downlink. The network shall indicate in the Notification/FACCH message sent on the voice broadcast or voice group call channel whether the paging is for a mobile terminating call, USSD or short message, if such information was provided to the BSS by the MSC in the Paging Information IE (see 3GPP TS 48.008). + +#### 3.3.2.1.1 Paging initiation using paging subchannel on CCCH + +Paging initiation using the paging subchannel on CCCH is used when sending paging information to a mobile station in idle mode. It is also used when sending paging information to a mobile station in packet idle mode, if PCCCH is not present in the cell. + +NOTE 1: There are 3 types of paging messages which may be used on CCCH: + +- PAGING REQUEST TYPE 1; +- PAGING REQUEST TYPE 2; and +- PAGING REQUEST TYPE 3. + +In a PAGING REQUEST message on CCCH to trigger RR connection establishment, the mobile station shall be identified by the TMSI (non-GPRS TMSI) or its IMSI. If the mobile station is identified by the TMSI, it shall proceed as specified in sub-clause 3.3.2.2. + +If the mobile station in packet idle mode is identified by its IMSI, it shall parse the message for a corresponding *Packet Page Indication* field: + +- if the Packet Page Indication field indicates a paging procedure for RR connection establishment, or the field is not present in the message, the mobile station shall proceed as specified in sub-clause 3.3.2.2; +- if the Packet Page Indication field indicates a packet paging procedure, the mobile station shall proceed as specified in sub-clause 3.5.1.2. + +A PAGING REQUEST message on CCCH includes for each mobile station that is paged to trigger RR connection establishment an indication which defines how mobiles of different capabilities shall code the establishment cause field in the CHANNEL REQUEST message. The information received in the CHANNEL REQUEST can be used by the network to assign a suitable channel. + +A PAGING REQUEST message on CCCH may include more than one mobile station identification. + +A PAGING REQUEST TYPE 1 message on CCCH may have additionally a notification message coded in the P1 rest octets information element. The notification for one group call may be segmented over two PCH blocks. When the notification is segmented over two PCH blocks the second segment shall be sent at the next but one PCH block after the PCH block containing the first segment. The mobile station may receive the second segment before the first segment. + +A PAGING REQUEST message on CCCH may also include priority levels related to the mobile station identifications. A mobile station in group receive mode supporting eMLPP shall take into account this information to decide whether to respond to this PAGING REQUEST and, if the call is answered, the mobile station shall store the priority level for the duration of the call. A mobile station not supporting eMLPP shall ignore this information element when received in a PAGING REQUEST message. + +NOTE 2: A mobile station not supporting VGCS or VBS may ignore this information element when received in a PAGING REQUEST message, since the priority level is also provided in the SETUP message. + +If VGCS or VBS is supported by the network, messages sent on the PCH may also include an indication of the change of the information sent on the NCH (see sub-clause 3.3.3.2). + +The choice of the message type depends on the number of mobile stations to be paged and of the types of identities that are used. The maximum number of paged mobile stations per message is 4 when using only TMSIs for identification of the mobile stations. + +The mobile station in idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannel corresponding to its paging subgroup, as specified in 3GPP TS 45.002. + +NOTE 3: The possible immediate assignment messages are: the IMMEDIATE ASSIGNMENT, the IMMEDIATE ASSIGNMENT EXTENDED and the IMMEDIATE ASSIGNMENT REJECT messages. + +The paging and immediate assignment type messages contain a page mode information element. This information element controls possible additional requirements on mobile stations belonging to the paging subgroup corresponding to the paging subchannel the message was sent on. This implies that a given mobile station shall take into account the page mode information element of any message sent on its own paging subchannel whatever the nature of this message (paging messages or immediate assignment messages). This further implies that the mobile station does not take into account page mode information element of messages sent on paging subchannels other than its own paging subchannel. The requirements yielded by the page mode information element are as follows: + +- a) normal paging: no additional requirements; +- b) extended paging: the mobile station is required in addition to receive and analyse the next but one message on the PCH; +- c) paging reorganization: The mobile station shall receive all messages on the CCCH regardless of the BS-AG-BLKS-RES setting. It is required to receive all BCCH messages. When the mobile station receives the next message to its (possibly new) paging subgroup the subsequent action is defined in the page mode information element in that message; +- d) same as before: No change of page mode from the previous page mode. + +Note that a mobile station takes into account the page mode information only in messages of its own paging subchannel whatever the currently applied requirements (a, b, c or d). + +When the mobile station selects a new PCH, the initial page mode in the mobile station shall be set to paging reorganization. If a message in the paging subchannel is not received correctly, the message is ignored and the previous page mode is assumed. + +### 3.3.2.1.2 Paging initiation using paging subchannel on PCCCH + +Paging initiation using a paging subchannel on PCCCH, see 3GPP TS 44.060, applies when sending paging information to a mobile station in packet idle mode and PCCCH is provided in the cell. + +The paging initiation procedure and the paging request message used on PCCCH are specified in 3GPP TS 44.060. + +### 3.3.2.1.3 Paging initiation using PACCH + +Paging initiation using PACCH, see 3GPP TS 44.060, applies to a mobile station in packet transfer mode or in broadcast/multicast receive mode if so ordered by the network. + +The paging initiation procedure and the message used to carry paging related information on PACCH are specified in 3GPP TS 44.060. + +### 3.3.2.2 Paging response + +Upon receipt of a paging request message, or other message containing information to trigger the establishment of a RR connection, and if access to the network is allowed, the addressed mobile station shall, when camped on a cell as specified in 3GPP TS 23.022, initiate the immediate assignment procedure as specified in sub-clause 3.3.1. The establishment of the main signalling link is then initiated by use of an SABM with information field containing the PAGING RESPONSE message (see sub-clause 3.1.5). The MM sublayer in the mobile station is informed that the RR entity has entered the dedicated mode. + +If the PAGING RESPONSE message is being sent as part of a CS FallBack procedure, then the mobile station shall set the CSMT flag in the *Additional Update Parameters IE*. + +Upon receipt of the PAGING RESPONSE message the network stops timer T3113. The MM sublayer in the network is informed that an RR connection exists. + +### 3.3.2.3 Abnormal cases + +Lower layer failure occurring during the immediate assignment procedure is treated as specified for that procedure. + +If timer T3113 expires and a PAGING RESPONSE message has not been received, the network may repeat the paging request message and start timer T3113 again. The number of successive paging attempts is a network dependent choice. + +![Sequence diagram of the paging procedure between a mobile station and a network.](e05434e963901d7e9c0bf5a6758200ed_img.jpg) + +``` + +sequenceDiagram + participant mobile station + participant network + Note right of network: Start T3113 + network->>mobile station: PAGING REQUEST + mobile station->>network: RANDOM ACCESS + Note right of network: Start T3101 + network->>mobile station: IMM ASSIGN + mobile station->>network: SABM (PAGING RESPONSE) + Note right of network: Stop T3101, T3113 + +``` + +The diagram illustrates the interaction between a mobile station and a network during a paging procedure. It starts with the network sending a PAGING REQUEST to the mobile station, at which point the network starts timer T3113. The mobile station responds with a RANDOM ACCESS message. The network then sends an IMM ASSIGN message, starting timer T3101. Finally, the mobile station sends a SABM (PAGING RESPONSE) message, which causes the network to stop both timers T3101 and T3113. + +Sequence diagram of the paging procedure between a mobile station and a network. + +Figure 3.3.2.3.1: Paging sequence + +### 3.3.3 Notification procedure + +The support of notification procedure is mandatory for mobile stations supporting "VGCS receive" and/or "VBS receive". + +The network informs the mobile station of starting or on-going voice broadcast calls and voice group calls with the notification procedure. + +In cases where the mobile station has initiated a VGCS call, if the channel mode modify procedure is applied to turn the dedicated channel into a VGCS channel and ciphering may be applied for that call, in this case the network should suspend transmission of notification messages until ciphering with the group cipher key has started on the group channel. + +#### 3.3.3.1 Notification of a call + +The mobile station may receive a notification that a voice broadcast call or a voice group call is established. Notifications may be sent on the NCH, on the PCH, or on the FACCH when in dedicated mode or group receive mode. The presence of an NCH is indicated on the PCH in the Pi Rest Octets IE. A notification contains the group call reference and possibly other related information. This notification may be contained: + +- in a NOTIFICATION/NCH message sent on the NCH to notify mobile stations of VBS or VGCS calls in the current cell, possibly together with a description of the related VBS or VGCS channel, and if the call is ciphered the value of the related VSTK\_RAND and CELL\_GLOBAL\_COUNT. If talker priority is supported by the network then the notification shall contain the status of the emergency mode if the emergency mode is set and the priority uplink access method. When the notification is segmented over two Notification/NCH messages, the status of the emergency mode shall only be present in the block that contains the group channel description; If the group call is using AMR in the cell then this shall be indicated in the description of the VGCS/VBS channel together with an indication of whether the channel is FR or HR. The notification may indicate whether or not SMS data confidentiality and SMS guaranteed privacy are required. +- in a NOTIFICATION/FACCH message sent in unacknowledged mode on the main DCCH to notify mobile stations in dedicated mode or on the main DCCH of a VGCS or VBS channel, of another VBS or VGCS call in the current cell, possibly together with a description of the related VBS or VGCS channel, and if the call is ciphered the value of the related VSTK\_RAND, CELL\_GLOBAL\_COUNT and bit 22 of COUNT (related to TDMA frame number as defined in 3GPP TS 43.020). If talker priority is supported by the network then the notification shall contain the status of the emergency mode and the priority uplink access method; The + +notification shall also contain the AMR codec configuration if the notifications contains a channel description that indicates that AMR is being used. The notification may indicate whether or not SMS data confidentiality and SMS guaranteed privacy are required. + +- in the rest octets part of a PAGING REQUEST TYPE 1 message. The notification may contain a description of the related VBS or VGCS channel and if the call is ciphered the value of the related VSTK\_RAND and the CELL\_GLOBAL\_COUNT. The notification shall also contain the AMR codec configuration if the notifications contains a channel description that indicates that AMR is being used. + +If the contents of the notification cannot be contained within one message, then the notification can be segmented as described in 3.3.3.2.2. + +When the network supports ciphered group calls the CELL\_GLOBAL\_COUNT shall be provided on the NCH. When the MS camps on a cell it should read the NCH and determine if CELL\_GLOBAL\_COUNT is provided. + +When the MS obtains its CELL\_GLOBAL\_COUNT via a message on the main DCCH that contains the VGCS Ciphering Parameters information element, it must check if the CELL\_GLOBAL\_COUNT provided in the message is up to date by comparing bit 22 of COUNT in the message with the actual value of COUNT. If the value of bit 22 of COUNT in the message is '1' but the actual value is '0', then the value of CELL\_GLOBAL\_COUNT obtained from any of the above messages on the main DCCH shall be incremented by one (modulo 4). + +The CELL\_GLOBAL\_COUNT is optionally transmitted in the PAGING REQUEST TYPE 1 message on the PCH and in the Notification/FACCH message when these messages contain a notification for a ciphered group call. If the group call is ciphered but the CELL\_GLOBAL\_COUNT is not provided in notification on the PCH, then the mobile station may obtain the CELL\_GLOBAL\_COUNT from the NCH, if not already obtained. + +The notifications for ciphered group calls that contain a group channel description shall also contain the VSTK\_RAND. + +Once the MS has obtained the CELL\_GLOBAL\_COUNT for the serving cell it shall maintain its own copy of the parameter, incrementing the CELL\_GLOBAL\_COUNT by one (modulo 4) each time bit 22 of COUNT changes from '1' to '0'. + +Only one AMR codec configuration is allowed per cell for all VGCS/VBS calls using FR AMR and one for all VGCS/VBS calls using HR AMR. + +A mobile station supporting neither VGCS listening nor VBS listening may ignore the notifications sent on the NCH or PCH. It may also ignore the notifications sent on the main DCCH except that a RR-STATUS message shall be sent to the network with cause #97, "message not existent or not implemented". + +Upon receipt of every notification message a mobile station supporting VGCS listening or VBS listening shall give an indication containing the notified group call reference(s) to upper layers in the mobile station. + +### 3.3.3.2 Joining a VGCS or VBS call + +#### 3.3.3.2.1 General + +In order to join a VGCS or a VBS call the following procedures apply. + +In this sub-clause, the term **notification** refers to the notification which has triggered the decision to join a VGCS or VBS call. The notification for one VGCS/VBS call may be segmented across two messages, as described in sub-clause 3.3.3.2.2. + +If the notification on the main DCCH concerns a VBS or VGCS in the current cell and does not contain a description of the VGCS or VBS channel, the mobile station shall read the corresponding notification on the NCH. If the notification is for a VGCS/VBS call that is ciphered and contains a description of the VGCS or VBS channel but the ciphering mechanism parameters (VSTK\_RAND or CELL\_GLOBAL\_COUNT) or the corresponding group key on the USIM are not available, then the notification shall be discarded. + +If the description of the VGCS or VBS channel was included in the notification for the current cell, RR connection establishment shall not be initiated, instead, the mobile station shall enter the group receive mode, unless the group call is ciphered and the ciphering mechanism parameters (ie VSTK\_RAND or CELL\_GLOBAL\_COUNT) or the corresponding group key on the USIM are not available. In this case the notification shall be discarded. + +If no description for the VGCS or VBS channel is included in the notification, the mobile station shall establish a RR connection in dedicated mode in order to initiate the notification response procedure. + +When the group call is ciphered then the MS shall calculate the ciphering keys for use on the group channel using the group key with the following parameters, as described in 3GPP TS 43.020: + +- VSTK\_RAND (provided in the notification); +- CELL\_GLOBAL\_COUNT (provided in the notification); +- Cell Global Identifier (CGI) (provided in system information type 3 and 4); +- Group Cipher Key Number (provided in the group call reference that is contained within the notification). + +The group cipher keys need to be recalculated whenever CELL\_GLOBAL\_COUNT changes. The MS obtains the identity of its ciphering algorithm from its USIM, as described in 3GPP TS 43.020. + +When the VGCS mobile station is allocated a dedicated channel that is ciphered, the channel shall be ciphered with the individual ciphering keys of this mobile station. + +In the case that AMR is used on the VGCS/VBS group channel, the mobile station shall obtain the AMR codec configuration for the channel. This configuration may be obtained the notification/NCH, notification/FACCH, Notification/PCH, the Channel Release message or from the system information type 6 message. The network shall provide the configuration in the system information type 6 message if AMR is being used on the VGCS/VBS channel. Additionally, the mobile station shall set the codec configuration parameters Noise Suppression Control Bit (NSCB) and the Initial Codec Mode Indicator (ICMI) to 0 (see subclause 10.5.2.21aa, MultiRate configuration). + +### 3.3.3.2.2 Segmentation of notifications + +#### 3.3.3.2.2.1 General + +Segmented notifications are only applicable to ciphered group calls. The second segment is used to contain additional parameters related to the VGCS ciphering mechanism (VSTK\_RAND, CELL\_GLOBAL\_COUNT). + +Notifications can be segmented on the NCH, FACCH and PCH as described in the following sub-clauses. All segments of a segmented notification shall be transmitted and reassembled on the same logical channel (ie NCH, FACCH or PCH). + +#### 3.3.3.2.2.2 Segmentation of notifications on NCH + +The first segment of a segmented notification on the NCH contains the following fields; + +- Group call Reference with group channel description; +- Indication that the group call is a ciphered group call, as indicated by Group Cipher Key within the group call reference; +- Optionally CELL\_GLOBAL\_COUNT; +- Segment Id is set to 0; +- Status of the Emergency mode if talker priority is supported by the network and emergency mode is set; +- Priority uplink access method, if talker priority or sending of application data is supported by the network; +- Indication of whether AMR is being used (either FR or HR); +- Indication of whether or not SMS data confidentiality is required; +- Indication of whether or not SMS guaranteed privacy is required. + +The second segment of a segmented notification on the NCH contains the following fields: + +- Same Group call reference as first segment or a Reduced Group Call reference that contains the same group or broadcast call reference and service flag as contained in the Group Call Reference in the first segment. +- No group channel description; +- VSTK\_RAND and optionally CELL\_GLOBAL\_COUNT; + +- Segment Id is set to 1. + +When the MS receives a segment of a segmented notification for a group call that it is a member of and for which no previous segment has been received, it shall store the received segment and start timer T3206 for the given group call. The MS shall stop timer T3206 in any of the following cases + +- The MS joins another group call; +- The MS reselects to another cell; +- The value of NLN changes; +- The MS receives the missing segment. + +If timer T3206 expires, or if the MS has to stop T3206 for any other reason than receiving the missing segment, the MS shall discard the associated stored segment. + +### 3.3.3.2.2.3 Segmentation of notifications on FACCH + +The first segment of a segmented notification on the FACCH contains the following fields; + +- Group call reference with group channel description; +- Indication that the group call is a ciphered group call, as indicated by Group Cipher Key Number within the group call reference; +- Optionally CELL\_GLOBAL\_COUNT; +- Status of the Emergency mode if talker priority supported by the network ; +- Priority uplink access method for talker priority-related uplink access requests, if talker priority is supported by the network; +- AMR codec configuration, if the group channel description indicates that AMR is being used (either FR or HR); +- Indication of whether or not SMS data confidentiality is required; +- Indication of whether or not SMS guaranteed privacy is required. + +The second segment of a segmented notification on the FACCH contains the following fields: + +- Same group call reference as first segment, with no group channel description; +- VSTK\_RAND and optionally CELL\_GLOBAL\_COUNT. + +When the MS receives the first segment of a segmented notification for a group call that it is a member of, it shall store the received segment and start timer T3208 for the given group call. The MS shall stop timer T3208 in any of the following cases + +- The MS joins another call; +- The MS performs handover to another cell; +- The MS receives the associated second segment; +- The MS receives a VGCS Reconfigure message. + +If timer T3208 expires, or if the MS has to stop T3208 for any other reason than receiving the second segment, the MS shall discard the associated stored segment. If the MS wants to join this group call at expiry of T3208, it shall read the NCH to obtain the full description of the group call. + +When the MS receives the second segment of a notification of a group call that it is member of before receiving the associated first segment then the MS shall discard the second segment. If the MS wants to join this group call it shall read the NCH to obtain the full description of the group call. + +### 3.3.3.2.2.3 Segmentation of notifications on PCH + +The first segment of a segmented notification on the PCH contains the following fields; + +- Group call reference and group channel description; + +- Indication that the group call is a ciphered group call, as indicated by Group Cipher Key within the group call reference; +- Optionally CELL\_GLOBAL\_COUNT; +- AMR codec configuration, if the group channel description indicates that AMR is being used (either FR or HR). + +The MS determines that the message contains the first segment of a segmented notification if the message contains both an indication that the group call is ciphered and the group channel description, but does not contain the VSTK\_RAND. + +The second segment of a segmented notification on the PCH contains the following fields: + +- Same group call reference as first segment, or reduced group call reference; +- VSTK\_RAND and optionally CELL\_GLOBAL\_COUNT. + +The MS determines that the message contains the second segment of a segmented notification if the message contains both an indication that the group call is ciphered and the VSTK\_RAND, but does not contain the group channel description. + +The MS shall only combine the first segment of the notification with the second segment if they have the same group call reference. + +When the MS receives the first segment of a notification of a group call that it is member of but the second segment is not correctly received at the next but one PCH block after receiving the first segment, and the MS wants to join this group call, then the MS may either read further PCH blocks in an attempt to find the missing segment or read the NCH to obtain the full description of the group call. When the MS reads further blocks on the PCH to find the missing segment, the MS shall start timer T3210. If timer T3210 expires, the associated segment shall be discarded and the MS shall stop reading the PCH for the missing segment. + +When the MS receives the second segment of a notification of a group call that it is member of before receiving the associated first segment, and the MS wants to join this group call, then the MS may either read further PCH blocks in an attempt to find the missing segment or read the NCH to obtain the full description of the group call. When the MS reads further blocks on the PCH to find the missing segment, the MS shall start timer T3210. If timer T3210 expires, the associated segment shall be discarded and the MS shall stop reading the PCH for the missing segment. + +The MS shall stop timer T3210 if: + +- The missing segment is correctly received; +- The MS leaves Idle mode (the MS discards the associated segment); +- The MS determines that notifications for another group call are being sent on the PCH (the MS discards the associated segment). + +### 3.3.3.3 Reduced NCH monitoring mechanism + +This sub-clause applies to mobile stations which read the NCH in idle mode in order to receive the notification messages for the voice broadcast call and the voice group call, which read the PCH or PPCH to receive pagings and which aim at reducing the reception load. + +A reduced NCH monitoring mechanism shall be used on the NCH. When the mobile station in idle mode enters a cell and deduces from the BCCH that an NCH is present, it shall read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical. Then it may stop reading the NCH until it receives on the PCH an NLN(PCH) different from the last previously received NLN or on the SACCH an NLN(SACCH) different from the last previously received NLN or on the PPCH an NLN(PPCH) different from the last previously received NLN. + +For this, parameters are provided: + +- NLN:** Notification List Number. The NLN is a modulo 4 counter. A change of NLN indicates that new notifications are provided on the NCH. The network shall ensure that a mobile station receives the NLN as often as necessary for a good functioning of the reduced monitoring. + +**NLN status:** The NLN status is a single bit field which indicates the status of the content of the NOTIFICATION/NCH messages for a particular NLN value. A change of the NLN status field indicates a change of information on the NCH which is not related to new calls (e.g. There may have been a release of a previous notified call, a change in status of the emergency mode etc...). + +The network has to provide both NLN and NLN status parameters. + +These parameters are defined on the NCH, PCH, SACCH and PPCH: + +**NLN(NCH):** Notification List Number (contained in certain NOTIFICATION messages on the NCH as required by the reduced NCH monitoring function). + +**NLN(PCH):** Notification List Number (contained in all PAGING REQUEST TYPE 2 messages, PAGING REQUEST TYPE 3 messages and those PAGING REQUEST TYPE 1 messages with P1 rest octets value part of length $\geq 1$ on the PCH). + +**NLN(SACCH):** Notification List Number (contained in all SYSTEM INFORMATION TYPE 6 messages on the SACCH when there are NCH blocks allocated ). + +**NLN(PPCH):** Notification List Number (contained in all PACKET PAGING REQUEST messages containing at least one page request for an RR connection establishment and optionally contained in other PACKET PAGING REQUEST messages). + +**NLN status(PCH):** NLN status (contained in all PAGING REQUEST TYPE 2 messages, PAGING REQUEST TYPE 3 messages and those PAGING REQUEST TYPE 1 messages with P1 rest octets value part of length $\geq 1$ on the PCH). + +**NLN status(SACCH):** NLN status (contained in all SYSTEM INFORMATION TYPE 6 messages on the SACCH when there are NCH blocks allocated). + +**NLN status(PPCH):** NLN status (contained in all PACKET PAGING REQUEST messages containing at least one page request for an RR connection establishment and optionally contained in other PACKET PAGING REQUEST messages). + +When there are no VGCS or VBS calls active in the cell, the network shall transmit notification messages with an empty notification list (not necessarily in every NCH block) but with NLN(NCH). + +A mobile station supporting neither VGCS listening nor VBS listening shall ignore the NLN(NCH),NLN(PCH), NLN(SACCH), NLN(PPCH) and NLN status fields. + +If a mobile station (supporting VGCS listening and/or VBS listening) receives a NLN parameters on the NLN(PCH) or NLN(SACCH) or NLN(PPCH) field different from the last received NLN value it shall read the NCH until it has received at least two messages on the NCH indicating NLN with the two last received NLN being identical. + +If a message in the paging subchannel on CCCH is not received correctly, or if a paging message on CCCH does not contain the information on the notification status, the mobile station shall read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical. + +If a message in the paging subchannel on PCCCH is not received correctly and the mobile station has previously received notification status on PCCCH in that cell, the mobile station shall read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical. + +If a packet paging message on PCCCH contains at least one page request for an RR connection establishment and does not contain the information on the notification status, the mobile station shall assume that information on the notification status on PCCCH is not provided in this cell. In this case the mobile shall perform reduced NCH mechanism by reading NLN(PCH) and NLN status(PCH) on PCH until the MS received information on the notification status on PCCCH. + +### 3.3.3.4 Notification response procedure + +In order to initiate the notification response procedure, if access to the network is allowed, the mobile station shall, when camped on a cell as specified in 3GPP TS 43.022, initiate the immediate assignment procedure as specified in 3.3.1. The establishment of the main signalling link is then initiated by use of an SABM with information field containing the NOTIFICATION RESPONSE message (see sub-clause 3.1.5). The Group or Broadcast Call Reference + +and the Service Flag in the *Descriptive Group or Broadcast Call Reference* Information Element shall be identical as received in the corresponding IE in the notification or paging messages. The MM sublayer in the mobile station is informed that the RR entity has entered the dedicated mode. + +Upon receipt of the NOTIFICATION RESPONSE message the network stops timer T3101. The MM sublayer in the network may be informed that an RR connection exists; in this case, the MM sublayer may initiate MM common procedures. + +The network may use the dedicated connection to order the mobile station to enter the group receive mode. + +## 3.4 Procedures in dedicated mode and in group transmit mode + +Procedures described in this sub-clause apply to the dedicated mode and/or the group transmit mode. + +Those procedures which are specific for group transmit mode or refer to transitions to the group transmit mode are only applicable for mobile stations supporting VGCS talking. + +Direct transition between dedicated mode and group transmit mode is possible in both directions by use of the following procedures: + +- Channel assignment procedure; +- Handover procedure; +- Channel mode modify procedure. + +### 3.4.1 SACCH procedures + +#### 3.4.1.1 General + +In dedicated mode and group transmit mode, the SACCH is used in signalling layer at least for measurement results transmission from the mobile station. + +The SACCH has the particularity that continuous transmission must occur in both directions at least on the channel carrying the main signalling link. For that purpose, in the mobile station to network direction, measurement result messages are sent at each possible occasion when nothing else has to be sent (see sub-clause 3.4.1.2). Similarly, SYSTEM INFORMATION TYPE 5, 6 and optionally 5bis and 5ter messages are sent in the network to mobile station direction in UI frames when nothing else has to be sent. + +The network may in addition send MEASUREMENT INFORMATION messages on the SACCH, which may order the MS to use the enhanced measurement report. + +In a multislot configuration the SYSTEM INFORMATION TYPE 5, 6 and optionally 5bis, 5ter and MEASUREMENT INFORMATION messages shall be sent on the SACCH associated with the channel carrying the main signalling link. + +In a multislot configuration the mobile station shall ignore all messages received on the SACCH(s) that are not associated with the channel carrying the main signalling link. + +On a VGCS channel, the network may send additional or alternative system information messages for both mobile stations in group transmit mode and those in group receive mode (see sub-clause 3.4.15.2.1). + +A mobile station with extended measurement capabilities which receives EXTENDED MEASUREMENT ORDER (EMO) messages on the SACCH, shall perform and report extended measurements, see sub-clause 3.4.1.3. + +The SYSTEM INFORMATION TYPE 5bis message shall be sent if and only if the EXT IND bit in the Neighbour Cell Description information element in both the SYSTEM INFORMATION TYPE 5 and TYPE 5bis messages indicates that each information element only carries part of the BA. + +A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may consider the EXT-IND bit in the Neighbour cell description IE in the SYSTEM INFORMATION TYPE 5 message bit as a spare bit, assume that the information element carries the complete BA, and ignore any SYSTEM INFORMATION TYPE 5bis messages. + +NOTE: The network should take into account limitations of certain mobile stations to understand SYSTEM INFORMATION TYPE 5ter and TYPE 5bis messages, the EXT-IND bit in the Neighbour cell description, and formats used in the Neighbour cell description information element and Cell Channel Description information element used in SYSTEM INFORMATION messages, see sub-clause 10.5.2.1b, and sub-clause 10.5.2.22. + +Problems occurring in the reception of SACCH frames are interpreted as a loss of communication means and appropriate procedures are then triggered as specified in 3GPP TS 45.008. + +### 3.4.1.2 Measurement Report and Enhanced Measurement Report + +When in dedicated mode or group transmit mode, the mobile station regularly sends either MEASUREMENT REPORT or ENHANCED MEASUREMENT REPORT messages to the network. These messages contain measurement results about reception characteristics from the current cell and from neighbour cells. The BA (list) which is the initial basis for the measurements is derived from information received on the BCCH in System Information 2 and optionally 2bis and/or 2ter messages and on the SACCH in System Information 5 and optionally 5bis and/or 5ter messages. MEASUREMENT INFORMATION and SI2quater messages may add information for the GSM Neighbour Cell List and provide 3G Neighbour Cell list and/or E-UTRAN Neighbour Cell list. If System Information 23 message is broadcast in the cell, a mobile station supporting network sharing shall build the 3G Neighbour Cell list and/or E-UTRAN Neighbour Cell list as described in sub-clause 3.4.1.2.1. + +The Mobile Station shall use ENHANCED MEASUREMENT REPORT messages instead of MEASUREMENT REPORT messages if that is indicated by the parameter REPORT\_TYPE and if at least one BSIC is allocated to each BA (list) frequency. For report with the MEASUREMENT REPORT message, reporting is performed on three separate lists: the BA (list), the 3G Neighbour Cell List (for a multi-RAT MS supporting UTRAN) and the E-UTRAN Neighbour Cell list (for a multi-RAT MS supporting "E-UTRA Measurement and Reporting"). For report with the ENHANCED MEASUREMENT REPORT message, reporting is performed on the Neighbour Cell List (defined in sub-clause 3.4.1.2.1.3) and the E-UTRAN Neighbour Cell list (for a multi-RAT MS supporting "E-UTRA Measurement and Reporting"). + +The mobile station shall indicate its support for "E-UTRA Measurement and Reporting" in the *Mobile Station Classmark 3 IE* (see 3GPP TS 24.008). + +In addition, the MS with ECSD options implemented shall use fast inband procedure for downlink quality reporting if the use of such procedure has been ordered by the BSC. + +When the information is received in more than one message the mobile station shall only combine information relating to the BA (list) from messages received on the same channel and indicating the same value of the BCCH allocation sequence number (BA\_IND) without any message indicating a different value of BA\_IND received in between. After intracell change of channel (i.e. via ASSIGNMENT COMMAND, DTM ASSIGNMENT COMMAND, or HANDOVER COMMAND message) where the frequency band is not changed (GSM and E-GSM are considered to belong to the same frequency band), the MS may use the BA (list) received on SACCH in system information 5 and optionally 5bis and/or 5ter messages in the previous channel configuration during the time it has not yet received a new list in the new channel. In case the BCCH allocation sequence number (BA\_IND) received in the new channel indicates the same value as the one already being used by the mobile station, the mobile station is not required to re-build the BA(list) in the new channel. If neighbour cell information for the serving cell is not available, the mobile station shall indicate this in the MEASUREMENT REPORT message. These measurement results are obtained as specified in 3GPP TS 45.008. + +These messages are sent on the slow ACCH, in unacknowledged mode. + +If no other message is scheduled on the SACCH at the instant when a layer 2 frame is due to be sent, then the mobile station shall send a MEASUREMENT REPORT message, an ENHANCED MEASUREMENT REPORT or an EXTENDED MEASUREMENT REPORT message (see sub-clause 3.4.1.3) in that frame. The interval between two successive layer 2 frames containing messages for measurement reporting shall not exceed one layer 2 frame. + +#### 3.4.1.2.1 Parameters for Measurements and Reporting + +Parameters from the Measurement Information, SI2quater or SI3quater messages allow an MS to build lists which are used for Measurement reporting, Enhanced Measurement reporting and for CCN mode settings. If the SI23 message is broadcast in the cell and the MS supports network sharing then: + +- a multi-RAT MS supporting E-UTRAN shall use parameters from the SI23 message instead of parameters from the SI2quater message to build the E-UTRAN Neighbour Cell list. + +- a multi-RAT MS supporting UTRAN shall use parameters received in the MEASUREMENT INFORMATION message instead of parameters from the SI2quater message or SI23 message to build the 3G Neighbour Cell list. + +A full set of MEASUREMENT INFORMATION messages is defined by a number of different instances indicated by the parameter MI\_COUNT. Consistent sets of system information messages are defined in 3GPP TS 44.060. Two different instances of MEASUREMENT INFORMATION (respectively: SI2quater and SI23) messages are two MEASUREMENT INFORMATION (respectively: SI2quater and SI23) messages with different MI\_INDEX (respectively: SI2quater\_INDEX and SI23\_INDEX) parameter values. + +In the SI2quater message, the parameters with identical names in the GPRS specific structures (i.e. structures with the prefix GPRS) and in the non-GPRS specific structures (i.e. structures without the prefix GPRS) can have different values. For Measurement reporting and Enhanced Measurement reporting the MS shall ignore the parameters in the GPRS specific structures unless otherwise specified (e.g. sub-clause 3.4.1.2.1.2 and sub-clause 3.4.1.2.1.4). If the SI2quater message is not broadcast or all instances are not yet received or non-GPRS specific parameters in the SI2quater message are omitted, the MS in idle mode or dedicated mode or group transmit mode shall assume the default values defined in 3GPP TS 45.008. + +The parameters for Measurements and Reporting received in a MEASUREMENT INFORMATION message shall override the old values. + +Upon leaving dedicated mode or group transmit mode and entering idle mode, the MS shall delete the parameters received in all instances of the MEASUREMENT INFORMATION message and read the parameters from the SI2quater message and, for an MS supporting network sharing, the parameters from the SI23 message (if broadcast by the network), or use the parameters which were stored before entering the dedicated mode if they are still valid or assume the default values if the SI2quater message is not broadcast or non-GPRS specific parameters are omitted. + +When fast acquisition of system information is not being used in the cell, the following procedures shall apply. The conditions for applying the fast acquisition of system information procedure are described in sub-clause 3.4.1.2.1.11. In Idle mode a multi-RAT MS supporting UTRAN camping on BCCH shall read and decode a consistent set of SI2quater messages to form a 3G Neighbour Cell list (each instance can be used as received). When the 3G\_BA\_IND parameter is changed in idle mode, the MS shall re-read all instances of the consistent set of SI2quater messages and rebuild the 3G Neighbour Cell list. A multi-RAT MS supporting UTRAN camping on PBCCH shall construct the 3G Neighbour Cell list from PSI3quater messages, see 3GPP TS 44.060. This list (either from SI2quater or from PSI3quater) shall then be used for reporting when the MS enters dedicated mode, until the MS has received a given number of instances of MEASUREMENT INFORMATION messages that contain 3G Neighbour Cell Description. This number of instances is defined by the 3G-WAIT parameter. When the 3G\_BA\_IND parameter is changed when on SACCH, the MS shall also re-read all instances, rebuild the 3G Neighbour Cell list, and use the new list for reporting based on the parameter 3G-Wait. + +When the fast acquisition of system information procedure is being used in the cell, the procedure defined in sub-clause 3.4.1.2.1.11 shall be used. + +For the GSM neighbour cell list the MS shall combine the BA (list) received in SI5/SI5bis/SI5ter with the BSIC list received in one or more instances, in ascending order of MI\_INDEX, of the MEASUREMENT INFORMATION message with the same BA\_IND value as the BA (list). When the BA\_IND is changed the MS shall rebuild the combined list (the BSIC list shall also be rebuilt). The GSM neighbour cell list is also defined by the combination of the BA (list) received in SI2/SI2bis/SI2ter and the BSIC list received in one or more instances, in ascending order of SI2quater\_INDEX, of the SI2quater message. When the BA\_IND is changed the MS shall rebuild the combined list (the BSIC list shall also be rebuilt). + +The MS shall combine the BA (list) received in SI5/SI5bis/SI5ter (respectively SI2/SI2bis/SI2ter) messages with the Real Time Differences parameters received in the MEASUREMENT INFORMATION (respectively SI2quater) message with the same BA\_IND value as the BA (list). When the BA\_IND is changed the MS shall re-read the Real Time Differences parameters in all instances. + +The MS shall combine the Neighbour Cell list derived from SI5/SI5bis/SI5ter/MEASUREMENT INFORMATION messages (respectively SI2/SI2bis/SI2ter/SI2quater) with the REP\_PRIORITY parameters received in the MEASUREMENT INFORMATION (respectively SI2quater) message with the same BA\_IND and 3G\_BA\_IND values respectively as the Neighbour Cell list. When the BA\_IND or 3G\_BA\_IND are changed the MS shall re-read the REP\_PRIORITY parameters in all instances. + +The MS shall combine the GSM Neighbour Cell list with the CCN\_SUPPORTED parameters received in the SI2quater messages with the same BA\_IND value as the GSM Neighbour Cell list. When the BA\_IND is changed the MS shall re-read the CCN\_SUPPORTED parameters in all instances. + +If the MP\_CHANGE\_MARK parameter is changed, the MS shall re-read the Real Time differences, REP\_PRIORITY, CCN\_SUPPORTED, Measurement Parameters, 3G Measurement Parameters, Serving Cell Priority Parameters Description (SI2quater message only), 3G Priority Parameters Description (SI2quater message only) and 3G Measurement Control Parameters (MEASUREMENT INFORMATION message only) in all instances. The MS shall start using the parameters as soon as they have been received. In the case that not all the parameters have been received in a full set of instances, then the default values shall be used. + +If the 3G\_BA\_IND parameter is changed a multi-RAT MS supporting E-UTRAN shall re-read the E-UTRAN Parameters Description. If SI23 message is broadcast in the cell a multi-RAT MS supporting network sharing shall re-read the Priority and E-UTRAN Parameters Description of the selected PLMN only when the SI 23\_3G\_BA\_IND parameter in the SI23 message is changed. The MS shall start using the parameters as soon as they have been received. In the case that not all the parameters have been received in a full set of instances, then the default values shall be used. + +When attempting to decode a consistent set of SI2quater (respectively, a full set of MEASUREMENT INFORMATION) messages, if none of the BA\_IND, 3G\_BA\_IND (for a Multi-RAT MS supporting UTRAN and/or E-UTRAN), and MP\_CHANGE\_MARK values obtained from the first received SI2quater (respectively MEASUREMENT INFORMATION) message instance has changed since the previous acquisition then the mobile station can consider the parameters from SI2quater (respectively MEASUREMENT INFORMATION) as unchanged and should not decode the other SI2quater (respectively MEASUREMENT INFORMATION) message instances of the set. + +When attempting to decode a consistent set of SI23 messages, if none of the SI 23\_3G\_BA\_IND and SI 23\_CHANGE\_MARK values obtained from the first received SI23 message instance has changed since the previous acquisition then a multi-RAT mobile station supporting network sharing can consider the parameters from SI23 as unchanged and should not decode the other SI23 message instances of the set. + +#### 3.4.1.2.1.1 Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description sent on BCCH or on SACCH + +This applies only to a multi-RAT MS supporting UTRAN. One or more instances of the MEASUREMENT INFORMATION message or SI2quater message may provide *3G Neighbour Cell Description* information. This information is used to build the 3G Neighbour Cell list. The 3G Neighbour Cell list may contain up to 96 3G Neighbour Cells and/or UTRAN frequencies for RSSI reporting. + +Each *3G Neighbour Cell Description* received in the MEASUREMENT INFORMATION message or in the SI2quater message is added to the 3G Neighbour Cell list, starting with the index equal to the parameter Index\_Start\_3G. If this parameter is not present then the value 0 shall be used. + +For each *3G Neighbour Cell Description*, the cells / UTRAN frequencies received in SI2quater or MEASUREMENT INFORMATION message are indexed in the following order: + +- 1) UTRAN FDD cells / UTRAN FDD frequencies: FDD ARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. For each FDD ARFCN indicating UTRAN FDD cells, the cells are indexed in the order of increasing values of the decoded FDD\_CELL\_INFORMATION parameters. +- 2) UTRAN TDD cells / UTRAN TDD frequencies: TDD ARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. For each TDD ARFCN indicating UTRAN TDD cells, the cells are indexed in the order of increasing values of the decoded TDD\_CELL\_INFORMATION parameters. +- 3) CDMA 2000 cells: the cells are indexed in the order of occurrence in the 3G Neighbour Cell description. + +If a *3G Neighbour Cell Description* includes non-supported frequencies or Radio Access Technologies, this shall not be considered as an error; indices in the 3G Neighbour Cell list shall be incremented accordingly. + +If more than one cell / UTRAN frequency with the same index in the 3G Neighbour Cell list are provided by different instances of *3G Neighbour Cell Descriptions*, the cell / UTRAN frequency from the message instance with the highest index shall be used. In case the same 3G Cell / UTRAN frequency occurs more than once in the resulting 3G Neighbour Cell list, each occurrence shall be assigned an index but only the cell / UTRAN frequency with the highest index in the 3G Neighbour Cell list shall be referred to in measurement reports. + +For a mobile station indicating support for UTRA Multiple Frequency Band Indicators (MFBI) in the MS Classmark 3 IE (see 3GPP TS 24.008), the network may send different FDD ARFCN values corresponding to different frequency bands but designating the same physical UTRAN frequency in the MEASUREMENT INFORMATION message. The network may also broadcast different FDD ARFCN values corresponding to different frequency bands but designating the same physical UTRAN frequency in the SI2quater message; in such a case, a mobile station supporting UTRA Multiple Frequency Band Indicators (MFBI) shall consider a FDD ARFCN value belonging to frequency band it does + +not support as a non-supported frequency. When a MEASUREMENT INFORMATION message or a SI2quater message is received by the MFBI capable MS, each occurrence of a FDD ARFCN corresponding to different frequency bands but designating the same physical UTRAN frequency shall be assigned an index in the 3G Neighbour Cell list. However, only the highest index in the list that corresponds to a supported frequency band shall be referred to in measurement reports. + +If a cell / UTRAN frequency is provided for an index higher than 95 in the 3G Neighbour Cell list, this shall not be considered as an error; the cell / UTRAN frequency shall not be included in the 3G Neighbour Cell list. + +The MS behaviour is not specified if the number of 3G frequencies or cells exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008. + +#### 3.4.1.2.1.1a Deriving the E-UTRAN Neighbour Cell list from the Repeated E-UTRAN Neighbour Cell information sent on BCCH or on SACCH + +This applies only to a multi-RAT MS supporting E-UTRAN. One or more instances of the MEASUREMENT INFORMATION message or SI2quater message may provide E-UTRAN Neighbour Cell Description information in one or more instances of the *Repeated E-UTRAN Neighbour Cells* (respectively for the MEASUREMENT INFORMATION message and if the mobile station and the network supports extended EARFCNs, the *Repeated E-UTRAN NC with extended EARFCNs IE*). This is used to build the E-UTRAN Neighbour Cell list. The fast acquisition of system information procedure, as defined in subclause 3.4.1.2.1.11, shall be used to acquire E-UTRAN measurement parameters and neighbour cell information from SI2quater and MEASUREMENT INFORMATION. + +In the case network sharing is in use in the cell, the SI23 message may provide PLMN specific E-UTRAN frequencies in *Priority and E-UTRAN Parameters Description IE*; when broadcasted in the cell, a multi-RAT MS supporting network sharing shall use this information to build the E-UTRAN Neighbour Cell list for the selected PLMN. When the SYSTEM INFORMATION TYPE 23 message is not broadcasted in the cell, a mobile station supporting network sharing shall use the information provided within the SYSTEM INFORMATION TYPE 2quater message to build the E-UTRAN NCL (see above); the same requirement applies when the mobile station does not support network sharing. + +In the case extended EARFCNs is in use in the cell, the SI2quater message may additionally provide E-UTRAN frequencies within the *Extended EARFCNs Description IE*. A multi-RAT MS supporting extended EARFCNs but not supporting network sharing shall use this information to build the E-UTRAN Neighbour Cell list; the same requirement applies for a multi-RAT MS supporting network sharing when the SI23 message is not broadcasted in the cell. + +The E-UTRAN Neighbour Cell list may contain up to 8 E-UTRAN frequencies. For each E-UTRAN frequency, zero or more E-UTRAN neighbour cells may be specified that are not allowed for cell reselection. The list of not allowed cells is defined in the Not Allowed Cells IEs (alternatively, defined in PLMN-specific *Repeated E-UTRAN Not Allowed Cells* in the SI23 message). + +If a *Priority and E-UTRAN Parameters Description* includes non-supported frequencies or Radio Access Technologies, this shall not be considered as an error; indices in the *Priority and E-UTRAN Parameters Description* shall be incremented accordingly. + +Each EARFCN in each instance of the *Repeated E-UTRAN Neighbour Cells IE* (respectively and if the mobile station and the network supports extended EARFCNs, the *Repeated E-UTRAN NC with extended EARFCNs IE*) is added to the E-UTRAN Neighbour Cell list in the order in which they appear in the IE. Different instances of the Repeated E-UTRAN Neighbour Cells IE shall be evaluated in ascending order of the SI2quater\_INDEX (respectively MI\_INDEX) of the SI2quater (respectively MEASUREMENT INFORMATION) message that they are received in. + +Alternatively, each EARFCN in each instance of the PLMN-specific *Repeated E-UTRAN Neighbour Frequency and Priority IE* in SYSTEM INFORMATION TYPE 23 message is added to the E-UTRAN Neighbour Cell list in the order in which they appear in the IE. Different instances of the PLMN-specific *Repeated E-UTRAN Neighbour Frequency and Priority IE* (respectively and if the mobile station and the network supports extended EARFCNs, the *Repeated E-UTRAN NC with extended EARFCNs IE*) shall be evaluated in ascending order of the SI23\_INDEX (respectively MI\_INDEX) of the SYSTEM INFORMATION TYPE 23 (respectively MEASUREMENT INFORMATION) message instances that they are received in. + +In case the same E-UTRAN frequency occurs more than once in the resulting E-UTRAN Neighbour Cell list, each occurrence shall be assigned an index but only the E-UTRAN frequency with the highest index in the E-UTRAN Neighbour Cell list shall be referred to in measurement reports. + +For a mobile station indicating support for E-UTRA Multiple Frequency Band Indicators (MFBI) in the MS Classmark 3 IE (see 3GPP TS 24.008), the network may send different EARFCN values corresponding to different frequency + +bands but designating the same physical E-UTRAN frequency in the MEASUREMENT INFORMATION message. The network may also broadcast different EARFCN values corresponding to different frequency bands but designating the same physical E-UTRAN frequency in the SI2quater message or SI23 message; in such a case, a mobile station supporting E-UTRA Multiple Frequency Band Indicators (MFBI) shall consider an EARFCN value belonging to frequency band it does not support as a non-supported frequency. When a MEASUREMENT INFORMATION message or a SI2quater message or a SI23 message is received by the MFBI capable MS, each occurrence of an EARFCN corresponding to different frequency bands but designating the same physical E-UTRAN frequency shall be assigned an index in the E-UTRAN Neighbour Cell list. However, only the highest index in the list that corresponds to a supported frequency band shall be referred to in measurement reports. + +The mobile station behaviour is not specified if the number of E-UTRAN frequencies exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008. + +When SI23 message is broadcast in the cell and network sharing is supported by the multi-RAT MS, the MS shall read the SI23 message instances of the selected PLMN in order to build the E-UTRAN Neighbour Cell list. When the SI 23\_BA\_IND parameter is changed in idle mode, the MS shall re-read the SI23 message instances of the selected PLMN and rebuild the E-UTRAN Neighbour Cell list. + +The E-UTRAN Neighbour Cell list derived from the SI23 message shall then be used for measurement reporting when the MS enters dedicated mode, until it has received all relevant instances of the MEASUREMENT INFORMATION message. + +#### 3.4.1.2.1.1b Deriving the E-UTRAN Neighbour Cell list from the Repeated E-UTRAN Neighbour Cell information sent on BCCH or on SACCH (abnormal cases) + +In the case Extended EARFCNs is in use in the cell, the network may broadcast EARFCNs > 65535 within the SI2quater message using the *Extended EARFCNs Description* IE (see table 10.5.2.33b.2). A mobile station supporting Extended EARFCNs and using the SI2quater message to build its E-UTRAN Neighbour Cell list shall manage each EARFCN value 65535 within the *Repeated E-UTRAN Neighbour Cells* IE as described within the table 10.5.2.33b.2. In the case no EARFCN corresponding to the $n^{\text{th}}$ EARFCN value 65535 can be found within the *Extended EARFCNs Description* IE the mobile station shall assume the value 65535 for the $n^{\text{th}}$ EARFCN. + +#### 3.4.1.2.1.2 Deriving the GSM Neighbour Cell list from the BSICs and the BA (list) + +One or more instances of the Measurement Information message may provide BSIC information. This is used to build the GSM Neighbour Cell list. The GSM Neighbour Cell list may contain up to 96 Neighbour Cells. + +The BSICs are associated to the frequencies in the BA (list) with the same BA\_IND value. The BSICs may be received before the corresponding BA (list). The first BSIC in each instance applies to the frequency in the BA (list) referenced by the parameter BA\_Index\_Start\_BSIC. For each successive BSIC, one bit indicates if the BSIC applies to the same frequency as the previous BSIC or to the next frequency in the BA (list), as defined in sub-clause 9.1.54, Measurement Information message. + +In case the same cell (ARFCN+BSIC) occurs more than once in the resulting GSM Neighbour Cell list, each occurrence shall be assigned an GSM Neighbour Cell list index but only the cell with the highest GSM Neighbour Cell list index shall be used and referred to in measurement reports. + +If GPRS BSIC Description is provided in the SI2quater message (see sub-clause 3.4.1.2.1.6), it shall be saved and used by a non-GPRS mobile station as initial BSIC information in connected mode. + +#### 3.4.1.2.1.3 Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list + +For report with the ENHANCED MEASUREMENT REPORT message, the Neighbour Cell list is the concatenation of the GSM Neighbour Cell list and the 3G Neighbour Cell list (if any). In this concatenation the value of the parameter Absolute\_Index\_Start\_EMR is added to the 3G Neighbour Cell list indices. The Neighbour Cell list may contain up to 96 Neighbour Cells. If the same index occurs for a GSM Cell and a 3G Cell, the GSM Cell shall be used. + +NOTE: For report with the MEASUREMENT REPORT message, the concatenated list is not used. Instead, the two lists are used separately, as defined in sub-clause 10.5.2.20, 'Measurement Results'. + +#### 3.4.1.2.1.4 Real Time Differences + +One or more instances of the Measurement Information message may provide Real Time Difference information. This is used to build the Real Time Difference list. The mobile station may use Real Time Difference parameters before + +receiving the BSIC information defined in sub-clause 3.4.1.2. The Real Time Difference list may contain up to 96 Real Time Difference parameters. + +The Real Time Difference list is associated with the BA (list) having the same BA\_IND value. Each frequency in the BA (list) may be associated to 0, 1 or more Real Time Difference parameters. The Real Time Difference parameters may be received before the corresponding BA (list). The parameter BA\_Index\_Start\_RTD in each structure indicates the index of the frequency in the BA (list) to be taken as a starting reference. A sub-structure is included for each frequency referenced. Each of those sub-structures indicates if 0, 1 or more RTD parameters are present for this frequency. If a frequency in the BA (list) is not provided with Real Time Difference information by any of the message instances with correct BA\_IND, it shall be assumed that no information is available for that frequency, see sub-clause 9.1.54 'Measurement Information message'. If more than 96 Real Time Difference parameters are provided for the Real Time Difference list, this shall not be considered as an error. + +If GPRS Real Time Differences Description is provided in the SI2quater message (see sub-clause 3.4.1.2.1.6), it may also be used by a non-GPRS mobile station in Idle mode. + +The MS is not required to take into account more RTDs than cells on the frequency. + +#### 3.4.1.2.1.5 Report Priority Description + +Report Priority information can be received in one instance of the MEASUREMENT INFORMATION message. The Report Priority information is associated with the Neighbour Cell list (see sub-clause 3.4.1.2.1.3) having the same BA\_IND value and 3G\_BA\_IND value. Each REP\_PRIORITY bit of this field relates to indices of the Neighbour Cell list, starting with index 0. The Report Priority information may be received before the corresponding Neighbour Cell list. + +Indices exceeding the value 95 shall be ignored. If there are fewer indices than the number of Neighbour Cells, the value 0 shall be assumed for the missing bits. + +#### 3.4.1.2.1.6 GPRS Parameters + +A set of information may be received in the SI2quater message to be used for GPRS neighbour cell measurement and (NC) Measurement reporting when the cell has no PBCCH allocated, see 3GPP TS 44.060. This information comprises GPRS Report Priority Description, GPRS BSIC Description, GPRS Real Time Differences Description, GPRS Measurement Parameters, GPRS 3G Measurement Parameters, NC Measurement Parameters and GPRS E-UTRAN Measurement Parameters. The use of the parameters is similar to parameters without the term "GPRS". + +#### 3.4.1.2.1.7 The 3G Cell Reselection list + +This applies only to a multi-RAT MS. One or more instances of the SI2quater and/or SI2ter messages may provide 3G Cells. If 3G Cells are provided in both of these messages, the union of the cells shall be included in the 3G Cell Reselection list. If network sharing is used in the cell, a mobile station supporting network sharing shall instead use information provided in the SI23 message to build the 3G Cell reselection list. The 3G Cell Reselection list may contain up to 96 3G Cells. 3G Cells not provided explicitly in the SI2ter message or in the SI2quater message (frequencies on their own) are not included in these 96 cells. Up to 8 frequencies on their own, can be added to these 96 cells including when applicable, 3G frequencies broadcast in the SI23 message. + +NOTE: Frequencies in the SI2quater message for which the parameter NR\_OF\_FDD\_CELLS or NR\_OF\_TDD\_CELLS is set to 31 are only added to the 3G Cell Reselection list (frequencies on their own). Frequencies for which NR\_OF\_FDD\_CELLS is set to 0 (and FDD\_Indic0 is set to 0) are added to the 3G Neighbour Cell list and are only used for RSSI reporting (subject to the restrictions given in 3GPP TS 45.008). Frequencies for which NR\_OF\_FDD\_CELLS is set to a value from 17 to 30 or NR\_OF\_TDD\_CELLS is set to a value of 0 with TDD\_indic0 set to 0 or to a value from 21 to 30 are not added to the 3G Cell Reselection list, they are handled as described in sub-clause 10.5.2.33b. + +The MS behaviour is not specified if the number of 3G frequencies or cells exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008. + +#### 3.4.1.2.1.7a (void) + +#### 3.4.1.2.1.7b Closed Subscriber Group Information + +This applies only to a multi-RAT MS supporting UTRAN and/or E-UTRAN. One or more instances of the SI2quater message or MEASUREMENT INFORMATION message may provide the *E-UTRAN CSG Description* IE and/or the + +3G CSG Description IE. An MS supporting cell reselection to UTRAN and/or E-UTRAN shall use this information as described in 3GPP TS 45.008. + +In the case extended EARFCNs is in use in the cell, the SI2quater message may provide E-UTRAN CSG frequencies within the *Extended EARFCNs Description for CSG Cells* IE. A multi-RAT MS supporting extended EARFCNs shall use this information as described in 3GPP TS 45.008. + +If an MS receives a *CSG\_PSC\_SPLIT* IE and/or a *CSG\_PCI\_SPLIT* IE it shall store this information and shall consider it as being valid for the specified frequencies for a period of up to 24 hours or until a new *CSG\_PSC\_SPLIT* IE and/or a new *CSG\_PCI\_SPLIT* IE is received, whichever occurs first. + +Any valid "CSG PSC Split Information" received from a UTRAN frequency and stored by the mobile station shall take precedence over the information received from the *CSG\_PSC\_SPLIT* IE for that frequency. Any valid "CSG PCI Split Information" received from an E-UTRAN frequency and stored by the mobile station shall take precedence over the information received from the *CSG\_PCI\_SPLIT* IE for that frequency. + +#### 3.4.1.2.1.7c The 3G Frequency list + +The 3G Frequency list consists of the set of UTRAN frequencies contained in the 3G Cell Reselection list (derived from the SI2quater and/or the SI2ter messages) or in the 3G Neighbour Cell list (derived from the MEASUREMENT INFORMATION message) or, if network sharing is supported in the cell, in the set of UTRAN frequencies contained in the SI23 message. The 3G Frequency list includes all frequencies with cells contained in the 3G Neighbour Cell list and (where applicable) frequencies on their own provided by the SI2quater message and/or the SI2ter message or frequencies provided in the SI23 message. + +When multiple cells on the same frequency or multiple references to the same frequency are included in the 3G Neighbour Cell list or 3G Cell Reselection list an index into the 3G Frequency list is allocated for that frequency only the first time it is encountered as outlined below. + +Indices for the 3G Frequency list are allocated according to the following steps. When indices are allocated using the 3G Neighbour Cell list derived from the MEASUREMENT INFORMATION message, steps 2 and 3 shall be ignored. + +- 1) Frequencies contained in the 3G Neighbour Cell list are allocated indices that start from 0 and are incremented for each frequency. An index value of 0 refers to the first UTRAN frequency (TDD-ARFCN or FDD-ARFCN) contained in the 3G Neighbour Cell list; an index value of 1 refers to the second frequency contained in the 3G Neighbour Cell list; and so on. Indices to the 3G Frequency list are allocated according to the order in which 3G cells appear in the 3G Neighbour Cell list. An entry in the 3G Neighbour Cell list indicating a frequency for RSSI reporting shall not result in the allocation of an index. +- 2) UTRAN frequencies on their own provided by the SI2quater message (i.e. frequencies for which the parameter *NR\_OF\_FDD\_CELLS* or *NR\_OF\_TDD\_CELLS* is set to 31) are allocated indices that start from 31 and continue in descending order. Indices are first allocated according to increasing order of the SI2quater\_INDEX field within a consistent set of SI2quater messages then according to their order of occurrence within the 3G *Neighbour Cell description* IE for a given SI2quater\_INDEX. +- 3) UTRAN frequencies on their own provided by the SI2ter message are allocated indices that start from (31 - *N\_UTRAN\_OWN\_SI2QUATER*) and continue in descending order. Indices are first allocated according to increasing order of the SI2ter\_INDEX field within a consistent set of SI2ter messages then according to their order of occurrence within the *UTRAN FDD Description* and/or *UTRAN TDD Description* IEs for a given SI2ter\_INDEX. *N\_UTRAN\_OWN\_SI2QUATER* is defined as the number of the UTRAN frequencies on their own provided by the SI2quater message. + +#### 3.4.1.2.1.8 CCN Support description + +The SI2quater message may also contain information, the CCN Support description, to be used when CCN is enabled in the serving cell, see 3GPP TS 44.060. This CCN Support description is associated with the GSM Neighbour Cell list (see 3.4.1.2.1.2) having the same *BA\_IND* value. Each *CCN\_SUPPORTED* bit of this field relates to indices of the GSM Neighbour Cell list, starting with index 0. The CCN Support description may be received before the corresponding GSM Neighbour Cell list. + +Indices exceeding the value 95 or the number of cells in the GSM Neighbour Cell List shall be ignored. If there are fewer indices than the number of cells in the GSM Neighbour Cell List, the value 0 shall be assumed for the missing bits. + +When this information is not present but CCN is enabled in the serving cell, the mobile station shall assume that CCN is enabled towards all neighbour cells. + +#### 3.4.1.2.1.9 3G\_CCN\_ACTIVE Description + +The SI2quater message may also contain the 3G\_CCN\_ACTIVE parameter in order to indicate whether the MS shall perform the CCN procedures in the serving cell when re-selecting to a 3G neighbour cell, see 3GPP TS 44.060. + +The 3G\_CCN\_ACTIVE parameter indicates if CCN is activated in serving cell towards all 3G neighbour cells. + +#### 3.4.1.2.1.9a E-UTRAN\_CCN\_ACTIVE Description + +The SI2quater message may also contain the E-UTRAN\_CCN\_ACTIVE parameter in order to indicate whether the MS shall perform the CCN procedures in the serving cell when re-selecting to an E-UTRAN neighbour cell, see 3GPP TS 44.060. + +The E-UTRAN\_CCN\_ACTIVE parameter indicates if CCN is activated in the serving cell towards all E-UTRAN neighbour cells. + +#### 3.4.1.2.1.10 GSM Neighbour Cell Selection parameters + +The SI2n message contains cell reselection parameters for the GSM neighbouring cells. These GSM Neighbour Cell Selection parameters are associated with the GSM Neighbour Cell list (see 3.4.1.2.1.2) having the same BA\_IND value. For the application of this information, see 3GPP TS 45.008. + +The GSM Neighbour Cell Selection parameters may be received before the corresponding GSM Neighbour Cell list. + +#### 3.4.1.2.1.11 Fast Acquisition of System Information + +For a multi-RAT MS, the fast acquisition of system information procedure shall be applied to UTRAN if the *3G Priority Parameters Description* IE is present in the SI2quater message or *3G Supplementary Parameters Description* IE is present in the MEASUREMENT INFORMATION message. The procedure shall apply to E-UTRAN if the *E-UTRAN Parameters Description* IE is present in the SI2quater or MEASUREMENT INFORMATION messages. + +The network shall ensure that UTRAN (respectively E-UTRAN) neighbour cell list, UTRAN (respectively E-UTRAN) measurement parameters and UTRAN (respectively E-UTRAN) priority information are contained in consecutive instances of SI2quater message and that, immediately following this information, 3G CSG Description (respectively E-UTRAN CSG Description) parameters are contained in consecutive instances of the message together forming a UTRAN information set (respectively E-UTRAN information set). Similarly, in the case of MEASUREMENT INFORMATION messages, the network shall ensure that UTRAN (respectively E-UTRAN) neighbour cell list and UTRAN (respectively E-UTRAN) measurement parameters are contained in consecutive instances of the message and that, immediately following this information, 3G CSG Description (respectively E-UTRAN CSG Description) parameters are contained in consecutive instances of the message together forming a UTRAN information set (respectively E-UTRAN information set). + +The UTRAN\_Start (respectively E-UTRAN\_Start) bit and the UTRAN\_Stop (respectively E-UTRAN\_Stop) bit shall be set as specified below: + +- The first instance of the SI2quater or MEASUREMENT INFORMATION message containing UTRAN (respectively E-UTRAN) neighbour cell list and/or UTRAN (respectively E-UTRAN) measurement parameters and/or UTRAN (respectively E-UTRAN) priority information shall have the UTRAN\_Start (respectively E-UTRAN\_Start) bit set to value '1'. The last instance of the SI2quater or MEASUREMENT INFORMATION message containing UTRAN (respectively E-UTRAN) neighbour cell list and/or UTRAN (respectively E-UTRAN) measurement parameters and/or UTRAN (respectively E-UTRAN) priority information shall have the UTRAN\_Stop (respectively E-UTRAN\_Stop) bit set to value '1'; or +- Alternatively, if all instances of the SI2quater or MEASUREMENT INFORMATION message contain UTRAN (respectively E-UTRAN) neighbour cell list and/or UTRAN (respectively E-UTRAN) measurement parameters and/or UTRAN (respectively E-UTRAN) priority information, the network may instead set UTRAN\_Start (respectively E-UTRAN\_Start) bit and UTRAN\_Stop (respectively E-UTRAN\_Stop) bit to '0' in every instance containing these bits. + +Not including or not setting of UTRAN\_Start (respectively E-UTRAN\_Start) bit and/or UTRAN\_Stop (respectively E-UTRAN\_Stop) bit according to the above is considered as an abnormal case in which the mobile station's behaviour is implementation specific. + +The network shall ensure that the Serving cell priority parameters are included in at least one instance of the SI2quater message containing the UTRAN (respectively E-UTRAN) neighbour cell list, measurement parameters, or priority information. If the network repeats the Serving cell priority parameters within a consistent set of messages, then the network shall ensure that same set of Serving cell priority parameters are included in all repeated instances. + +The network may repeat a UTRAN information set or an E-UTRAN information set within a consistent set of messages, provided that the information contained in all repeated information sets is the same. On BCCH, the MS needs only receive and decode the information in a single information set. + +In idle mode or packet idle mode a multi-RAT MS supporting UTRAN and camping on BCCH shall read and decode all instances of SI2quater messages containing the UTRAN information set. When the 3G\_BA\_IND parameter is changed in idle mode or packet idle mode, the MS shall acquire the new UTRAN information set and rebuild the 3G Neighbour Cell list. The 3G Neighbour Cell list derived from SI2quater shall then be used for reporting when the MS enters dedicated mode, until it has received all instances of MEASUREMENT INFORMATION messages containing the UTRAN information set. In this case, the newly constructed 3G Neighbour Cell list shall be used. When the 3G\_BA\_IND parameter is changed when on SACCH, the MS shall also re-read all the instances of MEASUREMENT INFORMATION messages containing the new UTRAN information set, rebuild the 3G Neighbour Cell list, and use the new list for reporting. + +In idle mode or packet idle mode a multi-RAT MS supporting E-UTRAN and camping on BCCH shall read and decode all instances of SI2quater messages containing the E-UTRAN information set. When the 3G\_BA\_IND parameter is changed in idle mode or packet idle mode, the MS shall acquire the new E-UTRAN information set and rebuild the E-UTRAN Neighbour Cell list. The E-UTRAN Neighbour Cell list shall then be used for reporting when the MS enters dedicated mode, until it has received all instances of MEASUREMENT INFORMATION messages containing the E-UTRAN information set. In this case, the newly constructed E-UTRAN Neighbour Cell list shall be used. When the 3G\_BA\_IND parameter is changed when on SACCH, the MS shall also re-read all the instances of MEASUREMENT INFORMATION messages containing the new E-UTRAN information set, rebuild the E-UTRAN Neighbour Cell list, and use the new list for reporting. + +#### 3.4.1.2.1.12 Reporting of CSG Cells and Hybrid Cells + +A multi-RAT mobile station in dedicated mode or dual transfer mode may report a UTRAN CSG cell or hybrid cell if: + +- the mobile station has received the *UTRAN CSG Cells Reporting Description* IE from the network in the SI2quater or MEASUREMENT INFORMATION message; and +- the mobile station has determined that it is allowed to access the CSG cell or hybrid cell, i.e. the CSG ID and the PLMN ID of the CSG cell or hybrid cell matches both a CSG ID and an associated PLMN ID stored in the mobile station's CSG Whitelist (see 3GPP TS 23.122) and the PLMN ID of the CSG cell or hybrid cell matches: + - RPLMN ID or a PLMN ID in the EPLMN list and + - in dedicated mode after handover, the PLMN ID received in the *System Information Type 6* message; + - in dual transfer mode, the RPLMN ID or a PLMN ID in the EPLMN list received during the latest registration or registration update with CS domain. + +Further conditions and measurement reporting restrictions are specified in 3GPP TS 45.008. + +The mobile station shall not report UTRAN CSG cells if it receives a MEASUREMENT INFORMATION message that does not include the *UTRAN CSG Cells Reporting Description* IE. + +A mobile station shall report a detected UTRAN CSG cell, or hybrid cell which meets all the conditions and measurement reporting restrictions applicable to CSG cells, by including the *UTRAN CSG Measurement Report* IE in the *Measurement Results* IE when reporting with the MEASUREMENT REPORT message or by including the *UTRAN CSG Measurement Report* IE in the ENHANCED MEASUREMENT REPORT message. + +A hybrid cell which does not meet all the conditions and measurement reporting restrictions applicable to CSG cells shall be reported according to the rules for reporting non-CSG cells. + +NOTE: The autonomous search function used to detect a CSG cell and determine whether a detected cell is a hybrid cell or not is implementation dependent and no performance requirements apply for this function while the mobile station is in dedicated or dual transfer mode. + +### 3.4.1.3 Extended measurement report \$(MAFA)\$ + +Only applicable to mobile stations which support extended measurement. + +When in dedicated mode or group transmit mode, a mobile station may receive an EXTENDED MEASUREMENT ORDER message, from the network. As defined in 3GPP TS 45.008, the mobile station shall then perform measurements on the frequencies specified by this EXTENDED MEASUREMENT ORDER message for one reporting period. The mobile station shall thereafter send an EXTENDED MEASUREMENT REPORT message. This message contains the measurement results as defined in 3GPP TS 45.008. + +If the mobile station has not started to send its EXTENDED MEASUREMENT REPORT message within 10 seconds after the reception of the EXTENDED MEASUREMENT ORDER message, no EXTENDED MEASUREMENT REPORT message shall be sent. The mobile station shall after a successful channel change abort any pending measurements or reporting related to an EXTENDED MEASUREMENT ORDER message received on the old channel. + +If a mobile station receives an EXTENDED MEASUREMENT ORDER message indicating the same value of the sequence code as an EXTENDED MEASUREMENT ORDER message received earlier on the same channel without having received any EXTENDED MEASUREMENT ORDER message indicating a different value of the sequence code in between, that EXTENDED MEASUREMENT ORDER message shall be ignored. If the mobile station, before the reporting related to an EXTENDED MEASUREMENT ORDER message has started, receives a new EXTENDED MEASUREMENT ORDER message with a different value of the sequence code, any pending measurements or reporting related to the earlier EXTENDED MEASUREMENT ORDER message shall be aborted and the new message treated. + +The EXTENDED MEASUREMENT ORDER message and the EXTENDED MEASUREMENT REPORT message are sent on the SACCH, in unacknowledged mode. + +### 3.4.2 Transfer of messages and link layer service provision + +When in dedicated mode or in group transmit mode, upper layers can send messages in multiframe or unacknowledged mode on SAPI 0. In group receive mode optionally messages in multiframe mode can be sent on SAPI 3. + +Moreover, but only when in dedicated mode, upper layers have access to the full link layer services for SAPIs other than 0, with the exception of the error indication and local end release that are directly treated by the RR sublayer, as specified in particular places of clause 3. + +### 3.4.3 Channel assignment procedure + +In dedicated mode, dual transfer mode or in group transmit mode, an intracell change of channel can be requested by upper layers for changing the channel type, or decided by the RR sublayer, e.g. for an internal handover. This change may be performed through the dedicated channel assignment procedure. + +The purpose of the channel assignment procedure is to completely modify the physical channel configuration of the mobile station without frequency redefinition or change in synchronization while staying in the same cell. + +This procedure shall not be used for changing between dependent configurations, i.e. those sharing Radio Resource for the main signalling link. An example of dependent channels is a full rate channel and one of the corresponding half rate channels. In multislot operation however, it is allowed to use the same timeslots before and after the assignment, as long as the main signalling link has been changed. The only procedures provided for changing between dependent configurations for the main signalling link are the additional assignment and the partial release procedures. + +The channel assignment procedure happens only in dedicated mode, dual transfer mode and in group transmit mode. This procedure cannot be used in the idle mode; in this case the immediate assignment procedure is used. + +The channel assignment procedure includes: + +- the suspension of normal operation except for RR management (layer 3); +- the release of the main signalling link, and of the other data links as defined in sub-clause 3.1.4, the disconnection of TCHs if any, and the release of packet resources, if in dual transfer mode; +- the deactivation of previously assigned channels (layer 1); +- the activation of the new channels and their connection if applicable; + +- the triggering of the establishment of the data link connections for SAPI = 0. + +The channel assignment procedure is always initiated by the network. + +### 3.4.3.1 Channel assignment initiation + +The network initiates the channel assignment procedure by sending an ASSIGNMENT COMMAND message to the mobile station on the main signalling link. It then starts timer T3107. + +NOTE: The network should take into account limitations of certain mobile stations to understand formats used in the Frequency List IE and Cell Channel Description IE used in the ASSIGNMENT COMMAND message, see sub-clause 10.5.2.13 and sub-clause 10.5.2.1b. + +When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases is suspended until resumption is indicated. These RR messages can be deduced from sub-clauses 3.4.3 and 8.8 Radio Resource management. + +Upon receipt of the ASSIGNMENT COMMAND message, the mobile station initiates a local end release of link layer connections and packet resources, if in dual transfer mode, disconnects the physical channels, commands the switching to the assigned channels and initiates the establishment of lower layer connections (this includes the activation of the channels, their connection and the establishment of the main signalling links). + +The ASSIGNMENT COMMAND message contains the description of the new configuration, including for the multislot configuration and the TCH/H + TCH/H + ACCHs configuration, the exact ACCHs to be used and a power command. The power level defined in this power command shall be used by the mobile station for the initial power on the new channel(s). It shall not affect the power used on the old channel(s). The message may also contain definitions of the channel mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the ASSIGNMENT COMMAND message, a definition of the channel mode for the new channel set shall be included in the message. + +If the channel mode to be applied corresponds to an initial assignment of a multi-rate speech codec, the ASSIGNMENT COMMAND message shall contain the MultiRate Configuration IE, which defines the set of codec modes and related information to use on the new channel. + +If the assignment is related to an intra-cell handover from a multi-rate speech codec to a multi-rate speech codec, the MultiRate Configuration IE shall be included in the case of full rate to half rate or in the case of a change of multi-rate speech version. If not included in those cases, the mobile station shall behave as if the MultiRate Configuration IE was inconsistent. If not included in other cases, the MS shall use on the new channel the AMR configuration it was using on the old channel when it received the ASSIGNMENT COMMAND message. + +An ASSIGNMENT COMMAND message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions. + +In the case of the reception of an ASSIGNMENT COMMAND message which contains only the description of a channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the reception of the message (see 3GPP TS 45.010 for the timing constraints). + +If the message contains both the description of a channel to be used after the indicated time and of a channel to be used before, the mobile station accesses a channel as an immediate reaction to the reception of the message. If the moment the mobile station is ready to access is before the indicated time, the mobile station accesses the channels described for before the starting time. The mobile station then changes to the channel described for after the starting time at the indicated time. New parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated channels must be identical to the parameters described for before the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described for after the starting time. + +If frequency hopping is applied, the cell allocation if present in the message is used to decode the mobile allocation. If the cell allocation is not included, the mobile station uses its current cell allocation, the current CA is the last CA received on the BCCH. Afterward, the current CA may be changed by some messages sent on the main signalling link containing a CA (the possible messages are: ASSIGNMENT COMMAND, HANDOVER COMMAND and FREQUENCY REDEFINITION). Note that there are cases in which the current CA is undefined, see sub-clause 3.4.3.3. + +The ASSIGNMENT COMMAND message may contain a cipher mode setting IE. In that case, this ciphering mode has to be applied on the new channel. If no such information is present, the ciphering mode and the use of Selective Ciphering of Downlink SACCH (see sub-clause 3.4.7a) are the same as on the previous channel. In either case the ciphering key shall not be changed as long as the key length remains unchanged. However, in case of a switch between ciphering algorithms requiring different key lengths, i.e. 64 or 128 bits, a change from the 64 bit key to the 128 bit key or vice versa must be performed. If the cipher mode setting IE indicates "start ciphering" the mobile station supporting Selective Ciphering of Downlink SACCH shall be able to decode both ciphered and not-ciphered SACCH blocks (see sub-clause 3.4.7a). The ASSIGNMENT COMMAND message shall not contain a cipher mode setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been transmitted earlier in the RR connection or ciphering has been started earlier in UTRAN: if such an ASSIGNMENT COMMAND message is received it shall be regarded as erroneous, an ASSIGNMENT FAILURE with cause "Protocol error unspecified" message shall be returned immediately, and no further action taken. + +In a voice group call, the ASSIGNMENT COMMAND message may contain a VGCS target mode information element defining which RR mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present, the mode shall be assumed to be the same as on the previous channel. When the VGCS target mode information element indicates that the RR mode of the new channel is group transmit mode the information element shall also indicate the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode and group cipher key shall be the same as on the previous channel. Additionally, when the RR mode of the new channel is group transmit mode and the group cipher key number indicates that the new channel is ciphered (ie group key number is non zero), then the VGCS Ciphering Parameters Information Element shall be included to provide the VSTK\_RAND and Cell\_Global\_Count. Mobile stations not supporting VGCS talking shall ignore the ASSIGNMENT COMMAND message if the VGCS target mode information element or the VGCS Ciphering Parameters Information Element are included in the message and shall send an RR STATUS message to the network with cause #96. If the ASSIGNMENT COMMAND message contains a cipher mode setting information element together with either a VGCS target mode information element indicating a RR mode of group transmit mode, or a VGCS Ciphering Parameters information element, then a mobile station supporting VGCS talking shall regard the message as erroneous, an ASSIGNMENT FAILURE message with cause "Protocol error unspecified" shall be returned immediately, and no further action taken. + +If the ASSIGNMENT COMMAND message assigns a VGCS mobile station to a dedicated channel, then the message may contain a cipher mode setting IE. In that case, this ciphering mode has to be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous channel, provided that the previous channel was also a dedicated channel. If no such information is present and the RR mode of the previous channel was group transmit mode, the new ciphering mode is "no ciphering". In either case the ciphering key to be used on the dedicated channel is the individual GSM ciphering key. The ASSIGNMENT COMMAND message shall not contain a cipher mode setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been transmitted earlier in the RR connection or a group cipher key number different from zero has been transmitted for this voice group call. If an ASSIGNMENT COMMAND message is received that contains a cipher mode setting IE indicating "start ciphering" and the mobile station has received neither a CIPHERING MODE COMMAND message in the RR connection, nor a group cipher key number different from zero for this voice group call, via any channel, then the ASSIGNMENT COMMAND message shall be considered as erroneous, the mobile station shall send an ASSIGNMENT FAILURE with cause "Protocol error unspecified", and no further action taken. + +When the VGCS Ciphering Parameters are included in the Assignment Command the MS shall adjust and maintain the Cell Global Count using the procedure described in sub-clause 3.3.3.1. The MS shall then calculate the ciphering keys as described in 3GPP TS 43.020. Also, the MS shall fetch from the USIM the identity of its ciphering algorithm to use on the resource, as described in 3GPP TS 43.020. + +### 3.4.3.2 Assignment completion + +After the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE message, specifying cause "normal event", to the network on the main DCCH. + +The sending of this message on the mobile station side and its receipt on the network side allow the resumption of the transmission of signalling layer messages other than those belonging to RR management. + +At the receipt of the ASSIGNMENT COMPLETE message, the network releases the previously allocated resources and stops timer T3107. + +### 3.4.3.3 Abnormal cases + +If the mobile station has no current CA and if it needs a CA to analyse the ASSIGNMENT COMMAND message, it stays on the current channel(s) and sends an ASSIGNMENT FAILURE message with cause "no cell allocation available". + +If the ASSIGNMENT COMMAND message instructs the mobile station to use a Channel Description or Mode that it does not support, or if the Channel Mode to use is not defined for all channel sets, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Channel Mode(s). + +If the mobile station receives an ASSIGNMENT COMMAND message containing an inconsistent MultiRate Configuration IE, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Channel Mode(s). + +The MultiRate Configuration IE shall be considered as inconsistent by the MS if: + +- the active set does not include any codec mode or the active set includes more than four codec modes; or +- one or more codec modes of the active codec set are not supported by the assigned channel; or +- the threshold and hysteresis values are not set according to requirements given in 3GPP TS 45.009. + +If during the initial assignment of the multirate speech the mobile station receives an ASSIGNMENT COMMAND message and the MultiRate Configuration IE is not present, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Channel Mode(s). + +If the ASSIGNMENT COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "frequency not implemented", and the mobile station shall remain on the current channel(s). + +If the mobile station receives an ASSIGNMENT COMMAND message with a Frequency List IE indicating frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause "frequency not implemented". If the mobile station receives an ASSIGNMENT COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause "frequency not implemented". + +NOTE: An ASSIGNMENT COMMAND message sent to a multi band mobile station shall not be considered invalid because it indicates frequencies that are all in a different frequency band to that of the current channel. + +On the mobile station side, if a lower layer failure happens on the new channel before the ASSIGNMENT COMPLETE message has been sent, the mobile station deactivates the new channels, reactivates the old channels, reconnects the TCHs if any and triggers the establishment of the main signalling link. It then sends a ASSIGNMENT FAILURE message, cause "protocol error unspecified" on the main DCCH and resumes the normal operation, as if no assignment attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the procedure. + +When receiving the ASSIGNMENT FAILURE message, the network stops T3107. + +If a lower layer failure happens while attempting to connect back to the old channels, the radio link failure procedure is applied (see sub-clause 3.4.13.2 for dedicated mode and sub-clause 3.4.13.5 for group transmit mode). + +On the network side, if timer T3107 elapses before either the ASSIGNMENT COMPLETE message has been received on the new channels or an ASSIGNMENT FAILURE message is received on the old channels, the old channels and the new channels are released if they both were dedicated channels and, unless the mobile station has re-established the call, all contexts related to the connections with that mobile station are cleared. If one of the channels was a VGCS channel, it shall be maintained and the uplink shall be set free. If both channels were VGCS channels, the network shall maintain one of the channels and the uplink shall be set free. + +On the network side, lower layer failure occurring on the old channels after the sending of the ASSIGNMENT COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM Frame on the new main signalling link are treated following the general rules (cf. sub-clause 3.5.2). + +### 3.4.4 Handover procedure + +In dedicated mode, dual transfer mode or group transmit mode, an intercell or intracell change of channel(s) can be requested by the network RR sublayer. This change may be performed through the handover procedure. In case of intercell change in dual transfer mode, the DTM handover procedure can be used to change one dedicated channel together with one or more packet data channels (see sub-clause 3.7). + +The network RR sublayer shall not request an intercell or intracell change of channel when a mobile station has temporarily entered the dedicated mode on a SDCCH, in order to initiate a priority uplink request. + +For a talker in group transmit mode, the network RR sublayer shall delay the allocation of resources for handover of the talker to the voice group call channel of the target cell if the uplink of the target cell has already been granted to a subscriber with priority (this collision case may occur if the network supports uplink access option (i) as defined in 3GPP TS 43.068). If the allocation of the uplink to the new subscriber is confirmed, the network shall cancel the handover resource request and release the current talker. If the request for the uplink is rejected, the network proceeds with the handover of the current talker. Alternatively instead of delaying the handover, it may be continued to a different cell if possible. + +NOTE: The decision to do a handover and the choice of the new cell is out of the scope of this technical specification. + +The purpose of the handover procedure is to completely modify the channels allocated to the mobile station e.g. when the cell is changed. A change in the channel configuration nature is possible. This procedure is used only while in dedicated mode, dual transfer mode or group transmit mode. + +The handover procedure shall not be used for changing between dependent configurations (see sub-clause 3.4.3). + +The handover procedure includes: + +- The suspension of normal operation except for RR management (layer 3). +- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH(s) if any. +- The abortion of the packet resources (see 3GPP TS 44.060), if in class A mode of operation. +- The disconnection and the deactivation of previously assigned channels and their release (layer 1). +- The activation of the new channels, and their connection if applicable. +- The triggering of the establishment of data link connection for SAPI = 0 on the new channels. + +The handover procedure is always initiated by the network. + +#### 3.4.4.1 Handover initiation + +The network initiates the handover procedure by sending a HANDOVER COMMAND message to the mobile station on the main DCCH. It then starts timer T3103. + +The network should not initiate a handover which may result in the transmission of a HANDOVER ACCESS message by the MS (see sub-clauses 3.4.4.2.1, 3.4.4.2.2, 3.4.4.2.3, 3.4.4.2.4) if the new traffic channel is in VAMOS mode. If it is determined from the HANDOVER COMMAND message that the assigned traffic channel is potentially in VAMOS mode (e.g. TSC Set 2 assigned, or VAMOS mode signaled), this shall not be considered as an error. + +If the HANDOVER COMMAND message refers to a cell to which the mobile station is not synchronised to, this shall not be considered as an error (see 3GPP TS 45.008). + +NOTE: The network should take into account limitations of certain mobile stations to understand formats used in the Frequency List IE, Frequency Short List IE, and Cell Channel Description IE used in the HANDOVER COMMAND message, see sub-clause 10.5.2.13, sub-clause 10.5.2.14, and sub-clause 10.5.2.1b. + +When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended until resuming is indicated. These RR messages can be deduced from sub-clauses 3.4.3 and 8.5.1 "Radio Resource management". + +Upon receipt of the HANDOVER COMMAND message, the mobile station initiates, as described in sub-clause 3.1.4, the release of link layer connections, disconnects the physical channels (including the packet resources, if in class A mode of operation), commands the switching to the assigned channels and initiates the establishment of lower layer connections (this includes the activation of the channels, their connection and the establishment of the data links). + +The HANDOVER COMMAND message contains: + +- The characteristics of the new channels, including for the multislot configuration and the TCH/H + TCH/H + ACCHs configuration the exact ACCHs to be used. The message may also contain definitions of the channel mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the HANDOVER COMMAND message, a definition of the channel mode for the new channel set shall be included in the message. +- The characteristics of the new cell that are necessary to successfully communicate (e.g. frequency list in the case of slow frequency hopping), including the data that allows the mobile station to use the pre-knowledge about synchronization it acquires by the measurement process (i.e. BSIC + BCCH frequency). +- A power command (cf. 3GPP TS 45.008). The power level defined in this power command shall be used by the mobile station for the initial power on the new channel(s). It shall not affect the power used on the old channel(s). +- An indication of the physical channel establishment procedure to be used. +- A handover reference, used as specified in the following sub-clause. The choice of the handover reference by the network is out of the scope of this specification and left to the manufacturers. +- Optionally a timing advance to be used on the new cell. +- Optionally a cipher mode setting. In that case, this ciphering mode has to be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous channel. In either case the ciphering key shall not be changed as long as the key length remains unchanged. However, in case of a switch between ciphering algorithms requiring different key lengths, i.e. 64 or 128 bits, a change from the 64 bit key to the 128 bit key or vice versa must be performed. If the cipher mode setting IE indicates "start ciphering" the mobile station supporting Selective Ciphering of Downlink SACCH shall be able to decode both ciphered and not-ciphered SACCH blocks (see sub-clause 3.4.7a). In the case of GERAN A/Gb mode to GERAN A/Gb mode handover, if the HANDOVER COMMAND message contains a cipher mode setting IE that indicates "start ciphering" and neither an RR Ciphering Mode Setting procedure (see sub-clause 3.4.7) nor a UTRAN RRC Security Mode Control procedure (see 3GPP TS 25.331) has been successfully completed prior to the handover for this CS connection the HANDOVER COMMAND message shall be regarded as erroneous, a HANDOVER FAILURE message with cause "Protocol error unspecified" shall be returned immediately, and no further action taken. In the case of UTRAN to GERAN A/Gb mode handover or GERAN Iu mode to GERAN A/Gb mode handover or E-UTRAN to GERAN A/Gb mode SRVCC handover (see 3GPP TS 23.216 [94], 3GPP TS 29.280 [95]), the HANDOVER COMMAND message, which is sent transparently via RNC/BSC/eNB from BSS to the mobile station, shall always contain the cipher mode setting IE to indicate the ciphering mode to be used in GERAN A/Gb mode. If the cipher mode setting IE indicates "start ciphering" and neither an RR Ciphering Mode Setting procedure (see sub-clause 3.4.7) nor a UTRAN RRC Security Mode Control procedure (see 3GPP TS 25.331) has been successfully completed prior to the handover for this CS connection, the HANDOVER COMMAND message shall be regarded as erroneous and the applicable procedure as specified in 3GPP TS 25.331 for the case of an Invalid HANDOVER FROM UTRAN COMMAND message shall be followed; a HANDOVER FAILURE message with cause "Protocol error unspecified" shall be included in the HANDOVER FROM UTRAN FAILURE message. In the case of CDMA2000 to GERAN A/Gb mode handover, the HANDOVER COMMAND message, which is sent transparently via RNC from BSS to the mobile station, shall always contain the cipher mode setting IE. +- Optionally, in a voice group call, a VGCS target mode information element defining which RR mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present, the mode shall be assumed to be the same as on the previous channel. When the RR mode on the new channel is group transmit mode, the VGCS target mode information element shall also indicate the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. + +Additionally, when the RR mode is group transmit mode and the group cipher key number is non zero, then the VGCS Ciphering Parameters information element shall contain the CELL\_GLOBAL\_COUNT and optionally contain the VSTK\_RAND, the target cell identity, the cell's location area. If the VGCS target mode information element is not present, the ciphering mode and ciphering key shall be assumed to be the same as on the previous channel. If any of the following parameters are not included in the VGCS Ciphering Parameters information element, the parameter shall be assumed to be the same as on the previous channel: VSTK\_RAND, the target cell identity, or the cell's location area. The network shall include the VSTK\_RAND (within the VGCS Ciphering Parameters IE) if the group call is ciphered, the new RR mode is group transmit mode and the old RR mode is dedicated mode or is not known. Mobile stations not supporting VGCS talking shall ignore the HANDOVER COMMAND message if the VGCS target mode information element or VGCS Ciphering Parameters information element is included in the message and shall send an RR STATUS message to the network with cause #96. If the HANDOVER COMMAND message contains a cipher mode setting information element together with either a VGCS target mode information element indicating a RR mode of group transmit mode, or a VGCS Ciphering Parameters information element, , then a mobile station supporting VGCS talking shall regard the message as erroneous, an HANDOVER FAILURE message with cause "Protocol error unspecified" shall be returned immediately, and no further action taken. + +- Optionally, in a voice group call, if the RR mode of the new channel is dedicated mode, a cipher mode setting IE. In that case, this ciphering mode shall be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous channel, provided that the previous channel was also a dedicated channel. If no such information is present and the previous channel had RR mode group transmit mode, the new ciphering mode is "no ciphering". In either case the ciphering key to be used on the dedicated channel is the individual GSM ciphering key. The HANDOVER COMMAND message shall not contain a cipher mode setting IE that indicates "start ciphering", unless a CIPHERING MODE COMMAND message has been transmitted earlier in the RR connection or a group cipher key number different from zero has been transmitted for this voice group call. If a HANDOVER COMMAND message is received that contains a cipher mode setting IE indicating "start ciphering" and the mobile station has received neither a CIPHERING MODE COMMAND message earlier in the RR connection nor a group cipher key number different from zero for this voice group call, via any channel, then the HANDOVER COMMAND message shall be considered as erroneous, the mobile station shall send an HANDOVER FAILURE with cause "Protocol error unspecified", and no further action taken. +- Optionally, when the channel mode indicates that a multi-rate speech codec must be applied, the MultiRateconfiguration to be used in the new cell. The MultiRate Configuration IE defines the set of codec mode and related information to use after the handover. When accessing the new channel, the mobile station shall use for the Initial Codec Mode the mode specified in the MultiRate Configuration IE, if present, or apply by default the implicit rule defined in 3GPP TS 45.009. +- Optionally, if the network supports dedicated mode MBMS notification and the mobile previously completed the service information sending to the network, an indication of whether the service information sending should be completed on the main DCCH of the new cell. +- Optionally, if the target network and the MS support network sharing and DTM, the PLMN Index corresponding to the selected PLMN. + +In addition, a HANDOVER COMMAND message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions. + +In the case of the reception of a HANDOVER COMMAND message which contains only the description of a channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the reception of the message (see 3GPP TS 45.010 for the timing constraints). + +In the case of a handover towards a GERAN cell to which the mobile station is not synchronised to and in the case of an intersystem handover to GERAN, at the reception of a HANDOVER COMMAND message which contains only the description of a channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the new channel. If the starting time has already elapsed, the mobile shall access the new channel as an immediate reaction to the reception of the message (see 3GPP TS 45.010 for the timing constraints). Between the reception of the HANDOVER COMMAND and the starting time there is no requirement for the mobile station to receive or transmit on the old channel. + +NOTE: This case may result to a long interruption and should not be used. + +If the message contains both the description of a channel to be used after the indicated time and of a channel to be used before, the mobile station accesses a channel as an immediate reaction to the reception of the message. If the moment the mobile station is ready to access is before the indicated time, the mobile station accesses the channels described for before the starting time. The mobile station then changes to the channel described for after the starting time at the indicated time. New parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated channels must be identical to the parameters described for before the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described for after the starting time. + +In the case of a handover from a GERAN cell, if the channel mode indicates that a multi-rate speech codec must be applied, and the MultiRateConfiguration IE is not included in the HANDOVER COMMAND message, then the mobile station shall use on the new channel the AMR configuration it was using on the old channel when it received the HANDOVER COMMAND message. The MultiRate Configuration IE shall be included in the case of full rate channel to half rate channel handover or in the case of a change of multi-rate speech version.. If not included in thosecases, the mobile station shall behave as if the MultiRate Configuration IE was inconsistent (see sub-clause 3.4.4.4). + +In the case of an intersystem handover to GERAN, if the channel mode indicates that a multi-rate speech codec must be applied, the MultiRateConfiguration IE shall be included in the HANDOVER COMMAND message. If not included the mobile station shall treat the HANDOVER COMMAND message as invalid and shall perform the corresponding RRC error handling, see 3GPP TS 25.331. + +In the case of a VGCS talker that is handed over to a ciphered VGCS group channel the MS shall calculate the voice group ciphering keys from the following parameters, as described in 3GPP TS 43.020: + +- VSTK\_RAND; +- CGI (as supplied in the Handover Command); +- CELL\_GLOBAL\_COUNT (value of parameter in the target cell, as supplied in the Handover Command); +- Group Cipher Key Number (value obtained via the Handover Command); +- B22\_COUNT - Bit 22 of COUNT ( as defined in 3GPP TS 43.020). + +The HANDOVER COMMAND message shall provide the VGCS talker with the above parameters if the values have changed on handover or if the MS was not using VGCS/VBS ciphering prior to handover. + +When the VGCS talker is handed over to a channel that is ciphered with VGCS ciphering, the talker adjust and maintain the CELL\_GLOBAL\_COUNT provided in the HANDOVER COMMAND message as described in sub-clause 3.3.3.1. Also, this talker shall fetch from the USIM the identity of its ciphering algorithm to use on the new resource, as described in 3GPP TS 43.020. + +In the case of a VGCS talker that is handover a dedicated channel, the setting of the Cipher Mode IE in the HANDOVER COMMAND message shall indicate if the dedicated resource is ciphered. If the new resource is ciphered then the MS shall assume the following: + +- the Cipher Mode Setting IE shall indicate the identity of the ciphering algorithm to use on the dedicated channel; If this information is not present the MS shall use the algorithm that was last used when on a ciphered dedicated channel; +- the ciphering key sequence number shall be the same value as when the MS was last used on a ciphered dedicated channel. + +### 3.4.4.2 Physical channel establishment + +Four procedures are defined. The support of three of them is mandatory in the mobile station. The pseudo-synchronization case is optional in the mobile station. A pseudo-synchronized handover can be commanded only to a mobile station that can support it, as indicated in the classmark. + +#### 3.4.4.2.1 Finely synchronized cell case + +If the mobile station knows that the timing advance with the new cell is not out of range, i.e. smaller than or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004, or if the new cell does accept out of range timing advance as indicated in the HANDOVER COMMAND message, the mobile station proceeds as follows. + +After having switched to the assigned channels, the mobile station sends four times the HANDOVER ACCESS message in four successive layer 1 frames on the main DCCH. This message is sent in an access burst. Its content is reduced to the handover reference information element. The transmission of these four messages is optional if so indicated by the network in the HANDOVER COMMAND message. + +Before completion of the 4 access bursts on the DCCH, additional access bursts may also be sent on the SACCH. + +In those cells that support extended TA values if TA value in new cell is greater than 63 and the HANDOVER COMMAND message indicates that the transmission of four HANDOVER ACCESS messages is optional the MS shall not transmit these four messages. MS shall not send additional bursts on the SACCH. + +It then activates the channels in sending and receiving mode and connects the channels if need be. + +If applicable, ciphering is immediately started . The access bursts are not ciphered, including when sent on the group channel. + +#### 3.4.4.2.2 Non synchronized cell case + +After having switched to the assigned channels, the mobile station starts repeating the HANDOVER ACCESS message in successive layer 1 frames on the main DCCH and optionally on the SACCH. This message is sent in an access burst. Its content is reduced to the handover reference information element. The mobile station starts timer T3124 at the start point of the timeslot in which the HANDOVER ACCESS message is sent the first time on the main DCCH. + +The mobile station then activates the channels in receiving mode and connects the channels if need be (only for reception). + +If applicable, deciphering is then immediately started . The access bursts are not ciphered, including when sent on the group channel. + +When the network has the RF characteristics that are necessary, it sends in unacknowledged mode a PHYSICAL INFORMATION message to the mobile station on the main DCCH. If applicable, ciphering and deciphering is immediately started (i.e., before even the reception of a correct access burst), and the message is sent enciphered. + +The PHYSICAL INFORMATION message contains various physical layer related information, allowing a proper transmission by the mobile station. + +When sending the PHYSICAL INFORMATION message, the network starts timer T3105. If this timer times out before the reception of a correctly decoded layer 2 frame in format A or B (see 3GPP TS 44.006), or a correctly decoded TCH frame from the mobile station, the network repeats the PHYSICAL INFORMATION message and restarts timer T3105. The maximum number of repetitions is $N_{y1}$ . + +The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no error. + +When the mobile station receives a PHYSICAL INFORMATION message, it stops timer T3124, stops sending access bursts, activates the physical channels in sending and receiving mode and connects the channels if need be. If the allocated channel is an SDCCH (+ SACCH), performance of the mobile station must enable the mobile station to accept a correct PHYSICAL INFORMATION message sent by the network in any block while T3124 is running. + +#### 3.4.4.2.3 Pseudo-synchronized cell case + +The details of the use of this procedure are described in 3GPP TS 45.010. The mobile station computes the timing advance to be used with the new cell from the real time difference value given in the HANDOVER COMMAND message. If the mobile station knows that the timing advance with the new cell is not out of range, i.e. smaller or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004, or if the new cell accepts an out of range timing advance as indicated in the HANDOVER COMMAND message, the mobile station switches to the new channel and proceeds as follows. + +After having switched to the assigned channels, the mobile station sends in four successive slots on the main DCCH a HANDOVER ACCESS message. This message is sent in random mode and thus does not follow the basic format. Its content is reduced to the handover reference information element. The transmission of these four messages is optional if so indicated by the network in the HANDOVER COMMAND message. + +Before completion of the 4 access bursts on the DCCH, additional access bursts may also be sent on the SACCH. + +In those cells that support extended TA values if TA value in new cell is greater than 63 and the HANDOVER COMMAND message indicates that the transmission of four HANDOVER ACCESS messages is optional the MS shall not transmit these four messages. The MS shall not send additional bursts on the SACCH. + +The mobile station then activates the channels in sending and receiving mode and connects the channels if need be. The mobile station may activate the channels in receiving mode and connect the channels while sending access bursts. + +If applicable, ciphering is then immediately started. The access bursts are not ciphered, including when sent on the group channel. + +#### 3.4.4.2.4 Pre-synchronized cell case + +The details of the use of this procedure are described in 3GPP TS 45.010. The mobile station switches to the new channel and proceeds as follows. + +After having switched to the assigned channels, the mobile station sends in four successive slots on the main DCCH a HANDOVER ACCESS message. This message is sent in an access burst and thus does not follow the basic format. Its content is reduced to the handover reference information element. The transmission of these four messages is optional if so indicated by the network in the HANDOVER COMMAND message. + +Before completion of the 4 access bursts on the DCCH, additional access bursts may also be sent on the SACCH. + +In those cells that support extended TA values if TA value in new cell is greater than 63 and the HANDOVER COMMAND message indicates that the transmission of four HANDOVER ACCESS messages is optional the MS shall not transmit these four messages. MS shall not send additional bursts on the SACCH. + +The mobile station then activates the channel in sending and receiving mode and connects the channels if need be. The timing advance value to be used with the new cell is: + +- either the value contained in the HANDOVER COMMAND message if the timing advance information element is present; or +- the default value for pre-synchronized handover as defined in 3GPP TS 45.010, if the timing advance information element is not included in the HANDOVER COMMAND message. The MS may activate the channels in receiving mode and connect the channels while sending access bursts. + +If applicable, ciphering is immediately started. The access bursts are not ciphered, including when sent on the group channel. + +#### 3.4.4.3 Handover completion + +After lower layer connections are successfully established, the mobile station returns a HANDOVER COMPLETE message, specifying cause "normal event", to the network on the main DCCH. + +The sending of this message on the mobile station side and its receipt on the network side allow the resumption of the transmission of signalling layer messages other than those for RR management. + +When receiving the HANDOVER COMPLETE message, the network stops timer T3103 and releases the old channels. + +If requested to do so in the HANDOVER COMMAND message, the mobile station includes the observed time difference it has measured when performing the handover, corrected by half the timing advance, in the HANDOVER COMPLETE message (detailed specifications are given in 3GPP TS 45.010). + +If the new cell and the mobile station support DTM, the network shall send the DTM INFORMATION message on the main DCCH after the HANDOVER COMPLETE message has been received. + +#### 3.4.4.4 Abnormal cases + +In the case of a synchronous or pseudo-synchronous handover, if the mobile station knows that the timing advance with the new cell is out of range, i.e. is bigger than the maximum timing advance that can be coded as specified in 3GPP TS 44.004, and if the new cell does not accept out of range timing advance as indicated in the HANDOVER COMMAND message, the mobile station sends a HANDOVER FAILURE message, cause "handover impossible, timing advance out of range", on the main signalling link and does not attempt that handover. + +If the HANDOVER COMMAND message instructs the mobile station to use a Channel Description or Mode that it does not support, or if the Channel Mode to use is not defined for all channel sets, then the MS shall return a HANDOVER FAILURE message with cause "channel mode unacceptable", and the MS shall remain on the current channel(s) and uses the old Channel Description or Mode(s). + +If the mobile station receives a HANDOVER COMMAND message containing an inconsistent MultiRateConfiguration IE, then the mobile station shall return a HANDOVER FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Mode(s). + +The MultiRate Configuration IE shall be considered as inconsistent by the MS if: + +- the active set does not include any codec mode or the active set includes more than four codec modes; or +- one or more codec modes of the active codec set are not supported by the assigned channel; or +- the threshold and hysteresis values are not set according to requirements given in 3GPP TS 45.009. + +If the HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall return a HANDOVER FAILURE message with cause "frequency not implemented", and the mobile station shall remain on the current channel(s). + +If the mobile station receives a HANDOVER COMMAND message with a Frequency List IE or Frequency Short List IE indicating frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send a HANDOVER FAILURE message with cause "frequency not implemented". If the mobile station receives a HANDOVER COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send a HANDOVER FAILURE message with cause "frequency not implemented". + +NOTE: A HANDOVER COMMAND message sent to a multi band mobile station shall not be considered invalid because it indicates target channel frequencies that are all in a different frequency band to that of the ARFCN in the Cell Description IE. + +On the mobile station side, if timer T3124 times out (only in the non- synchronized case) or if a lower layer failure happens on the new channel before the HANDOVER COMPLETE message has been sent, the mobile station deactivates the new channels, reactivates the old channels, reconnects the TCHs if any and triggers the establishment of the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation as if no handover attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the HANDOVER COMMAND message was received. + +When the HANDOVER FAILURE message has been received, the network releases the new channels if they were dedicated channels and stops timers T3105 and stops T3103 in the non-synchronized case. If the new channels were VGCS channels, they shall be maintained. + +If a DTM capable mobile station is in a cell supporting dual transfer mode and is in GMM READY state, it shall perform a Cell Update procedure immediately after sending the HANDOVER FAILURE message. + +If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf. sub-clause 3.4.13.2 for dedicated mode and sub-clause 3.4.13.5 for group transmit mode). + +On the network side, if timer T3103 elapses before either the HANDOVER COMPLETE message is received on the new channels, or a HANDOVER FAILURE message is received on the old channels, or the mobile station has re-established the call, the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared. If the old channel was a VGCS channel, it shall be maintained and the uplink shall be set free. + +On the network side, if neither a correctly layer 2 frame in format A or B nor a correctly TCH frame have been received from the mobile station on the new channel, the newly allocated channels are released if they were dedicated channels. If the new channels were VGCS channels, they shall be maintained and the uplink shall be set free. + +On the network side, lower layer failures occurring on the old channels after the sending of the HANDOVER COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM frame on the new main signalling link are treated following a general scheme (cf. sub-clause 3.4.13.2 for dedicated mode and sub-clause 3.4.13.5 for group transmit mode). + +### 3.4.4a Handover to UTRAN procedure + +Only valid for a UTRAN capable MS. In dedicated mode or dual transfer mode, a change to UTRAN channel(s) can be requested by the network RR sublayer. This change is performed through the handover to UTRAN procedure. + +NOTE: The decision to do a handover to UTRAN and the choice of the new cell is out of the scope of this technical specification. + +The handover to UTRAN procedure includes: + +- The suspension of normal operation except for RR management (layer 3); +- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH(s) if any; +- The disconnection and the deactivation of previously assigned channels and their release (layer 1); +- The abortion of the packet resources (see 3GPP TS 44.060), if in class A mode of operation; +- The establishment of UTRAN channel(s), see 3GPP TS 25.331. + +The handover to UTRAN procedure is always initiated by the network. + +#### 3.4.4a.1 Handover to UTRAN initiation + +The network initiates the handover to UTRAN procedure by sending an INTER SYSTEM TO UTRAN HANDOVER COMMAND message to the mobile station on the main DCCH. It then starts timer T3121. + +If the INTER SYSTEM TO UTRAN HANDOVER COMMAND refers to a not known cell (see 3GPP TS 25.133 and 3GPP TS 25.123), this shall not be considered as an error. + +When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended until resuming is indicated. These RR messages can be deduced from sub-clause 3.4.3 and 8.5.1 "Radio Resource management". + +Upon receipt of the INTER SYSTEM TO UTRAN HANDOVER COMMAND message, the mobile station initiates, as described in sub-clause 3.1.4, the release of link layer connections and disconnects the physical channels (including the packet resources, if in class A mode of operation). Switching to the assigned cell(s) and physical channel establishment is described in 3GPP TS 25.331. + +#### 3.4.4a.2 Handover to UTRAN completion + +NOTE: After lower layer connections are successfully established, the mobile station returns a Handover to UTRAN Complete message on UTRAN channels(s), see 3GPP TS 25.331. + +When receiving the Handover to UTRAN Complete message (3GPP TS 25.331), the network stops timer T3121 and releases the old channels. + +If there are any upper layer messages for which LAPDm has not yet received acknowledgement from the network, the MS shall, after the handover has been successfully completed, send the messages to the network using the newly established radio connection to the UTRAN. + +### 3.4.4a.3 Abnormal cases + +If the INTER SYSTEM TO UTRAN HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall stay on the current channel(s) and return a HANDOVER FAILURE message with cause "frequency not implemented". + +If the INTER SYSTEM TO UTRAN HANDOVER COMMAND message instructs the mobile station to use a UTRAN predefined configuration that the mobile station has not read or instructs to use a default configuration not implemented by the mobile station, then the mobile station shall stay on the current channel(s) and return a HANDOVER FAILURE message with cause "UTRAN configuration unknown". + +If connection is not possible on the UTRAN channel(s) (see 3GPP TS 25.331), the MS reactivates the old channel(s) and reconnects TCHs and triggers the establishment of the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation. + +When sending a HANDOVER FAILURE message in response to an INTERSYSTEM TO UTRAN HANDOVER COMMAND, the mobile station shall erase all the UTRAN predefined configurations. + +When the HANDOVER FAILURE message has been received, the network releases the UTRAN channel(s) if they were dedicated channels and stops timer T3121. + +If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf. sub-clause 3.4.13.2 for dedicated mode). + +On the network side, if timer T3121 elapses before either the Handover to UTRAN Complete (3GPP TS 25.331) message is received on the UTRAN channel(s), or a HANDOVER FAILURE message is received on the old channels, or the mobile station has re-established the call, the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared. + +On the network side, lower layer failures occurring on the old channels after the sending of the INTER SYSTEM TO UTRAN HANDOVER COMMAND message are ignored. + +### 3.4.4b Handover to CDMA2000 procedure + +Only valid for a CDMA2000 capable MS. In dedicated mode or dual transfer mode, a change to CDMA2000 channel(s) can be requested by the network RR sublayer. This change is performed through the handover to CDMA2000 procedure. + +NOTE: The decision to do a handover to CDMA2000 and the choice of the new cell is out of the scope of this technical specification. + +The handover to CDMA2000 procedure includes: + +- The suspension of normal operation except for RR management (layer 3); +- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH(s) if any; +- The disconnection and the deactivation of previously assigned channels and their release (layer 1); +- The abortion of the packet resources (see 3GPP TS 44.060), if in class A mode of operation; +- The establishment of CDMA2000 channel(s), see TTA/ETIA/IS-833 and TTA/ETIA/IS-2000-5-A. + +The handover to CDMA2000 procedure is always initiated by the network. + +### 3.4.4b.1 Handover to CDMA2000 initiation + +The network initiates the handover to CDMA2000 procedure by sending an INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message to the mobile station on the main DCCH. It then starts timer T3123. + +If the INTER SYSTEM TO CDMA2000 HANDOVER COMMAND refers to a not known base station (see TIA/EIA/IS-98-D), this shall not be considered as an error. + +When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended until resuming is indicated. These RR messages can be deduced from sub-clause 3.4.3 and 8.5.1 "Radio Resource management". + +Upon receipt of the INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message, the mobile station initiates, as described in sub-clause 3.1.4, the release of link layer connections and disconnects the physical channels (including the packet resources, if in class A mode of operation). Switching to the assigned base stations and physical channel establishment is described in TIA/EIA/IS-2000-5-A. + +### 3.4.4b.2 Handover to CDMA2000 completion + +NOTE: After lower layer connections are successfully established, the mobile station returns a Handoff Completion Message on CDMA2000 channels(s), see TIA/EIA/IS-833. + +When receiving the Handoff Completion Message (TIA/EIA/IS-833), the network stops timer T3123 and releases the old channels. + +### 3.4.4b.3 Abnormal cases + +If the INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall return a HANDOVER FAILURE message with cause "frequency not implemented", and the mobile station shall remain on the current channel(s). + +If connection is not possible on the CDMA2000 channel(s) (see TIA/EIA/IS-2000-5-A), the MS reactivates the old channels, reconnects TCHs and triggers the establishment of the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation. + +When the HANDOVER FAILURE message has been received, the network releases the CDMA2000 channel(s) if they were dedicated channels and stops timer T3123. + +If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf. sub-clause 3.4.13.2 for dedicated mode). + +On the network side, if timer T3123 elapses before either the Handoff Completion Message (TIA/EIA/IS-833) is received on the CDMA2000 channel(s), or a HANDOVER FAILURE message is received on the old channels, or the mobile station has re-established the call, the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared. + +On the network side, lower layer failures occurring on the old channels after the sending of the INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message are ignored. + +## 3.4.4c Intermode handover to GERAN Iu mode procedure + +### 3.4.4c.1 General + +This sub-clause is only valid for a GERAN *Iu mode* capable MS. In dedicated mode or dual transfer mode, a change to GERAN *Iu mode* channel(s) can be requested by the network RR sublayer. This change is performed through the intermode handover to GERAN Iu procedure. + +NOTE: The decision to do a handover to GERAN *Iu mode* and the choice of the new cell is out of the scope of this technical specification. + +The handover to GERAN *Iu mode* procedure includes: + +- The suspension of normal operation except for RR management (layer 3); + +- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH(s) if any; +- The disconnection and the deactivation of previously assigned channels and their release (layer 1); +- The abortion of the packet resources (see 3GPP TS 44.060), if in class A mode of operation; +- The establishment of the channel(s) in GERAN Iu mode, see 3GPP TS 44.118. + +### 3.4.4c.2 Initiation of the handover to GERAN *Iu mode* procedure + +The network initiates the handover to GERAN *Iu mode* procedure by sending an HANDOVER TO GERAN Iu MODE COMMAND message to the mobile station on the main DCCH. It then starts timer T3121. + +If the HANDOVER TO GERAN Iu MODE COMMAND message refers to a not known cell (see 3GPP TS 45.008), this shall not be considered as an error. + +When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended until resumption is indicated. These RR messages can be deduced from sub-clause 3.4.3 and sub-clause 8.5.1. + +Upon receipt of the HANDOVER TO GERAN Iu MODE COMMAND message, the mobile station initiates, as described in sub-clause 3.1.4, the release of link layer connections and disconnects the physical channels (including the packet resources, if in class A mode of operation). Switching to the assigned cell(s) and physical channel establishment is described in 3GPP TS 44.118. + +### 3.4.4c.3 Completion of the Handover to GERAN *Iu Mode* procedure + +NOTE: After lower layer connections are successfully established, the mobile station returns a RADIO BEARER RECONFIGURATION COMPLETE message on GERAN Iu mode, see 3GPP TS 44.118. + +When receiving the RADIO BEARER RECONFIGURATION COMPLETE message (3GPP TS 44.118), the network stops timer T3121 and releases the old channels. + +### 3.4.4c.4 Abnormal cases + +If the intermode HANDOVER TO GERAN Iu MODE COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall stay on the current channel(s) and return a HANDOVER FAILURE message with cause "frequency not implemented". + +If connection is not possible on the channel(s) in GERAN *Iu mode* (see 3GPP TS 44.118), the MS reactivates the old channel(s) and reconnects TCHs and triggers the establishment of the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation. + +When the HANDOVER FAILURE message has been received, the network releases the new channel(s) if they were dedicated channels and stops timer T3121. + +If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf. sub-clause 3.4.13.2 for dedicated mode). + +On the network side, if timer T3121 expires, the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared. + +On the network side, lower layer failures occurring on the old channels after the sending of the HANDOVER TO GERAN Iu MODE COMMAND message are ignored. + +### 3.4.4d CS to PS SRVCC procedure + +This procedure is only valid for a CS to PS SRVCC capable MS. In dedicated mode or dual transfer mode, a change to E-UTRAN / UTRAN PS bearer can be requested by the network RR sublayer. This change is performed through the CS to PS SRVCC procedure. + +The CS to PS SRVCC procedure includes: + +- The suspension of normal operation except for RR management (layer 3); + +- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH(s) if any; +- The disconnection and the deactivation of previously assigned channels and their release (layer 1); +- The abortion of the packet resources (see 3GPP TS 44.060), if applicable; +- The establishment of E-UTRAN / UTRAN PS bearers, see 3GPP TS 36.331, 3GPP TS 25.331. + +The SRVCC to E-UTRAN/UTRAN procedure is always initiated by the network. The decision to perform CS to PS SRVCC procedure and the choice of the new cell is out of the scope of this technical specification. + +In case of dual transfer mode, when this procedure is initiated there is no handover functionality related to the PS domain (i.e. no PS Handover is initiated and the CS to PS SRVCC procedure is therefore the same for both dedicated mode and dual transfer mode). + +### 3.4.4d.1 CS to PS SRVCC procedure initiation + +The network initiates the CS to PS SRVCC procedure by sending an INTER SYSTEM TO E-UTRAN HANDOVER COMMAND or INTER SYSTEM TO UTRAN HANDOVER COMMAND message to the mobile station on the main DCCH. The network then starts timer T3121. + +If the INTER SYSTEM TO UTRAN HANDOVER COMMAND refers to an unknown cell (see 3GPP TS 25.133 and 3GPP TS 25.123), this shall not be considered as an error. + +When sending one of these messages on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages, except for those RR messages needed for this procedure and for abnormal cases, is suspended until resumption is indicated. These RR messages can be deduced from sub-clause 3.4.3 and 8.5.1 "Radio Resource management". + +Upon receipt of the INTER SYSTEM TO E-UTRAN HANDOVER COMMAND or INTER SYSTEM TO UTRAN HANDOVER COMMAND message, the mobile station initiates, as described in sub-clause 3.1.4, the release of link layer connections and disconnects the physical channels (including the packet resources, if applicable). + +Switching to the assigned cell(s) and physical channel establishment in E-UTRAN or UTRAN is described in 3GPP TS 36.331 and 3GPP TS 25.331. + +### 3.4.4d.2 CS to PS SRVCC procedure completion + +NOTE: After lower layer connections are successfully established, the mobile station sends a RRCConnectionReconfigurationComplete message on E-UTRAN channels(s), see 3GPP TS 36.331 or a Handover to UTRAN Complete message on UTRAN channel(s), see 3GPP TS 25.331. + +When receiving the RRCConnectionReconfigurationComplete message (3GPP TS 36.331), the network stops timer T3121 and releases the old channels. + +When receiving the Handover to UTRAN Complete message (3GPP TS 25.331), the network stops timer T3121 and releases the old channels. + +If there are any upper layer messages for which LAPDm has not yet received acknowledgement from the network, the MS shall, after the handover has been successfully completed, discard these messages. + +### 3.4.4d.3 Abnormal cases + +For CS to PS SRVCC to UTRAN (HSPA) the same abnormal cases as defined in 3.4.4a.3 apply. + +If the INTER SYSTEM TO E-UTRAN HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall stay on the current channel(s) and return a HANDOVER FAILURE message with cause "frequency not implemented". + +If connection is not possible on the E-UTRAN channel(s) (see 3GPP TS 36.331), the MS reactivates the old channel(s) and reconnects TCHs and triggers the establishment of the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation. + +When the HANDOVER FAILURE message has been received, the network releases the E-UTRAN dedicated bearer and stops timer T3121. + +If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf. sub-clause 3.4.13.2 for dedicated mode). + +On the network side, if timer T3121 elapses before either the RRCConnectionReconfigurationComplete (3GPP TS 36.331) message is received on the E-UTRAN channel(s), or a HANDOVER FAILURE message is received on the old channels, or the mobile station has re-established the call, the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared. + +On the network side, lower layer failures occurring on the old channels after the sending of the INTER SYSTEM TO E-UTRAN HANDOVER COMMAND message are ignored. + +### 3.4.5 Frequency redefinition procedure + +In dedicated mode, dual transfer mode and group transmit mode, this procedure is used by the network to change the frequencies and hopping sequences of the allocated channels. This is meaningful only in the case of frequency hopping. + +The network sends to the mobile station a FREQUENCY REDEFINITION message containing the new parameters together with a starting time indication. + +NOTE: The network should take into account limitations of certain mobile stations to understand formats used in the Cell Channel Description IE used in the FREQUENCY REDEFINITION message, see sub-clause 10.5.2.13. + +For a mobile in dual transfer mode with resources assigned on two channels, the Frequency redefinition procedure may be applied to either or both channels. + +When receiving such a message, the mobile station modifies the frequencies/hopping sequences it uses at the exact indicated time slot, i.e. the indicated time slot is the first with new parameters. All other functions are not disturbed by this change. New parameters can be the cell channel description, the mobile allocation and the MAIO. In case of multislot configuration, the Channel Description IE shall describe the channel carrying the main signalling link, the new parameters however, shall be used for all assigned timeslots. Other parameters describing the allocated channels must be identical to the current parameters. + +#### 3.4.5.1 Abnormal cases + +If the mobile station receives a FREQUENCY REDEFINITION message with a Mobile Allocation IE indexing frequencies that are not all in one band and a Starting Time IE indicating a time that has not elapsed, then the mobile station shall stay on the current channel(s) and send a RR STATUS message with cause "frequency not implemented". + +If the mobile station receives a FREQUENCY REDEFINITION message with a Mobile Allocation IE indexing frequencies that are not all in one band and a Starting Time IE indicating a time that has elapsed, then the mobile station shall locally abort the radio connection and, if permitted, attempt Call Re-establishment. + +If the mobile station receives a FREQUENCY REDEFINITION message on a channel for which it has a pending redefinition (defined by the immediate assignment, assignment or handover procedure or a previous frequency redefinition procedure) the frequencies, hopping and starting time parameters defined by the new frequency redefinition procedure supersedes those of the pending one. + +NOTE: A FREQUENCY REDEFINITION message sent to a multi band mobile station shall not be considered invalid because it indicates new frequencies that are all in a different frequency band to that of the ARFCN of the serving cell. + +If the mobile station in dual transfer mode with assigned resources on two channels receives a FREQUENCY REDEFINITION message which neither contains a *Carrier Indication* IE nor contains frequency parameters for both carriers (i.e. the *Channel Description C2* and the *Mobile Allocation C2* IEs are not included), then the mobile station shall stay on the current channel(s) and send a RR STATUS message with cause "semantically incorrect message". + +### 3.4.6 Channel mode modify procedure + +In dedicated mode, dual transfer mode or group transmit mode, higher layers can request the setting of the channel mode. + +The channel mode modify procedure allows the network to request the mobile station to set the channel mode for one channel or one channel set. The procedure shall not be used if the multislot configuration contains more than one channel set. The channel mode covers the coding, decoding and transcoding mode used on the indicated channel. + +This message shall not be used to modify the mode of a non-multislot configured traffic channel when the MS has requested a multislot configuration, ie it cannot be used to modify the mode of a traffic channel when the channel was assigned during the immediate assignment procedure and the user has requested a multislot configuration. + +This procedure is always initiated by the network. + +NOTE: Direct transitions between full rate speech coder version 1 and full rate speech coder version 2 (and vice versa) may cause unpleasant audio bursts. + +### 3.4.6.1 Normal channel mode modify procedure + +#### 3.4.6.1.1 Initiation of the channel mode modify procedure + +The network initiates the procedure by sending a CHANNEL MODE MODIFY message to the mobile station. This message contains: + +- a channel description of the channel(s) on which the mode in the CHANNEL MODE MODIFY message shall be applied; and +- the mode to be used on that channel, or on all the channels of a channel set in a multislot configuration. +- Optionally, when the channel mode indicates that a multi-rate speech codec must be applied, the MultiRateConfiguration to be used. The MultiRateConfiguration IE defines the set of codec modes and related information to use after the mode modify procedure. + +If the channel mode is changed from a non multi-rate speech codec to a multi-rate speech codec or if the channel mode is changed from a multi-rate speech codec to another mutli-rate speech version but the old multi-rate speech version and the new multi-rate speech version are not the same, the CHANNEL MODE MODIFY message shall contain the MultiRate Configuration IE, which defines the set of codec modes and related information to use as a new mode. + +If the old channel mode and the new channel mode are both multi-rate speech codec and if the old multi-rate speech version and the new multi-rate speech version are the same, the MultiRate Configuration IE may not be present. If not present, the MS shall go on with the current multi-rate speech configuration. + +#### 3.4.6.1.2 Completion of channel mode modify procedure + +When it has received the CHANNEL MODE MODIFY message, the mobile station sets the mode for the indicated channel, and if that is in a multislot configuration, the whole channel set and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the ordered channel mode. + +This applies whether the mode commanded by the CHANNEL MODE MODIFY is different from the one used by the mobile station or whether it is already in use. + +#### 3.4.6.1.3 Abnormal cases + +If the new mode is multi-rate speech codec and if the MultiRate Configuration IE is inconsistent, the MS shall ignore the CHANNEL MODE MODIFY message and shall not send CHANNEL MODE MODIFY ACKNOWLEDGE message to the network. + +No other specific action for a lower layer failure is specified in this sub-clause. If the mobile station does not support the indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL MODE MODIFY ACKNOWLEDGE message. + +### 3.4.6.2 Channel mode modify procedure for a voice group call talker + +#### 3.4.6.2.1 Initiation of the channel mode modify procedure + +The network initiates the procedure by sending a CHANNEL MODE MODIFY message to the mobile station. This message contains: + +- a channel description of the channel on which the CHANNEL MODE MODIFY message is sent; and + +- the new channel mode to be used on the channel; and +- optionally, the VGCS target mode information element defining which RR mode (i.e. dedicated mode or group transmit mode) is to be used with the new channel mode. If this information element is not present, the RR mode shall be assumed to be the same as with the previous channel mode. The VGCS target mode information element shall also indicate the group cipher key number for the group cipher key to be used after the channel mode change. If the information element is not present, the ciphering mode and ciphering key shall be the same as with the previous channel mode. Mobile stations not supporting VGCS talking shall ignore the CHANNEL MODE MODIFY message if the VGCS target mode information element is included in the message and shall send an RR STATUS message to the network with cause #96. + +When the RR mode to be used after the channel mode change is group transmit mode and the group cipher key number indicates that the resource is ciphered (ie group key number is non zero), then the VGCS Ciphering Parameters Information Element shall be included to provide the VSTK\_RAND and Cell\_Global\_Count. The MS shall adjust and maintain the Cell Global Count using the procedure described in sub-clause 3.3.3.1. The MS shall then calculate the ciphering keys as described in 3GPP TS 43.020. Also, the MS shall fetch from the USIM the identity of its ciphering algorithm to use on the resource, as described in 3GPP TS 43.020. + +When the RR mode used before the channel mode change and the RR mode to be used after the channel mode change are both dedicated mode and the channel was ciphered before the channel mode change, then new channel shall continue to be ciphered after the channel mode change with the same ciphering algorithm and ciphering keys as previously used. + +If a VGCS target mode information element indicating a RR mode of dedicated mode and a non zero group cipher key number is included, the mobile station shall behave as if it would not support the indicated channel mode. + +#### 3.4.6.2.2 Completion of mode change procedure + +When it has received the CHANNEL MODE MODIFY message, the mobile station changes the mode for the indicated channel and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the new channel mode. + +#### 3.4.6.2.3 Abnormal cases + +No specific action for a lower layer failure is specified in this sub-clause. If the mobile station does not support the indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL MODE MODIFY ACKNOWLEDGE message. + +### 3.4.7 Ciphering mode setting procedure + +In dedicated mode, the ciphering mode setting procedure is used by the network to set the ciphering mode, i.e. whether or not the transmission is ciphered, and if so which algorithm to use. The procedure shall only be used to change from "not ciphered" mode to "ciphered" mode, or vice-versa, or to pass a CIPHERING MODE COMMAND message to the mobile station while remaining in the "not ciphered" mode. The ciphering mode setting procedure is always triggered by the network and it only applies to dedicated resources. + +The cipher mode setting procedure shall not be applied in group transmit mode. + +#### 3.4.7.1 Ciphering mode setting initiation + +The network initiates the ciphering mode setting procedure by sending a CIPHERING MODE COMMAND message to the mobile station on the main signalling link, indicating whether ciphering shall be used or not, and if yes which algorithm to use. + +Additionally, the network may, by the use of the cipher response information element, request the mobile station to include its IMEISV in the CIPHERING MODE COMPLETE message. + +The new mode is applied for reception on the network side after the message has been sent. + +#### 3.4.7.2 Ciphering mode setting completion + +Whenever the mobile station receives a valid CIPHERING MODE COMMAND message, it shall, if a SIM is present and considered valid by the ME and the ciphering key sequence number stored on the SIM indicates that a ciphering + +key is available, load the ciphering key stored on the SIM into the ME. A valid CIPHERING MODE COMMAND message is defined to be one of the following: + +- one that indicates "start ciphering" and is received by the mobile station in the "not ciphered" mode; +- one that indicates "no ciphering" and is received by the MS in the "not ciphered" mode; or +- one that indicates "no ciphering" and is received by the mobile station in the "ciphered" mode. + +Other CIPHERING MODE COMMAND messages shall be regarded as erroneous, an RR STATUS message with cause "Protocol error unspecified" shall be returned, and no further action taken. + +Upon receipt of the CIPHERING MODE COMMAND message indicating ciphering, the mobile station shall start transmission and reception in the indicated mode. A mobile station supporting Selective Ciphering of Downlink SACCH shall be able to decode both ciphered and not-ciphered SACCH blocks (see sub-clause 3.4.7a). + +When the appropriate action on the CIPHERING MODE COMMAND has been taken, the mobile station sends back a CIPHERING MODE COMPLETE message. If the "cipher response" field of the cipher response information element in the CIPHERING MODE COMMAND message specified "IMEI must be included" the mobile station shall include its IMEISV in the CIPHERING MODE COMPLETE message. + +Upon receipt of the CIPHERING MODE COMPLETE message or any other correct layer 2 frame which was sent in the new mode, the network starts transmission in the new mode. + +![Sequence diagram illustrating the ciphering mode setting sequence between a mobile station and a network.](69733eeb3ef32197543f66f22a431771_img.jpg) + +``` + +sequenceDiagram + participant MS as mobile station + participant NW as network + Note left of MS: start transmission and reception in new mode + NW->>MS: CIPH MOD CMD + Note right of NW: start reception in new mode + MS->>NW: CIPH MOD COM + Note right of NW: start transmission in new mode + +``` + +The diagram shows the interaction between a mobile station (MS) and a network (NW) for setting the ciphering mode. + 1. The MS starts transmission and reception in the new mode (indicated by an arrow pointing right from the left). + 2. The NW sends a CIPH MOD CMD message to the MS (indicated by a long arrow pointing left from the right). + 3. Upon receiving the command, the NW starts reception in the new mode (indicated by an arrow pointing left from the right). + 4. The MS sends a CIPH MOD COM message back to the NW (indicated by a long arrow pointing right from the left). + 5. Upon receiving the complete message, the NW starts transmission in the new mode (indicated by an arrow pointing right from the right). + +Sequence diagram illustrating the ciphering mode setting sequence between a mobile station and a network. + +**Figure 3.4.7.2.1: Ciphering mode setting sequence** + +Upon starting ciphering with algorithm A5/1, the network may change the contents of the *Neighbour Cell Description* and *Neighbour Cell Description 2* information elements and *SI 6 Rest Octets* spare padding (see sub-clauses 10.5.2.22, 10.5.2.22a and 10.5.2.35a, respectively) in the System Information messages to be sent to the mobile station, compared to those sent prior to ciphering and (for the *Neighbour Cell Description* and *Neighbour Cell Description 2* information elements) those broadcast on the BCCH. In this case, such changes should be performed immediately after reception of the CIPHERING MODE COMPLETE message by the network. + +### 3.4.7a Selective Ciphering of Downlink SACCH + +Selective Ciphering of Downlink SACCH, when ciphering is started between the network and the mobile station in dedicated mode or dual-transfer mode, refers to the mechanism used by the network in downlink to cipher or not to cipher any given individual SACCH block selectively according to its content; and to the ability of the mobile station to decode downlink SACCH blocks whether any given individual SACCH block is ciphered or not. + +The use of Selective Ciphering of Downlink SACCH is under control of the network. The network may use Selective Ciphering of Downlink SACCH only if supported by the mobile station, as indicated in the MS Classmark 3 IE (see 3GPP TS 24.008). The network shall ensure that when Selective Ciphering of Downlink SACCH is used, it is used as long as ciphering is active during the RR connection. + +If Selective Ciphering of Downlink SACCH is used, the network shall ensure that: + +- a SACCH block shall not be ciphered if it contains any of the following RR messages: SYSTEM INFORMATION TYPE 5, SYSTEM INFORMATION TYPE 5bis, SYSTEM INFORMATION TYPE 5ter, + +SYSTEM INFORMATION TYPE 6, SYSTEM INFORMATION TYPE 14, MEASUREMENT INFORMATION, EXTENDED MEASUREMENT ORDER; and + +- a SACCH block shall be ciphered if it contains SAPI 3 data (SMS), see 3GPP TS 44.006, optionally it should not be ciphered if carrying a CP-Ack message (see 3GPP TS 24.011). + +A mobile station that supports Selective Ciphering of Downlink SACCH may use the above information to determine if Selective Ciphering of Downlink SACCH is used or not. + +### 3.4.8 Additional channel assignment procedure + +NOTE: In the present state of 3GPP TS 44.003, this procedure is only possible for the TCH/H + ACCHs to TCH/H + TCH/H + ACCHs transition. As a consequence it is not needed for simple mobile stations. The description of the procedure is in general terms to cope with possible evolution. + +In dedicated mode, a change of channel configuration to include an additional channel can be requested by upper layers. + +The additional channel assignment procedure shall not be applied in group transmit mode, + +The purpose of the additional assignment procedure is to allocate an additional dedicated channel to a mobile station while keeping the previously allocated channels. In particular the main DCCH and the SACCH are not modified, and signalling exchanges are not interrupted. + +The additional assignment procedure may happen only in dedicated mode. It is used for instance for the transition from the TCH/H + ACCHs configuration to the TCH/H + TCH/H + ACCHs configuration. + +The additional assignment procedure is always initiated by the network. + +#### 3.4.8.1 Additional assignment procedure initiation + +The network initiates the procedure by sending an ADDITIONAL ASSIGNMENT message to the mobile station on the main DCCH. The ADDITIONAL ASSIGNMENT message contains the description of the newly assigned channel. + +On receipt of the message, the mobile station activates the new channel. + +#### 3.4.8.2 Additional assignment procedure completion + +The mobile station sends an ASSIGNMENT COMPLETE message to the network on the channel, on which it receives the ADDITIONAL ASSIGNMENT message. + +#### 3.4.8.3 Abnormal cases + +A lower layer failure occurring during the procedure is treated according to the general case (see sub-clause 3.4.13.2). + +The network considers the channel as allocated from the sending of the ADDITIONAL ASSIGNMENT message. As a consequence, if a re-establishment occurs, the network will consider the context as if the mobile station has received the message, and the new configuration allocated after the re-establishment may differ from the one the mobile station had before the re-establishment. + +### 3.4.9 Partial channel release procedure + +In dedicated mode, a change of channel configuration to release one channel can be requested by upper layers. + +The partial channel release procedure shall not be applied in group transmit mode. + +The purpose of this procedure is to deactivate part of the dedicated channels in use. The channel configuration remains dedicated. + +NOTE: In the present state of 3GPP TS 44.003, this procedure is only possible for the TCH/H + TCH/H + ACCHs to TCH/H + ACCHs transition. As a consequence it is not needed for simple mobile stations. + +The partial release procedure is always initiated by the network. + +### 3.4.9.1 Partial release procedure initiation + +The network initiates the partial release by sending a PARTIAL RELEASE message to the mobile station on the main DCCH. + +On receipt of the PARTIAL RELEASE message the mobile station: + +- Initiates the disconnection of all the link layer connections carried by the channel to be released; +- Simultaneously initiates the connection on remaining channels of the data link layer connections that have been released; +- Deactivates the physical channels to be released; +- Sends a PARTIAL RELEASE COMPLETE to the network on the (possibly new) main signalling link. + +### 3.4.9.2 Abnormal cases + +A lower layer failure is treated following the general rules as specified in sub-clause 3.4.13.2. + +Moreover, on the network side, the channel configuration nature is set from the sending of the PARTIAL RELEASE message onward. As a consequence, any new assignment after a re-establishment may concern a different channel configuration nature from the one known by the mobile station before the re-establishment. + +## 3.4.10 Classmark change procedure + +In dedicated mode or in group transmit mode, this procedure allows the mobile station to indicate to the network a change of characteristics reflected in the classmark (e.g. due to addition of power amplification). Furthermore, a mobile station which implements the "controlled early classmark sending" option may also send a CLASSMARK CHANGE message and/or a UTRAN CLASSMARK CHANGE message and/or a CDMA2000 CLASSMARK CHANGE message and/or a GERAN IU MODE CLASSMARK CHANGE message as described in sub-clause 3.3.1.1.4.1, even if no change of characteristics has occurred. + +The mobile station sends a CLASSMARK CHANGE message to the network. This message contains the new mobile station classmark 2 information element. It may also contain a Classmark 3 Information Element. There is no acknowledgement from the network at layer 3. + +A UTRAN capable MS, independently of sending a CLASSMARK CHANGE message, sends a UTRAN CLASSMARK CHANGE message to the network. This message contains the INTER RAT HANDOVER INFO defined in 3GPP TS 25.331. There is no acknowledgement from the network at layer 3. + +NOTE: For the network, UTRAN predefined configuration status information may be invalid if the PLMN where predefined configurations were read and the PLMN of the connected cell do not use common predefined configurations. + +A CDMA2000 capable MS sends a CDMA2000 CLASSMARK CHANGE message to the network. + +A GERAN *Iu mode* capable MS, independently of sending a CLASSMARK CHANGE message, sends a GERAN IU MODE CLASSMARK CHANGE message to the network. This message contains the MS GERAN IU MODE RADIO ACCESS CAPABILITY IE defined in 3GPP TS 44.118. There is no acknowledgement from the network at layer 3. + +If the CLASSMARK CHANGE and one or more of these additional messages are to be sent by the MS, the CLASSMARK CHANGE message shall be sent first. + +## 3.4.11 Classmark interrogation procedure + +This procedure allows the network to request additional classmark information from the mobile station (e.g. if the information initially sent by the mobile station is not sufficient for network decisions). For a multi-RAT MS this procedure allows in addition the network to request INTER RAT HANDOVER INFO or CDMA2000 MS Capability information and/or GERAN *Iu mode* MS radio capability. + +### 3.4.11.1 Classmark interrogation initiation + +The network initiates the classmark interrogation procedure by sending a CLASSMARK ENQUIRY message to the mobile station on the main DCCH. + +### 3.4.11.2 Classmark interrogation completion + +On receipt of the CLASSMARK ENQUIRY message the mobile station sends a CLASSMARK CHANGE and/or a UTRAN CLASSMARK CHANGE and/or a CDMA2000 CLASSMARK CHANGE and/or a GERAN IU MODE CLASSMARK CHANGE message to the network on the main DCCH. The Classmark Enquiry Mask information element in the CLASSMARK ENQUIRY message indicates the type of request. If the Classmark Enquiry Mask information element is not included in the CLASSMARK ENQUIRY message, this indicates a request for CLASSMARK CHANGE message. + +The CLASSMARK CHANGE message contains the mobile station classmark 2 information element. It may also contain a Classmark 3 Information Element. + +The UTRAN CLASSMARK CHANGE message contains the INTER RAT HANDOVER INFO (UTRAN specific information). + +The CDMA2000 CLASSMARK CHANGE message contains CDMA2000 UE capability information. + +The GERAN IU MODE CLASSMARK CHANGE message contains MS GERAN IU MODE RADIO ACCESS CAPABILITY IE (see 3GPPP TS 44.118). + +If the CLASSMARK CHANGE and one or more of these additional messages are to be sent by the MS, the CLASSMARK CHANGE message shall be sent first. + +### 3.4.12 Indication of notifications and paging information + +Only applicable for mobile stations supporting VGCS or VBS. + +In dedicated mode or in group transmit mode, the RR entity shall provide indications to the upper layer on all received notifications for voice group calls or voice broadcast calls according to the VGCS or VBS subscription data stored in the mobile station. The indication shall include the notified group or broadcast call reference and possibly the related priority VSTK\_RAND and CELL\_GLOBAL\_COUNT, if provided. + +In group transmit mode, if the mobile station has decoded a paging message with the own mobile station identity on the PCH or on the voice group call channel downlink, the RR entity shall provide an indication to the upper layers, together with the related priority, if applicable. + +In group transmit mode, if the RR entity receives information on the voice group call channel of the existence of a paging message in its paging subgroup of the PCH, the RR entity shall pass this information to the upper layers together with the related priority if provided (see also sub-clauses 3.3.2 and 3.3.3). + +In group transmit mode, when a paging message that contains an indication of the paging is received on the VBS or VGCS channel, this indication shall be passed to the upper layer. If no paging cause is present in the paging message the VBS/VGCS mobile station shall assume that the paging is for a mobile terminating call. + +### 3.4.13 RR connection release procedure + +#### 3.4.13.1 Normal release procedure + +The release of the RR connection can be requested by upper layers. + +The purpose of this procedure is to deactivate all the dedicated channels in use. When the channels are released and the mobile station is not IMSI attached for GPRS services (clause 4), the mobile station returns to the CCCH configuration, idle mode. + +If the mobile station is IMSI attached for GPRS services the following four cases apply: + +- If the mobile station has no radio resources (i.e., no temporary block flow) allocated on a PDCH, the mobile station returns to the PCCCH or CCCH configuration, packet idle mode; +- If the mobile station is operating in dual transfer mode when the RR connection is released, the radio resources allocated on a PDCH are released, the mobile station returns to the PCCCH or CCCH configuration, packet idle mode; + +- If the mobile station is operating in dual transfer mode when the RR connection is released and the mobile station and the network support enhanced DTM CS release procedure, the mobile station may maintain its radio resources allocated on one or more PDCH(s) and enter packet transfer mode; +- Otherwise, if the mobile station has radio resources allocated on a PDCH, the mobile station enters packet transfer mode. + +The channel release procedure can be used in a variety of cases, including TCH release after a call release, and DCCH release when a dedicated channel allocated for signalling is released. + +In dedicated mode and group transmit mode, the channel release procedure is always initiated by the network. + +#### 3.4.13.1.1 Channel release procedure initiation in dedicated mode and in group transmit mode + +The network initiates the channel release by sending a CHANNEL RELEASE message to the mobile station on the main DCCH, starts timer T3109 and deactivates the SACCH. + +On receipt of a CHANNEL RELEASE message the mobile station starts timer T3110 and disconnects the main signalling link. When T3110 times out, or when the disconnection is confirmed, the mobile station deactivates all channels, considers the RR connection as released, and returns to CCCH idle mode, returns to PCCCH or CCCH packet idle mode or enters packet transfer mode. + +NOTE 1: Data Links other than the main signalling link are disconnected by local end link release. + +If case of dedicated mode, on the network side, when the main signalling link is disconnected, the network stops timer T3109 and starts timer T3111. When timer T3111 times out, the network deactivates the channels, they are then free to be allocated to another connection. + +NOTE 2: The sole purpose of timer T3111 is to let some time to acknowledge the disconnection and to protect the channel in case of loss of the acknowledge frame. + +If timer T3109 times out, the network deactivates the channels; they are then free to be allocated to another connection. + +The CHANNEL RELEASE message will include an RR cause indication as follows: + +- #0: if it is a normal release, e.g. at the end of a call or at normal release of a DCCH. +- #1: to indicate an unspecified abnormal release. +- #2, #3 or #4: to indicate a specific release event. +- #5: if the channel is to be assigned for servicing a higher priority call (e.g. an emergency call). +- #65: if e.g. a handover procedure is stopped because the call has been cleared. + +The CHANNEL RELEASE message may include the information element BA Range which may be used by a mobile station in its selection algorithm (see 3GPP TS 45.008 and 3GPP TS 23.022). + +The CHANNEL RELEASE message may include the information element "Cell selection indicator after release of all TCH and SDCCH" which shall be used by the mobile station in its cell selection algorithm after release of all TCH and SDCCH (see 3GPP TS 45.008). + +The CHANNEL RELEASE message may include Individual priorities IE to convey individual priorities information to the MS (see subclause 3.2.3.3). When the MS receives an Individual priorities IE it shall start an instance of timer T3230 with the value supplied in the Individual priorities IE. + +If the network redirects a mobile station towards E-UTRAN, it proceeds as follows: + +- The network shall use the information element "Cell selection indicator after release of all TCH and SDCCH" in the channel release message for redirection towards an EARFCN in the E-UTRAN band numbered less than 65. +- The network shall use the information element "individual priorities" in the channel release message for redirection towards an EARFCN in the E-UTRAN band numbered greater than 64. + +Mobile stations not supporting VGCS or VBS listening shall ignore Group Channel Description (or Group Channel Description 2), Group Cipher Key Number, Cell Channel Description, Talker Identity and Talker Priority Status information elements if present in the message and perform the channel release procedure as normal. + +For mobile stations supporting VGCS listening, the following procedures apply: + +The CHANNEL RELEASE message may include the Group Channel Description, Group Channel Description 2, and possibly the Cell Channel Description information element(s). In this case, the mobile station shall release the layer 2 link, enter the group receive mode and give an indication to the upper layer. The BSS may provide the Group Channel Description 2 in the CHANNEL RELEASE message to the current talker only when the voice group call channel cannot be fully described by the Group Channel Description IE and the Cell Channel Description IE. If a CHANNEL RELEASE message with neither Group Channel Description, nor Group Channel Description 2, nor Cell Channel Description is received, or if those information elements do not properly specify a group channel, the normal behaviour applies. + +If ciphering is applied on the VGCS or VBS channel, the network shall provide in the CHANNEL RELEASE message with the Group Cipher Key Number information element for the group cipher key to be used by the mobile station for reception of the VGCS or VBS channel. If this information element is not included, no ciphering is applied on the VGCS or VBS channel. When the group cipher key indicates that the group call is ciphered (ie group key is non zero), then the VGCS Ciphering Parameters Information Element shall be included to provide the VSTK\_RAND and Cell\_Global\_Count. The MS shall adjust and maintain the Cell Global Count using the procedure described in sub-clause 3.3.3.1. The MS shall then calculate the ciphering keys as described in 3GPP TS 43.020. Also, the MS shall fetch from the USIM the identity of its ciphering algorithm to use on the VGCS or VBS channel, as described in 3GPP TS 43.020. + +For mobile stations supporting VGCS talking, the following procedures apply: + +If the VGCS talking subscriber is being pre-empted by a higher priority talker, then the network shall include the talker priority status information element. The network shall also include, when available, the talker identity associated with the new talker. + +A mobile station not supporting the "GPRS" option shall consider the GPRS Resumption information element as an information element unknown in the CHANNEL RELEASE message and perform the RR connection release procedure as normal. + +For a mobile station supporting the "GPRS" option, the following additional procedures also apply: + +- The CHANNEL RELEASE message may include the information element GPRS Resumption. If the GPRS Resumption information element indicates that the network has resumed GPRS services, the RR sublayer of the mobile station shall indicate a RR GPRS resumption complete to the MM sublayer, see clause 4. If the GPRS Resumption information element indicates that the network has not successfully resumed GPRS services, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see clause 4. +- If the mobile station has performed the GPRS suspension procedure (see sub-clause 3.4.25) and the GPRS Resumption information element is not included in the message, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see clause 4. +- If the mobile station has not performed the GPRS suspension procedure and the GPRS Resumption information element is not included in the message, the mobile station shall perform the RR connection release procedure as normal. + +#### 3.4.13.1.1a Channel release procedure initiation in dual transfer mode + +If the mobile station and the network support enhanced DTM CS release procedure, the network may delay the release of the RR connection until the mobile station has received the needed system information, in order to maintain the radio resources on the PDCH(s) after the release of the RR connection. + +The network initiates enhanced DTM CS release procedure by sending the PACKET CS RELEASE INDICATION message as specified in 3GPP TS 44.060. + +If the acquisition of system information is completed, the network shall send a CHANNEL RELEASE message on the main DCCH with the *Enhanced DTM CS Release Indication* field indicating that the mobile station is allowed to continue in packet transfer mode after the release of the RR connection. Upon receipt of the CHANNEL RELEASE message the mobile station starts timer T3110 and disconnects the main signalling link. When T3110 times out, or when + +the disconnection is confirmed, the mobile station deactivates all dedicated channels, considers the RR connection as released and enters packet transfer mode. + +The network may for any reason send a CHANNEL RELEASE message on the main DCCH with the *Enhanced DTM CS Release Indication* field indicating that the mobile station is not allowed to continue in packet transfer mode after the release of the RR connection. Upon receipt of the CHANNEL RELEASE message the mobile station starts timer T3110 and disconnects the main signalling link. When T3110 times out, or when the disconnection is confirmed, the mobile station deactivates all channels, considers the RR connection as released, and enters packet idle mode. + +### 3.4.13.1.2 Abnormal cases + +Abnormal cases are taken into account in the main part of the description of the procedure. + +### 3.4.13.2 Radio link failure in dedicated mode or dual transfer mode + +The main part of these procedures concerns the "normal" cases, i.e. those without any occurrence of loss of communication means. A separate paragraph at the end of the description of each procedure treats the cases of loss of communication, called a radio link failure. In dedicated mode, in most of the cases the reaction of the mobile station or the network is the same. Those reactions are described in this sub-clause to avoid repetitions. + +A radio link failure can be detected by several ways: + +- 1) By analysis of reception at layer 1, as specified in 3GPP TS 45.008 and sub-clause 3.4.1.1. +- 2) By a data link layer failure as specified in 3GPP TS 44.006, on the main signalling link. A data link failure on any other data link shall not be considered as a radio link failure. +- 3) When a lower layer failure happens while the mobile station attempts to connect back to the old channels in a channel assignment procedure, handover procedure, DTM handover procedure or DTM assignment procedure with relocation of the RR connection. +- 4) In some cases where timers are started to detect the lack of answer from the other party, as described in clause 3. + +The two first cases are known by the term "lower layer failure". + +### 3.4.13.2.1 Mobile side + +When a radio link failure is detected by the mobile station, + +- the MS shall perform a local end release on all signalling links unless otherwise specified; +- the mobile station shall deactivate all dedicated channels; +- if the mobile station is in dual transfer mode, it shall abort the packet resources; +- the RR sublayer of the mobile station shall indicate an RR connection failure to the MM sublayer unless otherwise specified. + +NOTE: Upper layers may decide on a re-establishment (see 3GPP TS 24.008). + +When a mobile station which has performed the GPRS suspension procedure (sub-clause 3.4.25) detects a radio link failure, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see clause 4. + +### 3.4.13.2.2 Network side + +In dedicated mode, the reaction of the network to a lower layer failure depends on the context. Except when otherwise specified, it is to release the connection either with the channel release procedure as specified in sub-clause 3.5.1, or with the following procedure. The network starts timer T3109 and deactivates the SACCH (and hence to stop transmission on the SACCH). If the mobile station is in dual transfer mode, the network also aborts all the allocated packet resources. + +When a radio link failure has been detected, an indication is passed to the upper Mobility Management sublayer on the network side. + +When timer T3109 expires, the network can regard the channels as released and free for allocation. + +This procedure relies on the fact that if a mobile station does not receive the SACCH for some time, it completely releases the channels (cf. 3GPP TS 45.008). + +NOTE: The network should maintain for a while the transaction context in order to allow call re-establishment. The length of timer is for further study. + +When a mobile station which has performed the GPRS suspension procedure (sub-clause 3.4.25) detects a radio link failure, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see 3GPP TS 24.008. + +### 3.4.13.3 RR connection abortion in dedicated mode or dual transfer mode + +The mobile station aborts the RR connection by initiating a normal release of the main signalling link, performing local end releases on all other signalling links, disconnecting all traffic channels, if any, and aborting all the packet resources, if any. + +When a mobile station which has performed the GPRS suspension procedure (sub-clause 3.4.25) aborts the RR connection, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see 3GPP TS 24.008. + +### 3.4.13.4 Uplink release procedure + +If the uplink release is requested by the upper layer in group transmit mode, the mobile station shall send an UPLINK RELEASE message on the voice group call channel uplink, perform a release of the main signalling link and go back to the group receive mode. + +If the uplink release is requested by the upper layer when the VGCS talker is on a dedicated channel, the mobile station shall send an UPLINK RELEASE message on the dedicated channel. When a mobile station receives a CHANNEL RELEASE message from the network, the mobile station shall perform a release of the main signalling link. The mobile station enters group receive mode if the CHANNEL RELEASE message includes the Group Channel Description (or Group Channel Description 2) and possibly the Cell Channel Description information element(s), otherwise it enters idle mode. + +If the UPLINK RELEASE message is received from the network on the voice group call channel downlink, the MS shall perform a release of the main signalling link and go back to the group receive mode. + +### 3.4.13.5 Radio link failure in group transmit mode + +The main part of these procedures concerns the "normal" cases, i.e. those without any occurrence of loss of communication means. A separate paragraph at the end of the description of each procedure treats the cases of loss of communication, called a radio link failure. In group transmit mode, in most of the cases the reaction of the mobile station or the network is the same. Those reactions are described in this sub-clause to avoid repetitions. + +A radio link failure can be detected by several ways: + +- 1) By analysis of reception at layer 1, as specified in 3GPP TS 45.008 and sub-clause 3.4.1.1. +- 2) By a data link layer failure as specified in 3GPP TS 44.006, on the main signalling link. A data link failure on any other data link shall not be considered as a radio link failure. +- 3) When a lower layer failure happens while the mobile station attempts to connect back to the old channels in a channel assignment procedure or handover procedure. +- 4) In some cases where timers are started to detect the lack of answer from the other party, as described in clause 3. + +The two first cases are known by the term "lower layer failure". + +#### 3.4.13.5.1 Mobile side + +When a radio link failure is detected by the mobile station: + +- the MS shall perform a local end release on all signalling links; +- the mobile station shall go back to idle mode and, when possible, to group receive mode; + +- the RR sublayer of the mobile station shall indicate an RR connection failure to the MM sublayer unless otherwise specified. + +### 3.4.13.5.2 Network side + +When the uplink has been allocated and the network detects a lower layer failure, the network shall set the uplink free and provide an UPLINK FREE message on the main signalling channel, when appropriate. + +When a radio link failure has been detected, an indication is passed to the upper Mobility Management sublayer on the network side. + +### 3.4.13.6 RR connection abortion requested by upper layers + +The purpose of this procedure is to abort the RR connection and bar the current cell. The procedure is requested by upper layers when they determine that the network has failed an authentication check (see 3GPP TS 24.008). + +On request of the upper layers the MS shall locally abort the RR connection and behave as if a lower layer failure has occurred. The MS shall treat the current cell as barred (see 3GPP TS 23.022). + +## 3.4.14 Receiving a RR STATUS message by a RR entity. + +If the RR entity of the mobile station receives a RR STATUS message no transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible. + +The actions to be taken on receiving a RR STATUS message in the network are an implementation dependent option see also clause 8. + +## 3.4.15 Group receive mode procedures + +Only applicable for support of VGCS listening or VBS listening. + +### 3.4.15.1 Mobile station side + +#### 3.4.15.1.1 Reception of the VGCS or VBS channel + +##### 3.4.15.1.1.1 General + +In group receive mode, the mobile station receives the downlink of the voice broadcast channel or voice group call channel for which the channel description was provided within the notification message or in the related command message. The mobile station should also listen to the CCCH of the serving cell. Moreover, it measures the received levels on the serving cell and on the neighbour cells to assess the need for a cell reselection as specified in 3GPP TS 45.008. The general cell reselection procedure for the mobile station in group receive mode is described in 3GPP TS 23.022. If the group call is ciphered then the MS on cell reselection shall recalculate the cipher keys and obtain the identity of its ciphering algorithm as described in sub-clause 3.4.15.1.1.2. + +Information on neighbour cells used for cell reselection and reception of the VGCS or VBS channel in the neighbour cells may be provided on the downlink messages (see sub-clause 3.4.15.1.2). If no such information is provided or information is missing, the mobile station shall try to read this information on the BCCH and NCH of the neighbour cells. + +##### 3.4.15.1.1.2 Reception on ciphered VGCS or VBS channel + +The MS shall derive the group cipher key using the following parameters: + +- VSTK\_RAND - obtained via the notification message; +- CELL\_GLOBAL\_COUNT - obtained via the NCH, Notification/FACCH or Paging Request Type 1; +- CGI - obtained via System Information 3 or 4; +- Group Cipher Key Number - obtained via the group call reference. + +The derivation of the key from the above parameters is explained in 3GPP TS 43.020. + +The MS shall obtain the identity of its ciphering algorithm from its USIM, as described in 3GPP TS 43.020. + +### 3.4.15.1.2 Monitoring of downlink messages and related procedures + +Mobile stations in group receive mode shall monitor messages related to the following procedures on the VGCS or VBS channel downlink and act appropriately in order to be able to keep receiving the VGCS or VBS channel downlink. + +All messages for mobile stations in group receive mode shall be sent in UI format on the VGCS or VBS channel downlink. Mobile stations in group receive mode shall ignore all messages which are not sent in UI format or which are not related to the following mentioned procedures. + +The mobile should also monitor messages on the PCH or NCH of the current cell. + +#### 3.4.15.1.2.1 (void) + +#### 3.4.15.1.2.2 (void) + +#### 3.4.15.1.2.3 Channel mode modify procedure + +The mobile station shall receive CHANNEL MODE MODIFY messages. The mobile station shall use the new channel mode but shall not transmit any response to the network. + +#### 3.4.15.1.2.4 Notification and paging information + +The mobile station shall monitor messages related to notification and paging procedures. + +The RR entity shall provide indications on all received notifications for voice group calls or voice broadcast calls to the upper layer. The indication shall include the notified group or broadcast call reference and, if provided, and if the mobile station supports eMLPP the related priority. + +On request by the upper layer to join another voice broadcast call or voice group call for which a corresponding notification has been received on the VGCS or VBS channel downlink, the RR entity shall read the corresponding notification on the NCH. + +If the mobile station has received a paging message with its own mobile station identity on the PCH or on the voice broadcast channel or voice group call channel downlink, the RR entity shall provide an indication to the upper layers, together with the related priority, if applicable. + +When a paging message that contains an indication of the paging cause (mobile terminating call or short message) is received on the VBS or VGCS channel, this indication shall also be passed to the upper layer. If no paging cause is present in the paging message the VBS/VGCS mobile station shall assume that the paging is for a mobile terminating call. + +#### 3.4.15.1.2.4.1 Use of Reduced NCH monitoring + +This sub-clause applies to mobile stations which are in group receive mode or group transmit mode of dedicated mode and which in addition want to receive notification messages for other voice broadcast calls or voice group calls and which aim at reducing the reception load. + +When the MS in group receive mode or group transmit mode enters a cell, it may read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical. Then it may stop reading the NCH until it receives on the SACCH an NLN(SACCH) different from the last previously received NLN. + +For this, a parameter is provided on the SACCH in the SYSTEM INFORMATION TYPE 6 message: + +- NLN(SACCH): Notification List Number. + +If a mobile station receives on the SACCH an NLN(SACCH) different from the last received NLN it may read the NCH until it has received at least two messages on the NCH indicating NLN with the two last received NLN being identical. + +If a message in the SACCH is not received correctly the MS may read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical. + +#### 3.4.15.1.2.5 Uplink status messages + +Mobile stations supporting VGCS talking shall monitor the VGCS uplink control related messages UPLINK FREE and UPLINK BUSY. + +#### 3.4.15.1.2.6 Channel release message + +The mobile station shall receive CHANNEL RELEASE messages. On receipt of a CHANNEL RELEASE message, the RR entity shall go to idle mode and give an indication to the upper layer. (See also sub-clause 3.4.15.1.4.1, 4th paragraph.) + +#### 3.4.15.1.2.7 Information on paging channel restructuring + +On receipt of a SYSTEM INFORMATION TYPE 6 message indicating that paging channel restructuring has taken place, if the mobile station wants to be able to read its paging subchannel while in group receive mode or group transmit mode, the mobile station should read the related messages on the BCCH to know the position of its paging group. + +### 3.4.15.1.3 Uplink reply procedure + +In Group Receive mode, on receipt of an UPLINK FREE message with an uplink access request indication from the network on the voice group call channel downlink or voice broadcast channel downlink, the mobile station shall send two UPLINK ACCESS messages on the voice group call channel uplink or voice broadcast channel uplink with establishment cause "Reply on uplink access request" and then stop immediately transmitting on the uplink. + +The first UPLINK ACCESS message shall be transmitted by the mobile station with a random delay between 0 and 20 ms. The second UPLINK ACCESS messages shall be repeated after a further period of 100 ms plus a random delay between 0 and 20 ms. The UPLINK ACCESS messages shall be sent unciphered. + +If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the mobile station shall use this UIC for the coding of the UPLINK ACCESS messages. If no UIC is provided, the mobile station shall use the BSIC received of the serving cell, for instance as received from the initial synchronization. + +### 3.4.15.1.4 Leaving the group receive mode + +#### 3.4.15.1.4.1 Returning to idle mode + +If the mobile station enters a new cell in which: + +- notifications for the current group or broadcast call are sent; but +- no VGCS or VBS channel description for the current group or broadcast call is provided, + +the mobile station shall go to idle mode and give an indication to the upper (sub-)layers. + +NOTE: Upper (sub-)layers then can request the establishment of an RR connection in order to be informed about the channel description by the network. + +If the mobile station enters a cell in which notifications for the current group or broadcast call are not sent, the mobile station shall disconnect locally the TCH, go to idle mode and give an indication to the upper (sub-)layers. + +On request by the upper layer in order to respond to a paging message the RR entity shall go to the idle mode in order to establish a dedicated RR connection. + +On receipt of a CHANNEL RELEASE message in UI format from the network the RR entity shall go to idle mode and give an indication to the upper layer. + +If the upper layer requests to abort the group receive mode, the mobile station shall go back to idle mode. + +#### 3.4.15.1.4.2 Going to group transmit mode + +Only applicable for mobile stations supporting VGCS talking. + +If the upper layer requests an uplink access, the mobile station shall perform the uplink investigation procedure as defined in sub-clause 3.3.1.2.1.1 and 3.3.1.2.1.1a. + +If the uplink investigation procedure is not successful, the mobile station shall give an indication to the upper layers and remain in group receive mode. + +If the uplink investigation procedure is successful, the uplink access procedure as defined in sub-clause 3.3.1.2.1.2 and 3.3.1.2.1.2a or the priority uplink request procedure as defined in sub-clause 3.3.1.2.1.2b is initiated. + +If the uplink access procedure or priority uplink request procedure is successful, the mobile station shall give an indication to the upper layers and enter the group transmit mode. + +If the uplink access procedure or priority uplink request procedure is not successful, the mobile station shall give an indication to the upper layers and remain in group receive mode. + +### 3.4.15.2 Network side + +#### 3.4.15.2.1 Provision of messages on the VGCS or VBS channel downlink + +##### 3.4.15.2.1.1 General + +The network shall provide all messages directed to mobile stations in group receive mode (see sub-clause 3.4.15.1.2) in unacknowledged mode. Those messages which are also sent to the mobile station in group transmit mode in acknowledged mode have therefore to be repeated in addition as UI messages on the VGCS channel downlink if they shall also be received by mobile stations in group receive mode. + +When the VGCS/VBS call is ciphered the BSS shall derive the ciphering keys from the following parameters, as described in 3GPP TS 43.020: + +- Short term key as supplied at group call setup in the cell +- CELL\_GLOBAL\_COUNT +- Cell Global Identifier (CGI) + +The ciphering key needs to be recalculated whenever CELL\_GLOBAL\_COUNT changes. + +The ciphering algorithm is specified at resource assignment. + +##### 3.4.15.2.1.2 Provision of general information messages + +In the case where the group call area exceeds one cell, the network should provide the SYSTEM INFORMATION TYPE 6 message on the SACCH related to the voice broadcast channel or voice group call channel. + +In addition, if the group call area exceeds one cell, the network should provide SYSTEM INFORMATION TYPE 5 (possibly together with TYPE 5bis and 5ter) on the SACCH related to the voice broadcast channel or voice group call channel. + +- The SYSTEM INFORMATION TYPE 5, TYPE 5bis and TYPE 5ter messages provide information on the BCCH frequency of the neighbour cells. +- The SYSTEM INFORMATION TYPE 6 message provides information on the location area of the current cell, possibly the status of the NCH (see conditions in sub-clause 3.3.3), and an indication of whether paging channel restructuring has taken place, and an indication of the AMR codec configuration if AMR is being used on the VGCS/VBS group channel. +- \$(ASCII)\$ The SYSTEM INFORMATION TYPE 10 message provides information for cell re-selection in group receive mode. + +The network may also provide layer 3 messages for notification on the VGCS or VBS channel downlink FACCH. + +The network may in addition provide SYSTEM INFORMATION TYPE 10bis messages on the SACCH of a voice group call channel to describe the location of the group call channel in neighbour cells. In such a case, if the description of the group call channel for a neighbour cell (including frequency parameters) does not fit in a SYSTEM INFORMATION TYPE 10bis message, the network shall send in addition a SYSTEM INFORMATION TYPE 10ter message for that neighbour cell. + +In case the information in a SYSTEM INFORMATION TYPE 10bis (or TYPE 10ter) becomes invalid, the network shall immediately send a VGCS Neighbour Cell Information message on the FACCH of the group call channel. This shall indicate which parameters are now invalid for which neighbour cells, and shall include as much replacement information as possible. + +A mobile station in group receive mode shall consider any information relating to a neighbour cell received in a SYSTEM INFORMATION TYPE 10bis (respectively TYPE 10ter) message with sequence number n or in a VGCS Neighbour Cell Information message with sequence number n as valid unless: + +- a VGCS Neighbour Cell Information message is received which explicitly indicates that the information for that cell is invalid, or +- any SYSTEM INFORMATION TYPE 10bis or TYPE 10ter message is received with sequence number $m$ (where $m = (n + 1) \bmod 4$ ) and a VGCS Neighbour Cell Information message has not been received which explicitly indicates that the information in the SYSTEM INFORMATION TYPE 10bis (respectively TYPE 10ter) message with sequence number $n$ for that cell remains valid, or +- a SYSTEM INFORMATION TYPE 10bis (respectively TYPE 10ter) message is received containing information for that cell with sequence number $m$ (where $m > n \bmod 4$ ), or +- any SYSTEM INFORMATION TYPE 10bis or TYPE 10ter message is received with sequence number $m$ (where $m > (n + 1) \bmod 4$ ). + +#### 3.4.15.2.1.3 Provision of messages related to the voice group call uplink channel + +Only applicable for the support of VGCS talking. + +The network shall provide UPLINK FREE messages on the main signalling link of all voice group call channels when the uplink is set free. The provision of UPLINK FREE messages shall be repeated as long as no uplink is granted to a mobile station. When talker priority is supported by the network, the UPLINK FREE message shall indicate the status of the emergency mode. + +The network shall provide an UPLINK BUSY message on the main signalling link of all voice group call when the uplink has been granted to a mobile station. When talker priority is supported by the network, the UPLINK BUSY message shall indicate the current talker priority and the status of the emergency mode. When validation of PRIORITY UPLINK REQUEST messages is required, the UPLINK BUSY message shall also include a token (see subclause 3.3.1.2.2b.2.4). + +When the network supports uplink access option (i), as defined in 3GPP TS 43.068, and performs a handover of the talking service subscriber the network shall immediately send an updated UPLINK BUSY message: + +- In the handover target cell when the BSS allocates the resources for a handover of the talking service subscriber to the voice group call channel in the target cell; +- In the handover target cell when BSS releases the resources allocated for the handover of the talking service subscriber to the voice group call channel in the target cell; +- In the handover source cell after reception of a HANDOVER SUCCEEDED message; +- In the current cell after the talking service subscriber has been switched within the cell from the group call channel to a dedicated channel or vice versa. + +The network may send UPLINK FREE messages containing an uplink access request on the main signalling channel of the VGCS channels in order to obtain knowledge on whether any listening mobile is present in a cell or not. If there is no UPLINK ACCESS message, responding to the uplink access request or for the uplink access procedure, received by the network, the network may decide to clear the VGCS channel in that cell. + +#### 3.4.15.2.1.4 Provision of messages related to the voice broadcast uplink channel + +The network may send UPLINK FREE messages containing an uplink access request on the main signalling channel of the VBS channels in order to obtain knowledge on whether any listening mobile is present in a cell or not. If there is no mobile station responding to the uplink access request, the network may decide to clear the VBS channel in that cell. + +### 3.4.15.2.2 Release of the VGCS or VBS Channels + +If a release request for a voice group call is received from the upper layer, the network, after having released the RR connection with the mobile station in group transmit mode, shall stop the notification procedures for that voice group call and clear all related voice group call channels. + +If a release request for a voice broadcast call is received from the upper layer, the network shall stop the notification procedures for that voice broadcast call and locally disconnect any channel related to the voice broadcast call. + +### 3.4.15.2.a VBS/VGCS reconfiguration procedure + +#### 3.4.15.2.a.1 Normal behaviour + +This procedure is used by the network to indicate a change in Group Channel Description, and if required, in the Cell Channel Description, at a given time for VBS and VGCS listeners in group receive mode and the VGCS talker in group transmit mode. The VBS/VGCS RECONFIGURE and VBS/VGCS RECONFIGURE2 messages are sent in unacknowledged mode (to mobile stations in group receive mode) or acknowledged mode (to mobile stations in group transmit mode) on the main DCCH of a VBS or VGCS channel. + +The network sends a VBS/VGCS RECONFIGURE message containing the new group channel description together with a starting time indication. If the Cell Channel Description is to be changed then the Additional Segment field in the VBS/VGCS RECONFIGURE message shall indicate that the VBS/VGCS RECONFIGURE2 message is to follow. If the Cell Channel Description is unchanged then the Additional Segment field is set to '0' and no VBS/VGCS RECONFIGURE2 message is sent. The VBS/VGCS RECONFIGURE2 message shall be sent on the main DCCH with the same starting time as indicated in the VBS/VGCS RECONFIGURE message. + +Optionally, the VBS/VGCS RECONFIGURE and VBS/VGCS RECONFIGURE2 messages may be resent multiple times before starting time on the main DCCH of a VBS or VGCS channel. + +On receiving the VBS/VGCS RECONFIGURE message with Additional Segment set to '0' the mobile station shall wait until starting time before applying the new physical channel configuration, frequencies and/or hopping sequences to the VBS or VGCS call that the mobile station is currently listening to. If the mobile station was in group transmit mode and received the message in an I frame, it shall then, in addition, re-establish the main signalling link by sending a SABM containing a Talker Indication message (see sub-clause 3.1.5). + +On receiving the VBS/VGCS RECONFIGURE message with Additional Segment set to '1' the mobile station shall wait to receive the VBS/VGCS RECONFIGURE2 message with the same starting and then wait until starting time to apply the new physical channel configuration, frequencies and/or hopping sequences using the new Cell Channel Description to the VBS or VGCS call that the mobile station is currently listening to. If the mobile station was in group transmit mode and received the message in an I frame, it shall then, in addition, re-establish the main signalling link by sending a SABM containing a Talker Indication message (see sub-clause 3.1.5). + +On receiving only the VBS/VGCS RECONFIGURE2 message the mobile station shall wait to receive the VBS/VGCS RECONFIGURE message with the same starting time and then wait until starting time to apply the new physical channel configuration, frequencies and/or hopping sequences using the new Cell Channel Description to the VBS or VGCS call that the mobile station is currently listening to. If the mobile station was in group transmit mode and received the message in an I frame, it shall then, in addition, re-establish the main signalling link by sending a SABM containing a Talker Indication message (see sub-clause 3.1.5). + +If the Starting Time in the VBS/VGCS RECONFIGURE message indicates a time that has elapsed with Additional Segment set to '0', then the mobile station shall switch to the new Group Channel Description immediately. + +NOTE: The network implementation should take into account the possible presence of mobiles which do not recognize the VGCS/VBS RECONFIGURE or VBS/VGCS RECONFIGURE2 messages. An appropriate message (e.g. Channel Release) should be sent to indicate to such mobiles that the current group call channel is no longer in use. Such mobiles must determine the new location of the group channel by reading the NCH. + +#### 3.4.15.2.a.2 Abnormal cases + +If the starting time in the VBS/VGCS RECONFIGURE has elapsed with Additional Segment set to '1' and the mobile has not received the VBS/VGCS RECONFIGURE2 message, then the mobile station shall locally abort the radio connection and search all possible channel positions on the current cell and the neighbour cells for which a channel description is known for that call. + +If the starting time in the VBS/VGCS RECONFIGURE2 message has elapsed and the mobile has not received the VBS/VGCS RECONFIGURE message, then the mobile station shall locally abort the radio connection and search all possible channel positions on the current cell and the neighbour cells for which a channel description is known for that call. + +If the starting times in the received set of VBS/VGCS RECONFIGURE and VBS/VGCS RECONFIGURE2 messages are different then the mobile station shall ignore both of the messages. + +### 3.4.15.3 Failure cases + +If the mobile station loses the voice group call channel or voice broadcast channel, the mobile station shall search all possible channel positions on the current cell and the neighbour cells for which a channel description is known for that call. + +#### 3.4.15.3a Additional Information procedure + +In group receive mode, the network sends the talker's details on the main DCCH in either a VGCS ADDITIONAL INFORMATION or an UPLINK BUSY message. The VGCS ADDITIONAL INFORMATION message is sent in unacknowledged mode on the main DCCH of the voice group channel. In addition the transmission of the VGCS ADDITIONAL INFORMATION message is repeated every T3153 seconds on the SACCH, until the talker is released. + +The MS shall pass the information to the upper layers. + +#### 3.4.15.3b SMS to on going group call procedure + +The network may send VGCS mobile stations that are in group receive mode or group transmit mode a short message by sending it one or more RP-Data messages (see 3GPP TS 24.011). An RP-Data message is sent to the mobile stations by using one or more instances of the VGCS SMS Information message. Each VGCS SMS Information message contains an SMS reference number that identifies a particular RP-Data message. The VGCS SMS Information message is sent in unacknowledged mode on the SACCH of the group channel to the VGCS mobile stations that are in group receive mode and any VGCS talking subscriber that is using the uplink of the group channel. When the talker is on a dedicated channel the VGCS SMS Information message is sent in unacknowledged mode on the SACCH of this channel. The network may retransmit an SMS Information message for a period of up to 30s (including the initial transmission). + +The network shall insert an SMS reference number in the VGCS SMS Information message to identify the particular RP-Data message. In the case that the RP-Data message has to be segmented over multiple VGCS SMS Information messages, the network shall insert a segment number in each message segment to identify the segment. The first segment shall contain a segment number of zero, with the segment number incremented by one in each subsequent segment. + +The VGCS mobile station shall start an instance of T3112 for the RP-Data message when it first receives a segment of the message. The instance of timer T3112 relating to the message shall be stopped when: + +- the MS receives the complete RP-Data message; +- the MS receives a VGCS SMS Information message with an SMS reference number which is more than 4 higher (modulo 16) than that of this message; +- the MS changes its channel; +- the voice group call is cleared. + +If T3112 is stopped and the RP-Data message has not been completely received, the VGCS mobile station shall discard the segments of the RP-Data message. + +The VGCS mobile station shall (as far as possible) pass correctly received RP-Data messages to the upper layers in order of increasing SMS reference number. The MS shall store the parameter V(G) which is the SMS reference number of the message which is to be delivered next to the upper layer. The MS initialises the value of V(G) to the value in the first received segment on the current channel. + +If an RP-Data message is completely received which has an SMS reference number equal to V(G) it is passed to the upper layer, and V(G) is incremented by one (mod 16). + +If an RP-Data message is completely received which has an SMS reference number which is not equal to V(G) then the MS shall start timer T3114 for that message. Timer T3114 is stopped when the message is passed to the upper layer. + +On expiry of the timer T3114 for a message, each message (or any segments thereof) which has a sequence number between V(G) (inclusive) and the SMS reference number of the message for which timer T3114 expired (inclusive) shall be: + +discarded and the corresponding timer T3112 stopped, if the message has not been completely received, or + +passed to the upper layers in order, and the corresponding timer T3114 stopped, if it has been completely received. + +V(G) shall then be set to the SMS reference number of the message for which timer T3114 expired plus one modulo 16. + +All messages for which T3114 is running shall be passed to the upper layers, in order of increasing SMS reference number and the corresponding instances of timer T3114 stopped, if: + +- the MS changes its channel, or +- the voice group call is cleared + +NOTE: The delivery of the RP-Data message to the group call is not guaranteed. No confirmation is sent of the receipt of the RP-Data message by the VGCS mobile station. + +### 3.4.16 Configuration change procedure + +This is only applicable for multislot configuration. This message shall not be used to change a non-multislot configured channel to a multislot configured channel. + +The configuration change procedure is used by the network to change the number of timeslots used in a multislot configuration. The procedure can also be used to change the channel mode of one or several channels and change their allocation. The main signalling link however, cannot be changed by the configuration change procedure. If a change of the main signalling link is needed, the assignment or handover procedures shall be used. + +The network shall not initiate a new configuration change procedure before a response to the previous CONFIGURATION CHANGE COMMAND message has been received from the mobile station. + +#### 3.4.16.1 Configuration change initiation + +The procedure starts when the network sends a CONFIGURATION CHANGE COMMAND to the mobile station on the main DCCH. The message indicates: + +- which timeslots to use in uplink; +- which timeslots to use in downlink; and +- which channel set each timeslot belongs to. + +The message may also contain definitions of the channel mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the CONFIGURATION CHANGE COMMAND a definition of the channel mode for the new channel set shall be included in the message. + +#### 3.4.16.2 Configuration change completion + +When the mobile station receives the CONFIGURATION CHANGE COMMAND it changes its configuration in accordance with the message contents and returns a CONFIGURATION CHANGE ACKNOWLEDGE on the same channel as the command message was received, confirming the new channel configuration. This applies irrespective of whether the new configuration is different from the one already in use by the mobile station or if it is the same. + +#### 3.4.16.3 Abnormal cases + +If the CONFIGURATION CHANGE COMMAND message instructs the mobile station to use a Channel Configuration or Mode(s) that it does not support, or if the channel mode to use is not defined for all channel sets, the mobile station shall return a CONFIGURATION CHANGE REJECT message with cause 'channel mode unacceptable', and the mobile station shall remain on the current channel(s) and use the old Channel Configuration and Channel Mode(s). + +### 3.4.17 Mapping of user data substreams onto timeslots in a multislot configuration + +For multislot configurations the following rules for mapping of the user data substreams onto timeslots shall apply for each channel set: + +- at initial assignment (using assignment procedure), the lowest numbered user data substream shall be mapped to the lowest numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n is the number of substreams); +- at channel changes using handover procedure or assignment procedure (where none of the timeslots are present in both the old and the new configuration), the lowest numbered user data substream shall be mapped to the lowest numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n is the number of substreams); +- at channel changes using assignment procedure (where at least one of the timeslots is the same in both the old and the new configuration) or configuration change procedure: + - user data substream(s) mapped to timeslot(s) that are present in both the old and the new configuration shall continue to be mapped to the same timeslot(s) as before the channel change; and + - possibly added timeslot(s) shall carry the lowest numbered available user data substream so that the lowest numbered data substream among the added is mapped to the lowest numbered added timeslot and so on in ascending order. + +NOTE: The user data substream number is a number that need not be the same as the inband number used for transparent services. The user data substream number is only used as a point of reference to a specific user data substream. + +### 3.4.18 Handling of classmark information at band change + +The coding of some fields in the *Mobile Station Classmark 1* and in the *Mobile Station Classmark 2* information elements depends on the band in use as described in sub-clause 10.5.1.5 and sub-clause 10.5.1.6. When a command to change the frequency band (GSM 900, DCS 1800) has been received (by, e.g., an IMMEDIATE ASSIGNMENT message, an ASSIGNMENT COMMAND message, a HANDOVER COMMAND message, a DTM HANDOVER COMMAND message or a FREQUENCY REDEFINITION message) the following applies: + +- When an IMMEDIATE ASSIGNMENT message is received, "the band used" for the purpose of coding the classmark information in the service request message, see sub-clause 3.1.5, shall be understood as the band used for the CHANNEL REQUEST message or (one of) the band(s) indicated by the IMMEDIATE ASSIGNMENT message. +- For other cases "the band used" for the purpose of coding the classmark information shall be understood as one of the bands used or attempted to be used within the 2 seconds preceding the passing of the layer 3 message containing the classmark information to the layer 2 send queue as described in 3GPP TS 44.006. + +NOTE: This definition means that when a band change is being done the network must take appropriate actions to handle possible ambiguities in the frequency band related information in the classmark. + +### 3.4.19 (void) + +### 3.4.20 (void) + +### 3.4.21 Application Procedures + +#### 3.4.21.1 General + +While in dedicated mode, the following applications associated with the Radio Resource management layer may be supported in the network and MS: + +#### 3.4.21.2 Location Services (LCS) + +Common procedures are defined in the Radio Resource management layer to assist these applications. + +#### 3.4.21.2A Earthquake and Tsunami Warning System (ETWS) + +Mobile station support for reception of ETWS Primary Notification message is optional. + +Common procedures are defined in the Radio Resource management layer to assist this application. + +### 3.4.21.3 Application Information Transfer + +The Application Information Transfer procedure enables an Application on the network side and a peer application in the MS to exchange Application Protocol Data Units (APDUs). + +#### 3.4.21.3.1 Normal Procedure without Segmentation + +The maximum size of an APPLICATION INFORMATION message is 251 octets as defined in 3GPP TS 44.006. Segmentation shall not be used when an APDU fits into a single APPLICATION INFORMATION message of maximum or smaller size. + +![Sequence diagram for Application Information Transfer without segmentation. It shows two messages between a Mobile Station and a Network. The first message is APPLICATION INFORMATION [APDU, C/R] from Network to Mobile Station. The second message is APPLICATION INFORMATION [APDU, C/R] from Mobile Station to Network.](034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg) + +``` + +Mobile Station Network + APPLICATION INFORMATION [APDU, C/R ] + <----- + APPLICATION INFORMATION [APDU, C/R] + -----> + +``` + +Sequence diagram for Application Information Transfer without segmentation. It shows two messages between a Mobile Station and a Network. The first message is APPLICATION INFORMATION [APDU, C/R] from Network to Mobile Station. The second message is APPLICATION INFORMATION [APDU, C/R] from Mobile Station to Network. + +**Figure 3.4.21.3.4.1: Application Information Transfer without segmentation** + +Either the network or MS may send an APPLICATION INFORMATION message once the MS is in dedicated mode. The APDU Data in the APPLICATION INFORMATION message shall contain a complete APDU according to the protocol in use. The APDU ID IE identifies the protocol and associated application. The APDU Flags IE indicates "First or Only Segment", "Last or Only Segment" and conveys a C/R flag transparently between the communicating applications. The C/R Flag may be used to distinguish a command from other messages and a final response from a non-final response. The use of the C/R flag is defined with respect to each application. If one or several APDUs are awaiting delivery to the data link layer in the MS and other layer 3 messages are ready to be sent on the uplink, the RR layer may allow these other layer 3 messages to be sent before the next pending APPLICATION INFORMATION message is delivered to the data link layer. On receiving an APPLICATION INFORMATION message, the receiving layer 3 entity shall deliver the message contents to the identified local application. + +#### 3.4.21.3.2 Normal Procedure with Segmentation + +Segmentation is only included for support of interoperability with Legacy (3GPP R4 and older) equipment when a segmented message is received from a Legacy node. + +Segmentation is applicable when an APDU is too large to fit into a single APPLICATION INFORMATION message. The procedure is applicable for either direction of transfer. + +![Sequence diagram for Application Information Transfer with segmentation. It shows three messages between a Mobile Station or Network and a Network or Mobile Station. The first message is APPLICATION INFORMATION [APDU segment, First Segment, not Last Segment] from Network or Mobile Station to Mobile Station or Network. The second message is APPLICATION INFORMATION [APDU segment, not First Segment, not Last Segment] from Network or Mobile Station to Mobile Station or Network. The third message is APPLICATION INFORMATION [APDU segment, not First Segment, Last Segment, C/R] from Network or Mobile Station to Mobile Station or Network.](5f1417c85a44ed9672c976606bcfeba8_img.jpg) + +``` + +Mobile Station or Network Network or Mobile Station + APPLICATION INFORMATION [APDU segment, First Segment, not Last Segment] + <----- + APPLICATION INFORMATION [APDU segment, not First Segment, not Last Segment] + <----- + APPLICATION INFORMATION [APDU segment, not First Segment, Last Segment, C/R] + <----- + +``` + +Sequence diagram for Application Information Transfer with segmentation. It shows three messages between a Mobile Station or Network and a Network or Mobile Station. The first message is APPLICATION INFORMATION [APDU segment, First Segment, not Last Segment] from Network or Mobile Station to Mobile Station or Network. The second message is APPLICATION INFORMATION [APDU segment, not First Segment, not Last Segment] from Network or Mobile Station to Mobile Station or Network. The third message is APPLICATION INFORMATION [APDU segment, not First Segment, Last Segment, C/R] from Network or Mobile Station to Mobile Station or Network. + +**Figure 3.4.21.3.2.1: Application Information Transfer with segmentation** + +The sending layer 3 entity shall segment an APDU by dividing it into one or more segments exactly fitting into maximum sized APPLICATION INFORMATION messages plus a final segment fitting into an APPLICATION INFORMATION message of maximum size or smaller. Once segmented, the resulting APPLICATION INFORMATION messages shall be transferred in sequence to the data link layer for transmission, without being interspersed by other level 3 messages. The first APPLICATION INFORMATION message in the sequence shall indicate "First Segment" and "Not Last Segment". Subsequent APPLICATION INFORMATION messages except for the last shall indicate "Not First Segment" and "Not Last Segment". The last APPLICATION INFORMATION message shall indicate "Not First Segment" and "Last Segment" and shall include a C/R flag as provided by the sending application. + +The receiving layer 3 entity shall reassemble any segmented APDU before transfer to the local application. The receiver may employ a timer to detect possible loss of APDU segments. If employed, the timer shall be started when the first APDU segment is received and cancelled after the last segment is received. + +### 3.4.21.3.3 Abnormal Cases + +APPLICATION INFORMATION messages are sent using "low" priority at the data link layer except for the case of ETWS, see sub-clause 3.1.6. This can lead to message loss or truncation when preempted by other "high" priority messages. A receiving layer 3 entity shall detect APDU truncation if an APPLICATION INFORMATION message is received carrying an APDU or APDU segment that is shorter than indicated by the length indicator for the APDU Data IE. This test is reliable because preemption in the data link layer guarantees that at least the first $2 \cdot N_{201}$ octets of any truncated message will be reliably transferred. + +An APPLICATION INFORMATION transfer error shall be detected due to any of the following: + +- a) Receipt of a truncated APDU or APDU segment; +- b) While performing APDU reassembly: + - receipt of any other layer 3 message defined to use SAPI 0 on the main DCCH; + - receipt of an APDU or APDU segment indicating "First or Only Segment"; + - expiration of the reassembly timer (if supported); +- c) While not performing APDU reassembly, receipt of an APDU segment indicating "not First or only segment"; +- d) Detection of any other error for a received message as defined in clause 8. + +If APDU reassembly was in process when the error occurred, the receiving layer 3 entity shall discard the partially reassembled APDU and reprocess any received APDU or APDU segment that caused the error provided not an error defined in clause 8. In all other cases, any received APDU or APDU segment shall be discarded. + +## 3.4.22 RR procedures related to packet resource establishment while in dedicated mode + +The establishment of a packet resource is supported by procedures on the main DCCH when the mobile station is in dedicated mode. The procedures are only applicable to a mobile station supporting both GPRS and DTM. The procedures are optional for the network. + +These procedures constitute a complement to the corresponding procedures for temporary block flow establishment using CCCH or PCCCH while in idle mode defined in 3GPP TS 44.018 and 3GPP TS 44.060, respectively. + +The packet request procedure is initiated by the MS and it is described in sub-clause 3.4.22.1. The packet notification procedure is initiated by the network and it is described in sub-clause 3.4.22.2. The packet downlink assignment is initiated by the network and it is described in sub-clause 3.4.22.3. + +### 3.4.22.1 Packet request procedure while in dedicated mode + +The packet request procedure using the main DCCH may be used to establish a packet resource to support the transfer of LLC PDUs in the direction from the mobile station to the network. + +#### 3.4.22.1.1 Entering the dual transfer mode + +While in dedicated mode, the establishment of an uplink packet resource may be initiated by the RR entity of the mobile station using the packet request procedure. The procedure is triggered by a request from upper layers to transfer an LLC PDU; see 3GPP TS 24.007. The request from upper layers specifies: + +- TLLI; +- radio priority; +- requested RLC mode associated with the packet transfer; +- LLC frame type; + +- establishment cause; +- QoS information for the requested packet session; and +- optionally, the PFI. + +Upon such a request, the RR entity of the mobile station: + +- if access to the network is allowed (sub-clause 3.4.22.1.1.1), it initiates the packet request procedure as defined in sub-clause 3.4.22.1.1.2; +- otherwise, it rejects the request. + +If the request from upper layers indicates any signalling procedure the acknowledged RLC mode shall be requested. + +If both the mobile station and the BSS support multiple TBF procedures, or if the mobile station supports RLC non-persistent mode, the BSS may order its preferred RLC mode when establishing uplink packet resources, independently of the RLC mode requested by the mobile station. In particular, if the mobile station supports RLC non-persistent mode the network may allocate an EGPRS TBF that uses this RLC mode. + +#### 3.4.22.1.1.1 Permission to access the network + +Access to the network is allowed if dual transfer mode is supported in the cell. + +NOTE: belonging to an authorised access class or special class, radio priority level and LSA permission are not considered since they only apply to a mobile station in idle mode. + +#### 3.4.22.1.1.2 Initiation of establishment of the packet request procedure + +The mobile station initiates the establishment of the packet resource by sending a DTM REQUEST message on the main DCCH. + +The DTM REQUEST message contains: + +- TLLI; +- Channel Request Description; +- Packet establishment cause which indicates, as applicable, a request to send user data, cell update, page response or a mobility management message; +- PFI, if the PFC procedures are supported by the MS and irrespective of the network support of PFC procedures; +- Multiple TBF Capability, irrespective of the network support of Multiple TBF procedures; +- RLC Non-persistent Mode Capability, irrespective of the network support of RLC Non-persistent Mode; and +- MS capabilities related to support of Reduced Latency or FANR, Uplink EGPRS2 and Downlink EGPRS2, irrespective of the network support of these features. + +Having sent the DTM REQUEST message, the mobile station starts timer T3148. + +#### 3.4.22.1.1.3 Answer from the network + +##### 3.4.22.1.1.3.1 Packet assignment + +On receipt of a DTM REQUEST message the network may allocate an uplink packet resource. The packet uplink resource is assigned to the mobile station in one of the DTM assignment messages: + +- DTM ASSIGNMENT COMMAND; or +- PACKET ASSIGNMENT. + +These messages are sent in acknowledged mode. The DTM ASSIGNMENT COMMAND message may be sent on the SDCCH and on the FACCH. The PACKET ASSIGNMENT message shall be sent only on FACCH. If frequency hopping is applied, the mobile station shall use the cell allocation defined for the cell to decode the mobile allocation. + +The allocation of the uplink packet resource may imply the reallocation of the resource for the RR connection. In this case, the DTM ASSIGNMENT COMMAND message is used and the timer T3107 is started on the network side. The DTM ASSIGNMENT COMMAND message shall not be used to change to a dependent configuration. The DTM ASSIGNMENT COMMAND message may be used to change the ciphering mode by including the Ciphering Mode Setting IE when a mobile station supports the reception of this IE in the DTM ASSIGNMENT COMMAND message. If Ciphering Mode Setting IE is not present the ciphering mode and the use of Selective Ciphering of Downlink SACCH (see sub-clause 3.4.7a) are unchanged after the mobile station has switched to the assigned channels. If the Ciphering Mode Setting IE indicates "start ciphering" the mobile station supporting Selective Ciphering of Downlink SACCH shall be able to decode both ciphered and not-ciphered SACCH blocks (see sub-clause 3.4.7a). The DTM ASSIGNMENT COMMAND message shall not contain a Cipher Mode Setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been transmitted earlier in the RR connection or ciphering has been started earlier in UTRAN. If such a DTM ASSIGNMENT COMMAND message is received it shall be regarded as erroneous, a DTM ASSIGNMENT FAILURE with cause "Protocol error unspecified" message shall be returned immediately, and no further action taken. + +When sending the DTM ASSIGNMENT COMMAND message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases is suspended until resumption is indicated. These RR messages can be deduced from sub-clauses 3.4.22.1 and 8.8 Radio Resource management. + +The PACKET ASSIGNMENT message is only used when the packet resource is a PDCH and no reallocation of the RR connection is needed. + +On receipt of: + +- DTM ASSIGNMENT COMMAND message; or +- PACKET ASSIGNMENT message; + +the mobile station shall stop T3148. + +If the received DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message includes uplink packet resources, the mobile station shall proceed with the packet access. If, in addition, the received DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message includes concurrent downlink packet resources, the mobile station shall also obey the packet downlink assignment. If the received message includes downlink packet resources and no uplink packet resources, the mobile station shall abort the packet access procedure and proceed with the procedure specified in sub-clause 3.4.22.3, and then attempt an establishment of uplink TBF, using the applicable procedure specified in 3GPP TS 44.060. + +If the network supports multiple TBF procedures, it shall indicate this support in the Multiple TBF Capability field in the *GPRS Cell Options* IE included in the DTM ASSIGNMENT COMMAND and the PACKET ASSIGNMENT messages. + +Upon receipt of the DTM ASSIGNMENT COMMAND message, the mobile station initiates a local end release of link layer connections, disconnects the physical channels, commands the switching to the assigned channel and initiates the establishment of lower layer connection (this includes the activation of the channel, their connection and the establishment of the main signalling link). + +If the channel mode to be applied corresponds to an initial assignment of a multi-rate speech codec, the DTM ASSIGNMENT COMMAND message shall contain the MultiRate Configuration IE, which defines the set of codec modes and related information to use on the new channel. + +If the assignment is related to an assignment from a multi-rate speech codec to a multi-rate speech codec, the MultiRate Configuration IE shall be included in the DTM ASSIGNMENT COMMAND message in the case of full rate to half rate change. If not included in this case, the mobile station shall behave as if the MultiRate Configuration IE was inconsistent. If not included in other cases, the MS shall use on the new channel the AMR configuration it was using on the old channel when it received the DTM ASSIGNMENT COMMAND message. + +#### 3.4.22.1.1.3.2 RR reallocation only + +If the mobile station receives an ASSIGNMENT COMMAND or HANDOVER COMMAND message during the packet access procedure, the mobile station shall abort the packet access procedure, stop timer T3148 and proceed with the channel assignment procedure as specified in sub-clause 3.4.3 or the handover procedure as specified in sub-clause 3.4.4. The mobile station shall then attempt an establishment of uplink TBF, using the procedure specified in sub-clause 3.4.22. + +If the mobile station receives a CHANNEL RELEASE message during the packet access procedure, the mobile station shall abort the packet access procedure, stop timer T3148 and proceed with the RR connection release procedure as specified in sub-clause 3.4.13. The mobile station shall then attempt an establishment of uplink TBF. + +If the mobile station receives an INTER SYSTEM TO UTRAN HANDOVER COMMAND message during the packet access procedure, the mobile station shall abort the packet access procedure, stop timer T3148 and proceed with the handover to UTRAN procedure as specified in sub-clause 3.4.4a. If a mobile station which is not UTRAN capable receives this message, the error handling as defined in sub-clause 8.4 applies. + +#### 3.4.22.1.1.3.3 Packet request rejection + +If the network cannot allocate the requested packet resource it may send the mobile station a DTM REJECT message in acknowledged mode on the main DCCH. This message contains a wait time ("wait indication" information element). + +On receipt of the DTM REJECT message, the mobile station stops T3148, notifies upper layers of a packet resource establishment failure and starts timer T3142 with the indicated value. + +The mobile station is not allowed to make a new attempt for packet access in the same cell until T3142 expires. The value of the wait indication (i.e. T3142) relates to the cell from which it was received. + +#### 3.4.22.1.1.4 Packet request completion + +The completion of the packet request procedure depends on the actual assignment message used by the network. + +- When the network sends a DTM ASSIGNMENT COMMAND message (i.e. reallocation of the CS resource is required), after the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE message, specifying cause "normal event", to the network on the main DCCH. The packet request procedure is completed for the mobile station when the ASSIGNMENT COMPLETE message is sent and for the network when it is received. The network then stops timer T3107. The sending of the ASSIGNMENT COMPLETE message on the mobile station side and its receipt on the network side allow the resumption of the transmission of signalling layer messages other than those belonging to RR management. +- When the network sends a PACKET ASSIGNMENT message, the packet request procedure is completed for the network when assignment message is sent and for the mobile station when it is received. + +When the packet request procedure is completed, the mobile station has entered the dual transfer mode. + +#### 3.4.22.1.1.5 Abnormal cases + +In the following cases, a resource establishment failure has occurred: + +- a) If a DTM ASSIGNMENT COMMAND message indicates resources in a non-supported frequency band. +- b) If the information available in the mobile station after the reception of a DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message does not satisfactorily define uplink packet resources or concurrent uplink and downlink packet resources if both were included in the message. +- c) If a DTM ASSIGNMENT COMMAND message includes a mobile allocation or a frequency list that indexes frequencies in more than one frequency band. +- d) If a DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message assigns resources not compliant with the multislot capabilities of the mobile station. +- e) If the mobile station has no current Cell Allocation (*Cell Channel Description*) and if it needs a Cell Allocation to analyse the DTM ASSIGNMENT COMMAND message or the PACKET ASSIGNMENT message. +- f) If the DTM ASSIGNMENT COMMAND message instructs the mobile station to use a channel description or mode that it does not support. + +- g) If the DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message does not include any uplink or downlink packet resources. +- h) At expiry of timer T3148. +- i) If the DTM ASSIGNMENT COMMAND message includes a Channel Mode IE indicating multi-rate speech codec but the Multi-Rate configuration IE is missing and no old multi-rate configuration exists. +- j) If the DTM ASSIGNMENT COMMAND message includes a Channel Mode IE indicating multi-rate speech codec and the possibly included Multi-Rate configuration IE is inconsistent. + +The MultiRate Configuration IE shall be considered as inconsistent by the mobile station if: + +- the active set does not include any codec mode or the active set includes more than four codec modes; or + - one or more codec modes of the active codec set are not supported by the assigned channel; or + - the threshold and hysteresis values are not set according to requirements given in 3GPP TS 45.009. +- k) If a PACKET ASSIGNMENT message is received on SDCCH. + - l) If the DTM ASSIGNMENT COMMAND message or PACKET ASSIGNMENT message includes the description of a SDCCH channel. + - m) If the DTM ASSIGNMENT COMMAND message includes a mode of ciphering not supported by the mobile station. + +In any of these cases, the mobile station shall remain in dedicated mode. In addition, if the mobile station has received a DTM ASSIGNMENT COMMAND, it shall return a DTM ASSIGNMENT FAILURE message on the main DCCH with one of the following corresponding cause values: + +- In case of abnormal cases a), c) above, "frequency not implemented"; +- In case of abnormal cases b), d), g), l), m) above, "protocol error unspecified"; +- In case of abnormal case e) above, "no cell allocation available"; +- In case of abnormal cases f), i), j) above, "channel mode unacceptable". + +Upper layers shall also be notified (resource establishment failure). + +In addition: + +- If the network commands the mobile station to reallocate the RR connection and the establishment of the main DCCH fails, all the allocated packet resources described in the new configuration are released; the mobile station shall revert to the old channel in dedicated mode, trigger the establishment of the main DCCH and send a DTM ASSIGNMENT FAILURE message on the main DCCH with cause value "lower layer failure". +- If a lower layer failure happens while attempting to connect back to the old channel, the radio link failure procedure is applied (see sub-clause 3.4.13.2). + +When receiving the DTM ASSIGNMENT FAILURE message, the network stops T3107. + +On the network side, if timer T3107 elapses before either the ASSIGNMENT COMPLETE message has been received on the new channel or a DTM ASSIGNMENT FAILURE message is received on the old channel; the old channel and the new channel are released. On the network side, lower layer failures occurring on the old channel after the sending of the DTM ASSIGNMENT COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM frame on the new main DCCH are treated following the general rules (cf. sub-clause 3.5.2). + +### 3.4.22.2 Packet notification procedure in dedicated mode + +The packet notification procedure is initiated by the RR entity of the network side. It is triggered by a page request from the GMM sublayer, see 3GPP TS 24.007. + +### 3.4.22.2.1 Packet notification initiation by the network + +The network initiates the packet notification procedure by sending the mobile station a PACKET NOTIFICATION message on the main DCCH. + +The network shall not send the PACKET NOTIFICATION message to a mobile station that does not support dual transfer mode operation. If a mobile station not supporting dual transfer mode receives this message, the error handling as defined in sub-clause 8.4 applies. + +### 3.4.22.2.2 Packet notification response + +Upon receipt of the PACKET NOTIFICATION message, the RR sublayer of the mobile station indicates the receipt of a packet paging request to the GMM sublayer; see 3GPP TS 24.007. + +### 3.4.22.3 Packet downlink assignment in dedicated mode + +The packet downlink assignment procedure in dedicated mode may be used to establish a packet resource to support the transfer of LLC PDUs in the direction from the network to the mobile station. + +This procedure is only applicable to a mobile station in dedicated mode and with no TBF allocated. If the mobile station already has an ongoing TBF, the establishment of the downlink packet resource is performed on the PACCH; see 3GPP TS 44.060. + +The establishment of a downlink packet resource is initiated by the RR entity on the network side using the packet downlink assignment procedure in dedicated mode. The procedure is triggered by a request from upper layers to transfer an LLC PDU; see 3GPP TS 24.007. The request from upper layers specifies a QoS profile, an *RLC mode*, *DRX parameters* and an *MS classmark* associated with the packet transfer. The BSS may order its preferred RLC mode independently of the RLC mode signalled from upper layers. If the mobile station supports RLC non-persistent mode the network may allocate an EGPRS TBF that uses this RLC mode. + +#### 3.4.22.3.1 Initiation of the packet downlink assignment procedure in dedicated mode + +The network initiates the packet downlink assignment procedure in dedicated mode by sending a DTM assignment message (i.e. DTM ASSIGNMENT COMMAND or a PACKET ASSIGNMENT) in acknowledged mode. The DTM ASSIGNMENT COMMAND message may be sent on the SDCCH and on the FACCH. The PACKET ASSIGNMENT message shall be sent only on FACCH. + +When sending the DTM ASSIGNMENT COMMAND message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases is suspended until resumption is indicated. These RR messages can be deduced from sub-clauses 3.4.22.3 and 8.8 Radio Resource management. + +The allocation of the downlink packet resource may imply the reallocation of the resource for the RR connection. In this case, the DTM ASSIGNMENT COMMAND message is used and the timer T3107 is started on the network side. The DTM ASSIGNMENT COMMAND message shall not be used to change to a dependent configuration. The DTM ASSIGNMENT COMMAND message may be used to change the ciphering mode by including the Ciphering Mode Setting IE when a mobile station supports the reception of this IE in the DTM ASSIGNMENT COMMAND message. The DTM ASSIGNMENT COMMAND message shall not contain a Cipher Mode Setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been transmitted earlier in the RR connection or ciphering has been started earlier in UTRAN. If such a DTM ASSIGNMENT COMMAND message is received it shall be regarded as erroneous, a DTM ASSIGNMENT FAILURE with cause "Protocol error unspecified" message shall be returned immediately, and no further action taken. + +The network shall not send any of the DTM assignment messages to a mobile station that does not support dual transfer mode operation. If a mobile station not supporting dual transfer mode receives any of these messages, the error handling as defined in sub-clause 8.4 applies. + +Upon receipt of the DTM ASSIGNMENT COMMAND message, the mobile station initiates a local end release of link layer connections, disconnects the physical channels, commands the switching to the assigned channel and initiates the establishment of lower layer connection (this includes the activation of the channel, their connection and the establishment of the main signalling link). + +If the channel mode to be applied corresponds to an initial assignment of a multi-rate speech codec, the DTM ASSIGNMENT COMMAND message shall contain the MultiRate Configuration IE, which defines the set of codec modes and related information to use on the new channel. + +If the assignment is related to an assignment from a multi-rate speech codec to a multi-rate speech codec, the MultiRate Configuration IE shall be included in the DTM ASSIGNMENT COMMAND message in the case of full rate to half rate change. If not included in this case, the mobile station shall behave as if the MultiRate Configuration IE was inconsistent. If not included in other cases, the MS shall use on the new channel the AMR configuration it was using on the old channel when it received the DTM ASSIGNMENT COMMAND message. + +### 3.4.22.3.2 Packet downlink assignment completion + +The completion of the packet downlink assignment procedure while in dedicated mode depends on the actual assignment message used by the network: + +- when the network sends a DTM ASSIGNMENT COMMAND message (i.e. reallocation of the RR connection is required), after the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE message, specifying cause "normal event", to the network on the main DCCH. The packet downlink assignment procedure is completed for the mobile station when the ASSIGNMENT COMPLETE message is sent and for the network when it is received. The network then stops timer T3107. The sending of the ASSIGNMENT COMPLETE message on the mobile station side and its receipt on the network side allow the resumption of the transmission of signalling layer messages other than those belonging to RR management. +- when the network sends a PACKET ASSIGNMENT message, the packet downlink assignment procedure is completed for the network when assignment message is sent and for the mobile station when it is received. + +### 3.4.22.3.3 Abnormal cases + +In the following cases, a resource establishment failure has occurred: + +- a) If a DTM ASSIGNMENT COMMAND message indicates packet resources in a non-supported frequency band. +- b) If the information available in the mobile station after the reception of a DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message does not satisfactorily define downlink packet resources. +- c) If a DTM ASSIGNMENT COMMAND message includes a mobile allocation or a frequency list that indexes frequencies in more than one frequency band. +- d) If a DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message assigns resources not compliant with the multislot capabilities of the mobile station. +- e) If the mobile station has no current CA and if it needs a CA to analyse the DTM ASSIGNMENT COMMAND message. +- f) If the DTM ASSIGNMENT COMMAND message instructs the mobile station to use a channel description or mode that it does not support. +- g) If the DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message does not include any downlink packet resources, or if it includes uplink packet resources. +- h) If the DTM ASSIGNMENT COMMAND message includes a Channel Mode IE indicating multi-rate speech codec but the Multi-Rate configuration IE is missing and no old multi-rate configuration exists. +- i) If the DTM ASSIGNMENT COMMAND message includes a Channel Mode IE indicating multi-rate speech codec and the possibly included Multi-Rate configuration IE is inconsistent. + +The MultiRate Configuration IE shall be considered as inconsistent by the mobile station if: + +- the active set does not include any codec mode or the active set includes more than four codec modes; or + - one or more codec modes of the active codec set are not supported by the assigned channel; or + - the threshold and hysteresis values are not set according to requirements given in 3GPP TS 45.009. +- j) If a PACKET ASSIGNMENT message is received on SDCCH. + +- k) If the DTM ASSIGNMENT COMMAND message or PACKET ASSIGNMENT message includes the description of a SDCCH channel. +- l) If the DTM ASSIGNMENT COMMAND message includes a mode of ciphering not supported by the mobile station. + +In any of these cases, the mobile station shall remain in dedicated mode. + +If the mobile station has received a DTM ASSIGNMENT COMMAND message, it shall return a DTM ASSIGNMENT FAILURE message on the main DCCH with one of the following corresponding cause values: + +- In case of abnormal cases a), c) above, "frequency not implemented"; +- In case of abnormal cases b), d), g), k), l) above, "protocol error unspecified"; +- In case of abnormal case e) above, "no cell allocation available"; +- In case of abnormal case f), h), i) above, "channel mode unacceptable". + +In addition: + +- If the network commands the mobile station to reallocate the RR connection and the establishment of the main DCCH fails, all the allocated packet resources described in the new configuration are released; the mobile station shall revert to the old channel in dedicated mode, trigger the establishment of the main DCCH and send a DTM ASSIGNMENT FAILURE message on the old main DCCH with cause value "lower layer failure". +- If a lower layer failure happens while attempting to connect back to the old channel, the radio link failure procedure is applied (see sub-clause 3.4.13.2). + +When receiving the DTM ASSIGNMENT FAILURE message, the network stops T3107. + +On the network side, if timer T3107 elapses before either the ASSIGNMENT COMPLETE message has been received on the new channel or a DTM ASSIGNMENT FAILURE message is received on the old channel; the old channel and the new channel are released. + +On the network side, lower layer failures occurring on the old channel after the sending of the DTM ASSIGNMENT COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM frame on the new main DCCH are treated following the general rules (cf. sub-clause 3.5.2). + +### 3.4.22.4 Modification of packet resources while in DTM + +When the mobile station is in dual transfer mode, the network or mobile station may wish to modify only the allocated packet resources. When the mobile station has one or more ongoing TBFs, the procedures described in 3GPP TS 44.060 shall be used. + +## 3.4.23 RR procedures related to packet resource maintenance while in dual transfer mode + +### 3.4.23.1 General + +Once the mobile station enters the dual transfer mode, the existent procedures apply (see 3GPP TS 44.060). Some exceptions to the existent procedures while in dual transfer mode are: + +- When all packet resources have been released (or aborted), the mobile station returns to dedicated mode. +- When the mobile station is in dual transfer mode, it shall ignore any PACKET CELL CHANGE ORDER or PACKET ASSIGNMENT messages and shall remain in dual transfer mode. +- When the mobile station receives a HANDOVER COMMAND, HANDOVER TO UTRAN COMMAND, HANDOVER TO CDMA2000 COMMAND, HANDOVER TO IU MODE COMMAND or ASSIGNMENT COMMAND message, it shall abandon the packet resource immediately, enter dedicated mode and perform the handover or assignment procedure, respectively. +- When the mobile station receives a DTM ASSIGNMENT COMMAND message whilst in dual transfer mode, it shall follow procedures specified in sub-clause 3.4.23.2. + +- As stated in 3GPP TS 45.008, no GPRS measurement reporting is performed. + +In case the network has to change the frequency parameters and needs to specify a start time for the RR connection, the frequency redefinition procedure shall be used (see sub-clause 3.4.5) If the RR connection can be started immediately after resource reallocation with change of frequency parameters, the DTM ASSIGNMENT COMMAND message or the frequency redefinition procedure shall be used. + +In case the network has to change the channel mode of the traffic channel, the channel mode modify procedure shall be used (see sub-clause 3.4.6). + +The mobile station remains in dual transfer mode until the RR connection or all the packet resources are released. + +When the mobile station receives a DTM ASSIGNMENT COMMAND message encapsulated in a PACKET CS COMMAND message, it shall follow procedures specified in sub-clause 3.4.23.2.2 and 3.4.23.2.3 with the exceptions described in 3GPP TS 44.060. + +### 3.4.23.2 RR and packet resource reallocation whilst in dual transfer mode + +#### 3.4.23.2.1 General + +In dual transfer mode an intracell change of channel can be requested by upper layers for changing the channel type, or decided by the RR sublayer, e.g. for an internal handover or for the reallocation of all the resources of the mobile station. The purpose is to modify completely the physical channel configuration of the mobile station without change in synchronization while staying in the same cell. + +The mobile station and the network shall change neither the RLC mode nor TBF mode of an already established TBF during resource reallocation. The change of RLC mode or TBF mode shall be achieved through release of the TBF and establishment of a new TBF with the new RLC mode or TBF mode. + +The usage of the DTM ASSIGNMENT COMMAND message depends on whether the mobile station supports multiple TBF procedures, DTM enhancements or Downlink Dual Carrier: + +- If the mobile station does not support any of multiple TBF procedures, DTM enhancements or Downlink Dual Carrier, the DTM ASSIGNMENT COMMAND message is used by the network to reallocate the DTM resources assigned to a mobile station when the CS channel needs to be reallocated. All of the ongoing TBFs shall be addressed by the DTM ASSIGNMENT COMMAND message. The procedures in 3GPP TS 44.060 shall be used to establish an additional TBF or to release an ongoing TBF. +- If the mobile station supports multiple TBF procedures, DTM enhancements or Downlink Dual Carrier, the DTM ASSIGNMENT COMMAND message may be used by the network, when the CS channel needs to be reallocated, in order to reallocate the DTM resources assigned to a mobile station, to assign new uplink and downlink TBFs and to implicitly release TBFs. + +This procedure includes: + +- the suspension of normal operation except for RR management (layer 3); +- the release of the main signalling link and of the other data links as defined in sub-clause 3.1.4; +- the disconnection of TCHs and PDTCHs; +- the deactivation of previously assigned channels (layer 1); +- the activation of the new channels and their connection if applicable; +- the triggering of the establishment of the data link connections for SAPI = 0. + +#### 3.4.23.2.2 Normal resource reallocation case + +The reallocation of resources assigned to a mobile station is initiated by the network using a DTM ASSIGNMENT COMMAND message. Once the DTM ASSIGNMENT COMMAND message has been transmitted the timer T3107 is started on the network side. The DTM ASSIGNMENT COMMAND message may be used to change the ciphering mode by including the Ciphering Mode Setting IE when a mobile station supports the reception of this IE in the DTM ASSIGNMENT COMMAND message. The DTM ASSIGNMENT COMMAND message shall not contain a Cipher Mode Setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been + +transmitted earlier in the RR connection or ciphering has been started earlier in UTRAN. If such a DTM ASSIGNMENT COMMAND message is received it shall be regarded as erroneous, a DTM ASSIGNMENT FAILURE with cause "Protocol error unspecified" message shall be returned immediately, and no further action taken. + +Upon receipt of the DTM ASSIGNMENT COMMAND message, the mobile station initiates a local end release of link layer connections, disconnects the physical channels, commands the switching to the assigned channel and initiates the establishment of lower layer connection (this includes the activation of the channel, their connection and the establishment of the main signalling link). + +Upon receipt of the DTM ASSIGNMENT COMMAND message, the mobile station shall then switch to the assigned PDCHs and follow the applicable procedures specified in 3GPP TS 44.060. Neither the TLLI (in *A/Gb mode*) nor the G-RNTI (in *Iu mode*) shall be included in any of the uplink RLC data blocks in that case. If the mobile station supports multiple TBF procedures or DTM enhancements and the network addresses only a subset of the ongoing TBFs, the mobile station shall consider all ongoing TBFs not addressed by the DTM ASSIGNMENT COMMAND message as released. If while waiting for the frame number indicated by the TBF starting time the mobile station receives the DTM ASSIGNMENT COMMAND message, the mobile station shall act upon the most recently received uplink or downlink assignment and shall ignore the previous uplink or downlink assignment. + +After the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE message, specifying cause "normal event", to the network on the main DCCH. The reallocation of resources is completed for the mobile station when the ASSIGNMENT COMPLETE message is sent and for the network when it is received. The network then stops timer T3107. The sending of the ASSIGNMENT COMPLETE message on the mobile station side and its receipt on the network side allow the resumption of the transmission of signalling layer messages other than those belonging to RR management. + +If the mobile station has requested one or more new uplink TBFs (as specified in 3GPP TS 44.060) and a DTM ASSIGNMENT COMMAND message is received from the network before resources are allocated for the requested uplink TBFs, the mobile station shall: + +- follow the reallocation procedure as specified in this sub-clause; +- if the mobile station supports multiple TBF procedures or DTM enhancements it shall stop the instance of the RLC timer T3168 associated with the uplink TBF receiving a resource allocation (as specified in 3GPP TS 44.060); +- wait for the network response to the outstanding uplink TBF requests on the newly allocated resources. + +### 3.4.23.2.3 Abnormal cases + +In the following cases, a resource re-allocation failure has occurred : + +- a) If a DTM ASSIGNMENT COMMAND message indicates resources in a non-supported frequency band. +- b) If the information available in the mobile station after the reception of a DTM ASSIGNMENT COMMAND message does not satisfactorily define uplink packet resources if uplink packet resources were established or downlink packet resources if downlink packet resources were established. +- c) If a DTM ASSIGNMENT COMMAND message includes a mobile allocation or a frequency list that indexes frequencies in more than one frequency band. +- d) If a DTM ASSIGNMENT COMMAND message assigns resources not compliant with the multislot capabilities of the mobile station. +- e) If the mobile station has no current CA and if it needs a CA to analyse the DTM ASSIGNMENT COMMAND message. +- f) If the DTM ASSIGNMENT COMMAND message instructs the mobile station to use a channel description or mode that it does not support. +- g) If the DTM ASSIGNMENT COMMAND message does not include any uplink or downlink packet resources, except if encapsulated in a PACKET CS COMMAND message (as specified in 3GPP TS 44.060). +- h) If the DTM ASSIGNMENT COMMAND message includes a Channel Mode IE indicating multi-rate speech codec but the Multi-Rate configuration IE is missing and no old multi-rate configuration exists. + +- i) If the DTM ASSIGNMENT COMMAND message includes a Channel Mode IE indicating multi-rate speech codec and the possibly included Multi-Rate configuration IE is inconsistent. + +The MultiRate Configuration IE shall be considered as inconsistent by the mobile station if: + +- the active set does not include any codec mode or the active set includes more than four codec modes; or + - one or more codec modes of the active codec set are not supported by the assigned channel; or + - the threshold and hysteresis values are not set according to requirements given in 3GPP TS 45.009. +- j) If the DTM assignment command message, sent to a mobile station that does not support any of multiple TBF procedures, DTM enhancements or Downlink Dual Carrier, addresses more or fewer TBFs than the MS currently has been allocated. + +If the DTM assignment command message, sent to a mobile station that supports multiple TBF procedures, DTM enhancements or Downlink Dual Carrier, contains uplink assignments (including PFI values) for which no TBF was requested. + +- k) If the DTM ASSIGNMENT COMMAND message includes the description of a SDCCH channel. +- l) If the DTM ASSIGNMENT COMMAND message includes a mode of ciphering not supported by the mobile station. + +In any of these cases, the mobile station shall remain in DTM mode on the old configuration and return a DTM ASSIGNMENT FAILURE message on the current main DCCH with one of the following corresponding cause values: + +- In case of abnormal cases a), c) above, "frequency not implemented"; +- In case of abnormal cases b), d), g), k), j), l) above, "protocol error unspecified"; +- In case of abnormal case e) above, "no cell allocation available"; +- In case of abnormal cases f), h), i) above, "channel mode unacceptable". + +In addition: + +- If the establishment of the new main DCCH fails, all the allocated packet resources described in the new configuration in the DTM ASSIGNMENT COMMAND message are released; the mobile station shall revert to the old channel in dedicated mode, trigger the establishment of the main DCCH and send a DTM ASSIGNMENT FAILURE message on the main DCCH with cause value "lower layer failure" ; if an uplink TBF was active when the mobile station received the DTM ASSIGNMENT COMMAND message, the mobile station shall initiate the establishment of a new uplink TBF using the appropriate DTM procedure on the main DCCH, defined in sub-clause 3.4.22.1. +- If a lower layer failure happens on the circuit switched resource while attempting to connect back to the old channel, the radio link failure procedure is applied (see sub-clause 3.4.13.2). +- If a lower layer failure happens on re-allocated packet resources (such as T3180 or T3190 expiry ; see 3GPP TS 44.060) before the ASSIGNMENT COMPLETE message has been sent, all packet resources are released ; the mobile station shall revert to dedicated mode on the new channel ; if an uplink TBF was active when the mobile station received the DTM ASSIGNMENT COMMAND message, the mobile station shall initiate the establishment of a new uplink TBF using the appropriate DTM procedure on the main DCCH, defined in sub-clause 3.4.22.1 once the new main DCCH has been successfully established. + +When receiving the DTM ASSIGNMENT FAILURE message, the network stops T3107. + +On the network side, if timer T3107 elapses before either the ASSIGNMENT COMPLETE message has been received on the new channel or a DTM ASSIGNMENT FAILURE message is received on the old channel; the old channel and the new channel are released. + +On the network side, lower layer failures occurring on the old channel after the sending of the DTM ASSIGNMENT COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM frame on the new main DCCH are treated following the general rules (cf. sub-clause 3.5.2). + +### 3.4.24 RR procedures related to packet resource release while in dual transfer mode + +The release of a TBF shall follow the procedures in 3GPP TS 44.060. + +In the case of the release of the RR connection while in dual transfer mode, the mobile station may abandon the packet resources and, once in idle mode and packet idle mode, it may start a new establishment as described in 3GPP TS 44.060, or, if redirected to UTRAN according to the information element "Cell selection indicator after release of all TCH and SDCCH", as described in 3GPP TS 25.331, or, if redirected to E-UTRAN according to the information element "Cell selection indicator after release of all TCH and SDCCH", as described in 3GPP TS 36.331. + +If the network redirects a mobile station towards E-UTRAN, it proceeds as follows: + +- The network shall use the information element "Cell selection indicator after release of all TCH and SDCCH" in the channel release message for redirection towards an EARFCN in the E-UTRAN band numbered less than 65. +- The network shall use the information element "individual priorities" in the channel release message for redirection towards an EARFCN in the E-UTRAN band numbered greater than 64. + +If the mobile station and the network support the enhanced DTM CS release procedure, the network may delay the release of the RR connection until the mobile station has received the needed system information, in order to maintain the radio resources on the PDCH(s) after the release of the RR connection. + +### 3.4.25 GPRS suspension procedure + +#### 3.4.25.1 General + +This procedure enables the network to suspend GPRS services packet flow in the downlink direction. The support of this procedure is conditional to the support of GPRS by the mobile station. + +When a mobile station which is IMSI attached for GPRS services (see 3GPP TS 24.008) enters the dedicated mode, and when the mobile station limitations make it unable to handle both dedicated mode and either packet idle mode or packet transfer mode simultaneously, the mobile station shall perform the GPRS suspension procedure. + +The RR sublayer of the mobile station shall indicate a RR GPRS suspend condition to the MM sublayer, see 3GPP TS 24.008. + +#### 3.4.25.2 MS in class B mode of operation + +The GPRS suspension procedure shall be used to suspend GPRS services when the mobile station is in class B mode of operation and a circuit switched service is initiated. It is also used when a mobile station in CS/PS mode of operation in UTRAN reverts to class B mode of operation in GSM. + +The GPRS suspension procedure is initiated by the mobile station by sending a GPRS SUSPENSION REQUEST message with the appropriate suspension cause. This can be done as early as possible after access but shall be done after sending a CLASSMARK CHANGE message. + +#### 3.4.25.3 Dual transfer mode not supported + +The GPRS suspension procedure shall be used to suspend GPRS services: + +- a) when the mobile station in a class A mode of operation is handed over to a cell where the support of Class A mode of operation is not possible (e.g. a DTM mobile station entering a cell not supporting DTM); +- b) when the GPRS attached mobile station is in a cell that does not support DTM and a circuit switched service is initiated. + +In case a), when the mobile station concludes that DTM is not supported in the new cell after the handover procedure is completed, it shall initiate the GPRS suspension procedure by sending a GPRS SUSPENSION REQUEST message with the suspension cause set to "DTM not supported in the cell". + +In case b), the GPRS suspension procedure is initiated by the mobile station by sending a GPRS SUSPENSION REQUEST message with the suspension cause set to "DTM not supported in the cell". This can be done as early as possible after access but shall be done after sending a CLASSMARK CHANGE message. + +### 3.4.26 GPRS Transparent Transport Procedure + +While in dedicated mode, upper layers in the mobile station or in the network may request the transport of GPRS information transparently over the radio interface when DTM operation is supported by both the mobile station and the network. This procedure is only applicable when + +- the information from upper layers is signalling information; and +- the GTTP length of the message is below the maximum indicated by the network. + +On the mobile station side signalling is any LLC PDU carried on LLC SAPI 1. In any other case, the RR procedures related to packet resource establishment while in dedicated mode apply. + +The information from upper layers shall be carried inside the GTTP Information message. The GTTP Information message contains: + +- the TLLI of the MS; and +- the LLC PDU. + +If the mobile station supporting network sharing has received the PLMN Index (see sub-clause 3.4.4.1) in the HANDOVER COMMAND or DTM HANDOVER COMMAND message, it shall include it in the GTTP information message in the Skip Indicator (see sub-clause 10.3.1) if a foreign or random TLLI is used. + +If the indicated TLLI is not assigned to the mobile station, the mobile station shall ignore the received message. + +The GTTP messages are sent using "normal" priority at the data link layer. + +### 3.4.27 RR procedures related to dedicated mode MBMS notification + +#### 3.4.27.1 General + +The MBMS announcement of an mobile station is supported by procedures on the main DCCH when the mobile station is in dedicated mode. The procedures are only applicable to a mobile station supporting MBMS. The procedures are optional for the network. + +The packet request procedure is initiated by the MS and it is described in sub-clause 3.4.22.1. The packet notification procedure is initiated by the network and it is described in sub-clause 3.4.22.2. The packet downlink assignment is initiated by the network and it is described in sub-clause 3.4.22.3. + +#### 3.4.27.2 MBMS announcement procedure in dedicated mode + +##### 3.4.27.2.1 General + +The MBMS announcement procedure is initiated by the RR entity of the network side. It is triggered by the network being informed of a starting MBMS session or of an ongoing MBMS broadcast session with an updated MBMS service area list, see 3GPP TS 48.018. + +##### 3.4.27.2.2 MBMS announcement initiation by the network + +The network initiates the MBMS announcement procedure by sending the mobile station a MBMS ANNOUNCEMENT message on the main DCCH. + +The network shall not send the MBMS ANNOUNCEMENT message to a mobile station that does not support the MBMS service or to a mobile station that has not completed the Service Information Sending procedure. If a mobile station not supporting MBMS receives this message, the error handling as defined in sub-clause 8.4 applies. + +##### 3.4.27.2.3 MBMS notification response + +Upon receipt of the MBMS ANNOUNCEMENT message including the identity of an MBMS service to which the MBMS capable mobile station has not joined, the RR sublayer of the mobile station shall discard the MBMS ANNOUNCEMENT message. + +Upon receipt of the MBMS ANNOUNCEMENT message including the identity of an MBMS service to which the MBMS capable mobile station has joined and indicating a session that the mobile has not received, the RR sublayer of + +the mobile station indicates the receipt of a message, and passes the MBMS specific information contained within the MBMS ANNOUNCEMENT message, to the GMM sublayer. + +If the Restriction Timer IE is included in the received MBMS ANNOUNCEMENT message, the mobile station shall set and start an instance of T3222 to the value indicated in the Restriction Timer IE, otherwise if the Estimated Session Duration is included in the received MBMS ANNOUNCEMENT message the mobile station shall set and start both an instance of T3222 and the session duration timer for this MBMS session with a value equal to the Estimated Session Duration. The mobile station shall store the MBMS specific information contained in the MBMS ANNOUNCEMENT message. If T3222 expires the mobile station shall discard the stored MBMS information associated with this instance of T3222. + +If the mobile station in dedicated mode successfully completes the handover procedure, any MPRACH description or MBMS p-t-m channel description and MBMS Session Parameters List stored from a previously received MBMS ANNOUNCEMENT message shall be deleted. + +If the mobile station enters packet idle mode before the expiry of T3222 or where no instance of T3222 was set and the MBMS ANNOUNCEMENT message did not include the MBMS p-t-m channel description, the mobile station shall stop T3222, if started, and shall follow the MBMS Packet Access Procedure (3GPP TS 44.060). + +If the mobile station enters packet idle mode before the expiry of T3222 and the MBMS ANNOUNCEMENT message included the MBMS p-t-m channel description, the mobile station shall stop T3222 and shall start listening to downlink RLC blocks identified by the assigned TFI on the defined PDCHs either at the point in time denoted by the MBMS Radio Bearer Starting Time, if present and not already elapsed, or immediately otherwise (3GPP TS 44.060). + +NOTE: If the MBMS ANNOUNCEMENT message includes the MBMS p-t-m channel description, it shall also include the MBMS Session Parameters List (and vice versa). + +## 3.4.28 Transmission of application-specific data by the talker + +### 3.4.28.1 General + +This procedure is applicable only for the talker. + +The transmission of application-specific data by the talker is carried out by the mobile transmitting a DATA INDICATION message on the main signalling link. + +## 3.5 RR procedures on CCCH and EC-CCCH related to temporary block flow establishment + +### 3.5.0 General + +The establishment of a temporary block flow (TBF) on a packet data physical channel is supported by procedures on CCCH when PCCCH is not provided in the cell or on EC-CCCH when the cell supports EC-GSM-IoT and the mobile station has enabled EC operation. The procedures for temporary block flow establishment using CCCH are only applicable to a mobile station supporting GPRS. The procedures are optional for the network. + +These procedures constitute a complement to the corresponding procedures for temporary block flow establishment using PCCCH, defined in 3GPP TS 44.060, and include the procedures using: + +- CCCH for packet paging for mobile stations that have not enabled EC operation (sub-clause 3.5.1), +- EC-CCCH for packet paging for mobile stations that have enabled EC operation (sub-clause 3.5.1a), +- CCCH for packet access for mobile stations that have not enabled EC operation, (sub-clause 3.5.2), +- EC-CCCH for packet access for mobile stations that have enabled EC operation (sub-clause 3.5.2a), +- CCCH for packet downlink assignment for mobile stations that have not enabled EC operation (sub-clause 3.5.3), +- EC-CCCH for packet downlink assignment for mobile stations that have enabled EC operation (sub-clause 3.5.5), and +- CCCH for MBMS packet access (sub-clause 3.5.4). + +At any point in time a mobile station may enable one of PEO or EC operation. Support for GPRS services using GPRS TBFs or EGPRS TBFs is mandatory for a PEO capable mobile station and is optional for an EC capable mobile station. + +### 3.5.1 Packet paging procedure using CCCH + +The network can initiate the packet paging procedure in order to cause upper layers in the mobile station to respond, see clause 4. The packet paging procedure can only be initiated by the network. + +#### 3.5.1.1 Packet paging initiation by the network + +The packet paging procedure is initiated by the RR entity of the network side. It is triggered by a page request from the MM sublayer, see 3GPP TS 24.007, or by an MBMS session start procedure or by an MBMS session update procedure in case of an MBMS notification, see 3GPP TS 48.018. + +The network initiates the paging procedure by sending a paging request message on an appropriate paging subchannel on CCCH or PCCCH. Paging initiation using a paging subchannel on CCCH is used when sending paging information to a mobile station and PCCCH is not present in the cell. + +NOTE 1: There are three types of paging request messages that are applicable: + +- PAGING REQUEST TYPE 1; +- PAGING REQUEST TYPE 2; and +- PAGING REQUEST TYPE 3. + +In a PAGING REQUEST message used for the packet paging procedure, the mobile station shall be identified by the P-TMSI (GPRS TMSI) or its IMSI. If the mobile station is identified by the P-TMSI, it shall proceed as specified in sub-clause 3.5.1.2. + +In a paging request message used for MBMS notification, the MBMS session shall be identified by the TMGI and, if available, the MBMS Session Identity of that session, see sub-clause 3.5.1.3. + +If the mobile station identified by its IMSI, it shall parse the message for a corresponding *Packet Page Indication* field: + +- if the *Packet Page Indication* field indicates a paging procedure for RR connection establishment, or the field is not present in the message, the mobile station shall proceed as specified in sub-clause 3.3.2.2; +- if the *Packet Page Indication* field indicates a packet paging procedure, the mobile station shall proceed as specified in sub-clause 3.5.1.2. + +A PAGING REQUEST message may include more than one mobile station identification. + +The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannels on CCCH corresponding to the paging groups determined for it in packet idle mode, as specified in 3GPP TS 45.002. These messages contain a page mode information element. + +NOTE 2: The possible immediate assignment messages are: the IMMEDIATE ASSIGNMENT, the IMMEDIATE ASSIGNMENT EXTENDED, the IMMEDIATE PACKET ASSIGNMENT if supported and the IMMEDIATE ASSIGNMENT REJECT messages. + +The treatment of page mode information, including the procedure when the mobile station selects a new PCH, and the procedure if a message in a paging subchannel is not received correctly are defined in sub-clause 3.3.2.1.1. + +A PEO capable mobile station may negotiate the use of eDRX or PSM: + +- If it successfully negotiates eDRX (enables eDRX) for paging based reachability it shall consider eDRX to be supported in all cells in the corresponding Routing Area (i.e. eDRX is negotiated at the Routing Area level). +- If it successfully negotiates PSM (with or without eDRX) it shall consider PSM to be supported in all cells in the corresponding Routing Area. + +A PEO capable mobile station that has enabled eDRX wakes up to read a nominal paging group according to its negotiated eDRX as long as it remains in the same Routing Area it was in when it performed NAS signalling to enable eDRX regardless of whether or not PEO is enabled (see sub-clause 3.9.1). + +An MS that has enabled PEO and is using eDRX shall ignore the "Paging reorganization" condition indicated by the page mode information element if received in any message (i.e. this condition targets mobile stations not using eDRX). + +If PEO is enabled by a mobile station, after reading the message sent within its nominal paging group it shall use the RCC field in the message and the 6 bit BSIC field in the most recently read SCH to establish a BSIC (see 3GPP TS 45.008). If the BSIC does not match the BSIC value decoded upon first entering the serving cell (see 3GPP TS 45.008) or if the RCC and PEO\_BCCH\_CHANGE\_MARK fields are not included in the message it shall consider PEO as disabled, abort the packet paging procedure and attempt cell re-selection. + +### 3.5.1.2 On receipt of a packet paging request + +On the receipt of a paging request message, the RR sublayer of addressed mobile station indicates the receipt of a paging request to the MM sublayer, see 3GPP TS 24.007. + +An exception case is when a mobile station that has enabled PEO or EC operation and supports the MTA procedure or the MOTD procedure receives a paging request message that indicates a positioning event is pending (see sub-clauses 10.5.2.23, 10.5.2.24 and 10.5.2.25 for PEO and sub-clause 9.1.63 for EC operation). When this occurs the mobile station may perform a cell re-selection (see 3GPP TS 45.008 [34]) after which the RR sublayer of addressed mobile station indicates the receipt of a paging request to the MM sublayer, see 3GPP TS 24.007 [20]. + +Another exception case is when an EC-GSM-IoT capable mobile station, that has previously received an indication for restricted use of enhanced coverage (see 3GPP TS 24.008 [79]), receives a paging request message in (E)GPRS operation, while camping on a non-EC-GSM-IoT supporting cell, or in EC operation, while camping on an EC-GSM-IoT supporting cell, that indicates that the restricted use of enhanced coverage is removed. When this occurs, the mobile station may perform a cell re-selection (see 3GPP TS 45.008 [34]) after which the RR sublayer of addressed mobile station indicates the receipt of a paging request to the MM sublayer, see 3GPP TS 24.007 [20]. + +### 3.5.1.3 Packet Paging for MBMS notification on CCCH + +#### 3.5.1.3.1 General + +The packet paging procedure for MBMS notification is initiated by the network upon receipt of an MBMS-SESSION-START-REQUEST PDU or of an MBMS-SESSION-UPDATE-REQUEST PDU from the SGSN, see 3GPP TS 48.018. The MBMS notification may be repeated during the session. + +The packet paging procedure for MBMS notification consists of the following steps: + +- optionally, the pre-notification of the MBMS session; and +- the notification of the MBMS session. + +A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode if a paging procedure for a new MBMS session is not completed. + +The network initiates the paging procedure for MBMS notification of an MBMS session by sending a paging message including either an MBMS pre-notification or an MBMS notification for that session on one or more paging subchannels on CCCH. The paging request message may be of type: + +- PAGING REQUEST TYPE 1 message; or +- PAGING REQUEST TYPE 2 message. + +The MBMS session shall be identified by the TMGI and, if available, the MBMS Session Identity of that session as contained in the MBMS-SESSION-START-REQUEST PDU or in the MBMS-SESSION-UPDATE-REQUEST PDU received from the SGSN. + +The following requirements apply: + +- If in the paging message the mobile station is at the same time (pre-)notified (see sub-clauses 3.5.1.3.2 and 3.5.1.3.3) and paged, the mobile station shall discard all (pre-)notification(s) in that message and proceed as described in sub-clause 3.3.2 or 3.5.1.1 and 3.5.1.2 accordingly. +- If in the paging message the mobile station is at the same time pre-notified (see sub-clause 3.5.1.3.2) and notified (see sub-clause 3.5.1.3.3), the mobile station shall discard all pre-notifications in that message and proceed as described in sub-clause 3.5.1.3.3. + +### 3.5.1.3.2 MBMS pre-notification + +In order to pre-notify an MBMS session on a CCCH, the network shall send a relevant paging request message (see sub-clause 3.5.1.3.1) including the TMGI and, if available, the MBMS Session Identity of that session. The network shall not include the *MBMS Notification* information. + +Upon reception of a paging message including a pre-notification for an MBMS session, and if the mobile station requires reception of that session, the mobile station shall consider that session as being pre-notified (i.e. the mobile station is pre-notified). If the mobile station determines several pre-notified sessions in this message, the mobile station shall discard all pre-notifications but the pre-notification for the highest priority session. The mobile station in packet idle mode or MAC-Idle state shall then enter non-DRX mode, start timer T3220 and proceed as specified in sub-clause 3.5.1.3.3. + +NOTE: In case all pre-notified sessions have the same priority, the selection of the highest priority session is implementation-dependent. + +While timer T3220 is running, the mobile station shall stop timer T3220 and discard the pre-notification if: + +- Any other RR procedure on CCCH not related to MBMS is triggered. The mobile station shall then proceed as per that procedure. +- A notification is received for a higher priority session. The mobile station shall then proceed as described in sub-clause 3.5.1.3.3. + +If while timer T3220 is running the mobile station receives a pre-notification for a higher priority session, the mobile station shall discard the pre-notification for the lower priority session, remain in non-DRX mode, restart timer T3220 and proceed as specified in sub-clause 3.5.1.3.3. + +Upon expiry of timer T3220, the mobile station in packet idle mode or MAC-Idle state shall return to DRX mode and discard the pre-notification. The mobile station in broadcast/multicast receive mode shall discard the pre-notification and remain in broadcast/multicast receive mode. + +A mobile station in broadcast/multicast receive mode that is receiving an MBMS session shall ignore repeated pre-notifications of that session. + +### 3.5.1.3.3 MBMS notification + +In order to notify an MBMS session on CCCH, the network shall send a relevant paging request message (see sub-clause 3.5.1.3.1) including the following information: + +- the TMGI and, if available, the MBMS Session Identity of that session; +- an indication whether counting shall be performed or not; +- optionally the MBMS p-t-m channel description allocated to that session and the estimated duration of the MBMS session or, if the MBMS session is ongoing, the estimated remaining duration of the MBMS session; +- optionally the MPRACH description. + +NOTE 1: If the *MBMS Session Repetition Number* IE is included in the MBMS-SESSION-START-REQUEST PDU or in the MBMS-SESSION-UPDATE-REQUEST PDU (see 3GPP TS 48.018), the value part of this IE may be used by the network for e.g. deciding whether or not to perform the counting procedure or, in conjunction with the values of *Allocation/Retention Priority* IE (see 3GPP TS 48.018), whether or not to establish an MBMS radio bearer for the session. + +Upon reception of a paging message including the notification of an MBMS session and if the mobile station requires reception of this session, the mobile station shall consider that session as being notified (i.e. the mobile station is + +notified). If the mobile station determines several notified sessions in this message, the mobile station shall act upon the notification for the highest priority session. The mobile station shall then stop timer T3220, if running, and proceed as specified in sub-clause 3.5.1.3.4. + +NOTE 2: In case all notified sessions have the same priority, the selection of the highest priority session is implementation-dependent. + +NOTE 3: Depending on its capabilities, the MS may act upon the notification for lower priority MBMS sessions provided it does not affect any of the following procedures for the highest priority MBMS session: response to MBMS notification (see sub-clause 3.5.1.3.4), MBMS packet access procedure on CCCH (see sub-clause 3.5.4). + +A mobile station in broadcast/multicast receive mode that is receiving an MBMS session shall ignore repeated notifications of that session. + +### 3.5.1.3.4 Response to MBMS notification + +If the MBMS notification indicates that no counting shall be performed and contains no MBMS p-t-m channel description, the mobile station shall remain in or enter non-DRX mode and start timer T3214. The mobile station shall stop timer T3214 (specified in 3GPP TS 44.060) and proceed as specified in 3GPP TS 44.060 upon reception of an MBMS ASSIGNMENT message for that MBMS session. A mobile station in packet idle mode shall enter DRX mode upon expiry of T3214, and discard any corresponding notification. A mobile station in broadcast/multicast receive mode, i.e. engaged in one or more parallel MBMS session(s), shall remain in broadcast/multicast receive mode on expiry of T3214 and discard the corresponding notification. + +While timer T3214 is running, the mobile station shall stop timer T3214 if: + +- Any other RR procedure on CCCH not related to MBMS is triggered. The mobile station shall then proceed as per that procedure. +- A notification is received for a higher priority session. The mobile station shall then proceed as per that notification. Depending on its capabilities, the MS may act upon the notification for the lower priority MBMS session provided it does not affect any of the following procedures for the higher priority MBMS session: response to MBMS notification (see present sub-clause), MBMS packet access procedure on CCCH (see sub-clause 3.5.4). + +If the MBMS notification indicates that counting shall be performed the mobile station shall perform an MBMS packet access procedure as specified in the sub-clause 3.5.4. + +If the MBMS notification includes an MBMS p-t-m channel description, the mobile station shall set and start the session duration timer for this MBMS session with a value equal to the Estimated Session Duration (included in the MBMS Session Parameters List). If an MBMS Radio Bearer Starting Time parameter is not indicated or if the indicated starting time has elapsed, the mobile station shall switch to the assigned PDCH(s), start T3190 and listen for downlink RLC/MAC blocks for that session. If an MBMS Radio Bearer Starting Time parameter, that indicates a starting time that has not elapsed, is included, the mobile station shall wait until the point in time denoted by the MBMS Radio Bearer Starting Time parameter. It shall then switch to the assigned PDCHs, start timer T3190 and listen for downlink RLC/MAC blocks for that session. When receiving the first valid RLC/MAC block for that session, the mobile station shall restart timer T3190 and behave as described in 3GPP TS 44.060. + +Upon expiry of T3190, the mobile station shall abort the procedure and return to packet idle mode or MAC-Idle state. The mobile station in broadcast/multicast receive mode shall abort the procedure and remain in broadcast/multicast receive mode. + +### 3.5.1a Packet paging procedure using EC-CCCH + +The network can initiate the packet paging procedure in order to cause upper layers in a mobile station to respond, see clause 4. The packet paging procedure can only be initiated by the network (see subclause 3.5.1a.1 and sub-clauses 3.10.1 and 3.10.3). + +#### 3.5.1a.1 Packet paging initiation by the network + +The packet paging procedure is initiated by the RR entity of the network side. It is triggered by a page request from the MM sublayer, see 3GPP TS 24.007. + +The network initiates the paging procedure by sending an EC PAGING REQUEST message on an appropriate paging subchannel on EC-CCCH. Paging initiation using a paging subchannel on EC-CCCH is used when sending paging information to a mobile station that has enabled EC operation. + +The EC PAGING REQUEST message shall identify the mobile station by the P-TMSI (GPRS TMSI) or its IMSI and may include more than one mobile station identification. + +The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannels on EC-CCCH corresponding to the paging groups determined for it in packet idle mode, as specified in 3GPP TS 45.002. The messages sent on EC-CCCH may contain an EC Page Extension field. The DL coverage class included in the paging request message shall refer to the highest coverage class of all mobile stations being addressed in the paging request message. + +NOTE 1: The possible immediate assignment messages sent on EC-CCCH are the EC IMMEDIATE ASSIGNMENT TYPE 2, EC IMMEDIATE ASSIGNMENT TYPE 4, EC IMMEDIATE ASSIGNMENT REJECT and EC DOWNLINK ASSIGNMENT or EC DOWNLINK ASSIGNMENT TYPE 2 messages. + +A mobile station that has enabled EC operation and has successfully negotiated eDRX determines its nominal paging group as defined for EC operation (see 3GPP TS 45.002) according to its negotiated eDRX cycle and selected downlink coverage class. A mobile station that has enabled EC operation but has not negotiated eDRX determines its nominal paging group as defined for EC operation according to the lowest eDRX cycle, its IMSI and its selected downlink CC (see 3GPP TS 45.002). If it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, if it receives any other message on the EC-PCH and the EC Page Extension field is included therein it shall proceed as follows: + +- If the EC Page Extension field indicates paging extension is enabled for its downlink coverage class last communicated to the network (see 3GPP TS 45.008) it shall attempt to read one additional paging message using a paging group determined according to the downlink coverage class last communicated and the value of the Used DL Coverage Class field within the message where the EC Page Extension field was read as shown in Table 3.5.1a.1. +- If it finds a matching paging message therein it shall act on that message as described in sub-clause 3.5.1.2. +- If paging extension is not enabled or it does not find a matching paging message when attempting to read one additional paging message it sets its eDRX cycle to either the negotiated eDRX cycle (if eDRX has been negotiated) or the lowest eDRX cycle (if eDRX has not been negotiated), remains in packet idle mode and waits for the next instance of its nominal paging group. +- A mobile station that has enabled EC operation and has successfully negotiated eDRX shall, upon re-selecting to a cell in the same Routing Area that does not support EC operation, determine its nominal paging group as defined for PEO (see 3GPP TS 45.002 [32]) using its negotiated eDRX cycle length. + +**Table 3.5.1a.1: Page Extension Using Fixed Offset** + +| | | Used DL Coverage Class Indicated by Message Received on EC-PCH | | | | +|------------------------------------------------------------------|-----|-----------------------------------------------------------------------|---------------------|---------------------|-----------------------------------------| +| | | CC1 | CC2 | CC3 | CC4 | +| Last Communicated DL CC of MS Receiving Message on EC-PCH | CC1 | PG 1 + 2 | PG 1 + 4 | PG 1 + 8 | PG 1 + 8 | +| | CC2 | - | PG 1 + 4 | PG 1 + 4 | PG 1 + (2 or 6) 2 | +| | CC3 | - | - | PG 1 + 2 | PG 1 + (1 or 3) 3 | +| | CC4 | - | - | - | PG 1 + 2 | + +Note 1: PG (Paging Group) represents the start of the coverage class specific EC-PCH block corresponding to the nominal paging group of an MS (see 3GPP TS 45.002 [32]). The start of the coverage class specific EC-PCH block used for page extension is expressed as an offset relative to PG (where the value of the offset indicates the number of coverage class specific EC-PCH blocks comprising the offset). + +Note 2: Page Extension is determined using PG + 2 when a CC2 MS reading its nominal paging group in TDMA frames 35 to 42 (CC2 B2) or in TDMA frames 43 to 50 (CC2 B3) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 35 to 50 in MF N/N+1/N+2/N+3. Page Extension is determined using Paging Group PG + 6 when a CC2 MS reading its nominal paging group in TDMA frames 19 to 26 (CC2 B0) or in TDMA frames 27 to 34 (CC2 B1) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 19 to 34 in MF N/N+1/N+2/N+3. + +Note 3: Page Extension is determined using Paging Group PG + 1 when a CC3 MS reading its nominal paging group in TDMA frames 35 to 50 (CC3 B1) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 35 to 50 in MF N/N+1/N+2/N+3. Page Extension is determined using Paging Group PG + 3 when a CC3 MS reading its nominal paging group in TDMA frames 19 to 34 (CC3 B0) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 19 to 34 in MF N/N+1/N+2/N+3. + +A mobile station that has enabled EC operation where PSM is used wakes up to read its nominal paging group according to the lowest eDRX cycle (if PSM was negotiated without a corresponding eDRX value) or its negotiated eDRX cycle (if PSM was negotiated with a corresponding eDRX value) while the Active timer is running. It continues to monitor its nominal paging group while the Active timer is running and if it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, when the Active timer expires it stops monitoring its nominal paging group and remains in packet idle mode until its next uplink data transmission. + +The nominal paging group a mobile station monitors takes into account the selected downlink Coverage Class (see sub-clause 3.10.3, 3GPP TS 45.002 [32] and 3GPP TS 45.008 [34]) indicated during its most recent system access (e.g. transmission of an EC PACKET CHANNEL REQUEST message – see sub-clause 9.1.65) that resulted in the successful transmission of an uplink LLC PDU (e.g. a cell update). This downlink Coverage Class information is always provided to the BSS when it receives a PAGING-PS PDU from the SGSN. + +An EC capable MS whose last uplink transmission was in a cell that does not support EC-GSM-IoT may choose to enable EC operation upon reselection to a cell that supports EC-GSM-IoT. In this case it shall perform an uplink transmission (e.g. a cell update) to update the network (i.e. addition of Coverage Class information) and therefore be reachable for pages on the EC-PCH. + +If EC operation is enabled in the serving cell a MS that supports GPRS services using GPRS/EGPRS TBFs may choose to disable EC operation in which case it shall perform an uplink transmission (e.g. a cell update) to update the network (i.e. removal of Coverage Class information) and therefore be reachable for pages on the PCH. Similarly, if EC operation is enabled in the serving cell a MS that supports GPRS services using GPRS/EGPRS TBFs may reselect to a cell that supports both EC-GSM-IoT and GPRS/EGPRS TBFs and choose to disable EC operation, in which case it shall perform an uplink transmission (e.g. a cell update) to update the network (i.e. removal of Coverage Class information) and therefore be reachable for pages on the PCH. + +If EC operation is enabled in the serving cell a MS that performs reselection to a cell that does not support EC-GSM-IoT is not required to perform an uplink transmission (e.g. a cell update) to update the network in the new cell (i.e. the network retains Coverage Class information). An EC capable MS whose last uplink transmission was in a cell that does not support EC-GSM-IoT may choose to not enable EC operation upon reselection to a cell that supports EC-GSM-IoT in which case it is not required to perform an uplink transmission (e.g. a cell update) to update the network in the new cell. For both of these cases the MS is reachable for pages on the PCH as follows: + +- If it has not negotiated eDRX it shall listen to the PCH using DRX applicable to that cell (indicated by system information – see 3GPP TS 44.018). +- If it has negotiated eDRX it shall listen to the PCH using its negotiated eDRX cycle. + +- If it has negotiated PSM it shall listen to the PCH when the Active timer is running using DRX applicable to that cell (if PSM was negotiated without eDRX) or using the negotiated eDRX (if PSM was negotiated with eDRX.) +- When the MS monitors the PCH using the negotiated eDRX cycle it shall determine its nominal paging group as described in sub-clause 3.5.1 for the case of a PEO capable mobile station that has enabled eDRX. + +For the case where a mobile station is unable to read any message sent on EC-PCH or EC-AGCH when waking up according to its nominal paging group it returns to idle mode and waits for the next instance of its nominal paging group. + +### 3.5.2 Packet access procedure using CCCH + +The packet access procedure using CCCH may be used to establish a temporary block flow to support the transfer of LLC PDUs in the direction from the mobile station to the network. Establishment using one phase and two phase packet access, see 3GPP TS 44.060 [76], are supported. The two phase packet access is supported by means of the single block or multiple block packet access option in this procedure, allowing the transfer of a PACKET RESOURCE REQUEST and possibly an ADDITIONAL MS RADIO ACCESS CAPABILITIES message to the network. + +The single block packet access option in this procedure may also be used by a mobile station in packet idle mode to transfer an RLC/MAC control message other than the PACKET RESOURCE REQUEST message to the network, see sub-clause 3.5.2.2. + +The single block MBMS access option in this procedure shall be used by a mobile station in packet idle mode to transfer the RLC/MAC control message MBMS SERVICE REQUEST message network, see sub-clause 3.5.4. + +A MS that has enabled PEO (i.e. eDRX or PSM – see 3GPP TS 23.060 [74]) while in a cell that supports PEO, shall send an EGPRS PACKET CHANNEL REQUEST message with access type ‘PEO One Phase Access Request’ (see Table 3.5.2.1.2.2 and 3GPP TS 44.060 [76]) when attempting to establish a PS connection. An exception case is when the MS is accessing the network to perform the Multilateration Timing Advance (MTA) procedure (see sub-clause 3.11 and 3GPP TS 44.031) in a cell that supports MTA (see the MTA\_BITMAP field described in sub-clause 10.5.2.37b) in which case it sends an EGPRS MULTILATERATION REQUEST message specific to the MTA method it is using (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]). Another exception case is when the MS is accessing the network to send a Page Response due to receiving a page indicating ‘pending positioning event’ (see sub-clause 10.5.2.23, sub-clause 10.5.2.24 and sub-clause 10.5.2.25) in a cell that supports MTA in which case the MS sends an EGPRS MULTILATERATION REQUEST message indicating ‘Page Response for Positioning Event’ (see 3GPP TS 44.060 [76]). + +#### 3.5.2.1 Entering the packet transfer mode: packet access procedure + +The establishment of an uplink temporary block flow may be initiated by the RR entity of the mobile station using the packet access procedure. The procedure is triggered by a request from upper layers to transfer a LLC PDU, see 3GPP TS 24.007. The request from upper layers specifies *radio priority* and an *RLC mode* associated with the packet transfer or it indicates that the packet to be transferred contains signalling. + +Upon such a request, + +- if access to the network is allowed (sub-clause 3.5.2.1.1), the RR entity of the mobile station initiates the packet access procedure as defined in sub-clause 3.5.2.1.2; +- otherwise, it rejects the request. + +If the request from upper layers indicates signalling, the highest *radio priority* level shall be used at determination if access to the network is allowed, and the acknowledged RLC mode shall be requested. + +##### 3.5.2.1.1 Permission to access the network + +A mobile station configured for EAB and has enabled EAB (i.e. it has received EAB Authorization Mask and EAB Subcategory information for its selected PLMN from SYSTEM INFORMATION TYPE 21) shall, prior to proceeding with a mobile originated access attempt, re-read SI21 if more than 30 seconds have expired since the last time it read SI21. + +For a mobile originated access attempt, a mobile station configured for EAB and that has enabled EAB shall perform a preliminary access barring check (see sub-clause 3.3.1.4) unless it receives an indication from the upper layers to override EAB or it is attempting system access to perform the Multilateration Timing Advance (MTA) procedure (see + +sub-clause 3.11 and TS 3GPP 44.031) in which case access to the network is allowed. If the preliminary access barring check indicates network access is barred then access to the network is not allowed. Otherwise, the mobile station shall proceed according to the remainder of this sub-clause. + +Access to the network is allowed: + +- if the mobile station is a member of at least one authorized access class or special access class as defined in sub-clause 3.3.1.1.1; and +- if packet access is allowed in the cell for the radio priority level associated with the packet transfer, as indicated by the PRIORITY\_ACCESS\_THR parameter broadcast in SI 13 message; +- if the cell belongs to one of the allowed LSAs for the mobile station, as indicated on the SIM, in the case where the mobile station is a LSA only access subscriber. + +### 3.5.2.1.2 Initiation of the packet access procedure: channel request + +A mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008 [79]), when accessing the network to perform the packet access procedure, shall, while ignoring MS identities included within PAGING REQUEST messages, start listening to the downlink CCCH until successfully decoding one of the RR messages listed in sub-clause 3.3.1.1.1a. A MS that has enabled PEO shall read the PEO\_BCCH\_CHANGE\_MARK field and the RCC field within the successfully decoded RR message. It shall use the 6 bit BSIC from the most recently read SCH and the RCC field from the decoded RR message to establish a BSIC (see 3GPP TS 45.008). If the BSIC does not match the BSIC value decoded upon first entering the serving cell (see 3GPP TS 45.008) it shall abort the packet access procedure and attempt cell re-selection. If a change of PEO\_BCCH\_CHANGE\_MARK is detected it shall first read SI13 before proceeding with the packet access procedure. If the RR message indicates an implicit reject for the PS domain (see sub-clause 3.3.1.1.1a) the mobile station shall abort the packet access procedure and initiate the implicit reject procedure (see sub-clause 3.3.1.1.3.2a). An exception case is where the mobile station has enabled EC operation and is sending an EC PACKET CHANNEL REQUEST message using the RACH (the *RACH Access Control* field indicates that RACH usage on timeslot number 0 is allowed, see sub-clause 3.5.2a) in which case it proceeds with the packet access without first decoding one of the RR messages listed in sub-clause 3.3.1.1.1a and checking the status of the PEO\_BCCH\_CHANGE\_MARK field and implicit reject information sent therein. + +A MS that has enabled PEO accessing the network to perform packet access when the low priority indicator is set to "MS is not configured for NAS signalling low priority" shall also listen to the downlink CCCH until successfully decoding one of the RR messages listed in sub-clause 3.3.1.1.1a and read the PEO\_BCCH\_CHANGE\_MARK field and RCC field therein. It shall use the 6 bit BSIC from the most recently read SCH and the RCC field from the decoded RR message to establish a BSIC. If the BSIC does not match the BSIC value decoded upon first entering the serving cell (see 3GPP TS 45.008) or if the RCC and PEO\_BCCH\_CHANGE\_MARK fields are not included in the message it shall consider PEO as disabled, abort the packet access procedure and attempt cell re-selection. If a change of PEO\_BCCH\_CHANGE\_MARK is detected then it shall first read SI13 prior to performing the packet access. If it determines that the PEO\_DSC field is not included in the SI13 Rest Octets IE it shall consider PEO as disabled, abort the packet access procedure and attempt cell re-selection. + +The network indicates the RCC value corresponding to the serving cell within an IMMEDIATE ASSIGNMENT message using the *IA Rest Octets* IE (see sub-clause 10.5.2.16) or within an IMMEDIATE ASSIGNMENT REJECT message using the *IAR Rest Octets* IE (see sub-clause 10.5.2.17) or within an IMMEDIATE ASSIGNMENT EXTENDED message using the *IAX Rest Octets* IE (see sub-clause 10.5.2.18) or within an IMMEDIATE PACKET ASSIGNMENT message using the *IPA Rest Octets* IE (see sub-clause 10.5.2.78) or within a PAGING REQUEST TYPE 1 message using the *P1 Rest Octets* IE (see sub-clause 10.5.2.23) or within a PAGING REQUEST TYPE 2 message using the *P2 Rest Octets* IE (see sub-clause 10.5.2.24) or within a PAGING REQUEST TYPE 3 message using the *P3 Rest Octets* IE (see sub-clause 10.5.2.25). + +A mobile station that has enabled PEO shall, when attempting to establish a PS connection and while ignoring MS identities included within PAGING REQUEST messages, be able to successfully decode an RR message within 500ms of starting to listen to the downlink CCCH. Otherwise, the packet access procedure is aborted, a random access failure is indicated to upper layers and autonomous cell re-selection is performed according to 3GPP TS 43.022. + +If a MS that has enabled PEO does not detect a change in the PEO\_BCCH\_CHANGE\_MARK and the time elapsed since it last read SI13 exceeds 24 hours it should read SI13 before proceeding with the packet access procedure. + +A mobile station initiates the packet access procedure by leaving idle mode and scheduling the sending of CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST messages on RACH as described in sub-clause 3.3.1.1.2 (i.e. only the portion of sub-clause 3.3.1.1.2 describing message scheduling is used when the packet access procedure is initiated as described in this sub-clause). The cause to be used in the CHANNEL REQUEST message for a non-EGPRS TBF mode capable MS or an EGPRS TBF mode capable MS in a non-EGPRS capable cell depends on the purpose of the packet access procedure as follows: + +- If the purpose of the packet access procedure is to send user data and the requested RLC mode is unacknowledged mode, the mobile station shall request a single block packet access and attempt a two phase packet access. +- If the purpose of the packet access procedure is to send user data and the requested RLC mode is acknowledged mode, the mobile station shall request either a one phase packet access or a single block packet access. +- If the purpose of the packet access procedure is to send a Page Response, a Cell update (the mobile station was in GMM READY state before the cell reselection) or for any other GPRS Mobility Management or GPRS Session Management procedure, the mobile station shall request a one phase packet access. An exception case is when the purpose of the packet access procedure is to send a Page Response due to receiving a page indicating 'pending positioning event' (see sub-clause 10.5.2.23, sub-clause 10.5.2.24 and sub-clause 10.5.2.25), in which case the mobile station shall send an EGPRS MULTILATERATION REQUEST message indicating 'Page Response for Positioning Event' (see 3GPP TS 44.060 [76]). +- If the purpose of the packet access procedure is to send a Measurement Report, the mobile station shall request a single block packet access. +- If the purpose of the packet access procedure is to send a PACKET PAUSE message, the mobile station shall request a single block packet access. Upon sending the first CHANNEL REQUEST message the mobile station shall start timer T3204. If timer T3204 expires before an IMMEDIATE ASSIGNMENT message granting a single block period on an assigned packet uplink resource is received, the packet access procedure is aborted. If the mobile station receives an IMMEDIATE ASSIGNMENT message during the packet access procedure indicating a packet downlink assignment procedure, the mobile station shall ignore the message. +- If the purpose of the packet access procedure is to send an MBMS SERVICE REQUEST message to the network, the mobile station shall request a single block MBMS access. +- If the purpose of the packet access procedure is to send a signalling message and the mobile station is accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" it shall use the single block packet access option. + +A mobile station that has enabled PEO starts the radio access part of the MTA procedure upon receiving a RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031) if both the MS and the serving cell support the MTA procedure method indicated therein (see the MTA\_BITMAP field described in sub-clause 10.5.2.37b). In this case it starts the MPM timer and starts accessing the network using cells it has selected to perform the radio access part of the MTA procedure. For each selected cell it compares the BSIC of the CCCH to the BSIC. If the BSIC does not match it does not perform the radio access part of the MTA procedure using that cell. If the BSIC matches it does not check the status of the PEO\_BCCH\_CHANGE\_MARK field and implicit reject information sent for that cell, sends an EGPRS MULTILATERATION REQUEST message (see 3GPP TS 44.060 [76]) and proceeds as follows: + +- If the EGPRS MULTILATERATION REQUEST message indicates the RLC Data block method is used (see sub-clause 3.11 and 3GPP TS 44.060 [76]) it includes a random reference which is drawn randomly from a uniform probability distribution for every new transmission. After transmitting this message and receiving a matching IMMEDIATE ASSIGNMENT message (see sub-clause 9.1.18) or IMMEDIATE PACKET ASSIGNMENT message (see sub-clause 9.1.18b) it transmits a RLC data block containing MTA related parameters (see 3GPP TS 44.060 [76]) therein. After receiving a corresponding acknowledgement on the PACCH (see 3GPP TS 44.060 [76]) the MS tunes to the next cell in the list of applicable cells and continues the procedure therein. After performing the radio access part of the MTA procedure in all applicable cells or when the MPM timer expires it returns to idle mode in the cell it was in when the radio access part of the MTA procedure was triggered. +- If the EGPRS MULTILATERATION REQUEST message indicates the Access Burst method is used (see sub-clause 3.11 and 3GPP TS 44.060 [76]) it includes a Short ID parameter. After transmitting this message and + +receiving a matching IMMEDIATE ASSIGNMENT message (see sub-clause 9.1.18) or IMMEDIATE PACKET ASSIGNMENT message (see sub-clause 9.1.18b) it tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. After performing the radio access part of the MTA procedure in all applicable cells or when the MPM timer expires it returns to idle mode in the cell it was in when the radio access part of the MTA procedure was triggered. + +- If the Extended Access Burst method is used (see sub-clause 3.11) it sends a first EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst – part 1' and includes the "Random ID Low" and "MS Transmission Offset" parameters therein. After receiving a matching IMMEDIATE ASSIGNMENT message (see sub-clause 9.1.18) or IMMEDIATE PACKET ASSIGNMENT message (see sub-clause 9.1.18b) it sends a second EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst – part 2' and includes the "Random ID Low", the "MS Sync Accuracy", the "Random ID High" and the "Short BSS ID" parameters therein. After receiving a matching IMMEDIATE ASSIGNMENT message or IMMEDIATE PACKET ASSIGNMENT message for the second EGPRS MULTILATERATION REQUEST message it tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. After performing the radio access part of the MTA procedure in all applicable cells or when the MPM timer expires it returns to idle mode in the cell it was in when the radio access part of the MTA procedure was triggered. +- The MS shall not send an EGPRS PACKET CHANNEL REQUEST message with access type 'PEO One Phase Access Request' while performing the radio access part of the MTA procedure except for the case of a high priority transmission (i.e. 'PEO Priority' = 1, see 3GPP TS 44.060 [76]) in which case it shall stop the MPM timer and terminate the MTA procedure. When a BSS receives an uplink LLC PDU while the MPM timer is running for the corresponding MS it informs the SMLC that no additional timing advance information is pending for the corresponding MTA procedure (see 3GPP TS 49.031), stops the MPM timer and terminates the MTA procedure for that MS. + +EGPRS TBF mode capable mobile stations shall monitor the GPRS Cell Options IE on the BCCH (SI13) for the cell's EGPRS capability and, if the mobile station is also Reduced Latency capable, the cell's Reduced Latency Access capability. In the GPRS Cell Options IE it is also indicated if the EGPRS PACKET CHANNEL REQUEST message is supported in the cell and if Reduced Latency Access is supported in the cell. An exception case is where a MS has enabled PEO and is attempting to establish a PS connection in which case the EGPRS PACKET CHANNEL REQUEST message is sent regardless of whether or not the GPRS Cell Options IE indicates the EGPRS PACKET CHANNEL REQUEST message is supported in that cell. If the mobile station supports the IMMEDIATE PACKET ASSIGNMENT message, the mobile station shall monitor cell's capability for IMMEDIATE PACKET ASSIGNMENT message within paging messages received on its own paging sub-channel. Table 3.5.2.1.2.1 specifies which message and which establishment cause shall be used by an EGPRS mobile station when accessing an EGPRS capable cell depending on the purpose of the packet access procedure, and mobile station's and cell's capabilities for the case where the cell does not support PEO or EC operation; this table covers the case where PBCCH is not present in the cell (see 3GPP TS 44.060 for the case where PBCCH is present in the cell). Table 3.5.2.1.2.2 specifies which message and which establishment cause shall be used by a mobile station when PEO is enabled. Table 3.5.2.1.2.3 specifies which message and which establishment cause shall be used by a mobile station when EC operation is enabled and the *RACH Access Control* field (see sub-clause 9.1.30c) indicates the RACH is to be used by mobile stations that have selected coverage class 1 in both uplink and downlink. The network shall not indicate Reduced Latency Access is supported if the EGPRS PACKET CHANNEL REQUEST message is not indicated as supported. The network shall not indicate IMMEDIATE PACKET ASSIGNMENT message is supported if the EGPRS PACKET CHANNEL REQUEST message is not indicated as supported. + +**Table 3.5.2.1.2.1: EGPRS Packet Access Procedure (neither PEO nor EC operation enabled)** + +| Purpose of the packet access procedure | EGPRS PACKET CHANNEL REQUEST supported in the cell | EGPRS PACKET CHANNEL REQUEST not supported in the cell | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--|--| +| User data transfer - requested RLC mode = unacknowledged | EGPRS PACKET CHANNEL REQUEST with access type = 'Two Phase Access Request' | CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access | | | +| User data transfer - requested RLC mode = acknowledged | EGPRS PACKET CHANNEL REQUEST with access type = 'One Phase Access Request' or 'Two Phase Access Request' | CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access | | | +| User data transfer - requested RLC mode = acknowledged (Reduced Latency supported by MS) | EGPRS PACKET CHANNEL REQUEST with access type = 'One Phase Access Request by Reduced Latency MS' (NOTE 2) | CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access | | | +| User data transfer - requested RLC mode = acknowledged by an IPA capable mobile station | EGPRS PACKET CHANNEL REQUEST with access type = 'One Phase Access Request' or 'Two Phase Access Request by IPA capable MS' (NOTE 3) | CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access | | | +| Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc) | EGPRS PACKET CHANNEL REQUEST with access type = 'Signalling' | CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access | | | +| Upper layer signalling transfer for a mobile station when the low priority indicator is set to "MS is configured to NAS signalling low priority" (e.g. page response, cell update, MM signalling, etc) | EGPRS PACKET CHANNEL REQUEST with access type = 'Signalling' (NOTE 5) or 'Two Phase Access Request' (NOTE 6) | CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access | | | +| Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc) by an IPA capable mobile station | EGPRS PACKET CHANNEL REQUEST with access type = 'Signalling Request by IPA capable MS'(NOTE 4) | CHANNEL REQUEST with establishment cause = 'Single block packet access' for initiation of a two-phase access | | | +| Sending of a measurement report or of a PACKET CELL CHANGE FAILURE | CHANNEL REQUEST with establishment cause = 'Single block packet access' | | | | +| Sending of a PACKET PAUSE message | CHANNEL REQUEST with establishment cause = 'Single block packet access' (NOTE 1) | | | | +| Sending of an MBMS Service Request message | CHANNEL REQUEST with establishment cause = 'Single block MBMS access' | | | | +| NOTE 1: Upon sending the first CHANNEL REQUEST message the mobile station shall start timer T3204. If timer T3204 expires before an IMMEDIATE ASSIGNMENT message granting a single block period on an assigned packet uplink resource is received, the packet access procedure is aborted. If the mobile station receives an IMMEDIATE ASSIGNMENT message during the packet access procedure indicating a packet downlink assignment procedure, the mobile station shall ignore the message. | | | | | +| NOTE 2: The One phase Access Request by Reduced Latency MS shall be used by the mobile station supporting reduced latency if Reduced Latency Access is supported by the network. The 'One Phase Access Request by Reduced Latency MS' or 'Two Phase Access Request by IPA capable MS' may be used instead if the mobile station is capable of both Reduced Latency and IMMEDIATE PACKET ASSIGNMENT and the network supports IMMEDIATE PACKET ASSIGNMENT message and Reduced Latency Access. | | | | | +| NOTE 3: (This note does not apply if Note 2 is applicable) The 'One Phase Access Request' with IPA capability signalled by the MultislotClass field in the EGPRS PACKET CHANNEL REQUEST message or 'Two Phase Access Request by IPA capable MS' shall be used by the mobile station supporting IMMEDIATE PACKET ASSIGNMENT message if support of the IMMEDIATE PACKET ASSIGNMENT message is signalled by the network. | | | | | +| NOTE 4: The 'Signalling Request by IPA capable MS' shall be used if both mobile station and network supports IMMEDIATE PACKET ASSIGNMENT. | | | | | +| NOTE 5: The access type 'Signalling' shall be used unless the mobile station is accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008). | | | | | +| NOTE 6: The access type 'Two Phase Access Request' shall be used if the mobile station is accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008). | | | | | + +**Table 3.5.2.1.2.2: EGPRS Packet Access Procedure (PEO enabled)** + +| Purpose of the packet access procedure | PEO Capable Cell | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| User data transfer (requested RLC mode = acknowledged) or Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc) | EGPRS PACKET CHANNEL REQUEST with access type = 'PEO One Phase Access Request' (see TS 44.060 [76]) (NOTE 1) | +| Transmission of a EGPRS MULTILATERATION REQUEST message indicating 'RLC Data Block' method or 'Page Response for Positioning Event' or 'Extended Access Burst' method or 'Access Burst' method. | EGPRS MULTILATERATION REQUEST see TS 44.060 [76]) (NOTE 1) | +| NOTE 1: A PEO capable MS in a cell that does not support PEO shall operate according to Table 3.5.2.1.2.1. | | + +**Table 3.5.2.1.2.3: EGPRS Packet Access Procedure (EC operation enabled – RACH used)** + +| Purpose of the packet access procedure | EC-GSM-IoT Capable Cell | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| +| User data transfer (requested RLC mode = acknowledged) or Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc) | EC PACKET CHANNEL REQUEST sent using TS3 - see sub-clause 9.1.65 (NOTE 1) | +| NOTE 1: An EC capable MS in a cell that does not support EC-GSM-IoT shall operate according to Table 3.5.2.1.2.1 if it supports GPRS services using GPRS TBFs or EGPRS TBFs. | | + +Upon leaving idle mode the mobile station shall ignore PAGING REQUEST messages indicating a packet paging procedure. + +A mobile station belonging to GPRS MS class A or B shall continue to monitor its paging subchannel on CCCH for PAGING REQUEST messages indicating an establishment of RR connection. A mobile station belonging to GPRS MS class B may abort the packet access procedure at the receipt of a PAGING REQUEST messages indicating an establishment of RR connection. An exception is the case of a MS that has enabled PEO or EC operation in which case the MS never monitors its paging subchannel on CCCH for PAGING REQUEST messages indicating an establishment of RR connection (see sub-clause 3.3.1). + +The CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages are sent on RACH and contain the parameters: + +- an establishment cause which indicates packet access, and as applicable, a request for one phase packet access, single block packet access or a single block MBMS access for a CHANNEL REQUEST (sub-clause 9.1.8), or a request for one phase access or two phase access or short access or sending of signalling data for an EGPRS PACKET CHANNEL REQUEST (see 3GPP TS 44.060); +- a random reference which is drawn randomly from an uniform probability distribution for every new transmission; +- a capability indication which indicates the support of IMMEDIATE PACKET ASSIGNMENT for an EGPRS PACKET CHANNEL REQUEST (see 3GPP TS 44.060). + +The EGPRS MULTILATERATION REQUEST message is sent on RACH and indicates packet access by a mobile station that has enabled PEO operation and is accessing the network to send a 'Page Response for Positioning Event' or to a perform the radio access part of a MTA procedure using one of the following methods: + +- If the RLC Data block method is used (see sub-clause 3.11) this message includes a random reference which is drawn randomly from a uniform probability distribution for every new transmission. +- If the Access Burst method is used (see sub-clause 3.11) this message includes a Short ID parameter (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]). +- If the Extended Access Burst method is used (see sub-clause 3.11) the first instance of this message includes the "Random ID Low" and "MS Transmission Offset" parameters and the second instance of this message includes + +the "Random ID Low", "MS Sync Accuracy", "Random ID High" and the "Short BSS ID" parameters (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]). + +Prior to sending an EGPRS PACKET CHANNEL REQUEST or EGPRS MULTILATERATION REQUEST message on the RACH a MS shall determine the applicable CCCH\_GROUP as follows: + +- If eDRX is enabled or it is attempting to enable eDRX the MS shall determine its CCCH\_GROUP as per idle mode when extended DRX cycles are used (see 3GPP TS 45.002 [32]). +- Otherwise, the MS shall determine its CCCH\_GROUP as per idle mode when extended DRX cycles are not used (see 3GPP TS 45.002 [32]). + +The EC PACKET CHANNEL REQUEST messages are sent on RACH and indicate packet access by a mobile station that has enabled EC operation where the included parameters are as described in sub-clause 9.1.65. Prior to sending an EC PACKET CHANNEL REQUEST message on the RACH the MS shall set CCCH\_GROUP = 0 (see sub-clauses 3.5.2.1.2 and 9.1.30c). + +After sending the first CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EGPRS MULTILATERATION REQUEST message, the mobile station shall start listening to the full downlink CCCH timeslot corresponding to its CCCH\_GROUP. After sending the first EC PACKET CHANNEL REQUEST message a mobile station that has enabled EC operation shall listen to the downlink CCCH timeslot using CCCH\_GROUP = 0 (see 3GPP TS 45.002). In addition, a mobile station that has sent a CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EGPRS MULTILATERATION REQUEST message shall start listening to the BCCH to perform signal strength measurements as they are defined for packet idle mode, see 3GPP TS 45.008. A mobile station that has sent an EC PACKET CHANNEL REQUEST message need not perform signal strength measurements. + +A mobile station accessing the network to perform the radio access part of a MTA procedure (see TS 3GPP 44.031) or accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) that has sent one or more CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST or EGPRS MULTILATERATION REQUEST messages shall proceed as follows: + +- If the mobile station receives an IMMEDIATE ASSIGNMENT, an IMMEDIATE ASSIGNMENT EXTENDED, an EC IMMEDIATE ASSIGNMENT TYPE 1 (if EC operation is enabled), an IMMEDIATE PACKET ASSIGNMENT (if supported) or an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its last 3 transmitted CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST or EGPRS MULTILATERATION REQUEST messages it shall act on that message as described in sub-clause 3.5.2.1.3. +- If the mobile station successfully decodes an RR message, which is not a response corresponding to one of its last 3 transmitted CHANNEL REQUEST or EGPRS CHANNEL REQUEST or EC PACKET CHANNEL REQUEST messages, that indicates an implicit reject for the PS domain (see sub-clause 3.3.1.1.1a) it shall start timer T3146 (if not already running) and initiate the implicit reject procedure as described in sub-clause 3.3.1.1.3.2a. +- If the mobile station has enabled PEO and has sent one or more EGPRS MULTILATERATION REQUEST messages in a cell that supports MTA then it shall ignore the implicit reject information when received in an RR message which is not a response corresponding to one of its last 3 transmitted EGPRS MULTILATERATION REQUEST messages. +- If a mobile station sends a EGPRS MULTILATERATION REQUEST message indicating 'RLC Data Block method' or 'Page Response for Positioning Event' (see 3GPP TS 44.060 [76]) a matching IMMEDIATE ASSIGNMENT message includes "Request Reference" information that matches the Random Bits and TDMA Frame information used by the MS when sending the EGPRS MULTILATERATION REQUEST message (see sub-clause 10.5.2.30). Similarly, a matching IMMEDIATE PACKET ASSIGNMENT message includes Random Reference information that matches the 11 bits of information included within the EGPRS MULTILATERATION REQUEST message. +- If a mobile station sends a EGPRS MULTILATERATION REQUEST message indicating 'Access Burst method' (see 3GPP TS 44.060 [76]) a matching IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message includes the same "Short ID" parameter value used by the MS when sending the EGPRS MULTILATERATION REQUEST message (see sub-clause 10.5.2.87). +- If a mobile station sends a EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 1' (see 3GPP TS 44.060 [76]) a matching IMMEDIATE ASSIGNMENT or IMMEDIATE + +PACKET ASSIGNMENT message includes the same "Random ID Low" parameter value used by the MS when sending the EGPRS MULTILATERATION REQUEST message (see sub-clause 10.5.2.87). + +- If a mobile station sends a EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 2' (see 3GPP TS 44.060 [76]) a matching IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message message includes the same "Random ID High" parameter value used by the MS when sending the EGPRS MULTILATERATION REQUEST message (see sub-clause 10.5.2.87). + +Having sent the maximum number of CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST or EGPRS MULTILATERATION REQUEST messages, the mobile station starts timer T3146. At expiry of timer T3146, if the packet access procedure is ongoing then it is aborted, a random access failure is indicated to upper layers and autonomous cell re-selection is performed according to 3GPP TS 43.022. At expiry of timer T3146, if the radio access part of the MTA procedure is ongoing then it is aborted for the current cell and the mobile station MS tunes to the next cell in the list of applicable cells and continues the radio access part of the MTA procedure therein. + +If the mobile station receives an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message (if supported) during the packet access procedure indicating a packet downlink assignment procedure, the mobile station shall abort the packet access procedure and respond to the IMMEDIATE ASSIGNMENT or the IMMEDIATE PACKET ASSIGNMENT message as specified in sub-clause 3.5.3.1.2 or sub-clause 3.5.3.2. If the Packet Downlink Assignment IE in IMMEDIATE ASSIGNMENT message or *IPA Downlink Assignment struct* in IMMEDIATE PACKET ASSIGNMENT message indicates a downlink TBF, the mobile station shall then attempt an establishment of uplink TBF, using the procedure specified in 3GPP TS 44.060 which is applicable in packet transfer mode. If the Packet Downlink Assignment IE in IMMEDIATE ASSIGNMENT message indicates a downlink single block then the mobile station shall wait for the allocated single block and react on the received message before reattempting the uplink TBF establishment. + +### 3.5.2.1.2a EC Packet access procedure (EC-CCCH) + +The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST messages (see Table 3.5.2.1.2a.1 and sub-clause 9.1.65) as follows: + +- Using the 1TS EC-RACH Mapping method if CC1 has been selected on the uplink or if *Access\_Timeslots=0*, sent in EC SYSTEM INFORMATION TYPE 2. +- Using the 2TS EC-RACH Mapping method if CC2, CC3, CC4 or CC5 has been selected on the uplink and *Access\_Timeslots=1*, sent in EC SYSTEM INFORMATION TYPE 2 has been selected on the uplink and *Access\_Timeslots=1*, sent in EC SYSTEM INFORMATION TYPE 2. +- When the 2TS EC-RACH Mapping method for CC2, CC3 and CC4 is used the EC-RACH is mapped over two consecutive timeslots, and the EC PACKET CHANNEL REQUEST messages sent across the 2 timeslots shall be identical and shall use the same training sequence code (i.e one of TS5, TS6 or TS7 is used according to the uplink CC). +- When the 2TS EC-RACH Mapping method is used for CC5 and EC SI 2 parameter CC5\_EC-RACH\_FORMAT\_IND (see sub-clause 9.1.43q) indicates usage of ESAB, then EC-RACH CC5 transmissions are performed using ESAB (see 3GPP TS 45.002 [32]). +- When the 2TS EC-RACH Mapping method is used for CC5 and EC SI 2 parameter CC5\_EC-RACH\_FORMAT\_IND (see sub-clause 9.1.43q) indicates usage of EDAB, then EC-RACH CC5 transmissions are performed using EDAB (see 3GPP TS 45.002 [32]). + +See 3GPP TS 45.002 for details regarding coverage class specific rules for multiplexing blind physical layer transmissions using the 2 TS EC-RACH. + +Prior to sending an EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message on the EC-RACH a MS shall determine the applicable EC\_CCCH\_GROUP as per idle mode for EC-GSM-IoT (see 3GPP TS 45.002 [32]). + +After scheduling the transmission of EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST messages it leaves idle mode (in particular, the mobile station shall ignore EC PAGING REQUEST messages). + +**Table 3.5.2.1.2a.1: EC Packet Access Procedure** + +| Purpose of the packet access procedure | EC-GSM-IoT Capable Cell | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| User data transfer (requested RLC mode = acknowledged) or Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc) | EC PACKET CHANNEL REQUEST sent using either TS3, TS5, TS6, TS7 or TS8 - see sub-clause 9.1.65 (NOTE 1) | +| Transmission of an EC MULTILATERATION REQUEST message indicating 'RLC Data Block' method or 'Page Response for Positioning Event' or 'Extended Access Burst' method or 'Access Burst' method. | EC MULTILATERATION REQUEST sent using either TS4, TS5, TS6, TS7 or TS8- see sub-clause 9.1.65 (NOTE 1) | +| NOTE 1: An EC capable MS in a cell that does not support EC-GSM-IoT shall operate according to Table 3.5.2.1.2.1 if it supports GPRS TBFs or EGPRS TBFs. | | + +The mobile station then sends maximally $M + 1$ EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST messages where each message is repeated according to the number of blind physical layer transmissions corresponding to its uplink CC. The first EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message is sent using a transmission opportunity corresponding to its uplink coverage class randomly selected (with uniform probability distribution) from a set of Tcc 51-multiframes on the EC-RACH/RACH as shown in Table 3.5.2.1.2a.2. When sending a page response the set of Tcc 51-multiframes starts with the first 51-multiframe immediately following the last 51-multiframe used for receiving the corresponding paging request. For a mobile originated access attempt the set of Tcc 51-multiframes starts with the first 51-multiframe (following the 51-multiframe during which upper layers requested the transfer of a LLC PDU) that contains a transmission opportunity corresponding to its uplink coverage class. + +**Table 3.5.2.1.2a.2: Values of parameters Scc and Tcc** + +| | Scc | Tcc | +|-----|--------------|--------------------| +| CC1 | Sm | Tm | +| CC2 | Sm | Tm | +| CC3 | $2 \cdot Sm$ | $2 \cdot Tm$ | +| CC4 | $4 \cdot Sm$ | $2 \cdot (Tm + 1)$ | +| CC5 | $4 \cdot Sm$ | $3 \cdot (Tm + 2)$ | + +The value for Sm is sent in the EC SYSTEM INFORMATION TYPE 2 message and is used for determining the Scc value applicable for monitoring the EC-AGCH according to the selected downlink coverage class of the mobile station. + +The value for Tm is sent in the EC SYSTEM INFORMATION TYPE 2 message and is used for determining the Tcc value applicable for randomly selecting an EC-RACH (and possibly RACH) transmission opportunity corresponding to the selected uplink coverage class of the mobile station. + +M is the value of the parameter "EC\_Max\_Retrans" sent in the EC SYSTEM INFORMATION TYPE 2 message. + +The EC PACKET CHANNEL REQUEST message (see sub-clause 9.1.65) contains the following parameters: + +- a random reference field which is drawn randomly from a uniform probability distribution for every new transmission; +- a field indicating the downlink coverage class selected by the mobile station (only included when the message is sent on EC-RACH); +- a field indicating the signal strength measured by the MS (only included when the message is sent on RACH); +- a field indicating the purpose of the data transfer ("page response", "cell update", "RLC/MAC control message" or "uplink data transfer") and the number of uplink data blocks it has to send (assuming MCS-1 channel coding is used); +- a field indicating the priority of the packet access request. + +A mobile station that has enabled EC operation starts the radio access part of the MTA procedure upon receiving a RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031) if both the MS and the serving cell support the MTA procedure method indicated therein (see the MTA\_BITMAP field described in sub-clause 10.5.2.37b). In this case it starts the MPM timer and starts accessing the network using cells it has selected to perform the radio access part of a MTA procedure. For each selected cell it compares the BSIC of the EC-CCCH to the BSIC. If the BSIC does not match it does not perform the radio access part of the MTA procedure using that cell. If the BSIC matches it does not check the status of the *EC-BCCH CHANGE MARK* field and implicit reject status information sent for that cell, sends a EC MULTILATERATION REQUEST message (see sub-clause 9.1.65) and proceeds as follows: + +- If the EC MULTILATERATION REQUEST message indicates the RLC Data block method is used (see sub-clause 3.11) it includes a random reference which is drawn randomly from a uniform probability distribution for every new transmission and a field indicating the downlink coverage class selected by the mobile station (see sub-clause 9.1.65). After transmitting this message and receiving a matching EC IMMEDIATE ASSIGNMENT TYPE 2 message it transmits a RLC data block containing MTA related parameters (see 3GPP TS 44.060 [76]) therein. After receiving a corresponding acknowledgement on the EC-PACCH (see 3GPP TS 44.060 [76]) the MS tunes to the next cell in the list of applicable cells and continues the procedure therein. After performing the radio access part of the MTA procedure in all applicable cells or when the MPM timer expires it returns to idle mode in the cell it was in when the radio access part of the MTA procedure was triggered. +- If the EC MULTILATERATION REQUEST message indicates the Access Burst method is used (see sub-clause 3.11) it includes a Short ID parameter (see sub-clause 9.1.65). After transmitting this message and receiving a matching EC IMMEDIATE ASSIGNMENT TYPE 3 message (see sub-clause 9.1.68) it tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. After performing the radio access part of the MTA procedure in all applicable cells or when the MPM timer expires it returns to idle mode in the cell it was in when the radio access part of the MTA procedure was triggered. +- If the Extended Access Burst method is used (see sub-clause 3.11) it sends a first EC MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 1' and includes the "Random ID Low" and "MS Transmission Offset" parameters therein (see sub-clause 9.1.65). After receiving a matching EC IMMEDIATE ASSIGNMENT TYPE 3 message (see sub-clause 9.1.68) it sends a second EC MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 2' and includes the "Random ID Low", the "MS Sync Accuracy", the "Random ID High" and the "Short BSS ID" parameters therein. After receiving a matching EC IMMEDIATE ASSIGNMENT TYPE 3 message for the second EC MULTILATERATION REQUEST message it tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. After performing the radio access part of the MTA procedure in all applicable cells or when the MPM timer expires it returns to idle mode in the cell it was in when the radio access part of the MTA procedure was triggered. +- The MS shall not send an EC PACKET CHANNEL REQUEST message while performing the radio access part of the MTA procedure except for the case of a high priority transmission (i.e. 'EC Priority' = 1, see sub-clause 9.1.65) in which case it shall stop the MPM timer and abort the MTA procedure. When a BSS receives an uplink LLC PDU while the MPM timer is running for the corresponding MS it informs the SMLC that no additional timing advance information is pending for the corresponding MTA procedure (see 3GPP TS 49.031), stops the MPM timer and terminates the MTA procedure for that MS. + +After sending the first EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message or a subsequent retransmission, the mobile station shall start reading the EC-AGCH (according to the downlink coverage class indicated within the corresponding EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message) in an attempt to find a response matching its last transmission. + +- For the case where the EC MULTILATERATION REQUEST message indicates 'RLC Data Block method' or 'Page Response for Positioning Event' (see sub-clause 9.1.65) a matching EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60) includes "EC Request Reference" information that matches the Random Bits and TDMA Frame information used by the MS when sending the EC MULTILATERATION REQUEST message (see sub-clause 10.5.2.83). +- For the case where the EC MULTILATERATION REQUEST message indicates 'Access Burst method' (see sub-clause 9.1.65) a matching EC IMMEDIATE ASSIGNMENT TYPE 3 message (see sub-clause 9.1.68) indicates a downlink coverage class corresponding to the training sequence used by the MS and includes the same "Short ID" parameter value used by the MS when sending the EC MULTILATERATION REQUEST message. + +- For the case where the EC MULTILATERATION REQUEST message indicates 'Extended Access Burst method – part 1' (see sub-clause 9.1.65) a matching EC IMMEDIATE ASSIGNMENT TYPE 3 message indicates downlink coverage class 1 and includes the same "Random ID Low" parameter value used by the MS when sending the EC MULTILATERATION REQUEST message. +- For the case where the EC MULTILATERATION REQUEST message indicates 'Extended Access Burst method – part 2' (see sub-clause 9.1.65) a matching EC IMMEDIATE ASSIGNMENT TYPE 3 message indicates downlink coverage class 1 and includes the same "Random ID High" parameter value used by the MS when sending the EC MULTILATERATION REQUEST message. +- A MS that has selected downlink CC1 shall begin looking for a matching response starting within downlink 51-multiframe N (i.e. $N = \text{TDMA FN div } 51$ ) if it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message and there is at least one remaining valid CC1 reception opportunity in downlink 51-multiframe N. If a matching response is not found or there are no remaining valid CC1 reception opportunities within downlink 51-multiframe N it shall start reading 51-multiframe N+1 in an attempt to find a matching response. The total number of downlink 51-multiframes it reads (excluding downlink 51-multiframe N) in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2). +- A MS that has selected downlink CC2 shall begin looking for a matching response starting within downlink 51-multiframe N if it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message, $N \bmod 2 = 0$ and there is at least one remaining valid CC2 reception opportunity that starts in downlink 51-multiframe N. If a matching response is not found using downlink 51-multiframes N and N+1 or there are no remaining valid CC2 reception opportunities that start within downlink 51-multiframe N it shall start reading downlink 51-multiframe N+1 (respectively N+2) if $N \bmod 2 = 1$ (respectively $N \bmod 2 = 0$ ). The total number of downlink 51-multiframes it reads (excluding downlink 51-multiframe N) in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2). +- A MS that has selected downlink CC3 shall begin looking for a matching response starting with downlink 51-multiframe N+1 (respectively N+2) when it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message where $N \bmod 2 = 1$ (respectively $N \bmod 2 = 0$ ). The total number of downlink 51-multiframes it reads in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2). +- A MS that has selected downlink CC4 shall begin looking for a matching response starting with downlink 51-multiframe N+1 (respectively N+2, N+3, N+4) when it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message where $N \bmod 4 = 3$ (respectively $N \bmod 4 = 2, 1, 0$ ). The total number of downlink 51-multiframes it reads in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2). + +A mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) that has sent one or more EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST messages shall proceed as follows: + +- If, while reading the total number of downlink 51-multiframes determined by Scc, the mobile station receives an EC IMMEDIATE ASSIGNMENT TYPE 2, EC IMMEDIATE ASSIGNMENT TYPE 4 or an EC IMMEDIATE ASSIGNMENT REJECT or an EC IMMEDIATE ASSIGNMENT TYPE 3 message corresponding to its last transmitted EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message it shall act on that message as described in sub-clause 3.5.2.1.3a. +- If a matching response is not found and the mobile station is not sending an exception report (see sub-clause 9.1.65) it shall examine the Implicit Reject Status (IRS) field sent as part of the EC-SCH INFORMATION message (see sub-clause 9.1.30c). If the IRS field indicates the access attempt is rejected the mobile station shall abort the packet access procedure, start timer T3146 (if not already running) and initiate the EC Implicit Reject procedure (see sub-clause 3.5.2a.2). An exception case is where a mobile station is performing the radio access part of the MTA procedure in a cell that supports MTA (see the MTA\_BITMAP field described in sub-clause 9.1.43q) in which case it shall not examine the IRS field. +- Otherwise, the MS schedules the sending of another EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message (if allowed according to "EC\_Max\_Retrans") using a transmission opportunity corresponding to its uplink coverage class randomly selected (with uniform probability distribution) from a set of Tcc 51-multiframes on the EC-RACH (determined using Tm as shown in Table 3.5.2.1.2a.2). + +- The set of Tcc 51-multiframes starts with the first 51-multiframe (following the set of Scc downlink 51-multiframe read in attempt to find a matching response or following the last downlink 51-multiframe read to acquire the IRS field) that contains a transmission opportunity corresponding to its uplink coverage class. +- When scheduling another EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message the MS uses the "CC\_Access\_Adaptation" parameter (broadcast in EC SYSTEM INFORMATION TYPE 2 message) to determine if it is allowed to increment both its uplink CC and downlink CC to the next CC supported by the network (unless it is already using CC4). +- Upon incrementing its uplink/downlink CC the number of subsequent EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message transmission attempts that may occur before it is allowed to increment its uplink/downlink CC once again is the same as when sending the first EC PACKET CHANNEL REQUEST message (i.e. determined by the "CC\_Access\_Adaptation" parameter). +- When sending up to M + 1 EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST messages the MS may increment its uplink CC and downlink CC a maximum of 2 times if CC adaptations are allowed according to the "CC\_Access\_Adaptation" parameter. + +Having sent M + 1 EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST messages, the RR entity of the mobile station starts timer T3146 at the start of the first of the set of downlink 51-multiframes (excluding downlink 51-multiframe N) it reads in an attempt to find a matching response as determined by Scc (see Table 3.5.2.1.2a.2). At expiry of timer T3146, if the packet access procedure is ongoing then it is aborted, a random access failure is indicated to upper layers and autonomous cell re-selection is performed according to 3GPP TS 43.022. At expiry of timer T3146, if the radio access part of the MTA procedure is ongoing then it is aborted for the current cell and the mobile station tunes to the next cell in the list of applicable cells and continues the radio access part of the MTA procedure therein. + +### 3.5.2.1.3 Packet immediate assignment + +#### 3.5.2.1.3.1 On receipt of a CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST message or EGPRS MULTILATERATION REQUEST + +On receipt of a CHANNEL REQUEST message indicating a packet access, the network may allocate a temporary flow identity and assign a packet uplink resource comprising one PDCH for an uplink temporary block flow in GPRS TBF mode. On receipt of an EGPRS PACKET CHANNEL REQUEST message, the network may allocate a temporary flow identity and assign a packet uplink resource comprising one PDCH for an uplink temporary block flow in EGPRS TBF mode or GPRS TBF mode. + +On receipt of an EC PACKET CHANNEL REQUEST message on the RACH, the network may allocate a temporary flow identity and assign pre-allocated packet uplink resources comprising one or several PDCHs for an uplink temporary block flow in EC TBF mode. + +On receipt of an EGPRS MULTILATERATION REQUEST message on the RACH (see 3GPP TS 44.060 [76]), the network proceeds according the Multilateration Timing Advance (MTA) method indicated therein (see sub-clause 3.5.2.1.2 and 3.11). + +If the establishment cause in the CHANNEL REQUEST message indicates a request for a single block packet access, the network shall grant only the single block period on the assigned packet uplink resource if the network allocates resource for the mobile station. If the establishment cause in the EGPRS PACKET CHANNEL REQUEST message indicates a request for a two phase access, the network shall grant one or two radio blocks for the mobile station (within a Multi Block allocation) to send a PACKET RESOURCE REQUEST and possibly an ADDITIONAL MS RADIO ACCESS CAPABILITIES messages on the assigned packet uplink resource if the network allocates resource for the mobile station. + +If the establishment cause in the CHANNEL REQUEST message indicates a request for one phase packet access, the network may grant either a one phase packet access or a single block packet access for the mobile station. If a single block packet access is granted, it forces the mobile station to perform a two phase packet access. If the establishment cause in the EGPRS PACKET CHANNEL REQUEST message indicates a request for one phase packet access or sending signalling data, the network may grant either a one phase packet access or a two phase access (within a Multi Block allocation). If a multiple block packet access is granted, it forces the mobile station to perform a two phase packet access. In the case of a MS that has enabled PEO the establishment cause always indicates a one phase access and the network shall prioritize the granting of a one phase packet access. + +When EC operation is not enabled the packet uplink resource is assigned to the mobile station in an IMMEDIATE ASSIGNMENT or an IMMEDIATE PACKET ASSIGNMENT message (if supported) sent in unacknowledged mode on the same CCCH timeslot on which the network has received the CHANNEL REQUEST or the EGPRS PACKET CHANNEL REQUEST message. The network may assign packet resource to the mobile station in an IMMEDIATE PACKET ASSIGNMENT message if the received EGPRS PACKET CHANNEL REQUEST message indicates the support of this assignment message. There is no further restriction on what part of the downlink CCCH timeslot the IMMEDIATE ASSIGNMENT and IMMEDIATE PACKET ASSIGNMENT message can be sent. Timer T3141 is started on the network side. + +When EC operation is enabled the packet uplink resource is assigned to the mobile station in an EC IMMEDIATE ASSIGNMENT TYPE 1 message sent in unacknowledged mode on the same CCCH timeslot on which the network received the EC PACKET CHANNEL REQUEST message (see Table 3.5.2.1.2.3). Timer T3141 is started on the network side. + +The IMMEDIATE ASSIGNMENT and EC IMMEDIATE ASSIGNMENT TYPE 1 messages contain: + +- the information field of the CHANNEL REQUEST, the EGPRS PACKET CHANNEL REQUEST or the EC PACKET CHANNEL REQUEST message and the frame number of the frame in which the CHANNEL REQUEST, the EGPRS PACKET CHANNEL REQUEST or the EC PACKET CHANNEL REQUEST message was received; +- the packet channel description; +- the initial timing advance; +- the packet uplink assignment or EGPRS packet uplink assignment construction (only applies to the IMMEDIATE ASSIGNMENT message). +- the packet resources used for the uplink EC TBF which includes the set of pre-allocated uplink resources described by the *EC Fixed Uplink Allocation* IE (only applies to the EC IMMEDIATE ASSIGNMENT TYPE 1 message). + +The IMMEDIATE PACKET ASSIGNMENT message contains parameters relevant to the assignment of packet resources as specified in subclauses 3.5.2.1.3.2 and 3.5.2.1.3.3. + +If frequency hopping is applied, the network may use the indirect encoding or the direct encoding of the frequency configuration in the *Packet Channel Description* information element in IMMEDIATE ASSIGNMENT message or in the *IPA Uplink Assignment struct*, *IPA Downlink Assignment struct*, or *IPA Single Block Uplink Assignment struct* in IMMEDIATE PACKET ASSIGNMENT message. If the indirect encoding is used, the mobile station uses information received in system information or stored from a previous assignment to determine the frequency parameters, see 3GPP TS 44.060. If the direct encoding is used, the mobile station uses the cell allocation defined for the cell to decode the mobile allocation. + +If the *indirect encoding* is used, the IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message may contain a CHANGE\_MARK\_1 field. If that is present, the mobile station shall verify the validity of the SI13\_CHANGE\_MARK associated with the GPRS mobile allocation to which the message refers, see 3GPP TS 44.060. If the CHANGE\_MARK\_1 field and the SI13\_CHANGE\_MARK do not match, the message does not satisfactorily define a PDCH. + +If EC operation is enabled the network indicates the frequency configuration in the *EC Packet Channel Description Type 1* information element (see sub-clause 10.5.2.84) in the EC IMMEDIATE ASSIGNMENT TYPE 1 message. + +If the mobile station receives an IMMEDIATE ASSIGNMENT message and the *Dedicated mode or TBF* information element indicates that this is the first message in a two-message assignment, the mobile station shall continue to listen to the full CCCH. The network may send a second IMMEDIATE ASSIGNMENT message to the mobile station within two multiframe periods following the first IMMEDIATE ASSIGNMENT message, specifying the packet channel description and, if required, a mobile allocation for the assignment. The two IMMEDIATE ASSIGNMENT messages in a two-message assignment shall have the same contents of the *Request Reference* information elements. + +If the mobile station does not receive the second IMMEDIATE ASSIGNMENT messages in a two-message assignment within two multiframe periods following the first message, the mobile station shall discard the first IMMEDIATE ASSIGNMENT message received. + +On receipt of an IMMEDIATE ASSIGNMENT message or, in case of a two-message assignment, a matching pair of IMMEDIATE ASSIGNMENT messages corresponding to one of its 3 last CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, the mobile station stops T3146 (if running), stops sending CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, and switches to the assigned PDCH. + +On receipt of an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message (see sub-clauses 9.1.18 and sub-clause 9.1.18b) corresponding to one of its 3 last EGPRS MULTILATERATION REQUEST messages (see 3GPP TS 44.060 [76]), the mobile station stops T3146 (if running), stops sending EGPRS MULTILATERATION REQUEST messages, and proceeds as follows: + +- If the EGPRS MULTILATERATION REQUEST message indicated 'Page Response for Positioning Event' (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]) the mobile station switches to the assigned PDCH and transmits a RLC Data Block thereon. Upon receiving a corresponding Ack the mobile station returns to Idle mode. +- If the EGPRS MULTILATERATION REQUEST message indicated 'RLC Data Block method' (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]) the mobile station switches to the assigned PDCH and transmits a RLC Data Block thereon. Upon receiving a corresponding Ack the mobile station considers the radio access part of the MTA procedure as successfully completed in the current cell, tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. +- If the EGPRS MULTILATERATION REQUEST message indicated 'Access Burst method' (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]) the mobile station considers the radio access part of the MTA procedure as successfully completed in the current cell, tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. +- If the EGPRS MULTILATERATION REQUEST message indicated 'Extended Access Burst method – part 1' (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]) the mobile station starts sending EGPRS MULTILATERATION REQUEST messages indicating 'Extended Access Burst method – part 2'. +- If the EGPRS MULTILATERATION REQUEST message indicated 'Extended Access Burst method – part 2' (see sub-clause 3.5.2.1.2 and 3GPP TS 44.060 [76]) the mobile station considers the radio access part of the MTA procedure as successfully completed in the current cell, tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. + +On receipt of an EC IMMEDIATE ASSIGNMENT TYPE 1 message corresponding to one of its 3 last EC PACKET CHANNEL REQUEST messages on the RACH, the mobile station stops T3146 (if running), stops sending EGPRS PACKET CHANNEL REQUEST messages, and switches to the assigned PDCH(s). + +The content of the packet uplink assignment construction (respectively EGPRS packet uplink assignment construction) indicates which type of packet access is granted: *one phase packet access* or *single (respectively multiple) block packet access*. + +### 3.5.2.1.3.2 One phase packet access + +In the case the one phase packet access is granted, the packet uplink assignment construction contains: + +- the temporary flow identity; +- the USF value +- the channel coding scheme for RLC data blocks; +- the power control parameters; +- the polling bit; +- optionally, the timing advance index (see 3GPP TS 45.010); +- optionally, the TBF starting time. + +In addition, the EGPRS packet uplink assignment construction also contains: + +- the EGPRS modulation and coding scheme; +- information whether retransmitted uplink data blocks shall be resegmented or not; + +- the EGPRS window size to be used within the transmission; and +- optionally a request for the mobile station to send its radio access capability information. + +In addition, if sent in response to a one phase access with access type indicating "One Phase Access Request by Reduced Latency MS" as defined in 3GPP TS 44.060, the EGPRS packet uplink assignment construction also allows: + +- the possibility to assign an uplink EGPRS TBF on a maximum of two uplink PDCH pairs situated on consecutive or on non-consecutive timeslots for RTTI configuration; +- the inclusion of an indication if RTTI or BTI USF mode is used; +- the inclusion of an indication of whether the SSN-based or Time-Based approach shall be used for PAN fields. + +The medium access method is *dynamic allocation* and the RLC mode is *acknowledged mode*, see 3GPP TS 44.060. + +If the timing advance index (TAI) is included in the packet uplink assignment construction, the mobile station shall use the continuous update timing advance mechanism, see 3GPP TS 45.010, using PTCCH in the same timeslot as the assigned PDCH. If a timing advance index (TAI) field is not included, the continuous update timing advance mechanism shall not be used. + +In case the packet uplink assignment or EGPRS packet uplink assignment construction contains a TBF starting time and the mobile station receives the message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time before accessing the channel. If the mobile station receives the message after the TBF starting time has expired, it shall ignore the TBF starting time and may immediately access the channel. If the medium access method is *dynamic allocation*, the mobile station shall start timer T3164. Regardless of which allocation mode is used, the mobile station shall proceed with the contention resolution at one phase access defined in 3GPP TS 44.060. + +If the Polling bit is set to 1, MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message (see 44.060) on the assigned PDCH, in the uplink block specified by the TBF Starting Time. In this case the TBF Starting Time is used both to indicate when the assigned PDCH becomes valid and to specify the uplink block. If the TBF Starting Time is not present or has expired, the MS shall ignore the polling request. + +When the mobile station switches to the assigned PDCH, it shall take the power control parameters received in the IMMEDIATE ASSIGNMENT or the IMMEDIATE PACKET ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode, see 3GPP TS 45.008. + +In the case the one phase packet access is granted to MS supporting IMMEDIATE PACKET ASSIGNMENT, the *IPA Uplink Assignment struct* sent in the IMMEDIATE PACKET ASSIGNMENT message may assign packet uplink resource for multiple mobile stations and contain following parameters specific to different mobile stations: + +- the temporary flow identity; +- the USF value; +- the EGPRS channel coding command for RLC data block; +- the timing advance value; +- the Radio Access Capabilities Request bit. + +In addition, the *IPA Uplink Assignment struct* contains the timeslot number which is common to all mobile stations addressed in this construction. Relevant default values shall be used for the RLC window size, Alpha, RESEGMENT and USF\_GRANULARITY parameters as specified in subclause 10.5.2.78. + +If the *Radio Access Capability Request* bit is set to 1, mobile stations addressed in the *IPA Uplink Assignment struct* in the IMMEDIATE PACKET ASSIGNMENT message shall send *MS Radio Access Capability 2 IE* in PACKET RESOURCE REQUEST message. + +When assigning an EGPRS TBF, the network may request information about radio access capabilities of the mobile station on one or several frequency bands within the IMMEDIATE ASSIGNMENT or the IMMEDIATE PACKET ASSIGNMENT message; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall provide the network with its radio access capabilities for the frequency bands it supports, in the same priority order as the one specified by the network, by sending a PACKET + +RESOURCE REQUEST message, and an ADDITIONAL MS RADIO ACCESS CAPABILITIES if all the requested informations do not fit in the PACKET RESOURCE REQUEST. If the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the BCCH frequency band. The mobile station shall indicate in the PACKET RESOURCE REQUEST if it will send more information about its radio access capabilities in the ADDITIONAL MS RADIO ACCESS CAPABILITIES message. The PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES shall be sent within the one or two first radio blocks allocated for the mobile station on the assigned PDCH. + +The network may request a retransmission of the PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES messages. A request for retransmission of one or both of these messages shall be indicated in the PACKET UPLINK ACK/NACK message. The mobile station has to indicate within the PACKET RESOURCE REQUEST if the message is a retransmitted one. + +In the case of an uplink EGPRS TBF assignment in RTTI configuration where an IMMEDIATE ASSIGNMENT message is sent in response to a one phase access with access type indicating "One Phase Access Request by Reduced Latency MS" as defined in 3GPP TS 44.060, the assigned timeslots of the uplink PDCH pair(s) and the corresponding downlink PDCH pair (as defined in 3GPP TS 44.060) associated with each assigned uplink PDCH pair are indicated by a combination of the TN given by the *Packet Channel Description* information element and information in the EGPRS Packet Uplink Assignment construction of the IA Rest Octets information element as described in sub-clause 10.5.2.16. + +### 3.5.2.1.3.3 Single block packet access + +In the case the single block packet access is granted, the packet uplink resource description contains: + +- the power control parameter setting; +- the TBF starting time. + +In the case the single block packet access is granted to a mobile station supporting IMMEDIATE PACKET ASSIGNMENT message, the *IPA Single Block Uplink Assignment struct* sent in the IMMEDIATE PACKET ASSIGNMENT message may assign one uplink block for multiple mobile stations and contains the following parameters specific to different mobile stations: + +- the power control parameter setting; +- the timing advance value; +- the relative TBF starting time; and +- the frequency parameters. + +In addition, the *IPA Single Block Uplink Assignment struct* contains the timeslot number which is common to all mobile stations addressed in this construction. + +If the mobile station receives the IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message before the TBF starting time has expired, it shall wait until the block period indicated by the TBF starting time. The network shall use the TBF starting time to indicate the first frame number belonging to the single block period granted for packet access. The mobile station may either use the assigned block period to send a PACKET RESOURCE REQUEST message to initiate the two phase packet access procedure defined in 3GPP TS 44.060, or to send an RLC/MAC control message other than the PACKET RESOURCE REQUEST message to the network, see sub-clause 3.5.2.2. + +If the mobile station receives the IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message after the TBF starting time has expired, a failure has occurred. + +If a failure occurs and the packet access attempt was due to a request from upper layers to transfer a LLC PDU, a TBF establishment failure has occurred and the mobile station proceeds as specified in sub-clause 3.5.2.1.5. If a failure occurs and the packet access attempt was due to the sending of an RLC/MAC control message, the packet access is aborted, the mobile station returns to packet idle mode. + +### 3.5.2.1.3.3a Multiblock packet access + +In the case the multiblock packet access is granted, the EGPRS packet uplink assignment description contains: + +- timeslot number of the allocation and the number of blocks allocated; + +- the power control parameter setting; +- the TBF starting time. + +When assigning a multiblock packet access, the network may request information about radio access capabilities of the mobile station on one or several frequency bands within the IMMEDIATE ASSIGNMENT message and allocate one or two radio blocks for uplink control messages accordingly ; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall then provide the network with its radio access capabilities for the frequency bands it supports, in the same priority order as the one specified by the network, by sending a PACKET RESOURCE REQUEST message in the first radio block on the assigned PDCH, and an ADDITIONAL MS RADIO ACCESS CAPABILITIES immediately after the PACKET RESOURCE REQUEST message on the assigned PDCH if all the requested informations do not fit in the PACKET RESOURCE REQUEST and two radio blocks have been allocated by the network. If the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the BCCH frequency band in the PACKET RESOURCE REQUEST message. The mobile station shall indicate in the PACKET RESOURCE REQUEST if it will send more information about its radio access capabilities in the ADDITIONAL MS RADIO ACCESS CAPABILITIES message. If the mobile station has been allocated two radio blocks and all the requested informations fit in the PACKET RESOURCE REQUEST message, no ADDITIONAL MS RADIO ACCESS CAPABILITIES message shall be sent (see 3GPP TS 44.060). Instead, some uplink control block (e.g. packet measurement report, packet uplink dummy control block) may be sent by the mobile station. + +The network may indicate in the next PACKET UPLINK ASSIGNMENT message a request for retransmission of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message (see 3GPP TS 44.060). + +If the mobile station receives the IMMEDIATE ASSIGNMENT message before the TBF starting time has expired, it shall wait until the block period indicated by the TBF starting time. The network shall use the TBF starting time to indicate the first frame number belonging to the multi block period granted for packet access. If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, a failure has occurred. + +If a failure occurs and the packet access attempt was due to a request from upper layers to transfer a LLC PDU, a TBF establishment failure has occurred and the mobile station proceeds as specified in sub-clause 3.5.2.1.5. If a failure occurs and the packet access attempt was due to the sending of an RLC/MAC control message, the packet access is aborted, the mobile station returns to packet idle mode. + +#### 3.5.2.1.3.4 Packet access rejection + +The network may send to the mobile station an IMMEDIATE ASSIGNMENT REJECT message in unacknowledged mode on the same CCCH timeslot on which the channel request message was received. There is no further restriction on what part of the downlink CCCH timeslot an IMMEDIATE ASSIGNMENT REJECT message can be sent. This message contains the request reference and a wait indication. + +On receipt of an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its 3 last CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages or EC PACKET CHANNEL REQUEST messages, the mobile station stops sending CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST messages, starts timer T3142 with the indicated value, ("wait indication" information element), starts T3146 if it has not already been started, and listens to the downlink CCCH or EC-CCCH until T3146 expires. During this time, additional IMMEDIATE ASSIGNMENT REJECT messages are ignored, but any immediate assignment corresponding to any other of its 3 last CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST messages make the mobile station follow the procedure in sub-clause 3.5.2.1.3.1. If no such immediate assignment is received (i.e. T3146 expires), the mobile station shall abort the packet access procedure, return to packet idle mode and notify higher layers (TBF establishment failure). + +If the purpose of the packet access procedure is to send a PACKET PAUSE message and an IMMEDIATE ASSIGNMENT REJECT message is received, the packet access procedure is aborted. + +If the mobile station has not received responses from the network on all, or in case more than 3 were sent the last 3, of its CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST messages, it shall abort the packet access procedure, immediately return to packet idle mode and notify higher layers. + +The mobile station is not allowed to make a new attempt for packet access in the same cell until T3142 expires, but may attempt packet access in an other cell after successful cell reselection for radio conditions reasons (see 3GPP TS 45.008). The value of the wait indication (i.e. T3142) relates to the cell from which it was received. + +The mobile station may initiate RR connection establishment in the same cell before T3142 has expired, see sub-clause 3.3.1.1.3.2 and subclause 3.3.1. + +### 3.5.2.1.3a Packet immediate assignment (EC-CCCH) + +#### 3.5.2.1.3a.1 On receipt of an EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST message + +On receipt of an EC PACKET CHANNEL REQUEST message on the EC-RACH (see Table 3.5.2.1.2a.1), the network may allocate a temporary flow identity and assign pre-allocated packet uplink resources comprising one or four PDCHs (determined by the uplink coverage class of the mobile station) for an uplink temporary block flow in EC TBF mode. + +When an EC PACKET CHANNEL REQUEST message is transmitted on the EC-RACH it implicitly indicates a request for an uplink EC TBF. Packet uplink resources are assigned to the mobile station in an EC IMMEDIATE ASSIGNMENT TYPE 2 or EC IMMEDIATE ASSIGNMENT TYPE 4 message sent on the same EC-CCCH timeslot on which the network has received the EC PACKET CHANNEL REQUEST message. + +On receipt of an EC IMMEDIATE ASSIGNMENT TYPE 2 or EC IMMEDIATE ASSIGNMENT TYPE 4 message corresponding to its last EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST (see sub-clause 9.1.65) message, the mobile station stops T3146 (if running), stops sending EC PACKET CHANNEL REQUEST or EC MULTILATERATION REQUEST messages, and switches to the assigned PDCH(s). + +The EC IMMEDIATE ASSIGNMENT TYPE 2 or EC IMMEDIATE ASSIGNMENT TYPE 4 message contains: + +- The downlink coverage class used when transmitting the message; +- optionally, an indication of page extension information; +- the 3 random bits of the information field of the EC PACKET CHANNEL REQUEST message and the 10 least significant bits of the frame number of the frame in which the EC PACKET CHANNEL REQUEST message was received; +- the EC\_MA\_NUMBER; +- training sequence code (TSC) information; +- the temporary flow identity; +- the EGPRS modulation and coding scheme for RLC data blocks; +- the power control parameters; +- optionally, the initial timing advance; +- the packet resources used for the uplink TBF which includes the set of pre-allocated uplink resources described by the EC Fixed Uplink Allocation IE; +- an indication of the uplink and downlink coverage class the MS is to use on the assigned packet resources; +- an indication of the quarter hyperframe used to send the EC IMMEDIATE ASSIGNMENT TYPE 2 or EC IMMEDIATE ASSIGNMENT TYPE 4 message. + +The EC\_MA\_NUMBER field of the *EC Packet Channel Description Type 2 IE* (see sub-clause 10.5.2.85) indicates the mobile allocation set to be used for EC operation. + +When the mobile station switches to the assigned PDCH(s), it shall take the power control parameters received in the EC IMMEDIATE ASSIGNMENT TYPE 2 or EC IMMEDIATE ASSIGNMENT TYPE 4 message into account. + +On receipt of an EC IMMEDIATE ASSIGNMENT TYPE 3 message (see sub-clause 9.1.68) corresponding to its last EC MULTILATERATION REQUEST message when the Access Burst method is used (see sub-clause 3.5.2.1.2a), the mobile station stops T3146 (if running), stops sending EC MULTILATERATION REQUEST messages, considers the radio access part of the MTA procedure as successfully completed in the current cell, tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. In this case the EC IMMEDIATE ASSIGNMENT TYPE 3 message contains: + +- The downlink coverage class set according to the uplink coverage class used when transmitting the corresponding EC MULTILATERATION REQUEST message; +- optionally, an indication of page extension information; +- the 8 bit Short ID field included within the corresponding EC MULTILATERATION REQUEST message. + +On receipt of an EC IMMEDIATE ASSIGNMENT TYPE 3 message (see sub-clause 9.1.68) corresponding to its last EC MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 1' (see sub-clause 3.5.2.1.2a), the mobile station stops T3146 (if running), stops sending EC MULTILATERATION REQUEST messages indicating 'Extended Access Burst method – part 1', restarts TT3146 and starts sending EC MULTILATERATION REQUEST messages indicating 'Extended Access Burst method – part 2'. In this case the EC IMMEDIATE ASSIGNMENT TYPE 3 message contains: + +- Downlink coverage class 1; +- optionally, an indication of page extension information; +- the "Random ID Low" parameter included in the corresponding EC MULTILATERATION REQUEST message; +- timing advance information. + +On receipt of an EC IMMEDIATE ASSIGNMENT TYPE 3 message (see sub-clause 9.1.68) corresponding to its last EC MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 2' (see sub-clause 3.5.2.1.2a), the mobile station stops T3146 (if running), stops sending EC MULTILATERATION REQUEST messages indicating 'Extended Access Burst method – part 2', considers the radio access part of the MTA procedure as successfully completed in the current cell, tunes to the next cell in the list of applicable cells and performs the radio access part of the MTA procedure therein. In this case the EC IMMEDIATE ASSIGNMENT TYPE 3 message contains: + +- Downlink coverage class 1; +- optionally, an indication of page extension information; +- the "Random ID" parameter (derived from the "Random ID Low" parameter included in the first EC MULTILATERATION REQUEST message and the "Random ID High" parameter included in the second EC MULTILATERATION REQUEST message). + +### 3.5.2.1.3a.2 Packet access rejection + +The network may send to the mobile station an EC IMMEDIATE ASSIGNMENT REJECT message in unacknowledged mode on the same EC-CCCH timeslot on which the EC PACKET CHANNEL REQUEST message was received. There is no further restriction on what part of the downlink EC-CCCH timeslot an EC IMMEDIATE ASSIGNMENT REJECT message can be sent. This message contains the EC Request Reference and EC Wait Timer information. + +On receipt of an EC IMMEDIATE ASSIGNMENT REJECT message corresponding to its last EC PACKET CHANNEL REQUEST message, the mobile station stops sending EC PACKET CHANNEL REQUEST messages, starts timer T3142 with the indicated value, (determined by the corresponding "EC Wait Timer" field), starts T3146 if it has not already been started, and listens to the downlink EC-CCCH until T3146 expires. During this time, additional EC IMMEDIATE ASSIGNMENT REJECT messages are ignored, but upon reception of any immediate assignment corresponding to its last EC PACKET CHANNEL REQUEST message it switches to the assigned PDCH(s) as + +described in sub-clause 3.5.2.1.3a. If no such immediate assignment is received (i.e. T3146 expires), the mobile station aborts the packet access procedure, returns to packet idle mode and notifies higher layers (TBF establishment failure). + +The mobile station is not allowed to make a new attempt for packet access in the same cell until T3142 expires, but may attempt packet access in another cell after successful cell reselection for radio conditions reasons (see 3GPP TS 45.008). The value of the EC Wait Timer field (i.e. T3142) relates to the cell from which it was received. + +The mobile station may initiate RR connection establishment in the same cell before T3142 has expired, see sub-clause 3.3.1. + +#### 3.5.2.1.4 Packet access completion + +The one phase packet access procedure is completed at a successful contention resolution. The mobile station has entered the packet transfer mode. Timer T3141 is stopped on the network side. Timer T3164 is stopped on the mobile station side. + +##### 3.5.2.1.4a Packet access completion (EC-CCCH) + +The packet access procedure is completed at a successful contention resolution. The mobile station has entered the packet transfer mode. Timer T3141 is stopped on the network side. Timer T3164 is stopped on the mobile station side. + +##### 3.5.2.1.5 Abnormal cases + +If a failure occurs on the mobile station side before a successful contention resolution procedure is completed, the allocated temporary block flow is released; the mobile station returns to packet idle mode, upper layers are notified (TBF establishment failure), transactions in progress are aborted: + +- If a TLLI mismatch has occurred during the contention resolution procedure, and the repetition of the packet access has been repeated the maximum number of times as defined in 3GPP TS 44.060, a TBF establishment failure has occurred. +- If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT or the second IMMEDIATE ASSIGNMENT message of a two-message assignment, does not satisfactorily define a PDCH, a TBF establishment failure has occurred. +- If the information available in the mobile station, after the reception of an EC IMMEDIATE ASSIGNMENT TYPE 1 message indicates a starting uplink timeslot other than timeslot 0, 1, 2, 3 or 4 for a mobile station using CC2, CC3 or CC4 on the uplink, a TBF establishment failure has occurred. +- If the mobile allocation indexes frequencies in more than one frequency band then a TBF establishment failure has occurred. +- If an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT or EC IMMEDIATE ASSIGNMENT TYPE 1 message indicates a PDCH in a non-supported frequency band then a TBF establishment failure has occurred. + +On the network side, if timer T3141 elapses before a successful contention resolution procedure is completed, the newly allocated temporary block flow is released as specified in 3GPP TS 44.060 and the packet access is forgotten. + +### 3.5.2.1.5a Abnormal cases (EC-CCCH) + +If a failure occurs on the mobile station side before a successful contention resolution procedure is completed, the allocated temporary block flow is released; the mobile station returns to packet idle mode, upper layers are notified (TBF establishment failure), and transactions in progress are aborted: + +- If a TLLI mismatch has occurred during the contention resolution procedure, and the EC PACKET CHANNEL REQUEST message has been sent the maximum number of times as defined by the "EC\_Max\_Retrans" field broadcast in EC SYSTEM INFORMATION TYPE 2 message, a TBF establishment failure has occurred. +- If the information available in the mobile station, after the reception of an EC IMMEDIATE ASSIGNMENT TYPE 2 or EC IMMEDIATE ASSIGNMENT TYPE 4 message indicates a starting uplink timeslot other than timeslot 0, 1, 2, 3 or 4 for a mobile station using CC2, CC3 or CC4 on the uplink, a TBF establishment failure has occurred. +- The EC\_MA\_NUMBER field of the *EC Packet Channel Description Type 2 IE* (see sub-clause 10.5.2.85) indicates an EC Mobile Allocation set for which resources are not defined (according to the EC SYSTEM INFORMATION TYPE 1 message) then a TBF establishment failure has occurred. +- If an EC IMMEDIATE ASSIGNMENT TYPE 2 or EC IMMEDIATE ASSIGNMENT TYPE 4 message indicates a PDCH in a non-supported frequency band then a TBF establishment failure has occurred. + +On the network side, if timer T3141 elapses before a successful contention resolution procedure is completed, the newly allocated temporary block flow is released as specified in 3GPP TS 44.060 and the packet access is forgotten. + +3.5.2.1.6 (void) + +### 3.5.2.2 Sending an RLC/MAC control message: single block packet access procedure + +The sending of an RLC/MAC control message other than the PACKET RESOURCE REQUEST message from a mobile station in packet idle mode to the network may be initiated by the RR entity on the mobile station side using the packet access procedure. If access to the network is allowed (sub-clause 3.5.2.1.1), the packet access is done according to the procedures defined in sub-clauses 3.5.2.1.2 and 3.5.2.1.3, using the single block packet access option defined in sub-clause 3.5.2.1.3.3. + +Further action depends on the RLC/MAC control message sent by the mobile station, see 3GPP TS 44.060. Unless otherwise indicated by the RLC/MAC control message, the mobile station remains in packet idle mode. + +## 3.5.2a Packet access procedure using EC-CCCH + +The packet access procedure using EC-CCCH may be used to establish a temporary block flow to support the transfer of LLC PDUs in the direction from the mobile station to the network. + +If EC operation is enabled a MS that supports GPRS services using GPRS/EGPRS TBFs may choose to disable EC operation in the serving cell in which case the MS shall perform packet access as described in sub-clause 3.5.2. Similarly, an EC capable mobile station that reselects from a cell that does not support EC-GSM-IoT to a cell that supports EC-GSM-IoT may choose to not enable EC operation in which case it shall perform packet access as described in sub-clause 3.5.2. If EC operation is enabled and a MS performs reselection to a cell that does not support EC-GSM-IoT then it shall perform packet access as described in sub-clause 3.5.2. + +A mobile station in EC operation enables PLMN specific access barring upon reading EC\_Access\_Control\_Class and Exception\_Report\_Status information corresponding to its selected PLMN within the EC SYSTEM INFORMATION TYPE 2 message or EC SYSTEM INFORMATION TYPE 4 message. The mobile station disables PLMN specific access barring upon reading an EC SYSTEM INFORMATION TYPE 2 message or EC SYSTEM INFORMATION TYPE 4 message for which EC\_Access\_Control\_Class and Exception\_Report\_Status information is not included for its selected PLMN. While PLMN specific access barring is enabled for its selected PLMN the mobile station shall perform an EC-GSM-IoT preliminary access barring check before accessing the network (see sub-clause 3.5.2a.1) unless it is attempting system access to perform the Multilateration Timing Advance (MTA) procedure (see sub-clause 3.11 and 3GPP TS 44.031). If the preliminary access barring check is performed and indicates network access is barred then access to the network is not allowed. Otherwise, the mobile station proceeds as described in the remainder of this sub-clause. + +A mobile station that is accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008 [79]) and is not sending an exception report (see sub-clause 9.1.65) and is not accessing the network to perform the Multilayer Timing Advance (MTA) procedure (see sub-clause 3.11 and 3GPP TS 44.031), shall read the *Implicit Reject Status* (IRS) field, *EC-BCCH CHANGE MARK* field and *RACH Access Control* field sent in the EC-SCH INFORMATION message (see Figure 9.1.30c.1 and 3GPP TS 45.002) prior to accessing the network. If a change of *EC-BCCH CHANGE MARK* is detected it shall read one or more EC-SYSTEM INFORMATION messages as needed (see sub-clause 3.10.4). The MS then proceeds as follows: + +- If the IRS field indicates the access attempt is rejected the mobile station shall abort the packet access procedure and initiate the EC Implicit Reject procedure (see sub-clause 3.5.2a.2). +- If the IRS field indicates the access attempt is not rejected, the *RACH Access Control* field indicates that RACH usage on timeslot number 0 is not allowed it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a. +- If the IRS field indicates the access attempt is not rejected, the *RACH Access Control* field indicates that RACH usage on timeslot number 0 is allowed and the mobile station has selected CC1 in both uplink and downlink, see 3GPP TS 45.008 [34], it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2. +- If the IRS field indicates the access attempt is not rejected and the mobile station has selected CC2, CC3 or CC4 in the uplink and/or downlink (see 3GPP TS 45.008 [34]) then it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a. + +A mobile station that is accessing the network when the low priority indicator is set to "MS is not configured for NAS signalling low priority" or is sending an exception report when the low priority indicator is set to "MS is configured to NAS signalling low priority" and is configured for dual priority (see 3GPP TS 24.008[79]) or is accessing the network to perform the radio access part of a MTA procedure, shall examine the *EC-BCCH CHANGE MARK* field and *RACH Access Control* field sent in the EC-SCH INFORMATION message. If a change of *EC-BCCH CHANGE MARK* is detected it shall read one or more EC SYSTEM INFORMATION messages as needed (see clause 3.10.4) and then proceed as follows: + +- If the *RACH Access Control* field indicates that RACH usage is allowed and the mobile station has selected CC1 in both the uplink and downlink it shall proceed with the packet access procedure using the RACH on timeslot 0 (see sub-clause 3.5.2.1.2). +- Otherwise, it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a. + +### 3.5.2a.1 EC-GSM-IoT Preliminary Access Barring Check + +The EC-GSM-IoT preliminary access barring check shall indicate network access is barred for a MS that has enabled EC operation if any of the following conditions are satisfied: + +- A MS that is a member of an Access Class in the range 0-9 and is attempting to send a normal report (see sub-clause 9.1.65) shall read the corresponding AC0 to AC9 bit in the *EC\_Access\_Control\_Class* field sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell). The MS determines it is not authorized based on the current value of the AC0 to AC9 bit. +- A MS that is a member of an Access Class in the range 0-9 and is attempting to send an exception report (see sub-clause 9.1.65) shall read the corresponding *Exception\_Report\_Status* field sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell). The MS determines it is not authorized based on the current value of the *Exception\_Report\_Status* bit. +- A MS that is a member of one or more of a special Access Class in the range 11-15 and is attempting to send a normal report or an exception report shall read the corresponding AC11 to AC15 bit in the *EC\_Access\_Control\_Class* field corresponding to its special Access Class sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell). The MS determines it is not authorized based on the current value of the AC11 to AC15 bit. + +If none of the conditions above are fulfilled, the EC-GSM-IoT preliminary access barring check shall indicate network access is not barred. + +### 3.5.2a.2 EC-GSM-IoT Implicit Reject procedure + +A mobile station for which timer T3146 is running shall proceed as follows: + +- While T3146 is running, the mobile station listens to the downlink EC-CCCH for a response from the network and is not allowed to make a new access attempt. +- If a response corresponding to its last transmitted EC PACKET CHANNEL REQUEST messages is received the mobile station shall stop T3146 and act on that message as described in sub-clause 3.5.2.1.3. +- If T3146 expires the mobile station proceeds according to the remainder of this sub-clause. + +The mobile station initiates timer T3236, returns to idle mode and monitors the EC-CCCH. The mobile station is not allowed to make a mobile originated access attempt in the same cell until T3236 expires or is stopped unless it is accessing the network when the low priority indicator is set to "MS is not configured for NAS signalling low priority" or is sending an exception report when the low priority indicator is set to "MS is configured to NAS signalling low priority" and is configured for dual priority (see 3GPP TS 24.008[79]). + +If the mobile station receives an EC PAGING REQUEST message while T3236 is running it shall stop T3236 and respond to the EC PAGING REQUEST message. + +## 3.5.3 Packet downlink assignment procedure using CCCH + +The packet downlink assignment procedure using CCCH may be used to establish a temporary block flow to support the transfer of LLC PDUs in the direction from the network to the mobile station. + +This procedure may also be used to assign a single downlink block on a PDCH to support the transfer of an RLC/MAC control message from the network to a mobile station in packet idle mode, see sub-clause 3.5.3.2. + +### 3.5.3.1 Entering the packet transfer mode: packet downlink assignment procedure + +The establishment of a downlink temporary block flow may be initiated by the RR entity on the network side using the packet downlink assignment procedure. The procedure is triggered by a request from upper layers to transfer a LLC PDU, see 3GPP TS 24.007. The request from upper layers specifies an optional *Priority* level, a QoS profile including the requested *RLC mode*, optional *DRX parameters*, and optional *IMSI* and an optional *MS Radio Access Capability* associated with the packet transfer. The BSS may order its preferred RLC mode independently of the RLC mode signalled from upper layers. If the mobile station supports RLC non-persistent mode the network may allocate an EGPRS TBF that uses this RLC mode. + +Upon such a request, the network shall determine whether the mobile station is in packet idle mode or packet transfer mode. The packet downlink assignment procedure using CCCH is applicable when the mobile station is in packet idle mode and when there is no PCCCH present in the cell. + +The network may allocate a temporary flow identity and assign a packet downlink resource comprising one PDCH for a downlink temporary block flow. + +#### 3.5.3.1.2 Initiation of the packet downlink assignment procedure + +The network initiates the packet downlink assignment procedure by sending an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message (if supported) in unacknowledged mode on the CCCH timeslot corresponding to CCCH group the mobile station belongs to. The appropriate CCCH group is calculated from the IMSI, see 3GPP TS 45.002. The behaviour of the network when the RR entity does not receive the IMSI from the upper layers is implementation dependent for the calculation of the CCCH group where the IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message has to be sent. If the mobile station is in non-DRX mode or if the RR entity does not receive the IMSI or the DRX parameters from the upper layers, there is no further restriction on what part of the downlink CCCH timeslot the IMMEDIATE ASSIGNMENT, or IMMEDIATE PACKET ASSIGNMENT message, or the first part of the IMMEDIATE ASSIGNMENT message (in the case of a two-message assignment), can be sent. If the mobile station applies DRX, the IMMEDIATE ASSIGNMENT, or IMMEDIATE PACKET ASSIGNMENT message, or the first part of the IMMEDIATE ASSIGNMENT message (in the case of a two-message assignment), shall be sent in a CCCH block corresponding to a paging group determined for the mobile station in packet idle mode, see 3GPP TS 45.002. If the mobile station has negotiated the use of eDRX, the IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message shall be sent in a CCCH block corresponding to a paging group determined for the mobile station in packet idle mode according to the lowest eDRX cycle, see 3GPP TS 45.002. + +The IMMEDIATE ASSIGNMENT message contains: + +- the packet channel description; +- the initial timing advance; +- the packet downlink assignment construction. + +The contents of the packet downlink assignment construction determines the further action. At the establishment of a downlink temporary block flow, the packet downlink assignment construction shall contain: + +- the TLLI; +- the temporary flow identity; +- the RLC mode; +- the power control parameters; +- the polling bit; +- the initial timing advance validity flag; +- optionally, EGPRS Window Size (see 3GPP TS 44.060) and Link Quality Measurement Mode (see 3GPP TS 44.060); +- optionally, the timing advance index (see 3GPP TS 45.010); +- optionally, the TBF starting time; +- optionally, the NPM Transfer Time (see 3GPP TS 44.060); +- optionally, the Event-Based FANR indication (see 3GPP TS 44.060); +- optionally, the TTI Configuration (see 3GPP TS 44.060). + +At the establishment of a downlink temporary block flow for MS supporting IMMEDIATE PACKET ASSIGNMENT message, the *IPA Downlink Assignment struct* sent in IMMEDIATE PACKET ASSIGNMENT message may assign packet downlink resources for multiple mobile stations and contains the following parameters specific to different mobile stations: + +- the TLLI; +- the temporary flow identity; +- the power control parameters; +- optionally, the timing advance value. + +In addition, the *IPA Downlink Assignment struct* also contains the following parameters which are common to all mobile stations addressed in this structure: + +- the timeslot number; +- optionally the link quality measurement mode; +- the RLC mode; +- the frequency parameters; + +Relevant default values shall be used for the RLC window size and Alpha parameters as specified in in subclause 10.5.2.78. + +If frequency hopping is applied, the network may use the indirect encoding or the direct encoding of the frequency configuration in the *Packet Channel Description* information element in IMMEDIATE ASSIGNMENT message or in *IPA Downlink Assignment struct* in IMMEDIATE PACKET ASSIGNMENT message. If the indirect encoding is used, the mobile station uses information received in system information or stored from a previous assignment to determine + +the frequency parameters, see 3GPP TS 44.060. If the direct encoding is used, the mobile station uses the cell allocation defined for the cell to decode the mobile allocation. + +If the BSS receives a DL-UNITDATA PDU that includes eDRX information but excludes coverage class information (i.e. the corresponding mobile station has enabled PEO) and that indicates timing advance information is needed (see 3GPP TS 48.018) it sends an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message to the mobile station that indicates timing advance information is needed (see sub-clause 10.5.2.16 and sub-clause 10.5.2.78). + +If the *indirect encoding* is used, the IMMEDIATE ASSIGNMENT or the IMMEDIATE PACKET ASSIGNMENT message may contain a CHANGE\_MARK\_1 field. If that is present, the mobile station shall verify the validity of the SI *change mark* associated with the GPRS mobile allocation to which the message refers, see 3GPP TS 44.060. If the CHANGE\_MARK\_1 field and the SI *change mark* do not match, the message does not satisfactorily define a PDCH. + +If the mobile station receives an IMMEDIATE ASSIGNMENT message and the *Dedicated mode or TBF* information element indicates that this is the first message in a two-message assignment, the mobile station shall start listen to the full CCCH. The network may send a second IMMEDIATE ASSIGNMENT message to the mobile station within two multiframe periods following the first IMMEDIATE ASSIGNMENT message, specifying the packet channel description and, if required, a mobile allocation for the assignment. The two IMMEDIATE ASSIGNMENT messages in a two-message assignment shall have the same contents of the *Request Reference* information elements. + +If the mobile station was operating in DRX mode when it received the first message of a two-message assignment, the network shall not send the second IMMEDIATE ASSIGNMENT message within the two block periods immediately following the first message. + +If the mobile station does not receive the second IMMEDIATE ASSIGNMENT messages in a two-message assignment within two multiframe periods following the first message, the mobile station shall discard the first IMMEDIATE ASSIGNMENT message received. After the two multiframe periods following the first message, the mobile station may resume to DRX mode. + +On receipt of an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message or, in case of a two-message assignment, a matching pair of IMMEDIATE ASSIGNMENT messages, the mobile station stops monitoring downlink CCCH and switches to the assigned PDCH and starts listening for downlink RLC/MAC blocks identified by the assigned TFI; it starts timer T3190. + +The IMMEDIATE ASSIGNMENT message may indicate a TBF starting time. If the mobile station receives the message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time, start timer T3190 and switch to the assigned PDCH. If the mobile station receives the message after the TBF starting time has expired, it shall ignore the indicated TBF starting time, immediately start timer T3190 and switch to the assigned PDCH. + +When the mobile station switches to the assigned PDCH, it shall take the power control parameters received in the IMMEDIATE ASSIGNMENT or the IMMEDIATE PACKET ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode, see 3GPP TS 45.008. + +If the Polling bit is set to 1, MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message (see 44.060) on the assigned PDCH, in the uplink block specified by the TBF Starting Time. In this case the TBF Starting Time is used both to indicate when the assigned PDCH becomes valid and to specify the uplink block. If the TBF Starting Time is not present or has expired, the MS shall ignore the polling request. + +An IMMEDIATE ASSIGNMENT message may indicate a timing advance index (TAI) in the packet timing advance IE. The mobile station shall then use the continuous update timing advance mechanism, see 3GPP TS 45.010, using PTCCH in the same timeslot as the assigned PDCH. If there is no indication of a timing advance index, the continuous update timing advance mechanism shall not be used. + +The TA\_VALID flag indicates if the value of the *Timing Advance* IE is valid or not. + +If the network does not have a valid timing advance value for the mobile station to include in the IMMEDIATE ASSIGNMENT or the IMMEDIATE PACKET ASSIGNMENT message, the network shall use the procedures defined in 3GPP TS 44.060 on the assigned TBF, or the polling mechanism defined in the above paragraph if the PACKET CONTROL ACKNOWLEDGEMENT format is set to four access bursts, to obtain a timing advance value and to update the initially assigned timing advance value before the mobile station is required to transmit other than access burst on the newly assigned channel. + +The packet downlink construction may optionally contain the EGPRS Window Size (see 3GPP TS 44.060) and Link Quality Measurement Mode (see 3GPP TS 44.060). The presence of these fields indicates EGPRS TBF mode (see 3GPP TS 44.060). If these fields are not present, this indicates GPRS TBF mode. + +### 3.5.3.1.3 Packet downlink assignment completion + +After having sent the packet downlink assignment, the network starts sending downlink RLC/MAC blocks on the assigned packet downlink resource and the packet downlink assignment procedure is completed at the network side. + +On the mobile station side, the procedure is completed when the mobile station receives an RLC/MAC block identified by the assigned temporary flow identity. The mobile station stops timer T3190. The mobile station has entered packet transfer mode. + +### 3.5.3.1.4 Abnormal cases + +If a failure occurs on the mobile station side before the packet downlink assignment procedure is completed (TBF establishment failure), the temporary block flow is released; the mobile station returns to packet idle mode: + +- If the mobile station does not receive a RLC/MAC block on the assigned PDCHs before timer T3190 expires, then a TBF establishment failure has occurred. +- If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message or the second IMMEDIATE ASSIGNMENT message of a two-message assignment, does not satisfactorily define a PDCH, then a TBF establishment failure has occurred. +- If the mobile allocation in the frequency parameters indexes frequencies in more than one frequency band, then a TBF establishment failure has occurred. + +If an IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message indicates a PDCH in a non-supported frequency band, then a TBF establishment failure has occurred. + +### 3.5.3.2 Sending an RLC/MAC control message: single block packet downlink assignment procedure + +The sending of an RLC/MAC control message to a mobile station in packet idle mode may be initiated by the RR entity on network side using the packet downlink assignment procedure. The procedure is used to assign a single downlink block on a PDCH for the transfer of the RLC/MAC control message. Using this procedure, the network shall not apply segmentation of the RLC/MAC control message. + +The single downlink block assignment is done according to the procedure defined in sub-clause 3.5.3.1.2, with the following exceptions: + +The packet downlink assignment construction in the IMMEDIATE ASSIGNMENT message shall contain only: + +- the TLLI; and +- the TBF starting time. + +If the mobile station receives the IMMEDIATE ASSIGNMENT message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time. The network shall use the TBF starting time to indicate the first frame number belonging to the single block period assigned to the mobile station. The mobile station shall switch to the assigned PDCH and attempt to decode an RLC/MAC control message in the assigned downlink block. Further action depends on the RLC/MAC control message sent by the network, see 3GPP TS 44.060. Unless otherwise indicated by the RLC/MAC control message, the mobile station remains in packet idle mode. If the mobile station remains in packet idle mode, it shall continue to monitor downlink CCCH once the block period indicated by the TBF starting time has passed. + +If the mobile station fails to decode or does not receive an RLC/MAC control message in the assigned downlink block, it shall remain in packet idle mode and continue to monitor downlink CCCH once the block period indicated by the TBF starting time has passed. + +If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, it shall ignore the assignment. + +If a failure occurs on the mobile station side due to any other reason, the mobile station shall ignore the assignment. + +### 3.5.3.2a Sending an RLC/MAC control message: multiple blocks packet downlink assignment procedure + +The sending of an RLC/MAC control message to a mobile station in packet idle mode may be initiated by the RR entity on network side using the packet downlink assignment procedure. The procedure is used to assign multiple downlink blocks on a PDCH for the transfer of the RLC/MAC control message. Using this procedure, the network may apply segmentation of the RLC/MAC control message. + +The multiple downlink blocks assignment is done according to the procedure defined in sub-clause 3.5.3.1.2, with the following exceptions: + +The multiple blocks packet downlink assignment construction in the IMMEDIATE ASSIGNMENT message shall contain only: + +- the TBF starting time; +- the number of allocated blocks; +- optionally, the TMGI; +- optionally, the MBMS session identity; +- optionally, the TLLI / G-RNTI; +- optionally, the MS\_ID and packet timing advance parameters. + +If the message contains the TLLI / G-RNTI not addressing the mobile station, the message shall be ignored. + +If the mobile station receives the IMMEDIATE ASSIGNMENT message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time. The network shall use the TBF starting time to indicate the first frame number belonging to the multiple block period assigned to the mobile station. The mobile station shall switch to the assigned PDCH and attempt to decode an RLC/MAC control message in the assigned downlink block(s). Further action depends on the RLC/MAC control message sent by the network, see 3GPP TS 44.060. Unless otherwise indicated by the RLC/MAC control message, the mobile station remains in packet idle mode. If the mobile station remains in packet idle mode, it shall continue to monitor downlink CCCH. + +If the mobile station fails to decode or does not receive an RLC/MAC control message in the assigned downlink block(s), it shall remain in packet idle mode and continue to monitor downlink CCCH. + +If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, it shall ignore the assignment. + +If a failure occurs on the mobile station side due to any other reason, the mobile station shall ignore the assignment. + +## 3.5.4 MBMS packet access procedure using CCCH + +### 3.5.4.1 General + +If access to the network is allowed (sub-clause 3.5.2.1.1), the MBMS packet access is done according to the procedures defined in sub-clauses 3.5.2.1.2 and 3.5.2.1.3, using the single block MBMS access option. + +The initiation of the MBMS packet access procedure is defined in 3GPP TS 44.060. + +A mobile station shall continue to monitor its paging subchannel on CCCH for PAGING REQUEST messages indicating an establishment of RR connection or a packet paging procedure during the MBMS packet access procedure. A mobile station shall abort the MBMS packet access procedure at the receipt of a PAGING REQUEST message indicating an establishment of RR connection or a packet paging procedure. + +### 3.5.4.2 On receipt of a CHANNEL REQUEST message + +On receipt of a CHANNEL REQUEST message with access type indicating "Single block MBMS access", the network shall grant only the single block period on the assigned packet uplink resource if the network allocates resource for the mobile station. + +The packet uplink resource is assigned to the mobile station in an IMMEDIATE ASSIGNMENT message sent in unacknowledged mode on the same CCCH timeslot on which the network has received the CHANNEL REQUEST message. The packet uplink resource description shall contain: + +- the power control parameter setting; +- the TBF starting time. + +If uplink resources are not available, the network may reject the access request by sending a IMMEDIATE ASSIGNMENT REJECT message (see sub-clause 3.5.4.4). + +### 3.5.4.3 On receipt of an IMMEDIATE ASSIGNMENT message + +If the mobile station receives the IMMEDIATE ASSIGNMENT message or, in case of a two-message assignment, a matching pair of IMMEDIATE ASSIGNMENT messages corresponding to one of its 3 last CHANNEL REQUEST messages, before the TBF starting time has expired, the mobile station shall wait until the block period indicated by the TBF starting time. The network shall use the TBF starting time to indicate the first frame number belonging to the single block period granted for packet access. The mobile station may use the assigned block period to send an MBMS SERVICE REQUEST message, as defined in 3GPP TS 44.060. + +If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, a failure has occurred and the mobile station proceeds as specified in sub-clause 3.5.4.6. + +While timer T3214 is running the mobile shall accept reception of repeated IMMEDIATE ASSIGNMENT messages, on the same CCCH timeslot on which the mobile station has sent the CHANNEL REQUEST message, and re-send the MBMS SERVICE REQUEST message, as defined in 3GPP TS 44.060. + +### 3.5.4.4 On receipt of an IMMEDIATE ASSIGNMENT REJECT message + +The network may send an IMMEDIATE ASSIGNMENT REJECT message to the mobile station in response to the CHANNEL REQUEST message. The mobile station shall then react according to the description in sub-clause 3.3.1.1.3.2. + +### 3.5.4.5 On receipt of an MBMS ASSIGNMENT message + +The MBMS assignment procedure using CCCH may be used in order to assign the radio bearer resources for an MBMS session in the cell or to notify the mobile station(s) that a radio bearer for that MBMS session is not established in the cell. + +The assignment for the MBMS session is done by using the multiple blocks packet downlink assignment procedure (non-distribution or distribution MBMS assignment) as specified in the sub-clause 3.5.3.2a. + +When the mobile station receives an MBMS ASSIGNMENT message for an MBMS session, it shall stop any ongoing packet access procedure for that MBMS session and proceed as defined in 3GPP TS 44.060. + +### 3.5.4.6 Abnormal cases + +If the mobile station receives an IMMEDIATE ASSIGNMENT message that contains faulty parameters, the mobile station shall abort the MBMS access procedure. + +## 3.5.5 Packet downlink assignment procedure using EC-CCCH + +The packet downlink assignment procedure using EC-CCCH may be used to establish a temporary block flow to support the transfer of LLC PDUs in the direction from the network to the mobile station when the mobile station has enabled EC operation. + +### 3.5.5.1 Entering the packet transfer mode: packet downlink assignment procedure + +The establishment of a downlink temporary block flow may be initiated by the RR entity on the network side using the packet downlink assignment procedure. The procedure is triggered by a request from upper layers to transfer a LLC PDU, see 3GPP TS 24.007. The request from upper layers specifies an optional *Priority* level, eDRX cycle, a downlink coverage class, P-TMSI, IMSI and an optional *MS Radio Access Capability* associated with the packet transfer. + +Upon such a request, the network shall determine whether the mobile station is in packet idle mode or packet transfer mode. The packet downlink assignment procedure using EC-CCCH is applicable when the mobile station is in packet idle mode and the corresponding Ready timer is running. + +The network may allocate a temporary flow identity and assign a packet downlink resource comprising one PDCH (for a mobile station using CC1 on the downlink) or 4 PDCHs (for a mobile station using CC2, CC3 or CC4 on the downlink) for a downlink temporary block flow. The uplink EC-PACCH corresponding to the downlink temporary block flow is also assigned by the network, comprising one PDCH (when CC1 assigned on the uplink) or 4 PDCHs (when CC2, CC3 or CC4 assigned on the uplink). + +### 3.5.5.2 Initiation of the packet downlink assignment procedure + +When the Ready timer is running the network initiates the packet downlink assignment procedure by sending an EC DOWNLINK ASSIGNMENT message (see sub-clause 9.1.64) or EC DOWNLINK ASSIGNMENT TYPE 2 (see sub-clause 9.1.67) in unacknowledged mode using the paging group determined using IMSI, the lowest eDRX cycle and the downlink coverage class of the mobile station (see 3GPP TS 45.002). The downlink coverage class information last transmitted to the network for a given mobile station is provided to the BSS in a DL-UNITDATA PDU (see 3GPP TS 48.018 [107]) sent for that mobile station. + +The EC DOWNLINK ASSIGNMENT message or EC DOWNLINK ASSIGNMENT TYPE 2 contains: + +- the temporary flow identity; +- the EGPRS modulation and coding scheme for RLC data blocks; +- the power control parameters; +- optionally, the initial timing advance; +- the packet resources used for the downlink TBF; +- the downlink Coverage Class used to send the message; +- the EC\_MA\_NUMBER; +- an indication of the uplink and downlink coverage class the MS is to use on the assigned packet resources; +- an indication of the quarter hyperframe used to send the EC DOWNLINK ASSIGNMENT message. + +The EC\_MA\_NUMBER field of the *EC Packet Channel Description Type 2* IE (see sub-clause 10.5.2.85) indicates the mobile allocation to be used. + +When a BSS receives a DL-UNITDATA PDU that includes both Coverage Class and eDRX information it sends an assignment message on the EC-AGCH (associated with the EC-PCH of its EC\_CCCH\_GROUP) using the indicated downlink Coverage Class and the lowest eDRX cycle (see 3GPP TS 45.002 [48]). + +When a BSS receives a DL-UNITDATA PDU that does not include Coverage Class information but includes eDRX information it sends an assignment message on the AGCH (associated with the PCH of its CCCH\_GROUP) using the lowest eDRX cycle (see 3GPP TS 45.002 [48]). + +If the BSS receives a DL-UNITDATA PDU that includes coverage class information (i.e. the corresponding mobile station has enabled EC-GSM-IoT operation) and that indicates timing advance information is needed (see 3GPP TS 48.018) it sends an EC DOWNLINK ASSIGNMENT message to the mobile station that includes this indication (see sub-clause 9.1.64). + +On receipt of an EC DOWNLINK ASSIGNMENT message (see sub-clause 9.1.64) or EC DOWNLINK ASSIGNMENT TYPE 2 message the mobile station stops monitoring downlink EC-CCCH, switches to the assigned PDCH(s), starts listening for downlink RLC/MAC blocks identified by the assigned TFI and starts timer T3190. See 3GPP TS 45.010 [35] for mobile station reaction time requirements applicable to receiving an assignment message. + +When the mobile station switches to the assigned PDCH(s), it shall take the power control parameters received in the EC DOWNLINK ASSIGNMENT or EC DOWNLINK ASSIGNMENT TYPE 2 message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode, see 3GPP TS 45.008. + +### 3.5.5.3 Packet downlink assignment completion + +After having sent the packet downlink assignment, the network starts sending downlink RLC/MAC blocks on the assigned packet downlink resource and the packet downlink assignment procedure is completed at the network side. + +On the mobile station side, the procedure is completed when the mobile station receives an RLC/MAC block identified by the assigned temporary flow identity. The mobile station stops timer T3190. The mobile station has entered packet transfer mode. + +### 3.5.5.4 Abnormal cases + +If a failure occurs on the mobile station side before the packet downlink assignment procedure is completed (TBF establishment failure), the temporary block flow is released; the mobile station returns to packet idle mode: + +- If the mobile station does not receive a RLC/MAC block on the assigned PDCHs before timer T3190 expires, then a TBF establishment failure has occurred. +- If the information available in the mobile station, after the reception of an EC DOWNLINK ASSIGNMENT message or EC DOWNLINK ASSIGNMENT TYPE 2, does not satisfactorily define a PDCH, then a TBF establishment failure has occurred. + +## 3.6 RR Procedures in packet transfer mode + +### 3.6.1 RR Connection establishment using enhanced DTM CS establishment + +The initiation of the procedure and the assignment of resources for the establishment of the RR connection are described in 3GPP TS 44.060. + +In respect of the establishment of the RR connection, the mobile station shall act on the starting time information element, if present in an IMMEDIATE ASSIGNMENT message, as specified in sub-clause 3.3.1.1.3.1. + +The establishment of the main signalling link is described in sub-clause 3.1.5. In the case of a network initiated establishment (i.e. not following the sending of a PACKET CS REQUEST message), the layer 2 SABM frame shall contain a PAGING RESPONSE message. Otherwise (i.e. the mobile station has sent a PACKET CS REQUEST message), an appropriate layer 3 service request message shall be sent in the layer 2 SABM frame. + +The completion of the establishment of the RR connection is described in sub-clause 3.6.2. + +### 3.6.2 Completion of RR Connection establishment + +#### 3.6.2.1 Connection established in response to an encapsulated IMMEDIATE ASSIGNMENT message + +The RR connection establishment procedure is terminated on the network side when the main signalling link is established. Timer T3101 is stopped, the MM sublayer on the network side is informed that the RR entity has entered the dedicated mode and the network may release the old packet resources. + +On the mobile station side, the procedure is terminated when the establishment of the main signalling link is confirmed. The MM sublayer is informed that the RR entity has entered the dedicated mode. + +#### 3.6.2.2 Connection established in response to an encapsulated DTM ASSIGNMENT COMMAND message + +For the handling of the packet resources upon reception of the encapsulated DTM ASSIGNMENT COMMAND message the sub-clauses 3.4.23.2.2 and 3.4.23.2.3 are applicable. + +The RR connection establishment procedure is terminated on the network side when the main signalling link is established. Timer T3107 is stopped, the MM sublayer on the network side is informed that the RR entity has entered the dual transfer mode, and the network may release the old packet resources. + +On the mobile station side, the procedure is terminated when the establishment of the main signalling link is confirmed. The MM sublayer is informed that the RR entity has entered the dual transfer mode. + +## 3.7 DTM Handover procedure + +### 3.7.1 General + +In dual transfer mode an intercell change of dedicated and packet data channel(s) can be requested by the network RR sublayer. This change may be performed using the DTM handover procedure. + +This procedure is optional and is only applicable in dual transfer mode when both the mobile station and the network support DTM handover. The mobile station shall indicate its support for DTM handover in the Mobile Station Classmark 3 IE and the MS Radio Access Capability IE. The purpose of the procedure is to handover the dedicated channel and one or more of the packet resources while in dual transfer mode when a cell is changed. The DTM handover procedure is a combination of the handover procedure for circuit switched handover, defined in sub-clause 3.4.4, and the procedure for packet switched handover, defined in 3GPP TS 44.060. + +NOTE: The decision to initiate a DTM handover and the choice of the new cell is out of the scope of this technical specification. + +The DTM handover procedure is always initiated by the network. + +### 3.7.2 *DTM Handover from GERAN A/Gb mode to GERAN A/Gb mode procedure* + +The DTM handover procedure includes: + +- The suspension of normal operation except for RR management (layer 3). +- The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH. +- The mobile station suspension of the packet resources used in the old cell (see 3GPP TS 44.060) until the MS determines the DTM handover procedure to be successfully completed at which point these packet resources are released. +- The mobile station disconnection and deactivation of the dedicated channel used in the old cell (see 3GPP TS 44.018) until the MS determines the DTM handover procedure to be successfully completed at which point the dedicated channel is released (at layer 1). +- The activation of the new channels, and their connection if applicable. +- The triggering of the establishment of data link connection for SAPI = 0 on the new channels. +- The activation of the new PDCH(s) and the resumption of the packet resources (see 3GPP TS 44.060). + +For the circuit switched domain the requirements and procedures listed in sub-clauses 3.4.4.1, 3.4.4.2 and 3.4.4.3 are valid with the following exceptions: + +- Handover of VGCS is not supported by the DTM handover procedure. +- MBMS service information sending completion is not supported by the DTM handover procedure. +- The DTM HANDOVER COMMAND message applies instead of the HANDOVER COMMAND message and is sent on the PACCH (see 3GPP TS 44.060). +- Sending of DTM Information is not needed. + +For the packet switched domain the requirements and procedures described for PS handover in 3GPP TS 44.060 are valid with the following exceptions: + +- The synchronisation of the physical channels is not performed in the PS domain, i.e. the mobile station shall not send the PS HANDOVER ACCESS message. + +- The target BSS considers the DTM handover procedure to be successfully completed upon receiving a HANDOVER COMPLETE message on the main DCCH according to sub-clause 3.4.4.3. +- Timer T3216 shall not be started for DTM handover. +- The DTM HANDOVER COMMAND message applies instead of the PS HANDOVER COMMAND message. + +### 3.7.2.1 Abnormal cases + +The failure cases and actions defined in sub-clause 3.4.4.4, shall apply for DTM handover from GERAN *A/Gb mode* to GERAN *A/Gb mode* with the following exceptions: + +- The DTM HANDOVER COMMAND message applies instead of the HANDOVER COMMAND message and is sent on the PACCH. + +In addition, a mobile station operating in *A/Gb mode* shall consider the DTM handover to *A/Gb mode* to have failed if the DTM HANDOVER COMMAND message: + +- violates the mobile station's DTM multislot capabilities; or +- does not include at least one uplink TBF; or +- provides one or more downlink TBFs with PFIs that are different from those currently allocated; or +- provides one or more uplink TBFs with PFIs that are different from those currently allocated except when there are no ongoing uplink TBFs in which case a single uplink TBF with a PFI that indicates signalling shall be allocated. + +If these additional error cases occur, the mobile station shall remain in DTM in the old cell and return a HANDOVER FAILURE message on the current main DCCH with the PS Cause IE set as follows: + +- in case a) above, "DTM multislot capabilities violated"; or +- in case b) above, "No uplink TBF"; or +- in case c) above, "Too many TBFs"; or +- in case d) above, "Too many TBFs". + +If there are no errors in the DTM HANDOVER COMMAND message related to the CS domain and there are no common errors then the RR Cause IE shall indicate "Normal Event". Any error that is common to both the CS domain and the PS domain shall be reported in the RR Cause IE. + +The transmission of a HANDOVER FAILURE message terminates the DTM handover procedure in the mobile station. + +After terminating the DTM handover procedure the mobile station shall resume all uplink and downlink TBFs that were ongoing in the old cell prior to receiving the DTM HANDOVER COMMAND message and for which T3180 (uplink TBFs) and T3190 (downlink TBFs) are still running (see 3GPP TS 44.060). + +For each TBF that is resumed the corresponding RLC state machine shall reflect its state when the last RLC data block was transmitted for that TBF in the old cell (uplink TBFs) and the last RLC data block was received for that TBF in the old cell (downlink TBFs) (see 3GPP TS 44.060). + +### 3.7.3 DTM Handover from GERAN A/Gb mode to UTRAN procedure + +For the successful case of DTM Handover from GERAN *A/Gb mode* to UTRAN, the behaviour of the MS in the old cell is as specified for DTM Handover from GERAN *A/Gb mode* to GERAN *A/Gb mode* (see sub-clause 3.7.2). The behaviour of the MS in the new cell is as specified for Inter-RAT Handover to UTRAN in 3GPP TS 25.331. The behaviour of the old BSS is as specified in sub-clause 3.7.2. + +The definition of abnormal cases for the mobile is specified in 3GPP TS 25.331. If the UE/MS receives a HANDOVER TO UTRAN COMMAND message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE (see 3GPP TS 25.331), the MS sends a HANDOVER FAILURE message on the main DCCH to the old cell. The appropriate cause shall be included (see sub-clause 3.4.4a.3). + +The definition of abnormal cases for the old BSS and the behaviour of the old BSS in such cases (including on receipt of a HANDOVER FAILURE) is as specified in sub-clause 3.7.2.1. + +## 3.8 Network sharing + +### 3.8.1 General + +A network supporting network sharing shall broadcast network sharing information indicating the core network operators sharing the Radio Access Network (see sub-clause 3.8.2; + +Additionally, in a cell where network sharing information is broadcast in SYSTEM INFORMATION TYPE 22 message, the network: + +- shall broadcast network sharing information indicating the core network operators sharing the Radio Access Network; +- shall configure the contents of the SYSTEM INFORMATION TYPE 5/5bis/5ter and SYSTEM INFORMATION TYPE 6 messages to indicate the selected PLMN when the mobile station supports network sharing; +- may broadcast domain-specific access control information. Only networks and mobile stations supporting network sharing may support domain-specific access control. +- may broadcast when applicable PLMN-specific UTRAN and/or E-UTRAN information for inter-RAT cell re-selection. + +A mobile station supporting network sharing shall use this information for PLMN (re)selection, cell reselection, E-UTRAN measurement reporting and to determine whether or not access to the network is allowed, possibly on a domain (CS or PS) basis. + +A mobile station that has enabled EC operation shall use the network sharing information (if broadcast in the cell) for PLMN (re-)selection, cell reselection and to determine whether or not access to the network is allowed, see sub-clause 3.8.3.2. + +NOTE: In a network supporting network sharing, a mobile station not supporting network sharing may reselect cells of other RATs not belonging to an equivalent PLMN of the registered PLMN. Setting different priorities for frequencies belonging to different PLMNs but in the same RAT may favour one PLMN over the other in areas shared by these PLMNs. + +### 3.8.2 Network side + +#### 3.8.2.1 Provision of network sharing information + +A cell where network sharing is supported shall broadcast the SYSTEM INFORMATION TYPE 22 message in which it shall indicate: + +- whether or not mobile stations supporting network sharing are allowed to select the Common PLMN; and +- the PLMN ID (MCC and MNC) of up to four Additional PLMNs; and +- the permitted NCCs for cell (re)selection and measurement reporting corresponding to each of the up to four Additional PLMNs. + +Additionally and individually for each of the up to four Additional PLMNs SYSTEM INFORMATION TYPE 22 may indicate the applicable access control information to be used for accessing the network (see sub-clauses 3.3.1.1.1, 3.5.2.1.1). + +The network may also indicate in the SYSTEM INFORMATION TYPE 21 message access control information for EAB used for the preliminary access barring check (see sub-clause 3.3.1.4) individually for each of the up to four Additional PLMNs. + +If domain-specific access control is used for a PLMN (Common PLMN and/or any of the up to four Additional PLMNs), the network shall include the corresponding information in the SYSTEM INFORMATION TYPE 22 message and SYSTEM INFORMATION TYPE 21 message as applicable. + +The network may include PLMN-specific UTRAN and/or E-UTRAN information for inter-RAT cell re-selection purpose in the SYSTEM INFORMATION TYPE 23 message. When the SYSTEM INFORMATION TYPE 23 message is broadcast, the network shall broadcast the UTRAN and/or E-UTRAN information for inter-RAT cell re-selection related to a given PLMN in consecutive instances of the SYSTEM INFORMATION TYPE 23 message. + +NOTE: So as to take into account the monitoring capabilities (see 3GPP TS 45.008) of mobile stations not supporting network sharing, the network may provide updates of the UTRAN/E-UTRAN frequencies lists broadcast within the SI2ter/SI2quater messages that are not applicable to mobile stations supporting network sharing (see sub-clause 3.8.3). + +The network shall use the PLMN index provided by a mobile station supporting network sharing (see sub-clause 3.8.3) to map it upon the list of PLMN IDs it broadcasts in order to derive the PLMN selected by the mobile station and to route the initial access to the appropriate CN node (see subclause 10.3.1 and 3GPP TS 48.008 for the CS domain, see 3GPP TS 48.018 for the PS domain). + +The network shall indicate the selected PLMN when configuring the neighbour cell information included in the SYSTEM INFORMATION TYPE 5/5bis/5ter messages for a mobile station supporting network sharing. + +The network shall indicate the selected PLMN ID when configuring the Location Area Identification IE included in the SYSTEM INFORMATION TYPE 6 message for a mobile station supporting network sharing. Otherwise, it shall configure the Location Area Identification IE to indicate the common PLMN. + +### 3.8.2.2 EC System information broadcasting + +A cell supporting EC-GSM-IoT may broadcast the EC SYSTEM INFORMATION TYPE 4 message in which it shall indicate: + +- whether or not the mobile station in EC operation is allowed to select the Common PLMN; and +- the PLMN ID (MCC and MNC) of up to four Additional PLMNs; and +- the permitted NCCs for cell (re)selection corresponding to each of the up to four Additional PLMNs; and +- whether or not sending of exception reports (see sub-clause 9.1.65) is allowed in each of the four Additional PLMNs. + +Additionally and individually for each of the up to four Additional PLMNs the EC SYSTEM INFORMATION TYPE 4 message may indicate the applicable access control information to be used for accessing the network (see sub-clause 3.5.2a.1). + +The network shall use the PLMN index provided by the mobile station to map it upon the list of PLMN IDs it broadcasts in order to derive the PLMN selected by the mobile station and to route the initial access to the appropriate CN node (see 3GPP TS 48.018). + +### 3.8.3 Mobile station side + +A mobile station supporting network sharing that has not enabled EC operation shall read the SYSTEM INFORMATION TYPE 22 message if broadcast in the cell and acquire the *Network Sharing Information*. + +The mobile station shall use this information to determine the PLMNs available in this cell for (re)selection, the applicable access control information for the selected PLMN and the allowed NCC for measurement reporting and cell reselection (see 3GPP TS 45.008, 3GPP TS 23.003) for the selected PLMN. + +A mobile station that has enabled EC operation shall read the EC SYSTEM INFORMATION TYPE 4 message if broadcast in the cell and acquire the *Network Sharing Information* therein. The mobile station shall use this information to determine the PLMNs available in the cell for (re)selection, the applicable access control information for the selected PLMN and the allowed NCC for cell reselection (see 3GPP TS 45.008 [34], 3GPP TS 23.003) for the selected PLMN. + +The mobile station shall consider the Common PLMN (only if the Common PLMN is indicated as allowed in the SYSTEM INFORMATION TYPE 22 message or in the EC SYSTEM INFORMATION TYPE 4 message) and each indicated Additional PLMN in its PLMN selection process as specified in 3GPP TS 23.122. + +Once a PLMN is selected, the mobile station shall only use the information applicable to this PLMN (i.e. PLMN ID, access control information, NCC Permitted) within the serving cell, until it is either modified, becomes invalid or a different PLMN or a new cell is reselected, whichever occurs first. If the applicable information is made invalid in the + +cell (see sub-clause 3.2.1), the mobile station shall assume network sharing is not used in the cell until it can again determine that network sharing is used. + +For the mobile station, "applicable to this PLMN" shall be understood as meaning either "explicitly broadcast within (EC) SYSTEM INFORMATION messages for this PLMN" or "derived by the mobile station using a field explicitly provided by (EC) SYSTEM INFORMATION messages for a PLMN listed previous to its selected PLMN"; using a "previously listed field" means the mobile station attempts to find a PLMN previous to its selected PLMN for which a field of interest is explicitly provided by (EC) SYSTEM INFORMATION messages. The Annex M provides examples of using a "previously listed field". + +A UTRAN and/or E-UTRAN capable mobile station supporting network sharing shall also read the SYSTEM INFORMATION TYPE 23 message if broadcast in the cell, to acquire PLMN-specific UTRAN and/or E-UTRAN information used for inter-RAT cell re-selection. + +If so indicated by the *SI\_CHANGE\_ALT* field provided in the SYSTEM INFORMATION TYPE 13 message (see sub-clause 10.5.2.37b), a UTRAN and/or E-UTRAN capable mobile station supporting network sharing shall ignore any change in system information signalled by a *SI\_CHANGE\_FIELD* value '2' provided in the same message. + +When accessing the network, the mobile station shall indicate the selected PLMN index as follows: + +- For access to CS domain via Initial Layer 3 message (see 3GPP TS 24.008 and sub-clause 10.3.1). +- For access to PS domain via AS signalling (see 3GPP TS 44.060). + +### 3.8.4 Abnormal cases + +The mobile station shall ignore any information provided for an Additional PLMN in the SYSTEM INFORMATION TYPE 22 message or in the EC SYSTEM INFORMATION TYPE 4 message if this Additional PLMN is the same as the Common PLMN. + +If the same Additional PLMN ID is provided more than once in the SYSTEM INFORMATION TYPE 22 message or in the EC SYSTEM INFORMATION TYPE 4 message, the mobile station shall use the information corresponding to the first instance of that Additional PLMN. + +If the number of Additional PLMNs broadcast in the SYSTEM INFORMATION TYPE 21 message as part of the *EAB Network Sharing Information* (see sub-clause 10.5.2.37m) differs from the number of Additional PLMNs broadcast in the SYSTEM INFORMATION TYPE 22 message as part of the *Network Sharing Information* (see sub-clause 10.5.2.37n) a mobile station supporting network sharing and configured for EAB shall ignore the *EAB Network Sharing Information* in the SYSTEM INFORMATION TYPE 21 message and assume the *EAB Authorization Mask* and *EAB Subcategory* information otherwise included in this message applies to all PLMNs in this cell (i.e. Common PLMN and all Additional PLMNs). + +If the SYSTEM INFORMATION TYPE 21 message indicates that EAB is used for an Additional PLMN for which the previously listed EAB Authorization Mask/Subcategory apply, but no corresponding *Additional EAB Authorization Mask / Additional EAB Subcategory* fields and *EAB Authorization Mask / EAB Subcategory* fields are provided by the network (see Table 10.5.2.37m.2), the mobile station shall assume that EAB is not used for this Additional PLMN in this cell. + +If the SYSTEM INFORMATION TYPE 21 message indicates that domain-specific access control is used for EAB for an Additional PLMN for which the previously listed EAB Authorization Mask/Subcategory apply, but no corresponding *PS EAB Authorization Mask / PS EAB Subcategory* fields and *Common PS EAB Authorization Mask / Common PS EAB Subcategory* fields are provided by the network (see Table 10.5.2.37m.2), the mobile station shall assume that domain-specific access control for EAB is not used for this Additional PLMN in this cell. + +If the SYSTEM INFORMATION TYPE 22 message indicates that domain-specific access control is used for an Additional PLMN for which the previously listed Access Control Class bitmap applies, but no corresponding *PS\_ACC* field and *Common\_PLMN\_PS\_ACC* field are provided by the network (see Table 10.5.2.37n.2), the mobile station shall assume that domain-specific access control is not used for this Additional PLMN in this cell. If this occurs, this will not preclude a mobile station from using domain-specific access control information for EAB. + +If the number of Additional PLMNs broadcast in the SYSTEM INFORMATION TYPE 23 message as part of the *IRAT Cell Reselection Information* (see sub-clause 10.5.2.37o) differs from the number of Additional PLMNs broadcast in the SYSTEM INFORMATION TYPE 22 message as part of the *Network Sharing Information* (see sub-clause 10.5.2.37n) a mobile station supporting network sharing shall ignore the *IRAT Cell reselection Information* in the SYSTEM + +INFORMATION TYPE 23 message and assume the SYSTEM INFORMATION TYPE 2ter/2quater messages fully apply to all PLMNs in this cell (i.e. Common PLMN and all Additional PLMNs). + +## 3.9 Power Efficient Operation (PEO) + +### 3.9.1 General + +Power Efficient Operation (PEO) is an optional feature used by a MS in a cell that supports PEO to reduce its power consumption through the use of relaxed mobility related requirements (see 3GPP TS 43.064 [109]) and a power saving feature while in idle mode. The power saving feature consists of either extended DRX (eDRX – see 3GPP TS 45.002 [32]) or Power Saving Mode (PSM – see 3GPP TS 23.060 [74]), and a PEO capable mobile station shall support at least one. A cell indicates its support of PEO by including the PEO\_DSC field in the *SI13 Rest Octets* IE. + +A PEO capable mobile station camping in a cell that supports PEO performs NAS signalling to negotiate the use of a power saving feature (i.e. eDRX or PSM – see 3GPP TS 23.060 [74]). A mobile station that has enabled PEO (see 3GPP TS 43.064 [109]) shall only transmit an EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’ (see Table 3.5.2.1.2.2 and 3GPP TS 44.060 [76]) when performing system access. A BSS that receives this message shall send a response that only assigns the MS packet resources in the frequency band corresponding to CCCH on which the EGPRS PACKET CHANNEL REQUEST message was received. + +When PEO is enabled it shall be disabled in case the MS enters a cell that does not support PEO or the MS decides to disable PEO for any reason. When PEO is disabled the MS shall continue to use eDRX or PSM (whichever is enabled) as long as it remains in the same Routing Area it was in when it performed NAS signalling to enable eDRX/PSM (i.e. regardless of whether or not the serving cell indicates PEO is enabled). When PEO is disabled the use of relaxed mobility related requirements and the use of the EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’ shall be disabled. Upon reselecting to a cell in a new Routing Area a mobile station that has enabled eDRX/PSM shall consider it as disabled (i.e. the MS must perform additional NAS signalling in the new Routing Area to enable eDRX/PSM). + +### 3.9.2 PEO Power Saving States + +A MS that has enabled PEO where eDRX is used supports eDRX paging cycles that can range from multiple seconds to about 52 minutes (see 3GPP TS 45.002 [32]). In this case the mobile station supports reachability while in packet idle mode as follows: + +- The mobile station uses the lowest eDRX cycle while the Ready timer (see 3GPP TS 24.008 [79]) is running. +- Upon expiration of the Ready timer or waking up and determining it has not been paged using its nominal paging group the mobile station re-enters the eDRX based power saving state for the time remaining until its next paging occasion. +- A BSS that receives a PAGING-PS PDU containing eDRX information uses it to determine when the corresponding MS is reachable (see 3GPP TS 48.018 [107]). + +A MS that has enabled PEO where PSM with eDRX is used supports reachability while in packet idle mode as follows: + +- While in packet idle mode the mobile station uses the lowest eDRX cycle while the Ready timer is running. +- While in packet idle mode the mobile station uses the negotiated eDRX cycle while the Active timer is running and a PAGING-PS PDU received by the BSS for that mobile station shall contain eDRX information indicating the negotiated eDRX cycle. +- The mobile station enters the PSM based power saving state upon expiration of the Ready timer if the Active timer is not used or upon expiration of the Active timer if a non-zero Active timer is used. +- A BSS that receives a PAGING-PS PDU containing eDRX information will use it to determine when the corresponding MS is reachable (see 3GPP TS 48.018 [107]). + +A MS that has enabled PEO where PSM without eDRX is used supports reachability while in packet idle mode as follows: + +- While in packet idle mode the mobile station uses the broadcasted DRX cycle while the Ready timer is running. A DL-UNITDATA PDU received by the BSS for a mobile station that has enabled PSM without eDRX shall contain DRX information (if available at the SGSN). + +- While in packet idle mode the mobile station uses the broadcasted DRX cycle while the Active timer is running and a PAGING-PS PDU received by the BSS for that mobile station shall contain DRX information (if available at the SGSN). +- The mobile station enters the PSM based power saving state upon expiration of the Ready timer if the Active timer is not used or upon expiration of the Active timer if a non-zero Active timer is used. +- A BSS that receives a PAGING-PS PDU containing DRX information will use it to determine when the corresponding MS is reachable (see 3GPP TS 48.018 [107]). + +### 3.9.3 Extended DRX (eDRX) + +A PEO capable mobile station in a cell that supports PEO that wants to use eDRX selects an eDRX cycle value from the set of available eDRX cycles (see 3GPP TS 45.002 [32]) and indicates it as its preferred eDRX cycle length when registering with the network (see 3GPP TS 24.008 [79]). A mobile station may negotiate the use of both eDRX and PSM when registering with the network in which case its power saving feature is considered to be PSM and the mobile station only makes use of eDRX based reachability when the Active timer is running (see 3GPP TS 23.060 [74] and 3GPP TS 23.682 [108]). The mobile station selects a nominal paging group determined using IMSI and its eDRX cycle and monitors pages thereon (see 3GPP TS 45.002 [32]). + +### 3.9.4 BCCH Acquisition + +A MS that has enabled PEO shall read the PEO\_BCCH\_CHANGE\_MARK field when performing the packet access procedure (see sub-clause 3.5.2.1.2). If a change of PEO\_BCCH\_CHANGE\_MARK is detected it shall first read SI13 before proceeding with the packet access procedure. If no change is detected and the time elapsed since it last read SI13 exceeds 24 hours it should read SI13 before proceeding with the packet access procedure. + +To help avoid the case where a change in PEO\_BCCH\_CHANGE\_MARK is detected when a MS reads its paging subchannel it may acquire an AGCH/PCH message (for the purpose of checking PEO\_BCCH\_CHANGE\_MARK and acquiring the RCC field) before the next instance of its paging subchannel. It shall use the 6 bit BSIC from the most recently read SCH and the acquired RCC field to establish a BSIC. If the BSIC does not match the BSIC value decoded upon first entering the serving cell (see 3GPP TS 45.008) or if the RCC and PEO\_BCCH\_CHANGE\_MARK fields are not included in the message it shall consider PEO as disabled and attempt cell re-selection. + +The network indicates a change to the PEO\_BCCH\_CHANGE\_MARK field within an IMMEDIATE ASSIGNMENT message using the *IA Rest Octets* IE (see sub-clause 10.5.2.16) or within an IMMEDIATE ASSIGNMENT REJECT or an IMMEDIATE ASSIGNMENT EXTENDED or an IMMEDIATE PACKET ASSIGNMENT message using the *Feature Indicator* IE (see sub-clause 10.5.2.76) or within a PAGING REQUEST TYPE 1 message using the *P1 Rest Octets* IE (see sub-clause 10.5.2.23) or within a PAGING REQUEST TYPE 2 message using the *P2 Rest Octets* IE (see sub-clause 10.5.2.24) or within a PAGING REQUEST TYPE 3 message using the *P3 Rest Octets* IE (see sub-clause 10.5.2.25). + +Considering the time spanned by the longest eDRX cycle, changes to the PEO\_BCCH\_CHANGE\_MARK field should not occur more frequently than 3 times within a 24 hour time period. + +If a mobile station determines that more than 3 changes to the PEO\_BCCH\_CHANGE\_MARK field have occurred within a 24 hour time period it shall disable PEO\_BCCH\_CHANGE\_MARK monitoring for 1 hour (i.e. it shall ignore changes to the PEO\_BCCH\_CHANGE\_MARK field when performing the packet access procedure for 1 hour), re-read system information and then resume PEO\_BCCH\_CHANGE\_MARK monitoring. If it then determines that more than 3 changes to the PEO\_BCCH\_CHANGE\_MARK field occur in the next hour it shall disable PEO\_BCCH\_CHANGE\_MARK monitoring for 24 hours (i.e. it shall ignore changes to the PEO\_BCCH\_CHANGE\_MARK field when performing the packet access procedure for 24 hours), re-read system information and then resume PEO\_BCCH\_CHANGE\_MARK monitoring. + +A mobile station in PEO may support deferred system information acquisition (see subclause 3.9.4.1). + +#### 3.9.4.1 Deferred System Information Acquisition for PEO + +A mobile station that supports deferred system information acquisition for PEO, shall read BCCH after cell selection and determine from SI13 message (see subclause 9.1.43a), if the serving cell provides the PEO Idle Mode Mobility (IMM) Cell Group Definition IE, by this indicating the use of common cell parameters across a group of cells in order to potentially defer reading of BCCH data after performing a cell reselection to one of these non-serving cells. + +- If not provided, the MS in idle mode shall apply legacy operation for BCCH acquisition until it reselects to a cell which provides the PEO Idle Mode Mobility (IMM) Cell Group Definition IE in SI13. +- If provided, the MS in idle mode shall determine, based on the content of the PEO IMM Cell Group Definition IE in SI13 as well as common and specific cell parameters, broadcasted in SI2 and SI3 messages, the cell parameters related to cell selection / reselection, cell barring, RA assignment and paging reception, valid for all cells belonging to the same PEO IMM cell group as its serving cell. + +Prior to receiving any instance of its paging subchannel, the MS supporting deferred system information acquisition for PEO shall identify, after evaluation of the PEO\_BCCH\_CHANGE\_MARK field, as specified in subclause 3.9.4 and as specified below for the case of activation / deactivation of deferred system information acquisition for PEO, if the serving cell has modified the PEO IMM Cell Group Definition IE, by reading an SI 13 message and / or AGCH/PCH message in order to determine the PEO IMM Cell Group Identifier and the PEO IMM Change Mark. If either of both values is different to the previously stored one, the MS is obliged to read SI 13 to obtain the latest sent PEO IMM Cell Group Definition IE. + +In case PEO IMM Cell Group Definition IE is provided by the current serving cell, the MS shall use the related information when triggering measurements for cell reselection (i.e. BCCH frequencies, specific BSIC's, PEO IMM Cell Group Identifier and PEO IMM Change Mark fields) and shall determine for non-serving cells, for which BSIC identification is required (see 3GPP TS 45.008 [34]) whether the non-serving cell supports broadcast of PEO IMM Cell Group Definition IE.. To this purpose it may acquire an SI13 message and / or an AGCH/PCH message (for the purpose of reading the RCC field, see subclause 3.9.4) which both contain the PEO IMM Cell Group Details IE (i.e. PEO IMM Cell Group Identifier and PEO IMM Change Mark fields) indicating whether the non-serving cell supports broadcast of PEO IMM Cell Group Definition IE and whether it is part of the same PEO IMM cell group as the serving cell. If the mobile station detects that the non-serving cell has the same values of the PEO IMM Cell Group Identifier and the PEO IMM Change Mark fields as its serving cell, it shall apply the common and specific cell parameters belonging to the PEO IMM cell group of its serving cell for this cell when evaluating if cell reselection is required and shall omit reading of the BCCH of this cell, else it shall read BCCH of this non-serving cell except cell reselection parameters are broadcasted for this non-serving cell in SI2n, i.e. the serving cell indicates SI2n support in SI13. If the MS detects that the PEO IMM Change Mark field in the non-serving cell, which belongs to the same PEO IMM cell group as the serving cell, has been incremented by 1 or more compared to the last one obtained in the serving cell, it immediately stops measuring non-serving cells and starts acquisition of the complete set of System Information messages in the serving cell. The MS shall use the common and specific cell parameters for all cells belonging to the same PEO IMM cell group when evaluating if cell reselection is required and identifying the target cell for reselection. If the MS has reselected to a cell that is part of the same PEO IMM cell group as its previous serving cell, it shall monitor in the new serving cell, i.e. the cell it has reselected to, its paging channel without reading the BCCH in this cell. Only in case + +- a matching page is received, that requires to send a paging response, or +- the MS needs to perform an uplink data transmission, or +- a configurable timeout, i.e. Timeout Read Complete SI, since the last reading of the complete set of System Information messages in a different than the current serving cell is expired, + +the MS is required to immediately read the complete set of System Information messages in the current serving cell. + +The network may choose to deactivate deferred SI acquisition for PEO in network deployments for which System Information needs to be reconfigured rather frequently or for which adjacent cells' idle mode mobility parameters differ too much. In this case the support of deferred SI acquisition for PEO is discontinued by removing the PEO IMM Cell Group Definition IE from SI13 and PEO IMM Cell Group Details IE from AGCH/PCH messages. + +Otherwise the network may choose to activate deferred SI acquisition for PEO in specific cells. In this case the support of deferred SI acquisition in EC operation is indicated by addition of the PEO IMM Cell Group Definition IE to SI 13 and PEO IMM Cell Group Details IE to AGCH/PCH messages. + +The requirement for reading PEO\_BCCH\_CHANGE\_MARK in the serving cell, as specified in subclause 3.9.4, applies also for deferred SI acquisition for PEO. In addition, in case of activation or deactivation of deferred SI acquisition for PEO, the PEO\_BCCH\_CHANGE\_MARK field shall be incremented in the respective cells whilst in case of modification (reconfiguration) of the PEO IMM Cell Group Definition IE it shall not be incremented (rather the PEO IMM Change Mark field is incremented). + +## 3.10 EC Operation + +### 3.10.1 General + +EC-GSM-IoT is an optional feature that allows a MS to use relaxed mobility requirements, extended coverage and optionally, a power saving feature while in packet idle mode. The power saving feature consists of either extended DRX (eDRX – see 3GPP TS 23.060) or Power Saving Mode (PSM – see 3GPP TS 23.060). A cell indicates it supports EC-GSM-IoT operation by the presence of the EC-SCH (see 3GPP TS 45.002). The relaxed mobility related requirements supported by a MS that has enabled EC operation are described in 3GPP TS 43.064 [109]. + +An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT operation may perform NAS signalling to negotiate the use of a power saving feature. An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT operation attempts packet access by: + +- transmitting an EC PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or +- transmitting an EC PACKET CHANNEL REQUEST message using the 1TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a); or +- transmitting an EC PACKET CHANNEL REQUEST message using the 2TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a). + +When sending a response to an EC PACKET CHANNEL REQUEST message a BSS shall only assign the MS packet resources in the frequency band corresponding to CCCH or EC-CCCH on which the EC PACKET CHANNEL REQUEST message was received. + +When EC operation is enabled it shall be disabled in case the MS enters a cell that does not support EC operation or the MS decides to disable EC operation for any reason. When EC operation is disabled then the MS shall continue to use eDRX or PSM (if either one is enabled) as long as it remains in the same Routing Area it was in when it performed NAS signalling to enable eDRX/PSM. When EC operation is disabled the use of relaxed mobility related requirements and the use of the EC PACKET CHANNEL REQUEST message shall be disabled. Upon reselecting to a cell in a new Routing Area a mobile station that has enabled eDRX/PSM shall consider it as disabled (i.e. the MS must perform additional NAS signalling in the new Routing Area to enable eDRX/PSM). + +### 3.10.2 Power Saving States + +A MS that has enabled EC operation where eDRX is used supports reachability while in packet idle mode when the Ready timer is running as described in sub-clause 3.9.2 for the case of a mobile station that uses PEO with eDRX. + +A MS that has enabled EC operation where PSM with eDRX is used supports reachability while in packet idle mode when the Ready timer or Active timer is running as described in sub-clause 3.9.2 for the case of a mobile station that uses PEO with PSM and eDRX. + +A MS that has enabled EC operation where PSM without eDRX is used supports reachability while in packet idle mode as follows: + +- While in packet idle mode the mobile station uses the lowest eDRX cycle while the Ready timer is running. A DL-UNITDATA PDU received by the BSS for a mobile station that has enabled PSM without eDRX shall contain eDRX information indicating the lowest eDRX cycle. +- While in packet idle mode the mobile station uses the lowest eDRX cycle while the Active timer is running. A PAGING-PS PDU received by the BSS for that mobile station shall not contain eDRX information. +- The mobile station enters the PSM based power saving state upon expiration of the Ready timer if the Active timer is not used or upon expiration of the Active timer if a non-zero Active timer is used. +- A BSS that receives a PAGING-PS PDU containing eDRX information will use it to determine when the corresponding MS is reachable (see 3GPP TS 48.018 [107]). + +A MS that has enabled EC operation where neither eDRX nor PSM is used supports reachability while in packet idle mode when the Ready timer is running as follows: + +- The mobile station uses the lowest eDRX cycle while the Ready timer (see 3GPP TS 24.008 [79]) is running. A BSS that receives a DL-UNITDATA PDU (see 3GPP TS 48.018 [107]) containing coverage class information but no eDRX information shall always use the lowest eDRX cycle. +- Upon expiration of the Ready timer the mobile station shall continue using the lowest eDRX cycle. + +### 3.10.3 Extended DRX (eDRX) + +An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT enables eDRX by selecting an eDRX cycle value from the set of available eDRX cycles (see 3GPP TS 45.002 [32]) and indicating it as its preferred eDRX cycle length when registering with the network (see 3GPP TS 24.008 [79]). If an eDRX value is successfully negotiated with the network, the mobile station shall use it when monitoring the paging channel of any cell within the Routing Area where the eDRX value was negotiated. The mobile station selects a nominal paging group on the EC-PCH of its selected EC-CCCH (see 3GPP TS 45.002 [32]) by taking into account its IMSI, its negotiated eDRX cycle and its selected downlink coverage class and monitors pages thereon (see 3GPP TS 45.002 [32]). + +- A MS that has enabled EC operation where eDRX is used supports reachability while in packet idle mode as described in sub-clause 3.5.1a when in packet idle mode and the Ready timer is not running. +- A MS that has enabled EC operation where PSM is used supports reachability while in packet idle mode as described in sub-clause 3.5.1a when in packet idle mode and the Active timer is running. + +### 3.10.4 EC-BCCH Acquisition + +A MS that has enabled EC operation shall have read a complete set of EC SYSTEM INFORMATION messages set no longer than 24 hours prior to attempting packet access. In addition, if the mobile station detects a change to the *EC-BCCH CHANGE MARK* field when reading the EC-SCH INFORMATION message (see sub-clause 9.1.30c) it shall subsequently read one or more EC SYSTEM INFORMATION messages as needed before attempting packet access (see sub-clause 3.5.2a). The EC SI reading can occur immediately after the EC-SCH INFORMATION reading. + +To help avoid the case where a MS detects a change in *EC-BCCH CHANGE MARK* shortly before any instance of its paging subchannel it may acquire the EC-SCH INFORMATION message sufficiently in advance of each instance of its paging subchannel (see 3GPP TS 45.002). + +Each EC SYSTEM INFORMATION message instance includes an EC SI\_CHANGE\_MARK bitmap used by a mobile station to determine which specific EC SYSTEM INFORMATION message(s) has changed after it first detects a change to the *EC-BCCH CHANGE MARK* field in the EC-SCH INFORMATION message. A mobile station makes use of this bitmap as follows: + +- Upon detecting a change to the *EC-BCCH CHANGE MARK* field (sent using the EC-SCH INFORMATION message) a mobile station reads any EC SYSTEM INFORMATION message to acquire the EC SI\_CHANGE\_MARK bitmap. +- If the Overflow Control Bit therein (see sub-clause 9.1.43p) has not changed since the last time the corresponding bitmap was acquired the mobile station determines which of the message specific bits (i.e. EC SI 1, EC SI 2, EC SI 3 and EC SI 4 bits - see sub-clause 9.1.43p) in the EC SI\_CHANGE\_MARK bitmap have changed since the last time the bitmap was acquired. +- The mobile station then reads the subset of EC SYSTEM INFORMATION messages for which a change has been indicated by the message specific bits of the EC SI\_CHANGE\_MARK bitmap. +- If the Overflow Control Bit has changed since the last time the mobile station acquired the EC SI\_CHANGE\_MARK bitmap from any EC SYSTEM INFORMATION message it shall read all EC SYSTEM INFORMATION messages. + +Changes to the *EC-BCCH CHANGE MARK* field should not occur more frequently than 7 times per 24 hours. + +A network that follows the principle of not changing the *EC-BCCH CHANGE MARK* field more frequently than 7 times per 24 hours should manage changes to EC SYSTEM INFORMATION messages as follows: + +- After using a given *EC-BCCH\_CHANGE\_MARK* field code point the network should not re-use the same code point for at least 24 hours. +- If the time between two successive changes for any given EC SYSTEM INFORMATION message is less than 24 hours the network shall change (toggle) the Overflow Control Bit (see sub-clause 9.1.43p). +- After changing the Overflow Control Bit the network shall not change it again for 24 hours regardless of how many additional changes to EC SYSTEM INFORMATION messages are made in that time period (i.e. once an overflow condition is indicated using the Overflow Control Bit it shall continue to be indicated for 24 hours). + +If a mobile station determines that more than 7 changes to the EC-BCCH CHANGE MARK field have occurred within a 24 hour time period or that less than 24 hours have expired since the last time the Overflow Control Bit was changed in the serving cell it shall disable EC-BCCH CHANGE MARK monitoring for 1 hour (i.e. it shall ignore changes to the EC-BCCH CHANGE MARK field when performing the packet access procedure for 1 hour), re-read system information and then resume EC-BCCH CHANGE MARK monitoring. If it then determines that more than 7 changes to the EC-BCCH CHANGE MARK field occur in the next hour or that the Overflow Control Bit changes again in the next hour it shall disable EC-BCCH CHANGE MARK monitoring for 24 hours (i.e. it shall ignore changes to the EC BCCH-CHANGE MARK field when performing the packet access procedure for 24 hours), re-read system information and then resume EC-BCCH CHANGE MARK monitoring. + +A mobile station that supports deferred system information acquisition in EC operation, shall read EC-BCCH after cell selection and determine from EC SI type 2 message (see subclause 9.1.43q), if the serving cell provides the Idle Mode Mobility (IMM) Cell Group Definition, by this indicating the use of common cell parameters across a group of cells in order to potentially defer reading of EC-BCCH data after performing a cell reselection to one of these cells. + +- If not provided, the MS shall apply legacy operation for EC-BCCH acquisition until it reselects to a cell which provides the Idle Mode Mobility (IMM) Cell Group Definition. +- If provided, the MS shall determine, based on the content of the IMM Cell Group Definition as well as common and specific cell parameters, broadcasted in EC SI type 2 and EC SI type 3 messages, the cell parameters related to cell selection / reselection, cell barring, downlink coverage class selection in idle mode, RA assignment and paging reception, valid for all cells belonging to the same IMM Cell Group as its serving cell. + +Prior to receiving any instance of its paging subchannel, the MS supporting deferred system information acquisition in EC operation shall identify, after evaluation of the *EC-BCCH CHANGE MARK* field as specified above, if the current serving cell provides the IMM Cell Group Definition, by reading two consecutive EC-SCH Information messages, starting in the 51-multiframe M with $M \bmod 8 = 0$ , in order to determine the IMM Cell Group Identifier and the IMM Change Mark. If either of both values is different to the previously stored one, the MS is obliged to read EC SI 2 to either obtain the latest sent IMM Cell Group Definition, if its provision is indicated by the cell, or, if its provision is not indicated by the cell, to obtain cell parameters related to legacy operation for EC-BCCH acquisition. + +In case IMM Cell Group Definition is provided by the current serving cell, the MS in idle mode shall use the related information when triggering measurements for cell reselection (i.e. BCCH frequencies, specific BSIC's, IMM Cell Group Identifier and IMM Change Mark) and shall identify, by reading two consecutive EC-SCH Information messages in the non-serving cell, starting in the 51-multiframe M with $M \bmod 8 = 0$ , whether the non-serving cell supports broadcast of IMM Cell Group Definition (see subclause 9.1.30c) and if yes, whether a non-serving cell is part of the same IMM Cell Group as the current serving cell. If the mobile station detects that the non-serving cell is part of the same IMM Cell Group and the IMM Change Mark has the same value as in the serving cell, it shall apply the common and specific cell parameters belonging to the IMM Cell Group for this cell when evaluating if cell reselection is required and shall omit reading of the EC-BCCH of this cell, else it shall read EC-BCCH of this non-serving cell in case no cell reselection parameters are broadcasted for this cell in EC SI type 3 message. If the MS detects that the IMM Change Mark in the non-serving cell, belonging to the same IMM Cell Group as the current serving cell, has been incremented by 1 or more compared to the last one obtained in the serving cell, it immediately stops measuring non-serving cells and starts to acquire a full set of EC System Information messages in the serving cell. + +The MS shall use the common and specific cell parameters for all cells belonging to the same IMM Cell Group when evaluating if cell reselection is required and identifying the target cell for reselection. If the MS has reselected to a cell that is part of the same IMM Cell Group which the previous serving cell belongs to, it shall monitor in the current serving cell, i.e. the cell it has reselected to, its paging channel and, if applicable, its paging indication channel, without reading the EC-BCCH in this cell. + +Only in case + +- a matching page is received, that requires to send a paging response, or + +- the MS needs to perform an uplink data transmission, or +- a configurable timeout, i.e. Timeout Read Complete SI, since the last reading of the complete set of EC System Information messages in a different than the current serving cell is expired, + +the MS is required to immediately read the complete set of EC System Information messages in the current serving cell. + +The network may choose to deactivate deferred SI acquisition in EC operation in network deployments for which EC System Information needs to be reconfigured rather frequently or for which adjacent cells' idle mode mobility parameters differ too much. In this case the support of deferred SI acquisition in EC operation is discontinued by removing the IMM Cell Group Definition IE from EC SI 2 and indicating in the IMM CGI field of the EC-SCH Information message 'IMM Cell Group Definition is not broadcasted or not supported in the cell'. + +Otherwise the network may choose to activate deferred SI acquisition in EC operation in specific cells. In this case the support of deferred SI acquisition in EC operation is indicated by addition of the IMM Cell Group Definition IE to EC SI 2 and by the IMM CGI field in the EC-SCH Information message indicating 'Cell belongs to IMM Cell Group Identity X' with X being 1, 2, ..., or 7. + +### 3.10.5 Extended Coverage + +An EC-GSM-IoT capable mobile station supports extended coverage whereby blind physical layer transmissions are used on both the uplink and downlink according to the current coverage conditions and the logical channel used (see 3GPP TS 45.002). Four different coverage classes for downlink and five coverage classes for uplink are defined, each corresponding to a fixed number of blind physical layer transmissions for each logical channel, where the fixed number of blind physical layer transmissions need not be the same for different logical channels belonging to the same coverage class. A mobile station that has enabled EC operation selects its uplink and downlink coverage class based on thresholds broadcast by the network. The mobile station uses its selected uplink coverage class to determine the number of blind physical layer transmissions to use when sending an EC PACKET CHANNEL REQUEST message (see sub-clause 3.5.2a) and includes the selected downlink coverage class in the message (see sub-clause 9.1.65). + +Upon determining that its currently selected downlink coverage class has changed, a mobile station that has enabled EC operation shall trigger the transmission of a cell update under certain conditions (see 3GPP TS 45.008). + +Blind physical layer transmissions in a cell on EC-PDTCH and EC-PACCH channels in uplink and downlink are mapped on to either 4 consecutive PDCH resources or 2 consecutive PDCH resources. The number of consecutive PDCH resources used for EC TBF operation in an EC-GSM-IoT capable cell is controlled via the EC System information type 2 message. The mapping of EC channels onto physical channels shall be as specified in 3GPP TS 45.002. + +### 3.10.6 EC-CCCH/D Operation + +On EC-CCCH/D, the EC-CCCH blocks designated to mobile stations in CC1 and to mobile stations in the higher coverage classes (CC2, CC3 and CC4) use different training sequences. For EC-PCH and EC-AGCH, the TSC shall be selected from the TSC Set 1, if the EC-PCH / EC-AGCH block, is designated to MSs in CC1 only and shall be selected from TSC Set 2 if the EC-PCH / EC-AGCH block, is designated to at least one MS in a higher coverage class (CC2, CC3 or CC4). + +A mobile station in idle mode which has selected a higher coverage class (CC2, CC3 or CC4) attempts to detect, based on the training sequence in the received bursts, whether the EC-CCCH/D block is sent to mobile stations in the lower coverage class CC1 and if detected, may suspend further reception of the EC-CCCH/D blocks belonging to the selected coverage class. + +A mobile station in idle mode which has selected CC1 as downlink coverage class needs to decode the received EC-CCCH/D block, irrespective of whether the EC-CCCH/D block is designated to mobile stations in CC1 or mobile stations in the higher coverage classes (CC2, CC3 and CC4). In both cases it attempts to decode, based on the detected training sequence in the received bursts, the message sent on EC-CCCH/D. + +A mobile station which supports monitoring of the EC paging indication channel, camps on a cell that indicates paging indication channel support and has selected CC3 or CC4 as downlink coverage class, shall monitor in idle mode the EC paging indication channel (EC-PICH) in a cell which indicates EC paging indication channel support in EC System Information type 2 (see subclause 9.1.43q). The mapping between the paging block of the mobile station and the EC-PICH block which the mobile station shall monitor is specified in 3GPP TS 45.002 [32]. If the EC-PICH block + +indicates that no paging message is scheduled in the EC-CCCH/D blocks corresponding to its paging block, the mobile station enters into sleep mode until the next paging occasion after completion of the current (e)DRX cycle. Else if the EC-PICH block indicates presence of a paging message in the EC-CCCH/D blocks corresponding to its paging block, the mobile station shall read its paging block. + +On EC-PICH channel, for a mobile station that has selected CC4 as downlink coverage class, the paging indication sequence contained in the EC PAGING INDICATION message (see subclause 9.1.69) corresponds to the wake-up or go-to-sleep indication for the paging block mapped to the EC-PICH block. For a mobile station that has selected CC3 as downlink coverage class, the paging indication sequence contained in the EC PAGING INDICATION message (see subclause 9.1.69) corresponds to the wake-up or go-to-sleep indication for any of the two paging blocks mapped to the EC-PICH block (see 3GPP TS 45.002 [32]). A mobile station which supports monitoring of EC paging indication channel detects the paging indication sequence contained within the EC PAGING INDICATION message based on the received bursts of the EC-PICH block (e.g. based on correlation of the received bursts against the expected bursts from a candidate paging indication sequence as specified in subclause 9.1.69) and determines whether to further receive the EC-CCCH/D blocks corresponding to the EC-PICH block based on the detected sequence. + +## 3.11 Multilateration Timing Advance + +### 3.11.1 General + +Multilateration Timing Advance (MTA) is an optional MS feature whereby a MS attempts system access in multiple cells to allow the network to acquire information applicable for estimating the position of the MS (see 3GPP TS 43.059 and 3GPP TS 44.031). The MTA\_BITMAP parameter sent in SI13 (see sub-clause 10.5.2.37b) and EC SI 2 (see sub-clause 9.1.43q) indicates if the Multilateration Timing Advance procedure is supported in a cell. + +- A MS performs the radio access part of the MTA procedure using a set of autonomously selected cells which may include one or more cells for which it receives corresponding assistance information in the RRLP Multilateration Timing Advance Request message it receives from the SMLC (see 3GPP TS 44.031). + +Assistance information may provide information for multiple sets of cells. When multiple cells are identified for any given set then each cell in that set shall be viewed as being co-sited and the MS shall therefore use at most use one cell from that set when performing the radio access part of the MTA procedure. + +- A MS that supports the Multilateration Timing Advance feature shall support one or more of the RLC Data Block method (see sub-clause 3.11.2), Access Burst method (see sub-clause 3.11.3) and Extended Access Burst method (3.11.4) for performing the radio access part of the MTA procedure. +- If the information required to perform the radio access part of a MTA procedure in a cell selected by the MS is not provided by the assistance information but can be acquired by reading SI 13 (if PEO is enabled) or EC SI 2 information (if EC-GSM is enabled) then the MS shall read the necessary system information prior to performing the radio access part of the MTA procedure therein. Otherwise, it shall perform the radio access part of the MTA procedure in that cell using the RLC Data Block method if supported by both the MS and the selected cell. +- If the MS does not support the MTA method indicated by the RRLP Multilateration Timing Advance Request message it shall use the RLC Data Block method if both the MS and the selected cells support the RLC Data Block method. + +### 3.11.2 RLC Data Block Method + +Upon selecting a cell in which to perform the radio access part of a MTA procedure a MS shall use the RLC Data Block method therein if the corresponding RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031) indicates it is to use the RLC Data Block method and both the MS and cell support that method. + +- If PEO is enabled a MS performs the radio access part of the MTA procedure using this method by sending an EGPRS MULTILATERATION REQUEST on the RACH indicating 'RLC Data Block method' (see sub-clause 3.5.2.1.2), is assigned an uplink EGPRS TBF and sends a single MCS-1 coded RLC data block thereon. +- If EC operation is enabled a MS performs the radio access part of the MTA procedure using this method by sending an EC MULTILATERATION REQUEST message on the EC-RACH indicating 'RLC Data Block method' (see sub-clause 3.5.2.1.2a), is assigned an uplink EC TBF and sends a single MCS-1 coded RLC data block thereon. + +- In both cases the "TLLI", "Cell Identity", "Routing Area Identification", "MS Sync Accuracy", "MS Transmission Offset" and "Random ID" parameters are conveyed from the MS to the BSS (see 3GPP TS 44.060 [76]). + +### 3.11.3 Access Burst Method + +Upon selecting a cell in which to perform the radio access part of a MTA procedure a MS shall use the Access Burst method therein if the corresponding RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031) indicates it is to use the Access Burst method and both the MS and cell support that method. + +- If EC operation is enabled a MS performs the radio access part of the MTA procedure using this method by sending an EC MULTILATERATION REQUEST message on the EC-RACH indicating 'Access Burst method' (see sub-clause 9.1.65). + +### 3.11.4 Extended Access Burst Method + +Upon selecting a cell in which to perform the radio access part of a MTA procedure a MS shall use the Extended Access Burst method therein if the corresponding RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031) indicates it is to use the Extended Access Burst method and both the MS and cell support that method. + +- If PEO is enabled a MS performs the radio access part of the MTA procedure using this method by sending two instances of an EGPRS MULTILATERATION REQUEST message on the RACH indicating 'Extended Access Burst method' (see 3GPP TS 44.060 [76]). +- If EC operation is enabled a MS performs the radio access part of the MTA procedure using this method by sending two instances of an EC MULTILATERATION REQUEST message on the EC-RACH indicating 'Extended Access Burst method' (see sub-clause 3.5.2.1.2a and sub-clause 9.1.65). +- In both cases the "MS Transmission Offset", "MS Sync Accuracy", "Random ID" and "Short BSS ID" parameters are conveyed from the MS to the BSS (see sub-clause 9.1.65 and 3GPP TS 44.060 [76]). + +### 3.11.5 BSS Support of Multilateration Timing Advance + +If a MS performs the radio access part of the MTA procedure using the RLC Data Block method and the corresponding BSS determines it has not triggered the MTA procedure (i.e. it has not sent the SMLC a request for a location estimate for the MS, see 3GPP TS 49.031) the BSS sends the estimated "Timing Advance Value", "Cell Identity" of the cell for which the Timing Advance value was estimated, the "BTS Reception Accuracy Level" applicable to the BTS that derived the Timing Advance value, the extracted "TLLI", the extracted "Cell Identity", the extracted "Routing Area Identification" and the extracted "MS Sync Accuracy" to the MSC (see 3GPP TS 48.008). + +If a MS performs the radio access part of the MTA procedure using the Extended Access Burst method and the corresponding BSS determines it has not triggered the MTA procedure the BSS sends the estimated "Timing Advance Value", "Cell Identity" of the cell for which the Timing Advance value was estimated, the "BTS Reception Accuracy Level" applicable to the BTS that derived the Timing Advance value, the extracted "Random ID", the extracted "Short BSS ID" and the extracted "MS Sync Accuracy" to the MSC (see 3GPP TS 48.008). + +If a MS performs the radio access part of the MTA procedure using the RLC Data Block method or the Extended Access Burst method and the corresponding BSS determines it has triggered the MTA procedure (i.e. it sent the SMLC a request for a location estimate corresponding to the extracted "TLLI" or "Random ID", see 3GPP TS 49.031) the BSS sends its default SMLC the estimated "Timing Advance Value", the "Cell Identity" of the cell for which the Timing Advance value was estimated, the "BTS Reception Accuracy Level" applicable to the BTS that derived the Timing Advance value and the extracted "MS Sync Accuracy". Note that the "Timing Advance Value" is adjusted according to the "MS Transmission Offset" parameter extracted from the RLC Data Block or extracted from the first of two EGPRS MULTILATERATION REQUEST messages sent when PEO is enabled or extracted from the first of two EC MULTILATERATION REQUEST messages sent when EC operation is enabled (see 3GPP TS 44.060 [76], see sub-clause 9.1.65 and see 3GPP TS 45.010). + +If a MS performs the radio access part of the MTA procedure using the Access Burst method and the corresponding BSS determines it triggered the MTA procedure it sends its default SMLC the estimated "Timing Advance Value", the "Cell Identity" of the cell for which the Timing Advance value was estimated and the "BTS Reception Accuracy Level" applicable to the BTS that derived the Timing Advance value. + +When sending a EGPRS MULTILATERATION REQUEST message or EC MULTILATERATION REQUEST message the MS uses the *Final MTA Access* field (see sub-clause 9.1.65 and 3GPP TS 44.060 [76]) to indicate whether or not it is in the last cell it will use to perform the radio access part of the MTA procedure. If it indicates it is in the last cell it will use to perform the radio access part of the MTA procedure then upon completion of the radio access part of the MTA procedure in that cell it stops the MPM timer and terminates the MTA procedure. Upon receiving an EGPRS MULTILATERATION REQUEST message or EC MULTILATERATION REQUEST message indicating the MS is in the last cell it will use to perform the radio access part of the MTA procedure the BSS shall complete the MTA procedure for the MS in the current cell, inform the SMLC that no additional timing advance information is pending for the current MTA procedure (see 3GPP TS 49.031), stop the corresponding MPM timer and terminate the MTA procedure. In addition, upon receiving an uplink LLC PDU and determining that a MPM timer is running for the corresponding MS, the BSS shall inform the SMLC that no additional timing advance information is pending for the current MTA procedure, stop the corresponding MPM timer and terminate the MTA procedure. + +--- + +## 4 Elementary procedures for Mobility Management + +See 3GPP TS 24.008. + +--- + +## 5 Elementary procedures for circuit-switched Call Control + +See 3GPP TS 24.008. + +--- + +## 6 Support for packet services + +See 3GPP TS 24.008. + +--- + +## 7 Examples of structured procedures + +See 3GPP TS 24.008. + +--- + +## 8 Handling of unknown, unforeseen, and erroneous protocol data + +### 8.1 General + +The procedures specified in this technical specification apply to those messages which pass the checks described in this sub-clause. + +This sub-clause also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. + +Sub-clauses 8.1 to 8.8 shall be applied in order of precedence. + +Most error handling procedures are mandatory for the mobile station. + +Detailed error handling procedures in the network are implementation dependent and may vary from PLMN to PLMN. However, when extensions of this protocol are developed, networks will be assumed to have the error handling that is indicated in this sub-clause as mandatory ("shall") and that is indicated as strongly recommended ("should"). Sub-clauses 8.2, 8.3, 8.4, 8.5 and 8.7.2 do not apply to the error handling in the network applied to the receipt of initial layer 3 message: If the network diagnoses an error described in one of these sub-clauses in the initial layer 3 message received from the mobile station, it shall either: + +- try to recognize the classmark and then take further implementation dependent actions; or +- release the RR-connection. + +Also, the error handling of the network is only considered as mandatory or strongly recommended when certain thresholds for errors are not reached during a dedicated connection. + +In this sub-clause the following terminology is used: + +- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in sub-clause 10, or if its value part violates rules of clause 10. However it is not a syntactical error that a type 4 IE specifies in its length indicator a greater length than defined in clause 10. +- A message is defined to have semantically incorrect contents if it contains information which, possibly dependent on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part (i.e. Clauses 3, 4, 5) of this technical specification. + +### 8.2 Message too short + +When a message is received that is too short to contain a complete message type information element, that message shall be ignored, cf. 3GPP TS 24.007. + +### 8.3 (void) + +### 8.4 Unknown or unforeseen message type + +If a mobile station or the network receives a GTTP message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message. + +If a mobile station receives an RR message with message type not defined for the PD or not implemented by the receiver in unacknowledged mode, it shall ignore the message. + +If a mobile station in packet idle mode has enabled EC operation then it shall interpret RR messages received on the EC-CCCH as described in sub-clause 10.1. + +If a mobile station receives an RR message with message type not defined for the PD or not implemented by the receiver in acknowledged mode, it shall return a status message (RR STATUS) with cause # 97 "message type non-existent or not implemented". + +If the network receives an RR message with message type not defined for the PD or not implemented by the receiver in a protocol state where reception of an unsolicited message with the given PD from the mobile station is not foreseen in the protocol, the network actions are implementation dependent. Otherwise, if the network receives an RR message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message except that it should return a status message (RR STATUS) with cause #97 "message type non-existent or not implemented". + +NOTE: A message type not defined for the PD in the given direction is regarded by the receiver as a message type not defined for the PD, see 3GPP TS 24.007. + +If the mobile station receives an RR message not compatible with the protocol state, the mobile station shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (RR STATUS) with cause #98 "Message type not compatible with protocol state". + +If the network receives an RR message not compatible with the protocol state, the network actions are implementation dependent. + +## 8.5 Non-semantical mandatory information element errors + +When on receipt of a message, + +- an "imperative message part" error; or +- a "missing mandatory IE" error; + +is diagnosed or when a message containing: + +- a syntactically incorrect mandatory IE; or +- an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007); or +- an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007); + +is received: + +- the mobile station shall proceed as follows: + - for RR protocol, if the message is not one of the messages listed in sub-clause 8.5.1 the mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (RR STATUS) with cause # 96 "Invalid mandatory information"; + - for GTTP, the mobile station shall ignore the message. +- the network shall proceed as follows: + - for RR protocol, the network shall either: + - try to treat the message (the exact further actions are implementation dependent); or + - ignore the message except that it should return a status message (RR STATUS) with cause # 96 "Invalid mandatory information". + - for GTTP, the network shall ignore the message. + +### 8.5.1 Radio resource management + +For the mobile station the following procedures shall apply: + +- a) If the message is a CHANNEL RELEASE message, the actions taken shall be the same as specified in sub-clause 3.4.13 "RR connection release". + +- b) If the message is a PARTIAL RELEASE message, the reactions of the MS are for further study. + +## 8.6 Unknown and unforeseen IEs in the non-imperative message part + +### 8.6.1 IEs unknown in the message + +The MS shall ignore all IEs unknown in a message which are not encoded as "comprehension required" (see 3GPP TS 24.007). + +The network shall take the same approach. + +### 8.6.2 Out of sequence IEs + +The MS shall ignore all out of sequence IEs in a message which are not encoded as "comprehension required" (see 3GPP TS 24.007). + +The network should take the same approach. + +### 8.6.3 Repeated IEs + +If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified in clause 9 of this technical specification, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. + +The network should follow the same procedures. + +## 8.7 Non-imperative message part errors + +This category includes: + +- syntactically incorrect optional IEs; +- conditional IE errors. + +### 8.7.1 Syntactically incorrect optional IEs + +The MS shall treat all optional IEs that are syntactically incorrect in a message as not present in the message. + +The network shall take the same approach. + +### 8.7.2 Conditional IE errors + +When the MS upon receipt of an RR message diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives an RR message containing at least one syntactically incorrect conditional IE, it shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (RR STATUS) with cause value # 100 "conditional IE error". + +When the MS or the network upon receipt of a GTTP message diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a GTTP message containing at least one syntactically incorrect conditional IE, it shall ignore the message. + +When the network receives an RR message and diagnose a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives an RR message containing at least one syntactically incorrect conditional IE, the network shall either: + +- try to treat the message (the exact further actions are implementation dependent); or + +- ignore the message except that it should return a status message (RR STATUS) with cause # 100 "conditional IE error". + +## 8.8 Messages with semantically incorrect contents + +When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part of 3GPP TS 44.018 are performed. If however no such reactions are specified, the MS shall ignore the message except for the RR protocol in which case, if an RR connection exists, it returns a status message (RR STATUS) with cause value # 95 "semantically incorrect message". + +The network should follow the same procedure except that a status message is not normally transmitted. + +## 8.9 Incomplete rest octets + +When the number of octets in a rest octets information element is too small to contain the complete set of components, these components may be truncated by the sending entity (i.e. the network) to fit into the rest octets information element. Whether or not truncation is allowed depends on the construction of the rest octets information element and must be explicitly specified in the relevant rest octet definition (truncated concatenation). + +If truncation is allowed, the mobile station shall assume the value 'L' for the missing components. + +If the truncation is not specified for the relevant rest octet definition, the sending entity must ensure that the complete set of components fits into the rest octets. + +A truncated concatenation is an ordered sequence of components encapsulated in curly brackets and followed by the '//' postfix. The components are the terms appearing at the first level of the concatenation construction. + +The truncated concatenation is equivalent either to the null string or to a concatenation including any number of the components of the sequence put in the same consecutive order and starting with the first component. + +As an example, the set: + +| | +|-------------------------| +| { < a > < b > < c > }// | +|-------------------------| + +is equivalent to: + +| | +|-------------------------------------------------------------------------------| +| { < a > < b > < c > } or
{ < a > < b > } or
{ < a > }        or
null | +|-------------------------------------------------------------------------------| + +--- + +# 9 Message functional definitions and contents + +This sub-clause defines the structure of the messages of those layer 3 protocols defined in 3GPP TS 44.018. These are standard L3 messages as defined in 3GPP TS 24.007 with the exception of those sent on the SCH, RACH, and the HANDOVER ACCESS message. + +Each definition given in the present sub-clause includes: + +- a brief description of the message direction and use, including whether the message has: + - Local significance, *i.e.* relevant only on the originating or terminating access; + - Access significance, *i.e.* relevant in the originating and terminating access, but not in the network; + - Dual significance, *i.e.* relevant in either the originating or terminating access and in the network; or + - Global significance, *i.e.* relevant in the originating and terminating access and in the network. +- a table listing the information elements known in the message and their order of their appearance in the message. All information elements that may be repeated are explicitly indicated. (V and LV formatted IEs, which compose the imperative part of the message, occur before T, TV, and TLV formatted IEs which compose the non- + +imperative part of the message, cf. 3GPP TS 24.007.) In a (maximal) sequence of consecutive information elements with half octet length, the first information element with half octet length occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements. + +For each information element the table indicates: + +1. the information element identifier, in hexadecimal notation, if the IE has format T, TV, or TLV. Usually, there is a default IEI for an information element type; default IEIs of different IE types of the same protocol are different. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-). + +NOTE The same IEI may be used for different information element types in different messages of the same protocol. + +2. the name of the information element (which may give an idea of the semantics of the element). The name of the information element (usually written in italics) followed by "IE" or "information element" is used in 3GPP TS 44.018 as reference to the information element within a message. + 3. the name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced sub-clause of clause 10 of 3GPP TS 44.018 describing the value part of the information element. + 4. the presence requirement indication (M, C, or O) for the IE as defined in 3GPP TS 24.007. + 5. The format of the information element (T, V, TV, LV, TLV) as defined in 3GPP TS 24.007. + 6. The length of the information element (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by link layer protocol. This indication is non-normative. +- c) sub-clauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant message which together with other conditions specified in 3GPP TS 44.018 define when the information elements shall be included or not, what non-presence of such IEs means, and - for IEs with presence requirement C - the static conditions for presence and/or non-presence of the IEs (cf. 3GPP TS 24.007). + +## 9.1 Messages for Radio Resources management + +Table 9.1.1 summarizes the messages for Radio Resources management. + +**Table 9.1.1: Messages for Radio Resources management** + +| Channel establishment messages: | Reference | +|-------------------------------------------|------------------| +| ADDITIONAL ASSIGNMENT | 9.1.1 | +| IMMEDIATE ASSIGNMENT | 9.1.18 | +| IMMEDIATE PACKET ASSIGNMENT | 9.1.18b | +| IMMEDIATE ASSIGNMENT EXTENDED | 9.1.19 | +| IMMEDIATE ASSIGNMENT REJECT | 9.1.20 | +| DTM ASSIGNMENT FAILURE | 9.1.12f | +| DTM REJECT | 9.1.12h | +| DTM REQUEST | 9.1.12i | +| PACKET ASSIGNMENT | 9.1.21f | +| EC IMMEDIATE ASSIGNMENT TYPE 1 | 9.1.59 | +| EC IMMEDIATE ASSIGNMENT TYPE 2 | 9.1.60 | +| EC IMMEDIATE ASSIGNMENT TYPE 4 | 9.1.66 | +| EC IMMEDIATE ASSIGNMENT REJECT | 9.1.61 | +| EC DOWNLINK ASSIGNMENT | 9.1.64 | +| EC DOWNLINK ASSIGNMENT TYPE 2 | 9.1.67 | +| EC PACKET CHANNEL REQUEST | 9.1.65 | +| EC IMMEDIATE ASSIGNMENT TYPE 3 | 9.1.68 | +| Ciphering messages: | Reference | +| CIPHERING MODE COMMAND | 9.1.9 | +| CIPHERING MODE COMPLETE | 9.1.10 | +| Handover messages: | Reference | +| ASSIGNMENT COMMAND | 9.1.2 | +| ASSIGNMENT COMPLETE | 9.1.3 | +| ASSIGNMENT FAILURE | 9.1.4 | +| DTM ASSIGNMENT COMMAND | 9.1.12e | +| INTER SYSTEM TO UTRAN HANDOVER COMMAND | 9.1.15a | +| HANDOVER ACCESS | 9.1.14 | +| HANDOVER COMMAND | 9.1.15 | +| HANDOVER COMPLETE | 9.1.16 | +| HANDOVER FAILURE | 9.1.17 | +| PHYSICAL INFORMATION | 9.1.28 | +| INTER SYSTEM TO CDMA2000 HANDOVER COMMAND | 9.1.15b | +| INTER SYSTEM TO E-UTRAN HANDOVER COMMAND | 9.1.15d | +| Channel release messages: | Reference | +| CHANNEL RELEASE | 9.1.7 | +| PARTIAL RELEASE | 9.1.26 | +| PARTIAL RELEASE COMPLETE | 9.1.27 | +| Paging messages: | Reference | +| PACKET NOTIFICATION | 9.1.21g | +| PAGING REQUEST TYPE 1 | 9.1.22 | +| PAGING REQUEST TYPE 2 | 9.1.23 | +| PAGING REQUEST TYPE 3 | 9.1.24 | +| PAGING RESPONSE | 9.1.25 | +| EC DUMMY | 9.1.62 | +| EC PAGING REQUEST | 9.1.63 | +| System information messages: | Reference | +| SYSTEM INFORMATION TYPE 1 | 9.1.31 | +| SYSTEM INFORMATION TYPE 2 | 9.1.32 | +| SYSTEM INFORMATION TYPE 2bis | 9.1.33 | +| SYSTEM INFORMATION TYPE 2ter | 9.1.34 | +| SYSTEM INFORMATION TYPE 2quater | 9.1.34a | +| SYSTEM INFORMATION TYPE 2n | 9.1.34b | +| SYSTEM INFORMATION TYPE 3 | 9.1.35 | +| SYSTEM INFORMATION TYPE 4 | 9.1.36 | +| SYSTEM INFORMATION TYPE 5 | 9.1.37 | +| SYSTEM INFORMATION TYPE 5bis | 9.1.38 | +| SYSTEM INFORMATION TYPE 5ter | 9.1.39 | +| SYSTEM INFORMATION TYPE 6 | 9.1.40 | +| SYSTEM INFORMATION TYPE 7 | 9.1.41 | +| SYSTEM INFORMATION TYPE 8 | 9.1.42 | +| SYSTEM INFORMATION TYPE 9 | 9.1.43 | +| SYSTEM INFORMATION TYPE 10 | 9.1.50 | +| SYSTEM INFORMATION TYPE 10bis | 9.1.50a | + +| | | +|---------------------------------------------|------------------| +| SYSTEM INFORMATION TYPE 10ter | 9.1.50b | +| SYSTEM INFORMATION TYPE 13 | 9.1.43a | +| SYSTEM INFORMATION TYPE 13alt | 9.1.43k | +| SYSTEM INFORMATION TYPE 14 | 9.1.43i | +| SYSTEM INFORMATION TYPE 15 | 9.1.43j | +| SYSTEM INFORMATION TYPE 16 | 9.1.43d | +| SYSTEM INFORMATION TYPE 17 | 9.1.43e | +| SYSTEM INFORMATION TYPE 18 | 9.1.43g | +| SYSTEM INFORMATION TYPE 19 | 9.1.43f | +| SYSTEM INFORMATION TYPE 20 | 9.1.43h | +| SYSTEM INFORMATION TYPE 21 | 9.1.43m | +| SYSTEM INFORMATION TYPE 22 | 9.1.43n | +| SYSTEM INFORMATION TYPE 23 | 9.1.43o | +| EC SYSTEM INFORMATION TYPE 1 | 9.1.43p | +| EC SYSTEM INFORMATION TYPE 2 | 9.1.43q | +| EC SYSTEM INFORMATION TYPE 3 | 9.1.43r | +| EC SYSTEM INFORMATION TYPE 4 | 9.1.43s | +| DTM INFORMATION | 9.1.12g | +| Specific messages for VBS/VGCS: | Reference | +| NOTIFICATION/FACCH | 9.1.21a | +| NOTIFICATION/NCH | 9.1.21b | +| NOTIFICATION RESPONSE | 9.1.21d | +| VBS/VGCS RECONFIGURE | 9.1.21h | +| VBS/VGCS RECONFIGURE2 | 9.1.21i | +| TALKER INDICATION | 9.1.44 | +| UPLINK ACCESS | 9.1.45 | +| UPLINK BUSY | 9.1.46 | +| UPLINK FREE | 9.1.47 | +| UPLINK RELEASE | 9.1.48 | +| VGCS UPLINK GRANT | 9.1.49 | +| PRIORITY UPLINK REQUEST | 9.1.44a | +| VGCS Neighbour Cell Information | 9.1.57 | +| DATA INDICATION | 9.1.44b | +| DATA INDICATION 2 | 9.1.44c | +| NOTIFY APPLICATION DATA | 9.1.58 | +| Measurement specific messages: | Reference | +| EXTENDED MEASUREMENT ORDER | 9.1.51 | +| EXTENDED MEASUREMENT REPORT | 9.1.52 | +| MEASUREMENT REPORT | 9.1.21 | +| MEASUREMENT INFORMATION | 9.1.54 | +| ENHANCED MEASUREMENT REPORT | 9.1.55 | +| Miscellaneous messages: | Reference | +| CHANNEL MODE MODIFY | 9.1.5 | +| CHANNEL MODE MODIFY ACKNOWLEDGE | 9.1.6 | +| CHANNEL REQUEST | 9.1.8 | +| CLASSMARK CHANGE | 9.1.11 | +| CLASSMARK ENQUIRY | 9.1.12 | +| UTRAN CLASSMARK CHANGE | 9.1.11a | +| cdma2000 CLASSMARK CHANGE | 9.1.11b | +| GERAN IU MODE CLASSMARK CHANGE | 9.1.11d | +| FREQUENCY REDEFINITION | 9.1.13 | +| SYNCHRONIZATION CHANNEL INFORMATION | 9.1.30a | +| COMPACT SYNCHRONIZATION CHANNEL INFORMATION | 9.1.30b | +| EC-SCH INFORMATION | 9.1.30c | +| RR STATUS | 9.1.29 | +| GPRS SUSPENSION REQUEST | 9.1.13b | +| Configuration Change messages: | Reference | +| CONFIGURATION CHANGE COMMAND | 9.1.12b | +| CONFIGURATION CHANGE ACKNOWLEDGE | 9.1.12c | +| CONFIGURATION CHANGE REJECT | 9.1.12d | +| Application messages: | Reference | +| APPLICATION INFORMATION | 9.1.53 | + +### 9.1.1 Additional assignment + +This message is sent on the main DCCH by the network to the mobile station to allocate an additional dedicated channel while keeping the previously allocated channels. See table 9.1.1.1. + +Message type: ADDITIONAL ASSIGNMENT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.1.1: ADDITIONAL ASSIGNMENT message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | ½ | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | ½ | +| | Additional Assignment
Message Type | Message Type
10.4 | M | V | 1 | +| | Channel Description | Channel Description
10.5.2.5 | M | V | 3 | +| 72 | Mobile Allocation | Mobile Allocation
10.5.2.21 | C | TLV | 3-10 | +| 7C | Starting Time | Starting Time
10.5.2.38 | O | TV | 3 | +| 6D | Extended TSC Set | Extended TSC Set 10.5.2.82 | O | TV | 2 | + +#### 9.1.1.1 Mobile Allocation + +This information element shall appear if the *Channel Description* information element indicates frequency hopping. + +If the *Channel Description* IE does not indicate frequency hopping and the information element is present it shall be considered as an IE unnecessary in the message. + +#### 9.1.1.2 Starting Time + +This information element appears in particular if e.g., a change of frequency is planned. + +#### 9.1.1.3 Extended TSC Set + +If the message is sent to a mobile station that indicates support for extended TSC sets (see 3GPP TS 24.008 [79]) this information element may be included to provide TSC related information for the assigned radio resources. In the absence of this information element the TSC related information provided by the *Channel Description* IE shall apply. + +### 9.1.2 Assignment command + +This message is sent on the main DCCH by the network to the mobile station to change the channel configuration to another independent dedicated channel configuration, when no timing adjustment is needed. See table 9.1.2.1. + +Message type: ASSIGNMENT COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.2.1: ASSIGNMENT COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|--------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | ½ | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | ½ | +| | Assignment command
Message Type | Message Type
10.4 | M | V | 1 | + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|------------------------------------------------|----------------------------------------|----------|--------|--------| +| | Description of the First Channel, after time | Channel Description 2 10.5.2.5a | M | V | 3 | +| | Power Command | Power Command 10.5.2.28 | M | V | 1 | +| 05 | Frequency List, after time | Frequency List 10.5.2.13 | C | TLV | 4-132 | +| 62 | Cell Channel Description | Cell Channel Description 10.5.2.1b | O | TV | 17 | +| 10 | Description of the multislot configuration | Multislot Allocation 10.5.2.21b | C | TLV | 3-12 | +| 63 | Mode of the First Channel (Channel Set 1) | Channel Mode 10.5.2.6 | O | TV | 2 | +| 11 | Mode of Channel Set 2 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 13 | Mode of Channel Set 3 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 14 | Mode of Channel Set 4 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 15 | Mode of Channel Set 5 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 16 | Mode of Channel Set 6 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 17 | Mode of Channel Set 7 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 18 | Mode of Channel Set 8 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 64 | Description of the Second Channel, after time | Channel Description 10.5.2.5 | O | TV | 4 | +| 66 | Mode of the Second Channel | Channel Mode 2 10.5.2.7 | O | TV | 2 | +| 72 | Mobile Allocation, after time | Mobile Allocation 10.5.2.21 | C | TLV | 3-10 | +| 7C | Starting Time | Starting Time 10.5.2.38 | O | TV | 3 | +| 19 | Frequency List, before time | Frequency List 10.5.2.13 | C | TLV | 4-132 | +| 1C | Description of the First Channel, before time | Channel Description 2 10.5.2.5a | O | TV | 4 | +| 1D | Description of the Second Channel, before time | Channel Description 10.5.2.5 | O | TV | 4 | +| 1E | Frequency channel sequence before time | Frequency channel sequence 10.5.2.12 | C | TV | 10 | +| 21 | Mobile Allocation, before time | Mobile Allocation 10.5.2.21 | C | TLV | 3-10 | +| 9- | Cipher Mode Setting | Cipher Mode Setting 10.5.2.9 | O | TV | 1 | +| 01 | VGCS target mode Indication | VGCS target mode Indication 10.5.2.42a | O | TLV | 3 | +| 03 | Multi-Rate configuration | MultiRate configuration 10.5.2.21aa | O | TLV | 4-8 | +| 04 | VGCS Ciphering Parameters | VGCS Ciphering Parameters 10.5.2.42b | O | TLV | 3-15 | +| 6D | Extended TSC Set, after time | Extended TSC Set 10.5.2.82 | O | TV | 2 | +| 6E | Extended TSC Set, before time | Extended TSC Set 10.5.2.82 | O | TV | 2 | + +#### 9.1.2.1 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" (2=Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Assignment Complete
Message Type | Message Type
10.4 | M | V | 1 | +| | RR Cause | RR Cause
10.5.2.31 | M | V | 1 | + +### 9.1.4 Assignment failure + +This message is sent on the main DCCH on the old channel from the mobile station to the network to indicate that the mobile station has failed to seize the new channel. See table 9.1.4.1. + +Message type: ASSIGNMENT FAILURE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.4.1: ASSIGNMENT FAILURE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|--------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Assignment Failure
Message Type | Message Type
10.4 | M | V | 1 | +| | RR cause | RR Cause
10.5.2.31 | M | V | 1 | + +### 9.1.5 Channel mode modify + +This message is sent on the main DCCH by the network to the mobile station to request the setting of the mode for the indicated channel(s). The message can be used to change the channel mode of a Multislot Configuration which only contains one channel set. See table 9.1.5.1. + +Message type: CHANNEL MODE MODIFY + +Significance: local + +Direction: network to mobile station + +**Table 9.1.5.1: CHANNEL MODE MODIFY message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|-------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Channel Mode Modify
Message Type | Message Type
10.4 | M | V | 1 | +| | Channel Description | Channel Description 2
10.5.2.5a | M | V | 3 | +| | Channel Mode | Channel Mode
10.5.2.6 | M | V | 1 | +| 01 | VGCS target mode Indication | VGCS target mode Indication
10.5.2.42a | O | TLV | 3 | +| 03 | Multi-Rate
configuration | MultiRate configuration
10.5.2.21aa | O | TLV | 4-8 | +| 04 | VGCS Ciphering Parameters | VGCS Ciphering Parameters
10.5.2.42b | O | TLV | 3-15 | +| 6D | Extended TSC Set | Extended TSC Set 10.5.2.82 | O | TV | 2 | + +#### 9.1.5.1 Channel Description + +This is sufficient to identify the channel in the case of a TCH/H + TCH/H configuration. If used for a multislot configuration, the IE shall describe the present channel configuration with TN indicating the main channel. The IE shall not indicate a new channel configuration when included in the Channel Mode Modify message. + +### 9.1.5.2 VGCS target mode Indication + +This information element is identified as "comprehension required". Only mobile stations supporting "VGCS talking" are required to accept the presence of the element. The presence of the element shall trigger an exception handling if received by a mobile station not supporting "VGCS talking". + +This IE indicates which RR mode is to be used with the new channel mode (i.e. dedicated mode or group transmit mode). If this information element is not present, the RR mode shall be the same as with the previous channel mode. + +When the RR mode of the new channel mode is group transmit mode, the IE also indicates the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as with the previous channel mode. + +NOTE: A mobile station supporting VGCS Talking shall not consider a syntactical error if this IE is present and the channel mode is not speech. + +### 9.1.5.3 Multi Rate configuration + +This information element appears if the Channel Mode IE indicates a multi-rate speech codec. + +### 9.1.5.4 VGCS Ciphering Parameters + +This information element is only applicable to a VGCS talker. It is only included if the assigned resource is ciphered using VGCS ciphering. + +### 9.1.5.5 Extended TSC Set + +If the message is sent to a mobile station that indicates support for extended TSC sets (see 3GPP TS 24.008 [79]) this information element may be included to provide TSC related information for the assigned radio resources. In the absence of this information element the TSC related information provided by the *Channel Description 2* IE shall apply. + +## 9.1.6 Channel mode modify acknowledge + +This message is sent on the main DCCH by the mobile station to the network to indicate the successful or unsuccessful execution of a channel mode modify request. See table 9.1.6.1. + +Message type: CHANNEL MODE MODIFY ACKNOWLEDGE + +Significance: local + +Direction: mobile station to network + +**Table 9.1.6.1: CHANNEL MODE MODIFY ACKNOWLEDGE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------------------------|------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Channel Mode Modify
Acknowledge Message Type | Message Type
10.4 | M | V | 1 | +| | Channel Description | Channel Description 2
10.5.2.5a | M | V | 3 | +| | Channel Mode | Channel Mode
10.5.2.6 | M | V | 1 | +| 6D | Extended TSC Set | Extended TSC Set 10.5.2.82 | C | TV | 2 | + +### 9.1.6.1 Extended TSC Set + +This information element is included if it was present in the corresponding CHANNEL MODE MODIFY message. + +## 9.1.7 Channel release + +This message is sent on the main DCCH from the network to the mobile station to initiate deactivation of the dedicated channel used. See table 9.1.7.1. + +Message type: CHANNEL RELEASE + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.7.1: CHANNEL RELEASE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------------------------------|--------------------------------------------------------------------------------|------------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Channel Release
Message Type | Message Type
10.4 | M | V | 1 | +| | RR Cause | RR Cause
10.5.2.31 | M | V | 1 | +| 73 | BA Range | BA Range
10.5.2.1a | O | TLV | 6 - ? | +| 74 | Group Channel Description | Group Channel Description
10.5.2.14b | O (note 1) | TLV | 5-13 | +| 8x | Group Cipher Key Number | Group Cipher Key Number
10.5.1.10 | C | TV | 1 | +| Cx | GPRS Resumption | GPRS Resumption
10.5.2.14c | O | TV | 1 | +| 75 | BA List Pref | BA List Pref
10.5.2.1c | O | TLV | 3-? | +| 76 | UTRAN Freq List | UTRAN Freq List
10.5.2.1d | O | TLV | 3-? | +| 62 | Cell Channel Description | Cell Channel Description
10.5.2.1b | O | TV | 17 | +| 77 | Cell selection indicator after
release of all TCH and SDCCH | Cell selection indicator after
release of all TCH and
SDCCH
10.5.2.1e | O | TLV | 4 - ? | +| Ax | Enhanced DTM CS Release
Indication | Enhanced DTM CS Release
Indication
10.5.2.14e | O | TV | 1 | +| 04 | VGCS Ciphering Parameters | VGCS Ciphering Parameters
10.5.2.42b | O | TLV | 3-15 | +| 78 | Group Channel Description 2 | Group Channel Description 2
10.5.2.14f | O (note 1) | TLV | 13 | +| 79 | Talker Identity | Talker Identity
10.5.2.65 | O | TLV | 3-20 | +| 7A | Talker Priority Status | Talker Priority Status
10.5.2.64 | O | TLV | 3 | +| 7B | VGCS AMR Configuration | VGCS AMR Configuration
10.5.2.67 | O | TLV | 3 | +| 7C | Individual priorities | Individual priorities
10.5.2.75 | O | TLV | 3 - ? | + +NOTE 1: The network may only send either the Group Channel Description or the Group Channel Description 2 element. + +### 9.1.7.1 Group Channel Description / Group Channel Description 2 + +If a CHANNEL RELEASE is sent to a mobile station which is in dedicated mode and which is involved in a voice group call or has responded to a notification to a voice group call or voice broadcast call, a group channel description (or group channel description 2) may be included, describing the voice group call channel or voice broadcast channel to which the mobile station shall go after the channel release procedure. + +Mobile stations not supporting VGCS listening or VBS listening shall ignore the group channel description (or group channel description 2) information element if present. + +### 9.1.7.2 Group Cipher Key Number + +This IE may be present only if the Group channel description IE or the Group Channel Description 2 IE is provided. The presence of these IE indicates that the mobile station shall use the Group Cipher Key indicated by the Group Cipher Key Number IE for deciphering on the VGCS or VBS channel. If these IE are not present, no ciphering is applied on the VGCS or VBS channel. + +Mobile stations not supporting VGCS listening or VBS listening shall ignore this information element. + +### 9.1.7.3 UTRAN Freq List + +This IE should only be sent to UTRAN capable mobile station. This information element is used to describe the UTRAN frequencies used by the network. + +### 9.1.7.4 Cell Channel Description + +This IE may be present if the following conditions are satisfied: + +- the CHANNEL RELEASE message is ordering the release of the uplink to the originator or to the talker of a VGCS call over a dedicated channel; and +- the Group Channel Description IE is included in the message and is describing a hopping channel. + +It shall not be included in any other case. + +Mobile stations not supporting VGCS talking or VGCS originating shall ignore this information element if present. + +### 9.1.7.5 VGCS Ciphering Parameters + +This information element is only applicable to a VGCS mobile station. It is only included if the group channel is ciphered. + +### 9.1.7.6 Talker Identity + +This information element is only applicable to a VGCS talking subscriber. Mobile stations not supporting VGCS talking shall ignore this information element if present. + +### 9.1.7.7 Talker Priority Status + +This information element is only applicable to a VGCS talking subscriber. Mobile stations not supporting VGCS talking shall ignore this information element if present. + +### 9.1.7.8 VGCS AMR Configuration + +This information element is only applicable to a VGCS talking subscriber. Mobile stations not supporting VGCS talking shall ignore this information element if present. + +### 9.1.7.9 Individual priorities + +This information element is sent to provide MS-specific priorities for priority-based cell reselection. The individual priorities shall override the priorities received through system information or individual priorities received previously. The timer T3230 is used to control the availability of the individual priorities. + +## 9.1.8 Channel request + +This message is sent in random mode on the RACH. It does not follow the basic format. The possible formats are presented directly below, without reference to information fields. The order of bit transmission is defined in 3GPP TS 44.004. + +The message is only one octet long, coded as shown in figure 9.1.8.1 and table 9.1.8.1. + +![Diagram of CHANNEL REQUEST message content (octet 1)](7474a6dfb4787da442d12dcaec98fd04_img.jpg) + +The diagram shows a single octet (8 bits) structure for the CHANNEL REQUEST message. The bits are numbered 8 to 1 from left to right. Bit 8 is the most significant bit. The first three bits (8, 7, 6) are labeled 'ESTABLISHMENT CAUSE'. The remaining five bits (5, 4, 3, 2, 1) are labeled 'RANDOM REFERENCE'. A dashed line separates the 'ESTABLISHMENT CAUSE' field from the 'RANDOM REFERENCE' field, indicating a variable length for the cause field. The label 'octet 1' is placed to the right of the bit box. + +Diagram of CHANNEL REQUEST message content (octet 1) + +**Figure 9.1.8.1: CHANNEL REQUEST message content** + +### **ESTABLISHMENT CAUSE** (octet 1) + +This information field indicates the reason for requesting the establishment of a connection. This field has a variable length (from 3 bits up to 6 bits). + +### **RANDOM REFERENCE** (octet 1) + +This is an unformatted field with variable length (from 5 bits down to 2 bits). + +The Channel Request message is coded as follows: + +(Random Reference field is filled with "x"). + +**Table 9.1.8.1: CHANNEL REQUEST message content** + +| | | +|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MS codes According to Establishment cause: | | +| bits | | +| 8 .... 1 | | +| 101xxxx | Emergency call | +| 110xxxx | Call re-establishment; TCH/F was in use, or TCH/H was in use but the network does not set NECI bit to 1 | +| 011010xx | Call re-establishment; TCH/H was in use and the network sets NECI bit to 1 | +| 011011xx | Call re-establishment; TCH/H + TCH/H was in use and the network sets NECI bit to 1 | +| 100xxxx
0010xxxx
0011xxxx
0001xxxx | Answer to paging
See Table 9.1.8.2. | +| 111xxxx | Originating call and TCH/F is needed, or originating call and the network does not set NECI bit to 1, or procedures that can be completed with a SDCCH and the network does not set NECI bit to 1.
note | +| 0100xxxx | Originating speech call from dual-rate mobile station when TCH/H is sufficient and supported by the MS for speech calls and the network sets NECI bit to 1. See note 5 | +| 0101xxxx | Originating data call from dual-rate mobile station when TCH/H is sufficient and supported by the MS for data calls and the network sets NECI bit to 1. See note 5 | +| 000xxxx | Location updating and the network does not set NECI bit to 1. See note 2c. | +| 0000xxxx | Location updating and the network sets NECI bit to 1. See note 2c. | +| 0001xxxx | Other procedures which can be completed with an SDCCH and the network sets NECI bit to 1.
See note 1 | +| 011110xx
01111x0x
01111xx0 | One phase packet access with request for single timeslot uplink transmission; one PDCH is needed. | +| 01110xxx | Single block packet access; one block period on a PDCH is needed for two phase packet access or other RR signalling purpose. | +| 01100111 | LMU establishment, see note 2 | +| 01100xx0 | Single block MBMS access; one block period on a PDCH is needed for transfer of MBMS SERVICE REQUEST message. | +| 01100x01
01100011 | Reserved for future use
note 2a | +| 01111111 | Reserved, see note 2b | + +NOTE 1: Examples of these procedures are: IMSI detach, Short Message Service (SMS), Supplementary Service management, Location Services, sending of application-specific data. + +NOTE 2: If such messages are received by a network, an SDCCH shall be allocated. + +NOTE 2a: If such messages are received by a network, an SDCCH may be allocated. + +NOTE 2b: This value shall not be used by the mobile station on RACH. If such message is received by the network, it may be ignored. The value is used by the network to answer to a 11 bits EGPRS Packet Channel request. + +NOTE 2c: If the MS is Location Updating as part of a CS Fallback Mobile Originating call setup then the MS shall instead use the appropriate Originating call Establishment cause value. If the MS is Location Updating as part of a CS Fallback for other Mobile Originating services (e.g. USSD or Location Services) then the MS may either use the Establishment cause for the other service or the Establishment cause for Location Updating. If the MS is Location Updating as part of a Mobile Terminating CS Fallback procedure then the MS shall instead use the appropriate Answer to paging Establishment cause value as specified below Table 9.1.8.2. + +**Table 9.1.8.2: CHANNEL REQUEST message +(when answering to paging for RR connection establishment)** + +| MS Capability
Paging Indication
(note 3) | Full rate only | Dual rate (note 5) | SDCCH only | +|------------------------------------------------|----------------|--------------------|------------| +| Any channel | 100xxxxx | 100xxxxx | 100xxxxx | +| SDCCH | 0001xxxx | 0001xxxx | 0001xxxx | +| TCH/F | 100xxxxx | 0010xxxx | 0001xxxx | +| TCH/H or TCH/F | 100xxxxx | 0011xxxx | 0001xxxx | + +In case of a CHANNEL REQUEST triggered within a CS Fallback procedure, see 3GPP TS 23.272, the CHANNEL REQUEST message content shall be based on the relevant information provided in the paging notification received in source RAT, see 3GPP TS 24.301, as for a Paging Indication (see Table 9.1.8.2) set to: + +- "TCH/H or TCH/F" if the mobile station is paged for a speech call or for any other CS service requiring a traffic channel, +- "SDCCH" if the mobile station is paged for a supplementary service transaction, a terminating location services request or any other CS service that can be completed with an SDCCH, +- "Any channel" otherwise (including where no relevant information is provided in the paging notification). + +NOTE 3: The Paging Indication is provided by the Channel Needed IE (or the Channel Needed field) associated with the page which triggered the sending of the CHANNEL REQUEST message. + +NOTE 4: In some cases the established connection will be used only to allow a default rejection mechanism to take place (typically the mobile station will send a RELEASE COMPLETE message with cause #88 "incompatible destination" as an answer to the incoming SETUP message). + +NOTE 5: In this sub-clause, "dual rate capability" means that the MS supports both full rate and half-rate channels at least for the signalling channel mode. In addition, it may support either speech channel mode, or data channel modes, or both on half-rate channels. + +### 9.1.9 Ciphering mode command + +This message is sent on the main DCCH from the network to the mobile station to indicate that the network has started deciphering and that enciphering and deciphering shall be started in the mobile station, or to indicate that ciphering will not be performed. See table 9.1.9.1. + +Message type: CIPHERING MODE COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.9.1: CIPHERING MODE COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Cipher Mode Command
Message Type | Message Type
10.4 | M | V | 1 | +| | Ciphering Mode Setting | Cipher Mode Setting
10.5.2.9 | M | V | 1/2 | +| | Cipher Response | Cipher Response
10.5.2.10 | M | V | 1/2 | + +## 9.1.10 Ciphering mode complete + +This message is sent on the main DCCH from the mobile station to the network to indicate that enciphering and deciphering has been started in the MS. See table 9.1.10.1. + +Message type: CIPHERING MODE COMPLETE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.10.1: CIPHERING MODE COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|--------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Cipher Mode Complete
Message Type | Message Type
10.4 | M | V | 1 | +| 17 | Mobile Equipment
Identity | Mobile Identity
10.5.1.4 | O | TLV | 3-11 | + +### 9.1.10.1 Mobile Equipment Identity + +This information element is included if and only if the mobile station shall include its IMEISV (see sub-clause 3.4.7). This information element shall only refer to IMEISV. + +## 9.1.11 Classmark change + +This message is sent on the main DCCH by the mobile station to the network to indicate a classmark change or as a response to a classmark enquiry. See table 9.1.11.1. + +Message type: CLASSMARK CHANGE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.11.1: CLASSMARK CHANGE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------------------|----------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Classmark Change
Message Type | Message Type
10.4 | M | V | 1 | +| | Mobile Station
Classmark | Mobile Station Classmark 2
10.5.1.6 | M | LV | 4 | +| 20 | Additional Mobile Station
Classmark Information | Mobile Station Classmark 3
10.5.1.7 | C | TLV | 3-34 | + +### 9.1.11.1 Additional Mobile Station Classmark Information + +This IE shall be included if and only if the CM3 bit in the *Mobile Station Classmark* IE is set to 1. + +### 9.1.11.2 Mobile Station Classmark + +This IE shall include for multiband MS the Classmark 2 corresponding to the frequency band in use. + +### 9.1.11a UTRAN Classmark Change + +This message is sent on the main DCCH by the mobile station to the network to indicate a UTRAN Classmark Change or as a response to a UTRAN classmark enquiry. See table 9.1.11a.1. + +Message type: UTRAN CLASSMARK CHANGE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.11a.1: UTRAN CLASSMARK CHANGE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-----------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | UTRAN Classmark Change Message Type | Message Type 10.4 | M | V | 1 | +| | UTRAN Classmark | UTRAN Classmark 10.5.2.7a | M | LV | 2-n | + +NOTE: The ASN.1 coding of the INTER RAT HANDOVER INFO (see 3GPP TS 25.331) included in *UTRAN Classmark* information element is done such that segmentation of the UTRAN CLASSMARK CHANGE message and hence excessive call setup time can be avoided if the network uses similar values of version numbers (Value Tags). + +### 9.1.11b cdma2000 Classmark Change + +This message is sent on the main DCCH by the mobile station to the network to indicate a cdma2000 Classmark Change or as a response to a classmark enquiry with cdma2000 Capabilities specified in the Classmark Enquiry Mask. See table 9.1.11b.1. + +Message type: CDMA2000 CLASSMARK CHANGE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.11b.1: CDMA2000 CLASSMARK CHANGE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|----------------------------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | cdma2000 Classmark Change Message Type | Message Type 10.4 | M | V | 1 | +| | Terminal Information | Terminal Information TIA/EIA/IS-2000-5-A and TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Security Status | Security Status TIA/EIA/IS-2000-5-A and TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Band Class Information | Band Class Information TIA/EIA/IS-2000-5-A and TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Power Class Information | Power Class Information TIA/EIA/IS-2000-5-A and TIA/EIA/IS-833 | M (note) | LV | 1-n | + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------------------------|----------------------------------------------------------------------------------------------|----------|--------|--------| +| | Operating Mode Information | Operating Mode Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Service Option Information | Service Option Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Multiplex Option Information | Multiplex Option Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Power Control Information | Power Control Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Capability Information | Capability Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Channel Configuration
Capability Information | Channel Configuration
Capability Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Extended Multiplex Option
Information | Extended Multiplex Option
Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Band Subclass Information | Band Subclass Information
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | +| | Encryption Capability | Encryption Capability
TIA/EIA/IS-2000-5-A and
TIA/EIA/IS-833 | M (note) | LV | 1-n | + +NOTE: The variable part of the Information Element is coded as the corresponding Information Record defined in TIA/EIA/IS-2000-5-A and TIA/EIA/IS-833. The bit number 1 of the first octet of each Information Element shall be coded as the first bit of the first field of the corresponding Information Record defined in TIA/EIA/IS-2000-5-A and in TIA/EIA/IS-833, reading the fields defined in TIA/EIA/IS-2000-5-A and in TIA/EIA/IS-833 from left to right. + +### 9.1.11c (void) + +### 9.1.11d GERAN IU Mode Classmark Change + +This message is sent on the main DCCH by the mobile station to the network to indicate a GERAN Iu Mode Classmark Change or as a response to a GERAN Iu Mode Classmark Enquiry. See table 9.1.11d.1. + +Message type: GERAN IU MODE CLASSMARK CHANGE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.11d.1: GERAN IU MODE CLASSMARK CHANGE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | GERAN Iu Mode Classmark
Change
Message Type | Message Type
10.4 | M | V | 1 | +| | GERAN Iu Mode Classmark | GERAN Iu Mode Classmark
10.5.2.7d | M | LV | 15-n | + +## 9.1.12 Classmark enquiry + +This message is sent on the main DCCH by the network to the mobile station to request classmark information and/or (for a multi-RAT mobile station) UTRAN information and/or CDMA2000 and/or GERAN *Iu mode* capability information. See table 9.1.12.1. + +Message type: CLASSMARK ENQUIRY + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.12.1: CLASSMARK ENQUIRY message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------|-------------------------------------|----------|--------|--------| +| | RR management | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Classmark Enquiry
Message Type | Message Type
10.4 | M | V | 1 | +| 10 | Classmark Enquiry Mask | Classmark Enquiry Mask
10.5.2.7c | O | TLV | 3 | + +### 9.1.12a (void) + +## 9.1.12b Configuration change command + +This message is sent on the main DCCH from the network to the mobile station to change the channel configuration of a multislot configuration. See table 9.1.12b.1. + +Message type: CONFIGURATION CHANGE COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.12b.1: CONFIGURATION CHANGE COMMAND message contents** + +| IEI | Information element | Type/Reference | Presence | Format | length | +|-----|--------------------------------------------|------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Configuration change Message Type | Message Type
10.4 | M | V | 1 | +| | Description of the multislot configuration | Multislot Allocation
10.5.2.21b | M | LV | 2-11 | +| 63 | Mode of Channel Set 1 | Channel Mode
10.5.2.6 | O | TV | 2 | +| 11 | Mode of Channel Set 2 | Channel Mode
10.5.2.6 | O | TV | 2 | +| 13 | Mode of Channel Set 3 | Channel Mode
10.5.2.6 | O | TV | 2 | +| 14 | Mode of Channel Set 4 | Channel Mode
10.5.2.6 | O | TV | 2 | +| 15 | Mode of Channel Set 5 | Channel Mode
10.5.2.6 | O | TV | 2 | +| 16 | Mode of Channel Set 6 | Channel Mode
10.5.2.6 | O | TV | 2 | +| 17 | Mode of Channel Set 7 | Channel Mode
10.5.2.6 | O | TV | 2 | +| 18 | Mode of Channel Set 8 | Channel Mode
10.5.2.6 | O | TV | 2 | + +### 9.1.12b.1 Description of the multislot allocation + +This information element is used to assign channels that do not carry the main signalling link in a multislot configuration. It indicates if multiple channel sets are used. + +### 9.1.12b.2 Mode of Channel Set "X" ( 1=10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | DTM Assignment Failure Message Type | Message Type
10.4 | M | V | 1 | +| | RR cause | RR Cause
10.5.2.31 | M | V | 1 | + +### 9.1.12g DTM Information + +This message is sent on the main DCCH by the network to the mobile station to provide the mobile station with necessary information for the operation in dual transfer mode. See table 9.1.12g.1. + +Message type: DTM INFORMATION + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.12g.1: DTM INFORMATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------|-------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | DTM Information Message Type | Message Type
10.4 | M | V | 1 | +| | Routeing Area Identification | Routeing Area Identification
10.5.5.15 | M | V | 6 | +| | DTM Information Details | DTM Information Details
10.5.2.11a | M | LV | 4-n | + +#### 9.1.12g.1 Routeing Area Identification + +This information element shall contain the routeing area identification of the routeing area to which the serving cell belongs (see 3GPP TS 23.003). + +### 9.1.12h DTM Reject + +This message is sent on the main DCCH by the network to the mobile station to indicate that no radio resources are available for assignment. See table 9.1.12h.1. + +Message type: DTM REJECT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.12h.1: DTM REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------|--------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | DTM Reject Message Type | Message Type
10.4 | M | V | 1 | +| | DTM wait indication | Wait indication
10.5.2.43 | M | V | 1 | + +### 9.1.12i DTM Request + +This message is sent on the main DCCH by the mobile station to request the establishment of dual transfer mode. See table 9.1.12i.1. + +Message type: DTM Request + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.12i.1: DTM Request message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-----------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | DTM Request Message Type | Message Type
10.4 | M | V | 1 | +| | TLLI | TLLI
10.5.2.41a | M | V | 4 | +| | Channel Request Description 2 | Channel Request Description
2
10.5.2.8b | M | LV | 5 - n | + +NOTE: the MS capabilities relevant to DTM are either provided to the network in the *Mobile Station Classmark 3* IE (see 3GPP TS 24.008 [79]) or contained in the *Channel Request Description 2* IE in the present message. + +### 9.1.13 Frequency redefinition + +This message is sent on the main DCCH from the network to the MS to indicate that the frequencies and the hopping sequence of the allocated channels shall be changed. See table 9.1.13.1 + +Message type: FREQUENCY REDEFINITION + +Significance: dual + +Direction: network to MS + +**Table 9.1.13.1: FREQUENCY REDEFINITION message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | ½ | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | ½ | +| | Frequency Redefinition Message Type | Message Type 10.4 | M | V | 1 | +| | Channel Description | Channel Description 10.5.2.5 | M | V | 3 | +| | Mobile Allocation | Mobile Allocation 10.5.2.21 | M | LV | 1-9 | +| | Starting Time | Starting Time 10.5.2.38 | M | V | 2 | +| 62 | Cell Channel Description | Cell Channel Description 10.5.2.1b | O | TV | 17 | +| 9- | Carrier Indication | Carrier Indication 10.5.2.69 | C | TV | 1 | +| 11 | Mobile Allocation C2 | Mobile Allocation 10.5.2.21 | C | TLV | 2-10 | +| 12 | Channel Description C2 | Channel Description 3 10.5.2.5c | C | TV | 3 | +| 6D | Extended TSC Set | Extended TSC Set 10.5.2.82 | C | TV | 2 | + +#### 9.1.13.1 Cell Channel Description + +If it does not appear, the cell channel description is assumed to be unchanged. + +#### 9.1.13.2 Carrier Indication + +This information element shall only be included if the mobile station is in dual transfer mode, has been assigned packet resources on two carriers, and the Frequency Redefinition message is applicable only to one carrier. The IE shall indicate which carrier the message applies to. In this case the frequency parameters applicable to the indicated carrier are provided in the *Channel Description* IE and the *Mobile Allocation* IE. + +#### 9.1.13.3 Mobile Allocation C2 and Channel Description C2 + +These information element shall be included if the Frequency Redefinition message is used to change the frequency parameters for both carriers being used by a downlink dual carrier capable mobile station in dual transfer mode (in this case the *Carrier Indication* IE is not present). The frequency parameters applicable to carrier 1 are provided in the *Channel Description* and the *Mobile Allocation* IEs, while the frequency parameters applicable to carrier 2 are provided in the *Channel Description C2* and the *Mobile Allocation C2* IEs. + +Either the *Carrier Indication* IE, or the two *Mobile Allocation C2* and *Channel Description C2* IEs shall be present, not all three IEs. + +#### 9.1.13.4 Extended TSC Set + +If the message is sent to a mobile station that indicates support for extended TSC sets (see 3GPP TS 24.008 [79]) this information element may be included to provide TSC related information for the assigned radio resources. In the absence of this information element the TSC related information provided by the *Channel Description* 3 IE shall apply. + +### 9.1.13a (void) + +### 9.1.13b GPRS suspension request + +#### 9.1.13b.1 General + +This message is sent on the main DCCH by the mobile station to the network to request a suspension of GPRS services. See table 9.1.13b.1. + +Message type: GPRS SUSPENSION REQUEST + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.13b.1: GPRS SUSPENSION REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|----------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | GPRS Suspension Request Message Type | Message Type 10.4 | M | V | 1 | +| | Temporary Logical Link Identity | TLLI 10.5.2.41a | M | V | 4 | +| | Routeing Area Identification | Routeing Area Identification 10.5.5.15 | M | V | 6 | +| | Suspension cause | Suspension cause 10.5.2.47 | M | V | 1 | +| 01 | Service Support | Service Support 10.5.2.57 | O | TV | 2 | + +#### 9.1.13b.2 Routeing Area Identification + +This information element shall contain the stored routeing area identification (e.g. received in the last attach or routeing area update procedure, see 3GPP TS 24.008). + +#### 9.1.13b.3 Temporary Logical Link Identity + +This information element contains the TLLI derived from the P-TMSI, see 3GPP TS 23.060. The network shall accept a local TLLI even if the current RA where the message is received differs from the one indicated in this message. + +### 9.1.14 Handover access + +This message is sent in random mode on the main DCCH during a handover procedure. It does not follow the basic format. The format is presented directly below without reference to information elements. The order of bit transmission is defined in 3GPP TS 44.004. + +This message is only one octet long, coded as shown in figure 9.1.14.1 and table 9.1.14.1. + +![Diagram of HANDOVER ACCESS message content showing 8 bits (8 to 1) labeled 'handover reference' in a single octet.](77f52cfcb91105c4eb89664aa75a2834_img.jpg) + +The diagram shows a single octet structure for the HANDOVER ACCESS message. It consists of a horizontal rectangle divided into eight equal segments, labeled from left to right as 8, 7, 6, 5, 4, 3, 2, and 1. The entire rectangle is labeled 'handover reference' in the center. To the right of the rectangle, the text 'octet 1' is present. + +Diagram of HANDOVER ACCESS message content showing 8 bits (8 to 1) labeled 'handover reference' in a single octet. + +**Figure 9.1.14.1: HANDOVER ACCESS message content** + +**Table 9.1.14.1: HANDOVER ACCESS message content** + +| | +|-------------------------------------------------------------------------------------------------------| +| HANDOVER REFERENCE
This is an unformatted 8 bit field.
(also described in sub-clause 10.5.2.15) | +|-------------------------------------------------------------------------------------------------------| + +## 9.1.15 Handover command + +This message is sent on the main DCCH by the network to the mobile station to change the dedicated channel configuration, timing adjustment needed. See table 9.1.15.1. + +Message type: HANDOVER COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.15.1: HANDOVER COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------------|------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Handover Command Message Type | Message Type 10.4 | M | V | 1 | +| | Cell Description | Cell description 10.5.2.2 | M | V | 2 | +| | Description of the first channel, after time | Channel Description 2 10.5.2.5a | M | V | 3 | +| | Handover Reference | Handover Reference 10.5.2.15 | M | V | 1 | +| | Power Command and Access type | Power Command and Access type 10.5.2.28a | M | V | 1 | +| D- | Synchronization Indication | Synchronization Indication 10.5.2.39 | O | TV | 1 | +| 02 | Frequency Short List, after time | Frequency Short List 10.5.2.14 | C | TV | 10 | +| 05 | Frequency List, after time | Frequency List 10.5.2.13 | C | TLV | 4-131 | +| 62 | Cell Channel Description | Cell Channel Description 10.5.2.1b | C | TV | 17 | +| 10 | Description of the multislot configuration | Multislot Allocation 10.5.2.21b | C | TLV | 3-12 | +| 63 | Mode of the First Channel(Channel Set 1)) | Channel Mode 10.5.2.6 | O | TV | 2 | +| 11 | Mode of Channel Set 2 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 13 | Mode of Channel Set 3 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 14 | Mode of Channel Set 4 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 15 | Mode of Channel Set 5 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 16 | Mode of Channel Set 6 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 17 | Mode of Channel Set 7 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 18 | Mode of Channel Set 8 | Channel Mode 10.5.2.6 | O | TV | 2 | +| 64 | Description of the Second Channel, after time | Channel Description 10.5.2.5 | O | TV | 4 | +| 66 | Mode of the Second Channel | Channel Mode 2 10.5.2.7 | O | TV | 2 | +| 69 | Frequency Channel Sequence, after time | Frequency Channel Sequence 10.5.2.12 | C | TV | 10 | + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|------------------------------------------------|--------------------------------------------|----------|--------|--------| +| 72 | Mobile Allocation, after time | Mobile Allocation
10.5.2.21 | C | TLV | 3-10 | +| 7C | Starting Time | Starting Time
10.5.2.38 | O | TV | 3 | +| 7B | Real Time Difference | Time Difference
10.5.2.41 | C | TLV | 3 | +| 7D | Timing Advance | Timing Advance
10.5.2.40 | C | TV | 2 | +| 12 | Frequency Short List, before time | Frequency Short List
10.5.2.14 | C | TV | 10 | +| 19 | Frequency List, before time | Frequency List
10.5.2.13 | C | TLV | 4-131 | +| 1C | Description of the First Channel, before time | Channel Description 2
10.5.2.5a | O | TV | 4 | +| 1D | Description of the Second Channel, before time | Channel Description
10.5.2.5 | O | TV | 4 | +| 1E | Frequency channel sequence before time | Frequency channel sequence
10.5.2.12 | C | TV | 10 | +| 21 | Mobile Allocation, before time | Mobile Allocation
10.5.2.21 | C | TLV | 3-10 | +| 9- | Cipher Mode Setting | Cipher Mode Setting
10.5.2.9 | O | TV | 1 | +| 01 | VGCS target mode Indication | VGCS target mode Indication
10.5.2.42a | O | TLV | 3 | +| 03 | Multi-Rate configuration | MultiRate configuration
10.5.2.21aa | O | TLV | 4-8 | +| 76 | Dynamic ARFCN Mapping | Dynamic ARFCN Mapping
10.5.2.11b | O | TLV | 6-34 | +| 04 | VGCS Ciphering Parameters | VGCS Ciphering Parameters
10.5.2.42b | O | TLV | 3-15 | +| 51 | Dedicated Service Information | Dedicated Service Information
10.5.2.59 | O | TV | 2 | +| A- | PLMN Index | PLMN Index
10.5.2.81 | O | TV | 1 | +| 6D | Extended TSC Set, after time | Extended TSC Set 10.5.2.82 | O | TV | 2 | +| 6E | Extended TSC Set, before time | Extended TSC Set 10.5.2.82 | O | TV | 2 | + +### 9.1.15.1 Synchronization Indication + +If this information element does not appear, the assumed value is "non-synchronized". + +### 9.1.15.2 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" ( $2 \leq X \leq 8$ ) + +If this information element is not present the channel mode of the previously allocated channel or channels for Channel Set "X" ( $1 \leq X \leq 8$ ) shall be assumed. + +If Channel Set "X" is not defined for the configuration, the *Mode of Channel Set "X"* IE shall be considered as an IE unnecessary in the message. + +NOTE: Sub-clause 3.4.4.1 defines cases when one or several *Mode of Channel Set "X"* IEs shall be included in the message. + +### 9.1.15.3 Description of the Second Channel + +These information element appear if the mobile station carries two connections (on two dedicated channels, for the TCH/H+TCH/H configuration). + +The connection using the channel previously defined in the *Description of the First Channel* IE of an ASSIGNMENT COMMAND or HANDOVER COMMAND message shall use the channel defined in the first channel description IE of the HANDOVER COMMAND message defining the new configuration. + +The channel described in the *Description of the First Channel* IE carries the main DCCH. The SACCH used is the one associated with that channel. + +#### 9.1.15.4 Mode of the Second Channel + +If the *Description of the Second Channel* IE is not present and the information element is present it shall be considered as an IE unnecessary in the message. + +This element appears at least when the channel mode is changed for the channel defined in the Description of the Second Channel information element. + +#### 9.1.15.5 Frequency Channel Sequence, Frequency List, Frequency short list and Mobile Allocation, after time. + +If at least one of the channel descriptions for after time indicates frequency hopping, one and only one of the following information elements shall be present: + +- Frequency Channel Sequence, after time; +- Frequency list, after time; +- Frequency Short List, after time; +- Mobile Allocation, after time. + +If neither of the Channel Description IEs indicate frequency hopping, if they are not required for the decoding of Channel Description IEs for before time, and if any of the four information elements are present they shall be considered as IEs unnecessary in the message. + +The *Frequency Channel Sequence* information element shall not be used unless all the ARFCNs that it indicates are in the P-GSM band. + +#### 9.1.15.6 Starting Time + +The *starting time* information element is included when the network wants the mobile station to change the frequency parameters of the channels more or less at the moment a change of channel occurs. In this case a number of information elements may be included to give the frequency parameters to be used before the starting time. + +The *starting time* information element refers to the new cell time. + +If the *starting time* information element is present and none of the information elements referring to before the starting time are present, the mobile station waits and accesses the channels at the indicated time. + +If the *starting time* information element is present and at least one of the information elements referring to before the starting time is present, the mobile station does not wait for the indicated time and accesses the channel using the frequency parameters for before the starting time. + +If the *starting time* information element is not present and some of the information elements referring to before the starting time is present, these information elements shall be considered as IEs unnecessary in the message. + +If the *description of the first channel, before time* IE is not present, the channel description to apply for before the time, if needed, is given by the *description of the first channel, after time* IE. + +If the *description of the second channel, after time* IE is present, the *description of the second channel, before time* IE not present, and a description of the configuration for before the time needed, the channel configuration before the starting time is nevertheless of two traffic channels, and the channel description to apply to the second channel before the starting time is given by the *description of the second channel, after time* IE. + +If the *starting time* IE is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, one and only one of the following information elements may be present and applies before the starting time to all assigned channels: + +- Mobile Allocation, before time IE; +- Frequency Short list, before time IE; +- Frequency list, before time IE; +- Frequency channel sequence, before time IE. + +If the *starting time* IE is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, and none of the above mentioned IE is present, a frequency list for after the starting time must be present (see sub-clause 9.1.2.4), and this list applies also for the channels before the starting time. + +#### 9.1.15.7 Reference cell frequency list + +If any of the *mobile allocation* information elements is present, then the *cell channel description* IE must be present. It is used to decode the *mobile allocation* IEs in the message. + +In addition, if no information elements pertaining to before the starting time is present in the message, the frequency list defined by the *cell channel description* IE is used to decode the *mobile allocation* IEs in later messages received in the new cell until reception of a new reference cell frequency list or the new cell is left. + +#### 9.1.15.8 Real Time Difference + +This information element shall appear if the *Synchronization Indication* information element indicates a pseudo-synchronous handover otherwise it shall be considered as an unnecessary information element. + +#### 9.1.15.9 Timing Advance + +This information element shall appear if the "synchronization indication" element indicates a presynchronized handover. If not included for a presynchronized handover, then the default value as defined in 3GPP TS 45.010 shall be used. For other types of handover it shall be considered as an unnecessary information element. + +#### 9.1.15.10 Cipher Mode Setting + +If this information element is omitted, the mode of ciphering is not changed after the mobile station has switched to the assigned channel. + +In the case of inter-RAT or inter-mode handover to GERAN A/Gb mode, the HANDOVER COMMAND message shall always contain the cipher mode setting IE (see sub-clause 3.4.4.1). + +Only applicable for mobile stations supporting VGCS talking: + +The cipher mode setting IE shall not be included if the HANDOVER COMMAND message is sent on a VGCS channel or on a dedicated channel for a handover to a VGCS channel. + +The cipher mode setting IE shall be included if the HANDOVER COMMAND message is sent on a ciphered VGCS channel for a handover to a dedicated channel. If the information element is not present, the MS shall use ciphering mode "no ciphering" on the assigned channel. + +#### 9.1.15.11 VGCS target mode indication + +This information element is identified as "comprehension required". Only mobile stations supporting "VGCS talking" are required to accept the presence of the element. The presence of the element shall trigger an exception handling if received by a mobile station not supporting "VGCS talking". + +This IE indicates which mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present, the mode shall be the same as on the previous channel. + +The IE also indicates the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as on the previous channel. + +NOTE: A mobile station supporting VGCS Talking shall not consider a syntactical error if this IE is present and the channel mode is not speech. + +#### 9.1.15.12 Description of the multislot allocation + +This information element is included if so indicated by the channel type and TDMA offset field in the *Channel Description* information element and is used to assign channels that do not carry a main signalling link in a multislot configuration. It indicates how the used timeslots are divided into separate channel sets. + +If the *Channel Description* IE does not require the presence the information element it shall be considered as an IE unnecessary in the message. + +If multislot configuration is indicated by the *Channel Description* IE but the *Multislot Allocation* IE is not present, all channels in the configuration belong to one channel set, "Channel Set 1". + +NOTE: As a change of timeslot number cannot occur for the channel described for after the starting time, the *Multislot Allocation* IE does not have to be included more than once. + +#### 9.1.15.13 MultiRateconfiguration + +This information element appears if the Mode of the First Channel indicates a multi-rate speech codec, and if the assigned configuration is new, i.e. it is different from the MultiRateconfiguration used in the serving cell. + +In the case of a handover from a GERAN cell, if the Mode of the First Channel indicates a multi-rate speech codec, and this IE is not included, then the mobile station shall assume that the MultiRateconfiguration has not changed. + +In the case of an intersystem handover to GERAN, if the Mode of the First Channel indicates a multi-rate speech codec, this IE shall be included. If not included in this case, the mobile station shall act as defined in sub-clause 3.4.4.1. + +#### 9.1.15.14 Dynamic ARFCN Mapping + +This information element should only be included if the network supports dynamic ARFCN mapping and there is a need to define new dynamic ARFCN mapping, e.g. at handover to another PLMN or from another RAT to GSM. This information replaces any previously received information about dynamic ARFCN mapping. After returning to idle mode or packet idle mode, the mobile station shall acquire new dynamic ARFCN mapping information, except for the cases specified in sub-clause 3.2.2.1 (SI15). This mapping shall apply to any ARFCN used in the same message. + +NOTE: If this information element is received with a value part length equal to zero or a value part that does not contain any dynamic ARFCN mapping, any previously received information about dynamic ARFCN mapping is deleted. + +#### 9.1.15.15 VGCS Target cell Ciphering information + +Only mobile stations supporting "VGCS talking" have to accept the presence of the element. The presence of the element shall trigger an exception handling if received by a mobile station not supporting "VGCS talking". + +#### 9.1.15.16 Dedicated Service Information + +This information element shall only be included if the network supports dedicated mode MBMS notification and the mobile station supports MBMS. + +#### 9.1.15.17 Extended TSC Set, after time + +If the message is sent to a mobile station that indicates support for extended TSC sets (see 3GPP TS 24.008 [79]) this information element may be included to provide TSC related information for the assigned radio resources. In the absence of this information element the TSC related information provided by the *Description of the first channel, after time* IE shall apply. + +#### 9.1.15.18 Extended TSC Set, before time + +If the message is sent to a mobile station that indicates support for extended TSC sets (see 3GPP TS 24.008 [79]) this information element may be included to provide TSC related information for the assigned radio resources. In the absence of this information element the TSC related information provided by the *Description of the First Channel, before time* IE shall apply. If the *Description of the First Channel, before time* IE is not present, the TSC related information to apply for before the time, if needed, is given by the *Extended TSC Set, after time* IE. + +#### 9.1.15a Inter System To UTRAN Handover Command + +This message is sent on the main DCCH by the network to the mobile station to change the dedicated channel in GSM to a dedicated channel configuration in UTRAN or a dedicated PS bearer in UTRAN. See table 9.1.15a.1. + +Message type: INTER SYSTEM TO UTRAN HANDOVER COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.15a.1: INTER SYSTEM TO UTRAN HANDOVER COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------------------|-----------------------------------------------|------------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Inter System to UTRAN Handover Command Message Type | Message Type
10.4 | M | V | 1 | +| | Handover to UTRAN Command | Handover To UTRAN Command
10.5.2.51 | M | LV | 2-n | +| | CN to MS transparent information | CN to MS transparent information
10.5.2.80 | O (Note 1) | TLV | 3-n | + +NOTE 1: This field is only present in case of a CS to PS SRVCC to UTRAN (HSPA). + +#### 9.1.15b Inter System To cdma2000 Handover Command + +This message is sent on the main DCCH by the network to the mobile station to change the dedicated channel in GSM to a dedicated channel configuration in cdma2000. See table 9.1.15b.1. + +Message type: INTER SYSTEM TO CDMA2000 HANDOVER COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.15b.1: INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------------------------|-------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Inter System to cdma2000 Handover Command Type Message | Message Type
10.4 | M | V | 1 | +| | Handover to cdma2000 Command | Handover To cdma2000 Command
10.5.2.52 | M | LV | 4 - n | + +### 9.1.15c HANDOVER TO GERAN Iu MODE Command + +This message is sent on the main DCCH by the network to the mobile station to reconfigure the dedicated channels in GSM to a dedicated channel configuration in GERAN *Iu mode*. See table 9.1.15c.1. + +Message type: HANDOVER TO GERAN Iu MODE COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.15c.1: HANDOVER TO GERAN Iu MODE COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------------------------------------|---------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | HANDOVER TO GERAN Iu
MODE COMMAND Message
Type | Message Type
10.4 | M | V | 1 | +| | RADIO BEARER
RECONFIGURATION | RADIO BEARER
RECONFIGURATION
3GPP TS 44.118 | M | LV | 2-n | + +#### 9.1.15d Inter System To E-UTRAN Handover Command + +This message is sent on the main DCCH by the network to the mobile station to change the dedicated channel in GSM to a dedicated PS bearer in E-UTRAN. See table 9.1.15d.1. + +Message type: INTER SYSTEM TO E-UTRAN HANDOVER COMMAND + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.15d.1: INTER SYSTEM TO E-UTRAN HANDOVER COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------------------------------------|--------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | INTER SYSTEM TO E-UTRAN
HANDOVER COMMAND
Message Type | Message Type
10.4 | M | V | 1 | +| | DL-DCCH-Message | DL-DCCH-Message
10.5.2.79 | M | LV | 2-n | +| | CN to MS transparent
information | CN to MS transparent
information
10.5.2.80 | M | LV | 2-n | + +### 9.1.16 Handover complete + +This message is sent on the main DCCH from the mobile station to the network to indicate that the mobile station has established the main signalling link successfully. See table 9.1.16.1. + +Message type: HANDOVER COMPLETE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.16.1: HANDOVER COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------------------|-------------------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Handover Complete Message Type | Message Type 10.4 | M | V | 1 | +| | RR Cause | RR Cause 10.5.2.31 | M | V | 1 | +| 77 | Mobile Observed Time Difference | Mobile Time Difference 10.5.2.21a | O | TLV | 5 | +| 67 | Mobile Observed Time Difference on Hyperframe level | Mobile Time Difference on Hyperframe level 10.5.21ab. | O | TLV | 7 | + +#### 9.1.16.1 Mobile Observed Time Difference + +This information element is included if and only if the Synchronization Indication IE in the HANDOVER COMMAND message requests it to be sent. + +#### 9.1.16.2 Mobile Observed Time Difference on Hyperframe level + +This information element is included if and only if the Synchronization Indication IE in the HANDOVER COMMAND message requests it to be sent. + +### 9.1.17 Handover failure + +This message is sent on the main DCCH on the old channel from the mobile station to the network to indicate that the mobile station has failed to seize the new channel. See table 9.1.17.1. + +Message type: HANDOVER FAILURE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.17.1: HANDOVER FAILURE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-----------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Handover Failure Message Type | Message Type 10.4 | M | V | 1 | +| | RR Cause | RR Cause 10.5.2.31 | M | V | 1 | +| 9- | PS Cause | PS Cause 10.5.2.67 | O | TV | 1 | + +#### 9.1.17.1 PS Cause + +The PS Cause IE shall only be included in the case of DTM Handover where there is an error in the packet resources described in the DTM HANDOVER COMMAND message. + +### 9.1.18 Immediate assignment + +This message is sent on the CCCH or encapsulated in the PACKET CS COMMAND message on the PACCH (see 3GPP TS 44.060) by the network to the mobile station in idle mode to change the channel configuration to a dedicated configuration while staying in the same cell or to the mobile station in packet idle mode to change the channel configuration to either an uplink or a downlink packet data channel configuration, or to provide the configuration of an MBMS session in the cell. In addition, this message is sent on the CCCH to a mobile station in packet idle mode when + +it has sent an EGPRS MULTILATERATION REQUEST message indicating 'RLC Data Block method' or 'Page Response for Positioning Event' (see table 9.1.18.1) or indicating 'Access Burst method' or 'Extended Access Burst method' (see sub-clause 3.5.2.1.2, sub-clause 3.11 and table 9.1.18.1a). + +The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the *IA Rest Octets* and *L2 Pseudo Length* information elements. + +Message type: IMMEDIATE ASSIGNMENT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.18.1: IMMEDIATE ASSIGNMENT message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Immediate Assignment Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Dedicated mode or TBF | Dedicated mode or TBF
10.5.2.25b | M | V | 1/2 | +| | Channel Description | Channel Description
10.5.2.5 | C | V | 3 | +| | Packet Channel Description | Packet Channel Description
10.5.2.25a | C | V | 3 | +| | Request Reference | Request Reference
10.5.2.30 | M | V | 3 | +| | Timing Advance | Timing Advance
10.5.2.40 | M | V | 1 | +| | Mobile Allocation | Mobile Allocation
10.5.2.21 | M | LV | 1-9 | +| 7C | Starting Time | Starting Time
10.5.2.38 | O | TV | 3 | +| | IA Rest Octets | IA Rest Octets
10.5.2.16 | M | V | 0-11 | +| 6D | Extended TSC Set | Extended TSC Set 10.5.2.82 | O | TV | 2 | + +**Table 9.1.18.1a: IMMEDIATE ASSIGNMENT message content (MTA Access Burst or Extended Access Burst Method only)** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Immediate Assignment Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Dedicated mode or TBF | Dedicated mode or TBF
10.5.2.25b | M | V | 1/2 | +| | Request Reference | Request Reference
10.5.2.30 | M | V | 3 | +| | Timing Advance | Timing Advance
10.5.2.40 | M | V | 1 | +| | Mobile Allocation | Mobile Allocation
10.5.2.21 | M | LV | 1-9 | +| | IA Rest Octets | IA Rest Octets
10.5.2.16 | M | V | 0-11 | +| 05 | Request Reference 1 | Request Reference Alt
10.5.2.87 | O | TV | 5 | +| 06 | Request Reference 2 | Request Reference Alt
10.5.2.87 | O | TV | 5 | +| 07 | Request Reference 3 | Request Reference Alt
10.5.2.87 | O | TV | 5 | +| 08 | Request Reference 4 | Request Reference Alt
10.5.2.87 | O | TV | 5 | + +#### 9.1.18.0a Dedicated mode or TBF + +A mobile station not supporting GPRS may ignore the contents of this information element and regard it as an unnecessary IE. Such mobile station shall assume that this message assigns a dedicated mode resource. + +If the *Dedicated mode or TBF* IE indicates that neither a TBF nor a dedicated resource has been assigned (see sub-clause 10.5.2.25b) then the *IA Rest Octets* IE shall be coded using the ‘LL’ option and indicate either a ‘0’ or a ‘1’ for the *Compressed\_Inter\_RAT\_HO\_INFO\_IND* field (see sub-clause 10.5.2.16). In this case a mobile station that has enabled PEO and has sent an EGPRS MULTILATERATION REQUEST message indicating ‘Access Burst’ or ‘Extended Access Burst’ method (see sub-clause 3.5.2.1.2 and sub-clause 3.11) shall ignore the *Compressed\_Inter\_RAT\_HO\_INFO\_IND* field and examine the *Request Reference 1*, *Request Reference 2*, *Request Reference 3*, and *Request Reference 4* information elements (as necessary) in attempt to find an Immediate Assignment message (see Table 9.1.18.1a) that matches its transmitted EGPRS MULTILATERATION REQUEST message (see sub-clause 10.5.2.87). A mobile station that has enabled PEO and has sent an EGPRS MULTILATERATION REQUEST message indicating ‘RLC Data Block method’ or ‘Page Response for Positioning Event’ shall ignore an Immediate Assignment message where the *Dedicated mode or TBF* IE indicates neither a TBF nor a dedicated resource has been assigned. + +#### 9.1.18.0b Channel Description + +If the *Dedicated mode or TBF* IE indicates that the message assigns a dedicated mode resource, the mobile station shall consider this information element present in the message. + +#### 9.1.18.0c Packet Channel Description + +If the *Dedicated mode or TBF* IE indicates that the message assigns a Temporary Block Flow (TBF), the mobile station shall consider this information element present in the message. If the *Dedicated mode or TBF* IE indicates that this message is the first of two in a two-message assignment of an uplink or downlink TBF, the mobile station shall ignore the contents of this information element and regard it as an unnecessary IE. + +#### 9.1.18.0d Request Reference + +If this message is used in an assignment of a downlink TBF, the network shall code this information element, e.g. by using a suitably offset frame number, such that the resource reference cannot be confused with any CHANNEL REQUEST message sent by a mobile station. + +If the *IA Rest Octets* IE indicates that this message is the second message of a two-message assignment of an uplink or downlink TBF, this information element shall have the same contents as the first message of the assignment. + +When set to the value '0111 1111', the RA information of the Request Reference IE indicates that an Extended RA field may be included in the IA Rest Octets. The mobile station shall use the information in the Extended RA field to identify the Immediate Assignment message corresponding to an EGPRS Packet Channel Request message. If the Extended RA field is not included, the mobile station shall assume that the Immediate Assignment message does not correspond to the EGPRS Packet Channel Request message. + +A mobile station has enabled PEO and has sent an EGPRS MULTILATERATION REQUEST message indicating 'Access Burst' method or 'Extended Access Burst' method (see sub-clause 3.5.2.1.2 and sub-clause 3.11) shall ignore this field and instead examine the *Request Reference 1*, *Request Reference 2*, *Request Reference 3* and *Request Reference 4* information elements (as necessary) in attempt to find an IMMEDIATE ASSIGNMENT message (see Table 9.1.18.1a) that matches its transmitted message (see sub-clause 10.5.2.87). + +When the mobile station receives the IMMEDIATE ASSIGNMENT message encapsulated in the PACKET CS COMMAND message on the PACCH (see 3GPP TS 44.060), it shall ignore the contents of this information element and regard it as an unnecessary IE. + +#### 9.1.18.0e Timing Advance + +If the *IA Rest Octets* IE indicates that this message is the second message of a two-message assignment of an uplink or downlink TBF, the mobile station shall ignore the contents of this information element and regard it as an unnecessary IE. + +#### 9.1.18.1 Mobile Allocation + +If this message assigns a dedicated mode resource and the *Channel Description* IE does not indicate frequency hopping, the length indicator of this information element shall be set to zero, and the mobile station shall consider the IE as an unnecessary IE. + +If this message assigns a TBF and the *Packet Channel Description* IE does not indicate frequency hopping or if it uses indirect encoding of a hopping RF channel configuration, the length indicator of this information element shall be set to zero, and the mobile station shall consider the IE as an unnecessary IE. + +#### 9.1.18.2 Starting Time + +This information element appears if e.g. a frequency change is in progress. + +If this message is used in an assignment of an uplink or downlink TBF, the mobile station shall ignore the contents of the Starting Time information element if included and consider it as an unnecessary IE. + +#### 9.1.18.3 IA Rest Octets (Frequency parameters, before time) + +The sum of the length of this IE and the L2 Pseudo Length of the message equals 22. + +If the *starting time* IE is present but not the *frequency parameters, before time* construction, the mobile stations must wait until the starting time before accessing the channel. + +If the *starting time* IE is present and the *Channel Description* IE does not indicate frequency hopping the mobile station shall consider the *frequency parameters, before time* construction as unnecessary in the message and the mobile must wait until the starting time before accessing the channel. + +If the *starting time* IE is not present, the mobile station shall consider the *frequency parameters, before time* construction as unnecessary in the message. + +#### 9.1.18.4 IA Rest Octets (assignment of uplink or downlink TBF) + +If the *Dedicated mode or TBF* IE indicates that this message is used in an assignment of a TBF, this information element shall contain a *Packet Uplink Assignment, Packet Downlink Assignment, Second Part Packet Assignment* construction or *Multiple Blocks Packet Downlink Assignment* construction. + +If the *Dedicated mode or TBF* IE indicates that this message assigns a dedicated mode resource, but not that the mobile station is identified in the *IA Rest Octets* IE information element, the mobile station shall consider the *Packet Uplink Assignment, Packet Downlink Assignment, Second Part Packet Assignment and Multiple Blocks Packet Downlink Assignment* constructions as unnecessary in the message. + +#### 9.1.18.5 Extended TSC Set + +If the message is sent on the PACCH to a mobile station that indicates support for extended TSC sets (see 3GPP TS 24.008 [79]) this information element may be included to provide TSC related information for the assigned radio resources. In the absence of this information element the TSC related information provided by the *Channel Description* IE and *Packet Channel Description* IE shall apply. + +#### 9.1.18.6 Request Reference N + +A mobile station that has enabled PEO and has sent an EGPRS MULTILATERATION REQUEST message indicating the 'Access Burst' method or 'Extended Access Burst' method shall ignore the *Request Reference* information element and shall instead examine the *Request Reference 1, Request Reference 2, Request Reference 3 and Request Reference 4* information elements (as necessary) in attempt to find an IMMEDIATE ASSIGNMENT message (see Table 9.1.18.1a) that matches its transmitted EGPRS MULTILATERATION REQUEST message (see sub-clause 10.5.2.30 and sub-clause 10.5.2.87). + +A mobile station that has enabled PEO and has sent an EGPRS MULTILATERATION REQUEST message indicating the 'RLC Data Block' method or 'Page Response for Positioning Event' shall only examine the *Request* information element in attempt to find an IMMEDIATE ASSIGNMENT message (see Table 9.1.18.1a) that matches its transmitted EGPRS MULTILATERATION REQUEST message (i.e. it shall ignore all instances of the *Request Reference N* information element if included). + +#### 9.1.18a (void) + +#### 9.1.18b Immediate packet assignment + +This message is sent on the CCCH by the network to multiple mobile stations in idle mode to assign either an uplink or a downlink packet data channel configuration in the cell. In addition, this message is sent on the CCCH to a mobile station in packet idle mode when it has sent an EGPRS MULTILATERATION REQUEST message indicating 'RLC Data Block method' or 'Page Response for Positioning Event' (see table 9.1.18.1) or indicating 'Access Burst method' or 'Extended Access Burst method' (see sub-clause 3.5.2.1.2, sub-clause 3.11 and table 9.1.18.1a). + +See table 9.1.18b.1. + +The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the *IPA Rest Octets* and *L2 Pseudo Length* information elements. + +NOTE: The network should take into account limitations of certain mobile stations to understand IMMEDIATE PACKET ASSIGNMENT message as these mobile stations may not be able to decode the *Page Mode* information element. + +Message type: IMMEDIATE PACKET ASSIGNMENT + +Significance: dual + +Direction: network to mobile station + +Table 9.1.18b.1: IMMEDIATE PACKET ASSIGNMENT message content + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|------------------------------------------|------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Immediate Packet Assignment Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Feature Indicator | Feature Indicator
10.5.2.76 | M | V | 1/2 | +| | IPA Rest Octets | IPA Rest Octets
10.5.2.78 | M | V | 19 | +| 05 | Request Reference 1 | Request Reference Alt
10.5.2.87 | O | TV | 5 | +| 06 | Request Reference 2 | Request Reference Alt
10.5.2.87 | O | TV | 5 | +| 07 | Request Reference 3 | Request Reference Alt
10.5.2.87 | O | TV | 5 | +| 08 | Request Reference 4 | Request Reference Alt
10.5.2.87 | O | TV | 5 | + +### 9.1.19 Immediate assignment extended + +This message is sent on the CCCH by the network to two mobile stations in idle mode to change their channel configurations to different dedicated configurations while they stay in the same cell. See table 9.1.19.1 + +The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the *IPA Rest Octets* and *L2 Pseudo Length* information elements. + +Message type: IMMEDIATE ASSIGNMENT EXTENDED + +Significance: dual + +Direction: network to mobile station + +Table 9.1.19.1: IMMEDIATE ASSIGNMENT EXTENDED message content + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Immediate Assignment Extended Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Feature Indicator | Feature Indicator
10.5.2.76 | M | V | 1/2 | +| | Channel Description 1 | Channel Description
10.5.2.5 | M | V | 3 | +| | Request Reference 1 | Request Reference
10.5.2.30 | M | V | 3 | +| | Timing Advance 1 | Timing Advance
10.5.2.40 | M | V | 1 | +| | Channel Description 2 | Channel Description
10.5.2.5 | M | V | 3 | + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|---------------------|--------------------------------|----------|--------|--------| +| | Request Reference 2 | Request Reference
10.5.2.30 | M | V | 3 | +| | Timing Advance 2 | Timing Advance
10.5.2.40 | M | V | 1 | +| | Mobile Allocation | Mobile Allocation
10.5.2.21 | M | LV | 1-5 | +| 7C | Starting Time | Starting Time
10.5.2.38 | O | TV | 3 | +| | IAX Rest Octets | IAX Rest Octets
10.5.2.18 | M | V | 0-4 | + +NOTE: Index 1 refers to the first mobile station, index 2 refers to the second mobile station. + +#### 9.1.19.1 Unnecessary IEs + +A mobile station which reacts on the request reference 1 shall consider all information elements as unnecessary IEs except for *Requests Reference 1*, *Channel Description 1*, *Timing advance 1*, *Starting Time* and if *Channel Description 1* IE indicates frequency hopping mobile allocation. + +A mobile station which reacts on the request reference 2 shall consider all information elements as unnecessary IE except *Requests Reference 2*, *Channel Description 2*, *Timing advance 2*, *Starting Time* and if *channel description 2* IE indicates frequency hopping mobile allocation. + +A mobile station in idle mode shall consider all information elements as unnecessary IEs except for the *Page Mode* IE. + +#### 9.1.19.2 Mobile Allocation + +If both channel description IE do not indicate frequency hopping, the length indicator shall be set to zero. + +#### 9.1.19.3 Starting Time + +This information element appears if a frequency change is in progress. If included the starting time is common to the two referenced mobile stations. + +#### 9.1.19.4 Maximum message length + +As the maximum length of the resulting layer 3 data cannot exceed 22 octets, it is not possible to use this message type if the total length of the value part of the *Mobile Allocation* plus, optionally, the length of the *Starting Time* IE exceeds 5 octets. In this case it is necessary to use the IMMEDIATE ASSIGNMENT message. + +#### 9.1.19.5 IAX Rest Octets + +The sum of the length of this IE and the L2 Pseudo Length of the message equals 22. + +### 9.1.20 Immediate assignment reject + +This message is sent on the CCCH or encapsulated in the PACKET CS COMMAND message on the PACCH (see 3GPP TS 44.060) by the network to up to four mobile stations to indicate that no channel is available for assignment. See table 9.1.20.1. This message has L2 pseudo length 19. + +Message type: IMMEDIATE ASSIGNMENT REJECT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.20.1: IMMEDIATE ASSIGNMENT REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|------------------------------------------|--------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Immediate Assignment Reject Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Feature Indicator | Feature Indicator
10.5.2.76 | M | V | 1/2 | +| | Request Reference 1 | Request Reference
10.5.2.30 | M | V | 3 | +| | Wait Indication 1 | Wait Indication
10.5.2.43 | M | V | 1 | +| | Request Reference 2 | Request Reference
10.5.2.30 | M | V | 3 | +| | Wait Indication 2 | Wait Indication
10.5.2.43 | M | V | 1 | +| | Request Reference 3 | Request Reference
10.5.2.30 | M | V | 3 | +| | Wait Indication 3 | Wait Indication
10.5.2.43 | M | V | 1 | +| | Request Reference 4 | Request Reference
10.5.2.30 | M | V | 3 | +| | Wait Indication 4 | Wait Indication
10.5.2.43 | M | V | 1 | +| | IAR Rest Octets | IAR Rest Octets
10.5.2.17 | M | V | 3 | + +NOTE: Index 1 refers to the first mobile station, index 2 refers to the second MS and so on. + +#### 9.1.20.1 Use of the indexes + +A request reference information element and the following wait indication information element refer to the same mobile station. So it is possible to reject up to four channel requests with this message. + +#### 9.1.20.2 Filling of the message + +If necessary the request reference information element and the wait indication information element should be duplicated to fill the message. + +#### 9.1.20.2a Request Reference + +When set to the value '0111 1111', the RA information of the Request Reference i IE indicates that an Extended RA i field may be included in the IAR Rest Octets. The mobile station shall use the information in the Extended RA i field to identify the Immediate Assignment Reject message corresponding to an EGPRS Packet Channel Request message. If the Extended RA i field is not included, the mobile station shall assume that the Request Reference i IE does not correspond to the EGPRS Packet Channel Request message. + +When the mobile station receives the IMMEDIATE ASSIGNMENT REJECT message encapsulated in the PACKET CS COMMAND message on the PACCH (see 3GPP TS 44.060), it shall ignore the contents of all the Request Reference i IEs and regard them as unnecessary IEs. + +#### 9.1.20.3 Wait Indication + +When IMMEDIATE ASSIGNMENT REJECT message is for RR connection establishment then this IE contains timeout value for T3122. If IMMEDIATE ASSIGNMENT REJECT message is for TBF establishment for GPRS MS then this IE contain timeout value for T3142. + +When the mobile station receives the IMMEDIATE ASSIGNMENT REJECT message encapsulated in the PACKET CS COMMAND message on the PACCH (see 3GPP TS 44.060), it shall ignore the contents of the Wait Indication 2, 3 and 4 IEs and regard them as unnecessary IEs. + +#### 9.1.20.4 IAR Rest Octets + +The sum of the length of this IE and the L2 Pseudo Length of the message equals 22. + +### 9.1.21 Measurement report + +This message is sent on the SACCH by the mobile station to the network to report measurement results about the dedicated channel and about neighbour cells. See table 9.1.21.1. + +Message type: MEASUREMENT REPORT + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.21.1: MEASUREMENT REPORT message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Measurement Report Message Type | Message Type 10.4 | M | V | 1 | +| | Measurement Results | Measurement Results 10.5.2.20 | M | V | 16 | + +#### 9.1.21a Notification/FACCH + +The understanding of this message is only required for mobile stations supporting VGCS listening or VBS listening. + +This message is sent on the main DCCH, in unacknowledged mode using the RR short protocol discriminator by the network to notify the mobile stations in dedicated mode or in on-going voice broadcast calls or voice group calls on other voice broadcast calls or voice group calls in that cell. + +Notification/FACCH messages for VBS or VGCS calls are differentiated by a flag in the call reference. + +It is possible in the case of a notification for a ciphered VGCS/VBS call that the notification cannot be described within one Notification/FACCH message. In this case a second message may be used to contain the group call reference, a VSTK\_RAND, possibly the CELL\_GLOBAL\_COUNT and bit 22 of COUNT. The group channel description shall be in the first segment. + +Mobile stations not supporting VGCS listening or VBS listening shall ignore this message. + +See table 9.1.21a.1. + +Message type: NOTIFICATION/FACCH + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.21a.1: NOTIFICATION/FACCH message content** + +``` + ::= + -- See 3GPP TS 24.007 + -- See 10.4 + -- See 3GPP TS 44.006 + { + 0 + |1 + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 6 : + } +``` + +``` + + { 0|1 + } + { 0|1 } + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 7 : + + + { 0|1 } + { 0|1 } + { 0|1 < SMS Data Confidentiality Ind : bit (1)> + < SMS Guaranteed Privacy Ind : bit (1)> + } + } + ; + + ::= + + {0|1 } ; + + ::= + -- RACH access + | ; -- Group Channel access + + ::= + -- emergency mode not set + | ; -- emergency mode set + +``` + +##### + +This field is syntactically and semantically equivalent to octets 2-5 and bits 5 to 8 of octet 6 of the *Descriptive Group or Broadcast Call Reference* information element as defined in 3GPP TS 24.008. + +The field is optionally present. When present only the Channel description is provided in the case of non hopping channels or if, when used in the SI10bis Rest Octets, the Frequency List is included. In the case where the channel is hopping (and, in the case of SI10bis Rest Octets, no Frequency List is included) then either a mobile allocation or a frequency short list is provided. + +``` + + : ::= + + { 0 + |1 { 0 > + |1 } + }; + ::= null | bit ; + +``` + +##### + +This field is syntactically and semantically equivalent to octets 3-5 of the *Group Channel Description* information element. See sub-clause 10.5.2.14b. + +##### + +This field is syntactically and semantically equivalent to octets 1-8 of the *Frequency Short List 2* information element. See sub-clause 10.5.2.14a. + +##### + +This field is syntactically and semantically equivalent to octet 2 to n+2 of the *Mobile Allocation* information element. See sub-clause 10.5.2.21. + +The field may be used to inform the mobile station in Group Receive or in Group Transmit mode that the corresponding mobile identity is paged in that cell. + +``` + + ::= + > + + {0|1 } ; + +``` + +| | +|--------------------------------------------| +| ::= null bit ; | +|--------------------------------------------| + +##### + +This field is syntactically and semantically equivalent to octet 2-n of the *Mobile Identity* information element. See sub-clause 10.5.1.4. + +##### + +This field is syntactically and semantically equivalent to bits 1 and 2 of the *Channel Needed* information element. See sub-clause 10.5.2.8. + +##### + +This field is coded as the field in the *PI Rest Octets* information element. See sub-clause 10.5.2.23. + +##### + +The 36-bit value that is used for derivation of a short term key VSTK, as defined in 3GPP TS 43.020. This parameter is only provided when the group call reference is present and the group call is ciphered. + +##### + +This field contains the value of the CELL\_GLOBAL\_COUNT that is used by the VGCS/VBS ciphering mechanism. The value is incremented by one (modulo 4) each time bit 22 of COUNT ( defined in 3GPP TS 43.020) changes from '1' to '0'. + +##### + +This field contains the value of bit 22 of COUNT (see 3GPP TS43.020) corresponding to the moment when the value of was valid. + +##### + +Indicates the method to be used for priority uplink access. + +##### Bit + +- | | | +|---|----------------| +| L | RACH access | +| H | Group Channel. | + +##### + +This field indicates the status of the emergency mode for the group call. + +- | | | +|---|-------------------------| +| L | Emergency mode not set. | +| H | Emergency mode set. | + +##### + +This field indicates the set of AMR codec modes to be used on a group channel using speech version 3. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92]. + +##### + +This field indicates whether the paging contained in the field 'Paging Information' is for a mobile terminating call, USSD or short message. Mobile stations shall ignore the contents of this field when the notification does not contain paging information. + +##### bit + +##### 2 1 + +- | | | +|-----|--------------------------------------------------------------------------| +| 0 0 | Paging is for a mobile terminating call | +| 0 1 | Paging is for a mobile terminating short message. | +| 1 0 | Paging is for a USSD | +| 1 1 | Spare – if received, mobile shall treat as for a mobile terminating call | + +##### **** + +This field shall be included periodically (the frequency with which this field is included is implementation dependent) if the network supports the transfer of mobile originated point-to-point short messages via the group call channel. The value is provided by the network (see 3GPP TS 43.068). + +If this field is not present the most recently received value in either a Notification/FACCH message or Notification/NCH message shall be used. If no previous value has been received, a default value of "1" shall be assumed. + +- 0 SMS data confidentiality not required. +- 1 SMS data confidentiality required. + +##### **** + +This field shall be included periodically (the frequency with which this field is included is implementation dependent) if the network supports the transfer of mobile originated point-to-point short messages via the group call channel. The value is provided by the network (see 3GPP TS 43.068). + +If this field is not present the most recently received value in either a Notification/FACCH message or Notification/NCH message shall be used. If no previous value has been received, a default value of "1" shall be assumed. + +- 0 SMS guaranteed privacy not required. +- 1 SMS guaranteed privacy required. + +9.1.21a.1 (void) + +9.1.21a.2 (void) + +9.1.21a.3 (void) + +9.1.21a.4 (void) + +#### 9.1.21b Notification/NCH + +The understanding of this message is only required for mobile stations supporting VGCS listening or VBS listening. + +This message is sent on the NCH by the network to notify mobile stations of VBS or VGCS calls in the current cell. The VBS or VGCS calls are identified by their broadcast call reference or group call reference, respectively. For each reference, the corresponding VBS or VGCS call channel may be indicated. See table 9.1.21b.1. + +Notification/NCH messages for VBS or VGCS calls are differentiated by a flag in the call reference. + +The L2 pseudo length of this message has a value one. + +It is possible in the case of a notification for a ciphered VGCS/VBS call that the notification cannot be described within one message. In this case a second message may be used to contain the group call reference, a VSTK\_RAND, and possibly CELL\_GLOBAL\_COUNT. The Group channel description shall be included in the first segment. + +Mobile stations not supporting VGCS listening or VBS listening shall ignore this message. + +Message type: NOTIFICATION/NCH +Significance: dual +Direction: network to mobile station + +**Table 9.1.21b.1: NOTIFICATION/NCH message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|--------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Notification/NCH Message Type | Message Type
10.4 | M | V | 1 | +| | NT/N Rest Octets | NT/N Rest Octets
10.5.2.22c | M | V | 20 | + +9.1.21b.1 (void) + +9.1.21b.2 (void) + +9.1.21c (void) + +#### **9.1.21d Notification response** + +This message is sent by the mobile station to the network to respond on a notification for a voice group call or voice broadcast call. See table 9.1.21d.1. + +Message type: NOTIFICATION RESPONSE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.21d.1: NOTIFICATION RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------|-----------------------------------------------------------|----------|--------|--------| +| | RR management Protocol discriminator | Protocol discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Notification response Message type | Message type
10.4 | M | V | 1 | +| | Mobile station Classmark | Mobile station classmark 2
10.5.1.6 | M | LV | 4 | +| | Mobile identity | Mobile identity
10.5.1.4 | M | LV | 2-9 | +| | Group or broadcast Call reference | Descriptive group or broadcast call reference
10.5.1.9 | M | V | 5 | + +#### 9.1.21e (void) + +#### 9.1.21f Packet Assignment + +This message is sent on the FACCH by the network to the mobile station to change the channel configuration to a multislot configuration with CS and PS connections when neither timing adjustment nor reallocation of the CS timeslot is needed. See table 9.1.21f.1. + +Message type: PACKET ASSIGNMENT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.21f.1: PACKET ASSIGNMENT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------------------------|-------------------------------------------------|----------|--------|---------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Packet Assignment Message Type | Message Type 10.4 | M | V | 1 | +| | GPRS broadcast information | GPRS broadcast information 10.5.2.14d | M | LV | 7 - n | +| 22 | Description of the Uplink Packet Channel Assignment | RR Packet Uplink Assignment 10.5.2.25c | O | TLV | 3 - n | +| 23 | Description of the Downlink Packet Channel Assignment | RR Packet Downlink Assignment 10.5.2.25d | O | TLV | 3 - n | +| 12 | Frequency List C2 | Frequency List 10.5.2.13 | C | TLV | 4 - 132 | +| 13 | Mobile Allocation C2 | Mobile Allocation 10.5.2.21 | C | TLV | 3 - 10 | +| 14 | Channel Description C2 | Channel Description 3 10.5.2.5c | O | TV | 3 | +| 24 | Description of the Downlink Packet Channel Assignment Type 2 | RR Packet Downlink Assignment Type 2 10.5.2.25e | C | TLV | 3 - n | +| 6D | Extended TSC Set | Extended TSC Set 10.5.2.82 | C | TV | 2 | + +#### 9.1.21f.1 RR Packet Uplink Assignment and RR Packet Downlink Assignment IEs + +These information elements are optional, but at least one of them shall be present. + +#### 9.1.21f.2 (void) + +#### 9.1.21f.3 Frequency List C2, Mobile Allocation C2 and Description of the Downlink Packet Channel Assignment Type 2 + +These information elements may be included to assign packet resources on a second radio frequency channel, which does not include the dedicated resource, to a mobile station supporting Downlink Dual Carrier (see 3GPP TS 44.060). + +If the *Channel Description C2* IE is present, the *Description of the Downlink Packet Channel Assignment Type 2* IE shall be present and provides the description of the downlink packet resources for both carriers C1 and C2. In this case, the *Description of the Downlink Packet Channel Assignment* IE shall not be included. + +If the *Channel Description C2* IE is present and indicates frequency hopping, one and only one of the following information elements shall be present: + +- *Mobile Allocation C2* IE +- *Frequency List C2* IE + +If the *Mobile allocation C2* IE is present, then the network must ensure that the mobile station has received in a previous message the proper reference cell frequency list. + +If the *Channel Description C2* IE is not included then the *Description of the Downlink Packet Channel Assignment Type 2* IE if present shall be considered as an unnecessary IE in the message. + +If the *Channel Description C2* IE is not included or is included but does not indicate frequency hopping, then any of the *Mobile Allocation C2* or *Frequency List C2* IEs if present shall be considered as an unnecessary IE in the message. + +#### 9.1.21f.4 Extended TSC Set + +If the message is sent to a mobile station that indicates support for extended TSC sets (see 3GPP TS 24.008 [79]) this information element may be included to provide TSC related information for the assigned radio resources. In the absence of this information element the TSC related information provided by the *Channel Description 3* IE shall apply. + +### 9.1.21g Packet Notification + +This message is sent on the main DCCH by the network to trigger the mobile station to perform a cell update procedure. See table 9.1.21g.1. + +Message type: PACKET NOTIFICATION + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.21g.1: PACKET NOTIFICATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------|--------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Packet Notification Message Type | Message Type
10.4 | M | V | 1 | +| 10 | Packet TMSI | P-TMSI
10.5.2.42 | C | TV | 5 | +| 11 | Mobile identity | Mobile identity
10.5.1.4 | C | TLV | 3-11 | + +#### 9.1.21g.1 P-TMSI + +If this IE is included the *Mobile identity* IE shall not be included. + +NOTE: The condition when to include P-TMSI in this message is defined in TS 48.018. + +#### 9.1.21g.2 Mobile identity + +This IE shall be included if and only if the *P-TMSI* IE is not included. + +### 9.1.21h VBS/VGCS reconfigure + +This message is sent on the main DCCH, in unacknowledged mode (to mobile stations in group receive mode) or acknowledged mode (to mobile stations in group transmit mode) using the RR short protocol discriminator by the network to notify mobile stations in an on-going voice broadcast calls or voice group calls of a change to the current VBS/VGCS channel description with a starting time. + +Mobile stations not supporting VBS or VGCS shall ignore this message. + +See table 9.1.21h.1. + +Message type: VBS/VGCS RECONFIGURE + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.21h.1: VBS/VGCS RECONFIGURE message content** + +``` + ::= + -- See 3GPP TS 24.007 + -- See 10.4 + -- See 3GPP TS 44.006 + + + + { null | 0 bit** = }- Receiver backward compatible with earlier version +``` + +#### + +This field provides only the Channel description in the case of non hopping channels. In the case where the channel is hopping either a mobile allocation or a frequency short list is provided. + +``` + ::= + + { 0 -- Non hopping case + | 1 { 0 > + | 1 } ; + + ::= null | bit ; +``` + +#### + +This field is syntactically and semantically equivalent to octets 3-5 of the *Group Channel Description* information element. See sub-clause 10.5.2.14b. + +#### + +This field is syntactically and semantically equivalent to octets 1-8 of the *Frequency Short List 2* information element. See sub-clause 10.5.2.14a. + +#### + +This field is syntactically and semantically equivalent to octet 2 to n+2 of the *Mobile Allocation* information element. See sub-clause 10.5.2.21. + +#### + +This field defines a starting time at which the new VBS or VGC channel description takes effect. The starting time field is coded as the V format of the type 3 information element *Starting Time*. See sub-clause 10.5.2.38. + +#### + +This field indicates that a VBS/VGCS RECONFIGURE2 message with a *Cell Channel Description* follows the VBS/VGCS RECONFIGURE message. If this field is set to '0' then cell channel description is assumed to be unchanged and no VBS/VGCS RECONFIGURE2 follows. + +#### 9.1.21i VBS/VGCS reconfigure2 + +This message follows the VBS/VGCS RECONFIGURE message. + +This message is sent on the main DCCH, in unacknowledged mode (to mobile stations in group receive mode) or acknowledged mode (to mobile stations in group transmit mode) using the RR short protocol discriminator by the network to additionally notify mobile stations in an on-going voice broadcast calls or voice group calls of a change to the current cell channel description with a starting time. + +Mobile stations not supporting VBS or VGCS shall ignore this message. + +See table 9.1.21i.1. + +Message type: VBS/VGCS RECONFIGURE2 + Significance: dual + Direction: network to mobile station + +**Table 9.1.21i.1: VBS/VGCS RECONFIGURE2 message content** + +``` + ::= + -- See 3GPP TS 24.007 + -- See 10.4 + -- See 3GPP TS 44.006 + + + { null | 0 bit** = < no string > } - Receiver backward compatible with earlier version +``` + +#### + +This field is syntactically and semantically equivalent to octets 2-17 of the *Cell Channel Description* information element. This information element shall be used to decode the *Mobile Allocation* IE in the VBS/VGCS RECONFIGURE message. See sub-clause 10.5.2.1b. + +##### + +This field defines a starting time at which the new *Cell Channel Description* takes effect. The starting time field is coded as the V format of the type 3 information element *Starting Time*. See sub-clause 10.5.2.38. + +### 9.1.21j MBMS Announcement + +This message is sent on the main DCCH by the network to inform the mobile station about a starting MBMS Session or an ongoing MBMS Broadcast Session with an updated MBMS service area list. See table 9.1.21j.1. + +Message type: MBMS ANNOUNCEMENT + Significance: dual + Direction: network to mobile station + +**Table 9.1.21j.1: MBMS Announcement message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------|------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | MBMS Announcement Type | Message Type 10.4 | M | V | 1 | +| | Temporary Mobile Group Identity | TMGI 10.5.6.13 | M | LV | 4-7 | +| 01 | MBMS Session Identity | MBMS Session Identity 10.5.2.62 | O | TV | 2 | +| 02 | MBMS Counting Channel Description | MPRACH Description 10.5.2.60 | O | TLV | 3-n | +| 03 | MBMS p-t-m Channel Description | MBMS p-t-m Channel Description 10.5.2.58 | O | TLV | 4-n | +| 04 | MBMS Session Parameters List | MBMS Session Parameters List 10.5.2.58a | O | TLV | 4-7 | +| 05 | Restriction Timer | Restriction Timer 10.5.2.61 | O | TV | 2 | + +### 9.1.22 Paging request type 1 + +This message is sent on the CCCH by the network and may identify up to two mobile stations. It may be sent to a mobile station in idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure) or to perform an MBMS pre-notification or an MBMS notification. It may be sent to mobile stations in idle mode to transfer the segments of an ETWS Primary Notification message. The mobile stations are identified by their TMSI/P-TMSI or IMSI. If an MBMS (pre)notification is included in this message, the corresponding TMGI and, if available, MBMS Session Identity shall be included within Mobile Identity 1 or 2 IEs, or if Mobile Identity 1 and 2 IEs are not available, within the *P1 Rest Octets*. The remaining information pertinent to an MBMS notification may only be included within the *P1 Rest Octets*. See table 9.1.22.1. + +The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the *P1 Rest Octets* and *L2 Pseudo Length* information elements. + +The P1 Rest Octets may contain a notification for a VGCS/VBS call or a segment of an ETWS Primary Notification message. + +It is possible in the case of a notification for a ciphered VGCS/VBS call that the notification cannot be described within one message. When the notification is segmented across two messages, the first message shall contain the group channel description whilst the second message can be used to contain the group call reference, the VSTK\_RAND and possibly the CELL\_GLOBAL\_COUNT. The second message shall be sent at the next but one PCH block after the PCH block containing the first message. + +Message type: PAGING REQUEST TYPE 1 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.22.1: PAGING REQUEST TYPE 1 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|--------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Paging Request Type 1 Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Channels Needed for Mobiles 1 and 2 | Channel Needed
10.5.2.8 | M | V | 1/2 | +| | Mobile Identity 1 | Mobile Identity
10.5.1.4 | M | LV | 2-9 | +| 17 | Mobile Identity 2 | Mobile Identity
10.5.1.4 | O | TLV | 3-10 | +| | P1 Rest Octets | P1 Rest Octets
10.5.2.23 | M | V | 0-17 | + +#### 9.1.22.1 Unnecessary IE + +A mobile station in idle mode shall consider all information elements as unnecessary IEs except for the *Page Mode* IE. + +#### 9.1.22.2 Channels needed for Mobiles 1 and 2 + +The first CHANNEL field of *Channel Needed* IE is associated with *Mobile Identity 1*. The second CHANNEL field of *Channel Needed* IE is associated with *Mobile Identity 2*. + +If this message is used in the packet paging procedure, the *Channel Needed* IE associated with the corresponding *Mobile Identity 1* or 2 shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet paging request shall treat this information element as unnecessary in the message. + +#### 9.1.22.3 Mobile Identities + +The *Mobile Identity 1* and *2* IEs shall not refer to IMEI. + +#### 9.1.22.4 P1 Rest Octets + +The sum of the length of this IE and the L2 Pseudo Length of the message equals 22. + +This IE may contain a *notification list number* field and/or, referring respectively to the *Mobile Identity 1* IE and, if present, to the *Mobile Identity 2* IE, a *Priority 1* and a *Priority 2* field(s), and/or a *Packet Page Indication 1* and a *Packet Page Indication 2* field(s), or an *MBMS Notification 1* and/or an *MBMS Notification 2* field(s), and MBMS Information, or a segment of an ETWS Primary Notification message. + +### 9.1.23 Paging request type 2 + +This message is sent on the CCCH by the network and may identify two mobile station and, possibly, either a third mobile station or an MBMS session. It may be sent to a mobile station in idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure) or to perform an MBMS pre-notification or an MBMS notification. Two of the mobile stations are identified by their TMSI/P-TMSI while the third is identified by its TMSI/P-TMSI or IMSI. If an MBMS (pre)notification is included in this message, the corresponding TMGI and, if available, MBMS Session Identity shall be included within Mobile Identity 3 IE, or if Mobile Identity 3 IE is not available, within the *P2 Rest Octets*. The remaining information pertinent to an MBMS notification may only be included within the *P2 Rest Octets*. See table 9.1.23.1. + +The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the *P2 Rest Octets* and *L2 Pseudo Length* information elements. + +Message type: PAGING REQUEST TYPE 2 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.23.1: PAGING REQUEST TYPE 2 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|--------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Paging Request Type 2 Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Channels Needed for Mobiles 1 and 2 | Channel Needed
10.5.2.8 | M | V | 1/2 | +| | Mobile Identity 1 | TMSI/P-TMSI
10.5.2.42 | M | V | 4 | +| | Mobile Identity 2 | TMSI/P-TMSI
10.5.2.42 | M | V | 4 | +| 17 | Mobile Identity 3 | Mobile Identity
10.5.1.4 | O | TLV | 3-10 | +| | P2 Rest Octets | P2 Rest Octets
10.5.2.24 | M | V | 1-11 | + +#### 9.1.23.1 Channels needed for Mobiles 1 and 2 + +The first CHANNEL field of Channel Needed IE is associated with Mobile Identity 1. The second CHANNEL field of *Channel Needed* IE is associated with *Mobile Identity 2*. + +If this message is used in the packet paging procedure, the *Channel Needed* IE associated with the corresponding *Mobile Identity 1 or 2* shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet paging request shall treat this information element as unnecessary in the message. + +#### 9.1.23.2 Mobile Identity 3 + +The *Mobile Identity 3* information element shall not refer to IMEI. + +#### 9.1.23.3 P2 Rest Octets + +The sum of the length of this IE and the L2 Pseudo Length of the message equals 22. + +This IE contains the channel needed indication related to the paging of *Mobile Identity 3*. The treatment of this indication in the case this message is used in a packet paging procedure is specified in sub-clause 9.1.23.1. + +This IE may further contain a *notification list number* field and/or, referring respectively to the *Mobile Identity 1* and *Mobile Identity 2* IEs and, if present, *Mobile Identity 3* IE, a *Priority 1, 2 and 3* fields and/or, referring to the *Mobile Identity 3* IE, a *Packet Page Indication 3* field, or an *MBMS Notification 3* field, and MBMS Information. + +### 9.1.24 Paging request type 3 + +This message is sent on the CCCH by the network to four mobile stations. It may be sent to a mobile station in idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure). The mobile stations are identified by their TMSIs/P-TMSIs. See table 9.1.24.1. + +This message has a L2 Pseudo Length of 19. + +Message type: PAGING REQUEST TYPE 3 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.24.1: PAGING REQUEST TYPE 3 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|--------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Paging Request Type 3 Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Channels Needed for Mobiles 1 and 2 | Channel Needed
10.5.2.8 | M | V | 1/2 | +| | Mobile Identity 1 | TMSI/P-TMSI
10.5.2.42 | M | V | 4 | +| | Mobile Identity 2 | TMSI/P-TMSI
10.5.2.42 | M | V | 4 | +| | Mobile Identity 3 | TMSI/P-TMSI
10.5.2.42 | M | V | 4 | +| | Mobile Identity 4 | TMSI/P-TMSI
10.5.2.42 | M | V | 4 | +| | P3 Rest Octets | P3 Rest Octets
10.5.2.25 | M | V | 3 | + +#### 9.1.24.1 Channels needed for Mobiles 1 and 2 + +The first CHANNEL field of *Channel Needed* IE is associated with *Mobile Identity 1*. The second CHANNEL field of *Channel Needed* IE is associated with *Mobile Identity 2*. + +If this message is used in the packet paging procedure, the *Channel Needed* IE associated with the corresponding *Mobile Identity 1 or 2* shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet paging request shall treat this information element as unnecessary in the message. + +#### 9.1.24.2 P3 Rest Octets + +This IE contains the channel needed indication related to the paging of *Mobile Identity 3 and 4*. The treatment of these indications in the case this message is used in a packet paging procedure is specified in sub-clause 9.1.24.1. + +This IE may further contain a *notification list number* field and/or, referring to each one of the *Mobile Identity 1, 2, 3 and 4* IEs, a *Priority 1, 2, 3 and 4* field. + +### 9.1.25 Paging response + +This message is sent on the main DCCH by the mobile station to the network in connection with establishment of the main signalling link as a response to the paging request message. See table 9.1.25.1. + +Message type: PAGING RESPONSE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.25.1: PAGING RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|--------------------------------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Paging Response Message Type | Message Type
10.4 | M | V | 1 | +| | Ciphering Key Sequence Number | Ciphering Key Sequence Number
10.5.1.2 | M | V | 1/2 | +| | Spare Half Octet | Spare Half Octet
10.5.1.8 | M | V | 1/2 | +| | Mobile Station Classmark | Mobile Station Classmark 2
10.5.1.6 | M | LV | 4 | +| | Mobile Identity | Mobile Identity
10.5.1.4 | M | LV | 2-9 | +| C- | Additional update parameters | Additional update parameters
TS 24.008 [79] clause
10.5.3.14 | O | TV | 1 | + +#### 9.1.25.1 Mobile Station Classmark + +This IE shall include for multiband mobile station the Classmark 2 corresponding to the frequency band in use. + +#### 9.1.25.2 Additional Update Parameters + +The MS shall include this IE during CS fallback for a mobile terminating call (see subclause 3.3.2.2). + +### 9.1.26 Partial release + +This message is sent on the main DCCH by the network to the mobile station to deactivate part of the dedicated channels in use. See table 9.1.26.1. + +Message type: PARTIAL RELEASE + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.26.1: PARTIAL RELEASE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Partial Release Message Type | Message Type 10.4 | M | V | 1 | +| | Channel Description | Channel Description 10.5.2.5 | M | V | 3 | + +#### 9.1.26.1 Channel Description + +This information element describes the channel to be released. + +### 9.1.27 Partial release complete + +This message is sent on the main DCCH by the mobile station to the network to indicate that a part of the dedicated channels has been deactivated. See table 9.1.27.1. + +Message type: PARTIAL RELEASE COMPLETE + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.27.1: PARTIAL RELEASE COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|---------------------------------------|-----------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Partial release Complete Message Type | Message Type 10.4 | M | V | 1 | + +### 9.1.28 Physical information + +This message is sent on the main DCCH by the network to the mobile station to stop the sending of access bursts from the mobile station. See table 9.1.28.1. + +Message type: PHYSICAL INFORMATION + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.28.1: PHYSICAL INFORMATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-----------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Physical Information Message Type | Message Type 10.4 | M | V | 1 | +| | Timing Advance | Timing Advance 10.5.2.40 | M | V | 1 | + +#### 9.1.28a (void) + +### 9.1.29 RR Status + +This message is sent by the mobile station or the network at any time to report certain error conditions as described in clause 8. See table 9.1.29.1. + +Message type: RR STATUS + +Significance: local + +Direction: both + +**Table 9.1.29.1: RR STATUS message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|--------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | RR Status Message Type | Message Type
10.4 | M | V | 1 | +| | RR Cause | RR Cause
10.5.2.31 | M | V | 1 | + +#### 9.1.30a Synchronization channel information + +This message is sent on the SCH, which is one of the broadcast channels (ref. 3GPP TS 45.002). Its purpose is to support the synchronization of a mobile station to a BSS. It does not follow the basic format. Its length is 25 bits. The order of bit transmission is defined in 3GPP TS 44.004. See figure 9.1.30a.1 and table 9.1.30a.1. + +Message type: SYNCHRONIZATION CHANNEL INFORMATION + +Significance: dual + +Direction: network to mobile station + +![](db7ae70402c81d140ae7df14b002e057_img.jpg) + +| | | | | | | | | | +|-------------|----|---|---|---|------------|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| BSIC | | | | | T1 (high) | | | octet 1 | +| T1 (middle) | | | | | | | | octet 2 | +| T1 (low) | T2 | | | | T3' (high) | | | octet 3 | +| | | | | | | | | T3' (low) | + +**Figure 9.1.30a.1: Frame synchronization information element** + +**Table 9.1.30a.1: Synchronization channel information message contents** + +**BSIC**, the base station identity code of the base station + +**T1, T2 and T3'**, the 3 parts of the reduced TDMA frame number (RFN) as specified in 3GPP TS 45.002. + +#### 9.1.30b COMPACT Synchronization channel information + +This message is sent on the CSCH, which is one of the broadcast channels (ref. 3GPP TS 45.002). Its purpose is to support the synchronization of a COMPACT mobile station to a BSS. It does not follow the basic format. Its length is 25 bits. The order of bit transmission is defined in 3GPP TS 44.004. See figure 9.1.30b.1 and table 9.1.30b.1. + +Message type: COMPACT SYNCHRONIZATION CHANNEL INFORMATION + +Significance: dual + +Direction: network to mobile station + +![](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +| | | | | | | | | | | +|--|----------|---|---|---|---|---|-----------|-------|---------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | BSIC | | | | | | R1 (high) | | octet 1 | +| | R1 (low) | | | | | | | | octet 2 | +| | R2 | | | | | | TG | | octet 3 | +| | | | | | | | | spare | | + +**Figure 9.1.30b.1: COMPACT Frame synchronization information element** + +**Table 9.1.30b.1: COMPACT Synchronization channel information message contents** + +**BSIC**, the base station identity code of the base station + +**R1 and R2**, the 2 parts of the reduced TDMA frame number (RFN) as specified in 3GPP TS 45.002. + +**TG**, the time group as specified in 3GPP TS 45.002. + +#### 9.1.30c EC-SCH INFORMATION + +This message is sent on the EC-SCH, which is one of the broadcast channels (ref. 3GPP TS 45.002). Its purpose is to support the synchronization of an EC capable mobile station to a BSS when a cell supports EC operation (i.e. the presence of the EC-SCH indicates that EC operation is supported in the cell). It does not follow the basic format. Its length is 30 bits (see 3GPP TS 45.003). The order of bit transmission is defined in 3GPP TS 44.004. See figure 9.1.30c.1 and table 9.1.30c.1. + +Message type: EC-SCH INFORMATION + +Significance: dual + +Direction: network to mobile station + +![](ead623e6a8ec701df64567695a57d01c_img.jpg) + +| Octet no. | Bit number | | | | | | | | +|-----------|---------------------|---------------------|-----------|---|------------------------|---|-----------|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | T1' (hi) | | BSIC (hi) | | | | | | +| 2 | T2' (hi) | | T1' (low) | | | | | | +| 3 | RACH Access Control | EC-BCCH CHANGE MARK | | | Implicit Reject Status | | T2' (low) | | +| 4 | BSIC (low) | | | | IMM CGI | | | | + +**Figure 9.1.30c.1: EC-SCH INFORMATION message information elements, if sent in 51-multiframe M with $M \bmod 8 = 0, 1, 2, 3$ .** + +![](d5918cee231b536f20789a18d861fae3_img.jpg) + +| Octet no. | Bit number | | | | | | | | +|-----------|---------------------|---------------------|-----------|---|------------------------|---|-----------|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 1 | T1' (hi) | | BSIC (hi) | | | | | | +| 2 | T2' (hi) | | T1' (low) | | | | | | +| 3 | RACH Access Control | EC-BCCH CHANGE MARK | | | Implicit Reject Status | | T2' (low) | | + +| | | | | +|---|------------|--------|-------| +| 4 | BSIC (low) | IMM CM | Spare | +|---|------------|--------|-------| + +**Figure 9.1.30c.1a: EC-SCH INFORMATION message information elements, if sent in 51-multiframe M with $M \bmod 8 = 4,5,6,7$ .** + +**Table 9.1.30c.1: EC-SCH INFORMATION message contents** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

BSIC, base station identity code is a 9 bit field identifying the base station (see 3GPP TS 45.002).

T1' and T2', these are 2 parts of the reduced TDMA frame number per quarter hyperframe (RFNQH) as specified in 3GPP TS 45.002[32].

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

RACH Access Control is a 1 bit field, is only applicable to mobile stations that have selected CC1 on both the uplink and downlink (i.e. all other mobile stations shall ignore this field) and is coded as follows:

0: A mobile station that has selected CC1 in both uplink and downlink shall use the EC_CCCH_GROUP (i.e. one of timeslots 1, 3, 5 or 7 - see 3GPP TS 45.002 [32]) to transmit the EC PACKET CHANNEL REQUEST

1: A mobile station that has selected CC1 in both uplink and downlink shall use timeslot 0 to transmit the EC PACKET CHANNEL REQUEST

| +|

EC-BCCH CHANGE MARK is a 3 bit field that operates as a modulo 8 counter and is therefore incremented each time the content of any of the EC SYSTEM INFORMATION messages is changed. An exception is when PLMN specific access barring is enabled (see sub-clause 3.5.2a) for a given set of PLMNs and changes are made only to the EC Access Control Class field or the Exception Report Status field corresponding to this set of PLMNs in which case the EC-BCCH CHANGE MARK field is not incremented.

| +|

Implicit Reject Status is a 2 bit field and is coded as follows:

00: no barring

01: roamer barring enabled for all mobile stations that are neither in their HPLMN nor in a PLMN that is equivalent to it (see 3GPP TS 22.011 [6]).

10: roamer barring enabled for all mobile stations that are neither in the PLMN listed as most preferred PLMN of the country where the MS is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in an PLMN that is equivalent to it (see 3GPP TS 22.011 [6]).

11: all mobile stations barred. Only applies to MS with Access Class 0 to 9 (see 3GPP TS 22.011)

| +|

IMM CGI is a 3 bit field that provides the IMM Cell Group Identifier (see subclause 9.1.43q) and is coded as follows:

000: IMM Cell Group Definition is not broadcasted or not supported in the cell.

001: Cell belongs to IMM Cell Group Identity 1.

010: Cell belongs to IMM Cell Group Identity 2.

...

111: Cell belongs to IMM Cell Group Identity 7.

| +|

IMM CM is a 2 bit field that identifies the change mark of the IMM Cell Group (see subclause 9.1.43q) and is coded as follows, if IMM CGI has a different value from "000":

00: IMM Change Mark value is 0

01: IMM Change Mark value is 1

10: IMM Change Mark value is 2

11: IMM Change Mark value is 3

Otherwise, if IMM CGI has the value "000", these bits shall be ignored.

| + +### 9.1.31 System information type 1 + +This message is sent on the BCCH by the network to all mobile stations within the cell giving information of control of the RACH and of the cell allocation. See table 9.1.31.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. This message has a L2 Pseudo Length of 21. + +Message type: SYSTEM INFORMATION TYPE 1 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.31.1: SYSTEM INFORMATION TYPE 1 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|---------------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 1 Message Type | Message Type
10.4 | M | V | 1 | +| | Cell Channel Description | Cell Channel Description
10.5.2.1b | M | V | 16 | +| | RACH Control Parameter | RACH Control Parameters
10.5.2.29 | M | V | 3 | +| | SI 1 Rest Octets | SI 1 Rest Octets
10.5.2.32 | M | V | 1 | + +### 9.1.32 System information type 2 + +This message is sent on the BCCH by the network to all mobile stations within the cell giving information of control of the RACH and of the BCCH allocation in the neighbour cells. See table 9.1.32.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. This message has a L2 Pseudo Length of 22. + +Message type: SYSTEM INFORMATION TYPE 2 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.32.1: SYSTEM INFORMATION TYPE 2 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|-----------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 2 Message Type | Message Type
10.4 | M | V | 1 | +| | BCCH Frequency List | Neighbour Cell Description
10.5.2.22 | M | V | 16 | +| | NCC Permitted | NCC permitted
10.5.2.27 | M | V | 1 | +| | RACH Control Parameter | RACH Control Parameters
10.5.2.29 | M | V | 3 | + +### 9.1.33 System information type 2bis + +This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving information on control of the RACH and of the extension of the BCCH allocation in the neighbour cells. See table 9.1.33.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may ignore this message, see sub-clause 3.2.2.1. + +This message has a L2 pseudo length of 21. + +Message type: SYSTEM INFORMATION TYPE 2bis + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.33.1: SYSTEM INFORMATION TYPE 2bis message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------------------|-----------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 2bis Message Type | Message Type
10.4 | M | V | 1 | +| | Extended BCCH Frequency List | Neighbour Cell Description
10.5.2.22 | M | V | 16 | +| | RACH Control Parameters | RACH Control Parameters
10.5.2.29 | M | V | 3 | +| | SI 2bis Rest Octets | SI 2bis Rest Octets
10.5.2.33 | M | V | 1 | + +### 9.1.34 System information type 2ter + +This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving information on the extension of the BCCH allocation in the neighbour cells. See table 9.1.34.1. Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +A mobile station that supports either: + +- only the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005); or +- only the DCS 1800 band (cf. 3GPP TS 45.005); + +may ignore this message, see sub-clause 3.2.2.1. + +This message has a L2 pseudo length of 18. This message may be sent by the network with either a L2 pseudo length of 18 or some other value. A mobile station that does not ignore this message shall not discard the message due to a received L2 pseudo length different from 18. + +Message type: SYSTEM INFORMATION TYPE 2ter + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.34.1: SYSTEM INFORMATION TYPE 2ter message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------------------|--------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 2ter Message Type | Message Type
10.4 | M | V | 1 | +| | Extended BCCH Frequency List | Neighbour Cell Description 2
10.5.2.22a | M | V | 16 | +| | SI 2ter Rest Octets | SI 2ter Rest Octets
10.5.2.33a | M | V | 4 | + +#### 9.1.34a System information type 2quater + +This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving information on additional measurement and reporting parameters and/or UTRAN neighbour cells and/or E-UTRAN neighbour frequencies and/or CSG neighbour cells. A mobile station with no UTRAN capability should ignore the 3G Neighbour Cell, 3G MEASUREMENT parameter, GPRS\_3G MEASUREMENT parameter and 3G Priority parameters + +descriptions in this message. A mobile station with no E-UTRAN capability should ignore the E-UTRAN parameters description and GPRS E-UTRAN measurement parameters description in this message. Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply on BCCH, see 3GPP TS 45.002. + +This message has a L2 pseudo length of 1. + +Message type: SYSTEM INFORMATION TYPE 2quater + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.34a.1: SYSTEM INFORMATION TYPE 2 quater message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------------|--------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 2quater Message Type | Message Type
10.4 | M | V | 1 | +| | SI 2 quater Rest Octets | SI 2quater Rest Octets
10.5.2.33b | M | V | 20 | + +#### 9.1.34b System information type 2n + +This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving the parameters affecting cell reselection for the neighbouring cells. Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply on BCCH, see 3GPP TS 45.002. + +This message has a L2 pseudo length of 1. + +Message type: SYSTEM INFORMATION TYPE 2n + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.34b.1: SYSTEM INFORMATION TYPE 2n message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 2n Message Type | Message Type
10.4 | M | V | 1 | +| | SI 2n Rest Octets | SI 2n Rest Octets
10.5.2.33c | M | V | 20 | + +### 9.1.35 System information type 3 + +This message is sent on the BCCH by the network giving information of control on the RACH, the location area identification, the cell identity and various other information about the cell. See table 9.1.35.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. This message has a L2 Pseudo Length of 18. + +Message type: SYSTEM INFORMATION TYPE 3 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.35.1: SYSTEM INFORMATION TYPE 3 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 3 Message Type | Message Type
10.4 | M | V | 1 | +| | Cell Identity | Cell Identity
10.5.1.1 | M | V | 2 | +| | Location Area Identification | Location Area Identification
10.5.1.3 | M | V | 5 | +| | Control Channel Description | Control Channel description
10.5.2.11 | M | V | 3 | +| | Cell Options | Cell Options (BCCH)
10.5.2.3 | M | V | 1 | +| | Cell Selection Parameters | Cell Selection Parameters
10.5.2.4 | M | V | 2 | +| | RACH Control Parameters | RACH Control Parameters
10.5.2.29 | M | V | 3 | +| | SI 3 Rest Octets | SI 3 Rest Octets
10.5.2.34 | M | V | 4 | + +### 9.1.36 System information type 4 + +This message is sent on the BCCH by the network giving information on control of the RACH, the location area identification and various other information about the cell. See table 9.1.36.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the *SI 4 Rest Octets* and *L2 Pseudo Length* information elements. + +Message type: SYSTEM INFORMATION TYPE 4 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.36.1: SYSTEM INFORMATION TYPE 4 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 4 Message Type | Message Type
10.4 | M | V | 1 | +| | Location Area Identification | Location Area Identification
10.5.1.3 | M | V | 5 | +| | Cell Selection Parameters | Cell Selection Parameters
10.5.2.4 | M | V | 2 | +| | RACH Control Parameters | RACH Control Parameters
10.5.2.29 | M | V | 3 | +| 64 | CBCH Channel Description | Channel description
10.5.2.5 | O | TV | 4 | +| 72 | CBCH Mobile Allocation | Mobile Allocation
10.5.2.21 | C | TLV | 3-6 | +| | SI 4 Rest Octets | SI 4 Rest Octets
10.5.2.35 | M | V | 0-10 | + +#### 9.1.36.1 CBCH Channel description + +This information element is present if SMSCB is active in the cell and indicates (together with the *CBCH Mobile Allocation IE*) where to find the CBCH. + +#### 9.1.36.2 CBCH Mobile Allocation + +If the *CBCH Channel Description* Information Element indicates frequency hopping, the *CBCH Mobile Allocation IE* shall be present. If the *CBCH Channel Description* does not indicate frequency hopping, the *CBCH Mobile Allocation IE* shall be considered as an unnecessary IE in the message. + +#### 9.1.36.3 SI 4 Rest Octets + +The sum of the length of this IE and the L2 pseudo length of the message equals 22. + +### 9.1.37 System information type 5 + +This message is sent on the SACCH by the network to mobile stations within the cell giving information on the BCCH allocation in the neighbour cells. See table 9.1.37.1. + +When received this information shall be used as the list of BCCH frequencies of the neighbouring cells to be reported on. Any change in the neighbour cell description must overwrite any old data held by the mobile station. The mobile station must analyse all correctly received system information type 5 messages. This message has a L2 Pseudo Length of 18. + +Message type: SYSTEM INFORMATION TYPE 5 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.37.1: SYSTEM INFORMATION TYPE 5 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|-----------------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 5 Message Type | Message Type
10.4 | M | V | 1 | +| | BCCH Frequency List | Neighbour Cell Description
10.5.2.22 | M | V | 16 | + +### 9.1.38 System information type 5bis + +This message is sent optionally on the SACCH by the network to mobile stations within the cell giving information on the extension of the BCCH allocation in the neighbour cells. See table 9.1.38.1. + +A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may ignore this message, see sub-clause 3.2.2.1. + +When received (and not ignored) this information must be used as the list of neighbouring cells to be reported on. Any change in the neighbour cell description must overwrite any old data held by the mobile station. The mobile station must, with the exception stated above, analyse all correctly received system information type 5bis messages. This message has a L2 Pseudo Length of 18. + +Message type: SYSTEM INFORMATION TYPE 5bis + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.38.1: SYSTEM INFORMATION TYPE 5bis message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------------------|-----------------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 5 bis Message Type | Message Type
10.4 | M | V | 1 | +| | Extension of the BCCH Frequency List Description | Neighbour Cell Description
10.5.2.22 | M | V | 16 | + +### 9.1.39 System information type 5ter + +This message is sent optionally on the SACCH by the network to mobile stations within the cell giving information on the extension of the BCCH allocation in the neighbour cells. See table 9.1.39.1. + +A mobile station that supports either: + +- only the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005); or +- only the DCS 1800 band (cf. 3GPP TS 45.005); +- may ignore this message, see sub-clause 3.2.2.1. + +When received (and not ignored) this information must be used as part of the list of neighbouring cells to be reported on. Any change in the neighbour cell description must overwrite this part of any old data held by the mobile station. The mobile station shall, with the exception stated above, analyse all correctly received system information type 5ter messages. This message has a L2 Pseudo Length of 18. + +Message type: SYSTEM INFORMATION TYPE 5ter + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.39.1: SYSTEM INFORMATION TYPE 5ter message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------------------|--------------------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 5ter Message Type | Message Type
10.4 | M | V | 1 | +| | Extended BCCH Frequency List | Neighbour Cell Description 2
10.5.2.22a | M | V | 16 | + +### 9.1.40 System information type 6 + +This message is sent on the SACCH by the network to mobile stations within the cell giving information of location area identification, of cell identity and various other information. See table 9.1.40.1. If received correctly by the mobile station this message is treated as in sub-clauses 9.1.40.1 to 9.1.40.4. + +This message has a L2 Pseudo Length of 11. + +Message type: SYSTEM INFORMATION TYPE 6 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.40.1: SYSTEM INFORMATION TYPE 6 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|------------------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 6 Message Type | Message Type
10.4 | M | V | 1 | +| | Cell Identity | Cell Identity
10.5.1.1 | M | V | 2 | +| | Location Area Identification | Location Area Identification
10.5.1.3 | M | V | 5 | +| | Cell Options | Cell Options (SACCH)
10.5.2.3 | M | V | 1 | +| | NCC Permitted | NCC Permitted
10.5.2.27 | M | V | 1 | +| | SI 6 Rest Octets | SI6 Rest Octets
10.5.2.35a | M | V | 7 | + +#### 9.1.40.1 Cell Identity + +Only applicable for mobile stations supporting SIM Application Toolkit class 2 or higher: + +- if a new Cell Identity is identified, an indication shall be given to the upper layer together with the new identity. + +Other mobile stations may ignore this IE. + +#### 9.1.40.2 Location Area Identification + +Only applicable for mobile stations supporting VGCS listening and VBS listening or SIM Application Toolkit class 2 or higher or for mobile stations supporting CSG Cells Reporting. + +For mobile stations supporting VGCS listening and VBS listening or SIM Application Toolkit class 2 or higher if a new Location Area Identification is identified, an indication shall be given to the upper layer together with the new identification. + +Other mobile stations may ignore this IE. + +#### 9.1.40.3 Cell Options + +When correctly received, this information shall be used as the current Cell Options information. Any change in the Cell Options shall overwrite any old Cell Options data held by the mobile station. + +#### 9.1.40.4 NCC permitted + +As for BCCH Frequency List in SYSTEM INFORMATION TYPE 5. + +### 9.1.41 System information type 7 + +This message is sent on the BCCH by the network giving information about cell reselection parameters to be used in that cell. See table 9.1.41.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. The L2 pseudo length of this message has the value 1. + +Message type: SYSTEM INFORMATION TYPE 7 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.41.1: SYSTEM INFORMATION TYPE 7 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|--------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 7 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 7 Rest Octets | SI 7 Rest Octets
10.5.2.36 | M | V | 20 | + +### 9.1.42 System information type 8 + +This message is sent on the BCCH by the network giving information about cell reselection parameters to be used in that cell. See table 9.1.42.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. The L2 Pseudo Length of this message has the value 1. + +Message type: SYSTEM INFORMATION TYPE 8 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.42.1: SYSTEM INFORMATION TYPE 8 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|--------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 8 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 8 Rest Octets | SI 8 Rest Octets
10.5.2.37 | M | V | 20 | + +### 9.1.43 System information Type 9 + +This message is sent on the BCCH by the network to all mobile stations within the cell giving some, but not necessarily all information on the scheduling of information on the BCCH. See table 9.1.43.1. Special requirements for the transmission of this message apply, see sub-clause 3.2.2.1 and 3GPP TS 45.002. This message has a L2 Pseudo Length of 1. + +Message type: SYSTEM INFORMATION TYPE 9 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43.1: SYSTEM INFORMATION TYPE 9 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|----------------------------------------|--------------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 9 Message Type | Message Type
10.4 | M | V | 1 | +| | RACH Control Parameter | RACH Control Parameters
10.5.2.29 | M | V | 3 | +| | SI 9 Rest Octets | SI 9 Rest Octets
10.5.2.37a | M | V | 17 | + +#### 9.1.43a System information Type 13 + +This message is sent on the BCCH if indicated in at least one of the SYSTEM INFORMATION TYPE 3, 4, 7 or 8 messages. The message is sent by the network to provide information related to GPRS in the cell. See table 9.1.43a.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +A mobile station not supporting GPRS shall treat this message as an unknown message type. + +The L2 Pseudo Length of this message has the value 0. + +Message type: SYSTEM INFORMATION TYPE 13 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43a.1: SYSTEM INFORMATION TYPE 13 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 13 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 13 Rest Octets | SI 13 Rest Octets
10.5.2.37b | M | V | 20 | + +#### 9.1.43b (void) + +#### 9.1.43c (void) + +#### 9.1.43d System information type 16 + +This message is sent on the BCCH if indicated in the SYSTEM INFORMATION TYPE 3 message. The message is sent by the network giving information about cell selection and reselection parameters to be used in that cell. See table 9.1.43d.1. Special requirements for the transmission of this message applies, see 3GPP TS 45.002. + +The L2 pseudo length of this message has the value 1. + +Message type: SYSTEM INFORMATION TYPE 16 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43d.1: SYSTEM INFORMATION TYPE 16 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 16 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 16 Rest Octets | SI 16 Rest Octets
10.5.2.37e | M | V | 20 | + +#### 9.1.43e System information type 17 + +This message is sent on the BCCH if indicated in the SYSTEM INFORMATION TYPE 3 message. The message is sent by the network giving information about cell selection and reselection parameters to be used in that cell. See table 9.1.43e.1. Special requirements for the transmission of this message applies, see 3GPP TS 45.002. + +The L2 pseudo length of this message has the value 1. + +Message type: SYSTEM INFORMATION TYPE 17 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43e.1: SYSTEM INFORMATION TYPE 17 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 17 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 17 Rest Octets | SI 17 Rest Octets
10.5.2.37f | M | V | 20 | + +#### 9.1.43f System information type 19 + +This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving information on COMPACT neighbour cells. See table 9.1.43f.1. Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +A mobile station that does not support COMPACT should ignore this message. + +This message has a L2 pseudo length of 1. + +Message type: SYSTEM INFORMATION TYPE 19 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43f.1: SYSTEM INFORMATION TYPE 19 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information
Type 19 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 19 Rest Octets | SI 19 Rest Octets
10.5.2.37g | M | V | 20 | + +#### 9.1.43g System information type 18 + +This message is sent in one or more instances on the BCCH when the operator decides to transmit non-GSM broadcast information. + +A mobile station with non-GSM capabilities shall read all instances of this message (by using parameters in the SI 18 Rest Octets). The mobile station needs only decode the Non-GSM information according to the Non-GSM protocols it supports, indicated by the Non-GSM protocol discriminator. + +The L2 pseudo length of this message has the value 1. + +Message type: SYSTEM INFORMATION TYPE 18 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43g.1: SYSTEM INFORMATION TYPE 18 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information
Type 18 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 18 Rest Octets | SI 18 Rest Octets
10.5.2.37h | M | V | 20 | + +#### 9.1.43h System information type 20 + +This message is sent in one or more instances on the BCCH when the operator decides to transmit non-GSM broadcast information. + +A mobile station with non-GSM capabilities shall read all instances of this message (by using parameters in the SI 20 Rest Octets). The mobile station needs only decode the Non-GSM information according to the Non-GSM protocols it supports, indicated by the Non-GSM protocol discriminator. + +The L2 pseudo length of this message has the value 1. + +Message type: SYSTEM INFORMATION TYPE 20 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43h.1: SYSTEM INFORMATION TYPE 20 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information
Type 20 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 20 Rest Octets | SI 18 Rest Octets
10.5.2.37i | M | V | 20 | + +#### 9.1.43i System information type 14 + +This message is sent optionally on the SACCH by the network to mobile stations within the cell giving information on dynamic ARFCN mapping. It allows to allocate ARFCN values and dynamically map them to physical frequencies, see 3GPP TS 45.005. See table 9.1.43i.1. Multiple instances of this message may be sent by the network + +When received, this information replaces any previously received information about dynamic ARFCN mapping. This message has a L2 Pseudo Length of 18. + +Message type: SYSTEM INFORMATION TYPE 14 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43i.1: SYSTEM INFORMATION TYPE 14 message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|---------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management Protocol
Discriminator | Protocol Discriminator
10.2 | M | V | ½ | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | ½ | +| | System Information Type 14
Message Type | Message Type
10.4 | M | V | 1 | +| | SI 14 Rest Octets | SI 14 Rest Octets
10.5.2.37j | M | V | 16 | + +### 9.1.43j System information type 15 + +This message is sent optionally on the BCCH by the network to all mobile stations within the cell giving information about dynamic ARFCN mapping. It allows to allocate ARFCN values and dynamically map them to physical frequencies, see 3GPP TS 45.005. Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply on BCCH, see 3GPP TS 45.002. + +This message has a L2 pseudo length of 1 + +Message type: SYSTEM INFORMATION TYPE 15 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43j.1: SYSTEM INFORMATION 15 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 15
Message Type | Message Type
10.4 | M | V | 1 | +| | SI 15 Rest Octets | SI 15 Rest Octets
10.5.2.37k | M | V | 20 | + +### 9.1.43k System information Type 13alt + +This message is sent on the BCCH if indicated in the SYSTEM INFORMATION TYPE 3 message. The message is sent by the network to provide information related to *Iu mode* in the cell. See table 9.1.43k.1. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +A mobile station not supporting GERAN *Iu mode* shall treat this message as an unknown message type. + +The L2 Pseudo Length of this message has the value 0. + +Message type: SYSTEM INFORMATION TYPE 13alt + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43k.1: SYSTEM INFORMATION TYPE 13alt message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 13alt
Message Type | Message Type
10.4 | M | V | 1 | +| | SI 13alt Rest Octets | SI 13 Rest Octets
10.5.2.37l | M | V | 20 | + +### 9.1.43m System information type 21 + +This message is sent optionally on the BCCH by the network to provide the list of EAB specific authorized access classes and an indication of the subcategory of mobile stations targeted by EAB (see also 3GPP TS 22.011). Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +This message has a L2 pseudo length of 2. + +Message type: SYSTEM INFORMATION TYPE 21 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43m.1: SYSTEM INFORMATION TYPE 21 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 21 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 21 Rest Octets | SI 21 Rest Octets
10.5.2.37m | M | V | 20 | + +### 9.1.43n System information type 22 + +This message is sent on the BCCH if indicated in the SYSTEM INFORMATION TYPE 3 message. It is sent by the network, giving information about network sharing and domain-specific access control. Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +This message has a L2 pseudo length of 2. + +Message type: SYSTEM INFORMATION TYPE 22 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43m.1: SYSTEM INFORMATION TYPE 22 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 22 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 22 Rest Octets | SI 22 Rest Octets
10.5.2.37n | M | V | 20 | + +### 9.1.43o System information type 23 + +This message is sent on the BCCH if indicated in the SYSTEM INFORMATION TYPE 22 message. It is sent by the network when network sharing is in use in a cell, providing PLMN-specific information about UTRAN/E-UTRAN frequencies related to inter RAT cell reselection. Multiple instances of this message may be sent by the network. Special requirements for the transmission of this message apply, see 3GPP TS 45.002. + +This message has a L2 pseudo length of 2. + +Message type: SYSTEM INFORMATION TYPE 23 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.43o.1: SYSTEM INFORMATION TYPE 23 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|---------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | System Information Type 23 Message Type | Message Type
10.4 | M | V | 1 | +| | SI 23 Rest Octets | SI 23 Rest Octets
10.5.2.37o | M | V | 20 | + +### 9.1.43p EC System information type 1 + +This message is sent on the EC-BCCH if EC-GSM-IoT is supported in the cell. It is sent by the network providing cell allocation information to mobile stations that have enabled EC operation. Multiple instances of this message may be sent by the network. The requirements for transmission of this message are defined in 3GPP TS 45.002. + +Message type: EC SYSTEM INFORMATION TYPE 1 + +Significance: dual + +Direction: network to mobile station + +``` + +< EC System Information Type 1 > ::= + < Message Type : bit (3) > + < EC SI 1_INDEX : bit (2) > + < EC SI 1_COUNT : bit (2) > + < EC SI_CHANGE_MARK : bit (5) > + + { 0 | 1 < EC Cell Channel Description : < EC Cell Channel Description struct >> } + < EC Mobile Allocation List : < EC Mobile Allocation List struct > > + < Band Indicator : bit (1) > + < spare padding > ; + +< EC Cell Channel Description struct > ::= + < NumberOfOctets : bit (5) > + < Frequency List Information : bit (val(NumberOfOctets + 1)*8) > ; + +< EC Mobile Allocation List struct > ::= { 1 < EC Mobile Allocation struct > } ** 0 ; +< EC Mobile Allocation struct > ::= + < EC_MA_NUMBER : bit (5) > + { 0 | 1 < MAIO : bit (6) > } + { 0 < ARFCN : bit (10) > -- Single radio frequency channel included in the current MA set + | 1 -- Multiple radio frequency channels included in the current MA set + { 0 -- The radio frequency channels of the previous MA set apply to the current MA set + | 1 -- The indicated radio frequency channels apply for the current MA set + { 0 | 1 < HSN : bit (6) > } + < MA_LENGTH : bit (6) > + < MA_BITMAP : bit (val(MA_LENGTH) + 1) > + } +} ; + +``` + +**Figure 9.1.43p.1: EC SYSTEM INFORMATION TYPE 1 message content****Table 9.1.43p.1: EC SYSTEM INFORMATION TYPE 1 information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Type (3 bits)
The Message Type field is encoded according to Table 10.4 .4. | +| EC SI 1_INDEX (2 bits) and EC SI 1_COUNT (2 bits)
The purpose of these fields is to indicate the number of individual message instances within the sequence of EC SI 1 | + +messages and to assign an index to identify each instance. The EC SI 1\_INDEX field is binary coded, range 0 to 3, and provides an index to identify an individual EC SI 1 message instance. The EC SI 1\_COUNT field is binary coded, range 0 to 3, and provides the value of the highest indexed message instance in the sequence of EC SI 1 messages. + +#### EC SI\_CHANGE\_MARK (5 bits) + +This field contains a bitmap indicating the status of each EC SI message broadcasted in the cell. Whenever the content of a given EC SI message is modified the associated bit position within the bitmap (EC SI N) is changed to "0" or "1" depending on its previous value; N = 1, 2, 3, 4. + +An Overflow Control bit (bit 1 in the bitmap) indicates whether one or more of the EC SI messages have changed more than once during a given time period (see sub-clause 3.10.4). + +The EC SI\_CHANGE\_MARK field is encoded as follows. + +Bits + +5 4 3 2 1 + +| | | | | | | | | | | +|---|---|---|---|---|---------|---------|---------|---------|----------------------| +| x | x | x | x | x | EC SI 4 | EC SI 3 | EC SI 2 | EC SI 1 | Overflow Control bit | +|---|---|---|---|---|---------|---------|---------|---------|----------------------| + +#### EC Cell Channel Description struct + +The EC Cell Channel Description struct identifies the list of frequencies in the serving cell. + +##### NumberOfOctets (5 bits) + +This field indicates the number of octets used to provide the serving cell frequency list information. + +It is coded as follows: + +Bits + +5 4 3 2 1 + +| | | | | | | +|-----|-----|-----|-----|-----|-----------| +| 0 | 0 | 0 | 0 | 0 | 1 octet | +| 0 | 0 | 0 | 0 | 1 | 2 octets | +| ... | ... | ... | ... | ... | ... | +| 1 | 1 | 1 | 1 | 1 | 32 octets | + +##### Frequency List Information + +This field defines the radio frequency channels in the cell as a set of ARFCNs. It consists of the value part of the *Frequency List* IE defined in sub-clause 10.5.2.13. The value part starts from octet 3 and the length of the value part is determined by the NumberOfOctets field. + +The number of radio frequency channels (ARFCNs) included in the Frequency List Information field (excluding any duplication of ARFCN) is denoted NF. The radio frequency channels provided in one or more instances of this message shall be arranged by the receiver of this field in the order of ascending ARFCN, except for ARFCN = 0, if included, which shall be put last. Each radio frequency channel shall then be assigned an ARFCN\_INDEX value, ranging from zero, for the first radio frequency channel, to NF-1, for the last radio frequency channel. + +#### EC Mobile Allocation List (construction) + +This construction is the representation of the EC Mobile Allocation set(s) defined for the cell. An EC\_MA\_NUMBER field preceding the EC Mobile Allocation set identifies each individual EC Mobile Allocation set. The EC Mobile Allocation List may be provided in more than one instance of the EC SI 1 message. + +#### EC\_MA\_NUMBER (5 bits) + +This field identifies the EC Mobile Allocation set provided in the EC Mobile Allocation List struct. It is coded as follows: + +Bits + +5 4 3 2 1 + +| | | | | | | +|-----|-----|-----|-----|-----|-----------------------------| +| 0 | 0 | 0 | 0 | 0 | EC Mobile Allocation set 1 | +| 0 | 0 | 0 | 0 | 1 | EC Mobile Allocation set 2 | +| ... | ... | ... | ... | ... | ... | +| 1 | 1 | 1 | 1 | 1 | EC Mobile Allocation set 32 | + +##### MAIO (6 bits) + +This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 45.002. + +##### ARFCN (10 bits) + +This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 45.005. | +| HSN (6 bits)
The HSN field is the binary representation of the hopping sequence number, see 3GPP TS 45.002. | +| MA_LENGTH (6 bits)
This field indicates the length of the MA_BITMAP field in number of bits.
It is coded as follows:
Bits
6 5 4 3 2 1
0 0 0 0 0 0    1 bit
0 0 0 0 0 1    2 bits
...
1 1 1 1 1 1    64 bits | +| MA_BITMAP (variable length, 1 to 64 bits field)
This field is a bitmap representing the radio frequency channels belonging to a given EC Mobile Allocation set. The number of bit positions in MA_BITMAP is determined by the MA_LENGTH field and shall equal the number of radio frequency channels (NF) provided in the EC Cell Channel Description struct. The first bit position in MA_BITMAP (bit position 1) corresponds to ARFCN_INDEX = NF-1 and the last bit position (bit position NF) corresponds to ARFCN_INDEX = 0, as follows:
Bit position                    ARFCN_INDEX
NF, NF-1 ... 2, 1            0,1 ... NF-2, NF-1
In the absence of this field, the MA_BITMAP field of the previous EC Mobile Allocation set described in this message shall be used for the current EC Mobile Allocation set.
Each bit position in the MA_BITMAP field is coded:
0        the corresponding radio frequency channel does not belong to the EC Mobile Allocation set.
1        the corresponding radio frequency channel belongs to the EC Mobile Allocation set. | +| Band Indicator (1 bit)
The Band Indicator associates the ARFCN channel numbers provided in the EC Cell Channel Description struct and in the EC Mobile Allocation List struct to the DCS 1800 respectively to the PCS 1900 band, see 3GPP TS 45.005. If no ARFCN channel numbers associated to DCS 1800 or PCS 1900 are included in the EC Cell Channel Description struct or in the EC Mobile Allocation List struct, the Band Indicator shall be set to 0.
Value
0        ARFCN indicates 1800 band
1        ARFCN indicates 1900 band | + +### 9.1.43q EC System information type 2 + +This message is sent on the EC-BCCH if EC-GSM-IoT is supported in the cell. It is sent by the network providing EC-RACH/RACH control information and cell selection information to mobile stations that have enabled EC operation. Multiple instances of this message may be sent by the network. The requirements for transmission of this message are defined in 3GPP TS 45.002. + +Message type: EC SYSTEM INFORMATION TYPE 2 + +Significance: dual + +``` + +Direction: network to mobile station< EC System Information Type 2 > ::= + < Message Type : bit (3) > + < EC SI 2_INDEX : bit (2) > + < EC SI 2_COUNT : bit (2) > + < EC SI_CHANGE_MARK : bit (5) > + + { 0 | 1 < EC Cell Selection Parameters : < EC Cell Selection Parameters struct >> } + { 0 | 1 < Coverage Class Selection Parameters : < Coverage Class Selection Parameters struct >> } + { 0 | 1 < EC-RACH Control Parameters : < EC-RACH Control Parameters struct >> } + { 0 | 1 < Short RACH Control Parameters : < Short RACH Control Parameters struct >> } + { 0 | 1 < EC Cell Options : < EC Cell Options struct >> } + -- Additions in Rel-14: + { 0 | 1 < MTA_BITMAP : bit (4) > } + { 0 | 1 < Coverage Class Selection Parameters Ext : < Coverage Class Selection Parameters Ext struct >> } + < MS_ASSISTED_DCN : bit (1) > + { 0 | 1 < CE_AUTH_OFFSET : bit (2) > } + + -- Additions in Rel-15: + < EC paging indication channel support : bit(1)> + { 0 | 1 < IMM Cell Group Definition : < IMM Cell Group Definition struct >> } + < spare padding > ; + +< EC Cell Selection Parameters struct > ::= + < Location Area Identification : bit (40) > + < Routing Area Code : bit (8) > + < Cell Identity : bit (16) > + < EC_BS_CC_CHANS : bit (2) > + < EC_RXLEV_ACCESS_MIN : bit (6) > -- used in the path loss criterion C1 + < MS_TXPWR_MAX_CCH : bit (5) > -- used in the path loss criterion C1 + { 0 | 1 < LB_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < CELL_SELECTION_RLA_MARGIN : bit (3) > }; + +< Coverage Class Selection Parameters struct > ::= + < DL_CC_Selection : bit (1) > + < BT_Threshold_DL : bit (5) > + { 0 | 1 < CC2_Range_DL : bit (5) > } + { 0 | 1 < CC3_Range_DL : bit (5) > } + < BT_Threshold_UL : bit (5) > + { 0 | 1 < CC2_Range_UL : bit (5) > } + { 0 | 1 < CC3_Range_UL : bit (5) > } + < BSPWR : bit (6) > + { 0 | 1 < DL_Signal_Strength_Step_Size : bit (2) > } + < EC_Reduced_PDCH_Allocation : bit(1) > ; + +< EC-RACH Control Parameters struct > ::= + < EC_Max_Retrans : bit (2) > + < Sm : bit (2) > + < Tm : bit (2) > + < Access_Timeslots : bit (1) > + < CC_Access_Adaptation : bit (2) > + < Cell_Bar_Access : bit (1) > + { 0 | 1 < EC_Access_Control_Class : bit (7) > + < Exception_Report_Status : bit (1) > } + { 0 | 1 < BT_Threshold_UL_Margin : bit (3) > } ; + +< Short RACH Control Parameters struct > ::= + < Max_Retrans : bit (2) > + < Tx-integer : bit (4) > + < Cell_Bar_Access : bit (1) > + { 0 -- Access Control Class information and Exception Report Status in EC-RACH Control Parameters applies + | 1 -- The indicated Access Control Class bitmap and Exception Report Status field applies + < Access_Control_Class : bit (16) > + < Exception_Report_Status : bit (1) > + } ; + +< EC Cell Options struct > ::= + { 0 | 1 < ALPHA : bit (4) > } + { 0 | 1 < T3168 : bit (3) > } + +``` + +``` + +{ 0 | 1 < T3192 : bit (3) > } +{ 0 | 1 < T3226 : bit (3) > } +< T3248 : bit (2) > ; + +< Coverage Class Selection Parameters Ext struct > ::= -- Addition in Rel-14 + < CC4_Range_UL : bit (5) > + < CC5_EC-RACH_FORMAT_IND : bit(1) > ; + +< IMM Cell Group Definition struct > ::= -- Addition in Rel-15 + < IMM Cell Group Identifier : bit (3) > + < IMM Change Mark : bit (2) > + < Timeout Read Complete SI : bit (2) > + < NumberOfOctets : bit (5) > + < Broadcast Frequency List Information : bit (val(NumberOfOctets + 1)*8) > + { 0 | 1 < IMM Cell Group Specific Parameters : < IMM Cell Group Specific Parameters struct >> } + +< IMM Cell Group Specific Parameters struct > ::= + < Nb_NCELL : bit (5) > + { + { 0 < BSIC : bit (6) > + | 1 < BSIC : bit (9) > } + { 0 | 1 < EC_BS_CC_CHANS_SPECIFIC : bit (2) > } + { 0 | 1 < CELL_BAR_ACCESS_SPECIFIC : bit (1) > } + } * (val(Nb_NCELL)+1) ; + { 0 | 1 < EC_BS_CC_CHANS_DEFAULT : bit (2) > } + { 0 | 1 < CELL_BAR_ACCESS_DEFAULT : bit (1) > } ; + +``` + +Figure 9.1.43q.1: EC SYSTEM INFORMATION TYPE 2 message content + +Table 9.1.43q.1: EC SYSTEM INFORMATION TYPE 2 information element details + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Message Type (3 bits)
The Message Type field is encoded according to Table 10.4.4.

| +|

EC SI 2_INDEX (2 bits) and EC SI 2_COUNT (2 bits)
The purpose of these fields is to indicate the number of individual message instances within the sequence of EC SI 2 messages and to assign an index to identify each instance. The EC SI 2_INDEX field is binary coded, range 0 to 3, and provides an index to identify an individual EC SI 2 message instance. The EC SI 2_COUNT field is binary coded, range 0 to 3, and provides the value of the highest indexed message instance in the sequence of EC SI 2 messages.

| +|

EC SI_CHANGE_MARK (5 bits)
This field is defined in Table 9.1.43p.1.

| +|

EC Cell Selection Parameters struct
This structure provides the cell selection parameters for the serving cell.

| +|

Location Area Identification (40 bits)
The Location Area Identification field is coded as the value part of the Location Area Identification IE specified in sub-clause 10.5.1.3.

| +|

Routing Area Code (8 bits)
This field is the binary representation of the Routing Area Code, see 3GPP TS 23.003.

| +|

Cell Identity (16 bits)
The Cell Identity field is coded as the value part of the Cell Identity IE specified in sub-clause 10.5.1.1.

| + +#### **EC\_BS\_CC\_CHANS (2 bits)** + +This field indicates the number of extended coverage common control channels (EC-CCCHs) supported in the cell. + +##### Value + +- | | | +|----|----------------------| +| 00 | 1 EC-CCCH supported | +| 01 | 2 EC-CCCHs supported | +| 10 | 3 EC-CCCHs supported | +| 11 | 4 EC-CCCHs supported | + +If the Access\_Timeslots field provided in this message indicates that 2 TS EC-RACH mapping shall be applied in the cell, then the number of EC-CCCHs supported in the cell shall be equal to or lower than the number of common control channels (CCCHs) configured in the same cell. + +#### **EC\_RXLEV\_ACCESS\_MIN (6 bits)** + +The EC\_RXLEV\_ACCESS\_MIN field is coded as the binary representation of the minimum received signal level at the MS for which it is permitted to access the system, see 3GPP TS 45.008. + +#### **MS\_TXPWR\_MAX\_CCH (5 bits)** + +The MS\_TXPWR\_MAX\_CCH field is coded as the binary representation of the "power control level" in 3GPP TS 45.005 corresponding to the maximum TX power level an MS may use when accessing the system on the (EC-)CCCH. This value shall be used by the Mobile Station according to 3GPP TS 45.008. + +##### **LB\_MS\_TXPWR\_MAX\_CCH (5 bits)** + +The LB\_MS\_TXPWR\_MAX\_CCH field is coded as the binary representation of the "power control level" in 3GPP TS 45.005 corresponding to the maximum TX power level an MS may use on all other than DCS 1800 and PCS 1900 frequency bands when accessing the system on the (EC-)CCCH. This value shall be used by the Mobile Station according to 3GPP TS 45.008. + +##### **CELL\_SELECTION\_RLA\_MARGIN (3 bits)** + +The CELL\_SELECTION\_RLA\_MARGIN field provides the MS with information whether RLA\_EC and RLA\_GC based measurements may be omitted or not. The use of this field is defined in 3GPP TS 45.008. + +#### **CE\_AUTH\_OFFSET (2 bits)** + +The CE\_AUTH\_OFFSET field is the coverage enhancement authorization offset corresponding to the level of desensitization of a MS in restricted use of enhanced coverage compared to the non-restricted use of enhanced coverage. + +##### Bits + +- | | | +|----|-------| +| 00 | 5 dB | +| 01 | 10 dB | +| 10 | 15 dB | +| 11 | 20 dB | + +##### **Coverage Class Selection Parameters struct** + +This structure provides information for the MS to estimate its uplink and downlink coverage class. + +##### **DL\_CC\_Selection (1 bit)** + +This field indicates the method for selecting the downlink coverage class to be used by the MS. + +##### Bit + +- | | | +|---|---------------------------------------| +| 0 | RLA_EC based coverage class selection | +| 1 | SLA based coverage class selection | + +The use of this field is defined in 3GPP TS 45.008. + +##### **BT\_Threshold\_DL (5 bits)** + +This field indicates the threshold below which blind physical layer transmissions are used on EC-CCCH. The use of this field is defined in 3GPP TS 45.008. + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

CC2_Range_DL (5 bits)
CC3_Range_DL (5 bits)

These fields are optionally sent by the network to indicate the signal level range of the indicated downlink coverage classes. The presence of one or both of the above fields indicates network support of the associated downlink coverage class.
The use of these fields is defined in 3GPP TS 45.008.

| +|

BT_Threshold_UL (5 bits)

This field indicates the signal level threshold below which blind physical layer transmissions are used on EC-RACH.
The use of this field is defined in 3GPP TS 45.008.

| +|

CC2_Range_UL (5 bits)
CC3_Range_UL (5 bits)

These fields are optionally sent by the network to indicate the signal level range of the indicated uplink coverage classes. The presence of one or both of the above fields indicates network support of the associated uplink coverage class.
The use of these fields is defined in 3GPP TS 45.008.

| +|

CC4_Range_UL (5 bits)

This field is optionally sent by the network to indicate the signal level range of coverage class CC4. Presence of this field indicates that network support uplink coverage class CC5. The use of this field is defined in 3GPP TS 45.008.

| +|

CC5_EC-RACH_FORMAT_IND (1 bit)

This field indicates the EC-RACH format that has to be used by EC-GSM-IoT device that uses CC5 as its Uplink coverage class.

Bit
0 EDAB method supported for EC-RACH CC5
1 ESAB method supported for EC-RACH CC5

If the parameter CC5_EC-RACH_FORMAT_IND is set to 0 and Access_Timeslot is set to 0, then CC4 EC-RACH transmissions on TN1 and the second access burst transmission (see 3GPP TS 45.002 [32]) of EDAB use TS7.

| +|

BSPWR (6 bits)

This field indicates the BTS output power transmitted on FCCH and EC-SCH.
The use of this field is defined in 3GPP TS 45.008.

| +|

DL_Signal_Strength_Step_Size (2 bits)

This field indicates the step-size in signal level above BT_Threshold_DL possible to report by the MS in the EC Packet Channel Request message (see sub-clause 9.1.65). It is encoded as follows:

Bits
2 1
0 0 X = 2
0 1 X = 4
1 0 X = 6
1 1 X = 8

| +|

EC_Reduced_PDCH_Allocation (1 bit)

This field indicates that the number of consecutive PDCHs the network allocates when assigning an EC TBF to a MS indicating Coverage Class CC2, CC3 or CC4 on the uplink or downlink during packet access.

Bit
0 Four consecutive PDCHs are always allocated to MS for an EC TBF.
1 Two consecutive PDCHs are always allocated to MS for an EC TBF.

| + +#### **EC-RACH Control Parameters struct** + +The EC-RACH Control Parameters contains the access control parameters needed when accessing the network on the EC-RACH. + +##### **EC\_Max\_Retrans (2 bits)** + +This field indicates the maximum number of retransmissions on EC-RACH (see sub-clause 3.5.2.1.2a). It is encoded as the Max retrans field in the *RACH Control Parameters* IE defined in sub-clause 10.5.2.29. + +##### **Sm (2 bits)** + +This field is used by a MS to determine the number of multiframes it needs to read on the EC-AGCH in an attempt to find a response matching its last EC-RACH transmission (see sub-clause 3.5.2.1.2a). + +##### Bits + +2 1 + +0 0 1 or more multiframes + +0 1 2 or more multiframes + +1 0 3 or more multiframes + +1 1 4 or more multiframes + +##### **Tm (2 bits)** + +This field is used by a MS to determine the number of multiframes on the EC-RACH from which it randomly selects a transmission/retransmission opportunity (see sub-clause 3.5.2.1.2a). + +##### Bits + +2 1 + +0 0 1 or more multiframes + +0 1 2 or more multiframes + +1 0 3 or more multiframes + +1 1 4 or more multiframes + +##### **Access\_Timeslots (1 bit)** + +This field indicates whether random access mapped over two timeslots (e.g. TS 0 and TS 1, or, TS 2 and TS 3) shall be applied or not (see sub-clause 3.5.2.1.2a). + +##### Bit + +0 1 TS EC-RACH mapping shall be applied. + +1 2 TS EC-RACH mapping shall be applied if uplink Coverage Class 2, Coverage Class 3 or Coverage Class 4 has been selected. + +The number of EC-RACH supported in the cell is indicated by the EC\_BS\_CC\_CHANS field provided in this message. + +#### **CC\_Access\_Adaptation (2 bits)** + +This field indicates whether the mobile station is allowed to increment its Coverage Class after one or more failed access attempts on the EC-RACH (see sub-clause 3.5.2.1.2a). + +##### Bits + +2 1 + +0 0 Coverage Class adaptation not allowed + +0 1 Coverage Class adaptation after 1 failed EC-RACH transmission attempt + +1 0 Coverage Class adaptation after 2 failed EC-RACH transmission attempts + +1 1 Coverage Class adaptation after 3 failed EC-RACH transmission attempts + +##### **Cell\_Bar\_Access (1 bit)** + +This field indicates whether the cell is barred for access. It is encoded as the CELL\_BAR\_ACCESS field in the *RACH Control Parameters* IE defined in sub-clause 10.5.2.29. + +#### **EC\_Access\_Control\_Class (7 bits)** + +This field contains a bitmap indicating the barring status for Access Control Classes 0 to 15 (AC C0 to AC C15) applicable for the Common PLMN provided in this message. + +The EC\_Access\_Control\_Class field is encoded as follows. + +Bits + +7 6 5 4 3 2 1 + +x x x x x x x AC C15 AC C14 AC C13 AC C12 AC C11 AC C10 AC C0 to AC C9 + +For a mobile station with AC C = N access is not barred if the AC CN bit is coded with a "0"; N = 0, 1, .. 9, 11, .., 15. + +Access control for mobile stations belonging to one of the access control classes 0 to 9 (AC C0 to AC C9) is indicated by the first bit in the bitmap (bit 1). If this field is not present and the MS has selected the common PLMN it shall assume its access class is not barred. + +For an MS in EC operation the AC C10 field is not used in this version of the specification. + +##### **Exception\_Report\_Status (1 bit)** + +This field indicates whether sending of exception reports are allowed or not. It is encoded as follows: + +Bit + +0 Sending of exception reports allowed in the cell for all MSs + +1 Sending of exception reports not allowed in the cell except for the MSs that belong to one of the authorized Access Control Classes 11 to 15. + +If this field is not present and the MS has selected the common PLMN it shall assume exception reports are not barred. + +##### **BT\_Threshold\_UL\_Margin (3 bits)** + +This optional field indicates the power margin above BT\_Threshold\_UL used for (EC-)RACH open-loop power control. The use of this field is defined in 3GPP TS 45.008. + +##### **Short RACH Control Parameters struct** + +The Short RACH Control Parameters contains the access control parameters needed when accessing the network on the RACH on the common control channel (CCCH) on TS 0. + +##### **Max\_Retrans (2 bits)** + +This field indicates the maximum number of retransmissions on RACH. It is encoded as the Max retrans field in the *RACH Control Parameters* IE defined in sub-clause 10.5.2.29. + +##### **Tx-integer (4 bits)** + +This field indicates the number of slots to spread the transmission on RACH. It is encoded as the Tx-integer field in the *RACH Control Parameters* IE defined in sub-clause 10.5.2.29. + +##### **Access\_Control\_Class (16 bits)** + +This field contains a bitmap indicating the barring status for Access Control Classes 0 to 15 (AC C0 to AC C15) applicable for the Common PLMN provided in this message. In the absence of this field, the Access Control Class information provided in the *EC-RACH Control Parameters* struct shall be used instead. + +The Access\_Control\_Class field is encoded as follows. + +Bits + +16 15 ... 1 + +x x ... x AC C15 AC C14 ... AC C0 + +For an MS in EC operation the AC C10 field is not used in this version of the specification. + +**EC Cell Options struct** + + + +**ALPHA (4 bits)** + +This field is the binary representation of the parameter $\alpha$ for MS output power control in units of 0.1, see 3GPP TS 45.008. For encoding and description of the ALPHA field see the *Global Power Control Parameters* IE in 3GPP TS 44.060. + +**T3168 (3 bits)** + +**T3192 (3 bits)** + +These fields are defined in 3GPP TS 44.060. + +**T3226 (3 bits)** + +This field is the binary representation of the timeout value of timer T3226. Range: 0 to 7. +The timeout values are given in the following table. + +Bits + +| | | | | +|---|---|---|---------| +| 3 | 2 | 1 | | +| 0 | 0 | 0 | 20 ms | +| 0 | 0 | 1 | 60 ms | +| 0 | 1 | 0 | 100 ms | +| 0 | 1 | 1 | 200 ms | +| 1 | 0 | 0 | 500 ms | +| 1 | 0 | 1 | 700 ms | +| 1 | 1 | 0 | 1000 ms | +| 1 | 1 | 1 | 1200 ms | + +**T3248 (2 bits)** + +This field is the binary representation of the timeout value of timer T3248. Range: 0 to 3. +The timeout values are given in the following table. + +Bits + +| | | | +|---|---|-----------| +| 2 | 1 | | +| 0 | 0 | not used | +| 0 | 1 | 1 second | +| 1 | 0 | 2 seconds | +| 1 | 1 | 3 seconds | + +**MTA\_BITMAP (4 bits)** + +See sub-clause 10.5.2.37b. + +**MS\_ASSISTED\_DCN** + +See sub-clause 10.5.2.37b. + +--- + +**EC paging indication channel support (1 bit)** + +This field indicates if paging indication on EC-PICH is supported in the cell. + +| | | +|-----|-----------------------------------------------| +| Bit | | +| 0 | EC paging indication channel is not supported | +| 1 | EC paging indication channel is supported | + +#### **IMM Cell Group Definition struct** + +This structure provides identifier, change mark indication as well as common and specific cell parameters of the IMM Cell Group which the serving cell belongs to. Common cell parameters across cells in the same IMM Cell Group are contained in the IMM Cell Group Definition structure (see below) and further refer to following cell parameters outside the IMM Cell Group Definition structure, if sent for the serving cell in EC SI type 2 and EC SI type 3 (i.e. these parameters broadcasted by the serving cell are interpreted as common parameters of the IMM Cell Group): + +Common cell parameters outside the IMM Cell Group Definition structure in EC SI type 2: + +Parameters in EC Cell Selection Parameters structure: + +Routing Area Code : bit (8) + +EC\_BS\_CC\_CHANS : bit (2) + +EC\_RXLEV\_ACCESS\_MIN : bit (6) + +MS\_TXPWR\_MAX\_CCH : bit (5) + +LB\_MS\_TXPWR\_MAX\_CCH : bit (5) + +CELL\_SELECTION\_RLA\_MARGIN : bit (3) + +Parameters in Coverage Class Selection Parameters structure: + +DL\_CC\_Selection: bit (1) + +BT\_Threshold\_DL: bit (5) + +CC2\_Range\_DL : bit (5) + +CC3\_Range\_DL : bit (5) + +Parameters in EC-RACH Control Parameters structure: + +Cell\_Bar\_Access : bit (1) + +Common cell parameters outside the IMM Cell Group Definition structure in EC SI type 3: + +Parameters in EC Cell Reselection Parameters struct: + +CELL\_RESELECT\_HYSTERESIS : bit (3) + +CELL\_RESELECT\_OFFSET : bit (6) + +C1\_DELTA\_MIN : bit (2) + +C1\_DELTA\_MAX : bit (3) + +##### **IMM Cell Group Identifier (3 bits)** + +This field is the binary representation of the identity of the IMM Cell Group. Range: 1 to 7. The code point "000" is not used, as it indicates on EC-SCH that IMM Cell Group description is not broadcasted, see subclause 9.1.30c. + +##### Bits + +3 2 1 + +| | | +|-------|-----------------------| +| 0 0 0 | not used | +| 0 0 1 | Cell Group Identity 1 | +| 0 1 0 | Cell Group Identity 2 | +| 0 1 1 | Cell Group Identity 3 | +| 1 0 0 | Cell Group Identity 4 | +| 1 0 1 | Cell Group Identity 5 | +| 1 1 0 | Cell Group Identity 6 | +| 1 1 1 | Cell Group Identity 7 | + +#### **IMM Change Mark (2 bits)** + +This field is the binary representation of the IMM Change Mark value N indicating the status of the IMM Cell Group description, referring to parameters belonging to the IMM Cell Group Definition struct and to specific parameters in EC SI type 2 and EC SI type 3. Range: 0 to 3. Whenever the value of parameters belonging to the IMM Cell Group description is modified, the IMM Change Mark value N is incremented to (N+1) modulo 4. If only parameters are modified that belong to the IMM Cell Group Definition struct, the EC SI\_CHANGE\_MARK field shall not be modified. + +##### **Timeout Read Complete SI (2 bits)** + +This field indicates the timeout for triggering the acquisition of the complete set of EC System Information messages in the serving cell, if the last acquisition of the complete set of System Information messages has been performed in a different cell. It is coded as follows. + +##### Bits + +2 1 + +| | | +|-----|--------------| +| 0 0 | [2] minutes | +| 0 1 | [5] minutes | +| 1 0 | [15] minutes | +| 1 1 | reserved | + +##### **NumberOfOctets (5 bits)** + +This field is coded in the same way as in EC SI type 3. + +##### **Broadcast Frequency List Information** + +This field defines all BCCH carriers, as a set of ARFCNs, of cells belonging to the same IMM Cell Group as the serving cell belongs to. It is coded in the same way as the field Neighbour Frequency List Information in EC SI type 3. + +#### IMM Cell Group Specific Parameters struct + +This structure provides specific cell parameters of neighbour cells belonging to the same IMM Cell Group as the serving cell. + +##### Nb\_NCELL (5 bits) + +This field indicates the number of neighbour BCCH carriers belonging to the same IMM Cell Group as the serving cell for which the number of extended coverage common control channels (EC-CCCHs) or the cell barring status deviates from the default parameter EC\_BS\_CC\_CHANS\_DEFAULT or CELL\_BAR\_ACCESS\_DEFAULT, respectively. The same coding as for Nb\_NCELL field in EC SI type 3 applies. + +##### BSIC (6 or 9 bits) + +The BSIC field identifies the neighbour base station for which the specific IMM Cell Group parameters (rather than the default values) are valid. The BSIC field is encoded either as a 6 bit field or as a 9 bit field, see 3GPP TS 45.002. The use of the BSIC field is defined in 3GPP TS 45.008. + +##### EC\_BS\_CC\_CHANS\_SPECIFIC (2 bits) + +This field indicates the number of extended coverage common control channels (EC-CCCHs) that shall be applied for a cell sharing the same IMM Cell Group as the serving cell, if the BSIC of that cell is contained in the cell description of the IMM Cell Group Definition struct. It is coded as the field EC\_BS\_CC\_CHANS (sent in EC SI type 2). It overwrites the default parameter EC\_BS\_CC\_CHANS\_DEFAULT for that cell. + +##### CELL\_BAR\_ACCESS\_SPECIFIC (1 bit) + +This field indicates the cell barring status that shall be applied for a cell sharing the same IMM Cell Group as the serving cell, if the BSIC of that cell is contained in the cell description of the IMM Cell Group Definition struct. It is coded as the field Cell\_Bar\_Access (sent in EC SI type 2). It overwrites the default parameter CELL\_BAR\_ACCESS\_DEFAULT for that cell. + +##### EC\_BS\_CC\_CHANS\_DEFAULT (2 bits) + +This field indicates the number of extended coverage common control channels (EC-CCCHs) that shall be used by default for a cell sharing the same IMM Cell Group as the serving cell, if the BSIC of that cell is not contained in the cell description of the IMM Cell Group Definition struct. It is coded as the field EC\_BS\_CC\_CHANS (sent in EC SI type 2). If this parameter is not broadcasted, the MS shall assume that all cells belonging to the same IMM Cell Group use the same value for this parameter and the value indicated in EC\_BS\_CC\_CHANS (sent in EC SI type 2) applies. + +##### CELL\_BAR\_ACCESS\_DEFAULT (1 bit) + +This field indicates the cell barring status that shall be used by default for a cell sharing the same IMM Cell Group as the serving cell, if the BSIC of that cell is not contained in the cell description of the IMM Cell Group Definition struct. It is coded as the field Cell\_Bar\_Access (sent in EC SI type 2). If this parameter is not broadcasted, the MS shall assume that all cells belonging to the same IMM Cell Group use the same value for this parameter and the value indicated in Cell\_Bar\_Access (sent in EC SI type 2) applies. + +### 9.1.43r EC System information type 3 + +This message is sent on the EC-BCCH if EC-GSM-IoT is supported in the cell. It is sent by the network providing cell reselection parameters for the serving and neighbour cells and EC-BCCH allocation information for the neighbour cells. Multiple instances of this message may be sent by the network. The requirements for transmission of this message are defined in 3GPP TS 45.002. + +Message type: EC SYSTEM INFORMATION TYPE 3 + +Significance: dual + +Direction: network to mobile station + +``` + +< EC System Information Type 3 > ::= + < Message Type : bit (3) > + < EC SI 3_INDEX : bit (2) > + < EC SI 3_COUNT : bit (2) > + < EC SI_CHANGE_MARK : bit (5) > + < EC SI 4 Indicator : bit (1) > + + { 0 | 1 < EC Cell Reselection Parameters : < EC Cell Reselection Parameters struct >> } + { 0 | 1 < EC Neighbour Cell Description : < EC Neighbour Cell Description struct >> } + { 0 | 1 < EC Neighbour Cell Reselection Parameters : < EC Neighbour Cell Reselection Parameters struct >> } + < spare padding > ; + +< EC Cell Reselection Parameters struct > ::= + < CELL_RESELECT_HYSTERESIS : bit (3) > + < CELL_RESELECT_OFFSET : bit (6) > + { 0 | 1 < C1_DELTA_MIN : bit (2) > + < C1_DELTA_MAX : bit (3) > } ; + +< EC Neighbour Cell Description struct > ::= + < NumberOfOctets : bit (5) > + < Neighbour Frequency List Information : bit (val(NumberOfOctets + 1)*8) > ; + +< EC Neighbour Cell Reselection Parameters struct > ::= +< Nb_NCELL : bit (5) > +{ + { + 0 | 1 + { 0 < BSIC : bit (6) > + | 1 < BSIC : bit (9) > } + } + < CELL_TYPE : bit (1) > + { 0 -- The previously listed EC Neighbour Cell Reselection Parameters applies + | 1 -- The indicated EC Neighbour Cell Reselection Parameters applies } + { 0 | 1 < CELL_BAR_ACCESS : bit (1) > + < SAME_RA_AS_SERVING_CELL : bit (1) > } + + { 0 | 1 < EC_RXLEV_ACCESS_MIN : bit (6) > + < MS_TXPWR_MAX_CCH : bit (5) > } + + { 0 | 1 < CELL_RESELECT_OFFSET : bit (6) > } + { 0 | 1 < CE_AUTH_OFFSET : bit (2) > } +} +* (val(Nb_NCELL)+1) ; + +``` + +Figure 9.1.43r.1: EC SYSTEM INFORMATION TYPE 3 message content + +Table 9.1.43r.1: EC SYSTEM INFORMATION TYPE 3 information element details + +| | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|--|---|------------------------------------------------------------|---|--------------------------------------------------------| +|

Message Type (3 bits)
The Message Type field is encoded according to Table 10.4.4.

| | | | | | | +|

EC SI 3_INDEX (2 bits) and EC SI 3_COUNT (2 bits)
The purpose of these fields is to indicate the number of individual message instances within the sequence of EC SI 3 messages and to assign an index to identify each instance. The EC SI 3_INDEX field is binary coded, range 0 to 3, and provides an index to identify an individual EC SI 3 message instance. The EC SI 3_COUNT field is binary coded, range 0 to 3, and provides the value of the highest indexed message instance in the sequence of EC SI 3 messages.

| | | | | | | +|

EC SI_CHANGE_MARK (5 bits)
This field is defined in Table 9.1.43p.1.

| | | | | | | +|

EC SI 4 Indicator (1 bit)
This field indicates whether or not the EC SYSTEM INFORMATION TYPE 4 message is broadcast by the network. It is coded as follows:

Bit
0 The EC SYSTEM INFORMATION TYPE 4 message is not available.
1 The EC SYSTEM INFORMATION TYPE 4 message is available.
| Bit | | 0 | The EC SYSTEM INFORMATION TYPE 4 message is not available. | 1 | The EC SYSTEM INFORMATION TYPE 4 message is available. | +| Bit | | | | | | | +| 0 | The EC SYSTEM INFORMATION TYPE 4 message is not available. | | | | | | +| 1 | The EC SYSTEM INFORMATION TYPE 4 message is available. | | | | | | + +| | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------|-----------|----------|-----|--|-----------|-----------| +|

EC Cell Reselection parameters
This structure provides the cell reselection parameters used in the reselection criteria C2 for the serving cell.

CELL_RESELECT_HYSTERESIS (3 bits)
The usage of this field is defined in 3GPP TS 45.008. It is coded as specified in sub-clause 10.5.2.4.

| | | | | | | | | +|

CELL_RESELECT_OFFSET (6 bits)
The CELL_RESELECT_OFFSET field is coded as the binary representation of the "CELL_RESELECT_OFFSET" in 3GPP TS 45.008. It is a value used by the mobile station to apply a positive or negative offset to the value of C2 as defined in 3GPP TS 23.022 and 3GPP TS 45.008.

| | | | | | | | | +|

C1_DELTA_MIN (2 bits)
The C1_DELTA_MIN field indicates the minimum value of C1_DELTA. It is used by the mobile station to compare the current C1 value with the best C1 value experienced since entering the serving cell. The C1_DELTA_MIN field is coded as defined in 3GPP TS 45.008.

| | | | | | | | | +|

C1_DELTA_MAX (3 bits)
The C1_DELTA_MAX field indicates the maximum value of C1_DELTA. It is used by the mobile station to compare the current C1 value with the best C1 value experienced since entering the serving cell. The C1_DELTA_MAX field is coded as defined in 3GPP TS 45.008.

| | | | | | | | | +|

EC Neighbour Cell Description struct
The EC Neighbour Cell Description structure determines the BA (EC-BCCH) list which identifies the BCCH carriers of the neighbour cells.

| | | | | | | | | +|

NumberOfOctets (5 bits)
This field indicates the number of octets used to provide the neighbour frequency list information.
It is coded as follows:

Bits
5 4 3 2 1

0 0 0 0 0 1 octet
0 0 0 0 1 2 octets
...
1 1 1 1 1 32 octets
| 0 0 0 0 0 | 1 octet | 0 0 0 0 1 | 2 octets | ... | | 1 1 1 1 1 | 32 octets | +| 0 0 0 0 0 | 1 octet | | | | | | | | +| 0 0 0 0 1 | 2 octets | | | | | | | | +| ... | | | | | | | | | +| 1 1 1 1 1 | 32 octets | | | | | | | | +|

Neighbour Frequency List Information
This field defines the BCCH carriers of the neighbour cells as a set of ARFCNs. It consists of the value part of the Frequency List IE defined in sub-clause 10.5.2.13. The value part starts from octet 3 and the length of the value part is determined by the NumberOfOctets field.

The number of BCCH carriers (ARFCNs) included in the Neighbour Frequency List Information field (excluding any duplication of ARFCN) is denoted NF. The BCCH carriers provided in one or more instances of this message shall be arranged by the receiver of this field in the order of ascending ARFCN, except for ARFCN = 0, if included, which shall be put last. Each BCCH carrier shall then be assigned an NCELL_LIST_INDEX value, ranging from zero, for the first BCCH carrier, to NF-1, for the last BCCH carrier.

| | | | | | | | | + +#### EC Neighbour Cell Reselection Parameters struct + +This structure provides a set of cell reselection parameters for each BCCH carrier included in the EC Neighbour Cell Description struct. The first set of cell reselection parameters in the EC Neighbour Cell Reselection Parameters struct refers to the BCCH carrier with NCELL\_LIST\_INDEX value = 0, the second set of cell reselection parameters refers to the BCCH carrier with NCELL\_LIST\_INDEX value = 1 and so on. + +General rules for handling of the neighbour cell reselection parameter default values are as follows: + +If the first set of cell reselection parameters in the EC Neighbour Cell Reselection Parameters struct does not include all the cell reselection parameters, the following default values shall be applied: + +| Field name | Default value | +|---------------------------|------------------------------------------------------------------------| +| CELL_BAR_ACCESS : | Serving cell CELL_BAR_ACCESS | +| SAME_RA_AS_SERVING_CELL : | 1 (The neighbour cell is in the same Routing Area as the serving cell) | +| EC_RXLEV_ACCESS_MIN : | Serving cell EC_RXLEV_ACCESS_MIN | +| MS_TXPWR_MAX_CCH : | Serving cell MS_TXPWR_MAX_CCH | +| CELL_RESELECT_OFFSET : | C2=C1, see 3GPP TS 45.008 | + +In the absence of any neighbour cell reselection parameter for any given BCCH carrier, the cell reselection parameter value of the previous BCCH carrier shall apply. This principle also applies when going from EC SI 3 instance i over to EC SI 3 instance i+1. + +##### Nb\_NCELL (5 bits) + +This field indicates the number of neighbour BCCH carriers for which cell reselection parameters are provided. The value of the Nb\_NCELL field shall equal the number of BCCH carriers (NF) included in the Neighbour Frequency List Information field. + +The Nb\_NCELL field is coded as follows: + +Bits + +5 4 3 2 1 + +0 0 0 0 0 1 neighbour cell + +0 0 0 0 1 2 neighbour cells + +... + +1 1 1 1 1 32 neighbour cells + +##### CE\_AUTH\_OFFSET (2 bits) + +See table 9.1.43q.1. + +##### BSIC (6 or 9 bits) + +The BSIC field identifies the neighbour base station for which the indicated cell reselection parameters are valid. The BSIC field is encoded either as a 6 bit field or as a 9 bit field, see 3GPP TS 45.002. + +The use of the BSIC field is defined in 3GPP TS 45.008. + +##### CELL\_TYPE (1 bit) + +The CELL\_TYPE field identifies whether or not the neighbour cell supports EC-GSM-IoT. + +Bit + +0 The neighbour cell supports EC-GSM-IoT + +1 The neighbour cell does not support EC-GSM-IoT + +##### CELL\_BAR\_ACCESS (1 bit) + +This field indicates whether the neighbour cell is barred for access. It is encoded as the CELL\_BAR\_ACCESS field in the *RACH Control Parameters* IE defined in sub-clause 10.5.2.29. + +##### SAME\_RA\_AS\_SERVING\_CELL (1 bit) + +This field indicates whether the neighbour cell belongs to the same Routing Area as the serving cell. + +Bit + +0 The neighbour cell is in a different Routing Area compared to the serving cell + +1 The neighbour cell is in the same Routing Area as the serving cell + +**EC\_RXLEV\_ACCESS\_MIN** (6 bits) +**MS\_TXPWR\_MAX\_CCH** (5 bits) + See table 9.1.43q.1 for the corresponding fields. + +### 9.1.43s EC System information type 4 + +This message is optionally sent on the EC-BCCH if EC-GSM-IoT and network sharing is supported in the cell. It is sent by the network providing network sharing information and access control information for the additional PLMNs. + +Multiple instances of this message may be sent by the network. The requirements for transmission of this message are defined in see 3GPP TS 45.002. + +Message type: EC SYSTEM INFORMATION TYPE 4 + Significance: dual + Direction: network to mobile station + +``` +< EC System Information Type 4 > ::= + < Message Type : bit (3) > + < EC SI 4_INDEX : bit (2) > + < EC SI 4_COUNT : bit (2) > + < EC SI_CHANGE_MARK : bit (5) > + + { 0 | 1 < Network Sharing Information : < Network Sharing Information struct >> } + < spare padding > ; + +< Network Sharing Information struct > ::= + < Common_PLMN_Allowed : bit (1) > + < Nb_Additional_PLMNs : bit (2) > + { + { 0 | 1 < MCC : bit (12) > } < MNC : bit (12) > + { 0 | 1 < NCC Permitted : bit (8) > } + { 0 | 1 < EC_Access_Control_Class : bit (7) > + < Exception_Report_Status : bit (1) > } + } * ( val ( Nb_Additional_PLMNs ) + 1 ) ; +``` + +**Figure 9.1.43s.1: EC SYSTEM INFORMATION TYPE 4 message content** + +**Table 9.1.43s.1: EC SYSTEM INFORMATION TYPE 4 information element details** + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|--|-----|--------------------------------------------------|-----|----------------------------------------------| +|

Message Type (3 bits)
The Message Type field is encoded according to Table 10.4.4.

| | | | | | | +|

EC SI 4_INDEX (2 bits) and EC SI 4_COUNT (2 bits)
The purpose of these fields is to indicate the number of individual message instances within the sequence of EC SI 4 messages and to assign an index to identify each instance. The EC SI 4_INDEX field is binary coded, range 0 to 3, and provides an index to identify an individual EC SI 4 message instance. The EC SI 4_COUNT field is binary coded, range 0 to 3, and provides the value of the highest indexed message instance in the sequence of EC SI 4 messages.

| | | | | | | +|

EC SI_CHANGE_MARK (5 bits)
This field is defined in Table 9.1.43p.1.

| | | | | | | +|

Common_PLMN_Allowed (1 bit)
This field indicates whether or not a MS is allowed to select the Common PLMN. It is coded as follows:

Bit
0 The MS is not allowed to select the Common PLMN.
1 The MS is allowed to select the Common PLMN.
| Bit | | 0 | The MS is not allowed to select the Common PLMN. | 1 | The MS is allowed to select the Common PLMN. | +| Bit | | | | | | | +| 0 | The MS is not allowed to select the Common PLMN. | | | | | | +| 1 | The MS is allowed to select the Common PLMN. | | | | | | +|

Nb_Additional_PLMNs (2 bits)
This field indicates the number of Additional PLMN IDs broadcasted in this message. It is coded as follows:

Value
0 0 a single Additional PLMN ID is broadcast
0 1 2 Additional PLMN IDs are broadcast
| Value | | 0 0 | a single Additional PLMN ID is broadcast | 0 1 | 2 Additional PLMN IDs are broadcast | +| Value | | | | | | | +| 0 0 | a single Additional PLMN ID is broadcast | | | | | | +| 0 1 | 2 Additional PLMN IDs are broadcast | | | | | | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| 1 0 | 3 Additional PLMN IDs are broadcast | +| 1 1 | 4 Additional PLMN IDs are broadcast | +| MCC and MNC (24 bits) | | +| This field contains the PLMN ID for each Additional PLMN. If for a given MNC the MCC field is missing, the previously listed MCC in this message shall be used instead, or if no such exists, the MCC provided as part of the Location Area Identification IE in EC SYSTEM INFORMATION TYPE 2 message shall be used instead. | | +| The MCC and MNC value fields are coded as specified in sub-clause 10.5.3. | | +| NCC Permitted (8 bits) | | +| The purpose of this field is to provide for each Additional PLMN the list of allowed NCCs on the neighbour BCCH carriers. | | +| The NCC Permitted value field is coded as the value part of the NCC Permitted IE specified in sub-clause 10.5.2.27. | | +| In the absence of this field all neighbour BCCH carriers (regardless of NCC) are allowed for cell reselection. | | +| EC Access Control Class (7 bits) | | +| This field contains a bitmap indicating the barring status for Access Control Classes 0 to 15 (AC C0 to AC C15), applicable in the corresponding Additional PLMN. It is coded as defined in Table 9.1.43q.1. If this field is not present for the PLMN selected by the MS it shall assume its access class is not barred. | | +| Exception_Report_Status (1 bit) | | +| This field indicates whether sending of exception reports are allowed or not in the corresponding Additional PLMN. It is coded as defined in Table 9.1.43q.1. If this field is not present for the PLMN selected by the MS it shall assume exception reports are not barred. | | + +### 9.1.44 Talker indication + +This message is sent on the main DCCH by the mobile station to the network to give the talker information when a new layer 2 connection is established on a VGCS channel after an uplink access. See table 9.1.44.1. + +Message type: TALKER INDICATION + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.44.1: TALKER INDICATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|----------------------------------------|------------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Talker Indication Message Type | Message Type 10.4 | M | V | 1 | +| | Mobile Station Classmark | Mobile Station Classmark 2 10.5.1.6 | M | LV | 4 | +| | Mobile Identity | Mobile Identity 10.5.1.4 | M | LV | 2-9 | +| B- | Ciphering Key Sequence Number | Ciphering Key Sequence Number 10.5.1.2 | O (note 1) | TV | 1 | + +NOTE 1: In this release the MS shall provide this field if the group call is ciphered. + +#### 9.1.44a Priority Uplink Request + +If the network supports the Priority Uplink Request procedure, this message may be sent on a SDCCH by the mobile station to the network to request the uplink of the identified group call when the requested priority is higher than the current talker priority. See table 9.1.44a.1. + +Message type: PRIORITY UPLINK REQUEST + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.44a.1: PRIORITY UPLINK REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|---------------------------------------|-----------------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Priority Uplink Request Message Type | Message Type 10.4 | M | V | 1 | +| | Establishment Cause/ Random Reference | Establishment Cause/ Random Reference 10.5.2.30a | M | V | 1 | +| | Token | Token 10.5.2.66 | M | V | 4 | +| | Reduced Group Call Reference | Reduced group or broadcast call reference 10.5.2.63 | M | V | 4 | +| | Mobile Identity | Mobile Identity 10.5.1.4 | M | LV | 2-9 | + +#### 9.1.44b Data Indication + +This message contains application-specific data sent to/by mobile stations belonging to a voice group call and is transmitted on the voice group call channel or on the uplink of the dedicated channel. See table 9.1.44b.1. + +**Table 9.1.44b.1: DATA INDICATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-----------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Data Indication Message Type | Message Type 10.4 | M | V | 1 | +| | Mobile Identity | TMSI/P-TMSI 10.5.2.42 | M | V | 4 | +| | Application Data | Application Data 10.5.2.72 | M | V | 9 | +| | Data Identity | Data Identity 10.5.2.73 | M | V | 1 | + +#### 9.1.44c Data Indication 2 + +This message is sent on the main DCCH of a dedicated channel to send application-specific data from a mobile station in a voice group call. See table 9.1.44c.1. + +**Table 9.1.44c.1: DATA INDICATION 2 message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|--------------------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | DATA INDICATION 2 Message Type | Message Type
10.4 | M | V | 1 | +| | Mobile Identity | TMSI/P-TMSI
10.5.2.42 | M | V | 4 | +| | Reduced Group Call Reference | Reduced group or broadcast call reference
10.5.2.63 | M | V | 4 | +| | Application Data | Application Data
10.5.2.72 | M | V | 9 | +| | Data Identity | Data Identity
10.5.2.73 | M | V | 1 | + +### 9.1.45 Uplink access + +This message is sent in random mode on the voice group call channel uplink. It does not follow the basic format. The possible formats are presented directly below, without reference to information fields. The order of bit transmission is defined in 3GPP TS 44.004. + +The message is only one octet long, coded as shown in figure 9.1.45.1 and table 9.1.45.1. + +![Diagram of Uplink Access message content. It shows a single octet with 8 bits. Bit 8 is labeled 'ESTABLISHMENT CAUSE'. Bits 7 through 1 are labeled 'RANDOM REFERENCE'. The entire octet is labeled 'octet 1' on the right.](06291c5328a7a4335d41a48850a3a207_img.jpg) + +| | | +|----------------------------------------------------|------------------| +| 8      7      6      5      4      3      2      1 | | +| ESTABLISHMENT
CAUSE | RANDOM REFERENCE | + +octet 1 + +Diagram of Uplink Access message content. It shows a single octet with 8 bits. Bit 8 is labeled 'ESTABLISHMENT CAUSE'. Bits 7 through 1 are labeled 'RANDOM REFERENCE'. The entire octet is labeled 'octet 1' on the right. + +**Figure 9.1.45.1: UPLINK ACCESS message content** + +#### ESTABLISHMENT CAUSE (octet 1) + +This information field indicates the reason for requesting the establishment of a connection. This field has a variable length (from 3 bits up to 8 bits). + +#### RANDOM REFERENCE (octet 1) + +This is an unformatted field with variable length (from 5 bits down to 0 bits). + +The Uplink access message is coded as follows: + +(Random Reference field is filled with "x"). + +**Table 9.1.45.1: UPLINK ACCESS message content** + +| Message
8 7 6 5 4 3 2 1 | Meaning of Establishment Cause | +|----------------------------|--------------------------------------------------| +| 1 1 0 x x x x x | Subsequent talker uplink request | +| 0 0 1 0 0 1 0 1 | Reply on uplink access request | +| 1 0 1 x x x x x | Privilege subscriber request | +| 1 1 1 x x x x x | Emergency subscriber request | +| 0 0 0 x x x x x | Emergency mode reset request | +| 0 1 0 x x x x x | UL request for sending application-specific data | +| other values | reserved for future use | + +### 9.1.46 Uplink busy + +The understanding of this message is only required for mobile stations supporting VGCS talking and sending of application-specific data. + +This message is broadcasted on the voice group call channel on the main DCCH, SAPI=0, by the network in unacknowledged mode to inform the mobile station of the uplink status of the voice group call channel. See table 9.1.46.1. + +Message type: UPLINK BUSY + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.46.1: UPLINK BUSY message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|------------------------------------------|------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Uplink busy Message Type | Message Type 10.4 | M | V | 1 | +| 31 | Talker Priority and emergency indication | Talker Priority Status 10.5.2.64 | O | TLV | 3 | +| 32 | Token | Token 10.5.2.66 | O | TV | 5 | +| 33 | Talker Identity | Talker Identity 10.5.2.65 | O | TLV | 3 - 20 | +| 8- | Uplink Access Indication | Uplink Access Indication 10.5.2.74 | O | TV | 1 | + +#### 9.1.46.1 Talker Priority and Emergency Indication + +This IE contains the talker priority, the status of the emergency mode and the availability of the voice group call channel for sending uplink access requests related to talker priority. If the IE is not present then the MS assumes that the emergency mode is not set and that the network does not support talker priority. + +NOTE: The channel to be used for uplink access requests related to application-specific data is specified in the Uplink Access Indication (see sub-clause 9.1.46.4). + +#### 9.1.46.2 Token + +This IE contains the 32 bit long token for the validation of the Priority Uplink Request. + +#### 9.1.46.3 Talker Identity + +This IE contains the identity of the current talker. + +#### 9.1.46.4 Uplink Access Indication + +This IE indicates whether a mobile sending application-specific data should perform uplink access on the group call channel or via the RACH. + +### 9.1.47 Uplink free + +This message is sent on the main DCCH, in unacknowledged mode using the RR short protocol discriminator by the network to inform the mobile station of the uplink status of the voice group call channel. See table 9.1.47.1. The message indicates the uplink as free unless it is used by the network to request the mobile station to perform an uplink reply procedure. + +Message type: UPLINK FREE + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.47.1: UPLINK FREE message content** + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------------------------------| +| ::= | < RR short PD : bit > | -- See 3GPP TS 24.007 | +| | < message type : bit(5) > | -- See 10.4 | +| | < short layer 2 header : bit(2) > | -- See 3GPP TS 44.006 | +| | < Uplink Access Request : bit > | | +| | { L H < Uplink Identity Code : bit(6) > } | | +| | {     null L | -- Receiver compatible with earlier release | +| | H | -- Additions for Release-7 | +| | { 0 1 } | | +| | } | | +| | < spare padding > ; | | +| Uplink Access Request : | | | +| | L | Mobile station shall not perform the uplink reply procedure; | +| | H | Mobile station shall perform the uplink reply procedure. | +| Uplink Identity Code : | | | +| This field is coded as the binary representation of the UIC. | | | +| If provided by the network, the Uplink Identity Code shall be used by the mobile for the coding of the UPLINK ACCESS message | | | +| Emergency_Ind: | | | +| This field indicates the status of the emergency mode for the group call. | | | +| | 0 | Emergency mode not set. | +| | 1 | Emergency mode set. | +| If Emergency_Ind is not present in the message, then it is assumed that the emergency mode is not set and talker priority is not supported by the network. | | | + +### 9.1.48 Uplink release + +Only applicable for mobile stations supporting VGCS talking. + +This message is sent on the uplink of the voice group call channel to initiate a deactivation of the group transmit mode and to set the uplink free or on the uplink by a talker on the dedicated channel or on the downlink of the voice group call channel in order to reject an uplink access which was already granted by the network. See table 9.1.48.1. + +Message type: UPLINK RELEASE + +Significance: local + +Direction: both + +**Table 9.1.48.1: UPLINK RELEASE message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-----------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | Uplink Release Message Type | Message Type 10.4 | M | V | 1 | +| | RR Cause | RR Cause 10.5.2.31 | M | V | 1 | + +### 9.1.49 VGCS uplink grant + +The understanding of this message is only required for mobile stations supporting VGCS talking. + +This message is sent in unacknowledged mode on the main signalling channel by the network to the mobile station to stop the sending of access bursts from the mobile station and to change the channel configuration to a dedicated configuration. See table 9.1.49.1. + +Message type: VGCS UPLINK GRANT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.49.1: VGCS UPLINK GRANT message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|--------------------------------------|-----------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator 10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator 10.3.1 | M | V | 1/2 | +| | VGCS Uplink Grant Message Type | Message Type 10.4 | M | V | 1 | +| | Request Reference | Request Reference 10.5.2.30 | M | V | 3 | +| | Timing Advance | Timing Advance 10.5.2.40 | M | V | 1 | + +#### 9.1.49a VGCS Additional Information + +This message is sent on the main DCCH or SACCH of the voice group channel, in unacknowledged mode using the RR short protocol discriminator by the network to inform the mobile stations of the identity of the current talker. + +Mobile stations not supporting VBS or VGCS shall ignore this message. + +See Figure 9.1.49a and Table 9.1.49a. + +Message type: VGCS ADDITIONAL INFORMATION + +Significance: dual + +Direction: network to mobile station + +``` + ::= -- See 3GPP TS 24.007 + -- See sub-clause 10.4 + -- See 3GPP TS 44.006 + + +{} +; +``` + +**Figure 9.1.49a: VGCS Additional Information message content** + +**Table 9.1.49a VGCS Additional Information message content details** + +##### **talker identity length** (5 bit field) + +This field contains the length of the talker identity field in (0-17) bytes + +#### **filler bits** (3 bit field) + +This field contains the number of filler bits in the last octet of the talker identity field. The contents of this field is copied from the filler bits field within the talker identity IE that is received in the VGCS Additional Information message on the A-interface (see 3GPP TS 48.008). + +##### **talker identity** (8 \* val (talker identity length) bit field) + +Contains the identity of the current talker. The contents of this field are copied from the Talker Identity field within the Talker Identity IE included in the VGCS Additional Information message received on the A-interface (see 3GPP TS 48.008) + +#### **9.1.49b VGCS SMS Information** + +This message is sent on the SACCH of the voice group channel, in unacknowledged mode using the RR short protocol discriminator by the network to inform the mobile stations of an incoming RP-Data message for the VGCS group call. + +When the talker is on a dedicated channel the VGCS SMS Information message is also sent in unacknowledged mode on the SACCH of this channel. + +See Figure 9.1.49b and Table 9.1.49b. + +Message type: VGCS SMS INFORMATION + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.49b VGCS SMS Information message content details** + +``` + ::= + -- See 3GPP TS 24.007 + -- See sub-clause 10.4 + -- See 3GPP TS 44.006 + { + 0 + |1 + ; + + ::= + < Length : bit (8) > + < SMS Reference Number: bit (4) > + < SMS_Final_Content : bit (val(Length)) > + + ::= + < SMS Reference Number : bit (4) > + < Segment Number : bit (4) > + { + 0 -- Not the last Segment + |1 < Length : bit (8)> + < SMS_Final_Content : bit (val(Length)) > } -- Last segment +``` + +##### **Length (8 bit field)** + +This field contains the length in bits of the SMS Final Content that is contained within this message instance. + +##### **SMS Reference Number (4 bit field)** + +A number that is allocated by the BSS that identifies the RP-Data message (see 3GPP TS 24.011) over the air interface. The number is incremented by one each time a new RP-Data message is transmitted over the air interface. + +#### **Segment Number (4 bit field)** + +Identifies the segment of a RP-Data message that has been segmented over the air interface. + +**SMS\_Final\_Content (val(Length) bit field)** + +Contains the content of the last segment of a segmented RP-Data message or the entire RP-Data message of a non segmented RP-Data message. + +**SMS\_Content (n bit field)** + +Contains the content of a segment of a segmented RP-Data message when the segment is not the last segment. The field is variable in size, and fills to the end of the radio block. + +**Figure 9.1.49b VGCS SMS Information message content details** + +### 9.1.50 System information type 10 $\text{(ASCII)}$ + +The understanding of messages of this message type is only required for mobile stations supporting VGCS listening and VBS listening. A mobile station not understanding the message shall treat it as unknown message. + +Messages of this message type are optionally sent by the network in unacknowledged mode on the SACCH related to the voice broadcast channel or voice group call channel. SYSTEM INFORMATION TYPE 10 messages contain information about neighbour cells. When sent on the SACCH of a VGCS or VBS downlink, SYSTEM INFORMATION TYPE 10 messages address all mobile stations receiving that downlink within the cell. There may be different SYSTEM INFORMATION TYPE 10 messages sent on the same SACCH. + +They are not standard layer 3 messages. They shall be transferred using the short header format for SACCH messages sent in unacknowledged mode specified in 3GPP TS 24.007. + +Each SYSTEM INFORMATION TYPE 10 message defines a list of cells and may contain further information for cells of that list, a cell being identified by the pair of ARFCN and BSIC of the BCCH. Newer information about a cell received in SYSTEM INFORMATION TYPE 10 messages shall replace older information. + +Message type: SYSTEM INFORMATION TYPE 10 + +Significance: dual + +Direction: network to mobile station + +``` + + ::= + < RR short PD : bit > -- See 3GPP TS 24.007 + < message type : bit(5) > -- See 10.4 + < short layer 2 header : bit(2) > -- See 3GPP TS 44.006 + < SI10 Rest Octets : bit(160) >; -- See 10.5.2.44 + +``` + +#### 9.1.50a System information type 10bis $\text{(ASCII)}$ + +The understanding of messages of this message type is only required for mobile stations supporting VGCS listening and VBS listening. A mobile station not understanding the message shall treat it as unknown message. + +Messages of this message type are optionally sent by the network in unacknowledged mode on the SACCH related to the voice group call channel. SYSTEM INFORMATION TYPE 10bis messages contain a description of the voice group call channel in one or more neighbour cells. SYSTEM INFORMATION TYPE 10bis messages shall only refer to neighbour cells where the voice group call is active. When sent on the SACCH of a VGCS downlink, SYSTEM INFORMATION TYPE 10bis messages address all mobile stations receiving that downlink within the cell. There may be different SYSTEM INFORMATION TYPE 10bis messages sent on the same SACCH. + +They are not standard layer 3 messages. They shall be transferred using the short header format for SACCH messages sent in unacknowledged mode specified in 3GPP TS 24.007. + +Each SYSTEM INFORMATION TYPE 10bis message specifies the location of the group call channel in one or more cells. Newer information about a cell received in SYSTEM INFORMATION TYPE 10bis messages or in VGCS Neighbour Cell Information messages shall replace older information. + +Message type: SYSTEM INFORMATION TYPE 10bis + +Significance: dual + +Direction: network to mobile station + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
<SYSTEM INFORMATION TYPE 10bis> ::=   < RR short PD : bit >           -- See 3GPP TS 24.007   < message type : bit(5) >        -- See 10.4   < short layer 2 header : bit(2) > -- See 3GPP TS 44.006   < SI10bis Rest Octets : bit(160) >; -- See 10.5.2.70
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 9.1.50b System information type 10ter \$(ASCI)\$ + +The understanding of messages of this message type is only required for mobile stations supporting VGCS listening and VBS listening. A mobile station not understanding the message shall treat it as unknown message. + +Messages of this message type are optionally sent by the network in unacknowledged mode on the SACCH related to the voice group call channel. SYSTEM INFORMATION TYPE 10ter messages contain system information relating to neighbouring cells in which the voice group call is present. When sent on the SACCH of a VGCS downlink, SYSTEM INFORMATION TYPE 10ter messages address all mobile stations receiving that downlink within the cell. There may be different SYSTEM INFORMATION TYPE 10ter messages sent on the same SACCH. + +They are not standard layer 3 messages. They shall be transferred using the short header format for SACCH messages sent in unacknowledged mode as specified in 3GPP TS 24.007. + +Each SYSTEM INFORMATION TYPE 10ter message specifies, for one cell, the frequencies used in the cell and the location of the NCH channel. Newer information about a cell received in SYSTEM INFORMATION TYPE 10ter messages shall replace older information. + +Message type: SYSTEM INFORMATION TYPE 10ter + +Significance: dual + +Direction: network to mobile station + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
<SYSTEM INFORMATION TYPE 10ter> ::=   < RR short PD : bit >           -- See 3GPP TS 24.007   < message type : bit(5) >        -- See 10.4   < short layer 2 header : bit(2) > -- See 3GPP TS 44.006   < Cell Channel Description : bit (128) >   < SI10ter Rest Octets : bit(32) >; -- See 10.5.2.71
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### + +This field is syntactically and semantically equivalent to octets 2-17 of the *Cell Channel Description* information element. This information element shall be used to decode the *Mobile Allocation* IE. See sub-clause 10.5.2.1b. + +### 9.1.51 EXTENDED MEASUREMENT ORDER + +This message is sent on the SACCH by the network to the mobile station, to order the mobile station to send one extended measurement report. See table 9.1.51.1. + +A mobile station which does not support Extended Measurements shall discard this message. + +This message has a L2 Pseudo Length of 18. + +Message type: EXTENDED MEASUREMENT ORDER + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.51.1 EXTENDED MEASUREMENT ORDER message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|-----------------------------------------------------|----------|--------|--------| +| | L2 pseudo length | L2 pseudo length
10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Extended Measurement
Order | Message Type
10.4 | M | V | 1 | +| | Extended Measurement
Frequency List | Extended Measurement
Frequency List
10.5.2.46 | M | V | 16 | + +### 9.1.52 Extended measurement report + +This message is sent on the SACCH by the mobile station to the network to report extended measurement results about the signal strength on specified carriers. See table 9.1.52.1. + +Message type: EXTENDED MEASUREMENT REPORT + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.52.1: EXTENDED MEASUREMENT REPORT message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|---------------------------------------------|----------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Extended Measurement Report
Message Type | Message Type
10.4 | M | V | 1 | +| | Extended Measurement
Results | Extended Measurement
Results
10.5.2.45 | M | V | 16 | + +### 9.1.53 Application Information + +This message is sent on the main DCCH by the network or the mobile station to convey an embedded Application Protocol Data Unit (APDU) or APDU segment between the network and the mobile station. See table 9.1.53.1. + +Message type: Application + +Significance: global + +Direction: both + +**Table 9.1.53.1: Application Information message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | +|-----|-----------------------------------------|--------------------------------|----------|--------|--------| +| | RR management Protocol
Discriminator | Protocol discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Application Information
message type | Message type
10.4 | M | V | 1 | +| | APDU ID | APDU ID
10.5.2.48 | M | V | 1/2 | +| | APDU Flags | APDU Flags
10.5.2.49 | M | V | 1/2 | +| | APDU Data | APDU Data
10.5.2.50 | M | LV | 2 to N | + +### 9.1.54 MEASUREMENT INFORMATION + +This message is sent on the SACCH by the network to the mobile station. If not all information fits into one message, the remaining information will be sent in other instances of this message. This message may contain a combination of information for e.g. 3G Neighbour Cell Description, E-UTRAN Parameters Description, 3G Measurement Control Parameters, Real Time Differences, BSICs, Report priority, Measurement parameters or 3G Measurement parameters. + +Message type: MEASUREMENT INFORMATION + +Significance: dual + +Direction: network to mobile station + +``` + + ::= + < RR short PD : bit > -- See 3GPP TS 24.007 + < Message type : bit (5) > -- See 10.4 + < Short layer 2 header : bit (2) > -- See 3GPP TS 44.006 + < BA_IND : bit > + < 3G_BA_IND : bit > + < MP_CHANGE_MARK : bit > + < MI_INDEX : bit (4) > + < MI_COUNT : bit (4) > + < PWRC : bit > + < REPORT_TYPE : bit > + < REPORTING_RATE : bit > + < INVALID_BSIC_REPORTING : bit > + { 0 | 1 < Real Time Difference Description : < Real Time Difference Description struct >> } + { 0 | 1 < BSIC Description : < BSIC Description struct >> } + { 0 | 1 < REPORT PRIORITY Description : < REPORT PRIORITY Description struct >> } + { 0 | 1 < MEASUREMENT Parameters Description : < MEASUREMENT Parameters Description struct >> } + { 0 | 1 < extension length : bit (8) > + < spare bit (val(extension length)+1) > } -- used for future extensions of the 2G parameters + { 0 | 1 < 3G Neighbour Cell Description : < 3G Neighbour Cell Description struct >> } + { 0 | 1 < 3G MEASUREMENT Parameters Description : < 3G MEASUREMENT Parameters Description struct +>> } + { + null | L -- Receiver compatible with earlier release + | H + -- Additions in Rel-5: + { 0 | 1 < 3G ADDITIONAL MEASUREMENT Parameters Description 2 : + < 3G ADDITIONAL MEASUREMENT Parameters Description 2 struct >> } + { + null | L -- Receiver compatible with earlier release + | H + -- Additions in Rel-7: + { 0 | 1 < 700_REPORTING_OFFSET : bit (3) > + < 700_REPORTING_THRESHOLD : bit (3) > } + { 0 | 1 < 810_REPORTING_OFFSET : bit (3) > + < 810_REPORTING_THRESHOLD : bit (3) > } + { + null | L -- Receiver compatible with earlier release + | H + -- Additions in Rel-8 + { 0 | 1 < 3G Supplementary Parameters Description : + < 3G Supplementary Parameters Description struct >> } + { 0 | 1 < E-UTRAN Parameters Description : + < E-UTRAN Parameters Description struct >> } + { 0 | 1 < E-UTRAN CSG Description : < E-UTRAN CSG Description struct >> } + { + null | L -- Receiver compatible with earlier release + | H + -- Additions in Rel-9 + { 0 | 1 < 3G CSG Description : < 3G CSG Description struct >> } + { 0 | 1 < UTRAN CSG Cells Reporting Description : + < UTRAN CSG Cells Reporting Description struct >> } + { null | L -- Receiver compatible with earlier release + | H + -- Additions in Rel-11 + { 0 | 1 < E-UTRAN NC with extended EARFCNs Description : + < E-UTRAN NC with extended EARFCNs Description struct >> } + } + } + } + } + } + } + } + < spare padding > ; + +< 3G Neighbour Cell Description struct > ::= + { 0 | 1 < 3G_Wait : bit (3) > } + { 0 | 1 < Index_Start_3G : bit (7) > } + { 0 | 1 < Absolute_Index_Start_EMR : bit (7) > } + { 0 | 1 < UTRAN FDD Description : < UTRAN FDD Description struct >> } + { 0 | 1 < UTRAN TDD Description : < UTRAN TDD Description struct >> } + { 0 | 1 < CDMA2000 Description : < CDMA2000 Description struct >> } ; + +< UTRAN FDD Description struct > ::= + { 0 | 1 < Bandwidth_FDD : bit (3) > } + { 1 < Repeated UTRAN FDD Neighbour Cells : < Repeated UTRAN FDD Neighbour Cells struct >> } ** 0 ; + +``` + +``` + +< Repeated UTRAN FDD Neighbour Cells struct > ::= +0 < FDD-ARFCN : bit (14) > -- The value '1' was used in an earlier version of + -- the protocol and shall not be used. +< FDD_Indic0 : bit > +< NR_OF_FDD_CELLS : bit (5) > +< FDD_CELL_INFORMATION Field : bit(p(NR_OF_FDD_CELLS)) > ; -- p(x) defined in table 9.1.54.1. + +< UTRAN TDD Description struct > ::= +{ 0 | 1 < Bandwidth_TDD : bit (3) > } +{ 1 < Repeated UTRAN TDD Neighbour Cells : Repeated UTRAN TDD Neighbour Cells struct > } ** 0 ; + +< Repeated UTRAN TDD Neighbour Cells struct > ::= +0 < TDD-ARFCN : bit (14) > -- The value '1' was used in an earlier version of + -- the protocol and shall not be used. +< TDD_Indic0 : bit > +< NR_OF_TDD_CELLS : bit (5) > +< TDD_CELL_INFORMATION Field : bit(q(NR_OF_TDD_CELLS)) > ; -- q(x) defined in table 9.1.54.1. + +< CDMA 2000 Description struct > ::= + < cdma2000 frequency band : bit(5) > + < cdma2000 frequency : bit(11) > + < number_cdma2000_cells : bit (5) > + + { < Pilot PN offset : bit (9) > -- this information is enough for 1X Common Pilot + + { 0 | 1 { + 000 { < TD_MODE : bit (2) > < TD_POWER_LEVEL : bit (3) > } + -- additional information for 1X Common Pilot with Transmit Diversity + + | 001 { < QOF : bit (2) > < WALSH_LEN_A : bit (3) > + < AUX_PILOT_WALSH : bit(val(WALSH_LEN_A)+6) > } + -- additional information for 1X Auxiliary Pilot + + | 010 { < QOF : bit (2) > < WALSH_LEN_B : bit (3) > + < AUX_TD_WALSH : bit (val(WALSH_LEN_B)+6) > + < AUX_TD_POWER_LEVEL : bit (2) > < TD_MODE : bit (2) > } + -- additional information for 1X Auxiliary Pilot with Transmit Diversity + + | 011 { < SR3_PRIM_PILOT : bit (2) > < SR3_PILOT_POWER1 : bit (3) > + < SR3_PILOT_POWER2 : bit(3) > } + -- additional information for 3X Common Pilot + + | 110 { < SR3_PRIM_PILOT : bit (2) > < SR3_PILOT_POWER1 : bit (3) > + < SR3_PILOT_POWER2 : bit (3) > < QOF : bit (2) > + < WALSH_LEN_C : bit (3) > + < AUX_WALSH_LEN : bit(val(WALSH_LEN_C)+6) > + { 0 | 1 < QOF1 : bit (2) > < WALSH_LENGTH1 : bit (3) > + < AUX_PILOT_WALSH1 : bit(val(WALSH_LENGTH1)+6) > } + { 0 | 1 < QOF2 : bit (2) > < WALSH_LENGTH2 : bit (3) > + < AUX_PILOT_WALSH2 : bit(val(WALSH_LENGTH2)+6) > } + } + -- additional information for 3X Auxiliary Pilot + } + } + } * val(number_cdma2000_cells) ; + +< Real Time Difference Description struct > ::= +{ 0 | 1 { 0 | 1 < BA_Index_Start_RTD : bit (5) > } --default value=0 + < RTD Struct : < RTD6 Struct > > + { 0 < RTD Struct : < RTD6 Struct > > } ** 1 } -- '0' indicates to increment by 1 + -- the index of the frequency in the BA (list) + +{ 0 | 1 { 0 | 1 < BA_Index_Start_RTD : bit (5) > } --default value=0 + < RTD Struct : < RTD12 Struct > > + { 0 < RTD Struct : < RTD12 Struct > > } ** 1 }; -- '0' indicates to increment by 1 + -- the index of the frequency in the BA (list) + +``` + +``` + +< RTD6 Struct > ::= + { 0 | 1 < RTD : bit (6) > } ** 1; -- Repeat until '1' ; '1' means last RTD for this frequency + +< RTD12 Struct > ::= + { 0 | 1 < RTD : bit (12) > } ** 1; -- Repeat until '1' ; '1' means last RTD for this frequency + +< BSIC Description struct > ::= + { 0 | 1 < BA_Index_Start_BSIC : bit (5) > } -- default value=0 + < BSIC : bit (6) > + < Number_Remaining_BSIC : bit (7) > + { + < Frequency_Scrolling : bit > -- 0 means same frequency + < BSIC : bit (6) > + } * (val(Number_Remaining_BSIC)); + +< REPORT PRIORITY Description struct > ::= + < Number_Cells : bit (7) > + { REP_PRIORITY : bit } * (val(Number_Cells)); + +< MEASUREMENT PARAMETERS Description struct > ::= + { 0 | 1 < MULTIBAND_REPORTING : bit (2) > } + { 0 | 1 < SERVING_BAND_REPORTING : bit (2) > } + < SCALE_ORD : bit (2) > + + { 0 | 1 < 900_REPORTING_OFFSET : bit (3) > + < 900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1800_REPORTING_OFFSET : bit (3) > + < 1800_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 400_REPORTING_OFFSET : bit (3) > + < 400_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1900_REPORTING_OFFSET : bit (3) > + < 1900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 850_REPORTING_OFFSET : bit (3) > + < 850_REPORTING_THRESHOLD : bit (3) > } ; + +< 3G MEASUREMENT PARAMETERS Description struct > ::= + < Qsearch_C : bit (4) > + { 1 | < Ignore : bit = < no string >> } -- this bit shall be ignored by the receiver + -- for backward compatibility with earlier releases + < FDD_REP_QUANT : bit (1) > -- FDD Parameters + { 0 | 1 < FDD_MULTIRAT_REPORTING : bit (2) > } + { 0 | 1 < FDD_REPORTING_OFFSET : bit (3) > + < FDD_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) > } -- TDD Parameters + { 0 | 1 < TDD_REPORTING_OFFSET : bit (3) > + < TDD_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < CDMA2000_MULTIRAT_REPORTING : bit (2) > } -- CDMA2000 Parameters + { 0 | 1 < CDMA2000_REPORTING_OFFSET : bit (3) > + < CDMA2000_REPORTING_THRESHOLD : bit (3) > } ; + +< 3G ADDITIONAL MEASUREMENT Parameters Description 2 struct > ::= + { 0 | 1 < FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; + +< 3G Supplementary Parameters Description struct > ::= + < UTRAN_Start : bit > + < UTRAN_Stop : bit > + { 0 | 1 < 3G Measurement Control Parameters Description : + < 3G Measurement Control Parameters Description struct >> } ; + +< 3G Measurement Control Parameters Description struct > ::= + { 0 | 1 < DEFAULT_Measurement_Control_UTRAN : bit(1) > } + { 1 < Repeated UTRAN Measurement Control Parameters : + < Repeated UTRAN Measurement Control Parameters struct >> } ** 0 ; + +``` + +``` + +< Repeated UTRAN Measurement Control Parameters struct > ::= + { 1 < UTRAN_FREQUENCY_INDEX : bit(5) > } ** 0 + < Measurement_Control_UTRAN : bit(1) > ; + +< E-UTRAN Parameters Description struct > ::= + < E-UTRAN_Start : bit > + < E-UTRAN_Stop : bit > + { 0 | 1 < E-UTRAN Measurement Parameters Description : + < E-UTRAN Measurement Parameters Description struct >> } + { 1 < Repeated E-UTRAN Neighbour Cells : < Repeated E-UTRAN Neighbour Cells struct >> } ** 0 + { 1 < Repeated E-UTRAN Not Allowed Cells : < Repeated E-UTRAN Not Allowed Cells struct >> } ** 0 + { 0 | 1 < E-UTRAN Measurement Control Parameters Description : + < E-UTRAN Measurement Control Parameters Description struct >> } ; + +< E-UTRAN Measurement Parameters Description struct > ::= + < Qsearch_C_E-UTRAN : bit(4) > + < E-UTRAN_REP_QUANT : bit > + < E-UTRAN_MULTIRAT_REPORTING : bit(2) > + { 0 { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD : bit(3) > -- FDD 6 bit reporting + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD : bit(3) > -- TDD 6 bit reporting + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } + | 1 { 0 | 1 < E-UTRAN_FDD_MEASUREMENT_REPORT_OFFSET : bit(6) > -- FDD 3 bit reporting + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } + { 0 | 1 < E-UTRAN_TDD_MEASUREMENT_REPORT_OFFSET : bit(6) > -- TDD 3 bit reporting + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } + < REPORTING_GRANULARITY : bit(1) > } ; + +< Repeated E-UTRAN Neighbour Cells struct > ::= + < EARFCN : bit (16) > + { 1 < EARFCN : bit (16) > } ** 0 + { 0 | 1 < Measurement Bandwidth : bit (3) > } ; + +< Repeated E-UTRAN Not Allowed Cells struct > ::= + < Not Allowed Cells : < PCID Group IE >> + { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 ; + +< E-UTRAN Measurement Control Parameters Description struct > ::= + { 0 | 1 < DEFAULT_Measurement_Control_E-UTRAN : bit(1) > } + { 1 < Repeated E-UTRAN Measurement Control Parameters : + < Repeated E-UTRAN Measurement Control Parameters struct >> } ** 0 ; + + + +--- + + +< Repeated E-UTRAN Measurement Control Parameters struct > ::= + { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 + < Measurement_Control_E-UTRAN : bit(1) > ; + + + +--- + + +< E-UTRAN CSG Description struct > ::= + { 1 < CSG_PCI_SPLIT : < PCID Group IE >> + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 } ** 0 ; +< 3G CSG Description struct > ::= + { 1 < CSG_PSC_SPLIT : < PSC Group IE >> + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 } ** 0 + { 1 { 0 < CSG_FDD_UARFCN : bit (14) > | 1 < CSG_TDD_UARFCN : bit (14) > } } ** 0 ; + -- UTRAN CSG Dedicated Frequencies + +< UTRAN CSG Cells Reporting Description struct > ::= + { 0 | 1 < UTRAN_CSG_FDD_REPORTING_THRESHOLD : bit(3) > + < UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } + { 0 | 1 < UTRAN_CSG_TDD_REPORTING_THRESHOLD : bit(3) > } ; + +``` + +``` + +< E-UTRAN NC with extended EARFCNs Description struct > ::= + { 1 < Repeated E-UTRAN NC with extended EARFCNs struct > } ** 0 ; + +< Repeated E-UTRAN NC with extended EARFCNs struct > ::= + < EARFCN_extended : bit (18) > + { 1 < EARFCN_extended : bit (18) > } ** 0 + { 0 | 1 < Measurement Bandwidth : bit (3) > } ; + +``` + +**Figure 9.1.54.1: Measurement Information message content** + +**Table 9.1.54.1: Measurement Information information element details.** + +**BA\_IND** (1 bit), BCCH allocation sequence number indication. + +The BA\_IND is needed to allow the network to discriminate measurements results related to different GSM Neighbour Cell lists sent to the MS, as described in sub-clause 3.4.1.2.1. The value of this parameter is reflected in the ENHANCED MEASUREMENT REPORT message and in the MEASUREMENT REPORT message. + +**3G\_BA\_IND** (1 bit), 3G Sequence Number. + +The 3G\_BA\_IND is needed to indicate new sets of 3G Neighbour Cell information or E-UTRAN Neighbour Cell information, as described in sub-clause 3.4.1.2.1. The value received is reflected in the MEASUREMENT REPORT and ENHANCED MEASUREMENT REPORT message. + +**MP\_CHANGE\_MARK** (1 bit), measurement parameters change mark. + +This parameter is used to indicate the MS a change of information concerning REPORT PRIORITY, MEASUREMENT INFORMATION, 3G MEASUREMENT INFORMATION and 3G Measurement Control Parameters, as described in sub-clause 3.4.1.2.1., + +**MI\_INDEX** (4 bits) and **MI\_COUNT** (4 bits) + +The purpose of the MI\_INDEX and MI\_COUNT fields is to indicate the number of individual messages within the sequence of MEASUREMENT INFORMATION messages and to assign an index to identify each of them. The MI\_INDEX field is binary coded, range 0 to 15, and provides an index to identify the individual MEASUREMENT INFORMATION message. The MI\_COUNT field is binary coded, range 0 to 15, and provides the MI\_INDEX value for the last (highest indexed) message in the sequence of MEASUREMENT INFORMATION messages. + +**PWRC**, Power control indicator (1 bit field) + +The use of this parameter is defined in 3GPP TS 45.008. + +**Bit** + +- | | | +|---|-----------------| +| 0 | PWRC is not set | +| 1 | PWRC is set. | + +**REPORT\_TYPE** (1bit) + +This parameter is used to indicate to the mobile to use the Enhanced Measurement report or Measurement report messages for reporting: + +**Bit** + +- | | | +|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | The MS shall use the Enhanced Measurement Report message for reporting if at least one BSIC is allocated to each BA (list) frequency. Otherwise, the Measurement Report message shall be used. | +| 1 | The MS shall use the Measurement Report message for reporting. | + +**REPORTING\_RATE** (1 bit) + +This parameter is used for measurements, see 3GPP TS 45.008. + +**bit** + +- | | | +|---|---------------------------------| +| 0 | SACCH rate reporting | +| 1 | Reduced reporting rate allowed. | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

INVALID_BSIC_REPORTING (1 bit)
This field specifies if cells with invalid BSIC and allowed NCC part of BSIC are allowed to be reported or not, see 3GPP TS 45.008.

bit
0     Report on cells with invalid BSIC and allowed NCC part of BSIC is not allowed.
1     Report on cells with invalid BSIC and allowed NCC part of BSIC is allowed.

| +|

3G Neighbour Cell Description:

The building of the 3G Neighbour Cell list and the ordering of indices within each Radio Access Technology is described in sub-clause 3.4.1.2.1.1, 'Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description'.

| +|

3G WAIT (3 bits)
When 3G_BA_IND is received in a changed state, this parameter indicates the number of instances of MEASUREMENT INFORMATION messages that contain 3G Neighbour Cell Description which shall be received before the MS reports on the new 3G Neighbour Cell list. Two different instances of MEASUREMENT INFORMATION messages are two MEASUREMENT INFORMATION messages with different MI_INDEX. See sub-clause 3.4.1.2.1.

bit
3 2 1
0 0 0   1 instance that contain 3G Neighbour Cell Description shall be received
0 0 1   2 instances that contain Neighbour Cell Description shall be received
:
:
1 1 1   8 instances that contain Neighbour Cell description shall be received

| +|

Index_Start_3G (7 bit)
This optional information element indicates the binary value of the first index to use to build this instance of the 3G Neighbour Cell list. When missing, the value 0 is assumed. See sub-clause 3.4.1.2.1.1.

| +|

Absolute_Index_Start_EMR (7 bit)
This parameter indicates in binary the value to be added to the indexes of the 3G Neighbour Cell list for reporting 3G Cells with the ENHANCED MEASUREMENT REPORT message (see sub-clause 3.4.1.2.1.1). If different values are received for this parameter in different instances of this message, the instance with the highest index shall be used. If this parameter is absent in all instances of the message, the value "0" shall be used.

NOTE:    This parameter is not used for reporting 3G Cells with the MEASUREMENT REPORT message, see sub-clause 10.5.2.20, 'Measurement Results'.

| +|

UTRAN FDD Description:

| +|

Bandwidth_FDD (3bit field)
This optional information element will be used for future releases of the protocol. When missing, this indicates the present FDD bandwidth. When present, this shall not be considered as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly.

| +|

FDD_ARFCN (14 bit field)
This optional information element is defined as the UARFCN in 3GPP TS 25.101. Any non-supported frequency shall not be considered as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly.

| +|

FDD_Indic0, information 0 indicator (1 bit):
This field indicates if the FDD_CELL_INFORMATION parameter value '0000000000' is a member of the set.

Bit
0        parameter value '0000000000' is not a member of the set
1        parameter value '0000000000' is a member of the set

NOTE:    This bit FDD_Indic0 is equivalent to the bit F0 bit in the frequency list information element (see sub-clause 10.5.2.13.3).

| + +#### **NR\_OF\_FDD\_CELLS (5 bit field)** + +This field defines the number of FDD\_CELL\_INFORMATION parameters. + +#### **FDD\_CELL\_INFORMATION Field (p bit field)** + +This field allows to compute a set of 10-bit-long FDD\_CELL\_INFORMATION parameters, re-using the *Range 1024 format* compression algorithm, see Annex J: 'Algorithm to encode frequency list information'. The formulas for decoding are given in the 'Range 1024 format' sub-clause, 10.5.2.13.3. The consecutive parameters of this field are concatenated, starting with w1, and then w2, w3... + +The total number of bits p of this field depends on the value of the parameter NR\_OF\_FDD\_CELLS = n, as follows: + +| n | p | n | p | n | p | n | p | +|---|----|---|----|----|-----|-------|-----| +| 0 | 0 | 5 | 44 | 10 | 81 | 15 | 116 | +| 1 | 10 | 6 | 52 | 11 | 88 | 16 | 122 | +| 2 | 19 | 7 | 60 | 12 | 95 | 17-31 | 0 | +| 3 | 28 | 8 | 67 | 13 | 102 | | | +| 4 | 36 | 9 | 74 | 14 | 109 | | | + +**Table 9.1.54.1a.** + +If n=0 and FDD\_Indic0=0, this indicates the 3G Neighbour Cell list index for report on RSSI, see 3GPP TS 45.008. + +If n is equal or greater than 17, this shall not be considered as an error; the corresponding index in the 3G Neighbour Cell list shall be incremented by one. The entry created in the 3G Neighbour Cell list does not contain valid information. + +For each (10-bit-long) decoded Parameter, bits 1-9 are the Scrambling Code and bit 10 is the corresponding Diversity Parameter. + +#### **Scrambling Code (9 bit field)** + +This parameter indicates the Primary Scrambling Code as defined in 3GPP TS 25.213. + +#### **Diversity (1 bit field)** + +This parameter indicates if diversity is applied for the cell: + +#### Bit + +- 0 Diversity is not applied for this cell +- 1 Diversity is applied for this cell. + +#### **UTRAN TDD Description:** + +#### **Bandwidth\_TDD (3 bit field)** + +This optional information element refers to 3GPP TS 25.331. + +#### Bit + +321 + +000 3.84Mcps + +001 1.28Mcps + +All other values shall not be interpreted as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly (and no measurements can be performed). When missing, this indicates 3.84 Mcps. + +#### **TDD\_ARFCN (14 bit field)** + +This optional information element is defined as the UARFCN in 3GPP TS 25.102. Any non-supported frequency shall not be considered as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly. + +#### **TDD\_Indic0, information 0 indicator (1 bit):** + +This field indicates if the TDD\_CELL\_INFORMATION parameter value '0000000000' is a member of the set. + +##### Bit + +- 0 parameter value '0000000000' is not a member of the set +- 1 parameter value '0000000000' is a member of the set + +#### **NR\_OF\_TDD\_CELLS (5 bit field)** + +This field defines the number of TDD\_CELL\_INFORMATION parameters. + +#### **TDD\_CELL\_INFORMATION Field (q bit field)** + +This field allows to compute a set of 9-bit-long TDD\_CELL\_INFORMATION parameters, re-using the *Range 512 format* compression algorithm, see Annex J: 'Algorithm to encode frequency list information'. The formulas for decoding are given in the 'Range 512 format' sub-clause, 10.5.2.13.4, with $w_0=0$ . The consecutive parameters of this field are concatenated, starting with $w_1$ , and then $w_2$ , $w_3$ ... + +The total number of bits $q$ of this field depends on the value of the parameter $NR\_OF\_TDD\_CELLS = m$ , as follows: + +| m | q | m | q | m | q | m | q | m | q | +|---|----|---|----|----|----|----|-----|-------|-----| +| 0 | 0 | 5 | 39 | 10 | 71 | 15 | 101 | 20 | 126 | +| 1 | 9 | 6 | 46 | 11 | 77 | 16 | 106 | 21-31 | 0 | +| 2 | 17 | 7 | 53 | 12 | 83 | 17 | 111 | | | +| 3 | 25 | 8 | 59 | 13 | 89 | 18 | 116 | | | +| 4 | 32 | 9 | 65 | 14 | 95 | 19 | 121 | | | + +**Table 9.1.54.1b.** + +If $m=0$ and $TDD\_Indic0=0$ or $m$ is equal or greater than 21, this shall not be considered as an error; the corresponding index in the 3G Neighbour Cell list shall be incremented by one. The entry created in the 3G Neighbour Cell list does not contain valid information. + +For each (9-bit-long) decoded Parameter, bits 1-7 are the Cell Parameter, bit 8 is the Sync Case TSTD and bit 9 is the Diversity TDD bit. + +#### **Cell Parameter (7 bit field)** + +This parameter is defined in 3GPP TS 25.213. + +#### **Sync Case TSTD (1 bit field)** + +For 3.84 Mcps TDD, this parameter indicates the Sync Case as defined in 3GPP TS 25.304. + +Bit + +- 0 Sync case 1 +- 1 Sync case 2. + +For 1.28 Mcps TDD, this indicates if TSTD (see 3GPP TS 25.224) is applied for the cell: + +Bit + +- 0 TSTD is not applied for this cell +- 1 TSTD is applied for this cell. + +#### **Diversity TDD (1 bit field)** + +This parameter indicates if SCTD (see 3GPP TS 25.224) is applied for the cell: + +Bit + +- 0 SCTD is not applied for this cell +- 1 SCTD is applied for this cell. + +#### **CDMA 2000 Description:** + +##### **cdma2000 frequency band (5 bit field)** + +A binary representation of cdma2000 BAND\_CLASS, as defined in TIA/EIA-IS-2000-5-A. The mobile station shall ignore all the information relative to a cdma2000 frequency band that it can not support. + +##### **cdma2000 frequency (5 bit field)** + +A binary representation of cdma2000 CDMA\_FREQ, as defined in TIA/EIA-IS-2000-5-A. The mobile station shall ignore all the information relative to a cdma2000 frequency that it can not support. + +##### **number\_cdma2000\_cells (5 bit field)** + +This field indicates the number of CDMA 2000 neighbour cells. + +##### **cdma2000 Pilot PN offset (9 bit field)** + +A binary representation of the PN offset of the Pilot PN sequence (in units of 64 cdma2000 1x-chips), PILOT\_PN, as defined in TIA/EIA-IS-2000-5-A. + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

TD_MODE (2 bit field)
An indication of transmit diversity mode is specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore TD_MODE if it does not support 1X Common Pilot with Transmit Diversity.

| +|

TD_POWER_LEVEL (3 bit field)
Power level of the Transmit Diversity Pilot relative to that of the Forward Pilot Channel as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore TD_POWER_LEVEL if it does not support 1X Common Pilot with Transmit Diversity.

| +|

QOF (2 bit field)
Quasi-orthogonal function index is defined in TIA/EIA-IS-2000-5-A. The mobile station shall ignore QOF if it does not support the quasi-orthogonal function.

| +|

WALSH_LEN_A, WALSH_LEN_B and WALSH_LEN_C (3 bit field each)
A three bit field to indicate the length of the Walsh code for the pilot that is used in as the Auxiliary Pilot, and specified as WALSH_LEN in TIA/EIA-IS-2000-5-A. The mobile station shall ignore WALSH_LEN if it does not support 1X Auxiliary Pilot.

| +|

AUX_PILOT_WALSH (var. length)
Indicates the walsh code corresponding to the Auxiliary Pilot, as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore AUX_PILOT_WALSH if it does not support 1X Auxiliary Pilot.

| +|

AUX_TD_WALSH (var. length)
Indicates the walsh code corresponding to the Auxiliary Transmit Diversity Pilot, as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore AUX_TD_WALSH if it does not support 1X Auxiliary Pilot with Transmit Diversity.

| +|

AUX_TD_POWER_LEVEL (2 bit field)
Power level of the Auxiliary Transmit Diversity Pilot relative to that of the Forward Pilot Channel as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore AUX_TD_POWER_LEVEL if it does not support 1X Auxiliry Pilot with Transmit Diversity.

| +|

SR3_PRIM_PILOT (2 bit field)
Position of the primary SR3 pilot as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore SR3_PRIM_PILOT if it does not support 3X Common Pilot.

| +|

SR3_PILOT_POWER1 (2 bit field)
Relative power level between the primary SR3 pilot and the pilot on the lower frequency of the two remaining SR3 frequencies, as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore SR3_PILOT_POWER1 if it does not support 3X Common Pilot.

| +|

SR3_PILOT_POWER2 (2 bit field)
Relative power level between the primary SR3 pilot and the pilot on the higher frequency of the two remaining SR3 frequencies, as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore SR3_PILOT_POWER2 if it does not support 3X Common Pilot.

| +|

QOF1 (1 bit field), WALSH_LEN1 (3 bit field) and AUX_PILOT_WALSH1 (var. length)
Are the corresponding quantities for pilot on the lower frequency of the two remaining SR3 frequencies, as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore QOF1, WALSH_LEN1 and AUX_PILOT_WALSH1 if it does not support 3X Auxiliary Pilot.

| +|

QOF2 (2 bit field), WALSH_LENGTH2 (3 bit field) and AUX_PILOT_WALSH2 (var. length)
Are the corresponding quantities for pilot on the higher frequency of the two remaining SR3 frequencies, as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore QOF2, WALSH_LEN2 and AUX_PILOT_WALSH2 if it does not support 3X Auxiliary Pilot.

| + +#### **REPORT PRIORITY Description** + +If the *REPORT PRIORITY Description* is included in more than one instance of the MEASUREMENT INFORMATION message, the *REPORT PRIORITY Description* of the instance with the highest MI\_INDEX shall be used. + +##### **REP\_PRIORITY bit:** + +**0** Normal reporting priority + +**1** High reporting priority + +The use of these bits is defined in sub-clause 3.4.1.2.1.5 'Report Priority Description'. + +#### **BSIC Description** + +BSIC parameters are used to create the GSM Neighbour Cell list, see sub-clause 3.4.1.2.1.2 'Deriving the GSM Neighbour Cell list from the BSICs and the BA (list)'. + +The first **BSIC** parameter received in the structure relates to the index in the BA(list) frequency referenced by the parameter **BA\_Index\_Start\_BSIC** (index 0 if **BA\_Index\_Start\_BSIC** is missing). Then the + +**FREQUENCY\_SCROLLING** bit indicates whether the next **BSIC** in the structure relates to the same frequency in the BA(list), with '0', or if the next **BSIC** in the structure relates to the subsequent frequency in the BA (list), with '1'. Each next **BSIC** within the structure creates a subsequent GSM Cell list index. + +When **BSIC** information is received in different instances, the first **BSIC** referring to a BA (list) index in one instance shall be allocated the subsequent GSM Cell list index than the last **BSIC** referring to a BA (list) index in the previously numbered message instance. + +GSM Cell list index = 0 is defined by the first **BSIC** parameter received in the lowest numbered message instance. + +#### **Real Time Difference Description** + +#### **BA\_Index\_Start\_RTD** (5 bit field) + +This field indicates the BA (list) index for the first **RTD** parameter. When missing, the value '0' is assumed. + +**RTD** (6 or 12 bit field) are defined in 3GPP TS 45.008. + +The use of these parameters is defined in sub-clause 3.4.1.2.1.4, 'Real Time Differences'. + +#### **MEASUREMENT PARAMETERS Description** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. If the *MEASUREMENT PARAMETERS Description* is included in more than one instance of the MEASUREMENT INFORMATION message, the *MEASUREMENT PARAMETERS Description* of the instance with the highest MI\_INDEX shall be used. + +#### **3G MEASUREMENT PARAMETERS Description** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. If the 3G *MEASUREMENT PARAMETERS Description* is included in more than one instance of the MEASUREMENT INFORMATION message, the 3G *MEASUREMENT PARAMETERS Description* of the instance with the highest MI\_INDEX shall be used. + +##### **3G ADDITIONAL MEASUREMENT Parameters Description 2** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. If the 3G *ADDITIONAL MEASUREMENT Parameters Description 2* is included in more than one instance of the MEASUREMENT INFORMATION message, the 3G *ADDITIONAL MEASUREMENT Parameters Description 2* of the instance with the highest MI\_INDEX shall be used. + +##### **700\_REPORTING\_OFFSET** (3 bit field) + +##### **700\_REPORTING\_THRESHOLD** (3 bit field) + +These fields are used for measurements as defined in 3GPP TS 45.008. If these fields are included in more than one instance of the MEASUREMENT INFORMATION message, those of the instance with the highest MI\_INDEX shall be used. + +##### **810\_REPORTING\_OFFSET** (3 bit field) + +##### **810\_REPORTING\_THRESHOLD** (3 bit field) + +These fields are used for measurements as defined in 3GPP TS 45.008. If these fields are included in more than one instance of the MEASUREMENT INFORMATION message, those of the instance with the highest MI\_INDEX shall be used. + +#### **3G Supplementary Parameters Description** + +##### **UTRAN\_Start** (1 bit field) + +This field indicates whether this instance of the message is the first one to contain UTRAN related parameters. It is coded as follows: + +- 0 This is not the first instance of the message +- 1 This is the first instance of the message + +##### **UTRAN\_Stop** (1 bit field) + +This field indicates whether this instance of the message is the last one to contain UTRAN related parameters. It is coded as follows: + +- 0 This is not the last instance of the message +- 1 This is the last instance of the message + +#### **3G Measurement Control Parameters Description** + +If this IE is present it overrides any old data held by the mobile station for these parameters. + +If the *3G Neighbour Cell Description* IE is included in the message, the contents of this IE shall be ignored. + +##### **DEFAULT\_Measurement\_Control\_UTRAN** (1 bit field) + +This field is used to control whether measurements are made on UTRAN neighbour cells. The definition of this field is same as the definition of *Measurement\_Control\_UTRAN* as defined in 3GPP TS 45.008. Any UTRAN frequency not explicitly listed in the *Repeated UTRAN Measurement Control Parameters* structure shall be assigned this value. + +##### **Repeated UTRAN Measurement Control Parameters** + +##### **UTRAN\_FREQUENCY\_INDEX** (5 bit field) + +This field is an index into the 3G Frequency list (see sub-clause 3.4.1.2.1.7c). + +##### **Measurement\_Control\_UTRAN** (1 bit field) + +This field is used to control whether measurements are made on UTRAN neighbour cells for the UTRAN frequency referenced by *UTRAN\_FREQUENCY\_INDEX*, as defined in 3GPP TS 45.008. This parameter applies to each UTRAN frequency indexed within this structure. + +#### **E-UTRAN Parameters Description** + +##### **E-UTRAN\_Start** (1 bit field) + +This field indicates whether this instance of the message is the first one to contain E-UTRAN related parameters. It is coded as follows: + +- 0 This is not the first instance of the message +- 1 This is the first instance of the message + +##### **E-UTRAN\_Stop** (1 bit field) + +This field indicates whether this instance of the message is the last one to contain E-UTRAN related parameters. It is coded as follows: + +- 0 This is not the last instance of the message +- 1 This is the last instance of the message + +#### E-UTRAN Measurement Parameters Description + +**Qsearch\_C\_E-UTRAN** (4 bit field) +**E-UTRAN\_REP\_QUANT** (1 bit field) +**E-UTRAN\_MULTIRAT\_REPORTING** (2 bit field) +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD** (3 bit field) +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD\_2** (6 bit field) +**E-UTRAN\_FDD\_MEASUREMENT\_REPORT\_OFFSET** (6 bit field) +**E-UTRAN\_FDD\_REPORTING\_OFFSET** (3 bit field) +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD** (3 bit field) +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD\_2** (6 bit field) +**E-UTRAN\_TDD\_MEASUREMENT\_REPORT\_OFFSET** (6 bit field) +**E-UTRAN\_TDD\_REPORTING\_OFFSET** (3 bit field) +**REPORTING\_GRANULARITY** (1 bit field) + +These fields control the measurement and reporting of E-UTRAN cells, as defined in 3GPP TS 45.008. + +If both TDD and FDD frequencies are provided in the Repeated E-UTRAN Neighbour Cells IE and the E-UTRAN reporting thresholds are present for only one mode (i.e. TDD or FDD), then the parameter values for both modes shall be interpreted as having the same values. + +Any parameter present overwrites any old data held by the mobile station for these parameters. + +##### Repeated E-UTRAN Neighbour Cells + +If E-UTRAN cells or frequencies are included in the neighbour cell list, this information element shall be included in the message unless conditions for sending the *E-UTRAN NC with extended EARFCNs Description* information element are met (see below). + +**EARFCN** (16 bit field) + +This field specifies the E-UTRA Absolute Radio Frequency Channel Number as defined in 3GPP TS 36.104. + +**Measurement Bandwidth** (3 bit field) + +This field specifies the minimum value of the channel bandwidth of all valid E-UTRAN cells on the specified EARFCN. It is defined by the parameter Transmission Bandwidth Configuration, $N_{RB}$ (see 3GPP TS 36.104). The values indicate the number of resource blocks over which the mobile station could measure if the mobile station does not support wideband RSRQ measurements (see 3GPP TS 24.008). A mobile station supporting wideband RSRQ measurements shall measure over the indicated number of resource blocks. The field is coded according to the following table: + +| bit | | | | +|------------|---|---|-----------------------------------------------------------------------------------------------| +| 3 | 2 | 1 | | +| 0 | 0 | 0 | $N_{RB} = 6$ | +| 0 | 0 | 1 | $N_{RB} = 15$ | +| 0 | 1 | 0 | $N_{RB} = 25$ | +| 0 | 1 | 1 | $N_{RB} = 50$ | +| 1 | 0 | 0 | $N_{RB} = 75$ | +| 1 | 0 | 1 | $N_{RB} = 100$ | +| All others | | | Reserved for future use. If received by the mobile station, it shall be interpreted as '101'. | + +When missing, this indicates $N_{RB} = 6$ . + +This parameter applies to each E-UTRAN frequency listed within this structure. + +##### Repeated E-UTRAN Not Allowed Cells struct + +This structure identifies Not Allowed Cells with zero or more corresponding E-UTRAN frequency indices. If no E-UTRAN\_FREQUENCY\_INDEX is present, the **Not Allowed Cells** IE is applicable to all E-UTRAN frequencies specified in the Repeated E-UTRAN Neighbour Cells struct(s). + +This field is defined as described for the "Repeated E-UTRAN Measurement Control Parameters" information element.. + +##### Not Allowed Cells + +This information element identifies a group of one or more E-UTRAN cells by means of their physical layer cell identities (see 3GPP TS 36.211). The mobile station shall not perform measurements or attempt reselection to these cells. This information element is defined as the PCID Group IE described in 3GPP TS 44.060. + +#### E-UTRAN Measurement Control Parameters Description + +If this IE is present it overrides any old data held by the mobile station for these parameters. + +If the E-UTRAN Neighbour Cell Description IE is included in the message, the contents of this IE shall be ignored. + +##### DEFAULT\_Measurement\_Control\_E-UTRAN (1 bit field) + +This field is used to control whether measurements are made on E-UTRAN neighbour cells. The definition of this field is same as the definition of Measurement\_Control\_E-UTRAN as defined in 3GPP TS 45.008. Any E-UTRAN frequency not explicitly listed in Repeated E-UTRAN Measurement Control Parameters structure shall be assigned this value. + +##### Repeated E-UTRAN Measurement Control Parameters + +##### E-UTRAN\_FREQUENCY\_INDEX (3 bit field) + +This field is an index into the E-UTRAN Neighbour Cell list of the E-UTRAN frequency. A value of 0 refers to the first E-UTRAN frequency defined in the list. A value of 1 refers to the second defined frequency and so on. + +##### Measurement\_Control\_E-UTRAN (1 bit field) + +This field is used to control whether measurements are made on E-UTRAN neighbour cells for the E-UTRAN frequency referenced by E-UTRAN\_FREQUENCY\_INDEX, as defined in 3GPP TS 45.008. This parameter applies to each E-UTRAN frequency indexed within this structure. + +#### CSG\_PCI\_SPLIT + +This information element identifies one or more E-UTRAN physical layer cell identities (see 3GPP TS 36.211) as being reserved for CSG cells. The range of reserved physical layer cell identities applies to all E-UTRAN frequencies specified in the list of frequencies. + +This information element is defined as the PCID Group IE described in 3GPP TS 44.060. + +#### 3G CSG Description + +This information element is described in sub-clause 10.5.2.33b. + +#### UTRAN CSG Cells Reporting Description + +This information element signals the parameters for measurement and reporting of UTRAN CSG cells in dedicated mode or dual transfer mode. Any parameter present overwrites any old data held by the mobile station for this parameter. + +##### UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD (3 bit field) + +##### UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD\_2 (6 bit field) + +##### UTRAN\_CSG\_TDD\_REPORTING\_THRESHOLD (3 bit field) + +These fields are used to control the reporting of CSG cells as specified in 3GPP TS 45.008. + +#### E-UTRAN NC with extended EARFCNs Description + +This information element shall be included in the message if both the network and the mobile station support extended EARFCNs (see 3GPP TS 24.008). + +##### Repeated E-UTRAN NC with extended EARFCNs + +##### EARFCN\_extended (18 bit field) + +This field specifies the E-UTRA Absolute Radio Frequency Channel Number as defined in 3GPP TS 36.104. For an E-UTRA frequency for which the corresponding EARFCN has a value below 65535, the two most significant bits (bit 17 and 18) shall be set to 0. + +#### Measurement Bandwidth (3 bit field) + +See *Repeated E-UTRAN Neighbour Cell* information element. + +### 9.1.55 ENHANCED MEASUREMENT REPORT + +This message containing measurement results is sent on the SACCH by the mobile to the network. See figure 9.1.55.1. + +This message may contain reports on GSM and/or on other Radio Access Technologies. Measurements are defined in 3GPP TS 45.008. + +Message type: ENHANCED MEASUREMENT REPORT + +Significance: dual + +Direction: mobile station to network + +``` + + ::= + < RR short PD : bit > -- See 3GPP TS 24.007 + < Message type : bit (5) > -- See 10.4 + < Short layer 2 header : bit (2) > -- See 3GPP TS 44.006 + < BA_USED : bit > + < 3G_BA_USED : bit > + < BSIC_Seen : bit > + < SCALE : bit > + { 0 | 1 < Serving cell data : < Serving cell data struct >> } + { 1 < Repeated Invalid_BSIC_Information : < Repeated Invalid_BSIC_Information struct >> } ** 0 + { 0 | 1 { 0 | 1 < REPORTING_QUANTITY : bit (6) > } ** } -- bitmap type reporting + { null | L bit ** = < no string > -- Receiver compatible with earlier release + | H -- Additions in Rel-8 : + < BITMAP_LENGTH : bit(7) > + { 0 | 1 < REPORTING_QUANTITY : bit (6) > } * (val(BITMAP_LENGTH + 1) ) + { 0 | 1 < E-UTRAN Measurement Report : < E-UTRAN Measurement Report struct > > } + { null | L bit ** = < no string > -- Receiver compatible with earlier release + | H -- Additions in Rel-9 : + { 0 | 1 < UTRAN CSG Measurement Report : < UTRAN CSG Measurement Report IE > > } + { null | L bit ** = < no string > -- Receiver compatible with earlier release + | H -- Additions in Rel-11 : + < SI23_BA_USED : bit > + } } } + < spare padding > ; + +< Serving cell data struct > ::= + < DTX_USED : bit > + < RXLEV_VAL : bit (6) > + < RX_QUAL_FULL : bit (3) > + < MEAN_BEP : bit (5) > + < CV_BEP : bit (3) > + < NBR_RCVD_BLOCKS : bit (5) > ; + +< Repeated Invalid_BSIC_Information struct > ::= + < BCCH-FREQ-NCELL : bit (5) > + < BSIC : bit (6) > + < RXLEV-NCELL : bit (6) > ; + +< E-UTRAN Measurement Report struct > ::= + < N_E-UTRAN : bit (2) > + { + < E-UTRAN_FREQUENCY_INDEX : bit (3) > + < CELL IDENTITY : bit (9) > + < REPORTING_QUANTITY : bit (6) > } * (val(N_E-UTRAN + 1) ) ; + +``` + +**Figure 9.1.55.1: Enhanced Measurement Report message content** + +**Table 9.1.55.1: Enhanced Measurement Report information element details.** + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|--|----------|----------------------------------------------------------------|----------|-------------------------------------------------------------------------| +| BA_USED (1 bit field),
The value of the BA-IND field of the neighbour cell description information element or elements defining the BCCH allocation used. Range 0 to 1. | | | | | | | +| 3G_BA_USED (1 bit field)
The value of the 3G-BA-IND field of the neighbour cell description information element or elements defining the 3G and/or E-UTRAN allocation used. Range 0 to 1.. | | | | | | | +| BSIC_Seen (1 bit field)
This parameter indicates if a GSM cell with invalid BSIC and allowed NCC part of BSIC is one of the six strongest, see 3GPP TS 45.008. | | | | | | | +|
Bit
0 No cell with invalid BSIC and allowed NCC part of BSIC is seen
1 One Cell or more with invalid BSIC and allowed NCC part of BSIC is seen
| Bit | | 0 | No cell with invalid BSIC and allowed NCC part of BSIC is seen | 1 | One Cell or more with invalid BSIC and allowed NCC part of BSIC is seen | +| Bit | | | | | | | +| 0 | No cell with invalid BSIC and allowed NCC part of BSIC is seen | | | | | | +| 1 | One Cell or more with invalid BSIC and allowed NCC part of BSIC is seen | | | | | | + +#### **SCALE (1 bit field)** + +The value of this field is defined in 3GPP TS 45.008. + +##### **Serving cell reporting** + +If this structure is missing, this indicates that no valid measurement exist for the serving cell. + +Parameters **RXLEV\_VAL (6 bits)**, **RX\_QUAL\_FULL (3 bits)**, **MEAN\_BEP (5 bits)**, **CV\_BEP (3 bits)**, **NBR\_RCVD\_BLOCKS (5 bits)** are defined in 3GPP TS 45.008. + +#### **DTX\_USED (1 bit field)** + +This bit indicates whether or not the mobile station used DTX during the previous measurement period. + +- 0 DTX was not used +- 1 DTX was used. + +#### **Neighbour cell reporting** + +#### ***Repeated Invalid BSIC*** + +This structure contains the report of cells with invalid BSIC. + +**BCCH-FREQ-NCELL (5 bits)**. This field represents the index of the BA (list), see 10.5.2.20. + +**BSIC (6 bits)**. Base station identity code of the corresponding index in the BA (list). + +**RXLEV (6 bits)**. GSM reporting quantity, see 3GPP TS 45.008. + +#### ***Bitmap type reporting:*** + +This structure contains the report of cells with valid BSIC. + +Each bit of the bitmap points to the corresponding index of the Neighbour Cell list defined in sub-clause 3.4.1.2.1.3 'Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list'. + +If this structure is present and more bits than needed are available at the end of the message, the MS shall set the value of the redundant bitmap positions to '0'. + +At least 96 neighbour cell entries shall be encoded in the bitmap. + +If this structure is present, some remaining bits indicating no report at the end of the message may be omitted if these bits do not fit into the message. This shall not lead to an error in the receiver of that message. + +If E-UTRAN neighbour cells are to be reported, then this structure shall be omitted and replaced by the bitmap reporting structure in the release-8 extension of this message. + +#### **REPORTING\_QUANTITY (6 bits):** + +Measurement quantities are defined in 3GPP TS 45.008. + +#### **E-UTRAN Neighbour cell reporting** + +#### **BITMAP\_LENGTH (7 bit field)** + +1+val(BITMAP\_LENGTH) indicates the number of entries in the reporting bitmap. + +#### ***Bitmap type reporting:*** + +This structure contains the report of cells with valid BSIC. + +Each bit of the bitmap points to the corresponding index of the Neighbour Cell list defined in sub-clause 5.6.3.3 ("Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list"). + +#### **REPORTING\_QUANTITY (6 bits):** + +Measurement quantities are defined in 3GPP TS 45.008. + +#### **E-UTRAN Measurements** + +Measurement reporting for E-UTRAN Cells is defined in 3GPP TS 45.008. + +#### **E-UTRAN\_FREQUENCY\_INDEX** (3 bit field) + +This field contains the index of the frequency of the cell for which the measurement is reported. This field is defined in sub-clause 9.1.54. + +#### **CELL\_IDENTITY** (9 bit field) + +This field contains the physical layer cell identity (as defined in 3GPP TS 36.211) of the cell being reported. + +#### **REPORTING\_QUANTITY** (6 bit field) + +This is the reporting quantity for the E-UTRAN cell identified by the E-UTRAN frequency and physical layer cell identity. The quantities are defined in 3GPP TS 45.008 for the respective Radio Access Technology. + +#### **UTRAN CSG Measurement Report** + +This information element contains the measurement report for a UTRAN CSG cell or detected hybrid cell. A UTRAN CSG cell or detected hybrid cell is identified by the Cell Identity and optionally the PLMN-ID. + +This information element is defined as the *UTRAN CSG Measurement Report* IE described in 3GPP TS 44.060. + +#### **SI23\_BA\_USED** (1 bit field) + +This field contains the value of the SI 23\_BA\_IND field in SYSTEM INFORMATION TYPE 23 message defining the E-UTRAN allocation used. In the case SYSTEM INFORMATION TYPE 23 message is not broadcast in the cell or if the mobile station does not support network sharing, this field shall be set to 0. Range 0 to 1 + +### 9.1.56 Service Information message + +This message is sent on the main DCCH by an MBMS capable mobile station, in class A mode of operation, to the network to indicate support of MBMS and additionally indicating whether the mobile station has joined an MBMS service. See table 9.1.56.1. + +Message type: SERVICE INFORMATION + +Significance: dual + +Direction: mobile station to network + +**Table 9.1.56.1: Service Information message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-----------------------------------------|-------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | Service Information Message
Type | Message Type
10.4 | M | V | 1 | +| | Temporary Logical Link Identity | TLLI
10.5.2.41a | M | V | 4 | +| | Routeing Area Identification | Routeing Area Identification
10.5.5.15 | M | V | 6 | +| | Service Support | Service Support
10.5.2.57 | M | V | 1 | + +#### 9.1.56.1 Temporary Logical Link Identity + +This information element contains the TLLI derived from the P-TMSI, see 3GPP TS 23.060. The network shall accept a local TLLI even if the current RA where the message is received differs from the one indicated in this message. + +#### 9.1.56.2 Routeing Area Identification + +This information element shall contain the stored routeing area identification (e.g. received in the last attach or routeing area update procedure, see 3GPP TS 24.008). + +### 9.1.57 VGCS Neighbour Cell Information message + +The understanding of this message is only required for mobile stations supporting VGCS listening or VBS listening. + +This message is sent on the main DCCH, in unacknowledged mode using the RR short protocol discriminator by the network to notify the mobile stations in on-going voice group calls of a change in the validity of information previously sent in System Information Type 10bis messages and/or System Information Type 10ter messages, which specify parameters for voice group calls in neighbouring cells. + +Mobile stations not supporting VGCS listening or VBS listening shall ignore this message. + +See table 9.1.57.1. + +Message type: VGCS Neighbour Cell Information + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.57.1: VGCS Neighbour Cell Information message content** + +``` + + ::= + -- See 3GPP TS 24.007 + -- See 10.4 + -- See 3GPP TS 44.006 + < SI10bis Sequence : bit (2) > -- new sequence number i + { 0 + { 0 | 1 BSIC : bit (6) } + < Validity Information > } ** 1 + { 0 < SI10bis Neighbour Cell Info > } ** 1 + ; + +< Validity Information > ::= + { 0 -- information for this cell with sequence number i-1 is still valid + | 1 < Validity bitmap : bit (3) > } + +Validity bitmap: +bit 0: +1 SI10bis information with sequence number i-1 is invalid +0 SI10bis information with sequence number i-1 is valid + +bit 1: +1 SI10ter information with sequence number i-1 is invalid +0 SI10ter information with sequence number i-1 is valid + +bit 2: +1 Group call is no longer active in neighbour cell +0 Group call is still active in neighbour cell + +``` + +Validity Information is included for each neighbour cell, in order of increasing BCCH ARFCN (i.e. in the same order as used in SI10 Rest Octets, see sub-clause 10.5.2.44). If two or more neighbour cells have the same BCCH ARFCN then the BSIC shall be included to distinguish the cells. + +If the group channel (either before or after a change) in a neighbouring cell is non-hopping, then bit 1 of the Validity bitmap shall be set to 1. + +SI10bis Neighbour Cell Info is included for as many cells as possible for which bit 0 of the Validity bitmap is equal to 1 and bit 2 of the Validity bitmap is equal to 0, in the order in which the corresponding cells' Validity Information was included. + +If a mobile station receives a message including a Validity bitmap in which all 3 bits are set to 0, the mobile station shall diagnose an imperative message part error. + +### 9.1.58 NOTIFY APPLICATION DATA + +This message is sent on the main DCCH of the voice group channel in unacknowledged mode and (if applicable in the cell) on the main DCCH of the talker channel) using the RR short protocol discriminator by the network to broadcast + +the application data to mobile stations in group receive mode and group transmit mode and to VGCS talkers in dedicated mode. + +Mobile stations not supporting VBS or VGCS shall ignore this message. + +See Figure 9.1.58.1 and Table 9.1.58.1. + +Message type: NOTIFY APPLICATION DATA + +Significance: dual + +Direction: network to mobile station + +``` + := -- See 3GPP TS 24.007 + -- See sub-clause 10.4 + -- See 3GPP TS 44.006 + + + { 0 | 1 + + } + ; +``` + +**Figure 9.1.58.1: Notify Application Data message content** + +**Table 9.1.58.1 Notify Application Data message content details** + +#### **MSISDN length (4 bit field)** + +This field contains the length of the MSISDN field in octets + +#### **MSISDN** + +This field contains the value part of the MSISDN IE contained in the NOTIFICATION DATA message (see 3GPP TS 48.008), if present. + +#### **application data (72 bit field)** + +This field contains the value part of the Application Data IE contained in the NOTIFICATION DATA message (see 3GPP TS 48.008) + +#### **data identity (8 bit field)** + +This field contains the value part of the Data Identity IE contained in the NOTIFICATION DATA message (see 3GPP TS 48.008) + +### 9.1.59 EC IMMEDIATE ASSIGNMENT TYPE 1 + +This message is sent on the CCCH by the network to assign uplink packet resources to a mobile station that has enabled EC operation and attempts system access using the RACH. When sending this message the network assigns pre-allocated uplink resources to the mobile station (see sub-clause 3.5.2.1.3.1). + +The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the *L2 Pseudo Length* information elements. + +Message type: EC IMMEDIATE ASSIGNMENT TYPE 1 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.59.1: EC IMMEDIATE ASSIGNMENT TYPE 1 information elements** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|---------------------------------------------|---------------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
10.5.2.19 | M | V | 1 | +| | RR management Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | EC Immediate Assignment Type 1 Message Type | Message Type
10.4 | M | V | 1 | +| | Page Mode | Page Mode
10.5.2.26 | M | V | 1/2 | +| | Feature Indicator | Feature Indicator
10.5.2.76 | M | V | 1/2 | +| | Request Reference | Request Reference
10.5.2.30 | M | V | 3 | +| | EC Packet Channel Description Type 1 | EC Packet Channel Description Type 1
10.5.2.84 | M | V | 2 | +| | EC Fixed Uplink Allocation | EC Fixed Uplink Allocation
10.5.2.86 | M | V | 4 - 14 | + +#### 9.1.59.0 Request Reference + +When included in the EC IMMEDIATE ASSIGNMENT TYPE 1 message the content of Request Reference IE reflects the TDMA frame used to send the EC PACKET CHANNEL REQUEST message on the RACH and the random bits included within the EC PACKET CHANNEL REQUEST message (see sub-clause 9.1.65). + +#### 9.1.59.1 EC Packet Channel Description Type 1 + +The *EC Packet Channel Description Type 1* IE identifies the radio parameters applicable to an uplink EC TBF for a mobile station that has enabled EC operation and is attempting system access using the RACH (i.e. Coverage Class 1 has been selected by the mobile station for both the uplink and the downlink). + +#### 9.1.59.2 EC Fixed Uplink Allocation + +The *EC Fixed Uplink Allocation* IE identifies the parameters required for uplink packet data transfer when EC operation is enabled (see sub-clause 10.5.2.86). + +### 9.1.60 EC IMMEDIATE ASSIGNMENT TYPE 2 + +This message is sent on the EC-CCCH by the network to assign uplink packet resources to a mobile station that has enabled EC operation and attempts system access using the 1TS EC-RACH Mapping method or the 2TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a). When sending this message the network assigns pre-allocated uplink resources to the mobile station (see sub-clause 3.5.2.1.3a). + +Message type: EC IMMEDIATE ASSIGNMENT TYPE 2 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.60.1: EC IMMEDIATE ASSIGNMENT TYPE 2 message content** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < EC Immediate Assignment Type 2 message content > ::=   < Message Type : bit (4) >   < Used DL Coverage Class : bit (2) >   { 0   1 < EC Page Extension : bit (4) > }   < EC Request Reference : bit (13) >   < EC Packet Channel Description Type 2 : bit (15) >   < EC Fixed Uplink Allocation : < EC Fixed Uplink Allocation struct >>   < spare padding > ;
| +| 
 < EC Fixed Uplink Allocation struct > ::=   < Enhanced Access Burst : bit (1) >   { 0   1 < Timing Advance : bit (6) > }   < STARTING_UL_TIMESLOT : bit (3) >   < Uplink_TFI_Assignment : bit (5) >   < STARTING_DL_TIMESLOT_OFFSET : bit (2) >   < OVERLAID_CDMA_CODE : bit (2) >   { 0     – use MCS-1 for uplink packet transfer     1 < Assigned MCS : bit (4) > }   < GAMMA : bit (5) >   < ALPHA Enable : bit (1) >   { 0   1 < P0 : bit (4) >     < PR_MODE : bit (1) > }   < Start_First_UL_Data_Block : bit (4) >   { 1 { 0 < Start_FN_Next_Data_Block : bit (3) >       1     – no gap between last block and next block } } ** 0 ;
| + +**Table 9.1.60.2: EC IMMEDIATE ASSIGNMENT TYPE 2 message details** + +| | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------|---------|------------------------------------------------------------------------------|---------|------------------------------------------------------------------------------|---------|------------------------------------------------------------------------------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| | | | | | | | | +|

Used DL Coverage Class (2 bit field)

Control messages on the EC-AGCH or EC-PCH are sent using blind physical layer transmissions, depending on the assigned downlink coverage class for the mobile station that the message is being sent to. The Used DL Coverage Class field is included in order to inform other mobile stations about the downlink coverage class, and thus the number of blind physical layer transmissions, that have been used to transmit the current control message. Mobile stations that have selected a lower downlink coverage class than what is indicated by this field can, upon successfully reading the control message, can avoid monitoring any remaining blind physical layer transmissions used to send the control message. This field is coded as follows:

bit
2 1

0 0 DL CC 1
0 1 DL CC 2
1 0 DL CC 3
1 1 DL CC 4
| 0 0 | DL CC 1 | 0 1 | DL CC 2 | 1 0 | DL CC 3 | 1 1 | DL CC 4 | +| 0 0 | DL CC 1 | | | | | | | | +| 0 1 | DL CC 2 | | | | | | | | +| 1 0 | DL CC 3 | | | | | | | | +| 1 1 | DL CC 4 | | | | | | | | +|

EC Page Extension (4 bit field)

This field indicates whether an EC capable mobile station of a specific coverage class should attempt one additional instance of page reading on the EC-PCH (see sub-clause 3.5.1a) when it successfully reads a message when waking up according to its nominal paging group but does not receive a matching page. This field is coded as follows:

bit
4 3 2 1

1 X X X mobile stations using downlink CC1 shall attempt one additional page reading
X 1 X X mobile stations using downlink CC2 shall attempt one additional page reading
X X 1 X mobile stations using downlink CC3 shall attempt one additional page reading
X X X 1 mobile stations using downlink CC4 shall attempt one additional page reading
| 1 X X X | mobile stations using downlink CC1 shall attempt one additional page reading | X 1 X X | mobile stations using downlink CC2 shall attempt one additional page reading | X X 1 X | mobile stations using downlink CC3 shall attempt one additional page reading | X X X 1 | mobile stations using downlink CC4 shall attempt one additional page reading | +| 1 X X X | mobile stations using downlink CC1 shall attempt one additional page reading | | | | | | | | +| X 1 X X | mobile stations using downlink CC2 shall attempt one additional page reading | | | | | | | | +| X X 1 X | mobile stations using downlink CC3 shall attempt one additional page reading | | | | | | | | +| X X X 1 | mobile stations using downlink CC4 shall attempt one additional page reading | | | | | | | | +|

EC Request Reference (13 bit field)

This field is coded as described in sub-clause 10.5.2.83

| | | | | | | | | +|

EC Packet Channel Description Type 2 (15 bit field)

This information element is coded as described in sub-clause 10.5.2.85

| | | | | | | | | +|

Enhanced Access Burst (1 bit field)

This field indicates whether or not the mobile station shall use the Enhanced Access Burst procedure for contention resolution (see 3GPP TS 44.060) on the assigned EC TBF. This field is coded as follows:

Bit

0 The Enhanced Access Burst procedure shall not be used
1 The Enhanced Access Burst procedure shall be used
| 0 | The Enhanced Access Burst procedure shall not be used | 1 | The Enhanced Access Burst procedure shall be used | | | | | +| 0 | The Enhanced Access Burst procedure shall not be used | | | | | | | | +| 1 | The Enhanced Access Burst procedure shall be used | | | | | | | | + +#### **Timing Advance** (6 bit field) + +This field provides the timing advance value and is coded as per the value part of the Timing Advance IE described in sub-clause 10.5.2.40, with the value range limited to 0 to 63. If this field is not included the mobile station shall use a default value of 0 (i.e. no timing advance). + +#### **STARTING\_UL\_TIMESLOT** (3 bit field) + +This field indicates the first assigned timeslot within the set of assigned uplink timeslots.: + +Bit + +**3 2 1** + +0 0 0 Timeslot 0 is the first assigned uplink timeslot + +0 0 1 Timeslot 1 is the first assigned uplink timeslot + +0 1 0 Timeslot 2 is the first assigned uplink timeslot + +0 1 1 Timeslot 3 is the first assigned uplink timeslot + +1 0 0 Timeslot 4 is the first assigned uplink timeslot + +1 0 1 Timeslot 5 is the first assigned uplink timeslot + +1 1 0 Timeslot 6 is the first assigned uplink timeslot + +1 1 1 Timeslot 7 is the first assigned uplink timeslot + +If the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q): a mobile station assigned CC2, CC3 or CC4 on the uplink is always assigned the use of 4 consecutive timeslots and therefore only timeslot 0, 1, 2, 3 or 4 shall be indicated as the first assigned uplink timeslot. + +If the field EC\_Reduced\_PDCH\_Allocation is set to 1 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q): A mobile station assigned CC2, CC3 or CC4 on the uplink is always assigned the use of 2 consecutive timeslots and therefore only timeslot 0, 1, 2, 3, 4, 5 or 6 shall be indicated as the first assigned uplink timeslot. + +#### **Uplink\_TFI\_Assignment** (5 bit field) + +This field is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31. + +#### STARTING\_DL\_TIMESLOT\_OFFSET (2 bit field) + +This field defines the timeslot number of the lowest timeslot included in the assignment that is used for transfer of downlink RLC/MAC control messages on the EC-PACCH during the UL EC TBF. The number of additional timeslots that are included in the downlink assignment depends on the assigned DL Coverage Class. The assigned timeslots are contiguous, starting with the timeslot number indicated in the STARTING\_DL\_TIMESLOT\_OFFSET field. The STARTING\_DL\_TIMESLOT\_OFFSET field is encoded as an offset to the timeslot assigned with the STARTING\_UL\_TIMESLOT field. The encoding of the field is dependent of the value of the UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS fields in the same message. + +If both UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS > CC1, the same timeslots are assigned in both the uplink and the downlink directions. The STARTING\_DL\_TIMESLOT\_OFFSET field can then be considered as not valid by the mobile station. + +If UL\_COVERAGE\_CLASS = CC1 and DL\_COVERAGE\_CLASS > CC1, the STARTING\_DL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | +|-----|----------------------------------------------------| +| bit | | +| 2 | 1 | +| 0 0 | Same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT - 1 | +| 1 0 | STARTING_UL_TIMESLOT - 2 | +| 1 1 | STARTING_UL_TIMESLOT - 3 | + +If UL\_COVERAGE\_CLASS > CC1 and DL\_COVERAGE\_CLASS = CC1, the STARTING\_DL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | +|-----|----------------------------------------------------| +| bit | | +| 2 | 1 | +| 0 0 | Same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT + 1 | +| 1 0 | STARTING_UL_TIMESLOT + 2 | +| 1 1 | STARTING_UL_TIMESLOT + 3 | + +If both UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS = CC1, the downlink is assigned to the timeslot indicated by the STARTING\_UL\_TIMESLOT field. If timer T3248 (sent in EC SI) is used, the STARTING\_DL\_TIMESLOT\_OFFSET field defines the lowest assigned timeslot for EC-PACCH transfers using CC2 while timer T3248 is running (see 3GPP TS 44.060). The STARTING\_DL\_TIMESLOT\_OFFSET field is then encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | +|-----|---------------------------------------------------------------------| +| bit | | +| 2 | 1 | +| 0 0 | Same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT - 1 | +| 1 0 | STARTING_UL_TIMESLOT - 2 | +| 1 1 | No valid CC2 mapping applies while T3248 is running, CC1 to be used | + +If the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q), a mobile station using CC2, CC3 or CC4 on the downlink is always assigned the use of 4 consecutive timeslots. If the field EC\_Reduced\_PDCH\_Allocation is set to 1 in the EC SYSTEM INFORMATION TYPE 2 message (sub-clause 9.1.43q), a mobile station using CC2, CC3 or CC4 on the downlink is always assigned the use of 2 consecutive timeslots. + +#### **OVERLAID\_CDMA\_CODE** (2 bit field) + +This field indicates the type overload CDMA code to be used for an uplink TBF (see 3GPP TS 45.002 [32]). This field is coded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +bit + +2 1 + +0 0 Overlaid CDMA Code 0 + +0 1 Overlaid CDMA Code 1 + +1 0 Overlaid CDMA Code 2 + +1 1 Overlaid CDMA Code 3 + +Note: Overlaid CDMA Code 0 corresponds to that the bursts are transmitted as if no code was applied. + +#### **Assigned MCS** (4 bit field) + +This field is coded as per EGPRS Modulation and Coding Scheme IE described in 3GPP TS 44.060. + +#### **GAMMA** (5 bit field) + +This field is the binary representation of the parameter $\Gamma$ CH for MS output power control in units of 2 dB, see 3GPP TS 45.008. + +#### **ALPHA Enable** (1 bit field) + +This field indicates whether or not the mobile station shall use the ALPHA parameter (if sent as part of EC SI) for uplink power control (see 3GPP TS 45.008 [34]). This field is coded as follows: + +0 Do not use the ALPHA parameter + +1 Use the ALPHA parameter + +#### **P0** (4 bit field) + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +#### **PR\_MODE** (1 bit field) + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +#### **Start\_First\_UL\_Data\_Block** (4 bit field) + +This field identifies the uplink transmission opportunity corresponding to the assigned uplink coverage class (see the *EC Packet Channel Description Type 2* IE described in sub-clause 10.5.2.85) that the mobile station is to use to start sending its first uplink RLC data block on the set of assigned uplink timeslots. The 1st transmission opportunity occurs no earlier than in TDMA frame N+10 where TDMA frame N is the last TDMA frame used for transmission of the EC IMMEDIATE ASSIGNMENT TYPE 1 or EC IMMEDIATE ASSIGNMENT TYPE 2 message. See 3GPP TS 45.010 [35] for mobile station reaction time requirements applicable to receiving an assignment message. This field is coded as follows: + +Bit + +**4 3 2 1** + +0 0 0 0 Use the 1st transmission opportunity + +0 0 0 1 Use the 2nd transmission opportunity + +0 0 1 0 Use the 3rd transmission opportunity + +. + +. + +. + +1 1 1 1 Use the 16th transmission opportunity + +For CC1 the Kth transmission opportunity = the Kth BTTI radio block on the assigned timeslot occurring after TDMA frame N+9. The Kth BTTI radio block occurs in one of {B0, B1, ...B11} (see 3GPP TS 45.002 [32]), whichever occurs first after TDMA frame N+9. + +For CC2 the Kth transmission opportunity = the Kth set of 4 BTTI radio blocks on the assigned timeslots occurring after TDMA frame N+9. The Kth set of 4 BTTI radio blocks occurs in one of {B0, B1, ...B11}, if the field *EC\_Reduced\_PDCH\_Allocation* is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q), whichever occurs first after TDMA frame N+9. The Kth set of 4 BTTI radio blocks occurs in one of {B0, B1, ...B5} (see 3GPP TS 45.003[86]), if the field *EC\_Reduced\_PDCH\_Allocation* is set to 1, whichever occurs first after TDMA frame N+9. + +For CC3 the Kth transmission opportunity = the Kth set of 8 BTTI radio blocks on the assigned timeslots occurring after TDMA frame N+9. The Kth set of 8 BTTI radio blocks occurs in one of {[B0, B1], [B2, B3], ...[B10, B11]}, if the field *EC\_Reduced\_PDCH\_Allocation* is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q), whichever occurs first after TDMA frame N+9. The Kth set of 8 BTTI radio blocks occurs in one of {B0, B1, B2} see 3GPP TS 45.003[86]), if the field *EC\_Reduced\_PDCH\_Allocation* is set to 1, whichever occurs first after TDMA frame N+9. + +For CC4 the Kth transmission opportunity = the Kth set of 16 BTTI radio blocks on the assigned timeslots occurring after TDMA frame N+9. The Kth set of 16 BTTI radio blocks occurs in one of {[B0, B1, B2, B3], [B4, B5, B6, B7], [B8, B9, B10, B11]}, if the field *EC\_Reduced\_PDCH\_Allocation* is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q), whichever occurs first after TDMA frame N+9. The Kth set of 16 BTTI radio blocks occurs in one of {B0, B1, B2} see 3GPP TS 45.003[86]), if the field *EC\_Reduced\_PDCH\_Allocation* is set to 1, whichever occurs first after TDMA frame N+9. + +#### **Start\_FN\_Next\_Data\_Block (3 bit field)** + +This field identifies the gap (in coverage class specific transmission opportunities) between the last pre-allocated uplink radio block transmitted on assigned uplink timeslots and the next pre-allocated uplink radio block to be used for the uplink transmission. This field is coded as follows: + +Bit + +**3 2 1** + +0 0 0 a gap of 1 transmission opportunity + 0 0 1 a gap of 2 transmission opportunities + 0 1 0 a gap of 3 transmission opportunities + +. + +. + +. + +1 1 1 a gap of 8 transmission opportunities + +For CC1 a gap of K transmission opportunities = K BTTI radio blocks on the assigned timeslot occurring immediately after the last BTTI radio block used for the uplink transmission. Any BTTI radio block in the set of {B0, B1, ...B11} counts as a gap of one CC1 transmission opportunity (see 3GPP TS 45.002 [32]). + +For CC2 a gap of K transmission opportunities = K sets of 4 BTTI radio blocks on the assigned timeslots occurring immediately after the last set of 4 BTTI radio blocks used for the uplink transmission. Each set of 4 BTTI radio blocks occurring in one of {B0, B1, ...B11} counts as a gap of one CC2 transmission opportunity, if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). Else if the field EC\_Reduced\_PDCH\_Allocation is set to 1, each set of 4 BTTI radio blocks occurring in one of {B0, B1, ...B5} (see 3GPP TS 45.003[86]) counts as a gap of one CC2 transmission opportunity. + +For CC3 a gap of K transmission opportunities = K sets of 8 BTTI radio blocks on the assigned timeslots occurring immediately after the last set of 8 BTTI radio blocks used for the uplink transmission. Each set of 8 BTTI radio blocks occurring in one of {[B0, B1], [B2, B3], ...[B10, B11]} counts as a gap of one CC3 transmission opportunity, if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). Else if the field EC\_Reduced\_PDCH\_Allocation is set to 1, each set of 8 BTTI radio blocks occurring in one of {B0, B1, B2} (see 3GPP TS 45.003[86]) counts as a gap of one CC3 transmission opportunity. + +For CC4 a gap of K transmission opportunities = K sets of 16 BTTI radio blocks on the assigned timeslots occurring immediately after the last set of 16 BTTI radio blocks used for the uplink transmission. Each set of 16 BTTI radio blocks occurring in one of {[B0, B1, B2, B3], [B4, B5, B6, B7], [B8, B9, B10, B11]} counts as a gap of one CC4 transmission opportunity, if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). Else if the field EC\_Reduced\_PDCH\_Allocation is set to 1, each set of 16 BTTI radio blocks occurring in one of {B0, B1, B2} (see 3GPP TS 45.003[86]) counts as a gap of one CC4 transmission opportunity. + +### 9.1.61 EC Immediate Assignment Reject + +This message is sent on the EC-CCCH by the network to up to three mobile stations to indicate that no channel is available for assignment. See table 9.1.61.1. + +Message type: EC IMMEDIATE ASSIGNMENT REJECT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.61.1: EC IMMEDIATE ASSIGNMENT REJECT message content** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < EC Immediate Assignment Reject message content > ::=    < Message Type : bit (4) >   < Used DL Coverage Class: bit (2) >   { 0   1 < EC Page Extension ; bit (4) > }   < EC Request Reference 1 : bit (13) >   < EC Wait Timer 1 : bit (8) >   { 0   1 < EC Request Reference 2 : bit (13) >     < EC Wait Timer 2 : bit (8) > }   { 0   1 < EC Request Reference 3 : bit (13) >     < EC Wait Timer 3 : bit (8) > }   < spare padding > ;
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.1.61.2: EC IMMEDIATE ASSIGNMENT REJECT message details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| +|

Used DL Coverage Class (2 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

EC Page Extension (4 bit field)

This field is coded as described in sub-clause 9.1.60.

| + +**EC Request Reference 1** (13 bit field) +**EC Request Reference 2** (13 bit field) +**EC Request Reference 3** (13 bit field) + +This field is coded as described in sub-clause 10.5.2.83. When multiple instances of this field are included in the EC IMMEDIATE ASSIGNMENT REJECT message then each instance refers to a different mobile station for which the ongoing packet access procedure is to be aborted. + +**EC Wait Timer 1** (8 bit field) +**EC Wait Timer 2** (8 bit field) +**EC Wait Timer 3** (8 bit field) + +This field is coded as the binary representation of the T3142 timeout value in seconds. + +### 9.1.62 EC Dummy + +This message is sent on the EC-CCCH whenever there are no other messages to send. See table 9.1.62.1. + +Message type: EC DUMMY + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.62.1: EC DUMMY message content** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< EC-Dummy message content > ::=   < Message Type : bit (4) >   < Used DL Coverage Class: bit (2) >    < spare padding > ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.1.62.2: EC DUMMY message details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| +|

Used DL Coverage Class (2 bit field)

This field is coded as described in sub-clause 9.1.60

| + +### 9.1.63 EC PAGING REQUEST + +This message is sent on the EC-CCCH by the network and may identify up to two mobile stations. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure). The mobile stations are identified by their P-TMSI or IMSI. + +Message type: EC PAGING REQUEST + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.63.1: EC PAGING REQUEST message content** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< EC Paging Request message content > ::=   < Message Type : bit (4) >   < Used DL Coverage Class: bit (2) >   { 0   1 < EC Page Extension ; bit (4) > }   < Mobile Identity 1 : < Mobile Identity struct > >   { 0   1 < Mobile Identity 2 : < Mobile Identity struct > > }   {     null   L    -- Receiver compatible with earlier release     H           -- Additions in Release 14     < Positioning Event Pending Indicator : bit (2) >     < Enhanced Coverage Restriction Indicator : bit (2) >   }    < spare padding > ;
| +| 
< Mobile Identity struct > ::=   { 0 < P-TMSI : bit (32) >     1 < Number of IMSI Digits : bit (4) >     < IMSI Digits : bit (4 * (val(Number of IMSI Digits) + 1)) > } ;
| + +**Table 9.1.63.2: EC PAGING REQUEST message details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| +|

Used DL Coverage Class (2 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

EC Page Extension (4 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

P-TMSI field (32 bit field)

This field identifies the P-TMSI assigned to the mobile station using NAS signalling. It is coded as the value part of the TMSI/P-TMSI IE as described in sub-clause 10.5.2.42.

| +|

Number of IMSI Digits (4 bit field)

This field identifies the number of digits in the IMSI. This field is coded as follows:

Bit
4 3 2 1
0 0 0 0 1 digit
0 0 0 1 2 digits
0 0 1 0 3 digits
.
.
.
1 1 1 1 16 digits

| +|

IMSI Digits

This field is coded as a set of N digits where N = val(Number of IMSI Digits + 1) where the first instance of IMSI Digits corresponds to "Identity digit 1" of Figure 10.5.4/3GPP TS 24.008, the second instance of IMSI Digits corresponds to "Identity digit 2" of Figure 10.5.4/3GPP TS 24.008 and so on.

| + +#### **Positioning Event Pending Indicator (2 bit field)** + +This field is a 2 bit bitmap indicating whether or not a paging request is sent due to a pending positioning event for the MS identified by the Mobile Identity 1 and Mobile Identity 2 fields. + +Bit + +2 1 + +x 0 Page not sent for Mobile Identity 1 due to a pending positioning event + +x 1 Page sent for Mobile Identity 1 due to a pending positioning event + +0 x Page not sent for Mobile Identity 2 due to a pending positioning event + +1 x Page sent for Mobile Identity 2 due to a pending positioning event + +#### **Enhanced Coverage Restriction Indicator (2 bit field)** + +This field is a 2 bit bitmap indicating whether or not the use of enhanced coverage is restricted for the MS identified by the Mobile Identity 1 and Mobile Identity 2 fields. + +Bit + +2 1 + +x 0 Restricted use of enhanced coverage for Mobile Identity 1 + +x 1 No restriction on use of enhanced coverage for Mobile Identity 1 + +0 x Restricted use of enhanced coverage for Mobile Identity 2 + +1 x No restriction on use of enhanced coverage for Mobile Identity 2 + +### 9.1.64 EC DOWNLINK ASSIGNMENT + +This message is sent on the EC-CCCH by the network to assign downlink packet resources to a mobile station that has enabled EC operation. + +Message type: EC DOWNLINK ASSIGNMENT + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.64.1: EC DOWNLINK ASSIGNMENT message content** + +``` +< EC Downlink Assignment message content > ::= + < Message Type : bit (4) > + < Used DL Coverage Class: bit (2) > + { 0 | 1 < EC Page Extension : bit (4) > } + < TLLI : bit (32) > + < EC Packet Channel Description Type 2 : bit (15) > + < EC Downlink Allocation : < EC Downlink Allocation struct >> + -- Additions in release Rel-14: + < Multilateration Information Request : bit (1) > + ; + +< EC Downlink Allocation struct > ::= + < Timing Advance : bit (6) > + < STARTING_DL_TIMESLOT : bit (3) > + < Downlink_TFI_Assignment : bit (5) > + < TIMESLOT_MULTIPLICATOR : bit (2) > + < STARTING_UL_TIMESLOT_OFFSET (2) > + < GAMMA : bit (5) > + < ALPHA Enable : bit (1) > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } ; +``` + +**Table 9.1.64.2: EC DOWNLINK ASSIGNMENT message details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| +|

Used DL Coverage Class (2 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

EC Page Extension (4 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

TLLI (32 bit field)

This field is the binary representation of a TLLI. The coding of TLLI is left open for each administration using the structure specified in 3GPP TS 23.003.

| +|

EC Packet Channel Description Type 2 (15 bit field)

This information element is coded as described in sub-clause 10.5.2.85

| +|

Timing Advance (6 bit field)

This field is coded as described in sub-clause 9.1.60

| +|

STARTING_DL_TIMESLOT (3 bit field)

This field indicates the first assigned timeslot within the set of assigned downlink timeslots.:

Bit
3 2 1

0 0 0 Timeslot 0 is the first assigned downlink timeslot
0 0 1 Timeslot 1 is the first assigned downlink timeslot
0 1 0 Timeslot 2 is the first assigned downlink timeslot
0 1 1 Timeslot 3 is the first assigned downlink timeslot
1 0 0 Timeslot 4 is the first assigned downlink timeslot
1 0 1 Timeslot 5 is the first assigned downlink timeslot
1 1 0 Timeslot 6 is the first assigned downlink timeslot
1 1 1 Timeslot 7 is the first assigned downlink timeslot

If the field EC_Reduced_PDCH_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q): A mobile station using CC2, CC3 or CC4 on the downlink is always assigned 4 consecutive timeslots and therefore only timeslot 0, 1, 2, 3 or 4 shall be indicated as the first assigned downlink timeslot.

If the field EC_Reduced_PDCH_Allocation is set to 1 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q): A mobile station using CC2, CC3 or CC4 on the downlink is always assigned 2 consecutive timeslots and therefore only timeslot 0, 1, 2, 3, 4, 5 or 6 shall be indicated as the first assigned downlink timeslot.

| +|

Downlink_TFI_Assignment (5 bit field)

This field is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31.

| + +#### **TIMESLOT\_MULTIPLICATOR (2 bit field)** + +This field defines how many downlink timeslots the assignment contains when the assigned downlink Coverage Class is CC1. The field is coded as follows: + +| bit | | +|-----|----------------------| +| 2 | 1 | +| 0 0 | 1 timeslot assigned | +| 0 1 | 2 timeslots assigned | +| 1 0 | 3 timeslots assigned | +| 1 1 | 4 timeslots assigned | + +Values other than '00' can only be used if supported by the mobile station, as indicated by its multislot capability, see 3GPP TS 45.002 [32]. If the assigned downlink Coverage Class > CC1 (see the EC Packet Channel Description Type 2 field), the mobile station shall consider the TIMESLOT\_MULTIPLICATOR field as invalid. + +#### **STARTING\_UL\_TIMESLOT\_OFFSET (2 bit field)** + +This field defines the timeslot number of the lowest timeslot included in the assignment that is used for transfer of uplink RLC/MAC control messages on the EC-PACCH during the DL EC TBF. The number of additional timeslots that are included in the uplink assignment depends on the assigned UL Coverage Class. The assigned timeslots are contiguous, starting with the timeslot number indicated in the STARTING\_UL\_TIMESLOT\_OFFSET field. The STARTING\_UL\_TIMESLOT\_OFFSET field is encoded as an offset to the timeslot assigned with the STARTING\_DL\_TIMESLOT field. The encoding of the field is dependent of the value of the DL\_COVERAGE\_CLASS and UL\_COVERAGE\_CLASS fields in the same message. + +If both DL\_COVERAGE\_CLASS and UL\_COVERAGE\_CLASS > CC1, the same timeslots are assigned in both the uplink and the downlink directions. The STARTING\_UL\_TIMESLOT\_OFFSET field can then be considered as not valid by the mobile station. + +If DL\_COVERAGE\_CLASS = CC1 and UL\_COVERAGE\_CLASS > CC1, the STARTING\_UL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| bit | | +|-----|----------------------------------------------------| +| 2 | 1 | +| 0 0 | Same timeslot as indicated by STARTING_DL_TIMESLOT | +| 0 1 | STARTING_DL_TIMESLOT - 1 | +| 1 0 | STARTING_DL_TIMESLOT - 2 | +| 1 1 | STARTING_DL_TIMESLOT - 3 | + +If DL\_COVERAGE\_CLASS > CC1 and UL\_COVERAGE\_CLASS = CC1, the STARTING\_UL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| bit | | +|-----|----------------------------------------------------| +| 2 | 1 | +| 0 0 | Same timeslot as indicated by STARTING_DL_TIMESLOT | +| 0 1 | STARTING_DL_TIMESLOT + 1 | +| 1 0 | STARTING_DL_TIMESLOT + 2 | +| 1 1 | STARTING_DL_TIMESLOT + 3 | + +If both DL\_COVERAGE\_CLASS and UL\_COVERAGE\_CLASS = CC1 (indicated by the *EC Packet Channel Description Type 2 IE* - see sub-clause 10.5.2.85), the uplink EC-PACCH is assigned to the timeslot indicated by the STARTING\_DL\_TIMESLOT field. In this case the STARTING\_UL\_TIMESLOT\_OFFSET field is considered as invalid by the mobile station. + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GAMMA (5 bit field)

This field is the binary representation of the parameter FCH for MS output power control in units of 2 dB, see 3GPP TS 45.008. | +| ALPHA Enable (1 bit field)

This field is coded as described in sub-clause 9.1.60 | +| P0 (4 bit field)

For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. | +| PR_MODE (1 bit field)

For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. | +| Multilateration Information Request (1 bit field)
This field indicates whether or not a MS is to include "MS Transmission Offset" and "MS Sync Accuracy" parameters when sending an EC Packet Downlink Ack/Nack message (see 3GPP TS 44.060 [76]) during a downlink EC TBF.
This field is coded as follows:
0 Do not include "MS Transmission Offset" and "MS Sync Accuracy" parameters
1 Include the "MS Transmission Offset" and "MS Sync Accuracy" parameters | + +### 9.1.65 EC Packet Channel Request + +This message may be sent by an EC capable mobile station attempting system access using the EC-RACH (see sub-clause 3.5.2.1.2a) in which the message format is as shown in Tables 9.1.65.1 and 9.1.65.2. This message can also be sent using the RACH (see sub-clause 3.5.2.1.2) in which the message format is as shown in Tables 9.1.65.3 and 9.1.65.4. + +The uplink access burst block format is defined in 3GPP TS 44.004. The order of bit transmission is defined in 3GPP TS 44.004. The message is coded in 11-bit format. + +The EC capability is implied when a MS attempts system access using the EC-RACH or by the use of TS3 when a MS attempts system access using the RACH. + +**Table 9.1.65.1: EC PACKET CHANNEL REQUEST messages and EC MULTILATERATION REQUEST messages (EC-RACH)** + +| Training sequence
(see 3GPP TS 45.002) | bits
11.....1 | Packet Channel Access | +|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------| +| TS3 | < EC PACKET CHANNEL REQUEST message content > | Uplink CC1 MS | +| TS4 | < EC MULTILATERATION REQUEST message content > (Note 1) | Uplink CC1 MS | +| TS5 | < EC PACKET CHANNEL REQUEST message content > or < EC MULTILATERATION REQUEST message content > (Note 1, Note 2, Note 4) | Uplink CC2 MS or CC5 MS | +| TS6 | < EC PACKET CHANNEL REQUEST message content > or < EC MULTILATERATION REQUEST message content > (Note 1, Note 2, Note 4) | Uplink CC3 MS or CC5 MS | +| TS7 | < EC PACKET CHANNEL REQUEST message content > or < EC MULTILATERATION REQUEST message content > (Note 1, Note 2, Note 4) | Uplink CC4 MS or CC5 MS | +| TS8 | < EC PACKET CHANNEL REQUEST message content > or < EC MULTILATERATION REQUEST message content > (Note 1, Note 3, Note 4) | Uplink CC5 MS | + +Note 1: See sub-clauses 3.5.2.1.2a and 3.11 for which type of EC MULTILATERATION REQUEST message described in Table 9.1.65.2 is sent by a MS when performing the radio access part of the MTA procedure or when sending a Page Response for a positioning event. +Note 2: For CC5 MS, EDAB (see 3GPP TS 45.002 [32]) is supported with TS5 or TS6 or TS7 when sending an EC PACKET CHANNEL REQUEST message if EC SI 2 message indicates CC5 access is supported (i.e. CC4\_Range\_UL parameter is included) and if EC SI 2 parameter CC5\_EC-RACH\_FORMAT\_IND is set to EDAB. +Note 3: For CC5 MS, ESAB (see 3GPP TS 45.002 [32]) is supported when sending an EC PACKET CHANNEL REQUEST message if EC SI 2 message indicates CC5 access is supported (i.e. CC4\_Range\_UL parameter is included) and if EC SI 2 parameter CC5\_EC-RACH\_FORMAT\_IND is set to ESAB. +Note 4: For CC5 an EC MULTILATERATION REQUEST message can be sent if EC SI 2 message indicates CC5 access is supported (i.e. CC4\_Range\_UL parameter is included). + +**Table 9.1.65.2: EC PACKET CHANNEL REQUEST message and EC MULTILATERATION REQUEST message content (EC-RACH)** + +| TS | Bit 11 | Bit 10 | Bit 9 | Bit 8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | | | | | | | | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|---------------------|--|--|--|--|--|--|--|--| +| 3
(CC1) | < EC PACKET CHANNEL REQUEST message content > ::=
< EC-NumberOfBlocks : bit (3) >
< EC Priority : bit (1) >
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) > ; | | | | | | | | | | EGPRS
Capability | | | | | | | | | +| 4
(CC1) | 0 | 0 | < EC MULTILATERATION REQUEST message content (RLC Data Block method or Page Response for Positioning Event) > ::=
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) >
< Access Discriminator : bit (1) >
< Final MTA Access : bit (1) > ; | | | | | | | | EGPRS
Capability | | | | | | | | | +| 4
(CC1) | 0 | 1 | < EC MULTILATERATION REQUEST message content (Access Burst method) > ::=
< Short ID : bit (8) > ; | | | | | | | | Spare | | | | | | | | | +| 4
(CC1) | 1 | 0 | < EC MULTILATERATION REQUEST message content (Extended Access Burst Method – part 1) > ::=
< Random ID Low : bit (4) >
< MS Transmission Offset : bit (4) > ; | | | | | | | | 0 | | | | | | | | | +| 4
(CC1)
Note 1 | 1 | 0 | < EC MULTILATERATION REQUEST message content (Extended Access Burst Method – part 2) > ::=
< Random ID Low : bit (4) >
< MS Sync Accuracy : bit (4) > ; | | | | | | | | 1 | | | | | | | | | +| 4
(CC1) | 1 | 1 | Spare (9) | | | | | | | | | | | | | | | | | +| 5
(CC2) | < EC PACKET CHANNEL REQUEST message content > ::=
< EC-NumberOfBlocks : bit (3) >
< EC Priority : bit (1) >
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) > ; | | | | | | | | | | 0 | | | | | | | | | +| 5
(CC2) | 0 | 0 | < EC MULTILATERATION REQUEST message content (RLC Data Block method or Page Response for Positioning Event) > ::=
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) >
< Access Discriminator : bit (1) >
< Final MTA Access : bit (1) > ; | | | | | | | | 1 | | | | | | | | | +| 5
(CC2) | 0 | 1 | < EC MULTILATERATION REQUEST message content (Access Burst method) > ::=
< Short ID : bit (8) > ; | | | | | | | | 1 | | | | | | | | | +| 5
(CC2) | 1 | Spare (9) | | | | | | | | | 1 | | | | | | | | | +| 6
(CC3) | < EC PACKET CHANNEL REQUEST message content > ::=
< EC-NumberOfBlocks : bit (3) >
< EC Priority : bit (1) >
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) > ; | | | | | | | | | | 0 | | | | | | | | | +| 6
(CC3) | 0 | 0 | < EC MULTILATERATION REQUEST message content (RLC Data Block method or Page Response for Positioning Event) > ::=
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) >
< Access Discriminator : bit (1) >
< Final MTA Access : bit (1) > ; | | | | | | | | 1 | | | | | | | | | +| 6
(CC3) | 0 | 1 | < EC MULTILATERATION REQUEST message content (Access Burst method) > ::=
< Short ID : bit (8) > ; | | | | | | | | 1 | | | | | | | | | +| 6
(CC3) | 1 | Spare (9) | | | | | | | | | 1 | | | | | | | | | + +| | | | | +|-----------------------------|---------------------------------------------------|-----------|------------------------------------------------------------------------------------------------------------------| +| 7
(CC4)
or 8
(CC5) | < EC PACKET CHANNEL REQUEST message content > ::= | | 0 | +| | < EC-NumberOfBlocks : bit (3) > | | | +| | < EC Priority : bit (1) > | | | +| | < RandomBits : bit (3) > | | | +| | < Selected DL Coverage Class : bit (3) > ; | | | +| 7
(CC4)
or 8
(CC5) | 0 | 0 | < EC MULTILATERATION REQUEST message content RLC Data Block method or Page Response for Positioning Event) > ::= | +| | | | < RandomBits : bit (3) > | +| | | | < Selected DL Coverage Class : bit (3) > | +| | | | < Access Discriminator : bit (1) > | +| | | | < Final MTA Access : bit (1) > ; | +| 7
(CC4)
or 8
(CC5) | 0 | 1 | < EC MULTILATERATION REQUEST message content (Access Burst method) > ::= | +| | | | < Short ID : bit (8) > ; | +| 7
(CC4)
or 8
(CC5) | 1 | Spare (9) | 1 | + +Note 1: See Table 9.1.65.2.1 for 19 remaining bits of EC MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 2'. + +**Table 9.1.65.2.1: EC MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 2' (Bit 12 to Bit 30)** + +| TS | Bits 12 to Bit 30 | +|------------|--------------------------------| +| 4
(CC1) | < Random ID High : bit (12) > | +| | < Short BSS ID : bit (3) > | +| | < Final MTA Access : bit (1) > | +| | < spare : bit (3) > ; | + +**Table 9.1.65.3: EC PACKET CHANNEL REQUEST message and EC MULTILATERATION REQUEST message (RACH)** + +| Training sequence
(see 3GPP TS 45.002) | bits
11.....1 | Packet Channel Access | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| TS3 | < EC PACKET CHANNEL REQUEST message content > (Note 1) | Uplink CC1 MS | +| TS5 | < EC PACKET CHANNEL REQUEST message content > or < EC MULTILATERATION REQUEST message content > (Note 2, Note 3, Note 4, Note 6) | Uplink CC2 MS or CC5 MS | +| TS6 | < EC PACKET CHANNEL REQUEST message content > or < EC MULTILATERATION REQUEST message content > (Note 2, Note 3, Note 4, Note 6) | Uplink CC3 MS or CC5 MS | +| TS7 | < EC PACKET CHANNEL REQUEST message content > or < EC MULTILATERATION REQUEST message content > (Note 2, Note 3, Note 4, Note 6) | Uplink CC4 MS or CC5 MS | +| TS8 | < EC PACKET CHANNEL REQUEST message content > (Note 1, Note 5, Note 6) | Uplink CC5 MS | + +Note 1: Only sent on RACH when RACH Access Control is enabled (see sub-clause 9.1.30c) + +Note 2: Only sent on RACH when 2TS EC-RACH is enabled (see sub-clause 9.1.43q) + +Note 3: See sub-clauses 3.5.2.1.2a and 3.11 for which type of EC MULTILATERATION REQUEST message described in Table 9.1.65.4 is sent by a MS when performing the radio access part of the MTA procedure or when sending a Page Response for a positioning event. + +Note 4: For CC5 MS, EDAB (see 3GPP TS 45.002 [32]) is supported with TS5 or TS6 or TS7 when sending an EC PACKET CHANNEL REQUEST message if EC SI 2 message indicates CC5 access is supported (i.e. CC4\_Range\_UL parameter is included) and if EC SI 2 parameter CC5\_EC-RACH\_FORMAT\_IND is set to EDAB. + +Note 5: For CC5 MS, ESAB (see 3GPP TS 45.002 [32]) is supported when sending an EC PACKET CHANNEL REQUEST message if EC SI 2 message indicates CC5 access is supported (i.e. CC4\_Range\_UL parameter is included) and if EC SI 2 parameter CC5\_EC-RACH\_FORMAT\_IND is set to ESAB. + +Note 6: For CC5 an EC MULTILATERATION REQUEST message can be sent if EC SI 2 message indicates CC5 access is supported (i.e. CC4\_Range\_UL parameter is included). + +Table 9.1.65.4: EC PACKET CHANNEL REQUEST message content (RACH) + +| TS | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | Bit 8 | Bit 9 | Bit 10 | Bit 11 | | | | | | | | | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|--------|------------------|--|--|--|--|--|--|--|--| +| 3 (CC1) | < EC PACKET CHANNEL REQUEST message content > ::=
< EC-NumberOfBlocks : bit (3) >
< EC Priority : bit (1) >
< RandomBits : bit (3) >
< Signal Strength : bit (3) > ; | | | | | | | | | | EGPRS Capability | | | | | | | | | +| 5 (CC2) | < EC PACKET CHANNEL REQUEST message content > ::=
< EC-NumberOfBlocks : bit (3) >
< EC Priority : bit (1) >
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) > ; | | | | | | | | | | 0 | | | | | | | | | +| 5 (CC2) | 0 | 0 | < EC MULTILATERATION REQUEST message content (RLC Data Block method or Page Response for Positioning Event) > ::=
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) >
< Access Discriminator : bit (1) >
< Spare : bit (1) > ; | | | | | | | | 1 | | | | | | | | | +| 5 (CC2) | 0 | 1 | < EC MULTILATERATION REQUEST message content (Access Burst method) > ::=
< Short ID : bit (8) > ; | | | | | | | | 1 | | | | | | | | | +| 5 (CC2) | 1 | Spare (9) | | | | | | | | | 1 | | | | | | | | | +| 6 (CC3) | < EC PACKET CHANNEL REQUEST message content > ::=
< EC-NumberOfBlocks : bit (3) >
< EC Priority : bit (1) >
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) > ; | | | | | | | | | | 0 | | | | | | | | | +| 6 (CC3) | 0 | 0 | < EC MULTILATERATION REQUEST message content (RLC Data Block method or Page Response for Positioning Event) > ::=
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) >
< Access Discriminator : bit (1) >
< Spare : bit (1) > ; | | | | | | | | 1 | | | | | | | | | +| 6 (CC3) | 0 | 1 | < EC MULTILATERATION REQUEST message content (Access Burst method) > ::=
< Short ID : bit (8) > ; | | | | | | | | 1 | | | | | | | | | +| 6 (CC3) | 1 | Spare (9) | | | | | | | | | 1 | | | | | | | | | +| 7 (CC4) or 8 (CC5) | < EC PACKET CHANNEL REQUEST message content > ::=
< EC-NumberOfBlocks : bit (3) >
< EC Priority : bit (1) >
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) > ; | | | | | | | | | | 0 | | | | | | | | | +| 7 (CC4) or 8 (CC5) | 0 | 0 | < EC MULTILATERATION REQUEST message content (RLC Data Block method or Page Response for Positioning Event) > ::=
< RandomBits : bit (3) >
< Selected DL Coverage Class : bit (3) >
< Access Discriminator : bit (1) >
< Spare : bit (1) > ; | | | | | | | | 1 | | | | | | | | | +| 7 (CC4) or 8 (CC5) | 0 | 1 | < EC MULTILATERATION REQUEST message content (Access Burst method) > ::=
< Short ID : bit (8) > ; | | | | | | | | 1 | | | | | | | | | + +Error: + +112 + +| | | | | +|-----------------------------|---|-----------|---| +| 7
(CC4)
or 8
(CC5) | 1 | Spare (9) | 1 | +|-----------------------------|---|-----------|---| + +**Table 9.1.65.5: EC PACKET CHANNEL REQUEST details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

EC-NumberOfBlocks (3 bit field)

This field indicates the type of payload a mobile station has to send as follows:

bit
3 2 1

0 0 0    page response
0 0 1    RLC/MAC control message
0 1 0    cell update or uplink data transfer requiring 1 MCS-1 coded RLC data block
0 1 1    uplink data transfer – 2 MCS-1 coded RLC data blocks required
1 0 0    uplink data transfer – 3 MCS-1 coded RLC data blocks required
.
.
.
1 1 1    uplink data transfer – 6 or more MCS-1 coded RLC data blocks required

| +|

EC Priority (1 bit field)

This field indicates the priority of the uplink data transfer being requested by the mobile station as follows:

0    normal priority (normal report)
1    high priority (exception report)

| +|

Selected DL Coverage Class (3 bit field)

This field indicates the Downlink Coverage Class that the mobile station has determined to be applicable at the point of sending an EC PACKET CHANNEL REQUEST and, when CC1 applies to the downlink, the extent to which the C-value exceeds the value indicated by the BT_Threshold_DL parameter sent in EC SI2 (see sub-clause 9.1.43q):

Case 1: EC SYSTEM INFORMATION indicates 4 of 4 possible coverage classes are supported:

bit
3 2 1

0 0 0    DL CC4
0 0 1    DL CC3
0 1 0    DL CC2
0 1 1    DL CC1; BT\_Threshold\_DL \leq C\_VALUE < BT\_Threshold\_DL + X \text{ dB}
1 0 0    DL CC1; BT\_Threshold\_DL + X \leq C\_VALUE < BT\_Threshold\_DL + 2X \text{ dB}
1 0 1    DL CC1; BT\_Threshold\_DL + 2X \leq C\_VALUE < BT\_Threshold\_DL + 3X \text{ dB}
1 1 0    DL CC1; BT\_Threshold\_DL + 3X \leq C\_VALUE < BT\_Threshold\_DL + 4X \text{ dB}
1 1 1    DL CC1; C\_VALUE \geq BT\_Threshold\_DL + 4X \text{ dB}

Case 2: EC SYSTEM INFORMATION indicates 3 of 4 possible coverage classes are supported:

bit
3 2 1

0 0 0    DL CC4
0 0 1    DL CC2 or CC3
0 1 0    DL CC1; BT\_Threshold\_DL \leq C\_VALUE < BT\_Threshold\_DL + X \text{ dB}
0 1 1    DL CC1; BT\_Threshold\_DL + X \leq C\_VALUE < BT\_Threshold\_DL + 2X \text{ dB}
1 0 0    DL CC1; BT\_Threshold\_DL + 2X \leq C\_VALUE < BT\_Threshold\_DL + 3X \text{ dB}
1 0 1    DL CC1; BT\_Threshold\_DL + 3X \leq C\_VALUE < BT\_Threshold\_DL + 4X \text{ dB}
1 1 0    DL CC1; BT\_Threshold\_DL + 4X \leq C\_VALUE < BT\_Threshold\_DL + 5X \text{ dB}
1 1 1    DL CC1; C\_VALUE \geq BT\_Threshold\_DL + 5X \text{ dB}

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

Case 3: EC SYSTEM INFORMATION indicates coverage classes 1 and 4 are supported:

bit
3 2 1

0 0 0 DL CC4
0 0 1 DL CC1; BT\_Threshold\_DL \leq C\_VALUE < BT\_Threshold\_DL + X dB
0 1 0 DL CC1; BT\_Threshold\_DL + X \leq C\_VALUE < BT\_Threshold\_DL + 2X dB
0 1 1 DL CC1; BT\_Threshold\_DL + 2X \leq C\_VALUE < BT\_Threshold\_DL + 3X dB
1 0 0 DL CC1; BT\_Threshold\_DL + 3X \leq C\_VALUE < BT\_Threshold\_DL + 4X dB
1 0 1 DL CC1; BT\_Threshold\_DL + 4X \leq C\_VALUE < BT\_Threshold\_DL + 5X dB
1 1 0 DL CC1; BT\_Threshold\_DL + 5X \leq C\_VALUE < BT\_Threshold\_DL + 6X dB
1 1 1 DL CC1; C\_VALUE \geq BT\_Threshold\_DL + 6X dB

X is defined by the DL_Signal_Strength_Step_Size field (see sub-clause 9.1.43q). When determining the value of this field the received signal level based measurements (RLA_EC) or SINR based measurements (SLA) are used to determine the C-value, see 3GPP TS 45.008 [34].

| +|

Access Discriminator (1 bit field)

This field indicates whether the MS sending an access request for performing the radio access part of the MTA procedure using the RLC Data Block method or for sending a Page Response for a positioning event:

bit
0 Radio access part of MTA procedure using the RLC Data Block method
1 Page Response for a positioning event

| +|

Signal Strength (3 bit field)

This field indicates the extent to which the received power exceeds the CC1 threshold:

bit
3 2 1

0 0 0 DL CC1; BT\_Threshold\_DL \leq C\_VALUE < BT\_Threshold\_DL + X dB
0 0 1 DL CC1; BT\_Threshold\_DL + X \leq C\_VALUE < BT\_Threshold\_DL + 2X dB
0 1 0 DL CC1; BT\_Threshold\_DL + 2X \leq C\_VALUE < BT\_Threshold\_DL + 3X dB
0 1 1 DL CC1; BT\_Threshold\_DL + 3X \leq C\_VALUE < BT\_Threshold\_DL + 4X dB
1 0 0 DL CC1; BT\_Threshold\_DL + 4X \leq C\_VALUE < BT\_Threshold\_DL + 5X dB
1 0 1 DL CC1; BT\_Threshold\_DL + 5X \leq C\_VALUE < BT\_Threshold\_DL + 6X dB
1 1 0 DL CC1; BT\_Threshold\_DL + 6X \leq C\_VALUE < BT\_Threshold\_DL + 7X dB
1 1 1 DL CC1; C\_VALUE \geq BT\_Threshold\_DL + 7X dB

X is defined by the DL_Signal_Strength_Step_Size field (see sub-clause 9.1.43q). When determining the value of this field the received signal level based measurements (RLA_EC) or SINR based measurements (SLA) are used to determine the C-value, see 3GPP TS 45.008 [34].

| +|

EGPRS Capability (1 bit field)

This field indicates whether the MS supports GMSK only (EGPRS without 8PSK) or GMSK and 8PSK (EGPRS with 8PSK on uplink and downlink)

0 EGPRS without 8PSK
1 EGPRS with 8PSK (uplink and downlink)

| +|

RandomBits (3 bit field)

For the definition of these three last information fields see 3GPP TS 44.060.

| +|

Short ID (8 bit field)

This field identifies the cell specific Short ID value used by a MS performing the radio access part of the MTA procedure using the Access Burst method (see sub-clause 3.11). The Short ID value used by a MS in a given cell is pre-determined (selected by the SMLC and is included in the RRLP Multilateration Timing Advance message sent to a MS to trigger the Multilateration Timing Advance procedure – see 3GPP TS 44.031). It allows the BSS to identify the applicable SCCP connection between the BSS and the serving SMLC (see 3GPP TS 49.031 and 3GPP TS 44.031).

| + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---|----------------------------------------| +| Random ID Low (4 bit field)
This field is sent as part of an EC MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 1' or 'Extended Access Burst Method – part 2'. It is coded as described in 3GPP TS 44.060 [76]). It consists of the 4 least significant bits of a Random ID parameter provided in the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031). | | | | | +| Random ID High (12 bit field)
This field is sent as part of an EC MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 2'. It consists of the 12 most significant bits of a Random ID parameter provided in the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031). | | | | | +| Short BSS ID (3 bit field)
This field is sent as part of an EC MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 2'. It consists of the Short BSS ID parameter provided to the MS in the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031). | | | | | +| MS Transmission Offset (4 bit field)
This field is sent as part of an EC MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 1'. It is coded as described in 3GPP TS 44.060 [76]). | | | | | +| MS Sync Accuracy (4 bit field)
This field is sent as part of an EC MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 2'. It is coded per the value part of the "MS Synchronization Accuracy" IE defined in 3GPP TS 49.031. | | | | | +| Final MTA Access (1 bit field)
This field indicates whether or not the current access request is the final access request the MS will make for the radio access part of the MTA procedure. It is ignored by the BSS if the Access Discriminator field indicates 'Page Response for a positioning event'.

bit
0 One or more additional access requests pending for the radio access part of the MTA procedure
1 Final access request for MTA procedure
| 0 | One or more additional access requests pending for the radio access part of the MTA procedure | 1 | Final access request for MTA procedure | +| 0 | One or more additional access requests pending for the radio access part of the MTA procedure | | | | +| 1 | Final access request for MTA procedure | | | | + +### 9.1.66 EC IMMEDIATE ASSIGNMENT TYPE 4 + +This message is sent on the EC-CCCH by the network to assign uplink packet resources to a mobile station that has enabled EC operation and has selected CC5 as uplink coverage class and is attempting system access. When sending this message the network assigns pre-allocated uplink resources to the mobile station (see sub-clause 3.5.2.1.3a). + +Message type: EC IMMEDIATE ASSIGNMENT TYPE 4 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.66.1: EC IMMEDIATE ASSIGNMENT TYPE 4 message content** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < EC IMMEDIATE ASSIGNMENT TYPE 4 message content > ::=   < Message Type : bit (4) >   < Used DL Coverage Class : bit (2) >   { 0   1 < EC Page Extension : bit (4) > }   < EC Request Reference : bit (13) >   < EC Packet Channel Description Type 3 : bit (15) > -- This is a new parameter in EC IA type 3 vs. EC IA type 2.   < EC Fixed Uplink Allocation : < EC Fixed Uplink Allocation struct >>   <spare padding> ;
| +| 
 < EC Fixed Uplink Allocation struct > ::=   < Enhanced Access Burst : bit (1) >   { 0   1 < Timing Advance : bit (6) > }   < STARTING_UL_TIMESLOT : bit (3) >   < Uplink_TFI_Assignment : bit (5) >   < STARTING_DL_TIMESLOT_OFFSET : bit (2) >   < OVERLAID_CDMA_CODE : bit (2) >   { 0     – use MCS-1 for uplink packet transfer     1 < Assigned MCS : bit (4) > }   < GAMMA : bit (5) >   < ALPHA Enable : bit (1) >   { 0   1 < P0 : bit (4) >     < PR_MODE : bit (1) > }   < Start_First_UL_Data_Block : bit (4) >   { 1 { 0 < Start_FN_Next_Data_Block : bit (3) >       1 – no gap between last block and next block } } ** 0 ;
| + +**Table 9.1.66.2: EC IMMEDIATE ASSIGNMENT TYPE 4 message details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| +|

Used DL Coverage Class (2 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

EC Page Extension (4 bit field)

This field is coded as described in sub-clause 9.1.60.

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

EC Request Reference (13 bit field)

This field is coded as described in sub-clause 10.5.2.83

| +|

EC Packet Channel Description Type 3 (15 bit field)

This information element is coded as described in sub-clause 10.5.2.88

| +|

Enhanced Access Burst (1 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

Timing Advance (6 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

STARTING_UL_TIMESLOT (3 bit field)

This field indicates the first assigned timeslot within the set of assigned uplink timeslots.:

Bit
3 2 1
0 0 0 Timeslot 0 is the first assigned uplink timeslot
0 0 1 Timeslot 1 is the first assigned uplink timeslot
0 1 0 Timeslot 2 is the first assigned uplink timeslot
0 1 1 Timeslot 3 is the first assigned uplink timeslot
1 0 0 Timeslot 4 is the first assigned uplink timeslot
1 0 1 Timeslot 5 is the first assigned uplink timeslot
1 1 0 Timeslot 6 is the first assigned uplink timeslot
1 1 1 Timeslot 7 is the first assigned uplink timeslot

If the field EC_Reduced_PDCH_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q): a mobile station assigned CC5 on the uplink is always assigned the use of 4 consecutive timeslots and therefore only timeslot 0, 1, 2, 3 or 4 shall be indicated as the first assigned uplink timeslot.

If the field EC_Reduced_PDCH_Allocation is set to 1 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q): A mobile station assigned CC5 on the uplink is always assigned the use of 2 consecutive timeslots and therefore only timeslot 0, 1, 2, 3, 4, 5 or 6 shall be indicated as the first assigned uplink timeslot.

| +|

Uplink_TFI_Assignment (5 bit field)

This field is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31.

| +|

STARTING_DL_TIMESLOT_OFFSET (2 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

OVERLAID_CDMA_CODE (2 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

Assigned MCS (4 bit field)

This field is coded as per EGPRS Modulation and Coding Scheme IE decribed in 3GPP TS 44.060.

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

GAMMA (5 bit field)

This field is the binary representation of the parameter ΓCH for MS output power control in units of 2 dB, see 3GPP TS 45.008.

| | | | | | | | | | | | | | | | | | | +|

ALPHA Enable (1 bit field)

This field is coded as described in sub-clause 9.1.60.

| | | | | | | | | | | | | | | | | | | +|

P0 (4 bit field)

For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060.

| | | | | | | | | | | | | | | | | | | +|

PR_MODE (1 bit field)

For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060.

| | | | | | | | | | | | | | | | | | | +|

Start_First_UL_Data_Block (4 bit field)

This field identifies the uplink transmission opportunity corresponding to the assigned uplink coverage class (see the EC Packet Channel Description Type 2 IE described in sub-clause 10.5.2.85) that the mobile station is to use to start sending its first uplink RLC data block on the set of assigned uplink timeslots. The 1st transmission opportunity occurs in 52 multiframe immediately following the last TDMA frame (i.e TDMA frame N) used for transmission EC IMMEDIATE ASSIGNMENT TYPE 4 message. See 3GPP TS 45.010 [35] for mobile station reaction time requirements applicable to receiving an assignment message. This field is coded as follows:

Bit
4 3 2 1
0 0 0 0 Use the 1st transmission opportunity
0 0 0 1 Use the 2nd transmission opportunity
0 0 1 0 Use the 3rd transmission opportunity
. .
. .
. .
1 1 1 1 Use the 16th transmission opportunity

For CC1 the Kth transmission opportunity equals that for CC1 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2).

For CC2 the Kth transmission opportunity equals that for CC2 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2).

For CC3 the Kth transmission opportunity equals that for CC3 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2).

For CC4 the Kth transmission opportunity equals that for CC4 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2).

For CC5 the Kth transmission opportunity = the Kth set of 48 BTTI radio blocks on the assigned timeslots occurring after TDMA frame N+9. If the field EC_Reduced_PDCH_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q), the Kth set of 48 BTTI radio blocks occurs in B0 of the Kth 52-multiframe that occurs after TDMA frame N. If the field EC_Reduced_PDCH_Allocation is set to 1 the Kth set of 48 BTTI radio blocks occurs in B0 of the Kth pair of 52-multiframes that occurs after TDMA frame N wherein the first 52-multiframe of the pair is an even number (i.e. (TDMA\ FN\ div\ 52)\ mod\ 2 = 0).

| Bit | | 4 3 2 1 | | 0 0 0 0 | Use the 1 st transmission opportunity | 0 0 0 1 | Use the 2 nd transmission opportunity | 0 0 1 0 | Use the 3 rd transmission opportunity | . | . | . | . | . | . | 1 1 1 1 | Use the 16 th transmission opportunity | +| Bit | | | | | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | | | | | +| 0 0 0 0 | Use the 1 st transmission opportunity | | | | | | | | | | | | | | | | | | +| 0 0 0 1 | Use the 2 nd transmission opportunity | | | | | | | | | | | | | | | | | | +| 0 0 1 0 | Use the 3 rd transmission opportunity | | | | | | | | | | | | | | | | | | +| . | . | | | | | | | | | | | | | | | | | | +| . | . | | | | | | | | | | | | | | | | | | +| . | . | | | | | | | | | | | | | | | | | | +| 1 1 1 1 | Use the 16 th transmission opportunity | | | | | | | | | | | | | | | | | | + +#### **Start\_FN\_Next\_Data\_Block (3 bit field)** + +This field identifies the gap (in coverage class specific transmission opportunities) between the last pre-allocated uplink radio block transmitted on assigned uplink timeslots and the next pre-allocated uplink radio block to be used for the uplink transmission. This field is coded as follows: + +Bit + +**3 2 1** + +0 0 0 a gap of 1 transmission opportunity + 0 0 1 a gap of 2 transmission opportunities + 0 1 0 a gap of 3 transmission opportunities + +. + +. + +. + +1 1 1 a gap of 8 transmission opportunities + +For CC1 a gap of K transmission opportunities equals that for CC1 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2). + +For CC2 a gap of K transmission opportunities equals that for CC2 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2). + +For CC3 a gap of K transmission opportunities equals that for CC3 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2). + +For CC4 a gap of K transmission opportunities equals that for CC4 specified in the EC IMMEDIATE ASSIGNMENT TYPE 2 message (see sub-clause 9.1.60 – Table 9.1.60.2). + +For CC5 a gap of K transmission opportunities = K sets of 48 BTTI radio blocks on the assigned timeslots occurring immediately after the last set of 16 BTTI radio block used for the uplink transmission. If the field **EC\_Reduced\_PDCH\_Allocation** is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q), each 52-multiframe counts as a gap of one CC5 transmission opportunity. If the field **EC\_Reduced\_PDCH\_Allocation** is set to 1 each pair of 52-multiframes counts as a gap of one CC5 transmission opportunity. + +### 9.1.67 EC DOWNLINK ASSIGNMENT TYPE 2 + +This message is sent on the EC-CCCH by the network to assign downlink packet resources to a mobile station that has enabled EC operation, supports uplink coverage class CC5 and uplink coverage class CC5 is assigned. + +Message type: EC DOWNLINK ASSIGNMENT TYPE 2 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.67.1: EC DOWNLINK ASSIGNMENT TYPE 2 message content** + +``` +< EC Downlink Assignment message Type 2 content > ::= + < Message Type : bit (4) > + < Used DL Coverage Class: bit (2) > + { 0 | 1 < EC Page Extension : bit (4) > } + < TLLI : bit (32) > + < EC Packet Channel Description Type 3 : bit (15) > -- This is a new parameter in EC DA type 2 vs. EC DA type 1. + < EC Downlink Allocation : < EC Downlink Allocation struct >> + < spare padding > ; + +< EC Downlink Allocation struct > ::= + < Timing Advance : bit (6) > +``` + +``` + +< STARTING_DL_TIMESLOT : bit (3) > +< Downlink_TFI_Assignment : bit (5) > +< TIMESLOT_MULTIPLICATOR : bit (2) > +< STARTING_UL_TIMESLOT_OFFSET (2) > +< GAMMA : bit (5) > +< ALPHA Enable : bit (1) > +{ 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } ; + +``` + +**Table 9.1.67.2: EC DOWNLINK ASSIGNMENT TYPE 2 message details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| +|

Used DL Coverage Class (2 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

EC Page Extension (4 bit field)

This field is coded as described in sub-clause 9.1.60.

| +|

TLLI (32 bit field)

This field is the binary representation of a TLLI. The coding of TLLI is left open for each administration using the structure specified in 3GPP TS 23.003.

| +|

EC Packet Channel Description Type 3 (15 bit field)

This information element is coded as described in sub-clause 10.5.2.88.

| +|

Timing Advance (6 bit field)

This field is coded as described in sub-clause 9.1.60

| +|

STARTING_DL_TIMESLOT (3 bit field)

This field is coded as described in sub-clause 9.1.64.

| +|

Downlink_TFI_Assignment (5 bit field)

This field is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31.

| +|

TIMESLOT_MULTIPLICATOR (2 bit field)

This field is coded as described in sub-clause 9.1.64.

| +|

STARTING_UL_TIMESLOT_OFFSET (2 bit field)

This field is coded as described in sub-clause 9.1.64.

| +|

GAMMA (5 bit field)

This field is the binary representation of the parameter \Gamma_{CH} for MS output power control in units of 2 dB, see 3GPP TS 45.008.

| +|

ALPHA Enable (1 bit field)

This field is coded as described in sub-clause 9.1.60.

| + +#### **P0 (4 bit field)** + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +#### **PR\_MODE (1 bit field)** + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +### 9.1.68 EC IMMEDIATE ASSIGNMENT TYPE 3 + +This message is sent on the EC-CCCH by the network to a mobile station that has enabled EC operation and has sent an EC MULTILATERATION REQUEST message when performing the radio access part of the MTA procedure using the Access Burst method or the Extended Access Burst method (see sub-clause 3.5.2.1.2a and sub-clause 3.11). + +Message type: EC IMMEDIATE ASSIGNMENT TYPE 3 + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.68.1: EC IMMEDIATE ASSIGNMENT TYPE 3 message content** + +``` +< EC Immediate Assignment Type 3 message content > ::= + < Message Type : bit (4) > + < Used DL Coverage Class : bit (2) > + { 0 | 1 < EC Page Extension : bit (4) > } + < Acknowledged Access Request 1 : Acknowledged Access Request struct > + { 0 | 1 < Acknowledged Access Request 2 : Acknowledged Access Request struct > } + { 0 | 1 < Acknowledged Access Request 3 : Acknowledged Access Request struct > } + { 0 | 1 < Acknowledged Access Request 4 : Acknowledged Access Request struct > } + { 0 | 1 < Acknowledged Access Request 5 : Acknowledged Access Request struct > } + { 0 | 1 < Acknowledged Access Request 6 : Acknowledged Access Request struct > } + < spare padding > ; + +< Acknowledged Access Request struct > ::= + { + 00 < Short ID : bit (8) > + | 01 < Random ID Low : bit (4) > + | 10 < Random ID High : bit (12) > + | 11 -- Reserved } + } +``` + +**Table 9.1.68.2: EC IMMEDIATE ASSIGNMENT TYPE 3 message details** + +| | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--|---|---|-----|---------|-----|---------|-----|---------|-----|---------| +|

Message Type (4 bit field)

This field indicates the type of message sent on the EC-CCCH (see Table 10.4.4)

| | | | | | | | | | | | | +|

Used DL Coverage Class (2 bit field)

The EC IMMEDIATE ASSIGNMENT TYPE 3 message is sent using blind physical layer transmissions specific to the TSC value used by the MS when sending the corresponding EC MULTILATERATION REQUEST message on the EC-RACH. The Used DL Coverage Class field is included to inform other mobile stations about the downlink coverage class, and thus the number of blind physical layer transmissions, that have been used to transmit the current EC IMMEDIATE ASSIGNMENT TYPE 3 message. Mobile stations that have selected a lower downlink coverage class than what is indicated by this field can, upon successfully reading the control message, can avoid monitoring any remaining blind physical layer transmissions used to send the control message. This field is coded as follows:

bit
2 1
0 0 DL CC 1
0 1 DL CC 2
1 0 DL CC 3
1 1 DL CC 4
| bit | | 2 | 1 | 0 0 | DL CC 1 | 0 1 | DL CC 2 | 1 0 | DL CC 3 | 1 1 | DL CC 4 | +| bit | | | | | | | | | | | | | +| 2 | 1 | | | | | | | | | | | | +| 0 0 | DL CC 1 | | | | | | | | | | | | +| 0 1 | DL CC 2 | | | | | | | | | | | | +| 1 0 | DL CC 3 | | | | | | | | | | | | +| 1 1 | DL CC 4 | | | | | | | | | | | | +|

EC Page Extension (4 bit field)

See sub-clause 9.1.60.

| | | | | | | | | | | | | +|

Acknowledged Access Request N

This field allows for acknowledging up to 6 access requests within a single EC IMMEDIATE ASSIGNMENT TYPE 3 message. Each instance of an acknowledged access request may indicate one of "Short ID", "Random ID Low" or "Random ID High" (see sub-clauses 3.5.2.1.2a, 3.11 and 9.1.65).

| | | | | | | | | | | | | +|

Short ID (8 bit field)

See sub-clause 9.1.65

| | | | | | | | | | | | | +|

Random ID Low (4 bit field)

This field consists of the Random ID Low value received from a MS when the Extended Access Burst method is used (see sub-clauses 3.5.2.1.2a, 3.11 and 9.1.65).

| | | | | | | | | | | | | +|

Random ID High (12 bit field)

This field consists the Random ID High value received from a MS when the Extended Access Burst method is used (see sub-clauses 3.5.2.1.2a, 3.11 and 9.1.65).

| | | | | | | | | | | | | + +### 9.1.69 EC PAGING INDICATION + +This message is sent on the EC-PICH by the network to a mobile station that has selected its downlink coverage class as CC3/CC4 and is capable of receiving EC-PICH indicating whether the MS should further receive the EC-CCCH/D blocks corresponding to the EC-PICH block or can enter into sleep mode. + +Message type: EC PAGING INDICATION + +Significance: dual + +Direction: network to mobile station + +**Table 9.1.69.1: EC PAGING INDICATION message content** + +| | +|---------------------------------------------------------------------------------------------------------| +| < EC Paging Indication > ::=
< Message Type : bit (4) >
< Paging Indication Sequence : bit (84) > | +|---------------------------------------------------------------------------------------------------------| + +**Table 9.1.69.2: EC PAGING INDICATION message details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Type (4 bit field) | +| This field indicates the type of message sent on the EC-CCCH (see Table 10.4.5) | +| Paging Indication Sequence (84 bit field) | +|

If the message is sent towards mobile station(s) in CC4 coverage condition, this field includes the sequence selected from Table 9.1.69.3 based on the training sequence used for EC-CCCH/D CC1 and the indication (wake-up or go-to-sleep) to be sent in the EC-PICH block.

If the message is sent towards mobile station(s) in CC3 coverage condition, this field includes the sequence selected from Tables 9.1.69.4 and 9.1.69.5 based on the training sequence used for EC-CCCH/D CC1, the indication (wake-up or go-to-sleep) to be sent in the EC-PICH block and the referred paging block (first or second) mapped to the EC-PICH block.

| + +**Table 9.1.69.3: Paging Indication Sequence in EC PAGING INDICATION message for CC4** + +| Training sequence
(see
3GPP TS 45.002) | Paging Indication Sequence for wake-up-indication for paging block mapped to EC-PICH block | Paging Indication Sequence for go-to-sleep indication for paging block mapped to EC-PICH block | +|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TS0 | 0,0,0,1,0,0,0,1,1,1,0,0,1,0,1,0,0,1,1,0,0,0,0,1,0,1,0,0,1
,0,1,1,1,0,0,0,0,0,0,0,1,0,0,0,0,0,1,1,0,1,1,0,1,1,0,0
,0,0,1,1,0,1,1,0,0,1,0,0,0,1,1,1,1,1,0,1,1,1,1,0,1,0,1 | 0,0,1,0,1,1,0,1,0,0,0,0,1,0,0,0,1,1,0,0,1,0,1,0,1,0,0,0,0
,0,0,0,1,1,1,0,0,1,1,1,1,0,1,0,0,1,1,1,1,1,0,1,1,0,0,0,1,1,
1,1,0,1,0,1,1,1,1,1,1,0,0,0,1,0,1,1,1,1,1,0,1,1,0,0,0,0 | +| TS1 | 0,0,0,0,1,0,0,0,0,1,1,1,0,1,0,1,0,1,0,1,1,0,1,1,1,1,1,0,0
,0,1,0,0,0,1,0,0,0,1,1,1,0,0,0,0,0,1,1,1,1,0,1,1,0,0,0,1,
0,1,0,0,0,0,0,0,0,1,1,1,0,0,1,0,1,0,1,0,1,1,1,1,0,0,0 | 0,0,1,1,1,0,1,0,1,0,1,0,1,0,0,0,0,0,0,0,1,0,1,1,1,1,0,0,1
,0,1,0,0,1,0,0,1,1,0,0,1,0,0,1,0,1,1,0,1,1,1,0,0,1,1,0,0,
0,1,0,1,1,1,0,0,0,0,0,0,0,0,1,0,1,0,1,1,1,1,0,0,0,0,0,0 | +| TS2 | 0,0,1,0,0,0,1,1,0,1,0,1,0,0,0,0,1,0,0,0,1,1,1,0,1,0,1,0,0
,1,1,1,0,0,1,0,0,1,1,1,1,1,0,0,0,0,0,1,0,0,1,1,0,0,0,0,1,
0,1,0,0,0,0,1,0,0,1,0,0,0,1,1,1,0,0,0,1,0,1,0,1,0,0 | 0,0,0,1,0,1,0,0,1,1,1,1,1,0,1,0,1,1,0,1,1,1,1,1,0,0,0,0,1
,0,1,0,0,0,0,1,0,1,0,1,0,1,1,1,1,1,0,0,1,1,1,0,1,0,1,1,0,
0,0,0,1,0,1,0,1,0,0,1,1,1,1,1,1,1,1,0,0,0,0,0,0,0,1 | +| TS3 | 0,0,1,0,0,1,0,1,0,1,1,1,1,1,0,1,1,1,1,1,0,1,0,0,0,0,0,0,1
,1,0,1,0,1,1,1,0,1,1,1,1,1,0,0,1,1,1,1,0,0,1,1,1,1,1,1,1,
1,1,0,0,0,0,0,1,0,1,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,1 | 0,0,0,1,1,0,1,0,0,0,1,1,0,1,0,0,0,0,0,1,1,1,1,1,0,1,1,1,0
,0,1,0,0,1,1,0,1,1,0,1,1,0,0,1,0,1,0,1,1,1,0,1,0,1,1,1,1,
0,0,1,0,1,1,0,1,0,1,0,1,0,1,1,1,0,0,0,0,0,0,0,1,1,0,0 | +| TS4 | 0,0,0,0,1,0,0,0,0,1,1,1,0,1,0,1,0,1,0,1,1,0,1,1,1,1,1,0,0
,0,1,0,0,0,1,0,0,0,1,1,1,0,0,0,0,0,1,1,1,1,0,1,1,0,0,0,1,
0,1,0,0,0,0,0,0,0,1,1,1,0,0,1,0,1,0,1,0,1,1,1,1,0,0,0 | 0,0,1,1,1,0,1,0,1,0,1,0,1,0,0,0,0,0,0,0,1,0,1,1,1,1,0,0,1
,0,1,0,0,1,0,0,1,1,0,0,1,0,0,1,0,1,1,0,1,1,1,0,0,1,1,0,0,
0,1,0,1,1,1,0,0,0,0,0,0,0,0,1,0,1,0,1,1,1,1,0,0,0,0,0,0 | +| TS5 | 0,0,0,0,0,0,0,0,1,0,1,1,0,0,0,0,1,1,1,0,1,0,1,0,1,0,1,0,1
,1,1,0,0,0,0,0,1,0,1,0,0,1,1,1,0,1,1,0,1,1,1,1,0,0,1,0,1,
0,1,1,1,1,0,1,0,1,1,0,0,0,1,0,1,1,0,0,0,1,0,1,0,0,0,0,0 | 0,0,0,1,1,1,1,1,1,1,1,1,1,1,0,1,1,0,1,0,0,1,0,1,1,0,1,0,1,0
,0,1,0,0,0,0,0,0,0,1,1,1,0,0,0,0,0,1,1,0,0,0,1,1,0,1,0,1,0,
1,0,1,1,1,0,0,1,1,1,0,1,1,0,1,1,1,1,0,0,1,1,0,1,0,0,1 | +| TS6 | 0,0,1,0,1,1,1,1,1,1,0,1,0,1,1,1,0,0,1,1,1,0,0,0,1,0,1,0,0
,0,0,1,1,0,1,1,0,1,0,0,1,0,0,0,0,1,1,0,1,0,0,0,0,1,1,0,0,0,
1,0,0,1,1,1,1,1,0,1,0,0,1,1,0,1,1,0,0,0,1,1,1,0,0,1,1 | 0,0,0,1,1,0,0,0,1,1,0,0,0,0,0,0,0,1,0,1,1,0,0,1,1,1,1,0,1
,1,1,1,1,1,0,1,0,1,0,0,1,1,1,1,1,1,0,1,1,1,1,0,0,1,0,0,0,1,1,
1,0,1,1,0,1,1,0,0,0,0,1,1,1,0,1,1,0,1,1,1,1,1,1,1,1,1 | +| TS7 | 0,0,0,0,0,0,0,0,1,0,1,1,0,0,0,0,1,1,1,0,1,0,1,0,1,0,1,0,1
,1,1,0,0,0,0,0,1,0,1,0,0,1,1,1,0,1,1,0,1,1,1,1,0,0,1,0,1,
0,1,1,1,1,0,1,0,1,1,0,0,0,1,0,1,1,0,0,0,1,0,1,0,0,0,0,0 | 0,0,0,1,1,1,1,1,1,1,1,1,1,1,0,1,1,0,1,0,0,1,0,1,1,0,1,0,1,0
,0,1,0,0,0,0,0,0,0,1,1,1,0,0,0,0,0,1,1,0,0,0,1,1,0,1,0,1,0,
1,0,1,1,1,0,0,1,1,1,0,1,1,0,1,1,1,1,0,0,1,1,0,1,0,0,1 | + +**Table 9.1.69.4: Paging Indication Sequence in EC PAGING INDICATION message for CC3 for first paging block** + +| Training sequence
(see
3GPP TS 45.002) | Paging Indication Sequence for wake-up-indication for first paging block mapped to EC-PICH block | Paging Indication Sequence for go-to-sleep indication for first paging block mapped to EC-PICH block | +|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TS0 | 0,0,1,0,1,0,0,0,0,0,0,1,0,0,1,0,0,1,0,1,0,0,0,1,0,1,1,0,1
,0,0,0,0,1,1,0,1,1,1,1,0,1,1,0,0,1,0,1,1,1,1,0,0,1,1,0,1,0,1,
1,1,0,1,1,0,0,1,0,0,1,0,1,0,1,0,0,1,1,1,1,1,0,0,1,1,1 | 0,0,1,0,0,1,0,1,0,0,1,1,0,1,1,1,1,0,1,0,0,1,0,0,0,0,1,0,1,1,1
,0,1,0,1,1,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,1,1,1,0,0,0,1,1,0,0,
1,1,1,0,0,1,0,0,0,1,1,0,1,0,0,1,0,0,1,0,0,0,1 | +| TS1 | 0,0,0,0,1,0,1,0,1,1,0,0,1,1,0,0,0,1,0,0,1,1,0,1,0,1,1,0,1
,0,0,1,1,1,0,1,0,0,1,0,1,0,0,1,1,0,0,1,1,0,1,1,1,0,0,0,1,0,
0,1,0,0,0,1,1,1,0,0,1,1,1,1,0,0,1,0,0,0,1,0,0,1,1,0,1 | 0,0,1,0,1,0,1,1,0,1,1,0,0,0,0,1,1,1,0,0,1,0,1,1,1,0,0,0,0,1,0
,0,1,0,0,1,0,0,1,1,0,0,1,0,0,1,0,1,1,0,1,1,1,0,0,0,1,0,0,0,1,0,
1,1,0,1,0,1,1,0,1,0,1,0,0,1,0,1,1,0,0,0,0,0,0 | +| TS2 | 0,0,0,1,0,0,1,1,1,1,1,0,0,1,1,1,1,0,0,1,0,0,1,0,0,1,1,0,1,0
,0,0,0,1,0,1,0,1,0,0,0,1,0,1,0,0,1,0,0,1,0,0,1,0,1,0,1,1,
0,1,0,0,0,0,1,1,1,1,1,0,1,1,0,0,0,0,0,1,1,0,1,0,1,0,0 | 0,0,0,0,0,1,1,0,0,0,0,1,1,1,1,1,1,1,1,1,1,0,0,0,1,0,0,1,1,1,1,0
,1,1,0,1,1,0,1,0,0,1,0,0,0,1,0,0,0,1,1,0,1,1,0,1,0,0,0,1,1,1,1,0,1,
0,0,1,0,1,0,1,0,1,0,1,1,0,1,0,1,0,0,1,0,0,1,1 | +| TS3 | 0,0,0,0,1,0,1,0,1,0,0,1,1,1,0,0,1,0,0,0,1,1,1,1,1,1,1,0,0,0
,0,0,1,0,0,0,0,1,0,0,1,1,1,0,0,1,1,1,0,1,0,0,0,1,0,0,0,0,0,
1,1,0,0,1,0,1,0,0,0,1,0,1,1,0,1,1,0,0,0,1,0,1,0,0,0,1 | 0,0,0,0,1,0,0,1,1,1,0,0,0,0,0,0,1,1,1,1,1,1,1,1,0,0,1,0,1,1,1,1
,0,1,0,1,0,0,1,0,0,1,0,0,0,0,0,0,0,0,1,0,1,1,1,1,0,0,1,0,1,1,0,1,
0,1,1,1,1,0,0,0,1,0,0,1,0,1,0,0,0,1,0,0,1,1,1,1 | +| TS4 | 0,0,0,0,1,1,1,1,0,1,0,1,1,1,1,1,0,1,1,1,1,0,1,1,1,1,0,1
,0,0,1,0,0,1,1,1,1,0,1,0,0,0,0,1,0,1,1,1,0,0,0,0,1,1,1,0,
0,0,0,0,0,1,0,1,0,1,1,1,0,1,0,0,0,0,0,1,0,0,0,1,1,1,0 | 0,0,0,1,1,0,1,0,1,0,1,0,1,0,0,1,1,0,0,1,1,0,1,1,1,0,1,0,0,1,0
,1,0,0,1,1,0,0,0,0,0,1,0,0,0,1,1,0,0,0,1,0,1,0,0,1,1,1,0,0,0,0,
0,0,1,1,0,0,0,0,0,1,0,0,1,1,0,1,0,1,0,1,0,1,1,0 | +| TS5 | 0,0,1,1,1,0,1,0,1,1,1,1,0,0,0,0,1,1,0,0,0,1,0,0,1,0,0,1,1
,0,1,0,1,0,1,0,0,0,0,0,1,1,1,0,0,0,0,0,1,0,1,0,0,0,0,1,
1,1,0,0,1,1,1,1,1,0,1,1,1,1,1,1,0,1,0,0,1,1,0,1,0,1,0 | 0,0,0,1,1,0,1,0,1,0,1,0,1,0,0,1,1,0,0,1,1,0,1,1,1,0,1,0,0,1,0
,1,0,0,1,1,0,0,0,0,0,1,0,0,0,1,1,0,0,0,1,0,1,0,0,1,1,1,0,0,0,0,
0,0,1,1,0,0,0,0,0,1,0,0,1,1,0,1,0,1,0,1,0,1,1,0 | +| TS6 | 0,0,1,0,1,0,0,0,0,0,0,1,0,0,1,0,0,1,0,1,0,0,0,1,0,1,1,0,1
,0,0,0,0,1,1,0,1,1,1,1,0,1,1,0,0,1,0,1,1,1,1,0,0,1,1,0,1,0,1,
1,1,0,1,1,0,0,1,0,0,1,0,1,0,1,0,0,1,1,1,1,1,0,0,1,1,1 | 0,0,1,0,0,1,0,1,0,0,1,1,0,1,1,1,1,0,1,0,0,1,0,0,0,0,1,0,1,1,1
,0,1,0,1,1,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,1,1,1,0,0,0,1,1,0,0,
1,1,1,0,0,1,0,0,0,1,1,0,1,0,0,1,0,0,1,0,0,0,1 | +| TS7 | 0,0,1,0,0,1,1,1,1,0,1,1,0,0,1,0,1,1,0,1,0,0,0,0,0,0,0,0,1
,1,0,1,0,1,1,0,0,0,1,1,0,1,0,1,0,1,0,0,1,1,1,0,0,0,0,0,1,0,
0,1,1,1,1,1,1,0,1,1,0,1,0,1,1,1,1,1,1,1,0,1,0,1,0,1,1 | 0,0,1,0,0,0,1,0,1,1,1,1,0,0,1,0,0,1,0,1,1,0,1,0,1,1,1,0,0,0,1
,0,1,1,1,1,0,0,1,1,0,1,1,0,1,1,1,1,0,0,1,1,0,0,1,1,1,0,1,0,0,
1,1,0,0,1,1,0,0,0,1,0,1,1,1,1,1,0,1,1,0,1,1,0,1 | + +**Table 9.1.69.5: Paging Indication Sequence in EC PAGING INDICATION message for CC3 for second paging block** + +| Training sequence (see 3GPP TS 45.002) | Paging Indication Sequence for wake-up-indication for second paging block mapped to EC-PICH block | Paging Indication Sequence for go-to-sleep indication for second paging block mapped to EC-PICH block | +|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TS0 | 0,0,1,0,1,1,1,1,0,0,0,0,1,1,0,1,1,1,1,1,0,0,1,1,0,0,0,1,0,
0,1,0,0,0,0,0,1,0,0,0,0,1,0,0,1,0,0,1,0,1,0,1,1,1,1,
0,1,1,0,1,0,0,0,1,1,0,0,1,0,0,0,1,0,0,0,1,0,0,1,0,0 | 0,0,1,1,1,1,0,1,1,0,1,0,0,0,1,0,1,0,0,1,1,0,1,1,0,0,0,0,0,1,
0,0,0,1,0,1,1,1,0,0,0,0,0,1,1,1,1,0,1,1,1,0,0,1,1,1,0,0,1,1,
0,0,0,0,0,1,0,0,1,1,0,0,1,1,1,0,0,0,0,0,0,0,0,0 | +| TS1 | 0,0,0,0,1,1,1,1,0,1,1,1,1,0,0,1,1,1,0,1,1,0,1,1,0,0,0,1,1,
1,1,1,0,1,1,0,1,1,0,1,1,0,1,0,1,1,1,1,1,0,0,1,1,0,0,0,1,1,1,
0,0,1,1,1,0,1,1,0,1,1,0,0,0,1,0,0,1,0,0,0,1,1 | 0,0,1,1,1,0,1,0,0,0,0,1,0,0,0,0,0,0,0,1,0,1,1,1,0,0,1,1,0,0,
0,1,1,0,0,1,1,1,0,0,1,0,1,0,1,0,0,1,0,1,0,0,0,1,1,0,1,0,
0,0,0,1,1,1,0,0,1,0,0,0,0,1,1,1,1,0,1,1,0,1,1,1 | +| TS2 | 0,0,0,1,1,0,0,1,0,0,1,1,0,1,1,0,1,0,0,1,0,0,1,1,1,0,1,1,1,
0,1,1,1,1,0,0,0,0,1,0,1,0,1,0,0,1,0,0,1,0,0,1,1,1,0,1,0,1,0,
0,1,0,0,0,0,1,1,0,0,0,1,0,0,0,1,0,0,0,0,1,0,0,0,0,1 | 0,0,1,1,0,0,1,0,0,1,0,1,0,0,0,1,1,1,0,0,0,1,0,0,1,0,0,0,0,0,
1,1,1,0,1,0,1,1,1,0,0,1,1,0,1,0,1,0,0,1,0,1,0,1,1,1,1,0,
1,1,0,0,1,0,0,1,0,0,0,0,0,1,1,0,1,0,0,1,0,1,0,0 | +| TS3 | 0,0,1,1,1,1,0,1,0,1,0,0,0,1,0,1,1,1,0,0,1,1,1,1,0,0,1,0,0,
0,1,0,0,1,0,1,1,0,0,0,0,1,1,1,1,0,0,1,1,1,0,1,0,0,1,0,1,1,
0,1,0,0,1,1,0,1,1,1,0,0,1,1,0,1,0,1,1,1,1,1,1,1,1,1 | 0,0,1,0,1,0,0,0,1,1,0,1,0,1,1,0,1,1,0,0,1,0,1,1,0,0,1,0,0,1,
0,1,1,1,0,0,1,1,1,1,1,1,0,1,0,1,0,1,0,1,0,0,1,0,1,0,1,1,0,1,
1,0,1,1,0,0,1,0,1,1,1,1,1,0,1,1,0,1,1,0,0,0,0,1,0 | +| TS4 | 0,0,1,1,0,0,0,0,0,0,1,1,0,1,0,0,0,0,1,1,0,1,0,1,0,1,1,0,1,
0,0,0,0,0,0,1,0,0,0,1,0,1,0,1,0,0,0,1,1,0,0,1,1,0,0,0,1,0,
1,0,0,1,0,0,0,1,0,1,0,0,1,1,0,0,0,0,0,0,0,1,0,0,1,0 | 0,0,1,1,1,1,0,1,1,1,1,1,0,0,0,1,1,0,1,1,1,0,1,0,1,0,1,1,1,1,
0,1,1,1,0,0,0,0,0,0,0,0,0,0,0,1,1,0,1,1,1,1,0,0,1,0,0,1,0,0,
1,1,0,1,0,0,0,0,1,1,0,1,1,1,0,1,1,1,1,1,1,0,0,0 | +| TS5 | 0,0,1,1,0,0,0,0,0,0,1,1,0,1,0,0,0,0,1,1,0,1,0,1,0,1,1,0,1,
0,0,0,0,0,0,1,0,0,0,1,0,1,0,1,0,0,0,1,1,0,0,1,1,0,0,0,1,0,
1,0,0,1,0,0,0,1,0,1,0,0,1,1,0,0,0,0,0,0,0,1,0,0,1,0 | 0,0,1,1,1,1,0,1,1,1,1,1,0,0,0,1,1,0,1,1,1,0,1,0,1,0,1,1,1,1,
0,1,1,1,0,0,0,0,0,0,0,0,0,0,0,1,1,0,1,1,1,1,0,0,1,0,0,1,0,0,
1,1,0,1,0,0,0,0,1,1,0,1,1,1,0,1,1,1,1,1,1,0,0,0 | +| TS6 | 0,0,1,0,1,1,1,1,0,0,0,0,1,1,0,1,1,1,1,1,0,0,1,1,0,0,0,1,0,
0,1,0,0,0,0,0,1,0,0,0,0,1,0,0,1,0,0,1,0,1,0,1,1,1,1,
0,1,1,0,1,0,0,0,1,1,0,0,1,0,0,0,1,0,0,0,1,0,0,1,0,0 | 0,0,1,1,1,1,0,1,1,0,1,0,0,0,1,0,1,0,0,1,1,0,1,1,0,0,0,0,0,1,
0,0,0,1,0,1,1,1,0,0,0,0,0,1,1,1,1,0,1,1,1,0,0,1,1,1,0,0,1,1,
0,0,0,0,0,1,0,0,1,1,0,0,1,1,1,0,0,0,0,0,0,0,0,0 | +| TS7 | 0,0,0,1,0,1,1,0,0,0,0,1,0,1,1,1,1,1,1,1,0,1,0,1,1,1,1,1,0,
1,1,1,0,0,0,1,0,0,0,0,0,1,1,0,0,1,0,1,0,0,1,0,0,1,0,1,0,0,
0,0,1,0,1,1,1,1,0,1,0,0,1,0,0,1,0,1,1,1,0,1,1,0,0,0,0 | 0,0,1,1,1,0,0,0,0,1,0,1,1,1,1,1,1,0,0,0,1,1,1,0,1,0,0,0,1,1,1,
0,1,0,0,0,1,0,0,0,1,1,1,0,1,1,1,0,1,1,0,0,1,0,1,1,1,0,1,0,1,
1,0,1,0,0,0,0,1,0,0,1,1,1,0,1,1,0,1,0,1,0,0,0,0 | + +## 9.2 Messages for mobility management + +See 3GPP TS 24.008. + +## 9.3 Messages for circuit-switched call control + +See 3GPP TS 24.008. + +## 9.4 GPRS Mobility Management Messages + +See 3GPP TS 24.008. + +## 9.5 GPRS Session Management Messages + +See 3GPP TS 24.008. + +## 9.6 GTTP Messages + +Table 9.6.1 summarises the GTTP messages. + +**Table 9.6.1: GTTP messages** + +| GPRS Transparent Transport messages | Reference | +|--------------------------------------------|------------------| +| GPRS Information | 9.6.1 | + +### 9.6.1 GPRS Information + +This message is sent in acknowledged mode on the main DCCH in order to carry GPRS information in a transparent manner between the mobile station and the network. See table 9.6.2. + +Message type: GPRS Information + Significance: global + Direction: both + +**Table 9.6.2: GPRS Information message content** + +| IEI | Information element | Type / Reference | Presence | Format | length | +|-----|-------------------------------|--------------------------------|----------|--------|--------| +| | GTTP Protocol Discriminator | Protocol Discriminator
10.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
10.3.1 | M | V | 1/2 | +| | GPRS Information Message Type | Message Type
10.4 | M | V | 1 | +| | TLLI | TLLI
10.5.2.41a | M | V | 4 | +| | LLC PDU | LLC PDU Container
10.5.8.1 | M | LV | 2-n | + +#### 9.6.1.1 TLLI + +This information element carries the Temporary Logical Link Identifier. + +#### 9.6.1.2 LLC PDU Container + +This information element carries an LLC PDU with upper layer information. + +# 10 General message format and information elements coding + +The figures and text in this sub-clause describe the Information Elements contents. + +## 10.1 Overview + +Within the RR protocols defined in 3GPP TS 44.018, every message with the exception of the messages sent on the BCCH, downlink CCCH, SCH, EC-SCH, RACH and the HANDOVER ACCESS message, is a standard L3 message as defined in 3GPP TS 24.007. This means that the message consists of the following parts: + +- protocol discriminator; +- skip indicator; +- message type; +- other information elements, as required. + +This organization is illustrated in the example shown in figure 10.1.1. + +![](8d6b56ea28d70ce527efde127103e045_img.jpg) + +| | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|----------------|------------------------|--------------|--|----------------------------------------|--|----------------------------| +| 8      7      6      5      4      3      2      1 | | | | | | | | | +|
Skip Indicator Protocol discriminator
Message type
Other information elements as required
| | Skip Indicator | Protocol discriminator | Message type | | Other information elements as required | | octet 1
octet 2
etc. | +| Skip Indicator | Protocol discriminator | | | | | | | | +| Message type | | | | | | | | | +| Other information elements as required | | | | | | | | | + +**Figure 10.1.1: General message organization example** + +Messages sent on the EC-AGCH are formatted as described in sub-clause 9.1.30c. Messages sent on the EC-BCCH and EC-CCCH use a short message type as described in sub-clause 10.4. All messages sent on the EC-CCCH consist of the following fields in the order listed: + +- Message Type field (4 bits) +- Used DL Coverage Class (2 bits) + +- EC Page Extension (5 bits, except for the EC Dummy message in which case this field is excluded) + +Additional fields (message specific) A mobile station that has enabled EC operation and receives an RR message on downlink EC-CCCH with a message type it does not understand shall still read the Used DL Coverage Class and EC Page Extension fields while ignoring the remaining part of the message. + +Unless specified otherwise in the message descriptions of sub-clause 9, a particular information element shall not be present more than once in a given message. + +The term "default" implies that the value defined shall be used in the absence of any assignment, or that this value allows negotiation of alternative values in between the two peer entities. + +When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. + +When a message is coded using CSN.1 notation, the definition of the CSN.1 syntax in CSN.1 Specification, Version 2.0, shall be used. + +## 10.2 Protocol Discriminator + +The Protocol Discriminator (PD) and its use are defined in 3GPP TS 24.007. + +## 10.3 Skip indicator + +### 10.3.1 Skip indicator + +Bits 5 to 8 of the first octet of every Radio Resource management message and GPRS Transparent Transport protocol message contain the skip indicator. + +When network sharing is in use in a cell, and in the case of the PAGING RESPONSE message, a mobile station supporting network sharing shall encode the skip indicator as described within 3GPP TS 24.008. A supporting network receiving a PAGING RESPONSE message with a skip indicator different from '0000' shall consider the mobile station as supporting network sharing. + +When network sharing is in use in a cell, and in the case of the GPRS Transparent Transport protocol message, a mobile station supporting network sharing may encode the skip indicator different from '0000' (see sub-clause 3.4.26) coded as described within 3GPP TS 24.008. + +For all other cases, a message received with skip indicator different from '0000' shall be ignored. A message received with skip indicator encoded as '0000' shall not be ignored (unless it is ignored for other reasons). A protocol entity sending a Radio Resource management message or GPRS Transparent Transport protocol message shall encode the skip indicator as '0000'. + +## 10.4 Message Type + +The message type IE and its use are defined in 3GPP TS 24.007. Tables 10.4.1 and 10.4.2 define the value part of the message type IE used in the Radio Resource management protocol. Table 10.4.3 defines the value part of the message type IE used in the GPRS Transparent Transport protocol. Table 10.4.4 defines the value part of the message type IE used in the Radio Resource management protocol for messages sent on the EC-BCCH and EC-CCCH. + +**Table 10.4.1: Message types for Radio Resource management** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|---|---|---|---|--------------------------------| +| Channel establishment messages: | | | | | | | | | +| 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | Reserved (see NOTE) | +| 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | ADDITIONAL ASSIGNMENT | +| 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | IMMEDIATE ASSIGNMENT | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | IMMEDIATE ASSIGNMENT EXTENDED | +| 0 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | IMMEDIATE ASSIGNMENT REJECT | +| 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | IMMEDIATE PACKET ASSIGNMENT | +| 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | EC IMMEDIATE ASSIGNMENT TYPE 1 | + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|---|---|---|---|---|---|---|---------------------------------| +| Ciphering messages: | | | | | | | | | +| 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | CIPHERING MODE COMMAND | +| 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | CIPHERING MODE COMPLETE | +| Configuration change messages: | | | | | | | | | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | CONFIGURATION CHANGE COMMAND | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | CONFIGURATION CHANGE ACK. | +| 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | CONFIGURATION CHANGE REJECT | +| Handover messages: | | | | | | | | | +| 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | ASSIGNMENT COMMAND | +| 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | ASSIGNMENT COMPLETE | +| 0 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | ASSIGNMENT FAILURE | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | HANDOVER COMMAND | +| 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | HANDOVER COMPLETE | +| 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | HANDOVER FAILURE | +| 0 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | PHYSICAL INFORMATION | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | Reserved (see NOTE) | +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | Reserved (see NOTE) | +| Channel release messages: | | | | | | | | | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | CHANNEL RELEASE | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | PARTIAL RELEASE | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | PARTIAL RELEASE COMPLETE | +| Paging and Notification messages: | | | | | | | | | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | PAGING REQUEST TYPE 1 | +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | PAGING REQUEST TYPE 2 | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | PAGING REQUEST TYPE 3 | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | PAGING RESPONSE | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | NOTIFICATION/NCH | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | Reserved (see NOTE) | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | NOTIFICATION/RESPONSE | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | Reserved (see NOTE) | +| System information messages: | | | | | | | | | +| 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | SYSTEM INFORMATION TYPE 8 | +| 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | SYSTEM INFORMATION TYPE 1 | +| 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | SYSTEM INFORMATION TYPE 2 | +| 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | SYSTEM INFORMATION TYPE 3 | +| 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | SYSTEM INFORMATION TYPE 4 | +| 0 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | SYSTEM INFORMATION TYPE 5 | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | SYSTEM INFORMATION TYPE 6 | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | SYSTEM INFORMATION TYPE 7 | +| System information messages: | | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | SYSTEM INFORMATION TYPE 2bis | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | SYSTEM INFORMATION TYPE 2ter | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | SYSTEM INFORMATION TYPE 2quater | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | SYSTEM INFORMATION TYPE 5bis | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | SYSTEM INFORMATION TYPE 5ter | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | SYSTEM INFORMATION TYPE 9 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | SYSTEM INFORMATION TYPE 13 | +| System information messages: | | | | | | | | | +| 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | SYSTEM INFORMATION TYPE 16 | +| 0 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | SYSTEM INFORMATION TYPE 17 | +| Miscellaneous messages: | | | | | | | | | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | CHANNEL MODE MODIFY | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | RR STATUS | +| 0 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | CHANNEL MODE MODIFY ACKNOWLEDGE | +| 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | FREQUENCY REDEFINITION | +| 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | MEASUREMENT REPORT | +| 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | CLASSMARK CHANGE | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | CLASSMARK ENQUIRY | +| 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | EXTENDED MEASUREMENT REPORT | +| 0 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | EXTENDED MEASUREMENT ORDER | +| 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | GPRS SUSPENSION REQUEST | +| 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | MBMS ANNOUNCEMENT | +| 0 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | SERVICE INFORMATION | + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|---|---|---|---|---|---|---|-------------------------------------------| +| VGCS uplink control messages: | | | | | | | | | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | VGCS UPLINK GRANT | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | UPLINK RELEASE | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | Reserved (see NOTE) | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | UPLINK BUSY | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | TALKER INDICATION | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | PRIORITY UPLINK REQUEST | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | DATA INDICATION | +| 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | DATA INDICATION 2 | +| Application messages: | | | | | | | | | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | APPLICATION INFORMATION | +| System information messages: | | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | SYSTEM INFORMATION TYPE 14 | +| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | SYSTEM INFORMATION TYPE 15 | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | SYSTEM INFORMATION TYPE 18 | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | SYSTEM INFORMATION TYPE 19 | +| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | SYSTEM INFORMATION TYPE 20 | +| 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | SYSTEM INFORMATION TYPE 13alt | +| 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | SYSTEM INFORMATION TYPE 2n | +| 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | SYSTEM INFORMATION TYPE 21 | +| 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | SYSTEM INFORMATION TYPE 22 | +| 0 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | SYSTEM INFORMATION TYPE 23 | +| DTM control messages: | | | | | | | | | +| 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | DTM ASSIGNMENT FAILURE | +| 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | DTM REJECT | +| 0 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | DTM REQUEST | +| 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | PACKET ASSIGNMENT | +| 0 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | DTM ASSIGNMENT COMMAND | +| 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | DTM INFORMATION | +| 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | PACKET NOTIFICATION | +| Inter RAT specific messages: | | | | | | | | | +| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | UTRAN CLASSMARK CHANGE | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | CDMA 2000 CLASSMARK CHANGE | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | INTER SYSTEM TO UTRAN HANDOVER COMMAND | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | INTER SYSTEM TO CDMA2000 HANDOVER COMMAND | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | GERAN IU MODE CLASSMARK CHANGE | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | INTER SYSTEM TO E-UTRAN HANDOVER COMMAND | + +Bit 8 is reserved for possible future use as an extension bit, see 3GPP TS 24.007. + +NOTE This value was allocated but never used in earlier phases of the protocol. + +**Table 10.4.2: Message types for Radio Resource management messages using the RR short protocol discriminator** + +| 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|--------------------------------------| +| 0 | 0 | 0 | 0 | 0 | System Information Type 10 | +| 0 | 0 | 0 | 0 | 1 | Notification/FACCH | +| 0 | 0 | 0 | 1 | 0 | Uplink Free | +| 0 | 0 | 1 | 0 | 0 | Enhanced Measurement Report (uplink) | +| 0 | 0 | 1 | 0 | 1 | Measurement Information (downlink) | +| 0 | 0 | 1 | 1 | 0 | VBS/VGCS Reconfigure | +| 0 | 0 | 1 | 1 | 1 | VBS/VGCS Reconfigure2 | +| 0 | 1 | 0 | 0 | 0 | VGCS Additional Information | +| 0 | 1 | 0 | 0 | 1 | VGCS SMS Information | +| 0 | 1 | 0 | 1 | 0 | System Information Type 10bis | +| 0 | 1 | 0 | 1 | 1 | System Information Type 10ter | +| 0 | 1 | 1 | 0 | 0 | VGCS Neighbour Cell Information | +| 0 | 1 | 1 | 0 | 1 | Notify Application Data | + +**Table 10.4.3: Message types for GTTP messages** + +| Message type | Message | +|-----------------|------------------| +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | GPRS Information | + +**Table 10.4.4: Message types for Radio Resource management on EC-BCCH and EC-CCCH** + +| 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|--------------------------------| +| Channel establishment messages: | | | | | +| 0 | 0 | 0 | 1 | EC IMMEDIATE ASSIGNMENT TYPE 2 | +| 0 | 0 | 1 | 0 | EC IMMEDIATE ASSIGNMENT REJECT | +| 0 | 0 | 1 | 1 | EC DUMMY | +| 0 | 1 | 0 | 0 | EC DOWNLINK ASSIGNMENT | +| 0 | 1 | 0 | 1 | EC IMMEDIATE ASSIGNMENT TYPE 3 | +| 0 | 1 | 1 | 0 | EC DOWNLINK ASSIGNMENT TYPE 2 | +| 0 | 1 | 1 | 1 | EC IMMEDIATE ASSIGNMENT TYPE 4 | +| Paging messages: | | | | | +| 1 | 0 | 0 | 1 | EC PAGING REQUEST | +| System information messages: | | | | | +| 3 | 2 | 1 | | | +| 0 | 0 | 1 | | EC-SYSTEM INFORMATION TYPE 1 | +| 0 | 1 | 0 | | EC-SYSTEM INFORMATION TYPE 2 | +| 0 | 1 | 1 | | EC-SYSTEM INFORMATION TYPE 3 | +| 1 | 0 | 0 | | EC-SYSTEM INFORMATION TYPE 4 | + +**Table 10.4.5: Message types for Radio Resource management on EC-PICH** + +| 4 | 3 | 2 | 1 | | +|----------------------------|---|---|---|----------------------| +| Paging Indication message: | | | | | +| 1 | 0 | 0 | 0 | EC PAGING INDICATION | + +## 10.5 Other information elements + +The different formats (V, LV, T, TV, TLV) and the four categories of information elements (type 1, 2, 3, and 4) are defined in 3GPP TS 24.007. + +The first octet of an information element in the non-imperative part contains the IEI of the information element. If this octet does not correspond to an IEI known in the message, the receiver shall determine whether this IE is of type 1 or 2 (i.e. it is an information element of one octet length) or an IE of type 4 (i.e. that the next octet is the length indicator indicating the length of the remaining of the information element) (see 3GPP TS 24.007). + +This allows the receiver to jump over unknown information elements and to analyse any following information elements. + +The information elements which are common for at least two of the three protocols Radio Resources management, Mobility Management and Call Control, are listed in 3GPP TS 24.008. + +The information elements for the protocols Radio Resources management are listed in sub-clause 10.5.2. Default information element identifiers are listed in annex K. + +NOTE: Different information elements may have the same default information element identifier if they belong to different protocols. + +The descriptions of the information element types in sub-clause 10.5.2 are organized in alphabetical order of the IE types. Each IE type is described in one sub-clause. + +The sub-clause may have an introduction: + +- possibly explaining the purpose of the IE; +- possibly describing whether the IE belongs to type 1, 2, 3, 4 or 5; +- possibly indicating the length that the information element has if it is either type 5 or if it is used in format TV (type 1 and 3) or TLV (type 4). + +A figure of the sub-clause defines the structure of the IE indicating: + +- possibly the position and length of the IEI. (However it depends on the message in which the IE occurs whether the IE contains an IEI.); +- the fields the IE value part is composed of; +- possibly the position and length of the length indicator. (However it depends on the IE type whether the IE contains a length indicator or not.); +- possibly octet numbers of the octets that compose the IE (see sub-clause a) below). + +Finally, the sub-clause contains tables defining the structure and value range of the fields that compose the IE value part. The order of appearance for information elements in a message is defined in clause 9. + +The order of the information elements within the imperative part of messages has been chosen so that information elements with 1/2 octet of content (type 1) go together in succession. The first type 1 information element occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N + 1 etc. If the number of type 1 information elements is odd then bits 5 to 8 of the last octet occupied by these information elements contains a spare half octet IE in format V. + +Where the description of information elements in this Technical Specification contains bits defined to be "spare bits", these bits shall set to the indicated value (0 or 1) by the sending side, and their value shall be ignored by the receiving side. With few exceptions, spare bits are indicated as being set to "0" in 3GPP TS 44.018. + +The following rules apply for the coding of type 4 information elements: + +- The octet number of an octet (which is defined in the figure of a sub-clause) consists of a positive integer, possibly of an additional letter, and possibly of an additional asterisk, see sub-clause f). The positive integer identifies one octet or a group of octets. +- Each octet group is a self contained entity. The internal structure of an octet group may be defined in alternative ways. +- An octet group is formed by using some extension mechanism. The preferred extension mechanism is to extend an octet (N) through the next octet(s) (Na, Nb, etc.) by using bit 8 in each octet as an extension bit. + +The bit value "0" indicates that the octet group continues through to the next octet. The bit value "1" indicates that this octet is the last octet of the group. If one octet (Nb) is present, the preceding octets (N and Na) shall also be present. + +In the format descriptions appearing in sub-clause 10.5.1 to 10.5.4, bit 8 is marked "0/1 ext" if another octet follows. Bit 8 is marked "1 ext" if this is the last octet in the extension domain. + +Additional octets may be defined in later versions of the protocols ("1 ext" changed to "0/1 ext") and equipments shall be prepared to receive such additional octets; the contents of these octets shall be ignored. However the length indicated in clauses 9 and 10 only takes into account this version of the protocols. + +- In addition to the extension mechanism defined above, an octet (N) may be extended through the next octet(s) (N+1, N+2 etc.) by indications in bits 7-1 (of octet N). +- The mechanisms in c) and d) may be combined. +- Optional octets are marked with asterisks (\*). + +### 10.5.1 Common information elements. + +#### 10.5.1.0 General + +The content of the common information elements identified below is specified in the corresponding sub-clauses in 3GPP TS 24.008. + +##### 10.5.1.1 Cell identity + +See 3GPP TS 24.008. + +##### 10.5.1.2 Ciphering Key Sequence Number + +See 3GPP TS 24.008. + +#### 10.5.1.3 Location Area Identification + +See 3GPP TS 24.008. + +##### 10.5.1.4 Mobile Identity + +See 3GPP TS 24.008. + +##### 10.5.1.5 Mobile Station Classmark 1 + +See 3GPP TS 24.008. + +#### 10.5.1.6 Mobile Station Classmark 2 + +See 3GPP TS 24.008. + +#### 10.5.1.7 Mobile Station Classmark 3 + +See 3GPP TS 24.008. + +#### 10.5.1.8 Spare Half Octet + +See 3GPP TS 24.008. + +#### 10.5.1.9 Descriptive group or broadcast call reference + +See 3GPP TS 24.008. + +#### 10.5.1.10 Group Cipher Key Number + +See 3GPP TS 24.008. + +##### 10.5.1.10a (void) + +##### 10.5.1.11 (void) + +##### 10.5.1.12 (void) + +##### 10.5.1.13 (void) + +### 10.5.2 Radio Resource management information elements. + +#### 10.5.2.1a BA Range + +The purpose of the BA Range information element is to provide the mobile station with ARFCN range information which can be used in the cell selection procedure. + +The BA Range information element is coded as shown in figure 10.5.21a.1 and table 10.5.2.1a.1. + +The BA Range is a type 4 information element with a minimum length of 6 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|-----------------------------|------------------------------|---|---|-----------------------------|------------------------------|---|---|----------|--|--|--| +| | BA RANGE IEI | | | | | | | octet 1 | | | | +| | Length of BA Range contents | | | | | | | octet 2 | | | | +| | Number of Ranges | | | | | | | octet 3 | | | | +| | RANGE1_LOWER (high part) | | | | | | | octet 4 | | | | +| RANGE1_LOWER
(low part) | RANGE1_HIGHER
(high part) | | | | | | | octet 5 | | | | +| RANGE1_HIGHER
(low part) | | | | RANGE2_LOWER
(high part) | | | | octet 6 | | | | +| RANGE2_LOWER
(low part) | | | | | RANGE2_HIGHER
(high part) | | | octet 7 | | | | +| RANGE2_HIGHER (low part) | | | | | | | | octet 8 | | | | +| RANGE3_LOWER (high part) | | | | | | | | octet 9 | | | | +| RANGE3_LOWER
(low part) | RANGE3_HIGHER
(high part) | | | | | | | octet 10 | | | | +| RANGE3_HIGHER
(low part) | | | | RANGE4_LOWER
(high part) | | | | octet 11 | | | | +| RANGE4_LOWER
(low part) | | | | | RANGE4_HIGHER
(high part) | | | octet 12 | | | | +| RANGE4_HIGHER (low part) | | | | | | | | octet 13 | | | | +| | | | | | | | | octet n | | | | + +Figure 10.5.21a.1: BA RANGE information element + +Table 10.5.21a.1: BA Range information element + +##### **Number of Ranges parameter** + +The number of Ranges parameter indicates in binary the number of ranges to be transmitted in the IE. It shall have a minimum value of 1. + +##### **RANGEi\_LOWER** + +If \$(impr-BA-range-handling)\$ is not supported: + +\$begin + +The RANGEi\_LOWER is coded as the binary representation of the ARFCN used as the lower limit of a range of frequencies to be used by the mobile station in cell selection (see 3GPP TS 45.008 and 3GPP TS 23.022) + +\$end + +If \$(impr-BA-range-handling)\$ is supported: + +\$begin + +The RANGEi\_LOWER is coded as the binary representation of the ARFCN used as the lower limit of a range of frequencies which could be used by the mobile station in cell selection (see 3GPP TS 45.008 and 3GPP TS 23.022) + +\$end + +##### **RANGEi\_HIGHER** + +If \$(impr-BA-range-handling)\$ is not supported: + +\$begin + +The RANGEi\_HIGHER is coded as the binary representation of the ARFCN used as the higher limit of a range of frequencies to be used by the mobile station in cell selection (see 3GPP TS 45.008 and 3GPP TS 23.022) + +\$end + +If \$(impr-BA-range-handling)\$ is supported: + +\$begin + +The RANGEi\_HIGHER is coded as the binary representation of the ARFCN used as the higher limit of a range of frequencies which could be used by the mobile station in cell selection (see 3GPP TS 45.008 and 3GPP TS 23.022) + +\$end + +If the length of the BA range information element is greater than the number of octets required to carry the Number of Ranges given in octet 3, then any unused octets or parts of octets at the end of the IE shall be considered as spare. + +If \$(impr-BA-range-handling)\$ is supported: + +If a mobile station receives range information which has ranges or part of the ranges which are not supported by the mobile station, the mobile station shall take into account those parts of the ranges which it does support. + +#### 10.5.2.1b Cell Channel Description + +The purpose of the *Cell Channel Description* information element is to provide the reference frequency list to be used to decode the mobile allocation information element. + +The *Cell Channel Description* is a type 3 information element with 17 octets length. + +There are several formats for the *Cell Channel Description* information element, distinguished by the "format indicator" subfield. Some formats are frequency bit maps, the others use a special encoding scheme. + +NOTE: No more than 64 RF channels should be encoded in the Cell Allocation since this is the maximum number of RF channels which can be referenced in the Mobile Allocation IE. + +##### 10.5.2.1b.1 General description + +Figure 10.5.2.1b.1.1 shows only a special bit numbering. The different general format is described in table 10.5.2.1b.1.1. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---------|---------|---------|---------|---------|---------|---------|----------| +| Cell Channel Description IEI | | | | | | | | octet 1 | +| Bit 128 | Bit 127 | 0 spare | 0 spare | Bit 124 | Bit 123 | Bit 122 | Bit 121 | octet 2 | +| Bit 120 | Bit 119 | Bit 118 | Bit 117 | Bit 116 | Bit 115 | Bit 114 | Bit 113 | octet 3 | +| | | | | | | | | | +| Bit 008 | Bit 007 | Bit 006 | Bit 005 | Bit 004 | Bit 003 | Bit 002 | Bit 001 | octet 17 | + +Figure 10.5.2.1b.1.1: *Cell Channel Description* information element (general format) + +**Table 10.5.2.1b.1.1: Cell Channel Description information element, general format** + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------|------------|------------|------------|------------|------------------------| +| FORMAT-ID , Format Identifier (Bit 128 and next) | | | | | | +| The different formats are distinguished by the bits of higher number. The possible values are the following: | | | | | | +| Bit | Bit | Bit | Bit | Bit | format notation | +| 128 | 127 | 124 | 123 | 122 | | +| 0 | 0 | X | X | X | bit map 0 | +| 1 | 0 | 0 | X | X | 1024 range | +| 1 | 0 | 1 | 0 | 0 | 512 range | +| 1 | 0 | 1 | 0 | 1 | 256 range | +| 1 | 0 | 1 | 1 | 0 | 128 range | +| 1 | 0 | 1 | 1 | 1 | variable bit map | +| All other combinations are reserved for future use. | | | | | | + +A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may consider all values except the value for bit map 0 as reserved. + +The significance of the remaining bits depends on the FORMAT-ID. The different cases are specified in the next sub-clauses. + +Mobile stations shall treat all ARFCNs in the set {0, 1, 2 ... 1023} as valid ARFCN values even if the mobile station is unable to transmit or receive on that ARFCN. + +##### 10.5.2.1b.2 Bit map 0 format + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|-------|-------|-------|-------|-------|-------|-------|----------| +| Cell Channel Description IEI | | | | | | | | octet 1 | +| 0 | 0 | 0 | 0 | CA | CA | CA | CA | octet 2 | +| FORMAT-ID | | spare | spare | ARFCN | ARFCN | ARFCN | ARFCN | | +| | | | | 124 | 123 | 122 | 121 | | +| CA | CA | CA | CA | CA | CA | CA | CA | octet 3 | +| ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | | +| 120 | 119 | 118 | 117 | 116 | 115 | 114 | 113 | | +| | | | | | | | | | +| CA | CA | CA | CA | CA | CA | CA | CA | octet 17 | +| ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | | +| 008 | 007 | 006 | 005 | 004 | 003 | 002 | 001 | | + +**Figure 10.5.2.1b.2.1: Cell Channel Description information element, bit map 0 format****Table 10.5.2.1b.2.1: Cell channel Description information element, bit map 0 format** + +| | +|---------------------------------------------------------------------------------------------------------------------------------| +| CA ARFCN N , Cell Allocation Absolute RF Channel Number N (octet 2 etc.) | +| For a RF channel with ARFCN = N belonging to the cell allocation the CA ARFCN N bit is coded with a "1"; N = 1, 2, ... , 124. | +| For a RF channel with ARFCN = N not belonging to the cell allocation the CA ARFCN N bit is coded with a "0"; N = 1, 2 .. , 124. | + +##### 10.5.2.1b.3 Range 1024 format + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | +|------------------------------|---------------------|---------------------|-------------------|-------------------|----------------------|---------------------|---------------|----------|--|--|--|--|--|--|--|--|--|--|--|--| +| Cell Channel Description IEI | | | | | | | | octet 1 | | | | | | | | | | | | | +| 1 | 0 | 0 | 0 | 0 | F0 | W(1)
(high part) | | octet 2 | | | | | | | | | | | | | +| FORMAT-ID | | | | | | | | octet 2 | | | | | | | | | | | | | +| spare | | | | | | | | octet 3 | | | | | | | | | | | | | +| W(1) (low part) | | | | | | | | octet 4 | | | | | | | | | | | | | +| W(2) (high part) | | | | | | | | octet 5 | | | | | | | | | | | | | +| W(2)
(low) | W(3)
(high part) | | | | | | | octet 6 | | | | | | | | | | | | | +| W(3)
(low part) | | W(4)
(high part) | | | | | | octet 7 | | | | | | | | | | | | | +| W(4)
(low part) | | W(5)
(high part) | | | | | | octet 8 | | | | | | | | | | | | | +| W(5)
(low part) | | W(6)
(high part) | | | | | | octet 9 | | | | | | | | | | | | | +| W(6)
(low part) | | W(7)
(high part) | | | | | | octet 10 | | | | | | | | | | | | | +| W(7)
(low part) | | W(8)
(high part) | | | | | | octet 11 | | | | | | | | | | | | | +| W(8)
(low) | W(9) | | | | | | | octet 12 | | | | | | | | | | | | | +| W(10) | | | | | | | W(11)
high | octet 13 | | | | | | | | | | | | | +| W(11)
(low part) | | | | | W(12)
(high part) | | | octet 14 | | | | | | | | | | | | | +| W(12) (low part) | | | | W(13) (high part) | | | | octet 15 | | | | | | | | | | | | | +| W(13) (low part) | | | W(14) (high part) | | | | | octet 16 | | | | | | | | | | | | | +| W(14) (low part) | | W(15) (high part) | | | | | | octet 17 | | | | | | | | | | | | | +| W(15)
(low part) | W(16) | | | | | | | | | | | | | | | | | | | | + +Figure 10.5.2.1b.3.1: **Cell Channel Description** information element (1024 range format) + +Table 10.5.2.1b.3.1: **Cell Channel Description** information element, range 1024 format + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| F0, frequency 0 indicator (octet 2, bit 3): | +| 0 ARFCN 0 is not a member of the set | +| 1 ARFCN 0 is a member of the set | +| W(i), i from 1 to 16 (octet 2 to 17): | +| Each W(i) encodes a non negative integer in binary format. | +| If W(k) is null, W(k+1) to W(16) must be null also. | +| Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.3. | + +##### 10.5.2.1b.4 Range 512 format + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | +|------------------------------|------------------|------------------|-------|-------------------|---|-------------------|-----------------|----------|--|--|--|--|--|--| +| Cell Channel Description IEI | | | | | | | | octet 1 | | | | | | | +| 1 | 0 | 0 | 0 | 1 | 0 | 0 | ORIG-ARFCN high | octet 2 | | | | | | | +| FORMAT-ID | | | | | | | | octet 3 | | | | | | | +| ORIG-ARFCN (middle part) | | | | | | | | octet 4 | | | | | | | +| ORIG-ARFCN low | W(1) (high part) | | | | | | | octet 5 | | | | | | | +| W(1) (low part) | | W(2) (high part) | | | | | | octet 6 | | | | | | | +| W(2) (low part) | | W(3) (high part) | | | | | | octet 7 | | | | | | | +| W(3) (low part) | | W(4) (high part) | | | | | | octet 8 | | | | | | | +| W(4) low | W(5) | | | | | | | octet 9 | | | | | | | +| W(6) | | | | | | | | octet 10 | | | | | | | +| W(7) (low part) | | | | | | W(8) (high part) | | octet 11 | | | | | | | +| W(8) (low part) | | | | W(9) (high part) | | | | octet 12 | | | | | | | +| W(9) (low part) | | W(10) | | | | | | octet 13 | | | | | | | +| W(11) | | | | | | W(12) (high part) | | octet 14 | | | | | | | +| W(12) (low part) | | | | W(13) (high part) | | | | octet 15 | | | | | | | +| W(13) (low part) | | W(14) | | | | | | octet 16 | | | | | | | +| W(15) | | | | | | W(16) (high part) | | octet 17 | | | | | | | +| W(16) (low part) | | | W(17) | | | | | | | | | | | | + +Figure 10.5.2.1b.4.1: **Cell Channel Description information element (512 range format)** + +Table 10.5.2.1b.4.1: **Cell Channel Description information element, range 512 format** + +**ORIG-ARFCN**, origin ARFCN (octet 2, 3 and 4) + +This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. + +W(i), i from 1 to 17 (octet 4 to 17): + +Each W(i) encodes a non negative integer in binary format. + +If W(k) is null, W(k+1) to W(17) must be null also. + +Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.4. + +##### 10.5.2.1b.5 Range 256 format + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---------------------|--------------|------------------|-------------------|----------------|----------------------|------------------------|----------| +| Cell Channel Description IEI | | | | | | | | octet 1 | +| 1 0
FORMAT-ID | | 0 0
spare | | 1 | 0
FORMAT-ID | 1 | ORIG-
ARFCN
high | octet 2 | +| ORIG-ARFCN (middle part) | | | | | | | | octet 3 | +| ORIG-
ARFCN
low | W(1)
(high part) | | | | | | | octet 4 | +| W(1)
(low) | W(2) | | | | | | | octet 5 | +| W(3) | | | | | | | W(4)
high | octet 6 | +| W(4) (low part) | | | | W(5) (high part) | | | | octet 7 | +| W(5) (low part) | | | W(6) (high part) | | | | | octet 8 | +| W(6)
low | W(7) | | | | | | W(8)
high | octet 9 | +| W(8) (low part) | | | | W(9) (high part) | | | | octet 10 | +| W(9)
low | W(10) | | | | | W(11)
(high part) | | octet 11 | +| W(11) (low part) | | | W(12) | | | | | octet 12 | +| W(13) | | | | W(14) (high part) | | | | octet 13 | +| W(14)
low | W(15) | | | | | | W(16)
high | octet 14 | +| W(16)
(low part) | | | W(17) | | | | W(18)
high | octet 15 | +| W(18)
(low part) | | | W(19) | | | | W(20)
high | octet 16 | +| W(20)
(low part) | | | W(21) | | | | 0
spare | octet 17 | + +Figure 10.5.2.1b.5.1: **Cell Channel Description** information element, range 256 formatTable 10.5.2.1b.5.1: **Cell Channel Description** information element, range 256 format + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ORIG-ARFCN, origin ARFCN (octet 2, 3 and 4)

This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element.

W(i), i from 1 to 21 (octet 4 to 17):

Each W(i) encodes a non negative integer in binary format.

If W(k) is null, W(k+1) to W(21) must be null also.

Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.5.

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### 10.5.2.1b.6 Range 128 format + +![](93bd00a00fa28558486f0664550699b1_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|-------|-------|-------|------------------|---|-------------------|-----------------|----------| +| Cell Channel Description IEI | | | | | | | | octet 1 | +| 1 | 0 | 0 | 0 | 1 | 1 | 0 | ORIG-ARFCN high | octet 2 | +| FORMAT-ID spare spare FORMAT-ID | | | | | | | | | +| ORIG-ARFCN (middle part) | | | | | | | | octet 3 | +| ORIG-ARFCN low | W(1) | | | | | | | octet 4 | +| W(2) | | | | W(3) | | | | octet 5 | +| W(3) (low part) | | | | W(4) (high part) | | | | octet 6 | +| W(4) low | W(5) | | | W(6) (high part) | | | | octet 7 | +| W(6) (low part) | | | W(7) | | | | | octet 8 | +| W(8) | | | | W(9) | | | | octet 9 | +| W(10) | | | | W(11) | | | | octet 10 | +| W(12) | | | | W(13) | | | | octet 11 | +| W(14) | | | | W(15) | | | | octet 12 | +| W(16) | | | W(17) | | | W(18) (high part) | | octet 13 | +| W(18) low | W(19) | | W(20) | | | W(21) high | | octet 14 | +| W(21) (low part) | | W(22) | | W(23) | | | | octet 15 | +| W(24) | | | W(25) | | | W(26) (high part) | | octet 16 | +| W(26) low | W(27) | | W(28) | | | 0 spare | | octet 17 | + +**Figure 10.5.2.1b.6.1: Cell Channel Description information element, range 128 format** + +**Table 10.5.2.1b.6.1: Cell Channel Description information element, range 128 format** + +**ORIG-ARFCN**, origin ARFCN (octet 2, 3 and 4) + +This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. + +W(i), i from 1 to 28 (octet 4 to 17): + +Each W(i) encodes a non negative integer in binary format. + +If W(k) is null, W(k+1) to W(28) must be null also. + +Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.6. + +##### 10.5.2.1b.7 Variable bit map format + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|--------------|--------------|--------------|--------------|--------------|--------------|-----------------------|----------| +| Cell Channel Description IEI | | | | | | | | octet 1 | +| 1 | 0 | 0 | 0 | 1 | 1 | 1 | ORIG
ARFCN
high | octet 2 | +| FORMAT-ID | | spare | spare | FORMAT-ID | | | | | +| ORIG-ARFCN
(middle part) | | | | | | | | octet 3 | +| ORIG-
ARFCN
low | RRFCN
1 | RRFCN
2 | RRFCN
3 | RRFCN
4 | RRFCN
5 | RRFCN
6 | RRFCN
7 | octet 4 | +| | | | | | | | | | +| RRFCN
104 | RRFCN
105 | RRFCN
106 | RRFCN
107 | RRFCN
108 | RRFCN
109 | RRFCN
110 | RFCN
111 | octet 17 | + +**Figure 10.5.2.1b.7.1: Cell Channel Description information element, variable bit map format** + +**Table 10.5.2.1b.7.1: Cell Channel Description information element, variable bit map format** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ORIG-ARFCN, origin ARFCN (octet 2, 3 and 4)

This field encodes the ARFCN of one frequency belonging to the set. This value is also used as origin of the bit map to generate all other frequencies.

RRFCN N, relative radio frequency channel number N (octet 4 etc.)

For a RF channel with ARFCN = (ORIG-ARFCN + N) \bmod 1024 belonging to the set, RRFCN N bit is coded with a "1"; N = 1, 2, .. , 111

For a RF channel with ARFCN = (ORIG-ARFCN + N) \bmod 1024 not belonging to the set, RRFCN N bit is coded with a "0"; N = 1, 2, .. , 111

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 10.5.2.1c BA List Pref + +The purpose of the BA List Pref information element is to provide the mobile station with ARFCN information which can be used in the cell selection/reselection procedure. + +The BA List Pref is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< BA List Pref > ::=   < LENGTH OF BA LIST PREF : bit (8) >   {1 < RANGE LIMITS >}**0   {1 < BA FREQ : bit (10) >}**0   < spare padding >; < RANGE LIMITS > ::=   < RANGE LOWER : bit (10) >   < RANGE UPPER : bit (10) >;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +The RANGE LOWER is coded as the binary representation of the ARFCN used as the lower limit of a range of frequencies to be used by the mobile station in cell selection and reselection (see 3GPP TS 45.008 and 3GPP TS 23.022). + +The RANGE HIGHER is coded as the binary representation of the ARFCN used as the higher limit of a range of frequencies to be used by the mobile station in cell selection and reselection (see 3GPP TS 45.008 and 3GPP TS 23.022). + +BA FREQ is coded as the binary representation of the ARFCN indicating a single frequency to be used by the mobile station in cell selection and reselection (see 3GPP TS 45.008 and 3GPP TS 23.022). + +##### 10.5.2.1d UTRAN Freq List + +The UTRAN Freq List information element provides the mobile station with a list of UTRAN frequencies used by the network. These frequencies may be used in the cell selection procedure, see 3GPP TS 25.304. + +FDD\_ARFCN and TDD\_ARFCN are defined as the UARFCN in 3GPP TS 25.101 and 3GPP TS 25.102. If both an UTRAN Freq List information element and an UTRAN Frequency List Description struct (3GPP TS 44.060) are received, the mobile station shall use the one most recently received. + +The UTRAN Freq List is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +``` +< UTRAN Freq List >:= + < LENGTH OF UTRAN FREQ LIST : bit (8) > -- length following in octets + { 1 < FDD_ARFCN > : bit (14) } ** 0 -- FDD frequencies + { 1 < TDD_ARFCN > : bit (14) } ** 0 -- TDD frequencies + < spare bit >**; +``` + +Spare bits in the end of the field are used to fill the last octet. + +##### 10.5.2.1e Cell selection indicator after release of all TCH and SDCCH IE + +This IE indicates on which frequency/cell the cell selection after channel release shall be performed. + +The "Cell selection indicator after release of all TCH and SDCCH" information element is coded as shown in figure 10.5.2.1e.1 and tables 10.5.2.1e.1 and 10.5.2.1e.2. + +The "Cell selection indicator after release of all TCH and SDCCH" is a type 4 information element with a minimum length of 4 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Cell selection indicator after release of all TCH and SDCCH IEI | | | | | | | | octet 1 | +| Length of Cell selection indicator after release of all TCH and SDCCH value part | | | | | | | | octet 2 | +| Cell selection indicator after release of all TCH and SDCCH value part | | | | | | | | octet 3 - n | + +**Figure 10.5.2.1e.1: Cell selection indicator after release of all TCH and SDCCH information element** + +**Table 10.5.2.1e.1: Cell selection indicator after release of all TCH and SDCCH value part** + +``` + + ::= + { + 000 { 1 > } ** 0 + | 001 { 1 > } ** 0 + | 010 { 1 > } ** 0 + | 011 { 1 > } ** 0 }; + +< GSM Description struct > ::= + < Band_Indicator : bit > + < ARFCN : bit (10) > + < BSIC : bit (6) > ; + +< UTRAN FDD Description struct > ::= + { 0 | 1 < Bandwidth_FDD : bit (3) > } + < FDD-ARFCN : bit (14) > + { 0 | 1 < FDD_Indic0 : bit > + < NR_OF_FDD_CELLS : bit (5) > + < FDD_CELL_INFORMATION Field : bit (p(NR_OF_FDD_CELLS)) > }; + -- p(x) defined in table 9.1.54.1 + +< UTRAN TDD Description struct > ::= + { 0 | 1 < Bandwidth_TDD : bit (3) > } + < TDD-ARFCN : bit (14) > + { 0 | 1 < TDD_Indic0 : bit > + < NR_OF_TDD_CELLS : bit (5) > + < TDD_CELL_INFORMATION Field : bit (q(NR_OF_TDD_CELLS)) > }; + -- q(x) defined in table 9.1.54.1 + +< E-UTRAN Description struct > ::= + < EARFCN : bit (16) > + { 0 | 1 < Measurement Bandwidth : bit (3) > } + { 0 | 1 < Not Allowed Cells: < PCID Group IE > > } + { 0 | 1 < TARGET_PCID : bit (9) > }; + +``` + +**Table 10.5.2.1e.2: Cell selection indicator after release of all TCH and SDCCH value part details** + +**Band\_Indicator** (1 bit field) + +| | | +|----------|---------------------------| +| 0 | ARFCN indicates 1800 band | +| 1 | ARFCN indicates 1900 band | + +The band indicator for 1800 and 1900 associates the ARFCN channel numbers to the DCS 1800 respectively to the PCS 1900 band, see 3GPP TS 45.005. + +**ARFCN** (10 bit field) + The ARFCN is coded as the binary representation of the absolute RF channel number. + +Range 0 to 1023 + +**BSIC** (6 bit field) + The BSIC field is coded as the "Base Station Identity Code" defined in 3GPP TS 23.003. + +Range 0 to 63 + +**UTRAN FDD DESCRIPTION** + For detailed element definitions see the Measurement Information message. + +##### **UTRAN TDD DESCRIPTION** + +For detailed element definitions see the Measurement Information message. + +##### **E-UTRAN description** + +For detailed element definitions see the Measurement Information message + +##### **TARGET\_PCID** (9 bit field) + +This field specifies the physical layer cell identity of the target cell (see 3GPP TS 36.211). + +#### 10.5.2.2 Cell Description + +The purpose of the *Cell Description* information element is to provide a minimum description of a cell, e.g. to allow the mobile station to use its pre-knowledge about synchronization. + +The *Cell Description* information element is coded as shown in figure 10.5.2.2.1 and table 10.5.2.2.1. + +The *Cell Description* is a type 3 information element with 3 octets length. + +![](45580ccf627a95d8c2bb3f03bf9fa0dd_img.jpg) + +| | | | | | | | | | +|---------------------------|---|-----|---|---|-----|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Cell Description IEI | | | | | | | | octet 1 | +| BCCH ARFCN
(high part) | | NCC | | | BCC | | | octet 2 | +| BCCH ARFCN (low part) | | | | | | | | octet 3 | + +**Figure 10.5.2.2.1: *Cell Description* information element** + +**Table 10.5.2.2.1: *Cell Description* information element** + +##### **NCC**, PLMN colour code (octet 2) + +The NCC field is coded as the binary representation of the PLMN colour code (see 3GPP TS 23.003). + +##### **BCC**, BS colour code (octet 2) + +The BCC field is coded as the binary representation of the BS colour code (see 3GPP TS 23.003). + +##### **BCCH ARFCN** (octet 2, bits 7 and 8, and octet 3) + +The BCCH ARFCN number field is coded as the binary representation of the BCCH carriers absolute RF channel number. + +Range: 0 to 1023 + +#### 10.5.2.3 Cell Options (BCCH) + +The purpose of the *Cell Options (BCCH)* information element is to provide a variety of information about a cell. + +The *Cell Options (BCCH)* information element is coded as shown in figure 10.5.2.3.1 and table 10.5.2.3a.1. + +The *Cell Options (BCCH)* is a type 3 information element with 2 octets length. + +![](c0433bf641e79edba72eb47f584894cb_img.jpg) + +| | | | | | | | | | +|-------------------------|------|-----|---|--------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Cell Options (BCCH) IEI | | | | | | | | octet 1 | +| DN-IND | PWRC | DTX | | RADIO-LINK-TIMEOUT | | | | octet 2 | + +**Figure 10.5.2.3.1: *Cell Options (BCCH)* information element** + +**Table 10.5.2.3.1: Cell Options (BCCH) information element** + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| PWRC Power control indicator (octet 2) Note 1
Bit
7
0 PWRC is not set
1 PWRC is set | | +| DTX, DTX indicator (octet 2) Note 3
Bit
6 5
0 0 The MSs may use uplink discontinuous transmission
0 1 The MSs shall use uplink discontinuous transmission
1 0 The MS shall not use uplink discontinuous transmission | | +| RADIO-LINK_TIMEOUT (octet 2) Note 2
Bits
4 3 2 1
0 0 0 0 4
0 0 0 1 8
0 0 1 0 12
:
1 1 1 0 60
1 1 1 1 64 | | +| DN-TND, Dynamic ARFCN mapping indicator (octet 2) Note 4
Bit
8
0 Dynamic ARFCN mapping is not used by the PLMN
1 Dynamic ARFCN mapping is used by the PLMN | | + +NOTE 1: The precise meaning of the PWRC parameter can be found in 3GPP TS 45.008. + +NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in 3GPP TS 45.008. + +NOTE 3: The DTX indicator field is not related to the use of downlink discontinuous transmission. + +NOTE 4: Dynamic ARFCN mapping is specified in 3GPP TS 45.005. + +##### 10.5.2.3a Cell Options (SACCH) + +The purpose of the *Cell Options* (SACCH) information element is to provide a variety of information about a cell. + +The *Cell Options* (SACCH) information element is coded as shown in figure 10.5.2.3a.1 and table 10.5.2.3a.2. + +The *Cell Options* (SACCH) is a type 3 information element with 2 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|--------------------------|-----|---|--------------------|---|---|---|---------| +| | Cell Options (SACCH) IEI | | | | | | | octet 1 | +| DTX | PWRC | DTX | | RADIO-LINK-TIMEOUT | | | | octet 2 | + +**Figure 10.5.2.3a.1: Cell Options (SACCH) information element** + +Table 10.5.2.3a.1: (void) + +Table 10.5.2.3a.2: *Cell Options (SACCH)* information element + +| | | +|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| PWRC Power control indicator (octet 2) Note 1 | | +| bit 7 | | +| 0 | PWRC is not set | +| 1 | PWRC is set | +| DTX, DTX indicator (octet 2) Note 3 | | +| Bit | | +| 8 6 5 | | +| 0 0 0 | The MS may use uplink discontinuous transmission on a TCH-F. The MS shall not use uplink discontinuous transmission on TCH-H. | +| 0 0 1 | The MS shall use uplink discontinuous transmission on a TCH-F. The MS shall not use uplink discontinuous transmission on TCH-H. | +| 0 1 0 | The MS shall not use uplink discontinuous transmission on a TCH-F. The MS shall not use uplink discontinuous transmission on TCH-H. | +| 0 1 1 | Note 4: The MS shall use uplink discontinuous transmission on a TCH-F. The MS may use uplink discontinuous transmission on TCH-H. | +| 1 0 0 | The MS may use uplink discontinuous transmission on a TCH-F. The MS may use uplink discontinuous transmission on TCH-H. | +| 1 0 1 | The MS shall use uplink discontinuous transmission on a TCH-F. The MS shall use uplink discontinuous transmission on TCH-H. | +| 1 1 0 | The MS shall not use uplink discontinuous transmission on a TCH-F. The MS shall use uplink discontinuous transmission on TCH-H. | +| 1 1 1 | Note 4: The MS may use uplink discontinuous transmission on a TCH-F. The MS shall use uplink discontinuous transmission on TCH-H. | +| RADIO-LINK_TIMEOUT (octet 2) Note 2 | | +| Bits | | +| 4 3 2 1 | | +| 0 0 0 0 | 4 | +| 0 0 0 1 | 8 | +| 0 0 1 0 | 12 | +| . | | +| . | | +| . | | +| 1 1 1 0 | 60 | +| 1 1 1 1 | 64 | + +NOTE 1: The precise meaning of the PWRC parameter can be found in 3GPP TS 45.008. + +NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in 3GPP TS 45.008. + +NOTE 3: The DTX indicator field is not related to the use of downlink discontinuous transmission. + +NOTE 4: These codes shall not be sent to mobile stations that implement an earlier version of this protocol in which these codes were not defined. + +#### 10.5.2.4 Cell Selection Parameters + +The purpose of the *Cell Selection Parameters* information element is to provide a variety of information about a cell. + +The *Cell Selection Parameters* information element is coded as shown in figure 10.5.2.4.1 and table 10.5.2.4.1. + +The *Cell Selection Parameters* information element is a type 3 information element with 3 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|------|------------------|------------------|---|---|---|---|---------| +| Cell Selection Parameters IEI | | | | | | | | octet 1 | +| CELL-RESELECT
HYSTERESIS | | | MS-TXPWR-MAX-CCH | | | | | octet 2 | +| ACS | NECI | RXLEV-ACCESS-MIN | | | | | | octet 3 | + +**Figure 10.5.2.4.1: *Cell Selection Parameters* information element** + +**Table 10.5.2.4.1: *Cell Selection Parameters* information element** + +| | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-------------------------------------------|-------|-------------------------------------------|-------|-------------------------------------------|-------|-------------------------------------------|-------|-------------------------------------------|-------|--------------------------------------------|-------|--------------------------------------------|-------|--------------------------------------------| +|

CELL-RESELECT-HYSTERESIS (octet 2)

The usage of this information is defined in 3GPP TS 45.008

Bits
8 7 6

0 0 00 dB RXLEV hysteresis for LA re-selection
0 0 12 dB RXLEV hysteresis for LA re-selection
0 1 04 dB RXLEV hysteresis for LA re-selection
0 1 16 dB RXLEV hysteresis for LA re-selection
1 0 08 dB RXLEV hysteresis for LA re-selection
1 0 110 dB RXLEV hysteresis for LA re-selection
1 1 012 dB RXLEV hysteresis for LA re-selection
1 1 114 dB RXLEV hysteresis for LA re-selection

MS-TXPWR-MAX-CCH (octet 2)

The MS-TXPWR-MAX-CCH field is coded as the binary representation of the "power control level" in 3GPP TS 45.005 corresponding to the maximum TX power level an MS may use when accessing on a Control Channel CCH. This value shall be used by the Mobile Station according to 3GPP TS 45.008.

Range: 0 to 31.


RXLEV-ACCESS-MIN (octet 3)

The RXLEV-ACCESS-MIN field is coded as the binary representation of the minimum received signal level at the MS for which it is permitted to access the system.

Range: 0 to 63. (See 3GPP TS 45.008).


ACS, ADDITIONAL RESELECT PARAM IND (octet 3)

Bit 8:

In System Information type 3 message:

  • 0 System information type 16 and 17 are not broadcast on the BCCH.
  • 1 System information type 16 and 17 are broadcast on the BCCH. A mobile station which does not support System information type 16 and 17 may consider this bit as "0".

In System Information type 4 message:

  • 0 The SI 4 rest octets, if present, and SI 7 and SI 8 rest octets, if so indicated in the SI 4 rest octets shall be used to derive the value of PI and possibly C2 parameters and/or other parameters
  • 1 The value of PI and possibly C2 parameters and/or other parameters in a System information type 7 or type 8 message shall be used
| 0 0 0 | 0 dB RXLEV hysteresis for LA re-selection | 0 0 1 | 2 dB RXLEV hysteresis for LA re-selection | 0 1 0 | 4 dB RXLEV hysteresis for LA re-selection | 0 1 1 | 6 dB RXLEV hysteresis for LA re-selection | 1 0 0 | 8 dB RXLEV hysteresis for LA re-selection | 1 0 1 | 10 dB RXLEV hysteresis for LA re-selection | 1 1 0 | 12 dB RXLEV hysteresis for LA re-selection | 1 1 1 | 14 dB RXLEV hysteresis for LA re-selection | +| 0 0 0 | 0 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | +| 0 0 1 | 2 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | +| 0 1 0 | 4 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | +| 0 1 1 | 6 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | +| 1 0 0 | 8 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | +| 1 0 1 | 10 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | +| 1 1 0 | 12 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | +| 1 1 1 | 14 dB RXLEV hysteresis for LA re-selection | | | | | | | | | | | | | | | | + +NECI: HALF RATE SUPPORT (octet 3) + +Bit 7: + +- 0 New establishment causes are not supported +1 New establishment causes are supported + +##### 10.5.2.4a (void) + +#### 10.5.2.5 Channel Description + +The purpose of the *Channel Description* information element is to provide a description of an allocable channel together with its SACCH. + +The *Channel Description* information element is coded as shown in figure 10.5.2.5.1 and table 10.5.2.5.1. + +The *Channel Description* is a type 3 information element with 4 octets length. + +![](24b10c86fe55f7126e355d9bc6fef7b9_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|-----------|-------------------|---|---|---|---------| +| Channel Description IEI | | | | | | | | octet 1 | +| Channel type and TDMA offset | | | | TN | | | | octet 2 | +| TSC | | | H=1-> | MAIO (high part) | | | | octet 3 | +| | | | --- H --- | ARFCN (high part) | | | | | +| MAIO (low part) | | | H=0-> | 0 spare | | | | octet 4 | +| | | | HSN | | | | | | +| ARFCN (low part) | | | | | | | | | + +Figure 10.5.2.5.1: *Channel Description* information element + +Table 10.5.2.5.1: *Channel Description* information element + +Channel type and TDMA offset (octet 2) + +Bits + +8 7 6 5 4 + +S 0 0 0 1 TCH/F + ACCHs + +S 0 0 1 T TCH/H + ACCHs + +0 0 1 T T SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4); TSC Set 1 shall be used + +0 1 T T T SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8); TSC Set 1 shall be used + +The T bits indicate the subchannel number coded in binary. + +S, TSC set + +Bit + +8 + +0 TSC Set 1 shall be used + +1 TSC Set 2 shall be used + +All other values are reserved. + +The sender set the spare bits to the coding for TCH/F+ACCHs + +TN, Timeslot number (octet 2) + +The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010. + +Range: 0 to 7. + +The Timeslot number field shall be ignored and all bits treated as spare when received in a PDCH ASSIGNMENT COMMAND message. The sender sets the spare bits as '000' + +TSC, Training Sequence Code (octet 3) + The TSC field is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002 + The TSC set for the CS channels is signalled via 'Channel type and TDMA offset' field. In case of DTM the PS channels shall use the training sequence with the training sequence code as signalled in the TSC field and always selected from TSC Set 1 regardless of the TSC set signalled in the 'Channel type and TDMA offset' field. If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) and the 'Extended TSC Set' IE is included in the assignment message the mobile station shall use information provided therein for the CS and PS channels (see sub-clause 10.5.2.82). + +Range: 0 to 7. + +H, Hopping channel (octet 3) + Bit + 5 + 0 Single RF channel + 1 RF hopping channel + +NOTE: The value of H affects the semantics of the channel selector field + +Channel selector (octet 3 and 4) + H = "0": The channel selector field consists of the absolute RF channel number + +Octet 3 + Bits + 4 3 + 0 0 Spare + +ARFCN, (octet 3, bits 2 and 1, and octet 4, bits 8 to 1) + The ARFCN is coded as the binary representation of the absolute RF channel number + +Range: 0 to 1023 + +H = "1": The channel selector field consists of the mobile allocation index offset, MAIO, and the hopping sequence number, HSN. + +MAIO, (octet 3 bit 4 to 1 high part and octet 4 bit 8 to 7 low part) + The MAIO field is coded as the binary representation of the mobile allocation index offset as defined in 3GPP TS 45.002. + +Range: 0 to 63. + +HSN, (octet 4 bit 6 to 1) + The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 45.002 + Range 0 to 63. + +##### 10.5.2.5a Channel Description 2 + +The purpose of the *Channel Description 2* information element is to provide a description of an allocable channel configuration together with its SACCH. + +The *Channel Description 2* information element is coded as shown in figure 10.5.2.5a.1 and table 10.5.2.5a.1. + +The *Channel Description 2* is a type 3 information element with 4 octets length. + +![](ff722ae9516b94709d721deaf5523d2e_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|-----|-----------|------------------|---|-------------------|---|---------| +| Channel Description 2 IEI | | | | | | | | octet 1 | +| Channel type and TDMA offset | | | | TN | | | | octet 2 | +| TSC | | | H=1-> | MAIO (high part) | | | | octet 3 | +| | | | --- H --- | ----- | | | | | +| | | | H=0-> | 0 spare | | ARFCN (high part) | | octet 4 | +| | | | ----- | | | | | | +| MAIO (low part) | | HSN | | | | | | | +| ARFCN (low part) | | | | | | | | | + +Figure 10.5.2.5a.1: *Channel Description 2* information element + +**Table 10.5.2.5a.1: Channel Description 2 information element** + +|

Channel type and TDMA offset (octet 2)
Bits

8 7 6 5 4
00000 TCH/F + FACCH/F and SACCH/M at the timeslot indicated by TN, and additional bidirectional or unidirectional TCH/Fs and SACCH/Ms according to the multislot allocation information element
 
00001 TCH/F + FACCH/F and SACCH/F
0001T TCH/H + ACCHs
001TT SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4)
01TTT SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8)
 
11000 TCH/F + ACCHs using TSC Set 2
1110T TCH/H + ACCHs using TSC Set 2

The T bits indicate the subchannel number coded in binary.

In the description below "n" is the timeslot number indicated by TN. The description is valid only if all the indicated timeslot numbers are in the range 0 to 7.

1 0 X X X    TCH/F + FACCH/F and SACCH/M at the time slot indicated by TN, and additional bidirectional TCH/Fs and SACCH/Ms at other timeslots according to the following:

X X X:
000no additional timeslots
001at timeslot n-1
010at timeslot n+1, n-1
011at timeslot n+1, n-1 and n-2
100at timeslot n+1, n-1, n-2, and n-3
101at timeslot n+1, n-1, n-2, n-3 and n-4
110at timeslot n+1, n-1, n-2, n-3, n-4 and n-5
111at timeslot n+1, n-1, n-2, n-3, n-4, n-5 and n-6

1 1 0 0 1
to
1 1 0 1 1    TCH/F + FACCH/F and SACCH/M at the time slot indicated by TN and additional unidirectional TCH/FDs and SACCH/MDs at other timeslots according to the following:

11001at timeslot n-1
11010at timeslot n+1, n-1
11011at timeslot n+1, n-1 and n-2

1 1 1 1 0    TCH/F + FACCH/F and SACCH/M at the time slot indicated by TN and additional bidirectional TCH/F and SACCH/M at timeslot n+1 and unidirectional TCH/FD and SACCH/MD at timeslot n-1

All other values are reserved.

TN, Timeslot number (octet 2)
The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 3GPP TS 45.010.

Range: 0 to 7.

TSC, Training Sequence Code (octet 3)
The TSC field is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002
Unless stated otherwise by coding of 'Channel type and TDMA offset' IE, TSC Set 1 shall be used. If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) and the 'Extended TSC Set' IE is included in the assignment message the mobile station shall use information provided therein for the CS and PS channels (see sub-clause 10.5.2.82).

Range: 0 to 7.

| 8 | 7 | 6 | 5 | 4 | | 0 | 0 | 0 | 0 | 0 | TCH/F + FACCH/F and SACCH/M at the timeslot indicated by TN, and additional bidirectional or unidirectional TCH/Fs and SACCH/Ms according to the multislot allocation information element | | | | | | | 0 | 0 | 0 | 0 | 1 | TCH/F + FACCH/F and SACCH/F | 0 | 0 | 0 | 1 | T | TCH/H + ACCHs | 0 | 0 | 1 | T | T | SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4) | 0 | 1 | T | T | T | SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8) | | | | | | | 1 | 1 | 0 | 0 | 0 | TCH/F + ACCHs using TSC Set 2 | 1 | 1 | 1 | 0 | T | TCH/H + ACCHs using TSC Set 2 | X | X | X: | | 0 | 0 | 0 | no additional timeslots | 0 | 0 | 1 | at timeslot n-1 | 0 | 1 | 0 | at timeslot n+1, n-1 | 0 | 1 | 1 | at timeslot n+1, n-1 and n-2 | 1 | 0 | 0 | at timeslot n+1, n-1, n-2, and n-3 | 1 | 0 | 1 | at timeslot n+1, n-1, n-2, n-3 and n-4 | 1 | 1 | 0 | at timeslot n+1, n-1, n-2, n-3, n-4 and n-5 | 1 | 1 | 1 | at timeslot n+1, n-1, n-2, n-3, n-4, n-5 and n-6 | 1 | 1 | 0 | 0 | 1 | at timeslot n-1 | 1 | 1 | 0 | 1 | 0 | at timeslot n+1, n-1 | 1 | 1 | 0 | 1 | 1 | at timeslot n+1, n-1 and n-2 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|----|--------------------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|---|---|---|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|--|--|---|---|---|---|---|-----------------------------|---|---|---|---|---|---------------|---|---|---|---|---|--------------------------------------|---|---|---|---|---|--------------------------------------|--|--|--|--|--|--|---|---|---|---|---|-------------------------------|---|---|---|---|---|-------------------------------|---|---|----|--|---|---|---|-------------------------|---|---|---|-----------------|---|---|---|----------------------|---|---|---|------------------------------|---|---|---|------------------------------------|---|---|---|----------------------------------------|---|---|---|---------------------------------------------|---|---|---|--------------------------------------------------|---|---|---|---|---|-----------------|---|---|---|---|---|----------------------|---|---|---|---|---|------------------------------| +| 8 | 7 | 6 | 5 | 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | TCH/F + FACCH/F and SACCH/M at the timeslot indicated by TN, and additional bidirectional or unidirectional TCH/Fs and SACCH/Ms according to the multislot allocation information element | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 0 | 1 | TCH/F + FACCH/F and SACCH/F | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 1 | T | TCH/H + ACCHs | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 1 | T | T | SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | T | T | T | SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 0 | 0 | 0 | TCH/F + ACCHs using TSC Set 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 1 | 0 | T | TCH/H + ACCHs using TSC Set 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| X | X | X: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | no additional timeslots | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 1 | at timeslot n-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | 0 | at timeslot n+1, n-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | 1 | at timeslot n+1, n-1 and n-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 0 | at timeslot n+1, n-1, n-2, and n-3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 1 | at timeslot n+1, n-1, n-2, n-3 and n-4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 0 | at timeslot n+1, n-1, n-2, n-3, n-4 and n-5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 1 | at timeslot n+1, n-1, n-2, n-3, n-4, n-5 and n-6 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 0 | 0 | 1 | at timeslot n-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 0 | 1 | 0 | at timeslot n+1, n-1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 0 | 1 | 1 | at timeslot n+1, n-1 and n-2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +H, Hopping channel (octet 3) + Bit + 5 + 0 Single RF channel + 1 RF hopping channel + +NOTE: The value of H affects the semantics of the channel selector field + +Channel selector (octet 3 and 4) + H = "0": The channel selector field consists of the absolute RF channel number + +Octet 3 + Bits + 4 3 + 0 0 Spare + +ARFCN, (octet 3, bits 2 and 1, and octet 4, bits 8 to 1) + The ARFCN is coded as the binary representation of the absolute RF channel number + +Range: 0 to 1023 + +H = "1": The channel selector field consists of the mobile allocation index offset, MAIO, and the hopping sequence number, HSN. + +MAIO, (octet 3 bit 4 to 1 high part and octet 4 bit 8 to 7 low part) + The MAIO field is coded as the binary representation of the mobile allocation index offset as defined in 3GPP TS 45.002. + +Range: 0 to 63. + +HSN, (octet 4 bit 6 to 1) + The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 45.002 + +Range 0 to 63. + +##### 10.5.2.5c Channel Description 3 + +The purpose of the *Channel Description 3* information element is to provide a description of a channel which does not specify a TCH. + +The *Channel Description 3* information element is coded as shown in figure 10.5.2.5c.1. All elements are as specified for the Channel Description IE (see sub-clause 10.5.2.5). + +The *Channel Description 3* is a type 3 information element with 3 octets length. + +![](516174e327ed8fcb75cb3af20f110de8_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------|---|-------|-----------|------------------|---|-------------|---|---------| +| Channel Description 3 IEI | | | | | | | | octet 1 | +| TSC | | | H=1-> | MAIO (high part) | | | | octet 2 | +| | | | --- H --- | ----- | | | | | +| | | | H=0-> | 0 | | ARFCN | | octet 3 | +| | | | | spare | | (high part) | | | +| MAIO | | HSN | | | | | | | +| (low part) | | ----- | | | | | | | +| ARFCN (low part) | | | | | | | | | + +Figure 10.5.2.5c.1: *Channel Description 3* information element + +#### 10.5.2.6 Channel Mode + +The *Channel Mode* information element gives information of the mode on coding/decoding and transcoding. The exact mode is determined by the contents of this IE and the channel type. + +The *Channel Mode* information element is coded as shown in figure 10.5.2.6.1 and table 10.5.2.6.1. + +The *Channel Mode* is a type 3 information element with 2 octets length. + +![](2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg) + +| | | | | | | | | | | +|---|---|---|---|---|---|---|---|------------------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| | | | | | | | | Channel Mode IEI | octet 1 | +| | | | | | | | | Mode | octet 2 | + +**Figure 10.5.2.6.1: Channel Mode information element** + +**Table 10.5.2.6.1: Channel Mode information element** + +| The mode field is encoded as follows:
(octet 2) | | | | | | | | | | +|----------------------------------------------------|---|---|---|---|---|---|---|----------------------------------------------------------------|--| +| Bits | | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | signalling only | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | speech full rate or half rate version 1 | | +| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | speech full rate or half rate version 1 in VAMOS mode (Note 3) | | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | speech full rate or half rate version 2 | | +| 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | speech full rate or half rate version 2 in VAMOS mode (Note 3) | | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | speech full rate or half rate version 3 | | +| 1 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | speech full rate or half rate version 3 in VAMOS mode (Note 3) | | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | speech full rate or half rate version 4 | | +| 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | speech full rate or half rate version 5 | | +| 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | speech full rate or half rate version 5 in VAMOS mode (Note 3) | | +| 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | speech full rate or half rate version 6 | | +| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | data, 43.5 kbit/s (downlink)+14.5 kbps (uplink) | | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | data, 29.0 kbit/s (downlink)+14.5 kbps (uplink) | | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | data, 43.5 kbit/s (downlink)+29.0 kbps (uplink) | | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | data, 14.5 kbit/s (downlink)+43.5 kbps (uplink) | | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | data, 14.5 kbit/s (downlink)+29.0 kbps (uplink) | | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | data, 29.0 kbit/s (downlink)+43.5 kbps (uplink) | | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | data, 43.5 kbit/s radio interface rate | | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | data, 32.0 kbit/s radio interface rate | | +| 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | data, 29.0 kbit/s radio interface rate | | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | data, 14.5 kbit/s radio interface rate | | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | data, 12.0 kbit/s radio interface rate | | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | data, 6.0 kbit/s radio interface rate | | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | data, 3.6 kbit/s radio interface rate | | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | data, 64.0 kbit/s Transparent Data Bearer (Note 2) | | + +Other values are reserved for future use. + +Note 1: The speech versions are also referred as follows +(see 3GPP TS 26.103): + +| | | +|-----------------------------------|-----------------------------------------------------------------------------| +| full rate or half rate version 1: | GSM FR or GSM HR | +| full rate or half rate version 2: | GSM EFR (half rate version 2 not defined in this version of the protocol) | +| full rate or half rate version 3: | FR AMR or HR AMR | +| full rate or half rate version 4: | OFR AMR-WB or OHR AMR-WB | +| full rate or half rate version 5: | FR AMR-WB (half rate version 5 not defined in this version of the protocol) | +| full rate or half rate version 6: | OHR AMR (full rate version 6 not defined in this version of the protocol) | + +Note 2: This code point is only used for channel assignments made in GAN mode. +Note 3: This code point is only used for a mobile station that indicates support for VAMOS II or VAMOS III (see 3GPP TS 24.008) + +#### 10.5.2.7 Channel Mode 2 + +The *Channel Mode 2* information element gives information of the mode of coding/decoding and transcoding. + +The *Channel Mode 2* information element is coded as shown in figure 10.5.2.7.1 and table 10.5.2.7.1. + +The *Channel Mode 2* is a type 3 information element with 2 octets length. + +![](832570a3a00d9064e8068d0bb5def3a9_img.jpg) + +| | | | | | | | | | | +|---|---|---|---|---|---|---|---|------------------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| | | | | | | | | Channel Mode IEI | octet 1 | +| | | | | | | | | Mode | octet 2 | + +**Figure 10.5.2.7.1: Channel Mode 2 information element** + +**Table 10.5.2.7.1: Channel Mode 2 information element** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|------------------------------------------------------------------| +| The mode field is encoded as follows:
(octet 2) | | | +| Bits | | | +| 8 | 7 | 6 5 4 3 2 1 | +| 0 | 0 | 0 0 0 0 0 0 0 0 signalling only | +| 0 | 0 | 0 0 0 0 1 0 1 speech half rate version 1 | +| 1 | 1 | 0 0 0 0 0 0 1 speech half rate version 1 in VAMOS mode (Note: 2) | +| 0 | 0 | 1 0 0 1 0 1 speech half rate version 2 | +| 0 | 1 | 0 0 0 1 0 1 speech half rate version 3 | +| 1 | 1 | 0 0 0 0 1 1 speech half rate version 3 in VAMOS mode (Note: 2) | +| 1 | 0 | 0 0 0 1 0 1 speech half rate version 4 | +| 0 | 1 | 0 0 1 1 0 speech half rate version 6 | +| 0 | 0 | 0 1 1 1 1 data, 6.0 kbit/s radio interface rate | +| 0 | 0 | 1 0 1 1 1 data, 3.6 kbit/s radio interface rate | +| Other values are reserved for future use. | | | +| Note 1: The speech versions are also referred as follows (see 3GPP TS 26.103): | | | +| half rate version 1: | GSM HR | | +| half rate version 2: | not defined in this version of the protocol | | +| half rate version 3: | HR AMR | | +| half rate version 4: | OHR AMR-WB | | +| half rate version 6: | OHR AMR | | +| Note 2: This code point is only used for a mobile station that indicates support for VAMOS II or VAMOS III (see 3GPP TS 24.008). | | | + +##### 10.5.2.7a UTRAN Classmark information element + +Only valid for a UTRAN capable mobile station. The *UTRAN Classmark* information element includes the INTER RAT HANDOVER INFO (defined in 3GPP TS 25.331) which gives UTRAN related information to the network (target system) for intersystem handover. + +The UTRAN Classmark information element is a type 4 information element with a minimum length of 2 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|----------------------------|---|---|---|---|---|---|-----------| +| | UTRAN Classmark IEI | | | | | | | octet 1 | +| | Length of UTRAN Classmark | | | | | | | octet 2 | +| | UTRAN Classmark value part | | | | | | | octet 3-n | + +**Figure 10.5.2.7a: UTRAN Classmark information element** + +The value part of the *UTRAN Classmark information element* is the INTER RAT HANDOVER INFO as defined in 3GPP TS 25.331. + +##### 10.5.2.7b (void) + +##### 10.5.2.7c Classmark Enquiry Mask + +The Classmark Enquiry mask defines the information to be returned to the network. The bit mask defines the specific information to be returned, such as UTRAN specific information and/or CDMA2000 capability and/or requests the sending of the CLASSMARK CHANGE or GERAN IU MODE CLASSMARK CHANGE message. The classmark change procedure is described in sub-clause 3.4.10. + +The Classmark Enquiry Mask is a type 4 information element with 3 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|-------------------------------------------|---|---|---|---|---|---|---------| +| | Classmark Enquiry Mask IEI | | | | | | | octet 1 | +| | Length of Classmark Enquiry Mask contents | | | | | | | octet 2 | +| | Classmark Enquiry Mask value part | | | | | | | octet 3 | + +**Figure 10.5.2.7c.1: Classmark Enquiry Mask information element** + +**Table 10.5.2.7c.2: Classmark Enquiry Mask value part.** + +| | | +|--------------------------------------------------------------------------------------|-------------------------------------------------------| +| Bit 8: | | +| 0 | CLASSMARK CHANGE message is requested | +| 1 | CLASSMARK CHANGE message is not requested | +| Bits 7-5: | | +| 000 | UTRAN CLASSMARK CHANGE message is requested | +| 111 | UTRAN CLASSMARK CHANGE message is not requested. | +| All other values shall not be sent. If received, they shall be interpreted as '000'. | | +| Bit 4: | | +| 0 | CDMA2000 CLASSMARK CHANGE message requested | +| 1 | CDMA2000 CLASSMARK CHANGE message not requested. | +| Bit 3: | | +| 0 | GERAN IU MODE CLASSMARK CHANGE message requested | +| 1 | GERAN IU MODE CLASSMARK CHANGE message not requested. | +| Bits 2 - 1: | spare(0). | + +##### 10.5.2.7d GERAN Iu Mode Classmark information element + +Only valid for a GERAN *Iu mode* capable mobile station. The *GERAN Iu Mode Classmark* information element includes the MS GERAN IU MODE RADIO ACCESS CAPABILITY IE defined in 3GPP TS 44.118. + +The GERAN Iu mode Classmark information element is a type 4 information element with a minimum length of 13 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.060). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|------------------------------------|---|---|---|---|---|-----------| +| | | GERAN Iu Mode Classmark IEI | | | | | | octet 1 | +| | | Length of GERAN Iu Mode Classmark | | | | | | octet 2 | +| | | GERAN Iu Mode Classmark value part | | | | | | octet 3-n | + +**Figure 10.5.2.7d: GERAN Iu Mode Classmark information element** + +The value part of the *GERAN Iu Mode Classmark information element* is the MS GERAN IU MODE RADIO ACCESS CAPABILITY as defined in 3GPP TS 44.118. If the value part of the *GERAN Iu Mode Classmark information element* has a length which is not an integer number of octets, then the remaining bits in the *GERAN Iu Mode Classmark* information element shall be padding bits. + +#### 10.5.2.8 Channel Needed + +The purpose of the *Channel Needed* information element is to indicate to up to two mobile stations which type of channel is needed (for each mobile station) for the transaction linked to the paging procedure. + +The *Channel Needed* information element is coded as shown in figure 10.5.2.8.1 and table 10.5.2.8.1. + +The *Channel Needed* is a type 1 information element. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|--------------------|---|------------------|---|-----------------|---|---------| +| | | Channel Needed IEI | | CHANNEL (second) | | CHANNEL (first) | | octet 1 | + +**Figure 10.5.2.8.1: Channel Needed information element** + +**Table 10.5.2.8.1: Channel Needed information element** + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------|-----|-----------------------------| +| CHANNEL (octet 1) | | | +| Bits | | | +| 2/4 | 1/3 | | +| 0 | 0 | Any channel. | +| 0 | 1 | SDCCH. | +| 1 | 0 | TCH/F (Full rate). | +| 1 | 1 | TCH/H or TCH/F (Dual rate). | +| If this information element is used for only one mobile station, then the first CHANNEL field is used and the second CHANNEL field is spare. | | | + +##### **10.5.2.8a (void)** + +##### **10.5.2.8b Channel Request Description 2** + +The purpose of the *Channel Request Description 2* information element is to indicate to the network the reason of the request to enter dual transfer mode and MS capabilities relevant to DTM. + +The *Channel Request Description 2* information element is coded as shown in figure 10.5.2.8b.1 and tables 10.5.2.8b.1 and 10.5.2.8b.2. + +The *Channel Request Description 2* information element is a type 4 information element with a minimum length of 6 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below. + +![](3295c6ffe9f6d00c3811c37d327ac844_img.jpg) + +| | | | | | | | | | +|----------------------------------------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Channel Request Description 2 IEI | | | | | | | | octet 1 | +| Length of Channel Request Description 2 value part | | | | | | | | octet 2 | +| Channel Request Description 2 value part | | | | | | | | octet 3 - n | + +**Figure 10.5.2.8b.1: Channel Request Description 2 information element****Table 10.5.2.8b.1: Channel Request Description 2 value part** + +``` + +< Channel Request Description 2 value part > ::= + < PACKET_ESTABLISHMENT_CAUSE : bit(2) > + < Channel Request Description : Channel Request Description IE > -- Defined in 3GPP TS 44.060 + { 0 | 1 < PFI : bit (7) > } + < Multiple TBF Capability : bit > -- Additions in Rel-6 + { + null | L -- Receiver backward compatible with earlier version + | H + -- Additions in Rel-7 + { + < RLC Non-persistent Mode Capability : bit > + < Reduced Latency Capability : bit > + < Uplink EGPRS2 : bit(2) > + < Downlink EGPRS2 : bit(2) > + } + { + null | L -- Receiver backward compatible with earlier version + | H + -- Additions in Rel-9 + { + < EMST_MS_Capability : bit > } + { + null | L -- Receiver backward compatible with earlier version + | H + -- Additions in Rel-10 + { + < EMSR_MS_Capability : bit > } + { + null | L -- Receiver backward compatible with earlier version + | H + -- Additions in Rel-11 + { + < FANR_Capability : bit > } + } -- End of additions for Rel-11 + } -- End of additions for Rel-10 + } -- End of additions for Rel-9 + } -- End of additions for Rel-7 + } + < spare padding > ; + +``` + +**Table 10.5.2.8b.2: Channel Request Description 2 value part details** + +##### **PACKET\_ESTABLISHMENT\_CAUSE (2 bit field)** + +This field indicates the reason for requesting the access. + +| Bit | | +|-----|-------------------------------| +| 2 1 | | +| 0 0 | User Data | +| 0 1 | Page Response | +| 1 0 | Cell Update | +| 1 1 | Mobility Management procedure | + +##### **Channel Request Description (information element)** + +The Channel Request Description information element is defined in 3GPP TS 44.060. + +###### **PFI (7 bit field)** + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. + +##### **Multiple TBF Capability (1 bit field)** + +This field is included as the MS Radio Access Capability IE is not present and the Mobile Station Classmark 3 does not contain this information. + +| Bit | | +|-----|----------------------------------------------------| +| L | Multiple TBF procedures in A/Gb mode not supported | +| H | Multiple TBF procedures in A/Gb mode supported | + +##### **RLC Non-persistent Mode Capability (1 bit field)** + +This field is included as the MS Radio Access Capability IE is not present and the Mobile Station Classmark 3 does not contain this information. + +| Bit | | +|-----|---------------------------------------| +| 0 | RLC Non-persistent Mode not supported | +| 1 | RLC Non-persistent Mode supported | + +##### **Reduced Latency Capability (1 bit field)** + +This field indicates whether the mobile station supports Reduced TTI configurations and Fast Ack/Nack Reporting (see 3GPP TS 44.060 [76]) for both EGPRS and, if supported, EGPRS2. + +| Bit | | +|-----|--------------------------------------------------------------------------------------------| +| 0 | The mobile station does not support Reduced TTI configurations and Fast Ack/Nack Reporting | +| 1 | The mobile station supports Reduced TTI configurations and Fast Ack/Nack Reporting | + +NOTE: A mobile station supporting both FANR and RTTI in (non DTM) packet transfer mode but whose multislot class does not allow the support of RTTI configurations in dual transfer mode due to a limited number of uplink or downlink timeslots (see 3GPP TS 45.002 [32]) shall support FANR for BTTI configurations in dual transfer mode and set the Reduced Latency Capability field to '1'. + +##### **Uplink EGPRS2 (2 bit field)** + +This field indicates whether the mobile station supports EGPRS2-A or EGPRS2-A and EGPRS2-B in the uplink + +| | | +|-----|-------------------------------------------------------------------------------------------------------------------| +| Bit | | +| 2 1 | | +| 0 0 | The mobile station does not support either EGPRS2-A or EGPRS2-B in the uplink | +| 0 1 | The mobile station supports EGPRS2-A in the uplink | +| 1 0 | The mobile station supports both EGPRS2-A and EGPRS2-B in the uplink | +| 1 1 | This value is not used in this release/version of the specifications. If received it shall be interpreted as '10' | + +##### **Downlink EGPRS2 (2 bit field)** + +This field indicates whether the mobile station supports EGPRS2-A or EGPRS2-A and EGPRS2-B in the downlink + +| | | +|-----|-------------------------------------------------------------------------------------------------------------------| +| Bit | | +| 2 1 | | +| 0 0 | The mobile station does not support either EGPRS2-A or EGPRS2-B in the downlink | +| 0 1 | The mobile station supports EGPRS2-A in the downlink | +| 1 0 | The mobile station supports both EGPRS2-A and EGPRS2-B in the downlink | +| 1 1 | This value is not used in this release/version of the specifications. If received it shall be interpreted as '10' | + +##### **EMST\_MS\_Capability (1 bit field)** + +This field indicates whether the mobile station supports the enhanced multiplexing for single TBF. + +| | | +|-----|------------------------------------------| +| Bit | | +| 0 | The mobile station does not support EMST | +| 1 | The mobile station supports EMST | + +##### **EMSR\_MS\_Capability (1 bit field)** + +This field indicates whether the mobile station supports the enhanced multiplexing for single RLC entity. + +| | | +|-----|------------------------------------------| +| Bit | | +| 0 | The mobile station does not support EMSR | +| 1 | The mobile station supports EMSR | + +##### **FANR Capability (1 bit field)** + +This field indicates whether the mobile station supports Fast Ack/Nack Reporting (see 3GPP TS 44.060 [76]) in packet transfer mode for EGPRS and, if supported, EGPRS2. If mobile station indicates support for Reduced TTI configurations and Fast Ack/Nack Reporting using the Reduced Latency Capability then network shall ignore FANR Capability information. + +| | | +|-----|-------------------------------------------------------------| +| Bit | | +| 0 | The mobile station does not support Fast Ack/Nack Reporting | +| 1 | The mobile station supports Fast Ack/Nack Reporting | + +#### 10.5.2.9 Cipher Mode Setting + +The purpose of the *Cipher Mode Setting* information element is to indicate whether stream ciphering shall be started or not and if it is to be started, which algorithm to use. + +The *Cipher Mode Setting* information element is coded as shown in figure 10.5.2.9.1 and table 10.5.2.9.1. + +The *Cipher Mode Setting* is a type 1 information element. + +![](a2b2175c4ea64d37fa63b71f79d6d48b_img.jpg) + +| | | | | | | | | | +|------------------|---|---|---|----------------------|---|---|----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet 1 | +| Ciph Mod Set IEI | | | | algorithm identifier | | | SC | | + +**Figure 10.5.2.9.1: Cipher Mode Setting information element** + +**Table 10.5.2.9.1: Cipher Mode Setting information element** + +| | | +|-------------------------------------------------------|----------------------------| +| algorithm identifier | | +| If SC=1 then: | | +| bits | | +| 4 3 2 | | +| 0 0 0 | cipher with algorithm A5/1 | +| 0 0 1 | cipher with algorithm A5/2 | +| 0 1 0 | cipher with algorithm A5/3 | +| 0 1 1 | cipher with algorithm A5/4 | +| 1 0 0 | cipher with algorithm A5/5 | +| 1 0 1 | cipher with algorithm A5/6 | +| 1 1 0 | cipher with algorithm A5/7 | +| 1 1 1 | reserved | +| If SC=0 then bits 4, 3 and 2 are spare and set to "0" | | +| SC (octet 1) | | +| Bit | | +| 1 | | +| 0 | No ciphering | +| 1 | Start ciphering | + +#### 10.5.2.10 Cipher Response + +The *Cipher Response* information element is used by the network to indicate to the mobile station which information the mobile station has to include in the CIPHERING MODE COMPLETE message. + +The *Cipher Response* information element is coded as shown in figure 10.5.2.10.1 and table 10.5.2.10.1. + +The *Cipher Response* is a type 1 information element. + +![](813ef40a14c7e2a52988a63e33c2b59f_img.jpg) + +| | | | | | | | | | +|---|------------------|---|---|-------|---|---|----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | Cipher Resp. IEI | | | 0 | 0 | 0 | CR | octet 1 | +| | | | | Spare | | | | | + +**Figure 10.5.2.10.1: Cipher Response information element****Table 10.5.2.10.1: Cipher Response information element** + +| | | +|------------------------------|------------------------------| +| CR Cipher Response (octet 1) | | +| Bit | | +| 1 | | +| 0 | IMEISV shall not be included | +| 1 | IMEISV shall be included | + +#### 10.5.2.11 Control Channel Description + +The purpose of the *Control Channel Description* information element is to provide a variety of information about a cell. + +The *Control Channel Description* information element is coded as shown in figure 10.5.2.11.1 and table 10.5.2.11.1. + +The *Control Channel Description* is a type 3 information element with 4 octets length. + +![](82ebf1d055f86cd379f5f38b8e948e2a_img.jpg) + +| | | | | | | | | | +|---------|---------------------------------|----------------|---|---|-------------|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | Control Channel Description IEI | | | | | | | octet 1 | +| MSCR | ATT | BS-AG-BLKS-RES | | | CCCH-CONF | | | octet 2 | +| SI22IND | CBQ3 | | 0 | 0 | BS-PA-MFRMS | | | octet 3 | +| | spare | | | | | | | | +| | T 3212 | | | | | | | octet 4 | +| | time-out value | | | | | | | | + +**Figure 10.5.2.11.1: Control Channel Description information element** + +**Table 10.5.2.11.1: Control Channel Description information element** + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| MSCR , MSC Release (octet 2) | | +| Bit | | +| 8 | | +| 0 | MSC is Release '98 or older | +| 1 | MSC is Release '99 onwards | +| ATT , Attach-detach allowed (octet 2) | | +| Bit | | +| 7 | | +| 0 | MSs in the cell are not allowed to apply IMSI attach and detach procedure. | +| 1 | MSs in the cell shall apply IMSI attach and detach procedure. | +| BS-AG-BLKS-RES (octet 2) | | +| The BS-AG-BLKS-RES field is coded as the binary representation of the number of blocks reserved for access grant. In a cell that supports eDRX this field is subject to special requirements (see 3GPP TS 45.002 [32]). | | +| Range | | +| 0 to 2 | if CCCH-CONF = "001" | +| 0 to 7 | for other values of CCCH-CONF | +| All other values are reserved in the first case | | +| CCCH-CONF (octet 2) | | +| bits | | +| 3 2 1 | | +| 0 0 0 | 1 basic physical channel used for CCCH, not combined with SDCCHs | +| 0 0 1 | 1 basic physical channel used for CCCH, combined with SDCCHs | +| 0 1 0 | 2 basic physical channel used for CCCH, not combined with SDCCHs | +| 1 0 0 | 3 basic physical channel used for CCCH, not combined with SDCCHs | +| 1 1 0 | 4 basic physical channels used for CCCH, not combined with SDCCHs | +| all other values are reserved | | +| SI22IND , SYSTEM INFORMATION TYPE 22 indicator (octet 3) | | +| Bit | | +| 8 | | +| 0 | SI22 is not broadcast. | +| 1 | SI22 is broadcast. | +| CBQ3 , Cell Bar Qualify 3 (octet 3) | | +| Bits | | +| 7 6 | | +| 0 0 | lu mode not supported | +| 0 1 | lu mode capable MSs barred | +| 1 0 | lu mode supported, cell not barred | +| 1 1 | lu mode supported, cell not barred. The network shall not use this value. | +| NOTE: See 3GPP TS 45.008 for information on Cell Bar Qualify 3 | | + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| BS-PA-MFRMS (octet 3) | | +| Bits | | +| 3 2 1 | | +| 0 0 0 | 2 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup | +| 0 0 1 | 3 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup | +| 0 1 0 | 4 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup. | +| . | . | +| . | . | +| 1 1 1 | 9 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup | +|
This field is not used by a MS that uses eDRX (see 3GPP TS 45.002 [32]). | | +|

NOTE: The number of different paging subchannels on the CCCH is:

$ \begin{aligned} & \text{MAX}(1, (3 - \text{BS-AG-BLKS-RES})) * \text{BS-PA-MFRMS} \\ & \text{if CCCH-CONF} = \text{"001"} \\ & (9 - \text{BS-AG-BLKS-RES}) * \text{BS-PA-MFRMS} \\ & \text{for other values of CCCH-CONF} \end{aligned} $ | | +| T3212 timeout value (octet 4) | | +| The T3212 timeout value field is coded as the binary representation of the timeout value for periodic updating in decihours. | | +|
Range: 1 to 255 | | +|
The value 0 is used for infinite timeout value i.e. periodic updating shall not be used within the cell. | | + +NOTE: The MSC Release bit indicates the version of the MSC specific protocols and is not applicable to access stratum protocols. + +##### 10.5.2.11a DTM Information Details + +The *DTM Information Details* Information Element provides the mobile station with relevant GPRS information needed for correct DTM operation. This information element is contained in messages addressed to mobile stations supporting GPRS and DTM. + +The *DTM Information Details* information element is coded as shown in figure 10.5.2.11a.1 and tables 10.5.2.11a.1 and 10.5.2.11a.2. + +The *DTM Information Details* is a type 4 information element with a minimum length of 5 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|---|-----------| +| DTM Information Details IEI | | | | | | | | octet 1 | +| Length of DTM Information Details value part | | | | | | | | octet 2 | +| DTM Information Details value part | | | | | | | | octet 3-n | + +**Figure 10.5.2.11a.1: DTM Information Details information element** + +**Table 10.5.2.11a.1: DTM Information Details value part** + +``` + +< DTM Information Details value part > ::= + < MAX_LAPDm : bit (3) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > + < Cell identity: bit (16) > + { + null | L -- Receiver backward compatible with earlier version + | H -- Additions for REL-6 + { + 0 -- MBMS procedures not supported by the cell if the choice bit is set to '0' + | 1 -- MBMS procedures supported by the cell if the choice bit is set to '1' + } + < DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT: bit > + < MNCI_SUPPORT: bit > + < spare bit >** + }; + +``` + +**Table 10.5.2.11a.2: DTM Information Details value part details** + +###### **MAX\_LAPDm (3 bit field)** + +This field indicates the maximum number of LAPDm frames on which a layer 3 can be segmented into and be sent on the main DCCH. It is coded as described in the SI 6 Details IE. + +###### **GPRS\_MS\_TXPWR\_MAX\_CCH (5 bits field)** + +The GPRS\_MS\_TXPWR\_MAX\_CCH field is coded as the binary representation of the "power control level" in 3GPP TS 45.005 corresponding to the maximum TX power level the MS shall use for packet resources while in dual transfer mode. This value shall be used by the Mobile Station according to 3GPP TS 45.008. + +Range: 0 to 31. + +###### **Cell identity (16 bits field)** + +The purpose of the Cell Identity is to identify a cell within a routing area. The Cell Identity is coded as the value part of the Cell Identity IE defined in 3GPP TS 24.008. + +###### **DEDICATED\_MODE\_MBMS\_NOTIFICATION\_SUPPORT (1 bit field)** + +This field is encoded as the DEDICATED\_MODE\_MBMS\_NOTIFICATION\_SUPPORT field in the GPRS Cell Options information element as defined in 3GPP TS 44.060 + +###### **MNCI\_SUPPORT (1 bit field)** + +This field is encoded as the MNCI\_SUPPORT field in the GPRS Cell Options information element as defined in 3GPP TS 44.060 + +##### **10.5.2.11b Dynamic ARFCN Mapping** + +The purpose of the *Dynamic ARFCN Mapping* information element is to provide information on ARFCN mapping to physical frequencies (see 3GPP TS 45.005). + +The *Dynamic ARFCN Mapping* is a type 4 information element with a minimum length of 6 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.060). + +Parameters GSM\_Band, ARFCN\_FIRST, BAND\_OFFSET and ARFCN\_RANGE are defined in table 10.5.2.37j. + +Spare bits in the end of the field are used to fill the last octet. + +**Table 10.5.2.11b.1: Dynamic ARFCN Mapping content** + +``` + +< Dynamic ARFCN Mapping > ::= + < LENGTH OF DYNAMIC ARFCN MAPPING : bit (8) > -- length of value part in octets + < DYNAMIC ARFCN MAPPING Description : { 1 < DYNAMIC ARFCN MAPPING > } ** 0 > + < spare bit > ** ; + +< DYNAMIC ARFCN MAPPING > ::= + < GSM_Band : bit (4) > + < ARFCN_FIRST : bit (10) > + < BAND_OFFSET : bit (10) > + < ARFCN_RANGE : bit (7) > ; + +``` + +#### 10.5.2.12 Frequency Channel Sequence + +The purpose of the *Frequency Channel Sequence* information element is to provide the absolute radio frequency channel numbers used in the mobile hopping sequence. This information element shall only be used for radio frequency channels in the primary GSM band (see 3GPP TS 45.005). + +The *Frequency Channel Sequence* information element is coded as shown in figure 10.5.2.12.1 and table 10.5.2.12.1. + +The *Frequency Channel Sequence* is a type 3 information element with 10 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------|--------------------------------|---|---|----------------------|---|---|---|----------| +| | Frequency Channel Sequence IEI | | | | | | | octet 1 | +| 0 | Lowest ARFCN | | | | | | | octet 2 | +| spare | inc skip of ARFCN 01 | | | inc skip of ARFCN 02 | | | | octet 3 | +| | inc skip of ARFCN 15 | | | inc skip of ARFCN 16 | | | | octet 10 | + +**Figure 10.5.2.12.1: Frequency Channel Sequence information element****Table 10.5.2.12.1: Frequency Channel Sequence information element** + +``` + +Lowest ARFCN (octet 2) +The lowest ARFCN field is coded as the binary representation of the +lowest absolute RF channel number appearing in the sequence of +channels used in the frequency hopping. + +Range: 1 to 124 + +All other values are reserved. + +Increment skip ARFCN n (octet 3 to 10) +The increment skip ARFCN n is coded as the binary representation of +the increment of the preceding absolute RF channel number appearing +in the sequence of channels used in the frequency hopping: + +n = 1, ..., 16. + +Range: 0 to 15 + +The value 0 indicates that the increment value is 15 but the +concerned channel is not used and the next field, i.e. Increment +skip ARFCN n+1 (if present) must be added to the increment to +determine the next absolute RF channel number in the sequence of +channels used in the frequency hopping. + +``` + +#### 10.5.2.13 Frequency List + +The purpose of the *Frequency List* information element is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence. + +The *Frequency List* information element is a type 4 information element. + +There are several formats for the *Frequency List* information element, distinguished by the "format indicator" subfield. Some formats are frequency bit maps, the others use a special encoding scheme. + +##### 10.5.2.13.1 General description + +**Table 10.5.2.13.1.1: *Frequency List* information element, general format** + +| FORMAT-ID, Format Identifier (part of octet 3) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|------------------|-----------------|---|---|---|---|---|--|--|-----------|---|---|---|---|---|--|--|------------|---|---|---|---|---|--|--|-----------|---|---|---|---|---|--|--|-----------|---|---|---|---|---|--|--|-----------|---|---|---|---|---|--|--|------------------| +| The different formats are distinguished by the FORMAT-ID field. The possible values are the following: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|
Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 format notation
0 0 X X X bit map 0
1 0 0 X X 1024 range
1 0 1 0 0 512 range
1 0 1 0 1 256 range
1 0 1 1 0 128 range
1 0 1 1 1 variable bit map
All other combinations are reserved for future use. | Bit 8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | format notation | 0 | 0 | X | X | X | | | bit map 0 | 1 | 0 | 0 | X | X | | | 1024 range | 1 | 0 | 1 | 0 | 0 | | | 512 range | 1 | 0 | 1 | 0 | 1 | | | 256 range | 1 | 0 | 1 | 1 | 0 | | | 128 range | 1 | 0 | 1 | 1 | 1 | | | variable bit map | +| Bit 8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | format notation | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | X | X | X | | | bit map 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 0 | X | X | | | 1024 range | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 1 | 0 | 0 | | | 512 range | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 1 | 0 | 1 | | | 256 range | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 1 | 1 | 0 | | | 128 range | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 1 | 1 | 1 | | | variable bit map | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may consider all values except the value for bit map 0 as reserved. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| The significance of the remaining bits depends on the FORMAT-ID. The different cases are specified in the next sub-clauses. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +##### 10.5.2.13.2 Bit map 0 format + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|----------| +| Frequency List IEI | | | | | | | | octet 1 | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | | +| Length of frequency list contents | | | | | | | | octet 2 | +| 0 | 0 | 0 0 spare | | ARFCN 124 | ARFCN 123 | ARFCN 122 | ARFCN 121 | octet 3 | +| ARFCN 120 | ARFCN 119 | ARFCN 118 | ARFCN 117 | ARFCN 116 | ARFCN 115 | ARFCN 114 | ARFCN 113 | octet 4 | +| | | | | | | | | | +| ARFCN 008 | ARFCN 007 | ARFCN 006 | ARFCN 005 | ARFCN 004 | ARFCN 003 | ARFCN 002 | ARFCN 001 | octet 18 | + +**Figure 10.5.2.13.2.1: *Frequency List* information element, bit map 0 format** + +**Table 10.5.2.13.2.1: *Frequency List* information element, bit map 0 format** + +| | +|-----------------------------------------------------------------------------------------------------------------------------| +| ARFCN N, Absolute RF Channel Number N (octet 3 etc.) | +| For a RF channel with ARFCN = N belonging to the frequency list the ARFCN N bit is coded with a "1"; N = 1, 2, .. , 124. | +| For a RF channel with ARFCN = N not belonging to the frequency list the ARFCN N bit is coded with a "0"; N = 1, 2 .. , 124. | + +##### 10.5.2.13.3 Range 1024 format + +The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0. + +![](437a88375397eec8390174b5426e99b0_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------|---|---|---|--------------------|----|---------------------|---|---------| +| Frequency List IEI | | | | | | | | octet 1 | +| Length of frequency list contents | | | | | | | | octet 2 | +| 1 | 0 | 0 | 0 | 0
FORMA
T-ID | F0 | W(1)
(high part) | | octet 3 | +| W(1) (low part) | | | | | | | | octet 4 | +| W(2) to W(3) are on 9 bits, when present | | | | | | | | | +| W(4) to W(7) are on 8 bits, when present | | | | | | | | | +| W(8) to W(15) are on 7 bits, when present | | | | | | | | | +| W(16) to W(31) are on 6 bits, when present | | | | | | | | | +| W(2 k ) to W(2 k+1 -1) are on 10-k bits when present | | | | | | | | | +| and so on | | | | | | | | | + +**Figure 10.5.2.13.3.1: *Frequency List* information element (Range 1024 format)** + +**Table 10.5.2.13.3.1: *Frequency List* information element, range 1024 format** + +F0, frequency 0 indicator (octet 3, bit 3): + +0 ARFCN 0 is not a member of the set +1 ARFCN 0 is a member of the set + +W(i), i from 1 to M (octet 3 and next): + +Each W(i) encodes a non negative integer in binary format. + +If W(k) is null, W(i) for i>k must be null also. + +Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: + +Wi denotes W(i); +Fi denotes F(i); ++ indicates the natural integer addition; +\* indicates the natural integer multiplication; +n mod m indicates the remainder of the euclidian division of n by m, ie + $0 \leq (n \bmod m) \leq m-1$ and there exists k such that + $n = (k*m) + (n \bmod m)$ ; +n smod m indicates the offset remainder of the euclidian division of n by m, ie + $1 \leq (n \text{ smod } m) \leq m$ and there exists k such that + $n = (k*m) + (n \text{ smod } m)$ ; + +``` + +F1 = W1 +F2 = (W1 - 512 + W2) smod 1023 +F3 = (W1 + W3) smod 1023 +F4 = (W1 - 512 + (W2 - 256 + W4) smod 511) smod 1023 +F5 = (W1 + (W3 - 256 + W5) smod 511) smod 1023 +F6 = (W1 - 512 + (W2 + W6) smod 511) smod 1023 +F7 = (W1 + (W3 + W7) smod 511) smod 1023 +F8 = (W1 - 512 + (W2 - 256 + (W4 - 128 + W8) smod 255) smod 511) smod 1023 +F9 = (W1 + (W3 - 256 + (W5 - 128 + W9) smod 255) smod 511) smod 1023 +F10 = (W1 - 512 + (W2 + (W6 - 128 + W10) smod 255) smod 511) smod 1023 +F11 = (W1 + (W3 + (W7 - 128 + W11) smod 255) smod 511) smod 1023 +F12 = (W1 - 512 + (W2 - 256 + (W4 + W12) smod 255) smod 511) smod 1023 +F13 = (W1 + (W3 - 256 + (W5 + W13) smod 255) smod 511) smod 1023 +F14 = (W1 - 512 + (W2 + (W6 + W14) smod 255) smod 511) smod 1023 +F15 = (W1 + (W3 + (W7 + W15) smod 255) smod 511) smod 1023 +F16 = (W1 - 512 + (W2 - 256 + (W4 - 128 + (W8 - 64 + W16) smod 127) smod 255) smod 511) smod 1023 + +``` + +More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): + +``` +INDEX := K; +J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); +N := W(INDEX); +while INDEX>1 loop + if 2*INDEX < 3*J then + INDEX := INDEX - J/2; -- left child + N := (N + W(PARENT) + 1024/J - 2) mod (2048/J - 1) + 1; + else + INDEX := INDEX - J; -- right child + N := (N + W(PARENT) + 2048/J - 2) mod (2048/J - 1) + 1; + end if; + J := J/2; +end loop; +F(K) := N; +``` + +##### 10.5.2.13.4 Range 512 format + +The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0. + +![](8bdf315853992d21f389da554f3a8215_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------|---|---|---|---|-----------------|---------| +| Frequency List IEI | | | | | | | | octet 1 | +| Length of frequency list contents | | | | | | | | octet 2 | +| 1 | 0 | 0 | 0 | 1 | 0 | 0 | ORIG-ARFCN high | octet 3 | +| ORIG-ARFCN (middle part) | | | | | | | | octet 4 | +| ORIG-ARFCN low | W(1) (high part) | | | | | | | octet 5 | +| W(1) (low part) | | W(2) (high part) | | | | | | octet 6 | +| W(2) to W(3) are on 8 bits, when present
W(4) to W(7) are on 7 bits, when present
W(8) to W(15) are on 6 bits, when present
W(16) to W(31) are on 5 bits, when present
W(2 k ) to W(2 k+1 -1) are on 9-k bits when present
and so on | | | | | | | | | + +Figure 10.5.2.13.4.1: *Frequency List* information element (Range 512 format) + +**Table 10.5.2.13.4.1: Frequency List information element, range 512 format** + +ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) + +This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. + +W(i), i from 1 to M (octet 5 and next): + +Each W(i) encodes a non negative integer in binary format. + +If W(k) is null, W(i) for i>k must be null also. + +Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: + +Wi denotes W(i); W0 denotes the value of ORIG-ARFCN + Fi denotes F(i); + + indicates the natural integer addition; + \* indicates the natural integer multiplication; + +n mod m indicates the remainder of the euclidian division of n by m, ie + $0 \leq (n \bmod m) \leq m-1$ and there exists k such that + $n = (k*m) + (n \bmod m)$ ; + +n smod m indicates the offset remainder of the euclidian division of n by m, ie + $1 \leq (n \text{ smod } m) \leq m$ and there exists k such that + $n = (k*m) + (n \text{ smod } m)$ ; + +``` + +F1 = (W0 + W1) mod 1024 +F2 = (W0 + (W1 - 256 + W2) smod 511) mod 1024 +F3 = (W0 + (W1 + W3) smod 511) mod 1024 +F4 = (W0 + (W1 - 256 + (W2 - 128 + W4) smod 255) smod 511) mod 1024 +F5 = (W0 + (W1 + (W3 - 128 + W5) smod 255) smod 511) mod 1024 +F6 = (W0 + (W1 - 256 + (W2 + W6) smod 255) smod 511) mod 1024 +F7 = (W0 + (W1 + (W3 + W7) smod 255) smod 511) mod 1024 +F8 = (W0 + (W1 - 256 + (W2 - 128 + (W4 - 64 + W8) smod 127) smod 255) smod 511) mod 1024 +F9 = (W0 + (W1 + (W3 - 128 + (W5 - 64 + W9) smod 127) smod 255) smod 511) mod 1024 +F10 = (W0 + (W1 - 256 + (W2 + (W6 - 64 + W10) smod 127) smod 255) smod 511) mod 1024 +F11 = (W0 + (W1 + (W3 + (W7 - 64 + W11) smod 127) smod 255) smod 511) mod 1024 +F12 = (W0 + (W1 - 256 + (W2 - 128 + (W4 + W12) smod 127) smod 255) smod 511) mod 1024 +F13 = (W0 + (W1 + (W3 - 128 + (W5 + W13) smod 127) smod 255) smod 511) mod 1024 +F14 = (W0 + (W1 - 256 + (W2 + (W6 + W14) smod 127) smod 255) smod 511) mod 1024 +F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 127) smod 255) smod 511) mod 1024 +F16 = (W0 + (W1 - 256 + (W2 - 128 + (W4 - 64 + (W8 - 32 + W16) smod 63) smod 127) smod 255) smod 511) mod 1024 +F17 = (W0 + (W1 + (W3 - 128 + (W5 - 64 + (W9 - 32 + W17) smod 63) smod 127) smod 255) smod 511) mod 1024 + +``` + +More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): + +``` + +INDEX := K; +J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); +N := W(INDEX); +while INDEX>1 loop + if 2*INDEX < 3*J then + INDEX := INDEX - J/2; -- left child + N := (N + W(PARENT) + 512/J - 2) mod (1024/J - 1) + 1; + else + INDEX := INDEX - J; -- right child + N := (N + W(PARENT) + 1024/J - 2) mod (1024/J - 1) + 1; + end if; + J := J/2; +end loop; +F(K) := N; + +``` + +##### 10.5.2.13.5 Range 256 format + +The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0. + +![](87f8b579bc67022e8dd0a0a50585fd4d_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---|---|---|---|---|-----------------|---------| +| Frequency List IEI | | | | | | | | octet 1 | +| Length of frequency list contents | | | | | | | | octet 2 | +| 1 | 0 | 0 | 0 | 1 | 0 | 1 | ORIG-ARFCN high | octet 3 | +| FORMAT-ID | | | | | | | | | +| ORIG-ARFCN (middle part) | | | | | | | | octet 4 | +| ORIG-ARFCN low | W(1) (high part) | | | | | | | octet 5 | +| W(1) low | W(2) | | | | | | | octet 6 | +| W(2) to W(3) are on 7 bits, when present
W(4) to W(7) are on 6 bits, when present
W(8) to W(15) are on 5 bits, when present
W(16) to W(31) are on 4 bits, when present
W(2 k ) to W(2 k+1 -1) are on 8-k bits when present
and so on | | | | | | | | | + +Figure 10.5.2.13.5.1: *Frequency List information element (Range 256 format)* + +**Table 10.5.2.13.5.1: Frequency List information element, range 256 format** + +ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) + +This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. + +W(i), i from 1 to M (octet 5 and next): + +Each W(i) encodes a non negative integer in binary format. + +If W(k) is null, W(i) for i>k must be null also. + +Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: + +Wi denotes W(i); W0 denotes the value of ORIG-ARFCN + +Fi denotes F(i); + ++ indicates the natural integer addition; + +\* indicates the natural integer multiplication; + +n mod m indicates the remainder of the euclidian division of n by m, ie + $0 \leq (n \bmod m) \leq m-1$ and there exists k such that + $n = (k*m) + (n \bmod m)$ ; + +n smod m indicates the offset remainder of the euclidian division of n by m, ie + $1 \leq (n \bmod m) \leq m$ and there exists k such that + $n = (k*m) + (n \bmod m)$ ; + +``` + +F1 = (W0 + W1) mod 1024 +F2 = (W0 + (W1 - 128 + W2) smod 255) mod 1024 +F3 = (W0 + (W1 + W3) smod 255) mod 1024 +F4 = (W0 + (W1 - 128 + (W2 - 64 + W4) smod 127) smod 255) mod 1024 +F5 = (W0 + (W1 + (W3 - 64 + W5) smod 127) smod 255) mod 1024 +F6 = (W0 + (W1 - 128 + (W2 + W6) smod 127) smod 255) mod 1024 +F7 = (W0 + (W1 + (W3 + W7) smod 127) smod 255) mod 1024 +F8 = (W0 + (W1 - 128 + (W2 - 64 + (W4 - 32 + W8) smod 63) smod 127) smod 255) mod 1024 +F9 = (W0 + (W1 + (W3 - 64 + (W5 - 32 + W9) smod 63) smod 127) smod 255) mod 1024 +F10 = (W0 + (W1 - 128 + (W2 + (W6 - 32 + W10) smod 63) smod 127) smod 255) mod 1024 +F11 = (W0 + (W1 + (W3 + (W7 - 32 + W11) smod 63) smod 127) smod 255) mod 1024 +F12 = (W0 + (W1 - 128 + (W2 - 64 + (W4 + W12) smod 63) smod 127) smod 255) mod 1024 +F13 = (W0 + (W1 + (W3 - 64 + (W5 + W13) smod 63) smod 127) smod 255) mod 1024 +F14 = (W0 + (W1 - 128 + (W2 + (W6 + W14) smod 63) smod 127) smod 255) mod 1024 +F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 63) smod 127) smod 255) mod 1024 +F16 = (W0 + (W1 - 128 + (W2 - 64 + (W4 - 32 + (W8 - 16 + W16) smod 31) smod 63) smod 127) smod 255) mod 1024 +F17 = (W0 + (W1 + (W3 - 64 + (W5 - 32 + (W9 - 16 + W17) smod 31) smod 63) smod 127) smod 255) mod 1024 +F18 = (W0 + (W1 - 128 + (W2 + (W6 - 32 + (W10 - 16 + W18) smod 31) smod 63) smod 127) smod 255) mod 1024 +F19 = (W0 + (W1 + (W3 + (W7 - 32 + (W11 - 16 + W19) smod 31) smod 63) smod 127) smod 255) mod 1024 +F20 = (W0 + (W1 - 128 + (W2 - 64 + (W4 + (W12 - 16 + W20) smod 31) smod 63) smod 127) smod 255) mod 1024 +F21 = (W0 + (W1 + (W3 - 64 + (W5 + (W13 - 16 + W21) smod 31) smod 63) smod 127) smod 255) mod 1024 + +``` + +More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): + +``` + +INDEX := K; +J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); +N := W(INDEX); +while INDEX>1 loop + if 2*INDEX < 3*J then -- left child + INDEX := INDEX - J/2; + N := (N + W(INDEX) + 256/J - 2) mod (512/J - 1) + 1; + else -- right child + INDEX := INDEX - J; + N := (N + W(INDEX) + 512/J - 2) mod (512/J - 1) + 1; + end if; + J := J/2; +end loop; +F(K) := (W(0) + N) mod 1024; + +``` + +##### 10.5.2.13.6 Range 128 format + +The information element contains a header, and $W(1)$ to $W(M)$ for some $M$ . If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0. + +![](274c9f072648ced2fb71212d6e30fea9_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---|---|---|---|---|-----------------|---------| +| Frequency List IEI | | | | | | | | octet 1 | +| Length of frequency list contents | | | | | | | | octet 2 | +| 1 | 0 | 0 | 0 | 1 | 1 | 0 | ORIG-ARFCN high | octet 3 | +| ORIG-ARFCN (middle part) | | | | | | | | octet 4 | +| ORIG-ARFCN low | W(1) (high part) | | | | | | | octet 5 | +| $W(2)$ to $W(3)$ are on 6 bits, when present
$W(4)$ to $W(7)$ are on 5 bits, when present
$W(8)$ to $W(15)$ are on 4 bits, when present
$W(16)$ to $W(31)$ are on 3 bits, when present
$W(2^k)$ to $W(2^{k+1}-1)$ are on $7-k$ bits when present
and so on | | | | | | | | | + +Figure 10.5.2.13.6.1: *Frequency List* information element (Range 128 format) + +Table 10.5.2.13.6.1: *Frequency List* information element, range 128 format + +ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) + +This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. + +$W(i)$ , $i$ from 1 to $M$ (octet 5 and next): + +Each $W(i)$ encodes a non negative integer in binary format. + +If $W(k)$ is null, $W(i)$ for $i > k$ must be null also. + +Each non null $W(k)$ allows to compute, together with some previous $W(i)$ the ARFCN $F(k)$ of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: + +$W_i$ denotes $W(i)$ ; $W_0$ denotes the value of ORIG-ARFCN + $F_i$ denotes $F(i)$ ; + $+$ indicates the natural integer addition; + $*$ indicates the natural integer multiplication; + $n \bmod m$ indicates the remainder of the euclidian division of $n$ by $m$ , ie + $0 \leq (n \bmod m) \leq m-1$ and there exists $k$ such that + $n = (k*m) + (n \bmod m)$ ; + $n \text{ smod } m$ indicates the offset remainder of the euclidian division of $n$ by $m$ , ie + $1 \leq (n \text{ smod } m) \leq m$ and there exists $k$ such that + $n = (k*m) + (n \text{ smod } m)$ ; + +``` + +F1 = (W0 + W1) mod 1024 +F2 = (W0 + (W1 - 64 + W2) smod 127) mod 1024 +F3 = (W0 + (W1 + W3) smod 127) mod 1024 +F4 = (W0 + (W1 - 64 + (W2 - 32 + W4) smod 63) smod 127) mod 1024 +F5 = (W0 + (W1 + (W3 - 32 + W5) smod 63) smod 127) mod 1024 +F6 = (W0 + (W1 - 64 + (W2 + W6) smod 63) smod 127) mod 1024 +F7 = (W0 + (W1 + (W3 + W7) smod 63) smod 127) mod 1024 +F8 = (W0 + (W1 - 64 + (W2 - 32 + (W4 - 16 + W8) smod 31) smod 63) smod 127) mod 1024 +F9 = (W0 + (W1 + (W3 - 32 + (W5 - 16 + W9) smod 31) smod 63) smod 127) mod 1024 +F10 = (W0 + (W1 - 64 + (W2 + (W6 - 16 + W10) smod 31) smod 63) smod 127) mod 1024 +F11 = (W0 + (W1 + (W3 + (W7 - 16 + W11) smod 31) smod 63) smod 127) mod 1024 +F12 = (W0 + (W1 - 64 + (W2 - 32 + (W4 + W12) smod 31) smod 63) smod 127) mod 1024 +F13 = (W0 + (W1 + (W3 - 32 + (W5 + W13) smod 31) smod 63) smod 127) mod 1024 +F14 = (W0 + (W1 - 64 + (W2 + (W6 + W14) smod 31) smod 63) smod 127) mod 1024 +F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 31) smod 63) smod 127) mod 1024 +F16 = (W0 + (W1 - 64 + (W2 - 32 + (W4 - 16 + (W8 - 8 + W16) smod 15) smod 31) smod 63) smod 127) mod 1024 +F17 = (W0 + (W1 + (W3 - 32 + (W5 - 16 + (W9 - 8 + W17) smod 15) smod 31) smod 63) smod 127) mod 1024 +F18 = (W0 + (W1 - 64 + (W2 + (W6 - 16 + (W10 - 8 + W18) smod 15) smod 31) smod 63) smod 127) mod 1024 +F19 = (W0 + (W1 + (W3 + (W7 - 16 + (W11 - 8 + W19) smod 15) smod 31) smod 63) smod 127) mod 1024 +F20 = (W0 + (W1 - 64 + (W2 - 32 + (W4 + (W12 - 8 + W20) smod 15) smod 31) smod 63) smod 127) mod 1024 +F21 = (W0 + (W1 + (W3 - 32 + (W5 + (W13 - 8 + W21) smod 15) smod 31) smod 63) smod 127) mod 1024 +F22 = (W0 + (W1 - 64 + (W2 + (W6 + (W14 - 8 + W22) smod 15) smod 31) smod 63) smod 127) mod 1024 +F23 = (W0 + (W1 + (W3 + (W7 + (W15 - 8 + W23) smod 15) smod 31) smod 63) smod 127) mod 1024 +F24 = (W0 + (W1 - 64 + (W2 - 32 + (W4 - 16 + (W8 + W24) smod 15) smod 31) smod 63) smod 127) mod 1024 +F25 = (W0 + (W1 + (W3 - 32 + (W5 - 16 + (W9 + W25) smod 15) smod 31) smod 63) smod 127) mod 1024 +F26 = (W0 + (W1 - 64 + (W2 + (W6 - 16 + (W10 + W26) smod 15) smod 31) smod 63) smod 127) mod 1024 +F27 = (W0 + (W1 + (W3 + (W7 - 16 + (W11 + W27) smod 15) smod 31) smod 63) smod 127) mod 1024 +F28 = (W0 + (W1 - 64 + (W2 - 32 + (W4 + (W12 + W28) smod 15) smod 31) smod 63) smod 127) mod 1024 +F29 = (W0 + (W1 + (W3 - 32 + (W5 + (W13 + W29) smod 15) smod 31) smod 63) smod 127) mod 1024 + +``` + +More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): + +``` + +INDEX := K; +J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); +N := W(INDEX); +while INDEX > 1 loop + if 2*INDEX < 3*J then + INDEX := INDEX - J/2; + N := (N + W(INDEX) + 128/J - 2) mod (256/J - 1) + 1; + else + INDEX := INDEX - J; + N := (N + W(INDEX) + 256/J - 2) mod (256/J - 1) + 1; + end if; + J := J/2; +end loop; +F(K) := (W(0) + N) mod 1024; + +``` + +##### 10.5.2.13.7 Variable bit map format + +![](1fd763be1b7a05b52e554f0583617642_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-----------------|---------| +| Frequency List IEI | | | | | | | | octet 1 | +| Length of frequency list contents | | | | | | | | octet 2 | +| 1 | 0 | 0 | 0 | 1 | 1 | 1 | ORIG-ARFCN high | octet 3 | +| FORMAT-ID (continued) | | | | | | | | | +| ORIG-ARFCN (middle part) | | | | | | | | octet 4 | +| ORIG-ARFCN low | RRFCN 1 | RRFCN 2 | RRFCN 3 | RRFCN 4 | RRFCN 5 | RRFCN 6 | RRFCN 7 | octet 5 | +| RRFCN 8k-40 | RRFCN 8k-39 | RRFCN 8k-38 | RRFCN 8k-37 | RRFCN 8k-36 | RRFCN 8k-35 | RRFCN 8k-34 | RRFCN 8k-33 | octet k | + +Figure 10.5.2.13.7.1: *Frequency List* information element, variable bit map formatTable 10.5.2.13.7.1: *Frequency List* information element, variable bit map format + +ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) + +This field encodes the ARFCN of one frequency belonging to the set. This value is also used as origin of the bit map to generate all the other frequencies. + +RRFCN N, relative radio frequency channel number N (octet 5 etc.) + +For a RF channel with ARFCN = (ORIG-ARFCN + N) mod 1024 belonging to the set, RRFCN N bit is coded with a "1"; N = 1, 2, .. , 8M+7 with $1 \leq M \leq 127$ + +For a RF channel with ARFCN = (ORIG-ARFCN + N) mod 1024 not belonging to the set, RRFCN N bit is coded with a "0"; N = 1, 2, .. , 8M+7 with $1 \leq M \leq 127$ + +#### 10.5.2.14 Frequency Short List + +The purpose of the *Frequency Short List* information element is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence, in a small fixed length information element to obtain when possible the HANDOVER COMMAND message in a single block. + +The *Frequency Short List* information element is a type 3 information element of 10 octet length. + +This element is encoded exactly as the *Frequency List* information element, except that it has a fixed length instead of a variable length and does not contain a length indicator and that it shall not be encoded in bitmap 0 format. + +##### 10.5.2.14a Frequency Short List 2 + +The purpose of the *Frequency Short List 2* information element is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence, in a small fixed length information element to obtain the SYSTEM INFORMATION TYPE 11 and NOTIFICATION FACCH messages in a single block. + +The *Frequency Short List* information element is a type 3 information element of 8 octet length. + +This element is encoded exactly as the *Frequency List* information element, except that it has a fixed length instead of a variable length and does not contain a length indicator and that it shall not be encoded in bitmap 0 format. + +##### 10.5.2.14b Group Channel Description + +The purpose of the *Group Channel Description* information element is to provide a description of an allocable voice group call or voice broadcast call channel together with its SACCH and that part of the RF channels belonging to the cell allocation which is used in the mobile hopping sequence if applicable. + +The *Group Channel Description* information element is coded as shown in figure 10.5.2.14b.1 and table 10.5.2.14b.1. + +The *Group Channel Description* is a type 4 information element with 5 to 13 octets length. + +![](c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|-----------------|-----------------|-----------------|------------------|-----------------|-------------------|-----------------|-----------| +| Group Channel Description IEI | | | | | | | | octet 1 | +| Length of Group Channel Description contents | | | | | | | | octet 2 | +| Channel type and TDMA offset | | | | TN | | | | octet 3 | +| TSC | | | H=1-> | MAIO (high part) | | | | octet 4 | +| | | | --- H --- | ----- | | | | | +| MAIO (low part) | | | H=0-> | 0 spare | | ARFCN (high part) | | octet 5 | +| | | | HSN | | | | | | +| ARFCN (low part) | | | | | | | | | +| MA
C
8n | MA
C
8n-1 | MA
C
8n-2 | MA
C
8n-3 | MA
C
8n-4 | MA
C
8n-5 | MA
C
8n-6 | MA
C
8n-7 | octet 6 | +| | | | | | | | | | +| MA
C
008 | MA
C
007 | MA
C
006 | MA
C
005 | MA
C
004 | MA
C
003 | MA
C
002 | MA
C
001 | octet n+5 | + +Figure 10.5.2.14b.1: *Group Channel Description* information element + +**Table 10.5.2.14b.1: Group Channel Description information element** + +|

Channel type and TDMA offset (octet 3)

Bits

8 7 6 5 4
0 0 0 0 1 TCH/FS + ACCHs (speech codec version 1)
0 0 0 1 T TCH/HS + ACCHs (speech codec version 1)
1 0 0 0 0 TCH/FS + ACCHs (speech codec version 2)
1 0 0 0 1 TCH/AFS + ACCHs (speech codec version 3)
1 0 0 1 T TCH/AHS + ACCHs (speech codec version 3)
0 0 1 T T SDCCH/4 + SACCH/C4
0 1 T T T SDCCH/8 + SACCH/C8

The T bits indicate the subchannel number coded in binary.
All other values are reserved for future use.

A mobile station that is not able to recognise the channel type when set to a value that is defined as 'reserved for future use' in earlier versions of this specification, may be able to join the group call from the signalling point of view but is not able to decode any speech.

| 8 | 7 | 6 | 5 | 4 | | 0 | 0 | 0 | 0 | 1 | TCH/FS + ACCHs (speech codec version 1) | 0 | 0 | 0 | 1 | T | TCH/HS + ACCHs (speech codec version 1) | 1 | 0 | 0 | 0 | 0 | TCH/FS + ACCHs (speech codec version 2) | 1 | 0 | 0 | 0 | 1 | TCH/AFS + ACCHs (speech codec version 3) | 1 | 0 | 0 | 1 | T | TCH/AHS + ACCHs (speech codec version 3) | 0 | 0 | 1 | T | T | SDCCH/4 + SACCH/C4 | 0 | 1 | T | T | T | SDCCH/8 + SACCH/C8 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------|---|-------------------|------------------------------------------|--------------------|---|---|---|---|---|-----------------------------------------|---|---|---|---|---|-----------------------------------------|---|---|---|---|---|-----------------------------------------|---|---|---|---|---|------------------------------------------|---|---|---|---|---|------------------------------------------|---|---|---|---|---|--------------------|---|---|---|---|---|--------------------| +| 8 | 7 | 6 | 5 | 4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 0 | 1 | TCH/FS + ACCHs (speech codec version 1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 1 | T | TCH/HS + ACCHs (speech codec version 1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 0 | 0 | 0 | TCH/FS + ACCHs (speech codec version 2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 0 | 0 | 1 | TCH/AFS + ACCHs (speech codec version 3) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 0 | 1 | T | TCH/AHS + ACCHs (speech codec version 3) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 1 | T | T | SDCCH/4 + SACCH/C4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | T | T | T | SDCCH/8 + SACCH/C8 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

TN, Timeslot number (octet 3)

The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010.

Range: 0 to 7.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

TSC, Training Sequence Code (octet 4)

The TSC field is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002

Range: 0 to 7.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

H, Hopping channel (octet 4)

Bit

5
0 Single RF channel
1 RF hopping channel

NOTE 1: The value of H affects the semantics of the channel selector field
NOTE 2: If H=0, the information element terminates with octet 5

| 5 | | 0 | Single RF channel | 1 | RF hopping channel | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | Single RF channel | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | RF hopping channel | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Channel selector (octet 4 and 5)

H = "0": The channel selector field consists of the absolute RF channel number

Octet 4

Bits

4 3
0 0 Spare
| 4 | 3 | | 0 | 0 | Spare | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4 | 3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | Spare | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

ARFCN, (octet 4, bits 2 and 1, and octet 5, bits 8 to 1)

The ARFCN is coded as the binary representation of the absolute RF channel number

Range: 0 to 1023

H = "1": The channel selector field consists of the mobile allocation index offset, MAIO, and the hopping sequence number, HSN.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MAIO, (octet 4 bit 4 to 1 high part and octet 5 bit 8 to 7 low part)

The MAIO field is coded as the binary representation of the mobile allocation index offset as defined in 3GPP TS 45.002.

Range: 0 to 63.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

HSN, (octet 5 bit 6 to 1)

The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 45.002

Range 0 to 63.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +MA C i, Mobile allocation RF channel i (octet 6 etc.), i = 1, 2, ..., NF + The MA C i bit indicates whether or not the Mobile allocation frequency list includes the i'th frequency in the cell allocation frequency list. In the cell allocation frequency list the absolute RF channel numbers are placed in increasing order of ARFCN, except that ARFCN 0, if included in the set, is put in the last position in the list. + +For a RF channel belonging to the mobile allocation the MA C i bit is coded with a "1"; i = 1, 2, ..., NF. + +For a RF channel not belonging to the mobile allocation the MA C i bit is coded with a "0"; i = 1, 2, ..., NF. + +If NF mod 8 <> 0 then bits NF to 8n in octet 6 must be coded with a "0" in each. + +##### 10.5.2.14c GPRS Resumption + +The purpose of the *GPRS Resumption* information element is to indicate whether the network has successfully resumed GPRS services or not. + +The *GPRS Resumption* information element is coded as shown in figure 10.5.2.14c.1 and table 10.5.2.14c.1. + +The *GPRS Resumption* is a type 1 information element. + +![](b1a5e556856e7d7d0a4a97692c70247a_img.jpg) + +| | | | | | | | | | +|---------------------|---|---|---|---|------------|---|-----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| GPRS resumption IEI | | | | 0 | Spare
0 | 0 | ACK | Octet 1 | + +**Figure 10.5.2.14c.1: GPRS Resumption information element** + +**Table 10.5.2.14c.1: GPRS Resumption information element** + +The ACK field (1 bit) is the binary acknowledge of a successful resumption of GPRS services: + +- | | | +|---|------------------------------------------------------------| +| 0 | resumption of GPRS services not successfully acknowledged; | +| 1 | resumption of GPRS services successfully acknowledged. | + +##### 10.5.2.14d GPRS broadcast information + +The *GPRS broadcast information* information element provides the mobile station with relevant GPRS information needed for correct DTM operation. This information element is contained in messages addressed to mobile stations supporting GPRS and DTM. + +The *GPRS broadcast information* information element is coded as shown in figure 10.5.2.14d.1 and tables 10.5.2.14d.1 and 10.5.2.14d.2. + +The *GPRS broadcast information* is a type 4 information element with a minimum length of 7 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below. + +![](0ebd24d723abddc0387f7c549449c8e3_img.jpg) + +| | | | | | | | | | +|-------------------------------------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| GPRS Broadcast Information IEI | | | | | | | | octet 1 | +| Length of GPRS Broadcast Information value part | | | | | | | | octet 2 | +| GPRS Broadcast Information value part | | | | | | | | octet 3 - n | + +**Figure 10.5.2.14d.1: GPRS Broadcast Information information element** + +**Table 10.5.2.14d.1: GPRS broadcast information value part** + +``` +< GPRS broadcast information value part > ::= + < GPRS Cell Options : < GPRS Cell Options IE > > + < GPRS Power Control Parameters : < GPRS Power Control Parameters IE > > + < spare bit >**; +``` + +**Table 10.5.2.14d.2: GPRS broadcast information value part details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------| +| GPRS Cell Options
The GPRS Cell Option information element is defined in 3GPP TS 44.060. | +| GPRS Power Control Parameters
The GPRS Power Control Parameters information element is defined in 3GPP TS 44.060. | + +#### 10.5.2.14e Enhanced DTM CS Release Indication + +The purpose of the *Enhanced DTM CS Release Indication* information element is to indicate whether the mobile station is allowed to enter packet transfer mode or not, when the RR connection is released while in dual transfer mode. + +The *Enhanced DTM CS Release Indication* information element is coded as shown in figure 10.5.2.14e.1 and table 10.5.2.14e.1. + +The *Enhanced DTM CS Release Indication* is a type 1 information element. + +![](59ddd2018cd0efd2c932ccf0dfc2a5fd_img.jpg) + +| | | | | | | | | | +|----------------------------------------|---|---|---|---|------------|---|-----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Enhanced DTM CS Release Indication IEI | | | | 0 | Spare
0 | | IND | Octet 1 | + +**Figure 10.5.2.14e.1: Enhanced DTM CS Release Indication information element****Table 10.5.2.14e.1: Enhanced DTM CS Release Indication information element** + +The IND field (1 bit) is the binary indication whether the mobile station is allowed to enter packet transfer mode directly after the release of the RR connection: + +- 0 the mobile station is not allowed to continue in packet transfer mode; +- 1 the mobile station is allowed to continue in packet transfer mode. + +##### 10.5.2.14f Group Channel Description 2 + +The purpose of the *Group Channel Description 2* information element is to provide a description of an allocatable voice group call channel together with its SACCH and the list of the absolute radio frequency channel numbers used in a frequency hopping sequence, in a small fixed length information element. + +The *Group Channel Description 2* information element is coded as shown in figure 10.5.2.14f.1 and table 10.5.2.14f.1. + +The *Group Channel Description 2* is a type 4 information element with the value part that has fixed length of 11 octets. + +![](08282b490d242bfa2043a339d2b9cdcc_img.jpg) + +| | | | | | | | | | +|----------------------------------------------------------------------|---|-----|------------|------------------|---|----|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Group Channel Description 2 IEI | | | | | | | | octet 1 | +| Length of Group Channel Description 2 | | | | | | | | octet 2 | +| Channel type and TDMA offset | | | | MAIO (high part) | | TN | | octet 3 | +| TSC | | | 0
spare | | | | | octet 4 | +| MAIO
(low part) | | HSN | | | | | | octet 5 | +| Same coding as Frequency Short List 2 (sub-clause 10.5.2.14a) | | | | | | | | octet 6 | +| | | | | | | | | octet 13 | + +**Figure 10.5.2.14f.1: Group Channel Description 2 information element** + +**Table 10.5.2.14f.1: Group Channel Description2 information element** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Channel type and TDMA offset (octet 3)
Bits
8 7 6 5 4
0 0 0 0 1 TCH/FS + ACCHs (speech codec version 1)
0 0 0 1 T TCH/HS + ACCHs (speech codec version 1)
1 0 0 0 0 TCH/FS + ACCHs (speech codec version 2)
1 0 0 0 1 TCH/AFS + ACCHs (speech codec version 3)
1 0 0 1 T TCH/AHS + ACCHs (speech codec version 3)
0 0 1 T T SDCCH/4 + SACCH/C4
0 1 T T T SDCCH/8 + SACCH/C8

The T bits indicate the subchannel number coded in binary.
All other values are reserved for future use.

A mobile station that is not able to recognise the channel type when set to a value that is defined as 'reserved for future use' in earlier versions of this specification, may be able to join the group call from the signalling point of view but is not able to decode any speech. | +| TN, Timeslot number (octet 3)
The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010.

Range: 0 to 7. | +| TSC, Training Sequence Code (octet 4)
The TSC field is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002

Range: 0 to 7. | +| MAIO, (octet 4 bit 4 to 1 high part and octet 5 bit 8 to 7 low part)
The MAIO field is coded as the binary representation of the mobile allocation index offset as defined in 3GPP TS 45.002.

Range: 0 to 63. | +| HSN, (octet 5)
The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 45.002
Range 0 to 63. | +| Octet 6 to octet 13 have the same coding as Frequency Short List 2 (sub-clause 10.5.2.14a) | + +#### 10.5.2.15 Handover Reference + +The purpose of the *Handover Reference* information element is to provide a handover reference value used for access identification. + +The *Handover Reference* information element is coded as shown in figure 10.5.2.15.1 and table 10.5.2.15.1. + +The *Handover Reference* is a type 3 information element with 2 octets length. + +![](3c4b75cb7b7c07754e9dc980da012b8d_img.jpg) + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Handover Reference IEI | | | | | | | | octet 1 | +| Handover reference value | | | | | | | | octet 2 | + +**Figure 10.5.2.15.1: Handover Reference information element****Table 10.5.2.15.1: Handover Reference information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------| +| Handover reference value (octet 2)
The handover reference value field is coded using binary representation.

Range: 0 to 255. | +|----------------------------------------------------------------------------------------------------------------------------------------| + +#### 10.5.2.16 IA Rest Octets + +The *IA Rest Octets* information element contains spare bits and possibly either a *packet uplink assignment* construction, a *packet downlink assignment* construction, a *second part packet assignment* construction, a *frequency parameters, before time* or a *multiple blocks packet downlink assignment* construction. + +The *frequency parameters, before time* construction combines a mobile allocation (see sub-clause 10.5.2.21) and a MAIO (see the *channel description* information element). + +The *IA Rest Octets* information element is coded according to the syntax specified below and described in table 10.5.2.16.1. + +The *IA Rest Octets* information element is a type 5 information element with 0-11 octets length. + +``` + + ::= +{ + LL < Compressed_Inter_RAT_HO_INFO_IND > + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < Implicit Reject PS : bit > + < PEO_BCCH_CHANGE_MARK : bit (2) > + < RCC : bit (3) > + } + + | LH + { + 00 < EGPRS Packet Uplink Assignment > + | 01 < Multiple Blocks Packet Downlink Assignment > + | 1 -- reserved for future use (however the value 7C for the first octet shall not be used) + } + + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < Implicit Reject PS : bit > + < PEO_BCCH_CHANGE_MARK : bit (2) > + < RCC : bit (3) > + } + + | HL < Length of frequency parameters : bit string (6) > + < Frequency Parameters, before time > + < Compressed_Inter_RAT_HO_INFO_IND > + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < Implicit Reject PS : bit > + < PEO_BCCH_CHANGE_MARK : bit (2) > + < RCC : bit (3) > + } + + | HH { + 00 < Packet Uplink Assignment > + | 01 < Packet Downlink Assignment > + | 1 < Second Part Packet Assignment > + } + + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 10 + < Implicit Reject CS : bit > + < Implicit Reject PS : bit > + } + + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < PEO_BCCH_CHANGE_MARK : bit (2) > + < RCC : bit (3) > + } + +} +-- Additions for Rel-14 +{ 0 | 1 < Multilateration Information Request : bit (1) > } +-- Additions for Release 15 +{ 0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } +; + +``` + +``` + +< EGPRS Packet Uplink Assignment > ::= +< Extended RA : bit (5) > +{ 0 | 1 < Access Technologies Request : Access Technologies Request struct > } + +{ + 1 < TFI_ASSIGNMENT : bit (5) > + < POLLING : bit > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < USF : bit (3) > + < USF_GRANULARITY : bit > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + < EGPRS CHANNEL_CODING_COMMAND : < EGPRS Modulation and Coding IE >> + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + < RESEGMENT : bit (1) > + < EGPRS Window Size : < EGPRS Window Size IE >> + { 0 | 1 < ALPHA : bit (4) > + < GAMMA : bit (5) > } + { 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > } + { 0 | 1 < TBF_STARTING_TIME : bit (16) > } + { + null | L -- Receiver compatible with earlier release + | H -- Additions for Rel-7 + { 0 -- An uplink BTTI TBF is assigned + { 0 -- '0' indicates that FANR is not activated + | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < REPORTED TIMESLOTS : bit (8) > + < TSH : bit (2) > } } + | 1 -- An uplink RTTI TBF is assigned + < RTTI USF Mode : bit(1) > + < PDCH PAIR INDICATION : bit(3) > + < Additional_USF : bit (3) >*(1-val(RTTI USF MODE)) + { 0 -- One PDCH Pair assigned + | 1 < USF2 : bit(3) > -- Two PDCH Pairs assigned + < Additional_USF2 : bit (3) >*(1-val(RTTI USF MODE)) } + { 0 -- SSN-based encoding is selected + | 1 < REPORTED TIMESLOTS : bit (8) > -- Time-based encoding is selected + < TSH : bit (2) > } + } + } + | 0 -- Multi Block Allocation + { 0 | 1 < ALPHA : bit (4) > } + < GAMMA : bit (5) > + < TBF_STARTING_TIME : bit (16) > + < NUMBER OF RADIO BLOCKS ALLOCATED : bit (2) > + { 0 | 1 < P0 : bit (4) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < PR_MODE : bit (1) > } + { + null | L -- Receiver compatible with earlier release + | H -- Additions for Rel-6 + { 0 | 1 < PFI : bit (7) > } + } +} ; + + ::= +-- recursive structure allows any combination of Access technologies +< Access Technology Type : bit (4) > +{ 0 | 1 < Access Technologies Request struct > } ; + +``` + +``` + +< Packet Uplink Assignment > ::= + { 1 + < TFI_ASSIGNMENT : bit (5) > + < POLLING : bit > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be + used. + < USF : bit (3) > + < USF_GRANULARITY : bit > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + < CHANNEL_CODING_COMMAND : bit (2) > + < TLLI_BLOCK_CHANNEL_CODING : bit > + { 0 | 1 < ALPHA : bit (4) > } + < GAMMA : bit (5) > + { 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > } + { 0 | 1 < TBF_STARTING_TIME : bit (16) > } + + | 0 -- Single Block Allocation + { 0 | 1 < ALPHA : bit (4) > } + < GAMMA : bit (5) > + 0 1 -- See note + < TBF_STARTING_TIME : bit (16) > + { L | H < P0 : bit (4) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be + used. + < PR_MODE : bit (1) > } + } + { null | L -- Receiver compatible with earlier + release + | H -- Additions for R99 + { 0 | 1 < Extended RA : bit (5) > } + } + { null | L -- Receiver compatible with earlier release + | H -- Additions for Rel-6 + { 0 | 1 < PFI : bit (7) > } + } ; + +``` + +``` + +< Packet Downlink Assignment > ::= + < TLLI : bit (32) > + { 0 | 1 < TFI_ASSIGNMENT : bit (5) > + < RLC_MODE : bit > + { 0 | 1 < ALPHA : bit (4) > } + < GAMMA : bit (5) > + < POLLING : bit > + < TA_VALID : bit (1) > } + { 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > } + { 0 | 1 < TBF_STARTING_TIME : bit (16) > } + { 0 | 1 < P0 : bit (4) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be +used. + < PR_MODE : bit (1) > } + { null | L -- Receiver compatible with earlier release + | H -- Additions for R99 + -- indicates EGPRS TBF mode, see 44.060 + < EGPRS Window Size : < EGPRS Window Size IE >> + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + } + { null | L -- Receiver compatible with earlier +release + | H -- Additions for Rel-6 + { 0 | 1 < PFI : bit (7) > } + } + { null | L -- Receiver compatible with earlier +release + | H -- Additions for Rel-7 + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 -- A downlink BTTI TBF is assigned + { 0 -- FANR is not activated for the assigned TBF + | 1 -- FANR is activated for the assigned TBF + < EVENT_BASED_FANR: bit (1) > } + | 1 -- A downlink RTTI TBF is assigned + < EVENT_BASED_FANR: bit (1) > + < PDCH PAIR INDICATION: bit(3) > + } + < Downlink EGPRS Level: < EGPRS Level IE > > +}; + +< Frequency Parameters, before time > ::= + { null -- Length of frequency parameters = 0 + | 0 0 + < MAIO : bit (6) > + < Mobile Allocation : octet (val (Length of frequency parameters) - 1) > +}; + +< Second Part Packet Assignment > ::= + { null | L -- Receiver compatible with earlier +release + | H -- Additions for R99 + { 0 | 1 < Extended RA : bit (5) > } +}; + +``` + +``` + +< Multiple Blocks Packet Downlink Assignment > ::= + < TBF_STARTING_TIME : bit (16) > + < NUMBER_OF_ALLOCATED_BLOCKS : bit (4) > + { + 0 -- Reserved for future use + | 1 + { + 0 -- MBMS Assignment (Distribution) + < TMGI : < TMGI IE > > + { 0 | 1 < MBMS Session Identity : bit (8) > } + | 1 -- MBMS Assignment (Non-distribution) + { + < TLLI / G-RNTI bit (32) > + { 0 | 1 < Length Indicator of MS ID : bit (2) > + < MS_ID : bit (val (Length Indicator of MS_ID)+1) > + < PACKET_TIMING_ADVANCE : < Packet Timing Advance IE > > + { 0 | 1 < ALPHA : bit (4) > + { 0 | 1 < GAMMA : bit (5) > } + } + } + } + } + }; +< PEO IMM Cell Group Details struct > ::= -- Addition in Rel-15 + < PEO IMM Cell Group Identifier : bit (3) > + < PEO IMM Change Mark : bit (2) > ; + +``` + +NOTE: A 'Timing Advance index' shall not be allocated at a Single Block allocation. A 'TBF Starting Time' shall be allocated at a Single Block allocation. The control bits set to fixed values to specify these requirements in a way compatible with early GPRS mobile stations in release 1997. + +**Table 10.5.2.16.1: IA Rest Octet information element** + +#### Packet Uplink Assignment + +The **Extended RA** (5 bit field) is the Extended Random Access information. This is an unformatted 5 bit field, whose content is coded as the 5 least significant bits of the EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 44.060. + +The **POLLING** field (1 bit field) indicates if the MS is being polled for a PACKET CONTROL ACKNOWLEDGEMENT: + +| | | +|---|----------------------------------------------------------------------------------------------------------------------------------| +| 0 | no action is required from MS; | +| 1 | MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by TBF Starting Time, on the assigned PDCH. | + +The **TFI\_ASSIGNMENT** field (5 bit field) is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31. + +The **USF** field (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. For the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration, this field indicates the USF to be monitored on the first PDCH of the first corresponding downlink PDCH pair assigned for that TBF. + +The **USF2** field (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. This field shall only be used in the case when two PDCH pairs are assigned for an uplink EGPRS TBF in RTTI configuration, and will in such case apply to the second PDCH pair. For the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration, this field indicates the USF to be monitored on the first PDCH of the second corresponding downlink PDCH pair assigned for that TBF. + +The **USF\_GRANULARITY** field (1 bit field) indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation, see 3GPP TS 44.060: + +| | | +|---|--------------------------------------------------------------------| +| 0 | the mobile station shall transmit one RLC/MAC block; | +| 1 | the mobile station shall transmit four consecutive RLC/MAC blocks. | + +The **CHANNEL\_CODING\_COMMAND** field (2 bit field) indicates the coding scheme to be used for transmission, see 3GPP TS 45.003: + +| | | +|-----|------------------------| +| 0 0 | coding scheme 1, CS-1; | +| 0 1 | coding scheme 2, CS-2; | +| 1 0 | coding scheme 3, CS-3; | +| 1 1 | coding scheme 4, CS-4. | + +The **TLLI\_BLOCK\_CHANNEL\_CODING** field (1 bit field) indicates the channel coding to be used for RLC data block comprising TLLI for contention resolution: + +| | | +|---|----------------------------------------------------------------------------------------------------------------------------------------| +| 0 | mobile station shall use CS-1 in GPRS TBF mode or MCS-1 in EGPRS TBF mode; | +| 1 | mobile station shall use coding scheme as specified by the corresponding CHANNEL CODING COMMAND or EGPRS CHANNEL CODING COMMAND field. | + +The **ALPHA** field (4 bit field) is the binary representation of the parameter $\alpha$ for MS output power control, see 3GPP TS 45.008: + +| | | +|---------|-----------------| +| 0 0 0 0 | $\alpha = 0.0;$ | +| 0 0 0 1 | $\alpha = 0.1;$ | +| : | : | +| 1 0 1 0 | $\alpha = 1.0.$ | + +All other values are reserved in this version of the protocol and shall be interpreted by the mobile station as $\alpha = 1.0$ . + +The **GAMMA** field (5 bit field) is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. + +The **TIMING\_ADVANCE\_INDEX** field (4 bit field) is the binary representation of the timing advance index (TAI), see 3GPP TS 45.010 and 3GPP TS 44.004. Range: 0 to 15. + +The **TBF\_STARTING\_TIME** field (16 bit field) defines a starting time for the packet uplink assignment. The TBF starting time is coded using the same coding as the V format of the type 3 information element *Starting Time* (10.5.2.38). + +##### **P0** (4 bit field) + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +##### **PR\_MODE** (1 bit field) + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +##### ***Packet Downlink Assignment*** + +The **TLLI** field (32 bit field) is the binary representation of a TLLI. The coding of TLLI is left open for each administration using the structure specified in 3GPP TS 23.003. + +The **TFI\_ASSIGNMENT** field (5 bit field) is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31. + +The **RLC\_MODE** field (1 bit field) indicates the RLC mode, see 3GPP TS 44.060: + +| | | +|---|--------------------------| +| 0 | RLC acknowledged mode; | +| 1 | RLC unacknowledged mode. | + +The **ALPHA** field (4 bit field) is the binary representations of the parameters $\alpha$ for MS output power control, see *Packet Uplink Assignment* construction. + +The **GAMMA** field (5 bit field) is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control, see *Packet Uplink Assignment* construction. + +The **POLLING** field (1 bit field) indicates if the MS is being polled for a PACKET CONTROL ACKNOWLEDGEMENT. + +0 no action is required from MS; + +1 MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by TBF Starting Time, on the assigned PDCH. + +The **TA\_VALID** field (1 bit field) indicates the validity of the timing advance value given in the *Timing Advance* IE. + +0 the timing advance value is not valid ; + +1 the timing advance value is valid. + +The **TIMING\_ADVANCE\_INDEX** field (4 bit field) is the binary representation of the timing advance index (TAI), see 3GPP TS 45.010 and 3GPP TS 44.004. Range: 0 to 15. + +The **TBF\_STARTING\_TIME** field (16 bit field) defines a starting time for the packet downlink assignment. The TBF starting time is coded using the same coding as the V format of the type 3 information element *Starting Time* (sub-clause 10.5.2.38). + +**P0** (4 bit field) + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +**PR\_MODE** (1 bit field) + +For description and encoding, see the Packet Uplink Assignment message in 3GPP TS 44.060. + +##### ***Second Part Packet Assignment*** + +The presence of the Second Part Packet Assignment is the indication that this message is the second message of two IMMEDIATE ASSIGNMENT messages in an assignment of an uplink or downlink Temporary Block Flow (TBF). + +The **Extended RA** (5 bits) is the Extended Random Access information. This is an unformatted 5 bit field, whose content is coded as the 5 least significant bits of the EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 44.060. The field shall be ignored by the mobile station, if present in a message used in an assignment of a downlink TBF. + +###### ***Frequency parameters, before time*** + +**Length of frequency parameters** (6 bit field) + +This field is coded as the binary representation of the number of octets occupied by the frequency parameters, before time field. If this length is 0, the frequency parameters, before time is not present. + +The **MAIO** field (6 bit field) is coded as the binary representation of the mobile allocation index offset. Range: 0 to 63. + +The **Mobile Allocation** field (k octet field (k = Length of frequency parameters -1) contains a bitmap referring to the *Cell Channel Description* IE in SI 1 message. The length of the bitmap is 8k, where $k = ((NF-1) \text{ div } 8 + 1)$ and where NF denotes the number of ARFCNs contained in the cell channel description. The different bit positions in the mobile allocation bitmap are assigned indices $i = 1$ to 8k, starting with $i = 8k$ in the most significant bit position and ending with $i = 1$ in the least significant bit position. The bit position with index $i$ corresponds to the $i$ 'th frequency in the cell channel description arranged in ascending order of ARFCN (except that ARFCN = 0, if included, is put last) and numbered from 1 to NF. Each bit position in the mobile allocation bitmap is coded: + +0 RF channel not belonging to mobile allocation; + +1 RF channel belonging to mobile allocation. + +If $NF \bmod 8 \neq 0$ , then bit positions $i = NF+1$ to 8k shall each be coded with a "0". + +##### ***EGPRS Packet Uplink Assignment*** + +***EGPRS Packet Downlink Assignment*** EGPRS specific fields are detailed here. + +##### **EGPRS Window Size IE** + +This information element is encoded as the EGPRS window size IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **LINK\_QUALITY\_MEASUREMENT\_MODE** (2 bit field) + +This field is encoded as the LINK\_QUALITY\_MEASUREMENT\_MODE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Access Technology Type** + +This field indicates the access technology that is requested from the mobile station. The field is coded according to the definition in 3GPP TS 24.008. The access technology types requested from the MS in the Access Technologies Request structure shall be classified by priority, the most important first. The MS shall reply using the same order. + +Among the three GSM 900 access technology types GSM P, GSM E and GSM R only one shall be requested by the network. + +##### **NUMBER OF RADIO BLOCKS ALLOCATED** (2 bit field) + +This field indicates the number of blocks reserved for uplink transmission. + +| | | +|-----|--------------------------------------------------| +| 0 0 | 1 radio block reserved for uplink transmission; | +| 0 1 | 2 radio blocks reserved for uplink transmission; | +| 1 0 | reserved for future use; | +| 1 1 | reserved for future use. | + +##### **EGPRS Modulation and Coding** + +The EGPRS Modulation and Coding information element is defined in 3GPP TS 44.060. + +##### **BEP\_PERIOD2** (4 bit field) + +This field contains a constant which is used for filtering channel quality measurements in EGPRS. This field is encoded as the BEP\_PERIOD2 in the PACKET DOWNLINK/UPLINK ASSIGNMENT messages in 3GPP TS 44.060. + +BEP\_PERIOD2 when present shall be used instead of BEP\_PERIOD. For details see 3GPP TS 45.008. + +##### **RESEGMENT** (1 bit field) + +This field is defined in 3GPP TS 44.060. + +##### **Compressed\_Inter\_RAT\_HO\_INFO\_IND** (1 bit field): + +**L** A compressed version of the INTER RAT HANDOVER INFO message shall not be used; + +**H** A compressed version of the INTER RAT HANDOVER INFO message shall be used. + +This information is used for determining whether a dual mode mobile station shall use a compressed version of the INTER RAT HANDOVER INFO message, see 3GPP TS 25.331. + +##### **PFI** (7 bit field) + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. + +##### **Number of Allocated Blocks** + +This field indicates the number of blocks reserved for the transmission of RLC/MAC control message in the downlink. + +| | | +|---------|----------------------------------------------------| +| 0 0 0 0 | 1 radio block reserved for downlink transmission; | +| 0 0 0 1 | 2 radio blocks reserved for downlink transmission; | +| 0 0 1 0 | 3 radio blocks reserved for downlink transmission; | +| 0 0 1 1 | 4 radio blocks reserved for downlink transmission; | +| 0 1 0 0 | 5 radio blocks reserved for downlink transmission; | +| 0 1 0 1 | 6 radio blocks reserved for downlink transmission; | +| 0 1 1 0 | 7 radio blocks reserved for downlink transmission; | +| 0 1 1 1 | 8 radio blocks reserved for downlink transmission; | +| 1 0 0 0 | 9 radio blocks reserved for downlink transmission. | + +All other values are reserved for future use. + +##### **TMGI** + +This field contains the Temporary Mobile Group Identity of the MBMS service. This field is encoded as defined in 3GPP TS 44.060. + +##### **MBMS Session Identity** (8 bit field) + +This field contains the MBMS Session Identity of the concerned MBMS session. + +##### **MS\_ID** (1-4 bit field) + +This field addresses the mobile station, identified by the TLLI, receiving the MBMS radio bearer that is described in this message and identified by the MBMS Bearer Identity. If the MS\_ID is allocated in this message the network shall omit it in the MBMS ASSIGNMENT message. This field is defined in 3GPP TS 44.060. + +##### **Packet Timing Advance** + +If this parameter is allocated in this message the network shall omit it in the MBMS ASSIGNMENT message. This information element is defined in 3GPP TS 44.060. + +##### **ALPHA** (4 bit field) + +If this parameter is allocated in this message the network shall omit it in the MBMS ASSIGNMENT message. For encoding and description see the Global Power Control Parameters IE specified in 3GPP TS 44.060. + +##### **GAMMA** (5 bit field) + +The GAMMA field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. If this parameter is allocated in this message the network shall omit it in the MBMS ASSIGNMENT message. The GAMMA field is coded according to the following table: + +| | | +|-----------|-----------------------| +| bit | | +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | +| ... | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | + +##### **NPM Transfer Time** (5 bit field) + +This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. + +##### **EVENT\_BASED\_FANR** (1 bit field) + +This field indicates whether the event-based FANR shall be used for the assigned TBF. The presence of this field means that FANR is activated for the assigned TBF. The coding of this information element is defined in 3GPP TS 44.060. + +##### **RTTI USF Mode** (1 bit field) + +This field identifies whether RTTI or BTTI USF Mode is used for this uplink RTTI TBF. + +| | | +|---|-----------------------| +| 0 | BTTI USF Mode is used | +| 1 | RTTI USF Mode is used | + +The **Additional USF** (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. This field is used only in the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration and indicates the USF to be monitored on the second PDCH of the first corresponding downlink PDCH pair assigned for that TBF. + +The **Additional USF2** (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. This field shall only be used in the case when two PDCH pairs are assigned for an uplink EGPRS TBF in RTTI configuration, and will in such case apply to the second PDCH pair. This field is used only in the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration and indicates the USF to be monitored on the second PDCH of the second corresponding downlink PDCH pair assigned for that TBF. + +##### **PDCH PAIR INDICATION (3 bit field)** + +This field is the binary encoding of the relative placement of the timeslots constituting the uplink PDCH pair(s) and the corresponding downlink PDCH pair(s) in case of an uplink RTTI assignment, or the downlink PDCH pair(s) and the corresponding uplink PDCH pair(s) in case of a downlink RTTI assignment (see 3GPP TS 44.060). The placement is relative to the TN as indicated in the Packet Channel Description Information Element as described in subclause 10.5.2.25a. In the case the timeslot number indicated by the Packet Channel Description is TN=i, then this field is encoded as follows: + +| bit | uplink PDCH pair(s) | downlink PDCH pair(s) | +|-------|----------------------|-----------------------| +| 3 2 1 | | | +| 0 0 0 | [i, i+1] | [i, i+1] | +| 0 0 1 | [i, i+1] | [i-1, i] | +| 0 1 0 | [i, i+1] | [i-2, i] | +| 0 1 1 | [i, i+2] | [i-1, i] | +| 1 0 0 | [i, i+1], [i+2, i+3] | [i, i+1], [i+2, i+3] | +| 1 0 1 | not used | | +| 1 1 0 | not used | | +| 1 1 1 | not used | | + +##### **REPORTED TIMESLOTS (8 bit field)** + +The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is defined in 3GPP TS 44.060. + +##### **TSH (2 bit field)** + +This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent and is defined in 3GPP TS 44.060. + +##### **Downlink EGPRS Level** + +The coding of this information element is defined in 3GPP TS 44.060. + +##### **Implicit Reject CS (1 bit)** + +A mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) shall interpret this field as follows: + +- 0 An implicit reject is not indicated for the CS domain. +- 1 An implicit reject is indicated for the CS domain. + +##### **Implicit Reject PS (1 bit)** + +A mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) shall interpret this field as follows: + +- 0 An implicit reject is not indicated for the PS domain. +- 1 An implicit reject is indicated for the PS domain. + +##### **PEO\_BCCH\_CHANGE\_MARK (2 bit)** + +See P1 Rest Octets IE, sub-clause 10.5.2.23. + +##### **RCC (3 bit)** + +This field contains Radio frequency Colour Code (RCC), and used when determining the 9 bit BSIC (see 3GPP TS 45.003 and 3GPP TS 45.008). It has a value in the range 0 to 7. + +##### **Multilateration Information Request** (1 bit field) + +This field indicates whether or not a MS is to include "MS Transmission Offset" and "MS Sync Accuracy" parameters when sending an EGPRS Packet Downlink Ack/Nack Type 2 message (see 3GPP TS 44.060 [76]) or an EGPRS Packet Downlink Ack/Nack Type 3 message (see 3GPP TS 44.060 [76]) during a downlink TBF. This field can be included when the *IA Rest Octets* or *IPA Rest Octets* information element is used to assign a downlink TBF to deliver a downlink LLC PDU for which the corresponding DL-UNITDATA PDU indicates timing advance information is needed (see 3GPP TS 48.018). This field is coded as follows: + +- 0 Do not include "MS Transmission Offset" and "MS Sync Accuracy" parameters +- 1 Include "MS Transmission Offset" and "MS Sync Accuracy" parameters + +##### **PEO IMM Cell Group Details struct** + +This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). + +##### **PEO IMM Cell Group Identifier** (3 bits) + +This 3 bit field provides the PEO IMM Cell Group Identifier (see subclause 10.5.2.37b) and is coded as follows: + +bit + +3 2 1 + +- 0 0 0 Cell belongs to PEO IMM Cell Group Identity 0 +- 0 0 1 Cell belongs to PEO IMM Cell Group Identity 1 +- 0 1 0 Cell belongs to PEO IMM Cell Group Identity 2 +- ... +- 1 1 1 Cell belongs to PEO IMM Cell Group Identity 7 + +##### **PEO IMM Change Mark** (2 bits) + +This 2 bit field identifies the change mark of the PEO IMM Cell Group (see subclause 10.5.2.37b) and is coded as follows: + +bit + +2 1 + +- 0 0 PEO IMM Change Mark value is 0 +- 0 1 PEO IMM Change Mark value is 1 +- 1 0 PEO IMM Change Mark value is 2 +- 1 1 PEO IMM Change Mark value is 3 + +#### **10.5.2.17 IAR Rest Octets** + +The *IAR Rest Octets* information element contains spare bits or possibly Extended RA informations. + +The *IAR Rest Octets* information element is a type 5 information element with 3 octets length. + +``` + + ::= + { 0 | 1 < Extended RA 1 : bit (5) > } + { 0 | 1 < Extended RA 2 : bit (5) > } + { 0 | 1 < Extended RA 3 : bit (5) > } + { 0 | 1 < Extended RA 4 : bit (5) > } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < RCC : bit (3) > + } + -- Additions in Release 15 + { 0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } + + ; + +< PEO IMM Cell Group Details struct > ::= -- Addition in Rel-15 + < PEO IMM Cell Group Identifier : bit (3) > + < PEO IMM Change Mark : bit (2) > ; + +``` + +**Figure 10.5.2.17.1: IAR Rest Octets information element** + +The **Extended RA i** (5 bits) is the Extended Random Access information related to the Request Reference i (i within the range 1..4). + +These are unformatted 5 bit fields, whose contents are coded as the 5 least significant bits of the EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 44.060. + +##### **RCC (3 bit)** + +See sub-clause 10.5.2.16. + +##### **PEO IMM Cell Group Details struct** + +This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). + +##### **PEO IMM Cell Group Identifier (3 bits)** + +See sub-clause 10.5.2.16. + +##### **PEO IMM Change Mark (2 bits)** + +See sub-clause 10.5.2.16. + +#### 10.5.2.18 IAX Rest Octets + +The *IAX Rest Octets* information element is coded according to the syntax specified below and described in table 10.5.2.18.1. + +The *IAX Rest Octets* information element is a type 5 information element with 0-4 octets length. + +``` + + ::= + < Compressed_Inter_RAT_HO_INFO_IND : bit > + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < RCC : bit (3) > + } + -- Additions in Release 15 + {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } + + ; + +< PEO IMM Cell Group Details struct > ::= -- Addition in Rel-15 + < PEO IMM Cell Group Identifier : bit (3) > + < PEO IMM Change Mark : bit (2) > ; + +``` + +**Figure 10.5.2.18.1: IAX Rest Octets information element** + +**Table 10.5.2.18.1: IAX Rest Octet information element** + +##### **Compressed\_Inter\_RAT\_HO\_INFO\_IND** (1 bit field): + +**L** A compressed version of the INTER RAT HANDOVER INFO message shall not be used; + +**H** A compressed version of the INTER RAT HANDOVER INFO message shall be used. + +This information is used for determining whether a multi-RAT mobile station shall use a compressed version of the INTER RAT HANDOVER INFO message, see 3GPP TS 25.331. + +##### **RCC** (3 bit) + +See sub-clause 10.5.2.16. + +##### **PEO IMM Cell Group Details struct** + +This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). + +##### **PEO IMM Cell Group Identifier** (3 bits) + +See sub-clause 10.5.2.16. + +##### **PEO IMM Change Mark** (2 bits) + +See sub-clause 10.5.2.16. + +#### 10.5.2.19 L2 Pseudo Length + +The *L2 Pseudo Length* information element indicates the number of octets following it in the message which are to be interpreted in the scope of the phase 1 protocol, i.e. the total number of octets (excluding the Rest Octets when present) for which T, V, TV, LV, or TLV formatting is used (reference table 11.1/3GPP TS 24.007). + +The *L2 Pseudo Length* information element is the first part of e.g. SYSTEM INFORMATION messages which are mentioned as exceptions in sub-clause 10.1. It occupies the first octet of such messages. + +For any of the SYSTEM INFORMATION messages sent on the BCCH, a mobile station should ignore the contents of the *L2 Pseudo Length* value contained in the *L2 Pseudo Length* information element. For some specific messages, further requirements are specified in clause 9. + +The *L2 Pseudo Length* Information element is an element with 2 octets length: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|----------------------|---|---|---|---|---|---|---------| +| | L2 Pseudo Length IEI | | | | | | | octet 1 | +| L2 Pseudo Length value | | | | | | 0 | 1 | octet 2 | + +**Figure 10.5.2.19.1: L2 Pseudo Length information element** + +**Table 10.5.2.19.1: L2 Pseudo Length information element** + +L2 pseudo length value (octet 2) + +The coding of the L2 pseudo length value field is the binary representation of the L2 pseudo length of the message in which the L2 pseudo length information element occurs. + +NOTE: Bits 1 and 2 are not spare. + +#### 10.5.2.20 Measurement Results + +The purpose of the *Measurement Results* information element is to provide the results of the measurements made by the mobile station on the serving cell and the neighbour cells. + +The *Measurement Results* information element is coded as shown in figure 10.5.2.20.1 and tables 10.5.2.20.0 and 10.5.2.20.1. The field mapping convention defined for RLC/MAC control blocks shall be used (see 3GPP TS 44.060). + +The *Measurement Results* is a type 3 information element with 17 octets length. + +![](6f97d19f0a9f27cb869c6e1af68e6e79_img.jpg) + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Measurement Results IEI | | | | | | | | octet 1 | +| Measurement Results Contents | | | | | | | | octets 2-17 | + +**Figure 10.5.2.20.1: Measurement Results information element****Table 10.5.2.20.0: Measurement Results Contents** + +``` + +< Measurement Results Contents > ::= + { < BA_USED : bit (1) > + < DTX_USED : bit (1) > + < RXLEV_FULL_SERVING_CELL : bit (6) > + < 3G_BA_USED : bit (1) > + < MEAS_VALID : bit (1) > + < RXLEV_SUB_SERVING_CELL : bit (6) > + < SI23_BA_USED : bit (1) > + < RXQUAL_FULL_SERVING_CELL : bit (3) > + < RXQUAL_SUB_SERVING_CELL : bit (3) > + { + < NO_NCELL_M : { bit (3) := 111 } > + 0** -- Padding with zeroes + } | + { + < NO_NCELL_M : { bit (3) exclude 111 } > + { < NCELL Report : < NCELL Report struct > > } * val (NO_NCELL_M) + { null | 0** -- Padding with zeroes + | 1 < UTRAN_CSG_Measurement_Report : < UTRAN_CSG_Measurement_Report IE > > + { null | 0** } -- Padding with zeroes + } + } + } & octet (16) ; +< NCELL Report struct > ::= + < RXLEV-NCELL : bit (6) > + < BCCH-FREQ-NCELL : bit (5) > + < BSIC-NCELL : bit (6) > ; + +``` + +**Table 10.5.2.20.1: Measurement Results Contents details** + +**BA-USED** (1 bit field) + +The value of the BA\_IND field of the neighbour cell description information element or elements defining the BCCH allocation used for the coding of BCCH-FREQ-NCELL fields. Range 0 to 1. + +##### **DTX-USED** (1 bit field) + +This bit indicates whether or not the mobile station used DTX during the previous measurement period. + +Bit 7 + +- | | | +|---|------------------| +| 0 | DTX was not used | +| 1 | DTX was used | + +##### **RXLEV-FULL-SERVING-CELL** and **RXLEV-SUB-SERVING-CELL** (6 bit fields) + +Received signal strength on serving cell, measured respectively on all slots and on a subset of slots (see 3GPP TS 45.008) + +The RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL fields are coded as the binary representation of a value N. N corresponds according to the mapping defined in 3GPP TS 45.008 to the received signal strength on the serving cell. + +Range: 0 to 63 + +##### **MEAS-VALID** (1 bit field) + +This bit indicates if the measurement results for the dedicated channel are valid or not + +Bit 7 + +- | | | +|---|---------------------------------------| +| 0 | The measurement results are valid | +| 1 | the measurement results are not valid | + +##### **3G-BA-USED** (1 bit field) + +The value of the 3G\_BA\_IND field of the neighbour cell description information element or elements defining the 3G Neighbour Cell list used for the coding of 3G BCCH-FREQ-NCELL fields and/or for defining the E-UTRAN Neighbour Cell list. Range 0 to 1. + +##### **SI23\_BA\_USED** (1 bit field) + +This field contains the value of the SI 23\_BA\_IND field in SYSTEM INFORMATION TYPE 23 message defining the E-UTRAN Neighbour Cell list used. In the case SYSTEM INFORMATION TYPE 23 message is not broadcast in the cell or if the mobile station does not support network sharing, this field shall be set to 0. Range 0 to 1. + +##### **RXQUAL-FULL-SERVING-CELL** and **RXQUAL-SUB-SERVING-CELL** (3 bit fields) + +Received signal quality on serving cell, measured respectively on all slots and on a subset of the slots (see 3GPP TS 45.008) + +CELL fields are coded as the binary representation of the received signal quality on the serving cell. + +Range: 0 to 7 (See 3GPP TS 45.008) + +##### **NO-NCELL-M** (3 bit field) + +Number of neighbour cell measurements for non-CSG cells + +Bits + +| 1 | 8 | 7 | Neighbour cell measurement result | +|---|---|---|-----------------------------------------------------------| +| 0 | 0 | 0 | None | +| 0 | 0 | 1 | 1 | +| 0 | 1 | 0 | 2 | +| 0 | 1 | 1 | 3 | +| 1 | 0 | 0 | 4 | +| 1 | 0 | 1 | 5 | +| 1 | 1 | 0 | 6 | +| 1 | 1 | 1 | Neighbour cell information not available for serving cell | + +##### **NCELL Report** + +The NCELL Report IE provides neighbour cell measurement reports for GSM cells, UTRAN cells or E-UTRAN cells. + +##### **RXLEV-NCELL i** (6 bit field) + +Result of measurement on the i'th neighbour cell + +If the i'th neighbour cell is a GSM cell, the RXLEV-NCELL field is coded as the binary representation of a value N. N corresponds according to the mapping defined in 3GPP TS 45.008 to the received signal strength on the i'th neighbouring cell. + +If the i'th neighbour cell is a 3G cell, the contents of the RXLEV-NCELL field is defined in 3GPP TS 45.008. + +Range: 0 to 63. + +##### **BCCH\_FREQ\_NCELL** (5 bit field) + +The content of this field depends on whether the report is on a GSM cell, UTRAN cell or E-UTRAN cell, as described below. + +##### **BSIC\_NCELL** (6 bit field) + +The content of this field depends on whether the report is on a GSM cell, UTRAN cell or E-UTRAN cell, as described below. + +###### **Report on GSM cells:** + +BCCH-FREQ-NCELL i, BCCH carrier of the i'th neighbour cell. + +The BCCH-FREQ-NCELL i field is coded as the binary representation of the position, starting with 0, of the i'th neighbour cells BCCH carrier in the BCCH channel list. The BCCH channel list is composed of one or two BCCH channel sub lists, each sub list is derived from the set of frequencies defined by reference neighbour cell description information element or elements. In the latter case the set is the union of the two sets defined by the two neighbour cell description information elements. + +In each BCCH channel sub list the absolute RF channel numbers are placed in increasing order of ARFCN, except that ARFCN 0, if included in the set, is put in the last position in the sub list. The BCCH channel list consists either of only the sub list derived from the neighbour cell description information element(s) in System Information 2/5 (and possible 2bis/5bis) or of that sub list immediately followed by the sub list derived from the neighbour cell description information element in System Information 2ter/5ter for the case System Information 2ter/5ter is also received. If the set of ARFCNs defined by the reference neighbour cell description information element or elements includes frequencies that the mobile station does not support then these ARFCNs shall be included in the list. + +The notation 2/5 etc. means that the rules above apply to the neighbour cell description information elements received in System Information 2, 2bis and 2ter and to those received in System Information 5, 5bis and 5ter separately. + +Range: 0 to 31/30. + +###### **Report on 3G cells:** + +If no more than 31 (GSM) ARFCN frequencies are included in the BA (list), the index BCCH-FREQ-NCELL 31 indicates report(s) on 3G cells. + +In this case, the corresponding 'BSIC-NCELL' field in figure 10.5.2.20.1 carries the index of the i'th 3G neighbour cell in the 3G Neighbour Cell list defined in sub-clause 3.4.1.2.1.1, "Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description". 3G cells with indexes above 63 are not reported (6 bits field). + +If more than 31 (GSM) ARFCN frequencies are included in the BA (list), reporting of 3G cells is not possible with this IE. + +Range: 0 to 63. + +###### **Report on E-UTRAN cells:** + +If no more than (31 - NUM\_E-UTRAN\_FREQUENCIES) GSM ARFCN frequencies are included in the BA (list), the BCCH-FREQ-NCELL indices from (31 - NUM\_E-UTRAN\_FREQUENCIES) to 30 (inclusive) indicate report(s) on E-UTRAN cells. The index BCCH-FREQ-NCELL 30 indicates a report of an E-UTRAN neighbour cell on the first frequency defined in the E-UTRAN Neighbour Cell list, the value 29 indicates a report of an E-UTRAN neighbour cell on the second frequency in the E-UTRAN Neighbour Cell list and so on. + +NUM\_E-UTRAN\_FREQUENCIES is defined as the number of separate E-UTRAN frequencies in the E-UTRAN Neighbour Cell list. + +If the BCCH-FREQ-NCELL index indicates an E-UTRAN frequency, the corresponding 'BSIC-NCELL' field in figure 10.5.2.20.1 contains the least significant 6 bits of the physical layer cell identity (see 3GPP TS 36.211) of the E-UTRAN neighbour cell. The corresponding 'RXLEV-NCELL' field in figure 10.5.2.20.1 contains the 3 bit measurement value (see 3GPP TS 45.008) in the most significant 3 bits of the field and the most significant 3 bits of the physical layer cell identity in the least significant 3 bits of the field. + +If more than (31 - NUM\_E-UTRAN\_FREQUENCIES) GSM ARFCN frequencies are included in the BA (list), reporting of E-UTRAN cells is not possible with this IE. + +##### **BSIC-NCELL i (6 bit field)** + +Base station identity code of the i'th neighbour cell + +For GSM cells, the BSIC-NCELL i field is coded as the binary representation of the base station identity code of the i'th neighbour cell. + +Range: 0 to 63. + +##### **UTRAN CSG Measurement Report** + +This information element contains the measurement report for a UTRAN CSG cell or detected hybrid cell. A UTRAN CSG cell or detected hybrid cell is identified by the Cell Identity and optionally the PLMN-ID. This information element is defined as the UTRAN CSG Measurement Report IE described in 3GPP TS 44.060. + +##### **10.5.2.20a (void)** + +#### **10.5.2.21 Mobile Allocation** + +The purpose of the *Mobile Allocation* information element is to provide that part of the RF channels belonging to the cell allocation (coded with a "1" in the cell channel description information element) which is used in the mobile hopping sequence. + +The *Mobile Allocation* information element is coded as shown in figure 10.5.2.21.1 and table 10.5.2.21.1. + +The *Mobile Allocation* is a type 4 information element with 3 to 10 octets length except for the cases specified in sub-clauses 9.1.18.1 and 9.1.19.2. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|------|------|------|------|------|------|------|-----------| +| Mobile Allocation IEI | | | | | | | | octet 1 | +| Length of mobile allocation contents | | | | | | | | octet 2 | +| MA | MA | MA | MA | MA | MA | MA | MA | | +| C | C | C | C | C | C | C | C | octet 3 | +| 8n | 8n-1 | 8n-2 | 8n-3 | 8n-4 | 8n-5 | 8n-6 | 8n-7 | | +| | | | | | | | | | +| MA | MA | MA | MA | MA | MA | MA | MA | | +| C | C | C | C | C | C | C | C | octet n+2 | +| 008 | 007 | 006 | 005 | 004 | 003 | 002 | 001 | | + +**Figure 10.5.2.21.1: Mobile Allocation information element** + +**Table 10.5.2.21.1: Mobile Allocation information element** + +MA C i, Mobile allocation RF channel i (octet 3 etc.), i = 1, 2, ..., NF + The MA C i bit indicates whether or not the Mobile allocation frequency list includes the i'th frequency in the cell allocation frequency list. + The cell allocation frequency list is derived from the set of frequencies defined by the reference cell channel description information element. NF denotes the number of frequencies in the cell allocation frequency list. + In the cell allocation frequency list the absolute RF channel numbers are placed in increasing order of ARFCN, except that ARFCN 0, if included in the set, is put in the last position in the list, + For a RF channel belonging to the mobile allocation the MA C i bit is coded with a "1"; i = 1, 2, ..., NF. + For a RF channel not belonging to the mobile allocation the MA C i bit is coded with a "0"; i = 1, 2, ..., NF. + If NF mod 8 <> 0 then bits NF to 8n in octet 3 must be coded with a "0" in each. + +##### 10.5.2.21a Mobile Time Difference + +A *Mobile Time Difference* information element encodes a time related to the synchronization difference between the time bases of two base stations. This type of information is used in conjunction with the HANDOVER COMPLETE message. + +The *Mobile Time Difference* information element is coded as shown in figure 10.5.2.21a.1 and table 10.5.2.21a.1. + +The *Mobile Time Difference* information element is a type 4 information element with 5 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|-------------------------------------------|---|---|---|------------|------------|------------|---------| +| | Mobile Time Difference IEI | | | | | | | Octet 1 | +| | Length of Mobile Time difference contents | | | | | | | Octet 2 | +| | Mobile Time Difference value (high) | | | | | | | Octet 3 | +| | Mobile Time Difference value (contd) | | | | | | | Octet 4 | +| Mobile Time Difference value (low) | | | | | 0
spare | 0
spare | 0
spare | Octet 5 | + +**Figure 10.5.2.21a.1: Mobile Time Difference information element****Table 10.5.2.21a.1: Mobile Time Difference information element** + +**Mobile Time Difference value** (octet 3, 4 and 5) + The coding of the Mobile Time Difference value field is the binary representation of the time difference in half bit periods and modulo $2^{21}$ half bit periods; 1/2 bit period = 24/13 µs. + +##### 10.5.2.21aa MultiRate configuration + +The *MultiRate configuration* information element gives all parameters related to a multi-rate speech codec. + +The *MultiRate configuration* information element is coded as shown in figure 10.5.2.21aa.1 and table 10.5.2.21aa.1. + +The *MultiRate configuration* is a type 4 information element with a minimum length of 4 octets and a maximum length of 8 octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|--------------------------|------------------------------------|------|------|---|-------|------------|---|---------|--|--|--|--| +| | Multirate speech configuration IEI | | | | | | | octet 1 | | | | | +| | Length | | | | | | | octet 2 | | | | | +| Multirate speech version | | NSCB | ICMI | | spare | Start mode | | octet 3 | | | | | +| | Parameters for multirate speech | | | | | | | octet 4 | | | | | +| | . | | | | | | | . | | | | | +| | . | | | | | | | octet n | | | | | + +Figure 10.5.2.21aa.1: MultiRate *configuration* information element![](21df39ef27b27dec52a36c0bedc53e6b_img.jpg) + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 4 | +| Set of AMR codec modes | | | | | | | | | + +Figure 10.5.2.21aa.2: Parameters for multirate speech field for the Multirate speech versions 1 & 2 when a set with one codec mode is chosen + +![](f5dc5aa74ea5482955a1e8e161b5c549_img.jpg) + +| | | | | | | | | | +|------------------------|---|---|---|---|-------------|-------|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 4 | +| Set of AMR codec modes | | | | | | | | | +| Spare | | | | | | | | octet 5 | +| 0 | 0 | | | | Threshold 1 | | | | +| | | | | | | | | octet 6 | +| Hysteresis 1 | | | | 0 | 0 | Spare | 0 | | + +Figure 10.5.2.21aa.3: Parameters for multirate speech field for the Multirate speech versions 1 & 2 when a set with two codec modes is chosen + +![](5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg) + +| | | | | | | | | | +|------------------------|---|---|---|--------------|-------------|-------------|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 4 | +| Set of AMR codec modes | | | | | | | | | +| Spare | | | | | | | | octet 5 | +| 0 | 0 | | | | Threshold 1 | | | | +| | | | | | | | | octet 6 | +| Hysteresis 1 | | | | | | Threshold 2 | | | +| Threshold 2 (cont.) | | | | | | | | octet 7 | +| | | | | Hysteresis 2 | | Spare | 0 | | + +Figure 10.5.2.21aa.4: Parameters for multirate speech field for the Multirate speech versions 1 & 2 when a set of three codec modes is chosen + +![](39fd984f11d728164f7aae746b428037_img.jpg) + +| | | | | | | | | | +|------------------------|---|---|---|--------------|-------------|--------------|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 4 | +| Set of AMR codec modes | | | | | | | | | +| Spare | | | | | | | | octet 5 | +| 0 | 0 | | | | Threshold 1 | | | | +| | | | | | | | | octet 6 | +| Hysteresis 1 | | | | | | Threshold 2 | | | +| Threshold 2 (cont.) | | | | | | | | octet 7 | +| | | | | Hysteresis 2 | | Threshold 3 | | | +| | | | | | | | | octet 8 | +| Threshold (3) | | | | | | Hysteresis 3 | | | + +Figure 10.5.2.21aa.5: Parameters for multirate speech field for the Multirate speech versions 1 & 2 when a set of four modes is chosen + +**Table 10.5.2.21aa.1: *MultiRate configuration* information element** + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| Octet 3 | | | +| Bits | | | +| 8 7 6 | Multirate speech version | | +| 0 0 1 | Adaptive Multirate speech version 1 | | +| 0 1 0 | Adaptive Multirate speech version 2 | | +| Other values reserved | | | +| NOTE 1: The Adaptive Multirate speech versions are also referred as follows (see 3GPP TS 26.103): | | | +| | - | Adaptive Multirate speech version 1: FR AMR, HR AMR or OHR AMR | +| | - | Adaptive Multirate speech version 2: FR AMR-WB, OFR AMR-WB or OHR AMR-WB | +| Bit 5 | NSCB: Noise Suppression Control Bit | | +| 0 | Noise Suppression can be used (default) | | +| 1 | Noise Suppression shall be turned off | | +| Bit 4 | ICMI: Initial Codec Mode Indicator | | +| 0 | The initial codec mode is defined by the implicit rule provided in 3GPP TS 45.009 | | +| 1 | The initial codec mode is defined by the Start Mode field | | +| Bit 3 | | | +| 0 | Spare | | +| Bits | | | +| 2 1 | Start Mode | | +| The initial codec mode is coded as in 3GPP TS 45.009. | | | +| When Multirate speech version field indicates Adaptive Multirate speech version 1 or 2 then the remaining fields are coded as follows: | | | +| THRj (6 bits), is coded as the binary representation of a value N. N corresponds to the threshold of C/I in dB, as defined in 3GPP TS 45.009; | | | +| HYSTj (4 bits) is coded as the binary representation of the hysteresis value associated to THRj, as defined in 3GPP TS 45.009. | | | +| j = 1 corresponds to the lowest value of threshold in dB, j = 2 to the second lowest, j = 3 to the highest value. | | | + +**Table 10.5.2.21aa.2: Set of adaptive multirate codec modes field (octet 4) +for the Multirate speech version 1** + +| | | +|--------------|---------------------------------------------------| +| Bit 8 | | +| 0 | 12,2 kbit/s codec rate is not part of the subset; | +| 1 | 12,2 kbit/s codec rate is part of the subset; | +| Bit 7 | | +| 0 | 10,2 kbit/s codec rate is not part of the subset; | +| 1 | 10,2 kbit/s codec rate is part of the subset; | +| Bit 6 | | +| 0 | 7,95 kbit/s codec rate is not part of the subset; | +| 1 | 7,95 kbit/s codec rate is part of the subset; | +| Bit 5 | | +| 0 | 7,40 kbit/s codec rate is not part of the subset; | +| 1 | 7,40 kbit/s codec rate is part of the subset; | +| Bit 4 | | +| 0 | 6,70 kbit/s codec rate is not part of the subset; | +| 1 | 6,70 kbit/s codec rate is part of the subset; | +| Bit 3 | | +| 0 | 5,90 kbit/s codec rate is not part of the subset; | +| 1 | 5,90 kbit/s codec rate is part of the subset; | +| Bit 2 | | +| 0 | 5,15 kbit/s codec rate is not part of the subset; | +| 1 | 5,15 kbit/s codec rate is part of the subset; | +| Bit 1 | | +| 0 | 4,75 kbit/s codec rate is not part of the subset; | +| 1 | 4,75 kbit/s codec rate is part of the subset; | + +**Table 10.5.2.21aa.3: Set of adaptive multirate codec modes field (octets 4 & 5) +for the Multirate speech version 2** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------| +| Bit
8 (Octet 4)
0 spare | +| Bit
7 (Octet 4)
0 spare | +| Bit
6 (Octet 4)
0 spare | +| Bit
5 (Octet 4)
0 23,85 kbit/s codec rate is not part of the subset;
1 23,85 kbit/s codec rate is part of the subset; | +| Bit
4 (Octet 4)
0 15,85 kbit/s codec rate is not part of the subset;
1 15,85 kbit/s codec rate is part of the subset; | +| Bit
3 (Octet 4)
0 12,65 kbit/s codec rate is not part of the subset;
1 12,65 kbit/s codec rate is part of the subset; | +| Bit
2 (Octet 4)
0 8,85 kbit/s codec rate is not part of the subset;
1 8,85 kbit/s codec rate is part of the subset; | +| Bit
1 (Octet 4)
0 6,60 kbit/s codec rate is not part of the subset;
1 6,60 kbit/s codec rate is part of the subset; | + +##### 10.5.2.21ab Mobile Time Difference on Hyperframe level + +A *Mobile Time Difference on Hyperframe level* information element encodes a time related to the synchronization difference between the time bases of two base stations. This type of information is used in conjunction with the HANDOVER COMPLETE message. + +The *Mobile Time Difference on Hyperframe level* information element is coded as shown in figure 10.5.2.21ab.1 and table 10.5.2.21ab.1. + +The *Mobile Time Difference on Hyperframe level* information element is a type 4 information element with 7 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------|---------------------------------------------------------------|---------|---------|---------|---------|---------|---------|---------| +| | Mobile Time Difference on Hyperframe level IEI | | | | | | | Octet 1 | +| | Length of Mobile Time difference on Hyperframe level contents | | | | | | | Octet 2 | +| | Mobile Time Difference on Hyperframe level value (high) | | | | | | | Octet 3 | +| | Mobile Time Difference on Hyperframe level value (contd) | | | | | | | Octet 4 | +| | Mobile Time Difference on Hyperframe level value (contd) | | | | | | | Octet 5 | +| | Mobile Time Difference on Hyperframe level value (contd) | | | | | | | Octet 6 | +| Mobile Time Difference on Hyperframe level value (low) | 0 spare | 0 spare | 0 spare | 0 spare | 0 spare | 0 spare | 0 spare | Octet 7 | + +**Figure 10.5.2.21ab.1: Mobile Time Difference on Hyperframe level information element** + +**Table 10.5.2.21ab.1: Mobile Time Difference on Hyperframe level information element** + +**Mobile Time Difference on Hyperframe level value** (octets 3 to 7) + +The coding of the Mobile Time Difference on Hyperframe level value field is the binary representation of the time difference between the old BTS and the new BTS in half bit periods; 1/2 bit period = 24/13 $\mu$ s. + +The value is calculated by adding the timing advance value towards the old BTS to the time difference between the start of a hyperframe in the old BTS and the start of the next hyperframe in the new BTS as observed by the mobile station. (See 3GPP TS 45.010). + +##### 10.5.2.21b Multislot Allocation + +The purpose of the *Multislot Allocation* information element is to provide a description of which channels are used in downlink and uplink respectively, in a multislot configuration. It also groups the channels into channel sets, the channel mode for each channel set can be defined by a separate information element. + +The *Multislot Allocation* information element is coded as shown in figure 10.5.2.21b.1 and table 10.5.2.21b.1. + +The multislot allocation information element is a type 4 information element with a minimum length of 3 octets and a maximum length of 12 octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------|---------|---------|---------|---------|---------|---------|---------|-----------| +| Multislot allocation IEI | | | | | | | | octet 1 | +| Length of the multislot allocation contents | | | | | | | | octet 2 | +| 0/1
ext | DA
7 | DA
6 | DA
5 | DA
4 | DA
3 | DA
2 | DA
1 | octet 3 | +| 1
ext | UA
7 | UA
6 | UA
5 | UA
4 | UA
3 | UA
2 | UA
1 | octet 3a | +| Channel set 1 | | | | | | | | octet 4* | +| Channel set 2 | | | | | | | | octet 5* | +| . | | | | | | | | | +| . | | | | | | | | | +| . | | | | | | | | | +| Channel set 8 | | | | | | | | octet 11* | + +**Figure 10.5.2.21b.1: Multislot Allocation information element** + +**Table 10.5.2.21b.1: *Multislot allocation* information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DA 1-7, Downlink assignment (octet 3)

Indicates additional downlink channel allocation. If bit DA n is set to "1" this indicates that timeslot $TN = (n + TNm) \bmod 8$ is assigned. If bit DA n is set to "0" the corresponding timeslot is not assigned. TNm is the timeslot number of the main link.

UA 1-7, Uplink assignment (octet 3a)

Indicates additional uplink channel allocation. If bit UA n is set to "1" this indicates that timeslot $TN = (n + TNm) \bmod 8$ is assigned. If bit UA n is set to "0" the corresponding timeslot is not assigned. TNm is the timeslot number of the main link.

If octet 3a is not included the timeslots indicated by octet 3 are allocated in both downlink and uplink direction.

Note 1: Allocation of timeslots only in uplink is FFS.
Note 2: In combination with the channel description IE, all types of channels can be indicated. The channel carrying the main signalling link (indicated by the channel description IE is of type 1 (see below)), all other channels allocated both in downlink and uplink are of type 2 and channels with allocation in only one direction are of type 3.

Type 1: TCH/F + FACCH/F + SACCH/M      bidirectional
Type 2: TCH/F + SACCH/M                  bidirectional
Type 3: TCH/F + SACCH/M                  unidirectional

Channel set n (octet 4 to 11 (if included))
If octets 4-11 are omitted, all channels belong to channel set 1.

If bit m of Channel set n is set to "1" then timeslot m-1 is included in channel set n.
If bit m of Channel set n is set to "0" then timeslot m-1 is not included in channel set n.

Each allocated timeslot, including the timeslot carrying the main signalling link, shall be included in one (and only one) channel set. | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +##### 10.5.2.21c (void) + +#### 10.5.2.22 Neighbour Cell Description + +The purpose of the *Neighbour Cell Description* information element is to provide the absolute radio frequency channel numbers of the BCCH carriers to be monitored by the mobile stations in the cell. + +The *Neighbour Cell Description* information element is coded as the *Cell Channel Description* information element, as specified in sub-clause 10.5.2.1b, with the exception of bits 5 and 6 of octet 2. Figure 10.5.2.22.1 and table 10.5.2.22.1: contains the difference of specifications. + +The *Neighbour Cell Description* information element is a type 3 information element with 17 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------------|------------|-------------|------------|------------|------------|------------|------------|----------| +| Neighbour Cell Description IEI | | | | | | | | octet 1 | +| Bit
128 | Bit
127 | EXT-
IND | BA-
IND | Bit
124 | Bit
123 | Bit
122 | Bit
121 | octet 2 | +| Bit
120 | Bit
119 | Bit
118 | Bit
117 | Bit
116 | Bit
115 | Bit
114 | Bit
113 | octet 3 | +| -------------------------------------------------------------------------------- | | | | | | | | | +| Bit
008 | Bit
007 | Bit
006 | Bit
005 | Bit
004 | Bit
003 | Bit
002 | Bit
001 | octet 17 | + +**Figure 10.5.2.22.1: *Neighbour Cell Description* information element** + +**Table 10.5.2.22.1: Neighbour Cell Description information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EXT-IND, Extension indication (octet 2, bit 6) | +| If received in System Information 2, 2bis, 5 or 5bis this bit indicates whether the information element carries the complete information of a BCCH channel sub list or whether a complementary information element is sent in another message.
A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may consider this bit as a spare bit and assume that the information element carries the complete BA, see sub-clause 3.2.2.1. | +| NOTE 1: EXT-IND is set to 1 in the neighbour cell description information elements in System Information 2 and 2bis and 5 and 5bis respectively when more than one is needed to describe a BCCH channel sub list. | +| Bit 6 | +| 0      The information element carries the complete BA | +| 1      The information element carries only a part of the BA | +| BA-IND, BCCH allocation sequence number indication (octet 2). Range 0 to 1 | +| The BA-IND is needed to allow the network to discriminate measurements results related to different BAs (e.g. BA(BCCH) and BA(SACCH)) sent to the MS. | +| NOTE 2: The network should change the contents of the Neighbour Cell Description information element (FORMAT-ID and/or set of ARFCNs) when changing the ciphering mode from not ciphered to ciphered with algorithm A5/1 (see sub-clause 3.4.7.2). For this purpose, the network may change the set of frequencies, by including ARFCNs not in a frequency band supported by the MS, without changing the BA-IND value, provided the position in the resulting BA(SACCH) of the ARFCNs that are candidates for measurement reporting is not altered.
The network should also ensure that different mobiles in the cell receive different sets of ARFCNs when sent encrypted with A5/ | + +##### 10.5.2.22a Neighbour Cell Description 2 + +The purpose of the *Neighbour Cell Description 2* information element is to provide the absolute radio frequency channel numbers of the BCCH carriers to be monitored by the mobile stations in the cell. + +The *Neighbour Cell Description 2* information element is coded as the *Cell Channel Description* information element, as specified in sub-clause 10.5.2.1b, with the exception of bits 5 to 7 of octet 2. Figure 10.5.2.22a.1 and table 10.5.2.22a.1: contains the difference of specifications. + +The *Neighbour Cell Description 2* information element is a type 3 information element with 17 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------|---------------------|---------|---------|---------|---------|---------|---------|----------| +| Neighbour Cell Description IEI | | | | | | | | octet 1 | +| Bit 128 | Multiband reporting | | BA-IND | Bit 124 | Bit 123 | Bit 122 | Bit 121 | octet 2 | +| Bit 120 | Bit 119 | Bit 118 | Bit 117 | Bit 116 | Bit 115 | Bit 114 | Bit 113 | octet 3 | +| | | | | | | | | | +| Bit 008 | Bit 007 | Bit 006 | Bit 005 | Bit 004 | Bit 003 | Bit 002 | Bit 001 | octet 17 | + +**Figure 10.5.2.22a.1: Neighbour Cell Description 2 information element** + +**Table 10.5.2.22a.1: Neighbour Cell Description 2 information element** + +Octet 2 bit 8, 4, 3 and 2 + +FORMAT-ID, Format Identifier (Bit 128 and next) + +The different formats are distinguished by the bits of higher number. As an exception to the general format for the neighbour cell description the format ID is coded as follows : + +| Bit
128 | Bit
124 | Bit
123 | Bit
122 | format notation | +|------------|------------|------------|------------|------------------| +| 0 | X | X | X | bit map 0 | +| 1 | 0 | X | X | 1024 range | +| 1 | 1 | 0 | 0 | 512 range | +| 1 | 1 | 0 | 1 | 256 range | +| 1 | 1 | 1 | 0 | 128 range | +| 1 | 1 | 1 | 1 | variable bit map | + +Bits 6 and 7 of Octet 2 + +Multiband reporting + +Binary encoding of multiband reporting parameter as specified in 3GPP TS 45.008. + +Range: 0 to 3 + +Bit 5 of octet 2 + +BA-IND, BCCH allocation sequence number indication. + +The BA-IND is needed to allow the network to discriminate measurements results related to different BAs (e.g. BA(BCCH) and BA(SACCH)) sent to the MS. + +Range 0 to 1. + +NOTE: The network should change the contents of the *Neighbour Cell Description 2* information element (FORMAT-ID and/or set of ARFCNs) when changing the ciphering mode from not ciphered to ciphered with algorithm A5/1 (see sub-clause 3.4.7.2). For this purpose, the network may change the set of frequencies, by including ARFCNs not in a frequency band supported by the MS, without changing the BA-IND value, provided the position in the resulting BA(SACCH) of the ARFCNs that are candidates for measurement reporting is not altered. + +The network should also ensure that different mobiles in the cell receive different sets of ARFCNs when sent encrypted with A5/1. + +10.5.2.22b (void) + +10.5.2.22c NT/N Rest Octets + +The *NT/N Rest Octets* information element is a type 5 information element with 20 octets length. + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

NT/N Rest Octets ::=

 {0   1 < NLN(NCH) : bit (2) >} <list of Group Call NCH information> {     null   L -- Receiver compatible with earlier release   H -- Additions in Release 6°:     {0   1 < CELL_GLOBAL_COUNT: bit (2) >}     < List of Reduced GCR >     < List of VSTK_RAND information > } {     null   L -- Receiver compatible with earlier release   H -- Additions in Release 7°:     < List of Emergency information >     {0   1 < Priority Uplink access : bit(1)>}     {0   1 {0 1 <FR AMR Config:bit(4)>}         {0 1 <HR AMR Config:bit(4)>}     }     {0   1 < SMS Data Confidentiality Ind : bit(1)>}     < SMS Guaranteed Privacy Ind : bit(1)> } } <Spare padding>;
| +|

< List of Group Call NCH information > ::=

 {0   1 < Group Call information > < List of Group Call NCH information > } ;
| +|

< List of Emergency information > ::=

 {0   1 < Emergency_Ind > < List of Emergency information > } ;
| +|

If List of Emergency Information is not present in the notification, then the emergency mode is not set for all of the group calls in the List of Group Call NCH information that contain a group channel description. Each Emergency_Ind in the List of Emergency Information is associated with a VGCS/VBS call in the List of Group Call NCH information. The Emergency_Ind at position (i) in the List of Emergency Information is associated with (i)th group call in the List of Group Call NCH information that contains a group channel description.

| +|

NLN(NCH)

This field gives the NLN value to be used as specified in sub-clause 3.3.3

| +|

<Group Call information>

See sub-clause 9.1.21a

| +|

Segment Id (1 bit)

Indicates if this message instance contains the first or second segment of a segmented notification.

bit

0 First segment.

1 Second segment.

If the notification is not segmented then the Segment Id shall be set to 0.

| +|

CELL_GLOBAL_COUNT (2 bits)

This field contains the CELL_GLOBAL_COUNT that is used by the VGCS/VBS ciphering mechanism. The value is incremented by one (modulo 4) each time bit 22 of COUNT ( defined in 3GPP TS 43.020) changes from '1' to '0'.

| +|

< List of VSTK_RAND information > ::=

 {1 < Segment Id: bit > {0   1 < VSTK_RAND: bit (36) >} } **0;
| +|

Each VSTK_RAND and Segment Id that is in the List of VSTK_RAND Information is associated to a ciphered VGCS/VBS call that is in the List of Group Call NCH information or List of Reduced GCR information. The VSTK_RAND and Segment Id at position (i) in the List of VSTK_RAND Information is associated with (i)th ciphered group call in the combined List of Group Call NCH information and List of Reduced GCR information, where the elements in the List of Group Call NCH information precede the elements in the List of Reduced GCR.

| +|

< List of Reduced GCR > ::=

 {1 < Reduced GCR: bit (28) >} **0;

The Reduced Group Call Reference shall only be used in the second segment of a segmented notification.

| +|

VSTK_RAND (36 bit)

The 36-bit value that is used for derivation of a short term key VSTK, as defined in 3GPP TS 43.020. This parameter is only provided when the group call reference is present and the group call is ciphered.

| +|

Reduced GCR (28 bits)

This field contains the binary code of the group call reference together with the service flag. It is equivalent to octets 2-4 and bits 5 to 8 of octet 5 of the Reduced Group or Broadcast Call Reference information element (see sub-clause 10.5.2.63)

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

Emergency_Ind
This field indicates the status of the emergency mode for the group call.
0      Emergency mode not set.
1      Emergency mode set.
Each Emergency_Ind that is in the List of Emergency Information is associated to a VGCS/VBS call that is in the List of Group Call NCH information. The Emergency_Ind at position (i) in the List of Emergency Information is associated with (i)th group call in the List of Group Call NCH information that contains a group channel description.

| +|

Priority Uplink Access (1 bit)
Indicates the method to be used for priority uplink access related to talker priority and sending of application data.
bit
0      RACH Access
1      Group Channel
When "RACH Access" is indicated, the channel to be used for priority uplink access for talker priority-related requests shall be determined from the UAI parameter in the talker priority status IE (see subclause 10.5.2.64); in the case of the sending of application data the channel to be used shall be determined from the Uplink access IE (see subclause 10.5.2.74).

| +|

FR AMR Config (4 bit)
This field indicates the set of AMR codec modes to be used on a group channel using speech full rate version 3. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92]

| +|

HR AMR Config (4 bit)
This field indicates the set of AMR codec modes to be used on a group channel using speech half rate version 3. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92].

| +|

SMS Data Confidentiality Ind (1 bit)
This field shall be included if the network supports the transfer of mobile originated point-to-point short messages via the group call channel. The value is provided by the network (see 3GPP TS 43.068).
bit
0      SMS data confidentiality not required.
1      SMS data confidentiality required.

| +|

SMS Guaranteed Privacy Ind (1 bit)
This field shall be included if the network supports the transfer of mobile originated point-to-point short messages via the group call channel. The value is provided by the network (see 3GPP TS 43.068).
bit
0      SMS guaranteed privacy not required.
1      SMS guaranteed privacy required.

| + +#### 10.5.2.23 P1 Rest Octets + +The *P1 Rest Octets* information element contains information about the status of information on an existing NCH, priority levels, notification and packet page indications applied for mobile station identities, MBMS Notifications, a segment of an ETWS Primary Notification message and spare bits. + +The *P1 Rest Octets* information element is a type 5 information element with 0-17 octets length. + +``` + +{ + < P1 Rest Octets > ::= + { L | H < NLN(PCH) : bit (2) > < NLN status(PCH) : bit > } + { L | H < Priority1 ::= Priority > } + { L | H < Priority2 ::= Priority > } + { L | H < Group Call information > } + < Packet Page Indication 1 : { L | H } > + < Packet Page Indication 2 : { L | H } > + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 6 : + { 0 | 1 + { + 00 < CELL_GLOBAL_COUNT:bit(2) > + | 01 < CELL_GLOBAL_COUNT:bit(2) > + < VSTK_RAND : bit (36) > + | 10 < Reduced_GCR : bit (28) > + < VSTK_RAND : bit (36) > + | 11 < CELL_GLOBAL_COUNT:bit(2) > + < Reduced_GCR : bit (28) > + < VSTK_RAND : bit (36) > + } + } + { 0 | 1 -- MBMS parameters included + { + 0 -- MBMS pre-notification + | 1 -- MBMS notification + < MBMS Notification 1 : < MBMS Channel Parameters IE > > } + { + 0 -- MBMS pre-notification + | 1 -- MBMS notification + < MBMS Notification 2 : { 0 | 1 < MBMS Channel Parameters IE > } > } + -- '0' indicates that the same MBMS Channel Parameters as for MBMS Notification 1 apply + { 0 | 1 < MBMS Information > } + } + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 7 : + { 0 | 1 < AMR Config:bit(4) > } + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 8 + < Priority Uplink Access : bit > + { 0 | 1 < ETWS Primary Notification : < ETWS Primary Notification struct > > } + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 10 + < Implicit Reject CS : bit > + < Implicit Reject PS : bit > + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 11 + < IPA Support : bit > + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < PEO_BCCH_CHANGE_MARK : bit (2) > + < RCC : bit (3) > + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 14 + < Positioning Event Pending Indicator : bit (2) > + < Enhanced Coverage Restriction Indicator : bit (2) > + } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Release 15 + { 0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct > > } + } + < spare padding >; +} // -- truncation according to sub-clause 8.9 is allowed, bits "L" assumed + +``` + +``` + +< Priority > ::= < bit (3) >; + +< Group Call information > +See sub-clause 9.1.21a + + ::= + -- Pre-notifications + < MBMS Sessions List : < MBMS Sessions List IE > > + + -- Notifications: listed per MBMS Channel Parameters + -- 1) Notifications with same MBMS Channel Parameters as in Notification 1 or Notification 2 + { + 0 + | 1 { 0 | 1 } -- None + -- 0: same MBMS Channel Parameters as Notification 1. + -- 1: same MBMS Channel Parameters as Notification 2 + < MBMS Sessions List : < MBMS Sessions List IE > > + } + + -- 2) Notifications with specific MBMS Channels Parameters + { 1 < MBMS Channel Parameters : < MBMS Channel Parameters IE > > + < MBMS Sessions List : < MBMS Sessions List IE > > + } ** 0 ; + +< ETWS Primary Notification struct> ::= + {0 -- First segment of ETWS Primary Notification, number of segments included + < Total No Of Segments For ETWS Primary Notification : bit (4) > + | 1 -- Not first segment, segment number included + < Segment Number : bit (4) > + } + < PNI: bit (1) > -- identifier for segments belonging to one and the same ETWS Primary Notification message + < Length Of Segment : bit (7) > -- length of segment in bits + < ETWS Primary Notification Data : bit (val(Length of segment)) >; + +< PEO IMM Cell Group Details struct > ::= -- Addition in Rel-15 + < PEO IMM Cell Group Identifier : bit (3) > + < PEO IMM Change Mark : bit (2) >; + +``` + +NOTE: The value 17h shall not be used as a value of the first octet when this information element is used in the PAGING REQUEST TYPE 1 message. This will prevent mobile stations misinterpreting this information as the Mobile Identity IEI. + +**Table 10.5.2.23.1: *P1 Rest Octets* information element** + +**NLN(PCH) Notification List Number** + +The presence of the *NLN(PCH)* field indicates that if an NCH is present, reduced NCH monitoring can be used, and gives the *NLN(PCH)* value, to be used as specified in sub-clause 3.3.3. + +**NLN status(PCH) Notification List Number status** + +The *NLN status* indicates the status of the content of the NOTIFICATION/NCH messages for a particular *NLN* value. A change of the *NLN status* field indicates a change of information on the NCH which is not related to new calls, as specified in sub-clause 3.3.3. + +**Priority:** **Priority i** relates to *Mobile Identity i* ( $i = 1, 2$ ). If *Mobile Identity i* denotes an MBMS session, the corresponding *Priority i* field shall be ignored if present. + +| | | +|-------|-----------------------| +| 0 0 0 | no priority applied | +| 0 0 1 | call priority level 4 | +| 0 1 0 | call priority level 3 | +| 0 1 1 | call priority level 2 | +| 1 0 0 | call priority level 1 | +| 1 0 1 | call priority level 0 | +| 1 1 0 | call priority level B | +| 1 1 1 | call priority level A | + +The **Packet Page Indication i** field relates to *Mobile Identity i* ( $i = 1, 2$ ) and indicates the kind of paging procedure associated with the mobile station identity. If the identity is not IMSI the Packet Page Indication has no meaning and is ignored. + +| | | +|---|---------------------------------------------------| +| L | paging procedure for RR connection establishment; | +| H | packet paging procedure. | + +**Reduced GCR (28 bits)** + +This field contains the binary code of the group call reference together with the service flag. It is equivalent to octets 2-4 and bits 5 to 8 of octet 5 of the Reduced Group or Broadcast Call Reference information element (see sub-clause 10.5.2.63). + +**VSTK\_RAND (36 bits)** + +The 36-bit value that is used for derivation of a short term key VSTK, as defined in 3GPP TS 43.020. This parameter is only provided when the group call reference is present and the group call is ciphered. + +**CELL\_GLOBAL\_COUNT (2 bits)** + +This field contains the *CELL\_GLOBAL\_COUNT* that is used by the VGCS/VBS ciphering mechanism. Mobiles that don't support VGCS/VBS may ignore this parameter. The value is incremented by one (modulo 4) each time bit 22 of *COUNT* ( defined in 3GPP TS 43.020) changes from '1' to '0'.. + +The **MBMS Notification i** structure relates to *Mobile Identity i* ( $i = 1, 2$ ) and contains information related to a specific MBMS session. If *Mobile Identity i* does not denote an MBMS session or is not a TMGI of interest for the mobile station the corresponding MBMS Notification information shall be ignored. + +**MBMS Sessions List** + +This information element contains a list of MBMS sessions identified by their TMGI and if available MBMS Session Identity (see 3GPP TS 44.060). This information element is defined in 3GPP TS 44.060. + +**MBMS Channel Parameters** + +This information element contains the MBMS channel parameters of one or more MBMS sessions. This information element is defined in 3GPP TS 44.060. + +**AMR\_Config (4 bits)** + +This field indicates the set of AMR codec modes to be used on a group channel using speech version 3. It is coded as the binary representation of the parameter *Config-NB-Code* of one of the preferred AMR configurations defined in 3GPP TS 28.062 [91], subclause 7.11.3.1.3. + +##### **Priority Uplink Access (1 bit)** + +This field indicates the method to be used for priority uplink access related to talker priority and sending of application data. + +bit + +| | | +|---|---------------| +| 0 | RACH Access | +| 1 | Group Channel | + +When "RACH Access" is indicated, the channel to be used for priority uplink access for talker priority-related requests shall be determined from the UAI parameter in the talker priority status IE (see subclause 10.5.2.64); in the case of the sending of application data the channel to be used shall be determined from the Uplink access IE (see subclause 10.5.2.74). + +This bit shall be ignored by mobiles which do not support group receive mode. + +##### **Total No Of Segments For ETWS Primary Notification (4 bits)** + +This field contains the number of segments for the ETWS Primary Notification message. + +Bits + +| | | | | | +|---|---|---|---|------------------| +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | reserved | +| 0 | 0 | 0 | 1 | one segment | +| 0 | 0 | 1 | 0 | two segments | +| . | . | . | | | +| 1 | 1 | 1 | 1 | fifteen segments | + +##### **Segment Number (4 bits)** + +This field contains the Segment Number of the ETWS Primary Notification message. + +Bits + +| | | | | | +|---|---|---|---|-------------------| +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | reserved | +| 0 | 0 | 0 | 1 | reserved | +| 0 | 0 | 1 | 0 | second segment | +| 0 | 0 | 1 | 1 | third segment | +| . | . | . | | | +| 1 | 1 | 1 | 1 | fifteenth segment | + +##### **PNI, Primary Notification Identifier (1 bit)** + +This field is used as an identifier to determine the set of segments belonging to a certain ETWS Primary Notification message. This information element will have the same value (0 or 1) for all segments belonging to the same ETWS Primary Notification message. + +##### **Length Of Segment (7 bits)** + +This field indicates the length of a segment in number of bits. + +##### **ETWS Primary Notification Data (n\*8 bits)** + +The ETWS Primary Notification data is coded as specified in 3GPP TS 23.041. + +##### **Implicit Reject CS (1 bit)** + +##### **Implicit Reject PS (1 bit)** + +A mobile station configured for *NAS signalling low priority* (see 3GPP TS 24.008) shall interpret these fields as described for the *IA Rest Octets* IE (see sub-clause 10.5.2.16). + +**IPA\_Support (1 bit)** + +The *IPA\_Support* field indicates whether the network supports the IMMEDIATE PACKET ASSIGNMENT message. A mobile station supporting IPA (see 3GPP TS 24.008) shall interpret this field as described below: + +| | | +|---|-----------------------------------------------------------| +| 0 | IMMEDIATE PACKET ASSIGNMENT message is not supported | +| 1 | IMMEDIATE PACKET ASSIGNMENT message is supported on CCCH. | + + + +**PEO\_BCCH\_CHANGE\_MARK (2 bits)** + +This field is incremented every time one or more SI messages have changed. An exception is when EAB is enabled for a given set of PLMNs (see sub-clause 10.5.2.37m) and changes are made only to the EAB Authorization Mask and EAB Subcategory fields corresponding to this set of PLMNs in which case the PEO\_BCCH\_CHANGE\_MARK field is not incremented (i.e. the network shall use the PEO\_BCCH\_CHANGE\_MARK field to indicate when EAB has been enabled/disabled or when the set of PLMNs affected by EAB has changed). It is only used by a MS that has enabled PEO. In order for mobile stations that have negotiated the longest eDRX cycle to detect a change in PEO BCCH CHANGE MARK the network should not increment this field more frequently than three times per 24 hour period. + + + +**RCC (3 bits)** + +See sub-clause 10.5.2.16. + + + +**Positioning Event Pending Indicator (2 bit)** + +This field is a 2 bit bitmap indicating whether or not a paging request is sent due to a pending positioning event for the MS identified by the Mobile Identity 1 and Mobile Identity 2 fields. + +Bit +**2 1** + +| | | +|-----|------------------------------------------------------------------------| +| x 0 | Page not sent for Mobile Identity 1 due to a pending positioning event | +| x 1 | Page sent for Mobile Identity 1 due to a pending positioning event | +| 0 x | Page not sent for Mobile Identity 2 due to a pending positioning event | +| 1 x | Page sent for Mobile Identity 2 due to a pending positioning event | + + + +**Enhanced Coverage Restriction Indicator (2 bits)** + +See Table 9.1.63.2. + + + +**PEO IMM Cell Group Details struct** + +This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). + + + +**PEO IMM Cell Group Identifier (3 bits)** + +See sub-clause 10.5.2.16. + + + +**PEO IMM Change Mark (2 bits)** + +See sub-clause 10.5.2.16. + +#### 10.5.2.24 P2 Rest Octets + +The *P2 Rest Octets* information element contains information on the channel needed by the network and information about the status of information on an existing NCH, priority levels and packet page indications applied for mobile station identities, MBMS Notification and spare bits. + +The *P2 Rest Octets* information element is a type 5 information element with 1-11 octets length. + +``` + +{ + ::= + { L | H } + { L | H } + { L | H } + { L | H } + { L | H } + < Packet Page Indication 3 : { L | H } > + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 6 : + { 0 | 1 -- MBMS parameters included + { 0 -- MBMS pre-notification + | 1 -- MBMS notification + > } + { 0 | 1 < MBMS Information > } + } + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 10 + < Implicit Reject CS : bit > + < Implicit Reject PS : bit > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 11 + < IPA Support : bit > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < PEO_BCCH_CHANGE_MARK : bit (2) > + < RCC : bit (3) > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 14 + < Positioning Event Pending Indicator : bit (3) > + < Enhanced Coverage Restriction Indicator : bit (3) > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 15 + { 0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } + } +} // -- truncation according to sub-clause 8.9 is allowed, bits 'L' assumed + + ::= ; + + ::= + -- Pre-notifications + < MBMS Sessions List : < MBMS Sessions List IE > > + + -- Notifications: listed per MBMS Channel Parameters + -- 1) Notifications with same MBMS Channel Parameters as in Notification 3 + { 0 -- None + | 1 -- Same MBMS Channel Parameters as Notification 3 + < MBMS Sessions List : < MBMS Sessions List IE > > } + -- 2) Notifications with specific MBMS Channels Parameters + { 1 < MBMS Channel Parameters : < MBMS Channel Parameters IE > > + < MBMS Sessions List : < MBMS Sessions List IE > > } ** 0 ; + +< PEO IMM Cell Group Details struct > ::= -- Addition in Rel-15 + < PEO IMM Cell Group Identifier : bit (3) > + < PEO IMM Change Mark : bit (2) > ; + +``` + +NOTE: The value 17h shall not be used as a value of the first octet when this information element is used in the PAGING REQUEST TYPE 2 message. This will prevent mobile stations misinterpreting this information as the Mobile Identity IEI. + +**Table 10.5.2.24.1: P2 Rest Octets information element** + +##### **CN3 Channel Needed for Mobile Identity 3** + +The values and semantics used in the CN3 field are those of the CHANNEL field of *Channel Needed IE* (see sub-clause 10.5.2.8). The CN3 field is associated with the Mobile Identity 3 IE of the PAGING REQUEST TYPE 2 message. + +If the CN3 field is not present, the default value is 00 (any channel). If *Mobile Identity 3* denotes an MBMS session, the CN3 field shall be ignored if present. + +##### **NLN(PCH) Notification List Number** + +See P1 Rest Octets. + +##### **NLN status(PCH) Notification List Number status** + +See P1 Rest Octets. + +**Priority:** **Priority i** relates to *Mobile Identity i* (i = 1, 2, 3). If *Mobile Identity 3* denotes an MBMS session, the corresponding *Priority 3* field shall be ignored if present. + +| | | +|-------|-----------------------| +| 0 0 0 | no priority applied | +| 0 0 1 | call priority level 4 | +| 0 1 0 | call priority level 3 | +| 0 1 1 | call priority level 2 | +| 1 0 0 | call priority level 1 | +| 1 0 1 | call priority level 0 | +| 1 1 0 | call priority level B | +| 1 1 1 | call priority level A | + +The **Packet Page Indication 3** field relates to *Mobile Identity 3* and indicates the kind of paging procedure associated with the mobile station identity. If the identity is not IMSI the Packet Page Indication has no meaning and is ignored. + +| | | +|---|---------------------------------------------------| +| L | paging procedure for RR connection establishment; | +| H | packet paging procedure. | + +The **MBMS Notification 3** field relates to Mobile Identity 3 and contains information related to a specific MBMS session. If Mobile Identity 3 does not denote an MBMS session or is not a TMGI of interest for the mobile station the corresponding MBMS Notification information shall be ignored. + +See Table 10.5.2.23.1: "P1 Rest Octets information element" for the definitions of IEs used for MBMS related information. + +##### **Implicit Reject CS (1 bit)** + +##### **Implicit Reject PS (1 bit)** + +A mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) shall interpret these fields as described for the *IA Rest Octets IE* (see sub-clause 10.5.2.16). + +##### **IPA\_Support (1 bit)** + +A mobile station supporting IPA (see 3GPP TS 24.008) shall interpret this field as described in the *P1 Rest Octets* IE (see sub-clause 10.5.2.23) + +##### **PEO\_BCCH\_CHANGE\_MARK (2 bit)** + +See P1 Rest Octets IE, sub-clause 10.5.2.23. + +##### **RCC (3 bit)** + +See sub-clause 10.5.2.16. + +##### **Positioning Event Pending Indicator (3 bit)** + +This field is a 3 bit bitmap indicating whether or not a paging request is sent due to a pending positioning event for the MS identified by the Mobile Identity 1, Mobile Identity 2 and Mobile Identity 3 fields. + +Bit + +**3 2 1** + +x x 0 Page not sent for Mobile Identity 1 due to a pending positioning event + x x 1 Page sent for Mobile Identity 1 due to a pending positioning event + x 0 x Page not sent for Mobile Identity 2 due to a pending positioning event + x 1 x Page sent for Mobile Identity 2 due to a pending positioning event + 0 x x Page not sent for Mobile Identity 3 due to a pending positioning event + 1 x x Page sent for Mobile Identity 3 due to a pending positioning event + +##### **Enhanced Coverage RestrictionIndicator (3 bits)** + +This field is a 3 bit bitmap indicating whether or not the use of enhanced coverage is restricted for the MS identified by the Mobile Identity 1, Mobile Identity 2 and Mobile Identity 3 fields. + +Bit + +**3 2 1** + +x x 0 Restricted use of enhanced coverage for Mobile Identity 1 + x x 1 No restriction on use of enhanced coverage for Mobile Identity 1 + x 0 x Restricted use of enhanced coverage for Mobile Identity 2 + x 1 x No restriction on use of enhanced coverage for Mobile Identity 2 + 0 x x Restricted use of enhanced coverage for Mobile Identity 3 + 1 x x No restriction on use of enhanced coverage for Mobile Identity 3 + +##### **PEO IMM Cell Group Details struct** + +This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). + +##### **PEO IMM Cell Group Identifier (3 bits)** + +See sub-clause 10.5.2.16. + +##### **PEO IMM Change Mark (2 bits)** + +See sub-clause 10.5.2.16. + +#### 10.5.2.25 P3 Rest Octets + +The *P3 Rest Octets* information element contains information on the channel needed by the network and information about the status of information on an existing NCH, priority levels applied for mobile station identities and spare bits. The purpose of the spare bits is to allow the upward compatible introduction of new information on the PCH in later phases. + +The *P3 Rest Octets* information element is a type 5 information element with 3 octets length. + +``` + +< P3 Rest Octets > ::= + { L | H < CN3 : bit (2) > < CN4 : bit (2) > } + { L | H < NLN(PCH) : bit (2) > < NLN status(PCH) : bit > } + { L | H < Priority1 ::= Priority > } + { L | H < Priority2 ::= Priority > } + { L | H < Priority3 ::= Priority > } + { L | H < Priority4 ::= Priority > } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 10 + < Implicit Reject CS : bit > + < Implicit Reject PS : bit > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 11 + < IPA Support : bit > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < PEO_BCCH_CHANGE_MARK : bit (2) > + < RCC : bit (3) > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 14 + < Positioning Event Pending Indicator : bit (4) > + < Enhanced Coverage Restriction Indicator : bit (4) > + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 15 + { 0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } + } + + < spare padding >; +} // -- truncation according to sub-clause 8.9 is allowed, bits 'L' assumed +< Priority > ::= < bit(3) >; + +< PEO IMM Cell Group Details struct > ::= -- Addition in Rel-15 + < PEO IMM Cell Group Identifier : bit (3) > + < PEO IMM Change Mark : bit (2) >; + +``` + +**Table 10.5.2.25.1: P3 Rest Octets information element** + +##### CN3 Channel Needed for Mobile Identity 3 + +The values and semantics used in the CN3 field are those of the CHANNEL field of Channel Needed IE (see 10.5.2.8). The CN3 field is associated with the Mobile Identity 3 IE of the PAGING REQUEST TYPE 3 message. + +If the CN3 field is not present, the default value is 00 (any channel) + +##### CN4 Channel Needed for Mobile Identity 4 + +The values and semantics used in the CN43 field are those of the CHANNEL field of Channel Needed IE (see 10.5.2.8). The CN4 field is associated with the Mobile Identity 4 IE of the PAGING REQUEST TYPE 3 message. + +If the CN4 field is not present, the default value is 00 (any channel) + +| | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------|-------|-----------------------|-------|-----------------------|-------|-----------------------|-------|-----------------------|-------|-----------------------|-------|-----------------------|-------|-----------------------| +|

NLN(PCH) Notification List Number

See P1 Rest Octets

| | | | | | | | | | | | | | | | | +|

NLN status(PCH) Notification List Number status

See P1 Rest Octets.

| | | | | | | | | | | | | | | | | +|

Priority: Priority i relates to Mobile Station Identity i
i (i = 1,2,3,4)

0 0 0 no priority applied
0 0 1 call priority level 4
0 1 0 call priority level 3
0 1 1 call priority level 2
1 0 0 call priority level 1
1 0 1 call priority level 0
1 1 0 call priority level B
1 1 1 call priority level A
| 0 0 0 | no priority applied | 0 0 1 | call priority level 4 | 0 1 0 | call priority level 3 | 0 1 1 | call priority level 2 | 1 0 0 | call priority level 1 | 1 0 1 | call priority level 0 | 1 1 0 | call priority level B | 1 1 1 | call priority level A | +| 0 0 0 | no priority applied | | | | | | | | | | | | | | | | +| 0 0 1 | call priority level 4 | | | | | | | | | | | | | | | | +| 0 1 0 | call priority level 3 | | | | | | | | | | | | | | | | +| 0 1 1 | call priority level 2 | | | | | | | | | | | | | | | | +| 1 0 0 | call priority level 1 | | | | | | | | | | | | | | | | +| 1 0 1 | call priority level 0 | | | | | | | | | | | | | | | | +| 1 1 0 | call priority level B | | | | | | | | | | | | | | | | +| 1 1 1 | call priority level A | | | | | | | | | | | | | | | | +|

Implicit Reject CS (1 bit)
Implicit Reject PS (1 bit)

A mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) shall interpret these fields as described for the IA Rest Octets IE (see sub-clause 10.5.2.16).

| | | | | | | | | | | | | | | | | +|

IPA_Support (1 bit)

A mobile station supporting IPA (see 3GPP TS 24.008) shall interpret this field as described in the P1 Rest Octets IE (see sub-clause 10.5.2.23)

| | | | | | | | | | | | | | | | | + +##### **PEO\_BCCH\_CHANGE\_MARK (2 bit)** + +See P1 Rest Octets IE, sub-clause 10.5.2.23. + +##### **RCC (3 bit)** + +See sub-clause 10.5.2.16. + +##### **Positioning Event Pending Indicator (4 bit)** + +This field is a 4 bit bitmap indicating whether or not a paging request is sent due to a pending positioning event for the MS identified by the Mobile Identity 1, Mobile Identity 2, Mobile Identity 3 and Mobile Identity 4 fields. + +Bit + +**4 3 2 1** + +x x x 0 Page not sent for Mobile Identity 1 due to a pending positioning event + +x x x 1 Page sent for Mobile Identity 1 due to a pending positioning event + +x x 0 x Page not sent for Mobile Identity 2 due to a pending positioning event + +x x 1 x Page sent for Mobile Identity 2 due to a pending positioning event + +x 0 x x Page not sent for Mobile Identity 3 due to a pending positioning event + +x 1 x x Page sent for Mobile Identity 3 due to a pending positioning event + +0 x x x Page not sent for Mobile Identity 3 due to a pending positioning event + +1 x x x Page sent for Mobile Identity 3 due to a pending positioning event + +##### **Enhanced Coverage Restriction Indicator (4 bits)** + +This field is a 4 bit bitmap indicating whether or not the use of enhanced coverage is restricted for the MS identified by the Mobile Identity 1, Mobile Identity 2, Mobile Identity 3 and Mobile Identity 4 fields. + +Bit + +**4 3 2 1** + +x x x 0 Restricted use of enhanced coverage for Mobile Identity 1 + +x x x 1 No restriction on use of enhanced coverage for Mobile Identity 1 + +x x 0 x Restricted use of enhanced coverage for Mobile Identity 2 + +x x 1 x No restriction on use of enhanced coverage for Mobile Identity 2 + +x 0 x x Restricted use of enhanced coverage for Mobile Identity 3 + +x 1 x x No restriction on use of enhanced coverage for Mobile Identity 3 + +0 x x x Restricted use of enhanced coverage for Mobile Identity 4 + +1 x x x No restriction on use of enhanced coverage for Mobile Identity 4 + +##### **PEO IMM Cell Group Details struct** + +This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). + +##### **PEO IMM Cell Group Identifier (3 bits)** + +See sub-clause 10.5.2.16. + +##### **PEO IMM Change Mark (2 bits)** + +See sub-clause 10.5.2.16. + +##### **10.5.2.25a Packet Channel Description** + +The purpose of the *Packet Channel Description* information element is to provide a description of a packet data physical channel (PDCH). + +The *Packet Channel Description* information element is coded according to the syntax specified below and described in table 10.58. + +The *Packet Channel Description* is a type 3 information element with 4 octets length. + +``` + +< Packet Channel Description > ::= + < Channel type : bit (5) > + < TN : bit (3) > + < TSC : bit (3) > + { + 0 + { + 0 < spare bit > + < ARFCN : bit (10) > -- non-hopping RF channel configuration + } | 1 < spare bit > + { + < MAIO : bit (6) > -- indirect encoding of hopping RF channel configuration + < MA_NUMBER_IND : bit > + { + 0 < spare bits : bit (2) > + | 1 < CHANGE_MARK_1 : bit (2) > } + } + } | 1 + { + < MAIO : bit (6) > -- direct encoding of hopping RF channel configuration + < HSN : bit (6) > + } +}; + +``` + +**Table 10.5.2.25a.1: Packet Channel Description information element** + +The **Channel type** field (5 bit) shall be ignored by the receiver and all bits treated as spare. For backward compatibility reasons, the sender shall set the spare bits to binary '00001'. + +The **TN** field (3 bit) is the binary representation of the timeslot number as defined in 3GPP TS 45.010. Range: 0 to 7 + +The **TSC** field (3 bit) is the binary representation of the training sequence code as defined in 3GPP TS 45.002. Range: 0 to 7. + +##### Non-hopping RF channel configuration + +The **ARFCN** field (10 bit) is the binary representation of the absolute RF channel number, see 3GPP TS 45.005. Range: 0 to 1023. + +##### Indirect encoding of hopping RF channel configuration + +The **MAIO** field (6 bit) is the binary representation of the mobile allocation index offset, see 3GPP TS 45.002. Range: 0 to 63. + +The **MA\_NUMBER\_IND** field (1 bit) is the binary representation of the MA\_NUMBER to use as reference to a GPRS mobile allocation: + +| | | +|---|----------------| +| 0 | MA_NUMBER = 14 | +| 1 | MA_NUMBER = 15 | + +The **CHANGE\_MARK\_1** field (2 bit) is the binary representation of the allowed value of the SI *change mark* associated with the GPRS mobile allocation to which the MA\_NUMBER refers. Range: 0 to 3. + +If the *indirect encoding* is used, this information element may contain the CHANGE\_MARK\_1 field. If that is present, the mobile station being assigned the TBF shall verify the validity of the SI *change mark* associated with the GPRS mobile allocation to which this information element refers, see 3GPP TS 44.060. The CHANGE\_MARK\_1 field shall not be included in this information element if MA\_NUMBER = 15 is used. + +##### Direct encoding of hopping RF channel configuration + +The **MAIO** field (6 bit) is the binary representation of the mobile allocation index offset, see 3GPP TS 45.002. Range: 0 to 63. + +The **HSN** field (6 bit) is the binary representation of the hopping sequence number, see 3GPP TS 45.002. Range: 0 to 63. + +##### 10.5.2.25b Dedicated mode or TBF + +The *Dedicated mode or TBF* information element is used by the network to indicate to the mobile station whether the rest of the message shall be decoded as an IMMEDIATE ASSIGNMENT message allocating a channel in dedicated mode or whether the rest of the message shall be decoded as the allocation of a Temporary Block Flow or to indicate that no Temporary Block Flow is allocated for the case where an IMMEDIATE ASSIGNMENT message is sent in response to an EGPRS MULTILATERATION REQUEST message indicating 'Access Burst method' or 'Extended Access Burst method' (see sub-clause 3.5.2.1.2 and sub-clause 3.11). + +This information element also indicates: + +- whether the IMMEDIATE ASSIGNMENT message identifies a mobile station in the IA Rest Octets information elements for the assignment of a downlink TBF; and +- whether the IMMEDIATE ASSIGNMENT message is the first message of two IMMEDIATE ASSIGNMENT messages in a two-message assignment of an uplink or downlink TBF. + +The *Dedicated mode or TBF* information element is coded as shown in figure 10.5.2.25b.1, table 10.5.2.25b.1 and Table 10.5.2.25b.2. + +The *Dedicated mode or TBF* is a type 1 information element. + +![](6df742a7ac8e019dbf9e8ecfa4497d85_img.jpg) + +| | | | | | | | | | +|------------------------------|---|---|---|-----|-----|---------------|-----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Dedicated mode
or TBF IEI | | | | NRA | TMA | down-
link | T/D | octet 1 | + +**Figure 10.5.2.25b.1: *Dedicated mode or TBF* information element** + +**Table 10.5.2.25b.1: *Dedicated mode or TBF* information element** + +**T/D** : TBF or dedicated mode (octet 1, bit 1) + +The coding of this field is given by Table 10.5.2.2.25b.2. + +**Downlink** : Downlink TBF assignment to the mobile station identified in the IA Rest Octets IE (octet 1, bit 2) + +The coding of this field is given by Table 10.5.2.2.25b.2. + +**TMA** : Two-message assignment (octet 1, bit 3) + +The coding of this field is given by Table 10.5.2.2.25b.2. + +**NRA (No Resource Allocated)**: This field is used to indicate when neither a TBF nor a dedicated resource is allocated by the IMMEDIATE ASSIGNMENT message (octet 1, bit 4). The coding of this field is given by Table 10.5.2.2.25b.2. + +**Table 10.5.2.25b.2: Dedicated mode or TBF information element: +T/D, downlink, TMA and NRA fields** + +| NRA bit 4 | TMA bit 3 | downlink bit 2 | T/D bit 1 | Description | +|-----------|-----------|----------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 0 | 0 | 0 | This message assigns a dedicated mode resource | +| 0 | 0 | 1 | 0 | Not used (Note 1) | +| 0 | 1 | 0 | 0 | Not used (Note 1) | +| | 1 | 1 | 0 | Not used (Note 1) | +| 0 | 0 | 0 | 1 | This message assigns an uplink TBF or is the second message of two in a two-message assignment of an uplink or downlink TBF | +| 0 | 0 | 1 | 1 | This message assigns a downlink TBF to the mobile station identified in the IA Rest Octets IE | +| 0 | 1 | 0 | 1 | This message is the first message of two in a two-message assignment of an uplink TBF | +| 0 | 1 | 1 | 1 | This message is the first message of two in a two-message assignment of a downlink TBF to the mobile station identified in the IA Rest Octets IE | +| 1 | 0 | 0 | 0 | When the IMMEDIATE ASSIGNMENT message is sent in response to an EGPRS MULTILATERATION REQUEST message indicating 'Access Burst method' or 'Extended Access Burst method' (see sub-clause 3.5.2.1.2 and sub-clause 3.11) the NRA bit shall be set to '1' thereby indicating that no TBF or dedicated mode resources are allocated by the message. If a TBF is allocated by the IMMEDIATE ASSIGNMENT message then this bit shall be set to '0'. | + +NOTE 1: The code point is not used. The behaviour of the mobile station is not defined. The code point should not be used in future versions of the protocol. + +#### 10.5.2.25c RR Packet Uplink Assignment + +The *RR Packet Uplink Assignment* information element is sent by the network to the mobile station to indicate the assigned uplink resources. + +The *RR Packet Uplink Assignment* information element is coded as shown in figure 10.5.2.25c.1 and tables 10.5.2.25c.1 and 10.5.2.25c.2. + +The *RR Packet Uplink Assignment* is a type 4 information element with a minimum length of 4 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|--------------------------------------------------|---|---|---|---|---|---|-------------| +| | RR Packet Uplink Assignment IEI | | | | | | | octet 1 | +| | Length of RR Packet Uplink Assignment value part | | | | | | | octet 2 | +| | RR Packet Uplink Assignment value part | | | | | | | octet 3 - n | + +**Figure 10.5.2.25c.1: RR PACKET UPLINK ASSIGNMENT information element** + +**Table 10.5.2.25c.1: RR PACKET UPLINK ASSIGNMENT value part** + +``` + +< RR Packet Uplink Assignment value part > ::= + < CHANNEL_CODING_COMMAND : bit (2) > + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + < Packet Timing Advance : Packet Timing Advance IE > + { + 01 < Dynamic Allocation : Dynamic Allocation struct > + | 10 < reserved > -- The value '10' was allocated in an earlier version of the protocol and shall not be used. + | 11 < reserved > -- The value '11' was allocated in an earlier version of the protocol and shall not be used. + | 00 { 0 < Multiple TBF Allocation : Multiple TBF Allocation struct > + | 1 < Extension > } + } + { + null -- Receiver compatible with earlier release + | -- Additions for R99 + { 0 | 1 < EGPRS_MCS_MODE : bit (4) > + < RESEGMENT : bit (1) > + < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { + null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions for Rel-7 + { 0 | 1 < RLC_MODE : bit (1) > } -- This field may be present in case of single TBF allocation + { 1 { 0 | 1 < NPM Transfer Time : bit (5) > } }** 0 + < Uplink EGPRS Level : < EGPRS Level IE > > + { 0 | 1 < Pulse Format : < Pulse Format IE > > } + { 0 -- '0' indicates that FANR is not activated + | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < REPORTED TIMESLOTS : bit (8) > + < TSH : bit (2) > } } + { + null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-8 + { 0 | 1 { 1 < Measurement_Control_E-UTRAN : bit(1) > + < E-UTRAN_FREQUENCY_INDEX : bit (3) > + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 + } ** 0 + } + { 0 | 1 { 1 < Measurement_Control_UTRAN : bit(1) > + < UTRAN_FREQUENCY_INDEX : bit (5) > + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 + } ** 0 + } + { + null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used + | 1 -- EMST is used + < RLC Entity 2 : < RLC Entity Struct > > + { 0 + | 1 < RLC Entity 3 : < RLC Entity Struct > > } + } + { + null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + < spare bit >** + } -- End of additions for Rel-10 + } -- End of additions for Rel-9 + } -- End of additions for Rel-8 + } -- End of additions for Rel-7 + }; -- End of additions for R99 + +< Multiple TBF Allocation struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit(1) > } + { 0 | 1 < Timeslot description : < Timeslot description struct > > + { 1 < Uplink TBF Assignment : < Uplink TBF Assignment struct > > } ** 0 } ; + +``` + +< Timeslot description struct > ::= + +``` + +{ 0 | 1 < USF_GRANULARITY : bit(1) > } -- without power control params +{ 0 | 1 < USF_GRANULARITY : bit(1) > } -- '0' means TS not assigned +{ 0 | 1 < USF_GRANULARITY : bit(1) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > } +| 1 -- with power control params +< ALPHA : bit (4) > +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN0 : bit (5) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN1 : bit (5) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN2 : bit (5) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN3 : bit (5) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN4 : bit (5) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN5 : bit (5) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN6 : bit (5) > } +{ 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN7 : bit (5) > } ; + +``` + +< Uplink TBF Assignment struct > ::= + +-- Recursive for multiple TBFs + +``` + +< PFI : bit (7) > +< RLC_MODE : bit (1) > +< UPLINK_TFI_ASSIGNMENT : bit (5) > +{ 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } +{ 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } +{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } +{ + 0 < USF_ALLOCATION : bit (3) > + | 1 { 1 < USF Assignment: < USF Assignment struct > > } ** 0 } ; + +``` + +``` + +< USF Assignment struct > ::= -- Recursive for multiple USFs (per TBF) + { 0 | 1 < USF_ALLOCATION : bit (3) > }; -- '0' indicates no valid USF for this TS + + ::= + < Extended Dynamic Allocation : bit(1)> + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + < USF_GRANULARITY : bit (1) > + { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + { 0 -- Timeslot Allocation + { 0 | 1 < USF_TN0 : bit (3) > } + { 0 | 1 < USF_TN1 : bit (3) > } + { 0 | 1 < USF_TN2 : bit (3) > } + { 0 | 1 < USF_TN3 : bit (3) > } + { 0 | 1 < USF_TN4 : bit (3) > } + { 0 | 1 < USF_TN5 : bit (3) > } + { 0 | 1 < USF_TN6 : bit (3) > } + { 0 | 1 < USF_TN7 : bit (3) > } + | 1 -- Timeslot Allocation with Power Control Parameters + < ALPHA : bit (4) > + { 0 | 1 < USF_TN0 : bit (3) > + < GAMMA_TN0 : bit (5) > } + { 0 | 1 < USF_TN1 : bit (3) > + < GAMMA_TN1 : bit (5) > } + { 0 | 1 < USF_TN2 : bit (3) > + < GAMMA_TN2 : bit (5) > } + { 0 | 1 < USF_TN3 : bit (3) > + < GAMMA_TN3 : bit (5) > } + { 0 | 1 < USF_TN4 : bit (3) > + < GAMMA_TN4 : bit (5) > } + { 0 | 1 < USF_TN5 : bit (3) > + < GAMMA_TN5 : bit (5) > } + { 0 | 1 < USF_TN6 : bit (3) > + < GAMMA_TN6 : bit (5) > } + { 0 | 1 < USF_TN7 : bit (3) > + < GAMMA_TN7 : bit (5) > } + }; + +< RLC Entity Struct > ::= + < UPLINK_TFI_ASSIGNMENT : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < PFI : bit (7) >; +< Additional PFCs struct > ::= + < UPLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < PFI : bit (7) >; + +``` + +**Table 10.5.2.25c.2: RR PACKET UPLINK ASSIGNMENT value part details** + +**TIMESLOT\_ALLOCATION** (8 bit field) + This field is encoded as the TIMESLOT\_ALLOCATION field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +**CHANNEL\_CODING\_COMMAND** (2 bit field) + This field is encoded as the CHANNEL\_CODING\_COMMAND field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +**EGPRS\_MCS\_MODE** (4 bit field) + For backward compatibility reasons, the receiver of this message shall consider the case that the EGPRS\_MCS\_MODE parameter may not be present in the message. EGPRS\_MCS\_MODE is present for EGPRS only and if present the CHANNEL\_CODING\_COMMAND which is for GPRS mobiles is not valid. This field is coded as the EGPRS Modulation and Coding Scheme IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **RESEGMENT** (1 bit field) + +This field is coded as the RESEGMENT bit in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **EGPRS Window Size IE** + +This field is encoded as the EGPRS window size IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **TLLI\_BLOCK\_CHANNEL\_CODING** (1 bit field) + +This field is encoded as the TLLI\_BLOCK\_CHANNEL\_CODING field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Packet Timing Advance IE** + +This field is encoded as the Packet Timing Advance IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +###### **Dynamic Allocation struct** + +This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation. + +##### **Extended Dynamic Allocation** (1 bit field) + +This information field indicates the medium access mode to be used during the TBF. + +- 0 Dynamic Allocation +- 1 Extended Dynamic Allocation + +##### **UPLINK\_TFI\_ASSIGNMENT** (5 bit field) + +If present, this field is encoded as the UPLINK\_TFI\_ASSIGNMENT information element in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. If EMST is used (see 3GPP TS 44.060), each TFI identifies an RLC entity allocated on the uplink TBF. If EMSR is supported (see 3GPP TS 44.060), each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the uplink TBF. + +##### **Power Control Parameters IE** + +If present, this field is encoded as the Power Control Parameters IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **USF for Timeslot Number 0 (TN0)** (3 bit field) + +##### **USF for Timeslot Number 1 (TN1)** (3 bit field) + +##### **USF for Timeslot Number 2 (TN2)** (3 bit field) + +##### **USF for Timeslot Number 3 (TN3)** (3 bit field) + +##### **USF for Timeslot Number 4 (TN4)** (3 bit field) + +##### **USF for Timeslot Number 5 (TN5)** (3 bit field) + +##### **USF for Timeslot Number 6 (TN6)** (3 bit field) + +##### **USF for Timeslot Number 7 (TN7)** (3 bit field) + +If present, these fields are encoded as the USF for Timeslot Number X field (where $0 \leq X < 8$ ) in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **ALPHA** (4 bit field) + +The ALPHA Power control parameter field is coded according to the following table: +bits +4 3 2 1 +0 0 0 0 $\alpha = 0.0$ +0 0 0 1 $\alpha = 0.1$ +: : : +1 0 0 1 $\alpha = 0.9$ +1 0 1 0 $\alpha = 1.0$ + +All other values are reserved in this version of the protocol and shall be interpreted by the mobile station as $\alpha = 1.0$ . + +##### **TIMESLOT\_NUMBER** (3 bit field) + +If present, this field is encoded as the TIMESLOT\_NUMBER field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **GAMMA\_TN** (5 bit field) + +The GAMMA\_TN field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. + +##### **P0 and PR\_MODE fields** + +These fields are optional downlink power control parameters and are encoded as in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Packet Extended Timing Advance (2 bit field)** + +This bit field is used to support Extended Timing Advance. + +##### **Bit** + +- 1 bit 7 of the Timing Advance IE defined in sub-clause 10.5.2.40 +- 2 bit 8 of the Timing Advance IE defined in sub-clause 10.5.2.40 + +##### **PFI (7 bit field)** + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. If EMST is used (see 3GPP TS 44.060), this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported (see 3GPP TS 44.060), this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity. + +##### **USF GRANULARITY (1 bit field)** + +This field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation, see 3GPP TS 44.060: + +##### **Bit** + +- 0 the mobile station shall transmit one RLC/MAC block; +- 1 the mobile station shall transmit four consecutive RLC/MAC blocks. + +##### ***Extension and Message escape fields*** + +For mobile stations implemented according to this version of the protocol, those fields shall be considered as reserved values. + +##### **RLC\_MODE (1 bit field)** + +This field is encoded as the RLC\_MODE field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Uplink EGPRS Level** + +The coding of this information element is as the EGPRS Level IE as defined in 3GPP TS 44.060. A mobile station which does not support EGPRS2 in the uplink shall ignore this IE. + +##### **NPM Transfer Time (5 bit field)** + +This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. + +In case of single TBF allocation there is at most one NPM Transfer Time field. In case of multiple TBF allocation, the list of NPM Transfer Time fields is ordered as described by the loops in the Multiple TBF Allocation struct. + +##### **FANR (1 bit field)** + +This field indicates whether FANR is activated. This information element is defined in 3GPP TS 44.060. + +##### **REPORTED TIMESLOTS (8 bit field)** + +The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is defined in 3GPP TS 44.060. + +##### **TSH (2 bit field)** + +This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent and is defined in 3GPP TS 44.060. + +##### **Pulse Format** + +This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in 3GPP TS 44.060. + +**Measurement\_Control\_UTRAN** (1 bit field) +**Measurement\_Control\_E-UTRAN** (1 bit field) +**UTRAN\_FREQUENCY\_INDEX** (5 bit field) + This field is defined in sub-clause 9.1.54 +**E-UTRAN\_FREQUENCY\_INDEX** (3 bit field) + This field is defined in sub-clause 9.1.55. + +**EMST\_NW\_Capability** (1 bit field) + This field indicated the network's support of EMST. This information element is defined in 3GPP TS 44.060. + +**EMSR Additional PFCs 1** +**EMSR Additional PFCs 2** +**EMSR Additional PFCs 3** + These information elements are defined in 3GPP TS 44.060. + +#### 10.5.2.25d RR Packet Downlink Assignment + +The *RR Packet Downlink Assignment* information element is sent by the network to the mobile station to indicate the assigned downlink resources. + +The *RR Packet Downlink Assignment* information element is coded as shown in figure 10.5.2.25d.1 and tables 10.5.2.25d.1 and 10.5.2.25d.2. + +The *RR Packet Downlink Assignment* is a type 4 information element with a minimum length of 5 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------|---|---|---|---|---|---|---|-------------| +| RR Packet Downlink Assignment IEI | | | | | | | | octet 1 | +| Length of RR Packet Downlink Assignment value part | | | | | | | | octet 2 | +| RR Packet Downlink Assignment value part | | | | | | | | octet 3 - n | + +**Figure 10.5.2.25d.1: RR PACKET DOWNLINK ASSIGNMENT information element** + +Table 10.5.2.25d.1: RR PACKET DOWNLINK ASSIGNMENT value part + +``` + +< RR Packet Downlink Assignment value part > ::= + < MAC_MODE : bit (2) > + < RLC_MODE : bit (1) > + < TIMESLOT_ALLOCATION : bit (8) > + < Packet Timing Advance : Packet Timing Advance IE > + { 0 | 1 < P0 : bit (4) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < PR_MODE : bit (1) > } + { 0 | 1 < Power Control Parameters : Power Control Parameters IE > } + { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + { null -- Receiver compatible with earlier release + | { 0 | 1 -- indicates EGPRS TBF mode, see 3GPP TS 44.060 + < EGPRS Window Size : < EGPRS Window Size IE >> + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { null | 0 bit** = < no string > -- Receiver backward compatible + | 1 -- Additions for REL-6 + { 1 < Multiple Downlink TBF Assignment : < Multiple Downlink TBF Assignment struct > > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier release + | 1 -- Additions for REL-7 + < FANR: bit (1) > + { 1 + { 0 | 1 < NPM Transfer Time : bit (5) > } + < EVENT_BASED_FANR: bit (1) > + }** 0 + < Downlink EGPRS Level: < EGPRS Level IE >> + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-8 + { 0 | 1 { 1 < Measurement_Control_E-UTRAN : bit(1) > + < E-UTRAN_FREQUENCY_INDEX : bit (3) > + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 + }** 0 + } + { 0 | 1 { 1 < Measurement_Control_UTRAN : bit(1) > + < UTRAN_FREQUENCY_INDEX : bit (5) > + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 + }** 0 + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + { 0 -- EMST is not used + | 1 < RLC Entity 2 : < RLC Entity Struct > > + { 0 + | 1 < RLC Entity 3 : < RLC Entity Struct > > } + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + < spare bit > ** + } -- End of additions for Rel-10 + } -- End of additions for Rel-9 + } -- End of additions for Rel-8 + } -- End of additions for Rel-7 + } -- End of additions for Rel-6 + } ; -- End of additions for R99 +< Multiple Downlink TBF Assignment struct > ::= + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + < TIMESLOT_ALLOCATION : bit (8) > + { 1 < Downlink TBF assignment : < Downlink TBF assignment struct > > } ** 0 ; + +``` + +``` + +< Downlink TBF assignment struct > ::= + < PFI : bit (7) > + < RLC_MODE : bit (1) > + < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE >> } ; + +< RLC Entity Struct > ::= + < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE >> } + < PFI : bit (7) > ; + +< Additional PFCs struct > ::= + < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < PFI : bit (7) > ; + +``` + +**Table 10.5.2.25d.2: RR PACKET DOWNLINK ASSIGNMENT +value part details** + +##### **MAC\_MODE (2 bit field)** + +This field is encoded as the MAC\_MODE information field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **RLC\_MODE (1 bit field)** + +This field is encoded as the RLC\_MODE field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **TIMESLOT\_ALLOCATION (8 bit field)** + +This field is encoded as the TIMESLOT\_ALLOCATION field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Packet Timing Advance IE** + +This field is encoded as the Packet Timing Advance IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **P0 and PR\_MODE fields** + +These fields are optional downlink power control parameters and are encoded as in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Power Control Parameters IE** + +This field is encoded as the Power Control Parameters IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **DOWNLINK\_TFI\_ASSIGNMENT (5 bit field)** + +If present, this field is encoded as the DOWNLINK\_TFI\_ASSIGNMENT information element in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. Occurrences of the **DOWNLINK\_TFI\_ASSIGNMENT** field in the **Multiple Downlink TBF Assignment** struct take precedence over any other occurrence of this field in the message (e.g. in the main message body). If EMST is used (see 3GPP TS 44.060), each TFI identifies an RLC entity allocated on the downlink TBF. If EMSR is supported (see 3GPP TS 44.060), each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the downlink TBF. + +##### **EGPRS Window Size IE** + +This field is encoded as the EGPRS window size IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **LINK\_QUALITY\_MEASUREMENT\_MODE (2 bit field)** + +This field is encoded as the LINK\_QUALITY\_MEASUREMENT\_MODE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Packet Extended Timing Advance** (2 bit field) + +This bit field is used for support of Extended Timing Advance. + +##### **Bit** + +- | | | +|---|----------------------------------------------------------------| +| 1 | bit 7 of the Timing Advance IE defined in sub-clause 10.5.2.40 | +| 2 | bit 8 of the Timing Advance IE defined in sub-clause 10.5.2.40 | + +##### **Uplink Control Timeslot** (3 bit field) + +This field contains the timeslot number of the timeslot where the uplink PACCH for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. The mobile station shall send all uplink control messages on the PACCH/U on the uplink control timeslot. If the uplink control message relates to a TBF which does not have a valid TFI on the downlink timeslot corresponding to the uplink control timeslot, it shall indicate (one of) the downlink timeslot(s) associated with that downlink TBF in the TIMESLOT\_NUMBER field. The combination of downlink TFI and timeslot number enables the network to uniquely identify the TBF referred to in this message. + +##### **PFI** (7 bit field) + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. If EMST is used (see 3GPP TS 44.060), this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported (see 3GPP TS 44.060), this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity. + +##### **NPM Transfer Time** (5 bit field) + +This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. + +In case of single TBF allocation there is at most one NPM Transfer Time field. In case of multiple TBF allocation, the list of NPM Transfer Time fields is ordered as described by the loops in the Multiple Downlink TBF Assignment struct. + +##### **EVENT\_BASED\_FANR** (1 bit field) + +This field indicates whether the event-based FANR shall be used for the assigned TBF. This field shall be ignored if FANR is not activated. This information element is defined in 3GPP TS 44.060. + +In case of single TBF allocation there is at most one EVENT\_BASED\_FANR field. In case of multiple TBF allocation, the list of EVENT\_BASED\_FANR fields is ordered as described by the loops in the Multiple Downlink TBF Assignment struct. + +##### **FANR** (1 bit field) + +This field indicates whether FANR is activated. This information element is defined in 3GPP TS 44.060. + +##### **Downlink EGPRS Level** + +The coding of this information element is defined in 3GPP TS 44.060. + +##### **Measurement\_Control\_UTRAN** (1 bit field) + +##### **Measurement\_Control\_E-UTRAN** (1 bit field) + +##### **UTRAN\_FREQUENCY\_INDEX** (5 bit field) + +This field is defined in sub-clause 9.1.54 + +##### **E-UTRAN\_FREQUENCY\_INDEX** (3 bit field) + +This field is defined in sub-clause 9.1.55. + +##### **EMSR Additional PFCs 1** + +##### **EMSR Additional PFCs 2** + +##### **EMSR Additional PFCs 3** + +These information elements are defined in 3GPP TS 44.060. + +#### **10.5.2.25e RR Packet Downlink Assignment Type 2** + +The *RR Packet Downlink Assignment Type 2* information element is sent by the network to the mobile station to indicate the assigned downlink resources. + +The *RR Packet Downlink Assignment Type 2* information element is coded as shown in figure 10.5.2.25e.1 and tables 10.5.2.25e.1 and 10.5.2.25e.2. + +The *RR Packet Downlink Assignment Type 2* is a type 4 information element with a minimum length of 5 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|-----------------------------------------------------------|---|---|---|---|---|---|-------------| +| | RR Packet Downlink Assignment Type 2 IEI | | | | | | | octet 1 | +| | Length of RR Packet Downlink Assignment Type 2 value part | | | | | | | octet 2 | +| | RR Packet Downlink Assignment Type 2 value part | | | | | | | octet 3 - n | + +**Figure 10.5.2.25e.1: RR PACKET DOWNLINK ASSIGNMENT TYPE 2 information element** + +**Table 10.5.2.25e.1: RR PACKET DOWNLINK ASSIGNMENT TYPE 2 value part** + +``` + +< RR Packet Downlink Assignment Type 2 value part > ::= + < RLC_MODE : bit (1) > + { 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit (1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit (1) > } } + { 0 | 1 < Power Control Parameters C1 : < Power Control Parameters IE > > } + { 0 | 1 < Power Control Parameters C2 : < Power Control Parameters IE > > } + { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } + < EGPRS Window Size : < EGPRS Window Size IE > > + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 -- BTTI mode + < FANR: bit (1) > + { 1 < BTTI Multiple Downlink Assignment : < BTTI Multiple Downlink Assignment struct > > } ** 0 + | 1 -- RTTI mode + { 0 -- Single Carrier Assignment + { 00 -- Default PDCH-pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment SC : + < RTTI Multiple Downlink Assignment SC struct > > } ** 0 + | 1 -- Dual Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment DC : + < RTTI Multiple Downlink Assignment DC struct > > } ** 0 + } + } + < Downlink EGPRS Level: < EGPRS Level IE > > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-8 + { 0 | 1 { 1 < Measurement_Control_E-UTRAN : bit(1) > + < E-UTRAN_FREQUENCY_INDEX : bit (3) > + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 + } ** 0 + } + { 0 | 1 { 1 < Measurement_Control_UTRAN : bit(1) > + < UTRAN_FREQUENCY_INDEX : bit (5) > + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 + } ** 0 + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier release + | 1 -- Additions for Rel-99 + { 0 -- EMST is not used + | 1 < RLC Entity 2 : < RLC Entity Struct > > + { 0 + | 1 < RLC Entity 3 : < RLC Entity Struct > > } + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-11 + +``` + +``` + + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + < spare bit > ** + } -- End of additions for Rel-11 + } -- End of additions for Rel-10 + } -- End of additions for Rel-9 +}; -- End of additions for Rel-8 +< BTTI Multiple Downlink Assignment struct > ::= +{ 0 | 1 < Uplink Control Timeslot : bit (3) > } +{ 0 | 1 < TIMESLOT_ALLOCATION_C1 : bit (8) > } +{ 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } +{ 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< RTTI Multiple Downlink Assignment SC struct > ::= + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< RTTI Multiple Downlink Assignment DC struct > ::= + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< Downlink TBF assignment 2 struct > ::= + < PFI : bit (7) > + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < EVENT_BASED_FANR : bit (1) > + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } ; + +< RLC Entity Struct > ::= + < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < PFI : bit (7) > ; + +< Additional PFCs struct > ::= + < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < PFI : bit (7) > ; + +``` + +**Table 10.5.2.25e.2: RR PACKET DOWNLINK ASSIGNMENT TYPE 2** +value part details + +##### **RLC\_MODE (1 bit field)** + +This field is encoded as the RLC\_MODE field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **TIMESLOT\_ALLOCATION\_C1, TIMESLOT\_ALLOCATION\_C2 (8 bit field)** + +These information fields indicate the timeslots assigned for use during the TBF on carrier 1 (respectively, carrier 2) of a dual carrier configuration. These fields are encoded as in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **P0\_C1, P0\_C2, PR\_MODE\_C1 and PR\_MODE\_C2 fields** + +These fields are optional downlink power control parameters and are encoded as in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Power Control Parameters C1, Power Control Parameters C2** + +These information elements are encoded as in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **DOWNLINK\_TFI\_ASSIGNMENT (5 bit field)** + +If present, this field is encoded as the DOWNLINK\_TFI\_ASSIGNMENT information element in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. Occurrences of the **DOWNLINK\_TFI\_ASSIGNMENT** field in the **Downlink TBF Assignment 2** struct take precedence over any other occurrence of this field in the message (e.g. in the main message body). If EMST is used (see 3GPP TS 44.060), each TFI identifies an RLC entity allocated on the downlink TBF. If EMSR is supported (see 3GPP TS 44.060), each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the downlink TBF. + +##### **EGPRS Window Size IE** + +This field is encoded as the EGPRS window size IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **LINK\_QUALITY\_MEASUREMENT\_MODE** + +This field is encoded as the LINK\_QUALITY\_MEASUREMENT\_MODE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +##### **Uplink Control Timeslot (3 bit field)** + +This field contains the timeslot number of the timeslot where the uplink PACCH for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. The mobile station shall send all uplink control messages on the PACCH/U on the uplink control timeslot on the same carrier as the CS timeslot. If the uplink control message relates to a TBF which does not have a valid TFI on the downlink timeslot corresponding to the uplink control timeslot, it shall indicate (one of) the downlink timeslot(s) associated with that downlink TBF in the TIMESLOT\_NUMBER field. The combination of downlink TFI and timeslot number enables the network to uniquely identify the TBF referred to in this message. + +##### **PFI (7 bit field)** + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. If EMST is used (see 3GPP TS 44.060), this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported (see 3GPP TS 44.060), this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity. + +##### **EVENT\_BASED\_FANR (1 bit field)** + +This field indicates whether the event-based FANR shall be used for the assigned TBF. This field shall be ignored if FANR is not activated. This information element is defined in 3GPP TS 44.060. + +##### **DOWNLINK\_PDCH\_PAIRS\_C1** + +##### **DOWNLINK\_PDCH\_PAIRS\_C2** + +##### **UPLINK\_PDCH\_PAIRS\_C1** + +##### **UPLINK\_PDCH\_PAIRS\_C2** + +These fields indicate the set of timeslots which make up the PDCH pairs. These fields are formatted as defined for the PACKET TIMESLOT RECONFIGURE message in 3GPP TS 44.060. + +##### **FANR (1 bit field)** + +This field indicates whether FANR is activated. This information element is defined in 3GPP TS 44.060. + +##### **Downlink EGPRS Level** + +The coding of this information element is defined in 3GPP TS 44.060. + +##### **Measurement\_Control\_UTRAN (1 bit field)** + +##### **Measurement\_Control\_E-UTRAN (1 bit field)** + +##### **UTRAN\_FREQUENCY\_INDEX (5 bit field)** + +These fields are defined in sub-clause 9.1.54 + +##### **E-UTRAN\_FREQUENCY\_INDEX (3 bit field)** + +This field is defined in sub-clause 9.1.55. + +##### **NPM Transfer Time (5 bit field)** + +This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. + +##### **EMSR Additional PFCs 1** + +##### **EMSR Additional PFCs 2** + +##### **EMSR Additional PFCs 3** + +These information elements are defined in 3GPP TS 44.060. + +##### **EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)** + +See 3GPP TS 44.060 (Packet Downlink Assignment message). + +#### 10.5.2.26 Page Mode + +The purpose of the *Page Mode* information element is to control the action of the mobile station belonging to the paging subgroup corresponding to the paging subchannel. + +The *Page Mode* information element is coded as shown in figure 10.5.2.26.1 and table 10.5.2.26.1. + +The *Page Mode* is a type 1 information element. + +![](2f903f194dbf70f3aa6c281a6f96db03_img.jpg) + +| | | | | | | | | | +|---|---------------|---|---|------------|------------|----|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | Page Mode IEI | | | 0
spare | 0
spare | PM | | octet 1 | + +**Figure 10.5.2.26.1: Page Mode information element** + +**Table 10.5.2.26.1: Page Mode information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PM (octet 1) | +| Bits | +| 2 1 | +| 0 0 Normal paging. | +| 0 1 Extended paging. | +| 1 0 Paging reorganization. | +| 1 1 Same as before. | +| NOTE 1: The value "same as before" has been defined instead of "reserved" to allow the use of this coding with another meaning in an upwards compatible way in later phases of the GSM system. | +| NOTE 2: This information element is ignored when received by a mobile station that has enabled EC operation. An MS that has enabled EC operation only attempts page reception using the EC-PCH where it can detect a paging reorganization condition as a result of re-acquiring EC-SI information (e.g. due to detecting a change in the EC-BCCH CHANGE MARK field sent in the EC-SCH ). | + +10.5.2.26a (void) + +10.5.2.26b (void) + +10.5.2.26c (void) + +10.5.2.26d (void) + +#### 10.5.2.27 NCC Permitted + +The purpose of the *NCC Permitted* information element is to provide a definition of the allowed NCCs on the BCCH carriers to be reported in the MEASUREMENT REPORT message by the mobile stations in the cell. An MS supporting network sharing (see 3GPP TS 23.251 [103], 3GPP TS 45.008 [34]) shall use this parameter in the reselection procedure. + +The *NCC Permitted* information element is coded as shown in figure 10.5.2.27.1 and table 10.5.2.27.1. + +The *NCC Permitted* is a type 3 information element with 2 octets length. + +![](aed979c26976e0b8dc2b00653e2667bc_img.jpg) + +| | | | | | | | | | +|---------------|-------------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | NCC Permitted IEI | | | | | | | octet 1 | +| NCC permitted | | | | | | | | octet 2 | + +**Figure 10.5.2.27.1: NCC Permitted information element** + +**Table 10.5.2.27.1: NCC Permitted information element** + +NCC permitted (octet 2) + The NCC permitted field is coded as a bit map, i.e. + bit N is coded with a "0" if the BCCH carrier with + NCC = N-1 is not permitted for monitoring and with a + "1" if the BCCH carrier with NCC = N-1 is permitted + for monitoring; N = 1,2,...,8. + +#### 10.5.2.28 Power Command + +The purpose of the *Power Command* information element is to provide the power level to be used by the mobile station. + +The *Power Command* information element is coded as shown in figure 10.5.2.28.1 and table 10.5.2.28.1. + +The *Power Command* is a type 3 information element with 2 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------|----------|-------------|-------------|---|---|---|---|---------| +| Power Command IEI | | | | | | | | octet 1 | +| 0
spare | EPC mode | FPC_EP
C | POWER LEVEL | | | | | octet 2 | + +**Figure 10.5.2.28.1: Power Command information element****Table 10.5.2.28.1: Power Command information element** + +EPC\_mode (octet 2) + The EPC mode field (octet 2) indicates whether the assigned channel(s) shall be in enhanced power control (EPC) mode. It is only valid for channels on which EPC may be used. It is coded as follows: + +Value + +0 Channel(s) not in EPC mode + 1 Channel(s) in EPC mode + +FPC\_EPC (octet 2) + The FPC\_EPC field (octet 2) has different interpretation depending on the channel mode of the assigned channel(s) and the value of the EPC mode field. + +If the channel mode is such that fast power control (FPC) may be used, the FPC\_EPC field indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: + +Value + +0 FPC not in use + 1 FPC in use + +If the channel mode is such that EPC may be used and the EPC mode field indicates that the channel is in EPC mode, the FPC\_EPC field indicates whether EPC shall be used for uplink power control. It is coded as follows: + +Value + +0 EPC not in use for uplink power control + 1 EPC in use for uplink power control + +Power level (octet 2) + The power level field is coded as the binary Representation of the "power control level", see 3GPP TS 3GPP TS 45.005. This value shall be used by the mobile station According to 3GPP TS 45.008. + +Range: 0 to 31. + +##### 10.5.2.28a Power Command and access type + +The purpose of the *Power Command and access type* information element is to provide the power level to be used by the mobile station and the indication that the mobile station can avoid the transmission of handover access. + +The *Power Command and access type* information element is coded as shown in figure 10.5.2.28a.1 and table 10.5.2.28a.1. + +The *Power Command and access type* is a type 3 information element with 2 octets length. + +![](f3fd3ff8f78da4c2a4d39bb6330c49a1_img.jpg) + +| | | | | | | | | | | +|--|-----------------------------------|----------|-------------|-------------|---|---|---|---|---------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | Power Command and Access Type IEI | | | | | | | | octet 1 | +| | ATC | EPC mode | FPC_EP
C | POWER LEVEL | | | | | | +| | | | | | | | | | octet 2 | + +**Figure 10.5.2.28a.1: Power Command and access type information element** + +**Table 10.5.2.28a.1: Power Command and access type information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ATC (Access Type Control) (octet 2) | +| Bit 8 | +| 0      Sending of Handover access is mandatory | +| 1      Sending of Handover access is optional | +| EPC_mode (octet 2) | +| The EPC mode field (octet 2) indicates whether the assigned channel(s) shall be in enhanced power control (EPC) mode. It is only valid for channels on which EPC may be used. It is coded as follows: | +| Value | +| 0      Channel(s) not in EPC mode | +| 1      Channel(s) in EPC mode | +| FPC_EPC (octet 2) | +| The FPC_EPC field (octet 2) has different interpretation depending on the channel mode of the assigned channel (s) and the value of the EPC mode field. | +| If the channel mode is such that fast power control (FPC) may be used, the FPC_EPC field indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: | +| Value | +| 0      FPC not in use | +| 1      FPC in use | +| If the channel mode is such that EPC may be used and the EPC mode field indicates that the channel is in EPC mode, the FPC_EPC field indicates whether EPC shall be used for uplink power control. It is coded as follows: | +| Value | +| 0      EPC not in use for uplink power control | +| 1      EPC in use for uplink power control | +| Power level (octet 2) | +| The power level field is coded as the binary Representation of the "power control level", see 3GPP TS 3GPP TS 45.005. This value shall be used by the mobile station According to 3GPP TS 45.008. | +| Range: 0 to 31. | + +#### 10.5.2.29 RACH Control Parameters + +The purpose of the *RACH Control Parameters* information element is to provide parameters used to control the RACH utilization. This information element is broadcast to mobile stations in SYSTEM INFORMATION TYPE 1, 2, 2bis, 3, and 4 messages. + +The *RACH Control Parameters* information element is coded as shown in figure 10.5.2.29.1 and table 10.5.2.29.1. + +The *RACH Control Parameters* is a type 3 information element with 4 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------|-----------------------------|------------|-----------|-----------|-----------|------------------------|-----------|---------| +| | RACH Control Parameters IEI | | | | | | | octet 1 | +| Max retrans | | Tx-integer | | | | CELL
BARR
ACCESS | RE | octet 2 | +| AC
C15 | AC
C14 | AC
C13 | AC
C12 | AC
C11 | AC
C10 | AC
C09 | AC
C08 | octet 3 | +| AC
C07 | AC
C06 | AC
C05 | AC
C04 | AC
C03 | AC
C02 | AC
C01 | AC
C00 | octet 4 | + +**Figure 10.5.2.29.1: RACH Control Parameters information element** + +**Table 10.5.2.29.1: RACH Control Parameters information element** + +| | | | +|--------------------------------------------------------------------------------------------------------------------------|---|---------------------------------------------------------------------------------------------------------------| +| Max retrans, Maximum number of retransmissions (octet 2) | | | +| Bits | | | +| 8 | 7 | | +| 0 | 0 | Maximum 1 retransmission | +| 0 | 1 | Maximum 2 retransmissions | +| 1 | 0 | Maximum 4 retransmissions | +| 1 | 1 | Maximum 7 retransmissions | +| Tx-integer, Number of slots to spread transmission (octet 2) | | | +| Bits | | | +| 6 | 5 | 4 3 | +| 0 | 0 | 0 0 3 slots used to spread transmission | +| 0 | 0 | 0 1 4 slots used to spread transmission | +| 0 | 0 | 1 0 5 slots used to spread transmission | +| 0 | 0 | 1 1 6 slots used to spread transmission | +| 0 | 1 | 0 0 7 slots used to spread transmission | +| 0 | 1 | 0 1 8 slots used to spread transmission | +| 0 | 1 | 1 0 9 slots used to spread transmission | +| 0 | 1 | 1 1 10 slots used to spread transmission | +| 1 | 0 | 0 0 11 slots used to spread transmission | +| 1 | 0 | 0 1 12 slots used to spread transmission | +| 1 | 0 | 1 0 14 slots used to spread transmission | +| 1 | 0 | 1 1 16 slots used to spread transmission | +| 1 | 1 | 0 0 20 slots used to spread transmission | +| 1 | 1 | 0 1 25 slots used to spread transmission | +| 1 | 1 | 1 0 32 slots used to spread transmission | +| 1 | 1 | 1 1 50 slots used to spread transmission | +| CELL_BAR_ACCESS, Cell Barred for Access (octet 2) | | | +| Bit 2 | | | +| 0 | | The cell is not barred, see 3GPP TS 23.022 | +| 1 | | The cell is barred, see 3GPP TS 23.022 | +| RE, Call reestablishment allowed (octet 2) | | | +| Bit 1 | | | +| 0 | | Call Reestablishment allowed in the cell | +| 1 | | Call Reestablishment not allowed in the cell | +| EC Emergency Call allowed (octet 3 bit 3) | | | +| Bit 3 | | | +| 0 | | Emergency call allowed in the cell to all MSs | +| 1 | | Emergency call not allowed in the cell except for the MSs that belong to one of the classes between 11 to 15. | +| AC CN, Access Control Class N (octet 3(except bit 3) and octet 4) | | | +| For a mobile station with AC C = N access is not barred if the AC CN bit is coded with a "0"; N = 0, 1, .. 9,11, .., 15. | | | + +#### 10.5.2.30 Request Reference + +The purpose of the *Request Reference* information element is to provide the random access information used in the channel request and the frame number, FN modulo 42432 in which the channel request was received. + +The *Request Reference* information element is coded as shown in figure 10.5.2.30.1 and table 10.5.2.30.1. + +The *Request Reference* is a type 3 information element with 4 octets length. + +![](af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|----|-------------------|---|---|---|---------| +| Request Reference IEI | | | | | | | | octet 1 | +| RA | | | | | | | | octet 2 | +| T1' | | | | T3
(high part) | | | | octet 3 | +| T3
(low part) | | | T2 | | | | | octet 4 | + +**Figure 10.5.2.30.1: Request Reference information element** + +**Table 10.5.2.30.1: Request Reference information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RA, Random Access Information (octet 2)
This is an unformatted 8 bit field. Typically the contents of this field are coded the same as the CHANNEL REQUEST message shown in Figure 9.1.8.1 and Table 9.1.8.1, sub-clause 9.1.8. When included in an EC IMMEDIATE ASSIGNMENT TYPE 1 message (see sub-clause 9.1.59) this field is coded as the 8 least significant bits of the corresponding EC PACKET CHANNEL REQUEST message sent on the RACH (see sub-clause 9.1.65) and is never used to indicate the presence of Extended RA information. The 8 least significant bits of an EC PACKET CHANNEL REQUEST message are identified using the same method for identifying the 5 least significant of an EGPRS PACKET CHANNEL REQUEST message described in sub-clause 10.5.2.16 for the case where the Extended RA field is included in the IA Rest Octets information element (i.e. when the Request Reference IE is included in the EC IMMEDIATE ASSIGNMENT TYPE 1 message the RA field shall include all fields of the EC PACKET CHANNEL REQUEST message except for the ‘EC-NumberOfBlocks’ field).

When included in an IMMEDIATE ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating ‘RLC Data Block’ method or ‘Page Response for Positioning Event’ (see sub-clause 3.5.2.1.2, sub-clause 3.11 and 3GPP TS 44.060 [76]) this field includes the 8 least significant bits of the corresponding EGPRS MULTILATERATION REQUEST message sent on the RACH (see 3GPP TS 44.060). In this case the Dedicated mode or TBF IE indicates that a Temporary Block Flow (TBF) is assigned by the IMMEDIATE ASSIGNMENT message (see sub-clause 10.5.2.25b).

When included in an IMMEDIATE ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating the ‘Access Burst’ method or ‘Extended Access Burst’ method this field is ignored. In this case the Dedicated mode or TBF IE indicates that no TBF or dedicated mode resources are assigned by the IMMEDIATE ASSIGNMENT message.

| +|

T1' (octet 3)
The T1' field is coded as the binary representation of (FN div 1326) mod 32.

| +|

T3 (octet 3 and 4)
The T3 field is coded as the binary representation of FN mod 51. Bit 3 of octet 3 is the most significant bit and bit 6 of octet 4 is the least significant bit.

| +|

T2 (octet 4)
The T2 field is coded as the binary representation of FN mod 26.

NOTE 1: The frame number, FN modulo 42432 can be calculated as
51 \times ((T3 - T2) \bmod 26) + T3 + 51 \times 26 \times T1'

| + +##### 10.5.2.30a Random Reference/ Establishment Cause + +The purpose of the *Random Reference/ Establishment Cause* information element within Priority Uplink Request is to provide the reason for the request and a random reference to correlate a VGCS UPLINK GRANT with the PRIORITY UPLINK REQUEST message sent by a mobile station. It is based on the UPLINK ACCESS message (subclause 9.1.45). + +The *Random Reference/ Establishment Cause* is coded as shown in figure 10.5.2.30a.1 and table 10.5.2.30a.1 + +The *Random Reference/Establishment Cause* is a type 3 information element with 1 octet length. + +###### Establishment Cause (octet 1) + +This information field indicates the reason for requesting the uplink. This field has a variable length (from 3 bits to 8 bits) + +###### **Randon Reference (octet 1)** + +This is an unformatted field with variable length (from 5 down to 0 bits) indicated by 'xxxxx' in the table below. + +| | | | | | | | | | +|---------------------|---|---|---|------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Establishment Cause | | | | Random Reference | | | | octet 1 | + +**Figure 10.5.2.30a.1: Random Reference/Establishment Cause information element****Table 10.5.2.30a.1: Random Reference/Establishment Cause information element** + +| Random Reference/ Establishment Cause (octet 1) | | | | | | | | | +|-------------------------------------------------|---|---|---|---|---|---|---|-----------------------------------| +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 1 | 1 | 0 | x | x | x | x | x | reserved | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | reserved | +| 1 | 0 | 1 | x | x | x | x | x | Privilege subscriber request | +| 1 | 1 | 1 | x | x | x | x | x | Emergency subscriber request | +| 0 | 0 | 0 | x | x | x | x | x | Reset emergency talker indication | +| other values reserved for future use | | | | | | | | | + +#### **10.5.2.31 RR Cause** + +The purpose of the *RR Cause* information element is to provide the reason for release or the reason for completion of an assignment or handover. + +The *RR Cause* information element is coded as shown in figure 10.5.2.31.1 and table 10.5.2.31.1. + +The *RR Cause* is a type 3 information element with 2 octets length. + +| | | | | | | | | | +|----------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| RR Cause IEI | | | | | | | | octet 1 | +| RR cause value | | | | | | | | octet 2 | + +**Figure 10.5.2.31.1: RR Cause information element****Table 10.5.2.31.1: RR Cause information element** + +| RR cause value (octet 2) | | | | | | | | | +|----------------------------------------------------------------------|---|---|---|---|---|---|---|--------------------------------------------------| +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Normal event | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Abnormal release, unspecified | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | Abnormal release, channel unacceptable | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | Abnormal release, timer expired | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Abnormal release, no activity on the radio path | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Preemptive release | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | UTRAN configuration unknown | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | Handover impossible, timing advance out of range | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | Channel mode unacceptable | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | Frequency not implemented | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | Originator or talker leaving group call area | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | Lower layer failure | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | Call already cleared | +| 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | Semantically incorrect message | +| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Invalid mandatory information | +| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | Message type non-existent or not implemented | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Message type not compatible with protocol state | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | Conditional IE error | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | No cell allocation available | +| 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | Protocol error unspecified | +| All other cause values shall be treated as 0000 0000, 'normal event' | | | | | | | | | +| The listed RR cause values are defined in Annex F. | | | | | | | | | + +#### **10.5.2.32 SI 1 Rest Octets** + +The *SI 1 Rest Octets* information element contains the position about the NCH and spare bits. + +The *SI 1 Rest Octets* information element is a type 5 information element with 1 octet length. + +``` + ::= + {L |H } + < Band indicator > + ; + +< Band indicator > ::= + < BAND_INDICATOR : bit == L > -- ARFCN indicates 1800 band + | < BAND_INDICATOR : bit == H > ; -- ARFCN indicates 1900 band +``` + +**Table 10.5.2.32.1a: SI 1 Rest Octets information element details** + +##### **BAND\_INDICATOR (1 bit)** + +The band indicator for 1800 and 1900 associates the ARFCN channel numbers to the GSM 1800 respectively to the PCN 1900 band, see 3GPP TS 45.005. + +**Table 10.5.2.32.1b: SI 1 Rest Octets information element** + +##### **NCH Position on the CCCH** + +The values in the NCH Position field indicates the block number of the CCCH block which is used for the first NCH block and the number of blocks used for the NCH. (The block numbering corresponds to table 5 in clause 7 of 3GPP TS 45.002) + +The absence of the NCH position field indicates that there is no NCH in the cell/on the carrying CCCH slot + +The following coding applies if 1 or more basic physical channels are used for CCCH, not combined with SDCCHs. + +| Value | No of blocks | Number of first block | +|-----------|--------------|-----------------------| +| 0 0 0 0 0 | 1 | 0 | +| 0 0 0 0 1 | 1 | 1 | +| 0 0 0 1 0 | 1 | 2 | +| 0 0 0 1 1 | 1 | 3 | +| 0 0 1 0 0 | 1 | 4 | +| 0 0 1 0 1 | 1 | 5 | +| 0 0 1 1 0 | 1 | 6 | +| 0 0 1 1 1 | 2 | 0 | +| 0 1 0 0 0 | 2 | 1 | +| 0 1 0 0 1 | 2 | 2 | +| 0 1 0 1 0 | 2 | 3 | +| 0 1 0 1 1 | 2 | 4 | +| 0 1 1 0 0 | 2 | 5 | +| 0 1 1 0 1 | 3 | 0 | +| 0 1 1 1 0 | 3 | 1 | +| 0 1 1 1 1 | 3 | 2 | +| 1 0 0 0 0 | 3 | 3 | +| 1 0 0 0 1 | 3 | 4 | +| 1 0 0 1 0 | 4 | 0 | +| 1 0 0 1 1 | 4 | 1 | +| 1 0 1 0 0 | 4 | 2 | +| 1 0 1 0 1 | 4 | 3 | +| 1 0 1 1 0 | 5 | 0 | +| 1 0 1 1 1 | 5 | 1 | +| 1 1 0 0 0 | 5 | 2 | +| 1 1 0 0 1 | 6 | 0 | +| 1 1 0 1 0 | 6 | 1 | +| 1 1 0 1 1 | 7 | 0 | + +Other values are reserved for future use. A mobile station receiving a reserved value shall behave as if the NCH position was not present + +In the case the CCCH configuration is not compatible with the NCH position (e.g., CCCH with combined SDCCH and the value different from 00000, 00001 or 00111), the mobile station shall behave as if the NCH Position field was not present. + +#### 10.5.2.33 SI 2bis Rest Octets + +The *SI 2bis Rest Octets* information element contains only spare bits. Its purpose is to allow the upward compatible introduction of new information on the BCCH in later phases. + +The *SI 2bis Rest Octets* information element is a type 5 information element with 1 octet length. + +**Table 10.5.2.33.1: SI 2bis Rest Octets information element** + +``` + ::= + ; +``` + +##### 10.5.2.33a SI 2ter Rest Octets + +SI2ter Rest Octets information element contains optional information on UTRAN cell(s) to be monitored by the mobile in the cell. It is used together with 3G Cell(s) from the SI2quater message to build the 3G Cell Reselection list, see sub-clause 3.4.1.2.1.7. Optionally this information element may in addition include thresholds that the mobile shall use for cell reselection. Information received in this message do not modify the 3G Neighbour Cell list used for reporting and defined in sub-clause 3.4.1.2.1.1. + +The *SI 2ter Rest Octets* information element is a type 5 information element with 4 octets length. + +**Table 10.5.2.33a.1: SI 2ter Rest Octets information element** + +``` +< SI2ter Rest Octets > ::= + { L | H < SI2ter_MP_CHANGE_MARK : bit(1) > + < SI2ter_3G_CHANGE_MARK : bit(1) > + < SI2ter_INDEX : bit(3) > + < SI2ter_COUNT : bit(3) > + { 0 | 1 < UTRAN FDD Description : < UTRAN FDD Description struct > > } + { 0 | 1 < UTRAN TDD Description : < UTRAN TDD Description struct > > } + { 0 | 1 < 3G MEASUREMENT Parameters Description : + < 3G MEASUREMENT Parameters Description struct >> } + { null | L -- Receiver compatible with earlier release + | H -- Additions in release R5: + { 0 | 1 < 3G Additional Measurement Parameters Description : + < 3G Additional Measurement Parameters Description struct >> } + } + } + ; + +< UTRAN FDD Description struct > ::= + 01 < FDD-ARFCN : bit (14) > + -- 21 bits are available if this structure is present on its own + -- requires 2+14=16 bits + -- The values '00', '10' and '11' were used in an earlier version + -- of the protocol and shall not be used. + + { 0 | 1 < Bandwidth_FDD : bit (3) > } ; + +< UTRAN TDD Description struct > ::= + 01 < TDD-ARFCN : bit (14) > + -- 21 bits are available if this structure is present on its own + -- requires 2+14=16 bits + -- The values '00', '10' and '11' were used in an earlier version + -- of the protocol and shall not be used. + + { 0 | 1 < Bandwidth_TDD : bit (3) > } ; + +< 3G MEASUREMENT Parameters Description struct > ::= + < Qsearch_I : bit (4) > + { 0 | 1 < FDD_Qoffset : bit (4) > + < FDD_Qmin : bit (3) > } + -- FDD Parameters + { 0 | 1 < TDD_Qoffset : bit (4) > } ; + -- TDD Parameters + +< 3G Additional Measurement Parameters Description struct > ::= + < FDD_Qmin_Offset : bit (3) > + < FDD_RSCPmin : bit (4) > ; + -- FDD Parameters +``` + +**Table 10.5.2.33a.2: SI 2ter Rest Octets information element details** + +**SI2ter\_MP\_CHANGE\_MARK** (1 bit field), SI2ter Rest Octet Measurement Parameter Change Mark. + +This parameter is used to indicate to the MS a change of information concerning 3G Measurement Parameters, as described in sub-clause 3.2.2.1, 'System information broadcasting'. + +**SI2ter\_3G\_CHANGE\_MARK** (1 bit field), SI2ter Rest Octet 3G Change Mark. + +This parameter is used to indicate to the MS a change of information concerning UTRAN FDD Description and UTRAN TDD Description, as described in sub-clause 3.2.2.1 'System information broadcasting'. + +**SI2ter\_INDEX** (3 bit field) and **SI2ter\_COUNT** (3 bit field) + +The purpose of the SI2ter\_INDEX and SI2ter\_COUNT fields is to indicate the number of individual sequences of SI2ter Rest Octet information elements and to assign an index to identify each of them. The SI2ter\_INDEX field is binary coded, range 0 to 7, and provides an index to identify the individual SI2ter Rest Octet information element. The SI2ter\_COUNT field is binary coded, range 0 to 7, and provides the SI2ter\_INDEX value for the last (highest indexed) information element in the sequence of SI2ter Rest Octet information elements. + +##### ***UTRAN FDD Description*** + +**FDD\_ARFCN** (14 bit field) + +This information element is defined as the UARFCN in 3GPP TS 25.101. Any non-supported frequencies shall be ignored. + +When a frequency is included with no scrambling code information (no scrambling code and no SC\_P\_SCG), this indicates all the scrambling codes. + +**Bandwidth\_FDD** (3 bit field) + +This optional information element will be used for future releases of the protocol. When missing, this indicates the present FDD bandwidth. When present, this shall not be considered as an error. + +##### ***UTRAN TDD Description*** + +**TDD\_ARFCN** (14 bit field) + +This optional information element is defined as the UARFCN in 3GPP TS 25.102. Any non-supported frequency shall be ignored. + +When a frequency is included with no Cell Parameter information, this indicates all the Cell Parameter values. + +##### ***3G Measurement Parameters Description:*** + +These parameters are defined in 3GPP TS 45.008. + +**Bandwidth\_TDD** (3 bit field) + +This optional information element refers to 3GPP TS 25.331. + +Bit + +321 + +000 3.84Mcps + +001 1.28Mcps + +All other values shall not be interpreted as an error. When missing, this indicates 3.84 Mcps. + +##### ***3G Additional Measurement Parameters Description*** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +If the *3G Additional MeasurementParameters Description* is included in more than one instance of the SI2ter message, the *3G Additional MeasurementParameters Description* of the instance with the highest SI2ter\_INDEX shall be used. + +#### **10.5.2.33b SI 2quater Rest Octets** + +The *SI 2quater Rest Octets* information element contains neighbour cell lists for UTRAN and/or E-UTRAN cells and/or CSG cells. For cell reselection to UTRAN, it is used with the SI 2ter Rest Octets information to build the 3G Cell Reselection list, see sub-clause 3.4.1.2.1.7. For cell reselection to E-UTRAN, it is used directly to build the E-UTRAN Neighbour Cell list. + +The *SI 2quater Rest Octets* information element is a type 5 information element with 20 octet length. + +###### **Table 10.5.2.33b.1: SI2quater Rest Octets information element** + +``` + +< SI2quater Rest Octets > ::= + + < BA_IND : bit (1) > + < 3G_BA_IND : bit (1) > + < MP_CHANGE_MARK : bit (1) > + < SI2quater_INDEX : bit (4) > + < SI2quater_COUNT : bit (4) > + + { 0 | 1 < Measurement_Parameters Description : < Measurement Parameters Description struct >> } + { 0 | 1 < GPRS_Real Time Difference Description : < GPRS_Real Time Difference Description struct >> } + { 0 | 1 < GPRS_BSIC Description : GPRS_BSIC Description struct > } + { 0 | 1 < GPRS_REPORT PRIORITY Description : < GPRS_REPORT_PRIORITY Description struct >> } + { 0 | 1 < GPRS_MEASUREMENT_Parameters Description : + < GPRS_MEASUREMENT Parameters Description struct >> } + { 0 | 1 < NC Measurement Parameters : < NC Measurement Parameters struct >> } + { 0 | 1 < extension length : bit (8) > + < < bit (val(extension length)+1) > & + { < SI2q Extension Information > ! { Ignore: bit ** = } } > } + + { 0 | 1 < 3G Neighbour Cell Description : < 3G Neighbour Cell Description struct >> } + { 0 | 1 < 3G Measurement Parameters Description : < 3G Measurement Parameters Description struct >> } + { 0 | 1 < GPRS_3G_MEASUREMENT Parameters Description : + < GPRS_3G MEASUREMENT Parameters Description struct >> } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-5: + { 0 | 1 < 3G Additional Measurement Parameters Description : + < 3G Additional Measurement Parameters Description struct >> } + { 0 | 1 < 3G ADDITIONAL MEASUREMENT Parameters Description 2 : + < 3G ADDITIONAL MEASUREMENT Parameters Description 2 struct >> } + + { null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-6: + < 3G_CCN_ACTIVE : bit (1) > + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-7: + { 0 | 1 < 700_REPORTING_OFFSET : bit (3) > + < 700_REPORTING_THRESHOLD : bit (3) > } + { 0 | 1 < 810_REPORTING_OFFSET : bit (3) > + < 810_REPORTING_THRESHOLD : bit (3) > } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-8 + { 0 | 1 < Priority and E-UTRAN Parameters Description : + < Priority and E-UTRAN Parameters Description struct >> } + { 0 | 1 < 3G CSG Description : < 3G CSG Description struct >> } + { 0 | 1 < E-UTRAN CSG Description : < E-UTRAN CSG Description struct >> } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-9 + { 0 | 1 < Enhanced Cell Reselection Parameters Description : + < Enhanced Cell Reselection Parameters IE >> } + { 0 | 1 < CSG Cells Reporting Description : + < CSG Cells Reporting Description struct >> } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-10 + { 0 | 1 < INIT_PWR_RED : bit (1) > } + < NC2_CSG_PCCN_permitted : bit (1) > } + { + null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-11 + { 0 | 1 < Extended EARFCNs Description: + < Extended EARFCNs Description struct >> } + { 0 | 1 < Extended EARFCNs Description for CSG Cells: + < Extended EARFCNs Description for CSG Cells struct >> } + } + } + } + } + } + } + } + < spare padding > ; + +``` + +``` + +< 3G Neighbour Cell Description struct > ::= + { 0 | 1 < Index_Start_3G : bit (7) } + { 0 | 1 < Absolute_Index_Start_EMR : bit (7) } + { 0 | 1 < UTRAN FDD Description : UTRAN FDD Description struct >> } + { 0 | 1 < UTRAN TDD Description : UTRAN TDD Description struct >> } ; + +< UTRAN FDD Description struct > ::= + { 0 | 1 < Bandwidth_FDD : bit (3) } + { 1 < Repeated UTRAN FDD Neighbour Cells : Repeated UTRAN FDD Neighbour Cells struct >> } ** 0 ; + +< Repeated UTRAN FDD Neighbour Cells struct > ::= + 0 < FDD-ARFCN : bit (14) > + -- The value '1' was used in an earlier version of the protocol and shall not be used. + < FDD_Indic0 : bit > + < NR_OF_FDD_CELLS : bit (5) > + < FDD_CELL_INFORMATION Field : bit(p(NR_OF_FDD_CELLS)) > ; -- p(x) defined in table 9.1.54.1 + +< UTRAN TDD Description struct > ::= + { 0 | 1 < Bandwidth_TDD : bit (3) } + { 1 < Repeated UMTS TDD Neighbour Cells : Repeated UMTS TDD Neighbour Cells struct >> } ** 0 ; + +< Repeated UTRAN TDD Neighbour Cells struct > ::= + 0 < TDD-ARFCN : bit (14) > + -- The value '1' was used in an earlier version of the protocol and shall not be used. + < TDD_Indic0 : bit > + < NR_OF_TDD_CELLS : bit (5) > + < TDD_CELL_INFORMATION Field : bit(q(NR_OF_TDD_CELLS)) > ; -- q(x) defined in table 9.1.54.1 + + ::= + < REPORT_TYPE : bit > + < SERVING_BAND_REPORTING : bit (2) > ; + +< 3G MEASUREMENT PARAMETERS Description struct > ::= + < Qsearch_I : bit (4) > + < Qsearch_C_Initial : bit (1) > + { 0 | 1 < FDD_Qoffset : bit (4) > + < FDD_REP_QUANT : bit (1) > + < FDD_MULTIRAT_REPORTING : bit (2) > + < FDD_Qmin : bit (3) > } + { 0 | 1 < TDD_Qoffset : bit (4) > + < TDD_MULTIRAT_REPORTING : bit (2) > } ; + +< GPRS Real Time Difference Description struct > ::= + { 0 | 1 { 0 | 1 < BA_Index_Start_RTD : bit (5) > } + < RTD : < RTD6 Struct >> + { 0 < RTD : < RTD6 Struct >> } **1 } + --default value=0 + -- '0' : increment by 1 the index of the BA (list) frequency + + { 0 | 1 { 0 | 1 < BA_Index_Start_RTD : bit (5) > } + < RTD : < RTD12 Struct >> + { 0 < RTD : < RTD12 Struct >> } **1 } ; + --default value=0 + -- '0' : increment by 1 the index of the BA (list) frequency + +< RTD6 Struct > ::= + { 0 < RTD : bit (6) > } ** 1; -- Repeat until '1' ; '1' means last RTD for this frequency + +< RTD12 Struct > ::= + { 0 < RTD : bit (12) > } ** 1; -- Repeat until '1' ; '1' means last RTD for this frequency + +< GPRS BSIC Description struct > ::= + { 0 | 1 < BA_Index_Start_BSIC : bit (5) > } + < BSIC : bit (6) > + < Number_Remaining_BSIC : bit (7) > + { < Frequency_Scrolling : bit > + < BSIC : bit (6) > } * (val(Number_Remaining_BSIC)); + -- default value=0 + -- 0 means same frequency + +< GPRS REPORT PRIORITY Description struct > ::= + < Number_Cells : bit (7) > + { REP_PRIORITY : bit } * (val(Number_Cells)) ; + +``` + +``` + +< GPRS MEASUREMENT PARAMETERS Description struct > ::= + < REPORT_TYPE : bit > + < REPORTING_RATE : bit > + < INVALID_BSIC_REPORTING : bit > + { 0 | 1 < MULTIBAND_REPORTING : bit (2) > } + { 0 | 1 < SERVING_BAND_REPORTING : bit (2) > } + < SCALE_ORD : bit(2) > + + { 0 | 1 < 900_REPORTING_OFFSET : bit (3) > + < 900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1800_REPORTING_OFFSET : bit (3) > + < 1800_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 400_REPORTING_OFFSET : bit (3) > + < 400_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1900_REPORTING_OFFSET : bit (3) > + < 1900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 850_REPORTING_OFFSET : bit (3) > + < 850_REPORTING_THRESHOLD : bit (3) > } ; + +< GPRS 3G MEASUREMENT PARAMETERS Description struct > ::= + < Qsearch_P : bit (4) > + { 1 ! < Ignore : bit = < no string >> } -- this bit shall be ignored by the receiver + -- for backward compatibility with earlier releases + { 0 | 1 < FDD_REP_QUANT : bit > + < FDD_MULTIRAT_REPORTING : bit (2) > } -- FDD Parameters + { 0 | 1 < FDD_REPORTING_OFFSET : bit (3) > + < FDD_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) > + < TDD_REPORTING_OFFSET : bit (3) > + < TDD_REPORTING_THRESHOLD : bit (3) > } ; -- TDD Parameters + +< NC Measurement Parameters struct > ::= + < NETWORK_CONTROL_ORDER : bit (2) > + { 0 | 1 < NC_NON_DRX_PERIOD : bit (3) > + < NC_REPORTING_PERIOD_I : bit (3) > + < NC_REPORTING_PERIOD_T : bit (3) > } ; + +< SI2q Extension Information > ::= + { 0 | 1 < CCN Support Description : < CCN Support Description struct >> } + < spare bit > ** ; + +< CCN Support Description struct > ::= + < Number_Cells : bit (7) > + { CCN_SUPPORTED : bit } * (val(Number_Cells)) ; + +< 3G Additional Measurement Parameters Description struct > ::= + < FDD_Qmin_Offset : bit (3) > -- FDD information + < FDD_RSCPmin : bit (4) > ; + +< 3G Additional Measurement Parameters Description 2 struct > ::= + { 0 | 1 < FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; -- FDD information + +< Priority and E-UTRAN Parameters Description struct > ::= + { 0 | 1 < Serving Cell Priority Parameters Description : + < Serving Cell Priority Parameters Description struct >> } + { 0 | 1 < 3G Priority Parameters Description : + < 3G Priority Parameters Description struct >> } + { 0 | 1 < E-UTRAN Parameters Description : + < E-UTRAN Parameters Description struct >> } ; + +``` + +``` + +< Serving Cell Priority Parameters Description struct > ::= + < GERAN_PRIORITY : bit(3) > + < THRESH_Priority_Search : bit(4) > + < THRESH_GSM_low : bit(4) > + < H_PRIO : bit(2) > + < T_Reselection : bit(2) >; + +< 3G Priority Parameters Description struct > ::= + < UTRAN_Start : bit > + < UTRAN_Stop : bit > + { 0 | 1 < DEFAULT_UTRAN_PRIORITY : bit(3) > + < DEFAULT_THRESH_UTRAN : bit(5) > + < DEFAULT_UTRAN_QRXLEVMIN : bit(5) > } + { 1 < Repeated UTRAN Priority Parameters : < Repeated UTRAN Priority Parameters struct >> } ** 0 ; + +< Repeated UTRAN Priority Parameters struct > ::= + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 + { 0 | 1 < UTRAN_PRIORITY : bit(3) > } + < THRESH_UTRAN_high : bit(5) > + { 0 | 1 < THRESH_UTRAN_low : bit(5) > } + { 0 | 1 < UTRAN_QRXLEVMIN : bit(5) > } ; + +< E-UTRAN Parameters Description struct > ::= + + < E-UTRAN_CCN_ACTIVE : bit > + < E-UTRAN_Start : bit > + < E-UTRAN_Stop : bit > + { 0 | 1 E-UTRAN Measurement Parameters Description : + < E-UTRAN Measurement Parameters Description struct >> } + { 0 | 1 GPRS E-UTRAN Measurement Parameters Description : + < GPRS E-UTRAN Measurement Parameters Description struct >> } + { 1 < Repeated E-UTRAN Neighbour Cells : < Repeated E-UTRAN Neighbour Cells struct >> } ** 0 + { 1 < Repeated E-UTRAN Not Allowed Cells : < Repeated E-UTRAN Not Allowed Cells struct >> } ** 0 + { 1 < Repeated E-UTRAN PCID to TA mapping : < Repeated E-UTRAN PCID to TA mapping struct >> } ** 0 ; + +< E-UTRAN Measurement Parameters Description struct > ::= + < Qsearch_C_E-UTRAN_Initial : bit(4) > + < E-UTRAN_REP_QUANT : bit > + < E-UTRAN_MULTIRAT_REPORTING : bit(2) > + { 0 { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD : bit(3) > + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } } -- FDD 6 bit reporting + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD : bit(3) > + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } } -- TDD 6 bit reporting + | 1 { 0 | 1 < E-UTRAN_FDD_MEASUREMENT_REPORT_OFFSET : bit(6) > + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } } -- FDD 3 bit reporting + { 0 | 1 < E-UTRAN_TDD_MEASUREMENT_REPORT_OFFSET : bit(6) > + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } } -- TDD 3 bit reporting + < REPORTING_GRANULARITY : bit(1) > } ; + +< GPRS E-UTRAN Measurement Parameters Description struct > ::= + < Qsearch_P_E-UTRAN : bit(4) > + < E-UTRAN_REP_QUANT : bit > + < E-UTRAN_MULTIRAT_REPORTING : bit(2) > + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD : bit(3) > + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD : bit(3) > + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } ; + +``` + +``` + +< Repeated E-UTRAN Neighbour Cells struct > ::= + { 1 < EARFCN : bit (16) > + { 0 | 1 < Measurement Bandwidth : bit (3) > } ** 0 + { 0 | 1 < E-UTRAN_PRIORITY : bit(3) > } + < THRESH_E-UTRAN_high : bit(5) > + { 0 | 1 < THRESH_E-UTRAN_low : bit(5) > } + { 0 | 1 < E-UTRAN_QRXLEVMIN : bit(5) > } ; + +< Repeated E-UTRAN Not Allowed Cells struct > ::= + < Not Allowed Cells : < PCID Group IE >> + { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 ; + +< Repeated E-UTRAN PCID to TA mapping struct > ::= + { 1 -- each repetition corresponds to a different TA + < PCID to TA mapping : < PCID Group IE >> -- group of PCIDs belonging to the same TA + } ** 0 + { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 ; + +< 3G CSG Description struct > ::= + { 1 < CSG_PSC_SPLIT : < PSC Group IE >> + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 } ** 0 + { 1 { 0 < CSG_FDD_UARFCN : bit (14) > | 1 < CSG_TDD_UARFCN : bit (14) > } } ** 0 ; + -- UTRAN CSG Dedicated Frequencies + +< E-UTRAN CSG Description struct > ::= + { 1 < CSG_PCI_SPLIT : < PCID Group IE >> + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 } ** 0 + { 1 < CSG_EARFCN : bit (16) > } ** 0 ; + -- E-UTRAN CSG Dedicated Frequencies + +< CSG Cells Reporting Description struct > ::= + { 0 | 1 < UTRAN CSG Cells Reporting Description : < UTRAN CSG Cells Reporting Description struct >> } + { 0 | 1 < E-UTRAN CSG Cells Reporting Description : < E-UTRAN CSG Cells Reporting Description struct >> } ; + +< UTRAN CSG Cells Reporting Description struct > ::= + { 0 | 1 < UTRAN_CSG_FDD_REPORTING_THRESHOLD : bit (3) > + < UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } + { 0 | 1 < UTRAN_CSG_TDD_REPORTING_THRESHOLD : bit (3) > } ; + +< E-UTRAN CSG Cells Reporting Description struct > ::= + { 0 | 1 < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD : bit (3) > + < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } + { 0 | 1 < E-UTRAN_CSG_TDD_REPORTING_THRESHOLD : bit (3) > + < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; + +< Extended EARFCNs Description struct > ::= + { 1 < EARFCN_extended : bit(18) > } ** 0 ; + +< Extended EARFCNs Description for CSG Cells struct > ::= + { 1 < CSG_EARFCN_extended : bit(18) > } ** 0 ; + +``` + +**Table 10.5.2.33b.2: SI2quater Rest Octets information element** + +**BA\_IND** (1 bit), BCCH allocation sequence number indication. +The BA\_IND is needed to allow the network to discriminate measurements results related to different GSM Neighbour Cell lists sent to the MS, as described in sub-clause 3.4.1.2.1. The value of this parameter is reflected in the ENHANCED MEASUREMENT REPORT message and in the MEASUREMENT REPORT message. + +**3G\_BA\_IND** (1 bit), 3G BCCH allocation sequence number indication. +The 3G\_BA\_IND is needed to indicate new sets of 3G Neighbour Cell information, E-UTRAN Measurement Parameters, 3G CSG and/or E-UTRAN CSG neighbour cell information or E-UTRAN Neighbour Cell information, as described in sub-clause 3.4.1.2.1. The value received is reflected in the MEASUREMENT REPORT and ENHANCED MEASUREMENT REPORT message. + +##### **MP\_CHANGE\_MARK (1 bit)** + +The **MP\_CHANGE\_MARK** field is changed each time MEASUREMENT INFORMATION or 3G MEASUREMENT INFORMATION, Serving Cell Priority Parameters or 3G Priority Parameters has been updated in any instance of the SI2quater messages. A new value indicates that the mobile station shall re-read the MEASUREMENT INFORMATION, 3G MEASUREMENT INFORMATION, Serving Cell Priority Parameters and 3G Priority Parameters from all the SI2quater messages, as described in sub-clause 3.4.1.2.1. The coding of this field is network dependent. + +##### **SI2quater\_INDEX (4 bit field)** + +The SI2quater\_INDEX field is used to distinguish individual SI2quater messages. The field can take the binary representation of the values 0 to n, where n is the index of the last SI2quater message. (SI2quater\_COUNT). + +##### **SI2quater\_COUNT (4 bit field)** + +This field is coded as the binary representation of the SI2quater\_INDEX for the last (highest indexed) individual SI2quater message. + +##### **3G Neighbour Cell Description:** + +The building of the 3G Neighbour Cell list and the ordering of indices within each Radio Access Technology is described in sub-clause 3.4.1.2.1.1, 'Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description'. + +###### **Index\_Start\_3G (7 bit)** + +This optional information element indicates the binary value of the first index to use to build this instance of the 3G Neighbour Cell list. When missing, the value 0 is assumed. See sub-clause 3.4.1.2.1.1. + +###### **Absolute\_Index\_Start\_EMR (7 bit)** + +This parameter indicates in binary the value to be added to the indexes of the 3G Neighbour Cell list for reporting 3G Cells with the ENHANCED MEASUREMENT REPORT message (see sub-clause 3.4.1.2.1.1). If different values are received for this parameter in different instances of this message, the instance with the highest index shall be used. If this parameter is absent in all instances of the message, the value "0" shall be used. + +##### **UTRAN FDD DESCRIPTION** + +For detailed element definitions see the Measurement Information message with the following exception for the FDD\_CELL\_INFORMATION field: + +##### **FDD\_CELL\_INFORMATION (p bit field)** + +If parameter *n* in table 9.1.54.1a. is equal to 31, this indicates that the corresponding UARFCN shall be included in the 3G Cell Reselection list (see sub-clause 3.4.1.2.1.7); no index shall be allocated in the 3G Neighbour Cell list. + +##### **UTRAN TDD DESCRIPTION** + +For detailed element definitions see the Measurement Information message with the following exception for the TDD\_CELL\_INFORMATION field: + +###### **TDD\_CELL\_INFORMATION (q bit field)** + +If parameter *m* in table 9.1.54.1b. is equal to 31, this indicates that the corresponding UARFCN shall be included in the 3G Cell Reselection list (see sub-clause 3.4.1.2.1.7); no index shall be allocated in the 3G Neighbour Cell list. + +##### **UTRAN FDD DESCRIPTION** + +For detailed element definitions see the Measurement Information message. + +##### **UTRAN TDD DESCRIPTION** + +For detailed element definitions see the Measurement Information message. + +##### **MEASUREMENT PARAMETERS Description** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +If the *MEASUREMENT PARAMETERS Description* is included in more than one instance of the SI2quater message, the *MEASUREMENT PARAMETERS Description* of the instance with the highest SI2quater\_INDEX shall be used. + +##### **3G MEASUREMENT PARAMETERS Description** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +If the 3G *MEASUREMENT PARAMETERS Description* is included in more than one instance of the SI2quater message, the 3G *MEASUREMENT PARAMETERS Description* of the instance with the highest SI2quater\_INDEX shall be used. + +##### ***GPRS REPORT PRIORITY Description*** + +###### **REP\_PRIORITY bit:** + +- 0 Normal reporting priority +- 1 High reporting priority + +This information is used for GPRS Enhanced (NC) Reporting when the cell has no PBCCH allocated, see 3GPP TS 44.060 sub-clause 5.6.3.5 ("Report Priority Description"). + +If the *GPRS REPORT PRIORITY Description* is included in more than one instance of the SI2quater message, the *GPRS REPORT PRIORITY Description* of the instance with the highest SI2quater\_INDEX shall be used. + +The use of these bits is similar to the PRIORITY description, see sub-clause 3.4.1.2.1.5 ("Report Priority Description"). + +##### ***GPRS BSIC Description*** + +This information is used for GPRS Enhanced (NC) Measurement reporting when the cell has no PBCCH allocated, see 3GPP TS 44.060 sub-clause 5.6.3.2 ("Deriving the GSM Neighbour Cell list from the BSICs and frequency list"). The use of this information is similar to the BSIC Description, see sub-clause 3.4.1.2.1.2 ("Deriving the GSM Neighbour Cell list from the BSICs and the BA (list)"). + +##### ***GPRS Real Time Difference Description*** + +This information is used for GPRS neighbour cell measurement when the cell has no PBCCH allocated, see 3GPP TS 44.060 sub-clause 5.6.3.4 ("GPRS Real Time Differences"). The use of this information is similar to the Real Time Difference Description, see sub-clause 3.4.1.2.1.4 ("Real Time Differences"). + +##### ***GPRS MEASUREMENT PARAMETERS Description*** + +This information is used for GPRS neighbour cell measurement when the cell has no PBCCH allocated, see 3GPP TS 44.060 sub-clause 5.6.3.6 ("GPRS Measurement Parameters and GPRS 3G Measurement Parameters"). If the *GPRS MEASUREMENT PARAMETERS Description* is included in more than one instance of the SI2quater message, the *GPRS MEASUREMENT PARAMETERS Description* of the instance with the highest SI2quater\_INDEX shall be used. + +The fields of this Description are defined in 3GPP TS 45.008. + +##### ***GPRS 3G MEASUREMENT PARAMETERS Description*** + +This information is used for GPRS 3G neighbour cell measurement when the cell has no PBCCH allocated, see 3GPP TS 44.060 sub-clause 5.6.3.6 ("GPRS Measurement Parameters and GPRS 3G Measurement Parameters"). If the *GPRS 3G MEASUREMENT PARAMETERS Description* is included in more than one instance of the SI2quater message, the *GPRS 3G MEASUREMENT PARAMETERS Description* of the instance with the highest SI2quater\_INDEX shall be used. + +The fields of this Description are defined in 3GPP TS 45.008. + +##### ***NC Measurement Parameters struct*** + +Information in this structure is used when the cell has no PBCCH allocated, for (NC) measurement reporting. See 3GPP TS 44.060 sub-clause 5.6.1 ("Network Control (NC) measurement reporting"). + +If the *NC Measurement Parameters struct* is included in more than one instance of the SI2quater message, the *NC Measurement Parameters struct* of the instance with the highest SI2quater\_INDEX shall be used. + +Coding of the fields is defined in 3GPP TS 44.060, sub-clause 11.2.23 ("PACKET SYSTEM INFORMATION TYPE5"). + +##### ***CCN Support Description*** + +###### **CCN\_SUPPORTED bit:** + +- 0** CCN is enabled towards the corresponding cell +- 1** CCN is disabled towards the corresponding cell + +This information is used for determining whether the mobile station shall enter CCN mode when re-selecting a cell and CCN is enabled, see 3GPP TS 44.060. + +If the *CCN Support Description* is included in more than one instance of the SI2quater message, the *CCN Support Description* of the instance with the highest SI2quater\_INDEX shall be used. + +The use of these bits is described in sub-clause 3.4.1.2.1.8("CCN Support description"). + +##### ***3G Additional Measurement Parameters Description*** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +If the *3G Additional MeasurementParameters Description* is included in more than one instance of the SI2quater message, the *3G Additional MeasurementParameters Description* of the instance with the highest SI2quater\_INDEX shall be used. + +###### **3G\_CCN\_ACTIVE (1 bit field)** + +This field indicates whether CCN is enabled towards 3G neighbouring cells. It is coded as follows: + +- 0** CCN towards 3G cells is disabled in the cell. +- 1** CCN towards 3G cells is enabled in the cell. + +##### ***3G Additional Measurement Parameters Description 2*** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +If the *3G Additional Measurement Parameters Description 2* is included in more than one instance of the SI2quater message, the *3G Additional Measurement Parameters Description 2* of the instance with the highest SI2quater\_INDEX shall be used. + +###### **700\_REPORTING\_OFFSET (3 bit field)** + +##### **700\_REPORTING\_THRESHOLD (3 bit field)** + +These fields are used for measurements as defined in 3GPP TS 45.008. + +If these fields are included in more than one instance of the SI2quater message, those of the instance with the highest SI2quater\_INDEX shall be used. + +###### **810\_REPORTING\_OFFSET (3 bit field)** + +###### **810\_REPORTING\_THRESHOLD (3 bit field)** + +These fields are used for measurements as defined in 3GPP TS 45.008. + +If these fields are included in more than one instance of the SI2quater message, those of the instance with the highest SI2quater\_INDEX shall be used. + +##### **Serving Cell Priority Parameters** + +###### **GERAN\_PRIORITY (3 bit field)** + +###### **THRESH\_Priority\_Search (4 bit field)** + +###### **THRESH\_GSM\_low (4 bit field)** + +##### **H\_PRIO (2 bit field)** + +##### **T\_Reselection (2 bit field)** + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. Any parameter present overwrites any old data held by the mobile station for these parameters. + +##### 3G Priority Parameters Description + +**UTRAN\_Start** (1 bit field) + +**UTRAN\_Stop** (1 bit field) + +These fields are defined in sub-clause 9.1.54. + +**DEFAULT\_UTRAN\_PRIORITY** (3 bit field) + +**DEFAULT\_THRESH\_UTRAN** (5 bit field) + +**DEFAULT\_UTRAN\_QRXLEVMIN** (5 bit field) + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. Any UTRAN frequency included in the 3G Cell Reselection list which is not explicitly listed in the Repeated UTRAN Priority Parameters structure shall be assigned these default parameter values. In addition, any UTRAN frequency included in the 3G Frequency list which is explicitly listed in the Repeated UTRAN Priority Parameters structure but for which no UTRAN\_QRXLEVMIN is explicitly signalled shall be assigned the value DEFAULT\_UTRAN\_QRXLEVMIN. The value of DEFAULT\_THRESH\_UTRAN shall apply to both THRESH\_UTRAN\_high and THRESH\_UTRAN\_low. The DEFAULT\_UTRAN\_PRIORITY field is encoded as the UTRAN\_PRIORITY field; the DEFAULT\_THRESH\_UTRAN field is encoded as the THRESH\_UTRAN\_high field; the DEFAULT\_UTRAN\_QRXLEVMIN field is encoded as the UTRAN\_QRXLEVMIN field. + +Any parameter present overwrites any old data held by the mobile station for these parameters. + +###### Repeated UTRAN Priority Parameters + +**UTRAN\_FREQUENCY\_INDEX** (5 bit field) + +This field is an index into the 3G Frequency list (see sub-clause 3.4.1.2.1.7c).. The following priority parameters apply to each UTRAN frequency indexed within this structure. + +**UTRAN\_PRIORITY** (3 bit field) + +**THRESH\_UTRAN\_high** (5 bit field) + +**THRESH\_UTRAN\_low** (5 bit field) + +If THRESH\_UTRAN\_low is not present, then THRESH\_UTRAN\_low shall take on the same value as THRESH\_UTRAN\_high. + +**UTRAN\_QRXLEVMIN** (5 bit field) + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. These values apply to each of the frequencies indexed within this structure. Any parameter present overwrites any old data held by the mobile station for these parameters. + +##### E-UTRAN Parameters Description + +If E-UTRAN cells or frequencies are included in the neighbour cell list, this information element shall be included in the message. + +**E-UTRAN\_CCN\_ACTIVE** (1 bit field) + +This field indicates whether CCN is enabled towards E-UTRAN neighbouring cells. It is coded as follows: + +0 The broadcast E-UTRAN\_CCN\_ACTIVE parameter shall apply if available. Otherwise, CCN towards E-UTRAN cells is disabled in the cell. + +1 CCN towards E-UTRAN cells is enabled in the cell. + +**E-UTRAN\_Start** (1 bit field) + +**E-UTRAN\_Stop** (1 bit field) + +These fields are defined in sub-clause 9.1.54. + +##### E-UTRAN Measurement Parameters Description + +If the *E-UTRAN MeasurementParameters Description* is included in more than one instance of the SI2quater message, the *E-UTRAN MeasurementParameters Description* of the instance with the highest SI2quater\_INDEX shall be used. + +**Qsearch\_C\_E-UTRAN\_Initial** (4 bit field) + +**E-UTRAN\_MULTIRAT\_REPORTING** (2 bit field) + +**E-UTRAN\_REP\_QUANT** (1 bit field) + +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD** (3 bit field) + +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +**E-UTRAN\_FDD\_MEASUREMENT\_REPORT\_OFFSET** (6 bit field) + +**E-UTRAN\_FDD\_REPORTING\_OFFSET** (3 bit field) + +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD** (3 bit field) + +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +**E-UTRAN\_TDD\_MEASUREMENT\_REPORT\_OFFSET** (6 bit field) + +**E-UTRAN\_TDD\_REPORTING\_OFFSET** (3 bit field) + +**REPORTING\_GRANULARITY** (1 bit field) + +These fields control the measurement and reporting of E-UTRAN cells in dedicated mode and dual transfer mode, as defined in 3GPP TS 45.008. + +If both TDD and FDD frequencies are provided in the Repeated E-UTRAN Neighbour Cells IE and the E-UTRAN reporting thresholds are present for only one mode (i.e. TDD or FDD), then the parameter values for both modes shall be interpreted as having the same values. + +##### GPRS E-UTRAN Measurement Parameters Description + +If the *GPRS E-UTRAN Measurement Parameters Description* is included in more than one instance of the SI2quater message, the *GPRS E-UTRAN Measurement Parameters Description* of the instance with the highest SI2quater\_INDEX shall be used. + +**Qsearch\_P\_E-UTRAN** (4 bit field) + +**E-UTRAN\_MULTIRAT\_REPORTING** (2 bit field) + +**E-UTRAN\_REP\_QUANT** (1 bit field) + +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD** (3 bit field) + +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD** (3 bit field) + +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +These fields control the GPRS neighbour cell measurement and (NC) Measurement reporting of E-UTRAN cells when the MS is not performing autonomous cell reselection, as defined in 3GPP TS 45.008. + +If both TDD and FDD frequencies are provided in the Repeated E-UTRAN Neighbour Cells IE and the E-UTRAN reporting thresholds are present for only one mode (i.e. TDD or FDD), then the parameter values for both modes shall be interpreted as having the same values. + +###### **Repeated E-UTRAN Neighbour Cells** + +If E-UTRAN cells or frequencies are included in the neighbour cell list, this information element shall be included in the message. + +###### **EARFCN (16 bit field)** + +NOTE: in the case *Extended EARFCNs* is in use in the cell, the network may additionally broadcast EARFCNs > 65535 within the *Extended EARFCNs Description* IE (see below). Broadcast of *Extended EARFCNs Description* IE is indicated by the reserved EARFCN value 65535 in any position within the *Repeated E-UTRAN Neighbour Cells* IE. + +When applicable (see sub-clause 3.4.1.2.1.1a), a mobile station supporting extended EARFCNs shall manage EARFCN value 65535 as follows: assuming that the EARFCN value 65535 is the $n^{\text{th}}$ EARFCN with such value within the *Repeated E-UTRAN Neighbour Cells* IE ( $n = 1, 2, \dots$ ), the mobile station shall replace within the E-UTRAN NCL this EARFCN value 65535 by the $n^{\text{th}}$ EARFCN value within the *Extended EARFCNs Description* IE. + +##### **Measurement Bandwidth (3 bit field)** + +These fields are defined in sub-clause 9.1.54. + +##### **E-UTRAN\_PRIORITY (3 bit field)** + +###### **THRESH\_E-UTRAN\_high (5 bit field)** + +###### **THRESH\_E-UTRAN\_low (5 bit field)** + +If THRESH\_E-UTRAN\_low is not present, then THRESH\_E-UTRAN\_low shall take on the same value as THRESH\_E-UTRAN\_high. + +###### **E-UTRAN\_QRXLEVMIN (5 bit field)** + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. These values apply to each of the EARFCN values listed within this structure. + +##### **Repeated E-UTRAN Not Allowed Cells struct** + +This structure identifies Not Allowed Cells with zero or more corresponding E-UTRAN frequency indices. If no E-UTRAN\_FREQUENCY\_INDEX is present, the **Not Allowed Cells** IE is applicable to all E-UTRAN frequencies specified in the Repeated E-UTRAN Neighbour Cells struct(s). + +##### **E-UTRAN\_FREQUENCY\_INDEX (3 bit field)** + +This field is defined in sub-clause 9.1.54. + +###### **Not Allowed Cells** + +This information element is described in sub-clause 9.1.54. + +###### **PCID to TA mapping** + +This information element identifies, on the frequency or frequencies that this information element is associated with, one or more E-UTRAN cells by means of their physical layer cell identities (see 3GPP TS 36.211) that belong to the same Tracking Area. If no PCIDs or groups of PCIDs are indicated within this structure, then all PCIDs belong to the same Tracking Area. + +This information element is defined as the PCID Group IE described in 3GPP TS 44.060. + +##### **3G CSG Description** + +The fields of this description are used for inter-RAT cell reselection to UTRAN CSG cells as defined in 3GPP TS 45.008. + +###### **UTRAN\_FREQUENCY\_INDEX (5 bit field)** + +Each instance of this field describes a UTRAN frequency in the 3G Frequency list where the CSG PSC SPLIT is valid. If the *CSG\_PSC\_SPLIT* IE is present but there are no instances of this field present in the message, then the CSG PSC SPLIT shall apply to all UTRAN frequencies in the 3G Cell Reselection list. This field is an index into the 3G Frequency list (see sub-clause 3.4.1.2.1.7c). + +###### **CSG\_FDD\_UARFCN (14 bit field)** + +Each CSG\_FDD\_UARFCN describes a UTRAN FDD frequency dedicated to CSG cells. The field is formatted as a UARFCN as defined in 3GPP TS 25.101. + +###### **CSG\_TDD\_UARFCN (14 bit field)** + +Each CSG\_TDD\_UARFCN describes a UTRAN TDD frequency dedicated to CSG cells. The field is formatted as a UARFCN as defined in 3GPP TS 25.102. + +##### **E-UTRAN CSG Description** + +The fields of this description are used for inter-RAT cell reselection to E-UTRAN CSG cells as defined in 3GPP TS 45.008. + +##### **E-UTRAN\_FREQUENCY\_INDEX (3 bit field)** + +Each instance of this field describes an E-UTRAN frequency in the E-UTRAN Neighbour Cell list where the CSG PCI SPLIT is valid. If the *CSG\_PCI\_SPLIT* field is present but there are no instances of this field present in the message, then the CSG PCI SPLIT shall apply to all E-UTRAN frequencies in the E-UTRAN Neighbour Cell list. This field is described in sub-clause 9.1.55. + +###### **CSG\_EARFCN (16 bit field)** + +Each CSG\_EARFCN describes an E-UTRAN frequency dedicated to CSG cells. The field is formatted as an E-UTRA Absolute Radio Frequency Channel Number as defined in 3GPP TS 36.104. + +NOTE: in the case Extended EARFCNs is in use in the cell, the network may additionally broadcast CSG EARFCNs > 65535 within the *Extended EARFCNs Description for CSG Cells* IE (see below). + +##### **CSG\_PCI\_SPLIT** + +This information element is described in sub-clause 9.1.54. + +###### **CSG\_PSC\_SPLIT** + +This information element identifies one or more primary scrambling code values for UTRAN FDD cells (see 3GPP TS 25.213) or cell parameter values for UTRAN TDD cells (see 3GPP TS 25.223) as being reserved for CSG cells. The range of reserved primary scrambling codes or cell parameters applies to all UTRAN frequencies specified in the list of frequencies. + +This information element is defined as the PSC Group IE described in 3GPP TS 44.060. + +##### **Enhanced Cell Reselection Parameters Description** + +This information element contains parameters for enhanced cell reselection procedures towards E-UTRAN cells, see 3GPP TS 45.008. + +This information element is defined as the Enhanced Cell Reselection Parameters IE described in 3GPP TS 44.060. + +##### **CSG Cells Reporting Description** + +This information element signals the parameters for measurement and reporting of UTRAN CSG cells in dedicated mode, dual transfer mode or packet transfer mode and/or the parameters for measurement and reporting of E-UTRAN CSG cells in packet transfer mode. Any parameter present overwrites any old data held by the mobile station for this parameter. + +##### **UTRAN CSG Cells Reporting Description** + +**UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD (3 bit field)** + +**UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD\_2 (6 bit field)** + +**UTRAN\_CSG\_TDD\_REPORTING\_THRESHOLD (3 bit field)** + +These fields are defined in sub-clause 9.1.54. + +##### ***E-UTRAN CSG Cells Reporting Description*** + +**E-UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD** (3 bit field)**E-UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD\_2** (6 bit field)**E-UTRAN\_CSG\_TDD\_REPORTING\_THRESHOLD** (3 bit field)**E-UTRAN\_CSG\_TDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +These fields are used to control the reporting for CSG cells as specified in 3GPP TS 45.008. + +###### **INIT\_PWR\_RED (1 bit field)** + +The INIT\_PWR\_RED field indicates whether or not a mobile station that supports the initial power reduction feature shall apply it as described in 3GPP TS 45.008. If this field is not present, no power reduction shall apply. + +The following coding shall be used: + +- | | | +|---|-------------------------------------------------------------------------------------------------------| +| 0 | RACH power reduction, INIT_PWR_RED=10 dB | +| 1 | RACH power reduction, INIT_PWR_RED=10 dB. In case of emergency calls, no power reduction shall apply. | + +###### **NC2\_CSG\_PCCN\_permitted (1 bit field)** + +This field indicates whether a mobile station is permitted to send a PACKET CELL CHANGE NOTIFICATION message while in NC2 mode to report a detected CSG cell or hybrid cell (see 3GPP TS 44.060) + +##### **Extended EARFCNs Description struct** + +This information element contains one or more EARFCNs with value > 65535. + +###### **EARFCN\_Extended** (18 bits field) + +See table 9.1.54.1 for the definition of the *EARFCN\_extended* field. + +##### **Extended EARFCNs Description for CSG Cells struct** + +This information element contains one or more E-UTRAN CSG dedicated frequencies with EARFCN value > 65535. The fields of this description are used for inter-RAT cell reselection to E-UTRAN CSG cells as defined in 3GPP TS 45.008. + +###### **CSG\_EARFCN\_Extended** (18 bits field) + +Each CSG\_EARFCN\_Extended describes an E-UTRA frequency dedicated to CSG cells. This field is formatted as an E-UTRA Absolute Radio Frequency Channel Number as defined in 3GPP TS 36.104. + +#### **10.5.2.33c SI 2n Rest Octets** + +The *SI 2n Rest Octets* information element contains parameters affecting cell reselection for neighbouring cells. + +The *SI 2n Rest Octets* information element is a type 5 information element with 20 octet length. + +Table 10.5.2.33c.1: SI2n Rest Octets information element + +``` + +< SI2n Rest Octets > ::= + + < BA_IND : bit (1) > + < SI2n_CHANGE_MARK : bit (2) > + < SI2n_INDEX : bit (4) > + < SI2n_COUNT : bit (4) > + < GSM Neighbour Cell Selection parameters : { 1 < GSM Neighbour Cell Selection params struct > } ** 0 > + < spare padding > ; + +< GSM Neighbour Cell Selection params struct > ::= + < NCELL_LIST_INDEX : bit (6) > + { 0 | 1 < BSIC : bit (6) > } + { 0 | 1 + < CELL_BAR_ACCESS : bit (1) > + < SAME_LA_AS_SERVING_CELL : bit (1) > + + { 0 | 1 < RXLEV_ACCESS_MIN : bit (6) > + < MS_TXPWR_MAX_CCH : bit (5) > } + + { 0 | 1 < CBQ : bit (1) > + < CELL_RESELECT_OFFSET : bit (6) > + < TEMPORARY_OFFSET : bit (3) > + < PENALTY_TIME : bit (5) > } + + { 0 | 1 < POWER_OFFSET : bit (2) > } + { 0 | 1 < GPRS Support Indicator : < GPRS Support Indicator struct > > } +} ; + + ::= + { 0 -- GPRS not supported in the cell + | 1 -- GPRS supported in the cell + < SAME_RA_AS_SERVING_CELL : bit (1) > + < SI13_POSITION : bit (1) > + } ; + +``` + +Table 10.5.2.33c.2: SI2n Rest Octets information element + +**BA\_IND** (1 bit), BCCH allocation sequence number indication. + +The BA\_IND establishes the connection between the parameters provided by this message and the GSM Neighbour Cell list the parameters are referring to. + +**SI2n\_CHANGE\_MARK** (2 bit field), SI2n Rest Octet Change Mark + +This parameter is used to indicate to the MS a change of information in the SI2n Rest Octets, as described in sub-clause 3.4.1.2.1.10, 'GSM Neighbour Cell Selection parameters'. + +**SI2n\_INDEX** (4 bit field) + +The SI2n\_INDEX field is used to distinguish individual SI2n messages. The field can take the binary representation of the values 0 to n, where n is the index of the last SI2n message. (SI2n\_COUNT). + +**SI2n\_COUNT** (4 bit field) + +This field is coded as the binary representation of the SI2n\_INDEX for the last (highest indexed) individual SI2n message. + +##### GSM Neighbour Cell Selection params struct + +###### **General rules for handling neighbour cell parameter default values** + +If the first neighbour cell defined in SI2n with SI2n\_INDEX = 0 does not include all the parameter values, the following default values shall be used: + +| | | +|------------------------------------------------------------------|---------------------------------------------------------------------------| +| RXLEV_ACCESS_MIN : | Serving cell RXLEV_ACCESS_MIN | +| MS_TXPWR_MAX_CCH : | Serving cell MS_TXPWR_MAX_CCH | +| CBQ : | 0 | +| CELL_RESELECT_OFFSET,
TEMPORARY_OFFSET, and
PENALTY_TIME : | C2=C1, see 3GPP TS 45.008 | +| POWER_OFFSET | 0 dB | +| CELL_BAR_ACCESS : | Serving cell CELL_BAR_ACCESS | +| SAME_LA_AS_SERVING_CELL : | 1 (The cell is in the same Location Area as the serving cell) | +| GPRS Support Indicator (struct not present) : | | +| SAME_RA_AS_SERVING_CELL : | 1 (The cell is in the same Routeing Area as the serving cell) | +| SI13_POSITION : | As in the serving cell (not valid, if serving cell does not support GPRS) | + +The following neighbour cells defined in the set of SI2n messages use the parameter values of the previous neighbour cell in the set of SI2n messages as their default values. This principle also applies when going from SI2n instance i over to SI2n instance i+1. + +##### **NCELL\_LIST\_INDEX** (6 bit field) + +This field indicates the index to the GSM Neighbour Cell list to identify the neighbouring cell to which the parameters are given.. + +##### **BSIC** (6 bit field) + +This optional field is needed to identify the neighbour cell in case the GSM Neighbour Cell list is only a frequency list, see 3GPP TS 44.060 sub-clause 5.6.3.2 + +##### **SAME\_LA\_AS\_SERVING\_CELL** (1 bit field) + +This field indicates whether the cell is in the same location area as the serving cell. + +| | | +|---|------------------------------------------------------------| +| 0 | the cell is in different location area as the serving cell | +| 1 | the cell is in the same location area as the serving cell | + +###### **SAME\_RA\_AS\_SERVING\_CELL** (1 bit field) + +This field indicates whether the cell is in the same routeing area as the serving cell + +| | | +|---|------------------------------------------------------------| +| 0 | the cell is in different routeing area as the serving cell | +| 1 | the cell is in the same routeing area as the serving cell | + +For the description of the rest of the parameters in the GSM Neighbour Cell Selection params struct, see 3GPP TS 45.008. + +#### **10.5.2.34 SI 3 Rest Octets** + +The *SI 3 Rest Octets* information element is coded according to the syntax specified below and described in tables 10.5.2.34.1, 10.5.2.34.2 and 10.5.2.35.1 (see sub-clause 10.5.2.35). + +The *SI 3 Rest Octets* information element is a type 5 information element with 4 octets length. + +**Table 10.5.2.34.1: SI 3 Rest Octets information element** + +``` + + ::= + + + + + + { L | H } + <3G Early Classmark Sending Restriction> + { L | H < SI2quater Indicator : < SI2quater Indicator struct > > } + -- Conditional + + ; + ::= L | H ; + ::= + + + + ; + ::= L | H ; + ::= L | H; + ::= L | H; +::= L | H ; + ::= + < RA COLOUR : bit (3) > + < SI13 POSITION : bit >; +<3G Early Classmark Sending Restriction>::= L | H; +< SI2quater Indicator struct > ::= < SI2quater_POSITION : bit > ; + ::= ; + ::= L | H < SI21_POSITION : bit > ; + +``` + +**Table 10.5.2.34.2: SI 3 Rest Octets information element details** + +**CBQ, CELL\_BAR\_QUALIFY** (1 bit field) + CELL\_BAR\_QUALIFY is used by the network to control mobile station cell selection and reselection. The use and coding of this parameter is defined in 3GPP TS 45.008. + +**CELL\_RESELECT\_OFFSET** (6 bit field) + CELL\_RESELECT\_OFFSET is coded as the binary representation of the "CELL\_RESELECT\_OFFSET" in 3GPP TS 45.008. It is a value used by the mobile station to apply a positive or negative offset to the value of C2 as defined in 3GPP TS 23.022 and 3GPP TS 45.008. + +**TEMPORARY\_OFFSET** (3 bit field) + The TEMPORARY\_OFFSET field is coded as the binary representation of the "TEMPORARY\_OFFSET" in 3GPP TS 45.008. It is used by the mobile station as part of its calculation of C2 for the cell reselection process as described in 3GPP TS 45.008. It is used to apply a negative offset to C2 for the duration of PENALTY\_TIME. + +**PENALTY\_TIME** (5 bit field) + The PENALTY\_TIME is coded as the binary representation of the "PENALTY\_TIME" in 3GPP TS 45.008. It defines the length of time for which TEMPORARY\_OFFSET is active. The usage of PENALTY\_TIME is described in 3GPP TS 23.022 and 3GPP TS 45.008. + +##### **Power Offset (2 bit field)** + +Power Offset is used only by DCS 1800 Class 3 MSs to add a power offset to the value of MS\_TXPWR\_MAX\_CCH used for its random access attempts. It is also used by the MS in its calculation of C1 and C2 parameters. Its use is defined in GSM 45.008. + +If this parameter is transmitted on a BCCH carrier within the DCS 1800 band, its meaning shall be described below: + +| Value | Meaning | +|-------|-------------------| +| 00 | 0 dB power offset | +| 01 | 2 dB power offset | +| 10 | 4 dB power offset | +| 11 | 6 dB power offset | + +If this parameter is transmitted on a BCCH carrier outside the DCS 1800 band, then all bit positions shall be treated as spare. + +##### **System Information 2ter Indicator (1 bit field)** + +| | | +|---|-------------------------------------------------------| +| L | SYSTEM INFORMATION TYPE 2ter message is not available | +| H | SYSTEM INFORMATION TYPE 2ter message is available | + +##### **Early Classmark Sending Control (1 bit field)** + +| | | +|---|--------------------------------------| +| L | Early Classmark Sending is forbidden | +| H | Early Classmark Sending is allowed | + +##### **WHERE (3 bit field)** + +If the **WHERE** field is not contained in the information element, this indicates that BCCH scheduling information is not sent in SYSTEM INFORMATION TYPE 9 on the BCCH. + +If the **WHERE** field is contained in the information element, this indicates that BCCH scheduling information is sent in SYSTEM INFORMATION TYPE 9 on the BCCH and that SYSTEM INFORMATION TYPE 9 messages are sent in the blocks of the BCCH norm for which $((FN \text{ DIV } 51) \bmod (8) = 4 \text{ AND } (((FN \text{ DIV } 51) \text{ DIV } 8) \bmod (n+1)) = 0)$ , where $n$ is the value encoded in binary in **WHERE**. + +##### **GPRS Indicator** + +The **GPRS Indicator** contains the RA COLOUR field and the SI13\_POSITION field. If the GPRS Indicator is contained in the information element, it indicates that GPRS is supported in the cell. + +##### **RA COLOUR (3 bit field)** + +If the mobile station receives different values of the RA COLOUR field in two cells belonging to the same location area or there are two cells belonging to different location areas, the mobile station shall interpret the cell re-selection information as if the two cells belong to different routeing areas. Otherwise, the mobile station shall interpret the cell re-selection information as if the two cells belong to the same routeing area. + +##### **SI13\_POSITION (1 bit field)** + +The SI13\_POSITION field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13 message is sent on BCCH, see 3GPP TS 45.002: + +| | | +|---|----------------------------------------------------------| +| 0 | SYSTEM INFORMATION TYPE 13 message is sent on BCCH Norm; | +| 1 | SYSTEM INFORMATION TYPE 13 message is sent on BCCH Ext. | + +##### **3G Early Classmark Sending Restriction (1 bit field)** + +| | | +|---|--------------------------------------------------------------------------------------------------------------------------------------------| +| L | Neither UTRAN, CDMA2000 nor GERAN IU MODE CLASSMARK CHANGE message shall be sent with the Early classmark sending | +| H | The sending of UTRAN, CDMA2000 and GERAN IU MODE CLASSMARK CHANGE messages are controlled by the Early Classmark Sending Control parameter | + +**SI2quater Indicator struct** + +The presence of this field indicates that the SI2quater message is broadcast. + +**SI2quater\_POSITION (1 bit field)** + +This field indicates where the SYSTEM INFORMATION TYPE 2 quater message is sent: + +- | | | +|---|---------------------------------------------------------------| +| 0 | SYSTEM INFORMATION TYPE 2 quater message is sent on BCCH Norm | +| 1 | SYSTEM INFORMATION TYPE 2 quater message is sent on BCCH Ext. | + +**Iu Indicator** + +The Iu Indicator field contains the SI13alt POSITION field. If *Iu mode* is not supported in the cell, the Iu Indicator is not sent within this cell. Iu Indicator is included if and only if GPRS is not supported and *Iu mode* is supported in the cell. If both GPRS and *Iu mode* are supported in the cell then Iu Indicator is not sent, see 3GPP TS 44.118. + +**SI13alt POSITION (1 bit field)** + +The SI13alt POSITION field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13alt message is sent on BCCH: + +- | | | +|---|-------------------------------------------------------------| +| 0 | SYSTEM INFORMATION TYPE 13alt message is sent on BCCH Norm; | +| 1 | SYSTEM INFORMATION TYPE 13alt message is sent on BCCH Ext. | + +**SYSTEM INFORMATION 21 Indicator** + +This field is only present if 'WHERE' information is not contained in SI 3 Rest Octets + +- | | | +|---|-----------------------------------------------------| +| L | SYSTEM INFORMATION TYPE 21 message is not available | +| H | SYSTEM INFORMATION TYPE 21 message is available | + +**SI21\_POSITION (1 bit field)** + +- | | | +|---|---------------------------------------------------------| +| 0 | SYSTEM INFORMATION TYPE 21 message is sent on BCCH Norm | +| 1 | SYSTEM INFORMATION TYPE 21 message is sent on BCCH Ext. | + +**10.5.2.35 SI 4 Rest Octets** + +The *SI 4 Rest Octets* information element includes parameters which are used by the mobile station for cell selection and reselection purposes. It may also include the POWER OFFSET parameter used by DCS 1800 Class 3 MS. + +Its content is described in table 10.5.2.35.1. + +NOTE: In the future evolution of this standard the values 64h and 72h shall not be used as values of the first octet when this information element is used in the SYSTEM INFORMATION TYPE 4 message. This will prevent mobile stations misinterpreting this information as the CBCH IEIs . + +The *SI 4 Rest Octets* information element is a type 5 information element with 0 to 10 octets length. + +**Table 10.5.2.35.1: SI 4 Rest Octets information element content** + +``` + + ::= +{ + + { + L + | H + + } // ; + -- truncation according to sub-clause 8.9 is allowed, bits 'L' assumed +} + + ::= +{ + + + {L | H } +} // ; +-- truncation according to sub-clause 8.9 is allowed, bits 'L' assumed + + ::= +{L | H } +{L | H } +{L | H } +{L | H < CBQ3 : bit (2) > +{0 | 1 < SI13alt Position : bit >}} ; + + : := L | H ; + + ::= | ; + + ::= | ; + + ::= L | H ; + + ::= + + + +< PENALTY_TIME : bit (5)> ; + + ::= L | H ; + + ::= +< RA COLOUR : bit (3) > +< SI13 POSITION : bit > ; + + ::= + + +{0 | 1 +} ; + + ::= + +{0 | 1 } ; + + : := +{0 +|1 } ; + +``` + +If "ACS " in the System information type 4 message is set to "1" then the SI 7 and SI 8 rest octets consists of "SI4 Rest Octets\_O" and "SI4 Rest Octets\_S", otherwise of only "SI4 Rest Octets\_S". + +**Table 10.5.2.35.2: SI 4 Rest Octets information element details****CBQ, CELL\_BAR\_QUALIFY (1 bit field)** + +CELL\_BAR\_QUALIFY is used by the network to control mobile station cell selection and reselection. The use and coding of this parameter is defined in 3GPP TS 45.008. + +**CELL\_RESELECT\_OFFSET (6 bit field)** + +CELL\_RESELECT\_OFFSET is coded as the binary representation of the "CELL\_RESELECT\_OFFSET" in 3GPP TS 45.008. It is a value used by the mobile station to apply a positive or negative offset to the value of C2 as defined in 3GPP TS 23.022 and 3GPP TS 45.008. + +**TEMPORARY\_OFFSET (3 bit field)** + +The TEMPORARY\_OFFSET field is coded as the binary representation of the "TEMPORARY\_OFFSET" in 3GPP TS 45.008. It is used by the mobile station as part of its calculation of C2 for the cell reselection process as described in 3GPP TS 45.008. It is used to apply a negative offset to C2 for the duration of PENALTY\_TIME. + +**PENALTY\_TIME (5 bit field)** + +The PENALTY\_TIME is coded as the binary representation of the "PENALTY\_TIME" in 3GPP TS 45.008. It defines the length of time for which TEMPORARY\_OFFSET is active. The usage of PENALTY\_TIME is described in 3GPP TS 23.022 and 3GPP TS 45.008. + +**POWER\_OFFSET (2 bit field)** + +POWER\_OFFSET is used only by DCS 1800 Class 3 MSs to add a power offset to the value of MS\_TXPWR\_MAX\_CCH used for its random access attempts. It is also used by the MS in its calculation of C1 and C2 parameters. Its use is defined in 3GPP TS 45.008. + +If this parameter is transmitted on a BCCH carrier within the DCS 1800 band, its meaning shall be described below: + +| Value | Meaning | +|-------|-------------------| +| 00 | 0 dB power offset | +| 01 | 2 dB power offset | +| 10 | 4 dB power offset | +| 11 | 6 dB power offset | + +If this parameter is transmitted on a BCCH carrier outside the DCS 1800 band, then all bit positions shall be treated as spare. + +**GPRS Indicator** + +The **GPRS Indicator** contains the RA COLOUR field and the SI13\_POSITION field. If the GPRS Indicator is contained in the information element, it indicates that GPRS is supported in the cell. + +**RA COLOUR (3 bit field)** + +If the mobile station receives different values of the RA COLOUR field in two cells belonging to the same location area or there are two cells belonging to different location areas, the mobile station shall interpret the cell re-selection information as if the two cells belong to different routeing areas. Otherwise, the mobile station shall interpret the cell re-selection information as if the two cells belong to the same routeing area. + +**SI13\_POSITION (1 bit field)** + +The SI13\_POSITION field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13 message is sent on BCCH, see 3GPP TS 45.002: + +- 0 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Norm; +- 1 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Ext. + +**Break Indicator** + +The Break Indicator indicates if parameters in addition to those in SI 4 rest octets are sent in SI7 and SI8. + +- L Additional parameters are not sent in SYSTEM INFORMATION TYPE 7 and 8. +- H Additional parameters, "SI4 Rest Octets\_S", are sent in SYSTEM INFORMATION TYPE 7 and 8. + +**PRIO\_THR (3 bit field)** + +The PRIO\_THR field is a signal threshold used by the mobile station to determine whether prioritised cell re-selection shall apply. The use and coding of this parameters is defined in 3GPP TS 45.008. + +**LSA\_OFFSET** (3 bit field) + +The LSA\_OFFSET field applies an offset for LSA reselection between cells with same LSA priorities. The use and coding of this parameter is defined in 3GPP TS 45.008. + +**MCC and MNC** (24 bit field) + +If the escape PLMN is broadcast in SI3 and SI4 the cell is used for SoLSA exclusive access and the MCC and MNC field shall be included. The MS shall then for all purposes use the MCC and MNC values received in the LSA Parameters instead of the ones received in the Location Area information element in SI3 and 4, eg when deriving the PLMN identity, the Location Area Identity and Cell Global Identity broadcast by the cell. The MCC and MNC value field is coded as specified in figure 10.5.2.37.1 and table 10.5.2.37.1. + +**Cell Identity** (16 bit field) + +The purpose of the Cell Identity is to identify a cell within a location area (see sub-clause 10.5.1.1). + +**LSA\_ID** (24 bit field) + +The purpose of the LSA\_ID field is to identify a LSA. The LSA ID value field is specified in 3GPP TS 23.003. + +**Short LSA\_ID** (10 bit field) + +The purpose of the Short LSA\_ID field is to identify a LSA. The LSA ID defined by the Short LSA\_ID is a LSA\_ID as specified in 3GPP TS 23.003 with bit 0 set to "0" bit 1 to 10 set to the value of the Short LSA\_ID field (LSB in bit 1, MSB in bit 10) and bit 11 to 23 set to "0". + +**CBQ3, Cell Bar Qualify 3** (2 bit field) + +The Cell Bar Qualify 3 is coded as shown in table 10.5.2.11.1. + +**SI13alt Position** (1 bit field) + +The SI13alt Position is included if and only if GPRS is not supported and *Iu mode* is supported in the cell. If both GPRS and *Iu mode* are supported in the cell then SI13alt Position is not sent, see 3GPP TS 44.118. + +The SI13alt Position field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13alt message is sent on BCCH. + +| Bit | | +|-----|-------------------------------------------------------------| +| 0 | SYSTEM INFORMATION TYPE 13alt message is sent on BCCH Norm; | +| 1 | SYSTEM INFORMATION TYPE 13alt message is sent on BCCH Ext. | + +## 10.5.2.35a SI 6 Rest Octets + +The *SI 6 Rest Octet* information element may contain information concerning the paging, notification channels, VBS and VGCS services of the cell. + +The *SI 6 Rest Octets* information element is a type 5 information element with 7 octets length. + +The value part is as shown below: + +Table 10.5.2.35a.1: SI 6 Rest Octets information element content + +``` + + ::= + { L | H } + { L | H } + { + < DTM_support : bit == L > + | + < DTM_support : bit == H > + < RAC : bit (8) > + < MAX_LAPDm : bit (3) > } + < Band indicator > + { L | H < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { L | H + -- MBMS procedures supported by the cell + < DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT: bit > + < MNCI_SUPPORT: bit > } + { + L + -- Receiver compatible with earlier release + | + H + -- Additions in Release 7 : + { 0 | 1 } + } + { H < Random bit stream : bit ** > + | L + -- Extension must be made in expanding the "L" branch with a new structure including a 'Random bit stream' + } + < spare padding >; + + ::= + + + {0 | 1 } + ; + + ::= + 1| -- paging channel is restructured + 0 -- paging channel is not restructured + + ::= + + ; + + ::= + 0| -- the network does not provide notification on FACCH so that the mobile should + inspect the NCH for notifications + 1 -- the mobile shall be notified on incoming high priority VBS/VGCS calls through + NOTIFICATION/FACCH, the mobile need not to inspect the NCH + + ::= + 0| -- the network does not provide paging information on FACCH so that the mobile + should inspect the PCH for pagings + 1 -- the mobile shall be notified on incoming high priority point-to-point calls + through NOTIFICATION/FACCH, the mobile need not to inspect the PCH + +< Band indicator > ::= + < BAND_INDICATOR : bit == L > -- ARFCN indicates 1800 band +| + < BAND_INDICATOR : bit == H > ; -- ARFCN indicates 1900 band + +``` + +Table 10.5.2.35a.2: SI 6 Rest Octets information element details + +## Attributes, field contents: + +1. For : the presence of the NLN(SACCH) field indicates that if an NCH is present, reduced NCH monitoring can be used, and gives the NLN(SACCH) value, to be used as specified in sub-clause 3.3.3. +2. For the : the NLN status indicates the status of the content of the NOTIFICATION/NCH messages for a particular NLN value. A change of the NLN status field indicates a change of information on the NCH which is not related to new calls, as specified in sub-clause 3.3.3. +3. For : see 10.5.2.23. Indication of the highest priority associated with VBS/VGCS calls in a cell. + +**DTM\_support** (1 bit field) + +This field indicates whether DTM is supported in the serving cell (i.e. whether the MS is allowed to initiate the packet request procedure while in dedicated mode). It is coded as follows: + +| | | | +|-----|---|------------------------------------------| +| Bit | 0 | | +| | L | DTM is not supported in the serving cell | +| | H | DTM is supported in the serving cell | + +--- + +**RAC** (8 bit field) + +This field codes the Routeing Area Code of the RA to which the serving cell belongs (see 3GPP TS 23.003). + +--- + +**MAX\_LAPDm** (3 bit field) + +This field indicates the maximum number of LAPDm frames on which a layer 3 can be segmented into and be sent on the main DCCH. It is coded as follows: + +| Bit | | | | +|-----|---|---|----------------------------------------------------------------| +| 2 | 1 | 0 | | +| 0 | 0 | 0 | Any message segmented in up to 5 LAPDm frames (default value). | +| 0 | 0 | 1 | Any message segmented in up to 6 LAPDm frames. | +| 0 | 1 | 0 | Any message segmented in up to 7 LAPDm frames. | +| 0 | 1 | 1 | Any message segmented in up to 8 LAPDm frames. | +| 1 | 0 | 0 | Any message segmented in up to 9 LAPDm frames. | +| 1 | 0 | 1 | Any message segmented in up to 10 LAPDm frames. | +| 1 | 1 | 0 | Any message segmented in up to 11 LAPDm frames. | +| 1 | 1 | 1 | Any message segmented in up to 12 LAPDm frames. | + +If this parameter has not yet been received by the MS in the serving cell, the MS shall assume the default value of '000' (5 LAPDm frames) + +--- + +**BAND\_INDICATOR** (1 bit field) + +The band indicator for 1800 and 1900 associates the ARFCN channel numbers to the DCS 1800 respectively to the PCS 1900 band, see 3GPP TS 45.005. + +--- + +**GPRS\_MS\_TXPWR\_MAX\_CCH** (5 bits field) + +The GPRS\_MS\_TXPWR\_MAX\_CCH field is coded as the binary representation of the "power control level" in 3GPP TS 45.005 corresponding to the maximum TX power level the MS shall use for packet resources while in dual transfer mode. This value shall be used by the Mobile Station according to 3GPP TS 45.008. + +Range: 0 to 31. + +--- + +**DEDICATED\_MODE\_MBMS\_NOTIFICATION\_SUPPORT** (1 bit field) + +This field is encoded as the DEDICATED\_MODE\_MBMS\_NOTIFICATION\_SUPPORT field in the GPRS Cell Options information element as defined in 3GPP TS 44.060 + +--- + +**MNCI\_SUPPORT** (1 bit field) + +This field is encoded as the **MNCI\_SUPPORT** field in the GPRS Cell Options information element as defined in 3GPP TS 44.060 + +--- + +**AMR\_Config** (4 bit field) + +This field indicates the set of AMR codec modes to be used on a group channel using speech version 3. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92], subclause 7.11.3.1.3. + +--- + +**Random bit stream** + +For a given mobile station, the rest octets are filled with a random bit stream. + +## 10.5.2.36 SI 7 Rest Octets + +The *SI 7 Rest Octets* information element includes parameters which are used by the mobile station for cell selection and reselection purposes. It may also include the POWER OFFSET parameter used by a DCS 1800 Class 3 MS. + +The *SI 7 Rest Octets* information element is a type 5 information element with 20 octets length. + +The *SI 7 Rest Octets* information element is coded as described in tables 10.5.2.35.1 and 10.5.2.35.2. + +### 10.5.2.37 SI 8 Rest Octets + +The *SI 8 Rest Octets* information element includes parameters which are used by the mobile station for cell selection and reselection purposes. It may also include the POWER OFFSET parameter used by a DCS 1800 Class 3 MS. + +The *SI 8 Rest Octets* information element is a type 5 information element with 20 octets length. + +The *SI 8 Rest Octets* information element is coded as described in tables 10.5.2.35.1 and 10.5.2.35.2. + +### 10.5.2.37a SI 9 Rest Octets + +The *SI 9 Rest Octets* information element contains information about scheduling of some or all of the information on the BCCH. + +The *SI 9 Rest Octets* information element is coded as shown in table 10.5.2.37a.1 and table 10.5.2.37a.2. + +The *SI 9 Rest Octets* information element is a type 5 information element with 17 octets length. + +**Table 10.5.2.37a.1: SI 9 Rest Octets information element content** + +| | | | | +|-------------------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| | ::= | {L H
} | | +| | ::= |
{0 1 } | | +| | ::= | 0
1 0
1 1 } | | +| | ::= |
{0 1 } | | +| | ::= | < modulus: bit (4) == 0000 >
< bcch_type: bit (1) >
< modulus: bit (4) exclude 0000 >
< relative_position: < bit (1 + val(modulus)) >>
< bcch_type: bit (1) > ; | --length depends on modulus | + +**Table 10.5.2.37a.2: SI 9 rest octet information element details** + +#### Attributes + +The *scheduling info* indicates one or more information types (in *info type*) together with their *positions*. Here, a *position* specifies at which relative position P (specified in **relative\_position**) modulo a position modulus M (specified in **modulus**) messages of the given information type are sent, on the BCCH norm or BCCH ext (see 3GPP TS 45.002) as indicated in **bcch\_type**. Precisely, messages of the given information type are sent in the multiframes for which + +$$((\text{frame number}) \text{ DIV } 51) \bmod (M) = P.$$ + +If the position modulus M equals 0, the information type is not sent. + +#### Info\_type\_4\_(4 bits) + +This field contains a binary encoded non-negative integer number assigned to a type of information sent on the BCCH. All values indicate unknown, unnecessary information and are reserved for future use. + +**Info\_type\_5 (5 bits)** + +This field contains a binary encoded non-negative integer number assigned to a type of information sent on the BCCH. All values except those defined below indicate unknown, unnecessary information and are reserved for future use. + +**Info\_type\_5:** + +Bit + +5 4 3 2 1 + +| | | +|-----------|------------------------------| +| 0 0 0 0 0 | System Information type 1 | +| 0 0 0 0 1 | System Information type 2 | +| 0 0 0 1 0 | System Information type 2bis | +| 0 0 0 1 1 | System Information type 2ter | +| 0 0 1 0 0 | System Information type 3 | +| 0 0 1 0 1 | System Information type 4 | +| 0 0 1 1 0 | System Information type 7 | +| 0 0 1 1 1 | System Information type 8 | +| 0 1 0 0 0 | System Information type 9 | +| 0 1 0 0 1 | System Information type 13 | +| 0 1 0 1 1 | System Information type 16 | +| 0 1 1 0 0 | System Information type 17 | +| 0 1 1 0 1 | System Information type 18 | +| 0 1 1 1 0 | System Information type 19 | +| 0 1 1 1 1 | System Information type 20 | +| 1 0 0 0 0 | System Information type 21 | +| 1 0 0 0 1 | System Information type 22 | +| 1 0 0 1 0 | System Information type 23 | + +**Info\_type\_6 (6 bits)** + +This field contains a binary encoded non-negative integer number assigned to a type of information sent on the BCCH. All values indicate unknown, unnecessary information and are reserved for future use. + +**modulus (4 bits)** + +This field encodes the **position modulus**, according to the following encoding method. Let N be the integer encoded in binary in the **modulus** field; the **position modulus** is then defined as follows : + +If $N=0$ , the **position modulus** is 0, + +if $N>0$ , the **position modulus** is $2^{N+1}$ . + +**relative position** (0 bits if the non-negative integer n contained in the **modulus** field is 0; n+1 bits, if the non-negative integer n encoded in the **modulus** field is > 0) + +This field contains the N+1 bit binary encoding of a non-negative integer number $< 2^{N+1}$ . + +**bcch\_type (1 bit)** + +| | | +|---|------------------------------------------| +| 0 | BCCH Norm (as defined in 3GPP TS 45.002) | +| 1 | BCCH Ext (as defined in 3GPP TS 45.002) | + +### 10.5.2.37b SI 13 Rest Octets + +The *SI 13 Rest Octets* information element is coded according to the syntax specified below and described in tables 10.5.2.37b.1 and 10.5.2.37b.2. + +The *SI 13 Rest Octets* information element is a type 5 information element with 20 octets length. + +**Table 10.5.2.37b.1: SI 13 Rest Octets information element content** + +``` + +< SI 13 Rest Octets > ::= + { L | H + < BCCH_CHANGE_MARK : bit (3) > + < SI_CHANGE_FIELD : bit (4) > + + { 0 | 1 < SI13_CHANGE_MARK : bit (2) > + < GPRS Mobile Allocation : GPRS Mobile Allocation IE > } -- Defined in 3GPP TS 44.060 + + { 0 -- PBCCH not present in cell (This shall always be indicated. See sub-clause 1.8) : + < RAC : bit (8) > + < SPGC_CCCH_SUP : bit > + < PRIORITY_ACCESS_THR : bit (3) > + < NETWORK_CONTROL_ORDER : bit (2) > + < GPRS Cell Options : GPRS Cell Options IE > -- Defined in 3GPP TS 44.060 + < GPRS Power Control Parameters : GPRS Power Control Parameters IE > + + | 1 -- PBCCH present in cell (This shall never be indicated. See sub-clause 1.8) : + < PSI1_REPEAT_PERIOD : bit (4) > + < PBCCH Description : PBCCH Description struct > + } + + { null | L -- Receiver compatible with earlier release + | H -- Additions in release 99 : + < SGSNR : bit > + + { null | L -- Receiver compatible with earlier release + | H -- Additions in release Rel-4: + < SI_STATUS_IND : bit > + + { null | L -- Receiver compatible with earlier release + | H -- Additions in release Rel-6: + { 0 | 1 < LB_MS_TXPWR_MAX_CCH : bit (5) > } + < SI2n_SUPPORT : bit(2) > + { + -- Additions in Rel-11: + < SI_CHANGE_ALT > + -- Additions in Rel-13: + { 0 | 1 < PEO_DSC : bit (2) > + < RCC : bit (3) > } + { 0 | 1 < C1_DELTA_MIN : bit (2) > + < C1_DELTA_MAX : bit (3) > } + -- Additions in Rel-14: + { 0 | 1 < MTA_BITMAP : bit (4) > } + < MS_ASSISTED_DCN : bit (1) > + -- Additions in Rel-15: + { 0 | 1 < PEO IMM Cell Group Definition : < PEO IMM Cell Group Definition struct >> } + + -- Additions in future releases shall be indicated above this line + } // -- truncation according to sub-clause 8.9 is allowed, bits "L" assumed + } + } + } + } +} +< spare padding > ; + +``` + +``` + +< PBCH Description struct > ::= + < Pb : bit (4) > + < TSC : bit (3) > + < TN : bit (3) > + { + 00 -- BCCH carrier + | 01 < ARFCN : bit (10) > + | 1 < MAIO : bit (6) > } ; +< SI_CHANGE_ALT > ::= L | H ; +< PEO IMM Cell Group Definition struct > ::= -- Addition in Rel-15 + < PEO IMM Cell Group Identifier : bit (3) > + < PEO IMM Change Mark : bit (2) > + < Timeout Read Complete SI : bit (2) > + < BCCH Frequency List Bitmap : bit (32) > + { 0 | 1 < PEO IMM Cell Group Specific Parameters : < PEO IMM Cell Group Specific Parameters struct >> } ; + +< PEO IMM Cell Group Specific Parameters struct > ::= + < Nb_NCELL : bit (4) > + { + < BSIC : bit (9) > + { 0 | 1 < CCCH-CONF SPECIFIC : bit (2) > } + { 0 | 1 < CELL_BAR_ACCESS SPECIFIC : bit (1) > } + } * (val(Nb_NCELL)+1) ; + { 0 | 1 < CCCH-CONF DEFAULT : bit (2) > } + { 0 | 1 < CELL_BAR_ACCESS DEFAULT : bit (1) > } ; + +``` + +**Table 10.5.2.37b.2: SI 13 Rest Octets information element** + +#### BCCH\_CHANGE\_MARK (3 bit field) + +This field indicates the status of the information on BCCH. The value of this field may be changed when information on BCCH is changed, see 3GPP TS 44.060. An exception is when EAB is enabled for a given set of PLMNs (see sub-clause 10.5.2.37m) and changes are made only to the EAB Authorization Mask and EAB Subcategory fields corresponding to this set of PLMNs in which case the BCCH\_CHANGE\_MARK field is not incremented (i.e. the network shall use the BCCH\_CHANGE\_MARK field to indicate when EAB has been enabled/disabled or when the set of PLMNs affected by EAB has changed). + +#### SI\_CHANGE\_FIELD (4 bit field) + +This field is the binary representation of which information was changed at the last indication in BCCH\_CHANGE\_MARK, see 3GPP TS 44.060. Range 0 to 15: + +- 0 Update of *unspecified* SI message or SI messages; +- 1 Update of SI1 message; +- 2 Update of SI2, SI2 bis or SI2 ter message or any instance of SI2quater messages; +- 3 Update of SI3, SI4, SI7, SI8, SI16 or SI17 message; +- 4 Update of SI9 message; +- 5 Update of SI18 or SI20 message; +- 6 Update of SI19 message; +- 7 Update of SI15 message; +- 8 Update of SI2n message; +- 9 Update of SI22 or SI23 message; + +All other values shall be interpreted as 'update of unknown SI message type'. + +#### SI13\_CHANGE\_MARK (2 bit field) + +This field is the binary representation of the SI change mark identifying the GPRS Mobile Allocation provided in SI13 and PSI13 messages. Range: 0 to 3. + +#### GPRS Mobile Allocation (information element) + +This information element is the representation of the GPRS mobile allocation provided in SI13 and PSI13 messages. It is identified by MA\_NUMBER = 14 when referenced from a packet assignment message. The *GPRS Mobile Allocation* information element is defined in 3GPP TS 44.060. When used in SI13 or PSI13 message, this information element shall refer to the cell allocation defined for the cell in SI1 or PSI2. + +**RAC** (8 bit field) + +This field is the binary representation of the Routing Area Code, see 3GPP TS 23.003. + +**SPGC\_CCCH\_SUP** (bit field) + +This field indicates the support of the parameter SPLIT\_PG\_CYCLE on CCCH from the network side: + +- | | | +|---|-------------------------------------------------------| +| 0 | SPLIT_PG_CYCLE is not supported on CCCH in this cell; | +| 1 | SPLIT_PG_CYCLE is supported on CCCH in this cell. | + +The **PRIORITY\_ACCESS\_THR** field (3 bit) is the binary representation of the parameter PRIORITY\_ACCESS\_THR: + +- | | | +|-------|-------------------------------------------------------------------| +| 0 0 0 | packet access is not allowed in the cell; | +| 0 0 1 | spare, shall be interpreted as '000' (packet access not allowed); | +| 0 1 0 | spare, shall be interpreted as '000' (packet access not allowed); | +| 0 1 1 | packet access is allowed for priority level 1; | +| 1 0 0 | packet access is allowed for priority level 1 to 2; | +| 1 0 1 | packet access is allowed for priority level 1 to 3; | +| 1 1 0 | packet access is allowed for priority level 1 to 4; | +| 1 1 1 | spare, shall be interpreted as '110' (packet access allowed). | + +The **NETWORK\_CONTROL\_ORDER** field (2 bit) is the binary representation of the parameter NETWORK\_CONTROL\_ORDER, see 3GPP TS 44.060: + +- | | | +|-----|--------------------------------------------------------------------------| +| 0 0 | NC0: MS controlled cell re-selection, no measurement reporting. | +| 0 1 | NC1: MS controlled cell re-selection, MS sends measurement reports. | +| 1 0 | NC2: Network controlled cell re-selection, MS sends measurement reports. | +| 1 1 | Reserved for future use, interpreted as NC0 by mobile station. | + +**GPRS Cell Options** (information element) + +The *GPRS Cell Option* information element is defined in 3GPP TS 44.060. + +**PSI1\_REPEAT\_PERIOD** (4 bit field) + +This field is the representation of the PSI1 repeat period. The field is coded according to the following table: + +- | | | +|------|-------------------------------------| +| 0000 | PSI1 repeat period = 1 multiframe | +| 0001 | PSI1 repeat period = 2 multiframes | +| ⋮ | | +| 1111 | PSI1 repeat period = 16 multiframes | + +**GPRS Power Control Parameters** + +The *GPRS Power Control Parameters* information element is defined in 3GPP TS 44.060. + +**PBCCH Description struct** + +The PBCCH description struct provides the channel description for the PBCCH. The frequency description for the PBCCH may be specified by an ARFCN (non-hopping radio frequency channel) or a MAIO (hopping radio frequency channel) field. In case of a hopping radio frequency channel, the PBCCH shall use the GPRS mobile allocation specified in this message. If none of the ARFCN or MAIO fields are present, the PBCCH shall use the BCCH carrier. + +**Pb** (4bit) (for encoding and description see the Global Power Control Parameters IE) + +The **TSC** field (3 bit) is the binary representation of the training sequence code used for PBCCH. Range: 0 to 7. + +The **TN** field (3 bit) is the binary representation of the timeslot number for the PBCCH. Range: 0 to 7. + +The **ARFCN** field (10 bit) is the binary representation of the absolute RF channel number. Range: 0 to 1023. + +The **MAIO** field (6 bit) is the binary representation of the mobile allocation index offset. Range: 0 to 63. + +**SGSNR, SGSN Release** (1 bit field) + +- | | | +|---|------------------------------| +| 0 | SGSN is Release '98 or older | +| 1 | SGSN is Release '99 onwards | + +**SI\_STATUS\_IND** (1 bit field) + +- | | | +|---|------------------------------------------------------------| +| 0 | The network does not support the PACKET SI STATUS message; | +| 1 | The network supports the PACKET SI STATUS message. | + +**LB\_MS\_TXPWR\_MAX\_CCH** (5 bit field) + +The LB\_MS\_TXPWR\_MAX\_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008. + +**SI2n\_SUPPORT** (2 bit field) + +The SI2n\_SUPPORT field indicates whether the network supports the SI2n message provision. + +- | | | +|----|-------------------------------------------------------| +| 00 | SI2n is not supported | +| 01 | SI2n is supported on PACCH | +| 10 | SI2n is supported on PACCH and broadcast on BCCH | +| 11 | SI2n is supported on PACCH and broadcast on BCCH Ext. | + +**SI\_CHANGE\_ALT** + +This field indicates how a mobile station supporting network sharing shall take into account a change of system information signalled by a SI\_CHANGE\_FIELD value '2': + +- L A mobile station supporting network sharing should not attempt to re-read the SI2quater message; +- H A mobile station supporting network sharing shall fully take into account a change of system information signalled by the SI\_CHANGE\_FIELD value '2', SI2quater included. + +**PEO\_DSC (2 bit field)** + +This field provides an initial value for the downlink signalling counter (DSC) used for verifying the ongoing ability of a MS that has enabled eDRX to receive paging messages on the PCH (3GPP TS 45.008). The presence of the PEO\_DSC field indicates the serving cell supports PEO. + +The PEO\_DSC field is coded according to the following table: + +| | | +|----|----------| +| 00 | DSC = 4 | +| 01 | DSC = 6 | +| 10 | DSC = 8 | +| 11 | DSC = 10 | + +**RCC (3 bit)** + +See sub-clause 10.5.2.16. + +**C1\_DELTA\_MIN (2 bit field)** + +See sub-clause 9.1.43r. + +**C1\_DELTA\_MAX (3 bit field)** + +See sub-clause 9.1.43r. + +**MTA\_BITMAP (4 bits)** + +This field contains a bitmap indicating the MTA methods supported by a cell. This field is encoded as follows. + +Bits + +4 3 2 1 + +x x x 1 MTA RLC Data Block method supported + +x x 1 x MTA Access Burst method supported + +x 1 x x MTA Extended Access Burst method supported + +**MS\_ASSISTED\_DCN** + +This field indicates if the cell supports MS assisted Dedicated Core Network selection, see 3GPP TS 23.401 [110]. + +- 0 The network does not support MS assisted Dedicated Core Network selection; +- 1 The network supports MS assisted Dedicated Core Network selection. + +All remaining bit positions are reserved. + +### PEO IMM Cell Group Definition struct + +This structure provides identifier, change mark indication as well as common and specific cell parameters of the PEO IMM Cell Group which the serving cell belongs to. Common cell parameters across cells in the same PEO IMM cell group are contained in the PEO IMM Cell Group Definition structure (see below) and further refer to following cell parameters outside the PEO IMM Cell Group Definition structure, if sent for the serving cell in SI2 / SI3 messages (i.e. these parameters broadcasted by the serving cell are interpreted as common parameters of the PEO IMM cell group): + +Common cell parameters outside the PEO IMM Cell Group Definition structure in SI13: + +Parameters in Neighbour Cell Description IE (sent in SI2): + +BCCH Frequency List : octets (16) + +Parameters in Control Channel Description IE (sent in SI3): + +CCCH-CONF : bit (3) + +Parameters in Cell Selection Parameters structure (sent in SI3): + +CELL\_RESELECT\_HYSTERESIS : bit (3) + +RXLEV\_ACCESS\_MIN : bit (6) + +MS\_TXPWR\_MAX\_CCH : bit (5) + +Parameters in RACH Control Parameters structure (sent in SI3): + +Cell\_Bar\_Access : bit (1) + +Parameters in Selection Parameters structure (sent in SI3 rest octets ): + +CELL\_RESELECT\_OFFSET : bit (6) + +Parameters sent in SI13 rest octets: + +Routing Area Code : bit (8) + +LB\_MS\_TXPWR\_MAX\_CCH : bit (5) + +C1\_DELTA\_MIN : bit (2) + +C1\_DELTA\_MAX : bit (3) + +### PEO IMM Cell Group Identifier (3 bits) + +This field is the binary representation of the identity of the PEO IMM cell group. Range: 0 to 7. + +Bits + +3 2 1 + +0 0 0 not used + +0 0 1 Cell Group Identity 1 + +0 1 0 Cell Group Identity 2 + +0 1 1 Cell Group Identity 3 + +1 0 0 Cell Group Identity 4 + +1 0 1 Cell Group Identity 5 + +1 1 0 Cell Group Identity 6 + +1 1 1 Cell Group Identity 7 + +### PEO IMM Change Mark (2 bits) + +This field is the binary representation of the PEO IMM Change Mark value N indicating the status of the PEO IMM Cell Group description, referring to parameters belonging to the PEO IMM Cell Group Definition struct and to specific parameters sent in SI3 and SI13. Range: 0 to 3. Whenever the value of parameters belonging to the PEO IMM Cell Group description is modified, the PEO IMM Change Mark value N is incremented to (N+1) modulo 4. If only parameters are modified that belong to the PEO IMM Cell Group Definition struct, neither the BCCH CHANGE MARK nor the PEO BCCH CHANGE MARK field shall be incremented by the network. + +### BCCH Frequency List Bitmap (32 bits) + +This field informs about all BCCH carriers, as a set of ARFCNs, of cells belonging to the same PEO IMM Cell Group as the serving cell. The information is encoded as bitmap referring to the BCCH Frequency List IE in the Neighbour Cell Description sent in SI2 related to BCCH ARFCNs used in cells belonging to the same PEO IMM Cell Group as the serving cell. The bitmap is organised according to the ARFCN value, i.e. the lowest valued ARFCN in the BCCH Frequency List IE refers to LSB and the highest valued ARFCN in the BCCH Frequency List IE to MSB. + +**Timeout Read Complete SI (2 bits)** + +This field indicates the timeout for triggering the acquisition of the complete set of System Information messages in the serving cell, if the last acquisition of the complete set of System Information messages has been performed in a different cell. It is coded as follows. + +**Bits** + +2 1 + +0 0 [2] minutes + +0 1 [5] minutes + +1 0 [15] minutes + +1 1 reserved + +**PEO IMM Cell Group Specific Parameters struct** + +This structure provides specific cell parameters of neighbour cells belonging to the same PEO IMM Cell Group as the serving cell. + +**Nb\_NCELL (4 bits)** + +This field indicates the number of neighbour cells belonging to the same PEO IMM Cell Group as the serving cell for which the number of CCCHs or the cell barring status deviates from the default parameter CCCH-CONF\_DEFAULT or CELL\_BAR\_ACCESS\_DEFAULT, respectively. The Nb\_NCELL field is coded as follows: + +**Bits** + +4 3 2 1 + +0 0 0 0 1 neighbour cell + +0 0 0 1 2 neighbour cells + +... + +1 1 1 1 16 neighbour cells + +**BSIC (9 bits)** + +The BSIC field identifies the neighbour base station for which the specific PEO IMM Cell Group parameters (rather than the default values) are valid. The BSIC field is encoded as a 9 bit field, as specified for PEO, see 3GPP TS 45.002. + +The use of the BSIC field is defined in 3GPP TS 45.008. + +**CCCH-CONF\_SPECIFIC (2 bits)** + +This field indicates the number of common control channels (CCCHs) that shall be applied for each cell sharing the same PEO IMM Cell Group as the serving cell, if its BSIC is contained in the cell description of the PEO IMM Cell Group Definition struct to indicate specific parameters for that cell. It is coded as the field CCCH-CONF (sent in SI3). It overwrites the default parameter CCCH-CONF\_DEFAULT for that cell. + +**CELL\_BAR\_ACCESS\_SPECIFIC (1 bit)** + +This field indicates the cell barring status that shall be applied for each cell sharing the same PEO IMM Cell Group as the serving cell, if its BSIC is contained in the cell description of the PEO IMM Cell Group Definition struct to indicate specific parameters for that cell. It is coded as the field Cell\_Bar\_Access (sent in SI3). It overwrites the default parameter CELL\_BAR\_ACCESS\_DEFAULT for that cell. + +**CCCH-CONF\_DEFAULT (2 bits)** + +This field indicates the number of common control channels (CCCHs) that shall be used by default for all cells sharing the same PEO IMM Cell Group as the serving cell, if their BSIC is not contained in the cell description of the PEO IMM Cell Group Definition struct. It is coded as the field CCCH-CONF (sent in SI3). If this parameter is not broadcasted, the MS shall assume that all cells belonging to the same PEO IMM Cell Group use the same value for this parameter and the value indicated in CCCH-CONF (sent in SI3) applies. + +**CELL\_BAR\_ACCESS\_DEFAULT (1 bit)** + +This field indicates the cell barring status that shall be used by default for all cells sharing the same PEO IMM Cell Group as the serving cell, if their BSIC is not contained in the cell description of the PEO IMM Cell Group Definition struct. It is coded as the field Cell\_Bar\_Access (sent in SI3). If this parameter is not broadcasted, the MS shall assume that all cells belonging to the same PEO IMM Cell Group use the same value for this parameter and the value indicated in Cell\_Bar\_Access (sent in SI3) applies. + +NOTE: The SGSN Release bit indicates the version of the SGSN specific protocols and is not applicable to access stratum protocols. + +10.5.2.37c (void) + +10.5.2.37d (void) + +## 10.5.2.37e SI 16 Rest Octets + +The *SI 16 Rest Octets* information element includes parameters which are used by the mobile station for cell selection and reselection purposes. + +The *SI 16 Rest Octets* information element is coded according to the syntax specified below. Its contents is described in table 10.5.2.37c.1. + +The *SI 16 Rest Octets* information element is a type 5 information element with 20 octets length. + +**Table 10.5.2.37e.1: SI 16 Rest Octets information element** + +``` + + ::= {L | H } + ; + + ::= < SI16 Rest Octets> ; + + ::= + + {0 | 1 + } + ; + + ::= + {0 | 1 } ; + + ::= { 0 + |1 } ; + +``` + +**Table 10.5.2.37e.2: SI 16 Rest Octets information element details** + +**PRIO\_THR (3 bit field)** + +The PRIO\_THR field is a signal threshold used by the mobile station to determine whether prioritised cell re-selection shall apply. The use and coding of this parameters is defined in 3GPP TS 45.008. + +**LSA\_OFFSET (3 bit field)** + +The LSA\_OFFSET field applies an offset for LSA reselection between cells with same LSA priorities. The use and coding of this parameters is defined in 3GPP TS 45.008. + +**MCC and MNC (24 bit field)** + +If the escape PLMN is broadcast in SI3 and SI4 the cell is used for SoLSA exclusive access and the MCC and MNC field shall be included. The MS shall then for all purposes use the MCC and MNC values received in the LSA Parameters instead of the ones received in the Location Area information element in SI3 and 4, eg when deriving the PLMN identity, the Location Area Identity and Cell Global Identity broadcast by the cell. The MCC and MNC value field is coded as specified in figure 10.5.33 and table 10.5.3. + +**LSA\_ID (24 bit field)** + +The purpose of the LSA\_ID field is to identify a LSA. The LSA ID value field is coded as specified in 3GPP TS 23.003. + +**Short LSA\_ID (10 bit field)** + +The purpose of the Short LSA\_ID field is to identify a LSA. The LSA ID defined by the Short LSA\_ID is a LSA\_ID as specified in 3GPP TS 23.003 with bit 0 set to "0" bit 1 to 10 set to the value of the Short LSA\_ID field (LSB in bit 1, MSB in bit 10) and bit 11 to 23 set to "0". + +## 10.5.2.37f SI 17 Rest Octets + +The *SI 17 Rest Octets* information element includes parameters, which are used by the mobile station for cell selection and reselection purposes. + +The *SI 17 Rest Octets* information element is a type 5 information element with 20 octets length. + +The *SI 17 Rest Octets* information element is coded as the *SI 16 Rest Octets*. Its contents is described in tables 10.5.2.37e.1 and 10.5.2.37e.2. + +## 10.5.2.37g SI 19 Rest Octets + +The *SI 19 Rest Octets* information element contains information for cell re-selection to COMPACT channels. + +The *SI 19 Rest Octets* information element is a type 5 information element with 20 octets length. + +The value part is coded as shown below. + +**Table 10.5.2.37g.1: SI 19 Rest Octets information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < SI 19 Rest Octets > ::=   < SI19_CHANGE_MARK : bit (2) >   < SI19_INDEX : bit (3) >   < SI19_LAST : bit (1) >   < COMPACT Neighbour Cell Parameters : < COMPACT Neighbour Cell params struct > >   < spare padding >;  < COMPACT Neighbour Cell params struct > ::=   { 1 < START_FREQUENCY : bit (10) >     < COMPACT Cell selection params : COMPACT Cell Selection struct >     < NR_OF_REMAINING_CELLS : bit (4) >     < FREQ_DIFF_LENGTH : bit (3) >     { < FREQUENCY_DIFF : bit (n) >       < COMPACT Cell Selection struct > > } * val(NR_OF_REMAINING_CELLS)   } ** 0 ;  < COMPACT Cell Selection struct > ::=   { 0 < BCC : bit (3) >   1 < BSIC : bit (6) > }   < CELL_BARRED : bit (1) >   0 0     -- The values '01', '10' and '11' were allocated in an     -- earlier version of the protocol and shall not be used.   { < LA Different parameters : < LA Different struct > > }   { 0   1 < MS_TXPWR_MAX_CCH : bit (5) > }   { 0   1 < RXLEV ACCESS MIN : bit (6) > }   { 0   1 < CELL_RESELECT_OFFSET : bit (6) > }   { 0   1 < TEMPORARY_OFFSET : bit (3)     < PENALTY_TIME : bit (5) > }   { 0   1 < TIME_GROUP : bit (2) > }   { 0   1 < GUAR_CONSTANT_PWR_BLKS : bit (2) > } ;  < LA Different struct > ::=   { 0   1 < CELL_RESELECT_HYSTERISIS : bit (3) > ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.5.2.37g.2: SI 19 Rest Octets information element details** + +### SI19\_CHANGE\_MARK (2 bit field) + +The SI19 change mark field is changed each time information has been updated in any of the SI19 messages. A new value indicates that the mobile station shall re-read the information from all the SI19 messages. The coding of this field is network dependent. + +Range: 0-3. + +**SI19\_INDEX (3 bit field)** + +The SI19\_INDEX field is used to distinguish individual SI19 messages containing information about different neighbour cells. The field can take the binary representation of the values 0 to n, where n is the index of the last SI19 message. + +Range: 0-7. + +**SI19\_LAST (1 bit field)** + +This field is coded as binary one if the SI19\_INDEX in this message is the last SI19 message (*i.e.*, it represents the highest SI19\_INDEX being broadcast). If the field is coded as binary zero, then this is not the last SI19 message. + +Range: 0-1. + +**START\_FREQUENCY (10 bit field)** + +The Start Frequency defines the ARFCN for the BCCH frequency of the first cell in the list. + +**FREQ\_DIFF\_LENGTH (3 bit field)** + +The Freq Diff length field specifies the number of bits to be used for the Frequency diff field in the current Frequency group. The field is coded according to the following table + +| | | +|-------|--------| +| 3 2 1 | | +| 0 0 0 | 1 bit | +| 0 0 1 | 2 bits | +| ... | | +| 1 1 1 | 8 bits | + +**NR\_OF\_REMAINING\_CELLS (4 bit field)** + +This field specifies the remaining number of cells that are defined in the frequency group. For each of them the parameters 'Frequency diff' and 'Cell selection params' will be repeated. + +Range 1-16. + +**COMPACT Cell Selection params** + +This struct contains information about COMPACT neighbour cells. The first field of the COMPACT Cell Selection struct, BSIC, defines the BSIC of the cell and then comes the field same RA as serving cell. Then follows none, some, or all of the fields MS\_TXPWR\_MAX\_CCH, RXLEV ACCESS MIN, CELL\_RESELECT\_OFFSET, TEMPORARY\_OFFSET, PENALTY\_TIME, TIME\_GROUP, GUAR\_CONSTANT\_PWR\_BLKS. If fields are omitted, the values for these parameters are the same as for the preceding cell. + +**FREQUENCY\_DIFF ("Freq Diff length" bit field)** + +The Frequency Diff field specifies the difference in ARFCN to the BCCH carrier in the next cell to be defined. Note that the difference can be zero if two specified cells use the same frequency. + +**BSIC (6 bit field)** + +The BSIC field is coded as the "Base Station Identity Code" defined in 3GPP TS 23.003. + +**BCC (3 bit field)** + +The BCC is specified by encoding its binary representation; it specifies the BSIC given by that BCC and the NCC of the BSIC specified by the previous occurrence of or . + +**CELL\_BARRED (1 bit field)** + +| | | +|---|------------------------| +| 0 | The cell is not barred | +| 1 | The cell is barred | + +**TIME\_GROUP** (2 bit field) + +The TIME\_GROUP defines which time group (see 3GPP TS 45.002) the cell belongs to + +Bit +2 1 +0 0   Time Group 0 +0 1   Time Group 1 +1 0   Time Group 2 +1 1   Time Group 3 + +**GUAR\_CONSTANT\_PWR\_BLKS** (2 bit field) + +This field indicates the guaranteed number of constant power blocks in the neighbour cell. These are the blocks that the MS can use to perform neighbour cell measurements (see 3GPP TS 45.008). Note that there may be more CPBCCH blocks or allowed paging blocks in the neighbour cell than what is indicated in this field, but never less. + +Bit +2 1   Blocks at constant power +0 0   4 +0 1   5 +1 0   6 +1 1   12 (i.e. BS\_PAG\_BLKS\_RES = 0 in that cell) + +**10.5.2.37h SI 18 Rest Octets** + +The *SI 18 Rest Octets* information element includes parameters for non-GSM networks. + +The *SI 18 Rest Octets* information element is a type 5 information element and is 20 octets long. + +Several Non-GSM information containers may be mapped into one instance of this information element, separated by a Non-GSM protocol discriminator. The last Non-GSM information container may be continued in a subsequent instance of this information element. + +**Table 10.5.2.37h.1: *SI 18 Rest Octets* information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< SI 18 Rest Octets > ::=   < SI18_CHANGE_MARK : bit (2) >   < SI18_INDEX : bit (3) >   < SI18_LAST : bit (1) >   < spare bit > * 2    { < Non-GSM Message : < Non-GSM Message struct > > } **     -- 	The Non-GSM Message struct is repeated until:     -- 		A) val(NR_OF_CONTAINER_OCTETS) = 0, or     -- 		B) the SI message is fully used    < spare padding > ;  < Non-GSM Message struct > ::=   < Non-GSM Protocol Discriminator : bit(3) >   < NR_OF_CONTAINER_OCTETS : bit(5) >   { < CONTAINER : bit(8) > } * (val(NR_OF_CONTAINER_OCTETS)) ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.5.2.37h.2: SI 18 information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

SI18_INDEX (3 bit field)

The SI18_INDEX field is used to distinguish individual SI18 messages. The field can take the binary representation of the values 0 to n, where n is the index of the last SI18 message.

Range: 0-7.

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**SI18\_LAST (1 bit field)** + +This field is coded as binary one if the SI18\_INDEX in this message is the last instance of the SI18 messages (i.e., it represents the highest SI18\_INDEX being broadcast). Otherwise, this field is coded as binary zero. + +Range: 0-1. + +**Non-SM Protocol Discriminator (3 bit field)** + +This information element is used to identify the non-GSM network for which a SI18 message is transmitted and is coded as shown below. + +bit +3 2 1 + +0 0 1 TIA/EIA-136 + +All other values are reserved + +**NR\_OF\_CONTAINER\_OCTETS (5 bit field)** + +This field indicates the number of CONTAINER octets that forms a specific non-GSM message and is coded as shown below. + +Bit +5 4 3 2 1 +0 0 0 0 0 +0 0 0 0 1 +0 0 0 1 0 +through +1 0 0 1 0 +1 1 1 1 1 + +Zero octets. There are no more **NonGSM Messages** embedded in this SI message. The **Non-GSM Protocol Discriminator** field is spare (i.e., sent as '000', not verified by the receiver). +**CONTAINER** length is 1 octet +**CONTAINER** length is 2 octets +**CONTAINER** length is 18 octets + The remaining portion of the SI message instance is used by the associated **CONTAINER**. The Non-GSM message continues in a subsequent instance of the SI message, in the next **CONTAINER** with the same **Non-GSM Protocol Discriminator** value as the current one. + +All other values are reserved. + +**CONTAINER (8 bits)** + +The concatenation of one or several CONTAINER octets forms the actual contents, specific to the non-GSM network soliciting the transmission of a SI18 message. + +NOTE: The format of SI 18 Rest Octets when 2 different Non-GSM messages are sent is exemplified below. + +![](c1b8d1a76c94ebabe6784f51473b317b_img.jpg) + +| Bit | | | | Octet 1 | | | | +|--------------------------------|------------|------------------------|-----------|----------------|--------------------|---|---| +| 8 | 7 | 6 | 5 | | 4 | 3 | 2 | +| SI18 CHANGE MARK | SI18 INDEX | | SI18 LAST | Spare bits 0 0 | Octet 1 | | | +| Non-GSM Protocol Discriminator | | NR_OF_CONTAINER_OCTETS | | | Octet 2 | | | +| Non-GSM CONTAINER.1 | | | | | . | | | +| . | | | | | . | | | +| . | | | | | . | | | +| Non-GSM Protocol Discriminator | | NR_OF_CONTAINER_OCTETS | | | Octet M (optional) | | | +| . | | | | | Octet M+1 | | | +| . | | | | | . | | | +| Non-GSM CONTAINER 2 | | | | | . | | | +| . | | | | | . | | | +| . | | | | | Octet N-1 | | | +| . | | | | | Octet N | | | +| Spare padding | | | | | (if present) | | | + +## 10.5.2.37i SI 20 Rest Octets + +The *SI 20 Rest Octets* information element includes parameters for non-GSM networks. + +The *SI 20 Rest Octets* information element is a type 5 information element and is 20 octets long. + +The *SI 20 Rest Octets* are defined as the *SI 18 Rest Octets*, see also sub-clause 10.5.2.37h. + +## 10.5.2.37j SI 14 Rest Octets + +The *SI 14 Rest Octets* information element contains information about dynamic ARFCN mapping. It allows to allocate ARFCN values and dynamically map them to physical frequencies, see 3GPP TS 45.005. + +The *SI 14 Rest Octets* information element is a type 5 information element with 16 octet length. + +**Table 10.5.2.37j.1: SI14 message content** + +``` +< SI14 Rest Octets > ::= + < SI14_INDEX : bit (2) > + < SI14_COUNT : bit (2) > + < DM_CHANGE_MARK : bit (4) > + < DYNAMIC ARFCN MAPPING Description : { 1 < DYNAMIC ARFCN MAPPING > } ** 0 > + < spare padding > ; + +< DYNAMIC ARFCN MAPPING > ::= + < GSM_Band : bit (4) > + < ARFCN_FIRST : bit (10) > + < BAND_OFFSET : bit (10) > + < ARFCN_RANGE : bit (7) > ; +``` + +-- Dynamic ARFCN mapping parameters + +**Table 10.5.2.37j.2: SI14 message information** + +### SI14\_INDEX (2 bit field) + +The SI14\_INDEX field is used to distinguish individual SI14 messages. The field can take the binary representation of the values 0 to n, where n is the index of the last SI14 message. (SI14\_COUNT). + +### SI14\_COUNT (2 bit field) + +This field is coded as the binary representation of the SI14\_INDEX for the last (highest indexed) individual SI14 message. + +### DM\_CHANGE\_MARK (4 bit field), Dynamic ARFCN Mapping Change Mark. + +This parameter is used to indicate to the MS a change of information concerning Dynamic ARFCN Mapping. + +Dynamic ARFCN Mapping parameters description: + +**GSM\_Band** (4 bit field) + +This field indicates the band applicable for the parameters in this structure. + +Bits 4 - 1 + +| 4 | 3 | 2 | 1 | | +|---|---|---|---|-----------| +| 0 | 0 | 0 | 0 | GSM 750 | +| 0 | 0 | 0 | 1 | DCS 1800 | +| 0 | 0 | 1 | 0 | PCS 1900 | +| 0 | 0 | 1 | 1 | GSM T 380 | +| 0 | 1 | 0 | 0 | GSM T 410 | +| 0 | 1 | 0 | 1 | GSM T 900 | +| 0 | 1 | 1 | 0 | GSM 710 | +| 0 | 1 | 1 | 1 | GSM T 810 | + +All other values are reserved for future use and shall not be interpreted as an error. + +**ARFCN\_FIRST** (10 bit field) + +This parameter indicates the first ARFCN number for dynamic ARFCN mapping. + +**BAND\_OFFSET** (10 bit field) + +This parameter indicates the first carrier, on the band concerned, for dynamic ARFCN mapping. + +**ARFCN\_RANGE** (7 bit field) + +This parameter indicates the number of ARFCNs allocated, subsequent to ARFCN\_FIRST. + +The use of the parameters GSM\_Band, ARFCN\_FIRST, BAND\_OFFSET and ARFCN\_RANGE is described in 3GPP TS 45.005. + +If the mobile station receives more than 8 DYNAMIC\_ARFCN\_MAPPING structures, it shall store at least the 8 first structures in the order of occurrence, starting with the SI14 instance with the lowest index number. + +NOTE: For important guidelines on Dynamic ARFCN mapping, see Annex "Guidance on the Usage of Dynamic ARFCN Mapping" in 3GPP TS 45.005. + +## 10.5.2.37k SI 15 Rest Octets + +The *SI 15 Rest Octets* information element contains information about dynamic ARFCN mapping. It allows to allocate ARFCN values and then dynamically map to physical frequencies, see 3GPP TS 45.005. + +The *SI 15 Rest Octets* information element is a type 5 information element with 20 octet length. + +**Table 10.5.2.37k.1: SI15 message content** + +``` + +< SI15 Rest Octets > ::= + < SI15_INDEX : bit (2) > + < SI15_COUNT : bit (2) > + < DM_CHANGE_MARK : bit (4) > + < DYNAMIC ARFCN MAPPING Description : { 1 < DYNAMIC ARFCN MAPPING > } ** 0 > +< spare padding > ; + +< DYNAMIC ARFCN MAPPING > ::= + < GSM_Band : bit (4) > + < ARFCN_FIRST : bit (10) > -- Dynamic ARFCN mapping parameters + < BAND_OFFSET : bit (10) > + < ARFCN_RANGE : bit (7) > ; + +``` + +**Table 10.5.2.37k.2: SI15 message information****SI15\_INDEX** (2 bit field) + +The SI15\_INDEX field is used to distinguish individual SI15 messages. The field can take the binary representation of the values 0 to n, where n is the index of the last SI15 message. (SI15\_COUNT). + +**SI15\_COUNT** (2 bit field) + +This field is coded as the binary representation of the SI15\_INDEX for the last (highest indexed) individual SI15 message. + +**DM\_CHANGE\_MARK** (4 bit field), Dynamic ARFCN Mapping Change Mark. + +This parameter is used to indicate to the MS a change of information concerning Dynamic ARFCN Mapping. + +***Dynamic ARFCN Mapping parameters description*** + +These parameters are described in table 10.5.2.37j. + +**10.5.2.37l SI 13alt Rest Octets** + +The *SI 13alt Rest Octets* information element is coded according to the syntax specified below and described in tables 10.5.2.37l.1 and 10.5.2.37l.2. + +The *SI 13alt Rest Octets* information element is a type 5 information element with 20 octets length. + +**Table 10.5.2.37l.1: SI 13alt Rest Octets information element content** + +``` +< SI 13alt Rest Octets > ::= + < PBCCH Description : < PBCCH Description 2 struct >> + < spare padding > ; + +< PBCCH Description 2 struct > ::= + < PSII_REPEAT_PERIOD : bit (4) > + < Pb : bit (4) > + < TN : bit (3) > + < PBCCH Frequency Description : < Frequency Parameters IE >> ; -- Defined in +3GPP TS 44.060 +``` + +**Table 10.5.2.37l.2: SI 13alt Rest Octets information element****PSII\_REPEAT\_PERIOD** (4 bit field) + +This field is the binary representation, range 0 to 15, of the PSII repeat period. The coding of this field is identical to the coding of the PSII\_REPEAT\_PERIOD field in the PSII message defined in 3GPP TS 44.060. + +**Pb** (4 bit field) + +This is the binary representation, range 0 to 15, of the power reduction value used by the BTS on PBCCH blocks, relative to the output power on BCCH, see 3GPP TS 45.008. + +**TN** (3 bit field) + +This is the binary representation, range 0 to 7, of the timeslot number for the PBCCH, see 3GPP TS 45.002. + +**PBCCH Frequency Description** + +The PBCCH frequency description is encoded using the *Frequency Parameters* information element defined in 3GPP TS 44.060. When used in this message, the *Frequency Parameters* information element shall define a non-hopping radio frequency channel or use the *direct encoding* 2 to define a hopping radio frequency channel. + +**10.5.2.37m SI 21 Rest Octets** + +The *SI 21 Rest Octets* information element contains Extended Access Barring information. + +The SI 21 Rest Octets information element is a type 5 information element with 20 octet length. + +**Table 10.5.2.37m.1: SI 21 Rest Octets information element** + +``` +< SI 21 Rest Octets > ::= + < SI 21_CHANGE_MARK : bit (2) > + < SI 21_INDEX : bit (3) > + < SI 21_COUNT : bit (3) > + { 0 | 1 < EAB Authorization Mask: bit (10) > + < EAB Subcategory : bit (2) > } + { + -- Additions in Release 11 + { L | H < Network Sharing EAB Information : < Network Sharing EAB Information struct >> } + < spare padding > + } //; -- truncation according to sub-clause 8.9 is allowed, bits "L" assumed +< Network Sharing EAB Information struct > ::= + { 0 | 1 < Common PLMN PS EAB Authorization Mask : bit (10) > + < Common PLMN PS EAB Subcategory : bit (2) > } + < Nb_Additional_PLMNs : bit (2) > + { + { 0 -- The previously listed EAB Authorization Mask/Subcategory apply + | 1 -- The indicated EAB Authorization Mask/Subcategory apply + < Additional EAB Authorization Mask : bit (10) > + < Additional EAB Subcategory : bit (2) > } + { 0 -- Domain-specific access control for EAB not in use + | 1 -- Domain-specific access control for EAB in use + { 0 -- The previously listed PS EAB Authorization Mask/Subcategory apply + | 1 < PS EAB Authorization Mask : bit (10) > -- The indicated PS EAB Authorization +Mask/Subcategory apply + < PS EAB Subcategory : bit (2) > } + } +} * (val(Nb_Additional_PLMNs)+1); +``` + +**Table 10.5.2.37m.2: SI 21 Rest Octets information element** + +#### SI 21\_CHANGE\_MARK (2 bit) + +This field is changed each time the content of the SI 21 message changes. + +#### SI 21\_INDEX (3 bits) and SI 21\_COUNT (3 bits) + +The purpose of these fields is to indicate the number of individual message instances within the sequence of SI 21 messages and to assign an index to identify each instance. The SI 21\_INDEX field is binary coded, range 0 to 7, and provides an index to identify an individual SI 21 message instance. The SI 21\_COUNT field is binary coded, range 0 to 7, and provides the value of the highest indexed message instance in the sequence of SI 21 messages. + +#### EAB Authorization Mask (10 bit) + +This field is a bit map that provides the list of authorized access classes for mobile stations configured for Extended Access Barring. It allows for zero, one or more access classes to be indicated as authorized and is coded as follows: + +bit + +9 8 7 6 5 4 3 2 1 0 + +0 0 0 0 0 0 0 0 0 0 All mobile stations configured for EAB are authorized (i.e. no barring) + +x x x x x x x x x 1 Mobile stations configured for EAB and a member of Access Class 0 are barred + +x x x x x x x x 1 x Mobile stations configured for EAB and a member of Access Class 1 are barred + +x x x x x x x 1 x x Mobile stations configured for EAB and a member of Access Class 2 are barred + +..... + +1 x x x x x x x x x Mobile stations configured for EAB and a member of Access Class 9 are barred + +When network sharing is used, a mobile station supporting network sharing and configured for EAB shall consider this field applicable to the Common PLMN. + +**EAB Subcategory (2 bit)** + +This field identifies the targeted subcategory of mobile stations configured for EAB. It is coded as follows: + +- | | | +|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | The EAB Authorization mask is applicable to all mobile stations configured for EAB. | +| 01 | The EAB Authorization mask is only applicable to mobile stations configured for EAB and neither in their HPLMN nor in a PLMN that is equivalent to it (see TS 22.011). | +| 10 | The EAB Authorization mask is only applicable to mobile stations configured for EAB and neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in an PLMN that is equivalent to it (see TS 22.011). | + +All other values are unused. Upon receiving a value it considers to be unused, a mobile station configured for EAB shall ignore it and shall consider itself as not being part of the targeted subcategory. + +When network sharing is used, a mobile station supporting network sharing and configured for EAB shall consider this field applicable to the Common PLMN. + +**Nb\_Additional\_PLMNs (2 bit)** + +This field indicates the number of Additional PLMN for which EAB information is provided. It is coded as the Nb\_Additional\_PLMNs field in table 10.5.2.37n.1. The value of this field shall be equal to that of the Nb\_Additional\_PLMNs field broadcast in the SYSTEM INFORMATION TYPE 22 message. + +**Common PLMN PS EAB Authorization Mask (10 bit) and Common PLMN PS EAB Subcategory (2 bit)** + +These fields contain the EAB Authorization Mask/Subcategory applicable to the Common PLMN for the PS domain when domain-specific access control for EAB is used. In the absence of these fields, the mobile station shall consider domain-specific access control for EAB as not used for the Common PLMN. These fields are coded as specified for the EAB Authorization Mask/Subcategory fields. + +**Additional EAB Authorization Mask (10 bit) and Additional EAB Subcategory (2 bit)** + +These fields contain the EAB Authorization Mask/Subcategory applicable in the corresponding Additional PLMN. In the absence of these fields, the previously listed Additional EAB Authorization Mask/Subcategory fields in this message shall be used instead (see sub-clause 3.8.3), or if no such fields exist, the EAB Authorization Mask/Subcategory fields shall apply. If domain-specific access control for EAB is used for this Additional PLMN, these fields (and absence thereof) apply to CS domain only, otherwise to both CS and PS domains. These fields are coded as specified for the EAB Authorization Mask/Subcategory fields. + +**PS EAB Authorization Mask (10 bit) and PS EAB Subcategory (2 bit)** These fields contain the EAB Authorization Mask/Subcategory applicable in the corresponding Additional PLMN for the PS domain when domain-specific access control for EAB is used. In the absence of these fields and if domain-specific access control is indicated as used for this Additional PLMN, the previously listed PS EAB Authorization Mask/Subcategory fields in this message shall be used instead (see sub-clause 3.8.3), or if no such fields exist, the Common PS EAB Authorization Mask/Subcategory fields shall apply. These fields are coded as specified for the EAB Authorization Mask/Subcategory fields. + +**10.5.2.37n SI 22 Rest Octets** + +The *SI 22 Rest Octets* information element contains network sharing and domain-specific access control information. + +The *SI 22 Rest Octets* information element is a type 5 information element with 20 octet length. + +Table 10.5.2.37n.1: SI 22 Rest Octets information element + +``` + +< SI 22 Rest Octets > ::= + + < SI 22_CHANGE_MARK : bit (2) > + < SI 22_INDEX : bit (3) > + < SI 22_COUNT : bit (3) > + { 0 | 1 < Network Sharing Information : < Network Sharing Information struct >> } + < spare padding > ; + +< Network Sharing Information struct > ::= + < SI23 Indicator : bit > + < Common_PLMN_Allowed : bit > + { 0 | 1 < Common_PLMN_PS_ACC : bit(16) > } + < Nb_Additional_PLMNs : bit (2) > + { 0 | 1 < MCC : bit (12) > } < MNC : bit (12) > + < NCC Permitted : bit (8) > + { 0 -- The previously listed Access Control Class bitmap applies + | 1 -- The indicated Access Control Class bitmap applies + < Additional_ACC: bit (16) > } + { 0 -- Domain-specific access control not in use + | 1 -- Domain specific access control in use + { 0 -- The previously listed PS Access Control Class bitmap applies + | 1 < PS_ACC: bit(16) > } -- The indicated PS Access Control Class bitmap applies + } +} * ( val (Nb_Additional_PLMNs)+1) ; + +``` + +Table 10.5.2.37n.2: SI 22 Rest Octets information element + +**SI 22\_CHANGE\_MARK (2 bit)** + +This field is changed each time the content of the SI 22 message changes. + +**SI 22\_INDEX (3 bits) and SI 22\_COUNT (3 bits)** + +The purpose of these fields is to indicate the number of individual message instances within the sequence of SI 22 messages and to assign an index to identify each instance. The SI 22\_INDEX field is binary coded, range 0 to 7, and provides an index to identify an individual SI 22 message instance. The SI 22\_COUNT field is binary coded, range 0 to 7, and provides the value of the highest indexed message instance in the sequence of SI 22 messages. + +**SI23 Indicator (one bit field)** + +This field indicates whether or not the SYSTEM INFORMATION TYPE 23 message is broadcast by the network. It is coded as follows: + +**Bit** + +- | | | +|---|----------------------------------------------------------| +| 0 | The SYSTEM INFORMATION TYPE 23 message is not available. | +| 1 | The SYSTEM INFORMATION TYPE 23 message is available. | + +**Common\_PLMN\_Allowed (one bit field)** + +This field indicates whether or not a MS supporting network sharing is allowed to select the Common PLMN. It is coded as follows: + +**Bit** + +- | | | +|---|--------------------------------------------------| +| 0 | The MS is not allowed to select the Common PLMN. | +| 1 | The MS is allowed to select the Common PLMN. | + +**Common\_PLMN\_PS\_ACC (16 bit field)** + +This field contains a bitmap indicating the barring status for access control classes 0 to 15 (AC C0 to AC C15), applicable to the Common PLMN for the PS domain when domain-specific access control is used. Each AC CN is coded as the AC CN in the *RACH Control Parameters* IE (see sub-clause 10.5.2.29). In the absence of this field, the mobile station shall consider domain-specific access control as not used for the Common PLMN. The Common\_PS\_ACC field is coded as follows. + +**Bits** + +| | | | | +|----|----|-----|---| +| 15 | 14 | ... | 0 | +|----|----|-----|---| + +| | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-----|---|--------|--------|-----|-------| +| x | x | ... | x | AC C15 | AC C14 | ... | AC C0 | +| Nb_Additional_PLMNs (2 bit field)
This field indicates the number of Additional PLMN IDs broadcast in the SI22 message. It is coded as follows:
Value
0 0 a single Additional PLMN ID is broadcast
0 1 2 Additional PLMN IDs are broadcast
1 0 3 Additional PLMN IDs are broadcast
1 1 4 Additional PLMN IDs are broadcast | | | | | | | | +| MCC and MNC (24 bit field)
This field contains the PLMN ID for each Additional PLMN. If for a given MNC the MCC field is missing, the previously listed MCC in this message shall be used instead (see sub-clause 3.8.3), or if no such exists, the MCC provided as part of the Location Area Identification IE in SI3 and SI4 shall be used instead.
The MCC and MNC value field is coded as specified in sub-clause 10.5.3. | | | | | | | | +| NCC Permitted (8 bit field) The purpose of this field is to provide for each Additional PLMN the list of allowed NCCs on the BCCH carriers to be reported in the MEASUREMENT REPORT message by the mobile station in the cell.
The NCC Permitted value field is coded as the value part of the NCC Permitted IE specified in sub-clause 10.5.2.27 | | | | | | | | +| Additional_ACC (16 bit field)
This field contains a bitmap indicating the barring status for access control classes 0 to 15 (AC C0 to AC C15), applicable in the corresponding Additional PLMN. Each AC CN is coded as the AC CN in the RACH Control Parameters IE (see sub-clause 10.5.2.29). In the absence of this field, the previously listed Additional_ACC field in this message shall be used instead (see sub-clause 3.8.3), or if no such field exists, the AC CN in the RACH Control Parameters IE shall apply. If domain-specific access control is used for this Additional PLMN, this field (and absence thereof) applies to CS domain only, otherwise to both CS and PS domains. The Additional_ACC field is coded as follows.
Bits
15 14 ... 0
x x ... x AC C15 AC C14 ... AC C0 | | | | | | | | +| PS_ACC (16 bit field)
This field contains a bitmap indicating the barring status for access control classes 0 to 15 (AC C0 to AC C15), applicable in the corresponding Additional PLMN for the PS domain when domain-specific access control is used. Each AC CN is coded as the AC CN in the RACH Control Parameters IE (see sub-clause 10.5.2.29). In the absence of this field and if domain-specific access control is indicated as used for this Additional PLMN, the previously listed PS_ACC field in this message shall be used instead (see sub-clause 3.8.3), or if no such field exists, the Common_PLMN_PS_ACC field shall apply. The PS_ACC field is coded as follows.
Bits
15 14 ... 0
x x ... x AC C15 AC C14 ... AC C0 | | | | | | | | + +### 10.5.2.37o SI 23 Rest Octets + +The *SI 23 Rest Octets* information element contains inter RAT cell reselection information related to network sharing. + +The *SI 23 Rest Octets* information element is a type 5 information element with 20 octet length. + +**Table 10.5.2.37o.1: SI 23 Rest Octets information element** + +``` + +< SI 23 Rest Octets > ::= + < SI 23_BA_IND : bit (1) > + < SI 23_CHANGE_MARK : bit (2) > + < SI 23_INDEX : bit (3) > + < SI 23_COUNT : bit (3) > + { 0 | 1 < IRAT Cell Reselection Information : < IRAT Cell Reselection Information struct >> } + < spare padding > ; + +< IRAT Cell Reselection Information struct > ::= + { < Priority and UTRAN Parameters Description for the Common PLMN : + < Priority and UTRAN Parameters Description struct >> } + { < Priority and E-UTRAN Parameters Description for the Common PLMN : + < Priority and E-UTRAN Parameters Description struct >> } + < Nb_Additional_PLMNs : bit (2) > + { < PLMN index : bit (2) > + { < Priority and UTRAN Parameters Description : + < Priority and UTRAN Parameters Description struct >> } + { < Priority and E-UTRAN Parameters Description : + < Priority and E-UTRAN Parameters Description struct >> } + } * ( val (Nb_Additional_PLMNs)+1) ; + +< Priority and UTRAN Parameters Description struct > ::= +{ 0 -- Inter RAT Cell Reselection information for UTRAN not provided for the corresponding PLMN + | 1 + { 0 -- UTRAN default threshold information not provided for the corresponding PLMN + | 1 + { 0 | 1 < DEFAULT_UTRAN_PRIORITY : bit(3) > } + { 0 | 1 < DEFAULT_THRESH_UTRAN_low : bit(5) > } + { 0 | 1 < DEFAULT_UTRAN_QRXLEVMIN : bit(5) > } + { 0 | 1 < UTRAN FDD/TDD Description : < UTRAN FDD/TDD Description struct >> } + } ; + +< UTRAN FDD/TDD Description struct > ::= + {{ 0 | 1 < Bandwidth_FDD : bit (3) > } { 0 | 1 < Bandwidth_TDD : bit (3) > }} + { 1 < Repeated UTRAN FDD/TDD Neighbour Frequency and Priority : + < Repeated UTRAN FDD/TDD Neighbour Frequency and Priority struct >> } ** 0 ; + +< Repeated UTRAN FDD/TDD Neighbour Frequency and Priority struct > ::= + { 1 < UTRAN-ARFCN : bit (14) > } ** 0 + { 0 | 1 < UTRAN_PRIORITY : bit(3) > } + < THRESH_UTRAN_high : bit(5) > + { 0 | 1 < THRESH_UTRAN_low : bit(5) > } + { 0 | 1 < UTRAN_QRXLEVMIN : bit(5) > } ; + +< Priority and E-UTRAN Parameters Description struct > ::= +{ 0 -- Inter RAT Cell Reselection information for E-UTRAN not provided for the corresponding PLMN + | 1 + { 0 -- E-UTRAN threshold information not provided for the corresponding PLMN + | 1 + { 0 | 1 < DEFAULT_E-UTRAN_PRIORITY : bit(3) > } + { 0 | 1 < DEFAULT_THRESH_E-UTRAN_low : bit(5) > } + { 0 | 1 < DEFAULT_E-UTRAN_QRXLEVMIN : bit(5) > } + { 1 < Repeated E-UTRAN Neighbour Frequency and Priority : < Repeated E-UTRAN Neighbour Frequency and + Priority struct >> } ** 0 + { 1 < Repeated E-UTRAN Not Allowed Cells : < Repeated E-UTRAN Not Allowed Cells struct >> } ** 0 + { 1 < Repeated E-UTRAN PCID to TA mapping : < Repeated E-UTRAN PCID to TA mapping struct >> } ** 0 + { 0 | 1 < Enhanced Cell Reselection Parameters Description : < Enhanced Cell Reselection Parameters IE >> } + } ; + +``` + +``` + +< Repeated E-UTRAN Neighbour Frequency and Priority struct > ::= + { 1 < EARFCN_extended : bit (18) > + { 0 | 1 < Measurement Bandwidth : bit (3) > }} ** 0 + { 0 | 1 < E-UTRAN_PRIORITY : bit(3) > } + < THRESH_E-UTRAN_high : bit(5) > + { 0 | 1 < THRESH_E-UTRAN_low : bit(5) > } + { 0 | 1 < E-UTRAN_QRXLEVMIN : bit(5) > }; + +``` + +**Table 10.5.2.37o.2: SI 23 Rest Octets information element** + +**SI 23\_BA\_IND** (1 bit), 3G BCCH allocation sequence number indication. +The SI 23\_BA\_IND is needed to indicate new sets of Priority and E-UTRAN Parameters Description. The value received is reflected in the MEASUREMENT REPORT and ENHANCED MEASUREMENT REPORT messages. + +**SI 23\_CHANGE\_MARK** (2 bit) +This field is changed each time the content of the SI 23 message changes. + +**SI 23\_INDEX** (3 bits) and **SI 23\_COUNT** (3 bits) +The purpose of these fields is to indicate the number of individual message instances within the sequence of SI 23 messages and to assign an index to identify each instance. The SI 23\_INDEX field is binary coded, range 0 to 7, and provides an index to identify an individual SI 23 message instance. The SI 23\_COUNT field is binary coded, range 0 to 7, and provides the value of the highest indexed message instance in the sequence of SI 23 messages. + +***IRAT Cell Reselection Information:*** +Provides the information related to inter RAT Cell Reselection on a PLMN basis. The number of UTRAN/E-UTRAN frequencies broadcast by the network shall be in line with the monitoring requirements listed within 3GPP TS 45.008. This information supersedes the corresponding information provided within SI2ter/SI2quater messages. + +***Priority and UTRAN Parameters Description for the Common PLMN:*** +Provides the *Priority and UTRAN Parameters Description* for the Common PLMN. This information shall be provided by the network only if MS supporting Network Sharing are allowed to select the Common PLMN (i.e. the Common PLMN corresponds to a single Core Network Operator) and inter RAT cell reselection to UTRAN has to be managed for the Common PLMN. + +***Priority and E-UTRAN Parameters Description for the Common PLMN:*** +Provides the *Priority and E-UTRAN Parameters Description* for the Common PLMN. This information shall be provided by the network only if MS supporting Network Sharing are allowed to select the Common PLMN (i.e. the Common PLMN corresponds to a single Core Network Operator) and inter RAT cell reselection to E-UTRAN has to be managed for the Common PLMN. + +**Nb\_Additional\_PLMNs** (2 bit) +This field indicates the number of Additional PLMNs for which inter RAT Mobility information is provided in the SYSTEM INFORMATION TYPE 23 message. It is coded as the Nb\_Additional\_PLMNs field in table 10.5.2.37n.1. The value of this field shall be equal to that of the Nb\_Additional\_PLMNs field broadcast in the SYSTEM INFORMATION TYPE 22 message. + +**PLMN Index** (2 bit) +This field indicates the Additional PLMN ID for which inter RAT Mobility information is provided. It is coded as follows: + +Value + +| | | +|-----|---------------------------| +| 0 0 | First Additional PLMN ID | +| 0 1 | Second Additional PLMN ID | +| 1 0 | Third Additional PLMN ID | +| 1 1 | Fourth Additional PLMN ID | + +***Priority and UTRAN Parameters Description:*** +Provides the *Priority and UTRAN Parameters Description* for the PLMN corresponding to *PLMN\_Index*. + +***Priority and E-UTRAN Parameters Description:*** +Provides the *Priority and E-UTRAN Parameters Description* for the PLMN corresponding to *PLMN\_Index*. + +**Priority and UTRAN Parameters Description:** + +Provides for a given PLMN the information related to UTRAN frequencies. + +**DEFAULT\_UTRAN\_PRIORITY** (3 bit) + +**DEFAULT\_THRESH\_UTRAN\_low** (5 bit) + +**DEFAULT\_UTRAN\_QRXLEVMIN** (5 bit) + +These fields provide default values in the case the corresponding UTRAN\_PRIORITY, THRESH\_UTRAN\_low, UTRAN\_QRXLEVMIN fields are not broadcast within the *UTRAN FDD/TDD Description* applicable to this PLMN. + +**UTRAN\_FDD/TDD Description:** + +**BANDWIDTH\_FDD** (3 bit) + +**BANDWIDTH\_TDD** (3 bit) + +See table 10.5.2.33b.2 + +**Repeated UTRAN FDD/TDD Neighbour Frequency and Priority** + +See table 10.5.2.33b.2 for all corresponding fields. It is not allowed to mix FDD and TDD UTRAN ARFCNs within this description. + +**Priority and E-UTRAN Parameters Description:** + +Provides for a given PLMN the information related to E-UTRAN frequencies. + +**DEFAULT\_E-UTRAN\_PRIORITY** (3 bit) + +**DEFAULT\_THRESH\_E-UTRAN\_low** (5 bit) + +**DEFAULT\_E-UTRAN\_QRXLEVMIN** (5 bit) + +These fields provide default values in the case the corresponding E-UTRAN\_PRIORITY, THRESH\_E-UTRAN\_low, E-UTRAN\_QRXLEVMIN fields are not broadcast within the *Repeated E-UTRAN Neighbour Frequency and Priority* applicable to this PLMN. + +**Repeated E-UTRAN Neighbour Frequency and Priority:** + +See table 9.1.54.1 for the definition of the *EARFCN\_extended* field. + +See table 10.5.2.33b.2 for all remaining fields + +**Repeated E-UTRAN Not Allowed Cells:** + +See table 10.5.2.33b.2 for all corresponding fields. + +**Repeated E-UTRAN PCID to TA mapping:** + +See table 10.5.2.33b.2 for all corresponding fields. + +**Enhanced Cell Reselection Parameters Description:** + +See table 10.5.2.33b.2. + +## 10.5.2.38 Starting Time + +The purpose of the *Starting Time* information element is to provide the start TDMA frame number, FN modulo 42432. + +The *Starting Time* information element is coded as shown in figure 10.5.2.38.1 and table 10.5.2.38.1. + +The *Starting Time* is a type 3 information element with 3 octets length. + +![](210d8cabb9882dcd63f42b38f4f2a414_img.jpg) + +| | | | | | | | | | +|-------------------|---|---|---|-------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Starting Time IEI | | | | | | | | octet 1 | +| T1' | | | | T3
(high part) | | | | octet 2 | +| T3
(low part) | | | | | | | | octet 3 | + +**Figure 10.5.2.38.1: Starting Time information element** + +**Table 10.5.2.38.1: Starting Time information element** + +T1' (octet 2) + The T1' field is coded as the binary representation of (FN div 1326) mod 32. + +T3 (octet 2 and 3) + The T3 field is coded as the binary representation of FN mod 51. Bit 3 of octet 2 is the most significant bit and bit 6 of octet 3 is the least significant bit. + +T2 (octet 3) + The T2 field is coded as the binary representation of FN mod 26. + +NOTE 1: The frame number, FN modulo 42432 can be calculated as $51 \times ((T3 - T2) \bmod 26) + T3 + 51 \times 26 \times T1'$ + +The starting time and the times mentioned above are with reference to the frame numbering in the concerned cell. They are given in units of frames (around 4.615 ms). + +The *Starting Time* IE can encode only an interval of time of 42 432 frames, that is to say around 195.8 seconds. To remove any ambiguity, the specification for a reception at time T is that the encoded interval is (T-10808, T+31623). In rigorous terms, if we note ST the starting time: + +if $0 \leq (ST - T) \bmod 42432 \leq 31623$ , the indicated time is the next time when FN mod 42432 is equal to ST; + +if $32024 \leq (ST - T) \bmod 42432 \leq 42431$ , the indicated time has already elapsed. + +The reception time T is not specified here precisely. To allow room for various MS implementations, the limit between the two behaviours above may be anywhere within the interval defined by: + +$31624 \leq (ST - T) \bmod 42432 \leq 32023$ . + +### 10.5.2.39 Synchronization Indication + +The purpose of *Synchronization Indication* information element is to indicate which type of handover is to be performed. + +The *Synchronization Indication* information element is coded as shown in figure 10.5.2.39.1 and table 10.5.2.39.1. + +The *Synchronization Indication* is a type 1 information element. + +![](9531814db23e3f45bf99c865df5ae152_img.jpg) + +| | | | | | | | | | +|-------------------|---|---|---|-----|-----|----|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Synch. Indic. IEI | | | | NCI | ROT | SI | | | + +**Figure 10.5.2.39.1: Synchronization Indication information element** + +**Table 10.5.2.39.1: Synchronization Indication information element** + +ROT: Report Observed Time Difference (Octet1 bit 3) + +0 Mobile Time Difference IE and Mobile Time Difference on Hyperframe level IE shall not be included in the HANDOVER COMPLETE message + +1 Mobile Time Difference IE and Mobile Time Difference on Hyperframe level IE shall be included in the HANDOVER COMPLETE message + + + +SI: Synchronization indication (octet 1) + +Bit + +| | | | +|----------|----------|---------------------| +| 2 | 1 | | +| 0 | 0 | Non-synchronized | +| 0 | 1 | Synchronized | +| 1 | 0 | Pre-synchronised | +| 1 | 1 | Pseudo-synchronised | + + + +NCI: Normal cell indication (octet 1, bit 4) + +0 Out of range timing advance is ignored + +1 Out of range timing advance shall trigger a handover failure procedure + +### 10.5.2.40 Timing Advance + +The purpose of the *Timing Advance* information element is to provide the timing advance value. + +The *Timing Advance* information element is coded as shown in figure 10.5.2.40.1 and table 10.5.2.40.1 + +The *Timing Advance* is a type 3 information element with 2 octets length. + +![](790afbbc0b2f0aea6683499c6ef46e62_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------|---|---|---|---|---|---|---|---------| +| Timing Advance IEI | | | | | | | | octet 1 | +| Timing advance value | | | | | | | | octet 2 | + +**Figure 10.5.2.40.1: *Timing Advance* information element** + +**Table 10.5.2.40.1: *Timing Advance* information element** + +``` +Timing advance value (octet 2) +The coding of the timing advance value field is the binary representation of the +timing advance in bit periods; 1 bit period = 48/13 µs. + +For all the bands except GSM 400, the values 0 - 63 are valid TA values, and bit 7 +and bit 8 are set to spare. For GSM 400, the values 0 to 219 are valid TA values. +The remaining values 220 to 255 decimal are reserved. +``` + +### 10.5.2.41 Time Difference + +The purpose of the *Time Difference* information element is to provide information about the synchronization difference between the time bases of two Base Stations. This type of information element is used in relation with the pseudo-synchronization scheme, see 3GPP TS 45.010. + +The *Time Difference* information element is coded as shown in figure 10.5.2.41.1 and table 10.5.2.41.1. + +The *Time Difference* information element is a type 4 information element with 3 octets length. + +![](5446143e3814eda7fa1049af15fc7683_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---------------------|---|---|---|---|---|---|---------| +| | Time Difference IEI | | | | | | | octet 1 | +| Length of Time Difference contents | | | | | | | | octet 2 | +| Time difference value | | | | | | | | octet 3 | + +**Figure 10.5.2.41.1: *Time Difference* information element** + +**Table 10.5.2.41.1: *Time Difference* information element** + +``` +Time Difference value (octet 3) +The coding of the time difference value field is the binary representation of time +difference in half bit periods, modulo 256 half bit periods; 1/2 bit period = 24/13 µs. +``` + +### 10.5.2.41a TLLI + +The purpose of the *TLLI* information element is to provide the Temporary Logical Link Identifier. + +The *TLLI* information element is coded as shown in figure 10.5.2.41a.1 and table 10.5.2.41a.1. + +The *TLLI* is a type 3 information element with 5 octets length. + +![](09b293b3a4cad7c80f5a38a935442fcf_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|----------|---|---|---|---|---|---|---------| +| | TLLI IEI | | | | | | | octet 1 | +| TLLI value | | | | | | | | octet 2 | +| TLLI value (contd) | | | | | | | | octet 3 | +| TLLI value (contd) | | | | | | | | octet 4 | +| TLLI value (contd) | | | | | | | | octet 5 | + +**Figure 10.5.2.41a.1: *TLLI* information element** + +**Table 10.5.2.41a.1: TLLI information element** + +TLLI value (octet 2, 3, 4 and 5) + Bit 8 of octet 2 is the most significant bit and bit 1 of octet 5 is the least significant bit. + The TLLI is encoded as a binary number with a length of 4 octets. TLLI is defined in 3GPP TS 23.003 + +## 10.5.2.42 TMSI/P-TMSI + +The purpose of the *TMSI/P-TMSI* information element is to provide the Temporary Mobile Subscriber Identity for paging purposes. + +The *TMSI/P-TMSI* information element is coded as shown in figure 10.5.2.42.1 and table 10.5.2.42.1. + +The *TMSI/P-TMSI* is a type 3 information element with 5 octets length. + +![](357536e18f2ad306db16dc51ab0bb30b_img.jpg) + +| | | | | | | | | | +|---------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TMSI/P-TMSI IEI | | | | | | | | octet 1 | +| TMSI/P-TMSI value | | | | | | | | octet 2 | +| TMSI/P-TMSI value (contd) | | | | | | | | octet 3 | +| TMSI/P-TMSI value (contd) | | | | | | | | octet 4 | +| TMSI/P-TMSI value (contd) | | | | | | | | octet 5 | + +**Figure 10.5.2.42.1: TMSI/P-TMSI information element****Table 10.5.2.42.1: TMSI/P-TMSI information element** + +**TMSI/P-TMSI value** (octet 2, 3, 4 and 5) + Bit 8 of octet 2 is the most significant bit and bit 1 of octet 5 is the least significant bit. + +The coding of the TMSI/P-TMSI is left open for each administration according to 3GPP TS 23.003. The length is 4 octets. + +NOTE: For purposes other than paging the TMSI/P-TMSI should be provided using the mobile identity information element. + +## 10.5.2.42a VGCS target mode Indication + +The *VGCS target mode Indication* information element is a type 3 information element with 3 octets length. + +![](a81a31cf6a84e0a1f2f26e6fcad50e92_img.jpg) + +| | | | | | | | | | +|-----------------------------------|---|-------------------------|---|---|---|---------|---------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| VGCS target mode Indic. IEI | | | | | | | | octet 1 | +| Length of VGCS target mode Indic. | | | | | | | | octet 2 | +| Target mode | | Group cipher key number | | | | 1 spare | 1 spare | octet 3 | + +**Figure 10.5.2.42a.1: VGCS target mode Indication information element** + +**Table 10.5.2.42a.1: VGCS target mode information element** + +| | | | +|-------------------------------------------|---|-------------------------| +| Target mode (octet 3) | | | +| Bit | | | +| 8 | 7 | | +| 0 | 0 | dedicated mode | +| 0 | 1 | group transmit mode | +| Other values are reserved for future use. | | | +| Group cipher key number (octet 3) | | | +| Bit | | | +| 6 | 5 | 4 3 | +| 0 | 0 | 0 0 no ciphering | +| 0 | 0 | 0 1 cipher key number 1 | +| 0 | 0 | 1 0 cipher key number 2 | +| 0 | 0 | 1 1 cipher key number 3 | +| 0 | 1 | 0 0 cipher key number 4 | +| 0 | 1 | 0 1 cipher key number 5 | +| 0 | 1 | 1 0 cipher key number 6 | +| 0 | 1 | 1 1 cipher key number 7 | +| 1 | 0 | 0 0 cipher key number 8 | +| 1 | 0 | 0 1 cipher key number 9 | +| 1 | 0 | 1 0 cipher key number A | +| 1 | 0 | 1 1 cipher key number B | +| 1 | 1 | 0 0 cipher key number C | +| 1 | 1 | 0 1 cipher key number D | +| 1 | 1 | 1 0 cipher key number E | +| 1 | 1 | 1 1 cipher key number F | + +### 10.5.2.42b VGCS Ciphering Parameters + +The *VGCS Ciphering parameters* information element is a type 4 information element with 3-15 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +|-------------------------------------|---|--------------|-------------|--------------|--------------|-----------------------|---|------------------------------------|--|--| +| VGCS Ciphering Parameters IEI | | | | | | | | octet 1 | | | +| Length of VGCS Ciphering Parameters | | | | | | | | octet 2 | | | +| Spare | | RAND_I
ND | LAC_I
ND | CELL_I
ND | B22
COUNT | CELL_GLOBAL_CO
UNT | | octet 3 | | | +| Cell Identity | | | | | | | | Octet
4(Optional) | | | +| Location Area Identification | | | | | | | | Octet 5
Octet m
(optional) | | | +| VSTK_RAND | | | | | | | | Octet m+4
Octet n
(Optional) | | | +| VSTK_RAND | | | | | | | | | | | +| VSTK_RAND | | | | | | | | | | | +| VSTK_RAND | | | | | | | | | | | +| VSTK_RAND | | | | Spare | | | | Octet n + 4
(Optional) | | | + +**Figure 10.5.2.42b.1: VGCS Ciphering Parameters Information Element** + +**Table 10.5.2.42b.1: VGCS Ciphering Parameters Information Element** + +CELL\_GLOBAL\_COUNT (octet 3) + +B22\_COUNT (octet 3) + +This field contains the value of bit 22 of COUNT (see 3GPP TS43.020) corresponding to the moment when the value of was valid. + +CELL\_IND (Octet 3) + Bit + 0 Cell Identification not present + 1 Cell Identification present + +LAC\_IND (Octet 3) + Bit + 0 Location Area Identification not present + 1 Location Area Identification present + +RAND\_IND (Octet 3) + Bit + 0 VSTK\_RAND not present + 1 VSTK\_RAND present + +Cell Identity (octets 4 and 5) + The purpose of the Cell Identity is to identify a cell within a location area (see sub-clause 10.5.1.1). + +Location Area Identification (octets m to m+4) + The purpose of the Location Area Identification is to provide the identity of the location area. The Location Area Identification is coded as in sub-clause 9.1.40.2. + +VSTK\_RAND (octets n to n+4) + The purpose of this field is to provide the VSTK\_RAND, as defined in 3GPP TS 43.020. + +### 10.5.2.43 Wait Indication + +The purpose of the *Wait Indication* information element is to provide the time the mobile station shall wait before attempting another channel request. + +The *Wait Indication* information element is coded as shown in figure 10.5.2.43.1 and table 10.5.2.43.1. + +The *Wait Indication* is a type 3 information element with 2 octets length. + +![](ecc2b08e0d193ae74ff8a8241a83fb01_img.jpg) + +| | | | | | | | | | +|---------------------------|---------------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | Wait Indication IEI | | | | | | | octet 1 | +| T3122/T3142 timeout value | | | | | | | | octet 2 | + +**Figure 10.5.2.43.1: Wait Indication information element****Table 10.5.2.43.1: Wait Indication information element** + +T3122/T3142 timeout value (octet 2) + This field is coded as the binary representation of the T3122/T3142 timeout value in seconds. + +NOTE: The timeout value is used for T3122 when received in IMMEDIATE\_ASSIGNMENT REJECT message for RR connection establishment. For GPRS MS the timeout value is used for T3142 when received in the IMMEDIATE ASSIGNMENT REJECT or DTM REJECT message for TBF establishment. + +### 10.5.2.44 SI10 rest octets \$(ASCII)\$ + +The *SI 10 rest octets* information element contains information for cell re-selection in group receive mode. + +The *SI 10 Rest Octets* information element is a type 5 information element with 20 octets length. + +The value part is coded as shown below. + +**Table 10.5.2.44.1: SI 10 Rest Octets information element** + +``` + + ::= + { L | H }; + + ::= + { H }** L ; + + ::= { H | L }; + + ::= | L ; + + ::= H; + + ::= + + + + + ; + + ::= { H | L }; + + ::= ** L ; + + ::= H; + + ::= { H | L } + { H | L }; + + ::= | L ; + + ::= + { H | L } + { H | L } + { H | L } + { H | L } + { H | L }; + +``` + +**Static and dynamic conditions:** + +- 1) Information from the last received neighbour cell description in SYSTEM INFORMATION TYPE 5/5bis/5ter is necessary for the mobile station to interpret . If is different from the last received BA IND value indicated in SYSTEM INFORMATION TYPE 5/5bis/5ter, cannot be interpreted by the mobile station. +- 2) If the correspondence between neighbour cell frequencies and sets of pairs (BSIC, cell information) cannot be established following the rules below, or if more than one set of such pairs corresponds to one neighbour cell frequency, the mobile station shall diagnose an imperative message part error. + +**Attributes, field contents:** + +- 1) defines a BSIC given by . It also defines cell information. If is contained in , this cell information is the cell information given by ; if is not contained in , this cell information is empty. +- 2) defines a BSIC given by or by , see below. It also defines cell information. If is contained in , this cell information is the cell information given by ; if is not contained in , this cell information is empty. +- 3) either indicates a barred cell (by presence of ) or specifies cell information given by . +- 4) Each occurrence of either indicates a barred cell (by presence of ) or specifies cell information given by . + +5) specifies cell information given by its components: + +- ; +- ; +- ; +- ; +- ; +- ; + +as defined below. + +6) For each occurrence of , a cell information is defined. This information is given by and remaining cell information established as follows: + +The remaining cell information defined for the first occurrence of consists of the cell information given by its actual components plus the cell information specified by corresponding to its missing components. + +The remaining cell information defined for a later occurrence of consists of the cell information given by its actual components plus the remaining cell information corresponding to its missing components which is defined for the previous occurrence of . + +Here, the + +"actual components" of an occurrence of denotes those parameters among: + +- ; +- ; +- ; +- ; +- ; + +which are present in that occurrence. + +"missing components" of an occurrence of denote those parameters among: + +- ; +- ; +- ; +- ; +- ; + +which are not present in that occurrence. + +7) Each occurrence of specifies a BSIC by encoding its binary representation. specifies a BCC by encoding its binary representation; it specifies the BSIC given by that BCC and the NCC of the BSIC specified by the previous occurrence of or . All occurrences of and establish a list of BSIC. + +8) is the 5 bit binary coding of an integer $n$ with $0 \leq n \leq 31$ . It specifies a first frequency number $n+1$ . + +9) defines a correspondence between neighbour cell frequencies and sets of pairs (BSIC, cell information) defining the parameters for cell re-selection of any corresponding neighbour cell with BCCH on that frequency and having that BSIC: + +- Let $a(1), \dots, a(n)$ be the list of neighbour cell frequencies, in the order determined by the mobile station. Let $i$ be the first frequency number specified by (see above). + - The first BSIC and the cell information specified by build a pair belonging to the set corresponding to $a(i)$ . + - If an $m$ -th occurrence of is present (where $m \geq 2$ ), having established the correspondence of the $(m-1)$ -th BSIC to a neighbour frequency $a(k)$ , the $m$ -th BSIC and following : + - belong to $a(k)$ , if is not present in the $m$ -th occurrence of ; + - belong to $a((smod(k+t)))$ , if is present exactly $t$ times in the $m$ -th occurrence of . + - Here, for an integer $j$ , $smod(j) := ((j-1) \bmod n) + 1$ . +- 10) If contains a , this means that the cell is to be considered by the mobile station to belong to a different location area and that for the cell, the cell reselect hysteresis specified in applies. +- 11) If doesn't contain a , this means that the cell is to be considered by the mobile station to belong to the same location area. +- 12) For : see sub-clause 10.5.2.4. +- 13) For : see sub-clause 10.5.2.4. +- 14) For see sub-clause 10.5.2.4. +- 15) For : see sub-clause 10.5.2.35. +- 16) For : see sub-clause 10.5.2.35. +- 17) For : see sub-clause 10.5.2.35. + +## 10.5.2.45 EXTENDED MEASUREMENT RESULTS + +The purpose of the *Extended Measurement Results* information element is to provide the results of the measurements made by the mobile station on the carriers specified in the EXTENDED MEASUREMENT ORDER. + +The *Extended Measurement Results* information element is coded as shown in figure 10.5.2.45.1 and table 10.5.2.45.1. + +The *Extended Measurement Results* is a type 3 information element with 17 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|-----------------------------|----------------------------------|------------------|------------------------------|---|------------------------------|---|---|----------|--|--|--| +| | Extended Measurement Results IEI | | | | | | | octet 1 | | | | +| SC USED | DTX USED | RXLEV carrier 0 | | | | | | octet 2 | | | | +| RXLEV carrier 1 | | | | | RXLEV carrier 2 (high part) | | | octet 3 | | | | +| RXLEV carrier 2 (low part) | | | RXLEV carrier 3 (high part) | | | | | octet 4 | | | | +| RXLEV carrier 3 (low part) | | RXLEV carrier 4 | | | | | | octet 5 | | | | +| RXLEV carrier 5 | | | | | RXLEV carrier 6 (high part) | | | octet 6 | | | | +| RXLEV carrier 6 (low part) | | | RXLEV carrier 7 (high part) | | | | | octet 7 | | | | +| RXLEV carrier 7 (low part) | | RXLEV carrier 8 | | | | | | octet 8 | | | | +| RXLEV carrier 9 | | | | | RXLEV carrier 10 (high part) | | | octet 9 | | | | +| RXLEV carrier 10 (low part) | | | RXLEV carrier 11 (high part) | | | | | octet 10 | | | | +| RXLEV carrier 11 (low part) | | RXLEV carrier 12 | | | | | | octet 11 | | | | +| RXLEV carrier 13 | | | | | RXLEV carrier 14 (high part) | | | octet 12 | | | | +| RXLEV carrier 14 (low part) | | | RXLEV carrier 15 (high part) | | | | | octet 13 | | | | +| RXLEV carrier 15 (low part) | | RXLEV carrier 16 | | | | | | octet 14 | | | | +| RXLEV carrier 17 | | | | | RXLEV carrier 18 (high part) | | | octet 15 | | | | +| RXLEV carrier 18 (low part) | | | RXLEV carrier 19 (high part) | | | | | octet 16 | | | | +| RXLEV carrier 19 (low part) | | RXLEV carrier 20 | | | | | | octet 17 | | | | + +**Figure 10.5.2.45.1: Extended Measurement Results information element** + +**Table 10.5.2.45.1: Extended Measurement Results information element details** + +**SC USED** (octet 2), indicates the value of the SEQ-CODE in the extended measurement frequency list information element used for defining the list of frequencies reported on. + +Range: 0 to 1. + +**DTX USED** (octet 2). + +This bit indicates whether or not the mobile station used DTX during the previous measurement period. + +Bit 7 + +0 DTX was not used + +1 DTX was used + +**RXLEV carrier 'N' (octets 2 to 17).** + +This field is coded as the binary representation of a value M. M corresponds according to the mapping defined in 3GPP TS 45.008 to the received signal strength on carrier N. N is the index to the frequency in the sorted list of frequencies defined in the EXTENDED MEASUREMENT ORDER message. The list is sorted in increasing order of ARFCN, except that ARFCN 0, if included in the EXTENDED MEASUREMENT ORDER, is put in the last position of the sorted list. If the EXTENDED MEASUREMENT ORDER contains more than 21 carriers, only the signal strength of the carriers 0-20 shall be measured and reported. + +Range: 0 to 63 + +If the EXTENDED MEASUREMENT ORDER message contains less than 21 carriers, the fields in the EXTENDED MEASUREMENT REPORT not referring to any specified carrier shall have RXLEV values set to zero. + +### 10.5.2.46 Extended Measurement Frequency List + +The purpose of *Extended Measurement Frequency List* information element is to provide the absolute radio frequency channel numbers of carriers to measure signal strength on. + +The *Extended Measurement Frequency List* information element is coded as the *Cell Channel Description* information element, as specified in sub-clause 10.5.2.1b, with the exception of bit 5 of octet 2. Figure 10.5.2.46.1 and table 10.5.2.46.1: contains the difference of specifications. + +The *Extended Measurement Frequency List* information element is a type 3 information element with 17 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------|-----------------------------------------|---------|----------|---------|---------|---------|---------|----------| +| | Extended Measurement Frequency List IEI | | | | | | | octet 1 | +| Bit 128 | Bit 127 | 0 spare | SEQ-CODE | Bit 124 | Bit 123 | Bit 122 | Bit 121 | octet 2 | +| Bit 120 | Bit 119 | Bit 118 | Bit 117 | Bit 116 | Bit 115 | Bit 114 | Bit 113 | octet 3 | +| ⋮ | | | | | | | | | +| Bit 008 | Bit 007 | Bit 006 | Bit 005 | Bit 004 | Bit 003 | Bit 002 | Bit 001 | octet 17 | + +**Figure 10.5.2.46.1: *Extended Measurement Frequency List* information element** + +**Table 10.5.2.46.1: *Extended Measurement Frequency List* information element details** + +| | +|-------------------------------------------------------------------| +| SEQ-CODE, Sequence code (octet 2, bit 5).
Range 0 to 1. | +|-------------------------------------------------------------------| + +### 10.5.2.47 Suspension Cause + +The purpose of the *Suspension Cause* information element is to provide the reason for the GPRS suspension. + +The *Suspension Cause* information element is coded as shown in figure 10.5.2.47.1 and table 10.5.2.21aa.1. + +The *Suspension Cause* is a type 3 information element with 2 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|----------------------|---|---|---|---|---|---|---------| +| | Suspension Cause IEI | | | | | | | octet 1 | +| Suspension cause value | | | | | | | | octet 2 | + +**Figure 10.5.2.47.1: *Suspension Cause* information element** + +**Table 10.5.2.21aa.1: Suspension Cause information element** + +| Suspension cause value (octet 2) | | | | | | | | | +|----------------------------------|---|---|---|---|---|---|---|------------------------------------------------------------------| +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Emergency call, mobile originating call or call re-establishment | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Location Area Update | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | MO Short message service (note 1) | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | Other procedure which can be completed with an SDCCH | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | MO Voice broadcast or group call (note 2) | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Mobile terminating CS connection | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | DTM not supported in the cell | + +NOTE 1: As an option, cause value 0000 0011 may be used for an MO Short message service + +NOTE 2: As an option, cause value 0000 0000 may be used for an MO Voice broadcast or group call + +All other cause values shall be treated as 0000 0000 + +## 10.5.2.48 APDU ID + +The *APDU ID* information element identifies the particular protocol and associated application for an APDU. + +The *APDU ID* information element is coded as shown in figure 10.5.2.48.1 and table 10.5.2.48.1. + +The *APDU ID* is a type 1 information element. + +![](6d49c8b8197834dbfb3ac14809ec84f3_img.jpg) + +| | | | | | | | | +|---|-------------|---|---|---------------------|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| | APDU ID IEI | | | Protocol identifier | | | octet 1 | + +**Figure 10.5.2.48.1: APDU ID information element****Table 10.5.2.48.1: APDU ID information element format** + +| Protocol identifier (octet 1) | | | | | +|-------------------------------|---|---|-------------------------|----------------------------| +| Bits | | | | | +| 4 | 3 | 2 | 1 | Protocol / Application | +| 0 | 0 | 0 | 0 | RRLP (3GPP TS 44.031)/ LCS | +| 0 | 0 | 0 | 1 | ETWS (3GPP TS 23.041) | +| 0 | 0 | 1 | 0 | | +| to | | | reserved for future use | | +| 1 | 1 | 1 | 1 | | + +## 10.5.2.49 APDU Flags + +The *APDU Flags* information element provides segmentation and control information for an associated APDU. + +The *APDU Flags* information element is coded as shown in figure 10.5.2.49.1 and table 10.5.2.49.1. + +The *APDU Flags* is a type 1 information element. + +![](4346a953799e5ce8ac5a8fe4433fe26d_img.jpg) + +| | | | | | | | | +|---|----------------|---|---|-------|-----|------------|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| | APDU Flags IEI | | | 0 | C/R | first seg. | last seg. | +| | | | | spare | | | octet 1 | + +**Figure 10.5.2.49.1: APDU Flags information element** + +**Table 10.5.2.49.1: APDU Flags information element format** + +| | | +|----------------------------------------------------|-------------------------------| +| Last Segment (octet 1) | | +| bit 1 | | +| 0 | Last or only segment | +| 1 | Not last or only segment | +| First Segment (octet 1) | | +| bit 2 | | +| 0 | First or only segment | +| 1 | Not first or only segment | +| C/R (octet 1) | | +| If last seg. = 0, then: | | +| bit 3 | | +| 0 | Command or Final Response | +| 1 | Not Command or Final Response | +| If last seg. = 1, then bit 3 is spare and set to 0 | | + +## 10.5.2.50 APDU Data + +The purpose of the information element is to provide an APDU or APDU segment. + +The *APDU Data* information element is coded as shown in figure 10.5.2.50.1 and table 10.5.2.50.1. + +The APDU Data is a type 4 information element with minimum length of 2 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (3GPP TS 44.006). + +![](6fd4c6c23098ef713797b9e98ec299e8_img.jpg) + +| | | | | | | | | | +|-------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| APDU IEI | | | | | | | | octet 1 | +| Length of APDU contents | | | | | | | | octet 2 | +| APDU Information | | | | | | | | octet 3-n | + +**Figure 10.5.2.50.1: APDU Data information element****Table 10.5.2.50.1: APDU Data information element format** + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| APDU Information (octets 3-n) | | +| Contains an APDU message or APDU segment as follows: | | +| Protocol ID/
Application | APDU Message or Segment | +| ----- | ----- | +| RRLP | RRLP message in 3GPP TS 44.031 (1) | +| ETWS | ETWS Primary Notification message in 3GPP TS 23.041 | +| NOTE 1: Messages are segmented on octet boundaries. Zero bits are used, where necessary, to pad out the last segment to an octet boundary. | | + +## 10.5.2.51 Handover To UTRAN Command + +The purpose of Handover To UTRAN Command information element is to provide information to the mobile station when performing handover to UTRAN or CS to PS SRVCC to UTRAN (HSPA). The Handover to UTRAN Command information element contains all information needed by the mobile station when performing handover to UTRAN and part of information needed by the mobile station when performing CS to PS SRVCC to UTRAN (HSPA). + +The Handover To UTRAN Command is a type 4 information element with length 3-n octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|---|-----------| +| Handover to UTRAN Command IEI | | | | | | | | octet 1 | +| Length of Handover to UTRAN Command contents | | | | | | | | octet 2 | +| Handover to UTRAN Command value part | | | | | | | | Octet 3-n | + +**Figure 10.5.2.51.1: Handover to UTRAN Command information element** + +The value part of the Handover To UTRAN Command IE is coded as defined in 3GPP TS 25.331. + +### 10.5.2.52 Handover To cdma2000 Command + +The purpose of Handover To cdma2000 Command information element is to provide information to the mobile of handover to cdma2000. The Handover to cdma2000 Command information element contains all information needed by the mobile for handover to cdma2000. + +The Handover To cdma2000 Command IE is coded as follows. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------|---|---|---|---|---|---|---|-----------| +| Handover to cdma2000 Command IEI | | | | | | | | octet 1 | +| Length of cdma2000 command contents | | | | | | | | octet 2 | +| Handover to cdma2000 Command value part | | | | | | | | octet 3-n | + +**Figure 10.5.2.52.1: Handover to cdma2000 Command information element** + +The MSG\_TYPE of the cdma2000 message used for the intersystem handover shall be included in the first octet of the Handover to cdma2000 value part. It is specified in TTA/EIA/IS-2000-4-A and in TTA/EIA/IS-833. (E.g. MSG\_TYPE:= {00010001} if Extended Handoff Direction Message (EHDM) is used, MSG\_TYPE:= {00011111} if General Handoff Direction Message is used, etc.). The order of the bits in this octet representing is given by the following example. If MSG\_TYPE:= {00010001} (EHDM), the bit number 1 of 'cdma2000 MSG\_TYPE IEI' shall be '0', the bit number 2 shall be '0', etc., and the bit number 8 shall be '1', as illustrated below. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit | +|---|---|---|---|---|---|---|---|-----| +| 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | | + +The remaining octets in the Handover to cdma2000 value part shall be coded as the payload of the message used for the inter system handover, as specified in TTA/EIA/IS-2000-5-A and in TTA/EIA/IS-833. The bit ordering shall be similar to the case described above. The bit number 1 of 'cdma2000 message payload' shall be coded as the first bit of the first record of the message defined in TTA/EIA/IS-2000-5-A and in TTA/EIA/IS-833, reading the records defined in TTA/EIA/IS-2000-5-A and in TTA/EIA/IS-833 from left to right. + +The Handover To cdma2000 Command is a type 4 information element with length 4 to n octets. + +10.5.2.53 (void) + +10.5.2.54 (void) + +10.5.2.55 (void) + +10.5.2.56 (void) + +10.5.2.57 Service Support + +The *Service Support* information element provides information about which services the mobile station supports. + +The *Service Support* information element is coded as shown in figure 10.5.2.57.1 and table 10.5.2.57.1. + +The *Service Support* is a type 3 information element with 2 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|------------|------------|------------|------------|------------|-------------------|-------------------|---------| +| Service Support IEI | | | | | | | | octet 1 | +| Spare
0 | Spare
0 | Spare
0 | Spare
0 | Spare
0 | Spare
0 | MBMS
Multicast | MBMS
Broadcast | octet 2 | + +**Figure 10.5.2.57.1: Service Support information element** + +**Table 10.5.2.57.1: Service Support information element format** + +| | | +|------------------------|-------------------------------------------------------------------------| +| Last Segment (octet 2) | | +| bit 1 | | +| 0 | mobile station does not require notification of broadcast MBMS services | +| 1 | mobile station requires notification of broadcast MBMS services | +| bit 2 | | +| 0 | mobile station does not require notification of multicast MBMS services | +| 1 | mobile station requires notification of multicast MBMS services | + +## 10.5.2.58 MBMS p-t-m Channel Description + +The *MBMS p-t-m Channel Description* information element is sent by the network to the mobile station to indicate part of the preassigned resources for an MBMS service (see 3GPP TS 44.060). The remaining part is included in the *MBMS Session Parameters List* information element (see sub-clause 10.5.2.58a). + +The *MBMS p-t-m Channel Description* information element is coded as shown in figure 10.5.2.58.1 and table 10.5.2.58.1 and table 10.5.2.58.2. + +The *MBMS p-t-m Channel Description* is a type 4 information element with a minimum length of 4 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +![](9297c2df178fdaf3c88c9600b0d0b620_img.jpg) + +| | | | | | | | | | +|-----------------------------------------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| MBMS p-t-m Channel Description IEI | | | | | | | | octet 1 | +| Length of MBMS p-t-m Channel Description value part | | | | | | | | octet 2 | +| MBMS p-t-m Channel Description value part | | | | | | | | octet 3 - n | + +**Figure 10.5.2.58.1: MBMS p-t-m Channel Description information element****Table 10.5.2.58.1: MBMS p-t-m Channel Description value part** + +``` +< MBMS p-t-m Channel Description value part > ::= + < MBMS p-t-m Channel Description : < MBMS p-t-m Channel Description IE > > + < spare bit >**; +``` + +**Table 10.5.2.58.2: MBMS p-t-m Channel Description value part details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------| +| MBMS p-t-m Channel Description
The MBMS p-t-m Channel Description information element is defined in 3GPP TS 44.060. | +|--------------------------------------------------------------------------------------------------------------------------------------| + +## 10.5.2.58a MBMS Session Parameters List + +The *MBMS Session Parameters List* information element is sent by the network to the mobile station to indicate part of the preassigned resources for an MBMS service (see 3GPP TS 44.060). The remaining part is included in the *MBMS p-t-m Channel Description* information element (see sub-clause 10.5.2.58). + +The *MBMS Session Parameters List* information element is coded as shown in figure 10.5.2.58a.1 and table 10.5.2.58a.1 and table 10.5.2.58a.2. + +The *MBMS Session Parameters List* is a type 4 information element with a minimum length of 4 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006) and except for that given when the information element is included in the MBMS ANNOUNCEMENT message. + +If the *MBMS Session Parameters List* information element is included in the MBMS ANNOUNCEMENT message, its maximum length is equal to 8 octets (if octet 6 is included, then octet 7 shall also be included) and it shall contain one MBMS Bearer Identity, one Estimated Session Duration and may contain one MBMS Radio Bearer Starting Time, one EGPRS Window Size and one NPM Transfer Time. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---------------------------------------------------|---|---|---|---|---|---|-------------| +| | MBMS Session Parameters List IEI | | | | | | | octet 1 | +| | Length of MBMS Session Parameters List value part | | | | | | | octet 2 | +| | MBMS Session Parameters List value part | | | | | | | octet 3 - n | + +**Figure 10.5.2.58a.1: MBMS Session Parameters List information element** + +**Table 10.5.2.58a.1: MBMS Session Parameters List value part** + +``` +< MBMS Session Parameters List value part > ::= + < MBMS Session Parameters List : < MBMS Session Parameters List IE > > + < spare bit >**; +``` + +**Table 10.5.2.58a.2: MBMS Session Parameters List value part details** + +**MBMS Session Parameters List** + +The *MBMS Session Parameters List* information element is defined in 3GPP TS 44.060. + +## 10.5.2.59 Dedicated Service Information + +The *Dedicated Service Information* information element indicates to the mobile station whether any actions shall be performed on the target cell. + +The *Dedicated Service Information* information element is coded as shown in figure 10.5.2.59.1 and table 10.5.2.59.1. + +The *Dedicated Service Information* is a type 3 information element with 2 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------|-----------------------------------|---------|---------|---------|---------|---------|-----|---------| +| | Dedicated Service Information IEI | | | | | | | octet 1 | +| Spare 0 | Spare 0 | Spare 0 | Spare 0 | Spare 0 | Spare 0 | Spare 0 | SIS | octet 2 | + +**Figure 10.5.2.59.1: Dedicated Service Information information element** + +**Table 10.5.2.59.1: Dedicated Service Information information element format** + +``` +Last Segment (octet 2) +bit 1 +0 mobile station shall not perform Service Information Sending procedure on new cell. +1 mobile station shall perform Service Information Sending procedure on new cell. +``` + +## 10.5.2.60 MPRACH Description + +The *MPRACH Description* information element is sent by the network to the mobile station to indicate that Counting is to be used for MBMS (see 3GPP TS 44.060). + +The *MPRACH Description* information element is coded as shown in figure 10.5.2.60.1 and table 10.5.2.60.1 and table 10.5.2.60.2. + +The *MPRACH Description* is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|-----------------------------------------|---|---|---|---|---|---|-------------| +| | MPRACH description IEI | | | | | | | octet 1 | +| | Length of MPRACH description value part | | | | | | | octet 2 | +| | MPRACH description value part | | | | | | | octet 3 - n | + +**Figure 10.5.2.60.1: MPRACH description information element** + +**Table 10.5.2.60.1: MPRACH description value part** + +| | +|------------------------------------------------------------------------------------------------------------------------| +| < MPRACH description value part > ::=
< MPRACH description : < MPRACH description IE > >
< spare bit >**; | +|------------------------------------------------------------------------------------------------------------------------| + +**Table 10.5.2.60.2: MPRACH description value part details** + +| | +|--------------------------------------------------------------------------------------------------------------| +| MPRACH description
The MPRACH description information element is defined in 3GPP TS 44.060. | +|--------------------------------------------------------------------------------------------------------------| + +## 10.5.2.61 Restriction Timer + +The *Restriction Timer* information element indicates to the mobile station whether any actions shall be performed on the target cell (see 3GPP TS 44.060). + +The *Restriction Timer* information element is coded as shown in figure 10.5.2.61.1 and table 10.5.2.61.1 and table 10.5.2.61.2. + +The *Restriction Timer* is a type 3 information element with 2 octets length. + +![](1bee321e63e7ca14df7e4a8f2f386ce5_img.jpg) + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Restriction Timer IEI | | | | | | | | octet 1 | +| Restriction Timer value part | | | | | | | | octet 2 | + +**Figure 10.5.2.61.1: Restriction Timer information element****Table 10.5.2.61.1: Restriction Timer value part** + +| | +|----------------------------------------------------------------------------------------------------| +| < Restriction Timer value part > ::=
< RESTRICTION_TIMER : bit (4) >
< spare bit >**; | +|----------------------------------------------------------------------------------------------------| + +**Table 10.5.2.61.2: Restriction Timer value part details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RESTRICTION_TIMER
This field indicates the maximum reaction time to the MBMS ANNOUNCEMENT in seconds for mobile station, before the information contained in the MBMS ANNOUNCEMENT expires.
Bit
4 3 2 1
0 0 0 0    10
0 0 0 1    20
0 0 1 0    30
...
1 1 1 0    150
1 1 1 1    160 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 10.5.2.62 MBMS Session Identity + +The *MBMS Session Identity* information element is passed to the mobile station by the network and allows the mobile station to avoid duplication of reception of MBMS sessions. + +The *MBMS Session Identity* information element is coded as shown in figure 10.5.2.62.1 and table 10.5.2.62.1 and table 10.5.2.62.2. + +The *MBMS Session Identity* is a type 3 information element with 2 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------|---|---|---|---|---|---|---|-------------| +| MBMS Session Identity IEI | | | | | | | | octet 1 | +| Length of MBMS Session Identity value part | | | | | | | | octet 2 | +| MBMS Session Identity value part | | | | | | | | octet 3 - n | + +Figure 10.5.2.62.1: MBMS Session Identity information element + +Table 10.5.2.62.1: MBMS Session Identity value part + +``` +< MBMS Session Identity value part > ::= + < MBMS_Session_Identity : bit (8) > + < spare bit >**; +``` + +Table 10.5.2.62.2: MBMS Session Identity value part details + +**MBMS\_Session\_Identity** (8 bit field) +This field contains the MBMS Session Identity of the concerned MBMS session (see 3GPP TS 29.061). + +### 10.5.2.63 Reduced group or broadcast call reference + +The purpose of the *Reduced Group or Broadcast Call Reference* is to provide information describing a voice group or broadcast call. The IE of the *Reduced Group or Broadcast Call Reference* is composed of the group or broadcast call reference together with a service flag. + +The *Reduced Group or Broadcast Call Reference* information element is coded as shown in figure 10.5.2.63.1 and Table 10.5.2.63.1 + +The *Reduced Group or Broadcast Call Reference* is a type 3 information element with 5 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------|---|---|----|-------|---|---|---|---------| +| Reduced Group or broadcast call reference IEI | | | | | | | | Octet 1 | +| Binary coding of the group or broadcast call reference | | | | | | | | Octet 2 | +| | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| | | | SF | SPARE | | | | Octet 5 | + +Figure 10.5.2.63.1 Reduced Group or Broadcast Call Reference + +Table 10.5.2.63.1 Reduced Group or Broadcast Call Reference + +Binary code of the group or broadcast call reference +The length of the binary code has 27 bits which is encoded in the octet 2, 3, 4 and Bits 8,7,6 (octet 5). +The highest bit of the BC is the bit 8 in the octet 2 and the lowest bit is allocated in the bit 6 in the octet 5. +(see also 3GPP TS 23.003 [10]) + +SF Service flag (octet 5) +Bit +**5** +0 VBS (broadcast call reference) +1 VGCS (group call reference) + +### 10.5.2.64 Talker Priority status + +The *Talker Priority Status* information element identifies the priority of the current talker, the channel to be used for talker priority-related uplink access requests, and the status of the emergency mode. + +The *Talker Priority Status* information element is coded as shown in figure 10.5.2.64.1 and table 10.5.2.64.1. + +The *Talker Priority Status IE* is a type 4 information element with 3 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|-------|---|---|-----|----------|---|---|---------| +| Talker Priority Status IEI | | | | | | | | octet 1 | +| Length of Talker Priority Status | | | | | | | | octet 2 | +| ES | Spare | | | UAI | Priority | | | octet 3 | + +**Figure 10.5.2.64.1: Talker Priority Status information element** + +**Table 10.5.2.64.1: Talker Priority Status information element format** + +| | | +|-----------------------------------------|-------------------------| +| Priority (octet 3) | | +| Bits | | +| 3 2 1 | | +| 0 0 0 | Normal Priority | +| 0 0 1 | Privileged Priority | +| 0 1 0 | Emergency Priority | +| 0 1 1 | reserved for future use | +| to | | +| 1 1 1 | reserved for future use | +| UAI- Uplink Access Indication (octet 3) | | +| Bit | | +| 4 | | +| 0 | Group Channel | +| 1 | RACH Access | +| ES - Emergency Status (octet 3) | | +| Bits | | +| 8 | | +| 0 | Emergency mode not set | +| 1 | Emergency mode set | + +## 10.5.2.65 Talker Identity + +The *Talker identity* information element contains additional information regarding the identity of the talker. + +The *Talker identity* information element is coded as shown in figure 10.5.2.65.1 and table 10.5.2.65.1. + +The *Talker identity* is a type 4 information element with a minimum length of 3 octets and a maximum length of 20 octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|-------------|---|---|---|------------| +| Talker Identity IEI | | | | | | | | Octet 1 | +| Length of talker identity contents | | | | | | | | Octet 2 | +| Spare | | | | Filler Bits | | | | Octet 3 | +| Talker Identity field | | | | | | | | Octet 4-20 | + +**Figure 10.5.2.65.1: Talker identity information element** + +**Table 10.5.2.65.1: Talker identity information element** + +### Filler bits (octet 3, bits 1-3) + +This field contains the number of unused bits in the last octet of the Talker Identity field. The filler bits are situated in the val(Filler Bits) least significant bits of the last octet of the Talker Identity field. Bits 4 to 8 of octet 3 are spare and shall be encoded as zero. + +### Talker identity field (octets 4, etc.) + +This field contains the Talker Identity field. Bit 8 of octet 4 contains the most significant bit of the Talker Identity field. + +## 10.5.2.66 Token + +The purpose of the *Token* information element is for a handshake mechanism between the BSS and the MS to validate Priority Uplink Requests. It is therefore included in the BUSY UPLINK and the PRIORITY UPLINK REQUEST messages. + +The *Token* information element is coded as shown in figure 10.5.2.66.1 and table 10.5.2.66.1. + +The *Token 2* is a type 3 information element with 5 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------|---|---|---|---|---|---|---|---------| +| Identification Value 2 IEI | | | | | | | | octet 1 | +| | | | | | | | | octet 2 | +| Identification Value | | | | | | | | octet 3 | +| | | | | | | | | octet 4 | +| | | | | | | | | octet 5 | + +Figure 10.5.2.66.1: *Token* information element + +Table 10.5.2.66.1: *Token* information element + +| | +|--------------------------------------------------------------------------------------------------------------------------| +| Token (octets 2-5)
This is an unformatted 32 bit field. The contents of this field are randomly generated by the BSS. | +|--------------------------------------------------------------------------------------------------------------------------| + +## 10.5.2.67 PS Cause + +The purpose of the *PS Cause* information element is to provide the reason for release of a DTM handover. + +The *PS Cause* information element is coded as shown in Figure 10.5.2.67.1. The use of the *PS Cause* information element is described in sub-clause 3.7.2.1. + +The *PS Cause* is a type 1 information element. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------|---|---|---|----------------|---|---|---|---------| +| PS Cause IEI | | | | PS cause value | | | | octet 1 | + +Figure 10.5.2.67.1: *PS Cause* information element + +Table 10.5.2.67.1: *PS Cause* information element + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PS cause value (4 bit field)
Bit
4 3 2 1
0 0 0 0 DTM multislot capabilities violated
0 0 0 1 No uplink TBF
0 0 1 0 Too many TBFs
All remaining PS cause values are reserved | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 10.5.2.68 VGCS AMR Configuration + +The *VGCS AMR Configuration* information element identifies the AMR codec modes to be used on a group channel using speech version 3. + +The *VGCS AMR Configuration* information element is coded as shown in figure 10.5.2.67.1 and table 10.5.2.67.1. + +The *VGCS AMR Configuration IE* is a type 4 information element with 3 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|---|---|---|-------|---|---|---|---------| +| VGCS AMR Configuration IEI | | | | | | | | octet 1 | +| Length of VGCS AMR Configuration | | | | | | | | octet 2 | +| AMR Configuration | | | | Spare | | | | octet 3 | + +Figure 10.5.2.68.1: *VGCS AMR Configuration* information element + +**Table 10.5.2.68.1: VGCS AMR Configuration information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AMR Configuration bit 5-8 (octet 3)
This field indicates the set of AMR codec modes to be used. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92]. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 10.5.2.69 Carrier Indication + +This information element may be included in the Frequency Redefinition Message to indicate a change on only one carrier. + +The *Uplink Carrier Indication* is a type 1 information element with a length of 1 octet. + +![](6a0568674e792609ca7e6c1533614862_img.jpg) + +| | | | | | | | | | +|------------------------|---|---|---|-------|---|---|----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Carrier Indication IEI | | | | Spare | | | CI | | + +**Figure 10.5.2.69.1: Carrier Indication information element****Table 10.5.2.69.1: CARRIER INDICATION information element** + +| | | +|------------|-----------| +| CI | | +| bit | | +| 0 | Carrier 1 | +| 1 | Carrier 2 | + +## 10.5.2.70 SI10bis Rest Octets + +**Table 10.5.2.70.1: SI10bis Rest Octets** + +``` + + ::= + < SI10bis Sequence : bit (2) > + { H + { 0 | 1 < BCCH ARFCN : bit (10) > } + { 0 | 1 < BSIC : bit (6) > } + < SI10bis Neighbour Cell Info > } ** L + ; + + ::= + < Group Channel Description > + { 0 -- no additional frequency list is included + | 1 { 0 < Frequency Short List : bit (64) > + | 1 < Frequency List : > } } < CELL_GLOBAL_COUNT : bit (2) > + < B22_COUNT : bit > + { 0 -- all following parameters are same as in current cell + | 1 { 0 -- talker priority not supported + | 1 < Priority Uplink access : bit > } + { 0 | 1 { 0 | 1 < FR AMR Config : bit (4) > } + { 0 | 1 < HR AMR Config : bit (4) > } } + { 0 | 1 < SMS Data Confidentiality Ind : bit (1) > + < SMS Guaranteed Privacy Ind : bit (1) > } + { 0 | 1 < Max retrans : bit (2) > < Tx-Integer : bit (4) > } + }; + + ::= null | bit ; + +``` + +### SI10bis Sequence + +This sequence number identifies a consistent set of SI10bis/SI10ter messages. + +### Position in SI5 list + +This is coded as the *first frequency* field as specified in sub-clause 10.5.2.44 + +### BCCH ARFCN + +The BCCH ARFCN number field is coded as the binary representation of the BCCH carrier's absolute RF channel number. + +#### BSIC + +This field is optional and need only to be included to distinguish two cells which have the same BCCH ARFCN value. + +#### Group Channel Description + +This is coded as the Group Channel Description field as specified in sub-clause 9.1.21a. If the hopping sequence for the group channel is specified by means of the Frequency List, then neither the Mobile Allocation nor the Frequency Short List shall be included in the Group Channel Description. + +#### Frequency Short List + +This field is syntactically and semantically equivalent to octets 1-8 of the *Frequency Short List 2* information element. See sub-clause 10.5.2.14a. + +#### Frequency List + +This field is syntactically and semantically equivalent to octets 2-n of the *Frequency List* information element. See sub-clause 10.5.2.13. + +#### CELL\_GLOBAL\_COUNT, B22\_COUNT + +These are coded as specified in sub-clause 9.1.21a. + +#### Priority Uplink access, FR AMR Config, HR AMR Config, SMS Data Confidentiality Ind, SMS Guaranteed Privacy Ind + +These are coded as specified in sub-clause 10.5.2.22c. + +#### Max retrans, Tx-Integer + +These are coded as specified in sub-clause 10.5.2.29. + +### 10.5.2.71 SI10ter Rest Octets + +**Table 10.5.2.71.1: SI10ter Rest Octets** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 <SI10ter Rest Octets> ::=   < SI10bis Sequence : bit (2) >   {     0      <Position in SI5 list : bit(5) >       1 < BCCH ARFCN : bit (10) > }   { 0   1 < BSIC : bit (6) > }   <NCH Position : bit (5)> -- see SI1 rest octets, 44.018 / 10.5.2.32   <spare padding>;
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### Position in SI5 list + +This is coded as the *first frequency* field as specified in sub-clause 10.5.2.44 + +#### BCCH ARFCN + +The BCCH ARFCN number field is coded as the binary representation of the BCCH carrier's absolute RF channel number. + +#### BSIC + +This field is optional and need only to be included to distinguish two cells which have the same BCCH ARFCN value. + +#### SI10bis Sequence + +This sequence number identifies a consistent set of SI10bis/SI10ter messages. + +## 10.5.2.72 Application Data + +The *Application Data* element contains application data sent to or by the network. + +The *Application Data* element is a type 3 information element with a length of 10 octets. The contents of the *Application Data* is implementation-specific: + +![](4cb497b8657c6247d4faab7691cd93f2_img.jpg) + +| | | | +|----------------------------------------------------|--|-------------| +| 8      7      6      5      4      3      2      1 | | | +| Application Data IEI | | octet 1 | +| Application Data | | octets 2-10 | + +**Figure 10.5.2.72.1: *Application Data* information element** + +## 10.5.2.73 Data Identity + +The *Data Identity* Element contains Application Indicator, Data Identifier and Distribution Parameter. The Application Indicator is used to identify whether the Application data IE, which is sent together with the Data Identity IE, is an application-specific data or is a confirmation. The Data Identifier is to provide a sequence number of the sending of Application Data. The value of the Data Identifier is dependent on the value of the Application Indicator: + +- If the Application Indicator indicates sending application data to the network, the data identifier contains a number from the range between 0 and 15 which is generated by the mobile station. +- If the Application Indicator indicates sending confirmation of the reception of the application data, the Data Identifier shall contain the data identifier which was received in the Data Identity IE sent by the previous sender. + +![](828dfe8c7048066217f2199b4a1fb1a6_img.jpg) + +| | | | | | +|----------------------------------------------------|--|----|--|---------| +| 8      7      6      5      4      3      2      1 | | | | | +| Data Identity IEI | | | | Octet 1 | +| DP | | DI | | Octet 2 | +| AI | | | | | + +**Figure 10.5.2.73.1: *Data Identity* information element** + +**Table 10.5.2.73.1: *Data Identity* information element** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Application Indicator (1 bit):
Bit
1
0    Application-specific data
1    Confirmation of receiving application-specific data

Data identifier (4 bit):
The data identification can have 16 values to identify the data sending sequence.

Distribution parameter (3 bit):
8 7 6
1 x x data shall be distributed to talkers & listeners
x 1 x data shall be distributed to dispatchers
x x 1 data shall be distributed to network application | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 10.5.2.74 Uplink Access Indication + +The *Uplink Access Indication* is a type 1 information element. + +The *Uplink Access Indication* information element is coded as shown in figure 10.5.2.74.1 and table 10.5.2.74.1. + +![](9286389dd21b67a29ab5bfb4efc2d336_img.jpg) + +| | | | | | | | | | +|------------------------------|----------|----------|----------|----------|----------|----------|----------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Uplink Access Indication IEI | | | | Spare | | | UA Ind | Octet 1 | + +**Figure 10.5.2.74.1 Uplink Access Indication** + +**Table 10.5.2.74.1: Uplink Access Indication information element** + +| | | +|-------------------------|-----------------------------------------------------------------------| +| UA Ind (octet 1, bit 1) | | +| Bit | | +| 1 | | +| 0 | Uplink access for application-specific data on the group call channel | +| 1 | Uplink access for application-specific data on the RACH | + +## 10.5.2.75 Individual priorities + +The *Individual priorities* information element is coded as shown in figure 10.5.2.75.1 and table 10.5.2.75.1. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|---|---|---|---|-------------| +| Individual priorities IEI | | | | | | | | octet 1 | +| Length of Individual priorities | | | | | | | | octet 2 | +| Individual priorities | | | | | | | | octet 3 - n | + +**Figure 10.5.2.75.1 Individual priorities****Table 10.5.2.75.1: Individual priorities information element** + +``` + +< Individual priorities > ::= + { 0 | 1 -- delete all stored individual priorities + 1 -- provide individual priorities + < GERAN_PRIORITY : bit(3) > + { 0 | 1 < 3G Individual Priority Parameters Description : + < 3G Individual Priority Parameters Description struct >> } + { 0 | 1 < E-UTRAN Individual Priority Parameters Description : + < E-UTRAN Individual Priority Parameters Description struct >> } + { 0 | 1 < T3230 timeout value : bit(3) > } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Rel-11 + { 0 | 1 < E-UTRAN IPP with extended EARFCNs Description : + < E-UTRAN IPP with extended EARFCNs Description struct >> } + } + }; + +< 3G Individual Priority Parameters Description struct > ::= + { 0 | 1 < DEFAULT_UTRAN_PRIORITY : bit(3) > } + { 1 < Repeated Individual UTRAN Priority Parameters : < Repeated Individual UTRAN Priority Parameters struct >> } ** 0 ; + +< Repeated Individual UTRAN Priority Parameters struct > ::= + { 0 { 1 < FDD-ARFCN : bit (14) > } ** 0 | 1 { 1 < TDD-ARFCN : bit (14) > } ** 0 } + < UTRAN_PRIORITY : bit(3) > ; + +< E-UTRAN Individual Priority Parameters Description struct > ::= + { 0 | 1 < DEFAULT_E-UTRAN_PRIORITY : bit(3) > } + { 1 < Repeated Individual E-UTRAN Priority Parameters : + < Repeated Individual E-UTRAN Priority Parameters Description struct >> } ** 0 ; + +< Repeated Individual E-UTRAN Priority Parameters Description struct > ::= + { 1 < EARFCN : bit (16) > } ** 0 + < E-UTRAN_PRIORITY : bit(3) > ; + +< E-UTRAN IPP with extended EARFCNs Description struct > ::= + { 0 | 1 < DEFAULT_E-UTRAN_PRIORITY : bit(3) > } + { 1 < Repeated Individual E-UTRAN PP with extended EARFCNs : + < Repeated Individual E-UTRAN PP with extended EARFCNs Description struct >> } ** 0 ; + +< Repeated Individual E-UTRAN PP with extended EARFCNs Description struct > ::= + { 1 < EARFCN_extended : bit (18) > } ** 0 + < E-UTRAN_PRIORITY : bit(3) > ; + +``` + +**Table 10.5.2.75.2: Individual priorities information element details****GERAN\_PRIORITY** (3 bit field)**UTRAN\_PRIORITY** (3 bit field)**E-UTRAN\_PRIORITY** (3 bit field) + +These fields are used for the inter-RAT cell re-selection algorithm based on priority information, as defined in 3GPP TS 45.008. + +**DEFAULT\_UTRAN\_PRIORITY** (3 bit field)**DEFAULT\_E-UTRAN\_PRIORITY** (3 bit field) + +The **DEFAULT\_UTRAN\_PRIORITY** field is encoded as the **UTRAN\_PRIORITY** field; the **DEFAULT\_E-UTRAN\_PRIORITY** field is encoded as the **E-UTRAN\_PRIORITY** field. Any UTRAN frequency contained in the 3G Frequency list and not explicitly listed in any occurrence of the *Repeated Individual UTRAN Priority Parameters* IE or any E-UTRAN frequency contained in the E-UTRAN Neighbour Cell list and not explicitly listed in any occurrence of neither the *Repeated Individual E-UTRAN Priority Parameters* IE nor the *Repeated Individual E-UTRAN PP with extended EARFCNs* IE shall be assigned the corresponding default value. If the *Repeated Individual UTRAN Priority Parameters* IE is not present, every UTRAN frequency in the 3G Frequency list for the serving cell shall be assigned the default value. If neither the *Repeated Individual E-UTRAN Priority Parameters* IE nor the *Repeated Individual E-UTRAN PP with extended EARFCNs* IE are present, every E-UTRAN frequency in the E-UTRAN Neighbour Cell list for the serving cell shall be assigned the default value. + +**FDD-ARFCN** (14 bit field)**TDD-ARFCN** (14 bit field)**EARFCN** (16 bit field) + +These fields are used to indicate the frequencies for which priorities are provided, see sub-clause 9.1.54. + +**T3230 timeout value** (3 bit field) + +The timer uses 3 bits to indicate the time for which the signalled individual priorities are valid: + +| | | +|-------|-----------------------------------------------------------------------------------------------| +| 0 0 0 | 5 minute timeout; | +| 0 0 1 | 10 minute timeout; | +| 0 1 0 | 20 minute timeout; | +| 0 1 1 | 30 minute timeout; | +| 1 0 0 | 60 minute timeout; | +| 1 0 1 | 120 minute timeout; | +| 1 1 0 | 180 minute timeout; | +| 1 1 1 | reserved for future use; if received, it shall be interpreted by the mobile station as '110'; | + +If this information element is not present, the mobile station shall consider the signalled individual priorities to be valid until the occurrence of one of the conditions specified in subclause 3.2.3.3 + +#### **E-UTRAN IPP with extended EARFCNs Description** + +This information element shall be included in the message if both the network and the mobile station support extended EARFCNs (see 3GPP TS 24.008); in such a case the *E-UTRAN Individual Priority Parameters Description* IE shall not be included in the message. + +**DEFAULT E-UTRAN\_PRIORITY** (3 bit field)**E-UTRAN\_PRIORITY** (3 bit field) + +See the above description. + +**EARFCN\_extended** (18 bit field) + +See table 9.1.54.1 for the definition of the *EARFCN\_extended* field. + +### **10.5.2.76 Feature Indicator** + +The purpose of the *Feature Indicator* information element is to provide the mobile station with feature related indications. + +The *Feature Indicator* information element is coded as shown in figure 10.5.2.76.1 and table 10.5.2.76.1. + +The *Feature Indicator* is a type 1 information element. + +| 4 | | 3 | 2 | 1 | +|----------------------|--|---|-------|-------| +| PEO_BCCH_CHANGE_MARK | | | CS IR | PS IR | + +**Figure 10.5.2.76.1: Feature Indicator information element** + +**Table 10.5.2.76.1: Feature information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PS IR (PS Domain Implicit Reject)
0 An implicit reject is not indicated for the PS domain.
1 An implicit reject is indicated for the PS domain.

CS IR (CS Domain Implicit Reject)
0 An implicit reject is not indicated for the CS domain.
1 An implicit reject is indicated for the CS domain.

PEO_BCCH_CHANGE_MARK
See P1 Rest Octets IE, sub-clause 10.5.2.23. | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +10.5.2.77 (void) + +## 10.5.2.78 IPA Rest Octets + +The *IPA Rest Octets* information element contains spare bits and possibly at leaste one of the *IPA Uplink Assignment struct*, the *IPA Downlink Assignment struct*, and the *IPA Single Block Uplink Assignment struct*. It shall exclude the assignment of packet resources when sent in response to an EGPRS MULTILATERATION REQUEST message indicating the ‘Access Burst method’ or ‘Extended Access Burst method’. + +The *IPA Rest Octets* information element is coded according to the syntax specified below and described in table 10.5.2.78.1. + +The *IPA Rest Octets* information element is a type 5 information element with 19 octets length. + +Table 10.5.2.78.1: IPA Rest Octets information element + +``` + + ::= + { 0 | 1 < IPA Uplink Assignment struct >} + { 0 | 1 < IPA Downlink Assignment struct >} + { 0 | 1 < IPA Single Block Uplink Assignment struct >} + {null | L -- Receiver compatible with earlier release + | H -- Additions in Release 13 + < RCC : bit (3) > + } + {null | L -- Receiver compatible with earlier release + | H -- Additions in Release 14 + { 0 | 1 < Acknowledged Access Request 1 : Acknowledged Access Request struct > } + { 0 | 1 < Acknowledged Access Request 2 : Acknowledged Access Request struct > } + { 0 | 1 < Acknowledged Access Request 3 : Acknowledged Access Request struct > } + { 0 | 1 < Acknowledged Access Request 4 : Acknowledged Access Request struct > } + } + { null | L -- Receiver compatible with earlier release + | H -- Additions in Release 15 + {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } + } + + ; + + ::= + { 1 < Random Reference : bit (11) > + < FN_OFFSET : bit (8) > + < GAMMA : bit (5) > + < TIMING_ADVANCE_VALUE : bit (6) > + < TFI_ASSIGNMENT : bit (5) > + < USF : bit (3) > + < EGPRS_CHANNEL_CODING_COMMAND : bit (4) > + < Radio Access Capabilities Request : bit (1) > + }** 0; --Repeated as many times as necessary, once for each addressed device + < TN : bit (3) > + { 0 ; --'0' indicates that BCCH frequency shall be used + | 1 {< Frequency Parameters: Frequency Parameters struct >} + } + +< IPA Downlink Assignment struct> ::= + { 1 < TLLI : bit (32) > + < TFI_ASSIGNMENT : bit (5) > + < GAMMA : bit (5) > + { 0 | 1 < TIMING_ADVANCE_VALUE : bit (6) > } + }** 0; --Repeated as many times as necessary, limited by the space in the message + { 0 | 1 < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > } + < RLC_MODE : bit > + < TN : bit (3) > + { 0 --'0' indicates that BCCH frequency shall be used + | 1 {< Frequency Parameters: Frequency Parameters struct >} + } + + ::= + { 1 < Random Reference : bit (11) > + < FN_OFFSET : bit (8) > + < GAMMA : bit (5) > + < TIMING_ADVANCE_VALUE : bit (6) > + < STARTING_TIME_OFFSET : bit (6) >, + }** 0; --Repeated as many times as necessary, limited by the space in the message + < TN : bit (3) > + { 0 ; --'0' indicates that BCCH frequency shall be used + | 1 {< Frequency Parameters: Frequency Parameters struct >} + } + +< Acknowledged Access Request struct > ::= + { + 00 < Short ID : bit (8) > + | 01 < Random ID Low : bit (4) > + | 10 < Random ID High : bit (12) > + } + +``` + +| 11 -- Reserved } + +< PEO IMM Cell Group Details struct > ::= -- Addition in Rel-15 +    < PEO IMM Cell Group Identifier : bit (3) > +    < PEO IMM Change Mark : bit (2) >; + +**Table 10.5.2.78.2: IPA Rest Octets information element details****IPA Uplink Assignment struct** + +The **Random Reference** field (11 bit field) is the 11 bits of the EGPRS PACKET CHANNEL REQUEST message or the EGPRS MULTILATERATION REQUEST message indicating 'RLC Data Block method' or 'Page Response for Positioning Event' as defined in 3GPP TS 44.060. + +The **FN\_OFFSET** field (8 bit field) is a negative offset added to the first FN of this received IMMEDIATE PACKET ASSIGNMENT message which indicates the frame number where the MS sending the EGPRS PACKET CHANNEL REQUEST message. Range: - 255 to 0. + +The **GAMMA** field (5 bit field) is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The GAMMA field is coded according to the following table: + +| bit | | +|-----------|-----------------------| +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | +| ... | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | + +The **TIMING\_ADVANCE\_VALUE** field (6 bit field) is the binary representation of the timing advance in bit periods and encoded the same as the value of the Timing Advance information element defined in sub-clause 10.5.2.40. Range: 0 to 63. + +The **TFI\_ASSIGNMENT** field (5 bit field) is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31. + +The **USF** field (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. + +The **EGPRS\_CHANNEL\_CODING\_COMMAND** field (4 bit field) indicates the channel coding command that the mobile station shall use for any RLC data block regardless a TLLI field contained or not, and is defined in sub-clause 12.10d, 3GPP TS44.060. + +The **Radio Access Capabilities Request** field (1 bit field) indicates the request of MS Radio Access Capability by the network for the addressed MSs in this message. + +- 0 MS Radio Access Capability is not requested by the network; +- 1 MS Radio Access Capability for the BCCH band is requested by the network. + +The **TN** field (3 bit field) is the binary representation of the timeslot number as defined in 3GPP TS 45.010. Range: 0 to 7. + +**Frequency Parameters IE** + +This information element is defined in sub-clause 12.8, 3GPP TS44.060. + +The **EGPRS Window Size** parameter is not included, and default value 192 shall be used for this parameter. + +The **ALPHA** parameter is not included, and default value 0 shall be used for this parameter. + +The **RESEGMENT** parameter is not included, and default value 0 shall be used for this parameter. + +The **USF\_GRANULARITY** parameter is not included, and default value 0 shall be used for this parameter, i.e. the mobile station shall transmit one RLC/MAC block if assigned USF is received. + +***IPA Downlink Assignment struct*****Random Reference, FN\_OFFSET, GAMMA, TFI\_ASSIGNMENT, TIMING\_ADVANCE\_VALUE, TN, EGPRS Window Size, ALPHA fields and Frequency Parameters IE** + +These fields are encoded as in ***IPA Uplink Assignment struct.*** + +The **TLLI** field (32 bit field) is the binary representation of a TLLI. The coding of TLLI is left open for each administration using the structure specified in 3GPP TS 23.003. + +The **RLC\_MODE** field (1 bit field) indicates the RLC mode, see 3GPP TS 44.060: + +- 0 RLC acknowledged mode; +- 1 RLC unacknowledged mode. + +**LINK\_QUALITY\_MEASUREMENT\_MODE** (2 bit field) + +This field is encoded as the **LINK\_QUALITY\_MEASUREMENT\_MODE** in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +***IPA Single Block Uplink Assignment struct*****Random Reference, FN\_OFFSET, GAMMA, TIMING\_ADVANCE\_VALUE, TN, ALPHA fields and Frequency Parameters IE** + +These fields are encoded as in ***IPA Uplink Assignment struct.*** + +The **STARTING\_TIME\_OFFSET** field (6 bit field) is a positive offset added to the first FN of this received IMMEDIATE PACKET ASSIGNMENT message which indicates the start frame number of the assigned single uplink block. Range 0 to 63. + +**RCC** (3 bit) + +See sub-clause 10.5.2.16. + +The **Short ID** field (8 bit field) is the 8 bits of the "Short ID" parameter included in an EGPRS MULTILATERATION REQUEST message indicating 'Access Burst' method as defined in 3GPP TS 44.060 [76]. + +The **Random ID Low** field (4 bit field) is the "Random ID Low" parameter included in an EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 1' as defined in 3GPP TS 44.060 [76]. + +The **Random ID High** field (12 bit field) is the "Random ID High" parameter included in an EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst method – part 2' as defined in 3GPP TS 44.060 [76]. + +**Multilateration Information Request** (1 bit field) + +See sub-clause 10.5.2.16. + +**PEO IMM Cell Group Details struct** + +This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). + +**PEO IMM Cell Group Identifier** (3 bits) + +See sub-clause 10.5.2.16. + +**PEO IMM Change Mark** (2 bits) + +See sub-clause 10.5.2.16. + +**10.5.2.79 DL-DCCH-Message** + +The purpose of the DL-DCCH-Message information element is to provide information to the mobile station when performing CS to PS SRVCC to E-UTRAN. + +The DL-DCCH-Message IE is a type 4 information element with length 3-n octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|-----------| +| DL-DCCH-Message IEI | | | | | | | | octet 1 | +| Length of DL-DCCH-Message contents | | | | | | | | octet 2 | +| DL-DCCH-Message value part | | | | | | | | octet 3-n | + +**Figure 10.5.2.79.1: DL-DCCH-Message information element** + +The value part of the DL-DCCH-Message IE includes a complete RRCConnectionReconfiguration radio interface message as defined in 3GPP TS 36.331. + +#### 10.5.2.80 CN to MS transparent information + +This information element is defined as a general container for passing CN specific information transparently through the BSS from the CN to the MS. + +The CN to MS transparent information IE is a type 4 information element with length 3-n octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----------| +| CN to MS transparent information IEI | | | | | | | | octet 1 | +| Length of CN to MS transparent information contents | | | | | | | | octet 2 | +| CN to MS transparent information (NOTE 1) | | | | | | | | octet 3-n | +| NOTE 1: The content of this field is transparent to the BSS and will be determined by whether a CS to PS SRVCC to UTRAN (HSPA) or E-UTRAN is performed. | | | | | | | | | + +**Figure 10.5.2.80.1: CN to MS transparent information information element** + +CN to MS transparent information field is encoded as the CN to MS transparent information IE without the Element identifier as defined in 3GPP TS 48.008. + +#### 10.5.2.81 PLMN Index + +This information element refers either to the identity of the Common PLMN broadcast in the SYSTEM INFORMATION TYPE 3/4 message or to the identity of an Additional PLMN broadcast in the SYSTEM INFORMATION TYPE 22 message and is coded as in figure 10.5.2.81.1. + +The PLMN Index is a type 1 information element. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------|---|---|---|------------|---|---|---|---------| +| PLMN Index IEI | | | | PLMN Index | | | | octet 1 | + +**Figure 10.5.2.81.1 PLMN Index** + +The PLMN Index is mapped into the *Selected PLMN Index* field (see 3GPP TS 44.060) as shown in the table 10.5.2.81.1 below. + +**Table 10.5.2.81.1: Mapping PLMN Index to Selected PLMN Index** + +| PLMN Index
bit
4 3 2 1 | Selected PLMN Index | +|------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| 0 0 0 1 | 001 - PLMN identity of the Common PLMN broadcast in SYSTEM INFORMATION TYPE 3/4 | +| 0 0 1 0 | 010 - PLMN identity of the first Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22 | +| 0 0 1 1 | 011 - PLMN identity of the second Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22 | +| 0 1 0 0 | 100 - PLMN identity of the third Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22 | +| 0 1 0 1 | 101 - PLMN identity of the fourth Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22 | +| 0 1 1 0...1 1 1 1 | Reserved | + +## 10.5.2.82 Extended TSC Set + +The purpose of the *Extended TSC Set* information element is to provide TSC related information for the assigned radio resources (see 3GPP TS 45.002 for the TSC sets applicable to the CS domain and the PS domain). + +The *Extended TSC Set* information element is coded as shown in figure 10.5.2.82.1 and table 10.5.2.82.1. + +The *Extended TSC Set* is a type 3 information element with 2 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|---|-----------------------------|---------------------------|----------------------------------------|-------------------|---|---|---------| +| Extended TSC Set IEI | | | | | | | | octet 1 | +| Secondary PS Domain TSC Value | | Secondary PS Domain TSC Set | Primary PS Domain TSC Set | 2 nd PS Domain TSC Assigned | CS Domain TSC Set | | | | + +**Figure 10.5.2.82.1: *Extended TSC Set* information element** + +**Table 10.5.2.82.1: Extended TSC Set information element** + +**CS Domain TSC Set** (octet 2): Indicates the TSC set to be used for the radio resources assigned for the CS domain and takes precedence over the CS domain TSC set indicated by the *Channel Description* IE or the *Channel Description 2* IE in the assignment message. This field is ignored when no CS domain resources are provided by the assignment message. + +Bit + +**1 2** + +0 0 TSC set 1 +0 1 TSC set 2 +1 0 TSC set 3 +1 1 TSC set 4 + +**2nd PS Domain TSC Assigned** (octet 2): Indicates whether or not a secondary TSC value is assigned for the downlink of the PS domain. This field is ignored when no PS domain resources are provided by the assignment message. + +Bit + +**3** + +0 A secondary TSC value is not assigned for the PS domain. +1 A secondary TSC value is assigned for the PS domain. The TSC value is indicated by the *Secondary PS Domain TSC Value* field and the corresponding TSC set is indicated by the *Secondary PS Domain TSC Set* field. + +**Primary PS Domain TSC Set** (octet 2): This field indicates the TSC set corresponding to the TSC value indicated by the *Packet Channel Description* IE or the *Channel Description 3* IE in the assignment message regardless if a secondary TSC value is assigned. This field is used for the assigned uplink and downlink PS resources and is ignored when no PS domain resources are provided by the assignment message. + +Bit + +**4** + +0 TSC set 1 +1 Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain). + +**Secondary PS Domain TSC Set** (octet 2): This field indicates the TSC set corresponding to the TSC value indicated by the *Secondary PS Domain TSC Value* field when a secondary TSC value is assigned for the downlink PS resources. This field is ignored when no PS domain resources are provided by the assignment message. + +Bit + +**5** + +0 TSC set 1 +1 Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain). + +**Secondary PS Domain TSC Value** (octet 2): Indicates the secondary TSC value assigned for the downlink PS resources and is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002. Its corresponding TSC set is indicated by the *Secondary PS Domain TSC Set* field. This field is ignored when a secondary TSC value is not assigned for the PS domain or no PS domain resources are provided by the assignment message. Range: 0 to 7. + +### 10.5.2.83 EC Request Reference + +The purpose of the *EC Request Reference* information element is to indicate the 10 least significant bits of the uplink TDMA frame in which the BSS received an EC PACKET CHANNEL REQUEST message and the 3 random bits contained within that same message. + +The *EC Request Reference* information element is coded according to the syntax specified below and described in table 10.5.2.83.1. + +The *EC Request Reference* is a type 3 information element with 13 bits length. + +``` +< EC Request Reference Description > ::= + < Last TDMA Frame : bit (10) > + < Echoed Random Bits : bit (3) > ; +``` + +**Figure 10.5.2.83.1: Request Reference information element** + +**Table 10.5.2.83.1: EC Request Reference information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Last TDMA Frame (10 bit field)

This field identifies the 10 least significant bits of the TDMA frame in which the BSS received the EC PACKET CHANNEL REQUEST message to which the EC IMMEDIATE ASSIGNMENT TYPE 2 message corresponds.

| +|

Echoed Random Bits (3 bit field)

This field is set to the value of the 3 bit random field included within the EC PACKET CHANNEL REQUEST message to which the EC IMMEDIATE ASSIGNMENT TYPE 2 message corresponds.

| + +### 10.5.2.84 EC Packet Channel Description Type 1 + +The *EC Packet Channel Description Type 1* IE identifies the radio parameters applicable to a mobile station that has enabled EC operation and attempting system access using the RACH (i.e. coverage class 1 has been selected for both the uplink and the downlink). + +The *EC Packet Channel Description Type 1* information element is coded according to the syntax specified below and described in table 10.5.2.84.1. + +The *EC Packet Channel Description Type 1* is a type 3 information element with 16 bits length. + +``` +< EC Packet Channel Description Type 1 > ::= + < QUARTER_HYPERFRAME_INDICATOR : bit (2) > + < DL_COVERAGE_CLASS : bit (2) > + < UL_COVERAGE_CLASS : bit (2) > + < TSC Set : bit (1) > + < TSC : bit (3) > + < EC_MA_NUMBER : bit (5) > + < spare bit : bit (1) > ; +``` + +**Figure 10.5.2.84.1: EC Packet Channel Description Type 1 information element** + +**Table 10.5.2.84.1: EC Packet Channel Description Type 1 information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

The QUARTER_HYPERFRAME_INDICATOR field (2 bits) indicates the quarter hyperframe in which the last TDMA frame used to send the EC IMMEDIATE ASSIGNMENT TYPE 1 message was sent. The mobile station uses this information to determine the quarter hyperframe in which it last read the EC-SCH INFORMATION message and thereby acquires TDMA frame synchronization

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +(see 3GPP TS 45.002). This field is coded as follows: + +| | | +|------------|----------------------| +| Bit | | +| 2 1 | | +| 0 0 | Quarter Hyperframe 0 | +| 0 1 | Quarter Hyperframe 1 | +| 1 0 | Quarter Hyperframe 2 | +| 1 1 | Quarter Hyperframe 3 | + +The **DL\_COVERAGE\_CLASS** field (2 bits) indicates the downlink coverage class the mobile station is to use on the assigned packet resources. This field is coded as follows: + +| | | +|------------|---------------------| +| Bit | | +| 2 1 | | +| 0 0 | DL Coverage Class 1 | +| 0 1 | DL Coverage Class 2 | +| 1 0 | DL Coverage Class 3 | +| 1 1 | DL Coverage Class 4 | + +The **UL\_COVERAGE\_CLASS** field (2 bits) indicates the uplink coverage class the mobile station is to use on the assigned packet resources. This field is coded as follows: + +| | | +|------------|---------------------| +| Bit | | +| 2 1 | | +| 0 0 | UL Coverage Class 1 | +| 0 1 | UL Coverage Class 2 | +| 1 0 | UL Coverage Class 3 | +| 1 1 | UL Coverage Class 4 | + +The **TSC Set** field (1 bit) indicates the TSC set corresponding to the TSC value indicated by the TSC field. This field is used for the assigned uplink and downlink PS resources + +| | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------| +| 0 | TSC set 1 | +| 1 | Indicates TSC set 2 for 8PSK modulation and TSC set 3 for GMSK modulation (which is identical to TSC set 3 used for the CS domain). | + +The **TSC** field (3 bits) is the binary representation of the training sequence code as defined in 3GPP TS 45.002. +Range: 0 to 7. + +The **EC\_MA\_NUMBER** field (5 bits) identifies an EC Mobile Allocation set provided by the EC SYSTEM INFORMATION TYPE 1 message (see sub-clause 9.1.43p). This field is coded as follows: + +| | | +|------------------|-----------------------------| +| Bit | | +| 5 4 3 2 1 | | +| 0 0 0 0 0 | EC Mobile Allocation set 1 | +| 0 0 0 0 1 | EC Mobile Allocation set 2 | +| 0 0 0 1 0 | EC Mobile Allocation set 3 | +| . | . | +| . | . | +| 1 1 1 1 1 | EC Mobile Allocation set 32 | + +## 10.5.2.85 EC Packet Channel Description Type 2 + +The *EC Packet Channel Description Type 2* IE identifies the radio parameters applicable to a mobile station that has received an EC IMMEDIATE ASSIGNMENT TYPE 2 message or an EC DOWNLINK ASSIGNMENT message on the EC-AGCH. + +The *EC Packet Channel Description Type 2* information element is coded according to the syntax specified below and described in table 10.5.2.85.1. + +The *EC Packet Channel Description Type 2* is a type 3 information element with 15 bits length. + +``` +< EC Packet Channel Description Type 2 > ::= + < QUARTER_HYPERFRAME_INDICATOR : bit (2) > + < DL_COVERAGE_CLASS : bit (2) > + < UL_COVERAGE_CLASS : bit (2) > + < TSC Set : bit (1) > + < TSC : bit (3) > + < EC_MA_NUMBER : bit (5) > ; +``` + +**Figure 10.5.2.85.1: *EC Packet Channel Description Type 2* information element** + +**Table 10.5.2.85.1: *EC Packet Channel Description Type 2* information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

QUARTER_HYPERFRAME_INDICATOR (2 bit field)

This field indicates the quarter hyperframe in which the last TDMA frame used to send the EC IMMEDIATE ASSIGNMENT TYPE 2 message or EC DOWNLINK ASSIGNMENT message was sent. The mobile station uses this information to determine the quarter hyperframe in which it last read the EC-SCH INFORMATION message and thereby acquires TDMA frame synchronization (see 3GPP TS 45.002).

This field is coded as described in sub-clause 10.5.2.84.

| +|

DL_COVERAGE_CLASS (2 bit field)

This field is described in sub-clause 10.5.2.84.

| +|

UL_COVERAGE_CLASS (2 bit field)

This field is described in sub-clause 10.5.2.84.

| +|

TSC Set (1 bit field)

This field is described in sub-clause 10.5.2.84.

| +|

TSC (3 bit field)

This field is described in sub-clause 10.5.2.84.

| +|

EC_MA_NUMBER (5 bit field)

This field is described in sub-clause 10.5.2.84.

| + +## 10.5.2.86 EC Fixed Uplink Allocation + +The purpose of the *EC Fixed Uplink Allocation* information element is to indicate the set of one or more pre-allocated uplink radio blocks a mobile station is to use for packet data transmission. + +The *EC Fixed Uplink Allocation* information element is coded according to the *EC Fixed Uplink Allocation* struct described in sub-clause 9.1.60. + +The *EC Fixed Uplink Allocation* is a type 3 information element with 32 to 112 bits length. + +See 3GPP TS 24.008. + +### 10.5.2.87 Request Reference Alt + +The purpose of the *Request Reference Alt* information element is to provide the random access information included within the EGPRS MULTILATERATION REQUEST message (indicating the 'Access Burst' method or 'Extended Access Burst' method, see sub-clause 3.5.2.1.2 and sub-clause 3.11) and the frame number, FN modulo 42432 in which the EGPRS MULTILATERATION REQUEST message was received. + +The *Request Reference Alt* information element is coded as shown in figure 10.5.2.87.1 and table 10.5.2.87.1. + +The *Request Reference Alt* is a type 3 information element with 5 octets length. + +![](7e512bcb2039006080b1ad65c7a398c9_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------|---|---|----|----------------|---|-------|---|---------| +| Request Reference Alt IEI | | | | | | | | octet 1 | +| RA (low part) | | | | RA Type | | spare | | octet 2 | +| RA (high part) | | | | | | | | Octet 3 | +| T1' | | | | T3 (high part) | | | | octet 4 | +| T3 (low part) | | | T2 | | | | | octet 5 | + +**Figure 10.5.2.87.1: Request Reference Alt information element** + +**Table 10.5.2.87.1: Request Reference Alt information element** + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| RA , Random Access Information (octet 2 and octet 3) | | +| When included in an IMMEDIATE PACKET ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating 'Access Burst' method the 8 least significant bits of this field are used and contain the value of the 'Short ID' field included in the corresponding message (see 3GPP TS 44.060 [76]). | | +| When included in an IMMEDIATE PACKET ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst – part 1' the least significant 4 bits of this field are used and contain the value of the 'Random ID Low' field included in the corresponding message. | | +| When included in an IMMEDIATE PACKET ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst – part 2' all 12 bits of this field are used and contain the value of the 'Random ID High' field included in the corresponding message. | | +| RA Type , Random Access Type (octet 2) | | +| This field indicates the type of access request the IMMEDIATE PACKET ASSIGNMENT message sent in response to. This field is coded as follows: | | +| Bits | | +| 00 | Response to an EGPRS MULTILATERATION REQUEST message indicating 'Access Burst'. | +| 01 | Response to an EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst – part 1'. | +| 10 | Response to an EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst – part 2'. | +| 11 | Reserved | +| T1' (octet 3) | | +| The T1' field is coded as the binary representation of (FN div 1326) mod 32. | | + +**T3 (octet 3 and 4)** + +The T3 field is coded as the binary representation of FN mod 51. Bit 3 of octet 3 is the most significant bit and bit 6 of octet 4 is the least significant bit. + +**T2 (octet 4)** + +The T2 field is coded as the binary representation of FN mod 26. + +NOTE 1: The frame number, FN modulo 42432 can be calculated as $51 \times ((T3 - T2) \bmod 26) + T3 + 51 \times 26 \times T1'$ + +### 10.5.2.88 EC Packet Channel Description Type 3 + +The *EC Packet Channel Description Type 3* IE identifies the radio parameters applicable to a mobile station that has received an EC IMMEDIATE ASSIGNMENT TYPE 4 message on the EC-AGCH. + +The *EC Packet Channel Description Type 3* information element is coded according to the syntax specified below and described in table 10.5.2.88.1. + +The *EC Packet Channel Description Type 3* is a type 3 information element with 15 bits length. + +``` +< EC Packet Channel Description Type 3 > ::= + < QUARTER_HYPERFRAME_INDICATOR : bit (2) > + < DL_COVERAGE_CLASS : bit (2) > + < UL_COVERAGE_CLASS_EXTENDED : bit (2) > + < TSC Set : bit (1) > + < TSC : bit (3) > + < EC_MA_NUMBER : bit (5) > ; +``` + +Figure 10.5.2.88.1: *EC Packet Channel Description Type 3* information element + +**Table 10.5.2.88.1: *EC Packet Channel Description Type 3* information element** + +| | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------|-----|----------|-----|----------|-----|----------| +| QUARTER_HYPERFRAME_INDICATOR (2 bit field)
This field is coded as described in sub-clause 10.5.2.85.1. | | | | | | | | | +| DL_COVERAGE_CLASS (2 bit field)
This field is described in sub-clause 10.5.2.84. | | | | | | | | | +| UL_COVERAGE_CLASS_EXTENDED (2 bit field)

bit
2 1
0 0 UL CC5
0 1 Reserved
1 0 Reserved
1 1 Reserved
| 0 0 | UL CC5 | 0 1 | Reserved | 1 0 | Reserved | 1 1 | Reserved | +| 0 0 | UL CC5 | | | | | | | | +| 0 1 | Reserved | | | | | | | | +| 1 0 | Reserved | | | | | | | | +| 1 1 | Reserved | | | | | | | | +| TSC Set (1 bit field)
This field is described in sub-clause 10.5.2.84. | | | | | | | | | +| TSC (3 bit field)
This field is described in sub-clause 10.5.2.84. | | | | | | | | | +| EC_MA_NUMBER (5 bit field) | | | | | | | | | + +| | +|--------------------------------------------------| +| This field is described in sub-clause 10.5.2.84. | +|--------------------------------------------------| + +### 10.5.3 Void + +### 10.5.4 Call control information elements + +See 3GPP TS 24.008. + +### 10.5.5 GPRS mobility management information elements + +#### 10.5.5.0 General + +The content of the common information elements identified below is specified in the corresponding sub-clauses in 3GPP TS 24.008. + +10.5.5.1 (void) + +10.5.5.2 (void) + +10.5.5.3 (void) + +10.5.5.4 (void) + +10.5.5.5 (void) + +10.5.5.6 (void) + +10.5.5.7 (void) + +10.5.5.8 (void) + +10.5.5.8a (void) + +10.5.5.9 (void) + +10.5.5.10 (void) + +10.5.5.11 (void) + +10.5.5.12 (void) + +10.5.5.12a (void) + +10.5.5.13 (void) + +10.5.5.14 (void) + +10.5.5.15 Routing area identification + +See 3GPP TS 24.008. + +10.5.5.16 (void) + +10.5.5.17 (void) + +10.5.5.18 (void) + +10.5.5.19 (void) + +10.5.5.20 (void) + +10.5.5.21 (void) + +10.5.5.22 (void) + +10.5.5.23 (void) + +10.5.5.24 (void) + +10.5.5.25 (void) + +## 10.5.6 Session management information elements + +See 3GPP TS 24.008. + +## 10.5.7 GPRS Common information elements + +See 3GPP TS 24.008. + +## 10.5.8 GTTP information elements. + +### 10.5.8.1 LLC PDU Container + +The purpose of the *LLC PDU Container* information element is to carry an LLC PDU with upper layer information between the network and the mobile station. Within the scope of 3GPP TS 44.018 the content of the *LLC PDU* field is an array of octets. The usage of the contents of this transportation mechanism is defined in 3GPP TS 44.064. + +The *LLC PDU Container* information element is coded as shown in figure 10.5.8.1.1. + +The *LLC PDU Container* is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +![](13533a09243e784566d2227cb6ac60e5_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|---|---|-------------| +| LLC PDU Container IEI | | | | | | | | octet 1 | +| Length of LLC PDU Container contents | | | | | | | | octet 2 | +| LLC PDU | | | | | | | | octet 3 - n | + +Figure 10.5.8.1.1: *LLC PDU Container* information element + +| | +|--------------------------------------------------------------------------------------------------------------| +| LLC PDU (variable length field, octets 3 to n)
This field contains an LLC PDU; see 3GPP TS 44.064. | +|--------------------------------------------------------------------------------------------------------------| + +# 11 List of system parameters + +The description of timers in the following table should be considered a brief summary. The precise details are found in clauses 3 to 6, which should be considered the definitive descriptions. + +## 11.1 Timers and counters for radio resource management + +### 11.1.1 Timers on the mobile station side + +**T3110:** This timer is used to delay the channel deactivation after the receipt of a (full) CHANNEL RELEASE. Its purpose is to let some time for disconnection of the main signalling link. + +Its value is set to such that the DISC frame is sent twice in case of no answer from the network. (It should be chosen to obtain a good probability of normal termination (i.e. no time out of T3109) of the channel release procedure.) + +**T3112** The timer is used by a VGCS mobile when receiving segmented RP-Data message on the SACCH. The timer is started when receiving the first segment of a segmented RP-Data message for a group call that the MS is a member of, for which no previous segment has been received. + +It is stopped in the following situations: + +- The MS receives the complete RP-Data message +- The MS discards the message as a result of timer T3114 expiring for some other message +- The MS deletes the segment(s) (with SMS reference number n) because it has received a segment with a SMS reference number which is more than 4 higher (modulo 16) than that of the message corresponding to this timer +- The MS changes its channel +- The voice group call is cleared + +The value of the timer is 20 seconds. + +**T3114** The timer is used by a VGCS mobile when receiving a complete RP-Data message on the SACCH that is not the next in sequence message that is to be sent to the upper layer. + +It is stopped in the following situations: + +- The MS delivers the RP-Data message to the upper layer +- The MS changes its channel +- The voice group call is cleared + +The value of the timer is 10 seconds. + +**T3122:** This timer is used during random access or during dedicated channel assignment while in packet transfer mode, after the receipt of an IMMEDIATE ASSIGN REJECT message. + +Its value is given by the network in the IMMEDIATE ASSIGN REJECT message. + +**T3124:** This timer is used in the seizure procedure during a hand-over, when the two cells are not synchronized. + +Its purpose is to detect the lack of answer from the network to the special signal. + +Its value is set to 675 ms if the channel type of the channel allocated in the HANDOVER COMMAND is an SDCCH (+ SACCH); otherwise its value is set to 320 ms. + +**T3126:** This timer is started either + +after sending the maximum allowed number of CHANNEL REQUEST messages or EGPRS PACKET CHANNEL REQUEST messages during an immediate assignment procedure, + +or + +on receipt of an IMMEDIATE ASSIGNMENT REJECT message, + +or + +when a mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) has initiated the immediate assignment procedure, sent one or more CHANNEL REQUEST messages and received an implicit reject for the CS domain (see sub-clause 3.3.1.1.2), + +whichever occurs first. + +It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, an IMMEDIATE ASSIGNMENT EXTENDED message, or an IMMEDIATE PACKET ASSIGNMENT message (if supported). + +At its expiry, the immediate assignment procedure is aborted and the mobile station proceeds as described in sub-clause 3.3.1.1.2 or the Implicit Reject procedure is completed as described in sub-clause 3.3.1.1.3.2a. + +The minimum value of this timer is equal to the time taken by T+2S slots of the mobile station's RACH. S and T are defined in sub-clause 3.3.1.2. The maximum value of this timer is 5 seconds. + +**T3128:** This timer is started when the mobile station starts the uplink investigation procedure and the uplink is busy. + +It is stopped at receipt of the first UPLINK FREE message. + +At its expiry, the uplink investigation procedure is aborted. + +The value of this timer is set to 1 second. + +**T3130:** This timer is started after sending the first UPLINK ACCESS message during a VGCS uplink access procedure, or sending the first PRIORITY UPLINK REQUEST message during a VGCS priority uplink request procedure. + +It is stopped at receipt of a VGCS UPLINK GRANT message. + +It may be started a maximum of 3 times. On expiry of timer T3130 for the third time a rejection of the uplink request is indicated to the upper layers. + +The value of this timer is set to 5 seconds. + +**T3142:** The timer is used during packet access on CCCH and during packet access while in dedicated mode. It is started after the receipt of an IMMEDIATE ASSIGNMENT REJECT or a DTM REJECT or an EC IMMEDIATE ASSIGNMENT REJECT message. + +Its value is given by the network in the IMMEDIATE ASSIGNMENT REJECT or DTM REJECT message. + +**T3146:** This timer is started either + +after sending the maximum allowed number of CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or EC PACKET CHANNEL REQUEST or EGPRS MULTILATERATION REQUEST or EC MULTILATERATION REQUEST messages during a packet access procedure. + +or + +on receipt of an IMMEDIATE ASSIGNMENT REJECT or EC IMMEDIATE ASSIGNMENT REJECT message during a packet access procedure, + +or + +a mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) has initiated the packet access procedure, has sent one or more CHANNEL REQUEST or one or more EGPRS PACKET CHANNEL REQUEST or one or more EC PACKET CHANNEL REQUEST messages and received an implicit reject for the PS domain (see sub-clause 3.5.2.1.2 or 3.5.2.1.2a), + +whichever occurs first. + +It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, an IMMEDIATE ASSIGNMENT EXTENDED message, or an IMMEDIATE PACKET ASSIGNMENT message (if supported) or an EC IMMEDIATE ASSIGNMENT TYPE 1 message or an EC IMMEDIATE ASSIGNMENT TYPE 2 or an EC IMMEDIATE ASSIGNMENT TYPE 3 or EC IMMEDIATE ASSIGNMENT TYPE 4 message. + +At its expiry, if the packet access procedure is ongoing then it is aborted and the mobile station proceeds as described in sub-clause 3.5.2.1.2 or 3.5.2.1.2a or the Implicit Reject procedure is completed as described in sub-clause 3.3.1.1.3.2a or the EC Implicit Reject procedure is completed as described in sub-clause 3.5.2a.2. At expiry of timer T3146, if the radio access part of the MTA procedure is ongoing then it is terminated for the current cell and the mobile station MS tunes to the next cell in the list of applicable cells and continues the radio access part of the MTA procedure therein. + +For the case where a CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST has been sent the minimum value of this timer is equal to the time taken by T+2S slots of the mobile station's RACH. S and T are defined in sub-clause 3.3.1.2. The maximum value of this timer is 5 seconds. For the case where an EC PACKET CHANNEL REQUEST message has been sent the value of this timer is equal to the total number of downlink 51-multiframes it reads in an attempt to find a matching response (see sub-clause 3.5.2.1.2a). + +**T3148:** This timer is used during DTM establishment in dedicated mode. + +It is started after sending a DTM REQUEST message during a packet access procedure while in dedicated mode. + +It is stopped at the receipt of one of the following messages: + +- DTM ASSIGNMENT COMMAND; +- PACKET ASSIGNMENT; +- DTM REJECT; +- ASSIGNMENT COMMAND; +- HANDOVER COMMAND. + +At its expiry, the packet access procedure is aborted. + +Its value is 4 seconds. + +**T3164:** This timer is used during packet access using CCCH. It is started at the receipt of an IMMEDIATE ASSIGNMENT message or an IMMEDIATE PACKET ASSIGNMENT message (if supported). + +It is stopped at the transmission of a RLC/MAC block on the assigned temporary block flow, see 3GPP TS 44.060. + +At expire, the mobile station returns to the packet idle mode. + +The value of the timer is 5 seconds. + +**T3190:** The timer is used during packet downlink assignment on CCCH. It is started at the receipt of an IMMEDIATE ASSIGNMENT message or an IMMEDIATE PACKET ASSIGNMENT message (if supported) when in dedicated mode. + +It is stopped at the receipt of a RLC/MAC block on the assigned temporary block flow, see 3GPP TS 44.060. + +At expiry, the mobile station returns to the packet idle mode. + +The value of the timer is 5 seconds. + +**T3204:** This timer is used by a mobile station with non-GSM capabilities. The timer is started after sending the first CHANNEL REQUEST during a packet access procedure. The CHANNEL REQUEST was sent requesting a single block packet access and the purpose of the packet access procedure is to send a PACKET PAUSE message. + +It is stopped at the receipt of an IMMEDIATE ASSIGNMENT message granting a single block period on an assigned packet uplink resource. + +At expiry, the packet access procedure is aborted. + +The value of the timer is 1 second. + +**T3206** + +The timer is used by a VGCS mobile when receiving segmented notifications on the NCH. The timer is started when receiving a segment of a segmented notification for a group call that the MS is a member for which no previous segment has been received. + +It is stopped in the following situations: + +- The MS receives the second segment +- The MS joins another call +- The value of NLN changes +- The MS reselects to another cell + +The value of the timer is 5 second. + +**T3208** + +The timer is used by a VGCS mobile when receiving segmented notifications on the FACCH. The timer is started when receiving the first segment of a segmented notification for a group call that the MS is a member for which no previous segment has been received. + +It is stopped in the following situations: + +- The MS receives the complete message +- The MS joins another call +- The MS performs Handover to another cell + +The value of the timer is 1 second. + +**T3210** + +The timer is used by a VGCS mobile when receiving segmented notifications on the PCH. The timer is started when receiving the first segment of a segmented notification for a group call that the MS is a member for which no previous segment has been received. + +It is stopped in the following situations: + +- The MS receives the complete message +- The MS leaves Idle mode +- Notifications for another group call are received on the PCH + +The value of the timer is 5 seconds. + +**T3220** + +The timer is used by an MBMS capable mobile station when receiving pre-notification of an MBMS session. The timer is started when receiving a PAGING REQUEST message containing an MBMS pre-notification that the mobile station shall receive. + +It is stopped at the receipt of a PAGING REQUEST message containing a notification of the same session as when starting this timer, or if any other RR procedure on CCCH not related to MBMS is triggered or a notification is received for a higher priority session while the timer is running. + +At expiry, the mobile station returns to DRX mode unless it is engaged in any other MBMS session and then stays in broadcast/multicast receive mode. + +The value of the timer is 46 s. + +**T3222:** + +An instance of the timer may be used by an MBMS capable mobile station in dedicated mode during the notification of MBMS. An instance of this timer may be started at the receipt of an MBMS ANNOUNCEMENT message when in dedicated mode. + +The instance of this timer is stopped when the mobile enters packet idle mode. + +At expiry of an instance of this timer, the mobile station discards the MBMS related information stored upon receipt of the corresponding MBMS ANNOUNCEMENT message. + +The value of the timer is defined in sub-clause 3.4.27.2.3. + +**T3224:** The timer start at on receipt of a VGCS\_UPLINK\_GRANT message aimed to another mobile station. + +It is stopped when the mobile station received an UPLINK BUSY message. + +At expiry, the mobile station shall follow the same procedures as for expiry of timer T3130. + +The value of the timer is 1 s. + +**T3230:** The timer is used to control the validity period of individual priorities. It is started on receipt of the individual priorities for cell reselection via dedicated signalling or on inter-RAT reselection to GERAN if the corresponding timer in the source RAT (i.e., T320 in E-UTRA, and T322 in UTRA) was running when reselection occurred. + +When one of the conditions specified in subclause 3.2.3.3 is met, the MS shall stop T3230 and delete the corresponding individual priorities. + +At expiry the mobile station shall delete the corresponding individual priorities. + +**T3232:** The timer is used to control the length of the non-DRX mode period in which the mobile station is acquiring an ETWS Primary Notification message. It is started on receipt of a first PAGING REQUEST TYPE 1 message containing a valid segment of an ETWS Primary Notification message. + +It is stopped in the following situations: + +The mobile station receives the complete ETWS Primary Notification message + +Upon initiating cell reselection or connection establishment procedures + +The timer is restarted if the mobile station receives an indication of a new ETWS Primary Notification message prior to acquiring a complete ETWS Primary Notification message. + +At expiry the mobile station shall discard all segments of the partially received ETWS Primary Notification message and re-enter DRX mode. + +The value of the timer is 5 seconds. + +**T3234:** The timer is used to prevent a mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) from requesting CS resources (see sub-clause 3.3.1.1.3.2a). When a mobile station starts an implicit reject timer it selects a value randomly drawn from a uniform probability distribution within the set {10.0, 10.1, 10.2, ...200.0} seconds (inclusive). + +It is started when the Implicit Reject procedure is initiated following mobile station reception of an implicit reject indication for the CS domain prior to sending any CHANNEL REQUEST messages on the RACH or when T3126 expires (see sub-clause 3.3.1.1.3.2a). + +It is stopped in the following cases: + +- The mobile station responds to a PAGING REQUEST message +- The mobile station performs cell re-selection. + +At expiry, the mobile station may once again access the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" and request CS resources. + +**T3236:** The timer is used to prevent a mobile station accessing the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" (see 3GPP TS 24.008) from requesting PS resources (see sub-clause 3.3.1.1.3.2a and sub-clause 3.5.2a.2). When a mobile station starts an implicit reject timer it selects a value randomly drawn from a uniform probability distribution within the set {10.0, 10.1, 10.2, ...200.0} seconds (inclusive). + +It is started when T3146 expires (see sub-clause 3.3.1.1.3.2a or 3.5.2a.2). + +It is stopped in the following cases: + +- The mobile station responds to a PAGING REQUEST or an EC PAGING REQUEST message +- The mobile station performs cell re-selection. + +At expiry, the mobile station may once again access the network when the low priority indicator is set to "MS is configured to NAS signalling low priority" and request PS resources. + +## 11.1.2 Timers on the network side + +**T3101:** This timer is started when a channel is allocated with an IMMEDIATE ASSIGNMENT message. It is stopped when the MS has correctly seized the channels. + +Its value is network dependent. + +NOTE 1: It could be higher than the maximum time for a L2 establishment attempt. + +**T3103:** This timer is started by the sending of a HANDOVER message and is normally stopped when the MS has correctly seized the new channel. Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost. + +Its value is network dependent. + +NOTE 2: It could be higher than the maximum transmission time of the HANDOVER COMMAND, plus the value of T3124, plus the maximum duration of an attempt to establish a data link in multiframe mode.) + +**T3105:** This timer is used for the repetition of the PHYSICAL INFORMATION message during the handover procedure. + +Its value is network dependent. + +NOTE 3: This timer may be set to such a low value that the message is in fact continuously transmitted. + +**T3107:** This timer is started by the sending of an ASSIGNMENT COMMAND or a DTM ASSIGNMENT COMMAND message and is normally stopped when the MS has correctly seized the new RR channels. + +Its purpose is to release the new channels (and, in the case of Enhanced DTM CS establishment, the old PS resources) if the MS is lost and, except when used for Enhanced DTM CS Establishment, to keep the old channel sufficiently long for the MS to be able to return to the old channels. + +Its value is network dependent. + +NOTE 4: It could be higher than the maximum transmission time of the ASSIGNMENT COMMAND message plus twice the maximum duration of an attempt to establish a data link multiframe mode. + +**T3109:** This timer is started when a lower layer failure is detected by the network, when it is not engaged in a RF procedure. It is also used in the channel release procedure. + +Its purpose is to release the channels in case of loss of communication. + +Its value is network dependent. + +NOTE 5: Its value should be large enough to ensure that the MS detects a radio link failure. + +**T3111:** This timer is used to delay the channel deactivation after disconnection of the main signalling link. Its purpose is to let some time for possible repetition of the disconnection. + +Its value is equal to the value of T3110. + +**T3113:** This timer is started when the network has sent a PAGING REQUEST message and is stopped when the network has received the PAGING RESPONSE message. + +Its value is network dependent. + +NOTE 6: The value could allow for repetitions of the Channel Request message and the requirements associated with T3101. + +**T3115:** This timer is used for the repetition of the VGCS UPLINK GRANT message during the uplink access procedure or priority uplink request procedure. + +Its value is network dependent. + +NOTE 7: This timer may be set to such a low value that the message is in fact continuously transmitted. + +**T3121:** This timer is started by the sending of an INTER SYSTEM TO UTRAN HANDOVER COMMAND message or of an INTER SYSTEM TO E-UTRAN HANDOVER COMMAND and is normally stopped when the MS has correctly seized the UTRAN channel(s) or E-UTRAN channel(s). Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost. + +Its value is network dependent. + +**T3123:** This timer is started by the sending of an INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message and is normally stopped when the MS has correctly seized the CDMA2000 channel(s). Its purpose is to keep the old channels sufficiently long for the MS to be able to return to the old channels, and to release the channels if the MS is lost. + +Its value is network dependent. + +**T3141:** This timer is started when a temporary block flow is allocated with an IMMEDIATE ASSIGNMENT or an IMMEDIATE PACKET ASSIGNMENT or an EC IMMEDIATE ASSIGNMENT TYPE 1 message during a packet access procedure. It is stopped when the mobile station has correctly seized the temporary block flow. + +Its value is network dependent. + +**T3151:** This timer is used by the network to supervise the periodic transmission of the UPLINK BUSY message on the FACCH of the voice group call channel (see sub-clause 3.3.1.2.2a.2.2). + +Its value is network dependent. + +**T3153:** This timer is used by the network to supervise the periodic transmission of the VGCS ADDITIONAL INFORMATION message on the SACCH of the voice group call channel (see subclause 3.4.15.3a). + +Its value is network dependent. + +**T3155:** In a network supporting validation of Priority Uplink Requests, the timer T3155 supervises the broadcast of a new token after a valid Priority Uplink Request has been received. + +If a Priority Uplink Request is received, and the token matches the token in the BSS then the request is accepted, the token is invalidated and T3155 is started. On T3155 expiry a new token, and the priority of the accepted request, shall be sent in the UPLINK BUSY message on the FACCH of the voice group call channels. The T3155 timer should be set to a value that allows other service subscribers who sent a Priority Uplink Request at the same time as the one accepted by the network, to be back on the voice group call channel, in order to receive the new token. + +The default value for T3155 is 500ms. + +**T3157:** In a network supporting validation of Priority Uplink Requests, the timer T3157 supervises an additional validity period for an unused (old) token. When T3151 (supervising the periodic UPLINK BUSY) expires a new token is sent in the UPLINK BUSY message on the FACCH of the voice group call channels and timer T3157 is started. If a Priority Uplink Request is received before T3157 expires and the token matches either token in the BSS (old or new), the request is considered to be valid, both tokens in the BSS are invalidated and T3157 is stopped. If T3157 expires (i.e. no valid Priority Uplink Request has been received within T3157 seconds) the old token is invalidated. + +The value of timer T3157 is operator specific. The value chosen should allow for the reception of requests from service subscribers, who have left the group call channel before receipt of the UPLINK BUSY message with the new token. + +Its default value is 1s. + +### 11.1.3 Other parameters + +**Ny1:** The maximum number of repetitions for the PHYSICAL INFORMATION message during a handover (see sub-clause 3.4.4.2.2). The value is network dependent. + +**Ny2:** The maximum number of repetitions for the VGCS UPLINK GRANT message during an uplink access procedure or priority uplink request procedure (see sub-clause 3.3.1.2.2). The value is network dependent. + +## 11.2 Timers of mobility management + +See 3GPP TS 24.008. + +## 11.3 Timers of circuit-switched call control + +See 3GPP TS 24.008. + +--- + +## Annex A (informative): Example of subaddress information element coding + +See 3GPP TS 24.008. + +--- + +## Annex B (normative): Compatibility checking + +See 3GPP TS 24.008. + +--- + +## Annex C (normative): Low layer information coding principles + +See 3GPP TS 24.008. + +--- + +## Annex D (informative): Examples of bearer capability information element coding + +See 3GPP TS 24.008. + +--- + +## Annex E (informative): + +### Comparison between call control procedures specified in 3GPP TS 24.008 and ITU-T Recommendation Q.931 + +See 3GPP TS 24.008. + +--- + +## Annex F (informative): GSM specific cause values for radio resource management + +This annex is informative. + +Cause value = 0 Normal event; + +indicates that the channel is released because of a normal event or that an assignment or handover is successfully, and normally, completed. + +Cause value = 1 Abnormal release, unspecified; + +indicates that the channel is released because of an abnormal event without specifying further reasons. + +Cause value = 2 Abnormal release, channel unacceptable; + +indicates that the channel type or channel characteristics are not acceptable. + +Cause value = 3 Abnormal release, timer expired; + +indicates that the release is caused by a timer expiry. + +Cause value = 4 Abnormal release, no activity on the radio path; + +indicates that some supervisory function has detected that the channel is not active. + +Cause value = 5 Pre-emptive release; + +indicates that the channel is released in order to be allocated to a call with priority (e.g. an emergency call). + +Cause value = 6 UTRAN configuration unknown; + +indicates that the MS does not know the UTRAN predefined configuration (i.e. was not read from UTRAN Channels) or that the MS does not have the capability to handle the requested default configuration. + +Cause value = 8 Handover impossible, timing advance out of range; + +indicates that a handover is unsuccessful because the target BTS is beyond the normal range and the target BTS would not accept an out of range timing advance. + +Cause value = 9 Channel mode unacceptable + +indicates that the MS does not have the capability to handle the requested mode or type of channel. + +Cause value = 10 Frequency not implemented + +indicates that the MS does not have the capability to operate on (at least one of) the requested frequency(ies). + +Cause value = 11 Originator or talker leaving group call area + +indicates that VGCS uplink or VBS call is released because the mobile talking is outside the group call area + +Cause value = 12 Lower layer failure + +indicates that a lower layer failed to establish a connection on the new channel. + +Cause value = 65 Call already cleared; + +indicates that a handover is unsuccessful because the connection has been released by the network or the remote user. + +Cause value = 95 Semantically incorrect message; + +See annex H, sub-clause H5.10. + +Cause value = 96 Invalid mandatory information; + +See annex H, sub-clause H6.1. + +Cause value = 97 Message type non-existent or not implemented; + +See annex H, sub-clause H6.2. + +Cause value = 98 Message type not compatible with protocol state; + +See annex H, sub-clause H6.3 + +Cause value = 100 Conditional IE error; + +See annex H, sub-clause H6.5 + +Cause value = 101 No cell allocation available; + +indicates that an assignment or handover is unsuccessful because the MS has no current CA. + +Cause value = 111 Protocol error unspecified; + +See annex H, sub-clause H6.8. + +--- + +## Annex G (informative): GSM specific cause values for mobility management + +See 3GPP TS 24.008. + +--- + +## Annex H (informative): GSM specific cause values for call control + +See 3GPP TS 24.008. + +--- + +## Annex I (informative): GSM specific cause values for session management + +See 3GPP TS 24.008. + +## Annex J (informative): Algorithm to encode frequency list information elements + +This annex is informative. + +### J.1 Introduction + +Some information elements encode frequency lists with a special method. The main specification specifies the meaning of the fields and hence the way to decode them, but the corresponding encoding algorithm is difficult to infer from the decoding algorithm. This annex is intended as an aid for implementers of the encoding algorithm. + +It could be shown that any set of frequency with less or the same number of frequencies as the number of words can be encoded with a careful choice of F1, F2, and so on, i.e. that a set of $W_i$ can be found so that the decoding algorithm given in the main sub-clause will give back the frequency set. The right order is not the order of the frequency values. + +### J.2 General principle + +The encoding algorithm is based on a recursive dichotomy of both the range (i.e. the set of values that are possible) and the subset (the values to encode). + +The dichotomy is best understood if the range is seen as a circle. For instance, for the 1023 range. + +![Circular arrangement of 0..1023](208fd2da57f31de2a5ddaa409300f7f6_img.jpg) + +The diagram shows a circle representing the range of values from 0 to 1023. The circle is divided into two halves by a vertical diameter. The top half is labeled with values 1022, 1023, 0, 1, 2, and 3. The bottom half is labeled with values 512, 511, 510, and 509. The values are arranged in a clockwise direction starting from the top of the circle. + +Circular arrangement of 0..1023 + +**Figure J.1: Circular arrangement of 0..1023** + +The dichotomy consists in finding a value in the subset such that the diameter determined by this value splits the subset in two equal or nearly equal subsets. In the following case, we see that value 290 is acceptable (the two subsets have 3 elements), when value 250 is not acceptable (the two subsets have 4 and 2 elements): + +![Figure J.2: Example of dichotomy. A circle representing a range of values from 0 to 1000. A horizontal line at 500 represents the full range. A diagonal line passing through the center represents a pivot value. Tick marks on the circle are labeled: 50, 90, 250, 290, 480, 600, 650. The pivot value is indicated by the intersection of the diagonal line and the circle.](992e26bbe1f16e8a6ad84f8988034477_img.jpg) + +Figure J.2: Example of dichotomy. A circle representing a range of values from 0 to 1000. A horizontal line at 500 represents the full range. A diagonal line passing through the center represents a pivot value. Tick marks on the circle are labeled: 50, 90, 250, 290, 480, 600, 650. The pivot value is indicated by the intersection of the diagonal line and the circle. + +**Figure J.2: Example of dichotomy** + +The pivot value is part of the information field, then the two subsets are renumbered and the same algorithm is applied again on each of them. Because the range is halved at each step, the number of bits needed to encode a pivot value is 1 bit less than the number of bits needed to encode the parent pivot value. + +The convention is that if the number of values is even, the left subset (that is to say the values that can be expressed as the pivot value minus some integer between 1 and half the range) will have 1 element more than the right subset. + +At each step the subset is numbered from 0 to the range minus 1. The coding in the information field of the pivot value is its value as renumbered, plus 1. Value 0 is reserved to indicate no element. + +The order of appearance in the information field of the successive pivot values is particular. If we present the values as organized as a tree, with the left child being the pivot of the left subset and the right child the pivot of the right subset, the order of appearance is given by the following tree: + +![A binary tree diagram showing the order of appearance of pivot values. The root node is 1. Node 1 has two children: 2 (left) and 3 (right). Node 2 has two children: 4 (left) and 6 (right). Node 3 has two children: 5 (left) and 7 (right). Node 4 has two children: 8 (left) and 12 (right). Node 6 has two children: 10 (left) and 14 (right). Node 5 has two children: 9 (left) and 13 (right). Node 7 has two children: 11 (left) and 15 (right). Below the tree, the text '(and so on)' is centered.](cec58cb35e9803b6995668542162f534_img.jpg) + +``` + +graph TD + 1((1)) --> 2((2)) + 1 --> 3((3)) + 2 --> 4((4)) + 2 --> 6((6)) + 3 --> 5((5)) + 3 --> 7((7)) + 4 --> 8((8)) + 4 --> 12((12)) + 6 --> 10((10)) + 6 --> 14((14)) + 5 --> 9((9)) + 5 --> 13((13)) + 7 --> 11((11)) + 7 --> 15((15)) + +``` + +(and so on) + +A binary tree diagram showing the order of appearance of pivot values. The root node is 1. Node 1 has two children: 2 (left) and 3 (right). Node 2 has two children: 4 (left) and 6 (right). Node 3 has two children: 5 (left) and 7 (right). Node 4 has two children: 8 (left) and 12 (right). Node 6 has two children: 10 (left) and 14 (right). Node 5 has two children: 9 (left) and 13 (right). Node 7 has two children: 11 (left) and 15 (right). Below the tree, the text '(and so on)' is centered. + +This order has been chosen so that: + +- whatever the number $N$ of elements in the set, the meaningful nodes are the first $N$ and the value for all nodes from $N+1$ on are null (if sent); +- the tree and all subtrees are balanced. + +Important properties of these trees are used in the algorithms (with generation 1 corresponding to the root): + +- Generation $g$ contains $2^{g-1}$ nodes, and their indices are $2^{g-1}$ to $2^g-1$ ; +- For generation $g$ , nodes $2^{g-1}$ to $2^{g-1}+2^{g-2}-1$ are left children, the others are right children; +- If node $k$ belongs to generation $g$ , its left child is node $k + 2^{g-1}$ , and its right child is $k + 2^g$ ; + +- Reciprocally, if k is a left child from generation g, its parent node is node $k - 2^{g-2}$ , and if k is a right child of generation g, its parent is node $k - 2^{g-1}$ . + +## J.3 Performances + +The number of bits needed to encode a given set of values depends on the number of values and on the range they can span. + +For the application on the BCCH and the SACCH (CA and BA information ) 16 octets are available, and the number of frequencies that can be encoded in one information element is the following. + +| Range | Number of frequencies | +|-------------|-----------------------------------| +| 513 to 1024 | 2 to 16 (17 if frequency 0 is in) | +| 257 to 512 | 2 to 18 | +| 129 to 256 | 2 to 22 | +| 65 to 128 | 2 to 29 | +| up to 64 | any | + +With two messages (for the BA) the number of frequencies that can be encoded is the following. + +| Range | Number of frequencies | +|-------------|-----------------------| +| 513 to 1024 | 2 to 36 (NOTE 1) | +| 257 to 512 | 2 to 40 (NOTE 2) | +| 129 to 256 | 2 to 51 (NOTE 3) | +| up to 64 | any | + +NOTE 1: A 1024 range can be split cyclically in to two 512 ranges each with less than 18 frequencies; each subset is coded in one message with 512 range format. + +NOTE 2: A 512 range can be split in to two consecutive 256 ranges. If both sub-ranges contain 22 frequencies or less, it is possible to code each of these in a messages using the 256 range format. Otherwise one of the two ranges contains 23 frequencies or more: 22 of them can be coded in one message using the 256 range format and the remaining frequencies (numbering less than or equal to 18) can be coded in the other message using the 512 range format. + +NOTE 3: The principles described in notes 1 and 2, above apply in this case. + +The frequency short list information element allows the following. + +| Range | Number of frequencies | +|-------------|---------------------------------| +| 513 to 1024 | 2 to 7 (8 if frequency 0 is in) | +| 257 to 512 | 2 to 8 | +| 129 to 256 | 2 to 9 | +| 65 to 128 | 2 to 12 | +| up to 64 | any | + +The number of frequencies as a function of the range and the length in octets of the variable length frequency list information element (including the message type and length fields) is given by table J.1. + +**Table J.1: Performance of the variable length frequency list information element** + +| Range (octets) | 513 to 1024 | 257 to 512 | 129 to 256 | up to 128 | variable bit map | +|----------------|-------------|------------|------------|-----------|------------------| +| 5 | 1 | 1 | 1 | 1 | 8 | +| 6 | 2 | 2 | 3 | 3 | 16 | +| 7 | 3 | 3 | 4 | 4 | 24 | +| 8 | 4 | 4 | 5 | 6 | 32 | +| 9 | 5 | 6 | 6 | 8 | 40 | +| 10 | 6 | 7 | 8 | 10 | 48 | +| 11 | 7 | 8 | 9 | 12 | 56 | +| 12 | 9 | 9 | 11 | 14 | 64 | +| 13 | 10 | 11 | 13 | 16 | 72 | +| 14 | 11 | 12 | 14 | 18 | 80 | +| 15 | 12 | 13 | 16 | 21 | 88 | +| 16 | 13 | 15 | 18 | 24 | 96 | +| 17 | 14 | 16 | 20 | 26 | 104 | +| 18 | 16 | 18 | 22 | 29 | 112 | +| 19 | 17 | 19 | 24 | 32 | 120 | +| 20 | 18 | 21 | 26 | -- | 128 | +| 21 | 20 | 22 | 28 | | 136 | +| 22 | 21 | 24 | 30 | | 144 | +| 23 | 22 | 26 | 32 | | 152 | +| 24 | 24 | 27 | 34 | | 160 | +| 25 | 25 | 29 | 37 | | 168 | +| 26 | 26 | 30 | 40 | | 176 | +| 27 | 28 | 32 | 42 | | 184 | +| 28 | 29 | 34 | 45 | | 192 | +| 29 | 30 | 36 | 48 | | 200 | +| 30 | 32 | 38 | 50 | | 208 | +| 31 | 33 | 40 | 53 | | 216 | +| 32 | 35 | 42 | 56 | | 224 | + +## J.4 Encoding algorithm + +The choice is done recursively as given by the following programs, written in ADA: + +Let us define the recursive procedure: + +``` +procedure ENCODE_SUBTREE(in INDEX : INTEGER; + in SET : SET_OF_VALUE; + in RANGE : INTEGER); +``` + +This procedure is given a set of integer values and an index. It chooses one of those values and computes the corresponding W(INDEX) (considered as a global variable), it splits the set less the value in two equal or nearly equal subsets, and calls itself recursively for each of those subsets, with suitable INDEX. + +Assumption: all values in SET lie (inclusively) between 0 and RANGE-1, and they are all distinct. + +As written, the program does not assume special values for the range. With a range such as $2^k-1$ , some expressions can be simplified. + +``` +Declarative part: + INDEX_IN_SET : INTEGER; +begin +``` + +First the program tests the leaf conditions : + +``` +if SET'SIZE=0 then + W(INDEX) := 0; + return; +elsif SET'SIZE=1 then + W(INDEX) := 1 + SET(1); + return; +end if; +``` + +The following program finds a value in the set such that exactly $(\text{SET'SIZE}-1)/2$ values from the set are between this value plus 1 and this value plus half the range : + +``` +declare +N : INTEGER; +J : INTEGER; +begin +for I in 1..SET'SIZE loop +N:=0; +for J in 1..SET'SIZE loop +if (SET(J)-SET(I)) mod RANGE <= (RANGE-1)/2 then +N := N+1; +end if; +end loop; + +``` + +The test compares N-1 because the possible pivot value is counted. + +``` +if N-1 = (SET'SIZE-1)/2 then +INDEX_IN_SET := I; +exit; +end if; +end loop; +end; +``` + +INDEX\_IN\_SET is then the index in the list of the pivot value. + +The following sets W(INDEX) + +``` +W(INDEX) := SET(INDEX_IN_SET) + 1; +``` + +Then the program does the same thing for the two halves of the range delimited by W(INDEX) and W(INDEX) +RANGE/2. First the left subset: + +``` +declare +SUBSET : SET_OF_VALUE(1..SET'SIZE/2); +SUBSET_INDEX : INTEGER; +ORIGIN_VALUE : INTEGER; +begin +ORIGIN_VALUE := (SET(INDEX_IN_SET] + (RANGE-1)/2 ++ 1) mod RANGE; +SUBSET_INDEX:=1; +for I in 1..SET'SIZE loop +if (SET(I)-ORIGIN_VALUE) mod RANGE) < RANGE/2 then +SUBSET(SUBSET_INDEX) := +(SET(I) - ORIGIN_VALUE) mod RANGE; +SUBSET_INDEX := SUBSET_INDEX + 1; +end if; +end loop; +ENCODE_SUBTREE( +INDEX := INDEX + +GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX), +SET := SUBSET, +RANGE := RANGE/2); +end; +``` + +Then the right subset: + +``` +declare +SUBSET : SET_OF_VALUE(1..(SET'SIZE-1)/2); +SUBSET_INDEX : INTEGER; +ORIGIN_VALUE : INTEGER; +begin +ORIGIN_VALUE := (SET(INDEX_IN_SET] + 1) mod RANGE; +SUBSET_INDEX:=1; +for I in 1..SET'SIZE loop +if (SET(I)-ORIGIN_VALUE) mod RANGE) < RANGE/2 then +SUBSET(SUBSET_INDEX) := +(SET(I) - ORIGIN_VALUE) mod RANGE; +SUBSET_INDEX := SUBSET_INDEX + 1; +end if; +end loop; +ENCODE_SUBTREE( +INDEX := INDEX + +2*GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX), +SET := SUBSET, + +``` + +``` + +RANGE := (RANGE-1)/2; +end; + +end ENCODE_SUBTREE; + +``` + +The initial call of the procedure depends on the format. Given some set to encode, the first problem is to verify that it can be encoded, and by so doing to choose the format. + +First the encoding process must find the minimum range of the set, that is to say the minimum value $R$ such that there exists one frequency $F_0$ in the set such that all frequencies in the set can be written $(F_0 + N) \bmod 1024$ , with some $N$ , $0 \leq N \leq R-1$ . The choice of the format depends on $R$ and the number of frequencies : the 512 range format can be chosen only if $R \leq 512$ , the 256 range format can be chosen only if $R \leq 256$ , the 128 range format can be chosen only if $R \leq 128$ . + +If the chosen format is "1024 range", then the program must first check if frequency 0 is in the set. If so the $F_0$ subfield is set to 1, and frequency 0 is removed from the set. Otherwise, the $F_0$ subfield is set to 0. Then ENCODE\_SUBTREE is called with INDEX := 1, SET set to the set of values equal to the ARFCN of all frequencies minus 1, and RANGE := 1023. + +If the chosen format is "512 range", "256 range" or "128 range", $F_0$ is chosen as ORIG-ARFCN and ENCODE\_SUBTREE is called with INDEX := 1, SET set to the set of values equal to the ARFCN of all frequencies except $F_0$ , minus $F_0+1$ , and RANGE set respectively to 511, 255 or 127. + +## J.5 Decoding + +The decoding algorithm, as given below, is the inverse transform of the program given in the previous sub-clause, for the specific case where the original range is a power of 2 minus 1. It is given a set of integer values $W(i)$ , and an original range $R$ , and it builds a set of values from $0..R-1$ . + +The program is here written so that the fact that it is the inverse of the encoding program needs no more proof. + +``` + +procedure DECODE(in W : array <> of INTEGER; + out SET : SET_OF_VALUE; + in ORIGINAL_RANGE : INTEGER); + + -- local variables + INDEX : 1..W'SIZE; RANGE : INTEGER; + N : INTEGER; + + begin + for K in 1..W'SIZE loop + +``` + +The next loop follows the tree from child to parent, from the node of index $K$ to the root (index 1). For each iteration the node of index INDEX is tackled. The corresponding range is RANGE, and N is the value of the element in the range defined by the node. + +The data are set to their initial values : + +``` + +INDEX := K; +RANGE := ORIGINAL_RANGE / GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); +N := W(INDEX) - 1; + +while INDEX>1 loop + +``` + +Due to the assumption that the original range is a power of two minus one, the range for the parent node can be easily computed, and does not depend upon whether the current node is a left or right child : + +``` + +RANGE := 2*RANGE + 1; + +``` + +Let us note $J := 2^{g-1}$ , $g$ being the generation of node INDEX. We have $J = \text{GREATEST\_POWER\_OF\_2\_LESSER\_OR\_EQUAL\_TO}(\text{INDEX})$ . + +The numbering used in the tree is such that the nodes of index $J$ to $J + J/2 - 1$ are left children, and the nodes of index $J/2$ to $J+J-1$ are right children. Hence an easy test to distinguish left and right children: + +``` + +if 2*INDEX < +3*GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX) + +``` + +``` +then -- left child +``` + +The next computation gives the index of the parent node of the node of index INDEX, for a left child : + +``` +INDEX := INDEX - +GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX)/2; +``` + +The next formula is the inverse of the renumbering appearing in the encoding for a left child. It gives the value of the parent node in the range defined by the grand-parent node: + +``` +N := (N + W(INDEX) - 1 + (RANGE-1)/2 + 1) +mod RANGE; +else -- right child +``` + +The next computation gives the index of the parent node of the node of index INDEX, for a right child : + +``` +INDEX := INDEX - GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); +``` + +The next formula is the inverse of the renumbering appearing in the encoding for a right child: + +``` +N := (N + W(INDEX) - 1 + 1) mod RANGE; +end if; +end loop; +F(K) := N; +end loop; +end; +``` + +A careful study will show that the programs given in the main part of the Technical Specification are equivalent to the one presented here. The main difference is the use of different remnant variables to remove most of the calls to the function giving the greatest power of 2 less than or equal to some integer. + +The decoding must be terminated by the correction specific to the format. + +## J.6 A detailed example + +Let us take the following subset of 16 elements of the set [0..1023] : [13, 71, 122, 191, 251, 321, 402, 476, 521, 575, 635, 701, 765, 831, 906, 981] + +Range 1024 format will be used. Frequency 0 is not in the set, thus field F0 is set to 0. The set is renumbered, so as to give a subset of 0..1022 : [12, 70, 121, 190, 250, 320, 401, 475, 520, 574, 634, 700, 764, 830, 905, 980]. + +For the first node (corresponding to W(1)), the value 121 satisfies the requirements. The opposite value is $121 + 511 = 632$ . There are 8 values between 633 and 120 (namely the left-hand subset 634, 700, 764, 830, 905, 980, 12 and 70), and 7 values between 122 and 632 (namely the right-hand subset 190, 250, 320, 401, 475, 520 and 574). + +The encoded value W(1) is $121 + 1$ , i.e. 122. + +The second node (corresponding to W(2)) is the left-hand child of the first node. The corresponding subtree has to encode for the left-hand subset, renumbered beginning at 633. This gives the following 8 element subset of 0..510, ordered as resulting from the example of algorithm: [402, 460, 1, 67, 131, 197, 272, 347]. Out of these values, 1 splits the set in 4 and 3, and the encoded value W(2) is 2. + +Similarly, the third node (W(3)) is the right-hand child of the first node and then the corresponding subtree encodes for the right-hand subset, renumbered starting at 122. This gives the following set of 0..510: [68, 128, 198, 279, 353, 398, 452]. Out of these values, 68 splits the set into 3 and 3, and the encoded value W(3) is 69. + +The same method is applied for all nodes, giving the following encoded values per node: + +| Node | Value | +|------|-------| +| 1 | 122 | +| 2 | 2 | +| 3 | 69 | +| 4 | 204 | +| 5 | 75 | +| 6 | 66 | +| 7 | 60 | +| 8 | 70 | +| 9 | 83 | +| 10 | 3 | +| 11 | 24 | +| 12 | 67 | +| 13 | 54 | +| 14 | 64 | +| 15 | 70 | +| 16 | 9 | + +The encoding then consists in formatting, in that order: + +- 122 on 10 bits, then 2 and 69 on 9 bits each, then 204, 75, 66 and 60 on 8 bits each, then 70, 83, 3, 24, 67, 54, 64 and 70 on 7 bits each, and finally 9 on 6 bits. + +Conversely the decoding can be done easily. For instance for node 2, the original value is: + +- $(122 - 512 + 2) \bmod 1023 = 635$ . + +For node 14, we have as original value: + +- $(122 - 512 + (2 + (66 + 64) \bmod 255) \bmod 511) \bmod 1023 = 765$ . + +## Annex K (informative): Default Codings of Information Elements + +This annex is informative. + +The information in this annex does NOT define the value of any IEI for any particular message. This annex exists to aid the design of new messages, in particular with regard to backward compatibility with phase 1 mobile stations. + +### K.1 Common information elements + +For the common information elements see 3GPP TS 24.008 Annex K. + +### K.2 Radio Resource management information elements + +For the Radio Resource management information elements listed below, the default coding of the information element identifier bits is summarized in table K.2. + +**Table K.2: Default information element identifier coding +for Radio Resource management information elements** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | Reference | sub-clause | +|---|---|---|---|---|---|---|---|--------------------------------------------|-------------|------------| +| 1 | : | : | : | - | - | - | - | Type 1 info elements | | | +| 1 | 0 | 0 | 1 | - | - | - | - | Cipher Mode Setting | 10.5.2.9 | | +| 1 | 0 | 1 | 0 | - | - | - | - | Cipher Response | 10.5.2.10 | | +| 1 | 0 | 1 | 1 | - | - | - | - | Note | | | +| 1 | 1 | 0 | 1 | - | - | - | - | Synchronization Indication | 10.5.2.39 | | +| 1 | 1 | 1 | 0 | - | - | - | - | Channel Needed | 10.5.2.8 | | +| 0 | : | : | : | : | : | : | : | Type 3 & 4 info elements | | | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | Frequency Short List | 10.5.2.14 | | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Frequency List | 10.5.2.13 | | +| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | Note | | | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Cell Channel Description | 10.5.2.1b | | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | Channel Mode | 10.5.2.6 | | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | Channel Description | 10.5.2.5 | | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | Channel Mode 2 | 10.5.2.7 | | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | Mobile Time Difference on Hyperframe level | 10.5.2.21ab | | +| 0 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | Note | | | +| 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | Frequency Channel Sequence | 10.5.2.12 | | +| 0 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | Note | | | +| 0 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | Note | | | +| 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | Note | | | +| 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | Extended TSC Set, after time | 10.5.2.82 | | +| 0 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | Extended TSC Set, before time | 10.5.2.82 | | +| 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | Note | | | +| 0 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | Mobile Allocation | 10.5.2.21 | | +| 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | BA range | 10.5.2.1 | | +| 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | Note | | | +| 0 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | Note | | | +| 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | Note | | | +| 0 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | Mobile Time difference | 10.5.2.21a | | +| 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | Note | | | +| 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | Note | | | +| 0 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | Note | | | +| 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | Time Difference | 10.5.2.41 | | +| 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | Starting Time | 10.5.2.38 | | +| 0 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | Timing Advance | 10.5.2.40 | | +| 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | TMSI | 10.5.2.42 | | +| 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Note | | | + +NOTE: These values were allocated but never used in earlier phases of the protocol. + +--- + +## Annex L (normative): Additional Requirements for backward compatibility with PCS 1900 for NA revision 0 ME + +See 3GPP TS 24.008. + +--- + +## Annex M (informative): Application of the "previously listed field" rule by mobile stations supporting network sharing + +This annex is informative. It intends to provide examples of the way the mobile station shall derive the information applicable to a given selected PLMN using the "previously listed field" rule (see sub-clause 3.8.3). + +--- + +### M.1 Example for the Additional\_ACC field + +| Selected PLMN | ACC broadcast by the network | ACC to be considered by the MS | +|-------------------|------------------------------|--------------------------------| +| Common PLMN | ACC (SI3) | ACC | +| Additional PLMN 1 | None | ACC | +| Additional PLMN 2 | None | ACC | +| Additional PLMN 3 | Additional_ACC (SI22) | Additional_ACC | +| Additional PLMN 4 | None | Additional_ACC | + +--- + +### M.2 Example for the PS\_ACC field + +In the following examples, the mobile station shall derive the information applicable to a given selected PLMN depending on whether domain-specific access control is indicated by the network as being in use or not. + +#### M.2.1 With Common\_PLMN\_PS\_ACC field broadcast + +| Selected PLMN | PS ACC broadcast by the network | PS ACC to be considered by the MS | +|-------------------|--------------------------------------------------------------------------|-----------------------------------| +| Common PLMN | Common_PLMN_PS_ACC | Common_PLMN_PS_ACC | +| Additional PLMN 1 | None (previously listed Common PLMN PS ACC bitmap applies for this PLMN) | Common_PLMN_PS_ACC | +| Additional PLMN 2 | PS_ACC_1 | PS_ACC_1 | +| Additional PLMN 3 | None (domain-specific access control not in use for this PLMN) | None | +| Additional PLMN 4 | PS_ACC_2 | PS_ACC_2 | + +## M.2.2 With Common\_PLMN\_PS\_ACC field not broadcast + +| Selected PLMN | PS ACC broadcast by the network | PS ACC to be considered by the MS | +|-------------------|----------------------------------------------------------------|-----------------------------------| +| Common PLMN | None | None | +| Additional PLMN 1 | PS_ACC_1 | PS_ACC_1 | +| Additional PLMN 2 | None (previously listed PS ACC bitmap applies for this PLMN) | PS_ACC_1 | +| Additional PLMN 3 | None (domain-specific access control not in use for this PLMN) | None | +| Additional PLMN 4 | None (previously listed PS ACC bitmap applies for this PLMN) | PS_ACC_1 | + +## Annex N (informative): Change History + +| Date | TSG# | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|--------|-----------|------|-----|-----|-------------------------------------------------------------------------------|--------| +| 2015-12 | | | | | | Generation of Rel-13 version based on version 12.6.0 | 13.0.0 | +| | GP-68 | GP-151200 | 1023 | 7 | B | Introduction of Power Efficient Operation | 13.0.0 | +| | GP-69 | GP-160201 | 1031 | | F | Corrections to overlaid CDMA | 13.1.0 | +| | GP-69 | GP-160167 | 1025 | 4 | B | Introduction of EC-EGPRS | 13.1.0 | +| | GP-69 | GP-160163 | 1029 | 3 | F | Miscellaneous corrections to eDRX | 13.1.0 | +| | GP-69 | GP-160161 | 1026 | 4 | B | Introduction of System Information for EC-EGPRS | 13.1.0 | +| 2016-06 | GP-70 | GP-160438 | 1040 | 4 | C | Energy Efficient EC-CCCH/D Operation | 13.2.0 | +| 2016-06 | GP-70 | GP-160418 | 1039 | 1 | B | Introduction of Radio frequency Colour Code for PEO | 13.2.0 | +| 2016-06 | GP-70 | GP-160412 | 1034 | 2 | F | Miscellaneous corrections to eDRX_GSM | 13.2.0 | +| 2016-06 | GP-70 | GP-160411 | 1037 | 1 | B | Introduction of Radio Frequency Colour Code | 13.2.0 | +| 2016-06 | GP-70 | GP-160373 | 1036 | 2 | F | Miscellaneous corrections to EC System Information messages | 13.2.0 | +| 2016-06 | GP-70 | GP-160362 | 1038 | | B | EC-GSM-IoT SINR based measurements | 13.2.0 | +| 2016-09 | RP-73 | RP-161392 | 1042 | 2 | F | Miscellaneous EC-GSM-IoT Changes | 13.3.0 | +| 2016-09 | RP-73 | RP-161393 | 1043 | 2 | F | Clarification of CCCH_GROUP Determination | 13.3.0 | +| 2016-09 | RP-73 | RP-161393 | 1044 | 2 | F | Clarification of PEO Code Point Usage | 13.3.0 | +| 2016-09 | RP-73 | RP-161392 | 1045 | 3 | F | Miscellaneous corrections to EC-GSM-IoT | 13.3.0 | +| 2016-09 | | | | | | Editorial clean-up | 13.3.1 | +| 2016-09 | | | | | | Editorial clean-up | 13.3.2 | +| 2016-12 | RP-74 | RP-162069 | 1049 | 1 | F | Miscellaneous corrections | 13.4.0 | +| 2016-12 | RP-74 | RP-162070 | 1050 | 1 | F | Indication of used PDCH Mapping for Higher Coverage Classes on EC SI | 13.4.0 | +| 2016-12 | RP-74 | RP-162067 | 1048 | 1 | F | Correction on SI13 reading | 14.0.0 | +| 2017-03 | RP-75 | RP-170063 | 1052 | 1 | A | Miscellaneous PEO Corrections | 14.1.0 | +| 2017-03 | RP-75 | RP-170064 | 1054 | 3 | A | Clarifying EC_Access_Control_Class Operation for EC-GSM | 14.1.0 | +| 2017-03 | RP-75 | RP-170061 | 1056 | 2 | B | Introduction of Alternative Mappings for Higher Coverage Classes with 2 PDCHs | 14.1.0 | +| 2017-03 | RP-75 | RP-170064 | 1058 | 1 | A | Handling of unknown message types on EC-CCCH/D | 14.1.0 | +| 2017-06 | RP-76 | RP-170923 | 1047 | 7 | B | Introduction of Multilateration | 14.2.0 | +| 2017-06 | RP-76 | RP-170924 | 1061 | 7 | B | Introduction of new UL coverage class CC5 for UL MCL improvement | 14.2.0 | +| 2017-06 | RP-76 | RP-170928 | 1064 | 1 | A | Protection Against Malicious Changes to System Information | 14.2.0 | +| 2017-06 | RP-76 | RP-170925 | 1065 | 1 | F | Introduction of enhanced DECOR for GERAN | 14.2.0 | +| 2017-09 | RP-77 | RP-171598 | 1070 | 2 | A | Miscellaneous corrections for PEO_BCCH_CHANGE_MARK | 14.3.0 | +| 2017-09 | RP-77 | RP-171595 | 1071 | 2 | F | Training Sequence Selection for CC5 EC-RACH using EDAB | 14.3.0 | +| 2017-09 | RP-77 | RP-171596 | 1068 | 2 | C | Faster Detection of EAB Barring Conditions | 15.0.0 | +| 2017-12 | RP-78 | RP-172189 | 1076 | 1 | A | Corrections to multilateration positioning support for CC5 | 15.1.0 | +| 2017-12 | RP-78 | RP-172190 | 1080 | - | A | Extended-EARFCN related corrections | 15.1.0 | +| 2018-06 | RP-80 | RP-180821 | 1082 | 1 | B | Energy efficiency enhancements for EC-GSM-IoT MS in idle mode | 15.2.0 | +| 2018-06 | RP-80 | RP-180825 | 1083 | - | A | Introduction of Restricted Use of Enhanced Coverage | 15.2.0 | +| 2018-09 | RP-81 | RP-181593 | 1084 | 1 | B | Introduction of EC PAGING INDICATION message | 15.3.0 | +| 2018-09 | RP-81 | RP-181593 | 1085 | - | B | Deferred System Information Acquisition for PEO | 15.3.0 | +| 2018-12 | RP-82 | RP-182392 | 1086 | 1 | F | Corrections to Deferred System Information Acquisition in PEO | 15.4.0 | +| 2018-12 | RP-82 | RP-182392 | 1087 | 1 | F | Corrections to Deferred System Information Acquisition in EC operation | 15.4.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/44_series/44021/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Rel-16/44_series/44021/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ae10cf84f905f1aed9034a6c144a9e3c726f35f --- /dev/null +++ b/marked/Rel-16/44_series/44021/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec93ad8d29b642b713261a9762324618059dc25a845e42d1fdfb4c7a98030005 +size 36939 diff --git a/marked/Rel-16/44_series/44021/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/44_series/44021/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b87ef8869544a9b834e4636b7f6f1c6bcc07b6e --- /dev/null +++ b/marked/Rel-16/44_series/44021/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:994944d1c856d18cd05255f3da3a5fc7f7d22c86117ecc050266072ffa8dd0b4 +size 57931 diff --git a/marked/Rel-16/44_series/44021/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Rel-16/44_series/44021/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bce7058e9228e935a66aa7d5bc922f3a23dc65b --- /dev/null +++ b/marked/Rel-16/44_series/44021/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2a95b7025cb143534385b726443bd5265eaea11461f19e12f5826dc9e87e05d +size 58986 diff --git a/marked/Rel-16/44_series/44021/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-16/44_series/44021/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..659dec36f5fce43089d69849f57f39ab5e13aab2 --- /dev/null +++ b/marked/Rel-16/44_series/44021/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35f40c17d42861764593a88e5f66af5504eac888259d86517247b0bc5e0bc5ad +size 69857 diff --git a/marked/Rel-16/44_series/44021/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/Rel-16/44_series/44021/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15ab3f3fad39d31c18f71eb208b214ff89c46ba7 --- /dev/null +++ b/marked/Rel-16/44_series/44021/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed39c72325bf903e0b5d0f057b96e24dfa812e5982b4b43218dce9e50590208c +size 30283 diff --git a/marked/Rel-16/44_series/44021/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Rel-16/44_series/44021/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a033fca6fad7efc294d75c6478181fbaf9c405f --- /dev/null +++ b/marked/Rel-16/44_series/44021/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba626c68ffa8649b43ded1def4b2b609036ea32e0c11723ccc29def175cf1685 +size 29234 diff --git a/marked/Rel-16/44_series/44021/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Rel-16/44_series/44021/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddabe52ebd77cdbf743416f886f8c76756793b6e --- /dev/null +++ b/marked/Rel-16/44_series/44021/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd9ee4c61ea42f8da737f7706c4901b6227e3b5eecb9a5f5b9949caa8be8e0b0 +size 38499 diff --git a/marked/Rel-16/44_series/44021/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/44_series/44021/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0aca23131874d7907f64948b2d820672d434e9c2 --- /dev/null +++ b/marked/Rel-16/44_series/44021/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7778dbb5d38ccf7c02a125bbe4281a9e8880103b08943750dd1b8a5e81327954 +size 41363 diff --git a/marked/Rel-16/44_series/44021/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/marked/Rel-16/44_series/44021/b58cedaf15ad4f0edee5621820865ccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e005a6f7ac10a14d0149388d8304acee3d9ed037 --- /dev/null +++ b/marked/Rel-16/44_series/44021/b58cedaf15ad4f0edee5621820865ccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0435959ccf2d8b50d9a643f287d4cd53ea0adf6e036e762ad834fa2a5601b755 +size 35130 diff --git a/marked/Rel-16/44_series/44021/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/44_series/44021/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17e23c022cae80289c6b431c011a6826c6aa07c6 --- /dev/null +++ b/marked/Rel-16/44_series/44021/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6cb572d9c023c6a1e011907ca9abaa6e2a40e9910f1fc76bd55593ad0b37ca2 +size 38518 diff --git a/marked/Rel-16/44_series/44021/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/Rel-16/44_series/44021/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cfc3b174d185675fa4a3b2cba703cc1ad121c1f --- /dev/null +++ b/marked/Rel-16/44_series/44021/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af94a01f58814be8f2f0646833969d011497c4c051095096772db1a5c6b89eda +size 65445 diff --git a/marked/Rel-16/44_series/44021/raw.md b/marked/Rel-16/44_series/44021/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0af4cbae829fb31ab4b37789a19be2604ce0be1a --- /dev/null +++ b/marked/Rel-16/44_series/44021/raw.md @@ -0,0 +1,1489 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References, Definitions and Abbreviations ..... | 6 | +| 2.1 References..... | 6 | +| 2.2 Definitions..... | 7 | +| 2.2 Abbreviations..... | 7 | +| 3 General approach ..... | 7 | +| 3.1 Overview of data rates and configurations ..... | 7 | +| 4 The RA0 Function..... | 9 | +| 4.1 Asynchronous-to-Synchronous Conversion (RA0)..... | 9 | +| 4.2 Break signal ..... | 9 | +| 4.3 Overspeed/Underspeed ..... | 9 | +| 4.4 Parity Bits..... | 10 | +| 4.5 Flow Control ..... | 10 | +| 5 Void..... | 10 | +| 6 Void..... | 10 | +| 7 Void..... | 10 | +| 8 The Relay Functions RA1/RA1', RA1'/RA1", RA1'/RAA' and RA1'/RAA" ..... | 10 | +| 8.1 Single slot rates ..... | 10 | +| 8.1.1 Radio interface rate of 14,5 kbit/s ..... | 11 | +| 8.1.2 Radio Interface rate of 12 kbit/s..... | 11 | +| 8.1.3 Radio Interface rate of 6 kbit/s..... | 12 | +| 8.1.4 Radio Interface rate of 3,6 kbit/s (transparent services only) ..... | 13 | +| 8.1.5 Synchronisation..... | 13 | +| 8.1.6 Idle frames..... | 13 | +| 8.2 Multislot rates ..... | 13 | +| 8.2.1 AIURs up to 38,4 kbit/s using TCH/F9.6 and TCH/F4.8 channel codings ..... | 14 | +| 8.2.2 AIURs up to 64 kbit/s using TCH/F14.4 channel coding ..... | 14 | +| 8.2.3 AIUR of 48 kbit/s; Intermediate rate of 64 kbit/s; Radio interface rate of $5 \times 12$ kbit/s ..... | 14 | +| 8.2.4 AIUR of 56 kbit/s; Intermediate rate of 64 kbit/s, Radio interface rate of $5 \times 12$ kbit/s ..... | 15 | +| 8.2.5 AIUR of 64 kbit/s; Radio interface rate of $6 \times 12$ kbit/s..... | 15 | +| 9 The EDGE multiplexing function ..... | 15 | +| 9.1 Data block distribution into the substreams by the Multiplexing function; TCH/F28.8 channel coding..... | 16 | +| 9.1.1 AIUR of 57.6 kbit/s; Radio interface rate of $2 \times 29.0$ kbit/s..... | 16 | +| 9.2 Data block distribution to the radio interface by the Multiplexing function; TCH/F32.0 channel coding..... | 16 | +| 9.2.1 AIUR of 56 kbit/s; Radio interface rate of $2 \times 32.0$ kbit/s..... | 16 | +| 9.2.2 AIUR of 64 kbit/s; Radio interface rate of $2 \times 32.0$ kbit/s..... | 16 | +| 9.3 Data block distribution into the substreams by the Multiplexing function; TCH/F43.2 channel coding ..... | 17 | +| 10 The RA1' Function ..... | 17 | +| 10.1 Void..... | 17 | +| 10.2 TCH/F9.6 and TCH/F4.8 channel codings..... | 17 | +| 10.2.1 Network Independent Clocking ..... | 18 | +| 10.2.1.1 Multiframe Structure ..... | 18 | +| 10.2.1.2 Encoding and compensation..... | 18 | +| 10.2.2 Synchronisation..... | 19 | +| 10.2.3 Idle frames..... | 19 | +| 10.3 TCH/F14.4 channel coding ..... | 19 | +| 10.3.1 Multiframe structure over the radio-interface ..... | 20 | +| 10.3.2 Radio-interface data block for TCH/F14.4 channel coding ..... | 21 | +| 10.3.3 Network independent clocking..... | 21 | +| 10.3.3.1 Negative compensation ..... | 21 | +| 10.3.3.2 Positive compensation ..... | 21 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------| +| 11 | The Split/Combine and Padding-functions ..... | 22 | +| 11.1 | Data frame distribution into the substreams/channels by the Split/Combine function ..... | 22 | +| 11.1.1 | Data frame distribution into the substreams/channels by the Split/Combine function (TCH/F9.6 and TCH/F4.8 channel codings)..... | 22 | +| 11.1.2 | Data block distribution into the substreams by the Split/Combine function (TCH/F14.4 channel coding) .... | 22 | +| 11.2 | Substream numbering in transparent operation..... | 23 | +| 11.2.1 | Substream numbering for TCH/F4.8 and TCH/F9.6 channel codings..... | 23 | +| 11.2.2 | Substream numbering for TCH/F14.4 and TCH/F28.8 channel codings..... | 24 | +| 11.3 | Substream Synchronisation ..... | 24 | +| 11.4 | Void..... | 24 | +| 11.5 | Padding Functions ..... | 24 | +| 11.5.1 | Padding for TCH/F9.6 and TCH/F4.8..... | 24 | +| 11.5.1.1 | Padding for AIUR 14,4 kbit/s:..... | 24 | +| 11.5.1.2 | Padding for AIUR 64 kbit/s:..... | 24 | +| 11.5.2 | Padding for TCH/F14.4 channel coding ..... | 24 | +| 11.5.2.1 | Padding for AIURs up to 38,4 kbit/s ..... | 24 | +| 11.5.2.2 | Padding for AIURs of 48 kbit/s..... | 25 | +| 11.5.2.3 | Padding for AIURs of 56 kbit/s..... | 25 | +| 11.5.2.4 | Padding for AIURs of 64 kbit/s..... | 25 | +| 11.6 | Handling of the E1-E3 bits in multislot operation ..... | 25 | +| 12 | Support of Non-Transparent Bearer Services ..... | 25 | +| 12.1 | Support of non-transparent operation for TCH/F9.6 and TCH/F4.8 channel codings..... | 25 | +| 12.2 | Support of non-transparent operation for TCH/F14.4 channel coding ..... | 26 | +| 12.3 | Support of non-transparent operation for TCH/F28.8 channel coding ..... | 26 | +| 12.4 | Support of non-transparent operation for TCH/F43.2 channel coding ..... | 26 | +| 13 | Figures on Frame structures..... | 27 | +| Annex A (Informative): | Stacks of rate adaptation ..... | 32 | +| A.1 | Stacks of rate adaptation for 9,6/4,8 kbit/s single slot operation ..... | 32 | +| A.2 | Stacks of rate adaptation for 14,4 kbit/s single slot operation ..... | 34 | +| A.3 | Stacks of rate adaptation for 9,6/4,8 kbit/s multi slot operation ..... | 36 | +| A.4 | Stacks of rate adaptation for 14,4 kbit/s multi slot operation ..... | 38 | +| A.5 | Stacks of rate adaptation for EDGE channels TCH28.8 and TCH/F43.2 (NT only)..... | 40 | +| Annex B (Informative): | An example of mapping Network Independent Clocking information for TCH/F14.4 when the S-interface is deployed ..... | 42 | +| Annex C (Informative): | Change history..... | 43 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it is re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the rate adaptation functions to be used in PLMN Mobile Stations (MS)s for adapting terminal interface data rates to the Mobile Station - Base Station System (MS-BSS) interface data rates in accordance with 3GPP TS 43.010 [3]. + +The provision of these functions will depend on the services a particular station is designed to support. + +NOTE 1: The present document should be considered together with 3GPP TS 48.020 [9] (Rate Adaptation on the BSS-MSC Interface) to give a complete description of PLMN rate adaptation. + +NOTE 2: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. + +# --- 2 References, Definitions and Abbreviations + +## 2.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] 3GPP TR 21.905: "Vocabulary for 3GPP specifications". +- [2] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD) -Stage 1". +- [3] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types". +- [4] 3GPP TS 23.034: "High Speed Circuit Switched Data (HSCSD) - Stage 2 Service Description". +- [5] 3GPP TS 45.003: "Channel coding". +- [6] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [7] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities". +- [8] Void. +- [9] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [10] ITU-T Recommendation V.110: "Support of data terminal equipments (DTEs) with V-Series interfaces by an integrated services digital network". +- [11] ITU-T Recommendation X.30: "Support of X.21,X.21 bis and X.20 bis based terminal equipments (DTEs) by integrated services digital network (ISDN)". +- [12] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels". + +## 2.2 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Overall data stream:** The data stream in those parts of the network where the data flow is not split into multiple channels. + +**Substream:** Stream of data with explicit or implicit numbering between splitter and combiner functions. + +**Channel:** A physical full rate channel on the radio interface (TCH/F) independent of the contents + +**Multislot intermediate rate:** Intermediate rate per substream in those parts of the network where the overall data stream is split into substreams. + +**Intermediate rate:** Intermediate rate in the overall data stream. + +**Substream rate:** The user rate including padding, if applicable, on one individual substream + +**EDGE channel:** A general term referring to channels based on 8PSK modulation; i.e. TCH/F28.8, TCH/F32.0, and TCH/F43.2. + +## 2.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 21.905 [1]. + +# --- 3 General approach + +3GPP TS 43.010 defines the PLMN connection types necessary to support the GSM PLMN data and telematic services. + +Within the MS there are several different data rate adaptation functions - and a Split/Combine-function in case of a multislot data configuration - which are combined as shown in 3GPP TS 43.010 as part of the connection type. + +The rate adaptation functions are RA0, RA1', RA1'/RA1", RA1'/RAA", RA1'/RAA' and RA1/RA1'. The RA0 is similar to the RA0 function described in ITU-T recommendation V.110 [11] with the exception of the conversion of the rates 14.4 and 28,8 kbit/s. + +The RA1' function is similar to RA1 described in ITU-T recommendation V.110 [11] but has a reduced bit rate output compatible with the coding scheme proposed for data services on the radio interface. + +The RA1/RA1', RA1'/RA1", RA1'/RAA" and RA1'/RAA' are relay functions, used as indicated in 3GPP TS 43.010. + +In multislot data-configurations the overall data stream is split into parallel substreams between the Split/Combine-functions. + +## 3.1 Overview of data rates and configurations + +In Table 1, an overview of the supported transparent air-interface user rates is given. For each rate, also intermediate rates per channel between BTS and MSC, overall radio interface rates, and channel configurations are given. For single slot connections the intermediate rates are per channel carrying the overall data stream, whereas for multislot connections, the intermediate rates are per substream. + +For single slot rates up to 4,8 kbit/s, the used intermediate rate is 8 kbit/s, and for the 9,6 kbit/s single slot rate 16 kbit/s. + +For TCH/F9.6 and TCH/F4.8 channel codings, the multislot intermediate rates are 16 and 8 kbit/s per TCH/F, respectively. + +For TCH/F14.4 channel coding, the multislot intermediate rate is 16 kbit/s per TCH/F. + +Connections utilising TCH/F28.8 or TCH/F43.2 across the radio interface, use multislot combinations of TCH/F14.4 between BTS and MSC. Thus the corresponding multislot intermediate rate is 16 kbit/s. + +No multislot intermediate rates are applicable to 56 and 64 kbit/s connections using TCH/F32.0 radio interface channels. The intermediate rate for the 32 kbit/s user rate using the TCH/F32.0 channel is 32 kbit/s. + +**Table 1: AIUR/Multislot intermediate rates** + +| Air interface user rate | DTE/DCE statuses | RA0 | RA1'/RA1
RA1'/RAA'
RA1'/RA1"
RA1'/RAA"
(Note 4) | | RA1' | | +|-------------------------|------------------|-----|-------------------------------------------------------------|---------------|---------------------------|------------| +| | | | Multislot intermediate rate | Frame type | Radio interface rate | Padding | +| ≤ 600 bit/s | X | X | 8 kbit/s | 80 bit frames | 3,6 kbit/s | | +| 1200 bit/s | X | X | 8 kbit/s | 80 bit frames | 3,6 kbit/s | | +| 2,4 kbit/s | X | X | 8 kbit/s | 80 bit frames | 3,6 kbit/s | | +| 4,8 kbit/s | X | X | 8 kbit/s | 80 bit frames | 6 kbit/s | | +| 9,6 kbit/s | X | X | 16 kbit/s or 2×8 kbit/s | 80 bit frames | 12 kbit/s or 2×6 kbit/s | | +| 14,4 kbit/s | X | X | 2×16 kbit/s or 3×8 kbit/s | 80 bit frames | 2×12 kbit/s or 3×6 kbit/s | P (note 1) | +| | | | 16 kbit/s | Note 5 | 14,5 kbit/s | | +| 19,2 kbit/s | X | X | 2×16 kbit/s or 4×8 kbit/s | 80 bit frames | 2×12 kbit/s or 4×6 kbit/s | | +| 28,8 kbit/s | X | X | 3×16 kbit/s | 80 bit frames | 3×12 kbit/s | | +| | | | 2 × 16 kbit/s | Note 5 | 2×14,5 kbit/s | | +| | | | | | 1×29 kbit/s | | +| 32 kbit/s | | | 1 × 32 kbit/s | | 1 × 32 kbit/s | | +| 38,4 kbit/s | X | X | 4×16 kbit/s | 80 bit frames | 4×12 kbit/s | | +| | | | 3 × 16 kbit/s | Note 5 | 3×14,5 kbit/s | P (note 1) | +| 43,2 kbit/s
Note 6 | X | | 3 × 16 kbit/s | Note 5 | 1×43,5 kbit/s | | +| 48 kbit/s | X | | Note 2 | Note 2 | 5×12 kbit/s | | +| | | | 4 × 16 kbit/s | Note 5 | 4×14,5 kbit/s | P (note 1) | +| 56 kbit/s | | | Note 2 | Note 2 | 5×12 kbit/s (note 3) | | +| | | | 4×16 kbit/s | Note 5 | 4×14,5 kbit/s | P (note 1) | +| | | | Note 2 | Note 2 | 2×32,0 kbit/s | | +| 64 kbit/s | | | Note 2 | Note 2 | 6×12 kbit/s (note 3) | P (note 1) | +| | | | | | 5×14,5 kbit/s | (note 1) | +| | | | Note 2 | Note 2 | 2×32,0 kbit/s | | + +P=Padding used + +NOTE 1: For information on the padding procedure, please refer to clause 11 of the present document. + +NOTE 2: No multislot intermediate rate; substreams combined at the BSS with a resulting data rate of 64 kbit/s between BSS and MSC. + +NOTE 3: AIUR 11,2 kbit/s per channel + +NOTE 4: Different relay rate adaptation functions exist at the network side: + +- RA1'/RA1 applies if the radio interface rate is n × 3,6, 6 or 12 kbit/s and the AIUR is less than 48 kbit/s, +- RA1'/RAA' applies if the radio interface rate is n × 14,5, 29 or 43,2 kbit/s and the AIUR is less than 64 kbit/s, +- RA1'/RA1" applies if the radio interface rate is n × 12 kbit/s and the AIUR is equal to 48, 56 or 64 kbit/s, +- RA1'/RAA" applies if the radio interface rate is n × 14,5 kbit/s and the AIUR is equal to 64 kbit/s, +- a relay rate adaptation function does not apply if the radio interface rate is n × 32 kbit/s + +NOTE 5: A 320-bit frame format described in 3GPP TS 48.060. + +NOTE 6: Used only in non-transparent configurations. + +# 4 The RA0 Function + +## 4.1 Asynchronous-to-Synchronous Conversion (RA0) + +The RA0 Function is only used with asynchronous interfaces. Incoming asynchronous data is padded by the addition of stop elements to fit the same or nearest higher synchronous rate defined by 2 to the power $n$ (where $n \leq 6$ ) times 600 bit/s, 14,4 kbit/s or 28,8 kbit/s. Thus the 300 bit/s user data signalling rate shall be adapted to a synchronous 600 bit/s stream. The resultant synchronous stream is fed to RA1' or Split/Combine Function. The RA0 used in PLMN is not identical to that described in ITU-T Recommendation V.110 which converts 14,4 and 28,8 kbit/s user rates to 19,2 and 38,4 kbit/s, respectively. + +| Asynchronous user rate | Synchronous user rate | +|------------------------|-----------------------| +| $\leq 0,6$ kbit/s | 0,6 kbit/s | +| 1,2 kbit/s | 1,2 kbit/s | +| 2,4 kbit/s | 2,4 kbit/s | +| 4,8 kbit/s | 4,8 kbit/s | +| 9,6 kbit/s | 9,6 kbit/s | +| 14,4 kbit/s | 14,4 kbit/s | +| 19,2 kbit/s | 19,2 kbit/s | +| 28,8 kbit/s | 28,8 kbit/s | +| 38,4 kbit/s | 38,4 kbit/s | + +## 4.2 Break signal + +The RA0 shall detect and transmit the break signal in the following fashion: + +If the converter detects $2M$ to $2M+3$ bits, all of start polarity, where $M$ is the number of bits per character in the selected format including start and stops bits, the converter shall transmit $2M+3$ bits of start polarity. + +If the converter detects more than $2M+3$ bits all of start polarity, the converter shall transmit all these bits as start polarity. + +The $2M+3$ or more bits of start polarity received from the transmitting sides shall be output to the receiving terminal. + +The terminal shall transmit on circuit 103 at least $2M$ bits stop polarity after the start polarity break signal before sending further data character. The converter shall then regain character synchronism from the following stop to start transition. + +## 4.3 Overspeed/Underspeed + +A RA0 shall insert additional stop elements when its associated terminal is transmitting with a lower than nominal character rate. If the terminal is transmitting characters with an overspeed of up to 1 %, the asynchronous-to-synchronous converter may delete stop elements as often as is necessary to a maximum of one for every eight characters at 1 % overspeed. The converter on the receiving side shall detect the deleted stop elements and reinsert them in the received data stream (circuit 104). + +The realization of overspeed handling, as described above, at the interface to the associated terminal is implementation dependent. Possible implementations are e.g. the reduction of the length of the stop elements according to V.110 [9] or increased data rates between the TA and terminal. + +## 4.4 Parity Bits + +Possible parity bits included in the user data are considered as data bits by the RA0 function. + +## 4.5 Flow Control + +Where applicable, this function is as specified in the relevant terminal adaptation function Specification (see 3GPP TS 07 series). + +--- + +**5 Void** + +--- + +**6 Void** + +--- + +**7 Void** + +# --- **8 The Relay Functions RA1/RA1', RA1'/RA1", RA1'/RAA' and RA1'/RAA"** + +The relay functions realise conversions on the infrastructure side in both transparent and non-transparent cases as specified in 3GPP TS 43.010. + +The RA1/RA1' function shall be used for channel codings TCH/F4.8 and TCH/F9.6 if the AIUR is less than 48 kbit/s. It converts between the intermediate rate and the input rate to the channel coder. + +The RA1'/RA1" function shall be used for channel codings TCH/F4.8 and TCH/F9.6 if the AIUR is equal to 48, 56 or 64 kbit/s. It converts between the 64 kbit/s data stream and the input rate to the channel coder. + +The RA1/RA1' and RA1'/RA1" functions only apply in A/Gb mode. In GERAN Iu mode the rate adaptation function RA1' applies instead of that as specified in clause 10. + +The RA1'/RAA' function shall be used for channel codings TCH/F14.4, TCH/F28.8 and TCH/F43.2 if the AIUR is less than 64 kbit/s in A/Gb mode and if the AIUR is less than 56 kbit/s in GERAN Iu mode. It converts between the E-TRAU frame specified in 3GPP TS 48.060 and the input rate to the channel coder or the EDGE multiplexing function. + +The RA1'/RAA" function shall be used for channel codings TCH/F14.4 if the AIUR is equal to 64 kbit/s in A/Gb mode and if the AIUR is equal to 56 or 64 kbit/s in GERAN Iu mode. It converts between the 64 kbit/s data stream and the input rate to the channel coder. + +A relay adaptation function is not needed for the channel coding TCH/F32. + +## 8.1 Single slot rates + +There are seven data rates (known as Radio Interface data rates) used for data transfer to the channel coder. These are 43,5 kbit/s (NT only), 32 kbit/s (T only), 29 kbit/s, 14,5 kbit/s, 12 kbit/s, 6 kbit/s and 3.6 kbit/s. In cases where EDGE channel codings TCH/F43.2 or TCH/F28.8 are used, the RA1'/RAA' function adapts the data stream to 14,5 kbit/s substreams as if multiple 14,5 kbit/s radio interface channels were used. + +The 32 kbit/s user rate is identical to the 32 kbit/s intermediate rate. In this case the 32 kbit/s intermediate rate is directly mapped to the 32 kbit/s radio interface data rate. + +The 8, 16 and 64 kbit/s intermediate rates and the 32 kbit/s intermediate rate with other than 32 kbit/s user rates are adapted to the radio interface data rates as follows: + +| AIUR | Intermediate rate | Radio interface rate | +|-------------|--------------------------|-----------------------------| +| ≤ 600 bit/s | 8 kbit/s | 3,6 kbit/s | +| 1,2 kbit/s | 8 kbit/s | 3,6 kbit/s | +| 2,4 kbit/s | 8 kbit/s | 3,6 kbit/s | +| 4,8 kbit/s | 8 kbit/s | 6 kbit/s | +| 9,6 kbit/s | 16 kbit/s | 12 kbit/s | +| 14,4 kbit/s | 32 kbit/s | 14,5 kbit/s | +| 28,8 kbit/s | 64 kbit/s | 29 kbit/s (Note 2) | +| 43,2 kbit/s | (Note 1) | 43,5 kbit/s (Note 2) | + +Note 1: AIUR only used in non-transparent configurations. There is no direct relationship between AIUR and Intermediate rate. + +Note 2: The RA1'/RAA' function adapts the data stream to 14,5 kbit/s substreams as if multiple 14,5 kbit/s radio interface channels were used. + +### 8.1.1 Radio interface rate of 14,5 kbit/s + +The RA1'/RAA' function converts between the E-TRAU frame and the 290 bit blocks from the channel coder. The E-TRAU frames are defined in TS 48.060. The 290 bit blocks carry 288 data bits and the control bits M1 and M2 as specified in section 10.3.1 and 10.3.2. + +### 8.1.2 Radio Interface rate of 12 kbit/s + +In this case one modified ITU-T V.110 60 bit frame is received/sent from/to the radio interface every 5ms (see 3GPP TS 45.003 ). The RA1/RA1' function adds/subtracts the 17 bit synchronization pattern and the E1,E2 and E3 bits to/from each ITU-T V.110 80 bit frame as follows: + +The modified ITU-T V.110 60 bits frame received/sent from/to the radio interface at 12 Kbit/s (Figure 5), + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| D7 | D8 | D9 | D10 | D11 | D12 | X | +| D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| E4 | E5 | E6 | E7 | D25 | D26 | D27 | +| D28 | D29 | D30 | S6 | D31 | D32 | D33 | +| D34 | D35 | D36 | X | D37 | D38 | D39 | +| D40 | D41 | D42 | S8 | D43 | D44 | D45 | +| D46 | D47 | D48 | S9 | | | | + +is converted into the following a ITU-T V.110 80 bits frame at 16 Kbit/s (Figure 3): + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 1 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| 1 | E1 | E2 | E3 | E4 | E5 | E6 | E7 | +| 1 | D25 | D26 | D27 | D28 | D29 | D30 | S6 | +| 1 | D31 | D32 | D33 | D34 | D35 | D36 | X | +| 1 | D37 | D38 | D39 | D40 | D41 | D42 | S8 | +| 1 | D43 | D44 | D45 | D46 | D47 | D48 | S9 | + +In the case of the non transparent services, bits S1, X, S3, S4, E4, E5, E6, E7, S6, X (second occurrence), S8, and S9 carry bits D'1, D'2, D'3, D'4, D'5, D'6, D'7, D'8, D'9, D'10, D'11, and D'12, respectively. + +For a modified ITU-T V.110 60 bit frames received from the radio interface, the received D, S and X bits or D and D' bits are set to the same value as the transmitted bits. Bits E1, E2, E3 are set according to the user data rate as shown in figure 4 for the transparent services, or the RLP multiframe and DTX indication as per 3GPP TS 48.020 in the non transparent case. + +For modified ITU-T V.110 60 bit frames transmitted over the radio interface, the received D, S, and X bits or D and D' are set to the same value as the transmitted bits. Bits E1, E2, E3 are discarded. + +### 8.1.3 Radio Interface rate of 6 kbit/s + +In this case one modified ITU-T V.110 60 bit frame is received/sent from/to the radio interface every 10 ms (see 3GPP TS 45.003). The RA1/RA1' function adds/subtracts the 17 bit synchronization pattern and the E1, E2 and E3 bits to/from each ITU-T V.110 80 bit frame as follows: + +The modified ITU-T V.110 60 bits frame received/sent from/to the radio interface at 6 Kbit/s (Figure 6), + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| D7 | D8 | D9 | D10 | D11 | D12 | X | +| D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| E4 | E5 | E6 | E7 | D25 | D26 | D27 | +| D28 | D29 | D30 | S6 | D31 | D32 | D33 | +| D34 | D35 | D36 | X | D37 | D38 | D39 | +| D40 | D41 | D42 | S8 | D43 | D44 | D45 | +| D46 | D47 | D48 | S9 | | | | + +is converted into the following a ITU-T V.110 80 bits frame at 8 Kbit/s (Figure 3): + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 1 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| 1 | E1 | E2 | E3 | E4 | E5 | E6 | E7 | +| 1 | D25 | D26 | D27 | D28 | D29 | D30 | S6 | +| 1 | D31 | D32 | D33 | D34 | D35 | D36 | X | +| 1 | D37 | D38 | D39 | D40 | D41 | D42 | S8 | +| 1 | D43 | D44 | D45 | D46 | D47 | D48 | S9 | + +In the case of the non transparent services, bits S1, X, S3, S4, E4, E5, E6, E7, S6, X (second occurrence), S8, and S9 carry bits D'1, D'2, D'3, D'4, D'5, D'6, D'7, D'8, D'9, D'10, D'11, and D'12, respectively. + +For a modified ITU-T V.110 60 bit frames received from the radio interface, the received D, S and X bits or D and D' bits are set to the same value as the transmitted bits. Bits E1, E2, E3 are set according to the user data rate as shown in figure 4 for the transparent services, or the RLP multiframe and DTX indication as per 3GPP TS 48.020 in the non transparent case. + +For modified ITU-T V.110 60 bit frames transmitted over the radio interface, the received D, S, and X bits or D and D' bits are set to the same value as the transmitted bits. Bits E1, E2, E3 are discarded. + +This process is identical to that used for the 12 kbit/s case except that the frame repetition rates are halved. + +### 8.1.4 Radio Interface rate of 3,6 kbit/s (transparent services only) + +In this case one modified ITU-T V.110 36 bit frame is received/sent from/to the radio interface every 10ms (see 3GPP TS 45.003 [5]). The RA1/RA1' function adds/subtracts the 17 bit synchronization pattern and the E1,E2 and E3 bits to/from each ITU-T V.110 80 bit frame as follows: + +For the AIUR of 2,4 kbit/s the modified ITU-T V.110 36 bits frame received/sent from/to the radio interface at 3.6 kbit/s (Figure 7a), + +| | | | | | | | | +|-----|-----|-----|----|-----|-----|-----|----| +| D1 | D2 | D3 | S1 | D4 | D5 | D6 | X | +| D7 | D8 | D9 | S3 | D10 | D11 | D12 | S4 | +| E4 | E5 | E6 | E7 | D13 | D14 | D15 | S6 | +| D16 | D17 | D18 | X | D19 | D20 | D21 | S8 | +| D22 | D23 | D24 | S9 | | | | | + +is converted into the following a ITU-T V.110 80 bits frame at 8 Kbit/s (Figure 7b): + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D1 | D2 | D2 | D3 | D3 | S1 | +| 1 | D4 | D4 | D5 | D5 | D6 | D6 | X | +| 1 | D7 | D7 | D8 | D8 | D9 | D9 | S3 | +| 1 | D10 | D10 | D11 | D11 | D12 | D12 | S4 | +| 1 | E1 | E2 | E3 | E4 | E5 | E6 | E7 | +| 1 | D13 | D13 | D14 | D14 | D15 | D15 | S6 | +| 1 | D16 | D16 | D17 | D17 | D18 | D18 | X | +| 1 | D19 | D19 | D20 | D20 | D21 | D21 | S8 | +| 1 | D22 | D22 | D23 | D23 | D24 | D24 | S9 | + +Figure 8 and 9 show the bit mappings for the AIUR of 1200 and 600 bit/s. + +For modified ITU-T V.110 36 bit frames transmitted to the radio interface, E1, E2, E3 are discarded. For modified ITU-T V.110 36 bit frames received from the radio interface, E1, E2, E3 are set as shown in figure 4. + +NOTE: The action to be taken in the case where two bits which should have the same value (e.g. bits noted D1) are received with different values is for further study. + +### 8.1.5 Synchronisation + +In GERAN Iu mode, the BSS shall perform the synchronisation towards the MS according to the procedures defined for the A/Gb mode in 3GPP TS 29.007 with the modification that the the indication of "physical connection established" is given on sending the message RAB ASSIGNMENT COMPLETE. + +### 8.1.6 Idle frames + +Whenever no data is received from the radio interface (e.g. frame stealing applies, layer 2 fill frames are received, etc.) idle frames shall be created. These are V.110 frames with frame alignment pattern according to ITU-T V.110 [11] and all data, status and E-bits set to binary "1". + +## 8.2 Multislot rates + +In multislot operation the transmission is performed using parallel substreams between the Split/Combine-functions. + +### 8.2.1 AIURs up to 38,4 kbit/s using TCH/F9.6 and TCH/F4.8 channel codings + +| AIUR | Intermediate rate | Radio interface rate | +|-------------|-------------------|----------------------| +| 9,6 kbit/s | 16 kbit/s | 2×6 kbit/s | +| 14,4 kbit/s | 32 kbit/s | 2×12 or 3×6 kbit/s | +| 19,2 kbit/s | 32 kbit/s | 2×12 or 4×6 kbit/s | +| 28,8 kbit/s | 64 kbit/s | 3×12 kbit/s | +| 38,4 kbit/s | 64 kbit/s | 4×12 kbit/s | + +In these cases, the data stream is mapped from 80-bit intermediate rate frames into modified frames of 60 bits for radio-interface transmission as specified in subclause 8.1 for 12 kbit/s and 6 kbit/s except for the following cases: + +For AIURs 14,4 and 28,8 kbit/s using channel codings TCH/F4.8 and TCH/F9.6, respectively, four consecutive V.110 80-bit frames (Figure 12) are mapped onto three consecutive modified 60-bit V.110 (Figure 5 or 6) frames at the MS. The 4×36 data bits in the 80-bit frames are mapped onto the 3×48 data bits in the 60-bit frames. However, bits E4-E7 in the 80-bit frames are mapped onto the E4-E7 bits in the 60-bit frames when their value indicate either positive or negative compensation (NIC; See subclause 5.1.1). The E4-E7 bits that indicate 'No compensation' in the 80-bit frames need not be mapped onto the 60-bit frames. The S- and X-bits in every fourth 80-bit frame are not mapped onto the 60-bit frames. When radio interface rate of 2 × 12 kbit/s is used for carrying AIUR 14,4 kbit/s, padding is used in the 60-bit frames of the higher substream number (Subclause 11.6). + +For substream numbering information, please refer to subclause 10 of the present document. + +### 8.2.2 AIURs up to 64 kbit/s using TCH/F14.4 channel coding + +| AIUR | Intermediate rate/ | Radio interface rate | +|-------------|--------------------|----------------------| +| 28,8 kbit/s | 64 kbit/s | 2×14,5 | +| 38,4 kbit/s | 64 kbit/s | 3×14,5 | +| 48 kbit/s | 64 kbit/s | 3×14,5 | +| 56 kbit/s | 64 kbit/s | 4×14,5 | +| 64 kbit/s | 64 kbit/s | 5×14,5 | + +For AIURs < 64 kbit/s in A/Gb mode and for AIURs < 56 kbit/s in GERAN Iu mode, the RA1'/RAA' function extracts the eight 36 data bit blocks in the E-TRAU frames and sends them through the substreams in data blocks containing eight 36-bit frames as described in subclause 10.3. + +For AIUR of 64 kbit/s in A/Gb mode and for AIURs of 56 and 64 kbit/s, the RA1'/RAA" function sends the data bits in the 64 kbit/s data stream through the substreams in data blocks containing eight 36-bit frames as described in subclause 10.3. In GERAN Iu mode the data are provided in 640 bits size SDUs. For 56 kbit/s, the last bit of each octet is set to "1". + +An M1/M2-bit pair is sent over the radio-interface along with each data block every 20 ms. These bits carry the multiframe, substream number, V.24 status, and NIC information as described in subclauses 10.3.1 and 10.3.2. + +### 8.2.3 AIUR of 48 kbit/s; Intermediate rate of 64 kbit/s; Radio interface rate of 5 × 12 kbit/s + +One modified ITU-T V.110 60 bit frame (Figure 5) is received/sent from/to a TCH/F every 5 ms (see 3GPP TS 45.003) resulting in an radio-interface rate of 12 kbit/s per channel. + +One 60-bit radio-interface frame is converted into two ITU-T V.110 32-bit frames at 64 kbit/s (Figure 13): + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 0 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | + +### 8.2.4 AIUR of 56 kbit/s; Intermediate rate of 64 kbit/s, Radio interface rate of 5 × 12 kbit/s + +One modified ITU-T V.110 60 bit frame (Figure 10) is received/sent from/to the network every 5 ms (see 3GPP TS 45.003) resulting in a radio-interface rate of 12 kbit/s per channel. + +A modified ITU-T V.110 60 bits radio-interface frame (Figure 10): + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | T1 | +| D7 | D8 | D9 | D10 | D11 | D12 | T2 | +| D13 | D14 | D15 | D16 | D17 | D18 | T3 | +| D19 | D20 | D21 | D22 | D23 | D24 | T4 | +| D25 | D26 | D27 | D28 | D29 | D30 | D31 | +| D32 | D33 | D34 | D35 | D36 | D37 | D38 | +| D39 | D40 | D41 | D42 | D43 | D44 | D45 | +| D46 | D47 | D48 | D49 | D50 | D51 | D52 | +| D53 | D54 | D55 | D56 | | | | + +NOTE: For information on the T-bits, please refer to subclause 11.2 of the present document. + +is converted into an ITU-T V.110 64 bits frame at 64 kbit/s (Figure 14): + +| | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|---| +| D1 | D2 | D3 | D4 | D5 | D6 | D7 | 1 | +| D8 | D9 | D10 | D11 | D12 | D13 | D14 | 1 | +| D15 | D16 | D17 | D18 | D19 | D20 | D21 | 1 | +| D22 | D23 | D24 | D25 | D26 | D27 | D28 | 1 | +| D29 | D30 | D31 | D32 | D33 | D34 | D35 | 1 | +| D36 | D37 | D38 | D39 | D40 | D41 | D42 | 1 | +| D43 | D44 | D45 | D46 | D47 | D48 | D49 | 1 | +| D50 | D51 | D52 | D53 | D54 | D55 | D56 | 1 | + +### 8.2.5 AIUR of 64 kbit/s; Radio interface rate of 6 x 12 kbit/s + +One modified ITU-T V.110 60 bit frame (Figure 10) is received/sent from/to the network every 5 ms (see 3GPP TS 45.003) resulting in a radio-interface rate of 12 kbit/s per channel. + +A modified ITU-T V.110 60 bits radio-interface frame (Figure 10): + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | T1 | +| D7 | D8 | D9 | D10 | D11 | D12 | T2 | +| D13 | D14 | D15 | D16 | D17 | D18 | T3 | +| D19 | D20 | D21 | D22 | D23 | D24 | T4 | +| D25 | D26 | D27 | D28 | D29 | D30 | D31 | +| D32 | D33 | D34 | D35 | D36 | D37 | D38 | +| D39 | D40 | D41 | D42 | D43 | D44 | D45 | +| D46 | D47 | D48 | D49 | D50 | D51 | D52 | +| D53 | D54 | D55 | D56 | | | | + +NOTE: For information on the T-bits, please refer to subclause 11.2 of the present document. + +is converted as follows: The data bits are extracted from the 60-bit frames received from the network; six frames, one of which carries padding as explained in subclause 11.5, carry 320 bits of user data per 5 ms resulting in a 64 kbit/s user rate which is sent forward as such. + +# --- 9 The EDGE multiplexing function + +In EDGE configurations the number of channels across the radio interface and that of substreams do not necessarily match. In such cases a multiplexing function described below shall be used at MS and BTS (3GPP TS 48.020). These functions distribute data between the substreams and radio channels. + +At the MS the multiplexing function multiplexes 14.5 kbit/s substreams — produced either by the combination of Split/Combine and RA1/RA1' or RA1' functions in the transparent case, or by the combination of Split/Combine and RLP functions in the non-transparent case — into the TCH/F28.8 or TCH/F43.2 EDGE radio interface channels. + +In the case of transparent 56 kbit/s or 64 kbit/s operation, the multiplexing function maps the data stream into two EDGE TCH/F32.0 radio interface channels. + +## 9.1 Data block distribution into the substreams by the Multiplexing function; TCH/F28.8 channel coding + +The multiplexing function maps/extracts two 14.5 kbit/s substreams into/from a 29.0 kbit/s radio interface channel. + +A radio interface data block for a TCH/F28.8 channel contains the bit sequence: M1, M2, 288 user data bits, M1, M2, and 288 user data bits, in other words, the block is a combination of two TCH/F14.4 radio interface data blocks. The two TCH/F14.4 blocks belong to two separate substreams. One 580-bit block is transmitted/received every 20 ms. + +### a) Transparent services + +In uplink, the multiplexing function maps one 290-bit block from each substream into every 580-bit TCH/F28.8 radio interface data block. Blocks from one stream always occupy the same half of the 580-bit radio interface data blocks. + +In downlink, the multiplexing function demultiplexes the two substreams by extracting the two 290-bit blocks from the received 580-bit radio interface blocks; the 290-bit blocks belonging to one substream are carried in the same half of the 580-bit radio interface blocks. + +### b) Non-transparent services + +The multiplexing function works in the same way as in the transparent case, i.e. the multiplexing is based on the use of 290-bit blocks, which — in this case — contain halves of 576-bit RLP frames. + +### 9.1.1 AIUR of 57.6 kbit/s; Radio interface rate of $2 \times 29.0$ kbit/s + +Non-transparent 57.6 kbit/s radio interface user rate can be achieved by using a combination of two TCH/F28.8 channels across the radio interface. Two parallel multiplexing functions are applied; the operation of both of these is as described in section 9.1 above. + +## 9.2 Data block distribution to the radio interface by the Multiplexing function; TCH/F32.0 channel coding + +The multiplexing function divides the datastream into blocks of ten 64-bit V.110 frames (Figure 14) in case of the 56 kbit/s user rate or into blocks of 640 data bits in case of the 64 kbit/s user rate. These blocks are distributed cyclically into timeslots $a$ ( $0 \leq a \leq 6$ ) and $a+n$ ( $1 \leq a+n \leq 7$ ) in each TDMA-frame; in the data stream, data mapped into timeslot $a$ precedes that mapped into slot $a+n$ . The receiving Multiplexing function recombines overall data stream from radio-interface channels so that the data carried by timeslot $a$ ( $0 \leq a \leq 6$ ) precedes the data carried by timeslot $a+n$ ( $1 \leq a+n \leq 7$ ) of the same TDMA-frame. + +### 9.2.1 AIUR of 56 kbit/s; Radio interface rate of $2 \times 32.0$ kbit/s + +Two blocks of 10 64-bit V.110 frames (Figure 14) are sent/received every 20 ms over the radio interface. + +No V.24 status or NIC-information is transferred in association with AIUR 56 kbit/s. + +No substream numbering is needed as just one substream is used across a two-timeslot radio interface channel. + +### 9.2.2 AIUR of 64 kbit/s; Radio interface rate of $2 \times 32.0$ kbit/s + +Two blocks of 640 data bits are sent/received through the radio interface every 20 ms. + +No V.24 status or NIC-information is transferred in association with AIUR 64 kbit/s. + +No substream numbering is needed as just one substream is used across a two-timeslot radio interface channel. + +## 9.3 Data block distribution into the substreams by the Multiplexing function; TCH/F43.2 channel coding + +The multiplexing function maps/extracts three 14.5 kbit/s substreams into/from a 43.5 kbit/s radio interface channel. + +A radio interface data block for a TCH/F43.2 channel is a combination of three TCH/F14.4 radio interface data blocks. The three TCH/F14.4 blocks belong to separate substreams. One 870-bit block is transmitted/received every 20 ms. + +The TCH/F43.2 channel is used only in non-transparent operation. Therefore, the 290-bit blocks handled by the multiplexing function carry halves of 576-bit RLP frames. + +In uplink, the multiplexing function maps one 290-bit block from each substream into every 870-bit TCH/F43.2 radio interface data block. Blocks from one stream always occupy the same third of the 870-bit radio interface data blocks. + +In downlink, the multiplexing function demultiplexes the three substreams by extracting the 290-bit blocks from the received 870-bit radio interface blocks; the 290-bit blocks belonging to one substream are carried in the same third of the 870-bit radio interface blocks. + +# 10 The RA1' Function + +The RA1' function described below shall be used to adapt between the synchronous user data rates, or the output of the RA0 function and the radio interface data rates of 3.6, 6, 12, or 14,5 kbit/s. In cases where EDGE channel coding TCH/F28.8 is used, the RA1' function adapts the data stream to 14.5 kbit/s substreams as if multiple 14.5 kbit/s radio interface channels were used. + +## 10.1 Void + +## 10.2 TCH/F9.6 and TCH/F4.8 channel codings + +| Synchronous user rate | Total rate at the radio interface | DTE/DCE statuses | Air-interface bit frame structure | Single slot rate at the radio interface | +|-----------------------|-----------------------------------|------------------|-----------------------------------|-----------------------------------------| +| ≤ 2,4 kbit/s | 3.6 kbit/s | X | 36 bit (Figs. 7-9) | 3.6 kbit/s | +| 4,8 kbit/s | 6 kbit/s | X | 60 bit (Fig. 6) | 6 kbit/s | +| 9,6 kbit/s | 12 kbit/s | X | 60 bit (Fig. 5) | 12 kbit/s or 6 kbit/s | +| 14,4 kbit/s | 24 kbit/s or 18 kbit/s | X | 60 bit (Figs. 5 and 15) | 12 kbit/s or 6 kbit/s (note) | +| 19,2 kbit/s | 24 kbit/s | X | 60 bit (Fig. 5) | 12 kbit/s or 6 kbit/s | +| 28,8 kbit/s | 36 kbit/s | X | 60 bit (Fig. 5) | 12 kbit/s | +| 38,4 kbit/s | 48 kbit/s | X | 60 bit (Fig. 5) | 12 kbit/s | +| 48 kbit/s | 60 kbit/s | X | 60 bit (Fig. 5) | 12 kbit/s | +| 56 kbit/s | 60 kbit/s | | 60 bit (Fig. 10) | 12 kbit/s | +| 64 kbit/s | 72 kbit/s | | 60 bit (Figs. 10 and 16) | 12 kbit/s (note) | + +NOTE: Padding is used in frames making up the data substream of the highest substream number. + +The modified ITU-T V.110 36 or 60 bit frame structures for each user rate are shown in figures 5 – 10, 15 and 16. The structure to apply is that for the partial user rate. The D bits are used to convey the user data and the S and X bits are used to convey channel control information according to 3GPP TS 27.001. + +The E bits are used to convey the following information: + +- User Data Rate - E1, E2, E3 (for single slot operation see Figure 4, and for multislot operation Figure 4 and subclause 11.6) +- Network Independent Clocking - E4, E5, E6 (see subclause 10.2.1) +- Multiframe Synchronisation - E7 (see subclause 10.2.1). + +For description of the padding procedure, please refer to clause 11 of the present document. + +### 10.2.1 Network Independent Clocking + +Synchronous data signals received by the MT from the DTE at the MS or by IWF from the modem on the PSTN may not be synchronized to the PLMN. The following method shall be used to enable transfer of those data signals and the corresponding bit timing information via the V.110 frames. Such a situation would exist where the signals received from the modem at the IWF require its own clock or where the signals received from the DTE at the MS employs its own network independent clock. In any case, the frequency tolerance of the clocks involved is 100 ppm. + +#### 10.2.1.1 Multiframe Structure + +The transmitting end of the A/Gb mode PLMN connection shall establish a multiframe structure utilizing bit E7 consisting of four frames by setting E7 in every fourth frame to binary 0. This structure is identical to the use of E7 in V.110 (and X.30) except that such a multiframe structure exists for all user data rates. This frame synchronization is achieved and maintained during the entire call so that corrections for the network independent clocking by the receiving end of the A/Gb mode PLMN connection can be easily recognized and applied based on the code words (in c1, c2, c3, c4 and c5) positioned in bits E4, E5 and E6 of two consecutive V.110 frames as illustrated in figure 1. Thus, the multiframe structure allows for one 5-bit code words to be transmitted every two V.110 frames for the purposes of network independent clocking. The two code-words may be different from each other within the multiframe shown in figure 1. + +| Frame | E4 | E5 | E6 | E7 | +|-------|----|----|----|----| +| MF 0a | c1 | c2 | 1 | 0 | +| MF 1a | c3 | c4 | c5 | 1 | +| MF 0b | c1 | c2 | 1 | 1 | +| MF 1b | c3 | c4 | c5 | 1 | + +**Figure 1: NIC Multiframe Structure** + +Once Multiframe synchronization is achieved, each code word is independently evaluated to determine the compensation needed, if any. The compensation is applied as explained in section 3.1.2 in V.110 frames MF 1a and MF 1b. + +#### 10.2.1.2 Encoding and compensation + +The V.110 transmitter uses the following 5-bit code words, as shown in figure 2, to indicate the four possible states of compensation required for network independent clocking. + +| | c1 | c2 | c3 | c4 | c5 | +|---------------------------------|----|----|----|----|----| +| No compensation | 1 | 1 | 1 | 1 | 1 | +| Negative compensation | 1 | 0 | 0 | 1 | 0 | +| Positive compensation of a zero | 0 | 1 | 0 | 0 | 1 | +| Positive compensation of one | 0 | 0 | 1 | 0 | 0 | + +**Figure 2: NIC Code Words** + +When negative compensation is indicated, one less user data bit than normal is transported in the affected frame (MF1a or MF1b). A negative compensation shall cause the receiver to delete the user data bit occupied by bit position D25, since the transmitter sets this to binary 1 and does not utilize this position for user data. At those user data rates where the user data bit is repeated, all copies of D25 shall be discarded. In case of frames with 36 data bits, bit D19 is discarded instead. + +When a positive compensation is indicated, one additional user data bit is transferred by means of the code word. At the receiver, a positive compensation causes a user data bit of binary value 0 or 1, as indicated by the code word, to be inserted between the user data bits carried in bit positions D24 and D25 (in MF1a or MF1b). In case of frames with 36 data bits, the insertion is done to between bits D18 and D19. + +When no compensation is necessary, or when NIC is applied, the values of E4, E5, E6, E7, on the 4 multi frame scheme is: + +| Frame | E4 | E5 | E6 | E7 | +|-------|----|----|----|----| +| MF 0a | 1 | 1 | 1 | 0 | +| MF 1a | 1 | 1 | 1 | 1 | +| MF 0b | 1 | 1 | 1 | 1 | +| MF 1b | 1 | 1 | 1 | 1 | + +When NIC is not applicable, the MS and the IWF shall disregard the received value of bits E4, E5, E6 and E7 in the data transmission phase. + +NOTE: NIC is not applicable in the following cases: + +- transparent asynchronous bearer services; +- the facsimile teleservices in the transparent mode; +- every transparent bearer services when interworking with an UDI Information Transfer Capability. + +### 10.2.2 Synchronisation + +Two interfaces are involved in the TAF regarding the need for data frame synchronisation, i.e. the TAF/air-interface and TAF/TE interface. For detailed definition of the synchronisation procedures refer to 3GPP TS 27.001. + +### 10.2.3 Idle frames + +Whenever no data is received from the radio interface (e.g. frame stealing applies, layer 2 fill frames are received, etc.) idle frames shall be sent to the DTE. These are V.110 frames with frame alignment pattern according to ITU-T recommendation. V.110 [11] and all data, status and E-bits set to binary "1". + +## 10.3 TCH/F14.4 channel coding + +| Synchronous user rate | Total rate at the radio interface | DTE/DCE statuses | Air-interface bit frame structure | Single slot rate at the radio interface | +|-----------------------|-----------------------------------|------------------|-----------------------------------|-----------------------------------------| +| 14,4 kbit/s | 14,5 kbit/s | X | 36 bits, 290-bit block | 14,5 kbit/s | +| 28,8 kbit/s | 29.0 kbit/s | X | 36 bits, 290-bit block | 14,5 kbit/s | +| 38,4 kbit/s | 43.5 kbit/s | X | 36 bits, 290-bit block | 14,5 kbit/s (note) | +| 48 kbit/s | 58.0 kbit/s | X | 36 bits, 290-bit block | 14,5 kbit/s (note) | +| 56 kbit/s | 58.0 kbit/s | | 36 bits, 290-bit block | 14,5 kbit/s (note) | +| 64 kbit/s | 72.5 kbit/s | | 36 bits, 290-bit block | 14,5 kbit/s (note) | + +NOTE: Padding used as specified for TCH/F14.4 channel coding in clause 11. + +The format used for transferring a synchronous data stream over the radio-interface is a multiframe consisting of 31 data blocks. The RA' function transfers the synchronous data stream into data blocks containing eight 36-bit frames as described in subclause 10.3.2. Each data block contains bits M1 and M2 followed by 288 user data bits sent/received over the radio-interface every 20 ms. The M1-bit carries a 31-bit PN-sequence used for aligning the multiframe(s), whereas the M2-bit carries substream numbering, V.24 status information, and NIC-codes as described in subclause 10.3.1. The status information carried by the M2-sequence(s) is interpreted as specified in 3GPP TS 27.001. When three consecutive M2-bits carry a substream number, this is interpreted as specified in clause 11. Five consecutive M2-bits carrying NIC-information are interpreted according to subclause 10.3.1. + +In multislot operation the transmission is performed using parallel substreams between the Split/Combine-functions. + +### 10.3.1 Multiframe structure over the radio-interface + +Bit M1 carries a 31-bit PN multiframe code 0000 1001 0110 0111 1100 0110 1110 101. One multiframe bit is transmitted every 20 ms per substream, which means that one whole multiframe consists of 248 36-bit frames. + +Bit M2 carries V.24 circuit status information, network independent clocking (NIC) information and substream numbering as indicated in the following figure: + +| bit number | 0 1 2 3 | 4 5 6 7 | 8 - 11 | 12- 15 | 16 - 19 | 20 - 23 | 24 - 27 | 28 - 30 | +|------------|----------|----------|-----------|----------|----------|-----------|---------|---------| +| M1: | 0 0 0 0 | 1 0 0 1 | 0 1 1 0 | 0 1 1 1 | 1 1 0 0 | 0 1 1 0 | 1 1 1 0 | 1 0 1 | +| M2: | # # # SB | SB X # # | # X SB SB | # # # SB | SB X # # | # X SB SB | NNNN | N SB SB | + +where # # # = Substream number (multilink operation) + +SB = the SB status bit + +X = the X-status bit + +NNNNN = Network independent clocking code + +The information carried by the M2-sequences is read per substream; i.e. the substream number and a complete NIC-code are transferred through one substream. + +A NIC-code is carried on as many substreams as is necessary to cover all NIC-compensations that have taken place. On channels where no NIC-compensation is carried, the N-bits are set to 'no compensation'. For the exact NIC-procedures, refer to subclause 10.3.3. + +In the MS to Network direction the information carried by the M2-bit sequence is mapped in the following manner: + +An M1/M2-bit pair is transmitted along each block of data containing eight modified V.110 36-bit frames. The three-bit #-sequence carries a number identifying each substream (multislot operation); the substreams are numbered 0,1,2 etc. The status- and NIC-information is mapped between the M2-sequence(s) and the V.110-frames. Bits SB and X are mapped to V.24 circuits as specified in 3GPP TS 27.001. + +The SB-bit carries the V.110 SB-status information, and the X-bit the X-status information. + +Five consecutive N-bits carrying an NIC-code in the M2-sequence indicate 'negative compensation' or 'positive compensation' if such a compensation is required. Otherwise 'no compensation' is indicated by the N-bits. + +| | N-bit 24 in M2-sequence | N-bit 25 in M2-sequence | N-bit 26 in M2-sequence | N-bit 27 in M2-sequence | N-bit 28 in M2-sequence | +|---------------------------------|-------------------------|-------------------------|-------------------------|-------------------------|-------------------------| +| No compensation | 1 | 1 | 1 | 1 | 1 | +| Negative compensation | 1 | 0 | 0 | 1 | 0 | +| Positive compensation of a zero | 0 | 1 | 0 | 0 | 1 | +| Positive compensation of a one | 0 | 0 | 1 | 0 | 0 | + +#### The Network to MS direction: + +The status-information is filtered as described in 3GPP TS 27.001. To change the SB- or X-status mode, it is required that at least two consecutive SB- or X-bits, respectively, carry the same value. + +For NIC-procedure, refer to subclause 10.3.3. + +### 10.3.2 Radio-interface data block for TCH/F14.4 channel coding + +A radio-interface data block for a TCH/F14.4 channel consists of eight 36-bit data frames and bits M1 and M2 as shown in the following figure: + +| | | | | | | | | | | | | | | | | M1 | M2 | | +|---|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 2 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 3 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 4 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 5 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 6 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 7 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 8 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | + +The number on the left indicates the order of the data frames in the 290-bit block; the 36-bit frame in position one was received before that in position two etc. One such block is transmitted over the radio interface every 20 ms. + +### 10.3.3 Network independent clocking + +The data frames carrying an NIC-multiframe (subclause 10.2.1) indicating a positive or negative compensation are distributed into the substreams according to subclause 11.1. + +In the following, 'a data bit position' means a non-padded bit position in the 290-bit radio interface blocks. + +The NIC-codes are read per substream, i.e. the sequence of five N-bits in a substream carries one complete NIC-code. + +In a 29 kbit/s radio interface channel the two halves of the 580-bit radio interface block correspond to substreams. + +If NIC-compensation(s) take(s) place in the overall user data flow : + +#### 10.3.3.1. Negative compensation + +##### a) From overall data stream to substreams + +When only one substream is used and the data is mapped to the radio interface blocks, the 'extra null bit', which is set to '1', (subclause 10.2.1) is mapped to the first data bit position of the radio interface block which carries the fifth N-bit in the 31-block multiframe structure. The five N-bits encode 'negative compensation' as described in clause 10.2.1. + +If more than one substream is used, and more than one negative compensation should be performed the 'extra null bit' is mapped to the first data bit position of the radio interface block which carries the fifth N-bit in the 31-block multiframe structure in as many substreams as necessary to perform all compensations. In those substreams where no compensation is needed the N-bits are set to 'no compensation'. + +##### b) From substreams to overall data stream + +When a radio interface block carrying the fifth bit of an NIC-code indicating negative compensation is received, the receiver discards the first data bit of the block. + +#### 10.3.3.2 Positive compensation + +##### a) From overall data stream to substreams + +An NIC-code indicating positive compensation means that the data bit from the overall data stream preceding the bit mapped into the first position of the data block conveying the second N-bit is carried encoded by the five N-bits. + +If more than one substream is used, and if more than one compensation has taken place in the overall data stream, more than one substream carries a NIC-code indicating 'positive compensation'. In those substreams where no NIC-compensation is needed the N-bits indicate 'no compensation'. + +##### b) From substreams to overall data stream + +When an NIC-code indicating positive compensation is received, an extra '0' or '1' — depending on whether a compensation of a '0' or '1' is indicated — is mapped to before the first data bit position of the block with which the second bit of the NIC-code is associated. + +# 11 The Split/Combine and Padding-functions + +The split/combine and padding functions shall be used with multislot connections as described below. The Split/Combine function splits/recombines the overall data stream to/from the substreams. The Padding function inserts filling into one of the substreams in cases where the total capacity of the substreams is larger than necessary to achieve the required AIUR. + +## 11.1 Data frame distribution into the substreams/channels by the Split/Combine function + +### 11.1.1 Data frame distribution into the substreams/channels by the Split/Combine function (TCH/F9.6 and TCH/F4.8 channel codings) + +- a) In the transparent case the Split/Combine-function distributes the V.110-frames into the substreams and recombines the overall data stream from the substreams according to the following rules: + +In the overall data stream + +- 1) the frame in position p in substream q precedes the frame in position p in substream $q+1, 0 \leq q < n-1$ +- 2) the frame in position p in substream $n-1$ precedes the frame in position $p+1$ in substream 0; + +where in the rules above n is the number of substreams. + +- b) In the non-transparent case the Split/Combine-function distributes the RLP-frames — or the four V.110-frames making up an RLP-frame (Reference: 3GPP TS 48.020, Subclause 15.1) — into channels so that one whole RLP-frame is carried through one channel. Furthermore the RLP-frames are distributed into the available channels so that the resulting delay in the overall data stream is kept as small as possible. The receiving Split/Combine-function recombines the overall data stream according to the inherent RLP-frame numbering, i.e. the N(S)-numbers in the RLP-frame header (3GPP TS 24.022). + +### 11.1.2 Data block distribution into the substreams by the Split/Combine function (TCH/F14.4 channel coding) + +- a) Transparent services + +The Split/Combine-function distributes the user data carried in the 290-bit blocks (Refer to subclause 10.3.2) into the substreams and recombines the overall data stream from the substreams according to the following rules: + +In the overall data stream: + +- 1) the data block in position m of multiframe in substream q precedes the data block in position m of multiframe in substream $q+1, 0 \leq q < n-1, 0 \leq m \leq 30$ . +- 2) the data block in position m of multiframe in substream $n-1$ precedes the data block in position $m+1$ of multiframe in substream 0; + +where in the rules above n is the number of substreams. + +![Figure 2a: Distribution of data frames or data blocks into the substreams in transparent operation. The diagram shows an 'Overall stream' at the top with frames labeled k-2, k-1, k, k+1, k+2, k+3, k+4, k+5, k+6. A bracket above the frame labeled 'k' identifies it as 'frame/ block k'. Below the overall stream, three substreams are shown, labeled 'Substr. q=0', 'Substr. q=1', and 'Substr. q=2'. Substream q=0 contains frames k-3, k, k+3, k+6. Substream q=1 contains frames k-2, k+1, k+4, k+7. Substream q=2 contains frames k-1, k+2, k+5, k+8. A vertical arrow on the left points upwards, and a horizontal arrow points to the right. A label 'position m' with a dashed line points to the frame labeled 'k' in the overall stream.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 2a: Distribution of data frames or data blocks into the substreams in transparent operation. The diagram shows an 'Overall stream' at the top with frames labeled k-2, k-1, k, k+1, k+2, k+3, k+4, k+5, k+6. A bracket above the frame labeled 'k' identifies it as 'frame/ block k'. Below the overall stream, three substreams are shown, labeled 'Substr. q=0', 'Substr. q=1', and 'Substr. q=2'. Substream q=0 contains frames k-3, k, k+3, k+6. Substream q=1 contains frames k-2, k+1, k+4, k+7. Substream q=2 contains frames k-1, k+2, k+5, k+8. A vertical arrow on the left points upwards, and a horizontal arrow points to the right. A label 'position m' with a dashed line points to the frame labeled 'k' in the overall stream. + +**Figure 2a: Distribution of data frames or data blocks into the substreams in transparent operation** + +#### b) Non-transparent services + +In the non-transparent operation the Split/Combine-function distributes the RLP-frames into substreams so that one whole RLP-frame is carried through one substream. This means that the two 290-bit air-interface blocks carrying one RLP-frame are transmitted through the same substream. Furthermore the RLP-frames are distributed into the available substreams so that the resulting delay in the overall data stream is kept as small as possible. The receiving Split/Combine-function recombines the overall data stream according to the inherent RLP-frame numbering, i.e. the N(S)-numbers in the RLP-frame header (3GPP TS 24.022). + +## 11.2 Substream numbering in transparent operation + +### 11.2.1 Substream numbering for TCH/F4.8 and TCH/F9.6 channel codings + +In transparent multislot data configurations of more than one TCH/F the parallel data substreams between the Split/Combine-functions carry inband substream numbering. The status bits S1, S3, and the X-bit between data bits D12 and D13 (Figures 5 and 6) are used for transferring this substream numbering information (S1 is the MSB and S3 the LSB). The substreams are numbered 0, 1, 2, 3 etc. regardless of the physical channels through which the substreams are transmitted. The highest substream number is one less than the number of physical channels in use at a given time; i.e. the numbering cycle changes when physical channels are either added to or removed from a connection. + +The S4-bit is used for frame synchronisation between the parallel substreams. This bit follows a 31-bit PN-sequence of 0000 1001 0110 0111 1100 0110 1110 101. This thirty one bit sequence is used for substream resynchronisation in cases where delay has occurred on one or more substream(s); the position of a frame in a substream can be determined modulo 31 by the values of the S4-bit in a sequence of 5 consecutive frames including the frame in question. Provided that the relative delay between substreams is less than 75 ms (i.e. less than a 15-frame displacement), this and the frame distribution rules given in subclause 11.1 are sufficient to determine the correct order of the frames. + +Bits S6, S8, S9, and the other X-bit are used for conveying channel control information according to the relevant terminal adapter function specification. + +These rules apply to all multislot data AIURs up to and including 48 kbit/s. When the received 48 kbit/s AIUR is converted into 64 kbit/s rate, the bits extracted from the 60-bit radio interface frames (Figure 5) are mapped into the 32-bit frame format of Figure 13. Here the values for the status bits S1, X, S3, and S4 in the 32-bit frame shall be derived from status bits S6, X, S8, and S9 in the radio-interface frame because status bits S1, X, S3, and S4 in the upper right hand corner of the 60-bit frame have been used for data substream numbering as described above. + +In the 11,2 kbit/s frames used for AIURs 56 and 64 kbit/s (Figure 10) the T1, T2, T3 (T1 the MSB and T3 the LSB) are used for carrying the substream numbering as status bits S1, X, and S3 do according to the definition given in the first paragraph of subclause 10.1. Bit T4 is used for carrying the substream synchronisation sequence just as status bit S4 does in the description given in the second paragraph of this subclause. + +### 11.2.2 Substream numbering for TCH/F14.4 and TCH/F28.8 channel codings + +Bit M1 carries the multiframe sequence 0000 1001 0110 0111 1100 0110 1110 101. The number of the substream in which a multiframe is sent is carried four times in a 31-bit period of the M2-sequence. In the three-bit number code the bit in the lowest bit position is the MSB (See table in subclause 10.3.1). + +## 11.3 Substream Synchronisation + +Two interfaces are involved in the TAF regarding the need for the data frame synchronisation, i.e the TAF/multichannel interface and the TAF/TE interface. + +The Split/Combine function is responsible for controlling the synchronisation and resynchronisation procedures as described in 3GPP TS 27.001. + +## 11.4 Void + +## 11.5 Padding Functions + +### 11.5.1 Padding for TCH/F9.6 and TCH/F4.8 + +When the required AIUR is not a multiple of the rates supported by TCH/F4.8 or TCH/F9.6, padding is used for producing the required AIUR. + +To achieve the required AIUR the data bits are distributed across the substreams 1 to n as follows: + +- Substream(s) 1 (to n-1) carry multiples of the rate supported by the channel coding used. +- Substream n carries the remaining amount of data bits required to achieve the required AIUR. The remainder of data stream n carries padding bits set to binary value '1'. + +#### 11.5.1.1 Padding for AIUR 14,4 kbit/s: + +The frame of the lower substream number carries full 9,6 kbit/s. The frame of the higher substream number carries 4,8 kbit/s of user data in bit positions D1-D24 while bit positions D25-D48 are inserted with binary "1"s. (Figure 15) + +#### 11.5.1.2 Padding for AIUR 64 kbit/s: + +The frames numbered 1-5 carry full 11,2 kbit/s. Frame number 6 carries 8,0 kbit/s of user data in bit positions D1-D40 while bit positions D41-D56 are inserted with binary "1"s. (Figure 16) + +### 11.5.2 Padding for TCH/F14.4 channel coding + +#### 11.5.2.1 Padding for AIURs up to 38,4 kbit/s + +Padding is not necessary for AIURs 14,4 and 28,8 kbit/s. + +For AIUR 38,4 kbit/s the 290-bit blocks in the substreams of the lower substream numbers carry 288 user data bits while the 290-bit blocks in the substream of the highest substream number carries 192 user data bits; this means that five of the eight 36-bit frames making up the block carry 36 user data bits whereas the sixth frame carries 12 user data bits ( $5 \times 36 + 12$ ). Frames seven, eight, and the rest of the sixth frame are padded with '1's. + +#### 11.5.2.2 Padding for AIURs of 48 kbit/s + +The 290-bit blocks in the highest numbered substream carry 96 user data bits ( $2 \times 36 + 24$ ). + +The M2-bit sequences are used, for the applicable parts, as described in subclauses 10.3.1.1. + +#### 11.5.2.3 Padding for AIURs of 56 kbit/s + +The 290-bit blocks in the highest numbered substream carry 256 user data bits ( $7 \times 36 + 4$ ). + +The M2-bit sequences are used, for the applicable parts, as described in subclauses 10.3.1.1. + +#### 11.5.2.4 Padding for AIURs of 64 kbit/s + +The 290-bit blocks in the highest numbered substream carry 128 user data bits ( $3 \times 36 + 20$ ). + +The M2-bit sequences are used, for the applicable parts, as described in subclauses 10.3.1.1. + +## 11.6 Handling of the E1-E3 bits in multislot operation + +Between the Split / Combine functions the substreams carry the code associated with the substream rate as defined in Figure 4. When the substreams are combined the code is set to correspond to the overall AIUR according to Figure 4. + +# 12 Support of Non-Transparent Bearer Services + +In the case of non-transparent services, the RA1' function shall provide access to the 12 and 6 kbit/s radio interface data rates as described below. (Alignment of RLP frames with the four TDMA slots makes it physically impossible to provide 3,6 kbit/s.) The RA1' function is not applied in case of TCH/F14.4, TCH/F28.8 and TCH/F43.2 channel codings. + +| Air interface user rate | Radio interface rate | +|-------------------------|-------------------------------------------| +| 4,8 kbit/s | 6 kbit/s | +| 9,6 kbit/s | 12 kbit/s or 2×6 kbit/s | +| 14,4 kbit/s | 14,5 kbit/s or 2×12 kbit/s or 3×6 kbit/s | +| 19,2 kbit/s | 2×12 kbit/s or 4×6 kbit/s | +| 28,8 kbit/s | 29 kbit/s or 2×14,5 kbit/s or 3×12 kbit/s | +| 38,4 kbit/s | 3×14,5 kbit/s or 4×12 kbit/s | +| 43.2 kbit/s | 43.5 kbit/s or 3×14,5 kbit/s | +| 57.6 kbit/s | 2×29 kbit/s or 4×14,5 kbit/s | + +## 12.1 Support of non-transparent operation for TCH/F9.6 and TCH/F4.8 channel codings + +This access results in the use of a modified ITU-T V.110 60 bit frame for non-transparent services (figure 11). In this case, the RA1' function also provides for alignment of four modified ITU-T V.110 60 bit frames sent on the same radio slot corresponding with each complete 240 bit frame to be encoded by the radio subsystem as a single unit (see 3GPP TS 45.003). The difference between the non-transparent 60 bit frame and the 60 bit frame for the transparent service is that the bit positions used for status in a transparent frame are used to carry data (designated as D' bits in figure 11). + +NOTE: The status bits SA, SB, and the X bit are embedded in the L2R-PDU frames (see 3GPP TS 27.001, and 27.002). + +The first bit of each RLP frame to be transmitted corresponds to the first bit (D1) of the first 60 bit frame in a four frame sequence and the last bit corresponds to the last bit (D'12) of the last 60 bit frame in a four frame sequence. Each 60 bit frame is filled from left to right starting at D1 (see figure 11). + +The radio subsystem provides for the synchronous transmission and reception of 240 bit RLP frames through a connection consisting of up to four TCH/Fs. An RLP-frame is received/sent from/to a particular radio channel every 20 ms (12 kbit/s radio interface rate) or every 40 ms (6 kbit/s radio interface rate) irrespective of the user rate. + +The request to use 6 kbit/s radio interface rate on a Full Rate Channel is indicated in the BC-IE by setting the NIRR bit to 6 kbit/s (Negotiation procedure see 3GPP TS 27.001) and selecting a Full Rate Channel and Non-Transparent service. If the entity receiving the BC-IE is unable to support this request then the 12 kbit/s radio interface rate shall be provided automatically. + +Occasions may arise when there is no RLP frame ready to be transmitted. In this case a frame of 240 zeroes are transmitted. This is discarded by the distant RLP function, due to FCS failure, but allows physical link synchronization to be maintained between the MS and the MSC. + +In the case of an asymmetric connection the BTS shall send V110 idle frames towards the MSC on the channels which are unused in the direction from the MS towards the MSC. This ensures that the IWF does not interpret V110 frames which are not originated from the MS as complete RLP frames. + +## 12.2 Support of non-transparent operation for TCH/F14.4 channel coding + +In 14,4 kbit/s channel 576-bit RLP-frames shall be used as described below. + +The RA1' function is not applied in this case. Instead the RLP-, or in multislot operation the Split/Combine- function, handles the 290-bit data blocks received/sent from/to the network. The M1- bit is used for indicating the RLP-frame halves: in the first half M1= 0 and in the second half M1=1. Bit M2 is used for DTX-indication between the BSS and MSC as described in 3GPP TS 48.020 + +In cases where no RLP-frame is ready to be transmitted, a sequence of 576 '1's is transmitted. This frame is discarded by the distant RLP-function due to FCS failure. + +In the case of an asymmetric connection the BTS shall send idle frames towards the IWF on the channels which are unused in the direction from the MS towards the MSC, as specified in 3GPP TS 08.60. This ensures that the IWF does not interpret sequences of frames which are not originated from the MS as complete RLP frames. + +## 12.3 Support of non-transparent operation for TCH/F28.8 channel coding + +In a 28.8 kbit/s channel, 576-bit RLP-frames shall be used as described below. The 576-bit RLP-frames shall be mapped into the 580-bit radio interface blocks as described in section 9.1. + +The RA1' function is not applied in this case. Instead, RLP handles the 580-bit data blocks received/sent from/to the Split/Combine function. The M1- bits are used for indicating RLP-frame halves. The M2-bits are used for DTX-indication between the BSS and MSC as described in 3GPP TS 48.020. + +In cases where no RLP-frame is ready to be transmitted, a sequence of 576 '1's is transmitted. This frame is discarded by the distant RLP-function due to FCS failure. + +## 12.4 Support of non-transparent operation for TCH/F43.2 channel coding + +In a 43.2 kbit/s channel 576-bit RLP-frames shall be used as described below. The 576-bit RLP-frames shall be mapped into 870-bit radio interface blocks as described in section 9.3. + +The RA1' function is not applied in this case. Instead, RLP handles the 580-bit data blocks received/sent from/to the Split/Combine function. The M1- bits are used for indicating RLP-frame halves. The M2-bits are used for DTX-indication between the BSS and MSC as described in 3GPP TS 48.020. + +In cases where no RLP-frame is ready to be transmitted, a sequence of 576 '1's is transmitted. This frame is discarded by the distant RLP-function due to FCS failure. + +# 13 Figures on Frame structures + +| Octet No. | Bit number | | | | | | | | +|-----------|------------|-----|-----|-----|-----|-----|-----|----| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 2 | 1 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 3 | 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 4 | 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| 5 | 1 | E1 | E2 | E3 | E4 | E5 | E6 | E7 | +| 6 | 1 | D25 | D26 | D27 | D28 | D29 | D30 | S6 | +| 7 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | X | +| 8 | 1 | D37 | D38 | D39 | D40 | D41 | D42 | S8 | +| 9 | 1 | D43 | D44 | D45 | D46 | D47 | D48 | S9 | + +Figure 3: The ITU-T V.110 80 bit RA1 frame structure + +| Intermediate Data Rate | | | | E1 | E2 | E3 | Note | +|------------------------|-----------|---------|---------|----|----|----|------| +| 8 kbit/s | 16 kbit/s | 32 kb/s | 64 kb/s | | | | | +| 600 | | | | 1 | 0 | 0 | | +| 1200 | | | | 0 | 1 | 0 | | +| 2400 | | | | 1 | 1 | 0 | | +| 4800 | 9600 | 19200 | 38400 | 0 | 1 | 1 | | +| | | 14400 | 28800 | 1 | 0 | 1 | | + +NOTE: The 300 bit/s user data rate is carried on the 600 bit/s synchronous stream by adding stop elements, see subclause 4.1. + +Figure 4: Coding of data rates + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| D7 | D8 | D9 | D10 | D11 | D12 | X | +| D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| E4 | E5 | E6 | E7 | D25 | D26 | D27 | +| D28 | D29 | D30 | S6 | D31 | D32 | D33 | +| D34 | D35 | D36 | X | D37 | D38 | D39 | +| D40 | D41 | D42 | S8 | D43 | D44 | D45 | +| D46 | D47 | D48 | S9 | | | | + +Figure 5: Modified ITU-T V.110 60 bit frame for 9,6 kbit/s transparent data + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| D7 | D8 | D9 | D10 | D11 | D12 | X | +| D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| E4 | E5 | E6 | E7 | D25 | D26 | D27 | +| D28 | D29 | D30 | S6 | D31 | D32 | D33 | +| D34 | D35 | D36 | X | D37 | D38 | D39 | +| D40 | D41 | D42 | S8 | D43 | D44 | D45 | +| D46 | D47 | D48 | S9 | | | | + +Figure 6: Modified ITU-T V.110 60 bit frame for 4,8. kbit/s transparent data + +a) + +| | | | | | | | | +|-----|-----|-----|----|-----|-----|-----|----| +| D1 | D2 | D3 | S1 | D4 | D5 | D6 | X | +| D7 | D8 | D9 | S3 | D10 | D11 | D12 | S4 | +| E4 | E5 | E6 | E7 | D13 | D14 | D15 | S6 | +| D16 | D17 | D18 | X | D19 | D20 | D21 | S8 | +| D22 | D23 | D24 | S9 | | | | | + +b) + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D1 | D2 | D2 | D3 | D3 | S1 | +| 1 | D4 | D4 | D5 | D5 | D6 | D6 | X | +| 1 | D7 | D7 | D8 | D8 | D9 | D9 | S3 | +| 1 | D10 | D10 | D11 | D11 | D12 | D12 | S4 | +| 1 | 1 | 1 | 0 | E4 | E5 | E6 | E7 | +| 1 | D13 | D13 | D14 | D14 | D15 | D15 | S6 | +| 1 | D16 | D16 | D17 | D17 | D18 | D18 | X | +| 1 | D19 | D19 | D20 | D20 | D21 | D21 | S8 | +| 1 | D22 | D22 | D23 | D23 | D24 | D24 | S9 | + +Figure 7: a) Modified ITU-T V.110 36 bit frame for 2,4 kbit/s transparent data and b) the corresponding intermediate rate frame at 8 kbit/s + +a) + +| | | | | | | | | +|-----|-----|-----|----|-----|-----|-----|----| +| D1 | D1 | D2 | S1 | D2 | D3 | D3 | X | +| D4 | D4 | D5 | S3 | D5 | D6 | D6 | S4 | +| E4 | E5 | E6 | E7 | D7 | D7 | D8 | S6 | +| D8 | D9 | D9 | X | D10 | D10 | D11 | S8 | +| D11 | D12 | D12 | S9 | | | | | + +b) + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D1 | D1 | D1 | D2 | D2 | S1 | +| 1 | D2 | D2 | D3 | D3 | D3 | D3 | X | +| 1 | D4 | D4 | D4 | D4 | D5 | D5 | S3 | +| 1 | D5 | D5 | D6 | D6 | D6 | D6 | S4 | +| 1 | 0 | 1 | 0 | E4 | E5 | E6 | E7 | +| 1 | D7 | D7 | D7 | D7 | D8 | D8 | S6 | +| 1 | D8 | D8 | D9 | D9 | D9 | D9 | X | +| 1 | D10 | D10 | D10 | D10 | D11 | D11 | S8 | +| 1 | D11 | D11 | D12 | D12 | D12 | D12 | S9 | + +Figure 8: a) Modified ITU-T V.110 36 bit frame for 1,2 kbit/s transparent data and b) the corresponding intermediate rate frame at 8 kbit/s + +a) + +| | | | | | | | | +|----|----|----|----|----|----|----|----| +| D1 | D1 | D1 | S1 | D1 | D2 | D2 | X | +| D2 | D2 | D3 | S3 | D3 | D3 | D3 | S4 | +| E4 | E5 | E6 | E7 | D4 | D4 | D4 | S6 | +| D4 | D5 | D5 | X | D5 | D5 | D6 | S8 | +| D6 | D6 | D6 | S9 | | | | | + +NOTE: The 300 bit/s user data rate is carried on the 600 bit/s synchronous stream by adding stop elements, see subclause 4.1. + +b) + +| | | | | | | | | +|---|----|----|----|----|----|----|-----------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D1 | D1 | D1 | D1 | D1 | S1 | +| 1 | D1 | D1 | D2 | D2 | D2 | D2 | X | +| 1 | D2 | D2 | D2 | D2 | D3 | D3 | S3 | +| 1 | D3 | D3 | D3 | D3 | D3 | D3 | S4 | +| 1 | 1 | 0 | 0 | E4 | E5 | E6 | E7 (note) | +| 1 | D4 | D4 | D4 | D4 | D4 | D4 | S6 | +| 1 | D4 | D4 | D5 | D5 | D5 | D5 | X | +| 1 | D5 | D5 | D5 | D5 | D6 | D6 | S8 | +| 1 | D6 | D6 | D6 | D6 | D6 | D6 | S9 | + +NOTE: In order to maintain compatibility with Recommendation X.30 (I.461), for the 600 bit/s user rate bit E7 is coded to enable the 4×80 bit multiframe synchronisation. To this end, E7 in the fourth 80 bit frame is set to binary '0'. See Table 6 of ITU-T Recommendation V.110(09/92). + +**Figure 9: a) Modified ITU-T V.110 36 bit frame for 600 bit/s transparent data and b) the corresponding intermediate rate frame at 8 kbit/s** + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | T1 | +| D7 | D8 | D9 | D10 | D11 | D12 | T2 | +| D13 | D14 | D15 | D16 | D17 | D18 | T3 | +| D19 | D20 | D21 | D22 | D23 | D24 | T4 | +| D25 | D26 | D27 | D28 | D29 | D30 | D31 | +| D32 | D33 | D34 | D35 | D36 | D37 | D38 | +| D39 | D40 | D41 | D42 | D43 | D44 | D45 | +| D46 | D47 | D48 | D49 | D50 | D51 | D52 | +| D53 | D54 | D55 | D56 | | | | + +**Figure 10: Modified ITU-T V.110 60 bit frame for 11,2 kbit/s partial rate** + +| | | | | | | | +|-----|-----|-----|------|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | D'1 | +| D7 | D8 | D9 | D10 | D11 | D12 | D'2 | +| D13 | D14 | D15 | D16 | D17 | D18 | D'3 | +| D19 | D20 | D21 | D22 | D23 | D24 | D'4 | +| D'5 | D'6 | D'7 | D'8 | D25 | D26 | D27 | +| D28 | D29 | D30 | D'9 | D31 | D32 | D33 | +| D34 | D35 | D36 | D'10 | D37 | D38 | D39 | +| D40 | D41 | D42 | D'11 | D43 | D44 | D45 | +| D46 | D47 | D48 | D'12 | | | | + +**Figure 11: Modified ITU-T V.110 60 bit frame for non-transparent data** + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 1 | D7 | D8 | D9 | D10 | F | F | X | +| 1 | D11 | D12 | F | F | D13 | D14 | S3 | +| 1 | F | F | D15 | D16 | D17 | D18 | S4 | +| 1 | 1 | 0 | 1 | E4 | E5 | E6 | E7 | +| 1 | D19 | D20 | D21 | D22 | D23 | D24 | S6 | +| 1 | D25 | D26 | D27 | D28 | F | F | X | +| 1 | D29 | D30 | F | F | D31 | D32 | S8 | +| 1 | F | F | D33 | D34 | D35 | D36 | S9 | + +F =Fill bits, which are set to 1. + +**Figure 12: The ITU-T V.110 80 bit frame for 3.6 kbit/s transparent data (8 kbit/s intermediate rate)** + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 0 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | + +**Figure 13: The ITU-T V.110 32 bit 48 kbit/s frame structure (64 kbit/s intermediate rate)** + +| | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|---| +| D1 | D2 | D3 | D4 | D5 | D6 | D7 | 1 | +| D8 | D9 | D10 | D11 | D12 | D13 | D14 | 1 | +| D15 | D16 | D17 | D18 | D19 | D20 | D21 | 1 | +| D22 | D23 | D24 | D25 | D26 | D27 | D28 | 1 | +| D29 | D30 | D31 | D32 | D33 | D34 | D35 | 1 | +| D36 | D37 | D38 | D39 | D40 | D41 | D42 | 1 | +| D43 | D44 | D45 | D46 | D47 | D48 | D49 | 1 | +| D50 | D51 | D52 | D53 | D54 | D55 | D56 | 1 | + +**Figure 14: The ITU-T V.110 64 bit 56 kbit/s frame structure (64 kbit/s intermediate rate, option without status bits)** + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|----| +| D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| D7 | D8 | D9 | D10 | D11 | D12 | X | +| D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| E4 | E5 | E6 | E7 | 1 | 1 | 1 | +| 1 | 1 | 1 | S6 | 1 | 1 | 1 | +| 1 | 1 | 1 | X | 1 | 1 | 1 | +| 1 | 1 | 1 | S8 | 1 | 1 | 1 | +| 1 | 1 | 1 | S9 | | | | + +**Figure 15: Modified ITU-T V.110 60 bit frame for a padded 9,6 kbit/s transparent data frame carrying 4,8 kbit/s with padding** + +| | | | | | | | +|-----|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | T1 | +| D7 | D8 | D9 | D10 | D11 | D12 | T2 | +| D13 | D14 | D15 | D16 | D17 | D18 | T3 | +| D19 | D20 | D21 | D22 | D23 | D24 | T4 | +| D25 | D26 | D27 | D28 | D29 | D30 | D31 | +| D32 | D33 | D34 | D35 | D36 | D37 | D38 | +| D39 | D40 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 1 | 1 | 1 | 1 | | | | + +**Figure 16: Modified ITU-T V.110 60 bit frame for a padded 11,2 kbit/s transparent data frame carrying 8.0 kbit/s with padding** + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | +| D7 | D8 | D9 | D10 | D11 | D12 | +| D13 | D14 | D15 | D16 | D17 | D18 | +| D19 | D20 | D21 | D22 | D23 | D24 | +| D25 | D26 | D27 | D28 | D29 | D30 | +| D31 | D32 | D33 | D34 | D35 | D36 | + +**Figure 17: Modified ITU-T V.110 36-bit frame received/sent from/to the network at 14,4 kbit/s** + +# Annex A (Informative): Stacks of rate adaptation + +## A.1 Stacks of rate adaptation for 9,6/4,8 kbit/s single slot operation + +For transparent data services, the following stacks of rate adaptation are possible: + +![Diagram showing rate adaptation stacks for ASY, SYN, and FAX+FA services across DTE, MT, and BSS layers.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +The diagram illustrates the rate adaptation process for three different services: ASY, SYN, and FAX+FA. The layers involved are DTE (Data Terminal Equipment), MT (Mobile Terminal), and BSS (Base Station System). The adaptation steps are as follows: + +- DTE Layer:** Data from ASY, SYN, and FAX+FA is processed through an adaptation block labeled [R]. +- MT Layer:** The output of the [R] block for ASY is processed by RA0. The output of RA0, as well as the direct output of the [R] block for SYN, and the direct output of the [R] block for FAX+FA, are all processed by a common adaptation block labeled RA1'. +- BSS Layer:** The output of RA1' is processed by a block labeled FEC (12 or 6 kbit/s). The output of the FEC block is then processed by an adaptation block labeled RA1'/RA1, which finally leads to the RA2 block. + +Diagram showing rate adaptation stacks for ASY, SYN, and FAX+FA services across DTE, MT, and BSS layers. + +For the non-transparent services, the following stacks of rate adaptation and functions are possible: + +![A vertical flowchart showing the protocol stack for non-transparent services. The stack consists of several layers: ASY, [R], RLP + L2R, RA1', FEC (12 or 6 kbit/s), RA1'/RA1, and RA2. These layers are grouped into three entities on the left: DTE (containing ASY and [R]), MT (containing RLP + L2R, RA1', and FEC), and BSS (containing RA1'/RA1 and RA2). Arrows indicate a downward flow between the layers.](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +``` +graph TD; subgraph DTE; ASY[ASY]; R["[R]"]; end; subgraph MT; RLP["RLP + L2R"]; RA1["RA1'"]; FEC["FEC (12 or 6 kbit/s)"]; end; subgraph BSS; RA1RA1["RA1'/RA1"]; RA2["RA2"]; end; ASY --> R; R --> RLP; RLP --> RA1; RA1 --> FEC; FEC --> RA1RA1; RA1RA1 --> RA2; +``` + +A vertical flowchart showing the protocol stack for non-transparent services. The stack consists of several layers: ASY, [R], RLP + L2R, RA1', FEC (12 or 6 kbit/s), RA1'/RA1, and RA2. These layers are grouped into three entities on the left: DTE (containing ASY and [R]), MT (containing RLP + L2R, RA1', and FEC), and BSS (containing RA1'/RA1 and RA2). Arrows indicate a downward flow between the layers. + +## A.2 Stacks of rate adaptation for 14,4 kbit/s single slot operation + +For transparent data services, the following stacks of rate adaptation are possible: + +![Flowchart showing rate adaptation stacks for ASY, SYN, and FAX+FA services through various adaptation layers (RA0, RA1', FEC, RA1'/RAA', RAA', RA2) across DTE, MT, and BSS domains.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +The diagram illustrates three parallel rate adaptation stacks for different services: ASY, SYN, and FAX+FA. The layers are organized vertically from top to bottom, corresponding to the DTE, MT, and BSS domains. + +- DTE Domain:** Contains three service boxes: ASY, SYN, and FAX+FA. Each service has a downward arrow to a box labeled [R]. +- MT Domain:** + - The ASY [R] box has a downward arrow to an RA0 box. + - The SYN [R] and FAX+FA [R] boxes have downward arrows that bypass RA0 and point directly to the RA1' box. + - The RA0 box has a downward arrow to the RA1' box. + - All three paths (from RA0, SYN [R], and FAX+FA [R]) converge into a single RA1' box. + - The RA1' box has a downward arrow to an FEC (14.5 kbit/s) box. +- BSS Domain:** + - The FEC (14.5 kbit/s) box has a downward arrow to an RA1'/RAA' box. + - The RA1'/RAA' box has a downward arrow to an RAA' box. + - The RAA' box has a downward arrow to an RA2 box. + +Flowchart showing rate adaptation stacks for ASY, SYN, and FAX+FA services through various adaptation layers (RA0, RA1', FEC, RA1'/RAA', RAA', RA2) across DTE, MT, and BSS domains. + +For the non-transparent services, the following stacks of rate adaptation and functions are possible: + +![Flowchart showing the stack of rate adaptation and functions for non-transparent services. The stack starts with ASY at the DTE layer, followed by [R], RLP + L2R at the MT layer, FEC (14.5 kbit/s), RA1'/RAA', RAA', and RA2 at the BSS layer.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +``` +graph TD; DTE --- ASY[ASY]; ASY --> R["[R]"]; R --> MT["RLP + L2R"]; MT --> FEC["FEC (14.5 kbit/s)"]; FEC --> RA1RAA["RA1'/RAA'"]; RA1RAA --> RAA["RAA'"]; RAA --> RA2["RA2"]; +``` + +The diagram illustrates the protocol stack for non-transparent services. It is divided into three layers: DTE, MT, and BSS. The DTE layer contains the ASY block. The MT layer contains the [R], RLP + L2R, and FEC (14.5 kbit/s) blocks. The BSS layer contains the RA1'/RAA', RAA', and RA2 blocks. Arrows indicate the flow of data from top to bottom: ASY to [R], [R] to RLP + L2R, RLP + L2R to FEC (14.5 kbit/s), FEC (14.5 kbit/s) to RA1'/RAA', RA1'/RAA' to RAA', and RAA' to RA2. + +Flowchart showing the stack of rate adaptation and functions for non-transparent services. The stack starts with ASY at the DTE layer, followed by [R], RLP + L2R at the MT layer, FEC (14.5 kbit/s), RA1'/RAA', RAA', and RA2 at the BSS layer. + +## A.3 Stacks of rate adaptation for 9,6/4,8 kbit/s multi slot operation + +For transparent data services, the following stacks of rate adaptation are possible: + +![Diagram showing two stacks of rate adaptation for 9,6/4,8 kbit/s multi slot operation. The diagram is divided into three horizontal sections: DTE, MT, and BSS. The left stack shows ASY, SYN¹, and FAX+FA data streams passing through [R] and RA0 blocks, then merging into S/C / RA1' blocks, followed by FEC (12 or 6 kbit/s) and RA1'/RA1 blocks, ending in a MUX. The right stack shows SYN² data streams passing through [R] and S/C / RA1' blocks, then merging into FEC (12 or 6 kbit/s) and S/C / RA1'/RA1](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +``` +graph TD; subgraph DTE; ASY[ASY]; SYN1[SYN¹]; FAXFA[FAX+FA]; SYN2[SYN²]; end; subgraph MT; RA0[RA0]; SCRA1p[S/C / RA1']; SCRA1p2[S/C / RA1']; FEC[FEC (12 or 6 kbit/s)]; FEC2[FEC (12 or 6 kbit/s)]; RA1RA1[RA1'/RA1]; SCRA1pRA1q[S/C / RA1'/RA1"]; end; subgraph BSS; MUX[MUX]; end; ASY --> R1[R]; SYN1 --> R2[R]; FAXFA --> R3[R]; SYN2 --> R4[R]; R1 --> RA0; RA0 --> SCRA1p; R2 --> SCRA1p; R3 --> SCRA1p; R4 --> SCRA1p2; SCRA1p --> FEC; SCRA1p2 --> FEC2; FEC --> RA1RA1; FEC2 --> SCRA1pRA1q; RA1RA1 --> MUX; +``` + +Diagram showing two stacks of rate adaptation for 9,6/4,8 kbit/s multi slot operation. The diagram is divided into three horizontal sections: DTE, MT, and BSS. The left stack shows ASY, SYN¹, and FAX+FA data streams passing through [R] and RA0 blocks, then merging into S/C / RA1' blocks, followed by FEC (12 or 6 kbit/s) and RA1'/RA1 blocks, ending in a MUX. The right stack shows SYN² data streams passing through [R] and S/C / RA1' blocks, then merging into FEC (12 or 6 kbit/s) and S/C / RA1'/RA1 + +Note 1: for synchronous data services with user rates < 48 kbit/s +Note 2: for synchronous data services with user rates 48, 56 and 64 kbit/s + +For the non-transparent services, the following stacks of rate adaptation and functions are possible: + +![A vertical flowchart showing the protocol stack for non-transparent services. The stack consists of several layers: ASY, [R], RLP + L2R, S/C, RA1', FEC (12 or 6 kbit/s), RA1'/RA1, and MUX. These layers are grouped into three entities: DTE (containing ASY and [R]), MT (containing RLP + L2R, S/C, RA1', and FEC), and BSS (containing RA1'/RA1 and MUX). Arrows indicate the downward flow of data between layers.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +``` +graph TD; subgraph DTE; ASY[ASY] --> R["[R]"]; end; subgraph MT; R --> RLP["RLP + L2R"]; RLP --> SC["S/C"]; SC --> RA1["RA1'"]; RA1 --> FEC["FEC (12 or 6 kbit/s)"]; end; subgraph BSS; FEC --> RA1RA1["RA1'/RA1"]; RA1RA1 --> MUX["MUX"]; end; +``` + +A vertical flowchart showing the protocol stack for non-transparent services. The stack consists of several layers: ASY, [R], RLP + L2R, S/C, RA1', FEC (12 or 6 kbit/s), RA1'/RA1, and MUX. These layers are grouped into three entities: DTE (containing ASY and [R]), MT (containing RLP + L2R, S/C, RA1', and FEC), and BSS (containing RA1'/RA1 and MUX). Arrows indicate the downward flow of data between layers. + +## A.4 Stacks of rate adaptation for 14,4 kbit/s multi slot operation + +For transparent data services, the following stacks of rate adaptation are possible: + +![Diagram showing two stacks of rate adaptation for 14,4 kbit/s multi slot operation. The diagram is divided into three horizontal sections: DTE, MT, and BSS. The left stack shows ASY, SYN1, and FAX+FA data streams passing through rate adaptation blocks [R], RA0, S/C / RA1', FEC (14.5 kbit/s), RA1'/RAA', RAA', and finally MUX. The right stack shows SYN2 data passing through [R], S/C / RA1', FEC (14.5 kbit/s), and S/C / RA1'/RAA''.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +The diagram illustrates two possible rate adaptation stacks for 14,4 kbit/s multi slot operation, categorized by the type of data service (ASY, SYN1, FAX+FA, or SYN2) and the network element (DTE, MT, BSS). + +**Stack 1 (Left):** Data from ASY, SYN1, and FAX+FA passes through rate adaptation blocks [R] at the DTE level. At the MT level, the data from ASY goes through RA0, while SYN1 and FAX+FA pass through. All three streams then enter the S/C / RA1' block. The output of S/C / RA1' goes through the FEC (14.5 kbit/s) block. The output of FEC (14.5 kbit/s) then passes through RA1'/RAA' and RAA' blocks at the BSS level, finally reaching the MUX. + +**Stack 2 (Right):** Data from SYN2 passes through a rate adaptation block [R] at the DTE level. It then enters the S/C / RA1' block at the MT level. The output of S/C / RA1' goes through the FEC (14.5 kbit/s) block. The output of FEC (14.5 kbit/s) then passes through the S/C / RA1'/RAA'' block at the BSS level. + +Diagram showing two stacks of rate adaptation for 14,4 kbit/s multi slot operation. The diagram is divided into three horizontal sections: DTE, MT, and BSS. The left stack shows ASY, SYN1, and FAX+FA data streams passing through rate adaptation blocks [R], RA0, S/C / RA1', FEC (14.5 kbit/s), RA1'/RAA', RAA', and finally MUX. The right stack shows SYN2 data passing through [R], S/C / RA1', FEC (14.5 kbit/s), and S/C / RA1'/RAA''. + +Note 1: for synchronous data services with user rates < 64 kbit/s +Note 2: for synchronous data services with user rate 64 kbit/s + +For the non-transparent services, the following stacks of rate adaptation and functions are possible: + +![A vertical flowchart showing protocol stacks for DTE, MT, and BSS layers. The DTE layer contains ASY and [R]. The MT layer contains RLP + L2R, S/C, and FEC (14.5 kbit/s). The BSS layer contains RA1'/RAA', RAA', and MUX. Arrows indicate the flow of data between these components.](b58cedaf15ad4f0edee5621820865ccc_img.jpg) + +``` +graph TD; subgraph DTE; ASY[ASY] --> R["[R]"]; end; subgraph MT; R --> RLP["RLP + L2R"]; RLP --> SC["S/C"]; SC --> FEC["FEC (14.5 kbit/s)"]; end; subgraph BSS; FEC --> RA1["RA1'/RAA'"]; RA1 --> RAA["RAA'"]; RAA --> MUX["MUX"]; end; +``` + +A vertical flowchart showing protocol stacks for DTE, MT, and BSS layers. The DTE layer contains ASY and [R]. The MT layer contains RLP + L2R, S/C, and FEC (14.5 kbit/s). The BSS layer contains RA1'/RAA', RAA', and MUX. Arrows indicate the flow of data between these components. + +## A.5 Stacks of rate adaptation for EDGE channels TCH28.8 and TCH/F43.2 (NT only) + +For transparent data services, the following stacks of rate adaptation are possible: + +![A flowchart showing the stack of rate adaptation for EDGE channels. It starts at the DTE level with ASY and SYN inputs, which are processed through [R] and RA0 blocks. At the MT level, the data goes through S/C / RA1' and EDGE MUX blocks. This is followed by a FEC (29.0 kbit/s) block. At the BSS level, the data passes through another EDGE MUX, RA1'/RAA', RAA', and finally a MUX block.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` +graph TD; subgraph DTE; ASY[ASY] --> R1[R]; SYN[SYN] --> R2[R]; end; R1 --> RA0[RA0]; RA0 --> MT; subgraph MT; S_C_RA1[S/C / RA1'] --> EDGE_MUX1[EDGE MUX]; end; EDGE_MUX1 --> FEC[FEC 29.0 kbit/s]; FEC --> BSS; subgraph BSS; EDGE_MUX2[EDGE MUX] --> RA1_RAA[RA1'/RAA']; RA1_RAA --> RAA[RAA']; RAA --> MUX[MUX]; end; +``` + +A flowchart showing the stack of rate adaptation for EDGE channels. It starts at the DTE level with ASY and SYN inputs, which are processed through [R] and RA0 blocks. At the MT level, the data goes through S/C / RA1' and EDGE MUX blocks. This is followed by a FEC (29.0 kbit/s) block. At the BSS level, the data passes through another EDGE MUX, RA1'/RAA', RAA', and finally a MUX block. + +For the non-transparent services, the following stacks of rate adaptation and functions are possible: + +![Flowchart showing the stack of rate adaptation and functions for non-transparent services across DTE, MT, and BSS layers.](13fde41de77bf026013a0b81684d1fc9_img.jpg) + +The diagram illustrates the protocol stack for non-transparent services, showing the flow of data from the DTE (Data Terminal Equipment) through the MT (Mobile Terminal) and into the BSS (Base Station System). + +**Stack Components and Flow:** + +- DTE Layer:** + - Starts with **ASY** (Asynchronous). + - Followed by **[R]** (Reliable). + - Then **RLP + L2R** (RLP + Layer 2 Relocation). +- MT Layer (Mobile Terminal):** + - Contains a dashed box with **S/C** (Service Control) and **EDGE MUX** (Edge Multiplexer). + - The flow from **RLP + L2R** enters this box through **S/C** and exits through **EDGE MUX**. +- Intermediate:** + - Between the MT and BSS layers is **FEC (29.0 or 43.5 kbit/s)** (Forward Error Correction). +- BSS Layer (Base Station System):** + - Contains a dashed box with **EDGE MUX** and **RA1'/RAA'** (Rate Adaptation 1' / Rate Adaptation A'). + - The flow from **FEC** enters this box through **EDGE MUX** and exits through **RA1'/RAA'**. + - Following the BSS box is **RAA'** (Rate Adaptation A'). + - The final component is **MUX** (Multiplexer). + +**Visual Details:** The flow is indicated by downward arrows. Double-lined arrows are used between **S/C** and **EDGE MUX** in the MT, and between **EDGE MUX** and **RA1'/RAA'** in the BSS. The **RA1'/RAA'** and **RAA'** blocks are shown with a shadow effect. + +Flowchart showing the stack of rate adaptation and functions for non-transparent services across DTE, MT, and BSS layers. + +# --- Annex B (Informative):An example of mapping Network Independent Clocking information for TCH/F14.4 when the S-interface is deployed + +In the following, when data bits are moved forwards or backwards between data frames and blocks, padded bit positions are skipped, and the data is moved between bit positions occupied by data bits, i.e. data bit positions. + +### Negative compensation: + +- a) From overall data stream to substreams + +When the data is mapped from the V.110-frames to the radio interface blocks, the 'extra null bit' (subclause 5.1.1) is dropped and remapped to the first data bit position of radio interface block number 28, which is the block carrying the fifth N-bit in the 31-block multiframe structure. + +- b) From substreams to overall data stream + +When a radio interface block carrying the fifth bit of an NIC-code indicating negative compensation is received, the receiver discards the data in the first data bit position of the block. + +## Positive compensation: + +- a) From overall data stream to substreams + +When the data is mapped from the V.110-frames to the radio interface blocks, the extra bit — either 0 or 1 — is added to the data flow in the correct position (subclause 5.1.1). This means that the 36-bit frame (inside a radio interface block) in which this has taken place has a bit overflow; this overflow is carried over to the next frames and to the next radio interface blocks; i.e. bit position 1 of the following frame/block would carry the user data bit that originally was the last non-padded bit in the previous frame/block. The overflow is halted in the block carrying the second bit of the NIC-code; the value of the N-bit carried by this block (by bit M2) is set to either 1 or 0 depending on the value of the bit that would be mapped to the first data bit position of the block if the overflow carry over would continue. If this bit is a 1, the N-bit is set to 0 (positive compensation of a 1); if the bit is a 0, the N-bit is set to 1 (positive compensation of a 0). The bit that has been thus coded is not mapped to the first data bit position but carried by the NIC-code. The following bits are moved up by one data bit position. + +- b) From substreams to overall data stream + +When a radio interface block indicating positive compensation is received from the radio, the NIC is decoded and the data is mapped into the V.110-frames in the overall data stream. Decoding the NIC means that an 'extra bit' emerges. This bit takes its real place in the overall data stream (before the first data bit position of the block carrying the second bit of the NIC-code.) Thus a bit overflow results. This overflow is carried over the V.110-frames until an air-interface block associated with the M2-bit carrying the fifth bit of the NIC-code (subclause 5.1.1) has been fully received. After such block is received the next two suitable V.110-frames carry an NIC-code; the overflow of one bit which has been carried over a sequence of V.110-frames halts here as the second V.110-frame carries one extra bit; the value of the D-bit following the E4-E7 sequence in the V.110-frame is carried by the NIC-code and the following data bits are moved up by one step in the V.110-frame. + +# Annex C (Informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-----------------------------------------------------------------------------------------------------|-----------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| - | s21 | - | A004 | | HSCSD | 5.0.0 | 5.1.0 | +| - | s21 | - | A005 | | Support of 14.4 kbit/s (Radio interface related) | 5.0.0 | 5.1.0 | +| - | s22 | - | A006 | | Corrections and improvements for 14.4 kbit/s | 5.1.1 | 5.2.0 | +| - | s22 | - | A007 | | Clarification to HSCSD | 5.1.1 | 5.2.0 | +| - | s23 | - | A008 | | Editorial changes, rate adaptation procedure | 5.2.0 | 5.3.0 | +| - | s24 | - | A009 | | Removal of 2*14.4=19.2 Transparent configuration | 5.3.0 | 5.4.0 | +| - | s24 | - | A010 | | Update of the protocol stack models in Annex A | 5.3.0 | 5.4.0 | +| - | s25 | - | A011 | | Clarification to the association between channel codings and intermediate rates | 5.4.0 | 5.5.0 | +| - | s27 | - | A012 | | Synchronisation | 5.5.0 | 7.0.0 | +| - | s27 | - | A013 | | Break handling | 7.0.0 | 7.0.1 | +| - | s29 | - | A014 | | Introduction of EDGE channel codings into the specifications | 7.0.1 | 8.0.0 | +| - | s32 | - | A018 | | Harmonisation of split / combine function | 8.0.0 | 8.1.0 | +| 09-2000 | TSG#09 | NP-000551 | A019 | 1 | 32 kbit/s UDI/RDI multimedia in GSM | 8.1.0 | 8.2.0 | +| 12-2000 | TSG#10 | NP-000604 | A020 | | Removal of the 1200/75 bit/s data rate and general clean-up | 8.2.0 | 8.3.0 | +| 12-2000 | TSG#10 | NP-000605 | A021 | | Handover for 56 kbit/s | 8.2.0 | 8.3.0 | +| 12-2000 | TSG#10 | NP-000606 | A022 | | Removal of BS30 NT - moved from [04.21 to 44.021] | 8.3.0 | 4.0.0 | +| 12-2001 | TSG#14 | NP-010604 | 001 | 1 | Terminology clarifications requested by TSG GERAN | 4.0.0 | 5.0.0 | +| 09-2002 | TSG#17 | NP-020405 | 002 | 3 | Correction of Rate Adaptation RA1/RA1' for higher User Rates and removal of S Reference Point in MS | 5.0.0 | 5.1.0 | +| 09-2002 | TSG#17 | NP-020405 | 003 | | Correction of protocol stacks in annex A | 5.0.0 | 5.1.0 | +| 10-2002 | | | | | Replace corrupted diagram in figure 2a | 5.1.0 | 5.1.1 | +| 12-2002 | TSG#18 | NP-020617 | 004 | 1 | CS Data Services (including HSCSD and EDGE) for GERAN lu mode | 5.1.1 | 5.2.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.2.0 | 6.0.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.0.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.0.0 | 9.0.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | +| 2014-10 | | | | | Automatic upgrade from previous Release | 11.0.0 | 12.0.0 | +| 2014-12 | | | | | Automatic upgrade from previous Release | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | | Automatic upgrade from previous Release | 15.0.0 | +| 2020-07 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44031/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-16/44_series/44031/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..273fbee36385819273fae860e0e6cc1cf907fb39 --- /dev/null +++ b/marked/Rel-16/44_series/44031/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0943a812a8495cea3be9332f0367f3e82d773950d78ce8dc3748b1b993bb2036 +size 26735 diff --git a/marked/Rel-16/44_series/44031/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-16/44_series/44031/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..693992aeea3ceffc4042d5b16811eb01f2c512c6 --- /dev/null +++ b/marked/Rel-16/44_series/44031/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec5a4d710f6f56013f029a2ed48cba808df779ccfcfff616550e4dca87ae691b +size 64173 diff --git a/marked/Rel-16/44_series/44031/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/marked/Rel-16/44_series/44031/1bc1746388cb64bf23b356ce2365dfc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41565a5ad6b06d6ec054611b1ed7df55cf61a913 --- /dev/null +++ b/marked/Rel-16/44_series/44031/1bc1746388cb64bf23b356ce2365dfc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edaf70fe52d475aedaf052d52540fad78ba2ee54ac4e8e736f4fbc15a8d56557 +size 119922 diff --git a/marked/Rel-16/44_series/44031/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/44_series/44031/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c044a802487de904cd1625baf36e935a4ccfaf5c --- /dev/null +++ b/marked/Rel-16/44_series/44031/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d38a1e872a1fc12d917e3516a0aec0af5a670a3158aa72ec335fde9a5a64212e +size 106159 diff --git a/marked/Rel-16/44_series/44031/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg b/marked/Rel-16/44_series/44031/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8acfb9136a6eadac4f62d3c4f1231f862e980f70 --- /dev/null +++ b/marked/Rel-16/44_series/44031/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a793a0c70ea01d26c57948429e863672cb255b1927443d86b32a0445355bc35a +size 120259 diff --git a/marked/Rel-16/44_series/44031/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/44_series/44031/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..321316d0376594e2ed355b32e4a2884cff71e0c9 --- /dev/null +++ b/marked/Rel-16/44_series/44031/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62c075cb9a89f8cd815bb31ca4041c2068677df799baa505e3632c6c30d7d459 +size 53941 diff --git a/marked/Rel-16/44_series/44031/b5987d63203a5fa601921039922ac520_img.jpg b/marked/Rel-16/44_series/44031/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dea65783e380f660b9a3b7bddab82f9652513b39 --- /dev/null +++ b/marked/Rel-16/44_series/44031/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2859dc489391a59e6c58902bbb326a0ddd19c3d62bf8d9ae214dd1598cf07e2a +size 5742 diff --git a/marked/Rel-16/44_series/44031/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/44_series/44031/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b296f0be5b8501985cd487eb9e2d5714ce8f9e --- /dev/null +++ b/marked/Rel-16/44_series/44031/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07cc62909dd3d41ddbfc697e263cb5dfb642dcb16dfab6d4240dbfe762849753 +size 28671 diff --git a/marked/Rel-16/44_series/44031/dae88eec6d1005984029b794ff8b7a9e_img.jpg b/marked/Rel-16/44_series/44031/dae88eec6d1005984029b794ff8b7a9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57ca27c372dd52850d13b6ad37dcb5a314d16413 --- /dev/null +++ b/marked/Rel-16/44_series/44031/dae88eec6d1005984029b794ff8b7a9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:544198ae68a80cd04e0ce1995fa28718ef1a9ec8991b6e4c913b84b01596b216 +size 220028 diff --git a/marked/Rel-16/44_series/44031/f8da9cefc5f8a04f9ffb8f6c49aa03e2_img.jpg b/marked/Rel-16/44_series/44031/f8da9cefc5f8a04f9ffb8f6c49aa03e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8959126d0eea0fcd68efb8cf5fec3273e9c43b14 --- /dev/null +++ b/marked/Rel-16/44_series/44031/f8da9cefc5f8a04f9ffb8f6c49aa03e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:875dab610dea847456a10c06a2ebb7ebc2f7addcc0d0548329028cbf0e243fc9 +size 177332 diff --git a/marked/Rel-16/44_series/44031/raw.md b/marked/Rel-16/44_series/44031/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a0c3ad41f4b9ab67c81bf9e572a37103b0f97fd9 --- /dev/null +++ b/marked/Rel-16/44_series/44031/raw.md @@ -0,0 +1,8927 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------|-----------| +| Foreword..... | 6 | +| 1 Scope..... | 7 | +| 1.1 References..... | 7 | +| 1.2 Abbreviations..... | 8 | +| 2 Functionality of Protocol..... | 8 | +| 2.1 General..... | 8 | +| 2.2 Position Measurement Procedure..... | 9 | +| 2.3 Assistance Data Delivery Procedure..... | 10 | +| 2.3a Positioning Capability Transfer Procedure..... | 11 | +| 2.4 (void)..... | 11 | +| 2.5 Error Handling Procedures..... | 11 | +| 2.5.1 General..... | 11 | +| 2.5.1a Message Too Short..... | 11 | +| 2.5.2 Unknown Reference Number..... | 12 | +| 2.5.3 Missing Information Element or Component Element..... | 12 | +| 2.5.4 Incorrect Data..... | 12 | +| 2.5.5 Repeated Component..... | 12 | +| 2.5.6 (void)..... | 13 | +| 2.5.7 Missing Component..... | 13 | +| 2.5.8 Unforeseen Component..... | 13 | +| 2.5.8a RRLP Procedure..... | 13 | +| 2.5.9 Pseudo-Segmentation..... | 14 | +| 2.6 Multilateration Timing Advance Procedure..... | 14 | +| 3 Message Structure..... | 15 | +| 3.1 General Format of RRLP Message..... | 15 | +| 3.2 Reference Number IE..... | 16 | +| 3.3 Component IE..... | 17 | +| 4 Components..... | 17 | +| 4.1 Measure Position Request..... | 18 | +| 4.2 Measure Position Response..... | 18 | +| 4.3 Assistance Data..... | 19 | +| 4.4 Assistance Data Acknowledgement..... | 19 | +| 4.5 Protocol Error..... | 19 | +| 4.6 Positioning Capability Request..... | 20 | +| 4.7 Positioning Capability Response..... | 20 | +| 4.8 Positioning Multilateration Timing Advance Request..... | 21 | +| 4.9 Multilateration OTD Request..... | 21 | +| 4.10 Multilateration OTD Response..... | 22 | +| 5 Elements of Components..... | 22 | +| 5.1 ASN.1 Description..... | 22 | +| 6 TOM Protocol Header for RRLP Transport..... | 61 | +| 6.1 General..... | 61 | +| 6.2 Remaining Octets of TOM Protocol Header for RRLP..... | 61 | +| Annex A (informative): Description of Components..... | 63 | +| A.1 Introduction..... | 63 | +| A.2 Measure Position Request..... | 63 | +| A.2.1 General..... | 63 | +| A.2.2 Elements..... | 63 | +| A.2.2.1 Positioning Instructions Element..... | 63 | +| A.2.2.1a GANSS Positioning Method Element..... | 65 | +| A.2.2.2 E-OTD Reference BTS for Assistance Data Element..... | 65 | +| A.2.2.3 E-OTD Measurement Assistance Data Element..... | 66 | +| A.2.2.4 E-OTD Measurement Assistance Data for System Information List Element..... | 68 | +| A.2.2.4a GPS Time Assistance Measurement Request element..... | 70 | +| 3GPP | | + +| | | | +|------------|----------------------------------------------------------------------------|-----| +| A.2.2.4b | GPS Reference Time Uncertainty element..... | 71 | +| A.2.2.4c | Velocity Request element..... | 71 | +| A.2.2.4d | GANSS Carrier-Phase Measurement Request Element..... | 71 | +| A.2.2.4e | GANSS TOD - GSM Time Association Request Element..... | 71 | +| A.2.2.4f | Required Response Time..... | 71 | +| A.2.2.4g | GANSS Multi-frequency Measurement Request Element..... | 71 | +| A.2.2.5 | Extended Reference IE..... | 72 | +| A.3 | Measure Position Response..... | 72 | +| A.3.1 | General..... | 72 | +| A.3.2 | Elements..... | 73 | +| A.3.2.1 | Multiple Sets Element..... | 73 | +| A.3.2.2 | Reference BTS Identity Element..... | 73 | +| A.3.2.3 | E-OTD Measurement Information Element..... | 74 | +| A.3.2.3a | E-OTD Measurement Extended Information Element..... | 78 | +| A.3.2.4 | Location Information Element..... | 79 | +| A.3.2.5 | GPS Measurement Information Element..... | 80 | +| A.3.2.6 | Location Information Error Element..... | 84 | +| A.3.2.6a | GPS Time Assistance Measurements Element..... | 85 | +| A.3.2.6b | Velocity Estimate Element..... | 86 | +| A.3.2.7 | Extended Reference IE..... | 86 | +| A.3.2.8 | Uplink RRLP Pseudo Segmentation Indication..... | 86 | +| A.3.2.9 | GANSS Location Information Element..... | 86 | +| A.3.2.10 | GANSS Measurement Information Element..... | 89 | +| A.3.2.10.1 | GANSS Generic Measurement Information Element..... | 92 | +| A.4 | Assistance Data..... | 95 | +| A.4.1 | General..... | 95 | +| A.4.2 | Elements..... | 96 | +| A.4.2.1 | E-OTD Reference BTS for Assistance Data Element..... | 96 | +| A.4.2.2 | E-OTD Measurement Assistance Data Element..... | 96 | +| A.4.2.3 | E-OTD Measurement Assistance Data for System Information List Element..... | 96 | +| A.4.2.4 | GPS Assistance Data Element..... | 96 | +| A.4.2.4a | GPS Time Assistance Measurement Request Element..... | 108 | +| A.4.2.4b | GPS Reference Time Uncertainty Element..... | 108 | +| A.4.2.4c | Additional GPS Assistance Data..... | 108 | +| A.4.2.5 | More Assistance Data To Be Sent Element..... | 118 | +| A.4.2.5 | More Assistance Data To Be Sent Element..... | 118 | +| A.4.2.6 | GANSS Assistance Data..... | 118 | +| A.4.2.6.1 | GANSS Common Assistance Data..... | 119 | +| A.4.2.6.2 | GANSS Generic Assistance Data..... | 122 | +| A.4.2.7 | GANSS Carrier-Phase Measurement Request Element..... | 158 | +| A.4.2.8 | GANSS TOD - GSM Time Association Request Element..... | 159 | +| A.5 | Assistance Data Acknowledgement..... | 159 | +| A.5.1 | General..... | 159 | +| A.6 | Protocol Error..... | 159 | +| A.6.1 | General..... | 159 | +| A.6.2 | Extended Reference IE..... | 159 | +| A.7 | Positioning Capability Request..... | 159 | +| A.7.1 | General..... | 159 | +| A.8 | Positioning Capability Response..... | 160 | +| A.8.1 | General..... | 160 | +| A.8.2 | Elements..... | 160 | +| A.8.2.1 | Positioning Capabilities..... | 160 | +| A.8.2.2 | Assistance Data Supported..... | 162 | +| A.8.2.3 | Assistance Data Needed..... | 164 | +| A.9 | Multilateration Timing Advance Request..... | 165 | +| A.9.1 | General..... | 165 | +| A.9.2 | Elements..... | 165 | +| A.9.2.1 | Target-Number-of-Cells Element..... | 165 | +| A.9.2.2 | Requested-MS-Synchronization-Accuracy Element..... | 165 | +| A.9.2.3 | MTA-Method..... | 165 | +| A.9.2.4 | Random-ID..... | 166 | +| 3GPP | | | + +| | | | +|------------------------|-----------------------------------------------------|-----| +| A.9.2.5 | MPM-Timer..... | 166 | +| A.9.2.6 | Serving-Cell..... | 166 | +| A.9.2.7 | Co-Sited-Cells..... | 166 | +| A.9.2.8 | Cell-Set N..... | 166 | +| A.9.2.9 | MTA-Security..... | 169 | +| A.10 | Multilateration OTD Request..... | 169 | +| A.10.1 | General..... | 169 | +| A.10.2 | Elements..... | 169 | +| A.10.2.1 | Target Number of OTD Measurements..... | 169 | +| A.10.2.2 | Required DL Synchronisation Accuracy..... | 169 | +| A.10.2.3 | Serving Cell Set..... | 170 | +| A.10.2.4 | Neighbour Cell Sets..... | 170 | +| A.11 | Multilateration OTD Response..... | 170 | +| A.11.1 | General..... | 170 | +| A.11.2 | Elements..... | 170 | +| A.11.2.1 | Serving Cell Downlink Synchronisation Accuracy..... | 170 | +| A.11.2.2 | MOTD Measurement Results..... | 170 | +| A.11.2.3 | MOTD Receive Level Measurements..... | 171 | +| Annex B (informative): | Change History..... | 173 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document contains the definition of the Radio Resource LCS Protocol (RRLP) to be used between the Mobile Station (MS) and the Serving Mobile Location Centre (SMLC). + +Clause 2 defines the functionality of the protocol. Clause 3 describes the message structure, and Clause 4 the structure of components. Clause 5 contains the ASN.1 description of the components. + +## 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services in GERAN". +- [3] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [4] ITU-T Recommendation X.691: "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [5] ITU-T Recommendation X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [7] 3GPP TS 49.031: "Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". +- [8] ICD-GPS-200, Navstar GPS Space Segment/Navigation User Interfaces. +- [9] RTCM-SC104, RTCM Recommended Standards for Differential GNSS Service (v.2.2). +- [10] 3GPP TS 44.064: "General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) layer specification". +- [11] Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.42, ~~September~~ February 2010~~4~~, European Union. +- [12] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006. +- [13] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005. +- [14] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, March 31, 2008. +- [15] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. +- [16] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, June 17, 2008. +- [17] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002. + +[18] BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 2.0)", December 2013. + +## 1.2 Abbreviations + +For the purposes of the present document, the following abbreviations and the abbreviations given in 3GPP TR 21.905 or in 3GPP TS 43.059 apply. + +| | | +|---------|----------------------------------------------------------------------------------------------| +| ADR | Accumulated Delta-Range | +| BDS | BeiDou Navigation Satellite System | +| CNAV | Civil Navigation | +| ECEF | Earth-Centered, Earth-Fixed | +| ECI | Earth-Centered-Inertial | +| EGNOS | European Geostationary Navigation Overlay Service | +| FEC | Forward Error Correction | +| GAGAN | GPS Aided Geo Augmented Navigation | +| ICD | Interface Control Document | +| GANSS | Galileo and Additional Navigation Satellite Systems | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GNSS | Global Navigation Satellite System | +| IOD | Issue of Data | +| LSB | Least Significant Bit | +| MSAS | Multi-functional Satellite Augmentation System | +| MSB | Most Significant Bit | +| msd | mean solar day | +| NAV | Navigation | +| NICT | National Institute of Information and Communications Technology | +| NTSC | National Time Service Center | +| PZ-90 | Parametry Zemli 1990 Goda – Parameters of the Earth Year 1990 | +| QZSS | Quasi-Zenith Satellite System | +| SBAS | Space Based Augmentation System | +| SV | Space Vehicle | +| USNO | US Naval Observatory | +| WAAS | Wide Area Augmentation System | +| WGS-84 | World Geodetic System 1984 | + +# --- 2 Functionality of Protocol + +## 2.1 General + +The present document defines one generic RRLP message that is used to transfer Location Services (LCS) related information between the Mobile Station (MS) and the Serving Mobile Location Centre (SMLC). Usage of the RRLP protocol on a general level is described in 3GPP TS 43.059 that includes Stage 2 description of LCS. + +One message includes one of the following components: + +- Measure Position Request; +- Measure Position Response; +- Assistance Data; +- Assistance Data Acknowledgement; +- Protocol Error; +- Positioning Capability Request; +- Positioning Capability Response; +- Multilateration Timing Advance Request. + +Next sub-clauses describe the usage of these components. + +Delivery of components may be supported in the RRLP level using pseudo-segmentation by sending several shorter messages instead of one long message. Any assistance data that is successfully delivered to an MS and acknowledged prior to the interruption of the positioning procedure by an event like handover, or by any other event that causes an MS to terminate the positioning procedure or delivery of assistance data (see 3GPP TS 43.059), shall be retained by the MS and need not be resent by the SMLC when positioning or delivery of assistance data is again re-attempted. + +The RRLP maximum PDU size is 242 octets. If the amount of data that needs to be sent is larger than RRLP maximum PDU size, the RRLP pseudo-segmentation shall be used. The RRLP pseudo-segmentation is the use of several RRLP components (one in each RRLP message) to deliver a large amount of information. For SMLC to MS messages, the Assistance Data component is the one that is sent several times in order to deliver the information. For MS to SMLC messages, the Measure Position Response component may be sent twice in order to deliver the information. Legacy MS and SMLC (3GPP Rel-4 or older) may send RRLP components that are larger than the RRLP maximum PDU size. In this case lower level segmentation will be used. + +## 2.2 Position Measurement Procedure + +The purpose of this procedure is to enable the SMLC to request for position measurement data or location estimate from the MS, and the MS to respond to the request with measurements or location estimate. + +![Sequence diagram of the Position Measurement procedure between SMLC and MS.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +``` + +sequenceDiagram + participant SMLC + participant MS + Note right of SMLC: 1. Positioning Capability Transfer Procedure + Note right of SMLC: 2. Assistance Data Delivery Procedure + SMLC->>MS: 3. RRLP(Measure Position Request) + Note left of MS: 4. RRLP(Protocol Error) + Note left of MS: 5. RRLP(Measure Position Response) + Note left of MS: 5. RRLP(Measure Position Response) + +``` + +The diagram illustrates the interaction between the SMLC and the MS. The SMLC initiates the procedure with two optional steps (1 and 2) shown in dashed boxes. Step 3 is a solid arrow from SMLC to MS labeled 'RRLP(Measure Position Request)'. Step 4 is a dashed arrow from MS to SMLC labeled 'RRLP(Protocol Error)'. Step 5 consists of two dashed arrows from MS to SMLC, both labeled 'RRLP(Measure Position Response)'. + +Sequence diagram of the Position Measurement procedure between SMLC and MS. + +**Figure 2.1: Position Measurement procedure** + +1. The Measure Position Request component and any Assistance Data Delivery Procedure may be preceded by a Positioning Capability Transfer procedure (see sub-clause 2.3a) to transfer the MS positioning capabilities to the SMLC. +2. The Measure Position Request component may be preceded by an Assistance Data Delivery Procedure (see sub-clause 2.3) to deliver some or all of the entire set of assistance data that is needed by the subsequent positioning procedure (steps 3-5). +3. The SMLC sends the Measure Position Request component in a RRLP message to the MS. The component includes QoS, other instructions, and possible assistance data to the MS. The RRLP message contains a reference number and an extended reference ID of the request. +4. The MS sends a RRLP message containing the Protocol Error component to the SMLC, if there is a problem that prevents the MS to receive a complete and understandable Measure Position Request component. The RRLP message contains the reference number and, if available, the extended reference ID included in the Measure Position Request received incomplete. The Protocol Error component includes a more specific reason. When the SMLC receives the Protocol Error component, it may try to resend the Measure Position Request (go back to the step 3), abort location, or start a new position measurement procedure (e.g. with updated assistance data). +5. The MS tries to perform the requested location measurements, and possibly calculates its own position. When the MS has location measurements, location estimate, or an error indication (measurements/location estimation not possible), it sends the results in the Measure Position Response component to the SMLC. The RRLP message + +contains the reference number and, if received, the extended reference ID of the request originally received in the step 3. The MS may optionally send one additional Measure Position Response component in a second RRLP message to the SMLC if the amount of information it needs to transfer to the SMLC is too large to fit into one single Measure Position Response component (uplink RRLP pseudo-segmentation). This RRLP message also contains the reference number and, if received, the extended reference ID of the request originally received in the step 3. If two components are sent, the MS shall indicate in the first component that it is the first of many components and in the second one that it is the second of many components. If there is a problem that prevents the SMLC to receive a complete and understandable Measure Position Response component, the SMLC may decide to abort location, or start a new position measurement procedure instead. If additional Measure Position Response components are received by the SMLC after the 1st and optional 2nd one, they shall be ignored. + +## 2.3 Assistance Data Delivery Procedure + +The purpose of this procedure is to enable the SMLC to send assistance data to the MS related to position measurement and/or location calculation. Notice that RRLP protocol is not used by the MS to request assistance data, only to deliver it to the MS. The entire set of assistance data (i.e. the total amount of assistance data that the SMLC has decided to send in the current procedure) may be delivered in one or several Assistance Data components. In this case steps 1 and 3 below may be repeated several times by the SMLC. If several components are sent, the SMLC shall await the acknowledgement of each component before the next Assistance Data component is sent. If Assistance Data Delivery is used as part of the Position Measurement Procedure, as described in sub-clause 2.2, then some assistance data may be delivered in the final RRLP Measure Position Request. + +![Sequence diagram of the Assistance Data Delivery procedure between SMLC and MS.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +``` + +sequenceDiagram + participant SMLC + participant MS + SMLC->>MS: 1. RRLP(Assistance Data) + MS-->>SMLC: 2. RRLP(Protocol Error) + MS->>SMLC: 3. RRLP(Assistance Data Ack.) + +``` + +Sequence diagram of the Assistance Data Delivery procedure between SMLC and MS. + +**Figure 2.2: Assistance Data Delivery procedure** + +1. The SMLC sends the Assistance Data component to the MS. The component includes assistance data for location measurement and/or location calculation. The RRLP message contains a reference number and an extended reference ID of the delivery. The More Assistance Data To Be Sent Element in the Assistance Data component is used by the SMLC to indicate to the MS if either more Assistance Data components (in the current Assistance Data Delivery procedure) or a final RRLP Measure Position Request (if the Assistance Data Delivery Procedure forms part of a Position Measurement procedure as described in sub-clause 2.2) will be sent. +2. The MS sends a RRLP message containing the Protocol Error component to the SMLC, if there is a problem that prevents the MS to receive a complete and understandable Assistance Data component. The RRLP message contains the reference number and, if available, the extended reference ID included in the Assistance Data component received incomplete. The Protocol Error component includes a more specific reason. When the SMLC receives the Protocol Error component, it may try to resend the Assistance Data component (go back to the step 1), send a new measure Assistance Data set (e.g. with updated assistance data), or abort the delivery. +3. When the MS has received a complete Assistance Data component, it send the Assistance Data Acknowledgement component to the SMLC. The RRLP message contains the reference number of the Assistance Data originally received in step 1. + +## 2.3a Positioning Capability Transfer Procedure + +The purpose of this procedure is to enable the SMLC to obtain the positioning capabilities of the MS, the types of assistance supported and the types of assistance data that may be needed from the SMLC. MS support for this procedure can be indicated to the SMLC using the MS Classmark 3 IE for GSM (see 3GPP TS 24.008), the PS LCS Capability IE + +for GERAN Gb mode (see 3GPP TS 24.008) and the MS Positioning Capability IE for GERAN Iu mode (see 3GPP TS 44.118). + +![Sequence diagram illustrating the Positioning Capability Transfer procedure between SMLC and MS. Step 1: SMLC sends RRLP (Positioning Capability Request) to MS. Step 2: MS sends RRLP (Protocol Error) back to SMLC (dashed line). Step 3: MS sends RRLP (Positioning Capability Response) to SMLC.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant SMLC + participant MS + Note right of SMLC: 1. RRLP (Positioning Capability Request) + SMLC->>MS: 1. RRLP (Positioning Capability Request) + Note left of MS: 2. RRLP (Protocol Error) + MS-->>SMLC: 2. RRLP (Protocol Error) + Note right of MS: 3. RRLP (Positioning Capability Response) + MS->>SMLC: 3. RRLP (Positioning Capability Response) + +``` + +Sequence diagram illustrating the Positioning Capability Transfer procedure between SMLC and MS. Step 1: SMLC sends RRLP (Positioning Capability Request) to MS. Step 2: MS sends RRLP (Protocol Error) back to SMLC (dashed line). Step 3: MS sends RRLP (Positioning Capability Response) to SMLC. + +**Figure 2.3: Positioning Capability Transfer procedure** + +1. The SMLC sends the Positioning Capability Request component to the MS. The RRLP message contains a reference number and an extended reference ID of the request. The message may contain indication of GANSS positioning support. +2. The MS sends a RRLP message containing the Protocol Error component to the SMLC, if there is a problem that prevents the MS to receive a complete and understandable Positioning Capability Request component. The RRLP message contains the reference number and the extended reference ID included in the Positioning Capability Request component. The Protocol Error component includes a more specific reason. When the SMLC receives the Protocol Error component, it may try to resend the Positioning Capability Request component (go back to the step 1) or abort the request. +3. When the MS has received a complete Positioning Capability Request component, it sends the Positioning Capability Response component to the SMLC. The component shall include the positioning capabilities of the MS and the types of supported assistance data. The component may include the types of assistance needed by the MS to obtain a location estimate or positioning measurements. The RRLP message also contains the reference number and extended Reference ID of the Positioning Capability Request originally received in step 1. + +## 2.4 (void) + +## 2.5 Error Handling Procedures + +### 2.5.1 General + +In this sub-clause it is described how a receiving entity behaves in cases when it receives erroneous data or detects that certain data is missing. + +### 2.5.1a Message Too Short + +When MS receives a RRLP message, that is too short to contain all mandatory IEs, the MS sends a Protocol Error component with indication "Message Too Short". If the Reference Number can be found, it is included. If the Reference Number is not available, the Reference Number of the RRLP message carrying the Protocol Error component is set to '0'. If the Extended Reference IE can be found, it shall be included in the returned Protocol Error Component. If the Extended Reference IE is not available, an Extended Reference IE shall not be included. The original sending entity that receives the Protocol Error, may then resend the original message, or abort the procedure. + +### 2.5.2 Unknown Reference Number + +A SMLC detects that it has received a RRLP message with an unknown or invalid Reference Number, when one or more of the following conditions occur: + +- a Measure Position Response, Assistance Data Acknowledgement, Positioning Capability Response or Protocol Error component is received with a Reference Number that the SMLC has not sent in a Measure Position + +Request, Assistance Data or Positioning Capability Request component during a pending Position Measurement, Assistance Data Delivery or Positioning Capability Transfer procedure. + +- a Measure Position Response, Positioning Capability Response or Protocol Error component is received with an Extended Reference IE value that the SMLC has not sent in a Measure Position Request Assistance Data or Positioning Capability Request component during a pending Position Measurement, Assistance Data Delivery or Positioning Capability Transfer procedure. +- a Measure Position Response, Positioning Capability Response or Protocol Error component is received with a Reference Number and an Extended Reference IE value that the SMLC has not sent together in the same Measure Position Request, the same Assistance Data or the same Positioning Capability Request component during a pending Position Measurement, Assistance Data Delivery or Positioning Capability Transfer procedure. + +The SMLC shall then discard the message. If the SMLC receives a Measure Position Response or a Protocol Error component containing no Extended Reference ID, then the SMLC shall assume that the target MS is for Release 4 or earlier and shall only verify the received Reference Number. + +### 2.5.3 Missing Information Element or Component Element + +When MS receives a RRLP message, that does not contain IEs or component elements expected to be present, the MS sends a Protocol Error component with indication "Missing Information Element or Component Element". If the Reference Number can be found, it is included. If the Reference Number is not available, the Reference Number of the RRLP message carrying the Protocol Error component is set to '0'. If the Extended Reference IE can be found, it shall be included in the returned Protocol Error Component. If the Extended Reference IE is not available, an Extended Reference IE shall not be included. The SMLC that receives the Protocol Error, may then resend the original message, or abort the procedure. + +### 2.5.4 Incorrect Data + +When MS receives a RRLP message, that contains IEs or elements of components that are syntactically incorrect, the MS sends a Protocol Error component with indication "Incorrect Data". If the Reference Number can be found, it is included. If the Reference Number is not available, the Reference Number of the RRLP message carrying the Protocol Error component is set to '0'. If the Extended Reference IE can be found, it shall be included in the returned Protocol Error Component. If the Extended Reference IE is not available, an Extended Reference IE shall not be included. The SMLC that receives the Protocol Error, may then resend the original message, or abort the procedure. + +### 2.5.5 Repeated Component + +When after the reception of a Measure Position Request component, but before responding with a Measure Position Response or a Protocol Error component, the MS receives a new RRLP message with the Measure Position Request component, it acts as follows: + +- if the old and new Measure Position Request components have the same Reference Number and, if included, the same Extended Reference IE, the MS ignores the later component; +- if the old and new Measure Position Request components have different Reference Numbers or, if included, different Extended Reference IEs or if one Measure Position Request component (old or new) contains an Extended Reference IE but the other component does not, the MS aborts activity for the former component, and starts to act according to the later component, and sends a response to that. + +When after the reception of an Assistance Data component, but before responding with an Assistance Data Acknowledgement or a Protocol Error component, the MS receives a new RRLP message with the Assistance Data component, it acts as follows: + +- if the old and new Assistance Data components have the same Reference Number and, if included, the same Extended Reference IE and if pseudo-segmentation does not apply (see sub-clause 2.5.9), the MS ignores the later component; +- if the old and new Assistance Data components have different Reference Numbers or, if included, different Extended Reference IEs or if one Assistance Data component (old or new) contains an Extended Reference IE but the other component does not, the MS ignores the former component and sends an acknowledgement to the latter component. + +When after the reception of a Positioning Capability Request component, but before responding with a Positioning Capability Response or a Protocol Error component, the MS receives a new RRLP message with the Positioning Capability Request component, it acts as follows: + +- if the old and new Positioning Capability Request components have the same Reference Number and the same Extended Reference IE, the MS ignores the later component; +- if the old and new Positioning Capability Request components have different Reference Numbers or different Extended Reference IEs, the MS aborts activity for the former component, starts to act according to the later component and sends a response to that. + +When after the reception of an Measure Position Response component, the SMLC receives a new RRLP message with the Measure Position Response component, it acts as follows: + +- if the old and new Measure Position Response components have the same Reference Number and, if included, the same Extended Reference IE values, the SMLC may ignore the later component; + +### 2.5.6 (void) + +### 2.5.7 Missing Component + +When the SMLC sends a Measure Position Request component to the MS, it starts a timer. If the timer expires before the SMLC receives the last Measure Position Response component or a Protocol Error component from the MS with the same Reference Number and, if included, the same Extended Reference IE value as in the sent component, it may abort location attempt or send a new Measure Position Request. + +When the SMLC receives a Measure Position Response component with the same Reference Number and, if included, the same Extended Reference IE value as in the sent component indicating that it is the second of many segments, but the first of the many segments was never received by the SMLC, it may abort location attempt or send a new Measure Position Request. + +When the SMLC sends a Assistance Data component to the MS, it starts a timer. If the timer expires before the SMLC receives a Assistance Data Acknowledgement or Protocol Error component from the MS with the same Reference Number as in the sent component and, in the case of a Protocol Error component, either the same extended reference ID as in the sent component or no extended reference ID, it may abort delivery attempt or send a new Assistance Data. + +When the SMLC sends a Positioning Capability Request component to the MS, it starts a timer. If the timer expires before the SMLC receives a Positioning Capability Response or Protocol Error component from the MS with the same Reference Number and the same Extended Reference ID as in the sent component, it may abort the Positioning Capability Transfer Procedure attempt or send a new Positioning Capability Request. + +### 2.5.8 Unforeseen Component + +When the MS receives a complete Assistance Data pseudo-segmentation sequence or an Assistance Data component that was sent without pseudo-segmentation, that it is not expecting, MS may discard it. + +### 2.5.8a RRLP Procedure + +The MS and SMLC shall only support one RRLP procedure at a time for either positioning, delivery of assistance data or positioning capability transfer. The normal sequence of events for either procedure is defined in sub-clause 2.2, sub-clause 2.3 or sub-clause 2.3a, respectively. If the MS is engaged in an RRLP procedure and receives a correctly encoded RRLP message from the SMLC that starts a new procedure, the MS shall abort the first procedure without sending a response and start the second. + +### 2.5.9 Pseudo-Segmentation + +When the SMLC employs pseudo-segmentation to send an RRLP Measure Position Request message or an RRLP Assistance Data message, the SMLC shall send one or more RRLP Assistance Data components followed by: + +- a final RRLP Measure Position Request component (see sub-clause 2.2) or +- a final RRLP Assistance Data component (see sub-clause 2.3). + +The SMLC shall indicate in all but the final component (Measure Position Request or Assistance Data, respectively) that more components are on the way. + +When an MS receives an Assistance Data component indicating that more components are on the way, the MS may store the contents of the component. If the MS receives a subsequent Assistance Data component or a final Measure Position Request component that is correctly encoded, the MS shall assume that the new component continues the pseudo-segmentation of the earlier component and may then store the contents of the new component. If the new component is an Assistance Data component indicating that no more components are on the way or if it is a Measure Position Request, the MS shall assume that pseudo-segmentation is complete. The MS may then employ the rules defined in sub-clause 2.5.5 to verify if the new message is a repeated duplicate of a previous message. + +## 2.6 Multilateration Timing Advance Procedure + +The purpose of this procedure is to enable the SMLC to request an MS to perform the Multilateration Timing Advance procedure in multiple cells autonomously selected by the MS. The BSS(s) corresponding to the selected cells acquire and send timing advance related measurements to the SMLC which uses the received measurements to perform a location estimate for the MS. + +![Sequence diagram of the Multilateration Timing Advance procedure. The diagram shows three lifelines: SMLC, BSS, and MS. Step 1: A dashed box labeled '1. RRLP Multilateration Timing Advance Request' shows a message from SMLC to MS. Step 2: A series of messages from MS to BSS labeled '2a. MTA procedure in cell 1', '2b. MTA procedure in cell 2', '...', '2n. MTA procedure in cell N'. Step 3: A series of messages from BSS to SMLC labeled 'MTA information for cell 1', 'MTA Information for cell 2', '...', 'MTA Information for cell N'. Step 4: A dashed box labeled '3. SMLC Estimates MS position' is shown at the SMLC lifeline.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` +sequenceDiagram + participant SMLC + participant BSS + participant MS + Note left of SMLC: 1. RRLP Multilateration Timing Advance Request + SMLC->>MS: RRLP Multilateration Timing Advance Request + Note right of MS: 2a. MTA procedure in cell 1 + MS->>BSS: MTA procedure in cell 1 + Note right of BSS: MTA information for cell 1 + BSS->>SMLC: MTA information for cell 1 + Note right of MS: 2b. MTA procedure in cell 2 + MS->>BSS: MTA procedure in cell 2 + Note right of BSS: MTA Information for cell 2 + BSS->>SMLC: MTA Information for cell 2 + Note right of BSS: ... + Note right of MS: 2n. MTA procedure in cell N + MS->>BSS: MTA procedure in cell N + Note right of BSS: MTA Information for cell N + BSS->>SMLC: MTA Information for cell N + Note left of SMLC: 3. SMLC Estimates MS position +``` + +Sequence diagram of the Multilateration Timing Advance procedure. The diagram shows three lifelines: SMLC, BSS, and MS. Step 1: A dashed box labeled '1. RRLP Multilateration Timing Advance Request' shows a message from SMLC to MS. Step 2: A series of messages from MS to BSS labeled '2a. MTA procedure in cell 1', '2b. MTA procedure in cell 2', '...', '2n. MTA procedure in cell N'. Step 3: A series of messages from BSS to SMLC labeled 'MTA information for cell 1', 'MTA Information for cell 2', '...', 'MTA Information for cell N'. Step 4: A dashed box labeled '3. SMLC Estimates MS position' is shown at the SMLC lifeline. + +**Figure 2.6: Multilateration Timing Advance procedure** + +1. The RRLP Multilateration Timing Advance Request component is sent to the MS (see step 1 in Figure 2.6). The RRLP message contains assistance information acquired from the serving BSS which can be used by the MS to perform the Multilateration Timing Advance procedure. +2. The MS performs the Multilateration Timing Advance procedure in multiple cells that it selects autonomously which may include one or more cells for which it has received assistance information in the RRLP message (see steps 2a, 2b ... 2n). After the MS performs the radio access part of the MTA procedure in a given cell the corresponding BSS sends the cell specific Multilateration timing advance information to the SMLC. +3. The SMLC uses the collected timing advance information to estimate a “position” for the MS (see step 3). + +# 3 Message Structure + +## 3.1 General Format of RRLP Message + +The general format of the RRLP message is given below, and based on: + +- ITU-T Recommendation X.680; +- ITU-T Recommendation X.691; + +and is consistent with these ITU-T recommendations. Also further definitions in the present document are based on ASN.1/94 defined in ITU-T Recommendation X.680 (ASN.1 1994). BASIC-PER, unaligned variant is used. Both RRLP ASN.1 modules, RRLP-Messages and RRLP-Components, are based on recommendations presented above. + +ASN.1 identifiers have the same name as the corresponding parameters (information elements of the RRLP message, components, elements of components, fields of component elements etc) in other parts of the present document, except for the differences required by the ASN.1 notation (blanks between words are removed, the first letter of the first word is lower-case and the first letter of the following words are capitalized, e.g. "Reference Number" is mapped to "referenceNumber"). In addition some words may be abbreviated as follows: + +| | | +|-----|-----------------| +| msr | measure | +| req | request | +| rsp | response | +| nbr | number | +| ack | acknowledgement | + +Ellipsis Notation shall be used in the same way as described in 3GPP TS 29.002 and shall be supported on the radio interface by the MS and the network for all operations defined in the present document. + +**Table 3.1.a: RRLP Message Format** + +``` + +RRLP-Messages +-- { RRLP-messages } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + MsrPosition-Req, MsrPosition-Rsp, AssistanceData, + ProtocolError, PosCapability-Req, PosCapability-Rsp, + MultilaterationOTD-Req, MultilaterationOTD-Rsp, + PosMTA-Req +FROM + RRLP-Components -- { RRLP-Components } +; + +PDU ::= SEQUENCE { + referenceNumber INTEGER (0..7), + component RRLP-Component +} + +RRLP-Component ::= CHOICE { + msrPositionReq MsrPosition-Req, + msrPositionRsp MsrPosition-Rsp, + assistanceData AssistanceData, + assistanceDataAck NULL, + protocolError ProtocolError, + ... + posCapabilityReq PosCapability-Req, + posCapabilityRsp PosCapability-Rsp, + multilaterationOTDReq MultilaterationOTD-Req, + multilaterationOTDRsp MultilaterationOTD-Rsp, + posMTAReq PosMTA-Req +} + +END + +``` + +The message consists of two information elements, that are further described in the following sub-clauses. + +## 3.2 Reference Number IE + +This element is mandatory, and appears only once per RRLP message. It has the range from 0 to 7. Value 0 is reserved for indicating unknown Reference Number. Its ASN.1 definition is in sub-clause 3.1. This element contains the Reference Number that shall be used as follows: + +- in the Position Measurement procedure the SMLC shall select any number within the range 1 - 7 that it is not already using with the particular MS. The Reference Number serves as an identification of the Measure Position request component that it sends to the MS. When the MS responds either with the Measure Position Response component, or the Protocol Error component, it shall use the same Reference Number value and, if an Extended Reference ID was included by the SMLC, the same Extended Reference ID to identify to which Measure Position Request it is responding, if the Reference Number has been obtained. If the MS has not been able to decode the Reference Number (e.g. IE missing), it shall use '0' as the Reference number in the response. This mechanism helps for example in the cases where the SMLC sends a Measure Position Request to the MS, and before it receives the Response, it needs to send another Request (e.g. assistance data changes). Then the SMLC can identify to which Request the Response is related to; +- in the Assistance Data Delivery procedure the SMLC shall select any number within the range 1 - 7 that it is not already using with the MS. The Reference Number serves as an identification of the Assistance Data component that it sends to the MS. When the MS responds either with the Assistance Data Acknowledgement component or the Protocol Error component, it shall use the same Reference Number value if the Reference Number has been obtained and, in the case of Protocol Error, if an Extended Reference ID was included by the SMLC, the same Extended Reference ID to identify to which Assistance Data component it is responding. If the MS has not been able to decode the Reference Number (e.g. IE missing), it shall use '0' as the Reference number in the response. +- in the Position Capability Transfer procedure the SMLC shall select any number within the range 1 - 7 that it is not already using with the MS. The Reference Number serves as an identification of the Positioning Capability + +Request component that it sends to the MS. When the MS responds either with the Positioning Capability Response component, or the Protocol Error component, it shall use the same Reference Number value if the Reference Number has been obtained and the same Extended Reference ID value if that has been obtained to identify to which Positioning Capability Request component it is responding. If the MS has not been able to decode the Reference Number (e.g. IE missing), it shall use '0' as the Reference number in the response. + +- the SMLC shall use the same Reference Number and same Extended Reference ID to resend any RRLP component for which a response was not received from the MS. +- the SMLC shall use a different Reference Number to that in any RRLP component for which a response was not received from the MS if the SMLC aborts an existing RRLP procedure and starts a new procedure. +- the SMLC may use the same Reference Number and same Extended Reference ID or different Reference Numbers and Extended Reference IDs for different RRLP components within the same pseudo-segmentation sequence. + +In all RRLP messages except Assistance Data Acknowledgement, the Reference Number IE shall be supplemented by an Extended Reference IE in order to distinguish valid from invalid RRLP responses at the SMLC and duplicate from non-duplicate RRLP commands at the MS. In order to remain backward compatible, the receiving entity shall be able to receive Measure Position Request, Measure Position Response, Assistance Data and Protocol Error messages without the Extended Reference IE. The ASN.1 definition of the Extended Reference IE is given in sub-clause 5.1 and the procedures associated with sending and receiving it are given in clause 2 and in Annex A, sub-clauses A.2.2.5, A.3.2.7 and A.6.6. + +## 3.3 Component IE + +This element is mandatory, and appears only once per RRLP message. It contains the actual component to be transferred. + +Different components are described further in Chapter 4. This IE contains only one component, i.e. it is not possible to include two or more components. + +# 4 Components + +This ASN.1 module contains the definitions of the components and datatypes defined in the components. + +**Table 4.a: RRLP-Components format** + +``` + +RRLP-Components +-- { RRLP-Components } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + Ext-GeographicalInformation, VelocityEstimate +FROM + MAP-LCS-DataTypes { + itu-t identified-organization (4) etsi (0) mobileDomain (0) + gsm-Network (1) modules (3) map-LCS-DataTypes (25) version10 (10)} + + ExtensionContainer +FROM MAP-ExtensionDataTypes { + itu-t identified-organization (4) etsi (0) mobileDomain (0) + gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} +; + +-- Add here other ASN.1 definitions presented below +-- in chapters 4 and 5. + +END + +``` + +## 4.1 Measure Position Request + +This component is used by the SMLC to request location measurements or a location estimate from the MS. It includes QoS, other instructions, and possible assistance data to the MS. This component is defined as follows: + +**Table 4.1.a: Measure Position Request** + +``` +-- add this definition to RRLP-Components module + +-- Measurement Position request component +MsrPosition-Req ::= SEQUENCE { + positionInstruct PositionInstruct, + referenceAssistData ReferenceAssistData OPTIONAL, + msrAssistData MsrAssistData OPTIONAL, + systemInfoAssistData SystemInfoAssistData OPTIONAL, + gps-AssistData GPS-AssistData OPTIONAL, + extensionContainer ExtensionContainer OPTIONAL, + .... + -- Release 98 extension element + rel98-MsrPosition-Req-extension Rel98-MsrPosition-Req-Extension OPTIONAL, + -- Release 5 extension element + rel5-MsrPosition-Req-extension Rel5-MsrPosition-Req-Extension OPTIONAL, + -- Release 7 extension element + rel7-MsrPosition-Req-extension Rel7-MsrPosition-Req-Extension OPTIONAL +} +``` + +The elements of this component are defined in clause 5. + +## 4.2 Measure Position Response + +This component is used by the MS to respond to a Measure Position Request from the SMLC with location measurements, a location estimate, or an error indication. This component is defined as follows: + +**Table 4.2.a: Measure Position Response** + +``` +-- add this definition to RRLP-Components module + +-- Measurement Position response component +MsrPosition-Rsp ::= SEQUENCE { + multipleSets MultipleSets OPTIONAL, + referenceIdentity ReferenceIdentity OPTIONAL, + otd-MeasureInfo OTD-MeasureInfo OPTIONAL, + locationInfo LocationInfo OPTIONAL, + gps-MeasureInfo GPS-MeasureInfo OPTIONAL, + locationError LocationError OPTIONAL, + extensionContainer ExtensionContainer OPTIONAL, + .... + -- Release extension here + rel-98-MsrPosition-Rsp-Extension + Rel-98-MsrPosition-Rsp-Extension OPTIONAL, + rel-5-MsrPosition-Rsp-Extension + Rel-5-MsrPosition-Rsp-Extension OPTIONAL, + -- When RRLP pseudo-segmentation is used, rel-5-MsrPosition-Rsp-Extension + -- and other possible future extensions should be the ones included in + -- the 2nd MsrPosition-Rsp component. + rel-7-MsrPosition-Rsp-Extension + Rel-7-MsrPosition-Rsp-Extension OPTIONAL +} +``` + +The elements of this component are defined in clause 5. + +## 4.3 Assistance Data + +This component is used by the SMLC to deliver assistance data for location measurement and/or location calculation. This component is defined as follows: + +**Table 4.3.a: Assistance Data** + +``` + +-- add this definition to RRLP-Components module + +-- Assistance Data component +AssistanceData ::= SEQUENCE { + referenceAssistData ReferenceAssistData OPTIONAL, + msrAssistData MsrAssistData OPTIONAL, + systemInfoAssistData SystemInfoAssistData OPTIONAL, + gps-AssistData GPS-AssistData OPTIONAL, + moreAssDataToBeSent MoreAssDataToBeSent OPTIONAL, + -- If not present, interpret as only + -- Assistance Data component used to + -- deliver entire set of assistance + -- data. + + extensionContainer ExtensionContainer OPTIONAL, + ... + -- Release extension here + rel98-AssistanceData-Extension Rel98-AssistanceData-Extension OPTIONAL, + rel5-AssistanceData-Extension Rel5-AssistanceData-Extension OPTIONAL, + rel7-AssistanceData-Extension Rel7-AssistanceData-Extension OPTIONAL +} + +``` + +The elements of this component are defined in clause 5. + +## 4.4 Assistance Data Acknowledgement + +This component does not have any information contents. Its presence indicates that the MS has received the complete Assistance Data component. + +## 4.5 Protocol Error + +This component is used by the receiving entity (SMLC or MS) to indicate to the sending entity, that there is a problem that prevents the receiving entity to receive a complete and understandable component. This component is defined as follows: + +**Table 4.5.a: Protocol Error** + +``` + +-- add this definition to RRLP-Components module + +-- Protocol Error component +ProtocolError ::= SEQUENCE { + errorCause ErrorCodes, + extensionContainer ExtensionContainer OPTIONAL, + ... + -- Release extensions here + rel-5-ProtocolError-Extension Rel-5-ProtocolError-Extension OPTIONAL +} + +``` + +The elements of this component are defined in clause 5. + +## 4.6 Positioning Capability Request + +This component is used by the SMLC to request the positioning capabilities of the MS and optionally indicating GANSS positioning support. This component is defined as follows: + +**Table 4.6.a: Positioning Capability Request** + +``` + +-- add this definition to RRLP-Components module + +-- Positioning Capability request component +PosCapability-Req ::= SEQUENCE { + extended-reference Extended-reference, + gANSSPositionMethods GANSSPositionMethods OPTIONAL, + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +``` + +The elements of this component are defined in clause 5. + +## 4.7 Positioning Capability Response + +This component is used by the MS to respond to a Positioning Capability Request from the SMLC with the positioning capabilities of the MS, the types of assistance data supported and the types of assistance data possibly needed by the MS. This component is defined as follows: + +**Table 4.7.a: Positioning Capability Response** + +``` +-- add this definition to RRLP-Components module + +-- Positioning Capability response component +PosCapability-Rsp ::= SEQUENCE { + extended-reference Extended-reference, + posCapabilities PosCapabilities, + + -- assistanceSupported shall be included if and only if any of the assistance data is supported + assistanceSupported AssistanceSupported OPTIONAL, + assistanceNeeded AssistanceNeeded OPTIONAL, + extensionContainer ExtensionContainer OPTIONAL, + ... +} +``` + +The elements of this component are defined in clause 5. + +## 4.8 Positioning Multilateration Timing Advance Request + +This component is used by the SMLC to request a MS to perform the Multilateration Timing Advance (MTA) procedure and includes up to 8 sets of cells for which assistance information is provided. Upon receiving this request the MS autonomously determines the set of cells to use to perform MTA which may include one or more of the cells identified by the assistance information. If the MS selects a cell not identified by the assistance information then it shall read system information sent therein to determine if it supports MTA and PEO or EC operation. If the MS selects a cell identified by the assistance information then it shall be the strongest cell in the corresponding set of cells. The MS sends an EC MULTILATERATION REQUEST message if EC operation is enabled for the selected cell or an EGPRS MULTILATERATION REQUEST if PEO is enabled for the selected cell. This component is defined as follows: + +**Table 4.8.a: Positioning Multilateration Timing Advance Request** + +``` +-- add this definition to RRLP-Components module + +-- Positioning Multilateration Timing Advance request component, see sub-clause A.9 +PosMTA-Req ::= SEQUENCE { + target-Number-of-Cells INTEGER (0..7), + requested-MS-Synchronization-Accuracy INTEGER (0..15), + mta-Method MTA-Method, + random-ID-Set Random-ID-Set, + mpm-Timer INTEGER (0..7), + serving-cell BOOLEAN, + co-sited-cells Co-Sited-Cells OPTIONAL, -- identifies cells co-sited with serving cell + cell-Set1 Cell-Set, -- co-sited cells not co-sited with serving cell + cell-Set2 Cell-Set OPTIONAL, -- co-sited cells not co-sited with serving cell + cell-Set3 Cell-Set OPTIONAL, -- co-sited cells not co-sited with serving cell + cell-Set4 Cell-Set OPTIONAL, -- co-sited cells not co-sited with serving cell + cell-Set5 Cell-Set OPTIONAL, -- co-sited cells not co-sited with serving cell + cell-Set6 Cell-Set OPTIONAL, -- co-sited cells not co-sited with serving cell + cell-Set7 Cell-Set OPTIONAL, -- co-sited cells not co-sited with serving cell + cell-Set8 Cell-Set OPTIONAL -- co-sited cells not co-sited with serving cell + mta-security MTA-Security-Method OPTIONAL - identifies the MTA security method to be used +} +``` + +The elements of this component are defined in clause 5. + +## 4.9 Multilateration OTD Request + +This component is used by the SMLC to trigger the MS to perform Multilateration OTD (MOTD) measurements of the difference between the observed timing of the serving cell and the observed timings of a subset of neighbour cells. This message includes up to 8 sets of neighbour cells. For each set of the neighbour cells, the MS provides at most one MOTD report which shall refer to the neighbour cell with the highest received signal level from that set of neighbour cells. The message also includes a set of cells on which MOTD measurements are not required (i.e. a Serving Cell Set). This component triggers additional measurements if only one MOTD measurement can be reported by MS (cf. subclause A.10.2.3). + +**Table 4.9.a: Multilateration OTD Request** + +``` +-- add this definition to RRLP-Components module + +-- Multilateration OTD Request +MultilaterationOTD-Req ::= SEQUENCE { + targetNumOTDMeasurements INTEGER, + requiredDLSyncAccuracy INTEGER, + neighbourCellSets CellSets, + servingCellSet CellSet +} +``` + +The elements of this component are defined in clause 5. + +## 4.10 Multilateration OTD Response + +This component is used by MS to report the measured OTD results with neighbour cells to the SMLC. The difference between the TDMA frame timing of a neighbour cell and the TDMA frame timing of the serving cell is considered as OTD measurement of that particular neighbour cell. + +**Table 4.10.a: Multilateration OTD Response** + +``` +-- add this definition to RRLP-Components module + +-- Multilateration OTD Response +MultilaterationOTD-Rsp ::= SEQUENCE { + servingCellDLAccuracy INTEGER(1..16), + oTDMeasurementResults OTDMeasurementResults, + rXLEVMeasurementResults RXLEVMeasurementResults OPTIONAL +} +``` + +The elements of this component are defined in clause 5. + +# 5 Elements of Components + +## 5.1 ASN.1 Description + +The following ASN.1 code defines the elements of components. See the Annex A for further description of the contents of components and their elements. + +**Table 5.1.a: ASN.1 Description** + +``` +-- add these definitions to RRLP-Components module +-- Position instructions +PositionInstruct ::= SEQUENCE { + -- Method type + methodType MethodType, + positionMethod PositionMethod, + measureResponseTime MeasureResponseTime, + useMultipleSets UseMultipleSets, + environmentCharacter EnvironmentCharacter OPTIONAL +} +``` + +``` +-- +MethodType ::= CHOICE { + msAssisted AccuracyOpt, -- accuracy is optional + msBased Accuracy, -- accuracy is mandatory + msBasedPref Accuracy, -- accuracy is mandatory + msAssistedPref Accuracy -- accuracy is mandatory +} + +-- Accuracy of the location estimation +AccuracyOpt ::= SEQUENCE { + accuracy Accuracy OPTIONAL +} + +-- The values of this field are defined in 3GPP TS 23.032 (Uncertainty code) +Accuracy ::= INTEGER (0..127) + +-- Position Method +PositionMethod ::= ENUMERATED { + eotd (0), + gps (1), + gpsOrEOTD (2) +} + +-- Measurement request response time +MeasureResponseTime ::= INTEGER (0..7) + +-- useMultiple Sets, FFS! +UseMultipleSets ::= ENUMERATED { + multipleSets (0), -- multiple sets are allowed + oneSet (1) -- sending of multiple is not allowed +} + +-- Environment characterization +EnvironmentCharacter ::= ENUMERATED { + badArea (0), -- bad urban or suburban, heavy multipath and NLOS + notBadArea (1), -- light multipath and NLOS + mixedArea (2), -- not defined or mixed environment + ... +} + +-- E-OTD reference BTS for Assistance data IE +ReferenceAssistData ::= SEQUENCE { + bcchCarrier BCCHCarrier, -- BCCH carrier + bsic BSIC, -- BSIC + timeSlotScheme TimeSlotScheme, -- Timeslot scheme + btsPosition BTSPosition OPTIONAL +} + +-- ellipsoid point and +-- ellipsoid point with altitude and uncertainty ellipsoid shapes are supported +BTSPosition ::= Ext-GeographicalInformation + +-- RF channel number of BCCH +BCCHCarrier ::= INTEGER (0..1023) + +-- Base station Identity Code +BSIC ::= INTEGER (0..63) + +-- Timeslot scheme +TimeSlotScheme ::= ENUMERATED { + equalLength (0), + variousLength (1) +} + +-- Time slot (modulo) +ModuloTimeSlot ::= INTEGER (0..3) +``` + +``` + +-- E-OTD measurement assistance data IE +-- The total number of neighbors in this element (MsrAssistData) +-- and in SystemInfoAssistData element (presented neighbors +-- can be at a maximum 15!) +MsrAssistData ::= SEQUENCE { + msrAssistList SeqOfMsrAssistBTS +} +SeqOfMsrAssistBTS ::= SEQUENCE (SIZE(1..15)) OF MsrAssistBTS + +MsrAssistBTS ::= SEQUENCE { + bcchCarrier BCCHCarrier, -- BCCH carrier + bsic BSIC, -- BSIC + multiFrameOffset MultiFrameOffset, -- multiframe offset + timeSlotScheme TimeSlotScheme, -- Timeslot scheme + roughRTD RoughRTD, -- rough RTD value + + -- Location Calculation Assistance data is moved here + calcAssistanceBTS CalcAssistanceBTS OPTIONAL +} + +-- Multiframe offset +MultiFrameOffset ::= INTEGER (0..51) +-- The Multiframe Offset value 51 shall not be encoded by the transmitting entity and +-- shall be treated by the receiving entity as 0. + +-- Rough RTD value between one base station and reference BTS +RoughRTD ::= INTEGER (0..1250) +-- The RoughRTD value 1250 shall not be encoded by the transmitting entity and shall +-- be treated by the receiving entity as 0. + +-- E-OTD Measurement assistance data for system information List IE +-- The total number of base stations in this element (SystemInfoAssistData +-- presented neighbors) and in MsrAssistData element can be at a maximum 15. +SystemInfoAssistData ::= SEQUENCE { + systemInfoAssistList SeqOfSystemInfoAssistBTS +} +SeqOfSystemInfoAssistBTS ::= SEQUENCE (SIZE(1..32)) OF SystemInfoAssistBTS + +-- whether n.th is present or not ? +SystemInfoAssistBTS ::= CHOICE { + notPresent NULL, + present AssistBTSData +} + +-- Actual assistance data for system information base station +AssistBTSData ::= SEQUENCE { + bsic BSIC, -- BSIC + multiFrameOffset MultiFrameOffset, -- multiframe offset + timeSlotScheme TimeSlotScheme, -- Timeslot scheme + roughRTD RoughRTD, -- rough RTD value + + -- Location Calculation Assistance data + calcAssistanceBTS CalcAssistanceBTS OPTIONAL +} + +-- E-OTD Location calculation assistance data, +-- CalcAssistanceBTS element is optional not subfields +CalcAssistanceBTS ::= SEQUENCE { + fineRTD FineRTD, -- fine RTD value between base stations + referenceWGS84 ReferenceWGS84 -- reference coordinates +} + +-- Coordinates of neighbour BTS, WGS-84 ellipsoid +ReferenceWGS84 ::= SEQUENCE { + relativeNorth RelDistance, -- relative distance (south negative) + relativeEast RelDistance, -- relative distance (west negative) + -- Relative Altitude is not always known + relativeAlt RelativeAlt OPTIONAL -- relative altitude +} + +-- Fine RTD value between this BTS and the reference BTS +FineRTD ::= INTEGER (0..255) + +-- Relative north/east distance +RelDistance ::= INTEGER (-200000..200000) + +``` + +``` +-- Relative altitude +RelativeAlt ::= INTEGER (-4000..4000) + +-- Measure position response IEs +-- Reference Identity +-- Multiple sets +MultipleSets ::= SEQUENCE { + -- number of reference sets + nbrOfSets INTEGER (2..3), + + -- This field actually tells the number of reference BTSs + nbrOfReferenceBTSs INTEGER (1..3), + + -- This field is conditional and included optionally only if + -- nbrOfSets is 3 and number of reference BTSs is 2. + referenceRelation ReferenceRelation OPTIONAL +} + +-- Relation between refence BTSs and sets +ReferenceRelation ::= ENUMERATED { + secondBTSThirdSet (0), -- 1st BTS related to 1st and 2nd sets + secondBTSSecondSet (1), -- 1st BTS related to 1st and 3rd sets + firstBTSFirstSet (2) -- 1st BTS related to 1st set +} + +-- Reference BTS Identity, this element contains number of +-- BTSs told nbrOfReferenceBTSs field in Multiple sets element) +ReferenceIdentity ::= SEQUENCE { + -- Reference BTS list + refBTSList SeqOfReferenceIdentityType +} +SeqOfReferenceIdentityType ::= SEQUENCE (SIZE(1..3)) OF ReferenceIdentityType + +-- Cell identity +ReferenceIdentityType ::= CHOICE { + bsicAndCarrier BSICAndCarrier, -- BSIC and Carrier + ci CellID, -- Cell ID, LAC not needed + requestIndex RequestIndex, -- Index to Requested Neighbor List + systemInfoIndex SystemInfoIndex, -- Index to System info list, this type of ref. identity + -- shall not be used by the MS unless it has received + -- the SystemInfoAssistData from the SMLC for this cell. + ciAndLAC CellIDAndLAC -- CI and LAC +} + +BSICAndCarrier ::= SEQUENCE { + carrier BCCHCarrier, + bsic BSIC +} + +RequestIndex ::= INTEGER (1..16) + +SystemInfoIndex ::= INTEGER (1..32) + +CellIDAndLAC ::= SEQUENCE { + referenceLAC LAC, -- Location area code + referenceCI CellID -- Cell identity +} + +CellID ::= INTEGER (0..65535) +LAC ::= INTEGER (0..65535) + +-- OTD-MeasureInfo +OTD-MeasureInfo ::= SEQUENCE { + -- Measurement info elements, OTD-MsrElement is repeated number of times + -- told in nbrOfReferenceBTSs in MultipleSets, default value is 1 + otdMsrFirstSets OTD-MsrElementFirst, + + -- if more than one sets are present this element is repeated + -- NumberOfSets - 1 (-1 = first set) + otdMsrRestSets SeqOfOTD-MsrElementRest OPTIONAL +} + +SeqOfOTD-MsrElementRest ::= SEQUENCE (SIZE(1..2)) OF OTD-MsrElementRest +``` + +``` + +-- OTD measurment information for 1 set +OTD-MsrElementFirst ::= SEQUENCE { + refFrameNumber INTEGER (0..42431), -- Frame number modulo 42432 + referenceTimeSlot ModuloTimeSlot, + toaMeasurementsOfRef TOA-MeasurementsOfRef OPTIONAL, + stdResolution StdResolution, + taCorrection INTEGER (0..960) OPTIONAL, -- TA correction + + -- measured neighbors in OTD measurements + otd-FirstSetMsrs SeqOfOTD-FirstSetMsrs OPTIONAL +} +SeqOfOTD-FirstSetMsrs ::= SEQUENCE (SIZE(1..10)) OF OTD-FirstSetMsrs + +-- OTD measurment information 2 and 3 sets if exist +OTD-MsrElementRest ::= SEQUENCE { + refFrameNumber INTEGER (0..42431), -- Frame number modulo 42432 + referenceTimeSlot ModuloTimeSlot, + toaMeasurementsOfRef TOA-MeasurementsOfRef OPTIONAL, + stdResolution StdResolution, + taCorrection INTEGER (0..960) OPTIONAL, -- TA correction + + -- measured neighbors in OTD measurements + otd-MsrsOfOtherSets SeqOfOTD-MsrsOfOtherSets OPTIONAL +} +SeqOfOTD-MsrsOfOtherSets ::= SEQUENCE (SIZE(1..10)) OF OTD-MsrsOfOtherSets + +-- Standard deviation of the TOA measurements from the reference BTS +TOA-MeasurementsOfRef ::= SEQUENCE { + refQuality RefQuality, + numOfMeasurements NumOfMeasurements +} + +RefQuality ::= INTEGER (0..31) -- St Dev of TOA of reference as defined in annex +NumOfMeasurements ::= INTEGER (0..7) -- No. of measurements for RefQuality as defined in annex +StdResolution ::= INTEGER (0..3) -- Values of resolution are defined in annex + +OTD-FirstSetMsrs ::= OTD-MeasurementWithID + +-- Neighbour info in OTD measurements 0-10 times in TD measurement info +OTD-MsrsOfOtherSets ::= CHOICE { + identityNotPresent OTD-Measurement, + identityPresent OTD-MeasurementWithID +} + +-- For this OTD measurement identity is same as the identity of BTS +-- in the first set with same sequence number +OTD-Measurement ::= SEQUENCE { + nborTimeSlot ModuloTimeSlot, + eotdQuality EOTDQuality, + otdValue OTDValue +} + +-- This measurement contains the BTS identity and measurement +OTD-MeasurementWithID ::= SEQUENCE { + neighborIdentity NeighborIdentity, + nborTimeSlot ModuloTimeSlot, + eotdQuality EOTDQuality, + otdValue OTDValue +} + +EOTDQuality ::= SEQUENCE { + nbrOfMeasurements INTEGER (0..7), + stdOfEOTD INTEGER (0..31) +} + +NeighborIdentity ::= CHOICE { + bsicAndCarrier BSICAndCarrier, -- BSIC and Carrier + ci CellID, -- Cell ID, LAC not needed + multiFrameCarrier MultiFrameCarrier, -- MultiFrameOffset and BSIC + requestIndex RequestIndex, -- Index to Requested Neighbor List + systemInfoIndex SystemInfoIndex, -- Index to System info list, this type of neighbour + -- identity shall not be used by the MS unless it has + -- received the SystemInfoAssistData from the SMLC for + -- this cell. + ciAndLAC CellIDAndLAC -- CI and LAC +} + +``` + +``` + +-- Multiframe and carrier +MultiFrameCarrier ::= SEQUENCE { + bcchCarrier BCCHCarrier, + multiFrameOffset MultiFrameOffset +} + +-- OTD measurement value for neighbour +OTDValue ::= INTEGER (0..39999) + +-- Location information IE +LocationInfo ::= SEQUENCE { + refFrame INTEGER (0..65535), -- Reference Frame number + -- If refFrame is within (42432..65535), it shall be ignored by the receiver + -- in that case the MS should provide GPS TOW if available + gpsTOW INTEGER (0..14399999) OPTIONAL, -- GPS TOW + fixType FixType, + -- Note that applicable range for refFrame is 0 - 42431 + -- Possible shapes carried in posEstimate are + -- ellipsoid point, + -- ellipsoid point with uncertainty circle + -- ellipsoid point with uncertainty ellipse + -- ellipsoid point with altitude and uncertainty ellipsoid + posEstimate Ext-GeographicalInformation +} + +FixType ::= INTEGER { + twoDFix (0), + threeDFix (1) +} (0..1) + +-- GPS-Measurement information +GPS-MeasureInfo ::= SEQUENCE { + -- Measurement info elements + -- user has to make sure that in this element is number of elements + -- defined in reference BTS identity + gpsMsrSetList SeqOfGPS-MsrSetElement +} +SeqOfGPS-MsrSetElement ::= SEQUENCE (SIZE(1..3)) OF GPS-MsrSetElement + +-- OTD measurement information 1-3 times in message +GPS-MsrSetElement ::= SEQUENCE { + refFrame INTEGER (0..65535) OPTIONAL, -- Reference Frame number + gpsTOW GPSTOW24b, -- GPS TOW + -- Note that applicable range for refFrame is 0 - 42431 +} + +--N_SAT can be read from number of elements of gps-msrList + + gps-msrList SeqOfGPS-MsrElement +} + +-- 24 bit presentation for GPSTOW +GPSTOW24b ::= INTEGER (0..14399999) + +-- measured elements in measurement parameters field +SeqOfGPS-MsrElement ::= SEQUENCE (SIZE(1..16)) OF GPS-MsrElement + +GPS-MsrElement ::= SEQUENCE { + satelliteID SatelliteID, -- Satellite identifier + cNo INTEGER (0..63), -- carrier noise ratio + doppler INTEGER (-32768..32767), -- doppler, multiply by 0,2 + wholeChips INTEGER (0..1022), -- whole value of the code phase measurement + fracChips INTEGER (0..1024), -- fractional value of the code phase measurement + -- a value of 1024 shall not be encoded by the sender + -- the receiver shall consider a value of 1024 to be + -- invalid data + mpathIndic MpathIndic, -- multipath indicator + pseuRangeRMSErr INTEGER (0..63) -- index +} + +-- Multipath indicator +MpathIndic ::= ENUMERATED { + notMeasured (0), + low (1), + medium (2), + high (3) +} + +``` + +``` +-- Location error IE +LocationError ::= SEQUENCE { + locErrorReason LocErrorReason, + additionalAssistanceData AdditionalAssistanceData OPTIONAL, + ... +} + +LocErrorReason ::= ENUMERATED { + unDefined (0), + notEnoughBTSS (1), + notEnoughSats (2), + eotdLocCalAssDataMissing (3), + eotdAssDataMissing (4), + gpsLocCalAssDataMissing (5), + gpsAssDataMissing (6), + methodNotSupported (7), + notProcessed (8), + refBTSForGPSNotServingBTS (9), + refBTSForEOTDNotServingBTS (10), + ..., + notEnoughGANSSSats (11), + ganssAssDataMissing (12), + refBTSForGANSSNotServingBTS (13) +} + +-- exception handling: +-- an unrecognized value shall be treated the same as value 0 + +-- defines additional assistance data needed for any new location attempt +-- MS shall retain any assistance data already received +AdditionalAssistanceData ::= SEQUENCE { + gpsAssistanceData GPSAssistanceData OPTIONAL, + extensionContainer ExtensionContainer OPTIONAL, + ..., + ganssAssistanceData GANSSAssistanceData OPTIONAL +} + +GPSAssistanceData ::= OCTET STRING (SIZE (1..maxGPSAssistanceData)) +-- GPSAssistanceData has identical structure and encoding to octets 3 to n of the +-- GPS Assistance Data IE in 3GPP TS 49.031 + +maxGPSAssistanceData INTEGER ::= 40 + +GANSSAssistanceData ::= OCTET STRING (SIZE (1..maxGANSSAssistanceData)) +-- GANSSAssistanceData has identical structure and encoding to octets 3 to n of the +-- GANSS Assistance Data IE in 3GPP TS 49.031 + +maxGANSSAssistanceData INTEGER ::= 40 + +-- Protocol Error Causes +ErrorCodes ::= ENUMERATED { + unDefined (0), + missingComponent (1), + incorrectData (2), + missingIEorComponentElement (3), + messageTooShort (4), + unknownReferenceNumber (5), + ... +} + +-- exception handling: +-- an unrecognized value shall be treated the same as value 0 + +-- GPS assistance data IE +GPS-AssistData ::= SEQUENCE { + controlHeader ControlHeader +} +``` + +``` + +-- More Assistance Data To Be Sent IE +-- More Assistance Data Components On the Way indication for delivery of an entire set of assistance +-- data in multiple Assistance Data components. + +MoreAssDataToBeSent ::= ENUMERATED { + noMoreMessages (0), + -- This is the only or last Assistance Data message used to deliver + -- the entire set of assistance data. + moreMessagesOnTheWay (1) + -- The SMLC will send more Assistance Data messages or a final RRLP + -- Measure Position Request message to deliver the + -- the entire set of assistance data. +} + +-- Control header of the GPS assistance data +ControlHeader ::= SEQUENCE { + -- Field type Present information + referenceTime ReferenceTime OPTIONAL, + refLocation RefLocation OPTIONAL, + dgpsCorrections DGPSCorrections OPTIONAL, + navigationModel NavigationModel OPTIONAL, + ionosphericModel IonosphericModel OPTIONAL, + utcModel UTCModel OPTIONAL, + almanac Almanac OPTIONAL, + acquisAssist AcquisAssist OPTIONAL, + realTimeIntegrity SeqOf-BadSatelliteSet OPTIONAL +} + +ReferenceTime ::= SEQUENCE { + gpsTime GPSTime, + gsmTime GSMTime OPTIONAL, + gpsTowAssist GPSTOWAssist OPTIONAL +} + +-- GPS Time includes week number and time-of-week (TOW) +GPSTime ::= SEQUENCE { + gpsTOW23b GPSTOW23b, + gpsWeek GPSWeek +} + +-- GPSTOW, range 0-604799,92, resolution 0,08 sec, 23-bit presentation +GPSTOW23b ::= INTEGER (0..7559999) + +-- GPS week number +GPSWeek ::= INTEGER (0..1023) + +-- GPSTOWAssist consists of TLM message, Anti-spoof flag, Alert flag, and 2 reserved bits in TLM +Word +-- for each visible satellite. +-- N_SAT can be read from number of elements in GPSTOWAssist +GPSTOWAssist ::= SEQUENCE (SIZE(1..12)) OF GPSTOWAssistElement + +GPSTOWAssistElement ::= SEQUENCE { + satelliteID SatelliteID, + tlmWord TLMWord, + antiSpoof AntiSpoofFlag, + alert AlertFlag, + tlmRsvdBits TLMReservedBits +} + +``` + +``` + +-- TLM Word, 14 bits +TLMWord ::= INTEGER (0..16383) + +-- Anti-Spoof flag +AntiSpoofFlag ::= INTEGER (0..1) + +-- Alert flag +AlertFlag ::= INTEGER (0..1) + +-- Reserved bits in TLM word, MSB occurs earlier in TLM Word transmitted by satellite +TLMReservedBits ::= INTEGER (0..3) + +GSMTTime ::= SEQUENCE { + bcchCarrier BCCHCarrier, -- BCCH carrier + bsic BSIC, -- BSIC + frameNumber FrameNumber, + timeSlot TimeSlot, + bitNumber BitNumber +} + +-- Frame number +FrameNumber ::= INTEGER (0..2097151) + +-- Time slot number +TimeSlot ::= INTEGER (0..7) + +-- Bit number +BitNumber ::= INTEGER (0..156) + +-- Reference Location IE +RefLocation ::= SEQUENCE { + threeDLocation Ext-GeographicalInformation +} + +-- DGPS Corrections IE +DGPSCorrections ::= SEQUENCE { + + gpstow INTEGER (0..604799), -- DGPS reference time + status INTEGER (0..7), + -- N_SAT can be read from number of elements of satList + satList SeqOfSatElement +} + +SeqOfSatElement ::= SEQUENCE (SIZE (1..16)) OF SatElement + +-- number of correction for satellites +SatElement ::= SEQUENCE { + satelliteID SatelliteID, + + --- Sequence number for ephemeris + iode INTEGER (0..239), + -- User Differential Range Error + udre INTEGER (0..3), + + -- Pseudo Range Correction, range is + -- -655,04 - +655,04, + pseudoRangeCor INTEGER (-2047..2047), + + -- Pseudo Range Rate Correction, range is + -- -4,064 - +4,064, + rangeRateCor INTEGER (-127..127), + + -- Delta Pseudo Range Correction 2 + deltaPseudoRangeCor2 INTEGER (-127..127), -- This IE shall be ignored by the receiver + -- and set to zero by the sender + -- Delta Pseudo Range Correction 2 + deltaRangeRateCor2 INTEGER (-7..7), -- This IE shall be ignored by the receiver + -- and set to zero by the sender + -- Delta Pseudo Range Correction 3 + deltaPseudoRangeCor3 INTEGER (-127..127), -- This IE shall be ignored by the receiver + -- and set to zero by the sender + -- Delta Pseudo Range Correction 3 + deltaRangeRateCor3 INTEGER (-7..7) -- This IE shall be ignored by the receiver + -- and set to zero by the sender +} + +SatelliteID ::= INTEGER (0..63) -- identifies satellite + +``` + +``` + +-- Navigation Model IE +NavigationModel ::= SEQUENCE { + navModelList SeqOfNavModelElement +} + +-- navigation model satellite list +SeqOfNavModelElement ::= SEQUENCE (SIZE(1..16)) OF NavModelElement + +NavModelElement ::= SEQUENCE { + satelliteID SatelliteID, + satStatus SatStatus -- satellite status +} + +-- the Status of the navigation model +SatStatus ::= CHOICE { + -- New satellite, new Navigation Model + newSatelliteAndModelUC UncompressedEphemeris, + + -- Existing satellite, Existing Navigation Model + oldSatelliteAndModel NULL, + + -- Existing satellite, new Navigation Model + newNaviModelUC UncompressedEphemeris, + ... +} + +-- Uncompressed satellite ephemeris and clock corrections +UncompressedEphemeris ::= SEQUENCE { + ephemCodeOnL2 INTEGER (0..3), + ephemURA INTEGER (0..15), + ephemSVHealth INTEGER (0..63), + ephemIODC INTEGER (0..1023), + ephemL2Pflag INTEGER (0..1), + ephemSF1RsVd EphemerisSubframe1Reserved, + ephemTgd INTEGER (-128..127), + ephemToc INTEGER (0..37799), + ephemAF2 INTEGER (-128..127), + ephemAF1 INTEGER (-32768..32767), + ephemAF0 INTEGER (-2097152..2097151), + ephemCrs INTEGER (-32768..32767), + ephemDeltaN INTEGER (-32768..32767), + ephemM0 INTEGER (-2147483648..2147483647), + ephemCuc INTEGER (-32768..32767), + ephemE INTEGER (0..4294967295), + ephemCus INTEGER (-32768..32767), + ephemAPowerHalf INTEGER (0..4294967295), + ephemToe INTEGER (0..37799), + ephemFitFlag INTEGER (0..1), + ephemAODA INTEGER (0..31), + ephemCic INTEGER (-32768..32767), + ephemOmegaA0 INTEGER (-2147483648..2147483647), + ephemCis INTEGER (-32768..32767), + ephemI0 INTEGER (-2147483648..2147483647), + ephemCrc INTEGER (-32768..32767), + ephemW INTEGER (-2147483648..2147483647), + ephemOmegaADot INTEGER (-8388608..8388607), + ephemIDot INTEGER (-8192..8191) +} + +-- Reserved bits in subframe 1 of navigation message +EphemerisSubframe1Reserved ::= SEQUENCE { + reserved1 INTEGER (0..8388607), -- 23-bit field + reserved2 INTEGER (0..16777215), -- 24-bit field + reserved3 INTEGER (0..16777215), -- 24-bit field + reserved4 INTEGER (0..65535) -- 16-bit field +} + +``` + +``` + +-- Ionospheric Model IE +IonosphericModel ::= SEQUENCE { + alfa0 INTEGER (-128..127), + alfa1 INTEGER (-128..127), + alfa2 INTEGER (-128..127), + alfa3 INTEGER (-128..127), + beta0 INTEGER (-128..127), + beta1 INTEGER (-128..127), + beta2 INTEGER (-128..127), + beta3 INTEGER (-128..127) +} + +-- Universal Time Coordinate Model +UTCModel ::= SEQUENCE { + utcA1 INTEGER (-8388608..8388607), + utcA0 INTEGER (-2147483648..2147483647), + utcTot INTEGER (0..255), + utcWNT INTEGER (0..255), + utcDeltaTls INTEGER (-128..127), + utcWNlsf INTEGER (0..255), + utcDN INTEGER (-128..127), + utcDeltaTlsf INTEGER (-128..127) +} + +-- Almanac, Long term model +-- NOTE: These are parameters are subset of the ephemeris +-- NOTE: But with reduced resolution and accuracy +Almanac ::= SEQUENCE { + almanacWNa INTEGER (0..255), -- Once per message + + -- navigation model satellite list. + -- The size of almanacList is actually Nums_Sats_Total field + almanacList SeqOfAlmanacElement +} +SeqOfAlmanacElement ::= SEQUENCE (SIZE(1..64)) OF AlmanacElement + +-- Almanac info once per satellite +AlmanacElement ::= SEQUENCE { + satelliteID SatelliteID, + almanacE INTEGER (0..65535), + almanacToa INTEGER (0..255), + almanacKsii INTEGER (-32768..32767), + almanacOmegaDot INTEGER (-32768..32767), + almanacSVhealth INTEGER (0..255), + almanacAPowerHalf INTEGER (0..16777215), + almanacOmega0 INTEGER (-8388608..8388607), + almanacW INTEGER (-8388608..8388607), + almanacM0 INTEGER (-8388608..8388607), + almanacAF0 INTEGER (-1024..1023), + almanacAF1 INTEGER (-1024..1023) +} + +-- Acquisition Assistance +AcquisAssist ::= SEQUENCE { + + -- Number of Satellites can be read from acquistList + timeRelation TimeRelation, + + -- Acquisition assistance list + -- The size of Number of Satellites is actually Number of Satellites field + acquisList SeqOfAcquisElement +} +SeqOfAcquisElement ::= SEQUENCE (SIZE(1..16)) OF AcquisElement + +-- the relationship between GPS time and air-interface timing +TimeRelation ::= SEQUENCE { + -- + gpsTOW GPSTOW23b, -- 23b presentation + gsmTime GSMTime OPTIONAL +} + +``` + +``` + +-- data occurring per number of satellites +AcquisElement ::= SEQUENCE { + svid SatelliteID, + + -- Doppler 0th order term, + -- -5120,0 - 5117,5 Hz (= -2048 - 2047 with 2,5 Hz resolution) + doppler0 INTEGER (-2048..2047), + additionalDoppler AdditionalDopplerFields OPTIONAL, + codePhase INTEGER (0..1022), -- Code Phase + intCodePhase INTEGER (0..19), -- Integer Code Phase + gpsBitNumber INTEGER (0..3), -- GPS bit number + codePhaseSearchWindow INTEGER (0..15), -- Code Phase Search Window + additionalAngle AdditionalAngleFields OPTIONAL +} + +AdditionalDopplerFields ::= SEQUENCE { + -- Doppler 1st order term, -1,0 - +0,5 Hz/sec + -- (= -42 + (0 to 63) with 1/42 Hz/sec. resolution) + doppler1 INTEGER (0..63), + dopplerUncertainty INTEGER (0..7) + -- a sender shall not encode any DopplerUncertainty value in the range 5 to 7 + -- a receiver shall ignore any value between 5 and 7. +} + +AdditionalAngleFields ::= SEQUENCE { + -- azimuth angle, 0 - 348,75 deg (= 0 - 31 with 11,25 deg resolution) + azimuth INTEGER (0..31), + -- elevation angle, 0 - 78,75 deg (= 0 - 7 with 11,25 deg resolution) + elevation INTEGER (0..7) +} + +-- Real-Time Integrity +-- number of bad satellites can be read from this element +SeqOf-BadSatelliteSet ::= SEQUENCE (SIZE(1..16)) OF SatelliteID + +-- Extension Elements + +-- Release 98 Extensions here +Rel98-MsrPosition-Req-Extension ::= SEQUENCE { + rel98-Ext-ExpOTD Rel98-Ext-ExpOTD OPTIONAL, -- ExpectedOTD extension + ..., + gpsTimeAssistanceMeasurementRequest NULL OPTIONAL, + gpsReferenceTimeUncertainty GPSReferenceTimeUncertainty OPTIONAL +} + +-- Further R98 extensions here +} +Rel98-AssistanceData-Extension ::= SEQUENCE { + rel98-Ext-ExpOTD Rel98-Ext-ExpOTD OPTIONAL, -- ExpectedOTD extension + ..., + gpsTimeAssistanceMeasurementRequest NULL OPTIONAL, + gpsReferenceTimeUncertainty GPSReferenceTimeUncertainty OPTIONAL +} + +-- Further R98 extensions here +} + +-- Release 98 ExpOTD extension +Rel98-Ext-ExpOTD ::= SEQUENCE { + -- If MsrAssistBTS is included in message, msrAssistData-R98-ExpOTD shall be included. + msrAssistData-R98-ExpOTD MsrAssistData-R98-ExpOTD OPTIONAL, + + -- If SystemInfoAssistData is included in message, systemInfoAssistData-R98-ExpOTD shall be + -- included. + systemInfoAssistData-R98-ExpOTD SystemInfoAssistData-R98-ExpOTD OPTIONAL +} + +-- MsrAssistData R98 extension +MsrAssistData-R98-ExpOTD ::= SEQUENCE { + msrAssistList-R98-ExpOTD SeqOfMsrAssistBTS-R98-ExpOTD +} + +-- Indexes in SeqOfMsrAssistBTS-R98-ExpOTD refer to SeqOfMsrAssistBTS +-- If the index exceeds the SeqOfMsrAssistBTS range or if there is other +-- inconsistencies between the BTS indices, the MS shall apply protocol +-- error cause incorrectData +SeqOfMsrAssistBTS-R98-ExpOTD ::= SEQUENCE (SIZE(1..15)) OF MsrAssistBTS-R98-ExpOTD + +``` + +``` + +-- This element completes MsrAssistBTS IE +MsrAssistBTS-R98-ExpOTD ::= SEQUENCE { + expectedOTD ExpectedOTD, + expOTDUncertainty ExpOTDUncertainty +} + +-- SystemInfoAssistData R98 extension +SystemInfoAssistData-R98-ExpOTD ::= SEQUENCE { + systemInfoAssistListR98-ExpOTD SeqOfSystemInfoAssistBTS-R98-ExpOTD +} + +-- SeqOfSystemInfoAssistBTS-R98-ExpOTD index refer to SeqOfSystemInfoAssistBTS +-- If the index exceeds the SeqOfSystemInfoAssistBTS range or if there is other +-- inconsistencies between the BTS indices, the MS shall apply protocol +-- error cause incorrectData +SeqOfSystemInfoAssistBTS-R98-ExpOTD ::= SEQUENCE (SIZE(1..32)) OF SystemInfoAssistBTS-R98-ExpOTD + +-- whether n.th is present or not ? +SystemInfoAssistBTS-R98-ExpOTD ::= CHOICE { + notPresent NULL, + present AssistBTSData-R98-ExpOTD +} + +-- This element completes AssistBTSData IE +AssistBTSData-R98-ExpOTD ::= SEQUENCE { + expectedOTD ExpectedOTD, + expOTDUncertainty ExpOTDUncertainty -- Uncertainty of expected OTD +} + +-- Expected OTD value between nbor base station and reference BTS +-- at MS's current estimated location. +ExpectedOTD ::= INTEGER (0..1250) +-- The ExpectedOTD value 1250 shall not be encoded by the transmitting entity and +-- shall be treated by the receiving entity as 0. +-- Uncertainty of Expected OTD in bits +ExpOTDUncertainty ::= INTEGER(0..7) + +-- Release 98 extensions + +GPSReferenceTimeUncertainty ::= INTEGER (0 .. 127) -- Coding according to Annex + +GPSTimeAssistanceMeasurements ::= SEQUENCE { + referenceFrameMSB INTEGER (0 .. 63) OPTIONAL, -- MSB of frame number + gpsTowSubms INTEGER (0 .. 9999) OPTIONAL, -- in units of 100ns, for MS based AGPS + deltaTow INTEGER (0 .. 127) OPTIONAL, -- for MS assisted AGPS + gpsReferenceTimeUncertainty GPSReferenceTimeUncertainty OPTIONAL +} + +Rel-98-MsrPosition-Rsp-Extension ::= SEQUENCE { + -- First extension to Release 98 + rel-98-Ext-MeasureInfo SEQUENCE { + otd-MeasureInfo-R98-Ext OTD-MeasureInfo-R98-Ext OPTIONAL + }, + ..., + timeAssistanceMeasurements GPSTimeAssistanceMeasurements OPTIONAL + -- Further R98 extensions here +} + +-- This is an addition to OTD-MeasureInfo element defined in original message, +-- If OTD-MeasureInfo is absent, or if one or more OTD-MsrElementRest are present +-- OTD-MeasureInfo-R98-Ext shall be absent. +-- OTD-MeasureInfo-R98-Ext +OTD-MeasureInfo-R98-Ext ::= SEQUENCE { + -- Measurement info elements + otdMsrFirstSets-R98-Ext OTD-MsrElementFirst-R98-Ext +} + +``` + +``` + +-- OTD measurement information Ext for the first set only +OTD-MsrElementFirst-R98-Ext ::= SEQUENCE { + -- additional measured neighbors in OTD measurements + otd-FirstSetMsrs-R98-Ext SeqOfOTD-FirstSetMsrs-R98-Ext OPTIONAL +} +SeqOfOTD-FirstSetMsrs-R98-Ext ::= SEQUENCE (SIZE(1..5)) OF OTD-FirstSetMsrs + +Rel-5-MsrPosition-Rsp-Extension ::= SEQUENCE { + extended-reference Extended-reference OPTIONAL, + -- The extended-reference shall be included by the MS if and only if previously + -- received from the SMLC in a Measure Position Request. When included, the value sent + -- by the MS shall equal the value received from the SMLC. + + -- extension to Release 5, for RRLP pseudo-segmentation here + otd-MeasureInfo-5-Ext OTD-MeasureInfo-5-Ext OPTIONAL, + ulPseudoSegInd UlPseudoSegInd OPTIONAL, -- Included when uplink RRLP + -- Pseudo-segmentation is used, not included when no uplink pseudo-segmentation is used + ... + -- Possibly more extensions for Release 5 here later +} + +Extended-reference ::= SEQUENCE { + smlc-code INTEGER (0..63), + transaction-ID INTEGER (0..262143) +} + +OTD-MeasureInfo-5-Ext ::= SeqOfOTD-MsrElementRest + -- if more than one measurement sets are present this element is repeated + -- NumberOfSets - 1 (-1 = first set) combined in OTD-MeasureInfo-5-Ext and + -- OTD-MeasureInfo (e.g. if NumberOfSets is 3, then one otdMsrRestSets may + -- be sent in OTD-MeasureInfo-5-Ext and one in OTD-MeasureInfo) + +-- First part of Uplink RRLP Pseudo-segmentation indication, possibly more may be defined +-- in the future for segmentation with more than two segments. +UlPseudoSegInd ::= ENUMERATED { + firstOfMany (0), + secondOfMany(1) +} + +Rel5-MsrPosition-Req-Extension ::= SEQUENCE { + extended-reference Extended-reference, + ... + -- Possibly more extensions for Release 5 here later +} + +Rel5-AssistanceData-Extension ::= SEQUENCE { + extended-reference Extended-reference, + ... + + -- Possibly more extensions for Release 5 here later +} + +Rel-5-ProtocolError-Extension ::= SEQUENCE { + extended-reference Extended-reference OPTIONAL, + -- The extended-reference shall be included by the MS if and only if previously + -- received from the SMLC. + -- When included, the value sent by the MS shall equal the value received from the SMLC. + ... + + -- Possibly more extensions for Release 5 here later +} + +-- Release 7 Extensions here + +Rel7-MsrPosition-Req-Extension ::= SEQUENCE { + velocityRequested NULL OPTIONAL, + ganssPositionMethod GANSSPositioningMethod OPTIONAL, + ganss-AssistData GANSS-AssistData OPTIONAL, + ganssCarrierPhaseMeasurementRequest NULL OPTIONAL, + ganssTODGSMTTimeAssociationMeasurementRequest NULL OPTIONAL, + requiredResponseTime RequiredResponseTime OPTIONAL, + add-GPS-AssistData Add-GPS-AssistData OPTIONAL, + ganssMultiFreqMeasurementRequest NULL OPTIONAL, + ... + -- Further Release 7 extentions here +} + +``` + +``` + +-- additional satellite systems may be added in future versions of the protocol +-- Bit 0 of GANSSPositioningMethod bit map shall not be the only one set to TRUE ('1') +GANSSPositioningMethod ::= BIT STRING { + gps (0), + galileo (1), + sbas (2), + modernizedGPS (3), + qzss (4), + glonass (5), + bds (6) } (SIZE (2..16)) + +GANSS-AssistData ::= SEQUENCE { + ganss-controlHeader GANSS-ControlHeader +} +GANSS-ControlHeader ::= SEQUENCE { + ganssCommonAssistData GANSSCommonAssistData OPTIONAL, + ganssGenericAssistDataList SeqOfGANSSGenericAssistDataElement OPTIONAL +} + +-- GANSS Common Assistance Data Elements +GANSSCommonAssistData ::= SEQUENCE { + ganssReferenceTime GANSSReferenceTime OPTIONAL, + ganssRefLocation GANSSRefLocation OPTIONAL, + ganssIonosphericModel GANSSIonosphericModel OPTIONAL, + ... , + ganssAddIonosphericModel GANSSAddIonosphericModel OPTIONAL, + ganssEarthOrientParam GANSSEarthOrientParam OPTIONAL, + -- If GANSSReferenceTime is included, GANSSReferenceTime-R10-Ext shall also be included. + ganssReferenceTime-R10-Ext GANSSReferenceTime-R10-Ext OPTIONAL +} + +-- List of GANSS Generic Assistance Data Elements, up to 8 GANSS +SeqOfGANSSGenericAssistDataElement ::= SEQUENCE (SIZE (1..8)) OF GANSSGenericAssistDataElement +-- GANSS Generic Assistance Data Elements +GANSSGenericAssistDataElement ::= SEQUENCE { + ganssID INTEGER (0..7) OPTIONAL, -- Coding according to Annex + ganssTimeModel SeqOfGANSSTimeModel OPTIONAL, + ganssDiffCorrections GANSSDiffCorrections OPTIONAL, + ganssNavigationModel GANSSNavModel OPTIONAL, + ganssRealTimeIntegrity GANSSRealTimeIntegrity OPTIONAL, + ganssDataBitAssist GANSSDataBitAssist OPTIONAL, + ganssRefMeasurementAssist GANSSRefMeasurementAssist OPTIONAL, + ganssAlmanacModel GANSSAlmanacModel OPTIONAL, + ganssUTCModel GANSSUTCModel OPTIONAL, + ganssEphemerisExtension GANSS Ephemeris Extension OPTIONAL, + ganssEphemerisExtCheck GANSS Ephemeris Extension Check OPTIONAL, + ... , + sbasID INTEGER (0..7) OPTIONAL, -- Coding according to Annex + ganssAddUTCModel GANSSAddUTCModel OPTIONAL, + ganssAuxiliaryInfo GANSSAuxiliaryInformation OPTIONAL, + ganssDiffCorrectionsValidityPeriod GANSSDiffCorrectionsValidityPeriod OPTIONAL, + -- If SeqOfGANSSTimeModel is included, SeqOfGANSSTimeModel-R10-Ext shall also be included. + ganssTimeModel-R10-Ext SeqOfGANSSTimeModel-R10-Ext OPTIONAL, + -- If GANSSRefMeasurementAssist is included, GANSSRefMeasurementAssist-R10-Ext shall also be + -- included. + ganssRefMeasurementAssist-R10-Ext GANSSRefMeasurementAssist-R10-Ext OPTIONAL, + -- If GANSSAlmanacModel is included, GANSSAlmanacModel-R10-Ext shall also be included. + ganssAlmanacModel-R10-Ext GANSSAlmanacModel-R10-Ext OPTIONAL, + ganssAlmanacModel-R12-Ext GANSSAlmanacModel-R12-Ext OPTIONAL, + ganssRefMeasurementAssist-R12-Ext GANSSRefMeasurementAssist-R12-Ext OPTIONAL, + --The field may be present if the ganssID indicates BDS, otherwise it is not present. + bdsDifferentialCorrections-r12 BDS-DiffCorrections-r12 OPTIONAL, + --The field may be present if the ganssID indicates BDS, otherwise it is not present. + bdsGridModel-r12 BDS-GridModelParameter-r12 OPTIONAL +} + +-- GANSS COMMON ASSISTANCE DATA ELEMENTS + +-- GANSS Reference Time IE +GANSSReferenceTime ::= SEQUENCE { + ganssRefTimeInfo GANSSRefTimeInfo, + ganssTOD-GSMTimeAssociation GANSTOD-GSMTimeAssociation OPTIONAL +} + +``` + +``` +-- GANSS Reference Time includes GANSS TOD, GANSS Day, uncertainty +GANSSRefTimeInfo ::= SEQUENCE { + -- ganssDay shall be present in this version of the protocol + ganssDay INTEGER(0 .. 8191) OPTIONAL, + ganssTOD GANSSTOD, + ganssTODUncertainty GANSSTODUncertainty OPTIONAL, + ganssTimeID INTEGER (0 .. 7) OPTIONAL +} + +-- GANSS TOD integer seconds +GANSSTOD ::= INTEGER (0 .. 86399) + +-- GANSS TOD uncertainty +GANSSTODUncertainty ::= INTEGER (0 .. 127) -- Coding according to Annex + +-- GANSS Reference Time Rel-10 Extension: +GANSSReferenceTime-R10-Ext ::= SEQUENCE { + ganssDayCycleNumber INTEGER(0..7) -- coding according to annex +} + +-- GANSS TOD-GSM Time association +GANSSTOD-GSMTimeAssociation ::= SEQUENCE { + bcchCarrier BCCHCarrier, -- BCCH carrier + bsic BSIC, -- BSIC + frameNumber FrameNumber, + timeSlot TimeSlot, + bitNumber BitNumber, + frameDrift FrameDrift OPTIONAL +} + +-- Frame drift +FrameDrift ::= INTEGER(-64 .. 63) + +-- GANSS Reference Location IE +GANSSRefLocation ::= SEQUENCE { + threeDLocation Ext-GeographicalInformation +} +``` + +``` + +-- GANSS Ionospheric Model IE +-- GANSS Ionospheric Model consists of NeQuick model parameters and storm flags +GANSSIonosphericModel ::= SEQUENCE { + ganssIonoModel GANSSIonosphereModel, + ganssIonoStormFlags GANSSIonStormFlags OPTIONAL, + ... +} + +-- GANSS ionosphere model. Coding according to Annex +GANSSIonosphereModel ::= SEQUENCE { + ai0 INTEGER (0 .. 2047), + ai1 INTEGER (-1024 .. 1023), + ai2 INTEGER (-8192 .. 8191) +} + +-- GANSS ionosphere storm flags +GANSSIonStormFlags ::= SEQUENCE { + ionoStormFlag1 INTEGER (0 .. 1), + ionoStormFlag2 INTEGER (0 .. 1), + ionoStormFlag3 INTEGER (0 .. 1), + ionoStormFlag4 INTEGER (0 .. 1), + ionoStormFlag5 INTEGER (0 .. 1) +} + +-- GANSS Additional Ionospheric Model IE +-- GANSS Additional Ionospheric Model consists of Klobuchar model parameters +GANSSAddIonosphericModel ::= SEQUENCE { + dataID BIT STRING (SIZE (2)), -- Coding according to Annex + ionoModel IonosphericModel +} + +-- GANSS Earth Orientation Parameters IE +GANSSEarthOrientParam ::= SEQUENCE { + teop INTEGER (0..65535), + pmX INTEGER (-1048576..1048575), + pmXdot INTEGER (-16384..16383), + pmY INTEGER (-1048576..1048575), + pmYdot INTEGER (-16384..16383), + deltaUT1 INTEGER (-1073741824..1073741823), + deltaUT1dot INTEGER (-262144..262143) +} + +-- GANSS GENERIC ASSISTANCE DATA ELEMENTS + +-- GANSS Time Model IE consists of time offset and first and second order parameters to relate GNSS +-- specific system time to selected time reference +SeqOfGANSSTimeModel ::= SEQUENCE (SIZE(1..7)) OF GANSSTimeModelElement + +GANSSTimeModelElement ::= SEQUENCE { + ganssTimeModelRefTime INTEGER(0 .. 65535), + tA0 TA0, + tA1 TA1 OPTIONAL, + tA2 TA2 OPTIONAL, + gnssTOID INTEGER (0 .. 7), -- coding according to annex + weekNumber INTEGER (0 .. 8191) OPTIONAL +} + +-- GANSS time model parameter A0 +TA0 ::= INTEGER (-2147483648 .. 2147483647) + +-- GANSS time model parameter A1 +TA1 ::= INTEGER (-8388608 .. 8388607) + +-- GANSS time model parameter A2 +TA2 ::= INTEGER (-64 .. 63) + +-- GANSS Time Model Rel-10 Extension: +SeqOfGANSSTimeModel-R10-Ext ::= SEQUENCE (SIZE(1..7)) OF GANSSTimeModelElement-R10-Ext + +GANSSTimeModelElement-R10-Ext ::= SEQUENCE { + gnssTOID INTEGER (0 .. 7), -- coding according to annex + deltaT INTEGER (-128..127) +} + +``` + +``` + +-- DGANSS Corrections IE +GANSSDiffCorrections ::= SEQUENCE { + dganssRefTime INTEGER (0 .. 119), -- DGANSS reference time + + -- N_SGN_TYPE can be read from number of elements of sgnTypeList + sgnTypeList SeqOfSgnTypeElement +} + +SeqOfSgnTypeElement ::= SEQUENCE (SIZE (1..3)) OF SgnTypeElement -- max three signals per GNSS + +-- DGANSS signal type element, once per GNSS signal type included in DGANSS +SgnTypeElement ::= SEQUENCE { + ganssSignalID GANSSSignalID, -- signal type identity + ganssStatusHealth INTEGER (0 .. 7), + -- N_SAT can be read from number of elements of dganssSgnList + dganssSgnList SeqOfDGANSSSgnElement +} + +GANSSSignalID ::= INTEGER (0 .. 7) -- Coding according to Annex +SeqOfDGANSSSgnElement ::= SEQUENCE (SIZE (1..16)) OF DGANSSSgnElement + +-- number of correction for signals +DGANSSSgnElement ::= SEQUENCE { + svID SVID, -- Satellite identity + + --- Sequence number for GANSS Navigation Model that matches the DGANSS correction set + iod INTEGER (0 .. 1023), + + -- User Differential Range Error + udre INTEGER (0..3), + + -- Pseudo Range Correction, range is + -- -655,04 - +655,04, + pseudoRangeCor INTEGER (-2047..2047), + + -- Pseudo Range Rate Correction, range is + -- -4,064 - +4,064, + rangeRateCor INTEGER (-127..127) +} + +SVID ::= INTEGER (0 .. 63) -- Coding according to Annex + +-- GANSS Navigation Model IE +GANSSNavModel ::= SEQUENCE { + nonBroadcastIndFlag INTEGER (0 .. 1), + ganssSatelliteList SeqOfGANSSSatelliteElement +} + +SeqOfGANSSSatelliteElement ::= SEQUENCE (SIZE(1..32)) OF GANSSSatelliteElement + +GANSSSatelliteElement ::= SEQUENCE { + svID SVID, + svHealth BIT STRING (SIZE(5)), -- Coding according to Annex + iod INTEGER (0 .. 1023), -- Coding according to Annex + ganssClockModel GANSSClockModel, + ganssOrbitModel GANSSOrbitModel, + .... + svHealthMSB BIT STRING (SIZE(1)) OPTIONAL, -- Coding according to Annex + iodMSB INTEGER (0 .. 1) OPTIONAL, -- Coding according to Annex + svHealthExt BIT STRING (SIZE(4)) OPTIONAL -- Coding according to Annex +} + +-- GANSS orbit model for the GNSS satellite according to the choice +GANSSOrbitModel ::= CHOICE { + keplerianSet NavModel-KeplerianSet, -- Model-1 + ... , + navKeplerianSet NavModel-NAVKeplerianSet, -- Model-2 + cnavKeplerianSet NavModel-CNAVKeplerianSet, -- Model-3 + glonassECEF NavModel-GLONASSECef, -- Model-4 + sbasECEF NavModel-SBASecf, -- Model-5 + bdsKeplerianSet-r12 NavModel-BDSKeplerianSet-r12 -- Model-6 +} + +``` + +``` +-- Navigation model in Keplerian parameters +NavModel-KeplerianSet ::= SEQUENCE { + keplerToe INTEGER (0 .. 16383), + keplerW INTEGER (-2147483648..2147483647), + keplerDeltaN INTEGER (-32768..32767), + keplerM0 INTEGER (-2147483648..2147483647), + keplerOmegaDot INTEGER (-8388608..8388607), + keplerE INTEGER (0..4294967295), + keplerIDot INTEGER (-8192..8191), + keplerAPowerHalf INTEGER (0..4294967295), + keplerI0 INTEGER (-2147483648..2147483647), + keplerOmega0 INTEGER (-2147483648..2147483647), + keplerCrs INTEGER (-32768..32767), + keplerCis INTEGER (-32768..32767), + keplerCus INTEGER (-32768..32767), + keplerCrc INTEGER (-32768..32767), + keplerCic INTEGER (-32768..32767), + keplerCuc INTEGER (-32768..32767) +} + +NavModel-NAVKeplerianSet ::= SEQUENCE { + navURA INTEGER (0..15), + navFitFlag INTEGER (0..1), + navToe INTEGER (0..37799), + navOmega INTEGER (-2147483648..2147483647), + navDeltaN INTEGER (-32768..32767), + navM0 INTEGER (-2147483648..2147483647), + navOmegaADot INTEGER (-8388608..8388607), + navE INTEGER (0..4294967295), + navIDot INTEGER (-8192..8191), + navAPowerHalf INTEGER (0..4294967295), + navI0 INTEGER (-2147483648..2147483647), + navOmegaA0 INTEGER (-2147483648..2147483647), + navCrs INTEGER (-32768..32767), + navCis INTEGER (-32768..32767), + navCus INTEGER (-32768..32767), + navCrc INTEGER (-32768..32767), + navCic INTEGER (-32768..32767), + navCuc INTEGER (-32768..32767) +} + +NavModel-CNAVKeplerianSet ::= SEQUENCE { + cnavTop INTEGER (0..2015), + cnavURAindex INTEGER (-16..15), + cnavDeltaA INTEGER (-33554432..33554431), + cnavAdot INTEGER (-16777216..16777215), + cnavDeltaNo INTEGER (-65536..65535), + cnavDeltaNoDot INTEGER (-4194304..4194303), + cnavMo INTEGER (-4294967296..4294967295), + cnavE INTEGER (0..8589934591), + cnavOmega INTEGER (-4294967296..4294967295), + cnavOMEGA0 INTEGER (-4294967296..4294967295), + cnavDeltaOmegaDot INTEGER (-65536..65535), + cnavIo INTEGER (-4294967296..4294967295), + cnavIoDot INTEGER (-16384..16383), + cnavCis INTEGER (-32768..32767), + cnavCic INTEGER (-32768..32767), + cnavCrs INTEGER (-8388608..8388607), + cnavCrc INTEGER (-8388608..8388607), + cnavCus INTEGER (-1048576..1048575), + cnavCuc INTEGER (-1048576..1048575) +} +``` + +``` + +NavModel-GLONASSSecef ::= SEQUENCE { + gloEn INTEGER (0..31), + gloP1 BIT STRING (SIZE(2)), + gloP2 BOOLEAN, + gloM INTEGER (0..3), + gloX INTEGER (-67108864..67108863), + gloXdot INTEGER (-8388608..8388607), + gloXdotdot INTEGER (-16..15), + gloY INTEGER (-67108864..67108863), + gloYdot INTEGER (-8388608..8388607), + gloYdotdot INTEGER (-16..15), + gloZ INTEGER (-67108864..67108863), + gloZdot INTEGER (-8388608..8388607), + gloZdotdot INTEGER (-16..15) +} + +NavModel-SBASSecef ::= SEQUENCE { + sbasTo INTEGER (0..5399) OPTIONAL, + sbasAccuracy BIT STRING (SIZE(4)), + sbasXg INTEGER (-536870912..536870911), + sbasYg INTEGER (-536870912..536870911), + sbasZg INTEGER (-16777216..16777215), + sbasXgDot INTEGER (-65536..65535), + sbasYgDot INTEGER (-65536..65535), + sbasZgDot INTEGER (-131072..131071), + sbasXgDotDot INTEGER (-512..511), + sbasYgDotDot INTEGER (-512..511), + sbasZgDotDot INTEGER (-512..511) +} + +NavModel-BDSKeplerianSet-r12 ::= SEQUENCE { + bdsAODE-r12 INTEGER (0..31), + bdsURAI-r12 INTEGER (0..15), + bdsToe-r12 INTEGER (0..131071), + bdsAPowerHalf-r12 INTEGER (0..4294967295), + bdsE-r12 INTEGER (0..4294967295), + bdsW-r12 INTEGER (-2147483648..2147483647), + bdsDeltaN-r12 INTEGER (-32768..32767), + bdsM0-r12 INTEGER (-2147483648..2147483647), + bdsOmega0-r12 INTEGER (-2147483648..2147483647), + bdsOmegaDot-r12 INTEGER (-8388608..8388607), + bdsI0-r12 INTEGER (-2147483648..2147483647), + bdsIDot-r12 INTEGER (-8192..8191), + bdsCuc-r12 INTEGER (-131072..131071), + bdsCus-r12 INTEGER (-131072..131071), + bdsCrc-r12 INTEGER (-131072..131071), + bdsCrs-r12 INTEGER (-131072..131071), + bdsCic-r12 INTEGER (-131072..131071), + bdsCis-r12 INTEGER (-131072..131071) +} + +-- GNSS clock model for the GNSS satellite according to the choice +GANSSClockModel ::= CHOICE { + standardClockModelList SeqOfStandardClockModelElement, -- Model-1 + ... , + navClockModel NAVClockModel, -- Model-2 + cnavClockModel CNAVClockModel, -- Model-3 + glonassClockModel GLONASSClockModel, -- Model-4 + sbasClockModel SBASClockModel , -- Model-5 + bdsClockModel-r12 BDSClockModel-r12 -- Model-6 +} + +SeqOfStandardClockModelElement ::= SEQUENCE (SIZE(1..2)) OF StandardClockModelElement + +StandardClockModelElement ::= SEQUENCE { + stanClockToc INTEGER (0 .. 16383), + stanClockAF2 INTEGER (-32 .. 31), + stanClockAF1 INTEGER (-1048576 .. 1048575), + stanClockAF0 INTEGER (-1073741824 .. 1073741823), + stanClockTgd INTEGER (-512 .. 511) OPTIONAL, + stanModelID INTEGER (0 .. 1) OPTIONAL, + ... +} + +``` + +``` + +NAVclockModel ::= SEQUENCE { + navToc INTEGER (0.. 37799), + navaf2 INTEGER (-128..127), + navaf1 INTEGER (-32768..32767), + navaf0 INTEGER (-2097152..2097151), + navTgd INTEGER (-128..127) +} + +CNAVclockModel ::= SEQUENCE { + cnavToc INTEGER (0..2015), + cnavTop INTEGER (0..2015), + cnavURA0 INTEGER (-16..15), + cnavURA1 INTEGER (0..7), + cnavURA2 INTEGER (0..7), + cnavaf2 INTEGER (-512..511), + cnavAf1 INTEGER (-524288..524287), + cnavAf0 INTEGER (-33554432..33554431), + cnavTgd INTEGER (-4096..4095), + cnavISC11cp INTEGER (-4096..4095) OPTIONAL, + cnavISC11cd INTEGER (-4096..4095) OPTIONAL, + cnavISC11ca INTEGER (-4096..4095) OPTIONAL, + cnavISC12c INTEGER (-4096..4095) OPTIONAL, + cnavISC15i5 INTEGER (-4096..4095) OPTIONAL, + cnavISC15q5 INTEGER (-4096..4095) OPTIONAL +} + +GLONASSclockModel ::= SEQUENCE { + gloTau INTEGER (-2097152..2097151), + gloGamma INTEGER (-1024..1023), + gloDeltaTau INTEGER (-16..15) OPTIONAL +} + +SBASclockModel ::= SEQUENCE { + sbasTo INTEGER (0..5399), + sbasAgfo INTEGER (-2048..2047), + sbasAgf1 INTEGER (-128..127) +} + +BDSclockModel-r12 ::= SEQUENCE { + bdsAODC-r12 INTEGER (0..31), + bdsToc-r12 INTEGER (0..131071), + bdsA0-r12 INTEGER (-8388608..8388607), + bdsA1-r12 INTEGER (-2097152..2097151), + bdsA2-r12 INTEGER (-1024..1023), + bdsTgd1-r12 INTEGER (-512..511) +} + +-- GANSS Real-Time Integrity IE +GANSSRealTimeIntegrity ::= SEQUENCE { + -- list of satellites with bad signals + -- NBS can be read from number of elements in SeqOf-BadSignalSet + ganssBadSignalList SeqOfBadSignalElement +} + +SeqOfBadSignalElement ::= SEQUENCE (SIZE(1..16)) OF BadSignalElement + +BadSignalElement ::= SEQUENCE { + badSVID SVID, + badSignalID GANSSSignals OPTIONAL -- Coding according to Annex +} + +-- GANSS Data Bit Assistance IE +GANSSDataBitAssist ::= SEQUENCE { + ganssTOD INTEGER (0 .. 59), + -- N_SAT can be read from number of elements in SeqOfGanssDataBitsElement + ganssDataBitsSatList SeqOfGanssDataBitsElement, + ... +} + +SeqOfGanssDataBitsElement ::= SEQUENCE (SIZE(1 .. 32)) OF GanssDataBitsElement + +GanssDataBitsElement ::= SEQUENCE { + sVID SVID, + -- N_SGN can be read from number of elements in Seq-OfGANSSDataBitsSgn + ganssDataBitsSgnList Seq-OfGANSSDataBitsSgn, + ... +} + +``` + +``` + +Seq-Of-GANSSDataBitsSgn ::= SEQUENCE (SIZE(1..8)) OF GANSSDataBitsSgnElement + +GANSSDataBitsSgnElement ::= SEQUENCE { + ganssSignalType GANSSSignalID, + -- N_BIT can be read from number of elements in SeqOf-DataBits + ganssDataBits SeqOf-GANSSDataBits, + ... +} + +SeqOf-GANSSDataBits ::= SEQUENCE (SIZE(1 .. 1024)) OF GANSSDataBit +GANSSDataBit ::= INTEGER(0 .. 1) + +-- GANSS Reference Measurement Assistance IE +-- Code and Doppler assistance from the network. +GANSSRefMeasurementAssist ::= SEQUENCE { + ganssSignalID GANSSSignalID, -- Coding according to Annex + ganssRefMeasAssistList SeqOfGANSSRefMeasurementElement +} + +SeqOfGANSSRefMeasurementElement ::= SEQUENCE (SIZE(1 .. 16)) OF GANSSRefMeasurementElement + +GANSSRefMeasurementElement ::= SEQUENCE { + svID SVID, + -- Doppler 0th order term, + -- -1024 m/s to 1023,5 m/s with 0,5 m/s resolution) + doppler0 INTEGER (-2048 .. 2047), -- Coding according to Annex + additionalDoppler AdditionalDopplerFields OPTIONAL, + codePhase INTEGER (0 .. 1022), -- Code Phase in ms + intCodePhase INTEGER (0 .. 127), -- Integer Code Phase in ms + codePhaseSearchWindow INTEGER (0 .. 31), -- Code Phase Search Window, see Annex + additionalAngle AdditionalAngleFields OPTIONAL, + ... + codePhase1023 BOOLEAN OPTIONAL +} + +AdditionalDopplerFields ::= SEQUENCE { + -- Doppler 1st order term, -0,2 - +0,1 m/s2 + -- ( = -42 + (0 to 63) with 1/210 m/s2 resolution) + doppler1 INTEGER (0..63), + dopplerUncertainty INTEGER (0..4) +} + +-- GANSS Reference Measurement Rel-10 Extension: +-- GANSSRefMeasurementAssist-R10-Ext shall contain the same number of elements as the +-- SeqOfGANSSRefMeasurementElement included in GANSSRefMeasurementAssist IE +GANSSRefMeasurementAssist-R10-Ext ::= SEQUENCE (SIZE(1 .. 16)) OF + GANSSRefMeasurement-R10-Ext-Element + +GANSSRefMeasurement-R10-Ext-Element ::= SEQUENCE { + svID SVID, + azimuthLSB INTEGER(0..15), + elevationLSB INTEGER(0..15) +} + +-- GANSS Reference Measurement Rel-12 Extension: +GANSSRefMeasurementAssist-R12-Ext ::= SEQUENCE { + ganssSignalID GANSSSignalID, + confidence INTEGER (0..100) OPTIONAL, + ganssRefMeasAssistList SeqOfGANSSRefMeasurementElement-R12 OPTIONAL +} + +SeqOfGANSSRefMeasurementElement-R12 ::= SEQUENCE (SIZE(1 .. 16)) OF + GANSSRefMeasurement-R12-Ext-Element + +GANSSRefMeasurement-R12-Ext-Element ::= SEQUENCE { + svID SVID, + dopplerUncertaintyExt ENUMERATED { d60, + d80, + d100, + d120, + noInformation, ...} +} + +``` + +``` + +-- GANSS Almanac Model IE +GANSSAlmanacModel ::= SEQUENCE { + weekNumber INTEGER (0 .. 255), + toa INTEGER (0 .. 255) OPTIONAL, + ioda INTEGER (0 .. 3) OPTIONAL, + ganssAlmanacList SeqOfGANSSAlmanacElement +} + +SeqOfGANSSAlmanacElement ::= SEQUENCE (SIZE(1 .. 36)) OF GANSSAlmanacElement + +-- GANSS Almanac Model +GANSSAlmanacElement ::= CHOICE { + keplerianAlmanacSet Almanac-KeplerianSet, -- Model-1 + ..., + keplerianNAVAlmanac Almanac-NAVKeplerianSet, -- Model-2 + keplerianReducedAlmanac Almanac-ReducedKeplerianSet, -- Model-3 + keplerianMidiAlmanac Almanac-MidiAlmanacSet, -- Model-4 + keplerianGLONASS Almanac-GlonassAlmanacSet, -- Model-5 + ecefSBASAlmanac Almanac-ECEFsbasAlmanacSet, -- Model-6 + keplerianBDSAlmanac-r12 Almanac-BDSAlmanacSet-r12 -- Model-7 +} + +-- Almanac parameters according to Keplerian parameters +Almanac-KeplerianSet ::= SEQUENCE { + sVID SVID, + kepAlmanacE INTEGER (0 .. 2047), + kepAlmanacDeltaI INTEGER (-1024 .. 1023), + kepAlmanacOmegaDot INTEGER (-1024 .. 1023), + kepSVStatusINAV BIT STRING (SIZE (4)), + kepSVStatusFNAV BIT STRING (SIZE (2)) OPTIONAL, + kepAlmanacAPowerHalf INTEGER (-4096..4095), + kepAlmanacOmega0 INTEGER (-32768 .. 32767), + kepAlmanacW INTEGER (-32768 .. 32767), + kepAlmanacM0 INTEGER (-32768 .. 32767), + kepAlmanacAF0 INTEGER (-32768..32767), + kepAlmanacAF1 INTEGER (-4096..4095) +} + +Almanac-NAVKeplerianSet ::= SEQUENCE { + sVID SVID, + navAlmE INTEGER (0..65535), + navAlmDeltaI INTEGER (-32768..32767), + navAlmOMEGADOT INTEGER (-32768..32767), + navAlmSVHealth INTEGER (0..255), + navAlmSqrtA INTEGER (0..16777215), + navAlmOMEGAo INTEGER (-8388608..8388607), + navAlmOmega INTEGER (-8388608..8388607), + navAlmMo INTEGER (-8388608..8388607), + navAlmaf0 INTEGER (-1024..1023), + navAlmaf1 INTEGER (-1024..1023) +} + +Almanac-ReducedKeplerianSet ::= SEQUENCE { + sVID SVID, + redAlmDeltaA INTEGER (-128..127), + redAlmOmega0 INTEGER (-64..63), + redAlmPhi0 INTEGER (-64..63), + redAlmL1Health BOOLEAN, + redAlmL2Health BOOLEAN, + redAlmL5Health BOOLEAN +} + +``` + +``` + +Almanac-MidiAlmanacSet ::= SEQUENCE { + svID SVID, + midiAlmE INTEGER (0..2047), + midiAlmDeltaI INTEGER (-1024..1023), + midiAlmOmegaDot INTEGER (-1024..1023), + midiAlmSqrtA INTEGER (0..131071), + midiAlmOmega0 INTEGER (-32768..32767), + midiAlmOmega INTEGER (-32768..32767), + midiAlmMo INTEGER (-32768..32767), + midiAlmaf0 INTEGER (-1024..1023), + midiAlmaf1 INTEGER (-512..511), + midiAlmL1Health BOOLEAN, + midiAlmL2Health BOOLEAN, + midiAlmL5Health BOOLEAN +} + +Almanac-GlonassAlmanacSet ::= SEQUENCE { + gloAlmNA INTEGER (1..1461), + gloAlmnnA INTEGER (1..24), + gloAlmHA INTEGER (0..31), + gloAlmLambdaA INTEGER (-1048576..1048575), + gloAlmtLambdaA INTEGER (0..2097151), + gloAlmDeltaIa INTEGER (-131072..131071), + gloAlmDeltaTA INTEGER (-2097152..2097151), + gloAlmDeltaTdotA INTEGER (-64..63), + gloAlmEpsilonA INTEGER (0..32767), + gloAlmOmegaA INTEGER (-32768..32767), + gloAlmTauA INTEGER (-512..511), + gloAlmCA INTEGER (0..1), + gloAlmMA BIT STRING (SIZE(2)) OPTIONAL +} + +Almanac-ECEFsbasAlmanacSet ::= SEQUENCE { + sbasAlmDataID INTEGER (0..3), + svID SVID, + sbasAlmHealth BIT STRING (SIZE(8)), + sbasAlmXg INTEGER (-16384..16383), + sbasAlmYg INTEGER (-16384..16383), + sbasAlmZg INTEGER (-256..255), + sbasAlmXgdot INTEGER (-4..3), + sbasAlmYgDot INTEGER (-4..3), + sbasAlmZgDot INTEGER (-8..7), + sbasAlmTo INTEGER (0..2047) +} + +Almanac-BDSAlmanacSet-r12 ::= SEQUENCE { + svID SVID, + --This field may be present if the toa is not the same for all SVs; otherwise it is not present + and the toa is provided in GANSSAlmanacModel + bdsAlmToa-r12 INTEGER (0..255) OPTIONAL, + bdsAlmSqrtA-r12 INTEGER (0..16777215), + bdsAlmE-r12 INTEGER (0..131071), + bdsAlmW-r12 INTEGER (-8388608..8388607), + bdsAlmM0-r12 INTEGER (-8388608..8388607), + bdsAlmOmega0-r12 INTEGER (-8388608..8388607), + bdsAlmOmegaDot-r12 INTEGER (-65536..65535), + bdsAlmDeltaI-r12 INTEGER (-32768..32767), + bdsAlmA0-r12 INTEGER (-1024..1023), + bdsAlmA1-r12 INTEGER (-1024..1023), + --This field is mandatory present if SV-ID is between 0 and 29; otherwise it is not present. + bdsSvHealth-r12 BIT STRING (SIZE(9)) OPTIONAL +} + +-- GANSS Almanac Model Rel-10 Extension +GANSSAlmanacModel-R10-Ext ::= SEQUENCE { + completeAlmanacProvided BOOLEAN -- TRUE means that complete Almanac is provided +} + +-- GANSS Almanac Model Rel-12 Extension +GANSSAlmanacModel-R12-Ext ::= SEQUENCE { + -- Either toa in GANSSAlmanacModel or toa-ext shall be present if GANSS-ID indicates Galileo + toa-ext INTEGER (256..1023) OPTIONAL, + -- Either ioda in GANSSAlmanacModel or ioda-ext shall be present if GANSS-ID indicates Galileo + ioda-ext INTEGER (4..15) OPTIONAL +} + +``` + +``` + +-- GANSS Universal Time Coordinate Model (Model-1) +GANSSUTCModel ::= SEQUENCE { + ganssUtcAl INTEGER (-8388608..8388607), + ganssUtcA0 INTEGER (-2147483648..2147483647), + ganssUtcTot INTEGER (0..255), + ganssUtcWNt INTEGER (0..255), + ganssUtcDeltaTls INTEGER (-128..127), + ganssUtcWNlsf INTEGER (0..255), + ganssUtcDN INTEGER (-128..127), + ganssUtcDeltaTlsf INTEGER (-128..127) +} + +--GANSS Ephemeris Extension +GANSSEphemerisExtension ::= SEQUENCE { + ganssEphemerisHeader GANSSEphemerisExtensionHeader OPTIONAL, + ganssReferenceSet SeqOfGANSSRefOrbit OPTIONAL, + ganssephemerisDeltasMatrix GANSSEphemerisDeltaMatrix OPTIONAL, + ... +} + +-- The ganssEphemerisHeader and the ganssReferenceSet are mandatory only once in the delivery of the +-- GANSS Ephemeris Extension. The ganssReferenceSet shall include all healthy satellite vehicles +-- at the time of message construction. + +GANSSEphemerisExtensionHeader ::= SEQUENCE { + timeAtEstimation GANSSEphemerisExtensionTime, + validityPeriod INTEGER(1..8), + -- The validity period, represented in hours, is the validity period of each individual ephemeris + -- delta payload + ephemerisExtensionDuration INTEGER(1..512), + -- If the ephemerisExtensionDuration does not match the request duration made by the MS, the MS + -- should regard the provided ephemerisExtensionDuration as the limit of the SMLC ephemeris + -- extension capability at this time. + ... +} + +GANSSEphemerisExtensionTime ::= SEQUENCE { + ganssEphExtDay INTEGER(0..8191), + ganssEphExtTOD GANSS TOD, + ... +} + +-- Reference Nav Model for Ephemeris Extension +ReferenceNavModel ::= SEQUENCE { + keplerToe INTEGER (0..37799), + keplerW INTEGER (-2147483648..2147483647), + keplerDeltaN INTEGER (-32768..32767), + keplerM0 INTEGER (-2147483648..2147483647), + keplerOmegaDot INTEGER (-8388608..8388607), + keplerE INTEGER (0..4294967295), + keplerIDot INTEGER (-8192..8191), + keplerAPowerHalf INTEGER (0.. 4294967295), + keplerI0 INTEGER (-2147483648..2147483647), + keplerOmega0 INTEGER (-2147483648..2147483647), + keplerCrs INTEGER (-32768..32767), + keplerCis INTEGER (-32768..32767), + keplerCus INTEGER (-32768..32767), + keplerCrc INTEGER (-32768..32767), + keplerCic INTEGER (-32768..32767), + keplerCuc INTEGER (-32768..32767) +} + +SeqOfGANSSRefOrbit ::= SEQUENCE (SIZE(1..32)) OF GANSSReferenceOrbit +--The number of reference orbits can be read from number of elements in this sequence + +GANSSReferenceOrbit ::= SEQUENCE { + svID SVID, + ganssOrbitModel ReferenceNavModel, + ganssClockModel GANSSClockModel, + ... +} + +GANSSEphemerisDeltaMatrix ::= SEQUENCE (SIZE(1 .. 128)) OF GANSSEphemerisDeltaEpoch + +``` + +``` + +GANSS Ephemeris Delta Epoch ::= SEQUENCE { + ganssDeltaEpochHeader GANSS Delta Epoch Header OPTIONAL, + ganssDeltaElementList GANSS Delta Element List, + ... +} +-- Each GANSS Delta Epoch element contains a header and the delta values for a particular time window +-- for all PRN's. + +GANSS Delta Epoch Header ::= SEQUENCE { + validityPeriod INTEGER(1..8) OPTIONAL, + ephemerisDeltaSizes GANSS Ephemeris Delta Bit Sizes OPTIONAL, + ephemerisDeltaScales GANSS Ephemeris Delta Scales OPTIONAL, + ... +} +-- In each of the GANSS Delta Epochs, if the optional element, validityPeriod is not included, the +-- value in GANSS Ephemeris Extension Header shall be used. If the optional elements +-- ephemerisDeltaSizes or ephemerisDeltaScales are not included, then the default ephemeris delta +-- sizes and scales shall be used. The default sizes and scales are found in the annex in the +-- table 55.11. + +GANSS Delta Element List ::= SEQUENCE (SIZE(1 .. 32)) OF OCTET STRING(SIZE (1..49)) +-- Each octet string element in GANSS Delta Element List corresponds to one PRN within one epoch + +-- Table 55.11 of the annex shows the organization of the delta ephemeris octet string. +-- Decoding of each of the octet strings is accomplished by consulting the ephemerisDeltaSizes +-- table to learn the length and order of each of the parameters in the ephemerisDelta payload. + +-- Post decode scaling is accomplished by consulting the ephemerisDeltaScales table to learn the +-- scale factors to apply to the terms in the delta ephemeris. + +-- Ephemeris Delta Bit Sizes. + +GANSS Ephemeris Delta Bit Sizes ::= SEQUENCE { + +-- This structure defines the order and sizes of the fields in the GANSS Delta Epoch octet string +-- seqNum and svID are the first two elements of each GANSS Ephemeris Delta Element Structure +-- seqNum is always 7 bits, and svID is always 6 bits long and are thus not included in +-- the GANSS Ephemeris Delta Bit Sizes table. The value of seqNum indicates the GANSS Delta Epoch number + +-- The Ephemeris delta element payload mimics the bitsize table, but also includes the svID and +-- seqNum as the first two elements (in that order), in each block. + + bitsize-delta-omega INTEGER(1..32), + bitsize-delta-deltaN INTEGER(1..16), + bitsize-delta-m0 INTEGER(1..32), + bitsize-delta-omegadot INTEGER(1..24), + bitsize-delta-e INTEGER(1..32), + bitsize-delta-idot INTEGER(1..14), + bitsize-delta-sqrtA INTEGER(1..32), + bitsize-delta-i0 INTEGER(1..32), + bitsize-delta-omega0 INTEGER(1..32), + bitsize-delta-crs INTEGER(1..16), + bitsize-delta-cis INTEGER(1..16), + bitsize-delta-cus INTEGER(1..16), + bitsize-delta-crc INTEGER(1..16), + bitsize-delta-cic INTEGER(1..16), + bitsize-delta-cuc INTEGER(1..16), + bitsize-delta-tgd1 INTEGER(1..10), + bitsize-delta-tgd2 INTEGER(1..10), + ... +} + +``` + +``` + +GANSSEphemerisDeltaScales ::= SEQUENCE { + scale-delta-omega INTEGER(-16..15), + scale-delta-deltaN INTEGER(-16..15), + scale-delta-m0 INTEGER(-16..15), + scale-delta-omegadot INTEGER(-16..15), + scale-delta-e INTEGER(-16..15), + scale-delta-idot INTEGER(-16..15), + scale-delta-sqrtA INTEGER(-16..15), + scale-delta-i0 INTEGER(-16..15), + scale-delta-omega0 INTEGER(-16..15), + scale-delta-crs INTEGER(-16..15), + scale-delta-cis INTEGER(-16..15), + scale-delta-cus INTEGER(-16..15), + scale-delta-crc INTEGER(-16..15), + scale-delta-cic INTEGER(-16..15), + scale-delta-cuc INTEGER(-16..15), + scale-delta-tgd1 INTEGER(-16..15), + scale-delta-tgd2 INTEGER(-16..15), + ... +} + +-- GANSS Ephemeris Extension Check +GANSSEphemerisExtensionCheck ::= SEQUENCE { + ganssBeginTime GANSSEphemerisExtensionTime, + ganssEndTime GANSSEphemerisExtensionTime, + ganssSatEventsInfo GANSSSatEventsInfo, + ... +} + +GANSSSatEventsInfo ::= SEQUENCE { + eventOccured BIT STRING (SIZE (64)), + futureEventNoted BIT STRING (SIZE (64)), + ... +} + +-- If a bit is clear in the eventOccured field it indicates that no known errors have occured +-- between the current time and the ganssBeginTime nor is a maneuver planned for the next sixty +-- minutes. +-- If a bit is set in the futureEventNoted field it indicates that a maneuver is planned during the +-- time period between current time plus sixty minutes and the ganssEndTime +-- GANSS Additional Universal Time Coordinate Model +GANSSEAddUTCModel ::= CHOICE { + utcModel2 UTCmodelSet2, + utcModel3 UTCmodelSet3, + utcModel4 UTCmodelSet4, + ... , + utcModel5-r12 UTCmodelSet5-r12 +} + +UTCmodelSet2 ::= SEQUENCE { + utcA0 INTEGER (-32768..32767), + utcA1 INTEGER (-4096.. 4095), + utcA2 INTEGER (-64..63), + utcDeltaTls INTEGER (-128.. 127), + utcTot INTEGER (0..65535), + utcWNot INTEGER (0..8191), + utcWNlsf INTEGER (0..255), + utcDN BIT STRING (SIZE(4)), + utcDeltaTlsf INTEGER (-128..127) +} + +UTCmodelSet3 ::= SEQUENCE { + nA INTEGER (1..1461), + tauC INTEGER (-2147483648..2147483647), + b1 INTEGER (-1024..1023) OPTIONAL, + b2 INTEGER (-512..511) OPTIONAL, + kp BIT STRING (SIZE(2)) OPTIONAL +} + +``` + +``` + +UTCmodelSet4 ::= SEQUENCE { + utcAlwnt INTEGER (-8388608..8388607), + utcA0wnt INTEGER (-2147483648..2147483647), + utcTot INTEGER (0..255), + utcWNt INTEGER (0..255), + utcDeltaTls INTEGER (-128..127), + utcWNlsf INTEGER (0..255), + utcDN INTEGER (-128..127), + utcDeltaTlsf INTEGER (-128..127), + utcStandardID INTEGER (0..7) -- coding according to annex +} + +UTCmodelSet5-r12 ::= SEQUENCE { + utcA0-r12 INTEGER (-2147483648..2147483647), + utcAl-r12 INTEGER (-8388608..8388607), + utcDeltaTls-r12 INTEGER (-128..127), + utcWNlsf-r12 INTEGER (0..255), + utcDN-r12 INTEGER (0..255), + utcDeltaTlsf-r12 INTEGER (-128..127) +} + +-- GANSS Auxiliary Information +GANSSAuxiliaryInformation ::= CHOICE{ + ganssID1 GANSS-ID1, -- This choice may only be present if GANSS ID indicates Modernized GPS + ganssID3 GANSS-ID3, -- This choice may only be present if GANSS ID indicates GLONASS + ... +} + +GANSS-ID1 ::= SEQUENCE (SIZE(1..64)) OF GANSS-ID1-element + +GANSS-ID1-element ::= SEQUENCE { + svID SVID, + signalsAvailable GANSSSignals, + ... +} + +GANSS-ID3 ::= SEQUENCE (SIZE(1..64)) OF GANSS-ID3-element + +GANSS-ID3-element ::= SEQUENCE { + svID SVID, + signalsAvailable GANSSSignals, + channelNumber INTEGER (-7..13), + ... +} + +-- DGANSS Corrections Validity Period: +-- This element may only be included if GANSSDiffCorrections IE is included in +-- GANSSGenericAssistDataElement element. +-- GANSSDiffCorrectionsValidityPeriod shall contain the same number of elements as the +-- SeqOfSgnTypeElement included in GANSSDiffCorrections IE +GANSSDiffCorrectionsValidityPeriod ::= SEQUENCE (SIZE (1..3)) OF DGANSSExtensionSgnTypeElement + +DGANSSExtensionSgnTypeElement ::= SEQUENCE { + ganssSignalID GANSSSignalID, -- signal type identity + dganssExtensionSgnList SeqOfDGANSSExtensionSgnElement +} + +-- SeqOfDGANSSExtensionSgnElement shall contain the same number of elements as the +-- SeqOfDGANSSSgnElement included in GANSSDiffCorrections IE +SeqOfDGANSSExtensionSgnElement ::= SEQUENCE (SIZE (1..16)) OF DGANSSExtensionSgnElement + +DGANSSExtensionSgnElement ::= SEQUENCE { + svID SVID, -- Satellite identity + udreGrowthRate INTEGER(0..7), -- coding according to annex + udreValidityTime INTEGER(0..7), -- coding according to annex + ... +} + +--Required Measurement Request Response Time, range is 1 to 128 seconds. +RequiredResponseTime ::= INTEGER (1..128) + +-- Control header for additional GPS assistance data +Add-GPS-AssistData ::= SEQUENCE { + add-GPS-controlHeader Add-GPS-ControlHeader +} + +``` + +``` + +Add-GPS-ControlHeader ::= SEQUENCE { + gpsEphemerisExtension GPSEphemerisExtension OPTIONAL, + gpsEphemerisExtensionCheck GPSEphemerisExtensionCheck OPTIONAL, + ... / + dgpsCorrectionsValidityPeriod DGPSCorrectionsValidityPeriod OPTIONAL, + -- If ReferenceTime is included in ControlHeader, GPSReferenceTime-R10-Ext + -- shall also be included. + gpsReferenceTime-R10-Ext GPSReferenceTime-R10-Ext OPTIONAL, + -- If AcquisAssist is included in ControlHeader, GPSAcquisAssist-R10-Ext + -- shall also be included. + gpsAcquisAssist-R10-Ext GPSAcquisAssist-R10-Ext OPTIONAL, + -- If Almanac is included in ControlHeader, GPSAlmanac-R10-Ext + -- shall also be included. + gpsAlmanac-R10-Ext GPSAlmanac-R10-Ext OPTIONAL, + gpsAcquisAssist-R12-Ext GPSAcquisAssist-R12-Ext OPTIONAL +} + +GPSClockModel ::= SEQUENCE { + af2 INTEGER (-128..127), + af1 INTEGER (-32768..32767), + af0 INTEGER (-2097152..2097151), + tgd INTEGER (-128..127) +} + +--GPS Ephemeris Extension +GPSEphemerisExtension ::= SEQUENCE { + gpsEphemerisHeader GPSEphemerisExtensionHeader OPTIONAL, + gpsReferenceSet SeqOfGPSRefOrbit OPTIONAL, + gpsephemerisDeltaMatrix GPSEphemerisDeltaMatrix OPTIONAL, + ... +} + +-- The gpsEphemerisHeader and the gpsReferenceSet are mandatory only once in the delivery of the +-- GPS Ephemeris Extension. The gpsReferenceSet shall include all healthy satellite vehicles at the +-- time of message construction + +-- The SMLC is required to deliver the gpsReferenceSet for all healthy satellite vehicles +-- at the time of message construction. + +GPSEphemerisExtensionHeader ::= SEQUENCE { + timeOfEstimation GPSEphemerisExtensionTime, + validityPeriod INTEGER(1..8), + -- The validity period, represented in hours is the validity period of each individual ephemeris + -- delta payload + ephemerisExtensionDuration INTEGER(1..512), + -- If the ephemerisExtensionDuration does not match the request duration made by the MS, the MS + -- should regard the provided ephemerisExtensionDuration as the limit of the SMLC ephemeris + -- extension capability at this time. + ... +} + +GPSEphemerisExtensionTime ::= SEQUENCE { + gpsWeek GPSWeek, + gpsTOW INTEGER (0..604799), + ... +} + +SeqOfGPSRefOrbit ::= SEQUENCE (SIZE(1..32)) OF GPSReferenceOrbit +--The number of reference orbits can be read from number of elements in this sequence + +GPSReferenceOrbit ::= SEQUENCE { + svID SVID, + gpsOrbitModel ReferenceNavModel, + gpsClockModel GPSClockModel, + ... +} + +GPSEphemerisDeltaMatrix ::= SEQUENCE (SIZE(1 .. 128)) OF GPSEphemerisDeltaEpoch + +GPSEphemerisDeltaEpoch ::= SEQUENCE { + gpsDeltaEpochHeader GPSDeltaEpochHeader OPTIONAL, + gpsDeltaElementList GPSDeltaElementList, + ... +} + +-- Each GPSDeltaEpoch element contains a header and the delta values for a particular time window +-- for all PRN's. + +``` + +``` + +GPSDeltaEpochHeader ::= SEQUENCE { + validityPeriod INTEGER(1..8) OPTIONAL, + ephemerisDeltaSizes GPSEphemerisDeltaBitSizes OPTIONAL, + ephemerisDeltaScales GPSEphemerisDeltaScales OPTIONAL, + ... +} + +-- In each of the GPSDeltaEpochs, if the optional element validityPeriod is not included, +-- the value in GPSEphemerisExtensionHeader shall be used. if the optional elements +-- ephemerisDeltaSizes or ephemerisDeltaScales are not included, then the default ephemeris delta +-- sizes and scales shall be used. The default sizes and scales are found in the annex in section +-- A.29.m + +GPSDeltaElementList ::= SEQUENCE (SIZE(1 .. 32)) OF OCTET STRING(SIZE (1..47)) + +-- Each octet string element in GPSDeltaElementList corresponds to one PRN within one epoch + +-- Table A.29.m of the annex shows the organization of the delta ephemeris octet string. +-- Decoding of each of the octet strings is accomplished by consulting the ephemerisDeltaSizes +-- table to learn the length and order of each of the parameters in the ephemerisDelta payload + +-- Post decode scaling is accomplished by consulting the ephemerisDeltaScales table to learn the. +-- scale factors to apply to the terms in the delta ephemeris + +-- Ephemeris Delta Bit Sizes. + +GPSEphemerisDeltaBitSizes ::= SEQUENCE { + +-- This structure defines the order and sizes of the fields in the GPSsDeltaEpoch octet string +-- seqNum and svID are the first two elements of each GPS Ephemeris Delta Element Structure +-- seqNum is always 7 bits, and svID is always 5 bits long and are thus not included in +-- the GPSEphemerisDeltaBitSizes table. seqNum indicates the GPSDeltaEpoch number. + +-- The Ephemeris delta element payload mimics the bitsize table, but also includes the svID and +-- seqNum as the first two elements (in that order), in each block. + + bitsize-delta-omega INTEGER(1..32), + bitsize-delta-deltaN INTEGER(1..16), + bitsize-delta-m0 INTEGER(1..32), + bitsize-delta-omegadot INTEGER(1..24), + bitsize-delta-e INTEGER(1..32), + bitsize-delta-idot INTEGER(1..14), + bitsize-delta-sqrtA INTEGER(1..32), + bitsize-delta-i0 INTEGER(1..32), + bitsize-delta-omega0 INTEGER(1..32), + bitsize-delta-crs INTEGER(1..16), + bitsize-delta-cis INTEGER(1..16), + bitsize-delta-cus INTEGER(1..16), + bitsize-delta-crc INTEGER(1..16), + bitsize-delta-cic INTEGER(1..16), + bitsize-delta-cuc INTEGER(1..16), + bitsize-delta-tgd INTEGER(1..10), + ... +} + +GPSEphemerisDeltaScales ::= SEQUENCE { + scale-delta-omega INTEGER(-16..15), + scale-delta-deltaN INTEGER(-16..15), + scale-delta-m0 INTEGER(-16..15), + scale-delta-omegadot INTEGER(-16..15), + scale-delta-e INTEGER(-16..15), + scale-delta-idot INTEGER(-16..15), + scale-delta-sqrtA INTEGER(-16..15), + scale-delta-i0 INTEGER(-16..15), + scale-delta-omega0 INTEGER(-16..15), + scale-delta-crs INTEGER(-16..15), + scale-delta-cis INTEGER(-16..15), + scale-delta-cus INTEGER(-16..15), + scale-delta-crc INTEGER(-16..15), + scale-delta-cic INTEGER(-16..15), + scale-delta-cuc INTEGER(-16..15), + scale-delta-tgd INTEGER(-16..15), + ... +} + +``` + +``` + +GPSEphemerisExtensionCheck ::= SEQUENCE { + gpsBeginTime GPSEphemerisExtensionTime, + gpsEndTime GPSEphemerisExtensionTime, + gpsSatEventsInfo GPSSatEventsInfo, + ... +} + +GPSSatEventsInfo ::= SEQUENCE { + eventOccured BIT STRING (SIZE (32)), + futureEventNoted BIT STRING (SIZE (32)), + ... +} + +-- If a bit is clear in the eventOccured field it indicates that no known errors have occured since +-- the gpsBeginTime nor is a maneuver planned for the next sixty minutes. +-- If a bit is set in the futureEventNoted field it indicates that a maneuver is planned during the +-- time period between current time plus sixty minutes and gpsEndTime + +-- DGPS Corrections Validity Period: +-- This element may only be included if DGPCorrections IE is included in ControlHeader element. +-- DGPCorrectionsValidityPeriod shall contain the same number of elements as the SeqOfSatElement +-- included in DGPCorrections IE +DGPCorrectionsValidityPeriod ::= SEQUENCE (SIZE (1..16)) OF DGPSExtensionSatElement + +DGPSExtensionSatElement ::= SEQUENCE { + satelliteID SatelliteID, + udreGrowthRate INTEGER(0..7), -- coding according to annex + udreValidityTime INTEGER(0..7), -- coding according to annex + ... +} + +-- GPS Reference Time Rel-10 Extension: +GPSReferenceTime-R10-Ext ::= SEQUENCE { + gpsWeekCycleNumber INTEGER(0..7) -- coding according to annex +} + +-- GPS Acquisition Assistance Rel-10 Extension: +-- GPSAcquisAssist-R10-Ext shall contain the same number of elements as the SeqOfAcquisElement +-- included in AcquisAssist IE +GPSAcquisAssist-R10-Ext ::= SEQUENCE (SIZE (1..16)) OF GPSAcquisAssist-R10-Ext-Element + +GPSAcquisAssist-R10-Ext-Element ::= SEQUENCE { + satelliteID SatelliteID, + azimuthLSB INTEGER(0..15), + elevationLSB INTEGER(0..15) +} + +-- GPS Acquisition Assistance Rel-12 Extension: +GPSAcquisAssist-R12-Ext ::= SEQUENCE { + confidence INTEGER (0..100) OPTIONAL, + acquisList SeqOfGPSAcquisAssist-R12-Ext OPTIONAL +} + +SeqOfGPSAcquisAssist-R12-Ext ::= SEQUENCE (SIZE(1..16)) OF GPSAcquisAssist-R12-Ext-Element + +GPSAcquisAssist-R12-Ext-Element ::= SEQUENCE { + satelliteID SatelliteID, + dopplerUncertaintyExt ENUMERATED { + d300, + d400, + d500, + d600, + noInformation, ... + } +} + +-- GPS Almanac Rel-10 Extension: +GPSAlmanac-R10-Ext ::= SEQUENCE { + completeAlmanacProvided BOOLEAN -- TRUE means that complete Almanac is provided +} + +``` + +``` + +Rel-7-MsrPosition-Rsp-Extension ::= SEQUENCE { + velEstimate VelocityEstimate OPTIONAL, + -- Horizontal Velocity + -- Horizontal with Vertical Velocity + -- Horizontal Velocity with Uncertainty + -- Horizontal with Vertical Velocity and Uncertainty + ganssLocationInfo GANSSLocationInfo OPTIONAL, + ganssMeasureInfo GANSSMeasureInfo OPTIONAL, + ... + -- Further Release 7 extensions here +} + +-- GANSS Location Information contains location estimate, time stamp with uncertainty +-- and optionally Reference Frame field +GANSSLocationInfo ::= SEQUENCE { + referenceFrame ReferenceFrame OPTIONAL, -- Reference Frame Number + ganssTODm GANSSTODm OPTIONAL, -- GNSS TOD modulo + ganssTODFrac INTEGER (0 .. 16384) OPTIONAL, -- Coding according to Annex + -- a value of 16384 shall not be encoded by the sender + -- the receiver shall consider a value of 16384 to be invalid data + ganssTODUncertainty GANSSTODUncertainty OPTIONAL, -- Coding according to Annex + ganssTimeID INTEGER (0 .. 7) OPTIONAL, -- Coding according to Annex + fixType FixType, + posData PositionData, + stationaryIndication INTEGER(0 .. 1) OPTIONAL, -- '0' if moving or motion not + -- known + + -- Possible shapes carried in posEstimate are + -- ellipsoid point, + -- ellipsoid point with uncertainty circle + -- ellipsoid point with uncertainty ellipse + -- ellipsoid point with altitude and uncertainty ellipsoid + posEstimate Ext-GeographicalInformation, + ... +} + +PositionData ::= BIT STRING { + e-otd (0), + gps (1), + galileo (2), + sbas (3), + modernizedGPS (4), + qzss (5), + glonass (6), + bds (7)} (SIZE (3..16)) + +-- GANSS TOD modulo 1 hour +GANSSTODm ::= INTEGER (0 .. 3599999) + +ReferenceFrame ::= SEQUENCE { + referenceFN INTEGER (0 .. 65535), + -- Note that applicable range for referenceFN is 0 - 42431 + referenceFNMSB INTEGER (0 .. 63) OPTIONAL -- MSB of Reference Frame Number +} + +-- GANSS Measurement Information +GANSSMeasureInfo ::= SEQUENCE { + -- Measurement info elements + ganssMsrSetList SeqOfGANSS-MsrSetElement +} +SeqOfGANSS-MsrSetElement ::= SEQUENCE (SIZE(1..3)) OF GANSS-MsrSetElement + +``` + +``` + +-- GANSS measurement information 1-3 times in a message +GANSS-MsrSetElement ::= SEQUENCE { + referenceFrame ReferenceFrame OPTIONAL, -- Reference Frame Number + -- if ganssTODm is included, it is the GNSS specific system time of the GANSS reported + -- first in ganss-SgnTypeList. If GPS Measurement Information element is not included in + -- a Measure Position Response component, this field shall be present. + ganssTODm GANSSTODm OPTIONAL, -- GANSS TOD modulo 1 hour + deltaGANSSTOD INTEGER (0 .. 127) OPTIONAL, + ganssTODUncertainty GANSSTODUncertainty OPTIONAL, -- Coding according to Annex + --N_GANSS can be read from number of elements of SeqOfGANSS-MsrElement + ganss-MsrElementList SeqOfGANSS-MsrElement +} + +SeqOfGANSS-MsrElement ::= SEQUENCE (SIZE(1..8)) OF GANSS-MsrElement + +GANSS-MsrElement ::= SEQUENCE { + ganssID INTEGER (0..7) OPTIONAL, --Absence means Galileo + ganss-SgnTypeList SeqOfGANSS-SgnTypeElement +} + +-- Measurements can be returned up to 8 different signal types +-- N_SGN_TYPE can be read from number of elements of SeqOfGANSS-SgnTypeElement +-- Reporting of multiple signal types as defined in A.2.2.4g +SeqOfGANSS-SgnTypeElement ::= SEQUENCE (SIZE(1..8)) OF GANSS-SgnTypeElement + +GANSS-SgnTypeElement ::= SEQUENCE { + ganssSignalID GANSSSignalID, -- Coding according to Annex + ganssCodePhaseAmbiguity INTEGER (0 .. 127) OPTIONAL, + --N_SGN can be read from number of elements of SeqOfGANSS-SgnElement + ganss-SgnList SeqOfGANSS-SgnElement, + ... +} + +-- Up to 16 Measurements can be returned per signal type +SeqOfGANSS-SgnElement ::= SEQUENCE (SIZE(1..16)) OF GANSS-SgnElement + +GANSS-SgnElement ::= SEQUENCE { + svID SVID, + cNo INTEGER (0 .. 63), + mpathDet MpathIndic, -- Coding according to Annex + carrierQualityInd INTEGER (0 .. 3) OPTIONAL, -- Coding according to Annex + codePhase INTEGER (0 .. 2097151), + integerCodePhase INTEGER (0 .. 127) OPTIONAL, + codePhaseRMSError INTEGER (0..63), -- Coding according to Annex + doppler INTEGER (-32768 .. 32767) OPTIONAL, + adr INTEGER (0 .. 33554431) OPTIONAL +} + +``` + +``` + +Rel7-AssistanceData-Extension ::= SEQUENCE { + ganss-AssistData GANSS-AssistData OPTIONAL, + ganssCarrierPhaseMeasurementRequest NULL OPTIONAL, + ganssTODGSMTTimeAssociationMeasurementRequest NULL OPTIONAL, + add-GPS-AssistData Add-GPS-AssistData OPTIONAL, + ... + -- Possibly more extensions for Release 7 here +} + +BDS-DiffCorrections-r12 ::= SEQUENCE { + dbds-RefTime-r12 INTEGER (0..3599), + -- N_SGN_TYPE can be read from number of elements of bds-SgnTypeList-r12 + bds-SgnTypeList-r12 BDS-SgnTypeList-r12, + ... +} + +BDS-SgnTypeList-r12 ::= SEQUENCE (SIZE (1..3)) OF BDS-SgnTypeElement-r12 + +BDS-SgnTypeElement-r12 ::= SEQUENCE { + ganssSignalID GANSSSignalID OPTIONAL, + + -- N_SAT can be read from number of elements of dbds-CorrectionList-r12 + dbds-CorrectionList-r12 DBDS-CorrectionList-r12, + ... +} + +DBDS-CorrectionList-r12 ::= SEQUENCE (SIZE (1..64)) OF DBDS-CorrectionElement-r12 + +DBDS-CorrectionElement-r12 ::= SEQUENCE { + svID SVID, + bds-UDREI-r12 INTEGER (0..15), + bds-RURAI-r12 INTEGER (0..15), + bds-ECC-DeltaT-r12 INTEGER (-4096..4095), + ... +} + +BDS-GridModelParameter-r12 ::= SEQUENCE { + bds-RefTime-r12 INTEGER (0..3599), + + --N_IGP can be read from number of elements of GridIonList-r12 + gridIonList-r12 GridIonList-r12, + ... +} + +--Up to 16 instances are used in this version of the specification. The values 17 to 320 are +reserved for future use. +GridIonList-r12 ::= SEQUENCE (SIZE (1..320)) OF GridIonElement-r12 + +GridIonElement-r12 ::= SEQUENCE { + igp-ID-r12 INTEGER (1..320), + dt-r12 INTEGER (0..511), + givei-r12 INTEGER (0..15) , + ... +} + +``` + +``` +-- Rel-7 Positioning Capability parameters here + +PosCapabilities ::= SEQUENCE { + -- nonGANSSpositionMethods shall be included if and only if any + -- of the non-GANSS methods is supported. + nonGANSSpositionMethods NonGANSSpositionMethods OPTIONAL, + + -- gANSSpositionMethods shall be included if and only if any of the GANSS methods is supported. + gANSSpositionMethods GANSSpositionMethods OPTIONAL, + + -- multipleMeasurementSets shall be present if and only if 'multiple sets' is supported + -- for any of the positioning methods + multipleMeasurementSets MultipleMeasurementSets OPTIONAL, + ... +} + +NonGANSSpositionMethods ::= BIT STRING { + msAssistedEOTD (0), + msBasedEOTD (1), + msAssistedGPS (2), -- If this bit is set, gpsAssistance in AssistanceSupported IE + -- shall be present + msBasedGPS (3), -- If this bit is set, gpsAssistance in AssistanceSupported IE + -- shall be present + + standaloneGPS (4) } (SIZE (1..16)) + +GANSSpositionMethods ::= SEQUENCE (SIZE(1..16)) OF GANSSpositionMethod + +GANSSpositionMethod ::= SEQUENCE { + ganssID INTEGER (0..7) OPTIONAL, --Absence means Galileo + -- gANSSPositioningMethodTypes may be present for PosCapability-Req + -- and shall be present for PosCapability-Rsp + gANSSPositioningMethodTypes GANSSPositioningMethodTypes OPTIONAL, + gANSSSignals GANSSSignals, + ... + -- sbasID shall be present if and only if ganssID indicates SBAS + sbasID SBASID OPTIONAL +} + +GANSSPositioningMethodTypes ::= BIT STRING { + msAssisted (0), -- If this bit is set, gANSSAssistanceSet in AssistanceSupported IE + -- shall be present. + msBased (1), -- If this bit is set, gANSSAssistanceSet in AssistanceSupported IE + -- shall be present. + standalone (2) } (SIZE (1..8)) + +-- indicates MS support for particular GANSS signals and frequencies +GANSSSignals ::= BIT STRING { + signal1 (0), + signal2 (1), + signal3 (2), + signal4 (3), + signal5 (4), + signal6 (5), + signal7 (6), + signal8 (7) } (SIZE (1..8)) + +SBASID ::= BIT STRING { + waas (0), + egnos (1), + masas (2), + gagan (3) } (SIZE (1..8)) +``` + +``` + +-- indicates MS support of multiple measurement sets for MS assisted position methods +MultipleMeasurementSets ::= BIT STRING { + eotd (0), + gps (1), + ganss (2) } (SIZE (1..8)) + +-- indicates MS support of different types of assistance data +AssistanceSupported ::= SEQUENCE { + gpsAssistance GPSAssistance OPTIONAL, + gANSSAssistanceSet GANSSAssistanceSet OPTIONAL, + ... +} + +-- gANSSAdditionalAssistanceChoices shall be present if the MS supports other than native models +gANSSAdditionalAssistanceChoices ::= GANSSAdditionalAssistanceChoices OPTIONAL + +-- GPS assistance data supported +GPSAssistance ::= BIT STRING { + almanac (0), + uTCmodel (1), + ionosphericModel (2), + navigationmodel (3), + dGPScorrections (4), + referenceLocation (5), + referenceTime (6), + acquisitionAssistance (7), + realTimeIntegrity (8), + ephemerisExtension (9), + ephemerisExtensionCheck (10), + gPSAcquisAssist-R12-Ext (11) } (SIZE (1..16)) + +-- GANSS assistance data supported +GANSSAssistanceSet ::= SEQUENCE { + commonGANSSAssistance CommonGANSSAssistance, + specificGANSSAssistance SpecificGANSSAssistance, + ... +} + +-- Common GANSS assistance data supported +CommonGANSSAssistance ::= BIT STRING { + referenceTime (0), + referenceLocation (1), + ionosphericModel (3), + addIonosphericModel (4), + earthOrientationParam (5) } (SIZE (1..8)) + +SpecificGANSSAssistance ::= SEQUENCE (SIZE(1..16)) OF GANSSAssistanceForOneGANSS + +-- assistance data supported for a particular GANSS system +GANSSAssistanceForOneGANSS ::= SEQUENCE { + ganssID INTEGER (0..7) OPTIONAL, --Absence means Galileo + gANSSAssistance GANSSAssistance, + ... +} + +-- specific GANSS assistance data supported +GANSSAssistance ::= BIT STRING { + realTimeIntegrity (0), + differentialCorrections (1), + almanac (2), + referenceMeasurementInformation (3), + navigationModel (4), + timeModelGNSS-UTC (5), + timeModelGNSS-GNSS (6), + databitassistance (7), + ephemerisExtension (8), + ephemerisExtensionCheck (9), + addUTCmodel (10), + auxiliaryInformation (11), + gANSSRefMeasurementAssist-R12-Ext (12), + bdsDifferentialCorrections-r12 (13), + bdsGridModel-r12 (14) } (SIZE (1..16)) + +GANSSAdditionalAssistanceChoices ::= SEQUENCE (SIZE(1..16)) OF + GANSSAdditionalAssistanceChoicesForOneGANSS + +GANSSAdditionalAssistanceChoicesForOneGANSS ::= SEQUENCE { + ganssID INTEGER (0..7) OPTIONAL, --Absence means Galileo + ganssClockModelChoice GANSSModelID OPTIONAL, +} + +``` + +``` + gannsOrbitModelChoice GANSSModelID OPTIONAL, + gannsAlmanacModelChoice GANSSModelID OPTIONAL, + gannsAdditionalUTCModelChoice GANSSModelID OPTIONAL, + ... +} +``` + +``` + +GANSSModelID ::= BIT STRING { + model1 (0), + model2 (1), + model3 (2), + model4 (3), + model5 (4), + model6 (5), + model7 (6), + model8 (7) } (SIZE (1..8)) + +-- indicates assistance data that may be needed by the MS +-- These elements are coded as defined in TS 49.031 with the exceptions defined in section A.8.2.3 +AssistanceNeeded ::= SEQUENCE { + gpsAssistanceData GPSAssistanceData OPTIONAL, + ganssAssistanceData GANSSAssistanceData OPTIONAL, + ... +} + +CellSets ::= SEQUENCE { + cellSet1 CellSet, -- set 1 + cellSet2 CellSet OPTIONAL, -- set 2 + cellSet3 CellSet OPTIONAL, -- set 3 + cellSet4 CellSet OPTIONAL, -- set 4 + cellSet5 CellSet OPTIONAL, -- set 5 + cellSet6 CellSet OPTIONAL, -- set 6 + cellSet7 CellSet OPTIONAL, -- set 7 + cellSet8 CellSet OPTIONAL -- set 8 +} + +CellSet ::= SEQUENCE { + cell1 CellInfo, -- provides a GSM ARFCN value + cell2 CellInfo OPTIONAL, -- provides a GSM ARFCN and BSIC value + cell3 CellInfo OPTIONAL, -- provides a GSM ARFCN and BSIC value + cell4 CellInfo OPTIONAL, -- provides a GSM ARFCN and BSIC value + cell5 CellInfo OPTIONAL, -- provides a GSM ARFCN and BSIC value + cell6 CellInfo OPTIONAL -- provides a GSM ARFCN and BSIC value +} + +CellInfo ::= SEQUENCE { + bsic INTEGER (0..511), + arfcn INTEGER (0..1023) OPTIONAL +} + +OTDMeasurementResults ::= SEQUENCE { + oTDMeasurementInfo1 OTDMeasurementInfo, -- Measurement 1 + oTDMeasurementInfo2 OTDMeasurementInfo OPTIONAL, -- Measurement 2 + oTDMeasurementInfo3 OTDMeasurementInfo OPTIONAL, -- Measurement 3 + oTDMeasurementInfo4 OTDMeasurementInfo OPTIONAL, -- Measurement 4 + oTDMeasurementInfo5 OTDMeasurementInfo OPTIONAL, -- Measurement 5 + oTDMeasurementInfo6 OTDMeasurementInfo OPTIONAL, -- Measurement 6 + oTDMeasurementInfo7 OTDMeasurementInfo OPTIONAL -- Measurement 7 +} + +OTDMeasurementInfo ::= SEQUENCE { + reportedCell CellType, + msSyncAccuracy INTEGER (0..15), + observedTimeDiff INTEGER (0..999) +} + +CellType ::= CHOICE { + configuredNeighbourCellIdx INTEGER (1..48), --The cell is part of assistance info + detectedNeighbourCell CellInfo --The cell is not part of assistance info +} + +RXLEVMeasurementResults ::= SEQUENCE { + rxLEVMeasurementInfo1 RXLEVMeasurementInfo, --Rxlevel Measurement 1 + rxLEVMeasurementInfo2 RXLEVMeasurementInfo OPTIONAL, --Rxlevel Measurement 2 + rxLEVMeasurementInfo3 RXLEVMeasurementInfo OPTIONAL, --Rxlevel Measurement 3 + rxLEVMeasurementInfo4 RXLEVMeasurementInfo OPTIONAL, --Rxlevel Measurement 4 + rxLEVMeasurementInfo5 RXLEVMeasurementInfo OPTIONAL, --Rxlevel Measurement 5 + rxLEVMeasurementInfo6 RXLEVMeasurementInfo OPTIONAL --Rxlevel Measurement 6 +} + +``` + +``` + +RXLEVMeasurementInfo ::= SEQUENCE { + reportedCell CellType, + rxLEV INTEGER(0..63) +} + +MTA-Method ::= CHOICE { + rlc-Data-Block NULL, + access-Burst NULL, + extended-Access-Burst Extended-Access-Burst, + spare NULL +} + +Random-ID-Set ::= SEQUENCE { + random-ID1 INTEGER (0..65535), + random-ID2 INTEGER (0..65535), + random-ID3 INTEGER (0..65535) OPTIONAL, + random-ID4 INTEGER (0..65535) OPTIONAL, + random-ID5 INTEGER (0..65535) OPTIONAL, + random-ID6 INTEGER (0..65535) OPTIONAL, + random-ID7 INTEGER (0..65535) OPTIONAL, + random-ID8 INTEGER (0..65535) OPTIONAL, + random-ID9 INTEGER (0..65535) OPTIONAL +} + +Extended-Access-Burst ::= SEQUENCE { + short-BSS-ID INTEGER (0..7) +} + +Co-Sited-Cells ::= SEQUENCE { + co-sited-cell-Set-Member1 Co-Sited-Cell-Set-Member OPTIONAL, + co-sited-cell-Set-Member2 Co-Sited-Cell-Set-Member OPTIONAL, + co-sited-cell-Set-Member3 Co-Sited-Cell-Set-Member OPTIONAL, + co-sited-cell-Set-Member4 Co-Sited-Cell-Set-Member OPTIONAL, + co-sited-cell-Set-Member5 Co-Sited-Cell-Set-Member OPTIONAL, + co-sited-cell-Set-Member6 Co-Sited-Cell-Set-Member OPTIONAL +} + +Co-Sited-Cell-Set-Member ::= SEQUENCE { + arfcn INTEGER (0..1023), + bsic-Info BSIC-Info +} + +Cell-Set ::= SEQUENCE { + cell-Set-Member1 Cell-Set-Member, + cell-set-Member2 Cell-Set-Member OPTIONAL, + cell-set-Member3 Cell-Set-Member OPTIONAL, + cell-set-Member4 Cell-Set-Member OPTIONAL, + cell-set-Member5 Cell-Set-Member OPTIONAL, + cell-set-Member6 Cell-Set-Member OPTIONAL +} + +Cell-Set-Member ::= SEQUENCE { + arfcn INTEGER (0..1023), + bsic-Info BSIC-Info, + short-ID INTEGER (0..255) OPTIONAL, + ec-cell-information CHOICE { + ec-RACH-Control-Parameters EC-RACH-Control-Parameters, -- May be included for any member of + -- a Cell-Set that supports EC-GSM-IoT (see sub-clause A.9). + default-ec-RACH-Control-Parameters NULL -- Indicates a member uses the same ec-RACH-Control + -- Parameters as any other member of the Cell-Set for which +this information is provided. + }, + peo-cell-information CHOICE { + rach-Control-Parameters RACH-Control-Parameters, -- May be included for any member of + -- a Cell-Set that supports PEO (see sub-clause A.9). + default-rach-Control-Parameters NULL -- Indicates a member uses the same rach-Control + -- Parameters as any other member of the Cell-Set for which this +information is provided. + } +} + +BSIC-Info ::= SEQUENCE { + radio-Frequency-Colour-Code INTEGER (0..7), + network-Colour-Code INTEGER (0..7), + base-station-Colour-Code INTEGER (0..7) +} + +``` + +``` + +EC-RACH-Control-Parameters ::= SEQUENCE { + ec-BS-CC-CHANS INTEGER (0..3), + ec-RXLEV-ACCESS-MIN INTEGER (0..63), + ms-TXPWR-MAX-CCH INTEGER (0..31), + lb-MS-TXPWR-MAX-CCH INTEGER (0..31) OPTIONAL, + cell-SELECTION-RLA-MARGIN INTEGER (0..7) OPTIONAL, + dl-CC-Selection BOOLEAN, + bt-Threshold-DL INTEGER (0..31), + cc2-Range-DL INTEGER (0..31) OPTIONAL, + cc3-Range-DL INTEGER (0..31) OPTIONAL, + bt-Threshold-UL INTEGER (0..31), + cc2-Range-UL INTEGER (0..31) OPTIONAL, + cc3-Range-UL INTEGER (0..31) OPTIONAL, + cc4-Range-UL INTEGER (0..31) OPTIONAL, + bsPWR INTEGER (0..63), + dl-Signal-Strength-Step-Size INTEGER (0..3) OPTIONAL, + ec-Reduced-PDCH-Allocation BOOLEAN, + ec-Max-Retrans INTEGER , + sm INTEGER (0..3), + tm INTEGER (0..3), + access-Timeslots BOOLEAN, + alpha INTEGER (0..15) OPTIONAL, + t3168 INTEGER (0..7) OPTIONAL, + t3192 INTEGER (0..7) OPTIONAL, + t3226 INTEGER (0..7) OPTIONAL, + t3248 INTEGER (0..3), + mta-BITMAP MTA-BITMAP +} + +RACH-Control-Parameters ::= SEQUENCE { + rxlev-ACCESS-MIN INTEGER (0..63), + ms-TXPWR-MAX-CCH INTEGER (0..31), + max-Retrans INTEGER (0..3), + tx-integer INTEGER (0..15), + mta-BITMAP MTA-BITMAP +} + +MTA-BITMAP ::= SEQUENCE { + mta-RLC-Data-Block-method BOOLEAN, + mta-Access-Burst-method BOOLEAN, + mta-Extended-Access-Burst-method BOOLEAN, + mta-spares BOOLEAN +} + +MTA-Security ::= CHOICE { + mta-access-security-method NULL, + bss-duplication-detection-method NULL, + spare NULL +} + +``` + +# 6 TOM Protocol Header for RRLP Transport + +## 6.1 General + +For the specification of the TOM protocol, see 3GPP TS 44.064. + +## 6.2 Remaining Octets of TOM Protocol Header for RRLP + +The number of remaining octet following the first octets of the TOM protocol header for RRLP is one. The encoding of this octet is defined in the figure 6.1 and the table 6.1. + +![](b5987d63203a5fa601921039922ac520_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|-------|---|---|---|---|---|---|---|-------|---| +| Spare | | | | | | | | C/R | 1 | + +**Figure 6.1: Remaining Octets of TOM Protocol Header for RRLP** + +**Table 6.1: C/R bit content** + +| C/R | UI frame information field | +|-----|-----------------------------------------------------| +| 0 | Command (SMLC to MS) or Final Response (MS to SMLC) | +| 1 | Not Command or Final Response | + +The setting of the C/R flag is provided by the sending RRLP entity, for further details see 3GPP TS 43.059. + +The Spare bits shall be ignored by the receiver and set to 0 by the sender. If a protocol header with more than one remaining octet of the TOM protocol header is received, the additional octets after the first remaining octet shall be ignored by the receiver. + +# Annex A (informative): Description of Components + +## A.1 Introduction + +This annex describes the contents of components. + +## A.2 Measure Position Request + +### A.2.1 General + +The Measure Position Request is a RRLP component from the SMLC to the MS. This component is common to E-OTD, GPS and GANSS (Galileo and Additional Navigation Satellite Systems) location methods. As a response to this component, the MS performs E-OTD, GPS or GANSS measurements and possibly calculates its own position, if the MS and/or the network support these options. It contains the following elements. + +**Table A.1: Measure Position Request component content** + +| Element | Type/Reference | Presence | +|---------------------------------------------------------------|---------------------------------------------------------------------|----------| +| Positioning Instructions | Positioning Instructions 2.2.1 | M | +| E-OTD Reference BTS for Assistance Data | E-OTD Reference BTS for Assistance Data 2.2.2 | O | +| E-OTD Measurement Assistance Data | E-OTD Measurement Assistance Data 2.2.3 | O | +| E-OTD Measurement Assistance Data for System Information List | E-OTD Measurement Assistance Data for System Information List 2.2.4 | O | +| GPS Assistance Data | GPS Assistance Data 4.2.4 | O | +| Additional GPS Assistance Data | Additional GPS Assistance Data 4.2.4c | O | +| GPS Time Assistance Measurement Request | GPS Time Assistance Measurement Request 2.2.4a | O | +| GPS Reference Time Uncertainty | GPS Reference Time Uncertainty 2.2.4b | O | +| Velocity Request | Velocity Request 2.2.4c | O | +| Extended Reference | Extended Reference 2.2.5 | O | +| GANSS Positioning Method Element | GANSS Positioning Method Element 2.2.1a | O | +| GANSS Carrier-Phase Measurement Request | GANSS Carrier-Phase Measurement Request 2.2.4d | O | +| GANSS TOD - GSM Time Association Request | GANSS TOD - GSM Time Association Request 2.2.4e | O | +| GANSS Multi-frequency Measurement Request | GANSS Multi-frequency Measurement Request 2.2.4g | O | +| GANSS Assistance Data | GANSS Assistance Data 4.2.6 | O | +| Required Response Time | Required Response Time 2.2.4f | O | + +### A.2.2 Elements + +#### A.2.2.1 Positioning Instructions Element + +The purpose of Positioning Instructions element is to express the allowed/required location method(s), and to provide information required QoS. This element is mandatory in the Measure Position Request message, and contains the following fields: + +##### Method Type + +This field indicates whether MS based or assisted version is allowed/requested. If the Positioning Methods field includes more than one method, the Method Type applies to all of them. This field is mandatory, and has the following values: + +'0': MS assisted; + +'1': MS based; + +'2': MS based is preferred, but MS assisted is allowed; + +'3': MS assisted is preferred, but MS based is allowed. + +In GPS positioning methods, 'MS based' may indicate either MS Based Assisted GPS method or Conventional GPS method. If 'MS based' is indicated with no GPS assistance data then the MS may interpret this as either Conventional GPS or MS based A-GPS without assistance data. The same interpretation applies also to the GANSS positioning method. + +##### Positioning Methods + +This field indicates which location method or methods should be used. This field is mandatory. + +'0': E-OTD; + +'1': GPS; + +'2': E-OTD or GPS (i.e. both can be reported). + +NOTE: If the selected positioning method is 'GPS' or 'E-OTD or GPS', the field GANSS Positioning Method, if present in a Measure Position Request component, indicates request of GANSS method and indicates the allowed satellite systems. + +##### Response Time + +This field indicates the desired response time. However, when performing measurements, the desired response time may be exceeded. This field is mandatory. + +The response time is $2^N$ seconds, where N is the value in this field. Thus the desired maximum response time can be 1, 2, 4, 8, 16, 32, 64, or 128 seconds. + +Range: 0-7 + +##### Accuracy + +This field indicates the required accuracy of the location estimate. This field is mandatory when Method Type is '1', '2', or '3' and optional when Method Type is '0'. + +This field is 7 bit Uncertainty Code as defined in 3GPP TS 23.032. + +##### Multiple Sets + +This field indicates whether MS is requested to send multiple *E-OTD/GPS/GANSS Measurement Information Sets*. The maximum number of measurement sets is three. This field is mandatory. MS is expected to include the current measurement set. Additionally MS may include historical measurement sets, or measure new additional sets if the response time allows that. + +'0': multiple IEs can be sent; + +'1': sending of multiple sets is not allowed. + +##### Environment Characterization + +Environment Characterization field provides the MS with information about expected multipath and NLOS in the current area. This field is optional. + +'0': possibly heavy multipath and NLOS conditions (e.g. bad urban or urban). + +'1': no or light multipath and usually LOS conditions (e.g. suburban or rural). + +'2': not defined or mixed environment. + +'3': reserved for future use. + +#### A.2.2.1a GANSS Positioning Method Element + +This bit map indicates the satellite systems allowed by the SMLC corresponding to allowance of 'GPS' in the Positioning Methods field. Each bit is of type Boolean, where TRUE ('1') means the particular satellite system is allowed. For example EOTD + Galileo method can be indicated by setting 'E-OTD or GPS' in Positioning Methods and setting only the 'bit 1' to TRUE value in the GANSS Positioning Method element. The MS shall not request assistance data or report measurements for the systems that are not indicated in the bit map. + +NOTE: Bit 0 of this bit map shall not be the only one set to TRUE ('1'). + +'bit 0': GPS; + 'bit 1': Galileo; + 'bit 2': SBAS (WAAS, EGNOS, MSAS, GAGAN); + 'bit 3': Modernized GPS (L1C, L2C, L5); + 'bit 4': QZSS; + 'bit 5': GLONASS; + 'bit 6': BDS; + 'bit 7-15': Reserved for future GNSSes. + +#### A.2.2.2 E-OTD Reference BTS for Assistance Data Element + +The RTD and 51 multiframe offset values in the E-OTD Measurement Assistance Data element and the E-OTD Measurement Assistance Data for System Information List element are calculated relative to the BTS indicated in this element. Also the E-OTD Measurement Assistance data for System Information List element, if present, refers to the System Information Neighbor List of this reference BTS. + +Inclusion of this parameter is mandatory for E-OTD since it is not possible to reliably default to the current serving BTS for the target MS, as there is a small chance that the SMLC does not know this. If the E-OTD Measurement Assistance data for System Information List element is present, the current serving cell must be the same as reference BTS identified in this element. + +##### BCCH Carrier + +This field indicates the absolute RF channel number of BCCH of the reference BTS. This field is mandatory. + +Range: 0 - 1023 + +##### BSIC + +This field indicates the BSIC (Base Station Identity Code) of the reference BTS. This field is mandatory. + +Range: 0 - 63 + +##### Time Slot Scheme + +The Time Slot Scheme field indicates the type of transmission scheme the reference BTS is using. If the MS measures BTSs signals from time slots other than 0 or 4, and it is informed about the burst length schemes used by BTSs, then it can compensate for the possible error. (This is necessary if the MS averages bursts from different time slots, and the BTS uses varying lengths of bursts.) This field is mandatory. + +'0' = all time slots are 156,25 bits long. + +'1' = time slots 0 and 4 are 157 bits long and other time slots are 156 bits long. + +##### BTS Position + +This field contains the BTS position in the format defined in 3GPP TS 23.032. This field is optional, but should be present for MS based E-OTD positioning. The allowed shapes are: + +- ellipsoid point; + +3GPP + +- ellipsoid point with altitude and uncertainty ellipsoid. + +#### A.2.2.3 E-OTD Measurement Assistance Data Element + +This element identifies BTSs that are used for E-OTD measurements. This element helps the MS to make measurements from neighbor BTS (even below decoding level). This element is optional in the Measure Position Request component. The presence of this element means that the MS should try to measure the E-OTD values between the reference BTS and the BTSs identified in this element. + +This element is used to deliver E-OTD measurement assistance data for those BTSs, that are not included in the System Information Neighbor List of the reference BTS, if necessary. + +The RTD and 51 multiframe offset values are calculated relative to the BTS indicated in the E-OTD Reference BTS for Assistance Data element. This element contains the following fields. + +##### Number of BTSs + +This field indicates how many BTSs are included in this IE. This field is mandatory. The maximum number of BTSs in this message for whom the assistance data can be given is 16 (reference BTS and 15 neighbour BTSs). Thus the sum of **Number of BTSs** field in this IE and total amount of **E-OTD Neighbor present** bits with value '1' in **E-OTD Measurement Assistance Data for System Information List IE** can be at a maximum 15. + +Range: 1 to 15. + +The following fields are repeated for the number of BTSs included in the Number of BTSs field. + +##### BCCH Carrier + +This field indicates the absolute RF channel number of BCCH of the particular BTS. This field is mandatory. + +Range: 0 - 1023 + +##### BSIC + +This field indicates the BSIC (Base Station Identity Code) of the particular BTS. This field is mandatory. + +Range: 0 - 63 + +##### Multiframe Offset + +This field indicates the frame difference between the start of the 51 multiframes frames being transmitted from this BTS and the reference BTS. The multiframe offset is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of the 51 multiframe in the BTS in question, and $T_{Ref}$ is the time of the start of the 51 multiframe in the reference BTS. This field is mandatory. Multiframe Offset may be used to calculate the Expected Multiframe Offset (the Multiframe Offset value that MS is expected to measure between this BTS and reference BTS in its current estimated location). + +Expected Multiframe Offset = (Multiframe Offset + Adjustment) modulo 51 + +Adjustment = 1 if Rough RTD - Expected OTD $\geq 850$ + +Adjustment = -1 if Rough RTD - Expected OTD $\leq -850$ + +Adjustment = 0 if $-400 \leq \text{Rough RTD} - \text{Expected OTD} \leq 400$ + +If the Rough RTD - Expected OTD is not within any of the ranges above, an error has occurred and the Expected OTD should be ignored and no Expected Multiframe Offset can be calculated. + +Range: 0 - 51 + +Usable range of Multiframe Offset value is 0 - 50. The Multiframe Offset value 51 shall not be encoded by the transmitting entity and shall be treated by the receiving entity as 0. + +##### Time Slot Scheme + +The Time Slot Scheme field indicates the type of transmission scheme the particular BTS is using. If the MS measures BTSs signals from time slots other than 0 or 4, and it is informed about the burst length schemes used by BTSs, then it + +can compensate for the possible error. (This is necessary if the MS averages bursts from different time slots, and the BTS uses varying lengths of bursts.) This field is mandatory. + +'0' = all time slots are 156,25 bits long. + +'1' = time slots 0 and 4 are 157 bits long and other time slots are 156 bits long. + +##### Rough RTD + +This field indicates the rough RTD value between this BTS and reference BTS. The used resolution is 1 bits. This RTD value is the RTD value of TS0s (i.e. the difference in starting of TS0), not only the RTD between starts of bursts. The RTD is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of TS0 in the BTS in question, and $T_{Ref}$ is the time of the start of the TS0 in the reference BTS. This field is mandatory. + +Range: 0 - 1250 + +Usable range of Rough RTD value is 0 - 1249. The Rough RTD value 1250 shall not be encoded by the transmitting entity and shall be treated by the receiving entity as 0. + +Accurate RTD values are needed for MS based E-OTD, i.e. when the MS calculates its own position. + +##### Expected OTD + +This field indicates the OTD value that MS is expected to measure between this BTS and reference BTS in its current estimated location. SMLC can estimate MS's location roughly e.g. based on serving BTS coordinates, TA, and possibly some other information. The used resolution is 1 bits. This OTD value is the OTD value of TS0s (i.e. the difference in starting of TS0), not only the OTD between starts of bursts. The OTD is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of TS0 in the BTS in question, and $T_{Ref}$ is the time of the start of the TS0 in the reference BTS. This is element is Release 98 extension and it is an optional element included in Release98-Ext IE. SMLC shall send this element to MS supporting MS Assisted or MS Based E-OTD. + +Range: 0 - 1250 + +Usable range of Expected OTD value is 0 - 1249. The Expected OTD value 1250 shall not be encoded by the transmitting entity and shall be treated by the receiving entity as 0. + +##### Uncertainty Of Expected OTD + +This field indicates the uncertainty in Expected OTD value. The uncertainty is related to SMLC's estimation of MS's location. The uncertainty defines following search window for MS, that it can use to speed up the OTD measurements: + +$$\text{Expected OTD} - \text{Uncertainty} < \text{measured OTD} < \text{Expected OTD} + \text{Uncertainty}.$$ + +This is element is Release 98 extension and it is an optional element included in Release98-Ext IE. SMLC shall send this element to MS supporting MS Assisted or MS Based E-OTD. + +Range is 0 - 7 with following encoding: + +| | | +|-----|------------------------------------------------| +| '0' | $0 < \text{uncertainty} \leq 2 \text{ bit};$ | +| '1' | $2 < \text{uncertainty} \leq 4 \text{ bit};$ | +| '2' | $4 < \text{uncertainty} \leq 8 \text{ bit};$ | +| '3' | $8 < \text{uncertainty} \leq 12 \text{ bit};$ | +| '4' | $12 < \text{uncertainty} \leq 16 \text{ bit};$ | +| '5' | $16 < \text{uncertainty} \leq 22 \text{ bit};$ | +| '6' | $22 < \text{uncertainty} \leq 30 \text{ bit};$ | +| '7' | $\text{uncertainty} > 30 \text{ bit}.$ | + +NOTE: If uncertainty in MS's location is x bits, uncertainty in Expected OTD is $2^x$ (in the worst case). When the uncertainty is given with value '7' no upper bound exist for the uncertainty. + +The following fields tell the coordinates of neighbor BTSs that are used for E-OTD measurements, and also fine RTD values. This information allows the MS to calculate its own location. These fields (Fine RTD, Relative north, Relative east and Relative altitude) are optional. All of Fine RTD, Relative north, and Relative east fields must be present, if some of them is included. + +##### Fine RTD + +3GPP + +This field indicates the fine RTD value between this BTS and reference BTS. It provides the 1/256 bit duration resolution to the value expressed in the corresponding Rough RTD field. This RTD value is the RTD value of TS0s (i.e. the difference in starting of TS0), not only the RTD between starts of bursts. The RTD is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of TS0 in the BTS in question, and $T_{Ref}$ is the time of the start of the TS0 in the reference BTS. This field is optional. + +Range: 0 - 255 + +##### Relative North + +This field indicates the distance of the neighbor BTS from the reference BTS in north- (negative values mean south) direction. This field is optional. The units are 0,03 seconds. The used reference ellipsoid is WGS 84 ellipsoid. + +Range: -200000...200000 + +##### Relative East + +This field indicates the distance of the neighbor BTS from the reference BTS in east (negative values mean west) direction. This field is optional. The units are 0,03 seconds. The used reference ellipsoid is WGS 84 ellipsoid. + +Range: -200000 ... 200000 + +##### Relative Altitude + +This field indicates the altitude of the neighbor BTS relative to the reference BTS in meters. This field is optional. + +Range: -4000 .. 4000 meters + +#### A.2.2.4 E-OTD Measurement Assistance Data for System Information List Element + +This element identifies those BTSs in the System Information Neighbor List that are used for E-OTD measurements. The System Information Neighbor Lists, to which this assistance data is given, are System Information Neighbor Lists that are sent in the dedicated mode, packet idle mode, packet transfer mode, or dual transfer mode. This element helps the MS to make measurements from those neighbor BTS (even below decoding level). This element is optional in the Measure Position Request component. The presence of this element means that the MS should use the BTSs identified here to the E-OTD measurements. + +The RTD and 51 multiframe offset values are calculated relative to the reference BTS. This element contains the following fields. + +##### Number of Neighbors + +This field indicates how many neighbors are included in this IE. + +Range: 1-32 + +The following fields are repeated for the number indicated in the Number of Neighbors field. + +##### E-OTD Neighbor present + +This field indicates whether the information concerning a certain BTS in the Neighbor List is present. Altogether no more than 15 BTS can have the indication "Neighbor is included". The maximum number of BTSs in this message for whom the assistance data can be given is 16 (reference BTS and 15 neighbour BTSs). Thus the sum of total amount of **E-OTD Neighbor present** bits with value '1' in this IE and **Number of BTSs** field in **E-OTD Measurement Assistance Data IE** can be at a maximum 15. + +- '0' Neighbor not included; + +- '1' Neighbor is included. + +The following fields (BSIC, Multiframe Offset, Time Slot Scheme and Rough RTD) are included if E-OTD neighbor present field is set to '1'. + +##### BSIC + +This field indicates the BSIC (Base Station Identity Code) of the particular BTS. This field is mandatory. + +Range: 0 - 63 + +##### Multiframe Offset + +This field indicates the frame difference between the start of the 51 multiframes frames being transmitted from this BTS and the reference BTS. The multiframe offset is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of the 51 multiframe in the BTS in question, and $T_{Ref}$ is the time of the start of the 51 multiframe in the reference BTS. This field is mandatory. Multiframe Offset may be used to calculate the Expected Multiframe Offset (the Multiframe Offset value that MS is expected to measure between this BTS and reference BTS in its current estimated location). + +$$\text{Expected Multiframe Offset} = (\text{Multiframe Offset} + \text{Adjustment}) \bmod 51$$ + +Adjustment = 1 if $\text{Rough RTD} - \text{Expected OTD} \geq 850$ + +Adjustment = -1 if $\text{Rough RTD} - \text{Expected OTD} \leq -850$ + +Adjustment = 0 if $-400 \leq \text{Rough RTD} - \text{Expected OTD} \leq 400$ + +Range: 0 - 51 + +Usable range of Multiframe Offset value is 0 - 50. The Multiframe Offset value 51 shall not be encoded by the transmitting entity and shall be treated by the receiving entity as 0. + +##### Time Slot Scheme + +The Time Slot Scheme field indicates the type of transmission scheme the particular BTS is using. If the MS measures BTSs signals from time slots other than 0 or 4, and it is informed about the burst length schemes used by BTSs, then it can compensate for the possible error. (This is necessary if the MS averages bursts from different time slots, and the BTS uses varying lengths of bursts.) This field is mandatory. + +'0' = all time slots are 156,25 bits long; + +'1' = time slots 0 and 4 are 157 bits long and other time slots are 156 bits long. + +##### Rough RTD + +This field indicates the RTD value between this BTS and the reference BTS. The used resolution is 1 bit. This RTD value is the RTD value of TS0s (i.e. the difference in starting of TS0), not only the RTD between starts of bursts. The RTD is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of TS0 in the BTS in question, and $T_{Ref}$ is the time of the start of the TS0 in the reference BTS. This field is mandatory. + +Range: 0 - 1250 + +Usable range of Rough RTD value is 0 - 1249. The RoughRTD value 1250 shall not be encoded by the transmitting entity and shall be treated by the receiving entity as 0. + +##### Expected OTD + +This field indicates the OTD value that MS is expected to measure between this BTS and reference BTS in its current estimated location. SMLC can estimate MS's location roughly e.g. based on serving BTS coordinates, TA, and possibly some other information. The used resolution is 1 bits. This OTD value is the OTD value of TS0s (i.e. the difference in starting of TS0), not only the OTD between starts of bursts. The OTD is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of TS0 in the BTS in question, and $T_{Ref}$ is the time of the start of the TS0 in the reference BTS. This element is Release 98 extension and it is an optional element included in Release98-Ext IE. SMLC shall send this element to MS supporting MS Assisted or MS Based E-OTD. + +Range: 0 - 1250 + +Usable range of Expected OTD value is 0 - 1249. The Expected OTD value 1250 shall not be encoded by the transmitting entity and shall be treated by the receiving entity as 0. + +##### Uncertainty Of Expected OTD + +This field indicates the uncertainty in Expected OTD value. The uncertainty is related to SMLC's estimation of MS's location. The uncertainty defines following search window for MS, that it can use to speed up the OTD measurements: + +Expected OTD - Uncertainty < measured OTD < Expected OTD + Uncertainty. + +This element is Release 98 extension and it is an optional element included in Release98-Ext IE. SMLC shall send this element to MS supporting MS Assisted or MS Based E-OTD. + +Range is 0 - 7 with following encoding: + +| | | +|-----|------------------------------------------------| +| '0' | $0 < \text{uncertainty} \leq 2 \text{ bit};$ | +| '1' | $2 < \text{uncertainty} \leq 4 \text{ bit};$ | +| '2' | $4 < \text{uncertainty} \leq 8 \text{ bit};$ | +| '3' | $8 < \text{uncertainty} \leq 12 \text{ bit};$ | +| '4' | $12 < \text{uncertainty} \leq 16 \text{ bit};$ | +| '5' | $16 < \text{uncertainty} \leq 22 \text{ bit};$ | +| '6' | $22 < \text{uncertainty} \leq 30 \text{ bit};$ | +| '7' | $\text{uncertainty} > 30 \text{ bit}.$ | + +NOTE: If uncertainty in MS's location is x bits, uncertainty in Expected OTD is $2^x$ (in the worst case). When the uncertainty is given with value '7' no upper bound exist for the uncertainty. + +The following fields tell the coordinates of neighbor BTSs that are used for E-OTD measurements, and also fine RTD values. This information allows the MS to calculate its own location. These fields (Fine RTD, Relative north, Relative east and Relative altitude) are optional. All of Fine RTD, Relative north, and Relative east fields must be present, if some of them is included. + +##### Fine RTD + +This field indicates the fine RTD value between this BTS and reference BTS. It provides the $1/256$ bit duration resolution to the value expressed in the corresponding Rough RTD field. This RTD value is the RTD value of TS0s (i.e. the difference in starting of TS0), not only the RTD between starts of bursts. The RTD is defined as $T_{\text{BTS}} - T_{\text{Ref}}$ , where $T_{\text{BTS}}$ is the time of the start of TS0 in the BTS in question, and $T_{\text{Ref}}$ is the time of the start of the TS0 in the reference BTS. This field is optional. + +Range: 0 - 255 + +##### Relative North + +This field indicates the distance of the neighbor BTS from the reference BTS in north- (negative values mean south) direction. This field is optional. The units are 0,03 seconds. The used reference ellipsoid is WGS 84 ellipsoid. + +Range: -200000...200000 + +##### Relative East + +This field indicates the distance of the neighbor BTS from the reference BTS in east (negative values mean west) direction. This field is optional. The units are 0,03 seconds. The used reference ellipsoid is WGS 84 ellipsoid. + +Range: -200000 ... 200000 + +##### Relative Altitude + +This field indicates the altitude of the neighbor BTS relative to the reference BTS in meters. This field is optional. + +Range: -4000 .. 4000 meters + +#### A.2.2.4a GPS Time Assistance Measurement Request element + +This component does not have any information contents. If this component is present, the MS is requested to return GPS time assistance measurements. + +#### A.2.2.4b GPS Reference Time Uncertainty element + +This element provides the accuracy of the relation GPS and GSM time in the Reference Time field in GPS Assistance Data IE. If GPS TOW is the given GPS time, then the true GPS time, corresponding to the provided GSM time as observed at the MS location, lies in the interval (GPS TOW - GPS Reference Time Uncertainty, GPS TOW + GPS Reference Time Uncertainty). An entity that supports this element shall always include it when appropriate. This means + +that when the element is expected but is not received, lack of support at the sender can be assumed and some implementation dependent default interpretation can then be applied. + +The uncertainty $r$ , expressed in microseconds, is mapped to a number $K$ , with the following formula: + +$$r = C * (((1+x)^K) - 1)$$ + +with $C = 0,0022$ and $x = 0,18$ . With $0 \leq K \leq 127$ , a suitably useful range between 0 and 3 second is achieved for the uncertainty, while still being able to code down to values as small as 0,3 nanoseconds. To encode any higher value of uncertainty than that corresponding in the above formula to $K=127$ , the same value, $K=127$ , shall also be used. The uncertainty is then coded on 7 bits, as the binary encoding of $K$ . + +**Table A.1a: Example values for the GPS Reference Time Uncertainty Parameter Format** + +| Value of K | Value of uncertainty | +|------------|----------------------| +| 0 | 0 nanoseconds | +| 1 | 0,396 nanoseconds | +| 2 | 0,863 nanoseconds | +| - | - | +| 50 | 8,64 microseconds | +| - | - | +| 127 | $\geq 2,96$ seconds | + +#### A.2.2.4c Velocity Request element + +If this element is present, the MS is requested to return a velocity estimate along with the location estimate. Requesting velocity does not guarantee its delivery, if conditions support its availability and it is requested it will be provided. + +#### A.2.2.4d GANSS Carrier-Phase Measurement Request Element + +This component does not have any information contents. If this component is present, the MS is requested to return carrier phase measurements in the GANSS Measurement Information IE. + +#### A.2.2.4e GANSS TOD - GSM Time Association Request Element + +This component does not have any information contents. If this component is present, the MS is requested to return GANSS TOD - GSM time association measurements. Only either GPS Timing Assistance Measurement Request Element or GANSS TOD - GSM Time Association Measurement Request should be present in Measure Position Request. + +#### A.2.2.4f Required Response Time + +This element indicates the maximum response time that shall be allowed for the positioning request in the MS. When this element is received, the MS shall send an RRLP Measure Position Response before the required response time has elapsed. + +When this element is received, the MS shall ignore the Response Time field in the Positioning Instructions element. + +The Required Response Time has a value from 1 to 128 seconds. + +#### A.2.2.4g GANSS Multi-frequency Measurement Request Element + +This component does not have any information contents. + +If this component is present, the MS is requested to return measurements performed on multiple GANSS signal types if the MS supports this capability. If this component is not present, the MS shall report only one signal type for each GANSS. + +If SMLC has indicated supported signal types in Positioning Capability Request, the MS shall only report signals that are supported by SMLC. + +#### A.2.2.5 Extended Reference IE + +This element is mandatory in any RRLP Measure Position Request component, any RRLP Assistance Data component, any RRLP Positioning Capability Request component and any RRLP Positioning Capability response component. + +NOTE: For reasons of backward compatibility, the IE is not defined for a Release 4 or earlier SMLC and would be ignored, when received, by a Release 4 or earlier MS. Additionally, other requirements associated with this IE would not be supported by a Release 4 or earlier MS or SMLC. + +The Extended Reference IE contains the following elements: + +- SMLC code: an integer in the range 0-63 distinguishing any SMLC from other neighbour SMLCs in the same Routing Area. Each SMLC is assigned a specific SMLC ID value. The values assigned to neighbour SMLCs in the same Routing Area between which inter-NSE cell change is possible should be different. +- Transaction ID: an integer in the range 0-262143 distinguishing different RRLP transactions in different MSs currently being served by the same SMLC. An SMLC shall assign a different transaction ID to each currently open RRLP transaction for positioning and assistance data delivery among all target MSs. When any RRLP transaction for any MS is completed in the SMLC (e.g. the MS has sent a correctly formatted RRLP Measure Position Response or Assistance Data Ack.) or if the transaction is aborted (e.g. SMLC timeout on an RRLP response), the associated transaction ID value shall become free and may be later assigned to a new RRLP transaction by the SMLC. When any transaction ID value becomes free, an SMLC should attempt to wait for at least 128 seconds (the maximum defined RRLP response time from an MS) before reassigning the same value. + +## A.3 Measure Position Response + +### A.3.1 General + +The Measure Position Response is a RRLP component from the MS to the network. It is the response to the Measure Position Request. It contains the following elements. One of the five elements containing measurement data or location estimate (*E-OTD Measurement Information*, *Location Information*, *GPS Measurement Information*, *GANSS Measurement Information* or *GANSS Location Information*) or *Location Information Error element* must be included. + +**Table A.2: Measure Position Response component content** + +| Element | Type/Reference | Presence | +|--------------------------------------------|--------------------------------------------------|----------| +| Multiple Sets | Multiple Sets 3.2.1 | O | +| Reference BTS Identity | Reference BTS Identity 3.2.2 | O | +| E-OTD Measurement Information | E-OTD Measurement Information 3.2.3 | O | +| Location Information | Location Information 3.2.4 | O | +| GPS Measurement Information | GPS Measurement Information 3.2.5 | O | +| Location Information Error | Location Information Error 3.2.6 | C | +| GPS Time Assistance Measurements | GPS Time Assistance Measurements 3.2.6a | O | +| Velocity Estimate | Velocity Estimate 3.2.6b | O | +| Extended Reference | Extended Reference 3.2.7 | C | +| Uplink RRLP Pseudo Segmentation Indication | Uplink RRLP Pseudo Segmentation Indication 3.2.8 | C | +| GANSS Location Information | GANSS Location Information 3.2.9 | O | +| GANSS Measurement Information | GANSS Measurement Information 3.2.10 | O | + +### A.3.2 Elements + +#### A.3.2.1 Multiple Sets Element + +This element indicates how many E-OTD Measurement Information sets, GPS Measurement Information sets or GANSS Measurement Information sets, and Reference BTS Identities are included to this element. This element is optional. If this element is absent, a single measurement set is included. + +##### Number of E-OTD/GPS/GANSS Measurement Information Sets + +This field indicates the number of *Number of E-OTD/GPS/GANSS Measurement Information* sets included to this component. This field is mandatory. If two or more types of measurement elements are present, then there are the equal number of them, and each pair has the same reference BTS. + +Range: 2 - 3 + +##### Number of Reference BTS + +This field indicates the number of reference BTSs used in this component. This field is mandatory. + +Range: 1-3 + +##### Reference BTS relation to Measurement Elements + +This field indicates how the reference BTSs listed in this element relate to measurement sets later in this component. This field is conditional and included only if Number of E-OTD/GPS/GANSS Measurement Information Sets is '3' and Number of Reference BTSs is '2'. + +'0' = First reference BTS is related to first and second E-OTD/GPS/GANSS Measurement Information Sets, and second reference BTS is related to third E-OTD/GPS Measurement Information Sets. + +'1' = First reference BTS is related to first and third E-OTD/GPS/GANSS Measurement Information Sets, and second reference BTS is related to second E-OTD/GPS/GANSS Measurement Information Sets. + +'2' = First reference BTS is related to first E-OTD/GPS/GANSS Measurement Information Sets, and second reference BTS is related to second and third E-OTD/GPS/GANSS Measurement Information Sets. + +If this field is not included, the relation between reference BTS and Number of E-OTD/GPS/GANSS Measurement Information Sets is as follows: + +- if there are three sets and three reference BTSs -> First reference BTS relates to first set, second reference BTS relates to second set, and third reference BTS relates to third set; +- if there are two sets and two reference BTS -> First reference BTS relates to first set, and second reference BTS relates to second set; +- if there is only one reference BTS and 1-3 sets -> this reference BTS relates to all sets. + +#### A.3.2.2 Reference BTS Identity Element + +This element identifies the reference BTS(s). This element is conditional to the number of reference BTSs. It is mandatory, if there is more than one reference BTS, and optional otherwise. If this element is not included, the Reference BTS, used in other elements, is the current serving BTS of MS. If this element is included, the BTSs defined here are used as Reference BTSs in all other elements. + +*The following fields are repeated for the number of reference BTSs included in the Number of Reference BTS field.* + +##### CellIdType + +This field indicates is the identity method of the Reference BTS. This field is mandatory within this element. + +'0' = Cell identity is told using BSIC and BCCH carrier. + +'1' = Cell identity is told using CI, and the LAC is the same as the current serving BTS. + +'2' = Cell identity is told using an index referring to the BTS listed in the Measure Position Request component (the indicated reference BTS is 1) + +'3' = Cell identity is told using an index referring to the BTS listed in the BCCH allocation list (System Information Neighbor Lists) of the serving BTS. This type of reference identity shall not be used by the MS unless it has received the "E-OTD Measurement Assistance Data for System Information List Element" from the SMLC for this cell. + +'4' = Cell identity is told using CI, and the LAC. + +##### Reference LAC + +This field indicates the Location Area Code of the reference BTS. The purpose of the Location Area Code is to identify a location area. This field is conditional, and included, if CellIDType field is '4'. + +Range: 0 - 65535 + +##### Reference CI + +This field indicates the Cell Identity value of the reference BTS. The purpose of the Cell Identity value is to identify a cell within a location area. This field is conditional, and included, if CellIDType field is '1' or '4'. + +Range: 0 - 65535 + +##### Reference BCCH Carrier + +This field indicates the absolute RF channel number of the BCCH of the reference base station. BCCH carrier field is conditional and is included only if CellIDType is set '0'. + +Range: 0 - 1023 + +##### Reference BSIC + +This field indicates the BSIC (Base Station Identity Code of the base station). + +BSIC field is conditional and is included only if CellIDType is set '0' or '3'. + +Range: 0 - 63 + +##### Request Index + +This field indicates an index identifying the reference BTS by referring to the BTSs listed in the Measure Position Request component (the indicated reference BTS in the Measure Position Request component has the index value 1, and possible next BTS '2', and so on ) + +This field is conditional and included only if CellIDType is set to '2'. + +Range: 1-16 + +##### System Info Index + +This field indicates an index identifying the reference BTS by referring to the BCCH allocation list (System Information Neighbor List) of the serving BTS . + +This field is conditional and included only if CellIDType is set to '3'. + +Range: 1-32 + +#### A.3.2.3 E-OTD Measurement Information Element + +The purpose of the E-OTD Measurement Information element is to provide OTD measurements of signals sent from the reference and neighbor based stations. The length of this element depends on the number of neighbor cells for which OTD measurements have been collected. This element is optional in the Measure Position Response component. It is included in the Measure Position Response component, if the network has requested the mobile to perform the MS assisted E-OTD method. BTSs which cannot be measured or whose measurements are excessively inaccurate need not be reported. The MS may include measurements for other BTSs not given in the assistance data by the SMLC. + +The E-OTD and 51 multiframe offset values are reported relative to the reference BTS as defined in the previous sub-clauses. + +The following fields are repeated for each measurement set. + +##### Reference Frame Number + +This field indicates the frame number of the last measured burst from the reference BTS modulo 42432. This information can be used as a time stamp for the measurements. This field is mandatory. + +Range: 0 - 42431 + +##### Reference Time Slot + +Reference Time Slot indicates the time slot modulo 4 relative to which the MS reports the reference BTS measurements. This field is mandatory. + +Range: 0 to 3 + +NOTE 1: If MS does not know timeslot scheme, the MS reports the used timeslot. MS can only report results based on one time slot (N) or two time slots (N and N+4). If the MS knows the timeslot scheme, it can make measurements from several timeslots and reports that the used timeslot is zero (and makes correction). + +##### Reference Quality + +Reference Quality field includes the standard deviation of the TOA measurements from the reference BTS with respect to $T_{\text{Ref}}$ (where $T_{\text{Ref}}$ is the time of arrival of signal from the reference BTS used to calculate the OTD values). This field is optional. The Reference Quality field can be used to evaluate the reliability of E-OTD measurements in the SMLC and in weighting of the E-OTD values in the location calculation. + +Following linear 5 bit encoding is used: + +| | | +|---------|-----------------------| +| '00000' | 0 - (R*1-1) meters; | +| '00001' | R*1 - (R*2-1) meters; | +| '00010' | R*2 - (R*3-1) meters; | +| ... | | +| '11111' | R*31 meters or more. | + +where R is the resolution defined by Std Resolution field. For example, if R=20 meters, corresponding values are 0 - 19 meters, 20 - 39 meters, 40 - 59 meters, ..., 620+ meters. + +##### Number of Measurements + +Number of Measurements for the Reference Quality field is used together with Reference Quality to define quality of the reference base site TOA. The field indicates how many measurements have been used in the MS to define the standard deviation of the measurements. Following 3 bit encoding is used: + +| | | +|--------|-------------| +| '000': | 2-4; | +| '001': | 5-9; | +| '010': | 10-14; | +| '011': | 15-24; | +| '100': | 25-34; | +| '101': | 35-44; | +| '110': | 45-54; | +| '111': | 55 or more. | + +This field is optional. + +##### Std Resolution + +Std Resolution field includes the resolution used in Reference Quality field and Std of EOTD Measurements field. Encoding on 2 bits as follows: + +| | | +|------|------------| +| '00' | 10 meters; | +| '01' | 20 meters; | +| '10' | 30 meters; | +| '11' | Reserved. | + +This field is mandatory. + +##### TA Correction + +This field indicates the estimate of the time difference between the moment that the MS uses to adjust its internal timing for reception and transmission (e.g. corresponding to maximum energy) and the estimate of the reception of the first arriving component from the serving BTS. This value can be used as a correction by the SMLC to the Timing Advance (TA) value when the distance between the MS and the serving BTS is estimated based on TA. + +The value *TACor* in this field corresponds to the TA Correction in bit periods as follows: + +- TA Correction in bit periods = $TACor/64 - 8$ . + +TA Correction has the resolution of 1/64 bit period, and the range - 8 ... +7 bit periods. Negative TA Correction in bits indicates that the first signal component from the serving BTS is estimated to arrive before the moment used for communication. This field is optional. + +Range: 0-960 + +##### Number of Measured Neighbors + +This field indicates the number of different neighbor BTSs. This field is mandatory. + +Range: 0 - 10 + +NOTE 2: If the MS can not measure any neighbor BTSs, then this value is set to '0'. + +*The following fields are repeated for the number of BTSs included in the Number of Measured Neighbors field.* + +##### Neighbor Identity Present + +The presence of this field is conditional, it shall not be present in the first set. It is mandatory for the other sets. This field indicates whether the identity information (i.e. CellIDType and possibly Neighbor CI / Neighbor BCCH Carrier / Neighbor BSIC / Neighbor Multiframe Offset / Request Index / System Info Index fields) concerning a certain BTS is present or whether the BTS identity is given as reference to the first measurement set. + +'0' Identity information not included, and identity of this BTS is same as the identity of BTS in first set with same sequence number. + +'1' Identity information is included. + +##### CellIDType + +This field indicates the identity method of the cell. This field is conditional, and included if Neighbor Identity Present is '1'. If CellIDType field is not present, the following fields can not be present either: Neighbor CI, Neighbor BCCH Carrier, Neighbor BSIC, Neighbor Multiframe Offset, Request Index, System Info Index. + +'0' = Cell identity is told using BSIC and BCCH carrier. + +'1' = Cell identity is told using CI, and the LAC is the same as the current serving BTS. + +'2' = Cell identity is told using 51 Multiframe offset and BCCH carrier. + +'3' = Cell identity is told using an index referring to the BTS listed in the Measure Position Request component (the indicated reference BTS is 1). + +'4' = Cell identity is told using an index referring to the BTS listed in the BCCH allocation list (System Information Neighbor Lists) of the serving BTS. This type of neighbor identity shall not be used by the MS unless it has received the "E-OTD Measurement Assistance Data for System Information List Element" from the SMLC for this cell. + +'5' = Cell identity is told using CI and the LAC. + +NOTE: The MS can decide which of these methods to use. The CellIDType '3' and '4' are preferred. + +##### Neighbor LAC + +This field indicates the Location Area Code of the neighbor BTS. The purpose of the Location Area Code is to identify a location area. This field is conditional, and included, if CellIDType field is '5'. + +Range: 0 - 65535 + +##### Neighbor CI + +This field indicates the Cell Identity of the particular neighbor cell. The purpose of the Cell Identity value is to identify a cell within a location area. + +Neighbor CI field is conditional and is included only if CellIdType is set '1' or '5' and the CI value of the given cell is available. + +Range: 0 - 65535 + +##### Neighbor BCCH Carrier + +This field indicates the absolute RF channel number of the BCCH of the neighbor base station. BCCH carrier field is conditional and is included only if CellIdType is set '0' or '2'. + +Range: 0 - 1023 + +##### Neighbor BSIC + +This field indicates the BSIC (Base Station Identity Code of the base station). + +BSIC field is conditional and is included only if CellIdType is set '0' or '4'. + +Range: 0 - 63 + +##### Neighbor Multiframe Offset + +This field indicates the frame difference between the start of the 51 multiframes frames arriving from this BTS and the reference BTS. The multiframe offset is defined as $T_{BTS} - T_{Ref}$ , where $T_{BTS}$ is the time of the start of the 51 multiframe in the BTS in question, and $T_{Ref}$ is the time of the start of the 51 multiframe in the reference BTS. This field is conditional and included only if CellIdType is set to '2'. + +Range: 0 - 51 + +##### Request Index + +This field indicates an index identifying the reference BTS by referring to the BTSs listed in the Measure Position Request component (the indicated reference BTS in the Measure Position Request component has the index value 1, and possible next BTS '2', and so on). + +This field is conditional and included only if CellIdType is set to '3'. + +Range: 1-16 + +##### System Info Index + +This field indicates an index identifying the reference BTS by referring to the BCCH allocation list (System Information Neighbor List) of the serving BTS. + +This field is conditional and included only if CellIdType is set to '4'. + +Range: 1-32 + +##### Neighbor Time Slot + +Neighbor Time Slot indicates the time slot modulo 4 relative to which the MS reports the neighbor BTS measurements. This field is mandatory. + +Range: 0 to 3 + +NOTE 3: If the MS does not know the timeslot scheme, the MS reports the used timeslot. MS can only report a result based on one time slot (N) or two time slots (N and N+4). If the MS knows the timeslot scheme, the MS can make measurements from several timeslots and reports that the used timeslot is zero (and makes correction). + +##### Number of EOTD Measurements + +Number of Measurements field is used together with Std of EOTD Measurements field to define quality of a reported EOTD measurement. The field indicates how many EOTD measurements have been used in the MS to define the standard deviation of these measurements. Following 3 bit encoding is used. + +'000': 2-4; + +| | | +|--------|-------------| +| '001': | 5-9; | +| '010': | 10-14; | +| '011': | 15-24; | +| '100': | 25-34; | +| '101': | 35-44; | +| '110': | 45-54; | +| '111': | 55 or more. | + +This field is mandatory. + +##### Std of EOTD Measurements + +**Std of EOTD Measurements** field includes standard deviation of EOTD measurements. This field is mandatory. It can be used to evaluate the reliability of EOTD measurements in the SMLC and in weighting of the OTD values in location calculation. + +Following linear 5 bit encoding is used: + +| | | +|---------|-------------------------| +| '00000' | $0 - (R*1-1)$ meters; | +| '00001' | $R*1 - (R*2-1)$ meters; | +| '00010' | $R*2 - (R*3-1)$ meters; | +| ... | | +| '11111' | $R*31$ meters or more. | + +where R is the resolution defined by Std Resolution field. For example, if R=20 meters, corresponding values are 0 - 19 meters, 20 - 39 meters, 40 - 59 meters, ..., 620+ meters. + +##### OTD + +This field indicates the measured OTD value between the receptions of signals from the reference and the neighbor BTS. The OTD is defined as $T_{Nbor} - T_{Ref}$ (modulo burst length) where $T_{Nbor}$ is the time of arrival of signal from the neighbor BTS, and $T_{Ref}$ is the time of arrival of signal from the reference BTS. The reporting resolution of the OTD value is 1/256 bit. This field is mandatory. + +Range: 0 - 39999 + +#### A.3.2.3a E-OTD Measurement Extended Information Element + +The purpose of the E-OTD Measurement Ext Information element is to provide OTD measurements of signals sent from the reference and neighbour base stations. The length of this element depends on the number of neighbour cells for which OTD measurements have been collected. This element is optional in the Measure Position Response component. It is included in the Measure Position Response component, if E-OTD measurements didn't fit in the E-OTD Measurement Information Element. + +The E-OTD and 51 multiframe offset values are reported relative to the reference BTS as defined in the previous sub-clauses. + +The following fields are valid only for the first set of measurements + +##### Number of Measured Neighbors + +This field indicates the number of different neighbor BTSs. This field is mandatory. + +Range: 0 - 5 + +NOTE: If the MS can not measure any neighbor BTSs, then this value is set to '0'. + +*The following fields are repeated for the number of BTSs included in the Number of Measured Neighbors field. They are defined in the previous sub-clause :* + +- CellIdType, +- Neighbor LAC, +- Neighbor CI, +- Neighbor BCCH Carrier, +- Neighbor BSIC, +- Neighbor Multiframe Offset, +- Request Index, +- System Info Index, +- Neighbor Time Slot, +- Number of EOTD Measurements, +- Std of EOTD Measurements, +- OTD + +#### A.3.2.4 Location Information Element + +The purpose of Location Information element is to provide the location estimate from the MS to the network, if the MS is capable of determining its own position. Optionally, the element may contain the velocity parameters computed by the MS. + +This element is optional. This element contains the following fields. + +##### Reference Frame + +This field specifies the reference BTS Reference Frame number during which the location estimate was measured. The time of the Reference Frame boundary is as observed by the MS, ie without Timing Advance compensation. This field is mandatory. However, if the Reference Frame number is within (42432..65535), the value of this field shall be ignored and in that case the MS should provide GPS TOW if available. + +**Table A.3: Reference Frame field contents** + +| Parameter | # of Bits | Resolution | Range | Units | +|-----------------|-----------|------------|-----------|--------| +| Reference Frame | 16 | --- | 0 - 65535 | frames | + +Note that expected values for Reference Frame are in range 0 - 42431. + +##### GPS TOW + +This field specifies the GPS TOW for which the location estimate is valid , rounded down to the nearest millisecond unit. This field is optional but shall be included if GPS Time Assistance Measurements are included. If GPS Time Assistance Measurements are included in the RRLP Measure Position Response, the MS shall align GPS System time (as defined by the GPS TOW and the GPS TOW Subms fields) with the reported GSM frame boundary observed by the MS at that time. + +**Table A.4: GPS TOW field contents** + +| Parameter | # of Bits | Resolution | Range | Units | +|-----------|-----------|------------|--------------|-------| +| GPS TOW | 24 | 1 ms | 0 - 14399999 | ms | + +The 24 bits of GPS TOW are the least significant bits. The most significant bits shall be derived by the Serving Mobile Location Center to unambiguously derive the GPS TOW. + +##### Fix Type + +This field contains an indication as to the type of measurements performed by the MS: 2D or 3D. This field is mandatory. + +'0' = 2D fix. + +'1' = 3D fix. + +##### Position Estimate + +This field contains the calculated position estimate in the format defined in 3GPP TS 23.032. The allowed shapes are: + +- ellipsoid Point; +- ellipsoid point with uncertainty circle; +- ellipsoid point with uncertainty ellipse; +- ellipsoid point with altitude and uncertainty ellipsoid. + +#### A.3.2.5 GPS Measurement Information Element + +The purpose of the GPS Measurement Information element is to provide GPS measurement information from the MS to the SMLC. This information includes the measurements of code phase and Doppler, which enables the network-based GPS method where position is computed in the SMLC. The proposed contents are shown in table A.5, and the individual fields are described subsequently. See also Figure A.1 for an illustration of the relation between some of the fields. + +![Timing diagram showing GPS System Time, SV #1 time, SV #N_SAT time, and MS observations with clock biases and measurement information fields.](f8da9cefc5f8a04f9ffb8f6c49aa03e2_img.jpg) + +The diagram illustrates the timing relationships for GPS measurement information fields. It shows how GPS System Time, satellite times (SV #1 and SV #N\_SAT), and mobile station (MS) observations relate to each other, accounting for clock biases and rounding. + +**GPS System Time:** Shown as a sequence of milliseconds (211 to 217). A 1 C/A code (1023 chips, 1 ms) duration is indicated. SV #1 clock bias is shown as the offset between GPS Time t and SV #1 time tsv1. + +**At SV#1:** SV #1 time tsv1 is shown as a sequence of milliseconds (211 to 217). + +**At SV#N\_SAT:** SV #N\_SAT time tsvn\_sat is shown as a sequence of milliseconds (211 to 217). SV #N\_SAT clock bias is shown as the offset between GPS Time t and SV #N\_SAT time tsvn\_sat. + +**At MS:** + +- "GPS TOW" Estimate:** Shown as a sequence of milliseconds (211 to 217). A note indicates: "Reported GPS TOW rounded down to nearest millisecond unit." +- Serving BTS clock (frame number FN):** Shows frame numbers 2580215 and 2580216. +- Observed SV#1 time tsv\_1:** Shown as a sequence of milliseconds (141 to 147). The offset from the reference epoch is labeled as ~370 chips. +- GPS measurement information:** + - GPS TOW = 214ms + - Whole chips SV #1 ~ 370 chips + - ... + - Whole chips SV #N\_SAT ~ 220 chips + - Reference Frame = 34296 (2580216 mod 42432) + - Reference Frame MSB = 60 (2580216 div 42432) + - DeltaTOW = GPS TOW - tsv\_1 = 214-144 = 70 +- Observed SV#nsat time tsv\_nsat:** Shown as a sequence of milliseconds (133 to 139). The offset from the reference epoch is labeled as ~220 chips. + +A vertical dashed line marks the **Chosen reference epoch for GPS measurement information**. + +Timing diagram showing GPS System Time, SV #1 time, SV #N\_SAT time, and MS observations with clock biases and measurement information fields. + +Figure A.1. Exemplary definitions of GPS measurement information fields. + +This element is included in the Measure Position Response component if the network has requested the mobile to perform mobile-assisted location measurements using a GPS location method. + +Following fields are repeated a number of times told in Number of E-OTD/GPS Measurement Sets field if Multiple Sets element is included. If Multiple Sets element is not included, the default value for sets is one (i.e. the following fields are present only once). + +**Table A.5: GPS Measurement Information element content** + +| Element fields | Presence | Occurrences | +|----------------------------------|----------|--------------| +| Reference Frame | O | 1 | +| GPS TOW | M | 1 | +| # of Satellites ( N_SAT ) | M | 1 | +| Measurement Parameters | M | N_SAT | + +The following paragraphs describe the content of each information field of this element. + +##### Reference Frame + +This field is optional. + +**Table A.6: Reference Frame field contents** + +| Parameter | # of Bits | Resolution | Range | Units | +|-----------------|-----------|------------|-----------|--------| +| Reference Frame | 16 | --- | 0 - 65535 | frames | + +Note that expected values for Reference Frame are in range 0 - 42431. If Reference Frame and GPS Time Assistance Measurements both are included in the RRLP Measure Position Response, the code phase measurements shall be aligned with the reported GSM frame boundary observed by the MS at that time, as indicated in Figure A.1. The time of the Reference Frame boundary is as observed by the MS, ie without Timing Advance compensation. + +##### GPS TOW + +This field specifies the GPS TOW for which the location estimate is valid, rounded down to the nearest millisecond unit. This field is mandatory. + +**Table A.7: GPS TOW field contents** + +| Parameter | # of Bits | Resolution | Range | Units | +|-----------|-----------|------------|--------------|-------| +| GPS TOW | 24 | 1 ms | 0 - 14399999 | ms | + +The 24 bits of GPS TOW are the least significant bits. The most significant bits shall be derived by the Serving Mobile Location Center to unambiguously derive the GPS TOW. + +NOTE: The GPS Reference Time Uncertainty, if present, indicates the accuracy of GPSTOW, as described in sub-clause A.3.2.6.a. + +##### # of Satellites (*N\_SAT*) + +##### Number of Measurements + +This field specifies the number of measurements for which measurements satellites are provided in the component. This value represents the number of satellites that were measured by the MS. This value of *N\_SAT* determines the length of the payload portion of the component. Typical range for *N\_SAT* is four to a maximum of 12. This field is mandatory and occurs once per set. + +**Table A.7a: # of Satellites field contents** + +| Parameter | # of Bits | Resolution | Range | Units | +|--------------|-----------|------------|--------|-------| +| N_SAT | 4 | --- | 1 - 16 | --- | + +##### Measurement Parameters + +This field contains information about the measurements of code phase and Doppler, which enables the network-based method where position is computed in the SMLC. This field is mandatory and occurs $N\_SAT$ times per message. + +**Table A.8: Measurement Parameters field contents** + +| Parameter | # of Bits | Resolution | Range | Units | +|-----------------------|-----------|-----------------------------|---------------------|-------| +| Satellite ID | 6 | --- | 0 - 63 | --- | +| C/N 0 | 6 | 1 | 0 - 63 | dB-Hz | +| Doppler | 16 | 0,2 | ±6553,6 | Hz | +| Whole Chips | 10 | 1 | 0 - 1022 | chips | +| Fractional Chips | 11 | $2^{-10}$ | 0 - (1- $2^{-10}$ ) | chips | +| Multipath Indicator | 2 | see Table A.9 | TBD | --- | +| Pseudorange RMS Error | 6 | 3 bit mantissa
3 bit exp | 0,5 - 112 | m | + +###### Satellite ID + +This field identifies the particular satellite for which the measurement data is valid. This values 0 - 63 represent satellite PRNs 1 - 64, respectively. + +###### C/N0 + +This field contains the estimate of the carrier-to-noise ratio of the received signal from the particular satellite used in the measurement. It is given in whole dBs and has a range of 0 to 63. Typical levels observed by MS-based GPS units will be in the range of 20 dB to 50 dB. + +##### Doppler + +This field contains the Doppler measured by the MS for the particular satellite signal. This information can be used to compute the 3-D velocity of the MS. The Doppler range is sufficient to cover the potential range of values measured by the MS. + +##### Whole Chips + +This field contains the whole value of the code-phase measurement made by the MS for the particular satellite signal at the time of measurement, in units of 1 GPS chip in the range from 0 to 1022 chips, where increasing binary values of the field signify increasing measured pseudoranges. The code phase measurement is divided into two fields, "Whole Chips" and "Fractional Chips". + +###### Fractional Chips + +This field contains the fractional value of the code-phase measurement made by the MS for the particular satellite signal at the time of measurement. The resolution of the fractional portion is approximately 0,3 m. + +NOTE: The actual ASN.1 coding of this field reserves 11 bits for legacy compatibility. Only the 10 least significant bits are actually required to code the values (0..1023) + +##### Multipath Indicator + +This field contains the Multipath Indicator value. This parameter is specified according to the representation described in table A.9. + +**Table A.9: Multipath Indicator values and associated indications** + +| Value | Multipath Indication | +|-------|-----------------------------| +| 00 | Not measured | +| 01 | Low, MP error < 5m | +| 10 | Medium, 5m < MP error < 43m | +| 11 | High, MP error > 43m | + +Range: 0 - 3 + +##### Pseudorange RMS Error + +This field contains a Pseudorange RMS Error value. + +Range: 0,5 m to 112 m + +NOTE: This parameter is specified according to a floating-point representation as described in Table A.10. + +**Table A.10: Pseudorange RMS Error representation** + +| Index | Mantissa | Exponent | Floating-Point value, $x_i$ | Pseudorange value, $P$ | +|-------|----------|----------|---------------------------------|------------------------| +| 0 | 000 | 000 | 0,5 | $P < 0,5$ | +| 1 | 001 | 000 | 0,5625 | $0,5 \leq P < 0,5625$ | +| $i$ | $x$ | $y$ | $0,5 \cdot (1 + x/8) \cdot 2^y$ | $x_{i-1} \leq P < x_i$ | +| 62 | 110 | 111 | 112 | $104 \leq P < 112$ | +| 63 | 111 | 111 | -- | $112 \leq P$ | + +#### A.3.2.6 Location Information Error Element + +The purpose of Location Information Error element is to provide the indication of error and the reason for it, when the MS can not perform the required location or the network can not determine the position estimate. The element may also indicate what further assistance data may be needed by the target MS to produce a successful location estimate or location measurements. This element is optional. This element has the following fields. + +##### Error Reason + +This field indicates the reason for error. This field is mandatory. + +- '0': Undefined error. +- '1': There were not enough BTSs to be received when performing mobile based E-OTD. +- '2': There were not enough GPS satellites to be received, when performing GPS location. +- '3': E-OTD location calculation assistance data missing. +- '4': E-OTD assistance data missing. +- '5': GPS location calculation assistance data missing. +- '6': GPS assistance data missing. +- '7': Requested method not supported. +- '8': Location request not processed. +- '9': Reference BTS for GPS is not the serving BTS. +- '10': Reference BTS for E-OTD is not the serving BTS. +- '11': There were not enough GANSS satellites received, when performing GANSS location. +- '12': GANSS assistance data missing. +- '13': Reference BTS for GANSS is not the serving BTS. + +##### Additional Assistance Data + +This field is optional. Its presence indicates that the target MS will retain assistance data already sent by the SMLC. The SMLC may send further assistance data for any new location attempt but need not resend previous assistance data. The field may contain the following: + +- GPS Assistance Data: Necessary additional GPS assistance data (structure and encoding as for the GPS Assistance Data IE in 3GPP TS 49.031 excluding the IEI and length octets) +- GANSS Assistance Data: Necessary additional GANSS assistance data (structure and encoding as for the GANSS Assistance Data IE in 3GPP TS 49.031 excluding the IEI and length octets) + +#### A.3.2.6a GPS Time Assistance Measurements Element + +This IE contains measurements that are used to define an accurate relation between GSM and GPS time or to provide additional GPS TOW information for MS Assisted A-GPS. The contents are shown in Table A.10a, and the individual fields are described subsequently. + +**Table A.10a: GPS Time Assistance Measurements Information element content** + +| Element fields | Presence | +|--------------------------------|----------| +| Reference Frame MSB | O | +| GPS TOW Subms | O | +| Delta TOW | O | +| GPS Reference Time Uncertainty | O | + +##### **Reference Frame MSB** + +This field shall be included when GPS-GSM time association is provided for either MS Based A-GPS or MS Assisted A-GPS. It indicates the Most Significant Bits (MSBs) of the frame number of the reference BTS corresponding to the GPS measurement or location estimate. Starting from the complete GSM frame number denoted FN, the MS calculates Reference Frame MSB as + +$$\text{Reference Frame MSB} = \text{floor}(\text{FN}/42432)$$ + +The complete GSM frame number FN can then be reconstructed in the SMLC by combining the fields Reference Frame with Reference Frame MSB in the following way + +$$\text{FN} = \text{Reference Frame MSB} * 42432 + \text{Reference Frame}$$ + +Range: 0-63 + +##### **GPS TOW Subms** + +This field is only applicable for MS-Based A-GPS. This field indicates in units of 100ns the submillisecond part of the GPS time of measurement. This field together with the GPS TOW field in the Location Information Element provides a more accurate time stamp of the location estimate for MS based AGPS Expressed in units of microseconds. The precise GPS time of measurements in milliseconds is thus equal to + +$$\text{GPS TOW} + 0,0001 * \text{GPS TOW Subms}$$ + +The estimation of precise GPS time of measurement using AGPS is vulnerable to millisecond ambiguities. Therefore the MS shall only report this field when it is confident that any millisecond ambiguities have been avoided. + +Range: 0-9999 + +##### **Delta TOW** + +This field is only applicable for MS-Assisted A-GPS. This field specifies the difference in milliseconds between the GPS TOW reported in the GPS Measurement Information Element and the millisecond part of the SV time tsv\_1 of the first SV in the list reported from the MS. Figure A.1 shows an example of Delta TOW calculation. The Delta TOW is defined as $\text{Delta TOW} = \text{GPS TOW} - \text{fix}(\text{tsv\_1})$ + +where $\text{fix}()$ denotes rounding to the nearest integer towards zero. The estimation of $\text{tsv\_1}$ which forms the basis for the calculation of Delta TOW is vulnerable to millisecond ambiguities. Therefore the MS shall only report this field when it is confident that the correct millisecond event has been recovered. + +Range: 0-127 + +##### **GPS Reference Time Uncertainty** + +This element is optional. It provides the accuracy of the relation GPS and GSM time in the Location Information or GPS Measurement Information Element when GPS-GSM time association is provided. For MS Assisted A-GPS when GPS-GSM time association is not provided, even if GPS Time Assistance Measurement Request is not included in the Measure Position Request, this element can be included to provide the accuracy of the reported GPS TOW. The interval, range and treatment is as described in sub-clause 2.2.4b. + +#### **A.3.2.6b Velocity Estimate Element** + +This field contains the calculated velocity estimate in the format defined in 3GPP TS 23.032. The allowed encodings are: + +- Horizontal Velocity + +- Horizontal with Vertical Velocity +- Horizontal Velocity with uncertainty +- Horizontal with Vertical Velocity and uncertainty + +#### A.3.2.7 Extended Reference IE + +This IE shall be included in any Measure Position Response if and only if an Extended Reference IE was received in the corresponding previous Measure Position Request message. + +NOTE: For reasons of backward compatibility, a Release 4 or earlier MS will not include this IE. + +The Extended Reference IE contains the following elements. + +SMLC code: an integer in the range 0-63. The value returned by a target MS in a Measure Position Response shall equal the value received from the SMLC in the earlier Measure Position Request. + +Transaction ID: an integer in the range 0-262143 distinguishing different RRLP transactions in different MSs currently being served by the same SMLC. The value returned by a target MS in a Measure Position Response shall equal the value received from the SMLC in the earlier Measure Position Request. + +When an MS employs pseudo-segmentation to return an RRLP response, the same Extended Reference IE shall be included in each RRLP Measure Position Response component. + +#### A.3.2.8 Uplink RRLP Pseudo Segmentation Indication + +This element is included by the MS when up-link RRLP pseudo-segmentation is used. In the first segment, 'first of many' is indicated and in the second 'second of many' is indicated. It is not included when up-link pseudo-segmentation is not used. + +#### A.3.2.9 GANSS Location Information Element + +The purpose of GANSS Location Information element is to provide the GANSS location estimate from the MS to the SMLC, if the MS is capable of determining its own position. Optionally, the element may contain Reference Frame element for including accurate relation between the cellular frame and GANSS Time of Day (TOD) for the serving cell if requested by the SMLC. + +If GANSS Positioning Method was included in a Measure Position Request component, this field shall be used to report the location estimate from the MS to the network. + +The time reference of GANSS TOD in GANSS Location Information Element can be any GNSS specific system time. The time reference is indicated by GANSS\_TIME\_ID. + +The contents of GANSS Location Information are shown in Table A.10.1, and the individual fields are described subsequently. + +**Table A.10.1: GANSS Location Information Element Content** + +| Element fields | Presence | +|---------------------------------------------------------------------------------------------------------------------------------|------------| +| Reference Frame | O (note 1) | +| GANSS TOD | O (note 1) | +| GANSS TOD Frac | O | +| GANSS TOD Uncertainty | O | +| GANSS_TIME_ID | O (note 2) | +| Fix Type | M | +| Position Data | M | +| Stationary Indication | O | +| Location Estimate | M | +| NOTE 1: Either Reference Frame or GANSS Reference Time shall always be included.
NOTE 2: Absence of this field means Galileo | | + +This element contains Reference FN and Reference FN MSB fields. Reference FN field specifies the reference BTS reference frame number during which the location estimate was measured. The time of the reference frame boundary is as observed by the MS, i.e. without Timing Advance compensation. + +Note that expected values for Reference FN are in range 0 - 42431. + +Reference FN MSB field specifies the Most Significant Bits (MSB) of the frame number of the reference BTS corresponding to the GANSS Measurement Information or Location Estimate. Starting from the complete GSM frame number denoted FN, the MS calculates Reference FN MSB as + +$$\text{Reference FN MSB} = \text{floor}(\text{FN}/42432)$$ + +The complete GSM frame number FN can then be reconstructed in the SMLC by combining the fields Reference Frame with Reference FN MSB in the following way + +$$\text{FN} = \text{Reference FN MSB} * 42432 + \text{Reference FN}$$ + +Range: 0-63 + +**Table A.10.2: Reference Frame field contents** + +| Parameter | # of Bits | Resolution | Range | Unit | Incl. | +|------------------|-----------|------------|-----------|-------|-------| +| Reference FN | 16 | --- | 0 - 65535 | frame | M | +| Reference FN MSB | 6 | --- | 0 - 63 | frame | O | + +##### GANSS TOD + +This field specifies the time for which the location estimate is valid, rounded down to the nearest integer millisecond. This field is optional but shall be included if GANSS TOD - GSM time association is included in which case the MS shall align GANSS TOD with the reported GSM frame boundary observed by the MS at that time. The time reference of GANSS TOD is indicated by GANSS\_TIME\_ID. + +**Table A.10.3: GANSS TOD contents** + +| Parameter | # of Bits | Resolution | Range | Unit | +|-----------|-----------|------------|-------------|------| +| GANSS TOD | 22 | 1 | 0 - 3599999 | ms | + +The 22 bits of GANSS TOD are the least significant bits. The most significant bits shall be derived by the SMLC to unambiguously derive the GANSS TOD. + +##### GANSS TOD Frac + +This field is the submillisecond part of the GANSS time of day. This field together with the GANSS TOD field provides a more accurate time stamp of the Location Estimate having resolution of ~61 ns. This field is optional but shall be included if GANSS TOD - GSM time association is included. + +**Table A.10.4: GANSS TOD Frac contents** + +| Parameter | # of Bits | Resolution | Range | Unit | +|----------------|-----------|------------|-------------------|------| +| GANSS TOD Frac | 14 | $2^{-14}$ | 0 - $(1-2^{-14})$ | ms | + +##### GANSS TOD Uncertainty + +This parameter provides the accuracy of the relation between GANSS TOD and GSM time if GANSS TOD- GSM time association is provided. When GANSS TOD-GSM time association is not provided, this element can be included to provide the accuracy of the reported GANSS TOD. + +The uncertainty $r$ , expressed in microseconds, is mapped to a number $K$ , with the following formula: + +$$r = C * (((1+x)^K - 1)$$ + +with $C = 0,0022$ and $x = 0,18$ . With $0 \leq K \leq 127$ , a suitably useful range between 0 and 3 second is achieved for the uncertainty, while still being able to code down to values as small as 0,3 nanoseconds. To encode any higher value of + +uncertainty than that corresponding in the above formula to $K=127$ , the same value, $K=127$ , shall also be used. The uncertainty is then coded on 7 bits, as the binary encoding of $K$ . + +**Table A.10.5: Example values for the GANSS TOD Uncertainty Parameter Format** + +| Value of K | Value of uncertainty | +|------------|----------------------| +| 0 | 0 nanoseconds | +| 1 | 0,396 nanoseconds | +| 2 | 0,863 nanoseconds | +| - | - | +| 50 | 8,64 microseconds | +| - | - | +| 127 | $\geq 2,96$ seconds | + +##### **GANSS\_TIME\_ID** + +This field indicates which GNSS has been used as the time reference for GANSS Location Information. This field is optional and absence of this field means that Galileo system time is used as time reference. + +**Table A.10.6: GANSS\_TIME\_ID** + +| GANSS_TIME_ID | Indication | +|-------------------------|------------| +| GPS | 0 | +| QZSS | 1 | +| GLONASS | 2 | +| BDS | 3 | +| Reserved for future use | 4-7 | + +##### **Fix Type** + +This field contains an indication as to the type of measurements performed by the MS: 2D or 3D. This field is mandatory. + +'0' = 2D fix. + +'1' = 3D fix. + +###### **Position Data** + +This element provides a list of positioning methods and satellite systems used to calculate the Position Estimate. Each bit of this bitmap is of type Boolean, where TRUE ('1') means the particular positioning method or signal(s) from a satellite system has been used. + +'bit 0': E-OTD; +'bit 1': GPS; +'bit 2': Galileo; +'bit 3': SBAS; +'bit 4': Modernized GPS; +'bit 5': QZSS; +'bit 6': GLONASS; +'bit 7': BDS; +'bit 8-15': Reserved. + +##### **Stationary Indication** + +This field indicates whether the MS is stationary (horizontal and vertical speeds less than the resolution of the Velocity Estimate parameters as defined in 3GPP TS 23.032). + +If Velocity Estimate is requested and the MS is stationary, then the Stationary Indication is set to '1' and Velocity Estimate may not be included in Measure Position Response Element. + +###### Position Estimate + +This field contains the calculated position estimate in the format defined in 3GPP TS 23.032. The allowed shapes are: + +- ellipsoid Point; +- ellipsoid point with uncertainty circle; +- ellipsoid point with uncertainty ellipse; +- ellipsoid point with altitude and uncertainty ellipsoid. + +As defined in 3GPP TS 23.032, the position estimate is provided in WGS-84 reference system. + +#### A.3.2.10 GANSS Measurement Information Element + +The purpose of the GANSS Measurement Information element is to provide GANSS measurement information from the MS to the SMLC and GANSS TOD - GSM time association if requested by the SMLC. This information includes the measurements of code phase, Doppler, C/N0, and optionally accumulated carrier phase, also called accumulated delta range (ADR), which enable the network-based GANSS method where position is computed in the SMLC. The contents are shown in table A.10.7, and the individual fields are described subsequently. See also Figure A.1a for an illustration of the relation between some of the fields. + +![Timing diagram showing GNSS system time, satellite clock biases, and GANSS measurement information fields.](dae88eec6d1005984029b794ff8b7a9e_img.jpg) + +The diagram illustrates the timing relationships between GNSS system time and various satellite and ground-based clocks for GANSS measurement information. + +- GNSS system time using 1 ms resolution:** A timeline showing milliseconds 211 through 217. A double-headed arrow indicates a 1 ms resolution. +- System Time of a GNSS in ms:** Labeled as "GNSS Time t". +- At SV #1 time tsv1 in ms:** Shows a timeline with milliseconds 211 through 217. A "SV #1 clock bias" is indicated by an arrow pointing from the GNSS system time to the SV #1 time. +- At SV#N SAT time tsvn\_sat in ms:** Shows a timeline with milliseconds 211 through 217. A "SV #N\_SAT clock bias" is indicated by an arrow pointing from the GNSS system time to the SV #N\_SAT time. +- "GANSS TOD" Estimate:** A timeline showing milliseconds 210 through 216. A note indicates: "Reported GANSS TOD rounded down to nearest millisecond unit." This corresponds to the value 213 ms. +- Serving BTS clock (frame number FN):** Shows frame numbers 2580215 and 2580216. A vertical dashed line aligns the GANSS TOD estimate (213 ms) with the BTS frame number 2580216. +- Observed SV#1 time tsv 1:** A timeline showing milliseconds 140 through 145. A note indicates a time difference of $\sim 0.3617 \text{ ms}$ between the GANSS TOD estimate (213 ms) and the observed SV#1 time (143 ms). +- GANSS measurement information:** + - GANSS TOD = 213 ms + - GANSS Code phase Ambiguity = 4ms + - Code Phase SV #1 $\sim 0.3617 \text{ ms}$ + - Integer Code Phase SV #1 = 0 ms + - ... + - Code Phase SV #N\_SAT $\sim 0.7151 \text{ ms}$ + - Integer Code Phase SV #N = 1 ms + - Reference Frame = 34296 (2580216 mod 42432) + - Reference Frame MSB = 60 (2580216 div 42432) + - DeltaTOD = GANSS TOD - tsv\_1 = 213-143 = 70 +- Chosen reference millisecond for GANSS measurement information:** A vertical dashed line points to the start of the observed SV#1 time (143 ms). +- Observed SV#nsat time tsv\_nsat:** A timeline showing milliseconds 136 through 141. A note indicates a time difference of $\sim 1.7151 \text{ ms}$ between the GANSS TOD estimate (213 ms) and the observed SV#nsat time (138 ms). + +Timing diagram showing GNSS system time, satellite clock biases, and GANSS measurement information fields. + +Figure A.1a. Exemplary definitions of GANSS measurement information fields. + +GANSS Measurement Information element is included in the Measure Position Response component if the network has requested the mobile to perform mobile-assisted location measurements using GANSS Positioning Method. GANSS Measurement Information element will also optionally include carrier phase measurements if SMLC has requested the MS to perform carrier phase measurements. + +The following fields are repeated the number of times indicated in Number of E-OTD/GPS/GANSS Measurement Sets field if Multiple Sets element is included. If Multiple Sets element is not included, the default value for sets is one (i.e. the following fields are present only once). + +**Table A.10.7: GANSS Measurement Information element content** + +| Element fields | Presence | Occurrences | +|---------------------------------------------------------------------------------------------------------------------------------------|------------|-------------| +| Reference Frame | O | 1 | +| GANSS TOD | O (note 1) | 1 | +| DeltaTOD | O | 1 | +| GANSS TOD Uncertainty | O | 1 | +| GANSS Generic Measurement Information | M | N_GANSS | +| NOTE 1: If GPS Measurement Information element is not included in a Measure Position Response component, this field shall be present. | | | + +The following paragraphs describe the content of each information field of this element. + +##### Reference Frame + +These fields are shown in Table A.10.8 and are optional, but shall be included when GANSS TOD- GSM time association is provided. + +Note that expected values for Reference FN are in range 0 - 42431. The time of the reference frame boundary is as observed by the MS, ie without Timing Advance compensation. + +Reference FN MSB field indicates the Most Significant Bits (MSB) of the frame number of the reference BTS corresponding to the GANSS Measurement Information. + +Starting from the complete GSM frame number denoted FN, the MS calculates Reference FN MSB as + +$$\text{Reference FN MSB} = \text{floor}(\text{FN}/42432)$$ + +The complete GSM frame number FN can then be reconstructed in the SMLC by combining the fields Reference Frame with Reference FN MSB in the following way + +$$\text{FN} = \text{Reference FN MSB} * 42432 + \text{Reference FN}$$ + +**Table A.10.8: Reference Frame field contents** + +| Parameter | # of Bits | Resolution | Range | Unit | +|------------------|-----------|------------|-----------|-------| +| Reference FN | 16 | --- | 0 - 65535 | frame | +| Reference FN MSB | 6 | --- | 0 - 63 | frame | + +##### GANSS TOD + +This field specifies the GANSS TOD for which the GANSS Measurement Parameters in GANSS Generic Measurement Information Element are valid. This field shall be included when GANSS TOD-GSM time association is provided or if GPS Measurement Information element is not present in a Measure Position Response component. If GPS Measurement Information element is present in a Measure Position Response component, and GANSS TOD field is absent in the GANSS Measurement Information element, the GPS TOW included in the GPS Measurement Information element specifies the reference time for which the GANSS Measurement Parameters are valid. + +The 22 bits of GANSS TOD are the least significant bits. The most significant bits shall be derived by the Serving Mobile Location Centre to unambiguously derive the GANSS TOD. + +The value for GANSS TOD is derived from the GNSS specific system time of the GNSS reported first in the GANSS Measurement IE rounded down to the nearest millisecond unit. + +**Table A.10.9: GANSS TOD field contents** + +| Parameter | # of Bits | Resolution | Range | Units | +|-----------|-----------|------------|-------------|-------| +| GANSS TOD | 22 | 1 ms | 0 - 3599999 | ms | + +##### **DeltaTOD** + +This field specifies the difference in milliseconds between GANSS TOD reported in the GANSS Measurement Information Element and the millisecond part of the SV time tsv\_1 of the first SV in the list reported from the MS. The DeltaTOD is defined as + +$$\text{DeltaTOD} = \text{GANSS TOD} - \text{fix}(\text{tsv\_1})$$ + +where fix() denotes rounding to the nearest integer towards zero. + +Range: 0-127 + +##### **GANSS TOD Uncertainty** + +This element provides the accuracy of the relation GANSS TOD -GSM time when GANSS TOD-GSM time association is provided. When GANSS TOD-GSM time association is not provided, even if GANSS TOD - GSM Time Association Measurement Request is not included in the Measure Position Request, this element can be included to provide the accuracy of the reported GANSS TOD. + +If GANSS TOD is the given GNSS time, then the true GNSS time, corresponding to the provided GSM time as observed at the MS location, lies in the interval (GANSS TOD – GANSS TOD Uncertainty, GANSS TOD + GANSS TOD Uncertainty). + +The uncertainty $r$ , expressed in microseconds, is mapped to a number $K$ , with the following formula: + +$$r = C * (((1+x)^K - 1))$$ + +with $C = 0,0022$ and $x = 0,18$ . With $0 \leq K \leq 127$ , a suitably useful range between 0 and 3 second is achieved for the uncertainty, while still being able to code down to values as small as 0,3 nanoseconds. To encode any higher value of uncertainty than that corresponding in the above formula to $K=127$ , the same value, $K=127$ , shall also be used. The uncertainty is then coded on 7 bits, as the binary encoding of $K$ . + +Examples of GANSS TOD Uncertainty value are shown in Table A.10.10. + +**Table A.10.10: Example values for the GANSS TOD-GSM Time Uncertainty Parameter Format** + +| Value of K | Value of uncertainty | +|------------|----------------------| +| 0 | 0 nanoseconds | +| 1 | 0,396 nanoseconds | +| 2 | 0,863 nanoseconds | +| - | - | +| 50 | 8,64 microseconds | +| - | - | +| 127 | $\geq 2,96$ seconds | + +##### **N\_GANSS, Number of GANSS Generic Measurement Information Elements** + +N\_GANSS specifies the number of GANSS Generic Measurement Information Element occurrences in GANSS Measurement Information element, one occurrence for each reported GANSS. The range is from 1 to 8. + +##### **A.3.2.10.1 GANSS Generic Measurement Information Element** + +**Table A.10.11: GANSS Generic Measurement Information** + +| Element fields | Presence | Occurrences | +|----------------------------------------------|------------|-------------| +| GANSS ID | O (note 1) | 1 | +| GANSS Generic Measurement Element | M | N_SGN_TYPE | +| Note 1: Absence of this field means Galileo. | | | + +###### **GANSS ID** + +GANSS ID field identifies the GNSS constellation on which GANSS Measurement Parameters were measured according to Table A.40. + +Range: 0 – 7 + +###### **N\_SGN\_TYPE, Number of GANSS Generic Measurement Elements** + +N\_SGN\_TYPE specifies the number of GANSS Generic Measurement Element occurrences in GANSS Generic Measurement Information element. The range for N\_SGN\_TYPE is from 1 to 8. + +**Table A.10.12: GANSS Generic Measurement Element contents** + +| Element fields | Presence | Occurrences | +|------------------------------|----------|-------------| +| GANSS Signal ID | M | 1 | +| GANSS Code Phase Ambiguity | O | 1 | +| GANSS Measurement Parameters | M | N_SGN | + +This element contains measurement information for one GNSS signal type indicated by GANSS Signal ID. + +###### **GANSS Signal ID** + +GANSS Signal ID field identifies the signal on which GANSS Measurement Parameters were measured. The supported signals are listed in Table A.59. + +Range: 0 - 7 + +###### **GANSS Code Phase Ambiguity** + +The GANSS Code Phase Ambiguity field gives the ambiguity of the code phase measurement. It is given in ms and is an integer between 0 and 127. + +The Total Code Phase for a satellite k (Satk) is given modulo this GANSS Code Phase Ambiguity and is reconstructed with : + +$$\text{Code\_Phase\_Tot}(\text{Satk}) = \text{Code\_Phase}(\text{Satk}) + \text{Integer Code Phase}(\text{Satk}) + n * \text{Code Phase Ambiguity}, n= 0,1,2,\dots$$ + +If there is no code phase ambiguity, the GANSS Code Phase Ambiguity shall be set to 0. + +The field is optional. If GANSS Code Phase Ambiguity is absent, the default value is 0. + +###### **N\_SGN, Number of Signal Measurements** + +N\_SGN specifies the number of GANSS Measurement Parameters element occurrence in GANSS Generic Measurement Information element. Typical range for N\_SGN is 4 to a maximum of 16. + +###### **GANSS Measurement Parameters** + +This field contains information about the measurements of code phase and Doppler, which enables the network-based method where position is computed in the SMLC. This field is mandatory and occurs N\_SGN times in GANSS Generic Measurement Information element. + +**Table A.10.13: GANSS Measurement Parameters field contents** + +| Parameter | # of Bits | Resolution | Range | Units | Incl. | +|------------------------------------------------------------------------------------------|-----------|-----------------------------|---------------------------|-------|------------------| +| Signal Quality Parameters | | | | | | +| SV ID | 6 | --- | - | --- | M | +| C/N 0 | 6 | 1 | 0 - 63 | dB-Hz | M | +| Multipath Indicator | 2 | --- | See Table A.9 | --- | M | +| Carrier Quality Indication | 2 | --- | --- | --- | O (1) | +| Code Phase Measurements | | | | | | +| Code Phase | 21 | 2 -21 | 0 - (1-2 -21 ) | ms | M | +| Integer Code Phase | 7 | 1 | 0 - 127 | ms | O | +| Code Phase RMS Error | 6 | 3 bit mantissa
3 bit exp | 0,5 - 112 | m | M | +| Doppler Frequency Measurements | | | | | | +| Doppler | 16 | 0,04 | ±1310,7 | m/s | O | +| ADR | 25 | 2 -10 | 0 - 32767,5 | m | O (1) | +| NOTE 1: All of these fields shall be present together, or none of them shall be present. | | | | | | + +###### SV ID + +The SV ID is an index number for a satellite within a satellite system. The SV ID value range starts from 0 for each satellite system. The interpretation of SV ID for each GANSS is defined in Table A.10.14. + +**Table A.10.14: Interpretation of SV ID** + +| System | Value of SV ID | Interpretation of SV ID | +|----------------|----------------|------------------------------------------------------| +| Galileo | '0' - '35' | Code No. 1 to 36 | +| | '36' - '63' | Reserved | +| Modernized GPS | '0' - '62' | Satellite PRN Signal No. 1 to 63 | +| | '63' | Reserved | +| SBAS | '0' - '38' | Satellite PRN Signal No. 120 to 158 | +| | '39' - '63' | Reserved | +| QZSS | '0' - '4' | Satellite PRN Signal No. 193 to 197 | +| | '5' - '63' | Reserved | +| GLONASS | '0' - '23' | Slot Number 1 to 24 | +| | '24' - '63' | Reserved | +| BDS | '0' - '36' | Satellite ranging code number signal No.1 to 37 [18] | +| | '37' - '63' | Reserved | + +###### C/N0 + +This field contains the estimate of the carrier-to-noise ratio of the received signal from the particular satellite. It is given in whole dB-Hz and has a range of 0 to 63. Typical levels observed by GNSS receivers will be in the range of 16 dB-Hz to 50 dB-Hz. + +###### Carrier Quality Indication + +This field indicates the quality of a carrier phase measurement as a bit field. The LSB indicates the data polarity, that is, if the data from a specific satellite is received inverted, this is indicated by setting the LSB value to '1'. In the case the data is not inverted, the LSB is set to '0'. The MSB indicates if accumulation of the carrier phase has been continuous, that is, without cycle slips since the previous measurement report. If the carrier phase accumulation has been continuous, the MSB value is set to '1X'. Otherwise, the MSB is set to '0X'. + +This field is optional and shall be included only when carrier phase measurements are requested. + +**Table A.10.16: Carrier Phase Quality Indication values and associated indications** + +| Bit | Polarity Indication | +|-----------------|------------------------------| +| '0' | Data Direct | +| '1' | Data Inverted | +| '0X' | Carrier phase not continuous | +| '1X' | Carrier phase continuous | +| X = do not care | | + +###### Code Phase + +This field contains the whole and fractional value of the code-phase measurement made by the MS for the particular satellite signal at the time of measurement in the units of ms. GNSS specific code phase measurements (e.g. chips) are converted into unit of ms by dividing the measurements by the *nominal* values of the measured signal chipping rate (e.g. Galileo L1 OS measurement is divided by 1023,0 chip/ms). + +###### Integer Code Phase + +This field indicates the integer millisecond part of the code phase that is expressed modulo the GANSS Code PhaseAmbiguity. + +The value of the ambiguity is given in the GANSS Ambiguity field of the GANSS Generic Measurement Information element. + +The Integer code phase is optional. The default value is 0. + +###### Code Phase RMS Error + +This field contains Code Phase RMS Error value. This parameter has the same range as described in Table A.10. + +###### Doppler + +This field contains the Doppler measured by the MS for the particular satellite signal. This information can be used to compute the 3-D velocity of the MS. + +The Doppler range is sufficient to cover the potential range of values measured by the MS. Doppler measurements are converted into unit of m/s by multiplying the Doppler measurement in Hz by the *nominal* wavelength of the measured signal. + +##### ADR + +This field contains the ADR measurement measured by the MS for the particular satellite signal. This information can be used to compute the 3-D velocity or high-accuracy position of the MS. ADR measurements are converted into units of m by multiplying the ADR measurement by the *nominal* wavelength of the measured signal. + +This field is optional and shall be included only when carrier phase measurements are requested. + +## A.4 Assistance Data + +### A.4.1 General + +The Assistance Data is a RRLP component from the network to the MS. It is used by the network to provide assistance data to enable MS-based E-OTD or MS-based Assisted GPS capabilities in the MS and may be used to help support MS-assisted E-OTD and MS-assisted Assisted GPS. It contains the following elements. + +**Table A.11: Assistance Data component content** + +| Element | Type/Reference | Presence | +|---------------------------------------------------------------|---------------------------------------------------------------------|----------| +| E-OTD Reference BTS for Assistance Data | E-OTD Reference BTS for Assistance Data 2.2.3 | C | +| E-OTD Measurement Assistance Data | E-OTD Measurement Assistance Data 2.2.4 | C | +| E-OTD Measurement Assistance Data for System Information List | E-OTD Measurement Assistance Data for System Information List 2.2.5 | C | +| GPS Assistance Data | GPS Assistance Data 4.2.4 | C | +| Additional GPS Assistance Data | Additional GPS Assistance Data 4.2.4c | O | +| GPS Time Assistance Measurement Request | GPS Time Assistance Measurement Request 4.2.4a | O | +| GPS Reference Time Uncertainty | GPS Reference Time Uncertainty 4.2.4b | O | +| More Assistance Data To Be Sent | More Assistance Data To Be Sent 4.2.5 | C | +| Extended Reference | Extended Reference 2.2.5 | C | +| GANSS Assistance Data | GANSS Assistance Data 4.2.6 | C | +| GANSS Carrier-Phase Measurement Request | GANSS Carrier-Phase Measurement Request 4.2.7 | O | +| GANSS TOD - GSM Time Association Request | GANSS TOD - GSM Time Association Request 4.2.8 | O | + +### A.4.2 Elements + +#### A.4.2.1 E-OTD Reference BTS for Assistance Data Element + +This element is conditional. It is as described in sub-clause 2.2.3. If the network can provide assistance data, and data for E-OTD has been requested, this element is included. + +#### A.4.2.2 E-OTD Measurement Assistance Data Element + +This element is conditional. It is as described in sub-clause 2.2.4. If the network can provide assistance data, and data for E-OTD has been requested, this element is included. + +#### A.4.2.3 E-OTD Measurement Assistance Data for System Information List Element + +This element is conditional. It is as described in sub-clause 2.2.5. If the network can provide assistance data, and data for E-OTD has been requested, this element is included. + +#### A.4.2.4 GPS Assistance Data Element + +The GPS Assistance Data element contains a single GPS assistance message that supports both MS-assisted and MS-based GPS methods. This element can contain one or more of the fields listed in table A.12 below, which support both MS-assisted and MS-based GPS methods. As table A.12 shows, all fields are optional. + +Note that certain types of GPS Assistance data may be derived, wholly or partially, from other types of GPS Assistance data. + +In addition, an Integrity Monitor (IM) shall detect unhealthy (e.g., failed/failing) satellites and also shall inform users of measurement quality in DGPS modes when satellites are healthy. Excessively large pseudo range errors, as evidenced by the magnitude of the corresponding DGPS correction, shall be used to detect failed satellites. Unhealthy satellites should be detected within 10 seconds of the occurrence of the satellite failure. When unhealthy (e.g., failed/failing) satellites are detected, the assistance and/or DGPS correction data shall not be supplied for these satellites. When the error in the IM computed position is excessive for solutions based upon healthy satellites only, DGPS users shall be informed of measurement quality through the supplied UDRE values. After bad satellites have been indicated in the Real Time Integrity field, if the satellites return to healthy condition for some period of time, the indications for them shall be removed from this field. + +**Table A.12: Fields in the GPS Assistance Data element** + +| Parameter | Presence | Repetition | +|------------------------|----------|------------| +| Reference Time | O | Yes | +| Reference Location | O | No | +| DGPS Corrections | O | Yes | +| Navigation Model | O | Yes | +| Ionospheric Model | O | No | +| UTC Model | O | No | +| Almanac | O | Yes | +| Acquisition Assistance | O | Yes | +| Real-Time Integrity | O | Yes | + +When RRLP pseudo-segmentation is used, Table A.12 indicates which parameters may be repeated in more than one RRLP segment in order to provide data for multiple satellites. When any such parameter appears in more than one segment, the following rules shall apply. + +1. There shall be no repetition of data for the same satellite. +2. Optional and conditional elements in the parameter not associated with a particular satellite shall each appear in at most one RRLP segment. +3. Any mandatory element not associated with a particular satellite shall assume consistent values in the case of an element related to current GPS time and the same value otherwise. +4. The maximum number of satellites defined in sub-clause 5.1 for which data can be included for any parameter in one RRLP segment shall apply also when counted over all RRLP segments. + +##### Reference Time + +These fields specify the relationship between GPS time and air-interface timing of the BTS transmission in the reference cell. These fields occur once per message; some are mandatory and some are conditional, as shown in table A.14. Note that Reference Time may also be present within the Acquisition Assistance parameter. In such a case, the SMLC shall ensure consistency. + +**Table A.14: Reference Time (Fields occurring once per message)** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|------------------------------------------------------------------------------------------|----------|--------------|--------------------|-----------|------------| +| GPS Week | 10 | 1 | 0 - 1023 | weeks | M | +| GPS TOW | 23 | 0,08 | 0-604799,92 | sec | M | +| BCCH Carrier | 10 | 1 | 0 - 1023 | --- | O (note 1) | +| BSIC | 6 | 1 | 0 - 63 | --- | O (note 1) | +| FNm | 21 | 1 | 0 - ( $2^{21}-1$ ) | frames | O (note 1) | +| TN | 3 | 1 | 0 - 7 | timeslots | O (note 1) | +| BN | 8 | 1 | 0 - 156 | bits | O (note 1) | +| GPS TOW Assist | 24*N_SAT | --- | ---- | --- | O | +| NOTE 1: All of these fields shall be present together, or none of them shall be present. | | | | | | + +##### GPS Week + +This field specifies the GPS week number of the assistance being provided. GPS Week eliminates one-week ambiguities from the time of the GPS assistance. This field is mandatory. + +NOTE: The number of 1024 week cycles since the GPS zero time-point is provided in the GPS Reference Time Extension in Table A.29u. + +##### GPS TOW + +The GPS TOW (time-of-week) is a mandatory field and is specified with 80 msec resolution. When GSM Time Present is "1", GPS TOW and BCCH/BSIC/FNm/TN/BN IEs provide a valid relationship between GPS and GSM time, as seen at the approximate location of the MS, ie the propagation delay from BTS to MS shall be compensated for by the SMLC. Depending on implementation, the relation between GPS and GSM time may have varying accuracy. Therefore, the uncertainty of the timing relation may be provided in the optional field GPS Reference Time Uncertainty. If the 3GPP + +propagation delay from BTS to MS is not accurately known, the SMLC shall use the best available approximation of the propagation delay and take the corresponding delay uncertainty into account in the calculation of the field GPS Reference Time Uncertainty. When GSM Time Present is "0", GPS TOW is an estimate of current GPS time of week at time of reception of the RRLP segment containing this data by the MS. The SMLC should achieve an accuracy of +/- 3 seconds for this estimate including allowing for the transmission delay between SMLC and MS of the RRLP segment containing GPS TOW. Note that the MS should further compensate GPS TOW for the time between the reception of the segment containing GPS TOW and the time when the GPS TOW field is used. + +###### BCCH Carrier/BSIC/FNm/TN/BN + +These fields specify the state of the GSM frame number, timeslot number, and bit number, respectively, of the reference BTS with the specified BCCH carrier and BSIC at the time that correspond to GPS TOW. The SMLC shall use the current serving BTS as the reference BTS. The frame number field is given modulo $2^{21}$ , i.e., the MSB of the GSM frame number is truncated. The MS shall interpret FNm as the most recent of the two possible frame numbers that FNm could represent. The target MS has the option of rejecting a GPS position request or GPS assistance data if the reference BTS is not the serving BTS. + +##### GPS TOW Assist + +This field contains several fields in the Telemetry (TLM) Word and Handover Word (HOW) that are currently being broadcast by the respective GPS satellites. Combining this information with GPS TOW enables the MS to know the entire 1,2-second (60-bit) pattern of TLM and HOW that is transmitted at the start of each six-second subframe by the particular GPS satellite. This field contains information for each of N\_SAT satellites, and optional. The individual fields for each satellite in the message are shown in table A.15a. + +**Table A.15a: GPS TOW Assist (Fields occurring N\_SAT times per message)** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|--------------|--------|--------------|-----------|-----------|-------| +| SatID | 6 | --- | 0 - 63 | --- | M | +| TLM Message | 14 | --- | 0 - 16383 | Bit field | M | +| Anti-Spoof | 1 | 1 | 0 - 1 | Bit field | M | +| Alert | 1 | 1 | 0 - 1 | Bit field | M | +| TLM Reserved | 2 | --- | 0 - 3 | Bit field | M | + +##### SatID + +This field identifies the satellite for which the corrections are applicable. The values ranging from 0 to 63 represent satellite PRNs ranging from 1 to 64, respectively. + +##### TLM Message + +This field 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 fields contain the Anti-Spoof and Alert flags that are being broadcast by the GPS satellite identified by SatID. + +###### TLM Reserved + +These fields 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. + +##### Reference Location + +The Reference Location field contains a 3-D location (with uncertainty) specified as per 3GPP TS 23.032. The purpose of this field is to provide the MS with a priori knowledge of its location in order to improve GPS receiver performance. The allowed shape is 3-D location with uncertainty (ellipsoid point with altitude and uncertainty ellipsoid). + +##### DGPS Corrections + +These fields specify the DGPS corrections to be used by the MS. All fields are mandatory when DGPS Corrections are present in the GPS Assistance Data. + +**Table A.15: DGPS Corrections** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-------------------------------------------------------------|--------|--------------|------------|------------|-------| +| The following fields occur once per message | | | | | | +| GPS TOW | 20 | 1 | 0 - 604799 | sec | M | +| Status/Health | 3 | 1 | 0-7 | --- | M | +| N_SAT | 4 | 1 | 1-16 | --- | M | +| The following fields occur once per satellite (N_SAT times) | | | | | | +| SatID | 6 | --- | 0 - 63 | --- | M | +| IODE | 8 | --- | 0 - 255 | --- | M | +| UDRE | 2 | --- | 0 - 3 | --- | M | +| PRC | 12 | 0,32 | ±655,04 | meters | M | +| RRC | 8 | 0,032 | ±4,064 | meters/sec | M | +| Delta PRC2 | 8 | --- | --- | --- | M | +| Delta RRC2 | 4 | --- | --- | --- | M | +| Delta PRC3 | 8 | --- | --- | --- | M | +| Delta RRC3 | 4 | --- | --- | --- | M | + +###### GPS TOW + +This field indicates the baseline time for which the corrections are valid. + +###### Status/Health + +This field indicates the status of the differential corrections contained in the broadcast message. The values of this field and their respective meanings are shown below in table A.16. + +**Table A.16: Values of Status/Health IE** + +| Code | Indication | +|------|----------------------------------------------| +| 000 | UDRE Scale Factor = 1,0 | +| 001 | UDRE Scale Factor = 0,75 | +| 010 | UDRE Scale Factor = 0,5 | +| 011 | UDRE Scale Factor = 0,3 | +| 100 | UDRE Scale Factor = 0,2 | +| 101 | UDRE Scale Factor = 0,1 | +| 110 | Reference Station Transmission Not Monitored | +| 111 | Data is invalid - disregard | + +The first six values in this field indicate valid differential corrections. When using the values described below, the "UDRE Scale Factor" value is applied to the UDRE values contained in the message. The purpose is to indicate an estimate in the amount of error in the corrections. + +The value "110" indicates that the source of the differential corrections (e.g., reference station or external DGPS network) is currently not being monitored. The value "111" indicates that the corrections provided by the source are invalid, as judged by the source. In the later case, the message shall contain no corrections for individual satellites. Any MS that receives DGPS Corrections in a GPS Assistance Data IE shall contain the appropriate logic to properly interpret this condition and look for the next IE. + +###### N\_SAT + +This field indicates the number of satellites for which differential corrections are available. Corrections for up to 16 satellites. + +###### SatID + +This field identifies the satellite for which the corrections are applicable. The values ranging from 0 to 63 represent satellite PRNs ranging from 1 to 64, respectively. + +###### IODE + +This IE is the sequence number for the ephemeris for the particular satellite. The MS can use this IE to determine if new ephemeris is used for calculating the corrections that are provided in the broadcast message. This eight-bit IE identifies a particular set of ephemeris data for a GPS satellite and may occupy the numerical range of [0, 255]. The transmitted 3GPP + +IODE value will be different from any value transmitted by the GPS satellite during the preceding six hours. For more information about this field can be found from RTCM-SC104. + +###### User Differential Range Error (UDRE) + +This field provides an estimate of the uncertainty ( $1\text{-}\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. The meanings of the values for this field are described in table A.18. + +**Table A.18: Values of UDRE IE** + +| Value | Indication | +|-------|-------------------------------------------| +| 00 | $UDRE \leq 1,0 \text{ m}$ | +| 01 | $1,0 \text{ m} < UDRE \leq 4,0 \text{ m}$ | +| 10 | $4,0 \text{ m} < UDRE \leq 8,0 \text{ m}$ | +| 11 | $8,0 \text{ m} < UDRE$ | + +Each UDRE value shall be adjusted based on the operation of an Integrity Monitor (IM) function which exists at the network (SMLC, GPS server, or reference GPS receiver itself). Positioning errors derived at the IM which are excessive relative to DGPS expected accuracy levels shall be used to scale the UDRE values to produce consistency. + +###### Pseudo-Range Correction (PRC) + +This field indicates the correction to the pseudorange for the particular satellite at the GPS Reference Time, $t_0$ . The value of this field is given in meters (m) and the resolution is 0,32, as shown in table A.15 above. The method of calculating this field is described in [9]. + +If the SMLC has received a request for GPS assistance data from an MS which included a request for the navigation models and DGPS (i.e., bit D and E are set to one in 'Requested GPS Assistance Data, see 3GPP TS 49.031), the SMLC shall determine, for each satellite, if the navigation model stored by the MS is still suitable for use with DGPS corrections (also see navigation model update conditions right before Table A.19) and if so and if DGPS corrections are supported the SMLC should send DGPS corrections without including the navigation model. + +The IODE value sent for a satellite shall always be the IODE value that corresponds to the navigation model for which the pseudo-range corrections are applicable. + +The pseudo-range correction shall correspond to the available navigation model (the one already stored in and identified by the MS or the one included in the same procedure as the pseudo-range correction). The MS shall only use the PRC value when the IODE value received matches its available navigation model. + +###### Pseudo-Range Rate Correction (RRC) + +This field indicates the rate-of-change of the pseudorange correction for the particular satellite, using the satellite ephemeris identified by the IODE IE. The value of this field is given in meters per second (m/sec) and the resolution is 0,032, as shown in table A.15 above. For some time $t_1 > t_0$ , the corrections for IODE are estimated by + +$$PRC(t_1, IODE) = PRC(t_0, IODE) + RRC(t_0, IODE) \cdot (t_1 - t_0) ,$$ + +and the MS uses this to correct the pseudorange it measures at $t_1$ , $PR_m(t_1, IODE)$ , by + +$$PR(t_1, IODE) = PR_m(t_1, IODE) + PRC(t_1, IODE) .$$ + +The SMLC shall always send the RRC value that corresponds to the PRC value that it sends (see above for details). The MS shall only use the RRC value when the IODE value received matches its available navigation model. + +###### Delta Pseudo-Range Correction 2 (Delta PRC2) + +This IE is not used. The sender shall set it to zero and the receiver shall ignore it. + +###### Delta Pseudo-Range Rate Correction 2 (Delta RRC2) + +This IE is not used. The sender shall set it to zero and the receiver shall ignore it. + +###### Delta Pseudo-Range Correction 3 (Delta PRC3) + +This IE is not used. The sender shall set it to zero and the receiver shall ignore it. + +###### Delta Pseudo-Range Rate Correction 3 (Delta RRC3) + +This IE is not used. The sender shall set it to zero and the receiver shall ignore it. + +###### Navigation Model + +This set of fields contains information required to manage the transfer of precise navigation data to the GPS-capable MS. In response to a request from an MS for GPS assistance data, the SMLC shall determine whether to send the navigation model for a particular satellite to an MS based upon factors like the T-Toe limit specified by the MS and any request from the MS for DGPS (also see above). This information includes control bit fields as well as satellite ephemeris and clock corrections. The individual fields are given in Table A.19 below, and the conditions for their presence is discussed below. + +**Table A.19: Navigation Model (per-satellite fields - (1) = Positive range only)** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|---------------------------------------------------------------------|-------------------|------------------|-----------------------|-------| +| Navigation Model Flow Control (once per message) | | | | | +| Num_Sats_Total | 4 (1) | 1 | --- | M | +| Satellite and Format Identification (once per satellite) | | | | | +| SatID | 6 (1) | --- | --- | M | +| Satellite Status | 2 | --- | Boolean | M | +| Satellite Navigation Model and Associated Bits (once per satellite) | | | | | +| C/A or P on L2 | 2 | --- | Boolean | C | +| URA Index | 4 | --- | Boolean | C | +| SV Health | 6 | --- | Boolean | C | +| IODC | 10 (1) | --- | --- | C | +| L2 P Data Flag | 1 | --- | Boolean | C | +| SF 1 Reserved | 87 | --- | --- | C | +| T GD | 8 | 2 -31 | sec | C | +| t oc | 16 (1) | 2 4 | sec | C | +| af 2 | 8 | 2 -55 | sec/sec 2 | C | +| af 1 | 16 | 2 -43 | sec/sec | C | +| af 0 | 22 | 2 -31 | sec | C | +| C rs | 16 | 2 -5 | meters | C | +| Δn | 16 | 2 -43 | semi-circles/sec | C | +| M 0 | 32 | 2 -31 | semi-circles | C | +| C uc | 16 | 2 -29 | radians | C | +| e | 32 (1) | 2 -33 | --- | C | +| C us | 16 | 2 -29 | radians | C | +| (A) 1/2 | 32 (1) | 2 -19 | meters 1/2 | C | +| t oe | 16 (1) | 2 4 | sec | C | +| Fit Interval Flag | 1 | --- | Boolean | C | +| AODO | 5 | 900 | sec | C | +| C ic | 16 | 2 -29 | radians | C | +| OMEGA 0 | 32 | 2 -31 | semi-circles | C | +| C is | 16 | 2 -29 | radians | C | +| i 0 | 32 | 2 -31 | semi-circles | C | +| C rc | 16 | 2 -5 | meters | C | +| ω | 32 | 2 -31 | semi-circles | C | +| OMEGA dot | 24 | 2 -43 | semi-circles/sec | C | +| ldot | 14 | 2 -43 | semi-circles/sec | C | + +###### Num\_Sats\_Total + +This field specifies the number of satellites that are included in the provided Navigation Model. A range of 1-16 is available. This field is mandatory when the Navigation Model field is included in the message. + +###### SatID + +This field identifies the satellite for which the assistance is applicable. This value is the same as the PRN number provided in the navigation message transmitted by the particular satellite. The range is 0 to 63, with 0-31 indicating GPS satellites 1-32, respectively, and 32-63 indicating satellites in future augmentation systems (e.g., WAAS or EGNOS). This field is mandatory for each included satellite. + +###### Satellite Status + +This field is a two-bit value that indicates the status of the Navigation Model for the particular satellite specified by SatID. This field is mandatory for each included satellite. The MS shall interpret the combinations of the two bits as follows. + +**Table A.20: Satellite Status (per-satellite field)** + +| MSB | LSB | Interpretation | +|-----|-----|-------------------------------------------| +| 0 | 0 | New satellite, new Navigation Model | +| 0 | 1 | Existing satellite, same Navigation Model | +| 1 | 0 | Existing satellite, new Navigation Model | +| 1 | 1 | Reserved | + +This Satellite Navigation Model and associated bit fields include the parameters that accurately model the orbit and clock state of the particular satellite. For the particular satellite, these fields are conditional based on the value of Satellite Status for that satellite. The fields are absent when Satellite Status is "01", and present for all other values. The format for the ephemeris, clock corrections, and associate bits are specified in ICD-GPS-200. + +###### Ionospheric Model + +The Ionospheric Model contains fields needed to model the propagation delays of the GPS signals through the ionosphere. The information elements in this field are shown in table A.21. Proper use of these fields 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. All of the fields must be included when Ionospheric Model is present. + +**Table A.21: Ionospheric Model (occurs once per message, when present)** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------|--------|--------------|--------------------------------|-------| +| $\alpha_0$ | 8 | $2^{-30}$ | seconds | C | +| $\alpha_1$ | 8 | $2^{-27}$ | sec/semi-circle | C | +| $\alpha_2$ | 8 | $2^{-24}$ | sec/(semi-circle) 2 | C | +| $\alpha_3$ | 8 | $2^{-24}$ | sec/(semi-circle) 3 | C | +| $\beta_0$ | 8 | $2^{11}$ | seconds | C | +| $\beta_1$ | 8 | $2^{14}$ | sec/semi-circle | C | +| $\beta_2$ | 8 | $2^{16}$ | sec/(semi-circle) 2 | C | +| $\beta_3$ | 8 | $2^{16}$ | sec/(semi-circle) 3 | C | + +###### UTC Model + +The UTC Model field contains a set of parameters needed to relate GPS time to Universal Time Coordinate (UTC). All of the fields in the UTC Model are mandatory when the field is present. + +**Table A.22: UTC Model (occurs once per message, when present per-satellite fields - (1) = Positive range only)** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------|--------|--------------|---------|-------| +| $A_1$ | 24 | $2^{-50}$ | sec/sec | C | +| $A_0$ | 32 | $2^{-30}$ | seconds | C | +| $t_{0i}^{(1)}$ | 8 | $2^{12}$ | seconds | C | +| $WN_t^{(1)}$ | 8 | 1 | weeks | C | +| $\Delta t_{LS}$ | 8 | 1 | seconds | C | +| $WN_{LSF}^{(1)}$ | 8 | 1 | weeks | C | +| DN | 8 | 1 | days | C | +| $\Delta t_{LSF}$ | 8 | 1 | seconds | C | + +###### Almanac + +These fields specify the coarse, long-term model of the satellite positions and clocks. These fields are given in table A.23. With one exception ( $\delta i$ ), 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. If almanac is not provided for the full GPS constellation, the SMLC shall set the Complete Almanac Provided field in Table A.29w to FALSE. All fields in the Almanac are mandatory when the Almanac is present. The fields $t_{oa}$ and $WN_a$ specify the GPS time-of-week and week number, respectively, that are the reference points for the Almanac parameters. + +The Almanac also is useful as an acquisition aid for network-based GPS methods. Given a recent Almanac ( $< 3-4$ weeks old), the MS only needs Reference Time and Reference Location information to quickly acquire the signals and return measurements to the network. + +The Almanac also contains information about the health of that satellite as described in ICD-GPS-200. If this Almanac has been captured from the satellite signal, the SV Health field represents the predicted satellite health at the time the GPS control segment uploaded the Almanac to the satellite. According to ICD-GPS-200, this health information may differ from the SV Health field in the Navigation Model (table A.19) due to different upload times. + +The parameters Num\_Sats\_Total and SatID shall be interpreted in the same manner as described under table A.19. + +**Table A.23: Almanac (per-satellite fields - (1) = Positive range only)** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------------------------------------------|------------------|--------------|-----------------------|-------| +| The following fields occur once per message | | | | | +| Num_Sats_Total | 6 (1) | 1 | --- | M | +| $WN_a$ | 8 (1) | 1 | weeks | M | +| The following fields occur once per satellite | | | | | +| SatID | 6 (1) | --- | --- | M | +| $e^{(1)}$ | 16 | $2^{-21}$ | dimensionless | M | +| $t_{oa}^{(1)}$ | 8 | $2^{12}$ | sec | M | +| $\delta i$ | 16 | $2^{-19}$ | semi-circles | M | +| OMEGADOT | 16 | $2^{-38}$ | semi-circles/sec | M | +| SV Health | 8 | --- | Boolean | M | +| $A^{1/2(1)}$ | 24 | $2^{-11}$ | meters 1/2 | M | +| $OMEGA_0$ | 24 | $2^{-23}$ | semi-circles | M | +| $\omega$ | 24 | $2^{-23}$ | semi-circles | M | +| $M_0$ | 24 | $2^{-23}$ | semi-circles | M | +| $af_0$ | 11 | $2^{-20}$ | seconds | M | +| $af_1$ | 11 | $2^{-38}$ | sec/sec | M | + +###### Acquisition Assistance + +The Acquisition Assistance field of the GPS Assistance Data Information Element contains parameters that enable fast acquisition of the GPS signals in network-based GPS positioning. Essentially, these parameters describe the range and derivatives from respective satellites to the Reference Location at the Reference Time. Table A.24 illustrates the assistance data occurring once per message and table A.25 illustrates the assistance data occurring per number of satellites for which acquisition assistance is being provided. Figure A.2 illustrates the relation between some of the fields. + +This field is optional. The field would probably appear when the Method Type field of the Positioning Instructions IE is set to 0 (MS-Assisted) and the Positioning Methods field of the Position Instructions IE is set to 1 (GPS) or 2 (GPS or E-OTD). + +**Table A.24: GPS Acquisition Assist - Parameters appearing once per message** + +| Parameter | Range | Bits | Resolution | Incl. | Notes | +|----------------------|--------------|-------------------|------------|----------|----------------| +| Number of Satellites | 0 - 15 | 4 | | M | | +| Reference Time | GPS TOW | 0 - 604799,92 sec | 23 | 0,08 sec | M | +| | BCCH Carrier | 0 - 1023 | 10 | | O 1 | +| | BSIC | 0 - 63 | 6 | | O 1 | +| | Frame # | 0 - 2097151 | 21 | | O 1 | +| | Timeslots # | 0 - 7 | 3 | | O 1 | +| | Bit # | 0 - 156 | 8 | | O 1 | + +NOTE: All of these field shall be present together, or none of them shall be present. + +**Table A.25: GPS Acquisition Assist - Parameters appearing [number of satellites] times per message** + +| Parameter | Range | Bits | Resolution | Incl. | Notes | +|--------------------------------------|----------------------------------------------------------|------|--------------|------------------|-------| +| SVID/PRNID | 1 - 64 (0 - 63 ) | 6 | | M | | +| Doppler (0 th order term) | -5120 Hz to 5117,5 Hz | 12 | 2,5 Hz | M | | +| Doppler (1 st order term) | -1,0 - 0,5 Hz/sec. | 6 | 1/42 Hz/sec. | O 1 | | +| Doppler Uncertainty | 12.5 Hz - 200 Hz
[2 n (200) Hz, n = 0 - 4] | 3 | | O 1,3 | | +| Code Phase | 0 - 1022 chips | 10 | 1 chip | M | | +| Integer Code Phase | 0-19 | 5 | 1 C/A period | M | | +| GPS Bit number | 0 - 3 | 2 | | M | | +| Code Phase Search Window | 1 - 192 chips | 4 | | M | | +| Azimuth | 0 - 348,75 deg | 5 | 11,25 deg | O 2 | | +| Elevation | 0 - 78,75 deg | 3 | 11,25 deg | O 2 | | + +NOTE 1: Both of these fields shall be present together, or none of them shall be present. + +NOTE 2: Both of these fields shall be present together, or none of them shall be present. + +NOTE 3: If Doppler Uncertainty Extension (Table A.29x) is present, Doppler Uncertainty shall be set to value 0 (200 Hz). + +![Figure A.2: Exemplary calculations of Acquisition Assistance fields. The diagram illustrates the relationship between GPS system time and satellite-specific times. It shows timelines for SV#1 time, SV#N_SAT time, GPS TOW (system time), and predicted times at a reference location. Key elements include clock biases (Delta tsv), propagation delay (tau), and a chosen reference epoch at GPS TOW = 240 ms. Calculations for SV#1 show how code phase and bit number are derived from the predicted time.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +SV#1 clock bias $|\Delta t_{sv\_1}|$ + $(t = t_{sv} - \Delta t_{sv\_1}$ according to [8], pp 88) + +At SV#1: SV#1 time tsv1 [ms] | 237 | 238 | 239 | 240 | 241 | 242 | 243 | + +SV#N\_SAT clock bias $|\Delta t_{sv\_nsat}|$ + +At SV#N\_SAT: SV#N\_SAT time tsv\_sat [ms] | 237 | 238 | 239 | 240 | 241 | 242 | 243 | + +1 C/A code 1023 chips + +Chosen reference epoch for Acquisition assistance + +GPS TOW t [ms] (GPS system time) | 237 | 238 | 239 | 240 | 241 | 242 | 243 | + +~370 chips + +At Reference Location: Predicted SV#1 time tsv\_1 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | + +Exemplary calculation of predicted tsv + $t_{sv} = t + \Delta t_{sv} - \tau$ + $\tau$ : propagation delay from SV to MS + $\Delta t_{sv}$ : clock bias from [8], pp 88 + +Acquisition assistance for SV#1 + GPS TOW = 240 ms (a multiple of 80ms) + Code phase ~ 370 chips + Integer code phase = $\text{mod}(170, 20) = 10$ + GPS Bit number = $\text{mod}(\text{floor}(170/20), 4) = 0$ + +Predicted SV#N\_SAT time tsv\_nsat | 165 | 166 | 167 | 168 | 169 | 170 | 171 | + +~220 chips + +Figure A.2: Exemplary calculations of Acquisition Assistance fields. The diagram illustrates the relationship between GPS system time and satellite-specific times. It shows timelines for SV#1 time, SV#N\_SAT time, GPS TOW (system time), and predicted times at a reference location. Key elements include clock biases (Delta tsv), propagation delay (tau), and a chosen reference epoch at GPS TOW = 240 ms. Calculations for SV#1 show how code phase and bit number are derived from the predicted time. + +**Figure A.2. Exemplary calculations of Acquisition Assistance fields.** + +This field indicates whether or not angle information is present in this message. The MS shall interpret a value of "1" to mean that angle (Azimuth and Elevation) information is present, and "0" to mean that it is not provided. This field is mandatory. + +###### Number of Satellites + +This field contains the number of satellites identified in this information element. This field is mandatory. + +Range: 0 - 15 + +##### Reference Time + +The Reference Time field of the GPS Acquisition Assistance Data IE specifies the relationship between GPS time and air-interface timing of the BTS transmission in the reference cell. + +**GPS TOW** subfield specifies the GPS TOW for which the location estimate is valid. When the parameters BCCH Carrier/BSIC/Frame #/Timeslots #/Bit # are present, together with GPSTOW they provide a valid relationship between GPS and GSM time, as seen at the approximate location of the MS, ie the propagation delay from BTS to MS shall be compensated for by the SMLC. Depending on implementation, the relation between GPS and GSM time may have varying accuracy. The uncertainty of the timing relation may be provided in the optional field GPS Reference Time Uncertainty. If the propagation delay from BTS to MS is not accurately known, the SMLC shall use the best available approximation of the propagation delay and take the corresponding delay uncertainty into account in the calculation of the field GPS Reference Time Uncertainty. GPS TOW is mandatory when the GPS Acquisition Assistance Data 3GPP + +Information Element is included. When the GSM time parameters are not present the GPS TOW is an estimate of current GPS time of week at time of reception of the RRLP segment containing the GPS TOW by the MS. The SMLC should achieve an accuracy of +/- 3 seconds for this estimate including allowing for the transmission delay between SMLC and MS of the RRLP segment containing GPS TOW. Note that the MS should further compensate GPS TOW for the time between the reception of the segment containing GPS TOW and the time when the GPS TOW field is used. + +Range: 0 - 604799,92 sec + +The **BCCH Carrier #** and **BSIC** subfields specify the reference cell for which GSM timing is provided. These subfields are optional when the GPS Acquisition Assistance Data Information Element is included. If included, the SMLC shall set the reference cell to the current serving cell. A target MS has the option of rejecting a GPS position request or GPS assistance data if the reference cell is not the serving cell. + +The **Frame #** subfield specifies the GSM frame number of the BTS transmissions for the reference cell that occur at the given GPS TOW. This subfield is optional when the GPS Acquisition Assistance Data Information Element is included. + +Range: 0 - 2097151 + +The **Timeslots #** subfield specifies the GSM timeslot of the BTS transmissions for the reference cell that occur at the given GPS TOW. This subfield is optional when the GPS Acquisition Assistance Data Information Element is included. + +Range: 0 - 7 + +The **Bit #** subfield specifies the GSM and bit number of the BTS transmissions for the reference cell that occur at the given GPS TOW. This subfield is optional when the GPS Acquisition Assistance Data Information Element is included. + +Range: 0 - 156 + +###### **SVID/PRNID** + +This field identifies the particular satellite for which the measurement data is supplied. This value is the same as the PRN number provided in the navigation message transmitted by the particular satellite. + +The range is 0 to 63, where SVID = PRNID - 1 + +###### **Doppler (0th order term)** + +This field contains the Doppler (0th order term) value. A positive value defines the increase in satellite signal frequency due to velocity towards the MS. A negative value defines the decrease in satellite signal frequency due to velocity away from the MS. This field is mandatory. + +Range: 5120 Hz to 5117,5 Hz + +###### **Doppler (1st order term)** + +This field contains the Doppler (1st order term) value. A positive value defines the rate of increase in satellite signal frequency due to acceleration towards the MS. A negative value defines the rate of decrease in satellite signal frequency due to acceleration away from the MS. This field is optional. + +Range: -1,0 Hz to 0,5 Hz / s + +###### **Doppler Uncertainty** + +This field contains the Doppler uncertainty value. It is defined such that the Doppler experienced by a stationary MS is in the range "Doppler - Doppler Uncertainty" to "Doppler + Doppler Uncertainty". This field is optional. If Doppler Uncertainty (together with Doppler 1st order term) is omitted, the terminal shall interpret Doppler Uncertainty as greater than +/-200 Hz. If the Doppler Uncertainty Extension (Table A.29x) field is present, the MS that supports the Doppler Uncertainty Extension shall ignore this field. + +Permitted Values: 12,5 Hz, 25 Hz, 50 Hz, 100 Hz, 200 Hz as encoded by an integer n in the range 0-4 according to the formula in Table A.25 + +###### **Code Phase** + +This field contains code phase, in units of 1 GPS chip, in the range from 0 to 1022 GPS chips, where increasing binary values of the field signify increasing predicted pseudoranges, as seen by a receiver at the Reference Location at the time GPS TOW. The Reference Location would typically be an apriori estimate of the MS location. This field is mandatory. + +Range: 0-1022 chips + +###### Integer Code Phase + +This field contains integer code phase, i.e. the number of the code periods that have elapsed since the latest GPS bit boundary, in units of C/A code period, as seen by a receiver at the Reference Location at the time GPS TOW. This field is mandatory. + +Range: 0-19 + +###### GPS Bit Number + +This field contains GPS bit number (expressed modulo 4) currently being transmitted at the time GPS TOW, as seen by a receiver at the Reference Location. This field is mandatory. + +Range: 0-3 + +###### Code Phase Search Window + +This field contains the code phase search window. The code phase search window accounts for the uncertainty in the estimated MS location but not any uncertainty in GPS TOW. It is defined such that the expected code phase is in the range "Code Phase - Code Phase Search Window" to "Code Phase + Code Phase Search Window". This field is mandatory. + +Range: 0-15 (i.e. 1-512 chips according to following table) + +**Table A.26: Code Phase Search Window Parameter Format** + +| CODE_PHASE_WIN | Code Phase Search Window (GPS chips) | +|----------------|--------------------------------------| +| '0000' | 512 | +| '0001' | 1 | +| '0010' | 2 | +| '0011' | 3 | +| '0100' | 4 | +| '0101' | 6 | +| '0110' | 8 | +| '0111' | 12 | +| '1000' | 16 | +| '1001' | 24 | +| '1010' | 32 | +| '1011' | 48 | +| '1100' | 64 | +| '1101' | 96 | +| '1110' | 128 | +| '1111' | 192 | + +###### Azimuth + +This field together with the Azimuth LSB included in Acquisition Assistance Extension in Table A.29v contains the azimuth angle. An angle of x degrees means the satellite azimuth a is in the range ( $x \leq a < x+0,703125$ ) degrees. This field is optional. + +Range: 0 – 359,296875 degrees. + +###### Elevation + +This field together with the Elevation LSB included in Acquisition Assistance Extension in Table A.29v contains the elevation angle. An angle of y degrees means the satellite elevation e is in the range ( $y \leq e < y+0,703125$ ) degrees except for $y = 89,296875$ where the range is extended to include 90 degrees. This field is optional. + +Range: 0 – 89,296875 degrees + +##### Real-Time Integrity + +The Real-Time Integrity field of the GPS Assistance Data Information Element contains parameters that describe the real-time status of the L1C/A signal in GPS constellation. Primarily intended for non-differential applications, the real-time integrity of the satellite constellation is of importance as there is no differential correction data by which the mobile can determine the soundness of each satellite signal. The Real-Time GPS Satellite Integrity data communicates the health of the L1C/A signal to the mobile in real-time. The format is shown in table A.29. The SMLC shall always transmit the Real Time Integrity field with the current list of satellites with unhealthy L1C/A signal, for any A-GPS positioning attempt and whenever A-GPS assistance data is sent. The same applies for GANSS positioning attempt and assistance data when modernized GPS is involved. If the number of bad satellites (NBS) is zero, then the Real Time Integrity field shall be omitted. When the Extended Reference IE is included in the RRLP Measure Position Request message or in the RRLP Assistance Data message, then the MS shall interpret the absence of a Real Time Integrity field in the assistance data provided by the SMLC to mean that NBS is zero. If the Extended Reference IE is not present, this interpretation applies when the assistance data is provided by the SMLC following a previous request of the MS for Real Time Integrity data. + +**Table A.29: Real-Time Integrity - Parameters appearing NBS times** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-----------|--------|--------------|-------|-------|-------| +| Bad_SVID | 6 | 1 | 0-63 | --- | C | + +###### NBS (Number of Bad Satellites) + +The NBS value indicates the number of satellite ID's that follow. The user should not use the L1C/A signal of those satellites at this time in a fix. This NBS value is determined from the Bad\_SVID list. + +###### Bad\_SVID + +This six bit field appears NBS times, and indicates the SVID of satellites which L1C/A signal should not be used for fix by the user at this time. The values ranging from 0 to 63 represent satellite PRNs ranging from 1 to 64, respectively. + +#### A.4.2.4a GPS Time Assistance Measurement Request Element + +This element is optional and controls if the MS should return GPS time assistance measurements or not to the SMLC. The inclusion of this parameter implies use of measure Position Request The description is found in sub-chapter 2.2.4a. + +#### A.4.2.4b GPS Reference Time Uncertainty Element + +This element is conditional and provides the accuracy of the relation GPS and GSM time in the Acquisition Assistance in GPS Assistance Data Element. The interval, range and treatment is as described in sub-clause 2.2.4b. + +#### A.4.2.4c Additional GPS Assistance Data + +The Additional GPS Assistance Data Element contains additional GPS assistance data which are not included in the GPS Assistance Data Element. This element can contain one or more of the fields listed in Table A.29a below. + +**Table A.29a: Fields in the Additional GPS Assistance Data element** + +| Parameter | Presence | Repetition | +|------------------------------------------|----------|------------| +| GPS Ephemeris Extension | O | Yes | +| GPS Ephemeris Extension Check | O | Yes | +| DGPS Corrections Validity Period | O | Yes | +| GPS Reference Time Extension | O | No | +| GPS Acquisition Assistance Extension | O | Yes | +| GPS Almanac Extension | O | No | +| GPS Acquisition Assistance Extension-R12 | O | Yes | + +When RRLP pseudo-segmentation is used, Table A.29a indicates which parameters may be repeated in more than one RRLP segment in order to provide data for multiple satellites. When any such parameter appears in more than one segment, the following rules shall apply. + +1. There shall be no repetition of the same data for the same satellite, even though there might be multiple realizations of the IEs for the same satellite. For example, GPS Ephemeris Extension may occur multiple times for the same satellite, but with different data content. +2. Optional and conditional elements in the parameter not associated with a particular satellite shall each appear in at most one RRLP segment. +3. Any mandatory element not associated with a particular satellite shall assume consistent values in the case of an element related to current GPS time and the same value otherwise. +4. The maximum number of satellites defined in sub-clause 5.1 for which data can be included for any parameter in one RRLP segment shall apply also when counted over all RRLP segments. + +##### GPS Ephemeris Extension + +The GPS Ephemeris extension contains parameters designed to extend the time of applicability of the Ephemeris terms by the continuous addition of the delta ephemeris terms to the respective terms of the referenced ephemeris. + +This message can provide extension information for every satellite for many days into the future; doing so may create a large message, thus care must be taken to consider the transport bandwidth. The SMLC can limit the duration of the extension to decrease the message size. For example if the extension duration is limited to twelve hours the payload will be approximately 2,000 octets, for a typical 27 satellite constellation. + +**Table A.29.b: GPS Ephemeris Extension** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|----------------------|---------------------------------|--------------|-------|-------| +| gpsEphemerisHeader | See Table A.29.c | --- | | O | +| gpsReferenceSet | See Table A.29.e | --- | | O | +| ephemerisDeltaMatrix | List of GPSEphemerisDeltaEpochs | | | O | + +**Table A.29.c: GPS Ephemeris Header** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|--------------------------------------------|------------------|--------------|-------|-------| +| GPS Ephemeris Extension (Once per message) | | | | | +| timeOfEstimation | See Table A.29.d | --- | | M | +| validityPeriod | 3 | 1 | Hours | M | +| ephemerisExtensionDuration | 9 | 1 | Hours | M | + +###### Time of Estimation + +The GPS Time at Estimation provides the GPS time at which the ephemeris extensions were created. + +**Table A.29.d: Time of Estimation** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------------|--------|--------------|---------|-------| +| GPS Week of Estimation | 10 | 1 | Week | M | +| GPS TOW of Estimation | 20 | 1 | Seconds | M | + +##### GPS Week of Estimation + +This field specifies the week of the time that the estimation was determined. + +Range: 0 - 1023 weeks + +##### GPS TOW of Estimation + +Integer number of GPS TOW seconds within the current week of the time that the estimation was determined. + +Range: 0 - 604800 s. + +###### Validity Period + +The validityPeriod indicates the validity period of the GPS Reference Set. It also indicates the default validity period of each individual delta ephemeris packet in the case that the individual validityPeriod is not present in the GPS Delta 3GPP + +Epoch Header (see Table A.29.j). It is the length of time that the GPS Reference Set is intended to last and, if applicable, it is the length of time that the ephemeris constructed by application of the delta is intended to last. + +Range: 1 – 8 hours. + +###### Ephemeris Extension Duration + +The Ephemeris Extension duration indicates the total block of time measured in units of hours that the extended ephemeris covers. + +Range: 1 – 512 hours. + +The gpsEphemeris header is mandatory only once in the delivery of the GPS Ephemeris Extension message. + +##### GPS Reference Set + +**Table A.29.e: GPS Reference Set** + +| Parameter | Presence | Note | +|---------------------|----------|------------------| +| GPS Reference Orbit | M | See Table A.29.f | + +The GPS Reference Set is a list of GPS Reference Orbits, one for each healthy satellite vehicle at the time of construction. + +###### GPSReference Orbit + +**Table A.29.f: GPS Reference Orbit** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|---------------|------------------|--------------|-------|-------| +| svID | 5 | 1 | --- | M | +| gpsOrbitModel | See Table A.29.g | | -- | M | +| gpsClockModel | See Table A.29.h | | -- | M | + +###### SvID + +The satellite vehicle ID identifying to which satellite the following orbital and clock model apply + +###### GPSOrbitModel + +This field is a structure that contains the Reference Nav Model satellite orbit information upon which all subsequent delta information will be applied to create the next ephemeris for use in navigation. + +**Table A.29.g: Reference Nav Model** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------|--------|--------------|-----------------------|-------| +| keplerToe | 16 | 24 | seconds | M | +| keplerW | 32 | $2^{-31}$ | hours | M | +| keplerDeltaN | 16 | $2^{-43}$ | semi-circles/sec | M | +| keplerM0 | 32 | $2^{-31}$ | semi-circles | M | +| keplerOmegaDot | 27 | $2^{-43}$ | semi-circles/sec | M | +| keplerE | 32 | $2^{-33}$ | --- | M | +| keplerIDot | 14 | $2^{-43}$ | semi-circles/sec | M | +| keplerAPowerHalf | 32 | $2^{-19}$ | Meters 1/2 | M | +| keplerIO | 32 | $2^{-31}$ | semi-circles | M | +| keplerOmega0 | 32 | $2^{-31}$ | semi-circles | M | +| keplerCrs | 16 | $2^{-5}$ | meters | M | +| keplerCis | 16 | $2^{-29}$ | radians | M | +| keplerCus | 16 | $2^{-29}$ | radians | M | +| keplerCrc | 16 | $2^{-5}$ | meters | M | +| keplerCic | 16 | $2^{-29}$ | radians | M | +| KeplerCuc | 16 | $2^{-29}$ | radians | M | + +###### GPSClockModel + +This field is a structure that contains the satellite clock model upon which all subsequent clock information will be applied to create the next clock model for use in navigation. + +##### GPS Clock Model + +**Table A.29.h: GPS Clock Model** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------|--------|--------------|------------------------------|-------| +| aF2 | 8 | $2^{-55}$ | seconds/seconds 2 | M | +| aF1 | 16 | $2^{-43}$ | seconds/seconds | M | +| aF0 | 22 | $2^{-31}$ | seconds | M | +| tgd | 8 | $2^{-31}$ | seconds | M | + +##### GPS Ephemeris Delta Matrix + +GPS Ephemeris Delta Matrix is a list of GPS Ephemeris Delta Epochs. Each epoch is indicated by a unique seqNum. Each epoch corresponds to a specific update interval and contains a delta epoch header and ephemeris delta elements for all PRNs for that epoch. + +##### GPS Ephemeris Delta Epoch + +**Table A.29.i: GPS Ephemeris Delta Epoch** + +| Parameter | Note | Incl. | +|---------------------|--------------------------------------|-------| +| gpsDeltaEpochHeader | See Table A.29.j | O | +| gpsDeltaElementList | List of GPS Ephemeris Delta Elements | M | + +###### GPS Delta Epoch Header + +**Table A.29.j: GPS Delta Epoch Header** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|----------------------|------------------|--------------|-------|-------| +| validityPeriod | 3 | 1 | Hours | O | +| ephemerisDeltaSizes | See Table A.29.k | | | O | +| ephemerisDeltaScales | See Table A.29.l | | | O | + +###### Validity Period + +The validityPeriod indicates the validity period of each individual delta ephemeris packet. It is the length of time that the ephemeris constructed by application of the delta is intended to last. If not present then the default validityPeriod in the GPS Ephemeris Header IE applies (see Table A.29.c). + +Range: 1 – 8 hours. + +###### Ephemeris Delta Sizes + +This field is a structure that indicates the bit sizes for all the fields in the GPS Ephemeris Delta structure. + +**Table A.29.k: GPS Ephemeris Delta Sizes** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------------|--------|--------------|-------|-------| +| bitSize_delta_ω | 5 | 1 | --- | M | +| bitSize_delta_Δn | 4 | 1 | --- | M | +| bitSize_delta_M0 | 5 | 1 | --- | M | +| bitSize_delta_OMEGAdot | 5 | 1 | --- | M | +| bitSize_delta_e | 5 | 1 | --- | M | +| bitSize_delta_ldot | 4 | 1 | --- | M | +| bitSize_delta_sqrtA | 5 | 1 | --- | M | +| bitSize_delta_i0 | 5 | 1 | --- | M | +| bitSize_delta_OMEGA0 | 5 | 1 | --- | M | +| bitSize_delta_Crs | 4 | 1 | --- | M | +| bitSize_delta_Cis | 4 | 1 | --- | M | +| bitSize_delta_Cus | 4 | 1 | --- | M | +| bitSize_delta_Crc | 4 | 1 | --- | M | +| bitSize_delta_Cic | 4 | 1 | --- | M | +| bitSize_delta_Cuc | 4 | 1 | --- | M | +| bitSize_delta_tgd | 4 | 1 | --- | M | + +###### Ephemeris Delta Scales + +This field is a structure that indicates the scale factor modifiers for all the fields in the GPS Ephemeris Delta structure. + +**Table A.29.l: GPS Ephemeris Delta Scales** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|----------------------|--------|--------------|-------|-------| +| scale_delta_ω | 5 | 1 | --- | M | +| scale_delta_Δn | 5 | 1 | --- | M | +| scale_delta_M0 | 5 | 1 | --- | M | +| scale_delta_OMEGAdot | 5 | 1 | --- | M | +| scale_delta_e | 5 | 1 | --- | M | +| scale_delta_ldot | 5 | 1 | --- | M | +| scale_delta_sqrtA | 5 | 1 | --- | M | +| scale_delta_i0 | 5 | 1 | --- | M | +| scale_delta_OMEGA0 | 5 | 1 | --- | M | +| scale_delta_Crs | 5 | 1 | --- | M | +| scale_delta_Cis | 5 | 1 | --- | M | +| scale_delta_Cus | 5 | 1 | --- | M | +| scale_delta_Crc | 5 | 1 | --- | M | +| scale_delta_Cic | 5 | 1 | --- | M | +| scale_delta_Cuc | 5 | 1 | --- | M | +| scale_delta_tgd | 5 | 1 | --- | M | + +###### GPS Delta Element List + +GPS Delta Element List is a list of GPS Ephemeris Delta Elements + +###### GPS Ephemeris Delta Element + +Each GPS Ephemeris Delta Element is encoded as an octet string of up to 47 octets. Each element is uniquely identified by the pair (seqNum, sv\_ID) and it is defined as a structure as shown in table A.29.m. The MS should parse the octet string according to the fields specified in table A.29.m. Each element in table A.29.m but for seqNum and sv\_ID should be treated as a signed integer. The actual number of octets is determined by the size of the bit fields in the GPS\_Ephemeris\_Delta\_Sizes table (table A.29.k). Each set of up to 47 octets represents a single extension for a single satellite vehicle. Each element encodes the satellite vehicle ID and the sequence number. The sequence number specifies the order in which the individual ephemeris extension elements are assembled as time marches forward to create the next ephemeris. The sequence number is the same for all satellite vehicle IDs for a particular update period. + +Table A.29.m: GPS Ephemeris Delta Element + +| Parameter | # Bits | Default # Bits | Scale Factor | Default Scale | Units | Incl. | +|-----------------|-----------|----------------|--------------------------------------------------------|---------------|-----------------------|-------| +| sequenceNum | 7 | | 1 | 1 | --- | M | +| svID | 5 | | 1 | 1 | --- | M | +| delta_omega | 1..32 (1) | 21 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_Delta_n | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-43} \dots 2^{15} \cdot 2^{-43} (2)$ | $2^{-43}$ | semi-circles/sec | M | +| delta_M0 | 1..32 (1) | 21 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_OMEGA_dot | 1..24 (1) | 13 | $2^{-16} \cdot 2^{-43} \dots 2^{15} \cdot 2^{-43} (2)$ | $2^{-43}$ | semi-circles/sec | M | +| delta_e | 1..32 (1) | 18 | $2^{-16} \cdot 2^{-33} \dots 2^{15} \cdot 2^{-33} (2)$ | $2^{-33}$ | --- | M | +| delta_idot | 1..14 (1) | 11 | $2^{-16} \cdot 2^{-43} \dots 2^{15} \cdot 2^{-43} (2)$ | $2^{-43}$ | semi-circles/sec | M | +| delta_sqrtA | 1..32 (1) | 14 | $2^{-16} \cdot 2^{-19} \dots 2^{15} \cdot 2^{-19} (2)$ | $2^{-19}$ | meters 1/2 | M | +| delta_i0 | 1..32 (1) | 14 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_OMEGA0 | 1..32 (1) | 14 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_Crs | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-5} \dots 2^{15} \cdot 2^{-5} (2)$ | $2^{-5}$ | meters | M | +| delta_Cis | 1..16 (1) | 11 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_Cus | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_Crc | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-5} \dots 2^{15} \cdot 2^{-5} (2)$ | $2^{-5}$ | meters | M | +| delta_Cic | 1..16 (1) | 11 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_Cuc | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_tgd | 1..16 (1) | 2 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | seconds | M | + +- (1) The number of bits of each signed integer field is variable and it is indicated once for all numEphemerisDeltas by the structure ephemerisDeltasSizes. When the ephemerisDeltasSizes field is not present, the values found in the columns "Default # Bits" shall be used. +- (2) The scale factor of each parameter is variable around the default scale factor. The variation for each field is indicated once for all numEphemerisDeltas by the structure ephemerisDeltasScales. For example, if the scale factor modifier for delta\_omega has a value of 4, the scale factor for delta\_omega is $2^4 \cdot 2^{-31}$ . When the ephemerisDeltasScales is not used, the values found in the column "Default Scale" shall be used. + +###### sequenceNum + +This field indicates the order of the Ephemeris delta terms. The ephemeris constructed for use in satellite positioning is built by adding the delta terms to the referenced GPS\_Navigation Model in the order dictated by this sequence number. The sequence number shall remain the same for each svID in an epoch of Ephemeris Deltas corresponding to a particular update interval. + +###### svID + +This field identifies the satellite ID within a particular sequenceNum or epoch. + +These fields, with the exception of sequenceNum and svID, specify the deltas to be added to the existing Ephemeris to create a new Ephemeris suite that is extended from its predecessor by the time provided in the "validityPeriod" parameter. To compute the time of ephemeris for the newly constructed ephemeris, validityPeriod is added to the preceding toe. The ephemeris time of clock (toc) is set equal to the toe. + +For each of the other ephemeris terms the corresponding delta ephemeris term is added in order to create the updated ephemeris. The terms delta\_M0, delta\_i0, and delta\_OMEGA0 of the delta ephemeris must be extrapolated prior to the addition of the delta terms as follows: + +Where $\mu$ is the WGS 84 value of the earth's gravitational constant for GPS user and is equal to $3,986005 \cdot 10^{14} \text{ m}^3/\text{sec}^2$ , and $A_{(i)}$ is the semi-major axis associated with this satellite's update. The extrapolation of delta\_M0, uses the prior set's sqrtA term to compute $A_{(i)}$ as the square of sqrtA(i). + +$$\text{delta\_OMEGA0}_{(i+1)} = \text{delta\_OMEGA0}_{(i)} + \text{delta\_OMEGA\_dot}_{(i)} \cdot dt$$ + +$$i0_{(i+1)} = i0_{(i)} + \text{Idot}_{(i)} \cdot dt$$ + +Where dt is equal to the validity period \* 3600. The terms af0, and af1 from the GPS clock model must be extrapolated as follows: + +$$af0_{(i+1)} = af0_{(i)} + af1_{(i)} * dt + af2 * dt^2$$ + +$$af1_{(i+1)} = af1_{(i)} + 2 * af2_{(i)} * dt$$ + +$$af2_{(i+1)} = af2_{(i)}$$ + +Where $af0$ , $af1$ , and $af2$ are the clock model terms as shown in table A.29.c + +$dt$ is equal to the validity period represented in seconds ( $validityPeriod * 3600$ ) + +The following demonstrates the application of the ephemeris extension technique. Assume the $validityPeriod = 5$ , representing: $(5+1)$ hours = 6 hours, and the GPS Navigation model for a particular satellite, identified by the reference IOD has a $toe = 0$ seconds. + +The $toe$ for sequenceNumber 1 is computed by adding the $validityPeriod$ to the initial $toe$ of 0 as $0 + 6 \text{ hours} = 0 + 21600 \text{ seconds}$ . The new ephemeris is constructed by adding the delta ephemeris terms from set 1 to the reference ephemeris creating the new ephemeris, which will be used for the next six hours. For the five terms listed above ( $delta\_M0$ , $delta\_i0$ , $delta\_OMEGA0$ , $af0$ , and $af1$ ) the extrapolation described must occur prior to the addition of the delta term. + +The next ephemeris computation will occur by adding the $validityPeriod$ to the current $toe$ of 21600 as: $21600 + 6 \text{ hours} = 21600 + 21600 = 43200$ . The ephemeris delta terms from set two are added to the ephemeris resulting from the prior addition to create the next ephemeris. This is done for each satellite vehicle ID. + +##### GPS Ephemeris Extension check + +The GPS Ephemeris Extension check provides information about non foreseen events that occurred during the period starting at the $gpsBeginTime$ to the current time. An event is signified through a bit string. Each bits refers to one PRN. If a bit is set to one, this means that the ephemeris extension is no longer valid for this specific PRN. In order to indicate planned future maneuvers an end time is provided. The SMLC can indicate that a future event is planned between the current time and the end time of this ephemeris extension. + +**Table A.29.n: Ephemeris Extension check** + +| Parameter | Presence | Note | +|--------------------|----------|-----------------| +| $gpsBeginTime$ | M | See Table A.29o | +| $gpsEndTime$ | M | See Table A.29p | +| $gpsSatEventsInfo$ | M | See Table A.29q | + +###### GPS Begin Time + +The GPS begin time corresponds to the GPS Week and GPS Seconds of Estimation of the ephemeris extensions block. + +**Table A.29.o: GPS Begin Time** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------|--------|--------------|---------|-------| +| GPS Week | 10 | 1 | Weeks | M | +| GPS TOW | 20 | 1 | Seconds | M | + +###### GPS End Time + +The GPS end time represents the final time the Ephemeris extension is valid. + +**Table A.29.p: GPS End Time** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------|--------|--------------|---------|-------| +| GPS Week | 10 | 1 | Weeks | M | +| GPS TOW | 20 | 1 | Seconds | M | + +##### GPS Sat Event Information + +This IE is designed to indicate events that have or may occur between the $gpsBeginTime$ and the $gpsEndTime$ . +3GPP + +**Table A.29.q: GPS Sat Event Information** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------|--------|--------------|-------|-------| +| EventOccurred | 32 | - | - | M | +| FutureEventNoted | 32 | - | - | M | + +###### **EventOccurred** + +If a bit is clear in the eventOccured field it indicates that a satellite maneuver has not occurred since the ganssBeginTime nor is a maneuver planned for the next sixty minutes. + +###### **FutureEventNoted** + +If a bit is set in the futureEventNoted field it indicates that a maneuver is planned during the time period between current time plus sixty minutes and gpsEndTime. + +##### **DGPS Corrections Validity Period** + +This element is an extension to the DGPS Corrections IE and provides the validity period of the differential corrections for each satellite included in the DGPS Corrections IE (see Table A.15). This element may only be included if the DGPS Corrections IE is included in the GPS Assistance Data element. + +**Table A.29r: DGPS Corrections Validity Period** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-------------------------------------------------------------|--------|--------------|-------|-------|-------| +| N_SAT | 4 | 1 | 1-16 | --- | M | +| The following fields occur once per satellite (N_SAT times) | | | | | | +| SatID | 6 | --- | 0-63 | -- | M | +| UDRE Growth Rate | 3 | --- | 0-7 | --- | M | +| Time of Validity for UDRE Growth Rate | 3 | --- | 0-7 | --- | M | + +##### **N\_SAT** + +This field indicates the number of satellites for which differential corrections validity period is available. This field shall be set to the same value as the N\_SAT parameter in the DGPS Corrections element in Table A.15. + +###### **SatID** + +This field identifies the satellite for which the corrections validity period is applicable. The values ranging from 0 to 63 represent satellite PRNs ranging from 1 to 64, respectively. The UDRE Growth Rate and Time of Validity for UDRE Growth Rate IEs shall be included for the same satellite IDs as the differential corrections in Table A.15 are provided. + +###### **UDRE Growth Rate** + +This field provides an estimate of the growth rate of uncertainty ( $1-\sigma$ ) in the corrections for the particular satellite identified by SatID. The estimated UDRE at time value specified in the "Time of Validity for UDRE Growth Rate" $t_i$ is calculated as follows: + +$$UDRE(t_0+t_i) = UDRE(t_0) \times \text{UDRE Growth Rate}$$ + +where $t_0$ is the DGPS Reference Time GPS TOW for which the corrections in Table A.15 are valid, $t_i$ is the "Time of Validity for UDRE Growth Rate" field as shown in Table A.29t, $UDRE(t_0)$ is the User Differential Range Error field as provided in Table A.15, and "UDRE Growth Rate" field is the factor as shown in Table A.29s. + +**Table A.29s: Values of UDRE Growth Rate IE** + +| Value | Indication | +|-------|------------| +| 000 | 1,5 | +| 001 | 2 | +| 010 | 4 | +| 011 | 6 | +| 100 | 8 | +| 101 | 10 | +| 110 | 12 | +| 111 | 16 | + +###### **Time of Validity for UDRE Growth Rate** + +This field specifies the time when the "UDRE Growth Rate" field applies. The meaning of the values for this field is described in Table A.29t. + +**Table A.29t: Time of Validity for UDRE Growth Rate IE** + +| Value | Indication [seconds] | +|-------|----------------------| +| 000 | 20 | +| 001 | 40 | +| 010 | 80 | +| 011 | 160 | +| 100 | 320 | +| 101 | 640 | +| 110 | 1280 | +| 111 | 2560 | + +##### **GPS Reference Time Extension** + +This element is an extension to the Reference Time IE and is shown in Table A.29u. If Reference Time is provided by the SMLC, the GPS Reference Time Extension shall also be provided. + +NOTE: For reasons of backward compatibility, this IE is not defined for a Release 9 or earlier SMLC and would be ignored, when received, by a Release 9 or earlier MS. This means that when the element is expected but is not received, the SMLC is Release 9 or earlier. + +**Table A.29u: Reference Time Extension** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-----------------------|--------|--------------|-------|------------|-------| +| GPS Week Cycle Number | 3 | 1 | 0 - 7 | 1024 weeks | M | + +##### **GPS Week Cycle Number** + +This field provides the number of 1024 GPS week cycles occurred since the GPS zero time-point (midnight of the night of January 5, 1980/morning of January 6, 1980). The first 1024 GPS weeks since the zero time-point is GPS Week Cycle Number 0. + +##### **GPS Acquisition Assistance Extension** + +This element is an extension to the Acquisition Assistance IE and is shown in Table A.29v. If Acquisition Assistance is provided by the SMLC, the GPS Acquisition Assistance Extension shall also be provided. + +NOTE: For reasons of backward compatibility, this IE is not defined for a Release 9 or earlier SMLC and would be ignored, when received, by a Release 9 or earlier MS. This means that when the element is expected but is not received, the SMLC is Release 9 or earlier. + +**Table A.29v: Acquisition Assistance Extension** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-------------------------------------------------------------|--------|--------------|-------------|---------|-------| +| N_SAT | 4 | 1 | 0-15 | --- | M | +| The following fields occur once per satellite (N_SAT times) | | | | | | +| SatID | 6 | --- | 0-63 | -- | M | +| Azimuth LSB | 4 | 0,703125 | 0-10,546875 | degrees | M | +| Elevation LSB | 4 | 0,703125 | 0-10,546875 | degrees | M | + +###### **N\_SAT** + +This field indicates the number of satellites for which Acquisition Assistance is provided. This field shall be set to the same value as the Number of Satellites parameter in the Acquisition Assist element in Table A.24. + +###### **SatID** + +This field identifies the satellite for which the Acquisition Assistance is provided. This field shall be set to the same value as the SVID/PRN field in Table A.25. + +###### **Azimuth LSB** + +This field specifies the 4 least significant bits of the satellite azimuth angle. The 5 most significant bits are provided in the Azimuth field in Table A.25. The full satellite azimuth is constructed as "Azimuth" $\times$ 11,25 + "Azimuth LSB" $\times$ 0,703125 degrees. + +###### **Elevation LSB** + +This field specifies the 4 least significant bits of the satellite elevation angle. The 5 most significant bits are provided in the Elevation field in Table A.25. The full satellite elevation is constructed as "Elevation" $\times$ 11,25 + "Elevation LSB" $\times$ 0,703125 degrees. + +##### **GPS Almanac Extension** + +This element is an extension to the Almanac IE and and is shown in Table A.29w. If Almanac is provided by the SMLC, the Almanac Extension shall also be provided. + +NOTE: For reasons of backward compatibility, this IE is not defined for a Release 9 or earlier SMLC and would be ignored, when received, by a Release 9 or earlier MS. This means that when the element is expected but is not received, the SMLC is Release 9 or earlier. + +**Table A.29w: Almanac Extension** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|---------------------------|--------|--------------|-------|---------|-------| +| Complete Almanac Provided | 1 | --- | --- | Boolean | M | + +###### **Complete Almanac Provided** + +This field indicates whether the SMLC provided Almanac for the full GPS constellation or not. TRUE means complete GPS almanac is provided. + +###### **GPS Acquisition Assistance Extension-R12** + +This element is an extension to the Acquisition Assistance IE and is shown in Table A.29x. The SMLC should include this field only if supported by the MS. + +**Table A.29x: Acquisition Assistance Extension-R12** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-------------------------------------------------------------|--------|--------------|--------------------------------------|---------|-------| +| Confidence | 7 | 1 | 0-100 | percent | O | +| N_SAT | 4 | 1 | 0-15 | --- | O | +| The following fields occur once per satellite (N_SAT times) | | | | | | +| SatID | 6 | --- | 0-63 | -- | M | +| Doppler Uncertainty Extension | 3 | --- | 300, 400, 500, 600, 'No Information' | Hz | M | + +###### Confidence + +This field specifies the confidence level of the reference location area or volume used to calculate the GPS Acquisition Assistance parameters (search windows). A high percentage value (e.g., 98% or more) indicates to the MS that the provided search windows are reliable. The SMLC should include this field to indicate the confidence level of the provided information. + +Range: 0 – 100 + +###### N\_SAT + +This field indicates the number of satellites for which GPS Acquisition Assistance Extension-R12 is provided. + +###### SatID + +This field identifies the satellite for which the GPS Acquisition Assistance Extension-R12 is provided. + +###### Doppler Uncertainty Extension + +If this field is present, the MS that supports this field shall ignore the Doppler Uncertainty (Table A.25) field. This field specifies additional Doppler uncertainty values. It is defined such that the Doppler experienced by a stationary MS is in the range [Doppler-Doppler Uncertainty Extension] to [Doppler+Doppler Uncertainty Extension]. + +Enumerated values define 300 Hz, 400 Hz, 500 Hz, 600 Hz, and "No Information". + +#### A.4.2.5 More Assistance Data To Be Sent Element + +#### A.4.2.5 More Assistance Data To Be Sent Element + +This element is set by the SMLC to indicate to the MS if more Assistance Data components or a the final RRLP Measure Position Request component will be sent in the current procedure in order to deliver the entire set of assistance data. + +#### A.4.2.6 GANSS Assistance Data + +The GANSS Assistance Data consists of two or more data elements depending on the number of GNSS constellations included in the GANSS Assistance Data. GANSS Assistance Data elements are of two different types: GANSS Common Assistance Data and GANSS Generic Assistance Data. GANSS Common Assistance Data element is included at most only once and it contains Information Elements that can be used with any GNSS constellation. GANSS Generic Assistance data element can be included multiple times depending on the number of GNSS constellations supported in the GANSS Assistance Data. One GANSS Generic Assistance Data element contains Information Elements dedicated only for one specific GNSS constellation at a time. If two or more constellations are supported, GANSS Generic Assistance Data is given for each constellation separately. + +The fields in GANSS Assistance Data are listed in Table A.30 below. As table A.30 shows, all fields are optional. + +**Table A.30: Fields in the GANSS Assistance Data element** + +| Element | Presence | Repetition | +|-------------------------------|----------|------------| +| GANSS Common Assistance Data | O | No | +| GANSS Generic Assistance Data | O | Yes | + +When RRLP pseudo-segmentation is used, Tables A.30, A.31 and A.39 indicate which elements may be repeated in more than one RRLP segment in order to provide data for multiple constellations, satellites or signals. When any such element – with the exception of the GANSS ID and SBAS ID element – appears in more than one segment, the following rules shall apply. + +1. There shall be no repetition of the same data for the same constellation, satellite or signal even though there might be multiple realizations of the IEs for the same constellation, satellite or signal. For example, DGANSS corrections may occur multiple times for the same satellite. + +2. Optional and conditional fields in the element not associated with a particular satellite or signal shall each appear in at most one RRLP segment. +3. Any mandatory field not associated with a particular satellite or signal shall assume consistent values in the case of a field related to current reference time and the same value otherwise. +4. The maximum number of constellations, satellites or signals defined in sub-clause 5.1 for which data can be included for any parameter in one RRLP segment shall apply also when counted over all RRLP segments. + +##### A.4.2.6.1 GANSS Common Assistance Data + +GANSS Common Assistance Data element contains GNSS constellation independent information elements that can be applied on any specific GNSS or on a combination of GNSS. GANSS Common Assistance Data fields are included in GANSS Assistance Data only once. This element can contain one or more of the fields listed in table A.31 below. As Table A.31 shows, all fields are optional. + +**Table A.31: GANSS Common Assistance Data content** + +| Element | Presence | Repetition | +|------------------------------------|----------|------------| +| GANSS Reference Time | O | No | +| GANSS Reference Location | O | No | +| GANSS Ionospheric Model | O | No | +| GANSS Additional Ionospheric Model | O | No | +| GANSS Earth Orientation Parameters | O | No | +| GANSS Reference Time Extension | O | No | + +###### GANSS Reference Time + +This field specifies the GANSS Time Of Day (TOD) with uncertainty and relationship between GANSS Reference Time and air-interface timing of the BTS transmission in the reference cell. These fields occur once per message; some are mandatory and some are optional, as shown in Table A.33. + +When GANSS TOD -GSM Time association is present, GANSS TOD and BCCH/BSIC/FNm/TN/BN IEs provide a valid relationship between GANSS TOD and GSM time, as seen at the approximate location of the MS, i.e. the propagation delay from BTS to MS shall be compensated for by the SMLC. Depending on implementation, the relation between GANSS TOD and GSM time may have varying accuracy. Therefore, the uncertainty of the timing relation is provided in GANSS TOD Uncertainty. If the propagation delay from BTS to MS is not accurately known, the SMLC shall use the best available approximation of the propagation delay and take the corresponding delay uncertainty into account in the calculation of the field GANSS TOD Uncertainty. When GANSS TOD -GSM Time association is not present, GANSS TOD is an estimate of current GANSS TOD at time of reception of the RRLP segment containing this data by the MS. The SMLC should achieve an accuracy of +/- 3 seconds for this estimate including allowing for the transmission delay between SMLC and MS of the RRLP segment containing GANSS TOD. Note that the MS should further compensate GANSS TOD for the time between the reception of the segment containing GANSS TOD and the time when the GANSS TOD field is used. + +**Table A.33: GANSS Reference Time** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-----------------------------------------------------------------------------------------------|--------|------------------|----------------------------|-----------|------------| +| GANSS Reference Time Information (once per message) | | | | | | +| GANSS Day | 13 | 1 | 0 - 8191 | day | M | +| GANSS TOD | 17 | 1 | 0 - 86399 | sec | M | +| GANSS TOD Uncertainty | 7 | - | 0...127 | - | O | +| GANSS_TIME_ID | 3 | --- | --- | --- | O (note 3) | +| GANSS TOD - GSM Time Association (once per message) | | | | | | +| BCCH Carrier | 10 | 1 | 0 - 1023 | --- | O (note 1) | +| BSIC | 6 | 1 | 0 - 63 | --- | O (note 1) | +| FN m | 21 | 1 | 0 - (2 21 -1) | frames | O (note 1) | +| TN | 3 | 1 | 0 - 7 | timeslots | O (note 1) | +| BN | 8 | 1 | 0 - 156 | bits | O (note 1) | +| FN 1 | 7 | 2 -30 | -5,9605e-8 -
+5,8673e-8 | sec/sec | O (note 2) | +| NOTE 1: All of these fields shall be present together, or none of them shall be present. | | | | | | +| NOTE 2: This field can be optionally included if GANSS TOD - GSM Time association is present. | | | | | | +| NOTE 3: Absence of this field means Galileo system time. | | | | | | + +###### GANSS Day + +This field specifies the sequential number of days (with day count starting at 0) from the origin of the GNSS system time indicated by GANSS\_TIME\_ID modulo 8192 days (about 22 years). The GNSS system time origin is defined in Table A.34 for each GANSS. + +NOTE: The number of 8192 day cycles since the GANSS zero time-point is provided in the GANSS Reference Time Extension in Table A.35c. + +###### GANSS TOD + +Integer number of GANSS TOD seconds within the current day. + +Range: 0 - 86399 s. + +###### GANSS TOD Uncertainty + +GANSS TOD uncertainty value as described in 3.2.9. This field is optional. + +###### GANSS\_TIME\_ID + +This field specifies the GNSS system time used in GANSS Reference Time. The SMLC shall set the GANSS\_TIME\_ID only to system times for corresponding GANSSs supported by the MS. + +**Table A.34: GANSS\_TIME\_ID** + +| GANSS_TIME_ID | Indication | GNSS System Time Origin | +|-------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Galileo System Time | (default) | Days from Galileo System Time (GST) start epoch, defined as 13 seconds before midnight between 21st August and 22nd August 1999; i.e., GST was equal to 13 seconds at August 22nd 1999 00:00:00 UTC | +| GPS System Time | 0 | January 6, 1980; 00:00:00 UTC(USNO) | +| QZSS System Time | 1 | January 6, 1980; 00:00:00 UTC(USNO) | +| GLONASS System Time | 2 | December 31 st 1995 21:00:00 UTC (SU), which is local UTC Moscow January 1 st 1996 00:00:00, defined as UTC(SU) + 3 hours in [17] | +| BDS | 3 | January 1, 2006 00:00:00 UTC (NTSC) | +| Reserved for future use | 4 - 7 | – | + +###### BCCH Carrier/BSIC/FNm/TN/BN/FNl + +These fields specify the state of the GSM frame number, respectively, of the reference BTS with the specified BCCH carrier and BSIC at the time that correspond to GANSS TOD. Also, the drift rate of the frame timing, FNl, with respect to the GANSS TOD is optionally given. The SMLC shall use the current serving BTS as the reference BTS. The target MS has the option of rejecting a GANSS position request or GANSS assistance data if the reference BTS is not the serving BTS. If FNm field is present in the assistance, cellular time parameters FNm/TN/BN shall be aligned with the integer GANSS TOD second given in GANSS TOD field. + +###### GANSS Reference Location + +The Reference Location field contains a 3-D location (with uncertainty) specified as per 3GPP TS 23.032. The purpose of this field is to provide the MS with a priori knowledge of its location in order to improve GNSS receiver performance. The allowed shape is 3-D location with uncertainty (ellipsoid point with altitude and uncertainty ellipsoid). As defined in 3GPP TS 23.032, the GANSS Reference Location is provided in WGS-84 reference system. + +NOTE: If GPS Assistance Data component is present as well, the SMLC should include the Reference Location either in the GPS Assistance Data or GANSS Common Assistance Data element. + +###### GANSS Ionospheric Model + +GANSS Ionospheric Model contains parameters to model the propagation delay of the GNSS signals through the ionosphere. The information elements in this field are shown in Table A.35. Proper use of these fields as defined in [11] allows a single-frequency GNSS receiver to remove the ionospheric delay from the pseudorange measurements. + +**Table A.35: GANSS Ionospheric Model** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------------------------------------------------------------------------------|--------|--------------|--------------------------------------|------------| +| GANSS Ionosphere Model Parameters | | | | | +| $a_{i0}$ | 11 | $2^{-2}$ | Solar Flux Units | M | +| $a_{i1}$ | 11 | $2^{-8}$ | Solar Flux Units/degree | M | +| $a_{i2}$ | 14 | $2^{-15}$ | Solar Flux Units/degree 2 | M | +| GANSS Ionosphere Regional Storm Flags | | | | | +| Storm Flag 1 | 1 | --- | --- | O (note 1) | +| Storm Flag 2 | 1 | --- | --- | O (note 1) | +| Storm Flag 3 | 1 | --- | --- | O (note 1) | +| Storm Flag 4 | 1 | --- | --- | O (note 1) | +| Storm Flag 5 | 1 | --- | --- | O (note 1) | +| NOTE 1: All of these fields shall be present together, or none of them shall be present. | | | | | + +###### GANSS Ionosphere Parameters + +The ionosphere model parameters are used to estimate the ionospheric distortions on pseudoranges as described in [11] section 5.1.6. + +###### GANSS Ionosphere Regional Storm Flags + +These fields specify the Ionosphere disturbance flags (1,...,5) for five different regions as described in [11] section 5.1.6. If the ionosphere disturbance flag for a region is not present the target device shall treat the ionosphere disturbance condition as unknown. + +###### GANSS Additional Ionospheric Model + +The GANSS Additional Ionospheric Model contains parameters to model the propagation delays of the GANSS signals through the ionosphere. The information elements in this field are shown in table A.35.a. + +When Data ID has the value '11' it indicates that the parameters have been generated by QZSS, and the parameters have been specialized and are applicable within the area defined in [16]. When Data ID has the value '00' it indicates the parameters are applicable worldwide [16]. All other values for Data ID are reserved. When Data ID has the value '01' it indicates that the parameters have been generated by BDS, and UE shall use these parameters according to the description given in 5.2.4.7 in [18]. + +**Table A.35.a: GANSS Additional Ionospheric Model** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------|--------|--------------|--------------------------------|-------| +| Data ID | 2 | -- | See text | M | +| $\alpha_0$ | 8 | $2^{-30}$ | seconds | M | +| $\alpha_1$ | 8 | $2^{-27}$ | sec/semi-circle | M | +| $\alpha_2$ | 8 | $2^{-24}$ | sec/(semi-circle) 2 | M | +| $\alpha_3$ | 8 | $2^{-24}$ | sec/(semi-circle) 3 | M | +| $\beta_0$ | 8 | $2^{11}$ | seconds | M | +| $\beta_1$ | 8 | $2^{14}$ | sec/semi-circle | M | +| $\beta_2$ | 8 | $2^{16}$ | sec/(semi-circle) 2 | M | +| $\beta_3$ | 8 | $2^{16}$ | sec/(semi-circle) 3 | M | + +###### GANSS Earth Orientation Parameters + +The GANSS Earth Orientation Parameters provides parameters to construct the ECEF and ECI coordinate transformation as defined in [12] and are shown in Table A.35.b. GANSS Earth Orientation Parameters indicate the relationship between the Earth's rotational axis and WGS-84 reference system. + +**Table A.35.b: GANSS Earth Orientation Parameters** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-------------------------|--------|--------------|-----------------|-------| +| $t_{\text{eop}}$ | 16 | $2^4$ | seconds | M | +| PM_X | 21 | $2^{-20}$ | arc-seconds | M | +| PM_X_dot | 15 | $2^{-21}$ | arc-seconds/day | M | +| PM_Y | 21 | $2^{-20}$ | arc-seconds | M | +| PM_Y_dot | 15 | $2^{-21}$ | arc-seconds/day | M | +| $\Delta\text{UT1}$ | 31 | $2^{-24}$ | seconds | M | +| $\Delta\text{UT1\_dot}$ | 19 | $2^{-25}$ | seconds/day | M | + +###### **GANSS Reference Time Extension** + +This element is an extension to the GANSS Reference Time IE and is shown in Table A.35c. If GANSS Reference Time is provided by the SMLC, the GANSS Reference Time Extension shall also be provided. + +NOTE: For reasons of backward compatibility, this IE is not defined for a Release 9 or earlier SMLC and would be ignored, when received, by a Release 9 or earlier MS. This means that when the element is expected but is not received, the SMLC is Release 9 or earlier. + +**Table A.35c: GANSS Reference Time Extension** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|------------------------|--------|--------------|-------|-----------|-------| +| GANSS Day Cycle Number | 3 | 1 | 0 - 7 | 8192 days | M | + +###### **GANSS Day Cycle Number** + +This field provides the number of 8192 day cycles occurred since the GANSS zero time-point defined in Table A.34. The first 8192 GANSS days since the zero time-point is GANSS Day Cycle Number 0. + +##### **A.4.2.6.2 GANSS Generic Assistance Data** + +GANSS Generic Assistance data elements contain Information Elements that are applied on one specific GNSS at a time indicated by GANSS\_ID. The format of the IE's remains the same regardless of the GANSS; only the values of the parameters and inclusion of certain optional fields will vary. + +GANSS Generic Assistance Data is repeated for each GNSS included in GANSS Assistance Data. GANSS Generic Assistance Data can contain one or more of the elements listed in Table A.39 below. As Table A.39 shows, all fields are optional. + +**Table A.39: GANSS Generic Assistance Data content** + +| Element | Presence | Repetition | +|-------------------------------------------|------------|------------| +| GANSS ID | O (note 1) | Yes | +| GANSS Time Model | O | Yes | +| DGANSS Corrections | O | Yes | +| GANSS Navigation Model | O | Yes | +| GANSS Real-Time Integrity | O | Yes | +| GANSS Data Bit Assistance | O | Yes | +| GANSS Reference Measurement Information | O | Yes | +| GANSS Almanac Model | O | Yes | +| GANSS UTC Model | O | Yes | +| GANSS Ephemeris Extension | O | Yes | +| GANSS Ephemeris Ext Check | O | Yes | +| SBAS ID | O | Yes | +| GANSS Additional UTC Model | O | Yes | +| GANSS Auxiliary Information | O | Yes | +| DGANSS Corrections Validity Period | O | Yes | +| GANSS Time Model Extension | O | Yes | +| GANSS Reference Measurement Extension | O | Yes | +| GANSS Almanac Model Extension | O | Yes | +| GANSS Almanac Model Extension-R12 | O | Yes | +| GANSS Reference Measurement Extension-R12 | O | Yes | +| DBDS Corrections | O (note 2) | Yes | +| BDS Grid Model | O (note 2) | Yes | + +NOTE 1: Absence of this field means Galileo. +NOTE 2: The field may be present if the GANSS ID = BDS; otherwise it is not present. + +###### **GANSS\_ID** + +This field indicates the GNSS for which the following assistance data IE's in GANSS Generic Assistance Data element are dedicated. The supported GANSS are listed in Table A.40. Absence of this field indicates Galileo. If GANSS ID indicates SBAS, the SBAS ID shall be included to indicate the specific SBAS addressed. + +Range: 0 - 7 + +**Table A.40: GANSS\_ID** + +| GANSS_ID | Indication | +|-------------------------|------------| +| SBAS | 0 | +| Modernized GPS | 1 | +| QZSS | 2 | +| GLONASS | 3 | +| BDS | 4 | +| Reserved for future use | 5-7 | + +###### **GANSS Time Model** + +This field specifies a model to relate GNSS system time to a selected time reference. GNSS Time Offset ID (GNSS\_TO\_ID) identifies the GNSS for which the relation is provided. + +The SMLC may send multiple GANSS Time Models (up to 7) for a specific GNSS depending on the number of the allowed satellite systems in GANSS Positioning Method. For example, the SMLC may send two GANSS Time Models for Galileo to give the relations between Galileo and two GNSS system times. + +NOTE: The integer number of seconds of the GNSS-GNSS Time Offset is provided in the GANSS Time Model Extension in Table A.55.22. + +**Table A.41: GANSS Time Model** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|---------------------------------|--------|--------------|------------|----------------------|----------| +| GANSS Time Model Reference Time | 16 | $2^4$ | 0 - 604784 | s | M | +| $T_{A0}$ | 32 | $2^{-35}$ | | sec | M | +| $T_{A1}$ | 24 | $2^{-51}$ | | sec/sec | O (NOTE) | +| $T_{A2}$ | 7 | $2^{-68}$ | | sec/sec 2 | O (NOTE) | +| GNSS_TO_ID | 3 | --- | --- | --- | M | +| Week Number | 13 | 1 | 0 - 8191 | week | O | + +NOTE: The fields indicated by "NOTE" should not be included if GPS Reference Time is provided in the assistance data. + +###### **GANSS Time Model Reference Time** + +This field specifies the reference time of week for GANSS Time Model and it is given in GNSS specific system time. + +Range: 0 604784 seconds + +###### **$T_{A0}/T_{A1}/T_{A2}$** + +These fields specify the GANSS Time Model for a specific GNSS system by constant and first and second order terms of polynomial. The first and second order terms are optional. + +###### **GNSS\_TO\_ID** + +This field specifies GNSS Time Offset ID. GANSS Time Model contains parameters to convert GNSS System Time from the system indicated by GANSS\_ID to GNSS System Time indicated by GNSS\_TO\_ID. The conversion is defined in [12,13,14]. The SMLC should include a GANSS Time Model for the same GANSS\_ID as the GANSS\_TIME\_ID in GANSS Reference Time. If the SMLC does not include a GANSS Time Model for the same GANSS\_ID as the GANSS\_TIME\_ID in GANSS Reference Time or if GANSS Reference Time is not included the MS assumes $T_{A1}$ and $T_{A2}$ are equal to zero. + +**Table A.42: GNSS\_TO\_ID** + +| GNSS_TO_ID | Indication | +|-------------------------|------------| +| GPS | 0 | +| GALILEO | 1 | +| QZSS | 2 | +| GLONASS | 3 | +| BDS | 4 | +| Reserved for future use | 5-7 | + +###### **Week Number** + +This field specifies the reference week of GANSS Time Model given in GNSS specific system time. This field is optional. + +NOTE: The time relationship between the system time indicated by GANSS\_ID and system time indicated by GNSS\_TO\_ID is given by the following equation [12,13,14]: + +$$t_{\text{GNSS}} = t_E - (A_{0\text{GGTO}} + A_{1\text{GGTO}}(t_E - t_{\text{GGTO}} + 604800(WN - WN_{\text{GGTO}})) + A_{2\text{GGTO}}(t_E - t_{\text{GGTO}} + 604800(WN - WN_{\text{GGTO}}))^2)$$ + +where + +$t_{\text{GNSS}}$ is the system time of week for the GNSS indicated by GNSS\_TO\_ID. + +$t_E$ is the system time of week for the GNSS indicated by GANSS\_ID. + +WN is the week number of the GNSS system time indicated GANSS\_ID corresponding to the $t_E$ . + +$t_{\text{GGTO}}$ is the system time of week for the time model data in the GNSS time indicated by GANSS\_ID and given by the GANSS Time Model Reference Time field. + +$WN_{\text{GGTO}}$ is the week number for the time model data in the GNSS time indicated by GANSS\_ID corresponding to the $t_{\text{GGTO}}$ and given by the Week Number field. + +$A_{0\text{GGTO}}$ is given by the $T_{A0}$ field. + +$A_{1\text{GGTO}}$ is given by the $T_{A1}$ field. + +$A_{2\text{GGTO}}$ is given by the $T_{A2}$ field. + +If the $T_{A1}$ and $T_{A2}$ are not included in the GANSS Time Model, the MS assumes $A_{1\text{GGTO}}$ and $A_{2\text{GGTO}}$ are equal to zero. + +The GNSS system times in the GANSS Time Model and used in the equation above are all given in Time of Week (TOW) and Week Number (WN) in the indicated GNSS specific system time. For conversion between TOW/WN and Day Number/Time of Day (GANSS Day/GANSS TOD) a GNSS week consists of 7 days since the origin of the particular GNSS System time (with the week number count starting at 0), and a day consists of 86400 seconds. + +###### DGANSS Corrections + +These fields specify the DGANSS corrections to be used by the MS. + +**Table A.43: DGANSS Corrections** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|--------------------------------------------------------------------------|--------|--------------|--------------|------------|-------| +| The following fields occur once per message | | | | | | +| DGANSS Reference Time | 7 | 30 | 0 - 3570 | seconds | M | +| N_SGN_TYPE | 2 | 1 | 1 - 3 | --- | M | +| The following fields occur once per GANSS signal type (N_SGN_TYPE times) | | | | | | +| GANSS_Signal_ID | 3 | --- | --- | --- | M | +| Status/Health | 3 | 1 | 0 - 7 | --- | M | +| N_SAT | 4 | 1 | 1 - 16 | --- | M | +| The following fields occur once per satellite (N_SAT times) | | | | | | +| SV_ID | 6 | --- | 0..63 | --- | M | +| IOD | 10 | --- | --- | --- | M | +| UDRE | 2 | --- | 0 - 3 | --- | M | +| PRC | 12 | 0,32 | $\pm 655,04$ | meters | M | +| RRC | 8 | 0,032 | $\pm 4,064$ | meters/sec | M | + +###### DGANSS Reference Time + +This field indicates the baseline time for which the DGANSS corrections are valid as modulo 3600 s. DGANSS Reference Time is given in GNSS system time. + +Range: 0 - 3600 s + +###### N\_SGN\_TYPE + +This field indicates the number of GNSS signal types included in DGANSS Corrections IE. + +Range: 1 - 3 + +###### GANSS\_Signal\_ID + +3GPP + +DGANSS corrections are provided per GNSS signal type identified by GANSS\_Signal\_ID. The supported signals are listed in Table A.59. + +###### Status/Health + +This field indicates the status of the differential corrections contained in the broadcast message. The values of this field and their respective meanings are shown below in Table A.44. + +**Table A.44: Values of Status/Health IE** + +| Code | Indication | +|------|----------------------------------------------| +| 000 | UDRE Scale Factor = 1,0 | +| 001 | UDRE Scale Factor = 0,75 | +| 010 | UDRE Scale Factor = 0,5 | +| 011 | UDRE Scale Factor = 0,3 | +| 100 | UDRE Scale Factor = 0,2 | +| 101 | UDRE Scale Factor = 0,1 | +| 110 | Reference Station Transmission Not Monitored | +| 111 | Data is invalid - disregard | + +The first six values in this field indicate valid differential corrections. When using the values described below, the "UDRE Scale Factor" value is applied to the UDRE values contained in the message. The purpose is to indicate an estimate in the amount of error in the corrections. + +The value "110" indicates that the source of the differential corrections (e.g., reference station or external DGANSS network) is currently not being monitored. The value "111" indicates that the corrections provided by the source are invalid, as judged by the source. In the later case, the message shall contain no corrections for individual satellites. Any MS that receives DGANSS Corrections in a GANSS Assistance Data IE shall contain the appropriate logic to properly interpret this condition and look for the next IE. + +###### N\_SAT + +This field indicates the number of satellites (per specified GANSS\_Signal\_ID) for which differential corrections are included in this element. + +Range: 1 - 16 + +###### SV\_ID + +The SV ID is an index number for a satellite. The interpretation of SV ID is defined in Table A.10.14. + +###### Issue Of Data + +Issue of Data field contains the identity for the GANSS Navigation Model, as defined in Table A.48.2 (i.e., excluding the IOD\_MSB, if applicable for the particular GANSS or signal). + +###### User Differential Range Error (UDRE) + +This field provides an estimate of the uncertainty ( $1-\sigma$ ) in the corrections for the particular satellite. The value in this field shall be multiplied by the UDRE Scale Factor in the common Corrections Status/Health field to determine the final UDRE estimate for the particular satellite. The meanings of the values for this field are described in Table A.45. + +**Table A.45: Values of UDRE IE** + +| Value | Indication | +|-------|-------------------------------------------| +| 00 | $UDRE \leq 1,0 \text{ m}$ | +| 01 | $1,0 \text{ m} < UDRE \leq 4,0 \text{ m}$ | +| 10 | $4,0 \text{ m} < UDRE \leq 8,0 \text{ m}$ | +| 11 | $8,0 \text{ m} < UDRE$ | + +Each UDRE value shall be adjusted based on the operation of an Integrity Monitor (IM) function which exists at the network (SMLC, GPS server, or reference GPS receiver itself). Positioning errors derived at the IM which are excessive relative to DGPS expected accuracy levels shall be used to scale the UDRE values to produce consistency. + +###### Pseudo-Range Correction (PRC) + +This field indicates the correction to the pseudorange for the particular satellite at DGANSS Reference Time, $t_0$ . The value of this field is given in meters (m) and the resolution is 0,32, as shown in Table A.43 above. The method of calculating this field is described in [9]. + +If the SMLC has received a request for GANSS assistance data from an MS which included a request for the navigation models and DGANSS (i.e., bit J and M are set to one in 'Requested GANSS Assistance Data, see 3GPP TS 49.031), the SMLC shall determine, for each satellite, if the navigation model stored by the MS is still suitable for use with DGANSS corrections (also see navigation model update conditions right before Table A.46) and if so and if DGANSS corrections are supported the SMLC should send DGANSS corrections without including the navigation model. + +The IOD value sent for a satellite shall always be the IOD value that corresponds to the navigation model for which the pseudo-range corrections are applicable. + +The pseudo-range correction shall correspond to the available navigation model (the one already stored in and identified by the MS or the one included in the same procedure as the pseudo-range correction). The MS shall only use the PRC value when the IOD value received matches its available navigation model. + +Pseudo-range corrections are provided with respect to GNSS specific geodetic datum (e.g., PZ-90.02 if GANSS ID indicates GLONASS). + +###### Pseudo-Range Rate Correction (RRC) + +This field indicates the rate-of-change of the pseudorange correction for the particular satellite, using the satellite ephemeris and clock corrections identified by the IOD IE. The value of this field is given in meters per second (m/sec) and the resolution is 0,032, as shown in table A.43 above. For some time $t_1 > t_0$ , the corrections for IOD are estimated by + +$$\text{PRC}(t_1, \text{IOD}) = \text{PRC}(t_0, \text{IOD}) + \text{RRC}(t_0, \text{IOD}) \cdot (t_1 - t_0) ,$$ + +and the MS uses this to correct the pseudorange it measures at $t_1$ , $\text{PR}_m(t_1, \text{IOD})$ , by + +$$\text{PR}(t_1, \text{IOD}) = \text{PR}_m(t_1, \text{IOD}) + \text{PRC}(t_1, \text{IOD}) .$$ + +The SMLC shall always send the RRC value that corresponds to the PRC value that it sends (see above for details). The MS shall only use the RRC value when the IOD value received matches its available navigation model. + +###### GANSS Navigation Model + +This set of fields contains information required to manage the transfer of precise navigation data to the GANSS-capable MS. In response to a request from a MS for GANSS Assistance Data, the SMLC shall determine whether to send the navigation model for a particular satellite to an MS based upon factors like the T-Toe limit specified by the MS and any request from the MS for DGANSS (also see above). This information includes control bit fields as well as satellite ephemeris and clock corrections and clock and orbit accuracy models. GANSS Orbit Model can be given in Keplerian parameters or as state vector in Earth-Centered Earth-Fixed coordinates, dependent on the GANSS-ID and the MS capabilities. The meaning of these parameters is defined in relevant ICDs of the particular GANSS and GNSS specific interpretations apply. For example, Modernized GPS and QZSS use the same model parameters but some parameters have a different interpretation [16]. + +GANSS Navigation Model element can contain data up to at most 32 satellites. The individual fields are given in Table A.46 and the conditions for their presence is discussed below. + +**Table A.46: GANSS Navigation Model contents** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|----------------------------------------------------------------------|------------------|--------------|-------|-------| +| Navigation Model Flow Control (once per message) | | | | | +| Num_Sat | 5 | 1 | --- | M | +| Non-Broadcast Indication | 1 | --- | --- | M | +| The following fields occur once per satellite (Num_Sat times) | | | | | +| SV ID | 6 | --- | --- | M | +| SV Health | 5 | --- | --- | M | +| IOD | 10 | --- | --- | M | +| GANSS Clock Model | See Table A.49.1 | --- | --- | M | +| GANSS Orbit Model | See Table A.49.2 | --- | --- | M | +| SV Health_MSB | 1 | --- | --- | O | +| IOD_MSB | 1 | --- | --- | O | +| SV Health Extension | 4 | -- | -- | O | + +###### **Num\_Sat** + +This field specifies the number of satellites that are included in the provided GANSS Navigation Model element. A range of 1-32 is available. This field is mandatory when the GANSS Navigation Model field is included in the GANSS Assistance Data message. + +###### **Non-Broadcast Indication** + +This field indicates if the GANSS Navigation Model Elements are not derived from satellite broadcast data or are given in a format not native to the GANSS. + +**Table A.47: Values of Non-Broadcast Indication Flag** + +| Value | Non-Broadcast Indication | +|-------|--------------------------------------------------------------------| +| 0 | GANSS Navigation Data elements corresponding with broadcasted data | +| 1 | GANSS Navigation Data element not derived from satellite broadcast | + +###### **SV\_ID** + +The field specifies the SV/Slot ID for which the GANSS Navigation Model Elements is given. The interpretation of SV ID is defined in Table A.10.14. + +Range: 0 - 63 + +###### **SV Health and SV Health\_MSB** + +This parameter gives information about the satellite's current health. The health values are GNSS system specific. The SV Health bits have the encoding as in Table A.48.1 for a particular GANSS. The SV Health\_MSB may be present for some GANSS or signals as defined in Table A.48.1. If SV Health\_MSB is present, the total SV Health information is created by appending the SV Health field to the SV Health\_MSB field. + +**Table A.48.1: Interpretation SV Health Bits** + +| GANSS | SV Health_MSB | SV Health Bit String(5) | | | | | +|------------------------------------|-----------------------|------------------------------------|--------------------------------|---------------------------|--------------------------|----------------| +| | | Bit 1 (MSB) | Bit 2 | Bit 3 | Bit 4 | Bit 5 (LSB) | +| Galileo [11, section 5.1.9.3] | --- (1) | E5a Data Validity Status | E5b Data Validity Status | E1-B Data Validity Status | E5a Signal Health Status | | +| Modernized GPS (2) | --- (1) | L1C Health [14] | L1 Health [12,13] | L2 Health [12,13] | L5 Health [12,13] | '0' (reserved) | +| SBAS (3) | --- (1) | Ranging On (0), Off(1) | Corrections On (0), Off (1) | Integrity On (0), Off(1) | '0' (reserved) | '0' (reserved) | +| QZSS QZS-L1 (4) | MSB of SV Health [16] | 5 LSBs of SV Health [16] | | | | | +| QZSS QZS-L1C/L2C/L5 (5) | --- (1) | L1C Health [16] | L1 Health [16] | L2 Health [16] | L5 Health [16] | '0' (reserved) | +| GLONASS | --- (1) | B n (MSB) [17, page 23] | F T [17, Table 4.4] | | | | +| BDS | --- (1) | B1I Health (SatH1) [18] | '0' (reserved) | | | | + +Note 1: The SV Health\_MSB field shall not be present in GANSS Navigation Model for these GANSS or GANSS signals. +Note 2: If a certain signal is not supported on the satellite indicated by SV\_ID, the corresponding health bit shall be set to '1' (i.e., signal can not be used). +Note 3: SV Health in case of GANSS ID indicates SBAS includes the 5 LSBs of the Health included in GEO Almanac Message Parameters (Type 17) [15]. +Note 4: If GANSS ID indicates 'QZSS', and GANSS Orbit Model-2 is included, this interpretation of SV Health applies. +Note 5: If GANSS ID indicates 'QZSS', and GANSS Orbit Model-3 is included, this interpretation of SV Health applies. + +###### SV Health Extension + +This parameter gives additional information about the satellite's current health. The health values are GNSS system specific. The SV Health Extension bits have the encoding as in Table A.48.1a for a particular GANSS. + +**Table A.48.1a: Interpretation SV Health Extension Bits** + +| GANSS | SV Health Extension Bit String(4) | | | | +|-------------------------------|-----------------------------------|-------|---------------------------|-------------| +| | Bit 1 (MSB) | Bit 2 | Bit 3 | Bit 4 (LSB) | +| Galileo [11, section 5.1.9.3] | E5b Signal Health Status | | E1-B Signal Health Status | | + +###### Issue Of Data + +Issue of Data field contains the identity for GANSS Navigation Model. The IOD\_MSB may be present for some GANSS or signals as defined in Table A.48.2a. If IOD\_MSB is present, the total IOD information is constructed as defined in Table A.48.2a. + +In the case of broadcasted Galileo ephemeris, the IOD contains the IODnav as described in [11]. + +In case of broadcasted Modernized GPS ephemeris, the IOD contains the 11-bit parameter $t_{oe}$ as defined in [12, Table 30-I] [14, Table 3.5-1] and is constructed using IOD and IOD\_MSB fields. + +In case of broadcasted SBAS ephemeris, the IOD contains the 8 bits Issue of Data as defined in [15] Message Type 9. + +In case of broadcasted QZSS QZS-L1 ephemeris, the IOD contains the IODC as described in [16]. + +In case of broadcasted QZSS QZS-L1C/L2C/L5 ephemeris, the IOD contains the 11-bit parameter $t_{oe}$ as defined in [16] and is constructed using IOD and IOD\_MSB fields. + +In case of broadcasted GLONASS ephemeris, the IOD contains the parameter $t_b$ as defined in [17]. + +In case of broadcasted BDS ephemeris, the IOD contains the 11 MSB bits of $t_{oe}$ as defined in [18]. + +**Table A.48.2: Interpretation of Issue Of Data** + +| GANSS | Parameter | # Bits | Scale Factor | Range | Units | +|-----------------------------------------|-----------------------------------------|---------------|---------------------|--------------|--------------| +| Galileo | IODnav | 10 | -- | 0-1023 | -- | +| Modernized GPS (1) | LSBs of $t_{oe}$ | 10 | 300 | 0-306900 | seconds | +| SBAS | IOD | 8 | -- | 0-255 | -- | +| QZSS – QZS-L1 (2) | IODC | 10 | -- | 0-1023 | -- | +| QZSS – QZS-L1C/L2C/L5 (1)(3) | LSBs of $t_{oe}$ | 10 | 300 | 0-306900 | seconds | +| GLONASS | $t_b$ | 7 | 15 | 15-1425 | minutes | +| BDS (4) | bit 2 (MSB) to bit 11 (MSB) of $t_{oe}$ | 10 | 512 | 0-524288 | seconds | + +Note 1: The MSB of $t_{oe}$ is provided in IOD\_MSB field. + +Note 2: If GANSS ID indicates 'QZSS', and GANSS Clock and Orbit Model-2 are included, this interpretation of IOD applies. + +Note 3: If GANSS ID indicates 'QZSS', and GANSS Clock and Orbit Model-3 are included, this interpretation of IOD applies . + +Note 4: If GANSS ID indicates 'BDS', the bit 2 (MSB) to bit 11 (MSB) are provided in IOD field and the bit 1 (MSB) is provided in IOD\_MSB field. + +**Table A.48.2a: Interpretation of IOD\_MSB** + +| GANSS(1) | IOD_MSB | Scale Factor | Units | Comment | +|----------------------------|-------------------------|---------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Modernized GPS | MSB of $t_{oe}$ | 307200 | seconds | The full $t_{oe}$ is constructed as "MSB of $t_{oe}$ " x 307200 + "LSBs of $t_{oe}$ " x 300 (Effective range of full $t_{oe}$ is 0-604500 seconds) | +| QZSS – QZS-L1C/L2C/L5 | MSB of $t_{oe}$ | 307200 | seconds | The full $t_{oe}$ is constructed as "MSB of $t_{oe}$ " x 307200 + "LSBs of $t_{oe}$ " x 300 (Effective range of full $t_{oe}$ is 0-604500 seconds) | +| BDS | Bit 1 (MSB) of $t_{oe}$ | 524288 | seconds | The full IOD is constructed as " IOD_MSB " x 524288+ "IOD" x 512 (Effective range of IOD is 0-604672 seconds) | + +Note 1: The IOD\_MSB field shall not be present in GANSS Navigation Model for GANSS or GANSS signals not defined in this Table. + +###### GANSS Clock Model + +GANSS clock model (Model-1) contains one or two clock model elements. If included, Clock Model-1 shall be included once or twice depending on the MS capability. + +If the MS is supporting multiple Galileo signals, the SMLC shall include both F/Nav and I/Nav clock models in GANSS Clock Model IE if the SMLC assumes the MS to perform Location Information calculation using multiple signals. The MS capabilities to support multiple GNSS frequencies are indicated in the Positioning Capability Response element (clause A.8). Otherwise, SMLC shall include only the model suitable for the GNSS. + +Table A.49.1: GANSS Clock Model + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-------------------------------------------------------------------------------------------|-------------------|--------------|----------------------|------------------| +| One of the following models can be included: | | | | | +| Model-1: | | | | | +| Satellite Clock Model (Galileo [11]) | | | | | +| $t_{oc}$ | 14 (1) | 60 | sec | C (1) | +| $af_2$ | 6 | $2^{-59}$ | sec/sec 2 | C (1) | +| $af_1$ | 21 | $2^{-46}$ | sec/sec | C (1) | +| $af_0$ | 31 | $2^{-34}$ | sec | C (1) | +| $T_{GD}$ (BGD) | 10 | $2^{-32}$ | sec | O (1) | +| Model ID | 1 | --- | --- | O | +| Model-2: | | | | | +| NAV Clock Model | | | | | +| $t_{oc}$ | 16 | $2^4$ | seconds | C (1) | +| $af_2$ | 8 | $2^{-55}$ | sec/sec 2 | C (1) | +| $af_1$ | 16 | $2^{-43}$ | sec/sec | C (1) | +| $af_0$ | 22 | $2^{-31}$ | seconds | C (1) | +| $T_{GD}$ | 8 | $2^{-31}$ | seconds | C (1) | +| Model-3: | | | | | +| CNAV/CNAV-2 Clock Model | | | | | +| $t_{oc}$ | 11 | 300 | seconds | C (1) | +| $t_{op}$ | 11 | 300 | seconds | C (1) | +| URA oc Index | 5 | --- | --- | C (1) | +| URA oc1 Index | 3 | --- | --- | C (1) | +| URA oc2 Index | 3 | --- | --- | C (1) | +| $a_{i2-n}$ | 10 | $2^{-60}$ | sec/sec 2 | C (1) | +| $a_{i1-n}$ | 20 | $2^{-48}$ | sec/sec | C (1) | +| $a_{i0-n}$ | 26 | $2^{-35}$ | seconds | C (1) | +| $T_{GD}$ | 13 | $2^{-35}$ | seconds | C (1) | +| ISC L1CP | 13 | $2^{-35}$ | seconds | O (2) | +| ISC L1CD | 13 | $2^{-35}$ | seconds | O (2) | +| ISC L1C/A | 13 | $2^{-35}$ | seconds | O (3) | +| ISC L2C | 13 | $2^{-35}$ | seconds | O (3) | +| ISC L5I5 | 13 | $2^{-35}$ | seconds | O (4) | +| ISC L5Q5 | 13 | $2^{-35}$ | seconds | O (4) | +| Model-4: | | | | | +| GLONASS Satellite Clock Model | | | | | +| $\tau_n(t_b)$ | 22 | $2^{-30}$ | seconds | C (1) | +| $\gamma_n(t_b)$ | 11 | $2^{-40}$ | --- | C (1) | +| $\Delta\tau_n$ | 5 | $2^{-30}$ | seconds | O | +| Model-5: | | | | | +| SBAS Satellite Clock Model | | | | | +| $t_0$ | 13 | 16 | seconds | C (1) | +| $a_{Gf0}$ | 12 | $2^{-31}$ | seconds | C (1) | +| $a_{Gf1}$ | 8 | $2^{-40}$ | Seconds/sec | C (1) | +| Model-6: | | | | | +| BDS Satellite Clock Model | | | | | +| AODC | 5 | --- | --- | C (1) | +| $t_{oc}$ | 17 | $2^3$ | seconds | C (1) | +| $a_0$ | 24 | $2^{-33}$ | sec/sec | C (1) | +| $a_1$ | 22 | $2^{-50}$ | sec/sec 2 | C (1) | +| $a_2$ | 11 | $2^{-66}$ | seconds | C (1) | +| $T_{GD}$ | 10 | $10^{-10}$ | seconds | C (1) | +| NOTE 1: All of these fields shall be present together, or none of them shall be present. | | | | | +| NOTE 2: Both of these fields shall be present together, or none of them shall be present. | | | | | +| NOTE 3: Both of these fields shall be present together, or none of them shall be present. | | | | | +| NOTE 4: Both of these fields shall be present together, or none of them shall be present. | | | | | + +Model ID + +This field specifies the identity of the clock model according to Table A.49.1a. This field is optional. + +**Table A.49.1a: Galileo Clock Model Identity** + +| Value | Identity | +|-------|----------| +| 0 | I/Nav | +| 1 | F/Nav | + +###### **GANSS Orbit Model** + +GANSS Orbit Model IE contains the following presentation: Satellite Navigation Model Using Keplerian Parameters or Satellite Navigation Model Using Earth-Centered, Earth-fixed Parameters as described in Table A.49.2. + +###### **Table A.49.2: GANSS Orbit Model** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|---------------------------------------------------------------------------------|------------|--------------|-----------------------|-------| +| One of the following models can be included: | | | | | +| Model-1: | | | | | +| Satellite Navigation Model Using Keplerian Parameters | | | | | +| $t_{oe}$ | $14^{(u)}$ | 60 | sec | C | +| $\omega$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Delta n$ | 16 | $2^{-43}$ | semi-circles/sec | C | +| $M_0$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Omega_{EGS88dot}$ | 24 | $2^{-43}$ | semi-circles/sec | C | +| $e$ | $32^{(u)}$ | $2^{-33}$ | --- | C | +| $ldot$ | 14 | $2^{-43}$ | semi-circles/sec | C | +| $\sqrt{A}$ | $32^{(u)}$ | $2^{-19}$ | meters $^{1/2}$ | C | +| $i_0$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Omega_{EGS88_0}$ | 32 | $2^{-31}$ | semi-circles | C | +| $C_{rs}$ | 16 | $2^{-5}$ | meters | C | +| $C_{is}$ | 16 | $2^{-29}$ | radians | C | +| $C_{us}$ | 16 | $2^{-29}$ | radians | C | +| $C_{rc}$ | 16 | $2^{-5}$ | meters | C | +| $C_{ic}$ | 16 | $2^{-29}$ | radians | C | +| $C_{uc}$ | 16 | $2^{-29}$ | radians | C | +| Model-2: | | | | | +| Satellite Navigation Model Using NAV Keplerian Parameters | | | | | +| URA Index | 4 | -- | -- | C | +| Fit Interval Flag | 1 | -- | Boolean | C | +| $t_{oe}$ | 16 | $2^4$ | sec | C | +| $\omega$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Delta n$ | 16 | $2^{-43}$ | semi-circles/sec | C | +| $M_0$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Omega_{EGS88dot}$ | 24 | $2^{-43}$ | semi-circles/sec | C | +| $e$ | $32^{(u)}$ | $2^{-33}$ | --- | C | +| $ldot$ | 14 | $2^{-43}$ | semi-circles/sec | C | +| $\sqrt{A}$ | $32^{(u)}$ | $2^{-19}$ | meters $^{1/2}$ | C | +| $i_0$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Omega_{EGS88_0}$ | 32 | $2^{-31}$ | semi-circles | C | +| $C_{rs}$ | 16 | $2^{-5}$ | meters | C | +| $C_{is}$ | 16 | $2^{-29}$ | radians | C | +| $C_{us}$ | 16 | $2^{-29}$ | radians | C | +| $C_{rc}$ | 16 | $2^{-5}$ | meters | C | +| $C_{ic}$ | 16 | $2^{-29}$ | radians | C | +| $C_{uc}$ | 16 | $2^{-29}$ | radians | C | +| Model-3: | | | | | +| Satellite Navigation Model Using CNAV/CNAV-2 Keplerian Parameters | | | | | +| $t_{op}$ | 11 | 300 | seconds | C | +| URA $_{oe}$ Index | 5 | --- | --- | C | +| $\Delta A$ | 26 | $2^{-9}$ | meters | C | +| $A\_dot$ | 25 | $2^{-21}$ | meters/sec | C | +| $\Delta n_0$ | 17 | $2^{-44}$ | semi-circles/sec | C | +| $\Delta n_0\_dot$ | 23 | $2^{-57}$ | semi-circles/sec $^2$ | C | +| $M_{0-n}$ | 33 | $2^{-32}$ | semi-circles | C | +| $e_n$ | 33 | $2^{-34}$ | --- | C | +| $\omega_n$ | 33 | $2^{-32}$ | semi-circles | C | +| $\Omega_{0-n}$ | 33 | $2^{-32}$ | semi-circles | C | +| $\Delta \Omega\_dot$ | 17 | $2^{-44}$ | semi-circles/sec | C | +| $i_{0-n}$ | 33 | $2^{-32}$ | semi-circles | C | +| $i_{0-n\_dot}$ | 15 | $2^{-44}$ | semi-circles/sec | C | +| $C_{is-n}$ | 16 | $2^{-30}$ | radians | C | +| $C_{ic-n}$ | 16 | $2^{-30}$ | radians | C | +| $C_{rs-n}$ | 24 | $2^{-8}$ | meters | C | +| $C_{rc-n}$ | 24 | $2^{-8}$ | meters | C | +| $C_{us-n}$ | 21 | $2^{-30}$ | radians | C | +| $C_{uc-n}$ | 21 | $2^{-30}$ | radians | C | +| Model-4: | | | | | +| Satellite Navigation Model Using GLONASS Earth-Centered, Earth-fixed Parameters | | | | | +| $E_n$ | $5^{(u)}$ | 1 | days | C | +| $P1$ | $2^{(u)}$ | -- | --- | C | + +| | | | | | +|------------------------------------------------------------------------------|------------------|-----------|--------------------------------|------------------| +| P2 | 1 (u) | 1 | --- | C | +| M | 2 (u) | 1 | --- | O | +| | 27 | $2^{-11}$ | kilometers | C | +| | 24 | $2^{-20}$ | kilometres/second | C | +| | 5 | $2^{-30}$ | kilometres/second 2 | C | +| | 27 | $2^{-11}$ | kilometers | C | +| | 24 | $2^{-20}$ | kilometres/second | C | +| | 5 | $2^{-30}$ | kilometres/second 2 | C | +| | 27 | $2^{-11}$ | kilometers | C | +| | 24 | $2^{-20}$ | kilometres/second | C | +| | 5 | $2^{-30}$ | kilometres/second 2 | C | +| Model-5: | | | | | +| Satellite Navigation Model Using SBAS Earth-Centered, Earth-fixed Parameters | | | | | +| $t_0$ | 13 | 16 | seconds | O (1) | +| Accuracy | 4 | -- | -- | C | +| $X_G$ | 30 | 0,08 | meters | C | +| $Y_G$ | 30 | 0,08 | meters | C | +| $Z_G$ | 25 | 0,4 | meters | C | +| $X_G$ Rate-of-Change | 17 | 0,000625 | meters/sec | C | +| $Y_G$ Rate-of-Change | 17 | 0,000625 | meters/sec | C | +| $Z_G$ Rate-of-Change | 18 | 0,004 | meters/sec | C | +| $X_G$ Acceleration | 10 | 0,0000125 | meters/sec 2 | C | +| $Y_G$ Acceleration | 10 | 0,0000125 | meters/sec 2 | C | +| $Z_G$ Acceleration | 10 | 0,0000625 | meters/sec 2 | C | +| Model-6: | | | | | +| Satellite Navigation Model Using BDS Keplerian Parameters | | | | | +| AODE | 5 | -- | -- | C | +| URA Index | 4 | -- | -- | C | +| $t_{oe}$ | 17 | $2^3$ | seconds | C | +| $A^{1/2}$ | 32 | $2^{-19}$ | meters 1/2 | C | +| $e$ | 32 | $2^{-33}$ | -- | C | +| $\omega$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Delta n$ | 16 | $2^{-43}$ | semi-circles/sec | C | +| $M_0$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Omega_0$ | 32 | $2^{-31}$ | semi-circles | C | +| $\Omega\_dot$ | 24 | $2^{-43}$ | semi-circles/sec | C | +| $i_0$ | 32 | $2^{-31}$ | semi-circles | C | +| $ldot$ | 14 | $2^{-43}$ | semi-circles/sec | C | +| $C_{uc}$ | 18 | $2^{-31}$ | radians | C | +| $C_{us}$ | 18 | $2^{-31}$ | radians | C | +| $C_{rc}$ | 18 | $2^{-6}$ | meters | C | +| $C_{rs}$ | 18 | $2^{-6}$ | meters | C | +| $C_{ic}$ | 18 | $2^{-31}$ | radians | C | +| $C_{is}$ | 18 | $2^{-31}$ | radians | C | +| Note 1: If GANSS Clock Model-5 is not included, this field shall be present. | | | | | +| NOTE u: unsigned parameter | | | | | + +###### GANSS Real-Time Integrity + +Integrity Monitor (IM) shall detect unhealthy (e.g., failed/failing) satellite signals and also shall inform users of measurement quality in DGANSS modes when satellite signals are healthy. Excessively large pseudo range errors, as evidenced by the magnitude of the corresponding DGANSS correction, shall be used to detect failed satellite signals. Unhealthy satellite signals should be detected within 10 seconds of the occurrence of the satellite signal failure. When unhealthy (e.g., failed/failing) satellite signals are detected, the assistance and/or DGANSS correction data shall not be supplied for these satellite signals. When the error in the IM computed position is excessive for solutions based upon healthy satellite signals only, DGANSS users shall be informed of measurement quality through the supplied UDRE values. After bad satellite signals have been indicated in the Real Time Integrity field, if the satellite signals return to healthy condition for some period of time, the indications for them shall be removed from this field. + +GANSS Real-Time Integrity field of the GANSS Assistance Data Information Element contains parameters that describe the real-time status of the GANSS constellations. Primarily intended for non-differential applications, the real-time integrity of the satellite constellation is of importance as there is no differential correction data by which the mobile can determine the soundness of each satellite signal. GANSS Real-Time Integrity data communicates the health of the GNSS signals to the mobile in real-time. The format is shown in Table A.50. The SMLC shall always transmit the GANSS Real Time Integrity field with the current list of unhealthy signals, for any GANSS positioning attempt and whenever GANSS Assistance Data is sent. If the number of bad signals (NBS) is zero, then the GANSS Real Time Integrity field shall be omitted. + +**Table A.50: GANSS Real-Time Integrity** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|--------------------------------------------------------------------|--------|--------------|-------|-------|-------| +| The following fields occur once per SV with bad signal (NBS times) | | | | | | +| Bad_GNSS_SV_ID | 6 | 1 | --- | --- | M | +| Bad_GNSS_Signal_ID | 8 | 1 | --- | --- | O | + +###### NBS (Number of satellites with bad signal) + +The NBS value indicates the number of satellites with bad signal. + +###### Bad\_GNSS\_SV\_ID + +This field specifies the SV ID of the satellite with bad signal or signals. The interpretation of SV ID is defined in Table A.10.14. + +###### Bad\_GNSS\_Signal\_ID + +This field identifies the bad signal of a satellite. Absence of this field means that all signals on the specific SV are bad. The interpretation of Bad\_GNSS\_Signal\_ID is listed in Table A.59. If the satellite in question belongs to the modernized GPS constellation and has some healthy signals but bad L1C/A signal, Bad\_GNSS\_Signal\_ID shall be present but may have all the bits set to '0'. Status of L1C/A signal shall be indicated with Real-Time Integrity IE in GPS Assistance Data Element. + +###### GANSS Data Bit Assistance + +This element provides data bit assistance data for specific satellite signals for data wipe-off. The data bits included in the assistance data depends on the GANSS and its signal. + +**Table A.51: GANSS Data Bit Assistance** + +| Parameter | Bits | Resolution | Range | Incl. | +|-------------------------------------------------------------|-------|------------|----------|-------| +| GANSS TOD | 6 | 1 | 0 – 59 | M | +| The following fields occur once per satellite (N_SAT times) | | | | | +| SV ID | 6 | 1 | --- | M | +| The following fields occur once per signal (N_SGN times) | | | | | +| GANSS_Signal_ID | 3 | 1 | 0 - 7 | M | +| N_BIT | 10 | 1 | 1 – 1024 | M | +| Data Bits | N_BIT | --- | --- | M | + +###### GANSS TOD + +This field indicates the reference time of the first bit of the data in GANSS Data Bit Assistance in integer seconds in GNSS specific system time. + +Data Bit Reference Time is given as modulo 60 s from GANSS TOD. + +###### N\_SAT + +This field specifies the number of satellites in GANSS Data Bit Assistance element. + +###### SV\_ID + +The field specifies the SV for which the GANSS Data Bit Assistance is given. The interpretation of SV ID is defined in Table A.10.14. + +Range: 0 – 63 + +###### **N\_SGN** + +This field specifies the number of signals for which GANSS Data Bit Assistance is provided. + +Range: 1 – 8 + +###### **GANSS\_Signal\_ID** + +This field specifies the GANSS signal type of the GANSS Data Bit Assistance as listed in Table A.59. + +###### **N\_BIT** + +This field indicates the number of bits (or symbols) included in the IE. + +###### **Data Bits** + +Data bits are contained in GNSS system and data type specific format. + +In case of Galileo, it contains the FEC encoded and interleaved modulation symbols. The logical levels 1 and 0 correspond to signal levels -1 and +1, respectively. In case of Modernized GPS L1C, it contains the encoded and interleaved modulation symbols as defined in [14] section 3.2.3.1. + +In case of Modernized GPS L2C, it contains either the NAV data modulation bits, the FEC encoded NAV data modulation symbols, or the FEC encoded CNAV data modulation symbols, dependent on the current signal configuration of this satellite as defined in [12, Table 3-III]. + +In case of Modernized GPS L5, it contains the FEC encoded CNAV data modulation symbols as defined in [13]. + +In case of SBAS, it contains the FEC encoded data modulation symbols as defined in [15]. + +In case of QZSS QZS-L1, it contains the NAV data modulation bits as defined in [16] section 5.2. In case of QZSS QZS-L1C, it contains the encoded and interleaved modulation symbols as defined in [16] section 5.3. In case of QZSS QZS-L2C, it contains the encoded modulation symbols as defined in [16] section 5.5. In case of QZSS QZS-L5, it contains the encoded modulation symbols as defined in [16] section 5.6. + +In case of GLONASS, it contains the 100 sps differentially Manchester encoded modulation symbols as defined in [17] section 3.3.2.2. + +In case of BDS, it contains the encoded and interleaved modulation symbols as defined in [18] section 5.1.3. + +###### **GANSS Reference Measurement Information** + +This field provides reference code and Doppler measurement information of visible satellites of a GANSS constellation. The information can be used as acquisition assistance to improve the sensitivity of the receiver. + +These parameters describe the range and optionally the derivatives from respective satellites to the GANSS Reference Location at the GANSS Reference Time. The code phase and Doppler fields are aligned with the time provided in GANSS Reference Time. Figure A.4a illustrates the relation between some of the fields with respect to the GANSS TOD. + +If GPS Acquisition Assistance is included the Reference Time included in the GPS Acquisition Assistance is also valid for the GANSS Reference Measurement fields and the parameters are referenced to GPS TOW. Figure A.4b illustrates the relation between some of the fields with respect to GPS TOW. + +The parameters are given in units of ms and m/s which makes it possible to convert the values to any nominal frequency and chipping and code rate. + +**Table A.52: GANSS Reference Measurement Information Contents** + +| Parameter | Range | Bits | Resolution | Incl. | +|---------------------------------------------------------------|-----------------------------------------------------------|------|------------------------|--------------------| +| GANSS_Signal_ID | 0 - 7 | 3 | --- | M | +| The following fields occur once per satellite (Num_Sat times) | | | | | +| SV_ID | 0 - 63 | 6 | | M | +| Doppler (0 th order term) | -1024 m/s to 1023,5 m/s | 12 | 0,5 m/s | M | +| Doppler (1 st order term) | -0,2 - 0,1 m/s 2 | 6 | 1/210 m/s 2 | O (1) | +| Doppler Uncertainty | 2,5 m/s - 40 m/s
[2 -n (40) m/s, n = 0 - 4] | 3 | --- | O (1,3) | +| Code Phase | 0 - (1-2 -10 ) ms | 10 | 2 -10 ms | M | +| Integer Code Phase | 0 - 127 ms | 7 | 1 ms | M | +| Code Phase Search Window | See Table A.53 | 5 | --- | M | +| Azimuth | 0 - 348,75 deg | 5 | 11,25 deg | O (2) | +| Elevation | 0 - 78,75 deg | 3 | 11,25 deg | O (2) | +| Code Phase_1023 | boolean | 1 | --- | O | + +NOTE 1,2: All of these fields shall be present together, or none of them shall be present. +NOTE 3: If Doppler Uncertainty Extension (Table A.55.25) is present, Doppler Uncertainty shall be set to value 0 (40 m/s). + +![Figure A.4a: Exemplary calculations of some GANSS Reference Measurement fields with respect to GANSS TOD. The diagram shows a timeline of GANSS TOD in integer seconds [s] from 9 to 10. At the Reference Location, the Predicted SV#1 time tsv_1 [ms] is shown as a sequence from 9920 to 9926, with a calculation: tsv_1 = t + Δtsv - τ. The GANSS Reference Measurement for SV#1 shows GANSS TOD = 10 s (10000 ms), Code Phase ~ 0.6383 ms, and Integer Code Phase = 10000 - 9922 = 78 ms. The expected tsv_1 [ms] in the MS is calculated as tsv_1 = GANSS TOD - Integer Code Phase + Code Phase = 10000 - 78 + 0.6383 = 9922.6383 ms. The Predicted SV #N_SAT time tsv_nsat [ms] is shown as a sequence from 9924 to 9930. The SV #N_SAT clock bias Δtsv_nsat is indicated. The chosen reference time in integer seconds [s] for GANSS Reference Measurements is 10 s. The SV #1 clock bias Δtsv_1 (t = tsv - Δtsv_1) is also indicated.](6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg) + +SV #1 clock bias $\Delta t_{sv\_1}$ +( $t = tsv - \Delta t_{sv\_1}$ ) + +At SV#1 SV #1 time tsv1 [ms] 9997 9998 9999 10000 10001 10002 10003 + +SV #N\_SAT clock bias $\Delta t_{sv\_nsat}$ + +At SV#N\_SAT SV #N\_SAT time tsvn\_sat [ms] 9997 9998 9999 10000 10001 10002 10003 + +Chosen reference time in integer seconds [s] for GANSS Reference Measurements + +GANSS TOD in integer seconds [s] + +GANSS TOD t [s] (a GNSS system time) 9 10 + +~0.6383 ms + +At Reference Location Predicted SV#1 time tsv\_1 [ms] 9920 9921 9922 9923 9924 9925 9926 + +Exemplary calculation of predicted tsv + $tsv_1 = t + \Delta t_{sv} - \tau$ + $\tau$ : propagation delay from SV to MS + $\Delta t_{sv}$ : clock bias + +GANSS Reference Measurement for SV#1 +GANSS TOD = 10 s (10000 ms) +Code Phase ~ 0.6383 ms +Integer Code Phase = 10000 - 9922 = 78 ms + +Exemplary calculation of the expected tsv\_1 [ms] in the MS + $tsv_1 = \text{GANSS TOD} - \text{Integer Code Phase} + \text{Code Phase} = 10000 - 78 + 0.6383 = 9922.6383 \text{ ms}$ + +Predicted SV #N\_SAT time tsv\_nsat [ms] 9924 9925 9926 9927 9928 9929 9930 + +~0.7849 ms + +Figure A.4a: Exemplary calculations of some GANSS Reference Measurement fields with respect to GANSS TOD. The diagram shows a timeline of GANSS TOD in integer seconds [s] from 9 to 10. At the Reference Location, the Predicted SV#1 time tsv\_1 [ms] is shown as a sequence from 9920 to 9926, with a calculation: tsv\_1 = t + Δtsv - τ. The GANSS Reference Measurement for SV#1 shows GANSS TOD = 10 s (10000 ms), Code Phase ~ 0.6383 ms, and Integer Code Phase = 10000 - 9922 = 78 ms. The expected tsv\_1 [ms] in the MS is calculated as tsv\_1 = GANSS TOD - Integer Code Phase + Code Phase = 10000 - 78 + 0.6383 = 9922.6383 ms. The Predicted SV #N\_SAT time tsv\_nsat [ms] is shown as a sequence from 9924 to 9930. The SV #N\_SAT clock bias Δtsv\_nsat is indicated. The chosen reference time in integer seconds [s] for GANSS Reference Measurements is 10 s. The SV #1 clock bias Δtsv\_1 (t = tsv - Δtsv\_1) is also indicated. + +**Figure A.4a. Exemplary calculations of some GANSS Reference Measurement fields with respect to GANSS TOD.** + +![Figure A.4b: Exemplary calculations of some GANSS Reference Measurement fields with respect to GPS TOW. The diagram shows a timeline for GPS TOW and satellite times (SV #1 and SV #N_SAT) with various offsets and calculations for clock bias and predicted times.](1bc1746388cb64bf23b356ce2365dfc2_img.jpg) + +The diagram illustrates the relationship between GPS TOW and satellite times for GANSS reference measurements. A vertical dashed line marks the 'Chosen reference epoch [ms] in GPS Acquisition assistance' at 10000 ms. + +- SV #1 time tsv1 [ms]:** Shows a timeline from 9997 to 10003 ms. The clock bias $\Delta_{\text{tsv\_1}}$ is indicated between 9999 ms and the reference epoch. +- SV #N\_SAT time tsvn\_sat [ms]:** Shows a timeline from 9997 to 10003 ms. The clock bias $\Delta_{\text{tsv\_nsat}}$ is indicated between 9999 ms and the reference epoch. +- GPS TOW t [ms]:** Shows a timeline from 9997 to 10003 ms. A 1 ms interval is marked between 9997 and 9998 ms. +- Predicted SV#1 time tsv\_1 [ms]:** Shows a timeline from 9920 to 9926 ms. A delay of ~0.6383 ms is indicated from the reference epoch. +- Predicted SV #N\_SAT time tsv\_nsat [ms]:** Shows a timeline from 9924 to 9930 ms. A delay of ~0.7849 ms is indicated from the reference epoch. + +**Exemplary calculation of predicted tsv** + $\text{tsv} = t + \Delta_{\text{tsv}} - \tau$ + $\tau$ : propagation delay from SV to MS + $\Delta_{\text{tsv}}$ : clock bias + +**GANSS Reference Measurement for SV#1** + GPS TOW = 10000 ms (a multiple of 80 ms) + Code Phase ~ 0.6383 ms + Integer Code Phase = 10000 - 9922 = 78 ms + +**Exemplary calculation of the expected tsv\_1 [ms] in the MS** + $\text{tsv\_1} = \text{GPS TOW} - \text{Integer Code Phase} + \text{Code Phase} = 10000 - 78 + 0.6383 = 9922.6383 \text{ ms}$ + +Figure A.4b: Exemplary calculations of some GANSS Reference Measurement fields with respect to GPS TOW. The diagram shows a timeline for GPS TOW and satellite times (SV #1 and SV #N\_SAT) with various offsets and calculations for clock bias and predicted times. + +**Figure A.4b. Exemplary calculations of some GANSS Reference Measurement fields with respect to GPS TOW.** + +###### GANSS\_Signal\_ID + +This field specifies the GNSS signal type. The supported signals are listed in Table A.59. + +###### Num\_Sat + +This field specifies the number of satellites in GANSS Reference Measurement Information element. + +###### SV\_ID + +This field specifies the SV for which the GANSS Reference Measurement Assistance is given. The interpretation of SV ID is defined in Table A.10.14. + +Range: 0 – 63 + +###### Doppler (0th order term) + +This field contains the Doppler (0th order term) value. A positive value in Doppler defines the increase in satellite signal frequency due to velocity towards the MS. A negative value in Doppler defines the decrease in satellite signal frequency due to velocity away from the MS. + +Doppler is given in unit of m/s by multiplying the Doppler value in Hz by the *nominal* wavelength of the assisted signal. + +This field is mandatory. + +###### Doppler (1st order term) + +This field contains the Doppler (1st order term) value. A positive value defines the rate of increase in satellite signal frequency due to acceleration towards the MS. A negative value defines the rate of decrease in satellite signal frequency due to acceleration away from the MS. + +Doppler (1st order term) is given in unit of m/s by multiplying the Doppler value in Hz by the *nominal* wavelength of the assisted signal. + +This field is optional. + +###### Doppler Uncertainty + +This field contains the Doppler uncertainty value. It is defined such that the Doppler experienced by a stationary MS is in the range "Doppler - Doppler Uncertainty" to "Doppler + Doppler Uncertainty". This field is optional. If Doppler Uncertainty (together with Doppler 1st order term) is omitted, the terminal shall interpret Doppler Uncertainty as greater than +/-40 m/s. If the Doppler Uncertainty Extension (Table A.55.25) field is present, the MS that supports the Doppler Uncertainty Extension shall ignore this field. + +Doppler Uncertainty is given in unit of m/s by multiplying the Doppler Uncertainty value in Hz by the *nominal* wavelength of the assisted signal. + +Permitted Values: 2,5 m/s, 5 m/s, 10 m/s, 20 m/s, 40 m/s as encoded by an integer n in the range 0-4 according to the formula in Table A.52. + +###### Code Phase + +This field together with the Code Phase\_1023 field contains code phase, in units of milliseconds, in the range from 0 to 1 millisecond scaled by the *nominal* chipping rate of the GNSS signal, where increasing values of the field signify increasing predicted signal code phases, as seen by a receiver at the Reference Location at the GANSS Reference Time. The Reference Location would typically be an apriori estimate of the MS location. This field is mandatory. + +Range: 0 - (1-2-10) ms + +NOTE: The value (1-2-10) ms is encoded using the Code Phase\_1023 field. + +###### Integer Code Phase + +This field contains integer code phase (expressed modulo 128 ms). The satellite integer milliseconds code phase currently being transmitted at the GANSS Reference Time, as seen by a receiver at the Reference Location is calculated as reference time (GANSS TOD or GPS TOW, expressed in milliseconds) minus (Integer\_Code\_Phase + (n×128 ms)), as shown in Figure A.4a/b, with n = ...-2,-1,0,1,2.... This field is mandatory. + +Range: 0-127 ms + +###### Code Phase Search Window + +This field contains the code phase search window. The code phase search window accounts for the uncertainty in the estimated MS location but not any uncertainty in GANSS Reference Time. It is defined such that the expected code phase is in the range "Code Phase - Code Phase Search Window" to "Code Phase + Code Phase Search Window" given in units of milliseconds. This field is mandatory. + +Range: 0-31 (i.e. 0,002 - 2,000 ms according to following table) + +**Table A.53: Code Phase Search Window Parameter Format** + +| CODE_PHASE_SEARCH_WINDOW | Code Phase Search Window [ms] | +|---------------------------------|--------------------------------------| +| '00000' | No information | +| '00001' | 0,002 | +| '00010' | 0,004 | +| '00011' | 0,008 | +| '00100' | 0,012 | +| '00101' | 0,016 | +| '00110' | 0,024 | +| '00111' | 0,032 | +| '01000' | 0,048 | +| '01001' | 0,064 | +| '01010' | 0,096 | +| '01011' | 0,128 | +| '01100' | 0,164 | +| '01101' | 0,200 | +| '01110' | 0,250 | +| '01111' | 0,300 | +| '10000' | 0,360 | +| '10001' | 0,420 | +| '10010' | 0,480 | +| '10011' | 0,540 | +| '10100' | 0,600 | +| '10101' | 0,660 | +| '10110' | 0,720 | +| '10111' | 0,780 | +| '11000' | 0,850 | +| '11001' | 1,000 | +| '11010' | 1,150 | +| '11011' | 1,300 | +| '11100' | 1,450 | +| '11101' | 1,600 | +| '11110' | 1,800 | +| '11111' | 2,000 | + +###### **Azimuth** + +This field together with the Azimuth LSB included in GANSS Reference Measurement Extension in Table A.55.23 contains the azimuth angle. An angle of x degrees means the satellite azimuth a is in the range ( $x \leq a < x+0,703125$ ) degrees. This field is optional. + +Range: 0 - 359,296875 degrees. + +###### **Elevation** + +This field together with the Elevation LSB included in GANSS Reference Measurement Extension in Table A.55.23 contains the elevation angle. An angle of y degrees means the satellite elevation e is in the range ( $y \leq e < y+0,703125$ ) degrees except for $y = 89,296875$ where the range is extended to include 90 degrees. This field is optional. + +Range: 0 - 89,296875 degrees + +###### **Code Phase\_1023** + +This field if set to TRUE indicates that the code phase has the value $1023 \times 2^{-10} = (1-2^{-10})$ ms. This field may only be set to TRUE if the value provided in the Code Phase field is 1022. If this field is set to FALSE, the code phase is the value provided in the Code Phase field in the range from 0 to $(1 - 2 \times 2^{-10})$ ms. If this field is not present and the Code Phase field has the value 1022, the MS may assume that the code phase is between $(1 - 2 \times 2^{-10})$ and $(1 - 2^{-10})$ ms. + +###### **GANSS Almanac Model** + +These fields specify the coarse, long-term model of the satellite positions and clocks. These fields are given in Table A.54. The meaning of these parameters is defined in relevant ICDs of the particular GANSS and GNSS specific interpretations apply. For example, Modernized GPS and QZSS use the same model parameters but some parameters have a different interpretation [16]. + +GANSS Almanac Model is useful for receiver tasks that require coarse accuracy, such as determining satellite visibility. The model is valid for up to few weeks, typically. Since it is a long-term model, the field should be provided for all satellites in the GNSS constellation. If almanac is not provided for the full GNSS constellation, the SMLC shall set the Complete Almanac Provided field in Table A.55.24 to FALSE. + +**Table A.54: GANSS Almanac Model (per-satellite fields - (1) = Positive range only)** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-------------------------------------------------------------|--------|---------------------------------------------------------------------------|-----------------------|-------| +| The following fields occur once per message | | | | | +| Num_Sats_Total | 6 | 1 | --- | M | +| Week Number | 8 | 1 | weeks | M | +| T oa | 8 | 2 12 if GANSS-ID is not Galileo.
600 if GANSS-ID is Galileo | s | O | +| IOD a | 2 | --- | --- | O | +| One of the following models can be included: | | | | | +| Model-1: | | | | | +| This model occurs once per satellite (Num_Sats_Total times) | | | | | +| GANSS Almanac Model Using Keplerian Parameters | | | | | +| SV_ID | 6 | --- | --- | M | +| e | 11 | 2 -16 | dimensionless | M | +| δi | 11 | 2 -14 | semi-circles | M | +| OMEGADOT | 11 | 2 -33 | semi-circles/sec | M | +| SV Status INAV | 4 | --- | dimensionless | M | +| SV Status FNAV | 2 | --- | dimensionless | O | +| delta A 1/2 | 13 | 2 -9 | meters 1/2 | M | +| OMEGA 0 | 16 | 2 -15 | semi-circles | M | +| ω | 16 | 2 -15 | semi-circles | M | +| M 0 | 16 | 2 -15 | semi-circles | M | +| af 0 | 16 | 2 -19 | seconds | M | +| af 1 | 13 | 2 -38 | sec/sec | M | +| Model-2: | | | | | +| This model occurs once per satellite (Num_Sats_Total times) | | | | | +| GANSS Almanac Model Using NAV Keplerian Parameters | | | | | +| SV_ID | 6 | --- | --- | M | +| e | 16 | 2 -21 | dimensionless | M | +| δi | 16 | 2 -19 | semi-circles | M | +| OMEGADOT | 16 | 2 -38 | semi-circles/sec | M | +| SV Health | 8 | --- | Boolean | M | +| A 1/2 | 24 | 2 -11 | meters 1/2 | M | +| OMEGA 0 | 24 | 2 -23 | semi-circles | M | +| ω | 24 | 2 -23 | semi-circles | M | +| M 0 | 24 | 2 -23 | semi-circles | M | +| af 0 | 11 | 2 -20 | seconds | M | +| af 1 | 11 | 2 -38 | sec/sec | M | +| Model-3: | | | | | +| This model occurs once per satellite (Num_Sats_Total times) | | | | | +| GANSS Almanac Model Using Reduced Keplerian Parameters | | | | | +| SV_ID | 6 | --- | --- | M | +| δ A | 8 | 2 +9 | meters | M | +| Ω 0 | 7 | 2 -6 | semi-circles | M | +| Φ 0 | 7 | 2 -6 | semi-circles | M | +| L1 Health | 1 | --- | --- | M | +| L2 Health | 1 | --- | --- | M | +| L5 Health | 1 | --- | --- | M | + +| Model-4: | | | | | +|---------------------------------------------------------------------|----|-----------|-----------------------|---| +| This model occurs once per satellite ( Num_Sats_Total times) | | | | | +| GANSs Almanac Model Using Midi Keplerian Parameters | | | | | +| SV_ID | 6 | --- | --- | M | +| e | 11 | $2^{-16}$ | --- | M | +| $\delta_i$ | 11 | $2^{-14}$ | semi-circles | M | +| $\Omega\_dot$ | 11 | $2^{-33}$ | semi-circles/sec | M | +| sqrtA | 17 | $2^{-4}$ | meters 1/2 | M | +| $\Omega_0$ | 16 | $2^{-15}$ | semi-circles | M | +| $\omega$ | 16 | $2^{-15}$ | semi-circles | M | +| $M_0$ | 16 | $2^{-15}$ | semi-circles | M | +| $a_{to}$ | 11 | $2^{-20}$ | seconds | M | +| $a_{fi}$ | 10 | $2^{-37}$ | sec/sec | M | +| L1 Health | 1 | --- | --- | M | +| L2 Health | 1 | --- | --- | M | +| L5 Health | 1 | --- | --- | M | + +| Model-5: | | | | | +|---------------------------------------------------------------------|----|-----------|-----------------------------------|------------| +| This model occurs once per satellite ( Num_Sats_Total times) | | | | | +| GNSS Almanac Model Using GLONASS Keplerian Parameters | | | | | +| $N^A$ | 11 | 1 | days | M | +| $n^A$ | 5 | 1 | --- | M | +| $H_n^A$ | 5 | 1 | --- | M | +| $\lambda_n^A$ | 21 | $2^{-20}$ | semi-circles | M | +| $t_{un}^A$ | 21 | $2^{-5}$ | seconds | M | +| $\Delta I_n^A$ | 18 | $2^{-20}$ | semi-circles | M | +| $\Delta T_n^A$ | 22 | $2^{-9}$ | seconds/orbit period | M | +| $\Delta T\_DOT_n^A$ | 7 | $2^{-14}$ | seconds/orbit period 2 | M | +| $\epsilon_n^A$ | 15 | $2^{-20}$ | --- | M | +| $\omega_n^A$ | 16 | $2^{-15}$ | semi-circles | M | +| $\tau_n^A$ | 10 | $2^{-18}$ | seconds | M | +| $C_n^A$ | 1 | 1 | --- | M | +| $M_n^A$ | 2 | 1 | --- | O | +| Model-6: | | | | | +| This model occurs once per satellite ( Num_Sats_Total times) | | | | | +| GNSS Almanac Model Using SBAS ECEF Parameters | | | | | +| Data ID | 2 | 1 | -- | M | +| SV ID | 6 | -- | -- | M | +| Health | 8 | -- | -- | M | +| $X_G$ | 15 | 2600 | meters | M | +| $Y_G$ | 15 | 2600 | meters | M | +| $Z_G$ | 9 | 26000 | meters | M | +| $X_G$ Rate-of-Change | 3 | 10 | meters/sec | M | +| $Y_G$ Rate-of-Change | 3 | 10 | meters/sec | M | +| $Z_G$ Rate-of-Change | 4 | 40,96 | meters/sec | M | +| $t_0$ | 11 | 64 | seconds | M | +| Model-7: | | | | | +| This model occurs once per satellite ( Num_Sats_Total times) | | | | | +| GNSS Almanac Model Using BDS Keplerian Parameters | | | | | +| SV_ID | | -- | | M | +| $t_{oa}$ | 8 | $2^{12}$ | seconds | O(note 2) | +| $A^{1/2}$ | 24 | $2^{-11}$ | meters 1/2 | M | +| $e$ | 17 | $2^{-21}$ | -- | M | +| $\omega$ | 24 | $2^{-23}$ | semi-circles | M | +| $M_0$ | 24 | $2^{-23}$ | semi-circles | M | +| $\Omega_0$ | 24 | $2^{-23}$ | semi-circles | M | +| $\Omega\_dot$ | 17 | $2^{-38}$ | semi-circles/sec | M | +| $\delta_i$ | 16 | $2^{-19}$ | semi-circles | M | +| $a_0$ | 11 | $2^{-20}$ | seconds | M | +| $a_1$ | 11 | $2^{-38}$ | sec/sec | M | +| Hea | 9 | -- | -- | O (note 3) | + +NOTE 2: This field may be present if the toa is not the same for all SVs; otherwise it is not present and the toa is provided in GANSSAlmanacModel + +NOTE 3: This IE is mandatory present if the IE "SV ID" is between 0 and 29 and not needed otherwise. + +###### Num\_Sats\_Total + +This field specifies the total number of satellites in GNSS Almanac Model. + +Range: 1 - 36 + +###### Week Number + +This field specifies the Almanac reference week number in GNSS specific system time to which the Almanac Reference Time $T_{oa}$ is referenced, modulo 256 weeks. If $T_{oa}$ is not included in GNSS Almanac Model, the MS shall ignore the Week Number. + +Range: 0 - 255 + +NOTE: In case of Galileo, the almanac reference week number $WN_a$ natively contains only the 2 LSB's [11, section 5.1.10]. + +###### $T_{oa}$ + +This field specifies the Almanac Reference Time common to all satellites in GANSS Almanac Model Using Keplerian Parameters given in GNSS specific system time. + +Range: 0 - 255 + +In case of GNSS-ID does not indicate Galileo, the scale factor is $2^{12}$ seconds. In case of GNSS-ID does indicate Galileo, the scale factor is 600 seconds. + +NOTE: Range extension of $T_{oa}$ may be present in the GANSS Almanac Model Extension-R12 element (Table A.55.25), if GANSS-ID indicates Galileo. + +###### $IOD_a$ + +This field specifies the Issue-Of-Data common to all satellites in GANSS Almanac Model using Keplerian Parameters. + +Range: 0 - 3 + +NOTE: Range extension of $IOD_a$ may be present in the GANSS Almanac Model Extension-R12 element (Table A.55.25), if GANSS-ID indicates Galileo. + +###### SV\_ID + +This field identifies the satellite for which the GANSS Almanac Model is given. The interpretation of SV ID is defined in Table A.10.14. + +Range: 0 - 63 + +###### SV Status INAV + +This field contains the I/NAV health status bits [11, section 5.1.10]. + +###### SV Status FNAV + +This field contains the F/NAV health status bits [11, section 5.1.10]. If the MS is supporting multiple Galileo signals, the SMLC shall include this field. + +###### GANSS UTC Model + +The GANSS UTC Model field contains a set of parameters needed to relate GNSS system time to Universal Time Coordinate (UTC). All of the fields in the GANSS UTC Model are mandatory when the field is present. The UTC time standard, $UTC(k)$ , is GNSS specific. E.g., if GANSS ID indicates QZSS, GANSS UTC Model field contains a set of parameters needed to relate QZST to UTC(NICT). + +**Table A.55: GANSS UTC Model (Model-1)** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------|--------|--------------|---------|-------| +| $A_1$ | 24 | $2^{-50}$ | sec/sec | C | +| $A_0$ | 32 | $2^{-30}$ | seconds | C | +| $t_{ot}$ | 8 | $2^{12}$ | seconds | C | +| $WN_t$ | 8 | 1 | weeks | C | +| $\Delta t_{LS}$ | 8 | 1 | seconds | C | +| $WN_{LSF}$ | 8 | 1 | weeks | C | +| DN | 8 | 1 | days | C | +| $\Delta t_{LSF}$ | 8 | 1 | seconds | C | + +###### GANSS Ephemeris Extension + +The GANSS Ephemeris extension contains parameters designed to extend the time of applicability of the Ephemeris terms by the continuous addition of the delta ephemeris terms to the respective terms of the referenced ephemeris. + +This message can provide extension information for every satellite for many days into the future; doing so may create a large message, thus care must be taken to consider the transport bandwidth. The SMLC can limit the duration of the extension to decrease the message size. For example if the extension duration is limited to twelve hours the payload will be approximately 2,000 octets, for a typical 27 satellite constellation. + +**Table A.55.2: GANSS Ephemeris Extension** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|---------------------------|-----------------------------------|--------------|-------|-------| +| ganssEphemerisHeader | See Table A.55.3 | --- | | O | +| ganssReferenceSet | See Table A.55.5 | --- | | O | +| ganssEphemerisDeltaMatrix | List of GANSSEphemerisDeltaEpochs | | | O | + +**Table A.55.3: GANSS Ephemeris Header** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|----------------------------------------------|------------------|--------------|-------|-------| +| GANSS Ephemeris Extension (Once per message) | | | | | +| timeAtEstimation | See Table A.55.4 | --- | | M | +| validityPeriod | 3 | 1 | Hours | M | +| ephemerisExtensionDuration | 9 | 1 | Hours | M | + +###### Time at Estimation + +The Time at Estimation provides the GANSS time at which the ephemeris extensions were created. + +**Table A.55.4: Time at Estimation** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-------------------------|--------|--------------|---------|-------| +| GANSS Day of Estimation | 13 | 1 | Day | M | +| GANSS TOD of Estimation | 17 | 1 | Seconds | M | + +###### GANSS Day of Estimation + +This field specifies the sequential number of days (with day count starting at 0) from the origin of the GNSS system time indicated by GANSS\_TIME\_ID modulo 8192 days (about 22 years) of the time that the estimation was determined. The GNSS system time origin is defined in Table A.34 for each GANSS. + +Range: 0 - 8191 days + +###### GANSS TOD of Estimation + +Integer number of GANSS TOD seconds within the current day of the time that the estimation was determined. + +Range: 0 - 86399 s. + +###### Validity Period + +The validityPeriod indicates the validity period of the GANSS Reference Set. It also indicates the default validity period of each individual delta ephemeris packet in the case that the individual validityPeriod is not present in the GANSS Delta Epoch Header (see Table A.55.8). It is the length of time that the GANSS Reference Set is intended to last and, if applicable, it is the length of time that the ephemeris constructed by application of the delta is intended to last. + +Range: 1 – 8 hours. + +###### Ephemeris Extension Duration + +The Ephemeris Extension duration indicates the total block of time measured in units of hours that the extended ephemeris covers. + +Range: 1 - 512 Hours. + +The ganssEphemeris header is mandatory only once in the delivery of the GANSS Ephemeris Extension message + +###### GANSS Reference Set + +**Table A.55.5: GANSS Reference Set** + +| Parameter | Presence | Note | +|-----------------------|----------|------------------| +| GANSS Reference Orbit | M | See Table A.55.6 | + +###### **GANSS Reference Orbit** + +**Table A.55.6: GANSS Reference Orbit** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------------|------------------|--------------|-------|-------| +| svID | 6 | 1 | --- | M | +| ganssOrbitModel | See Table A.29.g | | -- | M | +| ganssClockModel | See Table A.49.1 | | -- | M | + +###### **SvID** + +The satellite vehicle ID identifying to which satellite the following orbital and clock model apply. The interpretation of SV ID is defined in Table A.10.14. + +###### **GANSS OrbitModel** + +This field is a structure that contains the Reference Nav Model (see Table A.29.g) satellite orbit information upon which all subsequent delta information will be applied to create the next ephemeris for use in navigation. + +###### **GANSS ClockModel** + +This field is a structure that contains the satellite clock model upon which all subsequent clock information will be applied to create the next clock model for use in navigation. + +###### **GANSA Ephemeris Delta Matrix** + +GANSS Ephemeris Delta Matrix is a list of GANSS Ephemeris Delta Epochs. Each epoch is indicated by a unique seqNum. Each epoch corresponds to a specific update interval and contains a delta epoch header and ephemeris delta elements for all PRNs for that epoch. + +###### **GANSS Ephemeris Delta Epoch** + +**Table A.55.7: GANSS Ephemeris Delta Epoch** + +| Parameter | Note | Incl. | +|-----------------------|----------------------------------------|-------| +| ganssDeltaEpochHeader | See Table A.55.8 | O | +| ganssDeltaElementList | List of GANSS Ephemeris Delta Elements | M | + +###### **GANSS Delta Epoch Header** + +**Table A.55.8: GANSS Delta Epoch Header** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|----------------------|-------------------|--------------|-------|-------| +| validityPeriod | 3 | 1 | Hours | O | +| ephemerisDeltaSizes | See Table A.55.9 | | | O | +| ephemerisDeltaScales | See Table A.55.10 | | | O | + +###### **Validity Period** + +The validityPeriod indicates the validity period of each individual delta ephemeris packet. It is the length of time that the ephemeris constructed by application of the delta is intended to last. If not present then the default validityPeriod in the GANSS Ephemeris Header IE applies (see Table A.55.3). + +Range: 1 – 8 hours. + +###### **Ephemeris Delta Sizes** + +This field is a structure that indicates the bit sizes for all the fields in the GANSS Ephemeris Delta structure + +**Table A.55.9: GANSS Ephemeris Delta Sizes** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------------|--------|--------------|-------|-------| +| bitSize_delta_ω | 5 | 1 | --- | M | +| bitSize_delta_Δn | 4 | 1 | --- | M | +| bitSize_delta_M0 | 5 | 1 | --- | M | +| bitSize_delta_OMEGAdot | 5 | 1 | --- | M | +| bitSize_delta_e | 5 | 1 | --- | M | +| bitSize_delta_ldot | 4 | 1 | --- | M | +| bitSize_delta_sqrtA | 5 | 1 | --- | M | +| bitSize_delta_i0 | 5 | 1 | --- | M | +| bitSize_delta_OMEGA0 | 5 | 1 | --- | M | +| bitSize_delta_Crs | 4 | 1 | --- | M | +| bitSize_delta_Cis | 4 | 1 | --- | M | +| bitSize_delta_Cus | 4 | 1 | --- | M | +| bitSize_delta_Crc | 4 | 1 | --- | M | +| bitSize_delta_Cic | 4 | 1 | --- | M | +| bitSize_delta_Cuc | 4 | 1 | --- | M | +| bitSize_delta_tgd1 | 4 | 1 | --- | M | +| bitSize_delta_tgd2 | 4 | 1 | --- | M | + +###### Ephemeris Delta Scales + +This field is a structure that indicates the scale factor modifiers for all the fields in the GANSS Ephemeris Delta structure. + +**Table A.55.10: GANSS Ephemeris Delta Scales** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|----------------------|--------|--------------|-------|-------| +| scale_delta_ω | 5 | 1 | --- | M | +| scale_delta_Δn | 5 | 1 | --- | M | +| scale_delta_M0 | 5 | 1 | --- | M | +| scale_delta_OMEGAdot | 5 | 1 | --- | M | +| scale_delta_e | 5 | 1 | --- | M | +| scale_delta_ldot | 5 | 1 | --- | M | +| scale_delta_sqrtA | 5 | 1 | --- | M | +| scale_delta_i0 | 5 | 1 | --- | M | +| scale_delta_OMEGA0 | 5 | 1 | --- | M | +| scale_delta_Crs | 5 | 1 | --- | M | +| scale_delta_Cis | 5 | 1 | --- | M | +| scale_delta_Cus | 5 | 1 | --- | M | +| scale_delta_Crc | 5 | 1 | --- | M | +| scale_delta_Cic | 5 | 1 | --- | M | +| scale_delta_Cuc | 5 | 1 | --- | M | +| scale_delta_tgd1 | 5 | 1 | --- | M | +| scale_delta_tgd2 | 5 | 1 | --- | M | + +###### GANSS Delta Element List + +GANSS Delta Element List is a list of GANSS Ephemeris Delta Elements + +###### Ephemeris Delta Element + +Each GANSS Ephemeris Delta element is uniquely identified by the pair (seqNum, sv\_ID) and it is defined as a structure as shown in table A.55.11. The MS should parse the octet string according to the fields specified in table A.55.4. Each element in table A.55.4 but for seqNum and sv\_ID should be treated as a signed integer. Each Ephemeris delta is transmitted as an octet string of up to 49 octets. The actual number of octets is determined by the size of the bit fields in the GPS\_Ephemeris\_Delta\_Sizes table (table A.55.9). Each set of up to 49 octets represents a single extension for a single satellite vehicle. Each set encodes the satellite vehicle ID and the sequence number. The sequence number specifies the order in which the individual ephemeris extension elements are assembled as time marches forward to create the next ephemeris. The sequence number is the same for all satellite vehicle IDs for a particular update period. + +**Table A.55.11: GANSS Ephemeris Delta Element** + +| Parameter | # Bits | Default # Bits | Scale Factor | Default Scale | Units | Incl. | +|---------------|-----------|----------------|--------------------------------------------------------|---------------|-----------------------|-------| +| sequenceNum | 7 | | 1 | 1 | --- | M | +| svID | 6 | | 1 | 1 | --- | M | +| delta_omega | 1..32 (1) | 21 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_Delta_n | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-43} \dots 2^{15} \cdot 2^{-43} (2)$ | $2^{-43}$ | semi-circles/sec | M | +| delta_M0 | 1..32 (1) | 21 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_OMEAdot | 1..24 (1) | 13 | $2^{-16} \cdot 2^{-43} \dots 2^{15} \cdot 2^{-43} (2)$ | $2^{-43}$ | semi-circles/sec | M | +| delta_e | 1..32 (1) | 18 | $2^{-16} \cdot 2^{-33} \dots 2^{15} \cdot 2^{-33} (2)$ | $2^{-33}$ | --- | M | +| delta_ldot | 1..14 (1) | 11 | $2^{-16} \cdot 2^{-43} \dots 2^{15} \cdot 2^{-43} (2)$ | $2^{-43}$ | semi-circles/sec | M | +| delta_sqrtA | 1..32 (1) | 14 | $2^{-16} \cdot 2^{-19} \dots 2^{15} \cdot 2^{-19} (2)$ | $2^{-19}$ | meters 1/2 | M | +| delta_i0 | 1..32 (1) | 14 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_OMEGA0 | 1..32 (1) | 14 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | semi-circles | M | +| delta_Crs | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-5} \dots 2^{15} \cdot 2^{-5} (2)$ | $2^{-5}$ | meters | M | +| delta_Cis | 1..16 (1) | 11 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_Cus | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_Crc | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-5} \dots 2^{15} \cdot 2^{-5} (2)$ | $2^{-5}$ | meters | M | +| delta_Cic | 1..16 (1) | 11 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_Cuc | 1..16 (1) | 12 | $2^{-16} \cdot 2^{-29} \dots 2^{15} \cdot 2^{-29} (2)$ | $2^{-29}$ | radians | M | +| delta_tgd1 | 1..16 (1) | 2 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | seconds | M | +| delta_tgd2 | 1..16 (1) | 2 | $2^{-16} \cdot 2^{-31} \dots 2^{15} \cdot 2^{-31} (2)$ | $2^{-31}$ | seconds | M | + +- (1) The number of bits of each signed integer field is variable and it is indicated once for all numEphemerisDeltas by the structure ephemerisDeltasSizes. When the ephemerisDeltasSizes field is not present, the values found in the columns "Default # Bits" shall be used. +- (2) The scale factor of each parameter is variable around the default scale factor. The variation for each field is indicated once for all numEphemerisDeltas by the structure ephemerisDeltasScales. For example, if the scale factor modifier for delta\_omega has a value of 4, the scale factor for delta\_omega is $2^4 \cdot 2^{-31}$ . When the ephemerisDeltasScales is not used, the values found in the column "Default Scale" shall be used. + +###### sequenceNum + +This field indicates the order of the Ephemeris delta terms. The ephemeris constructed for use in satellite positioning is built by adding the delta terms to the referenced GANSS\_Navigation Model in the order dictated by this sequence number. The sequence number shall remain the same for each svID in a group of Ephemeris Deltas corresponding to a particular update epoch. + +###### svID + +This field identifies the satellite ID within a particular sequenceNum. + +These fields, with the exception of sequenceNum and svID, specify the deltas to be added to the existing Ephemeris to create a new Ephemeris suite that is extended from its predecessor by the time provided in the "validityPeriod" parameter. To compute the time of ephemeris for the newly constructed ephemeris, validityPeriod is added to the preceding toe. The ephemeris time of clock (toc) is set equal to the toe. + +For each of the other ephemeris terms the corresponding delta ephemeris term is added in order to create the updated ephemeris. The terms delta\_M0, delta\_i0, and delta\_OMEGA0 of the delta ephemeris must be extrapolated prior to the addition of the delta terms as follows: + +Where $\mu$ is the WGS 84 value of the earth's gravitational constant for GANSS user, and $A_{(i)}$ is the semi-major axis associated with this satellite's update. The extrapolation of delta\_M0, uses the prior set's sqrtA term to compute $A_{(i)}$ . + +$$\text{OMEGA0}_{(i+1)} = \text{OMEGA0}_{(i)} + \text{deltaOMEGA0}_{(i)} + \text{OMEGAAdot}_{(i)} \cdot dt$$ + +$$i0_{(i+1)} = i0_{(i)} + \text{delta\_i0}_{(i)} + \text{Idot}_{(i)} \cdot dt$$ + +Where $dt$ is equal to $validityPeriod*3600$ . The terms $af0$ , and $af1$ from the GANSS clock model must be extrapolated as follows: + +$$af0_{(i+1)} = af0_{(i)} + af1_{(i)} * dt + af2_{(i)} * dt^2$$ + +$$af1_{(i+1)} = af1_{(i)} + 2 * af2_{(i)} * dt$$ + +$$af2_{(i+1)} = af2_{(i)}$$ + +Where $af0$ , $af1$ , and $af2$ are the clock model terms as shown in table A.49.1. + +The following demonstrates the application of the ephemeris extension technique. Assume the $validityPeriod = 5$ , representing: $(5+1)hours = 6$ hours, and the GANSS Navigation model for a particular satellite, identified by the reference IOD has a $toe = 0$ seconds. + +The $toe$ for sequenceNumber 1 is computed by adding the $validityPeriod$ to the initial $toe$ of 0 as $0 + 6\ hours = 0 + 21600\ seconds$ . The new ephemeris is constructed by adding the delta ephemeris terms from set 1 to the reference ephemeris creating the new ephemeris, which will be used for the next six hours. For the five terms listed above ( $delta\_M0$ , $delta\_i0$ , $delta\_OMEGA0$ , $af0$ , and $af1$ ) the extrapolation described must occur prior to the addition of the delta term. Of course if one of these three delta ephemeris terms was provided in full via the exception table then the extrapolation is unnecessary and the exception term combined with the $delta\_ephemeris$ term is used directly. + +The next ephemeris computation will occur by adding the $validityPeriod$ to the current $toe$ of 21600 as: $21600 + 6\ hours = 21600 + 21600 = 43200$ . The ephemeris delta terms from set two are added to the ephemeris resulting from the prior addition to create the next ephemeris. This is done for each satellite vehicle ID listed in the provided satellite list indicated in the $ganssSatRef$ field. + +###### GANSS Ephemeris Extension check + +The GANSS Ephemeris Extension check provides information about non foreseen events that occurred during the period starting at the $ganssBeginTime$ to the current time. An event is signified through a bit string . Each bits refers to one PRN. If a bit is set to one, this means that the ephemeris extension is no longer valid for this specific PRN. In order to indicate planned future manuevers an end time is provided. The SMLC can indicate that a future event is planned between the current time and the end time of this ephemeris extension. + +**Table A.55.12: Ephemeris Extension check** + +| Parameter | Presence | Note | +|----------------------|----------|-------------------| +| $ganssBeginTime$ | M | See Table A.55.13 | +| $ganssEndTime$ | M | See Table A.55.14 | +| $ganssSatEventsInfo$ | M | See Table A.55.15 | + +###### GANSS Begin Time + +The GANSS begin time corresponds to the GANSS Day and GANSS Seconds of Estimation of the ephemeris extensions block. + +**Table A.55.13: GANSS Begin Time** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------|--------|--------------|---------|-------| +| GANSS Day | 13 | 1 | Day | M | +| GANSS TOD | 17 | 1 | Seconds | M | + +###### GANSS End Time + +The GANSS end time represents the final time the Ephemeris extension is valid. + +**Table A.55.14: GANSS End Time** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------|--------|--------------|---------|-------| +| GANSS Day | 13 | 1 | Day | M | +| GANSS TOD | 17 | 1 | Seconds | M | + +###### GANSS Sat Event Information + +If a bit is clear in the eventOccured field it indicates that a satellite maneuver has not occurred since the ganssBeginTime nor is This IE is designed to indicate events that have or may occur between the ganssBeginTime and the ganssEndTime. + +**Table A.55.15: GANSS Sat Event Information** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------|--------|--------------|-------|-------| +| EventOccurred | 64 | - | - | M | +| FutureEventNoted | 64 | - | - | M | + +###### EventOccurred + +###### FutureEventNoted + +If a bit is set in the futureEventNoted field it indicates that a maneuver is planned during the time period between current time plus sixty minutes and ganssEndTime + +###### SBAS ID + +If GANSS ID indicates SBAS, this field defines the specific SBAS for which the GANSS specific assistance data are provided according to Table A.55.16. + +**Table A.55.16: SBAS ID** + +| SBAS | Value of SBAS ID | +|----------|------------------| +| WAAS | 0 | +| EGNOS | 1 | +| MSAS | 2 | +| GAGAN | 3 | +| Reserved | 4-7 | + +###### GANSS Additional UTC Model + +The GANSS Additional UTC Model field contains several sets of parameters needed to relate GNSS system time to Universal Time Coordinate (UTC), as defined in [12, 13, 14, 15, 16, 17]. Only one parameter set can be included in one GANSS Additional UTC Model and which set of parameters to include depends on the GANSS-ID and MS capabilities. + +The UTC time standard, UTC(k), is GNSS specific. E.g., if GANSS ID indicates QZSS, GANSS Additional UTC Model field contains a set of parameters needed to relate QZST to UTC(NICT). If GANSS ID indicates Modernized GPS, GANSS Additional UTC Model field contains a set of parameters needed to relate GPS system time to UTC(USNO). If GANSS ID indicates GLONASS, GANSS Additional UTC Model field contains a set of parameters needed to relate GLONASS system time to UTC(RU). If GANSS ID indicates SBAS, GANSS Additional UTC Model field contains a set of parameters needed to relate SBAS network time for the SBAS indicated by SBAS ID to the UTC standard defined by the UTC Standard ID. If GANSS ID indicates BDS, GANSS Additional UTC Model field contains a set of parameters needed to relate BDS system time to UTC (NTSC). + +Table A.55.17: GANSS Additional UTC Model + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|------------------------------------------------------------------------------------------|--------|--------------|----------------------|------------------| +| One of the following models can be included: | | | | | +| Model-2 (as defined in [12, 13, 14, 16]) | | | | | +| $A_{0-n}$ | 16 | $2^{-35}$ | seconds | C (1) | +| $A_{1-n}$ | 13 | $2^{-51}$ | sec/sec | C (1) | +| $A_{2-n}$ | 7 | $2^{-68}$ | sec/sec 2 | C (1) | +| $\Delta t_{LS}$ | 8 | 1 | seconds | C (1) | +| $t_{ot}$ | 16 | $2^4$ | seconds | C (1) | +| WN ot | 13 | 1 | weeks | C (1) | +| WN LSF | 8 | 1 | weeks | C (1) | +| DN | 4 | 1 | days | C (1) | +| $\Delta t_{LSF}$ | 8 | 1 | seconds | C (1) | +| Model-3 (as defined in [17]) | | | | | +| $N^A$ | 11 | 1 | days | C (1) | +| $\tau_c$ | 32 | $2^{-31}$ | seconds | C (1) | +| B1 | 11 | $2^{-10}$ | seconds | O (2) | +| B2 | 10 | $2^{-16}$ | sec/msd | O (2) | +| KP | 2 | 1 | --- | O | +| Model-4 (as defined in [15], Message Type 12) | | | | | +| $A_{1WNT}$ | 24 | $2^{-50}$ | sec/sec | C (1) | +| $A_{0WNT}$ | 32 | $2^{-30}$ | seconds | C (1) | +| $t_{ot}$ | 8 | $2^{12}$ | seconds | C (1) | +| WN t | 8 | 1 | weeks | C (1) | +| $\Delta t_{LS}$ | 8 | 1 | seconds | C (1) | +| WN LSF | 8 | 1 | weeks | C (1) | +| DN | 8 | 1 | days | C (1) | +| $\Delta t_{LSF}$ | 8 | 1 | seconds | C (1) | +| UTC
Standard
ID | 3 | 1 | --- | C (1) | +| Model-5 (as defined in [18]) | | | | | +| $A_{0UTC}$ | 32 | $2^{-30}$ | Seconds | C (1) | +| $A_{1UTC}$ | 24 | $2^{-50}$ | sec/sec | C (1) | +| $\Delta t_{LS}$ | 8 | 1 | Seconds | C (1) | +| WN LSF | 8 | 1 | Weeks | C (1) | +| DN | 8 | 1 | Days | C (1) | +| $\Delta t_{LSF}$ | 8 | 1 | Seconds | C (1) | +| Note 1: All of these fields shall be present together, or none of them shall be present. | | | | | +| Note 2: If the optional elements are included, both elements shall be included. | | | | | + +###### UTC Standard ID + +If GANSS ID indicates SBAS, this field indicates the UTC standard used for the SBAS network time indicated by SBAS ID to UTC relation as defined in Table A.55.18 ([15], Message Type 12). + +Table A.55.18: UTC Standard ID + +| UTC Standard | Value of UTC Standard ID | +|-------------------------------------------------------------------------------|--------------------------| +| UTC as operated by the Communications Research Laboratory (CRL), Tokyo, Japan | 0 | +| UTC as operated by the National Institute of Standards and Technology (NIST) | 1 | +| UTC as operated by the U. S. Naval Observatory (USNO) | 2 | +| UTC as operated by the International Bureau of Weights and Measures (BIPM) | 3 | +| Reserved for future definition | 4-7 | + +###### GANSS Auxiliary Information + +This field contains additional information dependent on the GANSS ID and is shown in Table A.55.19. If GANSS Auxiliary Information is provided together with other satellite dependent GANSS assistance data (i.e., any of DGANSS Corrections, GANSS Navigation Model, GANSS Data Bit Assistance, or GANSS Reference Measurement Information IEs) and RRLP pseudo-segmentation is used, the GANSS Auxiliary Information should be provided for the same satellites and in the same RRLP segment as the other satellite dependent GANSS assistance data. + +**Table A.55.19: GANSS Auxiliary Information Parameter Format** + +| Parameter | Range | Bits | Resolution | Incl. | +|---------------------------------------------------------------------------------------------------------------------------|------------|------|------------|-------| +| One of the following group of elements can be included, dependent on the GANSS ID | | | | | +| The following fields may only be present if GANSS ID indicates Modernized GPS and occur once per satellite (N_SAT times): | | | | | +| SV ID | 0-63 | 6 | --- | M | +| Signals Available | Table A.59 | 8 | --- | M | +| The following fields may only be present if GANSS ID indicates GLONASS and occur once per satellite (N_SAT times): | | | | | +| SV ID | 0-63 | 6 | --- | M | +| Signals Available | Table A.59 | 8 | --- | M | +| Channel number | -7 – 13 | 5 | --- | M | + +###### SV\_ID + +This field specifies the SV for which the GANSS Auxiliary Information is given. The interpretation of SV ID is defined in Table A.10.14. + +Range: 0 – 63 + +###### Signals Available + +This field indicates the ranging signals supported by the satellite indicated by SV ID. This field is given as a bit string as shown in Table A.59 for a particular GANSS. If a bit is set to '1' it indicates that the satellite identified by SV ID transmits ranging signals according to the signal correspondence in Table A.59. If a bit is set to '0' it indicates that the corresponding signal is not supported on the satellite identified by SV ID. + +###### Channel number + +This field indicates the GLONASS carrier frequency number of the satellite identified by SV ID, as defined in [17]. + +###### DGANSS Corrections Validity Period + +This element is an extension to the DGANSS Corrections IE and provides the validity period of the differential corrections for each satellite and signal included in the DGANSS Corrections IE (see Table A.43). This element may only be included if the DGANSS Corrections IE is included in the GANSS Generic Assistance Data element. + +**Table A.55.20: DGANSS Corrections Validity Period** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|--------------------------------------------------------------------------|--------|--------------|-------|-------|-------| +| N_SGN_TYPE | 2 | 1 | 1-3 | --- | M | +| The following fields occur once per GANSS signal type (N_SGN_TYPE times) | | | | | | +| GANSS_Signal_ID | 3 | --- | --- | --- | M | +| N_SAT | 4 | 1 | 1-16 | --- | M | +| The following fields occur once per satellite (N_SAT times) | | | | | | +| SV_ID | 6 | --- | 0-63 | -- | M | +| UDRE Growth Rate | 3 | --- | 0-7 | --- | M | +| Time of Validity for UDRE Growth Rate | 3 | --- | 0-7 | --- | M | + +###### N\_SGN\_TYPE + +This field indicates the number of GNSS signal types included in DGANSS Corrections Validity Period IE. This field shall be set to the same value as the N\_SGN\_TYPE parameter in the DGANSS Corrections element in Table A.43. + +###### GANSS\_Signal\_ID + +DGANSS corrections validity period are provided per GNSS signal type identified by GANSS\_Signal\_ID. The supported signals are listed in Table A.59. This field shall be set to the same value as the GANSS\_Signal\_ID parameter in the DGANSS Corrections element in Table A.43. + +###### N\_SAT + +This field indicates the number of satellites for which differential corrections validity period is available. This field shall be set to the same value as the N\_SAT parameter in the DGANSS Corrections element in Table A.43. + +###### SV\_ID + +This field identifies the satellite for which the corrections validity period is applicable. The interpretation of SV ID is defined in Table A.10.14. The UDRE Growth Rate and Time of Validity for UDRE Growth Rate IEs shall be included for the same SV\_IDs as the differential corrections in Table A.43 are provided. + +###### UDRE Growth Rate + +This field provides an estimate of the growth rate of uncertainty ( $1-\sigma$ ) in the corrections for the particular satellite identified by SV\_ID. The estimated UDRE at time value specified in the "Time of Validity for UDRE Growth Rate" $t_i$ is calculated as follows: + +$$UDRE(t_0+t_i) = UDRE(t_0) \times UDRE \text{ Growth Rate}$$ + +where $t_0$ is the DGANSS Reference Time for which the corrections in Table A.43 are valid, $t_i$ is the "Time of Validity for UDRE Growth Rate" field as shown in Table A.55.21, $UDRE(t_0)$ is the User Differential Range Error field as provided in Table A.43, and "UDRE Growth Rate" field is the factor as shown in Table A.55.21. + +**Table A.55.21: Values of UDRE Growth Rate IE** + +| Value | Indication | +|-------|------------| +| 000 | 1,5 | +| 001 | 2 | +| 010 | 4 | +| 011 | 6 | +| 100 | 8 | +| 101 | 10 | +| 110 | 12 | +| 111 | 16 | + +###### Time of Validity for UDRE Growth Rate + +This field specifies the time when the "UDRE Growth Rate" field applies. The meaning of the values for this field is described in Table A.55.21a. + +**Table A.55.21a: Time of Validity for UDRE Growth Rate IE** + +| Value | Indication
[seconds] | +|-------|-------------------------| +| 000 | 20 | +| 001 | 40 | +| 010 | 80 | +| 011 | 160 | +| 100 | 320 | +| 101 | 640 | +| 110 | 1280 | +| 111 | 2560 | + +###### GANSS Time Model Extension + +This element is an extension to the GANSS Time Model IE and is shown in Table A.55.22. If GANSS Time Model is provided by the SMLC, the GANSS Time Model Extension shall also be provided. + +NOTE: For reasons of backward compatibility, this IE is not defined for a Release 9 or earlier SMLC and would be ignored, when received, by a Release 9 or earlier MS. This means that when the element is expected but is not received, the SMLC is Release 9 or earlier. + +**Table A.55.22: GANSS Time Model Extension** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|------------|--------|--------------|------------|---------|-------| +| GNSS_TO_ID | 3 | --- | --- | --- | M | +| Delta T | 8 | 1 | -128 - 127 | seconds | M | + +###### **GNSS\_TO\_ID** + +This field is the same as defined in Table A.41 and specifies GNSS for which the GANSS Time Model Extension is provided. + +###### **Delta T** + +This field specifies the integer seconds of the GNSS-GNSS Time Offset provided in the GANSS Time Model in Table A.41. + +###### **GANSS Reference Measurement Extension** + +This element is an extension to the GANSS Reference Measurement Information IE and is shown in Table A.55.23. If GANSS Reference Measurement Information is provided by the SMLC, the GANSS Reference Measurement Extension shall also be provided. + +NOTE: For reasons of backward compatibility, this IE is not defined for a Release 9 or earlier SMLC and would be ignored, when received, by a Release 9 or earlier MS. This means that when the element is expected but is not received, the SMLC is Release 9 or earlier. + +**Table A.55.23: GANSS Reference Measurement Extension** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|---------------------------------------------------------------|--------|--------------|-------------|---------|-------| +| Num_Sat | 4 | 1 | 0-15 | --- | M | +| The following fields occur once per satellite (Num_Sat times) | | | | | | +| SV_ID | 6 | --- | 0-63 | -- | M | +| Azimuth LSB | 4 | 0,703125 | 0-10,546875 | degrees | M | +| Elevation LSB | 4 | 0,703125 | 0-10,546875 | degrees | M | + +###### **Num\_Sat** + +This field indicates the number of satellites for which GANSS Reference Measurement is provided. This field shall be set to the same value as the Num\_Sat parameter in the GANSS Reference Measurement Information element in Table A.52. + +###### **SV\_ID** + +This field identifies the satellite for which the GANSS Reference Measurement is provided. This field shall be set to the same value as the SV\_ID field in Table A.52. + +###### **Azimuth LSB** + +This field specifies the 4 least significant bits of the satellite azimuth angle. The 5 most significant bits are provided in the Azimuth field in Table A.52. The full satellite azimuth is constructed as $\text{"Azimuth"} \times 11,25 + \text{"Azimuth LSB"} \times 0,703125$ degrees. + +###### **Elevation LSB** + +This field specifies the 4 least significant bits of the satellite elevation angle. The 5 most significant bits are provided in the Elevation field in Table A.52. The full satellite elevation is constructed as $\text{"Elevation"} \times 11,25 + \text{"Elevation LSB"} \times 0,703125$ degrees. + +###### **GANSS Almanac Model Extension** + +This element is an extension to the GANSS Almanac Model IE and is shown in Table A.55.24. If GANSS Almanac Model is provided by the SMLC, the GANSS Almanac Model Extension shall also be provided. + +NOTE: For reasons of backward compatibility, this IE is not defined for a Release 9 or earlier SMLC and would be ignored, when received, by a Release 9 or earlier MS. This means that when the element is expected but is not received, the SMLC is Release 9 or earlier. + +**Table A.55.24: GANSS Almanac Model Extension** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|---------------------------|--------|--------------|-------|---------|-------| +| Complete Almanac Provided | 1 | --- | --- | Boolean | M | + +###### Complete Almanac Provided + +This field indicates whether the SMLC provided Almanac for the full GANSS constellation or not. TRUE means complete GANSS almanac is provided. + +###### GANSS Almanac Model Extension-R12 + +This element is an extension to the GANSS Almanac Model IE and is shown in Table A.55.25. It is used only if GANSS-ID is Galileo in this version of protocol. + +**Table A.55.25: GANSS Almanac Model Extension-R12** + +| Parameter | # Bits | Scale Factor | Units | Incl. | +|-----------------------|--------|--------------|-------|------------| +| T oa -Ext | 10 | 600 | s | O (note 1) | +| IOD a -Ext | 4 | -- | -- | O (note 2) | + +NOTE 1: If Toa in GANSS Almanac Model element (Table A.54) is present, this field shall not be present. +NOTE 2: If IODa in GANSS Almanac Model element (Table A.54) is present, this field shall not be present. + +###### Toa-Ext + +This field specifies the Almanac Reference Time common to all satellites in GANSS Almanac Model using Keplerian Parameters given in GNSS specific system time. + +Range: 256 - 1023 + +In case of GNSS-ID does indicate Galileo, the scale factor is 600 seconds. + +###### IODa-Ext + +This field specifies the Issue-Of-Data common to all satellites in GANSS Almanac Model using Keplerian Parameters. + +Range: 4 - 15 + +###### GANSS Reference Measurement Extension-R12 + +This element is an extension to the GANSS Reference Measurement Information IE and is shown in Table A.55.25.a. The SMLC should include this field only if supported by the MS. + +**Table A.55.25.a: GANSS Reference Measurement Extension-R12** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-----------------------------------------------------------------------------|--------|--------------|------------------------------------|---------|-------| +| GANSS_Signal_ID | 3 | --- | 0-7 | --- | M | +| Confidence | 7 | 1 | 0-100 | percent | O | +| Num_Sat | 4 | 1 | 0-15 | --- | O | +| The following fields, if included, occur once per satellite (Num_Sat times) | | | | | | +| SV_ID | 6 | --- | 0-63 | -- | M | +| Doppler Uncertainty Extension | 3 | --- | 60, 80, 100, 120, 'No Information' | m/s | M | + +##### **GANSS\_Signal\_ID** + +This field specifies the GNSS signal type. The supported signals are listed in Table A.59. + +###### **Confidence** + +This field specifies the confidence level of the reference location area or volume used to calculate the GANSS Reference Measurement parameters (search windows). A high percentage value (e.g., 98% or more) indicates to the MS that the provided search windows are reliable. The SMLC should include this field to indicate the confidence level of the provided information. + +Range: 0 – 100 + +###### **Num\_Sat** + +This field indicates the number of satellites for which GANSS Reference Measurement Extension-R12 is provided. + +###### **SV\_ID** + +This field identifies the satellite for which the GANSS Reference Measurement Extension-R12 is provided. + +###### **Doppler Uncertainty Extension** + +If this field is present, the MS that supports this field shall ignore the Doppler Uncertainty (Table A.52) field. This field specifies additional Doppler uncertainty values. It is defined such that the Doppler experienced by a stationary MS is in the range [Doppler-Doppler Uncertainty Extension] to [Doppler+Doppler Uncertainty Extension]. Doppler Uncertainty Extension is given in unit of m/s by multiplying the Doppler Uncertainty Extension value in Hz by the nominal wavelength of the assisted signal. + +Enumerated values define 60 m/s, 80 m/s, 100 m/s, 120 m/s, and "No Information". + +##### **DBDS Corrections** + +These fields specify the DBDS corrections to be used by the MS. + +**Table A.55.25.b: DBDS Corrections** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|--------------------------------------------------------------------------|--------|--------------|----------------|---------|-------| +| The following fields occur once per message | | | | | | +| N_SGN_TYPE | 2 | 1 | 1 - 3 | --- | M | +| DBDS Reference Time | 12 | 1 | 0 - 3599 | seconds | M | +| The following fields occur once per GANSS signal type (N_SGN_TYPE times) | | | | | | +| N_SAT | 6 | 1 | 1 - 64 | --- | M | +| DBDS Signal ID | 3 | --- | --- | --- | M | +| The following fields occur once per satellite (N_SAT times) | | | | | | +| SV_ID | 6 | --- | 0 - 63 | --- | M | +| UDREI | 4 | --- | 0 - 15 | --- | M | +| RURAI | 4 | --- | 0 - 15 | --- | M | +| Delta T | 13 | 0.1 | -409.5 – 409.5 | meters | M | + +###### **DBDS Reference Time** + +This field indicates the baseline time for which the DBDS corrections are valid as modulo 3600 s. DBDS Reference Time is given in BDS system time. + +Range: 0 - 3599 s + +###### **DBDS Signal\_ID** + +DBDS corrections are provided per BDS signal type identified by BDS Signal\_ID. The supported signals are listed in Table A.59. + +###### **UDREI** + +UDRE is used to describe the error of equivalent clock correction in meters. It is indicated by user differential range error index (UDREI). It occupies 4 bits for each satellite within the range of 1~15 and the update rate is 3 seconds. The corresponding relationship between UDRE and UDREI is shown in A.55.26. + +**Table A.55.26: UDREI definitions** + +| UDREI | UDRE
(meters, 99.9%) | +|-------|-------------------------| +| 0 | 1 | +| 1 | 1.5 | +| 2 | 2 | +| 3 | 3 | +| 4 | 4 | +| 5 | 5 | +| 6 | 6 | +| 7 | 8 | +| 8 | 10 | +| 9 | 15 | +| 10 | 20 | +| 11 | 50 | +| 12 | 100 | +| 13 | 150 | +| 14 | Not monitored | +| 15 | Not available | + +###### RURAI + +Regional User Range Accuracy (RURA) is used to describe the satellite signal pseudo-range error in meters. The satellite signal integrity information is indicated with the Regional User Range Accuracy Index (RURAI). It occupies 4 bits for each satellite so the effective range of RURAI is 0 to 15. See Table A.55.27 for the corresponding relationship between RURAI and RURA. + +**Table A.55.27: RURAI definitions** + +| RURAI | RURA
(meters, 99.9%) | +|-------|-------------------------| +| 0 | 0.75 | +| 1 | 1 | +| 2 | 1.25 | +| 3 | 1.75 | +| 4 | 2.25 | +| 5 | 3 | +| 6 | 3.75 | +| 7 | 4.5 | +| 8 | 5.25 | +| 9 | 6 | +| 10 | 7.5 | +| 11 | 15 | +| 12 | 50 | +| 13 | 150 | +| 14 | 300 | +| 15 | > 300.0 | + +###### Delta\_T + +The BDS differential correction information is expressed in equivalent clock correction ( $\Delta t$ ). It occupies 13 bits for each satellite with the unit and scale factor of meter and 0.1 respectively and is expressed with two's complement. The MSB is for the sign bit (+ or -). + +###### BDS Grid Model + +The BDS Grid Model parameters are used to estimate the ionospheric distortions on pseudoranges as described in [18] on page 76. + +**Table A.55.28: BDS Grid Model** + +| Parameter | # Bits | Scale Factor | Range | Units | Incl. | +|-----------------------------------------------------------------------------------------------------------------------------|--------|--------------|------------------------|---------|-------| +| The following fields occur once per message | | | | | | +| BDS Reference Time | 12 | 1 | 0 - 3599 | seconds | M | +| N_IGP | 9 | 1 | 1 - 320 (1) | - | M | +| The following fields occur once per IGP (N_IGP times (1) ) | | | | | | +| IGP number | 9 | -- | 1...320 | --- | M | +| Vertical Delay | 9 | 0.125 | 0 - 63.625 | meters | M | +| GIVEI | 4 | -- | -- | -- | M | +| NOTE 1: Up to 16 instances are used in this version of the specification. The values 17 to 320 are reserved for future use. | | | | | | + +###### BDS Reference Time + +This field indicates the baseline time for which the BDS Grid Model are valid as modulo 3600 s. BDS Reference Time is given in BDS system time. + +Range: 0 - 3599 s + +###### IGP number + +This field indicates the ionospheric grid point (IGP) number as defined in [18]. + +**Vertical Delay** Vertical delay is used to indicate the vertical ionosphere delay on B1I signal at the $i^{\text{th}}$ grid point, expressed in scale factor of 0.125 and with unit of meters. The effective range of vertical delay is between 0 to 63.625 meters. + +###### GIVEI + +The grid ionosphere vertical error (GIVE) describes the delay correction accuracy at ionosphere grid points and is indicated with GIVEI. See Table A.55.29 for the relationship between GIVEI and GIVE. + +**Table A.55.29: GIVEI definitions** + +| GIVEI | GIVE
(meters, 99.9%) | +|-------|-------------------------| +| 0 | 0.3 | +| 1 | 0.6 | +| 2 | 0.9 | +| 3 | 1.2 | +| 4 | 1.5 | +| 5 | 1.8 | +| 6 | 2.1 | +| 7 | 2.4 | +| 8 | 2.7 | +| 9 | 3 | +| 10 | 3.6 | +| 11 | 4.5 | +| 12 | 6 | +| 13 | 9 | +| 14 | 15 | +| 15 | 45 | + +#### A.4.2.7 GANSS Carrier-Phase Measurement Request Element + +This element is optional and controls if the MS should return carrier-phase measurements in GANSS Measurement Information IE or not to the SMLC. The inclusion of this parameter implies use of measure Position Request. The description is found in sub-chapter 2.2.4d. + +#### A.4.2.8 GANSS TOD - GSM Time Association Request Element + +This element is optional and controls if the MS should return GANSS TOD - GSM Time Association Measurements or not to the SMLC. The inclusion of this parameter implies use of measure Position Request. The description is found in sub-chapter 2.2.4e. + +## A.5 Assistance Data Acknowledgement + +### A.5.1 General + +The MS sends the Assistance Data Acknowledgement component to the SMLC to indicate that it has received the whole Assistance Data component. + +## A.6 Protocol Error + +### A.6.1 General + +This component is used by the receiving entity (SMLC or MS) to indicate to the sending entity, that there is a problem that prevents the receiving entity to receive a complete and understandable component. + +This component has the following values: + +| | | +|------|---------------------------------------------------| +| '0': | Undefined; | +| '1': | Missing Component; | +| '2': | Incorrect Data; | +| '3': | Missing Information Element or Component Element; | +| '4': | Message Too Short; | +| '5': | Unknown Reference Number. | + +### A.6.2 Extended Reference IE + +This IE shall be included in any Protocol Error message if and only if an Extended Reference IE was received in the corresponding previous Measure Position Request or Assistance Data message. + +NOTE: For reasons of backward compatibility, a Release 4 or earlier MS will not include this IE. + +The Extended Reference IE contains the following elements. + +SMLC code: an integer in the range 0-63. The value returned by a target MS in a Protocol Error message shall equal the value received from the SMLC in the earlier Measure Position Request or Assistance Data message. + +Transaction ID: an integer in the range 0-262143 distinguishing different RRLP transactions in different MSs currently being served by the same SMLC. The value returned by a target MS in a Protocol Error message shall equal the value received from the SMLC in the earlier Measure Position Request or Assistance Data message. + +## A.7 Positioning Capability Request + +### A.7.1 General + +The SMLC sends the Positioning Capability Request component to the MS to request the MS positioning capabilities, types of assistance data supported and any assistance data that may be needed. It contains the following elements. + +**Table A.56: Positioning Capability Request component content** + +| Element | Type/Reference | Presence | +|----------------------------------|----------------------------------------------|----------| +| Extended Reference | Extended Reference 2.2.5 | M | +| GANSS Position Method Parameters | GANSS Position Method Parameters, Table A.58 | O | + +## A.8 Positioning Capability Response + +### A.8.1 General + +The Positioning Capability Response is a RRLP component from the MS to the network. It is the response to the Positioning Capability Request. It contains the following elements. + +**Table A.57: Positioning Capability Response component content** + +| Element | Type/Reference | Presence | +|---------------------------|---------------------------------|----------| +| Extended Reference | Extended Reference 2.2.5 | M | +| Positioning Capabilities | Positioning Capabilities 8.2.1 | M | +| Assistance Data Supported | Assistance Data Supported 8.2.2 | O | +| Assistance Data Needed | Assistance Data Needed 8.2.3 | O | + +### A.8.2 Elements + +#### A.8.2.1 Positioning Capabilities + +This element indicates the positioning methods and other positioning capabilities supported by the MS. The inclusion of this element is mandatory. + +The MS may indicate support for non-GNSS position methods and/or GNSS position methods. The MS indicates its support for non-GNSS position methods using a bit string with one bit representing each method, set to one if the method is supported and zero if it is not. The following Non-GNSS Position Methods can be identified: + +- MS Assisted E-OTD; +- MS Based E-OTD; +- MS Assisted GPS; +- MS Based GPS; +- Standalone GPS. + +The MS indicates its support for GNSS position methods by providing the parameters shown in Table A.58 for each GNSS system supported. + +**Table A.58: GNSS Position Method Support** + +| GNSS Position Method Parameters | +|---------------------------------| +| GNSS_ID | +| GNSS Position Method Types | +| GNSS Signals | +| SBAS ID | + +##### GNSS\_ID + +Range: 0 - 7 + +This field indicates the GNSS. The supported GNSS are defined in sub-clause A.4.2.6.2 (Table A.40). Absence of this field indicates Galileo. + +##### GNSS Position Method Types + +For each supported GNSS system, the MS shall and SMLC may indicate which method types are supported. This is represented using a bit string with one bit per method type where a one value indicates support and a zero value no support. The following GNSS Method Types can be identified: + +- MS Assisted; +- MS Based; + +- Standalone. + +##### GANSS Signals + +For each supported GANSS system, the MS shall and SMLC may indicate which signals are supported. This is represented using a bit string with one bit per signal where a one value indicates support and a zero value no support. The individual signals are denoted generically as signal1, signal2 etc. in the ASN.1 in clause 5.1. Table A.59 shows the signal correspondence for each defined GANSS system. Unfilled table entries indicate no assignment and shall either not be included or set to zero if included. + +The GANSS Signal Correspondence in Table A.59 is also used when a single signal is addressed (e.g., when reporting GANSS measurements or providing GANSS assistance data). In this case, an Integer value is used to indicate the signal, and the values 0 to 7 correspond to GANSS Signal 1 to 8, respectively. + +**Table A.59: GANSS Signal Correspondence** + +| GANSS System | Signal 1 | Signal 2 | Signal 3 | Signal 4 | Signal 5 | Signal 6 | Signal 7 | Signal 8 | +|----------------|----------|----------|----------|----------|----------|----------|----------|----------| +| Galileo | E1 | E5a | E5b | E6 | E5a+E5b | | | | +| Modernized GPS | L1C | L2C | L5 | | | | | | +| SBAS | L1 | | | | | | | | +| QZSS | QZS-L1 | QZS-L1C | QZS-L2C | QZS-L5 | | | | | +| GLONASS | G1 | G2 | G3 | | | | | | +| BDS | B1I | | | | | | | | + +##### SBAS\_ID + +If GANSS ID in Table A.58 indicates support for SBAS, this field shall be present to indicate support of specific SBAS using a bit map with one bit per SBAS where a one value indicates support and a zero value no support. + +**Table A.59.a: SBAS ID Correspondence** + +| Bit 0 | Bit 1 | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Bit 7 | +|-------|-------|-------|-------|----------|----------|----------|----------| +| WAAS | EGNOS | MSAS | GAGAN | reserved | reserved | reserved | reserved | + +The MS shall also indicate whether it supports multiple measurement sets for the MS Assisted position methods listed below. This is represented using a bit string with one bit representing each position method which is set to a one if multiple measurement sets are supported for that method and to a zero if not. The following MS Assisted Position Methods associated with Multiple Measurement Sets can be identified: + +- E-OTD; +- GPS; +- GANSS. + +#### A.8.2.2 Assistance Data Supported + +This element indicates the types of assistance data that the MS supports for GPS and GANSS and is shown in Table A.59.b. + +**Table A.59.b: Assistance Data Supported** + +| GANSS Position Method Parameters | +|------------------------------------------| +| GPS Assistance Data | +| GANSS Assistance Data | +| GANSS Additional Assistance Data Choices | + +##### GPS Assistance Data + +In the case of GPS, support for each of the following types of assistance data can be individually indicated using a bit string in which a one value indicates support and a zero no support. The following GPS Assistance Indications can be identified: + +- Almanac; +- UTC model; +- Ionospheric Model; +- Navigation Model; +- DGPS Corrections; +- Reference Location; +- Reference Time; +- Acquisition Assistance; +- Real Time Integrity; +- Ephemeris Extension; +- Ephemeris Extension Check; +- GPS Acquisition Assistance Extension-R12. +- DBDS Corrections +- BDS Grid Model + +##### GANSS Assistance Data + +In the case of GANSS, support for each of the following types of common assistance data is indicated using a bit string in which each bit represents one type of assistance data and is set to a one to indicate support and a zero to indicate no support. The following Common GANSS Assistance Indications can be identified: + +- GANSS Reference Time; +- GANSS Reference Location; +- GANSS Ionospheric Model; +- GANSS Additional Ionospheric Model; +- GANSS Earth Orientation Parameters. + +The MS indicates its support for assistance data specific to each GANSS system by providing the parameters shown in Table A.60 for each GANSS system supported. + +**Table A.60: GANSS Assistance Support** + +| GANSS Assistance Parameters | +|------------------------------------| +| GANSS_ID | +| GANSS Assistance | + +##### GANSS\_ID + +Range: 0 - 7 + +This field indicates the GANSS. The supported GANSS are defined in sub-clause A.4.2.6.2 (Table A.40). Absence of this field indicates Galileo. + +##### GANSS Assistance + +Supported GANSS Assistance data is indicated using a bit string in which each bit represents one type of assistance data and is set to a one to indicate support and a zero to indicate no support. The following types of Specific GANSS Assistance Indications can be identified. + +- GANSS Real Time Integrity; + +- GANSS Differential Corrections; +- GANSS Almanac; +- GANSS Reference Measurement Information; +- GANSS Navigation Model; +- GANSS Time Model GNSS-UTC; +- GANSS Time Model GNSS-GNSS; +- GANSS Data Bit Assistance; +- GANSS Ephemeris Extension; +- GANSS Ephemeris Extension Check; +- GANSS Additional UTC Model; +- GANSS Auxiliary Information; +- GANSS Reference Measurement Extension-R12. + +##### GANSS Additional Assistance Data Choices + +For GANSS Assistance Data elements for which multiple choices exist (GANSS Clock Model (Table A.49.1), GANSS Orbit Model (Table A.49.2), GANSS Almanac Model (Table A.54), and GANSS UTC Model/Additional UTC Model (Table A.55/A.55.17)) the MS and SMLC shall support the native formats choice as defined in the relevant ICDs for each GANSS signal. The MS can indicate which additional non-native choice(s) is(are) supported for a particular GANSS using a bit map with one bit per model where a one value indicates support and a zero value no support. Note that native support need not be indicated in this bit map. + +**Table A.61: GANSS Additional Assistance Data Choices** + +| Parameter | #Bits | Type/Reference | Prsence | +|--------------------------------------------------------------------|-------|------------------------|------------------| +| The following fields occur once per GANSS (Num_GANSS times) | | | | +| GANSS ID | 3 | Table A.40 | O (1) | +| GANSS Clock Model Choice | 8 | Bit String –Table A.62 | C (2) | +| GANSS Orbit Model Choice | 8 | Bit String –Table A.62 | C (2) | +| GANSS Almanac Model Choice | 8 | Bit String –Table A.62 | C (3) | +| GANSS UTC Model Choice | 8 | Bit String –Table A.62 | C (4) | + +Note 1: Absence of this field indicates Galileo. + +Note 2: These elements may only be present if GANSS Navigation Model support is indicated in GANSS Assistance. + +Note 3: This element may only be present if GANSS Almanac support is indicated in GANSS Assistance. + +Note 4: This element may only be present if GANSS Additional UTC Model support is indicated in GANSS Assistance. + +**Table A.62: Bit String of GANSS Additional Assistance Data Choices** + +| Model 1 | Model 2 | Model 3 | Model 4 | Model 5 | Model 6 | Model 7 | Model 8 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|---------|---------|---------|---------|---------| +| The individual Models 1-8 are identified in Tables A.49.1, A.49.2, A.54, and A.55/A.55.17.
Non defined Models in Assistance Data Choices shall have the value '0' at the corresponding bit position. | | | | | | | | + +#### A.8.2.3 Assistance Data Needed + +This element indicates the types of assistance data that the MS may need to obtain a location estimate or positioning measurements. The MS shall use this IE to indicate to the SMLC all the supported assistance data types for which the MS does not have current versions using the assistance data request IEs defined in 3GPP TS 49.031. The SMLC can then decide which subset of these assistance data types if any to download. The IE is encoded using the request for assistance data IEs defined for GPS and GANSS in 3GPP TS 49.031, with the following exceptions: + +Requested GPS Assistance Data (clause 10.10 in 3GPP TS 49.031): + +- If the MS supports Navigation Model (Bit D), Ephemeris Extension (Bit J), and Ephemeris Extension Check (Bit K), all three bits D, J, and K can be set to value 1 if the MS has no current versions of these assistance data types. If bit D is set to value 1, the coding of octets 5 to 8+2n shall be according to Figure 10.10.2 in clause 10.10 of 3GPP TS 49.031. + +Requested GANSS Assistance Data (clause 10.31 in 3GPP TS 49.031): + +- If the MS supports Navigation Model (Bit M), Ephemeris Extension (Bit N), and Ephemeris Extension Check (Bit R), all three bits M, N, and R can be set to value 1 if the MS has no current versions of these assistance data types. +- If the MS supports GANSS Ephemeris Extension (Bit N) and the MS has no current version of this assistance data type, bit N shall be set to value 1 but the corresponding extension octets in Figure 10.31.3d of 3GPP TS 49.031 shall be omitted. +- If the MS supports GANSS Data Bit Assistance (Bit Q) and the MS has no current version of this assistance data type, bit Q shall be set to value 1 but the corresponding extension octets in Figure 10.31.3c of 3GPP TS 49.031 shall be omitted. +- If the MS supports GANSS Ephemeris Extension Check (Bit R) and the MS has no current version of this assistance data type, bit R shall be set to value 1 but the corresponding extension octets in Figure 10.31.3e of 3GPP TS 49.031 shall be omitted. + +## A.9 Multilateration Timing Advance Request + +### A.9.1 General + +The Multilateration Timing Advance Request is a RRLP component sent from the SMLC to the MS. The SMLC uses the minimum guaranteed assessment error value of the BTS (i.e. the BTS Reception Accuracy Capability received from the BSC as part of assistance information and MS Sync Accuracy received from SGSN in the PERFORM-LOCATION-REQUEST PDU) when determining the Target-Number-of-Cells to use in the triggering RRLP message and the BTS Reception Accuracy Level reported by that BTS (when the Multilateration Timing Advance procedure is ongoing) to estimate the MS position and the corresponding positioning accuracy (see 3GPP TS 45.010 and 3GPP TS 43.059). This RRLP component contains the following elements. + +**Table A.9.1: Multilateration Timing Advance Request component content** + +| Element | Type/Reference | Presence | +|---------------------------------------|-----------------------------------------------|----------| +| Target-Number-of-Cells | Target-Number-of-Cells A.9.2.1 | M | +| Requested-MS-Synchronization-Accuracy | Requested-MS-Synchronization-Accuracy A.9.2.2 | M | +| MTA-Method | MTA-Method A.9.2.3 | M | +| Random-ID-Set | MTA-Method A.9.2.4 | M | +| MPM-Timer | MPM-Timer A.9.2.5 | M | +| Serving-Cell | Serving-Cell A.9.2.6 | M | +| Co-Sited-Cells | Co-Sited-Cells A.9.2.7 | O | +| Cell-Set N | Cell Set N A.9.2.8 | M | +| MTA-Security | MTA-Security A.9.2.9 | O | + +### A.9.2 Elements + +#### A.9.2.1 Target-Number-of-Cells Element + +This field is a 3 bit integer used to indicate the optimum number of cells a MS is to use when performing the radio access part of the MTA procedure. This field is mandatory, and has the following values: + +0 0 0 : 2 cells + +0 0 1 : 3 cells + +3GPP + +... + +1 1 1 : 9 cells + +#### A.9.2.2 Requested-MS-Synchronization-Accuracy Element + +This field is a 4 bit integer used to indicate the synchronization accuracy the MS should attempt to realize when performing the radio access part of the MTA procedure using the RLC Data Block method or the Extended Access Burst method and is coded as per the value part of the MS Synchronization Accuracy IE defined in 3GPP TS 49.031 [7]. The synchronization accuracy requested by this field shall be ignored when performing the radio access part of the MTA procedure using the Access Burst method. + +#### A.9.2.3 MTA-Method + +This field indicates the MTA method the MS is to use when performing the radio access part of the MTA procedure and allows for indicating the following methods. + +| | | +|------------------------|------------------------------------------------------------------------------------------------------------| +| RLC Data Block: | If this method is indicated then no additional information is included within the MTA-Method information. | +| Access Burst: | If this method is indicated then no additional information is included within the MTA-Method information. | +| Extended Access Burst: | If this method is indicated then the Short BSS ID field is included as part of the MTA-Method information. | + +These methods require that either PEO or EC-GSM-IoT operation is enabled in the MS. If EC-GSM-IoT operation is enabled but CC1 is not used on the uplink then the MS shall use the RLC Data Block method (if supported). If neither PEO or EC-GSM-IoT operation is enabled the MS shall not perform the commanded MTA procedure. + +##### Short-BSS-ID + +This parameter identifies the serving BSS within a cluster of BSS areas and is used for the Extended Access Burst method. The Short BSS ID together with a Random ID value identify the target MS for the Multilateration Timing Advance procedure in a unique way in the network. + +#### A.9.2.4 Random-ID + +This parameter is used by a MS when it performs the radio access part of the MTA procedure using the RLC Data Block or Extended Access Burst method. The Random ID value sent by a MS performing the radio access part of the MTA procedure is selected from a set of up to 9 Random ID values provided by the RRLP Multilateration Timing Advance Request message. Each Random ID value provided by the RRLP message can only be used in one cell used by a MS when performing the radio access part of the MTA procedure. After reception by the BSS it is sent to the SMLC along with corresponding MTA timing advance information using a SCCP connection that the Random ID is logically associated with (i.e. when the SMLC first allocates a set of Random ID values for inclusion in a RRLP message they will always be associated with a SCCP connection used by the SMLC for an ongoing MTA procedure). The reception of any one of the allocated Random ID values along with corresponding MTA timing advance information therefore allows the SMLC to validate the timing advance information. + +#### A.9.2.5 MPM-Timer + +This field is a 3 bit integer used to indicate the maximum amount of time the MS can use to perform the radio access part of the MTA procedure and is coded as per the MPM Timer field defined in 3GPP TS 49.031 [7]. + +#### A.9.2.6 Serving-Cell + +This field is set to '1' if the SMLC requests the MS to include the serving cell when performing the radio access part of the MTA procedure. + +#### A.9.2.7 Co-Sited-Cells + +This field identifies the set of cells that are co-sited with the serving cell and therefore shall not be used by the MS when performing the radio access part of the MTA procedure. + +#### A.9.2.8 Cell-Set N + +This field provides assistance information for one or more sets of cells wherein information for at least one cell is provided within each Cell Set for which assistance information is provided. When multiple cells are identified for a given Cell Set then each cell in the set is co-sited and the MS shall therefore use at most one cell from the set when performing the radio access part of the MTA procedure. If the ARFCN and BSIC of the serving cell is included for a cell within a Cell Set then the MS shall use that cell when performing the radio access part of the MTA procedure. + +##### Short-ID + +This parameter identifies the cell specific Short ID value to be sent from the MS to the BSS when the MS performs the radio access part of the MTA procedure in a cell using the Access Burst method. It is part of the MTA related measurement information passed from the BSS to the SMLC and is used by the SMLC to validate the corresponding MTA related measurement information it receives for that cell. + +##### ARFCN + +This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS 45.005. + +##### BSIC-Info + +This field identifies the 9 bit BSIC (see 3GPP TS 45.003 and 3GPP TS 45.008) associated with the indicated ARFCN. + +##### EC-Cell-Information + +When a cell supports EC-GSM-IoT the corresponding EC-RACH-Control-Parameters may be included as part of the assistance information. If excluded for that cell the MS shall default to using the EC-RACH-Control-Parameters provided for any other cell in that set. If EC-RACH-Control-Parameters are not provided for any cell in a set of cells that support EC-GSM-IoT then the MS shall read the EC-BCCH for the cell in that cell set that it chooses to use to perform the Multilateration Timing Advance procedure and thereby acquire the required EC-RACH-Control-Parameters information. + +##### PEO-Cell-Information + +When a cell supports PEO the corresponding RACH-Control-Parameters may be included as part of the assistance information. If excluded for that cell the MS shall default to using the RACH-Control-Parameters provided for any other cell in that set. If RACH-Control-Parameters are not provided for any cell in a set of cells that support PEO then the MS shall read the BCCH for the cell in that cell set that it chooses to use to perform the Multilateration Timing Advance procedure and thereby acquire the required RACH-Control-Parameters information. + +##### EC-BS-CC-CHANS + +This field is a 2 bit integer and indicates the number of extended coverage common control channels (EC-CCCHs) supported in the cell (see 3GPP TS 44.018). + +##### EC-RXLEV-ACCESS-MIN + +This field is a 6 bit integer and is coded as the binary representation of the minimum received signal level at the MS for which it is permitted to access the system when using the EC-RACH, see 3GPP TS 45.008. + +##### MS-TXPWR-MAX-CCH + +This field is coded as the binary representation of the "power control level" in 3GPP TS 45.005 corresponding to the maximum TX power level an MS may use when accessing the system on the (EC-)CCCH. This value shall be used by the Mobile Station according to 3GPP TS 45.008. + +##### LB-MS-TXPWR-MAX-CCH + +The LB\_MS\_TXPWR\_MAX\_CCH field is coded as the binary representation of the "power control level" in 3GPP TS 45.005 corresponding to the maximum TX power level an MS may use on all other than DCS 1800 and PCS 1900 frequency bands when accessing the system on the (EC-)CCCH. The use of this field is defined in 3GPP TS 45.008. + +##### CELL-SELECTION-RLA-MARGIN + +The CELL\_SELECTION\_RLA\_MARGIN field provides the MS with information whether RLA\_EC and RLA\_GC based measurements may be omitted or not. The use of this field is defined in 3GPP TS 45.008. + +##### DL-CC-Selection + +This field is a BOOLEAN and indicates the method for selecting the downlink coverage class to be used by the MS (see 3GPP TS 44.018). The use of this field is defined in 3GPP TS 45.008. + +##### **BT-Threshold-DL** + +This field is a 5 bit integer and indicates the signal level threshold below which blind physical layer transmissions are used on EC-CCCH. The use of this field is defined in 3GPP TS 45.008. + +##### **CC2-Range-DL** + +##### **CC3-Range-DL** + +These fields are 5 bit integers and are optionally sent by the network to indicate the signal level range of the indicated downlink coverage classes. The presence of one or both of these fields indicates network support of the associated downlink coverage class. The use of these fields is defined in 3GPP TS 45.008. + +##### **BT-Threshold-UL** + +This field is a 5 bit integer and indicates the signal level threshold below which blind physical layer transmissions are used on EC-RACH. The use of this field is defined in 3GPP TS 45.008. + +##### **CC2-Range-UL** + +##### **CC3-Range-UL** + +These fields are 5 bit integers and are optionally sent by the network to indicate the signal level range of the indicated uplink coverage classes. The presence of one or both of the above fields indicates network support of the associated uplink coverage class. The use of these fields is defined in 3GPP TS 45.008. + +##### **CC4-Range-UL** + +This field is optionally sent by the network to indicate the signal level range of uplink coverage class 4 and when included it implicitly indicates uplink class 5 is supported. The use of this field is defined in 3GPP TS 45.008. + +##### **BSPWR** + +This field indicates the BTS output power transmitted on FCCH and EC-SCH. The use of this field is defined in 3GPP TS 45.008. + +##### **DL-Signal-Strength-Step-Size** + +This field indicates the step-size in signal level above BT\_Threshold\_DL possible to report by the MS in the EC MULTILATERATION REQUEST message. The use of this field is defined in 3GPP TS 44.018. + +##### **EC-Reduced-PDCH-Allocation** + +This field indicates that the number of consecutive PDCHs the network allocates when assigning an EC TBF to a MS indicating Coverage Class CC2, CC3 or CC4 on the uplink or downlink during packet access. The use of this field is defined in 3GPP TS 44.018. + +##### **EC-Max-Retrans** + +This field is a 2 bit integer and indicates the maximum number of retransmissions on EC-RACH. It is encoded as the Max retrans field in the RACH Control Parameters IE defined in 3GPP TS 44.018. + +##### **Sm** + +This field is a 2 bit integer used by a MS to determine the number of multiframes it needs to read on the EC-AGCH in an attempt to find a response matching its last EC-RACH transmission. The use of this field is defined in 3GPP TS 44.018. + +##### **Tm** + +This field is a 2 bit integer used by a MS to determine the number of multiframes on the EC-RACH from which it randomly selects a transmission/retransmission opportunity. The use of this field is defined in 3GPP TS 44.018. + +##### **Access-Timeslots** + +This field is a BOOLEAN and indicates whether random access mapped over two timeslots shall be applied or not (see 3GPP TS 44.018). The use of this field is defined in 3GPP TS 44.018. + +##### **ALPHA** + +This field is an optional 4 bit integer and provides the binary representation of the parameter $\alpha$ for MS output power control in units of 0.1, see 3GPP TS 45.008. For encoding and description of the ALPHA field see the Global Power Control Parameters IE in 3GPP TS 44.060. + +##### **T3168** + +##### **T3192** + +##### **T3226** + +These fields are optional 3 bit integers. The use of these fields is defined in 3GPP TS 44.060. + +##### **T3248** + +This field is a 2 bit integer. The use of this field is defined in 3GPP TS 44.060. + +##### **MTA-BITMAP** + +This field contains a 4 bit bitmap indicating the Multilateration Timing Advance methods supported by a cell. See 3GPP TS 44.018 for a description of the Multilateration Timing Advance methods. Support for each of the methods listed below is provided using a BOOLEAN. + +- MTA-RLC-Data-Block-method +- MTA-Access-Burst-method +- MTA-Extended-Access-Burst-method +- MTA-spare + +##### **RXLEV-ACCESS-MIN** + +This field is a 6 bit integer and is coded as the binary representation of the minimum received signal level at the MS for which it is permitted to access the system when using the RACH, see 3GPP TS 45.008. + +##### **Max-Retrans** + +This field is a 2 bit integer and indicates the maximum number of retransmissions on RACH. The use of this field is defined in 3GPP TS 44.018. + +##### **Tx-integer** + +This field is a 4 bit integer and indicates the number of slots to spread the transmission on RACH. The use of this field is defined in 3GPP TS 44.018. + +#### **A.9.2.9 MTA-Security** + +This field indicates the method for verifying the integrity of the MTA Access procedure. + +MTA Access Security: If this method is indicated the MS generates MTA Signature at the end of MTA Access procedure based on the parameters associated with the successfully completed radio access parts of the MTA procedure using the Integrity protection keys negotiated with SGSN. + +BSS Duplication Detection Method: If this method is indicated, MS sends MTA sequence number in each of the MTA Access attempt including the last attempt. BSS verifies the integrity of the access procedure based on detection of duplicate sequence numbers received from the same MS identifier. + +## A.10 Multilateration OTD Request + +### A.10.1 General + +The Multilateration OTD (MOTD) request is an RRLP component from the network to the MS. This message is sent to MS to start MOTD measurements of neighbour base stations based on the given cell list + +**Table A.63: Multilateration OTD Request content** + +| Element | Type/Reference | Presence | +|--------------------------------------|---------------------------------------------|----------| +| Target Number of OTD measurements | Target Number of OTD Measurements 10.2.1 | M | +| Required DL Synchronisation Accuracy | Required DL Synchronisation Accuracy 10.2.2 | M | +| Serving Cell Set | Cell Set 10.2.3 | O | +| Neighbouring Cell Set | Cell Sets 10.2.4 | O | + +### A.10.2 Elements + +#### A.10.2.1 Target Number of OTD Measurements + +This element indicates the number of OTD measurements required to achieve the estimated positioning accuracy. The MS can complete the OTD measurement procedure once the target number of OTD measurements are completed or if no neighbour cells from further neighbour cell sites can be received and send the Multilateration OTD response message. + +#### A.10.2.2 Required DL Synchronisation Accuracy + +This element indicates the downlink synchronisation accuracy the MS should try to achieve with serving cell and neighbour cells. MS shall estimate the DL sync accuracy (i.e MS Sync Accuracy (see 3GPP TS 45.010)) on reception of every additional synchronisation burst reception. MS stops further reception and processing of synchronisation bursts if the estimated downlink sync accuracy is better than the required DL synchronisation accuracy or the maximum number of synchronisation iterations is already reached. + +#### A.10.2.3 Serving Cell Set + +This element contains the list of cells which are co-sited with the serving cell. MS shall avoid OTD measurements on the cells from this cell set. Each information element consists of ARFCN and BSIC of the cell as shown in Table A.64. + +**Table A.64: Cell Set** + +| MOTD Measurements Parameter | +|-----------------------------| +| ARFCN | +| BSIC | + +#### A.10.2.4 Neighbour Cell Sets + +This information element provides up to 8 cell sets where each neighbour cell set consists of information about co-sited cells of (at least) one neighbour cell site. The co-sited cell information is used by MS while measuring the OTD with the neighbour cells. The MS shall measure the OTD only with the strongest cell per neighbour cell set. + +Each Cell set information element indicates the ARFCN and BSIC of the cell (refer to Table A.64). + +## A.11 Multilateration OTD Response + +### A.11.1 General + +The Multilateration OTD (MOTD) Response is a RRLP component from the MS to network. This message is sent by the MS in response to the Multilateration OTD Request message containing the multilateration OTD measurement results. + +**Table A.65 Multilateration OTD Request content** + +| Element | Type/Reference | Presence | +|------------------------------------------------|----------------------------------------|----------| +| Serving Cell Downlink synchronisation Accuracy | Serving Cell DL Synch Accuracy. 11.2.1 | M | +| MOTD Measurement Results | MOTD Measurement Results 11.2.2 | O | +| MOTD Receive Level Measurements | MOTD Receive level Measurements 11.2.3 | O | + +### A.11.2 Elements + +#### A.11.2.1 Serving Cell Downlink Synchronisation Accuracy + +This element indicates the downlink synchronisation accuracy estimated for the serving cell at MS when it measures the OTD with neighbour cells for Multilateration OTD Response. + +#### A.11.2.2 MOTD Measurement Results + +This element consists of up to 7 OTD Measurement Information elements each containing the OTD measurement results along with the cell related information. OTD Measurement Information is shown in Table A.66. + +**Table A.66: OTD Measurement Information** + +| OTD Measurement Information | +|-----------------------------| +| ReportedCell | +| MS Synchronisation Accuracy | +| OTD Measurement Result | + +##### The MS Synchronisation Accuracy + +This parameter refers to the estimated synchronisation accuracy of the cell for which the OTD measurement with respect to serving cell is measured. MS estimates the synchronisation accuracy based on received downlink synchronisation bursts as specified in 3GPP TS 45.010. + +##### Reported Cell + +This field indicates whether the reported cell is cell index within the CellSets given on MOTD Measurement Request message or combination of BSIC and ARFCN. + +'0' = Reported Cell is given as the index to the cell in the serving Cell Set and Neighbour Cell Sets provided in the MOTD Measurement Request. + +'1' = Reported Cell is given as BSIC(9 bit) and ARFCN of the cell. + +##### CellIdx + +The index of the cell within the Serving Cell Set and Neighbour Cell Sets provided in the MOTD Measurement Request message. The index spans across all the cells of the Serving Cell Set and Neighbour Cell Sets. (For example Index 0 refers to the first cell in the ServingCellSet. If ServingCellSet contains 3 cells, then index 3 refers to the first cell of the first Neighbour Cell Set). + +##### OTD Measurement Result + +This parameter indicates the observed time difference between the TDMA frame timing of the measured cell and the serving cell. The time difference is reported modulo 125 normal symbol periods in terms of 1/8 normal symbol period granularity. (For example, if the TDMA frame timing of the neighbour cell is observed to be $\frac{1}{8}$ normal symbol period earlier than the TDMA frame timing of the serving cell, $8 \cdot ((1250 - \frac{1}{8}) \bmod 125) = 999$ is reported.) + +#### A.11.2.3 MOTD Receive Level Measurements + +This element is included in the MOTD Measurement Response when only one MOTD measurement result can be reported as part of the MOTD Measurement Response. This element consists of Receive Level Information parameters for all neighbour cells that the MS can receive, each consisting of receive level measurement and the cell identity related information. The MOTD Receive Level Measurement Information parameter is shown in Table A.67. + +**Table A.67: OTD Measurement Information** + +| OTD Measurement Information | +|-----------------------------| +| ReportedCell | +| Receive Level Measurement | + +##### Reported Cell + +3GPP + +Refer to subclause A.10.2.2 for definition and encoding of this parameter. + +##### **Receive Level Measurement** + +This parameter contains the RXLEV measurement of the reported cell. MS measures and reports this value as specified in 3GPP TS 45.008. + +# Annex B (informative): Change History + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | | | | | | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2017-06 | RP-76 | RP-170923 | 0227 | 8 | B | Introduction of Multilateration | 14.1.0 | +| 2017-06 | RP-76 | RP-170923 | 0228 | 3 | B | Introduction of Multilateration OTD | 14.1.0 | +| 2017-09 | RP-77 | RP-171593 | 0230 | - | F | Clarification to GANSS time model | 14.2.0 | +| 2017-12 | RP-78 | RP-172189 | 0231 | - | F | RRLP ASN.1 syntax corrections for Multilateration Positioning and GANSS | 14.3.0 | +| 2018-06 | RP-80 | RP-180822 | 0234 | - | B | Security Enhancement for MTA in network configuration without LLC security | 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/44_series/44035/5d76c2e9976aaf97001ee189908830fb_img.jpg b/marked/Rel-16/44_series/44035/5d76c2e9976aaf97001ee189908830fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51ab9238619eba19e60e70ab954323c758271278 --- /dev/null +++ b/marked/Rel-16/44_series/44035/5d76c2e9976aaf97001ee189908830fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb25f7d57f6b8cf8225cf3e001aba0c0d182e617f3665a7beec1a6ab9f4a8088 +size 62985 diff --git a/marked/Rel-16/44_series/44035/raw.md b/marked/Rel-16/44_series/44035/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bd2c3335894bd134db9eb53a387e2d249e64d477 --- /dev/null +++ b/marked/Rel-16/44_series/44035/raw.md @@ -0,0 +1,1126 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|----------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Broadcast Message Contents ..... | 6 | +| 4.1 E-OTD Assistance Data Broadcast Message ..... | 6 | +| 4.1.1 E-OTD Assistance Data Broadcast Message Content..... | 7 | +| 4.1.1.1 Message Structure Definition IE..... | 8 | +| 4.1.1.2 Reference Time IE..... | 11 | +| 4.1.1.3 Ciphering Serial Number IE ..... | 11 | +| 4.1.1.4 Time Slot Scheme IE ..... | 11 | +| 4.1.1.5 Neighbour Bitmap Definition IE ..... | 12 | +| 4.1.1.6 Sected Channels Definition IE ..... | 12 | +| 4.1.1.7 Sected Channels BTS ID Definition IE..... | 12 | +| 4.1.1.8 Sected BTS Sync/Async Definition IE..... | 13 | +| 4.1.1.9 Multiframe Offset Values IE ..... | 13 | +| 4.1.1.10 BCC Definition IE ..... | 13 | +| 4.1.1.11 RTD Drift Factor Values IE..... | 14 | +| 4.1.1.12 Channel RTD Values IE ..... | 15 | +| 4.1.1.13 Serving Cell Location IE ..... | 16 | +| 4.1.1.14 Relative Neighbour Location IE ..... | 16 | +| 4.2 GPS Assistance Data Broadcast Message..... | 18 | +| 4.2.1 GPS Assistance Data Content ..... | 18 | +| 4.2.1.1 DGPS Correction Data..... | 19 | +| 4.2.1.1.1 GSM Time Present IE ..... | 20 | +| 4.2.1.1.2 BTS Clock Drift Present IE..... | 20 | +| 4.2.1.1.3 BTS Clock Drift IE ..... | 20 | +| 4.2.1.1.4 Reference Location IE..... | 20 | +| 4.2.1.1.5 Reference Time IE ..... | 20 | +| 4.2.1.1.6 Status/Health IE..... | 21 | +| 4.2.1.1.7 N_SAT IE..... | 21 | +| 4.2.1.1.8 DGPS Corrections IE ..... | 21 | +| 4.2.1.2 Ephemeris and Clock Correction Data ..... | 22 | +| 4.2.1.3 Almanac and Other Data..... | 24 | +| Annex A (informative): Overview of Broadcast Assistance for E-OTD and GPS ..... | 26 | +| A.1 General ..... | 26 | +| A.2 E-OTD Assistance Broadcast..... | 26 | +| A.3 GPS Assistance Broadcast ..... | 27 | +| A.4 Impact on Other Services ..... | 28 | +| Annex B (informative): Example of E-OTD Assistance Data Broadcast Message ..... | 29 | +| Annex C (informative): Example of GPS Assistance Data Broadcast Message..... | 33 | +| Annex D (informative): Change History..... | 34 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains the content of messages necessary for support of MS Based location service operation on the mobile radio interface layer 3. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] Void. +- [3] Void. +- [4] Void. +- [5] Void" +- [6] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [7] Void. +- [8] Void. +- [9] Void. +- [10] Void. +- [11] Void. +- [12] Void. +- [13] Void. +- [14] Void. +- [15] RTCM-SC104: "RTCM Recommended Standards for Differential GNSS Service (v.2.2)". +- [16] ICD-GPS-200: "Navstar GPS Space Segment / Navigation User Interfaces". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**E-OTD Assistance Data Message:** contains the RTD and BTS coordinates of the neighbours that should be used in E-OTD measurements. This E-OTD Assistance Data is broadcasted using CBCH channel using SMSCB DRX service. The reception of this broadcast message enables MS to calculate its own location. + +**GPS Assistance Data Message:** contains GPS differential corrections. The reception of this broadcast message enables MS to have calculate more accurate location estimate. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# 4 Broadcast Message Contents + +This clause describes the LCS Assistance Data messages to be broadcasted in SMSCB message's content part over CBCH channel using SMSCB DRX service. The rules and contents are described so that SMLC is able to construct the message as well as MS is able to process the received message. The E-OTD Assistance Data message contains RTD and BTS coordinate information and GPS Assistance Data contains GPS Differential Correction data, Ephemeris and Clock Correction Data and Almanac and Other Data. + +## 4.1 E-OTD Assistance Data Broadcast Message + +The E-OTD Assistance Data message contents are defined in this clause. The E-OTD Assistance Data message is built so that it has always a fixed length and some of the information elements are scalable according to the amount of neighbours and the amount of sectorized channels. The information elements are in the order which is described in subclause 4.1.1 and no spare bits are allowed between elements. The MSB bits of the information elements are presented always first and if boundary of the octet divides the information element then the LSB part of the information element continues in the LSB part of the next octet (figure 1). Example of E-OTD Assistance Data Broadcast Message is in annex B. The channel to broadcast the E-OTD Assistance Data message is CBCH over which the SMSCB DRX service is used. One SMSCB message has fixed information data length of 82 octets and the purpose is always to use the whole fixed length message capacity for the message. MS can identify the LCS SMSCB message with E-OTD Message Identifier declared in 3GPP TS 23.041. + +![Figure 1: Information element bit mapping to the broadcast message. The diagram shows a long horizontal bar at the top representing an 'Information Element Containing 26 bits', divided into 26 individual bit cells labeled 7 down to 0, repeated three times, followed by bits 1 and 0. The first bit is labeled 'MSB' and the last 'LSB'. Below this, a 'Broadcast Message' table shows how these bits are packed into octets. Octet n contains bits 7-0. Octet n+1 contains bits 7-0. Octet n+2 contains bits 7-0. Octet n+3 contains MSB, Next IE (bits 7-2), 1, and 0. Octet n+4 contains Next IE LSB (bits 1-0) and bits 7-4. Octet n+5 contains bits 3-0. Arrows show the mapping of bit groups from the top bar into the octets of the broadcast message table.](5d76c2e9976aaf97001ee189908830fb_img.jpg) + +Figure 1: Information element bit mapping to the broadcast message. The diagram shows a long horizontal bar at the top representing an 'Information Element Containing 26 bits', divided into 26 individual bit cells labeled 7 down to 0, repeated three times, followed by bits 1 and 0. The first bit is labeled 'MSB' and the last 'LSB'. Below this, a 'Broadcast Message' table shows how these bits are packed into octets. Octet n contains bits 7-0. Octet n+1 contains bits 7-0. Octet n+2 contains bits 7-0. Octet n+3 contains MSB, Next IE (bits 7-2), 1, and 0. Octet n+4 contains Next IE LSB (bits 1-0) and bits 7-4. Octet n+5 contains bits 3-0. Arrows show the mapping of bit groups from the top bar into the octets of the broadcast message table. + +Figure 1: Information element bit mapping to the broadcast message + +### 4.1.1 E-OTD Assistance Data Broadcast Message Content + +The Broadcast Assistance Data is a point-to-multipoint message from the GSM Network to the MSs. This message gives assistance data to the MS for performing E-OTD measurements and calculating its own position. It contains the following information elements. The information elements are always in the order described in table 1. The ciphered part of message is end of message and indicated with grey shading in table 1. + +**Table 1: E-OTD Assistance Data Broadcast Message Content** + +| Information element | Type/Reference | Presence | +|---------------------------------------|------------------------------------------------|----------| +| Message Structure Definition | Message Structure Definition 4.1.1.1 | M | +| Reference Time | Reference Time 4.1.1.2 | M | +| Ciphering Serial Number | Ciphering Serial Number 4.1.1.3 | C | +| Time Slot Scheme | Time Slot Scheme 4.1.1.4 | M | +| Neighbour Bitmap Definition | Neighbour Bitmap Definition 4.1.1.5 | C | +| Sectorized Channels Definition | Sectorized Channels Definition 4.1.1.6 | C | +| Sectorized Channels BTS ID Definition | Sectorized Channel's BTS ID Definition 4.1.1.7 | C | +| Sectorized BTS Sync/Async Definition | Sectorized BTS Sync/Async Definition 4.1.1.8 | C | +| 51 Multiframe Offset Values | 51 Multiframe Offset Values 4.1.1.9 | M | +| BCC Definition | BCC Definition 4.1.1.10 | M | +| RTD Drift Factor Values | RTD Drift Factor Values 4.1.1.11 | C | +| Channel RTD Values | Channel RTD Values 4.1.1.12 | C | +| Serving Cell Location | Serving Cell Location 4.1.1.13 | M | +| Relative Neighbour Location Values | Relative Neighbour Location Values 4.1.1.14 | M | + +#### 4.1.1.1 Message Structure Definition IE + +This IE contains the definition of this broadcast message. The length of this IE is 19 bits and it is mandatory. This IE contains the following bits. + +**Table 2: Message Structure Definition** + +| Bit | Bit order in field | Definition | +|-----|--------------------|---------------------------------| +| 1 | LSB | Neighbour List Map (bits 2-0) | +| 2 | | | +| 3 | MSB | | +| 4 | LSB | Accuracy Range (bits 2-0) | +| 5 | | | +| 6 | MSB | | +| 7 | | Ciphering Key Flag | +| 8 | | Cipher On/Off | +| 9 | | Sector Ind | +| 10 | | RTD Range | +| 11 | LSB | RTD Accuracy (bits 1-0) | +| 12 | MSB | | +| 13 | | RTD Drift Factors Present | +| 14 | | RTDs Present | +| 15 | LSB | Number of Neighbours (bits 4-0) | +| 16 | | | +| 17 | | | +| 18 | | | +| 19 | MSB | | + +The first three octets upto bit 3 in octet 3 in the broadcast message's content part containing the Message Structure Definition IE look always as follows. + +| 8 | 7 | 6 5 | | 4 3 | | 2 1 | | Octet1 | +|---------------------------------------|----------------------------|------------------------------|------------------------------------|----------------------------------|--|--------------|---------------|--------| +| Cipher On/Off | Cipher-
ing Key
Flag | Accuracy Range
(bits 2-0) | | Neighbour List Map
(bits 2-0) | | | | Octet1 | +| Number of
Neighbours
(bits 4-3) | | RTDs
Present | RTD
Drift
Factors
Present | RTD Accuracy
(bits 1-0) | | RTD
Range | Sector
Ind | Octet2 | +| (Next IE) | | | | Number of Neighbours (bits 2-0) | | | | Octet3 | + +The definitions of each structure item is declared below: + +##### Neighbour List Map + +These bits define in which order the neighbours in the System Information Neighbour List (max 32 neighbours) are reported with the broadcast message. + +- The Neighbour List Map will also affect the amount of bits that can be used for Relative Neighbour Location Value definitions. +- This Broadcast Assistance Data message is always referring to the neighbour BTSs included in the System Information Neighbour List which is received in idle state from BCCH. The E-OTD broadcast message does not allow the possibility for delivering assistance data for other BTSs (outside the the System Information Neighbour List). + +**Table 3: Neighbour List Map** + +| 2 | 1 | 0 | Definition | +|---|---|---|----------------------------------------| +| 0 | 0 | 0 | All Neighbours from neighbour list | +| 0 | 0 | 1 | Even Neighbours from neighbour list | +| 0 | 1 | 0 | Odd Neighbours from neighbour list | +| 0 | 1 | 1 | 1 st & 1 st +n*3 | +| 1 | 0 | 0 | 2 nd & 2 nd +n*3 | +| 1 | 0 | 1 | 3 rd & 3 rd +n*3 | +| 1 | 1 | 0 | Neighbour Bitmap Definition | +| 1 | 1 | 1 | Spare | + +- All Neighbours means all the neighbours from System Information Neighbour list (max 32 neighbours) are reported in this broadcast message (1 broadcast message). +- Even/Odd neighbours from neighbour list means the even/odd list entries in the System Information Neighbour List are reported in this broadcast message (two broadcast messages needed). +- 1st & 1st+n\*3 means that 1st, 4th, 7th, 10th, ..., 31st (max 11 neighbours) will be reported in this broadcast message (1/3 of total broadcast). +- 2nd & 2nd+n\*3 means that 2nd, 5th, 8th, 11th, ..., 32nd (max 11 neighbours) will be reported in this broadcast message (2/3 of total broadcast). +- 3rd & 3rd+n\*3 means that 3rd, 6th, 9th, 12th, ..., 30th (max 10 neighbours) will be reported in this broadcast message (3/3 of total broadcast). +- The 1st & 1st+n\*3, 2nd & 2nd+n\*3 and 3rd & 3rd+n\*3 means total 3 broadcast messages. +- Neighbour Bitmap Definition will define which neighbours are included into this broadcast message, see subclause 4.1.1.5. + +##### Accuracy Range + +The accuracy range declares the accuracy of the values in the Relative Neighbour Location Value IE. The accuracy range has the following information. + +**Table 4: Accuracy Range** + +| 2 | 1 | 0 | Definition | +|----------|----------|----------|-------------------| +| 0 | 0 | 0 | 5 km | +| 0 | 0 | 1 | 10 km | +| 0 | 1 | 0 | 15 km | +| 0 | 1 | 1 | 20 km | +| 1 | 0 | 0 | 30 km | +| 1 | 0 | 1 | 45 km | +| 1 | 1 | 0 | 60 km | +| 1 | 1 | 1 | 120 km | + +For example if there are 15 bits (1 sign bit and 14 value bits) reserved for Relative Neighbour North or East Value and the accuracy range is defined to be 20 km, then resolution of Relative Neighbour North or East Value is 0.6 m. + +##### Ciphering Key Flag + +The MS gets two (2) deciphering keys always with location update, a deciphering key that is time stamped to be current one and deciphering key that time stamped to be next one. Thus the MS has always two deciphering keys in memory. With this Ciphering Key Flag in this broadcast message the MS knows whether to use current/next deciphering key for deciphering the received broadcast message. The MS shall interpret this IE as follows: + +- **Ciphering Key Flag(previous message) = Ciphering Key Flag(this message)** => Deciphering Key not changed. +- **Ciphering Key Flag(previous message) <> Cipher Key Flag(this message)** => Deciphering Key changed. + +##### Cipher On/Off + +This bit indicates whether this broadcast message has been ciphered or not. The RTD Drift Factor Values IE, Channel RTD Values IE, Serving Cell Location IE and Relative Neighbour Location Values IE will be ciphered if ciphering is active. + +- '0' Ciphering Off. +- '1' Ciphering On. + +##### Sector Ind + +This bit indicates whether this broadcast message contains BTS Sectorized Cell information or not. + +- '0' No Sector Information included. +- '1' Sector Information included. + +##### RTD Range + +This bit indicates whether the RTD value covers only one time slot period or 8 time slot period. This bit will affect the RTD field so that there will be need for 3 bits more for RTD if whole 8 time slot period need to be indicated with RTD value. + +- '0' RTD value covers 1 time slot period. +- '1' RTD value covers 8 time slots period. + +##### RTD Accuracy + +This contains two bits, which define what will be the accuracy of RTD value in this broadcast message. The accuracy will be coded as follows. + +**Table 5: Accuracy Range** + +| 1 | 0 | Definition | +|----------|----------|--------------------| +| 0 | 0 | 1/16 bit accuracy | +| 0 | 1 | 1/32 bit accuracy | +| 1 | 0 | 1/64 bit accuracy | +| 1 | 1 | 1/128 bit accuracy | + +The RTD accuracy will affect the amount of bits needed to indicate the RTD value. The following table describes the accuracy related to needed bits. + +**Table 6: Amount of RTD bits needed** + +| Time Slots | Accuracy | Amount of Bits Needed | +|-------------------|-----------------|------------------------------| +| 1 | 1/16 | 12 bits | +| | 1/32 | 13 bits | +| | 1/64 | 14 bits | +| | 1/128 | 15 bits | +| 8 | 1/16 | 15 bits | +| | 1/32 | 16 bits | +| | 1/64 | 17 bits | +| | 1/128 | 18 bits | + +##### RTD Drift Factors Present + +This bit indicates whether the RTD Drift Factors are present in this broadcast message. If RTDs Present bit indicates that the RTD Values are not included into this broadcast message, the state of this bit should be ignored and the RTD Drift Factors are not present in this broadcast message. + +- '0' RTD Drift Factors are not present in the message. +- '1' RTD Drift Factors are present in the message. + +##### RTDs Present + +This bit indicates whether RTD Values IE is present in this broadcast or not. + +- '0' RTD Values IE not present. +- '1' RTD Values IE present. + +##### Number of Neighbours + +These 5 bits are indicating the amount of neighbours are in System Information Neighbour List according to which this broadcast message was created. The number of neighbours indicated here makes sure that MS can decode back this broadcast message IEs as they were originally sent. If the MS has received different amount of neighbours in System Information Neighbour List than indicated in this field in broadcast message, the MS should ignore this broadcast message. + +Range: 1 - 32 Neighbours. + +#### 4.1.1.2 Reference Time IE + +The Reference Time IE gives information about the time when the RTD values in the broadcast message are calculated. The Reference Time IE contains the serving cell frame number modulo 131072 with 7 LSB bits omitted. The resolution of this Reference Time IE is thus 0.59 s. The Reference Time IE has 10 minutes periodicity. This IE is mandatory. + +Range: 0 - 1023. + +#### 4.1.1.3 Ciphering Serial Number IE + +The Ciphering Serial Number IE contains the serial number used in ciphering process of the broadcast message. The IE contains two octets, MSB part and LSB part. The serial number range is 0 - 65535. This IE is conditional and it is present only if the ciphering flag is active in Message Structure Definition IE. + +**Table 7: Ciphering Serial Number IE** + +| MSB | LSB | +|----------------------------------|----------------------------------| +| Ciphering Serial Number (8 bits) | Ciphering Serial Number (8 bits) | + +#### 4.1.1.4 Time Slot Scheme IE + +This information element contains information about the serving cell channel and neighbour channel time slot scheme. The list starts with Serving Cell Channel and the rest of the list is in the same order as the neighbours in the System Information Neighbour List. For each list member there is one bit reserved to indicate whether the channel has 156.25 bits time slot duration or 156/157 bits time slot duration. This field is varying length depending on amount of neighbours of System Information Neighbour List (max 32) and maximum length of this IE is 33 bits (1+32 bits). The Serving Cell Channel time slot scheme is always indicated as the first (MSB) element of this field. This IE is mandatory. + +- '0' 156.25 bits time slot duration. +- '1' 156/157 bits time slot duration. + +**Table 8: Time Slot Scheme** + +| Serving Cell Ch (MSB) | Neigh Ch last | ... | Neigh Ch 3 | Neigh Ch 2 | Neigh Ch 1 (LSB) | +|-----------------------|--------------------------|-----|-----------------------|-----------------------|-----------------------------| +| 0/1 | 0/1 | ... | 0/1 | 0/1 | 0/1 | + +#### 4.1.1.5 Neighbour Bitmap Definition IE + +This IE defines which neighbours from System Information Neighbour List are included in this message. The IE is conditional and included only if Message Structure Definition IE's Neighbour List Map indicates the use of this Neighbour Bitmap Definition. The list is in the same order as the neighbours in the System Information Neighbour List, the last member of the list presented as the MSB element of this field. For each Neighbour List channel number there is one bit reserved to indicate whether the neighbour is included into this broadcast message. This field is varying length depending on the amount of neighbours of System Information Neighbour List (max 32) and maximum length of this IE is 32 bits. + +- '0' Neighbour not included into this broadcast message. +- '1' Neighbour included into this broadcast message. + +**Table 9: Neighbour Bitmap Definition** + +| Neigh Ch last (MSB) | ... | Neigh Ch 3 | Neigh Ch 2 | Neigh Ch 1 (LSB) | +|--------------------------------|-----|-----------------------|-----------------------|-----------------------------| +| 0/1 | ... | | 0/1 | 0/1 | + +#### 4.1.1.6 Sectored Channels Definition IE + +This information element defines which neighbours in System Information Neighbour List that are included in this broadcast message are belonging to sectored BTSs. This IE is conditional and included only if Message Structure Definition IE's Sector Indicator is active. This field is varying length depending on amount of neighbours included into this broadcast message (max 32) and the maximum length of this IE is 33 bits (1+32 bits). The Serving Cell Channel sector indication is always indicated in MSB of this field and the neighbours are in same order as the neighbours in the System Information Neighbour List. + +- '0' Channel not included to sectored BTS. +- '1' Channel included to sectored BTS. + +**Table 10: Sectored Channels Definition** + +| Serving Ch (MSB) | Neigh Ch last | ... | Neigh Ch 3 | Neigh Ch 2 | Neigh Ch 1 (LSB) | +|------------------|--------------------------|-----|-----------------------|-----------------------|-----------------------------| +| 0/1 | 0/1 | ... | 0/1 | 0/1 | 0/1 | + +#### 4.1.1.7 Sected Channels BTS ID Definiton IE + +This information element defines what sected channels are at the same BTS. The indication is done with three bits for each neighbour channel that is indicated to belong to sected BTS (definition in Sected Channels Definiton IE). Belonging to the same BTS site is indicated with the same three bit binary ID, maximum 8 sected BTS groups can be identified. This field is varying length depending on amount of sected BTS in this broadcast message (max 33\*3 bits = 99 bits when all 32 neighbours and the serving cell channel are belonging to some sector). This field follows the order of channels that have indicated to be belonging to sected BTS in Sected Channels Definiton starting from the MSB. This IE is conditional and included only if Message Structure Definiton IE's Sector Ind is active. + +**Table 11: Sected Channels BTS ID Definiton** + +| 2 | 1 | 0 | Definition | +|---|---|---|----------------| +| 0 | 0 | 0 | Sected BTS ID1 | +| 0 | 0 | 1 | Sected BTS ID2 | +| 0 | 1 | 0 | Sected BTS ID3 | +| 0 | 1 | 1 | Sected BTS ID4 | +| 1 | 0 | 0 | Sected BTS ID5 | +| 1 | 0 | 1 | Sected BTS ID6 | +| 1 | 1 | 0 | Sected BTS ID7 | +| 1 | 1 | 1 | Sected BTS ID8 | + +**Table 12: Sected Channels BTS ID Definiton** + +| Indicated Sected Serving Channel (MSB) | Indicated Sected Neighbour last | ... | Indicated Sected Neighbour 3 | Indicated Sected Neighbour 2 | Indicated Sected Neighbour 1 (LSB) | +|----------------------------------------|--------------------------------------------|-----|-----------------------------------------|-----------------------------------------|-----------------------------------------------| +| Sec. BTS ID X (3 bits) | Sec. BTS ID X (3 bits) | ... | Sec. BTS ID X (3 bits) | Sec. BTS ID X (3 bits) | Sec. BTS ID X (3 bits) | + +#### 4.1.1.8 Sected BTS Sync/Async Definiton IE + +This information element defines whether the indicated sected BTS site contains synchronized or asynchronous channels. The sync/async is informed with one bit per sected BTS ID. This field follows the order of IDs in Sected Channels BTS ID Definiton. This field is varying length depending on amount of sected BTS ID in this broadcast message (max 8 bits). This IE is conditional and is included only if Message Structure Definiton IE's Sector Ind is active. + +- '0' Sected BTS contains async channels. +- '1' Sected BTS contains sync channels. + +**Table 13: Sected BTS Sync/Async Definiton** + +| Sec BTS Last (MSB) | ... | Sec BTS ID3 | Sec BTS ID2 | Sec BTS ID1 (LSB) | +|-------------------------------|-----|------------------------|------------------------|------------------------------| +| 0/1 | ... | 0/1 | 0/1 | 0/1 | + +#### 4.1.1.9 Multiframe Offset Values IE + +This information element defines the neighbour channel's 51 Multiframe Values. The 51 Multiframe Offset Values are describing the offset value related to the Serving Cell 51 Multiframe Value. This field is needed when co-channels must be identified from the real neighbour channels (included into System Information Neighbour List). Each 51 Multiframe Offset Value is 6 bits long denoting the offset value to the Serving Cell 51 Multiframe number. The 51 Multiframe Offset Values must be declared to all neighbours in this broadcast message and the values are in the same order as the neighbours in the System Information Neighbour List. The maximum length of this IE is 192 bits (32\*6 bits). This IE is mandatory. + +Range: 0 - 50 Frames + +**Table 14: 51 Multiframe Offset Values IE** + +| 51 MF OffsetNbLast (MSB) | ... | 51 MF OffsetNb3 | 51 MF OffsetNb2 | 51 MF OffsetNb1 (LSB) | +|--------------------------------------------|------------|-----------------------------------|-----------------------------------|-----------------------------------------| +| Offset Value (6 bits) | ... | Offset Value (6 bits) | Offset Value (6 bits) | Offset Value (6 bits) | + +#### 4.1.1.10 BCC Definition IE + +This information element defines the BBC (Base Station Color Code) values. The BCC is needed to know what training sequence is in use in the bursts in BCCH frequency. Each BCC is 3 bits long denoting the one of the 8 possible TSCs (Training Sequence Codes) possible to be used in bursts. BCC values must be declared to all neighbours in this message and the values are in the same order as the neighbours in the System Information Neighbour List. The maximum length of this IE is 96 bits (32\*3 bits). This IE is mandatory. + +**Table 15: BCC Definition IE** + +| BCCNbLast (MSB) | ... | BCCNb3 | BCCNb2 | BCCNb1 (LSB) | +|-----------------------------------|------------|--------------------------|--------------------------|--------------------------------| +| BCC Value (3 bits) | ... | BCC Value (3 bits) | BCC Value (3 bits) | BCC Value (3 bits) | + +#### 4.1.1.11 RTD Drift Factor Values IE + +This IE contains the drift factor values for the Channel RTD Values included into this broadcast message. The RTD Drift Factor Values indicate the RTD drift in meters per second. Positive and negative RTD Drift Factors can be indicated as well as no drift value. This information element is conditional and included if the RTD Drift Factors Present bit in the Message Structure Definition IE is active and the RTDs Present bit is active. The RTD Drift Factors are included into the broadcast message with same conditions and in same order than the Channel RTD Values which are described in Channel RTD Values IE section (subclause 4.1.1.12). This IE should be ciphered if the ciphering is active. Each RTD Drift Factor Value is 5 bits long and the coding is as follows: + +**Table 16: RTD Drift Factor Values** + +| Positive/Negative
MSB | Coding Bits | | | | Definition | +|--------------------------|-------------|----------|----------|----------|------------| +| | MSB | 2 | 1 | LSB | | +| 3 | 3 | 2 | 1 | 0 | | +| Don't care | 0 | 0 | 0 | 0 | 0 m/s | +| 0 | 0 | 0 | 0 | 1 | +0.33 m/s | +| 0 | 0 | 0 | 1 | 0 | +0.66 m/s | +| 0 | 0 | 0 | 1 | 1 | +1 m/s | +| 0 | 0 | 1 | 0 | 0 | +1.33 m/s | +| 0 | 0 | 1 | 0 | 1 | +1.66 m/s | +| 0 | 0 | 1 | 1 | 0 | +2 m/s | +| 0 | 0 | 1 | 1 | 1 | +2.5 m/s | +| 0 | 1 | 0 | 0 | 0 | +3 m/s | +| 0 | 1 | 0 | 0 | 1 | +4 m/s | +| 0 | 1 | 0 | 1 | 0 | +5 m/s | +| 0 | 1 | 0 | 1 | 1 | +7 m/s | +| 0 | 1 | 1 | 0 | 0 | +9 m/s | +| 0 | 1 | 1 | 0 | 1 | +11 m/s | +| 0 | 1 | 1 | 1 | 0 | +13 m/s | +| 0 | 1 | 1 | 1 | 1 | +15 m/s | +| 1 | 0 | 0 | 0 | 1 | -0.33 m/s | +| 1 | 0 | 0 | 1 | 0 | -0.66 m/s | +| 1 | 0 | 0 | 1 | 1 | -1 m/s | +| 1 | 0 | 1 | 0 | 0 | -1.33 m/s | +| 1 | 0 | 1 | 0 | 1 | -1.66 m/s | +| 1 | 0 | 1 | 1 | 0 | -2 m/s | +| 1 | 0 | 1 | 1 | 1 | -2.5 m/s | +| 1 | 1 | 0 | 0 | 0 | -3 m/s | +| 1 | 1 | 0 | 0 | 1 | -4 m/s | +| 1 | 1 | 0 | 1 | 0 | -5 m/s | +| 1 | 1 | 0 | 1 | 1 | -7 m/s | +| 1 | 1 | 1 | 0 | 0 | -9 m/s | +| 1 | 1 | 1 | 0 | 1 | -11 m/s | +| 1 | 1 | 1 | 1 | 0 | -13 m/s | +| 1 | 1 | 1 | 1 | 1 | -15 m/s | + +**Table 17: RTD Drift Factor Values IE** + +| RTD Drift Factor NbLast
(MSB) | ... | RTD Drift Factor Nb3 | RTD Drift Factor Nb2 | RTD Drift Factor Nb1
(LSB) | +|------------------------------------|-----|------------------------------------|------------------------------------|------------------------------------| +| RTD Drift Factor Value
(5 bits) | ... | RTD Drift Factor Value
(5 bits) | RTD Drift Factor Value
(5 bits) | RTD Drift Factor Value
(5 bits) | + +#### 4.1.1.12 Channel RTD Values IE + +This IE contains the channel RTD values relative to the serving BTS. The RTD is defined as TBTS - TServ, where TBTS is the time of the start of TS0 (Time Slot 0) in the neighbor BTS, and Tserv is the time of the start of the TS0 in the serving BTS. The RTD value covers 1 or 8 time slot period with 1/16-1/128 bit accuracy. The 1 or 8 time slot period as well as 1/16-1/128 bit accuracy is defined in Message Structure Definition IE. The RTD values included here are conditional to the RTDs Present and Neighbour List Map (Message Structure Definition IE), Neighbour Bitmap Definition IE, Sected Channels Definition IE, Sected Channels BTS ID Definition and Sected BTS Sync/Async Definition. This IE should be ciphered if the ciphering is active. The decision which BTS RTD value is included in this broadcast message has the following decision process: + +- Channel RTD Values IE should not be included at all if RTDs Present bit (Message Structure Definition IE) is not active. +- Neighbours in this broadcast message are defined in Neighbour List Map (Message Structure Definition IE) and in case the Neighbour Bitmap Definition is active then the Neighbour Bitmap Definition IE declares the Neighbours included into this broadcast message. + +- If Sector Indicator in Message Structure Definition IE is not active the RTD values are included for all neighbours in this broadcast message. +- If sector indicator in Message Structure Definition IE is active then the Neighbour channels that are not belonging to sectorized BTS the RTD values are included directly according to neighbour list order. +- If sector indicator in Message Structure Definition IE is active then the Neighbour channels that are belonging to sectorized BTS, the Sectorized BTS ID values group the neighbour channels into the groups. If the Sectorized BTS ID group is indicated to be synchronous then only one RTD value (decided by SMLC) per the Sectorized BTS ID group is included into this broadcast message, if the Sectorized BTS ID group is indicated to be asynchronous then all the neighbour channel RTDs belonging to the Sectorized BTS ID group have to be included into this broadcast message. + +**Table 18: Channel RTD Value IE** + +| (MSB) | Varying Length (12-18 bits) | (LSB) | +|----------------------------|-----------------------------|-------| +| Neighbour RTD (Last) (MSB) | | | +| Neighbour RTD (Last-1) | | | +| ... | | | +| Neighbour RTD (2) | | | +| Neighbour RTD (1) (LSB) | | | + +The fields that are included into the Channel RTD Value IE may contain RTD values of neighbour channels and the RTD values of the sectorized channels BTS ID. The RTD values should be included into this IE in following order: + +- Starting from the last channel in the System Information Neighbour List that is included into this broadcast message. +- First are reported the neighbour channels that are not belonging to the Sectorized Channels BTS ID groups and then the Sectorized Channels ID groups from 1 up to 8 depending the amount of groups. See annex B for example. + +If the RTD value is invalid, following values in the RTD field are reserved for this indication (e.g. if invalid RTD value is indicated the MS shall discard the previous values). + +**Table 19: Invalid RTD Value Codes** + +| Time Slots | Accuracy | Amount of Bits in RTD | Invalid RTD Code in Hex | +|------------|----------|-----------------------|-------------------------| +| 1 | 1/16 | 12 bits | FFF | +| | 1/32 | 13 bits | 1FFF | +| | 1/64 | 14 bits | 3FFF | +| | 1/128 | 15 bits | 7FFF | +| 8 | 1/16 | 15 bits | 7FFF | +| | 1/32 | 16 bits | FFFF | +| | 1/64 | 17 bits | 1FFFF | +| | 1/128 | 18 bits | 3FFFF | + +This field is varying length depending on amount of Neighbour Channels included as well as amount of sectorized cells and the nature (sync/async) of sectorized cells. One RTD value has varying length of 12 bits to 18 bits indicating the amount on 1/16-1/128 bit durations over 1 time slot or 8 time slots. Maximum length of this IE is 576 bits (32\*18 bits). + +#### 4.1.1.13 Serving Cell Location IE + +This IE contains the Serving Cell Latitude/Longitude information. This IE should be ciphered if the ciphering is active. This IE is mandatory. + +##### Serving Cell Latitude + +This field indicates WGS-84 latitude with fixed length of 24 bits. Latitude value is coded according to 3GPP TS 23.032. This field is mandatory. + +**Table 20: Serving Cell Latitude** + +| (MSB) | 24 – 1 | (LSB) | +|---------------------------------|--------|-------| +| Serving Cell Latitude (24 bits) | | | + +##### **Serving Cell Longitude** + +This field indicates WGS-84 longitude with fixed length of 24 bits. Latitude value is coded according to 3GPP TS 23.032. This field is mandatory. + +**Table 21: Serving Cell Longitude** + +| (MSB) | 24 – 1 | (LSB) | +|----------------------------------|--------|-------| +| Serving Cell Longitude (24 bits) | | | + +#### **4.1.1.14 Relative Neighbour Location IE** + +This information element defines the location of Neighbour Channels (BTS) relative to Serving Cell Location. This IE should be ciphered if the ciphering is active. The fields are varying length depending on amount of neighbour channels and sectorized cells included in this broadcast message. The location information per neighbour has two elements, Relative North and Relative East. The Relative North positive values indicate north direction, negative values indicate south direction from Serving Cell Location. The Relative East positive values indicate east direction and negative values indicate west direction from Serving Cell Location. The MSB bit in Relative North/East value is reserved for sign indication (positive = 0, negative = 1). The values are expressed in meters according to the accuracy resolution which is defined by Accuracy Range bits in Message Structure Definition IE. For example if the Accuracy Range is set to 20 km and there is 15 bits (1+14 bits) reserved for Relative North/East values this means 0.6 m accuracy for Relative North or East value. This IE is mandatory. + +The amount of Relative North/East pairs depends on neighbours included in this broadcast message as well as the amount sectorized cells since only one Relative North/East pair is included per Sectorized BTS ID. + +**Table 22: Relative Neighbour Location** + +| (MSB) | Varying Length | (LSB) | +|---------------------------------------------|----------------|-------| +| Relative North Value Neighbour (Last) (MSB) | | | +| Relative East Value Neighbour (Last) | | | +| Relative North Value Neighbour (Last-1) | | | +| Relative East Value Neighbour (Last-1) | | | +| ... | | | +| Relative North Value (2) | | | +| Relative East Value (2) | | | +| Relative North Value (1) | | | +| Relative East Value (1) (LSB) | | | + +The decision what Relative North/East Values are included in this broadcast message has following decision process: + +- Neighbours in this broadcast message is defined in Neighbour List Map (Message Structure Definition IE) and in case the Neighbour Bitmap Definition is active then the Neighbour Bitmap Definition IE declares the Neighbours included into this broadcast message. +- If Sector Indicator in Message Structure Definition IE is not active the Relative North/East Values are included in the same order as they are indicated in Message Structure Definition IE / Neighbour Bitmap Definition IE. +- If sector indicator in Message Structure Definition IE is active then the Neighbour channels that are not belonging to sectorized BTS Relative North/East Values are included directly according to neighbour list order. +- If sector indicator in Message Structure Definition IE is active then the Neighbour channels that are belonging to sectorized BTS, the Sectorized BTS ID values group the neighbour channels into the groups. The Relative North/East Values are included in the broadcast message so that only one Relative North/East Value per Sectorized BTS ID is included. + +The fields that are included into the Relative Neighbour Location IE may contain the Relative North/East values of neighbour channels and the Relative North/East values of the sectorized channels BTS ID groups. The RTD values should be included into this IE in following order: + +- Starting from the last channel in the System Information Neighbour List that is included into this broadcast message. +- First are reported the neighbour channels that are not belonging to the Sectorized Channels BTS ID groups and then the Sectorized Channels ID groups from 1 up to 8 depending the amount of groups. +- The neighbour channel/BTS ID value will always contain Relative North value first and then Relative East value. The values are expressed in meters according to the Accuracy Range in the Message Structure Definition IE. See annex B for example. + +The bits available for Relative North/East Values can be calculated with following formula: + +$$\begin{aligned} + z &= \text{number of neighbours in System Info Neighbour List} \\ + x &= \text{number of neighbours in this broadcast message} \\ + a &= \text{number of channels in sectors} \\ + b &= \text{number of BTS IDs} \\ + c &= \text{RTD accuracy (12-18 bits)} \\ + w &= \text{Neighbour Bitmap used (yes = 1, no = 0)} \\ + s &= \text{RTDs Present (yes = 1, no = 0)} \\ + d &= \text{RTD Drift Factors included (yes = 1, no = 0)} \\ + y &= \text{bits per Relative Latitude / Longitude value} \\ + \text{Int}(y) &= (561 - 11 * x^{-3} * a - b - s * (c + d * 5) * (x - a + b) - w * z) / (2 * (x - a + b)) + \end{aligned}$$ + +If the y doesn't go even, the bits that remain are used as one extra bit (extension bit) per one Relative North or East value in same order as the values are presented in this IE as long as there are remain bits available. See Annex B for example. + +## 4.2 GPS Assistance Data Broadcast Message + +The GPS Assistance Data message contents are defined in this clause. The GPS Assistance Data message is built so that it is fitted into a fixed length message not necessary occupying the whole message. In case that the fixed length message has less information elements than bits available then the rest of message is filled with fill bits. The information elements are in the order which is described in subclause 4.2.1 and no undefined spare bits are allowed between elements. The channel to broadcast the GPS Assistance Data message is CBCH over which the SMSCB DRX service is used. One SMSCB message has fixed information data length of 82 octets and the maximum length of GPS Assistance Data is 82 octets. MS can identify the LCS SMSCB message with Message Identifiers declared in 3GPP TS 23.041. Example of GPS Assistance Data Broadcast Message is in Annex C. In addition, an Integrity Monitor (IM) shall detect unhealthy (e.g. failed/failing) satellites. When an unhealthy (i.e. failed/failing) satellite is detected, the assistance data, including DGPS corrections, shall not be supplied for that particular satellite. If more satellites are unhealthy, the same can be done to exclude them from the final location calculation. Even when all satellites are healthy, the IM shall monitor the quality of the DGPS corrections. It shall make use of the pseudoranges derived by the DGPS reference receiver, correct them using the DGPS reference receiver-generated DGPS corrections, and compute a position from the corrected pseudo ranges. This computed position shall then be compared with the known, surveyed location of the DGPS reference receiver to compute a DGPS positioning error. Positioning errors which are excessive relative to DGPS expected accuracy levels shall be used to inform users of measurement quality via the UDRE parameter. + +### 4.2.1 GPS Assistance Data Content + +The GPS Assistance Data Message contents are defined in this clause. It contains three data sets: DGPS correction, ephemeris and clock correction, almanac and other data information. The ephemeris, clock correction, almanac and other data are obtained from GPS navigation message. It is built so that it fits into a fixed length message not necessarily occupying the whole message. In case that the fixed length message has less information elements than bits available then the rest of message is filled with fill bits. + +This message is built to allow for broadcast rates that more closely match the time of applicability of the contained data. + +EXAMPLE: With a 30 s rate for DGPS broadcast, mobile station (MS) can effectively remove degradation caused by SA. + +GPS subframes 1 through 3 (ephemeris and clock correction data) are contained in the same single broadcast message. With a 90 s rate, Mobile Stations (MS) can receive all visible ephemeris and clock correction data at twelve to eighteen minute intervals depending on number of visible satellites. Subframes 4 and 5 (almanac, ionospheric delay, and other more slowly changing data) can be sent at another rate, such as once every several hours. By splitting the data into separate data sets (all based on the same single format), the data can be sent at rates that correspond to its validity time and/or the desire to update the mobile stations within its network at a particular rate. The Information Elements (IEs) in the message are listed in table 23. + +**Table 23: Information Elements of GPS Assistance Data message** + +| Parameter | Bits | Resolution | Range | Units | Occurrences | Presence | Ref | +|-------------------------|--------------------|------------|-----------|-------|-------------|----------|-----| +| Cipher Control | Cipher On/Off | 1 | --- | 0 - 1 | --- | 1 | M | +| | Ciphering Key Flag | 1 | --- | 0 - 1 | --- | 1 | M | +| Ciphering Serial Number | 16 | --- | 0 - 65535 | --- | 1 | C | | +| Data | 638 | --- | - | --- | --- | M | | + +#### Cipher Control IE + +This information element contains two bits indicating the ciphering properties of the received message. This IE is mandatory. + +#### Cipher On/Off + +This IE indicates whether this broadcast message has been ciphered or not. A value of "0" indicates that ciphering is off, while a value of "1" indicates that ciphering is active. The Data IE is ciphered if ciphering is active. + +#### Ciphering Key Flag + +The MS always receives two (2) cipher keys during the location update procedure. One of the keys is time-stamped to be current one and the other is time-stamped to be the next one. Thus, the MS always has two cipher keys in memory. The Cipher Key Change Indicator in this broadcast message instructs the MS whether to use current or next cipher key for deciphering the received broadcast message. The MS shall interpret this IE as follows: + +- **Ciphering Key Flag(previous message) = Ciphering Key Flag(this message)** => Deciphering Key not changed. +- **Ciphering Key Flag(previous message) <> Ciphering Key Flag(this message)** => Deciphering Key changed. + +#### Ciphering Serial Number IE + +The Ciphering Serial Number IE contains the serial number used in ciphering process of the broadcast message. The IE contains two octets, MSB part and LSB part. The serial number range is 0 - 65535. This IE is conditional and it is present only if the ciphering flag is active in Cipher Control IE. + +**Table 24: Ciphering Serial Number IE** + +| MSB | LSB | +|----------------------------------|----------------------------------| +| Ciphering Serial Number (8 bits) | Ciphering Serial Number (8 bits) | + +#### Data IE + +The Data IE contains the GPS assistance data included in the broadcast message. The Data IE may contain DGPS Correction Data (subclause 4.2.1.1), Ephemeris and Clock Correction Data (subclause 4.2.1.2) or Almanac and Other Data (subclause 4.2.1.3). The Data IE content is indicated with the SMSCB message identifier specified in 3GPP TS 23.041 and 3GPP TS 23.041. When ciphering is active (indicated with Ciphering Control Flags), the ciphering will apply only to the Data IE element. This IE is mandatory. + +#### 4.2.1.1 DGPS Correction Data + +This subclause describes the contents of the broadcast message for differential corrections. The message contents are based on a Type-1 message of version 2.2 of the RTCM-SC-104 recommendation for differential service RTCM-SC104. This format is a standard of the navigation industry and is supported by all DGPS receivers. For a 11 satellites, the length of the broadcast message is 82 octets, which also is the maximum length of an SMSCB message. The + +information elements (IEs) in the message are listed in table 26. If any of the conditional elements (Ciphering Serial Number, BTS Clock Drift, FN, TN and BN) are not included to the message, spare bits will be transmitted instead of these fields. The spare bits have equal length to the conditional IE, so that the message structure is unchanged (see annex C). The spare bits are set to '0'. + +**Table 26: DGPS Correction Data** + +| Parameter | Bits | Resolution | Range | Units | Occurrences | Presence | Ref | +|-------------------------|--------------|-----------------------|-----------|---------------------|-------------|----------|---------| +| GSM Time Present | 1 | --- | 0 - 1 | --- | 1 | M | 4.2.1.2 | +| BTS Clock Drift Present | 1 | --- | 0 - 1 | --- | 1 | M | 4.2.1.3 | +| BTS Clock Drift | 4 | $12.5 \times 10^{-3}$ | $\pm 0.1$ | $\mu\text{sec/sec}$ | 1 | C | 4.2.1.4 | +| Reference Location | 48 | --- | --- | Degrees | 1 | M | 4.2.1.5 | +| Reference time | FN | 22 | --- | 0 - 524287 | frames | 1 | C | +| | TN | 3 | --- | 0 - 7 | timeslots | 1 | C | +| | BN | 8 | --- | 0 - 156 | bits | 1 | C | +| | GPS TOW | 20 | 1 | 0 - 604794 | sec | 1 | M | +| Status/Health | 3 | --- | 0 - 7 | --- | 1 | M | 4.2.1.7 | +| N_SAT | 4 | --- | 1 - 12 | --- | 1 | C | 4.2.1.8 | +| DGPS Corrections | Satellite ID | 6 | --- | 1 - 64 | N_SAT | C | 4.2.1.9 | +| | IODE | 8 | --- | 0 - 239 | | | | +| | UDRE | 2 | --- | 0 - 3 | | | | +| | PRC | 12 | 0.32 | $\pm 655.34$ | | | | +| | RRC | 8 | 0.032 | $\pm 4.064$ | | | | +| | Delta PRC2 | 8 | 1 | $\pm 127$ | | | | +| | Delta RRC2 | 4 | 0.032 | $\pm 0.224$ | | | | + +##### 4.2.1.1.1 GSM Time Present IE + +This field indicates whether or not GSM air-interface timing information values for the serving cell are present in this message. The MS shall interpret a value of "1" to mean that GSM timing information values (FN, TN and BN) are present, and "0" to mean that only the GPS TOW field value is provided. This field is mandatory. + +##### 4.2.1.1.2 BTS Clock Drift Present IE + +This IE is indication whether this broadcast message contains BTS Clock Drift IE value or not. The length of this IE is one bit. The value '1' indicates that BTS Clock Drift IE value is present, '0' indicates that the IE value is not present in this broadcast message. This IE is mandatory. + +##### 4.2.1.1.3 BTS Clock Drift IE + +This IE provides an estimate of the drift rate of the BTS clock relative to GPS time. It has units of $\mu\text{sec/sec}$ (ppm) and a range of $\pm 0.1$ . This IE aids the MS in maintaining the relation between GPS and cell timing over a period of time. The value of the clock drift is valid starting at the time contained in the Reference Time IE. A positive value for BTS Clock Drift indicates that the BTS clock is running at a greater frequency than desired. This IE is conditional and value is included in the message if BTS Clock Drift Present IE flag is '1'. + +##### 4.2.1.1.4 Reference Location IE + +The Reference Location field contains a 2-D location (without uncertainty) specified as per 3GPP TS 23.032. The purpose of this field is to provide the MS with a priori knowledge of its location in order to improve GPS receiver performance. + +##### 4.2.1.1.5 Reference Time IE + +This IE specifies the relationship between GPS time and air-interface timing of the BTS transmission in the serving cell. The **GPS TOW** (time-of-week) has a one-second resolution with a range of 0 to 604799. The **FN**, **TN**, and **BN** IEs are respectively the GSM frame number, timeslot number, and bit number of the BTS transmissions for the serving cell that occur at that GPS time. The frame number FN is modulo- $2^{19}$ (0 - 524287) and the MS shall resolve the ambiguity by interpreting the frame to be as near as possible to the current frame of the serving BTS. The **GPS TOW** IE is mandatory. The **FN**, **TN**, and **BN** IEs are conditional and the values are present only when GSM Time Present bit is '1'. + +##### 4.2.1.1.6 Status/Health IE + +This IE indicates the status of the differential corrections contained in the broadcast message. It is equivalent to the "Station Health" IE in the common header for all reference station messages specified in RTCM-SC104. The values of this IE and their respective meanings are shown below in table 25. This IE is mandatory. + +Table 25: Values of Correction Status + +| Code | Indication | +|------|-----------------------------| +| 000 | UDRE Scale Factor = 1.0 | +| 001 | UDRE Scale Factor = 0.75 | +| 010 | UDRE Scale Factor = 0.5 | +| 011 | UDRE Scale Factor = 0.3 | +| 100 | UDRE Scale Factor = 0.2 | +| 101 | UDRE Scale Factor = 0.1 | +| 110 | No data available | +| 111 | Data is invalid - disregard | + +The first six values in this IE indicate valid differential corrections in the broadcast message. When using the corrections values described below, the "UDRE Scale Factor" value is applied to the UDRE values contained in the message. The purpose is to indicate an estimate in the amount of error in the corrections. + +The value "110" indicates that the source of the differential corrections (e.g. reference station or external DGPS network) is currently not providing information. The value "111" indicates that the corrections provided by the source are invalid, as judged by the source. In either case, the broadcast message shall contain no differential corrections. All MS that read the broadcast message shall contain the appropriate logic to ignore any data IEs following a Correction Status IE having a value of "110" or "111". + +##### 4.2.1.1.7 N\_SAT IE + +This IE indicates the number of satellites (N\_SAT) for which differential corrections are available. The maximum number of satellites that can be included into the message is 12. This IE is conditional and included if Correction Status IE value is not 110 or 111. + +##### 4.2.1.1.8 DGPS Corrections IE + +This IE contains GPS differential correction data. Each element described below will appear N\_SAT times in this message, once for each satellite for which corrections are available. This IE is conditional and included if Correction Status IE value is not 110 or 111. + +###### Satellite ID + +This IE identifies the satellite for which the corrections are applicable. This value is the same as the PRN number provided in the navigation message transmitted by the particular satellite. The range is 0 to 31, with 0 indicating satellite number 32 as per RTCM-SC104. + +###### IODE + +This IE is the sequence number for the ephemeris for the particular satellite. The MS can use this IE 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. For more information about this field can be found from RTCM-SC104. + +###### User Differential Range Error (UDRE) + +This IE provides an estimate of the uncertainty ( $1-\sigma$ ) in the corrections for the particular satellite. The value in this IE shall be multiplied by the UDRE Scale Factor in the common Corrections Status IE to determine the final UDRE estimate for the particular satellite. The meanings of the UDRE values are described in table 27. + +**Table 27: Values of UDRE** + +| Value | Indication | +|-------|-------------------------------------------| +| 00 | $UDRE \leq 1.0 \text{ m}$ | +| 01 | $1.0 \text{ m} < UDRE \leq 4.0 \text{ m}$ | +| 10 | $4.0 \text{ m} < UDRE \leq 8.0 \text{ m}$ | +| 11 | $8.0 \text{ m} < UDRE$ | + +Each UDRE value shall be adjusted based on the operation of an Integrity Monitor (IM) function which exists at the network (SMLC, GPS server, or reference GPS receiver itself). Positioning errors derived at the IM which are excessive relative to DGPS expected accuracy levels shall be used to scale the UDRE values to produce consistency. + +###### Pseudo-Range Correction (PRC) + +This IE indicates the correction to the pseudorange for the particular satellite at the reference time, $t_0$ . As mentioned above, this reference time is the GPS TOW. The value of this IE is given in meters (m) and the resolution is 1. The method of calculating this IE are described in RTCM-SC104. + +###### Pseudo-Range Rate Correction (RRC) + +This IE indicates the rate-of-change of the pseudorange correction for the particular satellite, using the satellite ephemeris identified by the IODE IE. The value of this IE is given in meters per second (m/sec) and the resolution is 0.032. For some time $t_1 > t_0$ , the corrections are estimated by: + +$$PRC(t_1, IODE) = PRC(t_0, IODE) + RRC(t_0, IODE) \cdot (t_1 - t_0),$$ + +and the MS uses this to correct the pseudorange it measures at $t_1$ , $PR_m(t_1)$ , by: + +$$PR(t_1, IODE) = PR_m(t_1, IODE) + PRC(t_1, IODE).$$ + +###### Delta Pseudo-Range Correction 2 (Delta PRC2) + +This IE indicates the difference in the pseudorange correction between the satellite's ephemeris identified by IODE and the previous ephemeris two issues ago IODE-2. The value of this IE is given in meters (m) and the resolution is 0.32. The method of calculating this IE are described in RTCM-SC104. + +###### Delta Pseudo-Range Rate Correction 2 (Delta RRC2) + +This IE indicates the difference in the pseudorange rate-of-change correction between the satellite's ephemeris identified by IODE and IODE-2. The value of this IE is given in meters per second (m/sec) and the resolution is 0.032. For some time $t_1 > t_0$ , the corrections for IODE-2 are estimated by: + +$$PRC(t_1, IODE-2) = [PRC(t_0, IODE) + DeltaPRC(t_0, IODE)] + [RRC(t_0, IODE) + DeltaRRC(t_0, IODE)] \cdot (t_1 - t_0);$$ + +and the MS uses this to correct the pseudorange it measures at $t_1$ using ephemeris IODE-2, $PR_m(t_1, IODE-2)$ , by: + +$$PR(t_1, IODE-2) = PR_m(t_1, IODE-2) + PRC(t_1, IODE-2).$$ + +If there is not an ephemeris set for a currently visible satellite that is two issues old, then the parameters Delta PRC2 and Delta RRC2 are both set to zero. + +#### 4.2.1.2 Ephemeris and Clock Correction Data + +This subclause describes the contents of the Data for ephemeris and clock corrections of a particular satellite. These IE fields are extracted from the subframes 1 to 3 of the GPS navigation message. They are listed in table 28. + +**Table 28: Ephemeris and Clock Correction Data (per-satellite fields - (1) = Positive range only)** + +| Parameter | Bits | Resolution | Range | Units | Occurrences | Presence | +|--------------------|-------------------|------------------|--------------------------|-----------------------|-------------|----------| +| Transmission TOW | 20 | 1 | 0 – 604799 | seconds | 1 | M | +| SVID/PRNID | 6 (1) | --- | 0 – 63 | --- | 1 | M | +| TLM Message | 14 | --- | 0 – 16383 | --- | 1 | M | +| TLM Reserved (C) | 2 | --- | 0 – 3 | --- | 1 | M | +| HOW | 22 | --- | 0 – 4194303 | --- | 1 | M | +| WN | 10 | --- | 0 – 1023 | weeks | 1 | M | +| C/A or P on L2 | 2 | --- | 0 – 3 | Boolean | 1 | M | +| URA Index | 4 | --- | 0 – 15 | Boolean | 1 | M | +| SV Health | 6 | --- | 0 – 63 | Boolean | 1 | M | +| IODC | 10 (1) | --- | 0 – 1023 | --- | 1 | M | +| L2 P Data Flag | 1 | --- | 0 – 1 | Boolean | 1 | M | +| SF1 Reserved | 87 | --- | Full Range | --- | 1 | M | +| T GD | 8 | 2 -31 | -128 – 127 | seconds | 1 | M | +| t oc | 16 (1) | 2 4 | 0 – 604784 | seconds | 1 | M | +| Af 2 | 8 | 2 -55 | -128 – 127 | sec/sec 2 | 1 | M | +| Af 1 | 16 | 2 -43 | -32768 – 32767 | sec/sec | 1 | M | +| Af 0 | 22 | 2 -31 | -2097152 – 2097151 | seconds | 1 | M | +| C rs | 16 | 2 -5 | -32768 – 32767 | meters | 1 | M | +| Δn | 16 | 2 -43 | -32768 – 32767 | semi-circles/sec | 1 | M | +| M 0 | 32 | 2 -31 | -2147483648 – 2147483647 | semi-circles | 1 | M | +| C uc | 16 | 2 -5 | -32768 – 32767 | meters | 1 | M | +| E | 32 (1) | 2 -33 | 0 – 4294967295 | --- | 1 | M | +| C us | 16 | 2 -29 | -32768 – 32767 | radius | 1 | M | +| (A) 1/2 | 32 (1) | 2 -19 | 0 – 4294967295 | meters 1/2 | 1 | M | +| t oe | 16 (1) | 2 4 | 0 – 604784 | seconds | 1 | M | +| Fit Interval Flag | 1 | --- | 0 – 1 | Boolean | 1 | M | +| AODO | 5 | 900 | 0 – 31 | seconds | 1 | M | +| C ic | 16 | 2 -29 | -32768 – 32767 | radians | 1 | M | +| OMEGA 0 | 32 | 2 -31 | -2147483648 – 2147483647 | semi-circles | 1 | M | +| C is | 16 | 2 -29 | -32768 – 32767 | radians | 1 | M | +| i 0 | 32 | 2 -31 | -2147483648 – 2147483647 | semi-circles | 1 | M | +| C rc | 16 | 2 -29 | -32768 – 32767 | meters | 1 | M | +| ω | 32 | 2 -31 | -2147483648 – 2147483647 | semi-circles | 1 | M | +| OMEGAdot | 24 | 2 -43 | -8388608 – 8388607 | Semi-circles/sec | 1 | M | +| ldot | 14 | 2 -43 | -8192 – 8191 | Semi-circles/sec | 1 | M | +| Spares/zero fill | 20 | --- | --- | --- | 1 | M | + +##### **Transmission TOW** + +This field indicates the approximate GPS time-of-week when the message is broadcast. The MS should interpret this field as a very coarse estimate of the current time. + +##### **SVID/PRNID** + +The satellite ID of the data from which this signal was obtained. + +##### **Rest of Fields** + +The rest of fields are defined as in figure 20-1 of ICD-GPS-200. + +#### 4.2.1.3 Almanac and Other Data + +This subclause describes the contents of the Data for ionospheric delay, UTC offset, and Almanac. These IE fields are extracted from the subframes 4 and 5 of the GPS navigation message, excluding the parity bits and other redundant bits. They are listed in table 29. + +**Table 29: Almanac and Other Data** + +| Parameter | Bits | Resolution | Range | Occurrences | Presence | +|------------------|------|------------|------------|------------------------------------------------------------------------------------------|----------| +| Transmission TOW | 20 | 1 | 0 - 604799 | 1 | M | +| SV Mask | 32 | --- | --- | 1 | M | +| LSB TOW | 8 | 1 | 0 - 255 | 1 | M | +| SFID 0 | 1 | 1 | 0 - 1 | Repeat three times:
Each corresponds to a different page no. as described in table 29 | M | +| Data ID | 2 | --- | --- | | | +| Page No. | 6 | 1 | 1 - 25 | | | +| Word 3 | 16 | COSP | COSP | | | +| Word 4 | 24 | COSP | COSP | | | +| Word 5 | 24 | COSP | COSP | | | +| Word 6 | 24 | COSP | COSP | | | +| Word 7 | 24 | COSP | COSP | | | +| Word 8 | 24 | COSP | COSP | | | +| Word 9 | 24 | COSP | COSP | | | +| Word 10 | 22 | COSP | COSP | | | +| Spares/zero fill | 5 | --- | --- | 1 | M | + +##### Transmission TOW + +This field indicates the approximate GPS time-of-week when the message is broadcast. The MS should interpret this field as a very coarse estimate of the current time. + +##### SV Mask + +This field indicates the satellites that contain the pages being broadcast in this data set. + +##### LSB TOW + +This field indicates the least significant 8 bits of the TOW. See ICD-GPS-200, figure 20-2. + +##### COSP + +Format Conditional on Subframe ID and Page Number. See ICD-GPS-200, subclause 20.3.3.5, figure 20-1. + +###### SFID 0 + +This one bit field conveys the least significant bit of the SubFrame(SF) ID for which the following word 3 through word 10 data applies. Zero indicates subframe ID = 4, and One indicates Subframe ID = 5. + +###### Data ID + +Indicates the Data ID field contained in the indicated subframe, word 3, most significant 2 bits, as defined by ICD-GPS-200. + +###### Page No. + +Six-bit field indicates the Page ID of the indicated subframe for which the following Word 3 through Word 10 data applies. The page field and SFID field define the data content and format for the following word 3 through word 10 data fields as defined by ICD-GPS-200. + +###### Word 3 through Word 10 + +Information bits (16, 22 or 24) that are contained in the respective words of the indicated subframe and page, excluding 2 bit "t" from Word 10. See reference ICD-GPS-200 for more information. + +Each broadcast Almanac and Other Data message contains three subframes of information. All three of subframe pages in this data set can be from the same subframe ID (all from subframe 5 for example), or a mixed set containing some subframe 4 and some subframe 5 data. + +Table 29 shows the subframe and page numbers corresponding to the Almanac, SV Health, and Iono / UTC Correction data. A total of 35 subframes must be broadcast if all the information is to be provided to the MS. Given that three subframes worth of content can be delivered per broadcast message, it will take only 12 broadcast messages to deliver the entire data set shown in table 29. If the data listed in table 29 is broadcast at the rate of approximately once per four hours, one Almanac and Other Data message must be broadcast on average every 20 minutes. An alternate approach is to broadcast the 12 messages as a set closely together in time, but with four-hour duration between sets. Note that the four-hour figure is only used to illustrate the concept, and a shorter or longer period may be used instead. + +It is possible to broadcast other data contained in Subframes 4 and/or 5 not shown in table 29. The format of the message remains the same, only the particular page of the desired data needs to be set properly. The contents of words 3 through 10 also need to be set as described in ICD-GPS-200. Using this format, it provides maximum compatibility for future expansion to include other data in subframes 4 and 5 not shown in table 30 or ICD-GPS-200. + +**Table 30: Mapping of Almanac, Health, Iono, and UTC Data to Subframe Number and Page Number** + +| Data Type | Subframe | Page(s) | +|--------------------------|-----------------|-------------------------| +| Almanac Data (SV1 – 24) | 5 | 1 - 24 | +| Almanac Data (SV25 – 32) | 4 | 2, 3, 4, 5, 7, 8, 9, 10 | +| SV Health (SV1 – 24) | 5 | 25 | +| SV Health (SV25 – 32) | 4 | 25 | +| Iono/UTC Corrections | 4 | 18 | + +# Annex A (informative): Overview of Broadcast Assistance for E-OTD and GPS + +This annex presents an overview of the functionality and requirements for broadcasting assistance information for GPS and E-OTD in GSM networks. Potential impacts to other services are also described. + +## A.1 General + +The E-OTD and GPS assistance information may be broadcast over the SMSCB service. The SMSCB DRX service is used to forecast the occurrences of the broadcast messages. The E-OTD and GPS broadcasts are independent of each other, have own SMSCB message identifiers and are broadcast on the demand of the characteristics of the E-OTD and GPS. In the network side, the SMLC is responsible for gathering the information, constructing the broadcast messages and ciphering a part of the message, if necessary. The SMLC also maintains the deciphering keys that MS requests with MO-LR. The deciphering keys are location area specific. + +SMSCB messages can be received when MS is in idle mode. When MS is in dedicated mode the same information that was received in idle mode via broadcast channel may be requested by MS via point-to-point messaging. + +## A.2 E-OTD Assistance Broadcast + +The information that is broadcast for E-OTD assistance is used in MS-based E-OTD to help the MS measure neighbour BTSs and compute its own position. The broadcast message is built so that it has always a fixed length of 82 octets, which is the size of one SMS Cell Broadcast (SMSCB) message. The information elements are scalable according to the number of neighbour BTSs and the amount of sectorized channels. + +In general, the following information is included in a broadcast E-OTD assistance message: + +- Reference Time. +- Neighbour Channel Time Slot Scheme. +- Information about sectorized neighbour channels. +- Neighbour channel 51 Multiframe Offset values. +- Neighbour channel BCC values. +- RTD Drift Factor values (ciphered if active). +- Neighbour channel RTD values (ciphered if active). +- Serving cell and neighbour cell location information (ciphered if active). + +The system information message that is received in idle mode contains the neighbour channel information. The E-OTD SMSCB message refers to this system information neighbour list so that there is indication which neighbours in the system information neighbour list are included in the broadcast message. The neighbour channel RTD values, serving cell location and neighbour cell location information may be ciphered. + +Based on the information in the broadcast message and the E-OTD measurements done by MS, MS is capable to calculate its position. MS that is not capable to calculate its position itself may receive the SMSCB messages and use the unciphered contents to help the synchronization to the neighbour channels. + +Most information contained in the E-OTD broadcast message is static. However, the RTD values change relatively often due to the drift in unsynchronized BTS clocks. The duration of validity of RTD values will affect the location accuracy calculated by MS. The RTD update rate is a function of BTS clock stability and required location accuracy from the operator and may be specified by the operator. + +## A.3 GPS Assistance Broadcast + +### Broadcast DGPS Data + +The main content of the broadcast message for GPS assistance is DGPS corrections. This information is used in MS-based GPS positioning to improve the accuracy of the position result. Some background information for DGPS broadcast is presented in this subclause. Requirements on the GSM network for broadcasting DGPS corrections are also discussed. + +In good signal environments, the primary determinant of position accuracy for GPS is the intentional degradation of the GPS satellite clocks, known as *selective availability* (SA). Another contributor to the error budget is unmodeled atmospheric delay. The techniques used to correct these error sources are collectively known as *differential GPS* (DGPS). These methods involve locating one or more reference receivers at known locations and observing the visible satellite signals. These receivers essentially solve the inverse GPS problem - find differences from the expected measurements at the known position. The accuracy of the DGPS corrections is inversely proportional to the distance from the reference location. The inaccuracy is caused by changes in the geometry and visibility of the satellite constellation. For most applications, however, the corrections are valid for receivers within a 200 km to 400 km radius of the reference station. + +One noteworthy characteristic of the DGPS corrections is that they have a short time constant compared to other GPS information such as satellite ephemeris. Once a correction model is computed, its accuracy degrades over time. This is mainly due to the time-varying nature of the SA imposed on the satellite signals. The duration of validity of a set of differential corrections depends on the accuracy requirements of the user or application, but in general the corrections must be updated at least every 30 s. + +The fact that DGPS corrections are valid for large areas but require frequent update make them very suitable for delivery over a GSM broadcast channel such as SMSCB. This broadcast strategy is used by other DGPS sources, such as FM broadcast stations and geostationary satellites (WAAS, EGNOS, and MSAS). However, broadcasting the DGPS corrections in the GSM network has a clear advantage over other sources. This is mainly due to the fact that GSM broadcast exploits the existing reliable data link between the GPS-capable MS and the GSM network. In the other methods, the MS must capture the DGPS information from another source and therefore pays a price in power consumption, complexity, or both. + +The format used for GSM broadcast of DGPS corrections includes a list of satellites visible at a nearby reference location, the correction in the range measurement for each satellite, and the rate-of-change of the range correction. In addition, an allowance is made for adding correction differences (i.e. $\Delta$ PRC and $\Delta$ RRC values) for multiple copies of the GPS ephemeris, to reduce the network traffic flow. Other information includes satellite health status and a reference GPS time for the corrections. The total amount of DGPS information is 48 bits (6 octets) per satellite with 80 bits (10 octets) of overhead information. The total message size for 12 visible satellites is 82 octets, which will fit within a single SMSCB message. + +### **Broadcast Other Data** + +The contents of the other broadcast GPS Assistance Message data sets are ephemeris and clock correction, as well as almanac and other data. This information can be used by the GPS receiver integrated with MS to improve the signal acquisition time and sensitivity, to recover GPS time and to obtain Ephemeris, clock correction, UTC offset, Ionospheric delay, and Almanac data. For example, the ephemeris data set may be broadcast every 90 s, and Almanac may be broadcast once every several hours. The mobile station which does not require E-OTD and/or DGPS assistance can wake up at 90 s intervals, download these data, and then go back to sleep. This broadcast message can assist mobile station in idle mode to acquire GPS satellites with improved sensitivity and perform GPS time recovery without point-to-point communication, therefore improving the time to the first fix and reducing the point-to-point message traffic. The message can be provided within a single SMSCB message. + +## **A.4 Impact on Other Services** + +### *Latency* + +The main impact is due to latency requirements for delivery of the DGPS and E-OTD assistance information. Both the DGPS corrections and the RTD values are valid for relatively short periods of time, and must be delivered in a timely manner. Thus, the service is sensitive to delays such as buffering broadcast SMSCB messages. The Reference Time in the broadcast messages and the drift factors can be used to compensate latency. + +The Ephemeris and Clock Correction data set needs to be broadcast once every 90 s. The period for broadcasting the data set is chosen to provide the entire ephemeris (three subframes) in a reasonable amount of time. For 8 satellites, it would take 12 minutes. The Almanac and Other Data data set can be broadcast every several hours. To deliver the entire data set within 6 minutes, 12 broadcasts with a 30 s rate are required. It can also be broadcast at a much slower rate. For instance, for a 20 minute rate, the data set can be delivered to the mobile station every 4 hours. + +### Capacity + +The SMSCB used for LCS uses the basic CBCH or extended CBCH. The support of E-OTD and/or DGPS broadcast needs capacity related to broadcast message characteristics (RTD/DGPS validity). The SMSCB DRX service also needs to schedule a message that is sent once per schedule period. The maximum schedule period is 48 SMSCB message slots. + +Example of capacity scenario: + +- The basic CBCH uses the same physical resource as SDCCH/4 (sub channel 2) or SDCCH/8 (sub channel 2). If SMSCB service is supported in basic CBCH it occupies 1/4 of SDCCH capacity when using SDCCH/4 and 1/8 of SDCCH capacity when using SDCCH/8. +- The basic CBCH capacity is 1 SMSCB message per 2 s. +- Both DGPS and E-OTD broadcast is assumed to be once per 30 s and the Ephemeris and Almanac messages are assumed to be once per 90 s or longer (capacity is 15 SMSCB messages per 30 s). +- Schedule period is 45 (= 45 x 2 s = 90 s). If SMSCB DRX service is used for other services in SMSCB, the one SMSCB DRX schedule message per schedule period is needed to support all services: +=> LCS needs $2/15 + 1/45$ of SMSCB capacity plus one schedule message every 90 s for delivering assistance data for both E-OTD and GPS methods. + +# --- Annex B (informative): Example of E-OTD Assistance Data Broadcast Message + +This example describes how the message is built when following neighbour cell information is enclosed into SMSCB broadcast message: + +- All neighbours (1-19) from System Information Neighbour List is included into one broadcast message. +- The neighbours 1, 2, 3, 7, 8, 9, 11, 12, 13, 16, 17 and 19 are belonging to sectorized BTS and following channels are in the same groups: (1, 2, 3), (7, 8, 9), (11, 12, 13) and (16, 17, 19). Serving cell channel is not belonging to sectorized BTS. +- The channels belonging to sectorized BTS are synchronized. +- The accuracy range is 15 km, and ciphering is active. +- The 51 Multiframe Value is included, the RTD range is 1 time slot and the RTD accuracy in 1/32 bit. +- BTS network is not synchronized. +- RTD Drift Factors are not included into message. + +NOTE: There are 15 remain bits for Relative Location Values and the 15 bits are used for Relative North or East extention bits. These bits are added to Nb18 North, Nb18 East, Nb15 North, Nb15 East, Nb14 North, Nb14 East, Nb10 North, Nb10 East, Nb6 North, Nb6 East, Nb5 North, Nb5 East, Nb4 North, Nb4 East and ID4 North.. These have 8 bits and the rest have 7 bits for relative location value. + + + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | +|---------------------------------------------------------------|----------------------------------|----------------------------|--------------------------------------------------|---------------------------------|--------------|----------------------------|--------------------------------------|---------|--|--|--|--|--|--|--|--|--| +| Cipher On (1) | Cipher Key Ind (0) | Accuracy Range MSB(010)LSB | | All Neighbours MSB(000)LSB | | | | Octet1 | | | | | | | | | | +| Number of Neigh MSB(11) | | RTDs Present (1) | RTD Drift Factors Present (0) | RTD Accuracy MSB(01)LSB | | RTD Range (1) | Sector Ind On (1) | Octet2 | | | | | | | | | | +| Reference Time (MSB, bits 9-5) | | | | Number of Neigh (001)LSB | | | | Octet3 | | | | | | | | | | +| Ciphering Serial Number (MSB, bits 15-13) | | | Reference Time (LSB, bits 4-0) | | | | | Octet4 | | | | | | | | | | +| Ciphering Serial Number (bits 12-5) | | | | | | | | Octet5 | | | | | | | | | | +| Time Slot Scheme Serv Cell (MSB)& Nb 19-18 | | | Ciphering Serial Number (bits 4-0, LSB) | | | | | Octet6 | | | | | | | | | | +| Time Slot Scheme Nb 17-10 | | | | | | | | Octet7 | | | | | | | | | | +| Time Slot Scheme Nb 9-2 | | | | | | | | Octet8 | | | | | | | | | | +| Sectorized Channels Serv Cell & Nb 19-14 (0101100) | | | | | | | Time Slot Scheme Nb 1 LSB | Octet9 | | | | | | | | | | +| Sectorized Channels Nb 13-6 (11101110) | | | | | | | | Octet10 | | | | | | | | | | +| Sec Ch BTS ID4 Nb19 MSB(011)LSB | | | Sectorized Channels Nb 5-1 (00111)LSB | | | | | Octet11 | | | | | | | | | | +| Sec Ch BTS ID3 Nb13 MSB(01) | Sec Ch BTS ID4 Nb16 MSB(011)LSB | | | Sec Ch BTS ID4 Nb17 MSB(011)LSB | | | | Octet12 | | | | | | | | | | +| Sec Ch BTS ID2 Nb9 MSB(0) | Sec Ch BTS ID3 Nb11 MSB(010)LSB | | Sec Ch BTS ID3 Nb12 MSB(010)LSB | | | Sec Ch BTS ID3 (0)LSB | | Octet13 | | | | | | | | | | +| Sec Ch BTS ID2 Nb7 MSB(001)LSB | | | Sec Ch BTS ID2 Nb8 MSB(001)LSB | | | Sec Ch BTS ID2 Nb9 (01)LSB | | Octet14 | | | | | | | | | | +| Sec Ch BTS ID1 Nb1 MSB(00) | Sec Ch BTS ID1 Nb2 MSB(000)LSB | | | Sec Ch BTS ID1 Nb3 MSB(000)LSB | | | | Octet15 | | | | | | | | | | +| 51MF Offset Value Nb19 (MSB) | | | Sync ID1 (1) | Sync ID2 (1) | Sync ID3 (1) | Sync ID4 (1) | Sec Ch BTS ID1 Nb1 (0)LSB | Octet16 | | | | | | | | | | +| 51MF Offset Value Nb18 (MSB) | | | | 51MF Offset Value Nb19 (LSB) | | | | Octet17 | | | | | | | | | | +| 51MF Offset Value Nb16 (MSB) | 51MF Offset Value Nb17 (MSB LSB) | | | | | | 51MF Offset Value Nb18 (LSB) | Octet18 | | | | | | | | | | +| 51MF Offset Value Nb15 (MSB) | | | 51MF Offset Value Nb16 (LSB) | | | | | Octet19 | | | | | | | | | | +| 51MF Offset Value Nb14 (MSB) | | | | 51MF Offset Value Nb15 (LSB) | | | | Octet20 | | | | | | | | | | +| 51MF Offset Value Nb12 (MSB) | 51MF Offset Value Nb13 (MSB LSB) | | | | | | 51MF Offset Value Nb14 (LSB) | Octet21 | | | | | | | | | | +| 51MF Offset Value Nb11 (MSB) | | | 51MF Offset Value Nb12 (LSB) | | | | | Octet22 | | | | | | | | | | +| 51MF Offset Value Nb10 (MSB) | | | | 51MF Offset Value Nb11 (LSB) | | | | Octet23 | | | | | | | | | | +| 51MF Offset Value Nb8 (MSB) | 51MF Offset Value Nb9 (MSB LSB) | | | | | | 51MF Offset Value Nb10 (LSB) | Octet24 | | | | | | | | | | +| 51MF Offset Value Nb7 (MSB) | | | 51MF Offset Value Nb8 (LSB) | | | | | Octet25 | | | | | | | | | | +| 51MF Offset Value Nb6 (MSB) | | | | 51MF Offset Value Nb7 (LSB) | | | | Octet26 | | | | | | | | | | +| 51MF Offset Value Nb4 (MSB) | 51MF Offset Value Nb5 (MSB LSB) | | | | | | 51MF Offset Value Nb6 (LSB) | Octet27 | | | | | | | | | | +| 51MF Offset Value Nb3 (MSB) | | | 51MF Offset Value Nb4 (LSB) | | | | | Octet28 | | | | | | | | | | + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | +|-----------------------------|---------------------------------|--------------------|---------------------|-----------------------------|----------------------|---------------------|-----------------------------|---------|--|--|--|--|--|--|--|--|--|--| +| 51MF Offset Value Nb2 (MSB) | | | | 51MF Offset Value Nb3 (LSB) | | | | Octet29 | | | | | | | | | | | +| BCC Nb19 (MSB) | 51MF Offset Value Nb1 (MSB LSB) | | | | | | 51MF Offset Value Nb2 (LSB) | Octet30 | | | | | | | | | | | +| BCC Nb17 (MSB LSB) | | | BCC Nb18 (MSB LSB) | | | BCC Nb19 (LSB) | | Octet31 | | | | | | | | | | | +| BCC Nb14 (MSB) | | BCC Nb15 (MSB LSB) | | BCC Nb16 (MSB LSB) | | | | Octet32 | | | | | | | | | | | +| BCC Nb11 (MSB) | BCC Nb12 (MSB LSB) | | BCC Nb13 (MSB LSB) | | | | BCC Nb14 (LSB) | Octet33 | | | | | | | | | | | +| BCC Nb9 (MSB LSB) | | | BCC Nb10 (MSB LSB) | | | BCC Nb11 (LSB) | | Octet34 | | | | | | | | | | | +| BCC Nb6 (MSB) | | BCC Nb7 (MSB LSB) | | BCC Nb8 (MSB LSB) | | | | Octet35 | | | | | | | | | | | +| BCC Nb3 (MSB) | BCC Nb4 (MSB LSB) | | BCC Nb5 (MSB LSB) | | | | BCC Nb6 (LSB) | Octet36 | | | | | | | | | | | +| BCC Nb1 (MSB LSB) | | | BCC Nb2 (MSB LSB) | | | BCC Nb3 (LSB) | | Octet37 | | | | | | | | | | | +| RTD Value Nb18 (MSB) | | | | | | | | Octet38 | | | | | | | | | | | +| RTD Value Nb15 (MSB) | | | RTD Nb18 (LSB) | | | | | Octet39 | | | | | | | | | | | +| RTD Value Nb15 | | | | | | | | Octet40 | | | | | | | | | | | +| RTD Value Nb14 (MSB) | | | | | RTD Value Nb15 (LSB) | | | Octet41 | | | | | | | | | | | +| RTD Value Nb10 (MSB) | RTD Value Nb14 (LSB) | | | | | | | Octet42 | | | | | | | | | | | +| RTD Value Nb10 | | | | | | | | Octet43 | | | | | | | | | | | +| RTD Value Nb6 (MSB) | | | | RTD Value Nb10 (LSB) | | | | Octet44 | | | | | | | | | | | +| RTD Value Nb6 | | | | | | | | Octet45 | | | | | | | | | | | +| RTD Value Nb5 (MSB) | | | | | | RTD Value Nb6 (LSB) | | Octet46 | | | | | | | | | | | +| RTD Value Nb4 (MSB) | RTD Value Nb5 (LSB) | | | | | | | Octet47 | | | | | | | | | | | +| RTD Value Nb4 | | | | | | | | Octet48 | | | | | | | | | | | +| RTD Value ID4 (MSB) | | | | RTD Value Nb4 (LSB) | | | | Octet49 | | | | | | | | | | | +| RTD Value ID4 (LSB) | | | | | | | | Octet50 | | | | | | | | | | | +| RTD value ID3 (MSB) | | | | | | | | Octet51 | | | | | | | | | | | +| RTD Value ID2 (MSB) | | | RTD Value ID3 (LSB) | | | | | Octet52 | | | | | | | | | | | +| RTD Value ID2 | | | | | | | | Octet53 | | | | | | | | | | | +| RTD Value ID1 (MSB) | | | | | RTD Value ID2 (LSB) | | | Octet54 | | | | | | | | | | | +| Serv Cell Lat (MSB) | RTD Value ID1 (LSB) | | | | | | | Octet55 | | | | | | | | | | | +| Serv Cell Lat | | | | | | | | Octet56 | | | | | | | | | | | +| Serv Cell Lat | | | | | | | | Octet57 | | | | | | | | | | | +| Serv Cell Long (MSB) | Serv Cell Lat (LSB) | | | | | | | Octet58 | | | | | | | | | | | +| Serv Cell Long | | | | | | | | Octet59 | | | | | | | | | | | +| Serv Cell Long | | | | | | | | Octet60 | | | | | | | | | | | +| Rel North Nb18 (MSB) | Serv Cell Long (LSB) | | | | | | | Octet61 | | | | | | | | | | | + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|----------------------|---------------------|--------------------|---------------------|--------------------|---|---------------------|---------| +| Rel East Nb18 (MSB) | Rel North Nb18 (LSB) | | | | | | | Octet62 | +| Rel North Nb15 (MSB) | Rel East Nb18 (LSB) | | | | | | | Octet63 | +| Rel East Nb15 (MSB) | Rel North Nb15 (LSB) | | | | | | | Octet64 | +| Rel North Nb14 (MSB) | Rel East Nb15 (LSB) | | | | | | | Octet65 | +| Rel East Nb14 (MSB) | Rel North Nb14 (LSB) | | | | | | | Octet66 | +| Rel North Nb10 (MSB) | Rel East Nb14 (LSB) | | | | | | | Octet67 | +| Rel East Nb10 (MSB) | Rel North Nb10 (LSB) | | | | | | | Octet68 | +| Rel North Nb6 (MSB) | Rel East Nb10 (LSB) | | | | | | | Octet69 | +| Rel East Nb6 (MSB) | Rel North Nb6 (LSB) | | | | | | | Octet70 | +| Rel North Nb5 (MSB) | Rel East Nb6 (LSB) | | | | | | | Octet71 | +| Rel East Nb5 (MSB) | Rel North Nb5 (LSB) | | | | | | | Octet72 | +| Rel North Nb4 (MSB) | Rel East Nb5 (LSB) | | | | | | | Octet73 | +| Rel East Nb4 (MSB) | Rel North Nb4 (LSB) | | | | | | | Octet74 | +| Rel North ID4 (MSB) | Rel East Nb4 (LSB) | | | | | | | Octet75 | +| Rel East ID4 (MSB) | Rel North ID4 (LSB) | | | | | | | Octet76 | +| Rel North ID3 (MSB) | Rel East ID4 (LSB) | | | | | | | Octet77 | +| Rel East ID3 (MSB) | | Rel North ID3 (LSB) | | | | | | Octet78 | +| Rel North ID2 (MSB) | | | Rel East ID3 (LSB) | | | | | Octet79 | +| Rel East ID2 (MSB) | | | | Rel North ID2 (LSB) | | | | Octet80 | +| Rel North ID1 (MSB) | | | | | Rel East ID2 (LSB) | | | Octet81 | +| Rel East ID1 (MSB LSB) | | | | | | | Rel North ID1 (LSB) | Octet82 | + +# Annex C (informative): Example of GPS Assistance Data Broadcast Message + +This annex gives an example of how the information IE should be packed into the GPS Assistance Data message. The example shown in table C.1 includes corrections for 12 satellites. + +**Table C.1: Example of a GPS Assistance Data (DGPS Correction) message with 11 satellites** + +| Octet | MSB | | | LSB | | | +|-------|---------------------------------------------------|-----------------|----------------------------------------------------------|----------------------------------|--|--| +| 1 | Cipher On/Off | Cipher Key Flag | Ciphering Serial Number (MSB, bits 15-10)
or
Spare | | | | +| 2 | Ciphering Serial Number (bits 9-2)
or
Spare | | | | | | +| 3 | BTS Clock Drift (bits 3-0)
or
Spare | | BTS Clock Drift Present | GSM Time Present | | | +| 4 | Reference Location | | | | | | +| ... | | | | | | | +| 9 | Reference Location | | | | | | +| 10 | FN (MSB bits 17-10)
or
Spare | | | | | | +| 11 | FN (bits 9-2)
or
Spare | | | | | | +| 12 | BN (MSB bits 7 - 5)
or
Spare | | TN (bits 3-0)
or
Spare | FN (LSB bits 1-0)
or
Spare | | | +| 13 | GPS TOW (MSB bits 19-17)
or
Spare | | BN (LSB bits 4 - 0)
or
Spare | | | | +| 14 | GPS TOW (bits 16-9) | | | | | | +| 15 | GPS TOW (bits 8-1) | | | | | | +| 16 | N_SAT (bits 3-0) | | Correction Status/Health (bits 2-0) | GPS TOW (LSB bit0) | | | +| 17 | Satellite ID (Sat 1) | | | UDRE (Sat 1) | | | +| 18 | IODE (Sat 1) | | | | | | +| 19 | PRC (Sat 1 – MSBs, 7 – 0) | | | | | | +| 20 | PRC (Sat 1 – MSBs, 7 – 4) | | RRC (Sat 1 – LSBs, 3-0) | | | | +| 21 | RRC (Sat 1 – LSBs, 7 – 4) | | Delta PRC (Sat 1 - LSBs, 3-0) | | | | +| 22 | Delta PRC (Sat 1 - MSBs, 7 – 4) | | Delta RRC (Sat 1) | | | | +| ... | | | | | | | +| 77 | Satellite ID (Sat 12) | | | UDRE (Sat 12) | | | +| 78 | IODE (Sat 12) | | | | | | +| 79 | PRC (Sat 12 – MSBs, 7 – 0) | | | | | | +| 80 | PRC (Sat 12 – MSBs, 7 – 4) | | RRC (Sat 12 – LSBs, 3-0) | | | | +| 81 | RRC (Sat 12– LSBs, 7 – 4) | | Delta PRC (Sat 12 - LSBs, 3-0) | | | | +| 82 | Delta PRC (Sat 12 – MSBs, 7 – 4) | | Delta RRC (Sat 12) | | | | + +# Annex D (informative): Change History + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-01 | | | - | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44056/0779125369ae9c0108101b54fe2428bf_img.jpg b/marked/Rel-16/44_series/44056/0779125369ae9c0108101b54fe2428bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60aea773391b5c5f71d4af5f7badc1afa1bb31a9 --- /dev/null +++ b/marked/Rel-16/44_series/44056/0779125369ae9c0108101b54fe2428bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:204ee7a7bd33daf103b5ef721f8e10501f8e860bbdc274423c9c1b29eb70c2e9 +size 21782 diff --git a/marked/Rel-16/44_series/44056/0908107b858fa3783d10d93b3a3444b2_img.jpg b/marked/Rel-16/44_series/44056/0908107b858fa3783d10d93b3a3444b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e2860ff4608ef3b5132460cc86583d8ff28727d --- /dev/null +++ b/marked/Rel-16/44_series/44056/0908107b858fa3783d10d93b3a3444b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e28c77446ddb3b6a5f3bf1f3849c09d5435cdeda64538129246006ed23f05b32 +size 37997 diff --git a/marked/Rel-16/44_series/44056/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/44_series/44056/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fc77f393bc307ee04b7bb862111caa59f4e8292 --- /dev/null +++ b/marked/Rel-16/44_series/44056/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6466206c5413f520646e3c2aa8f3ab12a289da5cc102c4050f4ffc71d299b784 +size 78558 diff --git a/marked/Rel-16/44_series/44056/0adcd19063a66145a465add40bf956e6_img.jpg b/marked/Rel-16/44_series/44056/0adcd19063a66145a465add40bf956e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63f05d3682731d901b205ef537b6ca7d4be74e47 --- /dev/null +++ b/marked/Rel-16/44_series/44056/0adcd19063a66145a465add40bf956e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fdc285b21fb97e8d31cdf952f02a6a596da4a64cbcef8b41eb961b2549c05ef +size 22424 diff --git a/marked/Rel-16/44_series/44056/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-16/44_series/44056/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..506a463e079a9c8bd47a96bca8ac60e7641de800 --- /dev/null +++ b/marked/Rel-16/44_series/44056/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fce2b9a4a6c8704884cc452538eb8c9abd43cc6fd2fce9430adca406423790d +size 92852 diff --git a/marked/Rel-16/44_series/44056/0d9b44054c70dcda35129f11b97a912f_img.jpg b/marked/Rel-16/44_series/44056/0d9b44054c70dcda35129f11b97a912f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6447a18064e94db742991d483987e4afb6fb44b1 --- /dev/null +++ b/marked/Rel-16/44_series/44056/0d9b44054c70dcda35129f11b97a912f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9edd95fe927a54217e2f0404b290d2a0f4125fbf89b0c1642775d4f602a44d75 +size 53300 diff --git a/marked/Rel-16/44_series/44056/11fc7b58448f884cac1a5481f7def5dc_img.jpg b/marked/Rel-16/44_series/44056/11fc7b58448f884cac1a5481f7def5dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b02b9fe8fbe6d5759bc9d073a16a4bf72d225e69 --- /dev/null +++ b/marked/Rel-16/44_series/44056/11fc7b58448f884cac1a5481f7def5dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee148044c04b0988cabc767f01a895165872b9960ae9e3dad317650dfab47b0a +size 23282 diff --git a/marked/Rel-16/44_series/44056/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg b/marked/Rel-16/44_series/44056/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e81b165470eae3ccda817e63d776cb56fc0821a1 --- /dev/null +++ b/marked/Rel-16/44_series/44056/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b1ec2feac034cd8cb51c5824f326c79dcedf1bad9309aadcede02a7b664067d +size 27061 diff --git a/marked/Rel-16/44_series/44056/24a27d17656bcf0ee131539f2bbb34cd_img.jpg b/marked/Rel-16/44_series/44056/24a27d17656bcf0ee131539f2bbb34cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..014fe5fea8d87880a3d0f831a8ca2a61d2f95bfd --- /dev/null +++ b/marked/Rel-16/44_series/44056/24a27d17656bcf0ee131539f2bbb34cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70a1d778ca12358b7bad283ad99ebb93394643c783a7e27c3586aa84694a3103 +size 51964 diff --git a/marked/Rel-16/44_series/44056/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/44_series/44056/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8453bf1e073edc4308acc00a775ef0c9309a6b8 --- /dev/null +++ b/marked/Rel-16/44_series/44056/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57a3ca17531cf93f57223b68e4c7a19cd8d7d28c77655e90818921b1a2afd5e1 +size 33337 diff --git a/marked/Rel-16/44_series/44056/34e9ca4d52796527c375f4bc187080f8_img.jpg b/marked/Rel-16/44_series/44056/34e9ca4d52796527c375f4bc187080f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ca5afd56eb06625c06145d0b4e5b491bb883dcb --- /dev/null +++ b/marked/Rel-16/44_series/44056/34e9ca4d52796527c375f4bc187080f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd0bbae65097433b9603a7bc3f1d2d182143b7420e7a96b5f40b6c1224fd31ae +size 32281 diff --git a/marked/Rel-16/44_series/44056/3621e1493d508bd789fec58ba8be9a40_img.jpg b/marked/Rel-16/44_series/44056/3621e1493d508bd789fec58ba8be9a40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7402587fc6c46401c2b8eaf13e4f9eeb5f8b1eca --- /dev/null +++ b/marked/Rel-16/44_series/44056/3621e1493d508bd789fec58ba8be9a40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b268ac1950673ced2d8bd676c47c1ee817fcf627f5363695535343da320c9af7 +size 8820 diff --git a/marked/Rel-16/44_series/44056/42f0611a8a2766c986ff45551918ca5d_img.jpg b/marked/Rel-16/44_series/44056/42f0611a8a2766c986ff45551918ca5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdb0ff0db8d0701dc1854113b6f313e2bab8a6a9 --- /dev/null +++ b/marked/Rel-16/44_series/44056/42f0611a8a2766c986ff45551918ca5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89468de1583fabf8906b24a34ac4bf5c0e6442c1b08fd9fcdc18cd1db9a07ca7 +size 37469 diff --git a/marked/Rel-16/44_series/44056/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-16/44_series/44056/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c04796d0a0c42d887002118e4633b5273cfbbfa3 --- /dev/null +++ b/marked/Rel-16/44_series/44056/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d30d7bdfeada84b4c4f7968926b7547ee870facfdaef393f136fe06edc3a1f48 +size 21559 diff --git a/marked/Rel-16/44_series/44056/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/44_series/44056/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f7889079b4ffead1d59924e5b4f8fc51c21064a --- /dev/null +++ b/marked/Rel-16/44_series/44056/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ede83bbfe81ecec9e8655a65b744454cc4362143374f6fa0a779ac53147bce3 +size 12697 diff --git a/marked/Rel-16/44_series/44056/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/marked/Rel-16/44_series/44056/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30924a49e26b30bc09a2cf62a62986d9a475a917 --- /dev/null +++ b/marked/Rel-16/44_series/44056/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68aad85eb687ad35d6b9040e6aacf2b20de1c7016964bc14c0414c52b3bc8cba +size 10474 diff --git a/marked/Rel-16/44_series/44056/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-16/44_series/44056/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c548cc4fc201848f7da99b1b414a84a8d9a22971 --- /dev/null +++ b/marked/Rel-16/44_series/44056/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2c0d01dde70f683a19e4d92e3064615f53139a09fffb4e888e26d66fb07595e +size 73742 diff --git a/marked/Rel-16/44_series/44056/5c3dd31372f59e15250f0ab1613ca485_img.jpg b/marked/Rel-16/44_series/44056/5c3dd31372f59e15250f0ab1613ca485_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f2450217c89786045ba12c62e9a966b4c54b48b --- /dev/null +++ b/marked/Rel-16/44_series/44056/5c3dd31372f59e15250f0ab1613ca485_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e847b6e8f307fe08e15a095dd4e620f70ac7133b2b64c166597bbe01c628570c +size 9420 diff --git a/marked/Rel-16/44_series/44056/5c6787bac31274e2dc992efeca74b303_img.jpg b/marked/Rel-16/44_series/44056/5c6787bac31274e2dc992efeca74b303_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c549370066f986ddccd6d7ae4db5b6a63e110d78 --- /dev/null +++ b/marked/Rel-16/44_series/44056/5c6787bac31274e2dc992efeca74b303_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6d1f581f8c87d7fdaec2d99e1244b73f0227b69b1d2cb8691691238f17b78f8 +size 23761 diff --git a/marked/Rel-16/44_series/44056/6f89a9b12884589d3a907f9df6c5c4c3_img.jpg b/marked/Rel-16/44_series/44056/6f89a9b12884589d3a907f9df6c5c4c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ffa1f5948bad2f001e80c4be0b3f1243273cccc --- /dev/null +++ b/marked/Rel-16/44_series/44056/6f89a9b12884589d3a907f9df6c5c4c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:619a2f9d2d060920d3f6fc7ec551db33cfd6c16f4bd07345cca8727c36554d55 +size 27485 diff --git a/marked/Rel-16/44_series/44056/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-16/44_series/44056/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1eae150bcdf15fa38c92a14d9ced2b3c3694b2c --- /dev/null +++ b/marked/Rel-16/44_series/44056/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05f3634417096c11f3d696a26fc3387b543aed0c06252ccccdf4d88061ade18d +size 22156 diff --git a/marked/Rel-16/44_series/44056/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/marked/Rel-16/44_series/44056/838c31609fac483fa2c01c7896a2fd6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb67171cf392d64e594db1440c7586bc24ddeaef --- /dev/null +++ b/marked/Rel-16/44_series/44056/838c31609fac483fa2c01c7896a2fd6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa034b62b701901b3a5bb0670566609e2f867f04ff62e786af8c8cf28cc7987a +size 117786 diff --git a/marked/Rel-16/44_series/44056/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg b/marked/Rel-16/44_series/44056/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4549af186be9b11d889d0643932ffec627f57e8d --- /dev/null +++ b/marked/Rel-16/44_series/44056/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6913300ffb56676c60577ece8851967159adfabdbdd7d58f44dbe3afe81b6d6e +size 14201 diff --git a/marked/Rel-16/44_series/44056/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/44_series/44056/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..152e596944d79a7860de917e2b787d9620075169 --- /dev/null +++ b/marked/Rel-16/44_series/44056/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a20a0b32d15dc126f7ff70716ce8a28b5d2faabeb7d8e59823b3c502a0efb09a +size 127845 diff --git a/marked/Rel-16/44_series/44056/91c33f8e1713989e8192322ec2d1212b_img.jpg b/marked/Rel-16/44_series/44056/91c33f8e1713989e8192322ec2d1212b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01eb400d0065c0793745678f73b541e867763861 --- /dev/null +++ b/marked/Rel-16/44_series/44056/91c33f8e1713989e8192322ec2d1212b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5decb71f39473db37a892fff572fe637ea77804a0d057a48389ec16ed59daa9a +size 42618 diff --git a/marked/Rel-16/44_series/44056/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-16/44_series/44056/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc3715879405e67605c8d7a209eed91a598ab390 --- /dev/null +++ b/marked/Rel-16/44_series/44056/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e2f78ad4ec7723a79544319fdedcdbd099cd5ce7f6a926bb72322bb22e845c2 +size 102175 diff --git a/marked/Rel-16/44_series/44056/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/44_series/44056/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcec680282ecd5d1b0156aeba9cf3fc468b04d92 --- /dev/null +++ b/marked/Rel-16/44_series/44056/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3422de6e00cd2d3ff1921ce3784338e21419620aab21c99ae7a91130c9620254 +size 42126 diff --git a/marked/Rel-16/44_series/44056/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/44_series/44056/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ce4a6dc96b94ddca3dcc89ea2bed6c63f42baaf --- /dev/null +++ b/marked/Rel-16/44_series/44056/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c2ec3654d789e369592cc6b2dd15673dae9754c1111f77a48a998ed06b7500b +size 38813 diff --git a/marked/Rel-16/44_series/44056/a2586540d49d5665489c8b5a273f86d3_img.jpg b/marked/Rel-16/44_series/44056/a2586540d49d5665489c8b5a273f86d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71bb6e9a0a90f973babde546abb36d98ab8f02c6 --- /dev/null +++ b/marked/Rel-16/44_series/44056/a2586540d49d5665489c8b5a273f86d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6508d6bcfbbecb58c7dc7986868ee9691de796738b582fa0f5929d6585c77ff8 +size 26642 diff --git a/marked/Rel-16/44_series/44056/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-16/44_series/44056/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a42f75155379a194f88b18b7924e6df860272f6 --- /dev/null +++ b/marked/Rel-16/44_series/44056/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8692e950e4e00005d903967751ec4a1961e259e9b36baa2cc0436a8d7b844dcd +size 20257 diff --git a/marked/Rel-16/44_series/44056/b055ff69db72d9cb5197aa273d629f82_img.jpg b/marked/Rel-16/44_series/44056/b055ff69db72d9cb5197aa273d629f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f3c4121ae4da23e7c6f3b41ad3f5ff8a4f7c665 --- /dev/null +++ b/marked/Rel-16/44_series/44056/b055ff69db72d9cb5197aa273d629f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e26b1c9e7d1e124db8d986230413600b9bb925f3a20e5cc21312df9d7921a253 +size 15555 diff --git a/marked/Rel-16/44_series/44056/b47f393ea2c781f313367435c7166abb_img.jpg b/marked/Rel-16/44_series/44056/b47f393ea2c781f313367435c7166abb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..328057854f9e34370b35c70e4b3144c72825e8af --- /dev/null +++ b/marked/Rel-16/44_series/44056/b47f393ea2c781f313367435c7166abb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1827f6e2a8ea2b446ee4df31e59a5d2f8ac551a36b84995bbf170217911b23a +size 15943 diff --git a/marked/Rel-16/44_series/44056/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-16/44_series/44056/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40baee03ead30d970f413068a6cd2f89abe47625 --- /dev/null +++ b/marked/Rel-16/44_series/44056/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:157da557728e52d247c9dca17b8df9196629192455fdca07e575be4e28a18c5a +size 18773 diff --git a/marked/Rel-16/44_series/44056/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/44_series/44056/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71ab16846e7003db40dfe0a9b31a9a3aa92d059e --- /dev/null +++ b/marked/Rel-16/44_series/44056/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eea02e9451fbf87675a7f3b137950464518fba330135d7cf3440bacbe5ffd58 +size 21775 diff --git a/marked/Rel-16/44_series/44056/c64555b7f91435b01997807dbb4bcc4c_img.jpg b/marked/Rel-16/44_series/44056/c64555b7f91435b01997807dbb4bcc4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..618cdd411672e6fa0b8ca517114df563941a512f --- /dev/null +++ b/marked/Rel-16/44_series/44056/c64555b7f91435b01997807dbb4bcc4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cf19c0c9175e85b35e38cea97374d891939f67e147a03b3bf9a7376ccf8f139 +size 59524 diff --git a/marked/Rel-16/44_series/44056/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/44_series/44056/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..567de789a8612c0e3d7144b720468dea24e28d8c --- /dev/null +++ b/marked/Rel-16/44_series/44056/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:540a721856b932deb0723a173d9ea1d3e439723e8bbf852c430e875c96ee5eaf +size 22127 diff --git a/marked/Rel-16/44_series/44056/e8c2fa58b461352bbb1b098928737da2_img.jpg b/marked/Rel-16/44_series/44056/e8c2fa58b461352bbb1b098928737da2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3610d50a1d09128055f18dea6a36ed31031301e --- /dev/null +++ b/marked/Rel-16/44_series/44056/e8c2fa58b461352bbb1b098928737da2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75350b5adf260218347f2370cd5e5707a98ec2f1c27c58b65955c1067898266a +size 42627 diff --git a/marked/Rel-16/44_series/44056/e97d663314aff9c29bf8971323e6539e_img.jpg b/marked/Rel-16/44_series/44056/e97d663314aff9c29bf8971323e6539e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bf301c252bd82ac82a44c17fb86a57ea245f224 --- /dev/null +++ b/marked/Rel-16/44_series/44056/e97d663314aff9c29bf8971323e6539e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:459086935cf38927384fad6863148889a4185d655d99ec44cdc8baddb677ce45 +size 103329 diff --git a/marked/Rel-16/44_series/44056/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-16/44_series/44056/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b94d55d050989930b3e066d380bd027ed7f341c --- /dev/null +++ b/marked/Rel-16/44_series/44056/ead623e6a8ec701df64567695a57d01c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5b52b4a6307728c0efcedcd85d70f8b66adc83678247c543daaa19c822fa3b5 +size 26567 diff --git a/marked/Rel-16/44_series/44056/f4b570ddd089f54943d46e9f8776f9f9_img.jpg b/marked/Rel-16/44_series/44056/f4b570ddd089f54943d46e9f8776f9f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59097403cab7d63c1786d27e51a4112254d97241 --- /dev/null +++ b/marked/Rel-16/44_series/44056/f4b570ddd089f54943d46e9f8776f9f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ea616d3030f695feec32b5e2020f666726ed4ffb85d48ecb63bcf31878e9b04 +size 73775 diff --git a/marked/Rel-16/44_series/44056/f92e919c70b7adda2d0e778889f44fae_img.jpg b/marked/Rel-16/44_series/44056/f92e919c70b7adda2d0e778889f44fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b577b11897ee0b1febf13616b7bed37c6174df5 --- /dev/null +++ b/marked/Rel-16/44_series/44056/f92e919c70b7adda2d0e778889f44fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a9583ee6768e22d9e6e9bf50bca10e8e5740ec0da593951c80a1aaf585ceca8 +size 32184 diff --git a/marked/Rel-16/44_series/44056/raw.md b/marked/Rel-16/44_series/44056/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..650480ee4bac688fc3690a169c4a9b86b7e6b17d --- /dev/null +++ b/marked/Rel-16/44_series/44056/raw.md @@ -0,0 +1,4302 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 10 | +| 1.1 Scope of the Technical Specification ..... | 10 | +| 1.2 Application to the interface structures ..... | 10 | +| 1.3 Structure of layer 3 procedures ..... | 10 | +| 1.4 Test procedures ..... | 10 | +| 1.5 Use of logical channels ..... | 10 | +| 1.6 Overview of control procedures ..... | 11 | +| 1.6.1 List of procedures ..... | 11 | +| 1.7 Applicability of implementations ..... | 12 | +| 2 References..... | 12 | +| 3 Definitions, abbreviations and Random values..... | 16 | +| 3.1 Definitions ..... | 16 | +| 3.2 Abbreviations ..... | 16 | +| 3.3 Random values ..... | 16 | +| 4 Overview/General ..... | 16 | +| 4.1 Overview ..... | 16 | +| 4.1.1 General ..... | 16 | +| 4.1.2 Services provided to upper layers..... | 17 | +| 4.1.2.1 CTS-Idle mode..... | 17 | +| 4.1.2.2 Dedicated mode ..... | 17 | +| 4.1.3 Services required from data link and physical layers ..... | 17 | +| 4.1.4 Change of dedicated channels ..... | 17 | +| 4.1.4.1 Change of dedicated channels using SAPI = 0 ..... | 18 | +| 4.1.4.2 Change of dedicated channels using other SAPIs than 0 ..... | 18 | +| 4.1.4.3 Sequenced message transfer operation ..... | 18 | +| 4.1.4.3.1 Variables and sequence numbers ..... | 18 | +| 4.1.4.3.1.1 Send state variable V(SD) ..... | 18 | +| 4.1.4.3.1.2 Send sequence number N(SD)..... | 18 | +| 4.1.4.3.2 Procedures for the initiation, transfer execution and termination of the sequenced message transfer operation..... | 19 | +| 4.1.4.3.2.1 Initiation ..... | 19 | +| 4.1.4.3.2.2 Transfer Execution ..... | 19 | +| 4.1.4.3.2.3 Termination ..... | 19 | +| 4.1.5 Procedure for Service Request and Contention Resolution..... | 19 | +| 4.2 Idle mode procedures ..... | 19 | +| 4.2.1 Mobile Station side..... | 19 | +| 4.2.1.1 CTSBCH and CTSPCH monitoring ..... | 19 | +| 4.2.1.2 Alive check response ..... | 20 | +| 4.2.2 CTS-FP side..... | 20 | +| 4.2.2.1 CTSBCH information broadcasting..... | 20 | +| 4.2.2.2 CTSPCH information broadcasting ..... | 20 | +| 4.2.2.3 Alive check ..... | 20 | +| 4.2.2.4 Hunting ..... | 21 | +| 4.2.2.5 Connectionless group alerting ..... | 22 | +| 4.2.2.5 CTS system information broadcasting..... | 23 | +| 4.3 RR connection establishment..... | 23 | +| 4.3.1 RR connection establishment initiated by the mobile station ..... | 23 | +| 4.3.1.1 Entering the dedicated mode: immediate assignment procedure..... | 23 | +| 4.3.1.1.1 Permission to access the CTS-FP ..... | 24 | +| 4.3.1.1.2 Initiation of the immediate assignment procedure ..... | 24 | +| 4.3.1.1.3 Answer from the CTS-FP..... | 24 | +| 4.3.1.1.3.1 On receipt of a CTS ACCESS REQUEST message..... | 24 | +| 4.3.1.1.3.2 Assignment rejection..... | 24 | +| 4.3.1.1.4 Assignment completion..... | 24 | +| 4.3.1.1.4.1 Early classmark sending..... | 25 | + +| | | | +|------------|------------------------------------------------------------|----| +| 4.3.1.1.5 | Abnormal cases ..... | 25 | +| 4.3.2 | Paging procedure for RR connection establishment..... | 25 | +| 4.3.2.1 | Paging initiation by the CTS-FP ..... | 25 | +| 4.3.2.2 | Paging response ..... | 25 | +| 4.3.2.3 | Abnormal cases..... | 25 | +| 4.4 | Procedures in dedicated mode..... | 26 | +| 4.4.1 | SACCH procedures ..... | 26 | +| 4.4.1.1 | General..... | 26 | +| 4.4.1.2 | Measurement report ..... | 26 | +| 4.4.2 | Transfer of messages and link layer service provision..... | 26 | +| 4.4.3 | Intracell handover procedure..... | 27 | +| 4.4.3.1 | Intracell handover initiation ..... | 27 | +| 4.4.3.2 | Intracell handover completion ..... | 27 | +| 4.4.3.3 | Abnormal cases..... | 27 | +| 4.4.4 | Intercell handover procedure..... | 28 | +| 4.4.5 | Frequency hopping definition procedure..... | 28 | +| 4.4.6 | Channel mode modify procedure ..... | 28 | +| 4.4.6.1 | Normal channel mode modify procedure ..... | 28 | +| 4.4.6.1.1 | Initiation of the channel mode modify procedure ..... | 28 | +| 4.4.6.1.2 | Completion of channel mode modify procedure..... | 28 | +| 4.4.6.1.3 | Abnormal cases ..... | 28 | +| 4.4.7 | Ciphering mode setting procedure..... | 29 | +| 4.4.7.1 | Ciphering mode setting initiation ..... | 29 | +| 4.4.7.2 | Ciphering mode setting completion..... | 29 | +| 4.4.8 | [Reserved: Additional channel assignment procedure]..... | 29 | +| 4.4.9 | [Reserved: Partial channel release procedure]..... | 30 | +| 4.4.10 | Classmark change procedure..... | 30 | +| 4.4.11 | Classmark interrogation procedure..... | 30 | +| 4.4.12 | [Reserved]..... | 30 | +| 4.4.13 | RR connection release procedure ..... | 30 | +| 4.4.13.1 | Normal release procedure ..... | 30 | +| 4.4.13.1.1 | Channel release procedure initiation ..... | 30 | +| 4.4.13.1.2 | Abnormal case..... | 30 | +| 4.4.13.2 | Radio link failure in dedicated mode..... | 31 | +| 4.4.13.2.1 | Mobile side..... | 31 | +| 4.4.13.2.2 | CTS-FP side ..... | 31 | +| 4.4.13.3 | RR connection abortion in dedicated mode..... | 31 | +| 4.4.14 | Receiving CTS RR STATUS message by a CTS-RR entity..... | 31 | +| 4.4.15 | CTS RR parameters update ..... | 31 | +| 5 | Elementary procedures for Mobility Management ..... | 32 | +| 5.1 | General ..... | 32 | +| 5.1.1 | Type of CTS-MM procedures ..... | 32 | +| 5.1.2 | CTS-MM sublayer states ..... | 33 | +| 5.1.2.1 | CTS-MM sublayer states in the mobile station ..... | 33 | +| 5.1.2.1.1 | Main states..... | 33 | +| 5.1.2.1.2 | Substates of the CTS-MM IDLE state ..... | 33 | +| 5.1.2.2 | CTS-MM sublayer states in the fixed part..... | 34 | +| 5.2 | CTS-MM common procedures..... | 34 | +| 5.2.1 | CTS detach procedure ..... | 34 | +| 5.2.1.1 | CTS detach initiation by the mobile station..... | 34 | +| 5.2.1.2 | CTS detach procedure in the fixed part ..... | 34 | +| 5.2.1.3 | CTS detach completion by the mobile station ..... | 34 | +| 5.2.1.4 | Abnormal cases..... | 35 | +| 5.2.2 | CTS de-enrolment procedure ..... | 35 | +| 5.2.2.1 | CTS de-enrolment initiation by the fixed part ..... | 35 | +| 5.2.2.2 | CTS de-enrolment procedure in the mobile station ..... | 35 | +| 5.2.2.3 | Abnormal cases..... | 35 | +| 5.2.3 | CTS mutual authentication procedure..... | 35 | +| 5.2.3.1 | CTS authentication initiation by the fixed part..... | 35 | +| 5.2.3.2 | CTS authentication response by the mobile station..... | 36 | +| 5.2.3.3 | CTS authentication processing by the fixed part..... | 36 | + +| | | | +|---------|-----------------------------------------------------------------------------|----| +| 5.2.3.4 | CTS authentication completion by the mobile station..... | 36 | +| 5.2.3.5 | Unsuccessful authentication ..... | 36 | +| 5.2.3.6 | Abnormal cases..... | 36 | +| 5.2.4 | CTSMSI update procedure ..... | 37 | +| 5.2.4.1 | CTSMSI update initiation by the fixed part..... | 37 | +| 5.2.4.2 | CTSMSI update response by the mobile station..... | 37 | +| 5.2.4.3 | CTSMSI update completion in the fixed part..... | 37 | +| 5.2.4.4 | Abnormal cases..... | 37 | +| 5.3 | CTS-MM specific procedures ..... | 38 | +| 5.3.1 | CTS enrolment procedure..... | 38 | +| 5.3.1.1 | CTS enrolment initiation by the mobile station..... | 38 | +| 5.3.1.2 | CTS enrolment completion by the fixed part..... | 38 | +| 5.3.1.3 | CTS enrolment completion by the mobile station ..... | 38 | +| 5.3.1.4 | Unsuccessful enrolment..... | 38 | +| 5.3.1.5 | Abnormal cases..... | 38 | +| 5.3.2 | CTS attach procedure ..... | 38 | +| 5.3.2.1 | CTS attach initiation by the mobile station ..... | 39 | +| 5.3.2.2 | CTS attach completion by the fixed part ..... | 39 | +| 5.3.2.3 | CTS attach completion by the mobile station..... | 39 | +| 5.3.2.4 | CTS attach rejection treatment by the mobile station..... | 39 | +| 5.3.2.5 | Abnormal cases..... | 39 | +| 5.3.3 | CTS re-attach procedure..... | 39 | +| 5.3.3.1 | CTS re-attach initiation by the mobile station..... | 40 | +| 5.3.3.2 | CTS re-attach completion by the fixed part..... | 40 | +| 5.3.3.3 | Abnormal cases..... | 40 | +| 5.3.4 | CTS periodic attach update procedure..... | 40 | +| 5.3.4.1 | CTS periodic attach update procedure behaviour in the fixed part ..... | 40 | +| 5.3.4.2 | Abnormal cases..... | 40 | +| 6 | Elementary procedures for circuit-switched Call Control ..... | 41 | +| 6.1 | Overview ..... | 41 | +| 6.1.1 | General ..... | 41 | +| 6.2 | Hook flash procedure ..... | 41 | +| 6.2.1 | Hook flash request by the mobile station ..... | 41 | +| 6.2.2 | Hook flash response by the fixed part ..... | 41 | +| 6.2.3 | Stop hook flash request by the mobile station..... | 41 | +| 6.2.4 | Stop hook flash response by fixed part..... | 42 | +| 6.3 | Internal call procedure..... | 42 | +| 7 | Examples of structured procedures ..... | 42 | +| 7.1 | General ..... | 42 | +| 7.1.1 | CTS paging request ..... | 42 | +| 7.1.2 | CTS immediate assignment..... | 42 | +| 7.1.3 | CTS mutual authentication ..... | 43 | +| 7.2 | Abnormal cases ..... | 43 | +| 7.3 | Selected examples ..... | 43 | +| 7.3.1 | Enrolment ..... | 43 | +| 7.3.1.1 | Enrolment with CTS-MS identity authentication done only by the CTS-FP ..... | 44 | +| 7.3.1.2 | Enrolment with CTS MS authentication done by CTS operator ..... | 45 | +| 7.3.2 | Attachment ..... | 46 | +| 7.3.3 | Detachment..... | 46 | +| 7.3.4 | De-enrolment..... | 47 | +| 7.3.5 | Mobile originating call establishment ..... | 47 | +| 8 | Handling of unknown, unforeseen, and erroneous protocol data ..... | 48 | +| 8.1 | General ..... | 48 | +| 8.2 | Message too short..... | 49 | +| 8.3 | Unknown or unforeseen transaction identifier ..... | 49 | +| 8.4 | Unknown or unforeseen message type..... | 49 | +| 8.5 | Non-semantical mandatory information element errors..... | 50 | +| 8.5.1 | Radio resource management..... | 50 | +| 8.5.2 | Mobility management..... | 50 | +| 8.5.3 | Call control ..... | 50 | + +| | | | +|----------|---------------------------------------------------------------------|----| +| 8.6 | Unknown and unforeseen IEs in the non-imperative message part ..... | 51 | +| 8.6.1 | IEIs unknown in the message ..... | 51 | +| 8.6.2 | Out of sequence IEs..... | 51 | +| 8.6.3 | Repeated IEs..... | 51 | +| 8.7 | Non-imperative message part errors ..... | 51 | +| 8.7.1 | Syntactically incorrect optional IEs..... | 51 | +| 8.7.2 | Conditional IE errors ..... | 51 | +| 8.8 | Messages with semantically incorrect contents ..... | 52 | +| 9 | Message functional definitions and contents ..... | 52 | +| 9.1 | Messages for Radio Resources management ..... | 53 | +| 9.1.1 | CTS access request ..... | 53 | +| 9.1.2 | CTS AFA monitoring command ..... | 54 | +| 9.1.3 | CTS AFA monitoring enquiry ..... | 55 | +| 9.1.4 | CTS AFA monitoring report ..... | 55 | +| 9.1.5 | CTS BCCH detection command ..... | 55 | +| 9.1.6 | CTS BCCH detection enquiry ..... | 56 | +| 9.1.7 | CTS BCCH detection report..... | 56 | +| 9.1.8 | CTS beacon channel synchronisation burst information ..... | 57 | +| 9.1.9 | CTS channel mode modify ..... | 57 | +| 9.1.10 | CTS channel mode modify acknowledge..... | 58 | +| 9.1.11 | CTS channel release ..... | 58 | +| 9.1.12 | CTS ciphering mode command ..... | 58 | +| 9.1.13 | CTS ciphering mode complete ..... | 59 | +| 9.1.14 | CTS classmark change ..... | 59 | +| 9.1.15 | CTS classmark enquiry..... | 59 | +| 9.1.16 | CTS frequency hopping definition ..... | 59 | +| 9.1.16.1 | Reference time ..... | 60 | +| 9.1.17 | CTS group alerting request..... | 60 | +| 9.1.17.1 | Rest Octets ..... | 60 | +| 9.1.18 | CTS hunting request..... | 61 | +| 9.1.18.1 | Rest Octets ..... | 61 | +| 9.1.19 | CTS immediate assignment..... | 61 | +| 9.1.20 | CTS immediate assignment extended ..... | 62 | +| 9.1.21 | CTS immediate assignment reject ..... | 62 | +| 9.1.21.1 | Use of Indexes ..... | 63 | +| 9.1.21.2 | Filling of the message ..... | 63 | +| 9.1.22 | CTS intracell handover command..... | 63 | +| 9.1.23 | CTS intracell handover complete ..... | 64 | +| 9.1.24 | CTS intracell handover failure ..... | 64 | +| 9.1.25 | CTS measurement report..... | 65 | +| 9.1.25.1 | Measurement results ..... | 65 | +| 9.1.26 | CTS OFO measurement command..... | 65 | +| 9.1.27 | CTS OFO measurement enquiry ..... | 66 | +| 9.1.28 | CTS OFO Measurement report ..... | 66 | +| 9.1.29 | CTS paging request ..... | 67 | +| 9.1.29.1 | Paging type ..... | 67 | +| 9.1.30 | CTS paging response..... | 67 | +| 9.1.30.1 | Ciphering Key Sequence ..... | 68 | +| 9.1.31 | CTS system information type 1 ..... | 68 | +| 9.1.31.1 | Starting Time ..... | 68 | +| 9.1.32 | CTS system information type 2 ..... | 69 | +| 9.1.33 | CTS system information type 3 ..... | 69 | +| 9.1.34 | CTS RR parameters update ..... | 69 | +| 9.2 | Messages for mobility management..... | 70 | +| 9.2.1 | CTS attach request..... | 70 | +| 9.2.2 | CTS attach accept..... | 71 | +| 9.2.3 | CTS attach reject ..... | 71 | +| 9.2.4 | CTS detachment indication ..... | 72 | +| 9.2.5 | CTS enrolment request..... | 72 | +| 9.2.6 | CTS enrolment accept ..... | 73 | +| 9.2.7 | CTS enrolment reject..... | 73 | + +| | | | +|-------------------------------|--------------------------------------------------------------|-----------| +| 9.2.8 | CTS de-enrolment indication ..... | 74 | +| 9.2.9 | CTS MS authentication request..... | 74 | +| 9.2.10 | CTS MS authentication response ..... | 75 | +| 9.2.11 | CTS FP authentication response..... | 75 | +| 9.2.12 | CTS MS authentication reject ..... | 76 | +| 9.2.13 | CTSMSI update command ..... | 76 | +| 9.2.14 | CTSMSI update complete ..... | 77 | +| 10 | General message format and information elements coding ..... | 77 | +| 10.1 | Overview ..... | 77 | +| 10.2 | Protocol Discriminator ..... | 77 | +| 10.3 | Sub-Protocol Discriminator and transaction identifier..... | 77 | +| 10.3.1 | Sub-Protocol Discriminator ..... | 77 | +| 10.3.2 | Transaction identifier..... | 77 | +| 10.4 | Message Type..... | 77 | +| 10.5 | Other information elements..... | 79 | +| 10.5.1 | Common information elements ..... | 79 | +| 10.5.1.1 | Mobile Identity ..... | 79 | +| 10.5.2 | Radio Resource management information elements ..... | 79 | +| 10.5.2.1 | CTSMSI..... | 79 | +| 10.5.2.2 | TFH General Parameters ..... | 80 | +| 10.5.2.3 | TFH Current Parameters ..... | 80 | +| 10.5.2.4 | CTS Channel Description ..... | 81 | +| 10.5.2.5 | CTS Access Request Reference..... | 82 | +| 10.5.2.6 | CTS L1 information ..... | 82 | +| 10.5.2.7 | Information Transfert Capability ..... | 83 | +| 10.5.2.8 | BCD Display..... | 83 | +| 10.5.2.9 | AFA Interference Level ..... | 83 | +| 10.5.2.10 | AFA Monitoring Cycles ..... | 84 | +| 10.5.2.11 | OFO Measurement Results ..... | 84 | +| 10.5.2.12 | Paging type ..... | 85 | +| 10.5.2.13 | CTS selection parameters ..... | 85 | +| 10.5.2.14 | CTS RR parameters ..... | 86 | +| 10.5.2.15 | Timeslot shifting parameters ..... | 87 | +| 10.5.3 | Mobility management information elements..... | 87 | +| 10.5.3.1 | Authentication parameter RIMS ..... | 87 | +| 10.5.3.2 | Authentication parameter RIFP ..... | 88 | +| 10.5.3.3 | Authentication parameter CH ..... | 88 | +| 10.5.3.4 | Authentication parameter XRES ..... | 89 | +| 10.5.3.5 | Authentication parameter Kax ..... | 89 | +| 10.5.3.6 | Fixed part Identity ..... | 90 | +| 10.5.3.7 | CTS mobile group list..... | 91 | +| 10.5.3.8 | Following attach request..... | 91 | +| 10.5.3.9 | Access right identity ..... | 92 | +| 10.5.3.10 | TC3252 ..... | 92 | +| 10.5.3.11 | Attach type..... | 93 | +| 10.5.4 | Call control information elements ..... | 93 | +| 10.5.4.1 | Called party BCD number ..... | 93 | +| 10.5.4.2 | Calling party BCD number ..... | 93 | +| 10.5.4.3 | Keypad facility..... | 94 | +| 11 | List of system parameters ..... | 94 | +| 11.1 | Timers and counters for radio resource management ..... | 94 | +| 11.1.1 | Timers on the MS side..... | 94 | +| 11.1.2 | Timers on the CTS-FP side ..... | 95 | +| 11.1.3 | Other parameters ..... | 95 | +| 11.2 | Timers of mobility management ..... | 95 | +| 11.2.1 | Timers on the MS side..... | 95 | +| 11.2.2 | Timers on the CTS-FP side ..... | 96 | +| 11.2.3 | Other parameters ..... | 96 | +| 11.3 | Timers of circuit-switched call control ..... | 96 | +| Annex A (informative): | Default Codings of Information Elements ..... | 97 | + +A.1 Common information elements..... 97 + +A.2 Radio Resource management information elements..... 97 + +A.3 Mobility management information elements ..... 98 + +A.4 Call control information elements..... 99 + +Annex B (informative): Change history..... 100 + +--- + +## 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 procedures used at the CTS radio interface (Reference Point Um\*, see GSM 03.56) for Call Control (CC), Mobility Management (MM), Radio Resource (RR). + +When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document. + +These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The CTS control channels are described in GSM 03.52. + +The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07. + +## 1.1 Scope of the Technical Specification + +The procedures currently described in the present document are for the call control of circuit-switched connections, mobility management and radio resource management for circuit-switched services over the CTS radio interface. + +GSM 04.10 contains functional procedures for support of supplementary services. + +GSM 04.11 contains functional procedures for support of point-to-point short message services. + +NOTE: "layer 3" includes the functions and protocols described in the present document. The terms "data link layer" and "layer 2" are used interchangeably to refer to the layer immediately below layer 3. + +## 1.2 Application to the interface structures + +The layer 3 procedures apply to the interface structures defined in GSM 04.03. They use the functions and services provided by layer 2 defined in GSM 04.05 and GSM 04.06. GSM 04.07 gives the general description of layer 3 including procedures, messages format and error handling. + +## 1.3 Structure of layer 3 procedures + +A building block method is used to describe the layer 3 procedures. + +The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer. + +Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences. + +## 1.4 Test procedures + +Test procedures of the GSM-CTS radio interface signalling are described in GSM 11.10 and GSM 11.56 series. + +## 1.5 Use of logical channels + +The logical control channels are defined in GSM 03.52. In the following those control channels are considered which carry signalling information or specific types of user packet information: [to be completed]: + +- i) CTS Beacon CHannel (CTSBCH): downlink only, used to broadcast Cell specific information and fixed part identification information; +- ii) CTS Paging CHannel (CTSPCH): downlink only, used to send page requests to Mobile Stations (MSs); +- iii) CTS Access Random CHannel (CTSARCH): uplink only, used to request a Dedicated Control CHannel; +- iv) CTS-Access Grant CHannel (CTSAGCH): downlink only, used to allocate a Dedicated Control CHannel; +- v) Fast Associated Control CHannel (FACCH): bi-directional, associated with a Traffic CHannel; +- vi) Slow Associated Control CHannel (SACCH): bi-directional, associated with a Traffic CHannel; + +Two service access points are defined on signalling layer 2 which are discriminated by their Service Access Point Identifiers (SAPI) (see GSM 04.06): + +- i) SAPI 0: supports the transfer of signalling information including user-user information; +- ii) SAPI 3: supports the transfer of user short messages. + +Layer 3 selects the service access point, the logical control channel and the mode of operation of layer 2 (acknowledged, unacknowledged or random access, see GSM 04.05 and GSM 04.06) as required for each individual message. + +## 1.6 Overview of control procedures + +### 1.6.1 List of procedures + +The following procedures are specified in the present document: + +- a) Clause 4 specifies elementary procedures for Radio Resource management: + - Idle mode procedures (subclause 4.2): + - alive check procedure (subclauses 4.2.1.2 and 4.2.2.3); + - BCH information broadcasting (subclause 4.2.2.1); + - CCH information broadcasting (subclause 4.2.2.2); + - hunting (subclause 4.2.2.4); + - connectionless group alerting (subclause 4.2.2.5). + - RR connection establishment (subclause 4.3): + - entering the dedicated mode : immediate assignment procedure (subclause 4.3.1.1); + - paging procedure for RR connection establishment (subclause 4.3.2). + - Procedures in dedicated mode (subclause 4.4): + - intracell change of channels (subclause 4.4.4); + - channel mode change procedure (subclause 4.4.6); + - ciphering mode setting procedure (subclause 4.4.7). + - RR connection release (subclause 4.4.13). +- b) Clause 5 specifies elementary procedures for CTS-Mobility Management: + - mobility management common procedures (subclause 5.2): + - CTS attach procedure (subclause 5.2.1); + - CTS periodic attach updating procedure (subclause 5.2.2); + - CTS detach procedure (subclause 5.2.3); + - CTS de-enrolment procedure (subclause 5.2.4); + - CTS mutual authentication procedure (subclause 5.2.5); + - CTS-MSI update procedure (subclause 5.2.6). + - mobility management specific procedures (subclause 5.3): + - CTS enrolment procedure (subclause 5.3.1); + - CTS de-enrolment procedure (subclause 5.3.2). + +- c) Clause 6 specifies CTS specific elementary procedure for circuit switched Call Control: + - signalling procedures during the active state: + - hook flash procedure (subclause 6.1.2). + +The elementary procedures can be combined to form structured procedures. Examples of such structured procedures are given in clause 7. This part of the Technical Specification is only provided for guidance to assist implementations. + +Clause 8 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol. + +## 1.7 Applicability of implementations + +The applicability of procedures of the present document for the mobile station is dependent on the services and functions which are to be supported by a mobile station. + +--- + +## 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.02: "Digital cellular telecommunications system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". +- [2] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [3] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". +- [4] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". +- [5] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects". +- [6] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility". +- [7] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber Identity Modules (SIM); Functional characteristics". +- [8] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications". +- [9] GSM 03.01: "Digital cellular telecommunications system (Phase 2+); Network functions". +- [10] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". +- [11] GSM 03.13: "Digital cellular telecommunications system (Phase 2+); Discontinuous Reception (DRX) in the GSM system". +- [12] GSM 03.14: "Digital cellular telecommunications system (Phase 2+); Support of Dual Tone Multi-Frequency signalling (DTMF) via the GSM system". + +- [13] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions". +- [14] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [15] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". +- [16] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". +- [17] GSM 04.04: "Digital cellular telecommunications system (Phase 2+); Layer 1; General requirements". +- [18] GSM 04.05: "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer; General aspects". +- [19] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". +- [20] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". +- [21] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". +- [22] GSM 04.11: "Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [23] GSM 04.12: "Digital cellular telecommunications system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [24] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". +- [25] GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services; Stage 3". +- [26] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services; Stage 3". +- [27] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3". +- [28] GSM 04.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services; Stage 3". +- [29] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services; Stage 3". +- [30] GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services; Stage 3". +- [31] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services; Stage 3". +- [32] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". +- [33] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [34] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". + +- [35] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronisation". +- [36] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [37] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". +- [38] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [39] GSM 11.10: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) conformance specification". +- [40] GSM 11.21: "Digital cellular telecommunications system (Phase 2+); Base Station System (BSS) equipment specification". +- [41] ISO/IEC 646 (1991): "Information technology - ISO 7-bit coded character set for information interchange". +- [42] ISO/IEC 6429: "Information technology - Control functions for coded character sets". +- [43] ISO 8348 (1987) (Addendum 2): "Information processing systems - Data communications - Network service definition". +- [44] ITU-T Recommendation E.163: "Numbering plan for the international telephone service". +- [45] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [46] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users". +- [47] ITU-T Recommendation F.69 (1993): "The international telex service - Service and operational provisions of telex destination codes and telex network identification codes". +- [48] ITU-T Recommendation I.330: "ISDN numbering and addressing principles". +- [49] ITU-T Recommendation I.440 (1989): "ISDN user-network interface data link layer - General aspects". +- [50] ITU-T Recommendation I.450 (1989): "ISDN user-network interface layer 3 - General aspects". +- [51] ITU-T Recommendation I.500 (1993): "General structure of the ISDN interworking recommendations". +- [52] ITU-T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange". +- [53] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic control". +- [54] ITU-T Recommendation V.21: "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [55] ITU-T Recommendation V.22: "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [56] ITU-T Recommendation V.22bis: "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [57] ITU-T Recommendation V.23: "600/1200-baud modem standardized for use in the general switched telephone network". + +- [58] ITU-T Recommendation V.26ter: "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [59] ITU-T Recommendation V.32: "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits". +- [60] ITU-T Recommendation V.110: "Support by an ISDN of data terminal equipments with V-Series type interfaces". +- [61] ITU-T Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". +- [62] ITU-T Recommendation X.21: "Interface between Data Terminal Equipment and Data Circuit-terminating Equipment for synchronous operation on public data networks". +- [63] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". +- [64] ITU-T Recommendation X.28: "DTE/DCE interface for a start-stop mode Data Terminal Equipment accessing the Packet Assembly/Disassembly facility (PAD) in a public data network situated in the same country". +- [65] ITU-T Recommendation X.30: "Support of X.21, X.21 bis and X.20 bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN)". +- [66] ITU-T Recommendation X.31: "Support of packet mode terminal equipment by an ISDN". +- [67] ITU-T Recommendation X.32: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and accessing a packet-switched public data network through a public switched telephone network or an integrated services digital network or a circuit-switched public data network". +- [68] ITU-T Recommendation X.75 (1988): "Packet-switched signalling system between public networks providing data transmission services". +- [69] ITU-T Recommendation X.121: "International numbering plan for public data networks". +- [70] ETSI ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface layer 3; Specifications for basic call control". +- [71] ETSI ETS 300 102-2: "Integrated Services Digital Network (ISDN); User-network interface layer 3; Specifications for basic call control; Specification Description Language (SDL) diagrams". +- [72] ISO/IEC 10646: "Information technology - Universal Multiple-Octet Coded Character Set (UCS)". +- [73] GSM 02.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; Service description; Stage 1". +- [74] GSM 03.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; CTS Architecture Description; Stage 2". +- [75] GSM 03.52: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; Lower Layers of the CTS Radio Interface; Stage 2". +- [76] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface; Layer 3 specification". + +--- + +## 3 Definitions, abbreviations and Random values + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in GSM 04.08 and the following apply: + +**CTS-idle mode:** in this mode, the mobile station is not allocated any dedicated channel; it listens to the BCH and to the CCH when requested + +NOTE: In CTS-RR connected mode, main DCCH means FACCH.4 CTS-Radio Resource management procedures + +### 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in GSM 01.04 apply. + +### 3.3 Random values + +In a number of places in the present document, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. + +It is required that there is a low probability that two equipment's in the same conditions (including the case of two equipment's of the same type from the same manufacturer) will choose the same value. Moreover, it is required that, if it happens that two equipment's in similar conditions choose the same value, the probability of their choices being identical at the next occasion is the same as if their first choices had been different. + +The meaning of such a specification is that any statistical test for these values, done on a series of similar events, will obtain a result statistically compatible with the specified distribution. This shall hold even in the cases where the tests are conducted with a subset of possible events, with some common parameters. Moreover, basic tests of independence of the values within the series shall pass. + +Data against which correlation with the values shall not be found are the protocol state, or the IMSI, or identities or other unrelated information broadcast by the network, or the current TDMA frame number. + +--- + +## 4 Overview/General + +### 4.1 Overview + +#### 4.1.1 General + +CTS-Radio Resource management procedures include the functions related to the management of the common transmission resources, e.g. the physical channels and the data link connections on control channels. + +The general purpose of CTS-Radio Resource procedures is to establish, maintain and release RR connections that allow a point-to-point dialogue between the CTS-FP and a mobile station. Moreover, Radio Resource management procedures at the CTS-MS side include the reception of the uni-directional CTSBCH and CTSPCH when no RR connection is established. This permits automatic cell selection/reselection. + +#### 4.1.2 Services provided to upper layers + +A CTS-RR connection is a physical connection used by the two peer entities to support the upper layers' exchange of information flows. + +##### 4.1.2.1 CTS-Idle mode + +In CTS-idle mode no CTS-RR connection exists. + +The RR procedures include (on the mobile station side) those for automatic cell selection/reselection. The RR entity indicates to upper layers the unavailability of a CTSBCH/CTSPCH and the cell change when decided by the RR entity. + +Upper layers are advised of the CTSBCH broadcast information when a new cell has been selected, or when a relevant part of this information changes. + +In Idle mode, upper layers can require the establishment of an CTS-RR connection. + +In Idle-mode, RR procedures provide the following service: + +- alive check (CTS-FP side); +- hunting; +- connectionless group alerting; +- CTS system information broadcasting. + +Connectionless group alerting is a point-to-multipoint unidirectional transmission on the CTSPCH. It can only be initiated by the CTS-FP. + +#### 4.1.2.2 Dedicated mode + +In dedicated mode, the CTS-RR connection is a physical point-to-point bi-directional connection, and includes a SAPI 0 data link connection operating in multiframe mode on the main DCCH. If dedicated mode is established, RR procedures provide the following services: + +- establishment/release of multiframe mode on data link layer connections other than SAPI 0, on the main DCCH or on the SACCH associated with the channel carrying the main signalling link; +- transfer of messages on any data link layer connection; +- indication of temporary unavailability of transmission (suspension, resuming); +- indication of loss of CTS-RR connection; +- setting/change of the transmission mode on the physical channels, including change of type of channel, change of the coding/decoding/transcoding mode and setting of ciphering; +- release of an CTS-RR connection. + +#### 4.1.3 Services required from data link and physical layers + +The CTS-RR sublayer uses the services provided by the data link layer as defined in GSM 04.05. + +Moreover, the RR sublayer directly uses services provided by the physical layer such as CTSBCH searching, as defined in GSM 04.04. + +#### 4.1.4 Change of dedicated channels + +NOTE: for this version of the protocol, no intra-cell handover is to be defined. + +##### 4.1.4.1 Change of dedicated channels using SAPI = 0 + +In case a change of dedicated channels is required using a dedicated assignment procedure, the RR sublayer will request the data link layer to suspend multiple frame operation before the mobile station leaves the old channel. When the channel change has been completed, layer 3 will request the data link layer to resume multiple frame operation again. The layer 2 suspend/resume procedures are described in GSM 04.05 and 04.06. + +These procedures are specified in such a way that a loss of a layer 3 message cannot occur on the radio interface. However, messages sent from the mobile station to the CTS-FP may be duplicated by the data link layer if a message has been transmitted but not yet completely acknowledged before the mobile station leaves the old channel (see GSM 04.06). + +As the RR sublayer is controlling the channel change, a duplication of RR messages does not occur. However, there are some procedures for which a duplication is possible, e.g. DTMF procedures. For all upper layer procedures using the transport service of the RR sub-layer (e.g. MM and CM procedures), the request messages sent by the mobile station contain a sequence number in order to allow the CTS-FP to detect duplicated messages, which are then ignored by the CTS-FP. The procedures for sequenced transmission on layer 3 are described in subclause 4.1.4.2. + +#### 4.1.4.2 Change of dedicated channels using other SAPIs than 0 + +For SAPIs other than 0, the data link procedures described in GSM 04.06 do not provide any guarantee against message loss or duplication. + +Therefore, if an application uses a SAPI other than 0 and if this application is sensitive to message loss or duplication, then it has to define its own protection mechanism. No general protection mechanism is provided by the protocol defined in the present document. + +#### 4.1.4.3 Sequenced message transfer operation + +Upper layer messages sent using the RR sub-layer transport service from the mobile station to the CTS-FP can be duplicated by the data link layer in the following case: + +- a channel change of dedicated channels is required (assignment procedure) and the last layer 2 frame has not been acknowledged by the peer data link layer before the mobile station leaves the old channel. + +In this case, the mobile station does not know whether the CTS-FP has received the message correctly. Therefore, the mobile station has to send the message again after the new dedicated channel is established (see GSM 04.06). + +The CTS-FP must be able to detect the duplicated received message. Therefore, each concerned upper layer message must be marked with a send sequence number. + +For historical reasons (see GSM 04.08), messages sent with the CC, SS and MM PDs share the same sequence numbering. + +##### 4.1.4.3.1 Variables and sequence numbers + +###### 4.1.4.3.1.1 Send state variable V(SD) + +The RR sublayer of the mobile station shall have one associated send state variable V(SD) ("Send Duplicated") for each upper layer message flow. The send state variable denotes the sequence number of the next in sequence numbered message in the flow to be transmitted. The value of the corresponding send state variable shall be incremented by one with each numbered message transmission. Arithmetic operations on V(SD) are performed modulo 2. + +###### 4.1.4.3.1.2 Send sequence number N(SD) + +At the time when such a message to be numbered is designated for transmission, the value of N(SD) for the message to be transferred is set equal to the value of the send state variable V(SD). See GSM 04.07. + +##### 4.1.4.3.2 Procedures for the initiation, transfer execution and termination of the sequenced message transfer operation + +###### 4.1.4.3.2.1 Initiation + +The sequenced message transfer operation is initiated by establishing a RR connection. The send state variables V(SD) are set to 0. + +###### 4.1.4.3.2.2 Transfer Execution + +The CTS-FP must compare the send sequence numbers of pairs of subsequent messages in the same upper layer messages flow. In case the send sequence numbers of two subsequent messages in a flow are not identical, no duplication has occurred. In case the send sequence numbers are identical, the CTS-FP must ignore the second one of the received messages. + +###### 4.1.4.3.2.3 Termination + +The sequenced message transfer operation is terminated by the RR connection release procedure. + +#### 4.1.5 Procedure for Service Request and Contention Resolution + +Upon seizure of the assigned dedicated channel, the mobile station establishes the main signalling link on this channel by sending a layer 2 SABM frame containing a layer 3 service request message. The data link layer will store this message to perform the contention resolution. The service request message will be returned by the CTS-FP in the UA frame. + +The data link layer in the mobile station compares the content of the information field (i.e. the layer 3 service request message) received in the UA frame with the stored message and leaves the channel in case they do not match. This procedure resolves contentions in the case where several mobile stations have accessed at the same random access slot and with the same random reference and one has succeeded due to capture. The full description of the procedure is given in GSM 04.06. + +The purpose of the service request message is to indicate to the CTS-FP which service the mobile station is requesting. This then allows the CTS-FP to decide how to proceed (e.g. to authenticate or not). + +The service request message must contain the identity of the mobile station and may include further information which can be sent without encryption. + +![Sequence diagram showing the interaction between CTS-MS and CTS-FP. The CTS-MS sends a SABM ('layer 3 service request message') to the CTS-FP. The CTS-FP responds with a UA ('layer 3 service request message') to the CTS-MS.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +sequenceDiagram + participant CTS-MS + participant CTS-FP + Note right of CTS-MS: SABM ("layer 3 service request message") + CTS-MS->>CTS-FP: SABM ("layer 3 service request message") + Note left of CTS-FP: UA ("layer 3 service request message") + CTS-FP-->>CTS-MS: UA ("layer 3 service request message") + +``` + +Sequence diagram showing the interaction between CTS-MS and CTS-FP. The CTS-MS sends a SABM ('layer 3 service request message') to the CTS-FP. The CTS-FP responds with a UA ('layer 3 service request message') to the CTS-MS. + +Figure 4.1/GSM 04.56: Service request and contention resolution + +## 4.2 Idle mode procedures + +### 4.2.1 Mobile Station side + +#### 4.2.1.1 CTSBCH and CTSPCH monitoring + +In CTS-idle mode, a MS which has recognised a known FPBI, listens to the CTSBCH and to the CTSPCH when CTSPCH indicator flags indicates "CTSPCH to decode". + +#### 4.2.1.2 Alive check response + +When the CTSPCH contains an CTS ALIVE CHECK REQUEST message, the addressed CTS-MS shall send a CTS ALIVE CHECK RESPONSE message. A CTS ALIVE CHECK RESPONSE message shall be send by the CTS-MS in response to each CTS ALIVE CHECK REQUEST message received with the corresponding CTSMSI. + +The CTS ALIVE CHECK RESPONSE messages are sent on the CTSARCH and contain as parameters: + +- an establishment cause which corresponds to "attachment update" given by the RR entity in response to a CTS ALIVE CHECK REQUEST message; +- the CTS-MS Mobile Subscriber Identity. + +### 4.2.2 CTS-FP side + +#### 4.2.2.1 CTSBCH information broadcasting + +FPBI and CTS-FP status are regularly broadcast by the CTS-FP on the CTSBCH. Based on this information, the CTS-MS is able to decide whether it may gain access to the CTS-FP. + +The information broadcast may be grouped in the following classes: + +- information giving unique identification of the current CTS-FP cell; +- information describing the Training Sequence Code to be used in dedicated mode; +- information describing the Radio Resource availability at the CTS-FP side; +- information describing the presence of a Paging Channel; +- information describing the timeslot number to be used by the CTSCCH except CTSBCH (i.e. CTSARCH, CTSPCH and CTSAGCH); + +- information describing the shifting status of the CTSBCH. + +#### 4.2.2.2 CTSPCH information broadcasting + +In pure idle mode, the Paging Channel is not used. The CTS-FP shall set the CTSPCH indicator flag to "no CTSPCH" value. + +#### 4.2.2.3 Alive check + +The CTS-FP initiates the alive check procedure by broadcasting a CTS PAGING REQUEST message with an indication of Alive Check, and start timer TC3101. The CTSPCH indicator flag shall be set to "CTSPCH to decode" and the CTSBCH-SB Status field shall be set to idle. The alive check procedure shall not be triggered if the CTS-FP is in a busy state (no radio resources available); i.e. CTS-FP RR layer shall reject upper layer alive check procedure initiation request. + +When receiving a CTS PAGING REQUEST with an indication of Alive Check, the CTS-MS shall send 2 CTS ACCESS REQUEST messages. + +When receiving a valid CTS ACCESS REQUEST, the CTS-FP shall stop timer TC3101. + +The CTS-FP RR sublayer shall end the alive check procedure when: + +- a CTS ACCESS REQUEST with a valid cause has been received from the polled CTS-MS; or +- timer TC3101 expires; or +- an end of alive check procedure is triggered by the upper layer; or +- a paging procedure requiring a new PAGING REQUEST message to be started; or +- a busy state occurs (i.e. no more radio resource available). + +The CTS-FP shall ignore unsolicited or out of sequence CTS ACCESS REQUEST. + +![Sequence diagram for alive check procedure between CTS-MS and CTS-FP. The diagram shows two messages: 1. CTS PAGING REQ (CTSMSI, AC ind) [CTSPCH] from CTS-FP to CTS-MS, which triggers 'Start TC3101'. 2. CTS ACCESS REQUEST (CTSMSI) [CTSARCH] from CTS-MS to CTS-FP, which triggers 'Stop TC3101'.](5c6787bac31274e2dc992efeca74b303_img.jpg) + +``` + +sequenceDiagram + participant CTS-MS + participant CTS-FP + Note right of CTS-FP: Start TC3101 + CTS-FP->>CTS-MS: CTS PAGING REQ (CTSMSI, AC ind) [CTSPCH] + Note right of CTS-MS: Stop TC3101 + CTS-MS->>CTS-FP: CTS ACCESS REQUEST (CTSMSI) [CTSARCH] + +``` + +Sequence diagram for alive check procedure between CTS-MS and CTS-FP. The diagram shows two messages: 1. CTS PAGING REQ (CTSMSI, AC ind) [CTSPCH] from CTS-FP to CTS-MS, which triggers 'Start TC3101'. 2. CTS ACCESS REQUEST (CTSMSI) [CTSARCH] from CTS-MS to CTS-FP, which triggers 'Stop TC3101'. + +Figure 4.2/GSM 04.56: alive check sequence + +#### 4.2.2.4 Hunting + +The CTS-FP initiates the hunting procedure by continuously broadcasting CTS HUNTING REQUEST messages on the CTSPCH channel, and start timer TC3102. The CTSPCH indicator flag shall be set to "CTSPCH to decode". The value of TC3102 is manufacturer dependant, but shall be less than 120 s. The hunting procedure shall not be triggered if the CTS-FP is in a busy state (no radio resources available); i.e. CTS-FP RR layer shall reject upper layer hunting procedure initiation request. + +Upon receipt of a CTS HUNTING REQUEST, the CTS-MSs shall act as following: + +- if group alerting was requested, the CTS-MS shall alert if the received connectionless group CTSMSI is equal to its assigned connectionless group CTSMSI (if any); +- if collective alerting was requested, the CTS-MS shall start alerting. + +Hunted CTS-MS are required to receive and analyse the message sent on the next CTSPCH occurrence. The CTS-MSs shall consider that the hunting procedure has been ended by the CTS-FP when no CTS HUNTING REQUEST message has been received within the 3 latest occurrences of the CTSPCH. The CTS-MSs shall stop alerting. + +The CTS-FP shall end the hunting procedure when: + +- $T_{C3102}$ expires; or +- a paging procedure is to be started; or +- an end of hunting procedure is triggered by the CTS-FP user; or +- a busy state occurs (i.e. no more radio resource available). + +A CTS-MS shall stop alerting when requested by the user. + +![Sequence diagram illustrating the hunting sequence between a USER, CTS-MS, and CTS-FP. The sequence starts with a CTS HUNTING REQUEST [CTSPCH] from CTS-FP to CTS-MS. The CTS-MS then sends a USER ALERTING message to the USER. The CTS-FP then sends another CTS HUNTING REQUEST [CTSPCH] to the CTS-MS. The CTS-MS then sends a STOP ALERTING message to the USER. A note indicates that there was no hunting request within the 3 latest occurrences of the CTSPCH.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +``` + +sequenceDiagram + participant USER + participant CTS-MS + participant CTS-FP + Note right of CTS-FP: CTS HUNTING REQUEST [CTSPCH] + CTS-FP->>CTS-MS: CTS HUNTING REQUEST [CTSPCH] + Note left of CTS-MS: USER ALERTING + CTS-MS->>USER: USER ALERTING + Note right of CTS-FP: CTS HUNTING REQUEST [CTSPCH] + CTS-FP->>CTS-MS: CTS HUNTING REQUEST [CTSPCH] + Note right of CTS-MS: [NO HUNTING REQUEST WITHIN THE +[3 LATEST OCCURRENCES OF THE CTSPCH]] + Note left of CTS-MS: STOP ALERTING + CTS-MS->>USER: STOP ALERTING + +``` + +Sequence diagram illustrating the hunting sequence between a USER, CTS-MS, and CTS-FP. The sequence starts with a CTS HUNTING REQUEST [CTSPCH] from CTS-FP to CTS-MS. The CTS-MS then sends a USER ALERTING message to the USER. The CTS-FP then sends another CTS HUNTING REQUEST [CTSPCH] to the CTS-MS. The CTS-MS then sends a STOP ALERTING message to the USER. A note indicates that there was no hunting request within the 3 latest occurrences of the CTSPCH. + +Figure 4.3/GSM 04.56: hunting sequence + +#### 4.2.2.5 Connectionless group alerting + +On receipt of a request for an incoming call, the CTS-FP may decide to alert part or all enrolled CTS-MSs. + +In this case the CTS-FP shall request the RR sublayer to send a request for alerting indicating which CTS-MSs shall alert. Either the group mask shall be used to alert all CTS-MSs having an assigned connectionless group CTSMSI matching the group mask, or the connectionless CTSMSI shall be used to alert the CTS-MSs having this connectionless CTSMSI assigned, or the Collective Broadcast Identifier shall be used to alert all CTS-MSs. + +This Connectionless CTS-MS paging procedure should be used for group or collective connectionless alerting service when the number of paged CTS-MS is greater than the number of available CTS-FP radio resources. + +The CTS-FP initiates the connectionless group alerting procedure by broadcasting continuously a GROUP ALERTING REQUEST message on the CTSPCH subchannel. The CTSPCH indicator flag shall be set to "CTSPCH to decode" and the CTSBCH-SB Status field shall be set to idle. Only connectionless group CTSMSI or Connectionless Broadcast Identifier are allowed in a CTS GROUP ALERTING REQUEST message. + +Upon receipt of a CTS GROUP ALERTING REQUEST, the CTS-MS shall react as following: + +- if group alerting was requested, the CTS-MS shall alert if the received connectionless group CTSMSI is equal to its assigned connectionless group CTSMSI (if any); +- if collective alerting was requested, the CTS-MS shall start alerting. + +Alerted CTS-MSs are required to receive and analyse the message sent on the next CTSPCH. Unless the user accept the call, the CTS-MS shall not answer to this paging. When the user accept the call, the "off hook" shall trigger an outgoing call request. The CTS-FP shall initiate the immediate assignment procedure as specified in subclause 4.3.1. The CTS-FP shall suspend the connectionless paging procedure. The establishment of the main signalling link is initiated by the use of an SABM. The SETUP message shall be then passed to the CTS-FP. + +At the CTS-FP, this outgoing call is directly mapped to the awaiting incoming call. + +The CTS-FP shall stop the connectionless group alerting procedure when: + +- the awaiting call is answered by a paged CTS-MS; or +- the fixed line end user hangs up before the call is answered; or + +- the call is answered by another device (e.g. answering machine); or +- the paging timer expires. + +The connectionless group alerting procedure could be resumed if the call establishment failed. + +The CTS-MSs shall consider that the connectionless group alerting procedure has been ended by the CTS-FP when CTS GROUP ALERTING REQUEST message has not been received within the 3 latest occurrences of the CTSPCH. The CTS-MSs shall stop alerting. + +![Sequence diagram showing the connectionless group alerting and response sequence between USER, CTS-MS, and CTS-FP.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +``` + +sequenceDiagram + participant USER + participant CTS-MS + participant CTS-FP + + Note left of USER: USER ALERTING + CTS-FP->>CTS-MS: CTS GROUP ALERTING REQUEST [CTSPCH] + Note left of USER: OFF HOOK + CTS-MS->>CTS-FP: CTS ACCESS REQUEST (CTSMSI) [CTSARCH] + CTS-FP->>CTS-MS: CTS IMMEDIATE ASSIGNMENT [CTSAGCH] + CTS-MS->>CTS-FP: SABM (CM SERVICE REQUEST) [DCCH] + CTS-FP->>CTS-MS: UA (CM SERVICE REQUEST) [DCCH] + Note right of CTS-FP: {AUTHENTICATION & CIPHERING} + CTS-MS->>CTS-FP: CC SETUP [DCCH] + Note right of CTS-FP: {//} + CTS-FP->>CTS-MS: CC CONNECT [DCCH] + +``` + +Sequence diagram showing the connectionless group alerting and response sequence between USER, CTS-MS, and CTS-FP. + +Figure 4.4/GSM 04.56: connectionless group alerting and response sequence + +#### 4.2.2.5 CTS system information broadcasting + +CTS SYSTEM INFORMATION TYPE 1, 2 or 3 may be broadcast by the CTS-FP on the CTSPCH channel. + +CTS SYSTEM INFORMATION TYPE 1, 2 or 3 may be sent to the attached CTS-MSs when the TFH list or the TFH parameters need to be changed. + +The information broadcast may be group in the following classes: + +- information about the frequency list to used; +- information about the Total Frequency Hopping parameters to used. + +### 4.3 RR connection establishment + +#### 4.3.1 RR connection establishment initiated by the mobile station + +The purpose of the immediate assignment procedure is to establish an RR connection between the mobile station and the CTS-FP. + +#### 4.3.1.1 Entering the dedicated mode: immediate assignment procedure + +The immediate assignment procedure can only be initiated by the RR entity of the mobile station. Initiation is triggered by request from the MM sublayer to enter the dedicated mode or by the RR entity in response to a CTS PAGING REQUEST message. Upon such a request: + +- if access to the CTS-FP is allowed (as defined in subclause 4.3.1.1.1), the RR entity of the mobile station initiates the immediate assignment procedure as defined in subclause 4.3.1.1.2; +- otherwise, it rejects the request. + +The request from the MM sublayer to establish an RR connection specifies an establishment cause. Similarly, the request from the RR entity to establish a RR connection in response to a paging message specifies one of the establishment causes "answer to paging". + +##### 4.3.1.1.1 Permission to access the CTS-FP + +Access to the CTS-FP is allowed to any enrolled CTS-MS when the CTSBCH status field indicates idle. CTS-MS shall not try to access the CTS-FP when the status field indicates busy and it shall continue to decode CTSBCH and if needed CTSPCH or CTSAGCH. + +##### 4.3.1.1.2 Initiation of the immediate assignment procedure + +The RR entity of the CTS-MS initiates the immediate assignment procedure by scheduling the sending on the CTSARCH and leaving idle mode. It then send maximally $M_{CTS} + 1$ CTS ACCESS REQUEST messages on the CTSARCH. + +The CTS ACCESS REQUEST messages are sent on the non-hopping CTSARCH for the enrolment and attachment MM-procedures and on the hopping CTSARCH for the other cases. They contain as parameters: + +- an establishment cause which corresponds to the establishment causes given by the MM sublayer or which corresponds to one of the establishment causes "answer to paging" given by the RR entity in response to a CTS PAGING REQUEST message; +- the CTS-MS Mobile Subscriber Identity. + +After sending the first CTS ACCESS REQUEST, the CTS-MS shall start listening continuously to the CTSAGCH. After having sent $M_{CTS} + 1$ CTS ACCESS REQUEST messages, the CTS-RR entity of the CTS-MS shall start timer $T_{C3150}$ . At expiry of this timer, the immediate assignment procedure is aborted. If the immediate assignment procedure was triggered by a request from the CTS-MM sublayer, a access failure is indicated to the CTS-MM sublayer. + +##### 4.3.1.1.3 Answer from the CTS-FP + +###### 4.3.1.1.3.1 On receipt of a CTS ACCESS REQUEST message + +The CTS-FP may allocate a dedicated channel to the CTS-MS by sending an CTS IMMEDIATE ASSIGNMENT message in unacknowledged mode. Timer $T_{C3103}$ is then started by the CTS-RR layer of the CTS-FP. + +The CTS IMMEDIATE ASSIGNMENT message contains: + +- the access request reference (cause, CTSMSI); +- the description of the dedicated channel; +- optionally the multiframe number reference. + +###### 4.3.1.1.3.2 Assignment rejection + +If no channel is available for assignment, the CTS-FP may send to the CTS-MS a CTS IMMEDIATE ASSIGNMENT REJECT in unacknowledged mode in the CTSAGCH channel. This message contains an access request reference and a wait indication. + +#### 4.3.1.1.4 Assignment completion + +The immediate assignment procedure is terminated on the CTS-FP side when the main signalling link is established. Timer $T_{C3103}$ is stopped and the MM sublayer on the CTS-FP side is informed that the RR entity has entered the dedicated mode. + +On the mobile station side, the procedure is terminated when the establishment of the main signalling link is confirmed. The MM sublayer is informed that the RR entity has entered the dedicated mode. + +##### 4.3.1.1.4.1 Early classmark sending + +Early classmark sending consists in the mobile station sending as early as possible after access a CTS CLASSMARK CHANGE message to provide the CTS-FP with additional classmark information. + +A mobile station which implements the "Controlled Early Classmark Sending" option shall indicate it in the classmark (ES IND bit). + +#### 4.3.1.1.5 Abnormal cases + +If a lower layer failure occurs on the mobile station side on the new channel before the successful establishment of the main signalling link, the allocated channels are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the failure is due to information field mismatch in the contention resolution procedure, see subclause 4.1.5, and no repetition as described in this paragraph has been performed, the immediate assignment procedure shall be repeated. +- If the failure is due to any other reason or if a repetition triggered by a contention resolution failure has been performed. The mobile station returns to idle mode (RR connection establishment failure), transactions in progress are aborted and cell reselection then may take place. + +### 4.3.2 Paging procedure for RR connection establishment + +The CTS-FP can initiate the establishment of an RR connection by the paging procedure for RR connection establishment. Such a procedure can only be initiated by the CTS-FP. + +#### 4.3.2.1 Paging initiation by the CTS-FP + +The CTS-FP initiates the paging procedure by broadcasting a CTS PAGING REQUEST message on the CTSPCH subchannel and starts timer $T_{C3104}$ . The CTSPCH indicator flag shall be set to "*CTSPCH to decode*" and the CTSBCH-SB Status field shall be set to idle. + +A CTS PAGING REQUEST message may include more than one CTS-MS identification. Only Assigned Individual CTSMSIs are allowed in a CTS PAGING REQUEST message. + +The CTS-MS is required to receive and analyse the paging messages sent on the CTSPCH according to the multiframe paging period. + +#### 4.3.2.2 Paging response + +Upon receipt of an CTS PAGING REQUEST, the addressed CTS-MS shall initiate the immediate assignment procedure as specified in subclause 4.3.1 The establishment of the main signalling link is then initiated by the use of an SABM with information field containing the paging response message. The MM sublayer in the CTS-MS is informed that an CTS-RR connection exists. + +Upon receipt of the paging response message, timer $T_{C3104}$ is stopped and the MM sublayer in the CTS-FP is informed that a CTS-RR connection exits. + +#### 4.3.2.3 Abnormal cases + +The CTS-FP shall abort the paging procedure when: + +- an end of paging procedure is triggered by the upper layer i.e.: + - the fixed line end user hangs up before the call is answered; or + +- the call is answered by another device (e.g. answering machine); or +- the call is forwarded; or +- the paging timer expires. + +If timer TC3104 expires and a valid CTS PAGING RESPONSE message has not been received, a specific failure indication shall be triggered to the upper layer and the CTS-FP upper layer may repeat the paging procedure. + +![Sequence diagram of individual paging sequence between CTS-MS and CTS-FP.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +``` + +sequenceDiagram + participant CTS-MS + participant CTS-FP + Note right of CTS-FP: Start TC3104 + CTS-FP->>CTS-MS: CTS PAGING REQUEST (CTSMSI) [CTSPCH] + CTS-MS->>CTS-FP: CTS ACCESS REQUEST (CTSMSI) [CTSARCH] + Note right of CTS-FP: Start TC3103 + CTS-FP->>CTS-MS: CTS IMMEDIATE ASSIGNMENT [CTSAGCH] + CTS-MS->>CTS-FP: SABM (CTS PAGING RESPONSE) [DCCH] + Note right of CTS-FP: Stop TC3103 + Note right of CTS-FP: Stop TC3104 + +``` + +Sequence diagram of individual paging sequence between CTS-MS and CTS-FP. + +Figure 4.5/GSM 04.56: individual paging sequence + +## 4.4 Procedures in dedicated mode + +Procedures described in this subclause apply to the dedicated mode. + +Direct transition between dedicated mode and group transmit mode is possible in both directions by use of the following procedures: + +- Channel assignment procedure; +- Channel mode modify procedure. + +### 4.4.1 SACCH procedures + +#### 4.4.1.1 General + +In RR connected mode, the SACCH is used in signalling at least for measurement results transmission from the CTS-MS. Continuous transmission must occur in both directions. For that purpose, in CTS-MS to CTS-FP direction, measurement result messages are sent at each possible occasion when nothing else has to be sent. Similarly, empty UI frames are sent in the CTS-FP to CTS-MS direction when nothing else has to be sent. + +#### 4.4.1.2 Measurement report + +When in RR connected mode, the CTS-MS regularly sends CTS MEASURMENT REPORT messages to the CTS-FP. These messages contain measurement results about reception characteristics from the current cell. They are sent on the slow ACCH, in unacknowledged mode. If no other message is scheduled on the SACCH at the instant when a layer 2 frame is due to be sent, then the CTS-MS shall send a CTS MEASUREMENT REPORT message. The interval between two successive layer 2 frame containing CTS MEASUREMENT REPORT messages shall not exceed one layer 2 frame. + +### 4.4.2 Transfer of messages and link layer service provision + +When in dedicated mode or in group transmit mode, upper layers can send messages in multiframe or unacknowledged mode on SAPI 0. + +Moreover, but only when in dedicated mode, upper layers have access to the full link layer services for SAPIs other than 0, with the exception of the error indication and local end release that are directly treated by the RR sublayer, as specified in particular places of clause 4. + +### 4.4.3 Intracell handover procedure + +In dedicated mode, an intracell change of channel can be requested by upper layers for changing the channel type, or decided by the RR sublayer, e.g. for an internal handover. This change may be performed through the dedicated channel assignment procedure. + +The purpose of the channel assignment procedure is to completely modify the physical channel configuration of the mobile station without frequency redefinition or change in synchronisation while staying in the same CTS-cell. + +This procedure shall not be used for changing between dependent configurations, i.e. those sharing Radio Resource for the main signalling link. An example of dependent channels is a full rate channel and one of the corresponding half rate channels. In multislot operation however, it is allowed to use the same timeslots before and after the assignment, as long as the main signalling link has been changed. The only procedures provided for changing between dependent configurations for the main signalling link are the additional assignment and the partial release procedures. + +The channel assignment procedure happens only in dedicated mode. This procedure cannot be used in the idle mode; in this case the immediate assignment procedure is used. + +The channel assignment procedure includes: + +- the suspension of normal operation except for RR management (layer 3); +- the release of the main signalling link, and of the other data links as defined in subclause 4.1.4, and the disconnection of TCHs if any; +- the deactivation of previously assigned channels (layer 1); +- the activation of the new channels and their connection if applicable; +- the triggering of the establishment of the data link connections for SAPI = 0. + +The channel assignment procedure is always initiated by the CTS-FP. + +#### 4.4.3.1 Intracell handover initiation + +The CTS-FP initiates the intracell handover procedure by sending a CTS INTRACELL HANDOVER COMMAND message to the CTS-MS on the main signalling link. The CTS-FP then starts timer $T_{C3105}$ . When sending this message on the CTS-FP side, and receiving it on the CTS-MS side, all transmission of signalling layer message except for those RR messages needed for this procedure and for abnormal cases is suspended until resumption is indicated. + +Upon receipt of the CTS INTRACELL HANDOVER COMMAND message, the CTS-MS initiates a local end release of link layer connections, disconnects the physical channels, commands the switching to the assigned channel and initiates the establishment of lower layer connections. + +The CTS-MS shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the CTS-MS shall access the channel as an immediate reaction to the reception of the message. + +#### 4.4.3.2 Intracell handover completion + +After the main signalling link is successfully established, the CTS-MS returns a CTS INTRACELL HANDOVER COMPLETE message specifying cause "normal event" to the CTS-FP on the main DCCH. + +The sending of this message on the CTS-MS side and its receipt on the CTS-FP side allow the resumption of the transmission of signalling layer messages other than those belonging to RR management. + +At the receipt of the CTS INTRACELL HANDOVER, the CTS-FP releases the previously allocated resources and stops timer $T_{C3105}$ . + +#### 4.4.3.3 Abnormal cases + +If the CTS INTRACELL HANDOVER COMMAND instruct the CTS-MS to use a parameter that it is not capable of, then the CTS-MS shall return a CTS INTRACELL HANDOVER FAILURE message, and the CTS-MS shall remain on the current channel(s) and use the old channel description or channel mode. + +When receiving a CTS INTRACELL HANDOVER FAILURE message, the CTS-FP stops $T_{C3105}$ . + +On the CTS-FP side, if timer $T_{C3105}$ elapses before either the CTS INTRACELL HANDOVER COMPLETE message has been received on the new channel or a CTS INTRACELL HANDOVER FAILURE message is received or the CTS-MS has re-established the call, the old and the new channels are released and all contexts related to the connection with that CTS-MS are cleared. + +#### 4.4.4 Intercell handover procedure + +Intercell handover is a CTS phase 2 issue. + +#### 4.4.5 Frequency hopping definition procedure + +This procedure is used by the CTS-FP to update the Total Frequency Hopping List and Total Frequency Hopping parameters in the MS. The CTS-FP send a CTS FREQUENCY HOPPING DEFINITION message containing the new parameters together with a reference time indication. The TFH parameters are split in general static parameters and current dynamic parameters which are valid for a given TDMA frame number. The values indicated by the current parameters IE are those used by the TFH algorithm at the frame number indicated by the reference time. These parameters shall be used after the RR connection is released when the MS is returning in idle mode. + +#### 4.4.6 Channel mode modify procedure + +In dedicated mode, higher layers can request the setting of the channel mode. + +The channel mode modify procedure allows the CTS-FP to request the mobile station to set the channel mode for one channel or one channel set. The channel mode covers the coding, decoding and transcoding mode used on the indicated channel. + +This procedure is always initiated by the CTS-FP. + +NOTE: Direct transitions between full rate speech coder version 1 and full rate speech coder version 2 (and vice versa) may cause unpleasant audio bursts. + +##### 4.4.6.1 Normal channel mode modify procedure + +###### 4.4.6.1.1 Initiation of the channel mode modify procedure + +The FP initiates the procedure by sending a message CTS CHANNEL MODE MODIFY to the CTS-MS. This message contains: + +- a channel description of the channel(s) on which the specified mode shall be applied; and +- the mode to be used on that channel. + +###### 4.4.6.1.2 Completion of channel mode modify procedure + +When it has received the CTS CHANNEL MODE MODIFY message, the CTS-MS sets the mode for the indicated channel, and if that is in a multislot configuration, the whole channel set and then replies by a CTS CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the ordered channel mode. + +This applies whether the mode commanded by the CTS CHANNEL MODE MODIFY message is different from the one used by the CTS-MS or whether it is already in use. + +###### 4.4.6.1.3 Abnormal cases + +No specific action for a lower layer failure is specified in this subclause. If the mobile station does not support the indicated mode, it shall retain the old mode and return the associated channel mode information in CTS CHANNEL MODE MODIFY message. + +#### 4.4.7 Ciphering mode setting procedure + +In dedicated mode, the ciphering mode setting procedure is used by the FP to set the ciphering mode, i.e. whether or not the transmission is ciphered, and if so which algorithm to use. The procedure shall only be used to change from "not ciphered" mode to "ciphered" mode, or vice-versa, or to pass a CTS CIPHERING MODE COMMAND message to the mobile station while remaining in the "not ciphered" mode. The ciphering mode setting procedure is always triggered by the FP and it only applies to dedicated resources. + +#### 4.4.7.1 Ciphering mode setting initiation + +The CTS-FP initiates the ciphering mode setting procedure by sending a CTS CIPHERING MODE COMMAND message to the mobile station on the main signalling link, indicating whether ciphering shall be used or not, and if yes which algorithm to use. + +The new mode is applied for reception on the CTS-FP side after the message has been sent. + +#### 4.4.7.2 Ciphering mode setting completion + +Whenever the CTS-MS receives a CTS CIPHERING MODE COMMAND message, it shall, if a SIM is present and considered valid by the mobile equipment and the ciphering key sequence number stored on the SIM indicates that a CTS ciphering key is available, load the ciphering key stored on the SIM into the ME. A valid CTS CIPHERING MODE COMMAND message is defined to be one of the following: + +- one that indicates "start ciphering" and is received by the mobile station in the "not ciphered" mode; +- one that indicates "no ciphering" and is received by the MS in the "not ciphered" mode; or +- one that indicates "no ciphering" and is received by the mobile station in the "ciphered" mode. + +Other CTS CIPHERING MODE COMMAND messages shall be regarded as erroneous, an CTS RR STATUS message with cause "Protocol error unspecified" shall be returned, and no further action taken. + +Upon receipt of the CTS CIPHERING MODE COMMAND message indicating ciphering, the mobile station shall start transmission and reception in the indicated mode. + +When the appropriate action on the CTS CIPHERING MODE COMMAND has been taken, the mobile station sends back a CTS CIPHERING MODE COMPLETE message. If the "cipher response" field of the cipher response information element in the CTS CIPHERING MODE COMMAND message specified "IMEI must be included" the mobile station shall include its IMEISV in the CTS CIPHERING MODE COMPLETE message. + +Upon receipt of the CTS CIPHERING MODE COMPLETE message or any other correct layer 2 frame which was sent in the new mode, the CTS-FP starts transmission in the new mode. + +![Sequence diagram showing the ciphering mode setting sequence between CTS-MS and CTS-FP. The CTS-FP sends a CTS CIPH MOD CMD message to the CTS-MS. The CTS-MS starts transmission and reception in the new mode upon receipt. The CTS-MS then sends a CTS CIPH MOD COM message back to the CTS-FP. The CTS-FP starts reception in the new mode upon receipt of the command and starts transmission in the new mode upon receipt of the complete message.](ead623e6a8ec701df64567695a57d01c_img.jpg) + +``` + +sequenceDiagram + participant CTS-MS + participant CTS-FP + Note left of CTS-MS: start transmission and reception in new mode + CTS-FP->>CTS-MS: CTS CIPH MOD CMD + Note right of CTS-FP: start reception in new mode + CTS-MS->>CTS-FP: CTS CIPH MOD COM + Note right of CTS-FP: start transmission in new mode + +``` + +Sequence diagram showing the ciphering mode setting sequence between CTS-MS and CTS-FP. The CTS-FP sends a CTS CIPH MOD CMD message to the CTS-MS. The CTS-MS starts transmission and reception in the new mode upon receipt. The CTS-MS then sends a CTS CIPH MOD COM message back to the CTS-FP. The CTS-FP starts reception in the new mode upon receipt of the command and starts transmission in the new mode upon receipt of the complete message. + +Figure 4.6/GSM 04.56: Ciphering mode setting sequence + +#### 4.4.8 [Reserved: Additional channel assignment procedure] + +This is a CTS phase 2 issue. + +#### 4.4.9 [Reserved: Partial channel release procedure] + +This is a CTS phase 2 issue. + +#### 4.4.10 Classmark change procedure + +In dedicated mode, this procedure allows the mobile station to indicate to the CTS-FP a change of characteristics reflected in the classmark (e.g. due to addition of power amplification). Furthermore, a mobile station which implements the "controlled early classmark sending" option may also send a CTS CLASSMARK CHANGE message as described in subclause 4.3.1.1.4, even if no change of characteristics has occurred. + +The mobile station sends a CTS CLASSMARK CHANGE message to the CTS-FP. This message contains the new mobile station classmark 2 information element. It may also contain a Classmark 3 Information Element. There is no acknowledgement from the CTS-FP at layer 3. + +#### 4.4.11 Classmark interrogation procedure + +This procedure allows the CTS-FP to request additional classmark information from the mobile station (e.g. if the information initially sent by the mobile station is not sufficient for CTS-FP decisions). + +The CTS-FP initiate the classmark interrogation procedure by sending a CTS CLASSMARK ENQUIRY message to the CTS-MS on the main DCCH. + +on receipt of the CTS CLASSMARK ENQUIRY message, the CTS-MS sends a CTS CLASSMARK CHANGE message to the CTS-FP on the main DCCH. + +#### 4.4.12 [Reserved] + +#### 4.4.13 RR connection release procedure + +##### 4.4.13.1 Normal release procedure + +The release of the RR connection can be requested by upper layers. + +The purpose of this procedure is to deactivate all the dedicated channels in use for this RR connection. When the channels are released, the mobile station returns to the idle mode. The channel release procedure can be used in a variety of cases, including TCH release after a call release, and DCCH release when a dedicated channel allocated for signalling is released. + +In dedicated mode, the channel release procedure is always initiated by the CTS-FP. + +###### 4.4.13.1.1 Channel release procedure initiation + +The CTS-FP initiates the channel release procedure by sending a CTS CHANNEL RELEASE message to the CTS-MS on the main DCCH, starts timer $T_{C3106}$ and deactivates the SACCH. + +On receipt of a CTS CHANNEL RELEASE message, the CTS-MS starts timer $T_{C3151}$ and disconnect the main signalling link. When $T_{C3151}$ times out or when the disconnection is confirmed, the CTS-MS deactivates all signalling link, considers the RR connection as released, and returns to idle mode. + +On CTS-FP side, when the main signalling link is disconnected, the CTS-FP stops timer $T_{C3106}$ and starts timer $T_{C3107}$ . When timer $T_{C3107}$ times out, the CTS-FP deactivates the channels. If timer $T_{C3106}$ times out, the CTS-FP deactivates the channels. + +###### 4.4.13.1.2 Abnormal case + +Abnormal cases are taken into account in the main part of the description of the procedure. + +##### 4.4.13.2 Radio link fai2lure in dedicated mode + +The main part of these procedures concerns the "normal" cases, i.e. those without any occurrence of loss of communication means. A separate paragraph at the end of the description of each procedure treats the cases of loss of communication, called a radio link failure. In dedicated mode, in most of the cases the reaction of the mobile station or the CTS-FP is the same. Those reactions are described in this subclause to avoid repetitions. + +A radio link failure can be detected by several ways: + +- 1) by analysis of reception at layer 1, as specified in GSM 05.08 and subclause 4.4.1.1; +- 2) by a data link layer failure as specified in GSM 04.06, on the main signalling link. A data link failure on any other data link shall not be considered as a radio link failure; +- 3) when a lower layer failure happens while the mobile station attempts to connect back to the old channels in a channel assignment procedure or handover procedure; +- 4) in some cases where timers are started to detect the lack of answer from the other party, as described in clause 3. + +The two first cases are known by the term "lower layer failure". + +#### 4.4.13.2.1 Mobile side + +When a radio link failure is detected by the mobile station: + +- the MS shall perform a local end release on all signalling links unless otherwise specified; +- the mobile station shall deactivate all channels; +- the RR sublayer of the mobile station shall indicate an RR connection failure to the MM sublayer unless otherwise specified. + +NOTE: Upper layers may decide on a re-establishment (see subclause 5.5.4). + +#### 4.4.13.2.2 CTS-FP side + +When a radio link failure has been detected, an indication is passed to the upper sublayer on CTS-FP side. + +The CTS-FP should release the connection except when otherwise specified, either with the channel release procedure as specified in subclause 4.4.13.1 or with the following procedure. The CTS-FP start timer TC3106 and deactivates the SACCH and hence stops transmission on the SACCH. When timer TC3106 expires, the CTS-FP can regard the channel as released. + +NOTE: The CTS-FP The network should maintain for a while the transaction context in order to allow call re-establishment. + +#### 4.4.13.3 RR connection abortion in dedicated mode + +The mobile station aborts the RR connection by initiating a normal release of the main signalling link, performing local end releases on all other signalling links and disconnecting all traffic channels, if any. + +### 4.4.14 Receiving CTS RR STATUS message by a CTS-RR entity + +If the CTS-RR entity of the mobile station receives a CTS RR STATUS message no transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible. + +The actions to be taken on receiving a CTS RR STATUS message in the CTS-FP are defined in GSM 04.08. See also clause 8. + +#### 4.4.15 CTS RR parameters update + +This procedure allows the CTS-FP to provide mandatory parameters to the mobile station. It shall be initiated during enrolment and attachment MM-procedures. + +The CTS-FP sends the CTS RR PARAMETERS UPDATE message containing the relevant parameters. + +--- + +## 5 Elementary procedures for Mobility Management + +### 5.1 General + +This subclause describes the procedures used for mobility management at the CTS radio interface (Reference Point Um\*). + +The general purpose of CTS Mobility Management sublayer is to support the mobility of the mobile stations, such as informing the fixed part of its presence and providing user identity confidentiality. The CTS-MM sublayer provides also connection management services to the different entities of the upper Connection Management (CM) sublayer. + +All the CTS-MM procedures can only be performed if a CTS-RR connection has been established between the mobile station and the fixed part. If no CTS-RR connection is currently established, the CTS-MM sublayer has to initiate such establishment. + +Depending of the CTS-MM procedure, they can be initiated either by the mobile station or by the fixed part or even indifferently by one of the two parties. + +The CTS-FP may also start all mobility management procedures defined in GSM 04.08, including: + +- the GSM authentication procedure; +- the GSM identity request procedure. + +The messages defined in GSM 04.08 shall be used for these procedures. + +### 5.1.1 Type of CTS-MM procedures + +Depending on how they can be initiated, two types of CTS-MM procedures can be distinguished: + +(i) CTS-MM common procedures: + +A CTS-MM common procedure can always be initiated whilst a CTS-RR connection exists. The procedures belonging to this type are: + +- Initiated by the fixed part: + - CTS mutual authentication procedure; + - CTSMSI update procedure; + - CTS de-enrolment procedure. +- Initiated by the mobile station + - CTS detach procedure. + +(ii) CTS-MM specific procedures: + +A CTS-MM specific procedure can only be initiated if no other MM specific procedure is running or no MM connection exists. The procedures belonging to this type are: + +- Initiated by the mobile station: + - CTS enrolment procedure; + - CTS attach procedure; + - CTS re-attach procedure. +- Initiated by the fixed part: + - CTS periodic attach update procedure. + +These running procedures do not preclude from running procedures defined in the CTS supervising system layer 3 specification. + +### 5.1.2 CTS-MM sublayer states + +#### 5.1.2.1 CTS-MM sublayer states in the mobile station + +An additional machine describes the states related to the CTS. + +##### 5.1.2.1.1 Main states + +###### 1. WAIT FOR CTS-RR ACTIVE + +The CTS-MM sublayer has requested activation of the CTS-RR sublayer. + +###### 2. WAIT FOR CTS-RR CONNECTION (ENROLMENT OR ATTACH) + +The CTS-MM sublayer has requested CTS-RR connection establishment for starting the enrolment procedure or the attach one. + +###### 3. ATTACH INITIATED + +The attach procedure has been started and the CTS-MM awaits a response from the fixed part. The timer TC3250 is running. + +#### 4. ENROLMENT INITIATED + +The enrolment procedure has been started and the CTS-MM awaits a response from the fixed part. The timer TC3254 is running. + +#### 5. ATTACH REJECTED + +The attach procedure has been rejected and CTS-RR connection release is awaited. The timer TC3256 is running. + +#### 6. ENROLMENT REJECTED + +The enrolment procedure has been rejected and CTS-RR connection release is awaited. + +#### 7. AUTHENTICATION INITIATED + +The mutual authentication procedure has been started by the fixed part. + +#### 8. CTS-MM IDLE + +There is no MM procedure running and no RR connection exist. This is a compound state. + +##### 5.1.2.1.2 Substates of the CTS-MM IDLE state + +###### 8.1 NORMAL SERVICE + +The mobile station is attached to a fixed part and it is reachable. + +###### 8.2 FP SEARCH + +The mobile station is searching for fixed parts on which the mobile station is enrolled. + +###### 8.3 NO FP AVAILABLE + +No fixed part can be selected. This state is entered after a first intensive search failed. Fixed parts are searched at a low rhythm. No CTS services are offered. + +##### 5.1.2.2 CTS-MM sublayer states in the fixed part + +###### 1. IDLE + +The CTS-MM sublayer is not active. + +###### 2. WAIT FOR CTS-RR CONNECTION + +The CTS-MM sublayer has requested activation of the CTS-RR sublayer. + +###### 3. CTS-MM CONNECTION ACTIVE + +The CTS-MM sublayer has a CTS-RR connection to a mobile station. One or more MM connections are active. + +###### 4. CTS AUTHENTICATION INITIATED + +The authentication procedure has been started by the fixed part. + +###### 5. CTS DE-ENROLMENT INITIATED + +The de-enrolment procedure has been started by the fixed part. + +###### 6. CTS CIPHERING MODE INITIATED + +The cipher mode setting procedure has been requested to the CTS-RR-sublayer. + +## 5.2 CTS-MM common procedures + +### 5.2.1 CTS detach procedure + +The purpose of the CTS detach procedure is to detach a mobile station from a fixed part. The mobile station may launch the detach procedure during the CTS mode deactivation (e.g. at the power off, when the SIM is extracted, when the mobile station is set in GSM mode only). + +The CTS detach procedure is always initiated by the mobile station. + +#### 5.2.1.1 CTS detach initiation by the mobile station + +The mobile station initiates the CTS detach procedure by sending a CTS DETACH INDICATION to the fixed part. The mobile station then starts timer TC3253. + +If no RR connection exists, the MM sublayer within the mobile station will request the RR sublayer to establish a RR connection. If a RR connection exists, the MM sublayer will release locally any ongoing MM connections before the CTS DETACH INDICATION message is sent. + +#### 5.2.1.2 CTS detach procedure in the fixed part + +On reception of a CTS DETACH INDICATION, the fixed part shall consider the mobile station as detached. No response is returned to the mobile station. After reception of the CTS DETACH INDICATION message, the fixed part shall release locally any ongoing MM connections, and start the normal RR connection release procedure. + +#### 5.2.1.3 CTS detach completion by the mobile station + +Timer TC3253 is stopped when the RR connection is released. The mobile station should, if possible, delay the local release of the channel to allow a normal release from the fixed part until TC3253. If this is not possible (e.g. detach at power down) the RR sublayer on the mobile side should be aborted. + +#### 5.2.1.4 Abnormal cases + +If establishment of an RR connection is not possible, or the RR connection is lost, the CTS detach procedure is aborted by the mobile station. + +### 5.2.2 CTS de-enrolment procedure + +The purpose of the CTS de-enrolment procedure is to inform a CTS MS that it is no more enrolled on this CTS-FP. + +The CTS de-enrolment procedure is always launched by the fixed part. + +This procedure shall be launched when the mobile station has no more right to be enrolled (e.g. expiration of validity period, de-enrolment requested by the CTS operator). Any reference to this mobile station should be removed in the fixed part. + +#### 5.2.2.1 CTS de-enrolment initiation by the fixed part + +The fixed part initiates the CTS de-enrolment procedure by sending a CTS DE-ENROLMENT INDICATION to the mobile station. Then the fixed part will request the RR sublayer to release the RR connection. + +#### 5.2.2.2 CTS de-enrolment procedure in the mobile station + +On reception of a CTS DE-ENROLMENT INDICATION, the CTS-MS shall remove the corresponding CTS-FP of the list of the fixed parts on which the mobile station is enrolled. + +The mobile station should inform the user that it is no more enrolled on this CTS-FP. + +#### 5.2.2.3 Abnormal cases + +If establishment of an RR connection is not possible, or the RR connection is lost, the CTS de-enrolment procedure is aborted by the fixed part. Nevertheless, any reference to the corresponding mobile station should be removed in the fixed part. + +## 5.2.3 CTS mutual authentication procedure + +The purpose of the CTS mutual authentication procedure is: + +- to permit the fixed part to check whether the identity provided by the mobile station is acceptable or not (see GSM 03.20 annex E); +- to permit the mobile station to check whether the identity provided by the fixed part is acceptable or not (see GSM 03.20 annex E); +- to agree on required parameters between the fixed part and mobile station to calculate a new ciphering key (see GSM 03.20 annex E). + +The authentication procedure uses the CTSMSI if it is available. If it is not available or if the authentication fails using this identity, the authentication procedure shall be started again using the IMSI. + +The CTS authentication procedure is always initiated by the CTS-FP on the radio interface. + +This procedure shall be used each time an enrolment procedure or an attach procedure is started. + +### 5.2.3.1 CTS authentication initiation by the fixed part + +The fixed part initiates the CTS authentication procedure by sending a CTS MS AUTHENTICATION REQUEST message to the CTS-MS and starts the timer TC3211. + +The CTS MS AUTHENTICATION REQUEST message specifies the authentication parameter. + +### 5.2.3.2 CTS authentication response by the mobile station + +The mobile station shall be ready to respond upon a CTS MS AUTHENTICATION REQUEST message at any time whilst a CTS-RR connection exists. + +On reception of a CTS MS AUTHENTICATION REQUEST from the fixed part, the mobile station shall send a CTS MS AUTHENTICATION RESPONSE and starts the timer TC3260. + +The CTS MS AUTHENTICATION RESPONSE message specifies the authentication parameter CH2 and the authentication parameter SRES1. + +### 5.2.3.3 CTS authentication processing by the fixed part + +On reception of the CTS MS AUTHENTICATION RESPONSE from the mobile station, the fixed part shall stop the timer TC3211 and shall check the validity of the response (see GSM 03.20 annex E). + +The fixed part shall respond with a CTS FP AUTHENTICATION RESPONSE message. This message specifies the authentication parameter SRES2. + +### 5.2.3.4 CTS authentication completion by the mobile station + +On reception of the CTS FP AUTHENTICATION RESPONSE from the fixed part, the mobile station shall stop the timer TC3260 and shall check the validity of the response (see GSM 03.20 annex E). + +### 5.2.3.5 Unsuccessful authentication + +If mobile station authentication fails, i.e. the response given by the mobile station is not valid, the fixed part may distinguish between the two different ways of identification: IMSI or CTSMSI. If the mobile station identifies itself using the CTSMSI, the fixed part may request the IMSI using the identity request procedure and may start a new mutual authentication procedure using the IMSI. + +If the fixed part does not start a new authentication procedure, it shall sent a CTS MS AUTHENTICATION REJECT message to the mobile station. After having sent this message, the fixed part shall release any ongoing MM connections and shall initiate the RR connection release procedure. If fixed part authentication fails, i.e. the response given by the fixed part is not valid, the mobile station may abort the RR connection. In this case, the CTS-MS shall abort any MM ongoing procedure. + +### 5.2.3.6 Abnormal cases + +Fixed part side + +#### (a) CTS-RR connection failure + +Upon a detection of a CTS-RR connection failure before the CTS MS AUTHENTICATION RESPONSE is received, the fixed part shall release all MM connections (if any) and abort any ongoing MM specific procedure. + +#### (b) Expiry of timer TC3211 + +The mutual authentication procedure is supervised on the fixed part by the timer TC3211. At expiry of this timer the fixed part may release the CTS-RR connection. In this case the fixed part shall abort the mutual authentication procedure and any ongoing MM specific procedure, release all MM connections if any, and initiate the CTS-RR connection release procedure described in subclause 4.4.13. + +Mobile station side + +#### (a) CTS-RR connection failure + +Upon a detection of a CTS-RR connection failure before the CTS FP AUTHENTICATION RESPONSE is received, the mobile station shall release all MM connections (if any) and abort any ongoing MM specific procedure. + +#### (b) Expiry of timer TC3260 + +The mutual authentication procedure is supervised on the mobile station by the timer TC3260. At expiry of this timer the mobile station may abort the CTS-RR connection. In this case the mobile station shall abort the mutual authentication procedure and any ongoing MM specific procedure, release all MM connections if any, and initiate the CTS-RR connection release procedure described in subclause 4.4.13. + +## 5.2.4 CTSMI update procedure + +The purpose of the CTSMI update procedure is to provide identity confidentiality, i.e. to protect a user against being identified and located by an intruder (see GSM 03.20 annex E). + +The CTSMI update procedure is always initiated by the CTS-FP on the radio interface. + +The structure of the CTSMI is specified in GSM 03.03. The CTSMI has significance only for a specific CTS-FP. + +The CTSMI update procedure shall be performed after each access to the fixed part done by a mobile station + +### 5.2.4.1 CTSMI update initiation by the fixed part + +The fixed part initiates the CTSMI update procedure by sending a CTSMI UPDATE COMMAND message to the CTS-MS and starts the timer TC3202. + +The CTSMI UPDATE COMMAND message specifies the new CTSMI of the mobile station. The CTSMI UPDATE COMMAND message shall be sent to the mobile station using a CTS-RR connection in ciphering mode (see GSM 03.20 annex E). + +### 5.2.4.2 CTSMI update response by the mobile station + +Upon receipt of the CTSMI UPDATE COMMAND message the mobile station stores the new CTSMI related to the corresponding fixed part in the SIM. + +The mobile station sends a CTSMI UPDATE COMPLETE message to the fixed part. + +### 5.2.4.3 CTSMI update completion in the fixed part + +Upon receipt of the CTSMI UPDATE COMPLETE message the fixed part stops the timer TC3202 and considers the new CTSMI as valid. + +### 5.2.4.4 Abnormal cases + +Mobile station side: + +Any CTS-RR connection failure after storage of the new CTSMSI value in the SIM does not have any impact on this storage. + +Fixed part side + +(a) CTS-RR connection failure: + +If the CTS-RR connection is lost before the CTSMSI UPDATE COMPLETE message is received, all MM connections (if any) shall be released and both the old and the new CTSMSIs should be maintained in order to be able to recover from unsuccessful CTSMSI update. + +(b) No response from the mobile station (expiry of timer TC3202) + +The fixed part should maintain the old and the new CTSMSI in order to be able to recover from unsuccessful CTSMSI update. + +## 5.3 CTS-MM specific procedures + +### 5.3.1 CTS enrolment procedure + +The purpose of the CTS enrolment procedure is: + +- to define an association between a certain CTS-MS and a certain CTS-FP; +- to ensure the rights of the CTS-MS to use CTS services on this CTS-FP. + +The CTS enrolment procedure is always initiated by the mobile station. + +The user shall provide the CTS-PIN (see GSM 03.20 annex E) on the mobile station and shall take a physical action on the CTS-FP. + +#### 5.3.1.1 CTS enrolment initiation by the mobile station + +The mobile station initiates the CTS enrolment procedure by sending a CTS ENROLMENT REQUEST message to the CTS-FP. The mobile station shall start the timer TC3254. + +#### 5.3.1.2 CTS enrolment completion by the fixed part + +After mutual authentication, the fixed part shall request the mobile station identity to perform the verification of its rights to use CTS services on this fixed part. This verification is done either locally by the fixed part or by the CTS operator via the Cf interface (see GSM 03.20 annex E). Upon these rights are verified, the CTS-FP shall enrol the CTS-MS and shall send a CTS ENROLMENT ACCEPT to the mobile station. The CTS ENROLMENT ACCEPT contains the identity of the fixed part (IFPSI or IFPEI), and the first CTSMSI value of the mobile station. + +#### 5.3.1.3 CTS enrolment completion by the mobile station + +On reception of a CTS ENROLMENT ACCEPT, the CTS-MS shall stop the timer TC3254 and enters in CTS MM IDLE state. + +#### 5.3.1.4 Unsuccessful enrolment + +If the mobile station has not the rights to be enrolled, the fixed part shall send a CTS ENROLMENT REJECT message to the mobile station. This message contains a reject cause and the identity of the fixed part. + +On reception of a CTS ENROLMENT REJECT, the CTS-MS shall stop the timer TC3254 and enters in ENROLMENT REJECTED state. + +#### 5.3.1.5 Abnormal cases + +(a) CTS-RR connection failure + +If the CTS-RR connection is lost before the CTS ENROLMENT ACCEPT message is received, the enrolment procedure has failed. A new enrolment attempt may be done by the user. + +(b) No response from the fixed part (expiry of timer TC3254) + +The mobile station should warn the mobile station user. A new enrolment attempt may be done by the user. + +## 5.3.2 CTS attach procedure + +The purpose of the CTS attach procedure is to attach the corresponding mobile station to a specific fixed part. Before performing the attach procedure, the corresponding mobile station has to be enrolled on this fixed part. + +The attach procedure is always initiated by the mobile station. + +### 5.3.2.1 CTS attach initiation by the mobile station + +The mobile station initiates the CTS attach procedure by sending a CTS ATTACH REQUEST message to the CTS-FP and starts the timer TC3250. + +The CTS ATTACH REQUEST message specifies the CTSSMSI, and the classmark of the mobile station. + +### 5.3.2.2 CTS attach completion by the fixed part + +If the mobile identity corresponds to an enrolled mobile station on the CTS-FP, the fixed part shall send a CTS ATTACH ACCEPT to the mobile station. + +If the mobile station sends its CTSSMSI as identity and it does not correspond to any enrolled mobile station, the fixed part could use the identity request procedure (see GSM 04.08) to obtain the IMSI of the mobile station. If the IMSI corresponds to an enrolled mobile station, the fixed part shall complete the attachment as described before. + +The fixed part shall send a CTS ATTACH REJECT with its identity (IFPSI or IFPEI) when the mobile shall not be attached: + +- the mobile station is not enrolled on this fixed part: the reject cause shall be #4 (IMSI unknown in VLR); +- the fixed part is not able to complete all the operations it has to perform at mobile station attachment (e.g. FMC registration). + +### 5.3.2.3 CTS attach completion by the mobile station + +On reception of a CTS ATTACH ACCEPT, the mobile station shall stop the timer TC3250 and shall start the timer TC3252. + +The CTS-MS enters in CTS MM IDLE state. + +### 5.3.2.4 CTS attach rejection treatment by the mobile station + +On reception of a CTS ATTACH REJECT, the mobile station shall verify if the CTS-FP identity (IFPSI or IFPEI) is the expected one and shall stop the timer TC3250. + +If the fixed part identity is the expected one and the reject cause is equal to #4 (IMSI unknown in VLR), the mobile station shall not re-attempt to attach automatically to the same fixed part. The CTS-MS should inform the user that it is no more enrolled on this fixed part. + +If the fixed part identity is the expected one and the reject cause is different of #4, the mobile station shall not attempt to attach to any fixed part having the same FPBI before expiration of the timer TC3257. + +If the fixed part identity is not the expected one, the mobile station shall start the timer TC3256. The mobile shall not attempt to attach to any fixed part having the same FPBI before expiration of the timer TC3256. This does not forbid attachment attempts to fixed parts having an other FPBI. + +### 5.3.2.5 Abnormal cases + +(a) CTS-RR connection failure: + +Upon a detection of a CTS-RR connection failure before the CTS ATTACH ACCEPT is received, the mobile station shall abort the ongoing attach procedure and shall stop the timer TC3250. + +(b) No response from the fixed part (expiry of TC3250 timer): + +The mobile station shall start the timer TC3251. The mobile station shall not re-attempt to attach again to the same fixed part before expiry of timer TC3251. + +### 5.3.3 CTS re-attach procedure + +The purpose of the CTS re-attach procedure is to inform the presence of a mobile station to the fixed part on which it is attached. + +The CTS re-attach procedure is always started by the mobile station. + +This procedure is started at expiry of the timer TC3252. + +#### 5.3.3.1 CTS re-attach initiation by the mobile station + +The mobile station initiates the CTS re-attach procedure by sending a CTS ATTACH REQUEST message with an indication of re-attachment to the CTS-FP and starts the timer TC3255. + +#### 5.3.3.2 CTS re-attach completion by the fixed part + +On reception of a CTS ATTACH REQUEST message with an indication of re-attachment, the fixed part shall respond with a CTS ATTACH ACCEPT and shall start again the CTS periodic attach update procedure (see subclause 5.3.4). + +#### 5.3.3.3 Abnormal cases + +(a) RR connection failure: + +Upon a detection of a RR connection failure before the CTS ATTACH ACCEPT is received, the mobile station shall consider to be detached from the fixed part. + +(b) RR not available: + +If no radio resource is currently available on the fixed part (STATUS field set to busy in the BCH-SB), the timer TC3252 shall be started again with its initial value. + +(c) Expiry of timer TC3255 + +The mobile station shall be considered to be detached of the corresponding fixed part. + +### 5.3.4 CTS periodic attach update procedure + +The purpose of the CTS periodic attach update procedure is to verify the presence of the attached mobile stations. + +The CTS periodic attach update procedure is started by the fixed part when it enters the MM IDLE state. + +#### 5.3.4.1 CTS periodic attach update procedure behaviour in the fixed part + +At the begin of this procedure, the timer TC3201 is started. + +At expiry of TC3201, the MM sublayer shall trigger the RR sublayer to launch the alive check procedure (see subclause 4.2.2.3) with the CTSMSI corresponding to the mobile. + +The fixed part can trigger up to NC320 times the alive check procedure using the same CTSMSI. At the next expiry of TC3201, the fixed part shall launch the CTSMSI update procedure instead of the alive check. + +#### 5.3.4.2 Abnormal cases + +After alive check triggering done by MM, the following abnormal cases may occur: + +(a) RR not available + +The fixed part shall start again the timer TC3201 with its initial value. + +(b) No response from the mobile station + +The fixed part shall considered that the mobile station is detached. + +--- + +## 6 Elementary procedures for circuit-switched Call Control + +### 6.1 Overview + +#### 6.1.1 General + +This subclause describes the Call Control (CC) protocol, which is one of the protocols of the Connection Management (CM) sublayer (see GSM 04.07). + +As a general rule, the CC protocol on the CTS radio interface Um\* is the same as the one used in the GSM radio interface Um. However, several specific procedures are introduced: the hook flash procedure and the internal call procedure. + +### 6.2 Hook flash procedure + +The hook flash is used for the control of some fixed-line supplementary services, associated with DTMF tones. + +The mobile station shall be capable of transmitting hook flash request with the same conditions as the ones required for DTMF transmission but only on the Um\* interface. The hook flash itself is generated by the CTS-FP on the fixed line. As a general rule, the hook flash procedure is the same procedure as the one used to perform DTMF transmission except that a specific keypad value is used. The DTMF protocol control procedure is defined in GSM 04.08. + +#### 6.2.1 Hook flash request by the mobile station + +A user may cause a hook flash to be generated e.g. by depression of a key in the mobile station. The relevant action is interpreted by the mobile station as a requirement for a hook flash to be sent in a START DTMF message on an established FACCH. + +#### 6.2.2 Hook flash response by the fixed part + +Upon receiving the START DTMF message indicating "hook flash", the fixed part shall generate a hook flash on the fixed line and shall return a START DTMF ACKNOWLEDGE message to the mobile station indicating successful initiation of the procedure. + +If the fixed line can not accept the hook flash (e.g. ISDN), a START DTMF REJECT message shall be sent to the mobile station. + +#### 6.2.3 Stop hook flash request by the mobile station + +When the user indicates that the hook flash generation should cease e.g. by releasing the key the mobile station will send a STOP DTMF message to the fixed part. + +#### 6.2.4 Stop hook flash response by fixed part + +After receiving the STOP DTMF message the fixed part returns a STOP DTMF ACKNOWLEDGE message to the mobile station when it has finished to generate the hook flash on the fixed line. + +NOTE 1: The Fixed Part may implement the time limit option where the hook flash duration is controlled by the Fixed Part irrespective of the receipt of a stop hook flash request from the mobile station. The maximum duration of the hook flash to be generated on the fixed line is outside the scope of the present document and may be determined by specific regulations. + +NOTE 2: The Fixed Part shall ensure that the minimum length of hook flash and minimum gap between hook flash and tones according to specific regulations are fulfilled. + +## 6.3 Internal call procedure + +To perform an internal call, the same procedure as the one used to perform a normal call shall be used except that the internal numbering plan is used. + +--- + +## 7 Examples of structured procedures + +Clause 7 is informative. + +### 7.1 General + +Clause 7 contains examples of how the fixed part may group together the elementary procedures (i.e. the procedures defined in clauses 3 to 5) in order to provide normal service. + +#### 7.1.1 CTS paging request + +The paging procedure is used to page a mobile station to which a connection shall be established. + +Upon receipt of a CTS PAGING REQUEST message the addressed mobile station initiates the immediate assignment procedure. + +![Sequence diagram for CTS paging request](3621e1493d508bd789fec58ba8be9a40_img.jpg) + +A sequence diagram showing the interaction between a Mobile Station and a Fixed Part. The Mobile Station is on the left and the Fixed Part is on the right. A message labeled 'CTS PAGING REQUEST' is sent from the Fixed Part to the Mobile Station, indicated by a long arrow pointing left with a small arrowhead at the Mobile Station's lifeline. + +Sequence diagram for CTS paging request + +**Figure 7.1/GSM 04.56: CTS paging request** + +#### 7.1.2 CTS immediate assignment + +The CTS immediate assignment procedure is always initiated by the mobile station. It may be triggered by a CTS paging request or by a mobile originating service request. + +The mobile station sends a CTS ACCESS REQUEST message on the Access Request Channel. The fixed part responds with a CTS IMMEDIATE ASSIGNMENT message on the CTS Access Grant Channel. + +![Sequence diagram for CTS immediate assignment](b055ff69db72d9cb5197aa273d629f82_img.jpg) + +A sequence diagram showing the interaction between a Mobile Station and a Fixed Part. The Mobile Station is on the left and the Fixed Part is on the right. A message labeled 'CTS ACCESS REQUEST' is sent from the Mobile Station to the Fixed Part, indicated by a long arrow pointing right with an arrowhead at the Fixed Part's lifeline. A second message labeled 'CTS IMMEDIATE ASSIGNMENT' is sent from the Fixed Part to the Mobile Station, indicated by a long arrow pointing left with a small arrowhead at the Mobile Station's lifeline. + +Sequence diagram for CTS immediate assignment + +**Figure 7.2/GSM 04.56: CTS immediate assignment** + +#### 7.1.3 CTS mutual authentication + +The purpose of CTS mutual authentication procedure is to validate the identity provided by the mobile station and the one provided by the fixed part. It is initiated by the fixed part. The CTS mutual authentication procedure also provides the mobile station with information from which a new ciphering key can be derived. The fixed part shall use the CTS mutual authentication at the beginning of each MM connection establishment (see GSM 03.20 annex E). + +![Sequence diagram for CTS mutual authentication](11fc7b58448f884cac1a5481f7def5dc_img.jpg) + +A sequence diagram showing the interaction between a Mobile Station and a Fixed Part. The Mobile Station is on the left and the Fixed Part is on the right. The sequence of messages is: 1. 'CTS MS AUTHENTICATION REQUEST' from Fixed Part to Mobile Station (long arrow pointing left with a small arrowhead). 2. 'CTS MS AUTHENTICATION RESPONSE' from Mobile Station to Fixed Part (long arrow pointing right with an arrowhead). 3. 'CTS FP AUTHENTICATION RESPONSE' from Fixed Part to Mobile Station (long arrow pointing left with a small arrowhead). + +Sequence diagram for CTS mutual authentication + +**Figure 7.3/GSM 04.56: CTS mutual authentication** + +## 7.2 Abnormal cases + +Abnormal cases are not described in the examples of clause 7. + +## 7.3 Selected examples + +The following examples are considered: + +- enrolment; +- attachment; +- detachment; +- de-enrolment; +- mobile originating call establishment. + +### 7.3.1 Enrolment + +The enrolment procedure is always initiated by the mobile station. + +#### 7.3.1.1 Enrolment with CTS-MS identity authentication done only by the CTS-FP + +![Sequence diagram of CTS enrolment procedure between Mobile Station and Fixed Part.](e97d663314aff9c29bf8971323e6539e_img.jpg) + +The diagram illustrates the sequence of messages for CTS enrolment. It starts with the Mobile Station sending a CTS ACCESS REQUEST to the Fixed Part, which responds with a CTS IMMEDIATE ASSIGNMENT. This is followed by a CTS ENROLMENT REQUEST from the Mobile Station. The Fixed Part then initiates mutual authentication with CTS MS AUTHENTICATION REQUEST and CTS FP AUTHENTICATION RESPONSE. Next, the Fixed Part sends a CTS CIPHERING MODE COMMAND, and the Mobile Station responds with CTS CIPHERING MODE COMPLETE. The Fixed Part then sends an IDENTITY REQUEST, and the Mobile Station responds with an IDENTITY RESPONSE. Finally, the Fixed Part sends a CTS ENROLMENT ACCEPT, and the Mobile Station sends a CTS CHANNEL RELEASE. + +``` +sequenceDiagram + participant Mobile Station + participant Fixed Part + Note right of Fixed Part: RR connection establishment (MO) + Mobile Station->>Fixed Part: CTS ACCESS REQUEST + Fixed Part-->>Mobile Station: CTS IMMEDIATE ASSIGNMENT + Note right of Fixed Part: Service request + Mobile Station->>Fixed Part: CTS ENROLMENT REQUEST + Note right of Fixed Part: Mutual authentication + Fixed Part->>Mobile Station: CTS MS AUTHENTICATION REQUEST + Mobile Station-->>Fixed Part: CTS MS AUTHENTICATION RESPONSE + Fixed Part->>Mobile Station: CTS FP AUTHENTICATION RESPONSE + Note right of Fixed Part: Ciphering mode setting + Fixed Part->>Mobile Station: CTS CIPHERING MODE COMMAND + Mobile Station-->>Fixed Part: CTS CIPHERING MODE COMPLETE + Note right of Fixed Part: MS identity + Fixed Part->>Mobile Station: IDENTITY REQUEST + Mobile Station-->>Fixed Part: IDENTITY RESPONSE + Fixed Part->>Mobile Station: CTS ENROLMENT ACCEPT + Mobile Station->>Fixed Part: CTS CHANNEL RELEASE +``` + +Sequence diagram of CTS enrolment procedure between Mobile Station and Fixed Part. + +Figure 7.4/GSM 04.56: CTS enrolment + +### 7.3.1.2 Enrolment with CTS MS authentication done by CTS operator + +![Sequence diagram showing Mobile Station and Fixed Part interactions for CTS enrolment. The diagram includes messages such as CTS ACCESS REQUEST, CTS IMMEDIATE ASSIGNMENT, CTS ENROLMENT REQUEST, CTS MS AUTHENTICATION REQUEST, CTS MS AUTHENTICATION RESPONSE, CTS FP AUTHENTICATION RESPONSE, CTS CIPHERING MODE COMMAND, CTS CIPHERING MODE COMPLETE, IDENTITY REQUEST, IDENTITY RESPONSE, AUTHENTICATION REQUEST, AUTHENTICATION RESPONSE, CTS ENROLMENT ACCEPT, and CTS CHANNEL RELEASE. Annotations on the right side describe the purpose of these messages, such as 'RR connection establishment (MO)', 'Service request', 'Mutual authentication', 'Ciphering mode setting', 'MS identity', and 'Authentication with CTS-SN'.](838c31609fac483fa2c01c7896a2fd6d_img.jpg) + +The diagram illustrates the sequence of messages for CTS enrolment between a Mobile Station (MS) and a Fixed Part (FP). The interaction is as follows: + +- The MS sends a **CTS ACCESS REQUEST** to the FP, which triggers **RR connection establishment (MO)**. +- The FP responds with **CTS IMMEDIATE ASSIGNMENT**. +- The MS then sends a **CTS ENROLMENT REQUEST**, which is a **Service request**. +- The FP initiates **Mutual authentication** with a **CTS MS AUTHENTICATION REQUEST**. +- The MS responds with **CTS MS AUTHENTICATION RESPONSE**. +- The FP completes the authentication with **CTS FP AUTHENTICATION RESPONSE**. +- The FP then sends a **CTS CIPHERING MODE COMMAND**, which is a **Ciphering mode setting**. +- The MS responds with **CTS CIPHERING MODE COMPLETE**. +- The FP sends an **IDENTITY REQUEST** to get the **MS identity**. +- The MS responds with **IDENTITY RESPONSE**. +- The FP then initiates **Authentication with CTS-SN** with an **AUTHENTICATION REQUEST**. +- The MS responds with **AUTHENTICATION RESPONSE**. +- The FP sends a **CTS ENROLMENT ACCEPT**. +- Finally, the MS sends a **CTS CHANNEL RELEASE**. + +Sequence diagram showing Mobile Station and Fixed Part interactions for CTS enrolment. The diagram includes messages such as CTS ACCESS REQUEST, CTS IMMEDIATE ASSIGNMENT, CTS ENROLMENT REQUEST, CTS MS AUTHENTICATION REQUEST, CTS MS AUTHENTICATION RESPONSE, CTS FP AUTHENTICATION RESPONSE, CTS CIPHERING MODE COMMAND, CTS CIPHERING MODE COMPLETE, IDENTITY REQUEST, IDENTITY RESPONSE, AUTHENTICATION REQUEST, AUTHENTICATION RESPONSE, CTS ENROLMENT ACCEPT, and CTS CHANNEL RELEASE. Annotations on the right side describe the purpose of these messages, such as 'RR connection establishment (MO)', 'Service request', 'Mutual authentication', 'Ciphering mode setting', 'MS identity', and 'Authentication with CTS-SN'. + +Figure 7.5/GSM 04.56: CTS enrolment + +## 7.3.2 Attachment + +The attachment procedure is always initiated by the mobile station. + +![Sequence diagram for CTS attachment procedure between Mobile Station and Fixed Part.](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +``` + +sequenceDiagram + participant Mobile Station + participant Fixed Part + Note right of Fixed Part: RR connection establishment (MO) + Mobile Station->>Fixed Part: CTS ACCESS REQUEST + Fixed Part-->>Mobile Station: CTS IMMEDIATE ASSIGNMENT + Note right of Fixed Part: Service request + Mobile Station->>Fixed Part: CTS ATTACH REQUEST + Note right of Fixed Part: Mutual authentication + Fixed Part-->>Mobile Station: CTS MS AUTHENTICATION REQUEST + Mobile Station-->>Fixed Part: CTS MS AUTHENTICATION RESPONSE + Fixed Part-->>Mobile Station: CTS FP AUTHENTICATION RESPONSE + Note right of Fixed Part: Ciphering mode setting + Fixed Part-->>Mobile Station: CTS CIPHERING MODE COMMAND + Mobile Station-->>Fixed Part: CTS CIPHERING MODE COMPLETE + Note right of Fixed Part: CTSMSI updating + Fixed Part-->>Mobile Station: CTS MSI UPDATE COMMAND + Mobile Station-->>Fixed Part: CTS MSI UPDATE COMPLETE + Note right of Fixed Part: + Mobile Station->>Fixed Part: CTS ATTACH ACCEPT + Fixed Part-->>Mobile Station: + Note right of Fixed Part: + Mobile Station->>Fixed Part: CTS CHANNEL RELEASE + Fixed Part-->>Mobile Station: + +``` + +The diagram illustrates the CTS attachment procedure. It begins with the Mobile Station sending a CTS ACCESS REQUEST to the Fixed Part, which responds with a CTS IMMEDIATE ASSIGNMENT, labeled as 'RR connection establishment (MO)'. Next, the Mobile Station sends a CTS ATTACH REQUEST, labeled as 'Service request'. The Fixed Part responds with a CTS MS AUTHENTICATION REQUEST, initiating 'Mutual authentication'. The Mobile Station replies with a CTS MS AUTHENTICATION RESPONSE, and the Fixed Part completes this with a CTS FP AUTHENTICATION RESPONSE. The Fixed Part then sends a CTS CIPHERING MODE COMMAND, labeled as 'Ciphering mode setting', to which the Mobile Station responds with a CTS CIPHERING MODE COMPLETE. The Fixed Part sends a CTS MSI UPDATE COMMAND, labeled as 'CTSMSI updating', and the Mobile Station responds with a CTS MSI UPDATE COMPLETE. Finally, the Mobile Station sends a CTS ATTACH ACCEPT, and the Fixed Part responds with a CTS CHANNEL RELEASE. + +Sequence diagram for CTS attachment procedure between Mobile Station and Fixed Part. + +Figure 7.6/GSM 04.56: CTS attachment + +## 7.3.3 Detachment + +The detachment procedure is always initiated by the mobile station. + +![Sequence diagram for CTS detachment procedure between Mobile Station and Fixed Part.](0908107b858fa3783d10d93b3a3444b2_img.jpg) + +``` + +sequenceDiagram + participant Mobile Station + participant Fixed Part + Note right of Fixed Part: RR connection establishment (MO) + Mobile Station->>Fixed Part: CTS ACCESS REQUEST + Fixed Part-->>Mobile Station: CTS IMMEDIATE ASSIGNMENT + Note right of Fixed Part: Service request + Mobile Station->>Fixed Part: CTS DETACH INDICATION + Note right of Fixed Part: + Mobile Station->>Fixed Part: CTS CHANNEL RELEASE + Fixed Part-->>Mobile Station: + +``` + +The diagram illustrates the CTS detachment procedure. It starts with the Mobile Station sending a CTS ACCESS REQUEST to the Fixed Part, which responds with a CTS IMMEDIATE ASSIGNMENT, labeled as 'RR connection establishment (MO)'. The Mobile Station then sends a CTS DETACH INDICATION, labeled as 'Service request'. Finally, the Mobile Station sends a CTS CHANNEL RELEASE, and the Fixed Part responds with a CTS CHANNEL RELEASE. + +Sequence diagram for CTS detachment procedure between Mobile Station and Fixed Part. + +Figure 7.7/GSM 04.56: CTS detachment + +### 7.3.4 De-enrolment + +The de-enrolment procedure is always initiated by the fixed part. + +![Sequence diagram showing the CTS de-enrolment procedure between a Mobile Station and a Fixed Part. The sequence includes: 1. CTS PAGING REQUEST (Fixed Part to Mobile Station) - RR connection establishment (MT); 2. CTS ACCESS REQUEST (Mobile Station to Fixed Part); 3. CTS IMMEDIATE ASSIGNMENT (Fixed Part to Mobile Station); 4. CTS PAGING RESPONSE (Mobile Station to Fixed Part); 5. CTS MS AUTHENTICATION REQUEST (Mobile Station to Fixed Part) - Mutual authentication; 6. CTS MS AUTHENTICATION RESPONSE (Fixed Part to Mobile Station); 7. CTS FP AUTHENTICATION RESPONSE (Mobile Station to Fixed Part); 8. CTS CIPHERING MODE COMMAND (Fixed Part to Mobile Station) - Ciphering mode setting; 9. CTS CIPHERING MODE COMPLETE (Mobile Station to Fixed Part); 10. CTS DE-ENROLMENT INDICATION (Fixed Part to Mobile Station) - De-enrolment indication; 11. CTS CHANNEL RELEASE (Mobile Station to Fixed Part).](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +``` +sequenceDiagram + participant Mobile Station + participant Fixed Part + Note right of Fixed Part: RR connection establishment (MT) + Fixed Part->>Mobile Station: CTS PAGING REQUEST + Mobile Station->>Fixed Part: CTS ACCESS REQUEST + Fixed Part->>Mobile Station: CTS IMMEDIATE ASSIGNMENT + Mobile Station->>Fixed Part: CTS PAGING RESPONSE + Note right of Fixed Part: Mutual authentication + Mobile Station->>Fixed Part: CTS MS AUTHENTICATION REQUEST + Fixed Part->>Mobile Station: CTS MS AUTHENTICATION RESPONSE + Mobile Station->>Fixed Part: CTS FP AUTHENTICATION RESPONSE + Note right of Fixed Part: Ciphering mode setting + Fixed Part->>Mobile Station: CTS CIPHERING MODE COMMAND + Mobile Station->>Fixed Part: CTS CIPHERING MODE COMPLETE + Note right of Fixed Part: De-enrolment indication + Fixed Part->>Mobile Station: CTS DE-ENROLMENT INDICATION + Mobile Station->>Fixed Part: CTS CHANNEL RELEASE +``` + +Sequence diagram showing the CTS de-enrolment procedure between a Mobile Station and a Fixed Part. The sequence includes: 1. CTS PAGING REQUEST (Fixed Part to Mobile Station) - RR connection establishment (MT); 2. CTS ACCESS REQUEST (Mobile Station to Fixed Part); 3. CTS IMMEDIATE ASSIGNMENT (Fixed Part to Mobile Station); 4. CTS PAGING RESPONSE (Mobile Station to Fixed Part); 5. CTS MS AUTHENTICATION REQUEST (Mobile Station to Fixed Part) - Mutual authentication; 6. CTS MS AUTHENTICATION RESPONSE (Fixed Part to Mobile Station); 7. CTS FP AUTHENTICATION RESPONSE (Mobile Station to Fixed Part); 8. CTS CIPHERING MODE COMMAND (Fixed Part to Mobile Station) - Ciphering mode setting; 9. CTS CIPHERING MODE COMPLETE (Mobile Station to Fixed Part); 10. CTS DE-ENROLMENT INDICATION (Fixed Part to Mobile Station) - De-enrolment indication; 11. CTS CHANNEL RELEASE (Mobile Station to Fixed Part). + +Figure 7.8/GSM 04.56: CTS de-enrolment + +### 7.3.5 Mobile originating call establishment + +The mobile station initiates immediate assignment, service request using the CM SERVICE REQUEST message, and contention resolution. + +![Sequence diagram of Mobile originating call establishment between Mobile Station and Fixed Part.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant MS as Mobile Station + participant FP as Fixed Part + Note right of FP: RR connection establishment (MO) + MS->>FP: CTS ACCESS REQUEST + FP-->>MS: CTS IMMEDIATE ASSIGNMENT + Note right of FP: Service request + MS->>FP: CM SERVICE REQUEST + Note right of FP: Mutual authentication + FP-->>MS: CTS MS AUTHENTICATION REQUEST + MS-->>FP: CTS MS AUTHENTICATION RESPONSE + FP-->>MS: CTS FP AUTHENTICATION RESPONSE + Note right of FP: Ciphering mode setting + FP-->>MS: CTS CIPHERING MODE COMMAND + MS-->>FP: CTS CIPHERING MODE COMPLETE + Note right of FP: CTMSI updating + FP-->>MS: CTS MSI UPDATE COMMAND + MS-->>FP: CTS MSI UPDATE COMPLETE + Note right of FP: Call initiation + MS->>FP: SET UP + FP-->>MS: CALL PROCEEDING + Note right of FP: Channel Assignment + FP-->>MS: + MS-->>FP: + Note right of FP: User alerting + FP-->>MS: ALERTING + Note right of FP: Call accepted + MS-->>FP: CONNECT + FP-->>MS: CONNECT ACKNOWLEDGE + +``` + +The diagram illustrates the sequence of messages for a mobile originating call establishment. It starts with the Mobile Station (MS) sending a CTS ACCESS REQUEST to the Fixed Part (FP), which responds with CTS IMMEDIATE ASSIGNMENT, labeled as 'RR connection establishment (MO)'. Next, the MS sends a CM SERVICE REQUEST, labeled as 'Service request'. This is followed by a mutual authentication exchange: FP sends CTS MS AUTHENTICATION REQUEST, MS responds with CTS MS AUTHENTICATION RESPONSE, and FP replies with CTS FP AUTHENTICATION RESPONSE. Then, the FP sends a CTS CIPHERING MODE COMMAND, and MS responds with CTS CIPHERING MODE COMPLETE, labeled as 'Ciphering mode setting'. The FP then sends a CTS MSI UPDATE COMMAND, and MS responds with CTS MSI UPDATE COMPLETE, labeled as 'CTMSI updating'. The call initiation phase begins with MS sending SET UP, FP responding with CALL PROCEEDING, and a subsequent message exchange labeled as 'Channel Assignment'. The FP then sends ALERTING, labeled as 'User alerting'. Finally, MS sends CONNECT, and FP responds with CONNECT ACKNOWLEDGE, labeled as 'Call accepted'. + +Sequence diagram of Mobile originating call establishment between Mobile Station and Fixed Part. + +Figure 7.9/GSM 04.56: Mobile originating call establishment + +## 8 Handling of unknown, unforeseen, and erroneous protocol data + +### 8.1 General + +The procedures specified in GSM 04.56 and call-related supplementary service handling in GSM 04.10 apply to those messages which pass the checks described in this subclause. + +This subclause also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. + +Error handling concerning the value part of the Facility IE and of the SS Version Indicator IE are not in the scope of the present document. It is defined in GSM 04.10 and the GSM 04.8x series. + +Subclauses 8.1 to 8.8 shall be applied in order of precedence. + +Most error handling procedures are mandatory for the CTS-MS. + +Detailed error handling procedures in the CTS-FP are implementation dependent and may vary. However, when extensions of this protocol are developed, CTS-FP will be assumed to have the error handling that is indicated in this subclause as mandatory ("shall") and that is indicated as strongly recommended ("should"). Subclauses 8.2, 8.3, 8.4, 8.5 and 8.7.2 do not apply to the error handling in the CTS-FP applied to the receipt of initial layer 3 message: If the CTS-FP diagnoses an error described in one of these subclauses in the initial layer 3 message received from the CTS-MS, it shall either: + +- try to recognise the classmark and then take further implementation dependent actions; or +- release the RR-connection. + +Also, the error handling of the CTS-FP is only considered as mandatory or strongly recommended when certain thresholds for errors are not reached during a dedicated connection. + +In this subclause the following terminology is used: + +- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in clause 10, or if its value part violates rules of clause 10. However it is not a syntactical error that a type 4 IE specifies in its length indicator a greater length than defined in clause 10. +- A message is defined to have semantically incorrect contents if it contains information which, possibly dependent on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part (i.e. clauses 4 and 5) of GSM 04.58, GSM 04.10, or relevant GSM 04.8X series. + +## 8.2 Message too short + +When a message is received that is too short to contain a complete message type information element, that message shall be ignored, see GSM 04.07. + +## 8.3 Unknown or unforeseen transaction identifier + +See GSM 04.08 clause 8.3. The CTS-FP shall act as the "network", whereas it is stated so. + +## 8.4 Unknown or unforeseen message type + +If a CTS-MS receives a message with message type not defined for the PD and SPD or not implemented by the receiver in unacknowledged mode, it shall ignore the message. + +If a CTS-MS receives a message with message type not defined for the PD and SPD or not implemented by the receiver in acknowledged mode, it shall return a status message (STATUS, CTS RR STATUS or MM STATUS depending on the protocol discriminator and sub-protocol discriminator) with cause # 97 "message type non-existent or not implemented". + +If the CTS-FP receives an RR message or MM message with message type not defined for the PD or not implemented by the receiver in a protocol state where reception of an unsolicited message with the given PD from the CTS-MS is not foreseen in the protocol, the CTS-FP actions are implementation dependent. Otherwise, if the CTS-FP receives a message with message type not defined for the PD and the SPD or not implemented by the receiver, it shall ignore the message except that it should return a status message (STATUS, CTS RR STATUS or MM STATUS depending on the protocol discriminator and Sub-Protocol Discriminator) with cause #97 "message type non-existent or not implemented". + +NOTE: A message type not defined for the PD and SPD in the given direction is regarded by the receiver as a message type not defined for the PD and SPD, see GSM 04.07 [20]. + +If the CTS-MS receives a message not compatible with the protocol state, the CTS-MS shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, CTS RR STATUS or MM STATUS depending on the protocol discriminator and sub-protocol discriminator) with cause #98 "Message type not compatible with protocol state". + +If the CTS-FP receives a message not compatible with the protocol state, the CTS-FP actions are implementation dependent. + +## 8.5 Non-semantical mandatory information element errors + +When on receipt of a message: + +- an "imperative message part" error; or +- a "missing mandatory IE" error; + +is diagnosed or when a message containing: + +- a syntactically incorrect mandatory IE; or +- an IE unknown in the message, but encoded as "comprehension required" (see subclause 10.5); or +- an out of sequence IE encoded as "comprehension required" (see subclause 10.5) + +is received, + +- the CTS-MS station shall proceed as follows: + +If the message is not one of the messages listed in subclauses 8.5.1, 8.5.2, and 8.5.3, the CTS-MS shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (STATUS, CTS RR STATUS or MM STATUS depending on the protocol discriminator and sub-protocol discriminator) with cause # 96 "invalid mandatory information". + +- the CTS-FP shall proceed as follows: + +When the message is not one of the messages listed in subclause 8.5.3 b), c), d) or e), the CTS-FP shall either + +- try to treat the message (the exact further actions are implementation dependent); or +- ignore the message except that it should return a status message (STATUS, CTS RR STATUS, or MM STATUS depending on the protocol discriminator and sub-protocol discriminator) with cause # 96 "invalid mandatory information". + +### 8.5.1 Radio resource management + +For the CTS-MS the following procedures shall apply: + +- If the message is a CTS CHANNEL RELEASE message, the actions taken shall be the same as specified in subclause 4.4.13 "RR connection release". + +### 8.5.2 Mobility management + +No exceptional cases are described for mobility management messages. + +### 8.5.3 Call control + +See GSM 04.08 subclause 8.5.3. + +## 8.6 Unknown and unforeseen IEs in the non-imperative message part + +### 8.6.1 IEs unknown in the message + +The CTS-MS shall ignore all IEs unknown in a message which are not encoded as "comprehension required". + +The CTS-FP shall take the same approach. + +## 8.6.2 Out of sequence IEs + +The CTS-MS shall ignore all out of sequence IEs in a message which are not encoded as "comprehension required". + +The CTS-FP should take the same approach. + +## 8.6.3 Repeated IEs + +If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified in clause 9 of the present document, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. + +The CTS-FP should follow the same procedures. + +## 8.7 Non-imperative message part errors + +This category includes: + +- syntactically incorrect optional IEs; +- conditional IE errors. + +### 8.7.1 Syntactically incorrect optional IEs + +The CTS-MS shall treat all optional IEs that are syntactically incorrect in a message as not present in the message. + +The CTS-FP shall take the same approach. + +### 8.7.2 Conditional IE errors + +When the CTS-MS upon receipt of a message diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE, it shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (STATUS, CTS RR STATUS, or MM STATUS depending on the PD and SPD) with cause value # 100 "conditional IE error". + +When the CTS-FP receives a message and diagnose a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE, the CTS-FP shall either: + +- try to treat the message (the exact further actions are implementation dependent); or +- ignore the message except that it should return a status message (STATUS, CTS RR STATUS or MM STATUS depending on the protocol discriminator and sub-protocol discriminator) with cause # 100 "conditional IE error". + +## 8.8 Messages with semantically incorrect contents + +When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part of GSM 04.56 (i.e. of clauses 5, 5, 6) are performed. If however no such reactions are specified, the CTS-MS shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, CTS RR STATUS, or MM STATUS depending on the PD and SPD) with cause value # 95 "semantically incorrect message". + +The CTS-FP should follow the same procedure except that a status message is not normally transmitted. + +Semantic checking of the Facility information element value part (defined in GSM 04.80) is the subject of the technical specifications GSM 04.10 and the GSM 04.8x series. + +## 9 Message functional definitions and contents + +This subclause defines the structure of the messages of those layer 3 protocols defined in GSM 04.56. These are standard L3 messages as defined in GSM 04.07 with the exception of those sent on the SCH, ARCH. + +Each definition given in the present subclause includes: + +- a) a brief description of the message direction and use, including whether the message has: + - 1. Local significance, i.e. relevant only on the originating or terminating access; + - 2. Access significance, i.e. relevant in the originating and terminating access, but not in the CTS-FP; + - 3. Dual significance, i.e. relevant in either the originating or terminating access and in the network; or + - 4. Global significance, i.e. relevant in the originating and terminating access and in the network. +- b) a table listing the information elements known in the message and their order of their appearance in the message. All information elements that may be repeated are explicitly indicated. (V and LV formatted IEs, which compose the imperative part of the message, occur before T, TV, and TLV formatted IEs which compose the non-imperative part of the message, see GSM 04.07.) In a (maximal) sequence of consecutive information elements with half octet length, the first information element with half octet length occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements. + +For each information element the table indicates: + +- 1. the information element identifier, in hexadecimal notation, if the IE has format T, TV, or TLV. Usually, there is a default IEI for an information element type; default IEIs of different IE types of the same protocol are different. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-). + +NOTE: The same IEI may be used for different information element types in different messages of the same protocol. + +- 2. the name of the information element (which may give an idea of the semantics of the element). The name of the information element (usually written in *italics*) followed by "IE" or "information element" is used in GSM 04.08 as reference to the information element within a message. + - 3. the name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced subclause of clause 10 of GSM 04.08 describing the value part of the information element. + - 4. the presence requirement indication (M, C, or O) for the IE as defined in GSM 04.07. + - 5. The format of the information element (T, V, TV, LV, TLV) as defined in GSM 04.07. + - 6. The length of the information element (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by link layer protocol, and in the case of the Facility IE by possible further conditions specified in GSM 04.10. This indication is non-normative. +- c) subclauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant message which together with other conditions specified in GSM 04.08 define when the information elements shall be included or not, what non-presence of such IEs means, and - for IEs with presence requirement C - the static conditions for presence and/or non-presence of the IEs (see GSM 04.07). + +### 9.1 Messages for Radio Resources management + +Table 9.1/GSM 04.56 summarises the messages for Radio Resources management. + +**Table 9.1.1/GSM 04.56: Messages for Radio Resources management** + +| Channel establishment messages: | Reference | +|----------------------------------------|------------------| +| CTS IMMEDIATE ASSIGNMENT | 9.1.21 | +| CTS IMMEDIATE ASSIGNMENT EXTENDED | 9.1.22 | +| CTS IMMEDIATE ASSIGNMENT REJECT | 9.1.23 | +| Ciphering messages: | Reference | +| CTS CIPHERING MODE COMMAND | 9.1.14 | +| CTS CIPHERING MODE COMPLETE | 9.1.15 | +| Channel release messages: | Reference | +| CTS CHANNEL RELEASE | 9.1.13 | +| Handover message: | Reference | +| CTS INTRACELL HANDOVER COMMAND | 9.1.24 | +| CTS INTRACELL HANDOVER COMPLETE | 9.1.25 | +| CTS INTRACELL HANDOVER FAILURE | 9.1.26 | +| Paging messages: | Reference | +| CTS GROUP ALERTING REQUEST | 9.1.19 | +| CTS PAGING REQUEST | 9.1.31 | +| CTS PAGING RESPONSE | 9.1.32 | +| CTS HUNTING REQUEST | 9.1.20 | +| Alive check messages: | Reference | +| | | +| Miscellaneous messages: | Reference | +| CTS ACCESS REQUEST | 9.1.1 | +| CTS CHANNEL MODE MODIFY | 9.1.11 | +| CTS CHANNEL MODE MODIFY ACKNOWLEDGE | 9.1.12 | +| CTS CLASSMARK CHANGE | 9.1.16 | +| CTS CLASSMARK ENQUIRY | 9.1.17 | +| CTS FREQUENCY HOPPING DEFINITION | 9.1.18 | +| CTS MEASUREMENT REPORT | 9.1.27 | +| CTS RR STATUS | | +| System messages: | Reference | +| CTS SYSTEM INFORMATION TYPE 1 | 9.1.33 | +| CTS SYSTEM INFORMATION TYPE 2 | 9.1.34 | +| CTS SYSTEM INFORMATION TYPE 3 | 9.1.35 | + +### 9.1.1 CTS access request + +This message is sent in random mode on the ARCH. It does not follow the basic format. The possible formats are presented directly below, without reference to information fields. The order of bit transmission is defined in GSM 04.04. + +The message is only 25 bits long, coded as shown in figure 9.1.1/GSM 04.56. + +![Diagram of CTS ACCESS REQUEST message content showing a 25-bit structure with CAUSE (3 bits) and CTSMSI (22 bits) fields.](5c3dd31372f59e15250f0ab1613ca485_img.jpg) + +``` + + 25 1 + +-----+ + | CAUSE | CTSMSI | + +-----+ + +``` + +Diagram of CTS ACCESS REQUEST message content showing a 25-bit structure with CAUSE (3 bits) and CTSMSI (22 bits) fields. + +**Figure 9.1.1/GSM 04.56: CTS ACCESS REQUEST message content** + +CAUSE (octet 1) + +This information field indicates the reason for requesting the access to a CTS-FP. This field has a fixed length (3 bits). + +CTSMSI + +This information field contains the individual Mobile Subscriber Identity. See GSM 03.03. + +**Table 9.1.2/GSM 04.56: CTS ACCESS REQUEST cause** + +| 3bits Code | Cause | +|------------|---------------------------------------------------------| +| 000 | Alive Check Response | +| 001 | MM procedures (Attachment, Re-attachment or detachment) | +| 010 | Reserved for future use | +| 011 | MS-originated call | +| 100 | Answer to paging | +| 101 | Enrolment | +| 110 | Reserved for future use | +| 111 | Reserved for future use | + +NOTE: Reserved for future use values shall not be used by the mobile station on ARCH. If such message is received by the CTS-FP, it may be ignored. + +## 9.1.2 CTS AFA monitoring command + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to instruct the CTS-MS to perform as soon as possible AFA interference measurements. + +Message type: CTS AFA MONITORING COMMAND + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.3/GSM 04.56: CTS AFA MONITORING COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|-------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS AFA Monitoring
Command Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | AFA Monitoring Frequency List | Frequency list
GSM 04.08 subclause 10.5.2.13 | M | LV | | +| | NAMC | AFA Monitoring Cycles | M | V | 2 | + +## 9.1.3 CTS AFA monitoring enquiry + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to request for AFA monitoring results report. + +Message type: CTS AFA MONITORING ENQUIRY + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.4/GSM 04.56: CTS AFA MONITORING ENQUIRY message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS AFA Monitoring
Enquiry Message Type | Message Type
subclause 10.4 | M | V | 1 | + +## 9.1.4 CTS AFA monitoring report + +This message is sent on the main DCCH by the CTS-MS to the CTS-FP to report AFA monitoring results. + +Message type: CTS AFA MONITORING REPORT + +Significance: dual + +Direction: CTS-MS to CTS-FP + +**Table 9.1.5/GSM 04.56: CTS AFA MONITORING REPORT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS AFA Monitoring
Report Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | AFA Interference Level | AFA Interference Level | M | LV | | +| | NAMC real | AFA Monitoring Cycles | M | V | 2 | + +### 9.1.5 CTS BCCH detection command + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to instruct the CTS-MS to perform as soon as possible the BCCH detection procedure. + +Message type: CTS BCCH DETECTION COMMAND + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.7/GSM 04.56: CTS BCCH DETECTION COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|-------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS BCCH Detection
Command Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | BCCH Detection
Frequency List | Frequency list
GSM 04.08 subclause 10.5.2.13 | M | LV | | + +### 9.1.6 CTS BCCH detection enquiry + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to request for a BCCH detection report. + +Message type: CTS BCCH DETECTION ENQUIRY + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.8/GSM 04.56: CTS BCCH DETECTION ENQUIRY message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS BCCH Detection
Enquiry Message Type | Message Type
subclause 10.4 | M | V | 1 | + +### 9.1.7 CTS BCCH detection report + +This message is sent on the main DCCH by the CTS-MS to the CTS-FP to report the table of BCCH detection status. + +Message type: CTS BCCH DETECTION REPORT + +Significance: dual + +Direction: CTS-MS to CTS-FP + +**Table 9.1.9/GSM 04.56: CTS BCCH DETECTION REPORT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|----------------------------------------|---------------------------------------------|----------|--------|--------| +| | RR management Protocol Discriminator | Protocol Discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS BCCH Detection Report Message Type | Message Type subclause 10.4 | M | V | 1 | +| | BCCH Detection Status | BCCH Detection Status | M | LV | | + +### 9.1.8 CTS beacon channel synchronisation burst information + +This message is sent on the CTSBCH-SB. Its purpose is to . It does not follow the basic format. Its length is 25 bits. + +Message type: BEACON CHANNEL SYNCHRONISATION BURST + +Significance: dual + +Direction: CTS-FP to CTS-MSs + +![](34e9ca4d52796527c375f4bc187080f8_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|------|-------|---|-----|---|--------|---|---------| +| Sta- | PCH | Shift | | | | FPBI | | octet 1 | +| tus | ind. | ind. | | TNC | | (high) | | | +| FPBI | | | | | | | | octet 2 | +| (middle part) | | | | | | | | | +| FPBI | | | | | | | | octet 3 | +| (middle part) | | | | | | | | | +| | | | | | | FPBI | | | +| | | | | | | (low) | | | + +**Figure 9.1.2/GSM 04.56: Beacon Channel synchronisation burst information element** + +**Table 9.1.10/GSM 04.56: Beacon Channel synchronisation burst information element** + +| | | | | +|------------------------------------|---|---|-------------------------------------| +| Status (octet 1 bit 8) | | | | +| Bits | | | | +| 8 | | | | +| 0 Idle | | | | +| 1 Busy | | | | +| PCH indicator (octet 1 bit 7) | | | | +| Bits | | | | +| 7 | | | | +| 0 No CTSPCH to decode | | | | +| 1 CTSPCH to decode | | | | +| Shifting indicator (octet 1 bit 6) | | | | +| Bits | | | | +| 6 | | | | +| 0 Shifting | | | | +| 1 No shifting | | | | +| TNC (octet 1 bit 5 to 3) | | | | +| Bits | | | | +| 5 | 4 | 3 | | +| X | X | X | CTS control channel timeslot number | +| FPBI | | | | + +### 9.1.9 CTS channel mode modify + +This message is sent on the main DCCH from the CTS-FP to the CTS-MS to request the setting of the mode for the indicated channel. See table 9.6/GSM 04.08. + +Message type: CTS CHANNEL MODE MODIFY + +Significance: local + +Direction: CTS-FP to CTS-MS + +### 9.1.10 CTS channel mode modify acknowledge + +This message is sent on the main DCCH from the CTS-MS to the CTS-FP to indicate the successful or unsuccessful execution of a channel mode modify request. See table 9.7/GSM 04.08. + +Message type: CTS CHANNEL MODE MODIFY ACKNOWLEDGE + +Significance: local + +Direction: CTS-FP to CTS-MS + +### 9.1.11 CTS channel release + +This message is sent on the main DCCH from the CTS-FP to the CTS-MS to initiate deactivation of the dedicated channel. . See table 9.1.11/GSM 04.56. + +Message type: CTS CHANNEL RELEASE + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.11/GSM 04.56: CTS CHANNEL RELEASE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-----------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Channel Release
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | RR Cause | RR Cause
GSM 04.08 subclause 10.5.2.31 | M | V | 1 | + +## 9.1.12 CTS ciphering mode command + +This message is sent on the main DCCH from the CTS-FP to the CTS-MS to indicate that the CTS-FP has started deciphering and that enciphering and deciphering shall be started in the mobile station, or to indicate that ciphering will not be performed. See table 9.1.12/GSM 04.56. + +Message type: CTS CIPHERING MODE COMMAND + +Significance: dual + +Direction: CTS-FP to CST-MS + +**Table 9.1.12/GSM 04.56: CTS CIPHERING MODE COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-----------------------------------------|-----------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Cipher Mode Command
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Ciphering Mode Setting | Cipher Mode Setting
GSM 04.08 subclause 10.5.2.9 | M | V | 1/2 | +| | Cipher Response | Cipher Response
GSM 04.08 subclause 10.5.2.10 | M | V | 1/2 | + +## 9.1.13 CTS ciphering mode complete + +This message is sent on the main DCCH from the CTS-MS to the CTS-FP to indicate that enciphering and deciphering has been started in the MS. See table 9.1.13/GSM 04.56 + +Message type: CTS CIPHERING MODE COMPLETE + +Significance: dual + +Direction: CTS-MS to CTS-FP + +**Table 9.1.13/GSM 04.56: CTS CIPHERING MODE COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Cipher Mode Complete
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| 17 | Mobile Equipment
Identity | Mobile Identity | O | TLV | 3-11 | + +### 9.1.14 CTS classmark change + +This message is sent on the main DCCH by the CTS-MS to the CTS-FP to indicate a classmark change or a response to a classmark enquiry. See table 9.12/GSM 04.08. + +Message type: CTS CLASSMARK CHANGE + +Significance: dual + +Direction: CTS-MS to CTS-FP + +### 9.1.15 CTS classmark enquiry + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to request classmark information. See table 9.12a/GSM 04.08. + +Message type: CTS CLASSMARK ENQUIRY + +Significance: dual + +Direction: CTS-FP to CTS-MS + +### 9.1.16 CTS frequency hopping definition + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to indicate the frequency list and the frequency hopping parameters to be used. See table 9.1.14/GSM 04.56. + +Message type: CTS FREQUENCY HOPPING REDEFINITION + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.14/GSM 04.56: CTS FREQUENCY HOPPING DEFINITION message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|-------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Frequency definition
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Reference Time | Starting Time
GSM 04.08 | M | V | 3 | +| | TFH Current Parameters | TFH Current Parameters | M | V | 8-n | +| | TFH General Parameter | TFH General Parameters | O | V | 10 | +| | TFH List | Frequency list
GSM 04.08 subclause 10.5.2.13 | O | V | 3-n | + +#### 9.1.16.1 Reference time + +The reference time information element indicates the time when the values given by the TFH current parameters IE are relevant. + +### 9.1.17 CTS group alerting request + +This message is sent on the CTSPCH by the CTS-FP to the mobile stations in order to initiate a connectionless group alerting procedure. The mobile stations are identified by their connectionless group CTSMSI. See table 9.1.15/GSM 04.56. + +Message type: CTS GROUP ALERTING REQUEST + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.15/GSM 04.56: CTS GROUP ALERTING REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------------------|----------------------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
subclause 10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Group Alerting Request
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Connectionless Group
CTS Mobile Subscriber Identity | CTSMSI
subclause 10.5.2.x | M | LV | | +| | Information Transfer Capability | Information Transfer Capability | M | V | 1/2 | +| | Spare Half Octet | Spare Half Octet
GSM 04.08 subclause 10.5.1.8 | M | V | 1/2 | +| | Calling Party BCD Number | Calling Party BCD Number
GSM 04.08 subclause 10.5.4.9 | M | LV | | +| | Rest Octets | Rest Octets
subclause 10.5.2.23 | M | V | | + +#### 9.1.17.1 Rest Octets + +The sum of the length of this IE and the L2 Pseudo Length of the message equals 22. + +### 9.1.18 CTS hunting request + +This message is sent on the CTSPCH by the CTS-FP to mobile stations to make a group of mobile station alert for location purpose. The mobile station are identified by their Connectionless Group CTSMSI See table 9.16/GSM 04.56. + +Message type: CTS HUNTING REQUEST + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.16/GSM 04.56: CTS HUNTING REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------------------|------------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
subclause 10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Hunting Request
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Connectionless Group
CTS Mobile Subscriber Identity | CTSMSI
subclause 10.5.2.x | M | V | 3 | +| | Rest Octets | Rest Octets
subclause 10.5.2.23 | M | V | 17 | + +#### 9.1.18.1 Rest Octets + +The sum of the length of this IE and the L2 Pseudo Length of the message equals 22. + +### 9.1.19 CTS immediate assignment + +This message is sent on the CTSAGCH by the CTS-FP to the CTS-MS in idle mode to change the channel configuration to a dedicated configuration. See table 9.1.17/GSM 04.56. + +Message type: CTS IMMEDIATE ASSIGNMENT + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.17/GSM 04.56: CTS IMMEDIATE ASSIGNMENT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|---------------------------------------------------|----------|--------|--------| +| | CTS L1 information | CTS L1 information | M | V | 3 | +| | L2 Pseudo Length | L2 Pseudo Length
GSM 04.08 subclause 10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Immediate Assignment
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Channel Description | CTS Channel Description | M | V | 3 | +| | Access Request
Reference | CTS Access Request Reference | M | V | 4 | +| | Rest Octets | Rest Octets | M | V | 10 | + +## 9.1.20 CTS immediate assignment extended + +This message is sent on the hopping CTSAGCH by the CTS-FP to two CTS-MSs in idle mode to change their channel configurations to a dedicated configurations. See table 9.1.18/GSM 04.56. + +This message has a L2 Pseudo Length of 16. + +Message type: CTS IMMEDIATE ASSIGNMENT EXTENDED + +Significance: dual + +Direction: CTS-FP to CTS-MSs + +**Table 9.1.18/GSM 04.56: CTS IMMEDIATE ASSIGNMENT EXTENDED message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|---------------------------------------------------|----------|--------|--------| +| | CTS L1 Information | CTS L1 Information | M | V | 3 | +| | L2 Pseudo Length | L2 Pseudo Length
GSM 04.08 subclause 10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Immediate Assignment
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Channel Description 1 | CTS Channel Description | M | V | 3 | +| | Access Request
Reference 1 | CTS Access Request Reference | M | V | 4 | +| | Channel Description 2 | CTS Channel Description | M | V | 3 | +| | Access Request
Reference 2 | CTS Access Request Reference | M | V | 4 | +| | Rest Octets | Rest Octets | M | V | 3 | + +### 9.1.21 CTS immediate assignment reject + +This message is sent on the CTSAGCH by the CTS-FP to up to three CTS-MSs to indicate that no channel is available for assignment. See table 9.1.19/GSM 04.56. + +This message has a L2 Pseudo Length of 22. + +Message type: CTS IMMEDIATE ASSIGNMENT REJECT + +Significance: dual + +Direction: CTS-FP to CTS-MSs + +**Table 9.1.19/GSM 04.56: CTS IMMEDIATE ASSIGNMENT REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|--------------------------------------------------|----------|--------|--------| +| | CTS L1 information | CTS L1 information | M | V | 3 | +| | L2 Pseudo Length | L2 Pseudo Length
GSM 0408 subclause 10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Immediate Assignment
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Access Request
Reference 1 | CTS Access Request Reference | M | V | 4 | +| | Wait Indication 1 | Wait Indication
GSM 04.08 subclause 10.5.2.43 | M | V | 1 | +| | Access Request
Reference 2 | CTS Access Request Reference | M | V | 4 | +| | Wait Indication 2 | Wait Indication
GSM 04.08 subclause 10.5.2.43 | M | V | 1 | +| | Access Request
Reference 3 | CTS Access Request Reference | M | V | 4 | +| | Wait Indication 3 | Wait Indication
GSM 04.08 subclause 10.5.2.43 | M | V | 1 | +| | Rest Octets | Rest octets | M | V | 2 | + +#### 9.1.21.1 Use of Indexes + +An Access Request information element and the following Wait Indication information element refer to the same CTS-MS. + +#### 9.1.21.2 Filling of the message + +If necessary, the Access Request Reference information element and the wait indication information element should be duplicated to fill the message + +### 9.1.22 CTS intracell handover command + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to change the dedicated channel configuration + +Message type: CTS INTRACELL HANDOVER COMMAND + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.20/GSM 04.56: CTS INTRACELL HANDOVER COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Immediate Assignment
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Channel Description | CTS Channel Description | M | V | 3 | +| | Starting Time | Starting Time
GSM 04.08 subclause 10.5.2.38 | M | V | 3 | +| | Channel Mode | Channel Mod
GSM 04.08 subclause 10.5.2.6 | O | V | 2 | + +### 9.1.23 CTS intracell handover complete + +This message is sent on the main DCCH by the CTS-MS to the CTS-FP to indicate that the CTS-MS has established the main signalling link. + +Message type: CTS INTRACELL HANDOVER COMPLETE + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.21/GSM 04.56: CTS INTRACELL HANDOVER COMPLETE message content** + +| IEI | Information element | Type / Référence | Presence | Format | Length | +|-----|------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Immediate Assignment
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | RR Cause | RR Cause
GSM 04.08 subclause 10.5.2.31 | M | V | 2 | + +### 9.1.24 CTS intracell handover failure + +This message is sent on the main DCCH by the CTS-MS to the CTS-FP to indicate that the CTS-MS has failed to seize the new channel. + +Message type: CTS INTRACELL HANDOVER COMMAND + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.22/GSM 04.56: CTS INTRACELL HANDOVER COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Immediate Assignment
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Channel Description | CTS Channel Description | M | V | 3 | +| | Starting Time | Starting Time
GSM 04.08 subclause 10.5.2.38 | M | V | 2 | + +## 9.1.25 CTS measurement report + +This message is sent on the SACCH by the CTS-MS to the CTS-FP to report measurement results about the dedicated channel. See table 9.1.23/GSM 04.56. + +Message type: CTS MEASUREMENT REPORT + +Significance: dual + +Direction: CTS-MS to CTS-FP + +**Table 9.1.23/GSM 04.56: CTS SYSTEM INFORMATION TYPE 1 message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-----------------------------------------|------------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Measurement Report
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Measurement Results | Measurement Results
GSM 04.08 subclause 10.5.2.20 | M | V | 16 | + +### 9.1.25.1 Measurement results + +For CTS purpose, the NO-NCELL-M field (number of neighbouring cell measurements) shall be set to *No neighbour cell measurement result* (000) in the Measurement Result IEI and therefore, RXLEV-NCELLi, BS-FREQ-NCELLi and BSISC-NCELLi field ( $1 \leq i \leq 6$ ) shall be coded with a "0" in each bit. + +## 9.1.26 CTS OFO measurement command + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to instruct the CTS-MS to perform as soon as possible OFO measurements. + +Message type: CTS OFO MEASUREMENT COMMAND + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.24/GSM 04.56: CTS OFO MEASUREMENT COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------|-------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS OFO Measurement
Command Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | OFO Measurement BCCH
Frequency List | Frequency list
GSM 04.08 subclause 10.5.2.13 | M | LV | | + +## 9.1.27 CTS OFO measurement enquiry + +This message is sent on the main DCCH by the CTS-FP to the CTS-MS to request for OFO measurement results report. + +Message type: CTS OFO MEASUREMENT ENQUIRY + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.25/GSM 04.56: CTS OFO MEASUREMENT ENQUIRY message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS OFO Measurement
Enquiry Message Type | Message Type
subclause 10.4 | M | V | 1 | + +## 9.1.28 CTS OFO Measurement report + +This message is sent on the main DCCH by the CTS-MS to the CTS-FP to report AFA monitoring results. + +Message type: CTS OFO MEASUREMENT REPORT + +Significance: dual + +Direction: CTS-MS to CTS-FP + +**Table 9.1.26/GSM 04.56: CTS OFO MEASUREMENT REPORT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS OFO Measurement
Report Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | OFO Measurement Results | OFO Measurement Result | M | LV | | + +## 9.1.29 CTS paging request + +This message is sent on the CTSPCH by the CTS-FP to CTS-MSs. It may be sent to a CTS-MS in idle mode to trigger channel access. The CTS-MS are identified by their CTSMSIs. See table 9.x/GSM 04.56. + +This message has a L2 Pseudo Length of 19. + +Message type: CTS PAGING REQUEST + +Significance: dual + +Direction: CTS-FP to CTS-MS + +**Table 9.1.27/GSM 04.56: CTS PAGING REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-----------------------------------------|------------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
subclause 10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Paging Request
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Mobile Identity 1 | CTSMSI
subclause 10.5.2.1 | M | V | 3 | +| | Mobile Identity 2 | CTSMSI
subclause 10.5.2.1 | M | V | 3 | +| | Mobile Identity 3 | CTSMSI
subclause 10.5.2.1 | M | V | 3 | +| | Mobile Identity 4 | CTSMSI
subclause 10.5.2.1 | M | V | 3 | +| | Paging type 1 | Paging type
subclause 10.5.2.12 | M | V | 1 | +| | Paging type 2 | Paging type
subclause 10.5.2.12 | M | V | 1 | +| | Paging type 3 | Paging type
subclause 10.5.2.12 | M | V | 1 | +| | Paging type 4 | Paging type
subclause 10.5.2.12 | M | V | 1 | +| | Rest Octets | | M | V | 4 | + +### 9.1.29.1 Paging type + +The Paging type x Information Element is related to the Mobile Identity x Information Element. + +### 9.1.30 CTS paging response + +This message is sent on the main DCCH by the CTS-MS to the CTS-FP in connection with establishment of the main signalling link as a response to the paging request message. See table 9.1.28/GSM 04.56. + +Message type: CTS PAGING RESPONSE + +Significance: dual + +Direction: CTS-MS to CTS-FP + +**Table 9.1.28/GSM 04.56: CTS PAGING RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-----------------------------------------|------------------------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS Paging Response
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Ciphering Key Sequence
Number | Ciphering Key Sequence
Number
GSM 04.08 subclause 10.5.1.2 | M | V | 1/2 | +| | Spare Half Octet | Spare Half Octet
subclause 10.5.1.8 | M | V | 1/2 | +| | Mobile Station
Classmark | Mobile Station
Classmark 2
GSM 0408 subclause 10.5.1.6 | M | LV | 4 | +| | Mobile Identity | Mobile Identity
GSM 04.08 subclause 10.5.1.4 | M | LV | 2-9 | + +### 9.1.30.1 Ciphering Key Sequence + +For CTS purpose, the key sequence value shall be set to *No key is available* (1 1 1) value in the Ciphering key Sequence IEI by the CTS-MS. + +### 9.1.31 CTS system information type 1 + +This message is sent on the CTSPCH by the CTS-FP to all the CTS-MSs within the cell giving information about the TFH List to be used. See table 9.1.29/GSM 04.56. + +Message type: CTS SYSTEM INFORMATION TYPE 1 + +Significance: dual + +Direction: CTS-FP to CTS-MSs + +**Table 9.1.29/GSM 04.56: CTS SYSTEM INFORMATION TYPE 1 message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-----------------------------------------|------------------------------------------------|----------|--------|--------| +| | L2 Pseudo Length | L2 Pseudo Length
subclause 10.5.2.19 | M | V | 1 | +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS System Info. Type 1
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Starting Time | Starting Time
GSM 04.08 subclause 10.5.2.38 | M | V | 2 | +| | TFH List | Frequency List | M | LV | | +| | Rest Octet | | M | | | + +#### 9.1.31.1 Starting Time + +The *starting time* information element indicates when the new TFH list apply. + +### 9.1.32 CTS system information type 2 + +This message is sent on the CTSPCH by the CTS-FP to all the CTS-MSs within the cell giving information about the hopping parameters to be used. See table 9.1.30/GSM 04.56. + +Message type: CTS SYSTEM INFORMATION TYPE 2 + +Significance: dual + +Direction: CTS-FP to CTS-MSs + +**Table 9.1.30/GSM 04.56: CTS SYSTEM INFORMATION TYPE 2 message content** + +| IEI | Information element | Type / Référence | Presence | Format | Length | +|-----|-----------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS System Info. Type 2
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Starting Time | Starting Time
GSM 04.08 subclause 10.5.2.38 | M | V | 2 | +| | TFH New Current Parameters | TFH Current parameters | M | LV | | +| | Rest Octet | | M | | | + +### 9.1.33 CTS system information type 3 + +This message is sent on the CTSPCH by the CTS-FP to all the CTS-MSs in order to invalidate the hopping parameters used by the CTS-MSs and to detach all the CTS-MSs. See table 9.1.31/GSM 04.56. + +Message type: CTS SYSTEM INFORMATION TYPE 3 + +Significance: dual + +Direction: CTS-FP to CTS-MSs + +**Table 9.1.31/GSM 04.56: CTS SYSTEM INFORMATION TYPE 3 message content** + +| IEI | Information element | Type / Référence | Presence | Format | Length | +|-----|-----------------------------------------|------------------------------------------------|----------|--------|--------| +| | RR management
Protocol Discriminator | Protocol Discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS System Info. Type 2
Message Type | Message Type
subclause 10.4 | M | V | 1 | +| | Starting Time | Starting Time
GSM 04.08 subclause 10.5.2.38 | M | V | 2 | +| | Rest Octet | | M | | | + +### 9.1.34 CTS RR parameters update + +This message is sent by the fixed part to the mobile station to provide RR parameters. See table 9.1.32/GSM 04.56 + +Message type: CTS RR PARAMETERS UPDATE + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.1.32/GSM 04.56: CTS RR PARAMETERS UPDATE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------|-----------------------------------------------------|----------|--------|--------| +| | RR management
Protocol discriminator | Protocol discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS RR parameters update
Message type | Message type
subclause 10.4 | M | V | 1 | +| 74 | CTS selection parameters | CTS selection parameters
subclause 10.5.3.12 | O | TV | 3 | +| 75 | CTS RR parameters | CTS RR parameters
subclause 10.5.3.13 | O | TV | 5 | +| 76 | Timeslot shifting parameters | Timeslot shifting parameters
subclause 10.5.3.14 | O | TV | 4 | + +## 9.2 Messages for mobility management + +Table 9.2.1/GSM 04.56 summarises the messages for mobility management. + +**Table 9.2.1/GSM 04.56: Messages for mobility management** + +| | | +|---------------------------------|------------------| +| Attach/detach messages: | Reference | +| CTS ATTACH REQUEST | 9.2.1 | +| CTS ATTACH ACCEPT | 9.2.2 | +| CTS ATTACH REJECT | 9.2.3 | +| CTS DETACH INDICATION | 9.2.4 | +| Enrolment messages: | Reference | +| CTS ENROLMENT REQUEST | 9.2.7 | +| CTS ENROLMENT ACCEPT | 9.2.8 | +| CTS ENROLMENT REJECT | 9.2.9 | +| CTS DE-ENROLMENT INDICATION | 9.2.10 | +| Authentication messages: | Reference | +| CTS MS AUTHENTICATION REQUEST | 9.2.11 | +| CTS MS AUTHENTICATION RESPONSE | 9.2.12 | +| CTS FP AUTHENTICATION RESPONSE | 9.2.13 | +| CTS MS AUTHENTICATION REJECT | 9.2.14 | +| Identity messages: | Reference | +| CTSMSI UPDATE COMMAND | 9.2.15 | +| CTSMSI UPDATE COMPLETE | 9.2.16 | + +## 9.2.1 CTS attach request + +This message is sent by the mobile station to the fixed part to indicate to request attachment on this fixed part. See table 9.2.2/GSM 04.56. + +Message type: CTS ATTACH REQUEST + +Significance: dual + +Direction: mobile station to fixed part + +**Table 9.2.2/GSM 04.56: CTS ATTACH REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|------------------------------------------------------------|----------|--------|--------| +| | CTS mobility management Protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS attach request Message type | Message type subclause 10.4 | M | V | 1 | +| | CTS Ciphering Key Sequence Number | Ciphering Key Sequence Number GSM 04.08 subclause 10.5.1.2 | M | V | 1/2 | +| | Attach type | Attach type subclause 10.5.3.11 | M | V | 1/2 | +| | Mobile Station Classmark | Mobile Station Classmark 1 GSM 04.08 subclause 10.5.1.5 | M | V | 1 | +| | Mobile identity | Mobile identity subclause 10.5.1.1 | M | LV | 2 - 9 | + +## 9.2.2 CTS attach accept + +This message is sent by the fixed part to the mobile station to indicate that the requested attachment has been accepted. See table 9.2.3/GSM 04.56 + +Message type: CTS ATTACH ACCEPT + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.3/GSM 04.56: CTS ATTACH ACCEPT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|------------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS attach accept message type | Message type subclause 10.4 | M | V | 1 | +| | TC3252 | TC3252 subclause 10.5.3.10 | M | V | 1 | +| 01 | CTS mobile group list | CTS mobile group list subclause 10.5.3.7 | O | TLV | 5 - 26 | +| 02 | Access right identity | Access right identity subclause 10.5.3.9 | O | TV | 4 | +| A1 | Follow on proceed | Follow on proceed GSM 04.08 subclause 10.5.3.7 | O | T | 1 | + +### 9.2.3 CTS attach reject + +This message is sent by the fixed part to the mobile station to indicate that the requested attachment has been rejected. See table 9.2.4/GSM 04.56. + +Message type: CTS ATTACH REJECT + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.4/GSM 04.56: CTS ATTACH REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|---------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS attach reject message type | Message type subclause 10.4 | M | V | 1 | +| | Fixed part identity | Fixed part identity subclause 10.5.3.6 | M | LV | 2 - 10 | +| | Reject cause | Reject cause GSM 04.08 subclause 10.5.3.6 | M | V | 1 | + +### 9.2.4 CTS detachment indication + +This message is sent by the mobile station to the fixed part to indicate the detachment of this fixed part. See table 9.2.5/GSM 04.56. + +Message type: CTS DETACH INDICATION + +Significance: dual + +Direction: mobile station to fixed part + +**Table 9.2.5/GSM 04.56: CTS DETACH INDICATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|---------------------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS detach indication message type | Message type subclause 10.4 | M | V | 1 | +| | Mobile Station Classmark | Mobile Station Classmark 1 GSM 04.08 subclause 10.5.1.5 | M | V | 1 | +| | Mobile identity | Mobile identity subclause 10.5.1.1 | M | LV | 2 - 9 | + +## 9.2.5 CTS enrolment request + +This message is sent by the mobile station to the fixed part to indicate to request enrolment on this fixed part. See table 9.2.8/GSM 04.56. + +Message type: CTS ENROLMENT REQUEST + +Significance: dual + +Direction: mobile station to fixed part + +**Table 9.2.8/GSM 04.56: CTS ENROLMENT REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|---------------------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS enrolment request message type | Message type subclause 10.4 | M | V | 1 | +| | Mobile Station Classmark | Mobile Station Classmark 1 GSM 04.08 subclause 10.5.1.5 | M | V | 1 | +| | Mobile identity | Mobile identity subclause 10.5.1.1 | M | LV | 2 - 9 | +| A2 | Following attach request | Following attach request subclause 10.5.3.8 | O | T | 1 | + +## 9.2.6 CTS enrolment accept + +This message is sent by the fixed part to the mobile station to indicate that the requested enrolment has been accepted. See table 9.2.9/GSM 04.56 + +Message type: CTS ENROLMENT ACCEPT + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.9/GSM 04.56: CTS ENROLMENT ACCEPT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|---------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS enrolment accept message type | Message type subclause 10.4 | M | V | 1 | +| | Fixed part identity | Fixed part identity subclause 10.5.3.6 | M | LV | 2 - 10 | +| | Mobile identity | Mobile identity subclause 10.5.1.1 | M | LV | 2 - 9 | + +## 9.2.7 CTS enrolment reject + +This message is sent by the fixed part to the mobile station to indicate that the requested enrolment has been rejected. See table 9.2.10/GSM 04.56. + +Message type: CTS ENROLMENT REJECT + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.10/GSM 04.56: CTS ENROLMENT REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|---------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS enrolment reject message type | Message type subclause 10.4 | M | V | 1 | +| | Fixed part identity | Fixed part identity subclause 10.5.3.6 | M | LV | 2 - 10 | +| | Reject cause | Reject cause GSM 04.08 subclause 10.5.3.6 | M | V | 1 | + +## 9.2.8 CTS de-enrolment indication + +This message is sent by the fixed part to the mobile station to indicate that the mobile station is no more enrolled on this fixed part. See table 9.2.11/GSM 04.56. + +Message type: CTS DE-ENROLMENT INDICATION + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.11/GSM 04.56: CTS DE-ENROLMENT INDICATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|---------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS de-enrolment indication message type | Message type subclause 10.4 | M | V | 1 | +| | Fixed part identity | Fixed part identity subclause 10.5.3.6 | M | LV | 2 - 10 | +| | Reject cause | Reject cause GSM 04.08 subclause 10.5.3.6 | M | V | 1 | + +## 9.2.9 CTS MS authentication request + +This message is sent by the fixed part to request authentication of the mobile station. See table 9.2.12/GSM 04.56. + +Message type: CTS MS AUTHENTICATION REQUEST + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.12/GSM 04.56: CTS MS AUTHENTICATION REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|------------------------------------------------------------|----------|--------|--------| +| | CTS mobility management protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS MS authentication request message type | Message type subclause 10.4 | M | V | 1 | +| | Ciphering key sequence number | Ciphering key sequence number GSM 04.08 subclause 10.5.1.2 | M | V | 1/2 | +| | Spare half octet | Spare half octet GSM 04.08 subclause 10.5.1.8 | M | V | 1/2 | +| | Authentication parameter CH1 | Auth. parameter CH subclause 10.5.3.3 | M | V | 16 | +| 03 | Authentication parameter RIMS | Auth. parameter RIMS subclause 10.5.3.1 | O | TV | 9 | + +## 9.2.10 CTS MS authentication response + +This message is sent by the mobile station to the fixed part to deliver a calculated response to the fixed part and to request authentication of the fixed part. See table 9.2.13/GSM 04.56. + +Message type: CTS MS AUTHENTICATION RESPONSE + +Significance: dual + +Direction: mobile station to fixed part + +**Table 9.2.13/GSM 04.56: CTS MS AUTHENTICATION RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------|---------------------------------------------|----------|--------|--------| +| | CTS mobility management Protocol discriminator | Protocol discriminator subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator subclause 10.3.1 | M | V | 1/2 | +| | CTS MS authentication Response message type | Message type subclause 10.4 | M | V | 1 | +| | Authentication Parameter SRES1 | Auth. parameter XRES subclause 10.5.3.4 | M | V | 16 | +| | Authentication Parameter CH2 | Auth. parameter CH subclause 10.5.3.3 | M | V | 16 | +| 04 | Authentication Parameter RIFP | Auth. parameter RIFP subclause 10.5.3.2 | O | TV | 9 | + +## 9.2.11 CTS FP authentication response + +This message is sent by the fixed part to the mobile station to deliver a calculated response to the mobile station. See table 9.2.14/GSM 04.56. + +Message type: CTS FP AUTHENTICATION RESPONSE + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.14/GSM 04.56: CTS FP AUTHENTICATION RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|------------------------------------------------|----------|--------|--------| +| | CTS mobility management
Protocol discriminator | Protocol discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS FP authentication response
Message type | Message type
subclause 10.4 | M | V | 1 | +| | Authentication
Parameter SRES2 | Auth. parameter XRES
subclause 10.5.3.4 | M | V | 16 | + +## 9.2.12 CTS MS authentication reject + +This message is sent by the fixed part to the mobile station to indicate that the authentication has failed (and that the receiving mobile station shall abort all activities). See table 9.2.15/GSM 04.56. + +Message type: CTS MS AUTHENTICATION REJECT + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.15/GSM 04.56: CTS MS AUTHENTICATION REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|------------------------------------------------|----------|--------|--------| +| | CTS mobility management
Protocol discriminator | Protocol discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTS MS authentication reject
Message type | Message type
subclause 10.4 | M | V | 1 | +| | Fixed part identity | Fixed part identity
subclause 10.5.3.6 | M | LV | 2 - 10 | + +## 9.2.13 CTSMSI update command + +This message is sent by the fixed part to the mobile station to update the CTSMSI. See table 9.2.16/GSM 04.56. + +Message type: CTSMSI UPDATE COMMAND + +Significance: dual + +Direction: fixed part to mobile station + +**Table 9.2.16/GSM 04.56: CTS MSI UPDATE COMMAND message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|------------------------------------------------|----------|--------|--------| +| | CTS mobility management
Protocol discriminator | Protocol discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTSMSI update command
Message type | Message type
subclause 10.4 | M | V | 1 | +| | Mobile identity | Mobile identity
subclause 10.5.1.1 | M | LV | 2 - 9 | + +## 9.2.14 CTSMI update complete + +This message is sent by the mobile station to the fixed part to indicate that the update of the CTSMI has taken place. See table 9.2.17/GSM 04.56. + +Message type: CTSMI UPDATE COMPLETE + +Significance: dual + +Direction: mobile station to fixed part + +**Table 9.2.17/GSM 04.56: CTSMI UPDATE COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|------------------------------------------------|----------|--------|--------| +| | CTS mobility management
Protocol discriminator | Protocol discriminator
subclause 10.2 | M | V | 1/2 | +| | Sub-Protocol Discriminator | Sub-Protocol Discriminator
subclause 10.3.1 | M | V | 1/2 | +| | CTSMI update complete
Message type | Message type
subclause 10.4 | M | V | 1 | + +# 10 General message format and information elements coding + +The figures and text in this clause describe the Information Elements contents. + +## 10.1 Overview + +See corresponding subclause in GSM 04.08. + +## 10.2 Protocol Discriminator + +The Protocol Discriminator (PD) and its use are defined in GSM 04.07 [20]. + +## 10.3 Sub-Protocol Discriminator and transaction identifier + +### 10.3.1 Sub-Protocol Discriminator + +Bits 5 to 8 of the first octet of every CTS Radio Resource management and CTS Mobility Management message contains the Sub-Protocol Discriminator. The Sub-Protocol Discriminator (SPD) and its use are defined in GSM 04.07. + +### 10.3.2 Transaction identifier + +See GSM 04.08. + +## 10.4 Message Type + +The message type IE and its use are defined in GSM 04.07 [20]. Tables 10.1/GSM 04.56, and 10.1/GSM 04.08 define the value part of the message type IE used in the Radio Resource management protocol, the Mobility Management protocol, the Call Control protocol, and Session management protocol. + +**Table 10.1/GSM 04.56: Message types for Radio Resource management** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|---------------------------------------| +| 0 | 0 | 1 | 1 | 1 | - | - | - | Channel establishment messages: | +| | | | 1 | 1 | 1 | - | - | - CTS IMMEDIATE ASSIGNMENT | +| | | | 0 | 0 | 1 | - | - | - CTS IMMEDIATE ASSIGNMENT EXTENDED | +| | | | 0 | 1 | 0 | - | - | - CTS IMMEDIATE ASSIGNMENT REJECT | +| 0 | 0 | 1 | 1 | 0 | - | - | - | Ciphering messages: | +| | | | 1 | 0 | 1 | - | - | - CTS CIPHERING MODE COMMAND | +| | | | 0 | 1 | 0 | - | - | - CTS CIPHERING MODE COMPLETE | +| 0 | 0 | 1 | 0 | 1 | - | - | - | Handover messages: | +| | | | 0 | 1 | 1 | - | - | - CTS INTRACELL HANDOVER COMMAND | +| | | | 1 | 0 | 0 | - | - | - CTS INTRACELLHANDOVER COMPLETE | +| | | | 0 | 0 | 0 | - | - | - CTS INTRACELLHANDOVER FAILURE | +| 0 | 0 | 0 | 0 | 1 | - | - | - | Channel release messages: | +| | | | 1 | 0 | 1 | - | - | - CTS CHANNEL RELEASE | +| 0 | 0 | 1 | 0 | 0 | - | - | - | Paging messages: | +| | | | 0 | 0 | 1 | - | - | - CTS PAGING REQUEST | +| | | | 0 | 1 | 0 | - | - | - CTS GROUP ALERTING | +| | | | 1 | 0 | 0 | - | - | - CTS HUNTING | +| | | | 1 | 1 | 1 | - | - | - CTS PAGING RESPONSE | +| 0 | 0 | 0 | 1 | 1 | - | - | - | System information messages: | +| | | | 0 | 0 | 1 | - | - | - CTS SYSTEM INFORMATION TYPE 1 | +| | | | 0 | 1 | 0 | - | - | - CTS SYSTEM INFORMATION TYPE 2 | +| | | | 0 | 1 | 1 | - | - | - CTS SYSTEM INFORMATION TYPE 3 | +| 0 | 0 | 0 | 1 | 0 | - | - | - | Miscellaneous messages: | +| | | | 0 | 0 | 0 | - | - | - CTS CHANNEL MODE MODIFY | +| | | | 0 | 1 | 0 | - | - | - CTS RR STATUS | +| | | | 1 | 1 | 1 | - | - | - CTS CHANNEL MODE MODIFY ACKNOWLEDGE | +| | | | 1 | 0 | 0 | - | - | - CTS FREQUENCY REDEFINITION | +| | | | 1 | 0 | 1 | - | - | - CTS MEASUREMENT REPORT | +| | | | 1 | 1 | 0 | - | - | - CTS CLASSMARK CHANGE | +| | | | 0 | 1 | 1 | - | - | - CTS CLASSMARK ENQUIRY | + +Bit 8 is reserved for possible future use as an extension bit, see GSM 04.07. + +**Table 10.2/GSM 04.56: Message types for Mobility Management** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|----------------------------------| +| 0 | x | 0 | 0 | - | - | - | - | Registration messages: | +| | | | 0 | 0 | 0 | 1 | - | - CTS DETACH INDICATION | +| | | | 0 | 0 | 1 | 0 | - | - CTS ATTACH ACCEPT | +| | | | 0 | 1 | 0 | 0 | - | - CTS ATTACH REJECT | +| | | | 1 | 0 | 0 | 0 | - | - CTS ATTACH REQUEST | +| | | | 1 | 1 | 0 | 1 | - | - CTS RE-ATTACH REQUEST | +| | | | 1 | 1 | 1 | 0 | - | - CTS RE-ATTACH ACCEPT | +| 0 | x | 0 | 1 | - | - | - | - | Security messages: | +| | | | 0 | 0 | 0 | 1 | - | - CTS MS AUTHENTICATION REJECT | +| | | | 0 | 0 | 1 | 0 | - | - CTS MS AUTHENTICATION REQUEST | +| | | | 0 | 1 | 0 | 0 | - | - CTS MS AUTHENTICATION RESPONSE | +| | | | 0 | 1 | 0 | 1 | - | - CTS FP AUTHENTICATION RESPONSE | +| | | | 1 | 0 | 1 | 0 | - | - CTSMSI UPDATE COMMAND | +| | | | 1 | 0 | 1 | 1 | - | - CTSMSI UPDATE COMPLETE | +| 0 | x | 1 | 0 | - | - | - | - | Enrolment messages: | +| | | | 0 | 0 | 0 | 1 | - | - CTS ENROLMENT REQUEST | +| | | | 0 | 0 | 1 | 0 | - | - CTS ENROLMENT RESPONSE | +| | | | 0 | 0 | 1 | 1 | - | - CTS ENROLMENT REJECT | +| | | | 0 | 1 | 0 | 0 | - | - CTS DE-ENROLMENT INDICATION | + +Bit 8 is reserved for possible future use as an extension bit, see GSM 04.07. + +Bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bit 7 is coded with a "0". See GSM 04.07. + +## 10.5 Other information elements + +See corresponding subclause in GSM 04.08. + +### 10.5.1 Common information elements. + +#### 10.5.1.1 Mobile Identity + +The purpose of the *Mobile Identity* information element is to provide either the international mobile subscriber identity, IMSI, or the international mobile equipment identity, IMEI, or the international mobile equipment identity together with the software version number, IMEISV or the CTS Mobile Subscriber Identity CTSMISI (see GSM 03.03). + +The *Mobile Identity* information element is coded as shown in figure 10.5/GSM 04.08, table 10.8/GSM 04.08 and table 10.4/GSM 04.56. + +**Table 10.4/GSM 04.56: *Mobile Identity* information element** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Type of identity (octet 3) | | +| Bits | | +| 3 | 2 1 | +| 0 0 1 | IMSI | +| 0 1 0 | IMEI | +| 0 1 1 | IMEISV | +| 1 0 1 | CTSMISI | +| All other values are defined in GSM 04.08 or reserved. | | +| Identity digits (octet 3 etc. figure 10.5 GSM 04.08) | | +| For CTSMISI, this field is coded using hexadecimal coding. The 22 bits of the CTSMISI are padded with 6 leading zeroes for having a 5 hexadecimal digits identity as follow: | | +| original CTSMISI: | xx xxxx xxxx xxxx xxxx xxxx | +| padded CTSMISI: | 0000 00xx xxxx xxxx xxxx xxxx xxxx | +| hex coded CTSMISI: | H1 H2 H3 H4 H5 H6 H7 | +| The Odd/even indication shall be set to odd for CTSMISI identity. | | + +### 10.5.2 Radio Resource management information elements + +#### 10.5.2.1 CTSMISI + +The purpose of the CTSMISI information element is to provide the CTS-MS Subscriber Identity for paging purposes. + +The CTSMISI information element is coded as shown in figure 10.1/GSM 04.56. + +The CTSMISI is a type 3 information element with 3 octets length. + +![](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------|------------|--------------|---|---|---|---|---|---------| +| CTSMSI IEI | | | | | | | | octet 1 | +| 0
spare | 0
spare | CTSMSI value | | | | | | octet 2 | +| CTSMSI value (contd) | | | | | | | | octet 3 | +| CTSMSI value (contd) | | | | | | | | octet 4 | + +**Figure 10.1/GSM 04.56: CTSMSI information element** + +**Table 10.5/GSM 04.56: CTSMSI information element** + +CTSMSI value (octet 2, 3 and 4) + Bit 6 of octet 2 is the most significant bit and bit 1 of octet 4 is the least significant bit. + The coding of the CTSMSI shall be done according to GSM 03.03. The length is 22 bits. + +NOTE: For purposes other than paging the CTSMSI should be provided using the mobile identity information element. + +### 10.5.2.2 TFH General Parameters + +The purpose of the *TFH General Parameters* information element is to provide the VA and VV vectors used in the hopping sequence. + +![](f4b570ddd089f54943d46e9f8776f9f9_img.jpg) + +| TFH General Parameters IEI | | | | | | | | octet 1 | +|----------------------------|-----|-----|-----|-----|-----|----|----|----------| +| v15 | v14 | v13 | v12 | v11 | v10 | v9 | v8 | octet 2 | +| v7 | v6 | v5 | v4 | v3 | v2 | v1 | v0 | octet 3 | +| a15 | | | | a14 | | | | octet 4 | +| a13 | | | | a12 | | | | octet 5 | +| a11 | | | | a10 | | | | octet 6 | +| a9 | | | | a8 | | | | octet 7 | +| a7 | | | | a6 | | | | octet 8 | +| a5 | | | | a4 | | | | octet 9 | +| a3 | | | | a2 | | | | octet 10 | +| a15 | | | | a0 | | | | octet 11 | + +**Figure 10.2/GSM 04.56: TFH General Parameters information element** + +### 10.5.2.3 TFH Current Parameters + +The purpose of the *TFH Current Parameters* information element is to provide the CSR value, the TFH Counter 1 value, the TFH Counter 2 values, and the VC vector used in the hopping sequence. + +![](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------|---|---|---|---|---|---|---|---------| +| TFH Current Parameters IEI | | | | | | | | octet 1 | +| Length of TFH Current Parameters contents (high part) | | | | | | | | octet 2 | +| CSR (high part) | | | | | | | | octet 3 | +| CSR (low part) | | | | | | | | octet 4 | +| Counter 1 (high part) | | | | | | | | octet 5 | +| Counter 1 (low part) | | | | | | | | octet 6 | +| Counter 2 (high part) | | | | | | | | octet 7 | +| Counter 2 (low part) | | | | | | | | octet 8 | +| VC | | | | | | | | octet 9 | +| . | | | | | | | | . | +| . | | | | | | | | . | +| VC | | | | | | | | octet n | + +**Figure 10.3/GSM 04.56: TFH Current Parameters information element** + +**Table 10.6/GSM 04.56: TFH Current Parameters information element** + +| | +|----------------------------------------------------------------------------------------| +| CSR (octets 3 and 4)
Current value of the shift register | +| Counter 1 (octets 5 and 6)
Current value of the counter 1 padded to a 16 bits value | +| Counter 1 (octets 7 and 8)
Current value of the counter 8 padded to a 16 bits value | +| VC (octets 9 to n)
Base sequence for the hopping sequence. See GSM 05.02 | + +## 10.5.2.4 CTS Channel Description + +The purpose of the *CTS Channel Description* information element is to provide a description of an allocable channel together with its SACCH. + +The *CTS Channel Description* information element is coded as shown in figure 10.19/GSM 04.08, table 10.23/GSM 04.08 and table 10.5x/GSM 04.56. + +**Table 10.7/GSM 04.56: CTS Channel Description information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Channel Type and TDMA offset (octet 2) shall be set to TCH/F and ACCHs by the CTS-FP. CTS-MSs shall also support all value defined in table 10.23/GSM 04.08. | +| TSC (octet 3) shall be set to 0 by the CTS-FP and ignored by the CTS-MSs. | +| HSN (octet 4 bit 6 to 1) shall be set to 0 by the CTS-FP and ignored by the CTS-MS | + +### 10.5.2.5 CTS Access Request Reference + +The purpose of the *CTS Access Request Reference* information element is to provide the access request information used in the CTSARCH channel. + +The *CTS Access Request* information elements coded as shown in figure 10.4/GSM 04.56 and table 10.8/GSM 04.56. + +The *CTS Access Request* is a type 3 information element with 5 octets length. + +![](91c33f8e1713989e8192322ec2d1212b_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|---|---|---|---|---|---------| +| Access Request Reference IEI | | | | | | | | octet 1 | +| Access Request Information | | | | | | | | octet 2 | +| Access Request Information | | | | | | | | octet 3 | +| Access Request Information | | | | | | | | octet 4 | +| Acc.
Rq. I | | | | | | | | octet 5 | + +**Figure 10.4/GSM 04.56: Access request Reference information element** + +**Table 10.8/GSM 04.08: Access request Reference information element** + +Access Request Information +This is an unformatted 25 bits field. Typically the contents of this field are coded the same as the CTS ACCESS REQUEST message. + +### 10.5.2.6 CTS L1 information + +The purpose of the *CTS L1 information* information element is to provide the TDMA frame number of the last burst containing the message. + +![](a2586540d49d5665489c8b5a273f86d3_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------|--------------------------------|----|---|----|---|---|---|---------| +| | CTS L1 information IEI octet 1 | | | | | | | octet 1 | +| T1 (high) | | | | | | | | octet 2 | +| T1 (low) | | | | T2 | | | | octet 3 | +| 0 spare | 0 spare | T3 | | | | | | octet 4 | + +**Figure 10.5/GSM 04.56: CTS L1 information information element** + +**Table 10.5/GSM 04.56: CTS L1 information information element** + +T1 (octet 2 and 3): +It is coded as the binary representation of $FN \text{ div } (26 \cdot 51)$ . Bit 8 of octet 2 is the most significant bit and bit 7 of octet 3 is the least significant bit. + +T2 (octet 3): +It is coded as the binary representation of $FN \bmod 26$ . + +T3 (octet 4): +It is coded as the binary representation of $FN \bmod 51$ . + +The computation of the FN is given in GSM 05.10. + +### 10.5.2.7 Information Transfert Capability + +The purpose of the *Information Transfert Capability* information element is to convey the information transfert capability. See figure 10.x/GSM 04.56 and table 10.72/GSM 04.08. + +![](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|--------------------------------|---|---|---|----------------------------|---|---|---------| +| | Info. Transfert Capability IEI | | | 0 | Info. Transfert Capability | | | octet 1 | + +Figure 10.6/GSM 04.56: *Information Transfert Capability* information element + +### 10.5.2.8 BCD Display + +The purpose of the *BCD Display* information element is to convey a BCD coded telephone number. + +![](42f0611a8a2766c986ff45551918ca5d_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------|-----------------|---|---|------------|---|---|---|---------| +| | BCD Display IEI | | | | | | | octet 1 | +| Length of BCD Display contents | | | | | | | | octet 2 | +| digit 2 | | | | digit 1 | | | | octet 3 | +| . | | | | . | | | | . | +| digit 2n | | | | digit 2n-1 | | | | octet n | + +Figure 10.7/GSM 04.56: *BCD Display* information element + +Table 10.9/GSM 04.08: *BCD Display* information element + +| | | +|---------------------------------------------------------------------------------|---------------| +| Digits are encoded as described in table 10.81/GSM 04.08 except for digit 1110: | | +| Bits | | +| 4 3 2 1 | | +| 1 1 1 0 | + (plus sign) | + +### 10.5.2.9 AFA Interference Level + +The purpose of the *AFA Interference Level* information element is to provide the results of the interference measurements made by the CTS-MS on the current serving CTS-cell. + +![](24a27d17656bcf0ee131539f2bbb34cd_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------|----------------------------|-----------------------|---|---|---|---|---|-------------| +| | AFA Interference Level IEI | | | | | | | octet 1 | +| Length of AFA Interference Level contents (high part) | | | | | | | | octet 2 | +| 0 | 0 | Interference level[1] | | | | | | octet 3 | +| 0 | 0 | Interference level[2] | | | | | | octet 4 | +| . | | . | | | | | | . | +| 0 | 0 | Interference level[N] | | | | | | octet N + 2 | + +Figure 10.8/GSM 04.56: *AFA Interference Level* information element + +**Table 10.10/GSM 04.56: AFA Interference Level information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Interference level[k] (octet k + 2)
Received interference level for the k th carrier of the AFA monitoring frequency list (see GSM 05.08). | +|----------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 10.5.2.10 AFA Monitoring Cycles + +The purpose of the *AFA Monitoring Cycles* information element is to specify a number of AFA monitoring cycles. + +![](18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg) + +| | | | | | | | | | | +|--|---------------------------|---|---|---|---|---|--------------|------|---------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | AFA Monitoring Cycles IEI | | | | | | | | octet 1 | +| | 0 | 0 | 0 | 0 | 0 | 0 | ½ | NAMC | octet 2 | +| | spare | | | | | | ½(high part) | | | +| | NAMC | | | | | | | | octet 3 | +| | (low part) | | | | | | | | | + +**Figure 10.10/GSM 04.56: AFA Monitoring Cycles information element****Table 10.11/GSM 04.56: AFA Monitoring Cycles information element** + +| | +|--------------------------------------------------------------------------| +| NAMC (octet 2 and 3)
Number of AFA monitoring cycles (see GSM 05.08). | +|--------------------------------------------------------------------------| + +### 10.5.2.11 OFO Measurement Results + +The purpose of the *OFO Measurement Results* is to provide the results of the OFO measurements made by the CTS-MS on the current serving CTS-cell. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0. + +![](c64555b7f91435b01997807dbb4bcc4c_img.jpg) + +| | | | | | | | | | | +|--|--------------------------------------------|-----------|---|---|---|---|---|--------------|---------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | OFO Measurement Result IEI | | | | | | | | octet 1 | +| | Length of OFO Measurement Results contents | | | | | | | | octet 2 | +| | OFO | | | | | | | OFO value[1] | octet 3 | +| | status[1] | | | | | | | (high part) | | +| | OFO 1 | OFO | | | | | | OFO value[2] | octet 4 | +| | (low) | status[2] | | | | | | (high part) | | +| | OFO Value 2 | OFO | | | | | | OFO value[3] | octet 5 | +| | (low part) | status[3] | | | | | | (high part) | | +| | . and so on. | | | | | | | | | + +**Figure 10.11/GSM 04.56: OFO Measurement Results information element** + +**Table 10.12/GSM 04.56: OFO Measurement Results information element** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| OFO value[k]
OFO measurement value for the k th carrier of the OFO measurement BCCH list (see GSM 05.08).

OFO status[k]
OFO measurement status of the k th BCCH carrier:
Bits
2 1
0 0 measurement OK
0 1 measurement failed
1 0 measurement not performed | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 10.5.2.12      Paging type + +The purpose of the Paging type information element is to provide the CTS-MS Subscriber Identity for paging purposes. + +The Paging type information element is coded as shown in figure 10.1/GSM 04.56. + +The Paging type is a type 3 information element with 2 octets length. + +![](8adc21ec44b6c7debe36fed5b1bb044f_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|-----------------|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Paging type IEI | | | | | | | | octet 1 | +| AC field | | | 0
spare bits | | | | | octet 2 | + +Figure 10.1/GSM 04.56: Paging type information element + +**Table 10.5/GSM 04.56: Paging type information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AC field (octet 2, bits 8,7 and 6)
000 Start paging procedure
100 Start Alive Check procedure
other values are reserved for future use

Octet 2, bits 5 to 1 are spare bits. | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 10.5.2.13 CTS selection parameters + +The purpose of the CTS selection parameters information element is to provide the value of the parameters needed for the FP selection procedure. + +The CTS selection parameters information element is coded as shown in figure 10.22/GSM 04.56 and table 10.22/GSM 04.56. + +The CTS selection parameters is a type 3 information element with 3 octets length. + +![](6f89a9b12884589d3a907f9df6c5c4c3_img.jpg) + +| | | | | | | | | | +|------------------------------|------------|----------------------|------------------------|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| CTS selection parameters IEI | | | | | | | | octet 1 | +| 0
spare | 0
spare | 0
spare | CTS MS MAX TXPWR value | | | | | octet 2 | +| 0
spare | 0
spare | CTS RXLEV ACCESS MIN | | | | | | octet 3 | + +**Figure 10.22/GSM 04.56 CTS selection parameters information element** + +**Table 10.22GSM 04.56: CTS selection parameters information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

CTS MS MAX TXPWR (octet 2):
It is coded as the binary representation of the maximum authorised output power control level a CTS-MS shall use with this CTS-FP.
Range: 0 to 31 (See GSM 05.08)

CTS RXLEV ACCESS MIN (octet 3):
It is coded as the binary representation of the minimum received signal level at the MS for which it is permitted to access the CTS FP.
Range: 0 to 63 (See GSM 05.08)

| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 10.5.2.14 CTS RR parameters + +The purpose of the CTS RR parameters information element is to provide the value of the parameters needed for the CTS dedicated and idle modes. + +The CTS RR parameters information element is coded as shown in figure 10.23/GSM 04.56 and table 10.23/GSM 04.56. + +The CTS RR parameters is a type 3 information element with 5 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|------------|--------------------------|------------|------------------------|-------------------------|---|---|---------| +| CTS selection parameters IEI | | | | | | | | octet 1 | +| 0
spare | 0
spare | CTS CELL RESELECT OFFSET | | | | | | octet 2 | +| 0
spare | 0
spare | 0
spare | 0
spare | CTS RADIO LINK TIMEOUT | | | | octet 3 | +| 0
spare | 0
spare | 0
spare | 0
spare | 0
spare | Number of paging groups | | | octet 4 | +| CTSPCH DECOD | | | | | | | | octet 5 | + +**Figure 10.23/GSM 04.56: CTS RR parameters information element****Table 10.23GSM 04.56: CTS RR parameters information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

CTS CELL RESELECT OFFSET (octet 2):
It is coded as the binary representation of the offset in dB to be applied for the C2 CTS criterion.
Range: 0 to 63 (See GSM 05.08)

CTS RADIO LINK TIMEOUT (octet 3):
It is coded as the binary representation of the maximum value of the radio link counter.
Range: 0(4 SACCH blocks) to 15(64 SACCH blocks) (See GSM 05.08)

Number of paging groups (octet 4):
It is coded as the representation of the number of multiframes period for transmission of CTS PAGING REQUEST to the same paging subgroup (see GSM 05.02)
Range: 0 to 7 with
0 means 2 multiframes period and
2 means 9 multiframes period (refer to GSM 04.08 table 10.29)

CTSPCH DECOD (octet 5)
It is coded as the binary representation of the number of non-decoded paging messages before declaring a downlink paging failure (see GSM 05.08).
Range: 1 to 255; 0 is a reserved value and shall not be sent by the CTS-FP

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 10.5.2.15 Timeslot shifting parameters + +The purpose of the Timeslot shifting parameters information element is to provide the value of the parameters + +The Timeslot shifting parameters information element is coded as shown in figure 10.24/GSM 04.56 and table 10.24/GSM 04.56. + +The Timeslot shifting parameters is a type 3 information element with 5 octets length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|----|---|-------|----|---|---|---|---------| +| Timeslot shifting parameters IEI | | | | | | | | octet 1 | +| TNSCO | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| spare | | | | | | | | octet 2 | +| 0 | x0 | | 0 | x1 | | | | octet 3 | +| spare | | | spare | | | | | | +| 0 | x2 | | 0 | x3 | | | | octet 4 | +| spare | | | spare | | | | | | + +**Figure 10.24/GSM 04.56: Timeslot shifting parameters information element** + +**Table 10.24GSM 04.56: Timeslot shifting parameters information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| TNSCO, TNS Couple Order (octet 2): | +| Bit | +| 8 | +| 0 see GSM 05.03 | +| 1 see GSM 05.03 | +| x0 (octet 3):
It is coded as the binary value of the parameter x0 needed to form the timeslot shifting sequence
Range: 0 to 7 (see GSM 05.02) | +| x1 (octet 3):
It is coded as the binary value of the parameter x1 needed to form the timeslot shifting sequence
Range: 0 to 7 (see GSM 05.02) | +| x2 (octet 4):
It is coded as the binary value of the parameter x2 needed to form the timeslot shifting sequence
Range: 0 to 7 (see GSM 05.02) | +| x3 (octet 4):
It is coded as the binary value of the parameter x3 needed to form the timeslot shifting sequence
Range: 0 to 7 (see GSM 05.02) | + +## 10.5.3 Mobility management information elements + +### 10.5.3.1 Authentication parameter RIMS + +The purpose of the *Authentication Parameter RIMS* information element is to provide the mobile station with a non-predictable number to be used to calculate the mutual initial key Kinit. + +The *Authentication Parameter RIMS* information element is coded as shown in figure 10.12/GSM 04.56 and table 10.13/GSM 04.56. + +The *Authentication Parameter RIMS* is a type 3 information element with 9 octets length. + +![](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|---|---|---|---|---|---|---|---------| +| Authentication parameter RIMS IEI | | | | | | | | octet 1 | +| RIMS value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | | +| | | | | | | | | octet 9 | + +**Figure 10.12/GSM 04.56: Authentication Parameter RIMS information element** + +**Table 10.13/GSM 04.56: Authentication Parameter RIMS information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------| +| RIMS value (octet 2, 3, ... and 9) | +| The RIMS value consists of 64 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 9 is the least significant bit. | + +### 10.5.3.2 Authentication parameter RIFP + +The purpose of the *Authentication Parameter RIFP* information element is to provide the fixed part with a non-predictable number to be used to calculate the mutual initial key Kinit. + +The *Authentication Parameter RIFP* information element is coded as shown in figure 10.13/GSM 04.56 and table 10.14/GSM 04.56. + +The *Authentication Parameter RIFP* is a type 3 information element with 9 octets length. + +![](7b2d685b805535c1e94aee1365753b92_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|---|---|---|---|---|---|---|---------| +| Authentication parameter RIFP IEI | | | | | | | | octet 1 | +| RIFP value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | | +| | | | | | | | | octet 9 | + +**Figure 10.13/GSM 04.56: Authentication Parameter RIFP information element** + +**Table 10.14/GSM 04.56: Authentication Parameter RIFP information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------| +| RIFP value (octet 2, 3, ... and 9) | +| The RIFP value consists of 64 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 9 is the least significant bit. | + +### 10.5.3.3 Authentication parameter CH + +The purpose of the *Authentication Parameter CH* information element is to provide the mobile station or the fixed part with a non-predictable number to be used to calculate the authentication response signature XRES and the ciphering key Kc. + +The *Authentication Parameter CH* information element is coded as shown in figure 10.14/GSM 04.56 and table 10.15/GSM 04.56. + +The *Authentication Parameter CH* is a type 3 information element with 17 octets length. + +![](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|---|---|---|---|----------| +| Authentication parameter CH IEI | | | | | | | | octet 1 | +| CH value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | octet 17 | + +**Figure 10.14/GSM 04.56: Authentication Parameter CH information element** + +**Table 10.15/GSM 04.56: Authentication Parameter CH information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------| +| CH value (octet 2, 3, ... and 17) | +| The CH value consists of 128 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 17 is the least significant bit. | + +### 10.5.3.4 Authentication parameter XRES + +The purpose of the *authentication parameter XRES* information element is to provide the fixed part or the mobile station with the authentication response signature calculated in the mobile station or in the fixed part. + +The *Authentication Parameter XRES* information element is coded as shown in figure 10.15/GSM 04.56 and table 10.16/GSM 04.56. + +The *Authentication Parameter XRES* is a type 3 information element with 17 octets length. + +![](0adcd19063a66145a465add40bf956e6_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|---|---|---|---|---|---|---|----------| +| Authentication parameter XRES IEI | | | | | | | | octet 1 | +| XRES value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | octet 17 | + +**Figure 10.15/GSM 04.56: Authentication Parameter XRES information element** + +**Table 10.16/GSM 04.56: Authentication Parameter XRES information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------| +| XRES value (octet 2, 3, ... and 17) | +| The XRES value consists of 128 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 17 is the least significant bit. | + +### 10.5.3.5 Authentication parameter Kax + +The purpose of the *Authentication Parameter Kax* information element is to provide the mobile station with the authentication key. + +The *Authentication Parameter Kax* information element is coded as shown in figure 10.16/GSM 04.56 and table 10.17/GSM 04.56. + +The *Authentication Parameter Kax* is a type 3 information element with 17 octets length. + +![](c07e21a8d65991db04263322f859c94f_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|---|---|---|---|---|---|---|----------| +| Authentication parameter Kax IEI | | | | | | | | octet 1 | +| Kax value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | octet 17 | + +**Figure 10.16/GSM 04.56: Authentication Parameter Kax information element** + +**Table 10.17/GSM 04.56: Authentication Parameter Kax information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------| +| Kax value (octet 2, 3, ... and 17) | +| The Kax value consists of 128 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 17 is the least significant bit. | + +### 10.5.3.6 Fixed part Identity + +The purpose of the *Fixed part Identity* information element is to provide either the international fixed part subscriber identity, IFPSI or the international fixed part equipment identity, IFPEI. + +The IFPSI shall not exceed 15 digits, the IFPEI is composed of 16 digits (see GSM 03.03). + +The *Fixed part Identity* information element is coded as shown in figure 10.17/GSM 04.56 and table 10.18/GSM 04.56. + +The Fixed part Identity is a type 4 information element with a minimum length of 3 octets and 11 octets length maximal. + +![](e8c2fa58b461352bbb1b098928737da2_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------|---|---|---|-----------------------|------------------|---|---|----------| +| Fixed part Identity IEI | | | | | | | | octet 1 | +| Length of fixed part identity contents | | | | | | | | octet 2 | +| Identity digit 1 | | | | odd/
even
indic | Type of identity | | | octet 3 | +| Identity digit p+1 | | | | Identity digit p | | | | octet 4* | + +**Figure 10.17/GSM 04.56: Fixed part Identity information element** + +**Table 10.18/GSM 04.56: Fixed part Identity information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type of identity (octet 3) | +| Bits | +| 3 2 1 | +| 0 0 1 IFPSI | +| 0 1 0 IFPEI | +| All other values are reserved. | +| Odd/even indication (octet 3) | +| Bit | +| 4 | +| 0 even number of identity digits and also when | +| 1 odd number of identity digits | +| Identity digits (octet 3 etc) | +| For the IFPSI, IFPEI this field is coded using BCD coding. If the number of identity digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". | + +### 10.5.3.7 CTS mobile group list + +The purpose of the *CTS mobile group list* information element is to provide a list containing up to 8 CTSMISI. The *CTS mobile group list* information element is coded as shown in figure 10.18/GSM 04.56 and table 10.19/GSM 04.56. + +The *CTS mobile group list* is a type 4 information element with a minimum length of 5 octets and 26 octets length maximal. + +![](0d9b44054c70dcda35129f11b97a912f_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|---------| +| CTS mobile group list IEI | | | | | | | | octet 1 | +| Length of CTS mobile group list contents | | | | | | | | octet 2 | +| CTSMISI 1 (first octet) | | | | | | | | octet 3 | +| CTSMISI 1 (second octet) | | | | | | | | octet 3 | +| CTSMISI 1 (third octet) | | | | | | | | octet 3 | +| ⋮ | | | | | | | | | +| CTSMISI n (third octet) | | | | | | | | octet m | + +**Figure 10.18/GSM 04.56: CTS mobile group list information element****Table 10.19/GSM 04.56: CTS mobile group list information element** + +| | +|-----------------------------------------------------------------------------------------------------------| +| CTSMISI (octets 2, 3, and n) | +| Each CTSMISI consists of 3 octets. They are defined in subclause 10.5.2.1. | +| The first one corresponds to octet 2 in 10.5.2.1, the second one to octet 3 and the third one to octet 4. | + +### 10.5.3.8 Following attach request + +The purpose of the *Following attach request* information element is to indicate that an attach request may be done on an existing RR connection. + +The *Following attach request* information element is coded as shown in figure 10.19/GSM 04.56. + +The *Following attach request* is a type 2 information element. + +![](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|---|---|---|---|---|---------| +| Following attach request IEI | | | | | | | | octet 1 | + +**Figure 10.19/GSM 04.56: Following attach request information element** + +### 10.5.3.9 Access right identity + +The purpose of the *Access right identity* information element is to provide the FPBI and the length of its significant part for access to this fixed part. + +The *Access right identity* information element is coded as shown in figure 10.20/GSM 04.56 and table 10.20/GSM 04.56. + +The *Access right identity* is a type 3 information element with 4 octets length. + +![](f92e919c70b7adda2d0e778889f44fae_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------|---|---|---|-------------|---|---|---|---------| +| Access right identity IEI | | | | | | | | octet 1 | +| FPBI Length Identifier | | | | FBPI (high) | | | | octet 2 | +| FPBI (middle) | | | | | | | | octet 3 | +| FPBI (low) | | | | | | | | octet 4 | + +**Figure 10.20/GSM 04.56: Access right identity information element** + +**Table 10.20/GSM 04.56: Access right identity information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------| +| FBPI Length Indicator (octet 2 bit 8 to 4) | +| The FLI is the length in bits of the FPBI significant part. | +| FBPI (octet 2 bit 3 to 1 and octets 3 and 4) | +| The FPBI value consists of 19 bits. Bit 3 of octet 2 is the most significant bit while bit 1 of octet 4 is the least significant bit. | + +### 10.5.3.10 TC3252 + +The purpose of the *TC3252* information element is to provide the value of the timer TC3252. + +The *TC3252* information element is coded as shown in figure 10.21/GSM 04.5656 and table 10.21/GSM 04.56. + +The *TC3252* is a type 3 information element with 2 octets length. + +![](b47f393ea2c781f313367435c7166abb_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------|---|---|---|---|---|---|---|---------| +| TC3252 IEI | | | | | | | | octet 1 | +| TC3252 value | | | | | | | | octet 2 | + +**Figure 10.21/GSM 04.56: TC3252 information element** + +**Table 10.21GSM 04.56: TC3252 information element** + +| | +|-----------------------------------------------------------------| +| TC3252 value | +| It is the value in deciminutes (6 seconds) of the timer TC3252. | + +### 10.5.3.11 Attach type + +The purpose of the Attach type information element is to indicate whether a normal attach or a reattach is wanted. It may also indicate that a follow-on request has been received from the mobile station CM layer. + +The Attach type information element is coded as shown in figure 10.22/GSM 04.56 and table 10.22/GSM 04.56. + +The Attach type is a type 1 information element. + +![](4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg) + +| | | | | | | | | | +|-----------------|---|---|---|-----|-------|--------|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Attach type IEI | | | | FOR | 0 | Attach | | octet 1 | +| | | | | | spare | type | | | + +**Figure 10.22/GSM 04.56: Attach type information element** + +**Table 10.22/GSM 04.56: Attach type information element** + +| | | | +|-----------------------|---|------------------------------| +| FOR (octet 1): | | | +| Bit 4 | | | +| 0 | | No Follow On Request pending | +| 1 | | Follow On Request pending | +| Attach type (octet 2) | | | +| Bits | | | +| 2 | 1 | | +| 0 | 0 | Normal attach procedure | +| 0 | 1 | Re-attach procedure | +| 1 | 0 | Reserved | +| 1 | 1 | Reserved | + +## 10.5.4 Call control information elements + +Call Control Information Elements are defined in GSM 04.08. The few exceptions for CTS specific procedures are defined in the following subclauses. + +### 10.5.4.1 Called party BCD number + +The called party BCD number information element is modified in order to support the CTS internal call procedure. See table 10.22/GSM 04.56. + +**Table 10.22/GSM 04.56: Called party BCD number** + +| | | | | | +|------------------------------------------------------------------|---|---|---|-----------------------------| +| Numbering plan identification (octet 3) | | | | | +| Number plan (applies for type of number = 000, 001, 010 and 100) | | | | | +| Bits | | | | | +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | see GSM 04.08 | +| 0 | 0 | 0 | 1 | see GSM 04.08 | +| 0 | 0 | 1 | 1 | see GSM 04.08 | +| 0 | 1 | 0 | 0 | see GSM 04.08 | +| 1 | 0 | 0 | 0 | see GSM 04.08 | +| 1 | 0 | 0 | 1 | see GSM 04.08 | +| 1 | 0 | 1 | 1 | CTS internal numbering plan | +| 1 | 1 | 1 | 1 | see GSM 04.08 | +| All other values are reserved. | | | | | + +### 10.5.4.2 Calling party BCD number + +The calling party BCD number information element is modified in order to support the CTS internal call procedure. See table 10.23/GSM 04.56. + +**Table 10.23/GSM 04.56: Calling party BCD number** + +| | | | | | +|------------------------------------------------------------------|---|---|---|-----------------------------| +| Numbering plan identification (octet 3) | | | | | +| Number plan (applies for type of number = 000, 001, 010 and 100) | | | | | +| Bits | | | | | +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | see GSM 04.08 | +| 0 | 0 | 0 | 1 | see GSM 04.08 | +| 0 | 0 | 1 | 1 | see GSM 04.08 | +| 0 | 1 | 0 | 0 | see GSM 04.08 | +| 1 | 0 | 0 | 0 | see GSM 04.08 | +| 1 | 0 | 0 | 1 | see GSM 04.08 | +| 1 | 0 | 1 | 1 | CTS internal numbering plan | +| 1 | 1 | 1 | 1 | see GSM 04.08 | +| All other values are reserved. | | | | | + +### 10.5.4.3 Keypad facility + +The purpose of the keypad facility information element is to convey IA5 characters, e.g. entered by means of a terminal keypad. A specific character is defined for CTS to transmit the hook flash request. This character is not used in the standard IA5 sense. + +The keypad facility information element is coded as shown in figure 10.22/GSM 04.56 and table 10.24/GSM 04.56. + +The keypad facility is a type 3 information element with 2 octets length. + +![](0779125369ae9c0108101b54fe2428bf_img.jpg) + +| | | | | | | | | | | | +|--|---------------------|------------------------------------|---|---|---|---|---|---|---------|---------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| | Keypad facility IEI | | | | | | | | octet 1 | | +| | Spare | Keypad information (IA5 character) | | | | | | | | octet 2 | +| | 0 | | | | | | | | | | + +**Figure 10.22/GSM 04.56: Keypad facility information element** + +NOTE: In CTS this information element is only used to transfer one DTMF digit (0, 1, ..., 9, A, B, C, D, \*, #) or a hook flash request as one IA5 character. + +**Table 10.24/GSM 04.56: Keypad information** + +| | | +|--------------------------------------------------------------------------------------------------|----------------------------| +| Keypad information is encoded as described in ITU-T T.50/ISO 646 except for the following value: | | +| Bits | | +| 7 6 5 4 3 2 1 | | +| 0 0 1 0 1 0 1 | hook flash (registry call) | + +## 11 List of system parameters + +The description of timers in the following table should be considered a brief summary. The precise details are found in clauses 3 to 6, which should be considered the definitive descriptions. + +### 11.1 Timers and counters for radio resource management + +#### 11.1.1 Timers on the MS side + +TC3150 This timer is started after sending the maximum allowed CTS ACCESS REQUEST message during an immediate assignment procedure. Its value is 5 s. + +TC3151 This timer is used to delay the channel deactivation (see GSM 04.08 11.1.1 T3110). + +## 11.1.2 Timers on the CTS-FP side + +- TC3101 This timer is started when the CTS-FP send a CTS PAGING REQUEST(CTSMSI, AliveCheck flag) for an Alive check procedure, and stopped when receiving a valid CTS ACCESS REQUEST. Its value is manufacturer dependent. +- TC3102 Hunting maximal duration timer. Its value is manufacturer dependent, but should be less than 120 s. +- TC3103 This timer is started when a channel is allocated with a CTS IMMEDIATE ASSIGN message. It is stopped when the CTS-MS has correctly seized the channels. Its value is manufacturer dependent, but should be greater than 1 s. +- TC3104 This timer is started when the CTS-FP has sent a CTS PAGING REQUEST message and is stopped when the CTS-FP has received the CTS PAGING RESPONSE. Its value is manufacturer dependent. +- TC3105 This timer is started when the CTS-FP has sent a CTS INTRACELL HANDOVER COMMAND message and is stopped when the CTS-MS has correctly seized the new channel. Its value is manufacturer dependent. +- TC3106 See GSM 04.08 11.1.2 T3109 +- TC3107 See GSM 04.08 11.1.2 T3111 + +## 11.1.3 Other parameters + +- MCTS The maximum number of retransmission for the CTS ACCESS REQUEST message. Its value is 7. + +# 11.2 Timers of mobility management + +## 11.2.1 Timers on the MS side + +- TC3250 This timer is started when the mobile station has sent a CTS ATTACH REQUEST message and it is normally stopped when the mobile station receives a CTS ATTACH COMPLETE message or a CTS ATTACH REJECT message. At its expiry, the mobile station shall start TC3251. Its value is 20 s. +- TC3251 This timer is started when the timer TC3250 expires. Its value is 5 minutes. +- TC3252 This timer is started when the mobile station enters the CTS MM IDLE state and it is normally stopped when the mobile station leaves this state. At its expiry, the mobile station shall start the CTS re-attach procedure. Its value is provided by the fixed part during the CTS attach procedure and is greater than $TC3201 + NC300 * TC3101$ and should be less than $TC3201 + 2 * NC300 * TC3101$ . +- TC3253 This timer is started when the mobile station has sent a CTS DETACH INDICATION message and it is normally stopped when the RR connection is released. Its value is 5 s. +- TC3254 This timer is started when the mobile station has sent a CTS ENROLMENT REQUEST message and it is normally stopped when a CTS ENROLMENT ACCEPT message is received. Its value is 45 s. +- TC3255 This timer is started when the mobile station has sent a CTS RE-ATTACH REQUEST message and it is normally stopped when a CTS RE-ATTACH RESPONSE message is received. Its value is 5 s. +- TC3256 This timer is started when the mobile station has received a CTS ATTACH REJECT with a fixed part identity. At its expiry, the mobile station may re-attempt an attachment on a fixed part having the same FPBI. Its value is 10 minutes. + +- TC3257 This timer is started when the mobile station has received a CTS ATTACH REJECT from the expected fixed part with a cause different of NOT ENROLLED. At its expiry, the mobile station may re-attempt an attachment on that fixed part. +Its value is 5 minutes. +- TC3260 This timer is started when the mobile station has sent a CTS MS AUTHENTICATION RESPONSE message and it is normally stopped when a CTS FP AUTHENTICATION RESPONSE message is received. +Its value is 5 s. + +## 11.2.2 Timers on the CTS-FP side + +- TC3201 This timer is started when the fixed part enters the MM IDLE state and it is normally stopped when the fixed part leaves the MM IDLE state. At its expiry, the MM sublayer shall trigger the alive check procedure. +Its value is manufacturer dependent, but greater than 15 s. +- TC3202 This timer is started when the fixed part has sent a CTSMSI UPDATE COMMAND message and it is normally stopped when a CTSMSI UPDATE COMPLETE message is received. +Its value is 5 s. +- TC3211 This timer is started when the fixed part has sent a CTS MS AUTHENTICATION REQUEST message and it is normally stopped when a CTS MS AUTHENTICATION RESPONSE message is received. +Its value is 5 s. + +## 11.2.3 Other parameters + +- NC320 The maximum number of alive check procedures allowed before changing the CTSMSI. Its value is manufacturer dependent. + +## 11.3 Timers of circuit-switched call control + +See GSM 04.08, subclause 11.3 + +## Annex A (informative): Default Codings of Information Elements + +The information in this annex does NOT define the value of any IEI for any particular message. This annex exists to aid the design of new messages. + +### A.1 Common information elements + +For the common information elements types listed below, the default coding of information element identifier bits is summarised in table A.1/GSM 04.56. + +**Table A.1/GSM 04.56: Default information element identifier coding +for common information elements** + +| 8 7 6 5 4 3 2 1 | Reference subclause | +|------------------------------------------|---------------------| +| 1 : : : - - - - Type 1 info elements | | +| 1 1 1 - - - - Reserved | | +| 0 : : : : : : Type 3 & 4 info elements | | +| 0 0 1 0 1 1 1 Mobile Identity | 10.5.1.1 | +| 0 1 0 0 0 0 0 Mobile Station classmark 3 | GSM 04.08 10.5.1.3 | +| All other values are reserved | | + +### A.2 Radio Resource management information elements + +For the Radio Resource management information elements listed below, the default coding of the information element identifier bits is summarised in table A.2/GSM 04.56. + +**Table A.2/GSM 04.56: Default information element identifier coding +for Radio Resource management information elements** + +| 8 7 6 5 4 3 2 1 | Reference subclause | +|--------------------------------------------|---------------------| +| 1 : : : - - - - Type 1 info elements | | +| 0 0 1 - - - - Cipher Mode Setting | | +| 0 1 0 - - - - Cipher Response | | +| 0 1 1 - - - - Note | | +| 1 0 1 - - - - Synchronisation Indication | | +| 1 1 0 - - - - Channel Needed | | +| 0 : : : : : : Type 3 & 4 info elements | | +| 0 0 0 0 0 1 0 Frequency Short List | | +| 0 0 0 0 1 0 1 Frequency List | | +| 1 1 0 0 0 0 1 Note | | +| 1 1 0 0 0 1 0 Cell Channel Description | | +| 1 1 0 0 0 1 1 Channel Mode | | +| 1 1 0 0 1 0 0 Channel Description | | +| 1 1 0 0 1 1 0 Channel Mode 2 | | +| 1 1 0 1 0 0 0 Note | | +| 1 1 0 1 0 0 1 Frequency Channel Sequence | | +| 1 1 0 1 0 1 0 Note | | +| 1 1 0 1 0 1 1 Note | | +| 1 1 1 0 0 0 1 Note | | +| 1 1 1 0 0 1 0 Mobile Allocation | | +| 1 1 1 0 0 1 1 BA range | | +| 1 1 1 0 1 0 0 CTS selection parameters | | +| 1 1 1 0 1 0 1 CTS RR parameters | | +| 1 1 1 0 1 1 0 Timeslot shifting parameters | | + +## A.3 Mobility management information elements + +For the mobility management information elements listed below, the default coding of the information element identifier bits is summarised in table A.3/GSM 04.56. + +**Table A.3/GSM 04.56: Default information element identifier coding +for mobility management information elements** + +| 8 7 6 5 4 3 2 1 | Reference subclause | +|---------------------------------------------|---------------------| +| 1 : : : - - - - Type 1 info elements | | +| 0 0 1 - - - - | | +| 0 1 0 - - - - | | +| 0 1 1 - - - - | | +| 1 0 1 - - - - | | +| 1 1 0 - - - - | | +| 1 0 1 0 - - - - Type 2 info elements | | +| 0 0 0 1 Follow-on proceed | GSM 04.08 10.5.3.7 | +| 0 0 1 0 Following attach request | 10.5.3.8 | +| 0 : : : : : : Type 3 & 4 info elements | | +| 0 0 0 0 0 0 1 CTS mobile group list | | +| 0 0 0 0 0 1 0 Access right identity | 10.5.3.7 | +| 0 0 0 0 0 1 1 Authentication parameter RIMS | 10.5.3.9 | +| 0 0 0 0 1 0 0 Authentication parameter RIFP | 10.5.3.1 | +| | 10.5.3.2 | + +--- + +## A.4 Call control information elements + +For the call control information elements listed below, the default coding of the information element identifiers is defined in table A.4/GSM 04. 08. + +## Annex B (informative): Change history + +| CN# | SPEC | CR | PHASE | VERS | NEW_VERS | SUBJECT | +|-------|--------|----|-------|--------|----------|---------------------------------------------------------------------------------------------------| +| S31 | | | | 7.1.0 | 8.0.0 | Specification release upgrade for R1999/ V8.0.0 | +| | | | | 8.0.0 | 8.0.1 | Version update to 8.0.1 for Publication | +| CN#11 | 44.056 | | Rel-4 | 8.0.1 | 4.0.0 | Release 4 after CN#11 | +| NP-16 | 44.056 | | Rel-5 | 4.0.0 | 5.0.0 | Plenary decision to make this TS also for Rel-5.
ETSI/MCC additionally made editorial cleanup. | +| NP-26 | 44.056 | | Rel-6 | 5.0.0 | 6.0.0 | Plenary decision to make this TS also for Rel-6. | +| | | | | 6.0.0 | 7.0.0 | Plenary decision to make this TS also for Rel-7. | +| | | | | 7.0.0 | 8.0.0 | Plenary decision to make this TS also for Rel-8 | +| CT-46 | | | | 8.0.0 | 9.0.0 | Plenary decision to make this TS also for Rel-9 | +| CT-51 | | | | 9.0.0 | 10.0.0 | Plenary decision to make this TS also for Rel-10 | +| CT-57 | | | | 10.0.0 | 11.0.0 | Plenary decision to make this TS also for Rel-11 | +| | | | | 11.0.0 | 11.0.1 | Deleted unexpected annex L | +| CT-65 | | | | 11.0.1 | 12.0.0 | Plenary decision to make this TS also for Rel-12 | +| CT-70 | | | | 12.0.0 | 13.0.0 | Upgrade to Rel-13 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | SA#88e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44057/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-16/44_series/44057/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b708d494fbeb90ee8803fca083efdf1fc3a1d82c --- /dev/null +++ b/marked/Rel-16/44_series/44057/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:214cf58051d4f6f768b65a867c3d1efb4c90c067a27ce7c9ad11c49e9ba4a6a1 +size 20698 diff --git a/marked/Rel-16/44_series/44057/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/44_series/44057/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..359e3f5bd055acd8b874e1f736f8c2bb5bdfd604 --- /dev/null +++ b/marked/Rel-16/44_series/44057/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd20fb56f2f65f6b0a24924f49c4337c78fb4e0bb846cdbb82c1fc71313d048b +size 22493 diff --git a/marked/Rel-16/44_series/44057/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/44_series/44057/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14f6e86833dc3111e44c938a10b3a80a20e7d368 --- /dev/null +++ b/marked/Rel-16/44_series/44057/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3d8fd012544d685f6fcd1c9fa4e400d07f8936fb3591049e0b15866d6693bae +size 52373 diff --git a/marked/Rel-16/44_series/44057/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-16/44_series/44057/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11aa26bcba690c8704bb6c5b935ee4803a0107a6 --- /dev/null +++ b/marked/Rel-16/44_series/44057/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49d35bc97701097eb2df804a6e97a414008db6982563f331d791ef5857c46471 +size 66418 diff --git a/marked/Rel-16/44_series/44057/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-16/44_series/44057/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..657ece1001df70940b217c0a26d03f6c2e2af4d9 --- /dev/null +++ b/marked/Rel-16/44_series/44057/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15f8c722503b87a70c2a6544c41de4f0688037d7036d1465620769270090b9c9 +size 26224 diff --git a/marked/Rel-16/44_series/44057/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/marked/Rel-16/44_series/44057/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5326b2f2063de48bfc0c4f89cefb8e0e5222ec1c --- /dev/null +++ b/marked/Rel-16/44_series/44057/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c139f98fe898141d78ee0c5b6b9825a4ff41975fd79744fefea5c10483ff9e52 +size 43032 diff --git a/marked/Rel-16/44_series/44057/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/44_series/44057/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4d2f0a1d27ee5c4580069e6b81b7076bd76c151 --- /dev/null +++ b/marked/Rel-16/44_series/44057/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c33ccafb6b75733a78781548e5ccdd784061b10cc188b968768ed8b9b6ec2527 +size 68201 diff --git a/marked/Rel-16/44_series/44057/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/marked/Rel-16/44_series/44057/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f8a7ad95aa1646711f847334b782d2e38a13428 --- /dev/null +++ b/marked/Rel-16/44_series/44057/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95777d4787ea9e313483475551d70a245188933c706a792ad6bf72f301bed369 +size 42650 diff --git a/marked/Rel-16/44_series/44057/5879500ca01e1a2521654beff6c289a4_img.jpg b/marked/Rel-16/44_series/44057/5879500ca01e1a2521654beff6c289a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29d0d1488ccfb46659cc4f10f65af2a295299b4e --- /dev/null +++ b/marked/Rel-16/44_series/44057/5879500ca01e1a2521654beff6c289a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b7888d5722fdccce8bb6102b17c549236cfdd62497c8bb1fde8c71eee93d218 +size 16413 diff --git a/marked/Rel-16/44_series/44057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/44_series/44057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f25c4afc05ab26aeee335ac26bcccd30f1dd2eed --- /dev/null +++ b/marked/Rel-16/44_series/44057/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97aba25808ed69b5b9daae3c840e739d92b30f4fc33afb92050cddc182b1fa6e +size 50358 diff --git a/marked/Rel-16/44_series/44057/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/44_series/44057/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab5c045a37b84bdde93716c7d5d8c67a5680f63a --- /dev/null +++ b/marked/Rel-16/44_series/44057/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6f59ad9fc82fb692a259a4a098aeccf124147e9b9482c0797df74104d9a7b0c +size 22318 diff --git a/marked/Rel-16/44_series/44057/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-16/44_series/44057/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b546aec88f574baba8bc5ac36f62fcefcec941d9 --- /dev/null +++ b/marked/Rel-16/44_series/44057/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb3ef737f55335fc126dd748e3fac8e6b4bfc9046cea84f2b0b8e18d4970e5d7 +size 34004 diff --git a/marked/Rel-16/44_series/44057/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/44_series/44057/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..795f8171338c80b201d3043676b685d88c0e051a --- /dev/null +++ b/marked/Rel-16/44_series/44057/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:822cc76d11790a8ecd7d315830bff4d27838b7d7f48c492ff3be2d8361f60af4 +size 87048 diff --git a/marked/Rel-16/44_series/44057/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/44_series/44057/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..994d858b12a75a18f790d8329b22d0dad67ae2a1 --- /dev/null +++ b/marked/Rel-16/44_series/44057/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58c2ac0038a331a28dc3ff944198715194aa5fcca027cd79af01376f8a65290f +size 32108 diff --git a/marked/Rel-16/44_series/44057/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/44_series/44057/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfcf92352352298bcb9a47a81acf7ddc10233312 --- /dev/null +++ b/marked/Rel-16/44_series/44057/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f14494d25e5bf2a29037ad3a605bc2654a56e35aed67010cbe1cb05692311768 +size 168928 diff --git a/marked/Rel-16/44_series/44057/b54ce9bffd341cd643e196d5f4538829_img.jpg b/marked/Rel-16/44_series/44057/b54ce9bffd341cd643e196d5f4538829_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06098b28e6dddb02316bb6af2b1ca50611cc117e --- /dev/null +++ b/marked/Rel-16/44_series/44057/b54ce9bffd341cd643e196d5f4538829_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a57291095e5d41600d8146d48ba62cb13083cfb5d5b5cb84c62b4af4cb2bc66 +size 22714 diff --git a/marked/Rel-16/44_series/44057/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg b/marked/Rel-16/44_series/44057/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d164a4de2ae891fe78302c0f21cdad18bd59f221 --- /dev/null +++ b/marked/Rel-16/44_series/44057/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:092ca4b565a213907b49ffe93fa034c7cf1bfcaab3934738ea71a0873329f448 +size 30715 diff --git a/marked/Rel-16/44_series/44057/raw.md b/marked/Rel-16/44_series/44057/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..de9202a49c20468f7301a370bf5bdd20d7a28793 --- /dev/null +++ b/marked/Rel-16/44_series/44057/raw.md @@ -0,0 +1,1891 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 1.1 Scope of the Technical Specification ..... | 7 | +| 1.2 Application to the interface structures ..... | 7 | +| 1.3 Structure of layer 3 procedures ..... | 7 | +| 1.4 Test procedures ..... | 7 | +| 1.5 Transmission layer ..... | 7 | +| 1.6 Overview of control procedures ..... | 7 | +| 1.6.1 List of procedures ..... | 7 | +| 1.7 Applicability of implementations..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, abbreviations and Random values..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Abbreviations ..... | 12 | +| 3.3 Random values ..... | 12 | +| 4 CTS supervising management procedures..... | 12 | +| 4.1 General ..... | 12 | +| 4.2 CTS-SPM procedures..... | 13 | +| 4.3 CTS-SPM states ..... | 13 | +| 4.3.1 CTS-SPM states at the Fixed Part ..... | 13 | +| 4.3.2 CTS-SPM states at the Service Node ..... | 13 | +| 4.4 CTS-SPM common procedures..... | 14 | +| 4.4.1 CTS-FP initialisation procedure ..... | 14 | +| 4.4.1.1 CTS-FP initialisation initiation..... | 14 | +| 4.4.1.2 CTS-FP initialisation completion ..... | 14 | +| 4.4.2 CTS enrolment procedure..... | 14 | +| 4.4.2.1 CTS-SPM enrolment initiation ..... | 15 | +| 4.4.2.2 CTS enrolment completion..... | 15 | +| 4.4.3 CTS operation data update procedure ..... | 15 | +| 4.4.3.1 CTS operation data update initiation ..... | 15 | +| 4.4.3.2 CTS operation data update completion..... | 15 | +| 4.4.4 CTS Information data request procedure..... | 15 | +| 4.4.4.1 CTS Information data request..... | 16 | +| 4.4.4.2 CTS Information data response ..... | 16 | +| 4.4.5 CTS-FP de-initialisation procedure..... | 16 | +| 4.4.5.1 CTS-FP de-initialisation initiation..... | 16 | +| 4.4.5.2 CTS de-initialisation completion..... | 16 | +| 4.4.6 CTS-SPM de-enrolment procedure ..... | 16 | +| 4.4.6.1 CTS-SPM de-enrolment initiated by the fixed part ..... | 16 | +| 4.4.6.2 CTS-SPM de-enrolment initiated by the service node ..... | 16 | +| 4.4.7 CTS FP authentication procedure..... | 16 | +| 4.4.7.1 CTS FP authentication request ..... | 17 | +| 4.4.7.2 CTS FP authentication response ..... | 17 | +| 4.4.8 CTS MS authentication procedure ..... | 17 | +| 4.4.8.1 CTS MS authentication request..... | 17 | +| 4.4.8.2 CTS MS authentication response..... | 17 | +| 5 Examples of structured procedures ..... | 17 | +| 5.1 CTS-FP Initialisation..... | 17 | +| 5.2 CTS-SPM Enrolment ..... | 18 | +| 5.3 Operation data update..... | 19 | +| 5.4 Information request ..... | 19 | +| 5.5 CTS-FP De-initialisation..... | 19 | +| 5.6 CTS-SPM De-enrolment..... | 20 | +| 5.6.1 CTS-SPM De-enrolment initiated by the fixed part..... | 20 | +| 5.6.2 CTS-SPM De-enrolment initiated by the service node ..... | 20 | + +| | | | +|------------------------|--------------------------------------------------------------------|----| +| 6 | Handling of unknown, unforeseen, and erroneous protocol data ..... | 21 | +| 7 | Message functional definitions and contents ..... | 21 | +| 7.1 | Messages for CTS Supervising management..... | 22 | +| 7.1.1 | CTS-FP initialisation request ..... | 22 | +| 7.1.2 | CTS-FP initialisation accept..... | 23 | +| 7.1.3 | CTS-FP initialisation complete ..... | 23 | +| 7.1.4 | CTS-FP initialisation reject ..... | 24 | +| 7.1.5 | CTS-FP de-initialisation request ..... | 24 | +| 7.1.6 | CTS-FP de-initialisation complete ..... | 24 | +| 7.1.7 | CTS-FP de-initialisation reject ..... | 25 | +| 7.1.8 | CTS enrolment request..... | 25 | +| 7.1.9 | CTS-SPM enrolment accept ..... | 26 | +| 7.1.10 | CTS-SPM enrolment reject ..... | 26 | +| 7.1.11 | CTS-SPM de-enrolment indication ..... | 26 | +| 7.1.12 | CTS-SPM de-enrolment request..... | 27 | +| 7.1.13 | CTS-SPM de-enrolment complete ..... | 27 | +| 7.1.14 | CTS-SPM de-enrolment reject ..... | 28 | +| 7.1.15 | CTS operation data request ..... | 28 | +| 7.1.16 | CTS operation data deliver..... | 28 | +| 7.1.17 | CTS operation data accept..... | 29 | +| 7.1.18 | CTS operation data reject..... | 29 | +| 7.1.19 | CTS information data request..... | 30 | +| 7.1.20 | CTS information data response ..... | 30 | +| 7.1.21 | CTS FP authentication request..... | 31 | +| 7.1.22 | CTS FP authentication response..... | 31 | +| 7.1.23 | CTS FP authentication reject..... | 31 | +| 7.1.24 | CTS MS authentication request..... | 32 | +| 7.1.25 | CTS MS authentication response ..... | 32 | +| 7.1.26 | CTS MS authentication reject ..... | 33 | +| 7.1.27 | CTS SN signing mode command ..... | 33 | +| 8 | General message format and information elements coding..... | 33 | +| 8.1 | Overview ..... | 33 | +| 8.2 | Protocol Discriminator ..... | 33 | +| 8.3 | Skip indicator and transaction identifier ..... | 34 | +| 8.3.1 | Skip indicator..... | 34 | +| 8.3.2 | Transaction identifier..... | 34 | +| 8.4 | Message Type..... | 34 | +| 8.4.1 | Supervising management information elements..... | 35 | +| 8.4.1.1 | Authentication parameter RAND1 ..... | 35 | +| 8.4.1.2 | Authentication parameter RAND2 ..... | 35 | +| 8.4.1.3 | Authentication parameter SRES ..... | 36 | +| 8.4.1.4 | Fixed part Identity..... | 36 | +| 8.4.1.5 | Mobile station Identity..... | 37 | +| 8.4.1.6 | Fixed Part Classmark ..... | 38 | +| 8.4.1.7 | Radio frequency control Parameters..... | 38 | +| 8.4.1.8 | Radio link control Parameters..... | 41 | +| 8.4.1.9 | Generic Frequency List..... | 42 | +| 8.4.1.10 | Cell Identity List ..... | 42 | +| 8.4.1.11 | Application time ..... | 44 | +| 8.4.1.12 | Enrolment time ..... | 44 | +| 8.4.1.13 | Validity period ..... | 45 | +| 8.4.1.14 | Recall period..... | 45 | +| 9 | List of system parameters ..... | 46 | +| 9.1 | Timers and counters for radio resource management ..... | 46 | +| 9.1.1 | Timers on the SN side ..... | 46 | +| 9.1.2 | Timers on the CTS-FP side ..... | 46 | +| Annex A (informative): | Change Request History..... | 47 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the procedures used at the CTS system interface with the supervision part i.e. the interface between the CTS-FP and the CTS-SN. + +Only CTS regular supervising procedures are described; FMC management is not intended to be standardised. + +The present document does not specify the transmission layer but only the layer 3. + +When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document. + +The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07. + +## 1.1 Scope of the Technical Specification + +The procedures currently described in the present document are for supervising management over the CTS-FP/CTS-SN interface. + +## 1.2 Application to the interface structures + +The layer 3 procedures apply to the interface structures defined in GSM 04.03. GSM 04.07 gives the general description of layer 3 including procedures, messages format and error handling. + +## 1.3 Structure of layer 3 procedures + +A building block method is used to describe the layer 3 procedures. + +The basic building blocks are "elementary procedures" provided by the protocol control entities. + +Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences. + +## 1.4 Test procedures + +Test procedures of the CTS / Fixed Network interface signalling are described in the GSM 11.56 series. + +## 1.5 Transmission layer + +The transmission layer is out of scope of the present document. One implementation could be a V.22bis modem with an HDLC based protocol. + +## 1.6 Overview of control procedures + +### 1.6.1 List of procedures + +The following procedures are specified in the present document: + +- Clause 4 specifies elementary procedures for CTS Supervising Management: + - CTS-FP initialisation procedure (subclause 4.4.1); + - CTS-FP de-initialisation procedure (subclause 4.4.5); + - CTS enrolment procedure (subclause 4.4.2); + - CTS de-enrolment procedure (subclause 4.4.6); + - CTS operation data update procedure (subclause 4.4.3); + - CTS information request procedure (subclause 4.4.4); + +- CTS FP authentication procedure (subclause 4.4.7); +- CTS MS authentication procedure (subclause 4.4.8). + +The elementary procedures can be combined to form structured procedures. Examples of such structured procedures are given in clause 5. This part of the Technical Specification is only provided for guidance to assist implementations. + +Clause 6 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol. + +## 1.7 Applicability of implementations + +The applicability of procedures of the present document for the fixed part is dependent on the services and functions which are to be supported by a fixed part. + +# --- 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.02: "Digital cellular telecommunications system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". +- [2] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [3] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". +- [4] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". +- [5] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects". +- [6] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility". +- [7] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber Identity Modules (SIM); Functional characteristics". +- [8] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications". +- [9] GSM 03.01: "Digital cellular telecommunications system (Phase 2+); Network functions". +- [10] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". +- [11] GSM 03.13: "Digital cellular telecommunications system (Phase 2+); Discontinuous Reception (DRX) in the GSM system". +- [12] GSM 03.14: "Digital cellular telecommunications system (Phase 2+); Support of Dual Tone Multi-Frequency signalling (DTMF) via the GSM system". +- [13] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions". + +- [14] GSM 03.22: "Digital cellular telecommunications system (Phase 2+); Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [15] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". +- [16] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". +- [17] GSM 04.04: "Digital cellular telecommunications system (Phase 2+); Layer 1; General requirements". +- [18] GSM 04.05: "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer; General aspects". +- [19] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". +- [20] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". +- [21] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". +- [22] GSM 04.11: "Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [23] GSM 04.12: "Digital cellular telecommunications system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [24] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". +- [25] GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services; Stage 3". +- [26] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services; Stage 3". +- [27] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3". +- [28] GSM 04.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services; Stage 3". +- [29] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services; Stage 3". +- [30] GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services; Stage 3". +- [31] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services; Stage 3". +- [32] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". +- [33] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [34] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". +- [35] GSM 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization". + +- [36] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [37] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". +- [38] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [39] GSM 11.10: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) conformance specification". +- [40] GSM 11.21: "Digital cellular telecommunications system (Phase 2+); Base Station System (BSS) equipment specification". +- [41] ISO/IEC 646 (1991): "Information technology - ISO 7-bit coded character set for information interchange". +- [42] ISO/IEC 6429: "Information technology - Control functions for coded character sets". +- [43] ISO 8348 (1987) (Addendum 2): "Information processing systems - Data communications - Network service definition". +- [44] ITU-T Recommendation E.163: "Numbering plan for the international telephone service". +- [45] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [46] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users". +- [47] ITU-T Recommendation F.69 (1993): "The international telex service - Service and operational provisions of telex destination codes and telex network identification codes". +- [48] ITU-T Recommendation I.330: "ISDN numbering and addressing principles". +- [49] ITU-T Recommendation I.440 (1989): "ISDN user-network interface data link layer - General aspects". +- [50] ITU-T Recommendation I.450 (1989): "ISDN user-network interface layer 3 - General aspects". +- [51] ITU-T Recommendation I.500 (1993): "General structure of the ISDN interworking recommendations". +- [52] ITU-T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange". +- [53] ITU-T Recommendation Q.931: ISDN user-network interface layer 3 specification for basic control". +- [54] ITU-T Recommendation V.21: "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [55] ITU-T Recommendation V.22: "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [56] ITU-T Recommendation V.22bis: "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [57] ITU-T Recommendation V.23: "600/1200-baud modem standardized for use in the general switched telephone network". + +- [58] ITU-T Recommendation V.26ter: "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [59] ITU-T Recommendation V.32: "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits". +- [60] ITU-T Recommendation V.110: "Support by an ISDN of data terminal equipments with V-Series type interfaces". +- [61] ITU-T Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". +- [62] ITU-T Recommendation X.21: "Interface between Data Terminal Equipment and Data Circuit-terminating Equipment for synchronous operation on public data networks". +- [63] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". +- [64] ITU-T Recommendation X.28: "DTE/DCE interface for a start-stop mode Data Terminal Equipment accessing the Packet Assembly/Disassembly facility (PAD) in a public data network situated in the same country". +- [65] ITU-T Recommendation X.30: "Support of X.21, X.21 bis and X.20 bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN)". +- [66] ITU-T Recommendation X.31: "Support of packet mode terminal equipment by an ISDN". +- [67] ITU-T Recommendation X.32: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and accessing a packet-switched public data network through a public switched telephone network or an integrated services digital network or a circuit-switched public data network". +- [68] ITU-T Recommendation X.75 (1988): "Packet-switched signalling system between public networks providing data transmission services". +- [69] ITU-T Recommendation X.121: "International numbering plan for public data networks". +- [70] ETSI ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface layer 3; Specifications for basic call control". +- [71] ETSI ETS 300 102-2: "Integrated Services Digital Network (ISDN); User-network interface layer 3; Specifications for basic call control; Specification Description Language (SDL) diagrams". +- [72] ISO/IEC 10646: "Information technology - Universal Multiple-Octet Coded Character Set (UCS)". +- [73] GSM 02.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; Service description; Stage 1". +- [74] GSM 03.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; CTS Architecture Description; Stage 2". +- [75] GSM 03.52: "Digital cellular telecommunications system (Phase 2+); GSM-CTS; Overall description of the CTS radio interface; Stage 2". +- [76] Void. +- [77] GSM 04.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification". + +# --- 3 Definitions, abbreviations and Random values + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**initialised Fixed Part:** Fixed Part which have been supplied with the necessary data to provide CTS service on the CTS radio interface. The CTS-FP initialisation procedure is performed at the Fixed Part installation and can be performed whenever the Fixed Part have been de-initialised. + +**de-initialised Fixed Part:** Fixed Part which does not contain the required data to offer CTS service. A de-initialised Fixed Part cannot offer any service. + +**enrolled Mobile Station:** Mobile Station is said to be enrolled on a Fixed Part if it has exchanged some data with this Fixed Part enabling attachment (e.g. in order to perform outgoing calls). + +**de-enrolled Mobile Station:** Mobile Station that is no more known by the Fixed Part. + +**CTS radio interface:** Radio interface between the Mobile Station and the Fixed Part. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in GSM 01.04 apply. + +## 3.3 Random values + +In a number of places in the present document, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. + +It is required that there is a low probability that two equipments in the same conditions (including the case of two equipments of the same type from the same manufacturer) will choose or get the same value. + +# --- 4 CTS supervising management procedures + +## 4.1 General + +CTS supervising management procedures include the functions related to the management of the CTS system by the CTS operator. These functions are based on: + +- radio control: the control of the radio parameters used on the CTS radio interface; +- security control: including subscription checking, CTS authentication (the authentication of the CTS subscriber identity by the CTS Service Node and the authentication of the signature issued by the Service Node by the Fixed Part), GSM authentication (authentication of the Mobile Station by the GSM operator through the Service Node) and administrative data management. + +All the CTS supervising procedures can only be performed if a CTS-FP/CTS-SN connection has been established between the fixed part and the service node. If no CTS-FP/CTS-SN connection is currently established, the CTS supervising layer has to initiate such establishment. + +As in most cases, the CTS-SN has no means of addressing the CTS-FP, it is assumed that the CTS procedures can only be started by the fixed part. CTS procedures initiated by the Service Node follow a procedure started by the Fixed Part. + +## 4.2 CTS-SPM procedures + +All CTS-SPM procedures can only be initiated if a CTS-FP/CTS-SN connection is established. + +The procedures initiated by the Fixed Part are: + +- CTS-SPM initialisation procedure; + +- CTS-SPM enrolment procedure; +- CTS-SPM de-enrolment indication procedure; +- CTS-SPM operation data update procedure. + +The procedures initiated by the Service Node (following a procedure started by the Fixed Part) are: + +- CTS-SPM de-initialisation procedure; +- CTS-SPM de-enrolment procedure; +- CTS-SPM FP authentication procedure; +- CTS-SPM MS authentication procedure; +- CTS-SPM signature mode setting procedure; +- CTS-SPM operation data inform procedure. + +## 4.3 CTS-SPM states + +### 4.3.1 CTS-SPM states at the Fixed Part + +#### 1. IDLE + +The CTS-SPM state is not active. + +#### 2. WAIT FOR CTS-FP/CTS-SN CONNECTION + +The CTS-SPM has requested the establishment of a CTS-FP/CTS-SN connection. + +#### 3. CTS-SPM CONNECTION ACTIVE + +A CTS-SPM connection is active. Only one CTS-SPM connection can be active at a time. + +#### 4. CTS-SPM INITIALISATION INITIATED + +The CTS-FP initialisation procedure has been started at the Fixed Part. + +#### 5. CTS-SPM ENROLMENT INITIATED + +The enrolment procedure has been started at the Fixed Part. + +#### 6. CTS-SPM OPERATION DATA UPDATE INITIATED + +The operation data update procedure has been started at the Fixed Part. + +Only one CTS-SPM connection can be active at a time on the Fixed Part. Nevertheless, an active CTS-SPM connection does not preclude having active CTS-RR and CTS-MM active connection on the CTS radio interface. + +### 4.3.2 CTS-SPM states at the Service Node + +#### 1. CTS-SPM DE-INITIALISATION INITIATED + +The CTS-FP de-initialisation procedure has been started by the Service Node. + +#### 2. CTS-SPM DE-ENROLMENT INITIATED + +The de-enrolment procedure has been started by the Service Node. + +#### 3. CTS-SPM INFORMATION DATA INITIATED + +The information data request procedure has been started by the Service Node. + +#### 4. CTS-SPM FP AUTHENTICATION INITIATED + +The FP authentication procedure has been started by the Service Node. + +#### 5. CTS-SPM MS AUTHENTICATION INITIATED + +The MS authentication procedure has been started by the Service Node. + +## 4.4 CTS-SPM common procedures + +### 4.4.1 CTS-FP initialisation procedure + +The purpose of the CTS-FP initialisation procedure is to provide the fixed part with the necessary data to enable CTS service. + +The CTS-FP initialisation procedure is always initiated by the CTS-FP. + +#### 4.4.1.1 CTS-FP initialisation initiation + +The fixed part initiates the CTS-FP initialisation procedure by sending a CTS-SPM INITIALISATION REQUEST message to the CTS-SN and starts the timer T\_init\_FP. + +The CTS-SPM INITIALISATION REQUEST message specifies the fixed part identity, and the classmark of the fixed part. + +The CTS-SPM INITIALISATION REQUEST message is sent on the CTS-FP/CTS-SN interface following a CTS-FP/CTS-SN connection initiated by the CTS fixed part. + +#### 4.4.1.2 CTS-FP initialisation completion + +If the CTS-FP initialisation can be performed, the service node shall send a CTS-SPM INITIALISATION ACCEPT to the fixed part. This message includes the necessary radio parameters to enable operation on the CTS interface. These data are associated to timers that are also sent in the message. The validity period (Tval) timer indicates the maximum duration where those data should be used. The recall period (Trecal) requires the fixed part to contact the service node on a regular basis. The recall period should enable the fixed part to update the necessary data before the validity period expires. If Tval and Trecal are not included in the CTS-SPM INITIALISATION ACCEPT message, their values are considered as being infinite. + +Upon reception of this message, the fixed part stops the timer T\_init\_FP. + +The service node shall send a CTS-SPM INITIALISATION REJECT if the rights are not verified. + +When, the fixed part has received and accepted the necessary data in order to operate, it sends a CTS-SPM INITIALISATION COMPLETE to the service node. + +### 4.4.2 CTS enrolment procedure + +The enrolment of a mobile station onto a fixed part is the procedure by which a mobile and a fixed part are made known to each other in order that the CTS service can be provided to the mobile station. This procedure can be performed under the control of the CTS operator depending on the information downloaded by the operator at subscription setting. The enrolment procedure performed locally between the mobile station and the fixed part is described in GSM 04.56. + +If required by the CTS operator, the additional CTS-SPM enrolment procedure should be performed. + +The CTS-SPM enrolment procedure is initiated by the fixed part following a successful first part local enrolment procedure. + +#### 4.4.2.1 CTS-SPM enrolment initiation + +The fixed part initiates the CTS-SPM enrolment procedure by sending the message CTS-SPM ENROLMENT REQUEST message and starting a timer T\_enrol\_FP. + +The CTS-SPM ENROLMENT REQUEST message specifies the fixed part identity and the mobile identity. + +#### 4.4.2.2 CTS enrolment completion + +If the service node agrees to enrol the mobile onto the fixed part, the service node sends a CTS-SPM ENROLMENT ACCEPT message. This message may include an enrolment validity time; if this information element is not included in the message, the enrolment validity period is considered as being infinite. + +Similarly, the service node shall send a CTS-SPM ENROLMENT REJECT if the request cannot be granted with the reject cause. Upon reception of CTS-SPM ENROLMENT ACCEPT or CTS-SPM ENROLMENT REJECT message, the fixed part stops timer T\_enrol\_FP. + +### 4.4.3 CTS operation data update procedure + +The purpose of the CTS operation data update procedure is to provide the fixed part with the necessary data to operate. Before performing the operation data update procedure the fixed part has to be initialised. + +This procedure is launched by the fixed part at the expiry of timer Trecal. The duration of Trecal is defined by the service node during the CTS-SPM initialisation procedure. + +#### 4.4.3.1 CTS operation data update initiation + +The fixed part initiates the CTS operation data update procedure by sending the message CTS-SPM OPERATION DATA REQUEST message and starting timer T\_opdata\_FP. + +#### 4.4.3.2 CTS operation data update completion + +The service node sends the required data in a CTS-SPM OPERATION DATA DELIVER message. Upon reception of this message the fixed part stops timer T\_opdata\_FP. + +The sent operation data are associated to 2 timers. The validity period (Tval) timer indicates the maximum duration where those data should be used. The recall period (Trecal) requires the fixed part to contact the service node on a regular basis. The recall period should enable the fixed part to update the necessary data before the validity period expires. If Tval and Trecal are not included in the CTS-SPM OPERATION DATA DELIVER message, there value are considered as being infinite. + +If the data are accepted by the fixed part, the fixed part shall send a CTS-SPM OPERATION DATA ACCEPT to the service node and shall launch the timers Tval and Trecal related to the corresponding data, if the application time Tapplic information element is set to "apply immediately". Otherwise, the fixed part stores the new operation data and starts timer Tapplic. At Tapplic expiry, the fixed part applies the new operation data and starts the associated timers Tval and Trecal. + +Similarly, the fixed part shall send CTS-SPM OPERATION DATA REJECT if the data cannot be accepted (i.e. the fixed part did not succeed in authenticating the signature issued by the service node). + +### 4.4.4 CTS Information data request procedure + +In some cases the service node may require to be informed of the data used by fixed part. The CTS Information data procedure can be initiated during any procedure started by the fixed part (e.g. enrolment procedure, operation data update procedure). + +#### 4.4.4.1 CTS Information data request + +The service node initiates the CTS information data request procedure by sending a CTS-SPM INFORMATION DATA REQUEST message to the fixed part. + +Upon receipt of the CTS-SPM INFORMATION DATA REQUEST message the fixed part collects the required data. + +#### 4.4.4.2 CTS Information data response + +The fixed part sends a CTS-SPM INFORMATION DATA RESPONSE to the service node including these data. + +### 4.4.5 CTS-FP de-initialisation procedure + +The purpose of the CTS-FP de-initialisation procedure is to allow the CTS operator to de-initialise a given fixed part. As the fixed part has no means to address a given fixed part, this procedure follows another procedure initiated by the fixed part. + +#### 4.4.5.1 CTS-FP de-initialisation initiation + +The service node initiates the CTS-FP de-initialisation procedure by sending a CTS-SPM DE-INITIALISATION REQUEST message to the fixed part and starts the timer T\_deinit\_SN. Upon receipt of the CTS-SPM DE-INITIALISATION REQUEST message the fixed part stops operation. + +#### 4.4.5.2 CTS de-initialisation completion + +As a response to the message the fixed part sends a CTS-SPM DE-INITIALISATION COMPLETE message. + +If the fixed part does not accept the de-initialisation command (i.e. the fixed part did not succeed in authenticating the signature issued by the service node) it sends a CTS-SPM DE-INITIALISATION REJECT message to the service node. Upon reception of either CTS-SPM DE-INITIALISATION COMPLETE or CTS-SPM DE-INITIALISATION REJECT, the service node stops timer T\_deinit\_SN. + +### 4.4.6 CTS-SPM de-enrolment procedure + +The CTS-SPM de-enrolment of a mobile from a fixed part can be initiated either by the fixed part or by the service node. + +#### 4.4.6.1 CTS-SPM de-enrolment initiated by the fixed part + +If the CTS-SPM de-enrolment procedure is initiated by the fixed part, the fixed part informs the service node of the mobile de-enrolment if specified by the operator at subscription setting, by sending a CTS-SPM DE-ENROLMENT INDICATION. + +If the de-enrolment is initiated by the service node, the following procedure applies. + +#### 4.4.6.2 CTS-SPM de-enrolment initiated by the service node + +The service node initiates the CTS-SPM de-enrolment procedure by sending a CTS-SPM DE-ENROLMENT REQUEST command to the fixed part including the mobile identity. + +Upon reception of the de-enrolment message, the fixed part performs de-enrolment of the specified mobile and responds by sending a CTS-SPM DE-ENROLMENT COMPLETE. + +### 4.4.7 CTS FP authentication procedure + +The purpose of the fixed part authentication procedure is twofold: + +First to permit the network to check whether the identity provided by the fixed part is acceptable or not. + +Second to provide parameters enabling the service node and the fixed part to calculate the signature key. + +The cases where the authentication procedure should be used are defined in GSM 03.56. + +The fixed part authentication procedure is always initiated and controlled by the CTS operator. + +#### 4.4.7.1 CTS FP authentication request + +The service node initiates the CTS FP authentication procedure by sending a CTS-SPM FP AUTHENTICATION REQUEST message to the fixed part and starting timer T\_FPauth\_SN. + +Upon receipt of the CTS-SPM FP AUTHENTICATION REQUEST message the fixed part calculates the response (see GSM 03.20 annex E). + +#### 4.4.7.2 CTS FP authentication response + +The fixed part processes a challenge response and sends it to the service node in a CTS-SPM FP AUTHENTICATION RESPONSE message. Upon reception of this message, the service node stops timer T\_FPauth\_SN. + +If the FP authentication fails the service node replies with a CTS-SPM FP AUTHENTICATION REJECT message. + +### 4.4.8 CTS MS authentication procedure + +Mobile authentication can be performed if required by the CTS operator. The procedure is similar to the GSM authentication procedure and aims to authenticate the mobile subscriber identity (the ciphering key is not required as no encryption applies through the CTS-FP/CTS-SN interface). + +The mobile authentication procedure is always initiated and controlled by the service node. + +#### 4.4.8.1 CTS MS authentication request + +The service node initiates the mobile authentication procedure by sending a CTS-SPM MS AUTHENTICATION REQUEST message to the fixed part and starts timer T\_MSauth\_SN. The fixed part acts as a relay and sends that request message to the mobile station. + +#### 4.4.8.2 CTS MS authentication response + +When the challenge response is transmitted from the mobile to the fixed part in a procedure described in GSM 04.56, the fixed part sends it to the service node in a CTS-SPM MS AUTHENTICATION RESPONSE message. The service node stops timer T\_MSauth\_SN. + +If the authentication fails the service node replies with a CTS-SPM MS AUTHENTICATION REJECT message. + +# --- 5 Examples of structured procedures + +Clause 5 is informative. + +## 5.1 CTS-FP Initialisation + +The CTS-FP initialisation procedure is always initiated by the fixed part. + +![Sequence diagram for CTS-FP initialisation between Fixed Part and Service Node.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant FP as Fixed Part + participant SN as Service Node + Note right of SN: CTS-FP/CTS-SN connection + FP->>SN: CTS-SPM INITIALISATION REQUEST + Note right of SN: Service request + SN-->>FP: CTS-SPM FP AUTHENTICATION REQUEST + Note right of SN: FP authentication + FP-->>SN: CTS-SPM FP AUTHENTICATION RESPONSE + SN-->>FP: CTS-SPM INITIALISATION ACCEPT + SN-->>FP: CTS-SPM SN SIGNING MODE COMMAND + Note right of SN: Signature mode setting + FP->>SN: CTS-SPM OPERATION DATA REQUEST + Note right of SN: Data transmission + SN-->>FP: CTS-SPM OPERATION DATA DELIVER + FP->>SN: CTS-SPM INITIALISATION COMPLETE + +``` + +Sequence diagram for CTS-FP initialisation between Fixed Part and Service Node. + +Figure 5.1/GSM 04.xx: CTS-FP initialisation + +## 5.2 CTS-SPM Enrolment + +The CTS-SPM enrolment procedure is always initiated by the fixed part following an initiation by the mobile station. + +![Sequence diagram for CTS-SPM Enrolment between Fixed Part and Service Node.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +``` + +sequenceDiagram + participant FP as Fixed Part + participant SN as Service Node + Note right of SN: CTS-FP/CTS-SN connection + FP->>SN: CTS-SPM ENROLMENT REQUEST + Note right of SN: Service request + SN-->>FP: CTS-SPM FP AUTHENTICATION REQUEST + Note right of SN: FP authentication + FP-->>SN: CTS-SPM FP AUTHENTICATION RESPONSE + Note right of SN: MS authentication + FP-->>SN: CTS-SPM MS AUTHENTICATION REQUEST + SN-->>FP: CTS-SPM MS AUTHENTICATION RESPONSE + SN-->>FP: CTS-SPM ENROLMENT ACCEPT + +``` + +Sequence diagram for CTS-SPM Enrolment between Fixed Part and Service Node. + +Figure 5.2/GSM 04.xx: CTS-SPM Enrolment + +## 5.3 Operation data update + +The operation data update procedure is always initiated by the fixed part. + +![Sequence diagram for CTS operation data update between Fixed Part and Service Node.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant FP as Fixed Part + participant SN as Service Node + Note right of SN: CTS-FP/CTS-SN connection + Note right of SN: Service request + FP->>SN: CTS-SPM OPERATION DATA REQUEST + Note right of SN: FP authentication + SN-->>FP: CTS-SPM FP AUTHENTICATION REQUEST + FP-->>SN: CTS-SPM FP AUTHENTICATION RESPONSE + Note right of SN: Signature mode setting + SN-->>FP: CTS-SPM SN SIGNING MODE COMMAND + SN-->>FP: CTS-SPM OPERATION DATA DELIVER + FP-->>SN: CTS-SPM OPERATION DATA ACCEPT + +``` + +The diagram illustrates the CTS operation data update procedure. It begins with the Fixed Part (FP) sending a CTS-SPM OPERATION DATA REQUEST to the Service Node (SN). The SN responds with a CTS-SPM FP AUTHENTICATION REQUEST, which the FP answers with a CTS-SPM FP AUTHENTICATION RESPONSE. Next, the SN sends a CTS-SPM SN SIGNING MODE COMMAND to the FP, followed by a CTS-SPM OPERATION DATA DELIVER. Finally, the FP responds with a CTS-SPM OPERATION DATA ACCEPT. Annotations on the right side of the diagram identify the initial connection, the service request, FP authentication, and signature mode setting phases. + +Sequence diagram for CTS operation data update between Fixed Part and Service Node. + +Figure 5.3/GSM 04.xx: CTS operation data update + +## 5.4 Information request + +The information request procedure is always initiated by the service node (the CTS-FP/CTS-SN connection is initiated by the fixed part). + +![Sequence diagram for Information request procedure between Fixed Part and Service Node.](77464a47f104d0d647b2414591137b64_img.jpg) + +``` + +sequenceDiagram + participant FP as Fixed Part + participant SN as Service Node + Note right of SN: CTS-FP/CTS-SN connection + Note right of SN: Other procedure + Note right of SN: Information transmission + SN-->>FP: CTS-SPM INFORMATION DATA REQUEST + FP-->>SN: CTS-SPM INFORMATION DATA RESPONSE + +``` + +The diagram illustrates the Information request procedure. It starts with the Service Node (SN) sending a CTS-SPM INFORMATION DATA REQUEST to the Fixed Part (FP). The FP responds with a CTS-SPM INFORMATION DATA RESPONSE. Annotations on the right side of the diagram indicate the CTS-FP/CTS-SN connection, an 'Other procedure' phase, and the 'Information transmission' phase. + +Sequence diagram for Information request procedure between Fixed Part and Service Node. + +Figure 5.4/GSM 04.xx: Information request procedure + +## 5.5 CTS-FP De-initialisation + +The CTS-FP de-initialisation procedure is always initiated by the service node (the CTS-FP/CTS-SN connection is initiated by the fixed part). + +![Sequence diagram for CTS-SPM De-initialisation procedure](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +Fixed Part Service Node + +---+ +---+ + | |------------------------------------------| | CTS-FP/CTS-SN connection + +---+ +---+ + +---+ +---+ + | |------------------------------------------| | Other procedure + +---+ +---+ + +---+ +---+ + | |<-----------------------------------------| | CTS-SPM DE-INITIALISATION REQUEST + | |----------------------------------------->| | CTS-SPM DE-INITIALISATION COMPLETE + +---+ +---+ + +``` + +Sequence diagram illustrating the CTS-SPM De-initialisation procedure between a Fixed Part and a Service Node. + +- The Service Node sends a **CTS-SPM DE-INITIALISATION REQUEST** to the Fixed Part. +- The Fixed Part responds with a **CTS-SPM DE-INITIALISATION COMPLETE** message. + +Sequence diagram for CTS-SPM De-initialisation procedure + +**Figure 5.5/GSM 04.xx: CTS-FP De-initialisation procedure** + +## 5.6 CTS-SPM De-enrolment + +The de-enrolment procedure can be either initiated by the fixed part or by the service node. + +### 5.6.1 CTS-SPM De-enrolment initiated by the fixed part + +The de-enrolment indication is sent by the fixed part to the service node. + +![Sequence diagram for CTS-SPM De-enrolment indication](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +``` + +Fixed Part Service Node + +---+ +---+ + | |------------------------------------------| | CTS-FP/CTS-SN connection + +---+ +---+ + +---+ +---+ + | |----------------------------------------->| | CTS-SPM DE-ENROLMENT INDICATION + +---+ +---+ + +``` + +Sequence diagram illustrating the CTS-SPM De-enrolment indication initiated by the Fixed Part. + +- The Fixed Part sends a **CTS-SPM DE-ENROLMENT INDICATION** to the Service Node. + +Sequence diagram for CTS-SPM De-enrolment indication + +**Figure 5.6/GSM 04.xx: CTS-SPM De-enrolment indication** + +### 5.6.2 CTS-SPM De-enrolment initiated by the service node + +The de-enrolment request is sent by the service node. + +![Sequence diagram for CTS-SPM De-enrolment request](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +``` + +Fixed Part Service Node + +---+ +---+ + | |------------------------------------------| | CTS-FP/CTS-SN connection + +---+ +---+ + +---+ +---+ + | |------------------------------------------| | Other procedure + +---+ +---+ + +---+ +---+ + | |<-----------------------------------------| | CTS-SPM DE-ENROLMENT REQUEST + | |----------------------------------------->| | CTS-SPM DE-ENROLMENT COMPLETE + +---+ +---+ + +``` + +Sequence diagram illustrating the CTS-SPM De-enrolment request initiated by the Service Node. + +- The Service Node sends a **CTS-SPM DE-ENROLMENT REQUEST** to the Fixed Part. +- The Fixed Part responds with a **CTS-SPM DE-ENROLMENT COMPLETE** message. + +Sequence diagram for CTS-SPM De-enrolment request + +**Figure 5.7/GSM 04.xx: CTS-SPM De-enrolment request** + +# 6 Handling of unknown, unforeseen, and erroneous protocol data + +Please refer to clause 8 of GSM 04.08. + +# 7 Message functional definitions and contents + +This clause defines the structure of the messages of those layer 3 protocols defined in GSM 04.xx. These are standard L3 messages as defined in GSM 04.07. + +Each definition given in the present clause includes: + +- a) a brief description of the message direction and use, including whether the message has: + - 1) Local significance, i.e. relevant only on the originating or terminating access; + - 2) Access significance, i.e. relevant in the originating and terminating access, but not in the CTS-FP; + - 3) Dual significance, i.e. relevant in either the originating or terminating access and in the network; or + - 4) Global significance, i.e. relevant in the originating and terminating access and in the network. +- b) a table listing the information elements known in the message and their order of their appearance in the message. All information elements that may be repeated are explicitly indicated. ( V and LV formatted IEs, which compose the imperative part of the message, occur before T, TV, and TLV formatted IEs which compose the non-imperative part of the message, see GSM 04.07.) In a (maximal) sequence of consecutive information elements with half octet length, the first information element with half octet length occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements. + +For each information element the table indicates: + +- 1) the information element identifier, in hexadecimal notation, if the IE has format T, TV, or TLV. Usually, there is a default IEI for an information element type; default IEIs of different IE types of the same protocol are different. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-). + +NOTE: The same IEI may be used for different information element types in different messages of the same protocol. + +- 2) the name of the information element (which may give an idea of the semantics of the element). The name of the information element (usually written in italics) followed by "IE" or "information element" is used as reference to the information element within a message. + - 3) the name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced subclause of clause 8 of GSM 04.xx describing the value part of the information element. + - 4) the presence requirement indication (M, C, or O) for the IE as defined in GSM 04.07. + - 5) the format of the information element (T, V, TV, LV, TLV) as defined in GSM 04.07. + - 6) the length of the information element (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by link layer protocol, and in the case of the Facility IE by possible further conditions specified in GSM 04.10. This indication is non-normative. +- c) subclauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant message which together with other conditions specified in GSM 04.xx define when the information elements shall be included or not, what non-presence of such IEs means, and - for IEs with presence requirement C - the static conditions for presence and/or non-presence of the IEs (see GSM 04.07). + +## 7.1 Messages for CTS Supervising management + +Table 7.1/GSM 04.xx summarises the messages for Supervising management. + +**Table 7.1/GSM 04.xx: Messages for CTS supervising management** + +| | | +|----------------------------------------|------------------| +| CTS-FP Initialisation messages: | Reference | +| CTS-SPM INITIALISATION REQUEST | 7.1.1 | +| CTS-SPM INITIALISATION ACCEPT | 7.1.2 | +| CTS-SPM INITIALISATION COMPLETE | 7.1.3 | +| CTS-SPM INITIALISATION REJECT | 7.1.4 | +| CTS-SPM DE-INITIALISATION REQUEST | 7.1.5 | +| CTS-SPM DE-INITIALISATION COMPLETE | 7.1.6 | +| CTS-SPM DE-INITIALISATION REJECT | 7.1.7 | +| Enrolment messages: | Reference | +| CTS-SPM ENROLMENT REQUEST | 7.1.8 | +| CTS-SPM ENROLMENT ACCEPT | 7.1.9 | +| CTS-SPM ENROLMENT REJECT | 7.1.10 | +| CTS-SPM DE-ENROLMENT INDICATION | 7.1.11 | +| CTS-SPM DE-ENROLMENT REQUEST | 7.1.12 | +| CTS-SPM DE-ENROLMENT COMPLETE | 7.1.13 | +| CTS-SPM DE-ENROLMENT REJECT | 7.1.14 | +| Operation data update messages: | Reference | +| CTS-SPM OPERATION DATA REQUEST | 7.1.15 | +| CTS-SPM OPERATION DATA DELIVER | 7.1.16 | +| CTS-SPM OPERATION DATA ACCEPT | 7.1.17 | +| CTS-SPM OPERATION DATA REJECT | 7.1.18 | +| CTS-SPM INFORMATION DATA REQUEST | 7.1.19 | +| CTS-SPM INFORMATION DATA RESPONSE | 7.1.20 | +| FP Authentication messages: | Reference | +| CTS-SPM FP AUTHENTICATION REQUEST | 7.1.21 | +| CTS-SPM FP AUTHENTICATION RESPONSE | 7.1.22 | +| CTS-SPM FP AUTHENTICATION REJECT | 7.1.23 | +| MS Authentication messages: | Reference | +| CTS-SPM MS AUTHENTICATION REQUEST | 7.1.24 | +| CTS-SPM MS AUTHENTICATION RESPONSE | 7.1.25 | +| CTS-SPM MS AUTHENTICATION REJECT | 7.1.26 | +| SN Authentication messages: | Reference | +| CTS-SPM SN SIGNING MODE COMMAND | 7.1.27 | + +### 7.1.1 CTS-FP initialisation request + +This message is sent by the fixed part to the service node to indicate to request initialisation on this fixed part. See table 7.2/GSM 04.xx. + +Message type: CTS-SPM INITIALISATION REQUEST + +Significance: dual + +Direction: fixed part to service node + +**Table 7.2/GSM 04.xx: CTS-SPM INITIALISATION REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|----------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS initialisation request message type | Message type subclause 8.4 | M | V | 1 | +| | Fixed Part Classmark | Fixed Part Classmark subclause 8.4.1.6 | M | V | 1 | +| | Fixed Part identity | Fixed Part identity subclause 8.4.1.4 | M | LV | 2 - 9 | + +### 7.1.2 CTS-FP initialisation accept + +This message is sent by the service node to the fixed part to indicate that initialisation of the fixed part is accepted. See table 7.3/GSM 04.xx. + +Message type: CTS-SPM INITIALISATION ACCEPT + +Significance: dual + +Direction: service node to fixed part + +**Table 7.3/GSM 04.xx: CTS-SPM INITIALISATION ACCEPT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS initialisation accept message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.3 CTS-FP initialisation complete + +This message is sent by the fixed part to the service node to indicate that initialisation of the fixed part has been completed. See table 7.4/GSM 04.xx. + +Message type: CTS-SPM INITIALISATION COMPLETE + +Significance: dual + +Direction: fixed part to service node + +**Table 7.4/GSM 04.xx: CTS-SPM INITIALISATION COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS initialisation complete message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.4 CTS-FP initialisation reject + +This message is sent by the service node to the the fixed part to indicate that the requested initialisation has been rejected. See table 7.5/GSM 04.xx. + +Message type: CTS-SPM INITIALISATION REJECT + +Significance: dual + +Direction: service node to fixed part + +**Table 7.5/GSM 04.xx: CTS-SPM INITIALISATION REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS initialisation reject message type | Message type subclause 8.4 | M | V | 1 | +| | Reject cause | Reject cause subclause 8.x | M | V | 1 | + +### 7.1.5 CTS-FP de-initialisation request + +This message is sent by the service node to the fixed part to indicate to request de-initialisation on this fixed part. See table 7.6/GSM 04.xx. + +Message type: CTS-SPM DE-INITIALISATION REQUEST + +Significance: dual + +Direction: service node to fixed part + +**Table 7.6/GSM 04.xx: CTS-SPM DE-INITIALISATION REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|----------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | ½ | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | ½ | +| | CTS de-initialisation request message type | Message type subclause 8.4 | M | V | 1 | +| | Fixed part Classmark | Fixed Part Classmark subclause 8.4.1.6 | M | V | 1 | +| | Fixed Part identity | Fixed part identity subclause 8.4.1.4 | M | LV | 2 - 9 | + +### 7.1.6 CTS-FP de-initialisation complete + +This message is sent by the fixed part to the service node to indicate that the requested de-initialisation has been completed. See table 7.7/GSM 04.xx. + +Message type: CTS-SPM DE-INITIALISATION COMPLETE + +Significance: dual + +Direction: fixed part to service node + +**Table 7.7/GSM 04.xx: CTS-SPM DE-INITIALISATION COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTSde-initialisation complete message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.7 CTS-FP de-initialisation reject + +This message is sent by the fixed part to the service node to indicate that the requested de-initialisation has not been completed. See table 7.8/GSM 04.xx. + +Message type: CTS-SPM DE-INITIALISATION REJECT + Significance: dual + Direction: fixed part to service node + +**Table 7.8/GSM 04.xx: CTS-SPM DE-INITIALISATION REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS de-initialisation reject message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.8 CTS enrolment request + +This message is sent by the fixed part to the service node to indicate to request a mobile enrolment onto this fixed part. See table 7.9/GSM 04.xx. + +Message type: CTS-SPM ENROLMENT REQUEST + Significance: + Direction: fixed part to service node + +**Table 7.9/GSM 04.xx: CTS-SPM ENROLMENT REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|-------------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS enrolment request message type | Message type subclause 8.4 | M | V | 1 | +| | Fixed Part identity | Fixed Part identity subclause 8.4.1.4 | M | LV | 2-9 | +| | Mobile station identity | Mobile station identity subclause 8.4.1.5 | M | LV | 2-9 | +| | Cell identity list | Cell identity list subclause 8.4.1.10 | M | LV | 7n | + +### 7.1.9 CTS-SPM enrolment accept + +This message is sent by the service node to the fixed part to indicate that enrolment of the mobile station onto the fixed part is accepted. See table 7.10/GSM 04.xx. + +Message type: CTS-SPM ENROLMENT ACCEPT + Significance: + Direction: service node to fixed part + +**Table 7.10/GSM 04.xx: CTS-SPM ENROLMENT ACCEPT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS-SPM enrolment accept message type | Message type subclause 8.4 | M | V | 1 | +| | Enrolment time | Enrolment time subclause 8.4.1.12 | M | V | 1 | + +### 7.1.10 CTS-SPM enrolment reject + +This message is sent by the service node to the fixed part to indicate that the requested enrolment has been rejected. See table 7.11/GSM 04.xx. + +Message type: CTS-SPM ENROLMENT REJECT + +Significance: dual + +Direction: service node to fixed part + +**Table 7.11/GSM 04.xx: CTS-SPM ENROLMENT REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS-SPM enrolment reject message type | Message type subclause 8.4 | M | V | 1 | +| | Reject cause | Reject cause subclause 8.x | M | V | 1 | + +### 7.1.11 CTS-SPM de-enrolment indication + +This message is sent by the fixed part to the service node to indicate de-enrolment of a mobile station from this fixed part. See table 7.12/GSM 04.xx. + +Message type: CTS-SPM DE-ENROLMENT INDICATION + +Significance: dual + +Direction: fixed part to service node + +**Table 7.12/GSM 04.xx: CTS-SPM DE-ENROLMENT INDICATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|-------------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS-SPM de-enrolment indication message type | Message type subclause 8.4 | M | V | 1 | +| | Mobile station identity | Mobile station identity subclause 8.4.1.5 | M | LV | 2 - 9 | +| | Fixed part identity | Fixed part identity subclause 8.4.1.4 | M | LV | 2 - 9 | +| | Cause | cause subclause 8.x | M | V | 1 | + +### 7.1.12 CTS-SPM de-enrolment request + +This message is sent by the service node to the fixed part to indicate to request de-enrolment of a given mobile station from the fixed part. See table 7.13/GSM 04.xx. + +Message type: CTS-SPM DE-ENROLMENT REQUEST + +Significance: dual + +Direction: service node to fixed part + +**Table 7.13/GSM 04.xx: CTS-SPM DE-ENROLMENT REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------------|----------------------------------------------|----------|--------|--------| +| | CTS supervising management
protocol discriminator | Protocol discriminator
subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
subclause 8.3.1 | M | V | 1/2 | +| | CTS de-enrolment request
message type | Message type
subclause 8.4 | M | V | 1 | +| | Fixed part identity | Fixed part identity
subclause 8.4.1.4 | M | LV | 2 - 9 | +| | Mobile station identity | Mobile station identity
subclause 8.4.1.5 | M | LV | 2 - 9 | + +### 7.1.13 CTS-SPM de-enrolment complete + +This message is sent by the fixed part to the service node to indicate that the requested de-enrolment has been completed. See table 7.14/GSM 04.xx. + +Message type: CTS-SPM DE-ENROLMENT COMPLETE + +Significance: dual + +Direction: fixed part to service node + +**Table 7.14/GSM 04.xx: CTS-SPM DE-ENROLMENT COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------------------------------------|-----------------------------------------|----------|--------|--------| +| | CTS supervising management
protocol discriminator | Protocol discriminator
subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator
subclause 8.3.1 | M | V | 1/2 | +| | CTS de-enrolment complete
message type | Message type
subclause 8.4 | M | V | 1 | + +### 7.1.14 CTS-SPM de-enrolment reject + +This message is sent by the fixed part to the service node to indicate that the requested de-enrolment has not been completed. See table 7.15/GSM 04.xx. + +Message type: CTS-SPM DE-ENROLMENT REJECT + +Significance: dual + +Direction: fixed part to service node + +**Table 7.15/GSM 04.xx: CTS-SPM DE-ENROLMENT REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS de-enrolment reject message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.15 CTS operation data request + +This message is sent by the fixed part to the service node to indicate that operation data are required. See table 7.16/GSM 04.xx. + +Message type: CTS-SPM OPERATION DATA REQUEST + +Significance: dual + +Direction: fixed part to service node + +**Table 7.16/GSM 04.xx: CTS-SPM OPERATION DATA REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|---------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS operation data request | Message type subclause 8.4 | M | V | 1 | +| | Fixed part identity | Fixed part identity subclause 8.4.1.4 | M | LV | 2 - 9 | +| | Cell identity list | Cell identity list subclause 8.4.1.10 | M | LV | 7n | + +### 7.1.16 CTS operation data deliver + +This message is sent by service node to the fixed part to deliver the operation data either following an FP request or initiated by the service node. See table 7.17/GSM 04.xx. + +Message type: CTS-SPM DE-OPERATION DATA DELIVER + +Significance: dual + +Direction: service node to fixed part + +**Table 7.17/GSM 04.xx: CTS-SPM OPERATION DATA DELIVER message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|------------------------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS operation data deliver message type | Message type subclause 8.4 | M | V | 1 | +| | Radio frequency control parameters | Radio frequency control parameters subclause 8.4.1.7 | M | V | 4 | +| | Radio link control parameters | Radio link control parameters subclause 8.4.1.8 | M | V | 4 | +| | Generic frequency list | GFL subclause 8.4.1.9 | M | LV | | +| | Validity period | Tval subclause 8.4.1.13 | M | V | 1 | +| | Recall period | Trecal subclause 8.4.1.14 | M | V | 1 | +| | Application time | Tappli subclause 8.4.1.x | M | V | 1 | + +### 7.1.17 CTS operation data accept + +This message is sent by the fixed part to the service node to indicate that the operation data sent the service node have been accepted by the fixed part. See table 7.18/GSM 04.xx. + +Message type: CTS-SPM OPERATION DATA ACCEPT + +Significance: dual + +Direction: fixed part to service node + +**Table 7.18/GSM 04.xx: CTS-SPM OPERATION DATA ACCEPT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS operation data accept message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.18 CTS operation data reject + +This message is sent by the fixed part to the service node to indicate that the operation data sent the service node have not been accepted by the fixed part. See table 7.19/GSM 04.xx. + +Message type: CTS-SPM DE-OPERATION DATA REJECT + +Significance: dual + +Direction: fixed part to service node + +**Table 7.19/GSM 04.xx: CTS-SPM OPERATION DATA REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS operation data reject message type | Message type subclause 8.4 | M | V | 1 | +| | Reject cause | Reject cause subclause 8.X | M | V | 1 | + +### 7.1.19 CTS information data request + +This message is sent by the service node to the fixed part indicate that information data are required. See table 7.20/GSM 04.xx. + +Message type: CTS-SPM INFORMATION DATA REQUEST + +Significance: dual + +Direction: service node to fixed part + +**Table 7.20/GSM 04.xx: CTS-SPM INFORMATION DATA REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS information data request message type | Message type subclause 8.4 | M | V | 1 | +| | Information data | Information data subclause 8.4.1.x | M | LV | tbd | + +### 7.1.20 CTS information data response + +This message is sent by the fixed part to the service node in response to an information data request. See table 7.21/GSM 04.xx. + +Message type: CTS-SPM INFORMATION DATA response + +Significance: dual + +Direction: fixed part to service node + +**Table 7.21/GSM 04.xx: CTS-SPM INFORMATION DATA RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS information data response message type | Message type subclause 8.4 | M | V | 1 | +| | Information data | Information data subclause 8.4.1.x | M | LV | tbd | + +### 7.1.21 CTS FP authentication request + +This message is sent by the service node to the fixed part to initiate authentication of the fixed part identity. See table 7.22/GSM 04.xx. + +Message type: CTS-SPM FP AUTHENTICATION REQUEST + +Significance: + +Direction: service node to the fixed part + +**Table 7.22/GSM 04.xx: CTS-SPM FP AUTHENTICATION REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS FP authentication request message type | Message type subclause 8.4 | M | V | 1 | +| | Authentication parameter RAND1 | Authentication parameter RAND1 subclause 8.4.1.1 | M | V | 16 | + +### 7.1.22 CTS FP authentication response + +This message is sent by the the fixed part to the service node to to deliver a calculated response to the service node. See table 7.23/GSM 04.xx. + +Message type: CTS-SPM FP AUTHENTICATION RESPONSE + +Significance: dual + +Direction: fixed part to service node + +**Table 7.23/GSM 04.xx: CTS-SPM FP AUTHENTICN RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS FP authentication response message type | Message type subclause 8.4 | M | V | 1 | +| | Authentication parameter RAND2 | Authentication parameter RAND2 subclause 8.4.1.2 | M | V | 16 | +| | Authentication parameter SRES | Authentication parameter SRES subclause 8.4.1.3 | M | V | 16 | + +### 7.1.23 CTS FP authentication reject + +This message is sent by the service node to the fixed part to indicate that authentication of the fixed part identity has failed. See table 7.24/GSM 04.xx. + +Message type: CTS-SPM FP AUTHENTICATION REJECT + +Significance: dual + +Direction: service node to the fixed part + +**Table 7.24/GSM 04.xx: CTS-SPM FP AUTHENTICATION REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS FP authentication reject message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.24 CTS MS authentication request + +This message is sent by the service node to the fixed part to initiate authentication of the mobile station identity. See table 7.25/GSM 04.xx. + +Message type: CTS-SPM MS AUTHENTICATION REQUEST + +Significance: dual + +Direction: service node to the fixed part + +**Table 7.25/GSM 04.xx: CTS-SPM MS AUTHENTICATION REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|---------------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS MS authentication request message type | Message type subclause 8.4 | M | V | 1 | +| | Mobile station identity | Mobile station identity subclause 8.4.1.5 | M | LV | 2 - 9 | +| | Authentication parameter RAND | Authentication parameter RAND subclause 8.x | M | V | 16 | + +### 7.1.25 CTS MS authentication response + +This message is sent by the the fixed part to the service node to to deliver a response calculated by the mobile station to the service node. See table 7.26/GSM 04.xx. + +Message type: CTS-SPM MS AUTHENTICATION RESPONSE + +Significance: dual + +Direction: fixed part to service node + +**Table 7.26/GSM 04.xx: CTS-SPM MS AUTHENTICATION RESPONSE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|---------------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS MS authentication response message type | Message type subclause 8.4 | M | V | 1 | +| | Mobile station identity | Mobile station identity subclause 8.4.1.5 | M | LV | 2 - 9 | +| | Authentication parameter SRES | Authentication parameter SRES subclause 8.x | M | V | 4 | + +### 7.1.26 CTS MS authentication reject + +This message is sent by the service node to the fixed part to indicate that authentication of the mobile station identity has failed. See table 7.27/GSM 04.xx. + +Message type: CTS-SPM MS AUTHENTICATION REJECT + +Significance: + +Direction: service node to the fixed part + +**Table 7.27/GSM 04.xx: CTS-SPM MS AUTHENTICATION REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS MS authentication reject message type | Message type subclause 8.4 | M | V | 1 | + +### 7.1.27 CTS SN signing mode command + +This message is sent by the service node to the fixed part to indicate that the service node starts signing. See table 7.28/GSM 04.xx. + +Message type: CTS-SPM SN signing mode command + +Significance: dual + +Direction: service node to fixed part + +**Table 7.28/GSM 04.xx: CTS-SPM SN signing mode command message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|---------------------------------------------------|--------------------------------------|----------|--------|--------| +| | CTS supervising management protocol discriminator | Protocol discriminator subclause 8.2 | M | V | 1/2 | +| | Skip Indicator | Skip Indicator subclause 8.3.1 | M | V | 1/2 | +| | CTS signing mode command message type | Message type subclause 8.4 | M | V | 1 | + +# --- 8 General message format and information elements coding + +The figures and text in this clause describe the Information Elements contents. + +## 8.1 Overview + +See corresponding clause in GSM 04.08. + +## 8.2 Protocol Discriminator + +The Protocol Discriminator (PD) and its use are defined in GSM 04.07 [20]. + +## 8.3 Skip indicator and transaction identifier + +### 8.3.1 Skip indicator + +Bits 5 to 8 of the first octet of every CTS Radio Resource management and CTS Mobility Management message contains the skip indicator. In order to differentiate GSM Radio Resource management and GSM Mobility Management messages from CTS Radio Resource management and CTS Mobility Management messages, the skip indicator used shall be 1111. A message received with skip indicator different from 1111 shall be ignored by the CTS Radio Resource management protocol entity and by the CTS Mobility Management protocol entity. A protocol entity sending a CTS Radio Resource management or a CTS Mobility Management message shall encode the skip indicator as 1111. + +### 8.3.2 Transaction identifier + +See GSM 04.08. + +## 8.4 Message Type + +The message type IE and its use are defined in GSM 04.07 [20]. Tables 8.1/GSM 04.xx define the value part of the message type IE used in the CTS Supervising management protocol. + +**Table 8.1/GSM 04.xx: Message types for CTS Supervising management** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|--------------------------------------| +| 0 | 0 | 1 | 1 | 1 | - | - | - | CTS-FP Initialisation messages: | +| | | | | 1 | 1 | 1 | - | - CTS-SPM INITIALISATION REQUEST | +| | | | | 0 | 0 | 1 | - | - CTS-SPM INITIALISATION ACCEPT | +| | | | | 0 | 1 | 0 | - | - CTS-SPM INITIALISATION COMPLETE | +| | | | | 1 | 0 | 0 | - | - CTS-SPM INITIALISATION REJECT | +| 0 | 0 | 1 | 1 | 0 | - | - | - | CTS-FP De-initialisation messages: | +| | | | | 1 | 0 | 1 | - | - CTS-SPM DE-INITIALISATION REQUEST | +| | | | | 0 | 1 | 0 | - | - CTS-SPM DE-INITIALISATION COMPLETE | +| | | | | 0 | 0 | 1 | - | - CTS-SPM DE-INITIALISATION REJECT | +| 0 | 0 | 1 | 0 | 1 | - | - | - | Enrolment messages: | +| | | | | 0 | 1 | 1 | - | - CTS-SPM ENROLMENT REQUEST | +| | | | | 1 | 0 | 0 | - | - CTS-SPM ENROLMENT ACCEPT | +| | | | | 0 | 0 | 0 | - | - CTS-SPM ENROLMENT REJECT | +| 0 | 0 | 0 | 0 | 1 | - | - | - | De-Enrolment messages: | +| | | | | 1 | 0 | 1 | - | - CTS-SPM DE-ENROLMENT INDICATION | +| | | | | 1 | 1 | 0 | - | - CTS-SPM DE-ENROLMENT REQUEST | +| | | | | 0 | 1 | 1 | - | - CTS-SPM DE-ENROLMENT COMPLETE | +| | | | | 0 | 0 | 0 | - | - CTS-SPM DE-ENROLMENT REJECT | +| 0 | 0 | 1 | 0 | 0 | - | - | - | Operation data update messages: | +| | | | | 0 | 0 | 1 | - | - CTS-SPM OPERATION DATA REQUEST | +| | | | | 0 | 1 | 0 | - | - CTS-SPM OPERATION DATA DELIVER | +| | | | | 1 | 0 | 0 | - | - CTS-SPM OPERATION DATA ACCEPT | +| | | | | 1 | 1 | 1 | - | - CTS-SPM OPERATION DATA REJECT | +| 0 | 0 | 0 | 1 | 1 | - | - | - | Information data request messages: | +| | | | | 0 | 0 | 1 | - | - CTS-SPM INFORMATION DATA REQUEST | +| | | | | 0 | 1 | 0 | - | - CTS-SPM INFORMATION DATA RESPONSE | +| 0 | 0 | 0 | 1 | 0 | - | - | - | Authentication messages: | +| | | | | 0 | 0 | 0 | - | - CTS-SPM FP AUTHENTICATION REQUEST | +| | | | | 0 | 1 | 0 | - | - CTS-SPM FP AUTHENTICATION RESPONSE | +| | | | | 1 | 1 | 1 | - | - CTS-SPM FP AUTHENTICATION REJECT | +| | | | | 1 | 0 | 0 | - | - CTS-SPM MS AUTHENTICATION REQUEST | +| | | | | 1 | 0 | 1 | - | - CTS-SPM MS AUTHENTICATION RESPONSE | +| | | | | 1 | 1 | 0 | - | - CTS-SPM MS AUTHENTICATION REJECT | +| | | | | 0 | 1 | 1 | - | - CTS-SPM SN SIGNING MODE COMMAND | + +Bit 8 is reserved for possible future use as an extension bit, see GSM 04.07. + +### 8.4.1 Supervising management information elements. + +#### 8.4.1.1 Authentication parameter RAND1 + +The purpose of the *Authentication Parameter RAND1* information element is to provide the fixed part with a non-predictable number to be used to calculate the authentication response SRES. + +The *Authentication Parameter RAND1* information element is coded as shown in figure 10.x/GSM 04.xx and table 10.x/GSM 04.xx. + +The *Authentication Parameter RAND1* is a type 3 information element with 17 octets length. + +![](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|----------| +| Authentication parameter RAND1 IEI | | | | | | | | octet 1 | +| RAND1 value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | octet 17 | + +**Figure 10.x/GSM 04.xx: Authentication Parameter RAND1 information element** + +**Table 10.x/GSM 04.xx: Authentication Parameter RAND1 information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------| +| RAND1 value (octet 2, 3, ... and 17) | +| The RAND1 value consists of 128 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 17 is the least significant bit. | + +#### 8.4.1.2 Authentication parameter RAND2 + +The purpose of the *Authentication Parameter RAND2* information element is to provide the service node with a non-predictable number to be used by the service node to calculate the data signature. + +The *Authentication Parameter RAND2* information element is coded as shown in figure 10.x/GSM 04.xx and table 10.x/GSM 04.xx. + +The *Authentication Parameter RAND2* is a type 3 information element with 17 octets length. + +![](b54ce9bffd341cd643e196d5f4538829_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|----------| +| Authentication parameter RAND2 IEI | | | | | | | | octet 1 | +| RAND2 value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | octet 17 | + +**Figure 10.x/GSM 04.xx: Authentication Parameter RAND2 information element** + +**Table 10.x/GSM 04.xx: Authentication Parameter RAND2 information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------| +| RAND2 value (octet 2, 3, ... and 17) | +| The RAND2 value consists of 128 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 17 is the least significant bit. | + +#### 8.4.1.3 Authentication parameter SRES + +The purpose of the *authentication parameter SRES* information element is to provide the service node with the authentication response signature calculated in the fixed part. + +The *Authentication Parameter SRES* information element is coded as shown in figure 10.x/GSM 04.xx and table 10.x/GSM 04.xx. + +The *Authentication Parameter SRES* is a type 3 information element with 17 octets length. + +![](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|---|---|---|---|---|---|---|----------| +| Authentication parameter SRES IEI | | | | | | | | octet 1 | +| SRES value | | | | | | | | octet 2 | +| ⋮ | | | | | | | | octet 17 | + +**Figure 10.x/GSM 04.xx Authentication Parameter SRES information element** + +**Table 10.x/GSM 04.xx: Authentication Parameter SRES information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------| +| SRES value (octet 2, 3, ... and 17) | +| The SRES value consists of 128 bits. Bit 8 of octet 2 is the most significant bit while bit 1 of octet 17 is the least significant bit. | +| | + +#### 8.4.1.4 Fixed part Identity + +The purpose of the *Fixed part Identity* information element is to provide either the international fixed part subscriber identity, IFPSI, or the international fixed part equipment identity, IFPEI. + +The IFPSI shall not exceed 15 digits, the IFPEI is composed of 16 digits (see GSM 03.03). + +The *Fixed part Identity* information element is coded as shown in figure 10.x/GSM 04.xx and table 10.x/GSM 04.xx. + +The Fixed part Identity is a type 4 information element with a minimum length of 3 octets and 11 octets length maximal. + +![](4b587081b669e7c6695b0e5db5ea7f6d_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------|---|---|---|-----------------------|------------------|---|---|----------| +| Fixed part Identity IEI | | | | | | | | octet 1 | +| Length of fixed part identity contents | | | | | | | | octet 2 | +| Identity digit 1 | | | | odd/
even
indic | Type of identity | | | octet 3 | +| Identity digit p+1 | | | | Identity digit p | | | | octet 4* | + +**Figure 10.5/GSM 04.xx Fixed part Identity information element** + +**Table 10.8/GSM 04.xx: Fixed part Identity information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type of identity (octet 3) | +| Bits | +| 3 2 1 | +| 0 0 1 IFPSI | +| 0 1 0 IFPEI | +| All other values are reserved. | +| Odd/even indication (octet 3) | +| Bit | +| 4 | +| 0 even number of identity digits and also when | +| 1 odd number of identity digits | +| Identity digits (octet 3 etc) | +| For the IFPSI, IFPEI this field is coded using BCD coding. If the number of identity digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". | + +#### 8.4.1.5 Mobile station Identity + +The purpose of the *Mobile station Identity* information element is to provide to the service node the international mobile station subscriber identity, IMSI. + +The IMSI shall not exceed 15 digits (see GSM 03.03). + +The *Mobile station Identity* information element is coded as shown in figure 10.x/GSM 04.xx and table 10.x/GSM 04.xx. + +The Mobile station Identity is a type 4 information element with a minimum length of 3 octets and 11 octets length maximal. + +![](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +| | | | | | | | | | | +|--|----------------------------------------|---|---|---|-----------------------|------------------|---|---|----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | Mobile station Identity IEI | | | | | | | | octet 1 | +| | Length of fixed part identity contents | | | | | | | | octet 2 | +| | Identity digit 1 | | | | odd/
even
indic | Type of identity | | | octet 3 | +| | Identity digit p+1 | | | | Identity digit p | | | | octet 4* | + +**Figure 10.5/GSM 04.xx: Mobile station Identity information element** + +**Table 10.8/GSM 04.xx: Mobile station Identity information element** + +| | | +|-------------------------------------------------------|----------------------------------------------| +| Type of identity (octet 3) | | +| Bits | | +| 3 | 2 1 | +| 0 0 1 | IMSI | +| All other values are reserved. | | +| Odd/even indication (octet 3) | | +| Bit | | +| 4 | | +| 0 | even number of identity digits and also when | +| 1 | odd number of identity digits | +| Identity digits (octet 3 etc) | | +| For the IMSI this field is coded using BCD | | +| coding. If the number of identity digits is even then | | +| bits 5 to 8 of the last octet shall be filled with | | +| an end mark coded as "1111". | | + +#### 8.4.1.6 Fixed Part Classmark + +The purpose of the *Fixed part Classmark* information element is to provide the service node with information concerning characteristics of the fixed part. The contents might affect the manner in which the service node handles the operation of the fixed part. + +The Fixed Part Classmark information element has 2 octets length. + +The value part of a *Fixed Part Classmark* information element is coded as shown in figure 10.5.1.7/GSM 04.xx. + +**Table 10.5.1.7/GSM 04.xx: Fixed Part Classmark information element** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------|--------------------------|---|---|-------|---|---|---|---------| +| | Fixed part Classmark IEI | | | | | | | octet 1 | +| 0 | Band | | | 0 | 0 | 0 | 0 | octet 2 | +| spare | | | | spare | | | | | + +**Table 10.8/GSM 04.xx: Fixed part Classmark information element** + +| | | +|--------------------------------|------------------------| +| Band (octet 2) | | +| Bits | | +| 7 | 6 5 | +| 0 0 0 | GSM900 band supported | +| 0 0 1 | E-GSM band supported | +| 0 1 0 | DCS1800 band supported | +| 0 1 1 | GSM1900 band supported | +| All other values are reserved. | | + +#### 8.4.1.7 Radio frequency control Parameters + +The purpose of the Radio Frequency control parameters information element is to provide the radio parameters to be applied on the fixed part. + +![](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------|--------------|---|---|------------------------|--------------------|---|---|---------| +| Radio Frequency Control parameters IEI | | | | | | | | octet 1 | +| AFA
USE | SEL_RANGE | | | | APPROACH
TYPE | | | octet 2 | +| MIN_NB_FREQ | | | | FWT_SIZE_WIN
(high) | | | | octet 3 | +| FWT_SIZE
WIN (low) | SWT_SIZE_WIN | | | | CTSBCH
SEL_MODE | | | octet 4 | +| INTERF_THRESHOLD | | | | 0 0 0
spare | | | | octet 5 | + +**Figure 10.2/GSM 04.xx: *Radio Frequency Control Parameters* information element** + +**Table 10.8/GSM 04.xx: Radio Frequency Control Parameters information element** + +| | | +|------------------------------------------------------------------------|----------------------------------| +| AFA_USE, use of AFA algorithm (octet 2) | | +| Bit | | +| 8 | | +| 0 | AFA used | +| 1 | AFA not used | +| SEL_RANGE, carrier list selection upper bound (octet 2) | | +| Bits | | +| 7 | 6 5 4 3 | +| 0 | 0 0 0 0 0 range 0 | +| 0 | 0 0 0 0 1 range 1 | +| . | . | +| . | . | +| 1 | 1 1 1 1 1 range 31 | +| APPROACH TYPE, type of approach used in selection range (octet 2) | | +| Bits | | +| 2 | 1 | +| 0 | 0 Basic Threshold (BASIC) | +| 0 | 1 Sliding window technique (SWT) | +| 1 | 0 Fixed window technique (FWT) | +| 1 | 1 List extension check (EXT) | +| MIN_NB_FREQ, minimum number of frequency (octet 3) | | +| Bits | | +| 8 | 7 6 5 4 | +| 0 | 0 0 0 0 0 no frequency | +| 0 | 0 0 0 0 1 1 frequency | +| . | . | +| . | . | +| 1 | 1 1 1 1 1 31 frequencies | +| FWT_SIZE_WIN, minimum size of the window for FWT (octet 3 and octet 4) | | +| Bits | | +| 3 | 2 1 8 7 | +| 0 | 0 0 0 0 0 size 0 | +| 0 | 0 0 0 0 0 size 1 | +| . | . | +| . | . | +| 1 | 1 1 1 1 1 size 31 | +| SWT_SIZE_WIN, fixed size of the window for SWT (octet 4) | | +| Bits | | +| 6 | 5 4 3 2 | +| 0 | 0 0 0 0 0 size | +| 0 | 0 0 0 0 0 size 1 | +| . | . | +| . | . | +| 1 | 1 1 1 1 1 size 31 | +| CTSBCH_SEL_MODE, CTSBCH selection mode (octet 4) | | +| Bit | | +| 1 | | +| 0 | best carrier of TFH list | +| 1 | random carrier of TFH list | +| INTERF_THRESHOLD, interference threshold (octet 5) | | +| Bits | | +| 8 | 7 6 5 4 | +| 0 | 0 0 0 0 0 0dB (steps of 2dB) | +| 0 | 0 0 0 0 0 2dB | +| . | . | +| . | . | +| 1 | 1 1 1 1 1 62dB | + +#### 8.4.1.8 Radio link control Parameters + +The purpose of the *Radio Link control Parameters* information element is to provide the radio parameters to be applied on the fixed part. + +![](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------|---|----------------------|---|----------------------------|---|------------|---|---------| +| Radio Frequency Link parameters IEI | | | | | | | | octet 1 | +| CTS_FP_MAX_TXPWR | | | | CTS_MS_MAX_TXPWR
(high) | | | | octet 2 | +| CTS_MAX_TXPWR
(low) | | CTS-RXLEV_ACCESS_MIN | | | | | | octet 3 | +| CTS_CELL_RESELECT_OFFSET | | | | 0 | | 0
spare | | octet 4 | +| CTS_RADIO_LINK_TIMEOUT | | | | | | | | octet 5 | + +Figure 10.2/GSM 04.xx: *Radio Link Control Parameters* information element + +**Table 10.8/GSM 04.xx: Radio Link Control Parameters information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CTS_FP_MAX_TXPWR, maximum Fixed Part transmission power
(octet 2)
Bits
8 7 6 5 4
0 0 0 0 0 level 0
0 0 0 0 1 level 1
.
.
1 1 1 1 1 level 31

CTS_MX_MAX_TXPWR, maximum Mobile Station transmission
power (octet 2 and octet 3)
Bits
3 2 1 8 7
0 0 0 0 0 level 0
0 0 0 0 1 level 1
.
.
1 1 1 1 1 level 31

CTS_RXLEV_ACCESS_MIN, minimum received level at the MS
(octet 3) Coded as defined in GSM05.08
Bits
6 5 4 3 2 1
0 0 0 0 0 0 level 0
0 0 0 0 0 1 level 1
.
.
1 1 1 1 1 1 level 63

CTS_CELL_RESELECT_OFFSET_, reselection offset (octet 4)
Bits
8 7 6 5 4 3
0 0 0 0 0 0 0 dB
0 0 0 0 0 1 1 dB
.
.
1 1 1 1 1 1 63 dB

CTS_RADIO_LINK_TIMEOUT, maximum value of the radio
link counter (octet 5)
Bits
8 7 6 5
0 0 0 0 4 SACCH blocks (setps of 4 blocks)
0 0 0 1 8 SACCH blocks
.
.
1 1 1 1 64 SACCH blocks | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 8.4.1.9 Generic Frequency List + +The purpose of the *Generic Frequency List* information element is to provide the generic frequency list to be used to derive the AFA list (see GSM04.56) to be used on the CTS interface. + +Its coding is similar to the "GSM04.08 Cell Channel Description" information field coding. + +#### 8.4.1.10 Cell Identity List + +The purpose of the *Cell Identity List* information element is to provide to the service node the list of the cell global identities surrounding the fixed part. + +![](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------|---|---|---|--------------|---|---|---|------------| +| Cell Identity List IEI | | | | | | | | octet 1 | +| Length of Cell Identity List contents | | | | | | | | octet 2 | +| MCC1 digit 2 | | | | MCC1 digit 1 | | | | octet 3 | +| 1 | 1 | 1 | 1 | MCC1 digit3 | | | | octet 4 | +| MNC1 digit 2 | | | | MNC1 digit1 | | | | octet 5 | +| LAC1 | | | | | | | | octet 6 | +| LAC1 (continued) | | | | | | | | octet 7 | +| CI1 value | | | | | | | | octet 8 | +| CI1 value (continued) | | | | | | | | octet 9 | +| MCC2 digit 2 | | | | MCC2 digit 1 | | | | octet 10 | +| 1 | 1 | 1 | 1 | MCC2 digit3 | | | | octet 11 | +| MNC2 digit 2 | | | | MNC2 digit1 | | | | octet 12 | +| LAC2 | | | | | | | | octet 13 | +| LAC2 (continued) | | | | | | | | octet 14 | +| CI2 value | | | | | | | | octet 15 | +| CI2 value (continued) | | | | | | | | octet 16 | +| MCCn digit 2 | | | | MCCn digit 1 | | | | octet 7n-4 | +| 1 | 1 | 1 | 1 | MCCn digit3 | | | | octet 7n-3 | +| MNCn digit 2 | | | | MNCn digit1 | | | | octet 7n-2 | +| LACn | | | | | | | | octet 7n-1 | +| LACn (continued) | | | | | | | | octet 7n | +| CIn value | | | | | | | | octet 7n+1 | +| CIn value (continued) | | | | | | | | octet 7n+2 | + +**Figure 10.5/GSM 04.xx: Cell Identity List information element** + +**Table 10.8/GSM 04.xx: Cell Identity List information element** + +| | +|------------------------------------------------------------------------------------------------------| +| MCC, Mobile country code (octets 7n-4 and 7n-3) | +| MNC, Mobile Network code (octet 7n-2) | +| LAC, Location area code (octets 7n-1 and 7n) | +| These fields are coded as the "Location Area Identification" Information element in GSM04.08 | +| CI, Cell Identity (octets 7n+1 and 7n+2) is coded as "Cell Identity" Information element in GSM04.08 | + +#### 8.4.1.11 Application time + +The purpose of the *Application time* information element is to provide to the fixed part the time when the new control data sent by the service node should apply. + +![](3b00a61116faef21d3a6009fd350b46a_img.jpg) + +| | | | | | | | | | +|------------------------------|--------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Application time IEI | | | | | | | | octet 1 | +| Application time information | Tapplc | | | | | | | octet 2 | +| Tapplc (continued) | | | | | | | | octet 3 | + +**Figure 10.5/GSM 04.xx: Application time information element****Table 10.8/GSM 04.xx: Application time information element** + +| | | +|--------------------------------------------|--------------------------------| +| Application time information (octet 2) | | +| Bits | | +| 8 | 7 | +| 0 | 0    apply immediately | +| 0 | 1    apply at Tval expiry | +| 1 | 0    apply at Tapplc | +| All other values are reserved. | | +| Tapplc, application timer (octets 2 and 3) | | +| Bits | | +| 8 | 7 6 5 4 3 2 1 | +| 0 | 0 0 0 0 0 0 0 Tapplc = 0day | +| 0 | 0 0 0 0 0 0 1 Tapplc = 1day | +| 1 | 1 1 1 1 1 1 1 Tapplc = 255days | + +#### 8.4.1.12 Enrolment time + +The purpose of the *Enrolment time* information element is to provide to the fixed part the duration associated to a mobile enrolment. + +![](5879500ca01e1a2521654beff6c289a4_img.jpg) + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Enrolment time IEI | | | | | | | | octet 1 | +| Tenrol | | | | | | | | octet 2 | + +**Figure 10.5/GSM 04.xx: Enrolment time information element** + +**Table 10.8/GSM 04.xx: Enrolment time information element** + +| | | | | | | | | | +|--------------------------------------|---|---|---|---|---|---|---|------------------| +| Enrolment time information (octet 2) | | | | | | | | | +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Tenrol = 0day | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Tenrol = 1day | +| . | . | . | . | . | . | . | . | | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Tenrol = 255days | + +#### 8.4.1.13 Validity period + +The purpose of the *Validity period* information element is to provide to the fixed part the validity period associated with parameters updated by the service node. + +| | | | | | | | | | +|---|---|---------------------|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | | Validity period IEI | | | | | | octet 1 | +| | | Tval | | | | | | octet 2 | + +**Figure 10.5/GSM 04.xx: *Validity period* information element****Table 10.8/GSM 04.xx: Validity period information element** + +| | | | | | | | | | +|---------------------------------------|---|---|---|---|---|---|---|----------------| +| Validity period information (octet 2) | | | | | | | | | +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Tval = 0day | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Tval = 1day | +| . | . | . | . | . | . | . | . | | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Tval = 255days | + +#### 8.4.1.14 Recall period + +The purpose of the *Recall period* information element is to require the fixed part to contact the service node for control purposes. + +| | | | | | | | | | +|---|---|-------------------|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | | Recall period IEI | | | | | | octet 1 | +| | | Trecal | | | | | | octet 2 | + +**Figure 10.5/GSM 04.xx: *Recall period* information element****Table 10.8/GSM 04.xx: Recall period information element** + +| | | | | | | | | | +|-------------------------------------|---|---|---|---|---|---|---|------------------| +| Recall period information (octet 2) | | | | | | | | | +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Trecal = 0day | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Trecal = 1day | +| . | . | . | . | . | . | . | . | | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Trecal = 255days | + +# --- 9 List of system parameters + +The description of timers in the following table should be considered a brief summary. The precise details are found in clauses 3 to 6, which should be considered the definitive descriptions. + +## 9.1 Timers and counters for radio resource management + +### 9.1.1 Timers on the SN side + +### 9.1.2 Timers on the CTS-FP side + +# Annex A (informative): Change Request History + +| Change history | | | | | | +|----------------|-----------------|---------|-------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CN No. | Document number | CR. No. | Old version | New version | Subject/Comments | +| S31 | R99 | | 7.0.1 | 8.0.0 | Upgrade of specification to release 1999/ V8.0.0 | +| | R99 | | 8.0.0 | 8.0.1 | Version update to 8.0.1 for Publication | +| CN#11 | Rel-4 | | 8.0.1 | 4.0.0 | Release 4 after CN#11 | +| NP-16 | Rel-5 | | 4.0.0 | 5.0.0 | Plenary decision to make this TS also for Rel-5. ETSI/MCC additionally made editorial cleanup. But open issues remains: Spec. number (eg.04.xx) is missing in figure 5.1 and elsewhere. Subclause numbers (eg.8.x) is missing in tables 7.5, 7.12, 7.19, 7.20, 7.21, 7.25 and 7.26. IE length defined as 'tbd' in tables 7.20 and 7.21. Should empty subclauses in clause 9 be changed to void? | +| NP-26 | Rel-6 | | 5.0.0 | 6.0.0 | Plenary decision to make this TS also for Rel-6. | +| | Rel-7 | | 6.0.0 | 7.0.0 | Plenary decision to make this TS also for Rel-7. | +| CP-42 | Rel-8 | | 7.0.0 | 8.0.0 | Plenary decision to make this TS also for Rel-8. | +| CP-46 | Rel-9 | | 8.0.0 | 9.0.0 | Plenary decision to make this TS also for Rel-9. | +| CP-51 | Rel-10 | | 9.0.0 | 10.0.0 | Plenary decision to make this TS also for Rel-10. | +| CP-57 | Rel-11 | | 10.0.0 | 11.0.0 | Plenary decision to make this TS also for Rel-11. | +| | Rel-11 | | 11.0.0 | 11.0.1 | Deleted unexpected annex L | +| CP-65 | Rel-12 | | 11.0.1 | 12.0.0 | Plenary decision to make this TS also for Rel-12. | +| CP-70 | Rel-13 | | 12.0.0 | 13.0.0 | Upgrade to Rel-13 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2018-06 | SA#80 | | | | | Upgrade to Rel-15 | 15.0.0 | +| 2020-07 | SA#88e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44060/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/44_series/44060/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dea9b732018f9aa038b97d2e43b1f3e255817e2e --- /dev/null +++ b/marked/Rel-16/44_series/44060/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ed6c7add6080260b54be93d5223ce8c4c71bbda4a587c133c9746ba60554d97 +size 56767 diff --git a/marked/Rel-16/44_series/44060/06faefab7f20d05bf410e9a250268f64_img.jpg b/marked/Rel-16/44_series/44060/06faefab7f20d05bf410e9a250268f64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f73dc6aef7cd34c913bb810932525d2bd47752bf --- /dev/null +++ b/marked/Rel-16/44_series/44060/06faefab7f20d05bf410e9a250268f64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c3ae21b7f925a4401a0df3ca2f9d2e202c58e2606c73b999f76e6810c1275ec +size 77425 diff --git a/marked/Rel-16/44_series/44060/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/44_series/44060/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d37043118c3f31d163a3db379de28105d9be79ab --- /dev/null +++ b/marked/Rel-16/44_series/44060/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e5d7b4ac5eda677b17af9065ee82d2a313171bb5f6e46b2c31d24b01a72d208 +size 34650 diff --git a/marked/Rel-16/44_series/44060/15e4a144a88176b71ea3eff2722253b0_img.jpg b/marked/Rel-16/44_series/44060/15e4a144a88176b71ea3eff2722253b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae6665e3037373675bf32a5f94972c02648f6d76 --- /dev/null +++ b/marked/Rel-16/44_series/44060/15e4a144a88176b71ea3eff2722253b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce4b47db68b11b7508fb56ff4795e3af5baaff953062252550277c22b7ed9d8d +size 24888 diff --git a/marked/Rel-16/44_series/44060/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-16/44_series/44060/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26de678cd9deaff02ac334b22c691a988edb4474 --- /dev/null +++ b/marked/Rel-16/44_series/44060/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:093174f8fadfe85f80bedaa96e4b95879240490026169c13918cf96f40d7feae +size 25002 diff --git a/marked/Rel-16/44_series/44060/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-16/44_series/44060/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccd32dd8657de71da3b25a703782693bdaaed499 --- /dev/null +++ b/marked/Rel-16/44_series/44060/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d07aac3af1eca83220167ee49dd1b77d35bb8b4baa275ddeca73784ea5f25bd5 +size 16821 diff --git a/marked/Rel-16/44_series/44060/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-16/44_series/44060/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34fef8b1a77b9f87b78847f3efc1ff0c98962751 --- /dev/null +++ b/marked/Rel-16/44_series/44060/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ea42f599ca949c3663e07913ba712d2c6f9cb4d04c742c6881bf443d6f8366e +size 19372 diff --git a/marked/Rel-16/44_series/44060/1f1e9d5f20165c68490ae895ad73d5a7_img.jpg b/marked/Rel-16/44_series/44060/1f1e9d5f20165c68490ae895ad73d5a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e5c213f312934d877b83dab95783b1039553855 --- /dev/null +++ b/marked/Rel-16/44_series/44060/1f1e9d5f20165c68490ae895ad73d5a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:092e80da9ca50495c533ca347ab80480d6ebea688ebf447ae5c8823782d0ae11 +size 76173 diff --git a/marked/Rel-16/44_series/44060/2d701e1404ebacb18f0b58713fe7d894_img.jpg b/marked/Rel-16/44_series/44060/2d701e1404ebacb18f0b58713fe7d894_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baca0e201a34fd32f17c5b0105fe2a42c26441ca --- /dev/null +++ b/marked/Rel-16/44_series/44060/2d701e1404ebacb18f0b58713fe7d894_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5f98282b563439b5c8576a22bae3b619bd8e02ceba72aa7de6080615a49cdfe +size 94290 diff --git a/marked/Rel-16/44_series/44060/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/44_series/44060/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c4a92076d92c62b42ee699da03c2e873c0d9b8 --- /dev/null +++ b/marked/Rel-16/44_series/44060/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30fc7b4ea30a0e347c5a182786285024d17e183f8dea505ceedaf063e6aa4828 +size 58644 diff --git a/marked/Rel-16/44_series/44060/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/44_series/44060/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3ead8481b6c9f07051cb67b42e7c3d93ebb7f2d --- /dev/null +++ b/marked/Rel-16/44_series/44060/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11ce54b53dca31256b02ae646c0fd9fca2c97e2a1a5d795289546c7c8213fec7 +size 44720 diff --git a/marked/Rel-16/44_series/44060/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/44_series/44060/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdbd752bfd3826f7fead868ff2af52767b425626 --- /dev/null +++ b/marked/Rel-16/44_series/44060/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ac55c8193eb7ba194687198f23f3f72b40b67d18af5c1b3443458404186eee2 +size 18361 diff --git a/marked/Rel-16/44_series/44060/4e0a625d1c8db7dab805bf443c880129_img.jpg b/marked/Rel-16/44_series/44060/4e0a625d1c8db7dab805bf443c880129_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7960c90a7d8e9156dc04eff192ad70fb04b014ce --- /dev/null +++ b/marked/Rel-16/44_series/44060/4e0a625d1c8db7dab805bf443c880129_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24bc4f5991d88046452e426c4c7182178f2f24447805163c4a50ac952c8d58cd +size 37552 diff --git a/marked/Rel-16/44_series/44060/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-16/44_series/44060/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e3b4c1834c3b21e8bec7d9971e2df77efc29898 --- /dev/null +++ b/marked/Rel-16/44_series/44060/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ce7a24b3944207b9c6986356af5c264575be001189217c2dca338c0f107d042 +size 42759 diff --git a/marked/Rel-16/44_series/44060/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/44_series/44060/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9ab93b78aeae822339a1b0ffbc2c2dad5fe59be --- /dev/null +++ b/marked/Rel-16/44_series/44060/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe811c487dcd2bfde00ab63d7ccc91df9efd92f59ec3a8403fee3258f7bf134f +size 46590 diff --git a/marked/Rel-16/44_series/44060/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/Rel-16/44_series/44060/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a20a8e02da1386acc732f58ef963eb3f1830296 --- /dev/null +++ b/marked/Rel-16/44_series/44060/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:305f1216d2b1345bd3dd8d9b38256cdd1c568f007f2d732b429e72a3ccbdf43e +size 28163 diff --git a/marked/Rel-16/44_series/44060/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-16/44_series/44060/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5574fe528c933d92879cf027c3525a2837e32d3 --- /dev/null +++ b/marked/Rel-16/44_series/44060/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e892efd8f15c918b0e6dda0f9792fdc22dcc0d5f2447b64879c7bed60a8f8af +size 64473 diff --git a/marked/Rel-16/44_series/44060/68d8089266ace7197304b43dcaf5d08e_img.jpg b/marked/Rel-16/44_series/44060/68d8089266ace7197304b43dcaf5d08e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1adc0a80841963d9fb5649ef17db169a8d686e38 --- /dev/null +++ b/marked/Rel-16/44_series/44060/68d8089266ace7197304b43dcaf5d08e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:748659a138475ef886b306bcdfc5599772ded117c4a0b4d278c763c4d3ea9607 +size 21061 diff --git a/marked/Rel-16/44_series/44060/6a555cff11e140861ce08db72b01a6a2_img.jpg b/marked/Rel-16/44_series/44060/6a555cff11e140861ce08db72b01a6a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae49bbbb48444de3387c95299b6e6e5e73b083a9 --- /dev/null +++ b/marked/Rel-16/44_series/44060/6a555cff11e140861ce08db72b01a6a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9e11cc8124e0b2ffe60b3482a8045207d6903c7676f7f924a380cb7f844574c +size 18360 diff --git a/marked/Rel-16/44_series/44060/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-16/44_series/44060/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c339f0215f1dfe1bbede8f97a9cb57352abf77d3 --- /dev/null +++ b/marked/Rel-16/44_series/44060/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ef6f775f9f26166ee7c1436a3fe796bb05603a7eae2d732207196447baee585 +size 23953 diff --git a/marked/Rel-16/44_series/44060/72445157c2c2b35e98cdc0d5b513f74b_img.jpg b/marked/Rel-16/44_series/44060/72445157c2c2b35e98cdc0d5b513f74b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41d43b885dbad2e813f3a9dd0bf39423c30c8533 --- /dev/null +++ b/marked/Rel-16/44_series/44060/72445157c2c2b35e98cdc0d5b513f74b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfe6b31c4b511dc041e571d08bf3321e60e55eb41deb8c224df24716052dc50b +size 43815 diff --git a/marked/Rel-16/44_series/44060/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg b/marked/Rel-16/44_series/44060/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..672db350b08c46b402f61b97c4a7a8cb6fc41a35 --- /dev/null +++ b/marked/Rel-16/44_series/44060/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1af4f1f693901c4caf784ecfabb6ce633284d57a2fd1f3004747ea93b8a1fecd +size 17544 diff --git a/marked/Rel-16/44_series/44060/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Rel-16/44_series/44060/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ef2a0cae1af8db729865e49ae2ae82b57ac1050 --- /dev/null +++ b/marked/Rel-16/44_series/44060/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ab949cbaae848ac4011c57a41227e3a891f9e099bed6a9251774c84a399a97e +size 27455 diff --git a/marked/Rel-16/44_series/44060/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/44_series/44060/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d44c6ca424e2d624f9d6f57331ca105bd37d8f52 --- /dev/null +++ b/marked/Rel-16/44_series/44060/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26ee842319322951b3cf7f2fc1818fbf36f7a7be724bb0344c01597356520fdd +size 67672 diff --git a/marked/Rel-16/44_series/44060/890973c123723e95fafd25e725668b4a_img.jpg b/marked/Rel-16/44_series/44060/890973c123723e95fafd25e725668b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..815016f09d4fc11bee6337701ab7b69a32a4715a --- /dev/null +++ b/marked/Rel-16/44_series/44060/890973c123723e95fafd25e725668b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1081a9e5e7b69d2fc5e237843f1058b96197a2e531737846285a97af3aeff5fa +size 47645 diff --git a/marked/Rel-16/44_series/44060/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/44_series/44060/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb94327668076075f78ff94e5f91ea25e22f619b --- /dev/null +++ b/marked/Rel-16/44_series/44060/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80f31c9898d4dff334feeda04b1048c62c3d1be98fa93a909fe8d5161cb0958d +size 18166 diff --git a/marked/Rel-16/44_series/44060/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/44_series/44060/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8672fc5c7e8252fd1ceeb6581ef05f60808a6524 --- /dev/null +++ b/marked/Rel-16/44_series/44060/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f11c0c0250ceedb262e07f2a56e6d50cd2706b98459abe33a0886e60f4ff6b1 +size 92219 diff --git a/marked/Rel-16/44_series/44060/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/Rel-16/44_series/44060/90ee16ccc0ad16aeca48087797d7b07f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ee9227ebd258dfac0a998b41ebcb8cf871cf3cd --- /dev/null +++ b/marked/Rel-16/44_series/44060/90ee16ccc0ad16aeca48087797d7b07f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a9920cab89f148c23b1622de8618beb29b82171b3f340791ceed585da0729e7 +size 2890 diff --git a/marked/Rel-16/44_series/44060/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-16/44_series/44060/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..edd462a723a23ba74f6576397baddad0c94dd3ab --- /dev/null +++ b/marked/Rel-16/44_series/44060/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9953636038a8d555e1b52dee0a317369e8359f1e4fadbc5db9405ca4e000e77 +size 18479 diff --git a/marked/Rel-16/44_series/44060/97474b58ccf5b5329b0b9ec637ab15d5_img.jpg b/marked/Rel-16/44_series/44060/97474b58ccf5b5329b0b9ec637ab15d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d07fab147cb778bd833c30d6b5bbd63fae0ba3d --- /dev/null +++ b/marked/Rel-16/44_series/44060/97474b58ccf5b5329b0b9ec637ab15d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc15dc0312698567889d276019d1860ec91adf3be431b1873211c19613d3dc3d +size 15250 diff --git a/marked/Rel-16/44_series/44060/9e47aa7528e713ae12a7739999286108_img.jpg b/marked/Rel-16/44_series/44060/9e47aa7528e713ae12a7739999286108_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ade255592b728a94d8b7fe1a04bacbdf1f78b1ec --- /dev/null +++ b/marked/Rel-16/44_series/44060/9e47aa7528e713ae12a7739999286108_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bdd12b1d5819ff441f943c39b41094778613c69e0847ab94ed68defb3736b4f +size 35280 diff --git a/marked/Rel-16/44_series/44060/9ecaf3842a06bb8defd6bea7de551283_img.jpg b/marked/Rel-16/44_series/44060/9ecaf3842a06bb8defd6bea7de551283_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baeb4271227c3baef166fdb4ace524b87a093ff3 --- /dev/null +++ b/marked/Rel-16/44_series/44060/9ecaf3842a06bb8defd6bea7de551283_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e562a68c1e3f2785d7f8ee579d299e92aff4f4162d2031e0dd967fe88d00b6b8 +size 20402 diff --git a/marked/Rel-16/44_series/44060/a0e4d56066bf089079b9b4d24f666b01_img.jpg b/marked/Rel-16/44_series/44060/a0e4d56066bf089079b9b4d24f666b01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..446b9bff2c5118833cff439ffef500ac6d43cfb1 --- /dev/null +++ b/marked/Rel-16/44_series/44060/a0e4d56066bf089079b9b4d24f666b01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f750c349d233f98b27d6bde785077dffe144ce394f9d68c88d462b015f3a505d +size 16929 diff --git a/marked/Rel-16/44_series/44060/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/44_series/44060/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6645de362fcbb4583baa0831b73b1c827844e72 --- /dev/null +++ b/marked/Rel-16/44_series/44060/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47b964df1dcbbdb6c1fc4518c1997528e32335cfff23e06722568da8d60b538a +size 29324 diff --git a/marked/Rel-16/44_series/44060/a48ecbf3100ebf31b5d615267fa263c3_img.jpg b/marked/Rel-16/44_series/44060/a48ecbf3100ebf31b5d615267fa263c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66c744f3d4568da6c758bedd59811a57e1d2d0d9 --- /dev/null +++ b/marked/Rel-16/44_series/44060/a48ecbf3100ebf31b5d615267fa263c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3be95b39c9d8f6ddafa37da00be1553c1c9cfd15f27df6e7333e5e9ca034e55c +size 20013 diff --git a/marked/Rel-16/44_series/44060/a51105b2031bad93b818b82f071c6add_img.jpg b/marked/Rel-16/44_series/44060/a51105b2031bad93b818b82f071c6add_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36e8d20677d01d447d9a8a0f37d58b903a808c9e --- /dev/null +++ b/marked/Rel-16/44_series/44060/a51105b2031bad93b818b82f071c6add_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46353b0d07ed6a66053ffb8ec13595297862e3368f37ac30aff9ad77ba03d5f5 +size 2720 diff --git a/marked/Rel-16/44_series/44060/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-16/44_series/44060/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4c9d63a36a17da2199562fc7fc04589e82a2271 --- /dev/null +++ b/marked/Rel-16/44_series/44060/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:317b073143e892f48b46480922f4384c1764163461771773f6e08f367e35740d +size 2976 diff --git a/marked/Rel-16/44_series/44060/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/44_series/44060/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c2ba5c093434cd72e92452038cc9d7adc1dd239 --- /dev/null +++ b/marked/Rel-16/44_series/44060/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcfce515a1c6f14f696b3e579d0ae19bae3e86b3822f6be3ce6cf95b608fa669 +size 17315 diff --git a/marked/Rel-16/44_series/44060/af01656e21a42c1d856cfb21185cd50e_img.jpg b/marked/Rel-16/44_series/44060/af01656e21a42c1d856cfb21185cd50e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1e8a89baf9f6e59a77db9ea911e220e9456c824 --- /dev/null +++ b/marked/Rel-16/44_series/44060/af01656e21a42c1d856cfb21185cd50e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b012c00cc823aae0846e27d3e9d4c8ce4ec491445e29b94361a4602d7442ed0 +size 86116 diff --git a/marked/Rel-16/44_series/44060/b1bb7109befc781cd95cf07248ad4b57_img.jpg b/marked/Rel-16/44_series/44060/b1bb7109befc781cd95cf07248ad4b57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..949affa4583cc60fd6256be0d6efddba03a8b5ed --- /dev/null +++ b/marked/Rel-16/44_series/44060/b1bb7109befc781cd95cf07248ad4b57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9920e59bce80d8221769acf61819ebba0c7f2e83e7020306b7db32f6ade96061 +size 23645 diff --git a/marked/Rel-16/44_series/44060/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/44_series/44060/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2595e2ca3664eefc7388fe9d442319a212f5dbbb --- /dev/null +++ b/marked/Rel-16/44_series/44060/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:908f20e1d09c08fe5ed713642fbfc26fcf63b52bf7384aec36c99b152be70400 +size 75980 diff --git a/marked/Rel-16/44_series/44060/b6783b3a83a0ade1dd26a3f176399cc2_img.jpg b/marked/Rel-16/44_series/44060/b6783b3a83a0ade1dd26a3f176399cc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5ce276d3cc35a7b551b839be94e7bd70200d3b3 --- /dev/null +++ b/marked/Rel-16/44_series/44060/b6783b3a83a0ade1dd26a3f176399cc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15bc12a98cf83f8534a4b386a43c6d6802c3667c5f8a663e1fc665930013a85a +size 56155 diff --git a/marked/Rel-16/44_series/44060/ba532d6e6b5002f33ff2c93a98ee3d5f_img.jpg b/marked/Rel-16/44_series/44060/ba532d6e6b5002f33ff2c93a98ee3d5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4abf6560620cd43dd3996b0a318acbc0f5b77368 --- /dev/null +++ b/marked/Rel-16/44_series/44060/ba532d6e6b5002f33ff2c93a98ee3d5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9529184ebcbdadc950df4044f720ac3abbf6d220aac5b7932726c705ae48736 +size 114128 diff --git a/marked/Rel-16/44_series/44060/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg b/marked/Rel-16/44_series/44060/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7c8cd224914e0fb4985f7c4d67852c2d148e22e --- /dev/null +++ b/marked/Rel-16/44_series/44060/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5283484a9b68b9d0246bb6841d5721ef72d216ea9c00dff392aca850847a1c8e +size 20659 diff --git a/marked/Rel-16/44_series/44060/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/Rel-16/44_series/44060/c9d8a18a6137ad054b841d7a614afb48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..145d22112b5e310f89b9db026fb03e45f8f689e4 --- /dev/null +++ b/marked/Rel-16/44_series/44060/c9d8a18a6137ad054b841d7a614afb48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:064b46fd28306629a6becd59f0f7b120d304005b8e34c36187233adae3f3e94f +size 27126 diff --git a/marked/Rel-16/44_series/44060/cd30974768c51b92c072e609be79501b_img.jpg b/marked/Rel-16/44_series/44060/cd30974768c51b92c072e609be79501b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..280e2c926b8d9d2534c97fe0c17fa33a3e354c16 --- /dev/null +++ b/marked/Rel-16/44_series/44060/cd30974768c51b92c072e609be79501b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dc06837ff0d025f3ad7c57b88c09dfc4de96d31252a8e04d0d3419c183a984f +size 19403 diff --git a/marked/Rel-16/44_series/44060/d09fda6826ea374ed615c22c3805dd94_img.jpg b/marked/Rel-16/44_series/44060/d09fda6826ea374ed615c22c3805dd94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08ddc3d7e598bbf20773f4fec9a83f2712269050 --- /dev/null +++ b/marked/Rel-16/44_series/44060/d09fda6826ea374ed615c22c3805dd94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2765b14f39536dc8f7f9cfe4140dbc3652aa96f64debbf5e7825f25eed5e1ff4 +size 106610 diff --git a/marked/Rel-16/44_series/44060/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-16/44_series/44060/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..417cf12b889e428c4dc46d8ac65c0b3e0d92c48a --- /dev/null +++ b/marked/Rel-16/44_series/44060/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79a89b87c96738b2d0ddacf33c8ffe5f15e4cfd59cd2d0c06b2ce334be815eae +size 12293 diff --git a/marked/Rel-16/44_series/44060/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-16/44_series/44060/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..503fce126380ab349e9fe72821ee63e466b1a7d0 --- /dev/null +++ b/marked/Rel-16/44_series/44060/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac1d3a8aa1e8c51e039c7f93c2100ffa033b3762037170081aa6eabbde4c5c28 +size 17048 diff --git a/marked/Rel-16/44_series/44060/db395493033edacd83e212049fd55715_img.jpg b/marked/Rel-16/44_series/44060/db395493033edacd83e212049fd55715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70372c8f9ef95f0ff74ebf6d45995c060c15a629 --- /dev/null +++ b/marked/Rel-16/44_series/44060/db395493033edacd83e212049fd55715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feb7dc53288e89a92023ca7e0bf1e22fe9af5e8ae1a7f0ad973ab8a477373bb9 +size 23116 diff --git a/marked/Rel-16/44_series/44060/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-16/44_series/44060/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40a21552790ff64f63bfe2f7887617658ee85b14 --- /dev/null +++ b/marked/Rel-16/44_series/44060/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f313b769b1f688181bb8b4890b7fa291255428e11788bd6c2eb2dad278d9873b +size 16914 diff --git a/marked/Rel-16/44_series/44060/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-16/44_series/44060/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff640abdda63685c93384e57bdaee51cf290b629 --- /dev/null +++ b/marked/Rel-16/44_series/44060/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06a35ee2a49117d8e466a5ada8ffe400ca3b41a4f95052b45f78895a4d6dd954 +size 18091 diff --git a/marked/Rel-16/44_series/44060/dda72b6afeac47479e0746d4eaf6745a_img.jpg b/marked/Rel-16/44_series/44060/dda72b6afeac47479e0746d4eaf6745a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cb74e00e122cfb92b9c03da3cabd73b001081da --- /dev/null +++ b/marked/Rel-16/44_series/44060/dda72b6afeac47479e0746d4eaf6745a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60ca488667b0cb0c09890c956f941ec06c83bf92a1e50f45b7f53a1bc19729db +size 74934 diff --git a/marked/Rel-16/44_series/44060/e04a952ad587547899d15c77183a5b24_img.jpg b/marked/Rel-16/44_series/44060/e04a952ad587547899d15c77183a5b24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37fef10d8273b3585b24a19ae5d684458217b3bb --- /dev/null +++ b/marked/Rel-16/44_series/44060/e04a952ad587547899d15c77183a5b24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81a30ff79041a5a45adaba227148160f55817b2fe1f654cf46029978cb516db8 +size 33633 diff --git a/marked/Rel-16/44_series/44060/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-16/44_series/44060/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..950246439576b636d90348ff90424a1bc8a60d9a --- /dev/null +++ b/marked/Rel-16/44_series/44060/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba93a6c04a07058d7ddc962a0248ce719ba5f95e2f8549808e36981b229276e1 +size 43236 diff --git a/marked/Rel-16/44_series/44060/e4a14961bdc9882e296b25f7ae5f9760_img.jpg b/marked/Rel-16/44_series/44060/e4a14961bdc9882e296b25f7ae5f9760_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4884f6c32790ddeaeaf28db3b346bb29562392da --- /dev/null +++ b/marked/Rel-16/44_series/44060/e4a14961bdc9882e296b25f7ae5f9760_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63524ba0d46ad0b7e4e5f8e497edb0218ce043887ba234089e0157a5937a22e8 +size 19787 diff --git a/marked/Rel-16/44_series/44060/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg b/marked/Rel-16/44_series/44060/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bab39d1df9f992ffd1117e0ca49bedda2b46afab --- /dev/null +++ b/marked/Rel-16/44_series/44060/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:076828e1d4ae6271ceae52c415cff9cd320d02cbee8b83b27f85ba469f0295bd +size 20448 diff --git a/marked/Rel-16/44_series/44060/f20786b603b41e24b5d5899f710b5947_img.jpg b/marked/Rel-16/44_series/44060/f20786b603b41e24b5d5899f710b5947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9272b58f6bac67e3152b2c85a546be67d4eee876 --- /dev/null +++ b/marked/Rel-16/44_series/44060/f20786b603b41e24b5d5899f710b5947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87f731343d6033fbf0e068ba43efb6be93c808b74b5f0f26d68acfd346f3f513 +size 3393 diff --git a/marked/Rel-16/44_series/44060/f2c8124b953b46b53423532cff4903e8_img.jpg b/marked/Rel-16/44_series/44060/f2c8124b953b46b53423532cff4903e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fe3db25fd6c5b75abffef739a2aa09701e492b5 --- /dev/null +++ b/marked/Rel-16/44_series/44060/f2c8124b953b46b53423532cff4903e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9de1b5eb3d2cc858080b111d487daaf159f3583f2157454ea6592bb200ac5f86 +size 19463 diff --git a/marked/Rel-16/44_series/44060/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-16/44_series/44060/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bb1dee5c3dad2de740bb6c8e1f1438dc3e1adcc --- /dev/null +++ b/marked/Rel-16/44_series/44060/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64744e25cd5cff454f802b4990fa4a4797c34bdd7d55bb2adf21db8079373bfc +size 24260 diff --git a/marked/Rel-16/44_series/44060/f609bd3fda53d5be094991a96addbf84_img.jpg b/marked/Rel-16/44_series/44060/f609bd3fda53d5be094991a96addbf84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6450ef23dc1bc8e5a647f2f359f22d5e2938e94 --- /dev/null +++ b/marked/Rel-16/44_series/44060/f609bd3fda53d5be094991a96addbf84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e17beec2fec6faf7eab3da98508ceffb14d156006a0bf378f0dd1ed41734873 +size 37862 diff --git a/marked/Rel-16/44_series/44060/raw.md b/marked/Rel-16/44_series/44060/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ced33d1d56aca13f420151a7460e7cc26896fb00 --- /dev/null +++ b/marked/Rel-16/44_series/44060/raw.md @@ -0,0 +1,30453 @@ +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 19 | +| 1 Scope..... | 20 | +| 1.1 General..... | 20 | +| 1.2 Related documents..... | 20 | +| 1.3 Use of logical control channels..... | 20 | +| 1.4 Use of logical traffic channels..... | 21 | +| 1.5 Conventions..... | 22 | +| 1.6 Restrictions..... | 22 | +| 2 References..... | 22 | +| 3 Definitions, abbreviations and symbols..... | 25 | +| 3.1 Definitions..... | 25 | +| 3.2 Abbreviations..... | 30 | +| 3.3 Symbols..... | 32 | +| 4 Layered overview of radio interface..... | 32 | +| 4.1 Layer services..... | 34 | +| 4.2 Layer functions..... | 34 | +| 4.3 Service primitives..... | 35 | +| 4.4 Services required from lower layers..... | 35 | +| 5 Introduction to the Medium Access Control (MAC) procedures..... | 35 | +| 5.1 General..... | 35 | +| 5.2 Multiplexing principles..... | 36 | +| 5.2.1 Temporary Block Flow..... | 36 | +| 5.2.2 Temporary Flow Identity..... | 37 | +| 5.2.3 Uplink State Flag..... | 38 | +| 5.2.4 Medium Access modes..... | 38 | +| 5.2.4a Multiplexing of GPRS, EGPRS and EGPRS2 capable mobile stations..... | 38 | +| 5.3 Packet idle mode..... | 39 | +| 5.3.1 Broadcast/multicast receive mode..... | 40 | +| 5.4 Packet transfer mode..... | 40 | +| 5.4a Dual transfer mode..... | 41 | +| 5.5 General procedures in packet idle and packet transfer modes..... | 41 | +| 5.5.1 Mobile station side..... | 41 | +| 5.5.0.1 Indication of a selected PLMN using PLMN Index..... | 41 | +| 5.5.0.2 Indication of DCN-ID..... | 42 | +| 5.5.1.1 Cell reselection..... | 42 | +| 5.5.1.1a Network Assisted Cell Change..... | 43 | +| 5.5.1.1a.1 Neighbour Cell System Information Distribution..... | 44 | +| 5.5.1.1a.2 CCN Mode..... | 44 | +| 5.5.1.1b Release of RR connection..... | 44 | +| 5.5.1.1b.1 General..... | 44 | +| 5.5.1.1b.2 Continuation of PBCCH information..... | 44 | +| 5.5.1.1b.3 Continuation of BCCH information..... | 45 | +| 5.5.1.1b.4 Receipt of PSI14 message in dual transfer mode..... | 45 | +| 5.5.1.1b.5 Acquisition of system information for enhanced DTM CS release procedure in dual transfer mode..... | 45 | +| 5.5.1.1c Inter-RAT cell re-selection based on priority information..... | 46 | +| 5.5.1.1c.1 General..... | 46 | +| 5.5.1.1c.2 Common priorities information..... | 47 | +| 5.5.1.1c.3 Provision of individual priorities information..... | 47 | +| 5.5.1.1d (void)..... | 47 | +| 5.5.1.2 System information on PBCCH..... | 47 | +| 5.5.1.2.1 Supervision of PBCCH_CHANGE_MARK and update of PBCCH information..... | 48 | +| 5.5.1.2.2 Replacement of PBCCH..... | 48 | +| 5.5.1.2.3 PSI1 reception failure..... | 49 | +| 5.5.1.3 System information on BCCH..... | 49 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------|----| +| 5.5.1.3.1 | Supervision of BCCH_CHANGE_MARK and update of BCCH information..... | 49 | +| 5.5.1.3.2 | Establishment of PBCCH..... | 50 | +| 5.5.1.3.3 | SI13 reception failure..... | 50 | +| 5.5.1.3a | System information on EC-BCCH..... | 50 | +| 5.5.1.4 | Acquisition of system information on the broadcast channel..... | 50 | +| 5.5.1.4.1 | Consistent sets of system information messages..... | 51 | +| 5.5.1.4.2 | Suspension of operation to receive system information..... | 51 | +| 5.5.1.4.3 | Request for acquisition of system information..... | 52 | +| 5.5.1.5 | Discontinuous reception (DRX)..... | 53 | +| 5.5.1.6 | Page mode procedures on PCCCH..... | 55 | +| 5.5.1.7 | Frequency Parameters..... | 55 | +| 5.5.1.8 | TLLI management..... | 58 | +| 5.5.1.9 | Packet Flow Context (PFC)..... | 58 | +| 5.5.1.10 | Acquisition of E-UTRAN Information on the PACCH..... | 59 | +| 5.5.2 | Network side..... | 60 | +| 5.5.2.1 | System Information broadcasting..... | 60 | +| 5.5.2.1.1 | System information on PBCCH..... | 60 | +| 5.5.2.1.2 | System information on BCCH..... | 60 | +| 5.5.2.1.3 | System information on PACCH (and other logical channels)..... | 61 | +| 5.5.2.1.3a | Rules for (P)SI distribution within Packet Serving Cell Data messages..... | 62 | +| 5.5.2.1.3b | Rules for (P)SI distribution on PACCH of an MBMS radio bearer..... | 62 | +| 5.5.2.1.4 | Consistent sets of system information messages..... | 62 | +| 5.5.2.2 | Paging..... | 63 | +| 5.5.2.3 | Network Assisted Cell Change..... | 64 | +| 5.5.2.4 | Packet Switched Handover..... | 64 | +| 5.6 | Measurement reports..... | 64 | +| 5.6.0 | General..... | 64 | +| 5.6.1 | Network Control (NC) measurement reporting..... | 65 | +| 5.6.2 | (void)..... | 66 | +| 5.6.3 | Additional measurement and reporting parameters..... | 66 | +| 5.6.3.1 | Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell description..... | 66 | +| 5.6.3.1a | Deriving the E-UTRAN Neighbour Cell list from the Repeated E-UTRAN Neighbour Cell information..... | 67 | +| 5.6.3.2 | Deriving BA(GPRS) and the GSM Neighbour Cell list..... | 68 | +| 5.6.3.3 | Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list..... | 69 | +| 5.6.3.4 | GPRS Real Time Differences..... | 69 | +| 5.6.3.5 | GPRS Report Priority Descriptions..... | 70 | +| 5.6.3.6 | GPRS Measurement Parameters and GPRS 3G Measurement Parameters..... | 70 | +| 5.6.3.6a | GPRS E-UTRAN Measurement Parameters..... | 70 | +| 5.6.3.7 | The GPRS 3G Cell Reselection list..... | 71 | +| 5.6.3.7a | (void)..... | 71 | +| 5.6.3.7b | The 3G Frequency list..... | 71 | +| 5.6.3.8 | Closed Subscriber Group Information..... | 71 | +| 5.6.3.9 | Reporting of CSG Cells and Hybrid Cells..... | 72 | +| 5.6.4 | Measurement reporting in broadcast/multicast receive mode..... | 73 | +| 5.7 | Dual transfer mode enhancements..... | 74 | +| 5.8 | DTM Handover..... | 74 | +| 5.9 | Downlink Dual Carrier..... | 74 | +| 5.10 | ETWS Primary Notification..... | 74 | +| 5.11 | Enhanced Multiplexing for Single TBF..... | 74 | +| 5.12 | Enhanced Multiplexing for a Single RLC Entity..... | 75 | +| 5.13 | Downlink Multi Carrier..... | 76 | +| 6 | Paging procedures..... | 77 | +| 6.1 | Paging procedure for RR connection establishment..... | 77 | +| 6.1.1 | Paging initiation using paging subchannel on CCCH..... | 77 | +| 6.1.2 | Paging initiation using paging subchannel on PCCCH..... | 77 | +| 6.1.3 | Paging initiation using PACCH..... | 78 | +| 6.1.4 | Paging response..... | 78 | +| 6.2 | Paging procedure for downlink packet transfer..... | 79 | +| 6.2.1 | Paging procedure using paging subchannel on CCCH..... | 79 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------|-----| +| 6.2.2 | Paging using paging subchannel on PCCCH..... | 79 | +| 6.2.3 | Paging response..... | 79 | +| 6.2.4 | Paging procedure using paging subchannel on EC-CCCH..... | 79 | +| 6.3 | Paging Procedures for MBMS Notification..... | 79 | +| 6.3.1 | Notification to mobile station in packet idle mode..... | 79 | +| 6.3.1.1 | General..... | 79 | +| 6.3.1.2 | Paging procedure for MBMS notification using paging subchannel on CCCH..... | 80 | +| 6.3.1.3 | Paging procedure for MBMS notification using paging subchannel on PCCCH..... | 80 | +| 6.3.1.3.1 | General..... | 80 | +| 6.3.1.3.2 | MBMS pre-notification..... | 80 | +| 6.3.1.3.3 | MBMS notification..... | 81 | +| 6.3.1.3a | Paging procedure for MBMS notification using PACCH..... | 81 | +| 6.3.1.4 | Response to MBMS Notification..... | 82 | +| 6.3.2 | Notification to mobile station in packet transfer mode or in dual transfer mode..... | 82 | +| 6.3.2.1 | General..... | 82 | +| 6.3.2.2 | MBMS Notification using the PACCH..... | 82 | +| 6.3.2.3 | Response to MBMS Notification received on PACCH..... | 83 | +| 6.4 | Paging Procedure for ETWS Primary Notification delivery..... | 83 | +| 6.4.1 | General..... | 83 | +| 6.4.2 | ETWS Primary Notification delivery using paging subchannel on CCCH..... | 83 | +| 6.4.3 | ETWS Primary Notification delivery using paging subchannel on PCCCH..... | 83 | +| 6.4.4 | Reception of ETWS Primary Notification message..... | 83 | +| 7 | Medium Access Control (MAC) procedures on PCCCH..... | 84 | +| 7.0 | General..... | 84 | +| 7.0a | Support of multiple TBF procedures..... | 84 | +| 7.0b | (void)..... | 85 | +| 7.1 | TBF establishment initiated by the mobile station on PCCCH..... | 85 | +| 7.1.1 | Permission to access the network..... | 85 | +| 7.1.2 | Initiation of a TBF establishment..... | 86 | +| 7.1.2.1 | Initiation of the packet access procedure..... | 86 | +| 7.1.2.1.1 | Access persistence control on PRACH..... | 87 | +| 7.1.2.2 | Packet assignment procedure..... | 89 | +| 7.1.2.2.1 | On receipt of a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message..... | 89 | +| 7.1.2.2.1a | Acquisition of MS Radio Access Capability information within EGPRS TBF establishment procedure..... | 90 | +| 7.1.2.2.2 | Packet access queuing notification procedure..... | 91 | +| 7.1.2.2.3 | Packet polling procedure..... | 91 | +| 7.1.2.2.4 | Packet access reject procedure..... | 91 | +| 7.1.2.3 | Contention resolution at one phase access..... | 92 | +| 7.1.2.3a | RLC/MAC procedures during contention resolution..... | 93 | +| 7.1.2.4 | One phase packet access completion..... | 93 | +| 7.1.2.5 | Timing Advance..... | 93 | +| 7.1.2.6 | PFC procedure at one phase access..... | 94 | +| 7.1.3 | TBF establishment using two phase access..... | 94 | +| 7.1.3.1 | Initiation of the Packet resource request procedure..... | 94 | +| 7.1.3.2 | Packet resource assignment for uplink procedure..... | 95 | +| 7.1.3.2.1 | On receipt of a PACKET RESOURCE REQUEST message..... | 96 | +| 7.1.3.3 | Contention resolution at two phase access..... | 97 | +| 7.1.3.4 | Two phase packet access completion..... | 97 | +| 7.1.3.5 | Timing Advance..... | 98 | +| 7.1.3.6 | RTTI Assignments..... | 98 | +| 7.1.3.7 | MTTI Configurations..... | 99 | +| 7.1.4 | Abnormal cases..... | 99 | +| 7.2 | TBF establishment initiated by the network on PCCCH..... | 100 | +| 7.2.1 | Entering the packet transfer mode..... | 100 | +| 7.2.1.1 | Packet downlink assignment procedure..... | 101 | +| 7.2.1.2 | Packet downlink assignment procedure completion..... | 102 | +| 7.2.1.3 | Packet polling procedure..... | 102 | +| 7.2.2 | Abnormal cases..... | 102 | +| 7.3 | Procedure for measurement report sending in packet idle mode..... | 102 | + +| | | | +|-------------|---------------------------------------------------------------------------------------------|-----| +| 7.3.1 | Measurement report sending procedure initiated on PCCCH..... | 103 | +| 7.3.1.1 | On receipt of a PACKET CHANNEL REQUEST message..... | 103 | +| 7.3.1.2 | On receipt of a PACKET UPLINK ASSIGNMENT message..... | 103 | +| 7.3.1.3 | On receipt of a PACKET ACCESS REJECT message..... | 103 | +| 7.3.1.4 | Abnormal cases..... | 104 | +| 7.3.2 | Measurement report sending procedure initiated on CCCH..... | 104 | +| 7.4 | Cell Change Order procedures in Packet Idle mode..... | 104 | +| 7.4.1 | Cell Change Order procedure initiated on PCCCH..... | 104 | +| 7.4.2 | Cell Change Order procedure initiated on CCCH..... | 105 | +| 7.5 | Measurement Order procedures in Packet Idle mode..... | 105 | +| 7.5.1 | Measurement Order procedures initiated on PCCCH..... | 106 | +| 7.5.2 | Measurement Order procedures initiated on CCCH..... | 106 | +| 7.6 | Packet Pause procedure..... | 106 | +| 7.6.1 | Packet pause procedure initiated on PCCCH..... | 106 | +| 7.6.1.1 | On receipt of a PACKET CHANNEL REQUEST message..... | 106 | +| 7.6.1.2 | On receipt of a PACKET UPLINK ASSIGNMENT message..... | 107 | +| 7.6.1.3 | On receipt of a PACKET ACCESS REJECT message..... | 107 | +| 7.6.1.4 | Abnormal cases..... | 107 | +| 7.6.2 | Packet pause procedure initiated on CCCH..... | 107 | +| 7.7 | MBMS packet access and establishment procedures..... | 107 | +| 7.7.1 | MBMS packet access procedure..... | 107 | +| 7.7.1.1 | General..... | 107 | +| 7.7.1.2 | MBMS packet access procedure on PCCCH..... | 108 | +| 7.7.1.2.0 | Initiation of the MBMS packet access procedure..... | 108 | +| 7.7.1.2.1 | On receipt of a PACKET CHANNEL REQUEST message..... | 108 | +| 7.7.1.2.2 | On receipt of a PACKET UPLINK ASSIGNMENT message..... | 108 | +| 7.7.1.2.3 | On receipt of a PACKET ACCESS REJECT message..... | 109 | +| 7.7.1.2.4 | On receipt of an MBMS ASSIGNMENT message..... | 109 | +| 7.7.1.2.5 | Abnormal cases..... | 109 | +| 7.7.1.3 | MBMS packet access procedure on CCCH..... | 109 | +| 7.7.1.4 | MBMS packet access procedure on MPRACH..... | 109 | +| 7.7.1.4.1 | Initiation of the MBMS packet access procedure on MPRACH..... | 109 | +| 7.7.1.4.1.1 | Access persistence control on MPRACH..... | 109 | +| 7.7.1.4.2 | On receipt of an MPRACH PACKET CHANNEL REQUEST..... | 110 | +| 7.7.1.4.3 | On receipt of a PACKET ACCESS REJECT message..... | 111 | +| 7.7.1.4.4 | On receipt of a PACKET UPLINK ASSIGNMENT message..... | 111 | +| 7.7.1.4.5 | On receipt of an MBMS ASSIGNMENT message..... | 112 | +| 7.7.2 | Establishment of MBMS bearer..... | 112 | +| 7.7.2.1 | General..... | 112 | +| 7.7.2.2 | On receipt of an MBMS ASSIGNMENT message..... | 112 | +| 7.7.2.3 | Abnormal cases..... | 113 | +| 7.7.2.4 | MBMS address assignment procedure..... | 113 | +| 7.7.3 | MBMS Neighbour Cell Information Distribution..... | 114 | +| 7a | Medium Access Control (MAC) procedures for EC-GSM-IoT on (EC-)CCCH..... | 115 | +| 7a.1 | General..... | 115 | +| 7a.2 | TBF establishment initiated by the mobile station for EC-GSM-IoT on (EC-)CCCH..... | 115 | +| 7a.2.1 | Contention Resolution..... | 115 | +| 7a.2.1.1 | Contention resolution at packet access procedure using Access Burst procedure..... | 115 | +| 7a.2.1.2 | Contention resolution at packet access procedure using Enhanced Access Burst procedure..... | 117 | +| 7a.2.2 | RLC/MAC procedures during contention resolution..... | 118 | +| 7a.2.3 | Timing Advance..... | 119 | +| 7a.2.4 | Abnormal cases..... | 119 | +| 7a.3 | TBF establishment initiated by the network for EC-GSM-IoT on EC-CCCH..... | 119 | +| 7a.3.1 | Timing Advance..... | 119 | +| 7a.3.2 | Packet polling procedure..... | 120 | +| 8 | Medium Access Control (MAC) Procedures in Packet Transfer Mode..... | 120 | +| 8.0 | General..... | 120 | +| 8.1 | Transfer of RLC data blocks..... | 120 | +| 8.1.0 | Medium access mode..... | 120 | +| 8.1.1 | Uplink RLC data block transfer..... | 121 | + +| | | | +|--------------|---------------------------------------------------------------------------------------|-----| +| 8.1.1.1 | Dynamic allocation uplink RLC data block transfer..... | 128 | +| 8.1.1.1.1 | PACCH operation..... | 129 | +| 8.1.1.1.2 | Resource Reallocation for Uplink..... | 130 | +| 8.1.1.1.2.1 | Abnormal cases..... | 132 | +| 8.1.1.1.3 | Establishment of Downlink TBF..... | 133 | +| 8.1.1.1.3.1 | Abnormal cases..... | 135 | +| 8.1.1.2 | Extended Dynamic Allocation uplink RLC data block transfer..... | 136 | +| 8.1.1.2.1 | Uplink PDCH Allocation..... | 137 | +| 8.1.1.2.2 | PACCH operation..... | 139 | +| 8.1.1.2.3 | Neighbour cell power measurements..... | 140 | +| 8.1.1.2.4 | Shifted USF operation..... | 140 | +| 8.1.1.3 | (void)..... | 140 | +| 8.1.1.3a | Exclusive allocation RLC data block transfer..... | 140 | +| 8.1.1.3a.1 | General..... | 140 | +| 8.1.1.3a.2 | Radio link failure..... | 141 | +| 8.1.1.3a.3 | (void)..... | 141 | +| 8.1.1.3a.4 | PACCH operation..... | 141 | +| 8.1.1.3a.5 | Resource Reallocation for Uplink..... | 142 | +| 8.1.1.3a.5.1 | General..... | 142 | +| 8.1.1.3a.5.2 | Change of service demand..... | 142 | +| 8.1.1.3a.5.3 | Reallocation of radio resources for an uplink TBF..... | 142 | +| 8.1.1.3a.5.4 | Rejection of new service demand..... | 143 | +| 8.1.1.3a.5.5 | Abnormal cases..... | 143 | +| 8.1.1.3a.6 | Establishment of Downlink TBF..... | 143 | +| 8.1.1.3a.6.1 | General..... | 143 | +| 8.1.1.3a.6.2 | Abnormal cases..... | 144 | +| 8.1.1.3b | Fixed Uplink Allocation RLC data block transfer..... | 144 | +| 8.1.1.3b.1 | EC-PACCH operation..... | 145 | +| 8.1.1.3b.2 | Prolonged Resources for Uplink transmission..... | 146 | +| 8.1.1.3b.3 | Abnormal cases..... | 146 | +| 8.1.1.3b.4 | Establishment of Downlink TBF..... | 146 | +| 8.1.1.4 | Network initiated release of uplink TBF..... | 146 | +| 8.1.1.5 | Abnormal cases..... | 147 | +| 8.1.1.6 | Change of RLC mode in extended uplink TBF mode..... | 147 | +| 8.1.1.6.1 | General..... | 147 | +| 8.1.1.6.2 | Change of RLC mode..... | 147 | +| 8.1.1.6.3 | Abnormal cases..... | 148 | +| 8.1.1.7 | Change of EGPRS level..... | 148 | +| 8.1.1.7.1 | Change of EGPRS level for downlink TBFs..... | 148 | +| 8.1.1.7.2 | Change of EGPRS level for uplink TBFs..... | 148 | +| 8.1.2 | Downlink RLC data block transfer..... | 151 | +| 8.1.2.1 | Downlink RLC data block transfer..... | 153 | +| 8.1.2.1.1 | Abnormal cases..... | 153 | +| 8.1.2.2 | Polling for Packet Downlink Ack/Nack..... | 155 | +| 8.1.2.2a | Polling for EC Packet Downlink Ack/Nack or EC Packet Downlink Ack/Nack Higher CC..... | 157 | +| 8.1.2.3 | (void)..... | 158 | +| 8.1.2.4 | Resource Reassignment for Downlink..... | 158 | +| 8.1.2.4.1 | Abnormal cases..... | 158 | +| 8.1.2.5 | Establishment of uplink TBF..... | 159 | +| 8.1.2.5.1 | Abnormal cases..... | 162 | +| 8.1.2.6 | (void)..... | 163 | +| 8.1.2.7 | (void)..... | 163 | +| 8.1.2.8 | Network initiated abnormal release of downlink TBF..... | 163 | +| 8.1.3 | (void)..... | 163 | +| 8.1.4 | RLC data block transfer during an MBMS radio bearer..... | 163 | +| 8.1.4.0 | General..... | 163 | +| 8.1.4.1 | RLC data block transfer during an MBMS radio bearer..... | 163 | +| 8.1.4.2 | Polling for MBMS Downlink Ack/Nack..... | 164 | +| 8.1.4.3 | Reconfiguration of an MBMS radio bearer..... | 164 | +| 8.1.4.3.1 | Individual reassignment of an MS_ID..... | 164 | +| 8.1.4.3.2 | Reassignment of the MBMS Bearer Identity..... | 165 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------------------|-----| +| 8.1.4.3.3 | Resource reassignment for an MBMS radio bearer..... | 166 | +| 8.1.4.4 | Network initiated release of an MBMS radio bearer..... | 167 | +| 8.1.4.5 | Suspension/Resumption of the reception of an MBMS radio bearer..... | 168 | +| 8.1.5 | Multiple MBMS radio bearers..... | 168 | +| 8.1.5.1 | Transmission of multiple MBMS radio bearers..... | 168 | +| 8.1.5.2 | Reception of multiple MBMS radio bearers..... | 168 | +| 8.1.5.2.1 | General..... | 168 | +| 8.1.5.2.2 | Reception of notification of lower priority MBMS session whilst receiving higher priority MBMS session(s)..... | 169 | +| 8.1.5.2.3 | Reception of assignment of lower priority MBMS session whilst receiving higher priority MBMS session(s)..... | 169 | +| 8.1.5.2.4 | Reception of notification of higher priority MBMS session whilst receiving lower priority MBMS session(s)..... | 169 | +| 8.1.5.2.5 | Reception of assignment of higher priority MBMS session whilst receiving lower priority MBMS session(s)..... | 169 | +| 8.1.5.2.6 | Cell change whilst receiving multiple MBMS sessions (with MBMS supported by the network in the target cell)..... | 169 | +| 8.1.5.2.7 | Resource reassignment for at least one of the received MBMS radio bearers..... | 170 | +| 8.1.6 | MBMS reception resumption after cell reselection..... | 170 | +| 8.1.6.1 | Default behaviour..... | 170 | +| 8.1.6.2 | Fast reception resumption..... | 170 | +| 8.1.7 | Packet Application Information..... | 171 | +| 8.1.7.1 | General..... | 171 | +| 8.1.7.2 | Earthquake and Tsunami Warning System (ETWS)..... | 171 | +| 8.1.8 | Dynamic Timeslot Reduction..... | 171 | +| 8.1.8.1 | General..... | 171 | +| 8.1.8.2 | DTR Activation..... | 171 | +| 8.1.8.3 | Resumption to normal operation..... | 172 | +| 8.2 | Packet PDCH Release..... | 173 | +| 8.3 | Procedure for measurement report sending in Packet Transfer mode..... | 173 | +| 8.4 | Network controlled cell reselection procedure..... | 174 | +| 8.4.1 | Network controlled cell reselection completion..... | 174 | +| 8.4.1b | (void)..... | 175 | +| 8.4.2 | Abnormal cases..... | 175 | +| 8.5 | Measurement Order procedures in Packet Transfer mode..... | 176 | +| 8.6 | PACKET CONTROL ACKNOWLEDGEMENT..... | 176 | +| 8.7 | Abnormal cases..... | 176 | +| 8.7.0 | General..... | 176 | +| 8.7.1 | Abnormal release without retry..... | 177 | +| 8.7.2 | Abnormal release with access retry..... | 178 | +| 8.7.3 | Abnormal release with system information..... | 178 | +| 8.7.4 | Abnormal release with RR connection establishment retry..... | 178 | +| 8.8 | Network Assisted Cell Change procedures..... | 178 | +| 8.8.1 | Neighbour Cell System Information Distribution..... | 178 | +| 8.8.2 | CCN setting procedure..... | 180 | +| 8.8.2a | CCN support description..... | 180 | +| 8.8.3 | Cell Change Notification procedure..... | 181 | +| 8.9 | RR connection establishment in packet transfer mode..... | 183 | +| 8.9.0 | General..... | 183 | +| 8.9.1 | Initiation..... | 183 | +| 8.9.1.1 | Initiation by the mobile station..... | 183 | +| 8.9.1.1.1 | Transmission of the PACKET CS REQUEST message..... | 183 | +| 8.9.1.1.2 | Answer from the network..... | 184 | +| 8.9.1.2 | Initiation by the network..... | 184 | +| 8.9.2 | Assignment..... | 184 | +| 8.9.2.1 | Assignment of both dedicated and packet resource..... | 184 | +| 8.9.2.2 | Assignment of dedicated resource only..... | 185 | +| 8.9.2.3 | Rejection of the mobile station request..... | 185 | +| 8.9.3 | (void)..... | 185 | +| 8.9.4 | Abnormal cases..... | 185 | +| 8.9.4.1 | RR connection establishment initiated by the mobile station..... | 185 | + +| | | | +|------------|---------------------------------------------------------------------|-----| +| 8.9.4.2 | RR connection establishment initiated by the network..... | 186 | +| 8.10 | Packet Switched Handover procedure..... | 186 | +| 8.10.1 | General..... | 186 | +| 8.10.2 | Neighbour Cell System Information Distribution..... | 187 | +| 8.10.3 | PS Handover at the network side..... | 187 | +| 8.10.3.1 | Initiation of PS Handover Procedure..... | 187 | +| 8.10.3.2 | A/Gb to A/Gb PS Handover..... | 187 | +| 8.10.3.3 | GERAN A/Gb to Iu/E-UTRAN PS Handover..... | 189 | +| 8.10.3.4 | Iu/E-UTRAN to GERAN A/Gb PS Handover..... | 189 | +| 8.10.3.5 | A/Gb to GAN PS Handover..... | 189 | +| 8.10.3.6 | GAN to A/Gb PS Handover..... | 189 | +| 8.10.4 | PS Handover at the mobile station side..... | 190 | +| 8.10.4.1 | A/Gb to A/Gb PS Handover..... | 190 | +| 8.10.4.2 | A/Gb to Iu/E-UTRAN PS Handover..... | 191 | +| 8.10.4.3 | Iu/E-UTRAN to A/Gb PS Handover..... | 191 | +| 8.10.4.4 | Physical channel establishment..... | 191 | +| 8.10.4.4.1 | General..... | 191 | +| 8.10.4.4.2 | Synchronized cell case..... | 192 | +| 8.10.4.4.3 | Pre-synchronized cell case..... | 192 | +| 8.10.4.4.4 | Non synchronized cell case..... | 192 | +| 8.10.4.5 | A/Gb to GAN PS Handover..... | 192 | +| 8.10.4.6 | GAN to A/Gb PS Handover..... | 193 | +| 8.10.5 | Abnormal Cases..... | 193 | +| 8.10.5.1 | MS Behaviour for A/Gb to A/Gb PS Handover..... | 193 | +| 8.10.5.2 | MS Behaviour for A/Gb to Iu/E-UTRAN PS Handover..... | 194 | +| 8.10.5.3 | MS Behaviour for Iu/E-UTRAN to A/Gb PS Handover..... | 194 | +| 8.10.5.4 | BSS Behaviour for PS Handover from A/Gb..... | 195 | +| 8.10.5.5 | BSS Behaviour for PS Handover to A/Gb..... | 195 | +| 8.10.5.6 | MS Behaviour for A/Gb to GAN PS Handover..... | 195 | +| 8.10.5.7 | MS Behaviour for GAN to A/Gb PS Handover..... | 195 | +| 9 | Radio Link Control (RLC) procedures in packet transfer mode..... | 196 | +| 9.0 | General..... | 196 | +| 9.1 | Procedures and parameters for peer-to-peer operation..... | 197 | +| 9.1.1 | Send state variable V(S)..... | 197 | +| 9.1.1a | Control send state variable V(CS)..... | 197 | +| 9.1.2 | Acknowledge state variable V(A)..... | 198 | +| 9.1.3 | Acknowledge state array V(B)..... | 198 | +| 9.1.3.1 | Acknowledge state array V(B) for GPRS TBF Mode..... | 198 | +| 9.1.3.2 | Acknowledge State Array V(B) for EGPRS TBF Mode..... | 199 | +| 9.1.3.2.1 | EGPRS TBF running in RLC acknowledged mode..... | 199 | +| 9.1.3.2.2 | EGPRS TBF running in RLC non-persistent mode..... | 200 | +| 9.1.3.3 | Acknowledge State Array V(B) for MBMS Bearers..... | 201 | +| 9.1.3.4 | Acknowledge State Array V(B) for EC TBF Mode..... | 201 | +| 9.1.4 | Block sequence number BSN..... | 201 | +| 9.1.4.1 | Block sequence number BSN for GPRS TBF..... | 201 | +| 9.1.4.2 | Block sequence number BSN for EGPRS TBF..... | 202 | +| 9.1.4.3 | Block sequence number BSN for EC TBF..... | 202 | +| 9.1.4a | Reduced Block Sequence Number RBSN..... | 202 | +| 9.1.4b | Reduced Block Sequence Number extension RBSNe..... | 202 | +| 9.1.5 | Receive state variable V(R)..... | 202 | +| 9.1.6 | Receive window state variable V(Q)..... | 202 | +| 9.1.6.1 | General..... | 202 | +| 9.1.6.2 | RLC acknowledged mode..... | 202 | +| 9.1.6.3 | RLC unacknowledged mode..... | 203 | +| 9.1.6.4 | RLC non-persistent mode..... | 203 | +| 9.1.7 | Receive state array V(N)..... | 203 | +| 9.1.7.1 | Receive state array V(N) in GPRS TBF..... | 203 | +| 9.1.7.2 | Receive state array V(N) in EGPRS TBF..... | 203 | +| 9.1.7.3 | Receive state array V(N) in TBF with FANR activated..... | 204 | +| 9.1.7.4 | Receive state array V(N) in EC TBF..... | 204 | +| 9.1.8 | Starting sequence number (SSN) and received block bitmap (RBB)..... | 204 | + +| | | | +|------------|----------------------------------------------------------------------------------|-----| +| 9.1.8.1 | Starting sequence number (SSN) and received block bitmap (RBB) in GPRS TBF..... | 204 | +| 9.1.8.2 | Starting sequence number (SSN) and received block bitmap (RBB) in EGPRS TBF..... | 205 | +| 9.1.8.2.1 | Extended Polling..... | 206 | +| 9.1.8.2.2 | Determination of SSN..... | 208 | +| 9.1.8.2.2a | Determination of ShortSSN and SSN in the Piggy-backed Ack/Nack field..... | 210 | +| 9.1.8.2.3 | Generation of the bitmap..... | 210 | +| 9.1.8.2.4 | Interpretation of the bitmap..... | 212 | +| 9.1.8.3 | Starting sequence number (SSN) and received block bitmap (RBB) in EC TBF..... | 213 | +| 9.1.9 | Window Size..... | 213 | +| 9.1.9.1 | GPRS..... | 213 | +| 9.1.9.2 | EGPRS..... | 213 | +| 9.1.9.2a | EC-GSM-IoT..... | 216 | +| 9.1.9.3 | RLC buffer..... | 216 | +| 9.1.10 | Compression..... | 216 | +| 9.1.11 | Segmentation of upper layer PDUs into RLC data units..... | 219 | +| 9.1.12 | Re-assembly of upper layer PDUs from RLC data units..... | 220 | +| 9.1.12a | Segmentation of RLC/MAC control messages into RLC/MAC control blocks..... | 222 | +| 9.1.12b | Re-assembly of RLC/MAC control messages from RLC/MAC control blocks..... | 222 | +| 9.1.13 | Priority of upper layer PDUs..... | 223 | +| 9.1.14 | Fast Ack/Nack Reporting..... | 223 | +| 9.1.14.1 | General..... | 223 | +| 9.1.14.2 | Polled Fast Ack/Nack Reporting..... | 224 | +| 9.1.14.3 | Event-based Fast Ack/Nack Reporting..... | 224 | +| 9.1.15 | Time-based encoding of the Piggy-backed Ack/Nack field..... | 225 | +| 9.1.15.1 | Generation of the bitmap..... | 225 | +| 9.1.15.2 | Interpretation of the bitmap..... | 226 | +| 9.2 | Operation during RLC/MAC control message transfer..... | 226 | +| 9.3 | Operation during RLC data block transfer..... | 227 | +| 9.3.0 | General..... | 227 | +| 9.3.1 | Countdown procedure..... | 228 | +| 9.3.1.1 | General..... | 228 | +| 9.3.1.2 | Non-extended uplink TBF mode..... | 229 | +| 9.3.1.3 | Extended uplink TBF mode..... | 229 | +| 9.3.1.4 | End of uplink EC TBF..... | 229 | +| 9.3.1a | Delayed release of downlink Temporary Block Flow..... | 230 | +| 9.3.1b | Extended uplink TBF mode..... | 231 | +| 9.3.1b.1 | Application..... | 231 | +| 9.3.1b.2 | Operation of uplink TBF in extended uplink TBF mode..... | 231 | +| 9.3.2 | Acknowledged mode operation..... | 232 | +| 9.3.2.0 | General..... | 232 | +| 9.3.2.1 | Additional functionality in acknowledged EGPRS TBF Mode..... | 232 | +| 9.3.2.1a | Additional functionality in acknowledged EC TBF Mode..... | 233 | +| 9.3.2.2 | Establishment of Temporary Block Flow..... | 235 | +| 9.3.2.3 | Operation of uplink Temporary Block Flow..... | 235 | +| 9.3.2.4 | Release of uplink Temporary Block Flow..... | 236 | +| 9.3.2.4.1 | General..... | 236 | +| 9.3.2.4.2 | Non-extended uplink TBF mode..... | 236 | +| 9.3.2.4.3 | Release of uplink EC TBF..... | 237 | +| 9.3.2.5 | Operation of downlink Temporary Block Flow..... | 238 | +| 9.3.2.6 | Release of downlink Temporary Block Flow..... | 239 | +| 9.3.3 | Unacknowledged mode operation..... | 241 | +| 9.3.3.0 | General..... | 241 | +| 9.3.3.1 | Establishment of Temporary Block Flow..... | 241 | +| 9.3.3.2 | Operation of uplink Temporary Block Flow..... | 241 | +| 9.3.3.3 | Release of uplink Temporary Block Flow..... | 241 | +| 9.3.3.3.1 | General..... | 241 | +| 9.3.3.3.2 | Non-extended uplink TBF mode..... | 242 | +| 9.3.3.4 | Operation of downlink Temporary Block Flow..... | 243 | +| 9.3.3.5 | Release of downlink Temporary Block Flow..... | 243 | +| 9.3.4 | Non-persistent mode operation..... | 244 | +| 9.3.4.0 | General..... | 244 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 9.3.4.1 | Operation during an MBMS bearer..... | 245 | +| 9.3.4.2 | Release of an MBMS radio bearer..... | 245 | +| 9.3.4.3 | Operation during an EGPRS TBF..... | 245 | +| 9.4 | Abnormal release cases..... | 245 | +| 9.4.1 | Abnormal release with access retry..... | 245 | +| 9.4.2 | Abnormal release with cell reselection..... | 245 | +| 9.5 | Uplink TBF release in extended uplink TBF mode..... | 245 | +| 10 | RLC/MAC block structure..... | 247 | +| 10.0a | RLC/MAC block structure..... | 247 | +| 10.0a.1 | GPRS RLC/MAC block for data transfer..... | 247 | +| 10.0a.2 | EGPRS and EC-GSM-IoT RLC/MAC block for data transfer..... | 247 | +| 10.0a.3 | RLC/MAC block for control message transfer..... | 249 | +| 10.0b | RLC/MAC block format conventions..... | 249 | +| 10.0b.1 | Numbering convention..... | 249 | +| 10.0b.2 | Assembling conventions..... | 249 | +| 10.0b.2.1 | Assembling convention for GPRS RLC data blocks and RLC/MAC control blocks, 11-bit and 8-bit control messages..... | 249 | +| 10.0b.2.2 | Assembling convention for EGPRS and EC-GSM-IoT RLC data blocks..... | 250 | +| 10.0b.3 | Field mapping conventions..... | 250 | +| 10.0b.3.1 | Field mapping convention for GPRS RLC data blocks, CS-1 or CS-3 encoded RLC/MAC control blocks, EC-PACCH/D and EC-PACCH/U, 11-bit and 8-bit control messages..... | 250 | +| 10.0b.3.2 | Field mapping convention for EGPRS and EC-GSM-IoT RLC data blocks and MCS-0 encoded RLC/MAC control blocks..... | 250 | +| 10.1 | Spare bits..... | 251 | +| 10.2 | GPRS RLC data blocks..... | 251 | +| 10.2.1 | Downlink RLC data block..... | 251 | +| 10.2.2 | Uplink RLC data block..... | 252 | +| 10.3 | RLC/MAC control blocks..... | 252 | +| 10.3.1 | Downlink RLC/MAC control block..... | 253 | +| 10.3.1.1 | Blocks encoded using CS-1..... | 253 | +| 10.3.1.2 | Blocks encoded using MCS-0..... | 253 | +| 10.3.1.3 | Blocks encoded for EC-PACCH/D..... | 254 | +| 10.3.2 | Uplink RLC/MAC control block..... | 254 | +| 10.3a | EGPRS and EC-GSM-IoT RLC data blocks and RLC/MAC headers..... | 255 | +| 10.3a.0 | General..... | 255 | +| 10.3a.1 | Downlink RLC data block..... | 258 | +| 10.3a.1.1 | EGPRS downlink RLC data block..... | 258 | +| 10.3a.1.2 | EC-GSM-IoT downlink RLC data block..... | 259 | +| 10.3a.2 | Uplink RLC data block..... | 259 | +| 10.3a.2.1 | EGPRS Uplink RLC data block..... | 259 | +| 10.3a.2.2 | EC-GSM-IoT Uplink RLC data block..... | 261 | +| 10.3a.3 | EGPRS and EC-GSM-IoT Downlink RLC/MAC header..... | 263 | +| 10.3a.3.1 | Header type 1: header for MCS-7, MCS-8 and MCS-9..... | 263 | +| 10.3a.3.2 | Header type 2: header for MCS-6, MCS-5, DAS-5, DAS-6 and DAS-7..... | 264 | +| 10.3a.3.3 | Header type 3: header for MCS-4, MCS-3, MCS-2, MCS-1 and MCS-0 case..... | 265 | +| 10.3a.3.4 | Header type 4: header for DAS-8 and DAS-9..... | 266 | +| 10.3a.3.5 | Header type 5: header for DAS-11 and DAS-12..... | 267 | +| 10.3a.3.6 | Header type 6: header for DBS-5 and DBS-6..... | 268 | +| 10.3a.3.7 | Header type 7: header for DBS-7 and DBS-8..... | 268 | +| 10.3a.3.8 | Header type 8: header for DBS-9 and DBS-10..... | 268 | +| 10.3a.3.9 | Header type 9: header for DBS-11 and DBS-12..... | 268 | +| 10.3a.3.10 | Header type 10: header for DAS-10..... | 269 | +| 10.3a.4 | EGPRS and EC-GSM-IoT Uplink RLC/MAC header..... | 269 | +| 10.3a.4.1 | Header type 1: header for MCS-7, MCS-8 and MCS-9..... | 269 | +| 10.3a.4.2 | Header type 2: header for MCS-6 and MCS-5..... | 270 | +| 10.3a.4.3 | Header type 3 : header for MCS-4, MCS-3, MCS-2 and MCS-1..... | 271 | +| 10.3a.4.4 | Header type 4: header for UAS-7, UAS-8 and UAS-9..... | 271 | +| 10.3a.4.5 | Header type 5: header for UAS-10 and UAS-11..... | 272 | +| 10.3a.4.6 | Header type 6: header for UBS-5 and UBS-6..... | 272 | +| 10.3a.4.7 | Header type 7: header for UBS-7 and UBS-8..... | 272 | +| 10.3a.4.8 | Header type 8: header for UBS-9 and UBS-10..... | 273 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------|-----| +| 10.3a.4.9 | Header type 9: header for UBS-11 and UBS-12..... | 273 | +| 10.3a.4.10 | Header type 4: header for MCS-1'..... | 273 | +| 10.3a.5 | Piggy-backed Ack/Nack field (SSN-based)..... | 273 | +| 10.3a.6 | Piggy-backed Ack/Nack field (Time-based)..... | 274 | +| 10.4 | Header fields..... | 274 | +| 10.4.1 | Uplink state flag (USF) field..... | 274 | +| 10.4.2 | Retry (R) bit..... | 275 | +| 10.4.3 | Stall indicator (SI) bit..... | 275 | +| 10.4.4 | Supplementary/Polling (S/P) Bit..... | 275 | +| 10.4.4a | EGPRS Supplementary/Polling (ES/P) Field..... | 275 | +| 10.4.4b | Combined EGPRS Supplementary/Polling (CES/P) Field..... | 276 | +| 10.4.4c | EC-GSM-IoT Supplementary/Polling (ECS/P) Field..... | 277 | +| 10.4.5 | Relative Reserved Block Period (RRBP) field..... | 277 | +| 10.4.5.1 | Special requirements in dual transfer mode..... | 292 | +| 10.4.6 | Countdown Value (CV) field..... | 293 | +| 10.4.6a | Follow-On Indicator field (FOI)..... | 293 | +| 10.4.7 | Payload Type field..... | 293 | +| 10.4.8 | Final block indicator (FBI) bit..... | 294 | +| 10.4.8a | Coding and Puncturing Scheme indicator field (CPS)..... | 294 | +| 10.4.8a.1 | Header type 1..... | 295 | +| 10.4.8a.2 | Header type 2..... | 295 | +| 10.4.8a.3 | Header type 3..... | 297 | +| 10.4.8a.4 | Header type 4..... | 298 | +| 10.4.8a.5 | Header type 5..... | 298 | +| 10.4.8a.6 | Header type 6..... | 300 | +| 10.4.8a.7 | Header type 7..... | 301 | +| 10.4.8a.8 | Header type 8..... | 301 | +| 10.4.8a.9 | Header type 9..... | 303 | +| 10.4.8a.10 | Header type 10..... | 305 | +| 10.4.8b | Split Block indicator field (SPB)..... | 306 | +| 10.4.9 | TLLI Indicator (TI) bit..... | 306 | +| 10.4.9a | Address Control (AC) bit..... | 306 | +| 10.4.9b | Final Segment (FS) bit..... | 307 | +| 10.4.9c | Radio Transaction Identifier (RTI) field..... | 307 | +| 10.4.9d | Direction (D) bit..... | 307 | +| 10.4.9e | Final Segment extension (FSe) bit..... | 307 | +| 10.4.9f | Reduced TLLI (rTLLI)..... | 307 | +| 10.4.9g | Reduced TLLI Indicator (RI)..... | 307 | +| 10.4.10 | Temporary Flow Identity (TFI) field..... | 308 | +| 10.4.10a | Power Reduction (PR) field..... | 308 | +| 10.4.10b | Power Reduction extension (PRe) field..... | 309 | +| 10.4.11 | Extension (E) Bit..... | 309 | +| 10.4.12 | Block Sequence Number (BSN) field..... | 309 | +| 10.4.12a | Reduced Block Sequence Number (RBSN) bit..... | 310 | +| 10.4.12b | Reduced Block Sequence Number extension (RBSNe) field..... | 310 | +| 10.4.13 | More (M) bit..... | 311 | +| 10.4.14 | Length Indicator (LI) field in GPRS TBF mode and DCCH TBF mode ( Iu mode )..... | 311 | +| 10.4.14a | Length Indicator (LI) field in EGPRS TBF mode, EC TBF mode and TCH TBF mode ( Iu mode )..... | 312 | +| 10.4.15 | TLLI field..... | 316 | +| 10.4.16 | RLC data field..... | 316 | +| 10.4.17 | Control message contents field..... | 316 | +| 10.4.18 | Resent Block Bit (RSB)..... | 316 | +| 10.4.19 | PFI Indicator (PI) bit..... | 317 | +| 10.4.20 | Packet Flow Identifier (PFI) field..... | 317 | +| 10.4.21 | PAN Indication (PANI) field..... | 317 | +| 10.4.22 | Beginning of Window (BOW) field..... | 317 | +| 10.4.23 | Short Starting Sequence Number (ShortSSN) field..... | 317 | +| 10.4.24 | Carrier ID (CI) field..... | 317 | +| 10.4.25 | TN/PDCH-pair field..... | 318 | +| 10.4.26 | DTR Blks..... | 318 | +| 10.4.27 | Selected PLMN Index field..... | 318 | + +| | | | +|------------|------------------------------------------------------------------|-----| +| 10.4.28 | Coverage Class field (CC)..... | 319 | +| 10.4.29 | Downlink Coverage Class Estimate (DCCE)..... | 319 | +| 10.4.30 | Cell Identity..... | 319 | +| 10.4.31 | Routing Area Identification..... | 319 | +| 10.4.32 | MS Sync Accuracy..... | 320 | +| 10.4.33 | MS Transmission Offset..... | 320 | +| 10.4.34 | Random ID..... | 320 | +| 10.4.35 | Downlink Coverage Class (DLCC)..... | 321 | +| 10.4.36 | DCN-ID field..... | 321 | +| 10.4.37 | MTA Signature..... | 321 | +| 10.4.38 | Final MTA Access (FMA)..... | 321 | +| 10.4.39 | MTA Report Instance..... | 322 | +| 11 | Message functional definitions and contents..... | 322 | +| 11.1 | Handling of erroneous protocol data..... | 323 | +| 11.1.1 | Message classification..... | 323 | +| 11.1.1.1 | Distribution messages..... | 323 | +| 11.1.1.2 | Non-distribution messages..... | 324 | +| 11.1.1.2.1 | Format of the address information..... | 325 | +| 11.1.1.3 | DBPSCH message ( Iu mode only )..... | 325 | +| 11.1.2 | Error detection mechanism..... | 325 | +| 11.1.3 | Error labels..... | 325 | +| 11.1.3.1 | Generic error labels..... | 326 | +| 11.1.3.2 | 'Ignore' error label..... | 327 | +| 11.1.3.3 | 'Message escape' error label..... | 327 | +| 11.1.4 | Error detection and order of precedence..... | 327 | +| 11.1.4.1 | Unknown message type..... | 327 | +| 11.1.4.2 | Message not compatible with current protocol state..... | 328 | +| 11.1.4.3 | Syntactically incorrect message..... | 328 | +| 11.1.4.3.1 | Messages with error label: 'Distribution part error'..... | 328 | +| 11.1.4.3.2 | Messages with error label: 'Address information part error'..... | 328 | +| 11.1.4.3.3 | Messages with error label: 'Non-distribution part error'..... | 328 | +| 11.1.4.3.4 | Messages with error label: 'Message escape'..... | 328 | +| 11.1.4.3.5 | Messages with error label: 'Ignore'..... | 329 | +| 11.1.4.3.6 | Messages with error label: "DBPSCH message part error"..... | 329 | +| 11.1.4.4 | Syntactic error in truncated concatenation..... | 329 | +| 11.1.4.5 | (void)..... | 330 | +| 11.2 | RLC/MAC control messages..... | 330 | +| 11.2.0 | Message format..... | 331 | +| 11.2.0.1 | Downlink RLC/MAC messages..... | 332 | +| 11.2.0.2 | Uplink RLC/MAC messages..... | 333 | +| 11.2.1 | Packet Access Reject..... | 334 | +| 11.2.2 | Packet Control Acknowledgement..... | 336 | +| 11.2.2a | Packet Cell Change Continue..... | 338 | +| 11.2.3 | Packet Cell Change Failure..... | 339 | +| 11.2.3a | Packet Cell Change Notification..... | 341 | +| 11.2.4 | Packet Cell Change Order..... | 345 | +| 11.2.5 | Packet Channel Request..... | 353 | +| 11.2.5a | EGPRS Packet Channel Request..... | 355 | +| 11.2.5b | Packet DBPSCH Assignment..... | 360 | +| 11.2.5c | MPRACH Packet Channel Request..... | 363 | +| 11.2.6 | Packet Downlink Ack/Nack..... | 363 | +| 11.2.6a | EGPRS Packet Downlink Ack/Nack..... | 366 | +| 11.2.6b | Packet DBPSCH Downlink Ack/Nack..... | 368 | +| 11.2.6c | Packet DBPSCH Downlink Ack/Nack Type 2..... | 369 | +| 11.2.6d | MBMS Downlink Ack/Nack..... | 370 | +| 11.2.6e | EGPRS Packet Downlink Ack/Nack Type 2..... | 373 | +| 11.2.6f | EGPRS Packet Downlink Ack/Nack Type 3..... | 374 | +| 11.2.7 | Packet Downlink Assignment..... | 376 | +| 11.2.7.1 | Special requirements in dual transfer mode for downlink TBF..... | 388 | +| 11.2.7a | Multiple TBF Downlink Assignment..... | 389 | +| 11.2.8 | Packet Downlink Dummy Control Block..... | 394 | + +| | | | +|------------|----------------------------------------------------------------|-----| +| 11.2.8b | Packet Uplink Dummy Control Block..... | 395 | +| 11.2.9 | Packet Measurement Report..... | 395 | +| 11.2.9b | Packet Measurement Order..... | 398 | +| 11.2.9b.1 | GPRS REP PRIORITY description..... | 413 | +| 11.2.9c | Packet Mobile TBF Status..... | 413 | +| 11.2.9d | Packet Enhanced Measurement Report..... | 414 | +| 11.2.9e | Packet Neighbour Cell Data..... | 417 | +| 11.2.10 | Packet Paging Request..... | 419 | +| 11.2.11 | Packet PDCH Release..... | 424 | +| 11.2.12 | Packet Polling Request..... | 425 | +| 11.2.13 | Packet Power Control/Timing Advance..... | 426 | +| 11.2.14 | Packet PRACH Parameters..... | 428 | +| 11.2.15 | Packet Queuing Notification..... | 428 | +| 11.2.16 | Packet Resource Request..... | 429 | +| 11.2.17 | Packet PSI Status..... | 433 | +| 11.2.17a | Packet Serving Cell Data..... | 434 | +| 11.2.17b | Packet SI Status..... | 436 | +| 11.2.17c | Packet Serving Cell SI..... | 439 | +| 11.2.18 | Packet System Information Type 1..... | 440 | +| 11.2.19 | Packet System Information Type 2..... | 442 | +| 11.2.19.1 | Reference Frequency Lists in PSI2..... | 446 | +| 11.2.19.2 | Cell Allocation in PSI2..... | 446 | +| 11.2.19.3 | GPRS Mobile Allocation in PSI2..... | 446 | +| 11.2.19.4 | PCCCH Description..... | 446 | +| 11.2.19.5 | Abnormal cases..... | 446 | +| 11.2.20 | Packet System Information Type 3..... | 446 | +| 11.2.21 | Packet System Information Type 3 bis..... | 456 | +| 11.2.21a | Packet System Information Type 3 ter..... | 460 | +| 11.2.21a.1 | GPRS REP PRIORITY description..... | 462 | +| 11.2.21b | Packet System Information Type 3 quater..... | 462 | +| 11.2.21b.1 | GPRS REP PRIORITY description..... | 466 | +| 11.2.22 | (void)..... | 466 | +| 11.2.23 | Packet System Information Type 5..... | 466 | +| 11.2.23a | Packet System Information Type 6..... | 470 | +| 11.2.23b | Packet System Information Type 7..... | 471 | +| 11.2.24 | Packet System Information Type 8..... | 471 | +| 11.2.25 | Packet System Information 13..... | 473 | +| 11.2.25a | Packet System Information 14..... | 477 | +| 11.2.25b | Packet System Information 15..... | 479 | +| 11.2.25c | Packet System Information Type 16..... | 479 | +| 11.2.26 | Packet TBF Release..... | 481 | +| 11.2.27 | (void)..... | 482 | +| 11.2.28 | Packet Uplink Ack/Nack..... | 482 | +| 11.2.28a | Packet DBPSCH Uplink Ack/Nack..... | 485 | +| 11.2.28b | Packet DBPSCH Uplink Ack/Nack Type 2..... | 487 | +| 11.2.29 | Packet Uplink Assignment..... | 487 | +| 11.2.29.1 | Special requirements in dual transfer mode for uplink TBF..... | 500 | +| 11.2.29a | Multiple TBF Uplink Assignment..... | 501 | +| 11.2.30 | (void)..... | 510 | +| 11.2.30a | Packet Pause..... | 510 | +| 11.2.31 | Packet Timeslot Reconfigure..... | 511 | +| 11.2.31.1 | Special requirements in dual transfer mode..... | 526 | +| 11.2.31a | Multiple TBF Timeslot Reconfigure..... | 527 | +| 11.2.32 | Additional MS Radio Access Capabilities..... | 537 | +| 11.2.33 | Handover Access ( Iu mode only )..... | 537 | +| 11.2.34 | Physical Information ( Iu mode only )..... | 538 | +| 11.2.35 | Packet CS Request..... | 538 | +| 11.2.36 | Packet CS Command..... | 539 | +| 11.2.37 | Packet CS Release Indication..... | 540 | +| 11.2.38 | MBMS Service Request..... | 548 | +| 11.2.39 | MBMS Assignment (Non-distribution)..... | 549 | + +| | | | +|----------|------------------------------------------------------------|-----| +| 11.2.39a | MBMS Assignment (Distribution)..... | 551 | +| 11.2.40 | MBMS Neighbouring Cell Information..... | 553 | +| 11.2.41 | MBMS MS_ID Assignment..... | 557 | +| 11.2.42 | Packet MBMS Announcement..... | 558 | +| 11.2.43 | PS Handover Command..... | 560 | +| 11.2.44 | PS Handover Access..... | 563 | +| 11.2.45 | Packet Physical Information ( A/Gb mode only )..... | 564 | +| 11.2.46 | DTM Handover Command..... | 564 | +| 11.2.47 | Packet Application Information..... | 566 | +| 11.2.48 | EGPRS Packet Downlink Ack/Nack DLMC..... | 566 | +| 11.2.49 | EC Packet Access Reject..... | 567 | +| 11.2.50 | EC Packet Control Acknowledgement..... | 568 | +| 11.2.51 | EC Packet Downlink Ack/Nack..... | 570 | +| 11.2.52 | EC Packet Downlink Assignment..... | 571 | +| 11.2.53 | EC Packet Downlink Dummy Control Block..... | 575 | +| 11.2.54 | EC Packet Polling Request..... | 576 | +| 11.2.55 | EC Packet Power Control/Timing Advance..... | 577 | +| 11.2.56 | EC Packet TBF Release..... | 578 | +| 11.2.57 | EC Packet Uplink Ack/Nack..... | 579 | +| 11.2.58 | EC Packet Uplink Assignment..... | 588 | +| 11.2.59 | EC Packet Uplink Ack/Nack and Contention Resolution..... | 598 | +| 11.2.60 | EC Packet Downlink Ack/Nack Higher CC..... | 603 | +| 11.2.61 | EC Packet Control Acknowledgement Higher CC..... | 604 | +| 12 | Information element coding..... | 605 | +| 12.1 | Overview..... | 605 | +| 12.2 | (void)..... | 605 | +| 12.3 | Ack/Nack Description..... | 605 | +| 12.3.1 | EGPRS Ack/Nack Description..... | 606 | +| 12.3.2 | FLO Ack/Nack Description..... | 608 | +| 12.3.3 | EGPRS Ack/Nack Description DLMC..... | 609 | +| 12.4 | (void)..... | 610 | +| 12.5 | EGPRS..... | 610 | +| 12.5.1 | EGPRS Channel Quality Report..... | 610 | +| 12.5.2 | EGPRS Window Size..... | 611 | +| 12.5.3 | EGPRS BEP Link Quality Measurements IE..... | 612 | +| 12.5.4 | EGPRS Timeslot Link Quality Measurements IE..... | 613 | +| 12.5.5 | PDCH Pairs Description..... | 614 | +| 12.5a | EGPRS2..... | 615 | +| 12.5a.1 | EGPRS Channel Quality Report Type 2..... | 615 | +| 12.5a.2 | EGPRS BEP Link Quality Measurements Type 2 IE..... | 616 | +| 12.5a.3 | EGPRS Timeslot Link Quality Measurements Type 2 IE..... | 617 | +| 12.6 | (void)..... | 619 | +| 12.7 | Channel Request Description..... | 619 | +| 12.7a | Iu mode Channel Request Description..... | 620 | +| 12.7b | Extended Channel Request Description..... | 621 | +| 12.8 | Frequency Parameters..... | 621 | +| 12.8.1 | Abnormal cases..... | 623 | +| 12.8.2 | Dual Carrier Frequency Parameters..... | 623 | +| 12.8.3 | Pulse Format description..... | 624 | +| 12.8.4 | DLMC Frequency Parameters..... | 626 | +| 12.9 | Global Power Control Parameters..... | 627 | +| 12.9a | GPRS Power Control Parameters..... | 628 | +| 12.10 | Global TFI..... | 628 | +| 12.10a | GPRS Mobile Allocation..... | 628 | +| 12.10a.1 | Abnormal cases..... | 630 | +| 12.10b | (void)..... | 630 | +| 12.10c | (void)..... | 630 | +| 12.10d | EGPRS Modulation and coding Scheme description..... | 630 | +| 12.10e | RESEGMENT description..... | 631 | +| 12.10f | EGPRS Level description..... | 631 | +| 12.11 | Packet Request Reference..... | 632 | + +| | | | +|----------|------------------------------------------------------|-----| +| 12.12 | Packet Timing Advance..... | 632 | +| 12.12a | Global Packet Timing Advance..... | 633 | +| 12.12b | Packet Extended Timing Advance..... | 634 | +| 12.13 | Power Control Parameters..... | 634 | +| 12.14 | PRACH Control Parameters..... | 635 | +| 12.15 | Temporary Flow Identity (TFI)..... | 637 | +| 12.16 | Temporary Logical Link Identity (TLLI)/G-RNTI..... | 638 | +| 12.16a | GERAN Radio Network Temporary Identity (G-RNTI)..... | 638 | +| 12.17 | Temporary Queueing Identifier (TQI)..... | 638 | +| 12.18 | TIMESLOT_ALLOCATION..... | 639 | +| 12.19 | (void)..... | 639 | +| 12.20 | PAGE_MODE..... | 639 | +| 12.21 | Starting Frame Number Description..... | 639 | +| 12.21.1 | Absolute Frame Number Encoding..... | 639 | +| 12.21.2 | Relative Frame Number Encoding..... | 640 | +| 12.22 | (void)..... | 640 | +| 12.23 | Cell Identification..... | 640 | +| 12.24 | GPRS Cell Options..... | 641 | +| 12.25 | PCCCH Organization Parameters..... | 645 | +| 12.26 | Extension Bits IE..... | 645 | +| 12.27 | Non GPRS Cell Options IE..... | 646 | +| 12.28 | LSA Parameters..... | 647 | +| 12.29 | COMPACT reduced MA..... | 647 | +| 12.30 | MS Radio Access Capability 2..... | 648 | +| 12.31 | UTRAN FDD Target cell ..... | 649 | +| 12.32 | UTRAN TDD Target cell ..... | 650 | +| 12.33 | Temporary Mobile Group Identity (TMGI)..... | 651 | +| 12.34 | MBMS Bearer Identity..... | 652 | +| 12.35 | MS_ID..... | 652 | +| 12.36 | MBMS Channel Parameters..... | 652 | +| 12.37 | MBMS p-t-m channel description..... | 653 | +| 12.38 | MPRACH description..... | 653 | +| 12.39 | MBMS Sessions List..... | 654 | +| 12.40 | MBMS Session Parameters List..... | 654 | +| 12.41 | MPRACH Control Parameters..... | 655 | +| 12.42 | PS Handover Radio Resources..... | 656 | +| 12.42a | PS Handover Radio Resources 2..... | 661 | +| 12.42b | PS Handover Radio Resources 3..... | 664 | +| 12.43 | NAS Container for PS Handover..... | 670 | +| 12.44 | Estimated Session Duration..... | 670 | +| 12.45 | MBMS In-band Signalling Indicator..... | 671 | +| 12.45a | NPM Transfer Time..... | 671 | +| 12.45b | RRC Container..... | 672 | +| 12.46 | DTM Handover PS Radio Resources..... | 673 | +| 12.47 | DTM Handover CS Radio Resources..... | 677 | +| 12.48 | DTM Handover PS Radio Resources 2..... | 678 | +| 12.48a | PS resources assignment information elements..... | 681 | +| 12.48a.1 | EGPRS mode 2..... | 681 | +| 12.48a.2 | Single Downlink Assignment 2..... | 681 | +| 12.48a.3 | Single Uplink Assignment 2..... | 683 | +| 12.48a.4 | Dynamic Allocation 2..... | 684 | +| 12.48a.5 | Multiple Downlink Assignment 2..... | 687 | +| 12.48a.6 | Multiple Uplink Assignment 2..... | 690 | +| 12.49 | E-UTRAN Target Cell..... | 695 | +| 12.50 | Individual Priorities..... | 696 | +| 12.51 | GSM Priority Parameters..... | 697 | +| 12.52 | 3G Priority Parameters..... | 698 | +| 12.53 | E-UTRAN Parameters..... | 699 | +| 12.54 | 3G CSG Description..... | 701 | +| 12.55 | E-UTRAN CSG Description..... | 702 | +| 12.56 | Measurement Control Parameters Description..... | 702 | + +| | | | +|-------------------------------|----------------------------------------------------------------------|------------| +| 12.57 | PCID Group..... | 703 | +| 12.58 | PSC Group..... | 704 | +| 12.59 | Enhanced Cell Reselection Parameters..... | 704 | +| 12.60 | E-UTRAN CSG Measurement Report ..... | 705 | +| 12.61 | UTRAN CSG Measurement Report ..... | 706 | +| 12.62 | E-UTRAN CSG Target cell..... | 707 | +| 12.63 | UTRAN CSG Target cell..... | 708 | +| 12.64 | DTM Handover PS Radio Resources 3..... | 708 | +| 12.65 | Dynamic Allocation 3..... | 711 | +| 12.66 | DLMC Channel Quality Report..... | 712 | +| 12.67 | DOWNLINK_eTFI_ASSIGNMENT..... | 715 | +| 12.68 | E-UTRAN Target Cell with extended EARFCN..... | 716 | +| 12.69 | E-UTRAN IPP with extended EARFCNs..... | 716 | +| 12.70 | E-UTRAN NC with extended EARFCNs..... | 717 | +| 12.71 | Used DL Coverage Class..... | 718 | +| 12.72 | EC Ack/Nack Description..... | 719 | +| 12.73 | EC Primary Ack/Nack Description..... | 719 | +| 12.74 | EC Packet Timing Advance..... | 719 | +| 12.75 | EC Channel Quality Report..... | 719 | +| 12.76 | EC Channel Quality Report Higher CC..... | 720 | +| 13 | Timers and counters..... | 721 | +| 13.1 | Timers on the Mobile Station side..... | 722 | +| 13.2 | Timers on the network side..... | 735 | +| 13.3 | Counters on the Mobile Station side..... | 738 | +| 13.4 | Counters on the Network side..... | 739 | +| Annex A (informative): | Bibliography..... | 740 | +| Annex B (informative): | RLC data block encoding..... | 741 | +| B.1 | Example 1..... | 741 | +| B.2 | Example 2..... | 741 | +| B.3 | Example 3..... | 742 | +| B.4 | Example 4..... | 744 | +| B.5 | Example 5..... | 745 | +| B.6 | Example 6..... | 745 | +| B.7 | Example 7..... | 746 | +| B.8 | RLC data block delimitation for EGPRS..... | 747 | +| B.8.1 | Example 1..... | 747 | +| B.8.2 | Example 2..... | 748 | +| B.8.3 | Example 3..... | 750 | +| B.8.4 | Example 4..... | 751 | +| Annex C (informative): | Message Sequence Diagrams..... | 753 | +| Annex D (informative): | (void)..... | 754 | +| Annex E (informative): | (void)..... | 755 | +| Annex F (informative): | Examples of Countdown procedure operation..... | 756 | +| F.1 | Example 1..... | 757 | +| F.2 | Example 2..... | 758 | +| F.3 | Example 3..... | 759 | +| Annex G (informative): | Handling of erroneous protocol data, examples..... | 760 | +| G.1 | Application of error labels..... | 760 | +| G.2 | Application of the 'Message escape' error label..... | 761 | +| G.3 | Application of truncated concatenation including 'padding bits'..... | 762 | +| G.4 | Message extension using 'padding bits'..... | 763 | +| G.5 | Message extension using the Extension Bits IE..... | 764 | + +**Annex H (informative): (void)..... 765** + +**Annex I (informative): EGPRS RLC Window Sizes..... 766** + +**Annex J (informative): An example of MCS-8 retransmission..... 768** + +J.1 Original MCS-8 RLC data block..... 768 + +J.2 Retransmission in two MCS-6 RLC data blocks..... 769 + +J.3 Retransmission in four MCS-3 RLC data blocks..... 770 + +**Annex K (informative): Signalling uplink assignments for Downlink Dual Carrier and/or +RTTI or MTI configurations..... 772** + +**Annex L (informative): MultislotClassGroup in EGPRS Packet Channel Request..... 774** + +**Annex M (informative): MTI Assignments and allocations..... 775** + +**Annex N (normative): Uplink Radio Block Transmission order for EFTA..... 777** + +**Annex O (informative): Change History..... 778** + +--- + +## 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 + +## 1.1 General + +This document specifies procedures for the following layers of the radio interface (*Um* reference point), the interface between the GSM/EDGE Radio Access Network (GERAN) and the Mobile Station (MS): + +- Radio Link Control (RLC) +- Medium Access Control (MAC), including Physical Link Control functions + +The procedures apply in *A/Gb mode* and may also apply in *Iu mode*. + +## 1.2 Related documents + +The following documents provide information related to this document: + +- 3GPP TS 43.064 contains an overview of the GPRS radio interface (*Um* reference point). +- 3GPP TS 44.003 specifies channel types, access capabilities and channel configurations at the *Um* reference point. +- 3GPP TS 44.004 specifies services offered by the physical layer of the *Um* reference point. It also specifies control channels. RLC and MAC use these services and control channels. +- 3GPP TS 24.007 specifies, in general terms, this protocol's structured functions, its procedures and its relationship with other layers and entities. It also specifies the basic message format and error handling applied by layer 3 protocols. +- 3GPP TS 44.018 specifies GPRS procedures when operating on the Common Control Channel (CCCH) or on dedicated channels. +- 3GPP TS 44.064 specifies the Logical Link Control (LLC) layer. +- 3GPP TS 43.051 is an overall description of the GSM/EDGE Radio Access Network (GERAN) in *Iu mode*. +- 3GPP TS 51.010 specifies test procedures for radio-interface signalling. + +## 1.3 Use of logical control channels + +3GPP TS 45.002 defines four similar sets of logical control. + +The first set consists of the following logical control channels: + +- Broadcast Control Channel (BCCH): downlink only, used to broadcast Cell specific information; +- Paging Channel (PCH): downlink only, used to send page requests to Mobile Stations (MSs); +- Random Access Channel (RACH): uplink only, used to request GPRS resources or a Dedicated Control Channel; +- Access Grant Channel (AGCH): downlink only, used to allocate GPRS resources or a Dedicated Control Channel; + +The second set consists of the following logical control channels (Packet Control Channels): + +- Packet Broadcast Control Channel (PBCCH): downlink only, used to broadcast Cell specific information (not used, see sub-clause 1.6); +- Packet Paging Channel (PPCH): downlink only, used to send page requests to Mobile Stations (MSs) (not used, see sub-clause 1.6); +- Packet Random Access Channel (PRACH): uplink only, used to request GPRS resources (not used, see sub-clause 1.6); + +- Packet Access Grant Channel (PAGCH): downlink only, used to allocate GPRS resources (not used, see sub-clause 1.6); +- Packet Associated Control Channel (PACCH): bi-directional, associated with a Temporary Block Flow (TBF); +- Packet Timing advance control channel uplink (PTCCH/U): used to transmit random access bursts to allow estimation of the timing advance for one MS in transfer state; +- Packet Timing advance control channel downlink (PTCCH/D): used to transmit timing advance updates for several MS. One PTCCH/D is paired with several PTCCH/U's. +- MBMS Packet Random Access Channel (MPRACH): uplink only, used during the initial counting procedure for MBMS. + +The third set consists of the following logical control channels (COMPACT control channels): + +- COMPACT Packet Broadcast Control Channel (CPBCCH): downlink only, used to broadcast Cell specific information; This channel broadcasts the same information as the PBCCH, but has a different physical structure (see 3GPP TS 45.002); +- COMPACT Packet Paging Channel (CPPCH): downlink only, used to send page requests to Mobile Stations (MSs) on a COMPACT control channel;; +- COMPACT Packet Random Access Channel (CPRACH): uplink only, used to request GPRS resources on a COMPACT control channel; +- COMPACT Packet Access Grant Channel (CPAGCH): downlink only, used to allocate GPRS resources on a COMPACT control channel; +- Packet Associated Control Channel (PACCH): see above; +- Packet Timing advance control channel uplink (PTCCH/U): see above; +- Packet Timing advance control channel downlink (PTCCH/D): see above. + +The fourth set consists of the following logical control channels (EC-GSM-IoT control channels): + +- Extended Coverage Broadcast Control Channel (EC-BCCH): downlink only, used to broadcast Cell specific information for EC-GSM-IoT; +- Extended Coverage Paging Channel (EC-PCH): downlink only, used to send page requests to Mobile Stations (MSs) that have enabled EC operation; +- Extended Coverage Random Access Channel (EC-RACH): uplink only, used to request EC-GSM-IoT resources; +- Extended Coverage Access Grant Channel (EC-AGCH): downlink only, used to allocate EC-GSM-IoT resources; +- Extended Coverage Packet Associated Control Channel (EC-PACCH): bi-directional, associated with an EC Temporary Block Flow (EC TBF); + +## 1.4 Use of logical traffic channels + +3GPP TS 45.002 defines the following logical traffic channels used by RLC and MAC: + +- Traffic Channel (TCH): bidirectional, carries encoded speech or user data using GMSK on a dedicated basic physical subchannel (DBPSCH). TCH can be full-rate (TCH/F) or half-rate (TCH/H). +- Octal Traffic Channel (O-TCH): bidirectional, carries encoded speech using 8-PSK on a DBPSCH. O-TCH can be full-rate (O-TCH/F) or half-rate (O-TCH/H). +- Enhanced Traffic Channel (E-TCH): bidirectional, carries user data using 8-PSK on a DBPSCH. + +- Packet Data Traffic Channel (PDTCH): downlink: carries user data using GMSK, 8-PSK, 16-QAM or 32-QAM with normal symbol rate, or QPSK, 16-QAM, or 32-QAM with higher symbol rate on a shared basic physical subchannel (SBPSCH) or a DBPSCH. PDTCHs can be full-rate (PDTCH/F) or half-rate (PDTCH/H). +- Packet Data Traffic Channel (PDTCH) uplink: carries user data using GMSK, 8-PSK, 16-QAM with normal symbol rate, or QPSK, 16-QAM, 32-QAM with higher symbol rate on a shared basic physical subchannel (SBPSCH) or a DBPSCH. PDTCHs can be full-rate (PDTCH/F) or half-rate (PDTCH/H). +- Extended Coverage Packet Data Traffic Channel (EC-PDTCH) downlink: carries user data using GMSK or 8-PSK on one or four PDCH(s). +- Extended Coverage Packet Data Traffic Channel (EC-PDTCH) uplink: carries user data using GMSK or 8-PSK on one or four PDCH(s). + +## 1.5 Conventions + +Unless explicitly stated otherwise, the following conventions apply: + +- The notations "further study", "FS" or "FFS" indicate the annotated text is not normative. +- "GPRS" refers to "GPRS and EGPRS". +- "EGPRS" refers to "EGPRS and EGPRS2". +- "EGPRS2" refers to "EGPRS2-A and EGPRS2-B". +- "PBCCH" refers to "PBCCH and CPBCCH". +- "PPCH" refers to "PPCH and CPPCH". +- "PRACH" refers to "PRACH and CPRACH". +- "PAGCH" refers to "PAGCH and CPAGCH". +- References to "PDCH" also apply to "SBPSCH" and vice-versa. +- "MBMS Assignment" refers to either "MBMS ASSIGNMENT (NON-DISTRIBUTION)" or "MBMS ASSIGNMENT (DISTRIBUTION)". + +## 1.6 Restrictions + +Independently of what is stated elsewhere in this and other 3GPP specifications, mobile station support for PBCCH, PCCCH and PACKET PSI STATUS is optional for A/Gb-mode of operation. The network shall never enable PBCCH and PCCCH. + +On PACCH the network may send Packet System Information (PSI) messages PSI13, PSI14 and PSI15 but shall not send any other PSI message. + +--- + +## 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.060: "General Packet Radio Service (GPRS); Service Description; Stage 1". +- [3] 3GPP TS 23.003: "Numbering, addressing and identification". +- [4] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM system". +- [5] 3GPP TS 43.064: " Overall description of GPRS radio interface; Stage 2". +- [6] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [7] 3GPP TS 44.003: "Mobile Station - Base Station System (MS-BSS) interface; Channel structures and access capabilities". +- [8] 3GPP TS 44.004: "Layer 1; General requirements". +- [9] 3GPP TS 44.005: "Data Link (DL) layer; General aspects". +- [10] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [11] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [12] 3GPP TS 44.064: " Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) Layer Specification". +- [13] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [14] 3GPP TS 45.003: "Channel coding". +- [15] 3GPP TS 45.008: "Radio subsystem link control". +- [16] 3GPP TS 45.010: "Radio subsystem synchronization". +- [17] (void) +- [18] (void). +- [19] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [20] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [21] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)". +- [22] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [23] ITU-T Recommendation T.4: "Standardization of Group 3 facsimile terminals for document transmission". +- [24] 3GPP TS 22.011: "Service accessibility". +- [25] 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)". +- [26] 3GPP TS 25.102: "UTRA (UE) TDD; Radio transmission and reception". +- [27] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [28] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [29] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". +- [30] 3GPP TS 45.005: "Radio transmission and reception". +- [31] 3GPP TS 45.009: "Link adaptation". +- [32] TTA/ETSI TS 102 234: "CDMA 2000 Series". + +- [33] 3GPP TS 51.010-1 (Rel-6): "Mobile Station (MS) conformance specification; Part 1: Conformance specification ". +- [34] 3GPP TS 51.010-2 (Rel-6): "Mobile Station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (ICS); proforma specification". +- [35] 3GPP TS 51.010-3 (Rel-6): "Mobile Station (MS) conformance specification; Part 3: Layer 3 Abstract Test Suite (ATS)". +- [36] 3GPP TS 51.010-4 (Rel-6): "Mobile Station (MS) conformance specification; Part 4: SIM application toolkit conformance specification". +- [37] 3GPP TS 51.021: "Base Station System (BSS) equipment specification; Radio aspects". +- [38] 3GPP TS 43.051: "GSM/EDGE Radio Access Network (GERAN); Overall Description - Stage 2". +- [39] Void. +- [40] Michel MOULY, "CSN.1 Specification, Version 2.0", Cell & Sys, ISBN: 2-9510062-0-9. +Web: . +- [41] 3GPP TS 25.224: "Physical Layer Procedures (TDD)". +- [42] 3GPP TS 44.318: "Generic access to the A/Gb interface; Mobile GA interface layer 3 specification". +- [43] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2". +- [44] 3GPP TS 43.318: "Generic access to the A/Gb interface; Stage 2". +- [45] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [46] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [47] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation". +- [48] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [49] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [50] 3GPP TS 23.251: "Network sharing; Architecture and functional description". +- [51] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3". +- [52] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)". +- [53] 3GPP TS 31.102: "Characteristics of the USIM Application". +- [54] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". + +--- + +## 3 Definitions, abbreviations and symbols + +### 3.1 Definitions + +This document uses the following definitions: + +Additional PLMN: when network sharing is in use within a given cell, an Additional PLMN refers to a PLMN of which the PLMN ID is broadcast in the SYSTEM INFORMATION TYPE 22 message (see 3GPP TS 44.018) + +**A/Gb mode:** mode of operation of the MS when connected to the Core Network via GERAN and the A and/or Gb interfaces. + +**Basic radio block period:** the time needed to transmit a radio block on one PDCH using a basic TTI configuration i.e. four TDMA frames. + +**Blind Physical Layer Transmissions:** See 3GPP TS 43.064 + +**Block period:** block period is the sequence of four timeslots on a PDCH used to convey one radio block + +**Broadcast/multicast receive mode:** In broadcast/multicast receive mode, the mobile station is receiving upper layer PDUs on packet data physical channels used for point-to-multipoint transmission (see sub-clause 5.3.1); it is not allocated any additional radio resource on packet data physical channels. Broadcast/multicast receive mode is a sub-state of packet idle mode. The mobile station listens to the PBCCH and PCCCH or, if those are not provided by the network, to the BCCH and CCCH. + +**BTTI configuration:** a configuration in which a radio block is sent using one PDCH in each of four consecutive TDMA frames. In a BTTI configuration, one radio block can be transmitted in a basic radio block period. + +**BTTI USF mode:** a mode in which the USF is received on one PDCH of a downlink PDCH-pair during four consecutive TDMA frames. + +**Cell Change Notification (CCN):** See sub-clause 5.5.1.1a. + +**Common PLMN:** when network sharing is in use within a given cell, the Common PLMN refers to the PLMN of which the PLMN ID is contained in the *Location Area Identification* IE broadcast in the SYSTEM INFORMATION TYPE 3 and SYSTEM INFORMATION TYPE 4 messages (see 3GPP TS 44.018, 3GPP TS 23.251 and 3GPP TS 24.008). + +**Corresponding PDCH pair:** The Corresponding PDCH pair associated with an uplink PDCH pair which forms part of an uplink TBF assignment is the downlink PDCH pair which is monitored by the mobile station for the USF for the TBF and on which PACCH/D is transmitted. The Corresponding PDCH pair associated with a downlink PDCH pair which forms part of a downlink TBF assignment is the uplink PDCH pair on which PACCH/U is transmitted. + +**Coverage Class:** See 3GPP TS 43.064. + +**CSG Cells Reporting:** refers to the ability of the mobile station to report measurements, CSG-ID and routing parameters of CSG cells in packet transfer mode. Routing parameters include Cell Identity and optionally the PLMN-ID and (for E-UTRAN cells only) the Tracking Area Code. + +**Downlink Dual Carrier:** Downlink Dual Carrier is a feature allowing resources (for uplink and/or downlink TBFs and/or dedicated resources) to be assigned to a mobile station on up to two radio frequency channels within the same frequency band. + +**Downlink Dual Carrier configuration:** A Downlink Dual Carrier configuration is one in which the mobile station has radio resources assigned over two radio frequency channels. In packet transfer mode, RLC/MAC blocks for uplink TBFs can only be transmitted on one radio frequency channel in any given radio block period, and RLC/MAC blocks for downlink TBFs can be transmitted on two radio frequency channels in any given radio block period. In dual transfer mode, uplink RLC/MAC blocks can be transmitted only on the radio frequency channel on which the dedicated resource is assigned. + +**Downlink Multi Carrier (DLMC):** Downlink Multi Carrier is a feature allowing resources for a downlink TBF (and optionally an uplink TBF) to be assigned to a mobile station on two or more radio frequency channels in the same or different frequency bands using EGPRS or EGPRS2-A. + +**DLMC configuration:** A DLMC configuration is one in which a mobile station in packet transfer mode has a downlink TBF where radio resources are configured on two or more radio frequency channels in the same or in different frequency bands. A mobile station in a DLMC configuration with an uplink TBF can only transmit RLC/MAC blocks for the uplink TBF on one radio frequency channel in any given radio block period whereas RLC/MAC blocks for the downlink TBF can be transmitted on one or more frequency channels in any given radio block period. + +**DTM handover:** DTM handover is a feature used by the network to command a mobile station to move from its old (source) cell to a new (target) cell while operating in dual transfer mode and continue the operation of its ongoing circuit switched service and one or more of its ongoing packet switched services in the new cell. The mobile station is + +allocated one circuit switched radio resource and packet switched radio resources applicable to the new cell within a DTM HANDOVER COMMAND message. + +**Dual transfer mode:** In dual transfer mode, the mobile station is allocated radio resources providing an RR connection (3GPP TS 44.018) and one or more Temporary Block Flows on one or more packet data physical channels. The allocation of radio resource for the RR connection and the Temporary Block Flow(s) is co-ordinated by the network in agreement with the capabilities of the mobile station in dual transfer mode. + +**Dynamic Timeslot Reduction:** Dynamic Timeslot Reduction (DTR) is a feature used by the network to reduce the number of downlink timeslots monitored by the mobile station during inactivity periods of an EGPRS TBF. It is applicable when extended uplink TBF mode and/or delayed downlink TBF release are used. + +**Early TBF establishment:** Procedure applicable when both the network and the mobile station support the extended uplink TBF mode, where the network keeps the uplink TBF open (by means of the extended uplink TBF mode operation) upon explicit request from the mobile station that pre-allocation is required. This allows the possibility to pre-allocate a TBF before actual data is ready for transmission. + +**EC-GSM-IoT:** See 3GPP TS 43.064. + +**EC operation:** See 3GPP TS 43.064. + +**EC TBF:** a TBF operating in EC TBF mode. + +**EC TBF mode:** refers to a TBF supporting extended coverage by operation on the EC-PDTCH and EC-PACCH channels. A TBF in EC TBF mode may consist of multiple EC-PDTCH and EC-PACCH channels if in coverage class 1 according to defined multislot capability of the mobile station. The EC TBF uses the EGPRS Modulation and Coding Schemes with GMSK modulation (MCS-1 to MCS-4) and optionally, with 8-PSK modulation (MCS-5 to MCS-9). An uplink TBF in EC TBF mode is allocated using fixed uplink allocation. + +**EGPRS:** Enhanced GPRS enables higher data rates through usage of 8PSK modulation in addition to GMSK. EGPRS also enables Incremental Redundancy operation. + +**EGPRS TBF mode:** refers to a TBF utilising the EGPRS enhancements (e.g. Incremental Redundancy and possibly 8-PSK) or the EGPRS2 enhancements. + +**EGPRS TBF:** refers to a TBF utilising the EGPRS enhancements, e.g. Incremental Redundancy and possibly 8-PSK. + +**EGPRS2:** In the downlink direction, Enhanced GPRS Phase 2 enables higher data rates through usage of higher symbol rate, turbo codes, and QPSK, 16-QAM and 32-QAM modulations in addition to (or instead of) GMSK and 8PSK. In the uplink direction, Enhanced GPRS Phase 2 enables higher data rates through usage of higher symbol rate, and QPSK, 16-QAM and 32-QAM modulations in addition to (or instead of) GMSK and 8PSK. EGPRS2 consists of EGPRS2-A and EGPRS2-B in both directions. + +**EGPRS2-A:** In the downlink direction, Enhanced GPRS Phase 2 Level A enables higher data rates through usage of turbo codes, and 16-QAM and 32-QAM modulations in addition to GMSK and 8-PSK. In the uplink direction, Enhanced GPRS Phase 2 Level A enables higher data rates through usage of 16-QAM modulation in addition to GMSK and 8-PSK. + +**EGPRS2-B:** In the downlink direction, Enhanced GPRS Phase 2 Level B enables higher data rates through usage of higher symbol rate, turbo codes, and QPSK, 16-QAM and 32-QAM modulations in addition to GMSK or instead of 8PSK. In the uplink direction, Enhanced GPRS Phase 2 Level B enables higher data rates through usage of higher symbol rate, and QPSK, 16-QAM and 32-QAM modulations in addition to GMSK or instead of 8PSK. + +**EGPRS2 TBF:** refers to a TBF utilising the EGPRS2 enhancements in the direction of data transfer, downlink or uplink. More specifically, in each direction, downlink or uplink, an EGPRS2-A TBF refers to a TBF utilising the EGPRS2-A enhancements and an EGPRS2-B TBF refers to a TBF utilising the EGPRS2-B enhancements. An EGPRS2 TBF operates in EGPRS TBF mode. + +**EGPRS-GMSK only TBF:** refers to a TBF in EGPRS TBF mode but making only use of MCS-1 to MCS-4 modulation and coding schemes. The number of PDCHs assigned to an EGPRS-GMSK only TBF can be extended to the maximum number of timeslots compatible with the GPRS multislot class of the MS. This mode is determined by the mobile station based on the aggregate timeslot allocation assigned by the network. In the case the aggregate timeslot allocation is not within the indicated EGPRS multislot class, but is within the indicated GPRS multislot class, a mobile station supporting this mode shall consider the TBF to be in EGPRS-GMSK only mode (see sub-clause 9.1.9.2). This mode is only applicable in packet transfer mode. + +**Enhanced Flexible Timeslot Assignment (EFTA):** Enhanced Flexible Timeslot Assignment gives the network the possibility to allocate one and the same mobile station uplink and downlink PDCH resources that overlap in time. This mobile station shall then for these overlapping instances prioritize uplink radio block transmission over attempting to read downlink radio blocks (unless performing pre-emptive retransmissions), but shall always attempt to read downlink radio blocks if it has nothing to transmit If it does not need to use all its allocated uplink PDCH resources, the mobile station shall transmit its uplink radio blocks in such a way that the number of downlink radio blocks it can read is maximized. Both network and mobile station must support extended uplink TBF mode in order for Enhanced Flexible Timeslot Assignment, EFTA, to be supported. + +**Enhanced Multiplexing for Single RLC Entity (EMSR):** Refers to the multiplexing of upper layer data flows associated with multiple PFCs with at least two of them having unique TFIs within the context of a single RLC entity for single TBF operation. EMSR may only be used on a TBF operating in EGPRS TBF mode. EMSR is not applicable to Multiple TBF operation or when Exclusive Allocation is used. + +**Enhanced Multiplexing for Single TBF (EMST):** refers to the multiplexing of upper layer data flows using one or more RLC entities on a single TBF where each RLC entity operates in a different RLC mode. EMST is applicable only to TBFs in EGPRS TBF mode. EMST is not applicable to Multiple TBF operation. + +**Extended EARFCNs:** refers to extended EARFCN value range (0 ...262143) with EARFCNs coded over 18 bits. MS and network support of extended EARFCNs is mandatory when network sharing is supported; support of extended EARFCNs is optional otherwise. + +When network sharing is in use within a given cell, the network shall provide extended EARFCNs within the SYSTEM INFORMATION TYPE 23 message, if broadcasted in the cell; additionally when extended EARFCNs is in use within a given cell, the network may provide at least one EARFCN value > 65535 within the SYSTEM INFORMATION TYPE 2quater message. + +**Extended uplink TBF mode:** In the *extended uplink TBF mode*, the uplink TBF may be maintained during temporary inactive periods, where the mobile station has no RLC information to send. The network determines the release of the uplink TBF (see sub-clause 9.3.1b). + +**Fast Ack/Nack Reporting (FANR):** Fast Ack/Nack Reporting enables the use of a PAN field within an RLC/MAC block for EGPRS data transfer or for EGPRS2 data transfer. FANR enables the mobile station to transmit in the uplink direction a PAN field corresponding to a downlink TBF. Similarly FANR enables the network to transmit in the downlink direction a PAN field corresponding to an uplink TBF. + +**Fixed Uplink Allocation:** Static allocation (and assignment) of limited resources in the uplink over one or more TTIs, using one or more PDCHs, that does not make use of USF based allocation. + +**Flexible Timeslot Assignment (FTA):** Flexible Timeslot Assignment allows increased flexibility in the assignment of PDCH resources by letting some of the limitations imposed by the mobile stations multislot class (see 3GPP 45.002) to be respected on an allocation basis (i.e. per radio block period) rather than on an assignment basis (i.e. at TBF setup time). + +**GAN Cell:** A cell under control of a GANC. + +**GAN Mode:** MS mode of operation where the MS is connected to the Core Network via a GANC and the A and/or Gb interfaces. + +**GPRS multislot class / EGPRS multislot class:** refers to the different mobile station capabilities to transmit and receive on different combinations of multiple PDCHs. The multislot classes are defined in 3GPP TS 45.002. Note that the mobile station may indicate different multislot classes for circuit mode services for GPRS and for EGPRS (see 3GPP TS 24.008). Different multislot class mobile stations are capable of supporting different medium access modes (see sub-clause 5.2.4). + +**GPRS TBF mode:** refers to a TBF not utilising EGPRS or EGPRS2. + +**Inter-band reception:** see 3GPP TS 45.005. + +**IR:** Incremental redundancy, enables higher data rates through combining information from different transmissions of RLC data blocks when decoding. Also known as Hybrid Type II/III ARQ. + +**Iu mode:** mode of operation of the MS when connected to the Core Network via GERAN or UTRAN and the Iu interface. + +**MAC-dedicated state:** a MAC-control-entity state where a DBPSCH is assigned and no SBPSCH is assigned. This state only applies in *Iu mode*. + +**MAC-DTM state:** a MAC-control-entity state where at least one DBPSCH and one SBPSCH are assigned. This state only applies in *Iu mode*. + +**MAC-idle state:** a MAC-control-entity state where no basic physical subchannels are assigned. This state only applies in *Iu mode*. + +**MAC-shared state:** a MAC-control-entity state where at least one SBPSCH is assigned. This state only applies in *Iu mode*. + +**MCS:** Modulation and Coding Scheme. + +**MS assisted Dedicated Core Networks selection:** MS assisted Dedicated Core Network selection is an optional feature wherein the selection of the Dedicated Core Network to which a BSS routes LLC PDUs is based on, in addition to the selected PLMN, the “DCN-ID” value provided by the MS (see 3GPP TS 23.401 [54]). + +**MS multislot class:** refers to GPRS multislot class in case of a GPRS TBF mode or EGPRS-GMSK only TBF mode. In case of EGPRS TBF mode, MS multislot class refers to EGPRS multislot class. + +**Multilateration Timing Advance (MTA):** See 3GPP TS 43.059. + +**Multiple TBF procedures:** A mobile station that supports multiple TBF procedures can support one or more concurrent TBFs in either direction while in packet transfer mode (A/Gb mode). A network that supports multiple TBF procedures can support one or more concurrent TBFs in either direction for a mobile station that supports multiple TBF procedures in packet transfer mode (A/Gb mode). + +**Multiple TTI (MTTI) configuration:** A mobile station that supports MTTI Configurations may be assigned a TBF using both RTTI resources (PDCH-pairs) and BTTI resources (PDCHs). + +**Network sharing:** network sharing is an optional feature that allows different core network operators to connect to the same shared radio access network (see 3GPP TS 23.251). When network sharing is in use within a given cell, the network broadcasts within system information the PLMN identities of the PLMNs sharing the cell. A mobile station supporting network sharing uses this information for its PLMN (re)selection processes and indicates the selected PLMN to the BSS. + +**Non-contiguous intra-band reception:** see 3GPP TS 45.005. + +**Non-extended uplink TBF mode:** Where a distinction is needed, an uplink TBF, not operating in the extended uplink TBF mode, is referred as operating in the *non-extended uplink TBF mode*. + +**Non-synchronized PS handover:** The basic type of PS handover which is used when the time bases of the involved cells bear no particular relationship between themselves and when the MS cannot predict the timing advance to be used in the target cell before access in this cell. The requirements that apply for the non-synchronized PS handover are given in 3GPP TS 45.010. + +**Packet access failure:** Packet access failure refers to the access cases where the mobile station is explicitly denied access to the network, i.e. is not allowed to transmit (EGPRS) PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST messages or receives a PACKET QUEUING NOTIFICATION message or a PACKET ACCESS REJECT message. + +**Packet flow context:** Packet Flow Context (PFC) procedures are described in 3GPP TS 23.060. A Packet Flow Identifier (PFI) is used to identify a PFC. + +**Packet idle mode:** In packet idle mode, the mobile station is prepared to transfer LLC PDUs on packet data physical channels (see sub-clause 5.3). The mobile station is not allocated any radio resource on a packet data physical channel; it listens to the PBCCH and PCCCH or, if those are not provided by the network, to the BCCH and the CCCH. + +**Packet transfer mode:** In packet transfer mode, the mobile station is prepared to transfer LLC PDUs on packet data physical channels (see sub-clause 5.4). The mobile station is allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs. + +**Piggy-backed Ack/Nack (PAN) field:** A Piggy-backed Ack/Nack field provides acknowledgement status of downlink (respectively uplink) RLC data blocks within an uplink (respectively downlink) RLC/MAC block for data transfer. + +**Power Efficient Operation (PEO):** Used by a MS to reduce its power consumption through the use of relaxed mobility related requirements and the use of eDRX or PSM - see 3GPP TS 23.060 [3]. A PEO capable MS in a cell supporting PEO, that has negotiated the use of eDRX or PSM is said to have enabled PEO. + +**Pre-synchronized PS handover:** A type of PS handover where the MS uses the timing advance included in the PS HANDOVER COMMAND message for immediate use in the target cell. The requirements that apply for the pre-synchronized PS handover are given in 3GPP TS 45.010. + +**PS handover:** PS handover is a feature used by the network to command a mobile station to move from its old (source) cell to a new (target) cell while operating in packet transfer mode and continue the operation of one or more of its ongoing packet switched services in the new cell using TBF resource allocations provided within a PS HANDOVER COMMAND message. For PS handover to a GAN cell the mobile station receives the assignment of the target cell radio resources prior to receiving the PS HANDOVER COMMAND message. + +**Radio block:** A radio block is the sequence of four normal bursts carrying one RLC/MAC protocol data units (see 3GPP TS 44.004). (The one exception is a radio block occasionally used on PACCH consisting of a sequence of four access bursts, each carrying a repetition of one short RLC/MAC block.). A radio block is sent either on a PDCH (BTTI configuration) or a PDCH-pair (RTTI configuration). + +**Random access failure:** Random access failure refers to the access case when the mobile station does not get any response from the network to its (EGPRS) PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST messages. + +**Random values:** In a number of places in this Technical Specification, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. For such random values refer to 3GPP TS 44.018. + +**Reduced Latency:** refers to the use of FANR either in BTTI configuration or in RTTI configuration. Reduced Latency capability is required for the use of MTI configurations. + +**Reduced radio block period:** the time needed to transmit a radio block on a PDCH-pair using a reduced TTI configuration i.e. two TDMA frames. + +**RLC/MAC block:** A RLC/MAC block is the protocol data unit exchanged between RLC/MAC entities (see clause 10 and 3GPP TS 44.004). + +**RLC/MAC control block:** A RLC/MAC control block is the part of an RLC/MAC block carrying a control message between RLC/MAC entities (see sub-clause 10.3). + +**RLC data block:** A RLC data block is the part of a RLC/MAC block carrying user data or signalling data received from an upper layer (see sub-clause 10.2). + +**RLC Non-Persistent Mode:** A mode of RLC operation where retransmissions are possible but it is not required that all RLC data blocks are correctly received at the receiving RLC endpoint. + +**RR connection:** An RR connection is a physical connection established between a mobile station and the network to support the upper layers' exchange of information flows. An RR connection is maintained and released by the two peer entities. + +**RRC connection:** An RRC connection is a point-to-point, bi-directional, logical connection between RRC peer entities in the mobile station and the GERAN characterised by the allocation of a G-RNTI. A mobile station has either zero or one RRC connections. RRC connections only apply in *Iu mode*. + +**RTTI configuration:** a configuration in which a radio block is sent using two PDCHs (PDCH-pair) in either the first two or the last two TDMA frames of any given basic radio block period. + +**RTTI USF mode:** a mode in which the USF is received on a downlink PDCH-pair during two consecutive TDMA frames. + +**Source BSS:** Within the context of a PS handover the source BSS is the BSS controlling the cell in which the mobile station is camping prior to performing PS handover (i.e. it controls the old cell). + +**Synchronized PS handover:** A type of PS handover which is possible when the time bases of the involved cells are synchronized, and for which no timing advance needs to be provided to the MS. The requirements that apply for the synchronized PS handover are given in 3GPP TS 45.010. + +**Target BSS:** Within the context of a PS handover the target BSS is the BSS controlling the cell in which the mobile station is camping after successful completion of PS handover (i.e. it controls the new cell). If the same BSS controls both the old cell and the new cell associated with the PS handover of any given mobile station then the source BSS and the target BSS are the same. + +**TBF abort:** The term "abort" as applied to TBF is used when the TBF is abruptly stopped without using the Release of TBF procedures defined in clause 9. + +**TBF release:** The term "release" as applied to TBF is used when the TBF is stopped using one of the Release of TBF procedures defined in clause 9. + +**Temporary Block Flow (TBF):** A Temporary Block Flow is, in *A/Gb mode*, a physical connection used by the two RR peer entities to support the unidirectional transfer of LLC PDUs on packet data physical channels (see sub-clause 5.2.1). In *Iu mode*, a TBF is a logical connection offered by two MAC entities to support the unidirectional transfer of RLC PDUs on basic physical subchannels. + +**Timer Expiry:** A started timer has run the time specified. + +**Timer Restart:** A timer that may already be running is stopped and then started again to run the time specified. + +**Timer Start:** A timer is started to run the time specified. + +**Timer Stop:** A started timer is stopped and its value is then undefined. + +**Unique Frequency Parameter Set (UFPS):** see 3GPP TS 45.008 + +**Uplink control timeslot:** refers to the timeslot number of the timeslot where the PACCH/U for the MS is located in case of a BTI configuration, or to the uplink PDCH pair where the PACCH/U for the MS is located in case of an RTTI configuration. This parameter is set to the value of the Uplink Control timeslot IE in an assignment message. Otherwise, this parameter is unassigned. In A/Gb mode, this parameter is applicable only to multiple TBF procedures. + +**Uplink State Flag (USF):** The Uplink State Flag (USF) is used on PDCH channel(s) to allow multiplexing of uplink Radio blocks from different TBFs belonging to the same or different mobile stations (see sub-clause 5.2.3, clause 10 and 3GPP TS 45.002). + +**Upper-layer PDU:** An upper-layer PDU is, in *A/Gb mode*, an LLC PDU and, in *Iu mode*, an RRC message, a PDCP PDU or a PDU from the NAS user plane. + +## 3.2 Abbreviations + +This document uses abbreviations from 3GPP TR 21.905 and 3GPP TS 43.064. It also uses the following abbreviations: + +| | | +|---------------|---------------------------------------------------------------| +| ARI | Access Request Identifier | +| ARQ | Automatic Repeat reQuest | +| AS | Access Stratum | +| BCCH | Broadcast Control CHannel | +| BSS | Base Station Subsystem | +| BTI | Basic Transmission Time Interval | +| CBCH | Cell Broadcast CHannel | +| CC | Call Control | +| CC | Coverage Class | +| CCCCH | COMPACT CCCH | +| CCCH | Common Control CHannel | +| CCN | Cell Change Notification | +| CN | Core Network | +| CPBCCH | COMPACT PBCCH | +| CS- i | GPRS Coding Scheme i | +| DAS- i | EGPRS2 Downlink level A modulation and coding Scheme i | +| DBS- i | EGPRS2 Downlink level B modulation and coding Scheme i | +| DC | Dedicated Control | +| DCN-ID | Dedicated Core Network ID | +| DLC | Data Link Control | +| DLMC | Downlink Multi Carrier | +| DBPSCH | Dedicated Basic Physical Sub CHannel | + +| | | +|---------------|---------------------------------------------| +| DTR | Dynamic Timeslot Reduction | +| EC-AGCH | Extended Coverage Access Grant CHannel | +| EC-BCCH | Extended Coverage BroadCast CHannel | +| EC-CCCH | Extended Coverage Common Control CHannel | +| EC-PCH | Extended Coverage Paging CHannel | +| EC-RACH | Extended Coverage Random Access CHannel | +| EC-SCH | Extended Coverage Synchronization CHannel | +| ECSD | Enhanced Circuit Switched Data | +| EC SI | Extended Coverage System Information | +| EDGE | Enhanced Data rates for Global Evolution | +| E-FACCH | Enhanced FACCH | +| EGPRS | Enhanced General Packet Radio Service | +| EGPRS2 | EGPRS Phase 2 | +| eNB | E-UTRAN NodeB | +| E-TCH | Enhanced TCH | +| eTFI | extended Temporary Flow Identifier | +| EUTRA | Evolved UTRA | +| E-UTRAN | Evolved UTRAN | +| FACCH | Fast Associated Control CHannel | +| FANR | Fast Ack/Nack Reporting | +| GAN | Generic Access Network | +| GANC | Generic Access Network Controller | +| GC | General Control | +| GERAN | GSM/EDGE Radio Access Network | +| GPRS | General Packet Radio Service | +| GRA | GERAN Registration Area | +| G-RNTI | GERAN Radio Network Temporary Identity | +| GSM | Global System for Mobile communications | +| IETF | Internet Engineering Task Force | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| LCS | LoCation Services | +| LLC | Logical Link Control | +| MAC | Medium Access Control | +| MCS- i | EGPRS Modulation and Coding Scheme i | +| MM | Mobility Management | +| MME | Mobility Management Entity | +| MPRACH | MBMS Packet Random Access Channel | +| MS | Mobile Station | +| MTA | Multilateration Timing Advance | +| NAS | Non Access Stratum | +| NSAPI | Network-layer SAPI | +| Nt | Notification | +| O-FACCH | Octal FACCH | +| O-TCH | Octal TCH | +| PAN | Piggy-backed Ack/Nack | +| PBCCH | Packet BCCH | +| PDCH | Packet Data CHannel | +| PDCP | Packet Data Convergence Protocol | +| PDP | Packet Data Protocol | +| PDTCH | Packet Data TCH | +| PDU | Protocol Data Unit | +| PEO | Power Efficient Operation | +| PFC | Packet Flow Context | +| PFI | Packet Flow Identifier | +| PLMN | Public Land Mobile Network | +| PTCCH | Packet Timing-advance Control CHannel | +| p-t-m | point-to-multipoint | +| P-TMSI | Packet TMSI | +| QoS | Quality of Service | +| RAB | Radio Access Bearer | + +| | | +|---------------|-------------------------------------------------------------| +| RANAP | Radio Access Network Application Part | +| RB | Radio Bearer | +| RLC | Radio Link Control | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| RNSAP | Radio Network Subsystem Application Part | +| ROHC | Robust Header Compression | +| RR | Radio Resource | +| RRC | Radio Resource Control | +| RTP | Real Time Protocol | +| RTTI | Reduced Transmission Time Interval | +| SACCH | Slow Associated Control CHannel | +| SAP | Service Access Point | +| SAPI | Service Access Point Identifier | +| SDCCH | Stand-alone Dedicated Control CHannel | +| SDU | Service Data Unit | +| SBPSCH | Shared Basic Physical Sub CHannel | +| TBF | Temporary Block Flow | +| TCH | Traffic Channel | +| TCP | Transmission Control Protocol | +| TFI | Temporary Flow Identifier | +| TLLI | Temporary Logical Link Identifier | +| TMSI | Temporary Mobile Subscriber Identity | +| TSC | Training Sequence Code | +| TTI | Transmission Time Interval | +| UAS- i | EGPRS2 Uplink level A modulation and coding Scheme i | +| UBS- i | EGPRS2 Uplink level B modulation and coding Scheme i | +| UDP | User Datagram Protocol | +| UMTS | Universal Mobile Telecommunication System | +| USF | Uplink State Flag | +| UTRAN | UMTS Terrestrial Radio Access Network | + +### 3.3 Symbols + +This document uses the following symbols: + +| | | +|--------------|-------------------------------------------------------------| +| A | Interface between a BSS and a 2G MSC | +| Gb | Interface between a BSS and a 2G SGSN | +| Iu | Interface between a BSS or an RNC and a 3G MSC or a 3G SGSN | +| Iu-cs | Interface between a BSS or an RNC and a 3G MSC | +| Iu-ps | Interface between a BSS or an RNC and a 3G SGSN | +| Iur-g | Interface between two BSSs or between a BSS and an RNC | +| Um | Interface between an MS and the GERAN | + +## 4 Layered overview of radio interface + +The Radio Resource sublayer provides the functions necessary for: + +- Radio Resource (RR) management of packet data physical channels (PDCHs); and +- Radio Link Control and Medium Access Control (RLC/MAC) on packet data physical channels. + +As shown in figure 4.1, the RR sublayer provides services to the MM and LLC sublayers. The RR sublayer utilises the services of the Data Link layer (signalling layer 2) and the Physical Link layer. The packet logical channels PBCCH, PCCCH (including PPCH, PAGCH and PRACH), PACCH and PDTCH, are multiplexed onto the packet data physical channels on a per radio block basis. + +![Protocol architecture diagram showing the MM sublayer, RR sublayer, and Data Link layer (signalling layer 2).](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The diagram illustrates the protocol architecture for the Radio Resource (RR) sublayer and RLC/MAC function. At the top, the MM sublayer is shown with two service access points: RR-SAP and GMMRR-SAP. To the right, the LLC sublayer is connected to the GMMRR-SAP via the GRR-SAP. Below the MM sublayer is the RR sublayer, which contains an RR management block. The RR sublayer provides services to the MM sublayer through the RR-SAP and GMMRR-SAP. It also interfaces with the Data Link layer (signalling layer 2) through the SAPI 0 and SAPI 3 interfaces. The Data Link layer contains logical channels: BCCH, RACH, PCH, SDCCH, AGCH, SACCH, and FACCH. The RR sublayer also includes a PD (Packet Data) block that connects to the RLC/MAC function. The RLC/MAC function is shown with logical channels: PBCH, PCCCH, and PACCH. The diagram also indicates the flow of non-RR and RR data through the PD block and the upper RLC/MAC block. + +Protocol architecture diagram showing the MM sublayer, RR sublayer, and Data Link layer (signalling layer 2). + +**Figure 4.1: Protocol architecture of Radio Resource (RR) sublayer and RLC/MAC function** + +Figure 4.2 shows how the RR sublayer provides services to the MM and LLC sublayers in EC operation. The RR sublayer utilises the services of the Data Link layer (signalling layer 2) and the Physical Link layer. The packet logical channels EC-PACCH and EC-PDTCH, are multiplexed onto the packet data physical channels on a per radio block basis or, in case a Coverage Class other than CC1 requiring the use of blind physical layer transmissions, on a predetermined number of radio blocks, using one or four PDCH(s). Blind physical layer transmissions on EC-PDTCH and EC-PACCH channels in uplink and downlink are mapped on to either 4 consecutive PDCH resources or 2 consecutive PDCH resources. The number of consecutive PDCH resources used for EC TBF operation in an EC-GSM-IoT capable cell is controlled via the EC System information type 2 message (refer to 3GPP TS 44.018). The mapping of EC logical channels onto physical channels shall be as specified in 3GPP TS 45.002. + +![Figure 4.2: Protocol architecture of Radio Resource (RR) sublayer and RLC/MAC function in EC operation. The diagram shows the MM sublayer and LLC sublayer above the RR sublayer. The RR sublayer contains RR management, RR PDUs, and RLC/MAC functions (EC-PACCH and EC-PDTCH). Interfaces GMMRR-SAP and GRR-SAP are shown between the sublayers. The RLC/MAC functions are connected to SAPI 0.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +The diagram illustrates the protocol architecture for the Radio Resource (RR) sublayer and RLC/MAC function in EC operation. At the top, the MM sublayer is shown in a dashed box. Below it, the LLC sublayer is also in a dashed box. The RR sublayer is a large solid box containing several components: + +- RR management**: A central block connected to the MM sublayer via the **GMMRR-SAP** interface. +- RR**: A block on the left side of the RR management, connected to a **PD** (Protocol Data) unit. +- upper layers' PDUs**: A block on the right side of the RR management, connected to the **RLC/MAC** block via the **GRR-SAP** interface. +- RLC/MAC**: A block below the upper layers' PDUs, which further branches into **EC-PACCH** and **EC-PDTCH**. +- SAPI 0**: Located at the bottom, connected to the EC-PACCH and EC-PDTCH blocks. + +Figure 4.2: Protocol architecture of Radio Resource (RR) sublayer and RLC/MAC function in EC operation. The diagram shows the MM sublayer and LLC sublayer above the RR sublayer. The RR sublayer contains RR management, RR PDUs, and RLC/MAC functions (EC-PACCH and EC-PDTCH). Interfaces GMMRR-SAP and GRR-SAP are shown between the sublayers. The RLC/MAC functions are connected to SAPI 0. + +**Figure 4.2: Protocol architecture of Radio Resource (RR) sublayer and RLC/MAC function in EC operation** + +## 4.1 Layer services + +The RR sublayer provides services for the transfer of upper layer PDUs using a shared medium between multiple mobile stations and the network. Direct communication is only possible between the network and one or more mobile stations. The RLC/MAC function supports three modes of operation: + +- unacknowledged operation; +- acknowledged operation; and +- non-persistent operation. + +Only acknowledged operation is supported in EC operation. + +The RR sublayer further provides services for the paging of mobile stations. + +## 4.2 Layer functions + +The RLC function defines the procedures for segmentation and reassembly of LLC PDUs into RLC/MAC blocks and, in RLC acknowledged mode of operation, for the Backward Error Correction (BEC) procedures enabling the selective retransmission of unsuccessfully delivered RLC/MAC blocks. In RLC acknowledged mode of operation, the RLC function preserves the order of higher layer PDUs provided to it. + +The RLC function provides also link adaptation. + +In EC-GSM-IoT or EGPRS in RLC acknowledged mode of operation, the RLC function may provide Incremental Redundancy (IR). + +The MAC function defines the procedures that enable multiple mobile stations to share a common transmission medium, which may consist of several physical channels. The function may allow a mobile station to use several physical channels in parallel, i.e. use several timeslots within the TDMA frame. + +For the mobile station originating access, the MAC function provides the procedures, including the contention resolution procedures, for the arbitration between multiple mobile stations simultaneously attempting to access the shared transmission medium. + +For the mobile station terminating access, the MAC function provides the procedures for queuing and scheduling of access attempts. + +When the PS handover procedure is supported the RLC and MAC functions provide the procedures for directing a mobile station to a new cell and continuing packet switched services without the use of contention resolution procedures (i.e. RACH/PRACH) in the new cell. + +When the DTM handover procedure is supported the procedures for directing a mobile station to a new cell and continuing both circuit switched and packet switched services are provided by the RLC and MAC functions, under the control of the RR function (see 3GPP TS 44.018). + +## 4.3 Service primitives + +Information flow between layers is performed by the use of Service Primitives. Service Access Points (SAP) and their corresponding Service Primitives for the RR sublayer are defined in 3GPP TS 24.007. + +## 4.4 Services required from lower layers + +The RLC/MAC function uses the services provided by the physical link layer as defined in 3GPP TS 44.004. + +The RR sublayer may use the services provided by the data link layer as defined in 3GPP TS 44.005. Moreover, the RR sublayer directly uses services provided by the physical layer such as BCCH searching, as defined in 3GPP TS 44.004. + +--- + +# 5 Introduction to the Medium Access Control (MAC) procedures + +## 5.1 General + +The Medium Access Control procedures include the functions related to the management of the shared transmission resources, e.g. the packet data physical channels and the radio link connections on packet data physical channels. + +The Medium Access Control procedures support the provision of Temporary Block Flows (TBFs) that allow the point-to-point transfer of signalling and user data within a cell between the network and a mobile station. The MAC procedures also support the provision of MBMS radio bearers that allow the point-to-multipoint transfer of signalling and user data within a cell between the network and one (or more) mobile station(s). + +Moreover, the Medium Access Control procedures include the procedures for reception of PBCCH and PCCCH, which permits autonomous cell reselection performed by the mobile station (see 3GPP TS 45.008). + +## 5.2 Multiplexing principles + +### 5.2.1 Temporary Block Flow + +A Temporary Block Flow (TBF) is a physical connection used by the two RR entities to support the unidirectional transfer of upper layer PDUs on packet data physical channels. + +The TBF is allocated radio resources on one or more assigned PDCHs and comprises a number of RLC/MAC blocks carrying one or more upper layer PDUs. If Downlink Dual Carrier is supported by both the mobile station and the + +network, the assigned PDCHs for a given TBF may be on one or two radio frequency channels. If Downlink Multi Carrier is supported by both the mobile station and the network and a DLMC configuration is used, the assigned PDCHs for the downlink TBF shall be on two or more radio frequency channels and the assigned PDCHs for the uplink TBF (if assigned) may be on one or more radio frequency channels. The maximum number of radio frequency channels the PDCHs can be assigned on is indicated by the maximum number of downlink carriers a DLMC capable MS supports, see 3GPP TS 24.008. A TBF is temporary and is maintained only for the duration of the data transfer (i.e. until there are no more RLC/MAC blocks to be transmitted and, in RLC acknowledged mode, all of the transmitted RLC/MAC blocks have been successfully acknowledged by the receiving entity). + +A TBF may operate in either GPRS TBF mode, EGPRS TBF mode or EC TBF mode. For Downlink Dual Carrier and DLMC configurations TBFs shall operate in EGPRS TBF mode. A TBF assigned in IMMEDIATE PACKET ASSIGNMENT message shall operate in EGPRS TBF mode. The network sets the TBF mode in the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, IMMEDIATE ASSIGNMENT or PACKET CS RELEASE INDICATION message, unless the TBF is assigned in EC TBF mode. The EGPRS TBF mode is only supported by EGPRS capable MSs. A TBF in EC TBF mode is assigned in an EC IMMEDIATE ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT or EC PACKET DOWNLINK ASSIGNMENT message. + +If a mobile station is assigned concurrent TBFs, these shall be in the same TBF mode. Concurrent TBFs either in same direction or opposite direction are not supported in EC operation. + +A TBF in EGPRS mode operates using one of four groups of modulation and coding schemes: + +- EGPRS-GMSK only (applicable to uplink TBFs only): this comprises MCS-1 to MCS-4 +- EGPRS: this comprises MCS-1 to MCS-9 +- EGPRS2-A: for uplink TBFs, this comprises MCS-1 to MCS-6 and UAS-7 to UAS-11; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 (only for retransmissions of blocks originally transmitted using EGPRS), MCS-7, MCS-8 and DAS-5 to DAS-12 +- EGPRS2-B: for uplink TBFs, this comprises MCS-1 to MCS-4 and UBS-5 to UBS-12; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 to MCS-9, DAS-5, DAS-6, DAS-8, DAS-9, DAS-11 and DBS-5 to DBS-12. + +The group of modulation and coding schemes to be used on a PDTCH associated with a TBF is indicated in the assignment message. The EGPRS-GMSK only group applies if the aggregate timeslot allocation is not within the indicated EGPRS multislot class, but is within the indicated GPRS multislot class. + +The use of the EGPRS2-A group for uplink or downlink is only supported by MSs which are capable of EGPRS2-A or EGPRS2-B in that direction. The EGPRS2-B group is only supported by MSs which are capable of EGPRS2-B in that direction. If a mobile station supports EGPRS2, the same group of modulation and coding schemes shall be used for all TBFs in a given direction. + +A TBF in EC TBF mode operates using one of two groups of modulation and coding schemes (both applicable to both uplink and downlink TBFs): + +- EGPRS-GMSK only: this comprises MCS-1 to MCS-4 +- EGPRS: this comprises MCS-1 to MCS-9 + +If a mobile station indicates support of Reduced Latency (see 3GPP TS 24.008), it may be assigned TBFs with FANR activated (see sub-clause 9.1.14), either in BTTI configuration, RTTI configuration or (if the mobile additionally supports MTI configurations) MTI configuration. If a mobile station indicates support of FANR (see 3GPP TS 24.008), it may be assigned TBFs with FANR activated (see sub-clause 9.1.14) in BTTI configuration only. The network shall ensure that, if a mobile station is assigned a TBF with FANR activated, FANR shall be activated for all concurrent TBFs assigned to that mobile station. + +For the case where a mobile station supports multiple TBF procedures the maximum number of TBFs it can support concurrently is not specified. Mobile station implementations are expected to ensure that the mobile station can support a sufficient number of TBFs to operate all the PDP contexts it has activated. As such, a mobile station may choose to release, modify or activate one or more PDP contexts when prioritizing the services it wants to operate concurrently. + +The network is not required to consider any potential complexity limitations regarding the number of concurrent TBFs when establishing an uplink or downlink TBF for a mobile station that supports multiple TBF procedures. + +The following messages are used only if both the mobile station and the network support multiple TBF procedures: + +- MULTIPLE TBF UPLINK ASSIGNMENT +- MULTIPLE TBF DOWNLINK ASSIGNMENT +- MULTIPLE TBF TIMESLOT RECONFIGURE. + +## 5.2.2 Temporary Flow Identity + +Each TBF is assigned a Temporary Flow Identity (TFI) by the network. The mobile station shall assume that the TFI value is unique among concurrent TBFs in the same direction (uplink or downlink) on all PDCHs used for the TBF. In (E)GPRS, the same TFI value may be used concurrently for TBFs on other PDCHs in the same direction and for TBFs in the opposite direction. In EC-GSM-IoT the same TFI value may be used for EC TBFs on different PDCHs in the same direction and for EC TBFs in opposite direction. In EC operation a mobile station shall only support one ongoing EC TBF. For a TBF with FANR activated, the TFI value shall be unique among concurrent TBFs assigned to one mobile station in the same direction (uplink or downlink). If Enhanced Multiplexing for Single TBF (EMST) is used, the network shall assign, according to the rules above, a unique TFI value to each RLC entity multiplexed on the TBF. If Enhanced Multiplexing for Single RLC Entity (EMSR) is supported by a mobile station the network may allocate multiple PFCs on a common RLC entity where at least two of these PFCs are allocated a unique TFI value (see sub-clause 5.12). The downlink TBF of a mobile station in a DLMC configuration may be assigned an eTFI if the maximum number of downlink timeslots the mobile supports is greater than 20. The eTFI supplements the TFI so that combined they uniquely identify the downlink TBF on all of the PDCH resources allocated for that TBF on a given downlink carrier. The TBF may be assigned different eTFI – TFI combinations for each downlink carrier used in a given DLMC configuration. If a mobile station receives an RLC/MAC control block which includes a downlink TFI equal to a TFI supported by a downlink TBF assigned to the mobile station, which is received on a timeslot or PDCH-pair which is not a timeslot or PDCH-pair which is assigned to the mobile station as part of that TBF, the mobile station shall consider that message as not addressed to it. If a mobile station receives an RLC/MAC control block which includes an uplink TFI equal to a TFI supported by an uplink TBF assigned to the mobile station, which is received on a timeslot or PDCH-pair which does not correspond to a timeslot or PDCH-pair which is assigned to the mobile station as part of that TBF, the mobile station shall consider that message as not addressed to it. + +NOTE: The behaviour of the mobile station in case it receives a control block not addressed to it is specified in sub-clause 10.4.10 + +An RLC/MAC block associated with a certain TBF shall comprise a TFI. The TBF is identified by the TFI together with, in case of a RLC data block, the direction (uplink or downlink) in which the RLC data block is sent; and in case of a RLC/MAC control message, the direction in which the RLC/MAC control message is sent and the message type. In the case of a DLMC configuration where a downlink TBF is assigned an eTFI on a specific downlink carrier, an RLC/MAC block associated with that TBF on that downlink carrier shall comprise a TFI and an eTFI (see sub-clause 10.0.a.2). + +Global\_TFI is used to unambiguously identify the mobile station in packet transfer mode, MAC-Shared state, dual transfer mode or MAC-DTM state within an uplink or downlink RLC/MAC control message. In the case of a DLMC configuration and a mobile station supporting eTFI, Global\_TFI and eTFI may be used to unambiguously identify the mobile station in packet transfer mode within a downlink RLC/MAC control message. If present, the Global\_TFI addresses the MS using either: + +- an uplink TFI identifying an uplink TBF assigned to the MS such that the timeslot or PDCH-pair on which the Global\_TFI is sent corresponds to a timeslot or PDCH-pair assigned to that TBF, or +- a downlink TFI identifying a downlink TBF assigned to the MS such that the timeslot or PDCH-pair on which the Global\_TFI is sent is a timeslot or PDCH-pair assigned to that TBF. + +If there is a choice of TFI to use, which TFI is used is at the discretion of the sender except where explicitly defined by procedure. For the mobile station in broadcast/multicast receive mode, the Global\_TFI includes the MBMS Bearer Identity of the MBMS radio bearer the RLC/MAC control message relates to (in the most significant bit(s) of the DOWNLINK\_TFI field) and, where explicitly defined by procedure, the current MS\_ID of the mobile station the message relates to (in the remaining least significant bit(s) of the DOWNLINK\_TFI field). + +### 5.2.3 Uplink State Flag + +An Uplink State Flag (USF) is included in the header of each RLC/MAC block on a downlink PDCH, as specified in clause 10. It may be used by the network to control the multiplexing of different mobile stations and TBFs on an uplink PDCH. The use of USF is further specified in 3GPP TS 45.002. + +### 5.2.4 Medium Access modes + +Four medium access modes are supported: + +- Dynamic Allocation, characterised by that the mobile station detecting an assigned USF value for each assigned uplink PDCH when operating in BTTI configuration or each assigned uplink PDCH-pair when operating in RTTI configuration-and block or group of four blocks that it is allowed to transmit on that PDCH/PDCH-pair (see sub-clause 8.1.1.1); +- Extended Dynamic Allocation is characterised by the mobile station detecting an assigned USF value for any assigned uplink PDCH when operating in BTTI configuration or any assigned uplink PDCH-pair when operating in RTTI configuration, allowing the mobile station to transmit on that PDCH/PDCH-pair and all higher numbered assigned PDCHs/PDCH-pairs in the same block or group of four blocks (see sub-clause 8.1.1.2); +- Exclusive Allocation, characterised by the mobile station being granted the exclusive right to transmit on the assigned PDCH/H for the duration of an uplink TBF (see sub-clause 8.1.1.3a). Exclusive allocation is applicable only in dual transfer mode. When using exclusive allocation, only one TBF shall be established in the uplink. +- Fixed Uplink Allocation, characterised by the mobile station being allocated uplink resources in an (EC-)AGCH assignment message or in an RLC/MAC control message (see sub-clause 8.1.1.3b). Fixed uplink allocation is applicable only in EC TBF mode. The uplink resources are allocated according to the uplink Coverage Class that the mobile station is assigned. + +Dynamic Allocation medium access mode shall be supported by all networks that support GPRS. The support of Extended Dynamic Allocation is optional for the network. + +Dynamic Allocation shall be supported in all mobile stations, except if the mobile station only supports EC operation in which case only Fixed Uplink Allocation needs to be supported. The support of Extended Dynamic Allocation is mandatory for mobile stations of multislot classes 22, 24, 25 and 27, for multislot class type 1 mobile stations that can transmit on three or more timeslots (either PDCH or TCH), and for mobile stations supporting Flexible Timeslot Assignment (see 3GPP TS 24.008). The support of Extended Dynamic Allocation for other mobile stations is optional and shall be indicated in the MS Radio Access Capability. + +NOTE: Flexible Timeslot Assignment is applicable only when Extended Dynamic Allocation is used, or as explicitly indicated for certain RTTI configurations in 3GPP TS 45.002. + +The exclusive allocation shall be used in dual transfer mode during uplink operation with a half-rate PDCH. + +The network shall ensure that the medium access mode and the resource allocation used for a mobile station are compatible with the permitted multislot configurations (see 3GPP TS 45.002). + +### 5.2.4a Multiplexing of GPRS, EGPRS and EGPRS2 capable mobile stations + +GPRS, EGPRS, EGPRS2 and EC GSM-IoT capable mobile stations can be multiplexed dynamically on the same PDCH. + +If dynamic or extended dynamic allocation is used, a mobile station shall be able to decode the USF that allocates the uplink to that mobile station as follows, + +- For a mobile station supporting only GPRS the network shall use GMSK modulation, i.e. either CS-1 to CS-4 or ,MCS-0, MCS-1 to MCS-4, in those blocks. The other blocks may use other modulations. +- For a mobile station supporting EGPRS, the network may use either GMSK modulation or 8-PSK modulation, i.e. CS-1 to CS-4, MCS-0, MCS-1 to MCS-4, MCS-5 to MCS-9 or DAS-5 to DAS-7 in those blocks. +- For a mobile station supporting EGPRS2-A in the downlink, the network may use either GMSK, 8-PSK, 16-QAM or 32-QAM modulation with normal symbol rate, i.e. CS-1 to CS-4, MCS-0, MCS-1 to MCS-9 or DAS-5 to DAS-12 in those blocks. + +- For a mobile station supporting EGPRS2-B in the downlink, the network may use GMSK, 8-PSK, 16-QAM and 32-QAM modulations with normal symbol rate, or QPSK, 16-QAM or 32-QAM modulations with higher symbol rate in those blocks, i.e. CS-1 to CS-4, MCS-0, MCS-1 to MCS-9, DAS-5 to DAS-12 or DBS-5 to DBS-12. +- For a mobile station supporting eTFI, the network may use CS-1 for RLC/MAC control blocks irrespective of whether or not the RLC/MAC control blocks are associated with a TBF assigned an eTFI (see sub-clause 5.2.2, 8.1.1.1.1 and 8.1.1.2.2). + +One exception to the list above is for mobile stations not supporting eTFI where the network shall not use RLC/MAC control blocks associated with a TBF assigned an eTFI. + +If Fixed Uplink Allocation is used, the mobile station does not decode any USF for uplink allocation. The USF shall however be included in downlink RLC blocks sent to a mobile station in EC operation in case another mobile station using dynamic or extended dynamic allocation is monitoring the same downlink channel. + +A mobile station assigned an uplink TBF using FANR shall be able to decode the PAN in a downlink block. If the PAN is addressed to a mobile station other than the one to which the data in the RLC/MAC block is addressed, then the network may use in this block any of the modulation and coding schemes allowed for USF transmission to that mobile station. One exception applies for a mobile station not supporting eTFI in which case the network shall not address the PAN to that mobile station if the RLC/MAC block is associated with a TBF assigned an eTFI (see sub-clause 8.1.2.1) unless the assigned eTFI field equals '000'. For a mobile station supporting eTFI (see sub-clause 5.2.2) the network may address the PAN to that mobile station irrespective of whether or not the RLC/MAC block is associated with a TBF assigned an eTFI. + +NOTE 1: The stealing bits in the EGPRS GMSK blocks are set to indicate CS-4. The coding and interleaving of the USF is done as defined for CS-4. That leads to: + +- 1) A GPRS mobile station is able to detect the USF in EGPRS GMSK blocks. The risk that the rest of the block will be misinterpreted as valid information is low; +- 2) An EGPRS mobile station cannot differentiate CS-4 blocks from EGPRS GMSK blocks by decoding the stealing bits only. However, an EGPRS mobile station in EGPRS TBF mode needs only to decode GMSK blocks assuming either of MCS-1 to MCS-4, in order to determine if they were aimed for it. + +NOTE 2: Due to mobile station synchronisation reasons, special requirements apply for the scheduling, the modulation and coding scheme and the output power of blocks that are transmitted to a mobile station with an active uplink or downlink TBF, see 3GPP TS 45.008. + +A mobile station shall only attempt to decode USF or PAN in a downlink radio block transmitted using a TSC it has been assigned. A mobile station that supports the extended TSC sets (see 3GPP TS 45.002 [32]) can have up to two TSCs assigned for a given PDCH and shall attempt to decode USF or PAN in a downlink radio block it receives on that PDCH using its assigned TSC(s). + +## 5.3 Packet idle mode + +In packet idle mode no temporary block flow (TBF) exists. + +In packet idle mode, the mobile station monitors the relevant paging subchannels on PCCCH, if such is present in the cell. If a PCCCH is not present in the cell, the mobile station monitors the relevant paging subchannels on CCCH or, if the mobile station has enabled EC operation, on EC-CCCH. + +In packet idle mode, upper layers may require the transfer of an upper layer PDU, which implicitly triggers the establishment of a TBF and the transition to packet transfer mode. + +In packet idle mode, upper layers may require the establishment of an RR connection. When the mobile station enters dedicated mode (see 3GPP TS 44.018), it may leave the packet idle mode, if the mobile station limitations make it unable to handle the RR connection and the procedures in packet idle mode simultaneously. A mobile station that has enabled PEO may use mobile originated RR connection establishment for GSM services (see 3GPP TS 23.060 [19]) while in packet idle mode. If it establishes a RR connection then it shall leave the packet idle mode and shall only re-enter packet idle mode when the RR connection is released. + +In packet idle mode, if a mobile station starts listening to an MBMS radio bearer, it shall enter broadcast/multicast receive mode (see sub-clause 5.3.1). + +### 5.3.1 Broadcast/multicast receive mode + +In broadcast/multicast receive mode, the mobile station listens to an MBMS radio bearer. + +Broadcast/multicast receive mode can only be entered by a mobile station when in packet idle mode; when leaving broadcast/multicast receive mode, the mobile station shall return to packet idle mode. + +Whenever a mobile station leaves broadcast/multicast receive mode to enter packet transfer mode, upon returning to packet idle mode it may re-enter broadcast/multicast receive mode to resume the reception of the ongoing MBMS session(s). + +The mobile station receives the system information and paging messages on the (P)BCCH and (P)CCCH as specified for packet idle mode or on the PACCH/D associated with the MBMS radio bearer, depending on the value of the MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT and MBMS NEIGHBOURING CELL INFORMATION messages. + +If the use of in-band signalling has been indicated (by the MBMS In-band Signalling Indicator), only mobile stations that have an MS\_ID on the MBMS radio bearer shall be addressed with paging messages on the PACCH/D of that MBMS radio bearer. Mobile stations without an MS\_ID shall continue monitoring their paging groups on the paging channel(s) on the (P)CCCH and skip the reception of the radio blocks of the MBMS radio bearer that prevent the monitoring of their paging groups, if needed. In this specification, requirements for mobile stations in packet idle mode apply also to mobile stations in broadcast/multicast receive mode unless stated otherwise. + +## 5.4 Packet transfer mode + +In packet transfer mode, the mobile station is allocated radio resources providing one or more TBFs for physical point-to-point connection(s) on one or more packet data physical channels for the unidirectional transfer of upper layer PDUs between the network and the mobile station. Successive transfer of one or more upper layer PDUs is possible. Concurrent TBFs may be established in opposite directions, unless the mobile station is in EC operation. The RR sublayer provides the following services: + +- transfer of upper layer PDUs in RLC acknowledged mode; +- transfer of upper layer PDUs in RLC unacknowledged mode; +- transfer of upper layer PDUs in RLC non-persistent mode. + +Only RLC acknowledged mode is supported for an EC TBF. + +When a transfer of upper layer PDUs terminates, in either downlink or uplink direction, the corresponding TBF is released. In packet transfer mode, when all TBFs have been released, in downlink and uplink direction, the mobile station returns to packet idle mode. + +In packet transfer mode, upper layers may require the establishment of an RR connection. When the mobile station enters dedicated mode (see 3GPP TS 44.018), it may abort all ongoing TBFs and leave the packet transfer mode, if the mobile station limitations make it unable to handle the RR connection and the procedures in packet transfer mode simultaneously. A MS that has enabled PEO may use mobile originated RR connection establishment for GSM services (see 3GPP TS 23.060 [19]) while in packet transfer mode in which case it shall abort the ongoing TBFs, leave packet transfer mode and enter packet idle mode when the RR connection is released. + +In packet transfer mode, a mobile station that supports PS handover may be ordered to move to a new cell through the use of a PS HANDOVER COMMAND message that provides resources to be used for one or more of its ongoing TBFs in the new cell (e.g. TBF resources in the new cell that have been pre-allocated by the target BSS). A mobile station indicates that it supports PS handover in the PS Handover Capability field/GAN PS Handover Capability field in the *MS Radio Access Capability* IE (see 3GPP TS 24.008). An E-UTRAN capable mobile station indicates that it supports PS handover to E-UTRAN in the "GERAN to E-UTRAN support in GERAN packet transfer mode" field of the *MS Radio Access Capability* IE (see 3GPP TS 24.008). The network may initiate the PS handover procedure as a result of various trigger conditions as described in sub-clause 8.10.3.1. The PS handover procedure is described in sub-clause 8.10. + +## 5.4a Dual transfer mode + +In dual transfer mode, the mobile station is allocated radio resources providing an RR connection on a dedicated traffic channel and one or more TBFs on one or more packet data physical channels. The allocation of radio resources for the RR connection and the TBFs is co-ordinated by the network, in agreement with the capabilities of the mobile station in dual transfer mode. + +If a mobile station that supports multiple TBF procedures has entered dual transfer mode where an uplink TBF is operating in exclusive allocation mode then no additional uplink TBFs may be requested. If exclusive allocation is not used a mobile station in dual transfer mode that supports multiple TBF procedures may request the establishment of one or more additional uplink TBFs by sending a PACKET RESOURCE REQUEST message on the PACCH. If this occurs and the network determines that re-allocation of the RR connection is required before it can satisfy the requested TBFs it sends the mobile station a DTM ASSIGNMENT COMMAND message to reallocate the RR connection and a combination of one or more ongoing uplink and downlink TBFs as specified in 3GPP TS 44.018. + +Successive transfer of one or more upper layer PDUs is possible. Concurrent TBFs may be established in opposite directions. Mobile stations supporting multiple TBF procedures may have multiple concurrent TBFs established in opposite directions. The transfer of upper layer PDUs in RLC acknowledged or RLC unacknowledged mode is provided. + +When a transfer of upper layer PDUs terminates, in either downlink or uplink direction, the corresponding TBF is released. In dual transfer mode, when all TBFs have been released, in downlink and uplink directions, the mobile station enters dedicated mode. + +In dual transfer mode, at the release of the RR connection, the mobile station may abort all ongoing TBFs and enter packet idle mode. If the mobile station and the network support enhanced DTM CS release procedure the mobile station may continue in packet transfer mode without entering packet idle mode, after the release of the RR connection. + +## 5.5 General procedures in packet idle and packet transfer modes + +Unless explicitly stated, the requirements in this sub-clause (and sub-clauses) apply only in packet idle mode and in packet transfer mode, neither in dedicated mode nor in dual transfer mode. + +### 5.5.1 Mobile station side + +The mobile station in either packet idle or packet transfer modes shall monitor the system information broadcast in the cell. A MS that has enabled PEO shall monitor system information as described in 3GPP TS 44.018 [11] while in packet idle mode and is not required to monitor system information while in packet transfer mode. A mobile station in EC operation shall not monitor the system information broadcast in the cell when in packet transfer mode. + +In packet idle mode, the mobile station shall monitor the radio blocks on PCCCH, CCCH or EC-CCCH, as defined in sub-clauses 5.5.1.5 and 5.5.1.6. The determination of the paging group for the mobile station is defined in 3GPP TS 45.002. + +#### 5.5.0.1 Indication of a selected PLMN using PLMN Index + +A mobile station supporting network sharing shall indicate the selected PLMN to the network when sending an upper layer PDU using a foreign TLLI or a random TLLI (see 3GPP TS 23.003) address for this transmission. The mobile station shall set the value of the *Selected PLMN Index* field in the first RLC data block used to transfer the PDU (see sub-clauses 10.4.14 and 10.4.14a.) to whichever of the following was the most recently received: + +- the corresponding PLMN ID index of the selected PLMN, if the selected PLMN is acquired from the system information when the SI22IND field contained in the *Control Channel Description* IE in the SYSTEM INFORMATION TYPE 3 message (see 3GPP TS 44.018) indicates that network sharing is used; or +- the Selected PLMN Index received in the PS HANDOVER COMMAND message; or +- the Selected PLMN index as indicated by the PLMN Index IE received in the CS HANDOVER COMMAND or DTM HANDOVER COMMAND (see 3GPP TS 44.018); or +- for a mobile station in EC operation, the corresponding PLMN ID index of the selected PLMN, if the selected PLMN is acquired from the EC SYSTEM INFORMATION TYPE 4 message (see 3GPP TS 44.018). + +### 5.5.0.2 Indication of DCN-ID + +A mobile station supporting MS assisted Dedicated Core Network selection shall indicate the DCN-ID (corresponding to its selected PLMN) to a network supporting MS assisted Dedicated Core Network selection when sending an upper layer PDU using a foreign TLLI or a random TLLI (see 3GPP TS 23.003) address for this transmission. The mobile station shall set the value of the *DCN-ID* in the first RLC data block used to transfer the PDU (see sub-clauses 10.4.14 and 10.4.14a.) according to the *DCN-ID* value indicated by upper layers (see 3GPP TS 23.401 [54] and 3GPP TS 24.008 [51]). + +#### 5.5.1.1 Cell reselection + +Cell reselection in packet idle and packet transfer modes is specified in 3GPP TS 45.008. The RR entity on the mobile station side indicates to the upper layers the availability of a cell and a cell change when decided by the RR sublayer. Upper layers are advised of system information broadcast in the cell when a new cell has been selected, or when a relevant part of this information changes. + +When the mobile station reselects a new (target) cell, the support of GPRS in the target cell is indicated in system information sent on BCCH, see 3GPP TS 44.018. If the mobile station has received a PBCCH description for the target cell, it shall assume that GPRS is supported, without further receiving system information on BCCH. The support for EC GSM-IoT in the target cell is indicated by the presence of the EC-SCH. + +NOTE: A PBCCH description for the target cell may be received in the packet system information (neighbour cell information in PS13 and 3bis) and/or in the MBMS NEIGHBOURING CELL INFORMATION message (for a mobile station in broadcast/multicast receive mode) in the old serving cell, or in a BCCH message (SI13) in the target cell. + +If a cell supports GPRS, the mobile station may perform packet access. If a cell does not support GPRS, the mobile station is not allowed to perform packet access. + +If a cell supports EC-GSM-IoT, a mobile station that is EC-GSM-IoT capable may enable EC operation and perform packet access to request a TBF in EC TBF mode. If a cell does not support EC-GSM-IoT, the mobile station may not enable EC operation in that cell and it may not perform packet access to request a TBF in EC TBF mode. + +When a cell reselection is determined by the mobile station or ordered by the network, the mobile station may continue its operation in packet idle or in packet transfer mode in the old serving cell, while acquiring certain system information for the target cell. + +When a cell reselection is determined by the mobile station in broadcast/multicast receive mode shall leave the old serving cell immediately if the distribution of MBMS NEIGHBOURING CELL INFORMATION messages is not supported in the old serving cell (see sub-clause 7.7.3). If the distribution of MBMS NEIGHBOURING CELL INFORMATION messages is supported in the old serving cell, the mobile station shall continue its operation in broadcast/multicast receive mode in the old serving cell as follows: + +- if the mobile station has received for the target cell the MBMS bearer description for each session it is acquiring it shall leave the cell immediately after it receives an MBMS NEIGHBOURING CELL INFORMATION message for that target cell with the same MBMS\_PTM\_CHANGE\_MARK as the last one received (see note), or after 1s after cell reselection is determined, whichever occurs first; +- otherwise the mobile station shall leave the cell immediately after 1s after cell reselection is determined. + +NOTE 1: An MBMS\_PTM\_CHANGE\_MARK is one received in an MBMS NEIGHBOURING CELL INFORMATION message for a session the mobile station is acquiring. + +NOTE 2: The behaviour of the mobile station after leaving the old serving cell is described in sub-clause 8.1.6. + +If the old cell does not support CCN, the operation in the old cell shall be aborted when one of the following conditions are met: + +- the mobile station starts to receive information on PBCCH in the target cell; +- the mobile station has received the SI13 message (see 3GPP TS 44.018) and there is no PBCCH present in the target cell; or + +- the criteria for camping on the old cell are no longer fulfilled (see 3GPP TS 45.008). + +For a mobile station that has enabled EC operation, the operation in the old cell shall be aborted when one of the following conditions are met: + +- the mobile station starts to receive information on BCCH or EC-BCCH in the target cell; or +- the criteria for camping on the old cell are no longer fulfilled (see 3GPP TS 45.008). + +If PBCCH is present in the target cell, the mobile station shall delay the start of receiving information on PBCCH until the first occurrence of PSI1 in block B0. If the reception of PSI1 or PSI2 messages fails (see sub-clause 5.5.1.2) the mobile station may re-establish and continue its operation in the old cell, until the next occurrence of PSI1 in block B0, unless the mobile station is in broadcast/multicast receive mode and performs fast reception resumption (see sub-clause 8.1.6.2) of at least one MBMS session in the target cell. + +While the operation is maintained in the old cell, the mobile station may suspend its TBF(s) or suspend the monitoring of radio blocks on PCCCH and CCCH, in order to receive necessary information on BCCH in the target cell. Such suspension may be required in both packet idle and packet transfer modes, but shall not apply in broadcast/multicast receive mode. It is performed without notification to the network. + +Suspension of the operation in the old cell for this purpose is allowed during the time required, for each message and according to the mobile station's multislot class, to receive the required messages on BCCH in the target cell. The allowable suspension of an uplink TBF may be extended with one block period, in case of dynamic or extended dynamic allocation, if the mobile station is unable to receive the corresponding USF due to the suspension of downlink operation. + +When the conditions are fulfilled to switch to the new cell, the mobile station shall abort all TBFs in progress by immediately ceasing to decode the downlink, ceasing to transmit on the uplink, stopping all RLC/MAC timers except for timers related to measurement reporting. The mobile station shall then switch to the identified specified new cell and shall obey the relevant RLC/MAC procedures on this new cell. + +If the old cell supports CCN, a mobile station shall, when the cell reselection has been determined for other reason than path loss criterion parameter C1 becomes negative, follow the procedures for Network Assisted Cell Change as specified in sub-clauses 5.5.1.1a.2 and 8.8.2. + +If the old cell supports CCN, a mobile station may, when the cell reselection has been determined because the path loss criterion parameter C1 has become negative, follow the procedures for Network Assisted Cell Change as specified in sub-clauses 5.5.1.1a.2 and 8.8.2. + +Under no circumstances and independent of whether CCN mode is supported, operations in the old cell shall be continued more than 5 s after a cell reselection has been determined. + +### 5.5.1.1a Network Assisted Cell Change + +The mobile station shall support the Network Assisted Cell Change procedures. The Network Assisted Cell Change consists of two independent procedures: + +- One procedure that can assist a mobile station in packet transfer mode or MAC-Shared state with neighbour cell system information for a GSM neighbouring cell required for initial packet access after a cell change; +- one procedure in which the mobile station notifies the network when it has determined to reselect to another GSM, to a 3G, or to an E-UTRAN cell and delays the cell re-selection (CCN mode procedures) to let the network e.g. in the case of reselection to a GSM cell, respond with neighbour cell system information. + +The Network Assisted Cell Change procedures are part of the *GERAN Feature Package 1*. A mobile station indicating support of the *GERAN Feature Package 1* in the Mobile Station Classmark 3 IE, the MS Radio Access Capability IE and the MS Radio Access Capability 2 IE supports the Network Assisted Cell Change procedures (see 3GPP TS 24.008). + +#### 5.5.1.1a.1 Neighbour Cell System Information Distribution + +The network may send GSM neighbour cell system information to a mobile station in packet transfer mode or MAC-Shared state. A mobile station, which receives this information, shall store the information for 30 seconds and during that period the information can be used for initial access in the neighbour cell (see sub-clause 8.8.1). + +### 5.5.1.1a.2 CCN Mode + +A mobile station, which has *CCN Enabled*, can enter *CCN Mode*. + +The mobile station shall enable CCN when the following criteria are fulfilled: + +- the mobile station is camping on a cell (see 3GPP TS 45.008); and +- the network indicates CCN ACTIVE/3G CCN ACTIVE/E-UTRAN CCN ACTIVE either in system information to all mobile stations in the cell or in an individual order to a certain mobile station; and +- the mobile station is neither in dedicated mode nor Dual Transfer Mode; and +- the mobile station is in NC0 or in NC1 mode; and +- the mobile station is in Packet Transfer mode. + +The CCN procedures and the criteria for entering and leaving CCN mode are specified in sub-clauses 8.8.2 and 8.8.3. + +### 5.5.1.1b Release of RR connection + +#### 5.5.1.1b.1 General + +After the release of an RR connection (see 3GPP TS 44.018, *Normal release procedure and Abnormal cases*), if the mobile station during the RR connection is unable to monitor the system information broadcast on BCCH or PBCCH (i.e. GPRS class B or GPRS class A mode of operation using DTM), the mobile station shall acquire the system information broadcast in the serving cell. The acquisition of system information shall be performed according to the requirements in sub-clause 5.5.1.2 (PBCCH present in the cell) or sub-clause 5.5.1.3 (PBCCH not present in the cell). The mobile station shall not attempt a packet access or accept a packet downlink assignment before those requirements are fulfilled. + +The following exceptions, stated in sub-clauses 5.5.1.1b.2 to 5.5.1.1b. 5, may apply. + +#### 5.5.1.1b.2 Continuation of PBCCH information + +At the establishment of an RR connection and if PBCCH is present in the cell, the mobile station may keep the PSI messages received on PBCCH before the RR connection establishment. + +If the RR connection is established, maintained and released in the same serving cell and the MS has received PSI14 messages or received and acted upon PSI1 messages during dual transfer mode at least every 30 seconds such that + +- for PSI1, the value of the PBCCH\_CHANGE\_MARK has indicated no change in the PSI messages (see sub-clause 5.5.1.2.1), and +- for PSI14, all instances of the PSI14 messages indicate no change in the contents of PSI messages, + +the mobile station may resume the supervision of PBCCH\_CHANGE\_MARK and update of PBCCH information, defined in sub-clause 5.5.1.2.1, and need not initiate a *complete acquisition* of PBCCH information, as specified in sub-clause 5.5.1.2. + +#### 5.5.1.1b.3 Continuation of BCCH information + +At the establishment of an RR connection and if PBCCH is not present in the cell, the mobile station may keep the SI messages received on BCCH before the RR connection establishment. + +If the RR connection is established, maintained and released in the same serving cell and the MS has received PSI14 messages or received and acted upon PSI13/SI13 messages during dual transfer mode at least every 30 seconds such that the value of the BCCH\_CHANGE\_MARK has indicated no change in the SI messages (see sub-clause 5.5.1.3.1), the mobile station may resume the supervision of BCCH\_CHANGE\_MARK and update of BCCH information, defined in sub-clause 5.5.1.3.1, and need not initiate a *complete acquisition* of BCCH information, as specified in sub-clause 5.5.1.3. + +#### 5.5.1.1b.4 Receipt of PSI14 message in dual transfer mode + +In dual transfer mode, the mobile station may receive the PSI14 message on PACCH in the serving cell. If the RR connection is released in the same serving cell within 30 s after the PSI14 message was last received, the mobile station + +may use the PSI14 message as a substitute for the SI13 message after the release of the RR connection, until the SI13 message has been received or the mobile station starts to receive information on PBCCH. + +The presence of a PBCCH in the cell is indicated by a PBCCH description in the PSI14 message. If the message does not contain the PBCCH description, the mobile station shall assume that PBCCH is not present in the cell. + +After the release of the RR connection and if PBCCH is present in the cell, the mobile station shall perform a *complete acquisition* of PBCCH information, as defined in sub-clause 5.5.1.2. + +After the release of the RR connection and if PBCCH is not present in the cell, the mobile station shall perform a *complete acquisition* of BCCH information, as defined in sub-clause 5.5.1.3. The mobile station shall attempt to receive the SI13 (or PSI13) message within 30 s after the last receipt of the PSI14 message. + +#### 5.5.1.1b.5 Acquisition of system information for enhanced DTM CS release procedure in dual transfer mode + +If the mobile station and the network support enhanced DTM CS release procedure, the network may delay the release of the RR connection until the mobile station has received the needed system information, in order to maintain the radio resources on the PDCH(s) after the release of the RR connection. + +The network initiates enhanced DTM CS release by sending the PACKET CS RELEASE INDICATION message on PACCH with the ENHANCED\_DTM\_CS\_RELEASE\_INDICATION parameter set to indicate that the RR connection is to be released (i.e. upon subsequent transmission of the CHANNEL RELEASE message to the mobile station) and starts timer T3197. + +On receipt of PACKET CS RELEASE INDICATION message with the ENHANCED\_DTM\_CS\_RELEASE\_INDICATION parameter set to indicate that the RR connection is to be released, the mobile station shall send the PACKET SI STATUS (respectively PACKET PSI STATUS if the PBCCH is present) message on PACCH to indicate which system information messages were stored while in the dual transfer mode by the mobile station. The following system information (respectively packet system information) messages are required to maintain radio resources and enter packet transfer mode after the release of the RR connection: + +- PSI1, PSI2 and PSI14 in the *Received PSI Message List*; or respectively +- SI13, SI3 and SI1, if present, in the *Received SI Message List*. + +The PSI (respectively SI) messages listed above shall be indicated as the first PSI (respectively SI) messages indicated in the PACKET PSI STATUS (respectively PACKET SI STATUS) messages. If other PSI (respectively SI) messages are indicated in the PACKET PSI STATUS (respectively PACKET SI STATUS) message, the priority order defined in Table 5.5.1.4.3.1 shall apply. + +In case the mobile station has no information available to determine whether PBCCH is allocated in the cell or not, the mobile station shall transmit the PACKET SI STATUS message where an empty *Received SI Message List* is indicated. Upon reception of such message, the network shall determine that the mobile station has no knowledge whether PBCCH is present in the cell. In this case the network shall start transmitting the PSI messages if PBCCH is present in the cell or, otherwise, SI messages. + +The mobile station may request the release of the RR connection and packet resources (e.g. if combined RAU procedure shall be performed after the release of the RR connection) with *PS\_REL\_REQ* field sent in the PACKET SI STATUS (respectively PACKET PSI STATUS) message. + +On receipt of the PACKET SI STATUS (respectively PACKET PSI STATUS) message the network shall send the missing system information messages by using the PACKET SERVING CELL SI message or it shall send respectively the corresponding packet system information messages. + +The mobile station is allowed to send the PACKET SI STATUS (respectively PACKET PSI STATUS) message twice and the second sending occurrence of this message shall take place at the first suitable opportunity at least one second after the first transmission of that message. Whenever the mobile station has received all required system information (respectively packet system information) messages, it shall send the PACKET SI STATUS (respectively PACKET PSI STATUS) message at the first suitable opportunity, even if it has already sent the PACKET SI STATUS (respectively PACKET PSI STATUS) twice. + +When the network receives the PACKET SI STATUS (respectively PACKET PSI STATUS) message indicating that all required system information (respectively packet system information) messages have been received by the mobile + +station it shall stop timer T3197, start timer T3109 (see 3GPP TS 44.018) and send the CHANNEL RELEASE message on the main DCCH indicating that the mobile station is allowed to continue in packet transfer mode after the release of the RR connection (see 3GPP TS 44.018). Upon reception of the CHANNEL RELEASE message the mobile station shall release the RR connection, continue in packet transfer mode and re-configure the packet resources (if provided by the PACKET CS RELEASE INDICATION message). + +If continuous timing advance parameters are provided to the mobile station in the PACKET CS RELEASE INDICATION message, the mobile station shall start the continuous timing advance procedure upon entering packet transfer mode. The mobile station shall use the last timing advance value received whilst in dual transfer mode until a new value of the timing advance is provided to the mobile station according to the procedures defined for packet transfer mode. + +If timer T3197 expires before the network receives the PACKET SI STATUS (respectively PACKET PSI STATUS) message indicating that all required system information (respectively packet system information) messages have been received by the mobile station, the network shall release the RR connection by sending the CHANNEL RELEASE message on the main DCCH indicating that the mobile station is not allowed to continue in packet transfer mode after the release of the RR connection (see 3GPP TS 44.018). + +### 5.5.1.1c Inter-RAT cell re-selection based on priority information + +#### 5.5.1.1c.1 General + +The network may provide priority information to enable priority-based cell reselection (see 3GPP TS 45.008). Inter-RAT cell reselection based on priority information applies only in case of autonomous cell reselection. + +Two sets of priorities are defined for inter-RAT cell re-selection based on priority information: common priorities (see sub-clause 5.5.1.1c.2) and individual priorities (see sub-clause 5.5.1.1c.3). The mobile station shall delete all priorities when switched off. + +While providing common or individual priorities, the network shall ensure that the GERAN priority value is different from all E-UTRAN priority values and from all UTRAN priority values, and that all UTRAN priority values are different from all E-UTRAN priority values. In addition, if for some E-UTRAN frequencies THRESH\_E-UTRAN\_high\_Q is provided in the *Enhanced Cell Reselection Parameters Description* IE in the PACKET MEASUREMENT ORDER message, the network shall ensure that the priority value for any frequency for which THRESH\_E-UTRAN\_high\_Q is provided is different from the priority value for all frequencies for which THRESH\_E-UTRAN\_high\_Q is not provided. + +The mobile station shall determine each set, considering only individual priorities (respectively common priorities) when building the set of individual (respectively common) priorities. The mobile station shall perform the following steps, in the specified order: + +- If the same priority value is assigned to GERAN and to one or more UTRAN or E-UTRAN frequencies then all such UTRAN and E-UTRAN priority values are considered as not in the set of priorities. +- If the same priority value is assigned to one or more UTRAN frequencies and one or more E-UTRAN frequencies, then all such priority values are considered as not in the set of priorities. +- If the same priority value is assigned to one or more E-UTRAN frequencies for which THRESH\_E-UTRAN\_high\_Q is provided and one or more E-UTRAN frequencies for which THRESH\_E-UTRAN\_high\_Q is not provided then all such priority values are considered as not in the set of priorities. + +NOTE 1: These steps mean that if, for example, there are two UTRAN priority values, one E-UTRAN priority value (for a frequency for which THRESH\_E-UTRAN\_high\_Q is provided) and one E-UTRAN priority value (for a frequency for which THRESH\_E-UTRAN\_high\_Q is not provided) that are all the same, then all four priority values are considered as not in the set of priorities. + +A set of individual priorities is valid if it contains at least one priority. + +A set of common priorities is valid if both of the following conditions are met: + +- The set of priorities includes a priority for GERAN; +- The mobile station does not have a valid set of individual priorities. + +If the mobile station has a valid set of priorities, the priorities in this set shall be used for priority-based reselection as specified in 3GPP TS 45.008. + +NOTE 2: It is possible that individual priorities inherited from UTRAN or E-UTRAN (see sub-clause 5.5.1.1c.3) do not contain a priority for GERAN. + +#### 5.5.1.1c.2 Common priorities information + +The mobile station may receive common priorities information as specified in 3GPP TS 44.018. + +In addition, a mobile station may receive common priorities information in the PACKET MEASUREMENT ORDER message in the *Priority and E-UTRAN Parameters Description* IE, or for a mobile station supporting extended EARFCNs, in the *E-UTRAN NC with extended EARFCNs* IE. + +#### 5.5.1.1c.3 Provision of individual priorities information + +The provision of individual priorities information is described in 3GPP TS 44.018. + +#### 5.5.1.1d (void) + +### 5.5.1.2 System information on PBCCH + +If PBCCH is present in the serving cell, the mobile station shall receive the PACKET SYSTEM INFORMATION (PSI) messages broadcast on PBCCH. The parameters determining the schedule of PSI messages on PBCCH are provided in the PSI1 message. + +When a new cell has been selected where PBCCH is present, the mobile station shall perform a *complete acquisition* of PBCCH messages (see 5.5.1.4). The mobile station shall not perform packet access in the selected cell, or enter the packet transfer mode or the MAC-Shared state, until it has: + +- acquired the PACKET SYSTEM INFORMATION TYPE 1 (PSI1) message; +- acquired a consistent set of PSI2 messages; and +- made at least one attempt to receive the complete set of PSI messages on PBCCH. + +If the network supports the PACKET PSI STATUS message, the mobile station may perform packet access or maintain its radio resources (PDCH(s)) when the RR connection is released while in dual transfer mode, and enter packet transfer mode or the MAC-Shared state, as soon as the PSI1 message and a consistent set of PSI2 messages have been received. In this case, the mobile station shall implement the request for acquisition of system information (see 5.5.1.4.3). + +When the PSI1 message has been received, the mobile station shall supervise the PBCCH\_CHANGE\_MARK and perform update of PBCCH information as specified in sub-clause 5.5.1.2.1. In addition, while camping on a cell, the mobile station shall take into account any PSI message that may be received on PCCCH and PACCH. + +Once that the mobile station starts to acquire the information on PBCCH, the information sent to a mobile station in RLC/MAC control messages shall be independent of the information provided on the BCCH. If the mobile station receives information in an RLC/MAC control message that depends on the BCCH information, the behaviour of the mobile station is not specified. + +#### 5.5.1.2.1 Supervision of PBCCH\_CHANGE\_MARK and update of PBCCH information + +While camping on a cell where PBCCH is present, the mobile station shall attempt to receive the PSI1 message at least every 30 seconds. The mobile station shall then take into account any occurrence of the PSI1 message that may be received on PACCH during packet transfer mode or MAC-Shared state. The mobile station shall also take into account any occurrence of the PSI1 message that may be received on PCCCH during periods in packet idle mode or MAC-Idle state. If the PSI1 message is not received, the mobile station shall attempt to receive this message on PBCCH during periods in packet idle mode or MAC-Idle state. + +If the mobile station has not received the PSI1 message within the last 30 seconds, it shall attempt to receive the PSI1 message each time it is scheduled on PBCCH. Such attempts shall be made during packet idle mode, packet transfer mode, MAC-Idle state and MAC Shared state. A mobile station in packet transfer mode or MAC-Shared state may suspend its TBF(s) for this purpose (see 5.5.1.4.2). + +The PSI1 message contains the PBCCH\_CHANGE\_MARK and PSI\_CHANGE\_FIELD parameters. The mobile station shall store the value of the last PBCCH\_CHANGE\_MARK received. + +If the mobile station receives a PBCCH\_CHANGE\_MARK and detects that the value has been incremented by one unit, compared to the previous value, the mobile station shall perform a *partial acquisition* of PBCCH information. The information that shall be received is determined by the PSI\_CHANGE\_FIELD parameter: + +- If the PSI\_CHANGE\_FIELD parameter indicates an update of a specific type or specific types of PSI messages, the mobile station shall receive at least one instance of each of the indicated type(s) of PSI messages. +- If the PSI\_CHANGE\_FIELD parameter indicates an update of an unspecified type or types of PSI messages, the mobile station shall receive at least one message instance within each consistent set of PSI messages on PBCCH. It shall also receive all PSI messages on PBCCH not belonging to a consistent set. +- If the PSI\_CHANGE\_FIELD parameter indicates an update of an unknown type of PSI message, the mobile station is not required to receive any PBCCH information. + +When a PSI message is received, the mobile station shall consider the PSI *change mark* value, if such is received in the message and take appropriate action (see sub-clause 5.5.1.4.1). + +Whenever the mobile station receives a PBCCH\_CHANGE\_MARK and detects that the value has been incremented by more than one unit, compared to the previous value, the mobile station shall perform a *complete acquisition* of PBCCH messages (see sub-clause 5.5.1.4). + +#### 5.5.1.2.2 Replacement of PBCCH + +The mobile station may receive a PSI1 message indicating that PBCCH is being deactivated in the cell. Moreover, the mobile station may receive a PSI3 message on PACCH or PCCCH providing a different PBCCH description than the one currently being used, or a PSI3 message indicating that PBCCH is not present in the cell. + +If the mobile station detects that PBCCH is being deactivated in the cell, or receives an indication that PBCCH is no longer present in the cell, it shall attempt to receive the SI3 message on BCCH. For this purpose, the mobile station may suspend its operation in packet idle mode, packet transfer mode, MAC-Idle state and MAC-Shared state (see 5.5.1.4.2). When the SI3 has been received, further action depends on the contents of the SI3 message: + +- If the SI3 message contains a PBCCH description, the mobile station shall perform a *complete acquisition* of PBCCH messages using the indicated PBCCH (see sub-clause 5.5.1.4). +- If the SI3 message does not contain a PBCCH description, the mobile station shall perform a *complete acquisition* of BCCH messages. +- If the mobile station receives a PSI3 message with a PBCCH description different from that currently being used, the mobile station shall perform a *complete acquisition* of PBCCH messages using the new PBCCH. + +#### 5.5.1.2.3 PSI1 reception failure + +If the mobile station has not received the PSI1 message within the last 60 s, a PSI1 reception failure has occurred. A PSI1 reception failure shall result in a cell reselection. + +#### 5.5.1.3 System information on BCCH + +The presence of a PBCCH in the cell is indicated by a PBCCH description in the SI3 message on BCCH. If the mobile station receives an SI3 message without a PBCCH description, it shall assume that PBCCH is not present in the cell. If PBCCH is not present in the serving cell, the mobile station shall receive the SYSTEM INFORMATION (SI) messages broadcast on BCCH. + +When a new cell has been selected where PBCCH is not present, the mobile station shall perform a *complete acquisition* of BCCH messages (see sub-clause 5.5.1.4). The mobile station shall not perform packet access in the selected cell, or enter the packet transfer mode, until it has: + +- acquired the SYSTEM INFORMATION TYPE 3 (SI3), SI3 and, if present, SI1 messages; +- made at least one attempt to receive other SI messages that may be scheduled within one TC cycle on BCCH (see 3GPP TS 45.002). + +If the network supports the PACKET SI STATUS message, the mobile station may perform packet access or maintain its radio resources (PDCH(s)) when the RR connection is released while in dual transfer mode, and enter packet transfer mode, as soon as the SI3, SI13 and, if present, SI1 messages have been received. In this case, the mobile station shall implement the request for acquisition of system information (see sub-clause 5.5.1.4.3). + +When the SI13 message has been received, the mobile station shall supervise the BCCH\_CHANGE\_MARK and perform update of BCCH information. + +#### 5.5.1.3.1 Supervision of BCCH\_CHANGE\_MARK and update of BCCH information + +While camping on a cell where PBCCH is not present, the mobile station shall attempt to receive the SI13 or the PSI13 message at least every 30 s. The mobile station shall then take into account any occurrence of the PSI13 message that may be received on PACCH during packet transfer mode. If PSI13 is not received, the mobile station shall attempt to receive the SI13 message on BCCH during periods in packet idle mode. + +If the mobile station has received neither the SI13 nor the PSI13 message within the last 30 s, it shall attempt to receive the SI13 message each time it is scheduled on BCCH. Such attempts shall be made during both packet idle and packet transfer modes. A mobile station in packet transfer mode may suspend its TBF(s) for this purpose (see sub-clause 5.5.1.4.2). + +An exception case is where a mobile station has enabled PEO in which case the mobile station shall monitor system information as described in 3GPP TS 44.018 [11] while in packet idle mode but shall not monitor system information while in packet transfer mode. + +The SI13 and PSI13 messages contain the BCCH\_CHANGE\_MARK and SI\_CHANGE\_FIELD parameters. When camped on a cell where PBCCH is not present, the mobile station shall store the value of the last BCCH\_CHANGE\_MARK received. In that case, if the mobile station detects that the value has been incremented by one unit, compared to the previous value, the mobile station shall perform a *partial acquisition* of BCCH information. The information that shall be received is determined by the SI\_CHANGE\_FIELD parameter: + +- If the SI\_CHANGE\_FIELD parameter indicates an update of a specific type or specific types of SI messages, the mobile station shall receive at least one instance of each of the indicated type(s) of SI messages. +- If the SI\_CHANGE\_FIELD parameter indicates an update of an unspecified type or types of SI messages, the mobile station shall receive at least one message instance within each consistent set of SI messages on BCCH. It shall also receive all SI messages on BCCH not belonging to a consistent set. +- If the SI\_CHANGE\_FIELD parameter indicates an update of an unknown type of SI message, the mobile station is not required to update any BCCH information. + +When an SI message is received, the mobile station shall consider a SI *change mark* value, if such is received in the message and take appropriate action (see sub-clause 5.5.1.4.1). + +If the mobile station detects that the BCCH\_CHANGE\_MARK value has been incremented by more than one unit, compared to the previous value, the mobile station shall perform a *complete acquisition* of BCCH messages (see sub-clause 5.5.1.4). + +#### 5.5.1.3.2 Establishment of PBCCH + +The mobile station may receive an SI13 or PSI13 message providing a PBCCH description indicating that PBCCH is present in the cell. The mobile station shall then perform a *complete acquisition* of PBCCH messages using the indicated PBCCH (see sub-clause 5.5.1.4). + +#### 5.5.1.3.3 SI13 reception failure + +If the mobile station has not received the SI13 or the PSI13 message within the last 60 s, a SI13 reception failure has occurred. An SI13 reception failure shall result in a cell reselection. + +#### 5.5.1.3a System information on EC-BCCH + +A mobile station that has enabled EC operation in a cell shall receive the EC SYSTEM INFORMATION messages broadcast on EC-BCCH (EC SI). The EC-BCCH shall be present in a cell that supports EC-GSM-IoT. + +When a mobile station that is EC-GSM-IoT capable has selected a new cell that supports EC-GSM-IoT, the mobile station shall perform a *complete acquisition* of EC-BCCH messages, see 3GPP TS 44.018. The mobile station shall not + +perform packet access in the selected cell, or enter the packet transfer mode, until it has acquired the full set of system information messages scheduled on the EC-BCCH. + +#### 5.5.1.4 Acquisition of system information on the broadcast channel + +This procedure shall be used by a mobile station that supports GPRS (in *A/Gb mode*) or *Iu mode* in order to perform a complete or partial acquisition of either PBCCH or BCCH information. As part of this procedure, the mobile station may implement the request for acquisition of system information as specified in sub-clause 5.5.1.4.3. + +The procedure to be used by a mobile station that has enabled EC operation, is described in 3GPP TS 44.018. + +When PBCCH is not present in a cell this procedure starts: + +- when the mobile station is camped on BCCH and receives a BCCH\_CHANGE\_MARK or SI *change mark* value indicating that system information is changed. + +When PBCCH is present in a cell this procedure starts: + +- when the mobile station is camped on PBCCH and receives a PBCCH\_CHANGE\_MARK or PSI *change mark* value indicating that packet system information is changed. + +Moreover, the procedure shall start at any other indication, which may be received by the mobile station, that the stored system information for the serving cell is no longer valid. + +At cell selection or cell reselection, in case PBCCH is present in the target cell, this procedure starts when the mobile station starts to receive the information on PBCCH. In case PBCCH is not present in the target cell, the procedure starts when the mobile station has received the SI13 message. + +In a *complete acquisition* of either PBCCH or BCCH information, the mobile station shall receive all PSI or SI messages that are scheduled on the respective broadcast channel. The mobile station shall delete any PSI or SI *change mark* value that was stored before the acquisition of PBCCH or BCCH information started. + +In a *partial acquisition* of either PBCCH or BCCH information, only a certain subset of the PSI or SI messages that are scheduled on the respective broadcast channel shall be received. The mobile station may consider the state of the PSI or SI *change mark* values, without restriction, to reduce the total number of messages to receive. + +When the mobile station acquires a set of PSI or SI messages on the respective broadcast channels, it may receive these messages during packet idle mode, packet transfer mode, MAC-Idle state, MAC-Shared state and broadcast/multicast receive mode. While the mobile station is in packet idle mode or MAC-Idle state or broadcast/multicast receive mode if the network has indicated that the system information is not sent on the PACCH, an attempt to receive a required message shall be made each time the message is scheduled on the broadcast channel, until the message is received. While the mobile station is in packet transfer mode, MAC-Shared state or broadcast/multicast receive mode if the network has indicated that the system information is sent on the PACCH, it shall receive any PSI message that is sent by the network on PACCH. While the mobile station is in dual transfer mode or MAC-DTM state, it may disregard any PSI message except PSI14 message that is sent by the network on PACCH. + +If the mobile station has not received the required messages within 10 seconds after the start of this procedure, an attempt to receive a missing message shall be made each time the message is scheduled on the broadcast channel. These attempts shall then be performed during packet idle mode, packet transfer mode, MAC-Idle state, MAC-Shared state and broadcast/multicast receive mode. A mobile station in packet transfer mode or MAC-Shared state may suspend its TBF(s) for this purpose, as specified in 5.5.1.4.2. A mobile station in broadcast/multicast receive mode may skip the reception of radio blocks of the MBMS radio bearer for the same purpose, as specified in 5.5.1.4.2. + +A second acquisition of either PBCCH or BCCH information may be initiated (e.g. when the mobile station receives a PSI or SI *change mark* value) before a previous acquisition is completed. In this case, the mobile station shall discard and immediately begin re-acquiring all the system information messages of the particular type to which the changemark value refers. + +To allow future extension of PSI message types, the mobile station may disregard a message in a position within the schedule of PSI messages on PBCCH, where it receives a valid RLC/MAC control block, but diagnoses an unknown or unexpected (non-PSI) message type. When this condition is detected, the mobile station needs not to receive the PBCCH block in this position again, until a change in the schedule of PBCCH messages is detected or a *complete acquisition* of PBCCH information is required. + +#### 5.5.1.4.1 Consistent sets of system information messages + +A mobile station, receiving a PSI or SI message belonging to a consistent set of system information messages, shall store the last PSI or SI *change mark* value received for the set of messages (see table 5.5.2.1.4.1). A mobile station lacking all non-GSM capabilities defined for PSI6, PSI7, SI 18 or SI 20 shall consider those message as irrelevant when making a determination of whether or not a consistent set of system information messages has been received. + +A mobile station that does not support UTRAN shall consider a PSI3quater message as irrelevant when making a determination of whether or not a consistent set of system information messages has been received. + +Whenever mobile station receives a PSI or SI *change mark* value, which is not equal to the previously stored value for the set of messages, the mobile station shall perform a *partial acquisition* of either PBCCH or BCCH information. It shall then receive all instances of the PSI or SI messages belonging to the consistent set of system information messages. + +If a mobile station detects an inconsistency amongst the PSI or SI *count* and *index* parameters within a consistent set of system information messages or any other inconsistency making the information that is contained invalid, the mobile station shall discard the messages received so far and delete the stored PSI or SI *change mark* value. The mobile station may then restart the acquisition of the affected system information messages. + +#### 5.5.1.4.2 Suspension of operation to receive system information + +During certain conditions, the mobile station in packet transfer mode or MAC-Shared state is allowed to suspend its TBF(s) to receive certain information on PBCCH or BCCH. A mobile station in broadcast/multicast receive mode may suspend the reception of radio blocks of the MBMS radio bearer for the same purpose. Such suspension is made without notification to the network. A mobile station in EC operation shall not suspend its TBF for reception of EC system information. + +Suspension of its TBF(s) or suspension of the reception of radio blocks of the MBMS radio bearer for this purpose is allowed during the time required, for each message and according to the mobile station's multislot class, to receive the required messages on PBCCH or BCCH. The allowable suspension of an uplink TBF may be extended with one block period, in case of dynamic or extended dynamic allocation, if the mobile station is unable to receive the corresponding USF due to the suspension of downlink operation. In case it conflicts with the transmission of a polling response, priority shall be given to the acquisition of blocks on the PBCCH or BCCH channel. + +#### 5.5.1.4.3 Request for acquisition of system information + +As an option, the mobile station may implement the request for acquisition of system information. If the network supports the PACKET PSI STATUS message or the PACKET SI STATUS message, the mobile station shall then send the PACKET PSI STATUS message to the network, each time an acquisition of PBCCH information is initiated or the PACKET SI STATUS message to the network, each time an acquisition of BCCH information is initiated. + +A mobile station supporting the Network Assisted Cell Change or enhanced DTM CS release procedures shall implement the request for acquisition of system information (see sub-clauses 5.5.1.1a and 5.5.1.1b.5). + +The PACKET SI STATUS message shall always contain the PSCSI\_SUPPORT field. + +The PACKET PSI STATUS (respectively PACKET SI STATUS) message shall indicate the present status of PSI (respectively SI) messages stored in or requested but not received by the mobile station. The mobile station shall include as many PSI (respectively SI) message types that fit into the *Received PSI Message List* (respectively *Received SI Message List*) construction in the PACKET PSI STATUS (respectively PACKET SI STATUS) message and that meet the following criteria: + +- The PSI (respectively SI) message type is relevant for the mobile station, based on the features the mobile station supports (e.g. non-GSM and multi-RAT capabilities); and +- In case of optional PSI (respectively SI) messages types, the PSI (respectively SI) message type shall be indicated by the network as present on PBCCH (respectively BCCH). + +If the presence of an optional PSI (respectively SI) message type cannot be determined, based on the information received, the mobile station shall assume that the optional PSI (respectively SI) message type is present. + +NOTE 1: On PBCCH, the presence of optional PSI messages is indicated in PSI1 and PSI2. + +NOTE 2: On BCCH, SI2, SI3, SI4 and, if present, SI9 indicate the presence of optional SI messages, except SI1. The presence of SI1 can be determined by reading the BCCH Norm block at TC = 0. + +The "ADDITIONAL\_MSG\_TYPE" information should reflect whether all PSI (respectively SI) message types that satisfy the criteria given above fit into a given PACKET PSI STATUS (respectively PACKET SI STATUS) message or not. + +The message type value for these PSI (respectively SI) messages shall be included in the *Received PSI Message List* (respectively *Received SI Message List*) in the PACKET PSI STATUS (respectively PACKET SI STATUS) message. The message types that may be indicated are given in table 5.5.1.4.3.1. The message types shall be indicated in descending order of priority. The network may use this information to determine which PSI (respectively SI) message types the mobile station is able to receive and the present status of the PSI (respectively SI) messages stored in the mobile station. + +**Table 5.5.1.4.3.1: Message types that may be indicated at a request for acquisition of system information during packet transfer mode** + +| Type of status message | PSI (respectively SI) message types, descending order of priority | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PACKET PSI STATUS message | PSI2 ( highest priority ), PSI3, PSI3bis, PSI5, PSI3ter, PSI3quater, PSI6, PSI7, and PSI8 ( lowest priority ) | +| PACKET SI STATUS message | SI1 ( highest priority ), SI3, SI2, SI2bis, SI2ter, SI2quater, SI4, SI2n, SI7, SI8, SI9, SI15, SI16, SI17, SI18, SI20 and SI19 ( lowest priority ) | + +During a partial acquisition of PSI (respectively SI) messages, see sub-clause 5.5.1.4, the mobile station may need to obtain the current PSI (respectively SI) *change mark* value for certain types of PSI (respectively SI) messages. In that case, the mobile station may use this procedure and indicate the present status for that PSI (respectively SI) message type in the PACKET PSI STATUS (respectively PACKET SI STATUS) message, except that the message instance corresponding to the PSI (respectively SI) *index* parameter = 0 shall be indicated as not received. + +The PACKET PSI STATUS (respectively PACKET SI STATUS) message may also be used to indicate the message type of a PSI (respectively SI) message that is required but has not been received by the mobile station. + +The PACKET PSI STATUS (respectively PACKET SI STATUS) message is sent on PACCH when the mobile station is in packet transfer mode or MAC-Shared state. The first sending of this message during the acquisition of PBCCH (respectively BCCH) information shall take place at the first suitable opportunity after the acquisition is initiated. This is also allowed during the contention resolution. + +During the acquisition of PBCCH (respectively BCCH) information, up to four PACKET PSI STATUS (respectively PACKET SI STATUS) messages may be sent to the network. The second sending occurrence of this message shall take place at the first suitable opportunity at least one second after that the message is sent the first time. Further sending occurrences shall take place at the first suitable opportunity at least two seconds after that the message was sent the previous time. At each sending occurrence, this message shall be updated according to the present status of PSI (respectively SI) messages in the mobile station. + +The PACKET PSI STATUS (respectively PACKET SI STATUS) message shall not be sent when the mobile station has started to suspend its TBF(s) in order to receive the required PSI (respectively SI) messages on PBCCH (respectively BCCH). The PACKET PSI STATUS (respectively PACKET SI STATUS) message shall not be sent when the mobile station has acquired the complete set of PSI (respectively SI) messages on PBCCH (respectively BCCH), unless a new partial or full acquisition of system information is required. + +### 5.5.1.5 Discontinuous reception (DRX) + +A mobile station in packet idle mode shall monitor the CCCH, PCCH or EC-CCCH as defined in 3GPP TS 45.002. + +In the *GPRS attach procedure*, defined in 3GPP TS 24.008, the mobile station requests values for the SPLIT\_PG\_CYCLE and NON\_DRX\_TIMER parameters to be applied on CCCH or PCCH. + +NOTE: The support of the SPLIT\_PG\_CYCLE parameter is optional on CCCH, see 3GPP TS 45.002. + +The SPLIT\_PG\_CYCLE and NON\_DRX\_TIMER parameters control: + +- the occurrence of paging blocks on CCCH or PCCH belonging to the mobile station (SPLIT\_PG\_CYCLE parameter, see 3GPP TS 45.002) in DRX mode (see 3GPP TS 43.064); and + +- the duration of the non-DRX mode period to be applied by the mobile station when it has left the packet transfer mode or the dual transfer mode and then enters the packet idle mode. + +There are five cases when the mobile station shall enter a non-DRX mode period. + +- 1) At the transition from the packet transfer mode to the packet idle mode, the mobile station shall enter the Transfer non-DRX mode period. +- 2) At the transition from the dual transfer mode to the dedicated mode or packet idle mode, the mobile station shall enter the Transfer non-DRX mode period. + +In both cases, the duration of the Transfer non-DRX mode period is determined by value of the NON\_DRX\_TIMER parameter, requested in the *GPRS attach procedure*, and the value of the DRX\_TIMER\_MAX parameter broadcast in the cell. The mobile station may use the minimum value of these two parameters. + +If the mobile station receives a new value of the DRX\_TIMER\_MAX parameter during the Transfer non-DRX mode period, the mobile station may wait to apply the new value until the next time the Transfer non-DRX mode period is entered. + +- 3) A mobile station operating in NC2 mode shall enter the NC2 non-DRX mode period when it sends an NC measurement report. The duration of this period is defined by the NC\_NON\_DRX\_PERIOD parameter. +- 4) When initiating the MM procedures for *GPRS attach* and *routeing area update* defined in 3GPP TS 24.008, the mobile station shall enter the MM non-DRX mode period. This period ends when either of the messages GPRS ATTACH ACCEPT, GPRS ATTACH REJECT, ROUTING AREA UPDATE ACCEPT or ROUTING AREA UPDATE REJECT is received by the mobile station. This period also ends after timeout when waiting for any of these messages. +- 5) The mobile station shall enter the MBMS non-DRX mode period when it receives a pre-notification for an MBMS service and MBMS session, and the MBMS service is a broadcast service or is a multicast service previously joined by the mobile station and the MBMS session has not yet been received by the mobile station. The mobile station shall also enter the MBMS non-DRX mode period, if not already in it, when the mobile station sends the MBMS SERVICE REQUEST message, unless the MBMS packet access procedure is performed on MPRACH during fast reception resumption. The mobile station shall also enter the MBMS non-DRX mode period, if not already in it, when it receives a notification for an MBMS service and MBMS session, and the MBMS service is a broadcast service or is a multicast service previously joined by the mobile station and the MBMS session has not yet been received by the mobile station, and the notification: + - indicates that no counting shall be performed and contains no MBMS p-t-m channel description; + - or, specifies an MBMS radio bearer starting time which has not yet elapsed. + +The MBMS non-DRX mode period ends when a notification (containing an MBMS p-t-m channel description) or the MBMS ASSIGNMENT message, addressing the same MBMS session and not specifying an MBMS radio bearer starting time or specifying an MBMS radio bearer starting time already elapsed, is received by the mobile station. If the notification or the MBMS ASSIGNMENT message specifies an MBMS radio bearer starting time which has not yet elapsed, the period ends when the point in time denoted by the MBMS radio bearer starting time occurs, unless any subsequent notification or MBMS ASSIGNMENT message addressing the same MBMS session and received by the mobile station, before the point in time denoted by the MBMS radio bearer starting time, provides an up-to-date value of the MBMS radio bearer starting time or does not include an MBMS radio bearer starting time. + +The MBMS non-DRX mode period also ends after timeout when waiting for the MBMS notification of the pre-notified MBMS service and MBMS session or after timeout when waiting for the MBMS ASSIGNMENT message. + +The non-DRX mode periods defined above run independent of each other and may overlap. The non-DRX mode periods have effect only in packet idle mode. In packet idle mode, the mobile station shall be in non-DRX mode during any of the non-DRX mode periods. Otherwise, the mobile station in packet idle mode may be in DRX mode. + +If the mobile station establishes an RR connection during any of the non-DRX mode periods, then that period shall continue to run. + +An exception case is where a mobile station has enabled PEO or EC operation in which case it shall operate as follows: + +- When initiating the MM procedures for GPRS attach and routing area update defined in 3GPP TS 24.008 [51], the mobile station shall enter a zero length MM non-DRX mode period. +- If eDRX has been negotiated (see 3GPP TS 24.008 [51]) then the mobile station shall not request values for the SPLIT\_PG\_CYCLE or the NON\_DRX\_TIMER parameter. +- At the transition from packet transfer mode to packet idle mode, the mobile station shall enter a zero-length Transfer non-DRX mode period. +- It may negotiate the use of eDRX or PSM with eDRX. If it has negotiated eDRX or PSM with eDRX then it shall consider eDRX to be supported in all cells in the corresponding Routing Area (i.e. eDRX is negotiated at the Routing Area level). +- If a mobile station that has enabled PEO enters extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b) then it monitors the downlink PACCH starting with the 2nd 52-multiframe following the 52-multiframe in which it received the PACKET UPLINK ACK/NACK message confirming reception of all uplink RLC data blocks. More specifically, when there is no ongoing downlink TBF it monitors radio block $[(\text{IMSI mod } 1e7) \text{ mod } 12]$ in that 52-multiframe and in each subsequent 52-multiframe for a matching PACCH message for as long as it remains in extended UL TBF mode or it receives a matching PACCH message assigning it a downlink TBF. +- If the mobile station in EC operation is indicated to continue monitoring the EC-PACCH in the EC PACKET UPLINK ACK/NACK with the Final Ack Indicator bit set to '1', then it monitors the EC-PACCH, according to its allocated downlink Coverage Class of the TBF, after an initial waiting time as indicated in the EC PACKET UPLINK ACK/NACK message. The mobile station then monitors the EC-PACCH, using a monitoring pattern as indicated in the EC PACKET UPLINK ACK/NACK message, for as long as timer T3238 is running. +- A mobile station that has enabled EC operation and negotiated eDRX shall monitor the EC-CCCH according to the selected downlink Coverage Class and the negotiated eDRX value, see 3GPP TS 45.008. If no eDRX value has been negotiated, the mobile station shall monitor the EC-CCCH according to the selected downlink Coverage Class and the lowest eDRX value. While in packet idle mode with the Ready timer running a mobile station that has enabled EC operation shall always use the lowest eDRX cycle (see 3GPP TS 45.002 [13]). +- A mobile station that has enabled PEO uses the lowest eDRX cycle (see 3GPP TS 45.002 [13]) while the Ready timer is running. If eDRX has been negotiated then upon expiration of the Ready timer the mobile station enters the eDRX based power saving state and uses its negotiated eDRX (see 3GPP TS 45.002 [13]). +- If PSM has been negotiated (see 3GPP TS 24.008 [51]) it starts the active timer upon expiration of the ready timer. While the active timer is running it remains reachable using the eDRX value last negotiated with the network. If no eDRX value has been negotiated then it uses the DRX cycle applicable to the serving cell while the Active timer is running. When the active timer expires the mobile station enters the PSM based power saving state and will not be reachable until the next time it performs an uplink data transfer. + +### 5.5.1.6 Page mode procedures on PCCCH + +The network sends page mode information in all downlink message on PCCCH (and PACCH, see note). The page mode information controls possible additional requirements on a mobile station receiving the message. + +NOTE: PCCCH, PDTCH and PACCH may be operated in frame stealing mode on the same PDCH. A mobile station in packet idle mode or MAC-Idle state shall consider any RLC/MAC control message received in such a radio block as belonging to PCCCH. A mobile station in packet transfer mode, dual transfer mode, MAC-Shared state or MAC-DTM state shall consider any RLC/MAC control message received as belonging to PACCH. + +A mobile station in packet transfer mode, dual transfer mode, MAC-Shared state or MAC-DTM state shall not consider the page mode information received in any message that is received on a PDCH. + +A mobile station in packet idle mode or MAC-Idle state shall take into account the page mode information in any message received in a radio block on PCCCH corresponding to its paging group. The mobile station shall not take into account the page mode information in a message received in any other radio block than those corresponding to its paging group. The requirements yielded by the page mode information are as follows: + +- *normal paging*: no additional requirements; +- *extended paging*: the mobile station is required in addition to receive and analyse the possible message in the third block period on PCCCH where paging may occur (PPCH), following the block corresponding to MS's paging group; +- *paging reorganization*: The mobile station shall receive all messages on the PCCCH regardless of the BS\_PAG\_BLKS\_RES setting. It is required to receive all PBCCH messages. When the mobile station receives the next message to its (possibly new) paging group, subsequent action is defined by the page mode information in that message; +- *same as before*: no change of page mode from the previous page mode. + +Note that a mobile station takes into account the page mode information only in packet idle mode or MAC-Idle state and only in messages received in a radio block corresponding to its paging group, whatever the currently applied requirements are (normal paging, extended paging or paging reorganization). + +When the mobile station selects a new PPCH, the initial page mode in the mobile station shall be set to paging reorganization. If an RLC/MAC block in a paging sub-channel does not contain page mode information, or if it is not received correctly, the default page mode information is *same as before*. + +### 5.5.1.7 Frequency Parameters + +Frequency parameters may be included in the packet assignment messages (i.e., PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION messages) or in the PS HANDOVER COMMAND message and define the training sequence codes(s) (TSC) and the radio frequency channels or set of radio frequency channels the mobile station is to use during the assigned TBF(s). The first packet assignment message, sent to the mobile station when it enters packet transfer mode or MAC-Shared state, shall include the frequency parameters. Subsequent packet assignment messages, sent to the mobile station during packet transfer mode or MAC-Shared state, may omit the frequency parameters. If a mobile station receives a subsequent packet assignment message, during packet transfer mode or MAC-Shared state, without the frequency parameters, the mobile station shall continue to use the previously assigned frequency parameters. + +A packet assignment message, when sent to a mobile station in dual transfer mode or MAC-DTM state, shall not include the frequency parameters for the carrier supporting the dedicated resources in a Downlink Dual Carrier configuration. If the network intends to change the frequency allocation of the carrier supporting the dedicated resources for a mobile station in dual transfer mode or MAC-DTM state, the network may use the DTM assignment procedure defined in 3GPP TS 44.018. + +If the network and mobile station both support Downlink Dual Carrier, the network may send a packet assignment message or a PS HANDOVER COMMAND message to a mobile station specifying packet resources for one or more TBFs on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. If the packet assignment message is sent to a mobile station in packet idle mode, this message shall include frequency parameters for both carriers. If this message is sent to a mobile station which is in packet transfer mode (and is not in a Downlink Dual Carrier configuration) the assignment message shall either: + +- provide new frequency parameters for both carriers, or +- provide frequency parameters for only one carrier (carrier 2) in which case the frequency parameters for carrier 1 remain unchanged. + +Subsequent packet assignment messages sent to a mobile station in a Downlink Dual Carrier configuration may: + +- include frequency parameters which correspond to the frequency parameters already in use for one or both carriers; or +- provide no new frequency parameters, in which case the existing parameters continue to apply; or +- provide new frequency parameters for both carriers; or +- provide new frequency parameters for only one carrier, in which case the frequency parameters for the other carrier remain unchanged. + +If the network and mobile station both support Downlink Multi Carrier, the network may send a packet assignment message (i.e. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE messages) or a PS HANDOVER COMMAND message to a mobile station specifying packet resources that establish a DLMC configuration. The PS HANDOVER COMMAND message shall always provide new frequency parameters for use in the new cell whereas the packet assignment message may: + +- provide new frequency parameters for all newly assigned and existing carriers, or +- provide new frequency parameters for all newly assigned carriers, modify the frequency parameters for a subset of the existing carriers and leave the frequency parameters for the remaining existing carriers unchanged. + +When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent packet assignment messages, that carrier shall be considered carrier 1. A subsequent packet assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the packet assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration. Similarly, a subsequent packet assignment message may assign resources on one or more additional carriers, thereby establishing a DLMC configuration; in this case, the packet assignment message shall provide DLMC frequency parameters as required for use in a DLMC configuration. + +A packet assignment message sent to a mobile station in packet transfer mode may specify frequency parameters for one or (in the case of a mobile station with a downlink dual carrier configuration) both carriers which are different from those currently in effect for that mobile station only in the following cases: + +- a) the assignment message is a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message. +- b) the assignment message is a PACKET DOWNLINK ASSIGNMENT message (respectively PACKET UPLINK ASSIGNMENT message) being sent to a mobile station which has no ongoing uplink (respectively downlink) TBF(s). +- c) the assignment message is a MULTIPLE TBF DOWNLINK ASSIGNMENT message (respectively MULTIPLE TBF UPLINK ASSIGNMENT message) being sent to a mobile station which is or, after this assignment, will be in a downlink dual carrier configuration and has no ongoing uplink (respectively downlink) TBF(s); in this case, the ongoing downlink (respectively uplink) TBFs are implicitly reassigned on the new frequency parameters with all other parameters for those TBFs unchanged. +- d) the assignment message is a PACKET DOWNLINK ASSIGNMENT message (respectively PACKET UPLINK ASSIGNMENT message) sent to a mobile station with a downlink dual carrier configuration, where the frequency parameters for only one carrier are changed, and where no ongoing uplink (respectively downlink) TBF(s) had resources assigned on that carrier. + +In cases c) and d) above, a format of the message which includes the Carrier ID field shall be used. + +When assigning resources on one carrier to a mobile station which is currently in a Downlink Dual Carrier configuration using a format of the message which does not include the Carrier ID field, the network shall always include frequency parameters; if one or more TBFs which are ongoing are not explicitly addressed in the packet assignment message and will remain ongoing after the new assignment, the included frequency parameters shall be those in use for either carrier 1 or carrier 2. + +A packet assignment message sent to a mobile station in packet transfer mode with a DLMC configuration may specify frequency parameters for one or more carriers which are different from those currently in effect for that mobile station only in the following cases: + +- a) the assignment message is a PACKET TIMESLOT RECONFIGURE message. +- b) the assignment message is a PACKET DOWNLINK ASSIGNMENT message sent to a mobile station which has no ongoing uplink TBF. +- c) the assignment message is a PACKET DOWNLINK ASSIGNMENT message sent to a mobile station which has an ongoing uplink TBF, subject to the restriction that all existing carriers on which USF is monitored remain assigned. +- d) the assignment message is a PACKET UPLINK ASSIGNMENT message for the case where the ongoing downlink TBF is not modified. + +Frequency parameters used for EC TBFs are specified in the EC SYSTEM INFORMATION TYPE 1 message, sent on the EC-BCCH, see 3GPP TS 44.018. The frequency parameters are included in EC Mobile Allocation sets, each set consisting of: + +- radio frequencies (ARFCNs), HSN and MAIO, for a hopping radio frequency channel; or +- a single ARFCN, for a non-hopping radio frequency channel. + +The frequency parameters for a specific EC TBF are assigned in the packet assignment messages (i.e. EC IMMEDIATE ASSIGNMENT TYPE 1, EC IMMEDIATE ASSIGNMENT TYPE 2, EC DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT or EC PACKET UPLINK ASSIGNMENT message). The packet assignment messages then includes a reference to one of the EC Mobile Allocation sets in the EC SYSTEM INFORMATION TYPE 1 message and a definition of the training sequence code (TSC) to use for the EC TBF. + +The Frequency Parameters information element is defined in sub-clause 12.8 and the Dual Carrier Frequency Parameters information element is defined in sub-clause 12.8.2 and the DLMC Frequency Parameters information element is defined in sub-clause 12.8.4. The frequency parameters may use an ARFCN defining a non-hopping radio frequency channel, or use the indirect encoding, direct encoding 1 or direct encoding 2 defining a hopping radio frequency channel. + +The indirect encoding defines the assigned set of radio frequency channels by referencing information stored within the mobile station. Such information may be received on PBCCH or BCCH (see sub-clauses 5.5.2.1, 11.2.19, 12.8 and 12.10a), or be received in a previous assignment message using one of the direct encoding options. An MA\_NUMBER identifies which of up to eight stored sets of frequency parameters is to be used. The MA\_NUMBER shall use the following coding: + +MA\_NUMBER = 0-13 shall be used to reference a GPRS mobile allocation received in a PSI2 message; + +MA\_NUMBER = 14 shall be used to reference a GPRS mobile allocation received in a SI13 or PSI13 message; + +MA\_NUMBER = 15 shall be used to reference a GPRS mobile allocation received in a previous assignment message using the direct encoding. + +When the indirect encoding is used, the network may include a CHANGE\_MARK\_1 and a CHANGE\_MARK\_2 in the Frequency Parameters information element. The mobile station shall then verify that it is using a set of PBCCH or BCCH information identified by a PSI or SI *change mark* corresponding to one of the CHANGE\_MARK\_1 or 2 parameters, for the decoding of the frequency information. If that is not the case, an abnormal condition occurs. + +The direct encoding defines the assigned set of radio frequency channels by using information contained within the assignment message. The direct encoding 1 references the cell allocation or reference frequency lists received on PBCCH for the decoding of this information. The direct encoding 2 is self contained. When the direct encoding 1 or 2 is used, the mobile station shall store the received GPRS mobile allocation for possible later reference in an assignment message using the indirect encoding. Such reference shall be made using the MA\_NUMBER = 15. + +NOTE: If there is a GPRS mobile allocation associated with MA\_NUMBER = 15, the association shall be kept unchanged if the mobile station receives a packet assignment using the indirect encoding (referencing any value of the MA\_NUMBER), the frequency parameters are not included in the packet assignment (i.e., in packet transfer mode, dual transfer mode, MAC-Shared state or MAC-DTM state) or the mobile station establishes an RR connection (for A/Gb mode) or is allocated a DBPSCH (for Iu mode). + +For the decoding of frequency parameters, the mobile station shall be able to store the following frequency information (see sub-clauses 11.2.19, 12.8 and 12.10a): + +- four Reference Frequency Lists received in the PSI2 information and the corresponding RFL\_NUMBERS for identification, each RFL having a contents length of up to 18 octets; +- a Cell Allocation received in the PSI2 information referencing up to four RFLs; +- seven GPRS Mobile Allocations received in the PSI2 or the SI13/PSI13 information and the corresponding MA\_NUMBERS for identification, each GPRS Mobile Allocation information element having a length of up to 12 octets (96 bits); and +- one GPRS mobile allocation received in an assignment message using direct encoding 1 or 2, consisting of either a GPRS Mobile Allocation information element having a length of up to 12 octets (96 bits) or a MA Frequency List having a contents length of up to 18 octets. + +The mobile station shall be able to store the frequency information for the PCCCH description corresponding to its own PCCCH\_GROUP (see sub-clause 11.2.19). + +If the mobile station supports SMSCB, it shall be able to store the frequency information for the CBCH to be used in packet idle mode or MAC-Idle state. + +The frequency information that the mobile station has stored while camping on a cell shall be deleted when the mobile station reselects a new cell. + +### 5.5.1.8 TLLI management + +In case the mobile station receives a message assigning a new P-TMSI from the network during the contention resolution procedure, the mobile station shall continue to use the old TLLI until the contention resolution is completed. + +After contention resolution the mobile station shall apply new TLLI in RLC/MAC control block if the mobile has received a new P-TMSI. + +The BSS shall not include TLLI within RLC/MAC control messages it sends to a mobile station in packet transfer mode. + +### 5.5.1.9 Packet Flow Context (PFC) + +Packet Flow Context (PFC) procedures are described in 3GPP TS 23.060. A Packet Flow Identifier (PFI) is used to identify a PFC. + +Mobile station support of packet flow context (PFC) procedures is indicated in the *MS Network Capability IE* (see 3GPP TS 24.008). Network support of packet flow context (PFC) procedures is indicated by the PFC\_FEATURE\_MODE parameter that is broadcast on either the BCCH or PBCCH. If the PFC\_FEATURE\_MODE field indicates that the network does not support PFC procedures then a mobile station shall not indicate a PFI value during uplink TBF establishment. If the PFC\_FEATURE\_MODE field indicates that the network supports PFC procedures then a mobile station may indicate a PFI value during uplink TBF establishment. The PFI value identifies the initial PFC used during the TBF. + +If the network or the mobile station indicates it supports multiple TBF procedures (see sub-clause 7.0) then it shall also indicate support for PFC procedures. When the network and the mobile station both support multiple TBF procedures then the mobile station shall indicate the PFI value associated with each uplink TBF it attempts to establish and the network shall indicate the PFI value associated with each downlink TBF it attempts to establish. + +If the network or the mobile station indicates it supports Enhanced Multiplexing for Single TBF (see sub-clause 5.10) then it shall also indicate support for PFC procedures. The mobile station supporting EMST shall indicate the PFI value associated with each RLC entity it requests to establish on an uplink TBF if the network indicates the support of PFC procedures. When EMST is used on a given TBF, the network shall always indicate the PFI value associated with each RLC entity it establishes on that TBF. + +EMSR requires the support of PFC procedures in both the network and the mobile station (see sub-clause 5.10). A mobile station that supports EMSR shall always indicate the PFI value associated with each PFC for which it requests resources from a network that supports PFC procedures. A network that supports EMSR shall always indicate the PFI value associated with each PFC it establishes on a given RLC entity when sending an assignment message to a mobile station that supports EMSR (see sub-clause 5.2.2). + +A network or mobile station that supports PS handover or DTM handover shall also support PFC procedures. + +In case no valid PFI value is assigned for the LLC data to be transmitted, and the network indicates support for the PFC procedures, an MS supporting PFC procedures shall associate and indicate the following PFI values for the LLC data: + +- PFI=0 (Best Effort) for user data, +- PFI=1 (Signalling) for GMM/SM signalling (LLC SAPI 1), or +- PFI=2 (SMS) for Short Message Service (LLC SAPI 7), or +- PFI=3 (TOM8) for LLC SAPI 8 data. + +### 5.5.1.10 Acquisition of E-UTRAN Information on the PACCH + +An MS that receives a full set of instances of the PACKET MEASUREMENT ORDER message that includes one or more IEs used to provide E-UTRAN related information shall proceed as follows: + +- The information provided by all instances of the *Repeated E-UTRAN Neighbour Cells* IE (alternatively, for an MS supporting extended EARFCNs, all instances of the *E-UTRAN NC with extended EARFCNs* IE when applicable, see sub-clause 11.2.9b) shall be added to the E-UTRAN Neighbour Cell list built by the last received consistent set of SI2quater message instances, or the last received consistent set of SI23 message instances if SI23 is broadcast in the cell and for a mobile station supporting network sharing (see sub-clause 5.6.3.1a). +- The information provided by all instances of the *Repeated E-UTRAN Not Allowed Cells* IE for any given frequency shall be used to build a new E-UTRAN Not Allowed Cells list for that frequency. +- The information provided by all instances of the *Repeated E-UTRAN PCID to TA mapping* IE for any given frequency shall be used to build new E-UTRAN PCID to TA mapping for that frequency. + +If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that excludes an IE used to provide E-UTRAN related information that was provided within the last received consistent set of SI2quater (or alternatively SI23) message instances (e.g. the *Priority and E-UTRAN Parameters Description struct* provides a "0" for the *E-UTRAN Parameters Description* IE), the MS shall resort back to using the corresponding information provided by the last received SI2quater (or alternatively SI23) message (see NOTE 1 and NOTE 2). + +If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that includes an IE used to provide E-UTRAN related information that was provided within the last received consistent set of SI2quater (or alternatively SI23) message instances but none of the fields associated with the included IE provide any information, the MS shall resort back to using the corresponding information provided by the last received SI2quater (or alternatively SI23) message (see NOTE 1 and NOTE 2). + +If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that includes an IE used to provide E-UTRAN related information but only a subset of the fields associated with the included IE actually provide information, the MS shall use the fields that provide information to update their corresponding stored parameters and shall use values for the fields for which no information was provided as described in Table 11.2.9b.2 (see NOTE 2). + +If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that limits the information provided within the *Repeated E-UTRAN Not Allowed Cells* IE to only providing one or more E-UTRAN frequency indices (i.e. only the E-UTRAN\_FREQUENCY\_INDEX field contains information), the MS shall ignore this IE. + +NOTE 1: If the last received consistent set of SI2quater (or alternatively SI23) message instances has not provided a value for any given E-UTRAN related parameter then the MS uses the default value for that parameter unless otherwise specified. + +NOTE 2: An MS that supports extended EARFCNs shall build its E-UTRAN Neighbour Cell list from the *E-UTRAN NC with extended EARFCNs* IE when included in the PACKET MEASUREMENT ORDER message. + +## 5.5.2 Network side + +### 5.5.2.1 System Information broadcasting + +#### 5.5.2.1.1 System information on PBCCH + +If PBCCH is present in the cell, the network regularly broadcasts PACKET SYSTEM INFORMATION TYPE (PSI) 1, 2, 3 and 3bis messages, and optionally PSI3ter, PSI3quater and some types of PSI messages on the PBCCH. The PSI 2, PSI 3bis, PSI3 ter, PSI3quater messages and some further types of PSI messages may be broadcast in multiple number of instances. Based on the information broadcast in PSI messages, the mobile station is able to decide whether and how it may gain access to the system via the current cell. + +NOTE: The network should take into account the limitations of earlier version of mobile equipments to understand the 3-digit MNC format of the location area identification, see sub-clause 12.23 and 3GPP TS 44.018, table "Location Area Identification .information element". + +Instances of the PSI 5 message are broadcast on PBCCH if the mobile stations camping on the cell shall perform measurement reporting, see 3GPP TS 45.008. + +Instances of the PSI6 and PSI7 message may be broadcast on the PBCCH if non-GSM broadcast information is transmitted. + +The PSI8 message may be broadcast on the PBCCH if additional information (i.e. CBCH configuration and dynamic ARFCN mapping) shall be provided to the mobile station camping on the cell. + +The PSI1 message contains the PBCCH\_CHANGE\_MARK and PSI\_CHANGE\_FIELD parameters. The value of the PBCCH\_CHANGE\_MARK may be incremented by one, modulo 8, each time the network makes a change in the PBCCH information. Such change includes any addition, removal or replacement of PSI messages, contents of PSI messages, or change in the scheduling of PSI messages on PBCCH. A change in the contents of the PSI1 message alone shall not be reflected in the PBCCH\_CHANGE\_MARK. When the PBCCH\_CHANGE\_MARK is incremented, the PSI\_CHANGE\_FIELD parameter shall be set to an appropriate value to indicate the nature of the latest change in the PBCCH information. + +The network may increment the PBCCH\_CHANGE\_MARK value by more than one, modulo 8, in order to enforce a complete acquisition of PBCCH information of all mobile stations. + +In order to avoid extensive TBF suspensions following an increment of the PBCCH\_CHANGE\_MARK parameter, the network may send PSI messages on PACCH to mobile stations in packet transfer mode. + +The network indicates the support of the PACKET PSI STATUS and EGPRS PACKET CHANNEL REQUEST messages in the PSI1 message. + +#### 5.5.2.1.2 System information on BCCH + +In addition to the requirements in 3GPP TS 44.018, a SYSTEM INFORMATION TYPE 13 (SI13) message is regularly broadcast by the network on the BCCH to support GPRS. Optionally and if PBCCH is not present in the cell, additional types of SI messages may be broadcast on BCCH. Some of them may be broadcast in multiple number of instances. If PBCCH is present in the cell, only the SI13 message is required on BCCH to support GPRS. + +Based on this information, the GPRS mobile station is able to decide whether and how it gains access to the system via the current cell when PBCCH is not present. + +The SI13 message contains the BCCH\_CHANGE\_MARK and SI\_CHANGE\_FIELD parameters. If PBCCH is not present in the cell, the value of the BCCH\_CHANGE\_MARK may be incremented by one, modulo 8, each time the network makes a change in the BCCH information. Such change includes any addition, removal or replacement of SI messages, contents of SI messages, or change in the scheduling of SI messages on BCCH. Changes in the contents of the SI13 message shall not to be reflected in the BCCH\_CHANGE\_MARK. Changes of the contents of the RACH Control Parameters information element alone (see 3GPP TS 44.018) may optionally be reflected in the BCCH\_CHANGE\_MARK; if reflected, the SI\_CHANGE\_FIELD parameter may indicate only one of the SI message containing the RACH Control Parameters. When the BCCH\_CHANGE\_MARK is incremented, the SI\_CHANGE\_FIELD parameter shall be set to an appropriate value to indicate the nature of the latest change in the BCCH information. + +When PBCCH is not present in the cell, the network may increment the BCCH\_CHANGE\_MARK value by more than one, modulo 8, in order to enforce a complete acquisition of BCCH information of all mobile stations. + +If PBCCH is not present in the cell, instances of the SI 18 and SI 20 message may be broadcast on the BCCH if non-GSM broadcast information is transmitted. + +The network indicates the support of the PACKET SI STATUS message in the SI13 message. + +#### 5.5.2.1.3 System information on PACCH (and other logical channels) + +The network may broadcast PSI and SI messages on PACCH. In particular, if a mobile station is busy in packet transfer mode or MAC-Shared state and thus unable to receive the relevant blocks on the broadcast channels (PBCCH or BCCH) for a period longer than 15 seconds, the following requirements apply: + +- If PBCCH is present in the cell, the network may broadcast the PSI1 message on PACCH such that the mobile station may receive the PSI1 message at least every 15 s. + +- If PBCCH is not present in the cell, the network may broadcast the PSI13 message on PACCH such that the mobile station may receive the PSI13 messages at least every 15 s. + +If the network has indicated the use of in-band signalling for a given MBMS radio bearer (with the MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT message in the serving cell and/or in the MBMS NEIGHBOURING CELL INFORMATION message in the old cell), it shall broadcast the full system information on PACCH of that MBMS radio bearer, as described in sub-clause 5.5.2.1.3b. + +Furthermore, the network may broadcast PSI messages on PCCCH. In particular, the network may send the PSI1 and PSI13 messages on PCCCH to notify mobile stations in packet idle mode or MAC-Idle state about changes in the PBCCH information or changes of the PBCCH channel description. + +If the network supports the PACKET PSI STATUS message and this message is received from a mobile station, the network may schedule the missing PSI messages for that mobile station on PACCH (sub-clause 5.5.1.4.3). Optionally, the missing PSI messages may be sent in one or more instances of the PACKET SERVING CELL DATA message for that mobile station on PACCH. + +If the network supports the PACKET SI STATUS message and this message is received from a mobile station, the network may schedule the missing SI messages in one or more instances of the PACKET SERVING CELL DATA message for that mobile station on PACCH (sub-clause 5.5.1.4.3), or, in case the mobile station has indicated in the PACKET SI STATUS message that it supports the PACKET SERVING CELL SI message, the network should use the PACKET SERVING CELL SI messages instead of the PACKET SERVING CELL DATA messages. + +If the network supports the SI2n message, it shall always use the PACKET SERVING CELL SI message when broadcasting the SI2n messages on PACCH. + +- NOTE: This is required due to the fact that the PACKET SERVING CELL SI is a distribution message making it possible for all mobile stations capable of decoding the SI2n message and listening to the PACCH to be able to receive the content. + +The network may send the PSI14 message on PACCH to a mobile station in dual transfer mode or MAC-DTM state. The scheduling of the PSI14 message is determined by the network. + +If PBCCH is present in the cell and the network changes the contents of any of the PSI messages, it shall set the PSI\_CHANGED\_IND to "1" in all the PSI14 messages it sends in the next 30 seconds. Otherwise, the PSI\_CHANGED\_IND shall be set to "0". + +When a PSI or SI message is received on PACCH during dual transfer mode, no parameters except those relevant for monitoring possible changes in the contents of SI or PSI messages (e.g. PBCCH\_CHANGE\_MARK, BCCH\_CHANGE\_MARK, PSI\_CHANGED\_IND) shall be applied by the MS for operation in dual transfer mode. + +The network may send neighbour cell PSI and SI messages on PACCH in one or more instances of the PACKET NEIGHBOUR CELL DATA message (see sub-clause 8.8.1). + +### 5.5.2.1.3a Rules for (P)SI distribution within Packet Serving Cell Data messages + +In order to ensure a consistent distribution and decoding of (P)SI messages contained in PACKET SERVING CELL DATA messages, the following rules shall apply: + +- Whenever the network starts sending a set of PACKET SERVING CELL DATA message instances in response to any PACKET (P)SI STATUS message, the first PACKET SERVING CELL DATA message instance shall be started with CONTAINER\_INDEX=0. If SI1 is broadcast in the serving cell and the MS has requested the SI1 message, the network shall include the SI1 message as the first SI message contained in the set of PACKET SERVING CELL DATA messages, starting from the message with CONTAINER\_INDEX=0. If the MS is able to decode the first SI message contained in the set of PACKET SERVING CELL DATA messages but it was not the SI1 message, the MS shall conclude that SI1 is not broadcast in the serving cell. +- All subsequent instances of a PACKET SERVING CELL DATA message set shall be sent in ascending order of CONTAINER\_INDEX value. It is allowed to send a PACKET SERVING CELL DATA message with the same CONTAINER\_INDEX value more than once. +- Whenever the MS receives a PACKET SERVING CELL DATA message instance with CONTAINER\_INDEX=0 or with a CONTAINER\_INDEX value that is less than the CONTAINER\_INDEX value of the last received PACKET SERVING CELL DATA message instance, it shall delete any PACKET + +SERVING CELL DATA message instances it may have stored but it shall keep the already extracted PSI/SI message instances. + +- Whenever the MS leaves packet transfer mode, it shall delete any PACKET SERVING CELL DATA message instances it may have stored but it shall keep the already extracted PSI/SI message instances. + +NOTE : In order to increase the probability that the MS receives the PACKET SERVING CELL DATA message instances (especially the one with CONTAINER\_INDEX =0), the network may poll the MS with a valid RRBP field in the RLC/MAC header of a PACKET SERVING CELL DATA message. Alternatively, the network may repeat the PACKET SERVING CELL DATA message instances one or more times. + +#### 5.5.2.1.3b Rules for (P)SI distribution on PACCH of an MBMS radio bearer + +If the network has indicated the use of in-band signalling for a given MBMS radio bearer, it shall broadcast on the PACCH the full system information provided on the (P)BCCH: + +- In case PBCCH is allocated in the cell, the network shall broadcast the consistent set of PSI messages (it broadcasts on PBCCH), on the PACCH/D of the MBMS radio bearer. +- In case PBCCH is not allocated in the cell, the network shall broadcast the consistent set of SI messages (it broadcasts on the BCCH), on the PACCH/D of the MBMS radio bearer using PACKET SERVING CELL SI messages. + +#### 5.5.2.1.4 Consistent sets of system information messages + +Certain types of PSI and SI messages are sent on PBCCH and BCCH in a multiple number of instances. If such a PSI or SI message type is sent on (P)BCCH, the mobile station shall receive a consistent set of that type of PSI or SI message. In some cases, more than one type of PSI messages may be joined into one consistent set, see table 5.5.2.1.4.1. + +**Table 5.5.2.1.4.1: Consistent sets of system information messages** + +| Consistent set / Message Type(s) | Broadcast Channel | Number of instances | PSI or SI change mark parameter | PSI or SI index parameter | PSI or SI count parameter | +|----------------------------------|-------------------|---------------------|-------------------------------------------------|---------------------------|---------------------------| +| PSI2 | PBCCH | 1 - 8 | PSI2_CHANGE_MARK
(Note 3) | PSI2_INDEX | PSI2_COUNT | +| PSI3 | PBCCH | 1 | PSI3_CHANGE_MARK | | | +| PSI3 bis | PBCCH | 1 - 16 | PSI3_CHANGE_MARK | PSI3bis_INDEX | PSI3bis_COUNT | +| PSI3 ter | PBCCH | 0 - 16 | PSI3_CHANGE_MARK | PSI3ter_INDEX | PSI3ter_COUNT | +| PSI3 quater | PBCCH | 0 - 16 | PSI3_CHANGE_MARK | PSI3quater_INDEX | PSI3quater_COUNT | +| PSI5 | PBCCH | 0 - 8 | PSI5_CHANGE_MARK | PSI5_INDEX | PSI5_COUNT | +| PSI6 | PBCCH | 0 - 8 | PSI6_CHANGE_MARK | PSI6_INDEX | PSI6_COUNT | +| PSI7 | PBCCH | 0 - 8 | PSI7_CHANGE_MARK | PSI7_INDEX | PSI7_COUNT | +| PSI8 | PBCCH | 0 - 8 | PSI8_CHANGE_MARK | PSI8_INDEX | PSI8_COUNT | +| SI13
(Notes 1 and 2) | BCCH | 1 | SI13_CHANGE_MARK
(Note 3) | | | +| SI2 ter | BCCH | 0 - 8 | SI2ter_MP_CHANGE_MARK and SI2ter_3G_CHANGE_MARK | SI2ter_INDEX | SI2ter_COUNT | +| SI2 quater | BCCH | 0 - 16 | BA_IND, 3G_BA_IND and MP_CHANGE_MARK | SI2quater_INDEX | SI2quater_COUNT | +| SI2n | BCCH | 0 - 16 | SI2n_CHANGE_MARK | SI2n_INDEX | SI2n_COUNT | +| SI15 | BCCH | 0 - 4 | DM_CHANGE_MARK | SI15_INDEX | SI15_COUNT | +| SI18 | BCCH | 0 - 8 | SI18_CHANGE_MARK | SI18_INDEX | None (Note 4) | +| SI19 | BCCH | 0 - 8 | SI19_CHANGE_MARK | SI19_INDEX | None (Note 4) | +| SI20 | BCCH | 0 - 8 | SI20_CHANGE_MARK | SI20_INDEX | None (Note 4) | +| SI21 | BCCH | 0 - 8 | SI21_CHANGE_MARK | SI21_INDEX | SI21_COUNT | +| SI22 | BCCH | 0 - 8 | SI22_CHANGE_MARK | SI22_INDEX | SI22_COUNT | +| SI23 | BCCH | 0 - 8 | SI23_CHANGE_MARK | SI23_INDEX | SI23_COUNT | + +NOTE 1: If the SI13 message provides a GPRS mobile allocation, it shall also provide an SI13\_CHANGE\_MARK. The SI13\_CHANGE\_MARK shall be used if the indirect encoding of the frequency information is applied in a packet assignment, referring to the GPRS mobile allocation provided in the SI13 message. There is only one instance of the SI13 message. + +NOTE 2: The PSI13 message may be received on PACCH. It provides the same information as SI13, including the SI13\_CHANGE\_MARK. + +NOTE 3: If PSI2 and SI13 *change mark* values need to be distinguished, e.g. during an activation or release of PBCCH, the network should assign appropriate values to these parameters. + +NOTE 4: For SI18, SI19 and SI20 messages, there is no *count* parameter (see 3GPP TS 44.018). + +A consistent set of system information messages is identified by a PSI or SI *change mark* parameter included in each message in the set. All messages within a consistent set shall have the same value of this parameter. + +The total number of system information messages of a certain type within a consistent set is indicated by a PSI or SI *count* parameter included in each message in the set. The position of a certain message instance within the consistent set of system information messages is indicated by a PSI or SI *index* parameter. + +The PSI or SI *count* parameter shall have the value N-1, where N is the number of instances of the particular message type present in the consistent set. The PSI or SI *index* parameter shall have a range from zero to N-1. Different instances of a particular message type in a consistent set shall have different values of the PSI or SI *index* parameter. + +## 5.5.2.2 Paging + +The network is required to send valid RLC data blocks or RLC/MAC control blocks continuously on all subchannels on PCCCH where paging can appear. + +NOTE: If RLC data blocks are sent in the blocks on PCCCH where paging may appear, the network uses the coding schemes CS-1 to CS-4, in order to avoid the expiry of the downlink signalling counter for non-EGPRS capable mobile stations (see 3GPP TS 45.002). + +## 5.5.2.3 Network Assisted Cell Change + +A cell that supports GPRS (in *A/Gb mode*) and/or *Iu mode* shall indicate if CCN is enabled. This shall be indicated on BCCH and on PBCCH in the parameter CCN\_ACTIVE (see sub-clause 12.24). The network may also send a PACKET + +MEASUREMENT ORDER message with the parameter CCN\_ACTIVE set to order an individual mobile station to apply the CCN procedures in the serving cell or a PACKET CELL CHANGE ORDER or a PS HANDOVER COMMAND message to order an individual mobile station to apply the CCN procedures in the new cell. This parameter controls the overall enabling of CCN. The network may also indicate in system information messages sent on BCCH and PBCCH and individually in the PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER or PS HANDOVER COMMAND messages whether CCN mode shall be entered towards a particular cell (see sub-clause 8.8.2). A GSM cell that supports PS handover to *GAN mode* shall ensure that CCN is enabled for all GAN neighbour cells. + +The network may also send neighbour cell system information on PACCH to be used by the mobile station at initial access after cell re-selection (see sub-clause 8.8.1). + +When the network receives a PACKET CELL CHANGE NOTIFICATION message from the mobile station, the network may respond by sending neighbour cell system information for the proposed cell or another cell and also complete the transmission of ongoing data packets before sending a PACKET CELL CHANGE CONTINUE message (to confirm the proposed cell) or a PACKET CELL CHANGE ORDER message. The neighbour cell information is sent in PACKET NEIGHBOUR CELL DATA messages. + +The ARFCN for BCCH and the BSIC identifying a GSM neighbour cell shall be included in the PACKET CELL CHANGE CONTINUE message in case a set of PACKET NEIGHBOUR CELL DATA messages referred by the corresponding CONTAINER\_ID value was sent for that cell without ARFCN and BSIC provided. If included by the network in the PACKET CELL CHANGE CONTINUE message, ARFCN and BSIC shall reflect the cell proposed in the PACKET CELL CHANGE NOTIFICATION message. Upon reception of the PACKET CELL CHANGE CONTINUE message the mobile station shall continue the cell reselection in NC0/NC1 mode irrespective of the cell indicated in the ARFCN and BSIC parameters. + +## 5.5.2.4 Packet Switched Handover + +Packet switched handover is applicable only in packet transfer mode. + +If the network supports PS handover it may initiate the PS handover procedure for a mobile station that supports PS handover as a result of various trigger conditions such as, but not restricted to, the following: + +- Upon reception of a PACKET CELL CHANGE NOTIFICATION message from a mobile station operating in NC0. +- Upon reception of a PACKET CELL CHANGE NOTIFICATION message or measurement reports from a mobile station operating in NC1. +- Upon reception of measurement reports from a mobile station operating in NC2. +- Upon determining that resource limitations exist for the serving cell. +- Upon receiving the *Service UTRAN CCO* IE from the SGSN indicating that a mobile station operating in A/Gb mode would be better served in a cell supporting a different RAT. + +For PS handover to a GSM neighbour cell the NC mode applicable to the new cell shall be indicated by the PS HANDOVER COMMAND message sent to the mobile station in the old cell. + +## 5.6 Measurement reports + +### 5.6.0 General + +The network may request measurement reports from the MS. The measurement reporting principles are specified in 3GPP TS 45.008. The measurement reports consists of + +- Network Control (NC) measurement reports sent when the MS is in *A/Gb mode* and GMM Ready state (see 3GPP TS 24.008) or the MS is in *Iu mode* and in RRC-Cell\_Shared state; this may be performed with either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message. + +## 5.6.1 Network Control (NC) measurement reporting + +The behaviour of the mobile station is controlled by the parameter NETWORK\_CONTROL\_ORDER broadcast in the PSI5 message on PBCCH, in the SI13 and SI2quater messages on the BCCH and in the PSI13 message on PACCH. Alternatively, the network may send the NETWORK\_CONTROL\_ORDER parameters in a PACKET MEASUREMENT ORDER or in a PACKET CELL CHANGE ORDER message on PCCCH or PACCH to a particular mobile station or in a PS HANDOVER COMMAND message sent on PACCH to a particular mobile station. The parameter NETWORK\_CONTROL\_ORDER may have one of the values NC0, NC1, NC2 or RESET, see 3GPP TS 45.008. + +When in mode NC1 or NC2, the mobile station shall perform the NC measurements as defined in 3GPP TS 45.008. The reporting periods are indicated in the NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T field of the PSI5, the SI2quater, the PACKET CELL CHANGE ORDER or the PACKET MEASUREMENT ORDER message. If NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I or NC\_REPORTING\_PERIOD\_T have not been received by the mobile station the default values shall be used. The mobile station shall apply to the timer T3158 either the NC\_REPORTING\_PERIOD\_I when in packet idle mode or the NC\_REPORTING\_PERIOD\_T when in packet transfer mode. The measurement results shall be sent to the network using the procedures specified in sub-clause 7.3 for packet idle mode, and in sub-clause 8.3 for packet transfer mode. + +On expiry of timer T3158, the mobile station shall restart timer T3158 with the indicated reporting period, perform the measurements and send either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT to the network. The condition for sending the PACKET ENHANCED MEASUREMENT REPORT message instead of the PACKET MEASUREMENT REPORT message is based on the REPORT\_TYPE parameter and if the MS has received BSIC information for all cells. For the detailed conditions see sub-clauses 11.2.23, 11.2.4 and 11.2.9b and also 3GPP TS 44.018 sub-clause 10.5.2.33b. A mobile station in packet idle mode (respectively packet transfer mode) in NC2 may transmit a PACKET CELL CHANGE NOTIFICATION message, instead of a PACKET MEASUREMENT REPORT message or PACKET ENHANCED MEASUREMENT REPORT message, if the conditions in sub-clause 5.6.3.9 are met. A mobile station shall send no more than one PACKET CELL CHANGE NOTIFICATION per ([4] x NC\_REPORTING\_PERIOD\_I) seconds (respectively ([4] x NC\_REPORTING\_PERIOD\_T) seconds). + +A mobile station in mode NC1 or NC2 may receive a new indicated reporting period while timer T3158 is active. If the new indicated reporting period is less than the time to expiry of timer T3158, the mobile station shall immediately restart timer T3158 with the new indicated reporting period. Otherwise, the timer T3158 shall continue to run. + +When changing from packet transfer mode to packet idle mode, a mobile station in mode NC1 or NC2 shall restart the timer T3158 with the reporting period determined by the NC\_REPORTING\_PERIOD\_I parameter if at least one PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message was sent in packet transfer mode. Otherwise the timer T3158 shall continue to run. + +When changing from packet idle mode to packet transfer mode, a mobile station in mode NC1 or NC2 shall restart the timer T3158 with the reporting period determined by the NC\_REPORTING\_PERIOD\_T parameter if the reporting period is less than the time to expiry of timer T3158. Otherwise the timer T3158 shall continue to run. + +When a mobile station leaves the GMM Ready state, the timer T3158 shall be stopped and no more measurement reports shall be sent to the network. + +A mobile station may reselect a new cell or may be ordered to reselect a new cell with mode NC1 or NC2 while timer T3158 is active. If time to expiry of timer T3158 is greater than the indicated reporting period for the new cell, the mobile station shall immediately restart timer T3158 with the indicated reporting period for the new cell. Otherwise, the timer T3158 shall continue to run. + +At cell reselection the NC measurement parameters valid for the mobile station in the new cell (NETWORK\_CONTROL\_ORDER, NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T) are either: + +- brought from the old cell if received in a PACKET CELL CHANGE ORDER message sent in the old cell; or +- received in a broadcast PSI5, SI13, PSI13 or SI2quater message in the new cell. If no parameters have been brought from the old cell, and until individual measurement parameters are received in the new cell, the mobile station shall use the broadcast measurement parameters from PSI5 if a PBCCH is allocated in the cell or SI2quater if a PBCCH is not allocated in the cell or use the default parameter values. + +The default frequency list to be applied in the new cell following a cell reselection or the successful completion of the PS handover procedure shall be the BA(GPRS) list of that cell until a new PACKET MEASUREMENT ORDER message is received. For the case of cell reselection the BA(GPRS) list could also have been modified by frequency parameters received in a PACKET CELL CHANGE ORDER message in the old cell. + +For (NC) measurements reporting, the Mobile Station shall use PACKET ENHANCED MEASUREMENT REPORT messages instead of PACKET MEASUREMENT REPORT messages if that is indicated by the parameter REPORT\_TYPE and if at least one BSIC is allocated to each frequency in the BA(GPRS) list. + +For a mobile station supporting UTRAN, reports on 3G cells may also be included in the reporting. For a mobile station supporting "E-UTRAN Neighbour Cell measurements and MS autonomous cell reselection to E-UTRAN", reports on E-UTRAN cells may also be included in the reporting. For report with the PACKET MEASUREMENT REPORT message, reporting is performed on three separate lists: the BA(GPRS), the 3G Neighbour Cell List (for a multi-RAT MS supporting UTRAN) and the E-UTRAN Neighbour Cell List (for a MS supporting "E-UTRAN Neighbour Cell measurements and MS autonomous cell reselection to E-UTRAN"). For report with the PACKET ENHANCED MEASUREMENT REPORT message, reporting is performed on the Neighbour Cell List (defined in sub-clause 5.6.3.3) and the E-UTRAN Neighbour Cell List (for a multi-RAT MS supporting "E-UTRAN Neighbour Cell measurements and MS autonomous cell reselection to E-UTRAN"). + +A multi-RAT MS supporting UTRAN and/or E-UTRAN with no CSG Whitelist or an empty CSG Whitelist shall not send any measurement reports for cells that are known to be UTRAN/E-UTRAN CSG cells. A multi-RAT MS supporting UTRAN and/or E-UTRAN which is a member of at least one Closed Subscriber Group (i.e. at least one CSG ID is included in its CSG Whitelist) but does not support CSG Cells Reporting shall not send any measurement reports for cells that are known to be UTRAN/E-UTRAN CSG cells other than in a PACKET CELL CHANGE NOTIFICATION message for a CSG cell which is the proposed target cell (see sub-clause 8.8.3). + +The reporting of CSG cells and hybrid cells is specified in sub-clause 5.6.3.9. + +A mobile station involved in an RR connection (in class A mode of operation), shall not send Network Control measurement reports to the network during that period. The mobile station shall return to the previous reporting mode when the RR connection is released. + +## 5.6.2 (void) + +## 5.6.3 Additional measurement and reporting parameters + +Some parameters from the PACKET MEASUREMENT ORDER, PACKET CELL CHANGE ORDER, SI2quater, SI23, PSI3bis, PSI3ter, PSI3quater or PSI5 messages allow to build GPRS Measurement Parameters, GPRS 3G Measurement Parameters, GPRS E-UTRAN Measurement Parameters and neighbour cell lists which are used for Network Control (NC) measurement reporting. + +### 5.6.3.1 Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell description + +In a cell without a PBCCH allocated, the 3G Neighbour Cell list is given by one or more instances of the SI2quater message with the same 3G\_BA\_IND value. If the SI23 message is broadcast in the cell, for a UTRAN capable mobile station supporting network sharing the 3G neighbour Cell list is given by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G\_BA\_IND value. + +In a cell with a PBCCH allocated, the 3G Neighbour Cell list is given by one or more instances of the PSI3quater message with the same PSI3\_CHANGE\_MARK value. + +The 3G Neighbour cell list may be modified by a PACKET CELL CHANGE ORDER message (in which case the reference list is given on the new cell) or by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G\_BA\_IND value as in the SI2quater message or PSI3\_CHANGE\_MARK value as in the PSI3quater message. A UTRAN capable mobile station supporting network sharing shall build its 3G Neighbour Cell list from the information received in the PACKET CELL CHANGE ORDER message (in which case the 3G Neighbour Cell list is only used in the new cell if the SI23 message is broadcast in the new cell). + +The 3G Neighbour Cell list may contain up to 96 3G Neighbour Cells and/or UTRAN frequencies for RSSI reporting. + +Each *3G Neighbour Cell Description* received is added to the 3G Neighbour Cell list, starting with the index equal to the parameter Index\_Start\_3G. If this parameter is not present then the value 0 shall be used. + +For each *3G Neighbour Cell Description* received, the cells / UTRAN frequencies are indexed in the following order: + +- 1: UTRAN FDD cells / UTRAN FDD frequencies: FDD UARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. For each FDD UARFCN indicating UTRAN FDD cells, the cells are indexed in the order of increasing values of the decoded FDD\_CELL\_INFORMATION parameters. +- 2: UTRAN TDD cells / UTRAN TDD frequencies: TDD UARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. For each TDD UARFCN indicating UTRAN TDD cells, the cells are indexed in the order of increasing values of the decoded TDD\_CELL\_INFORMATION parameters. + +If more than one cell / UTRAN frequency with the same index in the 3G Neighbour Cell list are provided by different instances of 3G Neighbour Cell descriptions, the cell / UTRAN frequency from the message instance with the highest index shall be used. In case the same 3G Cell / UTRAN frequency occurs more than once in the resulting 3G Neighbour Cell list, each occurrence shall be assigned an index but only the cell / UTRAN frequency with the highest index in the 3G Neighbour Cell list shall be referred to in measurement reports. + +The *3G Neighbour Cell Description* may contain information on 3G Neighbour Cells / UTRAN frequencies to be removed (*REMOVED\_3GCELL\_Description*). The cells / UTRAN frequencies to be removed are identified by their indices in the 3G Neighbour Cell list. Removed cells / UTRAN frequencies shall keep their indices but no measurement shall be performed. If the index is higher than 95 or points to a 3G cell / UTRAN frequency that does not exist, this shall not be considered as an error. + +In a cell without PBCCH allocated, the mobile station shall only combine 3G Neighbour cells / UTRAN frequencies from SI2quater (or PACKET MEASUREMENT ORDER, if the SI23 message is broadcast) message instances indicating the same value of the 3G\_BA\_IND without any message instance indicating a different value of the 3G\_BA\_IND received in between. + +In a cell with a PBCCH allocated, the mobile station shall only combine 3G Neighbour cells / UTRAN frequencies from PSI3quater messages indicating the same PSI3\_CHANGE\_MARK value. + +If a 3G Neighbour Cell Description includes non-supported frequencies or Radio Access Technologies or if the same cell / UTRAN frequency occurs more than once, this shall not be considered as an error; indices in the 3G neighbour Cell list shall be incremented accordingly. If a cell / UTRAN frequency is provided for an index higher than 95 in the 3G Neighbour Cell list, this shall not be considered as an error; the cell / UTRAN frequency shall not be included in the 3G Neighbour Cell list. + +For a mobile station indicating support for UTRA Multiple Frequency Band Indicators (MFBI) in the MS Radio Access Capabilities IE (see 3GPP TS 24.008), the network may send different FDD ARFCN values corresponding to different frequency bands but designating the same physical UTRAN frequency in the PACKET CELL CHANGE ORDER message or in the PACKET MEASUREMENT ORDER message. The network may also broadcast different FDD ARFCN values corresponding to different frequency bands but designating the same physical UTRAN frequency in the SI2quater message; in such a case, a mobile station supporting UTRA Multiple Frequency Band Indicators (MFBI) shall consider a FDD ARFCN value belonging to frequency band it does not support as a non-supported frequency. When a PACKET CELL CHANGE ORDER message or a PACKET MEASUREMENT ORDER message or a SI2quater message is received by the MFBI capable MS, each occurrence of a FDD ARFCN corresponding to different frequency bands but designating the same physical UTRAN frequency shall be assigned an index in the 3G Neighbour Cell list. However, only the highest index in the list that corresponds to a supported frequency band shall be referred to in measurement reports. + +The MS behaviour is not specified if the number of 3G frequencies or cells exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008. + +### 5.6.3.1a Deriving the E-UTRAN Neighbour Cell list from the Repeated E-UTRAN Neighbour Cell information + +The E-UTRAN Neighbour Cell list is given by one or more instances of the SI2quater message with the same 3G\_BA\_IND value, or alternatively, if the SI23 message is broadcast in the cell and for a mobile station supporting network sharing, by one or more instances of the SI23 message with the same SI 23\_BA\_IND value, see 3GPP TS 44.018. + +If the mobile station receives a full set of instances of the PACKET MEASUREMENT ORDER message (see sub-clause 11.2.9b) with the same 3G\_BA\_IND value as in the SI2quater message, each *E-UTRAN Parameters Description* IE received therein (alternatively, for a mobile station supporting extended EARFCNs, each *E-UTRAN NC with extended EARFCNs* IE received therein) shall be used to modify the E-UTRAN Neighbour Cell list received from SI2quater. When a mobile station supporting network sharing builds its E-UTRAN Neighbour Cell list from the + +information received in the SI23 message, this list shall only be modified if the mobile station receives a full set of instances of the PACKET MEASUREMENT ORDER message with the same 3G\_BA\_IND value as the SI 23\_BA\_IND value in the SI23 message, in which case each *E-UTRAN Parameters Description IE* (alternatively, each *E-UTRAN NC with extended EARFCNs IE*) received therein shall be used to modify the E-UTRAN Neighbour Cell list received from SI23. + +If the mobile station supporting extended EARFCNs receives a PACKET MEASUREMENT ORDER message with both *Repeated E-UTRAN Neighbour Cell IE* and *E-UTRAN NC with extended EARFCNs IE* included therein, it shall ignore the message. + +The E-UTRAN Neighbour Cell list may contain up to 8 E-UTRAN frequencies. Each frequency described by a *Repeated E-UTRAN Neighbour Cell IE* is added to the E-UTRAN Neighbour Cell list in the order in which they appear in the message. Different instances of the Repeated E-UTRAN Neighbour Cells IE shall be evaluated in ascending order of the PMO\_INDEX of the PACKET MEASUREMENT ORDER message that they are received in. + +In case the same E-UTRAN frequency occurs more than once in the resulting E-UTRAN Neighbour Cell list, each occurrence shall be assigned an index but only the E-UTRAN frequency with the highest index in the E-UTRAN Neighbour Cell list shall be referred to in measurement reports. + +For a mobile station indicating support for E-UTRA Multiple Frequency Band Indicators (MFBI) in the MS Radio Access Capabilities IE (see 3GPP TS 24.008), the network may send different EARFCN values corresponding to different frequency bands but designating the same physical E-UTRAN frequency in the PACKET MEASUREMENT ORDER message. The network may also broadcast different EARFCN values corresponding to different frequency bands but designating the same physical E-UTRAN frequency in the SI2quater message or SI23 message; in such a case, a mobile station supporting E-UTRA Multiple Frequency Band Indicators (MFBI) shall consider an EARFCN value belonging to frequency band it does not support as a non-supported frequency. When a PACKET MEASUREMENT ORDER message or a SI2quater message or a SI23 message is received by the MFBI capable MS, each occurrence of an EARFCN corresponding to different frequency bands but designating the same physical E-UTRAN frequency shall be assigned an index in the E-UTRAN Neighbour Cell list. However, only the highest index in the list that corresponds to a supported frequency band shall be referred to in measurement reports. + +The mobile station behaviour is not specified if the number of E-UTRAN frequencies exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008. + +NOTE 1: Multiple instances of a PACKET MEASUREMENT ORDER message may be received as described in sub-clause 11.2.9b. + +### 5.6.3.2 Deriving BA(GPRS) and the GSM Neighbour Cell list + +In a cell without a PBCCH allocated, BA(GPRS) is equal to the BA (list) from the SI2/SI2bis/SI2ter messages. BSICs from the GPRS BSIC Description from one or more instances of the SI2quater message (if broadcast) shall be associated with BA(GPRS) with the same BA\_IND value to create the GSM Neighbour Cell list, as described in 3GPP TS 44.018 (sub-clause 3.4.1.2.1.2). When the mobile station has acquired the GSM Neighbour Cell list, the mobile station shall include in the measurement reports only cells present in that list. If GPRS BSIC Description is not broadcast, the GSM Neighbour Cell list is equal to BA(GPRS) (only a frequency list). + +In a cell with a PBCCH allocated, BA(GPRS) is derived from the neighbour cell parameters sent in PSI3 and ascending order of PSI3bis on PBCCH with the same PSI3\_CHANGE\_MARK value (see sub-clause 11.2.20). Each neighbour cell listed in PSI3 and in one or more instances of PSI3bis is assigned an ascending index used for measurement reports. The first neighbour cell in PSI3 has the lowest index (= 0), and the last neighbour cell in the highest indexed PSI3bis message has the highest index. The GSM Neighbour Cell list is equal to BA(GPRS). + +The GSM Neighbour Cell list may contain up to 96 GSM Neighbour Cells. The total number of frequencies to measure shall not exceed 32. If the list includes more than 32 frequencies, the MS shall only measure the 32 frequencies with the lowest indices. + +The GSM Neighbour Cell list may be modified by "NC Frequency List" in a PACKET CELL CHANGE ORDER message (in which case the reference list is given on the new cell) or one or more instances of the PACKET MEASUREMENT ORDER message with the same BA\_IND value or PSI3\_CHANGE\_MARK value. + +The "NC Frequency List" may add cells to the GSM Neighbour Cell list (see sub-clauses 11.2.4 and 11.2.9b). These cells shall be added at the end of the GSM Neighbour Cell list and indexed in the order of occurrence within the PACKET CELL CHANGE ORDER message or ascending instances of the PACKET MEASUREMENT ORDER + +message. The list of added cells may contain GPRS and optionally *Iu mode* cell re-selection parameters. The "NC Frequency List" does not impact the serving cell parameters. + +The "NC Iu Mode Only Capable Cell List" may add cells to the GSM Neighbour Cell list (see sub-clauses 11.2.4 and 11.2.9b). These *Iu mode* only capable cells shall be added at the end of the GSM Neighbour Cell list after *A/Gb mode* or both *A/Gb* and *Iu mode* capable cells and indexed in the order of occurrence within the PACKET CELL CHANGE ORDER message or ascending instances of the PACKET MEASUREMENT ORDER message. The list of added cells may contain *Iu mode* only cell re-selection parameters. + +In case the same cell (ARFCN+BSIC) or the same ARFCN without BSIC occur more than once in the resulting GSM Neighbour Cell list, each occurrence shall be assigned an index but only the cell with the highest index shall be used for cell re-selection and referred to in measurement reports. + +The "NC Frequency List" may delete frequencies from the BA(GPRS) list (see sub-clause 11.2.9b). The frequencies to be removed are identified by their indices in the BA(GPRS). In this case all cells associated with the removed frequencies shall be removed from the GSM Neighbour Cell list. Removed cells/frequencies shall keep their indices but no measurements or reporting shall be performed. If the index points to a cell that does not exist, this shall not be considered as an error. + +If the mobile station receives a PACKET MEASUREMENT ORDER message (full set of instances) with changed PMO\_IND parameter value, any old "NC frequency list" shall be deleted. If the last PACKET MEASUREMENT ORDER message (full set of instances) does not contain a "NC frequency list" (no added or deleted frequencies) the mobile station shall return to BA(GPRS). + +In a cell without PBCCH allocated, if the BA\_IND parameter is changed, the mobile station shall re-read and rebuild the GSM Neighbour Cell list. + +In a cell with a PBCCH allocated, if PSI3\_CHANGE\_MARK is changed, the mobile station shall re-read and rebuild the GSM Neighbour Cell list. + +### 5.6.3.3 Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list + +The Neighbour Cell list may contain up to 96 Neighbour Cells. For report with the PACKET ENHANCED MEASUREMENT REPORT message, the Neighbour Cell list is the concatenation of the GSM Neighbour Cell list and the 3G Neighbour Cell list (if any). In this concatenation the value of the parameter Absolute\_Index\_Start\_EMR is added to the 3G Neighbour Cell list indices. If the same index occurs for a GSM Cell and a 3G Cell, the GSM Cell shall be used. + +NOTE: For report with the PACKET MEASUREMENT REPORT message, the concatenated list is not used. Instead, the two lists are used separately, as defined in table 11.2.9.2 from sub-clause 11.2.9. + +### 5.6.3.4 GPRS Real Time Differences + +The GPRS Real Time Difference list may contain up to 96 Real Time Difference parameters. + +In a cell without PBCCH allocated, GPRS Real Time Difference information may be received from the SI2quater message and associated with the BA (list) from the SI2/SI2bis/SI2ter messages with the same BA\_IND value, see 3GPP TS 44.018. Each frequency in the BA (list) may be associated to 0, 1 or more Real Time Difference parameters. The Real Time Difference parameters may be received before the corresponding BA (list). The parameter BA\_Index\_Start\_RTD in each structure indicates the index of the frequency in the BA (list) to be taken as a starting reference. A sub-structure is included for each frequency referenced. Each of those sub-structures indicates if 0, 1 or more RTD parameters are present for this frequency. If a frequency in the BA (list) is not provided with Real Time Difference information by any of the message instances with correct BA\_IND value, it shall be assumed that no information is available for that frequency. If the MP\_CHANGE\_MARK parameter is changed, the mobile station shall re-read the Real Time Difference parameters. + +In a cell with a PBCCH allocated, GPRS Real Time Difference information may be received from the PSI3ter messages and associated with the GSM Neighbour Cell list with the same PSI3\_CHANGE\_MARK value. In this case each cell may be associated to 0 or 1 Real Time Difference parameter. The Real Time Difference parameters may be received before the corresponding GSM Neighbour Cell list. The parameter Cell\_Index\_Start\_RTD in each structure indicates the index of the cell in the GSM Neighbour Cell list to be taken as a starting reference. A sub-structure is included for each GSM Neighbour Cell referenced. Each of those sub-structures indicate if 0 or 1 RTD parameter is present for this GSM Neighbour Cell. If a cell in the GSM Neighbour Cell list is not provided with Real Time Difference information by any of the message instances with correct PSI3\_CHANGE\_MARK value, it shall be assumed that no information is available for that cell. If some Real Time Difference information are provided for a cell that does not exist, this shall not be considered as an error. See sub-clause 11.2.21. + +### 5.6.3.5 GPRS Report Priority Descriptions + +In a cell without PBCCH allocated, Report Priority information may be received from the SYSTEM INFORMATION TYPE 2 QUATER message and associated to the Neighbour Cell list with the same BA\_IND value and 3G\_BA\_IND value, see 3GPP TS 44.018. If the parameter MP\_CHANGE\_MARK is changed, the mobile shall re-read the GPRS Report Priority information. Each REP\_PRIORITY bit of this field relates to indices of the Neighbour Cell list starting with index 0. + +In a cell with a PBCCH allocated, Report Priority information for GSM cells may be received from the PACKET SYSTEM INFORMATION TYPE 3 TER message and associated to the GSM Neighbour Cell list with the same PSI3\_CHANGE\_MARK value, see sub-clause 11.2.21a. Each REP\_PRIORITY bit of this field relates to indices of the GSM Neighbour Cell list starting with index 0. + +In a cell with a PBCCH allocated, Report Priority information for 3G cells may be received from the PACKET SYSTEM INFORMATION TYPE 3 QUATER message and associated to the 3G Neighbour Cell list with the same PSI3\_CHANGE\_MARK value, see sub-clause 11.2.21b. Each REP\_PRIORITY bit of this field relates to indices of the 3G Neighbour Cell list starting with index 0. + +If Report Priority information is received as part of a PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER message, it is associated to the Neighbour Cell list and may be received before the corresponding Neighbour Cell list. Each REP\_PRIORITY bit of this field relates to indices of the Neighbour cell list, starting with index 0. + +Indices exceeding the value 95 shall be ignored. If there are fewer indices than the number of Neighbour Cells, the value 0 shall be assumed for the missing bits. + +### 5.6.3.6 GPRS Measurement Parameters and GPRS 3G Measurement Parameters + +In a cell without a PBCCH allocated, GPRS Measurement Parameters, GPRS 3G Measurement Parameters and 3G Priority Parameters may be received from SI2quater message, see 3GPP TS 44.018. When the parameter MP\_CHANGE\_MARK is changed, the mobile station shall re-read GPRS Measurement Parameters and GPRS 3G Measurement Parameters and 3G Priority Parameters. + +In a cell with a PBCCH allocated, GPRS Measurement Parameters and GPRS 3G Measurement Parameters may be received from PSI3quater and PSI5 messages, see sub-clauses 11.2.21b and 11.2.23. Additionally, 3G Priority Parameters may also be received from PSI3quater messages. When the PSI5\_CHANGE\_MARK parameter is changed, the MS shall re-read the corresponding Measurement Parameters and 3G Measurement Parameters. When the PSI3\_CHANGE\_MARK parameter is changed, the MS shall re-read the corresponding Measurement Parameters, 3G Priority Parameters and 3G Measurement Parameters. + +If different values are received for the same parameter in different instances of a message, only the value in the instance with the highest index shall be used. + +#### 5.6.3.6a GPRS E-UTRAN Measurement Parameters + +This sub-clause applies only to an E-UTRAN capable mobile station. + +GPRS E-UTRAN Measurement Parameters may be received from SI2quater message, see 3GPP TS 44.018. + +GPRS E-UTRAN Measurement Parameters may be modified by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G\_BA\_IND value as the SI2quater message. + +If different values are received for the same parameter in different instances of the PACKET MEASUREMENT ORDER message, only the value in the instance with the highest index shall be used. + +### 5.6.3.7 The GPRS 3G Cell Reselection list + +This sub-clause applies only to a (3G) multi-RAT MS. + +In a cell without a PBCCH allocated, the GPRS 3G Cell Reselection list is equal to the 3G Cell Reselection list that is defined in 3GPP TS 44.018. + +In a cell with a PBCCH allocated, the GPRS 3G Cell Reselection list is the union of 3G Cells and/or 3G frequencies provided in one or more instances of the PSI3quater message. The GPRS 3G Cell Reselection list may contain up to 96 3G Cells. 3G Cells not provided explicitly in the PSI3quater message (frequencies on their own) are not included in these 96 cells. Up to 8 frequencies on their own can be added to these 96 cells. + +The MS behaviour is not specified if the number of 3G frequencies or cells exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008. + +When the 3G Neighbour Cell list is modified by a PACKET CELL CHANGE ORDER message or by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G\_BA\_IND value as in the SI2quater message, the GPRS 3G Cell Reselection list shall be updated according to the modified 3G Neighbour Cell list. A UTRAN capable mobile station supporting network sharing shall build its 3G Cell Reselection list from the information received in the PACKET CELL CHANGE ORDER message (in which case the 3G Cell Reselection list is only used in the new cell if the SI23 message is broadcast in the new cell). If SI23 is broadcast in the cell and for a mobile station supporting network sharing, the 3G Cell Reselection list shall only be modified by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G\_BA\_IND value as the SI 23\_BA\_IND value broadcast in the SI23 message. + +NOTE: Frequencies for which the parameter NR\_OF\_FDD\_CELLS is set to 0 (and FDD\_Indic0 is set to 0) or NR\_OF\_TDD\_CELLS is set to 0 (and TDD\_Indic0 is set to 0) are not added to the GPRS 3G Cell Reselection list. They are added to the 3G Neighbour Cell list and are only used for RSSI reporting (subject to the restrictions given in 3GPP TS 45.008). Frequencies for which NR\_OF\_FDD\_CELLS is set to a value from 17 to 31 or NR\_OF\_TDD\_CELLS is set to a value from 21 to 31 are not added to the 3G Cell Reselection list (see sub-clause 11.2.9b). + +#### 5.6.3.7a (void) + +### 5.6.3.7b The 3G Frequency list + +The 3G Frequency list consists of the set of UTRAN frequencies contained in the GPRS 3G Cell Reselection list or in the 3G Neighbour Cell list, depending on which list is being used by the mobile station. The 3G Frequency list is constructed as specified in 3GPP TS 44.018. + +When the 3G Neighbour cell list is modified (e.g. by a PACKET CELL CHANGE ORDER message or by one or more instances of the PACKET MEASUREMENT ORDER message), the 3G Frequency list shall be updated. + +### 5.6.3.8 Closed Subscriber Group Information + +This applies only to a multi-RAT MS supporting UTRAN and/or E-UTRAN. One or more instances of the SI2quater or the PACKET MEASUREMENT ORDER message may provide the *E-UTRAN CSG Description IE* and/or the *3G CSG Description IE*. An MS supporting cell reselection to UTRAN and/or E-UTRAN shall use this information as described in 3GPP TS 45.008. + +If an MS receives a *CSG\_PSC\_SPLIT IE* and/or a *CSG\_PCI\_SPLIT IE* it shall store this information and shall consider it as being valid for the specified frequencies for a period of up to 24 hours or until a new *CSG\_PSC\_SPLIT IE* and/or a new *CSG\_PCI\_SPLIT IE* is received, whichever occurs first. + +Any valid "CSG PSC Split Information" received from a UTRAN frequency and stored by the mobile station shall take precedence over the information received from the *CSG\_PSC\_SPLIT IE* for that frequency. Any valid "CSG PCI Split Information" received from an E-UTRAN frequency and stored by the mobile station shall take precedence over the information received from the *CSG\_PCI\_SPLIT IE* for that frequency. + +### 5.6.3.9 Reporting of CSG Cells and Hybrid Cells + +A multi-RAT mobile station in packet transfer mode may report a CSG cell or a detected hybrid cell in a PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message (see sub-clause 5.6.1) if all of the following conditions are met: + +- the mobile station supports "UTRA (respectively E-UTRA) CSG Cells Reporting"; +- the CSG Whitelist (see 3GPP TS 23.122) of the mobile station is not empty; +- the *UTRAN CSG Cells Reporting Description IE* (respectively *E-UTRAN CSG Cells Reporting Description IE*) has been received from the network (see subclause 5.6.1); +- the mobile station has determined that it is allowed to access the cell, i.e. the CSG ID and the PLMN ID of the CSG cell matches one of the CSG IDs with their associated PLMN IDs stored in its CSG Whitelist and the PLMN ID of the CSG cell matches the PLMN ID in the RAI received during latest registration or registration update with PS domain or that of an equivalent PLMN; +- the reporting criteria specified in 3GPP TS 45.008 are met. + +Under these conditions, the mobile station may report a E-UTRAN or UTRAN CSG cell or detected hybrid cell by including the *E-UTRAN CSG Measurement Report IE* or the *UTRAN CSG Measurement Report IE* in the PACKET MEASUREMENT REPORT or the PACKET ENHANCED MEASUREMENT REPORT message. + +If one or more of these conditions are not met the multi-RAT mobile station in packet transfer mode may only report a UTRAN or E-UTRAN cell detected as a hybrid cell in a PACKET MEASUREMENT REPORT message or PACKET ENHANCED MEASUREMENT REPORT message using the procedures for non-CSG cells defined in subclause 5.6. + +A multi-RAT mobile station in NC2 mode may send a PACKET CELL CHANGE NOTIFICATION message on PACCH in place of a PACKET MEASUREMENT REPORT message or PACKET ENHANCED MEASUREMENT REPORT message (see sub-clause 5.6.1), indicating a target cell which is a CSG cell or detected hybrid cell whose CSG ID is in the CSG whitelist of the MS if all of the following conditions are met: + +- the CSG Whitelist of the mobile station is not empty; and +- for a UTRAN cell, either the MS does not support "UTRA CSG Cells Reporting" or the *UTRAN CSG Cells Reporting Description IE* has not been received from the network (or both); and +- for an E-UTRAN cell, either the MS does not support "E-UTRA CSG Cells Reporting" or the *E-UTRAN CSG Cells Reporting Description IE* has not been received from the network (or both); and +- the cell reselection criteria for autonomous reselection towards a CSG cell in NC0/NC1 mode (see 3GPP TS 45.008) have been met and; +- the *NC2\_CSG\_PCCN\_permitted* field (see 3GPP TS 44.018) has been received in System Information Type 2quater and is equal to '1'. + +NOTE: The sending of the PACKET CELL CHANGE NOTIFICATION message when these conditions are met is not conditional on the setting of 3G\_CCN\_ACTIVE or E-UTRAN\_CCN\_ACTIVE. + +If these conditions are met and a mobile station sends a PACKET CELL CHANGE NOTIFICATION message, it shall indicate the CSG cell as the target cell in the PACKET CELL CHANGE NOTIFICATION message using the *3G Target Cell Struct* or *E-UTRAN Target Cell Struct* (alternatively, if the mobile station and the network supports extended EARFCNs, the *E-UTRAN Target Cell with extended EARFCN struct*) and shall include the CSG Discriminator bit. The remaining contents of the PACKET CELL CHANGE NOTIFICATION message shall be as specified for the case of entering CCN mode (see sub-clause 8.8.3). The network may respond to the PACKET CELL CHANGE NOTIFICATION with a PACKET CELL CHANGE ORDER message. The mobile station shall not enter CCN mode and shall not perform a cell change unless a PACKET CELL CHANGE ORDER message is received. + +NOTE: The use of PACKET CELL CHANGE NOTIFICATION message to report a CSG cell by a mobile station in packet transfer mode in NC0/NC1 mode (including the case where the MS supports CSG Cells Reporting and the *CSG Cells Reporting Description IE* has been received from the network) is specified in sub-clause 8.8.3. + +The CSG Discriminator shall be incremented by one modulo 2 whenever the mobile station reports a different CSG cell having the same physical layer parameters as the previously reported CSG cell. The initial value of the CSG Discriminator is 0. The mobile station shall use individual sequences of CSG Discriminator for CSG cells with different physical layer parameters. + +When the mobile station leaves NC2 mode or moves to a new cell, the mobile station shall delete all CSG Discriminator information. + +## 5.6.4 Measurement reporting in broadcast/multicast receive mode + +The mobile station in broadcast/multicast receive mode shall report neighbouring cell measurements when polled for an MBMS DOWNLINK ACK/NACK message according to the procedures specified in sub-clause 8.1.4.2. Measurement reporting in broadcast/multicast receive mode shall not affect the procedure for NC measurement reporting defined in sub-clause 5.6.1. + +For reporting neighbouring cells in the MBMS Neighbouring Cell Report struct, the following rules apply: + +- the neighbouring cells shall belong to the six strongest non-serving and allowed (see 3GPP TS 45.008) carriers +- the cells for which cell reselection parameters have been acquired, shall be reported in decreasing order of the corresponding cell re-selection ranking (see 3GPP TS 45.008), i.e. the highest ranked first. +- the neighbouring cells for which cell reselection parameters have not been acquired, shall be reported in decreasing order of the received signal level average (see 3GPP TS 45.008), i.e. the neighbouring cell with highest received signal average first. +- in case there are cells for which cell reselection parameters have and cells for which cell reselection parameters have not been acquired to be included in the MBMS Neighbouring Cell Report struct, the cells shall be reported in alternating order, starting with the highest ranked cell for which cell reselection parameters have been acquired. +- the MBMS Neighbouring Cell Report struct shall include as many cells as possible but shall not exceed 6 cells. + +EXAMPLE: there is space to report 4 neighbouring cells in the MBMS DOWNLINK ACK/NACK message. + +In this case, the neighbouring cells in the MBMS Neighbouring Cell Report struct shall be reported in the following order : + +y(1), n(1), y(2), y(3), cells y(4) and y(5) are not reported, + +where + +y(1) is the highest ranked cell for which cell reselection parameters have been acquired +y(2) is the 2nd highest ranked cell for which cell reselection parameters have been acquired +y(3) is the 3rd highest ranked cell for which cell reselection parameters have been acquired +y(4) is the 4th highest ranked cell for which cell reselection parameters have been acquired +y(5) is the 5th highest ranked cell for which cell reselection parameters have been acquired +n(1) is the highest ranked (and the only one within the 6 strongest) cell for which cell reselection parameters have not been acquired + +If cell re-selection is triggered towards a neighbouring cell (see 3GPP TS 45.008), the mobile station shall indicate this to the network with the RESEL\_CRITERIA\_FULFILLED parameter when reporting measurement results for that cell. In this case, the mobile station shall not include any other measurement results for any other neighbouring cell in the MBMS Neighbouring Cell Report struct. + +When reporting measurement results for a neighbouring cell, the mobile station shall indicate with the RESEL\_PARAMS\_ACQUIRED parameter whether it has acquired the reselection parameters for that cell. The mobile station shall also indicate whether it has received (as described in sub-clause 7.7.3) the MBMS bearer parameters in that cell for the MBMS session acknowledged in the MBMS DOWNLINK ACK/NACK message. If so the mobile station shall indicate the latest corresponding (i.e. for that cell and that session) MBMS\_PTM\_CHANGE\_MARK parameter received. The network may use this information to schedule MBMS NEIGHBOURING CELL INFORMATION messages accordingly. If for a given session the network has received from a mobile station an indication that no MBMS bearer parameters for that session in a neighbouring cell have been received, the network may establish that + +session in that neighbouring cell, if not already established provided that that cell supports MBMS and belongs to the MBMS service area. + +## 5.7 Dual transfer mode enhancements + +The mobile station and the network may support enhanced DTM CS establishment and enhanced DTM CS release procedures, called DTM enhancements. + +By using enhanced DTM CS establishment procedure, an RR connection can be initiated by either the mobile station or the network while the mobile station is in packet transfer mode. The procedure is specified in sub-clause 8.9. + +By using enhanced DTM CS release, the network may delay the release of the RR connection until the mobile station in dual transfer mode has received the required system information, in order to maintain the radio resources (PDCH(s)) after the release of the RR connection while in dual transfer mode, as specified in sub-clause 5.5.1.1b.5. + +The support of the DTM enhancements is optional for the mobile station and the network and is indicated in the *Mobile Station Classmark 3 IE*, the *MS Radio Access Capability IE* and the *GPRS Cell Options IE*. A mobile station supporting the DTM enhancements shall also support the extended RLC/MAC control message segmentation as defined in 9.1.12a. The DTM enhancements shall be used if the mobile station and the network support them. + +## 5.8 + +## DTM Handover + +Mobile station and network support for DTM handover is optional. The mobile station shall indicate its support for DTM handover in the *Mobile Station Classmark 3 IE* and the *MS Radio Access Capabilities IE* (see 3GPP TS 24.008). A mobile station supporting DTM handover shall also support the extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a. The DTM handover procedure consists of the CS handover procedure (see 3GPP TS 44.018) and the PS handover procedure (see sub-clause 8.10) running in parallel with exceptions as outlined in 3GPP TS 48.008. + +## 5.9 + +## Downlink Dual Carrier + +Mobile station and network support for Downlink Dual Carrier is optional. The mobile station shall indicate its support for Downlink Dual Carrier in the *MS Radio Access Capabilities IE* (see 3GPP TS 24.008). A mobile station and a network that support Downlink Dual Carrier shall also support EGPRS TBFs. A mobile station supporting Downlink Dual Carrier shall also support the extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a. + +Downlink Dual Carrier enables downlink TBFs and uplink TBFs to use allocated resources on one or more assigned PDCHs on two different radio frequency channels. Uplink RLC/MAC blocks shall not be scheduled on both carriers of a downlink dual carrier configuration in the same radio block period. Downlink RLC/MAC blocks may be scheduled on both carriers of a downlink dual carrier configuration in the same radio block period. + +If the network initially assigns a mobile station radio resources on only one carrier, it can extend this assignment to a downlink dual carrier configuration by sending a new single carrier assignment to the mobile station including assigned radio resources for the second carrier, without changing the resources already assigned for the initial carrier. Alternatively the network can include radio resources for two carriers in an initial or subsequent assignment message. + +## 5.10 ETWS Primary Notification + +Mobile station support for reception of Earthquake and Tsunami Warning System (ETWS) Primary Notification messages is optional. A mobile station supporting reception of ETWS Primary Notification shall also support the extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a. + +## 5.11 Enhanced Multiplexing for Single TBF + +Mobile station and network support for Enhanced Multiplexing for Single TBF (EMST) is optional. The mobile station shall indicate its support for EMST in the *MS Radio Access Capability* IE (see 3GPP TS 24.008). The mobile station supporting EMST and RLC non-persistent mode shall be able to operate up to three RLC entities on a single TBF concurrently. The mobile station supporting EMST and not supporting RLC non-persistent mode shall be able to operate up to two RLC entities on a single TBF concurrently. A mobile station and a network that support EMST shall also support EGPRS. A network supporting EMST shall also support the delayed release of downlink TBF and extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b). + +EMST enables the allocation and multiplexing of one or more RLC entities on a single TBF. In the uplink, each RLC entity allocated on the TBF shall operate according to radio parameters (radio priority and peak throughput) of the PFC currently being served, however different RLC entities allocated on the same uplink TBF may operate according to different radio parameters. The RLC entities allocated on the TBF shall operate in different RLC modes. The TBF shall be maintained when packet transfer switches between RLC entities using different RLC modes and/or radio priorities. The network shall not assign more than one RLC entity operating in a give RLC mode to a single TBF. + +NOTE: It is for further study, whether a specific PFC multiplexing shall apply if EMST is used. + +Each RLC entity allocated on a TBF using EMST shall be assigned a unique TFI as specified in sub-clause 5.2.2. + +An uplink TBF using EMST shall be assigned a unique USF as specified in sub-clause 5.2.3. The use of USF for an uplink TBF using EMST is the same as specified for an uplink TBF not using EMST. + +On an uplink TBF using EMST, the mobile station shall use the same rules for multiplexing LLC PDUs as specified for a single RLC entity case, i.e. use peak throughput and radio priority to decide how data from different PFCs are multiplexed. + +## 5.12 Enhanced Multiplexing for a Single RLC Entity + +Mobile station and network support for Enhanced Multiplexing for a Single RLC Entity (EMSR) is optional. The mobile station shall indicate its support for EMSR in the *MS Radio Access Capability* IE (see 3GPP TS 24.008). A network that supports EMSR shall also support the delayed release of a downlink TBF and extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b). A mobile station that supports EMSR shall support extended uplink TBF mode. + +EMSR is enabled for a given RLC entity when the network allocates multiple PFCs with at least two of them having unique TFI values within the context of that RLC entity. EMSR is disabled for a given RLC entity if that RLC entity is no longer allocated multiple PFCs with at least two of them having unique TFI values. + +If EMSR is enabled for a given RLC entity then uplink resource reallocation/downlink resource reassignment is not performed whenever RLC data block transmission priority decisions made in the MS or in the BSS result in switching between PFCs assigned to the same RLC entity but having different TFI values. If EMSR is enabled and a new upper layer PDU becomes available but is not associated with a PFC for which the MS has already sent a PACKET RESOURCE REQUEST message (and received a corresponding assignment message), then the MS shall proceed as described in sub-clause 8.1.1.1.2 regarding how the transmission of the new LLC PDU is to be managed. Similarly, if EMSR is enabled and a new upper layer PDU becomes available but is not associated with a PFC for which the MS has already received a downlink assignment message then the BSS shall perform downlink resource reassignment and the MS shall proceed as described in sub-clause 8.1.2.4. An uplink TBF using EMSR shall be assigned a unique USF as specified in sub-clause 5.2.3. + +If EMSR is enabled for a given RLC entity, the determination of the relative transmission priority of upper layer PDUs is implementation specific. The transmission of upper layer PDUs may be suspended or resumed depending on their relative priorities as specified in sub-clauses 9.1.11 and 9.1.12. + +If EMSR is enabled for a given RLC entity, the network may send the mobile station an assignment message (e.g. PACKET TIMESLOT RECONFIGURE, PACKET UPLINK ASSIGNMENT or PACKET DOWNLINK ASSIGNMENT message) that excludes a subset of the PFCs previously allocated to that RLC entity without releasing the RLC entity. In this case: + +- Upon reception of the assignment message, the mobile station may discard all upper layer PDUs corresponding to an excluded PFC for which transmission has not yet started. + +- Upon determining that there are no outstanding upper layer PDUs corresponding to an excluded PFC, the mobile station shall consider that PFC as no longer allocated to the corresponding RLC entity. The mobile station shall also consider the TFI value associated with such a PFC as no longer allocated to the corresponding RLC entity if there are no remaining PFCs allocated to that RLC entity still associated with that TFI value. +- If the mobile station has more upper layer PDUs to send for an excluded PFC then it shall send a PACKET RESOURCE REQUEST message requesting resources for that PFC as described in this sub-clause. + +## 5.13 + +### Downlink Multi Carrier + +Mobile station and network support for Downlink Multi Carrier is optional. The mobile station shall indicate its support for DLMC configuration in the *MS Radio Access Capability* IE (see 3GPP TS 24.008). A mobile station and a network that support DLMC configuration shall support: + +- the assignment of only one EGPRS TBF on the downlink where multiple PDCHs may be assigned on two or more different radio frequency channels. +- extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a. +- the optional assignment of one EGPRS TBF on the uplink. If assigned, one or more PDCHs may be assigned on one or more uplink radio frequency channels where each uplink radio frequency channel corresponds to an assigned downlink radio frequency channel. + +A mobile station that supports DLMC configuration shall, within the *MS Radio Access Capability* IE (see 3GPP TS 24.008), indicate the maximum number of downlink carriers it supports, the maximum number of downlink timeslots it supports, the maximum bandwidth it supports, and whether or not it support non-contiguous intra-band reception and/or inter-band reception. + +A mobile station that supports DLMC configuration may be assigned one or more UFPS (see 3GPP TS 45.008 [15]) where the assigned UFPS(s) and their associated carriers are numbered as described in sub-clause 8.1.1.1.3. For the case where a UFPS is defined by a mobile allocation (see sub-clause 12.10a) a mobile station in DLMC configuration will perform carrier selection to determine the set of downlink carriers it can receive during any given radio block period as described in 3GPP TS 45.002 [13]. + +In DLMC configuration RLC/MAC blocks shall not be scheduled on multiple uplink carriers in the same radio block period whereas RLC/MAC blocks may be scheduled on one or more downlink carriers in the same radio block period. + +If the maximum number of downlink timeslots a mobile station supports in a DLMC configuration is greater than 20 then it shall, in addition to supporting the EGPRS sequence number space (SNS) and window size, support an extended SNS of 8192, an extended window size (see sub-clause 9.0, 10.4.12 and 9.19), the assignment of eTFI values (see sub-clause 10.0a.2 and 10.0a.3) and CS-3 coding of EGPRS PACKET DOWNLINK ACK/NACK DLMC messages. The sequence number space to be used and the assigned eTFI values are indicated in the assignment message (see sub-clause 11.2.7). + +In DLMC configuration where eTFI values are assigned, the mobile station uses eTFI in combination with TFI to determine if the message (PACCH, PAN or a RLC data block) is addressed to it. See sub-clause 8.1.1.1.1, 8.1.1.2.2 and 8.1.2.1 for the use of eTFI. + +A mobile station in DLMC configuration where the continuous timing advance procedure is used shall fall back to single carrier configuration for PTCCH reception during each PTCCH frame occurring on the corresponding radio frequency channel (see sub-clause 7.1.2.5). In addition, the mobile station shall fall back to single carrier configuration for radio block reception according to a regular pre-determined interval (see 3GPP TS 45.002 [13]) using the radio frequency channel of its assigned PTCCH or using the radio frequency channel of the lowest numbered carrier (see sub-clause 8.1.1.1.3) if it has not been assigned a PTCCH. When inter-band reception is used in DLMC configuration (see 3GPP TS 45.005 and 3GPP TS 45.002), fall back to single carrier configuration only applies to the frequency band where the PTCCH is assigned or where the lowest numbered carrier is assigned (if a PTCCH has not been assigned). + +If a mobile station is using the continuous timing advance procedure, it shall, upon receiving an assignment message that causes it to enter DLMC configuration, continue to use the current PTCCH information for as long as the corresponding downlink carrier remains assigned unless one of the following occurs: + +- the current assignment message provides it with new PTCCH information. +- a subsequent assignment message or a Packet Power Control/Timing Advance message provides it with new PTCCH information. +- a subsequent assignment message results in the mobile station no longer being in a DLMC configuration (but still in packet transfer mode) in which case it shall consider the PTCCH allocation to be on the remaining carrier. + +## 6 Paging procedures + +For a mobile station in packet idle mode, the network may use the paging procedures to initiate the establishment of an RR connection, to trigger a cell update from the mobile station prior to a downlink packet transfer, or to send MBMS notification. A number of mobile stations can be paged for either downlink packet transfer or RR connection establishment in the same paging message. Mobile terminated RR connection establishment for GSM services (see 3GPP TS 23.060 [19]) shall not be used in packet idle mode when a mobile station has enabled PEO. + +For a mobile station in packet transfer mode, the network may use the paging procedures to initiate the establishment of an RR connection. A number of mobile stations can be paged for RR connection establishment in the same paging message. After sending the mobile station a PS HANDOVER COMMAND message the network shall not use paging procedures to initiate the establishment of an RR connection for that mobile station until the PS handover procedure has been completed (see sub-clause 8.10). Mobile terminated RR connection establishment for GSM services (see 3GPP TS 23.060 [19]) shall not be used in packet transfer mode when a mobile station has enabled PEO. + +Paging procedures for RR connection establishment are described in sub-clause 6.1. Paging procedures for downlink packet transfer are described in sub-clause 6.2. + +### 6.1 Paging procedure for RR connection establishment + +The network may initiate the establishment of an RR connection by the paging procedure for RR connection establishment. + +The network initiates the paging procedure for RR connection establishment by sending a paging request message on the appropriate paging subchannel on CCCH or PCCCH, addressing the mobile station and indicating RR connection establishment. + +The paging subchannels on CCCH and PCCCH are specified in 3GPP TS 45.002 and 3GPP TS 43.013. The paging request message for RR connection establishment is sent on the PCCCH if the mobile station is GPRS attached, PCCCH is present in the cell and the network operates in network mode of operation I (see 3GPP TS 23.060). Otherwise, the paging request message is sent on CCCH. + +The network may also page the mobile station for RR connection establishment by sending a paging request message on PACCH if the mobile station is in packet transfer mode. + +A mobile station in packet transfer mode is not required to decode the paging subchannels, on neither CCCH nor PCCCH, in the following two cases: + +- the mobile station is not capable to handle an RR connection and a TBF simultaneously (GPRS class B mode of operation); or +- the mobile station requires that the BSS co-ordinates the allocation of radio resources for an RR connection and one or more simultaneous TBFs (GPRS class A mode of operation by means of DTM). + +#### 6.1.1 Paging initiation using paging subchannel on CCCH + +The paging initiation procedure and the paging request messages used on CCCH are specified in 3GPP TS 44.018. + +#### 6.1.2 Paging initiation using paging subchannel on PCCCH + +The network initiates the paging procedure by sending a PACKET PAGING REQUEST message on an appropriate paging subchannel on PCCCH, considering the DRX parameters valid for each targeted mobile station. + +For each mobile station, that is paged for RR connection establishment, a channel needed field is included in the PACKET PAGING REQUEST message, see sub-clause 11.2.10. The channel needed field defines how the mobile stations shall use the establishment cause field in the CHANNEL REQUEST message, as specified in 3GPP TS 44.018. + +### 6.1.3 Paging initiation using PACCH + +Paging initiation using PACCH applies when sending a paging request message to a mobile station that is GPRS attached, when the mobile station is in packet transfer mode or in broadcast/multicast receive mode, if so indicated for that mobile by the network, and the network is able to co-ordinate the paging request with the radio resources allocated for the mobile station (or MBMS session) on a PDCH. + +This kind of paging co-ordination shall be provided in network mode of operation I (see 3GPP TS 23.060). A mobile station in packet transfer mode in a cell indicating support of network mode of operation I in the NMORelated fields broadcast on BCCH or PBCCH shall expect the paging messages to be received on the PACCH. + +This kind of paging co-ordination shall be provided for mobile stations capable of DTM if the network supports DTM. A mobile station capable of DTM in packet transfer mode in a cell indicating support of DTM procedures in the *DTM\_SUPPORT* field broadcast on BCCH or PBCCH shall expect the paging messages to be received on the PACCH. + +This kind of paging co-ordination may be provided also in network mode of operation II or III regardless of the DTM capability of the cell and of the mobile station and shall be indicated in that case by setting the *BSS\_PAGING\_COORDINATION* field to "The cell supports Circuit-Switched paging coordination" on BCCH or PBCCH. If such indication is received, a mobile station in packet transfer mode shall expect the paging messages to be received on the PACCH. + +A mobile station in broadcast/multicast receive mode shall expect the paging messages to be received on the PACCH of an MBMS radio bearer if the network has indicated so with the *MBMS In-band Signalling Indicator* field in the MBMS ASSIGNMENT and/or MBMS NEIGHBOURING CELL INFORMATION messages, and if the mobile station has an MS\_ID on that MBMS radio bearer. + +The network shall not send paging messages on the PACCH to a mobile station whose MS\_ID has been released because the mobile station has not responded when being polled (i.e. T3195 has started for that MS\_ID). + +If a mobile station is receiving multiple MBMS radio bearers and the mobile station has an MS\_ID on at least one of the MBMS radio bearers where the network has indicated that system information for the serving cell and paging messages are sent on the PACCH/D then the mobile station shall not monitor its paging group on the (P)CCCH in parallel to the MBMS radio bearers. The network shall send the PACKET PAGING REQUEST message to the mobile station on the appropriate PACCH. The message includes the mobile station identification and the channel needed field which defines how the mobile station shall use the establishment cause field in the CHANNEL REQUEST message, as specified in 3GPP TS 44.018. + +### 6.1.4 Paging response + +Upon receipt of a Paging Request or Packet Paging Request message, for the purpose of triggering an RR connection establishment, a mobile station operating in GPRS class B mode of operation and in packet transfer mode shall either ignore or respond to the paging request according to 3GPP TS 22.060. + +When the mobile station responds to a paging request for RR connection establishment, it shall follow the paging response procedures as specified in 3GPP TS 44.018. For that purpose, a mobile station in packet transfer mode or a mobile station that has initiated a packet access procedure may abort all ongoing TBFs or the packet access procedure in the following two cases: + +- the mobile station is not capable to handle an RR connection and a TBF simultaneously (GPRS class B mode of operation or a mobile station in DLMC configuration); or +- the mobile station requires that the BSS co-ordinates the allocation of radio resources for an RR connection and one or more simultaneous TBFs (GPRS class A mode of operation by means of DTM). + +## 6.2 Paging procedure for downlink packet transfer + +The network may initiate the paging procedure for downlink packet transfer in order to obtain the mobile station cell location required for the downlink packet transfer. The procedure is triggered by a page request from the GMM sublayer on the network side, see 3GPP TS 24.007 and 3GPP TS 44.018. The procedure is initiated by sending a paging request message on the appropriate paging subchannel on CCCH, EC-CCCH or PCCCH. The paging subchannels on CCCH, EC-CCCH and PCCCH are specified in 3GPP TS 45.002 and 3GPP TS 43.013. + +The paging request message is sent on PCCCH, if PCCCH is present in the cell. Otherwise, the paging request message is sent on CCCH. A paging request message to a mobile station that has enabled EC operation is sent on EC-CCCH. + +A mobile station that indicates DTM support to the network is not required to decode the paging subchannels, on neither CCCH nor PCCCH, while it is in dedicated mode. If the cell location for a mobile station that has indicated DTM support is required while the mobile station is in dedicated mode, the network may use the packet notification procedure defined in 3GPP TS 44.018. + +### 6.2.1 Paging procedure using paging subchannel on CCCH + +The packet paging procedure and the paging request messages used on CCCH are specified in 3GPP TS 44.018. + +### 6.2.2 Paging using paging subchannel on PCCCH + +The network initiates the paging procedure by sending a PACKET PAGING REQUEST message on an appropriate paging subchannel on PCCCH, considering the DRX parameters valid for each targeted mobile station. + +### 6.2.3 Paging response + +On receipt of a PACKET PAGING REQUEST message, the RR sublayer of addressed mobile station indicates the receipt the paging request to the GMM sublayer (see 3GPP TS 24.007 and 3GPP TS 44.018). + +NOTE: The mobile station performs a pageresponse by sending an upper layer PDU to the network as defined in 3GPP TS 44.018 and 3GPP TS 44.064. The transfer of an upper layer PDU may serve as a cell update. + +### 6.2.4 Paging procedure using paging subchannel on EC-CCCH + +The packet paging procedure and the paging request messages used on EC-CCCH are specified in 3GPP TS 44.018. + +## 6.3 Paging Procedures for MBMS Notification + +### 6.3.1 Notification to mobile station in packet idle mode + +#### 6.3.1.1 General + +The paging procedure for MBMS notification of an MBMS session is initiated by the reception of an MBMS-SESSION-START-REQUEST PDU or of an MBMS-SESSION-UPDATE-REQUEST PDU from the SGSN for this session, see 3GPP TS 48.018. The MBMS notification may be repeated during the session. + +The network initiates the paging procedure for MBMS notification on PCCCH (sub-clause 6.3.1.3) if PCCCH is present in the cell, otherwise on CCCH (sub-clause 6.3.1.2). The paging procedure for MBMS notification is also initiated on PACCH when the mobile station is in broadcast/multicast receive mode, if so indicated for that mobile station by the network (sub-clause 6.3.1.3a). + +The paging procedure for MBMS notification consists of the following steps: + +optionally, the pre-notification of the MBMS session; and + +the notification of the MBMS session. + +A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode if a paging procedure for a new MBMS session is not completed for any reason. + +### 6.3.1.2 Paging procedure for MBMS notification using paging subchannel on CCCH + +The paging procedure for MBMS notification and the paging request messages used on CCCH are specified in 3GPP TS 44.018. + +### 6.3.1.3 Paging procedure for MBMS notification using paging subchannel on PCCCH + +#### 6.3.1.3.1 General + +The network initiates the paging procedure for MBMS notification of an MBMS session by sending a PACKET PAGING REQUEST message including for that session either the MBMS pre-notification (see sub-clause 6.3.1.3.2) or MBMS notification (see sub-clause 6.3.1.3.3) on one or more paging subchannels on PCCCH. The PACKET PAGING REQUEST message may also contain other MBMS (pre)notification(s) and/or pages as described in sub-clauses 6.1.2 and 6.2.2. The following requirements apply: + +- If in the PACKET PAGING REQUEST message the mobile station is at the same time (pre)notified (see sub-clauses 6.3.1.3.2 and 6.3.1.3.3) and paged, the mobile station shall discard all (pre)notification(s) in that message and proceed as described in sub-clause 6.1 or 6.2, whichever applies. +- If in the PACKET PAGING REQUEST message the mobile station is at the same time pre-notified (see sub-clause 6.3.1.3.2) and notified (see sub-clause 6.3.1.3.3), the mobile station shall discard all pre-notifications in that message and proceed as described in sub-clause 6.3.1.3.3. + +#### 6.3.1.3.2 MBMS pre-notification + +In order to pre-notify an MBMS session, the network shall send a PACKET PAGING REQUEST message by including for that session only the TMGI and, if available, the MBMS Session Identity of that session as contained in the MBMS-SESSION-START-REQUEST PDU or in the MBMS-SESSION-UPDATE-REQUEST PDU. + +Upon reception of a PACKET PAGING REQUEST message including for an MBMS session only the TMGI and, if available, the MBMS Session Identity of that session, and if the mobile station requires reception of that session, the mobile station shall consider that session as being pre-notified (i.e. the mobile station is pre-notified). If the mobile station determines several pre-notified sessions in this message, the mobile station shall discard all pre-notifications but the pre-notification for the highest priority session. The mobile station in packet idle mode or MAC-Idle state shall then enter non-DRX mode, start timer T3220 and proceed as described in sub-clause 6.3.1.3.3. + +NOTE: In case all pre-notified sessions have the same priority, the selection of the highest priority session is implementation-dependent. + +While timer T3220 is running, the mobile station shall stop timer T3220 and discard the pre-notification if: + +- Any other procedure on PCCCH not related to MBMS is triggered. The mobile station shall then proceed as per that procedure. +- A notification is received for a higher priority session. The mobile station shall then proceed as described in sub-clause 6.3.1.3.3. + +If while timer T3220 is running the mobile station receives a pre-notification for a higher priority session, the mobile station shall discard the pre-notification for the lower priority session, remain in non-DRX mode, restart timer T3220 and proceed as described in sub-clause 6.3.1.3.3. + +Upon expiry of timer T3220, the mobile station in packet idle mode or MAC-Idle state shall return to DRX mode and discard the pre-notification. The mobile station in broadcast/multicast receive mode shall discard the pre-notification and remain in broadcast/multicast receive mode. + +A mobile station in broadcast/multicast receive mode that is receiving an MBMS session shall ignore repeated pre-notifications of that session. + +### 6.3.1.3.3 MBMS notification + +In order to notify an MBMS session, the network shall send a PACKET PAGING REQUEST message by including for that session: + +- the TMGI and, if available, the MBMS Session Identity of that session; +- an indication whether counting shall be performed or not; +- optionally the MBMS p-t-m channel description allocated to that session and the estimated duration of the MBMS session or, if the MBMS session is ongoing, the estimated remaining duration of the MBMS session; +- optionally the MPRACH description. + +NOTE 1: If the *MBMS Session Repetition Number* IE is included in the MBMS-SESSION-START-REQUEST PDU or in the MBMS-SESSION-UPDATE-REQUEST PDU (see 3GPP TS 48.018), the value part of this IE may be used by the network for e.g. deciding whether or not to perform the counting procedure or, in conjunction with the values of *Allocation/Retention Priority* IE (see 3GPP TS 48.018), whether or not to establish an MBMS radio bearer for the session. + +Upon reception of a PACKET PAGING REQUEST message including the notification of an MBMS session and if the mobile station requires reception of this session, the mobile station shall consider that session as being notified (i.e. the mobile station is notified). If the mobile station determines several notified sessions in this message, the mobile station shall act upon the notification for the highest priority session. The mobile station shall then stop timer T3220, if running, and proceed as described in sub-clause 6.3.1.4. + +NOTE 2: In case all notified sessions have the same priority, the selection of the highest priority session is implementation-dependent. + +NOTE 3: Depending on its capabilities, the MS may act upon the notification for lower priority MBMS sessions provided it does not affect any of the following procedures for the highest priority MBMS session: response to MBMS notification (see sub-clause 6.3.1.4), establishment of MBMS bearer upon receipt of MBMS ASSIGNMENT message (see sub-clause 7.7.2.2), MBMS packet access procedure (see sub-clause 7.7.1). + +A mobile station in broadcast/multicast receive mode that is receiving an MBMS session shall ignore repeated notifications of that session. + +### 6.3.1.3a Paging procedure for MBMS notification using PACCH + +A mobile station in broadcast/multicast receive mode shall expect the paging messages to be received on the PACCH of an MBMS radio bearer if the network has indicated so with the *MBMS In-band Signalling Indicator* field in the MBMS ASSIGNMENT and/or MBMS NEIGHBOURING CELL INFORMATION messages, and if the mobile station has an MS\_ID on that MBMS radio bearer. + +Under the above circumstances, the network initiates the paging procedure for MBMS notification of an MBMS session not only on PCCCH (see sub-clause 6.3.1.3) if PCCCH is present in the cell, otherwise on CCCH (see sub-clause 6.3.1.2), but also by sending a PACKET PAGING REQUEST message including for that session either the MBMS pre-notification (see sub-clause 6.3.1.3.2) or MBMS notification (see sub-clause 6.3.1.3.3) on the appropriate PACCH. The PACKET PAGING REQUEST message may also contain other MBMS (pre-)notification(s) and/or pages as described in sub-clauses 6.1.2 and 6.2.2 (see sub-clause 6.3.1.3.1). + +The network shall not send paging messages on the PACCH to a mobile station whose MS\_ID has been released because the mobile station has not responded when being polled (i.e. T3195 has started for that MS\_ID). + +Upon reception of MBMS notification on PACCH, the mobile station in broadcast/multicast receive mode shall act according to sub-clause 8.1.5.2. + +If the mobile station responds to the MBMS notification: + +- it shall act as described in sub-clause 6.3.1.4 if PCCCH is present in the cell; +- otherwise it shall act as described in 3GPP TS 44.018 (sub-clause 3.5.1.3.4). + +### 6.3.1.4 Response to MBMS Notification + +If the MBMS notification indicates that no counting shall be performed and contains no MBMS p-t-m channel description, the mobile station shall remain in or enter non-DRX mode and start timer T3214. Upon expiry of timer T3214, a mobile station in packet idle mode or MAC-Idle state (respectively broadcast-multicast receive mode) shall enter DRX mode (respectively remain in broadcast-multicast receive mode) and discard the corresponding notification. Upon reception of an MBMS ASSIGNMENT message for that session, the mobile station shall stop timer T3214 and shall proceed as described in sub-clause 7.7.2.2. + +While timer T3214 is running, the mobile station shall stop timer T3214 if: + +- Any other procedure on PCCCH not related to MBMS is triggered. The mobile station shall then proceed as per that procedure; +- A notification is received for a higher priority session. The mobile station shall then proceed as per that notification. Depending on its capabilities, the MS may act upon the notification for the lower priority MBMS session provided it does not affect any of the following procedures for the higher priority MBMS session: response to MBMS notification (see present sub-clause), establishment of MBMS bearer upon receipt of MBMS ASSIGNMENT (see sub-clause 7.7.2.2), MBMS packet access procedure (see sub-clause 7.7.1). + +If the MBMS notification indicates that counting shall be performed the mobile station shall perform an MBMS packet access procedure, as described in sub-clause 7.7.1. + +If the MBMS notification includes an MBMS p-t-m channel description the mobile station shall set and start the session duration timer for this MBMS session with a value equal to the Estimated Session Duration (included in the MBMS Session Parameters List) and shall use information received on the PBCCH to decode the channel descriptions contained in the assignment. If frequency hopping is applied, the mobile station shall use the last CA (Cell Allocation) received on PBCCH to decode the Mobile Allocation. Alternatively, the network may provide a Mobile Allocation in the assignment. If an MBMS Radio Bearer Starting Time is indicated, the mobile station shall monitor PCCCH until the point in time denoted by the MBMS Radio Bearer Starting Time. The mobile station shall then switch to the assigned PDCHs and start timer T3190. If the MBMS Radio Bearer Starting Time has already elapsed or is not present, the mobile station shall switch to the assigned PDCHs and start timer T3190. The timer T3190 is restarted when receiving the first valid RLC data block for that session. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. The mobile station is not allowed to send normal bursts on the uplink unless it has a valid timing advance, and is assigned an MS\_ID for that session. If the mobile station receives more than one MBMS notification including an MBMS p-t-m channel description for that same session while it monitors PCCCH, it shall act upon the most recently received assignment for that session and shall ignore the previous assignment. + +On expiry of timer T3190, the mobile station shall abort the procedure and return to packet idle mode or MAC-Idle state. The mobile station in broadcast/multicast receive mode shall abort the procedure and remain in broadcast/multicast receive mode. + +## 6.3.2 Notification to mobile station in packet transfer mode or in dual transfer mode + +### 6.3.2.1 General + +MBMS notification initiation using PACCH applies when sending an MBMS notification to a mobile station or a group of mobile stations that is/are in packet transfer mode or in dual transfer mode. + +### 6.3.2.2 MBMS Notification using the PACCH + +The network may send the PACKET MBMS ANNOUNCEMENT message on any PDCH. + +Upon receipt of a PACKET MBMS ANNOUNCEMENT message containing a TMGI and optionally an MBMS Session Identity corresponding to an MBMS session the mobile station is required to receive, the mobile station shall pass an indication including the TMGI, and when available the MBMS Session Identity, to the upper layers. If the Restriction Timer is included in the received PACKET MBMS ANNOUNCEMENT message, the mobile station shall set and start an instance of the T3222 to the value indicated in the Restriction Timer field, otherwise if the Estimated Session Duration is included in the received PACKET MBMS ANNOUNCEMENT message the mobile station shall set and start both an instance of the T3222 and the session duration timer for this MBMS session with a value equal to + +the Estimated Session Duration. The mobile station shall store the MBMS specific information contained in the PACKET MBMS ANNOUNCEMENT message. + +If T3222 expires the mobile station shall discard the stored MBMS information associated with this instance of T3222. + +### 6.3.2.3 Response to MBMS Notification received on PACCH + +If the mobile station enters packet idle mode and completes the Transfer non-DRX mode period before the expiry of T3222 or where no instance of T3222 was set and the PACKET MBMS ANNOUNCEMENT message did not include the MBMS p-t-m channel description, the mobile station shall stop T3222, if started, and initiates the MBMS Packet Access Procedure on a PCCCH (sub-clause 7.7.1.2) or, if a packet control channel does not exist, on a CCCH (sub-clause 7.7.1.3) or, if the PACKET MBMS ANNOUNCEMENT message contained uplink resource description for an MPRACH, on that MPRACH (sub-clause 7.7.1.4). + +Any MPRACH description or MBMS p-t-m channel description stored from a previously received PACKET MBMS ANNOUNCEMENT message shall be deleted after the mobile station completes cell reselection or after a handover procedure is completed. + +If the mobile station enters packet idle mode before the expiry of T3222 and the PACKET MBMS ANNOUNCEMENT message included the MBMS p-t-m channel description, the mobile station shall stop T3222 and shall start listening to downlink RLC blocks identified by the assigned TFI on the defined PDCHs either at the point in time denoted by the MBMS Radio Bearer Starting Time, if present and not already elapsed, or immediately otherwise. + +The mobile station shall follow the procedures described in sub-clause 6.3.1.4. + +## 6.4 Paging Procedure for ETWS Primary Notification delivery + +### 6.4.1 General + +The network may initiate the paging procedure for delivery of an ETWS Primary Notification message (see 3GPP TS 23.041) on PCCCH (sub-clause 6.4.3) if PCCCH is present in the cell, otherwise on CCCH (sub-clause 6.4.2). + +### 6.4.2 ETWS Primary Notification delivery using paging subchannel on CCCH + +The paging procedure for ETWS Primary Notification delivery and the paging request messages used on CCCH are specified in 3GPP TS 44.018. + +### 6.4.3 ETWS Primary Notification delivery using paging subchannel on PCCCH + +The network initiates the paging procedure for delivery of an ETWS Primary Notification message (see 3GPP TS 23.041) by broadcasting the PACKET PAGING REQUEST message on all paging subchannels on PCCCH with the ETWS Primary Notification field present. These paging messages are sent continuously during the ETWS warning period. + +Each paging message carries a segment of the actual ETWS Primary Notification message, i.e. segmentation is applicable if an ETWS Primary Notification message is too large to fit into a single PACKET PAGING REQUEST message. In order to allow a mobile station to receive the segments in any order, the size of a specific segment (retransmitted during the ETWS warning period) shall not be altered. Segments belonging to the same ETWS Primary Notification message shall be given the same Primary Notification Identifier (PNI) value. + +### 6.4.4 Reception of ETWS Primary Notification message + +Upon receipt of a PACKET PAGING REQUEST message carrying a segment of an ETWS Primary Notification message, the mobile station shall leave DRX mode, start timer T3232, start reading all paging groups corresponding to its PCCCH\_GROUP and attempt to acquire all segments of the ETWS Primary Notification message, having the same Primary Notification Identifier (PNI) value, before delivering the assembled message to the upper layers. + +While attempting to acquire the ETWS Primary Notification message a mobile station shall continue to follow packet idle mode and connection establishment procedures. Upon initiating cell reselection or connection establishment procedures (RR connection establishment or TBF establishment) while attempting to acquire an ETWS Primary + +Notification message, a mobile station shall discard any partially received ETWS Primary Notification message and stop timer T3232. The mobile station shall not attempt to acquire an ETWS Primary Notification message while performing a connection establishment procedure or while performing cell reselection. + +If the mobile station detects a change in the PNI value prior to acquiring a complete ETWS Primary Notification message, it shall abort the current message, restart timer T3232 and attempt to acquire the new message. + +When the mobile station successfully acquires a complete ETWS Primary Notification message it shall stop timer T3232 and enter DRX mode. If timer T3232 expires the mobile station shall abort the current message and enter DRX mode. + +--- + +## 7 Medium Access Control (MAC) procedures on PCCCH + +### 7.0 General + +The establishment of a Temporary Block Flow (TBF) can be initiated by either the mobile station or the network. + +The request for establishment of a TBF on PCCCH, if allocated in the cell, is described in this sub-clause. If no PCCCH is allocated in the cell, the establishment of a TBF occurs on CCCH as described in 3GPP TS 44.018. The establishment of an EC TBF, for a mobile station that has enabled EC operation, occurs on the EC-CCCH or on the CCCH as described in sub-clause 7a and in 3GPP TS 44.018. + +For mobile stations in packet idle mode on PCCCH, measurement reports messages are sent on temporary fixed allocations without the establishment of an uplink TBF (see sub-clause 7.3). + +### 7.0a Support of multiple TBF procedures + +If the mobile station supports multiple TBF procedures, the mobile station shall indicate its support in the Multiple TBF Capability field in the *MS Radio Access Capability 2* IE. If the network supports multiple TBF procedures, the network shall indicate its support in the Multiple TBF Capability field in the *GPRS Cell Options* IE. + +If both the network and the mobile station support multiple TBF procedures, and if more than one request is received from upper layers to transfer upper layer PDUs for more than one PFC before the packet access procedure can be initiated by the mobile station, then the mobile station may initiate a packet access procedure requesting multiple TBFs. + +During multiple TBF procedures in sub-clause 7: + +- The mobile station shall support the PACKET RESOURCE REQUEST message to request a single uplink TBF; +- The mobile station may send the PACKET RESOURCE REQUEST message to request multiple uplink TBFs in the second phase of a two-phase access; +- The network shall support the PACKET UPLINK ASSIGNMENT message to assign a single uplink TBF; +- The network may send the MULTIPLE TBF UPLINK ASSIGNMENT message to assign one or more uplink TBFs to a mobile station that requested multiple TBFs in the PACKET RESOURCE REQUEST message. In this sub-clause this message shall only be sent in response to a multiple uplink resource request in the second part of a two-phase access. + +### 7.0b (void) + +## 7.1 TBF establishment initiated by the mobile station on PCCCH + +The purpose of the packet access procedure is to establish a TBF to support the transfer of upper-layer PDUs in the direction from the mobile station to the network. Packet access shall be done on PCCCH, as defined in this sub-clause, if a PCCCH exists. Otherwise, packet access shall be done on CCCH, as defined in 3GPP TS 44.018. The packet access can be done in either one phase (sub-clause 7.1.2) or in two phases (sub-clauses 7.1.2 and 7.1.3). + +TBF establishment can also be done on PACCH if a TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station is already established (see sub-clause 8.1.2.5). TBF establishment can also be done on + +PACCH if the mobile station is releasing a TBF for transfer of upper-layer PDUs in the direction from the mobile station to the network and TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station is not established (see sub-clause 9.3.2.4 and sub-clause 9.3.3.3). + +If the mobile station is in dedicated mode and both the network and the mobile station support DTM, the establishment of a TBF shall be performed by the DTM assignment procedures on the main DCCH, as defined in 3GPP TS 44.018. + +The packet access procedure is initiated by the mobile station. Initiation is triggered by a request from upper layers to transfer an upper-layer PDU. The request from upper layers specifies throughput, RLC mode, an optional PFI, and a Radio Priority to be associated with the packet transfer or indicates that the packet to be transferred contains signalling. If both the network and the mobile station support the extended uplink TBF mode, the request from upper layers may also specify that the upper-layer PDU is meant to pre-allocate an uplink TBF (early TBF establishment). In this case, the mobile station shall use the two phase access procedure, setting the EARLY\_TBF\_ESTABLISHMENT field in the PACKET RESOURCE REQUEST message to indicate pre-allocation is required (as described in sub-clause 7.1.3). + +A mobile station indicates its support of RLC non-persistent mode in the *RLC non-persistent mode capability* bit of the MS Radio Access Capability information element (see 3GPP TS 24.008). + +A packet access procedure requesting multiple TBFs may be initiated by the mobile station if multiple TBF procedures are supported in the network and the mobile station (see sub-clause 7.0). Initiation is triggered when the mobile station receives more than one request from upper layers to transfer upper-layer PDUs before the packet access procedure can be initiated. Each request from upper layers specifies a PFI, RLC mode, Radio Priority and optionally an LLC mode to be associated with the packet transfer or indicates that the packet to be transferred contains signalling. + +Upon such a request: + +- if access to the network is allowed (sub-clause 7.1.1), the mobile station shall initiate the packet access procedure as defined in sub-clause 7.1.2.1; +- otherwise, the RR sublayer in the mobile station shall reject the request. + +If the request from upper layers indicates signalling, the highest Radio Priority shall be used at determination if access to the network is allowed, and the acknowledged RLC mode shall be requested. + +If both the mobile station and the BSS support multiple TBF procedures, or if the mobile station supports RLC non-persistent mode, the BSS may order its preferred RLC mode when establishing uplink TBF(s), independently of the RLC mode requested by the mobile station. In particular, if the mobile station supports RLC non-persistent mode the network may allocate an EGPRS TBF that uses this RLC mode. + +## 7.1.1 Permission to access the network + +The network broadcasts on PBCCH and PCCH the list of authorised access classes and authorised special access classes in the ACC\_CONTR\_CLASS parameter. + +Access to the network is allowed if the mobile station is a member of at least one authorised access class or special access class as defined in 3GPP TS 22.011. + +## 7.1.2 Initiation of a TBF establishment + +### 7.1.2.1 Initiation of the packet access procedure + +The mobile station shall initiate the packet access procedure by scheduling the sending of PACKET CHANNEL REQUEST messages on the PRACH corresponding to its PCCH\_GROUP and simultaneously leaving the packet idle mode. The mobile station shall use the last access parameters received on PBCCH. At sending of the first PACKET CHANNEL REQUEST message, the mobile station shall store the value for the Retry (R) bit to be transmitted in all the subsequent MAC headers as 'MS sent channel request message once'. If a second PACKET CHANNEL REQUEST message is sent, the mobile station shall change the value for the Retry (R) bit to 'MS sent channel request message twice or more'. + +While waiting for a response to the PACKET CHANNEL REQUEST message, the mobile station shall monitor the full PCCH corresponding to its PCCH\_GROUP. The mobile station shall perform signal strength measurements as they are defined for packet idle mode, see 3GPP TS 45.008. + +While monitoring the full PCCH, the mobile station shall decode any occurrence of the PERSISTENCE\_LEVEL parameter included in a message received on PCCH. When the mobile station receives the PERSISTENCE\_LEVEL parameter, the value of the PERSISTENCE\_LEVEL parameter shall be taken into account at the next PACKET CHANNEL REQUEST attempt that follows. + +A mobile station that is IMSI attached (GPRS class A or B mode of operation) shall respond to a PACKET PAGING REQUEST message indicating an RR connection establishment. For that purpose, the mobile station may abort the packet access procedure, according to the conditions stated in sub-clause 6.1.4. The mobile station shall not respond to a PACKET PAGING REQUEST message indicating TBF establishment. + +A mobile station that is not IMSI attached (GPRS class C mode of operation) shall not respond to any type of PACKET PAGING REQUEST messages during the packet access procedure, it shall only decode the PERSISTENCE\_LEVEL parameter, if that is included in the message. + +The PACKET CHANNEL REQUEST messages are sent on PRACH and contain an indication of the type of access and parameters required to indicate the mobile station's demand of radio resource. + +There are two formats of the PACKET CHANNEL REQUEST message containing either 8 bits or 11 bits of information. The format to be applied on PRACH is controlled by the parameter ACCESS\_BURST\_TYPE which is broadcast on PBCCH. The access type to be used in the PACKET CHANNEL REQUEST message for a non-EGPRS TBF mode capable MS or an EGPRS TBF mode capable MS in a non-EGPRS capable cell depends on the purpose of the packet access procedure as follows: + +- If the purpose of the packet access procedure is to request multiple TBFs, the mobile station shall indicate 'Two phase access' in the PACKET CHANNEL REQUEST message; +- If the purpose of the packet access procedure is to request a single TBF, the mobile station shall indicate one of the following access causes: + - If the mobile station intends to use the TBF to send user data, it shall request two phase access if the requested RLC mode is unacknowledged mode. If the requested RLC mode is acknowledged mode, the mobile station shall request either one phase access or two phase access. In case of two phase access, if both the mobile station and the BSS support multiple TBF procedures, the BSS may order its preferred RLC mode when establishing an uplink TBF, overriding the mobile station request; + - If the purpose of the packet access procedure is to send a Page Response, the mobile station shall indicate 'Page Response' in the PACKET CHANNEL REQUEST message; + - If the purpose of the packet access procedure is to send a Cell update (the mobile station was in GMM READY state before the cell reselection) the mobile station shall indicate 'Cell Update' in the PACKET CHANNEL REQUEST message; + - If the purpose of the packet access procedure is for any other Mobility Management procedure, the mobile station shall indicate 'MM Procedure' in the PACKET CHANNEL REQUEST message; + - If the purpose of the packet access procedure is to send a Measurement Report, the mobile station shall indicate 'Single block without TBF establishment' in the PACKET CHANNEL REQUEST message; + - If the purpose of the packet access procedure is to send a PACKET PAUSE message, the mobile station shall indicate 'Single block without TBF establishment' in the PACKET CHANNEL REQUEST message. Upon the first attempt to send a PACKET CHANNEL REQUEST message the mobile station shall start timer T3204. If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message before expiry of timer T3204, the mobile station shall ignore the message; + - If the purpose of the packet access procedure is to send an MBMS SERVICE REQUEST message to the network, the mobile station shall indicate 'Single block MBMS access' in the PACKET CHANNEL REQUEST message. + +EGPRS TBF mode capable mobile stations shall monitor the GPRS Cell Options IE on the PBCCH (PSI1/PSI13) for the cell's EGPRS capability and, if the mobile station is also Reduced Latency capable, the cell's Reduced Latency Access capability. In the GPRS Cell Options IE it is also indicated if the EGPRS PACKET CHANNEL REQUEST message is supported in the cell and if Reduced Latency Access is supported in the cell. If the mobile station supports the IMMEDIATE PACKET ASSIGNMENT message, the mobile station shall monitor cell's capability for IMMEDIATE PACKET ASSIGNMENT message within paging messages received on its own paging sub-channel. The + +following table specifies which message and which access type shall be used by an EGPRS mobile station when accessing an EGPRS capable cell depending on the purpose of the packet access procedure, and mobile station's and cell's capabilities; this table covers the case where PBCCH is present in the cell (see 3GPP TS 44.018 for the case where PBCCH is not present in the cell). The network shall not indicate Reduced Latency Access is supported if the EGPRS PACKET CHANNEL REQUEST message is not indicated as supported. The network shall not indicate IMMEDIATE PACKET ASSIGNMENT message is supported if the EGPRS PACKET CHANNEL REQUEST message is not indicated as supported. + +**Table 7.1.2.1.1: EGPRS PACKET CHANNEL REQUEST support** + +| Purpose of the packet access procedure | EGPRS PACKET CHANNEL REQUEST supported in the cell | EGPRS PACKET CHANNEL REQUEST not supported in the cell | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|--|--| +| User data transfer - requested RLC mode = unacknowledged | EGPRS PACKET CHANNEL REQUEST with access type = 'Two Phase Access Request' | PACKET CHANNEL REQUEST with access type = 'Two Phase Access Request' (NOTE 1) | | | +| User data transfer - requested RLC mode = acknowledged | EGPRS PACKET CHANNEL REQUEST with access type = 'One Phase Access Request' or 'Two Phase Access Request' | PACKET CHANNEL REQUEST with access type = 'Two Phase Access Request' (NOTE 1) | | | +| User data transfer - requested RLC mode = acknowledged (Reduced Latency supported by MS) | EGPRS PACKET CHANNEL REQUEST with access type = 'One Phase Access Request by Reduced Latency MS' (NOTE 3) | PACKET CHANNEL REQUEST with access type = 'Two Phase Access Request' (NOTE 1) | | | +| Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc) | EGPRS PACKET CHANNEL REQUEST with access type = 'Signalling' | PACKET CHANNEL REQUEST with access type = 'Two Phase Access Request' | | | +| Sending of a measurement report or of a PACKET CELL CHANGE FAILURE | PACKET CHANNEL REQUEST with access type = 'Single block without TBF establishment' (NOTE 1) | | | | +| Sending of a PACKET PAUSE message | PACKET CHANNEL REQUEST with access type = 'Single block without TBF establishment' (NOTE 1) (NOTE 2) | | | | +| Sending of an MBMS Service Request message | PACKET CHANNEL REQUEST with access type = 'Single block MBMS access' (NOTE 1) | | | | +| NOTE 1: The format to be used for the PACKET CHANNEL REQUEST message is defined by the parameter ACCESS_BURST_TYPE. | | | | | +| NOTE 2: Upon the first attempt to send a PACKET CHANNEL REQUEST message the mobile station shall start timer T3204. If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message before expiry of timer T3204, the mobile station shall ignore the message. | | | | | +| NOTE 3: The 'One phase Access Request by Reduced Latency MS' shall be used by the mobile station supporting reduced latency if Reduced Latency Access is supported by the network. | | | | | + +#### 7.1.2.1.1 Access persistence control on PRACH + +The mobile station shall make maximally $M + 1$ attempts to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message. + +After sending each PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, the mobile station shall listen to the full PCCCH corresponding to its PCCCH\_GROUP. + +The PRACH Control Parameters IE contains the access persistence control parameters and shall be broadcast on PBCCH and PCCCH. The parameters included in the PRACH Control Parameters IE are: + +- MAX\_RETRANS, for each radio priority $i$ ( $i = 1, 2, 3, 4$ ); +- PERSISTENCE\_LEVEL, which consists of the PERSISTENCE\_LEVEL $P(i)$ for each radio priority $i$ ( $i = 1, 2, 3, 4$ ); where $P(i) \in \{0, 1, \dots, 14, 16\}$ . If the PRACH Control Parameters IE does not contain the PERSISTENCE\_LEVEL parameter, this shall be interpreted as if $P(i) = 0$ for all radio priorities; +- S; +- TX\_INT. + +The mobile station shall start timer T3186 at the beginning of the packet access procedure. At expiry of timer T3186, the packet access procedure shall be aborted, and: + +- if at least one PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message was transmitted by the mobile station, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022; +- otherwise, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state. + +The first attempt to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, may be initiated at the first available PRACH block on the PDCH defined by the PCCCH\_GROUP for the mobile station (see 3GPP TS 45.002). The mobile station shall choose one of the four TDMA frames within the selected PRACH block randomly with a uniform probability distribution. + +For each attempt, the mobile station shall draw a random value $R$ with uniform probability distribution in the set $\{0, 1, \dots, 15\}$ . The mobile station is allowed to transmit a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message if $P(i)$ , where $i$ is the radio priority of the TBF being established, is less than or equal to $R$ . + +After each attempt, the $S$ and $T$ parameters are used to determine the next TDMA frame in which it may be allowed to make a successive attempt. The number of TDMA frames belonging to the PRACH on the PDCH defined by the PCCCH\_GROUP for the mobile station between two successive attempts to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message excluding the TDMA frames potentially containing the messages themselves is a random value drawn for each transmission with uniform probability distribution in the set $\{S, S + 1, \dots, S + T - 1\}$ . + +Here: + +$M$ is the value of the parameter MAX\_RETRANS, belonging to the Radio Priority of the access; + +$T$ is the value of the parameter TX\_INT; + +$S$ is the value of the parameter $S$ . + +Having made $M + 1$ attempts to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, the mobile station shall stop timer T3186 and start timer T3170 if at least one PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message was transmitted by the mobile station. In this case, at expiry of timer T3170, the packet access procedure shall be aborted, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022. Otherwise, the packet access procedure shall be aborted, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state. + +If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message while it is waiting for a response to a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, it shall abort the packet access procedure and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1). The mobile station shall then attempt establishment of an uplink TBF using the procedures defined in sub-clause 8.1.2.5. + +## 7.1.2.2 Packet assignment procedure + +### 7.1.2.2.1 On receipt of a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message + +On receipt of a PACKET CHANNEL REQUEST message, the network may assign a radio resource on one or more PDCHs to be used by the mobile station for the TBF in GPRS TBF mode. On receipt of an EGPRS PACKET CHANNEL REQUEST message, the network may assign a radio resource on one or more PDCHs to be used by the mobile station for the TBF in EGPRS TBF mode or GPRS TBF mode. + +The allocated PDTCH and PACCH resource is assigned to the mobile station in a PACKET UPLINK ASSIGNMENT message, sent on any PAGCH block on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. The *Packet Request Reference* information element shall be used to address the mobile station and frequency parameters shall be included. + +A mobile station supporting Downlink Dual Carrier may be sent a PACKET UPLINK ASSIGNMENT message to assign radio resources on two different radio frequency channels for a given uplink TBF. In such a configuration, uplink radio blocks shall not be allocated on both radio frequency channels during any given radio block period. + +The mobile station may use information received on PBCCH, BCCH or a previous assignment message to decode the frequency parameters contained in the assignment message. If the mobile station detects an invalid *Frequency Parameters* information element or an invalid *Dual Carrier Frequency Parameters* information element in the assignment message, it shall abort the procedure, if required initiate a partial acquisition of PBCCH or BCCH information, and may then re-initiate this procedure. + +If the dynamic allocation medium access mode is commanded, the network shall include the USF values allocated for PDCHs in the PACKET UPLINK ASSIGNMENT message. + +Unless the mobile station has indicated a "Single Block Without TBF Establishment" or "Single block MBMS access" in a PACKET CHANNEL REQUEST message, the mobile station shall perform a two phase access if the PACKET UPLINK ASSIGNMENT message includes a Single Block Allocation struct or a Multi Block Allocation struct. + +If the PACKET UPLINK ASSIGNMENT message includes Dynamic Allocation struct and the MS has not requested 'Single Block Without TBF Establishment', 'Two phase access', or 'Single Block MBMS access', the mobile station shall perform a one phase access. + +In case the MS requested two phase access, the procedures in sub-clause 7.1.3 shall apply. + +A mobile station that has indicated "Single Block Without TBF Establishment" in the PACKET CHANNEL REQUEST message for the purpose of sending a measurement report shall send a measurement report according to sub-clause 7.3.1. + +A mobile station that has indicated "Single Block Without TBF Establishment" in the PACKET CHANNEL REQUEST message for the purpose of sending a PACKET CELL CHANGE FAILURE message shall send that message according to sub-clause 8.4.2. + +On receipt of a PACKET UPLINK ASSIGNMENT message corresponding to one of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages the mobile station shall stop timers T3186 and T3170 if running and stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages. + +If the PACKET UPLINK ASSIGNMENT message does not specify a TBF starting time, the mobile station shall switch to the assigned PDCHs, start timer T3164 if dynamic or extended dynamic allocation is assigned and proceed with contention resolution of the one phase packet access procedure according to sub-clause 7.1.2.3 (*A/Gb mode*) or in case of EGPRS, sub-clause 7.1.2.3a (*A/Gb mode*). + +Unless assigning resources for RTTI, dual carrier, BTTI with FANR activated or EGPRS2 configurations, a PACKET UPLINK ASSIGNMENT message may indicate an assignment starting time in the TBF Starting Time parameter. The mobile station shall monitor the full PCCCH until the point in time denoted by the TBF Starting Time. Thereafter it shall switch to the assigned PDCHs. If dynamic or extended dynamic allocation is assigned, the mobile station shall start timer T3164. Regardless of which allocation mode is used, the mobile station shall proceed with the contention resolution defined in sub-clause 7.1.2.3 (*A/Gb mode*) or in case of EGPRS, sub-clause 7.1.2.3a (*A/Gb mode*). If the mobile station receives more than one PACKET UPLINK ASSIGNMENT message, it shall act upon the most recently received message and shall ignore the previous message. + +When the mobile station switches to the assigned PDCHs, it shall take the power control parameters received in the PACKET UPLINK ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode or MAC-Shared state (see 3GPP TS 45.008). + +On receipt of a PACKET CHANNEL REQUEST message with establishment cause indicating "Two Phase Access Request", "Single block without TBF establishment" or "Single block MBMS access", the network may allocate a single radio block on an uplink PDCH. In order to force the mobile station to make a two phase access, the network may allocate a single radio block on an uplink PDCH on receipt of a PACKET CHANNEL REQUEST message with any of the other access types. + +On receipt of an EGPRS PACKET CHANNEL REQUEST message with establishment cause indicating "Two Phase Access Request", the network may allocate a Multi Block allocation on an uplink PDCH. In order to force the mobile station to make a two phase access, the network may allocate a Multi Block allocation on an uplink PDCH on receipt of an EGPRS PACKET CHANNEL REQUEST message with any of the other access types. + +If the mobile station has been allocated a single block (respectively a Multi Block allocation) in the PACKET UPLINK ASSIGNMENT message and the mobile station has not indicated "Single block without TBF + +establishment" (respectively "Two phase access") in the PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message or "Single block MBMS access" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed with the two phase packet access procedure according to sub-clause 7.1.3 (*A/Gb mode*). + +If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT message and the purpose of the packet access procedure is to send a Measurement Report message and the mobile station has indicated "Single block without TBF establishment" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed according to sub-clause 7.3.1. + +If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT message and the purpose of the packet access procedure is to send a PACKET PAUSE message and the mobile station has indicated "Single block without TBF establishment" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed according to sub-clause 7.6. + +If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT message and the purpose of the packet access procedure is to send an MBMS SERVICE REQUEST message and the mobile station has indicated "Single block MBMS access" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed according to sub-clause 7.7.1.2.2. + +#### 7.1.2.2.1a Acquisition of MS Radio Access Capability information within EGPRS TBF establishment procedure + +When assigning an EGPRS TBF, the network may request information about radio access capabilities of the mobile station on one or several frequency bands within the PACKET UPLINK ASSIGNMENT message; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall provide the network with its radio access capabilities for the frequency bands it supports, in the same priority order as the one specified by the network, by sending a PACKET RESOURCE REQUEST message, and an ADDITIONAL MS RADIO ACCESS CAPABILITIES message if all the requested information does not fit in the PACKET RESOURCE REQUEST. If the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the BCCH frequency band. The mobile station shall indicate in the PACKET RESOURCE REQUEST if it will send more information about its radio access capabilities in the ADDITIONAL MS RADIO ACCESS CAPABILITIES message. The PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES messages shall be sent within the one or two first radio blocks allocated for the mobile station on the assigned PDCH. The mobile station shall include the TLLI in these two messages until contention resolution. After that, the mobile station may use either the uplink TFI or the TLLI when these messages are repeated. + +When constructing the PACKET RESOURCE REQUEST and ADDITIONAL MS RADIO ACCESS CAPABILITIES messages the mobile station shall take care that these messages fit in one UL radio block each. See sub-clause 12.30 for additional restrictions regarding how information for a given access technology type is to be provided using these messages. + +The network may request a retransmission of the PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES messages. A request for retransmission of one or both of these messages shall be indicated in the PACKET UPLINK ACK/NACK or the PACKET UPLINK ASSIGNMENT message. The mobile station has to indicate within the PACKET RESOURCE REQUEST message if the message is a retransmitted one. For the case of message retransmission the most recently sent instance of these messages shall be retransmitted. If these messages have not already been sent by the MS during the establishment (two phase access) or after the establishment (one phase access) of the corresponding uplink TBF then the request shall be ignored. + +#### 7.1.2.2.2 Packet access queuing notification procedure + +The network may send to the mobile station a PACKET QUEUING NOTIFICATION message. The PACKET QUEUING NOTIFICATION message shall be sent on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. It contains a Temporary Queuing Identity which is later used to identify the mobile station (either when polling or sending an assignment). + +On receipt of a PACKET QUEUING NOTIFICATION message corresponding to one of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, the mobile station shall stop timers T3170 and T3186 if running, start timer T3162, and stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages. It shall continue to listen to the full PCCCH corresponding to its PCCCH\_GROUP. If the mobile station receives a PACKET QUEUING NOTIFICATION message while waiting for + +the TBF Starting Time of a valid PACKET UPLINK ASSIGNMENT message, the mobile station shall ignore the PACKET QUEUING NOTIFICATION message. + +The network may send to the mobile station a PACKET UPLINK ASSIGNMENT message following a PACKET QUEUING NOTIFICATION message. In this case, the reference address to the mobile station shall be the Temporary Queuing Identity received in the PACKET QUEUING NOTIFICATION message. + +On receipt of a PACKET UPLINK ASSIGNMENT message following a PACKET QUEUING NOTIFICATION message, the mobile station shall stop timer T3162 and follow the procedures defined in sub-clause 7.1.2.2.1. + +At expiry of timer T3162, the packet access procedure shall be aborted and a packet access failure shall be indicated to the upper layer and the mobile station shall return to packet idle mode or MAC-Idle state. + +If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall abort the packet access queuing notification procedure and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1). The mobile station shall then attempt establishment of an uplink TBF using the procedures defined in sub-clause 8.1.2.5. + +#### 7.1.2.2.3 Packet polling procedure + +The network may send to the mobile station a PACKET POLLING REQUEST message after having sent a PACKET QUEUING NOTIFICATION message. The PACKET POLLING REQUEST message shall be sent on the same PDCH on which the network has received the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. The mobile station shall be addressed by the Temporary Queuing Identity. + +On receipt of a PACKET POLLING REQUEST message, the mobile station shall respond to the network with the PACKET CONTROL ACKNOWLEDGEMENT message in the reserved uplink radio block specified by the RRBP field. The reserved block is considered as a one block PACCH allocation. + +#### 7.1.2.2.4 Packet access reject procedure + +The network may, as response to a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message, send to the mobile station a PACKET ACCESS REJECT message on any PAGCH block on the same PCCCH on which the channel request message was received. This message contains the request reference with time of reception of the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message and optionally a WAIT\_INDICATION field in the Reject structure of the PACKET ACCESS REJECT message. + +On receipt of a PACKET ACCESS REJECT message containing a Reject structure addressed to the mobile station, where the Packet Request Reference in the Reject structure corresponds to one of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages: + +- The mobile station shall stop timer T3186, stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, start timer T3172 with the value indicated in the WAIT\_INDICATION field, start timer T3170 if it has not already been started and listen to the downlink PCCCH until timer T3170 expires. During this time, the mobile station shall ignore additional PACKET ACCESS REJECT messages, but on reception of any PACKET UPLINK ASSIGNMENT message corresponding to any other of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages the mobile station shall stop timers T3170 and T3172 if running, and follow the procedure defined in sub-clause 7.1.2.2.1; +- If no PACKET UPLINK ASSIGNMENT message is received before expiration of timer T3170, the mobile station shall indicate a packet access failure to upper layer and return to packet idle mode (listening to its paging channel). As an option the mobile station may stop timer T3170, indicate a packet access failure to upper layer and return to packet idle mode as soon as it has received responses from the network on all or, in case more than 3 were sent, the last 3 of its PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages; +- If an erroneous PACKET UPLINK ASSIGNMENT message (e.g. the mobile station has been assigned more PDCHs than it supports according to the relevant multislot configuration as defined in 3GPP TS 45.002) addressed to the mobile station is received before expiration of timer T3170, the mobile station shall stop T3170 and act as stated in sub-clause 7.1.4; +- If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall stop timer T3170 if running and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1); + +- The mobile station is not allowed to make a new attempt for packet access in the same cell until timer T3172 expires, but may attempt packet access in another cell after successful cell reselection for radio conditions reasons (see 3GPP TS 45.008). In *A/Gb mode*, a mobile station that is IMSI attached (GPRS class A or B mode of operation) may attempt to enter the dedicated mode in the same cell before timer T3172 has expired. During the time T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging requests sent to trigger RR connection establishment and paging requests sent to trigger the acquisition of an ETWS Primary Notification message; +- The value of the WAIT\_INDICATION field (i.e. timer T3172) relates to the cell from which it was received. + +### 7.1.2.3 Contention resolution at one phase access + +The TLLI is used to uniquely identify the mobile station when sending on uplink. Every RLC data block that is sent on the TBF shall include the TLLI of the mobile station, until the contention resolution is completed on the mobile station side. If MCS-7, MCS-8 or MCS-9 is used for the transmission of the TLLI in EGPRS TBF mode (i.e. the RLC/MAC block is carrying two RLC data blocks), the TLLI shall be inserted in both RLC data blocks. The TLLI shall also be included in the PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES messages, if those are sent during the contention resolution. + +The retransmission of an RLC data block shall include the TLLI (or the TLLI and the PFI field), if the RLC data block was originally transmitted including these fields, also if the retransmission occurs after the completion of the contention resolution. + +At sending of the first RLC data block, the mobile station shall stop timer T3164, set counter N3104 to 1, and start timer T3166. The counter N3104 shall be stopped each time the mobile station sends an RLC/MAC block for data transfer. + +The network shall respond by including the TLLI in the PACKET UPLINK ACK/NACK message after the first correctly received RLC data block that comprises the TLLI. In EGPRS TBF mode, the network may instead respond by addressing the mobile station with the TFI of the assigned TBF and including the TLLI (in the CONTENTION\_RESOLUTION\_TLLI field) in a PACKET UPLINK ASSIGNMENT message, if the resources allocated for the TBF need to be reallocated (see sub-clause 8.1.1.1.2). + +The contention resolution is completed on the network side when the network receives an RLC data block that comprises the TLLI value that identifies the mobile station and the TFI value associated with the TBF. + +The contention resolution is successfully completed on the mobile station side when the mobile station receives a PACKET UPLINK ACK/NACK message addressing the mobile station with the TFI value associated with the uplink TBF and including the same TLLI value that the mobile station has included in the RLC header of the first RLC data blocks, or alternatively, in EGPRS TBF mode, a PACKET UPLINK ASSIGNMENT message addressing the mobile station with the TFI value associated with the uplink TBF and including the same TLLI value that the mobile station included in the RLC header of the first RLC data blocks. The mobile shall then stop timer T3166 and counter N3104. + +The contention resolution has failed on the mobile station side when the counter N3104 reaches its maximum value, or timer T3166 expires. The contention resolution also fails, if the mobile station receives a PACKET UPLINK ACK/NACK message or in EGPRS TBF mode alternatively a PACKET UPLINK ASSIGNMENT message addressing the mobile station with the TFI associated with the uplink TBF and including a TLLI value other than that the mobile station included in the RLC header of the first RLC data blocks; in such a case, the mobile station shall not transmit a PACKET CONTROL ACKNOWLEDGEMENT in the uplink radio block specified if a valid RRBP field is received as part of the PACKET UPLINK ACK/NACK message or in EGPRS TBF mode alternatively as part of the PACKET UPLINK ASSIGNMENT message. + +In case of a contention resolution failure on the mobile station side, the mobile station shall reset the counter N3104 and stop timer T3166, if not expired. The mobile station shall stop transmitting on the TBF and reinitiate the packet access procedure, unless the packet access procedure has already been attempted four times. In that case, a TBF failure has occurred, see sub-clause 7.1.4. + +#### 7.1.2.3a RLC/MAC procedures during contention resolution + +During the contention resolution, the mobile station may receive a non-distribution RLC/MAC control message addressing the mobile station by TLLI, or the TFI value associated with the uplink TBF. The mobile station shall act on that message using the procedure defined for the message when it is received in packet transfer mode during operation on an uplink TBF (see clause 8), with the following restrictions: + +- The mobile station shall not accept a PACKET MEASUREMENT ORDER message, a PACKET CELL CHANGE ORDER message and a PACKET POWER CONTROL/TIMING ADVANCE message addressing the mobile station with the TFI value associated with the uplink TBF; +- The mobile station shall not accept a PACKET DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message. + +If a valid RRBP field is received as part of the RLC/MAC control block, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified (see sub-clause 10.4.5) if it acts on the message; the mobile station may transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified if it does not act on the message. + +If during the contention resolution, upper layers request the transfer of another upper layer PDU with a different PFI, a different Radio Priority, a different peak throughput class or a different RLC mode than the one which is in transfer, then the procedures as described in packet transfer mode (see sub-clause 8.1.1.1.2) shall be applied by the mobile station. + +In either case, the mobile station shall continue with the contention resolution on the uplink TBF, till it either completes successfully or fails, or that the uplink TBF is released as a result of the procedure defined for the message that is received. + +#### 7.1.2.4 One phase packet access completion + +The one phase packet access procedure is completed upon a successful contention resolution. The mobile station has entered the packet transfer mode or MAC-Shared state. + +#### 7.1.2.5 Timing Advance + +Initial timing advance may be provided in the PACKET UPLINK ASSIGNMENT in the TIMING\_ADVANCE\_VALUE field. + +Thereafter either the timing advance is updated with a PACKET POWER CONTROL/TIMING ADVANCE message or a continuous timing advance procedure is used. If a Timing Advance Index is included in the assignment message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise, the continuous timing advance procedure shall not be used. For the case where a TIMING\_ADVANCE\_VALUE field is not provided in the assignment message, the mobile station is not allowed to send normal bursts on the uplink until it receives a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL/TIMING ADVANCE message. + +In the case of a mobile station with a Downlink Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1 (see sub-clause 5.5.1.7). If a mobile station with a Downlink Dual Carrier configuration subsequently receives an assignment message which results in the mobile station no longer being in a Downlink Dual Carrier configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned. + +In the case of a mobile station in a DLMC configuration where the continuous timing advance procedure is used the assignment message indicates the carrier on which the PTCCH is allocated. If a mobile station in a DLMC configuration subsequently receives an assignment message that results in the mobile station no longer being in a DLMC configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned. + +#### 7.1.2.6 PFC procedure at one phase access + +If the PFC\_FEATURE\_MODE field indicates that the network supports PFC procedures in the system information and if a PFC exists for the LLC data to be transferred then the PFI shall be transmitted along with the TLLI of the mobile station in the RLC extended header during contention resolution. If the PFC\_FEATURE\_MODE field indicates that the network does not support PFC procedures, the mobile station shall not indicate a PFI value. If no valid PFI is assigned, the default mapping defined in sub-clause 5.5.1.9 shall be used. The PFI is not used for contention resolution but is included to indicate to the network which PFC shall initially be associated with the uplink TBF. + +### 7.1.3 TBF establishment using two phase access + +The two phase access procedure defined in this sub-clause, is applicable also in the case when no PCCCH is provided in the cell. For that case, the first phase is defined in 3GPP TS 44.018. + +#### 7.1.3.1 Initiation of the Packet resource request procedure + +In the first phase of a two phase access in a cell provided with a PCCCH, the same procedures as for one phase access are used until the network sends a PACKET UPLINK ASSIGNMENT message including a Single Block Allocation struct or Multi Block Allocation struct, denoting two phase access to the mobile station. The Multi Block Allocation struct may be used only if the mobile station has EGPRS capability (i.e. the network received an EGPRS PACKET CHANNEL REQUEST message from the mobile station). In the PACKET UPLINK ASSIGNMENT message, the network reserves a limited resource on one PDCH to the mobile station where the mobile station may transmit a PACKET RESOURCE REQUEST message and optionally an ADDITIONAL MS RADIO ACCESS CAPABILITIES message. + +If PCCCH is provided in the cell, a two phase access can be initiated: + +- by the network by ordering the mobile station to send a PACKET RESOURCE REQUEST message. The order is sent implicitly to the mobile station in the PACKET UPLINK ASSIGNMENT message by including either the Single Block Allocation struct or Multi Block Allocation struct; +- by a mobile station, by requiring a two phase access in the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. In this case, if access is granted, the network shall order the mobile station to send a PACKET RESOURCE REQUEST message. The order is sent implicitly to the mobile station in the PACKET UPLINK ASSIGNMENT message by including the Single Block Allocation struct or Multi Block Allocation struct. + +If no PCCCH is provided in the cell, a two phase access can be initiated by the network or by a mobile station, as defined in 3GPP TS 44.018. + +When the mobile station has received the PACKET UPLINK ASSIGNMENT message it shall respond with a PACKET RESOURCE REQUEST message in the first allocated radio block. + +A mobile station supporting EGPRS shall indicate the EGPRS capability in the MS Radio Access Capability 2 IE of the PACKET RESOURCE REQUEST message. + +A mobile station supporting multiple TBF procedures shall set the Multiple TBF Capability flag in the *MS Radio Access Capability 2* IE of the PACKET RESOURCE REQUEST message. + +A mobile station attempting a packet access for the purpose of *NAS signalling low priority* (see 3GPP TS 24.008) shall set the *Low Access Priority Signalling* field to "1" in the PACKET RESOURCE REQUEST message (see sub-clause 11.2.16). The *Low Access Priority Signalling* field shall be set to "0" if the PACKET RESOURCE REQUEST message is sent for any other reason and includes the *Low Access Priority Signalling* field. + +When the mobile station switches to the assigned PDCH, it shall take the power control parameters received in the PACKET UPLINK ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode (see 3GPP TS 45.008). + +At sending of the PACKET RESOURCE REQUEST message requesting a single uplink TBF, the mobile station shall start timer T3168. At sending of the PACKET RESOURCE REQUEST message requesting multiple TBFs, the mobile station shall start contention resolution timer T3188 and additionally one instance of T3168 for each of the resource requests for the transfer of upper layer PDUs. Furthermore, the mobile station shall not respond to PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT messages before contention resolution is completed on the mobile station side - but may acknowledge such messages if they contain a valid RRBP field. + +The mobile station may indicate in the PACKET RESOURCE REQUEST message the number of octets of user data it has to transfer. + +#### 7.1.3.2 Packet resource assignment for uplink procedure + +When assigning a Multi Block Allocation, the network may request information about radio access capabilities of the mobile station on one or several frequency bands within the PACKET UPLINK ASSIGNMENT message and allocate + +one or two radio blocks for uplink control messages accordingly; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall provide the network with its radio access capabilities for the frequency bands it supports, in the same order of priority as specified by the network, by sending a PACKET RESOURCE REQUEST message in the first radio block on the assigned PDCH and an ADDITIONAL MS RADIO ACCESS CAPABILITIES message in the next radio block on the assigned PDCH, if the requested information does not fit in the PACKET RESOURCE REQUEST and two radio blocks have been allocated by the network. If the network does not provide an Access Technologies Request in the PACKET UPLINK ASSIGNMENT message or the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the frequency band of the BCCH carrier in the PACKET RESOURCE REQUEST message. + +The mobile station shall indicate in the PACKET RESOURCE REQUEST message, by setting the ADDITIONAL MS RAC INFORMATION AVAILABLE bit, if it will send more information about its radio access capabilities in the ADDITIONAL MS RADIO ACCESS CAPABILITIES message if it has been allocated two radio blocks, or if it would have sent more information but has been allocated only one radio block. If the mobile station has been allocated two radio blocks and the requested information fit in the PACKET RESOURCE REQUEST message, no ADDITIONAL MS RADIO ACCESS CAPABILITIES message shall be sent. Instead, some uplink control block (e.g. packet measurement report, packet uplink dummy control block) may be sent by the mobile station. + +The network may indicate in the next PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message a request for retransmission of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message (see sub-clause 7.1.3.2.1). + +When constructing the PACKET RESOURCE REQUEST and ADDITIONAL MS RADIO ACCESS CAPABILITIES messages the mobile station shall take care that these messages fit in one uplink radio block each (see sub-clause 7.1.2.2.1a). + +If the network indicates that it supports packet flow procedures via the PFC\_FEATURE\_MODE in the system information, then the mobile station supporting PFC procedures shall indicate the initial PFI to be associated with the TBF in the PACKET RESOURCE REQUEST message. If the PFC\_FEATURE\_MODE field indicates that the network does not support PFC procedures, the mobile station shall not indicate a PFI value. If no valid PFI is assigned, the default mapping defined in sub-clause 5.5.1.9 shall be used. If the mobile station requests multiple TBFs in the PACKET RESOURCE REQUEST message, it shall indicate the PFI to be associated with each TBF. + +Whenever the mobile station wants to pre-allocate an uplink TBF, it shall send a PACKET RESOURCE REQUEST message with the EARLY\_TBF\_ESTABLISHMENT field set to indicate pre-allocation is required. + +#### 7.1.3.2.1 On receipt of a PACKET RESOURCE REQUEST message + +On receipt of a PACKET RESOURCE REQUEST message requesting a single uplink TBF scheduled with a Single Block or a Multi Block allocation, the network shall respond by sending a PACKET UPLINK ASSIGNMENT message (radio resources assignment on one or more PDCHs to be used by the mobile station for the TBF in EGPRS or GPRS TBF mode) or a PACKET ACCESS REJECT message to the mobile station on PACCH on the same PDCH on which the mobile station has sent the PACKET RESOURCE REQUEST message. If the mobile station supports RLC non-persistent mode the network may allocate an EGPRS TBF that uses this RLC mode. + +On receipt of a PACKET RESOURCE REQUEST message requesting multiple uplink TBFs, the network shall respond by sending either a MULTIPLE TBF UPLINK ASSIGNMENT message or a PACKET ACCESS REJECT message to the mobile station on PACCH on the same PDCH on which the mobile station has sent the PACKET RESOURCE REQUEST message. These messages shall address (assign or reject) some or all of the resource requests in the PACKET RESOURCE REQUEST message. For the resource requests that have not been addressed by the first assignment or reject message, additional MULTIPLE TBF UPLINK ASSIGNMENT or PACKET ACCESS REJECT messages may be sent to the mobile station on the PACCH to which the mobile station has been assigned. If the mobile station supports RLC non-persistent mode the network may allocate one or more EGPRS TBFs that use this RLC mode. + +If the received PACKET RESOURCE REQUEST message is indicating additional MS Radio Access Capabilities information available, the following additional requirements apply: + +- If the PACKET RESOURCE REQUEST message was scheduled with a Multi Block allocation of two blocks, the network shall respond by sending a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message after reception of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message; +- If the PACKET RESOURCE REQUEST message was scheduled with a Single Block allocation or with a Multi Block allocation of only one block, the network shall respond upon receipt by sending a + +PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message. When assigning one or more EGPRS TBFs, the network may request additional information about radio access capabilities of the mobile station on one or several frequency bands within the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall provide the network with its radio access capabilities for the frequency bands it supports, in the same priority order as the one specified by the network, by sending an ADDITIONAL MS RADIO ACCESS CAPABILITIES message within the first radio block allocated to the mobile station on the assigned PDCH(s). When constructing the ADDITIONAL MS RADIO ACCESS CAPABILITIES message, the mobile station shall take care that this message fits in one uplink radio block (see sub-clause 7.1.2.2.1a). If the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the BCCH frequency band. + +In case the ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not received correctly, the network may either: + +- send a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message assigning radio resources on one or more PDCHs to be used by the mobile station for the TBF(s) in EGPRS or GPRS TBF mode, based on the information the network has got, or let unchanged the already assigned PDCH(s); +- send a PACKET UPLINK ASSIGNMENT message assigning (or reassigning) radio resources on one or more PDCHs to be used by the mobile station for the TBF(s) in EGPRS TBF mode and request a retransmission of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message. + +In addition, in case the ADDITIONAL MS RADIO ACCESS CAPABILITIES message scheduled with a Multi Block allocation of two blocks is not received correctly, the network may either: + +- send a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message including a Multi Block allocation struct (allocating only one block) requesting a retransmission of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message; +- send a PACKET ACCESS REJECT message to the mobile station. + +On receipt of a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message where no TBF starting time is specified, the mobile station shall switch to the assigned PDCHs, stop T3168 for each resource request that is assigned a TBF in the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message, and start timer T3164 for each allocated TBF if dynamic or extended dynamic allocation is assigned. If a TBF starting time is specified the mobile station shall stop T3168 for each resource request assigned a TBF and wait until the indicated TBF starting time before switching to the assigned PDCHs and starting T3164 for each allocated TBF. + +At sending of the first RLC data block on a TBF, the mobile station shall stop timer T3164 for that TBF. + +The mobile station may use information received on PBCCH, BCCH or a previous assignment message to decode the frequency parameters contained in the assignment message. If the mobile station detects an invalid Frequency Parameters information element in the assignment message, it shall abort the procedure, if required initiate a *partial acquisition* of PBCCH or BCCH information, and may then re-initiate the access on the PRACH. + +On receipt of a PACKET ACCESS REJECT message that contains a Reject structure addressed to the mobile station, the mobile station shall stop timer T3168 and indicate a packet access failure to upper layer for each resource request which is rejected in the Reject structure. + +If the PACKET ACCESS REJECT message contains a WAIT\_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall start timer T3172 with the indicated value (Wait Indication). The mobile station is not allowed to make a new attempt for packet access in the same cell until timer T3172 expires, but may attempt packet access in another cell after successful cell reselection. + +When the network receives a Packet Flow Identifier (PFI) from the mobile then the network should handle the uplink transfer according the associated aggregate BSS QoS profile (ABQP). The Peak Throughput specified in the associated ABQP, available in the network, supersedes the Peak Throughput specified by the Channel Request Description IE. + +When an uplink TBF is established in response to a PACKET RESOURCE REQUEST message with the EARLY\_TBF\_ESTABLISHMENT field set to indicate pre-allocation is required, a network supporting early TBF establishment should keep the uplink TBF open by means of the extended uplink TBF mode operation (see sub-clause 9.3.1b.2). + +### 7.1.3.3 Contention resolution at two phase access + +The contention resolution is completed on the network side when the network receives a TLLI value identifying the mobile station, as part of the contention resolution procedure on the TBF. + +The contention resolution is completed on the mobile station side when the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT or PACKET ACCESS REJECT message with the same TLLI as the mobile station has included in the PACKET RESOURCE REQUEST and ADDITIONAL MS RADIO ACCESS CAPABILITIES messages that addresses at least one TBF for which resources were requested in the PACKET RESOURCE REQUEST message. + +- If the mobile station receives an assignment for its single uplink TBF request, it shall then stop timer T3168. It does not include its TLLI in any RLC data block; +- If the mobile station receives an assignment for at least one TBF of a multiple uplink TBF request, it shall then stop timer T3188 and the instance of T3168 which was started for the assigned TBF. It does not include its TLLI in any RLC data block. + +After contention resolution is successfully completed on the mobile station side, if the mobile station requested multiple uplink TBFs and an instance of timer T3168 expires, TBF establishment for the corresponding upper layer PDU has failed. The mobile station shall reinitiate a resource request for that upper layer PDU using the procedures described in sub-clauses 8.1.1.1.2a and 8.1.1.1.2b. + +The contention resolution has failed on the mobile station side when the mobile station does not receive a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message with its TLLI assigning at least one TBF for which resources were requested before expiry of timer T3168 (single uplink TBF requested) or T3188 (multiple uplink TBFs requested). The mobile station shall then reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred and an RLC/MAC error should be reported to the higher layer for each of the TBFs for which resources were requested. + +### 7.1.3.4 Two phase packet access completion + +The two phase packet access procedure is completed upon a successful contention resolution. The mobile station has entered the packet transfer mode or MAC-Shared state. + +### 7.1.3.5 Timing Advance + +If a Timing Advance Index is included in the PACKET UPLINK ASSIGNMENT message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise, the continuous timing advance procedure shall not be used. + +For the case where a TIMING\_ADVANCE\_VALUE field is not provided in the assignment message, the mobile station shall use its previous timing advance (either assigned in the previous IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message received on AGCH or in the previous PACKET UPLINK ASSIGNMENT message received on PAGCH or got through the continuous timing advance procedure). + +Otherwise, the mobile station is not allowed to send normal bursts on the uplink until it receives a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL/TIMING ADVANCE message. + +In the case of a mobile station with a Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1 (see sub-clause 5.5.1.7). If a mobile station with a Dual Carrier configuration subsequently receives an assignment message which results in the mobile station no longer being in a Dual Carrier configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned. + +### 7.1.3.6 RTTI Assignments + +If assigned resources are for an RTTI configuration, then the assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, etc.) specifies a set of PDCH pairs for both the uplink and downlink. + +If the default single carrier PDCH pair configuration is indicated, then the assignment is for resources on a subset of the PDCH pairs consisting of the ordered sequence of timeslots pairs 0 and 1 (pair 1), 2 and 3 (pair 2), 4 and 5 (pair 3), and 6 and 7 (pair 4) in both the uplink and on the downlink. If the default dual carrier PDCH pair configuration is indicated, then the assignment is for resources on a subset of the PDCH pairs consisting of the ordered sequence of timeslots pairs 0 and 1, 2 and 3, 4 and 5, and 6 and 7 on both carriers (respectively numbered as pairs 1 to 4 on the first carrier and pairs 5 to 8 on the second carrier) in both the uplink and on the downlink. Otherwise, the assignment is for resources on a subset of the PDCH pairs as specified in the DOWNLINK\_PDCH\_PAIRS\_C1, DOWNLINK\_PDCH\_PAIRS\_C2, UPLINK\_PDCH\_PAIRS\_C1 and UPLINK\_PDCH\_PAIRS\_C2 bitmaps. + +If the mobile station is currently in packet transfer mode with one or more ongoing TBFs operating in RTTI configuration, then the network may indicate in the assignment message that the PDCH pair configuration is 'Unchanged'. In this case, the PDCH pair configuration described in the most recently received assignment message (for this mobile station) previous to this message applies. + +The *Uplink Assignment PDCH Pairs Description* IE shall be included in a PACKET CS RELEASE INDICATION, PS HANDOVER COMMAND or DTM HANDOVER COMMAND message assigning an RTTI configuration for uplink TBF(s) if and only if no RTTI configuration description for downlink TBF(s) is provided in these messages. + +For the purposes of interpreting the RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_SC and RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_DC bitmaps and the repeated USF structures in the Dynamic Allocation 2 struct and Uplink TBF Assignment 2 struct, PDCH pairs are ordered starting with the PDCH pair on carrier 1 using the lowest numbered timeslots, followed by the PDCH pair on carrier 1 using the next lowest numbered timeslots and so on, followed by the PDCH pair on carrier 2 using the lowest numbered timeslots (if present), etc. + +For an uplink PDCH pair using timeslots i and j, where $j > i$ , the corresponding downlink PDCH pair is: + +- the one using timeslots i and j; else, if no such PDCH pair is specified +- the one using timeslots i-1 and i; else, if no such PDCH pair is specified +- the one using timeslots i-2 and i; else, if no such PDCH pair is specified +- the one using timeslots i-3 and i if such a PDCH pair exists. + +NOTE: It may be the case that there is no downlink PDCH pair which corresponds to a given uplink PDCH pair. + +For a downlink PDCH pair, the corresponding uplink PDCH pair is the uplink PDCH pair (if it exists) for which the downlink PDCH pair is the corresponding downlink PDCH pair. + +NOTE: It may be the case that there is no uplink PDCH pair which corresponds to a given downlink PDCH pair. + +The network shall activate FANR for any assigned TBF which uses an RTTI configuration (see sub-clause 9.1.14). + +### 7.1.3.7 MTI Configurations + +If the mobile station supports MTI configurations, the network may assign a mobile station a TBF comprising a combination of both RTTI and BTI resources (i.e. MTI resources). In this case the assigned MTI resources consist of one PDCH and one or more PDCH-pairs where the PDCH is always assigned the timeslot adjacent to either the lowest or highest numbered timeslot of the assigned PDCH-pairs on that carrier. In a downlink dual carrier configuration, a TBF operating in MTI configuration shall be assigned MTI resources on one or both carriers. If MTI resources are only assigned on one carrier then the remaining carrier may be assigned either BTI or RTTI resources. + +NOTE: Examples of valid and invalid MTI configurations are illustrated in Annex M. + +The specification of the following MAC procedures includes aspects which are specific to MTI configurations: + +- Selection of RLC data blocks for transmission on RTTI and BTI resources (see sub-clause 8.1.1); +- Uplink transfer and PACCH operation when using Extended Dynamic Allocation (see sub-clauses 8.1.1.2.1 and 8.1.1.2.2). + +Other MAC procedures applicable to the RTTI and BTI resources assigned as part of an MTI configuration apply as if they were separate TBFs, and therefore references to a "TBF operating in RTTI configuration" (respectively "TBF + +operating in BTTI configuration") shall also refer to "resources operating in RTTI configuration within an MTI configuration" (respectively "resources operating in BTTI configuration within an MTI configuration"). + +The specification of the following RLC procedures includes aspects which are specific to MTI configurations: + +- Encoding and interpretation of Piggy-backed Ack/Nack fields encoded using Time-based encoding (see sub-clauses 9.1.15 and 11.2.29); +- Countdown procedure: definition of MTS parameter (see sub-clause 9.3.1.1). + +The network shall activate FANR for any assigned TBF which uses an MTI configuration. + +Reaction times applicable to TBFs operating in MTI configurations shall be those specified for TBFs operating in RTTI configurations (see 3GPP TS 45.010) + +### 7.1.4 Abnormal cases + +If a failure occurs on the mobile station side of the new TBF before mobile station has successfully entered the packet transfer mode, the newly reserved resources are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the failure is due to a TLLI mismatch, or to the expiry of timers T3166 or T3168, or to the fact that the counter N3104 reaches its maximum value in the contention resolution procedure, and repetition as described in sub-clauses 7.1.2.3, 7.1.3.2.1 or 7.1.3.3 has been performed, the mobile station shall remain in packet idle mode, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continued, unless the failure takes place during a RR-cell change order procedure, in which case the mobile behaviour shall be as described in the Abnormal cases of the RR-Network Commanded Cell Change Order Procedure in 3GPP TS 44.018; +- If the mobile station has been assigned more PDCHs than it supports according to the relevant multislot configuration as defined in 3GPP TS 45.002, the mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred; +- If the information in the PACKET UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred; +- If the information in the MULTIPLE TBF UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall reinitiate the packet access procedure for each of the TBFs for which there is an error unless the procedure has already been attempted 4 times for the TBF. In that case, TBF failure has occurred; +- If the MULTIPLE TBF UPLINK ASSIGNMENT message contains assignments including PFI values for which no TBF was requested, the mobile station shall not act upon these assignments. The mobile station shall act upon the valid assignments contained in the received message; +- If the MULTIPLE TBF UPLINK ASSIGNMENT message contains assignments such that more than one PFI value has been assigned to the same TFI, then TBF failure has occurred for the requests containing each of those PFI values; +- If the PACKET UPLINK ASSIGNMENT message contains an assignment including a PFI value for which no resources were requested, the mobile station shall not act upon the assignment. The mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred; +- If the PACKET ACCESS REJECT message incorrectly specifies a *Reject structure* and *A/Gb mode Reject structure* for this mobile station, or contains one or more PFIs in the *A/Gb mode Reject structure* for which no TBF was requested, the mobile station shall ignore this message; +- If the mobile station has been assigned a TBF in EGPRS mode and the MS does not support EGPRS, or has been assigned an MCS (e.g. 8-PSK in the Uplink) that the MS does not support, the MS shall return to packet idle mode and notify higher layers (TBF establishment failure); + +- On expiry of timer T3164, the mobile station shall reinitiate the packet access procedure for the corresponding TBF unless the packet access procedure has already been attempted four times for this TBF, in which case the mobile station shall notify higher layers of TBF establishment failure. If the mobile station has no remaining TBFs allocated it shall return to packet idle mode and notify higher layers (TBF establishment failure); +- If the failure is due to any other reason, the mobile station shall return to packet idle mode, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continues. + +## 7.2 TBF establishment initiated by the network on PCCCH + +The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of upper layer PDUs in the direction from the network to the mobile station. The procedure may be entered when the mobile station is in packet idle mode. Network initiated TBF establishment can also be done on PACCH if a TBF for transfer of upper layer PDUs in the direction from the mobile station to the network is already established (sub-clause 8.1.1.1.3). + +If the mobile station is in dedicated mode and both the network and the mobile station support DTM, the establishment of a TBF shall be performed by the DTM assignment procedures on the main DCCH, as defined in 3GPP TS 44.018. + +### 7.2.1 Entering the packet transfer mode + +The procedure is triggered by a request from upper layers on the network side to transfer an upper layer PDU to a mobile station in packet idle mode. The request from upper layers specifies an optional priority level, a QoS profile including the requested RLC mode, optional DRX parameters, an optional IMSI and an optional MS Radio Access Capability, multislot class and mobile classmark to be associated with the packet transfer. The request is implicit when receiving an upper layer PDU to a mobile station not already having any assigned radio resources. Upon such a request, the network shall initiate a packet downlink assignment procedure as defined in sub-clause 7.2.1.1. The BSS may order its preferred RLC mode when establishing a downlink TBF, independently of the RLC mode signalled from upper layers. If the mobile station supports RLC non-persistent mode the network may allocate a downlink EGPRS TBF that uses this RLC mode. + +#### 7.2.1.1 Packet downlink assignment procedure + +The network may assign a radio resource on one or more PDCHs to be used for the TBF. The amount of radio resource to be reserved is a network dependent choice. If the network and mobile station both support Downlink Dual Carrier, the network may assign radio resources on one or more PDCHs on two different radio frequency channels to be used for the TBF. + +The allocated radio resource is assigned to the mobile station in a PACKET DOWNLINK ASSIGNMENT message to the mobile station. The PACKET DOWNLINK ASSIGNMENT message is transmitted on the PCCCH timeslot corresponding to the PCCCH group the mobile station belongs to. The appropriate PCCCH group is calculated from the IMSI (see 3GPP TS 45.002). The behaviour of the network when the IMSI is not provided by the upper layers is implementation dependent for the calculation of the PCCCH group where the PACKET DOWNLINK ASSIGNMENT message has to be sent. If the mobile station is in non-DRX mode or if the IMSI or the DRX parameters are not provided by the upper layers, there is no further restriction on what part of the downlink PCCCH timeslot this PACKET DOWNLINK ASSIGNMENT message can be sent, provided that this part corresponds to one or more blocks where paging may appear. If the mobile station applies DRX, this message shall be sent in one or more PCCCH block(s) corresponding to a paging group determined for the mobile station in packet idle mode or MAC-Idle state (see 3GPP TS 45.002). The multislot capabilities of the mobile station shall be considered. + +Initial timing advance can be provided in the PACKET DOWNLINK ASSIGNMENT message as Timing Advance Value field. In case valid timing advance for the mobile station is not available, the network may use one of the following two methods to trigger the mobile station to transmit a PACKET CONTROL ACKNOWLEDGEMENT message: + +- if the PACKET DOWNLINK ASSIGNMENT message is not segmented and the CONTROL\_ACK\_TYPE parameter in the System Information indicates acknowledgement is access bursts, the network may set the poll bit in the PACKET DOWNLINK ASSIGNMENT message. +- if the PACKET DOWNLINK ASSIGNMENT message is segmented or the CONTROL\_ACK\_TYPE parameter in the System Information does not indicate acknowledgement is access bursts, the network may send PACKET POLLING REQUEST message with TYPE\_OF\_ACK parameter set to access bursts (see sub-clause 11.2.12). + +The mobile station shall then send the PACKET CONTROL ACKNOWLEDGEMENT message as four access bursts in the reserved uplink radio block specified by the RRBG field as defined in sub-clause 10.4.5. The reserved block is considered as a one block PACCH allocation. The PACKET CONTROL ACKNOWLEDGEMENT message is used to derive the timing advance. + +Thereafter, either the timing advance in the mobile station is updated with a PACKET POWER CONTROL / TIMING ADVANCE message or a continuous timing advance procedure is used. If a Timing Advance Index is included in the assignment message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise the continuous timing advance procedure shall not be used. For the case where Timing Advance Value is not provided in the assignment message, the mobile station is not allowed to send normal bursts (e.g. PACKET DOWNLINK ACK/NACK message) on the uplink until it receives a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL / TIMING ADVANCE message. + +In the case of a mobile station with a Downlink Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1 (see sub-clause 5.5.1.7). If a mobile station with a Downlink Dual Carrier configuration receives an assignment message which results in the mobile station no longer being in a Downlink Dual Carrier configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned. + +The mobile station shall use information received on the PBCCH to decode the channel descriptions contained in the assignment. If frequency hopping is applied, the mobile station shall use the last CA received on PBCCH to decode the Mobile Allocation. Alternatively, the network may provide a Mobile Allocation in the assignment. The radio resource is assigned to the mobile station in a PACKET DOWNLINK ASSIGNMENT message. On receipt of a PACKET DOWNLINK ASSIGNMENT message, the mobile station shall switch to the assigned PDCHs. + +A PACKET DOWNLINK ASSIGNMENT message may indicate an assignment starting time in the TBF Starting Time parameter. The mobile station shall monitor PCCCH until the point in time denoted by the TBF Starting Time. If the mobile station receives more than one PACKET DOWNLINK ASSIGNMENT message while it monitors the PCCCH, it shall act upon the most recently received message and shall ignore the previous message. + +When the PACKET DOWNLINK ASSIGNMENT message is received and after awaiting the point in time denoted by the TBF Starting Time, if such is indicated, the mobile station shall switch to the assigned PDCHs and start timer T3190. The timer T3190 is restarted when receiving the first valid RLC data block addressed to the mobile station. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. + +When the mobile station switches to the assigned PDCHs, it shall take the power control parameters received in the PACKET DOWNLINK ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode or MAC-Shared state (see 3GPP TS 45.008). In the case of a mobile station with a Downlink Dual Carrier configuration, the power control parameters may be different for each of the two carriers. + +On expiry of timer T3190, the mobile station shall abort the procedure and return to packet idle mode or MAC-Idle state. + +### 7.2.1.2 Packet downlink assignment procedure completion + +The packet downlink assignment procedure is completed when the mobile station receives a valid RLC/MAC block. The mobile station has entered the packet transfer mode or MAC-Shared state. + +### 7.2.1.3 Packet polling procedure + +The network may send to the mobile station a PACKET POLLING REQUEST message. If the MS has received a PACKET DOWNLINK ASSIGNMENT message with no starting time or with a starting time that has already elapsed, the PACKET POLLING REQUEST message shall be sent on PACCH. Otherwise the PACKET POLLING REQUEST message shall be sent on PAGCH. The mobile station shall be addressed by its TLLI (*A/Gb mode*), G-RNTI (*Iu mode*) or TFI. + +On receipt of a PACKET POLLING REQUEST message, the mobile station shall respond to the network with the PACKET CONTROL ACKNOWLEDGEMENT message in the reserved uplink radio block specified by the RRBG field as defined in sub-clause 10.4.5. The reserved block is considered as a one block PACCH allocation. + +## 7.2.2 Abnormal cases + +If a failure occurs on the mobile station side of the new TBF before mobile station has successfully entered the packet transfer mode or MAC-Shared state, the newly reserved resources are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the mobile station has been assigned more PDCHs than it supports according to the relevant multislot configuration as defined in 3GPP TS 45.002, the mobile station shall return to packet idle mode or MAC-Idle state; +- If the mobile station has been assigned a TBF in EGPRS TBF mode and the MS does not support EGPRS, the MS shall return to packet idle mode or MAC-Idle state and notify higher layers (TBF establishment failure); +- On expiry of timer T3190, the mobile station shall return to packet idle mode or MAC-Idle state; +- If the failure is due to any other reason, the mobile station shall return to packet idle mode or MAC-Idle state and cell reselection continues. + +## 7.3 Procedure for measurement report sending in packet idle mode + +The procedure for measurement report sending shall be initiated by the mobile station at expiry of the NC measurement report interval timer T3158. At expiry of the timer T3158 the mobile station shall restart the expired timer T3158, perform the measurements and initiate the packet access. + +The procedure for measurement report sending is initiated by the mobile station either on PCCCH (sub-clause 7.3.1) or, if a packet control channel not exists, on CCCH (sub-clause 7.3.2). + +If the mobile station initiates the establishment of an RR connection, the timer T3158 shall be stopped and no measurement reports shall be sent. When the RR connection is released and if the mobile station has not changed cell, the measurement reporting procedure shall be restarted. + +If a cell change has occurred during the RR connection, the measurements shall be cancelled until new NC orders have been received (see sub-clause 5.6). + +### 7.3.1 Measurement report sending procedure initiated on PCCCH + +The packet access procedure is initiated by the RR entity in the mobile station as specified in sub-clauses 7.1.2.1 and 7.1.2.2 but with access type "Single block without TBF establishment" indicated in the PACKET CHANNEL REQUEST message. In the following sub-clauses the procedure is only briefly summarised and special requirements are indicated. + +#### 7.3.1.1 On receipt of a PACKET CHANNEL REQUEST message + +On receipt of a PACKET CHANNEL REQUEST message with access type indicating 'Single block without TBF establishment', the network may allocate one radio block on an uplink PDCH. + +If uplink resources are not available, the network may reject the access request by sending a PACKET ACCESS REJECT message (see sub-clause 7.3.1.3). The network shall not respond to a packet access for measurement reporting by sending a PACKET QUEUING NOTIFICATION message. + +The radio resource is assigned to the mobile station in a PACKET UPLINK ASSIGNMENT message sent on any PAGCH on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST message. The PACKET UPLINK ASSIGNMENT message shall include the following optional parameters: + +- Power Control Parameters with timeslot allocation; +- Frequency parameters; +- TBF\_STARTING\_TIME indicating the frame number of the allocated block; +- TIMING\_ADVANCE\_VALUE; +- Packet Request Reference. + +### 7.3.1.2 On receipt of a PACKET UPLINK ASSIGNMENT message + +When receiving a PACKET UPLINK ASSIGNMENT message the mobile station shall send either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message in the allocated radio block on the assigned PDCH and immediately switch back to the PCCCH in non-DRX mode (see sub-clause 5.5.1.5). No TBF is established and the network shall not acknowledge the reception of the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message. + +The PACKET MEASUREMENT REPORT message shall contain the NC Measurement Report struct. + +If timer T3170 expires before a PACKET UPLINK ASSIGNMENT message is received, the packet access procedure is aborted, the transmission of the measurement report for that measurement period is cancelled, and the mobile station shall indicate a random access failure to upper layer and perform autonomous cell re-selection. + +### 7.3.1.3 On receipt of a PACKET ACCESS REJECT message + +The network may send to the mobile station a PACKET ACCESS REJECT message. + +The mobile station shall react to this as described in sub-clause 7.1.2.2.4 with the exception of the actions taken when either of the timers T3172 or T3162 expires. In this case, the measurement report initiating the packet access shall be discarded and the mobile station shall return to packet idle mode or MAC-Idle state. + +If the measurement report interval timer T3158 expires before any of the timers T3172 or T3162 expires, no new measurement shall be initiated but the timer T3158 shall be restarted. + +### 7.3.1.4 Abnormal cases + +If the PACKET UPLINK ASSIGNMENT message contains faulty parameters, the mobile station shall abort the packet access procedure and return to packet idle mode or MAC-Idle state. The measurement report initiating the packet access shall be discarded. + +If the mobile station receives either a PACKET QUEUING NOTIFICATION message or a PACKET POLLING REQUEST message, the mobile station shall abort the packet access procedure and return to packet idle mode or MAC-Idle state. The measurement report initiating the packet access shall be discarded. + +## 7.3.2 Measurement report sending procedure initiated on CCCH + +For detailed description of the procedures following in this sub-clause, see 3GPP TS 44.018. The procedure is here only briefly summarised and special requirements are indicated. + +The packet access procedure is initiated by the RR entity in the mobile station. The mobile station sends a CHANNEL REQUEST message indicating 'Single block packet access' on RACH. The network shall then respond with either an IMMEDIATE ASSIGNMENT message granting a "single block access" on a PDCH or an IMMEDIATE ASSIGNMENT REJECT message (see 3GPP TS 44.018). + +If a PDCH block is assigned, the mobile station shall send either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message in the allocated radio block on the assigned PDCH and then immediately switch back to the CCCH in non-DRX mode (see sub-clause 5.5.1.5). No TBF is established and the network shall not acknowledge the reception of the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message. + +The PACKET MEASUREMENT REPORT message shall contain the NC Measurement Report struct. + +On receipt of an IMMEDIATE ASSIGNMENT REJECT message the mobile station shall follow the procedure specified in 3GPP TS 44.018 sub-clause 'Packet access rejection' with the exception of the actions taken when either of the 3GPP TS 44.018 timers T3142 or T3146 expires. In this case, the measurement report initiating the packet access shall be discarded and the mobile station shall return to packet idle mode. + +If the measurement report interval timer T3158 expires before any of the 3GPP TS 44.018 timers T3142 or T3146 expires, no new measurement shall be initiated but the timer T3158 shall be restarted. + +## 7.4 Cell Change Order procedures in Packet Idle mode + +For an individual mobile station in packet idle mode, the network may initiate the cell change order procedure either on PCCH or, if a packet control channel does not exist, on CCCH. + +### 7.4.1 Cell Change Order procedure initiated on PCCH + +The network may initiate the cell change order procedure by sending a PACKET CELL CHANGE ORDER message in a PCCH block monitored by the mobile station. No TBF shall be established. + +The PACKET CELL CHANGE ORDER message contains: + +- The characteristics of the new cell that are necessary to identify it (i.e. BSIC + BCCH frequency); +- The NC measurement parameters valid for the mobile station in the new cell (NETWORK\_CONTROL\_ORDER and optionally: NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T). + +For a multi-RAT mobile station supporting UTRAN, the PACKET CELL CHANGE ORDER message may contain information on a UTRAN target cell; in this case, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 25.331. + +For a multi-RAT mobile station supporting "CCN towards E-UTRAN, E-UTRAN Neighbour Cell measurement reporting and Network controlled cell reselection to E-UTRAN", the PACKET CELL CHANGE ORDER message may contain information on an E-UTRAN target cell; in this case, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 36.331. + +If the mobile station is not involved in an RR connection, upon receipt of the PACKET CELL CHANGE ORDER message, the mobile station shall stop all relevant RLC/MAC timers except for timers related to measurement reporting and start timer T3174. The mobile station shall then switch to the specified new cell and obey the relevant RLC/MAC procedures on this new cell. If a valid RRBP field was received in the PACKET CELL CHANGE ORDER message then the MS shall send a PACKET CONTROL ACKNOWLEDGMENT message in the reserved uplink radio block specified by the RRBP field before switching to the new cell. If the timers related to measurement reporting expire while the reselection procedure has not yet been completed, these timers shall be restarted so that the mobile station resumes the measurement reporting procedures once camped on the new cell. A UTRAN capable mobile station ordered to a UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 25.133 and 3GPP TS 25.123); an E-UTRAN capable mobile station ordered to an E-UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 36.133). + +If the mobile station is involved in an RR connection, the mobile station shall ignore the PACKET CELL CHANGE ORDER message. + +The procedure for completion of the cell change order is defined in sub-clause 8.4.1 and abnormal procedures are defined in sub-clause 8.4.2. + +### 7.4.2 Cell Change Order procedure initiated on CCCH + +The network may initiate the cell change order procedure by sending an IMMEDIATE ASSIGNMENT message for single block assignment in a CCCH block monitored by the mobile station. No TBF shall be established. The single block assignment procedure is specified in 3GPP TS 44.018. + +The network shall then send the PACKET CELL CHANGE ORDER message in the assigned downlink block to the mobile station. The PACKET CELL CHANGE ORDER message contains: + +- the characteristics of the new cell that are necessary to identify it (i.e. BSIC + BCCH frequency); +- the NC measurement parameters valid for the mobile station in the new cell (NETWORK\_CONTROL\_ORDER and optionally: NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T). + +For a multi-RAT mobile station supporting UTRAN, the PACKET CELL CHANGE ORDER message may contain information on a UTRAN target cell; in this case, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 25.331. + +For a multi-RAT mobile station supporting "CCN towards E-UTRAN, E-UTRAN Neighbour Cell measurement reporting and Network controlled cell reselection to E-UTRAN", the PACKET CELL CHANGE ORDER message may contain information on an E-UTRAN target cell; in this case, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 36.331. + +Upon receipt of the PACKET CELL CHANGE ORDER message, the mobile station shall stop all relevant RLC/MAC timers except for timers related to measurement reporting and start timer T3174. The mobile station shall then switch to the specified new cell and obey the relevant RLC/MAC procedures on this new cell. If a valid RRBG field was received in the PACKET CELL CHANGE ORDER message then the MS shall send a PACKET CONTROL ACKNOWLEDGMENT message in the reserved uplink radio block specified by the RRBG field before switching to the new cell. If the timers related to measurement reporting expire while the reselection procedure has not yet been completed, these timers shall be restarted so that the mobile station resumes the measurement reporting procedures once camped on the new cell. A UTRAN capable mobile station ordered to a UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether or not the target cell is known (see 3GPP TS 25.133 and 3GPP TS 25.123); an E-UTRAN capable mobile station ordered to an E-UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 36.133). + +The procedure for completion of the cell change order is defined in sub-clause 8.4.1 and abnormal procedures are defined in sub-clause 8.4.2. + +## 7.5 Measurement Order procedures in Packet Idle mode + +To send the NC Measurement order to an individual mobile station in packet idle mode, the network may establish a connection either on PCCCH or, if a packet control channel does not exist, on CCCH. + +### 7.5.1 Measurement Order procedures initiated on PCCCH + +The network may initiate the measurement order procedure by sending a PACKET MEASUREMENT ORDER message in a PCCCH block monitored by the mobile station. The PACKET MEASUREMENT ORDER message overrides a broadcast PSI5 message. If the PACKET MEASUREMENT ORDER message contains multiple instances, the network shall send all instances to the mobile station. + +The PACKET MEASUREMENT ORDER message may contain the following optional Measurement order parameters:- TLLI (shall be included in *A/Gb mode*); + +- G-RNTI (shall be included in *Iu mode*); +- Enhanced measurement parameters. + +Upon receipt of the PACKET MEASUREMENT ORDER message, the mobile station shall store the Measurement order parameters. The mobile station shall obey the NETWORK\_CONTROL\_ORDER as specified in 3GPP TS 45.008 and in sub-clause 5.6. + +### 7.5.2 Measurement Order procedures initiated on CCCH + +The network may initiate the measurement order procedure by allocating a single block in an IMMEDIATE ASSIGNMENT message sent to the mobile station on a CCCH block in the same way as specified in sub-clause 7.4.2. + +The network shall then send the PACKET MEASUREMENT ORDER message in the assigned downlink block to the mobile station. The PACKET MEASUREMENT ORDER message overrides a broadcast PSI5 message. If the PACKET MEASUREMENT ORDER message contains multiple instances, the network has to repeat the complete procedure with new assignment for each instance of the message. + +The PACKET MEASUREMENT ORDER message may contain the following optional Measurement order parameters: + +- TLLI (shall be included); +- NC Measurement Parameters (NETWORK\_CONTROL\_ORDER; NC\_NON\_DRX\_PERIOD; NC\_REPORTING\_PERIOD\_I; NC\_REPORTING\_PERIOD\_T; NC\_FREQUENCY\_LIST); +- Enhanced measurement parameters. + +Upon receipt of the PACKET MEASUREMENT ORDER message, the mobile station shall store the Measurement order parameters . The mobile station shall obey the NETWORK\_CONTROL\_ORDER as specified in 3GPP TS 45.008 and in sub-clause 5.6. + +## 7.6 Packet Pause procedure + +This procedure enables the network to pause GPRS services packet flow for a mobile station with non-GSM capabilities in the downlink direction. The procedure is initiated by the mobile station either on a PCCCH (sub-clause 7.6.1) or, if a packet control channel does not exist, on a CCCH (sub-clause 7.6.2). + +### 7.6.1 Packet pause procedure initiated on PCCCH + +The packet access procedure is initiated by the RR entity in the mobile station as specified in sub-clauses 7.1.2.1 and 7.1.2.2 but with access type 'Single block without TBF establishment' indicated in the PACKET CHANNEL REQUEST message. + +#### 7.6.1.1 On receipt of a PACKET CHANNEL REQUEST message + +On receipt of a PACKET CHANNEL REQUEST message with access type indicating "Single block without TBF establishment", the network may allocate one radio block on an uplink PDCH. + +If uplink resources are not available, the network may reject the access request by sending a PACKET ACCESS REJECT message (see sub-clause 7.6.1.3). The network shall not respond by sending a PACKET QUEUING NOTIFICATION message. + +The radio resource is assigned to the mobile station in a PACKET UPLINK ASSIGNMENT message sent on any PAGCH on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST message. The PACKET UPLINK ASSIGNMENT message shall include the following optional parameters: + +- Power Control Parameters with timeslot allocation; +- Frequency parameters; +- TBF\_STARTING\_TIME indicating the frame number of the allocated block; +- TIMING\_ADVANCE\_VALUE; +- Packet Request Reference. + +#### 7.6.1.2 On receipt of a PACKET UPLINK ASSIGNMENT message + +When receiving a PACKET UPLINK ASSIGNMENT message the mobile station shall send PACKET PAUSE in the allocated radio block on the assigned PDCH. The mobile station shall stop timer T3204. No TBF is established and the network shall not acknowledge the reception of the PACKET PAUSE message. + +If timer T3204 expires before a PACKET UPLINK ASSIGNMENT message is received, the packet pause procedure is aborted. + +#### 7.6.1.3 On receipt of a PACKET ACCESS REJECT message + +The network may send to the mobile station a PACKET ACCESS REJECT message. The mobile station shall react by aborting the packet pause procedure and stopping timer T3204. + +#### 7.6.1.4 Abnormal cases + +If on the mobile station side timer T3204 expires indicating unsuccessful channel request procedure or if the PACKET UPLINK ASSIGNMENT message contains faulty parameters, the mobile station shall abort the packet pause procedure. + +If the mobile station receives either a PACKET QUEUING NOTIFICATION message or a PACKET POLLING REQUEST message, the mobile station shall abort the packet pause procedure. + +## 7.6.2 Packet pause procedure initiated on CCCH + +For a description of the procedure, see 3GPP TS 44.018. + +# 7.7 MBMS packet access and establishment procedures + +## 7.7.1 MBMS packet access procedure + +### 7.7.1.1 General + +This procedure enables the network to count the number of mobile stations in a cell that want to receive an MBMS session. If the procedure is initiated by the mobile station as a response to an MBMS notification, which contains uplink resource description for an MPRACH, or after cell reselection during an ongoing MBMS session, if the mobile station is in DRX mode (e.g. it is not involved in a *routeing area update* procedure) and has received in the old serving cell the indication that in the new cell an MPRACH is allocated for that MBMS session, the procedure shall be initiated on that MPRACH (sub-clause 7.7.1.4). Otherwise the procedure is initiated by the mobile station either on a PCCCH (sub-clause 7.7.1.2) or, if a packet control channel is not allocated in the cell, on a CCCH (sub-clause 7.7.1.3). + +The procedure may be initiated by the mobile station either: + +- as a response to an MBMS notification where counting is requested; or +- in the new cell after cell reselection during an ongoing MBMS session, if MBMS is supported by the network in the new cell; or +- when a request is received from upper layer in the mobile station, if MBMS is supported by the network in the cell; or +- after timeout when waiting for an RLC block for this session. + +NOTE: The mobile station shall not initiate an MBMS packet access procedure in a new cell after cell reselection if the mobile station already has information about the location and identifier of the MBMS radio bearer relevant to the ongoing MBMS session in that new cell and it contains no uplink feedback channel. + +A mobile station that is IMSI attached (GPRS class A or B mode of operation) shall respond to a PACKET PAGING REQUEST message indicating an RR connection establishment or TBF establishment. For that purpose, the mobile station shall abort the MBMS packet access procedure, according to the conditions stated in sub-clause 6.1.4. + +If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall abort the MBMS packet access procedure and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1) + +### 7.7.1.2 MBMS packet access procedure on PCCCH + +#### 7.7.1.2.0 Initiation of the MBMS packet access procedure + +The packet access procedure for an MBMS session is initiated by the mobile station on PCCCH, as specified in sub-clauses 7.1.2.1 with access type "Single block MBMS access" indicated in the PACKET CHANNEL REQUEST message. + +##### 7.7.1.2.1 On receipt of a PACKET CHANNEL REQUEST message + +On receipt of a PACKET CHANNEL REQUEST message with access type indicating "Single block MBMS access", the network may either allocate one radio block on an uplink PDCH, as specified in sub-clause 7.1.2.1 or, if uplink resources are not available, reject the access request by sending a PACKET ACCESS REJECT message (see sub-clause 7.7.1.2.3). + +The radio resource is assigned to the mobile station in a PACKET UPLINK ASSIGNMENT message sent on any PAGCH on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST message. The PACKET UPLINK ASSIGNMENT message shall include the following optional parameters: + +- Power Control Parameters with timeslot allocation; +- Frequency parameters; + +- TBF\_STARTING\_TIME indicating the frame number of the allocated block; +- TIMING\_ADVANCE\_VALUE; +- Packet Request Reference. + +#### 7.7.1.2.2 On receipt of a PACKET UPLINK ASSIGNMENT message + +When receiving a PACKET UPLINK ASSIGNMENT message, corresponding to one of its 3 last PACKET CHANNEL REQUEST messages, the mobile station shall send the MBMS SERVICE REQUEST message in the allocated radio block on the assigned PDCH and then start timer T3214. While timer T3214 is running the mobile station shall accept reception of repeated PACKET UPLINK ASSIGNMENT messages, on any PAGCH on the same PCCCH on which the mobile station has sent the PACKET CHANNEL REQUEST message, and re-send the MBMS SERVICE REQUEST in the allocated block on the assigned PDCH and restart the timer T3214. + +At expiry of timer T3214, a mobile station in packet idle mode or MAC-Idle state shall return to DRX mode. No radio bearer will be established in the cell for the concerned MBMS session. A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode. + +#### 7.7.1.2.3 On receipt of a PACKET ACCESS REJECT message + +The network may send a PACKET ACCESS REJECT message to the mobile station in response to a PACKET CHANNEL REQUEST message. The mobile station shall then react as described in sub-clause 7.1.2.2.4. + +#### 7.7.1.2.4 On receipt of an MBMS ASSIGNMENT message + +When the mobile station receives an MBMS ASSIGNMENT message for an MBMS session, it shall stop any ongoing packet access procedure for that MBMS session and proceed according to sub-clause 7.7.2.2. + +#### 7.7.1.2.5 Abnormal cases + +If the mobile station receives a PACKET UPLINK ASSIGNMENT message that contains faulty parameters, the mobile station shall abort the MBMS packet access procedure. + +### 7.7.1.3 MBMS packet access procedure on CCCH + +For a description of the procedure, see 3GPP TS 44.018. + +### 7.7.1.4 MBMS packet access procedure on MPRACH + +#### 7.7.1.4.1 Initiation of the MBMS packet access procedure on MPRACH + +The mobile station initiates the MBMS packet access procedure on MPRACH by sending an MPRACH PACKET CHANNEL REQUEST message (see sub-clause 11.2.5c) with access type "Single block MBMS access" on the MPRACH. + +The mobile station shall determine the control parameters from the MPRACH control parameters included in the MBMS notification or in the MBMS NEIGHBOURING CELL INFORMATION message transmitted in the old serving cell, if present. If an MPRACH control parameter is not available, the last received corresponding control parameter for the PRACH, if PCCCH is present, shall be used; otherwise the last received corresponding control parameter for the RACH shall be used. + +At sending of the first MPRACH PACKET CHANNEL REQUEST message, the mobile station shall store the value for the Retry (R) bit to be transmitted in all the subsequent MAC headers as 'MS sent channel request message once'. If a second MPRACH PACKET CHANNEL REQUEST message is sent, the mobile station shall change the value for the Retry (R) bit to 'MS sent channel request message twice or more'. + +While waiting for a response to the MPRACH PACKET CHANNEL REQUEST message the mobile station shall continue to monitor the CCCH/PCCCH (whichever is applicable) corresponding to its CCCH\_GROUP/PCCCH\_GROUP. The mobile station shall perform signal strength measurements as they are defined for packet idle mode, see 3GPP TS 45.008. + +A mobile station that is IMSI attached (GPRS class A or B mode of operation) shall respond to a PACKET PAGING REQUEST message indicating an RR connection establishment. For that purpose, the mobile station may abort the + +packet access procedure, according to the conditions stated in sub-clause 6.1.4. The mobile station shall not respond to a PACKET PAGING REQUEST message indicating TBF establishment. + +A mobile station that is not IMSI attached (GPRS class C mode of operation) shall not respond to any type of PACKET PAGING REQUEST messages during the packet access procedure, it shall only decode the PERSISTENCE\_LEVEL parameter, if that is included in the message. + +#### 7.7.1.4.1.1 Access persistence control on MPRACH + +The mobile station shall make maximally $M + 1$ attempts to send an MPRACH PACKET CHANNEL REQUEST message. + +The mobile station shall use the control parameters determined by the procedure described in sub-clause 7.7.1.4.1: + +- MAX\_RETRANS; +- PERSISTENCE\_LEVEL, which consists of the PERSISTENCE\_LEVEL $P \in \{0, 1, \dots, 14, 16\}$ . If the control parameters do not contain the PERSISTENCE\_LEVEL parameter, this shall be interpreted as if $P = 0$ ; +- S; +- TX\_INT. + +The mobile station shall start timer T3186 at the beginning of the MPRACH packet access procedure. At expiry of timer T3186, the MPRACH packet access procedure shall be aborted, and: + +- if at least one MPRACH PACKET CHANNEL REQUEST message was transmitted by the mobile station, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022; +- otherwise, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state. + +The first attempt to send an MPRACH PACKET CHANNEL REQUEST message may be initiated at the first available MPRACH block on the indicated PDCH. The mobile station shall choose one of the four TDMA frames within the selected MPRACH block randomly with a uniform probability distribution. + +For each attempt, the mobile station shall draw a random value $R$ with uniform probability distribution in the set $\{0, 1, \dots, 15\}$ . The mobile station is allowed to transmit an MPRACH PACKET CHANNEL REQUEST message if $P$ is less than or equal to $R$ . + +After each attempt, the $S$ and $T$ parameters are used to determine the next TDMA frame in which it may be allowed to make a successive attempt. The number of TDMA frames, belonging to the MPRACH on the indicated PDCH, between two successive attempts to send an MPRACH PACKET CHANNEL REQUEST message, excluding the TDMA frames potentially containing the messages themselves, is a random value drawn for each transmission, with uniform probability distribution, in the set $\{S, S + 1, \dots, S + T - 1\}$ ; + +Here: + +$M$ is the value of the parameter MAX\_RETRANS; + +$T$ is the value of the parameter TX\_INT; + +$S$ is the value of the parameter $S$ . + +Having made $M + 1$ attempts to send an MPRACH PACKET CHANNEL REQUEST message, the mobile station shall stop timer T3186 and start timer T3170 if at least one MPRACH PACKET CHANNEL REQUEST message was transmitted by the mobile station. In this case, at expiry of timer T3170, the packet access procedure shall be aborted, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022. Otherwise, the packet access procedure shall be aborted, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state. + +If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message while it is waiting for a response to an MPRACH PACKET CHANNEL REQUEST message, it shall abort the MBMS packet access procedure on MPRACH and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1). + +#### 7.7.1.4.2 On receipt of an MPRACH PACKET CHANNEL REQUEST + +On receipt of an MPRACH PACKET CHANNEL REQUEST message with access type indicating "Single block MBMS access", the network shall either allocate one radio block on an uplink PDCH by sending a PACKET UPLINK ASSIGNMENT message on the downlink PDCH corresponding to the uplink PDCH where the MPRACH is allocated or, if uplink resources are not available, reject the access request by sending a PACKET ACCESS REJECT message on the same downlink PDCH (see sub-clause 7.7.1.4.3). + +The PACKET UPLINK ASSIGNMENT message shall include the optional parameters: + +- Power Control Parameters with timeslot allocation; +- Frequency parameters; +- TBF\_STARTING\_TIME indicating the frame number of the allocated block; +- TIMING\_ADVANCE\_VALUE; +- Packet Request Reference. + +#### 7.7.1.4.3 On receipt of a PACKET ACCESS REJECT message + +The network may, as response to an MPRACH PACKET CHANNEL REQUEST message, send to the mobile station a PACKET ACCESS REJECT message on the downlink PDCH corresponding to the uplink PDCH where the MPRACH is allocated. This message contains the request reference with time of reception of the MPRACH PACKET CHANNEL REQUEST message and optionally a WAIT\_INDICATION field in the Reject structure of the PACKET ACCESS REJECT message. + +On receipt of a PACKET ACCESS REJECT message containing a Reject structure addressed to the mobile station, where the Packet Request Reference in the Reject structure corresponds to one of its 3 last MPRACH PACKET CHANNEL REQUEST messages: + +- The mobile station shall stop timer T3186, stop sending MPRACH PACKET CHANNEL REQUEST messages, start timer T3172 with the value indicated in the WAIT\_INDICATION field, start timer T3170 if it has not already been started and listen to the downlink PCCCH until timer T3170 expires. During this time, the mobile station shall ignore additional PACKET ACCESS REJECT messages. During this time, on reception of any PACKET UPLINK ASSIGNMENT message corresponding to any other of its 3 last MPRACH PACKET CHANNEL REQUEST messages, the mobile station shall stop timers T3170 and T3172 if running, and follow the procedure defined in sub-clause 7.1.2.2.1b; +- If no PACKET UPLINK ASSIGNMENT message is received before expiration of timer T3170, the mobile station shall indicate a packet access failure to upper layer and return to packet idle mode (listening to its paging channel). As an option the mobile station may stop timer T3170, indicate a packet access failure to upper layer and return to packet idle mode as soon as it has received responses from the network on all or, in case more than 3 were sent, the last 3 of its MPRACH PACKET CHANNEL REQUEST messages. If the mobile station is already engaged in a parallel broadcast/multicast session the mobile station shall remain in broadcast/multicast receive mode; +- If an erroneous PACKET UPLINK ASSIGNMENT message (e.g. the mobile station has been assigned more PDCHs than it supports according to the relevant multislot configuration as defined in 3GPP TS 45.002) addressed to the mobile station is received before expiration of timer T3170, the mobile station shall stop T3170 and act as stated in sub-clause 7.1.4; +- If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall stop timer T3170 if running and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1); +- The mobile station is not allowed to make a new attempt for packet access in the same cell until timer T3172 expires, but may attempt packet access in another cell after successful cell reselection for radio conditions reasons (see 3GPP TS 45.008). In *A/Gb mode*, a mobile station that is IMSI attached (GPRS class A or B mode of operation) may attempt to enter the dedicated mode in the same cell before timer T3172 has expired. During the time T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging requests sent to trigger RR connection establishment and paging requests sent to trigger the acquisition of an ETWS Primary Notification message; +- The value of the WAIT\_INDICATION field (i.e. timer T3172) relates to the cell from which it was received. + +#### 7.7.1.4.4 On receipt of a PACKET UPLINK ASSIGNMENT message + +On receipt of a PACKET UPLINK ASSIGNMENT message corresponding to one of its 3 last MPRACH PACKET CHANNEL REQUEST messages the mobile station shall stop timers T3186 and T3170 if running and stop sending MPRACH PACKET CHANNEL REQUEST messages. The mobile station shall send the MBMS SERVICE REQUEST message in the allocated radio block on the assigned PDCH and then start timer T3214. While timer T3214 is running the mobile station shall accept reception of repeated PACKET UPLINK ASSIGNMENT messages, on the downlink PDCH corresponding to the uplink PDCH where the MPRACH is allocated, and re-send the MBMS SERVICE REQUEST in the allocated block on the assigned PDCH and restart the timer T3214. + +At expiry of timer T3214, a mobile station in packet idle mode or MAC-Idle state shall return to DRX mode and shall consider the MBMS radio bearer as not established in the cell for the concerned MBMS session. A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode. + +#### 7.7.1.4.5 On receipt of an MBMS ASSIGNMENT message + +When the mobile station receives an MBMS ASSIGNMENT message for an MBMS session, it shall stop any ongoing packet access procedure for that MBMS session and proceed according to sub-clause 7.7.2.2. + +### 7.7.2 Establishment of MBMS bearer + +#### 7.7.2.1 General + +The network may send an MBMS ASSIGNMENT message to the mobile station(s) in order to inform about the establishment of a radio bearer for an MBMS session in the cell or to notify the mobile station(s) that a radio bearer for that MBMS session is not established in the cell. The decision of whether to establish a radio bearer for an MBMS session in a cell is a network dependent choice. + +If the network sends the MBMS ASSIGNMENT message subsequent to an MBMS Notification for the same MBMS session, the MBMS ASSIGNMENT message shall be sent on any PAGCH on the same PCCCH on which the network has sent the MBMS Notification or, if a packet control channel does not exist, the IMMEDIATE ASSIGNMENT message including the *Multiple Blocks Packet Downlink Assignment* construction shall be sent on any AGCH on the same CCCH on which the network has sent the MBMS Notification, followed by the MBMS ASSIGNMENT message sent on the PDCH specified by the *Packet Channel Description* IE in the IMMEDIATE ASSIGNMENT message (see 3GPP TS 44.018). + +In case the network sends the MBMS ASSIGNMENT message in response to an MBMS SERVICE REQUEST message which is not sent as a response to an MBMS Notification, the MBMS ASSIGNMENT message shall be sent either: + +- on the PCCCH corresponding to the mobile station PCCCH\_GROUP, if the mobile station initiated the MBMS packet access procedure on the MPRACH, or +- on any PAGCH on the same PCCCH on which the mobile station sent the PACKET CHANNEL REQUEST message with access type "Single block MBMS access" or, +- if a packet control channel does not exist, the IMMEDIATE ASSIGNMENT message including the *Multiple Blocks Packet Downlink Assignment* construction shall be sent on the CCCH corresponding to the mobile station CCCH\_GROUP, if the mobile station initiated the MBMS packet access procedure on the MPRACH, or on any AGCH on the same CCCH on which the mobile station sent the CHANNEL REQUEST message with access type "Single block MBMS access", followed by the MBMS ASSIGNMENT message sent on the PDCH specified by the *Packet Channel Description* IE in the IMMEDIATE ASSIGNMENT message (see 3GPP TS 44.018). + +#### 7.7.2.2 On receipt of an MBMS ASSIGNMENT message + +On reception of the MBMS ASSIGNMENT message the mobile station shall stop timer T3214 if running and enters broadcast/multicast receive mode. + +If the MBMS ASSIGNMENT message indicates that a radio bearer is established for the MBMS session in the cell, and thus contains an MBMS bearer description, the mobile station shall set and start the session duration timer for this MBMS session with a value equal to the Estimated Session Duration and shall listen to downlink RLC blocks identified by the assigned MBMS Bearer Identity value on the defined PDCHs. The network may assign a radio resource on one or more PDCHs to be used for the radio bearer. The amount of radio resource to be reserved is a network dependent + +choice and shall not exceed the multislot capability of an MBMS capable mobile station (see 3GPP TS 45.002). The MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT message indicates whether or not the network shall send system information messages and (for mobile stations with an assigned MS\_ID on that MBMS radio bearer) paging messages on the PACCH of the MBMS radio bearer. + +The MBMS bearer description may indicate an MBMS radio bearer starting time. If the mobile station receives the MBMS ASSIGNMENT message before the MBMS radio bearer starting time has expired, it shall wait until the point in time denoted by the MBMS radio bearer starting time, leave non-DRX mode, switch to the assigned PDCHs and start timer T3190. If the mobile station receives the MBMS ASSIGNMENT message after the MBMS radio bearer starting time has expired, it shall ignore the indicated MBMS radio bearer starting time, leave non-DRX mode, immediately switch to the assigned PDCHs and start timer T3190. If the mobile station receives an MBMS ASSIGNMENT message including an MBMS bearer description without an MBMS radio bearer starting time, it shall leave non-DRX mode, immediately switch to the assigned PDCHs and start timer T3190. The timer T3190 is restarted when receiving the first valid RLC data block including the assigned MBMS Bearer Identity. On expiry of timer T3190, the mobile station shall abort the procedure and repeat the MBMS packet access procedure for the MBMS session. + +If the mobile station receives more than one MBMS ASSIGNMENT message while it monitors the PCCH or, if a packet control channel does not exist, the CCCH (see 3GPP TS 44.018), it shall act upon the most recently received message and shall ignore the previous message. + +If the MBMS ASSIGNMENT message indicates that no radio bearer is established for the MBMS session in the cell, the mobile station shall act according to the indication in the Reject cause. + +- If the cause value indicates that further MBMS packet accesses are allowed for this MBMS session in the same cell, as long as the session duration timer for this MBMS session in the mobile station is still running, the mobile station may perform more access attempts for the current MBMS session in this cell or in any other cell where MBMS is supported by the network; +- If the cause value indicates that no further MBMS packet accesses are allowed for this MBMS session in the same cell, the mobile station shall not perform any further access attempts for the current MBMS session in this cell. As long as the session duration timer for this MBMS session in the mobile station is still running, the mobile station may perform access attempts for the MBMS session in any other cell to which the mobile station has performed cell reselection, if MBMS is supported by the network in that cell; +- If the cause value indicates that no further MBMS packet accesses are allowed for this MBMS session in the same Routing Area, the mobile station shall not perform any further access attempts for the current MBMS session in this Routing Area. As long as the session duration timer for this MBMS session in the mobile station is still running, the mobile station may perform access attempts for the MBMS session in any other cell, in any other Routing Area, to which the mobile station has performed cell reselection, if MBMS is supported by the network in that cell; +- If the cause value indicates that no further MBMS packet accesses are allowed for this MBMS session in this PLMN, the mobile station shall not perform any further access attempts for the MBMS session. + +When the session duration timer for the MBMS session in the mobile station expires, the mobile station shall no longer perform access attempts for that MBMS session in any cell and shall indicate to the upper layers the end of the MBMS session. + +Independent on the Reject cause value received and on the expiry of the session duration timer for the MBMS session, the mobile station may always perform new MBMS packet accesses for the MBMS session if a new MBMS Notification addressing that MBMS session, and indicating that counting shall be performed, is received. + +In case the network sends the MBMS ASSIGNMENT message in response to an MBMS SERVICE REQUEST message which is not sent as a response to an MBMS Notification, and the MBMS ASSIGNMENT message contains the MBMS bearer description and an uplink feedback channel is used, then the network may include the TLLI of the mobile station, the MS\_ID and the timing advance parameters in the MBMS ASSIGNMENT message. If no MS\_ID identifier is available on the network side, the network notifies the mobile station of the lack of an MS\_ID identifier, preventing the mobile station from repeating the MBMS packet access procedure in this cell. + +### 7.7.2.3 Abnormal cases + +If on the mobile station side timer T3214 expires indicating that no MBMS bearer will be established for the specific MBMS session in the cell or if the MBMS ASSIGNMENT message contains faulty parameters, the mobile station shall abort the MBMS packet access procedure. + +### 7.7.2.4 MBMS address assignment procedure + +In case an uplink feedback channel is associated to an established MBMS radio bearer, then the network may assign an MS\_ID to a given mobile station receiving this MBMS radio bearer by sending an MBMS MS\_ID ASSIGNMENT message including the MS\_ID and the timing advance parameters assigned to the mobile station. The mobile station shall be addressed by its TLLI. This message shall not be sent before the point in time denoted by the MBMS radio bearer starting time, if present in the previous MBMS ASSIGNMENT message. + +On a given PDCH a mobile station having been assigned an MS\_ID is identified with a TFI value including the MBMS Bearer Identity (in the most significant bit(s) of the TFI field) and the MS\_ID (in the remaining least significant bit(s) of the TFI field). + +The mobile station shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified if a valid RRBP field is received as part of the MBMS MS\_ID ASSIGNMENT message. The network shall reset counter N3109 for that MS\_ID on that MBMS radio bearer when transmitting for the first time the MBMS MS\_ID ASSIGNMENT message including a polling request. If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the specified radio block, it shall increment counter N3109 for that MS\_ID and may retransmit the MBMS MS\_ID ASSIGNMENT message. If N3109 = N3109\_MAX, the network shall start timer T3199 for that MS\_ID. While T3199 is running for a given MS\_ID and MBMS radio bearer, the network shall not use that MS\_ID in any RLC/MAC block belonging to that MBMS radio bearer. When timer T3199 expires, the network may reuse the corresponding MS\_ID value for that MBMS radio bearer. + +An initial timing advance value may be provided in the MBMS ASSIGNMENT message or in the MBMS MS\_ID ASSIGNMENT message in the *Packet Timing Advance* IE. Thereafter either the timing advance is updated with a PACKET POWER CONTROL/TIMING ADVANCE message or the continuous timing advance procedure is used. If timing advance timeslot number and index are provided in the MBMS ASSIGNMENT message or in the MBMS MS\_ID ASSIGNMENT message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise, the continuous timing advance procedure shall not be used. For the case where the timing advance value is not provided in the MBMS ASSIGNMENT message or in the MBMS MS\_ID ASSIGNMENT message, the mobile station is not allowed to send normal bursts (e.g. (EGPRS) PACKET DOWNLINK ACK/NACK message) on the uplink until it has received a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL/TIMING ADVANCE message. + +If the mobile station has been assigned an MS\_ID in the MBMS ASSIGNMENT message before the point in time denoted by the MBMS radio bearer starting time, if present in the MBMS ASSIGNMENT message, the mobile station shall switch to the assigned PDCH(s) at the point in time denoted by the MBMS radio bearer starting time and start timers T3190 and T3290. If the MBMS radio bearer starting time has already expired or has not been included in the MBMS ASSIGNMENT message including the MS\_ID, the mobile station shall switch to the assigned PDCH(s) within the reaction time defined in 3GPP TS 45.010 and start timers T3190 and T3290. If the mobile station is assigned an MS\_ID in the MBMS MS\_ID ASSIGNMENT message, the mobile station shall start timer T3290 within the reaction time defined in 3GPP TS 45.010. The mobile station shall restart timer T3190 whenever receiving an RLC/MAC block including the assigned MBMS Bearer Identity. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. The mobile station with an assigned MS\_ID value shall restart timer T3290 whenever receiving an RLC/MAC block including the corresponding MBMS Bearer Identity and the MS\_ID in the TFI field. + +### 7.7.3 MBMS Neighbour Cell Information Distribution + +The network shall indicate in GPRS Cell Options IE whether it supports the distribution of MBMS NEIGHBOURING CELL INFORMATION messages (see sub-clause 12.24). + +The network may send MBMS neighbour cell information to a mobile station during MBMS reception using the MBMS NEIGHBOURING CELL INFORMATION message on the PACCH. A mobile station, which receives this information, shall store the MBMS data channel information until refreshing or until the end of the MBMS session. During that period the information can be used for fast resumption of the MBMS reception in the neighbour cell (see sub-clause 8.1.6.2). + +The MS shall only combine information received in several instances of the MBMS NEIGHBOURING CELL INFORMATION messages that have the same value of the MBMS\_PTM\_CHANGE\_MARK specified for a neighbouring cell. + +In case the target cell has PBCCH allocated, this information shall be included in the MBMS NEIGHBOURING CELL INFORMATION message, if the PBCCH parameters can be encoded via the means provided in the message. If present, + +the MS shall use this information in order to avoid BCCH decoding, if not otherwise necessary unless the PBCCH location is known via PSI3 and PSI3bis messages, in the target cell. + +In case in the target cell an MPRACH is allocated on the uplink feedback channel of an MBMS radio bearer, this information shall be included in the MBMS NEIGHBOURING CELL INFORMATION message. + +--- + +## 7a Medium Access Control (MAC) procedures for EC-GSM-IoT on (EC-)CCCH + +### 7a.1 General + +The establishment of an EC Temporary Block Flow (EC TBF), for a mobile station that has enabled EC operation, is performed on the EC-CCCH. It can be initiated by either the mobile station or the network. The establishment of an EC TBF can also be performed on the CCCH if the mobile station has selected Coverage Class 1 in both the uplink and downlink directions, see 3GPP TS 45.008 and 3GPP TS 44.018, and is allowed to use the CCCH for its packet access procedure. The request for establishment of an EC TBF on the EC-CCCH or on the CCCH is described in 3GPP TS 44.018. + +Establishment of an EC TBF in the direction from the mobile station to the network can also be initiated using the EC-PACCH if an EC TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station is already established (see sub-clause 9.3.2.6). Establishment of an EC TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station can also be done on the EC-PACCH if an EC TBF in the direction from the mobile station to the network has been released with an EC PACKET UPLINK ACK/NACK message indicating that the mobile station shall continue to monitor the EC-PACCH for a limited time (see sub-clause 9.3.2.4.3). + +### 7a.2 TBF establishment initiated by the mobile station for EC-GSM-IoT on (EC-)CCCH + +The packet access procedure using the EC-CCCH or the CCCH wherein a mobile station is assigned an uplink EC TBF using fixed uplink allocation (see sub-clause 8.1.1.3b) is described in 3GPP TS 44.018. + +The following sub-clauses describe the contention resolution procedure and the timing advance handling at the establishment of an EC TBF for a mobile station that has enabled EC operation. + +#### 7a.2.1 Contention Resolution + +The TLLI is used to uniquely identify the mobile station when sending on the uplink. A mobile station, that has enabled EC operation, includes its TLLI in one or several of the uplink blocks that are transmitted during the establishment of an EC TBF, depending on what packet access procedure is used. + +The contention resolution is described for the different packet access procedures in the following sub-clauses: + +- using Access Burst procedure, with inclusion of the full TLLI in each RLC data block that is sent on the TBF until contention resolution is completed, described in 7a.2.1.1; +- using Enhanced Access Burst procedure, with inclusion of the full TLLI in only the first RLC data block that is sent on the TBF and then inclusion of a limited part of the TLLI in the subsequent RLC data blocks that are sent until contention resolution is completed, described in 7a.2.1.2. + +The network indicates in the EC Immediate Assignment message which of the procedures that shall be used for the contention resolution, see 3GPP TS 44.018. + +##### 7a.2.1.1 Contention resolution at packet access procedure using Access Burst procedure + +Every RLC data block that is sent on the TBF shall include the TLLI of the mobile station, until the contention resolution is completed on the mobile station side. If MCS-7, MCS-8 or MCS-9 is used for the transmission of the TLLI (i.e. the RLC/MAC block is carrying two RLC data blocks), the TLLI shall be inserted in both RLC data blocks. + +The retransmission of an RLC data block shall include the TLLI, if the RLC data block was originally transmitted including the TLLI, also if the retransmission occurs after the completion of the contention resolution. + +After the last allocated RLC data block has been transmitted according to the initial fixed uplink allocation (received in the EC Immediate Assignment message), the mobile station shall start timer T3226. When timer T3226 expires the mobile station shall start timer T3228 and start continuously monitoring the EC-PACCH for reception of an RLC/MAC control message, see sub-clause 8.1.1.3b. + +When the network has correctly received an RLC data block that comprises the TLLI, it shall include the TLLI in an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message that it sends to the mobile station (i.e. to allow for contention resolution on the mobile station side). The network may, after successful reception of the TLLI, include the reduced TLLI (rTLLI) of the mobile station in an EC PACKET UPLINK ACK/NACK message that it sends to the mobile station. The rTLLI consists of the 4 least significant bits of the TLLI of the mobile station. + +After the last allocated RLC data block of a fixed uplink allocation, the network shall start timer T3227. The mobile station is only reachable on the EC-PACCH once timer T3227 has expired. When timer T3227 expires, the network shall start timer T3229 and send the EC PACKET UPLINK ACK/NACK or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station. The network may send additional EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages to the mobile station while timer T3229 is running. The network should then however take into account that the mobile station will stop monitoring the EC-PACCH at reception of a matching EC PACKET UPLINK ACK/NACK or a matching EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message containing a fixed uplink allocation. If the network receives uplink data from the mobile station, on the resources that are part of the fixed uplink allocation, the network shall stop timer T3229, if running. + +If timer T3249 is not used, i.e. it has the value 0, the network may release the TBF and reuse the TFI resource when timer T3229 has expired and no uplink data has been received in a fixed uplink allocation sent to the mobile station in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages before expiry of timer T3229. If timer T3249 is used, i.e. it has a value $> 0$ , it shall be started at expiry of T3229. The network may send EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages to the mobile station using the next higher DL Coverage Class, compared to the last assigned DL Coverage Class, while T3249 is running, see sub-clause 8.1.1.3b. When timer T3249 has expired and no uplink data has been received in a fixed uplink allocation allocated to the mobile station in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages before expiry of timer T3249 (or preceding T3229), the network may release the TBF and reuse the TFI resource. + +The contention resolution is completed on the network side when the network receives an RLC data block that comprises the TLLI value that identifies the mobile station and the TFI value associated with the TBF. + +When the mobile station receives an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with the uplink TBF, the mobile station shall stop timer T3228, if running, and act on the received message, unless it included a TLLI value other than that the mobile station included in the RLC header of the RLC data blocks sent during the initial fixed uplink allocation or an rTLLI value which does not consist of the 4 least significant bits of the TLLI. If timer T3248 was running at reception of the EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message (and thus not T3228), the timer T3248 shall be stopped. + +The contention resolution is successfully completed on the mobile station side when the mobile station receives an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with the uplink TBF and including the same TLLI value that the mobile station has included in the RLC header of the RLC data blocks sent during the initial fixed uplink allocation. The TLLI shall thus be included in all RLC data blocks that are sent as part of the initial fixed uplink allocation. + +The mobile station has entered the packet transfer mode upon a successful contention resolution. + +The contention resolution has failed on the mobile station side when timer T3228 expires, if timer T3248 (sent in EC SI) is not used. If timer T3248 is used, i.e. it has a value $> 0$ , it shall be started when timer T3228 expires. The contention resolution has failed on the mobile station side when timer T3248 expires. The contention resolution also fails, if the mobile station receives an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI associated with the uplink TBF and including a TLLI value other than that the mobile station included in the RLC header of the RLC data blocks + +sent during the initial fixed uplink allocation or including an rTLLI value which does not consist of the 4 least significant bits of the TLLI; in such a case, the mobile station shall not transmit on any of the uplink resources that are allocated in the EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, nor shall it transmit an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC in the uplink resources specified if a valid RRBP field is received as part of the EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message. + +In case of a contention resolution failure on the mobile station side, the mobile station shall stop timer T3228, if running, stop transmitting on the TBF and enter packet idle mode. If timer T3248 was running when the contention resolution failure occurred (and thus not T3228), the timer T3248 shall be stopped. It shall then reinitiate the packet access procedure, unless the maximum allowed number of packet access procedure has already been attempted, see 3GPP TS 44.018. In that case, a TBF failure has occurred, see sub-clause 7a.2.4. + +### 7a.2.1.2 Contention resolution at packet access procedure using Enhanced Access Burst procedure + +When the Enhanced Access Burst procedure is used, only the first RLC data block that is sent on the TBF shall include the TLLI of the mobile station. If MCS-7, MCS-8 or MCS-9 is used for the transmission of the TLLI (i.e. the RLC/MAC block is carrying two RLC data blocks), the TLLI shall be inserted in both RLC data blocks that are included in the first RLC/MAC block. Every RLC data block that is sent on the TBF, except the first one, shall include the reduced TLLI (rTLLI) of the mobile station until the mobile station receives an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message or an EC PACKET UPLINK ACK/NACK message addressing the mobile station with the TFI value associated with the uplink TBF and containing either the TLLI or the rTLLI of the mobile station. The reduced TLLI (rTLLI) consists of the 4 least significant bits of the TLLI of the mobile station. The rTLLI shall not be included in the RLC/MAC header if the TLLI is included in the RLC Data block. The rTLLI value shall thus not be included in the RLC/MAC header of the first RLC Data block of a TBF, with BSN=0 and, if MCS-7, MCS-8 or MCS-9 is used for the transmission, with BSN=1, since the TLLI of the mobile station is included in the RLC data block(s). + +The retransmission of an RLC data block shall include the TLLI, if the RLC data block was originally transmitted including the TLLI. The retransmission of an RLC Data block shall include the rTLLI in the RLC/MAC header if the RLC Data block was initially transmitted including the rTLLI in the RLC/MAC header. + +After the last allocated RLC data block has been transmitted according to the initial fixed uplink allocation (received in the EC Immediate Assignment message), the mobile station shall start timer T3226. When timer T3226 expires the mobile station shall start timer T3228 and start continuously monitoring the EC-PACCH for reception of an RLC/MAC control message, see sub-clause 8.1.1.3b. + +When the network has correctly received an RLC data block that comprises the TLLI, it shall include the TLLI in an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message that it sends to the mobile station (i.e. to allow for contention resolution on the mobile station side). If the network has received an RLC Data block with the rTLLI included in the RLC/MAC header but no RLC Data block comprising the TLLI, the network shall include the rTLLI in the next EC PACKET UPLINK ACK/NACK message that it sends to the mobile station. + +After the last allocated RLC data block of a fixed uplink allocation, the network shall start timer T3227. The mobile station is only reachable on the EC-PACCH once timer T3227 has expired. When timer T3227 expires, the network shall start timer T3229 and send the EC PACKET UPLINK ACK/NACK or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station. The network may send additional EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages to the mobile station while timer T3229 is running. The network should then however take into account that the mobile station will stop monitoring the EC-PACCH at reception of a matching EC PACKET UPLINK ACK/NACK or a matching EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message containing a fixed uplink allocation. If the network receives uplink data from the mobile station, on the resources that are part of the fixed uplink allocation, the network shall stop timer T3229, if running. + +If timer T3249 is not used, i.e. it has the value 0, the network may release the TBF and reuse the TFI resource when timer T3229 has expired and no uplink data has been received in a fixed uplink allocation sent to the mobile station in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages before expiry of timer T3229. If timer T3249 is used, i.e. it has a value > 0, it shall be started at expiry of T3229. The network may send EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages to the mobile station using the next higher DL Coverage Class, compared to + +the last assigned DL Coverage Class, while T3249 is running, see sub-clause 8.1.1.3b. When timer T3249 has expired and no uplink data has been received in a fixed uplink allocation allocated to the mobile station in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages before expiry of timer T3249 (or preceding T3229), the network may release the TBF and reuse the TFI resource. + +The contention resolution is completed on the network side when the network receives an RLC data block that comprises the TLLI value that identifies the mobile station and the TFI value associated with the TBF. The subsequent RLC Data blocks that are part of the initial fixed uplink allocation are identified by the reduced TLLI (rTLLI) included in the RLC/MAC header and the TFI value associated with the TBF. + +When the mobile station receives an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with the uplink TBF, the mobile station shall stop timer T3228, if running, and act on the received message, unless it included a TLLI value other than that the mobile station included in the RLC header, or a rTLLI value other than that the mobile station included in the RLC/MAC header, of the RLC data blocks sent during the initial fixed uplink allocation. If timer T3248 was running at reception of the EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message (and thus not T3228), the timer T3248 shall be stopped. + +The contention resolution is successfully completed on the mobile station side when the mobile station receives an EC PACKET UPLINK ACK/NACK message addressing the mobile station with the TFI value associated with the uplink TBF and including the same TLLI value that the mobile station has included in the RLC header of the first RLC data block. + +The mobile station has entered the packet transfer mode upon a successful contention resolution. + +The contention resolution has failed on the mobile station side when timer T3228 expires, if T3248 (sent in EC SI) is not used. If timer T3248 is used, i.e. it has a value > 0, it shall be started when timer T3228 expires. The contention resolution has failed on the mobile station side when timer T3248 expires. The contention resolution also fails, if the mobile station receives an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI associated with the uplink TBF and including a TLLI value other than that which the mobile station included in the RLC header of the first RLC data block sent during the initial fixed uplink allocation or including an rTLLI other than that which the mobile station included in the RLC/MAC header of subsequent RLC Data blocks sent during the initial fixed uplink allocation; in such a case, the mobile station shall not transmit on any of the uplink resources that are allocated in the EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, nor shall it transmit an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC in the uplink resources specified if a valid RRBG field is received as part of the EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message. + +In case of a contention resolution failure on the mobile station side, the mobile station shall stop timer T3228, if running, stop transmitting on the TBF and enter packet idle mode. If timer T3248 was running when the contention resolution failure occurred (and thus not T3228), the timer T3248 shall be stopped. It shall then reinitiate the packet access procedure, unless the maximum allowed number of packet access procedure has already been attempted, see 3GPP TS 44.018. In that case, a TBF failure has occurred, see sub-clause 7a.2.4. + +## 7a.2.2 RLC/MAC procedures during contention resolution + +During the contention resolution, the only non-distribution RLC/MAC control message that the mobile station shall accept are the EC PACKET UPLINK ACK/NACK and EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages. Any other non-distribution RLC/MAC control message shall not be accepted by the mobile station. + +If a valid RRBG field is received as part of the RLC/MAC control block containing the EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station, the mobile station shall transmit an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message in the uplink resources specified (see sub-clause 10.4.5). + +## 7a.2.3 Timing Advance + +Initial timing advance is provided in the EC Immediate Assignment messages, in the TIMING\_ADVANCE\_VALUE field, when the packet access is performed using the EC-RACH or RACH. + +Thereafter the timing advance is updated with an EC PACKET POWER CONTROL/TIMING ADVANCE message or an EC PACKET UPLINK ACK/NACK message, containing a TIMING\_ADVANCE\_VALUE field, on the EC-PACCH. + +## 7a.2.4 Abnormal cases + +If a failure occurs on the mobile station side of the uplink TBF before the mobile station has successfully entered the packet transfer mode, the reserved resources are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the failure is due to a TLLI or rTLLI mismatch in the contention resolution procedure, the mobile station shall remain in packet idle mode, notify higher layers (TBF establishment failure), transactions in progress shall be aborted and the mobile station shall reinitiate the packet access procedure, unless the maximum number of access retransmissions allowed by the packet access procedure has already been attempted, see 3GPP TS 44.018. If the maximum number of access retransmissions allowed by the packet access procedure has been attempted a change of Coverage Class or cell reselection may be performed (see 3GPP TS 45.008); +- If the failure is due to the expiry of timer T3228 (if timer T3248 is not used) or timer T3248 in the contention resolution procedure, the mobile station shall remain in packet idle mode, notify higher layers (TBF establishment failure), transactions in progress shall be aborted and the mobile station shall reinitiate the packet access procedure, unless the maximum number of access retransmissions allowed by the packet access procedure has already been attempted, see 3GPP TS 44.018. If the maximum number of access retransmissions allowed by the packet access procedure has been attempted a change of Coverage Class or cell reselection may be performed (see 3GPP TS 45.008); +- If the mobile station, in the EC PACKET UPLINK ACK/NACK message has been assigned an MCS that the MS does not support (e.g. with 8-PSK modulation), the MS shall return to packet idle mode and notify higher layers (TBF establishment failure); +- If the failure is due to any other reason, the mobile station shall return to packet idle mode, notify higher layers (TBF establishment failure), transactions in progress shall be aborted and cell reselection may be performed (see 3GPP TS 45.008). + +## 7a.3 TBF establishment initiated by the network for EC-GSM-IoT on EC-CCCH + +The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of upper layer PDUs in the direction from the network to the mobile station. The procedure is triggered by a request from upper layers on the network side to transfer an upper layer PDU to a mobile station in packet idle mode that has enabled EC operation. Upon such a request, the network shall initiate a packet downlink assignment procedure on the EC-CCCH as described in 3GPP TS 44.018. + +On expiry of timer T3190, the mobile station shall abort the procedure and return to packet idle mode. + +The packet downlink assignment procedure is completed when the mobile station receives a valid RLC/MAC block. The mobile station then restarts timer T3190 and enters the packet transfer mode. + +### 7a.3.1 Timing Advance + +Initial timing advance can be provided in the EC Downlink Assignment message in the TIMING\_ADVANCE\_VALUE field. In case valid timing advance for the mobile station is not available, the network may trigger the packet polling procedure (see sub-clause 7a.3.2) by transmitting an EC PACKET POLLING REQUEST message with TYPE\_OF\_ACK parameter set to access bursts (see sub-clause 11.2.54). + +The EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message, received from the mobile station, is then used to derive the timing advance of the mobile station. + +Thereafter the timing advance in the mobile station is updated with the EC PACKET POWER CONTROL /TIMING ADVANCE message. For the case where a Timing Advance Value is not provided in the EC Downlink Assignment message, the mobile station is not allowed to send normal bursts (e.g. EC PACKET DOWNLINK ACK/NACK message) on the uplink until it receives a valid timing advance in an EC PACKET POWER CONTROL /TIMING ADVANCE message. + +### 7a.3.2 Packet polling procedure + +The network may send an EC PACKET POLLING REQUEST message to the mobile station, where the mobile station is addressed with its TFI. + +On receipt of an EC PACKET POLLING REQUEST message with the TYPE\_OF\_ACK parameter set to access bursts (see sub-clause 11.2.54), the mobile station shall send the EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message using identical repeated access bursts, on resources allocated by the RRBP field (as defined in sub-clause 10.4.5) and according to its uplink Coverage Class. + +The mobile station shall, in the EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message, include its latest downlink Coverage Class estimation and, in case the C value is above BT\_Threshold\_DL (see 3GPP TS 45.008), the latest estimated C value range in the DL\_CC\_EST field. + +--- + +## 8 Medium Access Control (MAC) Procedures in Packet Transfer Mode + +### 8.0 General + +The MAC procedures defined in this sub-clause are applicable in packet transfer mode. They are applicable in dual transfer mode, if both the network and the mobile station support DTM. + +The procedures in this sub-clause (clause 8) shall not be used to change the frequency allocation of the carrier supporting the dedicated resources for the mobile station in dual transfer mode. None of the PACKET DOWNLINK ASSIGNMENT, the MULTIPLE TBF DOWNLINK ASSIGNMENT, the PACKET UPLINK ASSIGNMENT, the MULTIPLE TBF UPLINK ASSIGNMENT, the PACKET TIMESLOT RECONFIGURE or the MULTIPLE TBF TIMESLOT RECONFIGURE messages shall include frequency parameters for the carrier supporting the dedicated resources when they are sent to a mobile station in dual transfer mode. + +NOTE: The network may use the DTM procedures on the main DCCH (the DTM ASSIGNMENT COMMAND message), if the radio resources for the RR connection and one or more TBF(s) need to be changed (see 3GPP TS 44.018). + +### 8.1 Transfer of RLC data blocks + +#### 8.1.0 Medium access mode + +The transfer of RLC data blocks is governed by different principles on both uplink and downlink for each of the defined medium access modes: dynamic allocation, extended dynamic allocation, exclusive allocation and fixed uplink allocation. + +The exclusive allocation is applicable only in dual transfer mode and MAC-DTM state and shall be used on a half-rate PDCH. The fixed uplink allocation is applicable only for an uplink EC TBF. + +#### 8.1.1 Uplink RLC data block transfer + +For a TBF operating in BTTI configuration, prior to the initiation of RLC data block transfer on the uplink, the network assigns the following parameters to characterise the uplink TBF in the uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION) message: + +- a Temporary Flow Identity (TFI). The mobile station shall set the TFI field of each uplink RLC data block to the TFI value assigned: + - to the mobile station for that uplink TBF, + - or in case EMST is used, to the TFI value assigned to the corresponding RLC entity on that uplink TBF, + - or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on the uplink TBF; +- a set of PDCHs to be used for the uplink transfer; +- a TBF Starting Time indication (optional in case of a dynamic or extended dynamic allocation and not applicable for dual carrier, multi carrier, BTTI with FANR activated, EGPRS2 configurations and EC TBFs); +- the PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures, or in case EMST is used, the PFI associated with each RLC entity on the allocated TBF, or in case EMSR is enabled for one or more RLC entities of the allocated TBF, the PFI associated with each PFC supported by these RLC entities. +- in case of an uplink EC TBF, the network also assigns the following parameters: + - a set of PDCHs to be used for transmission of downlink RLC/MAC control messages + - uplink and downlink coverage classes. + +In case the RTTI configuration is supported by the network and the mobile station and an uplink TBF operating in RTTI configuration is assigned, the following parameters shall be provided by the network in the assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). + +- a Temporary Flow Identity (TFI). The mobile station shall set the TFI field of each uplink RLC data block to the TFI value assigned: + - to the mobile station for that uplink TBF, + - or in case EMST is used, to the TFI value assigned to the corresponding RLC entity on that uplink TBF, + - or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on the uplink TBF; +- one or more PDCH-pairs to be used for the uplink transfer; +- the PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures, or in case EMST is used, the PFI associated with each RLC entity on the allocated TBF, or in case EMSR is enabled for one or more RLC entities of the allocated TBF, the PFI associated with each PFC supported by these RLC entities; +- BTTI USF or RTTI USF mode to be used when receiving USFs. + +For each PDCH-pair forming part of an assignment for an uplink TBF operating in RTTI configuration, the network may additionally assign a corresponding downlink PDCH-pair which shall be monitored by the mobile station for the USF (see sub-clause 7.1.3.6). + +The network may, at any time during uplink packet transfer, change the TTI configuration or USF mode (BTTI USF mode or RTTI USF mode) as well as the corresponding downlink PDCH-pairs of an already established uplink TBF by sending on the downlink PACCH, an uplink TBF assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). The mobile station shall begin using the new parameters within the reaction time defined in 3GPP TS 45.010. + +In a Downlink Dual Carrier configuration, one or more PDCHs are assigned to a single mobile station on each of two different radio frequency channels. In a DLMC configuration, one or more PDCHs are assigned to a single mobile station on one or more of the uplink radio frequency channels that correspond to the downlink radio frequency channels assigned for the DLMC configuration. A mobile station with a Downlink Dual Carrier configuration or a DLMC configuration shall not be allocated radio blocks on multiple radio frequency channels during any given radio block period. + +All the RLC data blocks of an uplink TBF initiated by one phase access, or for a mobile station in EC operation using the access burst procedure, see sub-clause 7a.2.1.1, shall each contain a TLLI (in *A/Gb mode*) or a G-RNTI (in *Iu mode*) field in the RLC data block header until the contention resolution is completed on the mobile station side (see sub-clause 7.1.2.3, 7a.2.1.1). A mobile station in EC operation using the enhanced access burst procedure, see sub-clause 7a.2.1.2, shall only include the TLLI in the first RLC data block of the uplink TBF and the rTLLI in the RLC/MAC headers of the remaining RLC data blocks until the contention resolution is completed (see sub-clause 7a.2.1.2). After the reaction time specified in 3GPP TS 45.010 no other RLC data blocks shall contain a TLLI/rTLLI field (in *A/Gb mode*) or a G-RNTI (in *Iu mode*), except for those retransmitted RLC data blocks that originally contained a TLLI/rTLLI (in *A/Gb mode*) or a G-RNTI (in *Iu mode*), which will be repeated including the same TLLI/rTLLI (in *A/Gb mode*) or G-RNTI (in *Iu mode*) (see sub-clause 7.1.2.3a, 7a.2.1). The TLLI\_BLOCK\_CHANNEL\_CODING parameter in the PACKET UPLINK ASSIGNMENT or in the MULTIPLE TBF UPLINK ASSIGNMENT message indicates whether a RLC data block containing a TLLI (in *A/Gb mode*) or a G-RNTI (in *Iu mode*) field in the RLC data block header shall be encoded using CS-1 in GPRS TBF mode, or MCS-1 in EGPRS TBF mode, or using the commanded modulation and channel coding scheme (see 3GPP TS 45.003). In GPRS TBF mode, the mobile station shall send all other RLC data blocks using the commanded channel coding scheme. + +In EGPRS TBF mode, RLC data blocks that are transmitted for the first time shall be transmitted with the commanded MCS, except if the commanded mode is MCS-5-7, in which case the data block shall be transmitted with MCS-5, or if the commanded mode is MCS-6-9, in which case the data block shall be transmitted with MCS-6. In EC TBF mode, the first RLC data block shall be transmitted with the commanded MCS, except if the commanded mode is MCS-5-7, in which case the first RLC data block shall be transmitted with MCS-5, or if the commanded mode is MCS-6-9, in which case the first RLC data block shall be transmitted with MCS-6. In the case of a Downlink Dual Carrier configuration or a DLMC configuration the commanded MCS shall apply to all of the uplink carriers for which PDCH resources have been assigned. In EGPRS TBF mode, a MS may choose an alternate MCS than the one commanded, for the initial transmission of the last RLC data blocks of the TBF under the following conditions: + +- the alternate MCS is more robust than the commanded MCS; +- the alternate MCS has already been commanded by the network during the TBF or was available for selection by the MS during the TBF according to the MCS selection rules for retransmissions; and +- the TBF requires no more radio blocks for initial transmission of the RLC data blocks using the alternate MCS than would be required when using the commanded MCS. + +For a TBF with FANR activated, if the commanded MCS is MCS-9 (respectively MCS-4), the initial transmission of the RLC data block(s) shall be done with MCS-8 (respectively MCS-3) if a PAN field is included in the radio block. + +When EMST is used, the commanded MCS shall apply to the RLC entity on the TBF identified by the TFI included in the header of the RLC/MAC block. + +A RESEGMENT bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message. In EC TBF mode a RESEGMENT bit is included in the EC PACKET UPLINK ACK/NACK or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message if it includes a Fixed Uplink Allocation. For initial transmissions of new RLC blocks the channel coding commanded is applied. The RESEGMENT bit is used to set the ARQ mode to type I or type II (incremental redundancy) for uplink TBFs when retransmissions are needed. For retransmissions, setting the RESEGMENT bit to '1' (type I ARQ) requires the mobile station to use an MCS within the same family as the initial transmission and the payload may be split (refer to table 8.1.1.1). For retransmissions, setting the RESEGMENT bit to '0' (type II ARQ) requires the mobile station to use an MCS within the same family as the initial transmission without splitting the payload even if the network has commanded it to use MCS-1, MCS-2 or MCS-3 for subsequent RLC blocks (refer to table 8.1.1.2), see note. In RLC unacknowledged mode, RESEGMENT bit shall be ignored and default value 0 should be used. + +NOTE: This bit is particularly useful for networks with uplink IR capability since it allows combining on retransmissions. + +**Table 8.1.1.1: Choice of MCS for retransmissions with re-segmentation (EGPRS/EC-GSM-IoT)** + +| Scheme used for initial transmission | Scheme to use for retransmissions after switching to a different MCS | | | | | | | | | | | +|--------------------------------------|----------------------------------------------------------------------|-----------------|-----------------|-------------------|-----------------|-------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | MCS-9 Commanded | MCS-8 Commanded | MCS-7 Commanded | MCS-6-9 Commanded | MCS-6 Commanded | MCS-5-7 Commanded | MCS-5 Commanded | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | +| MCS-9 | MCS-9 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-8 | MCS-8 | MCS-8 | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | +| MCS-7 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-6 | MCS-9 | MCS-6 | MCS-6 | MCS-9 | MCS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-5 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-1 | MCS-1 | MCS-1 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +NOTE: MCS to use for retransmissions when re-segmentation (RESEGMENT bit set to '1') is carried out (specified as a function of the scheme used for the initial transmission). + +**Table 8.1.1.2: Choice of MCS for retransmissions without re-segmentation (EGPRS/EC-GSM-IoT)** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to a different MCS | | | | | | | | | | | +|--------------------------------------|----------------------------------------------------------------------|-----------------|-----------------|-------------------|-----------------|-------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | MCS-9 Commanded | MCS-8 Commanded | MCS-7 Commanded | MCS-6-9 Commanded | MCS-6 Commanded | MCS-5-7 Commanded | MCS-5 Commanded | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | +| MCS-9 | MCS-9 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| MCS-8 | MCS-8 | MCS-8 | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | +| MCS-7 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| MCS-6 | MCS-9 | MCS-6 | MCS-6 | MCS-9 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| MCS-5 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +NOTE: MCS to use for retransmissions when re-segmentation is not (RESEGMENT bit set to '0') allowed (specified as a function of the scheme used for the initial transmission). + +**Table 8.1.1.3: Choice of modulation and coding scheme for retransmissions with re-segmentation (EGPRS2-A)** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UAS) | | | | | | | | | | | +|--------------------------------------|------------------------------------------------------------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | UAS-11 Commanded | UAS-10 Commanded | UAS-9 Commanded | UAS-8 Commanded | UAS-7 Commanded | MCS-6 Commanded | MCS-5 Commanded | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | + +| | | | | | | | | | | | | +|--------|--------|--------|-------|-------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| +| UAS-11 | UAS-11 | UAS-8 | UAS-8 | UAS-8 | MCS-6 (pad) | MCS-6 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | +| UAS-10 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | MCS-5 | MCS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| UAS-9 | UAS-9 | UAS-9 | UAS-9 | MCS-6 | MCS-6 | MCS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| UAS-8 | UAS-11 | UAS-8 | UAS-8 | UAS-8 | MCS-6 (pad) | MCS-6 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | MCS-3 (pad) | +| UAS-7 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | MCS-5 | MCS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-6 | UAS-9 | UAS-9 | UAS-9 | MCS-6 | MCS-6 | MCS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-5 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | MCS-5 | MCS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-1 | MCS-1 | MCS-1 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +**Table 8.1.1.4: Choice of modulation and coding scheme for retransmissions without re-segmentation (EGPRS2-A)** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UAS) | | | | | | | | | | | +|--------------------------------------|------------------------------------------------------------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | UAS-11 Commanded | UAS-10 Commanded | UAS-9 Commanded | UAS-8 Commanded | UAS-7 Commanded | MCS-6 Commanded | MCS-5 Commanded | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | +| UAS-11 | UAS-11 | UAS-8 | UAS-8 | UAS-8 | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | +| UAS-10 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| UAS-9 | UAS-9 | UAS-9 | UAS-9 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| UAS-8 | UAS-11 | UAS-8 | UAS-8 | UAS-8 | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | MCS-6 (pad) | +| UAS-7 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| MCS-6 | UAS-9 | UAS-9 | UAS-9 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| MCS-5 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +**Table 8.1.1.5: Choice of modulation and coding scheme for retransmissions with re-segmentation (EGPRS2-B)** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UBS) | | | | | | | | | | | | +|--------------------------------------|------------------------------------------------------------------------------------------------------------|------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | UBS-12 Commanded | UBS-11 Commanded | UBS-10 Commanded | UBS-9 Commanded | UBS-8 Commanded | UBS-7 Commanded | UBS-6 Commanded | UBS-5 Commanded | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | +| | | | | | | | | | | | | | + +| | | | | | | | | | | | | | +|--------|--------|--------|-----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| UBS-12 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| UBS-11 | UBS-11 | UBS-11 | UBS-10
(pad) | UBS-8
(pad) | UBS-8
(pad) | UBS-6
(pad) | UBS-6
(pad) | MCS-3
(pad) | MCS-3
(pad) | MCS-3
(pad) | MCS-3
(pad) | MCS-3
(pad) | +| UBS-10 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| UBS-8 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| UBS-7 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| UBS-6 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| UBS-5 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-1 | MCS-1 | MCS-1 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +**Table 8.1.1.6: Choice of modulation and coding scheme for retransmissions without re-segmentation (EGPRS2-B)** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UBS) | | | | | | | | | | | | +|--------------------------------------|------------------------------------------------------------------------------------------------------------|------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | UBS-12 Commanded | UBS-11 Commanded | UBS-10 Commanded | UBS-9 Commanded | UBS-8 Commanded | UBS-7 Commanded | UBS-6 Commanded | UBS-5 Commanded | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | +| UBS-12 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | +| UBS-11 | UBS-11 | UBS-11 | UBS-10
(pad) | UBS-8
(pad) | UBS-8
(pad) | UBS-6
(pad) | UBS-6
(pad) | UBS-6
(pad) | UBS-6
(pad) | UBS-6
(pad) | UBS-6
(pad) | UBS-6
(pad) | +| UBS-10 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | +| UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | +| UBS-8 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | +| UBS-7 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | +| UBS-6 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | +| UBS-5 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +In EGPRS (EGPRS TBF) or in EC operation (EC TBF), if these rules require a transmission (either original transmission or retransmission) in a) MCS-7 or b) MCS-8 or c) MCS-9, but there is only one RLC block that can be transmitted in that MCS, the MS shall send that block in either MCS-5 for case a) or MCS-6 for case b) or case c). In case b), padding is permitted. + +In EGPRS2, if these rules require a transmission (either original transmission or retransmission) in a modulation and coding scheme where there are fewer than the maximum number of RLC blocks that can be transmitted, the mobile station shall use the modulation and coding scheme specified in tables 8.1.1.7 and 8.1.1.8. + +**Table 8.1.1.7: Retransmissions with fewer RLC blocks (EGPRS2-A)** + +| Modulation and Coding Scheme specified | Modulation/Coding scheme to be used (only 1 block can be transmitted) | Modulation/Coding scheme to be used (only 2 blocks can be transmitted) | +|----------------------------------------|-----------------------------------------------------------------------|------------------------------------------------------------------------| +| UAS-7 | MCS-5 | n/a | +| UAS-8 | MCS-6 (with padding) | n/a | +| UAS-9 | MCS-6 | n/a | +| UAS-10 | MCS-5 | UAS-7 | +| UAS-11 | MCS-6 (with padding) | UAS-8 | + +**Table 8.1.1.8: Retransmissions with fewer RLC blocks (EGPRS2-B)** + +| Modulation and Coding Scheme Specified | Modulation/Coding scheme to be used (only 1 block can be transmitted) | Modulation/Coding scheme to be used (only 2 blocks can be transmitted) | Modulation/Coding scheme to be used (only 3 blocks can be transmitted) | +|----------------------------------------|-----------------------------------------------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------| +| UBS-7 | UBS-5 | n/a | n/a | +| UBS-8 | UBS-6 | n/a | n/a | +| UBS-9 | UBS-5 | UBS-7 | n/a | +| UBS-10 | UBS-6 | UBS-8 | n/a | +| UBS-11 | UBS-6 (with padding) | UBS-8 (with padding) | UBS-10 (with padding) | +| UBS-12 | UBS-6 | UBS-8 | UBS-10 | + +Modulation and coding schemes to be used for retransmissions after a transition from EGPRS to EGPRS2-A or EGPRS2-B or from EGPRS2-A or EGPRS2-B to EGPRS are specified in sub-clause 8.1.1.7.2. + +For a TBF with FANR activated, if these rules require a retransmission in MCS-9 and a PAN field is included in an EGPRS RLC/MAC block for data transfer, the mobile station shall use MCS-6. If these rules require a retransmission in MCS-4, a PAN field is to be included in an EGPRS RLC/MAC block for data transfer and re-segmentation is allowed, the mobile station shall use MCS-1. If these rules require a retransmission in MCS-4 and re-segmentation is not allowed, the mobile station shall use MCS-4 and shall not include a PAN field in this retransmission. + +Upon receipt of a command from the network to change channel coding scheme, the mobile station shall react in accordance with the time specified in 3GPP TS 45.010. + +Upon receipt of any message containing an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET UPLINK ACK/NACK or PACKET CS RELEASE INDICATION message), the mobile station shall be ready to transmit in accordance with the requirements given in 3GPP TS 45.010. + +The mobile station shall transmit RLC/MAC blocks with the following priority: + +- RLC/MAC control blocks containing a PACKET CS REQUEST message; +- RLC/MAC control blocks containing a PACKET CELL CHANGE NOTIFICATION message; +- Other RLC/MAC control blocks, except + - Packet Uplink Dummy Control Blocks; and + - RLC/MAC control block containing an EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message, when the mobile station is polled for a PAN (see sub-clause 10.4.4a); +- RLC data blocks (including a PAN field if required. See sub-clauses 8.1.2.2, 9.1.8.2.1 and 9.1.14.3.) except RLC data blocks including a PAN which is sent in response to a poll where all the element(s) of V(B) have the value TENTATIVE\_ACK or ACKED; +- when the mobile station is polled for a PAN (see sub-clause 10.4.4a), RLC/MAC control block containing an EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message; +- RLC data block including a PAN which is sent in response to a poll where all the elements of V(B) have the value TENTATIVE\_ACK or ACKED; +- RLC/MAC control blocks containing Packet Uplink Dummy Control Blocks. + +A mobile station in EC operation shall only send RLC data blocks according to the fixed uplink allocation received in the assignment message or in the EC PACKET UPLINK ACK/NACK or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message. + +If an uplink TBF operating in MTTC configuration and operating in EGPRS RLC acknowledged mode is allocated RTTC and BTTC radio blocks whose transmissions start in the same TDMA frame, the mobile station shall determine which (if any) RLC data blocks to transmit on the RTTC resources according to the above rules and those in sub-clause 9.1.3.2.1 before determining which (if any) RLC data blocks to transmit on the BTTC resources, regardless of the relative numbering of the timeslots used for the RTTC and BTTC resources. + +NOTE: Within the respective reaction times specified in 3GPP TS 45.010 at uplink assignment, change of coding scheme and completion of the contention resolution at one phase access, the mobile station may send RLC/MAC control blocks containing Packet Uplink Dummy Control Blocks, if there is no other block ready to be transmitted. + +In *A/Gb mode*, during the TBF, if the countdown procedure has not started or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and multiple TBF procedures are not supported (i.e. the mobile station or the network does not support multiple TBF procedures) the mobile station shall ask for new or different radio resources, by sending a PACKET RESOURCE REQUEST message (sub-clauses 8.1.1.1.2), in the following cases; + +- When the mobile station has indicated Page Response, Cell update or Mobility Management procedure as access type in the PACKET CHANNEL REQUEST message and it has data to send; +- When the mobile station has data to send with a lower priority than indicated in the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message; +- When the mobile station has indicated 'Signalling' as access type in the EGPRS PACKET CHANNEL REQUEST message and it has data to send. + +An exception is the case of a mobile station using an EC TBF where PACKET RESOURCE REQUEST is not supported. + +In *A/Gb mode* or *Iu mode*, a mobile station that supports multiple TBF procedures shall send a PACKET RESOURCE REQUEST message to a network supporting multiple TBF procedures (see sub-clause 8.1.1.1.2), if it has data to send for one or more PFCs (*A/Gb mode*) or RBs (*Iu mode*) for which no uplink TBFs are established. + +### 8.1.1.1 Dynamic allocation uplink RLC data block transfer + +This sub-clause specifies mobile station behaviour for dynamic allocation uplink RLC data block transfer while in packet transfer mode, MAC-Shared State, dual transfer mode or MAC-DTM state. + +When the mobile station receives an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) that does not contain a TBF starting time, if the uplink TBF is assigned in BTTI configuration the mobile station shall begin monitoring the downlink PDCHs corresponding to (i.e. with the same timeslot number as) the assigned uplink PDCHs for the assigned USF value for each assigned uplink PDCH within the reaction time defined in 3GPP TS 45.010. Alternatively, if the uplink TBF is assigned in RTTI configuration, the mobile station shall begin monitoring the downlink PDCH-pairs corresponding to the assigned uplink PDCH-pairs for the assigned USF value within the reaction time defined in 3GPP TS 45.010. If a TBF starting time information element is present and no uplink TBFs are in progress, but one or more downlink TBFs are in progress, the mobile station shall wait until the starting time before beginning to monitor the USFs and using the newly assigned uplink TBF parameters. While waiting for the starting time, the mobile station shall monitor the assigned downlink PDCHs. If a TBF starting time information element is present and one or more uplink TBFs are already in progress, the mobile station shall continue to use the assigned parameters of the ongoing uplink TBFs until the TDMA frame number indicated by the TBF starting time occurs, at which time the mobile station shall immediately begin to use the newly assigned uplink TBF parameters. The mobile station shall continue to use the newly assigned parameters of each uplink TBF until the TBF is either released or reconfigured. If while waiting for the frame number indicated by the TBF starting time the mobile station receives another uplink assignment, the mobile station shall act upon the most recently received uplink assignment and shall ignore the previous uplink assignment. + +If a mobile station has requested multiple uplink TBFs in a PACKET RESOURCE REQUEST message, the network may allocate resources for these TBFs by sending one or more uplink assignment messages in response (see sub-clause 8.1.1.1.2). The mobile station shall act upon each successive uplink assignment message as it is received. + +A mobile station that has a TBF operating in BTTI configuration shall monitor all the downlink PDCHs corresponding to the assigned uplink PDCHs except if the mobile station is in DTR mode (see sub-clause 8.1.8). When operating a TBF in RTTI configuration, the mobile station shall monitor the corresponding downlink PDCH-pairs associated with the assigned uplink PDCH-pairs that can be monitored according to the number of allocated uplink PDCH-pairs and its multislot capabilities except if the mobile station is in DTR mode (see sub-clause 8.1.8). + +Whenever the mobile station detects an assigned USF value on a monitored downlink PDCH or PDCH-pair, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH or corresponding PDCH-pair for that TBF except if that TBF is running in extended uplink TBF mode, in which case the mobile station may transmit RLC/MAC block(s) for other TBFs assigned on the same PDCH or corresponding PDCH-pair (see sub-clause 9.3.1b.2). The time relation between an uplink block, which the mobile station shall use for transmission, and the occurrence of the USF value is defined in 3GPP TS 45.002. The number of RLC/MAC blocks to transmit is controlled by the USF\_GRANULARITY parameter characterising the uplink TBF. + +For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching requirements of its multislot class (see 3GPP TS 45.002). + +An uplink TBF operating in RTTI configuration may receive the assigned USFs either in RTTI USF mode or BTTI USF mode. The USF mode is indicated during the assignment of the corresponding uplink TBF. + +For an uplink TBF in RTTI configuration that receives the USFs in BTTI USF mode: + +- An assigned USF received on the first PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the first two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair, depending on the value of USF\_GRANULARITY. +- An assigned USF received on the second PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the second two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair, depending on the value of USF\_GRANULARITY. + +For an uplink TBF in RTTI configuration that receives the USFs in RTTI USF mode: + +- An assigned USF received on a monitored downlink PDCH-pair in the first reduced radio block period of a given basic radio block period allocates resources for one or four uplink RTTI radio blocks in the second reduced radio block period starting in the same basic radio block period and continuing with the second reduced radio block period in the following basic radio block periods on the corresponding uplink PDCH-pair, depending on the value of USF\_GRANULARITY. +- An assigned USF received on a monitored downlink PDCH-pair in the second reduced radio block period of a given basic radio block period allocates resources for one or four uplink RTTI radio blocks in the first reduced radio block period starting in the next basic radio block period and continuing with the first reduced radio block period in the following basic radio block periods on the corresponding uplink PDCH-pair, depending on the value of USF\_GRANULARITY. + +The time relation between the uplink radio block(s) which the mobile station shall use for transmission and the occurrence of the USF value is further defined in 3GPP TS 45.002 + +In a Downlink Dual Carrier configuration, one or more PDCHs are assigned to a single mobile station on each of two different radio frequency channels. In a DLMC configuration, one or more PDCHs are assigned to a single mobile station on one or more of the uplink radio frequency channels that correspond to the downlink radio frequency channels assigned for the DLMC configuration. A mobile station with a Downlink Dual Carrier configuration or a DLMC configuration shall not be allocated radio blocks on more than one radio frequency channel during any given radio block period. + +When the mobile station transmits an RLC/MAC block to the network, it shall start timer T3180 for the uplink TBF on which the block was sent. When the mobile station detects an assigned USF value on a downlink PDCH corresponding to an assigned uplink PDCH for that TBF, the mobile station shall restart timer T3180. If any given timer T3180 expires, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2 (*A/Gb mode*)). + +Whenever the network receives a valid RLC/MAC block for any given TBF, it shall reset counter N3101 for that TBF. The network shall increment counter N3101 for each radio block, allocated to that TBF, for which no data is received. If N3101 = N3101max, the network shall stop the scheduling of RLC/MAC blocks for that TBF and start timer T3169. When T3169 expires, the network may reuse the USF and TFI(s) assigned to that TBF. If PS Handover is ongoing it is optional for the network to increment N3101. + +#### 8.1.1.1.1 PACCH operation + +The mobile station shall attempt to decode every downlink RLC/MAC block on all the downlink PDCHs corresponding to (i.e. with the same timeslot number as) the assigned uplink PDCHs when the uplink TBF operates in BTTI configuration except if the mobile station is in DTR mode (see sub-clause 8.1.8). + +In case the uplink TBF operates in RTTI configuration the mobile station shall attempt to decode every downlink RLC/MAC block on the corresponding downlink PDCH-pairs being monitored (see subclause 8.1.1.1) except if the mobile station is in DTR mode (see sub-clause 8.1.8). + +Downlink PACCH blocks shall be received in the same TTI configuration as the assigned uplink TBF. + +Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message addresses the mobile station, the mobile station shall act on the message. + +Whenever a mobile station, that has an assigned uplink TBF operating in BTTI configuration, detects an assigned USF value on any downlink PDCH corresponding to an assigned uplink PDCH, the mobile station may transmit a PACCH block on the same PDCH in the next block period (see 3GPP TS 45.002). Whenever a mobile station, that has an assigned uplink TBF operating in RTTI configuration, detects an assigned USF value on any corresponding downlink PDCH-pair associated with an assigned uplink PDCH-pair, the mobile station may transmit a PACCH block on the PDCH-pair. The PACCH block shall be transmitted according to the USF scheduling in sub-clause 8.1.1.1. The mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see sub-clauses 10.4.4, 10.4.4a, 10.4.4b) unless the uplink TBF operates in either RTTI configuration, or in BTTI configuration with FANR activated, and the mobile station is polled for a Piggy-backed Ack/Nack (see sub-clause 10.4.4b). + +In the case of a Downlink Dual Carrier configuration or a DLMC configuration, all segments belonging to each RLC/MAC control message shall be sent on PACCH blocks belonging to the same carrier. + +When a mobile station in a DLMC configuration supporting more than 20 downlink timeslots sends an EGPRS Packet Downlink Ack/Nack DLMC message (see sub-clause 11.2.48) it shall be coded using CS-1 or CS-3 as indicated by the + +most recently received assignment message. Otherwise, if it supports 20 or less downlink timeslots, EGPRS Packet Downlink Ack/Nack DLMC messages shall be coded using CS-1. + +#### 8.1.1.1.2 Resource Reallocation for Uplink + +The mobile station and the network are not allowed to change the RLC mode nor TBF mode of an already established TBF during resource reallocation. Change of RLC mode or TBF mode shall be achieved through release of on-going TBF and establishment of a new TBF with the newly requested RLC mode or TBF mode. If a new mode is assigned by the network for an already established TBF, the MS shall ignore the new assigned mode and shall maintain the TBF in the old mode. + +During an uplink packet transfer, upper layers may request to transfer another upper layer PDU with a different PFI, a different Radio Priority, a different peak throughput class or a different RLC mode than the one which is in transfer. An upper layer PDU containing signalling shall be treated as having the highest Radio Priority, an implementation specific peak throughput class and the acknowledged RLC mode shall be requested. + +If the mobile station or the network does not support multiple TBF procedures the following procedures apply unless resource reallocation is not needed when EMSR is enabled (see sub-clause 5.12): + +- If the mobile station has not started the countdown procedure or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and the new upper layer PDU has the same RLC mode as the current uplink TBF, or in case EMST is used, the new upper layer PDU has the same RLC mode as any of the RLC entities allocated on the ongoing uplink TBF, and either a higher radio priority or the same radio priority but a higher peak throughput class, the mobile station shall immediately request a resource reallocation for uplink according to the new Radio Priority and peak throughput class of the new upper layer PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. Then the mobile station shall complete the transmission of the current upper layer PDU; +- If the new upper layer PDU has the same RLC mode as the current uplink TBF, or in case EMST is used, the new upper layer PDU has the same RLC mode as any of the RLC entities allocated to the ongoing uplink TBF, and either a lower Radio Priority or the same radio priority but a lower peak throughput class, the mobile station shall first complete the sending of the upper layer PDU in transfer. When the sending of upper layer PDUs at the higher Radio Priority or the same radio priority but higher peak throughput class stops, without waiting for the acknowledgement from the network if in RLC acknowledged mode, the mobile station shall then perform the request of a resource reallocation for uplink for any remaining upper layer PDU(s) by sending a PACKET RESOURCE REQUEST message on the PACCH and start timer T3168 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. However if the upper layer PDUs at the higher Radio Priority does not completely fill the RLC data block the MS shall fill this RLC data block with payload from the new upper layer PDUs and then either transmit first the PACKET RESOURCE REQUEST message and subsequently the RLC data block or vice versa. +- If the mobile station or the network does not support EMST, and if the new upper layer PDU does not have the same RLC mode as the current uplink TBF but has a higher radio priority, the mobile station shall complete the transmission of the current upper layer PDU using the countdown procedure including acknowledgement from the network, if in RLC acknowledged mode. If the TBF is operated in non-extended uplink TBF mode, the mobile station shall then release the TBF and establish a new uplink TBF for transmission of the new upper layer PDU. If the TBF is operated in extended uplink TBF mode (see sub-clause 9.3.1b), the mobile station shall use the procedure in sub-clause 8.1.1.6 for changing the RLC mode. When the sending of upper layer PDUs with a higher radio priority is completed using the countdown procedure, including acknowledgement from the network if in RLC acknowledged mode, the mobile station shall try to establish an uplink TBF for the transmission of any remaining upper layer PDU(s); +- If both the mobile station and the network support EMST, the TBF is operated in extended uplink TBF mode, and the new upper layer PDU does not have the same RLC mode as any of the RLC entities allocated to the ongoing uplink TBF, the mobile station shall immediately request a resource reallocation for uplink according to the Radio Priority and peak throughput class of the new upper layer PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. Then the mobile station shall continue the transmission of the current upper layer PDU; +- If the mobile station has not started the countdown procedure or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and the new upper layer PDU does not have the same PFI but has the same radio + +priority and the same peak throughput class as the current uplink TBF, or if EMST is used, as one of the current RLC entities, the mobile station shall immediately request a resource reallocation for uplink with the new PFI by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. Then the mobile station shall complete the transmission of the current upper layer PDU. + +If both the mobile station and the network support multiple TBF procedures the following procedures apply: + +- The mobile station shall initiate a request for one or more new uplink TBFs when it has upper layer PDUs associated with one or more PFIs for which there are no ongoing uplink TBFs. In this case it sends a PACKET RESOURCE REQUEST message on the PACCH and starts an instance of timer T3168 for each uplink TBF requested; +- All ongoing uplink TBFs shall continue to operate using their currently allocated resources. + +If both the network and the mobile station support the extended uplink TBF mode, the request from upper layers may indicate that the new upper-layer PDU is meant to pre-allocate an uplink TBF (early TBF establishment). In this case, the EARLY\_TBF\_ESTABLISHMENT field in the PACKET RESOURCE REQUEST message shall indicate pre-allocation is required. + +On receipt of the PACKET RESOURCE REQUEST message the network shall respond by sending either an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE) or a PACKET ACCESS REJECT message to the mobile station on the downlink PACCH. If the mobile station supports RLC non-persistent mode the network may allocate one or more EGPRS TBFs that use this RLC mode. + +If the mobile station or the network does not support multiple TBF procedures, then after the transmission of the PACKET RESOURCE REQUEST message with the reason for changing PFI, the radio priority or peak throughput class of an assigned uplink TBF the mobile station shall continue to use the currently assigned uplink TBF assuming that the requested radio priority or peak throughput class is already assigned to that TBF. + +If both the mobile station and the network support multiple TBF procedures, then after transmission of a PACKET RESOURCE REQUEST message the mobile station shall maintain its ongoing uplink TBFs using their currently allocated TBF parameters. + +On receipt of an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) sent in response to a PACKET RESOURCE REQUEST message the mobile station shall stop timer T3168 for each uplink TBF assigned in the assignment message and switch to the assigned PDCHs. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.2.5. + +If the mobile station or the network does not support multiple TBF procedures, the mobile station is then not allowed to send new PACKET RESOURCE REQUEST messages until either a new packet transfer request is received from the upper layers or when sending of upper layer PDU(s) at a lower Radio Priority has to be continued. + +If the mobile station or the network does not support multiple TBF procedures, upon expiry of timer T3168 the mobile station shall retransmit the PACKET RESOURCE REQUEST message unless the PACKET RESOURCE REQUEST message has already been transmitted four times in which case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +If both the mobile station and the network support multiple TBF procedures, then upon expiry of all instances of timer T3168 the mobile station shall retransmit the PACKET RESOURCE REQUEST message to request resources for those uplink TBFs that did not receive an uplink assignment unless the PACKET RESOURCE REQUEST message has already been transmitted four times without receiving any uplink assignment in response. In this case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +If no assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) addressing any requested uplink TBF is received before the mobile station has completed its currently assigned TBFs the mobile station shall stop all instances of timer T3168. + +The network may at any time during uplink packet transfer initiate a change of resources by sending on the downlink PACCH monitored by the MS, an unsolicited uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT + +RECONFIGURE or PACKET CS RELEASE INDICATION message) to the mobile station. During the reallocation, TFI is allowed to be changed. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.2.5. + +When an uplink TBF is established in response to a PACKET RESOURCE REQUEST message with the EARLY\_TBF\_ESTABLISHMENT field set to indicate pre-allocation is required, a network supporting early TBF establishment should keep the uplink TBF open by means of the extended uplink TBF mode operation (see sub-clause 9.3.1b.2). + +On receipt of a PACKET ACCESS REJECT message, the mobile station shall stop timer T3168, if running, for the TBFs rejected in the PACKET ACCESS REJECT message, abort the uplink TBFs and indicate a packet access failure to the upper layer associated with each rejected TBF. If no more uplink or downlink TBFs exist, the mobile station in packet transfer mode shall return to packet idle mode; the mobile station in dual transfer mode shall return to dedicated mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. + +If the PACKET ACCESS REJECT message contains a WAIT\_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall: + +- If the mobile station or the network does not support multiple TBF procedures, start timer T3172 and if the mobile station has additional RLC data blocks to transmit, it shall initiate a new uplink TBF establishment, but the mobile station is not allowed to make a new attempt for an uplink TBF establishment in the same cell until timer T3172 expires, it may, however, attempt an uplink TBF establishment in an other cell after successful cell reselection. The mobile station may attempt to enter the dedicated mode in the same cell before timer T3172 has expired. During the time T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging request to trigger RR connection establishment; +- If both the mobile station and the network support multiple TBF procedures the mobile station shall start one instance of timer T3172 for each uplink TBF that was rejected. All TBFs in progress that are not rejected shall be maintained. The mobile station is not allowed to attempt re-establishment of a rejected uplink TBF in the same cell until its associated instance of timer T3172 expires. It may, however, attempt re-establishment of a rejected uplink TBF in another cell after successful cell reselection. The mobile station may attempt to enter the dedicated mode in the same cell before all instances of timer T3172 have expired. During the time one or more instances of T3172 are running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging request to trigger RR connection establishment. + +The value of the WAIT\_INDICATION field (i.e. timer T3172) relates to the cell from which it was received. + +#### 8.1.1.1.2.1 Abnormal cases + +The following abnormal cases apply: + +- If the mobile station receives an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) and detects an invalid Frequency Parameters information element in the message, the mobile station shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information; +- If the mobile station receives an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) specifying frequencies that are not all in one frequency band then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the information in the PACKET UPLINK ASSIGNMENT or the MULTIPLE TBF UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the information in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); + +- If the mobile station receives a PACKET UPLINK ASSIGNMENT or a MULTIPLE TBF UPLINK ASSIGNMENT message containing a Frequency Parameters information element specifying a frequency that is in a frequency band not supported by the mobile station then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station in dual transfer mode receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message indicating a change of EGPRS level which is forbidden (see sub-clause 8.1.1.7), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support multiple TBF procedures and if any given uplink assignment message provides an uplink TBF allocation for a PFI not indicated in the PACKET RESOURCE REQUEST message and not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST or EMSR and if any given uplink assignment message provides an allocation of an RLC entity for a PFI not indicated in the PACKET RESOURCE REQUEST message and not associated with any already allocated RLC entity on the uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) is due to any other reason (including frequency parameters which do not comply with the requirements specified in sub-clause 5.5.1.7), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +NOTE: An uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) received by a multi-band mobile station shall not be considered invalid if it indicates new frequencies that are all in a different frequency band to that of the PDCH(s) on which the assignment was received. The assignment may however be rendered invalid for some other reason. + +#### 8.1.1.1.3 Establishment of Downlink TBF + +During uplink transfer, the network may initiate the establishment of one or more downlink TBFs by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET CS RELEASE INDICATION) to the mobile station on the PACCH. If a PACKET TIMESLOT RECONFIGURE or a PACKET DOWNLINK ASSIGNMENT message is sent, then the message shall contain the DOWNLINK\_TFI\_ASSIGNMENT field for the downlink TBF being established. If multiple TBF procedures are supported by the mobile station and the network, the network shall indicate the PFI associated with each TBF it allocates or reallocates in the downlink assignment message. The network shall not attempt to establish multiple downlink TBFs for a mobile station with only one uplink TBF unless the mobile station's radio access capabilities are known. If EMST is used, the network shall indicate the PFI associated with each RLC entity in the downlink assignment message (i.e. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). The multislot restrictions of the mobile station shall be observed. + +A mobile station that supports multiple TBF procedures shall act on the downlink assignment message as follows: + +- Upon reception of a PACKET DOWNLINK ASSIGNMENT message the mobile station shall release all ongoing downlink TBFs not addressed by this message and shall act on the message. All ongoing uplink TBFs shall be maintained; + +- Upon reception of a PACKET TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message; +- Upon reception of a MULTIPLE TBF DOWNLINK ASSIGNMENT message the mobile station shall maintain all ongoing TBFs not addressed by this message using its currently allocated TBF parameters and shall act on the message; +- Upon reception of a MULTIPLE TBF TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message; +- Upon reception of a PACKET CS RELEASE INDICATION message the mobile station shall release all ongoing uplink and/or downlink TBFs not addressed by this message and shall act on the message. + +A mobile allocation or reference frequency list, received as part of a downlink assignment, replaces the previous parameters and shall be used until a new assignment is received or the mobile station has released all TBFs. + +If the network and mobile station both support Downlink Dual Carrier, the network may send a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION) to a mobile station assigning one or more TBFs with packet resources on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. + +If the assignment message contains the *Assignment Info* IE indicating an assignment type other than 'Dual Carrier assignment', then the packet resources specified in this message replace any existing assignment for the addressed TBFs on the carrier identified by the Carrier ID field. In this case, if the assignment message addresses TBFs that currently have packet resources assigned on the other carrier (i.e. the carrier not identified by the Carrier ID field) then these packet resources shall be treated as follows: + +- these resources are implicitly released, if the ASSIGNMENT TYPE field (carried in the *Assignment Info* IE) indicates that the assignment is an 'Assignment on single carrier only'; +- these resources are unchanged, if the ASSIGNMENT TYPE field indicates that the assignment is a 'Modification of existing assignment'. + +If the assignment message contains the *Assignment Info* IE indicating an assignment type of 'Dual Carrier assignment', then the packet resources specified in this message replace any existing assignment for the addressed TBFs. + +If the network and mobile station both support Downlink Multi Carrier, the network may send a downlink assignment message (PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE) to a mobile station assigning a downlink TBF with packet resources on multiple downlink carriers and thereby establish a DLMC configuration. In this case a mobile station is assigned a set of one or more UFPSs (see 3GPP TS 45.008 [15]) that in total provide up to 16 carriers. The carriers assigned to a given UFPS shall belong to the same frequency band and Mobile Allocation. If the MS has indicated it supports inter-band reception (see 3GPP TS 24.008) the set of provided carriers shall belong to a maximum of two of the supported frequency bands. The set of UFPS in a DLMC configuration are numbered UFPS1, UFPS2, and so on, ending with UFPSM where UFPS numbering is managed as follows: + +- If an assignment message is sent to a mobile station with an ongoing downlink TBF for which only a single carrier is assigned then that carrier shall be considered as UFPS1 for the case where the assignment message establishes a DLMC configuration information. +- An assignment message that assigns one or more new UFPS results in each new UFPS being numbered according to the order in which it was assigned. For example, if UFPS1 and UFPS2 are currently assigned and two new UFPS are added then the first new UFPS becomes UFPS3 and the second new UFPS becomes UFPS4. +- An assignment message that deletes one or more existing UFPS results in the remaining UFPS being renumbered to ensure sequential UFPS numbering. For example, if UFPS1, UFPS2 ...UFPS5 are currently assigned and UFPS3 is deleted then UFPS4 becomes UFPS3 and UFPS5 becomes UFPS4. + +The carriers associated with a DLMC configuration are numbered in ascending order beginning with C1, followed by C2, and so on, ending with CN where the carriers are sequentially numbered beginning with those in UFPS1, followed by those in UFPS2 and so on, ending with those in UFPSM. The ordering of carriers within a given UFPS reflects the order in which they have been assigned for that UFPS (i.e. C1 is first carrier assigned for UFPS1). + +If PDCH-pairs are assigned for a DLMC configuration they are numbered in ascending order starting with the lowest numbered PDCH-pair on C1 and ending with the highest numbered PDCH-pair on CN: + +- The RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_DLMC bitmap indicates which of the PDCH pairs available on a given downlink carrier (indicated by the DOWNLINK\_PDCH\_PAIRS\_DLMC bitmap) are assigned for DLMC configuration. +- The PDCH pairs identified by the UPLINK\_PDCH\_PAIRS\_DLMC bitmap (if any) indicate the PDCH-pairs assigned for the uplink carrier corresponding to a given downlink carrier assigned for a DLMC configuration. +- When downlink PDCH pairs are assigned they are numbered in ascending order starting with the first PDCH-pair (PDCH-pair 1) consisting of the two lowest numbered timeslots assigned on $C_1$ , followed by the PDCH-pair consisting of the next two lowest numbered timeslots assigned on $C_1$ (PDCH-pair 2), and so on for the remaining timeslot pairs assigned on $C_1$ and for the assigned timeslot pairs on $C_2 \dots C_N$ . +- The highest numbered PDCH-pair consists of the two highest numbered timeslots on carrier $C_N$ . + +A mobile station in a DLMC configuration may receive subsequent assignment messages (PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) as follows: + +- A PACKET UPLINK ASSIGNMENT message may be used to assign packet resources on one or more of the uplink carriers corresponding to the assigned downlink carriers (see sub-clause 8.1.1.2.1) for the case where the ongoing downlink TBF does not need to be modified. +- A PACKET DOWNLINK ASSIGNMENT message may be used for the case where there is either no uplink TBF or the ongoing uplink TBF does not need to be modified. For the case of an ongoing uplink TBF, this message is only used if all carriers on which USF is currently monitored remain assigned. +- Otherwise, the PACKET TIMESLOT RECONFIGURE message is used. + +On receipt of a downlink assignment message, and after the TBF starting time, if present, the mobile station shall switch to the assigned PDCHs, and start timer T3190 for each of the TBFs assigned. The operation of the downlink TBFs follows the procedures in sub-clause 8.1.2 with the following additions: + +- the mobile station shall prioritise transmission of RLC/MAC control blocks associated with a downlink TBF over RLC/MAC control blocks associated with an uplink TBF; +- if a timer or counter expiry causes an uplink TBF to be aborted in the mobile station, the mobile station shall perform an abnormal release with access retry as specified in sub-clause 8.7.2 (*A/Gb mode*); +- If one uplink and one downlink TBF are already established, then the network may send a PACKET TIMESLOT RECONFIGURE message without DOWNLINK\_TFI\_ASSIGNMENT or, for a DLMC configuration, without DOWNLINK\_eTFI\_ASSIGNMENT. The mobile station shall interpret this as a reassignment of the timeslot allocations of the concurrent uplink and downlink TBFs and the downlink TFI is not changed. + +#### 8.1.1.1.3.1 Abnormal cases + +If a failure occurs on the mobile station side before the new TBF(s) has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If one uplink and one downlink TBF are not already established and the PACKET TIMESLOT RECONFIGURE message does not include a DOWNLINK\_TFI\_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station in dual transfer mode or MAC-DTM state receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); + +- If a failure in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support multiple TBF procedures and if any given downlink assignment message provides an uplink TBF allocation for a PFI not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that does not support Downlink Dual Carrier receives a PACKET DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF DOWNLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on more than one carrier or includes the *Assignment Info* IE which indicates that the assignment is a 'Modification of an existing assignment' or a 'Dual Carrier assignment', the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile which supports Downlink Dual Carrier receives a PACKET DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF DOWNLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on two carriers and those two carriers are not within the same frequency band, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration wherein resources are assigned on carriers in different frequency bands but does not support inter-band reception, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration with more carriers or more downlink timeslots than it supports, or assigns eTFIs or a SNS of 8192 or CS-3 for PDAN coding when the mobile station supports 20 or fewer time slots, or assigns carriers in a frequency band it does not support, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message that modifies a DLMC configuration that releases carriers on which USF is being monitored, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that assigns two or more UFPSs to the same Mobile Allocation (as defined by the *DLMC Frequency Parameter* IE), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET UPLINK ASSIGNMENT message that modifies a DLMC configuration by assigning an uplink carrier that does not correspond to an existing downlink carrier, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS RELEASE INDICATION message is due to any other reason (including the presence of frequency parameters which do not comply with the requirements specified in sub-clause 5.5.1.7), the mobile station shall abort the procedure and continue the normal operation of the ongoing uplink TBFs and ongoing downlink TBFs. + +### 8.1.1.2 Extended Dynamic Allocation uplink RLC data block transfer + +The Extended Dynamic Allocation medium access method extends the Dynamic Allocation medium access method to allow higher uplink throughput. + +This sub-clause defines the extensions to the Dynamic Allocation medium access method. All procedures defined in sub-clause 8.1.1.1 apply, except where this sub-clause defines a new procedure. In cases where this sub-clause conflicts with sub-clause 8.1.1.1, this sub-clause takes precedence. + +### 8.1.1.2.1 Uplink PDCH Allocation + +The PACKET UPLINK ASSIGNMENT and MULTIPLE TBF UPLINK ASSIGNMENT messages assign to the mobile station a subset of 1 to N uplink PDCHs (when the uplink TBF operates in BTTI configuration) or uplink PDCH-pairs (when the uplink TBF operates in RTTI configuration), where N depends on the mobile station multislot class. + +An uplink TBF that operates in RTTI configuration may receive the assigned USFs either in BTTI USF mode or in RTTI USF mode. The indication of whether BTTI USF mode or RTTI USF mode is to be used is provided during the assignment of the corresponding uplink TBF. + +If a mobile station supports Downlink Dual Carrier, the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message may assign PDCHs (corresponding to any given uplink TBF) on more than one carrier frequency. If this occurs, the Extended Dynamic Allocation procedures shall operate independently on each of the two carriers. + +A mobile station with a DLMC configuration shall only act on a PACKET UPLINK ASSIGNMENT message if it includes the *DLMC UL Carrier Info* IE (see sub-clause 11.2.29). In this case the message may reference one or more of the uplink carriers corresponding to the set of downlink carriers and indicate the following: + +- The referenced uplink carrier is not part of the uplink TBF in which case all resources for that uplink carrier (if any) are released. +- The referenced uplink carrier is part of the uplink TBF. If the message assigns no resources for that carrier then its existing resources remain unchanged. Otherwise, the assigned resources shall replace the existing resources (if any) for that carrier. +- If the message does not reference an uplink carrier then all resources for that uplink carrier (if any) are released. + +A mobile station that has an uplink TBF operating in BTTI configuration shall monitor the downlink PDCHs corresponding to (i.e. with the same timeslot number as) its assigned uplink PDCHs starting with the lowest numbered PDCH, then the next lowest numbered PDCH, etc., up to the one corresponding to the highest numbered assigned uplink PDCH except if the mobile station is in DTR mode. A mobile station in DTR mode shall only monitor the timeslot indicated in the DTR information (see sub-clause 8.1.8). A mobile station that has an uplink TBF operating in RTTI configuration shall monitor the downlink PDCH-pairs starting with the one corresponding to the uplink PDCH-pair with the lowest numbered timeslots, then the next uplink PDCH-pair, etc., up to the downlink PDCH-pair corresponding to the uplink PDCH-pair with the highest numbered timeslots assigned to the mobile station except if the mobile station is in DTR mode. A mobile station in DTR mode shall only monitor the downlink PDCH-pair indicated in the DTR information (see sub-clause 8.1.8). When in dual transfer mode, the network shall not assign uplink PDCHs whose corresponding downlink PDCH cannot be monitored by the mobile station because of the presence of the uplink dedicated channel. As an exception, in the case of dual transfer mode, if the mobile station indicates support of DTM high multislot class capability, the network may also assign uplink PDCHs whose corresponding downlink PDCH cannot be monitored by the mobile station. In this case, the mobile station shall monitor only those downlink PDCHs that are feasible when taking into account the position of the uplink dedicated channel and the switching requirements of its multislot class (see 3GPP TS 45.002). + +Whenever a mobile station with an uplink TBF operating in BTTI configuration detects an assigned USF value on a monitored PDCH, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the corresponding uplink PDCH (i.e. with the same timeslot number as the downlink PDCH on which the USF was detected) and on all higher numbered assigned uplink PDCHs except if it is in DTR mode. A mobile station in DTR mode shall perform any necessary uplink transmissions upon the detection of its assigned USF(s) using Dynamic Allocation procedures as specified in sub-clause 8.1.1.1. + +The following applies for an uplink TBF in RTTI configuration that receives USFs in BTTI USF mode: + +- An assigned USF received on the first PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the first two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots. +- An assigned USF received on the second PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the second two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots. + +The following applies for an uplink TBF in RTTI configuration that receives USFs in RTTI USF mode: + +- An assigned USF received in the first reduced radio block period of a given basic radio block period on a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the second reduced radio block period starting in the same basic radio block period and continuing with the second reduced radio block period in the following basic radio block periods, depending on the USF granularity, on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots. +- An assigned USF received in the second reduced radio block period of a given basic radio block period on a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the first reduced radio block period starting in the next basic radio block period and continuing with the first reduced radio block period in the following basic radio block periods, depending on the USF granularity, on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots. + +The following applies for an uplink TBF operating in an MTTC configuration when BTTC USF mode is used (i.e. RTTI\_USF\_MODE is set to '0'): + +- An assigned USF received on the first or second PDCH of a monitored downlink PDCH-pair allocates resources as specified above for the case of an uplink TBF in RTTI configuration where USFs are received in BTTC USF mode. In addition, if, within the MTTC configuration, the uplink BTTC resource uses a higher numbered timeslot number than the RTTI resources, an assigned USF received on the first PDCH of a monitored downlink PDCH-pair (i.e. a PDCH-pair that corresponds to an uplink PDCH-pair that is part of the uplink MTTC configuration) allocates resources for one or four uplink BTTC radio blocks using the BTTC resources within the MTTC configuration. +- An assigned USF received on the downlink PDCH that corresponds to the uplink BTTC PDCH resource allocates resources for one or four uplink BTTC radio blocks using the BTTC resources within the MTTC configuration and, if the uplink RTTI resources use higher numbered timeslots than the uplink BTTC resource, two or eight uplink RTTI radio blocks (i.e. in both the first and second reduced radio block periods in the subsequent basic radio block period(s)) for each assigned RTTI PDCH-pair within the MTTC configuration. + +NOTE: Examples of allocations of MTTC resources are given in Annex M. + +The following applies for an uplink TBF operating in an MTTC configuration when RTTI USF mode is used (i.e. RTTI\_USF\_MODE is set to '1'): + +- An assigned USF received in RTTI USF mode (i.e. on a downlink PDCH-pair corresponding to an assigned uplink PDCH-pair) allocates resources only for the assigned uplink RTTI resources, in accordance with the specifications for RTTI-only assignments. RTTI USFs do not allocate the uplink BTTC PDCH within an MTTC configuration. +- An assigned USF received on the downlink PDCH corresponding to the uplink BTTC PDCH resource allocates resources for one or four uplink BTTC radio blocks using the BTTC resources within the MTTC configuration. In addition, if, within the MTTC configuration, the uplink BTTC resource uses a lower numbered timeslot number than the RTTI resources, then an assigned USF received on the downlink PDCH corresponding to the uplink BTTC PDCH resource allocates resources for two or eight uplink RTTI radio blocks (i.e. in both the first and second reduced radio block periods in the subsequent basic radio block period(s)) for each assigned RTTI PDCH-pair within the MTTC configuration. + +For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching time requirements of its multislot class (see 3GPP TS 45.002). + +The time relation between an uplink block which the mobile station shall use for transmission and the occurrence of the USF value is defined in 3GPP TS 45.002. The number of RLC/MAC blocks to transmit on each allocated uplink PDCH/PDCH-pair is controlled by the USF\_GRANULARITY parameter characterising the uplink TBF. The mobile station shall, in either BTTC or RTTI configuration, ignore the USF on those higher numbered PDCHs or PDCH-pairs with higher numbered timeslots during the block period where the assigned USF value is detected. In addition, if USF\_GRANULARITY is set to four blocks allocation, it may ignore the USF on all other PDCHs/PDCH-pairs during the first three block periods in which the mobile station has been granted permission to transmit. As specified in 3GPP TS 45.002, the USF corresponding to the last three blocks of a four blocks allocation shall be set to an unused value for each PDCH/PDCH-pair on which the mobile station has been granted permission to transmit. + +The mobile station shall, during a basic or reduced radio block period in which it has been granted permission to transmit, monitor the assigned USF on the downlink PDCHs/PDCH-pairs corresponding to its assigned uplink PDCHs/PDCH-pairs starting with the lowest numbered PDCH or PDCH-pair with the lowest numbered timeslots up to the highest numbered PDCH or PDCH-pair with the highest numbered timeslots which the mobile is able to monitor, taking into account the PDCHs/PDCH-pairs allocated for transmission in the basic or reduced radio block period and the switching requirements of the mobile station multislot class (see 3GPP TS 45.002). A mobile station in DTR mode shall only monitor the assigned USF on the downlink PDCH/PDCH-pair indicated in DTR information (see sub-clause 8.1.8). + +If the network wishes to reduce the number of PDCHs/PDCH-pairs allocated to a mobile station per basic/reduced radio block period, the network may do so, provided that this is compatible with the mobile station's ability to monitor the assigned USF in the downlink PDCH/PDCH-pairs corresponding to the lowest numbered uplink PDCH or PDCH-pair with the lowest numbered timeslots in the new allocation. Otherwise, the network shall not allocate any resources to that mobile station for one basic/reduced radio block period following the basic/reduced radio block period with the higher number of PDCHs/PDCH-pairs allocated. + +During the downlink block period where an uplink basic/reduced TTI radio block is allocated on a PDCH/PDCH-pair via the polling mechanism (see sub-clause 10.4.4), the mobile station shall monitor the assigned USF on the downlink PDCHs/PDCH-pairs corresponding to its assigned uplink PDCHs/PDCH-pairs starting with the lowest numbered PDCH or PDCH-pair with the lowest numbered timeslots up to the highest numbered PDCH or PDCH-pair with the highest numbered timeslots which is feasible when taking into account the PDCHs/PDCH-pairs allocated for transmission in the basic/reduced radio block period and the switching requirements of the mobile station multislot class (see 3GPP TS 45.002). + +#### 8.1.1.2.2 PACCH operation + +The mobile station shall attempt to decode every downlink RLC/MAC block on the downlink PDCH corresponding to (i.e. with the same timeslot number as) the lowest numbered timeslot in the PDCH assignment when the uplink TBF operates in the BTTI configuration. A mobile station operating in DTR mode (see sub-clause 8.1.8) shall attempt to decode every RLC/MAC block on a downlink PDCH which the mobile station is required to monitor for the assigned USF as indicated in the DTR information as specified in sub-clause 8.1.1.2.1. + +In case the uplink TBF operates in RTTI configuration the mobile station shall attempt to decode every downlink RLC/MAC block on the corresponding downlink PDCH-pair associated with the lowest numbered assigned uplink PDCH-pair (i.e. with lowest time slot numbers) in the set of assigned uplink PDCH-pairs (i.e. downlink PACCH blocks are received in the same mode as the assigned uplink TBF). A mobile station operating in DTR mode (see sub-clause 8.1.8) shall attempt to decode every RLC/MAC block on a downlink PDCH-pair which the mobile station is required to monitor for the assigned USF as indicated in the DTR information as specified in sub-clause 8.1.1.2.1. + +Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message addresses the mobile station, the mobile station shall act on the message. + +In case the uplink TBF operates in BTTI configuration then the network shall transmit all PACCH messages on the PDCH carried on the downlink timeslot corresponding to the lowest numbered timeslot in the assignment. Additionally for the concurrent TBF case, the network may transmit PACCH messages on any of the common timeslots assigned to the downlink and uplink PDCH assignment. + +In case the uplink TBF operates in RTTI configuration then the network shall transmit all PACCH messages on the corresponding downlink PDCH-pair associated with the lowest numbered assigned uplink PDCH-pair. Additionally, for the concurrent TBF case, the network may transmit PACCH messages on any of the PDCH-pairs assigned that are common to the downlink and uplink PDCH-pair assignments. + +In case the uplink TBF operates in MTI configuration, then the network shall transmit all PACCH messages on the PDCH or PDCH-pair that uses the lowest numbered timeslot in the MTI configuration. Additionally, for the case of concurrent uplink and downlink TBFs, the network may transmit PACCH messages on any PDCH or PDCH-pair which is common to the uplink and downlink resource assignments. + +Whenever a mobile station, that has an assigned uplink TBF that operates in BTTI configuration, detects an assigned USF value on any monitored PDCH, the mobile station may transmit a PACCH block on the same PDCH in the next block period. Whenever a mobile station, that has an assigned uplink TBF that operates in RTTI configuration, detects an assigned USF value on any corresponding downlink PDCH-pair associated with an assigned uplink PDCH-pair, the mobile station may transmit a PACCH block on the PDCH-pair. The PACCH block shall be transmitted according to + +the USF scheduling in 8.1.1.2.1. The mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see sub-clauses 10.4.4, 10.4.4a, 10.4.4b) unless the uplink TBF operates in either RTTI configuration, or in BTTI configuration with FANR activated, and the mobile station is polled for a Piggy-backed Ack/Nack (see sub-clause 10.4.4b). + +In the case of a Downlink Dual Carrier configuration or a DLMC configuration, all segments belonging to each RLC/MAC control message shall be sent on PACCH blocks belonging to the same carrier. + +When a mobile station in a DLMC configuration supporting more than 20 downlink timeslots sends an EGPRS Packet Downlink Ack/Nack DLMC message (see sub-clause 11.2.48) it shall be coded using CS-1 or CS-3 as indicated by the most recently received assignment message. Otherwise, if it supports 20 or less downlink timeslots, EGPRS Packet Downlink Ack/Nack DLMC messages shall be coded using CS-1. + +#### 8.1.1.2.3 Neighbour cell power measurements + +The mobile station shall perform neighbour cell measurements during any unused PDCH or group of unused PDCHs where the MS's Measurement Capabilities indicate that the mobile station is capable of making a neighbour cell measurement. + +The network shall ensure that there are sufficient gaps as to allow the necessary number of measurements based upon the MS's Measurement Capabilities. + +#### 8.1.1.2.4 Shifted USF operation + +In some instances (see 3GPP TS 45.002), Shifted USF operation shall apply. + +When Shifted USF operation is used, the USF for the first assigned uplink PDCH shall be sent on the downlink PDCH corresponding to (i.e. with the same timeslot number as) the second assigned uplink PDCH. The MS shall monitor this downlink PDCH for the USF corresponding to both the first assigned uplink PDCH and the second assigned uplink PDCH. If the USF corresponding to the first assigned uplink PDCH is detected then operation shall be as described in sub-clause 8.1.1.2.1. for the case where the assigned USF was received on the downlink PDCH corresponding to the first assigned uplink PDCH. Otherwise, operation shall be as described in sub-clause 8.1.1.2.1. + +The USF value corresponding to the first assigned uplink PDCH shall be different from the USF value corresponding to the second assigned uplink PDCH. + +When Shifted USF operation is used, PACCH operation shall be as described in sub-clause 8.1.1.2.2 except that the network shall transmit all PACCH messages on the PDCH carried on the downlink timeslot corresponding to the second lowest numbered timeslot in the uplink assignment, and the mobile station shall attempt to decode every downlink RLC/MAC block on that downlink PDCH. + +If a PACKET PDCH RELEASE message releases the second uplink PDCH in the current timeslot configuration of a mobile station using Shifted USF operation then the first uplink timeslot shall also be considered released. If any PDCHs remain in the new timeslot configuration then normal USF operation shall continue starting on the lowest available timeslot. + +#### 8.1.1.3 (void) + +#### 8.1.1.3a Exclusive allocation RLC data block transfer + +##### 8.1.1.3a.1 General + +This sub-clause specifies mobile station behaviour for *exclusive allocation* of radio resources for uplink RLC data block transfer. The exclusive allocation is applicable only in dual transfer mode (for half-rate PDCHs only) and MAC-DTM state (for half-rate PDCHs only). The conditions for using exclusive allocation are specified in sub-clause 8.1.0. + +When the mobile station receives an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE) that does not contain a TBF starting time, the mobile station shall switch to the assigned PDCHs and be ready to transmit within the reaction time defined in 3GPP TS 45.010. If a TBF starting time is present, the mobile station shall wait until the starting time before it switches to the assigned PDCHs and starts to transmit. If a TBF starting time is present and an uplink TBF or one or more downlink TBFs are already in progress, the mobile station shall continue to use the previously assigned resources for the uplink TBF until the TBF starting time occurs. If the + +mobile station receives another uplink assignment, while waiting for the TBF starting time, the mobile station shall act upon the most recently received uplink assignment and shall ignore the previous one. + +When mobile station has received the uplink assignment and been granted the right to transmit using exclusive allocation, the mobile station shall start timer T3184 and transmit an RLC/MAC block in every uplink radio block on the PDCHs assigned for the TBF. The timer T3184 shall be restarted every time the mobile station receives a PACKET UPLINK ACK/NACK message. + +The timer T3184 shall be stopped at the release of the TBF. The timer T3184 shall also be stopped if the resources for the TBF are reallocated, such that the conditions for exclusive allocation are no longer fulfilled and the TBF continues using dynamic or extended dynamic allocation (see sub-clause 8.1.0). + +A mobile station supporting multiple TBF procedures and operating in DTM mode with exclusive allocation may only establish a single uplink TBF. However, one or more downlink TBFs may still be established when exclusive allocation is used for the uplink TBF. In this case the network may allocate the radio resources for the uplink TBF by sending the mobile station one of the following messages: + +- A PACKET UPLINK ASSIGNMENT message if there is no more than one concurrent downlink TBF; +- A MULTIPLE TBF UPLINK ASSIGNMENT message if there are multiple concurrent downlink TBFs; +- A PACKET TIMESLOT RECONFIGURE message if there is one concurrent downlink TBF that is also being reallocated; +- A MULTIPLE TIMESLOT RECONFIGURE message if there are multiple concurrent downlink TBFs and at least one of them is being reallocated or there are multiple concurrent downlink TBFs and resources for at least one new downlink TBF are being allocated. + +#### 8.1.1.3a.2 Radio link failure + +If timer T3184 expires (see sub-clause 8.1.1.3a.1), the mobile station shall regard that as a radio link failure and perform an abnormal release with access retry (see sub-clause 8.7.2). + +The network shall increment counter N3101 for each radio block allocated to the TBF for which no RLC/MAC block is received. Whenever the network receives an RLC/MAC block from the mobile station, it shall reset counter N3101 for that TBF. If N3101 reaches the value N3101max, the network shall stop sending PACKET UPLINK ACK/NACK messages to the mobile station for that TBF and shall start timer T3169 for the TBF. If an RLC/MAC block is received from the TBF when timer T3169 is running, the network shall stop timer T3169 and resume sending PACKET UPLINK ACK/NACK messages to the TBF. When T3169 expires, the network may consider the TBF as released and reuse the TFI value(s). If PS Handover is ongoing, it is optional for the network to increment N3101. + +#### 8.1.1.3a.3 (void) + +#### 8.1.1.3a.4 PACCH operation + +The mobile station shall attempt to decode every downlink RLC/MAC block on the PDCH with the lowest timeslot number assigned for an uplink TBF operating in BTTI configuration and shall attempt to decode every downlink RLC/MAC block on the PDCH-pair with the lowest timeslot numbers assigned for an uplink TBF operating in RTTI configuration. Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message is a distribution message or a non-distribution message that addresses the mobile station, the mobile station shall act on the message. + +During the transmission on the uplink TBF, the mobile station may use any uplink RLC/MAC block, assigned for the uplink TBF, for the transmission of an RLC/MAC control block (PACCH). The mobile station shall not transmit an RLC data block in any uplink RLC/MAC block allocated to the mobile station via the polling mechanism (see sub-clause 10.4.4). + +#### 8.1.1.3a.5 Resource Reallocation for Uplink + +##### 8.1.1.3a.5.1 General + +The reallocation of radio resources may take place during an uplink TBF, due to a change of service demand from the mobile station, or due to reasons determined by the network. This procedure shall not be used to change neither the RLC mode nor the TBF mode of the uplink TBF. A change of RLC mode or TBF mode shall be achieved through the release of the uplink TBF and establishment of a new TBF. + +#### 8.1.1.3a.5.2 Change of service demand + +During an uplink packet transfer, upper layers may request the transfer an upper layer PDU with a different PFI, a different radio priority, a different peak throughput class or a different RLC mode than the one, which is in transfer. In case of an upper layer PDU containing signalling information, it shall be transferred with the highest radio priority and requesting acknowledged RLC mode. + +If upper layers request the transfer of another upper layer PDU with a different PFI, a different Radio Priority, a different peak throughput class or a different RLC mode than the one which is in transfer, then the procedures as described in packet transfer mode (see sub-clause 8.1.1.1.2) shall be applied by the mobile station. + +If the mobile station, at the change of service demand, has started the countdown procedure (see sub-clause 9.3.1) in order to release the uplink TBF, the mobile station shall perform the release of the uplink TBF as normal. The mobile station may then establish a new uplink TBF, according to the new service demand. + +If the countdown procedure has not been started or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and the new upper layer PDU shall be transferred with the same RLC mode as the current uplink TBF, the mobile station shall indicate a change of service demand to the network by sending a PACKET RESOURCE REQUEST message on PACCH. + +When the PACKET RESOURCE REQUEST message is sent, the mobile station shall start timer T3168. + +If the new upper layer PDU shall be transmitted with a different RLC mode than the current uplink TBF, the mobile station may complete the transmission of the preceding upper layer PDUs and shall then release the TBF and establish a new uplink TBF for transmission of the new upper layer PDU. If the TBF is operated in extended TBF mode (see sub-clause 9.3.1b), the mobile station shall use the procedure in sub-clause 8.1.1.6 for changing the RLC mode. + +After the transmission of the PACKET RESOURCE REQUEST message, the mobile station shall continue to use the currently assigned uplink TBF, assuming that the network grants the requested service demand. + +On receipt of the PACKET RESOURCE REQUEST message the network shall respond by either the reallocation of radio resources for an uplink TBF (sub-clause 8.1.1.3a.5.3) or the rejection of service demand (sub-clause 8.1.1.3a.5.4). + +The mobile station shall stop timer T3168 at the receipt of a PACKET UPLINK ASSIGNMENT, a MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message, or when the mobile station has completed its currently assigned TBFs. If timer T3168 expires, the mobile station shall retransmit the PACKET RESOURCE REQUEST message and again start timer T3168. + +#### 8.1.1.3a.5.3 Reallocation of radio resources for an uplink TBF + +The network may reallocate the radio resources for an uplink TBF by sending the mobile station a PACKET UPLINK ASSIGNMENT or a PACKET CS RELEASE INDICATION message if there is no more than one concurrent downlink TBF or a MULTIPLE TBF UPLINK ASSIGNMENT or a PACKET CS RELEASE INDICATION message if there are multiple concurrent downlink TBFs. If there is a concurrent downlink TBF and the radio resources for the downlink TBF are also affected, the network shall use a PACKET TIMESLOT RECONFIGURE or a PACKET CS RELEASE INDICATION message for the reallocation. If there are multiple concurrent downlink TBFs and the radio resources for at least one downlink TBF are also affected, the network shall use a MULTIPLE TBF TIMESLOT RECONFIGURE or a PACKET CS RELEASE INDICATION message for the reallocation. + +On receipt of the PACKET UPLINK ASSIGNMENT, the MULTIPLE TBF UPLINK ASSIGNMENT, the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or the PACKET CS RELEASE INDICATION message, the mobile station shall treat the message as an uplink assignment, as defined in sub-clause 8.1.1.1.2. On receipt of the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or the PACKET CS RELEASE INDICATION message, the mobile station shall, in addition, treat the message as a downlink assignment, as defined in sub-clause 8.1.2.1. + +#### 8.1.1.3a.5.4 Rejection of new service demand + +On the receipt of a PACKET RESOURCE REQUEST message from the mobile station indicating a change of service demand, the network may reject the service demand by sending a PACKET ACCESS REJECT message to the mobile station. + +On receipt of the PACKET ACCESS REJECT message, the mobile station shall stop timer T3168 if running, abort the uplink TBF and indicate a packet access failure to upper layers. If no downlink TBF exists, the mobile station in dual + +transfer mode shall return to dedicated mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. + +The PACKET ACCESS REJECT message may contain a wait indication (i.e. the WAIT\_INDICATION field) in the Reject structure addressed to the mobile station. In that case, the mobile station shall start timer T3172 with the indicated value. The mobile station shall not attempt to establish a new uplink TBF in the same cell while timer T3172 is running. If a successful cell reselection is performed, the mobile station shall stop timer T3172 and may establish an uplink TBF in the new cell. + +While timer T3172 is running, the mobile station shall ignore any PACKET PAGING REQUEST message that may be received, except paging requests to trigger RR connection establishment and paging request including MBMS notification. + +#### 8.1.1.3a.5.5 Abnormal cases + +The following abnormal cases apply: + +- If timer T3168 expires and the PACKET RESOURCE REQUEST message has already been transmitted four times, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the mobile station receives an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +#### 8.1.1.3a.6 Establishment of Downlink TBF + +##### 8.1.1.3a.6.1 General + +During an uplink TBF using exclusive allocation, the network may initiate the establishment of one or more downlink TBFs by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) to the mobile station on the PACCH. If multiple TBF procedures are not supported the PACKET TIMESLOT RECONFIGURE message shall be used if the timeslot allocation for the on-going uplink TBF needs to be changed. If the mobile station and network support multiple TBF procedures the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE and MULTIPLE TBF TIMESLOT RECONFIGURE messages shall be used as described in sub-clause 8.1.1.1.3. + +On receipt of the downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) the mobile station shall switch to the assigned PDCHs. If the assignment message includes a TBF starting time, the mobile station shall first wait until the indicated starting time and then switch to the assigned PDCHs. If the assigning message does not include a TBF starting time, or the TBF starting time has already passed when the assigning message is received, the mobile station shall switch to the assigned PDCHs within the reaction time specified in 3GPP TS 45.010. + +When the mobile station switches to the assigned PDCHs, it starts timer T3190 for each downlink TBF assigned. The operation of the downlink TBFs then follows the procedures defined in sub-clause 8.1.2, with the following additions: + +- The mobile station shall prioritise transmission of RLC/MAC control blocks associated with a downlink TBF over RLC/MAC control blocks associated with the uplink TBF; +- If a timer or counter expiry causes the uplink TBF to be aborted in the mobile station, the mobile station shall perform an abnormal release according to the procedure defined for the uplink TBF, which may cause also the downlink TBF to be aborted; +- If one uplink and one downlink TBF are established, the network may send a PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message without the + +UPLINK\_TFI\_ASSIGNMENT field. The mobile station shall interpret this as a reassignment of the concurrent uplink and downlink TBFs. The TFI of the uplink TBF is not changed. + +#### 8.1.1.3a.6.2 Abnormal cases + +If a failure occurs on the mobile station side before the downlink TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If the information in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a downlink TBF is not already established and the PACKET TIMESLOT RECONFIGURE message does not include a DOWNLINK\_TFI\_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station in dual transfer mode receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT message is due to any other reason, the mobile station shall abort the procedure and continue the normal operation of the ongoing uplink and downlink TBFs. + +#### 8.1.1.3b Fixed Uplink Allocation RLC data block transfer + +This sub-clause specifies the behaviour for fixed uplink allocation RLC data block transfer while in packet transfer mode with an uplink EC TBF. The downlink allocation follows the procedures as described in sub-clause 8.1.2. + +When the mobile station receives a Fixed Uplink Allocation, FUA, in e.g. the EC PACKET UPLINK ASSIGNMENT or EC PACKET UPLINK ACK/NACK message it shall perform uplink transmissions according to that allocation. The uplink resources are allocated with respect to a BTTI configuration, the mobile station uplink coverage class, the assigned MCS, the number of RLC data blocks required for the EC TBF as indicated by the mobile station and with respect to the latest ack/nack status as perceived by the network, if such exists, and transmitted to the mobile station in the message containing the FUA. The uplink resources will be allocated according to the coverage class dependent resource mapping (see 3GPP TS 45.002) and the mobile station shall transmit accordingly. + +The uplink EC TBF assignment also includes resources for reception of control messages on EC-PACCH/D as a function of the uplink allocated resources. + +Since fixed uplink allocation is used on the uplink, the network will always know the BSN transmitted by the mobile station within each RLC data block, and hence need not rely on RLC/MAC header decoding to acquire the BSN for the purpose of chase combining or incremental redundancy. One exception may apply in case the data to be transmitted by the mobile station can, due to the use of an MCS different from MCS-1, be contained in fewer RLC data blocks than allocated by the network. In that case the excessively allocated RLC data block will contain a pre-emptive uplink transmission, see 9.3.2.3 + +The BSN\_OFFSET field in the fixed uplink allocation defines the offset, in the list of available RLC data blocks for transmission, which shall be applied by the mobile station when selecting the RLC data blocks to transmit in the fixed uplink allocation. If the BSN\_OFFSET field is not present, the mobile station shall select the RLC data blocks to transmit in the resources within the fixed uplink allocation as described in sub-clause 9.1.3.4. If the BSN\_OFFSET field is present, the mobile station shall apply an offset in RLC data blocks and skip one, or several, of the RLC data blocks that would be transmitted first according to the procedures in sub-clause 9.1.3.4. In case pre-emptive transmission is required for the fixed uplink allocation, see sub-clause 9.3.2.3, the skipped RLC data blocks shall still be included when selecting RLC data blocks for pre-emptive retransmission. + +During the time between reception of the message containing the fixed uplink allocation until the time of transmission of the last radio block of the fixed uplink allocation, the mobile station shall not monitor the EC-PACCH on the downlink. + +When the last radio block is transmitted according to the fixed uplink allocation, the mobile station shall start timer T3226. When T3226 expires the mobile station shall start T3228 and monitor the EC-PACCH, see sub-clause 8.1.1.3b.1. If the mobile station receives an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressed to it, it shall act on the message and stop timer T3228. + +The network shall start timer T3227 after the last allocated RLC data block of the fixed uplink allocation. When timer T3227 expires, the network shall (re)start timer T3229. The network shall then send the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station. + +The mobile station is only allowed to transmit RLC data blocks in the fixed uplink allocation resources, i.e. no RLC/MAC control messages shall be sent. + +#### 8.1.1.3b.1 EC-PACCH operation + +When timer T3226 expires, the mobile station shall monitor the EC-PACCH according to its assigned downlink coverage class and, as long as T3228 is running, attempt to decode every downlink RLC/MAC block on the PDCHs corresponding to the downlink assigned EC-PACCH resources. + +Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message addresses the mobile station, the mobile station shall act on the message. + +If timer T3228 expires, the mobile station shall release the ongoing uplink TBF and may perform an abnormal release with access retry, unless timer T3248 (sent in EC-SI) is used. If T3248 is used, i.e. it has a value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH using the next higher DL Coverage Class, if such exists. If no higher DL CC than the assigned DL CC exists, the mobile station shall continue to monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message according to the last assigned DL CC until T3248 expires. + +The assigned resources (timeslots) to be used for the downlink EC-PACCH according to the next higher DL Coverage Class are either the same as the assigned timeslots for the uplink EC-PDTCH or given in the assignment message. If no valid resources for the next higher Coverage Class are assigned, the mobile station shall continue to monitor the downlink EC-PACCH using the assigned DL Coverage Class while timer T3248 is running. + +When the mobile station receives an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with its uplink TBF it shall stop T3228, if running. If timer T3248 was running at reception of the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message (and thus not T3228), the timer T3248 shall be stopped. + +At expiry of T3248, the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed. + +The mobile station is only reachable on the EC-PACCH once timer T3227 has expired. When timer T3227 expires, the network shall start timer T3229 and send the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station. The network may send additional EC PACKET UPLINK ACK/NACK messages or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages to the mobile station while timer T3229 is running. The network should then however take into account that the mobile station will stop monitoring the EC-PACCH at reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, addressed to it, with a fixed uplink allocation. If the network receives uplink data from the mobile station, on the resources that are part of the fixed uplink allocation, the network shall stop timer T3229, if running. + +If timer T3249 (sent in EC-SI) is not used, the network may release the TBF and reuse the TFI resource when timer T3229 has expired and no uplink data has been received according to the fixed uplink allocation sent to the mobile station in an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message before expiry of timer T3229. If timer T3249 is used, i.e. it has a value > 0, it shall be started at expiry of T3229. The network may send the EC PACKET UPLINK ACK/NACK messages or the EC + +PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station using the next higher DL Coverage Class compared to the assigned DL Coverage Class, if such exists, while T3249 is running. When timer T3249 has expired and no uplink data has been received on the resources assigned in the fixed uplink allocation sent to the mobile station in an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message before expiry of timer T3249 (or preceding T3229), the network may release the TBF and reuse the TFI resource. + +#### 8.1.1.3b.2 Prolonged Resources for Uplink transmission + +During an EC TBF, upper layers of the mobile station may request to transfer upper layer PDUs not accounted for in the initial resource request. The mobile station may then prolong the uplink TBF by including a Countdown Value, CV, that indicates a later end of the TBF than previously indicated, unless CV=0 has already been indicated in an RLC uplink data block, see sub-clause 9.3.1 for the countdown procedure. + +#### 8.1.1.3b.3 Abnormal cases + +The following abnormal cases apply: + +- If the information in the EC PACKET UPLINK ACK/NACK message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the uplink assignment message (e.g. EC PACKET UPLINK ACK/NACK message) is due to any other reason the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +#### 8.1.1.3b.4 Establishment of Downlink TBF + +The network may establish a downlink EC TBF at release of the uplink EC TBF, as described in sub-clause 9.3.2.4.3. + +#### 8.1.1.4 Network initiated release of uplink TBF + +The network may initiate release of an uplink TBF by transmitting a PACKET TBF RELEASE message to the mobile station on the PACCH. A cause value indicates the reason for release. + +If the cause value is "Normal release" the mobile station shall continue to the next upper layer PDU boundary, starting the count down procedure (see sub-clause 9.3.1) at whatever value of CV is appropriate to count down to zero at the upper layer PDU boundary, and then release the uplink TBF according to the procedures in sub-clause 9.3.2.3 or 9.3.3.3. If multiple TBF procedures are not supported and the mobile station has more upper layer PDU(s) to send, the mobile station may initiate the establishment of a new uplink TBF as defined in sub-clause 7.1, 8.1.1. If the mobile station and network support multiple TBF procedures the mobile station may initiate the establishment of one or more new uplink TBFs as defined in sub-clause 8.1.1 and 8.1.1.1.2. If the uplink TBF is using EMST, the mobile station shall release the uplink TBF by releasing each RLC entity allocated to this TBF as specified in sub-clause 9.3.2.3 or 9.3.3.3. + +If the cause value is "Abnormal Release", the mobile station shall abort the uplink TBF and perform an abnormal release with access retry (see sub-clause 8.7.2). If a valid RRBP field is received as part of the PACKET TBF RELEASE message, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified. + +#### 8.1.1.5 Abnormal cases + +The following abnormal cases apply: + +- if the mobile station receives a PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS RELEASE INDICATION message with an invalid Frequency Parameters information element, the mobile station shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information; +- if the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS + +RELEASE INDICATION message specifying frequencies that are not all in one band then the mobile shall perform an abnormal release with access retry (see sub-clause 8.7.2); + +- if a mobile station in dual transfer mode receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- if the mobile station receives a PACKET UPLINK ACK/NACK, an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message with missing mandatory fields, the MS shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- if the mobile station is operating in the non-extended uplink TBF mode (see sub-clause 9.3.1b) and the mobile station has not started, or has started but not completed the countdown procedure for a given TBF and it receives a PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator set for that TBF, it shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +NOTE: A PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS RELEASE INDICATION message sent to a multi-band mobile station shall not be considered invalid if it indicates new frequencies that are all in a different frequency band to that of the ARFCN of the serving cell. + +#### 8.1.1.6 Change of RLC mode in extended uplink TBF mode + +##### 8.1.1.6.1 General + +This procedure applies to a mobile station having an uplink TBF in extended uplink TBF mode. The procedure shall be used to release the ongoing uplink TBF and to setup a new TBF in another RLC mode. + +##### 8.1.1.6.2 Change of RLC mode + +The mobile station shall send a PACKET RESOURCE REQUEST message on PACCH indicating the new RLC mode and start timer T3168. + +If timer T3168 expires, the mobile station shall retransmit the PACKET RESOURCE REQUEST message and restart timer T3168. + +On receipt of a PACKET RESOURCE REQUEST message, indicating a change of RLC mode, the network shall release the uplink TBF at a point determined by the network, using the procedure defined in sub-clause 9.5. + +On receipt of PACKET UPLINK ACK/NACK with Final Ack Indicator set to '1' the mobile station shall stop timer T3168 and after sending the PACKET CONTROL ACKNOWLEDGEMENT message perform the change of RLC mode by establishing a new TBF. + +##### 8.1.1.6.3 Abnormal cases + +The following abnormal cases apply: + +- If timer T3168 expires and the PACKET RESOURCE REQUEST message has already been transmitted four times, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +#### 8.1.1.7 Change of EGPRS level + +##### 8.1.1.7.1 Change of EGPRS level for downlink TBFs + +The network may indicate to the mobile station that the EGPRS level applicable to a downlink TBF shall be changed. The mobile station shall not consider any transition (to or from any EGPRS level) to be an error, provided that the mobile station supports the new EGPRS level in the downlink. In EC operation the only level supported is EGPRS. + +### 8.1.1.7.2 Change of EGPRS level for uplink TBFs + +The network may indicate to the mobile station that the EGPRS level applicable to an uplink TBF shall be changed. The transitions which can be performed are shown in table 8.1.1.7.2.1. + +**Table 8.1.1.7.2.1: Permitted EGPRS level changes** + +| Current EGPRS level | New EGPRS Level | +|---------------------|-----------------| +| EGPRS | EGPRS2-A | +| EGPRS | EGPRS2-B | +| EGPRS2-B | EGPRS | +| EGPRS2-A | EGPRS | + +In EC operation the only level supported is EGPRS. + +Transitions not listed in Table 8.1.1.7.2.1 are not permitted. + +The modulation and coding scheme to be used for retransmissions in case of a transition from EGPRS to EGPRS2-A (respectively EGPRS2-B) is shown in Table 8.1.1.7.2.2 (respectively Table 8.1.1.7.2.3) below. + +**Table 8.1.1.7.2.2: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-A)** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS2-A (MCS or UAS) | | | | | +|--------------------------------------|----------------------------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | UAS-11 Commanded | UAS-10 Commanded | UAS-9 Commanded | UAS-8 Commanded | UAS-7 Commanded | +| MCS-9 | UAS-9 | UAS-9 | UAS-9 | MCS-6 | MCS-6 | +| MCS-8 | MCS-6 (NOTE 2) | | | | | +| MCS-7 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | +| MCS-6 | UAS-9 | UAS-9 | UAS-9 | MCS-6 | MCS-6 | +| MCS-5 | UAS-10 | UAS-10 | UAS-7 | UAS-7 | UAS-7 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +NOTE 1: If MCS-1 to MCS-6 is commanded, see Table 8.1.1.1 or Table 8.1.1.2 as appropriate. +NOTE 2: In this case, 6 octets of padding are used. + +**Table 8.1.1.7.2.3: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-B) with re-segmentation** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS2-B (MCS or UBS) | | | | | | | | +|--------------------------------------|----------------------------------------------------------------------------|------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | UBS-12 Commanded | UBS-11 Commanded | UBS-10 Commanded | UBS-9 Commanded | UBS-8 Commanded | UBS-7 Commanded | UBS-6 Commanded | UBS-5 Commanded | +| MCS-9 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | +| MCS-8 | UBS-11 | UBS-11 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | +| MCS-7 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | +| MCS-6 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | +| MCS-5 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.1. + +**Table 8.1.1.7.2.4a: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-B) without re-segmentation** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS2-B (MCS or UBS) | | | | | | | | +|--------------------------------------|----------------------------------------------------------------------------|------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | UBS-12 Commanded | UBS-11 Commanded | UBS-10 Commanded | UBS-9 Commanded | UBS-8 Commanded | UBS-7 Commanded | UBS-6 Commanded | UBS-5 Commanded | +| MCS-9 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | +| MCS-8 | UBS-11 | UBS-11 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | +| MCS-7 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | +| MCS-6 | UBS-12 | UBS-10 | UBS-10 | UBS-8 | UBS-8 | UBS-6 | UBS-6 | UBS-6 | +| MCS-5 | UBS-9 | UBS-9 | UBS-9 | UBS-9 | UBS-7 | UBS-7 | UBS-5 | UBS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +**Table 8.1.1.7.2.4b: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-B) without re-segmentation** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS2-B (MCS or UBS) | | | | +|--------------------------------------|----------------------------------------------------------------------------|-----------------|-----------------|-----------------| +| | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | +| MCS-9 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | +| MCS-8 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | +| MCS-7 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | +| MCS-6 | UBS-6 | UBS-6 | UBS-6 | UBS-6 | +| MCS-5 | UBS-5 | UBS-5 | UBS-5 | UBS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +The modulation and coding scheme to be used for retransmissions in case of a transition from EGPRS2-A (respectively EGPRS2-B) to EGPRS is shown in Tables 8.1.1.7.2.5 and 8.1.1.7.2.6 (respectively Tables 8.1.1.7.2.7 and 8.1.1.7.2.8) below. + +**Table 8.1.1.7.2.5: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-A, level changed to EGPRS) with re-segmentation** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS (MCS) | | | | | | | +|--------------------------------------|------------------------------------------------------------------|-----------------|-----------------|-------------------|-----------------|-------------------|-----------------| +| | MCS-9 Commanded | MCS-8 Commanded | MCS-7 Commanded | MCS-6-9 Commanded | MCS-6 Commanded | MCS-5-7 Commanded | MCS-5 Commanded | +| | | | | | | | | + +| | | | | | | | | +|------------------------------------------------------------|-------------------|-------------------|-------------------|-------------------|-------------------|-------------------|-------------------| +| UAS-11 | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-3
(NOTE 2) | MCS-3
(NOTE 2) | +| UAS-10 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| UAS-9 | MCS-9 | MCS-6 | MCS-6 | MCS-9 | MCS-6 | MCS-3 | MCS-3 | +| UAS-8 | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-3
(NOTE 2) | MCS-3
(NOTE 2) | +| UAS-7 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| MCS-6 | MCS-9 | MCS-6 | MCS-6 | MCS-9 | MCS-6 | MCS-3 | MCS-3 | +| MCS-5 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | +| NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.3. | | | | | | | | +| NOTE 2: In this case, 10 octets of padding are used. | | | | | | | | + +**Table 8.1.1.7.2.6: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-A, level changed to EGPRS) without re-segmentation** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS (MCS) | | | | | | | +|------------------------------------------------------------|------------------------------------------------------------------|-------------------|-------------------|-------------------|-------------------|-------------------|-------------------| +| | MCS-9 Commanded | MCS-8 Commanded | MCS-7 Commanded | MCS-6-9 Commanded | MCS-6 Commanded | MCS-5-7 Commanded | MCS-5 Commanded | +| UAS-11 | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | +| UAS-10 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| UAS-9 | MCS-9 | MCS-6 | MCS-6 | MCS-9 | MCS-6 | MCS-6 | MCS-6 | +| UAS-8 | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | MCS-6
(NOTE 2) | +| UAS-7 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| MCS-6 | MCS-9 | MCS-6 | MCS-6 | MCS-9 | MCS-6 | MCS-6 | MCS-6 | +| MCS-5 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | +| NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.4. | | | | | | | | +| NOTE 2: In this case, 10 octets of padding are used. | | | | | | | | + +**Table 8.1.1.7.2.7: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-B, level changed to EGPRS) with re-segmentation** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS (MCS) | | | | | | | +|--------------------------------------|------------------------------------------------------------------|-----------------|-----------------|-------------------|-----------------|-------------------|-----------------| +| | MCS-9 Commanded | MCS-8 Commanded | MCS-7 Commanded | MCS-6-9 Commanded | MCS-6 Commanded | MCS-5-7 Commanded | MCS-5 Commanded | +| | | | | | | | | + +| | | | | | | | | +|--------|------------------------------|------------------------------|-------|-------|-------|-------|-------| +| UBS-12 | MCS-9 | MCS-6 | MCS-6 | MCS-9 | MCS-6 | MCS-3 | MCS-3 | +| UBS-11 | MCS-8 | MCS-8 | MCS-6 | MCS-6 | MCS-6 | MCS-3 | MCS-3 | +| UBS-10 | MCS-8 /
MCS-9
(NOTE 2) | MCS-8 /
MCS-6
(NOTE 2) | MCS-6 | MCS-9 | MCS-6 | MCS-3 | MCS-3 | +| UBS-9 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| UBS-8 | MCS-8 /
MCS-9
(NOTE 2) | MCS-8 /
MCS-6
(NOTE 2) | MCS-6 | MCS-9 | MCS-6 | MCS-3 | MCS-3 | +| UBS-7 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| UBS-6 | MCS-8 /
MCS-9
(NOTE 2) | MCS-8 /
MCS-6
(NOTE 2) | MCS-6 | MCS-6 | MCS-6 | MCS-3 | MCS-3 | +| UBS-5 | MCS-7 | MCS-7 | MCS-7 | MCS-5 | MCS-5 | MCS-7 | MCS-5 | +| MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.5. + +NOTE 2: If the last transmission was with padding, then MCS-8 is used; otherwise, the alternative coding scheme specified above is used. + +**Table 8.1.1.7.2.8: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-B, level changed to EGPRS) without re-segmentation** + +| Scheme used for Initial transmission | Scheme to use for retransmissions after switching to EGPRS (MCS) | | | | | | | +|--------------------------------------|------------------------------------------------------------------|-------------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | MCS-9 or MCS-8 or MCS-7 or MCS-6-9 or MCS-6 Commanded | MCS-5-7 Commanded | MCS-5 Commanded | MCS-4 Commanded | MCS-3 Commanded | MCS-2 Commanded | MCS-1 Commanded | +| UBS-12 | MCSs defined in Table 8.1.1.7.2.7 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| UBS-11 | MCSs defined in Table 8.1.1.7.2.7 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| UBS-10 | MCSs defined in Table 8.1.1.7.2.7 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| UBS-9 | MCSs defined in Table 8.1.1.7.2.7 | MCS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| UBS-8 | MCSs defined in Table 8.1.1.7.2.7 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| UBS-7 | MCSs defined in Table 8.1.1.7.2.7 | MCS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| UBS-6 | MCSs defined in Table 8.1.1.7.2.7 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | MCS-6 | +| UBS-5 | MCSs defined in Table 8.1.1.7.2.7 | MCS-7 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | MCS-5 | +| MCS-4 | MCSs defined in Table 8.1.1.7.2.7 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | MCS-4 | +| MCS-3 | MCSs defined in Table 8.1.1.7.2.7 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | MCS-3 | +| MCS-2 | MCSs defined in Table 8.1.1.7.2.7 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | MCS-2 | +| MCS-1 | MCSs defined in Table 8.1.1.7.2.7 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | MCS-1 | + +## 8.1.2 Downlink RLC data block transfer + +For a TBF in BTTI configuration, prior to the initiation of RLC data block transfer on the downlink, the network assigns the following parameters in a downlink assignment (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, EC PACKET DOWNLINK ASSIGNMENT, or PACKET CS RELEASE INDICATION) message: + +- a Temporary Flow Identity (TFI). The TFI applies to all radio blocks transferred in regards to: + - the downlink Temporary Block Flow (TBF) , + - or in case EMST is used, to the RLC entity allocated on the downlink TBF, + - or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on the downlink TBF; + - or for a DLMC configuration, to a downlink carrier assigned to the downlink TBF where different TFIs may be assigned for each carrier of the TBF; +- an eTFI, optionally assigned in case of a downlink TBF assigned to a MS supporting eTFI (see sub-clause 5.13); +- a set of PDCHs to be used for the downlink transfer; +- optionally, a TBF starting time indication (not applicable for dual carrier, multi carrier, BTTI with FANR activated, and EGPRS2 configurations); +- a PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures. In case EMST is supported by the network and the mobile station, the PFI associated with each allocated RLC entity. In case EMSR is enabled for one or more RLC entities of the allocated TBF, the assignment message indicates the PFI associated with each PFC supported by these RLC entities. +- in case of a downlink EC TBF, the network also assigns the following parameters: + - uplink and downlink coverage classes; + - a set of PDCHs to be used for transmission of uplink RLC/MAC control messages. + +In case RTTI configuration is supported by the network and the mobile station and a downlink TBF operating in RTTI configuration is assigned, the following parameters shall be provided by the network in the assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). + +- a Temporary Flow Identity (TFI). The TFI applies to all radio blocks transferred in regards to: + - the downlink Temporary Block Flow (TBF) , + - or in case EMST is used, to the RLC entity allocated on the downlink TBF, + - or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on the downlink TBF; + - or for a DLMC configuration, to a downlink carrier assigned to the downlink TBF where different TFIs may be assigned for each carrier of the TBF; +- an eTFI, optionally assigned in case of a downlink TBF assigned to a MS supporting eTFI (see sub-clause 5.13); +- one or more downlink PDCH-pairs to be used for the downlink transfer; +- a PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures. In case EMST is supported by the network and the mobile station, the PFI associated with each allocated RLC entity. In case EMSR is enabled for one or more RLC entities of the allocated TBF, the assignment message indicates the PFI associated with each PFC supported by these RLC entities. + +The network may, at any time during downlink packet transfer, change the TTI configuration of an already established downlink TBF by sending on the downlink PACCH a downlink TBF assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). In case of a TTI configuration change the mobile station shall begin using the new TTI configuration within the reaction time defined in 3GPP TS 45.010. + +For each TBF, the network shall prioritise RLC/MAC control blocks, not containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message, to be transmitted ahead of RLC data blocks for that TBF. If the network has no other RLC/MAC block to transmit, but wishes to transmit on the downlink, the network + +shall transmit an RLC/MAC control block containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message. + +For the case where EMST is used for a downlink TBF where eTFI values have been assigned, when a corresponding PAN is sent on the uplink applicable TFI and eTFI values are those associated with the RLC entity for which the PAN is sent. + +A mobile station shall only attempt to decode downlink radio blocks transmitted using a TSC it has been assigned. A mobile station that supports the extended TSC sets (see 3GPP TS 45.002 [32]) can have up to two TSCs assigned for a given PDCH and shall attempt to decode a downlink radio block it receives on that PDCH using its assigned TSC(s). + +#### 8.1.2.1 Downlink RLC data block transfer + +A network may send an unsolicited downlink assignment message to a mobile station. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.1.1.3. + +Upon reception of a downlink assignment that does not contain a TBF starting time the mobile station shall start timer T3190 for each downlink TBF assigned in the downlink assignment message and within the reaction time defined in 3GPP TS 45.010, it shall attempt to decode every downlink block on its assigned PDCHs. If the downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) contains a TBF starting time information element and there is no downlink TBF in progress, but one or more uplink TBFs are in progress, the mobile station shall remain on the assigned PDCHs until the TDMA frame number indicated by the TBF starting time, at which time the mobile station shall start timer T3190 for each downlink TBF assigned in the downlink assignment message and immediately begin decoding the assigned downlink PDCH(s). If the downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) contains a TBF starting time and there are one or more downlink TBFs already in progress, the mobile station shall continue to use the parameters of the downlink TBFs in progress until the TDMA frame number indicated in the TBF starting time occurs, at which time the mobile station shall immediately begin to use the new assigned downlink TBF parameters. The mobile station shall continue to use the newly assigned parameters of each downlink TBF until the TBF is either released or reconfigured. If while waiting for the frame number indicated by the TBF starting time the mobile station receives another downlink assignment for the TBF, the mobile station shall act upon the most recently received downlink assignment and shall ignore the previous downlink assignment. Procedures on receipt of a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message) while no TBF is in progress are specified in sub-clause 7.2.1.1. + +Subsequent assignment messages may be sent to a mobile station operating in a Downlink Dual Carrier configuration or DLMC configuration as described in sub-clause 8.1.1.1.3. + +A mobile station in DTR mode with a downlink TBF assigned shall monitor only one of the assigned PDCHs/PDCH-pairs, as specified in sub-clause 8.1.8. + +If the mobile station receives a valid RLC data block addressed to one of its TBFs, the mobile station shall restart timer T3190 for that TBF. In EGPRS/EC TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. + +If any given timer T3190 expires, the mobile station shall release that downlink TBF. If there are one or more uplink TBFs in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If any given timer T3190 expires and there are no other ongoing uplink TBFs in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1). + +Upon receipt of a PACKET TBF RELEASE or EC PACKET TBF RELEASE message referring to a downlink TBF, the mobile station shall follow the procedure in sub-clause 8.1.2.8. + +##### 8.1.2.1.1 Abnormal cases + +If a failure occurs on the mobile station side before one or more new TBFs have been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If a mobile station receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET + +TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) and detects an invalid Frequency Parameters information element in the message, it shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information; + +- If a mobile station in dual transfer mode receives a PACKET DOWNLINK ASSIGNMENT, a MULTIPLE TBF DOWNLINK ASSIGNMENT, a PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1); +- If the information in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the PACKET TIMESLOT RECONFIGURE message does not include a DOWNLINK\_TFI\_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the information available in the mobile station, after the reception of a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or EC PACKET DOWNLINK ASSIGNMENT message does not satisfactorily define a PDCH, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT/MULTIPLE TBF DOWNLINK ASSIGNMENT/ EC PACKET DOWNLINK ASSIGNMENT message; +- If the mobile station does not support Downlink Dual Carrier but receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message specifying different frequency parameters than those currently in effect for the uplink TBF (see sub-clause 5.5.1.7), the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT/ MULTIPLE TBF DOWNLINK ASSIGNMENT message and continue normal operation of the uplink TBF; +- If the mobile station supports Downlink Dual Carrier, has one or more ongoing uplink TBFs and is not in a Downlink Dual Carrier configuration, but receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message specifying frequency parameters for carrier 1 that are different from those currently in effect for the uplink TBF, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT/ MULTIPLE TBF DOWNLINK ASSIGNMENT message and continue normal operation of the uplink TBF; +- If both the mobile station and the network support multiple TBF procedures and if any given downlink assignment message provides an uplink TBF allocation for a PFI not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST or EMSR and if any given downlink assignment message provides an uplink resource allocation for a PFI not associated with any RLC entity allocated on the ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that does not support Downlink Dual Carrier receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) that assigns resources on two carriers or includes the *Assignment Info* IE which indicates that the assignment is a 'Modification of an existing assignment' or a 'Dual Carrier assignment', the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1); + +- If a mobile which supports Downlink Dual Carrier receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) that assigns resources on two carriers and those two carriers are not within the same frequency band, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration wherein resources are assigned on carriers in different frequency bands but does not support inter-band reception, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration with more carriers or more downlink timeslots than it supports, or assigns eTFIs or a SNS of 8192 or CS-3 for PDAN coding when the mobile station supports 20 or fewer time slots, or assigns carriers in a frequency band it does not support, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message that modifies a DLMC configuration that releases carriers on which USF is being monitored, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that assigns two or more UFPS to the same Mobile Allocation (as defined by the *DLMC Frequency Parameter* IE), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station that supports Downlink Multi Carrier receives a PACKET UPLINK ASSIGNMENT message that modifies a DLMC configuration by assigning an uplink carrier that does not correspond to an existing downlink carrier, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or EC PACKET DOWNLINK ASSIGNMENT message is due to any other reason, the mobile station shall abort the establishment of the downlink TBFs indicated in the downlink assignment message. If one or more ongoing uplink or downlink TBFs exist, the mobile station shall continue the normal operation of all the ongoing uplink TBFs. If no ongoing uplink or downlink TBFs exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1). + +### 8.1.2.2 Polling for Packet Downlink Ack/Nack + +Whenever the mobile station receives an RLC data block addressed to one of its TBFs and with a valid RRBG field or with a valid CES/P field in the RLC data block header (i.e. is polled), the mobile station shall transmit one of the following replies in the uplink radio block specified by the RRBG field or CES/P field, whatever the BSN value of the received RLC data block, according to the subsequent decreasing order of priority: + +- 1) a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing a Final Ack Indicator; +- 2) a PACKET CS REQUEST message, if such a message is waiting to be transmitted; +- 3) a PACKET CELL CHANGE NOTIFICATION message, if such a message is waiting to be transmitted; +- 4) a (EGPRS) PACKET DOWNLINK ACK/NACK message or a EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or a EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing a Channel Request Description IE; +- 5) any other RLC/MAC control message, if such a message is waiting to be transmitted, other than a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message; +- 6) when FANR is activated and the mobile station is polled for a PAN (see sub-clause 10.4.4b) , a PAN field corresponding to this TBF included in an EGPRS RLC/MAC block for data transfer from one of the concurrent TBFs in uplink (see sub-clause 8.1.1.); + +- 7) a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message not containing a Final Ack Indicator or a Channel Request Description IE. + +However, the mobile station shall transmit an RLC/MAC control message other than a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message at most every second time it is polled for the TBF. For a TBF with FANR activated, the mobile station may transmit an RLC/MAC control message other than a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message only if a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message or EGPRS RLC/MAC block for data transfer including a PAN field was transmitted as the response to the last poll. + +The mobile station shall not send an EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message if not indicated as supported by the network according to the value of the *EGPRS Packet Downlink Ack/Nack Type 3 Support* field in assignment messages. + +The mobile station shall not send a PACKET CONTROL ACKNOWLEDGEMENT message unless otherwise specified. + +A mobile station in packet transfer mode in a Downlink Dual Carrier configuration or a DLMC configuration shall respond in the uplink radio block indicated by the RRBP field or by the CES/P field, on the same radio frequency channel as the one where the poll was received. A mobile station in dual transfer mode in a Downlink Dual Carrier configuration shall respond in the uplink radio block on the timeslot or on the PDCH pair indicated by the RRBP field or by the CES/P field, on the uplink radio frequency channel where the dedicated resource is assigned regardless of which downlink radio frequency channel the poll was received on. The network shall not poll the mobile station in a manner which would require the mobile station to respond on the same timeslot as that on which the dedicated resource is assigned. + +In EGPRS TBF mode the mobile station shall react on a poll inside an erroneously received RLC data block for which the header is correctly received and which addresses the mobile station. + +If EMST is used and the mobile station responds to the poll with a (EGPRS) PACKET DOWNLINK ACK/NACK message, an EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, an EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or an EGPRS PACKET DOWNLINK ACK/NACK DLMC message or an EGPRS RLC/MAC block for data transfer with a PAN field, then the message or the PAN field shall correspond to the RLC entity identified by the TFI in the header of the downlink RLC/MAC block containing the poll. + +Whenever the network receives a valid RLC/MAC control message from a TBF, it shall reset counter N3105 for that TBF. The network shall increment counter N3105 for each radio block, allocated to that TBF with the RRBP field or with the CES/P field, for which no RLC/MAC control message is received. If N3105 = N3105max, the network shall release the downlink TBF internally and start timer T3195 for that TBF. When T3195 expires, the network may reuse the TFI(s). + +The PACKET DOWNLINK ACK/NACK message contains a Channel Quality Report (see 3GPP TS 45.008). The optional I\_LEVEL measurement results shall be included in at least every other PACKET DOWNLINK ACK/NACK message. + +The EGPRS PACKET DOWNLINK ACK/NACK message may contain an EGPRS Channel Quality Report (see 3GPP TS 45.008). + +The EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message and the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message may contain an EGPRS Channel Quality Report Type 2 (see 3GPP TS 45.008). The EGPRS PACKET DOWNLINK ACK/NACK DLMC message may contain the *DLMC Channel Quality Report* IE (see sub-clause 12.66). + +In the case of simultaneous uplink and downlink TBFs, the transmission of the polling response takes precedence over the transmission of allocated uplink radio blocks. + +A mobile station of multislot class 1 to 12 or multislot class 30 to 45 need not respond to the poll if it is not compliant with the multislot class of the mobile station (see 3GPP TS 45.002). + +A mobile station of multislot class 13 to 18 shall always respond to the poll. + +A mobile station of multislot class 19 to 29 may omit the allocated downlink PDCHs with timeslot numbers greater than $n+1$ , while transmitting the polling response on timeslot number $n$ . If the remaining configuration is not compliant with the multislot class of the mobile station (see 3GPP TS 45.002), the mobile station need not respond to the poll. + +NOTE: The mobile station is required to make neighbour cell measurements while transmitting the polling response (see 3GPP TS 45.008). + +In case of simultaneous uplink and downlink TBFs and extended dynamic allocation (see sub-clause 8.1.1.2), the network may apply polling in downlink RLC data blocks only when sent on a PDCH common for both reception and transmission (see 3GPP TS 45.002). A mobile station operating with extended dynamic allocation need to respond to polling in downlink RLC data blocks only when received on a PDCH common for both reception and transmission. + +The mobile station shall not send a poll response using a TTI configuration that is different from that with which the poll was received. + +If a downlink TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed by the BSS (see sub-clause 11.2.7 and 3GPP TS 44.018 [11]) then EGPRS Packet Downlink Ack/Nack Type 2 and EGPRS Packet Downlink Ack/Nack Type 3 messages shall include these parameters when all downlink RLC data blocks have been received by the mobile station. The BSS uses the “MS Transmission Offset” parameter carried therein to adjust the estimated timing advance applicable to the mobile station (3GPP TS 45.010) and thereby establishes a “MultilaterationTiming Advance” value corresponding to that mobile station. The BSS then relays the “Multilateration Timing Advance”, “Cell Identifier” of the serving cell, the “MS Sync Accuracy” and the “BTS Reception Accuracy Value” to the SMLC using the SCCP connection corresponding to the mobile station (see 3GPP TS 49.031). + +#### 8.1.2.2a Polling for EC Packet Downlink Ack/Nack or EC Packet Downlink Ack/Nack Higher CC + +Whenever the mobile station receives an RLC data block addressed to its TBF and with a valid RRBP field in the RLC data block header (i.e. it is polled), the mobile station shall transmit a reply in the uplink radio block(s) specified by the RRBP field. The network can poll the mobile station in more than one downlink radio block where each valid RRBP field points to the same uplink resources to be used for transmission of the EC PACKET DOWNLINK ACK/NACK message. The mobile station shall thus not automatically stop listening to the downlink when it is polled. It shall instead stop listening according to its specified reaction time, see 3GPP TS 45.010, before transmission of the EC PACKET DOWNLINK ACK/NACK message. If the mobile station has not received an RLC data block containing the Final Block Indicator or it has received the Final Block Indicator but still has downlink data blocks that need to be negatively acknowledged, it shall transmit the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message including the ack/nack description accordingly. When the Final Block Indicator is received and all downlink data blocks have been correctly received, the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message shall be transmitted containing the Final Ack Indicator. If uplink data becomes available for transmission at any point in time during an ongoing downlink TBF, the mobile station can request uplink resources by including a channel request in the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message. + +After completing the transmission of an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message in TDMA frame $N$ the mobile station shall resume monitoring its assigned downlink PDCH(s). The first downlink TDMA frame monitored shall be according to its assigned downlink coverage class and may start as early downlink TDMA frame $N+1$ depending on the assigned uplink and downlink coverage classes. If the first downlink TDMA frame monitored occurs in downlink TDMA frame $N+1$ and the mobile station is unable to monitor all of its assigned downlink PDCHs therein due to multislot class limitations on switching from transmit to receive (see 3GPP TS 45.002 [13]) it shall still attempt recovery of a RLC data block (or an EC-PACCH block) using the bursts it is able to receive therein and in subsequent downlink TDMA frames. + +In EC TBF mode the mobile station shall react on a poll inside an erroneously received RLC data block for which the header is correctly received and which addresses the mobile station. + +Whenever the network receives a valid RLC/MAC control message from a TBF, it shall reset counter N3105 for that TBF. The network shall increment counter N3105 for each radio block allocated to that TBF with the RRBP field for + +which no RLC/MAC control message is received. If N3105 = N3105max, the network shall release the downlink TBF internally and start timer T3195 for that TBF. When T3195 expires, the network may reuse the TFI(s). + +If a downlink EC TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed by the BSS (see sub-clause 11.2.52 and 3GPP TS 44.018 [11]) then EC PACKET DOWNLINK ACK/NACK message shall include these parameters when all downlink RLC data blocks have been received by the mobile station. The BSS uses the “MS Transmission Offset” parameter carried therein to adjust the estimated timing advance applicable to the mobile station (3GPP TS 45.010) and thereby establishes a “MultilaterationTiming Advance” value corresponding to that mobile station. The BSS then relays the “Multilateration Timing Advance”, the “Cell Identifier” of the serving cell, the “MS Sync Accuracy” and the “BTS Reception Accuracy Value” to the SMLC using the SCCP connection corresponding to the mobile station (see 3GPP TS 49.031). + +#### 8.1.2.3 (void) + +#### 8.1.2.4 Resource Reassignment for Downlink + +The network initiates resource reassignment by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) on the downlink PACCH. These messages indicate a change in resources in the same TBF. The Control Ack bit in the message shall be set to '0'. If multiple TBF procedures are supported by the mobile station and the network, the network shall indicate the PFI associated with each TBF it allocates or reallocates in the downlink assignment message. If EMTS is supported by the mobile station and the network, the network shall indicate the PFI associated with each RLC entity in the downlink assignment message (i.e. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). During the reassignment of any given TBF its associated TFI is allowed to be changed. Mobile shall use the TFI indicated in the PACKET DOWNLINK ASSIGNMENT/ MULTIPLE TBF DOWNLINK ASSIGNMENT when using the resource indicated in the message. + +The network is not allowed to change the RLC mode nor TBF mode of an already established TBF during resource reallocation. Change of RLC mode or TBF mode shall be achieved through release of on-going TBF and establishment of a new TBF with the newly requested RLC mode or TBF mode using the procedures described in sub-clause 9.3.2.5 or sub-clause 9.3.3.5. + +On receipt of a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) and after the TBF starting time, if present, the mobile station shall switch to the assigned PDCHs. Upon switching to the new PDCHs the mobile station shall restart timer T3190 for each newly assigned downlink TBF. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.1.1.3. + +When the mobile station receives an RLC/MAC block addressed to (one of) its downlink TBF(s) on any of the new assigned resources it shall restart timer T3190 for that TBF. If any given timer T3190 expires, and if one or more uplink TBF is in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If any given timer T3190 expires and there are no uplink TBFs in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1). + +##### 8.1.2.4.1 Abnormal cases + +These abnormal cases apply during establishment of downlink TBF after downlink TBF release (see sub-clause 9.3.2.6). + +If a failure occurs on the mobile station side before the new TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If a mobile station receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) and detects an invalid Frequency Parameters information element in the message, the mobile station shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information; +- If a mobile station in dual transfer mode or MAC-DTM state receives a PACKET DOWNLINK ASSIGNMENT, a MULTIPLE TBF DOWNLINK ASSIGNMENT, a PACKET TIMESLOT RECONFIGURE + +or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1); + +- If the information in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the information available in the mobile station, after the reception of a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message does not satisfactorily define a PDCH, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT / MULTIPLE TBF DOWNLINK ASSIGNMENT message and maintain its ongoing TBFs; +- If the mobile station receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message specifying different frequency parameters than those currently in effect for its ongoing TBFs (see sub-clause 5.5.1.7), the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message and continue normal operation of its ongoing TBFs; +- If a failure in the PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message is due to any other reason, the mobile station shall abort the establishment of the downlink TBFs indicated in the downlink assignment message. If one or more ongoing uplink or downlink TBFs exist, the mobile station shall continue the normal operation of all ongoing uplink TBFs. If no ongoing uplink or downlink TBFs exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1); +- If both the mobile station and the network support multiple TBF procedures and if any given downlink assignment message provides an uplink TBF allocation for a PFI not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST or EMSR and if any given downlink assignment message provides an uplink resource allocation for a PFI not associated with any RLC entity allocated on the ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2). + +### 8.1.2.5 Establishment of uplink TBF + +The mobile station may request establishment of one or more uplink TBFs when there are one or more ongoing downlink TBFs by including a Channel Request Description or the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, or by including a Channel Request Description information element in an EGPRS PACKET DOWNLINK ACK/NACK DLMC message. Initiation is triggered by a request from upper layers to transfer an upper layer PDU. The request from upper layers specifies a Radio Priority to be associated with the packet transfer. + +When multiple TBF procedures are not supported, the mobile station initiates the packet access procedure by sending the Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message on the PACCH and starting timer T3168. + +When the mobile station has an ongoing downlink EC TBF, it may initiate an uplink EC TBF by including the EC Channel Request Description information element in the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message on the EC-PACCH and start timer T3168. The network may then establish an uplink EC TBF by sending an EC PACKET UPLINK ASSIGNMENT message to the mobile station, in which case the downlink EC TBF is released. + +When the mobile station and the network support multiple TBF procedures the mobile station may request one or more uplink TBFs by including the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message and starting one instance of timer T3168 for each uplink TBF it requests. Each requested uplink TBF is associated with a different PFI. A mobile station shall continue to use its ongoing downlink TBFs unless re-allocated or released as a result of the uplink assignment message(s) sent in response by the network. + +If both the network and the mobile station support the extended uplink TBF mode, the request from upper layers may indicate that the new upper-layer PDU is meant to pre-allocate an uplink TBF (early TBF establishment). In this case, the EARLY\_TBF\_ESTABLISHMENT field in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message shall indicate pre-allocation is required. + +On receipt of an (Extended) Channel Request Description or EC Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK, EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or a Channel Request Description information element in the EGPRS PACKET DOWNLINK ACK/NACK DLMC message, the network may assign radio resources to the mobile station on one or more PDCHs by transmitting an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) on the (EC-)PACCH, or may reject one or more of the requests by sending a PACKET ACCESS REJECT or an EC PACKET ACCESS REJECT message on the (EC-)PACCH. If the PACKET TIMESLOT RECONFIGURE message is sent, then the message shall contain the UPLINK\_TFI\_ASSIGNMENT field. If the mobile station supports RLC non-persistent mode the network may allocate one or more EGPRS TBFs that use this RLC mode. + +In EC operation, the downlink EC TBF is released at establishment of the uplink EC TBF. + +If multiple TBF procedures are supported by the mobile station and the network, the network shall indicate the PFI associated with each TBF it allocates or reallocates in the uplink assignment message. + +A mobile allocation or reference frequency list, when received in the Frequency Parameters IE, as part of an uplink assignment, replaces the previous parameters and shall be used until a new assignment is received or the mobile station has released all TBFs. + +If the network and mobile station both support Downlink Dual Carrier, the network may send an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) to a mobile station specifying one or more TBFs with packet resources on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. Subsequent assignment messages may be sent to a mobile station in a Downlink Dual Carrier configuration as described in sub-clause 8.1.1.1.3. + +If the network and mobile station both support Downlink Multi Carrier, the network may send a PACKET TIMESLOT RECONFIGURE message to a mobile station assigning an uplink TBF and thereby establish a DLMC configuration. Subsequent assignment messages may be sent to a mobile station in a DLMC configuration as described in sub-clause 8.1.1.1.3. + +On receipt of an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) the mobile station shall proceed as follows: + +- On reception of an uplink assignment message the mobile station shall stop the instance of timer T3168 associated with the TBF receiving a resource allocation; +- The mobile station shall, after expiry of the TBF starting time, if present, act upon the uplink assignment received for that TBF; +- The mobile station shall then switch to the assigned uplink PDCHs and begin to send RLC data blocks on the assigned PDCH(s). Neither the TLLI (in *A/Gb mode*) nor the G-RNTI (in *Iu mode*) shall be included in any of the uplink RLC data blocks in that case; +- A mobile station in EC operation, i.e. with a downlink TBF, shall release the downlink TBF at the establishment of the uplink TBF and stop timer T3192, if running. + +A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as follows: + +- Upon reception of a PACKET UPLINK ASSIGNMENT message the mobile station shall release all ongoing uplink TBFs not addressed by this message and shall act on the message. If multiple uplink TBFs were requested then the mobile station shall consider those not addressed by this message as rejected and shall stop the corresponding T3168 timer instances. All ongoing downlink TBFs shall be maintained; +- Upon reception of a PACKET TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message. If multiple uplink TBFs were requested then the mobile station shall consider those not addressed by this message as rejected and shall stop the corresponding T3168 timer instances; +- Upon reception of a MULTIPLE TBF UPLINK ASSIGNMENT message the mobile station shall maintain all ongoing TBFs not addressed by this message using its currently allocated TBF parameters and shall act on the message. If a requested uplink TBF is not addressed by this message and the associated timer T3168 is still running the mobile station shall wait for another instance of this message; +- Upon reception of a MULTIPLE TBF TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message. If multiple uplink TBFs were requested then the mobile station shall consider those not addressed by this message as rejected and shall stop the corresponding T3168 timer instances. + +When an uplink TBF is established in response to a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message with the EARLY\_TBF\_ESTABLISHMENT field set to indicate pre-allocation is required, a network supporting early TBF establishment should keep the uplink TBF open by means of the extended uplink TBF mode operation (see sub-clause 9.3.1b.2). + +On receipt of a PACKET ACCESS REJECT or EC PACKET ACCESS REJECT message that contains a Reject structure addressed to the mobile station, the mobile station shall stop the instance of timer T3168 associated with each uplink TBF being rejected and indicate a packet access failure to the corresponding upper layers. + +If the PACKET ACCESS REJECT or EC PACKET ACCESS REJECT message contains a WAIT\_INDICATION field in a Reject structure addressed to the mobile station, it shall proceed as follows: + +- If multiple TBF procedures are not supported the mobile station shall start timer T3172 with the indicated value (Wait Indication). The mobile station is not allowed to make a new attempt for uplink TBF establishment in the same cell until timer T3172 expires, but it may attempt uplink TBF establishment in another cell after successful cell reselection; +- If both the mobile station and the network support multiple TBF procedures the mobile station shall start one instance of timer T3172 for each uplink TBF that was rejected. All ongoing TBFs shall be maintained. The mobile station is not allowed to attempt re-establishment of a rejected uplink TBF in the same cell until its associated instance of timer T3172 expires. It may, however, attempt re-establishment of a rejected uplink TBF in another cell after successful cell reselection. The mobile station may attempt to enter the dedicated mode in the same cell before all instances of timer T3172 have expired. During the time one or more instances of T3172 are running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging request to trigger RR connection establishment and paging request including MBMS notification. + +If all instances of timer T3168 have expired, the mobile station shall retransmit the (Extended) Channel Request Description information element in the next (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or the Channel Request Description information element in the next EGPRS PACKET DOWNLINK ACK/NACK DLMC message unless the (Extended) Channel Request Description has already been transmitted four times in which case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +In EC operation, when the instance of timer T3168 expires, a mobile station may again include the EC Channel Request Description IE in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message. The EC Channel Request Description IE may however be included in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to '1' even if timer T3168 is still running. A mobile station that included the EC Channel Request Description IE in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to '1', shall release the TBF resources when timer T3168 expires, unless timer T3192 is still running. The packet access procedure may then be reinitiated on the (EC-)CCCH. + +If all the ongoing downlink TBFs are released, including expiry of timer T3192, before expiry of all instances of timer T3168 and no uplink TBFs are either ongoing or have received an uplink assignment with a TBF starting time, the + +mobile station shall stop all remaining instances of timer T3168 and perform an abnormal release with access retry (see sub-clause 8.7.2). + +#### 8.1.2.5.1 Abnormal cases + +If a failure occurs on the mobile station side before a new TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If the information in the PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the mobile station does not support Downlink Dual Carrier but receives a PACKET UPLINK ASSIGNMENT or a MULTIPLE TBF UPLINK ASSIGNMENT message specifying different frequency parameters than those currently in effect for the downlink TBF(s) (see sub-clause 5.5.1.7), the mobile station shall ignore the PACKET UPLINK ASSIGNMENT/ MULTIPLE TBF UPLINK ASSIGNMENT message, continue normal operation of the ongoing downlink TBF(s), and reinitiate the establishment of the uplink TBF(s) unless the establishment of the uplink TBF(s) has already been attempted four times, in which case, the mobile station shall perform the abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station in dual transfer mode or MAC-DTM state receives a PACKET UPLINK ASSIGNMENT or a MULTIPLE TBF UPLINK ASSIGNMENT message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT or in the MULTIPLE TBF UPLINK ASSIGNMENT message is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the information in the PACKET TIMESLOT RECONFIGURE or in the MULTIPLE TBF TIMESLOT RECONFIGURE message does not properly specify a set of uplink and downlink PDCH(s) or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the PACKET TIMESLOT RECONFIGURE or the MULTIPLE TBF TIMESLOT RECONFIGURE message does not include a correct UPLINK\_TFI\_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile station in dual transfer mode receives a PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a failure in the PACKET TIMESLOT RECONFIGURE or in the MULTIPLE TBF TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support multiple TBF procedures and if any given uplink assignment message provides an uplink TBF allocation for a PFI not indicated in the request for uplink TBF sent by the mobile station , the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST and if any given uplink assignment message provides an uplink resource allocation for a PFI not indicated in the request for uplink resource sent by the mobile station, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2); +- If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2); + +- If a mobile station that does not support Downlink Dual Carrier receives a PACKET UPLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF UPLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on two carriers, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If a mobile which supports Downlink Dual Carrier receives a PACKET DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF DOWNLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on two carriers and those two carriers are not within the same frequency band, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the failure is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2). + +8.1.2.6 (void) + +8.1.2.7 (void) + +#### 8.1.2.8 Network initiated abnormal release of downlink TBF + +The network may initiate immediate abnormal release of a downlink TBF by transmitting a PACKET TBF RELEASE message or an EC PACKET TBF RELEASE message to the mobile station on the (EC-)PACCH. + +The mobile station shall immediately stop monitoring its assigned downlink PDCHs. If a valid RRBG field is received as part of the PACKET TBF RELEASE or the EC PACKET TBF RELEASE message, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGMENT or an EC PACKET CONTROL ACKNOWLEDGMENT message in the uplink resources specified. + +In *A/Gb mode*, if there are no other on-going TBFs, the mobile station in packet transfer mode shall enter packet idle mode; the mobile station in dual transfer mode shall enter dedicated mode. If there is one or more on-going TBFs, the mobile station shall remain in its current mode i.e. packet transfer mode or dual transfer mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. + +In *Iu mode*, if no on-going TBFs on SBPSCH exist, the mobile station in MAC-Shared state shall enter the MAC-Idle State; the mobile station in MAC-DTM state shall enter the MAC-Dedicated state. If any on-going TBFs on SBPSCH exist, the mobile station shall remain in its current state, i.e. either MAC-Shared state or MAC-DTM state. The DRX mode procedures shall be applied. + +8.1.3 (void) + +### 8.1.4 RLC data block transfer during an MBMS radio bearer + +#### 8.1.4.0 General + +For each MBMS radio bearer, the network shall prioritise RLC/MAC control blocks not containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message to be transmitted ahead of RLC data blocks for that MBMS radio bearer. If the network has no other RLC/MAC block to transmit, but wishes to transmit on the downlink, the network may either follow the procedure specified in sub-clause 9.3.1a, to keep the MBMS radio bearer alive or transmit an RLC/MAC control block containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message. + +#### 8.1.4.1 RLC data block transfer during an MBMS radio bearer + +Procedures on receipt of a downlink assignment message (e.g. MBMS ASSIGNMENT message) are specified in sub-clause 7.7.2.2. After switching to the assigned PDCHs, the mobile station shall start a T3190 timer instance for the corresponding MBMS radio bearer and shall attempt to decode every downlink block on the assigned PDCHs. + +Additionally, upon reception of an MBMS ASSIGNMENT or MBMS MS\_ID ASSIGNMENT message assigning a specific MS\_ID value to a mobile station, this mobile station shall start a T3290 timer instance for the corresponding MBMS radio bearer, as specified in sub-clause 7.7.2.4. + +The mobile station shall restart the related T3190 timer instance whenever receiving a valid RLC/MAC block including the assigned MBMS Bearer Identity. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. A mobile station with an + +assigned MS\_ID value shall restart the related T3290 timer instance whenever receiving a valid RLC/MAC block including the corresponding MBMS Bearer Identity and the MS\_ID in the TFI field. + +On expiry of a T3290 timer instance, the mobile station shall consider the MS\_ID as released, i.e. it shall no longer answer when polled according to sub-clause 8.1.4.2 below. On expiry of a T3190 timer instance, the mobile station shall consider the related MBMS radio bearer as released and proceed as specified in sub-clause 7.7.1. + +#### 8.1.4.2 Polling for MBMS Downlink Ack/Nack + +If an uplink feedback channel is established, the network may poll any mobile station with an assigned MS\_ID value by setting the (E)S/P bit and a valid RRBP field in the RLC/MAC header of an RLC/MAC block for data transfer containing both the MBMS Bearer Identity and the corresponding MS\_ID value in the TFI field. Whenever a given mobile station is polled, the mobile station shall transmit an MBMS DOWNLINK ACK/NACK message in the uplink radio block specified by the RRBP field, whatever the BSN value of the received RLC data block. In GPRS TBF mode (respectively EGPRS TBF mode), the mobile station shall include the Ack/Nack Description IE (respectively the EGPRS Ack/Nack Description IE) in the message. + +The mobile station shall include in the MBMS DOWNLINK ACK/NACK message neighbouring cells measurement results as described in sub-clause 5.6.4. In EGPRS TBF mode, the number of measurement reports included is specified in sub-clause 9.1.8.2.1. In GPRS TBF mode where cell reselection criteria are not fulfilled three measurement reports shall be included. + +In EGPRS TBF mode, the mobile station shall react to a poll within an RLC/MAC block for data transfer if the RLC/MAC header is correctly received and addresses the mobile station (i.e. contains both the MBMS Bearer Identity and the corresponding MS\_ID value in the TFI field) regardless whether the RLC data block(s) is(are) correctly received or not. + +The mobile station shall notify, whenever possible, the network of the release of the MS\_ID (see note), for that MBMS radio bearer, on the mobile station side, by setting the MS\_ID Release Indication bit to '1' in the MBMS DOWNLINK ACK/NACK message. Any procedure triggering the release of the MS\_ID on the mobile station side shall not be delayed by such release indication (otherwise such release indication shall not be sent). + +NOTE: The mobile station may need to release the related MBMS session for whatever reason (e.g. due to cell reselection, start of the reception of a higher priority MBMS session whose MBMS radio bearer description does not allow the mobile station to receive it in parallel with the current MBMS session, start of a CS connection). + +Whenever the network receives a valid RLC/MAC control message containing an assigned MS\_ID value, it shall reset the counter N3105 for that MS\_ID. The network shall increment the counter N3105 for a given MS\_ID for each radio block, allocated via the polling procedure to the mobile station identified by that MS\_ID value, for which no RLC/MAC control message is received. If N3105 = N3105\_MBMS\_MAX, the network shall release the MS\_ID (i.e. shall internally remove the association between the MS\_ID value and the mobile station identified during the MBMS address assignment procedure) and start timer T3195 for that MS\_ID. When T3195 elapses, the network may reuse the corresponding MS\_ID value. + +#### 8.1.4.3 Reconfiguration of an MBMS radio bearer + +##### 8.1.4.3.1 Individual reassignment of an MS\_ID + +The network may modify or delete the MS\_ID previously assigned to a given mobile station by sending an MBMS MS\_ID ASSIGNMENT message on the PACCH/D, containing the current and, in case of a reassignment, the new MS\_ID value. + +The mobile station shall be addressed with the Global TFI, containing the DOWNLINK\_TFI field, which includes the MBMS Bearer Identity of the MBMS radio bearer and the current MS\_ID of the mobile station the message relates to. The size of the new MS\_ID, if present, shall be equal to the one of the current MS\_ID. If the new MS\_ID is present, the network may include the *Packet Timing Advance* IE. + +When modifying or deleting the current MS\_ID, the MBMS MS\_ID ASSIGNMENT message shall include a current MS\_ID expiry time. + +In response to an MBMS DOWNLINK ACK/NACK message with the MS\_ID Release Indication bit set to '1' (see sub-clause 8.1.4.2), the network may send an MBMS MS\_ID ASSIGNMENT message to the mobile station, deleting the MS\_ID previously assigned to that mobile station on that MBMS radio bearer and setting the current MS\_ID expiry + +time to the point in time when the message is transmitted to the mobile station, without further polling the mobile station on that MBMS radio bearer. The network shall then start timer T3199 for the current MS\_ID. + +Upon reception of an MBMS MS\_ID ASSIGNMENT message, modifying or deleting the current MS\_ID, the addressed mobile station shall consider the current MS\_ID as released at the point in time denoted by the current MS\_ID expiry time. If a new MS\_ID is included in the message, the mobile station shall consider the new MS\_ID as valid and restart timer T3290 at the point in time denoted by the current MS\_ID expiry time and react when polled with the new MS\_ID, according to sub-clause 8.1.4.2. + +If a valid RRBP field is received as part of the MBMS MS\_ID ASSIGNMENT message, the mobile station shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the specified uplink radio block. + +If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the specified radio block, it shall increment counter N3109 for the current MS\_ID and may retransmit the MBMS MS\_ID ASSIGNMENT message addressing the mobile station with the current MS\_ID. If counter N3109 = N3109\_MAX or at the point in time denoted by the current MS\_ID expiry time without receiving a PACKET CONTROL ACKNOWLEDGEMENT message, whatever occurs first, the network shall start timer T3199 for the current MS\_ID. While timer T3199 is running for the current MS\_ID, the network shall not include the current MS\_ID in any RLC/MAC block belonging to that MBMS radio bearer. When timer T3199 expires for the current MS\_ID, the network may reuse the current MS\_ID resource. At the point in time denoted by the current MS\_ID expiry time the network shall start timer T3199 for the new MS\_ID, if present. While timer T3199 is running for the new MS\_ID, the network shall not include the new MS\_ID in any RLC/MAC block belonging to that MBMS radio bearer. When timer T3199 expires for the new MS\_ID, the network may reuse the new MS\_ID resource. + +When modifying the current MS\_ID, after the point in time denoted by the current MS\_ID expiry time, the network shall address the mobile station with the new MS\_ID, unless counter N3109 for the current MS\_ID equals N3109\_MAX or within the point in time denoted by the current MS\_ID expiry time the network has not received a PACKET CONTROL ACKNOWLEDGEMENT message from the polled mobile station. + +#### 8.1.4.3.2 Reassignment of the MBMS Bearer Identity + +The network may reassign the MBMS Bearer Identity previously assigned to a given MBMS radio bearer by sending an MBMS ASSIGNMENT (NON-DISTRIBUTION) message on the PACCH/D, including the current MBMS Bearer Identity (in the most significant bit(s) of the DOWNLINK\_TFI field contained in the Global TFI), explicitly redefining (i.e. modifying the length and/or value of) such MBMS Bearer Identity and implicitly deleting or redefining MS\_IDs assigned to that MBMS radio bearer as described below. + +When reassigning the MBMS Bearer Identity the network shall not reuse the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field. + +If the mobile station receives more than one MBMS ASSIGNMENT (NON-DISTRIBUTION) message for a given MBMS radio bearer, it shall act upon the most recently received message and shall ignore the previous message. + +If a valid RRBP field is received as part of the MBMS ASSIGNMENT (NON-DISTRIBUTION) message, the mobile station identified by the corresponding MS\_ID shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the specified uplink radio block. + +Any redefinition of an MBMS Bearer Identity and any deletion or redefinition of MS\_IDs shall apply at the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise: + +- if the new MBMS Bearer Identity field has the same length as the current one all previously assigned MS\_ID values shall be considered still valid; +- if the new MBMS Bearer Identity field is x bits shorter than the current one, all previously assigned MS\_ID values shall be implicitly redefined by adding x most significant bits set to zero and shall be considered all valid; +- if the new MBMS Bearer Identity field is x bits longer than the current one, all previously assigned MS\_ID values characterized by their x most significant bits equal to zero shall be implicitly redefined by removing these x most significant bits and still considered valid. All other assigned MS\_ID values shall be considered as invalid and discarded. + +At the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise, a mobile station shall restart timer T3190 for the newly assigned MBMS Bearer Identity. The mobile station shall restart timer T3190 whenever receiving an RLC/MAC block including the new MBMS Bearer Identity. If timer T3190 expires, the + +mobile station shall consider the MBMS radio bearer as released and proceed as specified in sub-clause 7.7.1. At the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise, a mobile station with an assigned MS\_ID value shall start timer T3290. The mobile station shall restart timer T3290 whenever receiving an RLC/MAC block including both the new MBMS Bearer Identity and the new MS\_ID in the TFI field. + +The following table illustrates the definition of the new MS\_ID upon reassignment of the MBMS Bearer Identity: + +**Table 8.1.4.3.2.1: Reassignment of MBMS Bearer Identity and MS\_ID** + +| New
Current | | Bearer ID | MS_ID | Bearer ID | MS_ID | Bearer ID | MS_ID | Bearer ID | MS_ID | Bearer ID | MS_ID | +|------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----------------------------------------------------------------|-------|------------------------------------------------------------------|--------|------------------------------------------------------------------|--------|-----------------------------------------------|--------| +| | | 5 bits | - | 4 bits | 1 bit | 3 bits | 2 bits | 2 bits | 3 bits | 1 bit | 4 bits | +| Bearer ID | MS_ID | No MS_ID | | New MS_IDs available | | New MS_IDs available | | New MS_IDs available | | New MS_IDs available | | +| 5 bits | - | Discard current MS_ID | | Keep current MS_ID | | x $\leftarrow$ 0x
New MS_IDs available | | x $\leftarrow$ 00x
New MS_IDs available | | x $\leftarrow$ 000x
New MS_IDs available | | +| 4 bits | 1 bit | | | 0x $\leftarrow$ x
1x $\leftarrow$ Discard current MS_ID | | Keep current MS_ID | | xx $\leftarrow$ 0xx
New MS_IDs available | | xx $\leftarrow$ 00xx
New MS_IDs available | | +| 3 bits | 2 bits | | | 00x $\leftarrow$ x
Other $\leftarrow$ Discard current MS_ID | | 0xx $\leftarrow$ xx
1xx $\leftarrow$ Discard current MS_ID | | Keep current MS_ID | | xxx $\leftarrow$ 0xxx
New MS_IDs available | | +| 2 bits | 3 bits | | | 000x $\leftarrow$ x
Other $\leftarrow$ Discard current MS_ID | | 00xx $\leftarrow$ xx
Other $\leftarrow$ Discard current MS_ID | | 0xxx $\leftarrow$ xxx
1xxx $\leftarrow$ Discard current MS_ID | | Keep current MS_ID | | +| 1 bit | 4 bits | NOTE: The following notations are used:
"No MS_ID": no MS_ID available. MS is not allowed to use feedback
"Discard current MS_ID": MS shall discard the current MS_ID. MS is no longer allowed to use feedback
"New MS_IDs available": MS_IDs are made available for incoming MSs
"Keep current MS_ID": MS shall keep its current MS_ID and use feedback (i.e. reply when polled with this MS_ID)
n $\leftarrow$ m: current MS_ID $\leftarrow$ new MS_ID. Defines the value of the new MS_ID based on the value of the current MS_ID
"x" $\leftarrow$ "x" means the same bit value is used | | | | | | | | | | + +The network shall start timer T3191 at the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise. When timer T3191 expires the network may reuse the TFI values corresponding to the old MBMS Bearer Identity, i.e. the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field. + +### 8.1.4.3.3 Resource reassignment for an MBMS radio bearer + +The network may initiate resource reassignment for an MBMS radio bearer by sending the MBMS ASSIGNMENT (NON-DISTRIBUTION) message, including the MBMS Bearer Identity (in the most significant bit(s) of the DOWNLINK\_TFI field contained in the Global TFI), on the PACCH/D of the MBMS radio bearer. During the reassignment of the MBMS radio bearer its associated MBMS Bearer Identity may be changed. + +In case of partial or complete overlap between the old and the new resource configuration on the downlink, the MBMS Bearer Identity shall be changed. + +If the MBMS Bearer Identity is changed the network shall not reuse the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field. + +If the mobile station receives more than one MBMS ASSIGNMENT (NON-DISTRIBUTION) message for a given MBMS radio bearer, it shall act upon the most recently received message and shall ignore the previous message. + +If a valid RRBP field is received as part of the MBMS ASSIGNMENT (NON-DISTRIBUTION) message, the mobile station identified by the corresponding MS\_ID shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the specified uplink radio block. + +On receipt of an MBMS ASSIGNMENT (NON-DISTRIBUTION) message, and at the point in time denoted by the MBMS radio bearer starting time, if present, the mobile station shall switch to the assigned PDCHs. Upon switching to + +the assigned PDCHs the mobile station shall restart timer T3190 for the newly assigned MBMS radio bearer. The mobile station shall restart timer T3190 whenever receiving a valid RLC/MAC block belonging to that MBMS radio bearer. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. If timer T3190 expires, the mobile station shall consider the MBMS radio bearer as released and proceed as specified in sub-clause 7.7.1. Upon switching to the assigned PDCHs, a mobile station with an assigned MS\_ID value shall restart timer T3290. The mobile station shall restart timer T3290 whenever receiving an RLC/MAC block including both the MBMS Bearer Identity and the MS\_ID in the TFI field. + +With an MBMS ASSIGNMENT (NON-DISTRIBUTION) message the network may explicitly redefine (i.e. modify the length and/or value of) the MBMS Bearer Identity of an MBMS radio bearer and implicitly delete or redefine MS\_IDs assigned to that MBMS radio bearer as specified in sub-clause 8.1.4.3.2. Any redefinition of an MBMS Bearer Identity and any deletion or redefinition of MS\_IDs shall only be effective as of switching to the assigned PDCHs. + +After resource reassignment the mobile station shall receive system information messages and paging messages on the (P)BCCH and the (P)CCCH or on the PACCH of the MBMS radio bearer, depending on the value of the MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT (NON-DISTRIBUTION) message and on the presence of an assigned MS\_ID value. + +The network shall start timer T3191 at the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise. When timer T3191 expires the network may reuse the TFI values corresponding to the old MBMS Bearer Identity, i.e. the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field, on the old resource configuration. + +#### 8.1.4.4 Network initiated release of an MBMS radio bearer + +The network may initiate the normal or abnormal release of an MBMS radio bearer by transmitting a PACKET TBF RELEASE message to the mobile station(s) on the PACCH. + +The following applies when the PACKET TBF RELEASE message is used for releasing an MBMS radio bearer: + +- the Global TFI shall always contain the DOWNLINK\_TFI field. The most significant bit(s) of the DOWNLINK\_TFI field denote(s) the MBMS Bearer Identity of the MBMS radio bearer released by the message; +- the UPLINK\_RELEASE field shall be ignored by the mobile station; +- the DOWNLINK\_RELEASE field shall always be set to the value '1' by the network to indicate that the MBMS radio bearer is released. + +NOTE: The network may retransmit the PACKET TBF RELEASE message to increase the probability of its correct reception. Timer T3191 is (re)started every time the PACKET TBF RELEASE message is sent. When timer T3191 expires for the MBMS radio bearer, then the network may reuse all the TFIs related to the MBMS radio bearer. + +Upon receipt of a PACKET TBF RELEASE message referring to an MBMS radio bearer the mobile station is receiving, the mobile station shall immediately consider the MBMS Bearer Identity, and the MS\_ID if assigned, as released, and stop timers T3190 and T3290. + +If the mobile station in broadcast/multicast receive mode is not receiving any other MBMS radio bearers, it shall enter packet idle mode and apply the DRX mode procedures as specified in sub-clause 5.5.1.5, otherwise it shall remain in broadcast/multicast receive mode. + +#### 8.1.4.5 Suspension/Resumption of the reception of an MBMS radio bearer + +In case a mobile station that supports multiple TBF procedures suspends the reception of an MBMS radio bearer for whatever reason, the mobile station may retain the MBMS bearer description for such MBMS radio bearer until the expiry of the T3190 timer instance for the corresponding MBMS radio bearer. The corresponding MBMS bearer description shall be deleted if the mobile station completes a cell reselection or the session duration timer for this MBMS session in the mobile station expires. + +When the mobile station returns to packet idle mode or completes the reception of higher mobile station-specific priority MBMS session(s), preventing the mobile station from receiving the suspended MBMS session, still remaining in broadcast/multicast receive mode, + +- if the MBMS bearer description is still stored in the mobile station, then the mobile station may attempt to resume the reception of the suspended MBMS session (re-entering broadcast/multicast receive mode if the mobile station has previously left it); +- otherwise the mobile station shall repeat the MBMS packet access procedure for the MBMS session, as specified in sub-clause 7.7.1, unless the session duration timer for this MBMS session in the mobile station has expired. + +## 8.1.5 Multiple MBMS radio bearers + +### 8.1.5.1 Transmission of multiple MBMS radio bearers + +On a PDCH on which multiple MBMS radio bearers are multiplexed, the TFI value(s) including an MBMS Bearer Identity (in the most significant bit(s) of the TFI field) shall differ from all the other TFI values including any other MBMS Bearer Identity (in the most significant bit(s) of the TFI field). + +### 8.1.5.2 Reception of multiple MBMS radio bearers + +#### 8.1.5.2.1 General + +The reception of multiple MBMS radio bearers depends on the capabilities of the mobile station. If the mobile station supports multiple TBF procedures and MBMS, it shall be able to support the reception of multiple MBMS radio bearers. + +In this sub-clause (and sub-clauses 8.1.5.2.2 to 8.1.5.2.7) the priority is mobile station-specific and allows for prioritisation between MBMS sessions on a per-mobile station basis. If two or more MBMS sessions have the same priority, the mobile station shall perform an implementation-dependent selection of the MBMS session with the highest priority so the resulting priorities are distinct for each MBMS session. + +The mobile station shall be able, according to its capabilities, to receive as many MBMS sessions as possible in decreasing order of priority, and to transmit MBMS DOWNLINK ACK/NACK messages (when applicable) for as many MBMS sessions as possible in decreasing order of priority. + +NOTE: Depending on the radio resources allocated for the MBMS radio bearers, a mobile station may not be capable of transmitting MBMS DOWNLINK ACK/NACK messages on all associated uplink feedback channels. + +If a mobile station is receiving multiple MBMS radio bearers and the mobile station has an MS\_ID on at least one MBMS radio bearer where the network has indicated that system information for the serving cell and paging messages are sent on the PACCH/D, then the mobile station shall not read the system information on the (P)BCCH and shall not monitor its paging group on the (P)CCCH in parallel to the MBMS radio bearers. + +If a mobile station is receiving multiple MBMS radio bearers and the mobile station has no MS\_ID on any of the MBMS radio bearers where the network has indicated that system information for the serving cell and paging messages are sent on the PACCH/D, then the mobile station shall not read the system information on the (P)BCCH and shall monitor its paging group on the (P)CCCH in parallel to the MBMS radio bearers. + +#### 8.1.5.2.2 Reception of notification of lower priority MBMS session whilst receiving higher priority MBMS session(s) + +If the mobile station in broadcast/multicast receive mode receives a notification of a lower priority MBMS session which includes the MBMS bearer description: + +- if the capabilities of the mobile station allow, the mobile station shall receive that MBMS session in parallel with the higher priority MBMS session(s), provided the requirements defined in sub-clause 8.1.5.2.1 are fulfilled; +- otherwise, the mobile station shall discard the notification. + +If the mobile station in broadcast/multicast receive mode receives a notification of a lower priority MBMS session which does not include the MBMS bearer description and requests the counting procedure, the mobile station shall not perform the MBMS packet access procedure. + +#### 8.1.5.2.3 Reception of assignment of lower priority MBMS session whilst receiving higher priority MBMS session(s) + +If the mobile station in broadcast/multicast receive mode receives an assignment for a lower priority MBMS session, the mobile station shall act upon the assignment provided the requirements defined in sub-clause 8.1.5.2.1 are fulfilled. + +#### 8.1.5.2.4 Reception of notification of higher priority MBMS session whilst receiving lower priority MBMS session(s) + +If the mobile station in broadcast/multicast receive mode receives a notification of a higher priority MBMS session which includes the MBMS bearer description, the mobile station shall act upon the MBMS bearer description and receive in parallel other lower priority MBMS sessions according to the requirements defined in sub-clause 8.1.5.2.1. + +If the mobile station in broadcast/multicast receive mode receives a notification of a higher priority MBMS session which does not include the MBMS bearer description and requests the counting procedure, then the mobile station shall suspend the reception of the lower priority MBMS session(s) and perform the MBMS packet access procedure for the higher priority MBMS session, as specified in sub-clause 7.7.1. After performing the MBMS packet access procedure, if the MBMS bearer description(s) for the suspended lower priority MBMS session(s) is (are) still stored in the mobile station, then the mobile station may attempt to resume the reception of the suspended MBMS session(s) (see sub-clause 8.1.4.5). + +#### 8.1.5.2.5 Reception of assignment of higher priority MBMS session whilst receiving lower priority MBMS session(s) + +If the mobile station in broadcast/multicast receive mode receives an assignment for a higher priority MBMS session, the mobile station shall act upon the assignment and may drop lower priority MBMS sessions following the requirements defined in sub-clause 8.1.5.2.1. + +#### 8.1.5.2.6 Cell change whilst receiving multiple MBMS sessions (with MBMS supported by the network in the target cell) + +When the mobile station reselects a new (target) cell, the mobile station shall according to its capabilities: + +- first perform fast reception resumption (see sub-clause 8.1.6.2) of as many MBMS sessions as possible in decreasing order of priority, for the sessions for which the mobile station has received in the old cell MBMS NEIGHBOURING CELL INFORMATION messages containing the MBMS bearer description of these sessions in this target cell; + +NOTE 1: The mobile station shall not perform MBMS packet access procedure for requesting an MS\_ID for any MBMS session, with an associated uplink feedback channel, whose priority is lower than the priority of at least one of the MBMS sessions for which the MBMS bearer description is not known. + +- then perform MBMS packet access and establishment procedure as specified in sub-clause 7.7 for the sessions for which the MBMS bearer description is not known, in decreasing order of priority. The mobile station shall not operate two concurrent MBMS packet access and establishment procedures. + +NOTE 2: The MBMS packet access procedure is performed in passive mode (i.e. the mobile station notifies the network in the MBMS SERVICE REQUEST message that it shall not be counted) for any MBMS session whose priority is lower than the priority of at least one of the MBMS sessions already resumed. The mobile station may then perform MBMS packet access procedure for requesting an MS\_ID for the remaining MBMS sessions, with an associated uplink feedback channel, following the requirements defined in sub-clause 8.1.5.2.1. + +NOTE 3: The mobile station shall not perform an MBMS packet access procedure for an MBMS session, if the session duration timer for this MBMS session in the mobile station has expired. + +#### 8.1.5.2.7 Resource reassignment for at least one of the received MBMS radio bearers + +If a mobile station is receiving multiple MBMS radio bearers and any of these is reconfigured by the network in a way that the reception of all of them is no longer consistent with the capabilities of the mobile station, then the mobile station shall continue receiving the highest priority MBMS session and as many as possible of the other MBMS sessions, following the requirements defined in sub-clause 8.1.5.2.1. + +## 8.1.6 MBMS reception resumption after cell reselection + +### 8.1.6.1 Default behaviour + +If a mobile station in broadcast/multicast receive mode reselects a new (target) cell for which it does not have the description of (any of) the MBMS radio bearer(s) being allocated in this target cell for the MBMS session(s) the mobile station was receiving in the old serving cell, the mobile station shall follow the default behaviour in the target cell, as described in this sub-clause. Otherwise, the mobile station shall perform fast reception resumption, as described in sub-clause 8.1.6.2. + +In the target cell, the mobile station shall first perform the acquisition of the system information on the (P)BCCH. + +If the *GPRS Cell Options* IE denotes that the MBMS procedures are supported by the target cell, the mobile station shall then perform the MBMS packet access and establishment procedures, as specified in sub-clause 7.7, for the MBMS session the mobile station was receiving in the old serving cell. + +In case of reception of multiple sessions, the mobile station shall obey the procedures described in sub-clause 8.1.5.2.6. + +### 8.1.6.2 Fast reception resumption + +If a mobile station in broadcast/multicast receive mode reselects a new (target) cell for which it has received the description of (at least one of) the MBMS radio bearer(s) being allocated in this target cell for the MBMS session(s) the mobile station was receiving in the old serving cell (see sub-clauses 5.5.1.1 and 7.7.3), the mobile station shall perform fast reception resumption in the target cell, as described in this sub-clause. Otherwise, the mobile station shall follow the default behaviour, as described in sub-clause 8.1.6.1. + +In the target cell, the mobile station shall immediately resume the reception of the MBMS session for which the MBMS bearer description is known from the old serving cell, without first performing the acquisition of the system information. If the mobile station fails to resume the reception of the MBMS session for any reason and does not have any other MBMS bearer description known for any other MBMS session possibly received in the old serving cell, the mobile station shall then follow the default behaviour (see sub-clause 8.1.6.1). + +The acquisition of the system information shall be performed simultaneously with the reception of the MBMS session. If the network has indicated that the system information for the resumed MBMS session is not sent on the PACCH (with the MBMS In-band Signalling Indicator information element included in the MBMS NEIGHBOURING CELL INFORMATION message transmitted in the old serving cell), the mobile station shall perform the acquisition of the system information on the (P)BCCH. In this case, the reception of the MBMS session may need to be suspended during such acquisition. The mobile station may then attempt to resume the reception of the suspended MBMS session, according to the requirements and the procedures described in sub-clause 8.1.4.5. If the network has indicated that the system information for the resumed MBMS session is sent on the PACCH, the mobile station shall perform the acquisition of the system information on the PACCH, as described in sub-clause 5.5.2.1.3b. + +If the mobile station has received the indication (via the MBMS NEIGHBOURING CELL INFORMATION message transmitted in the old serving cell) that, for the MBMS radio bearer corresponding to the resumed MBMS session, an uplink feedback channel is established in the new cell, the mobile station initiates the MBMS packet access procedure either: + +- on the MPRACH, if the mobile station is in DRX mode (e.g. it is not involved in a *routing area update* procedure) and received the indication that an MPRACH is allocated on the uplink feedback channel (sub-clause 7.7.1.4), or +- on a PCCCH (sub-clause 7.7.1.2) or, +- if a packet control channel is not allocated in the cell, on a CCCH (sub-clause 7.7.1.3). + +In case of reception of multiple sessions, the mobile station shall obey the procedures described in sub-clause 8.1.5.2.6. + +## 8.1.7 Packet Application Information + +### 8.1.7.1 General + +The Packet Application Transfer procedure enables an application on the network side to transfer Application data to a mobile station. + +The network may send the PACKET APPLICATION INFORMATION message to a mobile station in packet transfer mode or in dual transfer mode on the PACCH with one of the following applications: + +### 8.1.7.2 Earthquake and Tsunami Warning System (ETWS) + +The PACKET APPLICATION INFORMATION message enables the network to transfer an ETWS Primary Notification message, see 3GPP TS 23.041, to a mobile station. + +A mobile station operating in packet transfer mode or in dual transfer mode may receive a PACKET APPLICATION INFORMATION message on the PACCH. Since this message may be segmented across more than two RLC/MAC control blocks, by using extended RLC/MAC control message segmentation, the mobile station shall attempt to acquire all segments of the PACKET APPLICATION INFORMATION message before attempting to decode the message. Upon receiving the complete PACKET APPLICATION INFORMATION message the ETWS Primary Notification message shall be sent to upper layers. + +## 8.1.8 Dynamic Timeslot Reduction + +### 8.1.8.1 General + +Dynamic Timeslot Reduction (DTR) allows the network to command the mobile station in packet transfer mode to reduce the number of downlink timeslots that it is required to monitor during inactivity periods of a TBF. The network should use DTR only when extended uplink TBF mode with EXT\_UTBF\_NODATA set to '1' and/or delayed downlink TBF release are used. + +The network orders a mobile station that supports DTR to reduce the number of downlink timeslots it shall monitor during the inactivity periods of a TBF (as specified for delayed downlink TBF release and extended uplink TBF mode) by sending it DTR information as defined in sub-clause 8.1.8.2. + +The mobile station shall indicate its support for DTR in the MS Radio Access Capabilities IE (see 3GPP TS 24.008). + +### 8.1.8.2 DTR Activation + +The network shall send DTR information including the TN/PDCH-pair field indicating the timeslot number (BTTI configuration) or the PDCH-pair number (RTTI configuration) and the carrier ID (if the mobile station is in dual carrier configuration) of the timeslot or the PDCH-pair the mobile station shall monitor for USFs and downlink RLC/MAC blocks while in DTR mode. A mobile station with an assigned uplink TBF shall ignore the DTR information in case the indicated timeslot or PDCH-pair is not within the timeslots assigned to the uplink TBF. A mobile station with an assigned downlink TBF shall ignore the DTR information if the indicated timeslot or PDCH-pair does not correspond to a timeslot or PDCH-pair assigned to the downlink TBF. For a DLTC configuration the network shall send DTR information including the TN/PDCH-pair field indicating the timeslot number (BTTI configuration) or the PDCH-pair number (RTTI configuration) of the timeslot or the PDCH-pair the mobile station shall monitor for radio blocks on the downlink carrier used for fall back according to a regular pre-determined interval (see sub-clause 5.13). + +In addition, the DTR information may indicate the mobile station is only required to monitor a sub-set of the radio blocks on the monitored timeslot/PDCH-pair, as indicated by the *DTR Blks* parameter. + +During a downlink TBF, the network may transmit the DTR information within downlink RLC data blocks of the TBF (see sub-clause 10.3a.1). During an uplink TBF, the network may transmit the DTR information within a PACKET UPLINK ACK/NACK message. If DTR information is received in a PACKET UPLINK ACK/NACK message and an RLC data block in the same block period, the mobile station shall ignore the DTR information received in the RLC data block. + +A mobile station not already in DTR mode shall enter DTR mode and start monitoring only the indicated PDCH or PDCH-pair (and if applicable, carrier) within the reaction time specified in 3GPP TS 45.010, when: + +- DTR information was included in whichever of the following was the most recently received: + - i) any PACKET UPLINK ACK/NACK message (applicable if the mobile station has an ongoing uplink TBF) and + - ii) the RLC data block with BSN equal to $V(Q) - 1$ modulo $SNS$ (applicable if the mobile station has an ongoing downlink TBF) and +- $V(R) = V(Q)$ , if the mobile station has an ongoing downlink TBF, and + +- if the mobile station has an ongoing uplink TBF, the RLC data block with BSN = V(S) is not available and either: + - $V(A) = V(S)$ , or + - $V(A) < V(S) \bmod \text{SNS}$ , the most recently received pre-emptive transmission bit is set to '0', and no element of V(B) has the value NACKED (for RLC acknowledged mode). + +NOTE 1: If the network includes DTR information in a PACKET UPLINK ACK/NACK message which includes one or more NACK indications, and the pre-emptive transmission bit is set to '0', upper layer PDUs may be delayed due to the limited uplink bandwidth available when in DTR mode. In order to ensure there are no delays in the delivery of upper layer uplink PDUs, the network should not send DTR information in a PACKET UPLINK ACK/NACK message which includes multiple NACK indications. + +NOTE 2: The network may not be able to determine the exact point when the mobile station enters DTR but may use appropriate means (e.g. polling on a timeslot other than the monitored timeslot) to confirm that the MS has entered DTR. + +A mobile station already in DTR mode shall assume the DTR information is unchanged and shall therefore remain in DTR mode, i.e. the network shall ensure the DTR information is kept unchanged for this MS while it remains in DTR mode. + +The mobile station shall respond to any poll for PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGMENT message received in radio block periods up to and including the one in which the mobile station is triggered to enter DTR mode (i.e. in which all conditions for entering DTR, as specified in this sub-clause, are met), as specified in sub-clause 8.1.2.2 and sub-clause 8.6. The mobile station shall respond to any poll for PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGMENT message if it was received on the timeslot/PDCH-pair to be monitored during DTR mode and was received during a radio block period after the one in which the mobile station is triggered to enter DTR mode. + +When a mobile station operating concurrent TBFs in both directions is ordered to enter DTR mode, it shall apply DTR mode on both TBFs. The mobile station shall monitor the indicated PDCH or PDCH-pair for USFs and downlink RLC/MAC blocks. + +### 8.1.8.3 Resumption to normal operation + +The mobile station shall exit DTR mode within the reaction time specified in 3GPP TS 45.010: + +- when an RLC data block with BSN equal to V(S) is transmitted and the medium access mode is Dynamic Allocation; +- when an EGPRS RLC/MAC block for data transfer including BSN higher than V(R) modulo SNS is received; +- when an RLC data block with BSN equal to V(R) not including a valid DTR information is received; +- upon reception of an assignment message (PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, PACKET CS RELEASE INDICATION) or PACKET UPLINK ACK/NACK message without a DTR information. If a TBF starting time information element is present in the received assignment message, the mobile station shall wait until the indicated TBF starting time before switching to the assigned PDCHs and exiting DTR mode; +- upon reception of a PACKET PDCH RELEASE message releasing the monitored PDCH/PDCH-pair when the mobile station shall act as specified in sub-clause 8.2. + +## 8.2 Packet PDCH Release + +The network may broadcast the PACKET PDCH RELEASE message on PACCH to indicate one or more timeslots is no longer available for packet data service. In the case where any of these timeslots belong to an assigned PDCH pair for a TBF in RTTI configuration, the mobile stations that use any of these time slots within their assigned TBF(s) in RTTI configuration shall consider both timeslots that constitute such a PDCH pair as being released. When a mobile station receives a PACKET PDCH RELEASE message, it shall immediately stop transmitting and receiving on all assigned PDCHs, which are indicated as not present in the TIMESLOTS\_AVAILABLE field, remove those PDCHs from its list of assigned PDCHs. + +If all of the mobile station's assigned PDCHs are removed from its list of assigned PDCHs, and, if at least one uplink TBF was in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If no uplink TBFs were in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1). + +If the mobile station has been assigned an uplink control timeslot(s) and the PACKET PDCH RELEASE message releases this PDCH/PDCH pair, and if at least one uplink TBF was in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If no uplink TBFs were in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1). + +If the current timeslot configuration requires Shifted USF operation (see sub-clause 8.1.1.2.4) and the PACKET PDCH RELEASE message modifies the configuration in such a way that Shifted USF operation is no longer required then normal USF operation shall apply after a suitable reaction time as defined in 3GPP TS 45.010. + +## 8.3 Procedure for measurement report sending in Packet Transfer mode + +The procedure for NC measurement report sending shall be initiated by the mobile station at expiry of the NC measurement report interval timer T3158 (see sub-clause 5.6.1). An exception is the case of a mobile station that has enabled PEO or EC operation in which case only NC0 shall be used (see 3GPP TS 45.008 [15]) and therefore NC measurement report sending shall not be initiated by the mobile station. At expiry of the timer T3158 the mobile station shall restart the timer T3158, perform the measurements and send either the PACKET MEASUREMENT REPORT message containing the 'NC measurement report struct' or the PACKET ENHANCED MEASUREMENT REPORT message on PACCH. + +Following a downlink TBF establishment, the PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message shall not be sent on the uplink PACCH associated with this TBF until two Packet Ack/Nack ((EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC) messages have been sent to the network. + +## 8.4 Network controlled cell reselection procedure + +A cell reselection is controlled either by the mobile station or by the network. An exception is the case of a mobile station that has enabled PEO in which case cell reselection is only initiated by the mobile station (see 3GPP TS 45.008 [15]). + +When the cell reselection is controlled by the mobile station, the mobile station shall apply the cell reselection procedure defined in sub-clause 5.5.1.1 (*A/Gb mode*). + +When a cell reselection is initiated by the network for an individual mobile station, the cell change order procedure is started by sending a PACKET CELL CHANGE ORDER message to the mobile station on the PCCCH or PACCH. + +The PACKET CELL CHANGE ORDER message contains: + +- The characteristics of the new cell that are necessary to identify it (i.e. BSIC + BCCH frequency); +- The NC measurement parameters valid for the mobile station in the new cell (NETWORK\_CONTROL\_ORDER and optionally: NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T); +- The IMMEDIATE\_REL parameter; +- The CCN\_ACTIVE parameter and optionally the CONTAINER\_ID referring to the one included in received instances of the PACKET NEIGHBOUR CELL DATA message. + +For a multi-RAT mobile station supporting UTRAN, the PACKET CELL CHANGE ORDER message may contain information on a UTRAN target cell, together with the IMMEDIATE\_REL parameter; the establishment of UTRAN channel(s) and subsequent measurement reporting are defined in 3GPP TS 25.331. + +For a multi-RAT mobile station supporting "CCN towards E-UTRAN, E-UTRAN Neighbour Cell measurement reporting and Network controlled cell reselection to E-UTRAN", the PACKET CELL CHANGE ORDER message may contain information on an E-UTRAN target cell; in this case, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 36.331. + +Upon receipt of the PACKET CELL CHANGE ORDER message the mobile station shall start timer T3174 and apply the cell reselection procedure defined in sub-clause 5.5.1.1 (*A/Gb mode*), with the additional rule that an immediate abort of operation in the old cell may be required by the network through the IMMEDIATE\_REL field, except for the acknowledgement, by means of a PACKET CONTROL ACKNOWLEDGEMENT message, of a valid RRBP field possibly included in the PACKET CELL CHANGE ORDER message. A UTRAN capable mobile station ordered to a UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 25.133 and 3GPP TS 25.123); an E-UTRAN capable mobile station ordered to an E-UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 36.133). + +If the timers related to measurement reporting expire while the reselection procedure has not yet been completed, these timers shall be restarted so that the mobile station resumes the measurement reporting procedures once camped on the new cell. + +#### 8.4.1 Network controlled cell reselection completion + +The mobile station shall regard the network controlled cell reselection procedure as successfully completed when it has performed access and successfully completed contention resolution in the new cell, or the GMM READY timer (see 3GPP TS 24.008) stops running during the execution of the procedure. The mobile station shall then stop timer T3174. + +NOTE 1: Access may be performed for the establishment of a dedicated connection or an uplink TBF. + +NOTE 2: If the GMM READY timer stops running, the mobile station shall apply the network controlled cell reselection mode NC0 (i.e., cell re-selection using 'normal MS control', see 3GPP TS 45.008). + +In case of inter-RAT network controlled cell reselection, the mobile station shall regard the network controlled cell reselection as successfully completed according to specifications of the target RAT, or when the GMM READY timer (see 3GPP TS 24.008) stops running during the execution of the procedure. The mobile station shall then stop timer T3174. + +NOTE 3: In case of network controlled cell reselection to UTRAN, the procedure is regarded as successfully completed when the mobile station receives an RRC CONNECTION SETUP message in the target cell (see 3GPP TS 25.331). In case of network controlled cell reselection to E-UTRAN, the procedure is regarded as successfully completed when the mobile station receives an *RRCConnectionSetup* message in the target cell (see 3GPP TS 36.331). + +#### 8.4.1b (void) + +#### 8.4.2 Abnormal cases + +In the following cases, the mobile station shall determine that the network controlled cell reselection procedure has failed: + +- The PACKET CELL CHANGE ORDER message commands the mobile station to a frequency in a frequency band not supported by the mobile station. *Cause*: "frequency not implemented"; +- The PACKET CELL CHANGE ORDER message is received while the mobile station is not in dual transfer mode but a circuit switched connection is on going. *Cause*: "on-going CS connection"; +- In *A/Gb mode*, the PACKET CELL CHANGE ORDER message is received and the GMM READY timer (see 3GPP TS 24.008) is not running (i.e., mobile station in GMM STAND-BY state). *Cause*, if the GMM READY timer has a negotiated value equal to zero: "Forced to the Standby State". *Cause*, if the GMM READY timer has a negotiated value greater than zero: "MS in GMM Standby state"; +- Access is denied in the new cell (i.e., the mobile station receives an IMMEDIATE ASSIGNMENT REJECT, a PACKET ASSIGNMENT REJECT or, in a UTRAN cell, an RRC CONNECTION REJECT message or fails to establish an RRC connection in an E-UTRAN cell as specified in 3GPP TS 36.331). *Cause*: "Immediate Assign Reject or Packet Access Reject on target cell"; +- The mobile station is unable to synchronise to the new cell (see 3GPP TS 45.008) or the timer T3174 expires before a successful completion of the network controlled cell reselection procedure. *Cause*: "No response on target cell"; + +- Due to any other reason (e.g. unknown or unsupported target cell information). In this case the MS shall set the ARFCN and BSIC fields to the value zero and set the cause to value "frequency not implemented". + +If the mobile station determines that the network controlled cell reselection procedure has failed, the mobile station shall stop timer T3174 (if it is still running) and start timer T3176. The mobile station shall return to the old cell, where it may trigger a cell update or other GMM specific procedure. In case the mobile station synchronised and attempted to access the new cell before returning to the old cell, the mobile station shall trigger a cell update or other GMM specific procedure, as appropriate according to the GMM requirements (see 3GPP TS 24.008). + +The mobile station shall send a PACKET CELL CHANGE FAILURE message with the appropriate cause value to the network in the old cell and stop timer T3176. The PACKET CELL CHANGE FAILURE message may be sent on PACCH when the mobile station is in packet transfer mode or MAC-Shared state. Alternatively, the mobile station may initiate random access with access type "single block without TBF establishment" (PCCCH) / "single block packet access" (CCCH) and send the PACKET CELL CHANGE FAILURE message using an allocated single uplink block. + +A mobile station shall ignore a PACKET CELL CHANGE ORDER message received while in dual transfer mode (refer to in 3GPP TS 44.018). + +If a MS which is UTRAN capable is commanded to a 3G-target cell whose description is in contradiction to the UTRAN capabilities of the mobile station, it shall include the UTRAN FDD target cell or UTRAN TDD Target cell IE in the PACKET CELL CHANGE FAILURE message. + +If a mobile station which is E-UTRAN capable is commanded to an E-UTRAN target cell whose description is in contradiction to the E-UTRAN capabilities of the mobile station, it shall include the *E-UTRAN target cell* IE in the PACKET CELL CHANGE FAILURE message. For a mobile station supporting extended EARFCNs, it may instead include the *E-UTRAN Target cell with extended EARFCN* IE in the PACKET CELL CHANGE FAILURE message. + +If a mobile station supporting extended EARFCNs receives a PACKET CELL CHANGE ORDER message with both *E-UTRAN target cell* IE and *E-UTRAN Target cell with extended EARFCN* IE included therein, it shall return the *E-UTRAN Target cell with extended EARFCN* IE in the PACKET CELL CHANGE FAILURE message. + +In case the network controlled cell reselection procedure fails and the MS returns to the old cell, the MS shall delete any stored NC measurement parameters and revert to the broadcast parameters. If individual priorities are indicated in the PACKET CELL CHANGE ORDER message, they shall be deleted. + +If the mobile station is unable to synchronise to the old cell (see 3GPP TS 45.008), or if timer T3176 expires, the mobile station shall cancel the sending of the PACKET CELL CHANGE FAILURE message and perform an autonomous cell re-selection. + +## 8.5 Measurement Order procedures in Packet Transfer mode + +The network may initiate the measurement order procedure by sending a PACKET MEASUREMENT ORDER message on the PACCH to a mobile station in packet transfer mode or in MAC-Shared state. The PACKET MEASUREMENT ORDER message overrides a broadcast PSI5 message. + +The PACKET MEASUREMENT ORDER message may also contain the following optional parameters: + +- NC Measurement Parameters (NETWORK\_CONTROL\_ORDER; NC\_NON\_DRX\_PERIOD; NC\_REPORTING\_PERIOD\_I; NC\_REPORTING\_PERIOD\_T; NC\_FREQUENCY\_LIST); +- Enhanced measurement reporting. + +Upon receipt of the PACKET MEASUREMENT ORDER message, the mobile station shall store the received parameters and obey the NETWORK\_CONTROL\_ORDER as specified in 3GPP TS 45.008 and in sub-clause 5.6. An exception is the case of a mobile station that has enabled PEO or EC operation in which case the mobile station shall ignore the NETWORK\_CONTROL\_ORDER parameter if included in the message and behave as in network control mode NC0. + +## 8.6 PACKET CONTROL ACKNOWLEDGEMENT + +An (EC) PACKET CONTROL ACKNOWLEDGEMENT message shall always be sent in the uplink resources specified by the corresponding valid RRBP field of a downlink RLC/MAC control block, and not in any other uplink resource that may be allocated to the mobile station. However the transmission of the (EC) PACKET CONTROL ACKNOWLEDGEMENT message takes precedence over the transmission of allocated uplink radio blocks or the + +reception of PCCCH or assigned (EC-)PDCH radio blocks. If transmission of the PACKET CONTROL ACKNOWLEDGEMENT message would result in more than the maximum Tx timeslots per TDMA frame allowed by the multislot class, transmission of the highest numbered PDCH(s) shall be omitted. + +In dual transfer mode the reception and transmission of assigned TCH radio blocks on dedicated resources takes precedence over the transmission of the PACKET CONTROL ACKNOWLEDGEMENT. + +A mobile station in packet transfer mode in a Downlink Dual Carrier configuration or a DLMC configuration shall respond in the uplink radio block indicated by the RRBP field on the same radio frequency channel as the one where the poll was received. A mobile station in dual transfer mode in a Downlink Dual Carrier configuration shall respond in the uplink radio block on the timeslot or the PDCH pair indicated by the RRBP field (see sub-clause 10.4.5) on the uplink radio frequency channel where the dedicated resource is assigned regardless of which downlink radio frequency channel the poll was received on, unless this would prevent the transmission or reception of a TCH radio block on a dedicated resource. + +## 8.7 Abnormal cases + +### 8.7.0 General + +The following abnormal cases apply: + +- If the PDCH containing the mobile station's only assigned TAI value is removed, the mobile station shall, if it has at least one ongoing uplink TBF, perform an abnormal release with access retry (see sub-clause 8.7.2, and otherwise shall perform an abnormal release without retry (see sub-clause 8.7.1); +- If the NC Measurement Parameters are sent in more than one instance of the PACKET MEASUREMENT ORDER message, the mobile station shall not obey the measurement order until all instances of the message has been correctly received; +- If the mobile station receives a Timing Advance Index and a Timing Advance Timeslot Number for one direction within a PACKET POWER CONTROL/TIMING ADVANCE message and the corresponding TBF does not exist, the Timing Advance Index and the Timing Advance Timeslot Number for that direction shall be ignored; +- While a TBF is in progress, if a mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET UPLINK ACK/NACK, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or a PACKET CS RELEASE INDICATION message with message escape bit indicating EGPRS (resp. GPRS) contents whereas the current TBF mode is GPRS (resp. EGPRS), the mobile station shall ignore the message; +- While a TBF is in progress, if a mobile station receives a PACKET DOWNLINK ASSIGNMENT message without extension message content related to R99 whereas the current TBF mode is EGPRS, the mobile station shall ignore the message; +- While a TBF is in progress, if a mobile station receives a PACKET DOWNLINK ASSIGNMENT message with extension message content related to R99 whereas the current TBF mode is GPRS, the mobile station shall ignore the EGPRS related information and act as a GPRS MS not supporting EGPRS; +- In Iu mode, if the network receives a PACKET CONTROL ACKNOWLEDGEMENT message with an incorrect timeslot in the TN\_RRBP field for the given radio block, then the message shall be ignored; +- If a mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message that would result in one or more TBFs with FANR activated and one or more TBFs with FANR not activated when considering all concurrent TBFs assigned to that mobile station, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1); +- If a mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message assigning two or more RLC entities operating in the same RLC mode to a TBF, or assigning more RLC entities than the mobile station supports, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.2); + +- If a mobile station receives DTR information including the TN/PDCH-pair field indicating a timeslot or a PDCH-pair which is not assigned to the mobile station as part of TBF (see sub-clause 8.1.8), the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1); +- If a mobile station receives a PACKET CS RELEASE INDICATION message including an inconsistent RTTI configuration assignment as per the conditions specified in sub-clause 7.1.3.6, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1). + +### 8.7.1 Abnormal release without retry + +The mobile station shall abort all TBFs on PDCH(s) in progress and report an RLC/MAC failure to upper layers. The mobile station in packet transfer mode or MAC-Shared state shall return to packet idle mode or MAC-Idle state; the mobile station in dual transfer mode or MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. Upon enhanced CS release while in dual transfer mode, on receipt of PACKET CS RELEASE INDICATION message, the mobile station shall abort all TBFs in progress and return to packet idle mode when the RR connection is released. Upon mobile originated or mobile terminated RR connection establishment, on receipt of IMMEDIATE ASSIGNMENT message while in packet transfer mode, the mobile station shall enter dedicated mode. The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5. + +### 8.7.2 Abnormal release with access retry + +The mobile station shall abort all TBFs in progress. The mobile station in packet transfer mode shall return to packet idle mode and initiate the establishment of one or more new uplink TBFs, using the procedures on CCCH, PCCCH or EC-CCCH, as defined in sub-clause 7.1 and 3GPP TS 44.018. + +The mobile station in dual transfer mode shall return to dedicated mode and initiate the establishment of one new uplink TBF (if exclusive allocation is used) or one or more new uplink TBFs (if exclusive allocation is not used) using the appropriate DTM procedure on the main DCCH, defined in 3GPP TS 44.018. Upon enhanced CS release, on receipt of PACKET CS RELEASE INDICATION message, the mobile station shall abort all TBFs in progress and return to packet idle mode and initiate the establishment of one or more new uplink TBFs, using the procedures on CCCH or PCCCH when the RR connection is released. + +Upon mobile originated or mobile terminated RR connection establishment, on receipt of IMMEDIATE ASSIGNMENT message while in packet transfer mode, the mobile station shall enter dedicated mode and initiate the establishment of one new uplink TBF (if exclusive allocation is used) or more new uplink TBFs (if exclusive allocation is not used) using the appropriate DTM procedure on the main DCCH, as defined in 3GPP TS 44.018. + +In case the mobile station fails to establish a new uplink TBF, the mobile station shall report an RLC/MAC failure to upper layers for that TBF. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. + +### 8.7.3 Abnormal release with system information + +The mobile station shall abort all of the TBFs indicated in the assignment message containing invalid frequency parameter information and proceed as follows: + +- If there are no on-going TBFs it shall immediately return to the BCCH /EC-BCCH and reread all relevant BCCH/EC-BCCH and PBCH information; +- If the mobile station had one ongoing uplink TBF when the abnormal release occurred, the mobile station shall then perform an abnormal release with access retry (see sub-clause 8.7.2); +- If the mobile station had no ongoing uplink TBFs when the abnormal release occurred, it shall perform an abnormal release without retry (see sub-clause 8.7.1); +- Otherwise, the mobile station shall maintain all its ongoing TBFs that were in progress prior to receiving the assignment message containing invalid frequency parameter information and provide a failure indication to the upper layers associated with the aborted TBFs. + +## 8.7.4 Abnormal release with RR connection establishment retry + +The mobile station shall abort all TBFs in progress and report an RLC/MAC failure to upper layers. The mobile station in packet transfer mode shall return to the CCCH configuration, enter packet idle mode and initiate the establishment of the RR connection as specified in 3GPP TS 44.018. + +# 8.8 Network Assisted Cell Change procedures + +## 8.8.1 Neighbour Cell System Information Distribution + +A mobile station in packet transfer mode or in MAC-Shared state may receive neighbouring cell system information for GSM neighbouring cells on PACCH. System Information messages are not distributed for 3G neighbouring cells or E-UTRAN neighbouring cells. The neighbouring cell system information is contained in one or more instances of the PACKET NEIGHBOUR CELL DATA message and the mobile station is addressed by its TFI as follows: + +- If a PBCCH is allocated in the neighbouring cell, the instances of the message may contain the PSI1, a consistent set of PSI2 and the PSI14 messages; +- If no PBCCH is allocated in the neighbouring cell, the instances of the message may contain the SI3, SI13 and, if available, SI1 messages. If SI1 is broadcast in the target cell, the network shall include the SI1 message as the first SI message contained in the set of PACKET NEIGHBOUR CELL DATA messages, starting from the message with CONTAINER\_INDEX=0. + +A mobile station, which receives this information shall, independent of NC mode or CCN mode, store the last received set of the information for at least one cell. The received system information can then be used for initial access when entering the designated neighbour cell. + +All instances of the PACKET NEIGHBOUR CELL DATA message form a complete container for a certain neighbour cell. The container is addressed by a container identity (CONTAINER\_ID) in each instance and optionally by the ARFCN for BCCH and the BSIC of the neighbour cell. The CONTAINER\_ID shall then be included in the PACKET CELL CHANGE CONTINUE or the PACKET CELL CHANGE ORDER message together with the ARFCN and the BSIC. This is in order to map the cell identity to the container identity for which neighbour cell information was received in the PACKET NEIGHBOUR CELL DATA messages. If the ARFCN and BSIC are given for a set of PACKET NEIGHBOUR CELL DATA messages, it is sufficient to include this information in only one instance in the set. + +In order to ensure a consistent distribution and decoding of (P)SI messages contained in PACKET NEIGHBOUR CELL DATA messages, the following rules shall apply for PACKET NEIGHBOUR CELL DATA messages with the same container identity: + +- Whenever the network starts sending a set of PACKET NEIGHBOUR CELL DATA message instances, the first PACKET NEIGHBOUR CELL DATA message instance shall be started with CONTAINER\_INDEX=0; +- All subsequent instances of a PACKET NEIGHBOUR CELL DATA message set shall be sent in ascending order of CONTAINER\_INDEX value. For retransmission purposes it is allowed to send a PACKET NEIGHBOUR CELL DATA message with the same CONTAINER\_INDEX value and the same content more than once; +- Whenever the MS receives a PACKET NEIGHBOUR CELL DATA message instance with CONTAINER\_INDEX=0 or with a CONTAINER\_INDEX value that is less than the CONTAINER\_INDEX value of the last received PACKET NEIGHBOUR CELL DATA message instance, it shall delete any PACKET NEIGHBOUR CELL DATA message instances it may have stored and the extracted system information of the neighbour cell; +- If the MS receives a PACKET NEIGHBOUR CELL DATA message with a different ARFCN and BSIC than was indicated in one or more already received PACKET NEIGHBOUR CELL DATA message instances, it shall delete any PACKET NEIGHBOUR CELL DATA message instances it may have stored and the extracted system information of the neighbour cell; +- 30 s after the reception of the latest PACKET NEIGHBOUR CELL DATA message instance, the MS shall delete any PACKET NEIGHBOUR CELL DATA message instances it may have stored the extracted system information of the neighbour cell. + +When the mobile station receives the PACKET CELL CHANGE ORDER or the PACKET CELL CHANGE CONTINUE message the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGMENT message in the specified uplink radio block if a valid RRBP field is received as part of the message; the mobile station may then switch to a new cell. If the mobile station has collected all required instances of the PACKET NEIGHBOUR CELL DATA message for the new cell already when in the old cell, then it may perform access depending on whether the PACKET PSI STATUS (or PACKET SI STATUS if PBCCH is not supported in the new cell) procedures are supported by the network in the new cell (see below). The required instances of the PACKET NEIGHBOUR CELL DATA message include PSI1, a consistent set of PSI2 messages and PSI14 (if the new cell has a PBCCH allocated) or SI3, SI13 and, if available, SI1 messages (if the new cell does not have a PBCCH allocated). If the MS is able to decode the first SI message contained in the set of PACKET NEIGHBOUR CELL DATA messages but it was not the SI1 message, the MS shall conclude that SI1 is not broadcast in that particular cell in determining when packet access is allowed in the cell (see sub-clause 5.5.1.3). + +If not all required instances of the PACKET NEIGHBOUR CELL DATA message have been received before the cell change, the MS shall first obtain the PBCCH description (if available) and the missing system information messages before making initial access in the new cell. However, it may switch to the new cell as soon as PSI1 has been received (if PBCCH is supported in the new cell) or SI13 has been received (if PBCCH is not supported in the new cell). + +Once all the required system information messages have been received, and if the new cell supports the PACKET PSI STATUS (respectively PACKET SI STATUS) procedures, the mobile station may perform access in the new cell and shall then use these procedures for acquisition of PSI (respectively SI) messages (see sub-clause 5.5.1.4.3). If the PACKET PSI STATUS (respectively PACKET SI STATUS) procedures are not supported by the network in the new cell, then the MS is still required to make at least one attempt to receive the complete set of PSI messages on PBCCH (respectively make at least one attempt to receive other SI messages that may be scheduled within one TC cycle on BCCH) prior to perform access in the new cell (see sub-clauses 5.5.1.2 and 5.5.1.3). + +## 8.8.2 CCN setting procedure + +The network uses the parameter CCN\_ACTIVE in the GPRS Cell Options IE on the BCCH (SI13) or PBCCH (PSI1/PSI13/PSI14) to indicate in the cell whether CCN is enabled for cell reselection towards GSM cells. + +The network uses the parameter 3G\_CCN\_ACTIVE on the BCCH (SI2quater) or PBCCH (PSI3quater) to indicate in the cell whether CCN is enabled for cell reselection towards 3G cells (including UTRAN CSG cells). + +The network uses the parameter E-UTRAN\_CCN\_ACTIVE on the BCCH (SI2quater) to indicate in the cell whether CCN is enabled for cell reselection towards E-UTRAN cells (including E-UTRAN CSG cells). + +- If CCN\_ACTIVE is not provided or it indicates that CCN is disabled in the cell, the mobile stations shall not follow the CCN procedures towards GSM cells. CCN\_ACTIVE can also be individually sent to the mobile station in either a PACKET MEASUREMENT ORDER, a PACKET CELL CHANGE ORDER message or a PS HANDOVER COMMAND message. In the latter cases, the setting applies in the target cell; +- If 3G\_CCN\_ACTIVE is not provided or it indicates that CCN is disabled in the cell, the mobile stations shall not follow the CCN procedures towards 3G cells. 3G\_CCN\_ACTIVE can also be individually sent to the mobile station in either a PACKET MEASUREMENT ORDER, a PACKET CELL CHANGE ORDER message or a PS HANDOVER COMMAND. In the latter cases, the setting applies in the target cell; +- If E-UTRAN\_CCN\_ACTIVE is not provided or it indicates that CCN is disabled in the cell, the mobile station shall not follow the CCN procedures towards E-UTRAN cells. E-UTRAN\_CCN\_ACTIVE can also be individually sent to the mobile station in either a PACKET MEASUREMENT ORDER, a PACKET CELL CHANGE ORDER message or a PS HANDOVER COMMAND. In the latter cases, the setting applies in the target cell; +- If CCN\_ACTIVE indicates that CCN is enabled in the cell and a mobile station determines a cell re-selection towards one of its neighbouring GSM cells is required, it shall first check the corresponding CCN\_SUPPORTED parameter if available. This allows the network to enable CCN mode towards some but not all neighbour GSM cells. + +NOTE: It is not possible for the network to enable CCN mode towards individual 3G or E-UTRAN neighbour cells. + +An individual setting of CCN shall take precedence over the broadcast setting of CCN. The latest individual ordered setting of CCN is the valid one. An individual setting of CCN is only valid within the cell it is ordered for. CCN is + +applicable to a mobile station in Network Control mode NC0 and NC1 but not in mode NC2 that takes precedence over CCN. + +## 8.8.2a CCN support description + +The CCN Support description contains the CCN\_SUPPORTED parameter for each GSM cell of the GSM Neighbour Cell list. + +If there is no PBCCH allocated in the cell, see 3GPP TS 44.018. + +If there is a PBCCH allocated in the cell, the parameter can be provided in the PSI3 message or any instance of the PSI3bis message. In that case, the bitmap applies to the GSM Neighbour Cell list having the same PSI3\_CHANGE\_MARK as the message in which it is provided. + +CCN\_SUPPORTED parameter can also be provided in a PACKET CELL CHANGE ORDER or a PACKET MEASUREMENT ORDER message. In this case, the bitmap applies to the updated GSM Neighbour Cell list. + +Each CCN\_SUPPORTED bit of this description relates to indices of the GSM Neighbour Cell list, starting with index 0. The CCN Support description may be received before the corresponding GSM Neighbour Cell list. + +Indices exceeding the value 95 or the number of cells in the GSM Neighbour Cell list (whichever is the lowest) shall be ignored. If there are fewer indices than the number of cells in the GSM Neighbour Cell list, the value 0 shall be assumed for the missing bits. + +When this information is not present but CCN is enabled in the serving cell, the mobile station shall assume that CCN is enabled towards all neighbour cells. + +## 8.8.3 Cell Change Notification procedure + +If CCN is enabled towards the target cell (see sub-clause 5.5.1.1a), the mobile station shall behave as in network control mode NC0 or NC1 up to the point when a new cell has been chosen. If the target cell is a GSM cell, the mobile station shall then check the CCN\_SUPPORTED parameter, if available, that was last received for that cell. This parameter can be sent on BCCH or PBCCH or individually in PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER or PS HANDOVER COMMAND messages. + +If for a GSM cell the CCN\_SUPPORTED parameter is available and if it indicates that CCN mode shall not be entered towards that cell, then the mobile station shall perform the cell change and not enter CCN mode. If the cell reselection is triggered by the path loss criterion parameter C1 becoming negative, the mobile station may perform the cell change without entering the CCN mode. + +If the target cell is a GSM cell and the CCN\_SUPPORTED parameter is available and if it indicates that CCN mode shall be entered towards that cell or if the CCN\_SUPPORTED parameter is not available, then instead of performing the cell change, the mobile station shall start timer T3206 and enter the CCN mode. At the first possible opportunity, the MS shall then, when in CCN mode, inform the network about the proposed target cell by sending a PACKET CELL CHANGE NOTIFICATION message, stop timer T3206, start timers T3208 and T3210. + +If the target cell is a 3G cell and if CCN is activated towards 3G cells or if the target cell is an E-UTRAN cell and the mobile station supports "CCN towards E-UTRAN, E-UTRAN Neighbour Cell measurement reporting and Network controlled cell reselection to E-UTRAN" and if CCN is activated towards E-UTRAN cells, then instead of performing the cell change, the mobile station shall start timer T3206 and enter the CCN mode. At the first possible opportunity, the MS shall then, when in CCN mode, inform the network about the proposed target cell by sending a PACKET CELL CHANGE NOTIFICATION message, stop timer T3206, start timers T3208 and T3210. + +If the target cell is a GAN cell and the CCN\_SUPPORTED parameter is available and if it indicates that CCN mode shall be entered towards that cell or if the CCN\_SUPPORTED parameter is not available, then instead of performing the cell change, the mobile station shall start timer T3206 and enter the CCN mode. At the first possible opportunity, a mobile station may, when in CCN mode, send a PACKET CELL CHANGE NOTIFICATION message that includes the ARFCN/BSIC for the GAN cell and indicates an RXLEV of 63 for the GAN cell and start timers T3208 and T3210. + +The PACKET CELL CHANGE NOTIFICATION message shall contain the identity of the proposed target cell. A GSM cell shall be identified by the ARFCN for the BCCH and the BSIC. A 3G-FDD cell shall be identified by FDD\_ARFCN, Bandwidth\_FDD and Scrambling Code. A 3G-TDD cell shall be identified by TDD\_ARFCN, Bandwidth\_TDD, Cell parameter and Sync Case. An E-UTRAN cell shall be identified by EARFCN, Measurement Bandwidth and Physical Layer Cell Identity. + +The PACKET CELL CHANGE NOTIFICATION message shall also contain measurement reports for the proposed cell and for six other (see 3GPP TS 45.008) neighbour cells, if available. If no 3G neighbour cell is available for reporting, and the 3G CCN Measurement Report Struct is included in the message, the MS shall set the N\_3G field to 0 and the 3G\_CELL\_LIST\_INDEX field to 127, see sub-clause 11.2.3a. If 3G Neighbour cells are reported, the type of report for FDD cells are specified by the FDD\_REP\_QUANT parameter and the number of 3G reports in the message are specified by the parameters FDD\_MULTIRAT\_REPORTING and TDD\_MULTIRAT\_REPORTING. These parameters may either be broadcast on BCCH or PBCCH or sent to the mobile station in a PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER message. If E-UTRAN Neighbour cells are reported, the type of report is specified by the E-UTRAN\_REP\_QUANT parameter and the maximum number of E-UTRAN reports in the message is specified by the parameter E-UTRAN\_MULTIRAT\_REPORTING. These parameters may either be broadcast on BCCH or sent to the mobile station in a PACKET MEASUREMENT ORDER message. + +When a multi-RAT MS attempts cell change to a UTRAN (respectively E-UTRAN) CSG cell or a detected hybrid cell if the cell's CSG ID is included in the CSG Whitelist of the MS and CCN procedures are used, if the *CSG Cells Reporting Description* IE has been received from the network and the mobile station supports CSG Cells Reporting, the mobile station shall include in the PACKET CELL CHANGE NOTIFICATION message the CSG-ID and the routing parameters of the target cell. In this case, if a cell change failure occurs, the subsequent transmission of a PACKET CELL CHANGE FAILURE message shall contain the routing parameters of the target cell. + +In CCN mode the mobile station shall continue the data transfer and store neighbour cell system information if received in instances of the PACKET NEIGHBOUR CELL DATA message, but not perform the cell change. At receipt of the first PACKET NEIGHBOUR CELL DATA message or PACKET CELL CHANGE CONTINUE message or PACKET CELL CHANGE ORDER message or PS HANDOVER COMMAND message, the mobile station shall stop the timer T3210. + +The mobile station shall retransmit the PACKET CELL CHANGE NOTIFICATION message once at the first possible opportunity when the timer T3210 expires. + +The mobile station shall leave CCN mode when either CCN is no longer enabled (towards all GSM, 3G or E-UTRAN neighbour cells with the CCN\_ACTIVE/3G\_CCN\_ACTIVE/E-UTRAN\_CCN\_ACTIVE bit or towards the cell that had been re-selected) or when the network has responded with a PACKET CELL CHANGE CONTINUE or PACKET CELL CHANGE ORDER message or a PS HANDOVER COMMAND message or when either of the timers T3206 or T3208 have expired. + +If the mobile station has been individually ordered to enable CCN, the order is only valid within the cell where the order is given. When a cell change has been performed using the cell reselection procedure, the mobile station shall use CCN in the new cell only if individually ordered in the previous cell with the PACKET CELL CHANGE ORDER message or if individually ordered or broadcast in the new cell. When a cell change has been performed using the PS handover procedure, the mobile station shall enable CCN in the new cell only if individually ordered in the previous cell with the PS HANDOVER COMMAND message or if individually ordered or broadcast in the new cell. + +Upon receiving a PACKET CELL CHANGE NOTIFICATION message, the network shall ignore any 3G neighbour cell report with a 3G\_CELL\_LIST\_INDEX equal to 127. + +After receiving a PACKET CELL CHANGE NOTIFICATION message from the mobile station the network can behave in different ways as described below: + +- 1) The network responds with a PACKET CELL CHANGE CONTINUE message. + +If a mobile station as response to a PACKET CELL CHANGE NOTIFICATION message receives a PACKET CELL CHANGE CONTINUE message without receiving any neighbour cell system information, the mobile station shall stop timer T3208, stop timer T3210 if still running, leave CCN mode and continue cell reselection in NC0/NC1 mode. + +- 2) The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message if the proposed target cell is a GSM cell in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE CONTINUE message. The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE CONTINUE message is received, the mobile station shall stop timer T3208, leave CCN mode and continue the cell reselection in NC0/NC1 mode irrespective of the cell indicated in the ARFCN and BSIC parameters in the PACKET CELL CHANGE CONTINUE message. + +- 3) The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message if the proposed target cell is a GSM cell, or for any other GSM cell, in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE ORDER message or a PS HANDOVER COMMAND message. + +The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE ORDER message is received, the mobile station shall stop timer T3208, leave CCN mode and follow the procedures as specified for the PACKET CELL CHANGE ORDER message (sub-clause 8.4) and in sub-clause 8.8.1. When the PS HANDOVER COMMAND message is received, the mobile station shall stop timer T3208, leave CCN mode and follow the procedures as specified for the PS HANDOVER COMMAND message in sub-clause 8.10.4. + +- 4) The network orders the mobile station into NC2 mode. + +A mobile station may in response to a PACKET CELL CHANGE NOTIFICATION message receive a PACKET MEASUREMENT ORDER message from the network indicating NC2 mode. When the mobile station receives the NC2 order it shall leave CCN mode, stop timer T3208, stop timer T3210 if still running, and go into NC2 mode. + +When the NC2 mode has been ordered, the network may send PACKET NEIGHBOUR CELL DATA messages on the PACCH before sending the PACKET CELL CHANGE ORDER message to the mobile station. When the NC2 mode has been ordered, the network shall send PACKET NEIGHBOUR CELL DATA messages on the PACCH before sending the PS HANDOVER COMMAND message (see sub-clause 8.10.2) to the mobile station except if these messages are not needed by the mobile station (i.e. for the case of PS handover to a GAN cell). + +- 5) No network response + +When timer T3210 expires, the mobile station shall retransmit once the PACKET CELL CHANGE NOTIFICATION message at the first possible opportunity. + +When timer T3208 expires, the mobile station shall leave CCN mode and continue cell reselection in NC0/NC1 mode as described in sub-clause 5.5.1.1 and in 3GPP TS 45.008. + +The CCN mode is only valid in packet transfer mode or in MAC-Shared state. If the mobile station is in CCN mode when entering packet idle mode or MAC-Idle state, the mobile station shall stop the timers T3206 and T3208, stop timer T3210 if still running, leave CCN mode and continue the cell reselection procedure according to the NC0/NC1 procedures. If PACKET NEIGHBOUR CELL DATA messages are received on the PACCH before entering packet idle mode or MAC-Idle state and the cell identity parameters are included, this information may then be used at the next cell change. + +If the cell reselection criteria have changed during the time the MS is in CCN mode but the path loss criterion parameter C1 remains positive, the MS shall, without notifying the network about the new preferred cell, remain in CCN mode until the criteria for CCN mode are no longer fulfilled. When leaving CCN mode the MS shall obey the new criteria according to the normal rules as specified in sub-clause 5.5.1.1 and in 3GPP TS 45.008 unless a PACKET CELL CHANGE ORDER or a PS HANDOVER COMMAND message has been received (see bullet 3 above). If the path loss criterion parameter C1 becomes negative while the MS is in CCN mode, the MS may leave the CCN mode without notifying the network and perform the cell change. + +## 8.9 RR connection establishment in packet transfer mode + +### 8.9.0 General + +The initiation of the procedure and the assignment of resources for the establishment of the RR connection are described in sub-clauses 8.9.1 and 8.9.2, respectively. A mobile station that has enabled PEO may use mobile originated RR connection establishment for GSM services (see 3GPP TS 23.060 [19]) while in packet transfer mode in which case it shall abort the ongoing TBFs, leave packet transfer mode and enter packet idle mode when the RR connection is released. + +The establishment of the main signalling link and the completion of the establishment of the RR connection are described in 3GPP TS 44.018. + +## 8.9.1 Initiation + +### 8.9.1.1 Initiation by the mobile station + +#### 8.9.1.1.1 Transmission of the PACKET CS REQUEST message + +The RR connection establishment procedure is initiated by the RR entity of the mobile station. Initiation is triggered by request from the MM sublayer to enter dual transfer mode. The request from the MM sublayer to establish the RR connection specifies an establishment cause. + +The RR entity in the mobile station shall not request the establishment of an RR connection while in packet transfer mode from the point where it receives a PS HANDOVER COMMAND message until the PS handover procedure has been completed (see sub-clause 8.10). + +On receipt of the RR connection establishment request from upper layer the mobile station shall start timer T3196. At expiry of timer T3196, the mobile station shall release all ongoing TBFs and start RR connection establishment as specified in 3GPP TS 44.018. If a mobile station that supports PS handover receives a PS HANDOVER COMMAND message while T3196 is running it shall stop T3196, abort its current attempt to establish an RR connection and not make another attempt to establish an RR connection until completion of the PS handover procedure. + +If the contention resolution is not solved, the mobile station shall delay the transmission of the PACKET CS REQUEST message until contention resolution is solved. + +If the countdown procedure has been started on all the ongoing uplink TBFs, none of those TBFs is operating in extended uplink TBF mode and there is no downlink TBF in progress, the mobile station may either send the PACKET CS REQUEST message, or may immediately release the ongoing TBF(s) and start an RR connection establishment as specified in 3GPP TS 44.018. + +The mobile station shall initiate the RR connection establishment by sending PACKET CS REQUEST messages on the PACCH. The mobile station is allowed to retransmit the PACKET CS REQUEST message once while timer T3196 is running. The second sending occurrence of this message shall take place at the first suitable opportunity at least 0.75 s after the first transmission of that message. + +#### 8.9.1.1.2 Answer from the network + +Upon receipt of a PACKET CS REQUEST message, the network shall answer to the mobile station by encapsulating one of the following RR messages in the PACKET CS COMMAND message, and sending the PACKET CS COMMAND message on PACCH: + +- DTM ASSIGNMENT COMMAND message (see sub-clause 8.9.2.1); or +- IMMEDIATE ASSIGNMENT message (see sub-clause 8.9.2.2); or +- IMMEDIATE ASSIGNMENT REJECT message (see sub-clause 8.9.2.3). + +Upon receipt of PACKET CS COMMAND message encapsulating one of the above messages the mobile station shall stop timer T3196. + +### 8.9.1.2 Initiation by the network + +The network initiates the RR connection establishment procedure by sending a PACKET CS COMMAND message to the mobile station on PACCH, encapsulating one of the following RR messages: + +- DTM ASSIGNMENT COMMAND message (see sub-clause 8.9.2.1); or +- IMMEDIATE ASSIGNMENT message (see sub-clause 8.9.2.2). + +After sending the mobile station a PS HANDOVER COMMAND message the network shall not initiate the establishment of an RR connection for that mobile station until the PS handover procedure has been completed (see sub-clause 8.10). + +## 8.9.2 Assignment + +### 8.9.2.1 Assignment of both dedicated and packet resource + +The network may allocate both a dedicated channel and radio resources on one or more PDCHs to be used by the mobile station and shall in this case send a DTM ASSIGNMENT COMMAND encapsulated in a PACKET CS COMMAND message. Having sent the DTM ASSIGNMENT COMMAND message, the network starts timer T3107, specified in 3GPP TS 44.018. The allocated dedicated channel shall be of TCH type. The network may also reallocate radio resources (PDCH(s)) in the DTM ASSIGNMENT COMMAND message. If both the RR Packet Uplink Assignment and the RR Packet Downlink Assignment information elements are omitted in the DTM ASSIGNMENT COMMAND the network implicitly indicates that the current radio resources shall be maintained. The mobile station shall act on the DTM ASSIGNMENT COMMAND message as specified in 3GPP TS 44.018. + +On receiving an encapsulated DTM ASSIGNMENT COMMAND message, the mobile station shall establish the main signalling link using the procedure described in 3GPP TS 44.018. + +The completion of the establishment of the RR connection is described in 3GPP TS 44.018. + +If timer T3107 elapses before the successful establishment of the main signalling link on the new channel, both the new CS channel and new PS resources are released. If the encapsulated DTM ASSIGNMENT COMMAND message was sent in response to a PACKET CS REQUEST message received from the mobile, then the old PS resources are also released. + +NOTE: If timer T3107 expires and the procedure was initiated by the network, the subsequent network behaviour with respect to the old PS resources is implementation dependent. + +### 8.9.2.2 Assignment of dedicated resource only + +The network may allocate only a dedicated channel to the mobile station and shall in this case send an IMMEDIATE ASSIGNMENT encapsulated in a PACKET CS COMMAND message. Having sent the IMMEDIATE ASSIGNMENT message, the network starts timer T3101, specified in 3GPP TS 44.018. + +If a mobile station receives an encapsulated IMMEDIATE ASSIGNMENT message which either does not specify a starting time or specifies a starting time which has already elapsed, the mobile station shall immediately: + +- perform an abnormal release without retry (see sub-clause 8.7.1), if no uplink TBF is in progress, or, +- perform an abnormal release with access retry (see sub-clause 8.7.2), if one or more uplink TBFs are in progress. + +On receiving an encapsulated IMMEDIATE ASSIGNMENT message which specifies a starting time which has not yet elapsed, the mobile station shall wait until the specified start time. If, at that time, no uplink TBF is in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1); else (i.e. one or more uplink TBFs are in progress) the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). + +The mobile station shall proceed with the assignment by establishing the main signalling link using the procedure described in 3GPP TS 44.018. In respect of the RR connection, the mobile station shall act on the starting time information element, if present, as specified in 3GPP TS 44.018. + +The completion of the establishment of the RR connection is described in 3GPP TS 44.018. + +If timer T3101 elapses before the main signalling link is established, the new CS channel is released. If the encapsulated IMMEDIATE ASSIGNMENT message was sent in response to a PACKET CS REQUEST message received from the mobile, the old PS resources are also released. + +NOTE: If timer T3101 expires and the procedure was initiated by the network, the subsequent network behaviour with respect to the old PS resources is implementation dependent. + +### 8.9.2.3 Rejection of the mobile station request + +If no dedicated channel is available for assignment, the network may send to the mobile station an IMMEDIATE ASSIGNMENT REJECT message encapsulated in a PACKET CS COMMAND message. + +On receipt of the encapsulated IMMEDIATE ASSIGNMENT REJECT message the mobile station shall stop sending PACKET CS REQUEST messages, starts timer T3122 with the indicated value ("wait indication" information element, specified in 3GPP TS 44.018) and continue in packet transfer mode. + +The behaviour of the mobile station while timer T3122 is running is specified in 3GPP TS 44.018. + +### 8.9.3 (void) + +## 8.9.4 Abnormal cases + +### 8.9.4.1 RR connection establishment initiated by the mobile station + +If a failure occurs on the mobile station side before the successful establishment of the main signalling link, the allocated channels are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If the radio resources have been dropped before the network has a chance to respond to the PACKET CS REQUEST, the network shall abort the current DTM procedure. +- If the mobile station does not receive the PACKET CS COMMAND message after it has sent a corresponding PACKET CS REQUEST message (i.e. expiry of timer T3196), the mobile station shall perform an abnormal release with the RR connection establishment retry (see sub-clause 8.7.4). +- If the mobile station receives the DTM ASSIGNMENT COMMAND or the IMMEDIATE ASSIGNMENT message specifying frequencies that are not all in one frequency band then the mobile station shall perform an abnormal release with RR connection establishment retry (see sub-clause 8.7.4). +- If the mobile station receives the DTM ASSIGNMENT COMMAND or the IMMEDIATE ASSIGNMENT message specifying a frequency that is in a frequency band not supported by the mobile station then the mobile station shall perform an abnormal release with RR connection establishment retry (see sub-clause 8.7.4). +- If the information in the DTM ASSIGNMENT COMMAND message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with RR connection establishment retry (see sub-clause 8.7.4). +- If the information in the DTM ASSIGNMENT COMMAND message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with RR connection establishment retry (see sub-clause 8.7.4). +- If a failure in the assignment message (e.g. DTM ASSIGNMENT COMMAND or the IMMEDIATE ASSIGNMENT message) is due to any other reason, the mobile station shall perform an abnormal release with RR connection establishment retry (see sub-clause 8.7.4). +- If the mobile fails to establish the main signalling link, it shall perform an abnormal release with RR connection establishment retry (see sub-clause 8.7.4). + +### 8.9.4.2 RR connection establishment initiated by the network + +If a failure occurs on the mobile station side before the successful establishment of the main signalling link, the allocated channels are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If the information in the DTM ASSIGNMENT COMMAND message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). +- If the information in the DTM ASSIGNMENT COMMAND message does not properly specify an uplink and downlink PDCH, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). +- If the mobile station has been reassigned a TBF in EGPRS TBF mode and the MS does not support EGPRS, or has been reassigned an MCS (e.g. 8-PSK in the uplink) that the MS does not support, the MS shall enter to dedicated mode and notify higher layers (TBF establishment failure). +- On expiry of timer T3190, the mobile station shall enter dedicated mode. +- If a failure in the DTM ASSIGNMENT COMMAND message is due to any other reason, the mobile station shall return to packet idle mode. + +- If there is a failure in the IMMEDIATE ASSIGNMENT message the mobile station shall continue in packet transfer mode. +- If the mobile fails to establish the main signalling link, it shall perform an abnormal release with RR connection establishment retry (see sub-clause 8.7.4). + +## 8.10 Packet Switched Handover procedure + +### 8.10.1 General + +This procedure is only applicable in packet transfer mode when both the mobile station and the network support PS handover. The support of PS handover procedures requires the support of PFC procedures in both the network and the mobile station. In packet transfer mode, a mobile station that supports PS handover may receive a PS HANDOVER COMMAND message from the BSS indicating the resources to be used in the new cell. + +The support of the PS handover procedures is optional for the mobile station and the network and is indicated in the *MS Radio Access Capability* IE. For an E-UTRAN capable multi-RAT mobile station, the support of PS handover to E-UTRAN is indicated in the "GERAN to E-UTRAN support in GERAN packet transfer mode" field within the *MS Radio Access Capability* IE (see 3GPP TS 24.008). A mobile station supporting the PS handover procedures shall also support the extended RLC/MAC control message segmentation as defined in 9.1.12a. + +### 8.10.2 Neighbour Cell System Information Distribution + +For the case of PS handover from *A/Gb mode* to *A/Gb mode* the network shall send the mobile station PACKET NEIGHBOUR CELL DATA messages containing PSI messages (PBCCH allocated in new cell) or SI messages (PBCCH not allocated in new cell) corresponding to the new cell prior to sending it the PS HANDOVER COMMAND message directing it to that cell. PACKET NEIGHBOUR CELL DATA messages are received on PACCH as described in sub-clause 8.8.1. The minimum set of SI and PSI messages to be sent in PACKET NEIGHBOUR CELL DATA messages is as follows: + +- If PBCCH is not allocated in the new cell then SI3, SI1 (if present in the new cell) and SI13 shall be sent. +- If PBCCH is allocated in the new cell then PSI1, a consistent set of PSI2 messages and PSI14 shall be sent. + +For the case of PS handover from *Iu mode* to *A/Gb mode* or from *GAN mode* to *A/Gb mode* or from E-UTRAN to *A/Gb mode* the network shall send the mobile station the same set of PSI messages or SI messages corresponding to the new cell as for the case of PS handover from *A/Gb mode* to *A/Gb mode*. In this case the network sends the mobile station the system information corresponding to the new cell within the Handover from UTRAN Command message as described in 3GPP TS 25.331 for the case of PS handover from *Iu mode* to *A/Gb mode* or within the GA-PSR HANDOVER COMMAND message as described in 3GPP TS 44.318 [42] for the case of PS handover from *GAN mode* to *A/Gb mode* or within the *MobilityFromEUTRACommand* message as described in 3GPP TS 36.331 [45] for the case of PS handover from *E-UTRAN* to *A/Gb mode*. + +For the case of PS handover from *A/Gb mode* to *Iu mode* or from *A/Gb mode* to *GAN mode* or from *A/Gb mode* to E-UTRAN, system information corresponding to the new cell is sent to the mobile station in the new cell as described in 3GPP TS 25.331 for PS handover to *Iu mode* or as described in 3GPP TS 44.318 [42] for PS handover to *GAN mode* or as described in 3GPP TS 36.331 [45] for PS handover to E-UTRAN. + +### 8.10.3 PS Handover at the network side + +#### 8.10.3.1 Initiation of PS Handover Procedure + +The source BSS may initiate the PS handover procedure as a result of various trigger conditions such as, but not restricted to, the following: + +- Upon receiving a measurement report or a PACKET CELL CHANGE NOTIFICATION message from a mobile station operating in *A/Gb mode*. +- Upon determining that resource limitations exist for the serving cell. +- Upon receiving the *Service UTRAN CCO* IE from the SGSN indicating that a mobile station operating in *A/Gb mode* would be better served in a cell supporting a different RAT. + +If the mobile station is not already in NC2 then the source BSS may order the mobile station to enter NC2 before initiating the PS handover procedure. For the normal case of PS handover the target RNC/BSS/GANC/eNB receives a network request to allocate resources required to perform a PS handover. For the optimized case of PS handover (applicable only for *A/Gb mode* to *A/Gb mode* PS handover - see 3GPP TS 43.129) an SGSN request for the BSS to allocate resources is not required as the resources required to perform a PS handover are allocated autonomously by the BSS (i.e. without SGSN involvement). + +### 8.10.3.2 A/Gb to A/Gb PS Handover + +For both the normal and optimized cases of PS handover from *A/Gb mode* to *A/Gb mode* the (source) BSS shall impose the following restrictions on RLC/MAC control plane corresponding to a mobile station for which the PS handover procedure is ongoing: + +- All mobile station requests to establish new uplink TBFs shall be ignored and no new downlink TBFs shall be established. +- The PS HANDOVER COMMAND message shall be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a) if three or more RLC/MAC control blocks are required to send the complete message. + +After sending the PS HANDOVER COMMAND to the MS, the source BSS shall continue to schedule opportunities for the mobile station to transmit an RLC/MAC control message, either by means of an existing uplink TBF, or by means of polling using an existing downlink TBF, for a period of time sufficiently long to allow the mobile station to transmit a PACKET CELL CHANGE FAILURE message (should a PS handover failure occur). During this period, the BSS may allocate fewer transmission opportunities than would otherwise be required according to the QoS requirements of the ongoing PFCs. No TBFs shall be released during this period except on receipt of a DELETE-BSS-PFC PDU from the SGSN. + +For both the normal and optimized cases of PS handover from *A/Gb mode* to *A/Gb mode* the (target) BSS creates a complete PS HANDOVER COMMAND message that is sent to the mobile station in the old cell: + +For the normal case of PS handover the source BSS shall send the Page Mode, Global TFI and Container ID information elements to the target BSS which uses them to create a complete PS HANDOVER COMMAND message (see sub-clause 11.2.43). + +For the normal case of PS handover the source BSS receives a complete PS HANDOVER COMMAND message from the target BSS (passed through the SGSN) and then sends it to the mobile station. For the optimized case of PS handover the BSS creates a complete PS HANDOVER COMMAND message and sends it directly to the mobile station. + +If the PS HANDOVER COMMAND indicates RLC reset for a TBF allocated in the new cell corresponding to the PFC(s) receiving a PS handover, the target BSS shall initialize one or more new RLC entities to support that TBF. Otherwise, the TBF allocated in the new cell shall be supported using the same set of RLC entities used to support the TBF in the old cell corresponding to the same PFC(s) (i.e. the RLC state machine is maintained across PS handover). + +The PS HANDOVER COMMAND message created by the target BSS shall always allocate resources for at least one uplink TBF to ensure that the mobile station can send PS HANDOVER ACCESS messages (if required) and one or more RLC data blocks in the new cell. When only one uplink TBF is allocated by the PS HANDOVER COMMAND message and does not correspond to a PFC, RLC acknowledged mode shall be used. + +The PS HANDOVER COMMAND message shall include the PS Handover Radio Resources Info IE if the allocated resources are not required to support any of the features Downlink Dual Carrier, Downlink Multi Carrier, EGPRS2, Fast Ack/Nack Reporting or RTTI configurations. If the allocated resources are required to support Downlink Multi Carrier the network shall include the *PS Handover Radio Resources 3 IE* in the PS HANDOVER COMMAND message. Otherwise, the network shall include the PS Handover Radio Resources 2 Info IE in the PS HANDOVER COMMAND message. + +The PS HANDOVER COMMAND message created by the target BSS shall indicate the PS Handover type with the synchronization indication field, i.e. non-synchronized, synchronized or pre-synchronized PS handover. + +The PS HANDOVER COMMAND shall contain the PFI for each TBF being set up if and only if both the network and the mobile station support multiple TBFs. A mobile station which receives a PS HANDOVER COMMAND and which does not support multiple TBFs shall ignore any PFI value(s) received in the PS HANDOVER COMMAND. The target BSS expects one or more PS HANDOVER ACCESS messages from the mobile station whenever Handover Reference + +information is included in the PS HANDOVER COMMAND message. Handover Reference information shall always be included whenever non-synchronized PS handover is used. + +Depending on the type of handover the target BSS shall proceed as follows: + +- In case of a synchronized or pre-synchronized PS handover the target BSS shall enable the reception of RLC data blocks on all uplink TBFs allocated by the PS HANDOVER COMMAND message. +- In case of a non-synchronized PS handover the target BSS shall, upon reception of the first PS HANDOVER ACCESS message containing the expected Handover Reference value, send the PACKET PHYSICAL INFORMATION message to the mobile station and then enable the reception of RLC data blocks on all uplink TBFs allocated by the PS HANDOVER COMMAND message. +- The BSS should schedule USFs on at least one uplink TBF in the target cell to minimize the delay incurred by the mobile station waiting for a USF in the target cell. + +The target BSS considers the PS handover procedure to be successfully completed upon receiving the first correct uplink RLC block on any of the uplink TBFs allocated to the mobile station in the PS HANDOVER COMMAND message. + +If the target BSS supports blind transmission it may begin transmitting downlink data that becomes available prior to determining that the PS handover procedure has been successfully completed. Otherwise, it may discard downlink data that becomes available prior to determining that the PS handover procedure has been successfully completed. + +If the target BSS supports network sharing in the target cell and the MS Radio Access Capabilities IE (see 3GPP TS 24.008) indicates a network sharing supporting MS, it shall include in the PS HANDOVER COMMAND message the *Selected PLMN Index* field (see sub-clause 10.4.27) corresponding to the PLMN received in the Target Cell Identifier IE in the PS HANDOVER REQUEST message (see 3GPP TS 48.018). + +### 8.10.3.3 GERAN A/Gb to Iu/E-UTRAN PS Handover + +For the case of PS handover from *A/Gb mode* to *Iu mode* or E-UTRAN the source BSS proceeds as described above for the normal case of *A/Gb mode* to *A/Gb mode* PS handover except for the following: + +- The source BSS shall create a complete PS HANDOVER COMMAND message using local values for the Page Mode, Global TFI and Container ID information elements and therefore shall not send these information elements to the target RNC or eNB. +- For the case of PS handover to *Iu mode*, the source BSS receives a complete Handover to UTRAN Command message from the target RNC (passed through the SGSN) and sends it to the mobile station within a PS HANDOVER COMMAND message. +- For the case of PS handover to E-UTRAN, the source BSS receives a complete (RRC E-UTRA) HandoverCommand message as defined in 3GPP TS 36.331 [45] from the target eNB (passed through the MME and SGSN) and sends it to the mobile station within a PS HANDOVER COMMAND message. +- The source BSS shall not send the mobile station unsolicited PACKET NEIGHBOUR CELL DATA messages in the old cell as system information corresponding to the new cell is sent to the mobile station in the new cell as described in 3GPP TS 25.331 (for PS handover to *Iu mode*) or as described in 3GPP TS 36.331 (for PS handover to E-UTRAN). + +### 8.10.3.4 Iu/E-UTRAN to GERAN A/Gb PS Handover + +For the case of PS handover from *Iu mode* or E-UTRAN to *A/Gb mode* the target BSS proceeds as described above for the normal case of *A/Gb mode* to *A/Gb mode* PS handover except that a complete PS HANDOVER COMMAND message is created by the target BSS using local values for the Page Mode, Global TFI and Container ID information elements (i.e. they are not passed to the target BSS from the source RNC or eNB) and the PS HANDOVER COMMAND message shall always indicate RLC reset and non-synchronized PS handover. The PS HANDOVER COMMAND message is sent to the MS as part of the *MobilityFromEUTRACommand* in E-UTRAN as specified in 3GPP TS 36.331 [45]. + +### 8.10.3.5 A/Gb to GAN PS Handover + +When the BSS and the mobile station support PS handover to *GAN mode* the normal case of *A/Gb mode* to *A/Gb mode* PS handover is followed as described in sub-clause 8.10.3.2 except for the following: + +- The target GANC shall only provide values for the mandatory fields within the PS Handover Radio Resources IE included within the PS HANDOVER COMMAND message it sends back to the source BSS. +- The source BSS will not send the mobile station system information corresponding to the target GAN cell prior to sending it a PS HANDOVER COMMAND message (i.e. the mobile station acquires the system information required for the target GAN cell during GAN registration - see 3GPP TS 44.318 [42]). + +### 8.10.3.6 GAN to A/Gb PS Handover + +For the case of PS handover from *GAN mode* to *A/Gb mode* the source GANC proceeds as described in 3GPP TS 44.318 [42]. The target BSS proceeds as described in sub-clause 8.10.3.2 for the normal case of *A/Gb mode* to *A/Gb mode* PS handover except that a complete PS HANDOVER COMMAND message is created by the target BSS using local values for the Page Mode, Global TFI and Container ID information elements (i.e. they are not passed to the target BSS from the source GANC) and the PS HANDOVER COMMAND message shall always indicate RLC reset for each PFC and non-synchronized PS handover. + +## 8.10.4 PS Handover at the mobile station side + +### 8.10.4.1 A/Gb to A/Gb PS Handover + +Upon reception of the PS HANDOVER COMMAND message for PS handover from *A/Gb mode* to *A/Gb mode*, the mobile station shall proceed as follows: + +- If an RLC/MAC control block containing a part of the PS HANDOVER COMMAND message contains a valid RRBP field or a polling response is outstanding the mobile station shall send a corresponding PACKET CONTROL ACKNOWLEDGMENT message (in the specified uplink radio block) prior to switching to the new cell. +- RLC/MAC control plane signalling shall be suspended except for the signalling needed to complete the PS handover procedure or to signal a failure of the PS handover procedure. +- The mobile station shall suspend the uplink transmission of user plane data. +- Each outstanding request for establishment or reconfiguration of an uplink TBF in the old cell shall be aborted and the corresponding instance of T3168 shall be stopped. +- All timers related to the RLC contexts in the old cell keep running. +- Timers T3180 and T3190 related to the ongoing TBFs in the old cell and which are currently running shall be re-started. +- If the timer T3192 related to a TBF in the old cell expires, the mobile station shall consider the corresponding TBF that was ongoing in the old cell as implicitly released. +- The mobile station shall start timer T3218, move to the new cell and perform the physical channel establishment as described in sub-clause 8.10.4.4. +- The mobile station may receive downlink RLC data blocks in the new cell prior to determining that the PS handover has been successfully completed if the target BSS uses blind transmission. If this occurs the mobile station shall forward the corresponding user data to upper layers if the PS HANDOVER COMMAND message did not include the *NAS Container for PS Handover* IE. Otherwise, the mobile station may either discard the received RLC data blocks or buffer them until the successful completion of the PS handover procedure at which point the corresponding user data shall be deciphered by the upper layers based on information contained within the *NAS Container for PS Handover* IE. + +NOTE: It is expected that PS Handover procedure will be completed successfully or terminated before the expiry of T3180 or T3190 and therefore that the MS will not release any TBFs due to the expiry of T3180 or T3190 during the PS Handover procedure. The mobile station considers the PS handover procedure to be successfully completed in the following cases: + +- Upon receiving a PACKET PHYSICAL INFORMATION message in the new cell in case of a non-synchronized PS handover (see sub-clause 8.10.4.4.3). +- Upon detecting the first USF for any uplink TBF assigned to the MS in the new cell in case of a synchronized and pre-synchronized PS handover (see subclause 8.10.4.4.1 and 8.10.4.4.2). + +If the mobile station is waiting for the PACKET PHYSICAL INFORMATION message when it receives a downlink RLC data block in which a valid polling indication is provided, it shall ignore the polling indication. + +Upon successfully completing the PS handover procedure the mobile station shall proceed as follows: + +- Stop T3216 (if running), consider all TBFs that were ongoing in the old cell as implicitly released and if the *NAS Container for PS Handover* IE was included in the PS HANDOVER COMMAND message it shall be sent to upper layers. +- If the PS HANDOVER COMMAND indicates RLC reset the mobile station shall initialize new RLC entities to support the allocated TBFs. Otherwise, the TBFs allocated in the new cell shall be supported using the same RLC entities used to support the TBFs in the old cell corresponding to the same PFCs (i.e. the RLC state machines are maintained across PS handover). +- The mobile station shall resume the uplink transmission of user plane data. +- The mobile station shall trigger a cell update or other GMM specific procedures, as appropriate according to the GMM requirements (see 3GPP TS 24.008). + +#### 8.10.4.2 A/Gb to Iu/E-UTRAN PS Handover + +Upon receiving a PS HANDOVER COMMAND message for PS handover from GERAN A/Gb mode to *Iu mode* or E-UTRAN, the mobile station shall act on the message if it is able to perform PS handover based on the content of the received message. If the PS HANDOVER COMMAND message is acted on the mobile station shall start the PS handover procedure and proceed as described above for the case of *A/Gb mode* to *A/Gb mode* PS handover while in the old cell. Upon moving to the new cell the mobile station shall proceed as described in 3GPP TS 25.331 for handover to *Iu mode* or as described in 3GPP TS 36.331 for handover to *E-UTRAN*. Upon successfully completing the PS handover procedure all TBFs that were ongoing in the old cell shall be considered as implicitly released. + +#### 8.10.4.3 Iu/E-UTRAN to A/Gb PS Handover + +Upon receiving a Handover from UTRAN Command message for PS handover from *Iu mode* to *A/Gb mode* or a *MobilityFromEUTRACommand* message for PS handover from *E-UTRAN* to *A/Gb mode*, the mobile station shall act on the message if all of the following conditions are satisfied: + +- It is able to perform PS handover based on the content of the received message. +- The Handover from UTRAN Command or *MobilityFromEUTRACommand* message contains the minimum set of PSI or SI messages required for mobile station to operate in the new cell (see sub-clause 8.10.4.1.). +- The PS HANDOVER COMMAND message carried within the Handover from UTRAN Command or *MobilityFromEUTRACommand* message provides resources for at least one uplink TBF in the new cell. + +If the Handover from UTRAN Command or *MobilityFromEUTRACommand* message is acted on the mobile station shall start the PS handover procedure and proceed as follows: + +- The mobile station shall act as described in 3GPP TS 25.331 (for handover from *Iu mode*) or as described in 3GPP TS 36.331 (for handover from E-UTRAN) prior to switching to the new cell except for the following: +- It shall ignore the value of the Page Mode, Global TFI and Container ID information elements included in the PS HANDOVER COMMAND message carried within the Handover from UTRAN Command or *MobilityFromEUTRACommand* message. +- After switching to the new cell the mobile station shall proceed as described above for the case of *A/Gb mode* to *A/Gb mode* PS handover except for the following: +- Upon successfully completing the PS handover procedure the mobile station shall stop T3216 (if running), consider all radio bearers that were ongoing in the old cell as implicitly released, send the *NAS Container for PS Handover* IE to upper layers if it was included in the PS HANDOVER COMMAND message, start an instance of T3180 corresponding to each uplink TBF allocated by the PS HANDOVER COMMAND message and start an instance of T3190 corresponding to each downlink TBF allocated by the PS HANDOVER COMMAND message. +- Upon successfully completing the PS handover procedure the mobile station shall always establish a new RLC entity for each TBF allocated by the PS HANDOVER COMMAND message. + +#### 8.10.4.4 Physical channel establishment + +##### 8.10.4.4.1 General + +Three procedures are defined. The support of them is mandatory in the mobile station. + +If the network requests the transmission of the PS HANDOVER ACCESS message it shall be sent with highest transmission priority using either the 8-bit or 11-bit access burst format on the PACCH associated with any uplink TBF allocated in the PS HANDOVER COMMAND message for which the mobile station detects an assigned USF value. Its content consists of the handover reference field. The burst format used shall be that specified by the ACCESS\_BURST\_TYPE in the system information for the target cell. + +Upon detecting the first USF for any uplink TBF assigned to the MS in the new cell, the MS shall stop T3218. + +##### 8.10.4.4.2 Synchronized cell case + +If the timing advance with the new cell calculated by the mobile station is not out of range, i.e. smaller than or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004, or if the new cell does accept out of range timing advance as indicated in the PS HANDOVER COMMAND message, the mobile station acts on the message. + +After having switched to the assigned channels, if the Handover Reference information is included within the PS HANDOVER COMMAND message the mobile station shall send four times the PS HANDOVER ACCESS message. + +The mobile station activates the channels in sending and receiving mode. The MS may activate the channels in downlink while sending access bursts. + +##### 8.10.4.4.3 Pre-synchronized cell case + +The details of the use of this procedure are described in 3GPP TS 45.010. + +After having switched to the assigned channels, if the Handover Reference information is included within the PS HANDOVER COMMAND message the mobile station shall send four times the PS HANDOVER ACCESS message. + +The mobile station activates the channels in sending and receiving mode. The MS may activate the channels in downlink while sending access bursts. + +The timing advance value to be used with the new cell is: + +- either the value contained in the PS HANDOVER COMMAND message if the timing advance information is included; or +- the default value for pre-synchronized handover as defined in 3GPP TS 45.010, if the timing advance information element is not included in the PS HANDOVER COMMAND message. + +##### 8.10.4.4.4 Non synchronized cell case + +After having switched to the assigned channels, the mobile station shall send four times the PS HANDOVER ACCESS message. The mobile station shall start timer T3216 at the start point of the timeslot in which the PS HANDOVER ACCESS message is sent the first time on the PACCH. + +The mobile station then activates the channels in receiving mode. + +Upon reception of the PS HANDOVER ACCESS message containing the expected Handover Reference value, once the network has the RF characteristics that are necessary, it sends a PACKET PHYSICAL INFORMATION message to the mobile station on the PACCH. + +When the mobile station receives a PACKET PHYSICAL INFORMATION message, it stops timer T3216, stops sending access bursts and activates the channels in sending and receiving mode. + +#### 8.10.4.5 A/Gb to GAN PS Handover + +Upon successfully performing a GAN registration (see 3GPP TS 43.129 [43]), a mobile station in packet transfer mode may trigger a PS handover to a GAN cell by sending a PACKET CELL CHANGE NOTIFICATION message (see sub-clause 8.8.3). The mobile station may send the PACKET CELL CHANGE NOTIFICATION message either at the first + +possible transmission opportunity following GAN registration if GAN mode is preferred or when the GERAN cell becomes sufficiently degraded if GERAN/UTRAN mode is preferred. If the network and the mobile station support PS handover to *GAN mode*, the network may initiate the PS handover procedure. The mobile station shall then proceed as described in sub-clause 8.10.4.1 for the case of *A/Gb mode* to *A/Gb mode* PS handover except for the following: + +- Since the mobile station provides an ARFCN and BSIC corresponding to a GAN cell within the PACKET CELL CHANGE NOTIFICATION message it does not expect a valid minimum set of PSI or SI messages prior to receiving a PS HANDOVER COMMAND message directing it to a GAN cell. +- Upon receiving a PS HANDOVER COMMAND message the MS determines that PS handover to a GAN cell has been ordered if the ARFCN and BSIC included within the message matches the corresponding values it included within the PACKET CELL CHANGE NOTIFICATION message. +- After successful PS handover to the GAN cell (see 3GPP TS 44.318 [42]) the mobile station switches to GAN mode and considers all TBFs that were ongoing in the old cell as implicitly released. + +#### 8.10.4.6 GAN to A/Gb PS Handover + +Upon receiving a GA-PSR HANDOVER COMMAND message for PS handover from *GAN mode* to *A/Gb mode*, a mobile station that supports GAN PS handover shall act on the message as described in 3GPP TS 44.318 [42] prior to switching to the new cell. After switching to the new cell the mobile station shall proceed as described in sub-clause 8.10.4.1 for the case of *A/Gb mode* to *A/Gb mode* PS handover except for the following: + +- None of the actions corresponding to TBFs in the old cell are applicable. +- Upon successful completion of the PS handover procedure the mobile station shall consider the GA-PSR Transport Channel used in the old cell as implicitly released. +- The mobile station shall always establish a new RLC entity for each TBF allocated by the PS HANDOVER COMMAND message (i.e. regardless if an intra-SGSN or an inter-SGSN PS handover was performed). + +### 8.10.5 Abnormal Cases + +#### 8.10.5.1 MS Behaviour for A/Gb to A/Gb PS Handover + +A mobile station operating in *A/Gb mode* shall consider the PS handover to *A/Gb mode* to have failed if the PS HANDOVER COMMAND message: + +- contains an invalid Frequency Parameters information element; or +- contains specifying frequencies that are not all in one frequency band; or +- contains a Frequency Parameters information element specifying a frequency that is in a frequency band not supported by the mobile station; or +- does not properly specify an uplink or downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002); or +- does not provide resources for at least one uplink TBF in the new cell; or +- would result in one or more TBFs with FANR activated and one or more TBFs with FANR not activated for that mobile station; or +- includes an inconsistent RTTI configuration assignment as per the conditions specified in sub-clause 7.1.3.6; or +- contains any other failure. + +A mobile station operating in *A/Gb mode* shall consider the PS handover to *A/Gb mode* to have failed for the following reasons: + +- In the synchronized cell case (see sub-clause 8.10.4.4.1), if the timing advance with the new cell calculated by the mobile station is out of range, i.e. is bigger than the maximum timing advance that can be coded as specified in 3GPP TS 44.004, and if the new cell does not accept out of range timing advance as indicated in the PS HANDOVER COMMAND message. + +- If it has not stored a valid minimum set of the following of PSI or SI messages (provided via PACKET NEIGHBOUR CELL DATA messages, see sub-clause 8.8.1) required for mobile station to operate in the new cell: PSI1, a consistent set of PSI2 messages and PSI14 (if PBCCH allocated in the new cell) or SI3, SI1 (if present in the new cell) and SI13 messages (if PBCCH not allocated in the new cell). +- Timer T3218 expires while in the new cell. +- Timer T3216 expires while in the new cell. + +A mobile station operating in *A/Gb mode* when a PS handover to *A/Gb mode* fails shall proceed as follows: + +- If timer T3218 expired it shall return to the cell on which the PS HANDOVER COMMAND message was received. +- If timer T3216 expired it shall return to the cell on which the PS HANDOVER COMMAND message was received. +- Send a PACKET CELL CHANGE FAILURE message with the cause code set to "No response on target cell" if timer T3218 or T3216 expired, otherwise "PS Handover failure-others". The message shall be sent on PACCH. +- The transmission of a PACKET CELL CHANGE FAILURE message terminates the PS handover procedure in the mobile station and after the transmission of this message the mobile station is therefore allowed to request the establishment of additional uplink TBFs. +- After terminating the PS handover procedure the mobile station shall resume all uplink and downlink TBFs that were ongoing in the old cell prior to receiving the PS HANDOVER COMMAND message. Timers T3180 (uplink TBFs) and T3190 (downlink TBFs) corresponding to these TBFs shall be re-started. +- For each TBF that is resumed the corresponding RLC state machine shall reflect its state when the last RLC data block was transmitted for that TBF in the old cell (uplink TBFs) and the last RLC data block was received for that TBF in the old cell (downlink TBFs). + +#### 8.10.5.2 MS Behaviour for A/Gb to Iu/E-UTRAN PS Handover + +A mobile station operating in *A/Gb mode* shall consider PS handover to *Iu mode* or E-UTRAN to have failed if it is unable to perform PS handover for any reason based on the content of the received PS HANDOVER COMMAND message. + +A mobile station operating in *A/Gb mode* when a PS handover to *Iu mode* or E-UTRAN fails shall proceed as described above for the case where PS handover from *A/Gb mode* to *A/Gb mode* fails except that T3216 shall never be running. + +#### 8.10.5.3 MS Behaviour for Iu/E-UTRAN to A/Gb PS Handover + +A mobile station operating in *Iu mode* or E-UTRAN shall consider PS handover to *A/Gb mode* to have failed for the following reasons: + +- It is unable to perform PS handover for any reason based on the content of the received Handover from UTRAN Command or *MobilityFromEUTRACommand* message. +- The Handover from UTRAN Command or *MobilityFromEUTRACommand* message does not contain the minimum set of PSI or SI messages required for mobile station to operate in the new cell (see sub-clause 8.10.2). +- Timer T3218 expires while in the new cell. +- Timer T3216 expires while in the new cell. +- The PS HANDOVER COMMAND message carried within the Handover from UTRAN Command or *MobilityFromEUTRACommand* message does not provide resources for at least one uplink TBF in the new cell. +- The PS HANDOVER COMMAND message would result in one or more TBFs with FANR activated and one or more TBFs with FANR not activated for that mobile station. +- The PS HANDOVER COMMAND message includes an inconsistent RTTI configuration assignment as per the conditions specified in sub-clause 7.1.3.6. + +A mobile station operating in *Iu mode* when a PS handover to *A/Gb mode* fails shall return to the cell it was in prior to receiving the Handover from UTRAN Command message (if T3216 or T3218 expired) and proceed as described in 3GPP TS 25.331. + +A mobile station operating in E-UTRAN when a PS handover to *A/Gb mode* fails shall return to the cell it was in prior to receiving the *MobilityFromEUTRACommand* message (if T3216 or T3218 expired) and proceed as described in 3GPP TS 36.331. + +#### 8.10.5.4 BSS Behaviour for PS Handover from A/Gb + +The source BSS shall terminate the PS handover procedure if any of the following events occur: + +- All TBFs allocated to the mobile station in the old cell are released at any point prior to sending the PS HANDOVER COMMAND message to the mobile station. +- The source BSS receives a PACKET CELL CHANGE FAILURE message or any other RLC block from the mobile station after sending the final segment of the PS HANDOVER COMMAND message, if the network does not request acknowledgement of receipt of that segment (i.e. does not include in any segment a valid RRBP field requiring the mobile station to send a PACKET CONTROL ACKNOWLEDGEMENT message), or after the receipt of a PACKET CONTROL ACKNOWLEDGEMENT message indicating that the mobile station has received the final segment of the PS HANDOVER COMMAND message. + +If the PS handover procedure is terminated for either of the above reasons, the (source) BSS shall resume all uplink and downlink TBFs that were ongoing in the old cell for that MS prior to sending the PS HANDOVER COMMAND message. For normal PS Handover the source BSS shall then indicate the PS handover failure to the SGSN. For optimized PS Handover the source BSS shall then release all resources associated with the new TBFs. + +For each TBF that is resumed the corresponding RLC state machine shall reflect its state when the last RLC data block was transmitted for that TBF in the old cell (downlink TBFs) and the last RLC data block was received for that TBF in the old cell (uplink TBFs). + +For both the normal and optimized cases of PS Handover, after sending the PS HANDOVER COMMAND to the MS, the source BSS shall continue to schedule transmission opportunities for the mobile station for a period of time sufficiently long to allow the mobile station to transmit a PACKET CELL CHANGE FAILURE message (should a PS handover failure occur). + +For normal PS Handover, if the source BSS does not receive any RLC/MAC block from the MS and does not receive (a) DELETE-BSS-PFC PDU(s) from the SGSN for all ongoing PFCs during this time period, the source BSS shall consider radio contact with the MS to be lost and shall release all resources related to the MS and initiate the PS Handover Cancel procedure (see 3GPP TS 48.018), by sending a PS-HANDOVER-CANCEL PDU to the SGSN with cause "Radio contact lost with MS". + +For optimized PS Handover, if the BSS does not receive any RLC/MAC block from the MS on any of the old TBFs and does not receive an uplink RLC data block from the MS on any of the new TBFs during this time period, the BSS shall consider the MS to be lost and therefore release all resources associated with the new TBFs and old TBFs. + +#### 8.10.5.5 BSS Behaviour for PS Handover to A/Gb + +If the (target) BSS expects but does not receive any PS HANDOVER ACCESS messages from the mobile station it considers the PS handover procedure to have failed and shall release all TBFs allocated to the mobile station in the new cell. + +If the (target) BSS expects but does not receive the correct Handover Reference value from the mobile station it considers the PS handover procedure to have failed and shall release all TBFs allocated to the mobile station in the new cell. + +#### 8.10.5.6 MS Behaviour for A/Gb to GAN PS Handover + +Upon receiving a PS HANDOVER COMMAND message in the source cell, if connectivity has been lost on the corresponding GA-PSR Transport Channel the MS shall discard the PS HANDOVER COMMAND message and send the source BSS a PACKET CELL CHANGE FAILURE message with the cause code set to "PS Handover failure". + +### 8.10.5.7 MS Behaviour for GAN to A/Gb PS Handover + +See 3GPP 44.318 [42]. + +--- + +## 9 Radio Link Control (RLC) procedures in packet transfer mode + +### 9.0 General + +The RLC function is responsible for: + +- Interface primitives allowing the transfer of upper layer PDUs between the upper layer and the MAC function; +- Segmentation of upper layer PDUs into RLC data blocks and re-assembly of RLC data blocks into upper layer PDUs; +- Segmentation of RLC/MAC control messages into RLC/MAC control blocks and re-assembly of RLC/MAC control messages from RLC/MAC control blocks; +- Backward Error Correction (BEC) procedures enabling the selective retransmission of RLC data blocks. + +In this clause Packet Ack/Nack refers to any of the following messages or field: + +- PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3, EGPRS PACKET DOWNLINK ACK/NACK DLMC, MBMS DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC; +- PACKET UPLINK ACK/NACK, EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION; +- PAN. + +Additionally the following definitions apply: + +- Sequence Number Space (SNS): + - 128 in GPRS, + - 2048 in EGPRS, + - 2048 or 8192 in DLMC configuration (see sub-clause 5.13), + - 32 in EC-GSM-IoT; +- Window Size (WS): + - GPRS: 64 + - EGPRS: 64 to 1024 + - DLMC configuration (EGPRS): determined by the buffer size supported by a mobile station (see Table 9.1.9.3.2) + - EC-GSM-IoT: 16. + +A mobile station that supports multiple TBF procedures can operate multiple RLC entities simultaneously each one with its' own set of RLC parameters (e.g. sequence number; receive and transmit windows etc.). + +If a mobile station in a DLMC configuration using a SNS of 8192 is reconfigured so that it leaves DLMC configuration while the downlink TBF remains assigned, it shall continue using a SNS of 8192. A mobile station that supports DLMC configuration and has a downlink TBF with a single downlink carrier assigned (i.e. it is not in a DLMC configuration) shall immediately begin using a SNS of 8192 if the maximum number of downlink timeslots it supports (see 3GPP TS 24.008) is greater than 20 and either of the following occurs: + +- It receives an assignment message that causes it to enter DLMC configuration, the assignment message indicates an SNS of 8192 shall be used, and it is not already using a SNS of 8192. +- It experiences PS Handover to a DLMC configuration and the PS HANDOVER COMMAND message indicates an SNS of 8192 shall be used. + +Only RLC acknowledged mode is supported in EC TBF mode. + +## 9.1 Procedures and parameters for peer-to-peer operation + +A TBF is comprised of two peer entities, which are the RLC endpoints. In case of EMST, a TBF is comprised of one, two or three pairs of peer RLC entities, which are the RLC endpoints. Each RLC endpoint has a receiver that receives RLC/MAC blocks. Each RLC endpoint also has a transmitter that transmits RLC/MAC blocks. + +An MBMS bearer is comprised of one transmitting RLC endpoint at the network side and several receiving RLC endpoints, one for each mobile station involved in the p-t-m transmission. The transmitting RLC endpoint transmits RLC/MAC data and control blocks and may receive only RLC/MAC control blocks. Each receiving RLC endpoint receives RLC/MAC data and control blocks and may transmit only RLC/MAC control blocks, upon polling. An MBMS bearer operates in RLC non-persistent mode (see also sub-clause 9.3.4). + +Each endpoint's receiver has a receive window of size WS (see sub-clause 9.1.9). + +In RLC acknowledged mode, the receive window is defined by the receive window state variable V(Q) in the following inequality: $[ V(Q) \leq BSN < V(Q) + WS ]$ modulo SNS (for the method of interpreting inequalities in this format refer to sub-clause 9.1.8). All BSNs which meet that criteria are valid within the receive window. + +In RLC unacknowledged mode, all values of BSN are within the receive window. + +In RLC non-persistent mode, the receive window is determined after recalculating the receive state variable V(R) (as described in sub-clause 9.1.5) and the corresponding receive window state variable V(Q) (as described in sub-clause 9.1.6.4). All BSNs which meet the following inequality $[ V(Q) \leq BSN \leq V(R) ]$ modulo SNS are valid within the receive window. + +An RLC data block is considered received, when it is received in a layer 1 frame with consistent parity bits (in EGPRS TBF mode: header and relevant data parity bits) and correctly addresses the receiving RLC endpoint. + +Each endpoint's transmitter has a transmit window of size WS. In RLC acknowledged mode and in RLC non-persistent mode, the transmit window is defined by the send state variable V(S) in the following inequality: $[ V(A) \leq BSN < V(S) ]$ modulo SNS, where $[ V(S) - V(A) ]$ modulo SNS $\leq WS$ . All BSNs which meet that criteria are valid within the transmit window. In RLC unacknowledged mode, all values of BSN are within the transmit window. + +In RLC non-persistent mode, if the NPM Transfer Time limitation is used then the network shall not change the NPM Transfer Time value. The mobile station shall ignore any NPM Transfer Time different from what is currently being used. If EMSR is enabled for an RLC entity operating in RLC Non-persistent mode then an independent NPM Transfer Time limitation may be assigned for each PFC assigned a unique TFI. + +### 9.1.1 Send state variable V(S) + +Each RLC endpoint transmitter shall have an associated send state variable V(S). V(S) denotes the sequence number of the next in-sequence RLC data block to be transmitted. V(S) can take on the value 0 through SNS - 1. V(S) shall be set to the value 0 at the beginning of each TBF in which the RLC endpoint is the transmitter. The value of V(S) shall be incremented by 1 after transmission of the RLC data block with BSN = V(S). In RLC acknowledged mode, V(S) shall not exceed V(A) modulo SNS by more than the maximum allowed number of outstanding RLC data blocks WS. In RLC non-persistent mode, V(S) may be incremented independently on the value of V(A). When EMSR is enabled, a single send state variable V(S) is maintained regardless of how many PFCs share a given RLC entity. + +#### 9.1.1a Control send state variable V(CS) + +The network RLC endpoint transmitter shall have one instance of an associated control send state variable V(CS) for each parallel control transaction identified by the RTI field of the RLC/MAC control block header. V(CS) denotes the sequence number of the next in-sequence RLC/MAC control block to be transmitted for the control transaction. V(CS) can take on the values 0 or 1 when RLC/MAC control message segmentation into two RLC/MAC control blocks is used, and the values 0 to 8 when extended RLC/MAC control message segmentation is used (see sub-clause 9.1.12a). + +V(CS) shall be set to the value 0 prior to the transmission of each RLC/MAC control block that contains the first octet of an RLC/MAC control message of the control transaction and the value of V(CS) shall be set to 1 after the transmission of the RLC/MAC control block with RBSN = 0. The value of V(CS) shall then be incremented by 1, when extended RLC/MAC control message segmentation is used, after the transmission of the next in-sequence RLC/MAC control block and so on. + +## 9.1.2 Acknowledge state variable V(A) + +In RLC acknowledged mode, each RLC endpoint transmitter shall have an associated acknowledge state variable V(A). V(A) contains the BSN value of the oldest RLC data block that has not been positively acknowledged by its peer. V(A) can take on the values 0 through SNS - 1. V(A) shall be set to the value 0 at the beginning of each TBF in which the RLC endpoint is the transmitter. The value of V(A) shall be updated from the values received from its peer in the received block bitmap (RBB) of the PACKET UPLINK ACK/NACK message, the EC PACKET UPLINK ACK/NACK message, the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, the EGPRS PACKET DOWNLINK ACK/NACK message, the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message, the EGPRS PACKET DOWNLINK ACK/NACK DLMC message or the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message (see sub-clause 9.1.8) + +Furthermore, $[ V(S) - V(A) ] \bmod \text{SNS} \leq \text{WS}$ . + +In RLC non-persistent mode, each RLC endpoint transmitter shall have an associated acknowledge state variable V(A). V(A) contains the BSN value of the oldest RLC data block that has not yet been positively acknowledged by the corresponding peer or peers and whose BSN satisfies the inequality $[ V(S) - \text{BSN} ] \bmod \text{SNS} \leq \text{WS}$ . V(A) can take on the values 0 through SNS - 1. V(A) shall be set to the value 0 at the beginning of each MBMS bearer or EGPRS TBF for which the RLC endpoint is the transmitter. + +- When RLC non-persistent mode is used for an MBMS bearer the value of V(A) shall be updated from the values received from its peers in the received block bitmap (RBB) of the MBMS DOWNLINK ACK/NACK message (see sub-clause 9.1.8). +- When RLC non-persistent mode is used for an EGPRS TBF the value of V(A) shall be updated from the values received from its peer in the PACKET UPLINK ACK/NACK message, the EGPRS PACKET DOWNLINK ACK/NACK message, the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message, the EGPRS PACKET DOWNLINK ACK/NACK DLMC message or the PAN field. +- V(A) shall be set to BSN', where BSN' is the BSN value of the oldest RLC data block not yet positively acknowledged by the corresponding peer or peers which meets the condition $[ V(S) - \text{BSN}' ] \bmod \text{SNS} \leq \text{WS}$ , or it shall be set to V(S) if all RLC data blocks have been positively acknowledged by the corresponding peer or peers. + +## 9.1.3 Acknowledge state array V(B) + +### 9.1.3.1 Acknowledge state array V(B) for GPRS TBF Mode + +In RLC acknowledged mode, each RLC endpoint transmitter shall have an associated acknowledge state array (V(B)). V(B) is an array of SNS elements indicating the acknowledgement status of WS previous RLC data blocks. The array is indexed relative to the acknowledge state variable V(A) modulo SNS. The values of V(B) shall be updated from the values received from its peer in the received block bitmap (RBB) of the Packet Ack/Nack message (see sub-clause 9.1.8) + +The transmitter shall transmit the oldest RLC data block whose corresponding element in V(B) indexed relative to V(A) has the value NACKED. As each RLC data block is transmitted the corresponding element in V(B) is set to the value PENDING\_ACK. + +If $[ V(S) < V(A) + \text{WS} ] \bmod \text{SNS}$ and no RLC data blocks have a corresponding element in V(B) with the value NACKED, the RLC data block with BSN = V(S) shall be transmitted and the corresponding element in V(B) shall be set to the value PENDING\_ACK. If there are no further RLC data blocks available for transmission (i.e. the RLC data block with BSN= V(S) does not exist), the sending side shall transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, then the next oldest block whose corresponding element in V(B) has the value PENDING\_ACK, etc. If all RLC data blocks whose corresponding element in V(B) has the value PENDING\_ACK have been transmitted once, the process shall be repeated beginning with the oldest RLC data block. + +If $V(S) = V(A) + WS$ modulo SNS (i.e. the transmit window is stalled), the sending side shall transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, then the next oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, etc. If all RLC data blocks whose corresponding element in V(B) has the value PENDING\_ACK has been transmitted once, the process shall be repeated beginning with the oldest RLC data block. This process of transmitting the oldest RLC data blocks whose value in V(B) has the value PENDING\_ACK shall continue, as long as equation $[V(S)=V(A)+WS]$ modulo SNS holds. + +When an element in V(B) falls outside of the active transmit window, i.e. $[V(A) \leq BSN < V(S)]$ modulo SNS, the element shall be set to the value INVALID. + +In the extended uplink TBF mode, if $V(S) = V(A)$ and there is no RLC data block with $BSN = V(S)$ available, the mobile station shall stop sending RLC data blocks. The mobile station shall continue sending RLC data blocks when a RLC data block with $BSN = V(S)$ is available. + +### 9.1.3.2 Acknowledge State Array V(B) for EGPRS TBF Mode + +#### 9.1.3.2.1 EGPRS TBF running in RLC acknowledged mode + +In RLC acknowledged mode, each RLC endpoint transmitter shall have an associated acknowledge state array (V(B)). V(B) is an array of SNS elements indicating the acknowledgement status of WS previous RLC data blocks. The array is indexed relative to the acknowledge state variable V(A) modulo SNS. The values of V(B) shall be updated from the values received from its peer in the reported bitmap (RB) of the Packet Ack/Nack message (see sub-clause 9.1.8). If a compressed reported bitmap is received, decompression shall be first applied according to sub-clause 9.1.10. + +The transmitter shall transmit the oldest RLC data block whose corresponding element in V(B) indexed relative to V(A) has the value NACKED. As each RLC data block is transmitted the corresponding element in V(B) is set to the value PENDING\_ACK. If the RLC data block to be transmitted is split over two radio blocks, both radio blocks shall be transmitted. As an exception, if the transmitter supports DTR, $[V(S) < V(A) + WS]$ modulo SNS and the RLC data block with $BSN = V(S)$ is available, the transmitter may transmit the RLC data block with $BSN = V(S)$ instead of the oldest RLC data block whose corresponding element in V(B) has the value NACKED. + +NOTE: This exception should only be used to avoid a mobile station entering DTR mode or the network believing that a mobile station may have entered DTR mode (see sub-clause 8.1.8.2) when the transmitter has received new data from the upper layers. + +If $[V(S) < V(A) + WS]$ modulo SNS and no RLC data blocks have a corresponding element in V(B) with the value NACKED, the RLC data block with $BSN = V(S)$ shall be transmitted and the corresponding element in V(B) shall be set to the value PENDING\_ACK. If the transmitter is the mobile station, the pre-emptive transmission bit is set to '1' in the PACKET UPLINK ACK/NACK message and there are no further RLC data blocks available for transmission (i.e. the RLC data block with $BSN = V(S)$ does not exist), the sending side shall retransmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, then the next oldest block whose corresponding element in V(B) has the value PENDING\_ACK, etc. If in this case there are no RLC data blocks whose corresponding element in V(B) has the value PENDING\_ACK and either the uplink TBF is not operated in extended uplink TBF mode or the uplink TBF is operated in extended uplink TBF mode but the mobile station shall not refrain from sending an RLC/MAC block (i.e. EXT\_UTBF\_NODATA is set to '0'), the sending side shall retransmit the oldest RLC data block whose corresponding element in V(B) has the value TENTATIVE\_ACK, then the next oldest block whose corresponding element in V(B) has the value TENTATIVE\_ACK, etc. This entire procedure shall be repeated, starting with the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK or has the value TENTATIVE\_ACK if no element has the value PENDING\_ACK, for as long as the applicable conditions for pre-emptive retransmission are true. + +If $[V(S) = V(A) + WS]$ modulo SNS (i.e. the transmit window is stalled), the sending side shall transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, then the next oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, etc. If in this case there are no RLC data blocks whose corresponding element in V(B) has the value PENDING\_ACK and either the uplink TBF is not operated in extended uplink TBF mode or the uplink TBF is operated in extended uplink TBF mode but the mobile station shall not refrain from sending an RLC/MAC block (i.e. EXT\_UTBF\_NODATA is set to '0'), the sending side shall retransmit the oldest RLC data block whose corresponding element in V(B) has the value TENTATIVE\_ACK, then the next oldest block whose corresponding element in V(B) has the value TENTATIVE\_ACK, etc. This process of retransmitting RLC data blocks whose value in V(B) has the value PENDING\_ACK (or TENTATIVE\_ACK) shall be repeated, starting with the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK or has the value TENTATIVE\_ACK if no element of V(B) has the value PENDING\_ACK, as long as equation $[V(S)=V(A)+WS]$ modulo SNS holds. If the transmitter is the mobile station and the pre-emptive transmission bit is set to '0' in the + +PACKET UPLINK ACK/NACK message the transmitter shall not retransmit RLC data blocks whose corresponding element in V(B) has the value PENDING\_ACK or TENTATIVE\_ACK. When a PACKET UPLINK ACK/NACK message or a PAN field is received the mobile station shall retransmit the RLC blocks which are set to NACKED in V(B) and new RLC data blocks as far as the transmit window (if advanced) allows. However if the RLC data block is the last in the TBF it shall be retransmitted even if its state is PENDING\_ACK or TENTATIVE\_ACK. The default for the mobile side is that the transmitter shall use pre-emptive retransmission. If the transmitter is on the network side this process (pre-emptive retransmission) of retransmitting the oldest RLC data blocks whose value in V(B) has the value PENDING\_ACK or TENTATIVE\_ACK is optional. + +NOTE: If the Mobile Station only has RLC data blocks whose value in V(B) has the value PENDING\_ACK or TENTATIVE\_ACK and the pre-emptive transmission bit is set to '0', the rules defined in sub-clause 8.1.1 apply (i.e. PACKET UPLINK DUMMY CONTROL BLOCK messages are sent). + +If the mobile station has been polled for a PAN, and the data blocks specified for transmission according to the rules in this sub-clause all have corresponding elements in V(B) whose value is TENTATIVE\_ACK then no RLC data block shall be transmitted (see sub-clause 8.1.1.). + +When an element in V(B) falls outside of the active transmit window, i.e. $[ V(A) \leq BSN < V(S) ]$ modulo SNS, the element shall be set to the value INVALID. + +In the extended uplink TBF mode, if $V(S) = V(A)$ and there is no RLC data block with $BSN = V(S)$ available, the mobile station shall stop sending RLC data blocks. The mobile station shall continue sending RLC data blocks when a RLC data block with $BSN = V(S)$ is available. + +When Enhanced Flexible Timeslot Assignment, EFTA, is used, and the applicable conditions for pre-emptive retransmission are true, the mobile station shall not prioritize uplink radio block transmission over attempting to read downlink radio blocks. + +#### 9.1.3.2.2 EGPRS TBF running in RLC non-persistent mode + +In RLC non-persistent mode, each RLC endpoint transmitter shall have an associated acknowledge state array (V(B)). V(B) is an array of SNS elements indicating the acknowledgement status of WS previous RLC data blocks. The array is indexed relative to the acknowledge state variable V(A) modulo SNS. The values of V(B) shall be updated from the values received from its peer in the reported bitmap (RB) of the Packet Ack/Nack message (see sub-clause 9.1.8). If a compressed reported bitmap is received, decompression shall be first applied according to sub-clause 9.1.10. + +The transmitter may transmit any RLC data block included in V(B), e.g. those whose corresponding element in V(B) indexed relative to V(A) has the value NACKED. As each RLC data block is transmitted the corresponding element in V(B) is set to the value PENDING\_ACK. If an NPM Transfer Time limitation is associated with the TBF, the transmitting RLC endpoint shall start a timer with a value equal to the NPM Transfer Time (see Table 12.45a.1) each time it begins transmitting a new upper layer PDU. If the timer expires, the transmitting RLC endpoint should not (re)transmit any of the RLC data blocks corresponding to that upper layer PDU and not containing data from other LLC PDU(s) whose timer has not yet expired. + +When an element in V(B) falls outside of the active transmit window, i.e. $[ V(A) \leq BSN < V(S) ]$ modulo SNS, the element shall be set to the value INVALID. + +If the RLC data block to be transmitted is split over two radio blocks, both radio blocks shall be transmitted. The selection of the Puncturing Scheme (PS) shall be performed according to sub-clause 9.3.2.1. + +In the extended uplink TBF mode, if $V(S) = V(A)$ and there is no RLC data block with $BSN = V(S)$ available, the mobile station shall stop sending RLC data blocks. The mobile station shall continue sending RLC data blocks when a RLC data block with $BSN = V(S)$ is available. + +#### 9.1.3.3 Acknowledge State Array V(B) for MBMS Bearers + +The RLC endpoint transmitter shall have an associated acknowledge state array (V(B)). V(B) is an array of SNS elements indicating the acknowledgement status of WS previous RLC data blocks. The array is indexed relative to the acknowledge state variable V(A) modulo SNS. + +The values of V(B) shall be updated from the values received from its peers in the reported bitmap (RB) of the MBMS DOWNLINK ACK/NACK message (see sub-clause 9.1.8). If a compressed reported bitmap is received, decompression shall be first applied according to sub-clause 9.1.10. + +The transmitter may retransmit any RLC data block included in V (B), e.g. those whose corresponding element in V (B) indexed relative to V (A) have the value NACKED. As each RLC data block is transmitted the corresponding element in V (B) is set to the value PENDING\_ACK. If an NPM Transfer Time limitation is associated with the MBMS bearer, the transmitting RLC endpoint shall start a timer with a value equal to the NPM Transfer Time (see Table 12.45a.1) each time it begins transmitting a new upper layer PDU. If the timer expires, the transmitting RLC endpoint should not (re)transmit any of the RLC data blocks corresponding to that upper layer PDU and not containing data from other LLC PDU(s) whose timer has not yet expired. + +When an element in V(B) falls outside of the active transmit window, i.e. $[ V(A) \leq BSN < V(S) ]$ modulo SNS, the element shall be set to the value INVALID. + +For an MBMS bearer running in EGPRS TBF mode, if the RLC data block intended for retransmission is split over two radio blocks, both radio blocks shall be transmitted. The selection of the Puncturing Scheme (PS) shall be performed according to sub-clause 9.3.2.1. + +### 9.1.3.4 Acknowledge State Array V(B) for EC TBF Mode + +Each RLC endpoint transmitter shall have an associated acknowledge state array (V(B)). V(B) is an array of SNS elements indicating the acknowledgement status of WS previous RLC data blocks. The array is indexed relative to the acknowledge state variable V(A) modulo SNS. The values of V(B) shall be updated from the values received from its peer in the received block bitmap (RBB) of the Packet Ack/Nack message (see sub-clause 9.1.8.3). + +The transmitter shall transmit the oldest RLC data block whose corresponding element in V(B) indexed relative to V(A) has the value NACKED. As each RLC data block is transmitted the corresponding element in V(B) is set to the value PENDING\_ACK. If the RLC data block to be transmitted is split over two radio blocks, both radio blocks shall be transmitted. + +If $[ V(S) < V(A) + WS ]$ modulo SNS and no RLC data blocks have a corresponding element in V(B) with the value NACKED, the RLC data block with BSN = V(S) shall be transmitted and the corresponding element in V(B) shall be set to the value PENDING\_ACK. If the transmitter is the mobile station that, for a fixed uplink allocation it has received, has no further RLC data blocks available for transmission (i.e. the RLC data block with BSN= V(S) does not exist), the mobile station shall retransmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, then the next oldest block whose corresponding element in V(B) has the value PENDING\_ACK, etc. + +If $[ V(S) = V(A) + WS ]$ modulo SNS (i.e. the transmit window is stalled), the sending side shall transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, then the next oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, etc. + +If the transmitter is on the network side the process of pre-emptive retransmission, i.e. retransmitting the oldest RLC data blocks whose value in V(B) has the value PENDING\_ACK, is optional. + +When an element in V(B) falls outside of the active transmit window, i.e. $[ V(A) \leq BSN < V(S) ]$ modulo SNS, the element shall be set to the value INVALID. + +## 9.1.4 Block sequence number BSN + +### 9.1.4.1 Block sequence number BSN for GPRS TBF + +Each RLC data block contains a block sequence number (BSN) field that is 7 bits in length. At the time that an in-sequence RLC data block is designated for transmission, the value of BSN is set equal to the value of the send state variable V(S). + +### 9.1.4.2 Block sequence number BSN for EGPRS TBF + +Each RLC data block contains a block sequence number (BSN) field that is 11 bits in length or, for the case of a DLMC configuration where a SNS of 8192 is used (see sub-clause 5.13), 13 bits long.. At the time that an in-sequence RLC data block is designated for transmission, the value of BSN is set equal to the value of the send state variable V(S). + +### 9.1.4.3 Block sequence number BSN for EC TBF + +Each RLC data block contains a block sequence number (BSN) field that is 5 bits in length. At the time that an in-sequence RLC data block is designated for transmission, the value of BSN is set equal to the value of the send state variable V(S). + +## 9.1.4a Reduced Block Sequence Number RBSN + +Each downlink RLC/MAC control block contains a Reduced Block Sequence Number (RBSN) bit. At the time that an in-sequence RLC/MAC control block is designated for transmission, the value of RBSN is set equal to the value of the control send state variable V(CS), except when extended RLC/MAC control message segmentation is used, in which case the value of RBSN is set equal to '0' for the first RLC/MAC control block, and to '1' for the second RLC/MAC control block onwards. + +## 9.1.4b Reduced Block Sequence Number extension RBSNe + +When extended RLC/MAC control message segmentation is used, the second to the ninth RLC/MAC control blocks shall contain a Reduced Block Sequence Number extension (RBSNe) field. The first RLC/MAC control block shall not contain a RBSNe field (see sub-clause 10.4.12b). At the time that an in-sequence RLC/MAC control block is designated for transmission, the value of RBSNe is set equal to the value of the control send state variable V(CS) minus 1. + +## 9.1.5 Receive state variable V(R) + +Each RLC endpoint receiver shall have an associated receive state variable V(R). The receive state variable denotes the BSN which has a value one higher than the highest BSN of those corresponding to the RLC data blocks so far received (modulo SNS). V(R) shall be set to the value '0' at the beginning of each TBF in which the RLC endpoint is the receiver. V(R) can take on the value 0 through SNS - 1. When EMSR is enabled, a single receive state variable V(R) is maintained regardless of how many PFCs share a given RLC entity. + +In RLC acknowledged mode, V(R) shall be set to $[ \text{BSN}' + 1 ]$ modulo SNS, where BSN' is the highest BSN of those corresponding to received RLC data blocks, provided $[ V(R) \leq \text{BSN}' < V(Q) + \text{WS} ]$ modulo SNS. + +In RLC unacknowledged mode, V(R) shall be set to $[ \text{BSN}' + 1 ]$ modulo SNS, where BSN' is the highest BSN of those corresponding to received RLC data blocks. + +In RLC non-persistent mode, V(R) of each receiving RLC endpoint shall be set to $[ \text{BSN}' + 1 ]$ modulo SNS, where BSN' is the highest BSN of those corresponding to received RLC data blocks, provided $[ V(R) \leq \text{BSN}' < V(R) + \text{SNS} - \text{WS} ]$ modulo SNS. + +## 9.1.6 Receive window state variable V(Q) + +### 9.1.6.1 General + +Each RLC endpoint receiver shall have an associated receive window state variable V(Q). The receive window state variable denotes the lowest BSN not yet received (modulo SNS), therefore representing the start of the receive window. V(Q) shall be set to the value 0 at the beginning of each TBF in which the RLC endpoint is the receiver. The receive window state variable can take on the value 0 through SNS - 1. + +### 9.1.6.2 RLC acknowledged mode + +In RLC acknowledged mode, the value of V(Q) shall be updated when the RLC receiver receives the RLC data block whose BSN is equal to V(Q). The value of V(Q) shall then be set to the BSN value of the next RLC data block in the receive window (modulo SNS) that has not yet been received, or it shall be set to V(R) if all RLC data blocks in the receive window have been received. + +### 9.1.6.3 RLC unacknowledged mode + +In RLC unacknowledged mode, if $[ V(R) - V(Q) ]$ modulo SNS > WS after updating V(R), then V(Q) is set to $[ V(R) - \text{WS} ]$ modulo SNS. + +### 9.1.6.4 RLC non-persistent mode + +In RLC non-persistent mode, V(Q) of each receiving RLC endpoint shall be set to V(R) if all RLC data blocks in the receive window have been received or to BSN', where BSN' is the lowest BSN of those corresponding to RLC data blocks not yet received which: + +- meets the condition $[ V(R) - \text{BSN}' ]$ modulo SNS $\leq \text{WS}$ and +- it is still expected by the receiving RLC endpoint. + +If an NPM Transfer Time limitation is associated with the corresponding MBMS bearer/EGPRS TBF, the receiving RLC endpoint shall start a timer with a value equal to the NPM Transfer Time (see Table 12. 45a.1) for an RLC data block with BSN equal to BSN' if at the end of a radio block period that data block is first detected as missing i.e. when both of the following conditions are first met for BSN': + +- the RLC data block with sequence number BSN' has not been received, and +- an RLC/MAC header containing a BSN equal to or higher than BSN' (modulo SNS) has been received. + +The timer shall be started at most once for any given RLC data block. The timer shall not be restarted in the event of an out-of-sequence retransmission (i.e. where the endpoint is expecting a retransmission of that block but receives a retransmission of a block with higher BSN). The timer shall be stopped on reception of the RLC data block. + +RLC data blocks are considered not expected if they have been received or (if an NPM Transfer Time limitation is associated with the corresponding MBMS bearer/EGPRS TBF) the corresponding timer has been stopped or has expired. + +## 9.1.7 Receive state array V(N) + +### 9.1.7.1 Receive state array V(N) in GPRS TBF + +Each RLC endpoint receiver shall have an associated receive state array V(N). V(N) is an array of SNS elements indicating the receive status of WS previous RLC data blocks. The array is indexed relative to the receive state variable V(R) modulo SNS. When an RLC data block is received with BSN within the receive window, V(R) is treated according to sub-clause 9.1.5 and the element in V(N) corresponding to the received RLC data block is set to the value RECEIVED. + +An element in V(N), corresponding to a BSN such that $[ V(R) \leq BSN < V(R) - WS ]$ modulo SNS, shall be set to the value INVALID. + +### 9.1.7.2 Receive state array V(N) in EGPRS TBF + +Each RLC endpoint receiver shall have an associated receive state array V(N). V(N) is an array of SNS elements indicating the receive status of WS RLC data blocks that are supposed to follow the block BSN=V(Q)-1. The array is indexed relative to the receive window state variable V(Q) modulo SNS. When an RLC data block is received with BSN within the receive window, the corresponding element in V(N) is set to the value RECEIVED. + +If the RLC data block is split over two radio blocks, the element shall be set to the value RECEIVED if and only if both radio blocks have been received. + +The elements in V(N) shall be set to the value INVALID at the beginning of each TBF. During the TBF, an element in V(N) that falls outside the receive window, shall be set to the value INVALID. + +### 9.1.7.3 Receive state array V(N) in TBF with FANR activated + +Each RLC endpoint receiver shall have an associated receive state array V(N). V(N) is an array of SNS elements indicating the receive status of RLC data blocks that are supposed to follow the block BSN=V(Q)-1. The array is indexed relative to the receive window state variable V(Q) modulo SNS. When an RLC data block is received with BSN within the receive window, the corresponding element in V(N) shall be set to the value RECEIVED. + +If the RLC data block is split over two radio blocks, the element shall be set to the value RECEIVED if and only if both radio blocks have been received. + +The elements in V(N) shall be set to the value INVALID at the beginning of each TBF. During the TBF, an element in V(N) that falls outside the receive window shall be set to the value INVALID. + +When an EGPRS RLC/MAC header is received, for each BSN' within the receive window included in the header the elements of V(N) shall be updated as follows: + +- if EFTA is not used, or if EFTA is used and the receiving RLC endpoint is in the network, and if the corresponding element in V(N) has the value INVALID, all elements of V(N) with the value INVALID and corresponding to RLC data blocks with BSN satisfying the following inequality $[ V(Q) \leq BSN < BSN' ]$ modulo SNS shall be set to the value UNREPORTED; + +- if the corresponding element in V(N) has the value REPORTED, all elements of V(N) with the value REPORTED and corresponding to RLC data blocks with BSN satisfying the following inequality $[BSN'' \leq BSN < BSN'] \bmod \text{SNS}$ shall be set to the value UNREPORTED, where BSN'' is: +- the BSN of the newest RLC data block for which the corresponding element in V(N) has the value UNREPORTED, if such a block exists, otherwise +- V(Q). + +An element in V(N) whose value is UNREPORTED shall be set to the value REPORTED when the status of the corresponding block is indicated in the RB of a Packet Ack/Nack. This includes the block with $BSN = SSN - 1$ , if the status of that block is implicitly reported in a Packet Ack/Nack. + +If the data field of the RLC/MAC block with sequence number BSN' could not be decoded and the corresponding element in V(N) has the value INVALID or REPORTED, then this element shall also be set to the value UNREPORTED. + +NOTE: The elements in V(N) with the value UNREPORTED correspond to RLC data blocks detected as missing due to e.g. the out-of-sequence reception of a data block. The elements in V(N) with the value REPORTED correspond to missing RLC data blocks whose state was indicated in the RB of a Packet Ack/Nack and have not been detected missing since then. + +#### 9.1.7.4 Receive state array V(N) in EC TBF + +Each RLC endpoint receiver shall have an associated receive state array V(N). V(N) is an array of SNS elements indicating the receive status of WS RLC data blocks that are supposed to follow the block $BSN = V(Q) - 1$ . The array is indexed relative to the receive window state variable V(Q) modulo SNS. When an RLC data block is received with BSN within the receive window, the corresponding element in V(N) is set to the value RECEIVED. + +If the RLC data block is split over two radio blocks, the element shall be set to the value RECEIVED if and only if both radio blocks have been received. + +The elements in V(N) shall be set to the value INVALID at the beginning of each TBF. During the TBF, an element in V(N) that falls outside the receive window, shall be set to the value INVALID. + +#### 9.1.8 Starting sequence number (SSN) and received block bitmap (RBB) + +##### 9.1.8.1 Starting sequence number (SSN) and received block bitmap (RBB) in GPRS TBF + +The Packet Ack/Nack message contains a starting sequence number (SSN) and a received block bitmap (RBB). The Packet Ack/Nack message is sent by the RLC receiver and is received by the RLC transmitter. The SSN and RBB are determined as defined in this sub-clause and transmitted in RLC acknowledged, RLC unacknowledged and RLC non-persistent modes. The SSN and RBB may be ignored by the RLC transmitter in unacknowledged mode. + +The RBB is defined as a binary valued array of WS elements, where the index of each element takes value 0, 1, 2, ..., WS-1 in the given order, respectively. The BSN values specified in the RBB are interpreted by subtracting the bit position in the bitmap from the starting sequence number (SSN) modulo SNS. + +A valid BSN value in the RBB is one that is in the range $[V(A) \leq BSN < V(S)] \bmod \text{SNS}$ . + +These inequalities shall be interpreted in the following way: + +BSN is valid if, and only if, $[BSN - V(A)] \bmod \text{SNS} < [V(S) - V(A)] \bmod \text{SNS}$ . + +At the RLC transmitter: + +- For each bit in the RBB whose corresponding BSN value is within the transmit window, if the bit contains the value '1', the corresponding element in V(B) indexed relative to SSN shall be set to the value ACKED. If the bit contains the value '0', the element in V(B) shall be set to the value NACKED. A bit within the RBB whose corresponding BSN is not within the transmit window, shall be ignored. If the RLC transmitter is on the mobile station side, the bit contains the value '0' and the number of block periods between the end of the block period used for the last transmission of the corresponding RLC data block and the beginning of the block period containing the Packet Uplink Ack/Nack message is less than $(\max(BS\_CV\_MAX, 1) - 1)$ (i.e. the RLC data + +block was recently (re)transmitted and thus can not be validly negatively acknowledged in this particular Packet Uplink Ack/Nack message), the element in V(B) shall not be modified. + +At the RLC receiver: + +- The starting sequence number (SSN) is assigned the value of the receive state variable V(R). The received block bitmap (RBB) is assigned the WS elements whose indices, with incrementing order, correspond to elements in the receive state array V(N) at the receiver whose indices, with decrementing order, range backwards from $[V(R) - 1]$ to $[V(R) - WS]$ (modulo SNS). For each bit in the bitmap, the bit is assigned the value '1' if the corresponding element in V(N) indexed relative to SSN has the value RECEIVED. The bit is assigned the value '0' if the element in V(N) has the value INVALID. +- When polled within a downlink RLC data block, the mobile station shall acknowledge all the RLC data blocks for this RLC instance that have been correctly received up to and including the radio block where the mobile station is polled. +- As an implementation option, the mobile station may also acknowledge as many as possible of the RLC data blocks that are correctly received after the radio block where the mobile station is polled. + +### 9.1.8.2 Starting sequence number (SSN) and received block bitmap (RBB) in EGPRS TBF + +The Packet Ack/Nack message and MBMS DOWNLINK ACK/NACK message contain a starting sequence number (SSN) and a reported bitmap (RB). When the SSN-based encoding is used (see sub-clause 9.1.14.1), the PAN field included in an EGPRS RLC/MAC block for data transfer contains a short SSN (ShortSSN) and a reported bitmap (RB). The Packet Ack/Nack message, MBMS DOWNLINK ACK/NACK message and PAN field are sent by the RLC receiver and are received by the RLC transmitter. The SSN and RB are determined as defined in this sub-clause and transmitted in RLC acknowledged, RLC unacknowledged and RLC non-persistent modes (note the SSN is calculated differently in EGPRS (refer to table 9.1.8.2.2.1) and GPRS (refer to sub-clause 9.1.8.1)). The SSN and RB may be ignored by the RLC transmitter in unacknowledged mode. For a TBF with FANR activated, the ShortSSN (and corresponding SSN) is determined as defined in sub-clause 9.1.8.2.2a and the RB is determined as defined for EGPRS (see sub-clause 9.1.8.2.3). The ShortSSN and RB fields are transmitted in both RLC acknowledged and RLC non-persistent modes. + +The BSN values specified in the RB are interpreted by adding the bit position in the bitmap to the starting sequence number (SSN) modulo SNS (where the first position of the bitmap has index '0'). A valid BSN value in the RB is one that is in the range $[V(A) \leq BSN < V(S)]$ modulo SNS. These inequalities shall be interpreted in the following way: BSN is valid if, and only if, $[BSN - V(A)]$ modulo SNS $< [V(S) - V(A)]$ modulo SNS. + +#### 9.1.8.2.1 Extended Polling + +For EGPRS uplink TBFs, the network may select any composition of the Packet Ack/Nack message to send to the mobile station. In EGPRS downlink TBFs and MBMS bearers running in EGPRS TBF mode, the ES/P field present in every downlink RLC block allows the network to request one of the following Ack/Nack bitmap types: + +- First Partial Bitmap (FPB) segment with $SSN = (V(Q) + 1) \bmod SNS$ (the beginning of the window is V(Q) but FPB starts at $V(Q) + 1$ as the bit in the bitmap corresponding to $V(Q)$ would have value '0') where SSN denotes the Starting Sequence Number. +- Next Partial Bitmap (NPB) segment with $SSN = (PBSN + 1) \bmod SNS$ where PBSN denotes a Partial Bitmap Sequence Number variable stored at the receiver. + +SSN is determined by the receiver as a function of ES/P, V(Q) and PBSN as described in the next sub-clause. The FPB and NPB are specific instances of the *EGPRS Ack/Nack Description Information Element* within the EGPRS PACKET DOWNLINK ACK/NACK message, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or MBMS DOWNLINK ACK/NACK message or specific instances of the *EGPRS Ack/Nack Description DLMC Information Element* within the EGPRS PACKET DOWNLINK ACK/NACK DLMC message. The mobile station shall respond to ES/P field according to table 9.1.8.2.1.1 (non-MBMS) or table 9.1.8.2.1.2 (MBMS). For a mobile station with one or more downlink TBFs using EGPRS2, the mobile station shall send the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message. A mobile station in a DLMC configuration using an SNS of 2048 shall always send the EGPRS PACKET DOWNLINK ACK/NACK DLMC message. Otherwise, the mobile station shall send the EGPRS PACKET DOWNLINK ACK/NACK message or the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message. + +**Table 9.1.8.2.1.1: Format of ES/P field within each EGPRS RLC block (non-MBMS)** + +| ES/P | Feedback Request (Poll) Description | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | Nothing (RRBP field invalid) | +| 01 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLCM message containing FPB (First Partial Bitmap), and if there is enough room left in RLC/MAC block, channel quality report(s) | +| 10 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLCM message containing NPB (Next Partial Bitmap), and if there is enough room left in RLC/MAC block, channel quality report(s) | +| 11 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLCM message containing Channel Quality Report and if there is enough room left in RLC/MAC block, NPB(s) | + +In a downlink dual carrier configuration the MS shall send channel quality reports for both carriers, if there is room in the message. If there is room for only one channel quality report, the MS shall include channel quality measurements for the radio frequency channel on which the poll was received. + +**Table 9.1.8.2.1.2: Format of ES/P field within each EGPRS RLC block (MBMS)** + +| ES/P | Feedback Request (Poll) Description | +|------|--------------------------------------------------------------------------------------| +| 00 | Nothing (RRBP field invalid) | +| 01 | MBMS DOWNLINK ACK/NACK message containing FPB (First Partial Bitmap) | +| 10 | MBMS DOWNLINK ACK/NACK message containing NPB (Next Partial Bitmap) | +| 11 | MBMS DOWNLINK ACK/NACK message containing neighbour cell measurement reports and NPB | + +For EGPRS when FANR is activated or for EGPRS2, the Combined EGPRS Supplementary/Polling field describes the feedback request and specifies a single uplink block in which the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message, a PACCH block or (applicable only if FANR is activated) a radio block containing a PAN field to the network, see table 9.1.8.2.1.3. The single uplink block is defined by a delay relative to the first TDMA frame (N) of the downlink block containing the CES/P value. If ordered to send an EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message, a mobile station with one or more downlink TBFs using EGPRS2 shall send the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message. A mobile station in a DLCM configuration using an SNS of 2048 shall always send the EGPRS PACKET DOWNLINK ACK/NACK DLCM message. Otherwise, the mobile station shall send the EGPRS PACKET DOWNLINK ACK/NACK message. + +**Table 9.1.8.2.1.3: Format of CES/P field within each EGPRS RLC block (EGPRS with FANR activated and EGPRS2)** + +| CES/P | Feedback Request (Poll) Description and Relative Reserved Block Period | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 000 | Nothing | +| 001 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing FPB, and if there is enough room left in RLC/MAC block, channel quality report(s) within the radio period (N+8 or N+9) mod 2715648 in the BTTI configuration or (N+6 or N+7) mod 2715648 in the RTTI configuration | +| 010 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing FPB, and if there is enough room left in RLC/MAC block, channel quality report(s) within the radio period (N+13) mod 2715648 in the BTTI configuration or (N+8 or N+9) mod 2715648 in the RTTI configuration | +| 011 | EGPRS RLC/MAC block for data transfer with a PAN field containing FPB within the radio period (N+8 or N+9) mod 2715648 in the BTTI configuration or (N+6 or N+7) mod 2715648 in the RTTI configuration (NOTE 1) | +| 100 | EGPRS RLC/MAC block for data transfer with a PAN field containing FPB within the radio period (N+13) mod 2715648 in the BTTI configuration or (N+8 or N+9) mod 2715648 in the RTTI configuration (NOTE 1) | +| 101 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing Channel Quality Report(s) and if there is enough room left in RLC/MAC block, NPB within the radio period (N+8 or N+9) mod 2715648 in the BTTI configuration or (N+6 or N+7) mod 2715648 in the RTTI configuration (NOTE 2) | +| 110 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing Channel Quality Report(s) and if there is enough room left in RLC/MAC block, NPB within the radio period (N+13) mod 2715648 in the BTTI configuration or (N+8 or N+9) mod 2715648 in the RTTI configuration (NOTE 2) | +| 111 | EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing NPB, and if there is enough room left in RLC/MAC block, channel quality report(s) within the radio period (N+8 or N+9) mod 2715648 in the BTTI configuration or (N+6 or N+7) mod 2715648 in the RTTI configuration (NOTE 2) | +| NOTE 1: The mobile station shall ignore the poll for PAN in the case when received for a TBF with FANR not activated. | | +| NOTE 2: The mobile station shall not truncate the EGPRS Ack/Nack Description IE in the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message (see sub-clause 11.2.6e) or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message (see sub-clause 11.2.6f) that would contain a final Ack indicator set to '1'. | | + +A mobile station in DLMC configuration using an SNS of 8192 shall respond to the feedback request indicated by the CES/P field within the RLC data block header (see sub-clause 10.3a.3.1, 10.3a.3.2, 10.3a.3.3, 10.3a.3.4, 10.3a.3.5 and 10.3a.3.10) as shown in Table 9.1.8.2.1.4. + +**Table 9.1.8.2.1.4: Format of CES/P field within each DLMC EGPRS RLC block (EGPRS with FANR activated and EGPRS2)** + +| CES/P | Feedback Request (Poll) Description and Relative Reserved Block Period | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | Nothing | +| 01 | EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing FPB, and if there is enough room left in the RLC/MAC block, channel quality report(s) within the radio period (N+8 or N+9) mod 2715648 in the BTTI configuration or (N+6 or N+7) mod 2715648 in the RTTI configuration | +| 10 | EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing Channel Quality Report(s) and if there is enough room left in the RLC/MAC block, NPB within the radio period (N+8 or N+9) mod 2715648 in the BTTI configuration or (N+6 or N+7) mod 2715648 in the RTTI configuration (NOTE 1) | +| 11 | EGPRS RLC/MAC block for data transfer with a PAN field containing FPB within the radio period (N+8 or N+9) mod 2715648 in the BTTI configuration or (N+6 or N+7) mod 2715648 in the RTTI configuration (NOTE 2) | +| NOTE 1: The mobile station shall not truncate the EGPRS Ack/Nack Description IE in the EGPRS PACKET DOWNLINK ACK/NACK DLMC message (see sub-clause 11.2.48) that would contain a final Ack indicator set to '1'. | | +| NOTE 2: The mobile station shall ignore the poll for PAN in the case when received for a TBF with FANR not activated. | | + +In a DLMC configuration, when the MS sends channel quality report information it shall use the value of the DLMC Measurement Type field (see sub-clause 11.2.7) within the most recently received assignment message as follows: + +- If this field indicates measurement information is to be reported on a per UFPS basis the MS shall always include channel quality measurements for the UFPS corresponding to the radio frequency channel on which the poll was received. If there is room in the message (see sub-clause 11.2.48) the MS shall report additional higher numbered UFPS (if any) beginning with the next in sequence UFPS (see sub-clause 8.1.1.1.3 for the numbering of UFPS and 3GPP TS 45.008 [15] for how DLMC BEP Link Quality Measurements are reported on a per UFPS basis). +- If this field indicates measurement information is to be reported on a per carrier basis the MS shall always include channel quality measurements for the carrier corresponding to the radio frequency channel on which the poll was received. If there is room in the message (see sub-clause 11.2.48) the MS shall report additional higher numbered carriers (if any) beginning with the next in sequence carrier (see sub-clause 8.1.1.1.3 for the numbering of downlink carriers in a DLMC configuration). + +For MBMS bearers, in case cell re-selection criteria are not fulfilled (see 3GPP TS 45.008): + +- If the ES/P field is set to '11' the mobile station shall include measurement reports for at least three neighbouring cells in addition to the NPB. If the complete NPB is included, the mobile station shall include measurement results for more neighbouring cells, if there is sufficient space; +- Else (i.e. the ES/P field is set to '01' or '10') the mobile station shall send as much of either the FPB or NPB (as specified in Table 9.1.8.2.1.2) as possible and, if the entire FPB/NPB is sent, measurement reports for as many neighbouring cells as can also be included. + +For MBMS bearers, in case cell re-selection criteria are fulfilled towards a neighbouring cell (see 3GPP TS 45.008), the mobile station if polled shall include in the MBMS DOWNLINK ACK/NACK message the measurement report only for that cell and as much of either the First Partial Bitmap (FPB) or Next Partial Bitmap (NPB) (as specified in Table 9.1.8.2.1.2) as possible. + +## 9.1.8.2.2 Determination of SSN + +If the receiving side is the network, the network may select any SSN within the receive window. If the receiving side is the mobile station, SSN shall be determined as follows: Let PBSN represent a Partial Bitmap Sequence Number variable stored at the receiver which helps to determine the Starting Sequence Number (SSN) for the next partial bitmap to be transmitted. Based on PBSN, V(Q) and the ES/P field set by the network, SSN and PBSN shall be determined according to table 9.1.8.2.2.1. For EGPRS when FANR is activated and for EGPRS2, SSN and PBSN shall be determined based on PBSN, V(Q) and CES/P fields according to table 9.1.8.2.2.2 and 9.1.8.2.2.3. + +**Table 9.1.8.2.2.1: Determination of SSN as a function of ES/P, V(Q) and PBSN** + +| Full bitmap (compressed or not) | ES/P | Determination of SSN | +|---------------------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| - | 00 | - | +| fits in available space | 01,
10,
11 | Set SSN = (V(Q)+1) modulo SNS
set PBSN = V(Q). | +| does not fit in available space | 01 | Set SSN = (V(Q)+1) modulo SNS,
set PBSN = last sequence number for which Ack/Nack status can be indicated in available space in EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC or MBMS DOWNLINK ACK/NACK message. | +| | 10,
11 | If (PBSN+1) modulo SNS = V(Q) or (PBSN+1) modulo SNS lies outside the receiver window set SSN = (V(Q)+1) modulo SNS,
else
set SSN = (PBSN+1) modulo SNS and
set PBSN = last sequence number for which Ack/Nack status can be indicated in available space in EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC or MBMS DOWNLINK ACK/NACK message. | + +**Table 9.1.8.2.2.2: Determination of SSN as a function of CES/P, V(Q) and PBSN** + +| Full bitmap (compressed or not) | CES/P | Determination of SSN | +|---------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| - | 000 | - | +| fits in available space | 001,
010,
101,
110,
111 | Set SSN = (V(Q)+1) modulo SNS
set PBSN = V(Q). | +| does not fit in available space | 001,
010 | Set SSN = (V(Q)+1) modulo SNS,
set PBSN = last sequence number for which Ack/Nack status can be indicated in available space in EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or MBMS DOWNLINK ACK/NACK message. | +| | 101,
110,
111 | If (PBSN+1) modulo SNS = V(Q) or (PBSN+1) modulo SNS lies outside the receiver window set SSN = (V(Q)+1) modulo SNS,
else
set SSN = (PBSN+1) modulo SNS and
set PBSN = last sequence number for which Ack/Nack status can be indicated in available space in EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or MBMS DOWNLINK ACK/NACK message.
(see Note) | + +NOTE: For a TBF with FANR activated, the CES/P combinations '011' and '100' mean the mobile station is polled for a PAN (see sub-clause 10.4.4b). If the mobile station responds to the poll by transmitting an EGPRS RLC/MAC block for data transfer with a PAN field included (see sub-clause 8.1.2.2), SSN is determined as specified in sub-clause 9.1.8.2.2a. For a TBF with FANR not activated, the CES/P combinations '011' and '100' shall be ignored by the mobile station. + +**Table 9.1.8.2.2.3: Determination of SSN as a function of CES/P, V(Q) and PBSN (DLMC configuration using an SNS of 8192)** + +| Full bitmap (compressed or not) | CES/P | Determination of SSN | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| - | 00 | - | +| fits in available space | 01, 10 | Set SSN = (V(Q)+1) modulo SNS
set PBSN = V(Q). | +| does not fit in available space | 01 | Set SSN = (V(Q)+1) modulo SNS,
set PBSN = last sequence number for which Ack/Nack status can be indicated in available space in EGPRS PACKET DOWNLINK ACK/NACK DLMC message. | +| | 10 | If (PBSN+1) modulo SNS = V(Q) or (PBSN+1) modulo SNS lies outside the receiver window set SSN = (V(Q)+1) modulo SNS,
else
set SSN = (PBSN+1) modulo SNS and
set PBSN = last sequence number for which Ack/Nack status can be indicated in available space in EGPRS PACKET DOWNLINK ACK/NACK DLMC.
(see NOTE 1) | +| NOTE 1: The CES/P value '11' indicates the mobile station is polled for a PAN (see sub-clause 10.4.4b).
If the mobile station responds to the poll by transmitting an EGPRS or EGPRS2 RLC/MAC block for data transfer with a PAN field included (see sub-clause 8.1.2.2), SSN is determined as specified in sub-clause 9.1.8.2.2a. | | | + +When a next partial bitmap needs to be transmitted in response to a poll, it may turn out that $(V(R)-PBSN) \bmod \text{SNS}$ is much smaller than the available space. In such cases, a larger amount of feedback can be provided as an implementation option if the receiver backtracks from PBSN and represents as much of the $V(Q)$ to PBSN range as possible, in addition to the PBSN to $V(R)$ range, possibly using compression. If backtracking is carried out, the SSN must be properly indicated within the Ack/Nack description in order to allow the transmitter to accurately interpret the feedback. For MBMS Bearers, this option may only apply if the cell re-selection criteria are fulfilled (see 3GPP TS 45.008). + +#### 9.1.8.2.2a Determination of ShortSSN and SSN in the Piggy-backed Ack/Nack field + +If the receiving side is the network, the network may select any SSN within the receive window. If the receiving side is the mobile station, SSN shall be determined as follows. + +In case of polled FANR (see sub-clause 9.1.14.2), SSN shall be set to $V(Q) + 1$ . + +In case of event-based FANR, the SSN shall be set to the following value (where BSN' is the BSN of the oldest RLC data block of which the corresponding element in $V(N)$ has the value UNREPORTED, and N is the number of bits in the bitmap): + +- the higher of $V(Q) + 1$ and $V(R) - N$ , provided that the bitmap includes BSN', else +- $BSN' + 1$ , if $V(Q)$ is equal to $BSN'$ , else +- $BSN'$ , if $V(Q)$ is not equal to $BSN'$ . + +The ShortSSN shall then be set to the value of the $L$ least significant bits of SSN. The number $L$ of bits is determined as defined in sub-clause 10.4.23. + +#### 9.1.8.2.3 Generation of the bitmap + +First, a Full Received Bitmap (FRB) is built from the receive state array $V(N)$ by extracting the part between $V(Q)$ and $V(R)$ similar to the GPRS case: it is assigned the elements whose indices in the receive state array $V(N)$ at the receiver range from $[V(Q)+1]$ to $[V(R)-1]$ (modulo SNS). For each bit in the bitmap, the bit is assigned the value '1' if the corresponding element in $V(N)$ indexed relative to SSN has the value RECEIVED. The bit is assigned the value '0' if the element in $V(N)$ has the value INVALID. For a TBF with FANR activated, the bit is assigned the value '0' also if the element in $V(N)$ has the value UNREPORTED or REPORTED. + +For EGPRS TBFs for which FANR is not active and for which neither downlink dual carrier configuration nor DLMC configuration nor EGPRS2 nor TBFs running in RLC non-persistent mode are used, the same principles and implementation options as for GPRS apply regarding the determination of V(R). + +For EGPRS TBFs for which FANR is not active and for which either downlink dual carrier configuration, or DLMC configuration or EGPRS2 or RLC non-persistent mode are used, when the mobile station is polled, V(R) shall be determined taking into account all RLC data blocks received up to and including those received in the radio block period where the poll is received. + +For EGPRS TBFs for which FANR is active, V(R) and therefore the bitmap shall be determined taking into account all RLC data blocks received up to and including those received in the reduced radio block period m-2 for RTTI configuration, and those received in the basic radio block period m-2 for BTTI configuration, where the bitmap is sent in radio block period m. + +From the FRB, a reported bitmap (RB) shall then be generated. The FRB shall be recalculated before each RB is generated, except that PAN fields transmitted during the same radio block period for the same TBF shall be based on the same FRB and the FRB shall therefore not be recalculated between the generation of these PAN fields. Different lengths of RBs exist (see clause 12 and sub-clause 10.3.a.5). For uplink TBFs, the network may transmit any RB size to the mobile station. For downlink TBFs, the network may order the mobile station to transmit a certain RB size through use of the ES/P field. The bitmap size may be selected based on e.g. risk of protocol stalling. The RB in a PAN field is always uncompressed. In EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 messages, and EGPRS PACKET DOWNLINK ACK/NACK DLMC the RB is one of the following types: + +a) Uncompressed reported bitmap: + +If the range of indices from SSN to the end of FRB is less than or equal to N bits, where N is the reported bitmap size, the RB starts at SSN and covers the range of indices from SSN to the end of FRB. When an RB is a part of a PAN field, if the number of indices from SSN to the end of FRB is less than N bits and the reported bitmap is generated by the mobile station, the bits not covering the FRB shall be set to the value '0'. When an RB is a part of a PAN field, if the number of indices from SSN to the end of FRB is less than N bits and the reported bitmap is generated by the network, the bits not covering the FRB shall be set to the value '1'. If the range of indices from SSN to the end of FRB is greater than N bits, the RB is assigned the first N bits of the FRB starting at SSN. + +b) Compressed reported bitmap: + +Using the compression algorithm, the receiver generates RB of length N bits starting at SSN, where N is the reported bitmap size used. + +If the compressed reported bitmap covers more blocks than the uncompressed reported bitmap, the receiver shall send the compressed reported bitmap, otherwise the receiver shall send the uncompressed reported bitmap. As an exception, if the FRB length or the range of indices from SSN to the end of FRB is less than or equal to N bits, the receiver may send the uncompressed reported bitmap without attempting compression. + +The BOW (begin of window) bit shall be set if $SSN = [V(Q) + 1] \bmod SNS$ , the EOW (end of window) bit shall be set if $[V(R) - 1] \bmod SNS$ is explicitly included in the bitmap. + +If V(Q) equals V(R), then SSN shall be set to the value $SSN = [V(Q) + 1] \bmod SNS$ , BOW bit shall be set to the value '1', EOW shall be set to the value '1' and the reported bitmap size shall equal 0 bits. + +For uplink TBFs, the reported bitmap is sent using the PACKET UPLINK ACK/NACK message corresponding to the used RB size. + +For downlink TBFs the reported bitmap is sent using the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message for mobiles with one or more downlink TBFs using EGPRS2, or using EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message otherwise. For MBMS bearers the reported bitmap is sent using the MBMS DOWNLINK ACK/NACK message. For a DLMC configuration the reported bitmap is sent using the EGPRS PACKET DOWNLINK ACK/NACK DLMC message. + +### 9.1.8.2.4 Interpretation of the bitmap + +If a compressed reported bitmap is received, the bitmap shall first be decompressed according to sub-clause 9.1.10. The uncompressed bitmap shall then be treated as follows: + +Firstly, if the BOW bit in PACKET UPLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLCM message has the value '1', then the bitmap acknowledges all blocks between V(A) and (SSN- 2) (modulo SNS), and the corresponding elements in V(B) shall be set to the value ACKED. Also a bitmap value of '0' is assumed at the bit position corresponding to (SSN-1) modulo SNS which corresponds to V(Q). If the BOW bit in MBMS DOWNLINK ACK/NACK message has the value '1', then the bitmap acknowledges all blocks between V(A) and (SSN-2) (modulo SNS), and a bitmap value of '0' is assumed at the bit position corresponding to (SSN-1) modulo SNS, only for the mobile station sending the message. The decision whether to set the corresponding elements in V(B) to the value ACKED is implementation specific. + +Then, in case of PACKET UPLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLCM message, for each bit in the uncompressed bitmap whose corresponding BSN value is within the transmit window, if the bit contains the value '1', the corresponding element in V(B) indexed relative to SSN shall be set to the value ACKED. If the bit contains the value '0', the element in V(B) shall be set to the value NACKED. A bit within the uncompressed bitmap whose corresponding BSN is not within the transmit window, shall be ignored. In case of MBMS DOWNLINK ACK/NACK message, for each bit in the uncompressed bitmap whose corresponding BSN value is within the transmit window, if the bit contains the value '1', it positively acknowledges the corresponding RLC data block only for the mobile station sending the message, and the decision whether to set to the value ACKED the corresponding element in V(B) indexed relative to SSN is implementation specific. If the bit contains the value '0', it negatively acknowledges the corresponding RLC data block only for the mobile station sending the message, and the decision whether to set to the value NACKED the corresponding element in V(B) indexed relative to SSN is implementation specific. A bit within the uncompressed bitmap whose corresponding BSN is not within the transmit window shall be ignored. + +If the EOW bit in the PACKET UPLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3, EGPRS PACKET DOWNLINK ACK/NACK DLCM or MBMS DOWNLINK ACK/NACK message has the value '1', then bitmap value '0' shall be assumed for all RLC blocks with a BSN value higher than the last entry in the bitmap but less than V(S) (i.e. $[V(R) - 1 < \text{BSN} < V(S)]$ modulo SNS). + +If the RLC transmitter is on the mobile station side, the bit in the bitmap contains the value '0' and the number of block periods between the end of the block period used for the last transmission of the corresponding RLC data block and the beginning of the block period containing the PACKET UPLINK ACK/NACK message is less than $(\max(\text{BS\_CV\_MAX}, 1) - 1)$ (i.e. the RLC data block was recently (re)transmitted and thus can not be validly negatively acknowledged in this particular PACKET UPLINK ACK/NACK message), the element in V(B) shall not be modified. Similarly, if the RLC transmitter is on the network side and the RLC data block cannot be validly negatively acknowledged in this particular Packet Ack/Nack message the element in V(B) shall not be modified. + +In the case of a PAN field, the bitmap shall be interpreted in the same way as for the case of PACKET UPLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLCM message with the following exceptions: + +- in the case when the PAN is received by the network, in RLC acknowledged mode, elements of V(B) shall not be set to ACKED; any element which would be set to ACKED shall be set to TENTATIVE\_ACK; +- in the case when the PAN is received by the mobile station, the contents of the reported bitmap shall be validated assuming a BS\_CV\_MAX value of 2, regardless of the value of the signalled BS\_CV\_MAX parameter; +- in the case when the PAN is received by the mobile station, the value '1' received in the reported bitmap shall not modify the current value of the corresponding element in V(B); the value '0' received in the reported bitmap shall set the corresponding element in V(B) to the value NACKED; in RLC acknowledged mode and when the BOW is set to the value '1' then all elements in V(B) corresponding to all blocks between V(A) and (SSN- 2) (modulo SNS) shall be set to the value TENTATIVE\_ACK; +- if the processing of a PAN would cause an element of V(B) to be changed from ACKED or TENTATIVE\_ACK to NACKED, the entire PAN field shall be ignored; + +- if a PAN positively acknowledges a block which has not yet been transmitted (i.e. whose BSN is higher than or equal to V(S)) the entire PAN field shall be ignored; +- if a time-based PAN indicates a reserved value the entire PAN field shall be ignored. + +NOTE: The last three conditions may arise due to undetected error in the PANI or in the PAN field. + +### 9.1.8.3 Starting sequence number (SSN) and received block bitmap (RBB) in EC TBF + +The Packet Ack/Nack message contains a starting sequence number (SSN) and a received block bitmap (RBB). The Packet Ack/Nack message is sent by the RLC receiver and is received by the RLC transmitter. The SSN and RBB are determined as defined in this sub-clause and transmitted in RLC acknowledged mode. + +The RBB is defined as a binary valued array of WS elements (see sub-clause 12.72), where the index of each element takes value 0, 1, 2, ..., WS-1 in the given order, respectively, or a binary valued array of WS/2 elements (see sub-clause 12.73), where the index of each element takes value 0, 1, 2, ..., WS/2-1 in the given order, respectively. The BSN values specified in the RBB are interpreted by adding the bit position in the bitmap from the starting sequence number (SSN) modulo SNS. + +A valid BSN value in the RBB is one that is in the range $[ V(A) < BSN < V(S) ]$ modulo SNS. + +These inequalities shall be interpreted in the following way: + +BSN is valid if, and only if, $([ BSN - V(A) ] \bmod SNS < [ V(S) - V(A) ] \bmod SNS)$ and $(BSN \neq V(A))$ . + +At the RLC transmitter: + +- For each bit in the RBB whose corresponding BSN value is within the transmit window, if the bit contains the value '1', the corresponding element in V(B) indexed relative to SSN shall be set to the value ACKED. If the bit contains the value '0', the element in V(B) shall be set to the value NACKED. All blocks between V(A) and $(SSN - 2)$ (modulo SNS) shall be considered acknowledged, and the corresponding elements in V(B) shall be set to the value ACKED. Also a bitmap value of '0' is assumed at the bit position corresponding to $(SSN - 1)$ modulo SNS, which corresponds to V(Q). A bit within the RBB whose corresponding BSN is not within the transmit window, shall be ignored. + +At the RLC receiver: + +- The starting sequence number (SSN) is assigned the value $(V(Q)+1)$ modulo SNS. The received block bitmap (RBB) is assigned the elements whose indices in the receive state array V(N) at the receiver range from $[V(Q) + 1]$ to $[V(R) - 1]$ (modulo SNS). For each bit in the bitmap, the bit is assigned the value '1' if the corresponding element in V(N) indexed relative to SSN has the value RECEIVED. The bit is assigned the value '0' if the element in V(N) has the value INVALID. + +## 9.1.9 Window Size + +### 9.1.9.1 GPRS + +For GPRS, the window size (WS) shall be 64. + +### 9.1.9.2 EGPRS + +A mobile station may support the use of the GPRS multislot class also for the EGPRS-GMSK only TBF mode. The support of this feature must be indicated as the "*Modulation based multislot class support*" information in the MS Radio Access Capability IE and the MS Radio Access Capability 2 IE. + +A mobile station in EGPRS TBF mode not supporting the "*Modulation based multislot class support*" shall apply the EGPRS multislot class. A mobile station in EGPRS-GMSK only TBF mode shall apply the GPRS multislot class. + +While a EGPRS-GMSK only TBF mode is in progress, if a mobile station receives DL blocks not coded with modulation and coding scheme MCS-1 to MCS-4 then the MS behavior is implementation specific. + +For EGPRS the window size (WS) shall be set by the network according to the number of timeslots assigned in the direction of the TBF (uplink or downlink) using the applicable multislot capability except for the case of a DLMC configuration where the window size is determined by the buffer size supported (see Table 9.1.9.3.2). The allowed + +window sizes are given in table 9.1.9.2.1. Preferably, the selected window size should be the maximum, or follow the definition in annex I. + +The window size may be set independently for each TBF on uplink and downlink. The mobile station shall support the maximum window size corresponding to its multislot capability. The selected WS shall be indicated within a PACKET UL/DL ASSIGNMENT, MULTIPLE TBF UL/DL ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message using the coding defined in table 9.1.9.2.1 except for the case of a DLMC configuration where the window size is determined by the buffer size supported (see Table 9.1.9.3.2). + +Once a window size is selected for a given TBF, it may be changed to a larger size but not to a smaller size, in order to prevent dropping data blocks from the window. + +In case the MS multislot class is not indicated during packet data connection establishment (access request for signalling message transfer), a default window size corresponding to the minimum window size for 1 timeslot (as defined in table 9.1.9.2.1) shall be selected. + +In case a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message is sent to the mobile station without any window size for a specific TBF, then any previous value received for the specific TBF shall be used or, if no previous value has been received for the specific TBF, default window size shall be used. + +NOTE: If a TBF is reallocated so that the number of assigned timeslots is reduced, the RLC window size may become larger than the maximum window size for the new resources. + +**Table 9.1.9.2.1: Allowed window sizes in EGPRS TBF mode for different multislot allocations** + +| Window size | Coding | Timeslots assigned (multislot capability) | | | | | | | | +|-------------|--------|-------------------------------------------|---|---|---|---|---|---|---| +| | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| | | | | | | | | | | + +| | | | | | | | | | | +|------------------------------------------------------------|-------|-----|-----|-----|-----|-----|-----|-----|-----| +| 64 | 00000 | | | | | | | | | +| 96 | 00001 | | | | | | | | | +| 128 | 00010 | | | | | | | | | +| 160 | 00011 | | | | | | | | | +| 192 | 00100 | Max | | | | | | | | +| 224 | 00101 | | | | | | | | | +| 256 | 00110 | | Max | | | | | | | +| 288 | 00111 | | | | | | | | | +| 320 | 01000 | | | | | | | | | +| 352 | 01001 | | | | | | | | | +| 384 | 01010 | | | Max | | | | | | +| 416 | 01011 | | | | | | | | | +| 448 | 01100 | | | | | | | | | +| 480 | 01101 | | | | | | | | | +| 512 | 01110 | | | | Max | | | | | +| 544 | 01111 | | | | | | | | | +| 576 | 10000 | | | | | | | | | +| 608 | 10001 | | | | | | | | | +| 640 | 10010 | | | | | Max | | | | +| 672 | 10011 | | | | | | | | | +| 704 | 10100 | | | | | | | | | +| 736 | 10101 | | | | | | | | | +| 768 | 10110 | | | | | | Max | | | +| 800 | 10111 | | | | | | | | | +| 832 | 11000 | | | | | | | | | +| 864 | 11001 | | | | | | | | | +| 896 | 11010 | | | | | | | Max | | +| 928 | 11011 | | | | | | | | | +| 960 | 11100 | | | | | | | | | +| 992 | 11101 | | | | | | | | | +| 1024 | 11110 | | | | | | | | Max | +| Reserved | 11111 | x | x | x | x | x | x | x | X | +| NOTE: The shaded cells represent the allowed window sizes. | | | | | | | | | | + +### 9.1.9.2a EC-GSM-IoT + +For EC-GSM-IoT, i.e. for an EC TBF, the window size (WS) shall be 16. + +### 9.1.9.3 RLC buffer + +A mobile station supporting multiple TBF or EMST shall support one RLC buffer per direction (uplink and downlink). The RLC buffer in a given direction represents the amount of physical memory the mobile station shall support in this direction for RLC PDUs from all RLC instances in the transmit (uplink) or receive (downlink) window(s). The RLC buffer size is given as the maximum number of RLC data blocks that can be stored in this buffer assuming the highest (modulation and) coding scheme supported by the mobile station in this direction. The RLC buffer shall be as follows: + +- A mobile station supporting GPRS (not supporting EGPRS) shall support a RLC buffer of size 64 in both uplink and downlink directions +- A mobile station supporting EGPRS shall support RLC buffers as defined in the Table 9.1.9.3.1 below +- A mobile station in DLMC configuration shall support RLC buffers in the uplink as defined in Table 9.1.9.3.1 and RLC buffers in the downlink as defined in Table 9.1.9.3.2. +- A mobile station supporting EC-GSM-IoT (not supporting GPRS or EGPRS) shall support a RLC buffer of size 16 in both uplink and downlink directions. + +**Table 9.1.9.3.1: RLC buffer in a given direction for EGPRS capable MS** + +| | Maximum amount N of timeslots the MS supports in this direction (see note 1) | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------|----------|----------|----------|----------|----------|----------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| RLC buffer size S (see note 2) | 192 | 256 | 384 | 512 | 640 | 768 | 896 | 1024 | +| NOTE 1: See 3GPP TS 45.002 for multislot classes | | | | | | | | | +| NOTE 2: An EGPRS capable mobile station able to support up to N timeslots in a direction shall support an RLC buffer in this direction that can store S RLC data blocks | | | | | | | | | + +**Table 9.1.9.3.2: Downlink RLC buffer for MS in DLMC Configuration** + +| | Maximum number of downlink timeslots supported (see note 1) | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------|----------------|---------------------| +| | 6 - 20 | 21 - 26 | 27 - 32 | More than 32 | +| RLC buffer size S (see note 2) | 1024 | 2048 | 3072 | 4096 | +| NOTE 1: See MS Radio Access Capability IE in 3GPP TS 24.008 | | | | | +| NOTE 2: A mobile station that supports up to N downlink timeslots in DLMC configuration shall support an RLC buffer that can store S RLC data blocks | | | | | + +NOTE: The sum of the RLC window sizes of all RLC instances running in the mobile station in a given direction may be larger than the mobile station's RLC buffer in this direction. The RLC buffer does not affect the allocation of RLC window size. + +## 9.1.10 Compression + +The compression algorithm is as follows. If the window size is less than the number of bits available for the bitmap, then full feedback is provided using an uncompressed bitmap. If the window size is larger than the number of bits available for the bitmap, then one-dimensional run length coding (based on ITU-T Recommendation T.4) is carried out starting at SSN. + +The T.4 procedure for encoding run lengths is as follows. Runs of ones and zeros alternate, and the run lengths are represented by the code words listed in the tables below. The code words for run lengths of zeros and ones are as described in T.4 except for one minor modification: the terminating code words used for indicating run lengths of 1 zero and 3 zeros are interchanged. This modification helps in achieving some throughput improvement when frequency hopping is carried out. The run length code words are of two types: terminating code words and make-up code words. + +Each run length is represented by either one terminating code word or one make-up code word followed by a terminating code word. Run lengths in the range 0-63 bits are encoded with their appropriate terminating code word. Run lengths greater than 63 bits are encoded first by the make-up code word which is equal to or shorter than that required. This is then followed by the terminating code word representing the difference between the required run length and the run length represented by the make-up code. + +No special code words are used either at the beginning of the bitmap or the end of a bitmap. A one bit indicator (i.e. Compressed Bitmap Starting Color Code) is used to indicate whether the compressed bitmap starts with a run length of zeros or a run length of ones. + +The compressed bitmap is assumed to be of length $L_c$ (see clause 12) bits. The run length encoder output is used only if a compression gain is realized; otherwise an uncompressed partial bitmap is transmitted. The compressed portion of the bitmap must end on a T.4 code word boundary which may or may not coincide with the number of bits available. In such cases, one possible implementation is to recognize the boundary of the last valid T.4 code word that fits into the available space as the end of the compressed bitmap. The rest of the bitmap is assumed to be uncompressed; the uncompressed portion of the bitmap has variable length (see clause 12). Any bits representing sequence numbers $V(R)$ or beyond in either the compressed or uncompressed portion of the bitmap must be set to 0. Implementations may use other schemes to determine the boundary between the compressed and uncompressed portions of the bitmap. + +**Table 9.1.10.1: Terminating codes (reproduced from ITU-T Recommendation T.4); +T.4 code words used for representing run lengths of 1 zero and 3 zeros are interchanged** + +| One run length | Code word | Zero run length | Code word | +|----------------|-----------|-----------------|--------------| +| 0 | 00110101 | 0 | 0000110111 | +| 1 | 000111 | 1 | 10 | +| 2 | 0111 | 2 | 11 | +| 3 | 1000 | 3 | 010 | +| 4 | 1011 | 4 | 011 | +| 5 | 1100 | 5 | 0011 | +| 6 | 1110 | 6 | 0010 | +| 7 | 1111 | 7 | 00011 | +| 8 | 10011 | 8 | 000101 | +| 9 | 10100 | 9 | 000100 | +| 10 | 00111 | 10 | 0000100 | +| 11 | 01000 | 11 | 0000101 | +| 12 | 001000 | 12 | 0000111 | +| 13 | 000011 | 13 | 00000100 | +| 14 | 110100 | 14 | 00000111 | +| 15 | 110101 | 15 | 000011000 | +| 16 | 101010 | 16 | 0000010111 | +| 17 | 101011 | 17 | 0000011000 | +| 18 | 0100111 | 18 | 0000001000 | +| 19 | 0001100 | 19 | 00001100111 | +| 20 | 0001000 | 20 | 00001101000 | +| 21 | 0010111 | 21 | 00001101100 | +| 22 | 0000011 | 22 | 00000110111 | +| 23 | 0000100 | 23 | 00000101000 | +| 24 | 0101000 | 24 | 00000010111 | +| 25 | 0101011 | 25 | 00000011000 | +| 26 | 0010011 | 26 | 000011001010 | +| 27 | 0100100 | 27 | 000011001011 | +| 28 | 0011000 | 28 | 000011001100 | +| 29 | 00000010 | 29 | 000011001101 | +| 30 | 00000011 | 30 | 000001101000 | +| 31 | 00011010 | 31 | 000001101001 | +| 32 | 00011011 | 32 | 000001101010 | +| 33 | 00010010 | 33 | 000001101011 | +| 34 | 00010011 | 34 | 000011010010 | +| 35 | 00010100 | 35 | 000011010011 | +| 36 | 00010101 | 36 | 000011010100 | +| 37 | 00010110 | 37 | 000011010101 | +| 38 | 00010111 | 38 | 000011010110 | +| 39 | 00101000 | 39 | 000011010111 | +| 40 | 00101001 | 40 | 000001101100 | +| 41 | 00101010 | 41 | 000001101101 | +| 42 | 00101011 | 42 | 000011011010 | +| 43 | 00101100 | 43 | 000011011011 | +| 44 | 00101101 | 44 | 000001010100 | +| 45 | 00000100 | 45 | 000001010101 | +| 46 | 00000101 | 46 | 000001010110 | +| 47 | 00001010 | 47 | 000001010111 | +| 48 | 00001011 | 48 | 000001100100 | +| 49 | 01010010 | 49 | 000001100101 | +| 50 | 01010011 | 50 | 000001010010 | +| 51 | 01010100 | 51 | 000001010011 | +| 52 | 01010101 | 52 | 000000100100 | +| 53 | 00100100 | 53 | 000000110111 | +| 54 | 00100101 | 54 | 000000111000 | +| 55 | 01011000 | 55 | 000000100111 | +| 56 | 01011001 | 56 | 000000101000 | +| 57 | 01011010 | 57 | 000001011000 | +| 58 | 01011011 | 58 | 000001011001 | +| 59 | 01001010 | 59 | 000000101011 | +| 60 | 01001011 | 60 | 000000101100 | +| 61 | 00110010 | 61 | 000001011010 | +| 62 | 00110011 | 62 | 000001100110 | + +| One run length | Code word | Zero run length | Code word | +|----------------|-----------|-----------------|--------------| +| 63 | 00110100 | 63 | 000001100111 | + +**Table 9.1.10.2: Make-up codes +(reproduced from ITU-T Recommendation T.4)** + +| One run length | Code word | Zero run length | Code word | +|----------------|-----------|-----------------|---------------| +| 64 | 11011 | 64 | 0000001111 | +| 128 | 10010 | 128 | 000011001000 | +| 192 | 010111 | 192 | 000011001001 | +| 256 | 0110111 | 256 | 000001011011 | +| 320 | 00110110 | 320 | 000000110011 | +| 384 | 00110111 | 384 | 000000110100 | +| 448 | 01100100 | 448 | 000000110101 | +| 512 | 01100101 | 512 | 0000001101100 | +| 576 | 01101000 | 576 | 0000001101101 | +| 640 | 01100111 | 640 | 0000001001010 | +| 704 | 011001100 | 704 | 0000001001011 | +| 768 | 011001101 | 768 | 0000001001100 | +| 832 | 011010010 | 832 | 0000001001101 | +| 896 | 011010011 | 896 | 0000001110010 | +| 960 | 011010100 | 960 | 0000001110011 | + +## 9.1.11 Segmentation of upper layer PDUs into RLC data units + +Segmentation of upper layer PDUs is supported to allow transport of upper layer PDUs larger than the data field of a single RLC data block. If the contents of an upper layer PDU do not fill an integer number of RLC data blocks, the beginning of the next upper layer PDU shall be placed within the final RLC data block of the first upper layer PDU, with no padding or spacing between the end of the first upper layer PDU and the beginning of the next. If the final upper layer PDU in the TBF does not fill an integer number of RLC data blocks, filler octets shall be used to fill the remainder of the RLC data block. + +The received (and segmented) upper layer PDUs shall be put into RLC data blocks in the same order as they are received from higher layers, except if resource reallocation for an uplink TBF is needed as described in sub-clause 8.1.1.1.2. A Block Sequence Number (BSN) is included in the header of each RLC data block to number the RLC data block. The RLC data blocks are to be numbered consecutively, modulo SNS, to allow re-assembly of the upper layer PDUs on the receiving side. + +If EMSR is enabled, the transmission of an upper layer PDU may be suspended to transmit one or more upper layer PDUs of a higher priority. Once all higher priority upper layer PDUs have been transmitted, the transmission of the lower priority upper layer PDU can be resumed. The transition between two upper layer PDUs resulting from this suspend-resume function is described in sub-clause 10.4.14a. + +In GPRS TBF mode, once an RLC data block has been transmitted over the physical link, should it be necessary to re-transmit the RLC data block, it shall be re-transmitted using the same channel coding scheme, BSN, and CV as it had in the previous transmission. + +In EGPRS TBF mode, once an RLC data block has been transmitted over the physical link, should it be necessary to re-transmit the RLC data block, it shall be re-transmitted using the same BSN and the same calculated CV as were used in the previous transmission. The modulation and coding scheme may be changed following the procedures described in sub-clause 9.3.2.1. + +In EC TBF mode, once an RLC data block has been transmitted over the physical link, should it be necessary to re-transmit the RLC data block, it shall be re-transmitted using the same BSN and the same CV as were used in the previous transmission. If the RLC data block is transmitted using blind physical layer transmissions, all the elements in the RLC/MAC header, except for the USF, shall be the same in the retransmission as were used in the previous transmission. Otherwise, the modulation and coding scheme may be changed following the procedures described in sub-clause 9.3.2.1a. + +### 9.1.12 Re-assembly of upper layer PDUs from RLC data units + +RLC data blocks shall be collected at the receiver until all RLC data blocks comprising an upper layer PDU have been received. The RLC headers shall be removed from each RLC data block at this time and the RLC data units re-assembled into an upper layer PDU and passed to the next higher layer. In *A/Gb mode*, the size of the upper layer PDU delivered to the higher layer shall not exceed 1560 octets. Any octet received beyond this maximum limit and until the next identified upper layer PDU boundary shall be discarded. + +During RLC acknowledged mode operation, received upper layer PDUs shall be delivered to the higher layer in the order in which they were originally transmitted. + +During RLC unacknowledged mode operation, received upper layer PDUs shall be delivered to the higher layer in the order in which they are received. + +During RLC non-persistent mode operation, received upper layer PDUs shall be delivered to the higher layer in the order in which they were originally transmitted. Nevertheless, since some RLC data units may not be received, some upper layer PDUs may be re-assembled and delivered to the higher layer erroneously. The receiving RLC endpoint shall use RLC data units up to the one characterized by $BSN = V(Q) - 1$ when reassembling upper layer PDUs, even if some RLC data units are missing. + +If EMSR is enabled, the transmission of an upper layer PDU may be suspended to transmit one or more upper layer PDUs of a higher priority and resumed thereafter. The transition between two upper layer PDUs resulting from this suspend-resume function is described in sub-clause 10.4.14a. + +Fill bits having the value '0' shall be substituted for RLC data units not received. However, in EGPRS TBF mode, for erroneous RLC data blocks for which the header is correctly received, the output from decoder shall be delivered to the higher layer. The number of fill bits substituted shall be determined using Tables 9.1.12.a, 9.1.12.b, 9.1.12.c, 9.1.12.d, 9.1.12.e, 9.1.12.f. In the uplink direction the channel coding scheme shall be the commanded channel coding scheme. In the downlink direction the channel coding scheme shall be the channel coding scheme of the last correctly received RLC data block. If no RLC data blocks have been correctly received, by the mobile station the requested channel coding scheme shall be used. If no requested channel coding scheme has been sent to the network, the mobile station shall use the number of fill bits for CS-1. + +**Table 9.1.12.a: RLC unacknowledged mode fill bits (GPRS)** + +| Channel Coding Scheme | Number of fill bits | +|-----------------------|---------------------| +| CS-1 | 160 | +| CS-2 | 240 | +| CS-3 | 288 | +| CS-4 | 400 | + +**Table 9.1.12.b: RLC unacknowledged mode fill bits (EGPRS)** + +| Channel Coding Scheme | Number of fill bits | +|-----------------------|---------------------| +| MCS-1 | 176 | +| MCS-2 | 224 | +| MCS-3 with padding | 248 | +| MCS-3 | 296 | +| MCS-4 | 352 | +| MCS-5 | 448 | +| MCS-6 with padding | 544 | +| MCS-6 | 592 | +| MCS-7 | 448 | +| MCS-8 | 544 | +| MCS-9 | 592 | + +**Table 9.1.12.c: RLC unacknowledged mode fill bits (EGPRS2-A downlink)** + +| Channel Coding Scheme | Number of fill bits | +|-----------------------|---------------------| +| MCS-2 with padding | 208 | +| DAS-5 | 448 | +| DAS-6 | 544 | +| DAS-7 | 656 | +| DAS-8 | 448 | +| DAS-9 | 544 | +| DAS-10 | 656 | +| DAS-11 | 544 | +| DAS-12 | 656 | + +NOTE: MCS-1, MCS-2 (with or without padding), MCS-3 (with or without padding), MCS-4, MCS-6, MCS-7 and MCS-8 are also used for EGPRS2-A downlink (see sub-clause 5.2.1). For these modulation and coding schemes, fill bits are defined in Table 9.1.12.b unless specified otherwise. + +**Table 9.1.12.d: RLC unacknowledged mode fill bits (EGPRS2-B downlink)** + +| Channel Coding Scheme | Number of fill bits | +|-----------------------|---------------------| +| DBS-5 | 448 | +| DBS-6 | 592 | +| DBS-7 | 448 | +| DAS-10 with padding | 592 | +| DBS-8 | 592 | +| DBS-9 | 448 | +| DAS-12 with padding | 592 | +| DBS-10 | 592 | +| DBS-11 | 544 | +| DBS-12 | 592 | + +NOTE: MCS-1, MCS-2, MCS-3 (with or without padding), MCS-4, MCS-6 to MCS-9, DAS-5, DAS-6, DAS-8, DAS-9, DAS-10 with padding, DAS-11 and DAS-12 with padding are also used for EGPRS2-B downlink (see sub-clause 5.2.1). For these modulation and coding schemes, fill bits are defined in Table 9.1.12.b and Table 9.1.12.c. unless specified otherwise. + +**Table 9.1.12.e: RLC unacknowledged mode fill bits (EGPRS2-A uplink)** + +| Channel Coding Scheme | Number of fill bits | +|-----------------------|---------------------| +| MCS-3 with padding | 216 | +| MCS-6 with padding | 512 | +| UAS-7 | 448 | +| UAS-8 | 512 | +| UAS-9 | 592 | +| UAS-10 | 448 | +| UAS-11 | 512 | + +NOTE: MCS-1, MCS-2, MCS-3 (with or without padding), MCS-4, MCS-5 and MCS-6 (with or without padding) are also used for EGPRS2-A uplink (see sub-clause 5.2.1). For these modulation and coding schemes, fill bits are defined in Table 9.1.12.b unless specified otherwise. + +**Table 9.1.12.f: RLC unacknowledged mode fill bits (EGPRS2-B uplink)** + +| Channel Coding Scheme | Number of fill bits | +|-----------------------|---------------------| +| UBS-5 | 448 | +| UBS-6 with padding | 544 | +| UBS-6 | 592 | +| UBS-7 | 448 | +| UBS-8 with padding | 544 | +| UBS-8 | 592 | +| UBS-9 | 448 | +| UBS-10 with padding | 544 | +| UBS-10 | 592 | +| UBS-11 | 544 | +| UBS-12 | 592 | + +NOTE: MCS-1 to MCS-4 are also used for EGPRS2-B uplink (see sub-clause 5.2.1). For these modulation and coding schemes, fill bits are defined in Table 9.1.12.b unless specified otherwise. + +## 9.1.12a Segmentation of RLC/MAC control messages into RLC/MAC control blocks + +The network may segment RLC/MAC control messages into one, two or up to nine RLC/MAC control blocks depending on the length of the RLC/MAC control message. Segmentation of an RLC/MAC control message into more than two RLC/MAC control blocks is referred to as extended RLC/MAC control message segmentation. Extended RLC/MAC control message segmentation shall not be used for an RLC/MAC control message that can be sent using one or two RLC/MAC control blocks. Unless explicitly stated otherwise, extended RLC/MAC control message segmentation shall not be used. If the contents of a control message do not fit an integer number of control blocks, filler octets shall be used to fill the remainder of the RLC/MAC control block. Only the last RLC/MAC control block containing elements of the control message shall contain filler octets. The Final Segment (FS) bit of the RLC/MAC control block header shall be set according to whether the RLC/MAC control block contains the final segment of an RLC/MAC control message, except in case of extended RLC/MAC control message segmentation in which case the FS bit shall always be set to '0'. In case of extended RLC/MAC control message segmentation, the Final Segment extension (FSe) bit of the RLC/MAC control block header (included in the second RLC/MAC control block onwards) shall be set according to whether the RLC/MAC control block contains the final segment of an RLC/MAC control message (see sub-clauses 10.4.9e and 10.4.12b). + +The mobile station shall not segment RLC/MAC control messages. + +NOTE: In order to provide the mobile station a Power Reduction value in a RLC/MAC control block, the network may use the segmentation mechanism although the RLC/MAC control block requires only one RLC/MAC control block to be transmitted. In that case the RBSN shall be set to '0' and FS shall be set to '1'. + +## 9.1.12b Re-assembly of RLC/MAC control messages from RLC/MAC control blocks + +RLC/MAC control blocks shall be collected at the receiver until all RLC/MAC control blocks comprising an RLC/MAC control message have been received. + +In packet idle mode, the mobile station shall be capable of receiving eight RLC/MAC control messages in parallel. If the mobile station receives RLC/MAC control blocks containing part of a ninth RLC/MAC control message while it still has RLC/MAC control blocks for eight partially received RLC/MAC control messages, the mobile station shall discard the RLC/MAC control blocks of the oldest partially received message. + +A mobile station that has enabled EC operation only needs to be capable of receiving one RLC/MAC control message at a time when in packet idle mode. + +In packet transfer mode, the mobile station shall be capable of receiving two RLC/MAC control messages in parallel on the same PDCH. If the mobile station receives RLC/MAC control blocks containing part of a third RLC/MAC control message while it still has RLC/MAC control blocks for two partially received RLC/MAC control messages, the mobile station shall discard the RLC/MAC control block of the oldest partially received message. + +A mobile station in EC operation only needs to be capable of receiving one RLC/MAC control message at a time when in packet transfer mode, i.e. when it has an EC TBF. + +A mobile station, which is not in EC operation, shall start an instance of timer T3200 following the receipt of an RLC/MAC control block whose RTI value does not correspond to the RTI value of a partially received RLC/MAC control message or if the RLC/MAC control blocks were received on different PDCHs. In non-DRX mode the duration of timer T3200 shall be four BS\_CV\_MAX block periods. In DRX mode the duration of timer T3200 shall be four times the DRX period (see 3GPP TS 43.064). + +A mobile station in EC operation shall start timer T3200 following the receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message such that the mobile station still does not have the complete RLC/MAC control message. + +On receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message such that the mobile station still does not have the complete RLC/MAC control message, the mobile station shall restart the corresponding instance of timer T3200. + +On receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message such that the mobile station now has the complete RLC/MAC control message, the mobile station shall stop the corresponding instance of timer T3200. + +If the mobile station discards a partially received RLC/MAC control message while the corresponding instance of timer T3200 is running, the mobile station shall stop the corresponding instance of timer T3200. + +On expiry of an instance of timer T3200, the mobile station shall discard and ignore all segments of the corresponding partially received RLC/MAC control message. + +Upon successful change of PDCH allocation, the mobile station shall discard all partially received RLC/MAC control messages and stop the corresponding instances of timer T3200. + +The mobile station shall discard any control message segment that contains an unknown TFI. + +## 9.1.13 Priority of upper layer PDUs + +The mobile station shall not transmit upper layer PDUs during a TBF that have a lower Radio Priority than the priority that was used at initial access or the priority sent in the last PACKET RESOURCE REQUEST message, except if the upper layer PDUs at the higher Radio Priority does not completely fill the RLC data block (see sub-clause 8.1.1.1.2). The mobile station may change the Radio Priority of an uplink TBF by sending a PACKET RESOURCE REQUEST message to the network (see sub-clause 8.1.1.1.2). + +## 9.1.14 Fast Ack/Nack Reporting + +### 9.1.14.1 General + +The Fast Ack/Nack reporting procedure (FANR) allows to piggy-back, within EGPRS RLC/MAC blocks for data transfer sent in one direction, the acknowledgement status of data blocks relative to a TBF in the opposite direction. The acknowledgement status is provided with a Piggy-backed Ack/Nack (PAN) field of which the presence within an EGPRS RLC/MAC block for data transfer is indicated with the PANI field within the RLC/MAC header of that block, see sub-clause 10.4.21. + +The activation of FANR for a given TBF is signalled by the network at TBF establishment/reconfiguration. The mobile station shall proceed as follows: + +- If a downlink TBF is established or reconfigured with FANR activated (see sub-clauses 11.2.7, 11.2.7a, 11.2.31, and 11.2.31a), the mobile station shall act upon sub-clauses 9.1.14.2 and 9.1.14.3. The mobile station shall always use the SSN-based encoding defined in subclause 9.1.8 to encode the PAN field. The RLC data blocks pertaining to a downlink TBF for which FANR is activated shall always be encoded using the relevant RLC/MAC header form specified in sub-clause 10.3a.3 (i.e. PANI and CES/P fields present) irrespective of the existence of a concurrent TBF in the uplink direction. +- If an uplink TBF is established or reconfigured with FANR activated (see sub-clauses 11.2.29, 11.2.29a, 11.2.31, and 11.2.31a), the mobile station shall monitor for the presence of a PAN field for this TBF on all downlink PDCHs on which it shall monitor the USF for this TBF. The mobile station shall only attempt to decode a PAN field in a downlink EGPRS RLC/MAC block for data transfer if it is already required to check for a USF within + +that RLC/MAC block. If the presence of a PAN field is indicated in the header of an EGPRS RLC/MAC block for data transfer received on these PDCHs, the mobile station shall attempt to decode the PAN field also in the blocks addressed to other mobile stations. The network may encode the PAN field according to the SSN-based encoding defined in subclause 9.1.8 or the time-based encoding defined in subclause 9.1.15. The specific encoding selected by the network is notified to the mobile station at TBF establishment/reconfiguration (see subclauses 11.2.29, 11.2.29a, 11.2.31, and 11.2.31a) and, if multiple TBFs procedures are supported, it shall be the same for all the uplink TBF of the same mobile station. The decision for transmitting a PAN field by the network is implementation specific. + +- If the PAN is addressed to a different mobile station than the one to which the data in the RLC/MAC block carrying the PAN is addressed, the same restrictions for the network's selection of the modulation and coding scheme apply as for the USF transmission to this MS, see sub-clause 5.2.4a (except for MCS-4 and MCS-9 which cannot carry a PAN). + +NOTE 1: FANR is supported only on full-rate PDCH and PDCH-pair. + +NOTE 2: If the network does not have any EGPRS RLC/MAC blocks for data transfer in downlink direction but a downlink PAN field is available for transmission to a mobile station operating in A/Gb mode, the network may use an LLC UI Dummy command (see 3GPP TS 44.064) to create an EGPRS RLC/MAC data block where the PAN field available for transmission can be sent. + +NOTE 3: FANR can be activated for a TBF operated in RLC unacknowledged mode. + +The network shall activate FANR for any assigned TBF which uses an RTTI or MTI configuration. + +### 9.1.14.2 Polled Fast Ack/Nack Reporting + +Polled FANR may be used together with event-based FANR (see sub-clause 9.1.14.3). + +If the RLC endpoint transmitter is the network and the mobile station has at least one concurrent TBF in the uplink direction, the network may poll the mobile station to trigger the FANR procedure. In this case the mobile station shall answer in a reserved radio block period which is allocated with the polling as described in sub-clause 8.1.2.2. + +In the case where the network polls for a PAN and the mobile station does not transmit a PAN (e.g. because it does not have any EGPRS RLC/MAC blocks for data transfer in the uplink direction, all the elements of V(B) have the value TENTATIVE\_ACK or ACKED, does not have any TBF assigned in the uplink direction or does not have an uplink TBF that has been assigned a PDCH corresponding to the downlink PDCH where the poll was received or a PDCH-pair corresponding to the downlink PDCH-pair where the poll was received), the mobile station shall transmit an EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing NPB, see sub-clause 10.4.4b. + +### 9.1.14.3 Event-based Fast Ack/Nack Reporting + +Event-based FANR may be used together with Polled FANR (see sub-clause 9.1.14.2). + +If the RLC endpoint receiver is the mobile station, event-based FANR is enabled for this TBF and the mobile station has at least one assigned TBF in the uplink direction, the mobile station shall insert one PAN field in an EGPRS RLC/MAC block for data transfer transmitted during a given radio block period for that uplink TBF if the state of any element in the receive state array V(N) is UNREPORTED and that element will not otherwise be reported (e.g. in response to a poll) during the radio block period. In addition, the mobile station may insert one PAN field in an EGPRS RLC/MAC block for data transfer transmitted during a given radio block period even if that element will be reported in response to a poll during the radio block period. + +The mobile station may continue to insert PAN fields in subsequent EGPRS RLC/MAC data blocks sent in the same radio block period as long as there exists one or more elements in the receive state array V(N) whose state is UNREPORTED. + +If event-based FANR is enabled and the network polls the mobile station, the mobile station shall transmit, in the reserved radio block period which is allocated with the polling, one of the messages as described in sub-clause 8.1.2.2. + +If the mobile station does not have any RLC data block waiting for the transmission, the mobile station shall transmit an EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS + +PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing NPB. + +In case of multiple-TBF allocation or if multiple RLC entities are multiplexed within a single TBF by means of EMST, a mobile station shall insert a PAN field indicating unreported erroneous RLC data blocks from TBFs, or in case of EMST, from an RLC entity in RLC non-persistent mode prior to a PAN field indicating unreported erroneous RLC data blocks from TBFs, or in case of EMST, from an RLC entity in RLC acknowledged mode. + +## 9.1.15 Time-based encoding of the Piggy-backed Ack/Nack field + +### 9.1.15.1 Generation of the bitmap + +When the time-based encoding is used (see sub-clause 9.1.14.1), the Piggy-backed Ack/Nack (PAN) field included in a radio block transmitted by the network in a given basic (respectively reduced) radio block period shall contain a bitmap providing feedback information relative to the reception of radio blocks in basic (respectively reduced) TTI configuration at the network side, possibly from different mobile stations, in the previous basic (respectively reduced) radio block periods on a number of uplink PDCHs (respectively PDCH-pairs). + +The network shall indicate at TBF establishment/reconfiguration (see sub-clauses 11.2.29, 11.2.29a, 11.2.31, and 11.2.31a) the timeslots for which feedback is provided and the time-shift TSH (expressed in number of TDMA frames) between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent. If the TBF operates in RTTI configuration or MTI configuration, feedback shall be provided for an even number of timeslots (see sub-clause 12.18). + +A variable number (between 1 and 3) of bits are used in the PAN field to notify the status of every reported radio block, as described in Table 9.1.15.1.1. For modulation and coding schemes where two RLC data blocks are transmitted within a single radio block, there is one RLC data block per "RLC data block group". For modulation and coding schemes where three RLC data blocks are transmitted within a single radio block, the first "RLC data block group" contains the first RLC data block and the second "RLC data block group" contains the second and third RLC data blocks. For modulation and coding schemes where four RLC data blocks are transmitted within a single radio block, the first "RLC data block group" contains the first two RLC data blocks and the second "RLC data block group" contains the third and fourth RLC data blocks. An RLC data block group containing two RLC data blocks shall be indicated as having been successfully decoded only if both constituent RLC data blocks have been successfully decoded. + +**Table 9.1.15.1.1: Feedback information for every reported radio block** + +| Bit string | Meaning (radio block contains one RLC block) | Meaning (radio block contains two or more RLC blocks) | +|------------|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 0 1 0 | failed header decoding | - failed header decoding
- header correctly received but failed decoding of the payload of both RLC data block groups | +| 0 0 | header correctly received but failed decoding of the payload of the RLC data block | header correctly received, successful decoding of the first RLC data block group, failed decoding of the second RLC data block group | +| 0 1 1 | reserved | header correctly received, successful decoding of the second RLC data block group, failed decoding of the first RLC data block group | +| 1 | header correctly received and successful decoding of the payload of the RLC data block | header correctly received and successful decoding of the payload of both RLC data block groups | + +For a PAN field transmitted in a given basic (respectively reduced) radio block starting with TDMA frame N, the first code in the bitmap shall refer to the radio block received on the first reported uplink PDCH (respectively PDCH-pair) starting with TDMA frame (N-TSH or N-TSH-1) mod 2715648, the second code shall refer to the radio block received on the second reported uplink PDCH (respectively PDCH-pair) starting with TDMA frame (N-TSH or N-TSH-1) mod 2715648, etc. If there is still space in the PAN field, then the next code shall refer to the radio block received on the first reported uplink PDCH (respectively PDCH-pair) starting with TDMA frame (N-TSH-4 or N-TSH-5) mod 2715648 for TBFs in basic TTI configuration (respectively TDMA frame (N-TSH-2 or N-TSH-3) mod 2715648 for TBFs in reduced TTI configuration) and so on. + +In a PAN field included in a radio block transmitted in basic (respectively reduced) TTI configuration, the network shall include a bit string as specified in Table 9.1.15.1.1 for every PDCH (respectively PDCH-pair) covered by the report, even if no uplink radio block in basic (respectively reduced) TTI configuration was scheduled to be transmitted on that PDCH/PDCH-pair. + +NOTE: For a PAN field included in a radio block transmitted in basic (respectively reduced) TTI configuration, bit strings shall be included in the positions corresponding to PDCHs (respectively PDCH-pairs) on which radio blocks in reduced (respectively basic) TTI configuration were scheduled. + +In the case of a PAN field received within an RTTI block by a mobile station with an uplink MTTC configuration (see sub-clause 7.1.3.7) and which covers both the PDCH and one or more PDCH-pairs for that MTTC configuration, the network shall include the applicable bit string for the BTTI radio block in the first of the two positions which would otherwise be used for reporting the status of two uplink RTTI radio blocks sent using a PDCH-pair that includes that PDCH. + +In the case of a PAN field received within a BTTI block by a mobile station with an uplink MTTC configuration (see sub-clause 7.1.3.7) and which covers both the PDCH and one or more PDCH-pairs for that MTTC configuration, the network shall include the applicable bit string for the later (respectively earlier) RTTI radio block in the first (respectively second) of the two positions which would otherwise be used for reporting the status of two uplink BTTI radio blocks sent using the PDCHs that comprise the PDCH-pair being reported. + +If necessary, the PAN field may be padded using either one or two bits. If one bit of padding is required, then a '0' shall be used. If two bits is required, the bit string '0 1' shall be used. + +## 9.1.15.2 Interpretation of the bitmap + +If the time-based encoding is used, when a mobile station successfully decodes a PAN field in a radio block transmitted in basic (respectively reduced) TTI configuration it correlates the received feedback information, which may refer to the transmission of different mobile stations, with the knowledge of the RLC data blocks (i.e. the BSNs) it transmitted in a given basic (respectively reduced) radio block period on a given uplink PDCH (respectively PDCH-pair) during the time window covered by the PAN field. The mobile station shall then derive which RLC data blocks were correctly received or not by the network in that time window. In case of multiple TBFs in different TTI configurations the mobile station shall not derive any information for TBFs in basic (respectively reduced) TTI configuration from PAN fields included in radio blocks transmitted in reduced (respectively basic) TTI configuration. A mobile station assigned uplink resources in an MTTC configuration (see sub-clause 7.1.3.7) shall derive information for both RTTI radio blocks and BTTI radio blocks which are covered by the PAN field (see sub-clause 9.1.15.1). + +If the final bit(s) in the bitmap do not correspond to any valid bitstring as specified in sub-clause 9.1.15.1, these bits shall be ignored. + +Where it is indicated that the decoding of an RLC data block group failed, and that RLC data block group contained two RLC data blocks, then the mobile station shall consider that the decoding of both RLC data blocks failed. + +For the RLC data blocks correctly received the corresponding elements in V(B) shall be set to the value ACKED. + +For each RLC data block not correctly received the corresponding element in V(B) shall be set to the value NACKED, if the number of basic (respectively reduced) radio block periods between the end of the radio block period used for the last transmission of the corresponding RLC data block and the beginning of the radio block period containing the PAN field is higher or equal than $(TSH/4)-1$ for TBFs in basic TTI configuration (respectively $(TSH/2)-1$ for TBFs in reduced TTI configuration), i.e. the RLC data block was not recently (re)transmitted and thus can be validly negatively acknowledged by this particular PAN field, otherwise the corresponding element in V(B) shall not be modified. + +## 9.2 Operation during RLC/MAC control message transfer + +RLC/MAC control blocks shall be used to transport RLC/MAC control messages. Segments of only one RLC/MAC control message shall be transported per RLC/MAC control block. + +RLC/MAC control blocks shall be sent at a higher priority than RLC data blocks. + +The receiving side shall determine the length of the RLC/MAC control message contents by interpreting the RLC/MAC control block contents. + +No general acknowledgement shall be made as part of the transfer of RLC/MAC control blocks or RLC/MAC control messages. The receiver shall not acknowledge an RLC/MAC control block except when a valid RRBP field is present in + +the MAC header of the RLC/MAC control block. The receiver shall not acknowledge an RLC/MAC control message except when the RLC/MAC procedures explicitly specify an acknowledgement. + +Each downlink RLC/MAC control block header, if present, contains a Radio Transaction Identifier (RTI) field that is 5 bits in length and performs in effect a modulo 32 count of the downlink RLC/MAC control messages sent on a PDCH. The RTI field shall be used to group the RLC/MAC control blocks that make up an RLC/MAC control message. The RTI field allows the transmitting and receiving entities to distinguish between up to 32 RLC/MAC control messages in a single transmit direction therefore allowing up to 32 parallel transactions per PDCH. + +The network shall not use the same RTI value at the same time on the same PDCH for two separate RLC/MAC control messages. The network may use the same RTI value at the same time on separate PDCHs. The network shall transmit all segments of a segmented control message on the same PDCH. + +## 9.3 Operation during RLC data block transfer + +### 9.3.0 General + +The RLC ARQ functions support three modes of operation: RLC acknowledged mode, RLC unacknowledged mode and RLC non-persistent mode. RLC acknowledged mode operation uses retransmission of RLC data blocks to achieve high reliability. RLC unacknowledged mode operation does not utilize retransmission of RLC data blocks. RLC non-persistent mode operation uses non-exhaustive retransmission of RLC data blocks. A TBF may operate in either RLC acknowledged mode, RLC unacknowledged mode or RLC non-persistent mode. An MBMS bearer operates in RLC non-persistent mode. An EC TBF operates in RLC acknowledged mode. + +A mobile station, which has not enabled EC operation, requests the RLC mode of the uplink TBF by setting the RLC\_MODE bit to either RLC acknowledged mode or RLC unacknowledged mode in the PACKET RESOURCE REQUEST or the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or the EGPRS PACKET DOWNLINK ACK/NACK DLMC message. When the establishment cause field in the PACKET CHANNEL REQUEST message indicates 'one phase access', the RLC mode defaults to RLC acknowledged mode. If both the mobile station and the BSS support multiple TBF procedures, or if the mobile station supports RLC non-persistent mode, the BSS may override the mobile station's indicated RLC mode, ordering its preferred RLC mode (including RLC non-persistent mode for EGPRS TBF(s), if the mobile station supports this RLC mode) when establishing uplink TBF(s) as follows: + +- The network shall always set the RLC\_MODE bit for the uplink TBF(s) in the MULTIPLE TBF UPLINK ASSIGNMENT and MULTIPLE TBF TIMESLOT RECONFIGURE messages. +- The network may order the RLC mode for the uplink TBF by setting the RLC\_MODE bit in the PACKET UPLINK ASSIGNMENT message or the UPLINK\_RLC\_MODE bit in the PACKET TIMESLOT RECONFIGURE message. The mobile station shall assume that its indicated RLC mode is used if the BSS does not override it in the PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message. + +The network sets the RLC mode of the downlink TBF by setting the RLC\_MODE bit in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message. + +An uplink TBF may be operating in either non-extended uplink TBF mode or extended uplink TBF mode, see sub-clause 9.3.1b. An uplink TBF operating in RLC non-persistent mode shall operate in extended uplink TBF mode. + +The extended uplink TBF mode is not applicable for an uplink EC TBF. The use of the Countdown Value (CV) is instead optional in an uplink EC TBF and it may be used to prolong the TBF, see sub-clause 9.3.1.4. The CV shall however always be included for the last uplink RLC data block of the uplink EC TBF. + +When one or more PDCH/Fs are used in conjunction with one PDCH/H in the same direction, the RLC/MAC data blocks may not be received in the same sequence they were sent, due to the different data rates of the channels. In RLC unacknowledged mode, the sending entity shall re-order the RLC/MAC data blocks before transmission to ensure their reception in sequence. + +## 9.3.1 Countdown procedure + +### 9.3.1.1 General + +The mobile station shall send the Countdown Value (CV) in each uplink RLC data block to indicate the current number of remaining RLC data blocks for the uplink TBF, except for an uplink EC TBF. In case EMST is used, the CV shall indicate the current number of remaining RLC data blocks for the corresponding RLC entity allocated to the uplink TBF. + +A mobile station with an uplink EC TBF is only required to send the Countdown Value (CV) in an uplink RLC data block in order to inform the network that there are more remaining RLC data blocks for the uplink TBF than it has previously signalled to the network. The mobile station is also required to send the CV in the last uplink RLC data block of the TBF. The Follow-On Indication (FOI) shall then be set to '1' to indicate the presence of the CV. + +The CV for a non EC TBF shall be calculated as follows: + +where: + +- TBC = total number of RLC data blocks currently to be transmitted in the TBF. +- BSN' = absolute block sequence number of the RLC data block, with range from 0 to (TBC - 1). +- NTS = number of timeslots assigned to the uplink TBF in the assignment message, with range 1 to 8 when operating in BTTI configuration. In RTTI configuration this parameter shall be equal to the number of assigned uplink PDCH pairs, with the range 1 to 4. In an MTI configuration, the parameter shall be equal to the number of uplink BTTI PDCHs assigned plus twice the number of RTTI PDCH-pairs assigned, with the range 3 to 7. +- K = 2 when commanded MCS is MCS-7, MCS-8, MCS-9, UAS-7, UAS-8, UAS-9, UBS-7 or UBS-8 +3 when commanded UAS-10, UAS-11, UBS-9 or UBS-10 +4 when commanded UBS-11 or UBS-12 otherwise K=1, +the function round() rounds upwards to the nearest integer. +- BS\_CV\_MAX is a parameter broadcast in the system information, +the division operation is non-integer and results in zero only for (TBC - BSN' - 1) = 0. + +The CV for an uplink EC TBF is calculated as follows: + +where: + +- TBC = total number of RLC data blocks currently to be transmitted in the TBF. +- BSN' = absolute block sequence number of the RLC data block, with range from 0 to (TBC - 1). +- K = 2 when commanded MCS is MCS-7, MCS-8 or MCS-9 +otherwise K=1, +the function round() rounds upwards to the nearest integer. + +The countdown procedure, for a non EC TBF, starts when RLC data blocks include CV values different from '15'. When the mobile station transmits the last RLC data block currently in the send buffer for the TBF (i.e. the RLC data block with BSN' = TBC - 1), the RLC data block shall have CV set to the value '0'. + +When an EGPRS, EGPRS2 or EC-GSM-IoT RLC/MAC block for data transfer consists of two or more RLC data blocks, a CV value is calculated for each block and the CV of the RLC/MAC header refers to the last RLC data block. + +### 9.3.1.2 Non-extended uplink TBF mode + +In an uplink TBF operating in non-extended uplink TBF mode, the CV shall indicate the absolute BSN (BSN') of the last RLC data block that will be sent in the uplink TBF. The TBC value is the total number of RLC data blocks that will be transmitted in the TBF. + +At the point in time the mobile station having an uplink TBF in non-extended TBF mode transmits the first RLC data block indicating a CV other than 15, the mobile station shall transmit afterwards exactly (TBC - BSN' - 1) untransmitted RLC data blocks. + +If the mobile station receives a change in the Channel Coding Command in a PACKET UPLINK ACK/NACK message during the countdown procedure, the mobile station shall act upon the new Channel Coding Command. The mobile station shall then recalculate the CV for any untransmitted RLC data block using the new RLC data block size. + +If the mobile station successfully completes the contention resolution procedure during one phase access and the countdown procedure is already running,, the mobile station shall recalculate the CV for any untransmitted RLC data blocks. + +Any data that arrives from the higher layer after the commencement of the countdown process shall be sent within a future TBF. + +The mobile station may retransmit during the countdown in response to a Packet Ack/Nack or if stalled. + +If the mobile station receives a new allocation during the countdown, the mobile station shall use this new allocation to the end of the countdown procedure. The network shall provide unsolicited uplink resources for any retransmissions that may be required. + +### 9.3.1.3 Extended uplink TBF mode + +In an uplink TBF operating in extended uplink TBF mode, the CV shall indicate the current number of RLC data blocks that has not been transmitted in the uplink TBF. The mobile station shall update the TBC value and recalculate the CV for any untransmitted RLC data block in the following cases: + +- The RLC entity of the mobile station receives new data from upper layers for transmission in the uplink TBF. +- The mobile station completes the contention resolution at one-phase packet access. +- The mobile station changes the coding scheme of the RLC data blocks transmitted in an uplink TBF operating in GPRS TBF mode. +- The mobile station changes the modulation and coding scheme of the RLC data blocks transmitted in an uplink TBF operating in EGPRS TBF mode. + +NOTE: Updating the TBC value shall not result in changing the CV of the RLC data blocks already transmitted, in the case they need to be retransmitted. + +### 9.3.1.4 End of uplink EC TBF + +An uplink EC TBF is released when the network has received all RLC data blocks for a TBF, as indicated by the mobile station, and sent the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1'. An exception is when the mobile station, in the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', is ordered to continue monitoring the EC-PACCH, see sub-clause 9.3.2.4.3. + +The end of the uplink TBF is indicated by the mobile station by inclusion of a block count indicating a specific number data blocks to be sent for the TBF in the EC Packet Channel Request message or by inclusion of the Countdown Value (CV) in the RLC/MAC header of one or several of the uplink RLC data blocks that are sent within the TBF. The mobile station indicates the presence of a valid CV field in the RLC/MAC header by setting the FOI field to '1'. The end of the uplink EC TBF, i.e. the absolute BSN (BSN') of the last RLC data block that will be sent in the TBF, shall be indicated by the mobile station by including the CV field in the first possible uplink RLC data block to be transmitted, in case the EC Packet Channel Request message did not indicate a specific number data blocks to be sent. The CV field shall be included, set to the value '0', in the last RLC data block of the TBF. + +The mobile station may prolong the uplink TBF by including a CV that indicates a later end of the TBF than previously indicated, unless CV=0 has already been indicated in an uplink RLC data block. If the network receives several uplink RLC data blocks with CV pointing at different end points for the TBF, the CV of the newest uplink RLC data block, i.e. with the highest absolute BSN (BSN'), shall be considered valid. + +In case the end of the uplink TBF, i.e. the absolute BSN (BSN') of the last RLC data block that will be sent in the TBF, is changed compared to the most recent indication, e.g. due to that a different Modulation and Coding Scheme (MCS) than previously used has been commanded for the TBF, the mobile station shall include the CV at the first possible occasion to indicate the end of the TBF. + +If the mobile station receives a change in the Channel Coding Command in an EC PACKET UPLINK ACK/NACK message, the mobile station shall act upon the new Channel Coding Command and recalculate the CV for any untransmitted RLC data block using the new RLC data block size. + +If the mobile station successfully completes the contention resolution procedure and the end of the uplink TBF has already been indicated to the network, as an absolute BSN (BSN') of the last RLC data block that will be sent in the TBF, the mobile station shall recalculate the CV for any untransmitted RLC data blocks. + +### 9.3.1a Delayed release of downlink Temporary Block Flow + +When the network exhausts its supply of downlink data for a downlink TBF, it may release the TBF by using one of the procedures in sub-clause 9.3.2.6 or sub-clause 9.3.3.5. If a TBF is not instantly released, the network may continue the downlink TBF awaiting new data to be received from the upper layers. After a period of inactivity, the TBF shall be released at a point determined by the network, using one of the procedures in sub-clause 9.3.2.6, sub-clause 9.3.3.5 or sub-clause 8.1.2.8. Once the release of a downlink TBF is initiated, the TBF shall not be continued. + +If the network continues a downlink TBF when the supply of downlink data is exhausted, the RLC entity on the network side shall insert filler information into the RLC data blocks that are transmitted to the mobile station. For a mobile station operating in *A/Gb mode*, this is achieved by the insertion of LLC UI Dummy commands (see 3GPP TS 44.064) into the TBF. For a mobile station operating in *Iu mode*, the network may directly transmit RLC data blocks with filler information by setting the LI field as described in sub-clauses 10.4.14 and 10.4.14a. The FBI bit in the RLC header shall be set to the value '0' unless the network releases the TBF, in which case the FBI bit shall be set to the value 1. + +If new data is received from the upper layers, the network stops sending filler information and resumes normal operation during RLC data block transfer. + +RLC data blocks shall be sent to the mobile station as required to prevent the expiry of timer T3190 for each TBF, according to power control requirements, and as needed to poll the mobile station for the provision of (EC-)PACCH uplink blocks. + +NOTE: Extensive delay of a downlink TBF release might impact badly on the mobile station power consumption and should be avoided. Inactivity periods should not be longer than necessary to keep the overall performance of GPRS services. Inactivity periods longer than 5 s should not be used unless the DTR mode is used, see sub-clause 8.1.8. + +### 9.3.1b Extended uplink TBF mode + +#### 9.3.1b.1 Application + +Network support of the extended uplink TBF mode shall be indicated by the NW\_EXT\_UTBF parameter that is broadcast on either BCCH or PBCCH, see sub-clause 12.24. A network which supports RLC non-persistent mode shall support extended uplink TBF mode. A network which supports Enhanced Flexible Timeslot Assignment, EFTA, shall support extended uplink TBF mode. + +The mobile station shall support the extended uplink TBF mode. The extended uplink TBF mode is a part of the *GERAN Feature Package 1*. A mobile station indicating support of *GERAN Feature Package 1* in the Mobile Station Classmark 3 IE, the MS Radio Access Capability IE and the MS Radio Access Capability 2 IE supports the extended uplink TBF mode (see 3GPP TS 24.008). + +Extended uplink TBF mode is not supported in EC-GSM-IoT. + +The RLC/MAC entity, which has received the indication that the peer supports the extended uplink TBF mode, shall operate an uplink TBF in the extended uplink TBF mode. + +NOTE: The network might not receive the radio access capabilities of the mobile station at one-phase packet access. In that case, the two entities may operate in different mode. + +#### 9.3.1b.2 Operation of uplink TBF in extended uplink TBF mode + +In extended uplink TBF mode, an uplink TBF may be maintained during temporary inactive periods, where the mobile station has no RLC information to send. + +During the temporary inactive periods, the mobile station may stop sending RLC data block, as defined in sub-clause 9.1.3. The network shall continue allocating the mobile station uplink radio blocks during the inactivity period, using the procedures defined in sub-clause 8.1.1 for each medium access mode. Uplink radio blocks shall be allocated as required allowing the mobile station to continue the transfer of RLC data blocks, when a new RLC data block becomes available. + +When the mobile station is allocated an uplink radio block and there is no RLC data block ready to send for any TBF, the mobile station shall send an RLC/MAC control block in each uplink radio block allocated by the network, unless indicated otherwise. When the mobile station is allocated an uplink radio block, and there is no RLC/MAC block for data transfer to send for this TBF but, in case of multiple TBFs, there is an RLC/MAC block for data transfer to send for one or more other TBF(s) assigned on the same PDCH, the mobile station should send an RLC/MAC block for data transfer from one of these other TBF(s) in the allocated uplink radio block indicating the TFI of that other TBF in the RLC/MAC header of that RLC/MAC block. The priorities defined in sub-clause 8.1.1 for different kinds of RLC/MAC blocks apply. The network may allow, via the EXT\_UTBF\_NODATA parameter broadcast in GPRS Cell Options IE (see sub-clause 12.24), any mobile station during extended uplink TBF mode not to send any PACKET UPLINK DUMMY CONTROL BLOCK message when there is no other RLC/MAC block ready to send. A mobile station during extended uplink TBF mode may refrain from sending PACKET UPLINK DUMMY CONTROL BLOCK messages when there is no other RLC/MAC block ready to send only if so indicated by the EXT\_UTBF\_NODATA parameter. + +During a period when the network does not receive any RLC data blocks from the mobile station, the network may periodically send a PACKET UPLINK ACK/NACK message to the mobile station. When applicable, depending on the medium access mode, the PACKET UPLINK ACK/NACK message shall be sent as required to prevent timer T3184 from expiring. + +The network determines the release of an uplink TBF. The network releases an uplink TBF using the procedure in sub-clause 9.5 (*A/Gb mode*). + +NOTE 1: An uplink TBF may be released also by procedures defined in clause 8. + +NOTE 2: Extensive delay of an uplink TBF release whilst the mobile station does not send any RLC information might impact badly on the mobile station power consumption and should be avoided. Inactivity periods should not be longer than necessary to keep the overall performance of GPRS services. Inactivity periods longer than 5 s should not be allowed unless the DTR mode is used, see sub-clause 8.1.8. If, however, the network has indicated that the mobile station during extended uplink TBF mode is not required to send PACKET UPLINK DUMMY CONTROL BLOCK messages, as described above, and the mobile station makes use of this option, the impact on the mobile station power consumption will be less critical and longer inactivity periods than 5 seconds can be allowed. + +NOTE 3: Enhanced Flexible Timeslot Assignment, EFTA, is applicable only if the network has indicated that the mobile station during extended uplink TBF mode is not required to send PACKET UPLINK DUMMY CONTROL BLOCK messages as described above. + +## 9.3.2 Acknowledged mode operation + +### 9.3.2.0 General + +The transfer of RLC data blocks in the RLC acknowledged mode uses retransmissions of RLC data blocks. The transmitting side numbers the RLC data blocks via the block sequence number (BSN). The BSN is used for retransmission and for reassembly. The receiving side sends Packet Ack/Nack messages in order to request retransmission of RLC data blocks. + +### 9.3.2.1 Additional functionality in acknowledged EGPRS TBF Mode + +In EGPRS TBF mode, the transfer of RLC Data Blocks in the acknowledged RLC/MAC mode may be controlled by a selective type I ARQ mechanism, or by type II hybrid ARQ (Incremental Redundancy: IR) mechanism, coupled with the numbering of the RLC Data Blocks within one Temporary Block Flow. + +According to the link quality, an initial Modulation and Coding Scheme (MCS) is selected for an RLC block (see note). For the retransmissions, the same or another MCS from the same family of MCSs may be selected. E.g. if MCS-7 is selected for the first transmission of an RLC block, any MCS of the family B may be used for the retransmissions. Further, RLC data blocks initially transmitted with any MCS other than MCS-1, MCS-2 or MCS-3, may be retransmitted with MCS-1, MCS-2 or MCS-3 as appropriate, by sending the different parts of the RLC data block in + +different radio blocks. In this case, the SPB field in the header shall be set to indicate that the RLC data block is split, and which part of the RLC data block is retransmitted in the radio block. + +For blocks initially transmitted with MCS-8 which are retransmitted using MCS-6 or MCS-3, for blocks initially transmitted with DAS-6, DAS-9, DAS-11 or DBS-11 which are retransmitted using MCS-3 and for blocks initially transmitted with UBS-11 which are retransmitted using UBS-10, UBS-8, UBS-6 or MCS-3, padding with all zeroes of the first six octets shall be applied. For blocks initially transmitted with UAS-8 or UAS-11 which are retransmitted using MCS-6 or MCS-3, padding with all zeroes of the first ten octets shall be applied. For blocks initially transmitted with DAS-7, DAS-10 or DAS-12 which are retransmitted using MCS-2, padding with all zeroes of the first two octets shall be applied. In all of these cases, the CPS and SPB fields shall be set accordingly. However, if the transmitter side is the mobile station and the RESEGMENT bit is not set, the mobile station shall use an MCS within the same family as the initial MCS without splitting the payload (refer to sub-clause 8.1.1, tables 8.1.1.2, 8.1.1.4 and 8.1.1.6) for retransmission. + +In case an RLC data block originally transmitted using MCS-8 is retransmitted using two MCS-3 RLC/MAC blocks, the CPS and SPB fields of the first MCS-3 RLC/MAC block shall indicate MCS-3 with (6 octets) padding, whereas the CPS field of the second MCS-3 RLC/MAC block should indicate MCS-3 without padding. In case an RLC data block originally transmitted using DAS-6, DAS-9, DAS-11, DBS-11 or UBS-11 is retransmitted using two MCS-3 RLC/MAC blocks, the CPS and SPB fields of the first MCS-3 RLC/MAC block shall indicate MCS-3 with (6 octets) padding, whereas the CPS field of the second MCS-3 RLC/MAC block shall indicate MCS-3 without padding. In case an RLC data block originally transmitted using UAS-8 or UAS-11 is retransmitted using two MCS-3 RLC/MAC blocks, the CPS and SPB fields of the first MCS-3 RLC/MAC block shall indicate MCS-3 with (10 octets) padding, whereas the CPS field of the second MCS-3 RLC/MAC block shall indicate MCS-3 without padding. In case an RLC data block originally transmitted using DAS-7, DAS-10 or DAS-12 is retransmitted using three MCS-2 RLC/MAC blocks, the CPS field of the first MCS-2 RLC/MAC block shall indicate MCS-2 with (2 octets) padding whereas the CPS field of the remaining two MCS-2 RLC/MAC blocks shall indicate MCS-2 without padding. + +The selection of MCS is controlled by the network. + +The RLC data blocks shall first be sent with one of the initial code rates (i.e. the rate 1/3 encoded data is punctured with the Puncturing Scheme (PS) 1 of the selected MCS). If the RLC data block needs to be retransmitted, additional coded bits (i.e. the output of the rate 1/3 encoded data which is punctured with PS 2 of the prevailing MCS) shall be sent. If all the codewords (different punctured versions of the encoded data block) have been sent, the procedure shall start over and the first codeword (which is punctured with PS 1) shall be sent followed by PS 2 etc. RLC data blocks which are retransmitted using a new MCS shall at the first transmission after the MCS switch be sent with the puncturing scheme indicated in table 9.3.2.1.1. + +**Table 9.3.2.1.1: RLC data blocks re-transmitted in new MCS** + +| MCS switched from | MCS switched to | PS of last transmission before MCS switch | PS of first transmission after MCS switch | +|------------------------|-----------------|-------------------------------------------|-------------------------------------------| +| MCS-9 | MCS-6 | PS 1 or PS 3 | PS 1 | +| | | PS 2 | PS 2 | +| MCS-6 | MCS-9 | PS 1 | PS 3 | +| | | PS 2 | PS 2 | +| MCS-7 | MCS-5 | any | PS 1 | +| MCS-5 | MCS-7 | any | PS 2 | +| all other combinations | | any | PS 1 | + +This procedure allows the receiver to operate either in type I or type II hybrid ARQ mode. In the type I ARQ mode, decoding of an RLC data block is solely based on the prevailing transmission (i.e. erroneous blocks are not stored). In the type II ARQ case, erroneous blocks are stored by the receiver and a joint decoding with new transmissions is done. If the memory for IR operation run out in the mobile station, the mobile station shall indicate this by setting the MS OUT OF MEMORY bit in the EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3, EGPRS PACKET DOWNLINK ACK/NACK DLMC or MBMS DOWNLINK ACK/NACK message (see note). For uplink TBFs, the network may implicitly set the type I mode by ordering the mobile station to use a specific MCS and setting the RESEGMENT bit or type II mode by ordering the mobile station to use a specific MCS and not setting the RESEGMENT bit. + +Type II hybrid ARQ is mandatory in EGPRS MS receivers and the associated performance requirements are specified in 3GPP TS 45.005. Furthermore, it is mandatory for an EGPRS MS receiver to be able to perform joint decoding among blocks with different MCSs if the combination of MCSs is one of the following: + +- MCS-5 and MCS-7; +- MCS-6 and MCS-9. + +Additionally if the mobile station supports EGPRS2-A in the downlink, it is mandatory for the mobile station to be able to perform joint decoding among blocks with different MCSs if the combination of MCSs is one of the following: + +- DAS-5 and DAS-8; +- DAS-6, DAS-9 and DAS-11; +- DAS-7, DAS-10 and DAS-12; + +and if the mobile station supports EGPRS2-B in the downlink, it is mandatory for the mobile station to be able to perform joint decoding among blocks with different MCSs if the combination of MCSs is one of the following: + +- DBS-5, DBS-7, DBS-9, DAS-5 and DAS-8; +- DBS-6, DBS-8, DBS-10 and DBS-12; +- DBS-11, DAS-6, DAS-9 and DAS-11. + +NOTE: The MCS selection may take the IR capability of the receiver into account, for example by using a less robust MCS for a given channel quality. + +### 9.3.2.1a Additional functionality in acknowledged EC TBF Mode + +In EC TBF mode, the transfer of RLC Data Blocks in the acknowledged RLC/MAC mode may be controlled by a selective type I ARQ mechanism, or by type II hybrid ARQ mechanism, coupled with the numbering of the RLC Data Blocks within one Temporary Block Flow. + +A limited number of puncturing schemes is supported in EC TBF mode compared to EGPRS TBF mode. Only one puncturing scheme (PS 1) is used for MCS-1 and MCS-2 and only two puncturing schemes (PS 1 and PS 2) are used for MCS-3 and MCS-4. + +According to the link quality, an initial Modulation and Coding Scheme (MCS) is selected for an RLC block (see note). For the retransmissions, the same or another MCS from the same family of MCSs may be selected. E.g. if MCS-7 is selected for the first transmission of an RLC block, any MCS of the family B may be used for the retransmissions. Further, RLC data blocks initially transmitted with any MCS other than MCS-1, MCS-2 or MCS-3, may be retransmitted with MCS-1, MCS-2 or MCS-3 as appropriate, by sending the different parts of the RLC data block in different radio blocks. In this case, the SPB field in the header shall be set to indicate that the RLC data block is split, and which part of the RLC data block is retransmitted in the radio block. + +For blocks initially transmitted with MCS-8 which are retransmitted using MCS-6 or MCS-3, padding with all zeroes of the first six octets shall be applied. In these cases, the CPS and SPB fields shall be set accordingly. However, if the transmitter side is the mobile station and the RESEGMENT bit is not set, the mobile station shall use an MCS within the same family as the initial MCS without splitting the payload (refer to sub-clause 8.1.1 and table 8.1.1.2) for retransmission. + +In case an RLC data block originally transmitted using MCS-8 is retransmitted using two MCS-3 RLC/MAC blocks, the CPS and SPB fields of the first MCS-3 RLC/MAC block shall indicate MCS-3 with (6 octets) padding, whereas the CPS field of the second MCS-3 RLC/MAC block should indicate MCS-3 without padding. + +The selection of MCS is controlled by the network. Only MCS-1 shall be used when the assigned Coverage Class > CC1. + +The RLC data blocks shall first be sent with one of the initial code rates (i.e. the rate 1/3 encoded data is punctured with the Puncturing Scheme (PS) 1 of the selected MCS). If the RLC data block was sent with an MCS of MCS-3 or higher and needs to be retransmitted, additional coded bits (i.e. the output of the rate 1/3 encoded data which is punctured with PS 2 of the prevailing MCS) shall be sent. If all the codewords (different punctured versions of the encoded data block) have been sent, the procedure shall start over and the first codeword (which is punctured with PS 1) shall be sent followed by PS 2 etc. + +If the RLC data block was sent with MCS-1 or MCS-2 and needs to be retransmitted, the retransmissions shall be performed with the same puncturing scheme as the initial transmission (PS 1). + +RLC data blocks which are retransmitted using a new MCS shall at the first transmission after the MCS switch be sent with the puncturing scheme indicated in table 9.3.2.1a.1. + +**Table 9.3.2.1a.1: RLC data blocks re-transmitted in new MCS** + +| MCS switched from | MCS switched to | PS of last transmission before MCS switch | PS of first transmission after MCS switch | +|------------------------|-----------------|-------------------------------------------|-------------------------------------------| +| MCS-9 | MCS-6 | PS 1 or PS 3 | PS 1 | +| | | PS 2 | PS 2 | +| MCS-6 | MCS-9 | PS 1 | PS 3 | +| | | PS 2 | PS 2 | +| MCS-7 | MCS-5 | any | PS 1 | +| MCS-5 | MCS-7 | any | PS 2 | +| all other combinations | | any | PS 1 | + +This procedure allows the receiver to operate either in type I or type II hybrid ARQ mode. In the type I ARQ mode, decoding of an RLC data block is solely based on the prevailing transmission (i.e. erroneous blocks are not stored). In the type II ARQ case, erroneous blocks are stored by the receiver and a joint decoding with new transmissions is done. If the memory for IR operation runs out in the mobile station, the mobile station shall indicate this by setting the MS OUT OF MEMORY bit in the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC (see note). For uplink TBFs, the network may implicitly set the type I mode by ordering the mobile station to use a specific MCS and setting the RESEGMENT bit or type II mode by ordering the mobile station to use a specific MCS and not setting the RESEGMENT bit. + +Type II hybrid ARQ is mandatory for EC-GSM-IoT capable MS receivers and the associated performance requirements are specified in 3GPP TS 45.005 [30]. Furthermore, it is mandatory for an EC-GSM-IoT capable MS receiver that supports 8-PSK modulation to be able to perform joint decoding among blocks with different MCSs if the combination of MCSs is one of the following: + +- MCS-5 and MCS-7; +- MCS-6 and MCS-9. + +NOTE: The MCS selection may take the IR capability of the receiver into account, for example by using a less robust MCS for a given channel quality. + +### 9.3.2.2 Establishment of Temporary Block Flow + +The establishment of a TBF occurs as described in clause 7 and clause 8. RLC functions related to the ARQ function shall not operate until RLC data block transfer has been initiated. + +If the last uplink TBF ended with an incompletely transmitted upper layer PDU or any unacknowledged upper layer PDUs, the mobile station shall begin transmission on the new TBF with the oldest unacknowledged upper layer PDU. + +### 9.3.2.3 Operation of uplink Temporary Block Flow + +The mobile station shall transmit an RLC/MAC block in each assigned uplink data block. RLC/MAC control blocks have preference to RLC data blocks, i.e. temporarily replacing the PDTCH with PACCH, except for an uplink EC TBF, for which EC-PACCH blocks shall not replace EC-PDTCH blocks. + +The network shall send (EC) PACKET UPLINK ACK/NACK messages when needed. + +The mobile station shall indicate a transmit window stall condition when $V(S) = V(A) + WS$ . Upon detecting a transmit window stall condition, the mobile station shall set the Stall indicator (SI) bit in all subsequent uplink RLC data blocks for this TBF, or if EMST is used, for the associated RLC entity, until the stall condition ceases to exist. An exception is the case of a mobile station using an EC TBF where the Stall indicator (SI) is not supported. + +Upon detecting the stall condition the mobile station shall also start timer T3182 for the TBF, or if EMST is used, for the associated RLC entity. Timer T3182 shall be stopped upon reception of a PACKET UPLINK ACK/NACK message + +that makes $V(S) < V(A) + WS$ . If timer T3182 expires, the mobile station shall decrement counter N3102 by PAN\_DEC, and proceed as follows: + +- If there are no other ongoing uplink TBFs and one or no ongoing downlink TBFs perform an abnormal release with access retry (see sub-clause 8.7.2) (*A/Gb mode*). +- If there are one or more other ongoing uplink TBFs or multiple ongoing downlink TBFs, perform a multiple TBF abnormal release with access retry (see sub-clause 8.7.4). + +Whenever the mobile station receives a PACKET UPLINK ACK/NACK message that allows the advancement of $V(S)$ or $V(A)$ , the mobile station shall increment N3102 by PAN\_INC, however N3102 shall never exceed the value PAN\_MAX. Upon cell reselection the mobile station shall set counter N3102 to the value PAN\_MAX. When $N3102 \leq 0$ is reached, the mobile station shall perform an abnormal release with cell re-selection (see sub-clause 9.4.2). If PAN\_DEC or PAN\_INC is set to the value 0, counter N3102 shall be disabled. + +Timer T3182 and counter N3102 shall not be used in EC TBF mode. A mobile station in EC TBF mode shall, if it in a fixed uplink allocation is allocated additional resources to what is needed to transmit each RLC data block within the transmit window, perform pre-emptive retransmission in those additional resources (see sub-clause 9.1.3.4). + +A mobile station operating with an exclusive allocation shall start or restart timer T3184 upon reception of a PACKET UPLINK ACK/NACK message. If timer T3184 expires, the mobile station shall perform an abnormal release with access retry (see sub-clause 9.4.2). + +If a mobile station with an uplink EC TBF, while monitoring the downlink EC-PACCH, receives an RLC/MAC block containing RLC data blocks (thus not intended for the mobile station), it may use the Coverage Class (CC) field in the RLC data block header, if present, to determine that it may avoid listening to the EC-PACCH while repetitions of the ongoing transmission (for a higher Coverage Class to another mobile station) are being transmitted. If the mobile station receives an RLC/MAC block, which is an RLC/MAC control message on the EC-PACCH, which is not addressed to the mobile station, it may use the USED\_DL\_COVERAGE\_CLASS information in the message to determine that it may avoid listening to the EC-PACCH while repetitions of the ongoing transmission (for a higher Coverage Class to another mobile station) are being transmitted. + +If a mobile station with an uplink EC TBF receives an RLC/MAC control message addressed to it on the EC-PACCH, it shall accept the message even if the USED\_DL\_COVERAGE\_CLASS information in the message indicates a different downlink Coverage Class than what is assigned to the mobile station. + +### 9.3.2.4 Release of uplink Temporary Block Flow + +#### 9.3.2.4.1 General + +In the non-extended uplink TBF mode, the mobile station initiates the release of the uplink TBF by beginning the countdown process (see sub-clause 9.3.1). + +In the extended uplink TBF mode, the network determines when to release the uplink TBF. The release of an uplink TBF in the extended uplink TBF mode is performed by the procedure defined in sub-clause 9.5. + +#### 9.3.2.4.2 Non-extended uplink TBF mode + +When the mobile station has sent the RLC data block with $CV = 0$ and there are no elements in the $V(B)$ array set to the value Nacked, it shall start timer T3182 for this TBF. The mobile station shall continue to send RLC data blocks on each assigned uplink data block, according to the algorithm defined in sub-clause 9.1.3. + +If the network has received all RLC data blocks when it detects the end of the TBF (i.e. when $CV=0$ and $V(Q) = V(R)$ ), it shall send the PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', include a valid RRBP field in the RLC/MAC control block header and clear counter N3103 for the TBF. The network may use the TBF Est field in the PACKET UPLINK ACK/NACK message to allow the mobile station to request the establishment of a new uplink TBF if there are no additional TBFs ongoing for that mobile station. + +If the network has not received all of the RLC data blocks when it detects the end of the TBF, it shall send a PACKET UPLINK ACK/NACK message to the mobile station and if necessary allocate sufficient uplink resources for the mobile station to retransmit the required RLC data blocks. + +Upon reception of a PACKET UPLINK ACK/NACK message for this TBF the mobile station shall stop timer T3182 for the TBF. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the following conditions are fulfilled: TBF Est field is set to '1'; the mobile station has new data to transmit; the mobile station has no other ongoing downlink TBFs, the mobile station shall release the uplink TBF and may request the establishment of a new TBF using one of the following procedures: + +- If Control Ack Type parameter in System Information indicates acknowledgement is access burst, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message with the Ctrl Ack bits set to '00'. The mobile station shall start timer T3168 for the TBF request and continue to monitor the PDCH used for transmitting the PACKET CONTROL ACKNOWLEDGEMENT message. The mobile station shall stop timer T3168 for the TBF upon reception of the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure assigning resources for the TBF or the PACKET ACCESS REJECT message rejecting the TBF request. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 starting from the point where the mobile station receives the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. +- If Control Ack Type parameter in System Information indicates acknowledgement is RLC/MAC control block, the mobile station shall transmit the PACKET RESOURCE REQUEST message and start timer T3168 for the TBF request. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 starting from the point where the mobile station transmits the PACKET RESOURCE REQUEST message. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the mobile station does not initiate the establishment of a new uplink TBF according to one of the procedures described above, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message and release the TBF. If there is no other ongoing TBFs, the mobile station in packet transfer mode or MAC-Shared state shall return to packet idle mode or MAC-Idle state; the mobile station in dual transfer mode or MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5. If there are one or more ongoing TBFs a mobile station shall remain in its current mode/state and can request additional uplink TBFs as follows: + +- It may send a PACKET RESOURCE REQUEST message using the PACCH if there is at least one ongoing uplink TBF as described in sub-clause 8.1.1.1.2. +- It may include a Channel Request Description or the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or a Channel Request Description information element in the EGPRS PACKET DOWNLINK ACK/NACK DLMC message if there are no ongoing uplink TBFs and at least one ongoing downlink TBF as described in sub-clause 8.1.2.5. + +If the PACKET UPLINK ACK/NACK message requests retransmission of RLC data blocks, the mobile station shall if necessary wait for allocation of uplink resources for this TBF and then retransmit the RLC data blocks requested. The mobile station shall then start timer T3182 for the TBF and wait for a PACKET UPLINK ACK/NACK message as above. + +If timer T3182 expires for the TBF the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2) (*A/Gb mode*). + +When the network receives the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field, it may reuse the TFI and USF resources. + +If the network receives the PACKET CONTROL ACKNOWLEDGEMENT message with Ctrl Ack bits set to '00' or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field and the network has set the TBF Est field to '1' in the PACKET UPLINK ACK/NACK message, the network shall follow one of the following procedures: + +- In case the mobile station requested the establishment of new TBF with the PACKET CONTROL ACKNOWLEDGEMENT message, the network shall respond to the mobile station with the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message on the same PDCH as the mobile station has sent the PACKET CONTROL ACKNOWLEDGEMENT message. TLLI (in *A/Gb mode*) or the G-RNTI (in *Iu mode*) shall be used to identify the mobile station. The network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 (*A/Gb mode*) starting from the point where the network transmits the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. + +- In case the mobile station requested the establishment of new TBF with the PACKET RESOURCE REQUEST message, the network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 (*A/Gb mode*) starting from the point where the network has received the PACKET RESOURCE REQUEST message. TLLI (in *A/Gb mode*) or the G-RNTI (in *Iu mode*) shall be used to identify the mobile station. + +If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field, it shall increment counter N3103 for the TBF and retransmit the PACKET UPLINK ACK/NACK message. If counter N3103 exceeds its limit, the network shall start timer T3169 for the TBF. When timer T3169 expires for the TBF the network may reuse the TFI and USF resources. + +#### 9.3.2.4.3 Release of uplink EC TBF + +When the network has received all RLC data blocks for a TBF (i.e. all RLC data blocks that the mobile station has indicated as part of the TBF have been received), it shall send the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1'. The network may include a valid RRBP field in the RLC/MAC control block header in order to poll the mobile station for an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET DOWNLINK ACK/NACK HIGHER CC message. The network shall then clear counter N3103 for the TBF at transmission of the EC PACKET UPLINK ACK/NACK message. + +When the mobile station receives the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1' and including a valid RRBP field in the RLC/MAC control block header, it shall transmit an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET DOWNLINK ACK/NACK HIGHER CC message in the uplink resources indicated by the RRBP field. The EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET DOWNLINK ACK/NACK HIGHER CC message shall be sent according to the last assigned UL Coverage Class. + +The network may, in the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', indicate that the mobile station shall continue monitoring the EC-PACCH for some time, for possible reception of a downlink RLC/MAC control message, before returning to packet idle mode, see sub-clause 11.2.57. The network shall then start timer T3237 at transmission of the EC PACKET UPLINK ACK/NACK message. If the mobile station is not indicated to continue monitoring the EC-PACCH, it shall return directly to packet idle mode after reception of the message and, if so indicated by the network, transmission of the EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET DOWNLINK ACK/NACK HIGHER CC message. + +If the mobile station, in the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', has been indicated to continue monitoring the EC-PACCH, it shall start timer T3238. The mobile station shall then monitor the EC-PACCH, according to its assigned downlink Coverage Class of the TBF, after an initial waiting time as indicated in the EC PACKET UPLINK ACK/NACK message. The mobile station shall then monitor the EC-PACCH, using a monitoring pattern as indicated in the EC PACKET UPLINK ACK/NACK message, until timer T3238 expires or until a downlink RLC/MAC control message triggering the release of the TBF is received. When timer T3238 expires, the mobile station shall leave the TBF and return to packet idle mode. + +If the mobile station receives an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station while listening to the EC-PACCH, it shall stop timer T3238, release the uplink TBF and act on the assigned resources. + +In case the mobile station receives an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station after it has transmitted the last RLC data block, with CV=0, but prior to reception of the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', it shall consider all the transmitted RLC data blocks as acknowledged, release the uplink TBF and act on the assigned resources. + +After returning to packet idle mode, the mobile station shall, as long as the Ready timer is still running, listen to its paging group on the EC-CCCH using the lowest eDRX cycle, see 3GPP TS 45.002 [13]. + +When the EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET DOWNLINK ACK/NACK HIGHER CC message is received in the radio block indicated by the RRBP field, the network may release the TBF and reuse the TFI resource directly unless the mobile station has been indicated to continue monitoring the EC-PACCH in the EC PACKET UPLINK ACK/NACK message, in which case the network may release the TBF and reuse the TFI resource when timer T3237 expires. + +If the network does not receive the EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET DOWNLINK ACK/NACK HIGHER CC message in the resources indicated by the RRBP field, it shall increment counter N3103 for the TBF and retransmit the EC PACKET UPLINK ACK/NACK message in the next available DL EC-PACCH occasion for the TBF, unless N3103 has exceeded its limit. If the EC PACKET UPLINK ACK/NACK message + +contains an indication that the mobile station shall continue monitoring the EC-PACCH for some time before returning to packet idle mode, the network shall restart timer T3237 at transmission of the message. + +When timer T3229 expires for the TBF the network may release the TBF and reuse the TFI resource, unless timer T3237 is still running. + +### 9.3.2.5 Operation of downlink Temporary Block Flow + +The mobile station receives RLC/MAC blocks on the assigned downlink PDCHs. On each assigned PDCH, the mobile station shall in the RLC header identify the TFI and decode the RLC data blocks intended for the mobile station. + +A mobile station with a downlink EC TBF receives RLC/MAC blocks on the downlink EC-PDTCH/EC-PACCH that is part of the TBF. Each RLC/MAC block in the TBF may then be transmitted with a fixed number of blind physical layer transmissions, depending on the Coverage Class that the TBF has been assigned for, see 3GPP TS 45.002 [13]. An RLC/MAC block is received on the EC-PDTCH/EC-PACCH, which thus is mapped to one or several PDCHs, depending on the Coverage Class. A downlink EC TBF, assigned for Coverage Class 1, may consist of more than one EC-PDTCH/EC-PACCH, in which case the mobile station shall receive RLC/MAC blocks on more than one EC-PDTCH/EC-PACCH. + +The mobile station shall identify the TFI in the RLC header of the RLC/MAC blocks containing RLC data blocks that are received on the EC-PDTCH, and decode the RLC data blocks intended for the mobile station. If the RLC/MAC block, containing RLC data blocks, is not intended for the mobile station, it may use the Coverage Class (CC) field in the RLC data block header, if present, to determine that it may avoid listening to the EC-PDTCH/EC-PACCH while repetitions of the ongoing transmission (for a higher Coverage Class to another mobile station) are being transmitted. + +If the mobile station receives an RLC/MAC block, containing RLC data blocks, which is intended for the mobile station, it shall accept the RLC/MAC block even if the Coverage Class (CC) field in the RLC data block header indicates a different downlink Coverage Class than what is assigned to the mobile station. + +If the RLC/MAC block is an RLC/MAC control message received on the EC-PACCH, which is not addressed to the mobile station, it may use the USED\_DL\_COVERAGE\_CLASS information in the message to determine that it may avoid listening to the EC-PDTCH/EC-PACCH while repetitions of the ongoing transmission (for a higher Coverage Class to another mobile station) are being transmitted. + +If the mobile station receives an RLC/MAC control message addressed to it on the EC-PACCH, it shall accept the message even if the USED\_DL\_COVERAGE\_CLASS information in the message indicates a different downlink Coverage Class than what is assigned to the mobile station. + +The operation during the TBF shall be as defined in sub-clause 9.1. + +### 9.3.2.6 Release of downlink Temporary Block Flow + +If EMST is used (see sub-clause 5.10), the network shall release a downlink TBF by releasing all the RLC entities allocated on that TBF. The downlink TBF is successfully released when the last RLC entity is released. The network shall perform the release of an RLC entity operating in RLC acknowledged mode as specified in the present sub-clause. The network shall perform the release of an RLC entity operating in RLC unacknowledged mode as specified in sub-clause 9.3.3.5. + +The network initiates the release of a downlink TBF, or if EMST is used, the release of an RLC entity on the downlink TBF by sending an RLC data block with the Final Block Indicator (FBI) set to the value '1' and with a valid RRBP field. The RLC data block sent must have the highest BSN' (see sub-clause 9.3.1) of the downlink TBF, or if EMST is used, of the RLC entity. The network shall start timer T3191 for the TBF, or if EMST is used, for the RLC entity. While timer T3191 is running for the TBF the network may retransmit the RLC data block with the FBI bit set to the value '1'. For each retransmission the timer T3191 is restarted. + +In EGPRS TBF mode or EC TBF mode, if the final RLC data block is split for retransmission over two radio blocks (see sub-clause 9.3.2.1 for EGPRS TBF mode and sub-clause 9.3.2.1a for EC TBF mode), the network shall set the FBI to the value '1' in each part of the retransmitted RLC data block. + +If the mobile station receives an RLC data block (or, in EGPRS TBF mode or EC TBF mode, a part of a retransmitted RLC data block) with the FBI bit set the value '1' and with a valid RRBP field, the mobile station shall transmit a (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC or EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message in the specified uplink block. The mobile station shall continue to monitor all assigned PDCHs. The mobile station in EC TBF mode shall continue to monitor the assigned EC-PDCH(s)/EC-PACCH(s). + +Whenever the mobile station receives an RLC data block (or, in EGPRS TBF mode or EC TBF mode, a part of a retransmitted RLC data block) with a valid RRBP and the mobile station has received all RLC data blocks of the TBF, the mobile station shall send the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC or EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to '1' in the reserved uplink radio block specified by the RRBP field, stop the timer T3190 for the TBF. If EMST is used, the mobile station shall stop the timer T3190 only if the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message with the Final Ack Indicator bit set to '1' corresponds to the last remaining RLC entity on the TBF. If the timeout value of timer T3192 (see sub-clause 12.24 or, for EC TBF mode, 3GPP TS 44.018 [11]) is different from 0 ms then the mobile station shall start or restart timer T3192 for the TBF, or if EMST is used, for the RLC entity and continue to monitor all assigned downlink PDCHs. Otherwise, if the timeout value of timer T3192 is 0 ms then the mobile station shall follow the same procedure as if the timer T3192 has expired. + +In GPRS TBF mode, if the mobile station receives more than one RLC data block with the FBI set to '1', it shall accept the data from only the first one of these blocks. + +If the network receives a (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC or EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message for the TBF, or if EMST is used, for the RLC entity before its timer T3191 expires, and if retransmissions are required, then the network stops timer T3191 for the TBF, or if EMST is used, for the RLC entity and retransmits necessary RLC data blocks according to the ARQ protocol before re-initiating the release of the downlink TBF, or if EMST is used, of the RLC entity. The FBI is set to '1' only if the RLC data block with the highest BSN' of the TBF, or if EMST is used, of the RLC entity is retransmitted. If no retransmission is required, the network shall stop timer T3191 for the TBF, or if EMST is used, for the RLC entity and start or restart timer T3193 for the TBF, or if EMST is used, of the RLC entity. When T3193 expires the network shall release the TBF, or if EMST is used, the associated RLC entity. + +If timer T3191 expires for the TBF, then the network shall release the TBF, or if EMST is used, the associated RLC entity. + +If the network has received the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message with the Final Ack Indicator bit set to '1' and has new data to transmit for the mobile + +station that cannot be transmitted on any ongoing downlink TBF, the network may establish one or more new downlink TBF(s) for the mobile station by sending on PACCH the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message with the Control Ack bit set to '1' for each TBF. The network may send these downlink assignment messages using the PACCH of any ongoing TBF for the mobile station. In case the network establishes a new downlink TBF for the mobile station, or if EMST is used, reconfigures the ongoing TBF using the PACCH of a downlink TBF for which T3193 is running, the network shall stop that instance of timer T3193 and release that TBF, or if EMST is used, the associated RLC entity. The abnormal cases are described in sub-clause 8.1.2.4.1. + +If the network has received the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to '1' from a mobile station in EC TBF mode and has new data to transmit for the mobile station while the timer T3193 is still running, the network may establish a new downlink TBF for the mobile station by sending on EC-PACCH the EC PACKET DOWNLINK ASSIGNMENT message. The network shall then release the old TBF and stop that instance of timer T3193. + +After receiving an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message in TDMA frame N the network shall resume downlink transmissions to the corresponding mobile station on its assigned PDCH(s) according to the assigned downlink coverage class of the mobile station and may start as early downlink TDMA frame N+1 depending on the assigned uplink and downlink coverage classes. + +If the mobile station, after sending the PACKET DOWNLINK ACK/NACK message with the Final Ack Indicator bit set to '1' for a given TBF, receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message with the Control Ack bit set to '1' on the PACCH associated with this TBF while its timer T3192 is running, or if EMST is used, the timer T3192 associated with the RLC entity identified by the TFI included in the message is running, the mobile station shall stop this instance of timer T3192, consider this downlink TBF released, or if EMST is used, consider the associated RLC entity released and act upon the new assignments. + +If the mobile station in EC TBF mode, after sending the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to '1', receives an EC PACKET DOWNLINK ASSIGNMENT message on the EC-PACCH associated with this TBF while its timer T3192 is running, the mobile station shall stop this instance of timer T3192, consider this downlink TBF released and act upon the new assignments. + +When timer T3192 expires the mobile station shall release the associated downlink TBF, or if EMST is used, the associated RLC entity. If there are no other ongoing TBFs, or if EMST is used, no other ongoing RLC entities, the mobile station in packet transfer mode or MAC-Shared state shall return to packet idle mode or MAC-Idle state; the mobile station in dual transfer mode respectively MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. If there are one or more ongoing TBFs a mobile station shall remain in its current mode/state and can request additional uplink TBFs as follows: + +- It may send a PACKET RESOURCE REQUEST message using the PACCH if there is at least one ongoing uplink TBF as described in sub-clause 8.1.1.1.2. +- It may include a Channel Request Description or the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message if there are no ongoing uplink TBFs and at least one ongoing downlink TBF as described in sub-clause 8.1.2.5. + +The mobile station in EC TBF mode may include an EC Channel Request Description in the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message in order to request an uplink TBF. The network may then establish an uplink EC TBF for the mobile station by sending an EC PACKET UPLINK ASSIGNMENT message, in which case the downlink EC TBF is released. When transmitting the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the EC Channel Request Description, the mobile station shall start timer T3168 and listen to the EC-PACCH of the downlink TBF as described in sub-clause 8.1.2.5. When the mobile station receives an EC PACKET UPLINK ASSIGNMENT allocating resources for the request in the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message, it shall stop timers T3168 and T3192, if running, release the downlink TBF and act on the new assignment. The mobile station shall also stop timer T3168 at reception of an EC PACKET ACCESS REJECT message, in which case the mobile station shall continue monitoring the assigned EC-PDTCH/EC-PACCH resources of the downlink TBF. + +## 9.3.3 Unacknowledged mode operation + +### 9.3.3.0 General + +The transfer of RLC data blocks in the RLC unacknowledged mode does not include any retransmissions, except during the release of a TBF where the last transmitted block may be retransmitted (see sub-clauses 9.3.3.3 and 9.3.3.5). In EGPRS TBF mode, retransmission with segmentation method shall not be used. The block sequence number (BSN) in the RLC data block header is used to number the RLC data blocks for reassembly. + +The receiving RLC endpoint shall expect all RLC data blocks received in the same radio block period were sent in increasing order of BSN (apart from the last transmitted block of a TBF). As an exception, in a downlink dual carrier configuration or a DLMC configuration, the mobile station shall never expect RLC data blocks received in the same radio block period to have been sent in any specific order of BSN. In this case the mobile station shall re-order the received RLC data blocks before detecting any missing RLC data blocks. + +The receiving side sends Packet Ack/Nack messages in order to convey the necessary other control signalling (e.g. monitoring of channel quality for downlink transfer or timing advance correction for uplink transfers). + +#### 9.3.3.1 Establishment of Temporary Block Flow + +If the last uplink TBF ended with an incompletely transmitted upper layer PDU, the mobile station shall begin transmission on the new TBF with the last incompletely transmitted upper layer PDU. + +#### 9.3.3.2 Operation of uplink Temporary Block Flow + +The network shall send PACKET UPLINK ACK/NACK messages when needed. + +The mobile station shall set the Stall indicator (SI) bit to '0' in all RLC data blocks of the TBF. + +If the mobile station transmits the number of RLC data blocks corresponding to the RLC window size (WS), without receiving a Packet Ack/Nack message the mobile station shall start timer T3182 for the TBF. Timer T3182 shall be stopped upon reception of a PACKET UPLINK ACK/NACK message for this TBF. If timer T3182 expires, the mobile station shall decrement counter N3102 by PAN\_DEC, and perform an abnormal release with access retry (see sub-clause 8.7.2 (*A/Gb mode*)). + +Whenever the mobile station receives a PACKET UPLINK ACK/NACK message, the mobile station shall increment N3102 by PAN\_INC, however N3102 shall never exceed the value PAN\_MAX. Upon cell reselection the mobile station shall set counter N3102 to the value PAN\_MAX. When N3102 $\leq$ 0 is reached, the mobile station shall perform an abnormal release with cell re-selection (see sub-clause 9.4.2). If PAN\_DEC or PAN\_INC is set to the value 0, counter N3102 shall be disabled. + +A mobile station operating with an exclusive allocation shall start or restart timer T3184 upon reception of a PACKET UPLINK ACK/NACK message. If timer T3184 expires, the mobile station shall perform an abnormal release with access retry (see sub-clause 9.4.1). + +#### 9.3.3.3 Release of uplink Temporary Block Flow + +##### 9.3.3.3.1 General + +In the non-extended uplink TBF mode, the mobile station initiates the release of the uplink TBF by beginning the countdown process (see sub-clause 9.3.1). + +In the extended uplink TBF mode, the network determines when to release the uplink TBF. The release of an uplink TBF in the extended uplink TBF mode is performed by the procedure defined in sub-clause 9.5 (*A/Gb mode*). + +##### 9.3.3.3.2 Non-extended uplink TBF mode + +The mobile station indicates the end of the TBF by sending the RLC data block with CV = 0. The mobile station shall start timer T3182 for the TBF. + +When the network detects the end of the TBF (i.e. when CV=0) it shall send a PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', include a valid RRBP field in the RLC/MAC control block header and clear counter N3103 for the TBF. The network may use the TBF Est field in the PACKET UPLINK ACK/NACK message to allow the mobile station to request the establishment of a new uplink TBF if there are no additional TBFs ongoing for that mobile station. + +In case the network receives multiple blocks with CV=0, only the first needs to be acknowledged with PACKET UPLINK ACK/NACK message. + +Upon reception of a PACKET UPLINK ACK/NACK message for this TBF the mobile station shall stop timer T3182 for the TBF. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the mobile station does not initiate the establishment of a new uplink TBF according to one of the procedures described below, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message and release the TBF. If there are no other ongoing TBFs, the mobile station in packet transfer mode or MAC-Shared state shall enter packet idle mode or MAC-Idle state; the mobile station in dual transfer mode MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. If there are one or more ongoing TBFs a mobile station shall remain in its current mode/state and can request additional uplink TBFs as follows: + +- It may send a PACKET RESOURCE REQUEST message using the PACCH if there is at least one ongoing uplink TBF as described in sub-clause 8.1.1.1.2. + +- It may include a Channel Request Description or the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or a Channel Request Description information element in the EGPRS PACKET DOWNLINK ACK/NACK DLMC message if there are no ongoing uplink TBFs and at least one ongoing downlink TBF as described in sub-clause 8.1.2.5. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the following conditions are fulfilled: TBF Est field is set to '1'; the mobile station has new data to transmit; the mobile station has no other ongoing TBFs, the mobile station shall release the uplink TBF and may request the establishment of a new TBF using one of the following procedures: + +- If Control Ack Type parameter in System Information indicates acknowledgement is access burst, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message with the Ctrl Ack bits set to '00'. The mobile station shall start timer T3168 for the TBF request and continue to monitor the PDCH used for transmitting the PACKET CONTROL ACKNOWLEDGEMENT message. The mobile station shall stop timer T3168 for the TBF upon reception of the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure assigning resources for the TBF or the PACKET ACCESS REJECT message rejecting the TBF request. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 (*A/Gb mode*) starting from the point where the mobile station receives the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. +- If Control Ack Type parameter in System Information indicates acknowledgement is RLC/MAC control block, the mobile station shall transmit the PACKET RESOURCE REQUEST message and start timer T3168 for the TBF request. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 (*A/Gb mode*) starting from the point where the mobile station transmits the PACKET RESOURCE REQUEST message. + +If the PACKET UPLINK ACK/NACK message does not have the Final Ack Indicator bit set to '1', the mobile station shall repeat sending the last block with CV=0, until a PACKET UPLINK ACK/NACK message with Final Ack Indicator bit set to '1' is received for this TBF. Upon each retransmission of the last block with CV=0, the mobile station shall restart timer T3182 for the TBF. The block with CV=0 shall not be retransmitted more than four times. If the medium access mode is dynamic allocation, the repetitions are transmitted when the mobile station is scheduled USFs. If timer T3182 expires for the TBF the mobile station shall release the TBF as if a PACKET UPLINK ACK/NACK message was received. + +When the network receives the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field, it may reuse the TFI and USF resources. + +If the network receives the PACKET CONTROL ACKNOWLEDGEMENT message with Ctrl Ack bits set to '00' or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field and the network has set the TBF Est field to '1' in the PACKET UPLINK ACK/NACK message, the network shall follow one of the following procedures: + +- In case the mobile station requested the establishment of new TBF with the PACKET CONTROL ACKNOWLEDGEMENT message, the network shall respond to the mobile station with the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message on the same PDCH as the mobile station has sent the PACKET CONTROL ACKNOWLEDGEMENT message. TLLI (in *A/Gb mode*) or G-RNTI (in *Iu mode*) shall be used to identify the mobile station. The network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 (*A/Gb mode*) starting from the point where the network transmits the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. +- In case the mobile station requested the establishment of new TBF with the PACKET RESOURCE REQUEST message, the network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 (*A/Gb mode*) starting from the point where the network has received the PACKET RESOURCE REQUEST message. TLLI (in *A/Gb mode*) or G-RNTI (in *Iu mode*) shall be used to identify the mobile station. + +If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message for the TBF in the radio block indicated by the RRBP field, it shall increment counter N3103 and retransmit the PACKET UPLINK ACK/NACK message for the TBF. If counter N3103 exceeds its limit, the + +network shall start timer T3169 for the TBF. When timer T3169 expires for the TBF the network may reuse the TFI and USF resources. + +#### 9.3.3.4 Operation of downlink Temporary Block Flow + +The mobile station receives RLC/MAC blocks on the assigned downlink PDCHs. On each assigned PDCH, the mobile station shall in the RLC header identify the TFI and decode the RLC data blocks intended for the mobile station. The operation during the TBF shall be as defined in sub-clause 9.1 (*A/Gb mode*). + +#### 9.3.3.5 Release of downlink Temporary Block Flow + +If EMST is used (see sub-clause 5.10), the network shall release a downlink TBF by releasing all the RLC entities allocated on that TBF. The downlink TBF is successfully released when the last RLC entity is released. The network shall perform the release of an RLC entity operating in RLC unacknowledged mode as specified in the present sub-clause. The network shall perform the release of an RLC entity operating in RLC acknowledged mode as specified in sub-clause 9.3.2.6. + +The network initiates the release of a downlink TBF, or if EMST is used, the release of an RLC entity on a downlink TBF by sending an RLC data block with the Final Block Indicator (FBI) set to the value '1' and with a valid RRBG field. The RLC data block sent must have the highest BSN' (see sub-clause 9.3.1) of the downlink TBF, or if EMST is used, of the RLC entity. The network shall start timer T3191 for the TBF, or if EMST is used, for the RLC entity. The network may retransmit the last block with FBI set to the value '1' and with a valid RRBG field. For each retransmission for the TBF, or if EMST is used, for each retransmission for the RLC entity, the timer T3191 is restarted. + +For each RLC data block with the FBI bit set to '1' and with a valid RRBG field, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by the RRBG field. The mobile station shall continue to read the assigned downlink PDCHs until the block period pointed to by the RRBG. If the mobile station receives more than one RLC data block with the FBI bit set to '1' and with valid RRBG fields that point the same uplink block period, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message only once. The mobile station shall then stop timer T3190 for the TBF. If EMST is used, the mobile station shall stop the timer T3190 only if the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message with the Final Ack Indicator bit set to '1' corresponds to the last remaining RLC entity on the TBF. If the timeout value of timer T3192 (see sub-clause 12.24) is different from 0 ms then the mobile station shall start timer T3192 for the TBF, or if EMST is used, for the RLC entity and continue to monitor all assigned downlink PDCHs. Otherwise, if the timeout value of timer T3192 is 0 ms then the mobile station shall follow the procedure as if the timer T3192 has expired. + +If the mobile station then receives a subsequent RLC data block with a valid RRBG and the FBI bit set to '1', the mobile station shall retransmit the PACKET CONTROL ACKNOWLEDGEMENT message and restart timer T3192 for the TBF, or if EMST is used, for the associated RLC entity. + +In GPRS TBF mode, if the mobile station receives more than one RLC data block with the FBI set to '1' for the same RLC instance, it shall accept the data from only the first one of these blocks. + +If the network receives the PACKET CONTROL ACKNOWLEDGEMENT message for the TBF, or if EMST is used, for the RLC entity before timer T3191 expires, the network shall stop timer T3191 for the TBF, or if EMST is used, for the associated RLC entity and start or restart timer T3193 for the TBF, or if EMST is used, for the RLC entity. When T3193 expires the network shall release the TBF, or if EMST is used, the associated RLC entity. + +If timer T3191 expires, the network shall release the associated TBF, or if EMST is used, the associated RLC entity. + +If the network has received the PACKET CONTROL ACKNOWLEDGEMENT message and has new data to transmit for the mobile station, the network may establish one or more new downlink TBF(s) for the mobile station by sending on PACCH the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message with the Control Ack bit set to '1' for each TBF. In case the network establishes a new downlink TBF for a mobile station that does not support multiple TBF procedures, or if EMST is used, reconfigures the ongoing TBF, the network shall stop timer T3193 for the TBF, or if EMST is used, for the associated RLC entity. + +If the mobile station, after sending the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message with the Final Ack Indicator bit set to '1' for a given TBF, receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message with the Control Ack bit set to '1' on the PACCH associated with this TBF while its timer T3192 is running, or if EMST is used, while the timer T3192 associated with the RLC entity identified by the TFI included in the message is running, the mobile station shall stop this instance of timer T3192, consider this downlink TBF, or if EMST is used, the associated RLC entity released and act upon the new assignments. + +When timer T3192 expires then the mobile station shall release the related downlink TBF, or if EMST is used, the associated RLC entity. If there are no other ongoing TBF the mobile station in packet transfer mode or MAC-Shared state shall enter packet idle mode or MAC-Idle state; the mobile station in dual transfer mode or MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5. If there are one or more ongoing TBFs a mobile station shall remain in its current mode/state and can request additional uplink TBFs as follows: + +- It may send a PACKET RESOURCE REQUEST message using the PACCH if there is at least one ongoing uplink TBF as described in sub-clause 8.1.1.1.2. +- It may include a Channel Request Description or the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message if there are no ongoing uplink TBFs and at least one ongoing downlink TBF as described in sub-clause 8.1.2.5. + +### 9.3.4 Non-persistent mode operation + +#### 9.3.4.0 General + +The transfer of RLC data blocks in RLC non-persistent mode includes non-exhaustive retransmissions. The block sequence number (BSN) in the RLC data block header is used to number the RLC data blocks for reassembly. When RLC non-persistent mode is used for an MBMS bearer the receiving side sends MBMS DOWNLINK ACK/NACK messages to inform the transmitting side of the status of the reception and to convey neighbouring cell measurements. When RLC non-persistent mode is used for an EGPRS TBF the receiving side sends a PACKET UPLINK ACK/NACK, an EGPRS PACKET DOWNLINK ACK/NACK, an EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, an EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message to inform the transmitting side of the reception status. + +#### 9.3.4.1 Operation during an MBMS bearer + +The mobile station receives RLC/MAC blocks on the assigned downlink PDCHs. On each assigned PDCH, the mobile station shall in the RLC/MAC header identify the MBMS\_BEARER\_ID within the TFI field and decode the RLC data blocks if the mobile station is monitoring that MBMS Bearer. The operation during the MBMS bearer shall be as defined in sub-clause 9.1 + +#### 9.3.4.2 Release of an MBMS radio bearer + +The network may initiate the normal or abnormal release of an MBMS radio bearer by transmitting a PACKET TBF RELEASE message to the mobile station(s) on the PACCH, as described in sub-clause 8.1.4.4. + +The Final Block Indicator (FBI) bit shall not be set to the value '1' in any RLC/MAC block for data transfer of the MBMS radio bearer. + +#### 9.3.4.3 Operation during an EGPRS TBF + +The MAC procedures defined in sub-clause 8.1.1 and 8.1.2 apply for EGPRS TBFs that make use of RLC non-persistent mode. Release of an uplink EGPRS TBF operating in Non-persistent mode is specified in sub-clause 9.5. Release of a downlink EGPRS TBF operating in Non-persistent mode is as specified for RLC unacknowledged mode, (see sub-clause 9.3.3.5). + +## 9.4 Abnormal release cases + +### 9.4.1 Abnormal release with access retry + +The procedure for abnormal release with access retry is defined in sub-clause 8.7.2. + +### 9.4.2 Abnormal release with cell reselection + +If the mobile station is not in dedicated mode of a circuit switched connection, or is in MAC-Shared state, the mobile station shall abort all TBFs in progress and return to packet idle mode or MAC-Idle state. The mobile station shall perform an abnormal cell reselection (see 3GPP TS 45.008) and initiate the establishment of one or more uplink TBFs, using the procedures on CCCH or PCCCH as defined in sub-clause 7.1 on the new cell. The mobile station shall not reselect back to the original cell for T\_RESEL seconds if another suitable cell is available. + +If the abnormal cell reselection is abandoned (see 3GPP TS 45.008), the mobile station shall report an RLC/MAC failure to upper layers. If the mobile station remains in the cell where the abnormal release occurred, the DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. + +If the mobile station is in dedicated mode of a circuit switched connection (applies in GPRS class A mode of operation) or is in MAC-DTM state, the mobile station shall perform an abnormal release without retry, defined in sub-clause 8.7.1. + +The parameter T\_RESEL (default value 5 s) is broadcast in PSI 3. + +## 9.5 Uplink TBF release in extended uplink TBF mode + +In the extended uplink TBF mode (see sub-clause 9.3.1b), the network may initiate the release an uplink TBF by sending a PACKET UPLINK ACK/NACK message with the Final Ack Indicator set to '1'. The network shall include a valid RRBP field in the RLC/MAC control block header and clear counter N3103 for the TBF. The network may use the TBF Est field in the PACKET UPLINK ACK/NACK message to allow the mobile station to request the establishment of new TBF. The release of the uplink TBF, using this procedure, may be initiated at a point determined by the network. + +In case EMST is used, the network shall release an uplink TBF by releasing all the RLC entities allocated on that uplink TBF. The uplink TBF is successfully released when the last RLC entity is released. The network shall perform the release of an RLC entity as specified in this sub-clause. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the following conditions are fulfilled: TBF Est field is set to '1'; the mobile station has new data to transmit; the mobile station has no other ongoing TBFs, or if EMST is used, no other active RLC entity, the mobile station shall release the uplink TBF and may request the establishment of a new TBF using one of the following procedures: + +- If Control Ack Type parameter in System Information indicates acknowledgement is access burst, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message with the Ctrl Ack bits set to '00'. The mobile station shall start timer T3168 for the TBF request and continue to monitor the PDCH used for transmitting the PACKET CONTROL ACKNOWLEDGEMENT message. The mobile station shall stop timer T3168 for the TBF upon reception of the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure assigning resources for the TBF or the PACKET ACCESS REJECT message rejecting the TBF request. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 starting from the point where the mobile station receives the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. +- If Control Ack Type parameter in System Information indicates acknowledgement is RLC/MAC control block, the mobile station shall transmit the PACKET RESOURCE REQUEST message and start timer T3168 for the TBF request. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 starting from the point where the mobile station transmits the PACKET RESOURCE REQUEST message. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the mobile station does not initiate the establishment of a new uplink TBF according to one of the procedures described above, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message and release the TBF, or if EMST is used, + +the RLC entity. If there are no other ongoing TBFs, or if EMST is used, no other ongoing RLC entities, the mobile station in packet transfer mode shall return to packet idle mode; the mobile station in dual transfer mode shall return to dedicated mode. The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5. If there are one or more ongoing TBFs a mobile station shall remain in its current mode/state and can request additional uplink TBFs as follows: + +- It may send a PACKET RESOURCE REQUEST message using the PACCH if there is at least one ongoing uplink TBF as described in sub-clause 8.1.1.1.2. +- It may include a Channel Request Description or the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or a Channel Request Description information element in the EGPRS PACKET DOWNLINK ACK/NACK DLMC message if there are no ongoing uplink TBFs and at least one ongoing downlink TBF as described in sub-clause 8.1.2.5. + +When the network receives the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field, it may reuse the TFI and USF resources. If EMST is used, the USF resources may be reused only if the TBF is released, i.e. the last RLC entity allocated on the uplink TBF is released. + +When EMST is not used or when EMST is used and the last RLC entity is released, if the network receives the PACKET CONTROL ACKNOWLEDGEMENT message with Ctrl Ack bits set to '00' or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field and the network has set the TBF Est field to '1' in the PACKET UPLINK ACK/NACK message, the network shall follow one of the following procedures: + +- In case the mobile station requested the establishment of new TBF with the PACKET CONTROL ACKNOWLEDGEMENT message, the network shall respond to the mobile station with the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message on the same PDCH as the mobile station has sent the PACKET CONTROL ACKNOWLEDGEMENT message. TLLI shall be used to identify the mobile station. The network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 starting from the point where the network transmits the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. +- In case the mobile station requested the establishment of new TBF with the PACKET RESOURCE REQUEST message, the network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.1.3 starting from the point where the network has received the PACKET RESOURCE REQUEST message. TLLI shall be used to identify the mobile station. + +If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message for the TBF, or if EMST is used, for the RLC entity in the radio block indicated by the RRBP field, it shall increment counter N3103 and retransmit the PACKET UPLINK ACK/NACK message for the TBF, or if EMST is used, the RLC entity. When EMST is not used or when EMST is used and the last RLC entity is released, if counter N3103 exceeds its limit, the network shall stop scheduling new uplink resources for the TBF, stop sending the PACKET UPLINK ACK/NACK message to the mobile station and start timer T3169 for the TBF. + +When timer T3169 expires for the TBF, the network may reuse the TFI and USF resources. If EMST is used for the TBF, the USF resources may be reused only once the TBF is released, i.e. the last RLC entity allocated on the uplink TBF is released. + +# --- 10 RLC/MAC block structure + +## 10.0a RLC/MAC block structure + +Different RLC/MAC block structures are defined for data transfers and for control message transfers. The RLC/MAC block structures for data transfers are different for GPRS and EGPRS/EC-GSM-IoT, whereas the RLC/MAC block structure used for control message transfers for EC-GSM-IoT is different than the one used for GPRS and EGPRS. + +#### 10.0.a.1 GPRS RLC/MAC block for data transfer + +The RLC/MAC block for GPRS data transfer consists of a MAC header and an RLC data block. The RLC data block consists of an RLC header, an RLC data unit and spare bits. + +![](d793cf7c174b89eb024d132f00679787_img.jpg) + +| RLC/MAC block | | | | +|---------------|----------------|---------------|------------| +| MAC header | RLC data block | | | +| | RLC header | RLC data unit | Spare bits | + +**Figure 10.0.a.1.1: RLC/MAC block structure for data transfer for GPRS** + +The RLC data unit contains octets from one or more upper layer PDUs. + +#### 10.0.a.2 EGPRS and EC-GSM-IoT RLC/MAC block for data transfer + +The RLC/MAC block for EGPRS, EC-GSM-IoT and EGPRS2 data transfer is shown in figure 10.0.a.2.1 and consists of: + +- a combined RLC/MAC header, +- one or two RLC data blocks for EGPRS and EC-GSM-IoT, or up to four RLC data blocks for EGPRS2, +- an optional PAN field which is included in case FANR is activated, +- and an optional eTFI field which is included for the case where a mobile station in a DLMC configuration is assigned an eTFI for a downlink TBF. If an eTFI is assigned for a downlink TBF then an eTFI is included in an uplink RLC/MAC block for data transfer only if a PAN field corresponding to that downlink TBF is also included. + +![](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +| RLC/MAC block | | | | | | | +|----------------|------------------|--------------------------------|--------------------------------|--------------------------------|----------------|-----------------| +| RLC/MAC header | RLC data block 1 | RLC data block 2 (conditional) | RLC data block 3 (conditional) | RLC data block 4 (conditional) | PAN (optional) | eTFI (optional) | + +**Figure 10.0.a.2.1: RLC/MAC block structure for EGPRS, EC-GSM-IoT and EGPRS2 data transfer** + +Each RLC data block contain octets from one or more upper layer PDUs. + +The PAN field may only be included within an EGPRS RLC/MAC block for data transfer within a TBF with FANR activated. + +In EGPRS and EC-GSM-IoT, depending on the modulation and coding scheme (see 3GPP TS 44.004 and 3GPP TS 45.003) one or two RLC data blocks are contained in one RLC/MAC block. For MCS-1, MCS-2, MCS-3, MCS-4, MCS-5 and MCS-6 there is one RLC data block, whereas for MCS-7, MCS-8 and MCS-9 there are two RLC data blocks in the RLC/MAC block. + +In EGPRS and EC-GSM-IoT, in each transfer direction, uplink and downlink, three different header types are defined. The header fields for a specific header type may differ between EGPRS and EC-GSM-IoT. Which header type that is used depends on the modulation and coding scheme (MCS): + +- Header type 1 is used with modulation and coding scheme MCS-7, MCS-8 and MCS-9. +- Header type 2 is used with modulation and coding scheme MCS-5 and MCS-6. +- Header type 3 is used with modulation and coding scheme MCS-1, MCS-2, MCS-3 and MCS-4. + +In EC-GSM-IoT Header type 4 is used in uplink direction as described in sub-clause 10.4.8a.3: + +- Header type 4 is used with modulation and coding scheme MCS-1’. + +In EGPRS2, depending on the modulation and coding scheme (see 3GPP TS 44.004 and 3GPP TS 45.003) one to four RLC data blocks are contained in one RLC/MAC block as follows: + +- One RLC data block per RLC/MAC block: MCS-1, MCS-2, MCS-3, MCS-4, MCS-5, MCS-6, DAS-5, DAS-6, DAS-7, DBS-5, DBS-6, UBS-5 and UBS-6; + +- Two RLC data blocks per RLC/MAC block: MCS-7, MCS-8, MCS-9, DAS-8, DAS-9, DAS-10, DBS-7, DBS-8, UAS-7, UAS-8, UAS-9, UBS-7 and UBS-8; +- Three RLC data blocks per RLC/MAC block: DAS-11, DAS-12, DBS-9, DBS-10, UAS-10, UAS-11, UBS-9 and UBS-10; +- Four RLC data blocks per RLC/MAC block: DBS-11, DBS-12, UBS-11 and UBS-12. + +In EGPRS2, ten header types are used in the downlink direction. Which header type is used depends on the modulation and coding scheme: + +- Header type 1 is used with modulation and coding scheme MCS-7, MCS-8 and MCS-9 +- Header type 2 is used with modulation and coding scheme DAS-5, DAS-6 and DAS-7. +- Header type 3 is used with modulation and coding scheme MCS-1, MCS-2, MCS-3 and MCS-4. +- Header type 4 is used with modulation and coding scheme DAS-8 and DAS-9. +- Header type 5 is used with modulation and coding scheme DAS-11 and DAS-12. +- Header type 6 is used with modulation and coding scheme DBS-5 and DBS-6. +- Header type 7 is used with modulation and coding scheme DBS-7 and DBS-8. +- Header type 8 is used with modulation and coding scheme DBS-9 and DBS-10. +- Header type 9 is used with modulation and coding scheme DBS-11 and DBS-12. +- Header type 10 is used with modulation and coding scheme DAS-10. + +In EGPRS2, eight header types are used in the uplink direction. Which header type is used depends on the modulation and coding scheme: + +- Header type 2 is used with modulation and coding scheme MCS-5 and MCS-6. +- Header type 3 is used with modulation and coding scheme MCS-1, MCS-2, MCS-3 and MCS-4. +- Header type 4 is used with modulation and coding scheme UAS-7, UAS-8 and UAS-9. +- Header type 5 is used with modulation and coding scheme UAS-10 and UAS-11. +- Header type 6 is used with modulation and coding scheme UBS-5 and UBS-6. +- Header type 7 is used with modulation and coding scheme UBS-7 and UBS-8. +- Header type 8 is used with modulation and coding scheme UBS-9 and UBS-10. +- Header type 9 is used with modulation and coding scheme UBS-11 and UBS-12. + +#### 10.0.a.3 RLC/MAC block for control message transfer + +The downlink RLC/MAC block for control message transfer not associated with a TBF assigned an eTFI and an uplink RLC/MAC block for control message transfer consists of a MAC header and an RLC/MAC control block as shown in Figure 10.0.a.3.1. + +| RLC/MAC block | | +|---------------|-----------------------| +| MAC header | RLC/MAC control block | + +**Figure 10.0.a.3.1: RLC/MAC block structure for control block** + +The downlink RLC/MAC block for control message transfer associated with a TBF assigned an eTFI consists of a MAC header, an RLC/MAC control block and an eTFI field as shown in Figure 10.0.a.3.2. + +| RLC/MAC block | | | +|---------------|-----------------------|------| +| MAC header | RLC/MAC control block | eTFI | + +**Figure 10.0a.3.2: RLC/MAC block structure for control block (DLMC configuration used)** + +## 10.0b RLC/MAC block format conventions + +### 10.0b.1 Numbering convention + +The physical layer transfers RLC/MAC blocks, 11-bit and 8-bit control messages in physical blocks of the packet data channel. The physical block formats are specified in 3GPP TS 44.004. The physical block is organised as a sequence of N1 octets that are numbered from 1 to N1. An octet is a sequence of eight bits that are numbered from 1 to 8. If the total number of bits in a physical block is not an integer number of octets, the last bits of the physical block (in octet number N1) does not form a complete octet. The bits that are transferred in the last, and possibly incomplete octet, are numbered from 1 to n, where $1 \leq n \leq 8$ . The total number of bits in the physical block is $8(N1 - 1) + n$ . + +### 10.0b.2 Assembling conventions + +Different assembling conventions apply for GPRS RLC data blocks, RLC/MAC control blocks, 11-bit and 8-bit control messages and EGPRS/EC-GSM-IoT RLC data blocks. + +#### 10.0b.2.1 Assembling convention for GPRS RLC data blocks and RLC/MAC control blocks, 11-bit and 8-bit control messages + +The different components of an RLC/MAC block carrying a GPRS RLC data block or an RLC/MAC control block shall be assembled sequentially. Each component consists of an integer number of octets with an exception for the EC-PACCH/D RLC/MAC control block where the block is of integer number of octets but not the individual components (MAC header and Control message content). The assembling of components shall be performed progressively, starting in octet number 1 of the physical block. + +The 11-bit and 8-bit control messages map directly into the corresponding physical block. + +In this respect, an RLC/MAC control message, defined in sub-clause 11, or a segment of an RLC/MAC control message, see sub-clause 9.1.12a, shall be treated as a single field of either: + +- 176 bits(22 octets, using the PBCCH/PCCCH downlink/CS-1 encoded PACCH block format), +- 304 bits (38 octets, using the CS-3 encoded PACCH block format), +- 11 bits or 8 bits (using the PRACH uplink/PACCH uplink short acknowledgement block formats, see 3GPP TS 44.004), +- 75 bits or 67 bits (using the EC-PACCH/D without or with the optional RLC/MAC header bits respectively), +- 64 bits (using the EC-PACCH/U). + +The message contents defines a sequence of bits in decreasing order of value, i.e. the first bit of the message contents represents the highest order value and the last bit the lowest order value. + +The RLC/MAC header and a GPRS RLC data block are components that consist of an integer number of octets. Each octet shall be treated as a separate field when mapped into the physical block. The lowest numbered bit represents the lowest order value. + +The PDTCH block type 2 (CS-2), type 3 (CS-3) and type 4 (CS-4) formats (see 3GPP TS 44.004) do not have an integer number of octets. In these block types, bits number n to 1 of octet number N1 are spare bits. + +#### 10.0b.2.2 Assembling convention for EGPRS and EC-GSM-IoT RLC data blocks + +The different components of the RLC/MAC block carrying an EGPRS or EC-GSM-IoT RLC data block shall be assembled sequentially. A component may consist of a non-integer number of octets. Each octet shall be treated as a separate field when mapped into the physical block. The lowest numbered bit represents the lowest order value. + +The assembling of components shall be performed progressively, starting with octet number 1 of the physical block. If the boundary between two components falls within an octet of the physical block, the components, or parts thereof, that are contained in that octet shall be assembled progressively, starting with bit number 1 of the octet. (i.e. going from bit + +number 1 to bit number 8, except in octet number N1, where components are assembled going from bit number 1 to bit number n). + +### 10.0b.3 Field mapping conventions + +Different field mapping conventions apply for GPRS RLC data blocks, RLC/MAC control blocks, 11-bit and 8-bit control messages and EGPRS/EC-GSM-IoT RLC data blocks. + +#### 10.0b.3.1 Field mapping convention for GPRS RLC data blocks, CS-1 or CS-3 encoded RLC/MAC control blocks, EC-PACCH/D and EC-PACCH/U, 11-bit and 8-bit control messages + +When a field within a GPRS RLC data block or a CS-1 encoded RLC/MAC control block, or a CS-3 encoded RLC/MAC control block, or EC-PACCH/D or EC-PACCH/U encoded RLC/MAC control block or an 11-bit or an 8-bit control message is contained within a single octet of the physical block, the lowest numbered bit of the field represents the lowest order value. + +When a field spans more than one octet of the physical block, the order of bit values within each octet progressively *decreases* as the octet number increases. In that part of a field contained in a given octet, the lowest numbered bit represents the lowest order value. + +#### 10.0b.3.2 Field mapping convention for EGPRS and EC-GSM-IoT RLC data blocks and MCS-0 encoded RLC/MAC control blocks + +When a field within an EGPRS or EC-GSM-IoT RLC data block is contained within a single octet of the physical block, the lowest numbered bit of the field represents the lowest order value. + +When a field spans more than one octet of the physical block, the order of bit values within each octet progressively *increases* as the octet number increases. In that part of a field contained in a given octet, the lowest numbered bit represents the lowest order value. + +## 10.1 Spare bits + +Where the description of RLC/MAC blocks in this Technical Specification contains bits defined to be 'spare bits', these bits shall set to the value '0' by the sending side, and their value shall be ignored by the receiving side. + +## 10.2 GPRS RLC data blocks + +The RLC data block consists of an RLC header, an RLC data unit, and spare bits. An RLC/MAC block containing an RLC data block may be encoded using any of the available channel coding schemes CS-1, CS-2, CS-3, or CS-4 (see 3GPP TS 45.003). RLC/MAC blocks encoded using CS-1 do not contain spare bits. The size of the RLC data block for each of the channel coding schemes is shown in table 10.2.1. + +**Table 10.2.1: RLC data block size** + +| Channel Coding Scheme | RLC data block size without spare bits (N2) (octets) | Number of spare bits | RLC data block size (octets) | +|-----------------------|------------------------------------------------------|----------------------|------------------------------| +| CS-1 | 22 | 0 | 22 | +| CS-2 | 32 | 7 | 32 7/8 | +| CS-3 | 38 | 3 | 38 3/8 | +| CS-4 | 52 | 7 | 52 7/8 | + +### 10.2.1 Downlink RLC data block + +The Downlink RLC data block together with its MAC header is formatted as shown in figure 10.2.1.1. + +![Diagram of Downlink RLC data block with MAC header. It shows a table with 8 bits per octet. The header includes Payload Type (8), RRBG (6-5), S/P (4), USF (3-1), PR (7), TFI (6-4), FBI (1), BSN (6-1), Length indicator (6-2), M (1), E (1), and RLC data. Octets are labeled from Octet 1 to Octet N2.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +| Bit | | | | | | | | | +|------------------|---|------|---|-------|-----|---|-----|--------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Payload Type | | RRBG | | S/P | USF | | | MAC header | +| PR | | TFI | | | | | FBI | Octet 1 | +| BSN | | | | | | | E | Octet 2 | +| Length indicator | | | | | | M | E | Octet 3 (optional) | +| . | | | | | | | | . | +| . | | | | | | | | . | +| . | | | | | | | | . | +| Length indicator | | | | | | M | E | Octet M (optional) | +| . | | | | | | | | Octet M+1 | +| . | | | | | | | | . | +| . | | | | | | | | . | +| . | | | | | | | | Octet N2-1 | +| . | | | | | | | | Octet N2 | +| . | | | | | | | | (if present) | +| RLC data | | | | | | | | | +| spare | | | | spare | | | | | + +Diagram of Downlink RLC data block with MAC header. It shows a table with 8 bits per octet. The header includes Payload Type (8), RRBG (6-5), S/P (4), USF (3-1), PR (7), TFI (6-4), FBI (1), BSN (6-1), Length indicator (6-2), M (1), E (1), and RLC data. Octets are labeled from Octet 1 to Octet N2. + +Figure 10.2.1.1: Downlink RLC data block with MAC header + +### 10.2.2 Uplink RLC data block + +The Uplink RLC data block together with its MAC header is formatted as shown in figure 10.2.2.1. + +![Diagram of Uplink RLC data block. It shows a table with 8 bits per octet. The header includes Payload Type (8), Countdown Value (6-4), SI (2), R (1), spare (8), PI (7), TFI (6-4), E (1), BSN (6-1), Length indicator (6-2), M (1), E (1), Selected PLMN Index (3-1), TLLI (6-1), DCN-ID (octet 1) (6-1), DCN-ID (octet 2) (6-1), PFI (1), and RLC data. Octets are labeled from Octet 1 to Octet N.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +| Bit | | | | | | | | | +|------------------|----|-----------------|---|-------|---------------------|---|---|-----------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Payload Type | | Countdown Value | | | SI | R | | MAC header | +| spare | PI | TFI | | | | | E | Octet 1 | +| BSN | | | | | | | E | Octet 2 | +| Length indicator | | | | | | M | E | Octet 3 (optional) | +| spare | | | | | Selected PLMN Index | | | Octet 4 (note 2) (optional) | +| . | | | | | | | | . | +| . | | | | | | | | . | +| . | | | | | | | | . | +| Length indicator | | | | | | M | E | Octet M (optional) | +| . | | | | | | | | Octet M+1 \ | +| . | | | | | | | | Octet M+2 } (optional) | +| . | | | | | | | | Octet M+3 / | +| . | | | | | | | | Octet M+4 / | +| . | | | | | | | | Octet M+5 (Note 3) | +| Length indicator | | | | | | M | E | (Optional) | +| DCN-ID (octet 1) | | | | | | | | Octet M+6 | +| DCN-ID (octet 2) | | | | | | | | Octet M+7 | +| PFI | | | | | | | E | Octet M + 8 / | +| . | | | | | | | | Octet M+9 | +| . | | | | | | | | . | +| . | | | | | | | | . | +| . | | | | | | | | Octet N-1 | +| . | | | | | | | | Octet N | +| . | | | | | | | | (if present) | +| RLC data | | | | | | | | | +| spare | | | | spare | | | | | + +Diagram of Uplink RLC data block. It shows a table with 8 bits per octet. The header includes Payload Type (8), Countdown Value (6-4), SI (2), R (1), spare (8), PI (7), TFI (6-4), E (1), BSN (6-1), Length indicator (6-2), M (1), E (1), Selected PLMN Index (3-1), TLLI (6-1), DCN-ID (octet 1) (6-1), DCN-ID (octet 2) (6-1), PFI (1), and RLC data. Octets are labeled from Octet 1 to Octet N. + +- NOTE 1: The field mapping convention for GPRS (sub-clause 10.0b.3.1) applies. According to that, in particular regarding the TLLI field, the *most significant byte* of the TLLI value shall be mapped on octet M+1 and the *least significant byte* of the TLLI value shall be mapped on octet M+4 of the uplink RLC data block. +- NOTE 2: This octet is only included if the value of the first instance of the Length indicator in the RLC data block is 62. +- NOTE 3: This octet and the following two octets are only included if both the network and MS support MS assisted Dedicated Core Network selection (see 3GPP TS 44.018 [11]). + +Figure 10.2.2.1: Uplink RLC data block with MAC header + +## 10.3 RLC/MAC control blocks + +The RLC/MAC control block consists of a control message contents field and in the downlink direction an optional control header. RLC/MAC control messages shall be transported within RLC/MAC control blocks. An RLC/MAC control blocks shall always be encoded using the coding scheme CS-1 (see 3GPP TS 44.004), except in the following conditions: + +- on a downlink PDCH-pair assigned to a TBF in RTTI configuration with BTTF USF mode, downlink RLC/MAC control blocks shall always be encoded using coding scheme MCS-0; +- on a downlink PDCH-pair assigned to a TBF in RTTI configuration with RTTI USF mode, downlink RLC/MAC control blocks shall always be encoded using either coding scheme CS-1 or coding scheme MCS-0; an MS can differentiate CS-1 blocks from MCS-0 blocks by examining the stealing bits. +- a mobile station that supports more than 20 timeslots in a DLMC configuration (see sub-clause 5.13) may send an EGPRS Packet Downlink Ack/Nack DLMC message using the coding scheme CS-1 or CS-3 as indicated by the *PDAN Coding* IE in the most recently received assignment message. However, a mobile station that has been commanded to use CS-3 shall use CS-1 for any given EGPRS Packet Downlink Ack/Nack DLMC message that includes a request for an uplink TBF. + +### 10.3.1 Downlink RLC/MAC control block + +#### 10.3.1.1 Blocks encoded using CS-1 + +The Downlink RLC/MAC control block together with its MAC header is formatted as shown in figure 10.3.1.1.1. + +![](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +| Bit | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------|-----|-------|-----|----|---|-------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Payload Type | | RRBP | | S/P | USF | | | MAC header | +| RBSN | RTI | | | | FS | AC | | Octet 1 (optional) | +| PR | | TFI | | | D | | | Octet 2 (optional) | +| RBSNe | | | FSe | spare | | | | Octet 2/3 (optional) see note | +| Control Message Contents | | | | | | | | Octet M | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet 21 | +| | | | | | | | | Octet 22 | +| NOTE: This optional octet is included in case of extended RLC/MAC control message segmentation. Its presence is indicated through the combination of RBSN bit and FS bit equal to (RBSN='1' and FS='0') | | | | | | | | | + +Figure 10.3.1.1.1: Downlink RLC/MAC control block together with its MAC header + +- NOTE: The header octets and the control message contents octets shall be encoded following the field mapping convention defined in sub-clause 10.0b.3.1. + +#### 10.3.1.2 Blocks encoded using MCS-0 + +The downlink RLC/MAC control block header shall use the Header type 3 as shown in figure 10.3a.3.3.3 of subclause 10.3a.3.3. The RLC/MAC control block message contents are formatted as shown in figure 10.3.1.2. + +![](410562339ce067fdc6fa41940c118658_img.jpg) + +| | | | | | | | | | +|--------------------------|-----|---|-----|-------|---|----|----|-------------------------------| +| Bit | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| RBSN | RTI | | | | | FS | AC | Octet 1 (optional) | +| PR | TFI | | | | | | D | Octet 2 (optional) | +| RBSNe | | | FSe | spare | | | | Octet 2/3 (optional) see note | +| Control Message Contents | | | | | | | | Octet M | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet 21 | +| | | | | | | | | Octet 22 | + +NOTE: This optional octet is included in case of extended RLC/MAC control message segmentation. Its presence is indicated through the combination of RBSN bit and FS bit equal to (RBSN='1' and FS='0') + +Figure 10.3.1.2.1: Downlink RLC/MAC control block message contents + +NOTE: The optional header octets and the control message contents octets shall be encoded following the field mapping convention defined in sub-clause 10.0b.3.2. + +#### 10.3.1.3 Blocks encoded for EC-PACCH/D + +A coding block payload content of up to 80 bits, including MAC header, has been defined for use on EC-PACCH/D where the USF is encoded separately. Depending on the value of the Payload Type bit, the payload size is either 75 or 67 bits and is coded to generate punctured bits for EC-PACCH/D and designed to provide compatibility with GPRS and EGPRS. The EC-PACCH/D RLC/MAC control block for EC-GSM-IoT, including the MAC header, is formatted as shown in figure 10.3.1.3.1 or 10.3.1.3.2. + +The USF is encoded separately, see 3GPP TS 45.003. A different USF value may be included in each block when several blind physical layer transmissions are used in the downlink. If only EC TBFs are assigned on a PDCH, the inclusion of the USF should be regarded as optional. + +![](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) + +| | | | | | | | | | +|--------------------------|--------------|------|---|-----|---|---|---|---------------------| +| Bit | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| PR | Payload Type | RRBP | | S/P | | | | MAC header (5 bits) | +| Control Message Contents | | | | | | | | Octet 1 | +| | | | | | | | | Octet 2 | +| | | | | | | | | ... | +| | | | | | | | | Octet 9 | + +| | | | +|-----|---|---| +| Bit | | | +| 3 | 2 | 1 | +| USF | | | + +Figure 10.3.1.3.1: EC-GSM-IoT Downlink RLC/MAC control block together with its normal MAC header when Payload Type is set to 0 + +![](f20786b603b41e24b5d5899f710b5947_img.jpg) + +| | | | +|-----|---|---| +| Bit | | | +| 3 | 2 | 1 | +| USF | | | + +![Diagram of EC-GSM-IoT Downlink RLC/MAC control block with extended MAC header. The MAC header is 13 bits long, with bits 8-1 labeled: PR (8), Payload Type (7), RRBP (6-5), S/P (4), PRe (3), RBSN (2), and FS (1). Below the header is a TFI field, followed by Control Message Contents. To the right, the header is labeled 'MAC header (13 bits)', and the contents are labeled 'Octet 1', 'Octet 2', '...', 'Octet 9'.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Diagram of EC-GSM-IoT Downlink RLC/MAC control block with extended MAC header. The MAC header is 13 bits long, with bits 8-1 labeled: PR (8), Payload Type (7), RRBP (6-5), S/P (4), PRe (3), RBSN (2), and FS (1). Below the header is a TFI field, followed by Control Message Contents. To the right, the header is labeled 'MAC header (13 bits)', and the contents are labeled 'Octet 1', 'Octet 2', '...', 'Octet 9'. + +Figure 10.3.1.3.2: EC-GSM-IoT Downlink RLC/MAC control block together with its extended MAC header when Payload Type is set to 1 + +### 10.3.2 Uplink RLC/MAC control block + +The Uplink RLC/MAC control block together with its MAC header is formatted as shown in figure 10.3.2.1. + +![Diagram of Uplink RLC/MAC control block with MAC header. The MAC header has bits 8-1: Payload Type (8-7), spare (6-2), and R (1). Below is the Control Message Contents. To the right, the header is labeled 'MAC header', and the contents are labeled 'Octet 1', 'Octet 2', 'Octet 3', '...', 'Octet 21', 'Octet 22'.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +Diagram of Uplink RLC/MAC control block with MAC header. The MAC header has bits 8-1: Payload Type (8-7), spare (6-2), and R (1). Below is the Control Message Contents. To the right, the header is labeled 'MAC header', and the contents are labeled 'Octet 1', 'Octet 2', 'Octet 3', '...', 'Octet 21', 'Octet 22'. + +Figure 10.3.2.1: Uplink RLC/MAC control block together with its MAC header + +A coding block payload content of 64 bits has been defined for use on EC-PACCH/U. The payload is coded to generate punctured bits for EC-PACCH/U and designed to provide compatibility with GPRS and EGPRS. The EC-PACCH/U RLC/MAC control block for EC-GSM-IoT is without MAC header and formatted as shown in figure 10.3.2.2. + +![Diagram of EC-GSM-IoT Uplink RLC/MAC control block without MAC header. It shows a single block of Control Message Contents with bits 8-1 labeled at the top. To the right, the contents are labeled 'Octet 1', '...', 'Octet 8'.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +Diagram of EC-GSM-IoT Uplink RLC/MAC control block without MAC header. It shows a single block of Control Message Contents with bits 8-1 labeled at the top. To the right, the contents are labeled 'Octet 1', '...', 'Octet 8'. + +Figure 10.3.2.2: EC-GSM-IoT Uplink RLC/MAC control block. + +## 10.3a EGPRS and EC-GSM-IoT RLC data blocks and RLC/MAC headers + +### 10.3a.0 General + +The EGPRS and EC-GSM-IoT RLC data block consists of a FBI (downlink) or TI (uplink) field and an E field followed by an EGPRS RLC data unit. The EGPRS RLC data unit is a sequence of N2 octets that are numbered from 1 to N2. + +NOTE: The octets of an EGPRS RLC data unit are not necessarily aligned with the octets of the RLC/MAC block. An octet of the EGPRS RLC data unit may thus span across the boundary between two consecutive octets of the RLC/MAC block. + +The RLC/MAC block format convention of sub-clause 10.0b for EGPRS and EC-GSM-IoT applies when the components of the EGPRS and EC-GSM-IoT RLC data block are assembled into the RLC/MAC block. + +| | | | +|---|--------|---------------------| +| E | FBI/TI | EGPRS RLC data unit | +|---|--------|---------------------| + +**Figure 10.3a.0.1: Components of the EGPRS and EC-GSM-IoT RLC data block** + +The size of the EGPRS RLC data unit for each of the channel coding schemes is shown in table 10.3a.0.1. + +**Table 10.3a.0.1: EGPRS and EC-GSM-IoT RLC data unit size** + +| Channel Coding Scheme | EGPRS RLC data unit size (N2) (octets) | Family | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|---------------| +| MCS-1 | 22 | C | +| MCS-2 | 28 | B | +| MCS-3 with padding | 31 | A padding | +| MCS-3 | 37 | A padding / A | +| MCS-4 | 44 | C | +| MCS-5 | 56 | B | +| MCS-6 with padding | 68 | A padding | +| MCS-6 | 74 | A | +| MCS-7 | 2x56 | B | +| MCS-8 | 2x68 | A padding | +| MCS-9 | 2x74 | A | +| NOTE 1: The four families of EGPRS RLC data blocks C, B, A and A padding based on a common size basis (22, 28, 37 and 68 octets respectively) enable link adaptation retransmission as described in sub-clause 9. | | | +| NOTE 2: Modulation and coding schemes of family A padding are compatible with Family A padding6 defined for EGPRS2. | | | + +The size of the RLC data unit for each of the channel coding schemes used in EGPRS2 is shown in tables 10.3a.0.3, 10.3a.0.4, 10.3a.0.5, and 10.3a.0.6. + +Table 10.3a.0.3: RLC data unit size (EGPRS2-A downlink) + +| Channel Coding Scheme | EGPRS RLC data unit size (N2) (octets) | Family | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------| +| MCS-1 | 22 | C | +| MCS-2 with padding | 26 | B padding2 | +| MCS-2 | 28 | B padding2 / B | +| MCS-3 with padding | 31 | A padding6 | +| MCS-3 | 37 | A padding6 | +| MCS-4 | 44 | C | +| DAS-5 | 56 | B | +| DAS-6 | 68 | A padding6 | +| MCS-6 | 74 | NOTE 2 | +| DAS-7 | 82 | B padding2 | +| MCS-7 | 2x56 | B | +| DAS-8 | 2x56 | B | +| MCS-8 | 2x68 | A padding6 | +| DAS-9 | 2x68 | A padding6 | +| DAS-10 | 2x82 | B padding2 | +| DAS-11 | 3x68 | A padding6 | +| DAS-12 | 3x82 | B padding2 | +| NOTE 1: The four families of RLC data blocks (C, B, A padding6, and B padding2) based on a common size basis (22, 28, 68 and 82 octets respectively) enable link adaptation retransmission as described in sub-clause 9. | | | +| NOTE 2: MCS-6 is also used for EGPRS2-A downlink (see sub-clause 5.2.1). | | | + +Table 10.3a.0.4: RLC data unit size (EGPRS2-B downlink) + +| Channel Coding Scheme | EGPRS RLC data unit size (N2) (octets) | Family | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------| +| MCS-1 | 22 | C | +| MCS-2 | 28 | B | +| MCS-3 with padding | 31 | A padding6 | +| MCS-3 | 37 | A padding6 / A | +| MCS-4 | 44 | C | +| DAS-5 | 56 | B | +| DBS-5 | 56 | B | +| DAS-6 | 68 | A padding6 | +| MCS-6 | 74 | A | +| DBS-6 | 74 | A | +| MCS-7 | 2x56 | B | +| DAS-8 | 2x56 | B | +| DBS-7 | 2x56 | B | +| MCS-8 | 2x68 | A padding6 | +| DAS-9 | 2x68 | A padding6 | +| MCS-9 | 2x74 | A | +| DAS-10 with padding | 2x74 | A padding8 | +| DBS-8 | 2x74 | A | +| DBS-9 | 3x56 | B | +| DAS-11 | 3x68 | A padding6 | +| DAS-12 with padding | 3x74 | A padding8 | +| DBS-10 | 3x74 | A | +| DBS-11 | 4x68 | A padding6 | +| DBS-12 | 4x74 | A | +| NOTE 1: The five families of RLC data blocks (C, B, A, A padding6 and A padding8) based on a common size basis (22, 28, 37, 68 and 74 octets respectively) enable link adaptation retransmission as described in sub-clause 9. | | | + +**Table 10.3a.0.5: RLC data unit size (EGPRS2-A uplink)** + +| Channel Coding Scheme | EGPRS RLC data unit size (N2) (octets) | Family | +|-----------------------|----------------------------------------|-----------------| +| MCS-1 | 22 | C | +| MCS-2 | 28 | B | +| MCS-3 with padding | 27 | A padding10 | +| MCS-3 | 37 | A padding10 / A | +| MCS-4 | 44 | C | +| MCS-5 | 56 | B | +| MCS-6 with padding | 64 | A padding10 | +| MCS-6 | 74 | A | +| UAS-7 | 2x56 | B | +| UAS-8 | 2x64 | A padding10 | +| UAS-9 | 2x74 | A | +| UAS-10 | 3x56 | B | +| UAS-11 | 3x64 | A padding10 | + +NOTE 1: The four families of RLC data blocks (C, B, A, and A padding10) based on a common size basis (22, 28, 37 and 64 octets respectively) enable link adaptation retransmission as described in sub-clause 9. + +**Table 10.3a.0.6: RLC data unit size (EGPRS2-B uplink)** + +| Channel Coding Scheme | EGPRS RLC data unit size (N2) (octets) | Family | +|-----------------------|----------------------------------------|----------------| +| MCS-1 | 22 | C | +| MCS-2 | 28 | B | +| MCS-3 with padding | 31 | A padding6 | +| MCS-3 | 37 | A padding6 / A | +| MCS-4 | 44 | C | +| UBS-5 | 56 | B | +| UBS-6 with padding | 68 | A padding6 | +| UBS-6 | 74 | A | +| UBS-7 | 2x56 | B | +| UBS-8 with padding | 2x68 | A padding6 | +| UBS-8 | 2x74 | A | +| UBS-9 | 3x56 | B | +| UBS-10 with padding | 3x68 | A padding6 | +| UBS-10 | 3x74 | A | +| UBS-11 | 4x68 | A padding6 | +| UBS-12 | 4x74 | A | + +NOTE 1: The four families of RLC data blocks (C, B, A and A padding6) based on a common size basis (22, 28, 37 and 68 octets respectively) enable link adaptation retransmission as described in sub-clause 9. + +### 10.3a.1 Downlink RLC data block + +#### 10.3a.1.1 EGPRS downlink RLC data block + +The EGPRS downlink RLC data blocks are formatted according to figure 10.3a.1.1.1. + +![](90ee16ccc0ad16aeca48087797d7b07f_img.jpg) + +Bit + +| | | +|-----|---| +| 2 | 1 | +| FBI | E | + +![](4356776ca004ecba5d599667a155d7d4_img.jpg) + +| Bit | | | | | | | | | +|----------------------|---|----------|---|----|--------------|---|---|------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Length indicator | | | | | | | E | Octet 1 (note)
(optional) | +| . | | | | | | | | . | +| . | | | | | | | | . | +| . | | | | | | | | . | +| Length indicator | | | | | | | E | Octet M (optional) | +|
RLC data

| | | | | | | | Octet M+1 | +| | | | | | | | | . | +| | | | | | | | | Octet K-1 | +| spare | | DTR Blks | | CI | TN/PDCH-pair | | | Octet K (optional) | +| | | | | | | | | . | +| | | | | | | | | Octet N2-1 | +| | | | | | | | | Octet N2 | + +NOTE: If padding is used, then "Octet 1" shall be replaced by "Octet 7", see example in annex J. + +**Figure 10.3a.1.1.1: EGPRS downlink RLC data block** + +#### 10.3a.1.2 EC-GSM-IoT downlink RLC data block + +For an EC TBF, the downlink RLC data blocks are formatted according to figure 10.3a.1.2.1. + +![](51db757d054ce1ce83c436a3578b56ca_img.jpg) + +| Bit | | +|-----|---| +| 2 | 1 | +| FBI | E | + +| Bit | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Length indicator | | | | | | | E | Octet 1 (note)
(optional) | +| . | | | | | | | | . | +| . | | | | | | | | . | +| . | | | | | | | | . | +| Length indicator | | | | | | | E | Octet M (optional) | +|

RLC data


| | | | | | | | Octet M+1 | +| | | | | | | | | . | +| | | | | | | | | Octet K | +| | | | | | | | | . | +| | | | | | | | | Octet N2-1 | +| | | | | | | | | Octet N2 | + +NOTE: If padding is used, then "Octet 1" shall be replaced by "Octet 7", see example in annex J. + +**Figure 10.3a.1.2.1: EC-GSM-IoT downlink RLC data block** + +### 10.3a.2 Uplink RLC data block + +#### 10.3a.2.1 EGPRS Uplink RLC data block + +The EGPRS uplink RLC data block is formatted according to figure 10.3a.2.1.1. + +![](a734898ce18e972938949637c32a34f4_img.jpg) + +| | | +|-----|---| +| Bit | | +| 2 | 1 | +| TI | E | + +![](12de9b926df0384ec07702671827c9cd_img.jpg) + +| | | | | | | | | | +|------------------------|---|---|---|---------------------|---|---|---|-----------------------------| +| Bit | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Length Indicator | | | | | | | E | Octet 1 (note 1) (optional) | +| spare | | | | Selected PLMN Index | | | | Octet 2 (note 3) (optional) | +| . | | | | | | | | . | +| . | | | | | | | | . | +| . | | | | | | | | . | +| Length Indicator | | | | | | | E | Octet M (optional) | +| TLLI | | | | | | | | Octet M+1 / | +| | | | | | | | | Octet M+2 (optional) | +| | | | | | | | | Octet M+3 / | +| | | | | | | | | Octet M+4 / | +| Length Indicator = 122 | | | | | | | E | Octet M+5 (optional) | +| Cell Identity | | | | | | | | Octet M+6 | +| | | | | | | | | Octet M+7 | +| | | | | | | | | Octet M+8 | +| | | | | | | | | | + +![](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +| | | | +|-----------------------------|------------------------|-------| +| Routing Area Identification | | | +| MS Sync Accuracy | MS Transmission Offset | | +| Random ID (low) | | | +| Random ID (high) | | | +| Length Indicator = 119 | | E | +| MTA Signature | | | +| Length Indicator = 121 | | E | +| MS Sync Accuracy | MS Transmission Offset | | +| Length Indicator = 120 | | E | +| DCN-ID (octet 1) | | | +| DCN-ID (octet 2) | | | +| Length Indicator = 118 | | E | +| FMA | MTA Report Instance | spare | +| PFI | | E | +| RLC data | | | + +Octet M+9 + Octet M+10 + Octet M+11 + Octet M+12 + Octet M+13 + Octet M+14 + Octet M+15 + Octet M+16 + Octet M+5 (optional) + Octet M+17 + Octet M+18 + Octet M+19 + Octet M+20 + Octet M+5 (optional) + Octet M+6 + Octet M+5 (optional, Note 4) + Octet M+6 + Octet M+7 + Octet M+5 (optional) + Octet M+6 + Octet M+8 / + Octet M+9 + . + . + . + Octet N2-1 + Octet N2 + +- NOTE 1: If padding is used, then "Octet 1" shall be replaced by "Octet 7", see example in annex J. +- NOTE 2: The field mapping convention for EGPRS (sub-clause 10.0b.3.2) applies. According to that, in particular regarding the TLLI field, the *least significant byte* of the TLLI value shall be mapped on octet M+1 and the *most significant byte* of the TLLI value shall be mapped on octet M+4 of the uplink EGPRS RLC data block. +- NOTE 3: This octet is only included if the value of the first instance of the *Length indicator* in the RLC data block is 123. +- NOTE 4: This octet and the following two octets are only included if both the network and MS support MS assisted Dedicated Core Network selection (see 3GPP TS 44.018). + +Figure 10.3a.2.1.1: Uplink EGPRS RLC data block + +#### 10.3a.2.2 EC-GSM-IoT Uplink RLC data block + +For an EC TBF, the uplink RLC data block is formatted according to figure 10.3a.2.2.1. + +![](a51105b2031bad93b818b82f071c6add_img.jpg) + +| | | +|-----|---| +| Bit | | +| 2 | 1 | +| TI | E | + +| Bit | | | | | | | | | | | | +|-----------------------------|---------------------|---|---|------------------------|---|---|---|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| Length Indicator | | | | | | | E | | | | | +| spare | | | | Selected PLMN Index | | | | | | | | +| . | | | | | | | | | | | | +| . | | | | | | | | | | | | +| . | | | | | | | | | | | | +| Length Indicator | | | | | | | E | | | | | +| TLLI | | | | | | | | | | | | +| Length Indicator = 122 | | | | | | | E | | | | | +| Cell Identity | | | | | | | | | | | | +| Routing Area Identification | | | | | | | | | | | | +| MS Sync Accuracy | | | | MS Transmission Offset | | | | | | | | +| Random ID (low) | | | | | | | | | | | | +| Random ID (high) | | | | | | | | | | | | +| Length Indicator = 119 | | | | | | | E | | | | | +| MTA Signature | | | | | | | | | | | | +| Length Indicator = 121 | | | | | | | E | | | | | +| MS Sync Accuracy | | | | MS Transmission Offset | | | | | | | | +| Length Indicator = 120 | | | | | | | E | | | | | +| DCN-ID (octet 1) | | | | | | | | | | | | +| DCN-ID (octet 2) | | | | | | | | | | | | +| Length Indicator = 118 | | | | | | | E | | | | | +| FMA | MTA Report Instance | | | spare | | | | | | | | +| RLC data | | | | | | | | | | | | + +Octet 1 (note 1) (optional) + +Octet 2 (note 3) (optional) + +. + +. + +. + +Octet M (optional) + +Octet M+1 / + +Octet M+2 (optional) + +Octet M+3 / + +Octet M+4 / + +Octet M+5 (optional) + +Octet M+6 + +Octet M+7 + +Octet M+8 + +Octet M+9 + +Octet M+10 + +Octet M+11 + +Octet M+12 + +Octet M+13 + +Octet M+14 + +Octet M+15 + +Octet M+16 + +Octet M+5 (optional) + +Octet M+17 + +Octet M+18 + +Octet M+19 + +Octet M+20 + +Octet M+5 (optional) + +Octet M+6 + +Octet M+5 (optional, Note 4) + +Octet M+6 + +Octet M+7 + +Octet M+5 (optional) + +Octet M+6 + +Octet M+8 + +. + +. + +. + +Octet N2-1 + +Octet N2 + +- NOTE 1: If padding is used, then "Octet 1" shall be replaced by "Octet 7", see example in annex J. +- NOTE 2: The field mapping convention for EC-GSM-IoT (sub-clause 10.0b.3.2) applies. According to that, in particular regarding the TLLI field, the *least significant byte* of the TLLI value shall be mapped on octet M+1 and the *most significant byte* of the TLLI value shall be mapped on octet M+4 of the uplink EC-GSM-IoT RLC data block. +- NOTE 3: This octet is only included if the value of the first instance of the *Length indicator* in the RLC data block is 123. +- NOTE 4: This octet and the following two octets are only included if both the network and MS support MS assisted Dedicated Core Network selection (see 3GPP TS 44.018). + +**Figure 10.3a.2.2.1: Uplink EC-GSM-IoT RLC data block** + +### 10.3a.3 EGPRS and EC-GSM-IoT Downlink RLC/MAC header + +#### 10.3a.3.1 Header type 1: header for MCS-7, MCS-8 and MCS-9 + +For an EGPRS TBF without FANR activated, the EGPRS combined downlink RLC/MAC header for MCS-7, MCS-8 and MCS-9 (header type 1) shall be formatted according to figure 10.3a.3.1.1. + +| Bit | | | | | | | | Octet | | | +|------|------|----|------|------|-----|---|------|-------|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| TFI | RRBP | | ES/P | | USF | | | 1 | | | +| BSN1 | | PR | | TFI | | | | 2 | | | +| BSN1 | | | | | | | | 3 | | | +| BSN2 | | | | | | | BSN1 | 4 | | | +| CPS | | | | BSN2 | | | | 5 | | | + +**Figure 10.3a.3.1.1: EGPRS downlink RLC data block header (FANR not activated) +for MCS-7, MCS-8 and MCS-9** + +For an EGPRS TBF with FANR activated and for an EGPRS2 TBF (see sub-clause 5.2.1), the downlink RLC/MAC header for MCS-7, MCS-8 and MCS-9 shall be formatted according to figure 10.3a.3.1.2. + +| Bit | | | | | | | | Octet | | | +|------|------|-------|---|------|---|---|------|-------|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| TFI | PANI | CES/P | | USF | | | | 1 | | | +| BSN1 | | PR | | TFI | | | | 2 | | | +| BSN1 | | | | | | | | 3 | | | +| BSN2 | | | | | | | BSN1 | 4 | | | +| CPS | | | | BSN2 | | | | 5 | | | + +**Figure 10.3a.3.1.2: EGPRS (FANR activated) / EGPRS2 downlink RLC data block header** + +For an EGPRS TBF without FANR activated in a DLMC configuration using an SNS of 8192, the EGPRS combined downlink RLC/MAC header for MCS-7, MCS-8 and MCS-9 (header type 1) shall be formatted according to figure 10.3a.3.1.3. + +| Bit | | | | | | | | Octet | | | +|------|------|------|------|------|-----|---|------|-------|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| TFI | BSN2 | RRBP | ES/P | | USF | | | 1 | | | +| BSN1 | | | | TFI | | | | 2 | | | +| BSN1 | | | | | | | | 3 | | | +| BSN2 | | | | | | | BSN1 | 4 | | | +| CPS | | | | BSN2 | | | | 5 | | | + +**Figure 10.3a.3.1.3: DLMC EGPRS downlink RLC data block header (FANR not activated) +for MCS-7, MCS-8 and MCS-9** + +For an EGPRS TBF with FANR activated in a DLMC configuration using an SNS of 8192 and for an EGPRS2 TBF in a DLMC configuration using an SNS of 8192, the downlink RLC/MAC header for MCS-7, MCS-8 and MCS-9 shall be formatted according to figure 10.3a.3.1.4. + +| Bit | | | | | | | | Octet | +|------|------|------|-------|---|---|------|------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | PANI | BSN2 | CES/P | | | USF | | 1 | +| BSN1 | | | | | | TFI | | 2 | +| | | | BSN1 | | | | | 3 | +| BSN2 | | | | | | | BSN1 | 4 | +| CPS | | | | | | BSN2 | | 5 | + +**Figure 10.3a.3.1.4: DLMC EGPRS (FANR activated) / DLMC EGPRS2 downlink RLC data block header for MCS-7, MCS-8 and MCS-9** + +For an EC TBF, the combined downlink RLC/MAC header for MCS-7, MCS-8 and MCS-9 (header type 1) shall be formatted according to figure 10.3a.3.1.5. + +| Bit | | | | | | | | Octet | | | +|-------|-------|------|-------|------|---|-----|---|-------|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| TFI | Spare | RRBP | ECS/P | | | USF | | 1 | | | +| BSN1 | | PR | | TFI | | | | 2 | | | +| Spare | BSN2 | | | BSN1 | | | | 3 | | | +| Spare | RRBP | | CPS | | | | | 4 | | | +| Spare | | | | | | | | 5 | | | + +**Figure 10.3a.3.1.5: EC-GSM-IoT downlink RLC data block header for MCS-7, MCS-8 and MCS-9** + +#### 10.3a.3.2 Header type 2: header for MCS-6, MCS-5, DAS-5, DAS-6 and DAS-7 + +For an EGPRS TBF without FANR activated, the EGPRS combined downlink RLC/MAC header for MCS-5 and MCS-6 (header type 2) shall be formatted according to figure 10.3a.3.2.1. + +| Bit | | | | | | | | Octet | +|------|------|----|------|-----|---|------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | RRBP | | ES/P | | | USF | | 1 | +| BSN1 | | PR | | TFI | | | | 2 | +| BSN1 | | | | | | | | 3 | +| | | | CPS | | | BSN1 | | 4 | + +**Figure 10.3a.3.2.1: EGPRS downlink RLC data block header (FANR not activated) for MCS-5 and MCS-6** + +For an EGPRS TBF with FANR activated and for an EGPRS2 TBF (see sub-clause 5.2.1), the downlink RLC/MAC header for MCS-5 and MCS-6 shall be formatted according to figure 10.3a.3.2.2, whereas the RLC/MAC header for DAS-5, DAS-6 and DAS-7 shall be formatted as shown on figure 10.3a.3.2.2. + +| Bit | | | | | | | | Octet | +|------|------|-------|-----|-----|-----|------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | PANI | CES/P | | | USF | | | 1 | +| BSN1 | | PR | | TFI | | | | 2 | +| BSN1 | | | | | | | | 3 | +| | | | CPS | | | BSN1 | | 4 | + +**Figure 10.3a.3.2.2: EGPRS (FANR activated) / EGPRS2 downlink RLC data block header for MCS-5, MCS-6, DAS-5, DAS-6 and DAS-7** + +For an EGPRS TBF without FANR activated in a DLMC configuration using an SNS of 8192, the EGPRS combined downlink RLC/MAC header for MCS-5 and MCS-6 (header type 2) shall be formatted according to figure 10.3a.3.2.3. + +![](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +| Bit | | | | | | | | Octet | +|------|-------|------|------|------|-----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | spare | RRBP | ES/P | | USF | | | 1 | +| BSN1 | | | | TFI | | | | 2 | +| BSN1 | | | | | | | | 3 | +| CPS | | | | BSN1 | | | | 4 | + +**Figure 10.3a.3.2.3: DLMC EGPRS downlink RLC data block header (FANR not activated) for MCS-5 and MCS-6** + +For an EGPRS TBF with FANR activated in a DLMC configuration using an SNS of 8192 and for an EGPRS2 TBF in a DLMC configuration using an SNS of 8192, the downlink RLC/MAC header for MCS-5, MCS-6, DAS-5, DAS-6 and DAS-7 shall be formatted according to figure 10.3a.3.2.4. + +![](171115f072e42b379238ed0dd438e9d7_img.jpg) + +| Bit | | | | | | | | Octet | +|------|------|-------|-------|------|-----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | PANI | spare | CES/P | | USF | | | 1 | +| BSN1 | | | | TFI | | | | 2 | +| BSN1 | | | | | | | | 3 | +| CPS | | | | BSN1 | | | | 4 | + +**Figure 10.3a.3.2.4: DLMC EGPRS (FANR activated) / DLMC EGPRS2 downlink RLC data block header for MCS-5, MCS-6, DAS-5, DAS-6 and DAS-7** + +For an EC TBF, the EGPRS combined downlink RLC/MAC header for MCS-5 and MCS-6 (header type 2) shall be formatted according to figure 10.3a.3.2.5. + +![](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|-------|------|-------|-----|------|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Spare | RRBP | ECS/P | | USF | | | 1 | +| BSN1 | | PR | | TFI | | | | 2 | +| RRBP | | CPS | | | BSN1 | | | 3 | +| Spare | | | | | | | | 4 | + +**Figure 10.3a.3.2.5: EC-GSM-IoT downlink RLC data block header for MCS-5 and MCS-6** + +#### **10.3a.3.3 Header type 3: header for MCS-4, MCS-3, MCS-2, MCS-1 and MCS-0 case** + +For an EGPRS TBF without FANR activated, the EGPRS combined downlink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 (header type 3) shall be formatted according to figure 10.3a.3.3.1. + +![](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +| Bit | | | | | | | | Octet | | +|------|------|----|------|-----|-----|---|------|-------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| TFI | RRBP | | ES/P | | USF | | | 1 | | +| BSN1 | | PR | | TFI | | | | 2 | | +| BSN1 | | | | | | | | 3 | | +| SPB | | | CPS | | | | BSN1 | | 4 | + +**Figure 10.3a.3.3.1: EGPRS downlink RLC data block header (FANR not activated) for MCS-1, MCS-2, MCS-3 and MCS-4** + +For an EGPRS TBF with FANR activated and for an EGPRS2 TBF (see sub-clause 5.2.1), the downlink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 shall be formatted according to figure 10.3a.3.3.2. + +![](73da53f7da73c0e2ead71eb1e2f746fb_img.jpg) + +| Bit | | | | | | | | Octet | | +|------|------|-------|-----|-----|-----|---|------|-------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| TFI | PANI | CES/P | | | USF | | | 1 | | +| BSN1 | | PR | | TFI | | | | 2 | | +| BSN1 | | | | | | | | 3 | | +| SPB | | | CPS | | | | BSN1 | | 4 | + +**Figure 10.3a.3.3.2: EGPRS (FANR activated) / EGPRS2 downlink RLC data block header for MCS-1, MCS-2, MCS-3 and MCS-4** + +For a TBF in RTTI configuration, the downlink RLC/MAC control block header for MCS-0 shall be formatted as defined in figure 10.3a.3.3.3. + +![](e354b57563dae469c00b412b2abdf765_img.jpg) + +| Bit | | | | | | | | Octet | | +|--------------|-------|---|------|-----|-----|---|-------|-------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| Payload type | Spare | | RRBP | S/P | USF | | | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 | | +| | 0 | 0 | CPS | | | | Spare | | 4 | + +NOTE2: Field indicated as '0' will be replaced by an 18 bit CRC during the channel coding, see sub-clause 5.1.4a.1.4 in 3GPP TS 45.003. + +**Figure 10.3a.3.3.3: Downlink RLC/MAC control block header for MCS-0.** + +For an EGPRS TBF without FANR activated in a DLMC configuration using an SNS of 8192, the EGPRS combined downlink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 (header type 3) shall be formatted according to figure 10.3a.3.3.4. + +![](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +| Bit | | | | | | | | Octet | | +|------|-------|------|------|-----|-----|---|------|-------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| TFI | spare | RRBP | ES/P | | USF | | | 1 | | +| BSN1 | | | | TFI | | | | 2 | | +| BSN1 | | | | | | | | 3 | | +| SPB | | | CPS | | | | BSN1 | | 4 | + +**Figure 10.3a.3.3.4: DLMC EGPRS downlink RLC data block header (FANR not activated) for MCS-1, MCS-2, MCS-3 and MCS-4** + +For an EGPRS TBF with FANR activated in a DLMC configuration using an SNS of 8192 and for an EGPRS2 TBF in a DLMC configuration using an SNS of 8192, the downlink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 shall be formatted according to figure 10.3a.3.3.2. + +![](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +| Bit | | | | | | | | Octet | | +|------|------|-------|-------|-----|-----|---|------|-------|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| TFI | PANI | spare | CES/P | | USF | | | 1 | | +| BSN1 | | | | TFI | | | | 2 | | +| BSN1 | | | | | | | | 3 | | +| SPB | | | CPS | | | | BSN1 | | 4 | + +**Figure 10.3a.3.3.5: DLMC EGPRS (FANR activated) / DLMC EGPRS2 downlink RLC data block header for MCS-1, MCS-2, MCS-3 and MCS-4** + +For an EC TBF, the EGPRS combined downlink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 (header type 3) shall be formatted according to figure 10.3a.3.3.6. Note that different USF values may be included in the different transmissions if blind physical layer transmissions are used in the downlink (when CC2, CC3 or CC4 is assigned for the transfer). + +![](c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|-------|------|-------|-----|------|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Spare | RRBP | ECS/P | | USF | | | 1 | +| BSN1 | | PR | | TFI | | | | 2 | +| Spare | CC | | SPB | | BSN1 | | | 3 | +| Spare | | | RRBP | | CPS | | | 4 | + +**Figure 10.3a.3.3.6: EC-GSM-IoT downlink RLC data block header for MCS-1, MCS-2, MCS-3 and MCS-4** + +##### 10.3a.3.4 Header type 4: header for DAS-8 and DAS-9 + +The combined downlink RLC/MAC header for DAS-8 and DAS-9 (header type 4) shall be formatted according to figure 10.3a.3.4.1. + +| Bit | | | | | | | | Octet | | | | +|-------|------|-------|---|------|-----|---|-------|-------|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| TFI | PANI | CES/P | | | USF | | | 1 | | | | +| BSN1 | | PR | | | TFI | | | 2 | | | | +| BSN1 | | | | | | | | 3 | | | | +| BSN2 | | | | | | | BSN1 | 4 | | | | +| Spare | CPS | | | BSN2 | | | Spare | 5 | | | | +| | | | | | | | | 6 | | | | + +**Figure 10.3a.3.4.1: Combined downlink RLC data block header for DAS-8 and DAS-9.** + +For an EGPRS2 TBF in a DLMC configuration using an SNS of 8192 the combined downlink RLC/MAC header for DAS-8 and DAS-9 (header type 4) shall be formatted according to figure 10.3a.3.4.2. + +| Bit | | | | | | | | Octet | | | | +|------|------|------|-------|------|-----|-----|-------|-------|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| TFI | PANI | BSN2 | CES/P | | | USF | | 1 | | | | +| BSN1 | | | | | TFI | | | 2 | | | | +| BSN1 | | | | | | | | 3 | | | | +| BSN2 | | | | | | | BSN1 | 4 | | | | +| BSN2 | CPS | | | BSN2 | | | Spare | 5 | | | | +| | | | | | | | | 6 | | | | + +**Figure 10.3a.3.4.2: DLMC Combined downlink RLC data block header for DAS-8 and DAS-9.** + +#### 10.3a.3.5 Header type 5: header for DAS-11 and DAS-12 + +The combined downlink RLC/MAC header for DAS-11 and DAS-12 (header type 5) shall be formatted according to figure 10.3a.3.5.1. + +| Bit | | | | | | | | Octet | | | | +|------|------|-------|-------|---|------|---|------|-------|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| TFI | PANI | CES/P | | | USF | | | 1 | | | | +| BSN1 | | PR | | | TFI | | | 2 | | | | +| BSN1 | | | | | | | | 3 | | | | +| BSN2 | | | | | | | BSN1 | 4 | | | | +| BSN3 | | | BSN2 | | | | | 5 | | | | +| CPS | | | | | BSN3 | | | 6 | | | | +| | | | Spare | | CPS | | | 7 | | | | + +**Figure 10.3a.3.5.1: Combined downlink RLC data block header for DAS-11 and DAS-12.** + +For an EGPRS2 TBF in a DLMC configuration using an SNS of 8192 the combined downlink RLC/MAC header for DAS-11 and DAS-12 (header type 5) shall be formatted according to figure 10.3a.3.5.2. + +| Bit | | | | | | | | Octet | | | | +|------|------|------|-------|-----|------|-----|------|-------|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| TFI | PANI | BSN2 | CES/P | | | USF | | 1 | | | | +| BSN1 | | | | | TFI | | | 2 | | | | +| BSN1 | | | | | | | | 3 | | | | +| BSN2 | | | | | | | BSN1 | 4 | | | | +| BSN3 | | | BSN2 | | | | | 5 | | | | +| CPS | | | | | BSN3 | | | 6 | | | | +| | | BSN2 | BSN3 | CPS | | | | 7 | | | | + +**Figure 10.3a.3.5.2: DLMC Combined downlink RLC data block header for DAS-11 and DAS-12.** + +#### 10.3a.3.6 Header type 6: header for DBS-5 and DBS-6 + +The combined downlink RLC/MAC header for DBS-5 and DBS-6 (header type 6) shall be formatted according to figure 10.3a.3.6.1. + +![](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|------|-------|-----|-----|-----|-----|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | PANI | CES/P | | | USF | | | 1 | +| BSN | | PR | | TFI | | | | 2 | +| BSN | | | | | | | | 3 | +| Spare | | | CPS | | | BSN | | 4 | + +**Figure 10.3a.3.6.1: Combined downlink RLC data block header for DBS-5 and DBS-6.** + +#### 10.3a.3.7 Header type 7: header for DBS-7 and DBS-8 + +The combined downlink RLC/MAC header for DBS-7 and DBS-8 (header type 7) shall be formatted according to figure 10.3a.3.7.1. + +![](15e4a144a88176b71ea3eff2722253b0_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|------|-------|---|------|-----|---|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | PANI | CES/P | | | USF | | | 1 | +| BSN1 | | PR | | TFI | | | | 2 | +| BSN1 | | | | | | | | 3 | +| BSN2 | | | | | | | BSN1 | 4 | +| Spare | CPS | | | BSN2 | | | | 5 | +| | | | | | | | Spare | 6 | + +**Figure 10.3a.3.7.1: Combined downlink RLC data block header for DBS-7 and DBS-8.** + +#### 10.3a.3.8 Header type 8: header for DBS-9 and DBS-10 + +The combined downlink RLC/MAC header for DBS-9 and DBS-10 (header type 8) shall be formatted according to figure 10.3a.3.8.1. + +![](803776dff64331076ffc951fc95358ee_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|------|-------|------|------|-----|---|------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | PANI | CES/P | | | USF | | | 1 | +| BSN1 | | PR | | TFI | | | | 2 | +| BSN1 | | | | | | | | 3 | +| BSN2 | | | | | | | BSN1 | 4 | +| BSN 3 | | | | BSN2 | | | | 5 | +| CPS | | | BSN3 | | | | | 6 | +| Spare | | | | CPS | | | | 7 | + +**Figure 10.3a.3.8.1: Combined downlink RLC data block header for DBS-9 and DBS-10.** + +#### 10.3a.3.9 Header type 9: header for DBS-11 and DBS-12 + +The combined downlink RLC/MAC header for DBS-11 and DBS-12 (header type 9) shall be formatted according to figure 10.3a.3.9.1. + +| Bit | | | | | | | | Octet | | | | | | | | | | | | | | | | | +|-------|------|-------|------|------|-----|---|------|-------|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | | | | | +| TFI | PANI | CES/P | | | USF | | | 1 | | | | | | | | | | | | | | | | | +| BSN1 | | PR | | | TFI | | | 2 | | | | | | | | | | | | | | | | | +| BSN1 | | | | | | | | 3 | | | | | | | | | | | | | | | | | +| BSN2 | | | | | | | BSN1 | 4 | | | | | | | | | | | | | | | | | +| BSN3 | | | | BSN2 | | | | 5 | | | | | | | | | | | | | | | | | +| BSN4 | | | BSN3 | | | | | 6 | | | | | | | | | | | | | | | | | +| CPS | BSN4 | | | | | | | 7 | | | | | | | | | | | | | | | | | +| Spare | CPS | | | | | | | 8 | | | | | | | | | | | | | | | | | +| | | | | | | | | 9 | | | | | | | | | | | | | | | | | +| | | | | | | | | Spare | | | | | | | | | | | | | | | | | + +Figure 10.3a.3.9.1: Combined downlink RLC data block header for DBS-11 and DBS-12. + +#### 10.3a.3.10 Header type 10: header for DAS-10 + +The combined downlink RLC/MAC header for DAS-10 (header type 10) shall be formatted according to figure 10.3a.3.10.1. + +| Bit | | | | | | | | Octet | | | | +|------|------|-------|-----|---|------|---|------|-------|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| TFI | PANI | CES/P | | | USF | | | 1 | | | | +| BSN1 | | PR | | | TFI | | | 2 | | | | +| BSN1 | | | | | | | | 3 | | | | +| BSN2 | | | | | | | BSN1 | 4 | | | | +| | | Spare | CPS | | BSN2 | | | 5 | | | | + +Figure 10.3a.3.10.1: Combined downlink RLC data block header for DAS-10. + +For an EGPRS2 TBF in a DLMC configuration using an SNS of 8192 the combined downlink RLC/MAC header for DAS-10 (header type 10) shall be formatted according to figure 10.3a.3.10.2. + +| Bit | | | | | | | | Octet | | | | +|------|------|-------|-------|---|------|-----|------|-------|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| TFI | PANI | BSN2 | CES/P | | USF | | | 1 | | | | +| BSN1 | | | | | | TFI | | 2 | | | | +| BSN1 | | | | | | | | 3 | | | | +| BSN2 | | | | | | | BSN1 | 4 | | | | +| BSN2 | | Spare | CPS | | BSN2 | | | 5 | | | | + +Figure 10.3a.3.10.2: DLMC Combined downlink RLC data block header for DAS-10. + +### 10.3a.4 EGPRS and EC-GSM-IoT Uplink RLC/MAC header + +#### 10.3a.4.1 Header type 1: header for MCS-7, MCS-8 and MCS-9 + +The EGPRS combined uplink RLC/MAC header for MCS-7, MCS-8 and MCS-9 (header type 1) shall be formatted according to figure 10.3a.4.1.1. + +| Bit | | | | | | | | Octet | | | | | | | | +|-------|----|-----------------|-----|---|----|-----|---|-------|--|--|--|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | +| TFI | | Countdown Value | | | SI | R | | 1 | | | | | | | | +| BSN1 | | | | | | TFI | | 2 | | | | | | | | +| BSN2 | | BSN1 | | | | | | 3 | | | | | | | | +| BSN2 | | | | | | | | 4 | | | | | | | | +| Spare | PI | RSB | CPS | | | | | 5 | | | | | | | | +| | | | | | | | | 6 | | | | | | | | +| | | | | | | | | Spare | | | | | | | | + +**Figure 10.3a.4.1.1: EGPRS uplink RLC data block header (FANR not activated) for MCS-7, MCS-8 and MCS-9.** + +For a EGPRS TBF with FANR activated, the uplink RLC/MAC header for MCS-7, MCS-8 and MCS-9 shall be formatted according to figure 10.3a.4.1.2. + +![](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +| Bit | | | | | | | | Octet | +|------|-----------------|------|-------|---|----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| BSN1 | | | TFI | | | | | 2 | +| BSN2 | | BSN1 | | | | | | 3 | +| BSN2 | | | | | | | | 4 | +| PANI | PI | RSB | CPS | | | | | 5 | +| | | | Spare | | | | | 6 | + +**Figure 10.3a.4.1.2: EGPRS uplink RLC data block header (FANR activated) for MCS-7, MCS-8 and MCS-9.** + +The EC-GSM-IoT combined uplink RLC/MAC header for MCS-7, MCS-8 and MCS-9 (header type 1) shall be formatted according to figure 10.3a.4.1.3. + +![](f2ea0f64a770b22b902820457d262265_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|-----------------|-------|-------|---|-----|------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | FOI | RI | | 1 | +| BSN1 | | | TFI | | | | | 2 | +| Spare | | BSN2 | | | | | | 3 | +| DCCE | | CPS | | | | | | 4 | +| Spare | | rTLLI | | | | DCCE | | 5 | +| | | | Spare | | | | | 6 | + +**Figure 10.3a.4.1.3: EC-GSM-IoT uplink RLC data block header for MCS-7, MCS-8 and MCS-9.** + +#### 10.3a.4.2 Header type 2: header for MCS-6 and MCS-5 + +The EGPRS combined uplink RLC/MAC header for MCS-5 and MCS-6 (header type 2) shall be formatted according to figure 10.3a.4.2.1. + +![](68d8089266ace7197304b43dcaf5d08e_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|-----------------|------|-----|-------|-----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| BSN1 | | | TFI | | | | | 2 | +| CPS | | BSN1 | | | | | | 3 | +| Spare | | | PI | RSB | CPS | | | 4 | +| | | | | Spare | | | | 5 | + +**Figure 10.3a.4.2.1: EGPRS uplink RLC data block header (FANR not activated) for MCS-5 and MCS-6** + +For an EGPRS TBF with FANR activated and for an EGPRS2 TBF, the uplink RLC/MAC header for MCS-5 and MCS-6 shall be formatted according to figure 10.3a.4.2.2. + +![](db395493033edacd83e212049fd55715_img.jpg) + +| Bit | | | | | | | | Octet | +|-------|-----------------|------|------|-------|-----|-----|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| BSN1 | | | TFI | | | | | 2 | +| CPS | | BSN1 | | | | | | 3 | +| Spare | | | PANI | PI | RSB | CPS | | 4 | +| | | | | Spare | | | | 5 | + +**Figure 10.3a.4.2.2: EGPRS (FANR activated) / EGPRS2 uplink RLC data block header for MCS-5 and MCS-6** + +The EC-GSM-IoT combined uplink RLC/MAC header for MCS-5 and MCS-6 (header type 2) shall be formatted according to figure 10.3a.4.2.3. + +| Bit | | | | | | | | Octet | | | | | +|-------|-----------------|---|-------|-----|-----|----|---|-------|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +| TFI | Countdown Value | | | | FOI | RI | | 1 | | | | | +| BSN1 | | | | TFI | | | | 2 | | | | | +| Spare | DCCE | | | CPS | | | | 3 | | | | | +| Spare | | | rTLLI | | | | | 4 | | | | | +| Spare | | | | | | | | 5 | | | | | + +**Figure 10.3a.4.2.3: EC-GSM-IoT uplink RLC data block header for MCS-5 and MCS-6** + +#### **10.3a.4.3 Header type 3 : header for MCS-4, MCS-3, MCS-2 and MCS-1** + +The EGPRS combined uplink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 (header type 3) shall be formatted according to figure 10.3a.4.3.1. + +| Bit | | | | | | | | Octet | +|-------|-----------------|-----|-----|-----|-----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| BSN1 | | | | TFI | | | | 2 | +| CPS | BSN1 | | | CPS | | | | 3 | +| Spare | PI | RSB | SPB | | CPS | | | 4 | + +**Figure 10.3a.4.3.1: EGPRS uplink RLC data block header (FANR not activated) for MCS-1, MCS-2, MCS-3 and MCS-4** + +For an EGPRS TBF with FANR activated and for an EGPRS2 TBF, the uplink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 shall be formatted according to figure 10.3a.4.3.2. + +| Bit | | | | | | | | Octet | +|------|-----------------|-----|-----|-----|-----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| BSN1 | | | | TFI | | | | 2 | +| CPS | BSN1 | | | CPS | | | | 3 | +| PANI | PI | RSB | SPB | | CPS | | | 4 | + +**Figure 10.3a.4.3.2: EGPRS (FANR activated)/EGPRS2 uplink RLC data block header for MCS-1, MCS-2, MCS-3 and MCS-4** + +The EC-GSM-IoT combined uplink RLC/MAC header for MCS-1, MCS-2, MCS-3 and MCS-4 (header type 3) shall be formatted according to figure 10.3a.4.3.3. + +| Bit | | | | | | | | Octet | +|-------|-----------------|-------|---|---------|-----|------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | FOI | RI | | 1 | +| BSN1 | | | | TFI | | | | 2 | +| DCCE | | SPB | | CPS/HCS | | | | 3 | +| Spare | | rTLLI | | | | DCCE | | 4 | + +**Figure 10.3a.4.3.3: EC-GSM-IoT uplink RLC data block header for MCS-1, MCS-2, MCS-3 and MCS-4** + +#### **10.3a.4.4 Header type 4: header for UAS-7, UAS-8 and UAS-9** + +The combined uplink RLC/MAC header for UAS-7, UAS-8 and UAS-9 (header type 4) shall be formatted according to figure 10.3a.4.4.1. + +| Bit | | | | | | | | Octet | | | | | +|-------|-----------------|----|-----|-----|----|---|-------|-------|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +| TFI | Countdown Value | | | | SI | R | | 1 | | | | | +| | BSN1 | | | TFI | | | | 2 | | | | | +| BSN2 | BSN1 | | | | | | | 3 | | | | | +| BSN2 | | | | | | | | 4 | | | | | +| Spare | PANI | PI | CPS | | | | | 5 | | | | | +| | | | | | | | Spare | 6 | | | | | + +**Figure 10.3a.4.4.1: Combined uplink RLC data block header for UAS-7, UAS-8 and UAS-9.** + +#### **10.3a.4.5 Header type 5: header for UAS-10 and UAS-11** + +The combined uplink RLC/MAC header for UAS-10 and UAS-11 (header type 5) shall be formatted according to figure 10.3a.4.5.1. + +| Bit | | | | | | | | Octet | | | | | | | | | | | | +|------|-----------------|---|---|-------|----|------|----|-------|--|--|--|--|--|--|--|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | +| TFI | Countdown Value | | | | SI | R | | 1 | | | | | | | | | | | | +| | BSN1 | | | TFI | | | | 2 | | | | | | | | | | | | +| BSN2 | BSN1 | | | | | | | 3 | | | | | | | | | | | | +| BSN2 | | | | | | | | 4 | | | | | | | | | | | | +| BSN3 | | | | | | | | 5 | | | | | | | | | | | | +| CPS | | | | | | BSN3 | | 6 | | | | | | | | | | | | +| | | | | Spare | | PANI | PI | 7 | | | | | | | | | | | | + +**Figure 10.3a.4.5.1: Combined uplink RLC data block header for UAS-10, UAS-11.** + +#### **10.3a.4.6 Header type 6: header for UBS-5 and UBS-6** + +The combined uplink RLC/MAC header for UBS-5 and UBS-6 (header type 6) shall be formatted according to figure 10.3a.4.6.1. + +| Bit | | | | | | | | Octet | +|-----|-----------------|---|---|-------|------|----|-----|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| | BSN | | | TFI | | | | 2 | +| CPS | BSN | | | | | | | 3 | +| | | | | Spare | PANI | PI | CPS | 4 | + +**Figure 10.3a.4.6.1: Combined uplink RLC data block header for UBS-5, UBS-6.** + +#### **10.3a.4.7 Header type 7: header for UBS-7 and UBS-8** + +The combined uplink RLC/MAC header for UBS-7 and UBS-8 (header type 7) shall be formatted according to figure 10.3a.4.7.1. + +| Bit | | | | | | | | Octet | | | | | +|-------|-----------------|----|-----|-----|----|---|---|-------|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +| TFI | Countdown Value | | | | SI | R | | 1 | | | | | +| | BSN1 | | | TFI | | | | 2 | | | | | +| BSN2 | BSN1 | | | | | | | 3 | | | | | +| BSN2 | | | | | | | | 4 | | | | | +| Spare | PANI | PI | CPS | | | | | 5 | | | | | + +**Figure 10.3a.4.7.1: Combined uplink RLC data block header for UBS-7, UBS-8.** + +#### 10.3a.4.8 Header type 8: header for UBS-9 and UBS-10 + +The combined uplink RLC/MAC header for UBS-9 and UBS-10 (header type 8) shall be formatted according to figure 10.3a.4.8.1. + +| Bit | | | | | | | | Octet | +|------|-----------------|---|-------|---|------|----|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| BSN1 | | | TFI | | | | | 2 | +| BSN2 | BSN1 | | | | | | | 3 | +| BSN2 | | | | | | | | 4 | +| BSN3 | | | | | | | | 5 | +| CPS | | | BSN3 | | | | | 6 | +| | | | Spare | | PANI | PI | | 7 | + +**Figure 10.3a.4.8.1: Combined uplink RLC data block header for UBS-9, UBS-10.** + +#### 10.3a.4.9 Header type 9: header for UBS-11 and UBS-12 + +The combined uplink RLC/MAC header for UBS-11 and UBS-12 (header type 9) shall be formatted according to figure 10.3a.4.9.1. + +| Bit | | | | | | | | Octet | +|-------|-----------------|----|------|---|----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| TFI | Countdown Value | | | | SI | R | | 1 | +| BSN1 | | | TFI | | | | | 2 | +| BSN2 | BSN1 | | | | | | | 3 | +| BSN2 | | | | | | | | 4 | +| BSN3 | | | | | | | | 5 | +| BSN4 | | | BSN3 | | | | | 6 | +| CPS | | | BSN4 | | | | | 7 | +| Spare | PANI | PI | CPS | | | | | 8 | + +**Figure 10.3a.4.9.1: Combined uplink RLC data block header for UBS-11, UBS-12.** + +#### 10.3a.4.10 Header type 4: header for MCS-1' + +The EC-GSM-IoT combined uplink RLC/MAC header for MCS-1' shall be formatted according to figure 10.3a.4.10.1. This header type is used on UL when the MS is assigned uplink coverage class CC5 for EC-PDTCH. + +| Bit | | | | | | | | Octet | +|-----------------|---|---|------|---|-------|----|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Countdown Value | | | DLCC | | FOI | RI | | 1 | +| rTLLI | | | SPB | | Spare | | | 2 | + +**Figure 10.3a.4.10.1: EC-GSM-IoT uplink RLC data block header for MCS-1'.** + +### 10.3a.5 Piggy-backed Ack/Nack field (SSN-based) + +When the SSN-based encoding is used (see sub-clause 9.1.14.1), the Piggy-backed Ack/Nack (PAN) field consists of a beginning of window (BOW), a short starting sequence number (ShortSSN), a reported bitmap (RB) and a temporary flow identifier (TFI) fields. In the downlink direction, the TFI field shall always include a valid value. In the uplink direction, the TFI field, or the combined TFI-eTFI fields (in case of a DLMC configuration and eTFI is assigned), shall include a valid value only if multiple TBF procedures or EMST or EMSR are supported by both the network and the mobile station; in all other cases, the bits of these fields shall be set to '0'. The length of the PAN field is 25 bits except if an eTFI is assigned in which case the length of the PAN is 28 bits in the uplink direction. The size of the ShortSSN + +field (defined in sub-clause 10.4.23) varies between 7 and 11 bits as shown in Figure 10.3a.5.1 except for a DLMC configuration where the size of the ShortSSN field varies between 11 and 13 bits (see sub-clause 10.4.12) in the uplink direction as shown in Figure 10.3a.5.2. The remaining bits in the PAN field are reserved for the reported bitmap with a size varying between 6 and 12 bits. + +The order of bits is as for the UNCOMPRESSED\_RECEIVE\_BLOCK\_BITMAP field in the EGPRS Ack/Nack Description information element (see sub-clause 12.3.1) i.e. the lowest order bit in the RB field corresponds to the block with the sequence number from which the ShortSSN is derived. + +![](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +| Bit | | | | | | | | Octet | +|----------|---|---|---|---------------|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| ShortSSN | | | | | | | | 1 | +| RB | | | | ShortSSN / RB | | | | 2 | +| TFI | | | | RB | | | | 3 | +| | | | | | | | | 4 | +| | | | | | | | | TFI | + +Figure 10.3a.5.1: Piggy-backed Ack/Nack field (SSN-based) + +![](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +| Bit | | | | | | | | Octet | +|----------|---|---------------|---|----------|---|-----|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| ShortSSN | | | | | | | | 1 | +| RB | | ShortSSN / RB | | ShortSSN | | | | 2 | +| TFI | | | | RB | | | | 3 | +| | | | | eTFI | | TFI | | 4 | + +Figure 10.3a.5.2: Uplink Piggy-backed Ack/Nack field (SSN-based, eTFI assigned) + +### 10.3a.6 Piggy-backed Ack/Nack field (Time-based) + +When the Time-based encoding is used (see sub-clause 9.1.14.1), the Piggy-backed Ack/Nack (PAN) field consists of a 20 bits reported bitmap, as described in sub-clause 9.1.15, plus 5 bits set to '0'. + +Codepoints are included so that the codepoints corresponding to blocks transmitted earlier are contained in the less significant bit(s) in the field. + +![](e4a14961bdc9882e296b25f7ae5f9760_img.jpg) + +| Bit | | | | | | | | Octet | +|-----------------------------|---|---|---|------------------------|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Reported bitmap | | | | | | | | 1 | +| Reported bitmap (continued) | | | | | | | | 2 | +| 0 | 0 | 0 | 0 | Reported bitmap (cont) | | | | 3 | +| | | | | | | | | 4 | +| | | | | | | | | 0 | + +Figure 10.3a.6.1: Piggy-backed Ack/Nack field (Time-based) + +## 10.4 Header fields + +### 10.4.1 Uplink state flag (USF) field + +The USF field is sent in all downlink RLC/MAC blocks and indicates the owner or use of the next uplink radio block on the same timeslot (see 3GPP TS 45.002). The USF field is three bits in length and eight different USF values can be assigned, except on PCCCH, where the value '111' (USF=FREE) indicates that the corresponding uplink radio block contains PRACH. + +### 10.4.2 Retry (R) bit + +The Retry (R) bit shall indicate whether the mobile station transmitted the CHANNEL REQUEST message (see 3GPP TS 44.018), PACKET CHANNEL REQUEST message, EGPRS PACKET CHANNEL REQUEST message or MPRACH PACKET CHANNEL REQUEST message one time or more than one time during its most recent channel access. The mobile station shall send the same value for the R bit in each uplink RLC/MAC block of the TBF. + +**Table 10.4.2.1: Retry (R) bit** + +| bit 1 | Retry (R) bit | +|-------|-----------------------------------------------| +| 0 | MS sent channel request message once | +| 1 | MS sent channel request message twice or more | + +### 10.4.3 Stall indicator (SI) bit + +The Stall indicator (SI) bit indicates whether the mobile's RLC transmit window can advance (i.e. is not stalled) or can not advance (i.e. is stalled). The mobile station shall set the SI bit in all uplink RLC data blocks. + +**Table 10.4.3.1: Stall indicator bit** + +| bit 1 | Stall indicator | +|--------------------------------------------------------------|---------------------------------------| +| 0 | MS RLC transmit window is not stalled | +| 1 | MS RLC transmit window is stalled | +| NOTE 1: The bit numbering is relative to the field position. | | + +### 10.4.4 Supplementary/Polling (S/P) Bit + +The S/P bit is used to indicate whether the RRBP field is valid or not valid in downlink GPRS RLC data blocks and downlink RLC/MAC control blocks using the coding scheme of CS-1 and in downlink EC-GSM-IoT RLC/MAC control blocks on EC-PACCH/D. + +**Table 10.4.4.1: Supplementary/Polling (S/P) bit - GPRS case and RLC/MAC control** + +| bit 4 | S/P | +|-------|-------------------------| +| 0 | RRBP field is not valid | +| 1 | RRBP field is valid | + +### 10.4.4a EGPRS Supplementary/Polling (ES/P) Field + +The ES/P field is used to indicate whether the RRBP field is valid or not valid, and what fields the next uplink control block shall contain (see further clause 9). + +NOTE: The type of Ack/Nack bitmap requested by this field is applicable only when the next uplink control block is used to send an EGPRS PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2, EGPRS PACKET DOWNLINK ACK/NACK TYPE 3, EGPRS PACKET DOWNLINK ACK/NACK DLMC or MBMS DOWNLINK ACK/NACK message. + +**Table 10.4.4a.1: EGPRS Supplementary/Polling (ES/P) field (non-MBMS only)** + +| bits 5 4 | ES/P | +|----------|--------------------------------------------------------------------------------------| +| 0 0 | RRBP field is not valid (no Polling) | +| 0 1 | RRBP field is valid - Extended Ack/Nack bitmap type FPB | +| 1 0 | RRBP field is valid - Extended Ack/Nack bitmap type NPB | +| 1 1 | RRBP field is valid - Extended Ack/Nack bitmap type NPB, measurement report included | + +**Table 10.4.4a.2: EGPRS Supplementary/Polling (ES/P) field (MBMS only)** + +| bits
5 4 | ES/P | +|-------------|---------------------------------------------------------------------------------------------------------| +| 0 0 | RRBP field is not valid (no Polling) | +| 0 1 | RRBP field is valid - Extended Ack/Nack bitmap type FPB | +| 1 0 | RRBP field is valid - Extended Ack/Nack bitmap type NPB | +| 1 1 | RRBP field is valid - Extended Ack/Nack bitmap type NPB, neighbouring cell measurement reports included | + +### 10.4.4b Combined EGPRS Supplementary/Polling (CES/P) Field + +The CES/P field is used to indicate what fields the next uplink radio block reserved by this field shall contain (see further clause 9). The single uplink block is defined by a delay relative to the first TDMA frame (N) of the downlink block containing the CES/P value. The procedures defined for transmission of a PACCH block to the network as described in sub-clause 10.4.5 shall apply. + +If the mobile station is polled for a Piggy-backed Ack/Nack, in case EFTA is not used at the time the CES/P field is received, the mobile station shall transmit the uplink radio block on the same timeslot as the block where the CES/P field was received (in case of a BTI configuration) or on the uplink PDCH pair corresponding to the downlink PDCH pair where the block containing the CES/P field was received (in case of an RTTI configuration). In case EFTA is used at the time the CES/P field is received, the mobile station shall transmit the uplink radio block according to the uplink radio block transmission order as described in Annex N regardless of the timeslot or PDCH pair where the block containing the CES/P field was received. The mobile station need not monitor the USF in the associated downlink RLC/MAC block appearing just before the uplink block it shall transmit. However, when Extended Dynamic Allocation or Shifted USF operation is used, the corresponding USF monitoring procedure shall apply as described in sub-clause 8.1.1.2.1 and sub-clause 8.1.1.2.4 respectively. + +**Table 10.4.4b.1: Combined EGPRS Supplementary/Polling (CES/P) field** + +| bits
6 5 4 | CES/P | | | +|---------------|-----------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------| +| | Feedback | Reserved Block | | +| | | BTI | RTTI | +| 0 0 0 | no Polling | - | - | +| 0 0 1 | Extended Ack/Nack bitmap type FPB, and if there is enough room left in RLC/MAC block, channel quality report(s) | (N+8 or N+9) mod 2715648 | (N+6 or N+7) mod 2715648 | +| 0 1 0 | Extended Ack/Nack bitmap type FPB, and if there is enough room left in RLC/MAC block, channel quality report(s) | (N+13) mod 2715648 | (N+8 or N+9) mod 2715648 | +| 0 1 1 | Piggy-backed Ack/Nack bitmap type FPB (see sub-clause 8.1.2.2) see note | (N+8 or N+9) mod 2715648 | (N+6 or N+7) mod 2715648 | +| 1 0 0 | Piggy-backed Ack/Nack bitmap type FPB (see sub-clause 8.1.2.2) see note | (N+13) mod 2715648 | (N+8 or N+9) mod 2715648 | +| 1 0 1 | Channel quality report(s), and if there is enough room left in RLC/MAC block, Extended Ack/Nack bitmap type NPB | (N+8 or N+9) mod 2715648 | (N+6 or N+7) mod 2715648 | +| 1 1 0 | Channel quality report(s), and if there is enough room left in RLC/MAC block, Extended Ack/Nack bitmap type NPB | (N+13) mod 2715648 | (N+8 or N+9) mod 2715648 | +| 1 1 1 | Extended Ack/Nack bitmap type NPB, and if there is enough room left in RLC/MAC block, channel quality report(s) | (N+8 or N+9) mod 2715648 | (N+6 or N+7) mod 2715648 | + +NOTE: In case where a PAN cannot be sent, the Extended Ack/Nack bitmap type NPB with measurement report included shall be transmitted on the allocated reserved block instead (see sub-clause 9.1.14.2). + +In case of a DLMC configuration using an SNS of 8192 the CES/P field within the RLC data block header (see sub-clause 10.3a.3.1, 10.3a.3.2, 10.3a.3.3, 10.3a.3.4, 10.3a.3.5 and 10.3a.3.10) is coded as shown in Table 10.4.4b.2. + +**Table 10.4.4b.2: Combined EGPRS Supplementary/Polling (CES/P) field - DLMC Configuration** + +| bits
5 4 | CES/P | | | +|-------------|---------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------| +| | Feedback | Reserved Block | | +| | | BTTI | RTTI | +| 0 0 | no Polling | - | - | +| 0 1 | Extended Ack/Nack bitmap type FPB, and if there is enough room left in the RLC/MAC block, channel quality report(s) | (N+8 or N+9) mod 2715648 | (N+6 or N+7) mod 2715648 | +| 1 0 | Channel quality report(s), and if there is enough room left in the RLC/MAC block, Extended Ack/Nack bitmap type NPB | (N+8 or N+9) mod 2715648 | (N+6 or N+7) mod 2715648 | +| 1 1 | Piggy-backed Ack/Nack bitmap type FPB (see sub-clause 8.1.2.2) - see note | (N+8 or N+9) mod 2715648 | (N+6 or N+7) mod 2715648 | + +NOTE: In case where a PAN cannot be sent, the Extended Ack/Nack bitmap type NPB with channel quality report(s) included shall be transmitted on the allocated reserved block instead (see sub-clause 9.1.14.2). + +### 10.4.4c EC-GSM-IoT Supplementary/Polling (ECS/P) Field + +The ECS/P field is used to indicate whether the RRBP field is valid or not valid and, if valid, if a quality report is to be included in the next uplink control block. + +**Table 10.4.4c.1: EC-GSM-IoT Supplementary/Polling (ECS/P) field** + +| bits
5 4 | ECS/P | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 | RRBP field is not valid (no Polling) | +| 0 1 | RRBP field is valid, Ack/Nack report to be included | +| 1 0 | RRBP field is valid, Ack/Nack report to be included. If there is enough room in the RLC/MAC block, a channel quality report shall also be included. | +| 1 1 | Reserved | + +### 10.4.5 Relative Reserved Block Period (RRBP) field + +The RRBP value specifies a single uplink block in which the mobile station shall transmit either a PACKET CONTROL ACKNOWLEDGEMENT message, an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message, a PACCH block or an EC-PACCH block to the network. If the RRBP field is received as part of an RLC/MAC block containing an RLC/MAC control block, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT or an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message in the uplink radio block specified, except if: + +- The received message is a Packet Paging Request, Packet Access Reject, or Packet Queuing Notification message, or +- It is specified elsewhere that the mobile station shall not respond to the polling request. + +If the RRBP field is received as part of an RLC/MAC block containing an RLC/MAC control block containing a Packet Paging Request, Packet Access Reject, or Packet Queuing Notification message, or it is specified elsewhere that the mobile station shall not respond to the polling request, the mobile station shall ignore this RRBP field. The mobile station shall only react on RLC/MAC control blocks containing a valid RRBP field if the mobile station is addressed either in the downlink RLC/MAC control block header or in the control message itself. If the control message is segmented into more than one downlink RLC/MAC control blocks the mobile station shall react only on RLC/MAC control blocks containing a valid RRBP field if the mobile station is addressed in the downlink RLC/MAC control block header. + +If the mobile station receives two or more RLC/MAC blocks containing an RLC/MAC control message with different RRBP values such that they specify the same uplink block, the mobile station shall transmit one PACKET CONTROL ACKNOWLEDGEMENT or an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message in the specified uplink radio block. + +If the RRBP field is received as part of a RLC/MAC block containing an RLC data block, the mobile station shall transmit a PACCH block or an EC-PACCH block in the specified uplink radio block. If the mobile station receives two or more RLC/MAC blocks containing an RLC data block with different RRBP values such they specify the same uplink radio block, the mobile station shall transmit one (EC-)PACCH block in the specified uplink radio block. + +If the mobile station receives an RLC data block and an RLC/MAC control block with different RRBP values such that they specify the same uplink radio block, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT or an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message in the specified uplink radio block. + +If no uplink control timeslot is assigned to the mobile station and EFTA is not used at the time the RRBP field is received, the mobile station shall transmit the uplink radio block on the same timeslot as the block where the RRBP was received (in case of a BTTI configuration) or on the corresponding uplink PDCH pair to the downlink PDCH pair where the block containing the RRBP was received (in case of a RTTI configuration). If EFTA is used at the time the RRBP field is received however, the mobile station shall instead transmit the uplink radio block according to the uplink radio block transmission order as described in Annex N regardless of the timeslot or PDCH-pair where the block containing the RRBP was received. + +If an uplink control timeslot is assigned to the mobile station, the mobile station shall transmit the uplink radio block on this uplink control timeslot (in case of a BTTI configuration) or on the uplink PDCH pair the uplink control timeslot belongs to (in case of an RTTI configuration). + +NOTE: In case of an RTTI configuration, the network should not poll the mobile station on a downlink PDCH pair for which no corresponding uplink PDCH pair exists. + +After receiving an RLC/MAC block containing a valid RRBP field the mobile station need not monitor the USF in the associated downlink RLC/MAC block appearing just before the uplink block it shall transmit. However, when Extended Dynamic Allocation or Shifted USF operation is used, the corresponding USF monitoring procedure shall apply as described in sub-clause 8.1.1.2.1 and sub-clause 8.1.1.2.4 respectively. + +After receiving an RLC/MAC block containing a valid RRBP field for an EC TBF, the mobile station need not monitor the downlink RLC/MAC blocks during the radio block periods where it shall transmit the uplink response. + +A polled control message shall always be sent in the uplink block specified by the corresponding valid RRBP field of a downlink RLC/MAC control block, and not in any other uplink block that may be allocated to the mobile station. + +The network should use the RRBP field to schedule the transmission of a PACKET CONTROL ACKNOWLEDGEMENT or an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message or an uplink (EC-)PACCH block as follows: + +- For BTTI configuration, no later than the second last BTTI radio block, $B(x-2) \bmod 12$ , before the first BTTI radio block, $B(x)$ , where the mobile station shall be ready to transmit and receive using a new assignment. +- For RTTI configuration, no later than the second last RTTI radio block, $B(x-2)_b$ , before the first RTTI radio block, $B(x)_a$ , where the mobile station shall be ready to transmit and receive using a new assignment or no later than the second last RTTI radio block, $B(x-1)_a$ , before the first RTTI radio block, $B(x)_b$ , where the mobile station shall be ready to transmit and receive using a new assignment. + +A mobile station that is scheduled an uplink block later than these times, may omit responding to the polling request. If a new assignment specifies an uplink TBF, and the TTI configuration of the uplink TBF specified is the same as the TTI configuration of the ongoing uplink TBF that this assignment modifies, or if the assignment does not specify any uplink TBF, then the mobile station may delay the access using the new assignment in order to respond to the polling request. + +The network should not use the RRBP field to schedule the transmission of PACKET CONTROL ACKNOWLEDGEMENT, EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC messages or uplink (EC-) PACCH blocks, in such way, that a mobile station has more than three such uplink blocks pending for transmission at any instant. A mobile station, that is scheduled such uplink blocks more frequent than that, may omit responding to the excessive polling requests. + +The RRBP field shall be interpreted according to the TTI configuration in use for the mobile station on the PDCH (or on the PDCH pair) where the block containing the RRBP field is received at the time it is received, and, for a BTTI configuration, according to whether FANR is activated or not for the mobile station. + +For non EC TBFs with FANR not activated, Table 10.4.5.1 specifies the coding of the RRBP field indicating the number of TDMA frames the mobile station shall wait before transmitting the uplink RLC/MAC block. The delay is relative to the first TDMA frame (N) of the downlink block containing the RRBP value. For definition of TDMA frame numbering, see 3GPP TS 45.002. + +**Table 10.4.5.1: Relative Reserved Block Period (RRBP) field (FANR not activated)** + +| bit
6-5/7-6 | Full-rate PDCH uplink
block with TDMA frame
number | Full-rate PDCH uplink block
with TDMA frame number
(DLMC configuration with
SNS 2048) | Half-rate PDCH uplink
block with TDMA frame
number | +|----------------|----------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| 0 0 | (N+13) mod 2715648 | (N+13) mod 2715648 | reserved | +| 0 1 | (N+17 or N+18) mod
2715648 | (N+17 or N+18) mod
2715648 | (N+17 or N+18) mod
2715648 | +| 1 0 | (N+21 or N+22) mod
2715648 | (N+21 or N+22) mod
2715648 | reserved | +| 1 1 | (N+26) mod 2715648 | (N+26) mod 2715648 | (N+26) mod 2715648 | + +If the mobile station is operating on a half-rate PDCH and it receives an RLC/MAC block with a reserved RRBP value, it shall regard the RRBP field as not valid and shall ignore the polling. + +For TBFs with FANR activated, Table 10.4.5.2 specifies the coding of the RRBP field indicating the number of TDMA frames the mobile station shall wait before transmitting the uplink RLC/MAC block. + +**Table 10.4.5.2: Relative Reserved Block Period (RRBP) field (FANR activated)** + +| bit
6-5 | PDCH uplink block with TDMA frame
number (BTTI) | PDCH uplink block with TDMA frame
number (RTTI) | +|------------|----------------------------------------------------|----------------------------------------------------| +| 0 0 | (N+13) mod 2715648 | reserved | +| 0 1 | (N+8 or N+9) mod 2715648 | (N+8 or N+9) mod 2715648 | +| 1 0 | reserved | (N+6 or N+7) mod 2715648 | +| 1 1 | reserved | reserved | + +NOTE: Table 10.4.5.2 only applies to RLC/MAC control blocks encoded using CS-1, while the CES/P field is used in case of polling in RLC data blocks (see sub-clause 10.4.4b). + +In downlink RLC/MAC Control blocks encoded using MSC-0, a 1-bit RRBP is defined (see subclause 10.3a.3.3). In this case the number of TDMA frames the mobile station shall wait before transmitting the uplink RLC/MAC block is indicated in Table 10.4.5.3. + +**Table 10.4.5.3: Relative Reserved Block Period (RRBP) field – 1 bit field** + +| bit
5 | PDCH uplink block with TDMA frame
number | +|----------|---------------------------------------------| +| 0 | (N+6 or N+7) mod 2715648 | +| 1 | (N+8 or N+9) mod 2715648 | + +In a DLMC configuration using an SNS of 8192 for a downlink TBF where FANR is not activated, Table 10.4.5.4 specifies the RRBP field in the RLC data block header (see sub-clause 10.3a.3.1, 10.3a.3.2 and 10.3a.3.3) by indicating the number of TDMA frames the mobile station shall wait before transmitting the uplink RLC/MAC block. The delay is relative to the first TDMA frame (N) of the downlink block containing the RRBP value. For definition of TDMA frame numbering, see 3GPP TS 45.002. + +**Table 10.4.5.4: Relative Reserved Block Period (RRBP) field (FANR not activated) – DLMC Configuration** + +| bit
6 | PDCH uplink block with TDMA frame
number | +|----------|---------------------------------------------| +| 0 | (N+6 or N+7) mod 2715648 | +| 1 | (N+8 or N+9) mod 2715648 | + +For EC TBFs, Table 10.4.5.5 specifies the coding of the RRBP field if it is received as part of an RLC/MAC block containing an RLC/MAC data block indicating the number of TDMA frames the mobile station shall wait before transmitting the uplink RLC/MAC block according to its uplink Coverage Class. The delay is relative to the first TDMA frame (N) of the downlink block containing the last blind physical layer transmission of the EC-PACCH or EC-PDTCH message, according to the USED\_DL\_COVERAGE\_CLASS field. For definition of TDMA frame numbering, see 3GPP TS 45.002 [13]. + +**Table 10.4.5.5: Relative Reserved Block Period (RRBP) field (EC TBF mode) if received as part of an RLC/MAC block containing an RLC/MAC data block** + +| bit
6 5 4 | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC1
or CC2 with 4
PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC3
with 4 PDCH
allocation or
UL CC2 with 2
PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC4
with 4 PDCH
allocation or
UL CC3 with 2
PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC4
with 2 PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC5
with 4 PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC5
with 2 PDCH
allocation | +|--------------|--------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 0 | (N+13) mod
2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
Or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648
Or
(N+47 or N+48)
mod 2715648
or
(N+52) mod
2715648
or
(N+56 or N+57)
mod 2715648
or
(N+60 or N+61)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
Or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648
Or
(N+47 or N+48)
mod 2715648
or
(N+52) mod
2715648
or
(N+56 or N+57)
mod 2715648
or
(N+60 or N+61)
mod 2715648
Or
(N+65) mod
2715648
or
(N+69 or N+70)
mod 2715648
or
(N+73 or N+74)
mod 2715648
or
(N+78) mod
2715648
Or
(N+82 or N+83)
mod 2715648
or
(N+86 or N+87)
mod 2715648
or
(N+91) mod
2715648
or | + +| | | | | | | | +|--|--|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | | (N+95 or N+96)
mod 2715648
Or
(N+99 or
N+100) mod
2715648
or
(N+104) mod
2715648
or
(N+108 or
N+109) mod
2715648
or
(N+112 or
N+113) mod
2715648 | +|--|--|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | +|-------|----------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 1 | (N+17 or N+18) mod 2715648 | (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 or (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 Or (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 Or (N+99 or N+100) mod 2715648 or (N+104) mod 2715648 or (N+108 or N+109) mod 2715648 or (N+112 or N+113) mod 2715648 | (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 Or (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 Or (N+99 or N+100) mod 2715648 or (N+104) mod 2715648 or (N+108 or N+109) mod 2715648 or (N+112 or N+113) mod 2715648 Or (N+117) mod 2715648 or (N+121 or N+122) mod 2715648 or (N+125 or N+126) mod 2715648 or (N+130) mod 2715648 Or (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 or (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 Or | +|-------|----------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | +|--|--|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | | (N+151 or
N+152) mod
2715648
or
(N+156) mod
2715648
or
(N+160 or
N+161) mod
2715648
or
(N+164 or
N+165) mode
2715648 | +|--|--|--|--|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | +|-------|-------------------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 0 1 0 | (N+21 or N+22)
mod 2715648 | (N+30 or N+31)
mod 2715648
or
(N+34 or N+35 )
mod 2715648 | (N+47 or N+48)
mod 2715648
or
(N+52) mod
2715648
or
(N+56 or N+57)
mod 2715648
or
(N+60 or N+61)
mod 2715648 | (N+82 or N+83)
mod 2715648
or
(N+86 or N+87)
mod 2715648
or
(N+91) mod
2715648
or
(N+95 or N+96)
mod 2715648
or
(N+99 or
N+100) mod
2715648
or
(N+104) mod
2715648
or
(N+108 or
N+109) mod
2715648
or
(N+112 or
N+113) mod
2715648 | (N+117) mod
2715648
or
(N+121 or
N+122) mod
2715648
or
(N+125 or
N+126) mod
2715648
or
(N+130) mod
2715648
Or
(N+134 or
N+135) mod
2715648
or
(N+138 or
N+139) mod
2715648
or
(N+143) mod
2715648
or
(N+147 or
N+148) mod
2715648
Or
(N+151 or
N+152) mod
2715648
or
(N+156) mod
2715648
or
(N+160 or
N+161) mod
2715648
or
(N+164 or
N+165) mode
2715648 | Reserved | +|-------|-------------------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| + +| | | | | | | | +|-------|-----------------------|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 0 1 1 | (N+26) mod
2715648 | (N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648 | (N+65) mod
2715648
or
(N+69 or N+70)
mod 2715648
or
(N+73 or N+74)
mod 2715648
or
(N+78) mod
2715648 | (N+117) mod
2715648
or
(N+121 or
N+122) mod
2715648
or
(N+125 or
N+126) mod
2715648
or
(N+130) mod
2715648
or
(N+134 or
N+135) mod
2715648
or
(N+138 or
N+139) mod
2715648
or
(N+143) mod
2715648
or
(N+147 or
N+148) mod
2715648 | (N+169) mod
2715648
or
(N+173 or
N+174) mod
2715648
or
(N+177 or
N+178) mod
2715648
or
(N+182) mod
2715648
Or
(N+186 or
N+187) mod
2715648
or
(N+190 or
N+191) mod
2715648
or
(N+195) mod
2715648
or
(N+199 or
N+200) mod
2715648
Or
(N+203 or
N+204) mod
2715648
or
(N+208) mod
2715648
or
(N+212 or
N+213) mod
2715648
or
(N+216 or
N+217) mode
2715648 | Reserved | +|-------|-----------------------|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| + +| | | | | | | | +|-------|-------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------| +| 1 0 0 | (N+30 or N+31)
mod 2715648 | (N+47 or N+48)
mod 2715648
or
(N+52) mod
2715648 | (N+82 or N+83)
mod 2715648
or
(N+86 or N+87)
mod 2715648
or
(N+91) mod
2715648
or
(N+95 or N+96)
mod 2715648 | (N+151 or
N+152) mod
2715648
or
(N+156) mod
2715648
or
(N+160 or
N+161) mod
2715648
or
(N+164 or
N+165) mod
2715648
or
(N+169) mod
2715648
or
(N+173 or
N+174) mod
2715648
or
(N+177 or
N+178) mod
2715648
or
(N+182) mod
2715648 | Reserved | Reserved | +| 1 0 1 | (N+34 or N+35)
mod 2715648 | (N+56 or N+57)
mod 2715648
or
(N+60 or N+61)
mod 2715648 | (N+99 or
N+100) mod
2715648
or
(N+104) mod
2715648
or
(N+108 or
N+109) mod
2715648
or
(N+112 or
N+113) mod
2715648 | (N+186 or
N+187) mod
2715648
or
(N+190 or
N+191) mod
2715648
or
(N+195) mod
2715648
or
(N+199 or
N+200) mod
2715648
or
(N+203 or
N+204) mod
2715648
or
(N+208) mod
2715648
or
(N+212 or
N+213) mod
2715648
or
(N+216 or
N+217) mod
2715648 | Reserved | Reserved | + +| | | | | | | | +|-------|----------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------| +| 1 1 0 | (N+39) mod 2715648 | (N+65) mod 2715648
or
(N+69 or N+70) mod 2715648 | (N+117) mod 2715648
or
(N+121 or N+122) mod 2715648
or
(N+125 or N+126) mod 2715648
or
(N+130) mod 2715648 | (N+221) mod 2715648
or
(N+225 or N+226) mod 2715648
or
(N+229 or N+230) mod 2715648
or
(N+234) mod 2715648
or
(N+238 or N+239) mod 2715648
or
(N+242 or N+243) mod 2715648
or
(N+247) mod 2715648
or
(N+251 or N+252) mod 2715648 | Reserved | Reserved | +| 1 1 1 | (N+43 or N+44) mod 2715648 | (N+73 or N+74) mod 2715648
or
(N+78) mod 2715648 | (N+134 or N+135) mod 2715648
or
(N+138 or N+139) mod 2715648
or
(N+143) mod 2715648
or
(N+147 or N+148) mod 2715648 | (N+255 or N+256) mod 2715648
or
(N+260) mod 2715648
or
(N+264 or N+265) mod 2715648
or
(N+268 or N+269) mod 2715648
or
(N+273) mod 2715648
or
(N+277 or N+278) mod 2715648
or
(N+281 or N+282) mod 2715648
or
(N+286) mod 2715648 | Reserved | Reserved | + +NOTE: Each RRBP value in Table 10.4.5.5 will assign only one valid uplink block given the downlink coverage class used, i.e. when the poll is received, and the uplink coverage class used. See 3GPP TS 45.002 [13] for the coverage class dependent channel mappings. The code points which indicates Reserved are not intended to be used. + +For EC TBFs, Table 10.4.5.6 specifies the coding of the RRBP field if it is received as part of an RLC/MAC block containing an RLC/MAC control block indicating the number of TDMA frames the mobile station shall wait before transmitting the uplink RLC/MAC block according to its uplink Coverage Class. The delay is relative to the first TDMA frame (N) of the downlink block containing the last blind physical layer transmission of the EC-PACCH or EC-PDTCH message, according to the USED\_DL\_COVERAGE\_CLASS field. For definition of TDMA frame numbering, see 3GPP TS 45.002 [13]. + +**Table 10.4.5.6: Relative Reserved Block Period (RRBP) field (EC TBF mode) if received as part of an RLC/MAC block containing an RLC/MAC control block** + +| bit
3 2 | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC1
or CC2 with 4
PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC3
with 4 PDCH
allocation or
UL CC2 with 2
PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC4
with 4 PDCH
allocation or
UL CC3 with 2
PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC4
with 2 PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC5
with 4 PDCH
allocation | Full-rate PDCH
uplink block
with TDMA
frame number
given UL CC5
with 2 PDCH
allocation | +|------------|--------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 | (N+13) mod
2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
Or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648
Or
(N+47 or N+48)
mod 2715648
or
(N+52) mod
2715648
or
(N+56 or N+57)
mod 2715648
or
(N+60 or N+61)
mod 2715648 | (N+13) mod
2715648
or
(N+17 or N+18)
mod 2715648
or
(N+21 or N+22)
mod 2715648
or
(N+26) mod
2715648
Or
(N+30 or N+31)
mod 2715648
or
(N+34 or N+35)
mod 2715648
or
(N+39) mod
2715648
or
(N+43 or N+44)
mod 2715648
Or
(N+47 or N+48)
mod 2715648
or
(N+52) mod
2715648
or
(N+56 or N+57)
mod 2715648
or
(N+60 or N+61)
mod 2715648
Or
N+65) mod
2715648
or
(N+69 or N+70)
mod 2715648
or
(N+73 or N+74)
mod 2715648
or
(N+78) mod
2715648
Or
(N+82 or N+83)
mod 2715648
or
(N+86 or N+87)
mod 2715648
or
(N+91) mod
2715648
or | + +| | | | | | | | +|--|--|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | | (N+95 or N+96)
mod 2715648
Or
(N+99 or
N+100) mod
2715648
or
(N+104) mod
2715648
or
(N+108 or
N+109) mod
2715648
or
(N+112 or
N+113) mod
2715648 | +|--|--|--|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | +|-----|----------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 1 | (N+17 or N+18) mod 2715648 | (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 Or (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 Or (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 Or (N+99 or N+100) mod 2715648 or (N+104) mod 2715648 or (N+108 or N+109) mod 2715648 or (N+112 or N+113) mod 2715648 | (N+117) mod 2715648 or (N+121 or N+122) mod 2715648 or (N+125 or N+126) mod 2715648 or (N+130) mod 2715648 Or (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 or (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 Or (N+151 or N+152) mod 2715648 or (N+156) mod 2715648 or (N+160 or N+161) mod 2715648 or (N+164 or N+165) mod 2715648 Or (N+169) mod 2715648 or (N+173 or N+174) mod 2715648 or (N+177 or N+178) mod 2715648 or (N+182) mod 2715648 Or (N+186 or N+187) mod 2715648 or (N+190 or N+191) mod 2715648 or (N+195) mod 2715648 | +|-----|----------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | +|--|--|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | | or
(N+199 or
N+200) mod
2715648
Or
(N+203 or
N+204) mod
2715648
or
(N+208) mod
2715648
or
(N+212 or
N+213) mod
2715648
or
(N+216 or
N+217) mode
2715648 | +|--|--|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | +|-----|-------------------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 1 0 | (N+21 or N+22)
mod 2715648 | (N+30 or N+31)
mod 2715648
or
(N+34 or N+35 )
mod 2715648 | (N+47 or N+48)
mod 2715648
or
(N+52) mod
2715648
or
(N+56 or N+57)
mod 2715648
or
(N+60 or N+61)
mod 2715648 | (N+82 or N+83)
mod 2715648
or
(N+86 or N+87)
mod 2715648
or
(N+91) mod
2715648
or
(N+95 or N+96)
mod 2715648
Or
(N+99 or
N+100) mod
2715648
or
(N+104) mod
2715648
or
(N+108 or
N+109) mod
2715648
or
(N+112 or
N+113) mod
2715648 | (N+117) mod
2715648
or
(N+121 or
N+122) mod
2715648
or
(N+125 or
N+126) mod
2715648
or
(N+130) mod
2715648
Or
(N+134 or
N+135) mod
2715648
or
(N+138 or
N+139) mod
2715648
or
(N+143) mod
2715648
or
(N+147 or
N+148) mod
2715648
Or
(N+151 or
N+152) mod
2715648
or
(N+156) mod
2715648
or
(N+160 or
N+161) mod
2715648
or
(N+164 or
N+165) mode
2715648 | Reserved | +|-----|-------------------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| + +| | | | | | | | +|-----|--------------------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| 1 1 | (N+26) mod 2715648 | (N+39) mod 2715648
or
(N+43 or N+44) mod 2715648 | (N+65) mod 2715648
or
(N+69 or N+70) mod 2715648
or
(N+73 or N+74) mod 2715648
or
(N+78) mod 2715648 | (N+117) mod 2715648
or
(N+121 or N+122) mod 2715648
or
(N+125 or N+126) mod 2715648
or
(N+130) mod 2715648
Or
(N+134 or N+135) mod 2715648
or
(N+138 or N+139) mod 2715648
or
(N+143) mod 2715648
or
(N+147 or N+148) mod 2715648 | (N+169) mod 2715648
or
(N+173 or N+174) mod 2715648
or
(N+177 or N+178) mod 2715648
or
(N+182) mod 2715648
Or
(N+186 or N+187) mod 2715648
or
(N+190 or N+191) mod 2715648
or
(N+195) mod 2715648
or
(N+199 or N+200) mod 2715648
Or
(N+203 or N+204) mod 2715648
or
(N+208) mod 2715648
or
(N+212 or N+213) mod 2715648
or
(N+216 or N+217) mode 2715648 | Reserved | +|-----|--------------------|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| + +NOTE: Each RRBP value in Table 10.4.5.6 will assign only one valid uplink block given the downlink coverage class used, i.e. when the poll is received, and the uplink coverage class used. See 3GPP TS 45.002 [13] for the coverage class dependent channel mappings. + +#### 10.4.5.1 Special requirements in dual transfer mode + +If the mobile station in dual transfer mode is using PDCH/H, where the *exclusive allocation is required, special requirements apply* when the mobile station receives a valid RRBP field in a downlink RLC/MAC block: + +- The mobile station may disregard the actual value of a valid RRBP field. The mobile station shall respond to the polling request at the TDMA frame number specified by one of the allowed RRBP values, regardless of which value that was actually received. +- If the mobile station receives more than one RLC/MAC block with a valid RRBP field, the mobile station shall respond to each one of the polling requests with a separate PACKET CONTROL ACKNOWLEDGEMENT message or PACCH block to the network. +- When the mobile station responds with a PACKET CONTROL ACKNOWLEDGEMENT message to a valid RRBP field, the mobile station shall use the RLC/MAC control block format. That is regardless of the CONTROL\_ACK\_TYPE parameter received in the broadcast information of the cell or the TYPE\_OF\_ACK parameter received in a PACKET POLLING REQUEST message. + +If the mobile station in dual transfer mode is not using PDCH/H, the *normal requirements apply* when the mobile station receives a valid RRBP field in a downlink RLC/MAC block. + +### 10.4.6 Countdown Value (CV) field + +The Countdown Value (CV) field is sent by the mobile station to allow the network to calculate the number of RLC data blocks remaining for the current uplink RLC entity. The CV value shall be calculated according to the process described in sub-clause 9.3.1. The CV field is 4 bits in length and is encoded as a binary number with range 0 to 15. + +A mobile station with an uplink EC TBF is required to send the Countdown Value in an RLC uplink data block in order to inform the network that there are more remaining RLC data blocks for the uplink EC TBF than it has previously signalled to the network. When transmitting the last RLC data block, the CV equal to zero shall always be included. The Follow-On Indicator (FOI) shall indicate the presence of a valid CV field. + +### 10.4.6a Follow-On Indicator field (FOI) + +The Follow-On Indicator bit is sent from the mobile station to the network to indicate the presence of a valid Countdown Value field in the uplink RLC data block header during an uplink EC TBF. + +**Table 10.4.6a.1: Follow On Indicator field** + +| bit
2 | FOI | +|----------|-----------------------------| +| 0 | Countdown Value not present | +| 1 | Countdown Value present | + +### 10.4.7 Payload Type field + +The Payload Type field shall indicate the type of data contained in remainder of the RLC/MAC block. The encoding of the Payload Type field is shown in table 10.4.7.1. + +**Table 10.4.7.1: Payload Type field** + +| bit
8 7 | Payload Type | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 | RLC/MAC block contains an RLC data block | +| 0 1 | RLC/MAC block contains an RLC/MAC control block that does not include the optional octets of the RLC/MAC control header | +| 1 0 | In the downlink direction, the RLC/MAC block contains an RLC/MAC control block that includes the optional first octet of the RLC/MAC control header.
In the uplink direction, this value is reserved. | +| 1 1 | Reserved. In this version of the protocol, the mobile station shall ignore all fields of the RLC/MAC block except for the USF field | + +In downlink RLC/MAC Control blocks encoded using MSC-0 the encoding of the Payload Type field is shown in table 10.4.7.2. + +**Table 10.4.7.2: Payload Type field, MCS-0** + +| bit
8 | Payload Type | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | RLC/MAC block contains an RLC/MAC control block that does not include the optional octets of the RLC/MAC control block message shown in figure 10.3.1.2.1 | +| 1 | RLC/MAC block contains an RLC/MAC control block that includes at least the first optional octet of the RLC/MAC control block message shown in figure 10.3.1.2.1 | + +In downlink RLC/MAC Control blocks on EC-PACCH/D, the encoding of the Payload Type field is shown in table 10.4.7.3. + +**Table 10.4.7.3: Payload Type field on EC-PACCH/D** + +| bit 7 | Payload Type | +|-------|-------------------------------------------------------------------------------------------------------| +| 0 | The RLC/MAC control block, including the normal MAC header, is coded according to figure 10.3.1.3.1 | +| 1 | The RLC/MAC control block, including the extended MAC header, is coded according to figure 10.3.1.3.2 | + +### 10.4.8 Final block indicator (FBI) bit + +The Final block indicator (FBI) bit indicates that the downlink RLC data block is the last RLC data block of the downlink TBF. + +**Table 10.4.8.1: Final block indicator bit** + +| bit 1 | Final block indicator | +|-------|-------------------------------------------------| +| 0 | Current block is not last RLC data block in TBF | +| 1 | Current block is last RLC data block in TBF | + +### 10.4.8a Coding and Puncturing Scheme indicator field (CPS) + +In EGPRS and EC-GSM-IoT headers, the Coding and Puncturing Scheme indicator field is used to indicate the kind of channel coding and puncturing used for data blocks (see 3GPP TS 45.003). + +#### 10.4.8a.1 Header type 1 + +**Table 10.4.8a.1.1: Coding and Puncturing Scheme indicator field for Header type 1 in EGPRS TBF, EC TBF or downlink EGPRS2 TBF** + +| bits 54321 | CPS | +|------------|--------------------------------------------------| +| 00000 | (MCS-9/P1 ; MCS-9/P1) (see NOTE 2) | +| 00001 | (MCS-9/P1 ; MCS-9/P2) (see NOTE 2) | +| 00010 | (MCS-9/P1 ; MCS-9/P3) (see NOTE 2) | +| 00100 | (MCS-9/P2 ; MCS-9/P1) (see NOTE 2) | +| 00101 | (MCS-9/P2 ; MCS-9/P2) (see NOTE 2) | +| 00110 | (MCS-9/P2 ; MCS-9/P3) (see NOTE 2) | +| 01000 | (MCS-9/P3 ; MCS-9/P1) (see NOTE 2) | +| 01001 | (MCS-9/P3 ; MCS-9/P2) (see NOTE 2) | +| 01010 | (MCS-9/P3 ; MCS-9/P3) (see NOTE 2) | +| 01011 | (MCS-8/P1 ; MCS-8/P1) | +| 01100 | (MCS-8/P1 ; MCS-8/P2) | +| 01101 | (MCS-8/P1 ; MCS-8/P3) | +| 01110 | (MCS-8/P2 ; MCS-8/P1) | +| 01111 | (MCS-8/P2 ; MCS-8/P2) | +| 10000 | (MCS-8/P2 ; MCS-8/P3) | +| 10001 | (MCS-8/P3 ; MCS-8/P1) | +| 10010 | (MCS-8/P3 ; MCS-8/P2) | +| 10011 | (MCS-8/P3 ; MCS-8/P3) | +| 10100 | (MCS-7/P1 ; MCS-7/P1) | +| 10101 | (MCS-7/P1 ; MCS-7/P2) | +| 10110 | (MCS-7/P1 ; MCS-7/P3) | +| 10111 | (MCS-7/P2 ; MCS-7/P1) | +| 11000 | (MCS-7/P2 ; MCS-7/P2) | +| 11001 | (MCS-7/P2 ; MCS-7/P3) | +| 11010 | (MCS-7/P3 ; MCS-7/P1) | +| 11011 | (MCS-7/P3 ; MCS-7/P2) | +| 11100 | (MCS-7/P3 ; MCS-7/P3) | +| | All the other values are reserved for future use | + +NOTE 1: The bit numbering is relative to the field position. +NOTE 2: MCS-9 shall only be used for an EGPRS TBF, for an EC TBF or for a downlink EGPRS2-B TBF. + +#### 10.4.8a.2 Header type 2 + +In EGPRS, EC-GSM-IoT and in EGPRS2-A uplink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.2.1. + +**Table 10.4.8a.2.1: Coding and Puncturing Scheme indicator field for Header type 2 in EGPRS TBF, EC TBF or uplink EGPRS2-A TBF** + +| bits
321 | (first block)
CPS | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| 000 | MCS-6/P1 | +| 001 | MCS-6/P2 | +| 010 | MCS-6/P1 with 6 octets padding (see NOTE 2) | +| 011 | MCS-6/P2 with 6 octets padding (see NOTE 2) | +| 100 | MCS-5/P1 | +| 101 | MCS-5/P2 | +| 110 | MCS-6/P1 with 10 octets padding (see NOTE 3) | +| 111 | MCS-6/P2 with 10 octets padding (see NOTE 3) | +| NOTE 1: The bit numbering is relative to the field position. | | +| NOTE 2: MCS-6 with 6 octets padding shall only be used for an EGPRS TBF or, in case of an uplink EGPRS2-A TBF, for retransmission of blocks originally transmitted using EGPRS. | | +| NOTE 3: MCS-6 with 10 octets padding shall only be used for an uplink EGPRS2-A TBF or, in case of an uplink EGPRS TBF, for retransmission of blocks originally transmitted using EGPRS2-A. | | + +In EGPRS2 downlink, if the Downlink EGPRS Level assigned (see Table 11.2.7.1 and Table 12.10f.1) is EGPRS2-A, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.2.2. + +**Table 10.4.8a.2.2: Coding and Puncturing Scheme indicator field for Header type 2 in downlink EGPRS2-A TBF** + +| bits
321 | CPS | +|--------------------------------------------------------------------------------------------------------------------------|-----------------------| +| 000 | MCS-6/P1 (see NOTE 2) | +| 001 | MCS-6/P2 (see NOTE 2) | +| 010 | DAS-5/P1 | +| 011 | DAS-5/P2 | +| 100 | DAS-6/P1 | +| 101 | DAS-6/P2 | +| 110 | DAS-7/P1 | +| 111 | DAS-7/P2 | +| NOTE 1: The bit numbering is relative to the field position. | | +| NOTE 2: In EGPRS2-A downlink, MCS-6 shall be used only for retransmissions of blocks originally transmitted using EGPRS. | | + +In EGPRS2 downlink, if the Downlink EGPRS Level assigned (see Table 11.2.7.1 and Table 12.10f.1) is EGPRS2-B, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.2.3. + +**Table 10.4.8a.2.3: Coding and Puncturing Scheme indicator field for Header type 2 in downlink EGPRS2-B TBF** + +| bits
321 | CPS | +|------------------------------------------------------------|--------------------------------------------------| +| 000 | MCS-6/P1 | +| 001 | MCS-6/P2 | +| 010 | DAS-5/P1 | +| 011 | DAS-5/P2 | +| 100 | DAS-6/P1 | +| 101 | DAS-6/P2 | +| | All the other values are reserved for future use | +| NOTE: The bit numbering is relative to the field position. | | + +#### 10.4.8a.3 Header type 3 + +**Table 10.4.8a.3.1: Coding and Puncturing Scheme indicator field for Header type 3 (non EC TBF)** + +| bits
4321 | First block
CPS | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| 0000 | MCS-4/P1 | +| 0001 | MCS-4/P2 | +| 0010 | MCS-4/P3 | +| 0011 | MCS-3/P1 | +| 0100 | MCS-3/P2 | +| 0101 | MCS-3/P3 | +| 0110 | MCS-3/P1 with padding | +| 0111 | MCS-3/P2 with padding | +| 1000 | MCS-3/P3 with padding | +| 1001 | MCS-2/P1 | +| 1010 | MCS-2/P2 | +| 1011 | MCS-1/P1 | +| 1100 | MCS-1/P2 | +| 1101 | MCS-2/P1 with padding (see NOTE 2) | +| 1110 | MCS-2/P2 with padding (see NOTE 2) | +| 1111 | MCS-0 (see NOTE 3) | +| NOTE 1: The bit numbering is relative to the field position. | | +| NOTE 2: MCS-2 with padding shall only be used for a downlink EGPRS2-A TBF or, in case of a downlink EGPRS TBF, for retransmissions of blocks originally transmitted using EGPRS2-A. | | +| NOTE 3: MCS-0 shall only be used for a downlink TBF. | | + +The number of padding octets for uplink is indicated by the SPB field (see sub clause 10.4.8b). + +In EC-GSM-IoT, the CPS field for MCS-1-4 in Header type 3 indicates the kind of channel coding and puncturing used for data block as defined in Table 10.4.8a.3.2. + +**Table 10.4.8a.3.2: CPS field for Header type 3 in EC TBF.** + +| bits
3 2 1 | CPS | +|---------------|-----------------------| +| 0 0 0 | MCS-4/P1 | +| 0 0 1 | MCS-4/P2 | +| 0 1 0 | MCS-3/P1 | +| 0 1 1 | MCS-3/P2 | +| 1 0 0 | MCS-3/P1 with padding | +| 1 0 1 | MCS-3/P2 with padding | +| 1 1 0 | MCS-2/P1 | +| 1 1 1 | MCS-1/P1 | + +A mobile station with an EC TBF of uplink coverage class CC2, CC3 or CC4 and capable of supporting CC5 on the uplink shall indicate the capability(CC5) to BSS using the CPS bit code in header type 3. The BSS shall interpret the CPS field of header type 3 as Higher Coverage Class Coding Scheme(HCS) field, if the uplink coverage class of EC TBF is CC2, CC3 or CC4, as defined in Table 10.4.8a.3.2a. + +**Table 10.4.8a.3.2a: HCS field for Header type 3 in EC TBF for higher UL coverage classes than CC1.** + +| bits
3 2 1 | HCS | +|---------------|----------------------| +| 0 0 0 | reserved | +| ... | ... | +| 1 0 1 | reserved | +| 1 1 0 | CC5 is supported | +| 1 1 1 | CC5 is not supported | + +#### 10.4.8a.4 Header type 4 + +In downlink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.4.1. + +**Table 10.4.8a.4.1: Coding and Puncturing Scheme indicator field for Header type 4 in downlink** + +| bits
4 3 2 1 | CPS | +|-----------------|------------------------------------------------------| +| 0000 | DAS-9/P1 ; DAS-9/P1 | +| 0001 | DAS-9/P1 ; DAS-9/P2 | +| 0010 | DAS-9/P1 ; DAS-9/P3 | +| 0011 | DAS-9/P2 ; DAS-9/P1 | +| 0100 | DAS-9/P2 ; DAS-9/P2 | +| 0101 | DAS-9/P2 ; DAS-9/P3 | +| 0110 | DAS-9/P3 ; DAS-9/P1 | +| 0111 | DAS-9/P3 ; DAS-9/P2 | +| 1000 | DAS-9/P3 ; DAS-9/P3 | +| 1001 | DAS-8/P1 ; DAS-8/P1 | +| 1010 | DAS-8/P1 ; DAS-8/P2 | +| 1011 | DAS-8/P2 ; DAS-8/P1 | +| 1100 | DAS-8/P2 ; DAS-8/P2 | +| | All the other values are reserved for future use | +| NOTE: | The bit numbering is relative to the field position. | + +In uplink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.4.2. + +**Table 10.4.8a.4.2: Coding and Puncturing Scheme indicator field for Header type 4 in uplink** + +| bits
54321 | CPS | +|------------------------------------------------------------|--------------------------------------------------| +| 00000 | (UAS-9/P1 ; UAS-9/P1) | +| 00001 | (UAS-9/P1 ; UAS-9/P2) | +| 00010 | (UAS-9/P1 ; UAS-9/P3) | +| 00011 | (UAS-9/P2 ; UAS-9/P1) | +| 00100 | (UAS-9/P2 ; UAS-9/P2) | +| 00101 | (UAS-9/P2 ; UAS-9/P3) | +| 00110 | (UAS-9/P3 ; UAS-9/P1) | +| 00111 | (UAS-9/P3 ; UAS-9/P2) | +| 01000 | (UAS-9/P3 ; UAS-9/P3) | +| 01001 | (UAS-8/P1 ; UAS-8/P1) | +| 01010 | (UAS-8/P1 ; UAS-8/P2) | +| 01011 | (UAS-8/P2 ; UAS-8/P1) | +| 01100 | (UAS-8/P2 ; UAS-8/P2) | +| 01101 | (UAS-7/P1 ; UAS-7/P1) | +| 01110 | (UAS-7/P1 ; UAS-7/P2) | +| 01111 | (UAS-7/P2 ; UAS-7/P1) | +| 10000 | (UAS-7/P2 ; UAS-7/P2) | +| | All the other values are reserved for future use | +| NOTE: The bit numbering is relative to the field position. | | + +#### 10.4.8a.5 Header type 5 + +In downlink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.5.1 for EGPRS2-A TBF and 10.4.8a.5.1a for EGPRS2-B TBF and table 10.4.8a.5.3. + +**Table 10.4.8a.5.1: Bit 6 of Coding and Puncturing Scheme indicator field for Header type 5 in downlink for EGPRS2-A TBF** + +| bit
6 | CPS | +|------------------------------------------------------------|--------| +| 0 | DAS-11 | +| 1 | DAS-12 | +| NOTE: The bit numbering is relative to the field position. | | + +**Table 10.4.8a.5.1a: Bit 6 of Coding and Puncturing Scheme indicator field for Header type 5 in downlink for EGPRS2-B TBF** + +| bit
6 | CPS | +|------------------------------------------------------------|---------------------| +| 0 | DAS-11 | +| 1 | DAS-12 with padding | +| NOTE: The bit numbering is relative to the field position. | | + +For DAS-12 with padding, the first 8 data octets of the RLC data block are padded with zeros. + +In uplink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.5.2 and table 10.4.8a.5.3. + +**Table 10.4.8a.5.2: Bit 6 of Coding and Puncturing Scheme indicator field for Header type 5 in uplink** + +| bit
6 | CPS | +|------------------------------------------------------------|--------| +| 0 | UAS-10 | +| 1 | UAS-11 | +| NOTE: The bit numbering is relative to the field position. | | + +**Table 10.4.8a.5.3: Bits 1 to 5 of Coding and Puncturing Scheme indicator field for Header type 5 common for downlink and uplink** + +| bits
54321 | CPS | +|------------------------------------------------------------|--------------------------------------------------| +| 00000 | (P1 ; P1 ; P1) | +| 00001 | (P1 ; P1 ; P2) | +| 00010 | (P1 ; P1 ; P3) | +| 00011 | (P1 ; P2 ; P1) | +| 00100 | (P1 ; P2 ; P2) | +| 00101 | (P1 ; P2 ; P3) | +| 00110 | (P1 ; P3 ; P1) | +| 00111 | (P1 ; P3 ; P2) | +| 01000 | (P1 ; P3 ; P3) | +| 01001 | (P2 ; P1 ; P1) | +| 01010 | (P2 ; P1 ; P2) | +| 01011 | (P2 ; P1 ; P3) | +| 01100 | (P2 ; P2 ; P1) | +| 01101 | (P2 ; P2 ; P2) | +| 01110 | (P2 ; P2 ; P3) | +| 01111 | (P2 ; P3 ; P1) | +| 10000 | (P2 ; P3 ; P2) | +| 10001 | (P2 ; P3 ; P3) | +| 10010 | (P3 ; P1 ; P1) | +| 10011 | (P3 ; P1 ; P2) | +| 10100 | (P3 ; P1 ; P3) | +| 10101 | (P3 ; P2 ; P1) | +| 10110 | (P3 ; P2 ; P2) | +| 10111 | (P3 ; P2 ; P3) | +| 11000 | (P3 ; P3 ; P1) | +| 11001 | (P3 ; P3 ; P2) | +| 11010 | (P3 ; P3 ; P3) | +| | All the other values are reserved for future use | +| NOTE: The bit numbering is relative to the field position. | | + +#### 10.4.8a.6 Header type 6 + +In downlink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.6.1. + +**Table 10.4.8a.6.1: Coding and Puncturing Scheme indicator field for Header type 6 in downlink** + +| bits
321 | CPS | +|------------------------------------------------------------|--------------------------------------------------| +| 000 | DBS-5 P1 | +| 001 | DBS-5 P2 | +| 010 | DBS-6 P1 | +| 011 | DBS-6 P2 | +| | All the other values are reserved for future use | +| NOTE: The bit numbering is relative to the field position. | | + +In uplink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.6.2. + +**Table 10.4.8a.6.2: Coding and Puncturing Scheme indicator field for Header type 6 in uplink** + +| bits
321 | CPS | +|------------------------------------------------------------|--------------------------------------------------| +| 000 | UBS-5 P1 | +| 001 | UBS-5 P2 | +| 010 | UBS-6 P1 | +| 011 | UBS-6 P2 | +| 100 | UBS-6 P1 with padding | +| 101 | UBS-6 P2 with padding | +| | All the other values are reserved for future use | +| NOTE: The bit numbering is relative to the field position. | | + +#### 10.4.8a.7 Header type 7 + +In downlink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.7.1 and table 10.4.8a.7.3. + +**Table 10.4.8a.7.1: Bit 4 of Coding and Puncturing Scheme indicator field for Header type 7 in downlink** + +| bit
4 | CPS | +|------------------------------------------------------------|------------| +| 0 | DBS-7 | +| 1 | DBS-8 | +| NOTE: The bit numbering is relative to the field position. | | + +In uplink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.7.2 and table 10.4.8a.7.3. + +**Table 10.4.8a.7.2: Bit 4 of Coding and Puncturing Scheme indicator field for Header type 7 in downlink** + +| bit
4 | CPS | +|------------------------------------------------------------|------------| +| 0 | UBS-7 | +| 1 | UBS-8 | +| NOTE: The bit numbering is relative to the field position. | | + +**Table 10.4.8a.7.3: Bit 1 and 3 of Coding and Puncturing Scheme indicator field for Header type 7 common for downlink and uplink** + +| bits
321 | CPS | +|------------------------------------------------------------|------------------------| +| 000 | (P1 ; P1) | +| 001 | (P1 ; P2) | +| 010 | (P2 ; P1) | +| 011 | (P2 ; P2) | +| 100 | (P1 ; P1) with padding | +| 101 | (P1 ; P2) with padding | +| 110 | (P2 ; P1) with padding | +| 111 | (P2 ; P2) with padding | +| NOTE: The bit numbering is relative to the field position. | | + +#### 10.4.8a.8 Header type 8 + +The Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.8.1 for uplink and table 10.4.8a.8.2 for downlink. DBS-9 and DBS-10, and also UBS-9 and UBS-10 use different modulations hence the CPS field need not distinguish between these coding schemes. + +**Table 10.4.8a.8.1: Coding and Puncturing Scheme indicator field for +Header type 8 in uplink** + +| bits
654321 | CPS | +|----------------|--------------------------------------------------| +| 000000 | (P1 ; P1 ; P1) | +| 000001 | (P1 ; P1 ; P2) | +| 000010 | (P1 ; P1 ; P3) | +| 000100 | (P1 ; P2 ; P1) | +| 000101 | (P1 ; P2 ; P2) | +| 000110 | (P1 ; P2 ; P3) | +| 001000 | (P1 ; P3 ; P1) | +| 001001 | (P1 ; P3 ; P2) | +| 001010 | (P1 ; P3 ; P3) | +| 001011 | (P2 ; P1 ; P1) | +| 001100 | (P2 ; P1 ; P2) | +| 001101 | (P2 ; P1 ; P3) | +| 001110 | (P2 ; P2 ; P1) | +| 001111 | (P2 ; P2 ; P2) | +| 010000 | (P2 ; P2 ; P3) | +| 010001 | (P2 ; P3 ; P1) | +| 010010 | (P2 ; P3 ; P2) | +| 010011 | (P2 ; P3 ; P3) | +| 010100 | (P3 ; P1 ; P1) | +| 010101 | (P3 ; P1 ; P2) | +| 010110 | (P3 ; P1 ; P3) | +| 010111 | (P3 ; P2 ; P1) | +| 011000 | (P3 ; P2 ; P2) | +| 011001 | (P3 ; P2 ; P3) | +| 011010 | (P3 ; P3 ; P1) | +| 011011 | (P3 ; P3 ; P2) | +| 011100 | (P3 ; P3 ; P3) | +| 011101 | (P1 ; P1 ; P1) with padding | +| 011110 | (P1 ; P1 ; P2) with padding | +| 011111 | (P1 ; P1 ; P3) with padding | +| 100000 | (P1 ; P2 ; P1) with padding | +| 100001 | (P1 ; P2 ; P2) with padding | +| 100010 | (P1 ; P2 ; P3) with padding | +| 100011 | (P1 ; P3 ; P1) with padding | +| 100100 | (P1 ; P3 ; P2) with padding | +| 100101 | (P1 ; P3 ; P3) with padding | +| 100110 | (P2 ; P1 ; P1) with padding | +| 100111 | (P2 ; P1 ; P2) with padding | +| 101000 | (P2 ; P1 ; P3) with padding | +| 101001 | (P2 ; P2 ; P1) with padding | +| 101010 | (P2 ; P2 ; P2) with padding | +| 101011 | (P2 ; P2 ; P3) with padding | +| 101100 | (P2 ; P3 ; P1) with padding | +| 101101 | (P2 ; P3 ; P2) with padding | +| 101110 | (P2 ; P3 ; P3) with padding | +| 101111 | (P3 ; P1 ; P1) with padding | +| 110000 | (P3 ; P1 ; P2) with padding | +| 110001 | (P3 ; P1 ; P3) with padding | +| 110010 | (P3 ; P2 ; P1) with padding | +| 110011 | (P3 ; P2 ; P2) with padding | +| 110100 | (P3 ; P2 ; P3) with padding | +| 110101 | (P3 ; P3 ; P1) with padding | +| 110110 | (P3 ; P3 ; P2) with padding | +| 110111 | (P3 ; P3 ; P3) with padding | +| | All the other values are reserved for future use | + +NOTE: The bit numbering is relative to the field position. + +**Table 10.4.8a.8.2: Coding and Puncturing Scheme indicator field for Header type 8 in downlink** + +| bits
654321 | CPS | +|------------------------------------------------------------|----------------| +| 000000 | (P1 ; P1 ; P1) | +| 000001 | (P1 ; P1 ; P2) | +| 000010 | (P1 ; P1 ; P3) | +| 000100 | (P1 ; P2 ; P1) | +| 000101 | (P1 ; P2 ; P2) | +| 000110 | (P1 ; P2 ; P3) | +| 001000 | (P1 ; P3 ; P1) | +| 001001 | (P1 ; P3 ; P2) | +| 001010 | (P1 ; P3 ; P3) | +| 001011 | (P2 ; P1 ; P1) | +| 001100 | (P2 ; P1 ; P2) | +| 001101 | (P2 ; P1 ; P3) | +| 001110 | (P2 ; P2 ; P1) | +| 001111 | (P2 ; P2 ; P2) | +| 010000 | (P2 ; P2 ; P3) | +| 010001 | (P2 ; P3 ; P1) | +| 010010 | (P2 ; P3 ; P2) | +| 010011 | (P2 ; P3 ; P3) | +| 010100 | (P3 ; P1 ; P1) | +| 010101 | (P3 ; P1 ; P2) | +| 010110 | (P3 ; P1 ; P3) | +| 010111 | (P3 ; P2 ; P1) | +| 011000 | (P3 ; P2 ; P2) | +| 011001 | (P3 ; P2 ; P3) | +| 011010 | (P3 ; P3 ; P1) | +| 011011 | (P3 ; P3 ; P2) | +| 011100 | (P3 ; P3 ; P3) | +| All the other values are reserved for future use | | +| NOTE: The bit numbering is relative to the field position. | | + +#### 10.4.8a.9 Header type 9 + +In downlink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.9.1 and table 10.4.8a.9.3. + +**Table 10.4.8a.9.1: Bit 8 of Coding and Puncturing Scheme indicator field for Header type 9 in downlink** + +| bit
8 | CPS | +|------------------------------------------------------------|--------| +| 0 | DBS-11 | +| 1 | DBS-12 | +| NOTE: The bit numbering is relative to the field position. | | + +In uplink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.9.2 and table 10.4.8a.9.3. + +**Table 10.4.8a.9.2: Bit 8 of Coding and Puncturing Scheme indicator field for Header type 9 in uplink** + +| bit
8 | CPS | +|------------------------------------------------------------|--------| +| 0 | UBS-11 | +| 1 | UBS-12 | +| NOTE: The bit numbering is relative to the field position. | | + +**Table 10.4.8a.9.3: Bits 1 to 7 of Coding and Puncturing Scheme indicator field for +Header type 9 common for downlink and uplink** + +| bits
7654321 | CPS | +|-----------------|--------------------| +| 0000000 | (P1 ; P1 ; P1; P1) | +| 0000001 | (P1 ; P1 ; P1; P2) | +| 0000010 | (P1 ; P1 ; P1; P3) | +| 0000011 | (P1 ; P1 ; P2; P1) | +| 0000100 | (P1 ; P1 ; P2; P2) | +| 0000101 | (P1 ; P1 ; P2; P3) | +| 0000110 | (P1 ; P1 ; P3; P1) | +| 0000111 | (P1 ; P1 ; P3; P2) | +| 0001000 | (P1 ; P1 ; P3; P3) | +| 0001001 | (P1 ; P2 ; P1; P1) | +| 0001010 | (P1 ; P2 ; P1; P2) | +| 0001011 | (P1 ; P2 ; P1; P3) | +| 0001100 | (P1 ; P2 ; P2; P1) | +| 0001101 | (P1 ; P2 ; P2; P2) | +| 0001110 | (P1 ; P2 ; P2; P3) | +| 0001111 | (P1 ; P2 ; P3; P1) | +| 0010000 | (P1 ; P2 ; P3; P2) | +| 0010001 | (P1 ; P2 ; P3; P3) | +| 0010010 | (P1 ; P3 ; P1; P1) | +| 0010011 | (P1 ; P3 ; P1; P2) | +| 0010100 | (P1 ; P3 ; P1; P3) | +| 0010101 | (P1 ; P3 ; P2; P1) | +| 0010110 | (P1 ; P3 ; P2; P2) | +| 0010111 | (P1 ; P3 ; P2; P3) | +| 0011000 | (P1 ; P3 ; P3; P1) | +| 0011001 | (P1 ; P3 ; P3; P2) | +| 0011010 | (P1 ; P3 ; P3; P3) | +| 0011011 | (P2 ; P1 ; P1; P1) | +| 0011100 | (P2 ; P1 ; P1; P2) | +| 0011101 | (P2 ; P1 ; P1; P3) | +| 0011110 | (P2 ; P1 ; P2; P1) | +| 0011111 | (P2 ; P1 ; P2; P2) | +| 0100000 | (P2 ; P1 ; P2; P3) | +| 0100001 | (P2 ; P1 ; P3; P1) | +| 0100010 | (P2 ; P1 ; P3; P2) | +| 0100011 | (P2 ; P1 ; P3; P3) | +| 0100100 | (P2 ; P2 ; P1; P1) | +| 0100101 | (P2 ; P2 ; P1; P2) | +| 0100110 | (P2 ; P2 ; P1; P3) | +| 0100111 | (P2 ; P2 ; P2; P1) | +| 0101000 | (P2 ; P2 ; P2; P2) | +| 0101001 | (P2 ; P2 ; P2; P3) | +| 0101010 | (P2 ; P2 ; P3; P1) | +| 0101011 | (P2 ; P2 ; P3; P2) | +| 0101100 | (P2 ; P2 ; P3; P3) | +| 0101101 | (P2 ; P3 ; P1; P1) | +| 0101110 | (P2 ; P3 ; P1; P2) | +| 0101111 | (P2 ; P3 ; P1; P3) | +| 0110000 | (P2 ; P3 ; P2; P1) | +| 0110001 | (P2 ; P3 ; P2; P2) | +| 0110010 | (P2 ; P3 ; P2; P3) | +| 0110011 | (P2 ; P3 ; P3; P1) | +| 0110100 | (P2 ; P3 ; P3; P2) | +| 0110101 | (P2 ; P3 ; P3; P3) | +| 0110110 | (P3 ; P1 ; P1; P1) | +| 0110111 | (P3 ; P1 ; P1; P2) | +| 0111000 | (P3 ; P1 ; P1; P3) | +| 0111001 | (P3 ; P1 ; P2; P1) | +| 0111010 | (P3 ; P1 ; P2; P2) | +| 0111011 | (P3 ; P1 ; P2; P3) | +| 0111100 | (P3 ; P1 ; P3; P1) | +| 0111101 | (P3 ; P1 ; P3; P2) | +| 0111110 | (P3 ; P1 ; P3; P3) | + +| | | +|---------|----------------------------------------------| +| 0111111 | (P3 ; P2 ; P1; P1) | +| 1000000 | (P3 ; P2 ; P1; P2) | +| 1000001 | (P3 ; P2 ; P1; P3) | +| 1000010 | (P3 ; P2 ; P2; P1) | +| 1000011 | (P3 ; P2 ; P2; P2) | +| 1000100 | (P3 ; P2 ; P2; P3) | +| 1000101 | (P3 ; P2 ; P3; P1) | +| 1000110 | (P3 ; P2 ; P3; P2) | +| 1000111 | (P3 ; P2 ; P3; P3) | +| 1001000 | (P3 ; P3 ; P1; P1) | +| 1001001 | (P3 ; P3 ; P1; P2) | +| 1001010 | (P3 ; P3 ; P1; P3) | +| 1001011 | (P3 ; P3 ; P2; P1) | +| 1001100 | (P3 ; P3 ; P2; P2) | +| 1001101 | (P3 ; P3 ; P2; P3) | +| 1001110 | (P3 ; P3 ; P3; P1) | +| 1001111 | (P3 ; P3 ; P3; P2) | +| 1010000 | (P3 ; P3 ; P3; P3) | +| | All other values are reserved for future use | + +#### 10.4.8a.10 Header type 10 + +In downlink, the Coding and Puncturing Scheme indicator field indicates the kind of channel coding and puncturing used for data block as defined in table 10.4.8a.10.1 for EGPRS2-A TBF and in table 10.4.8a.10.2 for EGPRS2-B TBF. + +**Table 10.4.8a.10.1: Coding and Puncturing Scheme indicator field for Header type 10 in downlink EGPRS2-A TBF** + +| bits
21 | CPS | +|------------------------------------------------------------|-----------------------| +| 00 | DAS-10/P1 ; DAS-10/P1 | +| 01 | DAS-10/P1 ; DAS-10/P2 | +| 10 | DAS-10/P2 ; DAS-10/P1 | +| 11 | DAS-10/P2 ; DAS-10/P2 | +| NOTE: The bit numbering is relative to the field position. | | + +**Table 10.4.8a.10.2: Coding and Puncturing Scheme indicator field for Header type 10 in downlink EGPRS2-B TBF** + +| bits
21 | CPS | +|------------------------------------------------------------|-----------------------------------------| +| 00 | DAS-10/P1 ; DAS-10/P1 both with padding | +| 01 | DAS-10/P1 ; DAS-10/P2 both with padding | +| 10 | DAS-10/P2 ; DAS-10/P1 both with padding | +| 11 | DAS-10/P2 ; DAS-10/P2 both with padding | +| NOTE: The bit numbering is relative to the field position. | | + +For DAS-10 with padding, the first 8 data octets of the RLC data block are padded with zeros. + +### 10.4.8b Split Block indicator field (SPB) + +In EGPRS uplink, EC-GSM-IoT uplink and EGPRS2 uplink, the Split Block indicator is only used in header type 3 to indicate if some user data is retransmitted using 2 block resegmentation (see clause 9). + +**Table 10.4.8b.1: Split Block indicator field (uplink)** + +| bits
2 1 | SPB | +|-------------|-------------------------------------------------------------------------| +| 0 0 | No retransmission | +| 0 1 | Retransmission - first part of block with 10 octet padding | +| 1 0 | Retransmission - first part of block with no padding or 6 octet padding | +| 1 1 | Retransmission - second part of block | +| NOTE: | The bit numbering is relative to the field position. | + +In case of EGPRS, 10 octet padding shall be used only for retransmissions of blocks originally transmitted using EGPRS2-A. In case of EGPRS2-A, 6 octet padding shall be used only for retransmissions of blocks originally transmitted using EGPRS. + +In EGPRS downlink, EC-GSM-IoT downlink and EGPRS2 downlink, the Split Block indicator is only used in header type 3 to indicate if some user data is retransmitted using 2 or 3 block resegmentation (see clause 9). + +**Table 10.4.8b.2: Split Block indicator field (downlink)** + +| bits
2 1 | SPB | +|-------------|-------------------------------------------------------------------------------------------------------------------------| +| 0 0 | No retransmission | +| 0 1 | Retransmission - third part of block (Note 2) | +| 1 0 | Retransmission - first part of block | +| 1 1 | Retransmission - second part of block | +| NOTE 1: | The bit numbering is relative to the field position. | +| NOTE 2: | In EGPRS downlink this code point is only used when retransmitting blocks at EGPRS level change from EGPRS2-A to EGPRS. | + +### 10.4.9 TLLI Indicator (TI) bit + +The TLLI Indicator (TI) bit indicates the presence of an optional TLLI/G-RNTI field within the RLC data block. + +**Table 10.4.9.1: TLLI Indicator (TI) bit** + +| bit 1 | TLLI indicator (TI) bit | +|-------|----------------------------------| +| 0 | TLLI/G-RNTI field is not present | +| 1 | TLLI/G-RNTI field is present | + +### 10.4.9a Address Control (AC) bit + +The Address Control (AC) bit is used to indicate the presence of the optional TFI/D octet in the header of downlink RLC/MAC control blocks. + +**Table 10.4.9a.1: Address Control (AC) bit** + +| bit 1 | Address Control (AC) bit | +|-------|----------------------------| +| 0 | TFI/D octet is not present | +| 1 | TFI/D octet is present | + +### 10.4.9b Final Segment (FS) bit + +The Final Segment (FS) bit indicates that the downlink RLC/MAC control block contains the final segment of an RLC/MAC control message except when it is sent using extended RLC/MAC control message segmentation. In case of extended RLC/MAC control message segmentation, the final segment of an RLC/MAC control message is indicated with the FSe bit as defined in sub-clause 10.4.9e while the FS bit is set to '0' (see sub-clauses 9.1.12a and 10.4.12b). + +**Table 10.4.9b.1: Final Segment (FS) bit** + +| bit 1 | Final Segment (FS) bit | +|-------|--------------------------------------------------------------------------------| +| 0 | Current block does not contain the final segment of an RLC/MAC control message | +| 1 | Current block contains the final segment of an RLC/MAC control message | + +NOTE: The bit numbering is relative to the field position. + +### 10.4.9c Radio Transaction Identifier (RTI) field + +The Radio Transaction Identifier (RTI) field is used to group the downlink RLC/MAC control blocks that make up an RLC/MAC control message and identifies the segmented control message sequence with which the downlink RLC/MAC control block is associated. The RTI field is five bits in length with range 0 to 31. + +### 10.4.9d Direction (D) bit + +The Direction (D) bit indicates the direction of the TBF identified by the TFI field in the downlink RLC/MAC control block header. + +**Table 10.4.9d.1: Direction (D) bit** + +| bit 1 | Direction (D) bit | +|-------|-------------------------------------| +| 0 | TFI field identifies an uplink TBF | +| 1 | TFI field identifies a downlink TBF | + +### 10.4.9e Final Segment extension (FSe) bit + +The Final Segment extension (FSe) bit indicates that the downlink RLC/MAC control block contains the final segment of an RLC/MAC control message segmented using extended RLC/MAC control message segmentation (see sub-clauses 9.1.12a and 10.4.12b). The FSe bit is only present from the second RLC/MAC control block onwards. + +**Table 10.4.9e.1: Final Segment extension (FSe) bit** + +| bit 5 | Final Segment extension (FSe) bit | +|-------|--------------------------------------------------------------------------------| +| 0 | Current block does not contain the final segment of an RLC/MAC control message | +| 1 | Current block contains the final segment of an RLC/MAC control message | + +### 10.4.9f Reduced TLLI (rTLLI) + +A mobile station in EC operation that has been indicated to use the enhanced access burst procedure shall only include the TLLI in the first RLC data block of the uplink EC TBF and the rTLLI in the RLC/MAC headers of the remaining RLC data blocks until the contention resolution is completed (see sub-clause 7a.2.1.2). + +### 10.4.9g Reduced TLLI Indicator (RI) + +The RI bit is used to indicate whether the rTLLI field is valid or not valid. + +**Table 10.4.9g.1: Reduced TLLI Indicator (RI)** + +| bit
1 | RI | +|----------|--------------------------| +| 0 | rTLLI field is not valid | +| 1 | rTLLI field is valid | + +### 10.4.10 Temporary Flow Identity (TFI) field + +In the header of an RLC/MAC block for data transfer, the TFI identifies the Temporary Block Flow (TBF) to which the RLC data block belongs. For the downlink and the uplink TFI the TFI field is 5 bits in length and are encoded as a binary number with range 0 to 31. When eTFI is assigned it is 3 bits in length and is encoded as a binary number with range 0 to 7. TFI and eTFI (if assigned) together identify the downlink Temporary Block Flow (TBF). In downlink RLC/MAC control blocks, the TFI identifies the Temporary Block Flow (TBF) to which the RLC/MAC control message contained in the downlink RLC/MAC control block relates. If present, this field indicates the mobile station to which the control message is addressed; all other mobile stations shall analyse the distribution contents, depending on their protocol state, as specified in clauses 5 and 7 of the present document, except if the downlink RLC/MAC control block is sent using an eTFI in which case only the mobile station to which the control message is addressed shall analyse the content. If this field is present and the contents of the control message also contain a TFI addressing the mobile station, the mobile station shall ignore the TFI in the control message contents. If this field is not present all mobile stations shall interpret the contents of the control message, except if the downlink RLC/MAC control block is sent using an eTFI in which case only the mobile stations that support that eTFI shall interpret the contents of the control message. + +If a valid TFI field or valid TFI-eTFI fields (see sub-clause 10.3a.5) are included in a PAN field, they identify the Temporary Block Flow (TBF) being acknowledged. + +### 10.4.10a Power Reduction (PR) field + +The Power Reduction (PR) field indicates the power level reduction of the current RLC block. + +The coding of Power Reduction (PR) field is shown in Table 10.4.10a.1. There is one value of the PR field which indicates that the field shall be ignored by the MS. + +If downlink power control is not used, the MS shall ignore the PR field. + +If downlink power control is used and the PR field is not included in a downlink RLC/MAC control block, the MS shall act as if the block contained a usable PR field with value '0 0'. + +**Table 10.4.10a.1: Power Reduction (PR) field** + +| bit
6 5 | Power Reduction | +|------------|---------------------------------------------------------------| +| 0 0 | 0 dB (included) to 3 dB (excluded) less than BCCH level - P0 | +| 0 1 | 3 dB (included) to 7 dB (excluded) less than BCCH level - P0 | +| 1 0 | 7 dB (included) to 10 dB (included) less than BCCH level - P0 | +| 1 1 | Not usable | + +The Power Reduction (PR) field in a downlink EC-GSM-IoT control block indicates the power level reduction of the current RLC/MAC control block. When PRe is not included, the coding of Power Reduction (PR) field for a downlink EC-GSM-IoT control block is shown in Table 10.4.10a.2. + +**Table 10.4.10a.2: Power Reduction (PR) field for EC-GSM-IoT control blocks** + +| bit
8 | Power Reduction | +|----------|--------------------------------------------------------------| +| 0 | 0 dB (included) to 3 dB (excluded) less than BCCH level - P0 | +| 1 | 3 dB (included) to 7 dB (excluded) less than BCCH level - P0 | + +#### 10.4.10b Power Reduction extension (PRe) field + +The Power Reduction extension (PRe) field indicates the extended power level reduction of the current RLC/MAC control block. The PRe field is only included if the Payload Type, see table 10.4.7.3, is set to 1. + +When included the PRe field, together with the PR field, gives the coding of the power reduction for a downlink EC-GSM-IoT control block as shown in Table 10.4.10b.1. + +**Table 10.4.10b.1: PR bit, PRe bit** + +| PR | PRe | Power Reduction | +|----|-----|------------------------------------------------------------------| +| 0 | 0 | 0 dB (included) to 3 dB (excluded)
less than BCCH level - P0 | +| 1 | 0 | 3 dB (included) to 7 dB (excluded)
less than BCCH level - P0 | +| 0 | 1 | 7 dB (included) to 10 dB (included)
less than BCCH level - P0 | +| 1 | 1 | Reserved | + +### 10.4.11 Extension (E) Bit + +The Extension (E) bit is used to indicate the presence of an optional octet in the RLC data block header. + +**Table 10.4.11.1: Extension (E) bit** + +| bit 1 | E bit | +|-------|-------------------------------------| +| 0 | Extension octet follows immediately | +| 1 | No extension octet follows | + +In *A/Gb mode*, extension (E) bit after the PFI field is used for extensions of the protocol by allowing optional octets in the RLC data block header. However, when extensions of this protocol are developed, networks will treat all unknown optional octets as spare until the E bit of 1. + +### 10.4.12 Block Sequence Number (BSN) field + +The Block Sequence Number (BSN) field carries the sequence absolute Block Sequence Number (BSN') modulo Sequence Number Space (SNS) (32 in EC-GSM-IoT, 128 in GPRS, 2 048 in EGPRS and 8192 in a DLMC configuration) of each RLC data block within the TBF. + +In EC-GSM-IoT, the BSN is 5 bits in length and is encoded as a binary number with range 0 to 31. + +In GPRS, the BSN is 7 bits in length and is encoded as a binary number with range 0 to 127. + +In EGPRS, or in a DLMC configuration where a SNS of 2048 is used (see sub-clause 5.13), the BSN is 11 bits in length and is encoded as a binary number with range 0 to 2 047. + +In a DLMC configuration where a SNS of 8192 is used (see sub-clause 5.13), the BSN is 13 bits in length and is encoded as a binary number with range 0 to 8191. + +In case two to four RLC data blocks are sent within a RLC/MAC block, BSN2 to BSN4 are relative to BSN1, provided the difference between the second to fourth block number and the first block modulo SNS is less than Window Size (WS). + +For example, + +Second block number = [BSN1 + BSN2] modulo SNS + +(e.g. SNS = 2 048, WS = 512, Block A block number = 10 and Block B block number= 2 000 then: + +[Block A - Block B] modulo SNS = 58 < 512; + +[Block B - Block A] modulo SNS = 1 990 > 512; + +Then: Block #1 = Block B and Block #2 = Block A, BSN1 = 2 000 and BSN2 = 58). + +In a DLMC configuration there are restrictions regarding the selection of RLC data blocks for inclusion within a given RLC/MAC block: + +- In the RLC/MAC header for MCS-7, MCS-8 and MCS-9 13 bits for BSN1 and 11 bits for BSN2 are defined. For these MCSs the difference between the two RLC data blocks (Block A and Block B) shall be less than 2048. + - i.e. [Block A - Block B] modulo SNS < 2048 or [Block B - Block A] modulo SNS < 2048 +- In the RLC/MAC header for DAS-11 and DAS-12 13 bits for BSN1, 12 bits for BSN2 and 11 bits for BSN3 are defined. For these MCSs the difference between two of the RLC data blocks (i.e. two out of Block A, B or C) shall be less than 2048. + - i.e. [Block X - Block Y] modulo SNS < 2048 or [Block Y - Block X] modulo SNS < 2048 where X is any one of Block A, B or C, and Y is any of the two remaining blocks. + +For example, + +SNS = 8192, WS = 4096: + +BSN1=2000 (Block B block number=2000) + +BSN2=58 (Block A block number=2058) + +- [Block A – Block B] modulo 8192 = 58 < 4096 +- [Block B – Block A] modulo 8192 = 8133 > 4096 + +then Block C block number shall fulfill [Block C - Block B] modulo SNS < 2048. + +For example Block C block number = 4003, and BSN3=2003 + +- [Block C – Block B] modulo 8192 = 2003 < 2048 + +#### 10.4.12a Reduced Block Sequence Number (RBSN) bit + +The Reduced Block Sequence Number (RBSN) bit carries the sequence number of the downlink RLC/MAC control blocks. The RBSN bit is encoded as a binary number with range 0 to 1. + +### 10.4.12b Reduced Block Sequence Number extension (RBSNe) field + +The Reduced Block Sequence Number extension (RBSNe) field together with the RBSN bit indicate the sequence number of the downlink RLC/MAC control blocks of an RLC/MAC control message segmented using extended RLC/MAC control message segmentation. The RBSNe field is encoded as a binary number with range 0 to 7. Along with the FS bit and the FSe bit, they allow for extended RLC/MAC control message segmentation as shown in table 10.4.12b.1 (see sub-clause 9.1.12a). + +**Table 10.4.12b.1: RBSN bit, FS bit, RBSNe field, FSe bit** + +| RBSN | FS | RBSNe | FSe | | +|------|----|-------|-------|------------------------------------------------| +| 0 | 0 | N/A | N/A | 1 st RLC/MAC control block | +| 1 | 0 | 0 0 0 | 0 | 2 nd RLC/MAC control block | +| 1 | 0 | 0 0 1 | 0 / 1 | 3 rd / last RLC/MAC control block | +| 1 | 0 | 0 1 0 | 0 / 1 | 4 th / last RLC/MAC control block | +| 1 | 0 | 0 1 1 | 0 / 1 | 5 th /last RLC/MAC control block | +| 1 | 0 | 1 0 0 | 0 / 1 | 6 th /last RLC/MAC control block | +| 1 | 0 | 1 0 1 | 0 / 1 | 7 th /last RLC/MAC control block | +| 1 | 0 | 1 1 0 | 0 / 1 | 8 th /last RLC/MAC control block | +| 1 | 0 | 1 1 1 | 1 | 9 th and last RLC/MAC control block | + +### 10.4.13 More (M) bit + +In GPRS TBF mode, the M bit, along with the E bit and the Length Indicator (LI), are used to delimit LLC PDUs within a TBF. When the M bit is present it indicates whether or not another LLC PDU follows the current one within the RLC data block. The function of the M and E bits when they occur in the same octet is defined in table 10.4.13.1. + +In EGPRS TBF mode the M bit is not used, instead a special combination of the LI field is used to indicate presence of following LLC PDUs. + +**Table 10.4.13.1: M bit and E bit** + +| bit
M E | | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 | In Iu mode , the RLC data block belongs to the signalling radio bearer identified by SRBId. In A/Gb mode, if received by the mobile station it shall ignore all fields of the RLC/MAC block except for the fields of the MAC header | +| 0 1 | no LLC data after the current LLC PDU, no more extension octets | +| 1 0 | a new LLC PDU starts after the current LLC PDU and there is another extension octet, which delimits the new LLC PDU | +| 1 1 | a new LLC PDU starts after the current LLC PDU and continues until the end of the RLC information field, no more extension octets | + +### 10.4.14 Length Indicator (LI) field in GPRS TBF mode and DCCH TBF mode (*Iu mode*) + +The Length Indicator is used to delimit Upper Layer PDUs within the RLC data block. Additionally for *Iu mode*, a Length Indicator of value 63 may be used to indicate the presence of filler information within the RLC data block. If the first length indicator in the RLC data block is set to 63, then the entire RLC data block contains filler information. + +A Length Indicator of value 62 is used by a mobile station supporting network sharing to indicate the presence of a *Selected PLMN Index* field (see sub-clause 10.4.27) in the octet immediately following this Length Indicator. In this case, it shall always be the first Length Indicator in the RLC data block. + +A Length Indicator of value 61 is used by a mobile station supporting MS assisted Dedicated Core Network selection and indicates the presence of a DCN-ID value (see sub-clause 10.4.30) in the two octets immediately following this Length Indicator. + +The first Length Indicator (respectively, second length Indicator, if the first is of value 62, as described above) shall indicate the number of octets of the RLC data field belonging to the first Upper Layer PDU, the second Length Indicator (respectively third Length Indicator, if the first is of value 62, as described above) shall indicate the number of octets of the RLC data field belonging to the second Upper Layer PDU, etc. Only the last segment of any Upper Layer PDU of a TBF (either this segment carries the entire Upper Layer PDU or not) shall be identified with a Length Indicator within the corresponding RLC data block. + +A singular case occurs when the end of the Upper Layer PDU would fit within the RLC data block but the addition of the corresponding Length Indicator octet (to indicate the Upper Layer PDU boundary) causes the Upper Layer PDU to extend into the next RLC data block. In this case, this additional LI field shall take the value 0 whatever is the length of the last but one Upper Layer PDU segment. The inclusion of a Length Indicator that indicates the presence of a Selected PLMN Index field will never correspond to an Upper Layer PDU and therefore will never result in this singular case. + +The final RLC data block of a TBF shall have a Length Indicator field corresponding to the final Upper Layer PDU unless this PDU fills the RLC data block precisely without the LI field being added (i.e. the singular case mentioned above never applies in this situation). + +The LI field is 6 bits in length and shall be encoded as a binary number with range 1 to 19, 29, 35 or 49, according to the coding scheme in use, i.e. CS-1, CS-2, CS-3 or CS-4 respectively. The value 0 shall indicate that no Upper Layer PDU boundary exists. In this case the M bit shall be set to '0' and the E bit shall be set to '1' on the transmitting side, while on the receiving side the M bit shall be ignored and the E bit shall be interpreted as having the value '1'. The value 61 or 62 may also be used as described above. In *Iu mode*, a value of 63 shall indicate the presence of filler information within the RLC data block. All other values are reserved, and in this version of the protocol, the mobile station shall ignore all fields of the RLC data block except for the USF field. + +#### 10.4.14a Length Indicator (LI) field in EGPRS TBF mode, EC TBF mode and TCH TBF mode (*Iu mode*) + +The Length indicator is used to delimit Upper Layer PDUs within the RLC data block. Additionally for *Iu mode*, a Length Indicator of value 127 may be used to indicate the presence of filler information within the RLC data block. If the first length indicator in the RLC data block is set to 127, then the entire RLC data block contains filler information. + +The first Length Indicator (respectively, second length Indicator, if the first is of value 123, as described below) shall indicate the number of octets of the RLC data field belonging to the first Upper Layer PDU, the second Length Indicator (respectively third Length Indicator, if the first is of value 123, as described below) shall indicate the number of octets of the RLC data field belonging to the second Upper Layer PDU, etc. Only the last segment of any Upper Layer PDU, including those with only one segment, shall be identified with a Length Indicator. The length indicator shall be placed in the RLC data block corresponding to the last segment of the Upper Layer PDU, unless the Upper Layer PDU without the corresponding LI field fills the RLC data block precisely. In this singular case, the Length Indicator shall be placed as the first Length Indicator in the next in sequence RLC data block and take the value 0. The inclusion of a Length Indicator that indicates the presence of a Selected PLMN Index field (see sub-clause 10.4.27) will never correspond to an Upper Layer PDU and therefore will never result in this singular case. + +If the Upper Layer PDU does not fill the current RLC data block, a Length Indicator with value 127 (111 1111) shall be included as the last Length Indicator of the current RLC data block, indicating that there is no following Upper Layer PDU in this RLC data block. If the Upper Layer PDU does not fill the RLC data block and there is only one octet left, then the Length Indicator corresponding to the Upper Layer PDU is the last Length Indicator field that shall be included in the RLC data block. + +During RLC non-persistent mode of operation, or, during RLC unacknowledged mode of operation if the network has commanded the usage of "Indication of Upper Layer PDU Start for RLC UM" for the TBF, and if the current RLC data block starts with the first segment of a new Upper Layer PDU, then a Length Indicator taking the value 126 shall be placed as the first Length Indicator in the RLC data block unless a Length Indicator with the value 0, signalling that the last segment of the previous Upper Layer PDU precisely fills the previous in sequence RLC data block, shall be included. + +If the network and the mobile station support dynamic timeslot reduction (see sub-clause 8.1.8), a Length Indicator with value 125 indicates the presence of dynamic timeslot reduction control information which shall be included after the last Upper Layer PDU. + +If EMSR is enabled, the transmission of an Upper Layer PDU can be suspended to transmit a higher priority Upper Layer PDU by including an LI with a value of 124 as the first LI field within the next transmitted RLC data block where an octet containing the TFI value associated with the higher priority Upper Layer PDU immediately follows the LI field. The transmission of the suspended Upper Layer PDU is resumed by including an LI with a value of 124 followed by an octet containing the TFI (and eTFI if assigned, see sub-clause 5.13) associated with the Upper Layer PDU whose transmission is resumed after the LI associated with the last segment of the higher priority Upper Layer PDU whose transmission is completed. The transition from the last segment of an Upper Layer PDU to the first segment of a new Upper Layer PDU associated with a different PFC can also occur within an RLC data block (i.e. no suspend occurs) in which case the transition is indicated by including an LI with a value of 124 followed by an octet containing the TFI (and eTFI if assigned) associated with the new Upper Layer PDU after the LI associated with the last segment of the Upper Layer PDU whose transmission is completed. In addition: + +- If the last segment of the Upper Layer PDU without the corresponding LI field fills the RLC data block precisely and the next in sequence RLC data block is in the same radio block, then a Length Indicator with the value 0 shall be placed as the first Length Indicator in the next in sequence RLC data block. +- If the last segment of the Upper Layer PDU without the corresponding LI field fills the RLC data block precisely and the next in sequence RLC data block is in a different radio block, then a Length Indicator with the value 0 shall be placed as the first Length Indicator in the next in sequence RLC data block and the TFI in the RLC/MAC header associated with the next in sequence RLC data block and, if eTFI is assigned, the eTFI indicated by the CRC of the next in sequence RLC data block, shall correspond to the last segment of the Upper Layer PDU. +- When a Length Indicator having the value 124 is included in the same RLC data block as the last segment of the Upper Layer PDU and fills the RLC data block precisely then the first octet of the RLC data field of the next in sequence RLC data block shall include the TFI (and eTFI if assigned) corresponding to the Upper Layer PDU whose transmission is resumed (if a suspend occurred) or to a new Upper Layer PDU (if no suspend occurred). + +A Length Indicator of value 123 is used by a mobile station supporting network sharing to indicate the presence of the *Selected PLMN Index* field (see sub-clause 10.4.27) in the octet immediately following this Length Indicator. In this case it shall always be the first Length Indicator in the RLC data block. The first Length Indicator used for the case of EMSR requires that at least one previous RLC data block has been sent for the uplink TBF whereas the first Length Indicator used to indicate the presence of the *Selected PLMN Index* field shall always occur within the very first RLC data block sent for the uplink TBF and as such they can never occur within the same RLC data block. + +When performing the radio access part of the MTA procedure using the RLC Data Block method (see 3GPP TS 44.018 [11]) a Length Indicator of value 122 is used by a mobile station to indicate the presence of the “*Cell Identity*” field (2 octets) starting in the octet immediately following LI = 122, the “*Routing Area Identification*” field (6 octets) starting in the octet immediately following the last octet used for the *Cell Identity* field, the “*MS Sync Accuracy*” field (4 bits) and the “*MS Transmission Offset*” field (4 bits) in the octet immediately following the last octet used for the “*Routing Area Identification*” field and the “*Random ID*” field (16 bits) in the two octets immediately following the octet used for the “*MS Sync Accuracy*” and the “*MS Transmission Offset*” fields (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). A single RLC data block is sent when performing the radio access part of the MTA procedure when using this method and does not include an Upper Layer PDU. As such, no additional payload beyond the 11 octets immediately following LI = 122 shall be carried by the RLC data block (i.e. an RLC data field shall not be included). + +When performing the radio access part of the MTA procedure using the RLC Data Block method (see 3GPP TS 44.018 [11]) a Length Indicator of value 119 is used by a mobile station to indicate the presence of the “*MTA Signature*” field (4 octets) starting in the octet immediately following LI = 119 (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). MS generates MTA signature using integrity protection algorithm (see 3GPP TS 43.020) with a concatenated string formed using cellid and transmission as input. A single RLC data block is sent when performing the radio access part of the MTA procedure when using this method and does not include an Upper Layer PDU. As such, no additional payload beyond the 4 octets immediately following LI = 119 shall be carried by the RLC data block (i.e. an RLC data field shall not be included). + +When performing the radio access part of the MTA procedure using the RLC Data Block method (see 3GPP TS 44.018 [11]) a Length Indicator of value 118 is used by a mobile station to indicate the presence of the “*MTA Report Instance*” field and the “*FMA*” field starting in the octet immediately following LI = 118 (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). A single RLC data block including these fields is sent when performing the radio access part of the MTA procedure with enhanced security provided according to the BSS Duplication Detection Method (see 3GPP TS 43.059 and 3GPP TS 49.031) and does not include an Upper Layer PDU. As such, no additional payload beyond the octet immediately following LI = 118 shall be carried by the RLC data block (i.e. an RLC data field shall not be included). + +When sending a Page Response due to receiving a Page with a ‘positioning event’ indication (see 3GPP TS 44.018 [11] and 3GPP TS 44.031) a Length Indicator of value 121 is used by a mobile station to indicate the presence of the “*MS Sync Accuracy*” field (4 bits) and the “*MS Transmission Offset*” field (4 bits) starting in the octet immediately following LI = 121 (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). The LLC PDU (i.e. the Page Response) is carried within the RLC data field. When receiving an RLC Data Block with LI = 121 the BSS sends the SGSN an UL-UNITDATA PDU that includes the LLC PDU, the “MultilaterationTiming Advance”, “MS Synchronization Accuracy” and the “BTS Reception Accuracy” parameters. + +A Length Indicator of value 120 is used by a mobile station supporting MS assisted Dedicated Core Network selection and indicates the presence of a DCN-ID value (see sub-clause 10.4.30) in the two octets immediately following this Length Indicator. + +The final RLC data block of a TBF shall have a Length Indicator field corresponding to the final Upper Layer PDU unless the final Upper Layer PDU fills the RLC data block precisely. If the final Upper Layer PDU fills the final RLC data block precisely, the final Upper Layer PDU shall be sent without a corresponding Length Indicator field. + +The Length Indicator field is 7 bits in length and shall be encoded as a binary number. The valid values are the values ranging from 0 to 74 for an EGPRS TBF, an EC TBF, an EGPRS2-A uplink TBF or an EGPRS2-B TBF, from 0 to 82 for an EGPRS2-A downlink TBF, from 0 to 103 in TCH TBF mode (*Iu mode*), and the values 118 to 127. All other values are reserved. A mobile station detecting a reserved Length Indicator value or an inconsistent encoding of the Length Indicator and E fields shall ignore the RLC data block. + +The interpretation of the value contained in the length indicator with corresponding E bit is summarized in table 10.4.14a.1 and some examples are shown in annex B. + +**Table 10.4.14a.1: Interpretation of values of LI field and E bit** + +| Value of LI in a RLC data block | Value of E bit in the same octet | Interpretation | +|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| k-th LI (k>0 integer):
0< value <75 (EGPRS/EC-GSM-IoT except EGPRS2-A downlink)
0< value <83 (EGPRS2-A downlink)
0< value <104 (TCH) | | The value of the k-th LI is the number of octets of the k-th Upper Layer PDU, or the last segment of it, in the current RLC data block. | +| | 0 | There is at least one Upper Layer PDU following the k-th Upper Layer PDU in the current RLC data block. | +| | 1 | There is no more than one Upper Layer PDU following the k-th Upper Layer PDU in the current RLC data block. | +| 1 st LI: value =0 | 0 | The last Upper Layer PDU of the previous in sequence RLC data block ends at the boundary of that RLC data block and it has no LI in the header of that RLC data block. Thus the current RLC data block contains the first segment of all included Upper Layer PDUs. | +| 1 st LI: value = 126 | 0 | The current RLC data block contains the first segment of all included Upper Layer PDUs.
The k-th LI contains the number of octets of the (k-1)-th Upper Layer PDU in the current RLC data block. | +| k-th LI (k>1 integer):
0< value <75 (EGPRS/EC-GSM-IoT except EGPRS2-A downlink)
0< value <83 (EGPRS2-A downlink)
0< value <104 (TCH) | | | +| | 0 | There is at least one Upper Layer PDU following the (k-1)-th Upper Layer PDU in the current RLC data block. | +| | 1 | There is no more than one Upper Layer PDU following the (k-1)-th Upper Layer PDU in the current RLC data block. | +| k-th LI: value=127 | 1 | The octets between the end of the Upper Layer PDU indicated by the (k-1)-th LI and the end of the current RLC data block are filling octets. | +| 1 st LI: value=0 | 1 | The previous RLC data block contains a Upper Layer PDU, or a part of it, that fills precisely the previous data block and for which there is no length indicator in that RLC data block. The current RLC data block contains a Upper Layer PDU that either fills the current RLC data block precisely or continues in the next RLC data block. | +| 1 st LI: value = 126 | 1 | The current RLC data block contains the first segment of an Upper Layer PDU that either fills the current RLC data block precisely or continues in the next RLC data block. | +| 1 st LI: value=127
( lu mode only ) | 1 | All octets of the RLC Data block contain filling information. | +| k-th LI: value=125
(this value is not supported in EC operation) | 0/1 | The current RLC data block contains the dynamic timeslot reduction control information. | +| k-th LI:value=124
(this value is only allowed if EMSR is enabled) | 0 | An LI value of 124 serves as a TFI transition indicator and is immediately followed by an octet containing the TFI associated with the next Upper Layer PDU segment in bit positions 1 to 5 (where bit 5 is the most significant bit) and reserved bits in bit positions 6 to 8. If eTFI is assigned then it shall be indicated by bit positions 6 to 8 (where bit 8 is the most significant bit). | +| 1 st LI:value=123
(this value is only allowed if network sharing is supported both by the network and the mobile station) | 0/1 | An LI value of 123 serves as a Selected PLMN Index field indicator and is immediately followed by an octet that contains the Selected PLMN Index field (see sub-clause 10.4.27). | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LI: value=122
(this value is only used if the MS is performing the radio access part of the MTA procedure using the RLC Data Block method) | 0/1 | An LI value of 122 indicates the RLC data block includes the “ Cell Identity ”, “ Routing Area Identification ”, “ MS Sync Accuracy ”, “ MS Transmission Offset ” and “ Random ID ” fields and is immediately followed by 11 octets that contain this information. The first 2 octets immediately following LI = 122 contain the “ Cell Identity ” field, the next 6 octets contain the “ Routing Area Identification ” field, the next octet contains the “ MS Sync Accuracy ” field and the “ MS transmission Offset ” fields and the last 2 octets include the “ Random ID ” field. | +| LI: value=121
(this value is only used if the MS is sending a Page Response due to receiving a page with a positioning event indication) | 0/1 | An LI value of 121 indicates the RLC data block includes the “ MS Sync Accuracy ” and “ MS Transmission Offset ” fields which are included starting in the octet immediately following LI = 121. | +| LI: value=120
(this value is only allowed if MS assisted Dedicated Core Network selection is supported both by the network (see 3GPP TS 44.018) and the mobile station) | 0/1 | An LI value of 120 serves as a DCN-ID field indicator and is immediately followed by two octets that contains the DCN-ID field (see sub-clause 10.4.30). | +| LI: value=119
(this value is only used if the MS is performing the radio access part of the MTA procedure and has need to provide MTA Signature using the RLC Data Block method) | 0/1 | An LI value of 119 indicates the RLC data block includes the “ MTA Signature ” field. | +| LI: value=118
(this value is only used if the MS is performing the radio access part of the MTA procedure using the RLC Data Block method where enhanced security is provided using the BSS Duplication Detection Method) | 0/1 | An LI value of 118 indicates the RLC data block includes the “ FMA ” and “ MTA Report Instance ” fields and is immediately followed by the octet that contains these fields. | +| No LI field present | n.a. | The Upper Layer PDU that starts with the current RLC data block either fills the current RLC data block precisely or continues in the following in-sequence RLC data block | + +### 10.4.15 TLLI field + +The TLLI field contains a TLLI encoded as the contents of the TLLI information element defined in 3GPP TS 44.018. + +### 10.4.16 RLC data field + +The RLC data field contains octets from one or more Upper Layer PDUs. The RLC data field may contain parts of one or two Upper Layer PDUs and all of an arbitrary number of Upper Layer PDUs. The E bit, the M bit, and the Length Indicator delimit the RLC data field into Upper Layer PDUs. If the last Upper Layer PDU of a downlink TBF or an uplink RLC data block with CV = 0 does not fill the entire RLC data field, an extension octet shall be used to indicate the number of valid RLC data octets. The remainder of the RLC data field shall be filled with filler octets with the value '00101011'. Only the last RLC data block of a downlink TBF or an uplink RLC data block with CV = 0 may contain filler octets. If an uplink TBF is continued after the RLC data block with CV = 0, the next Upper Layer PDU starts with the first octet of the RLC data field of the next in sequence RLC data block. + +### 10.4.17 Control message contents field + +The Control message contents field shall contain exactly one segment from one RLC/MAC control message field (i.e. RLC/MAC control block). + +### 10.4.18 Resent Block Bit (RSB) + +The Resent Block Bit (RSB) indicates whether any of the RLC data blocks contained within the EGPRS radio block have been sent previously. The setting of this field is shown in table 10.4.18.1. + +**Table 10.4.18.1: Resent block bit** + +| bit | | +|-------|------------------------------------------------------------------------------------------------------------| +| 0 | All of the RLC data blocks contained within the EGPRS radio block are being transmitted for the first time | +| 1 | At least one RLC data block contained within the EGPRS radio block has been transmitted before | +| NOTE: | The use of this bit shall be reconsidered in future versions of the present document. | + +### 10.4.19 PFI Indicator (PI) bit + +The PFI Indicator (PI) indicates the presence of the optional PFI field. The PI shall be ignored in *Iu mode*. + +**Table 10.4.19.1: PFI Indicator (PI) bit** + +| bit | PFI Indicator (PI) bit | +|-----|-------------------------------------------------------| +| 0 | PFI is not present | +| 1 | PFI is present if TI field indicates presence of TLLI | + +### 10.4.20 Packet Flow Identifier (PFI) field + +The PFI field contains a PFI value encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. The use of PFI is not supported in EC operation. + +### 10.4.21 PAN Indication (PANI) field + +The PANI field indicates the presence of the PAN field. + +**Table 10.4.21.1: PAN Indication (PANI) field** + +| bit | PANI | +|-----|-----------------------------| +| 0 | A PAN field is not included | +| 1 | A PAN field is included | + +### 10.4.22 Beginning of Window (BOW) field + +The BOW (begin of window) bit shall be set if $SSN = [V(Q) + 1] \bmod SNS$ . + +### 10.4.23 Short Starting Sequence Number (ShortSSN) field + +The ShortSSN field contains the $L$ least significant bits of an SSN. The size $L$ of the ShortSSN field is determined from the window size as follows: + +In RLC non-persistent mode, if the assigned window size is less than 64 the size of the ShortSSN field is 7 bits. + +### 10.4.24 Carrier ID (CI) field + +The CI field contains a carrier ID and shall be encoded as CI\_DTR IE as defined in sub-clause 11.2.28. It indicates the carrier the mobile station shall monitor when DTR is used (see sub-clause 8.1.8). The timeslot or PDCH-pair to monitor on this carrier is indicated with the TN/PDCH-pair field. + +When DTR is used in a DLMC configuration the mobile station shall ignore this field (see sub-clause 8.1.8.2). + +### 10.4.25 TN/PDCH-pair field + +This field contains the timeslot number (BTTI configuration) or the PDCH-pair number (RTTI configuration) the mobile station shall monitor on the indicated carrier (CI field) when DTR is used (see sub-clause 8.1.8). + +### 10.4.26 DTR BIks + +This field indicates the subset of downlink radio blocks the mobile station shall monitor for USFs and/or downlink RLC data blocks in DTR mode. The field is coded as in table 10.4.26.1, where the block numbers are specified in 3GPP TS 45.002. + +**Table 10.4.26.1: Radio blocks monitored in DTR mode** + +| DTR BIks
bit
6 5 | BTTI Configuration | RTTI Configuration | | +|------------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | BTTI USF mode | RTTI USF mode | +| 0 0 | All | All | All | +| 0 1 | B0, B2, B4, B6, B8, B10 | B0 a , B0 b , B2 a , B2 b , B4 a ,
B4 b , B6 a , B6 b , B8 a , B8 b ,
B10 a , B10 b | B0 a , B1 a , B2 a , B3 a , B4 a ,
B5 a , B6 a , B7 a , B8 a , B9 a ,
B10 a , B11 a | +| 1 0 | B0, B4, B8 | B0 a , B0 b , B4 a , B4 b , B8 a ,
B8 b | B0 a , B2 a , B4 a , B6 a , B8 a ,
B10 a | +| 1 1 (NOTE) | reserved | reserved | reserved | + +NOTE: When received it shall be interpreted as '00'. + +### 10.4.27 Selected PLMN Index field + +This field contains the index of the PLMN selected by a mobile station supporting network sharing. The index value refers either to the identity of the Common PLMN broadcast in the SYSTEM INFORMATION TYPE 3/4 message, or EC SYSTEM INFORMATION TYPE 2 message for EC-GSM-IoT, or to the identity of an Additional PLMN broadcast in the SYSTEM INFORMATION TYPE 22 message, or EC SYSTEM INFORMATION TYPE 4 message for EC-GSM-IoT, as described in Table 10.4.27.1. + +**Table 10.4.27.1: Selected PLMN Index field** + +| bit
3 2 1 | Selected PLMN Index | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 1 | PLMN identity of the Common PLMN broadcast in SYSTEM INFORMATION TYPE 3/4. For EC-GSM-IoT, the PLMN identity of the Common PLMN is broadcast in EC SYSTEM INFORMATION TYPE 2. | +| 0 1 0 | PLMN identity of the first Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22. For EC-GSM-IoT, the PLMN identity of the first Additional PLMN in the network sharing information is broadcast in EC SYSTEM INFORMATION TYPE 4. | +| 0 1 1 | PLMN identity of the second Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22. For EC-GSM-IoT, the PLMN identity of the second Additional PLMN in the network sharing information is broadcast in EC SYSTEM INFORMATION TYPE 4. | +| 1 0 0 | PLMN identity of the third Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22. For EC-GSM-IoT, the PLMN identity of the third Additional PLMN in the network sharing information is broadcast in EC SYSTEM INFORMATION TYPE 4. | +| 1 0 1 | PLMN identity of the fourth Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22. For EC-GSM-IoT, the PLMN identity of the fourth Additional PLMN in the network sharing information is broadcast in EC SYSTEM INFORMATION TYPE 4. | +| | All other values are reserved | + +### 10.4.28 Coverage Class field (CC) + +In EC operation, a 2-bit field is included in the downlink RLC data block header type 3 to signal the downlink Coverage Class used in the block. The Coverage Class indicates a predefined number of blind physical layer transmissions to be applied for each logical channel, where the use of blind physical layer transmissions can allow the mobile station to operate in extended coverage, see 3GPP TS 43.064. Coverage class 5 (CC5) is applicable only for UL TBFs. The field EC\_Reduced\_PDCH\_Allocation in the EC SYSTEM INFORMATION TYPE 2 message specifies if an EC TBF uses normal allocation with 4 PDCHs or reduced allocation with 2 PDCHs in the coverage class CC2, CC3 or CC4 in the cell. The corresponding mapping of EC channels onto physical channels shall be as specified in 3GPP TS 45.002. + +**Table 10.4.28.1: Coverage Class field** + +| bits
7 6 | CC | +|-------------|-----------------------| +| 0 0 | Coverage Class 1, CC1 | +| 0 1 | Coverage Class 2, CC2 | +| 1 0 | Coverage Class 3, CC3 | +| 1 1 | Coverage Class 4, CC4 | + +### 10.4.29 Downlink Coverage Class Estimate (DCCE) + +In EC operation, a 4-bit field is included in the uplink RLC data block header to signal the estimated downlink Coverage Class, see 3GPP TS 43.064, and, when CC1 is estimated, the extent to which the estimated C value (see 3GPP TS 45.008) exceeds the value indicated by the BT\_Threshold\_DL parameter sent in EC SI2 (see 3GPP TS 44.018). The C value will be reported in steps of 3 dB above the BT\_Threshold\_DL where BT\_Threshold\_DL indicates when blind physical layer transmissions are used. + +**Table 10.4.29.1: DCCE field** + +| bits
4 3 2 1 | DCCE | bits
4 3 2 1 | DCCE | +|-----------------|-----------------------------------------------------------------|-----------------|-----------------------------------------------------------------| +| 0 0 0 0 | DL CC4 | 1 0 0 0 | DL CC1; BT_Threshold_DL+15 dB ≤ C value < BT_Threshold_DL+18 dB | +| 0 0 0 1 | DL CC3 | 1 0 0 1 | DL CC1; BT_Threshold_DL+18 dB ≤ C value < BT_Threshold_DL+21 dB | +| 0 0 1 0 | DL CC2 | 1 0 1 0 | DL CC1; BT_Threshold_DL+21 dB ≤ C value < BT_Threshold_DL+24 dB | +| 0 0 1 1 | DL CC1; BT_Threshold_DL ≤ C value < BT_Threshold_DL+3 dB | 1 0 1 1 | DL CC1; BT_Threshold_DL+24 dB ≤ C value < BT_Threshold_DL+27 dB | +| 0 1 0 0 | DL CC1; BT_Threshold_DL+3 dB ≤ C value < BT_Threshold_DL+6 dB | 1 1 0 0 | DL CC1; BT_Threshold_DL+27 dB ≤ C value < BT_Threshold_DL+30 dB | +| 0 1 0 1 | DL CC1; BT_Threshold_DL+6 dB ≤ C value < BT_Threshold_DL+9 dB | 1 1 0 1 | DL CC1; BT_Threshold_DL+30 dB ≤ C value < BT_Threshold_DL+33 dB | +| 0 1 1 0 | DL CC1; BT_Threshold_DL+9 dB ≤ C value < BT_Threshold_DL+12 dB | 1 1 1 0 | DL CC1; BT_Threshold_DL+33 dB ≤ C value < BT_Threshold_DL+36 dB | +| 0 1 1 1 | DL CC1; BT_Threshold_DL+12 dB ≤ C value < BT_Threshold_DL+15 dB | 1 1 1 1 | DL CC1; BT_Threshold_DL+36 dB ≤ C value < BT_Threshold_DL+39 dB | + +NOTE: The bit numbering is relative to the field position. + +### 10.4.30 Cell Identity + +When the radio access part of the MTA procedure is performed using the RLC Data Block method, a 16 bit “Cell Identity” field is included in the uplink RLC data block (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2) and identifies the cell in which the MS received the RRLP Multilateration Timing Advance Request RRLP message (see 3GPP TS 44.031). The “Cell Identity” field is coded as per the value part of the “Cell Identity” information element defined in 3GPP TS 24.008. + +### 10.4.31 Routing Area Identification + +When the radio access part of the MTA procedure is performed using the RLC Data Block method a 48 bit “Routing Area Identification” field is included in the uplink RLC data block (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). This field identifies the Routing Area Identification corresponding to cell in which the MS received the RRLP + +Multilateration Timing Advance Request message (see 3GPP TS 44.031). It is coded as per the value part of the “Routing Area Identification” information element defined in 3GPP TS 24.008. + +### 10.4.32 MS Sync Accuracy + +When the radio access part of the MTA procedure is performed using the RLC Data Block method the octet immediately following the 6 octet “Routing Area Identification” field contains the 4 bit “MS Sync Accuracy” field and the 4 bit “MS Transmission Offset” field (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). The “MS Sync Accuracy” field is coded per the value part of the “*MS Synchronization Accuracy*” IE defined in 3GPP TS 49.031. + +### 10.4.33 MS Transmission Offset + +When the radio access part of the MTA procedure is performed using the RLC Data Block method the octet immediately following the 6 octet “*Routing Area Identification*” field contains the 4 bit “*MS Sync Accuracy*” field and the 4 bit “*MS Transmission Offset*” field (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). The “*MS Transmission Offset*” field is coded as shown in Table 10.4.33.1. + +**Table 10.4.33.1: MS Transmission Offset information element** + +| MS Transmission Offset (4 bits) | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| This field indicates the transmission offset applied by the MS when sending a RLC data block during the radio access part of the MTA procedure and is coded as follows: | | +| Bit | | +| 4321 | | +| 0000 | MS Trans. Offset = -7/32 of symbol period | +| 0001 | MS Trans. Offset = -3/16 of symbol period | +| 0010 | MS Trans. Offset = -5/32 of symbol period | +| 0011 | MS Trans. Offset = -1/8 of symbol period | +| 0100 | MS Trans. Offset = -3/32 of symbol period | +| 0101 | MS Trans. Offset = -1/16 of a symbol period | +| 0110 | MS Trans. Offset = -1/32 of a symbol period | +| 0111 | MS Trans. Offset = 0 | +| 1000 | MS Trans. Offset = 1/32 of a symbol period | +| 1001 | MS Trans. Offset = 1/16 of a symbol period | +| 1010 | MS Trans. Offset = 3/32 of a symbol period | +| 1011 | MS Trans. Offset = 1/8 of a symbol period | +| 1100 | MS Trans. Offset = 5/32 of symbol period | +| 1101 | MS Trans. Offset = 3/16 of symbol period | +| 1110 | MS Trans. Offset = 7/32 of symbol period | +| 1111 | MS Trans. Offset = 1/4 of symbol period | + +### 10.4.34 Random ID + +When the radio access part of the MTA procedure is performed using the RLC Data Block method the 2 octets immediately following the octet that with the 4 bit “MS Sync Accuracy” field and 4 bit “MS Transmission Offset” field contain the “Random ID” field (see sub-clause 10.3a.2.1 and sub-clause 10.3a.2.2). The “Random ID” value sent by a MS performing the radio access part of the MTA procedure is selected from the set of the Random ID values provided by the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031). Each Random ID value provided by the RRLP Multilateration Timing Advance Request message can only be used in one cell used during the MTA procedure. + +### 10.4.35 Downlink Coverage Class (DLCC) + +An EC TBF established with uplink coverage class CC5 shall include a 2 bit field in the uplink RLC data block header to signal the estimated downlink Coverage Class, see 3GPP TS 43.064. + +**Table 10.4.30.1: DLCC field** + +| bits
2 1 | DLCC | +|-------------|--------| +| 0 0 | DL CC4 | +| 0 1 | DL CC3 | +| 1 0 | DL CC2 | +| 1 1 | DL CC1 | + +NOTE: The bit numbering is relative to the field position. + +### 10.4.36 DCN-ID field + +This field contains the DCN-ID value (as indicated to the RLC/MAC layer by upper layers) sent from a mobile station to a BSS when both the mobile station and BSS support MS assisted Dedicated Core Network selection, see 3GPP TS 24.008 [51] and TS 3GPP TS 23.401 [54]. + +**Table 10.4.30.1: DCN-ID field** + +| | Bits | +|---------|-----------------------------------------------------| +| | 8 7 6 5 4 3 2 1 | +| Octet 1 | 8 least most significant bits
(8 7 6 5 4 3 2 1) | +| Octet 2 | 8 most significant bits
(16 15 14 13 12 11 10 9) | + +### 10.4.37 MTA Signature + +When the radio access part of the MTA procedure is performed using the RLC Data Block method, a four octet MTA signature is sent from the mobile station to the BSS if requested by the SMLC (see 3GPP TS 44.031). The mobile derives this based on cell-identifier and MS transmission offset parameters sent in all successful MTA attempts. + +### 10.4.38 Final MTA Access (FMA) + +This is field is set to '1' when the RLC data block is transmitted in conjunction with the MS performing the last instance of the radio access part of the MTA procedure using the RLC Data Block method where enhanced security is provided using the BSS Duplication Detection Method. Otherwise, it is set to '0'. + +### 10.4.39 MTA Report Instance + +This is field is set according to the instance of the radio access part of the MTA procedure performed using the RLC Data Block method where enhanced security is provided using the BSS Duplication Detection Method. It is 3 bits long and is coded as shown in Table 10.4.39.1. + +**Table 10.4.39.1: MTA Report Instance field** + +| bits
3 2 1 | MTA Report Instance | +|---------------|--------------------------| +| 0 0 0 | 1 st instance | +| 0 0 1 | 2 nd instance | +| 0 1 0 | 3 rd instance | +| 0 1 1 | 4 th instance | +| 1 0 0 | 5 th instance | + +NOTE: All remaining values are reserved. The bit numbering is relative to the field position. + +# 11 Message functional definitions and contents + +This sub-clause defines the structure of the RLC/MAC control messages. These are non-standard L3 messages as defined in 3GPP TS 24.007. The formats for the messages are valid only for the PDCH. The format for RLC/MAC control messages for use on the CCCH are defined in 3GPP TS 44.018. + +The RLC/MAC control messages defined in this sub-clause may be used also on DBPSCH and SBPSCH in *Iu mode*. A subset of these messages is used exclusively in *Iu mode*. Messages belonging to that subset are labelled as "*Iu mode only*" in this technical specification. + +A subset of the *Iu mode* only messages is used exclusively on DBPSCH. These messages do not follow the general syntactical rules for the RLC/MAC control messages used on shared channels. The error handling defined for shared channels does not apply. Messages that may be sent from the network to the mobile station, and that belong to this subset, are classified as *DBPSCH messages*, see sub-clause 11.1.1. + +Specific RLC/MAC control messages, sent on the EC-PACCH, are used for EC TBFs. + +Each definition given in the present sub-clause includes: + +- a brief description of the message direction and use; +- a CSN.1 description of the message information elements and fields (see CSN.1 Specification, Version 2.0). Definition of information elements may immediately follow the definition of the message. If the definition of an information element immediately follows the message definition, the information element name ends with 'struct'. Otherwise the information element name ends with 'IE' and the definition of the information element is defined in clause 12 or in 3GPP TS 44.018. The definition of a 'struct' is valid only within the table in which it is defined. No references shall be made to a 'struct' definition from outside of the table in which it is defined or from outside the present document. The definition of an information element is valid throughout clause 11 and clause 12 as well as in 3GPP TS 44.018; +- a note specifying, where appropriate, conditions for information elements or fields with presence requirement C or O in the relevant message which together with other conditions specified in 3GPP TS 44.060 define when the information elements shall be included or not, what non-presence of such information elements or fields means, and - for IEs with presence requirement C - the static conditions for presence and/or non-presence of the information elements or fields (see 3GPP TS 24.007); +- a table follows which contains a definition for each field referenced in the message definition or in an information element struct immediately following the message definition. + +Bit fields within RLC/MAC messages shall have the highest numbered bit of the bit field in the highest numbered bit of the lowest number octet (see sub-clause 10.0b.3.1). The mapping of an 11 bit field is illustrated in figure 11.1. + +![Diagram showing the mapping of an 11-bit field across four octets (N, N+1, N+2, N+3). Bit 8 is in Octet N, bits 11-8 are in Octet N+1, bits 7-1 are in Octet N+2, and Octet N+3 is unused.](e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg) + +| | | | | | | | | | | | | | +|-------------------------------------------|--|--|--|--|--|--|--|---------------------------|--|--|--|-----------| +| | | | | | | | | bit | | | | | +| 8 7 6 5 4 3 2 1 | | | | | | | | | | | | Octet N | +| | | | | | | | | bit 11 bit 10 bit 9 bit 8 | | | | Octet N+1 | +| bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 | | | | | | | | | | | | Octet N+2 | +| | | | | | | | | | | | | Octet N+3 | + +Diagram showing the mapping of an 11-bit field across four octets (N, N+1, N+2, N+3). Bit 8 is in Octet N, bits 11-8 are in Octet N+1, bits 7-1 are in Octet N+2, and Octet N+3 is unused. + +Figure 11.1: Field mapping within RLC/MAC messages + +The length of an RLC/MAC control messages is an integer number of RLC/MAC control blocks. Padding bits are necessary to fill the message up to the desired length. The padding bits may be the 'null' string. Otherwise, the padding bits starts with bit '0', followed by 'spare padding'. + +``` +< padding bits > ::= { null | 0 < spare padding > ! < ignore : 1 bit** = < no string > > } ; +``` + +The padding sequence used for 'spare padding' in the present document, see 3GPP TS 24.007, is a repetition of octet '00101011', starting on an octet boundary. + +## 11.1 Handling of erroneous protocol data + +This sub-clause specifies procedures for the handling of unknown and erroneous protocol data by the receiving entity. + +These error-handling procedures are mandatory for the mobile station. + +A message is defined to be syntactically incorrect if it violates rules of clauses 11 and 12, or if it contains at least one value defined as "reserved" in clauses 11 and 12. However, if the rules of clause 11 and 12 define a specific interpretation for a "reserved" value, the specified interpretation takes precedence and the considered field remains syntactically correct. + +Decoding a received message based on its CSN.1 description yields the complete acceptance or rejection of the message. Error handling allows a message to be partially accepted even when some parts are erroneous. + +Error detection mechanisms are introduced to identify which parts of a message to be protected against which kinds of errors. + +### 11.1.1 Message classification + +The packet data channel (PDCH) is a shared resource, i.e. all mobile stations assigned resources on a PDCH may receive a message sent by the network. The message type is identified by the MESSAGE\_TYPE field contained in each message. The message type is used for classification and determining the message syntax. + +Messages sent from the network to the mobile station on PDCH (*A/Gb mode* and *Iu mode*) or DBPSCH (*Iu mode*) are classified as either distribution messages or non-distribution messages. + +Messages sent from the network to the mobile station exclusively on DBPSCH (*Iu mode*) are classified as DBPSCH messages. + +#### 11.1.1.1 Distribution messages + +A distribution message is recognised by the most significant bit of the message type being set to bit '1'. The general format of a distribution message, except for distribution messages on the EC-PACCH, sent from the network to the mobile station is: + +| | +|-----------------------------------------------------------------------------------------------------------------| +| < Distribution message > ::=
< MESSAGE_TYPE : 1 bit (5) >
< Distribution contents >
< padding bits > ; | +|-----------------------------------------------------------------------------------------------------------------| + +The general format of a distribution message sent on the EC-PACCH from the network to the mobile station is: + +| | +|-----------------------------------------------------------------------------------------------------------------| +| < Distribution message > ::=
< MESSAGE_TYPE : 1 bit (4) >
< Distribution contents >
< padding bits > ; | +|-----------------------------------------------------------------------------------------------------------------| + +Any mobile stations may receive a distribution message. Depending on the protocol state of the mobile station, a distribution message shall be analysed as specified in sub-clauses 5, 6, 7, 8 and 9 of the present document. + +The 'Distribution contents' of a distribution message contains Page Mode information and any specific distribution information according to the syntax defined for the message type. The 'Distribution contents' of a distribution message on the EC-PACCH contains Used DL Coverage Class information instead of the Page Mode information. The 'padding bits' of a distribution message can be reduced to the null string. + +The general format of the 'Distribution contents', except for distribution messages sent on the EC-PACCH, is: + +| | +|-----------------------------------------------------------------------------------------------------| +| < Distribution contents > ::=
< PAGE_MODE : bit (2) >
< specific distribution information > ; | +|-----------------------------------------------------------------------------------------------------| + +The encoding of the Page Mode information is defined in sub-clause 12.20. + +The general format of the 'Distribution contents' for distribution messages sent on the EC-PACCH is: + +``` +< Distribution contents > ::= + < USED_DL_COVERAGE_CLASS : bit (2) > + < specific distribution information > ; +``` + +The encoding of the Used DL Coverage Class information is defined in sub-clause 12.71. + +#### 11.1.1.2 Non-distribution messages + +A non-distribution message is recognised by the most significant bit of the message type being set to bit '0'. The general format of a message, except for non-distribution messages on the EC-PACCH, sent from the network to the mobile station is: + +``` +< Non-distribution message > ::= + < MESSAGE_TYPE : 0 bit (5) > + < Distribution contents > + < Address information > < Non-distribution contents > + < padding bits > ; +``` + +The general format of a non-distribution message on the EC-PACCH sent from the network to the mobile station is: + +``` +< Non-distribution message > ::= + < MESSAGE_TYPE : 0 bit (4) > + < Distribution contents > + < Address information > < Non-distribution contents > + < padding bits > ; +``` + +Any mobile station may receive a non-distribution message. + +The 'Distribution contents' of a non-distribution message contains Page Mode information and any specific distribution information according to the syntax defined for the message type. The 'Distribution contents' of a non-distribution message on the EC-PACCH contains Used DL Coverage Class information instead of the Page Mode information. The general format of the 'Distribution contents' is defined in sub-clause 11.1.1.1. Depending on the protocol state of the mobile station, the 'Distribution contents' of a non-distribution message shall be analysed as specified in clauses 5 and 7 of the present document. + +The 'Address information' contained in a non-distribution message shall be analysed by a mobile station receiving the message. The 'Non-distribution contents' following the address information shall be ignored by any mobile station not identified by the address information. The allowed addressing options and the specific syntax of the 'Non-distribution contents' depend on the message type. The 'padding bits' of a non-distribution message can be reduced to the null string. + +##### 11.1.1.2.1 Format of the address information + +The general format of the 'Address information' in a non-distribution message is: + +``` +< Address information > ::= + 0 < Global TFI IE > | -- see sub-clause 12.10 + 1 0 < TLLI / G-RNTI > | -- see sub-clause 12.16 + 1 1 0 < TQI > | -- see sub-clause 12.17 + 1 1 1 < Packet Request Reference IE > ; -- see sub-clause 12.11 +``` + +The description of a certain message type may specify a restricted set of addressing options being syntactically correct in the message. A message received with a disallowed addressing option shall be regarded as syntactically incorrect. + +#### 11.1.1.3 DBPSCH message (*Iu mode* only) + +A DBPSCH message is sent exclusively on DBPSCH, from the network to the mobile station, in *Iu mode*. The general format of such a message is: + +``` +< DBPSCH message > ::= + < DBPSCH message contents > + < padding bits > ; +``` + +The 'padding bits' of a DBPSCH message can be reduced to the null string. + +The general format of the 'DBPSCH message contents' is: + +``` +< DBPSCH message contents > ::= + < MESSAGE_TYPE : bit (6) > + < specific DBPSCH message information > ; +``` + +### 11.1.2 Error detection mechanism + +The symbol '!' indicates an error branch. It acts as a separator (similar to the '|' choice symbol) where the choice on the right of the '!' are to be considered as an 'error' branch. The symbol '!' allows partial analysis of data in a received message, with some parts of the message to be ignored due to it being syntactically incorrect. + +The description on the left of '!' defines the set of syntactically correct data and shall be recognised correctly. Otherwise, the data associated shall be rejected and the description within the error branch shall be used. + +The description within the error branch, on the right of '!', shall accept any syntactically incorrect data. Therefore, according to the error label the relevant error handling procedure shall be implemented. + +### 11.1.3 Error labels + +There are different categories of error labels introduced in clauses 11 and 12 of the present document. + +#### 11.1.3.1 Generic error labels + +Generic error labels are defined for syntactical errors 'Unknown message type', 'Distribution part error', 'Address information part error' and 'Non-distribution part error'. + +The general format of a distribution message (except for a distribution message on the EC-PACCH), including these error labels, is: + +``` +< Distribution message > ::= + < MESSAGE_TYPE : 1 bit (5) > + { + < Distribution contents > + < padding bits > + ! < Distribution part error : bit (*) = < no string > > } + ! < Unknown message type : bit (6) = < no string > < Default downlink message content > > ; +``` + +The general format of a distribution message on the EC-PACCH, including these error labels, is: + +``` +< Distribution message > ::= + < MESSAGE_TYPE : 1 bit (4) > + { + < Distribution contents > + < padding bits > + ! < Distribution part error : bit (*) = < no string > > } + ! < Unknown message type : bit (5) = < no string > < Default downlink message content > > ; +``` + +The general format of a non-distribution message (except for a non-distribution message on the EC-PACCH), including these error labels, is: + +``` + +< Non-distribution message > ::= + < MESSAGE_TYPE : 0 bit (5) > + { + < Distribution contents > + { + < Address information > + { + < Non-distribution contents > + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > } + ! < Unknown message type : bit (6) = < no string > < Default downlink message content > > ; + } + } + +``` + +The general format of a non-distribution message on the EC-PACCH, including these error labels, is: + +``` + +< Non-distribution message > ::= + < MESSAGE_TYPE : 0 bit (4) > + { + < Distribution contents > + { + < Address information > + { + < Non-distribution contents > + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > } + ! < Unknown message type : bit (5) = < no string > < Default downlink message content > > ; + } + } + +``` + +The general format of a DBPSCH message, including these error labels, is: + +``` + +< DBPSCH message > ::= + { + < DBPSCH message contents > + < padding bits > + ! < DBPSCH message part error : bit (*) = < no string > > } ; + } + +``` + +These error labels allow ignoring a part of the message that is syntactically incorrect. Once an error is detected, the error branch is called. Except for the 'Unknown message type', the error branch is, followed by an unspecified bit string that expands to the end of the message. The corresponding data is ignored. In case of an 'Unknown message type', further treatment of the message is defined in sub-clause 11.1.4.1. + +#### 11.1.3.2 'Ignore' error label + +An 'Ignore' error label is used to ignore part of the message. The generic description is: + +``` + +< content > ! < Ignore : bit (*) = < no string > > -- Ignore by indefinite length + +``` + +Or + +``` + +< content of fixed length n > ! < Ignore : bit (n) = < no string > > -- Ignore by definite length + +``` + +An 'Ignore' error label shall be applied by the receiver of a downlink RLC/MAC control message when specified in the message description in clauses 11 and 12 of the present document. This error label allows ignoring a part of the message that is syntactically incorrect. Once the error is detected, the error branch 'Ignore' is called followed by an unspecified bit string. + +When this error label is used with an indefinite length (bit (\*) = < no string >), the unspecified bit string expands to the end of the message and the corresponding data is ignored. + +NOTE: If this error label is used with the indefinite length within a structure or delimited description (i.e. within { } brackets), any description following the structure or delimited description must allow truncation, in order to be consistent with the CSN.1 description of the message. + +When this error label is used with a definite length (bit (n) = < no string >), the unspecified bit string contains a defined number of bits. The corresponding data is ignored. + +#### 11.1.3.3 'Message escape' error label + +The 'Message escape' error label is used to provide an escape for, e.g. a future modification of the message syntax. The generic description is: + +| | +|----------------------------------------------------------------| +| 0 < Content > ! < Message escape : 1 bit (*) = < no string > > | +|----------------------------------------------------------------| + +An 'Message escape' error label shall be applied by the receiver of a downlink RLC/MAC control message when specified in the message description in clauses 11 and 12 of the present document. The description on the left of the error branch needs to be correctly recognised. Otherwise, the error branch 'Message escape' is called and the remaining part of the message is ignored. + +NOTE: Any description following a structure or delimited description (i.e. within { } brackets) including this error label must allow truncation. Otherwise, it is not consistent with the CSN.1 description of the message. + +### 11.1.4 Error detection and order of precedence + +A mobile station shall detect and process errors in the order in which they are defined in this sub-clause of the present document. (E.g. a message, which is not compatible with the current protocol state AND is syntactically incorrect, shall be treated as if it is not compatible with the current protocol state.) + +At certain error events defined in this sub-clause, the PACKET TBF STATUS message shall be sent by the mobile station. In case of multiple error events, and, due to restrictions defined in sub-clauses 5, 6, 7, 8 and 9, the mobile station is not able to send a first status message until the occurrence of a subsequent event generating a second status message, the mobile station shall suppress the sending of the second and additional status messages until the first status message has been sent to the network. + +#### 11.1.4.1 Unknown message type + +If a mobile station receives a message with message type either not defined or not implemented (generic error label: 'Unknown message type'), the content of the bits representing the message type shall be ignored. + +The remaining part of the message shall be analysed according to the syntax defined as the 'Default downlink message content' in sub-clause 11.2.0.1. The 'Default downlink message content' contains the Page Mode information. Depending on the protocol state of the mobile station, the Page Mode information shall be analysed as specified in clause 5 of the present document. The 'Default downlink message content' for a downlink message sent on the EC-PACCH contains the Used DL Coverage Class information instead of the Page Mode information. + +#### 11.1.4.2 Message not compatible with current protocol state + +When a non-distribution message is received, which is not expected by the addressed receiver in its current protocol state, the mobile station shall follow the procedures that are described in sub-clauses 5, 6, 7, 8 and 9 of the present document. + +If no such reaction is specified, the mobile station shall ignore the message. If in packet transfer mode, the mobile station, which is identified by the address information, shall return a status message (PACKET MOBILE TBF STATUS message) with TBF\_CAUSE #4, "Message not compatible with current protocol state", unless the mobile station has an ongoing EC TBF. + +Unexpected distribution messages are ignored. + +#### 11.1.4.3 Syntactically incorrect message + +When a message containing a syntactically incorrect data is received, depending on the error detection mechanisms that may be defined in the CSN.1 description of the message, the message can be rejected or partially accepted. + +NOTE: The order, in which the error labels mentioned in this sub-clause are detected and processed, depends on the nesting of error labels defined by the description of each message type in sub-clause 11.2 and clause 12. E.g. a message, which contains syntactically incorrect data in both the addressing information AND the non-distribution contents, is typically received with the error label 'Address information part error'. + +##### 11.1.4.3.1 Messages with error label: 'Distribution part error' + +For syntactically incorrect messages received with generic error label: 'Distribution part error', data corresponding to the description following the error label shall be recognised as erroneous data and be ignored. + +##### 11.1.4.3.2 Messages with error label: 'Address information part error' + +For syntactically incorrect messages received with generic error label: 'Address information part error', data corresponding to the description following the error label shall be recognised as erroneous data and be ignored. The distribution contents preceding the error label may be analysed and treated as described in clause 5 and clause 7 of the present document. + +##### 11.1.4.3.3 Messages with error label: 'Non-distribution part error' + +For syntactically incorrect messages received with generic error label: 'Non-distribution part error', data corresponding to the description following the error label shall be recognised as erroneous data and be ignored. + +The distribution contents preceding the error label may be analysed and treated as described in clause 5 and clause 7 of the present document. + +The address information preceding the error label shall be analysed. In packet transfer mode, the mobile station identified by the address information shall return a PACKET MOBILE TBF STATUS message with TBF\_CAUSE #2 "Syntactically incorrect message, non-distribution part error", unless the mobile station has an ongoing EC TBF. + +##### 11.1.4.3.4 Messages with error label: 'Message escape' + +For syntactically incorrect messages with error label: 'Message escape', data corresponding to the description following the error label shall be recognised as erroneously received mandatory data and be rejected. + +The distribution contents preceding the error label may be analysed and treated as described in clause 5 of the present document. + +If the address information proceeds the error label and it is received correctly, it shall be analysed. In packet transfer mode, the mobile station identified by the address information shall return a PACKET MOBILE TBF STATUS message with TBF\_CAUSE #3 "Syntactically incorrect message, message escape", unless the mobile station has an ongoing EC TBF. + +##### 11.1.4.3.5 Messages with error label: 'Ignore' + +For syntactically incorrect messages with error label: 'Ignore', data corresponding to the description following the error label shall be recognised as unnecessary data. If a syntactically incorrect message with the 'Ignore' error label is received, depending on the length of the unspecified bit string associated with the error label (sub-clause 11.1.3.2), the corresponding data shall be ignored. + +##### 11.1.4.3.6 Messages with error label: "DBPSCH message part error" + +For syntactically incorrect messages received with generic error label: 'DBPSCH message part error', data corresponding to the description following the error label shall be recognised as erroneous data and be ignored. + +#### 11.1.4.4 Syntactic error in truncated concatenation + +Truncated concatenation is sequences of components encapsulated by the { } brackets followed by the symbol '//'. The concatenation is any of the concatenations starting with null and up to any number of components. + +| | +|--------------------------| +| { < a > < b > < c > } // | +|--------------------------| + +The above set is equivalent to: + +| | +|------------------------------------------------------------------------| +| { < a > < b > < c > } or
{ < a > < b > } or
{ < a > } or
null | +|------------------------------------------------------------------------| + +Any syntactically incorrect component shall truncate the sequence. The correctly received components are accepted and the truncated components are ignored. + +NOTE: If the 'padding bits' at the end of a message are included within the concatenation, truncation requires the resulting concatenation to fit exactly with the received message length. Otherwise, it is a syntactical error, which may cause rejection of the complete message or part thereof. + +11.1.4.5 (void) + +## 11.2 RLC/MAC control messages + +Table 11.2.1 summarises the RLC/MAC control messages. Table 11.2.2 summarises the RLC/MAC control messages on the EC-PACCH. For each control message, the message type shall be a fixed number of bits from the beginning of the message. + +**Table 11.2.1: RLC/MAC control messages** + +| Uplink TBF establishment messages: | Reference | +|---------------------------------------------|------------------| +| Packet Access Reject | 11.2.1 | +| Packet Channel Request | 11.2.5 | +| EGPRS Packet Channel Request | 11.2.5a | +| Packet Queuing Notification | 11.2.15 | +| Packet Resource Request | 11.2.16 | +| Packet Uplink Assignment | 11.2.29 | +| Multiple TBF Uplink Assignment | 11.2.29a | +| Additional MS Radio Access Capabilities | 11.2.32 | +| Downlink TBF establishment messages: | Reference | +| Packet DBPSCH Assignment | 11.2.5b | +| Packet Downlink Assignment | 11.2.7 | +| Multiple TBF Downlink Assignment | 11.2.7a | +| TBF release messages: | Reference | +| Packet TBF Release | 11.2.26 | +| Paging messages: | Reference | +| Packet Paging Request | 11.2.10 | +| RLC messages: | Reference | +| Packet Downlink Ack/Nack | 11.2.6 | +| EGPRS Packet Downlink Ack/Nack | 11.2.6a | +| Packet DBPSCH Downlink Ack/Nack | 11.2.6b | +| Packet DBPSCH Downlink Ack/Nack Type 2 | 11.2.6c | +| MBMS Downlink Ack/Nack | 11.2.6d | +| EGPRS Packet Downlink Ack/Nack Type 2 | 11.2.6e | +| EGPRS Packet Downlink Ack/Nack Type 3 | 11.2.6f | +| Packet Uplink Ack/Nack | 11.2.28 | +| Packet DBPSCH Uplink Ack/Nack | 11.2.28a | +| Packet DBPSCH Uplink Ack/Nack Type 2 | 11.2.28b | +| EGPRS Packet Downlink Ack/Nack DLMC | 11.2.48 | +| System information messages: | Reference | +| Packet System Information Type 1 | 11.2.18 | +| Packet System Information Type 2 | 11.2.19 | +| Packet System Information Type 3 | 11.2.20 | +| Packet System Information Type 3 bis | 11.2.21 | +| Packet System Information Type 3 ter | 11.2.21a | +| Packet System Information Type 3 quater | 11.2.21b | +| Packet System Information Type 5 | 11.2.23 | +| Packet System Information Type 6 | 11.2.23a | +| Packet System Information Type 7 | 11.2.23b | +| Packet System Information Type 8 | 11.2.24 | +| Packet System Information Type 13 | 11.2.25 | +| Packet System Information Type 14 | 11.2.25a | +| Packet System Information Type 15 | 11.2.25b | +| Packet System Information Type 16 | 11.2.25c | +| Miscellaneous messages: | Reference | +| Packet Control Acknowledgement | 11.2.2 | +| Packet Cell Change Continue | 11.2.2a | +| Packet Cell Change Failure | 11.2.3 | +| Packet Cell Change Notification | 11.2.3a | +| Packet Cell Change Order | 11.2.4 | +| Packet Downlink Dummy Control Block | 11.2.8 | +| Packet Uplink Dummy Control Block | 11.2.8b | +| Packet Measurement Report | 11.2.9 | +| Packet Measurement Order | 11.2.9b | +| Packet Mobile TBF Status | 11.2.9c | +| Packet Enhanced Measurement Report | 11.2.9d | +| Packet Neighbour Cell Data | 11.2.9e | +| Packet PDCH Release | 11.2.11 | +| Packet Polling Request | 11.2.12 | +| Packet Power Control/Timing Advance | 11.2.13 | +| Packet PRACH Parameters | 11.2.14 | +| Packet PSI Status | 11.2.17 | +| Packet Serving Cell Data | 11.2.17a | +| Packet SI Status | 11.2.17b | +| Packet Pause | 11.2.30a | +| Packet Timeslot Reconfigure | 11.2.31 | +| Multiple TBF Timeslot Reconfigure | 11.2.31a | + +| | | +|------------------------------------|----------| +| Handover Access | 11.2.33 | +| Physical Information | 11.2.34 | +| Packet CS Request | 11.2.35 | +| Packet CS Command | 11.2.36 | +| Packet CS Release Indication | 11.2.37 | +| MBMS Service Request | 11.2.38 | +| MBMS Assignment (Non-distribution) | 11.2.39 | +| MBMS Assignment (Distribution) | 11.2.39a | +| MBMS Neighbouring Cell Information | 11.2.40 | +| MBMS MS_ID Assignment | 11.2.41 | +| Packet MBMS Announcement | 11.2.42 | +| PS Handover Command | 11.2.43 | +| PS Handover Access | 11.2.44 | +| Packet Physical Information | 11.2.45 | +| DTM Handover Command | 11.2.46 | +| Packet Application Information | 11.2.47 | + +**Table 11.2.2: RLC/MAC control messages on EC-PACCH** + +| | | +|-----------------------------------------------------|------------------| +| Uplink EC TBF establishment messages: | Reference | +| EC Packet Access Reject | 11.2.49 | +| EC Packet Uplink Assignment | 11.2.58 | +| Downlink EC TBF establishment messages: | Reference | +| EC Packet Downlink Assignment | 11.2.52 | +| EC TBF release messages: | Reference | +| EC Packet TBF Release | 11.2.56 | +| EC-GSM-IoT RLC messages: | Reference | +| EC Packet Downlink Ack/Nack | 11.2.51 | +| EC Packet Downlink Ack/Nack Higher CC | 11.2.60 | +| EC Packet Uplink Ack/Nack | 11.2.57 | +| EC Packet Uplink Ack/Nack and Contention Resolution | 11.2.59 | +| EC-GSM-IoT miscellaneous messages: | Reference | +| EC Packet Control Acknowledgement | 11.2.50 | +| EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC | 11.2.61 | +| EC Packet Polling Request | 11.2.54 | +| EC Packet Power Control/Timing Advance | 11.2.55 | +| EC Packet Downlink Dummy Control Block | 11.2.53 | + +### 11.2.0 Message format + +All RLC/MAC control messages, with the exception of the PACKET CONTROL ACKNOWLEDGEMENT message in access burst format (11-bit and 8-bit contents), the HANDOVER ACCESS message in access burst format (8-bit content), the PS HANDOVER ACCESS message, the PACKET CHANNEL REQUEST message, EGPRS PACKET CHANNEL REQUEST message, MPRACH PACKET CHANNEL REQUEST message and the RLC/MAC control messages sent on the EC-PACCH follow the same non-standard format (see 3GPP TS 24.007). + +The RLC/MAC control messages sent on the EC-PACCH follow the same non-standard format (see 3GPP TS 24.007). + +#### 11.2.0.1 Downlink RLC/MAC messages + +Downlink RLC/MAC control messages are received in RLC/MAC control block format. The different types of messages are distinguished by the MESSAGE\_TYPE field. + +``` +< Downlink RLC/MAC control message > ::= + < MESSAGE_TYPE : bit (6) == 1 00001 > < Packet Access Reject message content > | + < MESSAGE_TYPE : bit (6) == 0 00001 > < Packet Cell Change Order message content > | + < MESSAGE_TYPE : bit (6) == 0 00010 > < Packet Downlink Assignment message content > | + < MESSAGE_TYPE : bit (6) == 0 00011 > < Packet Measurement Order message content > | + < MESSAGE_TYPE : bit (6) == 1 00010 > < Packet Paging Request message content > | + < MESSAGE_TYPE : bit (6) == 1 00011 > < Packet PDCH Release message content > | + < MESSAGE_TYPE : bit (6) == 0 00100 > < Packet Polling Request message content > | + < MESSAGE_TYPE : bit (6) == 0 00101 > < Packet Power Control/Timing Advance message content > | + < MESSAGE_TYPE : bit (6) == 1 00100 > < Packet PRACH Parameters message content > | + < MESSAGE_TYPE : bit (6) == 0 00110 > < Packet Queueing Notification message content > | + < MESSAGE_TYPE : bit (6) == 0 00111 > < Packet Timeslot Reconfigure message content > | + < MESSAGE_TYPE : bit (6) == 0 01000 > < Packet TBF Release message content > | + < MESSAGE_TYPE : bit (6) == 0 01001 > < Packet Uplink Ack/Nack message content > | -- PACCH only + < MESSAGE_TYPE : bit (6) == 0 01010 > < Packet Uplink Assignment message content > | + < MESSAGE_TYPE : bit (6) == 0 01011 > < Packet Cell Change Continue message content > | + < MESSAGE_TYPE : bit (6) == 0 01100 > < Packet Neighbour Cell Data message content > | + < MESSAGE_TYPE : bit (6) == 0 01101 > < Packet Serving Cell Data message content > | + < MESSAGE_TYPE : bit (6) == 0 01110 > < Packet DBPSCH Assignment message content > | + < MESSAGE_TYPE : bit (6) == 0 01111 > < Multiple TBF Downlink Assignment message content > | + < MESSAGE_TYPE : bit (6) == 0 10000 > < Multiple TBF Uplink Assignment message content > | + < MESSAGE_TYPE : bit (6) == 0 10001 > < Multiple TBF Timeslot Reconfigure message content > | + < MESSAGE_TYPE : bit (6) == 0 10011 > < MBMS MS_ID Assignment message content > | -- PACCH only + < MESSAGE_TYPE : bit (6) == 0 10100 > < MBMS Assignment (Non-distribution) message content > | + < MESSAGE_TYPE : bit (6) == 0 10101 > < PS Handover Command message content > | -- PACCH only + < MESSAGE_TYPE : bit (6) == 0 10110 > < Packet Physical Information message content > | -- PACCH only + < MESSAGE_TYPE : bit (6) == 0 10111 > < DTM Handover Command message content > | -- PACCH only + < MESSAGE_TYPE : bit (6) == 1 00101 > < Packet Downlink Dummy Control Block message content > | + < MESSAGE_TYPE : bit (6) == 1 10001 > < PS11 message content > | + < MESSAGE_TYPE : bit (6) == 1 10010 > < PS12 message content > | + < MESSAGE_TYPE : bit (6) == 1 10011 > < PS13 message content > | + < MESSAGE_TYPE : bit (6) == 1 10100 > < PS13 bis message content > | + < MESSAGE_TYPE : bit (6) == 1 10101 > reserved | -- this value was allocated in an earlier + -- version of the protocol and shall not be used + < MESSAGE_TYPE : bit (6) == 1 10110 > < PS15 message content > | + < MESSAGE_TYPE : bit (6) == 1 10000 > < PS16 message content > | + < MESSAGE_TYPE : bit (6) == 1 11000 > < PS17 message content > | + < MESSAGE_TYPE : bit (6) == 1 11001 > < PS18 message content > | + < MESSAGE_TYPE : bit (6) == 1 10111 > < PS113 message content > | + < MESSAGE_TYPE : bit (6) == 1 11010 > < PS114 message content > | + < MESSAGE_TYPE : bit (6) == 1 11100 > < PS13 ter message content > | + < MESSAGE_TYPE : bit (6) == 1 11101 > < PS13 quater message content > | + < MESSAGE_TYPE : bit (6) == 1 11110 > < PS115 message content > | + < MESSAGE_TYPE : bit (6) == 1 01000 > < PS116 message content > | + < MESSAGE_TYPE : bit (6) == 1 00000 > < Packet Serving Cell SI message content > | + < MESSAGE_TYPE : bit (6) == 1 00111 > < Packet CS Command message content > | + < MESSAGE_TYPE : bit (6) == 1 01001 > < Packet CS Release Indication message content > | + < MESSAGE_TYPE : bit (6) == 1 01010 > < MBMS Assignment (Distribution) message content > | + < MESSAGE_TYPE : bit (6) == 1 01011 > < MBMS Neighbouring Cell Information message content > | + < MESSAGE_TYPE : bit (6) == 1 01100 > < Packet MBMS Announcement message content > | + < MESSAGE_TYPE : bit (6) == 1 01101 > < Packet Application Information message content > | + ! < Unknown message type : { bit (6) = < no string > } < Default downlink message content > ; +``` + +NOTE: the MESSAGE\_TYPE "010010" is reserved for the PHYSICAL INFORMATION message on DBPSCH only. + +The 'Default downlink message contents', for messages that are not sent on the EC-PACCH, consists of the Page Mode information and an unspecified bit string that expands to the end of the message. + +``` +< Default downlink message content > ::= + < PAGE_MODE : bit (2) > + bit (*) = < no string > ; +``` + +The encoding of the Page Mode information is defined in sub-clause 12.20. + +Downlink RLC/MAC control messages sent on EC-PACCH are received in RLC/MAC control block format. The different types of messages on the EC-PACCH are distinguished by the MESSAGE\_TYPE field. + +``` +< Downlink RLC/MAC control message on EC-PACCH > ::= + < MESSAGE_TYPE : bit (5) == 1 0001 > < EC Packet Access Reject message content > | + < MESSAGE_TYPE : bit (5) == 0 0001 > < EC Packet Downlink Assignment message content > | + < MESSAGE_TYPE : bit (5) == 0 0010 > < EC Packet Polling Request message content > | + < MESSAGE_TYPE : bit (5) == 0 0011 > < EC Packet Power Control/Timing Advance message content > | + < MESSAGE_TYPE : bit (5) == 0 0100 > < EC Packet TBF Release message content > | + < MESSAGE_TYPE : bit (5) == 0 0101 > < EC Packet Uplink Ack/Nack message content > | + < MESSAGE_TYPE : bit (5) == 0 0110 > < EC Packet Uplink Assignment message content > | + < MESSAGE_TYPE : bit (5) == 0 0111 > < EC Packet Uplink Ack/Nack and Contention Resolution message +content > | + < MESSAGE_TYPE : bit (5) == 1 0010 > < EC Packet Downlink Dummy Control Block message content > + ! < Unknown message type : { bit (5) = < no string > } < Default downlink message content > ; +``` + +The 'Default downlink message contents' for messages that are sent on the EC-PACCH consists of the Used DL Coverage Class information and an unspecified bit string that expands to the end of the message. + +``` +< Default downlink message content > ::= + < USED_DL_COVERAGE_CLASS : bit (2) > + bit (*) = < no string > ; +``` + +The encoding of the Used DL Coverage Class information element is defined in sub-clause 12.71. + +#### 11.2.0.2 Uplink RLC/MAC messages + +Uplink RLC/MAC control messages, except those using the access burst formats, are received in the RLC/MAC control block format. The different types of messages are distinguished by the MESSAGE\_TYPE field. + +``` +< Uplink RLC/MAC control message > ::= + < MESSAGE_TYPE : bit (6) == 000000 > < Packet Cell Change Failure message content > | + < MESSAGE_TYPE : bit (6) == 000001 > < Packet Control Acknowledgement message content > | + < MESSAGE_TYPE : bit (6) == 000010 > < Packet Downlink Ack/Nack message content > | -- PACCH only + < MESSAGE_TYPE : bit (6) == 000011 > < Packet Uplink Dummy Control Block message content > | + < MESSAGE_TYPE : bit (6) == 000100 > < Packet Measurement Report message content > | + < MESSAGE_TYPE : bit (6) == 001010 > < Packet Enhanced Measurement Report message content > | + < MESSAGE_TYPE : bit (6) == 000101 > < Packet Resource Request message content > | + < MESSAGE_TYPE : bit (6) == 000110 > < Packet Mobile TBF Status message content > | + < MESSAGE_TYPE : bit (6) == 000111 > < Packet PSI Status message content > | + < MESSAGE_TYPE : bit (6) == 001000 > < EGPRS Packet Downlink Ack/Nack message content > | + < MESSAGE_TYPE : bit (6) == 010001 > < EGPRS Packet Downlink Ack/Nack Type 2 message content > | + < MESSAGE_TYPE : bit (6) == 010010 > < EGPRS Packet Downlink Ack/Nack Type 3 message content > | + < MESSAGE_TYPE : bit (6) == 001001 > < Packet Pause message content > | + < MESSAGE_TYPE : bit (6) == 001011 > < Additional MS Radio Access Capabilities message content > | + < MESSAGE_TYPE : bit (6) == 001100 > < Packet Cell Change Notification message content > | + < MESSAGE_TYPE : bit (6) == 001101 > < Packet SI Status message content > | + < MESSAGE_TYPE : bit (6) == 001110 > < Packet CS Request message content > | + < MESSAGE_TYPE : bit (6) == 001111 > < MBMS Service Request message content > | + < MESSAGE_TYPE : bit (6) == 010000 > < MBMS Downlink Ack/Nack message content > | + < MESSAGE_TYPE : bit (6) == 010011 > < EGPRS Packet Downlink Ack/Nack DLMC message content > ; +``` + +Messages using the access burst formats (11-bit and 8-bit formats) are defined in sub-clauses 11.2.2 11.2.5, 11.2.5a, 11.2.5c, 11.2.33 and 11.2.44. + +Uplink RLC/MAC control messages sent on EC-PACCH, except those using the access burst formats, are received in the RLC/MAC control block format. + +The different types of messages on the EC-PACCH when one of the coverage classes CC1 to CC4 for uplink is selected are distinguished by the MESSAGE\_TYPE field as follows. + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Uplink RLC/MAC control message on EC-PACCH > ::=   < MESSAGE_TYPE : bit (5) == 00001 > < EC Packet Control Acknowledgement message content >     < MESSAGE_TYPE : bit (5) == 00010 > < EC Packet Downlink Ack/Nack message content > ;
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +The different types of messages on the EC-PACCH, when coverage class CC5 for uplink is selected are distinguished by the MESSAGE\_TYPE field as follows: + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Uplink RLC/MAC control message on EC-PACCH CC5 > ::=   < MESSAGE_TYPE : bit (3) == 001 > < EC Packet Control Acknowledgement message Higher CC content >     < MESSAGE_TYPE : bit (3) == 010 > < EC Packet Downlink Ack/Nack Higher CC message content > ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +The EC Packet Control Acknowledgement message or EC Packet Control Acknowledgement Higher CC message can be sent both using the normal burst format and the access burst format (11-bit format). The access burst format is defined in sub-clause 11.2.50. + +### 11.2.1 Packet Access Reject + +This message is sent on the PCCCH or PACCH by the network to the mobile station to indicate that the network has rejected the MSs access request. This message may contain fields addressing more than one mobile station. + +Message type: PACKET ACCESS REJECT + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.1.1: PACKET ACCESS REJECT information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Packet Access Reject message content > ::=   < PAGE_MODE : bit (2) >   < Reject : < Reject struct > >   { { 1 < Additional Reject : < Reject struct > > } ** 0     { null   0 bit ** = < no string > -- Receiver compatible with earlier releases         1 -- Additions in release 5       { 1 < Iu mode Reject : < Iu mode Reject struct > > } ** 0       { null   0 bit ** = < no string > -- Receiver compatible with earlier releases           1 -- Additions in release 6         { 1 < A/Gb mode Reject : < A/Gb mode Reject struct > > } ** 0 }      < padding bits > } } // -- truncation at end of message allowed, bits '0' assumed   ! < Distribution part error : bit (*) = < no string > > ;  < Reject struct > ::=   { 0 < TLLI / G-RNTI : bit (32) >     1 { 0 < Packet Request Reference : < Packet Request Reference IE > >         1 < Global TFI : < Global TFI IE > > } }   { 0   1 < WAIT_INDICATION : bit (8) >           < WAIT_INDICATION_SIZE : bit (1) > }   ! < Ignore : bit (*) = < no string > > ;  < Iu mode Reject struct > ::=   < G-RNTI_extension : bit (4) >   { 0 -- all TBF requests for the MS identified by the G-RNTI in the corresponding Reject structure rejected     { 1 < RB Id : bit (5) > } ** 0 } ; -- TBF requests for these RB Ids are rejected  < A/Gb mode Reject struct > ::=   { 0 -- all TBF requests for the MS identified by the TLLI in the corresponding Reject struct are rejected     { 1 < PFI : bit (7) > } ** 0 } ; -- TBF requests for these PFIs are rejected
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.1.2: PACKET ACCESS REJECT information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20. | +| Reject struct
The mobile station shall only accept the first Reject struct addressed to it and ignore all other Reject structs. | +| Iu mode Reject struct
For each occurrence of a G-RNTI in the TLLI / G-RNTI field of a Reject struct, a corresponding Iu mode Reject struct shall be included in the message. The list of Iu mode Reject structs shall address the Iu mode mobile stations in the same order as the list of G-RNTI values in the Reject structs. | +| A/Gb mode Reject struct
For each occurrence of a TLLI in the TLLI / G-RNTI field of a Reject struct, a corresponding A/Gb mode Reject struct shall be included in the message. The list of A/Gb mode Reject structs shall address the A/Gb mode mobile stations in the same order as the list of TLLI values in the Reject structs. | +| Packet Request Reference
This information element shall be included if the PACKET ACCESS REJECT message is sent in response to a PACKET CHANNEL REQUEST message. This information element is defined in sub-clause 12.11. | +| TLLI / G-RNTI (32 bit field)
This information field shall be included if the PACKET ACCESS REJECT message is sent in response to a PACKET RESOURCE REQUEST message or a Channel Request Description IE contained in a PACKET DOWNLINK ACK/NACK message. This information field is defined in sub-clause 12.16. | +| G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier for contention resolution in Iu-mode.

For each occurrence of the TLLI / G-RNTI field in the Reject struct, the corresponding G-RNTI extension field shall be included in the Iu mode reject struct in the same order as the list of G-RNTI values in the TLLI / G-RNTI field. | +| Global TFI
This information element contains the TFI of one of the mobile station's downlink TBFs or uplink TBFs. This field is defined in sub-clause 12.10. | +| WAIT_INDICATION (8 bit field)
The Wait Indication field indicates the time the mobile station shall wait before attempting another channel request. This field is coded as the binary representation of the T3172 timeout value in units of 20 ms or in units of seconds. The units are indicated in the WAIT_INDICATION_SIZE field.
Range 0 to 255. | +| WAIT_INDICATION_SIZE (1 bit field)
This field indicates the units of the WAIT_INDICATION field.

0 the WAIT_INDICATION field is coded in units of s
1 the WAIT_INDICATION field is coded in units of 20 ms | +| RB Id (5 bit field)
This field contains the identifier of the radio bearer for which a TBF was requested. | +| PFI (7 bit field)
This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element defined in 3GPP TS 44.018. | + +### 11.2.2 Packet Control Acknowledgement + +This message is sent on the PACCH from the mobile station to the network. In *Iu mode*, it is also sent on FACCH, SACCH and SDCCH from the mobile station to the network. The message is formatted either as an RLC/MAC control + +block using the PACCH block format defined in 3GPP TS 44.004 or as 4 identical access bursts using the PACCH short acknowledgement block format defined in 3GPP TS 44.004. If the CTRL\_ACK\_EXTENSION field is to be included (i.e. the MS is sending acknowledgement information for a RLC/MAC control message which it knows to have been segmented using extended RLC/MAC control message segmentation - see Table 11.2.2.2) the message shall be formatted as an RLC/MAC control block. Otherwise, if sent as response to a Packet Polling Request message this latter message shall specify the format of the Packet Control Acknowledgement message. Otherwise the System Information parameter CONTROL\_ACK\_TYPE indicates which format the mobile station shall use. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. + +The RLC/MAC control block format is shown in table 11.2.2.1 and table 11.2.2.2. + +The access burst format is either 11-bit or 8-bit and is coded as shown in table 11.2.2.1. The mobile station shall use the format indicated by the System Information parameter ACCESS\_BURST\_TYPE. The mobile station shall transmit the access burst four times, one time in each TDMA frame of the uplink radio block. + +Message type: PACKET CONTROL ACKNOWLEDGEMENT + +Direction: mobile station to network + +**Table 11.2.2.1: PACKET CONTROL ACKNOWLEDGEMENT** + +``` +< Packet Control Acknowledgement message content > ::= -- RLC/MAC control block format + < TLLI/G-RNTI : bit (32) > + < CTRL_ACK : bit (2) > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version of the protocol + | 1 -- Release 5 additions + { 0 | 1 < TN_RRBP : bit (3) > } + { 0 | 1 < G-RNTI extension : bit (4) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version of the protocol + | 1 -- Release 6 additions + { 0 | 1 < CTRL_ACK_EXTENSION : bit (9) > } + < padding bits > } ; + +< Packet Control Acknowledgement 11 bit message > ::= -- 11-bit access burst format + < MESSAGE_TYPE : bit (9) == 1111 1100 1 > + | { < MESSAGE_TYPE : bit (6) == 110111 > + < TN_RRBP : bit (3) > } + < CTRL_ACK : bit (2) > ; + +< Packet Control Acknowledgement 8 bit message > ::= -- 8-bit access burst format + < MESSAGE_TYPE : bit (6) == 0111 11 > + | { < MESSAGE_TYPE : bit (3) == 000 > + < TN_RRBP : bit (3) > } + < CTRL_ACK : bit (2) > ; +``` + +**Table 11.2.2.2: PACKET CONTROL ACKNOWLEDGEMENT** + +#### **TLLI/G-RNTI (32 bit field)** + +This field contains the TLLI/G-RNTI of the mobile station. This field is encoded as defined in sub-clause 12.16. + +#### **CTRL\_ACK (2 bit field)** + +This field contains acknowledgement information for the group of RLC/MAC control blocks that make up an RLC/MAC control message. The mobile station shall set the CTRL\_ACK field to indicate which segments of an RLC/MAC control message have been received by the time of transmission of the PACKET CONTROL ACKNOWLEDGEMENT message. + +This field can also be coded to contain the information if the mobile station is requesting the establishment of new TBF. This coding is allowed only when the message is sent in access burst format as a response to the PACKET UPLINK ACK/NACK message with Final Ack Indicator set to '1' and TBF Est is set to '1'. + +If the PACKET CONTROL ACKNOWLEDGEMENT message is being transmitted in response to a valid RRBP field received as part of an RLC/MAC block with Payload Type equal to '10', the CTRL\_ACK field shall be set according to the following table: + +| | | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bit | | +| 2 1 | | +| 0 0 | in case the message is sent in access burst format, the same meaning as for the value '11' except that the mobile station is requesting new TBF. Otherwise the bit value '00' is reserved and shall not be sent. If received it shall be interpreted as bit value '01'. | +| 0 1 | the MS received an RLC/MAC control block addressed to itself and with RBSN = 1, and did not receive an RLC/MAC control block with the same RTI value and RBSN = 0. | +| 1 0 | the MS received an RLC/MAC control block addressed to itself and with RBSN = 0, and did not receive an RLC/MAC control block with the same RTI value and RBSN = 1. This value is sent irrespective of the value of the FS bit. | +| 1 1 | the MS received two RLC/MAC blocks with the same RTI value, one with RBSN = 0 and the other with RBSN = 1. | + +If the PACKET CONTROL ACKNOWLEDGEMENT message is being transmitted in response to a valid RRBP field received as part of an RLC/MAC block with Payload Type not equal to '10', the CTRL\_ACK field shall be set to the value '11' in case the message is sent in normal burst format or in case the mobile station is not requesting new TBF. In case the message is sent in access burst format and the mobile station is requesting new TBF, the CTRL\_ACK field shall be set to the value '00'. + +If the PACKET CONTROL ACKNOWLEDGEMENT message is being transmitted in response to a polling request in an IMMEDIATE ASSIGNMENT message received on CCCH, the CTRL\_ACK field shall be set to the value '11'. + +If the mobile station receives an RLC/MAC block with Payload Type equal to '10' and RLC/MAC block with Payload Type not equal to '10' with different RRBP values such that they specify the same uplink block, the mobile station shall set the CTRL\_ACK field according to the group of RLC/MAC control blocks that the RLC/MAC block with Payload Type equal to '10' belongs. + +#### **CTRL\_ACK\_EXTENSION (9 bit field)** + +This field contains acknowledgement information for the group of up to nine RLC/MAC control blocks that make up an RLC/MAC control message sent using extended RLC/MAC control message segmentation. The mobile station shall set the CTRL\_ACK\_EXTENSION field to indicate which segments of an RLC/MAC control message addressed to itself have been received by the time of transmission of the PACKET CONTROL ACKNOWLEDGEMENT message. Bit at index n in the CTRL\_ACK\_EXTENSION field indicates whether RLC/MAC control block "10 - n" has been received. This bit shall be set to '1' if the corresponding RLC/MAC control block has been received and to '0' otherwise. When CTRL\_ACK\_EXTENSION field is present, the CTRL\_ACK field shall be ignored. The CTRL\_ACK\_EXTENSION field shall be included only if the MS knows an RLC/MAC control message has been segmented using extended RLC/MAC control message segmentation (i.e. the MS has received at least one segment other than the first segment of an RLC/MAC control message segmented using extended RLC/MAC control message segmentation). The CTRL\_ACK\_EXTENSION field shall not be included if the MS has only received the first segment of an RLC/MAC control message and hence does not know whether extended RLC/MAC control message segmentation is used. + +bit + +9 8 7 6 5 4 3 2 1 + +0 0 0 0 0 0 0 0 0 this value is reserved and shall not be sent. + +1 0 0 0 0 0 0 0 0 this value is reserved and shall not be sent. + +... + +0 0 1 0 1 0 0 0 0 the MS received the 3rd and 5th segments (i.e. with RBSN = '1' and RBSNe = '001' and RBSN = '1' and RBSNe = '011' respectively) of an RLC/MAC control message sent using a given RTI value and did not receive any other RLC/MAC control block(s) with other RBSN and RBSNe values having that same RTI value. + +... + +1 1 1 1 1 1 1 1 1 the MS received all nine segments of an RLC/MAC control message. + +If the mobile station receives an RLC/MAC block with Payload Type equal to '10' and an RLC/MAC block with Payload Type not equal to '10' with different RRBP values such that they specify the same uplink block, the mobile station shall set the CTRL\_ACK\_EXTENSION field according to the group of RLC/MAC control blocks that the RLC/MAC block with Payload Type equal to '10' belongs. + +#### **TN\_RRBP (3 bit field)** + +This field contains the timeslot number of the downlink PDCH on which the RRBP was received. The TN\_RRBP field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +#### **G-RNTI extension (4 bit field)** + +This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in *Iu mode*. + +### 11.2.2a Packet Cell Change Continue + +This message is sent on the PACCH by the network to the mobile station to command the mobile station to continue the cell reselection procedure. + +Message type: PACKET CELL CHANGE CONTINUE + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.2a.1: PACKET CELL CHANGE CONTINUE message content** + +``` +< Packet Cell Change Continue message content > ::= + < PAGE_MODE : bit (2) > + { 0 < GLOBAL_TFI : Global TFI IE > + { { 0 | 1 < ARFCN : bit (10) > + < BSIC : bit (6) > + < CONTAINER_ID : bit (2) > } + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.2a.2: PACKET CELL CHANGE CONTINUE information element details** + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **Global TFI** + +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +The **ARFCN**, **BSIC** and the **CONTAINER\_ID** parameters shall be included if the network has earlier sent neighbour cell system information for the cell within a set of PACKET NEIGHBOUR CELL DATA messages referred by the corresponding CONTAINER\_ID value but without ARFCN and BSIC provided. Otherwise these parameters are optional. + +#### **ARFCN** (10 bit field) + +This field contains the BCCH frequency of the new cell candidate for re-selection. This field is encoded as the ARFCN defined in 3GPP TS 44.018. + +Range 0 to 1023 + +#### **BSIC** (6 bit field) + +This field contains the BSIC of the new cell candidate for re-selection. This field is encoded as the BSIC value defined in 3GPP TS 44.018. + +Range 0 to 63 + +#### **CONTAINER\_ID** (2 bit field) + +This field contains the identity of the neighbour cell system information container previously sent in the PACKET NEIGHBOUR CELL DATA message for the cell addressed by the ARFCN and the BSIC above. + +Range 0 to 3 + +### 11.2.3 Packet Cell Change Failure + +This message is sent on the PACCH from the mobile station to the network to indicate that a commanded cell change order has failed. For a (3G) multi-RAT mobile station this may be a 3G Cell. For a (E-UTRAN) multi-RAT mobile station this may be an E-UTRAN cell. + +Message type: PACKET CELL CHANGE FAILURE + +Direction: mobile station to network + +**Table 11.2.3.1: PACKET CELL CHANGE FAILURE message content** + +``` + +< Packet Cell Change Failure message content > ::= + < TLLI / G-RNTI : bit (32) > + < ARFCN : bit (10) > + < BSIC : bit (6) > + < CAUSE : bit (4) > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release 99 : + { 0 | 1 < UTRAN FDD Target cell: < UTRAN FDD Target cell IE > > } + { 0 | 1 < UTRAN TDD Target cell: < UTRAN TDD Target cell IE > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-8 : + { 0 | 1 < E-UTRAN Target cell: < E-UTRAN Target cell IE > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-9 : + { 0 | 1 < UTRAN CSG Target cell: + < UTRAN CSG Target cell IE > > } + { 0 | 1 < E-UTRAN CSG Target cell : + < E-UTRAN CSG Target cell IE > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-11 : + { 0 | 1 < E-UTRAN Target cell with extended EARFCN : + < E-UTRAN Target cell with extended EARFCN IE > > } + < padding bits > } } } } ; + +``` + +**Table 11.2.3.2: PACKET CELL CHANGE FAILURE information element details** + +| | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|---------------------------|---------|----------------------------|---------|----------------------------------------------------------------|---------|------------------------|---------|---------------------------|---------|-------------------------|---------|-----------------------------|------------|-------------------------| +|

TLLI / G-RNTI (32 bit field)
This field is defined in sub-clause 12.16.

| | | | | | | | | | | | | | | | | +|

ARFCN (10 bit field)
This field contains, in case of a GSM cell, the BCH frequency of the target cell on which the failure occurred. This field is encoded as the ARFCN defined in 3GPP TS 44.018.
Range 0 to 1023
If a 3G Cell or an E-UTRAN Cell is indicated, this field shall be sent with the value 0

| | | | | | | | | | | | | | | | | +|

BSIC (6 bit field)
This field contains, in case of a GSM cell, the BSIC of the BCH frequency of the target cell on which the failure occurred. This field is encoded as the BSIC value defined in 3GPP TS 44.018.
Range 0 to 63
If a 3G Cell or an E-UTRAN Cell is indicated, this field shall be sent with the value 0.

| | | | | | | | | | | | | | | | | +|

CAUSE (4 bit field)
This field indicates the cause of the cell change order failure on the target cell.

bit
4 3 2 1

0 0 0 0Frequency not implemented
0 0 0 1No response on target cell
0 0 1 0Immediate Assign Reject or Packet Access Reject on target cell
0 0 1 1On going CS connection
0 1 0 0PS Handover failure-other
0 1 0 1MS in GMM Standby state
0 1 1 0Forced to the Standby state
All othersReserved for future use
| 0 0 0 0 | Frequency not implemented | 0 0 0 1 | No response on target cell | 0 0 1 0 | Immediate Assign Reject or Packet Access Reject on target cell | 0 0 1 1 | On going CS connection | 0 1 0 0 | PS Handover failure-other | 0 1 0 1 | MS in GMM Standby state | 0 1 1 0 | Forced to the Standby state | All others | Reserved for future use | +| 0 0 0 0 | Frequency not implemented | | | | | | | | | | | | | | | | +| 0 0 0 1 | No response on target cell | | | | | | | | | | | | | | | | +| 0 0 1 0 | Immediate Assign Reject or Packet Access Reject on target cell | | | | | | | | | | | | | | | | +| 0 0 1 1 | On going CS connection | | | | | | | | | | | | | | | | +| 0 1 0 0 | PS Handover failure-other | | | | | | | | | | | | | | | | +| 0 1 0 1 | MS in GMM Standby state | | | | | | | | | | | | | | | | +| 0 1 1 0 | Forced to the Standby state | | | | | | | | | | | | | | | | +| All others | Reserved for future use | | | | | | | | | | | | | | | | +|

UTRAN FDD Target cell

This information element contains the description of the UTRAN FDD Target cell. This information element is defined in sub-clause 12.31.

| | | | | | | | | | | | | | | | | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRAN TDD Target cell
This information element contains the description of the UTRAN TDD Target cell. This field is defined in sub-clause 12.32. | +| E-UTRAN Target cell
This information element contains the description of the E-UTRAN Target cell. This field is defined in sub-clause 12.49. If the conditions for sending the E-UTRAN Target cell with extended EARFCN information element are met (see definition of E-UTRAN Target cell with extended EARFCN IE below) then this information element shall not be included. | +| G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in Iu mode . | +| UTRAN CSG Target cell
This information element contains the routing parameters for the UTRAN CSG or hybrid cell. It is defined in sub-clause 12.63. | +| E-UTRAN CSG Target cell
This information element contains the routing parameters for the E-UTRAN CSG or hybrid cell. It is defined in sub-clause 12.62. | +| E-UTRAN Target cell with extended EARFCN
This information element contains the description of the E-UTRAN Target cell. It is defined in sub-clause 12.68. This information element shall only be included if both the mobile station and the network supports extended EARFCNs (see 3GPP TS 24.008); in such a case the E-UTRAN Target cell IE shall not be included in the message. | + +### 11.2.3a Packet Cell Change Notification + +This message is sent on the PACCH by the mobile station to the network to inform the network that the cell re-selection criteria are now fulfilled and that the mobile station has entered CCN mode or that the criteria specified in sub-clause 5.6.3.9 have been met in respect of a CSG or detected hybrid cell. + +Message type: PACKET CELL CHANGE NOTIFICATION + +Direction: mobile station to network + +**Table 11.2.3a.1: PACKET CELL CHANGE NOTIFICATION message content** + +``` + +< Packet Cell Change Notification message content > ::= + < Global TFI : < Global TFI IE > > + { 0 < ARFCN : bit (10) > + < BSIC : bit (6) > + | 10 -- Extension in Rel-6 and an escape bit for future extensions of the message added: + < 3G Target Cell : < 3G Target Cell Struct >> } -- Re-selection with a 3G cell as the preferred target cell + | 110 -- Extension in Rel-8 for E-UTRAN and an escape bit for future extensions of the message + { 0 | 1 < ARFCN : bit (10) > + < BSIC : bit (6) > } + { 0 | 1 < 3G Target Cell : < 3G Target Cell Struct >> } + { 0 | 1 < E-UTRAN Target Cell : < E-UTRAN Target Cell Struct >> } + { 0 | 1 < E-UTRAN CCN Measurement Report : < E-UTRAN CCN Measurement Report struct > > } + | 1110 -- Extension in Rel-9 for CSG target cells and an escape bit for future extensions of the message + { 0 + < UTRAN CSG Target Cell Measurement Report : < UTRAN CSG Measurement Report IE > > + | 1 + < E-UTRAN CSG Target Cell Measurement Report : < E-UTRAN CSG Measurement Report IE > > } + { 0 | 1 < E-UTRAN CCN Measurement Report : < E-UTRAN CCN Measurement Report struct > > } + ! < Message escape : { 1111 } bit (*) = > } + { 0 < BA_USED : bit > | 1 < PSI3_CHANGE_MARK : bit (2) > } + < PMO_USED : bit > + < PCCN_SENDING : bit (1) > + < CCN Measurement Report : < CCN Measurement Report struct > > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Addition in Rel-6 + { 0 | 1 < 3G_BA_USED : bit > } + < 3G CCN Measurement Report : < 3G CCN Measurement Report struct > > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-10 + < CSG Discriminator : bit (1) > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-11 + { 0 | 1 < E-UTRAN Target Cell with extended EARFCN : + < E-UTRAN Target Cell with extended EARFCN struct >> } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-12 + { 0 | 1 < Downlink_eTFI : bit (3) > } + < padding bits > } } } }; + +< CCN Measurement Report struct > ::= + < RXLEV_SERVING_CELL : bit (6) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < NUMBER_OF_NC_MEASUREMENTS : bit (3) > + { < FREQUENCY_N : bit (6) > + { 0 | 1 < BSIC_N : bit (6) > } + < RXLEV_N : bit (6) > } * (val(NUMBER_OF_NC_MEASUREMENTS)); + +< 3G Target Cell Struct > ::= + { 0 | 1 < FDD-ARFCN : bit (14) > -- 3G UTRAN FDD + { 0 | 1 < Bandwidth_FDD : bit (3) > } + < SCRAMBLING_CODE : bit (9) > } + { 0 | 1 < TDD-ARFCN : bit (14) > -- 3G UTRAN TDD + { 0 | 1 < Bandwidth_TDD : bit (3) > } + < Cell Parameter : bit (7) > + < Sync Case : bit > } + < REPORTING_QUANTITY : bit (6) > ; -- Measurement Report for 3G target cell + +< 3G CCN Measurement Report Struct > ::= -- Measurement Report for 3G neighbour cells + < N_3G : bit (3) > + { < 3G_CELL_LIST_INDEX : bit (7) > + < REPORTING_QUANTITY : bit (6) > } * (val(N_3G + 1 )); + +< E-UTRAN Target Cell struct > ::= + < EARFCN : bit (16) > + { 0 | 1 < Measurement Bandwidth : bit (3) > } + < Physical Layer Cell Identity : bit (9) > + < REPORTING_QUANTITY : bit (6) > ; -- Measurement Report for E-UTRAN target cell + +``` + +``` + +< E-UTRAN CCN Measurement Report struct > ::= -- Measurement Report for E-UTRAN neighbour cells + < 3G_BA_USED : bit > + < N_E-UTRAN: bit (2) > + { + < E-UTRAN_FREQUENCY_INDEX : bit (3) > + < CELL IDENTITY : bit (9) > + < REPORTING_QUANTITY : bit (6) > } * (val(N_E-UTRAN + 1 )); +< E-UTRAN Target Cell with extended EARFCN struct > ::= + < EARFCN_extended : bit (18) > + { 0 | 1 < Measurement Bandwidth: bit (3) > } + < Physical Layer Cell Identity : bit (9) > + < REPORTING_QUANTITY : bit (6) > ; -- Measurement Report for E-UTRAN target cell + +``` + +**Table 11.2.3a.2: PACKET CELL CHANGE NOTIFICATION information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Global TFI

This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10.

| +|

ARFCN (10 bit field)

This field contains the BCCH frequency of the proposed cell for re-selection. This field is encoded as the ARFCN defined in 3GPP TS 44.018.
Range 0 to 1023

| +|

BSIC (6 bit field)

This field contains the BSIC of the proposed cell for re-selection. This field is encoded as the BSIC value defined in 3GPP TS 44.018.
Range 0 to 63

| +|

BA_USED (1 bit field)

3G_BA_USED (1 bit field)

PSI3_CHANGE_MARK (2 bit field)

These fields shall be included and contain the value of the BA_IND, 3G_BA_IND and PSI3_CHANGE_MARK respectively in the messages defining the used GSM Neighbour Cell list.

In case PBCCH exists, PSI3_CHANGE_MARK shall be used.
In case PBCCH does not exist, BA_USED and 3G_BA_USED shall be used.

| +|

PMO_USED (1 bit field)

This parameter shall contain the value of the PMO_IND in the PACKET CELL CHANGE ORDER or PACKET MEASUREMENT ORDER messages that has modified the used GSM Neighbour Cell list. If no such message has been received, PMO_USED shall be set to zero.

| +|

CCN Measurement Report struct

This struct is identical to the NC Measurement Report struct specified in the PACKET MEASUREMENT REPORT message with the exception that the NC_MODE parameter is not part of the struct.

| +|

PCCN SENDING (1 bit field)

0 This is the first sending of the Packet Cell Change Notification message;
1 This is the second sending of the Packet Cell Change Notification message.

This field is used by the network to know whether the mobile station has just started T3208 or whether the reception of this message was triggered by T3210 expiry.

| +|

3G Target Cell struct

For information regarding the REPORTING QUANTITY see below. Regarding the other parameters see sub-clause 11.2.4 -PACKET CELL CHANGE ORDER message.

| + +#### **3G CCN Measurement Report struct** + +Measurement reporting for 3G Cells is defined in 3GPP TS 45.008. Should no 3G Cell be available for reporting, N\_3G shall be set to 0 and the 3G\_CELL\_LIST\_INDEX shall be set to 127 whenever this 3G CCN Measurement Report struct is included in the message. + +#### **3G\_CELL\_LIST\_INDEX (7 bit field)** + +This is the index of the i'th reported 3G neighbour cell in the 3G Neighbour Cell List. See sub-clause 5.6.3.1. + +##### **REPORTING\_QUANTITY (6 bit field)** + +This is the reporting quantity for the serving and for the i'th reported 3G cell. The quantities are defined in 3GPP TS 45.008 for the respective Radio Access Technology + +#### **E-UTRAN Target Cell struct** + +For information regarding the REPORTING QUANTITY see below. Regarding the other parameters see sub-clause 12.49. If the conditions for sending the *E-UTRAN Target cell with extended EARFCN* structure are met (see definition of *E-UTRAN Target Cell with extended EARFCN* below) then this structure shall not be included. + +#### **E-UTRAN CCN Measurement Report struct** + +Measurement reporting for E-UTRAN Cells is defined in 3GPP TS 45.008. + +#### **3G\_BA\_USED (1 bit field)** + +#### **N\_E-UTRAN (2 bit field)** + +##### **E-UTRAN\_FREQUENCY\_INDEX (3 bit field)** + +#### **CELL\_IDENTITY (9 bit field)** + +These fields are described in sub-clause 11.2.9. + +#### **REPORTING\_QUANTITY (6 bit field)** + +This is the reporting quantity for the E-UTRAN neighbour cell. The quantities are defined in 3GPP TS 45.008 for the respective Radio Access Technology. + +#### **UTRAN CSG Target Cell Measurement Report** + +Measurement reporting for UTRAN CSG cells is defined in 3GPP TS 45.008. This information element contains the measurement results and routing parameters for one UTRAN CSG or hybrid target cell. It is encoded as the UTRAN CSG Measurement Report IE defined in sub-clause 12.61. + +#### **E-UTRAN CSG Target Cell Measurement Report** + +Measurement reporting for E-UTRAN CSG cells is defined in 3GPP TS 45.008. This information element contains the measurement results and routing parameters for one E-UTRAN CSG or hybrid target cell. It is encoded as the E-UTRAN CSG Measurement Report IE defined in sub-clause 12.60. + +#### **CSG Discriminator (1 bit field)** + +This field is defined in sub-clause 5.6.3.9. It shall be included if the message includes a report for a CSG cell as specified in sub-clause 5.6.3.9, otherwise, it shall be omitted. + +#### **DOWNLINK\_eTFI (3 bit field)** + +See sub-clause 11.2.48 + +#### **E-UTRAN Target Cell with extended EARFCN struct** + +This structure shall only be included if both the mobile station and the network supports extended EARFCNs (see 3GPP TS 24.008); in such a case the *E-UTRAN Target Cell* structure shall not be included in the message. + +For information regarding the *REPORTING QUANTITY* field see above. For a description of the remaining fields included within this struct, see sub-clause 12.49 and 12.70. + +### 11.2.4 Packet Cell Change Order + +This message is sent on the PCCCH or PACCH by the network to the mobile station to command the mobile station to leave the current cell and change to a new cell. For a (3G) multi-RAT mobile station the new cell may be a 3G Cell. For a (E-UTRAN) multi-RAT mobile station the new cell may be an E-UTRAN cell. + +Message type: PACKET CELL CHANGE ORDER + +Direction: network to mobile station + +**Error:** + +**110** + +**Error: Reference source not** + +**found** + +**found** + +Classification: non-distribution message + +**Table 11.2.4.1: PACKET CELL CHANGE ORDER message content** + +``` +< Packet Cell Change Order message content > ::= + < PAGE_MODE : bit (2) > + { { 0 < Global TFI : < Global TFI IE > > + | 10 < TLLI / G-RNTI : bit (32) > } + { 0 + { < IMMEDIATE_REL : bit > + < GSM target cell: < GSM target cell struct >> + ! < Non-distribution part error : bit (*) = < no string > > } + | 1 + { 00 -- Message escape + { < IMMEDIATE_REL : bit > + { 0 | 1 < UTRAN FDD Target cell: < UTRAN FDD Target cell IE > > } + { 0 | 1 < UTRAN TDD Target cell: < UTRAN TDD Target cell IE > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-8 + { 0 | 1 < E-UTRAN Target cell : < E-UTRAN Target cell IE >> } + { 0 | 1 < Individual Priorities : < Individual Priorities IE >> } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-11 + { 0 | 1 < E-UTRAN Target cell with extended EARFCN : + < E-UTRAN Target cell with extended EARFCN IE >> } + { 0 | 1 < E-UTRAN IPP with extended EARFCNs: + < E-UTRAN IPP with extended EARFCNs IE >> } + < padding bits > } } } + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Message escape : { 01 | 10 | 11 } bit (*) = < no string > > } } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; +``` + +``` + +< GSM target cell struct > ::= + < ARFCN : bit (10) > + < BSIC : bit (6) > + < NC Measurement Parameters : < NC Measurement Parameters struct > > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release 98 : + { 0 | 1 < LSA Parameters : < LSA Parameters IE >> } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release 99 : + < ENH Measurement parameters : < ENH Measurement parameters struct >> + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-4 : + < CCN_ACTIVE : bit (1) > + { 0 | 1 < CONTAINER_ID : bit (2) > } + { 0 | 1 < CCN Support Description : < CCN Support Description struct >> } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + { 0 | 1 < Iu Mode Neighbour Cell Parameters : { 1 < Iu Mode Neighbour Cell params struct > } ** 0 + --Supplementary information for dual Iu mode and A/Gb mode capable cells + { 0 | 1 < NC Iu MODE ONLY CAPABLE CELL LIST : NC Iu Mode Only Cell List struct > } + { 0 | 1 < GPRS 3G Additional Measurement Parameters Description 2 : + < GPRS 3G Additional Measurement Parameters Description 2 struct >> } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-6 : + < 3G_CCN_ACTIVE : bit (1) > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-7 : + { 0 | 1 < 700_REPORTING_OFFSET : bit (3) > + < 700_REPORTING_THRESHOLD : bit (3) > } + { 0 | 1 < 810_REPORTING_OFFSET : bit (3) > + < 810_REPORTING_THRESHOLD : bit (3) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-8 + < E-UTRAN_CCN_ACTIVE : bit (1) > + { 0 | 1 < Individual Priorities : < Individual Priorities IE >> } + < padding bits > } } } } } } ; +> } + +< NC Measurement Parameters struct > ::= + < NETWORK_CONTROL_ORDER : bit (2) > + { 0 | 1 < NC_NON_DRX_PERIOD : bit (3) > + < NC_REPORTING_PERIOD_I : bit (3) > + < NC_REPORTING_PERIOD_T : bit (3) > } + { 0 | 1 < NC_FREQUENCY_LIST : NC Frequency list struct > } ; + +< NC Frequency list struct > ::= + { 0 | 1 < NR_OF_REMOVED_FREQ : bit (5) > + { < REMOVED_FREQ_INDEX : bit (6) > } * (1 + val(NR_OF_REMOVED_FREQ)) } + { 1 < List of added Frequency : < Add Frequency list struct > > } ** 0; + +< Add Frequency list struct > ::= + < START_FREQUENCY : bit (10) > + < BSIC : bit (6) > + { 0 | 1 < Cell selection params : < Cell Selection struct > > } + < NR_OF_FREQUENCIES : bit (5) > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (val(FREQ_DIFF_LENGTH)) > + < BSIC : bit (6) > + { 0 | 1 < Cell selection params : < Cell Selection struct > > } } * (val(NR_OF_FREQUENCIES)); + +``` + +``` +< Cell Selection struct > ::= + < CELL_BAR_ACCESS_2 : bit (1) > + < EXC_ACC : bit > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13_PBCCH_LOCATION : < SI13_PBCCH_LOCATION struct > > } ; + +< SI13_PBCCH_LOCATION struct > ::= + { 0 < SI13_LOCATION : bit (1) > + | 1 < PBCCH_LOCATION : bit (2) > + < PSI1_REPEAT_PERIOD : bit (4) > } ; + +< HCS struct > ::= + < PRIORITY_CLASS : bit (3) > + < HCS_THR : bit (5) > ; + +< ENH Measurement parameters struct > ::= + { 0 < BA_IND : bit > < 3G_BA_IND : bit > | 1 < PSI3_CHANGE_MARK : bit(2) > } + < PMO_IND : bit > + < REPORT_TYPE : bit > + < REPORTING_RATE : bit > + < INVALID_BSIC_REPORTING : bit > + { 0 | 1 < 3G Neighbour Cell Description : < 3G Neighbour Cell Description struct >> } + { 0 | 1 < GPRS REP PRIORITY Description : < GPRS REP PRIORITY Description struct >> } + { 0 | 1 < GPRS MEASUREMENT Parameters Description : + < GPRS MEASUREMENT PARAMETERS Description struct >> } + { 0 | 1 < GPRS 3G MEASUREMENT Parameters Description : + < GPRS 3G MEASUREMENT PARAMETERS Description struct >> } ; + +< 3G Neighbour Cell Description struct > ::= + { 0 | 1 < Index_Start_3G : bit (7) > } + { 0 | 1 < Absolute_Index_Start_EMR : bit (7) > } + { 0 | 1 < UTRAN FDD Description : < UTRAN FDD Description struct >> } + { 0 | 1 < UTRAN TDD Description : < UTRAN TDD Description struct >> } + { 0 | 1 < REMOVED_3GCELL_Description : < REMOVED_3GCELL_Description struct >> } ; + +< REMOVED_3GCELL_Description struct > ::= + < N1 : bit (2) > + { < N2 : bit (5) > + { < REMOVED_3GCELL_INDEX : bit (7) > + < 3G_CELL_DIFF_LENGTH : bit (3) > + < 3GCELL_DIFF : bit (val(3G_CELL_DIFF_LENGTH)) > + } * (1+val(N2)) + } * (1+val(N1)) ; + +< UTRAN FDD Description struct > ::= + { 0 | 1 < Bandwidth_FDD : bit (3) > } + { 1 < Repeated UTRAN FDD Neighbour Cells : < Repeated UTRAN FDD Neighbour Cells struct >> } ** 0 ; + +< Repeated UTRAN FDD Neighbour Cells struct > ::= + 0 < FDD-ARFCN : bit (14) > -- The value '1' was used in an earlier + -- version of the protocol and shall not be used. + < FDD_Indic0 : bit > + < NR_OF_FDD_CELLS : bit (5) > + < FDD_CELL_INFORMATION Field : bit(p(NR_OF_FDD_CELLS)) > ; + -- p(x) defined in table 11.2.9b.2.a/3GPP TS 44.060 + +< UTRAN TDD Description struct > ::= + { 0 | 1 < Bandwidth_TDD : bit (3) > } + { 1 < Repeated UTRAN TDD Neighbour Cells : < Repeated UTRAN TDD Neighbour Cells struct >> } ** 0 ; +``` + +``` + +< Repeated UTRAN TDD Neighbour Cells struct > ::= + 0 < TDD-ARFCN : bit (14) > -- The value '1' was used in an earlier + -- version of the protocol and shall not be used. + + < TDD_Indic0 : bit > + < NR_OF_TDD_CELLS : bit (5) > + < TDD_CELL_INFORMATION Field : bit(q(NR_OF_TDD_CELLS)) > ; + -- q(x) defined in table 11.2.9b.2.b/3GPP TS 44.060. + +< GPRS REP PRIORITY Description struct > ::= + < Number_Cells : bit(7) > + { < REP_PRIORITY : bit > } * (val(Number_Cells)); + +< GPRS MEASUREMENT PARAMETERS Description struct > ::= + { 0 | 1 < MULTIBAND_REPORTING : bit (2) > } + { 0 | 1 < SERVING_BAND_REPORTING : bit (2) > } + < SCALE_ORD : bit(2) > + + { 0 | 1 < 900_REPORTING_OFFSET : bit (3) > + < 900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1800_REPORTING_OFFSET : bit (3) > + < 1800_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 400_REPORTING_OFFSET : bit (3) > + < 400_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1900_REPORTING_OFFSET : bit (3) > + < 1900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 850_REPORTING_OFFSET : bit (3) > + < 850_REPORTING_THRESHOLD : bit (3) > } ; + +< GPRS 3G MEASUREMENT PARAMETERS Description struct > ::= + < Qsearch_P : bit (4) > + { 1 ! < Ignore : bit = < no string >> } -- this bit shall be ignored by the receiver + -- for backward compatibility with earlier releases + { 0 | 1 < FDD REP QUANT : bit > -- FDD Parameters + < FDD_MULTIRAT_REPORTING : bit (2) > } + + { 0 | 1 < FDD_REPORTING_OFFSET : bit (3) > + < FDD_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) > -- TDD Parameters + { 0 | 1 < TDD_REPORTING_OFFSET : bit (3) > + < TDD_REPORTING_THRESHOLD : bit (3) > } ; + +< CCN Support Description struct > ::= + < Number_Cells : bit (7) > + { CCN_SUPPORTED : bit } * (val(Number_Cells)); +< Iu Mode Neighbour Cell Params struct > ::= + { 0 | 1 < Iu Mode Cell Selection Params : > } + < NR_OF_FREQUENCIES : bit (5) > + { 0 | 1 < Iu Mode Cell Selection Params : + < Iu Mode Cell Selection struct > > } * (val(NR_OF_FREQUENCIES)); +< Iu Mode Cell Selection struct > ::= + < CELL BAR QUALIFY 3 : bit (2) > + { 0 | 1 < SI13Alt PBCCH Location : < SI13 PBCCH Location struct > > } ; +< NC Iu Mode Only Cell List struct > ::= + { 1 < List of added cells : < Add Iu Mode Only Cell List struct > > } ** 0; + +``` + +``` + +< Add Iu Mode Only Cell List struct > ::= + < START_FREQUENCY : bit (10) > + < BSIC : bit (6) > + { 0 | 1 < Cell selection params : < Iu Mode Only Cell Selection struct > > } + { < NR_OF_FREQUENCIES : bit (5) > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (val(FREQ_DIFF_LENGTH)) > + < BSIC : bit (6) > + { 0 | 1 < Cell selection params : < Iu Mode Only Cell Selection struct > > } } * (val(NR_OF_FREQUENCIES)) } + ; + +< Iu Mode Only Cell Selection struct > ::= + < CELL BAR QUALIFY 3 : bit (2) > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13Alt_PBCCH_LOCATION : < SI13_PBCCH_LOCATION struct > > } ; + +< GPRS 3G Additional Measurement Parameters Description 2 struct > ::= + { 0 | 1 < FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; -- FDD Parameters + +``` + +**Table 11.2.4.2: PACKET CELL CHANGE ORDER information element details** + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------|---|-----------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

| | | | | +|

Global TFI
This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10.

| | | | | +|

TLLI / G-RNTI (32 bit field)
This field is defined in sub-clause 12.16.

| | | | | +|

IMMEDIATE_REL (1 bit field)
This field indicates whether the MS shall immediately abort any operation in the old cell and move to the target cell (see sub-clause 8.4), or it shall not immediately abort operation in the old cell and follow the cell reselection procedure defined in sub-clause 5.5.1.1. This field is coded according to the following table:

0 No immediate abort of operation in the old cell is required.
1 Immediate abort of operation in the old cell is required.
| 0 | No immediate abort of operation in the old cell is required. | 1 | Immediate abort of operation in the old cell is required. | +| 0 | No immediate abort of operation in the old cell is required. | | | | +| 1 | Immediate abort of operation in the old cell is required. | | | | +|

ARFCN (10 bit field)
This field contains the BCCH frequency of the new cell. This field is encoded as the ARFCN defined in 3GPP TS 44.018.
Range 0 to 1023

| | | | | + +#### **BSIC (6 bit field)** + +This field contains the BSIC of the new cell. This field is encoded as the BSIC value defined in 3GPP TS 44.018. Range 0 to 63 + +#### **CCN\_ACTIVE (1 bit field)** + +This field indicates whether CCN is enabled towards GSM cells for the mobile station in the GSM cell addressed by ARFCN and BSIC. It is coded as follows: + +- 0 The broadcast CCN\_ACTIVE parameter shall apply if available. Otherwise, CCN is disabled for the mobile station. +- 1 CCN is enabled for the mobile station. + +#### **CONTAINER\_ID (2 bit field)** + +This optional parameter is included only if the network has earlier sent neighbour cell system information for the cell addressed by the ARFCN and the BSIC. For detailed element definition see sub-clause 11.2.2.a. + +The **NC\_Measurement\_Parameters struct** contains the NETWORK\_CONTROL\_ORDER and the optional parameters NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I, NC\_REPORTING\_PERIOD\_T and the NC\_FREQUENCY LIST. These parameters shall apply in the target cell (see sub-clause 5.6.1) + +#### **NETWORK\_CONTROL\_ORDER (2 bit field)** + +The NETWORK\_CONTROL\_ORDER field is coded according to the following table (for definition of NCx see 3GPP TS 45.008): + +| bit | | +|-----|---------| +| 2 | 1 | +| 0 | 0 NC0 | +| 0 | 1 NC1 | +| 1 | 0 NC2 | +| 1 | 1 RESET | + +#### **NC\_NON\_DRX\_PERIOD (3 bit field)** + +#### **NC\_REPORTING\_PERIOD\_I (3 bit field)** + +#### **NC\_REPORTING\_PERIOD\_T (3 bit field)** + +For detailed element definitions see the PSI5 message. + +#### **NR\_OF\_REMOVED\_FREQ (5 bit field)** + +#### **REMOVED\_FREQ\_INDEX (6 bit field)** + +#### **START\_FREQUENCY (10 bit field)** + +#### **BSIC (6 bit field)** + +For detailed element definitions, see the Packet Measurement Order message + +#### **FREQ\_DIFF\_LENGTH (3 bit field)** + +This field is required to calculate the number of bits to be used for the FREQUENCY\_DIFF field in the current frequency group. The FREQ\_DIFF\_LENGTH value shall be different to 0. + +#### **FREQUENCY\_DIFF (val(FREQ\_DIFF\_LENGTH) bit field)** + +Each FREQUENCY\_DIFF parameter field specifies the difference in frequency to the next carrier to be defined. The FREQUENCY\_DIFF parameter encodes a non negative integer in binary format (W). Each frequency following the start frequency (ARFCN(0)) and belonging to the Frequency List struct is then calculated by the formula $ARFCN(n) = (ARFCN(n-1) + W(n)) \bmod 1024$ , $n=1, \dots, val(NR\_OF\_FREQUENCIES)$ . + +#### **LSA Parameters** + +This information element is defined in sub-clause 12.28. The 'LSA parameters IE' is optional. For detailed element definition, see the PSI3 message. + +#### **ENH Measurement Parameters:** + +For detailed element definitions see the Packet Measurement Order message (except that CDMA2000 Description struct does not exist in this message). + +#### **UTRAN FDD Target cell** + +This information element contains the description of the UTRAN FDD Target cell. This information element is defined in sub-clause 12.31. + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

UTRAN TDD Target cell

This information element contains the description of the UTRAN TDD Target cell. This information element is defined in sub-clause 12.32.

| +|

E-UTRAN Target cell

This information element contains the description of the E-UTRAN Target cell. This information element is defined in sub-clause 12.49. If the conditions for sending the E-UTRAN Target cell with extended EARFCN information element are met (see definition of E-UTRAN Target cell with extended EARFCN IE below) then this information element shall not be included.

| +|

GPRS MEASUREMENT PARAMETERS Description

The fields of this Description are used for measurements, as defined in 3GPP TS 45.008. Any parameter present overwrites any old data held by the mobile station for this parameter.

| +|

GPRS 3G MEASUREMENT PARAMETERS Description

The fields of this Description are used for measurements, as defined in 3GPP TS 45.008. Any parameter present overwrites any old data held by the mobile station for this parameter.

| +|

GPRS REP PRIORITY Description

REP_PRIORITY bit:
0 Normal reporting priority
1 High reporting priority
The use of these bits is defined in sub-clause 5.6.3.5 and 3GPP TS 45.008.

| +|

CCN Support Description

CCN_SUPPORTED (1 bit field)
This parameter is used for determining whether the mobile station shall enter CCN mode when re-selecting a GSM cell and CCN is enabled. The use of these bits is described in sub-clause 8.8.2a:
Bit
0 CCN is enabled towards the corresponding cell
1 CCN is disabled towards the corresponding cell

| +|

G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in Iu mode.

| +|

Iu Mode Neighbour Cell Parameters

The Iu mode Neighbour Cell Parameters shall only be included when the List of added Frequency struct is present.

| +|

Iu Mode Neighbour Cell Params Struct

This struct presents supplementary information for Iu mode capable cells. The struct assigns Iu mode parameter values to the neighbouring cells defined by the message. The Iu mode Neighbour Cell params struct values are assigned to the neighbouring cells in the same order they appear in the List of added Frequency struct.

| +|

NC Iu Mode Only Capable Cell List Parameters

These parameters are used to add Iu mode only capable cells to BA(GPRS) list.

| +|

CELL BAR QUALIFY 3 (2 bit field)

This information element is defined in 3GPP TS 44.018.

| +|

GPRS 3G Additional Measurement Parameters Description 2

The fields of this Description are used for measurements, as defined in 3GPP TS 45.008. Any parameter present overwrites any old data held by the mobile station for this parameter.

| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G_CCN_ACTIVE (1 bit field)
This field indicates whether CCN is enabled towards 3G neighbouring cells. It is coded as follows:
0   The broadcast 3G_CCN_ACTIVE parameter shall apply if available. Otherwise, CCN towards 3G cells is disabled in the cell.
1   CCN towards 3G cells is enabled in the cell. | +| 700_REPORTING_OFFSET (3 bit field)
700_REPORTING_THRESHOLD (3 bit field)
These fields are used for measurements, as defined in 3GPP TS 45.008.
Any parameter present overwrites any old data held by the mobile station for these parameters. | +| 810_REPORTING_OFFSET (3 bit field)
810_REPORTING_THRESHOLD (3 bit field)
These fields are used for measurements, as defined in 3GPP TS 45.008.
Any parameter present overwrites any old data held by the mobile station for these parameters. | +| E-UTRAN_CCN_ACTIVE (1 bit field)
This field indicates whether CCN is enabled towards E-UTRAN neighbouring cells in the target cell. For description and encoding see subclause 12.53. | +| Individual Priorities
This information element is defined in sub-clause 12.50. If the conditions for sending the E-UTRAN IPP with extended EARFCNs information element are met (see definition of E-UTRAN IPP with extended EARFCNs IE below) then the E-UTRAN Individual Priority Parameters Description IE shall not be provided within the Individual Priorities information element. | +| E-UTRAN Target cell with extended EARFCN
This information element contains the description of the E-UTRAN Target cell. It is defined in sub-clause 12.68. This information element shall only be included if both the network and the mobile station support extended EARFCNs (see 3GPP TS 24.008); in such a case the E-UTRAN Target Cell IE shall not be provided in the message. | +| E-UTRAN IPP with extended EARFCNs
This information element is defined in sub-clause 12.69. It shall be included if E-UTRAN individual priorities are provided and both the network and the mobile station support extended EARFCNs (see 3GPP TS 24.008); in such a case the E-UTRAN Individual Priority Parameters Description IE shall not be provided within the Individual Priorities IE (see definition of Individual Priorities IE above). | + +### 11.2.5 Packet Channel Request + +This message is sent in random mode on the PRACH using the PRACH uplink block format defined in 3GPP TS 44.004. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. + +The message format is either 11-bit or 8-bit. The mobile station shall use the format indicated by the System Information parameter ACCESS\_BURST\_TYPE + +The 11-bit format is coded as shown in table 11.2.5.1. + +The 8-bit format is coded as shown in table 11.2.5.2. + +Table 11.2.5.1: PACKET CHANNEL REQUEST 11 bit message content + +``` + +< Packet channel request 11 bit message content > ::= + < One Phase Access Request : 0 < MultislotClass : bit (5) > + < Priority : bit (2) > + < RandomBits : bit (3) > > + | < Short Access Request : 100 -- The value 100 was allocated in an earlier version of the protocol and shall not + be used by the mobile station + < NumberOfBlocks : bit (3) > + < Priority : bit (2) > + < RandomBits : bit (3) > > + | < Two Phase Access Request : 110000 < Priority : bit (2) > + < RandomBits : bit (3) > > + | < Page Response : 110001 < RandomBits : bit (5) > > + | < Cell Update : 110010 < RandomBits : bit (5) > > + | < MM Procedure : 110011 < RandomBits : bit (5) > > + | < Single Block Without TBF Establishment : 110100 < RandomBits : bit (5) > > + | < One Phase Access Request in RLC unack mode : 110101 < RandomBits : bit (5) > > + | < Dedicated channel request : 110110 < RandomBits : bit (5) > > + | < Emergency call : 110111 < RandomBits : bit (5) > > + | < Single block MBMS access : 111000 < RandomBits : bit (5) > > ; + +``` + +Table 11.2.5.2: PACKET CHANNEL REQUEST 8 bit message content + +``` + +< Packet channel request 8 bit message content > ::= + < One Phase Access Request : 1 < MultislotClass : bit (5) > + < RandomBits : bit (2) > > + | < Short Access Request : 00 -- The value 00 was allocated in an earlier version of the protocol and shall not be + used by the mobile station + < NumberOfBlocks : bit (3) > + < RandomBits : bit (3) > > + | < Two Phase Access Request : 01000 < RandomBits : bit (3) > > + | < Page Response : 01001 < RandomBits : bit (3) > > + | < Cell Update : 01010 < RandomBits : bit (3) > > + | < MM Procedure : 01011 < RandomBits : bit (3) > > + | < Single Block Without TBF Establishment : 01100 < RandomBits : bit (3) > > + | < One phase Access Request in RLC unack mode : 011010 < RandomBits : bit (2) > > + | < Dedicated channel request : 011011 < RandomBits : bit (2) > > + | < Emergency call : 011100 < RandomBits : bit (2) > > + | < Single block MBMS access : 01111 < RandomBits : bit (3) > > ; + +``` + +Table 11.2.5.3: PACKET CHANNEL REQUEST details + +#### **MultislotClass** (5 bit field) + +This information field indicates the GPRS multislot class of the MS. The multislot class indicated by this field shall be the same as the GPRS multislot class indicated in the MS Radio Access Capability IE (see 3GPP TS 24.008). The coding is defined in the following table. + +| bit | | +|-----------|--------------------| +| 5 4 3 2 1 | | +| 0 0 0 0 0 | multislot class 1 | +| 0 0 0 0 1 | multislot class 2 | +| ⋮ | ⋮ | +| 1 1 1 0 0 | multislot class 29 | +| other | reserved values | + +| | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--|-------|--|-------|-------------------------------------|-------|-------------------|-----|------------------|-------|-----------------------------------| +|

Priority (2 bit field)

This information field indicates the requested Radio Priority. This field is coded as shown in the following table. The 8 bit format has a default Radio Priority of 4.

bit
2 1
0 0Radio Priority 1 (Highest priority)
0 1Radio Priority 2
1 0Radio Priority 3
1 1Radio Priority 4 (Lower priority)
| bit | | 2 1 | | 0 0 | Radio Priority 1 (Highest priority) | 0 1 | Radio Priority 2 | 1 0 | Radio Priority 3 | 1 1 | Radio Priority 4 (Lower priority) | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | Radio Priority 1 (Highest priority) | | | | | | | | | | | | +| 0 1 | Radio Priority 2 | | | | | | | | | | | | +| 1 0 | Radio Priority 3 | | | | | | | | | | | | +| 1 1 | Radio Priority 4 (Lower priority) | | | | | | | | | | | | +|

NumberOfBlocks (3 bit field)

This information field indicates the number of blocks requested during a mobile originated Temporary Block Flow. This field is coded as shown in the following table:

bit
3 2 1
0 0 01 RLC data block
0 0 12 RLC data blocks
...
1 1 18 RLC data blocks
| bit | | 3 2 1 | | 0 0 0 | 1 RLC data block | 0 0 1 | 2 RLC data blocks | ... | | 1 1 1 | 8 RLC data blocks | +| bit | | | | | | | | | | | | | +| 3 2 1 | | | | | | | | | | | | | +| 0 0 0 | 1 RLC data block | | | | | | | | | | | | +| 0 0 1 | 2 RLC data blocks | | | | | | | | | | | | +| ... | | | | | | | | | | | | | +| 1 1 1 | 8 RLC data blocks | | | | | | | | | | | | +|

RandomBits (2 bit field or 3 bit field or 5 bit field)

This is an unformatted field.

| | | | | | | | | | | | | + +#### 11.2.5a EGPRS Packet Channel Request + +This message may be sent by an EGPRS capable mobile station in a cell supporting EGPRS and where the EGPRS\_PACKET\_CHANNEL\_REQUEST parameter indicates that this message shall be used. + +This message is sent in random mode on the PRACH using the PRACH uplink block format or on the RACH (see 3GPP TS 44.018) using the RACH uplink / Uplink access burst block format defined in 3GPP TS 44.004. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. The message is coded in 11-bit format. + +The EGPRS capability is indicated using alternative training sequences (see 3GPP TS 45.002). + +**Table 11.2.5a.1: EGPRS PACKET CHANNEL REQUEST messages (non-PEO access)** + +| Training sequence
(see 3GPP TS 45.002) | bits
11.....1 | Packet Channel Access | +|-------------------------------------------|--------------------------------------------------|-----------------------------------------| +| TS1 | < EGPRS Packet channel request message content > | EGPRS with 8PSK capability in uplink | +| TS2 | < EGPRS Packet channel request message content > | EGPRS without 8PSK capability in uplink | + +Table 11.2.5a.2: EGPRS PACKET CHANNEL REQUEST message content (non-PEO access) + +| | | | +|--------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < EGPRS Packet channel request message content > ::= | | | +| < One Phase Access Request : | 0 | < MultislotClass : bit (5) >
< Priority : bit (2) >
< RandomBits : bit (3) > | +| < Short Access Request : | 100 | -- The value 100 was allocated in an earlier version of the protocol and shall not be used
< NumberOfBlocks : bit (3) >
< Priority : bit (2) >
< RandomBits : bit (3) > | +| < One Phase Access Request by Reduced Latency MS : 101 | | < MultislotClassGroup : bit (3) >
< Priority : bit (2) >
< RandomBits : bit (3) > | +| < Two Phase Access Request : | 110000 | < Priority : bit (2) >
< RandomBits : bit (3) > | +| < Signalling : | 110011 | < RandomBits : bit (5) > | +| < One phase Access Request in RLC unack mode : | 110101 | < RandomBits : bit (5) > | +| < Dedicated Channel Request : | 110110 | < RandomBits : bit (5) > | +| < Emergency call : | 110111 | < RandomBits : bit (5) > | +| < Two Phase Access Request by IPA capable MS | 111000 | < Priority : bit (2) >
< RandomBits : bit (3) > | +| < Signalling by IPA capable MS : | 111001 | < RandomBits : bit (5) > | + +Table 11.2.5a.3: EGPRS PACKET CHANNEL REQUEST messages (PEO access) + +| Training sequence
(see 3GPP TS 45.002) | bits
11.....1 | Packet Channel Access | +|-------------------------------------------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TS4 | < EGPRS PACKET CHANNEL REQUEST message content > | Access from a MS that has enabled PEO and is performing the Packet Access procedure. | +| TS4 | < EGPRS MULTILATERATION REQUEST message content > | Access from a MS that has enabled PEO and is performing the radio access part of the MTA procedure using the RLC Data Block method or sending a Page Response for a positioning event (see Table 11.2.5a.4). | + +Table 11.2.5a.4: EGPRS PACKET CHANNEL REQUEST message and EGPRS MULTILATERATION REQUEST message content (PEO access) + +| TS | Bit 11 | Bit 10 | Bit 9 | Bit 8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | +|----|--------|--------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------| +| 4 | 0 | 0 | 0 | | | | | | | | | +| | | | | < EGPRS PACKET CHANNEL REQUEST message content for 'PEO One Phase Access Request' > ::=
< Access Cause : bit (2) >
< PEO Priority : bit (1) >
< Random Bits : bit (3) >
< EGPRS Capability : bit (1) >
< Spare : bit (1) > ; | | | | | | | | +| 4 | 0 | 0 | 1 | | | | | | | | | +| | | | | < EGPRS MULTILATERATION REQUEST message content (RLC Data Block method or Page Response for Positioning Event) > ::=
< RandomBits : bit (3) >
< Access Discriminator : bit (1) >
< Final MTA Access : bit (1) >
< Spare : bit (3) > ; | | | | | | | | +| 4 | 0 | 1 | 0 | | | | | | | | | +| | | | | < EGPRS MULTILATERATION REQUEST message content (Access Burst method) > ::=
< Short ID : bit (8) > ; | | | | | | | | +| 4 | 0 | 1 | 1 | | | | | | | | | +| | | | | < EGPRS MULTILATERATION REQUEST message content (Extended Access Burst Method – part 1) > ::= | | | | | | | | + +| | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------|---|---|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | < Random ID Low : bit (4) >
< MS Transmission Offset : bit (4) > ; | +| 4
(Note 1) | 1 | 0 | 0 | < EGPRS MULTILATERATION REQUEST message content (Extended Access Burst Method – part 2) > ::=
< Random ID Low : bit (4) >
< MS Sync Accuracy : bit (4) > ; | +| 4 | 1 | 0 | 1 | Spare (8) | +| 4 | 1 | 1 | Spare (9) | | +| Note 1: See Table 11.2.5a.4.1 for 19 remaining bits of EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 2'. | | | | | + +NOTE: A mobile station that has enabled PEO (i.e. eDRX or PSM – see 3GPP TS 23.060 [19]) while in a cell that supports PEO, shall always send an EGPRS PACKET CHANNEL REQUEST message using TS4 (see Table 11.2.5a.3) and access type 'PEO One Phase Access Request' (see Table 11.2.5a.4) on the RACH when performing the Packet Access procedure. A mobile station that has enabled PEO while in a cell that supports PEO shall send an EGPRS MULTILATERATION REQUEST message on the RACH when performing the radio access part of the MTA procedure or when sending a Page Response due to receiving a page with a 'pending positioning event' indication (see 3GPP TS 44.018 [11] and 3GPP TS 44.031). The MTA method indicated by the EGPRS MULTILATERATION REQUEST message (i.e. one of the RLC Data Block method, Access Burst method or Extended Access Burst method) shall be supported by both the mobile station and the cell. + +**Table 11.2.5a.4.1: EGPRS MULTILATERATION REQUEST message indicating 'Extended Access Burst Method – part 2' (Bit 12 to Bit 30)** + +| TS | Bits 12 to Bit 30 | +|------------|------------------------------------------------------------------------------------------------------------------------| +| 4
(CC1) | < Random ID High : bit (12) >
< Short BSS ID : bit (3) >
< Final MTA Access : bit (1) >
< spare : bit (3) > ; | + +**Table 11.2.5a.5: EGPRS PACKET CHANNEL REQUEST details** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +|

MultislotClass (5 bit field)

This information field indicates the EGPRS multislot class of the MS. The multislot class indicated by this field shall be the same as the EGPRS multislot class indicated in the MS Radio Access Capability IE (see 3GPP TS 24.008). The coding is defined in the following table.

| | +| bit | | +| 5 4 3 2 1 | | +| 0 0 0 0 0 | multislot class 1 | +| 0 0 0 0 1 | multislot class 2 | +| : : | | +| 1 1 1 0 0 | multislot class 29 | +| 1 1 1 0 1 | multislot class with Tx=1 by IPA capable MS, the network shall assume the MS is multislot class 1 | +| 1 1 1 1 0 | multislot class with Tx=2 by IPA capable MS, the network shall assume the MS is multislot class 5 | +| 1 1 1 1 1 | multislot class with Tx=4 by IPA capable MS, the network shall assume the MS is multislot class 12 | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Priority (2 bit field)

This information field indicates the requested Radio Priority. This field is coded as shown in the following table. The 8 bit format has a default Radio Priority of 4.

bit
2 1
0 0 Radio Priority 1 (Highest priority)
0 1 Radio Priority 2
1 0 Radio Priority 3
1 1 Radio Priority 4 (Lower priority) | +| Access Cause (2 bit field)

This field indicates the type of payload a mobile station has to send as follows:

bit
2 1
0 0 signalling (e.g. page response, cell update, MM signalling, etc)
0 1 single block transfer
1 0 User data transfer - requested RLC mode = acknowledged
1 1 reserved | +| PEO Priority (1 bit field)

This field indicates the priority of the uplink data transfer being requested by the mobile station as follows:

0 low priority packet transfer
1 high priority packet transfer | +| EGPRS capability (1 bit field)

This field indicates whether the MS supports GMSK only (EGPRS without 8PSK) or GMSK and 8PSK (EGPRS with 8PSK on uplink and downlink)

0 EGPRS without 8PSK
1 EGPRS with 8PSK (uplink and downlink) | +| RandomBits (3 bit field or 5 bit field)
For the definition of these three last information fields see Packet Channel Request in sec. 11.2.5. | +| MultislotClassGroup (3 bit field)

This information field indicates the set of the EGPRS multislot classes to which the mobile station belongs. The network shall assume the longest transition times ( $T_{ta}$ , $T_{tb}$ , $T_{ra}$ , $T_{rb}$ ) and the minimum number of RX, TX and SUM slots common to multislot classes in each set for the assignments (see Annex L).

bit       multislot classes
3 2 1
0 0 0       5-7
0 0 1       9-11
0 1 0       31, 36, 41
0 1 1       12, 32, 37, 42
1 0 0       33, 34, 43
1 0 1       38, 39
1 1 0       44, 45
1 1 1       reserved | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Access Discriminator (1 bit field)

This field indicates whether the MS sending an EGPRS MULTILATERATION REQUEST message for performing the radio access part of the MTA procedure using the RLC Data Block method or for sending a Page Response for a positioning event:

bit

0      MTA procedure using the RLC Data Block method

1      Page Response for a positioning event

| +|

Short ID (8 bit field)

This field identifies a 8 bit Short ID value used by a MS performing the radio access part of the MTA procedure using the Access Burst method (see 3GPP TS 44.018 [11]). The Short ID value used by a MS in a given cell is pre-determined (selected by the SMLC and included as part of the assistance information included in a RRLP message sent to a MS to trigger the Multilateration Timing Advance procedure – see 3GPP TS 44.031). It allows the BSS managing a cell in which it receives an EGPRS MULTILATERATION REQUEST message indicating ‘Access burst method’ to identify the applicable SCCP connection between the BSS and the serving SMLC (see 3GPP TS 49.031 and 3GPP TS 44.031).

| +|

Random ID Low (4 bit field)

This field is sent as part of an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst Method – part 1’ or ‘Extended Access Burst Method – part 2’. It consists of the 4 least significant bits of the Random ID parameter provided to the MS in the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031).

| +|

MS Transmission Offset (4 bit field)

This field is sent as part of an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst Method – part 1’ or included in a RLC Data Block following the transmission of an EGPRS MULTILATERATION REQUEST message indicating ‘RLC Data Block method’ or ‘Page Response for Positioning Event’. It is coded as described in sub-clause 10.4.33

| +|

MS Sync Accuracy (4 bit field)

This field is sent as part of an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst Method – part 2’ or included in a RLC Data Block following the transmission of an EGPRS MULTILATERATION REQUEST message indicating ‘RLC Data Block method’ or ‘Page Response for Positioning Event’. It is coded as described in sub-clause 10.4.32

| +|

Random ID High (12 bit field)

This field is sent as part of an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst Method – part 2’. It consists of the 12 most significant bits of the Random ID parameter provided to the MS in the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031).

The value of the Random ID resulting from combining the Random ID Low and Random ID High fields sent by the MS is selected from the set of the Random ID values provided by the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031). Each Random ID value provided by the RRLP Multilateration Timing Advance Request message can only be used in one cell used during the MTA procedure.

| +|

Short DSS ID (3 bit field)

This field is sent as part of an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst Method – part 2’. It consists of the Short BSS ID parameter provided to the MS in the RRLP Multilateration Timing Advance Request message (see 3GPP TS 44.031).

| +|

Final MTA Access (1 bit field)

This field indicates whether or not the current access request is the final access request the MS will make when performing the radio access part of the MTA procedure. It is ignored by the BSS if the Access Discriminator field indicates ‘Page Response for a positioning event’.

bit

0      One or more additional access requests pending for MTA procedure

1      Final access request for MTA procedure

| + +#### 11.2.5b Packet DBPSCH Assignment + +This message is sent on the PCCH or the PACCH from the network to the mobile station in *lu mode* to assign one or more DBPSCH(s) or a SDCCH to the mobile station. + +Message type: PACKET DBPSCH ASSIGNMENT + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.5b.1: PACKET DBPSCH ASSIGNMENT information elements** + +``` + +< Packet DBPSCH Assignment message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } + { { 0 < Global TFI : < Global TFI IE > > + | 10 < G-RNTI : bit (32) > + | 11 < Packet Request Reference : < Packet Request Reference IE >> } + { 0 -- Message escape + { < CHANNEL_DESCRIPTION : < Channel Description struct >> + { 0 | 1 < TIMING_ADVANCE_VALUE : bit (8) > } + < NETWORK_RESPONSE_TIMES : < Network Response Times struct >> + < padding bits > -- truncation at end of message allowed, bits '0' assumed + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Message escape : 1 bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + + < Channel Description struct > ::= + < CHANNEL_TYPE : bit (6) > + < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > + { 0 -- Symmetric uplink and downlink timeslot allocation + | 1 < UPLINK_TIMESLOT_ALLOCATION : bit (8) > } -- Asymmetric uplink and downlink timeslot allocation + { 0 | 1 < USF : bit (3) > + < USF_GRANULARITY : bit (1) > } + < POWER_COMMAND : < Power Command struct > > + { 0 | 1 < CHANNEL_MODE : bit (8) > } + < TSC : bit (3) > + { 0 < MAIO : bit (6) > + < HSN : bit (6) > + | 1 < ARFCN : bit (10) > } ; + + < Network Response Times struct > ::= + { 0 -- Network's response times on SDCCH + < RESPONSE_TIME_SDCCH : < Response Time SDCCH struct > > + | 1 -- Network's response times on the assigned DBPSCH + < RESPONSE_TIME_SACCH : < Response Time SACCH struct >> -- Network's response time on SACCH + { 0 -- Network's response time on FACCH/F + -- i.e. between a request sent on TCH/F or FACCH/F and the corresponding response sent on FACCH/F + < RESPONSE_TIME_FACCH_F : < Response Time struct >> + | 1 < RESPONSE_TIME_FACCH_H : < Response Time struct >> }; -- Network's response time on FACCH/H + + < Response Time SDCCH struct > ::= + < TRMIN_SDCCH : bit (1) > -- Network's minimum response time on SDCCH + < TRESP_SDCCH : bit (1) > ; -- Network's maximum response time on SDCCH + + < Response Time SACCH struct > ::= + < TRMIN_SACCH : bit (1) > -- Network's minimum response time on SACCH + < TRESP_SACCH : bit (1) > ; -- Network's maximum response time on SACCH + + < Response Time struct > ::= + < TRMIN : bit (6) > + < TRESP_MAC_DTM : bit (7) > + < TRESP_MAC_Dedicated : bit (7) > ; + + < Power Command struct > ::= -- Provides the power level to be used by the mobile station + { 0 -- Normal power control + | 1 < FPC_EPC : bit (1) > } -- Fast or Enhanced Power Control + < POWER_LEVEL : bit (8) > ; + +``` + +**Table 11.2.5b.2: PACKET DBPSCH ASSIGNMENT information elements details** + +| | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|--|-------------|--|-------------|--------------------|-------------|--------------------|-------------|---------------------------|-------------|----------------------------|-------------|-----------------------------|------------------|----------| +| PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20. | | | | | | | | | | | | | | | | | +| PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1...4)
This field is defined in sub-clause 12.14, PRACH Control Parameters. | | | | | | | | | | | | | | | | | +| Global TFI
This information element contains one of the mobile station's downlink or uplink TFIs. This field is defined in sub-clause 12.10. | | | | | | | | | | | | | | | | | +| G-RNTI (32 bit field)
This field is defined in sub-clause 12.16. | | | | | | | | | | | | | | | | | +| Packet_Request_Reference
This information element is defined in sub-clause 12.11 | | | | | | | | | | | | | | | | | +| CHANNEL_TYPE (6 bit field)
This field indicates the type of channel allocated to the mobile station on DBPSCH. The T bits indicate the subchannel number coded in binary. See 3GPP TS 45.002.

bit
6 5 4 3 2 1
0 0 0 0 T T SDCCH/4 + SACCH/C4
0 0 1 T T T SDCCH/8 + SACCH/C8
0 1 0 0 0 0 TCH/F + FACCH/F + SACCH/F
0 1 0 0 1 T TCH/H + FACCH/H + SACCH/TH
0 1 0 1 0 0 PDTCH/F + PACCH/F + SACCH/F
All other values Reserved
| bit | | 6 5 4 3 2 1 | | 0 0 0 0 T T | SDCCH/4 + SACCH/C4 | 0 0 1 T T T | SDCCH/8 + SACCH/C8 | 0 1 0 0 0 0 | TCH/F + FACCH/F + SACCH/F | 0 1 0 0 1 T | TCH/H + FACCH/H + SACCH/TH | 0 1 0 1 0 0 | PDTCH/F + PACCH/F + SACCH/F | All other values | Reserved | +| bit | | | | | | | | | | | | | | | | | +| 6 5 4 3 2 1 | | | | | | | | | | | | | | | | | +| 0 0 0 0 T T | SDCCH/4 + SACCH/C4 | | | | | | | | | | | | | | | | +| 0 0 1 T T T | SDCCH/8 + SACCH/C8 | | | | | | | | | | | | | | | | +| 0 1 0 0 0 0 | TCH/F + FACCH/F + SACCH/F | | | | | | | | | | | | | | | | +| 0 1 0 0 1 T | TCH/H + FACCH/H + SACCH/TH | | | | | | | | | | | | | | | | +| 0 1 0 1 0 0 | PDTCH/F + PACCH/F + SACCH/F | | | | | | | | | | | | | | | | +| All other values | Reserved | | | | | | | | | | | | | | | | +| DOWNLINK_TIMESLOT_ALLOCATION (8 bit field)
This field is coded as the Timeslot Allocation field defined in sub-clause 12.18. The uplink timeslot allocation is identical to the downlink timeslot allocation given in this field in case the UPLINK_TIMESLOT_ALLOCATION field is not included.

NOTE: Multislot allocation is only possible with a CHANNEL_TYPE indicating TCH or PDTCH.

| | | | | | | | | | | | | | | | | +| UPLINK_TIMESLOT_ALLOCATION (8 bit field)
This field is coded as the Timeslot Allocation field defined in sub-clause 12.18. It is included only in case of asymmetric timeslot allocation between downlink and uplink.

NOTE: Multislot allocation is only possible with a CHANNEL_TYPE indicating TCH or PDTCH.

| | | | | | | | | | | | | | | | | +| CHANNEL_MODE (8 bit field)
This field is coded as the mode part of the channel mode IE defined in 3GPP TS 44.018. It shall be included only in case a TCH is assigned to the mobile station. | | | | | | | | | | | | | | | | | +| TSC (3 bit field)
This field is the binary representation of the training sequence code, see 3GPP TS 45.002.

Range: 0 to 7.

| | | | | | | | | | | | | | | | | +| MAIO (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 45.002.

Range: 0 to 63.

| | | | | | | | | | | | | | | | | +| HSN (6 bit field)
This field is the binary representation of the hopping sequence number, see 3GPP TS 45.002.

Range: 0 to 63.

| | | | | | | | | | | | | | | | | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| ARFCN (10 bit field)
This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS 45.005.

Range 0 to 1023. | | +| TIMING_ADVANCE_VALUE (8 bit field)
This field is defined in 3GPP TS 44.018. | | +| TRMIN_SDCCH (1 bit field)
This field indicates the minimum response time of the network on SDCCH, expressed as a number of TDMA frames.

Bit
1
0 32
1 83 | | +| TRESP_SDCCH (1 bit field)
This field indicates the maximum response time of the network on SDCCH, expressed as a number of TDMA frames.

Bit
1
0 134
1 185 | | +| TRMIN_SACCH (1 bit field)
This field indicates the minimum response time of the network on SACCH, expressed as a number of TDMA frames.

Bit
1
0 25
1 129 | | +| TRESP_SACCH (1 bit field)
This field indicates the maximum response time of the network on SACCH, expressed as a number of TDMA frames.

Bit
1
0 129
1 233 | | +| TRMIN (6 bit field)
This field indicates the minimum response time of the network, expressed as a number of TDMA frames.

Bit
6 5 4 3 2 1
0 0 0 0 0 0 9
0 0 0 0 0 1 10
... ...
1 1 1 1 1 1 72 | | +| TRESP_MAC_DTM (7 bit field)
TRESP_MAC_Dedicated (7 bit field)
These fields indicate for a given MAC state the maximum response time of the network expressed as a number of TDMA frames.

Bit
7 6 5 4 3 2 1
0 0 0 0 0 0 0 14
0 0 0 0 0 0 1 15
... ...
1 1 1 1 1 1 1 141 | | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FPC_EPC (1 bit field)
This field indicates whether fast power control or enhanced power control (see 3GPP TS 45.008) shall be used. It is coded as follows:

Bit
1
0 FPC in use
1 EPC in use | +| POWER_LEVEL (8 bit field)
This field is coded as the binary representation of the "power control level", see 3GPP TS 45.005. This value shall be used by the mobile station according to 3GPP TS 45.008.

Range: 0 to 31 | +| USF (3 bit field)
This field indicates the USF value assigned to the MS for all assigned timeslots (range 0 to 7). This field is encoded as a binary representation of the USF value as defined in sub-clause 10.4.1. | +| USF_GRANULARITY (1 bit field)
This information field indicates the USF granularity to be applied by the mobile station on DBPSCH.

0 the mobile station shall transmit one RLC/MAC block
1 the mobile station shall transmit four consecutive RLC/MAC blocks | + +### 11.2.5c MPRACH Packet Channel Request + +This message is sent in random mode on the MPRACH using the PRACH uplink block format defined in 3GPP TS 44.004. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. + +The message is coded as shown in table 11.2.5c.1. + +**Table 11.2.5c.1: MPRACH PACKET CHANNEL REQUEST message content** + +| | +|------------------------------------------------------------------------------| +| < MPRACH Packet channel request message content > ::= | +| < Single block MBMS access : 0000 < RandomBits : bit (7) > > ; | + +**Table 11.2.5c.2: MPRACH PACKET CHANNEL REQUEST details** + +| | +|------------------------------------------------------------------| +| RandomBits (7 bit field)
This is an unformatted field. | +|------------------------------------------------------------------| + +### 11.2.6 Packet Downlink Ack/Nack + +This message is sent on the PACCH from the mobile station to the network to indicate the status of downlink RLC data blocks received and to report the channel quality of the downlink. The mobile station may optionally initiate an uplink TBF. + +Message type: PACKET DOWNLINK ACK/NACK + +Direction: mobile station to network + +Table 11.2.6.1: PACKET DOWNLINK ACK/NACK information elements + +``` + +< Packet Downlink Ack/Nack message content > ::= + < DOWNLINK_TFI : bit (5) > + < Ack/Nack Description : < Ack/Nack Description IE > > + { 0 | 1 < Channel Request Description : < Channel Request Description IE > > } + < Channel Quality Report : < Channel Quality Report struct > > + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 1999 + { 0 | 1 < PFI : bit(7) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-5 + { 0 | 1 < Iu mode Channel Request Description : < Iu mode Channel Request Description IE > > } + { 0 | 1 < RB Id : bit (5) > } + { 0 | 1 < Timeslot Number : bit (3) > } + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 6 + { 0 | 1 < Extended Channel Request Description : < Extended Channel Request Description IE > > } + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 7 + < EARLY_TBF_ESTABLISHMENT : bit (1) > + < padding bits > } } }; + +< Channel Quality Report struct > ::= + < C_VALUE : bit (6) > + < RXQUAL : bit (3) > + < SIGN_VAR : bit (6) > + { 0 | 1 < I_LEVEL_TN0 : bit (4) > } + { 0 | 1 < I_LEVEL_TN1 : bit (4) > } + { 0 | 1 < I_LEVEL_TN2 : bit (4) > } + { 0 | 1 < I_LEVEL_TN3 : bit (4) > } + { 0 | 1 < I_LEVEL_TN4 : bit (4) > } + { 0 | 1 < I_LEVEL_TN5 : bit (4) > } + { 0 | 1 < I_LEVEL_TN6 : bit (4) > } + { 0 | 1 < I_LEVEL_TN7 : bit (4) > } ; + +``` + +Table 11.2.6.2: PACKET DOWNLINK ACK/NACK information element details + +#### **DOWNLINK\_TFI** (5 bit field) + +This field contains the TFI of the mobile station's downlink TBF. This field is defined in sub-clause 12.15. On DBPSCH, this field equals the radio bearer identity of the radio bearer to which this message applies. + +##### **Ack/Nack Description** + +This information element is defined in sub-clause 12.3. + +#### **Channel Request Description** + +This information element is defined in sub-clause 12.7. If a PFI field is included in this message, it relates to the TBF request contained in the *Channel Request Description* IE. Neither this IE nor the PFI field shall be included if the *Extended Channel Request Description* IE is included. + +##### **Iu mode Channel Request Description** + +This information element is defined in sub-clause 12.7a. + +#### **Extended Channel Request Description** + +This information element is defined in sub-clause 12.7b. This IE contains a request for one or more additional uplink TBFs and shall only be included if the mobile station and the network support multiple TBF procedures. If this IE is included, the *Channel Request Description* IE and PFI field in the message shall be omitted. + +#### **C\_VALUE** (6 bit field) + +This field is encoded as the binary representation of the C value as specified in 3GPP TS 45.008. Range 0 to 63 + +#### **RXQUAL (3 bit field)** + +This field contains the RXQUAL parameter field calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as defined in 3GPP TS 44.018. + +Range 0 to 7 + +#### **PFI (7 bit field)** + +This field contains the PFI parameter identifying a Packet Flow Context relating to the resource request specified in the *Channel Request Description* IE. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. This field may be included if the network supports packet flow context procedures and if a *Channel Request Description* IE is included in the message. If this field is included but the *Channel Request Description* IE is omitted, this field shall be ignored. + +##### **SIGN\_VAR (6 bit field)** + +This field contains the signal variance parameter SIGN\_VAR calculated by the mobile station (see 3GPP TS 45.008). + +bit + +6 5 4 3 2 1 + +0 0 0 0 0 0 0dB2 to 0.25 dB2 + +0 0 0 0 0 1 >0.25 dB2 to 0.50 dB2 + +0 0 0 0 1 0 >0.50 dB2 to 0.75 dB2 + +⋮ ⋮ + +1 1 1 1 1 0 >15.50 dB2 to 15.75 dB2 + +1 1 1 1 1 1 >15.75 dB2 + +##### **I\_LEVEL\_TN0 (4 bit field)** + +#### **I\_LEVEL\_TN1 (4 bit field)** + +#### **I\_LEVEL\_TN2 (4 bit field)** + +#### **I\_LEVEL\_TN3 (4 bit field)** + +#### **I\_LEVEL\_TN4 (4 bit field)** + +#### **I\_LEVEL\_TN5 (4 bit field)** + +#### **I\_LEVEL\_TN6 (4 bit field)** + +#### **I\_LEVEL\_TN7 (4 bit field)** + +These fields contain the I\_LEVEL value measured on timeslots 0 through 7, respectively. The I\_LEVEL is defined in 3GPP TS 45.008 and the coding of I\_LEVEL is as follows: + +bit + +4 3 2 1 + +0 0 0 0 I\_LEVEL 0 + +0 0 0 1 I\_LEVEL 1 + +⋮ + +1 1 1 0 I\_LEVEL 14 + +1 1 1 1 I\_LEVEL 15 + +#### **RB Id (5 bit field)** + +This field contains the radio bearer identity of the mobile station's radio bearer for which the downlink data transfer on SFACCH is acknowledged. This field is not included when the PACKET DOWNLINK ACK/NACK message is sent on DBPSCH. This field is encoded as a binary number with range 0-31 + +#### **Timeslot Number (3 bit field)** + +It contains the timeslot number of the timeslot on which the corresponding RRBP was received. This field shall be included if and only if the timeslot number of the PDTCH/SBPSCH on which the PACKET DOWNLINK ACK/NACK message is sent is different from the timeslot number of each of the timeslots assigned to this TBF in the direction of this TBF. This field is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +#### **EARLY\_TBF\_ESTABLISHMENT (1 bit field)** + +This field indicates whether or not the channel request is meant to request pre-allocation of an uplink TBF: + +- 0 The channel request is not meant to pre-allocate an uplink TBF. +- 1 The channel request is meant to pre-allocate an uplink TBF. + +### 11.2.6a EGPRS Packet Downlink Ack/Nack + +This message is sent on the PACCH from the mobile station to the network to indicate the status of downlink RLC data blocks received and to report the channel quality of the downlink. The mobile station may optionally initiate an uplink TBF or request a temporary suspension of the downlink TBF. + +Message type: EGPRS Packet Downlink Ack/Nack + +Direction: mobile station to network + +**Table 11.2.6a.1 : EGPRS PACKET DOWNLINK ACK/NACK information elements** + +``` +< EGPRS Packet Downlink Ack/Nack message content > ::= + < DOWNLINK_TFI : bit (5) > + < MS OUT OF MEMORY : bit(1) > + { 0 | 1 < EGPRS Channel Quality Report : < EGPRS Channel Quality Report IE > > } + { 0 | 1 < Channel Request Description : > Channel Request Description IE > > } + { 0 | 1 < PFI : bit(7) > } + { 0 | 1 < EPD A/N Extension length index : bit (6) > + < bit (expanded_EPDAN_extension_length(val(EPD A/N Extension length index))) + & { < EPD A/N Extension Info > ! { bit** = } } > } + < EGPRS Ack/Nack Description : < EGPRS Ack/Nack Description IE >> + ; +< EPD A/N Extension Info > ::= + {{ + -- Rel-5 extension + { 0 | 1 < Iu mode Channel Request Description : < Iu mode Channel Request Description IE > > } + { 0 | 1 < RB Id : bit (5) > } + { 0 | 1 < Timeslot Number : bit (3) > } + } + { + -- Rel-6 extension + { 0 | 1 < Extended Channel Request Description : < Extended Channel Request Description IE > > } + } + { + -- Rel-7 extension + < EARLY_TBF_ESTABLISHMENT : bit (1) > + { 0 | 1 < Secondary Dual Carrier Channel Report : < EGPRS Channel Quality Report IE > } + } + < spare bit** > } // ; + -- Truncation may occur between released versions of the protocol + -- The receiver shall assume the value zero of any truncated bits +``` + +**Table 11.2.6a.1a : expanded\_EPDAN\_extension\_length function** + +``` +/* + * The expanded_EPDAN_extension_length function returns the actual length of + * the EPD A/N Extension Info IE computed as follows: + * - if index_value >= 6 or the mobile station is NOT assigned a dual carrier + * configuration, the length is index_value + 1 (for sizes ranging from 1 to 64 bits) + * - if index_value < 6 and the mobile station is assigned a dual carrier configuration, + * the length is index_value + 65 (for "expanded" sizes ranging from 65 to 70 bits) + * + * The description of the function in ANSI C language is provided herein for illustration. + * + * Parameter: + * index: index ranging from 0 to 63 and representative of the actual IE size + * + * Returned value: actual (expanded) size of the IE + */ + +unsigned char expanded_EPDAN_extension_length (unsigned char index) +{ + /* Indicates whether the mobile station is assigned a DLDC configuration (1) or not (0) */ + extern unsigned char DLDC_configuration; + + unsigned char L; + + if ((index >= 6) OR (DLDC_configuration == 0)) + L = index + 1; + else + L = index + 65; + + return (L); +} +``` + +**Table 11.2.6a.2: EGPRS PACKET DOWNLINK ACK/NACK information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DOWNLINK_TFI (5 bit field)
This field contains the TFI of the mobile station's downlink TBF. This field is defined in sub-clause 12.15. On DBPSCH, this field equals the radio bearer identity of the radio bearer to which this message applies. | +| EGPRS Ack/Nack Description IE (L bit field)
This information element is defined in sub-clause 12.3.1. The number of bits (L) available for Ack/Nack Description information element depends on the inclusion of channel quality reports and channel requests. L shall be set so that the entire EGPRS PACKET DOWNLINK ACK/NACK message evenly fits into an RLC/MAC control block. If a lower L covers the entire receive window, that L shall be used. | +| MS OUT OF MEMORY (1 bit field)
This field indicates that the MS has no more enough memory to perform Incremental Redundancy.

0 The MS has enough memory
1 The MS is running out of memory | +| Channel Request Description IE
This information element is defined in sub-clause 12.7. If a PFI field is included in this message, it relates to the TBF request contained in the Channel Request Description IE . Neither this IE nor the PFI field shall be included if the Extended Channel Request Description IE is included.

Iu mode Channel Request Description IE
This information element is defined in sub-clause 12.7a.

Extended Channel Request Description
This information element is defined in sub-clause 12.7b. This IE contains a request for one or more additional uplink TBFs and shall only be included if the mobile station and the network support multiple TBF procedures. If this IE is included, the Channel Request Description IE and PFI field in the message shall be omitted.

EGPRS Channel Quality Report IE
This information element is defined in sub-clause 12.5.1. For a mobile station with a dual carrier downlink assignment, this IE shall contain measurements corresponding to the downlink carrier which is paired with the uplink carrier on which this message is being sent. | +| PFI (7 bit field)
This field contains the PFI parameter identifying a Packet Flow Context relating to the resource request specified in the Channel Request Description IE. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. This field may be included if the network supports packet flow context procedures and if a Channel Request Description IE is included in the message. If this field is included but the Channel Request Description IE is omitted, this field shall be ignored. | +| RB Id (5 bit field)
This field contains the radio bearer identity of the mobile station's radio bearer for which the downlink data transfer on SFACCH is acknowledged. This field is not included when the EGPRS PACKET DOWNLINK ACK/NACK message is sent on DBPSCH. This field is encoded as a binary number with range 0-31. | +| Timeslot Number (3 bit field)
It contains the timeslot number of the timeslot on which the corresponding RRBP was received. This field shall be included if and only if the timeslot number of the PDTCH/SBPSCH on which the EGPRS PACKET DOWNLINK ACK/NACK message is sent is different from the timeslot number of each of the timeslots assigned to this TBF in the direction of this TBF. This field is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. | +| EARLY_TBF_ESTABLISHMENT (1 bit field)
This field indicates whether or not the channel request is meant to request pre-allocation of an uplink TBF:

0 The channel request is not meant to pre-allocate an uplink TBF.
1 The channel request is meant to pre-allocate an uplink TBF. | + +#### **Secondary Dual Carrier Channel Report** + +This information element is described in sub-clause 12.5.1. For a mobile station with a dual carrier downlink assignment, this IE shall contain measurements corresponding to the downlink carrier which is not paired with the uplink carrier on which this message is being sent. This IE shall not be included by an MS with a single carrier downlink assignment. + +### **11.2.6b Packet DBPSCH Downlink Ack/Nack** + +This message is sent on FACCH, SACCH or SDCCH from the mobile station to the network to indicate the status of downlink RLC data blocks received. + +Message type: PACKET DBPSCH DOWNLINK ACK/NACK + +Direction: mobile station to network + +**Table 11.2.6b.1: PACKET DBPSCH DOWNLINK ACK/NACK information elements** + +``` +< Packet DBPSCH Downlink Ack/Nack message > ::= + < MESSAGE_TYPE : bit (6) == 000010 > + < RB Id : bit (5) > + { 0 -- TCH TBF mode + { 0 - All data blocks acknowledged, no retransmission requested + | 1 < STARTING_SEQUENCE_NUMBER : bit (8) > + < RECEIVED_BLOCK_BITMAP : bit (128) > } + | 1 -- DCCH TBF mode + { 0 - All data blocks acknowledged, no retransmission requested + | 1 < STARTING_SEQUENCE_NUMBER : bit (4) > + < RECEIVED_BLOCK_BITMAP : bit (8) > } } +``` + + ; + +**Table 11.2.6b.2: PACKET DBPSCH DOWNLINK ACK/NACK information element details** + +#### **RB Id (5 bit field)** + +This field contains the radio bearer identity of the mobile station's radio bearer for which the downlink data transfer is acknowledged. This field is encoded as a binary number with range 0-31. + +#### **STARTING\_SEQUENCE\_NUMBER (8 or 4 bit field)** + +The SSN contains the value of V(R) when this information element was transmitted. This field is encoded as the binary representation of V(R). + +Range 0 to 255 (8 bit field) + +Range 0 to 15 (4 bit field) + +**RECEIVE\_BLOCK\_BITMAP (RBB)** (128 or 8 bit field) + +The RBB is a bitmap representing Block Sequence Numbers. The bitmap is indexed relative to SSN as follows: + +$BSN = (SSN - bit\_number) \text{ modulo } 256$ , for $bit\_number = 1 \text{ to } 128$ (128 bit field). + $BSN = (SSN - bit\_number) \text{ modulo } 16$ , for $bit\_number = 1 \text{ to } 8$ (8 bit field). + +The BSN values represented range: + +from $(SSN - 1) \bmod 256$ to $(SSN - 128) \bmod 256$ (128 bit field) + from $(SSN - 1) \bmod 16$ to $(SSN - 8) \bmod 16$ (8 bit field) + +The value of each bit represents the acknowledgement status of the RLC data block with: + +$BSN = (SSN - bit\_number) \bmod 256$ (128 bit field) + $BSN = (SSN - bit\_number) \bmod 16$ (8 bit field), + +it is encoded as follows: + +- 0 Negative acknowledgement +- 1 Positive acknowledgement + +### 11.2.6c Packet DBPSCH Downlink Ack/Nack Type 2 + +This message shall only be used when FLO is used. It is sent on ADCH from the mobile station to the network to indicate the status of downlink RLC data blocks received. + +Message type: PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 + +Direction: mobile station to network + +**Table 11.2.6c.1: PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 information elements** + +``` + +< Packet DBPSCH Downlink Ack/Nack Type 2 message > ::= + < MESSAGE_TYPE : bit (6) == 000010 > -- The same message type as for Packet DBPSCH Downlink Ack/Nack is + -- used since these two messages are mutually exclusive + < RB Id : bit (5) > + < EGPRS Channel Quality Report : < EGPRS Channel Quality Report IE > > + { 0 -- UDCH TBF mode + { 0 -- All data blocks acknowledged, no retransmission requested + | 1 < FLO Ack/Nack Description : < FLO Ack/Nack Description IE > > } + | 1 -- CDCH TBF mode + { 0 -- All data blocks acknowledged, no retransmission requested + | 1 < STARTING_SEQUENCE_NUMBER : bit (4) > + < RECEIVED_BLOCK_BITMAP : bit (8) > } } + ; + +``` + +**Table 11.2.6c.2: PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RB Id (5 bit field)

This field contains the radio bearer identity of the mobile station's radio bearer for which the downlink data transfer is acknowledged. This field is encoded as a binary number with range 0-31.

| +|

FLO Ack/Nack Description IE (x bit field)

This information element is defined in sub-clause 12.3.2.

| +|

STARTING_SEQUENCE_NUMBER (4 bit field)

The SSN contains the value of V(R) when this information element was transmitted. This field is encoded as the binary representation of V(R).
Range 0 to 15

| + +#### **RECEIVE\_BLOCK\_BITMAP (RBB)** (128 or 8 bit field) + +The RBB is a bitmap representing Block Sequence Numbers. The bitmap is indexed relative to SSN as follows: + +BSN = (SSN - bit\_number) modulo 16, for bit\_number = 1 to 8 (8 bit field). + +The BSN values represented range: + +from (SSN - 1) mod 16 to (SSN - 8) mod 16 (8 bit field) + +The value of each bit represents the acknowledgement status of the RLC data block with: + +BSN = (SSN - bit\_number) mod 16 (8 bit field), + +it is encoded as follows: + +- 0 Negative acknowledgement +- 1 Positive acknowledgement + +### 11.2.6d MBMS Downlink Ack/Nack + +This message is sent on the PACCH from the mobile station to the network to indicate the status of downlink RLC data blocks received, to report neighbouring cell measurements and to notify the network of the release of the MS\_ID on the mobile station side. + +Message type: MBMS Downlink Ack/Nack + +Direction: mobile station to network + +**Table 11.2.6d.1: MBMS DOWNLINK ACK/NACK information elements** + +``` +< MBMS Downlink Ack/Nack message content > ::= + < DOWNLINK_TFI : bit (5) > + < MBMS Neighbouring Cell Report : < MBMS Neighbouring Cell Report struct > > -- Neighbouring cell reporting + < MS_ID Release Indication : bit (1) > + { 0 | 1 < Extension Bits : Extension Bits IE > } -- sub-clause 12.26 + { 0 < Ack/Nack Description : < Ack/Nack Description IE > > -- Ack/Nack information + | 1 < MS_OUT_OF_MEMORY : bit (1) > + < EGPRS Ack/Nack Description : < EGPRS Ack/Nack Description IE > > } + ; + +< MBMS Neighbouring Cell Report struct > ::= + { 0 < BA_USED : bit (1) > + | 1 < PSI3_CHANGE_MARK : bit (2) > } + < Neighbouring Cell Report : < Neighbouring Cell Report struct > > ; + +< Neighbouring Cell Report struct > ::= + < RXLEV_SERVING_CELL : bit (6) > -- Serving cell Rx level + < RESEL_CRITERIA_FULFILLED : bit (1) > -- If re-selection criteria are fulfilled, only the + -- corresponding neighbouring cell is reported + < NUMBER_OF_NEIGHBOURING_CELL_MEASUREMENTS : bit (3) > + { < NCELL_LIST_INDEX_N : bit (7) > -- Neighbouring cells Rx levels + { 0 | 1 < BSIC_N : bit (6) > } + < RXLEV_N : bit (6) > + < RESEL_PARAMS_ACQUIRED : bit (1) > + { 0 -- No ptm parameters acquired for that session + -- in that cell + | 1 < MBMS_PTM_CHANGE_MARK : bit (2) > } -- Ptm parameters acquired for that session in + -- that cell + } * val (NUMBER_OF_NEIGHBOURING_CELL_MEASUREMENTS) ; +``` + +**Table 11.2.6d.2: MBMS DOWNLINK ACK/NACK information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DOWNLINK_TFI (5 bit field)
This field contains the TFI identifying the mobile station sending this message (i.e. the concatenation of the MBMS Bearer ID and the MS_ID). | +| MS_ID Release Indication (1 bit field)
This field is used by the mobile station to notify the network of the release of the MS_ID, for the MBMS radio bearer the message relates to, on the mobile station side.

0 The MS_ID is not released on the mobile station side
1 The MS_ID is released on the mobile station side | +| Extension Bits
This information element, if present, shall be skipped over. Any information content shall be ignored by the network. This information element is defined in sub-clause 12.26. | +| Ack/Nack Description IE
This information element is defined in sub-clause 12.3. | +| MS OUT OF MEMORY (1 bit field)
This field indicates that the MS has no more enough memory to perform Incremental Redundancy.

0 The MS has enough memory
1 The MS is running out of memory | +| EGPRS Ack/Nack Description IE (L bit field)
This information element is defined in sub-clause 12.3.1. The number of bits (L) available for Ack/Nack Description information element may depend on the number of neighbouring cell measurements included (see sub-clause 9.1.8.2.1). L shall be set so that the entire MBMS DOWNLINK ACK/NACK message evenly fits into an RLC/MAC control block. If a lower L covers the entire receive window, that L shall be used. | +| BA_USED (1 bit field)
PSI3_CHANGE_MARK (2 bit field)
These fields shall contain the value of BA_IND and PSI3_CHANGE_MARK respectively in the message defining the used Neighbour Cell List.

In case PBCCH exists, PSI3_CHANGE_MARK shall be used.
In case PBCCH does not exist, BA_USED shall be used. | +| RXLEV_SERVING_CELL (6 bit field)
This field contains the value of the RXLEV parameter for the serving cell calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as the binary representation of the RXLEV parameter value defined in 3GPP TS 45.008.
Range 0 to 63. | +| Neighbouring cell reporting

The reporting of neighbouring cell measurement results is done in decreasing order of the corresponding cell re-selection ranking, as described in sub-clause 5.6.4. In case cell re-selection criteria are fulfilled, only the measurement results for the corresponding neighbouring cell are included and no other measurement results for any other neighbouring cell are included. | +| RESEL_CRITERIA_FULFILLED (1 bit field)
This field indicates whether cell re-selection criteria are fulfilled.

Bit
0 Cell re-selection criteria are not fulfilled
1. Cell re-selection criteria are fulfilled | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NUMBER_OF_NEIGHBOURING_CELL_MEASUREMENTS (3 bit field)
This field is encoded as the binary representation of the amount of neighbouring cells reported.

Bit
3 2 1
0 0 0 0
... ..
1 0 1 5
1 1 x 6 | +| NCELL_LIST_INDEX_N (7 bit field)
This field contains the index of the GSM Neighbour Cell list, see sub-clause 5.6.3.2. As an exception, if PBCCH is not present in the cell and the MS has not acquired the complete GSM Neighbour Cell list from the BCCH messages, this field shall refer to the BA(BCCH) list. | +| BSIC_N (6 bit field)
This field indicates the BSIC of the frequency upon which the measurement was made. This field shall be included only for frequencies that refer to the BA(BCCH) list. The field is encoded as the BSIC value defined in 3GPP TS 44.018.
Range 0 to 63 | +| RXLEV_N (6 bit field)
This field indicates the measured RXLEV of the frequency upon which the measurement was made (see 3GPP TS 45.008). This field is encoded as the RXLEV value defined in 3GPP TS 44.018.
Range 0 to 63 | +| RESEL_PARAMS_ACQUIRED (1 bit field)
This field indicates whether the mobile station has received the re-selection parameters for the reported neighbouring cell.

Bit
0 No re-selection parameters received for this neighbouring cell
1 Re-selection parameters received for this neighbouring cell | +| MBMS_PTM_CHANGE_MARK (2 bit field)
This field shall contain the value of the MBMS_PTM_CHANGE_MARK field in the latest MBMS NEIGHBOURING CELL INFORMATION message received by the mobile station for that MBMS session and that reported neighbouring cell. If no such MBMS_PTM_CHANGE_MARK is available, it shall not be included in the MBMS DOWNLINK ACK/NACK message. | + +### 11.2.6e EGPRS Packet Downlink Ack/Nack Type 2 + +This message is sent on the PACCH from the mobile station to the network to indicate the status of downlink RLC data blocks received and to report the channel quality of the downlink. The mobile station may optionally initiate an uplink TBF or request a temporary suspension of the downlink TBF. + +Message type: EGPRS Packet Downlink Ack/Nack Type 2 + +Direction: mobile station to network + +**Table 11.2.6e.1 : EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 information elements** + +``` + +< EGPRS Packet Downlink Ack/Nack Type 2 message content > ::= + < DOWNLINK_TFI : bit (5) > + < MS OUT OF MEMORY : bit(1)> + { 0 | 1 < EGPRS Channel Quality Report Type 2 : < EGPRS Channel Quality Report Type 2 IE > > } + { 0 | 1 < Channel Request Description : < Channel Request Description IE > > } + { 0 | 1 < PFI : bit(7) > } + { 0 | 1 < EPD A/N Type 2 Extension length : bit (8) > + < bit (val(EPD A/N Type 2 Extension length) + 1) + & { < EPD A/N Type 2 Extension Info > ! { bit** = } } > } + + -- Truncation of the EGPRS Ack/Nack Description is allowed if the mobile station is assigned a downlink + -- dual carrier configuration and the available space in the message without EGPRS Ack/Nack Description IE + -- does not allow for the inclusion of a valid EGPRS Ack/Nack Description IE, i.e. is less than 16 bits. + -- In the same conditions, the receiver shall assume that no EGPRS Ack/Nack description IE is included. + { < EGPRS Ack/Nack Description : < EGPRS Ack/Nack Description IE >> } // + { + -- Rel-14 extension + { 0 | 1 < MS Transmission Offset : bit (4) > + < MS Sync Accuracy : bit (4) > } + } + } ; +< EPD A/N Type 2 Extension Info > ::= + { 0 | 1 < Extended Channel Request Description : < Extended Channel Request Description IE > > } + < EARLY_TBF_ESTABLISHMENT : bit (1) > + { 0 | 1 < Secondary Dual Carrier Channel Report : < EGPRS Channel Quality Report Type 2 IE > } + < spare bit >** // ; + -- Truncation may occur between released versions of the protocol + -- The receiver shall assume the value zero of any truncated bits + +``` + +**Table 11.2.6e.2: EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 information element details** + +#### **DOWNLINK\_TFI (5 bit field)** + +This field contains the TFI of the mobile station's downlink TBF. This field is defined in sub-clause 12.15. On DBPSCH, this field equals the radio bearer identity of the radio bearer to which this message applies. + +#### **EGPRS Ack/Nack Description IE (L bit field)** + +This information element is defined in sub-clause 12.3.1. The number of bits (L) available for Ack/Nack Description information element depends on the inclusion of channel quality reports and channel requests. L shall be set so that the entire EGPRS PACKET DOWNLINK ACK/NACK message evenly fits into an RLC/MAC control block. If a lower L covers the entire receive window, that L shall be used. + +##### **MS OUT OF MEMORY (1 bit field)** + +This field indicates that the MS has no more enough memory to perform Incremental Redundancy. + +- 0 The MS has enough memory +- 1 The MS is running out of memory + +#### **Channel Request Description IE** + +This information element is defined in sub-clause 12.7. If a PFI field is included in this message, it relates to the TBF request contained in the *Channel Request Description* IE. Neither this IE nor the PFI field shall be included if the *Extended Channel Request Description* IE is included. + +#### **Extended Channel Request Description** + +This information element is defined in sub-clause 12.7b. This IE contains a request for one or more additional uplink TBFs and shall only be included if the mobile station and the network support multiple TBF procedures. If this IE is included, the *Channel Request Description* IE and PFI field in the message shall be omitted. + +#### **EGPRS Channel Quality Report Type 2 IE** + +This information element is defined in sub-clause 12.5a.1. For a mobile station with a dual carrier downlink assignment, this IE shall contain measurements corresponding to the downlink carrier which is paired with the uplink carrier on which this message is being sent. + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PFI (7 bit field)
This field contains the PFI parameter identifying a Packet Flow Context relating to the resource request specified in the Channel Request Description IE. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. This field may be included if the network supports packet flow context procedures and if a Channel Request Description IE is included in the message. If this field is included but the Channel Request Description IE is omitted, this field shall be ignored.

| +|

EARLY_TBF_ESTABLISHMENT (1 bit field)
This field indicates whether or not the channel request is meant to request pre-allocation of an uplink TBF:

0 The channel request is not meant to pre-allocate an uplink TBF.
1 The channel request is meant to pre-allocate an uplink TBF.

| +|

Secondary Dual Carrier Channel Report
This information element is described in sub-clause 12.5a.1. For a mobile station with a dual carrier downlink assignment, this IE shall contain measurements corresponding to the downlink carrier which is not paired with the uplink carrier on which this message is being sent. This IE shall not be included by an MS with a single carrier downlink assignment.

| +|

MS Transmission Offset (4 bit field)
If a downlink TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed then this field is included (8.1.2.2). It is coded as described in sub-clause 10.4.33.

| +|

MS Sync Accuracy (4 bit field)
If a downlink TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed then this field is included (8.1.2.2). It is coded as described in sub-clause 10.4.32.

| + +### 11.2.6f EGPRS Packet Downlink Ack/Nack Type 3 + +This message is sent on the PACCH from the mobile station to the network to indicate the status of downlink RLC data blocks received and to report the channel quality of the downlink. + +This message shall only be used by the mobile station if indicated as supported by the network according to the value of the *EGPRS Packet Downlink Ack/Nack Type 3 Support* field in assignment messages. + +Message type: EGPRS Packet Downlink Ack/Nack Type 3 + +Direction: mobile station to network + +**Table 11.2.6f.1: EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < EGPRS Packet Downlink Ack/Nack Type 3 message content > ::=    < DOWNLINK_TFI : bit (5) >   < MS OUT OF MEMORY : bit(1)>   { 0   1 < EGPRS Channel Quality Report : < EGPRS Channel Quality Report Type 2 IE > > }   { 0   1 < Secondary Dual Carrier Channel Report : < EGPRS Channel Quality Report Type 2 IE > > }   {     { 0   1 < Extension Bits : Extension Bits IE > }      -- sub-clause 12.26      -- Truncation of the EGPRS Ack/Nack Description is allowed     -- if the available space in the message without EGPRS Ack/Nack Description IE     -- does not allow for the inclusion of a valid EGPRS Ack/Nack Description IE, i.e. is less than 16 bits.     -- In these conditions, the receiver shall assume that no EGPRS Ack/Nack description IE is included.     < EGPRS Ack/Nack Description : < EGPRS Ack/Nack Description IE >>   } // -- Truncation allowed (specific conditions apply for the EGPRS Ack/Nack Description - see above)   {     -- Rel-14 extension     { 0   1    < MS Transmission Offset : bit (4) >                < MS Sync Accuracy : bit (4) > }   }   <padding bits> ;
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.6f.2: EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 information element details** + +#### **DOWNLINK\_TFI (5 bit field)** + +This field contains the TFI of the mobile station's downlink TBF. This field is defined in sub-clause 12.15. On DBPSCH, this field equals the radio bearer identity of the radio bearer to which this message applies. + +#### **MS OUT OF MEMORY (1 bit field)** + +This field indicates that the MS has no more enough memory to perform Incremental Redundancy. + +- 0 The MS has enough memory +- 1 The MS is running out of memory + +#### **EGPRS Channel Quality Report** + +This information element is defined in sub-clause 12.5a.1. For a mobile station with a dual carrier downlink assignment, this IE shall contain measurements corresponding to the downlink carrier which is paired with the uplink carrier on which this message is being sent. + +#### **Secondary Dual Carrier Channel Report** + +This information element is described in sub-clause 12.5a.1. For a mobile station with a dual carrier downlink assignment, this IE shall contain measurements corresponding to the downlink carrier which is not paired with the uplink carrier on which this message is being sent. This IE shall only be included by an MS in a Downlink Dual Carrier configuration. + +#### **EGPRS Ack/Nack Description (L bit field)** + +This information element is defined in sub-clause 12.3.1. The number of bits (L) available for Ack/Nack Description information element depends on the inclusion of channel quality reports and channel requests. L shall be set so that the entire EGPRS PACKET DOWNLINK ACK/NACK message fits into an RLC/MAC control block. If a lower L covers the entire receive window, that L shall be used. + +#### **MS Transmission Offset (4 bit field)** + +If a downlink TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed then this field is included (see sub-clause 8.1.2.2). It is coded as described in sub-clause 10.4.33. + +#### **MS Sync Accuracy (4 bit field)** + +If a downlink TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed then this field is included (see sub-clause 8.1.2.2). It is coded as described in sub-clause 10.4.32. + +### 11.2.7 Packet Downlink Assignment + +This message is sent on the PCCCH or PACCH by the network to the mobile station to assign downlink resources to the mobile station. If the mobile station supports Downlink Dual Carrier or Downlink Multi Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a). + +A mobile allocation or reference frequency list received as part of this assignment message shall be valid until a new assignment is received or each TBF of the MS are terminated. + +- Message type: PACKET DOWNLINK ASSIGNMENT +- Direction: network to mobile station +- Classification: non-distribution message + +**Table 11.2.7.1: PACKET DOWNLINK ASSIGNMENT information elements** + +``` + +< Packet Downlink Assignment message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } + { { 0 < Global TFI : < Global TFI IE > > + | 10 < TLLI / G-RNTI : bit (32) > } + { 0 -- Message escape + { < MAC_MODE : bit (2) > + < RLC_MODE : bit (1) > + < CONTROL_ACK : bit (1) > + < TIMESLOT_ALLOCATION : bit (8) > + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < P0 : bit (4) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < PR_MODE : bit (1) > } + { { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > } + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 1999 + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < COMPACT reduced MA : < COMPACT reduced MA IE > > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-5 + { 0 | 1 < RB Id : bit (5) > + { 0 | 1 < G-RNTI extension : bit (4) > } + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + { 0 | 1 < HFN_LSB : bit (1) > } } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-6 + { 0 | 1 < PFI : bit (7) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-7 + { 0 | 1 < NPM Transfer Time : bit (5) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-9 + < Indication of Upper Layer PDU Start for RLC UM : bit > + { 0 + | 1 < RLC Entity 2 : < RLC Entity Struct > > -- EMST is used + { 0 + | 1 < RLC Entity 3 : < RLC Entity Struct > > } + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-14 + { 0 | 1 < Multilateration Information Request : bit (1) > } } + < padding bits > } } } } } } } } // -- truncation at end of message allowed, bits '0' assumed +! < Non-distribution part error : bit (*) = < no string > > } + +``` + +``` + +| 1 -- message escape for dual carrier, multi carrier, RTTI, BTI with FANR activated, EGPRS2 + { 00 -- downlink dual carrier, RTTI, BTI with FANR activated, EGPRS2 + { < RLC_MODE : bit (1) > + < CONTROL_ACK : bit (1) > + < Assignment Info : < Assignment Info struct > > + { 0 -- BTI mode + < TIMESLOT_ALLOCATION_C1 : bit (8) > + { 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } + | 1 -- RTTI mode + { 0 -- Single Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > + | 1 -- Dual Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > + } + } + } + < Packet Timing Advance : < Packet Timing Advance IE > > + { 00 -- No frequency parameters included + | 01 -- Legacy IEs used + { 0 | 1 < Frequency Parameters C1 : < Frequency Parameters IE > > } + { 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE > > } + | 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE > > + ! < Frequency Parameters error: { 1 1 } bit(*) = < no string> > -- reserved for future used + { 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit (1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit (1) > } } + { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 | 1 < Power Control Parameters C1 : < Power Control Parameters IE > > } + { 0 | 1 < Power Control Parameters C2 : < Power Control Parameters IE > > } + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < PFI : bit (7) > } + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates Fast Ack/Nack Reporting is activated + < EVENT_BASED_FANR : bit (1) > } + < Downlink EGPRS Level : < EGPRS Level IE > > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + +``` + +``` + +| 1 -- Additions for REL-9 + < Indication of Upper Layer PDU Start for RLC UM: bit > + { 0 + | 1 < RLC Entity 2 : < RLC Entity Struct > > -- EMST is used + { 0 + | 1 < RLC Entity 3 : < RLC Entity Struct > > } + } + { 0 | 1 < MTTI_DOWNLINK_ASSIGNMENT_C1 : bit (1) > } + { 0 | 1 < MTTI_DOWNLINK_ASSIGNMENT_C2 : bit (1) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-11 + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + < padding bits > } } } } // -- truncation at end of message allowed, bits '0' assumed +! < Non-distribution part error : bit (*) = < no string > > } +| 01 -- downlink multi carrier, RTTI, BTTI with FANR activated, EGPRS2 + { + < RLC_MODE : bit (1) > + < CONTROL_ACK : bit (1) > + { 1 < UFPS : < UFPS struct > > } ** 0 + < DLMC Measurement Type : bit (1) > + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < Carrier for Interference Measurements : bit (4) > } + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < PTCCH_CARRIER : bit (4) > } + < PDAN Coding : bit (1) > + < Extended SNS : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + { 0 | 1 < PFI : bit (7) > } + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates Fast Ack/Nack Reporting is activated + < EVENT_BASED_FANR: bit (1) > } + < Downlink EGPRS Level: < EGPRS Level IE > > + < Indication of Upper Layer PDU Start for RLC UM : bit > + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + < padding bits > // -- truncation at end of message allowed, bits '0' assumed + ! < Non-distribution part error : bit (*) = < no string > > + } +! < Message escape : { 10 | 11 } bit (*) = < no string > > } +} +! < Address information part error : bit (*) = < no string > > } +! < Distribution part error : bit (*) = < no string > > ; + +``` + +< Assignment Info struct > ::= +   < Assignment Type : bit (2) > +   < Carrier ID : bit (1) > ; + +< RLC Entity Struct > ::= +   < DOWNLINK\_TFI\_ASSIGNMENT : bit (5) > +   < RLC\_MODE : bit (1) > +   { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } +   < PFI : bit (7) > ; + +< Additional PFCs struct > ::= +   < DOWNLINK\_TFI\_ASSIGNMENT : bit (5) > +   { 0 | 1 < NPM Transfer Time : bit (5) > } +   < PFI : bit (7) > ; + +``` + +< UFPS struct > ::= + { 00 -- Existing UFPS released + | 01 -- Existing UFPS remains unchanged (no information provided) + | 10 -- Existing UFPS changed/new UFPS provided + | 0 -- Existing DLMC Frequency Parameters unchanged + | 1 < DLMC Frequency Parameters : < DLMC Frequency Parameters IE > > } + | 1 < CARRIER_SPECIFIC_INFO : < Carrier Specific Info struct > > } ** 0 + | 11 bit (*) = < no string > -- Reserved + }; + +< Carrier Specific Info struct > ::= + { 00 -- Existing carrier released + | 01 -- Existing carrier remains unchanged (no information provided) + | 10 -- Existing carrier changed/new carrier provided + | 0 -- BTTL mode + | 0 -- same timeslots as the lowest numbered carrier + | 1 < TIMESLOT_ALLOCATION : bit (8) > } + | 1 -- RTTL mode + | 0 -- same PDCH-pairs as the lowest numbered carrier + | 1 < DOWNLINK_PDCH_PAIRS_DLMC : bit (8) > + | < RTTL_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DLMC : bit (4) > } + } + { 0 | 1 < MAIO : bit (6) > } + { 0 -- same P0 and PR_MODE as the lowest numbered carrier + | 1 < P0 : bit (4) > + | < PR_MODE : bit (1) > } + { 0 -- same DOWNLINK_TFI_ASSIGNMENT as the lowest numbered carrier + | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + | { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } + { 0 -- same Power Control Parameters as the lowest numbered carrier + | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 -- EMST is not used on this carrier + | 1 -- EMST is used on this carrier + | < RLC Entity 2 : < RLC Entity Struct > > + | { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } + | { 0 | 1 < RLC Entity 3 : < RLC Entity Struct > > } + | { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } + { 0 -- EMSR is not used on this carrier + | 1 -- EMSR is used on this carrier + | { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > + | { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } ** 0 + | { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > + | { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } ** 0 + | { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > + | { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } ** 0 + } + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + | < Secondary DL SC Set : bit (1) > + | < Secondary DL TSC Value : bit (3) > } + | 11 bit (*) = < no string > -- Reserved + }; + +``` + +Table 11.2.7.2: PACKET DOWNLINK ASSIGNMENT information element details + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **PERSISTENCE\_LEVEL** (4 bit field for each Radio Priority 1...4) + +This field is defined in sub-clause 12.14, PRACH Control Parameters. + +#### **Global TFI** + +This information element contains the TFI of one of the mobile station's downlink TBFs or uplink TBFs. This field is defined in sub-clause 12.10. + +#### **TLLI/ G-RNTI (32 bit field)** + +This field is defined in sub-clause 12.16. + +#### **MAC\_MODE (2 bit field)** + +This information field was used in an earlier version of the protocol to indicate the medium access method to be used during an uplink TBF. For backward compatibility reasons, if there is an ongoing uplink TBF using the extended dynamic allocation, the network shall set the value of this field to 'extended dynamic allocation'. Otherwise, the value shall be set to 'dynamic allocation'. The mobile station shall ignore this field. + +bit + +2 1 + +0 0 Dynamic Allocation + +0 1 Extended Dynamic Allocation + +1 0 Reserved -- The value '10' was allocated in an earlier version of the protocol and shall not be used. + +1 1 Reserved -- The value '11' was allocated in an earlier version of the protocol and shall not be used. + +#### **RLC\_MODE (1 bit field)** + +This field indicates the RLC mode of the requested TBF. If EMST is used, this field indicates the RLC mode of the RLC entity.. + +0 RLC acknowledged mode + +1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2). + +#### **CONTROL\_ACK (1 bit field)** + +In *A/Gb mode*, this field shall be set to '1' if the network establishes a new downlink TBF for the mobile station whose timer T3192 is running. Otherwise this field shall be set to '0'. + +In *Iu mode*, this field shall be set to '1' if the network wishes to instruct the mobile station to release a given TBF for which timer T3192 is running. The TBF to be released is identified by the TFI given in the DOWNLINK\_TFI\_ASSIGNMENT field and has to be valid on the PACCH on which this message was sent. Otherwise this field shall be set to '0'. + +#### **TIMESLOT\_ALLOCATION (8 bit field)** + +This field is defined in sub-clause 12.18. + +#### **TIMESLOT\_ALLOCATION\_C1, TIMESLOT\_ALLOCATION\_C2 (8 bit field)** + +These information fields indicate the timeslots assigned for use during the TBF. If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then TIMESLOT\_ALLOCATION\_C1 shall apply to the carrier indicated by the Carrier ID field. Otherwise, TIMESLOT\_ALLOCATION\_C1 and TIMESLOT\_ALLOCATION\_C2 shall apply on carrier 1 and carrier 2 respectively of a dual carrier configuration. These fields are defined in sub-clause 12.18. + +If TIMESLOT\_ALLOCATION\_C1 is present and TIMESLOT\_ALLOCATION\_C2 is not present and the Assignment Type field indicates 'Dual Carrier assignment', then the timeslots specified in TIMESLOT\_ALLOCATION\_C1 apply also to carrier 2. + +For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the TIMESLOT\_ALLOCATION IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the TIMESLOT\_ALLOCATION IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply. + +#### **Packet Timing Advance** + +This information element is defined in sub-clause 12.12. + +#### **P0, P0\_C1, P0\_C2 (4 bit field)** + +For description and encoding, see the Packet Uplink Assignment message. If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then P0\_C1 shall apply to the carrier indicated by the Carrier ID field. Otherwise, P0\_C1 and P0\_C2 shall apply to carrier 1 and carrier 2 respectively. If the P0\_C1 IE is present but the P0\_C2 IE is absent and the Assignment Type field indicates 'Dual Carrier assignment', then the P0\_C1 IE shall apply also to carrier 2. + +For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the P0 IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the P0 IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply. + +#### **PR\_MODE, PR\_MODE\_C1, PR\_MODE\_C2 (1 bit field)** + +For description and encoding, see the Packet Uplink Assignment message. If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then PR\_MODE\_C1 shall apply to the carrier specified in the Carrier ID field. Otherwise, PR\_MODE\_C1 and PR\_MODE\_C2 shall apply to carrier 1 and carrier 2 respectively. If the Assignment Type field indicates 'Dual Carrier assignment' and the PR\_MODE\_C1 IE is present but the PR\_MODE\_C2 IE is absent, then the PR\_MODE\_C1 IE shall apply also to carrier 2. + +For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the PR\_MODE IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the PR\_MODE IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply. + +#### **Power Control Parameters, Power Control Parameters C1, Power Control Parameters C2** + +These information elements are coded as defined in sub-clause 12.13. + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then the Power Control Parameters C1 IE shall apply to the carrier specified in the Carrier ID field. If, in this case, the Power Control Parameters C1 IE is absent, then the previous parameters for that carrier shall apply. + +If the Assignment Type field is included and indicates 'Dual Carrier assignment' and the Power Control Parameters C1 IE is present but the Power Control Parameters C2 IE is absent, then the Power Control Parameters C1 IE shall apply also to carrier 2. Otherwise, if either Power Control Parameters C1 IE or Power Control Parameters C2 IE is absent, the previous parameters for the respective carrier(s) shall apply. + +For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the Power Control Parameters IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the Power Control Parameters IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply. + +#### **Frequency Parameters** + +This information element is defined in sub-clause 12.8. + +##### **Frequency Parameters C1, Frequency Parameters C2** + +These information elements are coded as defined in sub-clause 12.8. + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then Frequency Parameters C1 (if present) shall apply to the carrier specified in the Carrier ID field. + +If the Assignment Type field is included and indicates 'Dual Carrier assignment', Frequency Parameters C1 and Frequency Parameters C2 (if present) assign frequency parameters for carrier 1 and carrier 2, respectively. + +##### **Dual Carrier Frequency Parameters** + +This information element is defined in sub-clause 12.8.2. + +#### **DOWNLINK\_TFI\_ASSIGNMENT** (5 bit field) + +This information element, if present, assigns the TFI to the mobile station to identify the downlink TBF described by this message. TFI is encoded as defined in sub-clause 12.15. If EMST is used, each TFI identifies an RLC entity allocated on the downlink TBF. If EMSR is supported, each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the downlink TBF. + +If a DLMC configuration is established, the assignment message shall provide the DOWNLINK\_TFI\_ASSIGNMENT IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the DOWNLINK\_TFI\_ASSIGNMENT IE for the first carrier in the first UFPS shall apply. + +##### **TBF Starting Time** + +The TBF Starting Time field contains a starting time that indicates the TDMA frame number during which the assigned TBF may start. If no downlink TBF is in progress, the mobile station need not monitor the TFI field of downlink RLC data blocks until the indicated TDMA frame number. After the indicated TDMA frame number, the mobile station shall operate as during a downlink TBF. If a downlink TBF is already in progress, the mobile station shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to use the new parameters assigned. This information element is defined in sub-clause 12.21. + +##### **EGPRS Window Size** + +This information element is defined in sub-clause 12.5.2. + +#### **LINK\_QUALITY\_MEASUREMENT\_MODE** (2 bit field) + +This field determines the measurements to be included within the EGPRS Timeslot Link Quality Measurements IE or EGPRS Timeslot Link Quality Measurements Type 2 IE. In case the assignment results in a dual carrier configuration, the value of the LINK\_QUALITY\_MEASUREMENT\_MODE field shall apply to both carriers. In case the assignment results in a DLMC configuration, the value of the LINK\_QUALITY\_MEASUREMENT\_MODE field shall apply to all carriers. + +bit + +2 1 + +0 0 The mobile station shall not report either interference measurements ( $\gamma$ values) or per slot (slot pair in RTTI configuration) mean BEP measurements. + +0 1 The mobile station shall report available interference measurements ( $\gamma$ values) for timeslots 0 through 7. The $\gamma$ value is defined in 3GPP TS 45.008. No per slot (slot pair in RTTI configuration) mean BEP measurements shall be reported. + +For a mobile station in a DLMC configuration, available interference measurements shall be reported for timeslots 0 through 7 for the carrier indicated by the assignment message or the lowest numbered downlink carrier if carrier information for interference measurements is not provided by the assignment message (see sub-clause 12.66 for additional reporting rules). + +1 0 The mobile station shall report the mean BEP on each assigned time slot (slot pair in RTTI configuration) as specified in 3GPP TS 45.008. No interference measurements ( $\gamma$ values) shall be reported. For a mobile station in a DLMC configuration where measurement information is to be reported on a per carrier basis (see sub-clause 11.2.7), the mean BEP (as specified in 3GPP TS 45.008) shall only be reported for the assigned timeslots on the carrier on which it was polled (see sub-clause 12.66). A mobile station in a DLMC configuration where measurement information is to be reported on a per UFPS basis (see sub-clause 9.1.8.2.1) shall treat this code point as the '00' code point. + +1 1 The mobile station shall report the mean BEP on each assigned time slot (slot pair in RTTI configuration) as specified in 3GPP TS 45.008. In addition to mean BEP, the mobile station shall report interference measurements ( $\gamma$ values) for no more than four time slots for a given carrier within a single reporting message instance. If the MS has interference measurements for more than four timeslots to report for a given carrier, the selection of timeslots for which interference measurements are included in each message instance is implementation specific, subject to the requirement that a measurement for each time slot on each carrier, unless not available (see 3GPP TS 45.008), is included in at least every other report. + +For a mobile station in a DLMC configuration, available interference measurements shall be reported for timeslots 0 through 7 for the carrier indicated by the assignment message or the lowest numbered downlink carrier if carrier information for interference measurements is not provided by the assignment message (see sub-clause 12.66 for additional reporting rules). If measurement information is to be reported on a per carrier basis (see sub-clause 11.2.7), the mean BEP (as specified in 3GPP TS 45.008) shall only be reported for the assigned timeslots on the carrier on which it was polled (see sub-clause 12.66). A mobile station in a DLMC configuration where measurement information is to be reported on a per UFPS basis (see sub-clause 9.1.8.2.1) shall treat this code point as the '01' code point. + +In addition, for a mobile station assigned a Downlink Dual Carrier configuration, if not all the required interference measurements can be included within a reporting message instance after all the required per slot mean BEP values for both carriers have been included, the mobile station shall include as many interference measurements (if any) as can fit in this message instance. The selection of timeslots for which interference measurements are included in each message instance is implementation specific. See sub-clause 9.1.8.2.1 for how a mobile station in a DLMC configuration can report information for more than one UFPS/carrier. + +#### **Packet Extended Timing Advance** (2 bit field) + +This field is defined in sub-clause 12.12b. + +#### **COMPACT reduced MA** + +This information element is defined in sub-clause 12.29. + +| | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------|-----|-----------|-----|-----------------------------------|-----|-------------------------------------|-----|-------------------------|-----|-------------------------| +|

BEP_PERIOD2 (4 bit field)
This field contains a constant which is used for filtering channel quality measurements in EGPRS. BEP_PERIOD2 when present, or if not, when received in a previous message of the same TBF session, shall be used instead of BEP_PERIOD. For details see 3GPP TS 45.008.
Range: 0 to 15

| | | | | | | | | | | | | +|

RB Id (5 bit field)
This field is included in Iu mode when a TBF is assigned. It contains the radio bearer identifier for the radio bearer using the assigned TBF.

| | | | | | | | | | | | | +|

G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier for contention resolution in Iu-mode.

| | | | | | | | | | | | | +|

Uplink Control Timeslot (3 bit field)
This field contains the timeslot number of the timeslot where the PACCH for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002.

| | | | | | | | | | | | | +|

HFN_LSB (1 bit field)
This field contains the least significant bit of the downlink HFN of the radio bearer for which the TBF is assigned. It is used in Iu mode only.

| | | | | | | | | | | | | +|

PFI (7 bit field)
This field contains the PFI parameter identifying the Packet Flow Context related to the TBF identified in the DOWNLINK_TFI_ASSIGNMENT field. The PFI parameter is encoded as the contents of the PFI information element defined in 3GPP TS 44.018. If EMST is used, this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported, this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity.

| | | | | | | | | | | | | +|

NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode.

| | | | | | | | | | | | | +|

Assignment Type (2 bit field)
This indicates the type of assignment:

bit
2 1
0 0 Assignment on single carrier only
0 1 Modification of existing assignment
1 0 Dual Carrier assignment
1 1 Reserved for future use

If the Assignment Type indicates an Assignment on a single carrier only the resources specified in this message are assigned for this TBF on the carrier identified by the Carrier ID field. If the assignment is sent to a mobile station that does not currently have a dual carrier configuration, the Carrier ID field shall indicate Carrier 1 and all resources specified in the message shall relate to Carrier 1.

If the Assignment Type indicates Modification of an existing assignment resources specified in this message replace any existing allocation for this TBF on the carrier indicated by the Carrier ID field. If this type of assignment is used to place a mobile station which currently has resources assigned on only one carrier in a dual carrier configuration the Carrier ID shall indicate Carrier 2.

If the Assignment Type indicates a Dual Carrier assignment the Carrier ID field shall be ignored by the mobile station.

The meaning of the different types of assignment is specified in sub-clause 8.1.1.1.3.

| bit | | 2 1 | | 0 0 | Assignment on single carrier only | 0 1 | Modification of existing assignment | 1 0 | Dual Carrier assignment | 1 1 | Reserved for future use | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | Assignment on single carrier only | | | | | | | | | | | | +| 0 1 | Modification of existing assignment | | | | | | | | | | | | +| 1 0 | Dual Carrier assignment | | | | | | | | | | | | +| 1 1 | Reserved for future use | | | | | | | | | | | | +|

Carrier ID (1 bit field)
This identifies the carrier to which the description refers.

0 Carrier 1
1 Carrier 2
| 0 | Carrier 1 | 1 | Carrier 2 | | | | | | | | | +| 0 | Carrier 1 | | | | | | | | | | | | +| 1 | Carrier 2 | | | | | | | | | | | | + +#### **EVENT\_BASED\_FANR** (1 bit field) + +This field indicates whether the event-based FANR shall be used for the assigned TBF. This field shall be included if the assignment is for a RTTI or MTI configuration. + +- 0 The MS shall not use event-based FANR +- 1 The MS shall use event-based FANR + +#### **DOWNLINK\_PDCH\_PAIRS\_C1** + +#### **DOWNLINK\_PDCH\_PAIRS\_C2** + +#### **UPLINK\_PDCH\_PAIRS\_C1** + +#### **UPLINK\_PDCH\_PAIRS\_C2** + +#### **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_SC** + +#### **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_DC** + +#### **DOWNLINK\_PDCH\_PAIRS\_DLMC** + +#### **UPLINK\_PDCH\_PAIRS\_DLMC** + +#### **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_DLMC** + +These fields are defined in sub-clause 11.2.31 + +#### **Downlink EGPRS Level** (2 bit field) + +This information element specifies the group of modulation and coding schemes applicable to the TBF. This information element is defined in sub-clause 12.10f. + +#### **Indication of Upper Layer PDU Start for RLC UM** (1 bit field) + +This field indicates whether "Indication of Upper Layer PDU Start for RLC UM" as described in sub-clause 10.4.14a is used for the assigned TBF. It is applicable only when the assigned TBF is operating in RLC unacknowledged mode. + +- 0 "Indication of Upper Layer PDU Start for RLC UM" is not used for the assigned TBF. +- 1 "Indication of Upper Layer PDU Start for RLC UM" is used for the assigned TBF. + +#### **MTTI\_DOWNLINK\_ASSIGNMENT\_C1** (1 bit field) + +#### **MTTI\_DOWNLINK\_ASSIGNMENT\_C2** (1 bit field) + +If either of these fields is present, it indicates that the assigned downlink TBF operates in an MTI configuration. If present, a PDCH is assigned on the respective carrier in addition to any assigned PDCH-pairs. If set to '1' (respectively '0'), the assigned PDCH uses the timeslot immediately adjacent to and lower than (respectively higher than) the lower (respectively higher) timeslot used by the lowest numbered (respectively highest numbered) PDCH-pair assigned on that carrier. If no PDCH-pairs are assigned on one carrier, then the assigned PDCH for that carrier is on the same timeslot as the assigned PDCH on the other carrier, regardless of the value of the field. + +#### **EMSR Additional PFCs 1** + +#### **EMSR Additional PFCs 2** + +#### **EMSR Additional PFCs 3** + +If EMSR is supported one or more of these information elements may be included for allocating multiple PFCs to their corresponding RLC entity: + +- if EMST is not used, **EMSR Additional PFCs 1** corresponds to the single RLC entity of the TBF; **EMSR Additional PFCs 2** and **EMSR Additional PFCs 3**, if present, shall be ignored. +- if EMST is used, **EMSR Additional PFCs 1**, **EMSR Additional PFCs 2** and **EMSR Additional PFCs 3** correspond to the first, the second and the third RLC entity, respectively, assigned to the TBF. **EMSR Additional PFCs 2** corresponds to the RLC entity assigned using the **RLC Entity 2** IE and **EMSR Additional PFCs 3** correspond to the RLC entity assigned using the **RLC Entity 3** IE if these RLC entities have been assigned; **EMSR Additional PFCs 2**, respectively **EMSR Additional PFCs 3**, if present, shall be ignored if the corresponding RLC entity has not been assigned. + +#### **EGPRS Packet Downlink Ack/Nack Type 3 Support** (1 bit field) + +This field indicates whether or not the network supports the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message (see sub-clause 11.2.6f): + +- 0 The network does not support the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message. +- 1 The network supports the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message. + +If this field is not present, the value '0' (EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message not supported) shall be assumed by the mobile station. + +#### **UFPS** + +This information element is used to identify the set of resources corresponding to each UFPS within the set of UFPS assigned for a DLMC configuration. Each UFPS in the set of UFPS is numbered according to the scheme described in sub-clause 8.1.1.1.3. The assignment message allows for releasing an existing UFPS, keeping an existing UFPS unchanged, modifying an existing UFPS or adding a new UFPS. + +For the case where a UFPS is defined by a MA the first frequency indicated for the UFPS (i.e. by the CARRIER\_SPECIFIC\_INFO IE) is that corresponding to highest numbered element of the MA\_BITMAP for which a '1' is indicated, the second frequency indicated is that corresponding to 2nd highest numbered element of the MA\_BITMAP for which a '1' is indicated, and so on where the last frequency indicated is that corresponding to lowest numbered element of the MA\_BITMAP for which a '1' is indicated. See sub-clause 12.10a for a description of the MA\_BITMAP field. + +#### **DLMC Measurement Type** + +This field indicates the type of measurement reporting to be used by a mobile station in a DLMC configuration. + +bit + +- 0 BEP Link Quality is reported on a per UFPS basis using a representative value averaged over all carriers in the reported UFPS (see 3GPP TS 45.008 [15]). +- 1 BEP Link Quality is reported on a per carrier basis. + +#### **Carrier for Interference Measurements (4 bit field)** + +This field indicates the carrier to be used for making interference measurements. If the + +**LINK\_QUALITY\_MEASUREMENT\_MODE** field indicates interference measurements are requested and this field is absent the MS shall make interference measurements using the lowest numbered carrier (see sub-clause 8.1.1.1.3). + +bit + +4 3 2 1 + +0 0 0 0 Use the 1st carrier + +0 0 0 1 Use the 2nd carrier + +0 0 1 0 Use the 3rd carrier + +... + +1 1 1 0 Use the 15th carrier + +1 1 1 1 Use the 16th carrier + +##### **CARRIER\_SPECIFIC\_INFO** + +This information element is used to describe the downlink carriers corresponding to a given UFPS applicable to the downlink TBF assigned for a DLMC configuration (see sub-clause 8.1.1.1.3 for the numbering of downlink carriers in a DLMC configuration). + +#### **DLMC Frequency Parameters** + +This information element provides frequency parameters for a UFPS and is described in sub-clause 12.8.4. For the case where a UFPS is defined by an MA this information element indicates the corresponding mobile allocation and TSC applicable to all carriers in that UFPS. + +##### **MAIO (6 bit field)** + +This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 45.002. Range 0 to 63. + +#### **PTCCH\_CARRIER (4 bit field)** + +This field is included if the continuous timing advance procedure is used and identifies the carrier that serves as the PTCCH carrier. + +#### **PDAN Coding** (1 bit field) + +This information field indicates the channel coding rate to be used when a mobile station in a DLMC configuration sends a Packet Downlink Ack/Nack message and is coded as follows: + +- | | | +|---|-----------------------------| +| 0 | CS-1 channel coding is used | +| 1 | CS-3 channel coding is used | + +#### **DOWNLINK\_eTFI\_ASSIGNMENT** (3 bit field) + +This field, if present, assigns an extended TFI (eTFI) used by a mobile station in a DLMC configuration that along with the TFI uniquely identifies a downlink Temporary Block Flow (TBF) on a given carrier (see sub-clause 5.13). This information element is encoded as defined in sub-clause 12.67. When this field is present, the assignment message shall provide it for at least the first carrier in the corresponding UFPS. If this field is absent for any remaining carriers, the DOWNLINK\_eTFI\_ASSIGNMENT IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply + +##### **Extended SNS** (1 bit field) + +This field indicates whether or not the Extended Sequence Number Space of 8192 shall be used in a DLMC configuration. A mobile station shall ignore this field if the maximum number of downlink timeslots it supports in a DLMC configuration is 20 or less. + +- | | | +|---|--------------------------| +| 0 | Extended SNS is disabled | +| 1 | Extended SNS is enabled | + +#### **Primary TSC Set** (1 bit field) + +If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the TSC set associated with the TSC value provided by the *Frequency Parameters* IE, *Dual Carrier Frequency Parameters* IE or *DLMC Frequency Parameters* IE for use on the assigned downlink PS resources. + +##### **Secondary DL TSC Set** (1 bit field) + +If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the TSC set associated with the *Secondary DL TSC Value* field. + +The Primary TSC Set and Secondary DL TSC Set fields are coded as follows: + +- | | | +|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | TSC set 1 | +| 1 | Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain). | + +#### **Secondary DL TSC Value** (3 bit field) + +If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the secondary TSC value to be used on the assigned downlink PS resources. It is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002. Range: 0 to 7. + +#### **Multilateration Information Request** (1 bit field) + +This field indicates whether or not a MS is to include “MS Transmission Offset” and “MS Sync Accuracy” parameters when sending an EGPRS Packet Downlink Ack/Nack Type 2 message (see sub-clause 11.2.6e) or an EGPRS Packet Downlink Ack/Nack Type 3 message (see sub-clause 11.2.6f) during a downlink TBF. This field can be included when establishing a downlink TBF to deliver a downlink LLC PDU for which the corresponding DL-UNITDATA PDU indicates timing advance information is needed (see 3GPP TS 48.018). This field is coded as follows: + +- | | | +|---|---------------------------------------------------------------------------| +| 0 | Do not include “MS Transmission Offset” and “MS Sync Accuracy” parameters | +| 1 | Include “MS Transmission Offset” and “MS Sync Accuracy” parameters | + +#### **11.2.7.1 Special requirements in dual transfer mode for downlink TBF** + +Special requirements apply when a downlink TBF is assigned to a mobile station in dual transfer mode or a mobile station about to enter dual transfer mode. + +If the mobile station has an RR connection to the network on a half-rate TCH, the network may assign a downlink TBF using the other sub-channel of the same timeslot for a half-rate PDCH (see 3GPP TS 45.002). In this case, the downlink assignment message shall be encoded with a timeslot allocation including the timeslot number for the half-rate TCH and the half-rate PDCH and only that timeslot number. The mobile station shall interpret this allocation as an allocation of a half-rate PDCH. + +### 11.2.7a Multiple TBF Downlink Assignment + +This message is sent on the PACCH by the network to the mobile station to assign multiple downlink resources to the mobile station. If the mobile station supports Downlink Dual Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a). + +A mobile allocation or reference frequency list received as part of this assignment message shall be valid until a new assignment is received or until all of the TBFs belonging to the MS are terminated. + +Message type: MULTIPLE TBF DOWNLINK ASSIGNMENT + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.7a.1: MULTIPLE TBF DOWNLINK ASSIGNMENT information elements** + +``` +< Multiple TBF Downlink Assignment message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } + { { 0 < Global TFI : < Global TFI IE > > + | 10 { < TLLI / G-RNTI : < TLLI / G-RNTI IE > > < G-RNTI extension : bit (4) > } } + { 0 -- Message escape + { < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + { { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > } + { 0 | 1 { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + } + { 0 | 1 < BEP_PERIOD2 : bit(4) > }} + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + } + { 1 < Multiple Downlink TBF Assignment : < Multiple Downlink TBF Assignment struct > > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-7 + { 1 { 0 | 1 < NPM Transfer Time : bit (5) > } ** 0 + < padding bits > }} // -- truncation at end of message allowed, bits '0' assumed + } + ! < Non-distribution part error : bit (*) = < no string > > } +``` + +``` + +| 1 -- Message escape for dual carrier, RTTI, BTTI with FANR activated, EGPRS2 + { 00 { < Packet Timing Advance : < Packet Timing Advance IE > > + < Assignment Info : < Assignment Info struct > > + { 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit (1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit (1) > } } + { 00 -- No frequency parameters included + | 01 -- Legacy IEs used + { 0 | 1 < Frequency Parameters C1 : < Frequency Parameters IE > > } + { 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE > > } + | 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters: < Dual Carrier Frequency Parameters IE > > + ! < Frequency Parameters error: { 11 } bit(*) = < no string> > } -- reserved for future use + { 0 | 1 < Power Control Parameters C1 : < Power Control Parameters IE > > } + { 0 | 1 < Power Control Parameters C2 : < Power Control Parameters IE > > } + { 0 | 1 { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } + { 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } + { 0 | 1 -- BTTI mode + < FANR: bit (1) > + { 1 < BTTI Multiple Downlink Assignment : + < BTTI Multiple Downlink Assignment struct > > } ** 0 + } + { 0 | 1 -- RTTI mode + { 0 -- Single Carrier Assignment + { 00 -- Default PDCH-pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment SC : + < RTTI Multiple Downlink Assignment SC struct > > } ** 0 + | 1 -- Dual Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment DC : + < RTTI Multiple Downlink Assignment DC struct > > } ** 0 + } + } + } + > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + { 1 < Indication of Upper Layer PDU Start for RLC UM : bit > } ** 0 + < padding bits > } // -- truncation at end of message allowed, bits '0' assumed + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Message escape : { 01 | 10 | 11 } bit (*) = < no string >> } +! < Address information part error : bit (*) = < no string > > } +! < Distribution part error : bit (*) = < no string > > ; + +< Multiple Downlink TBF Assignment struct > ::= + < TIMESLOT_ALLOCATION : bit (8) > + { 1 < Downlink TBF assignment : < Downlink TBF assignment struct > > } ** 0 ; + +``` + +``` + +< BTTI Multiple Downlink Assignment struct > ::= + { 0 | 1 < TIMESLOT_ALLOCATION_C1 : bit (8) > } + { 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< RTTI Multiple Downlink Assignment SC struct > ::= + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< RTTI Multiple Downlink Assignment DC struct > ::= + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< Downlink TBF assignment struct > ::= + { 0 < RB Id : bit (5) > + | 1 < PFI : bit (7) > + < RLC_MODE : bit (1) > } + < TFI Assignment : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < HFN_LSB : bit (1) > } ; -- HFN_LSB field used in Iu mode only + +< Downlink TBF assignment 2 struct > ::= + < PFI : bit (7) > + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < EVENT_BASED_FANR : bit (1) > + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } ; + +< Assignment Info struct > ::= + < Assignment Type : bit (2) > + < Carrier ID : bit (1) > ; + +``` + +**Table 11.2.7a.2: MULTIPLE TBF DOWNLINK ASSIGNMENT information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

| +|

PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1...4)
This field is defined in sub-clause 12.14, PRACH Control Parameters.

| +|

Global TFI
This information element identifies one of the mobile station's downlink or uplink TFIs. This field is defined in sub-clause 12.10.

| +|

TLLI / G-RNTI
This information element is defined in sub-clause 12.16.

| +|

G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier for contention resolution in Iu-mode.

| +|

CONTROL_ACK (1 bit field)
This field shall be set to "1" if the network wishes to instruct the mobile station to release the given TBFs for which timer T3192 is running. The TBFs to be released are identified by the TFIs given in the TFI Assignment field and have to be valid on the PACCH on which this message was sent. Otherwise this field shall be set to "0".

| +|

TIMESLOT_ALLOCATION, TIMESLOT_ALLOCATION_C1, TIMESLOT_ALLOCATION_C2 (8 bit field)
These fields describe the timeslot(s) on which all TBFs described in this message are assigned resources.

| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Uplink Control Timeslot, Uplink Control Timeslot C1, Uplink Control Timeslot C2 (3 bit field)
In case of a BTTI configuration, these fields contain the timeslot number of the timeslot where the PACCH/U for the MS is located. In case of an RTTI configuration, these fields contain the timeslot number of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the MS is located. These fields are encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. | +| Packet Timing Advance
This information element is defined in sub-clause 12.12. | +| P0, P0_C1, P0_C2 (4 bit field)
For description and encoding, see the Packet Uplink Assignment message. | +| PR_MODE, PR_MODE_C1, PR_MODE_C2 (1 bit field)
For description and encoding, see the Packet Uplink Assignment message. | +| Power Control Parameters, Power Control Parameters C1, Power Control Parameters C2
This information element is defined in sub-clause 12.13. | +| Frequency Parameters
This information element is defined in sub-clause 12.8. | +| Frequency Parameters C1, Frequency Parameters C2
The usage of these parameters is specified in sub-clause 11.2.7. These information elements are coded as defined in sub-clause 12.8. | +| Dual Carrier Frequency Parameters
This information element is defined in sub-clause 12.8.2. | +| TFI Assignment (5 bit field)
This information element assigns one (or more) TFI(s) to each TBF assigned to the mobile station in this message. This field is repeated for each TBF that is assigned in this message. TFI is encoded as defined in sub-clause 12.15. | +| TBF Starting Time
The TBF Starting Time field contains a starting time that indicates the TDMA frame number during which the assigned TBFs may start. If no downlink TBF is in progress, the mobile station need not monitor the TFI field of downlink RLC data blocks until the indicated TDMA frame number. After the indicated TDMA frame number, the mobile station shall operate as during a downlink TBF. If a downlink TBF is already in progress, the mobile station shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to use the new parameters assigned. This information element is defined in sub-clause 12.21. | +| EGPRS Window Size
This information element is defined in sub-clause 12.5.2. | +| LINK_QUALITY_MEASUREMENT_MODE (2 bit field)
This field is defined in sub-clause 11.2.7. | +| Packet Extended Timing Advance (2 bit field)
This field is defined in sub-clause 12.12b. | +| BEP_PERIOD2 (4 bit field)
This field contains a constant which is used for filtering channel quality measurements in EGPRS. BEP_PERIOD2 when present, or if not, when received in a previous message of the same TBF session, shall be used instead of BEP_PERIOD. For details see 3GPP TS 45.008.
Range: 0 to 15 | +| RB Id (5 bit field)
This field contains the radio bearer identifier for the radio bearer using the assigned TBF. This provides the mapping of TFI to RB Id which is necessary to uniquely identify Iu-mode data flows. | +| PFI (7 bit field)
This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RLC_MODE (1 bit field)
This field indicates the RLC mode of the assigned TBF.

0 RLC acknowledged mode
1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2). | +| HFN_LSB (1 bit field) ( Iu mode only)
This field contains the least significant bit of the downlink HFN of the radio bearer for which the TBF is assigned. | +| NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode

The list of NPM Transfer Time IEs in the Rel-7 additions is ordered as described by the loops in the earlier releases part. | +| Assignment Type (2 bit field)

This field is defined in sub-clause 11.2.7. | +| Carrier ID (1 bit field)
This identifies the carrier to which the description refers.

0 Carrier 1
1 Carrier 2 | +| EVENT_BASED_FANR (1 bit field)
This field indicates whether the event-based FANR shall be used for the assigned TBF:

0 The MS shall not use event-based FANR
1 The MS shall use event-based FANR

This field shall be ignored if FANR is not activated. The list of EVENT_BASED_FANR IEs in the Rel-7 additions is ordered as described by the loops in the earlier releases part. | +| DOWNLINK_PDCH_PAIRS_C1
DOWNLINK_PDCH_PAIRS_C2
UPLINK_PDCH_PAIRS_C1
UPLINK_PDCH_PAIRS_C2
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC

These fields are defined in sub-clause 11.2.31 | +| FANR (1 bit field)
This field indicates whether FANR is activated.

0 FANR is not activated for the assigned TBFs
1 FANR is activated for the assigned TBFs | +| Downlink EGPRS Level (2 bit field)
This field specifies the group of modulation and coding schemes applicable to the TBFs. This information element is defined in sub-clause 12.10f. | +| Indication of Upper Layer PDU Start for RLC UM (1 bit field)
This field is defined in section 11.2.7.

The list of Indication of Upper Layer PDU Start for RLC UM IEs in the Rel-9 additions is ordered as described by the loops in the earlier releases part. | + +### 11.2.8 Packet Downlink Dummy Control Block + +This message is sent on the PCCCH or PACCH by the network to the mobile station as a fill message with either of the optional parameters PAGE\_MODE and PERSISTENCE\_LEVEL or with no content. In *Iu mode*, it is also sent on FACCH, SACCH and SDCCH. + +Message type: PACKET DOWNLINK DUMMY CONTROL BLOCK +Direction: network to mobile station +Classification: distribution message + +**Table 11.2.8.1: PACKET DOWNLINK DUMMY CONTROL BLOCK information elements** + +``` +< Packet Downlink Dummy Control Block message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } + < padding bits > + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.8.2: PACKET DOWNLINK DUMMY CONTROL BLOCK information element details** + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **PERSISTENCE\_LEVEL** (4 bit field for each Radio Priority 1...4) + +This field is defined in sub-clause 12.14, PRACH Control Parameters. + +### 11.2.8b Packet Uplink Dummy Control Block + +This message is sent on the PACCH from the mobile station to the network when the mobile station has no other block to transmit. In *Iu mode*, it is also sent on FACCH, SACCH and SDCCH. + +Message type: PACKET UPLINK DUMMY CONTROL BLOCK +Direction: mobile station to network + +**Table 11.2.8b.1: PACKET UPLINK DUMMY CONTROL BLOCK information elements** + +``` +< Packet Uplink Dummy Control Block message content > ::= + < TLLI / G-RNTI : bit (32) > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + < padding bits > } ; +``` + +**Table 11.2.8b.2: PACKET UPLINK DUMMY CONTROL BLOCK information element details** + +#### **TLLI / G-RNTI** (32 bit field) + +This field contains the TLLI / G-RNTI of the mobile station. This field is encoded as defined in sub-clause 12.16. + +#### **G-RNTI extension** (4 bit field) + +This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in *Iu mode*. + +### 11.2.9 Packet Measurement Report + +This message is sent on the PACCH from the mobile station to the network to report measurement results. The message contains measurement results from the Network Control measurements. For a (3G) multi-RAT mobile station, report on 3G cells may be included. For a (E-UTRAN) multi-RAT mobile station, report on E-UTRAN cells may be included. + +Message type: PACKET MEASUREMENT REPORT +Direction: mobile station to network + +**Table 11.2.9.1: PACKET MEASUREMENT REPORT message content** + +``` + +< Packet Measurement Report message content > ::= + < TLLI / G-RNTI : bit (32) > + { 0 | 1 < PSI5_CHANGE_MARK : bit (2) > } + 0 < NC Measurement Report : < NC Measurement Report struct > > + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release 99 : + { 0 | 1 { 0 < BA_USED : bit > < 3G_BA_USED : bit > | 1 < PSI3_CHANGE_MARK : bit(2) > } + < PMO_USED : bit > } + { 0 | 1 < 3G Measurement Report : < 3G Measurement Report struct > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-8 : + { 0 | 1 < E-UTRAN Measurement Report : < E-UTRAN Measurement Report struct > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-9 : + { 0 | 1 < UTRAN CSG Measurement Report : < UTRAN CSG Measurement Report IE > > } + { 0 | 1 < E-UTRAN CSG Measurement Report : < E-UTRAN CSG Measurement Report IE > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-11 : + { 0 | 1 < SI23_BA_USED : bit > } + < padding bits > } } } } }; + +< NC Measurement Report struct > ::= + < NC_MODE : bit (1) > + < RXLEV_SERVING_CELL : bit (6) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < NUMBER_OF_NC_MEASUREMENTS : bit (3) > + { < FREQUENCY_N : bit (6) > + { 0 | 1 < BSIC_N : bit (6) > } + < RXLEV_N : bit (6) > } * (val(NUMBER_OF_NC_MEASUREMENTS)); + +< 3G Measurement Report struct > ::= + < N_3G : bit (3) > + { < 3G_CELL_LIST_INDEX : bit (7) > + < REPORTING_QUANTITY : bit (6) > } * (val(N_3G + 1 )); + +< E-UTRAN Measurement Report struct > ::= + < N_E-UTRAN : bit (2) > + { < E-UTRAN_FREQUENCY_INDEX : bit (3) > + < CELL_IDENTITY : bit (9) > + < REPORTING_QUANTITY : bit (6) > } * (val(N_E-UTRAN + 1 )); + +``` + +**Table 11.2.9.2: PACKET MEASUREMENT REPORT information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

TLLI / G-RNTI (32 bit field)
This field contains the TLLI / G-RNTI of the mobile station. This field is encoded as defined in sub-clause 12.16.

| +|

PSI5_CHANGE_MARK (2 bit field)
This field shall contain the value of the PSI5_CHANGE_MARK in the PSI5 message containing the list of frequencies to measure. If the measurement order has been initiated by a PACKET MEASUREMENT ORDER message, the PSI5_CHANGE_MARK parameter shall be omitted from the message.

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

BA_USED (1 bit field)
3G_BA_USED (1 bit field)
PSI3_CHANGE_MARK (2 bit field)

In case of NC measurement report, these fields shall be included and contain the value of the BA_IND, 3G_BA_IND and PSI3_CHANGE_MARK respectively in the messages defining the used Neighbour Cell list and E-UTRAN Neighbour Cell list.

In case PBCCH exists, PSI3_CHANGE_MARK shall be used.
In case PBCCH does not exist, BA_USED and 3G_BA_USED shall be used.

| +|

PMO_USED (1 bit field)

This parameter shall contain the value of the PMO_IND in the PACKET CELL CHANGE ORDER or PACKET MEASUREMENT ORDER messages that has modified the used Neighbour Cell list. If no such message has been received, PMO_USED shall be set to zero.

| +|

NC_MODE (1 bit field)

This field indicates if the mobile station was in mode NC1 or NC2 when sending the measurement report.

0 Mobile station in mode NC1
1 Mobile station in mode NC2

| +|

RXLEV_SERVING_CELL (6 bit field)

This field contains the value of the RXLEV parameter for the serving cell calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as the binary representation of the RXLEV parameter value defined in 3GPP TS 45.008.
Range 0 to 63

| +|

FREQUENCY_N (6 bit field)

This field indicates the frequency/cell upon which the measurement was made. The field is an index into the resulting Frequency/Cell List for NC measurements.

NC Measurements

If PBCCH is allocated in the cell, the resulting frequency/cell list for NC Measurements is the GSM Neighbour Cell list defined in sub-clause 5.6.3.2.

If PBCCH is not allocated in the cell, the resulting frequency/cell list for NC Measurements is

  • - The BA(GPRS) (defined in sub-clause 5.6.3.2) before the MS has acquired the complete GSM Neighbour Cell list from the BCCH messages. In this case, the MS shall not include R99 extension ('Additions in release 99') in the PACKET MEASUREMENT REPORT message.
  • - The GSM Neighbour Cell list (defined in sub-clause 5.6.3.2) after the MS has acquired the complete GSM Neighbour Cell list from the BCCH messages. When the mobile station has acquired the GSM Neighbour Cell list, the mobile station shall include in the measurement reports only cells present in that list.
| +|

BSIC_N (6 bit field)

This field indicates the BSIC of the frequency upon which the measurement was made. This field shall be included only for frequencies that refer to the BA(BCCH) list. The field is encoded as the BSIC value defined in 3GPP TS 44.018.
Range 0 to 63

| +|

RXLEV_N (6 bit field)

This field indicates the measured RXLEV of the frequency upon which the measurement was made (see 3GPP TS 45.008). This field is encoded as the RXLEV value defined in 3GPP TS 44.018.
Range 0 to 63

| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3G Measurements
Measurement reporting for 3G Cells is defined in 3GPP TS 45.008.

3G_CELL_LIST_INDEX (7 bit field)
This is the index of the i'th reported 3G neighbour cell in the 3G Neighbour Cell List. See sub-clause 5.6.3.1.

REPORTING_QUANTITY (6 bit field)
This is the reporting quantity for the i'th reported 3G cell. The quantities are defined in 3GPP TS 45.008 for the respective Radio Access Technology. | +| G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in Iu mode . | +| E-UTRAN Measurements
Measurement reporting for E-UTRAN Cells is defined in 3GPP TS 45.008.

E-UTRAN_FREQUENCY_INDEX (3 bit field)
This field contains the index into the frequencies specified as part of the E-UTRAN Neighbour Cell list. This field is described in sub-clause 12.53.

CELL_IDENTITY (9 bit field)
This field contains the physical layer cell identity (as defined in 3GPP TS 36.211) of the cell being reported.

REPORTING_QUANTITY (6 bit field)
This is the reporting quantity for E-UTRAN cell identified by the E-UTRAN frequency and physical layer cell identity. The quantities are defined in 3GPP TS 45.008 for the respective Radio Access Technology. | +| UTRAN CSG Measurement Report
Measurement reporting for UTRAN CSG cells is defined in 3GPP TS 45.008. This information element contains the measurement results and routing parameters for one UTRAN CSG or hybrid cell. It is defined in sub-clause 12.61. | +| E-UTRAN CSG Measurement Report
Measurement reporting for E-UTRAN CSG cells is defined in 3GPP TS 45.008. This information element contains the measurement results and routing parameters for one E-UTRAN CSG or hybrid cell. It is defined in sub-clause 12.60. | +| SI23_BA_USED (1 bit field)

In case of NC measurement report, this field contains the value of the SI 23_BA_IND field in the SYSTEM INFORMATION TYPE 23 message defining the E-UTRAN Neighbour Cell list used. In the case SYSTEM INFORMATION TYPE 23 message is not broadcast in the cell or if the mobile station does not support network sharing this field shall be set to 0. Range 0 to 1. | + +#### 11.2.9b Packet Measurement Order + +This message is sent on the PCCCH or PACCH by the network to a mobile station giving information for NC and EXT measurement reporting and network controlled cell reselection. If not all information fits into one message, the remaining information will be sent in other instances of the Packet Measurement Order message. + +- Message type: PACKET MEASUREMENT ORDER +- Direction: network to mobile station +- Classification: non-distribution message + +**Table 11.2.9b.1: Packet Measurement Order information elements** + +``` + +< Packet Measurement Order message content > ::= + < PAGE_MODE : bit (2) > + { 0 < Global TFI : < Global TFI IE > > + | 10 < TLLI / G-RNTI : bit (32) > } + { < PMO_INDEX : bit (3) > + < PMO_COUNT : bit (3) > + { 0 | 1 < NC Measurement Parameters : < NC Measurement Parameters struct > > } + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release 98 : + { 0 | 1 < LSA Parameters : < LSA Parameters IE >> } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release 99 : + { 0 | 1 < ENH Measurement Parameters : < ENH Measurement Parameters struct >> } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-4 : + < CCN_ACTIVE : bit > + { 0 | 1 < CCN Support Description : < CCN Support Description struct >> } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + { 0 | 1 < Iu Mode Neighbour Cell Parameters : + { 1 < Iu Mode Neighbour Cell params struct > } ** 0 > } + -- Supplementary information for dual Iu mode and A/Gb mode capable cells + { 0 | 1 < NC Iu MODE ONLY CAPABLE CELL LIST : NC Iu Mode Only Cell List struct > } + { 0 | 1 < GPRS 3G Additional Measurement Parameters Description 2 : + < GPRS 3G Additional Measurement Parameters Description 2 struct >> } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-6 : + < 3G_CCN_ACTIVE : bit > + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-7 : + { 0 | 1 < 700_REPORTING_OFFSET : bit (3) > + < 700_REPORTING_THRESHOLD : bit (3) > } + { 0 | 1 < 810_REPORTING_OFFSET : bit (3) > + < 810_REPORTING_THRESHOLD : bit (3) > } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-8 + { 0 | 1 < 3G_BA_IND : bit > < PMO_IND : bit > } + { 0 | 1 < Priority and E-UTRAN Parameters Description : + < Priority and E-UTRAN Parameters Description struct >> } + { 0 | 1 < Individual Priorities : < Individual Priorities IE >> } + { 0 | 1 < 3G CSG Description : < 3G CSG Description IE >> } + { 0 | 1 < E-UTRAN CSG Description : < E-UTRAN CSG Description IE >> } + { 0 | 1 < Measurement Control Parameters Description : + < Measurement Control Parameters Description IE >> } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-9 + { 0 | 1 < Enhanced Cell Reselection Parameters Description : + < Enhanced Cell Reselection Parameters IE >> } + { 0 | 1 < CSG Cells Reporting Description : + < CSG Cells Reporting Description struct >> } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-11 + { 0 | 1 < E-UTRAN IPP with extended EARFCNs: + < E-UTRAN IPP with extended EARFCNs IE>> } + { 0 | 1 < E-UTRAN NC with extended EARFCNs: + < E-UTRAN NC with extended EARFCNs IE>> } + + < padding bits > } } } } } } } } } + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + +``` + +``` + +< NC Measurement Parameters struct > ::= + < NETWORK_CONTROL_ORDER : bit (2) > + { 0 | 1 < NC_NON_DRX_PERIOD : bit (3) > + < NC_REPORTING_PERIOD_I : bit (3) > + < NC_REPORTING_PERIOD_T : bit (3) > } + { 0 | 1 < NC_FREQUENCY_LIST : < NC Frequency list struct > > } ; + +< NC Frequency list struct > ::= + { 0 | 1 { < NR_OF_REMOVED_FREQ : bit (5) > + { < REMOVED_FREQ_INDEX : bit (6) > } * (1 + val(NR_OF_REMOVED_FREQ)) } } + { 1 < List of added Frequency struct : < Add Frequency list struct > > } ** 0; + +< Add Frequency list struct > ::= + < START_FREQUENCY : bit (10) > + < BSIC : bit (6) > + { 0 | 1 < Cell selection params : < Cell Selection struct > > } + < NR_OF_FREQUENCIES : bit (5) > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (1+val(FREQ_DIFF_LENGTH)) > + < BSIC : bit (6) > + { 0 | 1 < Cell selection params : < Cell Selection struct > > } } * (val(NR_OF_FREQUENCIES)); + +< Cell Selection struct > ::= + < CELL_BAR_ACCESS_2 : bit (1) > + < EXC_ACC : bit > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13_PBCCH_LOCATION : < SI13_PBCCH_LOCATION struct > > } ; + +< SI13_PBCCH_LOCATION struct > ::= + { 0 < SI13_LOCATION : bit (1) > + | 1 < PBCCH_LOCATION : bit (2) > + < PSI1_REPEAT_PERIOD : bit (4) > } ; + +< HCS struct > ::= + < PRIORITY_CLASS : bit (3) > + < HCS_THR : bit (5) > ; + +< ENH Measurement parameters struct > ::= + { 0 < BA_IND : bit > < 3G_BA_IND : bit > | 1 < PSI3_CHANGE_MARK : bit(2) > } + < PMO_IND : bit > + < REPORT_TYPE : bit > + < REPORTING_RATE : bit > + < INVALID_BSIC_REPORTING : bit > + { 0 | 1 < 3G Neighbour Cell Description : < 3G Neighbour Cell Description struct >> } + { 0 | 1 < GPRS REP PRIORITY Description : < GPRS REP PRIORITY Description struct >> } + { 0 | 1 < GPRS MEASUREMENT Parameters Description : + < GPRS MEASUREMENT PARAMETERS Description struct >> } + { 0 | 1 < GPRS 3G MEASUREMENT Parameters Description : + < GPRS 3G MEASUREMENT PARAMETERS BIS Description struct >> } ; + +< 3G Neighbour Cell Description struct > ::= + { 0 | 1 < Index_Start_3G : bit (7) > } + { 0 | 1 < Absolute_Index_Start_EMR : bit (7) > } + { 0 | 1 < UTRAN FDD Description : < UTRAN FDD Description struct > } + { 0 | 1 < UTRAN TDD Description : < UTRAN TDD Description struct > } + { 0 | 1 < CDMA2000 Description : < CDMA2000 Description struct > } + { 0 | 1 < REMOVED_3GCELL_Description : < REMOVED_3GCELL_Description struct >> } ; + +``` + +``` + +< REMOVED_3GCELL_Description struct > ::= + < N1 : bit (2) > + { + < N2 : bit (5) > + { + < REMOVED_3GCELL_INDEX : bit (7) > + < 3G_CELL_DIFF_LENGTH : bit (3) > + < 3GCELL_DIFF : bit (val(3G_CELL_DIFF_LENGTH)) > + } * (1+val(N2)) + } * (1+val(N1)); + +< UTRAN FDD Description struct > ::= + { 0 | 1 < Bandwidth_FDD : bit (3) > } + { 1 < Repeated UTRAN FDD Neighbour Cells : Repeated UTRAN FDD Neighbour Cells struct >> } ** 0 ; + +< Repeated UTRAN FDD Neighbour Cells struct > ::= + 0 < FDD-ARFCN : bit (14) > -- The value '1' was used in an earlier + -- version of the protocol and shall not be used. + < FDD_Indic0 : bit > + < NR_OF_FDD_CELLS : bit (5) > + < FDD_CELL_INFORMATION Field : bit(p(NR_OF_FDD_CELLS)) > ; + -- p(x) defined in table 11.2.9b.2.a/3GPP TS 44.060 + +< UTRAN TDD Description struct > ::= + { 0 | 1 < Bandwidth_TDD : bit (3) > } + { 1 < Repeated UTRAN TDD Neighbour Cells : < Repeated UTRAN TDD Neighbour Cells struct >> } ** 0 ; + +< Repeated UTRAN TDD Neighbour Cells struct > ::= + < TDD_Indic0 : bit > + 0 < TDD-ARFCN : bit (14) > -- The value '1' was used in an earlier + -- version of the protocol and shall not be used. + < NR_OF_TDD_CELLS : bit (5) > + < TDD_CELL_INFORMATION Field : bit(q(NR_OF_TDD_CELLS)) > ; + -- q(x) defined in table 11.2.9b.2.b/3GPP TS 44.060 + +< CDMA 2000 Description struct > ::= + < cdma2000 frequency band : bit (5) > + < cdma2000 frequency : bit (11) > + < number_cdma2000_cells : bit (5) > + { + < Pilot PN offset : bit (9) > + -- this information is enough for 1X Common Pilot + { 0 | 1 { 000 { < TD_MODE : bit (2) > < TD_POWER_LEVEL : bit (3) > } + -- additional information for 1X Common Pilot with Transmit Diversity + | 001 { < QOF : bit (2) > < WALSH_LEN_A : bit (3) > + < AUX_PILOT_WALSH : bit(val(WALSH_LEN_A)+6) > } + -- additional information for 1X Auxiliary Pilot + | 010 { < QOF : bit (2) > < WALSH_LEN_B : bit (3) > + < AUX_TD_WALSH : bit(val(WALSH_LEN_B)+6) > + < AUX_TD_POWER_LEVEL : bit (2) > < TD_MODE : bit (2) > } + -- additional information for 1X Auxiliary Pilot with Transmit Diversity + | 011 { < SR3_PRIM_PILOT : bit (2) > < SR3_PILOT_POWER1 : bit (3) > + < SR3_PILOT_POWER2 : bit (3) > } + -- additional information for 3X Common Pilot + | 110 { < SR3_PRIM_PILOT : bit (2) > < SR3_PILOT_POWER1 : bit (3) > + < SR3_PILOT_POWER2 : bit (3) > < QOF : bit (2) > + < WALSH_LEN_C : bit (3) > + < AUX_WALSH_LEN : bit(val(WALSH_LEN_C)+6) > + { 0 | 1 < QOF1 : bit (2) > < WALSH_LENGTH1 : bit (3) > + < AUX_PILOT_WALSH1 : bit(val(WALSH_LENGTH1)+6) > } + { 0 | 1 < QOF2 : bit (2) > < WALSH_LENGTH2 : bit (3) > + < AUX_PILOT_WALSH2 : bit(val(WALSH_LENGTH2)+6) > } + -- additional information for 3X Auxiliary Pilot + } + } + } + } + } * val(number_cdma2000_cells); + +< GPRS REP PRIORITY Description struct > ::= + < Number_Cells : bit(7) > + { < REP_PRIORITY : bit > } * (val(Number_Cells)); + +``` + +``` + +< GPRS MEASUREMENT PARAMETERS Description struct > ::= +{ 0 | 1 < MULTIBAND_REPORTING : bit (2) > } +{ 0 | 1 < SERVING_BAND_REPORTING : bit (2) > } +< SCALE_ORD : bit(2) > + +{ 0 | 1 < 900_REPORTING_OFFSET : bit (3) > + < 900_REPORTING_THRESHOLD : bit (3) > } + +{ 0 | 1 < 1800_REPORTING_OFFSET : bit (3) > + < 1800_REPORTING_THRESHOLD : bit (3) > } + +{ 0 | 1 < 400_REPORTING_OFFSET : bit (3) > + < 400_REPORTING_THRESHOLD : bit (3) > } + +{ 0 | 1 < 1900_REPORTING_OFFSET : bit (3) > + < 1900_REPORTING_THRESHOLD : bit (3) > } + +{ 0 | 1 < 850_REPORTING_OFFSET : bit (3) > + < 850_REPORTING_THRESHOLD : bit (3) > } ; + +< GPRS 3G MEASUREMENT PARAMETERS BIS Description struct > ::= +< Qsearch_P : bit (4) > +{ 1 ! < Ignore : bit = < no string >> } -- this bit shall be ignored by the receiver +-- for backward compatibility with earlier releases +{ 0 | 1 < FDD_REP_QUANT : bit > -- FDD Parameters + < FDD_MULTIRAT_REPORTING : bit (2) > } + +{ 0 | 1 < FDD_REPORTING_OFFSET : bit (3) > + < FDD_REPORTING_THRESHOLD : bit (3) > } + +{ 0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) > } -- TDD Parameters +{ 0 | 1 < TDD_REPORTING_OFFSET : bit (3) > + < TDD_REPORTING_THRESHOLD : bit (3) > } + +{ 0 | 1 < CDMA2000_MULTIRAT_REPORTING : bit (2) > } -- CDMA2000 Parameters +{ 0 | 1 < CDMA2000_REPORTING_OFFSET : bit (3) > + < CDMA2000_REPORTING_THRESHOLD : bit (3) > } ; + +< CCN Support Description struct > ::= +< Number_Cells : bit (7) > +{ CCN_SUPPORTED : bit } * (val(Number_Cells)) ; +< lu Mode Neighbour Cell Params struct > ::= +{ 0 | 1 < lu Mode Cell Selection Params : < lu Mode Cell Selection struct > > } +< NR_OF_FREQUENCIES : bit (5) > +{ 0 | 1 < lu Mode Cell Selection Params : + < lu Mode Cell Selection struct > > } * (val(NR_OF_FREQUENCIES)) ; +< lu Mode Cell Selection struct > ::= +< CELL BAR QUALIFY 3 : bit (2) > +{ 0 | 1 < SI13Alt PBCCH Location : < SI13 PBCCH Location struct > > } ; +< NC lu Mode Only Cell List struct > ::= +{ 1 < List of added cells : < Add lu Mode Only Cell List struct > > } ** 0; +< Add lu Mode Only Cell List struct > ::= +< START_FREQUENCY : bit (10) > +< BSIC : bit (6) > +{ 0 | 1 < Cell selection params : < lu Mode Only Cell Selection struct > > } +< NR_OF_FREQUENCIES : bit (5) > +< FREQ_DIFF_LENGTH : bit (3) > +{ < FREQUENCY_DIFF : bit (val(FREQ_DIFF_LENGTH)) > + < BSIC : bit (6) > + { 0 | 1 < Cell selection params : + < lu Mode Only Cell Selection struct > > } } * (val(NR_OF_FREQUENCIES)) ; + +``` + +``` + +< Iu Mode Only Cell Selection struct > ::= + < CELL BAR QUALIFY 3 : bit (2) > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13Alt_PBCCH_LOCATION : < SI13_PBCCH_LOCATION struct > > } ; + +< GPRS 3G Additional Measurement Parameters Description 2 struct > ::= + { 0 | 1 < FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; + -- FDD Parameters + +< Priority and E-UTRAN Parameters Description struct > ::= + { 0 | 1 < Serving Cell Priority Parameters Description : < GSM Priority Parameters IE >> } + { 0 | 1 < 3G Priority Parameters Description : < 3G Priority Parameters IE >> } + { 0 | 1 < E-UTRAN Parameters Description : < E-UTRAN Parameters IE >> } ; + +< CSG Cells Reporting Description struct > ::= + { 0 | 1 < UTRAN CSG Cells Reporting Description : < UTRAN CSG Cells Reporting Description struct >> } + { 0 | 1 < E-UTRAN CSG Cells Reporting Description : < E-UTRAN CSG Cells Reporting Description struct >> } ; + +< UTRAN CSG Cells Reporting Description struct > ::= + { 0 | 1 < UTRAN_CSG_FDD_REPORTING_THRESHOLD : bit (3) > + < UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } + { 0 | 1 < UTRAN_CSG_TDD_REPORTING_THRESHOLD : bit (3) > } ; + +< E-UTRAN CSG Cells Reporting Description struct > ::= + { 0 | 1 < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD : bit (3) > + < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } + { 0 | 1 < E-UTRAN_CSG_TDD_REPORTING_THRESHOLD : bit (3) > + < E-UTRAN_CSG_TDD_REPORTING_THRESHOLD_2 : bit (6) > } ; + +``` + +**Table 11.2.9b.2 : Packet Measurement Order information element details** + +The Packet Measurement Order message contains measurement parameters either for Network Control measurements If parameters for the NC measurements are not included, a previous Packet Measurement Order message belonging to the same set of messages shall still be valid. + +The 'NC measurement parameters struct' contains the Network Control Order, the NC parameters and an NC Frequency List struct. If the value of the Network Control Order or any of the NC parameters differs between instances of the message, the value of the parameter in the instance with the highest PMO\_INDEX shall be valid and all others shall be ignored. + +If included the NC Frequency List struct is a deviation list which contains removed or added frequencies to the BA(GPRS) list (see 3GPP TS 45.008). The building of the resulting GSM Neighbour Cell list is defined in sub-clause 5.6.3.2. + +The 'LSA parameters IE' contains a list of LSA\_ID(s) corresponding to the entries in the 'Add Frequency list struct'. Some entries in 'LSA parameters IE' may be empty. The entries in the two structures are listed in the same order and the number of entries (nr\_of\_frequencies) should be the same. In case there are too few entries in the 'LSA parameters IE', empty entries shall be added at the end. In case there are too many entries in the 'LSA parameters IE', the last shall be discarded. The 'LSA parameters IE' is defined in sub-clause 12.28. + +The 'ENH Measurement parameters structure' contains information for performing enhanced measurements and reporting the measurement with the PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message. For a 3G multi-RAT mobile station it may also include information for reporting on 3G Cells. + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **PMO\_INDEX** (3 bit field) and **PMO\_COUNT** (3 bit field) + +The purpose of the PMO\_INDEX field and the PMO\_COUNT field is to indicate the number of individual messages within the sequence of Packet Measurement Order messages and to assign an index to identify each one of them. The PMO\_INDEX field is binary coded, range: 0 to 7, and provides an index to identify the individual Packet Measurement Order message. The PMO\_COUNT field is binary coded, range: 0 to 7, and provides the PMO\_INDEX value for the last (highest indexed) message in the sequence of Packet Measurement Order messages. A measurement order shall not be effected by the mobile station until all instances of a Packet Measurement Order message is received. + +##### **Global TFI** + +If present, this information element indicates the mobile station to which this message is addressed. This field is defined in sub-clause 12.10. + +#### **TLLI / G-RNTI** (32 bit field) + +If present, this field indicates the mobile station to which this message is addressed. This field is defined in sub-clause 12.16. + +#### **CCN\_ACTIVE** (1 bit field) + +This field indicates whether CCN is enabled in the serving cell for the mobile station when reselecting to a GSM cell. It is coded as follows: + +- 0 The broadcast CCN\_ACTIVE parameter shall apply if available. Otherwise CCN is disabled in the cell for the mobile station when reselecting to a GSM cell. +- 1 CCN is enabled in the cell for the mobile station when reselecting to a GSM cell. + +The NC Measurement Parameters gives the parameters for the serving cell and may contain frequency list deviations (add/delete) to the BA(GPRS) either on PBCCH or on BCCH. + +The **NC\_Measurement\_Parameters struct** contains the NETWORK\_CONTROL\_ORDER and the optional parameters NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I, NC\_REPORTING\_PERIOD\_T and the NC\_FREQUENCY LIST. + +#### **NETWORK\_CONTROL\_ORDER** (2 bit field) + +The NETWORK\_CONTROL\_ORDER field is coded according to the following table (for definition of NCx see 3GPP TS 45.008): + +| Bit | | | +|-----|---|-------| +| 2 | 1 | | +| 0 | 0 | NC0 | +| 0 | 1 | NC1 | +| 1 | 0 | NC2 | +| 1 | 1 | RESET | + +#### **NC\_NON\_DRX\_PERIOD** (3 bit field) + +#### **NC\_REPORTING\_PERIOD\_I** (3 bit field) + +#### **NC\_REPORTING\_PERIOD\_T** (3 bit field) + +For detailed element definitions, see the PSI5 message. + +#### **NR\_OF\_REMOVED\_FREQ** (5 bit field) + +1+val(NR\_OF\_REMOVED\_FREQ) indicates the number of frequencies in the BA-list which shall not be used for NC-measurements and gives the number of instances of the parameter REMOVED\_FREQ\_INDEX. Range of NR\_OF\_REMOVED\_FREQ: 0 to 31. + +#### **REMOVED\_FREQ\_INDEX** (6 bit field) + +This field indicates the index to the frequency to be removed in the BA(GPRS) sent on PBCCH or on BCCH, see sub-clause 5.6.3.2. + +Range: 0 to 63. + +Add Frequency list struct contains the frequency list for NC measurements. + +#### **START\_FREQUENCY** (10 bit field) + +#### **FREQ\_DIFF\_LENGTH** (3 bit field) + +#### **FREQUENCY\_DIFF** (1+val(FREQ\_DIFF\_LENGTH) bit field) + +For detailed element definition of these parameters, see the PSI5 message. + +#### **BSIC (6 bit field)** + +This field is encoded as the 'Base Station Identity Code' defined in 3GPP TS 23.003. + +Range 0 to 63 + +The **Cell selection params** in the Add Frequency list struct shall be present for the first neighbour cell added by the message. For description of the cell selection parameters see Table: *PSI3 information element details* + +As an abnormal case, if the **Cell selection params** is missed for the first neighbour cell added by the message then the same parameters as the serving cell shall be applied as default value: + +If PBCCH is present in the serving cell then : + +| | | +|---------------------------|------------------------------------------------------------------| +| CELL_BAR_ACCESS_2 : | Serving cell CELL_BAR_ACCESS_2 | +| EXC_ACC : | Serving cell EXC_ACC | +| SAME_RA_AS_SERVING_CELL : | The cell is in the same Routeing Area as the serving cell | +| GPRS_RXLEV_ACCESS_MIN : | Serving cell GPRS_RXLEV_ACCESS_MIN | +| GPRS_MS_TXPWR_MAX_CCH : | Serving cell GPRS_MS_TXPWR_MAX_CCH | +| GPRS_TEMPORARY_OFFSET : | 0 dB | +| GPRS_PENALTY_TIME : | Undefined | +| GPRS_RESELECT_OFFSET : | 0 dB | +| HCS_THR : | Serving cell HCS_THR | +| PRIORITY_CLASS : | Serving cell PRIORITY_CLASS | +| SI13_PBCCH_LOCATION : | Undefined. | + +If PBCCH is not present in the serving cell then : + +| | | +|---------------------------|------------------------------------------------------------------| +| CELL_BAR_ACCESS_2 : | Serving cell CELL_BAR_ACCESS | +| EXC_ACC : | Serving cell cell exclusive access support capability | +| SAME_RA_AS_SERVING_CELL : | The cell is in the same Routeing Area as the serving cell | + +The other parameters default values take the same values as if the structure is present and optional fields are omitted (see below). + +In case the cell selection params is given and if PBCCH is not present in the serving cell, optional parameters which are not present shall be affected with the following default values : + +| | | +|-------------------------|-------------------------------| +| GPRS_RXLEV_ACCESS_MIN : | Serving cell RXLEV_ACCESS_MIN | +| GPRS_MS_TXPWR_MAX_CCH : | Serving cell MS_TXPWR_MAX_CCH | +| GPRS_TEMPORARY_OFFSET : | 0 dB | +| GPRS_PENALTY_TIME : | Undefined | +| GPRS_RESELECT_OFFSET : | 0 dB | +| HCS_THR : | infinity | +| PRIORITY_CLASS : | undefined | +| SI13_PBCCH_LOCATION : | undefined | + +In case the cell selection params is given and if PBCCH is present in the serving cell, optional parameters which are not present shall be affected with the following default values : + +| | | +|-------------------------|------------------------------------| +| GPRS_RXLEV_ACCESS_MIN : | Serving cell GPRS_RXLEV_ACCESS_MIN | +| GPRS_MS_TXPWR_MAX_CCH : | Serving cell GPRS_MS_TXPWR_MAX_CCH | +| GPRS_TEMPORARY_OFFSET : | 0 dB | +| GPRS_PENALTY_TIME : | Undefined | +| GPRS_RESELECT_OFFSET : | 0 dB | +| HCS_THR : | Serving cell HCS_THR | +| PRIORITY_CLASS : | Serving cell PRIORITY_CLASS | +| SI13_PBCCH_LOCATION : | Undefined. | + +The following neighbour cells defined in the message use the parameter values of the previous neighbour cell as their default values. + +##### **ENH Measurement Parameters:** + +- BA\_IND** (1 bit field) +- 3G\_BA\_IND** (1 bit field) +- PSI3\_CHANGE\_MARK** (2 bit field) + +These parameters are needed to allow the mobile station to associate the removed/added cells or frequencies to the correct Neighbour Cell list. The values of this parameters are reflected in the PACKET ENHANCED MEASUREMENT REPORT message and in the PACKET MEASUREMENT REPORT message. + +#### **PMO\_IND** (1 bit field) + +This parameter is needed to allow the network to discriminate measurements results related to Neighbour Cell list modified by different Packet Cell Change Order or Packet Measurement Order messages sent to the MS. The value of this parameter is reflected in the PACKET ENHANCED MEASUREMENT REPORT message and in the PACKET MEASUREMENT REPORT message. + +#### **REPORT\_TYPE** (1 bit) + +This parameter is used to indicate to the mobile station to use the PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT messages for (NC) reporting: + +If the cell has a PBCCH allocated: + +##### **Bit** + +- 0** The mobile station shall use the PACKET ENHANCED MEASUREMENT REPORT message for (NC) reporting +- 1** The mobile station shall use the PACKET MEASUREMENT REPORT message for (NC) reporting + +If the cell has no PBCCH allocated: + +##### **Bit** + +- 0** The mobile station shall use the PACKET ENHANCED MEASUREMENT REPORT message for (NC) reporting if at least one BSIC is allocated to each BA(GPRS) frequency. Otherwise, the PACKET MEASUREMENT REPORT shall be used. +- 1** The mobile station shall use the PACKET MEASUREMENT REPORT message for (NC) reporting + +#### **REPORTING\_RATE** (1 bit) + +This parameter is used for measurements, see 3GPP TS 45.008. + +##### **bit** + +- 0** Normal rate reporting +- 1** Reduced reporting rate allowed + +#### **INVALID\_BSIC\_REPORTING** (1 bit) + +This field specifies if cells with invalid BSIC and allowed NCC part of BSIC are allowed to be reported or not, see 3GPP TS 45.008. + +##### **bit** + +- 0** Report on cells with invalid BSIC and allowed NCC part of BSIC is not allowed. +- 1** Report on cells with invalid BSIC and allowed NCC part of BSIC is allowed. In this case NCC\_PERMITTED is required in PSI5. + +#### **3G Neighbour Cell Description:** + +The building of the 3G Neighbour Cell list and the ordering of indices within each Radio Access Technology is described in sub-clause 5.6.3.1. + +##### **Index\_Start\_3G** (7 bit) + +This optional information element indicates the value of the first index to use to build this instance of the 3G Neighbour Cell list. When missing, the value 0 is assumed. See sub-clause 5.6.3.1. + +##### **Absolute\_Index\_Start\_EMR** (7 bit) + +This parameter indicates the value to be added to the indices of the 3G Neighbour Cell list for reporting 3G Cells with the PACKET ENHANCED MEASUREMENT REPORT message (see sub-clause 5.6.3.3). If present, it overrides the parameter value of the reference 3G Neighbour Cell list. If different values are received for this parameter in different instances of this message, the instance with the highest index shall be used. + +NOTE: This parameter is not used for reporting 3G Cells with the PACKET MEASUREMENT REPORT message, see sub-clause 11.2.9. + +#### **UTRAN FDD Description:** + +##### **Bandwidth\_FDD** (3 bit field) + +This information element will be used for future releases of the protocol. When missing, this indicates the present FDD bandwidth. When present, this shall not be considered as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly. + +##### **FDD\_ARFCN** (14 bit field) + +This information element is defined as the UARFCN in 3GPP TS 25.101. Any non-supported frequency shall not be considered as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly. + +##### **FDD\_Indic0**, information 0 indicator (1 bit): + +This field indicates if the Scrambling Code/Diversity parameter value '0000000000' is a member of the set. + +##### Bit + +- 0 parameter value '0000000000' is not a member of the set +- 1 parameter value '0000000000' is a member of the set + +NOTE: This bit FDD\_Indic0 is equivalent to the bit F0 bit in the frequency list information element (see 3GPP TS 44.018). + +#### **NR\_OF\_FDD\_CELLS** (5 bit field) + +This field defines the number of FDD\_CELL\_INFORMATION parameters. + +##### **FDD\_CELL\_INFORMATION Field** (p bit field) + +This field allows to compute a set of 10-bit-long FDD\_CELL\_INFORMATION parameters, re-using the *Range 1024 format* compression algorithm, see 3GPP TS 44.018 Annex J: 'Algorithm to encode frequency list information'. The formulas for decoding are given in 3GPP TS 44.018: 'Range 1024 format'. The consecutive parameters of this field are concatenated, starting with w1, and then w2, w3... + +The total number of bits p of this field depends on the value of the parameter NR\_OF\_FDD\_CELLS = n, as follows: + +| n | p | n | p | n | p | n | p | +|---|----|---|----|----|-----|-------|-----| +| 0 | 0 | 5 | 44 | 10 | 81 | 15 | 116 | +| 1 | 10 | 6 | 52 | 11 | 88 | 16 | 122 | +| 2 | 19 | 7 | 60 | 12 | 95 | 17-31 | 0 | +| 3 | 28 | 8 | 67 | 13 | 102 | | | +| 4 | 36 | 9 | 74 | 14 | 109 | | | + +Table 11.2.9b.2.a + +If n=0 and FDD\_Indic0 = 0, this indicates the 3G Neighbour Cell list index for report on RSSI, see 3GPP TS 45.008. + +If n is equal or greater than 17, this shall not be considered as an error; the corresponding index in the 3G Neighbour Cell list shall be incremented by one. The entry created in the 3G Neighbour Cell list does not contain valid information. + +For each (10-bit-long) decoded parameter, bits 1-9 are the Scrambling Code and bit 10 is the Diversity bit. + +##### **Scrambling Code** (9 bit field) + +This parameter indicates the Primary Scrambling Code as defined in 3GPP TS 25.213. + +##### **Diversity** (1 bit field) + +This parameter indicates if diversity is applied for the cell: + +##### Bit + +- 0 Diversity is not applied for this cell +- 1 Diversity is applied for this cell. + +#### **UTRAN TDD Description:** + +##### **Bandwidth\_TDD** (3bit field) + +This optional information element refers to 3GPP TS 25.331. + +##### Bit + +321 + +000 3,84 Mcps + +001 1,28 Mcps + +All other values shall not be interpreted as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly (but no reporting can be performed). When missing, this indicates 3,84 Mcps. + +##### **TDD\_ARFCN** (14 bit field) + +This optional information element is defined as the UARFCN in 3GPP TS 25.102. Any non supported frequency shall not be considered as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly. + +##### **TDD\_Indic0**, information 0 indicator (1 bit): + +This field indicates if the Cell\_Parameter/Sync\_Case/Diversity parameter value '000000000' is a member of the set. + +##### Bit + +- 0 parameter value '000000000' is not a member of the set +- 1 parameter value '000000000' is a member of the set + +#### **NR\_OF\_TDD\_CELLS** (5 bit field) + +This field defines the decimal value of the number of TDD\_CELL\_INFORMATION parameters. + +##### **TDD\_CELL\_INFORMATION Field** (q bit field) + +This field allows to compute a set of 9-bit-long TDD\_CELL\_INFORMATION parameters, re-using the *Range 512 format* compression algorithm, see 3GPP TS 44.018 Annex J: 'Algorithm to encode frequency list information'. The formulas for decoding are given in 3GPP TS 44.018 sub-clause 10.5.2.13.4: 'Range 512 format', with w0=0. The consecutive parameters of this field are concatenated, starting with w1, and then w2, w3... + +The total number of bits q of this field depends on the value of the parameter NR\_OF\_TDD\_CELLS = m, as follows: + +| m | q | m | q | m | q | m | q | m | q | +|---|----|---|----|----|----|----|-----|-------|-----| +| 0 | 0 | 5 | 39 | 10 | 71 | 15 | 101 | 20 | 126 | +| 1 | 9 | 6 | 46 | 11 | 77 | 16 | 106 | 21-31 | 0 | +| 2 | 17 | 7 | 53 | 12 | 83 | 17 | 111 | | | +| 3 | 25 | 8 | 59 | 13 | 89 | 18 | 116 | | | +| 4 | 32 | 9 | 65 | 14 | 95 | 19 | 121 | | | + +Table 11.2.9b.2.b. + +If m=0 and TDD\_Indic0=0, or m is equal or greater than 21, this shall not be considered as an error; the corresponding index in the 3G Neighbour Cell list shall be incremented by one. The entry created in the 3G Neighbour Cell list does not contain valid information. + +For each (9-bit-long) decoded parameter, bits 1-7 are the Cell Parameter, bit 8 is the Sync Case TSTD and bit 9 is the Diversity TDD bit. + +#### **Cell Parameter** (7 bit field) + +This parameter is defined in 3GPP TS 25.223. + +##### **Sync Case TSTD (1 bit field)** + +For 3.84 Mcps TDD, this parameter is defined in 3GPP TS 25.223. + +Bit + +- 0 Sync Case 1 +- 1 Sync Case 2 + +For 1.28 Mcps TDD, this parameter indicates if TSTD (see 3GPP TS 25.224) is applied for the cell: + +Bit + +- 0 TSTD is not applied for this cell +- 1 TSTD is applied for this cell. + +#### **Diversity TDD (1 bit field)** + +This parameter indicates if SCTD (see 3GPP TS 25.224) is applied for the cell: + +Bit + +- 0 SCTD is not applied for this cell +- 1 SCTD is applied for this cell. + +#### **CDMA 2000 Description:** + +##### **cdma2000 frequency band (5 bit field)** + +A binary representation of cdma2000 BAND\_CLASS, as defined in TIA/EIA-IS-2000-5-A. The mobile station shall ignore all the information relative to a cdma2000 frequency band that it can not support. + +##### **cdma2000 frequency (11 bit field)** + +A binary representation of cdma2000 CDMA\_FREQ, as defined in TIA/EIA-IS-2000-5-A. The mobile station shall ignore all the information relative to a cdma2000 frequency that it can not support. + +##### **number\_cdma2000\_cells (5 bit field)** + +This field indicates the number of CDMA 2000 neighbour cells. + +##### **Pilot PN offset (9 bit field)** + +A binary representation of the PN offset of the Pilot PN sequence (in units of 64 cdma2000 1x-chips), PILOT\_PN, as defined in TIA/EIA-IS-2000-5-A. + +#### **TD\_MODE (2 bit field)** + +An indication of transmit diversity mode is specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore TD\_MODE if it does not support 1X Common Pilot with Transmit Diversity. + +#### **TD\_POWER\_LEVEL (3 bit field)** + +Power level of the Transmit Diversity Pilot relative to that of the Forward Pilot Channel as specified in TIA/EIA-IS-2000-5-A. The mobile station shall ignore TD\_POWER\_LEVEL if it does not support 1X Common Pilot with Transmit Diversity. + +#### **QOF (2 bit field)** + +Quasi-orthogonal function index is defined in TIA/EIA-IS-2000-5-A. The mobile station shall ignore QOF if it does not support the quasi-orthogonal function. + +#### **WALSH\_LEN\_A, WALSH\_LEN\_B and WALSH\_LEN\_C (3 bit field each)** + +A three bit field to indicate the length of the Walsh code for the pilot that is used in as the Auxiliary Pilot, and specified as WALSH\_LEN in TIA/EIA-IS-2000-5-A. The mobile station shall ignore WALSH\_LEN if it does not support 1X Auxiliary Pilot. + +#### **AUX\_PILOT\_WALSH** (var.Length field) + +Indicates the walsh code corresponding to the Auxiliary Pilot, as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore AUX\_PILOT\_WALSH if it does not support 1X Auxiliary Pilot. + +#### **AUX\_TD\_WALSH** (var.Length field) + +Indicates the walsh code corresponding to the Auxiliary Transmit Diversity Pilot, as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore AUX\_TD\_WALSH if it does not support 1X Auxiliary Pilot with Transmit Diversity. + +##### **AUX\_TD\_POWER\_LEVEL** (2 bit field) + +Power level of the Auxiliary Transmit Diversity Pilot relative to that of the Forward Pilot Channel as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore AUX\_TD\_POWER\_LEVEL if it does not support 1X Auxiliary Pilot with Transmit Diversity. + +#### **SR3\_PRIM\_PILOT** (3 bit field) + +Position of the primary SR3 pilot as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore SR3\_PRIM\_PILOT if it does not support 3X Common Pilot. + +**SR3\_PILOT\_POWER1** (3 bit field), relative power level between the primary SR3 pilot and the pilot on the lower frequency of the two remaining SR3 frequencies, as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore SR3\_PILOT\_POWER1 if it does not support 3X Common Pilot. + +**SR3\_PILOT\_POWER2** (3 bit field), relative power level between the primary SR3 pilot and the pilot on the higher frequency of the two remaining SR3 frequencies, as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore SR3\_PILOT\_POWER2 if it does not support 3X Common Pilot. + +##### **QOF1** (2 bit field), **WALSH\_LEN1** (3 bit field) and **AUX\_PILOT\_WALSH1** (var. Length field) + +The corresponding quantities for pilot on the lower frequency of the two remaining SR3 frequencies, as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore QOF1, WALSH\_LEN1 and AUX\_PILOT\_WALSH1 if it does not support 3X Auxiliary Pilot. + +##### **QOF2** (2 bit field), **WALSH\_LENGTH2** (3 bit field) and **AUX\_PILOT\_WALSH2** (var Length field) + +The corresponding quantities for pilot on the higher frequency of the two remaining SR3 frequencies, as specified in TIA/EIA/IS-2000-5-A. The mobile station shall ignore QOF2, WALSH\_LEN2 and AUX\_PILOT\_WALSH2 if it does not support 3X Auxiliary Pilot. + +#### ***REMOVED\_3GCELL\_Description*** + +This struct contains a list of cells to be removed from the 3G Neighbour Cell list for measurements (see sub-clause 5.6.3.1). The cells are identified by their index. The struct consists of N1 sublists, each comprising the following three parameters: + +##### **REMOVED\_3GCELL\_INDEX** (7 bit field) + +This field indicates the index of the first cell in the sublist. + +#### **3G\_CELL\_DIFF\_LENGTH** (3 bit field) + +This field indicates the number of bits used for the 3GCELL\_DIFF field in the current sublist. + +##### **3GCELL\_DIFF** (variable size) + +This field indicates the difference in index to the next cell in the sublist. + +#### ***GPRS REP PRIORITY Description*** + +##### **REP\_PRIORITY bit:** + +**0** Normal reporting priority + +**1** High reporting priority + +The use of these bits is defined in sub-clause 5.6.3.5 and 3GPP TS 45.008. + +#### **GPRS MEASUREMENT PARAMETERS Description** + +The fields of this Description are used for measurements, as defined in 3GPP TS 45.008. + +Any parameter present overwrites any old data held by the mobile station for this parameter. + +#### **GPRS 3G MEASUREMENT PARAMETERS Description** + +The fields of this Description are used for measurements, as defined in 3GPP TS 45.008. + +Any parameter present overwrites any old data held by the mobile station for this parameter. + +#### **GPRS 3G Additional Measurement Parameters Description 2** + +The fields of this Description are used for measurements, as defined in 3GPP TS 45.008. + +Any parameter present overwrites any old data held by the mobile station for this parameter. + +#### **CCN Support Description** + +#### **CCN\_SUPPORTED** (1 bit field) + +This parameter is used for determining whether the mobile station shall enter CCN mode when re-selecting a cell and CCN is enabled. The use of these bits is described in sub-clause 8.8.2a ("CCN support description"): + +Bit + +**0** CCN is enabled towards the corresponding cell + +**1** CCN is disabled towards the corresponding cell + +#### **G-RNTI extension** (4 bit field) + +This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in *Iu mode*. + +#### **Iu Mode Neighbour Cell Parameters** + +The *Iu mode Neighbour Cell Parameters* shall only be included when the *List of added Frequency struct* is present. + +#### **Iu Mode Neighbour Cell Params Struct** + +This struct presents supplementary information for *Iu mode* capable cells. The struct assigns *Iu mode* parameter values to the neighbouring cells defined by the message. The *Iu mode Neighbour Cell params struct* values are assigned to the neighbouring cells in the same order they appear in the *List of added Frequency struct*. + +##### **NC Iu Mode Only Capable Cell List Parameters** + +These parameters are used to add Iu mode only capable cells to BA(GPRS) list. + +#### **CELL BAR QUALIFY 3** (2 bit field) + +This information element is defined in 3GPP TS 44.018. + +#### **3G\_CCN\_ACTIVE** (1 bit field) + +This field indicates whether CCN is enabled towards 3G neighbouring cells. It is coded as follows: + +**0** The broadcast 3G\_CCN\_ACTIVE parameter shall apply if available. Otherwise, CCN towards 3G cells is disabled in the cell. + +**1** CCN towards 3G cells is enabled in the cell. + +#### **700\_REPORTING\_OFFSET** (3 bit field) + +#### **700\_REPORTING\_THRESHOLD** (3 bit field) + +These fields are used for measurements, as defined in 3GPP TS 45.008. + +Any parameter present overwrites any old data held by the mobile station for these parameters. + +#### **810\_REPORTING\_OFFSET** (3 bit field) + +#### **810\_REPORTING\_THRESHOLD** (3 bit field) + +These fields are used for measurements, as defined in 3GPP TS 45.008. + +Any parameter present overwrites any old data held by the mobile station for these parameters. + +#### **3G\_BA\_IND** (1 bit field) + +#### **PMO\_IND** (1 bit field) + +These parameters are described in the *ENH Measurement Parameters* information element. + +If either of these parameters are included also in the *ENH Measurement Parameters* information element, the values provided by the *ENH Measurement Parameters* information element shall be used. + +#### **Serving Cell Priority Parameters Description** + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. Any parameter present overwrites any old data held by the mobile station for these parameters. This information element is defined in sub-clause 12.51. + +### **3G Priority Parameters Description** + +This information element is defined in sub-clause 12.52. Any parameter present overwrites any old data held by the mobile station for these parameters. + +### **E-UTRAN Parameters Description** + +This information element is defined in sub-clause 12.53. If the conditions for sending the *E-UTRAN NC with extended EARFCNs* information element are met (see definition of *E-UTRAN NC with extended EARFCNs* IE below) then the *Repeated E-UTRAN Neighbour Cells* IE shall not be provided within the *E-UTRAN Parameters Description* information element. + +#### **Individual Priorities** + +This information element is defined in sub-clause 12.50. If the conditions for sending the *E-UTRAN IPP with extended EARFCNs* information element are met (see definition of *E-UTRAN IPP with extended EARFCNs* IE below) then the *E-UTRAN Individual Priority Parameters Description* IE shall not be provided within the *Individual Priorities* information element. + +#### **3G CSG Description** + +This information element contains the description of the 3G CSG cells. This information element is defined in sub-clause 12.54. + +#### **E-UTRAN CSG Description** + +This information element contains the description of the E-UTRAN CSG cells. This information element is defined in sub-clause 12.55. + +#### **Measurement Control Parameters Description** + +This information element contains the Measurement control parameters per frequency for UTRAN and E-UTRAN. This information element is defined in sub-clause 12.56. + +#### **Enhanced Cell Reselection Parameters Description** + +This information element contains parameters for enhanced cell reselection procedures towards E-UTRAN cells, see 3GPP TS 45.008. + +This information element is defined in sub-clause 12.59. + +#### **CSG Cells Reporting Description** + +The fields of this structure are used to signal the related parameters for measurement and reporting for CSG cells in packet transfer mode as defined in 3GPP TS 45.008. If this structure is not present, the MS shall revert to the corresponding parameters for this structure as indicated by the last received SI2quater message. + +##### **UTRAN CSG Cells Reporting Description** + +**UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD** (3 bit field) +**UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD\_2** (6 bit field) +**UTRAN\_CSG\_TDD\_REPORTING\_THRESHOLD** (3 bit field) + +These fields are used to control the reporting for CSG cells as specified in 3GPP TS 45.008. If this IE is received containing none of the above fields for a given mode (FDD or TDD), the MS shall use the values of these fields from the *UTRAN CSG Cells Reporting Description* IE in the last received SI2quater within the serving cell. If no values have been received by the MS within the serving cell, the default values specified in 3GPP TS 45.008 shall apply. + +#### **E-UTRAN CSG Cells Reporting Description** + +**E-UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD** (3 bit field) +**E-UTRAN\_CSG\_FDD\_REPORTING\_THRESHOLD\_2** (6 bit field) +**E-UTRAN\_CSG\_TDD\_REPORTING\_THRESHOLD** (3 bit field) +**E-UTRAN\_CSG\_TDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +These fields are used to control the reporting for CSG cells as specified in 3GPP TS 45.008. If this IE is received containing none of the above fields for a given mode (FDD or TDD), the MS shall use the values of these fields from the *E-UTRAN CSG Cells Reporting Description* IE in the last received SI2quater within the serving cell. If no values have been received by the MS within the serving cell, the default values specified in 3GPP TS 45.008 shall apply. + +##### **E-UTRAN IPP with extended EARFCNs** + +This information element is defined in sub-clause 12.69. It shall be included if E-UTRAN individual priorities are provided and both the network and the mobile station support extended EARFCNs (see 3GPP TS 24.008); in such a case the *E-UTRAN Individual Priority Parameters Description* IE shall not be provided within the *Individual Priorities* IE (see definition of *Individual Priorities* IE above). + +##### **E-UTRAN NC with extended EARFCNs** + +This information element is defined in sub-clause 12.70. It shall be included if both the network and the mobile station support extended EARFCNs (see 3GPP TS 24.008); in such a case the *Repeated E-UTRAN Neighbour Cells* IE shall not be provided within the *E-UTRAN Parameters Description* IE (see definition of *E-UTRAN Parameters Description* IE above). + +#### **11.2.9b.1 GPRS REP PRIORITY description** + +A GPRS REP PRIORITY description construction shall be included in one and only one instance of the PACKET MEASUREMENT ORDER message within the consistent set of PACKET MEASUREMENT ORDER messages. + +### **11.2.9c Packet Mobile TBF Status** + +This message is sent from the mobile station to the network on the uplink PACCH to indicate erroneous messages have been received relating to either a downlink or an uplink TBF. + +Message type: PACKET MOBILE TBF STATUS + +Direction: mobile station to network + +**Table 11.2.9c.1: Packet MOBILE TBF STATUS information elements** + +``` +< Packet Mobile TBF Status message content > ::= + < GLOBAL TFI : < Global TFI IE > > + < TBF_CAUSE : bit (3) > + { 0 | 1 < STATUS_MESSAGE_TYPE : bit (6) > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-12 + { 0 | 1 < Downlink_eTFI : bit (3) > } + < padding bits > }; +``` + +**Table 11.2.9c.2: Packet MOBILE TBF STATUS information element details** + +#### **Global TFI IE** + +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +#### **TBF\_CAUSE** (3 bit field) + +The TBF\_CAUSE field indicates the error cause value of the current TBF. This field is encoded according to the following table: + +| Bit | | +|-------|---------------------------------------------------------------| +| 3 2 1 | | +| 0 0 0 | Normal event; | +| 0 0 1 | Status, unspecified; | +| 0 1 0 | Syntactically incorrect message, non-distribution part error; | +| 0 1 1 | Syntactically incorrect message, message escape; | +| 1 0 0 | Message not compatible with current protocol state. | + +All other values are reserved and may be interpreted "Status, unspecified". + +#### **STATUS\_MESSAGE\_TYPE** (6 bit field) + +The STATUS\_MESSAGE\_TYPE field, if present, is the binary representation of the message type of the downlink RLC/MAC control message that caused the status condition. Message type values are defined in sub-clause 11.2.0.1. + +#### **DOWNLINK\_eTFI** (3 bit field) + +See sub-clause 11.2.48 + +### 11.2.9d Packet Enhanced Measurement Report + +This message is sent either on the PACCH if in packet transfer mode or on an assigned block on a PDTCH, from the mobile station to the network to report enhanced measurement results. The message contains measurement results from the Network Control measurements. + +Message type: PACKET ENHANCED MEASUREMENT REPORT + +Direction: mobile station to network + +Table 11.2.9d.1: PACKET ENHANCED MEASUREMENT REPORT message content + +``` + +< PACKET ENHANCED MEASUREMENT REPORT message content > ::= + < TLLI / G-RNTI : bit (32) > + { < NC Measurement Report : < NC Measurement Report struct > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-8 : + < BITMAP_LENGTH : bit(7) > + { 0 | 1 < REPORTING_QUANTITY : bit (6) > } * (val(BITMAP_LENGTH + 1) ) + { 0 | 1 < E-UTRAN Measurement Report : < E-UTRAN Measurement Report struct > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-9 : + { 0 | 1 < UTRAN CSG Measurement Report : < UTRAN CSG Measurement Report IE > > } + { 0 | 1 < E-UTRAN CSG Measurement Report : < E-UTRAN CSG Measurement Report IE > > } + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-11 : + < SI23_BA_USED : bit > + < padding bits > } } } ; + +< NC Measurement Report struct > ::= + < NC_MODE : bit (1) > + { 0 < BA_USED : bit > < 3G_BA_USED : bit > + | 1 < PS13_CHANGE_MARK : bit(2) > } + < PMO_USED : bit > + < BSIC_Seen : bit > + < SCALE : bit > + { 0 | 1 < Serving cell data : < Serving cell data struct > > } + { 1 < Repeated Invalid_BSIC_Information : < Repeated Invalid_BSIC_Information struct > > } ** 0 + { 0 | 1 { 0 | 1 < REPORTING_QUANTITY : bit (6) > } ** } ; -- bitmap type reporting + +< Serving cell data struct > ::= + < RXLEV_SERVING_CELL : bit (6) > + 0 ; -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + +< Repeated Invalid_BSIC_Information struct > ::= + < BCCH-FREQ-NCELL : bit (5) > + < BSIC : bit (6) > + < RXLEV-NCELL : bit (6) > ; + +< E-UTRAN Measurement Report struct > ::= + < N_E-UTRAN : bit (2) > + { < E-UTRAN_FREQUENCY_INDEX : bit (3) > + < CELL_IDENTITY : bit (9) > + < REPORTING_QUANTITY : bit (6) > } * (val(N_E-UTRAN + 1) ) ; + +``` + +Table 11.2.9d.2: PACKET ENHANCED MEASUREMENT REPORT information element details + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TLLI / G-RNTI (32 bit field)
This field contains the TLLI / G-RNTI of the mobile station. This field is encoded as defined in sub-clause 12.16. | +| NC_MODE (1 bit field)
This field indicates if the mobile station was in mode NC1 or NC2 when sending the measurement report.
0 Mobile station in mode NC1
1 Mobile station in mode NC2 | + +**BA\_USED** (1 bit field), +**3G\_BA\_USED** (1 bit field) +**PSI3\_CHANGE\_MARK** (2 bit field) + +These fields shall contain the value of the BA\_IND, 3G\_BA\_IND and PSI3\_CHANGE\_MARK respectively in the messages defining the used Neighbour Cell list or E-UTRAN Neighbour Cell list. + +In case PBCCH exists, PSI3\_CHANGE\_MARK shall be used. +In case PBCCH does not exist, BA\_USED and 3G\_BA\_USED shall be used. + +**PMO\_USED** (1 bit field) + +This parameter shall contain the value of the PMO\_IND in the PACKET CELL CHANGE ORDER or PACKET MEASUREMENT ORDER messages that has modified the used Neighbour Cell list. If no such message has been received, PMO\_USED shall be set to zero. + +**BSIC\_Seen** (1 bit field) + +This parameter indicates if a GSM cell with invalid BSIC and allowed NCC part BSIC is one of the six strongest, see 3GPP TS 45.008. + +**Bit** + +- 0** No cell with invalid BSIC and allowed NCC part of BSIC is seen +- 1** One cell or more with invalid BSIC and allowed NCC part of BSIC is seen + +**SCALE** (1 bit field) + +The value of this field is defined in 3GPP TS 45.008. + +#### **Serving cell reporting** + +If the structure "serving cell data" is missing, this indicates that no valid measurement exist for the serving cell. + +**RXLEV\_SERVING\_CELL** (6 bit field) + +This field contains the value of the RXLEV parameter for the serving cell calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as the binary representation of the RXLEV parameter value defined in 3GPP TS 45.008. + +Range 0 to 63 + +#### **Neighbour cell reporting** + +##### ***Repeated Invalid BSIC*** + +This structure contains the report of cells with invalid BSIC. + +**BCCH-FREQ-NCELL** (5 bits). This field represents the index of the BA(GPRS), see 3GPP TS 44.018. + +**BSIC** (6 bits). Base station identity code of the corresponding index in the BA(GPRS). + +**RXLEV** (6 bits). GSM reporting quantity, see 3GPP TS 45.008. + +#### ***Bitmap type reporting:*** + +This structure contains the report of cells with valid BSIC. + +Each bit of the bitmap points to the corresponding index of the Neighbour Cell list defined in sub-clause 5.6.3.3 ("Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list"). + +If this structure is present and more bits than needed are available at the end of the message, the MS shall set the value of the redundant bitmap positions to '0'. + +At least 96 neighbour cell entries shall be encoded in the bitmap. + +If this structure is present, some remaining bits indicating no report at the end of the message may be omitted if these bits do not fit into the message. This shall not lead to an error in the receiver of that message. + +If E-UTRAN neighbour cells are to be reported, then this structure shall be omitted and replaced by the bitmap reporting structure in the release-8 extension of this message. + +**REPORTING\_QUANTITY** (6 bits): + +Measurement quantities are defined in 3GPP TS 45.008. + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in Iu mode . | +| E-UTRAN Neighbour cell reporting
BITMAP_LENGTH (7 bit field)
1+val(BITMAP_LENGTH) indicates the number of entries in the reporting bitmap.
Bitmap type reporting:
This structure contains the report of cells with valid BSIC.
Each bit of the bitmap points to the corresponding index of the Neighbour Cell list defined in sub-clause 5.6.3.3 ("Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list").
REPORTING_QUANTITY (6 bits):
Measurement quantities are defined in 3GPP TS 45.008. | +| E-UTRAN Measurement Report
This information element contains the measurement reports for one or more E-UTRAN neighbour cell. This field is defined in sub-clause 11.2.9. | +| UTRAN CSG Measurement Report
Measurement reporting for UTRAN CSG cells is defined in 3GPP TS 45.008. This information element contains the measurement results and routing parameters for one UTRAN CSG or hybrid cell. It is defined in sub-clause 12.61. | +| E-UTRAN CSG Measurement Report
Measurement reporting for E-UTRAN CSG cells is defined in 3GPP TS 45.008. This information element contains the measurement results and routing parameters for one E-UTRAN CSG or hybrid cell. It is defined in sub-clause 12.60. | +| SI23_BA_USED (1 bit field)
This field contains the value of the SI 23_BA_IND field in the SYSTEM INFORMATION TYPE 23 message defining the E-UTRAN Neighbour Cell list used. In the case SYSTEM INFORMATION TYPE 23 message is not broadcast in the cell or if the mobile station does not support network sharing this field shall be set to 0. Range 0 to 1. | + +### 11.2.9e Packet Neighbour Cell Data + +This optional message is sent by the network on the PACCH to provide system information required for initial access in a neighbouring cell. This message shall not be segmented across more than one RLC/MAC control block. If not all information fits into one instance of the PACKET NEIGHBOUR CELL DATA message, the message can be repeated. + +Message type: PACKET NEIGHBOUR CELL DATA + +Direction: network to mobile station + +Classification: non distribution message + +Table 11.2.9e.1: Packet Neighbour Cell Data information elements + +``` + +< Packet Neighbour Cell Data message content > ::= + < PAGE_MODE : bit (2) > + { 0 < Global TFI : < Global TFI IE > > + + { < CONTAINER_ID : bit (2) > + < spare : bit (1) > + < CONTAINER_INDEX : bit (5) > + { 0 | 1 < ARFCN : bit (10) > + < BSIC : bit (6) > } + < CONTAINER : < Container repetition struct > > + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + + < Container repetition struct > ::= + { + { < PD : bit (3) > + < CD_LENGTH : { bit (5) exclude 00000 exclude 11111 } > + < CONTAINER_DATA : octet (val(CD_LENGTH)) > -- Final container segment. Next container follows. + + | < PD : bit (3) > + < CD_LENGTH : { bit (5) == 11111 } > + < CONTAINER_DATA : octet ** > } ** -- Container continued in next message. + + { < spare bit (3) > -- Repetition of the container repetition struct continues until: + < CD_LENGTH : { bit (5) == 00000 } > } -- A) val(CD_LENGTH) = 0 or + } // -- B) end of PNCD message. + +``` + +Table 11.2.9e.2: Packet Neighbour Cell Data information element details + +The Packet Neighbour Cell Data message consists of up to 32 instances and contains neighbour cell system information messages from either the BCCH or from the PBCCH or from both. Each container repetition struct contains information from one or more SI/PSI message. One SI/PSI message can be distributed over more than one instance. + +A container may have the cell identity represented by the ARFCN and BSIC included. + +#### PAGE\_MODE (2 bit field) + +This field is defined in sub-clause 12.20 and gives the PAGE\_MODE parameter valid in the serving cell. + +#### Global TFI + +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +#### CONTAINER\_ID (2 bit field) + +This field contains the Container identity and shall have the same value in all instances to form a complete set of neighbour cell system information for a certain cell. + +Value range: 0-3. + +#### Spare (1 bit field) + +This bit is reserved for future use. + +#### CONTAINER\_INDEX (5 bit field) + +This field contains the message index within a complete set of neighbour cell system information for a certain cell + +Value range: 0-31. + +#### **ARFCN and BSIC** + +ARFCN and BSIC is optional, but if included their value shall be same in all instances forming a complete set. If not the same, the mobile station shall act as described in sub-clause 8.8.1. + +#### **ARFCN (10 bit field)** + +This field indicates the ARFCN of the BCCH of the neighbour cell for which the information contained in this message is valid for. This field is encoded as the ARFCN defined in 3GPP TS 44.018. + +Range 0 to 1023 + +#### **BSIC (6 bit field)** + +This field indicates the BSIC of the neighbour cell for which the information contained in this message is valid. + +This field is encoded as the BSIC value defined in 3GPP TS 44.018. + +Range 0 to 63 + +#### **PD (3 bit field)** + +This field contains a protocol discriminator and indicates the origin of the contained message. + +bit + +2 1 + +0 0 0 BCCH (LAPDm); + +0 0 1 PBCCH (RLC/MAC); + +0 1 0 Reserved; If received the contents of the container shall be discarded. + +..... + +1 1 1 Reserved; If received the contents of the container shall be discarded. + +#### **CD\_LENGTH (5 bit field)** + +This field indicates the number of CONTAINER DATA octets that forms a specific SI/PSI message and is coded as shown below. + +bit + +5 4 3 2 1 + +0 0 0 0 0 No CONTAINER DATA follows; Spare padding is used to fill the rest of the message; + +0 0 0 0 1 CONTAINER DATA length = 1 octet; + +..... + +1 0 0 1 0 CONTAINER DATA length = 18 octets; + +1 1 1 1 1 The remaining portion of the Packet Neighbour Cell Data message is used by the associated CONTAINER DATA. The message continues in a subsequent instance of the Packet Neighbour Cell Data message, in the next CONTAINER DATA with the same Protocol Discriminator value as the current one. + +All other values reserved. If a reserved value is received the contents of the container shall be discarded. + +#### **CONTAINER\_DATA(n\*8 bits)** + +The concatenation of one or several CONTAINER\_DATA octets forms the actual contents, specific to the SI/PSI messages. + +If the contained system information messages are copied from the BCCH the information contained in the Packet Neighbour Cell Data message shall exclude the following information elements from the beginning of the messages: L2 Pseudo Length; RR management Protocol Discriminator and Skip Indicator. + +If the contained system information messages are copied from the PBCCH the information contained in the Packet Neighbour Cell Data message shall include the complete PSI message. + +Extra octets of padding bits at the end of the SI/PSI messages may be excluded. + +### 11.2.10 Packet Paging Request + +This message is sent on the PCCH by the network to trigger channel access by up to four mobile stations, for either TBF or RR connection establishment. It may also be sent on PACCH to a mobile station in packet transfer mode to indicate page request for RR connection establishment. The mobile stations are identified by either IMSI, TMSI, P-TMSI or G-RNTI. Depending on the method used to identify the mobile station, 1 - 4 mobile stations can be addressed in the message. The PACKET PAGING REQUEST message may also be used to send MBMS (pre-)notifications. + +Special requirements for the transmission of this message on PACCH applies, see 3GPP TS 45.002. The PACKET PAGING REQUEST message may also be used to broadcast an ETWS Primary Notification message on the PCCCH. If not all information fits into one instance of the PACKET PAGING REQUEST message, the PACKET PAGING REQUEST message can be repeated. + +Message type: PACKET PAGING REQUEST + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.10.1: PACKET PAGING REQUEST message content** + +``` + +< Packet Paging Request message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } + { 0 | 1 < NLN(PPCH) : bit (2) > } + { 1 < Repeated Page info : < Repeated Page info struct > > } ** 0 + { null + | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- REL-5 additions: + { 1 < Repeated lu Page info : < Repeated lu Page info struct > > } ** 0 + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- REL-6 additions: + { 0 | 1 < MBMS Information > } + { 0 | 1 < NLN status(PPCH) : bit (1) > } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- REL-8 additions: + { 0 | 1 < ETWS Primary Notification : < ETWS Primary Notification struct > > } + < padding bits > > } } } // -- truncation at end of message allowed, bits '0' assumed +! < Distribution part error : bit (*) = < no string > > ; + +< Repeated Page info struct > ::= + { 0 -- Page request for TBF establishment + | 0 < PTMSI : bit (32) > + | 1 < Length of Mobile Identity contents : bit (4) > + < Mobile Identity : octet (val (Length of Mobile Identity contents)) > } + | 1 -- Page request for RR conn. establishment + { 0 < TMSI : bit (32) > + | 1 < Length of Mobile Identity contents : bit (4) > + < Mobile Identity : octet (val (Length of Mobile Identity contents)) > } + < CHANNEL_NEEDED : bit (2) > + { 0 | 1 < eMLPP_PRIORITY : bit (3) > } } +! < Ignore : bit (*) = < no string > > ; + +< Repeated lu Page info struct > ::= + { + | 0 < G-RNTI : bit(32) > -- used for a CN page to an MS in RRC connected mode, or a GERAN initiated page + | 0 | 1 < Page info struct : < Page info struct > > } -- only included for a CN page + | 1 + | 00 < TMSI : bit (32) > + | 01 < PTMSI : bit (32) > + | 11 { < Length of Mobile Identity contents : bit (4) > + < Mobile Identity : octet (val (Length of Mobile Identity contents)) > } + < Page info struct : < Page info struct > > } + { 0 | 1 < eMLPP_PRIORITY : bit (3) > } } +! < Ignore : bit (*) = < no string > > ; + +< MBMS Information > ::= + { + -- Pre-notifications + < MBMS Sessions List : < MBMS Sessions List IE > > + + -- Notifications: listed per MBMS Channel Parameters + { 1 < MBMS Channel Parameters : < MBMS Channel Parameters IE > > + < MBMS Sessions List : < MBMS Sessions List IE > > } ** 0 } } +! < Ignore : bit (*) = < no string > > ; + +< Page info struct > ::= + < PAGING CAUSE : bit (3) > + < CN DOMAIN IDENTITY : bit (2) > + { 0 | 1 < Paging Record Type Identifier : bit (2) > }; -- This field Is only included if the MS is paged using a G-RNTI + +``` + +``` + +< ETWS Primary Notification struct > ::= +{0 -- First segment of ETWS Primary Notification, number of segments included + < Total No Of Segments For ETWS Primary Notification : bit (4) > +| 1 -- Not first segment, segment number included + < Segment Number : bit (4) > +} +< PNI: bit (1) > -- identifier for segments belonging to one and the same ETWS Primary Notification message +< Length Of Segment : bit (7) > -- length of segment in bits +< ETWS Primary Notification Data : bit (val(Length of segment)) >; + +``` + +**Table 11.2.10.2: PACKET PAGING REQUEST information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

| +|

PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1...4)
This field is defined in sub-clause 12.14, PRACH Control Parameters.

| +|

NLN(PPCH) (2 bit field)
Notification List Number - This field may only be present if the message contains at least one page request for an RR connection establishment. The presence of the NLN(PPCH) field indicates that if an NCH is present, reduced NCH monitoring can be used, and gives the NLN(PPCH) value, to be used as specified in 3GPP TS 44.018. The field is coded as defined in the P1 Rest Octets information element in 3GPP TS 44.018.

NLN status(PPCH) (1 bit field)
Notification List Number status - This field may only be present if the message contains at least one page request for an RR connection establishment. The NLN status indicates the status of the content of the NOTIFICATION/NCH messages for a particular NLN value. A change of the NLN status field indicates a change of information on the NCH which is not related to new calls, as specified in 3GPP TS 44.018. The field is coded as defined in the P1 Rest Octets information element in 3GPP TS 44.018.

| +|

Repeated Page info struct
The Repeated Page info struct is repeated as many times as required to fulfil the number of wanted paged mobiles. If the Paging Request Message is used with only P-TMSIs or TMSIs, the field can be repeated up to four times within one message. If the Paging Request Message is used with only IMSIs, the field can be repeated up to two times within one message.

The first bit in the Repeated Page info field indicates if this is a page request for TBF connection establishment or for RR connection establishment.

A page request for TBF connection establishment can either be addressed with P-TMSI or IMSI.

A page request for RR connection establishment contains a Channel Needed and optionally a Priority parameter and can either be addressed with TMSI or IMSI.

| +|

PTMSI (32 bit field)
The Packet Temporary Mobile Station Identity (PTMSI) is defined in 3GPP TS 23.003. This field is encoded as a binary number.
Range 0 to 4294967295

| +|

Mobile Identity (variable length octet string)
This octet string is the representation of the Mobile Identity. It shall provide the international mobile subscriber identity, IMSI. The encoding of this octet string is the value part (starting with octet 3) of the type 4 information element Mobile Identity defined in 3GPP TS 44.018.

Any value other than IMSI for the type of identity in this octet string is spare. Such mobile identity shall be disregarded by the receiver but any further occurrence of the Repeated Page Info struct in the message shall be analysed.

| +|

TMSI (32 bit field)
TMSI is a unique Temporary Mobile Subscriber Identity. TMSI is associated with the mobile subscriber and defined in 3GPP TS 23.003. This field is coded as a binary number.
Range 0 to 4294967295

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

CHANNEL_NEEDED (2 bit field)

The channel needed field indicates which type of channel is needed for the mobile station for the transaction linked to the paging procedure. The field is coded according to following table:

bit
2 1
0 0 Any channel
0 1 SDCCH
1 0 TCH/F (Full rate)
1 1 TCH/H or TCH/F (Dual rate)
| bit | | 2 1 | | 0 0 | Any channel | 0 1 | SDCCH | 1 0 | TCH/F (Full rate) | 1 1 | TCH/H or TCH/F (Dual rate) | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | Any channel | | | | | | | | | | | | +| 0 1 | SDCCH | | | | | | | | | | | | +| 1 0 | TCH/F (Full rate) | | | | | | | | | | | | +| 1 1 | TCH/H or TCH/F (Dual rate) | | | | | | | | | | | | +|

eMLPP_PRIORITY (3 bit field)

The optional eMLPP_PRIORITY field relates to Mobile Station Identity i(i = 1, 2, 3, 4) and may only be present when the page relates to a paging request to trigger RR/RRC connection establishment. The eMLPP_PRIORITY field is coded as the Priority field defined in the P1 Rest Octets information element in 3GPP TS 44.018.

| | | | | | | | | | | | | +|

Repeated MBMS Notification info struct

The Repeated MBMS Notification info struct is repeated as many times as required to fulfil the number of wanted paged Temporary Mobile Groups.

The MBMS session identity is optional and shall be included whenever being made available in the MBMS-SESSION-START-REQUEST PDU or in the MBMS-SESSION-UPDATE-REQUEST PDU received from the SGSN.

If no counting should take place then a MBMS p-t-m channel description may be included.

If counting is requested then a MPRACH description may be included.

| | | | | | | | | | | | | +|

MBMS Sessions List

This information element contains a list of MBMS sessions identified by their TMGI and if available MBMS Session Identity. This information element is defined in sub-clause 12.39.

| | | | | | | | | | | | | +|

MBMS Channel Parameters

This information element contains the MBMS channel parameters of one or more MBMS sessions. This information element is defined in sub-clause 12.36.

| | | | | | | | | | | | | +|

Page info struct

This struct contains all information to be passed between RLC/MAC and RRC in the MS.

| | | | | | | | | | | | | +|

Repeated Iu_Page info struct

The Repeated Iu_Page info struct is repeated as many times as required to fulfil the number of wanted paged mobiles. If the PACKET PAGING REQUEST message is used with only P-TMSIs, TMSIs or G-RNTIs, the field can be repeated up to four times within one message. If the Paging Request Message is used with only IMSIs, the field can be repeated up to two times within one message.

| | | | | | | | | | | | | +|

G-RNTI (32 bits)

The G-RNTI field identifies the MS within GERAN when an RRC connection exists between this MS and GERAN.

| | | | | | | | | | | | | +|

PAGING RECORD TYPE IDENTIFIER (2 bits field)

The Paging Record Type Identifier field indicates the type of identity used in the core network page. This field shall be included in the message if the MS is identified in the page with a G-RNTI

bit
2 1
0 0 IMSI (GSM-MAP)
0 1 TMSI (GSM-MAP) / P-TMSI
1 0 IMSI (DS-41)
1 1 TMSI (DS-41)
| bit | | 2 1 | | 0 0 | IMSI (GSM-MAP) | 0 1 | TMSI (GSM-MAP) / P-TMSI | 1 0 | IMSI (DS-41) | 1 1 | TMSI (DS-41) | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | IMSI (GSM-MAP) | | | | | | | | | | | | +| 0 1 | TMSI (GSM-MAP) / P-TMSI | | | | | | | | | | | | +| 1 0 | IMSI (DS-41) | | | | | | | | | | | | +| 1 1 | TMSI (DS-41) | | | | | | | | | | | | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

CN DOMAIN IDENTITY (2 bit field)
The CN Domain Identity field indicates the domain of the core network from which the MS is paged.

 Bit 2 1 0 0    CS domain 0 1    PS domain 1 0    Either 1 1    Reserved
| +|

PAGING CAUSE (3 bits field)
The Paging Cause field indicates the cause for paging.

 bit 3 2 1 0 0 0    Terminating Conversational Call 0 0 1    Terminating Streaming Call 0 1 0    Terminating Interactive Call 0 1 1    Terminating Background Call 1 0 0    Terminating High Priority Signalling 1 0 1    Terminating Low Priority Signalling 1 1 0    Terminating - cause unknown 1 1 1    Reserved
| +|

Total No Of Segments For ETWS Primary Notification (4 bits)
This field contains the number of segments for the ETWS Primary Notification message.

 Bits 4 3 2 1 0 0 0 0    reserved 0 0 0 1    one segment 0 0 1 0    two segments . . .  1 1 1 1    fifteen segments
| +|

Segment Number (4 bits)
This field contains the Segment Number of the ETWS Primary Notification message.

 Bits 4 3 2 1 0 0 0 0    reserved 0 0 0 1    reserved 0 0 1 0    second segment 0 0 1 1    third segment . . .  1 1 1 1    fifteenth segment
| +|

PNI, Primary Notification Identifier (1 bit)
This field is used as an identifier to determine the set of segments belonging to a certain ETWS Primary Notification message. This information element will have the same value (0 or 1) for all segments belonging to the same ETWS Primary Notification message.

| +|

Length Of Segment (7 bits)
This field indicates the length of a segment in number of bits.

| +|

ETWS Primary Notification Data (n*8 bits)
The ETWS Primary Notification data is coded as specified in 3GPP TS 23.041.

| + +### 11.2.11 Packet PDCH Release + +This message is sent on PACCH by the network to notify all mobile stations listening to that PDCH that one or more PDCHs will be immediately released and become unavailable for packet data traffic. + +Message type: PACKET PDCH RELEASE + Direction: network to mobile station + Classification: distribution message + +**Table 11.2.11.1: PACKET PDCH RELEASE information elements** + +``` +< Packet PDCH Release message content > ::= + < PAGE_MODE : bit (2) > + { 1 < TIMESLOTS_AVAILABLE : bit (8) > } + < padding bits > + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.11.2: PACKET PDCH RELEASE information element details** + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **TIMESLOTS\_AVAILABLE** (8 bit field) + +This information field indicates the timeslots assigned for GPRS use on the current MAIO or ARFCN. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. + +- 0 Timeslot is not assigned +- 1 Timeslot is assigned + +NOTE: If the bit preceding the parameter TIMESLOTS\_AVAILABLE is received = 0 a distribution part error should be generated by the mobile station. To allow compatibility with early GPRS mobile stations in Release 97 such mobile stations may interpret this message, if received with the bit preceding the parameter TIMESLOTS\_AVAILABLE equal to 0, as a command to release the timeslot on which the message was received. + +### 11.2.12 Packet Polling Request + +This message is sent on the PCCCH or PACCH by the network to the mobile station to solicit a PACKET CONTROL ACKNOWLEDGEMENT message from the mobile station. + +Message type: PACKET POLLING REQUEST + Direction: network to mobile station + Classification: non-distribution message + +**Table 11.2.12.1: PACKET POLLING REQUEST information elements** + +``` +< Packet Polling Request message content > ::= + < PAGE_MODE : bit (2) > + { 0 < Global TFI : < Global TFI IE > > + | 10 < TLLI / G-RNTI : bit (32) > + | 110 < TQI : bit (16) > } + { < TYPE_OF_ACK : bit (1) > + { null | 0 bit ** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5 : + { 0 | 1 < G-RNTI extension : bit (4) > } + < padding bits > } + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.12.2: PACKET POLLING REQUEST information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20. | +| TQI (16 bit field)
This field is defined in sub-clause 12.17. | +| TLLI / G-RNTI (32 bit field)
This field is defined in sub-clause 12.16. | +| Global TFI
This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. | +| TYPE_OF_ACK
This field indicates the format of the PACKET CONTROL ACKNOWLEDGEMENT message requested from the mobile station by the PACKET POLLING REQUEST message.

0 PACKET CONTROL ACKNOWLEDGEMENT message format shall be sent as four access bursts
1 PACKET CONTROL ACKNOWLEDGEMENT message format shall be an RLC/MAC control block | +| G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier in Iu mode . | + +### 11.2.13 Packet Power Control/Timing Advance + +This message is sent on PACCH by the network to the mobile station in order to update the mobile station timing advance or power control parameters. + +Message type: PACKET POWER CONTROL/TIMING ADVANCE + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.13.1: PACKET POWER CONTROL/TIMING ADVANCE information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < Packet Power Control/Timing Advance message content > ::=   < PAGE_MODE : bit (2) >   { 0 < Global TFI : < Global TFI IE > >     { 0    -- Message escape       { { 0   1 < Global Power Control Parameters : < Global Power Control Parameters IE > > }         { 0 < Global Packet Timing Advance : < Global Packet Timing Advance IE > >             < Power Control Parameters : < Power Control Parameters IE > >             1 { 0 < Global Packet Timing Advance : < Global Packet Timing Advance IE > >                 1 < Power Control Parameters : < Power Control Parameters IE > > } }         { null   0 bit** = < no string > -- Receiver backward compatible with earlier version             1    -- Additions for R99             { 0   1 < Packet Extended Timing Advance : bit (2) > }             { null   0 bit** = < no string > -- Receiver backward compatible with earlier version                 1    -- Additions for REL-7                 { 0   1 < Carrier Identification : bit (2) > }                 { null   0 bit** = < no string > -- Receiver backward compatible with earlier version                     1    -- Additions for REL-12                     { 0   1 < Carrier Count : bit (4) >                         < DLMC Carrier Bitmap : bit (val(Carrier Count) + 1) > }   < padding bits > } } }   ! < Non-distribution part error : bit (*) = < no string > > }   ! < Message escape : 1 bit (*) = < no string > > }   ! < Address information part error : bit (*) = < no string > > }   ! < Distribution part error : bit (*) = < no string > > ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.13.2: PACKET POWER CONTROL/TIMING ADVANCE information element details** + +| | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|--|-----|---------------------------------------------------|-----|-----------------------------------------------|-----|-----------------------------------------------|-----|-------------------------|---|-------------------------------------------------|---|---------------------------------------------| +|

Global Power Control Parameters IE
This information field is defined in sub-clause 12.9.

Global_Packet Timing Advance IE
This information field is defined in sub-clause 12.12a.

Power Control Parameters IE
This information element contains the power control parameters the mobile station shall use to determine its TX power level. If this information element does not include the updated power control parameters for some of currently assigned timeslots, the MS shall continue to use the current power control parameters for these timeslots. This information field is defined in sub-clause 12.13.

Global TFI IE
This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10.

Packet Extended Timing Advance (2 bit field)
This field is defined in sub-clause 12.12b.

| | | | | | | | | | | | | | | +|

Carrier Identification (2 bit field)
This field identifies the carrier to which the Power Control Parameters refers.

bit
0 0 Power Control Parameters applies to both carriers
0 1 Power Control Parameters applies to carrier 1
1 0 Power Control Parameters applies to carrier 2
1 1 Reserved for future use

DLMC Carrier Bitmap (1 - 16 bit field)
This field identifies the carrier(s) to which the Power Control Parameters are applicable for a DLMC configuration. In the absence of this field the MS shall assume the Power Control Parameters applies to all downlink carriers assigned for the DLMC configuration.

The most significant bit of this bitmap (bit N) refers to the lowest number carrier in the DLMC configuration and the least significant bit of this bitmap (bit 1) refers to the highest number carrier in the DLMC configuration. Each bit position in this bitmap is coded as follows:

0 The Power Control Parameters are not applicable
1 The Power Control Parameters are applicable
| bit | | 0 0 | Power Control Parameters applies to both carriers | 0 1 | Power Control Parameters applies to carrier 1 | 1 0 | Power Control Parameters applies to carrier 2 | 1 1 | Reserved for future use | 0 | The Power Control Parameters are not applicable | 1 | The Power Control Parameters are applicable | +| bit | | | | | | | | | | | | | | | +| 0 0 | Power Control Parameters applies to both carriers | | | | | | | | | | | | | | +| 0 1 | Power Control Parameters applies to carrier 1 | | | | | | | | | | | | | | +| 1 0 | Power Control Parameters applies to carrier 2 | | | | | | | | | | | | | | +| 1 1 | Reserved for future use | | | | | | | | | | | | | | +| 0 | The Power Control Parameters are not applicable | | | | | | | | | | | | | | +| 1 | The Power Control Parameters are applicable | | | | | | | | | | | | | | + +### 11.2.14 Packet PRACH Parameters + +This message is sent on the PCCH by the network to all mobile stations within the cell to update the PRACH parameters in between Packet System Information messages containing PRACH parameters. + +Message type: PACKET PRACH PARAMETERS + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.14.1: PACKET PRACH PARAMETERS information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Packet PRACH Parameters message content > ::=   < PAGE_MODE : bit (2) >   < PRACH Control Parameters : < PRACH Control Parameters IE > >   < padding bits >   ! < Distribution part error : bit (*) = < no string > > ;
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.14.2: PACKET PRACH PARAMETERS information element details** + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **PRACH Control Parameters** + +This information element is defined in sub-clause 12.14. + +### 11.2.15 Packet Queueing Notification + +This message is sent on the PCCH by the network to the mobile station to notify the mobile station that it is being placed in queue. The message allocates a Temporary Queueing Identity to the mobile station. + +Message type: PACKET QUEUING NOTIFICATION + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.15.1: PACKET QUEUING NOTIFICATION information elements** + +``` +< Packet Queueing Notification message content > ::= + < PAGE_MODE : bit (2) > + { 111 < Packet Request Reference : < Packet Request Reference IE > > + { < TQI : bit (16) > + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.15.2: PACKET QUEUING NOTIFICATION information element details** + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **Packet Request Reference** + +This information element is defined in sub-clause 12.11. + +#### **TQI** (16 bit field) + +This information field is defined in sub-clause 12.17. + +### 11.2.16 Packet Resource Request + +This message is sent on the PACCH by the mobile station to the network to request a change in the uplink resources assigned. + +Message type: PACKET RESOURCE REQUEST + +Direction: mobile station to network + +Table 11.2.16.1: PACKET RESOURCE REQUEST information elements + +``` + +< Packet Resource Request message content > ::= +{ 0 | 1 < ACCESS_TYPE : bit (2) > } +{ 0 | 1 < Global TFI : < Global TFI IE > > + | 1 < TLLI / G-RNTI : < TLLI / G-RNTI IE > > } +{ 0 | 1 < MS Radio Access Capability 2 : < MS Radio Access Capability 2 IE > > } +< Channel Request Description : < Channel Request Description IE > > +{ 0 | 1 < CHANGE_MARK : bit (2) > } +< C_VALUE : bit (6) > +{ 0 | 1 < SIGN_VAR : bit (6) > } +{ 0 | 1 < I_LEVEL_TN0 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN1 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN2 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN3 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN4 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN5 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN6 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN7 : bit (4) > } +{ null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 1999 + { 0 | 1 < EGPRS BEP Link Quality Measurements : + < EGPRS BEP Link Quality Measurements IE > > } + { 0 | 1 < EGPRS Timeslot Link Quality Measurements : + < EGPRS Timeslot Link Quality Measurements IE > > } + { 0 | 1 < PFI : bit(7) > } + < ADDITIONAL MS RAC INFORMATION AVAILABLE : bit (1) > + < RETRANSMISSION OF PRR : bit (1) > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-5 + { 0 | 1 { 0 | 1 < G-RNTI extension : bit (4) > } + < lu mode Channel Request Description : < lu mode Channel Request Description IE > > } + { 0 | 1 < HFN_LSB : bit (1) > } + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 6 + { 0 | 1 < Extended Channel Request Description : + < Extended Channel Request Description IE > > } + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 7 + < EARLY_TBF_ESTABLISHMENT : bit (1) > + { 0 | 1 < EGPRS BEP Link Quality Measurements Type 2 : + < EGPRS BEP Link Quality Measurements Type 2 IE > > } + { 0 | 1 < EGPRS Timeslot Link Quality Measurements Type 2 : + < EGPRS Timeslot Link Quality Measurements Type 2 IE > > } + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additional contents for Release 10 + < Low Access Priority Signalling : bit (1) > + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-12 + { 0 | 1 < Downlink_eTFI : bit (3) > } + } + } + } + } + } +< padding bits > } } } } } + +``` + +Table 11.2.16.2: PACKET RESOURCE REQUEST information element details + +#### **Global TFI** + +This information element contains (one of) the TFI of the mobile station's uplink TBF, if available, or (one of) the TFI of the mobile station's downlink TBF. If no TFI is available, this field is omitted. This field is defined in sub-clause 12.10. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------------------------|---|---|---|-------------------------------------------------|---|---|---------------|---|---|-------------|---|------------------------------------------|-------------------------------|---|---|---|---|---|-----------------------------------------------|---|---|---|---|---|---|-----------------------------------------------|-------|--|--|--|--|--|--|---|---|---|---|---|---|-------------------------------------------------|---|---|---|---|---|---|------------------------| +|

ACCESS_TYPE (2 bit field)

This field indicates the reason for requesting the access. It shall be included only in response to a single block or Multi block assignment.

bit

2 1
0 0 Two Phase Access Request
0 1 Page Response
1 0 Cell Update
1 1 Mobility Management procedure
| 2 | 1 | | 0 | 0 | Two Phase Access Request | 0 | 1 | Page Response | 1 | 0 | Cell Update | 1 | 1 | Mobility Management procedure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | Two Phase Access Request | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | Page Response | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | Cell Update | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | Mobility Management procedure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

TLLI / G-RNTI

This information element is defined in sub-clause 12.16.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MS Radio Access Capability 2

This information element is defined in sub-clause 12.30. This information element is sent only during two phase access and shall not be include by MS operating in Iu mode. Additionally, this information element shall be sent in one phase EGPRS TBF establishment procedure if ordered by the network.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Channel Request Description

This information element is defined in sub-clause 12.7. If a PFI field is included in this message, it relates to the TBF request contained in the Channel Request Description IE. If the Extended Channel Request Description IE is included in this message, the value of this IE (and the PFI field) shall be ignored. When a PACKET RESOURCE REQUEST message is sent in response to an Access Technologies Request received by the MS during a one phase access this IE shall be ignored.

Extended Channel Request Description

This information element is defined in sub-clause 12.7b. This IE contains a request for one or more additional uplink TBFs and shall only be included if the mobile station and the network support multiple TBF procedures. If this IE is included, the Channel Request Description IE and PFI field in the message shall be ignored.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

CHANGE_MARK (2 bit field)

This field contains the PSI2_CHANGE_MARK value stored by the mobile station's if PBCCH is present in the current cell. If PBCCH is not present in the current cell, this field contains the SI13_CHANGE_MARK value stored by the mobile station. If the mobile station does not have a valid PSI2 or SI13 change mark for the current cell, the mobile station shall omit this field. The coding of this field is network dependent.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

C_VALUE (6 bit field)

This field is encoded as the binary representation of the C value as specified in 3GPP TS 45.008. Range 0 to 63

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

SIGN_VAR (6 bits)

This field contains the signal variance parameter SIGN_VAR calculated by the mobile station (see 3GPP TS 45.008). This field is not present for TBF establishment using two phase access or for a TBF in EGPRS mode.

bit

6 5 4 3 2 1
0 0 0 0 0 0 0dB2 to 0.25 dB2
0 0 0 0 0 1 >0.25 dB2 to 0.50 dB2
0 0 0 0 1 0 >0.50 dB2 to 0.75 dB2
: : :
1 1 1 1 1 0 >15.50 dB2 to 15.75 dB2
1 1 1 1 1 1 >15.75 dB2
| 6 | 5 | 4 | 3 | 2 | 1 | | 0 | 0 | 0 | 0 | 0 | 0 | 0dB 2 to 0.25 dB 2 | 0 | 0 | 0 | 0 | 0 | 1 | >0.25 dB 2 to 0.50 dB 2 | 0 | 0 | 0 | 0 | 1 | 0 | >0.50 dB 2 to 0.75 dB 2 | : : : | | | | | | | 1 | 1 | 1 | 1 | 1 | 0 | >15.50 dB 2 to 15.75 dB 2 | 1 | 1 | 1 | 1 | 1 | 1 | >15.75 dB 2 | +| 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0dB 2 to 0.25 dB 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | 1 | >0.25 dB 2 to 0.50 dB 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 0 | 1 | 0 | >0.50 dB 2 to 0.75 dB 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : : : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 1 | 1 | 1 | 0 | >15.50 dB 2 to 15.75 dB 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 1 | 1 | 1 | 1 | >15.75 dB 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| I_LEVEL_TN0 (4 bit field)
I_LEVEL_TN1 (4 bit field)
I_LEVEL_TN2 (4 bit field)
I_LEVEL_TN3 (4 bit field)
I_LEVEL_TN4 (4 bit field)
I_LEVEL_TN5 (4 bit field)
I_LEVEL_TN6 (4 bit field)
I_LEVEL_TN7 (4 bit field)
For element definition see sub-clause 11.2.6 - Packet Downlink Ack/Nack. These fields shall not be present if they are included in the EGPRS Timeslot Link Quality Measurements IE. | +| EGPRS BEP Link Quality Measurements
This information element is defined in sub-clause 12.5.3. This IE is transferred if it is available and if it would not cause the message to expand beyond one RLC/MAC control block and if the PACKET RESOURCE REQUEST is sent during on-going concurrent EGPRS TBF. | +| EGPRS Timeslot Link Quality Measurements
This information element is defined in sub-clause 12.5.4. This IE is transferred if it is available and if it would not cause the message to expand beyond one RLC/MAC control block and if the PACKET RESOURCE REQUEST is sent during on-going concurrent EGPRS TBF. | +| PFI (7 bit field)
This field contains the PFI parameter identifying a Packet Flow Context relating to the resource request specified in the Channel Request Description IE. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. This field may be included if the network supports packet flow context procedures. If the Extended Channel Request Description IE is included in this message, the value of this field (and the Channel Request Description IE) shall be ignored. | +| ADDITIONAL MS RAC INFORMATION AVAILABLE (1 bit field)
0 indicates that the MS will not send more information about its radio access capabilities than included in this message
1 indicates that the MS will provide more information about its radio access capabilities by sending an ADDITIONAL MS RADIO ACCESS CAPABILITIES message, either in the next radio block allocated to the mobile station on the assigned PDCH, or upon a further request from the network if the mobile station was allocated only one radio block. This value shall not be used by MS operating in Iu mode . | +| RETRANSMISSION OF PRR (1 bit field)
This field indicates whether the corresponding PACKET RESOURCE REQUEST message is a retransmission. In case the PACKET RESOURCE REQUEST message is a retransmission, the message content (except this field and the address information) shall be identical to the PACKET RESOURCE REQUEST message previously sent (see sub-clause 7.1.2.2.1a).

0 indicates that this message is an initial PACKET RESOURCE REQUEST message
1 indicates that this message is a retransmitted PACKET RESOURCE REQUEST message; in this case the corresponding PACKET RESOURCE REQUEST message shall not be interpreted as a request for resource reassignment. | +| G-RNTI extension (4 bit field)

This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier for contention resolution in Iu-mode . | +| HFN_LSB (1 bit field)
This field contains the least significant bit of the uplink HFN of the radio bearer for which the TBF is requested. | +| EARLY_TBF_ESTABLISHMENT (1 bit field)
This field indicates whether or not the packet resource request is meant to request pre-allocation of an uplink TBF:

0 The packet resource request is not meant to pre-allocate an uplink TBF.
1 The packet resource request is meant to pre-allocate an uplink TBF. | + +**EGPRS BEP Link Quality Measurements Type 2** + +This information element is defined in sub-clause 12.5a.2. This IE is transferred if it is available and if it would not cause the message to expand beyond one RLC/MAC control block and if the PACKET RESOURCE REQUEST is sent during on-going concurrent EGPRS2 TBF. + +--- + +**EGPRS Timeslot Link Quality Measurements Type 2** + +This information element is defined in sub-clause 12.5a.3. This IE is transferred if it is available and if it would not cause the message to expand beyond one RLC/MAC control block and if the PACKET RESOURCE REQUEST is sent during on-going concurrent EGPRS2 TBF. + +--- + +**Low Access Priority Signalling** + +This field allows a mobile station to indicate whether it is requesting a packet access for the purpose of *NAS signalling low priority* (see sub-clause 7.1.3.1). + +0 Indicates the PACKET RESOURCE REQUEST message is sent for requesting a packet access for a different purpose than *NAS signalling low priority* + +1 Indicates the PACKET RESOURCE REQUEST message is sent for requesting a packet access for the purpose of *NAS signalling low priority* + +--- + +**DOWNLINK\_eTFI (3 bit field)** + +See sub-clause 11.2.48 + +### 11.2.17 Packet PSI Status + +This message is sent on the PACCH from the mobile station to the network to indicate which PSI messages the mobile station has received. + +Message type: PACKET PSI STATUS + +Direction: mobile station to network + +**Table 11.2.17.1: PACKET PSI STATUS information elements** + +``` +< Packet PSI Status message content > ::= + < GLOBAL_TFI : < Global TFI IE > > + < PBCCH_CHANGE_MARK : bit (3) > + < Received PSI Message List : < PSI Message List struct > > + < Received Unknown PSI Message List : < Unknown PSI Message List struct > > + + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-6 : + < PS_REL_REQ : bit > + < padding bits > } ; + + < PSI Message List struct > ::= + { 1 < MESSAGE_TYPE : bit (6) > + < PSIX_CHANGE_MARK : bit (2) > + { 0 | 1 < PSIX_COUNT : bit (4) > + < Instance bitmap : bit (val(PSIX_COUNT) + 1) > } } ** 0 + < ADDITIONAL_MSG_TYPE : bit > ; + + < Unknown PSI Message List struct > ::= + { 1 < MESSAGE_TYPE : bit (6) > } ** 0 + < ADDITIONAL_MSG_TYPE : bit > ; +``` + +**Table 11.2.17.2: PACKET PSI STATUS information element details** + +#### **Global TFI (information element)** This information element contains the TFI of the mobile station's uplink or downlink TBF.. The coding of this information element is defined in sub-clause 12.10. + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PBCCH_CHANGE_MARK (3 bit field)

This field is the binary representation of the last PBCCH_CHANGE_MARK received in the PSI1 message on PBCCH.

| +|

Received PSI Message List (construction)

This construction contains a list of supported PSI messages (see sub-clause 5.5.1.4.3). The sender of this message may indicate as many messages in this list as can be fit into the message. Messages are listed by message type in descending order of priority. If there are more PSI messages than can be indicated in this list, the presence of additional message type(s) shall be indicated at the end of the list.

If the sender of this message has received a PSI message which is part of a consistent set of PSI messages (see 5.5.2.1.4), the Instance Bitmap may indicate which instances of this message type that have been received.

Under certain circumstances, see sub-clause 5.5.1.4.3, the sender of this message may use this construction to indicate the message type of a PSI message that has not been received. In that case, the corresponding Instance Bitmap field shall be included. The PSIX_CHANGE_MARK field, PSIX_COUNT field and the one element of the Instance Bitmap field shall all be set to the value '0'.

| +|

Received Unknown PSI Message List (construction)

This construction contains a list of message types that are received on PBCCH, which are either unknown or not recognized as supported PSI message types. The sender of this message may indicate as many messages in this list as can be fit into the message following the Received PSI Message List. Messages are listed by message type in the inverse order of reception, starting with the most recently received message type. If there are more messages than can be indicated in this list, the presence of additional message type(s) shall be indicated at the end of the list.

| +|

MESSAGE_TYPE (6 bit field)

This field is the binary representation of the message type (see sub-clause 11.2.0.1).

| +|

PSIX_CHANGE_MARK (2 bit field)

This field is the binary representation of the PSI change mark parameter received for a certain PSI message type. Range: 0 to 3.

| +|

PSIX_COUNT (4 bit field)

This field is the binary representation of the PSI count parameter received for a certain PSI message type. This field indicates the length of the corresponding Instance bitmap field and shall be provided only if the corresponding Instance bitmap field is provided in the message. Range: 0 to 7 or 0 to 15, depending on message type.

| +|

Instance bitmap (1 - 16 bit field)

This field is a bitmap indicating which instances of a certain message type that are received within a consistent set of PSI messages. This field shall be included when a sub-set of these messages has been received. This field shall not be included when the complete set of these messages has been received.

The most significant bit of this bitmap (bit N) refers to the message instance with the PSI index parameter = N-1, where N is the number of instances of the particular message type (PSI count + 1). The least significant bit of this bitmap (bit 1) refers to the message instance with the PSI index parameter = 0. Each bit position is coded:

0 Message instance is not received;
1 Message instance is received.

| +|

ADDITIONAL_MSG_TYPE (1 bit field)

0 No additional message type is present.
1 Additional message type(s) are available, but this information does not fit into the message.

| +|

PS_REL_REQ (1 bit field)

This field indicates whether the mobile station requests the release of the RR connection and packet resources. This field may only be set to "1" in certain cases, see 3GPP TS 44.018. This field shall always be present in the message when the enhanced DTM CS release procedure is ongoing.

0 The mobile station does not request the release of the RR connection and packet resources.
1 The mobile station requests the release of the RR connection and packet resources.

| + +#### 11.2.17a Packet Serving Cell Data + +This optional message is sent by the network on the PACCH to provide system information broadcast on the BCCH (respectively PBCCH) to a mobile station. For example, several instances of this message may be sent by the network in a cell supporting PACKET SI STATUS (respectively PACKET PSI STATUS) following the request for acquisition of system information by a mobile station. This message shall not be segmented across more than one RLC/MAC control block. If not all information fits into one instance of the PACKET SERVING CELL DATA message, the message can be repeated. + +Message type: PACKET SERVING CELL DATA + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.17a.1: Packet Serving Cell Data information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Packet Serving Cell Data message content > ::=    < PAGE_MODE : bit (2) >   { 0 < Global TFI : < Global TFI IE > >     { < spare : bit (4) >       < CONTAINER_INDEX : bit (5) >       < CONTAINER : < Container repetition struct > >       < padding bits >       ! < Non-distribution part error : bit (*) = < no string > > }     ! < Address information part error : bit (*) = < no string > > }   ! < Distribution part error : bit (*) = < no string > ;   < Container repetition struct > ::=   {     { < PD : bit (3) >       < CD_LENGTH : { bit (5) exclude 00000 exclude 11111 } >       < CONTAINER_DATA : octet (val(CD_LENGTH)) > -- Final container segment. Next container follows.              < PD : bit (3) >       < CD_LENGTH : { bit (5) == 11111 } >       < CONTAINER_DATA : octet ** > } ** -- Container continued in next message.      { < spare bit (3) >       < CD_LENGTH : { bit (5) == 00000 } > } -- Repetition continues until:                                              -- A) val(CD_LENGTH) = 0 or                                              -- B) end of PSCD message.   } // ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.17a.2: Packet Serving Cell Data information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

The Packet Serving Cell Data message consists of up to 32 instances and contains serving cell system information messages from the BCCH or from the PBCCH or from both. Each container repetition struct contains information from one or more SI/PSI message. One SI/PSI message can be distributed over more than one instance.

A container can only refer to the serving cell.

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

Global TFI
This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10.

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

PD (3 bit field)
This field contains a protocol discriminator and indicates the origin of the contained message.

Bit
2 1
0 0 0    BCCH (LAPDm);
0 0 1    PBCCH (RLC/MAC);
0 1 0    Reserved; If received the contents of the container shall be discarded.
......
1 1 1    Reserved; If received the contents of the container shall be discarded.

| +|

CD_LENGTH (5 bit field)
This field indicates the number of CONTAINER DATA octets that forms a specific SI/PSI message and is coded as shown below.

Bit
5 4 3 2 1
0 0 0 0 0    No CONTAINER DATA follows; Spare padding is used to fill the rest of the message;
0 0 0 0 1    CONTAINER DATA length = 1 octet;
....
1 0 0 1 0    CONTAINER DATA length = 18 octets;
1 1 1 1 1    The remaining portion of the Packet Serving Cell Data message is used by the associated CONTAINER DATA. The message continues in a subsequent instance of the Packet Serving Cell Data message, in the next CONTAINER DATA with the same Protocol Discriminator value as the current one.
All other values reserved. If a reserved value is received the contents of the container shall be discarded.

| +|

CONTAINER_DATA(n*8 bits)

The concatenation of one or several CONTAINER_DATA octets forms the actual contents, specific to the SI/PSI messages.

If the contained system information messages are copied from the BCCH the information contained in the Packet Serving Cell Data message shall exclude the following information elements from the beginning of the messages: L2 Pseudo Length; RR management Protocol Discriminator and Skip Indicator.
If the contained system information messages are copied from the PBCCH the information contained in the Packet Serving Cell Data message shall include the complete PSI message.

Extra octets of padding bits at the end of the SI/PSI messages may be excluded.

| + +### 11.2.17b Packet SI Status + +This message is sent on the PACCH from the mobile station to the network to indicate which SI messages the mobile station has received. + +Message type:   PACKET SI STATUS +Direction:          mobile station to network + +Table 11.2.17b.1: PACKET SI STATUS information elements + +``` + +< Packet SI Status message content > ::= + < GLOBAL_TFI : < Global TFI IE > > + < BCCH_CHANGE_MARK : bit (3) > + < Received SI Message List : < SI Message List struct > > + < Received Unknown SI Message List : < Unknown SI Message List struct > > + + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for REL-6 : + < PSCSI_SUPPORT : bit > + < PS_REL_REQ : bit > + < padding bits > } ; +< SI Message List struct > ::= + { 1 < SI_MESSAGE_TYPE : bit (8) > + { < MESS_REC : bit (2) == 00 > < null > -- Message type supported but not received + | < MESS_REC : bit (2) == 01 > < null > -- Message type supported and received, single instance + | < MESS_REC : bit (2) == 10 > -- Message type supported and partially received, multiple instances + < SIX_CHANGE_MARK : bit (3) > + < SIX_COUNT : bit (4) > + < Instance bitmap : bit (val(SIX_COUNT) + 1) > + | < MESS_REC : bit (2) == 11 > -- Message type supported and completely received, multiple instances + < SIX_CHANGE_MARK : bit (3) > } + } ** 0 + < ADDITIONAL_MSG_TYPE : bit > ; +< Unknown SI Message List struct > ::= + { 1 < SI_MESSAGE_TYPE : bit (8) > } ** 0 + < ADDITIONAL_MSG_TYPE : bit > ; + +``` + +Table 11.2.17b.2: PACKET SI STATUS information element details + +#### **Global TFI** (information element) + +This information element contains the TFI of the mobile station's uplink or downlink TBF. The coding of this information element is defined in sub-clause 12.10. + +#### **BCCH\_CHANGE\_MARK** (3 bit field) + +This field is the binary representation of the last BCCH\_CHANGE\_MARK received in the SI13 message on BCCH or PACCH. + +##### **Received SI Message List** (construction) + +This construction contains a list of supported SI messages (see sub-clause 5.5.1.4.3). The sender of this message may indicate as many messages in this list as can be fit into the message. Messages are listed by message type in descending order of priority. If there are more SI messages than can be indicated in this list, the presence of additional message type(s) shall be indicated at the end of the list. + +If the sender of this message has received an SI message which is part of a consistent set of SI messages (see sub-clause 5.5.2.1.4), the Instance Bitmap may indicate which instances of this message type that have been received. + +##### **Received Unknown SI Message List** (construction) + +This construction contains a list of message types that are received on BCCH, which are either unknown or not recognised as supported SI message types. The sender of this message may indicate as many messages in this list as can be fit into the message following the Received SI Message List. Messages are listed by message type in the inverse order of reception, starting with the most recently received message type. If there are more messages than can be indicated in this list, the presence of additional message type(s) shall be indicated at the end of the list. + +#### **SI\_MESSAGE\_TYPE** (8 bit field) + +This field is the binary representation of the message type of the indicated SI message (see 3GPP TS 24.007 and 3GPP TS 44.018). + +#### **MESS\_REC** (2 bit field) + +This field indicates for each message type that is supported by the mobile station whether one or more instances of the message have been received. The field is coded: + +Bit + +2 1 + +0 0 The message type is supported but not received; + +0 1 The message type is supported and received; this type of SI message does not exist in multiple instances; + +1 0 The message type is supported and instances of the message with the indicated change mark are partially received; + +1 1 The message type is supported and all instances of the message are received with the indicated change mark. + +#### **SIX\_CHANGE\_MARK** (3 bit field) + +This field is the binary representation of the SI change mark parameter received for a certain SI message type, except for the SI2ter, the SI2quater and the SI15 message types. For the SI2ter, SI2n,, SI18, SI19 and SI20 messages, the range is: 0 to 3. For the SI2quater and SI15 messages, the range is: 0 to 7. + +For the SI2ter message type, the three bits are used according to the following principles: + +SI2ter + +Bit + +3 2 1 + +0 - X Bit 1: SI2ter\_3G\_CHANGE\_MARK + +0 X - Bit 2: SI2ter\_MP\_CHANGE\_MARK. + +For the SI2quater message type, the mobile station shall include the latest received values of the BA\_IND, 3G\_BA\_IND and MP\_CHANGE\_MARK fields. The field is coded as follows: + +Bit + +3 2 1 + +- - X Bit 1: MP\_CHANGE\_MARK + +- X - Bit 2: 3G\_BA\_IND + +X - - Bit 3: BA\_IND + +For the SI15 message type, the mobile station shall include the three least significant bits of the DM\_CHANGE\_MARK parameter (i.e., DM\_CHANGE\_MARK modulo 8). + +#### **SIX\_COUNT** (4 bit field) + +This field is the binary representation of the SI *count* parameter received for a certain SI message type. This field indicates the length of the corresponding *Instance bitmap* field and shall be provided only if the corresponding *Instance bitmap* field is provided in the message. + +For SI18, SI19 and SI20 messages, this field shall be set to 7 if present. + +For the SI15 message the range is 0 to 3. + +For the SI2ter message the range is 0 to 7. + +For the SI2quater message the range is 0 to 15. + +For the SI2n message the range is 0 to 15. + +#### **Instance bitmap** (1 - 16 bit field) + +This field is a bitmap indicating which instances of a certain message type that are received within a consistent set of SI messages. This field shall be included when a sub-set of these messages has been received. This field shall not be included when the complete set of these messages has been received. + +The most significant bit of this bitmap (bit N) refers to the message instance with the SIX *index* parameter = N-1, where N is the number of instances of the particular message type (SIX *count* + 1). The least significant bit of this bitmap (bit 1) refers to the message instance with the SI *index* parameter = 0. Each bit position is coded: + +0 Message instance is not received; + +1 Message instance is received. + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ADDITIONAL_MSG_TYPE (1 bit field)

0 No additional message type is present.

1 Additional message type(s) are available, but this information does not fit in to the message.

| +|

PSCSI_SUPPORT (1 bit field)

0 PACKET SERVING CELL SI message not supported

1 PACKET SERVING CELL SI message supported

The MS shall set the PSCSI_SUPPORT bit to "1" in this revision of the specification. This field shall always be present in the PACKET SI STATUS message. If not present, '0' shall be assumed by the receiver

| +|

PS_REL_REQ (1 bit field)

This field indicates whether the mobile station requests the release of the RR connection and packet resources. This field may only be set to "1" in certain cases, see 3GPP TS 44.018. This field shall always be present in the message when the enhanced DTM CS release procedure is ongoing.

0 The mobile station does not request the release of the RR connection and packet resources.

1 The mobile station requests the release of the RR connection and packet resources.

| + +### 11.2.17c Packet Serving Cell SI + +This optional message is sent by the network on the PACCH to provide a SYSTEM INFORMATION message broadcast on the BCCH. For example, several instances of this message may be sent by the network in a cell supporting PACKET SI STATUS following the request for acquisition of system information by a mobile station. This message shall not be segmented across more than one RLC/MAC control block. + +Message type: PACKET SERVING CELL SI + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.17c.1: Packet Serving Cell SI information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Packet Serving Cell SI message content > ::=   < PAGE_MODE : bit (2) >   < CONTAINER_DATA : octet ** >   < padding bits > z   ! < Distribution part error : bit (*) = < no string > > ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.17c.2: Packet Serving Cell SI information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

The Packet Serving Cell SI message contains a serving cell SYSTEM INFORMATION message from the BCCH.

| +|

PAGE_MODE (2 bit field)

This field is defined in sub-clause 12.20.

| +|

CONTAINER_DATA (n*8 bits)

The CONTAINER_DATA octets forms the actual SI message content. The information contained in the Packet Serving Cell SI message shall exclude the following information elements from the beginning of the SI message: L2 Pseudo Length; RR management Protocol Discriminator and Skip Indicator.

Extra octets of padding bits at the end of the SI message may be excluded.

| + +### 11.2.18 Packet System Information Type 1 + +This message is sent by the network on the PBCCH or PACCH giving information for Cell selection, for control of the PRACH, for description of the control channel(s) and global power control parameters. This message shall not be + +segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. Special requirements for the transmission of this message apply on the PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 1 + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.18.1: PSI1 information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < PSI1 message content > ::=   < PAGE_MODE : bit (2) >   < PBCCH_CHANGE_MARK : bit (3) >   < PSI_CHANGE_FIELD : bit (4) >   < PSI1_REPEAT_PERIOD : bit (4) >   < PSI_COUNT_LR : bit (6) >   { 0   1 < PSI_COUNT_HR : bit (4) > }   < MEASUREMENT_ORDER : bit (1) >   < GPRS Cell Options : < GPRS Cell Options IE > >   < PRACH Control Parameters : < PRACH Control Parameters IE > >   < PCCCH Organization Parameters : < PCCCH Organization Parameters IE > >   < Global Power Control Parameters : < Global Power Control Parameters IE > >   < PSI_STATUS_IND : bit >   { null   0      -- Receiver backward compatible with earlier release       1      -- Additions in release 99 :     < MSCR : bit >     < SGSNR : bit >     < BAND_INDICATOR : bit >     { null   0      -- Receiver backward compatible with earlier release         1      -- Additions in Rel-6 :       { 0   1 < LB_MS_TXPWR_MAX_CCH : bit (5) > }       < padding bits > } }   ! < Distribution part error : bit (*) = < no string > > ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.18.2: PSI1 information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

GPRS Cell Options
This information element is defined in sub-clause 12.24

| +|

Global Power Control Parameters
This information element is defined in sub-clause 12.9.

| +|

MEASUREMENT ORDER (1 bit field)
The MEASUREMENT ORDER field indicates if set = 0 that the mobile station is in control of the cell re-selection in both packet idle mode and packet transfer mode and that the mobile station shall not send any measurement reports to the network (= NC0 in 3GPP TS 45.008). It also indicates that the Optional PSI5 message is not broadcast. If set = 1 the mobile station shall send measurement reports for cell re-selection to the network. Further cell re-selection and measurement details are included in the PSI5 message.

| +|

PAGE_MODE (2 bit field)
This field describes which type of page mode used, i.e. either normal paging, extended paging, paging reorganization or same as before from the previous page mode. The mobile station shall ignore this field if the message is received on the PACCH. Coding of this field is defined in 3GPP TS 44.018.

| +|

PBCCH_CHANGE_MARK (3 bit field)
The PBCCH_CHANGE_MARK field is a 3 bit counter incremented with one each time information has been changed in one or more of the broadcast PSI2-PSIn messages on PBCCH (n>2).

| + +#### **PSI\_CHANGE\_FIELD** (4 bit field) + +The PSI\_CHANGE\_FIELD is a 4 bit value reflecting which PSI message or group of instantiated PSI message was most recent updated when the PBCCH\_CHANGE\_MARK was last incremented. If more than one PSI message or group of instantiated PSI message were changed at the same time, the PSI\_CHANGE\_FIELD indicates unspecified updates. Range 0 to 15. + +Bit + +4 3 2 1 + +0 0 0 0 Update of unspecified PSI message(s); + +0 0 0 1 Unknown + +0 0 1 0 PSI2 updated + +0 0 1 1 PSI3/PSI3bis/PSI3ter/PSI3quater updated + +0 1 0 0 Unknown + +*-- This value was allocated in an earlier version of the protocol and shall not be used* + +0 1 0 1 PSI5 updated + +0 1 1 0 PSI6 updated + +0 1 1 1 PSI7 updated + +1 0 0 0 PSI8 updated + +All other values shall be interpreted as 'Update of unknown SI message type'. + +#### **PSI1\_REPEAT\_PERIOD** (4 bit field) + +This field is the binary representation of the PSI1\_REPEAT\_PERIOD parameter value minus one, see 3GPP TS 45.002. The field is coded according to the following table: + +Bit + +4 3 2 1 + +0 0 0 0 PSI1\_REPEAT\_PERIOD = 1 + +0 0 0 1 PSI1\_REPEAT\_PERIOD = 2 + +... + +1 1 1 1 PSI1\_REPEAT\_PERIOD = 16 + +#### **PSI\_COUNT\_LR** (6 bit field) + +This field is the binary representation of the PSI\_COUNT\_LR parameter, see 3GPP TS 45.002. The field is coded according to the following table: + +Bit + +6 5 4 3 2 1 + +0 0 0 0 0 0 PSI\_COUNT\_LR = 0 + +0 0 0 0 0 1 PSI\_COUNT\_LR = 1 + +... + +1 1 1 1 1 1 PSI\_COUNT\_LR = 63 + +#### **PSI\_COUNT\_HR** (4 bit field) + +This field is the binary representation of the PSI\_COUNT\_HR parameter value minus one, see 3GPP TS 45.002. If PSI\_COUNT\_HR is not included in PSI1 message, the default value PSI\_COUNT\_HR = 0 applies. The field is coded according to the following table: + +Bit + +4 3 2 1 + +0 0 0 0 PSI\_COUNT\_HR = 1 + +0 0 0 1 PSI\_COUNT\_HR = 2 + +... + +1 1 1 1 PSI\_COUNT\_HR = 16 + +#### **PCCCH Organization Parameters** + +This information element is defined in sub-clause 12.25 + +#### **PRACH Control Parameters** + +This information element is defined in sub-clause 12.14. + +#### **PSI\_STATUS\_IND** (1 bit field): + +0 The network does not support the PACKET PSI STATUS message; + +1 The network supports the PACKET PSI STATUS message. + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MSCR , MSC Release (1 bit field):
0 The MSC is Release '98 or older
1 The MSC is Release '99 onwards | +| SGSNR , SGSN Release (1 bit field)
0 The SGSN is Release '98 or older
1 The SGSN is Release '99 onwards | +| BAND_INDICATOR (1 bit field)
See 3GPP TS 45.005 for definition of this field, which is coded as follows:
0 ARFCN indicates 1800 band
1 ARFCN indicates 1900 band | +| LB_MS_TXPWR_MAX_CCH (5 bit field)

The LB_MS_TXPWR_MAX_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008. | + +NOTE 1: The MSC Release bit indicates the version of the MSC specific protocols and is not applicable to access stratum protocols. + +NOTE 2: The SGSN Release bit indicates the version of the SGSN specific protocols and is not applicable to access stratum protocols. + +### 11.2.19 Packet System Information Type 2 + +This message is sent by the network on PBCCH and PACCH giving information of reference frequency lists, cell allocation, GPRS mobile allocations and PCCCH descriptions being used in the cell. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 45.002. + +PSI2 also contains Non-GPRS cell options applicable for non-packet access. + +This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. A consistent set of this message type is required to completely decode the information (see sub-clause 5.5.2.1.4). + +- Message type: PACKET SYSTEM INFORMATION TYPE 2 +- Direction: network to mobile station +- Classification: distribution message + +##### **Table 11.2.19.1: PSI2 information elements** + +``` + +< PSI2 message content > ::= + < PAGE_MODE : bit (2) > + < PSI2_CHANGE_MARK : bit (2) > + < PSI2_INDEX : bit (3) > + < PSI2_COUNT : bit (3) > + { 0 | 1 < Cell Identification : < Cell Identification IE > > } + { 0 | 1 < Non GPRS Cell Options : < Non GPRS Cell Options IE > > } + < Reference Frequency Lists : < Reference Frequency Lists struct > > + < Cell Allocation : < Cell Allocation Lists struct > > + < GPRS Mobile Allocations : < GPRS Mobile Allocations Lists struct > > + < PCCCH Description : < PCCCH Description Lists struct > > + { null | 0 bit** = < no string > + | 1 -- Release 1999 additions: + { 0 | 1 < COMPACT Control Information : < COMPACT Control Info struct > > } + { 0 | 1 < Additional PSI Messages : < Additional PSI Messages struct > > } + < padding bits > } } // -- truncation at end of message allowed, bits '0' assumed + ! < Distribution part error : bit (*) > = < no string > > ; + +< Reference Frequency Lists struct > ::= { 1 < Reference Frequency struct > } ** 0; +< Reference Frequency struct > ::= + < RFL_NUMBER : bit (4) > + < Length of RFL contents : bit (4) > + < RFL contents : octet (val(Length of RFL contents) + 3) > ; + +< Cell Allocation Lists struct > ::= { 1 < Cell Allocation struct > } ** 0 ; +< Cell Allocation struct > ::= + < RFL_NUMBER : bit (4) > ; + +< GPRS Mobile Allocations Lists struct > ::= { 1 < GPRS Mobile Allocations struct > } ** 0 ; +< GPRS Mobile Allocations struct > ::= + < MA_NUMBER : bit (4) > + < GPRS Mobile Allocation : < GPRS Mobile Allocation IE > > ; + +< PCCCH Description Lists struct > ::= { 1 < PCCCH Description struct > } ** 0 ; +< PCCCH Description struct > ::= + < TSC : bit (3) > + { 0 < Non-hopping PCCCH carriers : < Non-Hopping PCCCH Carriers Lists struct > > + | 1 < MA_NUMBER : bit (4) > + < Hopping PCCCH carriers : < Hopping PCCCH Carriers Lists struct > > } ; + +< Non-hopping PCCCH Carriers Lists struct > ::= { 1 < Non-Hopping PCCCH Carriers struct > } ** 0 ; +< Non-Hopping PCCCH Carriers struct > ::= + < ARFCN : bit (10) > + < TIMESLOT_ALLOCATION : bit (8) > ; + +< Hopping PCCCH Carriers Lists struct > ::= { 1 < Hopping PCCCH Carriers struct > } ** 0 ; +< Hopping PCCCH Carriers struct > ::= + < MAIO : bit (6) > + < TIMESLOT_ALLOCATION : bit (8) > ; + +< COMPACT Control Info struct > ::= + < Large Cell Operation : bit (1) > + { 0 | 1 < Number of Idle Blocks : < Number of Idle Blocks struct > > } + { 0 | 1 < N_CCCH_NH : bit (4) > } ; + + ::= + { 0 | 1 < NIB_CCCH_0 : bit (4) > } + { 0 | 1 < NIB_CCCH_1 : bit (4) > } + { 0 | 1 < NIB_CCCH_2 : bit (4) > } + { 0 | 1 < NIB_CCCH_3 : bit (4) > } ; + +< Additional PSI Messages struct > ::= + < NON_GSM_INFORMATION : bit(2) > + < PSI8_BROADCAST : bit (1) > + < PSI3ter_BROADCAST : bit (1) > + < PSI3quater_BROADCAST : bit (1) > ; + +``` + +Table 11.2.19.2: PSI2 information element details + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PAGE_MODE (2 bit field)
This field describes which type of page mode used, i.e. either normal paging, extended paging, paging reorganization or same as before from the previous page mode. The mobile station shall ignore this field if the message is received on the PACCH. Coding of this field is defined in 3GPP TS 44.018 | +| PSI2_CHANGE_MARK (2 bit field)
This field is the binary representation of the PSI change mark parameter identifying a consistent set of PSI2 messages. Range: 0 to 3. | +| PSI2_INDEX (3 bit field) and PSI2_COUNT (3 bit field)
These fields are the binary representation of the PSI index and PSI count parameters associated with the PSI2 message. | +| Cell Identification
This information element is defined in sub-clause 12.23. This field shall be present in at least one instance of PSI2 and may appear only once in a complete set of PSI2 messages. | +| Non GPRS Cell Options
This field is defined in sub-clause 12.27.
This field shall be present in at least one instance of PSI2. | +| Reference Frequency Lists (construction)
This construction is the representation of the reference frequency lists provided in an instance of the PSI2 message. An RFL_NUMBER field preceding each reference frequency list (RFL) identifies the RFL. | +| Cell Allocations (construction)
This construction is a representation of the cell allocation (CA) defined for the cell. The set of radio frequency channels contained in the referenced RFLs in this construction defines the cell allocation. | +| GPRS Mobile Allocations (construction)
This construction is the representation of the GPRS mobile allocations provided in an instance of the PSI2 message. An MA_NUMBER field preceding each GPRS mobile allocation identifies the GPRS mobile allocation. The receiver shall disregard a GPRS mobile allocation provided in this message that is identified by MA_NUMBER = 14 or 15. | +| PCCCH Description (construction)
This construction is a representation of the timeslots carrying PCCCH in the cell and their frequency configurations. The training sequence code (TSC) preceding each list of PCCCH carriers in the PCCCH description shall be used for the timeslots selected for PCCCH on those PCCCH carriers. The TSC that is used for the timeslot also carrying PBCCH shall equal the TSC used for the PBCCH in the cell.

The number of timeslots carrying PCCCH in the cell is denoted KC. This is also the implicit value of the parameter BS_PCC_CHANS, see 3GPP TS 45.002. The range for KC is 1 to 16 if PBCCH (and PCCCH) is present in the cell. (KC = 0 if PBCCH is not present in the cell.)

The mapping of the PCCCH_GROUPS (numbered from 0 to KC-1) starts with the lowest numbered PCCCH_GROUP, which is mapped on the lowest numbered timeslot carrying PCCCH on the first (non-hopping or hopping) PCCCH carrier appearing in this construction. The next higher numbered PCCCH_GROUP is mapped on the next (if any) higher numbered timeslot carrying PCCCH on the same carrier, and so on. When all timeslots carrying PCCCH on the first carrier have been used, the next higher numbered PCCCH_GROUP is mapped on the lowest numbered timeslot carrying PCCCH on the next PCCCH carrier appearing in this construction, and so on. The highest numbered PCCCH_GROUP is mapped on the highest numbered timeslot carrying PCCCH on the last PCCCH carrier appearing in this construction. | +| RFL_NUMBER (4 bit field)
This field is the binary identification of an RFL provided in this message or the binary reference to such. Range: 0 to 15. | +| RFL contents (variable length octet string)
This variable length octet string is the representation of a set of radio frequency channels defining an RFL provided in the PSI2 message. The encoding of the octet string is defined by the value part of the type 4 information element Frequency List , defined in 3GPP TS 44.018. The allowed formats of the Frequency List information element are the bit map 0 , 1024 range , 512 range , 256 range , 128 range and variable bit map formats. | + +| | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|------------------------------------------------------------------------|--|---|---|--------------------------------------------------|---|---|--------------------------------------------------------------|---|---|--------------------------------------------------------------|---|---|------------------------------------------------------------------------| +|

MA_NUMBER (4 bit field)

This field is the binary identification of a GPRS Mobile Allocation provided in this message or the binary reference to such.
Range: 0 to 13. (MA_NUMBER = 14 and 15 shall not be used in this message.)

| | | | | | | | | | | | | | | | +|

GPRS Mobile Allocation (information element)

The GPRS Mobile Allocation information element is defined in sub-clause 12.10a.

| | | | | | | | | | | | | | | | +|

TSC (3 bit field)

This field is the binary representation of the training sequence code, see 3GPP TS 45.002.
Range: 0 to 7.

| | | | | | | | | | | | | | | | +|

ARFCN (10 bit field)

This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP 45.005.
Range 0 to 1023.

| | | | | | | | | | | | | | | | +|

MAIO (6 bit field)

This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 45.002.
Range: 0 to 63.

| | | | | | | | | | | | | | | | +|

TIMESLOT_ALLOCATION (8 bit field)

This field indicates which timeslot are assigned as PCCCH. This field is coded as defined in sub-clause 12.18. . Note that for a CPCCCH this information shall be ignored by the MS, the CPCCCH is rotating between odd timeslots and not allocated to a specific timeslot, see 3GPP TS 45.002.

| | | | | | | | | | | | | | | | +|

Large Cell Operation (LARGE_CELL_OP)

If this bit is set to one, the cell is in large cell operation mode (see 3GPP TS 45.002).

0 This cell is a nominal size cell
1 This cell is a large cell

| | | | | | | | | | | | | | | | +|

NIB_CCCH_0 (4 bit field)

This field is the binary representation of the number of radio blocks that shall remain idle in time group 0 for blocks associated with CPBCCH and CPCCCH (see 3GPP TS 45.002). If this information element is not present the value 0 shall be used. Note that this information element shall not be present for the serving cell time group (e.g. if the serving cell time group is time group zero, this information element is not present, but if the serving cell time group is time group one this information element is present).

| | | | | | | | | | | | | | | | +|

NIB_CCCH_1, NIB_CCCH_2, NIB_CCCH_3

Defined exactly as NIB_CCCH_0, except applied to time group 1, 2, and 3 respectively.

| | | | | | | | | | | | | | | | +|

N_CCCH_NH (4 bit field)

This field is the binary representation of the amount of non-hopping blocks on control channels (see 3GPP TS 45.002).
Range 1 to 11.

| | | | | | | | | | | | | | | | +|

Additional PSI messages struct

If any of the PSI messages named in this structure are broadcast in the cell, this field shall be present in at least one instance of PSI2 and may appear only once in a complete set of PSI2 messages.

| | | | | | | | | | | | | | | | +|

NON_GSM_INFORMATION (2 bit field)

This field indicates whether non-GSM information is broadcast on the cell and specifies the messages that are used for this purpose. If this field indicates that both PSI6 and PSI7 are broadcast on the cell, these messages shall be broadcast within different repetition rate groups (see 3GPP TS 45.002).

Bit

2 1
0 0 non-GSM information is not broadcast on the cell
0 1 non-GSM information is broadcast on the cell in PSI6 message
1 0 non-GSM information is broadcast on the cell in PSI7 message
1 1 non-GSM information is broadcast on the cell in PSI6 and PSI7 messages
| 2 | 1 | | 0 | 0 | non-GSM information is not broadcast on the cell | 0 | 1 | non-GSM information is broadcast on the cell in PSI6 message | 1 | 0 | non-GSM information is broadcast on the cell in PSI7 message | 1 | 1 | non-GSM information is broadcast on the cell in PSI6 and PSI7 messages | +| 2 | 1 | | | | | | | | | | | | | | | +| 0 | 0 | non-GSM information is not broadcast on the cell | | | | | | | | | | | | | | +| 0 | 1 | non-GSM information is broadcast on the cell in PSI6 message | | | | | | | | | | | | | | +| 1 | 0 | non-GSM information is broadcast on the cell in PSI7 message | | | | | | | | | | | | | | +| 1 | 1 | non-GSM information is broadcast on the cell in PSI6 and PSI7 messages | | | | | | | | | | | | | | + +| | +|---------------------------------------------------------------------------------------------------------------------------------| +| PSI8_BROADCAST (1 bit field)
0 PSI8 is not broadcast on the cell
1 PSI8 is broadcast on the cell | +| PSI3ter_BROADCAST (1 bit field)
0 PSI3ter is not broadcast on the cell
1 PSI3ter is broadcast on the cell | +| PSI3quater_BROADCAST (1 bit field)
0 PSI3quater is not broadcast on the cell
1 PSI3quater is broadcast on the cell | + +#### 11.2.19.1 Reference Frequency Lists in PSI2 + +A Reference Frequency Lists construction may be included in each instance of the PSI2 message. The presence of reference frequency lists (RFLs) is optional. RFLs shall be provided as required for the decoding of GPRS mobile allocations and cell allocation. + +#### 11.2.19.2 Cell Allocation in PSI2 + +A Cell Allocation construction shall not be included in more than one instance of the PSI2 message within the consistent set of PSI2 messages. The presence of a Cell Allocation construction is optional. It shall be provided as required for the decoding of GPRS mobile allocations and for the support of GPRS mobile stations which may access the network in dedicated, group receive and group transmit modes, see 3GPP TS 44.018. + +#### 11.2.19.3 GPRS Mobile Allocation in PSI2 + +A GPRS Mobile Allocations construction may be included in each instance of the PSI2 message. The presence of GPRS mobile allocations is optional. The GPRS mobile allocations shall be provided as required for determining the frequency configuration of PDCHs. + +#### 11.2.19.4 PCCH Description + +A PCCH Description construction shall be included in one and only one instance of the PSI2 message within the consistent set of PSI2 messages. + +#### 11.2.19.5 Abnormal cases + +If the receiver detects any violation against the rules for the appearance of the different constructions defined for this message within the consistent set of this message type, it may regard the contents of these messages as invalid. + +### 11.2.20 Packet System Information Type 3 + +This message is sent by the network on the PBCCH or PACCH giving information of the BCCH allocation (BA(GPRS)) in the neighbour cells and cell selection parameters for serving cell and non-serving cells. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. Special requirements for the transmission of this message apply on the PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 3 + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.20.1: PSI3 information elements** + +``` + +< PS13 message content > ::= + < PAGE_MODE : bit (2) > + < PS13_CHANGE_MARK : bit (2) > + < PS13_BIS_COUNT : bit (4) > + < Serving Cell parameters : < Serving Cell params struct > > + < General Cell Selection parameter : < Gen Cell Sel struct > > + < Neighbour Cell parameters : { 1 < Neighbour Cell params struct > } ** 0 > + { null | 0 bit** = < no string > + | 1 + -- Release 1998 additions: + < Serving Cell LSA ID information : < LSA ID information struct > > + { 0 | 1 < LSA Parameters : < LSA Parameters IE >> } + { null | 0 bit** = < no string > + | 1 + -- Release 1999 additions: + 0 0 + -- The values '01', '10' and '11' were allocated in an earlier version of the protocol + -- and shall not be used. + { 0 | 1 < COMPACT Information : < COMPACT Information struct > > } + 0 -- The value '1' was used in an earlier version of the protocol and shall not be used. + { null | 0 bit** = < no string > + | 1 + -- Rel-4 additions: + { 0 | 1 < CCN Support Description : < CCN Support Description struct >> } + { null | 0 bit** = < no string > + | 1 + -- Rel-5 additions: + < CELL BAR QUALIFY 3 : bit (2) > + -- Serving cell barring status. + < Iu Mode Neighbour Cell Parameters : { 1 < Iu Mode Neighbour Cell params struct > } ** 0 > + --Supplementary information for dual Iu mode and A/Gb mode capable cells + < Iu mode Only Neighbour Cell Parameters : + { 1 < Iu mode Only Neighbour Cell params struct > } ** 0 > + < padding bits > } } } } + ! < Distribution part error : bit (*) = < no string > > ; + +< Serving Cell params struct > ::= + < CELL_BAR_ACCESS_2 : bit > + < EXC_ACC : bit > + < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > + { 0 | 1 < HCS Serving Cell parameters : < HCS struct > > } + < MULTIBAND_REPORTING : bit (2) > ; + +< HCS struct > ::= + < PRIORITY_CLASS : bit (3) > + < HCS_THR : bit (5) > ; + +< Gen Cell Sel struct > ::= + < GPRS_CELL_RESELECT_HYSTERESIS : bit (3) > + < C31_HYST : bit (1) > + < C32_QUAL : bit (1) > + 1 -- The value '0' was used in an earlier version of the protocol and shall not be used. + { 0 | 1 < T_RESEL : bit (3) > } + { 0 | 1 < RA_RESELECT_HYSTERESIS : bit (3) > } ; + +< Neighbour Cell params struct > ::= + < START_FREQUENCY : bit (10) > + < Cell selection params : < Cell Selection struct > > + < NR_OF_REMAINING_CELLS : bit (4) > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (1 + val(FREQ_DIFF_LENGTH)) > + < Cell Selection Params : < Cell Selection struct >> } * (val(NR_OF_REMAINING_CELLS)) ; + +``` + +``` + +< Cell Selection struct > ::= + < BSIC : bit (6) > + < CELL_BAR_ACCESS_2 : bit > + < EXC_ACC : bit > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13 PBCCH Location : < SI13 PBCCH Location struct > > } ; + +< SI13 PBCCH Location struct > ::= + { 0 < SI13_LOCATION : bit (1) > + | 1 < PBCCH_LOCATION : bit (2) > + < PSI1_REPEAT_PERIOD : bit (4) > } ; + +< LSA ID information struct > ::= + { 1 { 0 < LSA_ID : bit (24) > + | 1 < ShortLSA_ID : bit (10) > } } ** 0 ; + +< COMPACT Information struct > ::= + < Cell Identification : Cell identification IE> + { 1 < COMPACT Neighbour Cell params struct > } ** 0 ; + +< COMPACT Neighbour Cell params struct > ::= + < START_FREQUENCY : bit (10) > + < COMPACT Cell selection params : < COMPACT Cell Selection struct > > + < NR_OF_REMAINING_CELLS : bit (4) > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (1 + val(FREQ_DIFF_LENGTH)) > + < COMPACT Cell selection params : + < COMPACT Cell Selection struct > > } * (val(NR_OF_REMAINING_CELLS)); + +< COMPACT Cell Selection struct > ::= + < BSIC : bit (6) > + < CELL_BAR_ACCESS_2 : bit > + < EXC_ACC : bit > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < TIME_GROUP : bit (2) > } + { 0 | 1 < GUAR_CONSTANT_PWR_BLKS : bit (2) > } ; + +< CCN Support Description struct > ::= + < Number_Cells : bit (7) > + { CCN_SUPPORTED : bit } * (val(Number_Cells)) ; + < Iu Mode Neighbour Cell Params struct > ::= + < NR_OF_REMAINING_CELLS : bit (4) > + { 0 | 1 < Iu Mode Cell Selection Params : + < Iu Mode Cell Selection struct > > } * (val(NR_OF_REMAINING_CELLS)); + < Iu Mode Cell Selection struct > ::= + < CELL BAR QUALIFY 3 : bit (2) > + { 0 | 1 < SI13Alt PBCCH Location : < SI13 PBCCH Location struct > > } ; + < Iu mode Only Neighbour Cell params struct > ::= + < START_FREQUENCY : bit (10) > + < Iu mode Only Cell selection params : < Iu mode Only Cell Selection struct > > + < NR_OF_REMAINING_CELLS : bit (4) > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (1 + val(FREQ_DIFF_LENGTH)) > + < Iu mode Only Cell selection params : + < Iu mode Only Cell Selection struct > > } * (val(NR_OF_REMAINING_CELLS)); + +``` + +``` +< Iu Mode Only Cell Selection struct > ::= + < BSIC : bit (6) > + < CELL BAR QUALIFY 3 : bit (2) > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13Alt PBCCH Location : < SI13 PBCCH Location struct > > }; +``` + +Table 11.2.20.2: PSI3 information element details + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)

This field describes which type of page mode used, i.e. either normal paging, extended paging, paging reorganization or same as before from the previous page mode. The mobile station shall ignore this field if the message is received on the PACCH. Coding of this field is defined in 3GPP TS 44.018

| +|

PSI3_CHANGE_MARK (2 bit field)

The PSI3 change mark field is changed each time information has been updated in any of the PSI3, PSI3 bis, PSI3 ter or PSI3 quater messages. A new value indicates that the mobile station shall re-read the information from the PSI3 and all PSI3 bis, PSI3 ter and PSI3 quater messages. The coding of this field is network dependent. Range: 0-3.

| +|

PSI3_BIS_COUNT (4 bit field)

This field is coded as the binary representation of the PSI3 bis index (in the PSI3 bis message) for the last (highest indexed) individual PSI3 bis message. Range: 0-15.

| +|

Serving Cell Parameters:

CELL_BAR_ACCESS_2 (1 bit field)

This field combines the CELL_BAR_ACCESS and CELL_BAR_QUALIFY parameters and indicates the status for cell reselection, see 3GPP TS 45.008:

0 Status for cell reselection is set to normal;
1 Status for cell reselection is set to barred.

| +|

EXC_ACC (1 bit field)

EXC_ACC is used by the network to prevent mobiles without exclusive access rights from camping on the cell. The usage of EXC_ACC is described in 3GPP TS 43.022. The coding of EXC_ACC is as follows:

0 The cell is not used for SoLSA exclusive access.
1 The cell is used for SoLSA exclusive access.

| +|

GPRS_RXLEV_ACCESS_MIN (6 bit field)

The GPRS_RXLEV_ACCESS_MIN field is coded as the binary representation of the 'RXLEV_ACCESS_MIN' defined in 3GPP TS 45.008. It is the minimum received level at the mobile station required for access to the system.

| +|

GPRS_MS_TXPWR_MAX_CCH (5 bit field)

The GPRS_MS_TXPWR_MAX_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008.

| +|

HCS struct

If the HCS struct is omitted for the serving cell, HCS is not used and the HCS parameters for the other cells shall be neglected i.e the HCS signal strength threshold shall be set to infinity for all cells. Otherwise PRIORITY_CLASS and HCS_THR are defined. The use of the HCS parameters is defined in 3GPP TS 45.008.

| + +#### **PRIORITY\_CLASS** (3 bit field) + +The PRIORITY\_CLASS field contains the binary representation of the HCS priority for the cell. + +Bit +3 2 1 +0 0 0 Lowest Priority +..... +1 1 1 Highest Priority + +#### **HCS\_THR** (5 bit field) + +The HCS\_THR is the HCS signal strength threshold + +Bit +5 4 3 2 1 +0 0 0 0 0 -110 dBm +0 0 0 0 1 -108 dBm +... .. +1 1 1 1 0 -50 dBm +1 1 1 1 1 infinity + +#### **MULTIBAND\_REPORTING** (2 bit field) + +Binary encoding of multiband reporting parameter as specified in 3GPP TS 45.008 +Range 0-3. + +#### *General Cell Selection Parameters* + +##### **GPRS\_CELL\_RESELECT\_HYSTERESIS** (3 bit field) + +The GPRS\_CELL\_RESELECT\_HYSTERESIS field indicates the Additional Hysteresis which applies in Ready state in *A/Gb mode* and RRC-Cell\_Shared state in *Iu mode* for cells in same RA. This field is encoded according to the following table: + +Bit +3 2 1 +0 0 0 0 dB +0 0 1 2 dB +0 1 0 4 dB +0 1 1 6 dB +1 0 0 8 dB +1 0 1 10 dB +1 1 0 12 dB +1 1 1 14 dB + +#### **C31\_HYST** (1 bit field) + +The C31\_HYST field indicates if set to 1 that the GPRS\_CELL\_RESELECT\_HYSTERESIS shall be applied to the C31 criterion. + +##### **C32\_QUAL** (1 bit field) + +C32\_QUAL is a flag indicating an exception rule for GPRS\_RESELECT\_OFFSET according to 3GPP TS 45.008. + +**T\_RESEL** (3 bit field) + If the mobile station has performed an abnormal release with cell reselection (see sub-clause 9.4.2) from this cell, the mobile station is not allowed to reselect this cell for T\_RESEL seconds if another cell is available. The default value of T\_RESEL is 5 s. If the field is omitted from the message, the default value shall be used by the mobile station. + +Bit +3 2 1 + +| | | +|-------|-------| +| 0 0 0 | 5 s | +| 0 0 1 | 10 s | +| 0 1 0 | 15 s | +| 0 1 1 | 20 s | +| 1 0 0 | 30 s | +| 1 0 1 | 60 s | +| 1 1 0 | 120 s | +| 1 1 1 | 300 s | + +**RA\_RESELECT\_HYSTERESIS** (3 bit field) + The RA\_RESELECT\_HYSTERESIS field indicates in both STANDBY and READY state in *A/Gb mode* and RRC-Idle and RRC-Connected mode in *Iu mode* the additional hysteresis which applies when selecting a cell in a new Routing Area. If this field is not present, the default value is GPRS\_CELL\_RESELECT\_HYSTERESIS. This field is encoded according to the following table: + +Bit +3 2 1 + +| | | +|-------|-------| +| 0 0 0 | 0 dB | +| 0 0 1 | 2 dB | +| 0 1 0 | 4 dB | +| 0 1 1 | 6 dB | +| 1 0 0 | 8 dB | +| 1 0 1 | 10 dB | +| 1 1 0 | 12 dB | +| 1 1 1 | 14 dB | + +*Neighbour Cell Parameters* + +The Neighbour cell parameters are used to specify neighbour cells (BA(GPRS)) and their corresponding cell selection parameters. The Neighbour cell parameters are specified in PSI3 and in at least one instance of PSI3bis. If one instance of PSI3bis is not sufficient to specify the cell selection parameters of all neighbour cells, the remaining neighbour cells are specified in consecutive instances of PSI3bis. If all information fits within the PSI3 message, one instance of PSI3bis without any neighbour cell parameters is broadcast. + +NOTE: For efficient coding, cells with common cell selection parameters may be grouped together. + +Building of BA(GPRS) is defined in sub-clause 5.6.3.2. + +**START\_FREQUENCY** (10 bit field) + The START\_FREQUENCY defines the ARFCN for the first carrier in the list (ARFCN(0)). **FREQ\_DIFF\_LENGTH** (3 bit field) + This field is required to calculate the number of bits to be used for the FREQUENCY\_DIFF field in the current frequency group. + +**FREQUENCY\_DIFF** (1+val(FREQ\_DIFF\_LENGTH) bit field) + Each FREQUENCY\_DIFF parameter field specifies the difference in frequency to the next carrier to be defined. The FREQUENCY\_DIFF parameter encodes a non negative integer in binary format (W). + +Each frequency following the start frequency (ARFCN(0)) and belonging to the Frequency List struct is then calculated by the formula $ARFCN(n) = (ARFCN(n-1) + W(n)) \bmod 1024$ , $n=1, \dots, val(NR\_OF\_REMAINING\_CELLS)$ . + +##### **General rules for handling neighbour cell parameter default values** + +The first neighbour cell defined in PSI3 uses as its default parameter values the parameter values defined for the serving cell. If a parameter is omitted for the serving cell then the specified default value shall be used. The following neighbour cells use the parameter values of the previous neighbour cell as their default values. + +#### **Cell Selection params** + +The first field of the Cell Selection struct, *BSIC*, defines the BSIC of the cell and then comes the fields + +**CELL\_BAR\_ACCESS\_2**, **ECX\_ACC** and **SAME\_RA\_AS\_SERVING\_CELL**. Then follows none, some, or all of the fields **GPRS\_RXLEV\_ACCESS\_MIN**, **GPRS\_MS\_TXPWR\_MAX\_CCH**, **GPRS\_TEMPORARY\_OFFSET**, **GPRS\_PENALTY\_TIME**, **GPRS\_RESELECT\_OFFSET**, HCS params, **SI13\_PBCCH\_LOCATION**, **PCCH\_TYPE** and **PSI1\_REPEAT\_PERIOD**. If fields are omitted, the values for these parameters are the same as for the preceding cell unless otherwise specified for the parameter. + +##### **BSIC** (6 bit field) + +The BSIC field is coded as the 'Base Station Identity Code' defined in 3GPP TS 23.003. One BSIC for each carrier in BA(GPRS) is defined. + +#### **CELL\_BAR\_ACCESS\_2** (1 bit field) + +#### **EXC\_ACC** (1 bit field) + +For definition see Serving Cell parameters + +#### **SAME\_RA\_AS\_SERVING\_CELL** (1 bit field) + +The same RA as serving cell field contains one bit, set to + +- 0 if the cell is in a Routeing Area different from the serving cell, or +- 1 if the cell is in the same Routeing Area as the serving cell. + +#### **GPRS\_TEMPORARY\_OFFSET** (3 bit field) + +The **GPRS\_TEMPORARY\_OFFSET** field indicates the negative offset to C32 that the mobile station shall use for duration of **GPRS\_PENALTY\_TIME**. It is used by the mobile station as part of its calculation of C32 for the cell reselection process. Default value is 0 dB. If the field is omitted for the first neighbour cell, the default value shall be used by the mobile station. + +##### Bit + +3 2 1 + +| | | +|-------|----------| +| 0 0 0 | 0 dB | +| 0 0 1 | 10 dB | +| 0 1 0 | 20 dB | +| 0 1 1 | 30 dB | +| 1 0 0 | 40 dB | +| 1 0 1 | 50 dB | +| 1 1 0 | 60 dB | +| 1 1 1 | infinity | + +#### **GPRS\_PENALTY\_TIME** (5 bit field) + +The **GPRS\_PENALTY\_TIME** defines the length of time for which **GPRS\_TEMPORARY\_OFFSET** is active. + +##### Bit + +5 4 3 2 1 + +| | | +|-----------|-------| +| 0 0 0 0 0 | 10 s | +| 0 0 0 0 1 | 20 s | +| ... | | +| 1 1 1 1 1 | 320 s | + +#### **GPRS\_RESELECT\_OFFSET (5 bit field)** + +GPRS\_RESELECT\_OFFSET is used by the mobile station to apply a positive or negative offset and a hysteresis to the GPRS cell reselection criterion. Default value is 0 dB. If the field is omitted from the message, the default value shall be used by the mobile station. + +| | | +|-----------|--------| +| Bit | | +| 5 4 3 2 1 | | +| 0 0 0 0 0 | -52 dB | +| 0 0 0 0 1 | -48 dB | +| ... | | +| 0 1 0 1 0 | -12 dB | +| 0 1 0 1 1 | -10 dB | +| ... | | +| 1 0 1 1 0 | +12 dB | +| 1 0 1 1 1 | +16 dB | +| ... | | +| 1 1 1 1 1 | +48 dB | + +#### **SI13\_PBCCH\_LOCATION construction** + +The optional SI13\_PBCCH\_LOCATION struct may either indicate the position of the SI13 message or a PBCCH position. If not included, SI3 and SI4 in the neighbour cell indicates if the neighbour cell supports GPRS. + +#### **SI13\_LOCATION (1 bit field)** + +The SI13\_LOCATION field, if present, indicates the logical channel where the SYSTEM INFORMATION TYPE 13 is broadcast (see 3GPP TS 45.002). + +- 0 SYSTEM INFORMATION TYPE 13 message is sent on BCCH norm +- 1 SYSTEM INFORMATION TYPE 13 message is sent on BCCH ext + +#### **PBCCH\_LOCATION (2 bit field)** + +The PBCCH\_LOCATION field, if present, indicates the location of the PBCCH on the BCCH carrier (see 3GPP TS 45.002). If the PBCCH location for a neighbour cell is given using this field, the TSC shall equal the BCC determined by the BSIC of that cell. + +| | | +|-----|-------------------------------| +| bit | | +| 2 1 | | +| 0 0 | PBCCH on TN 1 of BCCH carrier | +| 0 1 | PBCCH on TN 2 of BCCH carrier | +| 1 0 | PBCCH on TN 3 of BCCH carrier | +| 1 1 | PBCCH on TN 4 of BCCH carrier | + +#### **PSI1\_REPEAT\_PERIOD (4 bit field)** + +The PSI1\_REPEAT\_PERIOD field indicates the PSI repeat period. The field is coded according to the following table: + +| | | +|---------|-------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | PSI1 repeat period = 1 | +| 0 0 0 1 | PSI1 repeat period = 2 | +| ... | | +| 1 1 1 1 | PSI1 repeat period = 16 | + +#### **LSA Parameters IE** + +The LSA Parameters IE contains a list of LSA\_ID(s) corresponding to the entries in the Neighbour Cell Parameters. Some entries in LSA parameters may be empty. The entries in the LSA Parameters IE are listed in the same order as in the Neighbour Cell Parameters and the number of entries (nr\_of\_frequencies\_or\_cells) should be the same. In case there are too few entries in the LSA Parameters IE, empty entries shall be added at the end. In case there are too many entries in the LSA parameters, the last shall be discarded. The 'LSA parameters IE' is defined in sub-clause 12.28. + +##### **LSA\_ID** (24 bit field) + +The purpose of the LSA\_ID field is to identify a LSA. The LSA ID value field is coded as specified in 3GPP TS 23.003. + +##### **Short LSA\_ID** (10 bit field) + +The purpose of the Short LSA\_ID field is to identify a LSA. The LSA ID defined by the Short LSA\_ID is a LSA\_ID as specified in 3GPP TS 23.003 with bit 0 set to "0" bit 1 to 10 set to the value of the Short LSA\_ID field (LSB in bit 1, MSB in bit 10) and bit 11 to 23 set to "0". + +##### **TIME\_GROUP** (2 bit field) + +The TIME\_GROUP defines which time group (see 3GPP TS 45.002) the cell belongs to + +| | | +|-----|--------------| +| bit | | +| 2 1 | | +| 0 0 | Time Group 0 | +| 0 1 | Time Group 1 | +| 1 0 | Time Group 2 | +| 1 1 | Time Group 3 | + +##### **GUAR\_CONSTANT\_PWR\_BLKS** (2 bit field) + +This field indicates the guaranteed number of constant power blocks in the neighbour cell. These are the blocks that the MS can use to perform neighbour cell measurements (see 3GPP TS 45.008). Note that there may be more CPBCCH blocks or allowed paging blocks in the neighbour cell than what is indicated in this field, but never less. + +| | | +|-----|--------------------------------------------| +| bit | | +| 2 1 | Blocks at constant power | +| 0 0 | 4 | +| 0 1 | 5 | +| 1 0 | 6 | +| 1 1 | 12 (i.e. BS_PAG_BLKS_RES = 0 in that cell) | + +#### **Cell Identification** + +This information element is defined in sub-clause 12.23. + +#### **CCN Support Description** + +##### **CCN\_SUPPORTED** (1 bit field) + +This parameter is used for determining whether the mobile station shall enter CCN mode when re-selecting a cell and CCN is enabled. The use of these bits is described in sub-clause 8.8.2a ("CCN support description"): + +| | | +|-----|------------------------------------------------| +| Bit | | +| 0 | CCN is enabled towards the corresponding cell | +| 1 | CCN is disabled towards the corresponding cell | + +#### **CELL BAR QUALIFY 3** (2 bit field) + +This information element is defined in 3GPP TS 44.018. + +##### *Iu mode Neighbour Cell Parameters* + +The *Iu mode Neighbour Cell Parameters* are used to specify *Iu mode* (and *A/Gb mode*) capable neighbouring cells (BA(GPRS)) and their corresponding cell selection parameters. The *Iu mode Neighbour Cell Parameters* are specified in PSI3 and in at least one instance of PSI3bis. If one instance of PSI3bis is not sufficient to specify the cell selection parameters of all *Iu mode* capable neighbouring cells, the remaining *Iu mode* capable neighbouring cells are specified in consecutive instances of PSI3bis. If all information fits within the PSI3 message, one instance of PSI3bis without any *Iu mode Neighbour Cell Parameters* is broadcast. + +NOTE: For efficient coding, cells with common cell selection parameters may be grouped together. + +Building of BA(GPRS) is defined in sub-clause 5.6.3.2. + +##### *Iu mode Only Neighbour Cell Parameters* + +The *Iu mode Only Neighbour Cell Parameters* are used to specify *Iu mode* only capable neighbouring cells and their corresponding cell selection parameters. The *Iu mode Only Neighbour Cell Parameters* are specified in PSI3 and in at least one instance of PSI3bis. If one instance of PSI3bis is not sufficient to specify the cell selection parameters of all *Iu mode* only capable neighbouring cells, the remaining *Iu mode* only capable neighbouring cells are specified in consecutive instances of PSI3bis. If all information fits within the PSI3 message, one instance of PSI3bis without any *Iu mode Only Neighbour Cell Parameters* is broadcast. + +##### *Iu mode Neighbour Cell params struct* + +This struct presents supplementary information for *Iu mode* capable cells. The struct may be included in this message and assigns *Iu mode* parameter values to the neighbouring cells defined by the message. *Iu mode* capable neighbouring cells are defined by the *Neighbour Cell Parameter IE*. The *Iu mode Neighbour Cell params struct* values are assigned to the neighbouring cells in the same order they appear in the PSI3 and PSI3bis messages. + +### 11.2.21 Packet System Information Type 3 bis + +This message is sent by the network on the PBCCH and PACCH giving information of the BCCH allocation in the neighbour cells and cell selection parameters for non-serving cells. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. If not all information fits into one instance of the PSI3bis message, the PSI3bis message can be repeated. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 3 BIS + +Direction: network to mobile station + +Classification: distribution message + +##### **Table 11.2.21.1: PSI3 bis information elements** + +``` + +< PSI3 bis message content > ::= + < PAGE_MODE : bit (2) > + < PSI3_CHANGE_MARK : bit (2) > + < PSI3_BIS_INDEX : bit (4) > + < PSI3_BIS_COUNT : bit (4) > + { < Neighbour cell parameters : { 1 < Neighbour cell params struct > } ** 0 > + < Neighbour Cell parameters 2 : { 1 < Neighbour Cell params 2 struct > } ** 0 > + { null | 0 bit** = < no string > + | 1 + { 0 | 1 < LSA Parameters : < LSA Parameters IE >> } + { null | 0 bit** = < no string > + | 1 + < COMPACT Neighbour Cell Parameters : { 1 < COMPACT Neighbour Cell params 2 struct > } ** 0 > + 0 + -- The value '1' was used in an earlier version of the protocol and shall not be used. + { null | 0 bit** = < no string > + | 1 + { 0 | 1 < CCN Support Description : < CCN Support Description struct >> } + { null | 0 bit** = < no string > + | 1 + < lu Mode Neighbour Cell Parameters : { 1 < lu Mode Neighbour Cell params struct > } ** 0 > + --Supplementary information for dual lu mode and A/Gb mode capable cells + < lu mode Only Neighbour Cell Parameters : + { 1 < lu mode Only Neighbour Cell params struct > } ** 0 > + < padding bits > } } } } // -- truncation at end of message allowed, bits '0' assumed + ! < Distribution part error : bit (*) = < no string > > ; + +< Neighbour cell params struct > ::= + < START_FREQUENCY : bit (10) > + < Cell selection params : < Cell Selection struct > > + < NR_OF_REMAINING_CELLS : bit (4) > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (1 + val(FREQ_DIFF_LENGTH)) > + < Cell selection params : < Cell Selection struct > > } * (val(NR_OF_REMAINING_CELLS)); + +< Cell Selection struct > ::= + < BSIC : bit (6) > + < CELL_BAR_ACCESS_2 : bit > + < EXC_ACC : bit > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13_PBCCH_LOCATION : < SI13_PBCCH_LOCATION struct > > } ; + +< SI13_PBCCH_LOCATION struct > ::= + { 0 < SI13_LOCATION : bit (1) > + | 1 < PBCCH_LOCATION : bit (2) > + < PSI1_REPEAT_PERIOD : bit (4) > } ; + +< HCS struct > ::= + < PRIORITY_CLASS : bit (3) > + < HCS_THR : bit (5) > ; + +< Neighbour Cell params 2 struct > ::= + { 00 -- Message escape + { 1 < NCP2 Repeat struct > + < CELL_PARAMS_POINTER : bit (2) > } ** 0 --Up to four pointers to the 'Neighbour parameter set' + < Neighbour parameter set : < Neighbour parameter set struct > > * (1 + max(val(CELL_PARAMS_POINTER))) + ! < Message escape: { 01 | 10 | 11 } bit** = < no string >> } ; -- Reserved for future use + +``` + +``` +< NCP2 Repeat struct > ::= +{ 1 < START_FREQUENCY : bit (10) > -- Multiple START FREQ/FREQ DIFF sets may be defined + < NCP2 Property struct > + { < NR_OF_REMAINING_CELLS : { bit (4) - 0000 } > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (1 + val(FREQ_DIFF_LENGTH)) > + < NCP2 Property struct > } * (val(NR_OF_REMAINING_CELLS)) + < NCP2 Repeat struct > -- Repeated recursively + | 0000 } -- Break recursion (NR_OF_REMAINING_CELLS == 0) + | 0 } ; -- End recursion (no more START_FREQUENCY) + +< NCP2 Property struct > ::= + < SAME_RA_AS_SERVING_CELL : bit (1) > + < CELL_BAR_ACCESS_2 : bit > + < BCC : bit (3) > ; + +< Neighbour parameter set struct > ::= +{ 0 | 1 < NCC : bit (3) > } + < EXC_ACC : bit > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > } + { 0 | 1 < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < PRIORITY_CLASS : bit (3) > } + { 0 | 1 < HCS_THR : bit (5) > } + { 0 | 1 < SI13_PBCCH_LOCATION : < SI13_PBCCH_LOCATION struct > > } + < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > + < GPRS_RESELECT_OFFSET : bit (5) > ; + +< COMPACT Neighbour Cell params 2 struct > ::= +{ 00 -- Message escape + { 1 < COMPACT NCP2 Repeat struct > + < CELL_PARAMS_POINTER : bit (2) > } ** 0 -- Up to four pointers to the 'C Neighbour parameter set' + < COMPACT Neighbour parameter set : + < COMPACT Neighbour parameter set struct > > * (1+ max(val(CELL_PARAMS_POINTER))) + ! < Message escape: { 01 | 10 | 11 } bit** = < no string >> } ; -- Reserved for future use + +< COMPACT NCP2 Repeat struct > ::= +{ 1 < START_FREQUENCY : bit (10) > -- Multiple START FREQ/FREQ DIFF sets may be defined + < COMPACT NCP2 Property struct > + { < NR_OF_REMAINING_CELLS : { bit (4) - 0000 } > + < FREQ_DIFF_LENGTH : bit (3) > + { < FREQUENCY_DIFF : bit (1 + val(FREQ_DIFF_LENGTH)) > + < COMPACT NCP2 Property struct > } * (val(NR_OF_REMAINING_CELLS)) + < COMPACT NCP2 Repeat struct > -- Repeated recursively + | 0000 } -- Break recursion (NR_OF_REMAINING_CELLS == 0) + | 0 } ; -- End recursion (no more START_FREQUENCY) + +< COMPACT NCP2 Property struct > ::= + < SAME_RA_AS_SERVING_CELL : bit (1) > + < CELL_BAR_ACCESS_2 : bit > + < BCC : bit (3) > + { 0 | 1 < TIME_GROUP : bit (2) > } ; + +< COMPACT Neighbour parameter set struct > ::= +{ 0 | 1 < NCC : bit (3) > } + < EXC_ACC : bit > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > } + { 0 | 1 < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_PRIORITY_CLASS : bit (3) > } + { 0 | 1 < GPRS_HCS_THR : bit (5) > } + < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) > + < GPRS_RESELECT_OFFSET : bit (5) > + { 0 | 1 < GUAR_CONSTANT_PWR_BLKS : bit (2) > } ; +``` + +``` +< CCN Support Description struct > ::= +< Number_Cells : bit (7) > +{ CCN_SUPPORTED : bit } * (val(Number_Cells)); + +< lu mode neighbour cell params struct > ::= + < NR_OF_REMAINING_CELLS : bit (4) > + { 0 | 1 < lu Mode Cell Selection Params : > } * (val(NR_OF_REMAINING_CELLS)); + +< lu Mode Cell Selection struct > ::= + < CELL BAR QUALIFY 3 : bit (2) > + { 0 | 1 < SI13Alt PBCCH Location : < SI13 PBCCH Location struct > > }; + +< lu mode Only Neighbour Cell params struct > ::= + < START_FREQUENCY : bit (10) > + < lu mode Only Cell selection params : < lu mode Only Cell Selection struct > > + < NR_OF_REMAINING_CELLS : bit (4) > + < FREQ_DIFF_LENGTH : bit (3) > + { + < FREQUENCY_DIFF : bit (1 + val(FREQ_DIFF_LENGTH)) > + < lu mode Only Cell Selection params : + < lu mode Only Cell Selection struct > > } * (val(NR_OF_REMAINING_CELLS)); + +< lu Mode Only Cell Selection struct > ::= + < BSIC : bit (6) > + < CELL BAR QUALIFY 3 : bit (2) > + < SAME_RA_AS_SERVING_CELL : bit (1) > + { 0 | 1 < GPRS_RXLEV_ACCESS_MIN : bit (6) > + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } + { 0 | 1 < GPRS_TEMPORARY_OFFSET : bit (3) > + < GPRS_PENALTY_TIME : bit (5) } + { 0 | 1 < GPRS_RESELECT_OFFSET : bit (5) > } + { 0 | 1 < HCS params : < HCS struct > > } + { 0 | 1 < SI13Alt PBCCH Location : < SI13 PBCCH Location struct > > }; +``` + +Table 11.2.21.2: PSI3 bis information element details + +##### **PAGE\_MODE** (2 bit field) + +See description under PSI3. + +##### **PSI3\_CHANGE\_MARK** (2 bit field) + +See description under PSI3. + +#### **PSI3\_BIS\_INDEX** (4 bit field) + +The PSI3\_BIS\_INDEX field is used to distinguish individual PSI3 bis messages containing information about different neighbour cells. The field can take the binary representation of the values 0 to n, where n is the index of the last PSI3 bis message. (PSI3 bis count). + +##### **PSI3\_BIS\_COUNT** (4 bit field) + +See description under PSI3. + +#### **General rules for handling neighbour cell parameter default values** + +The first neighbour cell defined in the first PSI3bis instance uses as its default parameter values the parameter values defined for the last neighbour cell in PSI3. + +The following neighbour cells in PSI3bis use the parameter values of the previous neighbour cell as their default values. + +This principle of referring to the previous cell applies independently of the coding used in PSI3bis (Neighbour cell parameters, Neighbour cell parameters 2 and COMPACT Neighbour Cell Parameters). + +This principle also applies when going from PSI3bis instance i over to PSI3bis instance i+1. + +#### ***Neighbour cell params struct*** + +The coding of the Neighbour cell parameters is described under PSI3. + +##### ***Neighbour cell params 2 struct*** + +This coding may be used if the number of neighbour cells is high and many cells share common parameter values. The structure contains pointers to the list of sets of actual parameters. The coding of actual parameters that are contained in or referenced by the Neighbour Cell params 2 struct is described in PSI3. + +##### ***COMPACT Neighbour Cell params struct*** + +The coding of the Neighbour cell parameters is the same as the coding of the Neighbour cell params struct 2, except the two additional parameters, TIME\_GROUP and GUAR\_CONSTANT\_PWR\_BLKS. The coding of actual parameters that are contained in or referenced by the COMPACT Neighbour Cell params struct is described in PSI3. + +The following parameters (CELL\_PARAMS\_POINTER, BCC and NCC) are not defined in PSI3: + +##### **CELL\_PARAMS\_POINTER** (2 bit field) + +Pointer to the parameter set valid for a certain cell group (up to four). + +##### **BCC** (3 bit field) + +BTS Colour Code. + +##### ***Neighbour parameter set struct and COMPACT Neighbour parameter set struct*** + +The actual parameter values for the Neighbour Cell params 2 struct and the COMPACT Neighbour Cell params struct are given in these structures. Default values for absent parameters are defined according to the general rule given above, except: + +**NCC** : bit (3). Network Colour Code. The default value is given by the serving cell. + +#### **LSA Parameters IE** + +The LSA Parameters IE is described under PSI3 and in sub-clause 12.28. + +#### ***CCN Support Description*** + +##### **CCN\_SUPPORTED** (1 bit field) + +This parameter is used for determining whether the mobile station shall enter CCN mode when re-selecting a cell and CCN is enabled. The use of these bits is described in sub-clause 8.8.2a: + +Bit + +- 0** CCN is enabled towards the corresponding cell +- 1** CCN is disabled towards the corresponding cell + +#### **CELL BAR QUALIFY 3** (2 bit field) + +This information element is defined in 3GPP TS 44.018. + +##### ***Iu mode Neighbour Cell params struct*** + +This struct presents supplementary information for *Iu mode* capable cells. The struct may be included in this message and assigns *Iu mode* parameter values to the neighbouring cells defined by the message. *Iu mode* capable neighbouring cells may be defined by the *Neighbour Cell parameters* and the *Neighbour Cell parameters 2* IEs. The *Iu mode Neighbour Cell params struct* values are assigned to the neighbouring cells in the same order they appear in the PSI3 and PSI3bis messages. + +### 11.2.21a Packet System Information Type 3 ter + +This message is sent by the network on the PBCCH or PACCH giving information on additional measurement and reporting parameters. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. If not all information fits into one instance of the PSI3ter message, the PSI3ter message can be repeated. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 3 TER + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.21a.1: PSI3 ter information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < PSI3 ter message content > ::=    < PAGE_MODE : bit (2) >   < PSI3_CHANGE_MARK : bit (2) >   < PSI3_TER_INDEX : bit (4) >   < PSI3_TER_COUNT : bit (4) >   { 0   1 < Real Time Difference Description : < Real Time Difference Description struct >> }   { 0   1 < GPRS REP_PRIORITY Description : < GPRS REP_PRIORITY Description struct >> }   < padding bits > // -- truncation at end of message allowed, bits '0' assumed ! < Distribution part error : bit (*) = < no string > > ;  < Real Time Difference Description struct > ::=   { 0   1 { 0   1 < Cell_Index_Start_RTD : bit (7) > } -- default value=0     < RTD Struct : < RTD6 Struct >>     { 0 < RTD Struct : < RTD6 Struct >> } **1 } -- '0' : increment by 1 the index of the GSM Neighbour Cell list   { 0   1 { 0   1 < Cell_Index_Start_RTD : bit (7) > } -- default value=0     < RTD Struct : < RTD12 Struct >>     { 0 < RTD Struct : < RTD12 Struct >> } **1 } -- '0' : increment by 1 the index of the GSM Neighbour Cell list  < RTD6 Struct > ::=   { 0   1 < RTD : bit (6) > } ; --'0' means no RTD for this cell  < RTD12 Struct > ::=   { 0   1 < RTD : bit (12) > } ; -- '0' means no RTD for this cell  < GPRS REP_PRIORITY Description struct > ::=   < Number_Cells : bit(7) >   { < REP_PRIORITY : bit > } * (val(Number_Cells)) ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.21a.2: PSI3 ter information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
See description under PSI3.

| +|

PSI3_CHANGE_MARK (2 bit field)
See description under PSI3.

| +|

PSI3_TER_INDEX (4 bit field)
The PSI3_TER_INDEX field is used to distinguish individual PSI3 bis messages containing information about different neighbour cells. The field can take the binary representation of the values 0 to n, where n is the index of the last PSI3 ter message. (PSI3 ter count).

| +|

PSI3_TER_COUNT (4 bit field)
This field is coded as the binary representation of the PSI3 ter index (in the PSI3 ter message) for the last (highest indexed) individual PSI3 ter message.
Range: 0-15.

| +|

Real Time Difference Description

Cell_Index_Start_RTD (7 bit field)
This field indicates the GSM Neighbour Cell list index for the first RTD parameter. When missing, the value '0' is assumed.

RTD (6 or 12 bit field) is defined in 3GPP TS 45.008.
The use of these parameters is defined in sub-clause 5.6.3.4.

| + +#### ***GPRS REP PRIORITY Description*** + +##### **REP\_PRIORITY** bit: + +- 0 Normal reporting priority +- 1 High reporting priority + +The use of these bits is defined in sub-clause 5.6.3.5. + +#### 11.2.21a.1 GPRS REP PRIORITY description + +A GPRS REP PRIORITY description construction shall be included in one and only one instance of the PACKET SYSTEM INFORMATION TYPE 3 TER message within the consistent set of PACKET SYSTEM INFORMATION TYPE 3 TER messages. + +### 11.2.21b Packet System Information Type 3 quater + +This message is sent by the network on the PBCCH or PACCH giving information on 3G Neighbour Cells and additional measurement and reporting parameters. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. If not all information fits into one instance of the PSI3quater message, the PSI3quater message can be repeated. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 3 QUATER + +Direction: network to mobile station + +Classification: distribution message + +###### **Table 11.2.21b.1: PSI3 quater information elements** + +``` + +< PSI3 quater message content > ::= + < PAGE_MODE : bit (2) > + < PSI3_CHANGE_MARK : bit (2) > + < PSI3_QUATER_INDEX : bit (4) > + < PSI3_QUATER_COUNT : bit (4) > + { 0 | 1 < GPRS REP_PRIORITY Description : < GPRS REP PRIORITY Description struct >> } + { 0 | 1 < 3G Neighbour Cells Description : < 3G Neighbour Cells Description struct >> } + { 0 | 1 < 3G MEASUREMENT Parameters Description : + < 3G MEASUREMENT PARAMETERS Description struct >> } + { 0 | 1 < 3G Initial Dedicated Mode Reporting Description : + < 3G Initial Dedicated Mode Reporting Description struct >> } + { null | 0 bit** < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Release 5: + { 0 | 1 < GPRS 3G Additional Measurement Parameters Description : + < GPRS 3G Additional Measurement Parameters Description struct >> } + { 0 | 1 < GPRS 3G Additional Measurement Parameters Description 2 : + < GPRS 3G Additional Measurement Parameters Description 2 struct >> } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Release 6: + < 3G_CCN_ACTIVE : bit > + < padding bits > } } } // -- truncation at end of message allowed, bits '0' assumed ! + Distribution part error : bit (*) = < no string > > ; + +< GPRS REP PRIORITY Description struct > ::= + < Number_Cells : bit(7) > + { < REP_PRIORITY : bit > } * (val(Number_Cells)) ; + +< 3G Neighbour Cell Description struct > ::= + { 0 | 1 < Index_Start_3G : bit (7) > } + { 0 | 1 < Absolute_Index_Start_EMR : bit (7) > } + { 0 | 1 < UTRAN FDD Description : < UTRAN FDD Description struct >> } + { 0 | 1 < UTRAN TDD Description : < UTRAN TDD Description struct >> } ; + +< UTRAN FDD Description struct > ::= + { 0 | 1 < Bandwidth_FDD : bit (3) > } + { 1 < Repeated UTRAN FDD Neighbour Cells : < Repeated UTRAN FDD Neighbour Cells struct >> } ** 0 ; + +< Repeated UTRAN FDD Neighbour Cells struct > ::= + 0 < FDD-ARFCN : bit (14) > -- The value '1' was used in an earlier + -- version of the protocol and shall not be used. + < FDD_Indic0 : bit > + < NR_OF_FDD_CELLS : bit (5) > + < FDD_CELL_INFORMATION Field : bit(p(NR_OF_FDD_CELLS)) > ; + -- p(x) defined in table 11.2.9b.2.a/3GPP TS 44.060 + +< UTRAN TDD Description struct > ::= + { 0 | 1 < Bandwidth_TDD : bit (3) > } + { 1 < Repeated UTRAN TDD Neighbour Cells : < Repeated UTRAN TDD Neighbour Cells struct >> } ** 0 ; + +< Repeated UTRAN TDD Neighbour Cells struct > ::= + 0 < TDD-ARFCN : bit (14) > -- The value '1' was used in an earlier + -- version of the protocol and shall not be used. + < TDD_Indic0 : bit > + < NR_OF_TDD_CELLS : bit (5) > + < TDD_CELL_INFORMATION Field : bit(q(NR_OF_TDD_CELLS)) > ; + -- q(x) defined in table 11.2.9b.2.b/3GPP TS 44.060 + +< 3G MEASUREMENT PARAMETERS Description struct > ::= + < Qsearch_P : bit (4) > + { 1 ! < Ignore : bit = < no string >> } -- this bit shall be ignored by the receiver + -- for backward compatibility with earlier releases + { 0 | 1 < FDD_GPRS_Qoffset : bit (4) > -- FDD information + < FDD_Qmin : bit (3) > } + { 0 | 1 < TDD_GPRS_Qoffset : bit (4) > } ; -- TDD information + +``` + +``` + +< 3G Initial Dedicated Mode Reporting Description struct > ::= + < 3G_BA_IND : bit > + < Qsearch_I : bit (4) > + < Qsearch_C_Initial : bit (1) > + { 0 | 1 < FDD_Qoffset : bit (4) > -- FDD information + < FDD_REP_QUANT : bit (1) > + < FDD_MULTIRAT_REPORTING : bit (2) > } + { 0 | 1 < TDD_Qoffset : bit (4) > -- TDD information + < TDD_MULTIRAT_REPORTING : bit (2) > } ; + +< GPRS 3G Additional Measurement Parameters Description struct > ::= + < FDD_Qmin_Offset : bit (3) > -- FDD information + < FDD_RSCPmin : bit (4) > ; + +< GPRS 3G Additional Measurement Parameters Description 2 struct > ::= + { 0 | 1 < FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; -- FDD information + +``` + +Table 11.2.21b.2: PSI3 quater information element details + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PAGE_MODE (2 bit field)
See description under PSI3. | +| PSI3_CHANGE_MARK (2 bit field)
See description under PSI3. | +| PSI3_QUATER_INDEX (4 bit field)
The PSI3_QUATER_INDEX field is used to distinguish individual PSI3 quater messages containing information about different neighbour cells. The field can take the binary representation of the values 0 to n, where n is the index of the last PSI3 quater message. (PSI3 quater count). | +| PSI3_QUATER_COUNT (4 bit field)
This field is coded as the binary representation of the PSI3 quater index (in the PSI3 quater message) for the last (highest indexed) individual PSI3 quater message.
Range: 0-15. | +| GPRS REP PRIORITY Description

REP_PRIORITY bit:
0 Normal reporting priority
1 High reporting priority

The use of these bits is defined in sub-clause 5.6.3.5 ("GPRS Report Priority Description"). | + +#### ***3G Neighbour Cell Description*** + +The building of the 3G Neighbour Cell list and the ordering of indices within each Radio Access Technology is described in sub-clause 5.6.3.1. + +##### **Index\_Start\_3G (7 bit)** + +This optional information element indicates the value of the first index to use to build this instance of the 3G Neighbour Cell list. When missing, the value 0 is assumed. See sub-clause 5.6.3.1. + +##### **Absolute\_Index\_Start\_EMR (7 bit)** + +This parameter indicates the value to be added to the indexes of the 3G Neighbour Cell list for reporting 3G Cells with the PACKET ENHANCED MEASUREMENT REPORT message (see sub-clause 5.6.3.3). If different values are received for this parameter in different instances of this message, the instance with the highest index shall be used. If this parameter is absent in all instances of the message, the value "0" shall be used. + +NOTE: This parameter is not used for reporting 3G Cells with the PACKET MEASUREMENT REPORT message, see sub-clause 11.2.9. + +#### **UTRAN FDD Description:** + +For detailed element definitions see the Packet Measurement Order message with the following exception for the FDD\_CELL\_INFORMATION Field: + +##### **FDD\_CELL\_INFORMATION Field (p bit field)** + +If parameter *n* in table 11.2.9b.2.a is equal to 31, this indicates that the corresponding UARFCN shall be included in the GPRS 3G Cell Reselection list (see sub-clause 5.6.3.7); no index shall be allocated in the 3G Neighbour Cell list. + +#### **UTRAN TDD Description:** + +For detailed element definitions see the Packet Measurement Order message with the following exception for the TDD\_CELL\_INFORMATION Field: + +##### **TDD\_CELL\_INFORMATION Field (q bit field)** + +If parameter *m* in table 11.2.9b.2.b is equal to 31, this indicates that the corresponding UARFCN shall be included in the GPRS 3G Cell Reselection list (see sub-clause 5.6.3.7); no index shall be allocated in the 3G Neighbour Cell list. + +#### ***3G MEASUREMENT PARAMETERS Description*** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +##### ***3G Initial Dedicated Mode Reporting Description*** + +These parameters shall only be used in initial 3G neighbour cell reporting in dedicated mode. + +##### **3G\_BA\_IND (1 bit field)** + +The 3G\_BA\_IND is needed to identify set of 3G Neighbour Cell information used for reporting in dedicated mode. The value received is reflected in the MEASUREMENT REPORT and ENHANCED MEASUREMENT REPORT messages, see 3GPP TS 44.018 'Parameters for Measurements and Reporting'. + +The other fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +##### ***GPRS 3G Additional Measurement Parameters Description*** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +If the *GPRS 3G Additional MeasurementParameters Description* is included in more than one instance of the PSI3quater message, the *GPRS 3G Additional MeasurementParameters Description* of the instance with the highest PSI3quater\_INDEX shall be used. + +##### **3G\_CCN\_ACTIVE (1 bit field)** + +This field indicates whether CCN is enabled towards 3G neighbouring cells. It is coded as follows: + +- 0 CCN towards 3G cells is disabled in the cell. +- 1 CCN towards 3G cells is enabled in the cell. + +##### ***GPRS 3G Additional Measurement Parameters Description 2*** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +If the *GPRS 3G Additional Measurement Parameters Description 2* is included in more than one instance of the PSI3quater message, the *GPRS 3G Additional Measurement Parameters Description 2* of the instance with the highest PSI3quater\_INDEX shall be used. + +#### **11.2.21b.1 GPRS REP PRIORITY description** + +A GPRS REP PRIORITY description construction shall be included in one and only one instance of the PACKET SYSTEM INFORMATION TYPE 3 QUATER message within the consistent set of PACKET SYSTEM INFORMATION TYPE 3 QUATER messages. + +### **11.2.22 (void)** + +### **11.2.23 Packet System Information Type 5** + +This optional message is sent by the network on the PBCCH giving information for measurement reporting and network controlled cell reselection. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. If not all information fits into one message, the remaining information will be sent in other instances of the PSI5 message. The message is sent on PBCCH only if so indicated in PSI1. + +Message type: PACKET SYSTEM INFORMATION TYPE 5 + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.23.1: PSI5 information elements** + +``` + +< PS15 message content > ::= + < PAGE_MODE : bit (2) > + < PS15_CHANGE_MARK : bit (2) > + < PS15_INDEX : bit (3) > + < PS15_COUNT : bit (3) > + { 0 | 1 < NC Measurement Parameters : < NC Measurement Parameters struct > > } + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + { null | 0 bit** = -- Receiver backward compatible with earlier release + | 1 -- Additional contents for R99 + { 0 | 1 < ENH Reporting Parameters : < ENH Reporting Parameters struct > > } + { null | 0 bit** = -- Receiver compatible with earlier release + | 1 -- Additions in Rel-5: + { 0 | 1 < GPRS 3G Additional Measurement Parameters Description 2 : + < GPRS 3G Additional Measurement Parameters Description 2 struct > > } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-7 : + { 0 | 1 < 700_REPORTING_OFFSET : bit (3) > + < 700_REPORTING_THRESHOLD : bit (3) > } + { 0 | 1 < 810_REPORTING_OFFSET : bit (3) > + < 810_REPORTING_THRESHOLD : bit (3) > } + < padding bits > } } } } + ! < Distribution part error : bit (*) = < no string > > ; + +< NC Measurement Parameters struct > ::= + < NETWORK_CONTROL_ORDER : bit (2) > + { 0 | 1 < NC_NON_DRX_PERIOD : bit (3) > + < NC_REPORTING_PERIOD_I : bit (3) > + < NC_REPORTING_PERIOD_T : bit (3) > } ; + +< ENH Reporting parameters struct > ::= + < Report_Type : bit > + < REPORTING_RATE : bit > + < INVALID_BSIC_REPORTING : bit > + { 0 | 1 < NCC_PERMITTED : bit (8) > } + { 0 | 1 < GPRS MEASUREMENT Parameters Description : + < GPRS MEASUREMENT Parameters Description struct > > } + { 0 | 1 < GPRS 3G MEASUREMENT Parameters Description : + < GPRS 3G MEASUREMENT Parameters Description struct > > } ; + +< GPRS MEASUREMENT PARAMETERS Description struct > ::= + { 0 | 1 < MULTIBAND_REPORTING : bit (2) > } + { 0 | 1 < SERVING_BAND_REPORTING : bit (2) > } + { 0 | 1 < SCALE_ORD : bit (2) > } + + { 0 | 1 < 900_REPORTING_OFFSET : bit (3) > + < 900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1800_REPORTING_OFFSET : bit (3) > + < 1800_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 400_REPORTING_OFFSET : bit (3) > + < 400_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 1900_REPORTING_OFFSET : bit (3) > + < 1900_REPORTING_THRESHOLD : bit (3) > } + + { 0 | 1 < 850_REPORTING_OFFSET : bit (3) > + < 850_REPORTING_THRESHOLD : bit (3) > } ; + +``` + +``` + +< GPRS 3G MEASUREMENT PARAMETERS Description struct > ::= + { 0 | 1 < FDD REP QUANT : bit > -- FDD Parameters + < FDD MULTIRAT REPORTING : bit (2) > } + { 0 | 1 < FDD REPORTING OFFSET : bit (3) > + < FDD REPORTING THRESHOLD : bit (3) > } + + { 0 | 1 < TDD MULTIRAT REPORTING : bit (2) > -- TDD Parameters + { 0 | 1 < TDD REPORTING OFFSET : bit (3) > + < TDD REPORTING THRESHOLD : bit (3) > } ; + +< GPRS 3G Additional Measurement Parameters 2 struct > ::= + { 0 | 1 < FDD REPORTING THRESHOLD 2 : bit (6) > } ; -- FDD Parameters + +``` + +**Table 11.2.23.2: PSI5 information element details** + +The optional PSI5 message contains broadcast measurement parameters for Network Control (NC) measurements containing the NC Measurement Parameters. The NC Measurement parameters struct shall only exist in one instance of the PSI5 message. If the NC Measurement parameters struct is included in more than one instance, the value of the struct in the instance with the highest index shall be valid and all others shall be ignored. + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **PSI5\_CHANGE\_MARK** (2 bit field) + +The PSI5\_CHANGE\_MARK field is changed each time information has been updated in any of the individual instances of the PSI5 message. A new value indicates that the mobile station shall re-read the information from all PSI5 messages. Range: 0 to 3. The coding of this field is network dependent. + +#### **PSI5\_INDEX** (3 bit field) and **PSI5\_COUNT** (3 bit field) + +The purpose of the PSI5\_INDEX field and the PSI5\_COUNT field is to indicate the number of individual messages within the sequence of PSI5 messages and to assign an index to identify each one of them. The PSI5\_INDEX field is binary coded, range: 0 to 7, and provides an index to identify the individual PSI5 message. The PSI5\_COUNT field is binary coded, range: 0 to 7, and provides the PSI5\_INDEX value for the last (highest indexed) message in the sequence of PSI5 messages. + +#### **NETWORK\_CONTROL\_ORDER** (2 bit field) + +The NETWORK\_CONTROL\_ORDER field is coded according to the following table (for definition of NCx see 3GPP TS 45.008): + +| bit | | +|-----|------------| +| 2 | 1 | +| 0 | 0 NC0 | +| 0 | 1 NC1 | +| 1 | 0 NC2 | +| 1 | 1 Reserved | + +If the NETWORK\_CONTROL\_ORDER parameter = NC0, then the other parameters in the NC Measurement parameters struct may be omitted. If the NETWORK\_CONTROL\_ORDER parameter indicates NC1 or NC2 and the other parameters are omitted, the default value for these parameters shall be assumed. + +| | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------------------|-------|--------|-------|---------------------------------|-------|-----------------------------------------------------------|-------|--------|-------|---------|-------|---------|-------|------------------------------------------------------------| +|

NC_NON_DRX_PERIOD (3 bit field)
This field indicates the minimum time the mobile station shall stay in non-DRX mode after an NC-measurement report has been sent. The field is coded according to the following table:

bit
3 2 1
0 0 0 No non-DRX mode after a measurement report has been sent.
0 0 1 0,24 s
0 1 0 0,48 s (default value)
0 1 1 0,72 s
1 0 0 0,96 s
1 0 1 1,20 s
1 1 0 1,44 s
1 1 1 1,92 s
| bit | | 3 2 1 | | 0 0 0 | No non-DRX mode after a measurement report has been sent. | 0 0 1 | 0,24 s | 0 1 0 | 0,48 s ( default value ) | 0 1 1 | 0,72 s | 1 0 0 | 0,96 s | 1 0 1 | 1,20 s | 1 1 0 | 1,44 s | 1 1 1 | 1,92 s | +| bit | | | | | | | | | | | | | | | | | | | | | +| 3 2 1 | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 | No non-DRX mode after a measurement report has been sent. | | | | | | | | | | | | | | | | | | | | +| 0 0 1 | 0,24 s | | | | | | | | | | | | | | | | | | | | +| 0 1 0 | 0,48 s ( default value ) | | | | | | | | | | | | | | | | | | | | +| 0 1 1 | 0,72 s | | | | | | | | | | | | | | | | | | | | +| 1 0 0 | 0,96 s | | | | | | | | | | | | | | | | | | | | +| 1 0 1 | 1,20 s | | | | | | | | | | | | | | | | | | | | +| 1 1 0 | 1,44 s | | | | | | | | | | | | | | | | | | | | +| 1 1 1 | 1,92 s | | | | | | | | | | | | | | | | | | | | +|

NC_REPORTING_PERIOD_I (3 bit field)
NC_REPORTING_PERIOD_T (3 bit field)
These fields indicate the time period for cell reselection measurement reporting for packet idle mode (I) and packet transfer mode (T), respectively. The field is coded according to the following table:

bit
3 2 1
0 0 0 0,48 s
0 0 1 0,96 s
0 1 0 1,92 s
0 1 1 3,84 s (default value for NC_REPORTING_PERIOD_T)
1 0 0 7,68 s
1 0 1 15,36 s
1 1 0 30,72 s
1 1 1 61,44 s (default value for NC_REPORTING_PERIOD_I)
| bit | | 3 2 1 | | 0 0 0 | 0,48 s | 0 0 1 | 0,96 s | 0 1 0 | 1,92 s | 0 1 1 | 3,84 s ( default value for NC_REPORTING_PERIOD_T ) | 1 0 0 | 7,68 s | 1 0 1 | 15,36 s | 1 1 0 | 30,72 s | 1 1 1 | 61,44 s ( default value for NC_REPORTING_PERIOD_I ) | +| bit | | | | | | | | | | | | | | | | | | | | | +| 3 2 1 | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 | 0,48 s | | | | | | | | | | | | | | | | | | | | +| 0 0 1 | 0,96 s | | | | | | | | | | | | | | | | | | | | +| 0 1 0 | 1,92 s | | | | | | | | | | | | | | | | | | | | +| 0 1 1 | 3,84 s ( default value for NC_REPORTING_PERIOD_T ) | | | | | | | | | | | | | | | | | | | | +| 1 0 0 | 7,68 s | | | | | | | | | | | | | | | | | | | | +| 1 0 1 | 15,36 s | | | | | | | | | | | | | | | | | | | | +| 1 1 0 | 30,72 s | | | | | | | | | | | | | | | | | | | | +| 1 1 1 | 61,44 s ( default value for NC_REPORTING_PERIOD_I ) | | | | | | | | | | | | | | | | | | | | +|

NCC_PERMITTED (8 bit field)
This field is a bitmap of NCCs for which the mobile station is permitted to report measurement; this bitmap relates to NCC part of BSIC (see coding field in 3GPP TS 44.018).

| | | | | | | | | | | | | | | | | | | | | +|

ENH Reporting Parameters (Enhanced Measurement reporting parameters)

Report_Type (1bit)
This parameter is used to indicate to the mobile station to use the PACKET ENHANCED MEASUREMENT REPORT message or the PACKET MEASUREMENT REPORT message for (NC) reporting:

Bit
0 The MS shall use the PACKET ENHANCED MEASUREMENT REPORT message for (NC) reporting
1 The MS shall use the PACKET MEASUREMENT REPORT message for (NC) reporting.
| Bit | | 0 | The MS shall use the PACKET ENHANCED MEASUREMENT REPORT message for (NC) reporting | 1 | The MS shall use the PACKET MEASUREMENT REPORT message for (NC) reporting. | | | | | | | | | | | | | | | +| Bit | | | | | | | | | | | | | | | | | | | | | +| 0 | The MS shall use the PACKET ENHANCED MEASUREMENT REPORT message for (NC) reporting | | | | | | | | | | | | | | | | | | | | +| 1 | The MS shall use the PACKET MEASUREMENT REPORT message for (NC) reporting. | | | | | | | | | | | | | | | | | | | | +|

REPORTING_RATE (1 bit)
This parameter is used for measurements, see 3GPP TS 45.008.

Bit

0 normal rate reporting
1 Reduced reporting rate allowed.
| 0 | normal rate reporting | 1 | Reduced reporting rate allowed. | | | | | | | | | | | | | | | | | +| 0 | normal rate reporting | | | | | | | | | | | | | | | | | | | | +| 1 | Reduced reporting rate allowed. | | | | | | | | | | | | | | | | | | | | +|

INVALID_BSIC_REPORTING (1 bit)
This field specifies if cells with invalid BSIC and allowed NCC part of BSIC are allowed to be reported or not, see 3GPP TS 45.008.

Bit

0 Report on cells with invalid BSIC and allowed NCC part of BSIC is not allowed.
1 Report on cells with invalid BSIC and allowed NCC part of BSIC is allowed. In this case NCC_PERMITTED is required.
| 0 | Report on cells with invalid BSIC and allowed NCC part of BSIC is not allowed. | 1 | Report on cells with invalid BSIC and allowed NCC part of BSIC is allowed. In this case NCC_PERMITTED is required. | | | | | | | | | | | | | | | | | +| 0 | Report on cells with invalid BSIC and allowed NCC part of BSIC is not allowed. | | | | | | | | | | | | | | | | | | | | +| 1 | Report on cells with invalid BSIC and allowed NCC part of BSIC is allowed. In this case NCC_PERMITTED is required. | | | | | | | | | | | | | | | | | | | | +|

GPRS MEASUREMENT PARAMETERS Description
The fields of this Description are used for measurements as defined in 3GPP TS 45.008.

| | | | | | | | | | | | | | | | | | | | | + +**GPRS 3G MEASUREMENT PARAMETERS Description** + +The fields of this Description are used for measurements as defined in 3GPP TS 45.008. + +--- + +**GPRS 3G Additional Measurement Parameters 2 Description** + +The fields of this Description are used for measurements, as defined in 3GPP TS 45.008. + +--- + +**700\_REPORTING\_OFFSET** (3 bit field) + +**700\_REPORTING\_THRESHOLD** (3 bit field) + +These fields are used for measurements, as defined in 3GPP TS 45.008. + +--- + +**810\_REPORTING\_OFFSET** (3 bit field) + +**810\_REPORTING\_THRESHOLD** (3 bit field) + +These fields are used for measurements, as defined in 3GPP TS 45.008. + +### 11.2.23a Packet System Information Type 6 + +This optional message is sent by the network on the PBCCH or PACCH to provide broadcast information required by non-GSM networks. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. If not all information fits into one instance of the PSI6 message, the PSI6 message can be repeated.. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 6 + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.23a.1: PSI6 information elements** + +``` +< PSI6 message content > ::= + < PAGE_MODE : bit (2) > + < PSI6_CHANGE_MARK : bit (2) > + < PSI6_INDEX : bit (3) > + < PSI6_COUNT : bit (3) > + { { < NonGSM Message : < Non-GSM Message struct > > ** + -- The Non-GSM Message struct is repeated until: + { < spare bit > * 3 00000 } -- A) val(NR_OF_CONTAINER_OCTETS) = 0, or + < padding bits > } // -- B) the PSI message is fully used + ! < Distribution part error : bit (*) = < no string > > ; + +< NonGSM Message struct > ::= + < NonGSM Protocol Discriminator : bit(3) > + < NR_OF_CONTAINER_OCTETS : bit(5) exclude 00000 } > + { < CONTAINER : bit(8) > } * (val(NR_OF_CONTAINER_OCTETS)) ; +``` + +**Table 11.2.23a.2: PSI6 information element details** + +**PAGE\_MODE** (2 bit field) + This field is defined in sub-clause 12.20. + +--- + +**PSI6\_CHANGE\_MARK** (2 bit field) + +The PSI6 change mark field is changed each time information has been updated in any of the PSI6 messages. A new value indicates that the mobile station shall re-read the information from the PSI6 message. The coding of this field is network dependent. + +Range: 0-3. + +#### **PSI6\_INDEX (3 bit field) and PSI6\_COUNT (3 bit field)** + +The purpose of the PSI6\_INDEX field and the PSI6\_COUNT field is to indicate the number of individual messages within the sequence of PSI6 messages and to assign an index to identify each one of them. The PSI6\_INDEX field is binary coded, range: 0 to 7, and provides an index to identify the individual PSI6 message. The PSI6\_COUNT field is binary coded, range: 0 to 7, and provides the PSI6\_INDEX value for the last (highest indexed) message in the sequence of PSI6 messages. + +#### **NonGSM Protocol Discriminator (3 bit field)** + +This information element is used to identify the non-GSM network for which a PSI6 message is transmitted and is coded as shown below. + +Bit +3 2 1 + +0 0 1 TIA/EIA-136 + +All other values are reserved + +#### **NR\_OF\_CONTAINER\_OCTETS (5 bit field)** + +This field indicates the number of CONTAINER octets that forms a specific non-GSM message and is coded as shown below. + +Bit +5 4 3 2 1 + +0 0 0 0 1 CONTAINER length is 1 octet + +0 0 0 1 0 CONTAINER length is 2 octets + +.... through ... + +1 0 0 1 1 CONTAINER length is 19 octets + +1 1 1 1 1 The remaining portion of the PSI message is used by the associated CONTAINER. The Non-GSM message continues in a subsequent instance of the PSI message, in the next CONTAINER with the same **Non-GSM Protocol Discriminator** value as the current one. + +All other values are reserved. + +##### **CONTAINER (8 bits)** + +The concatenation of one or several CONTAINER octets forms the actual contents, specific to the non-GSM network soliciting the transmission of a PSI6 message. + +### 11.2.23b Packet System Information Type 7 + +This optional message is sent by the network on the PBCCH or PACCH to provide broadcast information required by non-GSM networks. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. If not all information fits into one instance of the PSI7 message, the PSI7 message can be repeated.. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 7 + +Direction: network to mobile station + +Classification: distribution message + +The PSI7 information elements are equal to the PSI6 elements defined in sub-clause 11.2.23a. + +### 11.2.24 Packet System Information Type 8 + +This message is optionally sent by the network on the PBCCH and PACCH giving information about Cell Broadcast Channel configuration and Dynamic ARFCN Mapping. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. Special requirements for the transmission of this message apply on PBCCH, see 3GPP TS 45.002. + +Message type: PACKET SYSTEM INFORMATION TYPE 8 + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.24.1: PSI8 information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < PSI8 message content > ::=    < PAGE_MODE : bit (2) >   < PSI8_CHANGE_MARK : bit (2) >   < PSI8_INDEX : bit (3) >   < PSI8_COUNT : bit (3) >   { 0   1 < CBCH Channel Description : < CBCH Channel Description struct > > }   { null   0 bit** = < no string >     1                               -- Release 4 additions:     { 0   1 < Dynamic ARFCN Mapping Description : < Dynamic ARFCN Mapping Description struct > > }     < padding bits > }   ! < Distribution part error : bit (*) = < no string > > ;  < CBCH Channel Description struct > ::=   < Channel type and TDMA offset : bit (5) >   < TN : bit (3) >   < Frequency Parameters : < Frequency Parameters IE > > ;  < Dynamic ARFCN Mapping Description struct > ::=   { 0   1 < DM_CHANGE_MARK : bit (4) > }   { 1 < DYNAMIC ARFCN MAPPING > } ** 0 ;  < DYNAMIC ARFCN MAPPING > ::=   < GSM_Band : bit (4) >   < ARFCN_FIRST : bit (10) >         -- Dynamic ARFCN mapping parameters   < BAND_OFFSET : bit (10) >   < ARFCN_RANGE : bit (7) > ;
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.24.2: PSI8 information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

PSI8_INDEX (3 bit field) and PSI8_COUNT (3 bit field)
These fields are the binary representation of the PSI index and PSI count parameters associated with the PSI8 messages.

PSI8_CHANGE_MARK (2 bit field)
The PSI8 change mark field is changed each time information has been updated in the PSI8 message. A new value indicates that the mobile station shall re-read the information from the PSI8 message. The coding of this field is network dependent. Range: 0-3.

CBCH Channel Description struct
The CBCH Channel Description provides the description for the CBCH. If the CBCH Channel Description is not available (either as it is not included in any instance of PSI8 or as no PSI8 is broadcast at all), the mobile station can assume that SMSCB is not active in the cell. If available, the CBCH Channel Description construction shall be included in one and only one instance of the PSI8 message within the consistent set of PSI8 messages

Channel type and TDMA offset (5 bit field)
For encoding and description see 3GPP TS 44.018 .

TN, Timeslot number(3 bit field)
The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.002.

Frequency Parameters
This information element is defined in sub-clause 12.8.

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**DM\_CHANGE\_MARK** (4 bit field), Dynamic ARFCN Mapping Change Mark. + +This parameter is used to indicate to the MS a change of information concerning Dynamic ARFCN Mapping. This field shall be present in only one instance of Dynamic ARFCN Mapping Description struct in a consistent set of PSI8 messages. + +Dynamic ARFCN Mapping parameters description: + +These parameters allow to allocate ARFCN values and then dynamically map to physical frequencies, see 3GPP TS 45.005. The parameters of this description are defined in 3GPP TS 44.018. + +If the mobile station receives more than 8 DYNAMIC\_ARFCN\_MAPPING structures, it shall store at least the 8 first structures in the order of occurrence, starting with the PSI8 instance with the lowest index number. + +### 11.2.25 Packet System Information 13 + +This message may be broadcast by the network on the PACCH or on the PCCCH (see sub-clause 5.5.2.1). The message provides the mobile station with GPRS cell specific access-related information. The information in this message shall be the same as provided in the SI13 message on BCCH, see 3GPP TS 44.018. This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. + +Message type: PACKET SYSTEM INFORMATION TYPE 13 + +Direction: network to mobile station + +Classification: distribution message + +Table 11.2.25.1: PSI3 information elements + +``` + +< PSI13 message content > ::= + < PAGE_MODE : bit (2) > + < BCCH_CHANGE_MARK : bit (3) > + < SI_CHANGE_FIELD : bit (4) > + { 0 | 1 < SI13_CHANGE_MARK : bit (2) > + < GPRS Mobile Allocation : < GPRS Mobile Allocation IE > > } + { 0 -- PBCCH not present in cell (This shall always be indicated. See sub-clause 1.6): + < RAC : bit (8) > + < SPGC_CCCH_SUP : bit > + < PRIORITY_ACCESS_THR : bit (3) > + < NETWORK_CONTROL_ORDER : bit (2) > + < GPRS Cell Options : < GPRS Cell Options IE > > + < GPRS Power Control Parameters : < GPRS Power Control Parameters IE > > + | 1 -- PBCCH present in cell (This shall never be indicated. See sub-clause 1.6): + < PSI1_REPEAT_PERIOD : bit (4) > + < PBCCH Description : < PBCCH Description struct > > } + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release 99 : + < SGSNR : bit > + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in release R4 : + < SI_STATUS_IND : bit > + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-6: + { 0 | 1 < LB_MS_TXPWR_MAX_CCH : bit (5) > } + < SI2n_SUPPORT : bit (2) > + { null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-11: + < SI_CHANGE_ALT : bit > + < padding bits > } } } } + ! < Distribution part error : bit (*) = < no string > > ; + +< PBCCH Description struct > ::= + < Pb : bit (4) > + < TSC : bit (3) > + < TN : bit (3) > + { 0 -- default to BCCH carrier + | 10 < ARFCN : bit (10) > + | 11 < MAIO : bit (6) > } ; + +``` + +Table 11.2.25.2: PSI3 information element details + +#### **PAGE\_MODE** (2 bit field) + +This field describes which type of page mode used, i.e. either normal paging, extended paging, paging reorganization or same as before from the previous page mode. The mobile station shall ignore this field if the message is received on the PACCH. Coding of this field is defined in 3GPP TS 44.018. + +#### **BCCH\_CHANGE\_MARK** (3 bit field) + +This field indicates the status of the information on BCCH. The value of this field shall be changed each time the information on BCCH, except for the contents of the SI-13 message, is changed. + +#### **SI\_CHANGE\_FIELD** (4 bit field) + +This field is the binary representation of which information was changed at the last indication in BCCH\_CHANGE\_MARK. Range 0 to 15: + +bit + +4 3 2 1 + +0 0 0 0 Update of *unspecified* SI message or SI messages; + +0 0 0 1 Update of SI1 message; + +0 0 1 0 Update of SI2, SI2 bis or SI2 ter message or any instance of SI2quater messages; + +0 0 1 1 Update of SI3, SI4, SI7, SI8, SI16 or SI17 message; + +0 1 0 0 Update of SI9 message; + +0 1 0 1 Update of SI18 or SI20 message; + +0 1 1 0 Update of SI19 message; 0 1 1 1 Update of SI15 message; + +1 0 0 0 Update of SI2n message; + +1 0 0 1 Update of SI22 or SI23 message; + +All other values shall be interpreted as 'update of unknown SI message type'. + +#### **SI13\_CHANGE\_MARK** (2 bit field) + +This field is the binary representation of the SI change mark identifying the GPRS Mobile Allocation provided in SI13 and PSI13 messages. + +Range: 0 to 3. + +#### **GPRS Mobile Allocation** (information element) + +This information element is the representation of the GPRS mobile allocation provided in SI13 and PSI13 messages. It is identified by MA\_NUMBER = 14 when referenced from a packet assignment message. When used in SI13 or PSI13 message, this information element shall refer to the cell allocation defined for the cell in SI1 or PSI2. + +##### **RAC** (8 bit field) + +This field is the binary representation of the Routing Area Code, see 3GPP TS 23.003. + +#### **SPGC\_CCCH\_SUP** (bit field) + +This field indicates the support of the parameter SPLIT\_PG\_CYCLE on CCCH from the network side: + +0 SPLIT\_PG\_CYCLE is not supported on CCCH in this cell; + +1 SPLIT\_PG\_CYCLE is supported on CCCH in this cell. + +The **PRIORITY\_ACCESS\_THR** field (3 bit) is the binary representation of the parameter PRIORITY\_ACCESS\_THR: + +bit + +3 2 1 + +0 0 0 packet access is not allowed in the cell; + +0 0 1 spare, shall be interpreted as '000' (packet access not allowed); + +0 1 0 spare, shall be interpreted as '000' (packet access not allowed); + +0 1 1 packet access is allowed for priority level 1; + +1 0 0 packet access is allowed for priority level 1 to 2; + +1 0 1 packet access is allowed for priority level 1 to 3; + +1 1 0 packet access is allowed for priority level 1 to 4; + +1 1 1 spare, shall be interpreted as '110' (packet access allowed). + +The **NETWORK\_CONTROL\_ORDER** field (2 bit) is the binary representation of the parameter NETWORK\_CONTROL\_ORDER, see 3GPP TS 45.008: + +bit + +2 1 + +0 0 NC0: MS controlled cell re-selection, no measurement reporting. + +0 1 NC1: MS controlled cell re-selection, MS sends measurement reports. + +1 0 NC2: Network controlled cell re-selection, MS sends measurement reports. + +1 1 Reserved for future use, interpreted as NC0 by mobile station. + +#### **GPRS Cell Options** (information element) + +The *GPRS Cell Option* information element is defined in sub-clause 12.24. + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--|---------|--|---------|-----------------------------------|---------|------------------------------------|---|--|---------|-------------------------------------| +| PSI1_REPEAT_PERIOD (4 bit field)
This field is the representation of the PSI1 repeat period. The field is coded according to the following table:

bit
4 3 2 1
0 0 0 0 PSI1 repeat period = 1 multiframe
0 0 0 1 PSI1 repeat period = 2 multiframes
⋮
1 1 1 1 PSI1 repeat period = 16 multiframes
| bit | | 4 3 2 1 | | 0 0 0 0 | PSI1 repeat period = 1 multiframe | 0 0 0 1 | PSI1 repeat period = 2 multiframes | ⋮ | | 1 1 1 1 | PSI1 repeat period = 16 multiframes | +| bit | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | +| 0 0 0 0 | PSI1 repeat period = 1 multiframe | | | | | | | | | | | | +| 0 0 0 1 | PSI1 repeat period = 2 multiframes | | | | | | | | | | | | +| ⋮ | | | | | | | | | | | | | +| 1 1 1 1 | PSI1 repeat period = 16 multiframes | | | | | | | | | | | | +| GPRS Power Control Parameters (information element)
The GPRS Power Control Parameters information element is defined in sub-clause 12.09a. | | | | | | | | | | | | | +| PBCCH Description struct
The PBCCH description struct provides the channel description for the PBCCH. The frequency description for the PBCCH may be specified by an ARFCN (non-hopping radio frequency channel) or a MAIO (hopping radio frequency channel) field. In case of a hopping radio frequency channel, the PBCCH shall use the GPRS mobile allocation specified in this message. If none of the ARFCN or MAIO fields are present, the PBCCH shall use the BCCH carrier. | | | | | | | | | | | | | +| Pb (4 bit field)
For encoding and description see the Global Power Control Parameters IE. | | | | | | | | | | | | | +| TSC (3 bit field)
This field is the binary representation of the training sequence code used for PBCCH.
Range: 0 to 7. | | | | | | | | | | | | | +| TN (3 bit field)
This field is the binary representation of the timeslot number for the PBCCH.
Range: 0 to 7. | | | | | | | | | | | | | +| ARFCN (10 bit field)
This field is the binary representation of the absolute RF channel number.
Range: 0 to 1023. | | | | | | | | | | | | | +| MAIO (6 bit field)
This field is the binary representation of the mobile allocation index offset.
Range: 0 to 63. | | | | | | | | | | | | | +| SGSNR (bit field)
This field indicates the Release of the SGSN:
0 SGSN is Release '98 or older
1 SGSN is Release '99 onwards. | | | | | | | | | | | | | +| SI_STATUS_IND (1 bit field):
0 The network does not support the PACKET SI STATUS message;
1 The network supports the PACKET SI STATUS message. | | | | | | | | | | | | | +| LB_MS_TXPWR_MAX_CCH (5 bit field)

The LB_MS_TXPWR_MAX_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008. | | | | | | | | | | | | | +| SI2n_SUPPORT (2 bit field)
This field indicates the support of SI2n in the network, see 3GPP TS 44.018. | | | | | | | | | | | | | +| SI_CHANGE_ALT (1 bit field)
This field indicates how a mobile station supporting network sharing shall take into account a change of system information signalled by a SI_CHANGE_FIELD value '0010':

0 A mobile station supporting network sharing should not attempt to re-read the SI2quater message;
1 A mobile station supporting network sharing shall fully take into account a change of system information signalled by the SI_CHANGE_FIELD value '0010', SI2quater included. | | | | | | | | | | | | | + +### 11.2.25a Packet System Information 14 + +This message may be sent by the network on the PACCH. The message may provide a mobile station in dual transfer mode or the in Network Assisted Cell Change procedure with GPRS access-related information. The information may be used as a substitute for the SI13 (and in some cases, the SI1) message on BCCH after the release of an RR connection, see 3GPP TS 44.018. This message may also be used during dual transfer mode to inform the mobile station about possible changes in the SI or PSI messages. This message may also be used in the network assisted cell change procedure when the target cell has PBCCH present. + +Message type: PACKET SYSTEM INFORMATION TYPE 14 + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.25a.1: PSI14 information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < PSI14 message content > ::=   < PAGE_MODE : bit (2) >   { 0 < CCCH Access Information : < CCCH Access Information struct >>  -- This information shall always be included. See sub-clause 1.6.        1 < PBCCH Description : < PBCCH Description struct 2 >>  -- This information shall never be included. See sub-clause 1.6.     < padding bits > }   ! < Distribution part error : bit (*) = < no string >> ;
| +| 
 < CCCH Access Information struct > ::=   < BCCH_CHANGE_MARK : bit (3) >   { 0   1 < SI13_CHANGE_MARK : bit (2) >     < SI13 Mobile Allocation : < GPRS Mobile Allocation IE >> }   < SPGC_CCCH_SUP : bit >   < PRIORITY_ACCESS_THR : bit (3) >   < NETWORK_CONTROL_ORDER : bit (2) >   < GPRS Cell Options : < GPRS Cell Options IE >>   < GPRS Power Control Parameters : < GPRS Power Control Parameters struct >>   < SGSNR : bit >   { null   0 bit ** = < no string >                                  -- Receiver backward compatible with earlier version       1                                                              -- Additions for Dual Transfer Mode       0                                                              -- compatible with earlier version       < RAC : bit (8) >       < SI_STATUS_IND : bit >       { null   0 bit ** = < no string >                              -- Receiver backward compatible with earlier version           1                                                          -- Additions for Rel-6           { 0   1 < LB_MS_TXPWR_MAX_CCH : bit (5) > }           < SI2n_SUPPORT : bit (2) >       }   } };
| +| 
 < PBCCH Description struct 2 > ::=   < PSI1_REPEAT_PERIOD : bit (4) >   < Pb : bit (4) >   < TN : bit (3) >   < PBCCH Frequency Description : < Frequency Parameters IE >>   { null   0 bit ** = < no string >                                  -- Receiver backward compatible with earlier version       1                                                              -- Additions for Dual Transfer Mode       1                                                              -- compatible with earlier version       < PSI_CHANGED_IND : bit >   } };
| + +**Table 11.2.25a.2: PSI14 information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20. | +| BCCH_CHANGE_MARK (3 bit field)
This field indicates the status of the information on BCCH. The value of this field shall be changed each time the information on BCCH, except for the contents of the SI13 message, is changed, see sub-clause 5.5.2.1.4. | +| SI13_CHANGE_MARK (2 bit field)
This field is the binary representation of the SI change mark identifying the GPRS Mobile Allocation provided in SI13 and PSI13 messages. Range: 0 to 3. | +| SI13 Mobile Allocation
This field is encoded using the GPRS Mobile Allocation information element defined in sub-clause 12.10a. This information shall be identical with the GPRS mobile allocation provided in SI13 and PSI13 messages. | +| SPGC_CCCH_SUP (1 bit field)
This field is defined in the SI13 message, see 3GPP TS 44.018. | +| PRIORITY_ACCESS_THR (3 bit field)
This field is defined in the SI13 message, see 3GPP TS 44.018. | +| NETWORK_CONTROL_ORDER (2 bit field)
This field is defined in the SI13 message, see 3GPP TS 44.018. | +| GPRS Cell Options (information element)
The GPRS Cell Option information element is defined in sub-clause 12.24. | +| SGSNR (1 bit field)
This field is defined in the SI13 message, see 3GPP TS 44.018. | +| GPRS Power Control Parameters (information element)
The GPRS Power Control Parameters information element is defined in sub-clause 12.9a. | +| PSI1_REPEAT_PERIOD (4 bit field)
This field is the binary representation, range 0 to 15, of the PSI1 repeat period. The coding of this field is identical to the coding of the PSI1_REPEAT_PERIOD field in the PSI1 message. | +| Pb (4 bit field)
This is the binary representation, range 0 to 15, of the power reduction value used by the BTS on PBCCH blocks and PCCCH blocks, relative to the output power on BCCH, see 3GPP TS 45.008. | +| TN (3 bit field)
This is the binary representation, range 0 to 7, of the timeslot number for the PBCCH, see 3GPP TS 45.002. | +| PBCCH Frequency Description
The PBCCH frequency description is encoded using the Frequency Parameters information element defined in sub-clause 12.8. When used in this message, the Frequency Parameters information element shall define a non-hopping radio frequency channel or use the direct encoding 2 to define a hopping radio frequency channel. | +| RAC (8 bit field)
This field is the binary representation of the Routing Area Code, see 3GPP TS 23.003. | +| PSI_CHANGED_IND (1 bit field)
This field indicates whether the contents of any PSI message have been changed, see sub-clause 5.5.2.1.3.
If not included in the message, the value "0" shall be assumed. | +| SI_STATUS_IND (1 bit field)
0 The network does not support the PACKET SI STATUS message;
1 The network supports the PACKET SI STATUS message.
If not included in the message, the value "0" shall be assumed. | + +#### **LB\_MS\_TXPWR\_MAX\_CCH** (5 bit field) + +The LB\_MS\_TXPWR\_MAX\_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008. + +#### **SI2n\_SUPPORT** (2 bit field) + +This field indicates the support of SI2n in the network, see 3GPP TS 44.018. + +### 11.2.25b Packet System Information 15 + +This message may be sent by the network on the PACCH. It may be sent to a mobile station with UTRAN capability. A mobile station with no UTRAN capability shall ignore this message. + +The message provides the mobile station with a list of the UTRAN frequencies used by the network. These frequencies may be used in the cell selection procedure, see 3GPP TS 25.304. If both an UTRAN Frequency List Description struct and an UTRAN Frequency List information element (3GPP TS 44.018) are received, the mobile station shall use the one most recently received. + +Message type: PACKET SYSTEM INFORMATION TYPE 15 + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.25b.1: PSI15 information elements** + +``` +< PSI15 message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < UTRAN Frequency List : < UTRAN Frequency List Description struct >> } + < padding bits > + ! < Distribution part error : bit (*) = < no string >> ; + +< UTRAN Frequency List Description struct > ::= + { 1 < FDD_ARFCN > : bit (14) } ** 0 -- FDD frequencies + { 1 < TDD_ARFCN > : bit (14) } ** 0 ; -- TDD frequencies +``` + +**Table 11.2.25b.2: PSI15 information element details** + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **UTRAN Frequency List Description struct** + +FDD\_ARFCN and TDD\_ARFCN (14 bits field) are defined as the UARFCN in 3GPP TS 25.101 and 3GPP TS 25.102. + +#### 11.2.25c Packet System Information Type 16 + +This message is sent by the network on the PBCCH and the PACCH giving information about *Iu mode* operation. Special requirements for the transmission of this message apply on the PBCCH, see 3GPP TS 45.002. + +This message shall not be segmented across more than one RLC/MAC control block by using the procedures specified in sub-clause 9.1.12a. A consistent set of this message type is required to completely decode the information (see sub-clause 5.5.2.1.4). + +Message type: PACKET SYSTEM INFORMATION TYPE 16 + +Direction: network to mobile station + +Classification: distribution message + +Table 11.2.25c.1: PSI16 information elements + +``` + +< PSI16 message content > ::= + < PAGE_MODE : bit (2) > + < PSI16_CHANGE_MARK : bit (2) > + < PSI16_INDEX : bit (3) > + < PSI16_COUNT : bit (3) > + < GRA_ID_LIST : < GRA ID struct > > + < Iu_MODE_NMO_SUPPORT : bit (1) > + < CN_DOMAIN_LIST : bit (2) > + { + < CN_DOMAIN_IDENTITY : < CN Domain Identity IE > > + < CN DOMAIN SPECIFIC DRX CYCLE LENGTH COEFFICIENT : + < CN Domain Specific DRX Cycle Length Coefficient IE > > + } * (1+val(CN_DOMAIN_LIST)) + { 0 | 1 < 3G_LAC : bit (16) > } + { 0 | 1 < 3G_RAC : bit (8) > } + { 0 | 1 < GRA_AND_CELL_UPDATE_TIMER : bit (3) > } + < padding bits > + ! < Distribution part error : bit (*) = < no string >> ; + +< GRA ID struct > ::= + < NUMBER_OF_GRA_IDs : bit (3) > + { < GRA_ID : bit (16) > } * (1 + val(NUMBER_OF_GRA_IDs)); + +``` + +Table 11.2.25c.2: PSI16 information element details + +#### **PAGE\_MODE** (2 bit field) + +This field describes which type of page mode used, i.e. either normal paging, extended paging, paging reorganization or same as before from the previous page mode. The mobile station shall ignore this field if the message is received on the PACCH. Coding of this field is defined in 3GPP TS 44.018 + +#### **PSI16\_CHANGE\_MARK** (2 bit field) + +This field is the binary representation of the PSI *change mark* parameter identifying a consistent set of PSI16 messages. Range: 0 to 3. + +#### **PSI16\_INDEX** (3 bit field) + +The PSI16 index field is used to distinguish individual PSI16 messages. The field can take the binary representation of the values 0 to n, where n is the index of the last PSI16 message. (PSI16 count). Range: 0 - 7. + +#### **PSI16\_COUNT** (3 bit field) + +The PSI16 count field is coded as the binary representation of the last (highest indexed) individual PSI16 message. Range: 0 - 7. + +#### *GERAN Id struct* + +At least one GRA Id shall be broadcast in each cell. Maximum number is eight. + +#### **NUMBER\_OF\_GRA\_IDs** (3 bit field) + +The NUMBER of GRA Ids field is coded as the binary representation of the amount of GRA IDs sent in an individual PSI16 message. Range: 0 - 7. + +#### **GRA\_ID** (16 bit field) + +The GRA\_ID defines the identity of a GERAN Registration Area Identity to which the cell belongs. + +#### **Iu\_MODE\_NMO\_SUPPORT** (1 bit field) + +This parameter is used for determining network mode of operation for the 3G SGSN and the 3G MSC. The mobile station may assume that the network has set this field equally in all instances of this message. + +##### Bit + +- 0 Network Mode Operation I +- 1 Network Mode Operation II + +| | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|--|-------|--|-------|-----------|-------|------------|-------|----------------------------|-------|------------|-------|-------------|-------|-------------|-------|-------------|-------|----------------------| +| CN_DOMAIN_LIST (2 bit field)
This field is used to repeat information for each CN domain. Range : 0 to MaxCNdomains-1. | | | | | | | | | | | | | | | | | | | | | +| CN_DOMAIN_IDENTITY | | | | | | | | | | | | | | | | | | | | | +| CN_DOMAIN_SPECIFIC_DRX_CYCLE_LENGTH_COEFFICIENT | | | | | | | | | | | | | | | | | | | | | +| 3G_LAC (16 bit field)
This field is only broadcast if the cell supports Iu mode and if 2G and 3G are using different location area codes. The coding of 3G_LAC is presented in 3GPP TS 23.003. | | | | | | | | | | | | | | | | | | | | | +| 3G_RAC (8 bit field)
This field is only broadcast if the cell supports Iu mode and if 2G and 3G are using different routing area codes. The coding of 3G_RAC is presented in 3GPP TS 23.003. | | | | | | | | | | | | | | | | | | | | | +| GRA_AND_CELL_UPDATE_TIMER (3 bit field)
This field is the binary representation of GRA and CELL UPDATE TIMERs.
bit
3 2 1
0 0 0 5 minutes
0 0 1 10 minutes
0 1 0 30 minutes (default value)
0 1 1 60 minutes
1 0 0 120 minutes
1 0 1 360 minutes
1 1 0 720 minutes
1 1 1 Infinity (no update)
| bit | | 3 2 1 | | 0 0 0 | 5 minutes | 0 0 1 | 10 minutes | 0 1 0 | 30 minutes (default value) | 0 1 1 | 60 minutes | 1 0 0 | 120 minutes | 1 0 1 | 360 minutes | 1 1 0 | 720 minutes | 1 1 1 | Infinity (no update) | +| bit | | | | | | | | | | | | | | | | | | | | | +| 3 2 1 | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 | 5 minutes | | | | | | | | | | | | | | | | | | | | +| 0 0 1 | 10 minutes | | | | | | | | | | | | | | | | | | | | +| 0 1 0 | 30 minutes (default value) | | | | | | | | | | | | | | | | | | | | +| 0 1 1 | 60 minutes | | | | | | | | | | | | | | | | | | | | +| 1 0 0 | 120 minutes | | | | | | | | | | | | | | | | | | | | +| 1 0 1 | 360 minutes | | | | | | | | | | | | | | | | | | | | +| 1 1 0 | 720 minutes | | | | | | | | | | | | | | | | | | | | +| 1 1 1 | Infinity (no update) | | | | | | | | | | | | | | | | | | | | + +### 11.2.26 Packet TBF Release + +This message is sent on the PACCH by the network to the mobile station to initiate release of an uplink or downlink TBF. + +Message type: PACKET TBF RELEASE + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.26.1: PACKET TBF RELEASE information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < Packet TBF Release message content > ::=   < PAGE_MODE : bit (2) >   { 0 < GLOBAL_TFI : Global TFI IE >     { < UPLINK_RELEASE : bit (1) >       < DOWNLINK_RELEASE : bit (1) >       < TBF_RELEASE_CAUSE : bit (4) = { 0000   0010 } >       < padding bits >       ! < Non-distribution part error : bit (*) = < no string > > }       ! < Address information part error : bit (*) = < no string > > }     ! < Distribution part error : bit (*) = < no string > > ;
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.26.2: PACKET TBF RELEASE information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20. | +| Global TFI IE
This information element contains the TFI of the mobile station's which uplink and/or downlink TBF to be released. This field is defined in sub-clause 12.10. | + +**Uplink\_Release** (1 bit field) + +**Downlink\_Release** (1 bit field) + +These fields indicate which TBF shall be release, uplink or downlink. Both directions can be released at the same time. + +- 0 TBF shall not be released +- 1 TBF shall be released + +--- + +**TBF\_RELEASE\_CAUSE** (4 bit field) + +This field indicates the reason for the release of the TBF. This field is encoded according to the following table: + +| | | | | | +|-----|---|---|---|------------------| +| bit | | | | | +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | Normal release | +| 0 | 0 | 1 | 0 | Abnormal release | + +All other values are reserved, the same behaviour in reception as if 'Abnormal release'. + +### 11.2.27 (void) + +### 11.2.28 Packet Uplink Ack/Nack + +This message is sent on the PACCH by the network to the mobile station indicate the status of the received RLC data blocks. This message may also update the timing advance and power control parameters. + +Message type: PACKET UPLINK ACK/NACK + +Direction: network to mobile station + +Classification: non-distribution message + +Table 11.2.28.1: PACKET UPLINK ACK/NACK information elements + +``` + +< Packet Uplink Ack/Nack message content > ::= + < PAGE MODE : bit (2) > + { 00 < UPLINK_TFI : bit (5) > + { 0 -- Message escape + { < CHANNEL_CODING_COMMAND : bit (2) > + < Ack/Nack Description : < Ack/Nack Description IE > > + { 0 | 1 < CONTENTION_RESOLUTION_TLLI : bit (32) > } + { 0 | 1 < Packet Timing Advance : < Packet Timing Advance IE > > } + { 0 | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 | 1 < Extension Bits : Extension Bits IE > } -- sub-clause 12.26 + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for R99 + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + < TBF_EST : bit (1) > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-5 + { 0 | 1 < CONTENTION_RESOLUTION Identifier extension : bit (4) > } + { 0 | 1 < RB Id : bit (5) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 0 | 1 -- DTR Information + < CI_DTR : bit (1) > + < TN_PDCH_pair_DTR : bit (3) > + < DTR BIks : bit (2) > } + < padding bits > } + } + } + } + } + } + ! < Non-distribution part error : bit (*) = < no string > > + } + | 1 -- Message escape bit used to define EGPRS message contents + { 00 + { < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > + < RESEGMENT : bit (1) > + < PRE_EMPTIVE_TRANSMISSION : bit (1) > + < PRR RETRANSMISSION REQUEST : bit (1) > + < ARAC RETRANSMISSION REQUEST : bit (1) > + { 0 | 1 < CONTENTION_RESOLUTION_TLLI : bit (32) > } + < TBF_EST : bit (1) > + { 0 | 1 < Packet Timing Advance : < Packet Timing Advance IE > > } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 | 1 < Extension Bits : Extension Bits IE > } -- sub-clause 12.26 + { < EGPRS Ack/Nack Description : < EGPRS Ack/Nack Description IE > > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + } // + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-5 + { 0 | 1 < CONTENTION_RESOLUTION Identifier extension : bit (4) > } + { 0 | 1 < RB Id : bit (5) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < PDAN Coding : bit (1) > + { 0 | 1 + < TN_PDCH_pair_DTR : bit (3) > + < DTR BIks : bit (2) > } + < padding bits > } } + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Message escape : { 01 | 10 | 11 } bit (*) = < no string > > } -- Extended for future changes + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + } + +``` + +**Table 11.2.28.2: PACKET UPLINK ACK/NACK information element details** + +| | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----|------------------------------------------------------------------------------------------------------------------------------|-----|------|-----|------|-----|------|-----|------| +|

PAGE_MODE (2 bit field)

This field is defined in sub-clause 12.20.

| | | | | | | | | | | | | +|

UPLINK_TFI (5 bit field)

This field identifies the uplink TBF to which this message applies. This field is coded the same as the TFI field defined in sub-clause 12.15. On DBPSCH, this field equals the radio bearer identity of the radio bearer to which this message applies.

| | | | | | | | | | | | | +|

CHANNEL_CODING_COMMAND (2 bit field)

The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting on the uplink.

bits
2 1 value
0 0 CS-1
0 1 CS-2
1 0 CS-3
1 1 CS-4
| bits | | 2 1 | value | 0 0 | CS-1 | 0 1 | CS-2 | 1 0 | CS-3 | 1 1 | CS-4 | +| bits | | | | | | | | | | | | | +| 2 1 | value | | | | | | | | | | | | +| 0 0 | CS-1 | | | | | | | | | | | | +| 0 1 | CS-2 | | | | | | | | | | | | +| 1 0 | CS-3 | | | | | | | | | | | | +| 1 1 | CS-4 | | | | | | | | | | | | +|

Ack/Nack Description

This information element is defined in sub-clause 12.3.

| | | | | | | | | | | | | +|

EGPRS Modulation and Coding Scheme

The EGPRS Modulation and Coding Scheme information element is defined in sub-clause 12.10d.

| | | | | | | | | | | | | +|

RESEGMENT (1 bit field)

This field is defined in sub-clause 12.10e.

| | | | | | | | | | | | | +|

PRE_EMPTIVE_TRANSMISSION (1 bit field)

This bit informs the mobile station if it may or may not transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING_ACK (and repeating the process, refer to sub-clause 9.1.3.2) when the protocol is stalled or has no more RLC data blocks to transmit.

0 The mobile station shall not use pre-emptive transmission.
1 The mobile station shall use pre-emptive transmission.
| 0 | The mobile station shall not use pre-emptive transmission. | 1 | The mobile station shall use pre-emptive transmission. | | | | | | | | | +| 0 | The mobile station shall not use pre-emptive transmission. | | | | | | | | | | | | +| 1 | The mobile station shall use pre-emptive transmission. | | | | | | | | | | | | +|

PRR RETRANSMISSION REQUEST (1 bit field)

0 indicates that retransmission of a PACKET RESOURCE REQUEST message is not requested
1 indicates that retransmission of a PACKET RESOURCE REQUEST message is requested (see sub-clause 7.1.2.2.1a)
| 0 | indicates that retransmission of a PACKET RESOURCE REQUEST message is not requested | 1 | indicates that retransmission of a PACKET RESOURCE REQUEST message is requested (see sub-clause 7.1.2.2.1a) | | | | | | | | | +| 0 | indicates that retransmission of a PACKET RESOURCE REQUEST message is not requested | | | | | | | | | | | | +| 1 | indicates that retransmission of a PACKET RESOURCE REQUEST message is requested (see sub-clause 7.1.2.2.1a) | | | | | | | | | | | | +|

ARAC RETRANSMISSION REQUEST (1 bit field)

0 indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested
1 indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is requested (see sub-clause 7.1.2.2.1a)
| 0 | indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested | 1 | indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is requested (see sub-clause 7.1.2.2.1a) | | | | | | | | | +| 0 | indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested | | | | | | | | | | | | +| 1 | indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is requested (see sub-clause 7.1.2.2.1a) | | | | | | | | | | | | +|

EGPRS Ack/Nack Description

This information element is defined in sub-clause 12.3.1. The number of bits (L) available for Ack/Nack Description information element depends on the inclusion of other information elements. L may be set so that the entire PACKET UPLINK ACK/NACK message evenly fits into an RLC/MAC control block. If a lower L covers the entire receive window, that L may be used.

| | | | | | | | | | | | | +|

CONTENTION_RESOLUTION_TLLI (32 bit field)

The CONTENTION_RESOLUTION_TLLI field is present only if the network has decoded one of the uplink RLC data blocks containing the TLLI or G-RNTI. The mobile station shall perform the contention resolution function if the TLLI or G-RNTI information element is present. This field contains a TLLI or a G-RNTI, which is defined in sub-clause 12.16.

| | | | | | | | | | | | | +|

Packet Timing Advance

This information element is defined in sub-clause 12.12.

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

Power Control Parameters
This information element, if present, contains the power control parameters the mobile station shall use to determine its TX power level. If this information element does not include the updated power control parameters for some of currently assigned timeslots, the MS shall continue to use the current power control parameters for these timeslots. This information element is defined in sub-clause 12.13.

| +|

Extension Bits
This information element, if present, shall be skipped over. Any information content shall be ignored by the mobile station. This information element is defined in sub-clause 12.26.

| +|

Packet Extended Timing Advance (2 bit field)
This field is defined in sub-clause 12.12b.

| +|

TBF_EST (1 bit field)
If included, this field indicates that the mobile station is allowed to request the establishment of new TBF on PACCH.

0 the mobile station is not allowed to request the establishment of new TBF

1 the mobile station is allowed to request the establishment of new TBF

| +|

CONTENTION_RESOLUTION Identifier extension (4 bit field)

This field contains the extra 4 bits of the G-RNTI not included in the CONTENTION_RESOLUTION_TLLI field which are necessary to provide a unique identifier for contention resolution in Iu-mode. This field is present when an assigned G-RNTI is used during the contention resolution procedure.

| +|

RB Id (5 bit field)
This field contains the radio bearer identity of the mobile station's radio bearer for which the uplink data transfer on SFACCH is acknowledged. This field is not included when the PACKET UPLINK ACK/NACK message is sent on DBPSCH. This field is encoded as a binary number with range 0-31.

| +|

CI_DTR (1 bit field)
This field indicates the carrier the mobile station shall monitor when DTR is used (see sub-clause 8.1.8). In case of single carrier configuration, this field shall be set to the value '0'. The timeslot or PDCH-pair to monitor on this carrier is indicated with the TN_PDCH_pair_DTR field.

0 carrier 1

1 carrier 2. If received by a mobile station not supporting dual carrier it shall be interpreted as '0'.

| +|

TN_PDCH_pair_DTR (3 bit field)
This field contains the timeslot number (BTTI configuration) or the PDCH-pair number (RTTI configuration) the mobile station shall monitor on the indicated carrier (CI_DTR field for a Downlink Dual Carrier configuration or the downlink carrier used for fall back according to a regular pre-determined interval (see sub-clause 8.1.8.2 and sub-clause 5.13) for a DLMC configuration) when DTR is used (see sub-clause 8.1.8).

| +|

DTR BIks (2 bit field)
This field indicates the subset of downlink radio blocks the mobile station shall monitor for USFs and/or downlink RLC data blocks in DTR mode. This field is coded as defined in sub-clause 10.4.26.

| +|

PDAN Coding (1 bit field)
See sub-clause 11.2.7.

| + +#### 11.2.28a Packet DBPSCH Uplink Ack/Nack + +This message is sent on FACCH, SACCH or SDCCH from the network to the mobile station to indicate the status of uplink RLC data blocks received. + +Message type: PACKET DBPSCH UPLINK ACK/NACK + +Direction: network to mobile station + +Classification: DBPSCH message + +**Table 11.2.28a.1: PACKET DBPSCH UPLINK ACK/NACK information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < Packet DBPSCH Uplink Ack/Nack message content > ::= { < MESSAGE_TYPE : bit (6) == 001001 >   < RB Id : bit (5) >   { 0   1 < CONTENTION_RESOLUTION_TLLI : bit (32) >           { 0   1 < G-RNTI extension : bit (4) > } }   { 0 -- TCH TBF mode       { 0 - All data blocks acknowledged, no retransmission requested         1 < STARTING_SEQUENCE_NUMBER : bit (8) >           < RECEIVED_BLOCK_BITMAP : bit (128) > }     1 -- DCCH TBF mode       { 0 - All data blocks acknowledged, no retransmission requested         1 < STARTING_SEQUENCE_NUMBER : bit (4) >           < RECEIVED_BLOCK_BITMAP : bit (8) > } }   < padding bits >   ! < DBPSCH message part error : bit (*) = < no string > > } ;
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.28a.2: PACKET DBPSCH UPLINK ACK/NACK information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

CONTENTION_RESOLUTION_TLLI (32 bit field)
The CONTENTION_RESOLUTION_TLLI field is present only if the network has decoded one of the uplink RLC data blocks containing the G-RNTI. The mobile station shall perform the contention resolution function if the G-RNTI information element is present. This field contains a G-RNTI, which is defined in sub-clause 12.16.

| +|

G-RNTI extension (4 bit field)
This field contains the extra 4 bits of the G-RNTI not included in the CONTENTION_RESOLUTION_TLLI field which are necessary to provide a unique identifier for contention resolution in Iu-mode. This field is present when an assigned G-RNTI is used during the contention resolution procedure.

| +|

RB Id (5 bit field)
This field contains the radio bearer identity of the mobile station's radio bearer for which the uplink data transfer is acknowledged. This field is encoded as a binary number with range 0-31.

| +|

STARTING_SEQUENCE_NUMBER (8 or 4 bit field)
The SSN contains the value of V(R) when this information element was transmitted. This field is encoded as the binary representation of V(R).
Range 0 to 255 (8 bit field)
Range 0 to 15 (4 bit field)

| +|

RECEIVED_BLOCK_BITMAP (RBB) (128 or 8 bit field)
The RBB is a bitmap representing Block Sequence Numbers. The bitmap is indexed relative to SSN as follows:

BSN = (SSN - bit_number) modulo 256, for bit_number = 1 to 128 (128 bit field).
BSN = (SSN - bit_number) modulo 16, for bit_number = 1 to 8 (8 bit field).

The BSN values represented range:

from (SSN - 1) mod 256 to (SSN - 128) mod 256 (128 bit field)
from (SSN - 1) mod 16 to (SSN - 8) mod 16 (8 bit field)

The value of each bit represents the acknowledgement status of the RLC data block with:

BSN = (SSN - bit_number) mod 256 (128 bit field)
BSN = (SSN - bit_number) mod 16 (8 bit field),

it is encoded as follows:

0 Negative acknowledgement
1 Positive acknowledgement

| + +#### 11.2.28b Packet DBPSCH Uplink Ack/Nack Type 2 + +This message shall only be used when FLO is used. It is sent on ADCH from the network to the mobile station to indicate the status of uplink RLC data blocks received. + +Message type: PACKET DBPSCH UPLINK ACK/NACK TYPE 2 + +Direction: network to mobile station + +Classification: DBPSCH message + +**Table 11.2.28b.1: PACKET DBPSCH UPLINK ACK/NACK TYPE 2 information elements** + +``` +< Packet DBPSCH Uplink Ack/Nack message content > ::= +{ + < MESSAGE_TYPE : bit (6) == 001001 > -- The same message type as for Packet DBPSCH Uplink Ack/Nack is + -- used since these two messages are mutually exclusive. + < RB Id : bit (5) > + { 0 -- UDCH TBF mode + { 0 -- All data blocks acknowledged, no retransmission requested + | 1 < FLO Ack/Nack Description : < FLO Ack/Nack Description IE > > } + | 1 -- CDCH TBF mode + { 0 -- All data blocks acknowledged, no retransmission requested + | 1 < STARTING_SEQUENCE_NUMBER : bit (4) > + < RECEIVED_BLOCK_BITMAP : bit (8) > } + } + < padding bits > + ! < DBPSCH message part error : bit (*) = < no string > > }; +``` + +**Table 11.2.28b.2: PACKET DBPSCH UPLINK ACK/NACK TYPE 2 information element details** + +##### RB Id (5 bit field) + +This field contains the radio bearer identity of the mobile station's radio bearer for which the uplink data transfer is acknowledged. This field is encoded as a binary number with range 0-31. + +#### STARTING\_SEQUENCE\_NUMBER (4 bit field) + +The SSN contains the value of V(R) when this information element was transmitted. This field is encoded as the binary representation of V(R). + +Range 0 to 15 (4 bit field) + +#### RECEIVED\_BLOCK\_BITMAP (RBB) (128 or 8 bit field) + +The RBB is a bitmap representing Block Sequence Numbers. The bitmap is indexed relative to SSN as follows: + +$BSN = (SSN - bit\_number) \bmod 16$ , for $bit\_number = 1$ to 8 (8 bit field). + +The BSN values represented range: + +from $(SSN - 1) \bmod 16$ to $(SSN - 8) \bmod 16$ (8 bit field) + +The value of each bit represents the acknowledgement status of the RLC data block with: + +$BSN = (SSN - bit\_number) \bmod 16$ (8 bit field), + +it is encoded as follows: + +- 0 Negative acknowledgement +- 1 Positive acknowledgement + +### 11.2.29 Packet Uplink Assignment + +This message is sent on the PCCCH or PACCH by the network to the mobile station to assign uplink resources. If the mobile station supports Downlink Dual Carrier or Downlink Multi Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a). The mobile station may be addressed by TFI, TQI, + +or Packet Request Reference depending upon the procedure used. A mobile allocation or reference frequency list received as part of this assignment message shall be valid until new assignment is received or each TBF of the MS are terminated. + +Message type: PACKET UPLINK ASSIGNMENT + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.29.1: PACKET UPLINK ASSIGNMENT information elements** + +``` + +< Packet Uplink Assignment message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } + { + { 0 < Global TFI : < Global TFI IE > > + | 10 < TLLI / G-RNTI : bit (32) > + | 110 < TQI : bit (16) > + | 111 < Packet Request Reference : < Packet Request Reference IE > > } + { 0 -- Message escape + { + < CHANNEL_CODING_COMMAND : bit (2) > + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Dynamic Allocation : < Dynamic Allocation struct > > + | 10 < Single Block Allocation : < Single Block Allocation struct > > + | 00 < extension > + } -- The value '11' was allocated in an earlier version of the protocol and shall not be used. + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for R99 + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-5 + { 0 | 1 < G-RNTI extension : bit (4) > } + { 0 | 1 < RB Id : bit (5) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-6 + { 0 | 1 < PFI : bit (7) > } + { 0 | 1 < RLC_MODE : bit (1) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + < padding bits > } } } } + ! < Non-distribution part error : bit (*) = < no string > > } + +``` + +``` + +| 1 -- Message escape bit used to define EGPRS message contents + { 00 { { 0 | 1 < CONTENTION_RESOLUTION_TLLI : bit(32) > } + { 0 | 1 < COMPACT reduced MA : < COMPACT reduced MA IE > > } + < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > + < RESEGMENT : bit (1) > + < EGPRS Window Size : < EGPRS Window Size IE > > + { 0 | 1 < Access Technologies Request : Access Technologies Request struct > } + < ARAC RETRANSMISSION REQUEST : bit (1) > + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Dynamic Allocation : < Dynamic Allocation struct > > + | 10 < Multi Block Allocation : < Multi Block Allocation struct > > + | 00 < extension > + } + -- The value '11' was allocated in an earlier version of the protocol and shall not be used. + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-5 + { 0 | 1 < G-RNTI extension : bit (4) > } + { 0 | 1 < RB Id : bit (5) > } + { null | 0 bit** = -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-6 + { 0 | 1 < PFI : bit (7) > } + { 0 | 1 < RLC_MODE : bit (1) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-7 + { 0 | 1 < NPM Transfer Time : bit (5) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + < Indication of Upper Layer PDU Start for RLC UM : bit > + < Enhanced Flexible Timeslot Assignment : bit > + { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used + | 1 < RLC Entity 2 : < RLC Entity Struct > > -- EMST is used + { 0 + | 1 < RLC Entity 3 : < RLC Entity Struct > > } + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + < padding bits > } } } } } } + ! < Non-distribution part error : bit (*) = < no string > > } + +| 01 -- Message escape for dual carrier, RTTI, BTTI with FANR activated, EGPRS2 + { { 0 | 1 < CONTENTION_RESOLUTION_TLLI : bit(32) > } + < RESEGMENT : bit (1) > + < Assignment Info : Assignment Info struct > + < EGPRS Window Size : < EGPRS Window Size IE > > + { 0 | 1 < Access Technologies Request : Access Technologies Request struct > } + < ARAC RETRANSMISSION REQUEST : bit (1) > + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 -- BTTI mode + | 1 -- RTTI mode + < RTTI_USF_MODE : bit (1) > + < PDCH Pairs Description : < PDCH Pairs Description IE > > } + +``` + +``` + +< Dynamic Allocation 2: < Dynamic Allocation 2 struct > > +< EGPRS Channel Coding Command: < EGPRS Modulation and Coding Scheme IE > > +{ 00 -- No frequency parameters included +| 01 -- Legacy IEs used + { 0 | 1 < Frequency Parameters C1: < Frequency Parameters IE > > } + { 0 | 1 < Frequency Parameters C2: < Frequency Parameters IE > > } +| 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE > > + ! < Frequency Parameters error: { 11 } bit(*) = < no string> > -- reserved for future used +} +{ 0 | 1 < PFI : bit (7) > } +{ 0 | 1 < RLC_MODE : bit (1) > } +{ 0 | 1 < NPM Transfer Time : bit (5) > } +{ 0 | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < REPORTED TIMESLOTS C1 : bit (8) > -- carrier 1 in Downlink Dual Carrier + --configuration + { 0 | 1 < REPORTED TIMESLOTS C2 : bit (8) > } -- carrier 2 in Downlink Dual Carrier + -- configuration + < TSH : bit (2) > } } +< Uplink EGPRS Level: < EGPRS Level IE > > +{ 0 | 1 < Pulse Format: < Pulse Format IE > > } +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 -- Additions for Rel-9 + < Indication of Upper Layer PDU Start for RLC UM: bit > + < Enhanced Flexible Timeslot Assignment : bit > + { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used + | 1 < RLC Entity 2 : < RLC Entity Struct > > -- EMST is used + { 0 + | 1 < RLC Entity 3 : < RLC Entity Struct > > } + } + { 0 | 1 MTTI_UPLINK_ASSIGNMENT_C1 : bit (1) } + { 0 | 1 MTTI_UPLINK_ASSIGNMENT_C2 : bit (1) } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > +< padding bits > } } } +! < Non-distribution part error : bit (*) = < no string > > } +| 10 -- Message escape for downlink multi carrier, RTTI, BTTI with FANR activated, EGPRS2 +{ + < RESEGMENT : bit (1) > + { 1 < DLMC UL Carrier Info: < DLMC UL Carrier Info struct > > } ** 0 + < EGPRS Window Size : < EGPRS Window Size IE > > + < UPLINK_TFI_ASSIGNMENT : bit (5) > + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + { 0 | 1 < PFI : bit (7) > } + { 0 | 1 < RLC_MODE : bit (1) > } + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < REPORTED TIMESLOTS : bit (8) > + < TSH : bit (2) > } } + < Uplink EGPRS Level: < EGPRS Level IE > > + { 0 | 1 < Pulse Format: < Pulse Format IE > > } + < Indication of Upper Layer PDU Start for RLC UM: bit > + < Enhanced Flexible Timeslot Assignment : bit > + +``` + +``` + + < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >> + < padding bits > // -- truncation at end of message allowed, bits '0' assumed + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Message escape : { 11 } bit (*) = < no string > > } } - Extended for future changes + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + + ::= -- Future extension can be done by modifying this structure + null ; + ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + < USF_GRANULARITY : bit (1) > + { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + { 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > } + { 0 -- Timeslot Allocation + { 0 | 1 < USF_TN0 : bit (3) > } + { 0 | 1 < USF_TN1 : bit (3) > } + { 0 | 1 < USF_TN2 : bit (3) > } + { 0 | 1 < USF_TN3 : bit (3) > } + { 0 | 1 < USF_TN4 : bit (3) > } + { 0 | 1 < USF_TN5 : bit (3) > } + { 0 | 1 < USF_TN6 : bit (3) > } + { 0 | 1 < USF_TN7 : bit (3) > } + } + | 1 -- Timeslot Allocation with Power Control Parameters + < ALPHA : bit (4) > + { 0 | 1 < USF_TN0 : bit (3) > + < GAMMA_TN0 : bit (5) > } + { 0 | 1 < USF_TN1 : bit (3) > + < GAMMA_TN1 : bit (5) > } + { 0 | 1 < USF_TN2 : bit (3) > + < GAMMA_TN2 : bit (5) > } + { 0 | 1 < USF_TN3 : bit (3) > + < GAMMA_TN3 : bit (5) > } + { 0 | 1 < USF_TN4 : bit (3) > + < GAMMA_TN4 : bit (5) > } + { 0 | 1 < USF_TN5 : bit (3) > + < GAMMA_TN5 : bit (5) > } + { 0 | 1 < USF_TN6 : bit (3) > + < GAMMA_TN6 : bit (5) > } + { 0 | 1 < USF_TN7 : bit (3) > + < GAMMA_TN7 : bit (5) > } } ; + + ::= + < TIMESLOT_NUMBER : bit (3) > + { 0 | 1 < ALPHA : bit (4) > + < GAMMA_TN : bit (5) > } + { 0 | 1 < P0 : bit (4) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < PR_MODE : bit (1) > } + < TBF Starting Time : < Starting Frame Number Description IE > > ; + +< Multi Block Allocation struct> ::= + < TIMESLOT_NUMBER : bit (3) > + { 0 | 1 < ALPHA : bit (4) > + < GAMMA_TN : bit (5) > } + { 0 | 1 < P0 : bit (4) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < PR_MODE : bit (1) > } + < TBF Starting Time : < Starting Frame Number Description IE > > + < NUMBER OF RADIO BLOCKS ALLOCATED: bit (2) > ; + +< Access Technologies Request struct> ::= -- recursive structure allows any combination of Access technologies + < Access Technology Type : bit (4) > + { 0 | 1 < Access Technologies Request struct > } ; + +``` + +``` + +< Assignment Info struct > ::= + < ASSIGNMENT TYPE : bit (2) > + < Carrier ID : bit (1) >; + +< Dynamic Allocation 2 struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit (1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit (1) > } } + < USF_GRANULARITY : bit (1) > + { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 + -- Allocation without Power Control Parameters + < N_USF : bit (4) > + { 0 | 1 < USF : bit (3) > } * (val(N_USF) + 1) + | 1 + -- Allocation with Power Control Parameters + < ALPHA_C1 : bit (4) > + { 0 | 1 < ALPHA_C2 : bit (4) > } + { 0 + -- BTTI mode + < N_TS : bit (4) > + { 0 | 1 + < USF : bit (3) > + < GAMMA : bit (5) > + } * (val(N_TS) + 1) + | 1 + -- RTTI mode + < N_PAIRS : bit (3) > + { 0 | 1 + < USF : bit (3) > + < GAMMA : bit (5) > + } * (val(N_PAIRS) + 1) + { 0 + -- RTTI USF + | 1 + -- BTTI USF + { 0 | 1 + < USF_2 : bit (3) > + { 0 | 1 < GAMMA : bit (5) > } + } * (val(N_PAIRS) + 1) + } + } + } +}; + +< RLC Entity Struct > ::= + < UPLINK_TFI_ASSIGNMENT : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + PFI : bit (7) >; + +``` + +``` + +< Additional PFCs struct > ::= + < UPLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < PFI : bit (7) > ; +< DLMC UL Carrier Info struct > ::= + { 00 -- Assigned carrier released + | 01 -- Carrier remains unchanged (no information provided) + | 10 -- Assigned carrier modified or new carrier assigned + { 0 -- BTTI mode + { 0 | 1 < UPLINK_TIMESLOT_ALLOCATION : bit (8) > } -- assigned PDCH + | 1 -- RTTI mode + { 0 | 1 < UPLINK_PDCH_PAIRS_DLMC : bit (8) > } -- assigned PDCH-pairs + } + < Dynamic Allocation 3 : < Dynamic Allocation 3 IE > > + { 0 -- EMST is not used on this carrier + | 1 -- EMST is used on this carrier + < Uplink RLC Entity 2 : < RLC Entity Struct > > + { 0 | 1 < Uplink RLC Entity 3 : < RLC Entity Struct > } } + { 0 -- EMSR is not used on this carrier + | 1 -- EMSR is used on this carrier + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + < Primary TSC Set : bit (1) > + | 11 bit (*) = < no string > -- reserved + } ; + +``` + +**Table 11.2.29.2: PACKET UPLINK ASSIGNMENT information element details** + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--|-----|--|-----|------|-----|------|-----|------|-----|------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

| | | | | | | | | | | | | +|

PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1...4)
This field is defined in sub-clause 12.14, PRACH Control Parameters.

| | | | | | | | | | | | | +|

Global TFI
This information element identifies the uplink TFI, if available, or the downlink TFI, to which this message applies.
This field is defined in sub-clause 12.10.

| | | | | | | | | | | | | +|

TLLI / G-RNTI
This information element is defined in sub-clause 12.16.

| | | | | | | | | | | | | +|

TQI (16 bit field)
This field is defined in sub-clause 12.17.

| | | | | | | | | | | | | +|

Packet Request Reference
This information element is defined in sub-clause 12.11.

| | | | | | | | | | | | | +|

CHANNEL_CODING_COMMAND (2 bit field)
The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting data on the uplink.

bit
2 1
0 0 CS-1
0 1 CS-2
1 0 CS-3
1 1 CS-4
| bit | | 2 1 | | 0 0 | CS-1 | 0 1 | CS-2 | 1 0 | CS-3 | 1 1 | CS-4 | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | CS-1 | | | | | | | | | | | | +| 0 1 | CS-2 | | | | | | | | | | | | +| 1 0 | CS-3 | | | | | | | | | | | | +| 1 1 | CS-4 | | | | | | | | | | | | + +#### **CONTENTION\_RESOLUTION\_TLLI** (32 bit field) + +The CONTENTION\_RESOLUTION\_TLLI field is present only if the network has decoded one of the uplink blocks containing the TLLI or G-RNTI during the EGPRS one phase access. The mobile station shall perform the contention resolution function if this field is present. This field contains a TLLI or G-RNTI, which is defined in sub-clause 12.16. See sub-clause 7.1.2.3a. + +#### **COMPACT reduced MA** + +This information element is defined in sub-clause 12.29. + +#### **EGPRS Modulation and Coding Scheme** + +The EGPRS Modulation and Coding Scheme information element is defined in sub-clause 12.10d. + +If this field is included in a Dual Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on both carriers. + +#### **RESEGMENT** (1 bit field) + +This field is defined in sub-clause 12.10e. + +#### **EGPRS Window Size** + +This information element is defined in sub-clause 12.5.2. + +#### **TLLI\_BLOCK\_CHANNEL\_CODING** (1 bit field) + +This field indicates the channel coding command that the mobile station shall use for any RLC data block containing a TLLI field in the RLC data block header. This field is coded as shown: + +- 0 the mobile station shall use CS-1 in GPRS TBF mode and MCS-1 in EGPRS TBF mode. +- 1 the mobile station shall use the value commanded in the CHANNEL\_CODING\_COMMAND or EGPRS\_CHANNEL\_CODING\_COMMAND field. + +#### **BEP\_PERIOD2** (4 bit field) + +This field contains a constant which is used for filtering channel quality measurements in EGPRS. BEP\_PERIOD2 when present, or if not, when received in a previous message of the same TBF session, shall be used instead of BEP\_PERIOD. For details see 3GPP TS 45.008. + +Range: 0 to 15 + +#### **UPLINK\_TFI\_ASSIGNMENT** (5 bit field) + +This information element, if present, assigns the contained TFI to the mobile station to identify the uplink TBF described by this message. This field is coded the same as the TFI field defined in sub-clause 12.15. If EMST is used, each TFI identifies an RLC entity allocated on the uplink TBF. If EMSR is supported, each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the uplink TBF. + +#### **Packet Timing Advance** + +This information element is defined in sub-clause 12.12. + +#### **Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink TBF. If this information element is not present the mobile station shall use its previously assigned frequency parameters. This information element is defined in sub-clause 12.8. + +##### **Frequency Parameters C1, Frequency Parameters C2** + +These information elements are coded as defined in sub-clause 12.8. See sub-clause 11.2.7 for the usage of these information elements. + +##### **Dual Carrier Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink TBF for both carriers in a dual carrier configuration. This information element is defined in sub-clause 12.8.2. + +#### **Dynamic Allocation struct** + +This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation. + +In case of a timeslot allocation without power control parameters, the values of the power control parameters for assigned timeslots shall be the default values as specified in 3GPP TS 45.008. However, in case some of the timeslots assigned by this message are already used by the mobile station, the mobile station shall continue to use the current power control parameters for these timeslots. + +#### **Dynamic Allocation 2 struct** + +This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation in a dual carrier, RTTI, BTTI with FANR activated, or EGPRS2 configuration. + +In case of a timeslot allocation without power control parameters, the values of the power control parameters for assigned timeslots shall be the default values as specified in 3GPP TS 45.008. However, in case some of the timeslots assigned by this message are already used by the mobile station, the mobile station shall continue to use the current power control parameters for these timeslots. + +#### **EXTENDED\_DYNAMIC\_ALLOCATION (1 bit field)** + +This information field indicates the medium access mode to be used during the TBF. + +- 0 Dynamic Allocation +- 1 Extended Dynamic Allocation + +#### **TBF Starting Time** + +The TBF Starting Time field contains a starting time that indicates the frame number during which the assigned TBF may start. + +In case of dynamic allocation, if no uplink TBF is in progress, the MS need not monitor the USF field until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. If an uplink TBF is already in progress, the MS shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. + +In case of single block allocation, the mobile station shall use the assigned timeslot during the RLC/MAC block whose first TDMA burst occurs in the indicated TDMA frame number. + +This information element is encoded as the Starting Frame Number Description IE. See sub-clause 12.21. + +#### **USF\_TN0 (3 bit field)** + +#### **USF\_TN1 (3 bit field)** + +#### **USF\_TN2 (3 bit field)** + +##### **USF\_TN3 (3 bit field)** + +##### **USF\_TN4 (3 bit field)** + +##### **USF\_TN5 (3 bit field)** + +##### **USF\_TN6 (3 bit field)** + +##### **USF\_TN7 (3 bit field)** + +These fields indicate the USF value assigned to the MS for assigned timeslots (range 0 to 7). These fields are encoded as a binary presentation of the USF value as defined in sub-clause 10.4.1. + +#### **USF\_GRANULARITY (1 bit field)** + +This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation. + +- 0 the mobile station shall transmit one RLC/MAC block +- 1 the mobile station shall transmit four consecutive RLC/MAC blocks + +#### **Single Block Allocation struct** + +This information element contains parameters necessary to define the radio resources of a Single Block allocation. For example for sending of a PACKET RESOURCE REQUEST message in a two phase access or a Measurement report. + +#### **TIMESLOT\_NUMBER (3 bit field)** + +This field indicates the timeslot assigned for transfer of a single RLC/MAC block on the uplink. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010. + +Range 0 to 7 + +#### **ALPHA (4 bit field)** + +For encoding and description see the Global Power Control Parameters IE. + +##### **ALPHA\_C1, ALPHA\_C2 (4 bit field)** + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then ALPHA\_C1 (if present) shall apply to the carrier specified in the Carrier ID field. + +If the Assignment Type field is included and indicates 'Dual Carrier assignment', ALPHA\_C1 and ALPHA\_C2 indicate the value of the parameter alpha to be applied in power control on carrier 1 and carrier 2 respectively. For encoding and description see the Global Power Control Parameters IE. If ALPHA\_C1 is present and ALPHA\_C2 is absent, then ALPHA\_C1 shall apply to carrier 2. + +#### **GAMMA, GAMMA\_TN (5 bit field)** + +This field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +bit + +5 4 3 2 1 + +0 0 0 0 0 $\Gamma_{CH} = 0$ dB + +0 0 0 0 1 $\Gamma_{CH} = 2$ dB + +... + +1 1 1 1 0 $\Gamma_{CH} = 60$ dB + +1 1 1 1 1 $\Gamma_{CH} = 62$ dB + +In the case of RTTI mode with BTTI USF, exactly one GAMMA field shall be included for each PDCH pair for which either one or two USF values are assigned. + +##### **P0, P0\_C1, P0\_C2 (4 bit field)** + +These fields are optional downlink power control parameters. + +If the Assignment Type field is present and indicates 'Dual Carrier assignment', P0\_C1 and P0\_C2 apply to carrier 1 and carrier 2, respectively. The presence of these parameters indicates that downlink power control is used for the indicated carrier; otherwise, downlink power control is not used for the indicated carrier. If the P0\_C1 IE is present but the P0\_C2 IE is absent, then the P0\_C1 IE shall apply also to carrier 2. + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then P0\_C1 shall apply to the carrier specified in the Carrier ID field. + +These fields are encoded as follows: + +bit + +4 3 2 1 + +0 0 0 0 P0 = 0 dB + +0 0 0 1 P0 = 2 dB + +0 0 1 0 P0 = 4 dB + +... + +1 1 1 1 P0 = 30 dB + +#### **PR\_MODE, PR\_MODE\_C1, PR\_MODE\_C2 (1 bit field)** + +These fields indicate the PR Management mode, as defined in 3GPP TS 45.008. + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then PR\_MODE\_C1 shall apply to the carrier specified in the Carrier ID field. Otherwise, PR\_MODE\_C1 and PR\_MODE\_C2 shall apply to carrier 1 and carrier 2 respectively. If the Assignment Type field indicates 'Dual Carrier assignment' and the PR\_MODE\_C1 IE is present but the PR\_MODE\_C2 IE is absent, then the PR\_MODE\_C1 IE shall apply also to carrier 2. It is encoded as follows: + +0 PR mode A: for one addressed MS + +1 PR mode B: for all MS + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Packet Extended Timing Advance (2 bit field)
This field is defined in sub-clause 12.12b.

| +|

Multi Block Allocation struct
This information element contains parameters necessary to define the radio resources of a Multi Block allocation.

| +|

NUMBER OF RADIO BLOCKS ALLOCATED (2 bit field)
Bits
1 0
0 0        1 radio block reserved for uplink transmission
0 1        2 radio blocks reserved for uplink transmission
1 0        reserved for future use
1 1        reserved for future use

| +|

ACCESS TECHNOLOGY TYPE

This field indicates the access technology that is requested from the mobile station. The field is coded according to the definition in 3GPP TS 24.008. The access technology types requested from the MS in the Access Technologies Request structure shall be classified by priority, the most important first. The MS shall reply using the same order. Among the three GSM 900 access technology types GSM P, GSM E and GSM R only one shall be requested by the network.

| +|

ARAC RETRANSMISSION REQUEST (1 bit field)
0 indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested
1 indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is requested (see sub-clause 7.1.2.2.1a)

| +|

G-RNTI extension (4 bit field)

This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier for contention resolution in Iu-mode. This field may also be included when an assigned G-RNTI is used in the CONTENTION_RESOLUTION_TLLI field during the contention resolution procedure.

| +|

RB Id (5 bit field)

This field is included in Iu mode when a TBF is assigned in MAC-Shared state. It contains the radio bearer identifier for the radio bearer using the assigned TBF.

| +|

PFI (7 bit field)

This field contains the PFI parameter identifying the Packet Flow Context related to the TBF identified in the UPLINK_TFI_ASSIGNMENT field. The PFI parameter is encoded as the contents of the PFI information element defined in 3GPP TS 44.018. If EMST is used, this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported, this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity.

| +|

RLC_MODE (1 bit field)

This field contains the RLC mode to be used for the assigned TBF.

0 RLC acknowledged mode
1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2).

| +|

NPM Transfer Time (5 bit field)

This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode.

| +|

ASSIGNMENT TYPE (2 bit field)

This indicates the type of assignment. The coding of this field is as specified in sub-clause 11.2.7.

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

Carrier ID (1 bit field)
This identifies the carrier to which the description refers.

0 Carrier 1
1 Carrier 2

| | | | | | | | | | | | | +|

REPORTED TIMESLOTS (8 bit field)
The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is encoded as the TIMESLOT_ALLOCATION IE defined in sub-clause 12.18.

| | | | | | | | | | | | | +|

PDCH Pairs Description
This information element is defined in sub-clause 12.5.5.

| | | | | | | | | | | | | +|

RTTI_USF_MODE (1 bit field)
This field identifies whether RTTI or BTTI USF Mode is enabled for this uplink RTTI TBF.

0 BTTI USF Mode is enabled
1 RTTI USF Mode is enabled

| | | | | | | | | | | | | +|

TSH (2 bit field)

This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent:

bit
2 1
0 0 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI or MTTI configuration)
0 1 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI or MTTI configuration)
1 0 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI or MTTI configuration)
1 1 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI or MTTI configuration)
| bit | | 2 1 | | 0 0 | 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI or MTTI configuration) | 0 1 | 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI or MTTI configuration) | 1 0 | 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI or MTTI configuration) | 1 1 | 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI or MTTI configuration) | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI or MTTI configuration) | | | | | | | | | | | | +| 0 1 | 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI or MTTI configuration) | | | | | | | | | | | | +| 1 0 | 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI or MTTI configuration) | | | | | | | | | | | | +| 1 1 | 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI or MTTI configuration) | | | | | | | | | | | | +|

Uplink EGPRS Level (2 bit field)
This field specifies the group of modulation and coding schemes applicable to the TBF. This information element is defined in sub-clause 12.10f.

| | | | | | | | | | | | | +|

Pulse Format (N bit field)
This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in sub-clause 12.8.3.

| | | | | | | | | | | | | +|

N_USF, N_TS (4 bit field)
N_PAIRS (3 bit field)
These fields indicate the number USF allocations signalled. The number of USFs is given as the binary value of the corresponding field plus one.

See Annex K for details of the coding of these fields.

| | | | | | | | | | | | | +|

USF, USF_2 (3 bit field)
These fields indicate the USF values assigned to the MS for the assigned timeslot or PDCH pair.

In the case of RTTI mode with BTTI USF, the USF value specified in the USF field (respectively USF_2 field) applies to the first two (respectively second two) TDMA frames of the following basic radio block period (see sub-clauses 8.1.1.1, 8.1.1.2.1).

These fields are encoded as a binary representation of the USF value as defined in sub-clause 10.4.1.

The order in which USF assignments are encoded and the meaning when the number of repetitions of the USF is lower than the maximum is described in Annex K.

| | | | | | | | | | | | | +|

Indication of Upper Layer PDU Start for RLC UM (1 bit field)
This field is defined in section 11.2.7.

| | | | | | | | | | | | | +|

Enhanced Flexible Timeslot Assignment (1 bit field)
This field indicates whether Enhanced Flexible Timeslot Assignment, EFTA, shall be used for the assigned uplink TBF. This field is coded as follows:

0 Enhanced Flexible Timeslot Assignment, EFTA shall not be used for the assigned uplink TBF.
1 Enhanced Flexible Timeslot Assignment, EFTA shall be used for the assigned uplink TBF.

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

EMST_NW_Capability (1 bit field)
This information element indicates the network’s support of EMST

0 The network does not support EMST
1 The network supports EMST

| +|

MTTI_UPLINK_ASSIGNMENT_C1 (1 bit field)
MTTI_UPLINK_ASSIGNMENT_C2 (1 bit field)

These fields indicate whether the assigned uplink TBF operates in MTTI configuration. If present, a PDCH is assigned on the respective carrier in addition to any assigned PDCH-pairs. If set to '1' (respectively '0'), the assigned PDCH uses the timeslot immediately adjacent to and lower than (respectively higher than) the lower (respectively higher) timeslot used by the lowest numbered (respectively highest numbered) PDCH-pair assigned on that carrier. If no PDCH-pairs are assigned on one carrier, then the assigned PDCH for that carrier is on the same timeslot as the assigned PDCH on the other carrier, regardless of the value of the field.

| +|

EMSR Additional PFCs 1
EMSR Additional PFCs 2
EMSR Additional PFCs 3
These IEs are defined in section 11.2.7.

| +|

DLMC UL Carrier Info
This information element is used to describe the uplink carriers applicable to an uplink TBF assigned for a DLMC configuration. It provides information for one or more of the uplink carriers corresponding to the downlink carriers (see sub-clause 8.1.1.2.1 and 8.1.2.5) where the uplink carriers are referenced in ascending order starting with the uplink carrier corresponding to downlink carrier C1, followed by the uplink carrier corresponding to downlink carrier C2 and so on (see sub-clause 8.1.1.1.3 for the numbering of downlink carriers in a DLMC configuration). The assignment message allows for releasing an existing carrier, keeping an existing carrier unchanged, modifying an existing carrier or adding a new carrier.

| +|

UPLINK_TIMESLOT_ALLOCATION (8 bit field)
This field is defined in sub-clause 12.18.

| +|

UPLINK_PDCH_PAIR_DLMC
This field is defined in sub-clause 11.2.31

| +|

Dynamic Allocation 3
This information element provides information for an uplink carrier corresponding to a downlink carrier assigned for a DLMC configuration. It shall always include information for the lowest numbered PDCH/PDCH-pair assigned on the referenced uplink carrier. If information is excluded for any additional PDCH/PDCH-pair assigned for the referenced uplink carrier then the MS shall apply the information provided for the lowest numbered PDCH/PDCH-pair assigned for that carrier. This information element is defined in sub-clause 12.65.

| +|

Primary TSC Set (1 bit field)
If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the TSC set associated with the TSC value indicated by the Frequency Parameters IE, Dual Carrier Frequency Parameters IE or DLMC Frequency Parameters IE for use on the assigned uplink PS resources. This field is coded as follows:

0 TSC set 1
1 Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain).

| + +#### 11.2.29.1 Special requirements in dual transfer mode for uplink TBF + +Special requirements apply when an uplink TBF is assigned to a mobile station in dual transfer mode or about to enter dual transfer mode. + +If the mobile station has an RR connection to the network on a half-rate TCH, the network may assign an uplink TBF using the other sub-channel of the same timeslot for a half-rate PDCH (see 3GPP TS 45.002). In this case, the uplink assignment message shall be encoded with a timeslot allocation including the timeslot number for the half-rate TCH and the half-rate PDCH, and only that timeslot number. The mobile station shall interpret this allocation as an allocation of a half-rate PDCH. + +In dual transfer mode, the mobile station may be assigned an uplink TBF using exclusive allocation. The exclusive allocation shall be applied according to the conditions specified in sub-clause 8.1.0. When the exclusive allocation is applied, the mobile station shall ignore the USF values assigned in the uplink assignment message. + +### 11.2.29a Multiple TBF Uplink Assignment + +This message is sent on the PACCH by the network to the mobile station to assign uplink resources. If the mobile station supports Downlink Dual Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a). The mobile station may be addressed by the G-RNTI or the TFI depending upon the procedure used. A mobile allocation or reference frequency list received as part of this assignment message shall be valid until new assignment is received or each TBF of the MS are terminated. + +Message type: MULTIPLE TBF UPLINK ASSIGNMENT + +Direction: network to mobile station + +Classification : non-distribution message + +**Table 11.2.29a.1: MULTIPLE TBF UPLINK ASSIGNMENT information elements** + +``` + +< Multiple TBF Uplink Assignment message content > ::= + < PAGE_MODE : bit (2) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } + { { 0 < Global TFI : < Global TFI IE > > + | 10 { < TLLI / G-RNTI : < TLLI / G-RNTI IE > > < G-RNTI extension : bit (4) > } } + { 0 -- Message escape bit for GPRS mode TBFs + { { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Uplink TBF Assignment : < Uplink Assignment struct > > } + < padding bits > } + ! < Non-distribution part error : bit (*) = < no string > > } + | 1 -- Message escape bit for EGPRS mode TBFs + { 00 + { { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + < Resegment : < RESEGMENT IE > > + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Uplink TBF Assignment : < Uplink Assignment struct > > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-7 + { 0 | 1 < NPM Transfer Time : bit (5) > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + { 1 < Indication of Upper Layer PDU Start for RLC UM : bit > } ** 0 + < Enhanced Flexible Timeslot Assignment : bit > + } + } + < padding bits > } } + ! < Non-distribution part error : bit (*) = < no string > > } + | 01 -- Message escape for dual carrier, RTTI, BTTI with FANR activated, EGPRS2 + { { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + < Assignment Info : < Assignment Info struct > > + < RESEGMENT : bit (1) > + < TLLI_BLOCK_CHANNEL_CODING : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 00 -- No frequency parameters included + | 01 -- Legacy IEs used + { 0 | 1 < Frequency Parameters C1 : < Frequency Parameters IE > > } + { 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE > > } + | 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE > > + ! < Frequency Parameters error: { 11 } bit(*) = < no string > > } -- reserved for future used + } + { 0 | 1 < Uplink TBF Assignment 2 : < Uplink Assignment 2 struct > > } + < Uplink EGPRS Level : < EGPRS Level IE > > + { 0 | 1 < Pulse Format : < Pulse Format IE > > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + { 1 < Indication of Upper Layer PDU Start for RLC UM : bit > } ** 0 + < Enhanced Flexible Timeslot Assignment : bit > + } + < padding bits > } + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Message escape : { 10 | 11 } bit (*) = < no string > > } } - Extended for future changes + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + +``` + +``` + +< Uplink Assignment struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit(1) > } + { 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink TBF Assignment : < Uplink TBF Assignment struct > > } ** 0 } ; + +< Uplink Assignment 2 struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } + { 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } + { 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit(1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit(1) > } } + { 0 | 1 + -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < TSH : bit (2) > } } + { 0 | 1 + { 0 | 1 + -- BTTI mode + < Global Timeslot description : < Timeslot description 2 struct > > + { 1 < Uplink TBF Assignment 2 : < Uplink TBF Assignment 2 IE > > } ** 0 + } + { 0 | 1 + -- RTTI mode + + < PDCH Pairs Description : < PDCH Pairs Description struct > > + { 0 -- without power control parameters + | 1 -- with power control parameters + < ALPHA_C1 : bit (4) > + { 0 | 1 < ALPHA_C2 : bit (4) > } + < N_PAIRS : bit (3) > + { 0 | 1 < GAMMA : bit (5) > } * (val(N_PAIRS) + 1) + { 0 -- RTTI USF, or no second GAMMA values are given in case of RTTI mode with BTTI USF + | 1 -- Second GAMMA values are given in case of RTTI mode with BTTI USF + { 0 | 1 < GAMMA : bit (5) > } * (val(N_PAIRS) + 1) + } + } + { 1 < Uplink TBF Assignment 2 : < Uplink TBF Assignment 2 struct > > + < RTTI_USF_MODE : bit (1) > } ** 0 + } + } +}; + +< Timeslot description struct > ::= +{ 0 + < MS_TIMESLOT_ALLOCATION : bit (8) > -- without power control params +| 1 + < ALPHA : bit (4) > -- with power control params + { 0 | 1 < GAMMA_TN0 : bit (5) > } + { 0 | 1 < GAMMA_TN1 : bit (5) > } + { 0 | 1 < GAMMA_TN2 : bit (5) > } + { 0 | 1 < GAMMA_TN3 : bit (5) > } + { 0 | 1 < GAMMA_TN4 : bit (5) > } + { 0 | 1 < GAMMA_TN5 : bit (5) > } + { 0 | 1 < GAMMA_TN6 : bit (5) > } + { 0 | 1 < GAMMA_TN7 : bit (5) > } } ; + +``` + +``` + +< Timeslot description 2 struct > ::= +{ 0 + < MS_TIMESLOT_ALLOCATION_C1 : bit (8) > -- without power control params + { 0 | 1 < MS_TIMESLOT_ALLOCATION_C2 : bit (8) > } +| 1 -- with power control params + < ALPHA_C1 : bit (4) > + { 0 | 1 < GAMMA_TN0_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN1_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN2_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN3_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN4_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN5_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN6_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN7_C1 : bit (5) > } + { 0 | 1 < ALPHA_C2 : bit (4) > } + { 0 | 1 < GAMMA_TN0_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN1_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN2_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN3_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN4_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN5_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN6_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN7_C2 : bit (5) > } +}; + +< Uplink TBF Assignment struct > ::= -- Recursive for multiple TBFs +{ 0 < RB Id : bit (5) > +| 1 < PFI : bit (7) > } + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < USF_GRANULARITY : bit (1) > + { 0 -- The timeslots assigned to the TBF are all the timeslots assigned + -- in the Global Timeslot description + | 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > } -- The timeslots assigned to the TBF are a subset of all the + -- timeslots assigned in the Global Timeslot description. Where + -- N is the amount of timeslots assigned to the MS in the Global + -- Timeslot description + { 0 < USF_ALLOCATION : bit (3) > -- The same USF is valid on all timeslots assigned to the TBF + | 1 -- Different USF(s) assigned + < USF_ALLOCATION : bit (3) > -- USF assignment on the lowest numbered timeslot + -- assigned to the TBF + { 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) ; -- USFs on subsequent timeslots assigned to the TBF: + -- A '0' (respectively a '1' followed by a USF value) + -- means same (respectively different) USF value as the + -- USF on the next lower numbered timeslot assigned to + -- the TBF. Where M is the amount of timeslots assigned + -- to the TBF in the TBF_TIMESLOT_ALLOCATION if + -- present, else in the Global Timeslot description + } +} + +``` + +``` + +< Uplink TBF Assignment 2 struct > ::= -- Recursive for multiple TBFs + < PFI : bit (7) > + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + { 0 | 1 < EGPRS Channel Coding Command: < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < USF_GRANULARITY : bit (1) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates that time-based FANR is selected + < REPORTED TIMESLOTS C1: bit (8) > -- carrier 1 in Downlink Dual Carrier configuration + { 0 | 1 < REPORTED TIMESLOTS C2 : bit (8) > } -- carrier 2 in Downlink Dual Carrier configuration + } + { 0 -- The timeslots/PDCH-pairs assigned to the TBF are all the timeslots assigned + -- in the Global Timeslot description or PDCH pair description + | 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > } -- see description in Table 11.2.29a.2 + { 0 < USF_ALLOCATION_C1 : bit (3) > + { 0 | 1 < USF_ALLOCATION_C2 : bit (3) > } -- The same USF is valid on all timeslots/PDCH-pairs assigned + -- to the TBF for each specified carrier + | 1 -- Different USF(s) assigned; see description in Table 11.2.29a.2 + < USF_ALLOCATION : bit (3) > + { 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) + }; +< Assignment Info struct > ::= + < Assignment Type : bit (2) > + < Carrier ID : bit (1) > ; + +``` + +**Table 11.2.29a.2: MULTIPLE TBF UPLINK ASSIGNMENT information element details** + +| | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------|--|---|---|--|---|---|------|---|---|------|---|---|------|---|---|------| +| PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20. | | | | | | | | | | | | | | | | | | | +| PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1...4)
This field is defined in sub-clause 12.14, PRACH Control Parameters. | | | | | | | | | | | | | | | | | | | +| TLLI / G-RNTI
This information element is defined in sub-clause 12.16. | | | | | | | | | | | | | | | | | | | +| G-RNTI extension (4 bit field)

This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field or CONTENTION_RESOLUTION Identifier field which are necessary to provide a unique identifier for contention resolution in Iu-mode. | | | | | | | | | | | | | | | | | | | +| Global TFI
This information element identifies one of the mobile station's downlink or uplink TFIs. This field is defined in sub-clause 12.10. | | | | | | | | | | | | | | | | | | | +| CHANNEL_CODING_COMMAND (2 bit field)
The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting data on the uplink. If this field is included in the main body of the message, it shall refer to all GPRS TBF mode uplink TBFs assigned in the message (default value). If this field is included in the Uplink TBF Assignment struct, it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every TBF defined in GPRS TBF mode shall be assigned either the default value or a specific value.

Bit
2 1
0 0 CS-1
0 1 CS-2
1 0 CS-3
1 1 CS-4
| Bit | | | 2 | 1 | | 0 | 0 | CS-1 | 0 | 1 | CS-2 | 1 | 0 | CS-3 | 1 | 1 | CS-4 | +| Bit | | | | | | | | | | | | | | | | | | | +| 2 | 1 | | | | | | | | | | | | | | | | | | +| 0 | 0 | CS-1 | | | | | | | | | | | | | | | | | +| 0 | 1 | CS-2 | | | | | | | | | | | | | | | | | +| 1 | 0 | CS-3 | | | | | | | | | | | | | | | | | +| 1 | 1 | CS-4 | | | | | | | | | | | | | | | | | +| RESEGMENT (1 bit field)
This field is defined in sub-clause 12.10e. | | | | | | | | | | | | | | | | | | | + +#### **EGPRS Window Size** + +This information element is defined in sub-clause 12.5.2. + +If this field is included in the main body of the message, it shall refer to all EGPRS TBF mode uplink TBFs assigned in the message (default value). If this field is included in the Uplink TBF Assignment struct, it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every TBF defined in EGPRS TBF mode shall be assigned either the default value or a specific value. + +#### **EGPRS Modulation and Coding Scheme** + +This field contains the *EGPRS Modulation and Coding Scheme* information element defined in sub-clause 12.10d. + +If this field is included in the main body of the message, it shall refer to all EGPRS TBF mode uplink TBFs assigned in the message (default value). If this field is included in the Uplink TBF Assignment struct, it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every TBF defined in EGPRS TBF mode shall be assigned either the default value or a specific value. + +If this field is included in a Dual Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on both carriers. + +#### **TLLI\_BLOCK\_CHANNEL\_CODING** (1 bit field) + +This field indicates the channel coding command that the mobile station shall use for any RLC data block containing a TLLI / G-RNTI field in the RLC data block header. This field is coded as shown: + +- 0 the mobile station shall use CS-1 in GPRS TBF mode and MCS-1 in EGPRS TBF mode. +- 1 the mobile station shall use the value commanded in the CHANNEL\_CODING\_COMMAND or EGPRS\_CHANNEL\_CODING\_COMMAND field. + +#### **BEP\_PERIOD2** (4 bit field) + +This field contains a constant which is used for filtering channel quality measurements in EGPRS. BEP\_PERIOD2 when present, or if not, when received in a previous message of the same TBF session, shall be used instead of BEP\_PERIOD. For details see 3GPP TS 45.008. + +Range: 0 to 15 + +#### **TFI Assignment** (5 bit field) + +This information element assigns one TFI to each TBF assigned to the mobile station in this message. This field is repeated for each TBF that is assigned in this message. TFI values are encoded as defined in sub-clause 12.15. + +##### **RB Id** (5 bit field) + +This field contains the radio bearer identifier for the radio bearer using the assigned TBF. This provides the mapping of TFI to RB Id which is necessary to uniquely identify Iu-mode data flows. + +##### **PFI** (7 bit field) + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. + +#### **RLC\_MODE** (1 bit field) + +This field contains the RLC mode to be used for the assigned TBF. + +- 0 RLC acknowledged mode +- 1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2). + +#### **Uplink Control Timeslot (3 bit field)** + +In case of a BTTI configuration, this field contains the timeslot number of the timeslot where the PACCH for the MS is located. In case of an RTTI configuration, this field contains the timeslot number of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +#### **Uplink Control Timeslot C1 (3 bit field)** + +In case of a BTTI configuration, this field contains the timeslot number of the timeslot where the PACCH for the MS is located. In case of an RTTI configuration, this field contains the timeslot number of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. If the Assignment Type field is present and indicates 'Dual Carrier assignment', this field applies to carrier 1, otherwise this field applies to the carrier identified by the Carrier ID field. + +##### **Uplink Control Timeslot C2 (3 bit field)** + +If the Assignment Type field is present and indicates 'Dual Carrier assignment', this field contains the timeslot number on carrier 2 of the timeslot where the PACCH for the MS is located in case of a BTTI configuration, or the timeslot number of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the MS is located in case of an RTTI configuration. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +#### **Packet Timing Advance** + +This information element is defined in sub-clause 12.12. + +#### **Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink TBF. If this information element is not present the mobile station shall use its previously assigned frequency parameters. This information element is defined in sub-clause 12.8. + +##### **Frequency Parameters C1, Frequency Parameters C2** + +These information elements are coded as defined in sub-clause 12.8. See sub-clause 11.2.7 for the usage of these information elements. + +##### **Dual Carrier Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink TBF for both carriers in a dual carrier configuration. This information element is defined in sub-clause 12.8.2. + +#### **EXTENDED\_DYNAMIC\_ALLOCATION (1 bit field)** + +This information field indicates the medium access mode to be used during the TBF. + +- 0 Dynamic Allocation +- 1 Extended Dynamic Allocation + +#### **TBF Starting Time** + +The TBF Starting Time field contains a starting time that indicates the frame number during which the assigned TBF may start. + +In case of dynamic allocation, if no uplink TBF is in progress, the MS need not monitor the USF field until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. If an uplink TBF is already in progress, the MS shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. + +In case of single block allocation, the mobile station shall use the assigned timeslot during the RLC/MAC block whose first TDMA burst occurs in the indicated TDMA frame number. + +This information element is encoded as the Starting Frame Number Description IE. See sub-clause 12.21. + +#### **MS\_TIMESLOT\_ALLOCATION** (8 bit field) + +This information field indicates the timeslots assigned for use by the MS for the assigned uplink TBFs. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least one timeslot must be assigned. In case of a timeslot allocation without power control parameters, the values of the power control parameters for assigned timeslots shall be the default values as specified in 3GPP TS 45.008. However, in case some of the timeslots assigned by this message are already used by the mobile station, the mobile station shall continue to use the current power control parameters for these timeslots. + +- 0 Timeslot is not assigned +- 1 Timeslot is assigned + +#### **TIMESLOT\_ALLOCATION\_C1, TIMESLOT\_ALLOCATION\_C2** (8 bit field) + +The usage of these fields is as specified in sub-clause 11.2.7. + +At least one timeslot must be assigned. In case of a timeslot allocation without power control parameters, the values of the power control parameters for assigned timeslots shall be the default values as specified in 3GPP TS 45.008. However, in case some of the timeslots assigned by this message are already used by the mobile station, the mobile station shall continue to use the current power control parameters for these timeslots. + +- 0 Timeslot is not assigned +- 1 Timeslot is assigned + +#### **TBF\_TIMESLOT\_ALLOCATION** (N bit field) + +This information field indicates the timeslots assigned to a particular uplink TBF, within the timeslots assigned to the MS in the Global Timeslot description. This field contains as many bits as there are timeslots assigned to the MS in the Global Timeslot description. Bit N indicates the status of the lowest numbered timeslot in the timeslots assigned to the MS in the Global Timeslot description. Bit N-1 (if any) indicates the status of the next lowest numbered timeslot, etc. At least one timeslot must be assigned per TBF + +- 0 Timeslot is not assigned +- 1 Timeslot is assigned + +#### **USF\_ALLOCATION** (3 bit field) + +This field indicates the USF value assigned to the MS for one or more assigned timeslots. This field is encoded as a binary presentation of the USF value as defined in sub-clause 10.4.1. + +##### **USF\_ALLOCATION\_C1, USF\_ALLOCATION\_C2** (3 bit field) + +These fields indicate the USF value assigned for all timeslots on the relevant carrier. + +If the Assignment Type field is present and indicates 'Dual Carrier assignment', USF\_ALLOCATION\_C1 applies to carrier 1, otherwise it applies to the carrier identified by the Carrier ID field. + +If the Assignment Type field is present and indicates 'Dual Carrier assignment', and USF\_ALLOCATION\_C1 is present and USF\_ALLOCATION\_C2 is absent, the value specified by USF\_ALLOCATION\_C1 applies to timeslots assigned on both carriers. + +#### **USF\_GRANULARITY** (1 bit field) + +This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation. + +- 0 the mobile station shall transmit one RLC/MAC block +- 1 the mobile station shall transmit four consecutive RLC/MAC blocks + +##### **ALPHA** (4 bit field) + +For encoding and description see the Global Power Control Parameters IE. + +##### **ALPHA\_C1, ALPHA\_C2** (4 bit field) + +These fields indicate the value of the parameter alpha to be applied in power control. For encoding and description see the Global Power Control Parameters IE. For usage of these parameters, see sub-clause 11.2.29. + +**N\_PAIRS (3 bit field)** + +This field indicate the number of PDCH pairs for which GAMMA values are signalled. The number PDCH pairs is given as the binary value of the corresponding field plus one. + +See Annex K for details of the coding of this field. + +--- + +**GAMMA, GAMMA\_TN (5 bit field)** + +The field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +bit + +5 4 3 2 1 + +0 0 0 0 0      $\Gamma_{CH} = 0$ dB + +0 0 0 0 1      $\Gamma_{CH} = 2$ dB + +: : : : + +1 1 1 1 0      $\Gamma_{CH} = 60$ dB + +1 1 1 1 1      $\Gamma_{CH} = 62$ dB + + + +**GAMMA\_TN\_C1 (5 bit field), GAMMA\_TN\_C2 (5 bit field)** + +For usage and coding of these parameters, see sub-clause 11.2.29. + +--- + +**P0 (4 bit field)** + +This field is an optional downlink power control parameter. If P0 is present, then downlink power control is used; otherwise, if P0 is not present, then downlink power control is not used. It is encoded as follows: + +bit + +4 3 2 1 + +0 0 0 0      $P0 = 0$ dB + +0 0 0 1      $P0 = 2$ dB + +0 0 1 0      $P0 = 4$ dB + +: + +1 1 1 1      $P0 = 30$ dB + + + +**P0\_C1, P0\_C2 (4 bit field)** + +For the usage of these fields, see sub-clause 11.2.29. + +--- + +**PR\_MODE (1 bit field)** + +This field indicates the PR Management mode, as defined in 3GPP TS 45.008. It is encoded as follows: + +0    PR mode A: for one addressed MS + +1    PR mode B: for all MS + + + +**PR\_MODE\_C1, PR\_MODE\_C2 (1 bit field)** + +For the usage of these fields, see sub-clause 11.2.29. + +--- + +**Packet Extended Timing Advance (2 bit field)** + +This field is defined in sub-clause 12.12b. + +--- + +**NPM Transfer Time (5 bit field)** + +This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode + + + +The list of NPM Transfer Time IEs in the Rel-7 additions is ordered as described by the loops in the earlier releases part. + +--- + +**Assignment Type (2 bit field)** + +This field is defined in sub-clause 11.2.7. + +--- + +**Carrier ID (1 bit field)** + +This identifies the carrier to which the description refers. + + + +0    Carrier 1 + +1    Carrier 2 + +| | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----|-----------------------------------------------------------------------------------------|-----|--------------------------------------------------------------------------------------------------|-----|--------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------| +|

REPORTED TIMESLOTS (8 bit field)
The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is encoded as the TIMESLOT_ALLOCATION IE defined in sub-clause 12.18.

| | | | | | | | | | | | | +|

Uplink TBF Assignment 2 struct
If the TBF_TIMESLOT_ALLOCATION bitmap is present, then the timeslots/PDCH-pairs assigned to the TBF are a subset of all the timeslots assigned in the Global Timeslot description or PDCH-pairs described in the PDCH-pair description. In BTTI mode, N is the number of timeslots assigned to the MS in the Global Timeslot description. In RTTI mode N is the number of PDCH-pairs described in the PDCH-pair description.

If different USFs are assigned on different timeslots/PDCH-pairs, then the USFs are listed in increasing order of timeslot numbers. In BTTI mode, M is the number of timeslots assigned to the TBF in the TBF_TIMESLOT_ALLOCATION if present, else in the Global Timeslot description. In RTTI configurations using RTTI USF mode M is the number of PDCH-pairs assigned to the TBF in the TBF_TIMESLOT_ALLOCATION if present, else M is the number of PDCH-pairs described in the PDCH-pair description. In RTTI configurations using BTTI USF mode M is twice the number of PDCH-pairs assigned to the TBF in the TBF_TIMESLOT_ALLOCATION if present, else M is twice the number of PDCH-pairs described in the PDCH-pair description.

If no USF is specified, then the USF value is the same as the previously indicated USF value.

| | | | | | | | | | | | | +|

PDCH Pairs Description
This information element is defined in sub-clause 12.5.5.

| | | | | | | | | | | | | +|

RTTI USF Mode (1 bit field)
This field is as specified in the Packet Uplink Assignment message

| | | | | | | | | | | | | +|

TSH (2 bit field)

This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent:

bit
2 1
0 0 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI configuration)
0 1 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI configuration)
1 0 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI configuration)
1 1 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI configuration)
| bit | | 2 1 | | 0 0 | 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI configuration) | 0 1 | 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI configuration) | 1 0 | 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI configuration) | 1 1 | 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI configuration) | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI configuration) | | | | | | | | | | | | +| 0 1 | 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI configuration) | | | | | | | | | | | | +| 1 0 | 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI configuration) | | | | | | | | | | | | +| 1 1 | 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI configuration) | | | | | | | | | | | | +|

Uplink EGPRS Level (2 bit field)
This field specifies the group of modulation and coding schemes applicable to the TBF(s). This information element is defined in sub-clause 12.10f.

| | | | | | | | | | | | | +|

Pulse Format (N bits field)
This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in sub-clause 12.8.3.

| | | | | | | | | | | | | +|

Indication of Upper Layer PDU Start for RLC UM (1 bit field)
This field is defined in section 11.2.7a.

| | | | | | | | | | | | | +|

Enhanced Flexible Timeslot Assignment (1 bit field)
This field indicates whether Enhanced Flexible Timeslot Assignment, EFTA, shall be used for all assigned uplink TBFs. This field is coded as follows:

0 Enhanced Flexible Timeslot Assignment, EFTA shall not be used for all assigned uplink TBFs.
1 Enhanced Flexible Timeslot Assignment, EFTA shall be used for all assigned uplink TBFs.
| 0 | Enhanced Flexible Timeslot Assignment, EFTA shall not be used for all assigned uplink TBFs. | 1 | Enhanced Flexible Timeslot Assignment, EFTA shall be used for all assigned uplink TBFs. | | | | | | | | | +| 0 | Enhanced Flexible Timeslot Assignment, EFTA shall not be used for all assigned uplink TBFs. | | | | | | | | | | | | +| 1 | Enhanced Flexible Timeslot Assignment, EFTA shall be used for all assigned uplink TBFs. | | | | | | | | | | | | + +### 11.2.30 (void) + +### 11.2.30a Packet Pause + +This optional message is sent on the PACCH from a mobile station with non-GSM capabilities to the network to request a pause of GPRS services. + +Message type: PACKET PAUSE + +Direction: mobile station to network + +**Table 11.2.30a.1: PACKET PAUSE information elements** + +| | +|--------------------------------------| +| < Packet pause message content > ::= | +| < TLLI : bit (32) > | +| < RAI : bit (48) > | +| < padding bits > ; | + +**Table 11.2.30a.2: PACKET PAUSE information element details** + +#### **TLLI** (32 bit field) + +This field contains the TLLI of the mobile station. This field is encoded as defined in sub-clause 12.16. + +#### **RAI** (48 bit field) + +This field contains the Routing Area identification. This field is described in 3GPP TS 44.018. + +### 11.2.31 Packet Timeslot Reconfigure + +This message is sent on the PACCH by the network to the mobile station to assign uplink and downlink resources. If the mobile station supports Downlink Dual Carrier or Downlink Multi Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a). A mobile allocation or reference frequency list received as part of this assignment message shall be valid until a new assignment is received or each TBF of the MS are terminated. + +Message type: PACKET TIMESLOT RECONFIGURE + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.31.1: PACKET TIMESLOT RECONFIGURE information elements** + +`< Packet Timeslot Reconfigure message content > ::= +   < PAGE_MODE : bit (2) > +   { 0 < GLOBAL_TFI : < Global TFI IE > > +     { 0 -- Message escape +       { < CHANNEL_CODING_COMMAND : bit (2) > +         < Global Packet Timing Advance : < Global Packet Timing Advance IE > > +         < DOWNLINK_RLC_MODE : bit (1) > +         < CONTROL_ACK : bit (1) > +         { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } +         { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } +         < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > +         { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } +         0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. +         < Dynamic Allocation : < Dynamic Allocation struct > > +         { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +         | 1 -- Additions for R99 +           { 0 | 1 < Packet Extended Timing Advance : bit (2) > } +           { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +           | 1 -- Additions for Rel-5 +             { 0 | 1 < RB Id of downlink TBF : bit (5) > +               < RB Id of uplink TBF : bit (5) > } +             { 0 | 1 < Uplink Control Timeslot : bit (3) > } +             { null | 0 bit** = < no string > -- Receiver backward compatible +             | 1 -- Additions for Rel-6 +               { 0 | 1 < PFI of downlink TBF : bit (7) > } +               { 0 | 1 < PFI of uplink TBF : bit (7) > } +               { 0 | 1 < UPLINK_RLC_MODE : bit (1) > } +               { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used +               | 1 -- EMST is used +                 { 0 +                 | 1 < Downlink RLC Entity 2 : < RLC Entity Struct > +                   { 0 +                   | 1 < Downlink RLC Entity 3 : < RLC Entity Struct > } +                 } +                 { 0 +                 | 1 < Uplink RLC Entity 2 : < RLC Entity Struct > +                   { 0 +                   | 1 < Uplink RLC Entity 3 : < RLC Entity Struct > } +                 } +               } +             } +           } +         } +         { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +         | 1 -- Additions for Rel-10 +           { 0 -- EMSR is not enabled in downlink +           | 1 -- EMSR is enabled in downlink +             { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 +             { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 +             { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 +           } +           { 0 -- EMSR is not enabled in uplink +           | 1 -- EMSR is enabled in uplink +             { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 +             { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 +             { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 +           } +         } +         { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +         | 1 -- Additions for Rel-12 +           < Primary TSC Set : bit (1) > +           { 0 | 1 -- Secondary DL TSC Value assigned +             < Secondary DL TSC Set : bit (1) > +             < Secondary DL TSC Value : bit (3) > } +           < padding bits > } } } } } +   ! < Non-distribution part error : bit (*) = < no string > > }` + +``` + +| 1 -- Message escape bit used to define EGPRS message contents +{ 00 { { 0 | 1 < COMPACT reduced MA : < COMPACT reduced MA IE >> } + < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >> + < RESEGMENT : bit (1) > + { 0 | 1 < DOWNLINK EGPRS Window Size : < EGPRS Window Size IE >> } + { 0 | 1 < UPLINK EGPRS Window Size : < EGPRS Window Size IE >> } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + < Global Packet Timing Advance : < Global Packet Timing Advance IE >> + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + < DOWNLINK_RLC_MODE : bit (1) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } + < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE >> } + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < Dynamic Allocation : < Dynamic Allocation struct >> + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 -- Additions for Rel-5 + { 0 | 1 < RB Id of downlink TBF : bit (5) > + < RB Id of uplink TBF : bit (5) > } + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + { null | 0 bit** = < no string > -- Receiver backward compatible +| 1 -- Additions for Rel-6 + { 0 | 1 < PFI of downlink TBF : bit (7) > } + { 0 | 1 < PFI of uplink TBF : bit (7) > } + { 0 | 1 < UPLINK_RLC_MODE : bit (1) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 -- Additions for Rel-7 + { 0 | 1 < Downlink NPM Transfer Time : bit (5) > } + { 0 | 1 < Uplink NPM Transfer Time : bit (5) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 -- Additions for Rel-9 + < Indication of Upper Layer PDU Start for RLC UM : bit > + < Enhanced Flexible Timeslot Assignment : bit > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + < padding bits > } } } } } +! < Non-distribution part error : bit (*) = < no string >> } +| 01 -- escape for Downlink Dual Carrier, BTTI using FANR, EGPRS2, RTTI +{ < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >> + < RESEGMENT : bit (1) > + < Assignment Info : Assignment Info struct > + { 0 | 1 < DOWNLINK EGPRS Window Size : < EGPRS Window Size IE >> } + { 0 | 1 < UPLINK EGPRS Window Size : < EGPRS Window Size IE >> } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + < Global Packet Timing Advance : < Global Packet Timing Advance IE >> + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + < DOWNLINK_RLC_MODE : bit (1) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } + +``` + +``` + +{ 0 -- BTTI mode + < TIMESLOT_ALLOCATION_C1 : bit (8) > + { 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } +| 1 -- RTTI mode + < RTTI_USF_MODE : bit (1) > + { 0 -- Single Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > + | 1 -- Dual Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > + } +} +{ 00 -- No frequency parameters included +| 01 -- Legacy IEs used + { 0 | 1 < Frequency Parameters C1 : < Frequency Parameters IE > > } + { 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE > > } +| 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE > > + ! < Frequency Parameters error: { 1 1 } bit(*) = < no string> > -- reserved for future used +} +< Dynamic Allocation 2 : < Dynamic Allocation 2 struct > > +{ 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } +{ 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } +{ 0 | 1 < PFI of downlink TBF : bit (7) > } +{ 0 | 1 < PFI of uplink TBF : bit (7) > } +{ 0 | 1 < UPLINK_RLC_MODE : bit (1) > } +{ 0 | 1 < Downlink NPM Transfer Time : bit (5) > } +{ 0 | 1 < Uplink NPM Transfer Time : bit (5) > } +{ 0 -- Fast Ack/Nack Reporting is not activated for the downlink TBF; +| 1 -- Fast Ack/Nack Reporting is activated for the downlink TBF + < EVENT_BASED_FANR: bit (1) > } +{ 0 -- Fast Ack/Nack Reporting is not activated for the uplink TBF +| 1 -- Fast Ack/Nack Reporting is activated for the uplink TBF + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < REPORTED TIMESLOTS C1 : bit (8) > -- carrier 1 in Downlink Dual Carrier + -- configuration + { 0 | 1 < REPORTED TIMESLOTS C2 : bit (8) > } -- carrier 2 in Downlink Dual Carrier + -- configuration + < TSH : bit (2) > } } -- This structure shall be considered only valid if + -- an uplink TBF is addressed +< Uplink EGPRS Level: < EGPRS Level IE > > +< Downlink EGPRS Level: < EGPRS Level IE > > +{ 0 | 1 < Pulse Format: < Pulse Format IE > > } +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 -- Additions for Rel-9 + < Indication of Upper Layer PDU Start for RLC UM: bit > + < Enhanced Flexible Timeslot Assignment : bit > + { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used + | 1 -- EMST is used + { 0 + | 1 < Downlink RLC Entity 2 : < RLC Entity Struct > + { 0 + +``` + +``` + + | 1 < Downlink RLC Entity 3 : < RLC Entity Struct > } + } + { 0 + | 1 < Uplink RLC Entity 2 : < RLC Entity Struct > + { 0 + | 1 < Uplink RLC Entity 3 : < RLC Entity Struct > } + } +} +{ 0 | 1 MTTI_DOWNLINK_ASSIGNMENT_C1 : bit (1) } +{ 0 | 1 MTTI_DOWNLINK_ASSIGNMENT_C2 : bit (1) } +{ 0 | 1 MTTI_UPLINK_ASSIGNMENT_C1 : bit(1) } +{ 0 | 1 MTTI_UPLINK_ASSIGNMENT_C2 : bit(1) } +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 + -- Additions for Rel-10 + { 0 + -- EMSR is not enabled in downlink + | 1 + -- EMSR is enabled in downlink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + { 0 + -- EMSR is not enabled in uplink + | 1 + -- EMSR is enabled in uplink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } +} +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 + -- Additions for Rel-11 + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 + -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + { 0 | 1 + -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } +< padding bits > } } } } +! < Non-distribution part error : bit (*) = < no string > > } + +``` + +``` + +| 10 -- escape for Downlink Multi Carrier, BTTI using FANR, EGPRS2, RTTI +{ + < DOWNLINK_RLC_MODE : bit (1) > + < CONTROL_ACK : bit (1) > + { 1 < UFPS : < UFPS struct > > } ** 0 + DLMC Measurement Type : bit (1) + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < Carrier for Interference Measurements : bit (4) > } + < Global Packet Timing Advance : < Global Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < PTCCH_CARRIER : bit (4) > } + < PDAN Coding : bit (1) > + < Extended SNS : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + { 0 | 1 < PFI of downlink TBF : bit (7) > } + { 0 | 1 < Downlink NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates Fast Ack/Nack Reporting is activated for downlink TBF + < EVENT_BASED_FANR: bit (1) > } + < Downlink EGPRS Level: < EGPRS Level IE > > + < Indication of Upper Layer PDU Start for RLC UM : bit > + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >> } +{ + < RESEGMENT : bit (1) > + { 1 < < DLMC UL Carrier Info : < DLMC UL Carrier Info struct > > } ** 0 + { 0 | 1 < UPLINK EGPRS Window Size : < EGPRS Window Size IE > > } + < UPLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < PFI of uplink TBF : bit (7) > } + { 0 | 1 < UPLINK_RLC_MODE : bit (1) > } + { 0 | 1 < Uplink NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < REPORTED TIMESLOTS : bit (8) > + < TSH : bit (2) > } } + < Uplink EGPRS Level: < EGPRS Level IE > > + { 0 | 1 < Pulse Format: < Pulse Format IE > > } + < Enhanced Flexible Timeslot Assignment : bit > + { 0 | 1 < Uplink Control Timeslot : bit (3) > } } + ! < Message escape : { 11 } bit (*) = > } } -- Extended for future changes + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + + ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + +``` + +``` + +{ 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } +< USF_GRANULARITY : bit (1) > +0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. +{ 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > } +{ 0 -- Timeslot Allocation + { 0 | 1 < USF_TN0 : bit (3) > } + { 0 | 1 < USF_TN1 : bit (3) > } + { 0 | 1 < USF_TN2 : bit (3) > } + { 0 | 1 < USF_TN3 : bit (3) > } + { 0 | 1 < USF_TN4 : bit (3) > } + { 0 | 1 < USF_TN5 : bit (3) > } + { 0 | 1 < USF_TN6 : bit (3) > } + { 0 | 1 < USF_TN7 : bit (3) > } +| 1 -- Timeslot Allocation with Power Control Parameters + < ALPHA : bit (4) > + { 0 | 1 < USF_TN0 : bit (3) > + < GAMMA_TN0 : bit (5) > } + { 0 | 1 < USF_TN1 : bit (3) > + < GAMMA_TN1 : bit (5) > } + { 0 | 1 < USF_TN2 : bit (3) > + < GAMMA_TN2 : bit (5) > } + { 0 | 1 < USF_TN3 : bit (3) > + < GAMMA_TN3 : bit (5) > } + { 0 | 1 < USF_TN4 : bit (3) > + < GAMMA_TN4 : bit (5) > } + { 0 | 1 < USF_TN5 : bit (3) > + < GAMMA_TN5 : bit (5) > } + { 0 | 1 < USF_TN6 : bit (3) > + < GAMMA_TN6 : bit (5) > } + { 0 | 1 < USF_TN7 : bit (3) > + < GAMMA_TN7 : bit (5) > } } ; + +< Dynamic Allocation 2 struct > ::= +< EXTENDED_DYNAMIC_ALLOCATION : bit (1) > +{ 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit (1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit (1) > } } +< USF_GRANULARITY : bit (1) > +{ 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } +{ 0 -- Allocation without Power Control Parameters + < N_USF : bit (4) > + { 0 | 1 < USF : bit (3) > } *( val(N_USF) + 1) +| 1 -- Allocation with Power Control Parameters + < ALPHA_C1 : bit (4) > + { 0 | 1 < ALPHA_C2 : bit (4) > } + { 0 -- BTTI mode + < N_TS : bit (4) > + { 0 | 1 + < USF : bit (3) > + < GAMMA : bit (5) > + } * ( val(N_TS) + 1) + | 1 -- RTTI mode + < N_PAIRS : bit (3) > + { 0 | 1 + < USF : bit (3) > + < GAMMA : bit (5) > + } * ( val(N_PAIRS) + 1) + { 0 -- RTTI USF + | 1 -- BTTI USF + { 0 | 1 < USF_2 : bit (3) > + { 0 | 1 < GAMMA : bit (5) > } + } * ( val(N_PAIRS) + 1) + } + } +} ; + +``` + +``` +< Assignment Info struct > ::= + < Assignment Type : bit (2) > + < Carrier ID : bit (1) >; + +< RLC Entity Struct > ::= + < TFI : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < PFI : bit (7) >; + +< UFPS struct > ::= + { 00 -- Existing UFPS released + | 01 -- Existing UFPS remains unchanged (no information provided) + | 10 -- Existing UFPS changed/new UFPS provided + { 0 -- Existing DLMC Frequency Parameters unchanged + | 1 < DLMC Frequency Parameters : < DLMC Frequency Parameters IE > > } + { 1 < CARRIER_SPECIFIC_INFO : < Carrier Specific Info struct > > } ** 0 + | 11 bit (*) = < no string > -- Reserved + }; +``` + +``` + +< Carrier Specific Info struct > ::= +{ + 00 -- Existing carrier released + | 01 -- Existing carrier remains unchanged (no information provided) + | 10 -- Existing carrier changed/new carrier provided + { 0 + { 0 + -- same timeslots as the lowest numbered carrier + | 1 < TIMESLOT_ALLOCATION : bit (8) > } + | 1 + -- RTTI mode + { 0 + -- same PDCH-pairs as the lowest numbered carrier + | 1 < DOWNLINK_PDCH_PAIRS_DLMC : bit (8) > + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DLMC : bit (4) > } + } + { 0 | 1 < MAIO : bit (6) > } + { 0 + -- same P0 and PR_MODE as the lowest numbered carrier + | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + { 0 + -- same DOWNLINK_TFI_ASSIGNMENT as the lowest numbered carrier + | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } + } + { 0 + -- same Power Control Parameters as the lowest numbered carrier + | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 + -- EMST is not used on this carrier + | 1 + -- EMST is used on this carrier + < RLC Entity 2 : < RLC Entity Struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } + { 0 | 1 < RLC Entity 3 : < RLC Entity Struct > > } + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } + } + { 0 + -- EMSR is not used on this carrier + | 1 + -- EMSR is used on this carrier + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } ** 0 + } + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } ** 0 + } + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } ** 0 + } + } + < Primary TSC Set : bit (1) > + { 0 | 1 + -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + | 11 bit (*) = < no string > -- Reserved +}; + +< DLMC UL Carrier Info struct > ::= +{ + 00 -- Assigned carrier released + | 01 -- Carrier remains unchanged (no information provided) + | 10 -- Assigned carrier modified or new carrier assigned + { 0 + -- BTTL mode + { 0 | 1 < UPLINK_TIMESLOT_ALLOCATION : bit (8) > } -- assigned PDCH + | 1 + -- RTTI mode + { 0 | 1 < UPLINK_PDCH_PAIRS_DLMC : bit (8) > } -- assigned PDCH-pairs + } + < Dynamic Allocation 3 : < Dynamic Allocation 3 IE > > + { 0 + -- EMST is not used on this carrier + | 1 + -- EMST is used on this carrier + < Uplink RLC Entity 2 : < RLC Entity Struct > + { 0 | 1 < Uplink RLC Entity 3 : < RLC Entity Struct > } + } + { 0 + -- EMSR is not used on this carrier + | 1 + -- EMSR is used on this carrier + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + < Primary TSC Set : bit (1) > + | 11 bit (*) = < no string > -- reserved +}; + +``` + +**Table 11.2.31.2: PACKET TIMESLOT RECONFIGURE information element details** + +| | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--|-----|--|-----|------|-----|------|-----|------|-----|------| +|

Global TFI (6 bit field)

This field identifies (one of) the uplink TFI, if available, or (one of) the downlink TFI, to which this message applies. This field is defined in sub-clause 12.10.

| | | | | | | | | | | | | +|

CHANNEL_CODING_COMMAND (2 bit field)

The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting on the uplink.

bit
2 1
0 0 CS-1
0 1 CS-2
1 0 CS-3
1 1 CS-4
| bit | | 2 1 | | 0 0 | CS-1 | 0 1 | CS-2 | 1 0 | CS-3 | 1 1 | CS-4 | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | CS-1 | | | | | | | | | | | | +| 0 1 | CS-2 | | | | | | | | | | | | +| 1 0 | CS-3 | | | | | | | | | | | | +| 1 1 | CS-4 | | | | | | | | | | | | +|

COMPACT reduced MA

This information element is defined in sub-clause 12.29.

| | | | | | | | | | | | | +|

EGPRS Modulation and Coding Scheme

The EGPRS modulation and coding scheme information element is defined in sub-clause 12.10d.

If this field is included in a Dual Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on both carriers. If this field is included in a Multi Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on all carriers.

| | | | | | | | | | | | | +|

RESEGMENT (1 bit field)

This field is defined in sub-clause 12.10e.

| | | | | | | | | | | | | +|

EGPRS Window Size

This information element is defined in sub-clause 12.5.2.

| | | | | | | | | | | | | +|

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)

This field is encoded as the LINK_QUALITY_MEASUREMENT_MODE IE of the PACKET DOWNLINK ASSIGNMENT message, as defined in sub-clause 11.2.7.

| | | | | | | | | | | | | +|

BEP_PERIOD2 (4 bit field)

This field contains a constant which is used for filtering channel quality measurements in EGPRS. BEP_PERIOD2 when present, or if not, when received in a previous message of the same TBF session, shall be used instead of BEP_PERIOD. For details see 3GPP TS 45.008. Range: 0 to 15

| | | | | | | | | | | | | +|

Global Packet Timing Advance

This information element is defined in sub-clause 12.12a.

| | | | | | | | | | | | | +|

DOWNLINK_RLC_MODE (1 bit field)

RLC_MODE (1 bit field)

This field indicates the RLC mode of the requested TBF. If a new mode is assigned by the network for an already established TBF, the MS shall ignore the new assigned mode and shall maintain the TBF in the old mode. If EMST is used, this field indicates the RLC mode of the RLC entity.

0 RLC acknowledged mode

1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2).

| | | | | | | | | | | | | +|

CONTROL_ACK (1 bit field)

This field shall be set to '1' if the network establishes a new downlink TBF for the mobile station whose timer T3192 is running. Otherwise this field shall be set to '0'.

| | | | | | | | | | | | | + +#### **DOWNLINK\_TFI\_ASSIGNMENT** (5 bit field) + +#### **TFI** (5 bit field) + +This information element, if present, assigns the contained TFI to the mobile station to identify a downlink TBF described by this message. This field is coded the same as the TFI field defined in sub-clause 12.15. If EMSR is supported, each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the downlink TBF. + +If a DLMC configuration is established, the assignment message shall provide the DOWNLINK\_TFI\_ASSIGNMENT IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the DOWNLINK\_TFI\_ASSIGNMENT IE for the first carrier in the first UFPS shall apply. + +#### **UPLINK\_TFI\_ASSIGNMENT** (5 bit field) + +#### **TFI** (5 bit field) + +This information element, if present, assigns the contained TFI to the mobile station to identify an uplink TBF described by this message. This field is coded the same as the TFI field defined in sub-clause 12.15. If EMSR is supported, each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the uplink TBF. + +#### **DOWNLINK\_TIMESLOT\_ALLOCATION** (8 bit field) + +#### **UPLINK\_TIMESLOT\_ALLOCATION** (8 bit field) + +This field is defined in sub-clause 12.18. + +#### **TIMESLOT\_ALLOCATION\_C1, TIMESLOT\_ALLOCATION\_C2** (8 bit field) + +These fields indicate the assigned timeslots for the downlink TBF. The usage of these fields is as specified in sub-clause 11.2.7. + +#### **Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink and downlink TBFs. If this information element is not present the mobile station shall use its previously assigned frequency parameters. This information element is defined in sub-clause 12.8. + +##### **Frequency Parameters C1, Frequency Parameters C2** + +These information elements are coded as defined in sub-clause 12.8. The usage of these fields is as specified in sub-clause 11.2.7. + +##### **Dual Carrier Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink TBF for both carriers in a dual carrier configuration. This information element is defined in sub-clause 12.8.2. + +#### **Dynamic Allocation struct** + +This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation. + +#### **Dynamic Allocation 2 struct** + +This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation in a dual carrier, RTTI, BTTI with FANR activated, or EGPRS2 configuration. + +#### **Power Control Parameters** + +This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation in a multi carrier, RTTI, BTTI with FANR activated, or EGPRS2 configuration (see sub-clause 12.13). + +In case of a timeslot allocation without power control parameters, the values of the power control parameters for assigned timeslots shall be the default values as specified in 3GPP TS 45.008. However, in case some of the timeslots assigned by this message are already used by the mobile station, the mobile station shall continue to use the current power control parameters for these timeslots. + +For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the Power Control Parameters IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the Power Control Parameters IE for the first carrier in the first UFPS shall apply. + +**EXTENDED\_DYNAMIC\_ALLOCATION** (1 bit field) + +This information field indicates the medium access mode to be used during the TBF. + +- 0 Dynamic Allocation +- 1 Extended Dynamic Allocation + +--- + +**TBF Starting Time** + +The TBF Starting Time field contains a starting time that indicates the frame number during which the assigned TBF may start. + +If no downlink TBF is in progress, the mobile station need not monitor the TFI field of downlink RLC data blocks until the indicated TDMA frame number. After the indicated TDMA frame number, the mobile station shall apply the new downlink parameters and then operate as during a downlink TBF. If a downlink TBF is already in progress, the mobile station shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to use the new downlink parameters assigned. + +If no uplink TBF is in progress, the MS need not monitor the USF field until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. If an uplink TBF is already in progress, the MS shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. + +This field is encoded as the Starting Frame Number Description IE. See sub-clause 12.21 + +--- + +**USF\_TN0** (3 bit field) +**USF\_TN1** (3 bit field) +**USF\_TN2** (3 bit field) +**USF\_TN3** (3 bit field) +**USF\_TN4** (3 bit field) +**USF\_TN5** (3 bit field) +**USF\_TN6** (3 bit field) +**USF\_TN7** (3 bit field) + +These fields indicate the USF value assigned to the MS for timeslots 0 to 7. These fields are encoded as a binary presentation of the USF value as defined in sub-clause 10.4.1. + +--- + +**ALPHA** (4 bit field) + +For encoding and description see the Global Power Control Parameters IE. + +**ALPHA\_C1, ALPHA\_C2** (4 bit field) + +The usage of these fields is as specified in sub-clause 11.2.29.2. + +--- + +**GAMMA, GAMMA\_TN** (5 bit field) + +This field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +| | | +|-----------|-----------------------| +| bit | | +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | +| : : : : : | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | + +In the case of RTTI mode with BTTI USF, exactly one GAMMA field shall be included for each PDCH pair for which either one or two USF values are assigned. + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

USF_GRANULARITY (1 bit field)

This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation.

0 the mobile station shall transmit one RLC/MAC block
1 the mobile station shall transmit four consecutive RLC/MAC blocks

| +|

P0, P0_C1, P0_C2 (4 bit field)

For description and encoding, see the Packet Uplink Assignment message.

For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the P0 IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the P0 IE for the first carrier in the first UFPS shall apply.

| +|

PR_MODE, PR_MODE_C1, PR_MODE_C2 (1 bit field)

For description and encoding, see the Packet Uplink Assignment message.

For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the PR_MODE IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the PR_MODE IE for the first carrier in the first UFPS shall apply.

| +|

Packet Extended Timing Advance (2 bit field)

This field is defined in sub-clause 12.12b.

| +|

RB Id of downlink TBF (5 bit field)

RB Id of uplink TBF (5 bit field)

These fields are included when this message is used to reconfigure TBFs in Iu mode. These fields contain the radio bearer identifier for the radio bearer using the assigned TBF.

| +|

Uplink Control Timeslot (3 bit field)

Uplink Control Timeslot C1 (3 bit field)

Uplink Control Timeslot C2 (3 bit field)

For description and coding see the Packet Uplink Assignment message.

| +|

PFI of downlink TBF (7 bit field)

PFI of uplink TBF (7 bit field)

TFI (5 bit field)

This field contains the PFI parameter identifying a Packet Flow Context related to the TBF identified in the DOWNLINK_TFI_ASSIGNMENT field or UPLINK_TFI_ASSIGNMENT field respectively. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. If EMST is used, this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported, each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the uplink/downlink TBF and each PFI identifies a Packet Flow Context supported by a specific RLC entity on the uplink/downlink TBF.

| +|

UPLINK_RLC_MODE (1 bit field)

RLC_MODE (1 bit field)

This field contains the RLC mode to be used for the assigned TBF. If a new mode is assigned by the network for an already established TBF, the MS shall ignore the new assigned mode and shall maintain the TBF in the old mode. If EMST is used, this field indicates the RLC mode of the RLC entity.

0 RLC acknowledged mode
1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2).

| +|

Downlink NPM Transfer Time (5 bit field)

Uplink NPM Transfer Time (5 bit field)

NPM Transfer Time (5 bit field)

This field contains the NPM Transfer Time limitation in case a TBF or an RLC entity, if EMST is used, using RLC non-persistent mode is established with the message. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. Otherwise, this field, if present, shall be ignored

| + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Assignment Type (2 bit field)
This field is defined in sub-clause 11.2.7 | +| Carrier ID (1 bit field)
This identifies the carrier to which the description refers.

0 Carrier 1
1 Carrier 2 | +| EVENT_BASED_FANR (1 bit field)
This field indicates whether the event-based FANR shall be used for the assigned TBF. This field shall be included if the assignment is for a RTTI configuration.

0 The MS shall not use event-based FANR
1 The MS shall use event-based FANR | +| REPORTED TIMESLOTS, REPORTED TIMESLOTS C1, REPORTED TIMESLOTS C2 (8 bit field)
The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is encoded as the TIMESLOT_ALLOCATION IE defined in sub-clause 12.18.

If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then REPORTED TIMESLOTS C1 shall apply to the carrier specified in the Carrier ID field. Otherwise, REPORTED TIMESLOTS C1 and REPORTED TIMESLOTS C2 apply to carrier 1 and carrier 2 respectively. | +| DOWNLINK_PDCH_PAIRS_C1
DOWNLINK_PDCH_PAIRS_C2
DOWNLINK_PDCH_PAIRS_DLMC

These specify the set of timeslots which make up the downlink PDCH pairs on the respective carrier. The first PDCH pair comprises the two lowest-numbered timeslots for which the corresponding bits are set to '1'; the next PDCH pair comprises the next two lowest-numbered timeslots for which the corresponding bits are set to '1', and so on. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least two timeslots must be assigned.

If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then DOWNLINK_PDCH_PAIRS_C1 shall apply to the carrier specified in the Carrier ID field. Otherwise, DOWNLINK_PDCH_PAIRS_C1 and DOWNLINK_PDCH_PAIRS_C2 apply to carrier 1 and carrier 2 respectively. | +| UPLINK_PDCH_PAIRS_C1
UPLINK_PDCH_PAIRS_C2
UPLINK_PDCH_PAIRS_DLMC

These specify the set of timeslots which make up the uplink PDCH pairs on the respective carrier. The first PDCH pair comprises the two lowest-numbered timeslots for which the corresponding bits are set to '1'; the next PDCH pair comprises the next two lowest-numbered timeslots for which the corresponding bits are set to '1', and so on. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least two timeslots must be assigned.

If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then UPLINK_PDCH_PAIRS_C1 shall apply to the carrier specified in the Carrier ID field. Otherwise, UPLINK_PDCH_PAIRS_C1 and UPLINK_PDCH_PAIRS_C2 apply to carrier 1 and carrier 2 respectively. | + +##### **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_SC** (4 bit field) + +This specifies which of the downlink PDCH pairs are included in the single carrier assignment for the downlink TBF. If the bit number (5 - n) of the **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_SC** field is set to '1', then the *n*th downlink PDCH pair specified in the **DOWNLINK\_PDCH\_PAIRS\_C1** bitmap, or in the default configuration if so indicated in the message, is included in the downlink assignment (see sub-clause 7.1.3.6). + +#### **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_DC** (8 bit field) + +This specifies which of the downlink PDCH pairs are included in the dual carrier assignment for the downlink TBF. If the bit number (9 - n) of the **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_DC** field is set to '1', then the *n*th downlink PDCH pair specified in the **DOWNLINK\_PDCH\_PAIRS\_C1** or **DOWNLINK\_PDCH\_PAIRS\_C2** bitmap, or in the default configuration if so indicated in the message, is included in the downlink assignment (see sub-clause 7.1.3.6). + +#### **RTTI\_DOWNLINK\_PDCH\_PAIR\_ASSIGNMENT\_DLMC** (4 bit field) + +This specifies which of the downlink PDCH pairs are included in the corresponding carrier of the downlink TBF of a DLMC configuration. If the bit number (5 - n) of this field is set to '1', then the *n*th downlink PDCH pair specified in the **DOWNLINK\_PDCH\_PAIRS\_DLMC** bitmap is included in the downlink assignment. + +#### **USF, N\_USF, N\_TS, N\_PAIRS, USF\_2** + +These fields are specified and encoded as for the Packet Uplink Assignment message (see sub-clause 11.2.29 and Annex K). + +#### **RTTI\_USF\_MODE** (1 bit field) + +This field is as specified in the Packet Uplink Assignment message + +#### **TSH** (2 bit field) + +This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent: + +bit + +2 1 + +0 0 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI or MTI configuration) + +0 1 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI or MTI configuration) + +1 0 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI or MTI configuration) + +1 1 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI or MTI configuration) + +#### **Uplink EGPRS Level, Downlink EGPRS Level** (2 bits field) + +These fields assign the group of modulation and coding schemes applicable to the uplink and downlink TBFs respectively. This information element is defined in sub-clause 12.10f. + +#### **Pulse Format** (N bits field) + +This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in sub-clause 12.8.3. + +#### **Indication of Upper Layer PDU Start for RLC UM** (1 bit field) + +This field is defined in section 11.2.7. + +#### **Enhanced Flexible Timeslot Assignment** (1 bit field) + +This field is defined in sub-clause 11.2.29. + +#### **EMST\_NW\_Capability** (1 bit field) + +This information element is defined in sub-clause 11.2.29. + +#### **MTI\_UPLINK\_ASSIGNMENT\_C1** (1 bit field) + +#### **MTI\_UPLINK\_ASSIGNMENT\_C2** (1 bit field) + +These fields are defined in sub-clause 11.2.29 + +#### **MTI\_DOWNLINK\_ASSIGNMENT\_C1** (1 bit field) + +#### **MTI\_DOWNLINK\_ASSIGNMENT\_C2** (1 bit field) + +These fields are defined in sub-clause 11.2.7 + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------| +| EMSR Additional PFCs 1
EMSR Additional PFCs 2
EMSR Additional PFCs 3
These IEs are defined in section 11.2.7. | +| EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| UFPS
See sub-clause 11.2.7. | +| DLMC Measurement Type
See sub-clause 11.2.7. | +| Carrier for Interference Measurements (4 bit field)
See sub-clause 11.2.7. | +| CARRIER_SPECIFIC_INFO
See sub-clause 11.2.7. | +| DLMC Frequency Parameters
See sub-clause 11.2.7. | +| MAIO (6 bit field)
See sub-clause 11.2.7. | +| DLMC UL Carrier Info
See sub-clause 11.2.29. | +| Dynamic Allocation 3
See sub-clause 11.2.29. | +| PTCCH_CARRIER (4 bit field)
See sub-clause 11.2.7. | +| PDAN Coding (1 bit field)
See sub-clause 11.2.7. | +| DOWNLINK_eTFI_ASSIGNMENT (3 bit field)
See sub-clause 11.2.7. | +| Extended SNS (1 bit field)
See sub-clause 11.2.7. | +| Primary TSC Set (1 bit field)
See sub-clause 11.2.7 and 11.2.29. | +| Secondary DL TSC Set (1 bit field)
See sub-clause 11.2.7. | +| Secondary DL TSC Value (3 bit field)
See sub-clause 11.2.7. | + +#### 11.2.31.1 Special requirements in dual transfer mode + +Special requirements apply when a TBF is assigned to a mobile station in dual transfer mode or about to enter dual transfer mode, see sub-clauses 11.2.7.1 and 11.2.29.1 of the present document. + +### 11.2.31a Multiple TBF Timeslot Reconfigure + +This message is sent on the PACCH by the network to the mobile station to assign uplink and downlink resources. If the mobile station supports Downlink Dual Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a). A mobile allocation or reference frequency list received as part of this assignment message shall be valid until a new assignment is received or each TBF of the MS are terminated. + +Message type: MULTIPLE TBF TIMESLOT RECONFIGURE + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.31a.1: MULTIPLE TBF TIMESLOT RECONFIGURE information elements** + +``` + +< Multiple TBF Timeslot Reconfigure message content > ::= + < PAGE_MODE : bit (2) > + { 0 < GLOBAL_TFI : < Global TFI IE > > + { 0 -- Message escape for GPRS mode TBFs + { { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + < Global Packet Timing Advance : < Global Packet Timing Advance IE > > + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 1 < Multiple Downlink Assignment : < Multiple Downlink Assignment struct > > } ** 0 + < Multiple Uplink Assignment : < Multiple Uplink Assignment struct > > + < padding bits > + } ! < Non-distribution part error : bit (*) = < no string > > } + | 1 -- Message escape bit for EGPRS mode TBFs + { 00 { + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + < RESEGMENT : bit (1) > + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > } + { 0 | 1 { 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } } + < Global Packet Timing Advance : < Global Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 1 < Multiple Downlink Assignment : < Multiple Downlink Assignment struct > > } ** 0 + < Multiple Uplink Assignment : < Multiple Uplink Assignment struct > > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-7 + { 0 | 1 < NPM Transfer Time : bit (5) > } ** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + { < Indication of Upper Layer PDU Start for RLC UM : bit > } ** 0 + < Enhanced Flexible Timeslot Assignment : bit > + < padding bits > } } + } ! < Non-distribution part error : bit (*) = < no string > > } + | 01 { -- Message escape for dual carrier, BTTI with FANR activated, RTTI, EGPRS2 + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + < RESEGMENT : bit (1) > + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > } + { 0 | 1 { 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + } + < Global Packet Timing Advance : < Global Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 00 -- No frequency parameters included + | 01 -- Legacy IEs used + { 0 | 1 < Frequency Parameters C1 : < Frequency Parameters IE > > } + { 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE > > } + | 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE > > + ! < Frequency Parameters error: { 11 } bit(*) = < no string > > -- reserved for future use + } +} + +``` + +``` + + { 0 | 1 -- BTTI mode + < FANR: bit (1) > + { 1 < BTTI Multiple Downlink Assignment : < BTTI Multiple Downlink Assignment struct > > } ** 0 + } + { 0 | 1 -- RTTI mode + { 0 -- Single Carrier Assignment + { 00 -- Default PDCH-pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment SC : + < RTTI Multiple Downlink Assignment SC struct > > } ** 0 + } + { 1 -- Dual Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment DC : + < RTTI Multiple Downlink Assignment DC struct > > } ** 0 + } + } + } + { 0 | 1 -- BTTI and/or RTTI mode for uplink + < Multiple Uplink Assignment : < Multiple Uplink Assignment 2 struct > > + } + < Uplink EGPRS Level: < EGPRS Level IE > > + < Downlink EGPRS Level: < EGPRS Level IE > > + { 0 | 1 < Pulse Format: < Pulse Format IE > > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + { < Indication of Upper Layer PDU Start for RLC UM : bit > } ** 0 + < Enhanced Flexible Timeslot Assignment : bit > + < padding bits > } + } + ! < Non-distribution part error : bit (*) = < no string > > +} +! < Message escape : { 10 | 11 } bit (*) = < no string > > --Extended for future changes +} +! < Address information part error : bit (*) = < no string > > +} +! < Distribution part error : bit (*) = < no string > > ; + +< Multiple Downlink Assignment struct > ::= + < TIMESLOT_ALLOCATION : bit (8) > + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + { 1 < Downlink TBF assignment : < Downlink TBF assignment struct > > } ** 0 ; + +< BTTI Multiple Downlink Assignment struct > ::= + { 0 | 1 < TIMESLOT_ALLOCATION_C1 : bit (8) > } + { 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } + { 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } + { 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< RTTI Multiple Downlink Assignment SC struct > ::= + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > + { 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +``` + +``` + +< RTTI Multiple Downlink Assignment DC struct > ::= + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > + { 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } + { 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } + { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< Downlink TBF assignment struct > ::= + { 0 < RB Id : bit (5) > + | 1 < PFI : bit (7) > + < RLC_MODE : bit (1) > } + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + < TFI Assignment : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } ; + +< Downlink TBF assignment 2 struct > ::= + < PFI : bit (7) > + < RLC_MODE : bit (1) > + { 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } + { 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } + < TFI Assignment : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < EVENT_BASED_FANR : bit (1) > + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } ; + +< Multiple Uplink Assignment struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit(1) > } + { 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink TBF Assignment : < Uplink TBF Assignment struct > > } ** 0 } ; + +< Multiple Uplink Assignment 2 struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit(1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit(1) > } } + { 0 | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < TSH : bit (2) > } } + { 0 | 1 + { 0 | 1 -- BTTI mode + < Global Timeslot description : < Timeslot description 2 struct > > + } { 1 < Uplink TBF Assignment : < Uplink TBF Assignment 2 struct > > } ** 0 + } + { 0 | 1 -- RTTI mode + { 0 -- without power control parameters + | 1 -- with power control parameters + < ALPHA_C1 : bit (4) > + { 0 | 1 < ALPHA_C2 : bit (4) > } + < N_PAIRS : bit (3) > + { 0 | 1 < GAMMA : bit (5) > } * (val(N_PAIRS) + 1) + { 0 -- RTTI USF, or no second GAMMA values are given in case of RTTI mode with BTTI USF + | 1 -- Second GAMMA values are given in case of RTTI mode with BTTI USF + { 0 | 1 < GAMMA : bit (5) > } * (val(N_PAIRS) + 1) + } + } + { 1 < Uplink TBF Assignment : < Uplink TBF Assignment 2 struct > > + < RTTI_USF_MODE : bit (1) > } ** 0 + } +} ; + +``` + +``` + +< Timeslot description struct > ::= +{ 0 -- without power control params + < MS_TIMESLOT_ALLOCATION : bit (8) > +| 1 -- with power control params + < ALPHA : bit (4) > + { 0 | 1 < GAMMA_TN0 : bit (5) > } + { 0 | 1 < GAMMA_TN1 : bit (5) > } + { 0 | 1 < GAMMA_TN2 : bit (5) > } + { 0 | 1 < GAMMA_TN3 : bit (5) > } + { 0 | 1 < GAMMA_TN4 : bit (5) > } + { 0 | 1 < GAMMA_TN5 : bit (5) > } + { 0 | 1 < GAMMA_TN6 : bit (5) > } + { 0 | 1 < GAMMA_TN7 : bit (5) > } +}; + +< Timeslot description 2 struct > ::= +{ 0 -- without power control params + < MS_TIMESLOT_ALLOCATION_C1 : bit (8) > + { 0 | 1 < MS_TIMESLOT_ALLOCATION_C2 : bit (8) > } +| 1 -- with power control params + < ALPHA_C1 : bit (4) > + { 0 | 1 < GAMMA_TN0_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN1_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN2_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN3_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN4_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN5_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN6_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN7_C1 : bit (5) > } + { 0 | 1 < ALPHA_C2 : bit (4) > } + { 0 | 1 < GAMMA_TN0_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN1_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN2_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN3_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN4_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN5_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN6_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN7_C2 : bit (5) > } +}; + +< Uplink TBF Assignment struct > ::= -- Recursive for multiple TBFs +{ 0 < RB Id : bit (5) > +| 1 < PFI : bit (7) > } + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } + < USF_GRANULARITY : bit (1) > + { 0 -- The timeslots assigned to the TBF are all the timeslots assigned + -- in the Global Timeslot description + | 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > } -- The timeslots assigned to the TBF are a subset of all the + -- timeslots assigned in the Global Timeslot description. Where + -- N is the amount of timeslots assigned to the MS in the Global + -- Timeslot description + { 0 < USF_ALLOCATION : bit (3) > -- The same USF is valid on all timeslots assigned to the TBF + | 1 -- Different USF(s) assigned + < USF_ALLOCATION : bit (3) > -- USF assignment on the lowest numbered timeslot + -- assigned to the TBF + { 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) ; -- USFs on subsequent timeslots assigned to the TBF: + -- A '0' (respectively a '1' followed by a USF value) + -- means same (respectively different) USF value as the + -- USF on the next lower numbered timeslot assigned to + -- the TBF. Where M is the amount of timeslots assigned + -- to the TBF in the TBF_TIMESLOT_ALLOCATION if + -- present, else in the Global Timeslot description + +``` + +``` + +< Uplink TBF Assignment 2 struct > ::= -- Recursive for multiple TBFs + < PFI : bit (7) > + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 | 1 < REPORTED TIMESLOTS C1 : bit (8) > -- carrier 1 in Downlink Dual Carrier configuration + { 0 | 1 < REPORTED TIMESLOTS C2 : bit (8) > } -- carrier 2 in Downlink Dual Carrier configuration + } + < USF_GRANULARITY : bit (1) > + { 0 | 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > } -- The timeslots assigned to the TBF are all the timeslots + -- assigned in the Global Timeslot description + -- see description in Table 11.2.29a.2 + + { 0 < USF_ALLOCATION_C1 : bit (3) > + { 0 | 1 < USF_ALLOCATION_C2 : bit (3) > } -- The same USF is valid on all timeslots assigned to the TBF + -- on the respective carriers + | 1 -- Different USF(s) assigned; see description in Table 11.2.29a.2 + < USF_ALLOCATION : bit (3) > + { 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) } ; + +< Assignment Info struct > ::= + < Assignment Type : bit (2) > + < Carrier ID : bit (1) > ; + +``` + +**Table 11.2.31a.2: MULTIPLE TBF TIMESLOT RECONFIGURE information element details** + +| | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------|--|---|---|--|---|---|------|---|---|------|---|---|------|---|---|------| +| Global TFI
This information element identifies one of the mobile station's downlink or uplink TFIs. This field is defined in sub-clause 12.10. | | | | | | | | | | | | | | | | | | | +| CHANNEL_CODING_COMMAND (2 bit field)
The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting on the uplink. If this field is included in the main body of the message, it shall refer to all GPRS TBF mode uplink TBFs assigned in the message (default value). If this field is included in the Uplink TBF Assignment struct, it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every uplink TBF defined in GPRS TBF mode shall be assigned either the default value or a specific value.

bit
2 1
0 0 CS-1
0 1 CS-2
1 0 CS-3
1 1 CS-4
| bit | | | 2 | 1 | | 0 | 0 | CS-1 | 0 | 1 | CS-2 | 1 | 0 | CS-3 | 1 | 1 | CS-4 | +| bit | | | | | | | | | | | | | | | | | | | +| 2 | 1 | | | | | | | | | | | | | | | | | | +| 0 | 0 | CS-1 | | | | | | | | | | | | | | | | | +| 0 | 1 | CS-2 | | | | | | | | | | | | | | | | | +| 1 | 0 | CS-3 | | | | | | | | | | | | | | | | | +| 1 | 1 | CS-4 | | | | | | | | | | | | | | | | | +| EGPRS Modulation and Coding Scheme
The EGPRS modulation and coding scheme information element is defined in sub-clause 12.10d.

If this field is included in the main body of the message, it shall refer to all EGPRS TBF mode uplink TBFs assigned in the message (default value). If this field is included in the Uplink TBF Assignment struct, it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every uplink TBF defined in EGPRS TBF mode shall be assigned either the default value or a specific value.

If this field is included in a Dual Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on both carriers. | | | | | | | | | | | | | | | | | | | +| RESEGMENT (1 bit field)
This field is defined in sub-clause 12.10e. | | | | | | | | | | | | | | | | | | | + +#### **EGPRS Window Size** + +This information element is defined in sub-clause 12.5.2. + +If this field is included in the main body of the message, it shall refer to all TBFs assigned in the message in the direction indicated (default value). If this field is included in the respective TBF Assignment struct (uplink or downlink), it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every TBF defined in EGPRS TBF mode shall be assigned either the default value or a specific value. + +#### **LINK\_QUALITY\_MEASUREMENT\_MODE (2 bit field)** + +This field is encoded as the LINK\_QUALITY\_MEASUREMENT\_MODE IE of the PACKET DOWNLINK ASSIGNMENT message, as defined in sub-clause 11.2.7. + +#### **Global Packet Timing Advance** + +This information element is defined in sub-clause 12.12a. + +#### **CONTROL\_ACK (1 bit field)** + +This field shall be set to "1" if the network wishes to instruct the mobile station to release the given TBFs for which T3192 is running. The TBFs to be released are identified by the TFIs given in the TFI Assignment field and have to be valid on the PACCH on which this message was sent. Otherwise this field shall be set to "0". + +#### **TFI Assignment (5 bit field)** + +This information element assigns one (or more) TFI(s) to each TBF assigned to the mobile station in this message. This field is repeated for each TBF that is assigned in this message. Optionally, this field may be repeated for each timeslot on which the TBF has been assigned resources. This is in order to assign different TFI values for the same TBF on different resources (BPSCH). TFI values are encoded as defined in sub-clause 12.15. + +#### **RB Id (5 bit field)** + +This field contains the radio bearer identifier for the radio bearer using the assigned TBF. This provides the mapping of TFI to RB Id which is necessary to uniquely identify Iu-mode data flows. + +#### **Uplink Control Timeslot (3 bit field)** + +In case of a BTTI configuration, this field contains the timeslot number of the timeslot where the PACCH/U for the MS is located. In case of an RTTI configuration, this field contains the timeslot number of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +If this field is included in the Multiple Downlink Assignment struct, it shall refer to all downlink TBFs assigned in the message. If this field is included in the Downlink TBF assignment struct, it refers only to the TBF given by the TFI Assignment field (this specific value overrules any default value given in the Multiple Downlink Assignment struct). If the Uplink Control Timeslot field is not included in the message at all, then the default rules for the location of PACCH/U apply. + +#### **Uplink Control Timeslot C1 (3 bit field)** + +In case of a BTTI configuration, this field, if present, contains the timeslot number on carrier1 of the timeslot where the PACCH/U for the MS is located. In case of an RTTI configuration, this field contains the timeslot number on carrier1 of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +#### **Uplink Control Timeslot C2 (3 bit field)** + +In case of a BTTI configuration, this field, if present, contains the timeslot number on carrier2 of the timeslot where the PACCH/U for the MS is located. In case of an RTTI configuration, this field contains the timeslot number on carrier2 of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +If the Uplink Control Timeslot C1 and/or the Uplink Control Timeslot C2 fields are included in the BTTI Multiple Downlink Assignment struct (respectively RTTI Multiple Downlink Assignment SC / DC struct), they shall refer to all downlink TBFs assigned in the message. If these fields are included in the Downlink TBF assignment 2 struct, they refer only to the TBF given by the TFI Assignment field (the specific values overrule any default values given in the BTTI Multiple Downlink Assignment struct (respectively RTTI Multiple Downlink Assignment SC / DC struct)). If the Uplink Control Timeslot field is not included in the message at all, then the default rules for the location of PACCH/U apply. + +#### **TIMESLOT\_ALLOCATION (8 bit field)** + +This field is defined in sub-clause 12.18. + +#### **TIMESLOT\_ALLOCATION\_C1, TIMESLOT\_ALLOCATION\_C2 (8 bit field)** + +These information fields indicate the timeslots assigned for use during the TBF on carrier 1 and carrier 2 respectively of a dual carrier configuration. These fields are defined in sub-clause 12.18. + +#### **Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink and downlink TBFs. If this information element is not present the mobile station shall use its previously assigned frequency parameters. This information element is defined in sub-clause 12.8. + +##### **Frequency Parameters C1, Frequency Parameters C2** + +These information elements are coded as defined in sub-clause 12.8. The usage of these parameters is specified in sub-clause 11.2.7. + +##### **Dual Carrier Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink TBF for both carriers in a dual carrier configuration. This information element is defined in sub-clause 12.8.2. + +#### **EXTENDED\_DYNAMIC\_ALLOCATION (1 bit field)** + +This information field indicates the medium access mode to be used during the TBF. + +- 0 Dynamic Allocation +- 1 Extended Dynamic Allocation + +##### **TBF Starting Time** + +The TBF Starting Time field contains a starting time that indicates the frame number during which the assigned TBF may start. + +If no downlink TBF is in progress, the mobile station need not monitor the TFI field of downlink RLC data blocks until the indicated TDMA frame number. After the indicated TDMA frame number, the mobile station shall apply the new downlink parameters and then operate as during a downlink TBF. If a downlink TBF is already in progress, the mobile station shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to use the new downlink parameters assigned. + +In case of dynamic allocation, if no uplink TBF is in progress, the MS need not monitor the USF field until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. If an uplink TBF is already in progress, the MS shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. + +This field is encoded as the Starting Frame Number Description IE. See sub-clause 12.21 + +#### **MS\_TIMESLOT\_ALLOCATION** (8 bit field) + +This information field indicates the timeslots assigned for use by the MS for the assigned uplink TBFs. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least one timeslot must be assigned. + +- 0 Timeslot is not assigned +- 1 Timeslot is assigned + +#### **MS\_TIMESLOT\_ALLOCATION\_C1, MS\_TIMESLOT\_ALLOCATION\_C2** (8 bit field) + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then the MS\_TIMESLOT\_ALLOCATION\_C1 field shall apply to the carrier specified in the Carrier ID field. Otherwise, MS\_TIMESLOT\_ALLOCATION\_C1 and MS\_TIMESLOT\_ALLOCATION\_C2 apply to carrier 1 and carrier 2 respectively. These information fields indicate the timeslots assigned for use by the MS for the assigned uplink TBFs. + +Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. If the Assignment Type field is included and indicates 'Dual Carrier assignment' and MS\_TIMESLOT\_ALLOCATION\_C1 is present and MS\_TIMESLOT\_ALLOCATION\_C2 is not present, then the timeslots specified in MS\_TIMESLOT\_ALLOCATION\_C1 apply also to carrier 2. + +#### **TBF\_TIMESLOT\_ALLOCATION** (N bit field) + +This information field indicates the timeslots assigned to a particular uplink TBF, within the timeslots assigned to the MS in the Global Timeslot description. This field contains as many bits as there are timeslots assigned to the MS in the Global Timeslot description. Bit N indicates the status of the lowest numbered timeslot in the timeslots assigned to the MS in the Global Timeslot description. Bit N-1 (if any) indicates the status of the next lowest numbered timeslot, etc. At least one timeslot must be assigned per TBF + +In the case of a dual carrier configuration, the timeslots indicated in the MS\_TIMESLOT\_ALLOCATION\_C1 field shall be considered as lower numbered than those in the MS\_TIMESLOT\_ALLOCATION\_C2 field. + +- 0 Timeslot is not assigned +- 1 Timeslot is assigned + +#### **USF\_ALLOCATION** (3 bit field) + +This field indicates the USF value assigned to the MS for one or more assigned timeslots. This field is encoded as a binary presentation of the USF value as defined in sub-clause 10.4.1. + +##### **USF\_ALLOCATION\_C1, USF\_ALLOCATION\_C2** (3 bit field) + +For description and encoding, see the Multiple TBF Uplink Assignment message. + +#### **USF\_GRANULARITY** (1 bit field) + +This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation. + +- 0 the mobile station shall transmit one RLC/MAC block +- 1 the mobile station shall transmit four consecutive RLC/MAC blocks + +#### **ALPHA** (4 bit field) + +For encoding and description see the Global Power Control Parameters IE. + +#### **ALPHA\_C1, ALPHA\_C2** (4 bit field) + +The usage of these fields is as specified in sub-clause 11.2.29. + +#### **N\_PAIRS** (3 bit field) + +This field indicate the number of PDCH pairs for which GAMMA values are signalled. The number PDCH pairs is given as the binary value of the corresponding field plus one. + +See Annex K for details of the coding of this field. + +| | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------|-----------|--------------------|---------|--|-----------|---------------------|-----------|---------------------| +|

GAMMA, GAMMA_TN (5 bit field)

The field is the binary representation of the parameter \GammaCH for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table:

bit
5 4 3 2 1

0 0 0 0 0 \GammaCH = 0 dB
0 0 0 0 1 \GammaCH = 2 dB
: : : :
1 1 1 1 0 \GammaCH = 60 dB
1 1 1 1 1 \GammaCH = 62 dB

GAMMA_TN_C1 (5 bit field)
GAMMA_TN_C2 (5 bit field)
The coding and usage of these fields is as specified for the Packet Uplink Assignment message.

| 0 0 0 0 0 | $\Gamma$ CH = 0 dB | 0 0 0 0 1 | $\Gamma$ CH = 2 dB | : : : : | | 1 1 1 1 0 | $\Gamma$ CH = 60 dB | 1 1 1 1 1 | $\Gamma$ CH = 62 dB | +| 0 0 0 0 0 | $\Gamma$ CH = 0 dB | | | | | | | | | | +| 0 0 0 0 1 | $\Gamma$ CH = 2 dB | | | | | | | | | | +| : : : : | | | | | | | | | | | +| 1 1 1 1 0 | $\Gamma$ CH = 60 dB | | | | | | | | | | +| 1 1 1 1 1 | $\Gamma$ CH = 62 dB | | | | | | | | | | +|

P0, P0_C1, P0_C2 (4 bit field)
For description and encoding, see the Packet Uplink Assignment message.

| | | | | | | | | | | +|

PR_MODE, PR_MODE_C1, PR_MODE_C2 (1 bit field)
For description and encoding, see the Packet Uplink Assignment message.

| | | | | | | | | | | +|

Packet Extended Timing Advance (2 bit field)
This field is defined in sub-clause 12.12b.

| | | | | | | | | | | +|

PFI (7 bit field)

This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018.

| | | | | | | | | | | +|

RLC_MODE (1 bit field)

This field contains the RLC mode to be used for the assigned TBF. If a new mode is assigned by the network for an already established TBF, the MS shall ignore the new assigned mode and shall maintain the TBF in the old mode.

0 RLC acknowledged mode
1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2).

| | | | | | | | | | | +|

NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode

The list of NPM Transfer Time IEs in the Rel-7 additions is ordered as described by the loops in the earlier releases part.

| | | | | | | | | | | +|

Assignment Type (2 bit field)
This indicates the type of assignment. The coding of this field is as specified in sub-clause 11.2.7.

| | | | | | | | | | | +|

Carrier ID (1 bit field)
This identifies the carrier to which the description refers.

0 Carrier 1
1 Carrier 2

| | | | | | | | | | | +|

EVENT_BASED_FANR (1 bit field)
For description and coding of this field see the Multiple TBF Downlink Assignment message.

The list of EVENT_BASED_FANR IEs in the Rel-7 additions is ordered as described by the loops in the earlier releases part.

| | | | | | | | | | | +|

REPORTED TIMESLOTS C1, REPORTED TIMESLOTS C2 (8 bit field)
The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is encoded as the TIMESLOT_ALLOCATION IE defined in sub-clause 12.18.
The list of fields related to the Fast Ack/Nack Reporting procedure in the Rel-7 additions is ordered as described by the loops in the earlier releases part.

| | | | | | | | | | | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DOWNLINK_PDCH_PAIRS_C1
DOWNLINK_PDCH_PAIRS_C2
UPLINK_PDCH_PAIRS_C1
UPLINK_PDCH_PAIRS_C2
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC

These fields are defined in sub-clause 11.2.31 | +| RTTI_USF_MODE (1 bit field)
This field is as specified in the Packet Uplink Assignment message | +| TSH (2 bit field)
This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent:

bit
2 1
0 0   4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI configuration)
0 1   8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI configuration)
1 0   12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI configuration)
1 1   16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI configuration) | +| Uplink EGPRS Level, Downlink EGPRS Level (2 bits field)
These fields are as specified in the Packet Timeslot Reconfigure message. | +| Pulse Format (N bits field)
This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in sub-clause 12.8.3. | +| FANR (1 bit field)
This field indicates whether FANR is activated:

0   FANR is activated for the assigned TBFs
1   FANR is not activated for the assigned TBFs | +| Indication of Upper Layer PDU Start for RLC UM (1 bit field)
This field is defined in section 11.2.7. | +| Enhanced Flexible Timeslot Assignment (1 bit field)
This field is defined in sub-clause 11.2.29a. | + +### 11.2.32 Additional MS Radio Access Capabilities + +This message is sent on the PACCH by the mobile station to the network to inform about radio access capabilities of the mobile station. It shall not be used in *Iu mode*. + +Message type: Additional MS Radio Access Capabilities + +Direction: mobile station to network + +**Table 11.2.32.1: ADDITIONAL MS RADIO ACCESS CAPABILITIES information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < Additional MS Radio Access Capabilities message content > ::=
{ 0 < Global TFI : < Global TFI IE > >
1 < TLLI : < TLLI IE > > }
< MS Radio Access Capability 2 : < MS Radio Access Capability 2 IE > >
{ null 0 bit ** = < no string > -- Receiver compatible with earlier release
1 -- Additions in Rel-12
{ 0 1 < Downlink_eTFI : bit (3) > }
< padding bits > } ; | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.32.2: ADDITIONAL MS RADIO ACCESS CAPABILITIES information element details** + +#### **Global TFI** + +This information element contains the TFI of the mobile station's uplink TBF, if available, or the TFI of the mobile station's downlink TBF. If no TFI is available, this field is omitted. This field is defined in sub-clause 12.10. + +#### **TLLI IE (32 bit field)** + +This information element is defined in sub-clause 12.16. + +#### **MS Radio Access Capability 2** + +This information element is defined in sub-clause 12.30. This information element is sent during one phase and two phase access procedures. + +#### **DOWNLINK\_eTFI (3 bit field)** + +See sub-clause 11.2.48 + +### **11.2.33 Handover Access (*Iu mode only*)** + +This message is sent on DBPSCH on either PACCH, FACCH or SDCCH and optionally on SACCH by the mobile station to the network during a handover procedure. It shall not be sent on the 52-multiframe structure (SBPSCH). This message is formatted as four identical access bursts on PACCH, FACCH and SDCCH, and as one individual access burst on SACCH. Each access burst shall use the 8-bit access burst format and follow the 8-bit PRACH uplink/PACCH uplink short acknowledgement block format defined in 3GPP TS 44.004. Each access burst is coded as shown in table 11.2.33.1. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. + +Direction: mobile station to network + +**Table 11.2.33.1: HANDOVER ACCESS information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------| +| < Handover Access 8 bit message > ::=      -- 8-bit access burst format
< HANDOVER_REFERENCE_VALUE : bit (8) > ; | +|---------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.33.2: HANDOVER ACCESS information element details** + +#### **HANDOVER\_REFERENCE\_VALUE (8 bit field)** + +This field is coded as the handover reference value field defined in 3GPP TS 44.018. + +### **11.2.34 Physical Information (*Iu mode only*)** + +This message is sent on DBPSCH on either PACCH, FACCH or SDCCH by the network to the mobile station during a handover procedure to indicate a valid timing advance to the mobile station. It shall not be sent on the 52-multiframe structure (SBPSCH). + +Message type: PHYSICAL INFORMATION + +Direction: network to mobile station + +Classification: DBPSCH message + +**Table 11.2.34.1: PHYSICAL INFORMATION information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < Physical information message content > ::=      -- RLC/MAC control block format
< MESSAGE_TYPE : bit (6) == 010010 >
< TIMING_ADVANCE_VALUE : bit (8) >
< padding bits > ;                                      -- truncation at end of message allowed, bits '0' assumed | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.34.2: PHYSICAL INFORMATION information element details** + +#### **TIMING\_ADVANCE\_VALUE** (8 bit field) + +This field is coded as the timing advance value field defined in 3GPP TS 44.018. + +### 11.2.35 Packet CS Request + +This message is sent from the mobile station to the network on the PACCH to request RR connection. + +Message type: PACKET CS REQUEST + +Direction: mobile station to network + +**Table 11.2.35.1: PACKET CS REQUEST information elements** + +``` +< Packet CS Request message content > ::= + < GLOBAL_TFI : < Global TFI IE > > + < ESTABLISHMENT CAUSE : bit (8) > + < padding bits > ; +``` + +**Table 11.2.35.2: PACKET CS REQUEST information element details** + +#### **Global TFI** + +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +#### **ESTABLISHMENT CAUSE** (8 bit field) + +The ESTABLISHMENT CAUSE field indicates the cause value of the RR connection establishment. This field is specified in 3GPP TS 44.018. The mobile station shall neither use cause values referring to answer to paging nor request of PDCH. + +### 11.2.36 Packet CS Command + +This optional message is sent by the network on the PACCH to encapsulate RR control messages. This message may be segmented across more than two RLC/MAC control block by using extended RLC/MAC control message segmentation. + +Message type: PACKET CS COMMAND + +Direction: network to mobile station + +Classification: non distribution message + +**Table 11.2.36.1: Packet CS Command information elements** + +``` +< Packet CS Command message content > ::= + < PAGE_MODE : bit (2) > + { < GLOBAL_TFI : < Global TFI IE > > + { < spare : bit (2) > + < CONTAINER_LENGTH : bit (8) > + < CONTAINER_DATA : octet ** > + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.36.2: Packet CS Command information element details** + +The Packet CS Command message encapsulates RR control message (e.g. DTM ASSIGNMENT COMMAND, IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT REJECT). + +| | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--|-----------------|--|-----------------|-----------------------------------------------------------------------------------|-----------------|----------------------------------|------|--|-----------------|-------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20 and gives the PAGE_MODE parameter valid in the serving cell.

| | | | | | | | | | | | | +|

Global_TFI
This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10.

| | | | | | | | | | | | | +|

CONTAINER_LENGTH (8 bit field)
This field indicates the number of CONTAINER_DATA octets that form the specific RR control message and is coded as shown below.

Bit
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 No CONTAINER_DATA follows; Spare padding is used to fill the rest of the message;
0 0 0 0 0 0 0 1 CONTAINER_DATA length = 1 octet;
....
1 0 1 0 1 0 0 0 CONTAINER_DATA length = 168 octets;

All other values reserved. If a reserved value is received the contents of the container shall be discarded.

| Bit | | 8 7 6 5 4 3 2 1 | | 0 0 0 0 0 0 0 0 | No CONTAINER_DATA follows; Spare padding is used to fill the rest of the message; | 0 0 0 0 0 0 0 1 | CONTAINER_DATA length = 1 octet; | .... | | 1 0 1 0 1 0 0 0 | CONTAINER_DATA length = 168 octets; | +| Bit | | | | | | | | | | | | | +| 8 7 6 5 4 3 2 1 | | | | | | | | | | | | | +| 0 0 0 0 0 0 0 0 | No CONTAINER_DATA follows; Spare padding is used to fill the rest of the message; | | | | | | | | | | | | +| 0 0 0 0 0 0 0 1 | CONTAINER_DATA length = 1 octet; | | | | | | | | | | | | +| .... | | | | | | | | | | | | | +| 1 0 1 0 1 0 0 0 | CONTAINER_DATA length = 168 octets; | | | | | | | | | | | | +|

CONTAINER DATA (n*8 bits)
The CONTAINER DATA octets forms the actual RR control message content. The information contained in the Packet CS Command message shall exclude the following information elements from the beginning of the RR control message: L2 Pseudo Length; RR management Protocol Discriminator and Skip Indicator.

Extra octets of padding bits at the end of the RR control message may be excluded.

| | | | | | | | | | | | | + +### 11.2.37 Packet CS Release Indication + +This message is sent from the network to the mobile station on the PACCH to indicate that the ongoing RR connection will be released. The network may indicate that the mobile station shall maintain its uplink and downlink packet resources used in dual transfer mode or it may convert half-rate PDCH into full-rate PDCH to be used in packet transfer mode or it may reconfigure uplink and/or downlink packet resources to be used in packet transfer mode after the RR connection is released.. If the mobile station supports Downlink Dual Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a) if three or more RLC/MAC control blocks are required to send the complete message. A mobile allocation or reference frequency list received as part of this assignment message shall be valid until a new assignment is received or each TBF of the MS are terminated. + +With reconfiguration option the network shall assign at least one uplink or downlink TBF. + +**Message type:** PACKET CS RELEASE INDICATION + +**Direction:** network to mobile station + +**Classification:** non-distribution message + +Table 11.2.37.1: PACKET CS RELEASE INDICATION information elements + +``` + +< Packet CS Release message content > ::= + < PAGE_MODE : bit (2) > + { + < GLOBAL_TFI : < Global TFI IE > > + < ENHANCED_DTM_CS_RELEASE_INDICATION : bit > + < Global Packet Timing Advance : < Global Packet Timing Advance IE > > + { 00 -- RR connection is released and the MS maintains its DL and/or UL TBF(s) + < padding bits > -- Allows future message extension for '00' choice. + } 01 -- When RR connection is released, PDTCH/H is converted to PDTCH/F + -- and the MS maintains its DL and/or UL TBF(s) + < padding bits > -- Allows future message extension for '01' choice. + } 10 -- RR connection is released and DL and/or UL TBF(s) are reconfigured + { 0 -- Message escape for GPRS mode TBFs + { { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 -- downlink TBF(s) + { 1 < Multiple Downlink Assignment : < Multiple Downlink Assignment struct > > } ** 0 + } + } 0 | 1 -- uplink TBF(s) + { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + < Multiple Uplink Assignment : < Multiple Uplink Assignment struct > > + } + } null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + < padding bits > } + ! < Non-distribution part error : bit (*) > = < no string > > } + | 1 -- Message escape bit for EGPRS mode TBFs + { 00 { + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + { 0 | 1 -- downlink TBF(s) + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 1 < Multiple Downlink Assignment : + < Multiple Downlink Assignment struct > > } ** 0 + } + } +} + +``` + +``` + +{ 0 | 1 -- uplink TBF(s) + { 0 | 1 < EGPRS Channel Coding Command : + < EGPRS Modulation and Coding Scheme IE > > } + < RESEGMENT : bit (1) > + { 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } + < Multiple Uplink Assignment : < Multiple Uplink Assignment struct > > +} +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 -- Additions for Rel-7 + { 1 { 0 | 1 < NPM Transfer Time : bit (5) > } }** 0 + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-9 + < Enhanced Flexible Timeslot Assignment : bit > + { 0 -- EMST is not used in DL + | 1 -- EMST is used in DL + < Downlink RLC Entity 2 : < RLC Entity struct > + { 0 + | 1 < Downlink RLC Entity 3 : < RLC Entity struct > } + } + { 0 -- EMST is not used in UL + | 1 -- EMST is used in UL + < Uplink RLC Entity 2 : < RLC Entity struct > + { 0 + | 1 < Uplink RLC Entity 3 : < RLC Entity struct > } + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-10 + { 0 -- EMSR is not enabled in downlink + | 1 -- EMSR is enabled in downlink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + { 0 -- EMSR is not enabled in uplink + | 1 -- EMSR is enabled in uplink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + < padding bits > } } } } +! < Non-distribution part error : bit (*) = < no string > > +} +| 01 -- Message escape for Dual Carrier, BTTI with FANR activated, RTTI, EGPRS2 +{ + < Assignment Info : Assignment Info struct > + { 00 -- No frequency parameters included + | 01 -- Legacy IEs used + < Frequency Parameters C1 : < Frequency Parameters IE > > + { 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE > > } + | 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE > > + ! < Frequency parameters error: { 11 } bit (*) = > -- Reserved for future use + } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + < EGPRS mode : < EGPRS mode 2 IE > > +} + +``` + +``` + +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 + -- Additions for Rel-9 + < Enhanced Flexible Timeslot Assignment : bit > + { 0 -- EMST is not used in DL + | 1 < Downlink RLC Entity 2 : < RLC Entity struct > -- EMST is used in DL + { 0 + | 1 < Downlink RLC Entity 3 : < RLC Entity struct > } + } + { 0 -- EMST is not used in UL + | 1 < Uplink RLC Entity 2 : < RLC Entity struct > -- EMST is used in UL + { 0 + | 1 < Uplink RLC Entity 3 : < RLC Entity struct > } + } +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 + -- Additions for Rel-10 + { 0 -- EMSR is not enabled in downlink + | 1 -- EMSR is enabled in downlink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + { 0 -- EMSR is not enabled in uplink + | 1 -- EMSR is enabled in uplink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } +{ null | 0 bit** = < no string > -- Receiver backward compatible with earlier version +| 1 + -- Additions for Rel-11 + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 + -- Additions for Rel-12 + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + < padding bits > } } } } + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Message escape : { 10 | 11 } bit (*) = < no string > > } -- Extended for future changes + } +| 11 -- Reserved for future use. When received it shall be interpreted as "00". + < padding bits > -- Allows future message extension for '11' choice. +} +! < Address information part error : bit (*) = < no string > > } +! < Distribution part error : bit (*) = < no string > > ; + +< Multiple Downlink Assignment struct > ::= + < TIMESLOT_ALLOCATION : bit (8) > + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + { 1 < Downlink TBF assignment : < Downlink TBF assignment struct > > } ** 0 ; + +< Downlink TBF assignment struct > ::= + { 0 | 1 < PFI : bit (7) > } + < DOWNLINK_RLC_MODE : bit (1) > + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + < TFI_ASSIGNMENT : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } ; + +< Multiple Uplink Assignment struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit(1) > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink TBF Assignment : < Uplink TBF Assignment struct > > } ** 0 } ; + +``` + +``` + +< Timeslot description struct > ::= +{ 0 -- without power control params + < MS_TIMESLOT_ALLOCATION : bit (8) > +| 1 -- with power control params + < ALPHA : bit (4) > + { 0 | 1 < GAMMA_TN0 : bit (5) > } + { 0 | 1 < GAMMA_TN1 : bit (5) > } + { 0 | 1 < GAMMA_TN2 : bit (5) > } + { 0 | 1 < GAMMA_TN3 : bit (5) > } + { 0 | 1 < GAMMA_TN4 : bit (5) > } + { 0 | 1 < GAMMA_TN5 : bit (5) > } + { 0 | 1 < GAMMA_TN6 : bit (5) > } + { 0 | 1 < GAMMA_TN7 : bit (5) > } ; + +< Uplink TBF Assignment struct > ::= -- Recursive for multiple TBFs +{ 0 | 1 < PFI : bit (7) > } +< TFI_ASSIGNMENT : bit (5) > +{ 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } +{ 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } +{ 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } +< USF_GRANULARITY : bit (1) > +{ 0 -- The timeslots assigned to the TBF are all the timeslots assigned + -- in the Global Timeslot description +| 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > -- The timeslots assigned to the TBF are a subset of all the + -- timeslots assigned in the Global Timeslot description. Where + -- N is the amount of timeslots assigned to the MS in the Global + -- Timeslot description +{ 0 < USF_ALLOCATION : bit (3) > -- The same USF is valid on all timeslots assigned to the TBF +| 1 < USF_ALLOCATION : bit (3) > -- Different USF(s) assigned + -- USF assignment on the lowest numbered timeslot + -- assigned to the TBF +{ 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) ; -- USFs on subsequent timeslots assigned to the TBF: + -- A '0' (respectively a '1' followed by a USF value) + -- means same (respectively different) USF value as the + -- USF on the next lower numbered timeslot assigned to + -- the TBF. Where M is the amount of timeslots assigned + -- to the TBF in the TBF_TIMESLOT_ALLOCATION if + -- present, else in the Global Timeslot description + +< Assignment Info struct > ::= +< Assignment Type : bit (2) > +< Carrier ID : bit (1) > ; + +< RLC Entity struct > ::= +< TFI_ASSIGNMENT : bit (5) > +< RLC_MODE : bit (1) > +{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } +PFI : bit (7) > ; + +< Additional PFCs struct > ::= +< TFI_ASSIGNMENT : bit (5) > +{ 0 | 1 < NPM Transfer Time : bit (5) > } +< PFI : bit (7) > ; + +``` + +Table 11.2.37.2: PACKET CS RELEASE INDICATION information element details + +#### **PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +#### **Global\_TFI** + +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +#### **ENHANCED\_DTM\_CS\_RELEASE\_INDICATION** (1 bit field) + +The ENHANCED\_DTM\_CS\_RELEASE\_INDICATION parameter indicates that the network will perform a delayed release of the RR connection while the mobile station is in dual transfer mode. + +- | | | +|---|------------------------------------------| +| 0 | The RR connection is not to be released. | +| 1 | The RR connection is to be released. | + +NOTE: The network should not use value "0" if the PACKET CS RELEASE INDICATION message is used with enhanced DTM CS release procedure. In this case the mobile station shall ignore the message. + +#### **Global Packet Timing Advance** + +This information element is defined in sub-clause 12.12a. + +#### **CHANNEL\_CODING\_COMMAND** (2 bit field) + +The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting on the uplink. + +- | | | +|-----|------| +| bit | | +| 2 1 | | +| 0 0 | CS-1 | +| 0 1 | CS-2 | +| 1 0 | CS-3 | +| 1 1 | CS-4 | + +#### **Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink and downlink TBFs. If this information element is not present the mobile station shall use its previously assigned frequency parameters. This information element is defined in sub-clause 12.8. + +##### **Frequency Parameters C1, Frequency Parameters C2** + +These information elements assign frequency parameters to the uplink and/or downlink TBFs for carrier 1 and carrier 2, respectively. If the Frequency Parameters C1 information element is not present the mobile station shall use its previously assigned frequency parameters for carrier 1. These information elements are coded as defined in sub-clause 12.8. + +##### **Dual Carrier Frequency Parameters** + +This information element, if present, assigns frequency parameters to the uplink and/or downlink TBFs for both carriers in a dual carrier configuration. This information element is defined in sub-clause 12.8.2. + +#### **Packet Extended Timing Advance** (2 bit field) + +This field is defined in sub-clause 12.12b. + +#### **TIMESLOT\_ALLOCATION** (8 bit field) + +This field is defined in sub-clause 12.18. + +#### **Uplink Control Timeslot** (3 bit field) + +In case of a BTTI configuration, this field contains the timeslot number of the timeslot where the PACCH/U for the downlink TBF is located. In case of an RTTI configuration, this field contains the timeslot number of the timeslot belonging to the uplink PDCH pair where the PACCH/U for the downlink TBF is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. + +If this field is included in the Multiple Downlink Assignment struct, it shall refer to all downlink TBFs assigned in the message. If this field is included in the Downlink TBF assignment struct, it refers only to the TBF given by the TFI Assignment field (this specific value overrules any default value given in the Multiple Downlink Assignment struct). If the Uplink Control Timeslot field is not included in the message at all, then the default rules for the location of PACCH/U apply. + +#### **PFI** (7 bit field) + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. This field shall be included if and only if both the network and mobile station support multiple TBFs. If EMST is used, this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported, this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity on the uplink/downlink TBF. + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

DOWNLINK_RLC_MODE (1 bit field)
RLC_MODE (1 bit field)
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message).

| +|

TFI_ASSIGNMENT (5 bit field)
This information element assigns one (or more) TFI(s) to each TBF assigned to the mobile station in this message. This field is repeated for each TBF that is assigned in this message. Optionally, this field may be repeated for each timeslot on which the TBF has been assigned resources. TFI values are encoded as defined in sub-clause 12.15. If EMST is used, each TFI identifies an RLC entity allocated on the TBF. If EMSR is supported, each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the uplink/downlink TBF.

| +|

CONTROL_ACK (1 bit field)
If multiple TBFs are supported by both network and mobile station, this field shall be set to "1" if the network wishes to instruct the mobile station to release the given TBFs for which T3192 is running. The TBFs to be released are identified by the TFIs given in the TFI Assignment field and have to be valid on the PACCH on which this message was sent. Otherwise this field shall be set to "0".
If either the network or the mobile station does not support the multiple TBF feature, this field shall be set to '1' if the network establishes a new downlink TBF for the mobile station whose timer T3192 is running. Otherwise this field shall be set to '0'.

| +|

EGPRS Window Size IE (Uplink EGPRS Window Size, Downlink EGPRS Window Size)
This information element is defined in sub-clause 12.5.2.

If this field is included in the main body of the message, it shall refer to all TBFs assigned in the message in the direction indicated (default value). If this field is included in the respective TBF Assignment struct (uplink or downlink), it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every TBF defined in EGPRS TBF mode shall be assigned either the default value or a specific value.

If this field is included in a Dual Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on both carriers.

| +|

EGPRS Modulation and Coding Scheme IE (EGPRS Channel Coding Command)
The EGPRS modulation and coding scheme information element is defined in sub-clause 12.10d.

If this field is included in the main body of the message, it shall refer to all EGPRS TBF mode uplink TBFs assigned in the message (default value). If this field is included in the Uplink TBF Assignment struct, it refers only to the TBF given by the TFI Assignment (this specific value overrules the default value). Every uplink TBF defined in EGPRS TBF mode shall be assigned either the default value or a specific value.

| +|

RESEGMENT (1 bit field)
This field is defined in sub-clause 12.10e.

| +|

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)
This field is encoded as the LINK_QUALITY_MEASUREMENT_MODE IE of the PACKET DOWNLINK ASSIGNMENT message, as defined in sub-clause 11.2.7.

| +|

BEP_PERIOD2 (4 bit field)
This field contains a constant which is used for filtering channel quality measurements in EGPRS. BEP_PERIOD2 when present, or if not, when received in a previous message of the same TBF session, shall be used instead of BEP_PERIOD. For details see 3GPP TS 45.008.
Range: 0 to 15

| +|

EXTENDED_DYNAMIC_ALLOCATION (1 bit field)
This information field indicates the medium access mode to be used during the TBF.

0 Dynamic Allocation
1 Extended Dynamic Allocation

| +|

P0 (4 bit field)
For description and encoding, see the Packet Uplink Assignment message. .

| +|

PR_MODE (1 bit field)
For description and encoding, see the Packet Uplink Assignment message.

| +|

MS_TIMESLOT_ALLOCATION (8 bit field)
This information field indicates the timeslots assigned for use by the MS for the assigned uplink TBFs. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least one timeslot must be assigned.

0 Timeslot is not assigned
1 Timeslot is assigned

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

ALPHA (4 bit field)
For encoding and description see the Global Power Control Parameters IE.

The usage of these fields is as specified in sub-clause 11.2.29.

| | | | | | | | | | | +|

GAMMA_TN (5 bit field)
The field is the binary representation of the parameter \Gamma_{CH} for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table:

bit
5 4 3 2 1

0 0 0 0 0 \Gamma_{CH} = 0 dB
0 0 0 0 1 \Gamma_{CH} = 2 dB
: : : :
1 1 1 1 0 \Gamma_{CH} = 60 dB
1 1 1 1 1 \Gamma_{CH} = 62 dB
| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | : : : : | | 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | | | | | | | | | | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | | | | | | | | | | +| : : : : | | | | | | | | | | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | | | | | | | | | | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | | | | | | | | | | +|

USF_GRANULARITY (1 bit field)
This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation.

0 the mobile station shall transmit one RLC/MAC block
1 the mobile station shall transmit four consecutive RLC/MAC blocks

| | | | | | | | | | | +|

TBF_TIMESLOT_ALLOCATION (N bit field)
This information field indicates the timeslots assigned to a particular uplink TBF, within the timeslots assigned to the MS in the Global Timeslot description. This field contains as many bits as there are timeslots assigned to the MS in the Global Timeslot description. Bit N indicates the status of the lowest numbered timeslot in the timeslots assigned to the MS in the Global Timeslot description. Bit N-1 (if any) indicates the status of the next lowest numbered timeslot, etc. At least one timeslot must be assigned per TBF .

In the case of a dual carrier configuration, the timeslots indicated in the MS_TIMESLOT_ALLOCATION_C1 field shall be considered as lower numbered than those in the MS_TIMESLOT_ALLOCATION_C2 field.

0 Timeslot is not assigned
1 Timeslot is assigned

| | | | | | | | | | | +|

USF_ALLOCATION (3 bit field)
This field indicates the USF value assigned to the MS for one or more assigned timeslots. This field is encoded as a binary presentation of the USF value as defined in sub-clause 10.4.1.

| | | | | | | | | | | +|

Assignment Type (2 bit field)

This field is defined in sub-clause 11.2.7.

| | | | | | | | | | | +|

Carrier ID (1 bit field)
This identifies the carrier to which the description refers.

0 Carrier 1
1 Carrier 2

| | | | | | | | | | | +|

NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode.

The list of NPM Transfer Time IEs in the Rel-7 additions is ordered as described by the loops in the earlier releases part.

| | | | | | | | | | | +|

EGPRS mode 2 IE
This information element is defined in sub-clause 12.48a.1.

| | | | | | | | | | | +|

Enhanced Flexible Timeslot Assignment (1 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| | | | | | | | | | | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EMSR Additional PFCs 1
EMSR Additional PFCs 2
EMSR Additional PFCs 3
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| Primary TSC Set (1 bit field)
See sub-clause 11.2.7 and 11.2.29.

Secondary DL TSC Set (1 bit field)
See sub-clause 11.2.7. | +| Secondary DL TSC Value (3 bit field)
See sub-clause 11.2.7. | + +### 11.2.38 MBMS Service Request + +This message is sent on the PACCH from a mobile station to the network in order to inform about the interest in an MBMS session. + +Message type: MBMS SERVICE REQUEST + +Direction: mobile station to network + +**Table 11.2.38.1: MBMS SERVICE REQUEST information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < MBMS service request message content > ::=
< TLLI : bit (32) >
< TMGI : < TMGI struct > >
{ 0 1 < MBMS Session Identity : bit (8) > }
< MS_ID Request Indication : bit (1) >
< padding bits > ; | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.38.2: MBMS SERVICE REQUEST information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TLLI (32 bit field)
This field contains the TLLI of the mobile station. This field is encoded as defined in sub-clause 12.16. | +| TMGI
This field contains the Temporary Mobile Group Identity of the MBMS service that is requested by the mobile station. This field is encoded as defined in sub-clause 12.33. | +| MBMS Session Identity (8 bit field)
The MBMS Session Identity field is included in the message if the request concerns a specific MBMS session, which is known by the mobile station. This field contains the MBMS Session Identity of the concerned MBMS session. | +| MS_ID Request Indication (1 bit field)
This field is used by the mobile station to indicate whether an MS_ID (and thus the possibility to send feedback) is requested by the mobile station. If no MS_ID is requested, the mobile station will not be counted by the network for the given MBMS session (that does not however prevent the network from addressing and assigning the mobile station an MS_ID, if available and the network wishes to do so).

0 MS_ID is not requested
1 MS_ID is requested | + +### 11.2.39 MBMS Assignment (Non-distribution) + +This message is sent on the PCCCH or on the PACCH from the network to (a) mobile station(s) in order to assign the radio bearer resources for an MBMS session or to notify the mobile station(s) that a radio bearer for that MBMS session is not established in the cell or to reassign the MBMS Bearer Identity for an MBMS radio bearer or to reassign radio resources for an MBMS radio bearer. + +Message type: MBMS ASSIGNMENT (NON-DISTRIBUTION) + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.39.1: MBMS ASSIGNMENT (NON-DISTRIBUTION) information elements** + +``` + +< MBMS Assignment Non-distribution message content > ::= + < PAGE_MODE : bit (2) > + { { 0 < Global TFI : < Global TFI IE > > + | 10 < TLLI / G-RNTI : bit (32) > } + { -- Non-distribution part + { 0 | 1 < Length Indicator of MS_ID : bit (2) > + < MS_ID : bit (val (Length Indicator of MS_ID)+1) > + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < ALPHA : bit (4) > + { 0 | 1 < GAMMA : bit (5) > } + } + } + { 0 | 1 < TMGI : < TMGI struct > > } + { 0 | 1 < MBMS Session Identity : bit (8) > } + { 00 -- Assignment reject. No point-to-multipoint channel is established for the MBMS session. + < Reject cause: bit (2) > + { 0 | 1 < Estimated Session Duration : bit (8) > } + } + { 01 -- A point-to-multipoint channel is established or reassigned for the MBMS session. + < MBMS bearer description : < MBMS bearer description struct > > + < Estimated Session Duration : bit (8) > + < MBMS In-band Signalling Indicator : < MBMS In-band Signalling Indicator IE > > + } + { 10 -- The MBMS Bearer Identity is reassigned for the MBMS radio bearer. + { 0 | 1 < MBMS Radio Bearer Starting Time : < bit (16) > } + < Length of MBMS Bearer Identity : bit (3) > + < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) > + ! < Message escape : { 11} bit (*) = < no string > > } -- Extended for future changes + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + } + +< MBMS bearer description struct > ::= + { 0 | 1 < MBMS Radio Bearer Starting Time : < bit (16) > } + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > + < Length of MBMS Bearer Identity : bit (3) > + < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL : bit (3) > } + { 0 | 1 < NPM Transfer Time : bit (5) > } ; + +``` + +**Table 11.2.39.2: MBMS ASSIGNMENT (NON-DISTRIBUTION) information element details** + +**PAGE\_MODE** (2 bit field) + +This field is defined in sub-clause 12.20. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|----|----------------------------------------------------------------------------------------------------------|----|------------------------------------------------------------------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------|--|--|--|--|-----------|--------------------|--|--|--|--|-----------|--------------------|--|--|--|--|-----------|--|--|--|--|--|-----------|---------------------|--|--|--|--|-----------|---------------------|--|--|--|--| +|

Global TFI
This information element shall always contain the DOWNLINK_TFI field. The most significant bit(s) of the DOWNLINK_TFI field denote(s) the MBMS Bearer Identity of the MBMS radio bearer the message relates to. This field is defined in sub-clause 12.10.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

TLLI / G-RNTI (32 bit field)
This field contains the TLLI/G-RNTI of the mobile station. This field is encoded as defined in sub-clause 12.16.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MS_ID (1-4 bit field)
This field addresses the mobile station, identified by the TLLI, receiving the MBMS radio bearer that is described in this message and identified by the MBMS Bearer Identity. If the MS_ID parameter is already assigned in the IMMEDIATE ASSIGNMENT message (specified in the 3GPP TS 44.018) the network shall omit it in this message. This field is defined in sub-clause 12.35.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Packet Timing Advance
If the Packet Timing Advance parameter is already allocated in the IMMEDIATE ASSIGNMENT message (specified in the 3GPP TS 44.018) the network shall omit it in this message. This information element is defined in sub-clause 12.12.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

ALPHA (4 bit field)
If the ALPHA parameter is already allocated in the IMMEDIATE ASSIGNMENT message (specified in the 3GPP TS 44.018) the network shall omit it in this message. For encoding and description see the Global Power Control Parameters IE.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

GAMMA (5 bit field)
The GAMMA field is the binary representation of the parameter \GammaCH for MS output power control in units of 2 dB, see 3GPP TS 45.008. If the GAMMA parameter is already allocated in the IMMEDIATE ASSIGNMENT message (specified in the 3GPP TS 44.018) the network shall omit it in this message. The GAMMA field is coded according to the following table:

bit
5 4 3 2 1
0 0 0 0 0 \GammaCH = 0 dB
0 0 0 0 1 \GammaCH = 2 dB
: : : : :
1 1 1 1 0 \GammaCH = 60 dB
1 1 1 1 1 \GammaCH = 62 dB
| bit | | | | | | 5 4 3 2 1 | | | | | | 0 0 0 0 0 | $\Gamma$ CH = 0 dB | | | | | 0 0 0 0 1 | $\Gamma$ CH = 2 dB | | | | | : : : : : | | | | | | 1 1 1 1 0 | $\Gamma$ CH = 60 dB | | | | | 1 1 1 1 1 | $\Gamma$ CH = 62 dB | | | | | +| bit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 5 4 3 2 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 0 0 | $\Gamma$ CH = 0 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 0 1 | $\Gamma$ CH = 2 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| : : : : : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 1 1 1 0 | $\Gamma$ CH = 60 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 1 1 1 1 | $\Gamma$ CH = 62 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

TMGI
This field contains the Temporary Mobile Group Identity of the MBMS service. This field is encoded as defined in sub-clause 12.33.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MBMS Session Identity (8 bit field)
This field contains the MBMS Session Identity of the concerned MBMS session.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Reject cause (2 bit field)
This field indicates whether the mobile station is allowed to perform further MBMS packet accesses for this MBMS session.

00 No radio bearer established - further MBMS packet accesses allowed for this MBMS session in this cell
01 No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this cell
10 No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this Routing Area
11 No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this PLMN
| 00 | No radio bearer established - further MBMS packet accesses allowed for this MBMS session in this cell | 01 | No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this cell | 10 | No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this Routing Area | 11 | No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this PLMN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 00 | No radio bearer established - further MBMS packet accesses allowed for this MBMS session in this cell | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 01 | No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this cell | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 10 | No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this Routing Area | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 11 | No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this PLMN | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Estimated Session Duration (8 bit field)
This field contains an estimation of either the duration for the concerned MBMS session or, if the MBMS session is ongoing, the remaining duration for the concerned MBMS session. This information element is defined in sub-clause 12.44.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

MBMS In-band Signalling Indicator
This information element contains the MBMS In-band Signalling Indicator. This information element is defined in sub-clause 12.45.

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

MBMS Radio Bearer Starting Time (16 bit field)

This field contains a starting time that indicates the frame number from which the data transfer on the assigned MBMS radio bearer may start. The MBMS Radio Bearer Starting Time is encoded as the value part of the type 3 information element Starting Time in 3GPP TS 44.018.

| +|

Frequency Parameters

If this information element is not present, the same frequency as for the PCCCH or, if the PCCCH is not present in the cell, for the CCCH, on which the network sends this message or the IMMEDIATE ASSIGNMENT message including the Multiple Blocks Packet Downlink Assignment construction and the Packet Channel Description IE specifying the PDCH over which this message is sent (see 3GPP TS 44.018), respectively, shall be used. This information element is defined in sub-clause 12.8.

| +|

DOWNLINK_TIMESLOT_ALLOCATION (8 bit field)

This field is defined in sub-clause 12.18.

| +|

Length of MBMS Bearer Identity (3 bit field)

This field indicates the length of the MBMS Bearer Identity. Any value from 1 to 5 inclusive is allowed. All other values are reserved.

| +|

MBMS Bearer Identity (1-5 bit field)

This field contains the Bearer identity for the MBMS session. This field is defined in sub-clause 12.34.

| +|

EGPRS Window Size

This information element is defined in sub-clause 12.5.2.

| +|

TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL (3 bit field)

This field, if present, identifies the timeslot where the uplink feedback channel, on which the MBMS DOWNLINK ACK/NACK reports shall be sent, is located.

| +|

NPM Transfer Time (5 bit field)

This field is defined in sub-clause 12.45a.

| + +### 11.2.39a MBMS Assignment (Distribution) + +This message is sent on the PCCCH or on the PACCH from the network to mobile stations in order to assign the radio bearer resources for an MBMS session or to notify the mobile stations that a radio bearer for that MBMS session is not established in the cell. + +Message type: MBMS ASSIGNMENT (DISTRIBUTION) + +Direction: network to mobile station + +Classification: distribution message + +Table 11.2.39a.1: MBMS ASSIGNMENT (DISTRIBUTION) information elements + +``` + +< MBMS Assignment Distribution message content > ::= + < PAGE_MODE : bit (2) > + { + < TMGI : < TMGI struct > > + { 0 | 1 < MBMS Session Identity : bit (8) > } + { 0 + -- Assignment reject. No point-to-multipoint channel is established for the MBMS session. + < Reject cause: bit (2) > + { 0 | 1 < Estimated Session Duration : bit (8) > } + } + | 1 + -- A point-to-multipoint channel is established for the MBMS session. + < MBMS bearer description : < MBMS bearer description struct > > + < Estimated Session Duration : bit (8) > + < MBMS In-band Signalling Indicator : < MBMS In-band Signalling Indicator IE > > + } + < padding bits > +! < Distribution part error : bit (*) = < no string > > } ; + +< MBMS bearer description struct > ::= + { 0 | 1 < MBMS Radio Bearer Starting Time : < bit (16) > > } + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > + < Length of MBMS Bearer Identity : bit (3) > + < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity) ) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL : bit (3) > } + { 0 | 1 < NPM Transfer Time : bit (5) > } ; + +``` + +Table 11.2.39a.2: MBMS ASSIGNMENT (DISTRIBUTION) information element details + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)

This field is defined in sub-clause 12.20.

| +|

TMGI

This field contains the Temporary Mobile Group Identity of the MBMS service. This field is encoded as defined in sub-clause 12.33.

| +|

MBMS Session Identity (8 bit field)

This field contains the MBMS Session Identity of the concerned MBMS session.

| +|

Reject cause (2 bit field)

This field indicates whether the mobile station is allowed to perform further MBMS packet accesses for this MBMS session.

00 No radio bearer established - further MBMS packet accesses allowed for this MBMS session in this cell
01 No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this cell
10 No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this Routing Area
11 No radio bearer established - no further MBMS packet accesses allowed for this MBMS session in this PLMN

| +|

Estimated Session Duration (8 bit field)

This field contains an estimation of the session duration for the concerned MBMS session. This information element is defined in sub-clause 12.44.

| +|

MBMS In-band Signalling Indicator

This information element contains the MBMS In-band Signalling Indicator. This information element is defined in sub-clause 12.45.

| +|

MBMS Radio Bearer Starting Time (16 bit field)

This field contains a starting time that indicates the frame number from which the data transfer on the assigned MBMS radio bearer may start. The MBMS Radio Bearer Starting Time is encoded as the value part of the type 3 information element Starting Time in 3GPP TS 44.018.

| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Frequency Parameters
If this information element is not present, the same frequency as for the PCCCH or, if the PCCCH is not present in the cell, for the CCCH, on which the network sends this message or the IMMEDIATE ASSIGNMENT message including the Multiple Blocks Packet Downlink Assignment construction and the Packet Channel Description IE specifying the PDCH over which this message is sent (see 3GPP TS 44.018), respectively, shall be used. This information element is defined in sub-clause 12.8. | +| DOWNLINK_TIMESLOT_ALLOCATION (8 bit field)
This field is defined in sub-clause 12.18. | +| MBMS Bearer Identity (1-5 bit field)
This field contains the Bearer identity for the MBMS session. This field is defined in sub-clause 12.34. | +| EGPRS Window Size
This information element is defined in sub-clause 12.5.2. | +| TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL (3 bit field)
This field, if present, identifies the timeslot where the uplink feedback channel, on which the MBMS DOWNLINK ACK/NACK reports shall be sent, is located. | +| NPM Transfer Time (5 bit field)
This field is defined in sub-clause 12.45a. | + +### 11.2.40 MBMS Neighbouring Cell Information + +This optional message is sent by the network on the PACCH to provide details of the bearer allocated to a particular MBMS session in a neighbouring cell. This message shall not be segmented across more than one RLC/MAC control block. If not all information fits into one instance of the MBMS NEIGHBOURING CELL INFORMATION message, the information can be distributed over more than one instance of the message. + +Message type: MBMS NEIGHBOURING CELL INFORMATION +Direction: network to mobile station +Classification: distribution message + +Table 11.2.40.1: MBMS Neighbouring Cell Information information elements + +``` + +< MBMS Neighbouring Cell Information message content > ::= + < PAGE_MODE : bit (2) > + { 1 < NEIGHBOUR_CELL_INDEX : bit (7) > + { 0 | 1 < BSIC : bit (6) > } + < MBMS_PTM_CHANGE_MARK : bit (2) > + { 1 + < Length of MBMS Bearer Identity : bit (3) > + < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) > + < Absence cause: bit (2) > + } ** 0 -- End of list of MBMS bearers for which no p-t-m channel description is given in the neighbour cell + } ** 0 + { 1 < MBMS Frequency List : < MBMS Frequency List struct > > } ** 0 + { 1 < MBMS p-t-m Frequency Parameters : < MBMS p-t-m Frequency Parameters struct > > + < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > -- default value + { 1 < Length of Serving MBMS Bearer Identity : bit (3) > + < Serving MBMS Bearer Identity : bit (val (Length of Serving MBMS Bearer Identity)) > + < Length of Neighbour MBMS Bearer Identity : bit (3) > + < Neighbour MBMS Bearer Identity : bit (val (Length of Neighbour MBMS Bearer Identity)) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > } -- specific value + { 0 | 1 < TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL : bit (3) > } + { 0 | 1 < MBMS Radio Bearer Starting Time : < bit (16) > > } + < MBMS In-band Signalling Indicator : < MBMS In-band Signalling Indicator IE > > + { 0 | 1 < NPM Transfer Time : bit (5) > } + } ** 0 -- End of list of MBMS bearer descriptions sharing the same PDCH (frequency parameters) + } ** 0 -- End of list of PDCHs for this cell + { 0 | 1 < PBCCH information : < PBCCH information struct > > } +} ** 0 -- End of list of neighbouring cells +{ null | 0 bit** = < no string > -- Receiver compatible with earlier release +| 1 -- Rel-7 additions +{ 1 { 0 | 1 < USF : bit (3) > -- choice bit indicates presence or not of parameters for the MBMS bearer + { 0 | 1 < MPRACH Control Parameters : < MPRACH Control Parameters IE > > } + } +} ** 0 -- End of list of MBMS bearers. +-- The list of MBMS bearers is ordered as described by the loops in the earlier releases part. +} +< padding bits > +! < Distribution part error : bit (*) = < no string > > ; + +< PBCCH information struct > ::= + < Pb : bit (4) > + < TSC : bit (3) > + < TN : bit (3) > + { 00 -- non-hopping PBCCH on BCCH carrier + | 01 < ARFCN : bit (10) > -- non-hopping PBCCH + | 1 -- hopping PBCCH, frequency parameters from an MBMS bearer description for this cell + < Length of Neighbour MBMS Bearer Identity : bit (3) > + < Neighbour MBMS Bearer Identity : bit (val (Length of Neighbour MBMS Bearer Identity)) > + } ; + +< MBMS Frequency List struct > ::= + < FREQ_LIST_NUMBER : bit (2) > + < Length of Frequency List contents : bit (4) > + < Frequency List contents : octet (val(Length of Frequency List contents) + 3) > ; + +< MBMS p-t-m Frequency Parameters struct > ::= + < TSC : bit (3) > + { 0 < ARFCN : bit (10) > + | 1 < MAIO : bit (6) > + < HSN : bit (6) > + < FREQ_LIST_NUMBER : bit (2) > } ; + +``` + +**Table 11.2.40.2: MBMS Neighbouring Cell Information information element details** + +| | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----|---------------------------------------------------------------------------------------------------------------|----|--------------------------------------------------------------------------------------------------------------|----|--------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20 and gives the PAGE_MODE parameter valid in the serving cell.

| | | | | | | | | +|

NEIGHBOUR_CELL_INDEX (7 bit field)
This information element is the index within the GSM Neighbour Cell list (defined in sub-clause 5.6.3.2) of the cell for which information is provided.

If the mobile station has not completed the construction of the GSM Neighbour Cell list (i.e. before the MS has acquired the complete GSM Neighbour Cell list from the BCCH messages, in case the PBCCH is not allocated in the cell), it shall not disregard this message but store the information contained in it.

| | | | | | | | | +|

BSIC (6 bit field)

This optional field is needed to identify the neighbour cell in case the GSM Neighbour Cell list is only a frequency list, see 3GPP TS 44.060 sub-clause 5.6.3.2.

| | | | | | | | | +|

MBMS_PTM_CHANGE_MARK (2 bit field)

This field contains the change mark value for the information given for a specific neighbouring cell. This information is used to combine information from multiple instances of the MBMS Neighbouring Cell Information message.

| | | | | | | | | +|

MBMS Bearer Identity (1-5 bit field)
This field contains the Bearer identity for the MBMS session. This field is defined in sub-clause 12.34.

| | | | | | | | | +|

Absence cause (2 bit field)
This field indicates why the description of the MBMS bearer for the neighbour cell is not provided in the message.

00 Neighbour cell not in the service area for the MBMS service associated with this Bearer identifier
01 No p-t-m bearer established in the neighbour cell for the MBMS service associated with this Bearer identifier
10 p-t-m bearer established in the neighbour cell for this MBMS service, but the description cannot be provided
11 No information available for the MBMS service associated with this bearer identifier
| 00 | Neighbour cell not in the service area for the MBMS service associated with this Bearer identifier | 01 | No p-t-m bearer established in the neighbour cell for the MBMS service associated with this Bearer identifier | 10 | p-t-m bearer established in the neighbour cell for this MBMS service, but the description cannot be provided | 11 | No information available for the MBMS service associated with this bearer identifier | +| 00 | Neighbour cell not in the service area for the MBMS service associated with this Bearer identifier | | | | | | | | +| 01 | No p-t-m bearer established in the neighbour cell for the MBMS service associated with this Bearer identifier | | | | | | | | +| 10 | p-t-m bearer established in the neighbour cell for this MBMS service, but the description cannot be provided | | | | | | | | +| 11 | No information available for the MBMS service associated with this bearer identifier | | | | | | | | +|

Serving MBMS Bearer Identity (1-5 bit field)
This field contains the Bearer identity used by the MBMS session in the serving cell. This field is encoded as the MBMS Bearer Identity IE defined in sub-clause 12.34.

| | | | | | | | | +|

Neighbour MBMS Bearer Identity (1-5 bit field)
This field contains the Bearer identity used by the MBMS session in the neighbour cell. This field is encoded as the MBMS Bearer Identity IE defined in sub-clause 12.34.

| | | | | | | | | +|

MBMS p-t-m Frequency Parameters
This information provides a description of a hopping or non-hopping radio frequency channel . In case hopping frequency channel is described, a reference to a specified MBMS Frequency List shall be provided. If MBMS Frequency List has not been received by the MS, it shall store this information for possible later use in case such MBMS Frequency List is received.

| | | | | | | | | +|

TSC (3 bit field)
This field is the binary representation of the training sequence code, see 3GPP TS 45.002. Range: 0 to 7.

| | | | | | | | | +|

ARFCN (10 bit field)
This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS 45.005. Range 0 to 1023.

| | | | | | | | | +|

MAIO (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 45.002. Range 0 to 63.

| | | | | | | | | +|

HSN (6 bit field)
This field is the binary representation of the hopping sequence number, see 3GPP TS 45.002. Range: 0 to 63.

| | | | | | | | | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FREQ_LIST_NUMBER (2 bit field)
This field is the binary identification of a MBMS Frequency List provided by an instance of this message, or the binary reference to such. Range: 0 to 3. | +| MBMS Frequency List
This information contains a set of radio frequency channels. This list shall be identified by the FREQ_LIST_NUMBER field. | +| Frequency List contents (variable length octet string)
This variable length octet string is the representation of a set of radio frequency channels defining a GPRS mobile allocation. The encoding of the octet string is defined by the value part of the type 4 information element Frequency List , defined in 3GPP TS 44.018. The allowed formats of the Frequency List information element are the bit map 0 , 1024 range , 512 range , 256 range , 128 range and variable bit map formats. | +| DOWNLINK_TIMESLOT_ALLOCATION (8 bit field)
This information element describes which timeslots are assigned to the MBMS bearer in the neighbouring cell. This field is encoded as the Timeslot Allocation field defined in sub-clause 12.18.

The field following the Frequency Parameters information element shall refer to all the MBMS bearers described in the subsequent loop (default value). If this field is provided for a particular MBMS bearer, it refers only to that MBMS bearer (this specific value overrides the default value). Every MBMS bearer shall be assigned either the default value or a specific value. | +| TIMELOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL (3 bit field)
This field indicates the timeslot used for the uplink feedback channel in the neighbour cell. This field is coded as the binary representation of the timeslot number. | +| EGPRS Window Size
This information element is defined in sub-clause 12.5.2. | +| MBMS Radio Bearer Starting Time (16 bit field)
This field contains a starting time that indicates the frame number from which the data transfer on the assigned MBMS radio bearer may start. The MBMS Radio Bearer Starting Time is encoded as the value part of the type 3 information element Starting Time in 3GPP TS 44.018. | +| MBMS In-band Signalling Indicator
This information element contains the MBMS In-band Signalling Indicator. This information element is defined in sub-clause 12.45. | +| PBCCH information

This information, if present, describes the PBCCH location in the target cell. In case PBCCH is allocated in the target cell and can be described with this encoding, this information shall be included in the message. | +| USF (3 bit field)
This field identifies the USF value that identifies the MPRACH defined on the uplink feedback channel in the neighbour cell.

The list of MBMS bearers in the Rel-7 additions is ordered as described by the loops in the earlier releases part. The choice bit indicates for each MBMS bearer whether the parameters are present or not. | +| MPRACH Control Parameters
This information element, if present, defines the access control parameters to be used on the MPRACH defined on the uplink feedback channel in the neighbour cell. This information element is defined in sub-clause 12.41. | +| NPM Transfer Time (5 bit field)
This field is defined in sub-clause 12.45a. | + +#### 11.2.4.1 MBMS MS\_ID Assignment + +This message is sent on the PACCH by the network to the mobile station to assign an MS\_ID and to provide the timing advance parameters to the mobile station in case of an MBMS radio bearer with an assigned uplink feedback channel. The message can also be used to reassign or delete the MS\_ID assigned to the mobile station. + +Message type: MBMS MS\_ID ASSIGNMENT + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.4.1.1: MBMS MS\_ID ASSIGNMENT information elements** + +``` +< MBMS MS_ID Assignment message content > ::= + < PAGE_MODE : bit (2) > + { { 0 < Global TFI : < Global TFI IE > > + | 10 < TLLI / G-RNTI : bit (32) > } + { 0 -- MS_ID is assigned the first time. + < Length of MBMS Bearer Identity : bit (3) > + < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) > + < MS_ID : bit (5 - val (Length of MBMS Bearer Identity)) > + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < ALPHA : bit (4) > + { 0 | 1 < GAMMA : bit (5) > } } + } + | 1 -- MS_ID is reassigned. + < Current MS_ID Expiry Time : bit (16) > + { 0 -- MS_ID is not redefined. + | 1 -- MS_ID is redefined. + < Length Indicator of MS_ID : bit (2) > + < MS_ID : bit (val (Length Indicator of MS_ID) + 1) > } + { 0 | 1 < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < ALPHA : bit (4) > + { 0 | 1 < GAMMA : bit (5) > } } + } + } + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.4.1.2: MBMS MS\_ID ASSIGNMENT information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

| +|

Global TFI
This information element shall always contain the DOWNLINK_TFI field. The most significant bit(s) of the DOWNLINK_TFI field denote(s) the MBMS Bearer Identity of the MBMS radio bearer the message relates to and the remaining least significant bit(s) denote(s) the MS_ID addressing the mobile station the message relates to. This field is defined in sub-clause 12.10.

| +|

TLLI / G-RNTI (32 bit field)
This field contains the TLLI/G-RNTI of the mobile station. This field is encoded as defined in sub-clause 12.16.

| +|

MBMS Bearer Identity (1-5 bit field)
This field identifies the MBMS radio bearer this message relates to and is defined in sub-clause 12.34.

| +|

MS_ID (1-4 bit field)
This field assigns an identifier to the mobile station, identified by the TLLI, on the MBMS radio bearer identified by the MBMS Bearer Identity, and can also be used to reassign the identifier assigned to the mobile station. This field is defined in sub-clause 12.35.

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

Packet Timing Advance
This information element is defined in sub-clause 12.12.

| +|

ALPHA (4 bit field)
For encoding and description see the Global Power Control Parameters IE.

| +|

GAMMA (5 bit field)
The GAMMA field is the binary representation of the parameter \Gamma_{CH} for MS output power control in units of 2 dB, see 3GPP TS 45.008. The GAMMA field is coded according to the following table:

bit
5 4 3 2 1
0 0 0 0 0   \Gamma_{CH} = 0 dB
0 0 0 0 1   \Gamma_{CH} = 2 dB
: : : : :
1 1 1 1 0   \Gamma_{CH} = 60 dB
1 1 1 1 1   \Gamma_{CH} = 62 dB

| +|

Current MS_ID Expiry Time
This field contains an expiry time that indicates the frame number during which the mobile station shall consider the current MS_ID as released and, if a new MS_ID is assigned, the new MS_ID as valid. This information element is encoded as the value part of the Starting Time information element specified in 3GPP TS 44.018.

| + +### 11.2.42 Packet MBMS Announcement + +This message is sent on PACCH by the network to notify all MBMS mobile stations listening to that PDCH that an MBMS Service Session is commencing or an ongoing MBMS Broadcast Service Session with an updated MBMS service area list is available. + +Message type: PACKET MBMS ANNOUNCEMENT + Direction: network to mobile station + Classification: distribution message + +**Table 11.2.42.1: PACKET MBMS ANNOUNCEMENT information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < PACKET MBMS ANNOUNCEMENT message content > ::=    < PAGE_MODE : bit (2) >   < TMGI : < TMGI IE > >   { 0   1 < MBMS Session Identity : bit (8) > }   { 0                                     -- counting is off     { 0   1 < MBMS p-t-m channel description : < MBMS p-t-m channel description struct > > }       1                                   -- counting is on     { 0   1 < MPRACH description : < MPRACH description struct > > }   }   { 0   1 < RESTRICTION_TIMER : bit (4) > }   < padding bits > } // -- truncation at end of message allowed, bits '0' assumed ! < Distribution part error : bit (*) = < no string > > ;
| +| 
 < MBMS p-t-m channel description struct > ::=    < Estimated Session Duration : bit (8) >   { 0   1 < MBMS Radio Bearer Starting Time : bit (16) > }   { 0   1 < Frequency Parameters : < Frequency Parameters IE > > }   < DL_TIMESLOT_ALLOCATION : bit (8) >   < Length of MBMS Bearer Identity : bit (3) >   < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) >   { 0   1 < EGPRS Window Size : < EGPRS Window Size IE > > }   { 0   1 < NPM Transfer Time : bit (5) > };
| +| 
 < MPRACH description struct > ::=    { 0   1 < Frequency Parameters : < Frequency Parameters IE > > }   < MPRACH_TIMESLOT : bit (3) >   < USF : bit (3) >   { 0                                     -- no MPRACH access parameters present     1                                     -- MPRACH access parameters present     < MPRACH Control Parameters : < MPRACH Control Parameters IE > > };
| + +**Table 11.2.42.2: PACKET MBMS ANNOUNCEMENT information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

| +|

TMGI IE
This field contains the Temporary Mobile Group Identity of the MBMS service that the MBMS Notification concerns. This field is encoded as defined in sub-clause 12.33.

| +|

MBMS Session Identity (8 bit field)
This field contains the MBMS Session Identity of the concerned MBMS session (see TS 23.003).

| +|

Estimated Session Duration (8 bit field)
This field contains an estimation of the session (remaining) duration for the concerned MBMS session. This information element is defined in sub-clause 12.44.

| +|

MBMS Radio Bearer Starting Time (16 bit field)
This field contains a starting time that indicates the frame number from which the data transfer on the assigned MBMS radio bearer may start. The MBMS Radio Bearer Starting Time is encoded as the value part of the type 3 information element Starting Time in 3GPP TS 44.018.

| +|

Frequency Parameters
If this information element is not present, the same frequency as for the PCCCH shall be used. This information element is defined in sub-clause 12.8.

| +|

DL_TIMESLOT_ALLOCATION (8 bit field)
This field is defined in sub-clause 12.18.

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

MBMS Bearer Identity (1-5 bit field)

This field assigns a TFI value, or a subset of a TFI value, which identifies the MBMS radio bearer that is described. In case only a subset of a TFI value is assigned for the MBMS radio bearer, that subset corresponds to the most significant bit(s) of the TFI field.

| | | | | | | | | | | | | | | | | +|

EGPRS Window Size

This information element is defined in sub-clause 12.5.2.

| | | | | | | | | | | | | | | | | +|

MPRACH_TIMESLOT (3 bit field)

This field identifies the timeslot number of the PDCH where the MPRACH is located.

| | | | | | | | | | | | | | | | | +|

USF (3 bit field)

This field identifies the USF value that identifies the MPRACH on the defined PDCH.

| | | | | | | | | | | | | | | | | +|

MPRACH Control Parameters

This information element, if present, defines the access control parameters to be used on the MPRACH. This information element is defined in sub-clause 12.41.

| | | | | | | | | | | | | | | | | +|

RESTRICTION_TIMER

This field indicates the maximum reaction time to the PACKET MBMS ANNOUNCEMENT message in seconds for mobile station, before the information contained in the PACKET MBMS ANNOUNCEMENT message expires.

Bit
4 3 2 1
0 0 0 0 10
0 0 0 1 20
0 0 1 0 30
...
1 1 1 0 150
1 1 1 1 160
| Bit | | 4 3 2 1 | | 0 0 0 0 | 10 | 0 0 0 1 | 20 | 0 0 1 0 | 30 | ... | | 1 1 1 0 | 150 | 1 1 1 1 | 160 | +| Bit | | | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | | | +| 0 0 0 0 | 10 | | | | | | | | | | | | | | | | +| 0 0 0 1 | 20 | | | | | | | | | | | | | | | | +| 0 0 1 0 | 30 | | | | | | | | | | | | | | | | +| ... | | | | | | | | | | | | | | | | | +| 1 1 1 0 | 150 | | | | | | | | | | | | | | | | +| 1 1 1 1 | 160 | | | | | | | | | | | | | | | | +|

NPM Transfer Time (5 bit field)

This field is defined in sub-clause 12.45a.

| | | | | | | | | | | | | | | | | + +### 11.2.43 PS Handover Command + +This message is sent on the PACCH by the network to the mobile station to command the mobile station to leave the current cell and change to a new cell. The mobile station shall acknowledge this message according to sub-clause 8.10.4. This message can be sent using Extended RLC/MAC control segmentation (see sub-clause 9.1.12a). The combined length of the IEs included in the PS HANDOVER COMMAND message shall not exceed 175 octets. + +If the network allocates PS resources on a single carrier where those resources are not required to support any of the features EGPRS2, Fast Ack/Nack Reporting or RTTI configurations, then the network shall include the PS Handover Radio Resources Info IE in the PS HANDOVER COMMAND message. Otherwise, the network shall include the PS Handover Radio Resources 2 Info IE or the PS Handover Radio Resources 3 IE the PS HANDOVER COMMAND message. + +Message type: PS HANDOVER COMMAND + +Direction: network to mobile station + +Classification: non-distribution message + +Table 11.2.43.1: PS HANDOVER COMMAND information elements + +``` + +< PS Handover Command message content > ::= + < PAGE_MODE : bit (2) > + { 0 < Global TFI : < Global TFI IE > > + { -- Non-distribution part + < CONTAINER_ID : bit(2) > + { 00 < PS Handover to A/Gb Mode Payload : + { 00 < PS Handover RR Info: < PS Handover Radio Resources IE > > + | 01 < PS Handover RR 2 Info: < PS Handover Radio Resources 2 IE > > + | 10 < PS Handover RR 3 Info: < PS Handover Radio Resources 3 IE > > + ! < RR Handover RR Info Error : { 11 } bit (*) = > } - Extended for future changes + { 0 | 1 < NAS Container for PS Handover IE > } + } + | 01 < PS Handover to UTRAN Payload : + { < RRC Container IE > > + } + | 10 < PS Handover to E-UTRAN Payload : + { < RRC Container IE > > + } + } < Message escape : 11 bit (*) = < no string > > } -- Extended for future changes + } null | 0 bit** = < no string > -- Receiver compatible with earlier release + | 1 -- Additions in Rel-8 : + { 0 | 1 < E-UTRAN_CCN_ACTIVE : bit (1) > } + { 0 | 1 < Measurement Control Parameters Description : + < MeasurementControl Parameters Description IE>> } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + } 1 -- Additions for Rel-9 + { < Enhanced Flexible Timeslot Assignment : bit > + { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used + } 1 -- EMST is used + { 0 + } 1 < Downlink RLC Entity 2 : < RLC Entity Struct > + { 0 + } 1 < Downlink RLC Entity 3 : < RLC Entity Struct > } + } + { 0 + } 1 < Uplink RLC Entity 2 : < RLC Entity Struct > + { 0 + } 1 < Uplink RLC Entity 3 : < RLC Entity Struct > } + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + } 1 -- Additions for Rel-10 + { 0 -- EMSR is not enabled in downlink + } 1 -- EMSR is enabled in downlink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + { 0 -- EMSR is not enabled in uplink + } 1 -- EMSR is enabled in uplink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + } 1 -- Additions for Rel-11 + { 0 | 1 < Selected PLMN Index : bit(3) > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + } 1 -- Additions for Rel-12 + { < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + } + < padding bits > } } } } + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; + +``` + +``` + +< RLC Entity Struct > ::= + < TFI : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < PFI : bit (7) >; + +< Additional PFCs struct > ::= + < TFI : bit (5) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < PFI : bit (7) >; + +``` + +**Table 11.2.43.2: PS HANDOVER COMMAND information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

| +|

Global TFI
This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10.

| +|

CONTAINER_ID (2 bit field)
This field contains the identity of the neighbour cell system information container previously sent in the PACKET NEIGHBOUR CELL DATA messages (see sub-clause 8.10.2). This field is ignored by the mobile station except in the case of PS Handover from GERAN A/Gb mode or GERAN Iu mode to GERAN A/Gb or GERAN Iu mode.

Range 0 to 3.

| +|

PS Handover to A/Gb Mode Payload
This information element contains the information needed by the mobile station when performing PS Handover to A/Gb mode. It consists of the PS Handover Radio Resources IE (see sub-clause 12.42) or the PS Handover Radio Resources 2 IE (see sub-clause 12.42a) or the PS Handover Radio Resources 3 IE (see sub-clause 12.42b) and optionally the NAS Container for PS Handover IE (see sub-clause 12.43).

| +|

PS Handover to UTRAN Payload
This information element contains a HANDOVER TO UTRAN COMMAND message (as defined in 3GPP TS 25.331) containing the information needed by the mobile station when performing PS Handover to UTRAN. This information element is defined in sub-clause 12.45b.

| +|

PS Handover to E-UTRAN Payload
This information element contains a DL-DCCH-Message including a RRCConnectionReconfiguration message (as defined in 3GPP TS 36.331) containing the information needed by the mobile station when performing PS Handover to E-UTRAN. This information element is defined in sub-clause 12.45b.

| +|

E-UTRAN_CCN_ACTIVE (1 bit field)
This field indicates whether CCN is enabled towards E-UTRAN neighbouring cells in the target cell. For description and encoding see subclause 12.53. This field shall be included only if the PS Handover to A/Gb Mode Payload structure is included.

| +|

Enhanced Flexible Timeslot Assignment (1 bit field)
This field is defined in sub-clause 11.2.29.

| +|

Measurement Control Parameters Description
This information element contains the Measurement control parameters per frequency for UTRAN and E-UTRAN for the target cell. This information element is defined in sub-clause 12.56. This field shall be included only if the PS Handover to A/Gb Mode Payload structure is included.

| +|

EMST_NW_Capability (1 bit field)
This information element is defined in sub-clause 11.2.29.

| +|

PFI (7 bit field)
This information element is defined in sub-clause 11.2.31.

| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TFI (5 bit field)
This information element is defined in sub-clause 11.2.31. | +| RLC_MODE (1 bit field)
This information element is defined in sub-clause 11.2.31. | +| NPM Transfer Time (5 bit field) | +| EMSR Additional PFCs 1
EMSR Additional PFCs 2
EMSR Additional PFCs 3
These IEs are defined in section 11.2.7. If the PS HANDOVER COMMAND message includes the PS Handover Radio Resources 3 IE then these information elements shall be ignored (if included). | +| Selected PLMN Index (3 bit field)
This field is defined in sub-clause 10.4.27 | +| PS Handover RR 3 Info
This information is included when performing a PS handover that results in a DLMC configuration (see sub-clause 12.42b). | +| Primary TSC Set (1 bit field)
See sub-clause 11.2.7 and 11.2.29. | +| Secondary DL TSC Set (1 bit field)
See sub-clause 11.2.7. | +| Secondary DL TSC Value (3 bit field)
See sub-clause 11.2.7. | + +### 11.2.44 PS Handover Access + +This message is sent by the mobile station to the network to make the network aware that the mobile station has left the old cell and arrived in the new cell. The message is sent four times using either the 8-bit or 11-bit access burst format on the PACCH associated with an uplink TBF allocated in the PS Handover Command message as described in sub-clause 8.10.4. The mobile station shall use the format indicated by the System Information parameter ACCESS\_BURST\_TYPE applicable to the target cell. Each message is coded as shown in table 11.2.42.1. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. + +Message type: PS HANDOVER ACCESS + +Direction: mobile station to network + +**Table 11.2.44.1: PS HANDOVER ACCESS information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < PS Handover Access message content 8 bit message > ::= -- 8-bit access burst format
< Handover Reference : bit (8) > ; | +| < PS Handover Access message content 11 bit message > ::= -- 11-bit access burst format
< Handover Reference : bit (8) >
< spare : bit (3) > ; | + +**Table 11.2.44.2 : PS HANDOVER ACCESS information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Handover Reference (8 bit field)
This information field identifies the mobile station in the new cell. The semantics of this field is defined in 3GPP TS 44.018. | +| spare (3 bit field)
These bits are reserved for future use and shall be set to '000' in this release. | + +### 11.2.45 Packet Physical Information (A/Gb mode only) + +This message is sent on PACCH by the network to the mobile station during a handover procedure as specified in sub-clause 8.10 to indicate a valid timing advance to the mobile station. + +Message type: PACKET PHYSICAL INFORMATION + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.45.1: PACKET PHYSICAL INFORMATION information elements** + +| | | +|-----------------------------------------------------|-----------------------------------------------------------| +| < Packet Physical information message content > ::= | -- RLC/MAC control block format | +| < PAGE_MODE : bit (2) > | | +| < Global TFI : < Global TFI IE > > | | +| < TIMING_ADVANCE_VALUE : bit (8) > | | +| < padding bits > ; | -- truncation at end of message allowed, bits '0' assumed | + +**Table 11.2.45.2: PACKET PHYSICAL INFORMATION information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20. | +| Global TFI
This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. | +| TIMING_ADVANCE_VALUE (8 bit field)
This field is coded as the timing advance value field defined in 3GPP TS 44.018. | + +### 11.2.46 DTM Handover Command + +This message is sent on the PACCH by the network to the mobile station in dual transfer mode to command the mobile station to leave the current cell and change to a new cell. This message may be sent using Extended RLC/MAC control segmentation (see sub-clause 9.1.12a). The combined length of the IEs included in the DTM HANDOVER COMMAND message shall not exceed 175 octets. + +If the network allocates PS resources on a single carrier where those resources are not required to support any of the features EGPRS2, Fast Ack/Nack Reporting or RTTI configurations, then the network shall include the DTM Handover PS Radio Resources IE in the DTM HANDOVER COMMAND message. Otherwise, the network shall include the DTM Handover PS Radio Resources 2 IE or DTM Handover PS Radio Resources 3 IE in the DTM HANDOVER COMMAND message. + +Message type: DTM HANDOVER COMMAND + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.46.1: DTM HANDOVER COMMAND information elements** + +``` + +< DTM Handover Command message content > ::= + < PAGE_MODE : bit (2) > + { 0 < Global TFI : < Global TFI IE > > + { -- Non-distribution part + { 00 < DTM Handover to A/Gb Mode Payload : + < DTM Handover to A/Gb mode Payload description struct > > + | 01 < DTM Handover to UTRAN Payload : < RRC Container IE > > + ! < Message escape : { 10 | 11 } bit (*) = < no string > > } -- Extended for future changes + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Non-distribution part error : bit (*) = < no string > > ; + + < DTM Handover to A/Gb mode Payload description struct > ::= + < DTM Handover CS RR Info: < DTM Handover CS Radio Resources IE > > + { 00 < DTM Handover PS RR Info: < DTM Handover PS Radio Resources IE > > + | 01 < DTM Handover PS RR 2 Info : < DTM Handover PS Radio Resources 2 IE > > + | 10 < DTM Handover PS RR 3 Info : < DTM Handover PS Radio Resources 3 IE > > + ! < Message escape : { 11 } bit (*) = < no string > > } -- reserved for future use + { 0 | 1 < NAS Container for PS Handover IE > }; + +``` + +**Table 11.2.46.2: DTM HANDOVER COMMAND information element details** + +#### **PAGE\_MODE (2 bit field)** + +This field is defined in sub-clause 12.20. + +#### **Global TFI** + +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +#### **DTM Handover CS Radio Resources** + +This information element contains the CS information needed by the mobile station when performing DTM Handover to *A/Gb mode* and is defined in sub-clause 12.47. If a mobile station supports extended TSC sets (see 3GPP TS 45.002 [32]) then TSC related information applicable to the PS domain identified by the *DTM Handover PS RR Info* IE, the *DTM Handover PS RR 2 Info* IE or the *DTM Handover PS RR 3 Info* IE shall take precedence over TSC related information applicable to the PS domain provided by this IE. + +#### **DTM Handover PS RR Info** + +This information element contains the PS information needed by the mobile station when performing DTM Handover to *A/Gb mode* and is defined in sub-clause 12.46. If a mobile station supports extended TSC sets (see 3GPP TS 45.002 [32]) then this IE can be used to identify TSC related information applicable to the PS domain. + +#### **DTM Handover PS RR 2 Info** + +This information element contains the PS information needed by the mobile station when performing DTM Handover to *A/Gb mode* when downlink PS resources are assigned on two carriers or requires the support of EGPRS2, Fast Ack/Nack Reporting or RTTI configurations, and is defined in sub-clause 12.48. If a mobile station supports extended TSC sets (see 3GPP TS 45.002 [32]) then this IE can be used to identify TSC related information applicable to the PS domain. + +#### **DTM Handover PS RR 3 Info** + +This information element contains the PS information needed by the mobile station and can only be used when EMSR or extended TSC sets (see 3GPP TS 45.002 [32]) is supported by the mobile station. This information element is defined in sub-clause 12.64. If a mobile station supports extended TSC sets (see 3GPP TS 45.002 [32]) then this IE can be used to identify TSC related information applicable to the PS domain. + +#### **NAS Container for PS Handover** + +This information element contains the NAS information needed by the mobile station when performing DTM Handover to *A/Gb mode* and is defined in sub-clause 12.43. + +#### **DTM Handover to UTRAN Payload** + +This information element contains a HANDOVER TO UTRAN COMMAND message (as defined in 3GPP TS 25.331) containing the information needed by the mobile station when performing DTM Handover to UTRAN. This information element is defined in sub-clause 12.45b. + +### 11.2.47 Packet Application Information + +This message is sent on the PACCH by the network to convey an embedded Application, e.g. an ETWS Primary Notification message (see 3GPP TS 23.041), between the network and the mobile station(s). This message may be segmented across more than two RLC/MAC control blocks by using extended RLC/MAC control message segmentation. + +Message type: PACKET APPLICATION INFORMATION + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.47.1: PACKET APPLICATION INFORMATION information elements** + +``` +< Packet Application Information message content > ::= + < PAGE_MODE : bit (2) > + { + < Application Type : bit (4) > -- type of Application + < Application Data : octet ** > + < padding bits >} + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.47.2: PACKET APPLICATION INFORMATION information element details** + +#### **PAGE\_MODE (2 bit field)** + +This field is defined in sub-clause 12.20. + +#### **Application Type (4 bit field)** + +This field identifies the particular protocol and associated application for the Application data. + +#### **Bit** + +4 3 2 1 + +0 0 0 0 ETWS (3GPP TS 23.041) + +0 0 0 1 reserved for future use + +to + +1 1 1 1 reserved for future use + +#### **Application Data (n\*8 bits)** + +The Application Data contains the data of following Application Types: + +ETWS The ETWS data forms the actual ETWS Primary Notification message. The ETWS Primary Notification data is coded as specified in 3GPP TS 23.041. + +### 11.2.48 EGPRS Packet Downlink Ack/Nack DLMC + +This message is sent on the PACCH from the mobile station to the network to indicate the status of downlink RLC data blocks received and to report the channel quality of the downlink for a DLMC configuration. + +Message type: EGPRS Packet Downlink Ack/Nack DLMC + +Direction: mobile station to network + +**Table 11.2.48.1: EGPRS PACKET DOWNLINK ACK/NACK DLMC information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < EGPRS Packet Downlink Ack/Nack DLMC message content > ::=
< DOWNLINK_TFI : bit (5) >
< DOWNLINK_eTFI : bit (3) >
< MS OUT OF MEMORY : bit(1)>
{ 0 1 < DLMC Channel Quality Report >}
{ 0 1 < Channel Request Description >}
{ 0 1 < PFI : bit(7) > }
{ 0 1 < EGPRS Ack/Nack Description DLMC >
{ 0 1 < DLMC Channel Quality Report >} }
; | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.48.2: EGPRS PACKET DOWNLINK ACK/NACK DLMC information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DOWNLINK_TFI (5 bit field)
This field contains the TFI of the mobile station's downlink TBF. This field is defined in sub-clause 12.15. | +| DOWNLINK_eTFI (3 bit field)
This field contains the eTFI of the mobile station's downlink TBF. A mobile station not assigned an eTFI shall set this field to ‘000’. | +| MS OUT OF MEMORY (1 bit field)
This field indicates that the MS has no more enough memory to perform Incremental Redundancy.

0 The MS has enough memory
1 The MS is running out of memory | +| DLMC Channel Quality Report
This information element is defined in sub-clause 12.66. This IE shall be used by a mobile station with a DLMC configuration and contains measurements corresponding to the set of reported UFPS/carriers (see sub-clause 9.1.8.2.1 for how the set of UFPS/carriers to report is determined). | +| Channel Request Description
This information element is defined in sub-clause 12.7. If a PFI field is included in this message, it relates to the TBF request contained in the Channel Request Description IE. | +| PFI (7 bit field)
This field contains the PFI parameter identifying a Packet Flow Context relating to the resource request specified in the Channel Request Description IE. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. This field may be included if the network supports packet flow context procedures and if a Channel Request Description IE is included in the message. If this field is included but the Channel Request Description IE is omitted, this field shall be ignored. | +| EGPRS Ack/Nack Description DLMC (L bit field)
This information element is defined in sub-clause 12.3.3. The number of bits (L) available for this information element depends on the inclusion of channel quality reports and channel requests. L shall be set so that the entire EGPRS PACKET DOWNLINK ACK/NACK DLMC message evenly fits into an RLC/MAC control block. If a lower L covers the entire receive window, that L shall be used.

Truncation of the EGPRS Ack/Nack Description DLMC IE is allowed if the available space in the message without this IE does not allow for the inclusion of a valid EGPRS Ack/Nack Description DLMC IE, i.e. is less than 16 bits of message space remains. In these conditions, the receiver shall assume that no EGPRS Ack/Nack Description DLMC IE is included. | + +### 11.2.49 EC Packet Access Reject + +This message is sent on the EC-PACCH by the network to the mobile station to indicate that the network has rejected the request from the mobile station. This message may contain fields addressing more than one mobile station. + +Message type: EC PACKET ACCESS REJECT + Direction: network to mobile station + Classification: distribution message + +**Table 11.2.49.1: EC PACKET ACCESS REJECT information elements** + +``` +< EC Packet Access Reject message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE > > + < Reject : < EC Reject struct > > + { { 1 < Additional Reject: < EC Reject struct > > } ** 0 + < padding bits > } // -- truncation at end of message allowed, bits '0' assumed + ! < Distribution part error : bit (*) = < no string > > ; + +< EC Reject struct > ::= + < Downlink_TFI : bit (5) > + { 0 | 1 < WAIT_INDICATION : bit (8) > + < WAIT_INDICATION_SIZE : bit (1) > } + ! < Ignore : bit (*) = < no string > > ; +``` + +**Table 11.2.49.2: EC PACKET ACCESS REJECT information element details** + +#### USED\_DL\_COVERAGE\_CLASS + +This information element is defined in sub-clause 12.71. + +#### EC Reject struct + +The mobile station shall only accept the first Reject struct addressed to it and ignore all other Reject structs. + +#### WAIT\_INDICATION (8 bit field) + +The Wait Indication field indicates the time the mobile station shall wait before attempting another channel request. This field is coded as the binary representation of the T3172 timeout value in units of 20 ms or in units of seconds. The units are indicated in the WAIT\_INDICATION\_SIZE field. Range 0 to 255. + +#### WAIT\_INDICATION\_SIZE (1 bit field) + +This field indicates the units of the WAIT\_INDICATION field. + +- 0 the WAIT\_INDICATION field is coded in units of s +- 1 the WAIT\_INDICATION field is coded in units of 20 ms + +### 11.2.50 EC Packet Control Acknowledgement + +This message is sent on the EC-PACCH from the mobile station to the network. The message is formatted either as an RLC/MAC control block using the EC-PACCH block format defined in 3GPP TS 44.004 or as a number of identical access bursts, according to the assigned uplink CC (see 3GPP TS 45.002), using the EC-PACCH short acknowledgement block format defined in 3GPP TS 44.004. If the message is sent as response to an EC Packet Polling Request message this latter message shall specify the format of the EC Packet Control Acknowledgement message. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. + +The RLC/MAC control block format is shown in table 11.2.50.1 and table 11.2.50.2. + +The access burst format is 11-bits and is coded as shown in table 11.2.50.1. The mobile station shall transmit the access burst four times, one time in each TDMA frame of the uplink radio block. The transmission of the four access bursts shall then be repeated in each of the uplink EC-PACCH resources assigned with the RRBP field according to the assigned uplink Coverage Class for the mobile station. + +Message type: EC PACKET CONTROL ACKNOWLEDGEMENT + Direction: mobile station to network + +**Table 11.2.50.1: EC PACKET CONTROL ACKNOWLEDGEMENT information elements** + +| | | +|-----------------------------------------------------------|----------------------------------------| +| < EC Packet Control Acknowledgement message content > ::= | -- RLC/MAC control block format | +| < TLLI : bit (32) > | | +| < CTRL_ACK : bit (2) > | | +| < DL_CC_EST : bit (4) > | | +| < padding bits > ; | | +| < EC Packet Control Acknowledgement 11 bit message > ::= | -- 11-bit access burst format | +| < MESSAGE_TYPE : bit (7) == 1110 111 > | | +| < DL_CC_EST : bit (4) > ; | | + +**Table 11.2.50.2: EC PACKET CONTROL ACKNOWLEDGEMENT information element details** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|---------|--|---------|-----------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------------------------------------------------------------|---------|---------------------------------------------------------------|---------|----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------|---------|-----------------------------------------------------------------| +| TLLI (32 bit field)
This field contains the TLLI of the mobile station. This field is encoded as defined in sub-clause 12.16. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CTRL_ACK (2 bit field)
This field contains acknowledgement information for the group of RLC/MAC control blocks that make up an RLC/MAC control message. The mobile station shall set the CTRL_ACK field to indicate which segments of an RLC/MAC control message have been received by the time of transmission of the EC PACKET CONTROL ACKNOWLEDGEMENT message. The CTRL_ACK field shall be set according to the following table:

bit
2 1
0 0 Reserved.
0 1 the MS received an RLC/MAC control block addressed to itself and with RBSN = 1, and did not receive an RLC/MAC control block with RBSN = 0 for the same RLC/MAC control message.
1 0 the MS received an RLC/MAC control block addressed to itself and with RBSN = 0, and did not receive an RLC/MAC control block with RBSN = 1 for the same RLC/MAC control message. This value is sent irrespective of the value of the FS bit.
1 1 the MS received two RLC/MAC blocks that contain different segments of the same RLC/MAC control message, one with RBSN = 0 and the other with RBSN = 1.
| bit | | 2 1 | | 0 0 | Reserved. | 0 1 | the MS received an RLC/MAC control block addressed to itself and with RBSN = 1, and did not receive an RLC/MAC control block with RBSN = 0 for the same RLC/MAC control message. | 1 0 | the MS received an RLC/MAC control block addressed to itself and with RBSN = 0, and did not receive an RLC/MAC control block with RBSN = 1 for the same RLC/MAC control message. This value is sent irrespective of the value of the FS bit. | 1 1 | the MS received two RLC/MAC blocks that contain different segments of the same RLC/MAC control message, one with RBSN = 0 and the other with RBSN = 1. | | | | | | | | | | | | | | | | | | | | | | | | | +| bit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 0 | Reserved. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 1 | the MS received an RLC/MAC control block addressed to itself and with RBSN = 1, and did not receive an RLC/MAC control block with RBSN = 0 for the same RLC/MAC control message. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 0 | the MS received an RLC/MAC control block addressed to itself and with RBSN = 0, and did not receive an RLC/MAC control block with RBSN = 1 for the same RLC/MAC control message. This value is sent irrespective of the value of the FS bit. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 1 | the MS received two RLC/MAC blocks that contain different segments of the same RLC/MAC control message, one with RBSN = 0 and the other with RBSN = 1. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| DL_CC_EST (4 bit field)
This field contains the latest downlink Coverage Class estimation and the latest estimated C value range in case the C value is above BT_Threshold_DL, see 3GPP TS 45.008. The BT_Threshold_DL value is broadcast in EC SI 2, see 3GPP TS 44.018. The DL_CC_EST field shall be set according to the following table:

bit
4 3 2 1
0 0 0 0 DL CC4
0 0 0 1 DL CC3
0 0 1 0 DL CC2
0 0 1 1 DL CC1; BT_Threshold_DL ≤ C Value < BT_Threshold_DL+3 dB
0 1 0 0 DL CC1; BT_Threshold_DL+3 dB ≤ C Value < BT_Threshold_DL+6 dB
0 1 0 1 DL CC1; BT_Threshold_DL+6 dB ≤ C Value < BT_Threshold_DL+9 dB
0 1 1 0 DL CC1; BT_Threshold_DL+9 dB ≤ C Value < BT_Threshold_DL+12 dB
0 1 1 1 DL CC1; BT_Threshold_DL+12 dB ≤ C Value < BT_Threshold_DL+15 dB
1 0 0 0 DL CC1; BT_Threshold_DL+15 dB ≤ C Value < BT_Threshold_DL+18 dB
1 0 0 1 DL CC1; BT_Threshold_DL+18 dB ≤ C Value < BT_Threshold_DL+21 dB
1 0 1 0 DL CC1; BT_Threshold_DL+21 dB ≤ C Value < BT_Threshold_DL+24 dB
1 0 1 1 DL CC1; BT_Threshold_DL+24 dB ≤ C Value < BT_Threshold_DL+27 dB
1 1 0 0 DL CC1; BT_Threshold_DL+27 dB ≤ C Value < BT_Threshold_DL+30 dB
1 1 0 1 DL CC1; BT_Threshold_DL+30 dB ≤ C Value < BT_Threshold_DL+33 dB
1 1 1 0 DL CC1; BT_Threshold_DL+33 dB ≤ C Value < BT_Threshold_DL+36 dB
1 1 1 1 DL CC1; BT_Threshold_DL+36 dB ≤ C Value < BT_Threshold_DL+39 dB
| bit | | 4 3 2 1 | | 0 0 0 0 | DL CC4 | 0 0 0 1 | DL CC3 | 0 0 1 0 | DL CC2 | 0 0 1 1 | DL CC1; BT_Threshold_DL ≤ C Value < BT_Threshold_DL+3 dB | 0 1 0 0 | DL CC1; BT_Threshold_DL+3 dB ≤ C Value < BT_Threshold_DL+6 dB | 0 1 0 1 | DL CC1; BT_Threshold_DL+6 dB ≤ C Value < BT_Threshold_DL+9 dB | 0 1 1 0 | DL CC1; BT_Threshold_DL+9 dB ≤ C Value < BT_Threshold_DL+12 dB | 0 1 1 1 | DL CC1; BT_Threshold_DL+12 dB ≤ C Value < BT_Threshold_DL+15 dB | 1 0 0 0 | DL CC1; BT_Threshold_DL+15 dB ≤ C Value < BT_Threshold_DL+18 dB | 1 0 0 1 | DL CC1; BT_Threshold_DL+18 dB ≤ C Value < BT_Threshold_DL+21 dB | 1 0 1 0 | DL CC1; BT_Threshold_DL+21 dB ≤ C Value < BT_Threshold_DL+24 dB | 1 0 1 1 | DL CC1; BT_Threshold_DL+24 dB ≤ C Value < BT_Threshold_DL+27 dB | 1 1 0 0 | DL CC1; BT_Threshold_DL+27 dB ≤ C Value < BT_Threshold_DL+30 dB | 1 1 0 1 | DL CC1; BT_Threshold_DL+30 dB ≤ C Value < BT_Threshold_DL+33 dB | 1 1 1 0 | DL CC1; BT_Threshold_DL+33 dB ≤ C Value < BT_Threshold_DL+36 dB | 1 1 1 1 | DL CC1; BT_Threshold_DL+36 dB ≤ C Value < BT_Threshold_DL+39 dB | +| bit | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 0 | DL CC4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 1 | DL CC3 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 0 1 0 | DL CC2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 0 1 1 | DL CC1; BT_Threshold_DL ≤ C Value < BT_Threshold_DL+3 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 1 0 0 | DL CC1; BT_Threshold_DL+3 dB ≤ C Value < BT_Threshold_DL+6 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 1 0 1 | DL CC1; BT_Threshold_DL+6 dB ≤ C Value < BT_Threshold_DL+9 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 1 1 0 | DL CC1; BT_Threshold_DL+9 dB ≤ C Value < BT_Threshold_DL+12 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 1 1 1 | DL CC1; BT_Threshold_DL+12 dB ≤ C Value < BT_Threshold_DL+15 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 0 0 0 | DL CC1; BT_Threshold_DL+15 dB ≤ C Value < BT_Threshold_DL+18 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 0 0 1 | DL CC1; BT_Threshold_DL+18 dB ≤ C Value < BT_Threshold_DL+21 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 0 1 0 | DL CC1; BT_Threshold_DL+21 dB ≤ C Value < BT_Threshold_DL+24 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 0 1 1 | DL CC1; BT_Threshold_DL+24 dB ≤ C Value < BT_Threshold_DL+27 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 1 0 0 | DL CC1; BT_Threshold_DL+27 dB ≤ C Value < BT_Threshold_DL+30 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 1 0 1 | DL CC1; BT_Threshold_DL+30 dB ≤ C Value < BT_Threshold_DL+33 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 1 1 0 | DL CC1; BT_Threshold_DL+33 dB ≤ C Value < BT_Threshold_DL+36 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 1 1 1 | DL CC1; BT_Threshold_DL+36 dB ≤ C Value < BT_Threshold_DL+39 dB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +### 11.2.51 EC Packet Downlink Ack/Nack + +This message is sent on the EC-PACCH from the mobile station to the network to indicate the status of downlink RLC data blocks received and to report the channel quality of the downlink. The mobile station may optionally initiate an uplink TBF by including the EC Channel Request Description in the message. + +Message type: EC Packet Downlink Ack/Nack + +Direction: mobile station to network + +**Table 11.2.5.1.1: EC PACKET DOWNLINK ACK/NACK information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < EC Packet Downlink Ack/Nack message content > ::=    < DOWNLINK_TFI : bit (5) >   < MS OUT OF MEMORY : bit(1) >   { 0 < EC Ack/Nack Description : < EC Ack/Nack Description IE >> -- Final Ack Indicator = 0     1 -- Final Ack Indicator = 1 }   { 0     1 { < EC Channel Quality Report : < EC Channel Quality Report IE > >         < DL_CC_EST : bit (4) > } }   { 0   1 < EC Channel Request Description : < EC Channel Request Description struct > > }   {     -- Rel-14 extension     { 0   1 < MS Transmission Offset : bit (4) >             < MS Sync Accuracy : bit (4) > }   }   <padding bits > ;  < EC Channel Request Description struct > ::=   < PRIORITY : bit (1) >   < NUMBER_OF_UL_DATA_BLOCKS : bit (4) > ;
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.5.1.2: EC PACKET DOWNLINK ACK/NACK information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

DOWNLINK_TFI (5 bit field)
This field contains the TFI of the mobile station's downlink TBF. This field is defined in sub-clause 12.15.

| +|

EC Ack/Nack Description IE
This information element is defined in sub-clause 12.72.

| +|

EC Channel Quality Report IE
This information element is defined in sub-clause 12.75.

| +|

MS OUT OF MEMORY (1 bit field)
This field indicates if the MS no more has enough memory to perform Incremental Redundancy.

  • 0 The MS has enough memory
  • 1 The MS is running out of memory
| + +**PRIORITY** + +This field indicates the priority of the transfer for which the mobile station is requesting uplink resources. + +- 0 Normal priority +- 1 High priority + +**NUMBER\_OF\_UL\_DATA\_BLOCKS** + +This field indicates the number of UL RLC Data blocks, using MCS-1, that are requested by the mobile station. The field is coded as shown in the following table: + +| bit | | +|---------|---------------------| +| 4 3 2 1 | | +| 0 0 0 0 | 1 RLC data block | +| 0 0 0 1 | 2 RLC data blocks | +| . . . | | +| 1 1 1 0 | 15 RLC data blocks | +| 1 1 1 1 | >15 RLC data blocks | + +--- + +**DL\_CC\_EST (4 bit field)** + +This field contains the latest downlink Coverage Class estimation and the latest estimated C value range in case the C value is above BT\_Threshold\_DL, see 3GPP TS 45.008. The BT\_Threshold\_DL value is broadcast in EC SI 2, see 3GPP TS 44.018. The DL\_CC\_EST field shall be set according to the following table: + +| bit | | +|---------|------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | DL CC4 | +| 0 0 0 1 | DL CC3 | +| 0 0 1 0 | DL CC2 | +| 0 0 1 1 | DL CC1; BT_Threshold_DL $\leq$ C Value $<$ BT_Threshold_DL+3 dB | +| 0 1 0 0 | DL CC1; BT_Threshold_DL+3 dB $\leq$ C Value $<$ BT_Threshold_DL+6 dB | +| 0 1 0 1 | DL CC1; BT_Threshold_DL+6 dB $\leq$ C Value $<$ BT_Threshold_DL+9 dB | +| 0 1 1 0 | DL CC1; BT_Threshold_DL+9 dB $\leq$ C Value $<$ BT_Threshold_DL+12 dB | +| 0 1 1 1 | DL CC1; BT_Threshold_DL+12 dB $\leq$ C Value $<$ BT_Threshold_DL+15 dB | +| 1 0 0 0 | DL CC1; BT_Threshold_DL+15 dB $\leq$ C Value $<$ BT_Threshold_DL+18 dB | +| 1 0 0 1 | DL CC1; BT_Threshold_DL+18 dB $\leq$ C Value $<$ BT_Threshold_DL+21 dB | +| 1 0 1 0 | DL CC1; BT_Threshold_DL+21 dB $\leq$ C Value $<$ BT_Threshold_DL+24 dB | +| 1 0 1 1 | DL CC1; BT_Threshold_DL+24 dB $\leq$ C Value $<$ BT_Threshold_DL+27 dB | +| 1 1 0 0 | DL CC1; BT_Threshold_DL+27 dB $\leq$ C Value $<$ BT_Threshold_DL+30 dB | +| 1 1 0 1 | DL CC1; BT_Threshold_DL+30 dB $\leq$ C Value $<$ BT_Threshold_DL+33 dB | +| 1 1 1 0 | DL CC1; BT_Threshold_DL+33 dB $\leq$ C Value $<$ BT_Threshold_DL+36 dB | +| 1 1 1 1 | DL CC1; BT_Threshold_DL+36 dB $\leq$ C Value $<$ BT_Threshold_DL+39 dB | + +--- + +**MS Transmission Offset (4 bit field)** + +If a downlink EC TBF is established using a downlink assignment message indicating ‘‘MS Transmission Offset’’ and ‘‘MS Sync Accuracy’’ parameters are needed then this field is included (see sub-clause 8.1.2.2a). It is coded as decribed in sub-clause 10.4.33. + +--- + +**MS Sync Accuracy (4 bit field)** + +If a downlink EC TBF is established using a downlink assignment message indicating ‘‘MS Transmission Offset’’ and ‘‘MS Sync Accuracy’’ parameters are needed then this field is included (see sub-clause 8.1.2.2a). It is coded as decribed in sub-clause 10.4.32. + +### 11.2.52 EC Packet Downlink Assignment + +This message is sent on the EC-PACCH by the network to the mobile station to assign resources for a downlink EC TBF. + +Frequency parameters received as part of this assignment message shall be valid until a new assignment is received or each TBF of the mobile station are terminated. + +Message type: EC PACKET DOWNLINK ASSIGNMENT + Direction: network to mobile station + Classification: non-distribution message + +**Table 11.2.52.1: EC PACKET DOWNLINK ASSIGNMENT information elements** + +``` +< EC Packet Downlink Assignment message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + { 0 < Global TFI : < Global TFI IE >> + { < CONTROL_ACK : bit (1) > + { 0 | 1 < Frequency Parameters : < Frequency Parameters struct >> } + < DL_COVERAGE_CLASS : bit (2) > + < STARTING_DL_TIMESLOT : bit (3) > + < TIMESLOT_MULTIPLICATOR : bit (3) > + < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + < UL_COVERAGE_CLASS : bit (2) > + < STARTING_UL_TIMESLOT_OFFSET : bit (2) > + { 0 | 1 < EC Packet Timing Advance : < EC Packet Timing Advance IE >> } + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + { 0 | 1 < GAMMA : bit (5) > + < ALPHA Enable : bit (1) > } + { + -- Rel-14 extension + { 0 | 1 < Multilateration Information Request : bit (1) > } + } + < padding bits > // -- truncation at end of message allowed, bits '0' assumed + ! < Non-distribution part error : bit (*) = < no string >> } + ! < Address information part error : bit (*) = < no string >> + ! < Message escape : { 1 } bit (*) = > } -- Extended for future changes + ! < Distribution part error : bit (*) = < no string >> ; + +< Frequency Parameters struct > ::= + < EC_MA_NUMBER : bit (5) > + < TSC : bit (3) > + < Primary TSC Set : bit (1) > ; +``` + +**Table 11.2.52.2: EC PACKET DOWNLINK ASSIGNMENT information element details** + +#### **USED\_DL\_COVERAGE\_CLASS (2 bit field)** + +This information element is defined in sub-clause 12.71. + +#### **Global TFI** + +This information element contains the TFI of one of the mobile station's downlink TBFs or uplink TBFs. This field is defined in sub-clause 12.10. + +#### **CONTROL\_ACK (1 bit field)** + +This field shall be set to '1' if the network establishes a new downlink TBF for the mobile station whose timer T3192 is running. Otherwise this field shall be set to '0'. + +#### **DL\_COVERAGE\_CLASS (2 bit field)** + +This field indicates the DL Coverage Class that is assigned for the DL EC TBF. The DL\_COVERAGE\_CLASS field shall be set according to the following table: + +bit + +2 1 + +0 0 DL Coverage Class = CC1 + +0 1 DL Coverage Class = CC2 + +1 0 DL Coverage Class = CC3 + +1 1 DL Coverage Class = CC4 + +#### **STARTING\_DL\_TIMESLOT (3 bit field)** + +This field defines the timeslot number of the lowest timeslot included in the downlink assignment for the DL EC TBF. The number of additional timeslots that are included in the downlink assignment for the TBF depends on the assigned DL Coverage Class and the Timeslot Multiplier setting. The assigned timeslots are contiguous, starting with the timeslot number indicated in the STARTING\_DL\_TIMESLOT field. The field is encoded according to the following table: + +| bit | | +|-------|-----------------------------------------------------| +| 3 2 1 | | +| 0 0 0 | Timeslot 0 is the lowest assigned downlink timeslot | +| 0 0 1 | Timeslot 1 is the lowest assigned downlink timeslot | +| 0 1 0 | Timeslot 2 is the lowest assigned downlink timeslot | +| 0 1 1 | Timeslot 3 is the lowest assigned downlink timeslot | +| 1 0 0 | Timeslot 4 is the lowest assigned downlink timeslot | +| 1 0 1 | Timeslot 5 is the lowest assigned downlink timeslot | +| 1 1 0 | Timeslot 6 is the lowest assigned downlink timeslot | +| 1 1 1 | Timeslot 7 is the lowest assigned downlink timeslot | + +A mobile station assigned CC2, CC3 or CC4 is always assigned 4 consecutive timeslots if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). Therefore only timeslot 0, 1, 2, 3 or 4 may be indicated as the lowest assigned downlink timeslot when the assignment is for CC2, CC3 or CC4 in the downlink. If the field EC\_Reduced\_PDCH\_Allocation is set to 1 a mobile station assigned CC2, CC3 or CC4 is always assigned the use of 2 consecutive timeslots and therefore only timeslot 0, 1, 2, 3, 4, 5 or 6 shall be indicated as the lowest assigned downlink timeslot. + +#### **TIMESLOT\_MULTIPLIER (3 bit field)** + +This field defines how many DL timeslots that the assignment contains when the assigned DL Coverage Class, according to the DL\_COVERAGE\_CLASS field, is CC1. The field is coded according to the following table: + +| bit | | +|-------|----------------------| +| 3 2 1 | | +| 0 0 0 | 1 timeslot assigned | +| 0 0 1 | 2 timeslots assigned | +| 0 1 0 | 3 timeslots assigned | +| 0 1 1 | 4 timeslots assigned | +| 1 0 0 | 5 timeslots assigned | +| 1 0 1 | 6 timeslots assigned | +| 1 1 0 | 7 timeslots assigned | +| 1 1 1 | 8 timeslots assigned | + +Values other than '000' can only be used if supported by the mobile station, as indicated by its multislots capability, see 3GPP TS 45.002. If the assigned downlink Coverage Class > CC1 (according to the DL\_COVERAGE\_CLASS field), the mobile station shall consider the TIMESLOT\_MULTIPLIER field as not valid. + +#### **UL\_COVERAGE\_CLASS (2 bit field)** + +This field indicates the UL Coverage Class that is assigned for transfer of uplink RLC/MAC control messages on the EC-PACCH during the DL EC TBF. The UL\_COVERAGE\_CLASS field shall be set according to the following table: + +| bit | | +|-----|-------------------------| +| 2 1 | | +| 0 0 | UL Coverage Class = CC1 | +| 0 1 | UL Coverage Class = CC2 | +| 1 0 | UL Coverage Class = CC3 | +| 1 1 | UL Coverage Class = CC4 | + +#### **EC Packet Timing Advance** + +This information element is defined in sub-clause 12.74. + +#### **STARTING\_UL\_TIMESLOT\_OFFSET (2 bit field)** + +This field defines the timeslot number of the lowest timeslot included in the allocation that is used for transfer of uplink RLC/MAC control messages on the EC-PACCH during the DL EC TBF. The number of additional timeslots that are included in the uplink allocation depends on the assigned UL Coverage Class. The allocated timeslots are contiguous, starting with the timeslot number indicated in the STARTING\_UL\_TIMESLOT\_OFFSET field. The STARTING\_UL\_TIMESLOT\_OFFSET field is encoded as an offset to the timeslot assigned with the STARTING\_DL\_TIMESLOT field. The encoding of the field is dependent of the value of the DL\_COVERAGE\_CLASS and UL\_COVERAGE\_CLASS fields in the same message. + +If both DL\_COVERAGE\_CLASS and UL\_COVERAGE\_CLASS > CC1, the same timeslots are assigned in both the uplink and the downlink directions. The STARTING\_UL\_TIMESLOT\_OFFSET field can then be considered as not valid by the mobile station. + +If DL\_COVERAGE\_CLASS = CC1 and UL\_COVERAGE\_CLASS > CC1, the STARTING\_UL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | +|-----|----------------------------------------------------| +| bit | | +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_DL_TIMESLOT | +| 0 1 | STARTING_DL_TIMESLOT - 1 | +| 1 0 | STARTING_DL_TIMESLOT - 2 | +| 1 1 | STARTING_DL_TIMESLOT - 3 | + +If DL\_COVERAGE\_CLASS > CC1 and UL\_COVERAGE\_CLASS = CC1, the STARTING\_UL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | +|-----|----------------------------------------------------| +| bit | | +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_DL_TIMESLOT | +| 0 1 | STARTING_DL_TIMESLOT + 1 | +| 1 0 | STARTING_DL_TIMESLOT + 2 | +| 1 1 | STARTING_DL_TIMESLOT + 3 | + +If both DL\_COVERAGE\_CLASS and UL\_COVERAGE\_CLASS = CC1, the uplink is assigned to the timeslot indicated by the STARTING\_DL\_TIMESLOT field. The STARTING\_UL\_TIMESLOT\_OFFSET field can then be considered as not valid by the mobile station. + +#### **P0 (4 bit field)** + +This field is an optional downlink power control parameter. It is encoded as follows: + +| | | +|---------|------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | P0 = 0 dB | +| 0 0 0 1 | P0 = 2 dB | +| 0 0 1 0 | P0 = 4 dB | +| : | | +| 1 1 1 1 | P0 = 30 dB | + +#### **PR\_MODE** (1 bit field) + +This field indicates the PR Management mode, as defined in 3GPP TS 45.008. The field is encoded as follows: + +- 0 PR mode A: for one addressed MS +- 1 PR mode B: for all MSs + +#### **GAMMA** (5 bit field) + +This field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +bit + +5 4 3 2 1 + +0 0 0 0 0 $\Gamma_{CH} = 0$ dB + +0 0 0 0 1 $\Gamma_{CH} = 2$ dB + +... + +1 1 1 1 0 $\Gamma_{CH} = 60$ dB + +1 1 1 1 1 $\Gamma_{CH} = 62$ dB + +#### **ALPHA Enable** (1 bit field) + +This field indicates whether or not the mobile station shall use the ALPHA parameter (if sent as part of EC SI) for uplink power control (see 3GPP TS 45.008 [34]). The field is coded as follows: + +- 0 The mobile station shall not use the ALPHA parameter +- 1 The mobile station shall use the ALPHA parameter + +#### **EC\_MA\_NUMBER** (5 bit field) + +This field indicates what EC Mobile Allocation set, as defined in the EC SYSTEM INFORMATION TYPE 1 message, the TBF is allocated to (see 3GPP TS 44.018 [11]). + +The field is encoded as a binary number with a range 0 to 31. + +#### **DOWNLINK\_TFI\_ASSIGNMENT** (5 bit field) + +This information element, if present, assigns the TFI to the mobile station to identify the downlink TBF described by this message. TFI is encoded as defined in sub-clause 12.15. + +#### **Primary TSC Set** (1 bit field) + +This field indicates to which TSC set the TSC field in the same message, for use on the assigned resources, shall be associated. This field is coded as follows: + +- 0 TSC set 1 +- 1 Indicates TSC set 2 for 8PSK modulation and TSC set 3 (which is identical to TSC set 3 used for the CS domain) for GMSK modulation. + +#### **Multilateration Information Request** (1 bit field) + +This field indicates whether or not a MS is to include “MS Transmission Offset” and “MS Sync Accuracy” parameters when sending an EC Packet Downlink Ack/Nack message (see sub-clause 11.2.51). This field can be included when establishing a downlink TBF to deliver a downlink LLC PDU for which the corresponding DL-UNITDATA PDU indicates timing advance information is needed (see 3GPP TS 48.018). This field is coded as follows: + +- 0 Do not include “MS Transmission Offset” and “MS Sync Accuracy” parameters +- 1 Include “MS Transmission Offset” and “MS Sync Accuracy” parameters + +### 11.2.53 EC Packet Downlink Dummy Control Block + +This message is sent on the EC-PACCH by the network to the mobile station as a fill message with just the USED\_DL\_COVERAGE\_CLASS parameter. + +Message type: EC PACKET DOWNLINK DUMMY CONTROL BLOCK + +Direction: network to mobile station + +Classification: distribution message + +**Table 11.2.53.1: EC PACKET DOWNLINK DUMMY CONTROL BLOCK information elements** + +``` +< EC Packet Downlink Dummy Control Block message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + < padding bits > + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.53.2: EC PACKET DOWNLINK DUMMY CONTROL BLOCK information element details** + +**USED\_DL\_COVERAGE\_CLASS** (2 bit field) +This information element is defined in sub-clause 12.71. + +### 11.2.54 EC Packet Polling Request + +This message is sent on the EC-PACCH by the network to the mobile station to solicit an EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message from the mobile station. + +Message type: EC PACKET POLLING REQUEST + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.54.1: EC PACKET POLLING REQUEST information elements** + +``` +< EC Packet Polling Request message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + { 0 < Global TFI : < Global TFI IE > > + { < TYPE_OF_ACK : bit (1) > + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > + ! < Message escape : { 1 } bit (*) = < no string > > } -- Extended for future changes + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.54.2: EC PACKET POLLING REQUEST information element details** + +**USED\_DL\_COVERAGE\_CLASS** (2 bit field) +This information element is defined in sub-clause 12.71. + +**Global TFI** +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +**TYPE\_OF\_ACK** +This field indicates the format of the EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message requested from the mobile station by the EC PACKET POLLING REQUEST message. + +0 EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message format shall be sent as four access bursts +1 EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message format shall be an RLC/MAC control block + +Depending on the UL Coverage Class assigned to the mobile station, the transmission of the EC PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC message shall be sent using a specific number of blind physical layer transmissions. This is valid both when the message format is four access bursts and when it is an RLC/MAC control block. + +### 11.2.55 EC Packet Power Control/Timing Advance + +This message is sent on EC-PACCH by the network to the mobile station in order to update the mobile station timing advance or power control parameters. + +Message type: EC PACKET POWER CONTROL/TIMING ADVANCE + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.55.1: EC PACKET POWER CONTROL/TIMING ADVANCE information elements** + +``` +< EC Packet Power Control/Timing Advance message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + { + < Global TFI : < Global TFI IE >> + { + { 0 | 1 < T_AVG_T : bit (5) > } + { 0 | 1 < EC Packet Timing Advance : < EC Packet Timing Advance IE >> } + { 0 | 1 < GAMMA : bit (5) > } + < padding bits > + ! < Non-distribution part error : bit (*) = < no string >> } + ! < Address information part error : bit (*) = < no string >> } + ! < Distribution part error : bit (*) = < no string >> ; + } + } + +``` + +**Table 11.2.55.2: EC PACKET POWER CONTROL/TIMING ADVANCE information element details** + +#### USED\_DL\_COVERAGE\_CLASS (2 bit field) + +This information element is defined in sub-clause 12.71. + +#### Global TFI IE + +This information element contains the TFI of the mobile station's downlink TBF or uplink TBF. This field is defined in sub-clause 12.10. + +#### T\_AVG\_T (5 bit field) + +The T\_AVG\_T parameter is a signal strength filter period for power control in packet transfer mode. $2^{(k/2)} / 6$ multiframes, $k = 0, 1, 2, \dots, 25$ (see 3GPP TS 45.008). Values greater than 25 shall be interpreted as 25 by the mobile station. + +#### EC Packet Timing Advance + +This information element is defined in sub-clause 12.74. + +#### GAMMA (5 bit field) + +This field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +| bit | | +|-----------|-----------------------| +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | +| ... | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | + +### 11.2.56 EC Packet TBF Release + +This message is sent on the EC-PACCH by the network to the mobile station to initiate release of an uplink or downlink EC TBF. + +Message type: EC PACKET TBF RELEASE + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.56.1: EC PACKET TBF RELEASE information elements** + +``` +< EC Packet TBF Release message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + { 0 < GLOBAL_TFI : Global TFI IE > + { < TBF_RELEASE_CAUSE : bit (4) = { 0000 | 0010 } > + { 0 | 1 < WAIT_INDICATION : bit (8) > + < WAIT_INDICATION_SIZE : bit (1) > } + < padding bits > + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > } + ! < Distribution part error : bit (*) = < no string > > ; +``` + +**Table 11.2.56.2: EC PACKET TBF RELEASE information element details** + +#### **USED\_DL\_COVERAGE\_CLASS (2 bit field)** + +This information element is defined in sub-clause 12.71. + +#### **Global TFI IE** + +This information element contains the TFI of uplink or downlink TBF that is to be released. This field is defined in sub-clause 12.10. + +#### **TBF\_RELEASE\_CAUSE (4 bit field)** + +This field indicates the reason for the release of the TBF. This field is encoded according to the following table: + +bit + +4 3 2 1 + +0 0 0 0 Normal release + +0 0 1 0 Abnormal release + +All other values are reserved, the same behaviour in reception as if 'Abnormal release'. + +#### **WAIT\_INDICATION (8 bit field)** + +The Wait Indication field indicates the time the mobile station shall wait before attempting another channel request. + +This field is coded as the binary representation of the T3172 timeout value in units of 20 ms or in units of seconds. The units are indicated in the WAIT\_INDICATION\_SIZE field. + +Range 0 to 255. + +#### **WAIT\_INDICATION\_SIZE (1 bit field)** + +This field indicates the units of the WAIT\_INDICATION field. + +0 the WAIT\_INDICATION field is coded in units of s + +1 the WAIT\_INDICATION field is coded in units of 20 ms + +### 11.2.57 EC Packet Uplink Ack/Nack + +This message is sent on the EC-PACCH by the network to the mobile station to indicate the status of the received RLC data blocks. This message may also include a fixed uplink allocation for the mobile station to (re)transmit not yet acknowledged/transmitted RLC Data blocks. This message may also update the timing advance and power control parameters. + +If the EGPRS Channel Coding Command parameter is not included in the message, the mobile station shall continue to use the previous EGPRS Modulation and Coding Scheme. + +Message type: EC PACKET UPLINK ACK/NACK + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.57.1: EC PACKET UPLINK ACK/NACK information elements** + +``` + +< EC Packet Uplink Ack/Nack message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + { + < UPLINK_TFI : bit (5) > + { 0 { -- Final Ack Indicator = 0 + { 00 < EC Ack/Nack Description : < EC Ack/Nack Description IE >> + | 01 { < CONTENTION_RESOLUTION_TLLI : bit (32) > + < EC Primary Ack/Nack Description : < EC Primary Ack/Nack Description IE >> } + | 10 { < CONTENTION_RESOLUTION_rTLLI : bit (4) > + < EC Primary Ack/Nack Description : < EC Primary Ack/Nack Description IE >> } } + } < PUAN Fixed Uplink Allocation : < PUAN Fixed Uplink Allocation struct > > + < RESEGMENT : bit (1) > + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >> } + { 0 | 1 < UL_COVERAGE_CLASS : bit (2) > + < STARTING_UL_TIMESLOT : bit (3) > + < DL_COVERAGE_CLASS : bit (2) > + < STARTING_DL_TIMESLOT_OFFSET : bit (2) > + < TIMESLOT_MULTIPLICATOR : bit (3) > } } + | 1 { -- Final Ack Indicator = 1 + { 0 + | 1 < CONTENTION_RESOLUTION_TLLI : bit (32) > } + { 0 -- the mobile station shall not continue monitoring the EC-PACCH + | 1 { < T3238 : bit (3) > -- the mobile station shall continue monitoring the EC-PACCH + < Initial Waiting Time : bit (2) > + < EC-PACCH Monitoring Pattern : bit (2) > } } } + { 0 | 1 < EC Packet Timing Advance : < EC Packet Timing Advance IE > > } + { 0 | 1 < GAMMA : bit (5) > + < ALPHA Enable : bit (1) > } + < UL_COVERAGE_CLASS_EXT : bit (1) > -- Rel-14 change support of uplink coverage class CC5 + < padding bits > } + ! < Non-distribution part error : bit (*) = > } + ! < Address information part error : bit (*) = > } + ! < Distribution part error : bit (*) = > ; + +< PUAN Fixed Uplink Allocation struct > ::= + { 0 | 1 < BSN_OFFSET : bit (2) > } + < START_FIRST_UL_RLC_DATA_BLOCK : bit (4) > + { 1 { 0 < DELAY_NEXT_UL_RLC_DATA_BLOCK : bit (3) > -- delay until start of next UL RLC Data block + | 1 } ** 0; -- next UL RLC Data block starts at first possible occasion after previous UL RLC Data block + } + +``` + +**Table 11.2.57.2: EC PACKET UPLINK ACK/NACK information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

USED_DL_COVERAGE_CLASS (2 bit field)

This information element is defined in sub-clause 12.71.

| +|

UPLINK_TFI (5 bit field)

This field identifies the uplink TBF to which this message applies. This field is coded the same as the TFI field defined in sub-clause 12.15.

| +|

EGPRS Modulation and Coding Scheme

The EGPRS Modulation and Coding Scheme information element is defined in sub-clause 12.10d.

| +|

RESEGMENT (1 bit field)

This field is defined in sub-clause 12.10e.

| +|

EC Ack/Nack Description IE

This information element is defined in sub-clause 12.72.

| +|

EC Primary Ack/Nack Description IE

This information element is defined in sub-clause 12.73.

| + +#### **UL\_COVERAGE\_CLASS (2 bit field)** + +This field indicates the new UL Coverage Class that is assigned for the UL EC TBF. The interpretation of the field is dependent on the field **UL\_COVERAGE\_CLASS\_EXT** (see further below). The **UL\_COVERAGE\_CLASS** field shall be set according to the following table in case **UL\_COVERAGE\_CLASS\_EXT = 0**: + +| bit | | | +|-----|---|-------------------------| +| 2 | 1 | | +| 0 | 0 | UL Coverage Class = CC1 | +| 0 | 1 | UL Coverage Class = CC2 | +| 1 | 0 | UL Coverage Class = CC3 | +| 1 | 1 | UL Coverage Class = CC4 | + +In case the UL Coverage Class is changed to CC1, the assignment is limited to 1 timeslot. + +The **UL\_COVERAGE\_CLASS** field shall be set according to the following table in case **UL\_COVERAGE\_CLASS\_EXT = 1**: + +| bit | | | +|-----|---|-------------------------| +| 2 | 1 | | +| 0 | 0 | UL Coverage Class = CC5 | +| 0 | 1 | reserved | +| 1 | 0 | reserved | +| 1 | 1 | reserved | + +#### **STARTING\_UL\_TIMESLOT (3 bit field)** + +This field defines the timeslot number of the lowest timeslot included in the uplink assignment for the UL EC TBF. The number of additional timeslots that are included in the uplink assignment for the TBF depends on the assigned UL Coverage Class. The assigned timeslots are contiguous, starting with the timeslot number indicated in the **STARTING\_UL\_TIMESLOT** field. The field is encoded according to the following table: + +| bit | | | | +|-----|---|---|---------------------------------------------------| +| 3 | 2 | 1 | | +| 0 | 0 | 0 | Timeslot 0 is the lowest assigned uplink timeslot | +| 0 | 0 | 1 | Timeslot 1 is the lowest assigned uplink timeslot | +| 0 | 1 | 0 | Timeslot 2 is the lowest assigned uplink timeslot | +| 0 | 1 | 1 | Timeslot 3 is the lowest assigned uplink timeslot | +| 1 | 0 | 0 | Timeslot 4 is the lowest assigned uplink timeslot | +| 1 | 0 | 1 | Timeslot 5 is the lowest assigned uplink timeslot | +| 1 | 1 | 0 | Timeslot 6 is the lowest assigned uplink timeslot | +| 1 | 1 | 1 | Timeslot 7 is the lowest assigned uplink timeslot | + +A mobile station assigned CC2, CC3 or CC4 is always assigned 4 consecutive timeslots if the field **EC\_Reduced\_PDCH\_Allocation** is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). Therefore only timeslot 0, 1, 2, 3 or 4 may be indicated as the lowest assigned uplink timeslot when the assignment is for CC2, CC3, CC4, or CC5 in the uplink. If the field **EC\_Reduced\_PDCH\_Allocation** is set to 1 a mobile station assigned CC2, CC3, CC4, or CC5 on the uplink is always assigned the use of 2 consecutive timeslots and therefore only timeslot 0, 1, 2, 3, 4, 5 or 6 shall be indicated as the lowest assigned uplink timeslot. + +#### **DL\_COVERAGE\_CLASS (2 bit field)** + +This field indicates the new DL Coverage Class that is assigned for transfer of downlink RLC/MAC control messages on the EC-PACCH during the UL EC TBF. The **DL\_COVERAGE\_CLASS** field shall be set according to the following table: + +| bit | | | +|-----|---|-------------------------| +| 2 | 1 | | +| 0 | 0 | DL Coverage Class = CC1 | +| 0 | 1 | DL Coverage Class = CC2 | +| 1 | 0 | DL Coverage Class = CC3 | +| 1 | 1 | DL Coverage Class = CC4 | + +#### **STARTING\_DL\_TIMESLOT\_OFFSET (2 bit field)** + +This field defines the timeslot number of the lowest timeslot included in the new assignment that is used for transfer of downlink RLC/MAC control messages on the EC-PACCH during the UL EC TBF. The number of additional timeslots that are included in the downlink assignment depends on the assigned DL Coverage Class. The assigned timeslots are contiguous, starting with the timeslot number indicated in the STARTING\_DL\_TIMESLOT\_OFFSET field. The STARTING\_DL\_TIMESLOT\_OFFSET field is encoded as an offset to the timeslot assigned with the STARTING\_UL\_TIMESLOT field. The encoding of the field is dependent of the value of the UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS fields in the same message. + +If both UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS > CC1, the same timeslots are assigned in both the uplink and the downlink directions. The STARTING\_DL\_TIMESLOT\_OFFSET field can then be considered as not valid by the mobile station. + +If UL\_COVERAGE\_CLASS = CC1 and DL\_COVERAGE\_CLASS > CC1, the STARTING\_DL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| bit | | +|-----|----------------------------------------------------| +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT - 1 | +| 1 0 | STARTING_UL_TIMESLOT - 2 | +| 1 1 | STARTING_UL_TIMESLOT - 3 | + +If UL\_COVERAGE\_CLASS > CC1 and DL\_COVERAGE\_CLASS = CC1, the STARTING\_DL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| bit | | +|-----|----------------------------------------------------| +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT + 1 | +| 1 0 | STARTING_UL_TIMESLOT + 2 | +| 1 1 | STARTING_UL_TIMESLOT + 3 | + +If both UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS = CC1, the downlink is assigned to the timeslot indicated by the STARTING\_UL\_TIMESLOT field. If timer T3248 (sent in EC SI) is used, the STARTING\_DL\_TIMESLOT\_OFFSET field defines the lowest assigned timeslot for EC-PACCH transfers using CC2 while the timer is running. The STARTING\_DL\_TIMESLOT\_OFFSET field is then encoded according to the following table: + +| bit | | +|-----|---------------------------------------------------------------------| +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT - 1 | +| 1 0 | STARTING_UL_TIMESLOT - 2 | +| 1 1 | no valid CC2 mapping applies while T3248 is running, CC1 to be used | + +#### **TIMESLOT\_MULTIPLICATOR (3 bit field)** + +This field defines how many UL timeslots that the assignment contains when the assigned UL Coverage Class, according to the UL\_COVERAGE\_CLASS field, is CC1. The field is coded according to the following table: + +| bit | | | +|-----|---|------------------------| +| 3 | 2 | 1 | +| 0 | 0 | 0 1 timeslot assigned | +| 0 | 0 | 1 2 timeslots assigned | +| 0 | 1 | 0 3 timeslots assigned | +| 0 | 1 | 1 4 timeslots assigned | +| 1 | 0 | 0 5 timeslots assigned | +| 1 | 0 | 1 6 timeslots assigned | +| 1 | 1 | 0 7 timeslots assigned | +| 1 | 1 | 1 8 timeslots assigned | + +Values other than '000' can only be used if supported by the mobile station, as indicated by its multislots capability, see 3GPP TS 45.002. If the assigned uplink Coverage Class > CC1 (according to the UL\_COVERAGE\_CLASS field), the mobile station shall consider the TIMESLOT\_MULTIPLICATOR field as not valid + +#### **T3238 (3 bit field)** + +This field is the binary representation of the timeout value of timer T3238. Range: 0 to 7. The timeout value is given as the binary value plus one in units of 1 second. + +#### **Initial Waiting Time (2 bit field)** + +This field gives the time that the mobile station shall wait, after the reception of this EC Packet Uplink Ack/Nack message, before it shall start to monitor the DL EC-PACCH. The waiting time is specified as the 52-multiframe, counted from the one containing the EC Packet Uplink Ack/Nack message, where the mobile station shall start monitoring the DL EC-PACCH. The field is coded according to the following table: + +| Bit | | +|-----|---------------------------------| +| 2 | 1 | +| 0 | 0 2 nd 52-multiframe | +| 0 | 1 4 th 52-multiframe | +| 1 | 0 6 th 52-multiframe | +| 1 | 1 8 th 52-multiframe | + +#### **EC-PACCH Monitoring Pattern (2 bit field)** + +The EC-PACCH Monitoring Pattern field indicates what pattern the mobile station shall use when monitoring the downlink EC-PACCH while timer T3238 is running. The pattern shall be applied after first monitoring the 52-multiframe as indicated by the Initial Waiting Time field. The EC-PACCH Monitoring Pattern field is coded according to the following table: + +| bit | | +|-----|-----------------------------------------------| +| 2 | 1 | +| 0 | 0 Continuous monitoring | +| 0 | 1 Monitor every 2 nd 52-multiframe | +| 1 | 0 Monitor every 4 th 52-multiframe | +| 1 | 1 Monitor every 8 th 52-multiframe | + +#### **CONTENTION\_RESOLUTION\_TLLI (32 bit field)** + +The CONTENTION\_RESOLUTION\_TLLI field is present only if the network has decoded one of the uplink RLC data blocks containing the TLLI. The mobile station shall perform the contention resolution function if the TLLI information element is present. This field contains a TLLI, which is defined in sub-clause 12.16. + +#### **CONTENTION\_RESOLUTION\_rTLLI (4 bit field)** + +The CONTENTION\_RESOLUTION\_rTLLI field is present only if the network has decoded one of the uplink RLC data blocks containing the rTLLI, and not any uplink RLC data block containing the TLLI. This field contains an rTLLI, which consists of the 4 least significant bits of the TLLI. + +#### **EC Packet Timing Advance** + +This information element is defined in sub-clause 12.74. + +#### **GAMMA (5 bit field)** + +This field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +| bit | | +|-----------|-----------------------| +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | +| ... | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | + +#### **ALPHA Enable (1 bit field)** + +This field indicates whether or not the mobile station shall use the ALPHA parameter (if sent as part of EC SI) for uplink power control (see 3GPP TS 45.008 [34]). The field is coded as follows: + +| | | +|---|------------------------------------------------------| +| 0 | The mobile station shall not use the ALPHA parameter | +| 1 | The mobile station shall use the ALPHA parameter | + +#### **UL\_COVERAGE\_CLASS\_EXT (1 bit field)** + +This field indicates how the field UL\_COVERAGE\_CLASS(see above) is to be interpreted and is coded as follows + +| bit | | +|-----|---------------------------------------------------------------------------------------------------------| +| 0 | UL_COVERAGE_CLASS field indicates one of UL Coverage Class CC1, CC2, CC3 or CC4 are assigned for uplink | +| 1 | UL_COVERAGE_CLASS field indicates UL Coverage Class CC5 is assigned for uplink | + +#### **BSN\_OFFSET (2 bit field)** + +This field defines the offset, in the list of available RLC Data blocks for transmission, that shall be applied by the mobile station when selecting the RLC Data blocks to transmit in the fixed uplink allocation. If the BSN\_OFFSET field is not present, the mobile station shall select the RLC Data blocks to transmit in the resources within the fixed uplink allocation as described in sub-clause 9.1.3.4. It shall e.g. start with the oldest NACKED block, if available, in the resources for the first RLC Data block within the fixed uplink allocation. If the BSN\_OFFSET field is present, the mobile station shall apply an offset in RLC Data blocks and skip one, or several, of the RLC Data blocks that would be transmitted first according to the procedures in sub-clause 9.1.3.4. This field is encoded according to the following table: + +| bit | | +|-----|-----------------------------------------------------------------------------------------------------------------------------| +| 2 1 | | +| 0 0 | Start with the 2 nd oldest RLC Data, to be transmitted, in the first resource within the fixed uplink allocation | +| 0 1 | Start with the 3 rd oldest RLC Data, to be transmitted, in the first resource within the fixed uplink allocation | +| 1 0 | Start with the 4 th oldest RLC Data, to be transmitted, in the first resource within the fixed uplink allocation | +| 1 1 | Start with the 5 th oldest RLC Data, to be transmitted, in the first resource within the fixed uplink allocation | + +#### **START\_FIRST\_UL\_RLC\_DATA\_BLOCK (4 bit field)** + +This field indicates the starting position of the resources for the first allocated RLC Data block in the fixed uplink allocation. The starting position is relative to the first TDMA frame (N) of the downlink block containing the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message, according to the USED\_DL\_COVERAGE\_CLASS field. The encoding of the field is dependent of the uplink Coverage Class and TIMESLOT\_MULTIPLICATOR assigned for the uplink EC TBF. + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 0 or if uplink Coverage Class = CC2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|----------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+17 or N+18) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+21 or N+22) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+26) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+30 or N+31) mod 2715648 | +| ... | | + +1 1 1 0 In the TDMA frame (N+73 or N+74) mod 2715648 + 1 1 1 1 In the TDMA frame (N+78) mod 2715648 + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 1, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + 4 3 2 1 + 0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 0 1 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + 0 0 1 0 In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + 0 0 1 1 In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 + .... + 1 1 1 0 In the timeslot with the lowest TN in TDMA frame (N+43 or N+44) mod 2715648 + 1 1 1 1 In the timeslot with the highest TN in TDMA frame (N+43 or N+44) mod 2715648 + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + 4 3 2 1 + 0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 1 0 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + 0 0 1 1 In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + 0 1 0 0 In the timeslot with the 2nd lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + 0 1 0 1 In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 + .... + 1 1 1 0 In the timeslot with the highest TN in TDMA frame (N+30 or N+31) mod 2715648 + 1 1 1 1 In the timeslot with the lowest TN in TDMA frame (N+34 or N+35) mod 2715648 + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 3, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + 4 3 2 1 + 0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 1 1 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + 0 1 0 0 In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + 0 1 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + .... + 1 1 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+26) mod 2715648 + 1 1 1 1 In the timeslot with the highest TN in TDMA frame (N+26) mod 2715648 + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 4, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + 4 3 2 1 + 0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+13) mod 2715648 + 0 0 1 1 In the timeslot with the 4th lowest TN in TDMA frame (N+13) mod 2715648 + 0 1 0 0 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + 0 1 0 1 In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + .... + 1 1 1 0 In the timeslot with the highest TN in TDMA frame (N+21 or N+22) mod 2715648 + 1 1 1 1 In the timeslot with the lowest TN in TDMA frame (N+26) mod 2715648 + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 5, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|---------------------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 5 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | +| 1 1 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 6, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|---------------------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 5 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the 6 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 0 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 1 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | +| 1 1 1 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 7, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|---------------------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 5 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the 6 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 0 | In the timeslot with the 7 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 1 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the 7 th lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 1 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 | + +If uplink Coverage Class = CC3 and the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018) or if uplink Coverage Class = CC2 and the field EC\_Reduced\_PDCH\_Allocation is set to 1, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|----------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 | + +| | | +|---------|--------------------------------------------------------------------------------| +| 1 1 1 0 | In the TDMA frame (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 | + +If uplink Coverage Class = CC4 and the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018) or if uplink Coverage Class = CC3 and the field EC\_Reduced\_PDCH\_Allocation is set to 1, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 or (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 | +| 1 1 1 0 | In the TDMA frame (N+255 or N+256) mod 2715648 or (N+260) mod 2715648 or (N+264 or N+265) mod 2715648 or (N+268 or N+269) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+273) mod 2715648 or (N+277 or N+278) mod 2715648 or (N+281 or N+282) mod 2715648 or (N+286) mod 2715648 | + +If uplink Coverage Class = CC4 and the field EC\_Reduced\_PDCH\_Allocation is set to 1 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018), the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 or (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 or (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 or (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 or (N+99 or N+100) mod 2715648 or (N+104) mod 2715648 or (N+108 or N+109) mod 2715648 or (N+112 or N+113) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+117) mod 2715648 or (N+121 or N+122) mod 2715648 or (N+125 or N+126) mod 2715648 or (N+130) mod 2715648 or (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 or (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+151 or N+152) mod 2715648 or (N+156) mod 2715648 or (N+160 or N+161) mod 2715648 or (N+164 or N+165) mod 2715648 or (N+169) mod 2715648 or (N+173 or N+174) mod 2715648 or (N+177 or N+178) mod 2715648 or (N+182) mod 2715648 | +| 1 1 1 0 | In the TDMA frame (N+464 or N+465) mod 2715648 or (N+468) mod 2715648 or (N+472 or N+473) mod 2715648 or (N+477 or N+478) mod 2715648 or (N+481) mod 2715648 or (N+485 or N+486) mod 2715648 or (N+490 or N+491) mod 2715648 or (N+494) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+498 or N+499) mod 2715648 or (N+503 or N+504) mod 2715648 or (N+507) mod 2715648 or (N+511 or N+512) mod 2715648 or (N+516 or N+517) mod 2715648 or (N+520) mod 2715648 or (N+524 or N+525) mod 2715648 or (N+529 or N+530) mod 2715648 | + +If uplink Coverage Class = CC5, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +If uplink Coverage Class = CC5 and the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018), the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 0 0 | The 1 st uplink 52-multiframe occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 0 0 0 1 | The 2 nd uplink 52-multiframe occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| .... | | +| 0 1 1 1 | The 8 th uplink 52-multiframe occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 1 0 0 0 to 1 1 1 1 | Not Applicable | +| If uplink Coverage Class = CC5 and the field EC_Reduced_PDCH_Allocation is set to 1 the START_FN_FIRST_UL_RLC_DATA_BLOCK field is encoded according to the following table: | | +| 0 0 0 0 | The 1 st pair of uplink 52-multiframes occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 0 0 0 1 | The 2 nd pair of uplink 52-multiframes occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| .... | | +| 0 1 1 1 | The 8 th pair of uplink 52-multiframes occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 1 0 0 0 to 1 1 1 1 | Not Applicable | + +#### **DELAY\_NEXT\_UL\_RLC\_DATA\_BLOCK (3 bit field)** + +This field indicates the position of the next allocated RLC Data block in the fixed uplink allocation. The position is calculated as the number of transmission opportunities from the previous uplink allocation, according to the assigned UL\_COVERAGE\_CLASS and TIMESLOT\_MULTIPLICATOR, where the next uplink allocation for the mobile station is placed and where the mobile station shall transmit the next UL RLC data block. In the transmission opportunity or opportunities between the previous uplink allocation and this allocation the mobile station is not allocated any resource, and shall thus not transmit. + +This field is encoded according to the following table: + +| bit | | +|-------|------------------------------------------------------| +| 3 | 2 | +| 1 | | +| 0 0 0 | In the 2 nd next transmission opportunity | +| 0 0 1 | In the 3 rd next transmission opportunity | +| 0 1 0 | In the 4 th next transmission opportunity | +| .... | | +| 1 1 0 | In the 8 th next transmission opportunity | +| 1 1 1 | In the 9 th next transmission opportunity | + +### 11.2.58 EC Packet Uplink Assignment + +This message is sent on the EC-PACCH by the network to the mobile station to assign an uplink EC TBF, including a fixed uplink allocation. Frequency parameters received as part of this assignment message shall be valid until a new assignment is received or until each TBF of the mobile station is terminated. + +If the EGPRS Channel Coding Command parameter is not included in the message, the mobile station is commanded to use MCS-1. + +Message type: EC PACKET UPLINK ASSIGNMENT + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.58.1: EC PACKET UPLINK ASSIGNMENT information elements** + +``` + +< EC Packet Uplink Assignment message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + { 0 < Global TFI : < Global TFI IE >> + { { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >> } + < OVERLAID_CDMA_CODE : bit (2) > + { 0 | 1 < EC Packet Timing Advance : < EC Packet Timing Advance IE >> } + { 0 | 1 < Frequency Parameters : < Frequency Parameters struct > > } + < UL_COVERAGE_CLASS : bit (2) > + < STARTING_UL_TIMESLOT : bit (3) > + < TIMESLOT_MULTIPLICATOR : bit (3) > + < Fixed Uplink Allocation : < Fixed Uplink Allocation struct > > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + { 0 | 1 < GAMMA : bit (5) > + < ALPHA Enable : bit (1) > } + < DL_COVERAGE_CLASS : bit (2) > + < STARTING_DL_TIMESLOT_OFFSET : bit (2) > + < UL COVERAGE CLASS EXT : bit (1) > -- Rel-14 change indicate UL CC5 support + < padding bits > // -- truncation at end of message allowed, bits '0' assumed + ! < Non-distribution part error : bit (*) = < no string > > } + ! < Address information part error : bit (*) = < no string > > + ! < Message escape : { 1 } bit (*) = < no string > > } -- Extended for future changes + ! < Distribution part error : bit (*) = < no string > > ; + +< Frequency Parameters struct > ::= + < EC_MA_NUMBER : bit (5) > + < TSC : bit (3) > + < Primary TSC Set : bit (1) > ; + +< Fixed Uplink Allocation struct > ::= + < START_FIRST_UL_RLC_DATA_BLOCK : bit (4) > + { 1 { + 0 < DELAY_NEXT_UL_RLC_DATA_BLOCK : bit (3) > -- delay until start of next UL RLC Data block + | 1 -- next UL RLC Data block starts at first possible occasion after previous UL RLC Data block } } ** 0; + +``` + +**Table 11.2.58.2: EC PACKET UPLINK ASSIGNMENT information element details** + +**USED\_DL\_COVERAGE\_CLASS (2 bit field)** + This information element is defined in sub-clause 12.71. + +**Global TFI** + This information element identifies the uplink TFI, if available, or the downlink TFI, to which this message applies. This field is defined in sub-clause 12.10. + +**EGPRS Modulation and Coding Scheme** + The EGPRS Modulation and Coding Scheme information element is defined in sub-clause 12.10d. + +**OVERLAID\_CDMA\_CODE (2 bit field)** + The Overlaid CDMA Code field indicates the Overlaid CDMA Code that shall be used at transmissions during the uplink EC TBF, see 3GPP TS 45.002. This field is encoded as following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | | +|-----|---|----------------------| +| bit | | | +| 2 | 1 | | +| 0 | 0 | Overlaid CDMA Code 0 | +| 0 | 1 | Overlaid CDMA Code 1 | +| 1 | 0 | Overlaid CDMA Code 2 | +| 1 | 1 | Overlaid CDMA Code 3 | + +Note: Overlaid CDMA Code 0 corresponds to that the bursts are transmitted as if no code was applied. + +#### **UPLINK\_TFI\_ASSIGNMENT** (5 bit field) + +This information element, if present, assigns the contained TFI to the mobile station to identify the uplink TBF described by this message. This field is coded the same as the TFI field defined in sub-clause 12.15. + +#### **EC Packet Timing Advance** + +This information element is defined in sub-clause 12.74. + +#### **EC\_MA\_NUMBER** (5 bit field) + +This field indicates what EC Mobile Allocation set, as defined in the EC SYSTEM INFORMATION TYPE 1 message, the TBF is allocated to (see 3GPP TS 44.018 [11]). + +The field is encoded as a binary number with a range 0 to 31. + +#### **UL\_COVERAGE\_CLASS** (2 bit field) + +This field indicates the UL Coverage Class that is assigned for the UL EC TBF. The interpretation of the field is dependent on the field **UL\_COVERAGE\_CLASS\_EXT** (see further below). The **UL\_COVERAGE\_CLASS** field shall be set according to the following table in case **UL\_COVERAGE\_CLASS\_EXT** = 0: + +bit + +2 1 + +0 0 UL Coverage Class = CC1 + +0 1 UL Coverage Class = CC2 + +1 0 UL Coverage Class = CC3 + +1 1 UL Coverage Class = CC4 + +The **UL\_COVERAGE\_CLASS** field shall be set according to the following table in case + +**UL\_COVERAGE\_CLASS\_EXT** = 1: + +bit + +2 1 + +0 0 UL Coverage Class = CC5 + +0 1 reserved + +1 0 reserved + +1 1 reserved + +#### **STARTING\_UL\_TIMESLOT** (3 bit field) + +This field defines the timeslot number of the lowest timeslot included in the uplink assignment for the UL EC TBF. The number of additional timeslots that are included in the uplink assignment for the TBF depends on the assigned UL Coverage Class and the Timeslot Multiplier setting. The assigned timeslots are contiguous, starting with the timeslot number indicated in the **STARTING\_UL\_TIMESLOT** field. The field is encoded according to the following table: + +bit + +3 2 1 + +0 0 0 Timeslot 0 is the lowest assigned uplink timeslot + +0 0 1 Timeslot 1 is the lowest assigned uplink timeslot + +0 1 0 Timeslot 2 is the lowest assigned uplink timeslot + +0 1 1 Timeslot 3 is the lowest assigned uplink timeslot + +1 0 0 Timeslot 4 is the lowest assigned uplink timeslot + +1 0 1 Timeslot 5 is the lowest assigned uplink timeslot + +1 1 0 Timeslot 6 is the lowest assigned uplink timeslot + +1 1 1 Timeslot 7 is the lowest assigned uplink timeslot + +A mobile station assigned CC2, CC3 or CC4 is always assigned 4 consecutive timeslots if the field + +**EC\_Reduced\_PDCH\_Allocation** is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018). Therefore only timeslot 0, 1, 2, 3 or 4 may be indicated as the lowest assigned uplink timeslot when the + +assignment is for CC2, CC3, CC4 or CC5 in the uplink. If the field **EC\_Reduced\_PDCH\_Allocation** is set to 1 a mobile station assigned CC2, CC3, CC4 or CC5 is always assigned 2 consecutive timeslots and therefore only a timeslot other than 7, i.e 0 to 6, shall be indicated as the lowest assigned uplink timeslot. + +#### **TIMESLOT\_MULTIPLICATOR** (3 bit field) + +This field defines how many UL timeslots that the assignment contains when the assigned UL Coverage Class, according to the UL\_COVERAGE\_CLASS field, is CC1. The field is coded according to the following table: + +| bit | | +|-------|----------------------| +| 3 2 1 | | +| 0 0 0 | 1 timeslot assigned | +| 0 0 1 | 2 timeslots assigned | +| 0 1 0 | 3 timeslots assigned | +| 0 1 1 | 4 timeslots assigned | +| 1 0 0 | 5 timeslots assigned | +| 1 0 1 | 6 timeslots assigned | +| 1 1 0 | 7 timeslots assigned | +| 1 1 1 | 8 timeslots assigned | + +Values other than '000' can only be used if supported by the mobile station, as indicated by its multislot capability, see 3GPP TS 45.002. If the assigned uplink Coverage Class > CC1 (according to the UL\_COVERAGE\_CLASS field), the mobile station shall consider the TIMESLOT\_MULTIPLICATOR field as not valid + +#### **START\_FIRST\_UL\_RLC\_DATA\_BLOCK** (4 bit field) + +This field indicates the starting position of the resources for the first allocated RLC Data block in the fixed uplink allocation. The starting position is relative to the first TDMA frame (N) of the downlink block containing the last blind physical layer transmission of this EC PACKET UPLINK ASSIGNMENT message, according to the USED\_DL\_COVERAGE\_CLASS field. The encoding of the field is dependent of the value of the UL\_COVERAGE\_CLASS and the TIMESLOT\_MULTIPLICATOR fields in the same message. + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 0 or if UL\_COVERAGE\_CLASS = CC2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|----------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+17 or N+18) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+21 or N+22) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+26) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+30 or N+31) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+73 or N+74) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+78) mod 2715648 | + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 1, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 0 0 1 1 | In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the lowest TN in TDMA frame (N+43 or N+44) mod 2715648 | +| 1 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+43 or N+44) mod 2715648 | + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|---------------------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | + +0 1 0 1 In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 + +.... + +1 1 1 0 In the timeslot with the highest TN in TDMA frame (N+30 or N+31) mod 2715648 + +1 1 1 1 In the timeslot with the lowest TN in TDMA frame (N+34 or N+35) mod 2715648 + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 3, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + +4 3 2 1 + +0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 1 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + +0 1 0 0 In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + +0 1 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + +.... + +1 1 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+26) mod 2715648 + +1 1 1 1 In the timeslot with the highest TN in TDMA frame (N+26) mod 2715648 + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 4, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + +4 3 2 1 + +0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 1 In the timeslot with the 4th lowest TN in TDMA frame (N+13) mod 2715648 + +0 1 0 0 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + +0 1 0 1 In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + +.... + +1 1 1 0 In the timeslot with the highest TN in TDMA frame (N+21 or N+22) mod 2715648 + +1 1 1 1 In the timeslot with the lowest TN in TDMA frame (N+26) mod 2715648 + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 5, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + +4 3 2 1 + +0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 1 In the timeslot with the 4th lowest TN in TDMA frame (N+13) mod 2715648 + +0 1 0 0 In the timeslot with the 5th lowest TN in TDMA frame (N+13) mod 2715648 + +0 1 0 1 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + +0 1 1 0 In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 + +.... + +1 1 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+21 or N+22) mod 2715648 + +1 1 1 1 In the timeslot with the 4th lowest TN in TDMA frame (N+21 or N+22) mod 2715648 + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 6, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +bit + +4 3 2 1 + +0 0 0 0 In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 0 1 In the timeslot with the 2nd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 0 In the timeslot with the 3rd lowest TN in TDMA frame (N+13) mod 2715648 + +0 0 1 1 In the timeslot with the 4th lowest TN in TDMA frame (N+13) mod 2715648 + +0 1 0 0 In the timeslot with the 5th lowest TN in TDMA frame (N+13) mod 2715648 + +0 1 0 1 In the timeslot with the 6th lowest TN in TDMA frame (N+13) mod 2715648 + +0 1 1 0 In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 + +| | | +|---------|---------------------------------------------------------------------------------------------| +| 0 1 1 1 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | +| 1 1 1 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | + +If UL\_COVERAGE\_CLASS = CC1 and TIMESLOT\_MULTIPLICATOR = 7, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|---------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 5 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the 6 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 0 | In the timeslot with the 7 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 1 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the 7 th lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 1 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 | + +If UL\_COVERAGE\_CLASS = CC3 and EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 3GPP TS 44.018), or, if the field EC\_Reduced\_PDCH\_Allocation is set to 1 and UL\_COVERAGE\_CLASS = CC2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|--------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 | + +If UL\_COVERAGE\_CLASS = CC4 and EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 3GPP TS 44.018), or, if the field EC\_Reduced\_PDCH\_Allocation is set to 1 and UL\_COVERAGE\_CLASS = CC3, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 or (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+255 or N+256) mod 2715648 or (N+260) mod 2715648 or (N+264 or N+265) mod 2715648 or (N+268 or N+269) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+273) mod 2715648 or (N+277 or N+278) mod 2715648 or (N+281 or N+282) mod 2715648 or (N+286) mod 2715648 | + +If UL\_COVERAGE\_CLASS = CC4 and EC\_Reduced\_PDCH\_Allocation is set to 1 in the EC SYSTEM + +INFORMATION TYPE 2 message (see 3GPP TS 44.018), the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 or (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 or (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 or (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 or (N+99 or N+100) mod 2715648 or (N+104) mod 2715648 or (N+108 or N+109) mod 2715648 or (N+112 or N+113) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+117) mod 2715648 or (N+121 or N+122) mod 2715648 or (N+125 or N+126) mod 2715648 or (N+130) mod 2715648 or (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 or (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+151 or N+152) mod 2715648 or (N+156) mod 2715648 or (N+160 or N+161) mod 2715648 or (N+164 or N+165) mod 2715648 or (N+169) mod 2715648 or (N+173 or N+174) mod 2715648 or (N+177 or N+178) mod 2715648 or (N+182) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+464 or N+465) mod 2715648 or (N+468) mod 2715648 or (N+472 or N+473) mod 2715648 or (N+477 or N+478) mod 2715648 or (N+481) mod 2715648 or (N+485 or N+486) mod 2715648 or (N+490 or N+491) mod 2715648 or (N+494) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+498 or N+499) mod 2715648 or (N+503 or N+504) mod 2715648 or (N+507) mod 2715648 or (N+511 or N+512) mod 2715648 or (N+516 or N+517) mod 2715648 or (N+520) mod 2715648 or (N+524 or N+525) mod 2715648 or (N+529 or N+530) mod 2715648 | + +If uplink Coverage Class = CC5, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +If uplink Coverage Class = CC5 and the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018), the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 0 0 | The 1 st uplink 52-multiframe occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 0 0 0 1 | The 2 nd uplink 52-multiframe occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| .... | | +| 0 1 1 1 | The 8 th uplink 52-multiframe occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 1 0 0 0 to 1 1 1 1 | Not Applicable | + +If uplink Coverage Class = CC5 and the field EC\_Reduced\_PDCH\_Allocation is set to 1 the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 0 0 | The 1 st pair of uplink 52-multiframes occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 0 0 0 1 | The 2 nd pair of uplink 52-multiframes occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| .... | | +| 0 1 1 1 | The 8 th pair of uplink 52-multiframes occurring after the downlink 52-multiframe used to send the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK message | +| 1 0 0 0 to 1 1 1 1 | Not Applicable | + +#### **DELAY\_NEXT\_UL\_RLC\_DATA\_BLOCK** (3 bit field) + +This field indicates the position of the next allocated RLC Data block in the fixed uplink allocation. The position is calculated as the number of transmission opportunities from the previous uplink allocation, according to the UL\_COVERAGE\_CLASS and TIMESLOT\_MULTIPLICATOR fields in the same assignment message, where the next uplink allocation for the mobile station is placed and where the mobile station thus shall transmit the next RLC data block. In the transmission opportunity/ies between the previous uplink allocation and this allocation the mobile station is not allocated any resource, and shall thus not transmit. + +This field is encoded according to the following table: + +| bit | | +|-------|------------------------------------------------------| +| 3 2 1 | | +| 0 0 0 | In the 2 nd next transmission opportunity | +| 0 0 1 | In the 3 rd next transmission opportunity | +| 0 1 0 | In the 4 th next transmission opportunity | +| .... | | +| 1 1 0 | In the 8 th next transmission opportunity | +| 1 1 1 | In the 9 th next transmission opportunity | + +#### **GAMMA** (5 bit field) + +This field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +| bit | | +|-----------|-----------------------| +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | +| .... | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | + +#### **ALPHA Enable** (1 bit field) + +This field indicates whether or not the mobile station shall use the ALPHA parameter (if sent as part of EC SI) for uplink power control (see 3GPP TS 45.008 [34]). The field is coded as follows: + +| | | +|---|------------------------------------------------------| +| 0 | The mobile station shall not use the ALPHA parameter | +| 1 | The mobile station shall use the ALPHA parameter | + +#### **P0** (4 bit field) + +This field is an optional downlink power control parameter. It is encoded as follows: + +| bit | | +|---------|---------------| +| 4 3 2 1 | | +| 0 0 0 0 | $P_0 = 0$ dB | +| 0 0 0 1 | $P_0 = 2$ dB | +| 0 0 1 0 | $P_0 = 4$ dB | +| ... | | +| 1 1 1 1 | $P_0 = 30$ dB | + +#### **PR\_MODE** (1 bit field) + +This field indicates the PR Management mode, as defined in 3GPP TS 45.008. The field is encoded as follows: + +| | | +|---|---------------------------------| +| 0 | PR mode A: for one addressed MS | +| 1 | PR mode B: for all MSs | + +#### **Primary TSC Set (1 bit field)** + +This field indicates to which TSC set the TSC field in the same message, for use on the assigned resources, shall be associated. This field is coded as follows: + +- 0 TSC set 1 +- 1 Indicates TSC set 2 for 8PSK modulation and TSC set 3 (which is identical to TSC set 3 used for the CS domain) for GMSK modulation. + +#### **DL\_COVERAGE\_CLASS (2 bit field)** + +This field indicates the DL Coverage Class that is assigned for transfer of downlink RLC/MAC control messages on the EC-PACCH during the UL EC TBF. The DL\_COVERAGE\_CLASS field shall be set according to the following table: + +| bit | | +|-----|-------------------------| +| 2 | 1 | +| 0 0 | DL Coverage Class = CC1 | +| 0 1 | DL Coverage Class = CC2 | +| 1 0 | DL Coverage Class = CC3 | +| 1 1 | DL Coverage Class = CC4 | + +#### **STARTING\_DL\_TIMESLOT\_OFFSET (2 bit field)** + +This field defines the timeslot number of the lowest timeslot included in the assignment that is used for transfer of downlink RLC/MAC control messages on the EC-PACCH during the UL EC TBF. The number of additional timeslots that are included in the downlink assignment depends on the assigned DL Coverage Class. The assigned timeslots are contiguous, starting with the timeslot number indicated in the STARTING\_DL\_TIMESLOT\_OFFSET field. The STARTING\_DL\_TIMESLOT\_OFFSET field is encoded as an offset to the timeslot assigned with the STARTING\_UL\_TIMESLOT field. The encoding of the field is dependent of the value of the UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS fields in the same message. + +If both UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS > CC1, the same timeslots are assigned in both the uplink and the downlink directions. The STARTING\_DL\_TIMESLOT\_OFFSET field can then be considered as not valid by the mobile station. + +If UL\_COVERAGE\_CLASS = CC1 and DL\_COVERAGE\_CLASS > CC1, the STARTING\_DL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | +|-----|----------------------------------------------------| +| bit | | +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT - 1 | +| 1 0 | STARTING_UL_TIMESLOT - 2 | +| 1 1 | STARTING_UL_TIMESLOT - 3 | + +If UL\_COVERAGE\_CLASS > CC1 and DL\_COVERAGE\_CLASS = CC1, the STARTING\_DL\_TIMESLOT\_OFFSET field is encoded according to the following code points if the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message (see 44.018 sub-clause 9.1.43q). If the field EC\_Reduced\_PDCH\_Allocation is set to 1 only the first two code points of the following shall be used: + +| | | +|-----|----------------------------------------------------| +| bit | | +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT + 1 | +| 1 0 | STARTING_UL_TIMESLOT + 2 | +| 1 1 | STARTING_UL_TIMESLOT + 3 | + +If both UL\_COVERAGE\_CLASS and DL\_COVERAGE\_CLASS = CC1, the downlink is assigned to the timeslot indicated by the STARTING\_UL\_TIMESLOT field. If timer T3248 (sent in EC SI) is used, the STARTING\_DL\_TIMESLOT\_OFFSET field defines the lowest assigned timeslot for EC-PACCH transfers using CC2 while the timer is running. The STARTING\_DL\_TIMESLOT\_OFFSET field is then encoded according to the following table: + +| | | +|-----|---------------------------------------------------------------------| +| bit | | +| 2 1 | | +| 0 0 | same timeslot as indicated by STARTING_UL_TIMESLOT | +| 0 1 | STARTING_UL_TIMESLOT - 1 | +| 1 0 | STARTING_UL_TIMESLOT - 2 | +| 1 1 | no valid CC2 mapping applies while T3248 is running, CC1 to be used | + +#### **UL\_COVERAGE\_CLASS\_EXT (1 bit field)** + +This field indicates how the field UL\_COVERAGE\_CLASS(see above) is to be interpreted and is coded as follows + +bit + +0 UL\_COVERAGE\_CLASS field indicates one of UL Coverage Class CC1, CC2, CC3 or CC4 are assigned for uplink + +1 UL\_COVERAGE\_CLASS field indicates UL Coverage Class CC5 is assigned for uplink + +### 11.2.59 EC Packet Uplink Ack/Nack and Contention Resolution + +This message is sent on the EC-PACCH by the network to the mobile station to indicate the status of the received RLC data blocks, include a fixed uplink allocation for the mobile station to (re)transmit not yet acknowledged/transmitted RLC Data blocks. The message includes the TLLI for contention resolution. + +The mobile station shall continue to use the previous EGPRS Modulation and Coding Scheme when transmitting in the resources allocated in this message. + +Message type: EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION + +Direction: network to mobile station + +Classification: non-distribution message + +**Table 11.2.59.1: EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION information elements** + +``` +< EC Packet Uplink Ack/Nack and Contention Resolution message content > ::= + < USED_DL_COVERAGE_CLASS : < Used DL Coverage Class IE >> + { + < UPLINK_TFI : bit (5) > + { + < CONTENTION_RESOLUTION_TLLI : bit (32) > + < EC Primary Ack/Nack Description : < EC Primary Ack/Nack Description IE >> + < PUANCN Fixed Uplink Allocation : < PUANCN Fixed Uplink Allocation struct > > + < RESEGMENT : bit (1) > + < padding bits > } + ! < Non-distribution part error : bit (*) = > } + ! < Address information part error : bit (*) = > } + ! < Distribution part error : bit (*) = > ; + + < PUANCN Fixed Uplink Allocation struct > ::= + < START_FIRST_UL_RLC_DATA_BLOCK : bit (4) > + { 1 { + 0 < DELAY_NEXT_UL_RLC_DATA_BLOCK : bit (3) > -- delay until start of next UL RLC Data block + | 1 -- next UL RLC Data block starts at first possible occasion after previous UL RLC Data block } } ** 0; +``` + +**Table 11.2.59.2: EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION information element details** + +#### USED\_DL\_COVERAGE\_CLASS (2 bit field) + +This information element is defined in sub-clause 12.71. + +#### UPLINK\_TFI (5 bit field) + +This field identifies the uplink TBF to which this message applies. This field is coded the same as the TFI field defined in sub-clause 12.15. + +#### CONTENTION\_RESOLUTION\_TLLI (32 bit field) + +The CONTENTION\_RESOLUTION\_TLLI field contains the TLLI that the network has received in uplink RLC data block(s). The mobile station shall perform the contention resolution function using the TLLI information in this field. The coding of this field is defined in sub-clause 12.16. + +#### **EC Primary Ack/Nack Description IE** + +This information element is defined in sub-clause 12.73. + +#### **RESEGMENT** (1 bit field) + +This field is defined in sub-clause 12.10e. + +#### **START\_FIRST\_UL\_RLC\_DATA\_BLOCK** (4 bit field) + +This field indicates the starting position of the resources for the first allocated RLC Data block in the fixed uplink allocation. The starting position is relative to the first TDMA frame (N) of the downlink block containing the last blind physical layer transmission of this EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, according to the USED\_DL\_COVERAGE\_CLASS field. The encoding of the field is dependent of the uplink Coverage Class and TIMESLOT\_MULTIPLICATOR assigned for the uplink EC TBF. + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 0 or if uplink Coverage Class = CC2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|----------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+17 or N+18) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+21 or N+22) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+26) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+30 or N+31) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+73 or N+74) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+78) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 1, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 0 0 1 1 | In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the lowest TN in TDMA frame (N+43 or N+44) mod 2715648 | +| 1 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+43 or N+44) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|---------------------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 0 1 0 1 | In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the highest TN in TDMA frame (N+30 or N+31) mod 2715648 | +| 1 1 1 1 | In the timeslot with the lowest TN in TDMA frame (N+34 or N+35) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 3, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| bit | | +|---------|-------------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | + +| | | +|---------|---------------------------------------------------------------------------------------------| +| 0 0 1 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 0 1 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+26) mod 2715648 | +| 1 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+26) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 4, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|-------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the highest TN in TDMA frame (N+21 or N+22) mod 2715648 | +| 1 1 1 1 | In the timeslot with the lowest TN in TDMA frame (N+26) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 5, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|---------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 5 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | +| 1 1 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 6, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|---------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 5 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the 6 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 0 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 1 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | +| 1 1 1 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+21 or N+22) mod 2715648 | + +If uplink Coverage Class = CC1 and TIMESLOT\_MULTIPLICATOR = 7, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|-------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 0 1 | In the timeslot with the 2 nd lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 0 1 0 | In the timeslot with the 3 rd lowest TN in TDMA frame (N+13) mod 2715648 | + +| | | +|---------|---------------------------------------------------------------------------------------------| +| 0 0 1 1 | In the timeslot with the 4 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 0 | In the timeslot with the 5 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 0 1 | In the timeslot with the 6 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 0 | In the timeslot with the 7 th lowest TN in TDMA frame (N+13) mod 2715648 | +| 0 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+13) mod 2715648 | +| 1 0 0 0 | In the timeslot with the lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| .... | | +| 1 1 1 0 | In the timeslot with the 7 th lowest TN in TDMA frame (N+17 or N+18) mod 2715648 | +| 1 1 1 1 | In the timeslot with the highest TN in TDMA frame (N+17 or N+18) mod 2715648 | + +If uplink Coverage Class = CC3 and the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018), or, if the field EC\_Reduced\_PDCH\_Allocation is set to 1 and the uplink Coverage Class = CC2, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|--------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 | + +If uplink Coverage Class = CC4 and the field EC\_Reduced\_PDCH\_Allocation is set to 0 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018), or, if the field EC\_Reduced\_PDCH\_Allocation is set to 1 and the uplink Coverage Class = CC3, the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 or (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 | +| 0 0 1 1 | In the TDMA frame (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod 2715648 or (N+95 or N+96) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+255 or N+256) mod 2715648 or (N+260) mod 2715648 or (N+264 or N+265) mod 2715648 or (N+268 or N+269) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+273) mod 2715648 or (N+277 or N+278) mod 2715648 or (N+281 or N+282) mod 2715648 or (N+286) mod 2715648 | + +If uplink Coverage Class = CC4 and the field EC\_Reduced\_PDCH\_Allocation is set to 1 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018), the START\_FN\_FIRST\_UL\_RLC\_DATA\_BLOCK field is encoded according to the following table: + +| | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | In the TDMA frame (N+13) mod 2715648 or (N+17 or N+18) mod 2715648 or (N+21 or N+22) mod 2715648 or (N+26) mod 2715648 or (N+30 or N+31) mod 2715648 or (N+34 or N+35) mod 2715648 or (N+39) mod 2715648 or (N+43 or N+44) mod 2715648 | +| 0 0 0 1 | In the TDMA frame (N+47 or N+48) mod 2715648 or (N+52) mod 2715648 or (N+56 or N+57) mod 2715648 or (N+60 or N+61) mod 2715648 or (N+65) mod 2715648 or (N+69 or N+70) mod 2715648 or (N+73 or N+74) mod 2715648 or (N+78) mod 2715648 | +| 0 0 1 0 | In the TDMA frame (N+82 or N+83) mod 2715648 or (N+86 or N+87) mod 2715648 or (N+91) mod | + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 1 1 | 2715648 or (N+95 or N+96) mod 715648 or (N+99 or N+100) mod 2715648 or (N+104) mod 2715648 or (N+108 or N+109) mod 2715648 or (N+112 or N+113) mod 2715648
In the TDMA frame (N+117) mod 2715648 or (N+121 or N+122) mod 2715648 or (N+125 or N+126) mod 2715648 or (N+130) mod 2715648 or (N+134 or N+135) mod 2715648 or (N+138 or N+139) mod 2715648 or (N+143) mod 2715648 or (N+147 or N+148) mod 2715648 | +| 0 1 0 0 | In the TDMA frame (N+151 or N+152) mod 2715648 or (N+156) mod 2715648 or (N+160 or N+161) mod 2715648 or (N+164 or N+165) mod 2715648 or (N+169) mod 2715648 or (N+173 or N+174) mod 2715648 or (N+177 or N+178) mod 2715648 or (N+182) mod 2715648 | +| .... | | +| 1 1 1 0 | In the TDMA frame (N+464 or N+465) mod 2715648 or (N+468) mod 2715648 or (N+472 or N+473) mod 2715648 or (N+477 or N+478) mod 2715648 or (N+481) mod 2715648 or (N+485 or N+486) mod 2715648 or (N+490 or N+491) mod 2715648 or (N+494) mod 2715648 | +| 1 1 1 1 | In the TDMA frame (N+498 or N+499) mod 2715648 or (N+503 or N+504) mod 2715648 or (N+507) mod 2715648 or (N+511 or N+512) mod 2715648 or (N+516 or N+517) mod 2715648 or (N+520) mod 2715648 or (N+524 or N+525) mod 2715648 or (N+529 or N+530) mod 2715648 | +| DELAY_NEXT_UL_RLC_DATA_BLOCK (3 bit field) | | +| This field indicates the position of the next allocated RLC Data block in the fixed uplink allocation. The position is calculated as the number of transmission opportunities from the previous uplink allocation, according to the assigned UL_COVERAGE_CLASS and TIMESLOT_MULTIPLICATOR, where the next uplink allocation for the mobile station is placed and where the mobile station thus shall transmit the next UL RLC data block. In the transmission opportunity/ies between the previous uplink allocation and this allocation the mobile station is not allocated any resource, and shall thus not transmit. | | +| This field is encoded according to the following table: | | +| bit | | +| 3 2 1 | | +| 0 0 0 | In the 2 nd next transmission opportunity | +| 0 0 1 | In the 3 rd next transmission opportunity | +| 0 1 0 | In the 4 th next transmission opportunity | +| .... | | +| 1 1 0 | In the 8 th next transmission opportunity | +| 1 1 1 | In the 9 th next transmission opportunity | + +### 11.2.60 EC Packet Downlink Ack/Nack Higher CC + +This message is sent on the EC-PACCH from the mobile station, whose uplink coverage class is set to CC5, to the network to indicate the status of downlink RLC data blocks received and to report the channel quality of the downlink. The mobile station may optionally initiate an uplink TBF by including the EC Channel Request Description in the message. + +Message type: EC Packet Downlink Ack/Nack Higher CC + +Direction: mobile station to network + +**Table 11.2.60.1: EC PACKET DOWNLINK ACK/NACK HIGHER CC information elements** + +``` + +< EC Packet Downlink Ack/Nack message content > ::= + < DOWNLINK_TFI : bit (5) > + < MS OUT OF MEMORY : bit(1) > + { 0 < EC Ack/Nack Description : < EC Ack/Nack Description IE > > -- Final Ack Indicator = 0 + | 1 -- Final Ack Indicator = 1 } + { 0 + | 1 { < EC Channel Quality Report Higher CC: < EC Channel Quality Report Type 2 IE > > + < DL_CC: bit (2) > } } + { 0 | 1 < EC Channel Request Description : < EC Channel Request Description struct > > } + < padding bits > ; + +< EC Channel Request Description struct > ::= + < PRIORITY : bit (1) > + < NUMBER_OF_UL_DATA_BLOCKS : bit (4) > ; + +``` + +**Table 11.2.60.2: EC PACKET DOWNLINK ACK/NACK HIGHER CC information element details** + +| | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--|------------|--|-----|--------|-----|--------|-----|--------|-----|--------| +| DOWNLINK_TFI (5 bit field)
This field contains the TFI of the mobile station's downlink TBF. This field is defined in sub-clause 12.15. | | | | | | | | | | | | | +| EC Ack/Nack Description IE
This information element is defined in sub-clause 12.72. | | | | | | | | | | | | | +| EC Channel Quality Report Higher CC IE
This information element is defined in sub-clause 12.76. | | | | | | | | | | | | | +| MS OUT OF MEMORY (1 bit field)
This information element is defined in sub-clause 11.2.51 | | | | | | | | | | | | | +| PRIORITY
This information element is defined in sub-clause 11.2.51 | | | | | | | | | | | | | +| NUMBER_OF_UL_DATA_BLOCKS
This information element is defined in sub-clause 11.2.51 | | | | | | | | | | | | | +| DL_CC (2 bit field)
This field contains the latest downlink Coverage Class estimation and the latest estimated C value range in case the C value is above BT_Threshold_DL, see 3GPP TS 45.008.

bit
2 1
0 0 DL CC4
0 1 DL CC3
1 0 DL CC2
1 1 DL CC1
| bit | | 2 1 | | 0 0 | DL CC4 | 0 1 | DL CC3 | 1 0 | DL CC2 | 1 1 | DL CC1 | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | DL CC4 | | | | | | | | | | | | +| 0 1 | DL CC3 | | | | | | | | | | | | +| 1 0 | DL CC2 | | | | | | | | | | | | +| 1 1 | DL CC1 | | | | | | | | | | | | + +### 11.2.61 EC Packet Control Acknowledgement Higher CC + +This message is sent on the EC-PACCH from the mobile station which uses uplink coverage class CC5 to the network. The message is formatted either as an RLC/MAC control block using the EC-PACCH block format defined in 3GPP TS 44.004 or as a number of identical access bursts, according to the assigned uplink CC (see 3GPP TS 45.002), using the EC-PACCH short acknowledgement block format defined in 3GPP TS 44.004. If the message is sent as response to an EC Packet Polling Request message this latter message shall specify the format of the EC Packet Control Acknowledgement message. The order of bit transmission is defined in 3GPP TS 44.004. The numbering, assembling and field mapping conventions defined for RLC/MAC control blocks in sub-clause 10.0b shall apply. + +The RLC/MAC control block format is shown in table 11.2.61.1 and table 11.2.61.2. + +The access burst format is 11-bits and is coded as shown in table 11.2.61.1. The mobile station shall transmit the access burst four times, one time in each TDMA frame of the uplink radio block. The transmission of the four access bursts shall then be repeated in each of the uplink EC-PACCH resources assigned with the RRBP field according to the assigned uplink Coverage Class for the mobile station. + +Message type: EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC + +Direction: mobile station to network + +**Table 11.2.61.1: EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< EC Packet Control Acknowledgement message Higher CC content > ::= -- RLC/MAC control block format   < TLLI : bit (32) >   < CTRL_ACK : bit (2) >   < DL_CC : bit (2) >   < padding bits > ;  < EC Packet Control Acknowledgement Higher CC 11 bit message > ::= -- 11-bit access burst format   < MESSAGE_TYPE : bit (7) == 1110 111 >   < DL_CC : bit (2) >   < Spare : bit (2) > ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.2.61.2: EC PACKET CONTROL ACKNOWLEDGEMENT HIGHER CC information element details** + +| | +|-----------------------------------------------------------------------------------------------------| +|

TLLI (32 bit field)
This information element is defined in sub-clause 11.2.50.

| +|

CTRL_ACK (2 bit field)
This information element is defined in sub-clause 11.2.50.

| +|

DL_CC (2 bit field)
This information element is defined in sub-clause 11.2.60.

| + +# 12 Information element coding + +## 12.1 Overview + +Information elements used within the context of only one RLC/MAC control message are defined in clause 11. All other information elements are defined within the present sub-clause. + +## 12.2 (void) + +## 12.3 Ack/Nack Description + +The Ack/Nack Description information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks. + +**Table 12.3.1: Ack/Nack Description information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Ack/Nack Description IE > ::=   < FINAL_ACK_INDICATION : bit (1) >   < STARTING_SEQUENCE_NUMBER : bit (7) >   < RECEIVED_BLOCK_BITMAP : bit (64) > ;
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.3.2: Ack/Nack Description information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

FINAL_ACK_INDICATION (1 bit field)

This field indicates whether the entire TBF is being acknowledged. If, in case the uplink TBF is operating in non-extended uplink TBF mode, the entire TBF is being acknowledged, the SSN and RBB fields contain no information and shall be ignored. When acknowledging the entire TBF in extended uplink TBF mode the SSN and RBB fields shall be interpreted.

0 retransmission are requested and the TBF is incomplete
1 no retransmissions are requested and this message indicates acknowledgement of all RLC data in the TBF

| +|

STARTING_SEQUENCE_NUMBER (SSN) (7 bit field)

The SSN contains the value of V(R) when this information element was transmitted. This field is encoded as the binary representation of V(R).
Range 0 to 127

| +|

RECEIVE_BLOCK_BITMAP (RBB) (64 bit field)

The RBB is a bitmap representing Block Sequence Numbers. The bitmap is indexed relative to SSN as follows:

BSN = (SSN - bit_number) modulo 128, for bit_number = 1 to 64.

The BSN values represented range from (SSN - 1) mod 128 to (SSN - 64) mod 128.

The value of each bit is encoded as:

0 Negative acknowledgement of the RLC data block with BSN = (SSN - bit_number) mod 128
1 Positive acknowledgement of the RLC data block with BSN = (SSN - bit_number) mod 128

Mapping of the bitmap is defined on sub-clause 11.

| + +### 12.3.1 EGPRS Ack/Nack Description + +The Ack/Nack Description information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks. The number of bits available for the bitmap depends on the inclusion or exclusion of other information elements in the used message. + +**Table 12.3.1.1: EGPRS Ack/Nack Description information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< EGPRS Ack/Nack Description IE > ::=   0 < EGPRS Ack/Nack Description struct > -- This IE fills rest of message     1 < Length L : bit (8) > -- Value part of this IE is of length L   { < bit (val(Length L)) > & < EGPRS Ack/Nack Description struct > } ;  < EGPRS Ack/Nack Description struct > ::=   < FINAL_ACK_INDICATION : bit (1) >   < BEGINNING_OF_WINDOW : bit (1) >   < END_OF_WINDOW : bit (1) >   < STARTING_SEQUENCE_NUMBER : bit (11) >   { 0   1 < COMPRESSED_BITMAP_LENGTH : bit (7) >     < COMPRESSED_BITMAP_STARTING_COLOR_CODE : bit (1) >     < COMPRESSED_RECEIVED_BLOCK_BITMAP :       bit (val(COMPRESSED_BITMAP_LENGTH)) > }   < UNCOMPRESSED_RECEIVED_BLOCK_BITMAP : bit** > ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.3.1.2: EGPRS Ack/Nack Description information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

LENGTH L (8 bit field)
Range 15 to 255
This field represents the length of the value part (i.e. the EGPRS Ack/Nack Description struct) of this information element. If this field is not included, this information element fills the remaining part of the message.

| +|

FINAL_ACK_INDICATION (1 bit field)
This field indicates whether the entire TBF is being acknowledged. If, in case the uplink TBF is operating in non-extended uplink TBF mode, the entire TBF is being acknowledged, the SSN, CRBB and URBB fields contain no information and shall be ignored. When acknowledging the entire TBF in extended uplink TBF mode, the SSN, CRBB and URBB fields shall be interpreted if present.

0 retransmissions are requested and the TBF is incomplete.
1 no retransmissions are requested and this message indicates acknowledgement of all RLC data in the TBF.

| +|

BEGINNING_OF_WINDOW (BOW, 1 bit field)
This bit indicates if the Ack/Nack bitmap starts at the beginning of the window.

0 SSN not equal to (V(Q)+1) \bmod 2048.
1 SSN = (V(Q) + 1) \bmod 2048

| +|

END_OF_WINDOW (EOW, 1 bit field)
This bit indicates if the end of the receiver window is included in the bitmap(s).

0 [V(R) - 1] \bmod \text{SNS} is not included in the bitmap.
1 [V(R) - 1] \bmod \text{SNS} is included in the bitmap.

| +|

STARTING_SEQUENCE_NUMBER (SSN) (11 bit field)
Range 0 to 2047
The SSN indicates the Block Sequence Number of the first RLC block for which the Ack/Nack receipt status is indicated within the bitmap. The SSN is determined using S/P, PBSN and V(Q).

| +|

COMPRESSED_BITMAP_LENGTH (Lc) (7 bit field)
Range 0 to 127
This field represents the length of the compressed bitmap. Compression is carried out using T.4 run length coding.

| +|

COMPRESSED_BITMAP_STARTING_COLOR_CODE (1 bit field)
This bit indicates if the first code word in the compressed bitmap (i.e. CRBB) represents a run length of ones or a run length of zeros.

0 First code word in CRBB represents run length of zeros.
1 First code word in CRBB represents run length of ones.

| +|

COMPRESSED_RECEIVE_BLOCK_BITMAP (CRBB) (Lc bit field)
The CRBB is a compressed bitmap. Compression is carried out starting at SSN using modified T.4 run length coding. The number of bits (Lc) available for Ack/Nack Description depends on the inclusion of other information elements in the used message.

The packing order of the CRBB shall be such that the codeword (or pair of make up/terminating codewords) corresponding to the run including the SSN starts at the most significant bit of the CRBB, and codewords (or pairs of make-up/terminating codewords) corresponding to runs including higher and successively increasing sequence numbers are placed in bits of successively decreasing significance.

NOTE: The URBB is packed in the opposite order.

| + +#### **UNCOMPRESSED\_RECEIVE\_BLOCK\_BITMAP (URBB)** (Lu bit field) + +The URBB is an uncompressed bitmap, which fills the remainder of this information element upto L bits, where L is the number of bits available for the EGPRS Ack/Nack description struct. The URBB field length, Lu, is determined by: + +Lu = L-Lc-23, when the compressed received block bitmap is included, or by + +Lu = L-15, when the compressed received block bitmap is not included: + +The bits in URBB, denoted here by index i, are numbered from i=1 (lowest order value) to i=Lu (highest order value). The value of each bit in the bitmap is encoded as following: + +- | | | +|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Negative acknowledgement of the RLC data block with BSN = (ESN_CRBB + i) modulo SNS, and | +| 1 | Positive acknowledgement of the RLC data block with BSN = (ESN_CRBB + i) modulo SNS, where ESN_CRBB is the ending block sequence number of CRBB and, if no CRBB is included, ESN_CRBB = (SSN - 1) modulo SNS. | + +### 12.3.2 FLO Ack/Nack Description + +The FLO Ack/Nack Description information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks. + +**Table 12.3.2.1: FLO Ack/Nack Description information elements** + +``` +< FLO Ack/Nack Description IE > ::= + < FLO Ack/Nack Description struct > ; + +< FLO Ack/Nack Description struct > ::= + < BEGINNING_OF_WINDOW : bit (1) > + < END_OF_WINDOW : bit (1) > + < STARTING_SEQUENCE_NUMBER : bit (10) > + { 0 < COMPRESSED_BITMAP_LENGTH: bit (7) > + < COMPRESSED_BITMAP_STARTING_COLOR_CODE: bit (1) > + < COMPRESSED_RECEIVED_BLOCK_BITMAP: bit (val(COMPRESSED_BITMAP_LENGTH)) > + | 1 < UNCOMPRESSED_RECEIVED_BLOCK_BITMAP: bit** > } ; +``` + +**Table 12.3.2.2: Ack/Nack Description information element details** + +#### **BEGINNING\_OF\_WINDOW (BOW, 1 bit field)** + +This bit indicates whether the status of the RLC data block corresponding to V(Q) i.e. '0' is included in the reported bitmap or not. + +- | | | +|---|-----------------------------------------| +| 0 | the reported bitmap does not cover V(Q) | +| 1 | the reported bitmap covers V(Q) | + +#### **END\_OF\_WINDOW (EOW, 1 bit field)** + +This bit indicates whether the end of the receiver window is included in the reported bitmap or not. + +- | | | +|---|---------------------------------------------------------------| +| 0 | [V(R) - 1] modulo SNS is not included in the reported bitmap. | +| 1 | [V(R) - 1] modulo SNS is included in the reported bitmap. | + +#### **STARTING\_SEQUENCE\_NUMBER (SSN) (10 bit field)** + +Range 0 to 1023 + +The SSN indicates the Block Sequence Number of the last RLC block for which the Ack/Nack receipt status is indicated within the reported bitmap. + +#### **COMPRESSED\_BITMAP\_LENGTH (Lc) (7 bit field)** + +Range 0 to 127 + +This field represents the length of the compressed bitmap. Compression is carried out using T.4 run length coding. + +#### **COMPRESSED\_BITMAP\_STARTING\_COLOR\_CODE** (1 bit field) + +This bit indicates if the first code word in the compressed bitmap (i.e. CRBB) represents a run length of ones or a run length of zeros. + +- 0 First code word in CRBB represents run length of zeros. +- 1 First code word in CRBB represents run length of ones. + +#### **COMPRESSED\_RECEIVE\_BLOCK\_BITMAP (CRBB)** (Lc bit field) + +The CRBB is a compressed bitmap. Compression is carried out starting at SSN-1 and going in decreasing order of the BSN, using modified T.4 run length coding. + +The packing order of the CRBB shall be such that the codeword (or pair of make up/terminating codewords) corresponding to the run including the SSN-1 starts at the least significant bit of the CRBB, and codewords (or pairs of make-up/terminating codewords) corresponding to runs including lower and successively decreasing sequence numbers are placed in bits of successively increasing significance. + +#### **UNCOMPRESSED\_RECEIVE\_BLOCK\_BITMAP (URBB)** (Lu bit field) + +The URBB is an uncompressed bitmap of length Lu bits. + +The bits in URBB, denoted here by index i, are numbered from i=1 (highest order value i.e. corresponding to SSN-1) to i=Lu (lowest order value). The value of each bit in the bitmap is encoded as following: + +- 0 Negative acknowledgement of the RLC data block with BSN = (SSN - 1 - i) modulo SNS, and +- 1 Positive acknowledgement of the RLC data block with BSN = (SSN - 1 - i) modulo SNS + +### 12.3.3 EGPRS Ack/Nack Description DLMC + +The EGPRS Ack/Nack Description DLMC information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks for a DLMC configuration. The number of bits available for the bitmap depends on the inclusion or exclusion of other information elements in the used message. + +**Table 12.3.3.1: EGPRS Ack/Nack Description DLMC information elements** + +``` +< EGPRS Ack/Nack Description DLMC IE > ::= + 0 < EGPRS Ack/Nack Description struct > -- This IE fills rest of message + | 1 < Length L : bit (8) > -- Value part of this IE is of length L + { < bit (val(Length L)) > & < EGPRS Ack/Nack Description struct > } ; + +< EGPRS Ack/Nack Description struct > ::= + < FINAL_ACK_INDICATION : bit (1) > + < BEGINNING_OF_WINDOW : bit (1) > + < END_OF_WINDOW : bit (1) > + { 0 < STARTING_SEQUENCE_NUMBER : bit (11) > + | 1 < STARTING_SEQUENCE_NUMBER : bit (13) > } + { 0 | 1 < COMPRESSED_BITMAP_LENGTH : bit (8) > + < COMPRESSED_BITMAP_STARTING_COLOR_CODE : bit (1) > + < COMPRESSED_RECEIVED_BLOCK_BITMAP : + bit (val(COMPRESSED_BITMAP_LENGTH)) > } + < UNCOMPRESSED_RECEIVED_BLOCK_BITMAP : bit** > ; +``` + +**Table 12.3.3.2: EGPRS Ack/Nack Description DLMC information element details** + +#### **LENGTH L** (8 bit field) + +See sub-clause 12.3.1. + +#### **FINAL\_ACK\_INDICATION** (1 bit field) + +See sub-clause 12.3.1. + +#### **BEGINNING\_OF\_WINDOW (BOW, 1 bit field)** + +See sub-clause 12.3.1. + +#### **END\_OF\_WINDOW (EOW, 1 bit field)** + +See sub-clause 12.3.1. + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

STARTING_SEQUENCE_NUMBER (SSN) (11 bit field)

This value is included when a DLMC configuration uses a SNS of 2048 (see sub-clause 5.13).

Range 0 to 2047

The SSN indicates the Block Sequence Number of the first RLC block for which the Ack/Nack receipt status is indicated within the bitmap. The SSN is determined using S/P, PBSN and V(Q).

| +|

STARTING_SEQUENCE_NUMBER (SSN) (13 bit field)

This value is included when a DLMC configuration uses a SNS of 8192 (see sub-clause 5.13).

Range 0 to 8191

The SSN indicates the Block Sequence Number of the first RLC block for which the Ack/Nack receipt status is indicated within the bitmap. The SSN is determined using S/P, PBSN and V(Q).

| +|

COMPRESSED_BITMAP_LENGTH (Lc) (7 bit field)

See sub-clause 12.3.1.

| +|

COMPRESSED_BITMAP_STARTING_COLOR_CODE (1 bit field)

See sub-clause 12.3.1.

| +|

COMPRESSED_RECEIVE_BLOCK_BITMAP (CRBB) (Lc bit field)

See sub-clause 12.3.1.

| +|

UNCOMPRESSED_RECEIVE_BLOCK_BITMAP (URBB) (Lu bit field)

See sub-clause 12.3.1.

| + +## 12.4 (void) + +## 12.5 EGPRS + +### 12.5.1 EGPRS Channel Quality Report + +The EGPRS Channel Quality Report Information Element IE is defined in tables 12.5.1.1 and 12.5.1.2. The information to be included within this IE depends on the setting of the ES/P field or CES/P field (see sub-clause 9.1.8.2.1) and on the most recently received LINK\_QUALITY\_MEASUREMENT\_MODE field (see sub-clause 11.2.7). + +**Table 12.5.1.1 : EGPRS Channel Quality Report Information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< EGPRS Channel Quality Report IE> ::=   < EGPRS BEP Link Quality Measurements : < EGPRS BEP Link Quality Measurements IE>>   < C_VALUE : bit (6) >   < EGPRS Timeslot Link Quality Measurements : <EGPRS Timeslot Link Quality Measurements IE >> ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.5.1.2 : EGPRS Channel Quality Report Information Elements details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

EGPRS BEP Link Quality Measurements IE

This information element is defined in sub-clause 12.5.3.

EGPRS Timeslot Link Quality Measurements

This information element is defined in sub-clause 12.5.4.

C_VALUE (6 bits)

This field contains the value of the C parameter calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as the binary representation of the C value parameter value defined in 3GPP TS 45.008.

Range 0 to 63

| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 12.5.2 EGPRS Window Size + +This information element defines the window size to be used in an EGPRS TBF. The network sets the window size according to the number of timeslots assigned in the direction of the TBF. + +If RLC acknowledged mode is signalled in the assignment/reconfiguration message, or if RLC unacknowledged mode is signalled and the mobile station does not support RLC non-persistent mode, the window size is defined according to Table 12.5.2.1 below. + +**Table 12.5.2.1: EGPRS Window Size Information Elements details for RLC (un)acknowledged mode** + +| bit
5 4 3 2 1 | Value of EGPRS
window size | Comment | +|------------------|-------------------------------|------------------------------------------------| +| 0 0 0 0 0 | 64 | | +| 0 0 0 0 1 | 96 | | +| 0 0 0 1 0 | 128 | | +| 0 0 0 1 1 | 160 | | +| 0 0 1 0 0 | 192 | (maximum window size for a 1 timeslot TBF) | +| 0 0 1 0 1 | 224 | | +| 0 0 1 1 0 | 256 | (maximum window size for a 2 timeslot TBF) | +| 0 0 1 1 1 | 288 | | +| 0 1 0 0 0 | 320 | | +| 0 1 0 0 1 | 352 | | +| 0 1 0 1 0 | 384 | (maximum window size for a 3 timeslot TBF) | +| 0 1 0 1 1 | 416 | | +| 0 1 1 0 0 | 448 | | +| 0 1 1 0 1 | 480 | | +| 0 1 1 1 0 | 512 | (maximum window size for a 4 timeslot TBF) | +| 0 1 1 1 1 | 544 | | +| 1 0 0 0 0 | 576 | | +| 1 0 0 0 1 | 608 | | +| 1 0 0 1 0 | 640 | (maximum window size for a 5 timeslot TBF) | +| 1 0 0 1 1 | 672 | | +| 1 0 1 0 0 | 704 | | +| 1 0 1 0 1 | 736 | | +| 1 0 1 1 0 | 768 | (maximum window size for a 6 timeslot TBF) | +| 1 0 1 1 1 | 800 | | +| 1 1 0 0 0 | 832 | | +| 1 1 0 0 1 | 864 | | +| 1 1 0 1 0 | 896 | (maximum window size for a 7 timeslot TBF) | +| 1 1 0 1 1 | 928 | | +| 1 1 1 0 0 | 960 | | +| 1 1 1 0 1 | 992 | | +| 1 1 1 1 0 | 1024 | (maximum window size for an 8-16 timeslot TBF) | +| 1 1 1 1 1 | Reserved | | + +If RLC unacknowledged mode is signalled in the assignment/reconfiguration message, and the mobile station supports RLC non-persistent mode, RLC non-persistent mode shall be assumed by the mobile station, except when the window size is set equal to 1, and the window size is defined according to Table 12.5.2.2 below. + +When a mobile station supporting RLC non-persistent mode operates in RLC unacknowledged mode (i.e. the window size is set to 1) it shall assume the maximum window size corresponding to the TBF's timeslot allocation (see Table 9.1.9.2.1) when defining the bitmap in sub-clause 9.1.8.2. + +If an MBMS bearer is allocated RLC non-persistent mode shall be used. For this case the window size is defined according to Table 12.5.2.2 below. + +**Table 12.5.2.2: EGPRS Window Size Information Elements details for RLC non-persistent mode** + +| bit
5 4 3 2 1 | Value of EGPRS
window size | Comment | +|------------------|-------------------------------|------------------------------------------------------------------------| +| 0 0 0 0 0 | 1 | This value indicates RLC unacknowledged mode is used for the EGPRS TBF | +| 0 0 0 0 1 | 2 | | +| 0 0 0 1 0 | 4 | | +| 0 0 0 1 1 | 6 | | +| 0 0 1 0 0 | 8 | | +| 0 0 1 0 1 | 10 | | +| 0 0 1 1 0 | 12 | | +| 0 0 1 1 1 | 16 | | +| 0 1 0 0 0 | 20 | | +| 0 1 0 0 1 | 24 | | +| 0 1 0 1 0 | 32 | | +| 0 1 0 1 1 | 40 | | +| 0 1 1 0 0 | 48 | | +| 0 1 1 0 1 | 56 | | +| 0 1 1 1 0 | 64 | | +| 0 1 1 1 1 | 80 | | +| 1 0 0 0 0 | 96 | | +| 1 0 0 0 1 | 112 | | +| 1 0 0 1 0 | 128 | | +| 1 0 0 1 1 | 160 | | +| 1 0 1 0 0 | 192 | (maximum window size for a 1 timeslot TBF) | +| 1 0 1 0 1 | 256 | (maximum window size for a 2 timeslot TBF) | +| 1 0 1 1 0 | 320 | | +| 1 0 1 1 1 | 384 | (maximum window size for a 3 timeslot TBF) | +| 1 1 0 0 0 | 448 | | +| 1 1 0 0 1 | 512 | (maximum window size for a 4 timeslot TBF) | +| 1 1 0 1 0 | 576 | | +| 1 1 0 1 1 | 640 | (maximum window size for a 5 timeslot TBF) | +| 1 1 1 0 0 | 768 | (maximum window size for a 6 timeslot TBF) | +| 1 1 1 0 1 | 896 | (maximum window size for a 7 timeslot TBF) | +| 1 1 1 1 0 | 1024 | (maximum window size for a 8-16 timeslot TBF) | +| 1 1 1 1 1 | Reserved | | + +### 12.5.3 EGPRS BEP Link Quality Measurements IE + +The EGPRS BEP Link Quality measurements IE is defined in tables 12.5.3.1 and 12.5.3.2. + +**Table 12.5.3.1: EGPRS BEP Link Quality Information elements** + +``` + ::= +{ 0 | 1 < GMSK_MEAN_BEP : bit (5) > + < GMSK_CV_BEP : bit (3) > } +{ 0 | 1 < 8PSK_MEAN_BEP : bit (5) > + < 8PSK_CV_BEP : bit (3) > }; +``` + +**Table 12.5.3.2 : EGPRS BEP Link Quality Information Elements details** + +#### GMSK\_MEAN\_BEP (5 bit field) + +This field contains the mean value of the Bit Error Probability of the channel averaged over all time slots in the TBF for GMSK, refer to 3GPP TS 45.008. + +#### 8PSK\_MEAN\_BEP (5 bit field) + +This field contains the mean value of the Bit Error Probability of the channel averaged over all time slots in the TBF for 8 PSK, refer to 3GPP TS 45.008. + +#### **GMSK\_CV\_BEP** (3 bit field) + +This field contains the variation co-efficient for the Bit Error Probability averaged over all time slots of the TBF for GMSK, refer to 3GPP TS 45.008. + +#### **8PSK\_CV\_BEP** (3 bit field) + +This field contains the variation co-efficient for the Bit Error Probability averaged over all time slots of the TBF for 8 PSK, refer to 3GPP TS 45.008. + +### 12.5.4 EGPRS Timeslot Link Quality Measurements IE + +The EGPRS Timeslot Link Quality measurements IE is defined in tables 12.5.4.1 and 12.5.4.2. + +**Table 12.5.4.1: EGPRS Timeslot Link Quality Measurements Information elements** + + ::= + +{ 0 | 1 < **BEP\_MEASUREMENTS** : BEP Measurement Report Struct > } + +{ 0 | 1 < **INTERFERENCE\_MEASUREMENTS** : Interference Measurement Report Struct > }; + +--- + +< BEP Measurement Report Struct > ::= + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN0** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN0** : bit (4) > } } + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN1** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN1** : bit (4) > } } + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN2** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN2** : bit (4) > } } + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN3** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN3** : bit (4) > } } + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN4** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN4** : bit (4) > } } + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN5** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN5** : bit (4) > } } + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN6** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN6** : bit (4) > } } + +{ 0 | 1 { 0 < **GMSK\_MEAN\_BEP\_TN7** : bit (4) > | 1 < **8PSK\_MEAN\_BEP\_TN7** : bit (4) > } }; + +--- + +< Interference Measurement Report Struct > ::= + +{ 0 | 1 < **I\_LEVEL\_TN0** : bit (4) > } + +{ 0 | 1 < **I\_LEVEL\_TN1** : bit (4) > } + +{ 0 | 1 < **I\_LEVEL\_TN2** : bit (4) > } + +{ 0 | 1 < **I\_LEVEL\_TN3** : bit (4) > } + +{ 0 | 1 < **I\_LEVEL\_TN4** : bit (4) > } + +{ 0 | 1 < **I\_LEVEL\_TN5** : bit (4) > } + +{ 0 | 1 < **I\_LEVEL\_TN6** : bit (4) > } + +{ 0 | 1 < **I\_LEVEL\_TN7** : bit (4) > }; + +**Table 12.5.4.2: EGPRS Timeslot Link Quality Measurements Information Elements details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

GMSK_MEAN_BEP_TN0 (4 bit field)
GMSK_MEAN_BEP_TN1 (4 bit field)
GMSK_MEAN_BEP_TN2 (4 bit field)
GMSK_MEAN_BEP_TN3 (4 bit field)
GMSK_MEAN_BEP_TN4 (4 bit field)
GMSK_MEAN_BEP_TN5 (4 bit field)
GMSK_MEAN_BEP_TN6 (4 bit field)
GMSK_MEAN_BEP_TN7 (4 bit field)

These fields contain the mean bit error probability value calculated on timeslots 0 through 7 for GMSK modulation, refer to 3GPP TS 45.008. These fields are transferred only when the mobile station is in packet transfer mode. In RTTI configuration, the mean bit error probability value calculated on per timeslot pair shall be reported on GMSK_MEAN_BEP_TNx where TNx is the lower numbered timeslot of each reported timeslot pair.

| +|

8PSK_MEAN_BEP_TN0 (4 bit field)
8PSK_MEAN_BEP_TN1 (4 bit field)
8PSK_MEAN_BEP_TN2 (4 bit field)
8PSK_MEAN_BEP_TN3 (4 bit field)
8PSK_MEAN_BEP_TN4 (4 bit field)
8PSK_MEAN_BEP_TN5 (4 bit field)
8PSK_MEAN_BEP_TN6 (4 bit field)
8PSK_MEAN_BEP_TN7 (4 bit field)

These fields contain the mean bit error probability value calculated on timeslots 0 through 7 for 8PSK modulation, refer to 3GPP TS 45.008. These fields are transferred only when the mobile station is in packet transfer mode. In RTTI configuration, the mean bit error probability value calculated on per timeslot pair shall be reported on 8PSK_MEAN_BEP_TNx where TNx is the lower numbered timeslot of each reported timeslot pair.

| +|

I_LEVEL_TN0 (4 bit field)
I_LEVEL_TN1 (4 bit field)
I_LEVEL_TN2 (4 bit field)
I_LEVEL_TN3 (4 bit field)
I_LEVEL_TN4 (4 bit field)
I_LEVEL_TN5 (4 bit field)
I_LEVEL_TN6 (4 bit field)
I_LEVEL_TN7 (4 bit field)

These fields contain the γ value calculated on timeslots 0 through 7, respectively. The γ value is defined in 3GPP TS 45.008. These fields are encoded relative to C_VALUE as defined for the mapping defined in 3GPP TS 45.008 for interference level (I_LEVEL):

 bit 4 3 2 1 0 0 0 0  I_LEVEL 0 0 0 0 1  I_LEVEL 1 ... 1 1 1 0  I_LEVEL 14 1 1 1 1  I_LEVEL 15
| + +### 12.5.5 PDCH Pairs Description + +The PDCH Pairs Description information element gives the description of the uplink and downlink corresponding pairs of an RTTI configuration. + +**Table 12.5.5.1: PDCH Pairs Description Information Element** + +``` + +< PDCH Pairs Description IE > ::= + { 0 -- Single Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + | 1 -- Dual Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + } ; + +``` + +**Table 12.5.5.2: PDCH Pairs Description Information Element** + +``` + +DOWNLINK_PDCH_PAIRS_C1 +DOWNLINK_PDCH_PAIRS_C2 +UPLINK_PDCH_PAIRS_C1 +UPLINK_PDCH_PAIRS_C2 + +``` + +These fields are defined in sub-clause 11.2.31 + +## 12.5a EGPRS2 + +#### 12.5a.1 EGPRS Channel Quality Report Type 2 + +The EGPRS2 Channel Quality Report Type 2 Information Element is defined in tables 12.5a.1.1 and 12.5a.1.2. The information to be included within this IE depends on the setting of the ES/P field or CES/P field (see sub-clause 9.1.8.2.1) and on the most recently received LINK\_QUALITY\_MEASUREMENT\_MODE field (see sub-clause 11.2.7). + +**Table 12.5a.1.1 : EGPRS Channel Quality Report Type 2 Information elements** + +``` + +< EGPRS Channel Quality Report Type 2 IE > ::= + < EGPRS BEP Link Quality Measurements Type 2 : < EGPRS BEP Link Quality Measurements Type 2 IE > > + < C_VALUE : bit (6) > + < EGPRS Timeslot Link Quality Measurements Type 2 : < EGPRS Timeslot Link Quality Measurements Type 2 IE > +> ; + +``` + +**Table 12.5a.1.2 : EGPRS Channel Quality Report Type 2 Information Elements details** + +#### **EGPRS BEP Link Quality Measurements Type 2** + +This information element is defined in sub-clause 12.5a.2. These fields are transferred according to the setting of the ES/P field or CES/P field, see sub-clause 9.1.8.2.1. + +#### **EGPRS Timeslot Link Quality Measurements Type 2** + +This information element is defined in sub-clause 12.5a.3. + +#### **C\_VALUE (6 bits)** + +This field contains the value of the C parameter calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as the binary representation of the C value parameter value defined in 3GPP TS 45.008. + +Range 0 to 63 + +### 12.5a.2 EGPRS BEP Link Quality Measurements Type 2 IE + +The EGPRS BEP Link Quality measurements Type 2 IE is defined in tables 12.5a.2.1 and 12.5a.2.2. In the case of dual carrier configurations, "all timeslots in the TBF" shall refer only to those timeslots on the carrier to which this IE relates. + +**Table 12.5a.2.1: EGPRS BEP Link Quality Measurements Type 2 Information elements** + +``` + ::= +{ 0 | 1 < GMSK_MEAN_BEP : bit (5) > + < GMSK_CV_BEP : bit (3) > } +{ 0 | 1 < 8PSK_MEAN_BEP : bit (5) > + < 8PSK_CV_BEP : bit (3) > } +{ 0 | 1 < QPSK_MEAN_BEP : bit (5) > + < QPSK_CV_BEP : bit (3) > } +{ 0 | 1 < 16QAM_NSR_MEAN_BEP : bit (5) > + < 16QAM_NSR_CV_BEP : bit (3) > } +{ 0 | 1 < 32QAM_NSR_MEAN_BEP : bit (5) > + < 32QAM_NSR_CV_BEP : bit (3) > } +{ 0 | 1 < 16QAM_HSR_MEAN_BEP : bit (5) > + < 16QAM_HSR_CV_BEP : bit (3) > } +{ 0 | 1 < 32QAM_HSR_MEAN_BEP : bit (5) > + < 32QAM_HSR_CV_BEP : bit (3) > }; +``` + +**Table 12.5a.2.2 : EGPRS BEP Link Quality Measurements Type 2 Information Elements details** + +GMSK\_MEAN\_BEP (5 bit field) + 8PSK\_MEAN\_BEP (5 bit field) + QPSK\_MEAN\_BEP (5 bit field) + 16QAM\_NSR\_MEAN\_BEP (5 bit field) + 32QAM\_NSR\_MEAN\_BEP (5 bit field) + 16QAM\_HSR\_MEAN\_BEP (5 bit field) + 32QAM\_HSR\_MEAN\_BEP (5 bit field) + +These fields contain the mean value of the Bit Error Probability of the channel averaged over all timeslots in the TBF for the relevant modulation scheme, refer to 3GPP TS 45.008. + +GMSK\_CV\_BEP (3 bit field) + 8PSK\_CV\_BEP (3 bit field) + QPSK\_CV\_BEP (3 bit field) + 16QAM\_NSR\_CV\_BEP (3 bit field) + 32QAM\_NSR\_CV\_BEP (3 bit field) + 16QAM\_HSR\_CV\_BEP (3 bit field) + 32QAM\_HSR\_CV\_BEP (3 bit field) + +These fields contain the variation coefficient for the Bit Error Probability averaged over all timeslots of the TBF for the relevant modulation scheme, refer to 3GPP TS 45.008. + +### 12.5a.3 EGPRS Timeslot Link Quality Measurements Type 2 IE + +The EGPRS Timeslot Link Quality Measurements Type 2 IE is defined in tables 12.5a.3.1 and 12.5a.3. + +**Table 12.5a.3.1: EGPRS Timeslot Link Quality Measurements Type 2 Information elements** + +``` + + ::= +{ 0 | 1 < BEP_MEASUREMENTS : BEP Measurement Report Struct >} +{ 0 | 1 < INTERFERENCE_MEASUREMENTS : Interference Measurement Report Struct >}; + +< BEP Measurement Report Struct > ::= +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +} +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +} +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +} +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +} +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +} +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +} +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +} +{ 0 +| 1 < REPORTED_MODULATION : bit (2) > + +}; + +< Interference Measurement Report Struct > ::= +{ 0 | 1 < I_LEVEL_TN0 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN1 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN2 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN3 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN4 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN5 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN6 : bit (4) > } +{ 0 | 1 < I_LEVEL_TN7 : bit (4) > }; + +``` + +**Table 12.5a.3.2: EGPRS Timeslot Link Quality Measurements Type 2 Information Elements details** + +MEAN\_BEP\_TN0 (4 bit field) + MEAN\_BEP\_TN1 (4 bit field) + MEAN\_BEP\_TN2 (4 bit field) + MEAN\_BEP\_TN3 (4 bit field) + MEAN\_BEP\_TN4 (4 bit field) + MEAN\_BEP\_TN5 (4 bit field) + MEAN\_BEP\_TN6 (4 bit field) + MEAN\_BEP\_TN7 (4 bit field) + +These fields contain the mean bit error probability value calculated on timeslots 0 through 7 for the modulation scheme as indicated using the REPORTED\_MODULATION field, see below. For the calculation of the mean bit error probability, refer to 3GPP TS 45.008. These fields are transferred only when the mobile station is in packet transfer mode. In RTTI configuration, the mean bit error probability value calculated on per timeslot pair shall be reported on **MODULATION\_1\_MEAN\_BEP\_TNx / MODULATION\_2\_MEAN\_BEP\_TNx** where TNx is the lower numbered timeslot of each reported timeslot pair. + +I\_LEVEL\_TN0 (4 bit field) + I\_LEVEL\_TN1 (4 bit field) + I\_LEVEL\_TN2 (4 bit field) + I\_LEVEL\_TN3 (4 bit field) + I\_LEVEL\_TN4 (4 bit field) + I\_LEVEL\_TN5 (4 bit field) + I\_LEVEL\_TN6 (4 bit field) + I\_LEVEL\_TN7 (4 bit field) + +These fields contain the y value calculated on timeslots 0 through 7, respectively. The y value is defined in 3GPP TS 45.008. These fields are encoded relative to C\_VALUE as defined for the mapping defined in 3GPP TS 45.008 for interference level (I\_LEVEL): + +| bit | | +|---------|------------| +| 4 3 2 1 | | +| 0 0 0 0 | I_LEVEL 0 | +| 0 0 0 1 | I_LEVEL 1 | +| ... | | +| 1 1 1 0 | I_LEVEL 14 | +| 1 1 1 1 | I_LEVEL 15 | + +#### **REPORTED\_MODULATION** (2 bit field) + +The mobile station shall, for each of its currently assigned timeslots, report the modulation scheme (indicated using the REPORTED\_MODULATION field) with which it has received the largest number of blocks since the last report and shall report the MEAN\_BEP\_TNx of that modulation scheme (see the section 10.2.3.2.3 in 3GPP TS 45.008). The mapping of the modulation scheme is as follows. + +For EGPRS2-A: + +| bit | | +|-----|-------| +| 2 1 | | +| 0 0 | GMSK | +| 0 1 | 8PSK | +| 1 0 | 16QAM | +| 1 1 | 32QAM | + +For EGPRS2-B: + +| bit | | +|-----|-------------------------------| +| 2 1 | | +| 0 0 | GMSK | +| 0 1 | QPSK | +| 1 0 | 16QAM with higher symbol rate | +| 1 1 | 32QAM with higher symbol rate | + +In case of EGPRS2-B, if there are any received radio blocks with 8PSK, 16QAM with normal symbol rate or 32QAM with normal symbol rate, those radio blocks shall be ignored for channel quality reporting on that timeslot. + +## 12.6 (void) + +## 12.7 Channel Request Description + +The Channel Request Description information element is sent by the mobile station to the network to request uplink resources. + +**Table 12.7.1: Channel Request Description information elements** + +``` +< Channel Request Description IE > ::= + < PEAK_THROUGHPUT_CLASS : bit (4) > + < RADIO_PRIORITY : bit (2) > + < RLC_MODE : bit (1) > + < LLC_PDU_TYPE : bit (1) > + < RLC_OCTET_COUNT : bit (16) > ; +``` + +**Table 12.7.2: Channel Request Description information element details** + +### PEAK\_THROUGHPUT\_CLASS (4 bit field) + +This field indicates the peak throughput class for the PDP context of the LLC PDU that caused the Channel Request Description IE to be transmitted. The field is coded as the binary representation of the Peak Throughput Class specified in 3GPP TS 24.008. + +Range: 1 to 9 + +### RADIO\_PRIORITY (2 bit field) + +This field indicates the Radio Priority of the requested TBF. The field is encoded as the Radio Priority field of the Packet Channel Request (see sub-clause 11.2.5). + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RLC_MODE (1 bit field)
This field indicates the RLC mode of the requested TBF.

0 RLC acknowledged mode
1 RLC unacknowledged mode

| +|

LLC_PDU_TYPE (1 bit field)
This field indicates the type of the first LLC PDU to be transmitted over the requested uplink TBF.

0 LLC PDU is SACK or ACK
1 LLC PDU is not SACK or ACK

| +|

RLC_OCTET_COUNT (16 bit field)
The RLC_OCTET_COUNT field indicates the number of RLC data octets, plus the number of RLC data block length octets, that the mobile station wishes to transfer. The value '0' indicates that the mobile station does not provide any information on the TBF size.
Range 0 to 65535

| + +## 12.7a Iu mode Channel Request Description + +The *Iu mode Channel Request Description* information element is sent by the mobile station to the network to request uplink resources. + +**Table 12.7a.1: Iu mode Channel Request Description information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Iu mode Channel Request Description IE > ::=    < RB Id : bit (5) >   < RADIO_PRIORITY : bit (2) >   { 0   1 < RLC_BLOCK_COUNT : bit (8) > }   { 0   1 < Iu mode Channel Request Description IE > } ;  -- IE to be repeated only when                                                         -- in a Multiple TBF request message
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.7a.2: Iu mode Channel Request Description information element details** + +| | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------|-----------------|--------------------|-------|--|-----------------|---------------------| +|

RB Id (5 bit field)
This field indicates the radio bearer identity of the upper layer PDU that caused the Iu mode Channel Request Description IE to be transmitted.

Range: 0 to 31

| | | | | | | | | +|

RADIO_PRIORITY (2 bit field)
This field indicates the Radio Priority of the requested TBF. The field is encoded as the Radio Priority field of the Packet Channel Request (see sub-clause 11.2.5).

| | | | | | | | | +|

RLC_BLOCK_COUNT (8 bit field)
If present, the RLC_BLOCK_COUNT field indicates the number of RLC data blocks that the mobile station wishes to transfer (assuming a CS-1 coding).

This field is encoded as a binary number as shown:

bit
8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 9 RLC data blocks
0 0 0 0 0 0 0 1 10 RLC data blocks
. . .
1 1 1 1 1 1 1 1 264 RLC data blocks
| 0 0 0 0 0 0 0 0 | 9 RLC data blocks | 0 0 0 0 0 0 0 1 | 10 RLC data blocks | . . . | | 1 1 1 1 1 1 1 1 | 264 RLC data blocks | +| 0 0 0 0 0 0 0 0 | 9 RLC data blocks | | | | | | | | +| 0 0 0 0 0 0 0 1 | 10 RLC data blocks | | | | | | | | +| . . . | | | | | | | | | +| 1 1 1 1 1 1 1 1 | 264 RLC data blocks | | | | | | | | + +### 12.7b Extended Channel Request Description + +The *Extended Channel Request Description* information element is sent by the mobile station to the network to request multiple uplink resources. + +**Table 12.7b.1: Extended Channel Request Description information elements** + +``` +< Extended Channel Request Description IE > ::= + < PFI : bit (7) > + < RADIO_PRIORITY : bit (2) > + < RLC_MODE : bit (1) > + { 0 | 1 < LLC_PDU_TYPE : bit (1) > } + { 0 | 1 < Extended Channel Request Description IE > } ; -- IE to be repeated only when needed and + -- when included in a Multiple TBF request message +``` + +**Table 12.7b.2: Extended Channel Request Description information element details** + +#### PFI (7 bit field) + +This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. + +#### RADIO\_PRIORITY (2 bit field) + +This field indicates the Radio Priority of the requested TBF. The field is encoded as the Radio Priority field of the Packet Channel Request (see sub-clause 11.2.5). + +#### RLC\_MODE (1 bit field) + +This field indicates the RLC mode of the requested TBF. + +- 0 RLC acknowledged mode +- 1 RLC unacknowledged mode + +#### LLC\_PDU\_TYPE (1 bit field) + +This field indicates the type of the first LLC PDU to be transmitted over the requested uplink TBF. If the TBF request is not for an LLC PDU then this field shall be omitted. + +- 0 LLC PDU is SACK or ACK +- 1 LLC PDU is not SACK or ACK + +## 12.8 Frequency Parameters + +The Frequency Parameters information element defines frequency parameters and a training sequence code (TSC), which may be allocated to a mobile station to define its channel configuration. All timeslots in the channel configuration of the mobile station shall use the same frequency parameters and training sequence code. + +NOTE: For COMPACT, for PDTCH/PACCH on primary and secondary carriers that are indicated in EXT\_FREQUENCY\_LIST by parameter INT\_FREQUENCY (see 3GPP TS 45.008), the TSCs should be equal to the BCC, as defined in 3GPP TS 23.003, otherwise the accuracy of interference measurement reporting may be compromised. + +The frequency parameters may consist of an ARFCN, defining a non-hopping radio frequency channel. The indirect encoding, the direct encoding 1 and the direct encoding 2 defines a hopping radio frequency channel. + +**Table 12.8.1: Frequency Parameters information elements** + +``` + +< Frequency Parameters IE > ::= + < TSC : bit (3) > + { 00 < ARFCN : bit (10) > + | 01 < Indirect encoding : < Indirect encoding struct > > + | 10 < Direct encoding 1 : < Direct encoding 1 struct > > + | 11 < Direct encoding 2 : < Direct encoding 2 struct > > } ; + +< Indirect encoding struct > ::= + < MAIO : bit (6) > + < MA_NUMBER : bit (4) > + { 0 | 1 < CHANGE_MARK_1 : bit (2) > + { 0 | 1 < CHANGE_MARK_2 : bit (2) > } } ; + +< Direct encoding 1 struct > ::= + < MAIO : bit (6) > + < GPRS Mobile Allocation : < GPRS Mobile Allocation IE > > ; + +< Direct encoding 2 struct > ::= + < MAIO : bit (6) > + < HSN : bit (6) > + < Length of MA Frequency List contents : bit (4) > + < MA Frequency List contents : octet (val(Length of MA Frequency List contents) + 3) > ; + +``` + +**Table 12.8.2: Frequency Parameters information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

TSC (3 bit field)
This field is the binary representation of the training sequence code, see 3GPP TS 45.002. Range: 0 to 7. A mobile station that supports the extended TSC sets (see 3GPP TS 45.002 [32]) shall associate this TSC with TSC set 1 unless otherwise indicated by the Primary TSC Set field within an assignment message or a handover command.

| +|

ARFCN (10 bit field)
This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS 45.005. Range 0 to 1023.

| +|

MAIO (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 45.002. Range 0 to 63.

| +|

MA_NUMBER (4 bit field)
This field is the binary reference to a GPRS mobile allocation received in either the PSI2 information, the SI13/PSI13 information or a previous assignment message, see sub-clause 5.5.1.6. Range: 0 to 15.

| +|

CHANGE_MARK_1 (2 bit field)
CHANGE_MARK_2 (2 bit field)
These fields are the binary representations of the allowed values for the PSI or SI change mark associated with the GPRS mobile allocation that the MA_NUMBER field refers to. Range: 0 to 3.

| +|

GPRS Mobile Allocation (information element)
The GPRS Mobile Allocation information element is defined in sub-clause 12.10a.

| +|

HSN (6 bit field)
This field is the binary representation of the hopping sequence number, see 3GPP TS 45.002. Range: 0 to 63.

| +|

MA Frequency List contents (variable length octet string)
This variable length octet string is the representation of a set of radio frequency channels defining a GPRS mobile allocation. The encoding of the octet string is defined by the value part of the type 4 information element Frequency List, defined in 3GPP TS 44.018. The allowed formats of the Frequency List information element are the bit map 0, 1024 range, 512 range, 256 range, 128 range and variable bit map formats.

| + +### 12.8.1 Abnormal cases + +If the indirect encoding is used, this information element may contain the CHANGE\_MARK\_1 and 2 fields. If one of these fields is present, the receiver shall verify the validity of the PSI or SI *change mark* associated with the GPRS mobile allocation that the MA\_NUMBER field refers to, see sub-clause 5.5.1.7. None of the CHANGE\_MARK\_1 and 2 fields shall be included if the MA\_NUMBER refers to a GPRS mobile allocation received in a previous assignment message. + +If the receiver detects that an inconsistency is contained in this information element, the information element shall be regarded as invalid. Such inconsistency may be that: + +- an invalid PSI or SI *change mark* is associated with the referred GPRS mobile allocation; +- an CHANGE\_MARK\_1 or 2 field is included and the MA\_NUMBER refers to a GPRS mobile allocation received in a previous assignment message; or +- an undefined MA\_NUMBER or an invalid GPRS Mobile Allocation is contained in this information element. + +If the inconsistency is due to an invalid PSI or SI *change mark* associated with the referred GPRS mobile allocation or an undefined MA\_NUMBER in the range 0 ñ 14, the mobile station shall initiate a *partial acquisition* of PBCCH or BCCH information (see sub-clause 5.5.1.4). It shall then obtain the PSI2 or SI13 information, which is concerned. + +### 12.8.2 Dual Carrier Frequency Parameters + +The Dual Carrier Frequency Parameters information element is used to define the frequency parameters for both carriers in a dual carrier configuration. It defines frequency parameters and a training sequence code (TSC), which may be allocated to a mobile station to define its channel configuration. All timeslots on each radio frequency channel in the channel configuration of the mobile station shall use the same frequency parameters and training sequence code. + +The dual carrier frequency parameters may consist of two ARFCNs, defining non-hopping radio frequency channels. The dual carrier indirect encoding, the dual carrier direct encoding 1 and the dual carrier direct encoding 2 define two hopping radio frequency channels. + +**Table 12.8.2.1: Dual Carrier Frequency Parameters information elements** + +``` +< Dual Carrier Frequency Parameters IE > ::= + < TSC : bit (3) > + { 00 + { 0 | 1 < ARFCN1 : bit (10) > + < ARFCN2 : bit (10) > } + | 01 < Indirect encoding : < Dual Carrier Indirect encoding struct > > + | 10 < Direct encoding 1 : < Dual Carrier Direct encoding 1 struct > > + | 11 < Direct encoding 2 : < Dual Carrier Direct encoding 2 struct > > } ; + +< Dual Carrier Direct encoding 1 struct > ::= + { 0 | 1 < MAIO1 : bit (6) > } + { 0 | 1 < MAIO2 : bit (6) > } + < GPRS Mobile Allocation : < GPRS Mobile Allocation IE > > ; + +< Dual Carrier Indirect encoding struct > ::= + { 0 | 1 < MAIO1 : bit (6) > } + { 0 | 1 < MAIO2 : bit (6) > } + < MA_NUMBER : bit (4) > + { 0 | 1 < CHANGE_MARK_1 : bit (2) > + { 0 | 1 < CHANGE_MARK_2 : bit (2) > } } ; + +< Dual Carrier Direct encoding 2 struct > ::= + { 0 | 1 < MAIO1 : bit (6) > } + { 0 | 1 < MAIO2 : bit (6) > } + < HSN : bit (6) > + < Length of MA Frequency List contents : bit (4) > + < MA Frequency List contents : octet (val(Length of MA Frequency List contents) + 3) > ; +``` + +**Table 12.8.2.2: Dual Carrier Frequency Parameters information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TSC (3 bit field)
This field is the binary representation of the training sequence code, see 3GPP TS 45.002. Range: 0 to 7. A mobile station that supports the extended TSC sets (see 3GPP TS 45.002 [32]) shall associate this TSC with TSC set 1 unless otherwise indicated by the Primary TSC Set field within an assignment message or a handover command. | +| ARFCN1 (10 bit field)
This field is the binary representation of the absolute radio frequency channel number (ARFCN) to be applied to carrier 1, as defined in 3GPP TS 45.005. Range 0 to 1023. | +| ARFCN2 (10 bit field)
This field is the binary representation of the absolute radio frequency channel number (ARFCN) to be applied to carrier 2, as defined in 3GPP TS 45.005. Range 0 to 1023. | +| MAIO1 (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO) to be applied to carrier 1, see 3GPP TS 45.002. Range 0 to 63. | +| MAIO2 (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO) to be applied to carrier 2, see 3GPP TS 45.002. Range 0 to 63. | +| MA_NUMBER (4 bit field)
This field is the binary reference to a GPRS mobile allocation received in either the PSI2 information, the SI13/PSI13 information or a previous assignment message, see sub-clause 5.5.1.6. Range: 0 to 15. | +| CHANGE_MARK_1 (2 bit field)
CHANGE_MARK_2 (2 bit field)
These fields are the binary representations of the allowed values for the PSI or SI change mark associated with the GPRS mobile allocation that the MA_NUMBER field refers to. Range: 0 to 3. | +| GPRS Mobile Allocation (information element)
The GPRS Mobile Allocation information element is defined in sub-clause 12.10a. | +| HSN (6 bit field)
This field is the binary representation of the hopping sequence number, see 3GPP TS 45.002. Range: 0 to 63. | +| MA Frequency List contents (variable length octet string)
This variable length octet string is the representation of a set of radio frequency channels defining a GPRS mobile allocation. The encoding of the octet string is defined by the value part of the type 4 information element Frequency List , defined in 3GPP TS 44.018. The allowed formats of the Frequency List information element are the bit map 0 , 1024 range , 512 range , 256 range , 128 range and variable bit map formats. | + +### 12.8.3 Pulse Format description + +This information element specifies on which, if any, radio frequency channels the mobile station shall transmit using the narrow pulse shaping filter or shall otherwise transmit using the wide pulse shaping filter with a specified spectrum mask (see 3GPP TS 45.004, 3GPP TS 45.005). The content of this information element is applicable only when one of UBS-5 to UBS-12 modulation and coding schemes is used. + +If this information element is not included in an assignment message and the mobile station is required to transmit using EGPRS2-B modulation and coding schemes UBS-5 to UBS-12, the mobile station shall use the wide pulse shaping filter option without tight spectrum mask on all frequencies in the mobile allocation (if hopping) or on the single frequency assigned (if non-hopping). + +**Table 12.8.3.1: Pulse Format information elements** + +``` + +< Pulse Format IE > ::= + { 0 < Pulse Format Coding 1 : bit (3) > + | 1 < Pulse Format Coding 2 : < Pulse Format Coding 2 struct > > }; + +< Pulse Format Coding 2 struct > ::= + { 0 < Pulse Format Bitmap Length : bit (7) > + < Pulse Format Bitmap: + bit (val (Pulse Format Bitmap Length) + 1) + & { { 1 | 01 | 00 } ** ! { bit** = } } > + | 1 < Non Hopping Carrier Pulse Format : 1 | 01 | 00 > + }; + +``` + +#### Pulse Format Coding 1 + +The pulse shaping filter format/spectrum mask to be used on the frequencies specified in the mobile allocation are as specified in the table below. Frequency 1 is the lowest frequency, and Frequency n is the highest frequency (when ordered according to the value of their frequency in Hz). + +Where 'W' is indicated, the wideband pulse option applies. + +Where 'N' is indicated, the narrowband pulse option applies. + +Where 'W2' is indicated, the wideband pulse with tighter spectrum mask applies. + +| bit | 1 | 2 | 3..(n-2) | n-1 | n | +|-------|----|----|----------|-----|----| +| 0 0 0 | W | W | W | W | W | +| 0 0 1 | W | W | W | W2 | N | +| 0 1 0 | N | W2 | W | W | W | +| 0 1 1 | N | W2 | W | W2 | N | +| 1 0 0 | N | N | N | N | N | +| 1 0 1 | W | W | W | W | W2 | +| 1 1 0 | W2 | W | W | W | W | +| 1 1 1 | W2 | W | W | W | W2 | + +#### Pulse Format Coding 2: + +#### Pulse Format Bitmap Length (7 bit field) + +Range 0 to 127 + +This field represents the length minus one of the **Pulse Format Bitmap** field. + +#### Pulse Format Bitmap (variable length bit field) + +This field comprises a bitmap with each codeword (comprising 1 or 2 bits) corresponding to a frequency specified in the mobile allocation, in increasing order of ARFCN value (except that ARFCN = 0, if included, is put last). + +- 1      Wide pulse shaping filter option without tight spectrum mask applies +- 0 1    Wide pulse shaping filter option with tight spectrum mask applies +- 0 0    Narrow pulse shaping filter option applies + +If the number of codewords in the bitmap is greater than the number of frequencies specified in the mobile allocation, the extra codewords shall be ignored. If the number of codewords in the bitmap is lower than the number of frequencies specified in the mobile allocation, the wide pulse shaping filter without tight spectrum mask shall apply for any frequency with no corresponding codeword. + +#### Non Hopping Carrier Pulse Format + +In the case of a non-hopping carrier, this field contains a single codeword that indicates which pulse format shall be used on the carrier. The meaning of the codeword values is identical as specified for the **Pulse Format Bitmap**. + +### 12.8.4 DLMC Frequency Parameters + +The DLMC Frequency Parameters information element defines frequency parameters allocated for a unique frequency parameter set associated with a DLMC configuration. + +**Table 12.8.4.1: DLMC Frequency Parameters information elements** + +``` +< DLMC Frequency Parameters IE > ::= + < TSC : bit (3) > + { 00 < ARFCN : bit (10) > + | 01 < DLMC Indirect encoding : < DLMC Indirect encoding struct > > + | 10 < DLMC Direct encoding 1 : < DLMC Direct encoding 1 struct > > + | 11 < DLMC Direct encoding 2 : < DLMC Direct encoding 2 struct > > } ; + +< DLMC Indirect encoding struct > ::= + < MA_NUMBER : bit (4) > + { 0 | 1 < CHANGE_MARK_1 : bit (2) > + { 0 | 1 < CHANGE_MARK_2 : bit (2) > } } ; + +< DLMC Direct encoding 1 struct > ::= + < GPRS Mobile Allocation : < GPRS Mobile Allocation IE > > ; + +< DLMC Direct encoding 2 struct > ::= + < HSN : bit (6) > + < Length of MA Frequency List contents : bit (4) > + < MA Frequency List contents : octet (val(Length of MA Frequency List contents) + 3) > ; +``` + +**Table 12.8.4.2: DLMC Frequency Parameters information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

TSC (3 bit field)

This field is the binary representation of the training sequence code, see 3GPP TS 45.002. Range: 0 to 7.

| +|

ARFCN (10 bit field)

This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS 45.005. Range 0 to 1023.

| +|

MA_NUMBER (4 bit field)

This field is the binary reference to a GPRS mobile allocation received in either the PSI2 information, the SI13/PSI13 information or a previous assignment message, see sub-clause 5.5.1.6. Range: 0 to 15.

| +|

CHANGE_MARK_1 (2 bit field)

CHANGE_MARK_2 (2 bit field)

These fields are the binary representations of the allowed values for the PSI or SI change mark associated with the GPRS mobile allocation that the MA_NUMBER field refers to. Range: 0 to 3.

| +|

GPRS Mobile Allocation (information element)

The GPRS Mobile Allocation information element is defined in sub-clause 12.10a.

| +|

HSN (6 bit field)

This field is the binary representation of the hopping sequence number, see 3GPP TS 45.002. Range: 0 to 63.

| +|

MA Frequency List contents (variable length octet string)

This variable length octet string is the representation of a set of radio frequency channels defining a GPRS mobile allocation. The encoding of the octet string is defined by the value part of the type 4 information element Frequency List, defined in 3GPP TS 44.018. The allowed formats of the Frequency List information element are the bit map 0, 1024 range, 512 range, 256 range, 128 range and variable bit map formats.

| + +## 12.9 Global Power Control Parameters + +The Global Power Control Parameters information element contains parameters the mobile station shall use to determine its TX power level. When provided, the MS shall use this information from the most recently received message. + +**Table 12.9.1: Global Power Control Parameters information elements** + +``` +< Global Power Control Parameters IE > ::= + < ALPHA : bit (4) > + < T_AVG_W : bit (5) > + < T_AVG_T : bit (5) > + < Pb : bit (4) > + < PC_MEAS_CHAN : bit (1) > + 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. + < N_AVG_I : bit (4) > ; +``` + +**Table 12.9.2: Global Power Control Parameters information element details** + +### ALPHA (4 bit field) + +This field is the binary representation of the parameter $\alpha$ for MS output power control in units of 0.1, see 3GPP TS 45.008. + +Range: 0 to 10. The ALPHA power control parameter field is coded according to the following table: + +| bit | | +|---------|----------------| +| 4 3 2 1 | | +| 0 0 0 0 | $\alpha = 0.0$ | +| 0 0 0 1 | $\alpha = 0.1$ | +| 0 0 1 0 | $\alpha = 0.2$ | +| : | : | +| 1 0 0 1 | $\alpha = 0.9$ | +| 1 0 1 0 | $\alpha = 1.0$ | + +All other values are reserved in this version of the protocol and shall be interpreted by the mobile station as $\alpha = 1.0$ . + +### T\_AVG\_W (5 bit field) + +The T\_AVG\_W parameter is a signal strength filter period for power control in packet idle mode. $2^{(k/2)} / 6$ multiframes, $k = 0, 1, 2, \dots, 25$ (see 3GPP TS 45.008). Values greater than 25 shall be interpreted as 25 by the mobile station. + +### T\_AVG\_T (5 bit field) + +The T\_AVG\_T parameter is a signal strength filter period for power control in packet transfer mode. $2^{(k/2)} / 6$ multiframes, $k = 0, 1, 2, \dots, 25$ (see 3GPP TS 45.008). Values greater than 25 shall be interpreted as 25 by the mobile station. + +### Pb (4 bit field) + +The Pb parameter is a power reduction value used by the BTS on PBCCH blocks and PCCCH blocks, relative to the output power used on BCCH. The field is coded according to the following table: + +| bit | | +|---------|-------------| +| 4 3 2 1 | | +| 0 0 0 0 | Pb = 0 dB | +| 0 0 0 1 | Pb = -2 dB | +| 0 0 1 0 | Pb = -4 dB | +| : | : | +| 1 1 1 1 | Pb = -30 dB | + +### PC\_MEAS\_CHAN (1 bit field) + +The PC\_MEAS\_CHAN parameter indicates where the mobile station shall measure the received power level on the downlink for the purpose of the uplink power control. + +| | | +|---|---------------------------------------------------------------| +| 0 | downlink measurements for power control shall be made on BCCH | +| 1 | downlink measurements for power control shall be made on PDCH | + +### **N\_AVG\_I** (4 bit field) + +The N\_AVG\_I parameter is an interfering signal strength filter constant for power control $2^{(k/2)}$ , $k=0, 1, \dots, 15$ (see 3GPP TS 45.008). + +Range: 0 to 15 + +## 12.9a GPRS Power Control Parameters + +The *GPRS Power Control Parameters* information element contains parameters the mobile station shall use to determine its TX power level. + +**Table 12.9a.1: GPRS Power Control Parameters information element** + +``` +< GPRS Power Control Parameters IE > ::= + < ALPHA : bit (4) > + < T_AVG_W : bit (5) > + < T_AVG_T : bit (5) > + < PC_MEAS_CHAN : bit > + < N_AVG_I : bit (4) > ; +``` + +**Table 12.9a.2: GPRS Power Control Parameters information element details** + +### **ALPHA** (4 bit field), + +### **T\_AVG\_W** (5 bit field), + +### **T\_AVG\_T** (5 bit field), + +### **PC\_MEAS\_CHAN** (1 bit field) and + +### **N\_AVG\_I** (4 bit field) + +These fields are defined in the *Global Power Control Parameters* information element, see sub-clause 12.9. + +## 12.10 Global TFI + +The Global TFI (Temporary Flow Identity) information element contains either an uplink TFI or a downlink TFI. The uplink or downlink TFI identifies a single Temporary Block Flow. + +**Table 12.10.1: Global TFI information elements** + +``` +< Global TFI IE > ::= + { 0 < UPLINK_TFI : bit (5) > + | 1 < DOWNLINK_TFI : bit (5) > } ; +``` + +**Table 12.10.2: Global TFI information element details** + +### **UPLINK\_TFI** (5 bit field) + +This field identifies an uplink TBF. This field is coded the same as the TFI field defined in sub-clause 12.15. + +### **DOWNLINK\_TFI** (5 bit field) + +This field identifies a downlink TBF. This field is coded the same as the TFI field defined in sub-clause 12.15. + +## 12.10a GPRS Mobile Allocation + +The GPRS Mobile Allocation information element defines a set of radio frequency channels and a hopping sequence number (HSN), which may be allocated to a mobile station to define its channel configuration. + +This information element may refer to a reference frequency list, or set of reference frequency lists defined in the PSI2 information. In case there is no such reference included in this information element, it refers to the cell allocation (CA) + +defined for the cell. The cell allocation is defined in the PSI2 information, if PBCCH is present in the cell, or in the SI information (see 3GPP TS 44.018), if PBCCH is not present in the cell. + +There are two alternative ways to encode the GPRS mobile allocation, using the MA\_BITMAP or the ARFCN index list. + +**Table 12.10a.1: GPRS Mobile Allocation information elements** + +``` +< GPRS Mobile Allocation IE > ::= + < HSN : bit (6) > + { 0 | 1 < RFL number list : < RFL number list struct > > } + { 0 < MA_LENGTH : bit (6) > + < MA_BITMAP : bit (val(MA_LENGTH) + 1) > + | 1 { 0 | 1 < ARFCN index list : < ARFCN index list struct > > } }; +< RFL number list struct > ::= + < RFL_NUMBER : bit (4) > + { 0 | 1 < RFL number list struct > }; +< ARFCN index list struct > ::= + < ARFCN_INDEX : bit (6) > + { 0 | 1 < ARFCN index list struct > }; +``` + +**Table 12.10a.2: GPRS Mobile Allocation information element details** + +### **HSN (6 bit field)** + +This field is the binary representation of the hopping sequence number, see 3GPP TS 45.002. Range: 0 to 63. + +### **RFL number list (construction)** + +This construction is a list specifying the referenced set of reference frequency lists for this information element. If the list is not included, this information element refers to the cell allocation defined for the cell. + +The number of radio frequency channels included in the referenced set of reference frequency lists or the referenced cell allocation (excluding any duplication of radio frequency channels) is denoted NF. The radio frequency channels shall be arranged by the receiver of this information element in the order of ascending ARFCN, except for ARFCN = 0, if included, which shall be put last. Each radio frequency channel shall then be assigned an ARFCN\_INDEX value, ranging from zero, for the first radio frequency channel, to NF-1, for the last radio frequency channel in the ordered set. + +#### **MA\_BITMAP (variable length, 1 to 64 bit, field)** + +This field is a bitmap representing the radio frequency channels belonging to the GPRS mobile allocation. The number of bit positions in MA\_BITMAP shall equal NF. The first bit position in MA\_BITMAP corresponds to ARFCN\_INDEX = NF-1, the last position corresponds to ARFCN\_INDEX = 0. Each bit position is coded: + +- 0 the corresponding radio frequency channel does not belong to the GPRS mobile allocation; +- 1 the corresponding radio frequency channel belongs to the GPRS mobile allocation. + +### **ARFCN index list (construction)** + +This construction is a list representing a set of radio frequency channels to be excluded from the definition of the GPRS mobile allocation. The GPRS mobile allocation is defined as consisting of the radio frequency channels included in the referenced set of reference frequency lists or the referenced cell allocation, except those represented by the ARFCN index list. If the list is not included, this information element defines a GPRS mobile allocation consisting of all radio frequency channels included in the referenced set of reference frequency lists or the referenced cell allocation, without exception. + +#### **RFL\_NUMBER (4 bit field)** + +This field is the binary reference to a reference frequency list provided in PSI2. Range 0 to 15. + +#### **ARFCN\_INDEX (6 bit field)** + +This field is the binary reference to a radio frequency channels in the referenced set of reference frequency lists or the referenced cell allocation. Range: 0 to NF-1. + +### 12.10a.1 Abnormal cases + +If the receiver of this information element detects any inconsistency between the encoding of this information element and the referenced frequency information (i.e. an MA\_BITMAP length or an ARFCN\_INDEX value out of range, or an undefined RFL\_NUMBER value), the information element shall be regarded as invalid. + +## 12.10b (void) + +## 12.10c (void) + +## 12.10d EGPRS Modulation and coding Scheme description + +This information element defines the modulation and coding scheme to be used. + +**Table 12.10d.1: EGPRS MCS information element details** + +| EGPRS modulation and coding scheme information element | | +|--------------------------------------------------------|----------| +| bits | | +| 4 3 2 1 | value | +| 0 0 0 0 | MCS-1 | +| 0 0 0 1 | MCS-2 | +| 0 0 1 0 | MCS-3 | +| 0 0 1 1 | MCS-4 | +| 0 1 0 0 | MCS-5 | +| 0 1 0 1 | MCS-6 | +| 0 1 1 0 | MCS-7 | +| 0 1 1 1 | MCS-8 | +| 1 0 0 0 | MCS-9 | +| 1 0 0 1 | MCS-5-7 | +| 1 0 1 0 | MCS-6-9 | +| 1 0 1 1
to
1 1 1 1 | reserved | + +In EGPRS2, this information element defines the modulation and coding scheme to be used. The value depends on the assigned EGPRS level, see sub-clause 12.10f. + +**Table 12.10d.2: EGPRS MCS information element details (EGPRS2-A)** + +| EGPRS modulation and coding scheme information element | | +|--------------------------------------------------------|----------| +| bits | | +| 4 3 2 1 | value | +| 0 0 0 0 | MCS-1 | +| 0 0 0 1 | MCS-2 | +| 0 0 1 0 | MCS-3 | +| 0 0 1 1 | MCS-4 | +| 0 1 0 0 | MCS-5 | +| 0 1 0 1 | MCS-6 | +| 0 1 1 0 | UAS-7 | +| 0 1 1 1 | UAS-8 | +| 1 0 0 0 | UAS-9 | +| 1 0 0 1 | UAS-10 | +| 1 0 1 0 | UAS-11 | +| 1 0 1 1
to
1 1 1 1 | reserved | + +Table 12.10d.3: EGPRS MCS information element details (EGPRS2-B) + +| EGPRS modulation and coding scheme information element | | +|--------------------------------------------------------|----------| +| bits | | +| 4 3 2 1 | value | +| 0 0 0 0 | MCS-1 | +| 0 0 0 1 | MCS-2 | +| 0 0 1 0 | MCS-3 | +| 0 0 1 1 | MCS-4 | +| 0 1 0 0 | UBS-5 | +| 0 1 0 1 | UBS-6 | +| 0 1 1 0 | UBS-7 | +| 0 1 1 1 | UBS-8 | +| 1 0 0 0 | UBS-9 | +| 1 0 0 1 | UBS-10 | +| 1 0 1 0 | UBS-11 | +| 1 0 1 1 | UBS-12 | +| 1 1 0 0
to
1 1 1 1 | reserved | + +## 12.10e RESEGMENT description + +The RESEGMENT field defines whether retransmitted uplink RLC data blocks shall be re-segmented or not. + +Table 12.10e.1: RESEGMENT information element details + +#### RESEGMENT (1 bit field) + +- 0 Retransmitted RLC data blocks shall not be re-segmented +- 1 Retransmitted RLC data blocks shall be re-segmented according to commanded MCS + +### 12.10f EGPRS Level description + +This information element defines the EGPRS level for this TBF and consequently the the set of modulation and coding schemes which shall be used. + +Table 12.10f.1: EGPRS Level information element details + +| EGPRS Level information element | | +|---------------------------------|----------| +| bits | | +| 2 1 | value | +| 0 0 | EGPRS | +| 0 1 | EGPRS2-A | +| 1 0 | EGPRS2-B | +| 1 1 | reserved | + +## 12.11 Packet Request Reference + +The purpose of the Packet Request Reference information element is to provide the information field sent in the Packet Channel Request (i.e. the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message) and the frame number, FN modulo 42432, in which the Packet Channel Request was received. + +Table 12.11.1: Packet Request Reference information elements + +``` +< Packet Request Reference IE > ::= + < RANDOM_ACCESS_INFORMATION value : bit (11) > + < FRAME_NUMBER : bit (16) > ; +``` + +**Table 12.11.2: Packet Request Reference information element details** + +| RANDOM_ACCESS_INFORMATION value (11 bit field) | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----|---|---|---|---|---|---|---|---|---| +| This is an unformatted 11 bit field. If the mobile station used the 11-bit message format in the Packet Channel Request, all 11 bits of this field are valid. Otherwise, only bits 8 through 1 are valid and bits 11 through 9 shall be set to '0' | | | | | | | | | | | | +| | Bit | | | | | | | | | | | +| | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 11-bit message format used | X | X | X | X | X | X | X | X | X | X | X | +| 8-bit message format used | 0 | 0 | 0 | X | X | X | X | X | X | X | X | + + + +| FRAME_NUMBER (16 bit field) | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------|--|--|--|--|--|--|--|--|--|--|--| +| This field is encoded the same as the Starting Time information element defined in 3GPP TS 44.018. | | | | | | | | | | | | + +## 12.12 Packet Timing Advance + +The Packet Timing Advance field describes the timing advance mode and timing advance value assigned to the mobile station. + +**Table 12.12.1: Packet Timing Advance information elements** + +| | +|-------------------------------------------------------| +| < Packet Timing Advance IE > ::= | +| { 0 1 < TIMING_ADVANCE_VALUE : bit (6) > } | +| { 0 1 < TIMING_ADVANCE_INDEX : bit (4) > } | +| < TIMING_ADVANCE_TIMESLOT_NUMBER : bit (3) > ; | + +**Table 12.12.2: Packet Timing Advance information element details** + +| TIMING_ADVANCE_VALUE (6 bit field) | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|--|--|--|--|--|--|--| +| If the TIMING_ADVANCE_VALUE field is present, the mobile station shall use the value contained therein after time defined in 3GPP TS 45.010. If the TIMING_ADVANCE_VALUE field is not present the mobile station shall not change its timing advance value. The Timing Advance value field is encoded the same as the Timing Advance value of the Timing Advance information element defined in 3GPP TS 44.018 | | | | | | | | | | | | +| TIMING_ADVANCE_INDEX (4 bit field) | | | | | | | | | | | | +| If the TIMING_ADVANCE_INDEX and TIMING_ADVANCE_TIMESLOT_NUMBER fields are present the mobile station shall begin operation of the Continuous Timing Advance procedure at the point in time denoted by the TBF starting time if present, otherwise after the reaction time specified in 3GPP TS 45.010.. If these two fields are not present the mobile station shall stop operation of the Continuous Timing Advance procedure. This information field is encoded as a binary representation of the Timing Advance Index defined in 3GPP TS 45.002.
Range 0 to 15. | | | | | | | | | | | | +| TIMING_ADVANCE_TIMESLOT_NUMBER (3 bit field) | | | | | | | | | | | | +| This field indicates the timeslot assigned for the Continuous Timing Advance procedure on the PTCCH. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010.
Range 0 to 7 | | | | | | | | | | | | + +### 12.12a Global Packet Timing Advance + +The Global Packet Timing Advance field describes the timing advance mode and timing advance value assigned to the mobile station for uplink and/or downlink TBF. + +**Table 12.12a.1: Global Packet Timing Advance information elements** + +``` +< Global Packet Timing Advance IE > ::= + { 0 | 1 < TIMING_ADVANCE_VALUE : bit (6) > } + { 0 | 1 < UPLINK_TIMING_ADVANCE_INDEX : bit (4) > + < UPLINK_TIMING_ADVANCE_TIMESLOT_NUMBER : bit (3) > } + { 0 | 1 < DOWNLINK_TIMING_ADVANCE_INDEX : bit (4) > + < DOWNLINK_TIMING_ADVANCE_TIMESLOT_NUMBER : bit (3) > } +``` + +**Table 12.12a.2: Global Packet Timing Advance information element details** + +#### **TIMING\_ADVANCE\_VALUE** (6 bit field) + +If the TIMING\_ADVANCE\_VALUE field is present, the mobile station shall use the value contained therein after time defined in 3GPP TS 45.010. If the TIMING\_ADVANCE\_VALUE field is not present the mobile station shall not change its timing advance value. The Timing Advance value field is encoded the same as the Timing Advance value of the Timing Advance information element defined in 3GPP TS 44.018 + +#### **UPLINK\_TIMING\_ADVANCE\_INDEX** (4 bit field) + +This field indicates the Timing Advance Index related to Uplink TBF. This information field is encoded as a binary representation of the Timing Advance Index defined in 3GPP TS 45.002. Range 0 to 15. + +#### **UPLINK\_TIMING\_ADVANCE\_TIMESLOT\_NUMBER** (3 bit field) + +This field indicates the timeslot assigned for the Continuous Timing Advance procedure on the PTCCH related to Uplink TBF. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010. Range 0 to 7 + +#### **DOWNLINK\_TIMING\_ADVANCE\_INDEX** (4 bit field) + +This field indicates the Timing Advance Index related to Downlink TBF. This information field is encoded as a binary representation of the Timing Advance Index defined in 3GPP TS 45.002. Range 0 to 15. + +#### **DOWNLINK\_TIMING\_ADVANCE\_TIMESLOT\_NUMBER** (3 bit field) + +This field indicates the timeslot assigned for the Continuous Timing Advance procedure on the PTCCH related to Downlink TBF. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010. Range 0 to 7 + +If Timing Advance Index and Timing Advance Timeslot Number are present for any of the TBFs already existing or to be established with this message, the mobile station shall begin operation of the Continuous Timing Advance procedure at the point in time denoted by the TBF starting time if present, otherwise within the reaction time specified in 3GPP TS 45.010. + +If Timing Advance Index and Timing Advance Timeslot Number are not present for any of the TBFs already existing or to be established with this message, the mobile station shall stop operation of the Continuous Timing Advance procedure. + +### 12.12b Packet Extended Timing Advance + +The Packet Extended Timing Advance field is a 2 bit field used to support Extended Timing Advance. These two bits represent the two most significant bits of the timing advance value to be applied by the mobile station. The coding of the timing advance value is defined in the Timing Advance IE defined in 3GPP TS 44.018. The mapping of the two bits of the Packet Extended Timing Advance field is defined as follows: + +#### Bit + +- 1 bit 7 of the Timing Advance IE defined in 3GPP TS 44.018 +- 2 bit 8 of the Timing Advance IE defined in 3GPP TS 44.018 + +The least significant bits of a timing advance value is provided the TIMING\_ADVANCE\_VALUE field in either a Packet Timing Advance IE (sub-clause 12.12) or a Global Packet Timing Advance IE (sub-clause 12.12a). If the least significant bits of the timing advance value is not provided in the message, then the Packet Extended Timing Advance field shall be ignored. + +## 12.13 Power Control Parameters + +The Power Control Parameters information element contains parameters the mobile station shall use to determine its TX power level. + +**Table 12.13.1: Power Control Parameters information elements** + +``` +< Power Control Parameters IE > ::= + < ALPHA : bit (4) > + { 0 | 1 < GAMMA_TN0 : bit (5) > } + { 0 | 1 < GAMMA_TN1 : bit (5) > } + { 0 | 1 < GAMMA_TN2 : bit (5) > } + { 0 | 1 < GAMMA_TN3 : bit (5) > } + { 0 | 1 < GAMMA_TN4 : bit (5) > } + { 0 | 1 < GAMMA_TN5 : bit (5) > } + { 0 | 1 < GAMMA_TN6 : bit (5) > } + { 0 | 1 < GAMMA_TN7 : bit (5) > }; +``` + +**Table 12.13.2: Power Control Parameters information element details** + +### ALPHA (4 bit field) + +For encoding and description see the Global Power Control Parameters IE. + +### GAMMA\_TN0 (5 bit field) + +### GAMMA\_TN1 (5 bit field) + +### GAMMA\_TN2 (5 bit field) + +### GAMMA\_TN3 (5 bit field) + +### GAMMA\_TN4 (5 bit field) + +### GAMMA\_TN5 (5 bit field) + +### GAMMA\_TN6 (5 bit field) + +### GAMMA\_TN7 (5 bit field) + +The GAMMA\_TN0..7 fields are the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. GAMMA\_TN0 contains the gamma value for timeslot number 0, GAMMA\_TN1 contains the gamma value for timeslot number 1, etc. The GAMMA\_TN0..7 field is coded according to the following table: + +#### bit + +5 4 3 2 1 + +0 0 0 0 0 $\Gamma_{CH} = 0$ dB + +0 0 0 0 1 $\Gamma_{CH} = 2$ dB + +... + +1 1 1 1 0 $\Gamma_{CH} = 60$ dB + +1 1 1 1 1 $\Gamma_{CH} = 62$ dB + +## 12.14 PRACH Control Parameters + +The purpose of the PRACH Control Parameters information element is to provide parameters used to control the PRACH utilization. + +**Table 12.14.1: PRACH Control Parameters information elements** + +``` +< PRACH Control Parameters IE > ::= + < ACC_CONTR_CLASS : bit (16) > + < MAX_RETRANS : bit (2) > * 4 + < S : bit (4) > + < TX_INT : bit (4) > + { 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 }; +``` + +**Table 12.14.2: PRACH Control Parameters information element details** + +### TX\_INT (4 bit field) + +Number of slots to spread transmission of the random access. The field is coded according to the following table: + +| bit | | +|---------|--------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | 2 slots used to spread transmission | +| 0 0 0 1 | 3 slots used to spread transmission | +| 0 0 1 0 | 4 slots used to spread transmission | +| 0 0 1 1 | 5 slots used to spread transmission | +| 0 1 0 0 | 6 slots used to spread transmission | +| 0 1 0 1 | 7 slots used to spread transmission | +| 0 1 1 0 | 8 slots used to spread transmission | +| 0 1 1 1 | 9 slots used to spread transmission | +| 1 0 0 0 | 10 slots used to spread transmission | +| 1 0 0 1 | 12 slots used to spread transmission | +| 1 0 1 0 | 14 slots used to spread transmission | +| 1 0 1 1 | 16 slots used to spread transmission | +| 1 1 0 0 | 20 slots used to spread transmission | +| 1 1 0 1 | 25 slots used to spread transmission | +| 1 1 1 0 | 32 slots used to spread transmission | +| 1 1 1 1 | 50 slots used to spread transmission | + +### S (4 bit field) + +S is a parameter used for calculation of the minimum number of slots between two successive Channel request messages. The field is coded according to the following table: + +| bit | | +|---------|---------| +| 4 3 2 1 | | +| 0 0 0 0 | S = 12 | +| 0 0 0 1 | S = 15 | +| 0 0 1 0 | S = 20 | +| 0 0 1 1 | S = 30 | +| 0 1 0 0 | S = 41 | +| 0 1 0 1 | S = 55 | +| 0 1 1 0 | S = 76 | +| 0 1 1 1 | S = 109 | +| 1 0 0 0 | S = 163 | +| 1 0 0 1 | S = 217 | + +All other values reserved. + +### **MAX\_RETRANS** (2 bit field for each Radio Priority 1..4) + +Indicates for each Radio Priority level 1 to 4 the maximum number of retransmissions allowed. Radio Priority 1 represents the highest priority. The field is coded with two bits per Radio Priority level according to the following table where the first two bits refer to Radio Priority 1, the second two bits to Radio Priority 2, etc.: + +| | | +|-----|---------------------------| +| bit | | +| 2 1 | | +| 0 0 | 1 retransmission allowed | +| 0 1 | 2 retransmissions allowed | +| 1 0 | 4 retransmissions allowed | +| 1 1 | 7 retransmissions allowed | + +### **PERSISTENCE\_LEVEL** (4 bit field for each Radio Priority 1..4) + +The PERSISTENCE\_LEVEL field indicates the values of the access persistence level P(i) for each Radio Priority i (i = 1..4) where Radio Priority 1 represents the highest Radio Priority of an LLC PDU to be transmitted. + +| | | +|---------|----------------------| +| bits | | +| 4 3 2 1 | | +| 0 0 0 0 | persistence level 0 | +| 0 0 0 1 | persistence level 1 | +| 0 0 1 0 | persistence level 2 | +| 0 0 1 1 | persistence level 3 | +| 0 1 0 0 | persistence level 4 | +| ... | | +| 1 1 1 0 | persistence level 14 | +| 1 1 1 1 | persistence level 16 | + +### **ACC\_CONTR\_CLASS** (16 bit field) + +Access Control Class N (bit 1-16) (see octet 3 and 4 of the RACH Control Parameters IE in 3GPP TS 44.018). For a mobile station with Access Control Class = N access is not barred if the Access Control Class N bit is coded with a '0'; N = 0, 1, ..., 9, 11, ..., 15. Bit 11 = the EC bit is the Emergency Call Allowed coded as specified in 3GPP TS 44.018. + +| | | | | | | | | | | | | | | | | | +|----------|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---| +| Bits: | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Class N: | 15 | 14 | 13 | 12 | 11 | EC | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | + +## 12.15 Temporary Flow Identity (TFI) + +The Temporary Flow Identity (TFI) uniquely identifies either a single uplink Temporary Block Flow (TBF) or a single downlink Temporary Block Flow (TBF). + +**Table 12.15.1: UPLINK\_TFI information element details** + +### **UPLINK\_TFI** (5 bit field) + +The Temporary Flow Identity field identifies an uplink Temporary Block Flow (TBF). This field is encoded as a binary number. + +Range 0 to 31 + +**Table 12.15.2: DOWNLINK\_TFI information element details** + +### **DOWNLINK\_TFI** (5 bit field) + +The Temporary Flow Identity field identifies a downlink Temporary Block Flow (TBF). This field is encoded as a binary number. + +Range 0 to 31 + +## 12.16 Temporary Logical Link Identity (TLLI)/G-RNTI + +The Temporary Logical Link Identity (TLLI) is associated with the GPRS subscriber. TLLI is defined in 3GPP TS 23.003. + +The TLLI codespace is re-used in some messages and contains the first 28 bits of the G-RNTI as defined in 3GPP TS 23.003. + +**Table 12.16.1: TLLI information element details** + +### **TLLI/G-RNTI (32 bit field)** + +The TLLI / G-RNTI field is encoded as a binary number. + +Range 0 to 4294967295 + +## 12.16a GERAN Radio Network Temporary Identity (G-RNTI) + +The G-RNTI (GERAN Radio Network Temporary Identity) is allocated to an MS at the RRC layer having a RRC connection and identifies the MS within GERAN. It is used by the RLC/MAC layer for contention resolution and to identify an MS. + +NOTE: The RRC layer uses the G-RNTI. + +< G-RNTI IE > ::= + +< **S-RNTI** : bit (20) > + +< **Serving BSC Identity** : bit (12) > ; + +#### **Serving BSC identity (12 bit field)** + +This field identifies the mobile station's serving BSC in GERAN. + +### **S-RNTI (20 bit field)** + +This field identifies the mobile station within the serving BSC. + +## 12.17 Temporary Queueing Identifier (TQI) + +The Temporary Queueing Identifier (TQI) field identifies a mobile station during the queueing procedure. The contents of this field are operator defined. + +**Table 12.17.1: TQI information element details** + +### **TQI (16 bit field)** + +The Temporary Queueing Identifier field is an unformatted field. + +## 12.18 TIMESLOT\_ALLOCATION + +The TIMESLOT\_ALLOCATION field indicates the timeslots for use during a TBF, the timeslots carrying a PCCCH or the timeslots for which feedback is provided by a time-based encoded PAN field. + +**Table 12.18.1: TIMESLOT\_ALLOCATION information element details** + +### **TIMESLOT\_ALLOCATION** (8 bit field) + +This information field indicates the timeslots assigned for use during the TBF, the timeslots carrying a PCCCH or the timeslots for which feedback is provided by a time-based encoded PAN field. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least one timeslot must be assigned. When used to indicate the timeslots constituting PDCH-pairs for which feedback is provided by a time-based encoded PAN field (for TBFs in RTTI or MTI configuration configuration) an even number of timeslots must be indicated. + +0 Timeslot is not assigned + +1 Timeslot is assigned + +## 12.19 (void) + +## 12.20 PAGE\_MODE + +The PAGE\_MODE field controls the action of the mobile station belonging to the paging subgroup corresponding to the paging subchannel. + +**Table 12.20.1 : PAGE\_MODE information element details** + +### **PAGE\_MODE** (2 bit field) + +bit + +2 1 value + +0 0 Normal Paging + +0 1 Extended Paging + +1 0 Paging Reorganization + +1 1 Same as before + +## 12.21 Starting Frame Number Description + +There are two types of encoding for this IE : Relative Frame Number or Absolute Frame Number. + +**Table 12.21.1: Starting Frame Number Description information element** + +``` +< Starting Frame Number Description IE > ::= +{ 0 < Absolute Frame Number Encoding > +| 1 < Relative Frame Number Encoding > } ; +``` + +If the mobile station is in packet transfer mode during the block immediately before the starting time and the lowest numbered PDCH assigned to the MS is different immediately before and after the starting time then the mobile station shall be ready to receive or transmit no later than one radio block from the starting time (see 3GPP TS 45.002). + +### 12.21.1 Absolute Frame Number Encoding + +In this case, the field is encoded as the 16-bit Starting Time IE defined in 3GPP TS 44.018, and the value of the Starting FN is obtained directly. + +If the Starting FN is not aligned to the start of a block period and the mobile station is in packet transfer mode during the TDMA immediately before the Starting FN, then the mobile station shall align the starting time to the next block boundary and continue to use the currently assigned allocation upto the next block boundary. + +### 12.21.2 Relative Frame Number Encoding + +In this case, the field indicates the delay, relative to the first TDMA frame (N) of the RLC/MAC block containing the Starting Time field, before the assigned or requested resource becomes valid. + +The value of this field is the 13 bit binary representation of the integer k, from which the offset to be applied to N can be derived. + +The value of the Starting Frame Number is calculated as follows: + +| For (k mod 3) equal to: | The value of the Starting Frame Number is: | +|-------------------------|----------------------------------------------------------------------------| +| 0 or 1 | $N + 4 + 4k + (k \text{ div3})$ , $N + 5 + 4k + (k \text{ div3})$ (NOTE 1) | +| 2 | $N + 5 + 4k + (k \text{ div3})$ | +| $0 \leq k \leq 8191$ | | + +EXAMPLE: Starting Frame Number Description (13-bit field): + +| | | | +|-------|---------------|---------------------------------------------------| +| k = 1 | 0000000000001 | block with first TDMA frame number = N+8 or N+9 | +| k = 2 | 0000000000010 | block with first TDMA frame number = N+13 | +| k = 3 | 0000000000011 | block with first TDMA frame number = N+17 or N+18 | + +NOTE 1: In these cases, only one of the frame numbers $N+4+4k+k \text{ div3}$ or $N+5+4k+k \text{ div3}$ is valid, because the other corresponds to an idle frame, depending on the position of the block in the multi-frame. + +NOTE 2: The value of (k+1) gives the number of relative blocks. The maximum number of relative blocks is therefore 8 192; this value was chosen according to the interval of time encoded by the Starting Time IE in 3GPP TS 44.018 (32 024 frames). + +NOTE 3: The value (k=0) should not be used, so as to leave time for the MS to analyse the message and get ready to receive or transmit. + +## 12.22 (void) + +## 12.23 Cell Identification + +The *Cell Identification* information element is used to uniquely identify the cell. + +**Table 12.23.1: Cell Identification information element** + +| | | +|--------------------------------------------------------|--------------------------| +| < Cell Identification IE > ::= | | +| < Location Area Identification IE : octet (5) > | -- 3GPP TS 44.018 | +| < RAC : bit (8) > | | +| < Cell Identity IE : octet (2) > ; | -- 3GPP TS 44.018 | + +**Table 12.23.2: Cell Identification information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location Area Identity IE (5 octet field)
This field is coded using the V format of the type 3 information element Location Area Identification defined in 3GPP TS 44.018. | +| RAC (8 bit field)
This field is the binary representation of the Routing Area Code, see 3GPP TS 23.003. | +| Cell Identity IE (2 octet field)
This field is coded using the V format of the type 3 information element Cell Identity defined in 3GPP TS 44.018. | + +## 12.24 GPRS Cell Options + +The *GPRS Cell Options* information element is used to control a set of cell options related to GPRS. + +This information element may include a nested *Extension Bit* information element to allow future extension of cell option parameters. + +**Table 12.24.1: GPRS Cell Options information element** + +``` + +< GPRS Cell Options IE > ::= + < NMO : bit (2) > + < T3168 : bit (3) > + < T3192 : bit (3) > + < DRX_TIMER_MAX : bit (3) > + < ACCESS_BURST_TYPE : bit > + < CONTROL_ACK_TYPE : bit > + < BS_CV_MAX : bit (4) > + { 0 | 1 < PAN_DEC : bit (3) > + < PAN_INC : bit (3) > + < PAN_MAX : bit (3) > } + -- Optional extension information: + { 0 | 1 < Extension Length : bit (6) > + < bit (val(Extension Length) + 1) > + & { < Extension Information > ! { bit ** = } } > } ; + +< Extension Information > ::= + { { -- R99 extension: + { 0 | 1 - EGPRS supported by the cell if the choice bit is set to '1' + < EGPRS_PACKET_CHANNEL_REQUEST : bit > + < BEP_PERIOD : bit (4) > } + < PFC_FEATURE_MODE : bit > + < DTM_SUPPORT : bit > + < BSS_PAGING_COORDINATION : bit > } + { -- REL-4 extension: + < CCN_ACTIVE : bit > + < NW_EXT_UTBF : bit > } + { -- REL 6 extension: + < MULTIPLE_TBF_CAPABILITY : bit > + < EXT_UTBF_NODATA : bit > + < DTM_ENHANCEMENTS_CAPABILITY : bit > + { 0 -- MBMS procedures not supported by the cell if the choice bit is set to '0' + | 1 -- MBMS procedures supported by the cell if the choice bit is set to '1' + < DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT : bit > + < MNCI_SUPPORT : bit > } } + { -- Rel-7 extension: + < REDUCED_LATENCY_ACCESS : bit > } + { -- Rel-10 extension: + < NMO_I_ALTERNATE : bit > } + < spare bit > ** } // ; + -- Extension information may be truncated between released versions of the protocol. + -- The receiver shall assume the value zero for any truncated bit. + +``` + +**Table 12.24.2: GPRS Cell Options information element details** + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|--------------------------------------|---------|------------------------------------------|---|-----------------------------|---|--------|------------------------------|---|---|-------------------------------|---|---|-----------|---------|---|---|---|------|---|---|---|-------|---|---|---|--------|---|---|---|--------|---|---|---|--------| +|

NMO (2 bit field)
This field is the binary representation of the Network Mode of Operation, see 3GPP TS 23.060:

Bit

21
00Network Mode of Operation I
01Network Mode of Operation II
10Network Mode of Operation III
11Reserved.
| 2 | 1 | | 0 | 0 | Network Mode of Operation I | 0 | 1 | Network Mode of Operation II | 1 | 0 | Network Mode of Operation III | 1 | 1 | Reserved. | | | | | | | | | | | | | | | | | | | | | | +| 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | Network Mode of Operation I | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | Network Mode of Operation II | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | Network Mode of Operation III | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | Reserved. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

T3168 (3 bit field)
This field is the binary representation of the timeout value of timer T3168. Range: 0 to 7. The timeout value is given as the binary value plus one in units of 500 ms.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

T3192 (3 bit field)
This field is the binary representation of the timeout value of timer T3192. Range: 0 to 7. The timeout value is given in the following table. In the case of 0 ms, the timer is not started and the mobile station shall consider T3192 as immediately expiring and follow procedures defined in sub-clauses 9.3.2.6 and 9.3.3.5:

Bit

321
000500 ms
0011000 ms
0101500 ms
0110 ms
10080 ms
101120 ms
110160 ms
111200 ms
| 3 | 2 | 1 | | 0 | 0 | 0 | 500 ms | 0 | 0 | 1 | 1000 ms | 0 | 1 | 0 | 1500 ms | 0 | 1 | 1 | 0 ms | 1 | 0 | 0 | 80 ms | 1 | 0 | 1 | 120 ms | 1 | 1 | 0 | 160 ms | 1 | 1 | 1 | 200 ms | +| 3 | 2 | 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 0 | 500 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 0 | 1 | 1000 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | 0 | 1500 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 1 | 1 | 0 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 0 | 80 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 0 | 1 | 120 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 0 | 160 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 1 | 1 | 200 ms | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

DRX_TIMER_MAX (3 bit field)
This field is the binary representation of the parameter DRX_TIMER_MAX. Range: 0 to 7. The parameter value is given as two taken to the power of the binary value minus one (2^{(bv-1)}) in units of 1 second. The binary value zero indicates the parameter value zero (i.e, the parameter takes the values: 0, 1 s, 2 s, 4 s, .. 64 s.)

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

ACCESS_BURST_TYPE (1 bit field)
The ACCESS_BURST_TYPE field indicates if the 8 or 11 bit format shall be used in the PACKET CHANNEL REQUEST message, the PS HANDOVER ACCESS message, the PTCCH uplink block (3GPP TS 44.004) and in the PACKET CONTROL ACKNOWLEDGMENT message when the format is four access bursts. The field is coded according to the following table:

08-bit format shall be used
111-bit format shall be used
| 0 | 8-bit format shall be used | 1 | 11-bit format shall be used | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | 8-bit format shall be used | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | 11-bit format shall be used | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

CONTROL_ACK_TYPE (1 bit field)
This field is the binary representation of the default format of the PACKET CONTROL ACKNOWLEDGMENT message:

0default format is four access bursts
1default format is RLC/MAC control block.
| 0 | default format is four access bursts | 1 | default format is RLC/MAC control block. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 0 | default format is four access bursts | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1 | default format is RLC/MAC control block. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

BS_CV_MAX (4 bit field)
This field is the binary representation of the parameter BS_CV_MAX. Range: 0 to 15. The value BS_CV_MAX=0 shall be interpreted as value BS_CV_MAX=1 for calculation of T3200 and N3104max values.

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

PAN_DEC (3 bit field)
This field is the binary representation of the parameter PAN_DEC. If the field is not included, the default value 0 shall be used. Range: 0 to 7.

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

PAN_INC (3 bit field)

This field is the binary representation of the parameter PAN_INC. If the field is not included, the default value 0 shall be used. Range: 0 to 7.

| +|

PAN_MAX (3 bit field)

This field defines the maximum value allowed for counter N3102.

bit
3 2 1
0 0 0 maximum value allowed for counter N3102 is 4
0 0 1 maximum value allowed for counter N3102 is 8
...
1 1 1 maximum value allowed for counter N3102 is 32

If the PAN_MAX field is not included, the default value 0 (i.e. N3102 max = 4) shall be used.

| +|

EGPRS_PACKET_CHANNEL_REQUEST (1 bit field)

0 EGPRS capable MSs shall use EGPRS PACKET CHANNEL REQUEST message for uplink TBF establishment on the PRACH when there is a PBCCH in the cell or on the RACH when there is no PBCCH in the cell.

1 EGPRS capable MSs shall use two phase packet access with PACKET CHANNEL REQUEST message on the PRACH for uplink TBF establishment when there is a PBCCH in the cell. EGPRS capable MSs shall use two phase packet access with CHANNEL REQUEST message on the RACH when there is no PBCCH in the cell.

As an exception, a mobile station that has enabled PEO (see 3GPP TS 43.064 [5]) shall always send an EGPRS PACKET CHANNEL REQUEST message with access type 'PEO One Phase Access Request' (see Table 11.2.5a.4) on the RACH regardless of the value of this field.

| +|

BEP_PERIOD (4 bit field)

This field is applicable in EGPRS TBF mode. For the definition of this field, refer to 3GPP TS 45.008.

| +|

PFC_FEATURE_MODE (1 bit field)

0 The network does not support packet flow context procedures.
1 The network supports packet flow context procedures.

| +|

DTM_SUPPORT (1 bit field)

This field indicates whether the cell supports DTM or not. It is coded as follows:

0 The cell does not support DTM procedures.
1 The cell supports DTM procedures.

| +|

CCN_ACTIVE (1 bit field)

This field indicates whether CCN is enabled in the cell or not. It is coded as follows:

0 CCN is disabled in the cell.
1 CCN is enabled in the cell.

| +|

NW_EXT_UTBF (1 bit field)

This field indicates whether the network supports the extended uplink TBF mode:

0 The extended uplink TBF mode is not supported by the network.
1 The extended uplink TBF mode is supported by the network.

| +|

BSS_PAGING_COORDINATION (1 bit field)

This field indicates the network support of CS paging co-ordination in packet transfer mode during network mode of operation II and III. This field shall be ignored by the mobile station during network mode of operation I or by a mobile station capable of DTM in a cell supporting DTM procedures, in which cases Circuit-Switched paging coordination in packet transfer mode shall be provided by the network. It is coded as follows:

0 The cell does not support Circuit-Switched paging coordination
1 The cell supports Circuit-Switched paging coordination

| + +### **MULTIPLE\_TBF\_CAPABILITY** (1 bit field) + +This field indicates whether or not the cell supports multiple TBF procedures for A/Gb mode: + +- 0 The cell does not support multiple TBF procedures. +- 1 The cell supports multiple TBF procedures. + +### **EXT\_UTBF\_NODATA** (1 bit field) + +This field indicates whether the mobile station during extended uplink TBF mode may refrain from sending PACKET UPLINK DUMMY CONTROL BLOCK messages when there is no other RLC/MAC block ready to send in an uplink radio block allocated by the network. + +- 0 The mobile station shall send a PACKET UPLINK DUMMY CONTROL BLOCK message when there is no other RLC/MAC block ready to send in an uplink radio block allocated by the network. +- 1 The mobile station may refrain from sending a PACKET UPLINK DUMMY CONTROL BLOCK message when there is no other RLC/MAC block ready to send in an uplink radio block allocated by the network. + +### **DTM\_ENHANCEMENTS\_CAPABILITY** (1 bit field) + +This field indicates whether the cell supports enhanced DTM CS establishment and enhanced DTM CS release or not. It is coded as follows: + +- 0 The cell does not support enhanced DTM CS establishment and enhanced DTM CS release procedures. +- 1 The cell supports enhanced DTM CS establishment and enhanced DTM CS release procedures. + +### **DEDICATED\_MODE\_MBMS\_NOTIFICATION\_SUPPORT** (1 bit field) + +This field indicates whether the cell supports Dedicated Mode MBMS Notification or not. It is coded as follows: + +- 0 The cell does not support the Dedicated Mode MBMS Notification procedures. +- 1 The cell supports the Dedicated Mode MBMS Notification procedures. + +### **MNCI\_SUPPORT** (1 bit field) + +This field indicates whether the cell supports the distribution of MBMS NEIGHBOURING CELL INFORMATION messages. It is coded as follows: + +- 0 The cell does not support the distribution of MBMS NEIGHBOURING CELL INFORMATION messages +- 1 The cell supports the distribution of MBMS NEIGHBOURING CELL INFORMATION messages + +### **REDUCED\_LATENCY\_ACCESS** (1 bit field) + +This field indicates whether the cell supporting the EGPRS PACKET CHANNEL REQUEST message also supports "One Phase Access Request by Reduced Latency MS", see sub-clause 7.1.2.1. + +- 0 The cell does not support "One Phase Access Request by Reduced Latency MS". +- 1 The cell supports "One Phase Access Request by Reduced Latency MS". + +### **NMO\_I\_ALTERNATE** (1 bit field) + +This field applies only to mobile stations which have the parameter "NMO\_I\_Behaviour" set to the value of "1" in the NAS configuration Management Object as specified in 3GPP TS 24.368 [50] or in the USIM file NASCONFIG as specified in 3GPP TS 31.102 [51] (the USIM file having priority if both parameters exist). + +- 0 The mobile station shall use the Network Mode of Operation indicated in the NMO field. +- 1 The mobile station shall use Network Mode of Operation I irrespective of the value in the NMO field. + +## 12.25 PCCCH Organization Parameters + +The *PCCCH Organization Parameters* information element is used to control the organization of PCCCHs present in the cell. This information element contains general PCCCH organization parameters. + +**Table 12.25.1: PCCCH Organization Parameters information element** + +``` +< PCCCH Organization Parameters IE > ::= + < BS_PCC_REL : bit > + < BS_PBCCH_BLKS : bit (2) > + < BS_PAG_BLKS_RES : bit (4) > + < BS_PRACH_BLKS : bit (4) > ; +``` + +**Table 12.25.2: PCCCH Organization Parameters information element details** + +### BS\_PCC\_REL (1 bit field) + +The BS\_PCC\_REL field indicates if set = 1 that the last PDCH carrying PCCCH and PBCCH will be released shortly. All mobile stations on PCCCH shall then as soon as this information has been received return to CCCH and there obey the information sent on BCCH as specified in 3GPP TS 44.018. If the field is set = 0, no channel release is pending. + +### BS\_PBCCH\_BLKS (2 bit field) + +The BS\_PBCCH\_BLKS field indicates the number of blocks allocated to the PBCCH in the multiframe. The field is coded as the binary representation of BS\_PBCCH\_BLKS as defined in 3GPP TS 45.002 minus 1. + +### BS\_PAG\_BLKS\_RES (4 bit field) + +The BS\_PAG\_BLKS\_RES field indicates the number of blocks on each PDCH carrying the PCCCH per multiframe where neither PPCH nor PBCCH should appear. The field is coded as the binary representation of BS\_PAG\_BLKS\_RES as defined in 3GPP TS 45.002. Range: 0-10. The BS\_PAG\_BLKS\_RES value shall fulfil the condition that is defined in 3GPP TS 45.002. If the condition is not fulfilled, then the behaviour of the mobile station is implementation dependent. + +### BS\_PRACH\_BLKS (4 bit field) + +The BS\_PRACH\_BLKS field indicates the number of blocks reserved in a fixed way to the PRACH channel on any PDCH carrying PCCCH (see 3GPP TS 45.002). The field is coded as the binary representation of BS\_PRACH\_BLKS as defined in 3GPP TS 45.002. Range: 0-12. All other values are reserved and shall be interpreted as no Block reserved for PRACH. + +## 12.26 Extension Bits IE + +The *Extension Bits* information element is used to provide a generalized means for possible future extension within a message. This information element is variable length and contains the length indicator and spare bits. + +**Table 12.26.1: Extension Bits information element** + +``` +< Extension Bits IE > ::= + < extension length : bit (6) > + < spare bit (val(extension length)+1) > ; +``` + +## 12.27 Non GPRS Cell Options IE + +The *Non GPRS Cell Options IE* is used to provide mobile stations operating in mode A or B with a repeated subset of BCCH information required for entering dedicated, group receive or group transmit mode. + +**Table 12.27.1: Non GPRS Cell Options information element** + +| | | +|----------------------------------------------------------------|---------------------------------------------------------------------------| +| < Non GPRS Cell Options IE > ::= | | +| < ATT : bit > | -- Attach/Detach allowed | +| { 0 1 < T3212 : bit (8) > } | -- Time-out value for periodic update | +| < NECI : bit > | -- Half rate support | +| < PWRC : bit > | -- Power Control indicator | +| < DTX : bit (2) > | -- DTX indicator | +| < RADIO-LINK-TIMEOUT : bit (4) > | -- Supervisory timer for RR connection | +| < BS-AG-BLKS-RES : bit (3) > | -- number of blocks reserved for access grant | +| < CCCH-CONF : bit (3) > | -- physical channel configuration for CCCH | +| < BS-PA-MFRMS : bit (3) > | -- number of 51 multiframes between
-- transmission of paging messages | +| < MAX-RETRANS : bit (2) > | -- maximum number of retransmissions | +| < TX-INTEGER : bit (4) > | -- number of slots to spread transmission | +| < EC : bit > | -- emergency call allowed | +| < MS-TXPWR-MAX-CCCH : bit (5) > | -- maximum Tx power level | +| -- Optional extension information: | | +| { 0 1 < Extension Length : bit (6) > | | +| < bit (val(Extension Length) + 1) | | +| & { ! { bit ** = } } > } ; | | +| < Extension Information > ::= | | +| < ECSC : bit > | -- Early Classmark Sending Control | +| < 3G ECSC : bit > | -- 3G Early Classmark Sending Restriction | +| < spare bit > ** ; | | + +**Table 12.27.2: Non GPRS Cell Options information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| For detailed descriptions of all elements see 3GPP TS 44.018. | +| If the optional T3212 parameter is not included, no periodic updating shall be performed. | +| ECSC (1 bit field)
This field defines the Early Classmark Sending Control. | +| 0     Early Classmark Sending is forbidden
1     Early Classmark Sending is allowed | +| If the optional ECSC parameter is not included, early classmark sending is allowed. For a detailed description see 3GPP TS 44.018. | +| 3G ECSC (1 bit field)
This field defines the 3G Early Classmark Sending Restriction. | +| 0     Neither UTRAN nor cdma2000 classmark change message shall be sent with the Early Classmark Sending
1     The sending of UTRAN and CDMA2000 Classmark Sending messages is controlled by the Early Classmark Sending Control parameter | +| If the optional 3G Early Classmark Sending Restriction parameter is not included, the default value '0' shall be assumed. For a detailed description see 3GPP TS 44.018. | + +## 12.28 LSA Parameters + +The *LSA Parameters* information element is used for cell reselection by SoLSA mobile stations. The IE contains a list of LSA\_ID(s) corresponding either to the entries in the 'Add Frequency list struct' defined in the Packet Cell Change Order message and in Packet Measurement Order message or to the entries in the Neighbour Cell Parameters when used in the packet System Information 3 and 3bis messages. Some entries in the 'LSA parameters IE' may be empty. In case there are too few entries in the 'LSA parameters IE', empty entries shall be added at the end. In case there are too many entries in the 'LSA parameters IE', the last shall be discarded. + +**Table 12.28.1: LSA Parameters information element** + +``` +< LSA Parameters IE > ::= + < NR_OF_FREQ_OR_CELLS : bit (5) >: + { < LSA ID information : < LSA ID information struct >> * (val(NR_OF_FREQ_OR_CELLS)) }; + +< LSA ID information struct > ::= + { 1 { 0 < LSA_ID : bit (24) > + | 1 < ShortLSA_ID : bit (10) > } } ** 0 ; +``` + +**Table 12.28.2: LSA Parameters information element details** + +### LSA\_ID (24 bit field) + +The purpose of the LSA\_ID field is to identify a LSA. The LSA ID value field is coded as specified in 3GPP TS 23.003. + +### Short LSA\_ID (10 bit field) + +The purpose of the Short LSA\_ID field is to identify a LSA. The LSA ID defined by the Short LSA\_ID is a LSA\_ID as specified in 3GPP TS 23.003 with bit 0 set to "0" bit 1 to 10 set to the value of the Short LSA\_ID field (LSB in bit 1, MSB in bit 10) and bit 11 to 23 set to "0". + +## 12.29 COMPACT reduced MA + +**Table 12.29.1: COMPACT reduced MA information element** + +``` +< COMPACT reduced MA IE > ::= + < Length of Reduced MA bitmap : bit (7) > + < Reduced MA bitmap : bit( val( Length of Reduced MA bitmap ) ) > + { 0 | 1 < MAIO_2 : bit(6) > }; +``` + +**Table 12.29.2: COMPACT reduced MA information element details** + +### Length of Reduced MA bitmap (7 bit field) + +This field is the binary representation of the length (in bits) of the field Reduced MA bitmap. If set to 0, then no reduced Mobile Allocation is used. Range 0 to 127. + +### **Reduced MA bitmap** (bitmap) + +This field gives the reduced Mobile Allocation. + +This bitmap uses the list of frequencies given in the current Mobile Allocation, i.e. the Mobile Allocation used by the mobile for the assigned TBF. These radio frequency channels shall be arranged in the order of ascending ARFCN, except for ARFCN = 0, if included, which shall be put last. + +The first bit position in the reduced MA bitmap corresponds to the last ARFCN put in the list, the last bit position corresponds to the first ARFCN put in the list. Each bit position is coded: + +- 0 the corresponding radio frequency channel does not belong to the reduced MA; +- 1 the corresponding radio frequency channel belongs to the reduced MA. + +### **MAIO\_2** (6 bit field) + +This field is present when a reduced MA is used, indicating more than one frequency. + +This parameter is the binary representation of the mobile allocation index offset (MAIO) to be used on blocks using a reduced Mobile Allocation. + +Range 0 to 63. + +## 12.30 MS Radio Access Capability 2 + +The MS Radio Access Capability 2 information element is used to provide the radio part of the network with information concerning radio aspects of the mobile station. The contents may affect the manner in which the network handles the operation of the mobile station. + +For the indication of the radio access capabilities the following conditions shall apply (see 3GPP TS 24.008 for the definition of the parameters): + +- Among the three Access Technology Types GSM 900-P, GSM 900-E and GSM 900-R the MS shall include only one access technology type denoting the GSM 900 band it supports. +- Due to shared radio frequency channel numbers between GSM 1800 and GSM 1900, the mobile station should provide the relevant radio access capability for either GSM 1800 band OR GSM 1900 band, not both. +- One of two different coding forms shall be used by the mobile station when indicating its radio access capabilities to the network: the regular coding is where all capabilities are indicated explicitly within an *Access capabilities struct* for each signalled access technology and the alternative coding where access technologies with same capabilities are indicated within the *Additional access technologies struct* (see 3GPP TS 24.008). +- If the alternative coding by using the Additional access technologies struct is chosen by the mobile station, the mobile station shall indicate its radio access capability for the serving BCCH frequency band in the first included *Access capabilities struct* if this information element is not sent in response to an Access Technologies Request from the network or if none of the requested Access Technology Types is supported by the mobile station - see note 3. Otherwise, the mobile station shall include the radio access capabilities for the frequency bands it supports in the order of priority requested by the network as specified in sub-clause 7.1.3.2. +- If this information element is sent during a GPRS TBF establishment, the mobile station should indicate as many as possible of its supported Access Technology Types. The maximum number of indicated Access Technology Types depends on the remaining bits left in the RLC/MAC message containing the MS Radio Access Capability 2 IE. The radio access capability for the serving BCCH frequency band shall be part of the indicated technologies, the inclusion of any other radio access capability is a mobile station implementation option. +- If this information element is sent during an EGPRS TBF establishment, the mobile station shall indicate its supported Access Technology Types within the ones that are requested by the network or the access technology of the serving BCCH frequency band, as specified by the relevant procedures. +- If the first instance of radio access capabilities information for a supported access technology type fits in its entirety using the *Access capabilities struct* of the MS Radio Access Capability 2 IE sent within the PACKET RESOURCE REQUEST message, the mobile station may use the alternative coding for encoding other access technology types that are provided within either the PACKET RESOURCE REQUEST message or the ADDITIONAL MS RADIO ACCESS CAPABILITIES message. In the case where the ADDITIONAL MS RADIO ACCESS CAPABILITIES message is sent to the network, the first Access Technology Type may be set to "1111". + +- If message size limitations prevent the first instance of access capabilities information for a supported access technology type from being provided in its entirety using the *Access capabilities struct* of the MS Radio Access Capability 2 IE sent within the PACKET RESOURCE REQUEST message, the mobile station shall: + - For this instance of access technology type, include as much of the access capabilities information as possible that can fit within the *Access capabilities struct* of the MS Radio Access Capability 2 IE sent within the PACKET RESOURCE REQUEST message. At minimum the mobile station shall provide up to and including its R99 access capabilities information within the *Access capabilities struct*. See note 1. + - For this instance of access technology type, include the entire access capabilities information using the *Access capabilities struct* of the MS Radio Access Capability 2 IE sent within the ADDITIONAL MS RADIO ACCESS CAPABILITIES message (if this message is sent to the network). See note 2. + +NOTE 1: The mobile station has to set the ADDITIONAL MS RAC INFORMATION AVAILABLE bit to 1 in the PACKET RESOURCE REQUEST message to signal that the instance of radio access capabilities provided in this message is incomplete - see sub-clauses 7.1.3.2 and 11.2.16. + +NOTE 2: Additional instances of access capabilities information for other access technology types may be described using either the *Access capabilities struct* (regular coding) or the *Additional access technologies struct* (alternative coding). + +NOTE 3: If the radio access capability for the serving BCCH frequency band has been included in its entirety in the PACKET RESOURCE REQUEST message, it should not be provided again in the ADDITIONAL MS RADIO ACCESS CAPABILITIES message, except in the cases specified in sub-clause 7.1.3.2.1 where this message is sent in response to a request from the network. + +**Table 12.30.1: MS Radio Access Capability 2 information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------| +| 
< MS Radio Access Capability 2 IE > ::=   < MS RA capability > : < MS RA capability value part struct > ;
| +|----------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.30.2: MS Radio Access Capability 2 information element details** + +### **MS RA capability** + +This information element is coded as defined by the *MS RA capability value part* defined in the *MS Radio Access Capability* IE defined in 3GPP TS 24.008. When this information element is sent, all spare bits shall be suppressed by the transmitter. + +## 12.31 UTRAN FDD Target cell + +The *UTRAN FDD Target cell* information element contains the description of a UTRAN FDD Target cell. + +**Table 12.31.1: UTRAN FDD Target cell information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< UTRAN FDD Target cell IE > ::=   < FDD-ARFCN : bit (14) >   < Diversity : bit >   { 0   1 < Bandwidth_FDD : bit (3) > }   < SCRAMBLING_CODE : bit (9) > ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.31.2: UTRAN FDD Target cell information element details** + +### **FDD\_ARFCN (14 bit field)** + +This information element is defined as the UARFCN in 3GPP TS 25.101. + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Diversity (1 bit field)
This parameter indicates if diversity is applied for the cell:
Bit
0 Diversity is not applied for this cell
1 Diversity is applied for this cell.

| +|

Bandwidth_FDD (3 bit field)
This information element will be used for future releases. It shall not be sent in this version of the protocol. When missing, this indicates the present FDD bandwidth. When present, this shall not be considered as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly.

| +|

Scrambling Codes (9 bit field)
This parameter indicates the Primary Scrambling Code as defined in 3GPP TS 25.331.

| + +## 12.32 UTRAN TDD Target cell + +The *UTRAN TDD Target cell* information element contains the description of a UTRAN TDD Target cell. + +**Table 12.32.1: *UTRAN TDD Target cell* information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< UTRAN TDD Target cell IE > ::=   < TDD-ARFCN : bit (14) >   < Diversity TDD : bit >   { 0   1 < Bandwidth_TDD : bit (3) > }   < Cell Parameter : bit (7) >   < Sync Case TSTD : bit > ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.32.2: *UTRAN TDD Target cell* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

TDD_ARFCN (14 bit field)
This information element is defined as the UARFCN in 3GPP TS 25.102.

| +|

Bandwidth_TDD (3bit field)
This information element refers to 3GPP TS 25.331.
Bit
321
000 3.84Mcps
001 1.28Mcps
All other values shall not be sent. All other values shall not be interpreted as an error; indices of the 3G Neighbour Cell list shall be incremented accordingly (but no reporting can be performed). When missing, this indicates 3,84 Mcps.

| +|

Diversity TDD (1 bit field)
This parameter indicates if SCTD (see 3GPP TS 25.224) is applied for the cell:
Bit
0 SCTD is not applied for this cell
1 SCTD is applied for this cell.

| +|

Cell Parameter (7 bit field)
This parameter is defined in 3GPP TS 25.223.

| + +### **Sync Case TSTD** (1 bit field) + +For 3.84 Mcps TDD, this parameter is defined in 3GPP TS 25.223. + +### Bit + +- 0 Sync Case 1 +- 1 Sync Case 2 + +For 1.28 Mcps TDD, this parameter indicates if TSTD (see 3GPP TS 25.224) is applied for the cell: + +### Bit + +- 0 TSTD is not applied for this cell +- 1 TSTD is applied for this cell. + +## 12.33 Temporary Mobile Group Identity (TMGI) + +The Temporary Mobile Group Identity (TMGI) identifies an MBMS service. The TMGI is defined in 3GPP TS 24.008. + +The Temporary Mobile Group Identity information element always contains an MBMS SERVICE ID. In case the TMGI originates from another PLMN than the local one, the MCC (Mobile Country Code) and the MNC (Mobile Network Code) of that originating PLMN shall also be present. + +**Table 12.33.1: TMGI information element** + +``` +< TMGI IE > ::= +{ 0 -- without MCC and MNC parameters + < MBMS SERVICE ID : bit (24) > +| 1 -- with MCC and MNC parameters + < MBMS SERVICE ID : bit (24) > + < MCC : bit (12) > + < MNC : bit (12) > } +``` + +**Table 12.33.2: TMGI information element details** + +### **MBMS SERVICE ID** (24 bit field) + +This field contains the identity of the MBMS service. The MBMS SERVICE ID is unique within a PLMN. + +### **MCC** (12 bit field) + +This field contains the Mobile Country Code of the originating PLMN. + +### **MNC** (12 bit field) + +This field contains the Mobile Network Code of the originating PLMN. + +## 12.34 MBMS Bearer Identity + +The MBMS Bearer Identity uniquely identifies an MBMS radio bearer on a PDCH. + +**Table 12.34.1: MBMS Bearer Identity information element details** + +### MBMS Bearer Identity (1-5 bit field) + +The MBMS Bearer Identity field assigns a TFI value, or a subset of a TFI value, which identifies an MBMS radio bearer on a PDCH. In case only a subset of a TFI value is assigned for the MBMS radio bearer, that subset corresponds to the most significant bit(s) of the TFI field. The length of this field is defined by the value of the *Length of MBMS Bearer Identity* field, whose value is defined by a 3 bit field (range 1 to 5). + +The MBMS Bearer Identity field is encoded as a binary number. + +Range: + +- 1 bit field 0 to 1 +- 2 bit field 0 to 3 +- 3 bit field 0 to 7 +- 4 bit field 0 to 15 +- 5 bit field 0 to 31 + +## 12.35 MS\_ID + +The MS\_ID uniquely addresses a mobile station on an MBMS radio bearer with an assigned uplink feedback channel. + +**Table 12.35.1: MS\_ID information element details** + +### MS\_ID (1-4 bit field) + +An MS\_ID is assigned to a mobile station for a given MBMS radio bearer with an uplink feedback channel. The length of the MS\_ID field is defined by the value, increased by 1, of the *Length Indicator of MS\_ID* field, whose value is defined by a 2 bit field (range 1 to 4). The sum of the length of the MBMS Bearer Identity field and of the length of the MS\_ID field is equal to 5, i.e. the length of the TFI field. + +The MS\_ID field is encoded as a binary number. + +Range: + +- 1 bit field 0 to 1 +- 2 bit field 0 to 3 +- 3 bit field 0 to 7 +- 4 bit field 0 to 15 + +## 12.36 MBMS Channel Parameters + +The MBMS Channel Parameters contain various parameters applicable to one or more MBMS sessions. + +**Table 12.36.1: MBMS Channel Parameters information element** + +``` +< MBMS Channel Parameters IE > ::= +{ + 0 -- counting is off + { 0 | 1 < MBMS p-t-m channel description : < MBMS p-t-m channel description IE > > + < MBMS Session Parameters List : < MBMS Session Parameters List IE >> } + 1 -- counting is on + { 0 | 1 < MPRACH description : < MPRACH description IE > > } } +``` + +**Table 12.36.2: MBMS Channel Parameters information element details** + +### MBMS p-t-m channel description + +This information element contains the MBMS p-t-m channel description of one or more MBMS sessions. This + +information element is defined in sub-clause 12.37. + +### MBMS Session Parameters List + +This information element contains a list of MBMS Session Parameters to use on the MBMS p-t-m channel provided in the MBMS p-t-m channel description. Each entry in this list is associated with a notified MBMS session as identified in the MBMS Sessions List for this MBMS p-t-m channel. The n-th entry in the MBMS Session Parameters list corresponds to the n-th notified MBMS Session in the MBMS Sessions List. This information element is defined in sub-clause 12.40. + +### MPRACH description + +This information element contains the description of the MPRACH on which the MBMS packet access procedure is initiated (see sub-clause 7.7.1). This information element is defined in sub-clause 12.38. + +## 12.37 MBMS p-t-m channel description + +The MBMS p-t-m channel description contains the p-t-m channel description for one or more MBMS sessions. + +**Table 12.37.1: MBMS p-t-m channel description information element** + +``` +< MBMS p-t-m channel description IE > ::= +{ 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } +< DL_TIMESLOT_ALLOCATION : bit (8) > ; +``` + +**Table 12.37.2: MBMS p-t-m channel description information element details** + +### Frequency Parameters + +If this information element is not present, the same frequency as for the PCCCH shall be used. This information element is defined in sub-clause 12.8. + +#### DL\_TIMESLOT\_ALLOCATION (8 bit field) + +This field is defined in sub-clause 12.18. + +## 12.38 MPRACH description + +The MPRACH description contains the MPRACH parameters to be used if MPRACH is indicated in an MBMS notification. + +**Table 12.38.1: MPRACH description information element** + +``` +< MPRACH description IE > ::= +{ 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } +< MPRACH_TIMESLOT NUMBER : bit (3) > +< USF : bit (3) > +{ 0 | 1 < MPRACH Control Parameters : < MPRACH Control Parameters IE > > } ; +``` + +**Table 12.38.2: MPRACH description information element details** + +### Frequency Parameters + +If this information element is not present, the same frequency as for the PCCCH shall be used. This information element is defined in sub-clause 12.8. + +#### MPRACH\_TIMESLOT NUMBER (3 bit field) + +This field identifies the timeslot number of the PDCH where the MPRACH is located. + +#### USF (3 bit field) + +This field identifies the USF value that identifies the MPRACH on the defined PDCH. + +### **MPRACH Control Parameters** + +This information element, if present, defines the access control parameters to be used on the MPRACH. This information element is defined in sub-clause 12.41. + +## 12.39 MBMS Sessions List + +The MBMS Session List contains a list of MBMS sessions, identified by their TMGI, and if available MBMS Session Identity. + +**Table 12.39.1: MBMS Sessions List information element** + +``` +< MBMS Session List IE > ::= + { 1 < TMGI : < TMGI IE >> + { 0 | 1 < MBMS Session Identity : bit (8) > } ** 0; +``` + +**Table 12.39.2: MBMS Sessions List information element** + +### **TMGI** + +This information element contains the Temporary Mobile Group Identity of an MBMS service. This information element is encoded as defined in sub-clause 12.33. + +### **MBMS Session Identity** (8 bit field) + +This field contains the MBMS Session Identity of the concerned MBMS session. + +## 12.40 MBMS Session Parameters List + +The MBMS Session Parameters List contains a list of MBMS Bearer IDs, Estimated Session Durations, MBMS Radio Bearer Starting Times, EGPRS Windows Sizes and NPM Transfer Times. + +**Table 12.40.1: MBMS Session Parameters List information element** + +``` +< MBMS Session Parameters List IE > ::= + { 1 < Length of MBMS Bearer Identity : bit (3) > -- Configurations '000', '110' and '111' are reserved + < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) > + < Estimated Session Duration : bit (8) > + { 0 | 1 < MBMS Radio Bearer Starting Time : bit (16) > } + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE >> } + { 0 | 1 < NPM Transfer Time : bit (5) > } ** 0; +``` + +**Table 12.40.2: MBMS Session Parameters List information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Length of MBMS Bearer Identity (3 bit field)
This field indicates the length of the MBMS Bearer Identity for the concerned MBMS session. Any value from 1 to 5 inclusive is allowed. All other values are reserved. | +| MBMS Bearer Identity (1-5 bit field)
This field contains the Bearer identity for the concerned MBMS session. This information element is defined in sub-clause 12.34. | +| Estimated Session Duration (8 bit field)
This field contains an estimation of either the duration for the concerned MBMS session or, if the MBMS session is ongoing, the remaining duration for the concerned MBMS session. This information element is defined in sub-clause 12.44. | +| MBMS Radio Bearer Starting Time (16 bit field)
This field contains a starting time that indicates the frame number from which the data transfer on the assigned MBMS radio bearer may start for the concerned MBMS session. The MBMS Radio Bearer Starting Time is encoded as the value part of the type 3 information element Starting Time in 3GPP TS 44.018. | +| EGPRS Window Size
This information element defines the EGPRS Window Size for the concerned MBMS session and is defined in sub-clause 12.5.2. | +| NPM Transfer Time (5 bit field)
This field defines the NPM Transfer Time limitation for the concerned MBMS session and is defined in sub-clause 12.45a. | + +## 12.41 MPRACH Control Parameters + +The purpose of the MPRACH Control Parameters information element is to provide parameters used to control the MPRACH utilization. + +**Table 12.41.1: MPRACH Control Parameters information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< MPRACH Control Parameters IE > ::=   { 0   1 < ACC_CONTR_CLASS : bit (16) > }   { 0   1 < MAX_RETRANS : bit (2) > }   < S : bit (4) >   { 0   1 < TX_INT : bit (4) > }   { 0   1 < PERSISTENCE_LEVEL : bit (4) > };
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.41.2: MPRACH Control Parameters information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TX_INT (4 bit field)
Number of slots to spread transmission of the random access. This information element is encoded as defined in sub-clause 12.14. | +| S (4 bit field)
S is a parameter used for calculation of the minimum number of slots between two successive Channel request messages. This information element is encoded as defined in sub-clause 12.14. | +| MAX_RETRANS (2 bit field)
Indicates the maximum number of retransmissions allowed. This information element is encoded as defined in sub-clause 12.14. | + +### **PERSISTENCE\_LEVEL (4 bit field)** + +The PERSISTENCE\_LEVEL field indicates the values of the access persistence level. This information element is encoded as defined in sub-clause 12.14. + +### **ACC\_CONTR\_CLASS (16 bit field)** + +Access Control Class N (bit 1-16) (see octet 3 and 4 of the RACH Control Parameters IE in 3GPP TS 44.018). This information element is encoded as defined in sub-clause 12.14. + +## 12.42 PS Handover Radio Resources + +This information element provides the radio resources assigned for PS services in the new cell and is included within the PS HANDOVER COMMAND message. + +**Table 12.42.1: PS Handover Radio Resources information element** + +``` + +< PS Handover Radio Resources IE > ::= +{ 0 | 1 < Handover Reference : bit (8) > } +< ARFCN : bit (10) > +< SI : bit (2) > +< NCI : bit (1) > +< BSIC : bit (6) > +{ 0 | 1 < CCN_ACTIVE : bit (1) > } +{ 0 | 1 < 3G_CCN_ACTIVE : bit (1) > } +{ 0 | 1 < CCN Support Description : < CCN Support Description struct >> } +< Frequency Parameters : < Frequency Parameters IE > > +< NETWORK_CONTROL_ORDER : bit (2) > +{ 0 | 1 < Global Packet Timing Advance : < Global Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } } +< EXTENDED_DYNAMIC_ALLOCATION : bit (1) > -- Only used in uplink +< RLC_RESET : bit (1) > +{ 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } +{ 0 | 1 < Uplink Control Timeslot : bit (3) > } +{ 0 < GPRS mode : < GPRS mode struct > > +| 1 < EGPRS mode : < EGPRS mode struct > > } ; + +< CCN Support Description struct > ::= +< Number_Cells : bit (7) > +{ CCN_SUPPORTED : bit } * (val(Number_Cells)) ; + +< GPRS mode struct > ::= +-- Uplink TBFs +{ { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink Assignment : < Uplink TBF Assignment struct > > } ** 0 } +-- Downlink TBFs +{ 1 < Downlink Assignment : < Downlink Assignment struct > > } ** 0 } ; + +< EGPRS mode struct > ::= +-- Uplink TBFs +{ { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink Assignment : < Uplink TBF Assignment struct > > } ** 0 } +-- Downlink TBFs +{ 0 | 1 + { 0 | 1 { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } } + { 1 < Downlink Assignment : < Downlink Assignment struct > > } ** 0 } ; + +``` + +``` + +< Uplink TBF Assignment struct > ::= -- Recursive for multiple TBFs +{ 0 | 1 < PFI : bit (7) > } +< RLC_MODE : bit (1) > +< TFI Assignment : bit (5) > +{ 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } +{ 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } +{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } +< USF_GRANULARITY : bit (1) > +{ 0 + | 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > } + -- The timeslots assigned to the TBF are all the timeslots assigned + -- in the Global Timeslot description + -- The timeslots assigned to the TBF are a subset of all the + -- timeslots assigned in the Global Timeslot description. Where + -- N is the number of timeslots assigned to the MS in the Global + -- Timeslot description +{ 0 < USF_ALLOCATION : bit (3) > -- The same USF is valid on all timeslots assigned to the TBF +| 1 < USF_ALLOCATION : bit (3) > -- Different USF(s) assigned + -- USF assignment on the lowest numbered timeslot + -- assigned to the TBF +{ 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) ; + -- USFs on subsequent timeslots assigned to the TBF: + -- A '0' (respectively a '1' followed by a USF value) + -- means same (respectively different) USF value as the + -- USF on the next lower numbered timeslot assigned to + -- the TBF. Where M is the amount of timeslots assigned + -- to the TBF in the TBF_TIMESLOT_ALLOCATION if + -- present, else in the Global Timeslot description. + +< Downlink Assignment struct > ::= -- Recursive for multiple TBFs +< TIMESLOT_ALLOCATION : bit (8) > +{ < Downlink TBF assignment : < Downlink TBF assignment struct > > } ; + +< Downlink TBF assignment struct > ::= +{ 0 | 1 < PFI : bit (7) > } +< RLC_MODE : bit (1) > +< TFI Assignment : bit (5) > +< CONTROL_ACK : bit (1) > +{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } ; + +< Timeslot description struct > ::= +{ 0 + | 1 < MS_TIMESLOT_ALLOCATION : bit (8) > + -- without power control params + -- with power control params + < ALPHA : bit (4) > + { 0 | 1 < GAMMA_TN0 : bit (5) > } + { 0 | 1 < GAMMA_TN1 : bit (5) > } + { 0 | 1 < GAMMA_TN2 : bit (5) > } + { 0 | 1 < GAMMA_TN3 : bit (5) > } + { 0 | 1 < GAMMA_TN4 : bit (5) > } + { 0 | 1 < GAMMA_TN5 : bit (5) > } + { 0 | 1 < GAMMA_TN6 : bit (5) > } + { 0 | 1 < GAMMA_TN7 : bit (5) > } } ; + +``` + +**Table 12.42.2: PS Handover Radio Resources information element details** + +### **Handover Reference** (8 bit field) + +This field contains the reference value to be used when performing PS Handover. The field is encoded as the contents of the Handover Reference information element as defined in 3GPP TS 44.018. + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

SI (2 bit field)
The Synchronization Indication (SI) field indicates which type of PS Handover is to be performed.

Bit
2 1
0 0 Non-synchronized
0 1 Synchronized
1 0 Pre-synchronised
1 1 reserved

| +|

NCI (1 bit field)
The Normal Cell Indication (NCI) field indicates how the MS shall behave in case of out of range timing advance values.

Bit
1
0 Out of range timing advance is ignored
1 Out of range timing advance shall trigger a handover failure procedure.

| +|

ARFCN (10 bit field)

This field contains the BCCH frequency of the new cell. This field is encoded as the ARFCN defined in 3GPP TS 44.018.

Range: 0 to 1023.

| +|

BSIC (6 bit field)
This field contains the BSIC of the new cell. The BSIC field is coded as the "Base Station Identity Code" defined in 3GPP TS 23.003.

| +|

CCN_ACTIVE (1 bit field)
For description and encoding, see the Packet Cell Change Order message.

| +|

3G_CCN_ACTIVE (1 bit field)
For description and encoding, see the Packet Cell Change Order message.

| +|

CCN Support Description

CCN_SUPPORTED (1 bit field)
For description and encoding, see the Packet Cell Change Order message.

| +|

Frequency Parameters
This information element is defined in sub-clause 12.8.

| +|

EXTENDED_DYNAMIC_ALLOCATION (1 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

NETWORK_CONTROL_ORDER (2 bit field)
For description and encoding, see the Packet Measurement Order message.

| +|

P0 (4 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

PR_MODE (1 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

Global Packet Timing Advance
This information element is defined in sub-clause 12.12a

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

RLC_RESET (1 bit field)

This information element indicates whether or not all RLC entities used to support the given TBFs in the old cell shall be reset to support the TBFs allocated for the corresponding PFCs in the new cell:

0 RLC is not reset (the RLC state machines are maintained across PS handover)
1 RLC is reset (the RLC state machines are not maintained across PS handover)

If this field is set to '1', then after successful completion of the PS Handover procedure, the mobile shall consider all TBFs which were ongoing when the PS Handover Command message was received to have been implicitly released.

| +|

Packet Extended Timing Advance (2 bit field)

This field is defined in sub-clause 12.12b.

| +|

Uplink Control Timeslot (3 bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

CHANNEL_CODING_COMMAND (2 bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

EGPRS Window Size

This information element is defined in sub-clause 12.5.2.

| +|

EGPRS Modulation and Coding Scheme

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

BEP_PERIOD2 (4 bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)

For description and encoding, see the Multiple TBF Downlink Assignment message.

| +|

PFI (7 bit field)

This field shall only be included for TBFs if both the network and the mobile station support multiple TBFs. This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.01

| +|

TFI Assignment (5 bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

USF_GRANULARITY (1 bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

TBF_TIMESLOT_ALLOCATION (N bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

USF_ALLOCATION (3 bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

RLC_MODE (1 bit field)

For description and encoding, see the Multiple TBF Uplink Assignment message or the Multiple TBF Downlink Assignment message. If the RLC_RESET field indicates that any given RLC entity is not reset across PS handover then the mobile station shall ignore this field and use the same RLC mode that was used for the corresponding PFC in the old cell.

| +|

CONTROL_ACK (1 bit field)

If the RLC_RESET field indicates that RLC entities are reset, this field shall be set to '0'.
If multiple TBFs are supported by both network and mobile station and the RLC_RESET field indicates that RLC entities are not reset, this field shall be coded as specified for the Multiple TBF Downlink Assignment message.
If either the network or the mobile station does not support the multiple TBF feature and the RLC_RESET field indicates that RLC entities are not reset, this field shall be set to '1' if the network establishes a new downlink TBF for the mobile station whose timer T3192 is running. Otherwise this field shall be set to '0'.

| + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TIMESLOT_ALLOCATION (8 bit field)
For description and encoding, see the Multiple TBF Downlink Assignment message. | +| MS_TIMESLOT_ALLOCATION (8 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message.
As the explicit power control parameters are omitted for the allocated timeslots in the new cell, the mobile station shall use the default values (see 3GPP TS 45.008) for the power control parameters. | +| ALPHA (4 bit field)
For encoding and description see the Global Power Control Parameters IE. | +| GAMMA_TN (5 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode.

The list of NPM Transfer Time IEs in the Rel-7 additions is ordered as described by the loops in the earlier releases part. | +| EVENT_BASED_FANR (1 bit field)
For description and encoding, see the Multiple TBF Downlink Assignment message. | +| REPORTED TIMESLOTS (8 bit field)
For description and encoding, see the Multiple TBF Downlink Assignment message. | +| TSH (2 bit field)
For description and encoding, see the Multiple TBF Downlink Assignment message. | + +### 12.42a PS Handover Radio Resources 2 + +This information element provides the radio resources assigned for PS services for a dual carrier configuration or where the PS resources require the support of EGPRS2, Fast Ack/Nack Reporting or RTTI configurations in the new cell and is included within the PS HANDOVER COMMAND message. + +Table 12.42a.1: PS Handover Radio Resources 2 information element + +``` + +< PS Handover Radio Resources 2 IE > ::= + { 0 | 1 < Handover Reference : bit (8) > } + < ARFCN : bit (10) > + < SI : bit (2) > + < NCI : bit (1) > + < BSIC : bit (6) > + { 0 | 1 < CCN_ACTIVE : bit (1) > } + { 0 | 1 < 3G_CCN_ACTIVE : bit (1) > } + { 0 | 1 < CCN Support Description : < CCN Support Description struct >> } + { 0 | 1 -- Legacy IEs used + < Frequency Parameters C1 : < Frequency Parameters IE >> + { 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE >> } + | 10 -- Optimized Dual Carrier frequency parameters used + < Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE >> + ! < Frequency Parameters error: { 00 | 11 } bit(*) = < no string > > } -- reserved for future use + < NETWORK_CONTROL_ORDER : bit (2) > + { 0 | 1 < Global Packet Timing Advance : < Global Packet Timing Advance IE >> + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } } -- Only used in uplink + < RLC_RESET : bit (1) > + < EGPRS mode : < EGPRS mode 2 IE >> + + -- Optional extension information: + { 0 | 1 < Extension Length : bit (6) > + < bit (val(Extension Length) + 1) + & { < Extension Information > ! { bit ** = } } > } ; + +< CCN Support Description struct > ::= + < Number_Cells : bit (7) > + { CCN_SUPPORTED : bit } * (val(Number_Cells)) ; + +< Extension Information > ::= + -- Additions for REL-9 + { 0 | 1 MTTI_DOWNLINK_ASSIGNMENT_C1 : bit (1) } + { 0 | 1 MTTI_DOWNLINK_ASSIGNMENT_C2 : bit (1) } + { 0 | 1 MTTI_UPLINK_ASSIGNMENT_C1 : bit(1) } + { 0 | 1 MTTI_UPLINK_ASSIGNMENT_C2 : bit(1) } + -- Additions for REL-11 + { < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > } + < spare bit > ** // ; + -- Extension information may be truncated between released versions of the protocol. + -- The receiver shall assume the value zero for any truncated bit. + +``` + +Table 12.42a.2: PS Handover Radio Resources 2 information element details + +### **Handover Reference** (8 bit field) + +This field contains the reference value to be used when performing PS Handover. The field is encoded as the contents of the Handover Reference information element as defined in 3GPP TS 44.018. + +#### **ARFCN** (10 bit field) + +This field contains the BCCH frequency of the new cell. This field is encoded as the ARFCN defined in 3GPP TS 44.018. + +Range: 0 to 1023. + +#### **SI** (2 bit field) + +The Synchronization Indication (SI) field indicates which type of PS Handover is to be performed. + +Bit + +2 1 + +0 0 Non-synchronized + +0 1 Synchronized + +1 0 Pre-synchronised + +1 1 reserved + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

NCI (1 bit field)
The Normal Cell Indication (NCI) field indicates how the MS shall behave in case of out of range timing advance values.

Bit
1
0 Out of range timing advance is ignored
1 Out of range timing advance shall trigger a handover failure procedure.

| +|

BSIC (6 bit field)
This field contains the BSIC of the new cell. The BSIC field is coded as the "Base Station Identity Code" defined in 3GPP TS 23.003.

| +|

CCN_ACTIVE (1 bit field)
For description and encoding, see the Packet Cell Change Order message.

| +|

3G_CCN_ACTIVE (1 bit field)
For description and encoding, see the Packet Cell Change Order message.

| +|

CCN Support Description

CCN_SUPPORTED (1 bit field)
For description and encoding, see the Packet Cell Change Order message.

| +|

Frequency Parameters C1
This information element is defined in sub-clause 12.8.

Frequency Parameters C2
This information element is defined in sub-clause 12.8.

Dual Carrier Frequency Parameters
This information element is defined in sub-clause 12.8.2.

| +|

NETWORK_CONTROL_ORDER (2 bit field)
For description and encoding, see the Packet Measurement Order message.

| +|

Global Packet Timing Advance
This information element is defined in sub-clause 12.12a

| +|

Packet Extended Timing Advance (2 bit field)
This field is defined in sub-clause 12.12b.

| +|

RLC_RESET (1 bit field)
This field is defined in sub-clause 12.42.

| +|

EGPRS mode 2 IE
This information element is defined in sub-clause 12.48a.1.

| +|

MTTI_DOWNLINK_ASSIGNMENT_C1 (1 bit field)
MTTI_DOWNLINK_ASSIGNMENT_C2 (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message).

| +|

MTTI_UPLINK_ASSIGNMENT_C1 (1 bit field)
MTTI_UPLINK_ASSIGNMENT_C2 (1 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message).

| + +## 12.42b PS Handover Radio Resources 3 + +This information element provides the radio resources assigned for PS services for a DLMC configuration in the new cell and is included within the PS HANDOVER COMMAND message. + +#### **Table 12.42b.1: PS Handover Radio Resources 3 information element** + +``` + +< PS Handover Radio Resources 3 IE > ::= + { 0 | 1 < Handover Reference : bit (8) > } + < SI : bit (2) > + < NCI : bit (1) > + < BSIC : bit (6) > + { 0 | 1 < CCN_ACTIVE : bit (1) > } + { 0 | 1 < 3G_CCN_ACTIVE : bit (1) > } + { 0 | 1 < CCN Support Description : < CCN Support Description struct > > } + { < DOWNLINK_RLC_MODE : bit (1) > + < CONTROL_ACK : bit (1) > + { 1 < UFPS : < UFPS struct > > } ** 0 + DLMC Measurement Type : bit (1) + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < Carrier for Interference Measurements : bit (4) > } + < Global Packet Timing Advance : < Global Packet Timing Advance IE > > + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } + { 0 | 1 < PTCCH_CARRIER : bit (4) > } + < PDAN Coding : bit (1) > + < Extended SNS : bit (1) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + { 0 | 1 < PFI of downlink TBF : bit (7) > } + { 0 | 1 < Downlink NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates Fast Ack/Nack Reporting is activated for downlink TBF + < EVENT_BASED_FANR : bit (1) > } + < Downlink EGPRS Level : < EGPRS Level IE > > + < Indication of Upper Layer PDU Start for RLC UM : bit > + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { < RESEGMENT : bit (1) > + { 1 < < DLMC UL Carrier Info : < DLMC UL Carrier Info struct > > } ** 0 + { 0 | 1 < UPLINK EGPRS Window Size : < EGPRS Window Size IE > > } + < UPLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < PFI of uplink TBF : bit (7) > } + { 0 | 1 < UPLINK_RLC_MODE : bit (1) > } + { 0 | 1 < Uplink NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < REPORTED TIMESLOTS : bit (8) > + < TSH : bit (2) > } } + < Uplink EGPRS Level : < EGPRS Level IE > > + { 0 | 1 < Pulse Format : < Pulse Format IE > > } + { 0 | 1 < Uplink Control Timeslot : bit (3) > } } + < NETWORK_CONTROL_ORDER : bit (2) > + < RLC_RESET : bit (1) > ; + +< CCN Support Description struct > ::= + < Number_Cells : bit (7) > + { CCN_SUPPORTED : bit } * (val(Number_Cells)) ; + +< UFPS struct > ::= + { 00 -- Existing UFPS released + | 01 -- Existing UFPS remains unchanged (no information provided) + | 10 + { 0 -- Existing DLMC Frequency Parameters unchanged + | 1 < DLMC Frequency Parameters : < DLMC Frequency Parameters IE > > } + { 1 < CARRIER_SPECIFIC_INFO : < Carrier Specific Info struct > > } ** 0 + | 11 bit (*) = < no string > -- Reserved + } ; + +< Carrier Specific Info struct > ::= + { 00 -- Existing carrier released + | 01 -- Existing carrier remains unchanged (no information provided) + | 10 -- Existing carrier changed/new carrier provided + { 0 -- BTTI mode + { 0 -- same timeslots as the lowest numbered carrier + | 1 < TIMESLOT_ALLOCATION : bit (8) > } + | 1 -- RTTI mode + { 0 -- same PDCH-pairs as the lowest numbered carrier + +``` + +``` + + | 1 < DOWNLINK_PDCH_PAIRS_DLMC : bit (8) > + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DLMC : bit (4) > } + } + { 0 | 1 < MAIO : bit (6) > } + { 0 -- same P0 and PR_MODE as the lowest numbered carrier + | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + { 0 -- same DOWNLINK_TFI_ASSIGNMENT as the lowest numbered carrier + | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } + { 0 -- same Power Control Parameters as the lowest numbered carrier + | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 -- EMST is not used on this carrier + | 1 -- EMST is used on this carrier + < RLC Entity 2 : < RLC Entity Struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } + { 0 | 1 < RLC Entity 3 : < RLC Entity Struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } + { 0 -- EMSR is not used on this carrier + | 1 -- EMSR is used on this carrier + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > + { 0 | 1 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } ** 0 + } + < Primary TSC Set : bit (1) > + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + | 11 bit (*) = < no string > -- Reserved +}; + +< DLMC UL Carrier Info struct > ::= +{ 00 -- Assigned carrier released +| 01 -- Carrier remains unchanged (no information provided) +| 10 -- Assigned carrier modified or new carrier assigned + { 0 -- BTI mode + { 0 | 1 < UPLINK_TIMESLOT_ALLOCATION : bit (8) > } -- assigned PDCH + | 1 -- RTTI mode + { 0 | 1 < UPLINK_PDCH_PAIRS_DLMC : bit (8) > } -- assigned PDCH-pairs + } + < Dynamic Allocation 3 : < Dynamic Allocation 3 IE > > + { 0 -- EMST is not used on this carrier + | 1 -- EMST is used on this carrier + < Uplink RLC Entity 2 : < RLC Entity Struct > + { 0 | 1 < Uplink RLC Entity 3 : < RLC Entity Struct > } } + { 0 -- EMSR is not used on this carrier + | 1 -- EMSR is used on this carrier + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + < Primary TSC Set : bit (1) > + | 11 bit (*) = < no string > -- reserved +}; + +< RLC Entity Struct > ::= + < TFI : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < PFI : bit (7) > ; + +< Additional PFCs struct > ::= + < TFI : bit (5) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < PFI : bit (7) > ; + +``` + +**Table 12.42b.2: PS Handover Radio Resources 3 information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Handover Reference (8 bit field)

This field contains the reference value to be used when performing PS Handover. The field is encoded as the contents of the Handover Reference information element as defined in 3GPP TS 44.018.

| +|

SI (2 bit field)

The Synchronization Indication (SI) field indicates which type of PS Handover is to be performed.

Bit
2 1
0 0 Non-synchronized
0 1 Synchronized
1 0 Pre-synchronised
1 1 reserved

| +|

NCI (1 bit field)

The Normal Cell Indication (NCI) field indicates how the MS shall behave in case of out of range timing advance values.

Bit
1
0 Out of range timing advance is ignored
1 Out of range timing advance shall trigger a handover failure procedure.

| +|

BSIC (6 bit field)

This field contains the BSIC of the new cell. The BSIC field is coded as the "Base Station Identity Code" defined in 3GPP TS 23.003.

| +|

CCN_ACTIVE (1 bit field)

This field is defined in sub-clause 11.2.4.

| +|

3G_CCN_ACTIVE (1 bit field)

This field is defined in sub-clause 11.2.4.

| +|

CCN Support Description

CCN_SUPPORTED (1 bit field)

This field is defined in sub-clause 11.2.4.

| +|

DOWNLINK_RLC_MODE (1 bit field)

UPLINK_RLC_MODE (1 bit field)

This field is defined in sub-clause 11.2.31.

| +|

CONTROL_ACK (1 bit field)

See sub-clause 11.2.7 (Packet Downlink Assignment message).

| +|

NETWORK_CONTROL_ORDER (2 bit field)

This field is defined in sub-clause 11.2.9b.

| +|

Global Packet Timing Advance

This information element is defined in sub-clause 12.12a

| +|

Packet Extended Timing Advance (2 bit field)

This field is defined in sub-clause 12.12b.

| +|

RLC_RESET (1 bit field)

This field is defined in sub-clause 12.42.

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

UFPS
This information element is used to identify the set of resources corresponding to each UFPS within the set of UFPS assigned for a DLMC configuration in the new cell. Each UFPS in the set of UFPS is numbered according to the scheme described in sub-clause 8.1.1.1.3.

| +|

DLMC Measurement Type
See sub-clause 11.2.7.

| +|

Carrier for Interference Measurements (4 bit field)
See sub-clause 11.2.7.

| +|

UPLINK EGPRS Window Size

EGPRS Window Size
This field is defined in sub-clause 12.5.2.

| +|

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)
This field is defined in sub-clause 11.2.7.

| +|

BEP_PERIOD2 (4 bit field)
This field is defined in sub-clause 11.2.7.

| +|

PFI of downlink TBF (7 bit field)
PFI of uplink TBF (7 bit field)
This field is defined in sub-clause 11.2.31.

| +|

Downlink NPM Transfer Time (5 bit field)
Uplink NPM Transfer Time (5 bit field)
This field is defined in sub-clause 11.2.31.

| +|

EVENT_BASED_FANR (1 bit field)
This field is defined in sub-clause 11.2.31.

| +|

Uplink EGPRS Level (2 bit field)
Downlink EGPRS Level (2 bit field)
These fields assign the group of modulation and coding schemes applicable to the uplink and downlink TBFs respectively and is defined in sub-clause 12.10f.

| +|

Indication of Upper Layer PDU Start for RLC UM (1 bit field)
This field is defined in section 11.2.7.

| +|

EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)
See sub-clause 11.2.7.

| +|

EGPRS Modulation and Coding Scheme
This field is defined in sub-clause 12.10d. If this field is included in a Multi Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on all assigned carriers.

| +|

CARRIER_SPECIFIC_INFO
See sub-clause 11.2.7.

| +|

DLMC Frequency Parameters
See sub-clause 11.2.7.

| +|

DOWNLINK_TIMESLOT_ALLOCATION (8 bit field)
UPLINK_TIMESLOT_ALLOCATION (8 bit field)
This field is defined in sub-clause 12.18.

| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DOWNLINK_PDCH_PAIRS_DLMC
UPLINK_PDCH_PAIRS_DLMC
This field is defined in sub-clause 11.2.31. | +| RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DLMC
This field is defined in sub-clause 11.2.31. | +| MAIO (6 bit field)
See sub-clause 11.2.7. | +| P0 (4 bit field)
See sub-clause 11.2.7. | +| PR_MODE (1 bit field)
See sub-clause 11.2.7. | +| DOWNLINK_TFI_ASSIGNMENT (5 bit field)
See sub-clause 11.2.7. | +| UPLINK_TFI_ASSIGNMENT (5 bit field)
See sub-clause 11.2.29. | +| Power Control Parameters
See sub-clause 11.2.7. | +| DLMC UL Carrier Info
See sub-clause 11.2.29. | +| REPORTED TIMESLOTS
This field is defined in sub-clause 11.2.31. | +| TSH (2 bit field)
This field is defined in sub-clause 11.2.31. | +| Pulse Format (N bits field)
This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in sub-clause 12.8.3. | +| Uplink Control Timeslot (3 bit field)
This field is defined in sub-clause 11.2.29. | +| Dynamic Allocation 3
This field is defined in sub-clause 11.2.29. | +| PTCCH_CARRIER (4 bit field)
See sub-clause 11.2.7. | +| PDAN Coding (1 bit field)
See sub-clause 11.2.7. | +| DOWNLINK_eTFI_ASSIGNMENT (3 bit field)
See sub-clause 11.2.7. | +| Extended SNS (1 bit field)
See sub-clause 11.2.7. | +| EMSR Additional PFCs 1
EMSR Additional PFCs 2
EMSR Additional PFCs 3
These IEs are defined in section 11.2.7. | + +#### **Primary TSC Set** (1 bit field) + +See sub-clause 11.2.7 and 11.2.29. + +#### **Secondary DL TSC Set** (1 bit field) + +See sub-clause 11.2.7. + +#### **Secondary DL TSC Value** (3 bit field) + +See sub-clause 11.2.7. + +## 12.43 NAS Container for PS Handover + +The purpose of the NAS Container for PS Handover information element (see Note 1) is to indicate the layer 3 information to be applied by the mobile station upon successful completion of PS handover or DTM handover to A/Gb mode. + +**Table 12.43.1: NAS Container for PS Handover information element** + +``` +< NAS Container for PS Handover IE > ::= + < NAS_CONTAINER_LENGTH : bit (7) > + < NAS_CONTAINER_DATA : octet (val(NAS_CONTAINER_LENGTH)) > + < padding bits > ; +``` + +**Table 12.43.2: NAS Container for PS Handover information element details** + +### **NAS\_CONTAINER\_DATA (N octet field)** + +This contents of this information element is identical to the value part of the *NAS Container for PS Handover* information element described in 3GPP TS 24.008 where N is the length of the value part of the *NAS Container for PS Handover* information element. + +## 12.44 Estimated Session Duration + +The Estimated Session Duration gives an estimation of the (remaining) duration for the MBMS session. The initial value is derived from the payload in the *MBMS Session Duration* IE (see 3GPP TS 48.018), rounded up to the next higher value that can be signalled with the coding provided in Table 12.44.1. Any subsequent value for the remaining duration of the MBMS session is derived from the initial value, unless an up-to-date value is available in the *MBMS Session Duration* IE. + +**Table 12.44.1: Estimated Session Duration information element details** + +### **Estimated Session Duration** (8 bit field) + +The Estimated Session Duration information element is coded as follows: + +bit + +8 7 6 5 4 3 2 1 + +0 0 0 0 0 0 0 0 5 seconds + +0 0 0 0 0 0 0 1 10 seconds + +... in 5s step + +0 0 0 0 1 0 1 1 1 minute + +0 0 0 0 1 1 0 0 1 minute 10 seconds + +... in 10s step + +0 0 1 0 0 0 1 1 5 minutes + +0 0 1 0 0 1 0 0 5 minutes 30 seconds + +... in 30s step + +0 0 1 0 1 1 0 1 10 minutes + +0 0 1 0 1 1 1 0 11 minutes + +... in 1m step + +0 1 0 1 1 1 1 1 1 hour + +| | | +|-----------------|----------------------| +| 0 1 1 0 0 0 0 0 | 1 hour 5 minutes | +| ... | in 5m step | +| 1 0 0 0 1 1 1 1 | 5 hours | +| 1 0 0 1 0 0 0 0 | 5 hours 15 minutes | +| ... | in 15m step | +| 1 0 1 0 0 0 1 1 | 10 hours | +| 1 0 1 0 0 1 0 0 | 10 hours 30 minutes | +| ... | in 30m step | +| 1 0 1 1 1 1 1 1 | 1 day | +| 1 1 0 0 0 0 0 0 | 1 day 3 hours | +| ... | in 3h step | +| 1 1 1 0 1 1 1 1 | 7 days | +| 1 1 1 1 0 0 0 0 | 7 days 12 hours | +| ... | in 12h step | +| 1 1 1 1 0 1 0 1 | 10 days | +| 1 1 1 1 0 1 1 0 | 11 days | +| ... | in 1 day step | +| 1 1 1 1 1 1 0 1 | 18days | +| 1 1 1 1 1 1 1 0 | 19 days | +| 1 1 1 1 1 1 1 1 | >19 days | + +## 12.45 MBMS In-band Signalling Indicator + +The MBMS In-band Signalling Indicator indicates whether the network sends system information messages and (for mobile stations with an assigned MS\_ID on that MBMS radio bearer) paging messages on the PACCH. + +**Table 12.45.1: MBMS In-band Signalling Indicator information elements** + +| | +|-------------------------------------------------| +| < MBMS In-band Signalling Indicator IE > ::= | +| < MBMS In-band Signalling Indicator: bit (1) >; | + +**Table 12.45.2: MBMS In-band Signalling Indicator information element details** + +### MBMS In-band Signalling Indicator (1 bit field) + +The MBMS In-band Signalling Indicator information element is coded as follows: + +| | | +|-----|--------------------------------------------------------------------------------------------| +| Bit | | +| 0 | System information and paging messages are not sent on the PACCH of the MBMS radio bearer. | +| 1 | System information and paging messages are sent on the PACCH of the MBMS radio bearer. | + +## 12.45a + +### NPM Transfer Time + +This information element defines the NPM Transfer Time limitation in case of RLC non-persistent mode and is derived from the Transfer Delay IE defined in 3GPP TS 24.008. + +**Table 12.45a.1: NPM Transfer Time Information Elements details** + +| bit
5 4 3 2 1 | NPM Transfer Time (in ms) | +|------------------|---------------------------| +| 0 0 0 0 0 | 30 | +| 0 0 0 0 1 | 40 | +| 0 0 0 1 0 | 50 | +| 0 0 0 1 1 | 60 | +| 0 0 1 0 0 | 70 | +| 0 0 1 0 1 | 80 | +| 0 0 1 1 0 | 90 | +| 0 0 1 1 1 | 100 | +| 0 1 0 0 0 | 125 | +| 0 1 0 0 1 | 150 | +| 0 1 0 1 0 | 175 | +| 0 1 0 1 1 | 200 | +| 0 1 1 0 0 | 225 | +| 0 1 1 0 1 | 250 | +| 0 1 1 1 0 | 275 | +| 0 1 1 1 1 | 300 | +| 1 0 0 0 0 | 400 | +| 1 0 0 0 1 | 500 | +| 1 0 0 1 0 | 600 | +| 1 0 0 1 1 | 700 | +| 1 0 1 0 0 | 800 | +| 1 0 1 0 1 | 900 | +| 1 0 1 1 0 | 1000 | +| 1 0 1 1 1 | 1500 | +| 1 1 0 0 0 | 2000 | +| 1 1 0 0 1 | 2500 | +| 1 1 0 1 0 | 3000 | +| 1 1 0 1 1 | 3500 | +| 1 1 1 0 0 | 4000 | +| 1 1 1 0 1 | 4500 | +| 1 1 1 1 0 | 5000 | +| 1 1 1 1 1 | Reserved | + +## 12.45b RRC Container + +The RRC Container is used to contain an RRC message (e.g. HANDOVER TO UTRAN COMMAND or *DL-DCCH-Message* including a *RRCConnectionReconfiguration*) as defined in 3GPP TS 25.331[20] or 3GPP TS 36.331[45]. + +**Table 12.45b.1: RRC Container information element** + +``` +< RRC Container IE > ::= + < RRC_CONTAINER_LENGTH : bit (8) > + < RRC_CONTAINER_DATA : octet (val(RRC_CONTAINER_LENGTH)) > + < padding bits > ; +``` + +**Table 12.45b.2: RRC Container information element details** + +**RRC\_CONTAINER\_LENGTH** (8 bit field) +This field indicates the number of octets in the RRC\_CONTAINER\_DATA. + +``` +bit +8 7 6 5 4 3 2 1 +0 0 0 0 0 0 0 0 reserved for future use; +0 0 0 0 0 0 0 1 RRC_CONTAINER_DATA length = 1 octet; +0 0 0 0 0 0 1 0 RRC_CONTAINER_DATA length = 2 octets; +.... +1 1 1 1 1 1 1 1 RRC_CONTAINER_DATA length = 255 octets; +``` + +### **RRC\_CONTAINER\_DATA** (N octet field) + +This field contains an RRC Container as specified in 3GPP TS 25.331 [20] or as specified in 3GPP TS36.331 [45]. + +## 12.46 + +### DTM Handover PS Radio Resources + +This information element provides the radio resources assigned for PS services in the new cell and is included within the DTM HANDOVER COMMAND message. + +**Table 12.46.1: DTM Handover PS Radio Resources information element** + +``` + +< DTM Handover PS Radio Resources IE > ::= + < Cell Identification : < Cell Identification IE > > -- provided by SI/PSI for PS HO + < MAX_LAPDm : bit (3) > -- needed for DTM in new cell + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > -- needed for DTM in new cell + < GPRS Cell Options : < GPRS Cell Options IE > > -- provided by SI/PSI for PS HO + < GPRS Power Control Parameters : < GPRS Power Control Parameters IE > > -- provided by SI/PSI for PS HO + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > -- only used in uplink + < RLC_RESET : bit (1) > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + { 0 < GPRS mode : GPRS mode struct > > + | 1 < EGPRS mode : EGPRS mode struct > > } + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Additions for Rel-12 + { 0 | 1 -- Primary TSC Value assigned + < Primary TSC Set : bit (1) > + < Primary TSC Value : bit (3) > } + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + < padding bits > } ; -- truncation at end of message allowed, bits '0' assumed + +< GPRS mode struct > ::= + -- Uplink TBFs + { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink Assignment : < Uplink TBF Assignment struct > > } ** 0 } + -- Downlink TBFs + { 1 < Downlink Assignment : < Downlink Assignment struct > > } ** 0 } ; + +< EGPRS mode struct > ::= + -- Uplink TBFs + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink Assignment : < Uplink TBF Assignment struct > > } ** 0 } + -- Downlink TBFs + { 0 | 1 + { 0 | 1 { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + { 0 | 1 < BEP_PERIOD2 : bit(4) > } } + { 1 < Downlink Assignment : < Downlink Assignment struct > > } ** 0 } ; + +``` + +``` + +< Uplink TBF Assignment struct > ::= -- Recursive for multiple TBFs + { 0 | 1 < PFI : bit (7) > } + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < USF_GRANULARITY : bit (1) > + { 0 -- The timeslots assigned to the TBF are all the timeslots assigned + -- in the Global Timeslot description + | 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > } -- The timeslots assigned to the TBF are a subset of all the + -- timeslots assigned in the Global Timeslot description. Where + -- N is the number of timeslots assigned to the MS in the Global + -- Timeslot_description + { 0 < USF_ALLOCATION : bit (3) > -- The same USF is valid on all timeslots assigned to the TBF + | 1 -- Different USF(s) assigned + < USF_ALLOCATION : bit (3) > -- USF assignment on the lowest numbered timeslot + -- assigned to the TBF + { 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) }; -- USFs on subsequent timeslots assigned to the TBF: + -- A ‘0’ (respectively a ‘1’ followed by a USF value) + -- means same (respectively different) USF value as the + -- USF on the next lower numbered timeslot assigned to + -- the TBF. Where M is the amount of timeslots assigned + -- to the TBF in the TBF_TIMESLOT_ALLOCATION if + -- present, else in the Global Timeslot description. + +< Downlink Assignment struct > ::= -- Recursive for multiple TBFs + < TIMESLOT_ALLOCATION : bit (8) > + { < Downlink TBF assignment : < Downlink TBF assignment struct > > } ; + +< Downlink TBF assignment struct > ::= + { 0 | 1 < PFI : bit (7) > } + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } ; + +< Timeslot description struct > ::= + { 0 -- without power control params + < MS_TIMESLOT_ALLOCATION : bit (8) > + | 1 -- with power control params + < ALPHA : bit (4) > + { 0 | 1 < GAMMA_TN0 : bit (5) > } + { 0 | 1 < GAMMA_TN1 : bit (5) > } + { 0 | 1 < GAMMA_TN2 : bit (5) > } + { 0 | 1 < GAMMA_TN3 : bit (5) > } + { 0 | 1 < GAMMA_TN4 : bit (5) > } + { 0 | 1 < GAMMA_TN5 : bit (5) > } + { 0 | 1 < GAMMA_TN6 : bit (5) > } + { 0 | 1 < GAMMA_TN7 : bit (5) > } } ; + +``` + +**Table 12.46.2: DTM Handover PS Radio Resources information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cell Identification (information element)
This information element is defined in sub-clause 12.23.

| +|

MAX_LAPDm (3 bit field)
This field indicates the maximum number of LAPDm frames on which a layer 3 can be segmented into and be sent on the main DCCH. It is coded as described in 3GPP TS 44.018.

| +|

GPRS_MS_TXPWR_MAX_CCH (5 bit field)
The GPRS_MS_TXPWR_MAX_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008.

| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GPRS Cell Options (information element)
The GPRS Cell Option information element is defined in sub-clause 12.24. | +| GPRS Power Control Parameters (information element)
The GPRS Power Control Parameters information element is defined in sub-clause 12.9a. | +| EXTENDED_DYNAMIC_ALLOCATION (1 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| RLC_RESET (1 bit field)
For description and encoding, see sub-clause 12.42. | +| P0 (4 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| PR_MODE (1 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| Uplink Control Timeslot (3 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| CHANNEL_CODING_COMMAND (2 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| EGPRS Window Size
This information element is defined in sub-clause 12.5.2. | +| EGPRS Modulation and Coding Scheme
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| BEP_PERIOD2 (4 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| LINK_QUALITY_MEASUREMENT_MODE (2 bit field)
For description and encoding, see the Multiple TBF Downlink Assignment message. | +| PFI (7 bit field)
This field shall only be included for TBFs if both the network and the mobile station support multiple TBFs. This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018. | +| RLC_MODE (1 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message or the Multiple TBF Downlink Assignment message. If the RLC_RESET field indicates that any given RLC entity is not reset across PS handover then the mobile station shall ignore this field and use the same RLC mode that was used for the corresponding PFC in the old cell. | +| TFI Assignment (5 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| USF_GRANULARITY (1 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| TBF_TIMESLOT_ALLOCATION (N bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| USF_ALLOCATION (3 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message. | +| TIMESLOT_ALLOCATION (8 bit field)
For description and encoding, see the Multiple TBF Downlink Assignment message. | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

CONTROL_ACK (1 bit field)
For description and encoding, see sub-clause 12.42.

| +|

MS_TIMESLOT_ALLOCATION (8 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

ALPHA (4 bit field)
For encoding and description see the Global Power Control Parameters IE.

| +|

GAMMA_TN (5 bit field)
For description and encoding, see the Multiple TBF Uplink Assignment message.

| +|

Primary TSC Set (1 bit field)
If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the TSC set associated with the Primary TSC Value field. In the absence of this field the TSC set indicated by the DTM Handover CS Radio Resources IE shall be used.

Secondary DL TSC Set (1 bit field)
If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the TSC set associated with the Secondary DL TSC Value field.

The Primary TSC Set and Secondary DL TSC Set fields are coded as follows:

0 TSC set 1
1 Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain).

| +|

Primary TSC Value (3 bit field)
If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the primary TSC value to be used on the assigned uplink and downlink PS resources. In the absence of this field the TSC value indicated by the DTM Handover CS Radio Resources IE shall be used as the Primary TSC value. It is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002. Range: 0 to 7.

| +|

Secondary DL TSC Value (3 bit field)
If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the secondary TSC value to be used on the assigned downlink PS resources. It is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002. Range: 0 to 7.

| + +## 12.47 + +### DTM Handover CS Radio Resources + +This information element provides the radio resources assigned for CS service in the new cell and is included within the DTM HANDOVER COMMAND message. + +**Table 12.47.1: DTM Handover CS Radio Resources information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< CS Handover Radio Resources IE > ::=   < CS_HANDOVER_RADIO_RESOURCES_LENGTH : bit (7) >   < CS_HANDOVER_RADIO_RESOURCES_DATA : octet (val(CS_HANDOVER_RADIO_RESOURCES_LENGTH)) >   < padding bits > ;
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.47.2: DTM Handover CS Radio Resources information element details** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| CS_HANDOVER_RADIO_RESOURCES_LENGTH (7 bit field) | | +| This field indicates the number of CS_HANDOVER_RADIO_RESOURCES_DATA octets included in the CS Handover Radio Resources IE . | | +| bit | | +| 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 | No CS_HANDOVER_RADIO_RESOURCES_DATA follows; Spare padding is used to fill the rest of the message; | +| 0 0 0 0 0 0 1 | CS_HANDOVER_RADIO_RESOURCES_DATA length = 1 octet; | +| 0 0 0 0 0 1 0 | CS_HANDOVER_RADIO_RESOURCES_DATA length = 2 octets; | +| .... | | +| 1 1 1 1 1 1 1 | CS_HANDOVER_RADIO_RESOURCES_DATA length = 127 octets; | +| CS_HANDOVER_RADIO_RESOURCES_DATA (N octet field) | | +| The contents of this information element are identical to the contents of the HANDOVER COMMAND (see 3GPP TS 44.018) except for the RR management Protocol Discriminator IE, the Skip Indicator IE and the Handover Command Message Type IE which are not included. N is the combined length of the information elements from the HANDOVER COMMAND that are included within this IE. | | + +## 12.48 + +### DTM Handover PS Radio Resources 2 + +This information element provides the radio resources assigned for PS services in the new cell and is included within the DTM HANDOVER COMMAND message. + +NOTE: The maximum length (64 bits) of the *Extension Information* IE as defined in the present sub-clause may constrain the information that can be included in this IE. + +**Table 12.48.1: DTM Handover PS Radio Resources 2 information element** + +``` + +< DTM Handover PS Radio Resources 2 IE > ::= + < Cell Identification : < Cell Identification IE > > --- provided by SI/PSI for PS HO + < MAX_LAPDm : bit (3) > --- needed for DTM in new cell + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > --- needed for DTM in new cell + < GPRS Cell Options : < GPRS Cell Options IE > > --- provided by SI/PSI for PS HO + < GPRS Power Control Parameters : < GPRS Power Control Parameters IE > > --- provided by SI/PSI for PS HO + < RLC_RESET : bit (1) > + { 00 < EGPRS mode : < EGPRS mode 2 IE > > + ! < TBF mode error: { 01 | 10 | 11 } bit(*) = < no string > > } -- reserved for future use + + -- Optional extension information: + { 0 | 1 < Extension Length : bit (6) > + < bit (val(Extension Length) + 1) + & { < Extension Information > ! { bit ** = < no string > } } > } ; + +< Extension Information > ::= + {{ -- Rel-9 extension: + { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used + | 1 -- EMST is used + { 0 + | 1 < Downlink RLC Entity 2 : < RLC Entity struct > + { 0 + | 1 < Downlink RLC Entity 3 : < RLC Entity struct > } + } + { 0 + | 1 < Uplink RLC Entity 2 : < RLC Entity struct > + { 0 + | 1 < Uplink RLC Entity 3 : < RLC Entity struct > } + } + } + { 0 | 1 MTTI_DOWNLINK_ASSIGNMENT_C1 : bit (1) } + { 0 | 1 MTTI_DOWNLINK_ASSIGNMENT_C2 : bit (1) } + { 0 | 1 MTTI_UPLINK_ASSIGNMENT_C1 : bit(1) } + { 0 | 1 MTTI_UPLINK_ASSIGNMENT_C2 : bit(1) } + } + { -- Rel-11 extension: + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > + } + { -- Rel-12 extension: + { 0 | 1 -- Primary DL TSC Value assigned + < Primary TSC Set : bit (1) > + < Primary TSC Value : bit (3) > } + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } + } + < spare bit > ** } // ; -- Extension information may be truncated between released versions of the protocol. + -- The receiver shall assume the value zero for any truncated bit. + +< RLC Entity struct > ::= + < TFI : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < PFI : bit (7) > ; + +``` + +**Table 12.48.2: DTM Handover PS Radio Resources 2 information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cell Identification (information element)

This information element is defined in sub-clause 12.23.

| +|

MAX_LAPDm (3 bit field)

This field indicates the maximum number of LAPDm frames into which a layer 3 message can be segmented sent on the main DCCH. It is coded as described in 3GPP TS 44.018.

| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GPRS_MS_TXPWR_MAX_CCH (5 bit field)
The GPRS_MS_TXPWR_MAX_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008. | +| GPRS Cell Options (information element)
The GPRS Cell Option information element is defined in sub-clause 12.24. | +| GPRS Power Control Parameters (information element)
The GPRS Power Control Parameters information element is defined in sub-clause 12.9a. | +| RLC_RESET (1 bit field)
This field is defined in sub-clause 12.42. | +| EGPRS mode 2 IE
This information element is defined in sub-clause 12.48a.1. | +| EMST_NW_Capability (1 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message). | +| TFI (5 bit field)
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message). | +| RLC_MODE (1 bit field)
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message). If the RLC_RESET field indicates that any given RLC entity is not reset across PS handover then the mobile station shall ignore this field and use the same RLC mode that was used for the corresponding PFC in the old cell. | +| EGPRS Window Size
This information element is defined in sub-clause 12.5.2. | +| PFI (7 bit field)
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message). | +| NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. | +| MTTI_DOWNLINK_ASSIGNMENT_C1 (1 bit field)
MTTI_DOWNLINK_ASSIGNMENT_C2 (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| MTTI_UPLINK_ASSIGNMENT_C1 (1 bit field)
MTTI_UPLINK_ASSIGNMENT_C2 (1 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message). | +| EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| Primary TSC Set (1 bit field)
Secondary DL TSC Set (1 bit field)
See sub-clause 12.46. | +| Primary TSC Value (3 bit field)
See sub-clause 12.46. | +| Secondary DL TSC Value (3 bit field)
See sub-clause 12.46. | + +## 12.48a PS resources assignment information elements + +### 12.48a.1 EGPRS mode 2 + +This information element provides the description of uplink and / or downlink radio resources assigned for PS services in a dual carrier configuration or supporting EGPRS2, Fast Ack/Nack Reporting or RTTI configurations for single TBF or a multiple TBF capable mobile station. + +**Table 12.48a.1.1: EGPRS mode 2 information element** + +``` +< EGPRS mode 2 IE > ::= + { 0 | 1 < BEP_PERIOD2 : bit(4) > } + { 0 -- SINGLE TBF ASSIGNMENT + { 0 | 1 -- Single Downlink TBF + < Downlink Assignment : < Single Downlink Assignment 2 IE > > + } + { 0 | 1 -- Single Uplink TBF + < Uplink Assignment : < Single Uplink Assignment 2 IE > > + } + } + | 1 -- MULTIPLE TBF ASSIGNMENT + -- THIS ASSIGNMENT CHOICE SHALL ONLY BE SELECTED BY THE NETWORK + -- FOR ASSIGNING RESOURCES TO A MOBILE STATION SUPPORTING + -- MULTIPLE TBF PROCEDURES IN A/GB MODE (see 3GPP TS 24.008) + { 0 | 1 -- Multiple downlink TBF(s) + < Multiple Downlink Assignment : < Multiple Downlink Assignment 2 IE > > + } + { 0 | 1 -- Multiple uplink TBF(s) + < Multiple Uplink Assignment : < Multiple Uplink Assignment 2 IE > > + } + } +}; +``` + +**Table 12.48a.1.2: EGPRS mode 2 information element details** + +| | +|---------------------------------------------------------------------------------------------------------| +| BEP_PERIOD2 (4 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message). | +| Single Downlink Assignment 2 IE
This information element is defined in sub-clause 12.48a.2. | +| Single Uplink Assignment 2 IE
This information element is defined in sub-clause 12.48a.3. | +| Multiple Downlink Assignment 2 IE
This information element is defined in sub-clause 12.48a.5. | +| Multiple Uplink Assignment 2 IE
This information element is defined in sub-clause 12.48a.6. | + +### 12.48a.2 Single Downlink Assignment 2 + +This information element provides the description of downlink radio resources assigned for PS services in a dual carrier configuration or supporting EGPRS2, Fast Ack/Nack Reporting or RTTI configurations for a single TBF. + +**Table 12.48a.2.1: Single Downlink Assignment 2 information element** + +``` + +< Single Downlink Assignment 2 IE > ::= + { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > + < Downlink EGPRS Level : < EGPRS Level IE > > + { 0 -- Fast Ack/Nack Reporting is not activated for the downlink TBF; + | 1 -- Fast Ack/Nack Reporting is activated for the downlink TBF + < EVENT_BASED_FANR : bit (1) > } + { 0 -- BTTI mode + < TIMESLOT_ALLOCATION_C1 : bit (8) > + { 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } + | 1 -- RTTI mode + { 0 -- Single Carrier Assignment + { 00 -- Default PDCH-pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > + | 1 -- Dual Carrier Assignment + { 00 -- Default PDCH pair configuration + | 01 -- Unchanged + | 10 -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > + } + } + { 0 | 1 < PFI : bit (7) > } + < RLC_MODE : bit (1) > + < DOWNLINK_TFI_ASSIGNMENT : bit (5) > + < CONTROL_ACK : bit (1) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + ; + +``` + +**Table 12.48a.2.2: Single Downlink Assignment 2 information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------| +| EGPRS Window Size IE (Downlink EGPRS Window Size)
This information element is defined in sub-clause 12.5.2. | +| LINK_QUALITY_MEASUREMENT_MODE (2 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| EGPRS Level IE (Downlink EGPRS Level)
This information element is defined in sub-clause 12.10f. | +| EVENT_BASED_FANR (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| TIMESLOT_ALLOCATION_C1, TIMESLOT_ALLOCATION_C2 (8 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DOWNLINK_PDCH_PAIRS_C1
DOWNLINK_PDCH_PAIRS_C2
UPLINK_PDCH_PAIRS_C1
UPLINK_PDCH_PAIRS_C2
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message). | +| PFI (7 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| RLC_MODE (1 bit field)
This field contains the RLC mode to be used for the assigned TBF. If a new mode is assigned by the network for an already established TBF, the MS shall ignore the new assigned mode and shall maintain the TBF in the old mode. If the RLC_RESET field indicates that any given RLC entity is not reset across PS handover (see sub-clause 12.42a) or DTM handover (see sub-clause 12.48) then the mobile station shall ignore this field and use the same RLC mode that was used for the corresponding PFC in the old cell.

The encoding of this field is defined as in sub-clause 11.2.29 (Packet Uplink Assignment message). | +| DOWNLINK_TFI_ASSIGNMENT (5 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| CONTROL_ACK (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| NPM Transfer Time (5 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | + +### 12.48a.3 Single Uplink Assignment 2 + +This information element provides the description of uplink radio resources assigned for PS services in a dual carrier configuration or supporting EGPRS2, Fast Ack/Nack Reporting or RTTI configurations for a single TBF. + +**Table 12.48a.3.1: Single Uplink Assignment 2 information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < Single Uplink Assignment 2 IE > ::=    { < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > }   < RESEGMENT : bit (1) >   { 0   1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > }   < Uplink EGPRS Level : < EGPRS Level IE > >   { 0   1  -- '1' indicates that FANR is activated     { 0    -- SSN-based encoding is selected       1    -- Time-based encoding is selected       < REPORTED TIMESLOTS_C1 : bit (8) >  -- Carrier 1 in Downlink Dual Carrier configuration       { 0   1 < REPORTED TIMESLOTS_C2 : bit (8) > } -- Carrier 2 in Downlink Dual Carrier configuration       < TSH : bit (2) > } }   { 0      -- BTTI mode     1      -- RTTI mode     < RTTI_USF_MODE : bit (1) >     -- The Uplink Assignment PDCH Pairs Description IE shall not be included     -- when an RTTI configuration description for downlink TBF(s) is provided in the message     { 0   1 < Uplink Assignment PDCH Pairs Description : < PDCH Pairs Description IE > > }   }   < Dynamic Allocation 2 : < Dynamic Allocation 2 IE > >   { 0   1 < PFI : bit (7) > }   < RLC_MODE : bit (1) >   { 0   1 < NPM Transfer Time : bit (5) > }   { 0   1 < Pulse Format : < Pulse Format IE > > }   ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.48a.3.2: Single Uplink Assignment 2 information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

EGPRS Modulation and Coding Scheme IE (EGPRS Channel Coding Command)
This information element is defined in sub-clause 12.10d.

See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

RESEGMENT (1 bit field)
This field is defined in sub-clause 12.10e.

| +|

EGPRS Window Size IE (Uplink EGPRS Window Size)
This information element is defined in sub-clause 12.5.2.

| +|

EGPRS Level IE (Uplink EGPRS Level)
This information element is defined in sub-clause 12.10f.

| +|

REPORTED TIMESLOTS C1, REPORTED TIMESLOTS C2 (8 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

TSH (2 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

RTTI_USF_MODE (1 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

PDCH Pairs Description IE (Uplink Assignment PDCH Pairs Description)
This information element is defined in sub-clause 12.5.5.

Specific conditions apply for the inclusion of this information element (see sub-clause 7.1.3.6).

| +|

Dynamic Allocation 2 IE
This information element is defined in sub-clause 12.48a.4.

| +|

PFI (7 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

RLC_MODE (1 bit field)
See sub-clause 12.48a.2 (Single Downlink Assignment 2 information element).

| +|

NPM Transfer Time (5 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

Pulse Format IE
This information element is defined in sub-clause 12.8.3.

| + +### 12.48a.4 Dynamic Allocation 2 + +This information element provides the description of the uplink dynamic allocation information for a BTTI or an RTTI assignment in a single or a dual carrier configuration with or without power control parameters. + +Table 12.48a.4.1: Dynamic Allocation 2 information element + +``` + +< Dynamic Allocation 2 IE > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit (1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit (1) > } } + < USF_GRANULARITY : bit (1) > + { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 + -- Allocation without Power Control Parameters + < N_USF : bit (4) > + { 0 | 1 < USF : bit (3) > } * (val(N_USF) + 1) + | 1 + -- Allocation with Power Control Parameters + < ALPHA_C1 : bit (4) > + { 0 | 1 < ALPHA_C2 : bit (4) > } + { 0 + -- BTTI mode + < N_TS : bit (4) > + { 0 | 1 + < USF : bit (3) > + < GAMMA : bit (5) > + } * (val(N_TS) + 1) + | 1 + -- RTTI mode + < N_PAIRS : bit (3) > + { 0 | 1 + < USF : bit (3) > + < GAMMA : bit (5) > + } * (val(N_PAIRS) + 1) + { 0 + -- RTTI USF + | 1 + -- BTTI USF + { 0 | 1 < USF_2 : bit (3) > + { 0 | 1 < GAMMA : bit (5) > } + } * (val(N_PAIRS) + 1) + } + } + } +}; + +``` + +Table 12.48a.4.2: Dynamic Allocation 2 element details + +##### **EXTENDED\_DYNAMIC\_ALLOCATION (1 bit field)** + +This information field indicates the medium access mode to be used during the TBF. + +- 0 Dynamic Allocation +- 1 Extended Dynamic Allocation + +##### **P0\_C1, P0\_C2 (4 bit field)** + +These fields are optional downlink power control parameters. + +If the Assignment Type field is present and indicates 'Dual Carrier assignment', P0\_C1 and P0\_C2 apply to carrier 1 and carrier 2, respectively. The presence of these parameters indicates that downlink power control is used for the indicated carrier; otherwise, downlink power control is not used for the indicated carrier. If the P0\_C1 IE is present but the P0\_C2 IE is absent, then the P0\_C1 IE shall apply also to carrier 2. + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then P0\_C1 shall apply to the carrier specified in the Carrier ID field. + +These fields are encoded as follows: + +bit + +4 3 2 1 + +0 0 0 0 P0 = 0 dB + +0 0 0 1 P0 = 2 dB + +0 0 1 0 P0 = 4 dB + +: + +1 1 1 1 P0 = 30 dB + +##### **PR\_MODE\_C1, PR\_MODE\_C2** (1 bit field) + +These fields indicate the PR Management mode, as defined in 3GPP TS 45.008. + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then PR\_MODE\_C1 shall apply to the carrier specified in the Carrier ID field. Otherwise, PR\_MODE\_C1 and PR\_MODE\_C2 shall apply to carrier 1 and carrier 2 respectively. If the Assignment Type field indicates 'Dual Carrier assignment' and the PR\_MODE\_C1 IE is present but the PR\_MODE\_C2 IE is absent, then the PR\_MODE\_C1 IE shall apply also to carrier 2. It is encoded as follows: + +- 0 PR mode A: for one addressed MS +- 1 PR mode B: for all MS + +##### **USF\_GRANULARITY** (1 bit field) + +This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation. + +- 0 the mobile station shall transmit one RLC/MAC block +- 1 the mobile station shall transmit four consecutive RLC/MAC blocks + +##### **UPLINK\_TFI\_ASSIGNMENT** (5 bit field) + +This information element, if present, assigns the contained TFI to the mobile station to identify an uplink TBF described by this message. This field is coded the same as the TFI field defined in sub-clause 12.15. + +##### **N\_USF, N\_TS** (4 bit field) + +##### **N\_PAIRS** (3 bit field) + +These fields indicate respectively the number of USF, timeslots or PDCH pairs assigned to a given uplink TBF. The number of timeslots or PDCH pairs is given as the binary value of the corresponding field plus one. + +See Annex K for details of the coding of these fields. + +##### **ALPHA\_C1, ALPHA\_C2** (4 bit field) + +If the Assignment Type field is included and indicates 'Assignment on single carrier only' or 'Modification of existing assignment', then ALPHA\_C1 (if present) shall apply to the carrier specified in the Carrier ID field. + +If the Assignment Type field is included and indicates 'Dual Carrier assignment', ALPHA\_C1 and ALPHA\_C2 indicate the value of the parameter alpha to be applied in power control on carrier 1 and carrier 2 respectively. For encoding and description see the Global Power Control Parameters IE. If ALPHA\_C1 is present and ALPHA\_C2 is absent, then ALPHA\_C1 shall apply to carrier 2. + +##### **USF, USF\_2** (3 bit field) + +These fields indicate the USF values assigned to a given TBF for the assigned timeslot or PDCH pair. + +In the case of RTTI mode with BTTI USF, the USF value specified in the USF field (respectively USF\_2 field) applies to the first two (respectively second two) TDMA frames of the following basic radio block period (see sub-clauses 8.1.1.1, 8.1.1.2.1). + +These fields are encoded as a binary representation of the USF value as defined in sub-clause 10.4.1. + +The order in which USF assignments are encoded and the meaning when the number of repetitions of the USF is lower than the maximum is described in Annex K. + +##### **GAMMA (5 bit field)** + +This field is the binary representation of the parameter $\Gamma_{CH}$ for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table: + +| bit | | +|-----------|-----------------------| +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma_{CH} = 0$ dB | +| 0 0 0 0 1 | $\Gamma_{CH} = 2$ dB | +| ⋮ ⋮ | | +| 1 1 1 1 0 | $\Gamma_{CH} = 60$ dB | +| 1 1 1 1 1 | $\Gamma_{CH} = 62$ dB | + +In the case of RTTI mode with BTTI USF, exactly one GAMMA field shall be included for each PDCH pair for which either one or two USF values are assigned. + +#### 12.48a.5 Multiple Downlink Assignment 2 + +This information element provides the description of downlink radio resources assigned for PS services in a dual carrier configuration or supporting EGPRS2, Fast Ack/Nack Reporting or RTTI configurations for a multiple TBF capable mobile station. + +This information element shall only be used by the network for assigning resources to a mobile station supporting multiple TBF procedures in A/Gb mode (see sub-clauses 11.2.37, 12.42a and 12.48 and 3GPP TS 24.008). + +Table 12.48a.5.1: Multiple Downlink Assignment 2 information element + +``` + +< Multiple Downlink Assignment 2 IE > ::= +{ 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } +< LINK_QUALITY_MEASUREMENT_MODE : bit (2) > +< Downlink EGPRS Level: < EGPRS Level IE > > +{ 0 | 1 + -- BTTI mode + < FANR: bit (1) > + { 1 < BTTI Multiple Downlink Assignment : < BTTI Multiple Downlink Assignment struct > > } ** 0 +} +{ 0 | 1 + -- RTTI mode + { 0 + -- Single Carrier Assignment + { 00 + -- Default PDCH-pair configuration + | 01 + -- Unchanged + | 10 + -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment SC : RTTI Multiple Downlink Assignment SC struct > > } ** 0 + | 1 + -- Dual Carrier Assignment + { 00 + -- Default PDCH pair configuration + | 01 + -- Unchanged + | 10 + -- Explicit PDCH pair configuration + < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > + < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > + < UPLINK_PDCH_PAIRS_C1 : bit (8) > + < UPLINK_PDCH_PAIRS_C2 : bit (8) > + ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > -- reserved + } + { 1 < RTTI Multiple Downlink Assignment DC : < RTTI Multiple Downlink Assignment DC struct > > } ** 0 + } +} + +< BTTI Multiple Downlink Assignment struct > ::= +< TIMESLOT_ALLOCATION_C1 : bit (8) > +{ 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } +{ 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } +{ 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } +{ 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< RTTI Multiple Downlink Assignment SC struct > ::= +< RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > +{ 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } +{ 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< RTTI Multiple Downlink Assignment DC struct > ::= +< RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > +{ 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } +{ 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } +{ 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; + +< Downlink TBF assignment 2 struct > ::= +{ 0 | 1 < PFI : bit (7) > } +< RLC_MODE : bit (1) > +{ 0 | 1 < Uplink Control Timeslot C1 : bit (3) > } +{ 0 | 1 < Uplink Control Timeslot C2 : bit (3) > } +< TFI Assignment : bit (5) > +< CONTROL_ACK : bit (1) > +{ 0 | 1 < NPM Transfer Time : bit (5) > } +< EVENT_BASED_FANR: bit (1) > +{ 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } ; + +``` + +**Table 12.48a.5.2: Multiple Downlink Assignment 2 information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

EGPRS Window Size IE (Downlink EGPRS Window Size)
This information element is defined in sub-clause 12.5.2.

Specific conditions apply for the interpretation of this information element. See sub-clause 11.2.37 (Packet CS Release Indication message).

| +|

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message).

| +|

EGPRS Level IE (Downlink EGPRS Level)
This information element is defined in sub-clause 12.10f.

| +|

FANR (1 bit field)
See sub-clause 11.2.7a (Multiple TBF Downlink Assignment message).

| +|

DOWNLINK_PDCH_PAIRS_C1
DOWNLINK_PDCH_PAIRS_C2
UPLINK_PDCH_PAIRS_C1
UPLINK_PDCH_PAIRS_C2
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC
RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message).

| +|

TIMESLOT_ALLOCATION_C1, TIMESLOT_ALLOCATION_C2 (8 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message).

| +|

Uplink Control Timeslot C1, Uplink Control Timeslot C2 (3 bit field)
In case of a BTTI configuration, these fields contain the timeslot number on carrier1 (respectively carrier 2) of the timeslot where the PACCH/U for the MS is located. In case of an RTTI configuration, these fields contain the timeslot number of the timeslot on carrier1 (respectively carrier 2) belonging to the uplink PDCH pair where the PACCH/U for the MS is located. They are encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002.

If these fields are included in the BTTI Multiple Downlink Assignment IE or in the RTTI Multiple Downlink Assignment SC / DC IE, they shall refer to all downlink TBFs assigned in the message. If these fields are included in the Downlink TBF Assignment 2 IE, they refer only to the TBF given by the TFI Assignment field (the specific values overrule any default values given in the BTTI Multiple Downlink Assignment IE or in the RTTI Multiple Downlink Assignment SC / DC IE). If the Uplink Control Timeslot C1 / Uplink Control Timeslot C2 field is not included in the message at all, then the default rules for the location of PACCH/U apply.

| +|

PFI (7 bit field)
This field shall only be included for TBFs if both the network and the mobile station support multiple TBFs. This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018.

| +|

RLC_MODE (1 bit field)
See sub-clause 12.48a.2 (Single Downlink Assignment 2 information element).

| +|

TFI Assignment (5 bit field)
See sub-clause 11.2.7a (Multiple TBF Downlink Assignment message).

| +|

CONTROL_ACK (1 bit field)
See sub-clause 12.42 (PS Handover Radio Resources information element).

| +|

NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode and is defined in sub-clause 12.45a.

| +|

EVENT_BASED_FANR (1 bit field)
See sub-clause 11.2.7a (Multiple TBF Downlink Assignment message).

| + +#### 12.48a.6 Multiple Uplink Assignment 2 + +This information element provides the description of uplink radio resources assigned for PS services in a dual carrier configuration or supporting EGPRS2, Fast Ack/Nack Reporting or RTTI configurations for a multiple TBF capable mobile station. + +This information element shall only be used by the network for assigning resources to a mobile station supporting multiple TBF procedures in A/Gb mode (see sub-clauses 11.2.37, 12.42a and 12.48 and 3GPP TS 24.008). + +##### **Table 12.48a.6.1: Multiple Uplink Assignment 2 information element** + +``` + +< Multiple Uplink Assignment 2 IE > ::= +{ 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } +< RESEGMENT : bit (1) > +{ 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } +< EXTENDED_DYNAMIC_ALLOCATION : bit (1) > +{ 0 | 1 < P0_C1 : bit (4) > + < PR_MODE_C1 : bit(1) > + { 0 | 1 < P0_C2 : bit (4) > + < PR_MODE_C2 : bit(1) > } +{ 0 | 1 -- '1' indicates that FANR is activated + { 0 -- SSN-based encoding is selected + | 1 -- Time-based encoding is selected + < TSH : bit (2) > } +{ 0 | 1 -- BTTI mode + < Global Timeslot description : < Timeslot description 2 struct > > + { 0 | 1 < BTTI Uplink TBF Assignment : < BTTI Uplink TBF Assignment struct > > } ** 0 +} + +{ 0 | 1 -- RTTI mode + + -- The Uplink Assignment PDCH Pairs Description IE shall not be included + -- when an RTTI configuration description for downlink TBF(s) is provided in the message + { 0 | 1 < Uplink Assignment PDCH Pairs Description : < PDCH Pairs Description IE > > } + + < N_PAIRS : bit (3) > -- Number minus 1 of the uplink pairs of the PDCH pairs description + -- assigned to the TBF + { 0 -- Without power control parameters + | 1 -- With power control parameters + < ALPHA_C1 : bit (4) > + { 0 | 1 < ALPHA_C2 : bit (4) > } + { 0 | 1 < GAMMA : bit (5) > } * (val (N_PAIRS) + 1) + { 0 -- RTTI USF, or no second GAMMA values are given in case of RTTI mode with BTTI USF + | 1 -- Second GAMMA values are given in case of RTTI mode with BTTI USF + { 0 | 1 < GAMMA : bit (5) > } * (val (N_PAIRS) + 1) + } + } + { 1 < RTTI_USF_MODE : bit (1) > + < RTTI Uplink TBF Assignment : < RTTI Uplink TBF Assignment struct > > + } ** 0 +} + +< Uplink EGPRS Level : < EGPRS Level IE > > +{ 0 | 1 < Pulse Format : < Pulse Format IE > > } +; + +``` + +``` + +< BTTI Uplink TBF Assignment struct > ::= -- Recursive for multiple BTTI TBFs + { 0 | 1 < PFI : bit (7) > } + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1': Time-based encoding FANR is activated + < REPORTED TIMESLOTS_C1 : bit (8) > -- Carrier 1 in Downlink Dual Carrier configuration + { 0 | 1 < REPORTED TIMESLOTS C2 : bit (8) > } -- Carrier 2 in Downlink Dual Carrier configuration + } + < USF_GRANULARITY : bit (1) > + + < N_TS : bit (4) > -- Number minus 1 of the timeslots of the Global Timeslot description + -- assigned to the TBF + { 0 -- 0: All timeslots in Global Timeslot description are assigned to the TBF + | 1 -- 1: Only timeslots in TBF_TIMESLOT_ALLOCATION are assigned to the TBF + < TBF_TIMESLOT_ALLOCATION : bit (val (N_TS) + 1) > } + { 0 < USF_C1 : bit (3) > -- Same USF valid on all timeslots assigned to the TBF on the respective carriers + { 0 | 1 < USF_C2 : bit (3) > } + | 1 -- Different USF(s) assigned: + < USF : bit (3) > -- USF for the first assigned timeslot + { 0 | 1 < USF : bit (3) > } * (val (N_TS) + 1) -- USF for next assigned timeslots (omitted=same as previous) + }; + + + +--- + + +< RTTI Uplink TBF Assignment struct > ::= -- Recursive for multiple RTTI TBFs + { 0 | 1 < PFI : bit (7) > } + < RLC_MODE : bit (1) > + < TFI Assignment : bit (5) > + { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } + { 0 | 1 < Uplink EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < NPM Transfer Time : bit (5) > } + { 0 | 1 -- '1': Time-based encoding FANR is activated + < REPORTED TIMESLOTS_C1 : bit (8) > -- Carrier 1 in Downlink Dual Carrier configuration + { 0 | 1 < REPORTED TIMESLOTS C2 : bit (8) > } -- Carrier 2 in Downlink Dual Carrier configuration + } + < USF_GRANULARITY : bit (1) > + + { 0 -- The PDCH pairs assigned to the TBF are all the PDCH pairs described + -- in the PDCH pairs description + | 1 < TBF_UPLINK_PAIRS_ALLOCATION : bit (val (N_PAIRS) + 1) > } + { 0 < USF_C1 : bit (3) > + { 0 | 1 < USF_C2 : bit (3) > } -- Same USF valid on all pairs assigned to the TBF on the respective carriers + | 1 -- Different USF(s) assigned + < USF : bit (3) > -- USF for the first assigned PDCH pair + { 0 | 1 < USF : bit (3) > } * (val (N_PAIRS)) -- Next assigned PDCH pairs (omitted=same as previous) + { 0 -- RTTI USF mode + | 1 -- BTTI USF mode (second USF) + < USF_2 : bit (3) > -- Second USF for the first assigned PDCH pair + { 0 | 1 < USF_2 : bit (3) > } * (val (N_PAIRS)) -- Next assigned PDCH pairs (omitted=same as previous) + } + }; + +``` + +``` + +< Timeslot description 2 struct > ::= +{ 0 + < MS_TIMESLOT_ALLOCATION_C1 : bit (8) > -- Without power control parameters + { 0 | 1 < MS_TIMESLOT_ALLOCATION_C2 : bit (8) > } +| 1 + < ALPHA_C1 : bit (4) > -- With power control parameters + { 0 | 1 < GAMMA_TN0_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN1_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN2_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN3_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN4_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN5_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN6_C1 : bit (5) > } + { 0 | 1 < GAMMA_TN7_C1 : bit (5) > } + { 0 | 1 < ALPHA_C2 : bit (4) > } + { 0 | 1 < GAMMA_TN0_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN1_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN2_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN3_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN4_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN5_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN6_C2 : bit (5) > } + { 0 | 1 < GAMMA_TN7_C2 : bit (5) > } } ; + +``` + +**Table 12.48a.6.2: Multiple Uplink Assignment 2 information element details** + +##### **EGPRS Modulation and Coding Scheme IE (EGPRS Channel Coding Command)** + +This information element is defined in sub-clause 12.10d . + +Specific conditions apply for the inclusion of this information element. See sub-clause 11.2.29a (Multiple TBF Uplink Assignment message). + +##### **RESEGMENT (1 bit field)** + +This field is defined in sub-clause 12.10e. + +##### **EXTENDED\_DYNAMIC\_ALLOCATION (1 bit field)** + +See sub-clause 11.2.29 (Packet Uplink Assignment message). + +##### **P0\_C1, P0\_C2 (4 bit field)** + +See sub-clause 11.2.29 (Packet Uplink Assignment message). + +##### **PR\_MODE\_C1, PR\_MODE\_C2 (1 bit field)** + +See sub-clause 11.2.29 (Packet Uplink Assignment message). + +##### **TSH (2 bit field)** + +See sub-clause 11.2.29 (Packet Uplink Assignment message). + +#### **Uplink Assignment PDCH Pairs Description** + +This information element is defined in sub-clause 12.5.5. + +Specific conditions apply for the inclusion of this information element (see sub-clause 7.1.3.6). + +##### **N\_TS, N\_PAIRS,** + +These fields indicate respectively the number of timeslots or PDCH pairs assigned to a given uplink TBF. The number of timeslots or PDCH pairs is given as the binary value of the corresponding field plus one. + +See Annex K for details of the coding of these fields. + +##### **ALPHA\_C1, ALPHA\_C2 (4 bit field)** + +See sub-clause 11.2.29 (Packet Uplink Assignment message). + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

GAMMA, GAMMA_TNx_C1, GAMMA_TNx_C2 (5 bit field)

These fields are the binary representation of the parameter \Gamma_{CH} for MS output power control in units of 2 dB, see 3GPP TS 45.008.

See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

RTTI_USF_MODE (1 bit field)

See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

EGPRS Level IE (Uplink EGPRS Level)

This information element is defined in sub-clause 12.10f.

| +|

Pulse Format IE

This information element is defined in sub-clause 12.8.3.

| +|

PFI (7 bit field)

This field shall only be included for TBFs if both the network and the mobile station support multiple TBFs. This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 44.018.

| +|

RLC_MODE (1 bit field)

See sub-clause 12.48a.2 (Single Downlink Assignment 2 information element).

| +|

TFI Assignment (5 bit field)

See sub-clause 11.2.29a (Multiple TBF Uplink Assignment message).

| +|

EGPRS Window Size IE (Uplink EGPRS Window Size)

This information element is defined in sub-clause 12.5.2.

Specific conditions apply for the interpretation of this information element. See sub-clause 11.2.37 (Packet CS Release Indication message).

| +|

NPM Transfer Time (5 bit field)

This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode and is defined in sub-clause 12.45a.

| +|

REPORTED TIMESLOTS C1, REPORTED TIMESLOTS C2 (8 bit field)

See sub-clause 11.2.7a (Multiple TBF Downlink Assignment message).

| +|

USF_GRANULARITY (1 bit field)

See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

TBF_TIMESLOT_ALLOCATION (N\_TS+1 bit field)

This field indicates the timeslots assigned to a particular uplink TBF, within the timeslots assigned to the mobile station in the Global Timeslot description. This field contains as many bits as there are timeslots assigned to the mobile station in the Global Timeslot description. Bit N\_TS+1 corresponds to the lowest numbered timeslot in the timeslots assigned to the mobile station; bit N\_TS (if any) corresponds to the next lowest numbered timeslot, etc. At least one timeslot must be assigned per TBF.

0 Timeslot not assigned
1 Timeslot assigned

If the TBF_TIMESLOT_ALLOCATION bitmap is present, then the timeslots assigned to the TBF are a subset of all the timeslots assigned in the Global Timeslot description, otherwise all timeslots in the Global Timeslot description are assigned to the TBF.

| + +##### **TBF\_UPLINK\_PAIRS\_ALLOCATION (N\_PAIRS+1 bit field)** + +This field indicates the PDCH pairs assigned to a particular uplink TBF within the uplink PDCH pairs assigned to the mobile station, i.e. within the RTTI configuration description for downlink TBF(s) if provided, otherwise within the *Uplink Assignment PDCH Pairs Description* IE (see sub-clause 7.1.3.6). This field contains as many bits as there are uplink PDCH pairs assigned to the mobile station. Bit N\_TS+1 corresponds to the lowest numbered uplink PDCH pair assigned to the mobile station; bit N\_TS (if any) corresponds to the next lowest numbered PDCH pair, etc. (PDCH pairs numbering should be understood as defined in Annex K). At least one PDCH pair must be assigned per TBF. + +- 0 PDCH pair not assigned +- 1 PDCH pair assigned + +If the TBF\_UPLINK\_PAIRS\_ALLOCATION bitmap is present, then the PDCH pairs assigned to the TBF are a subset of all the uplink PDCH pairs assigned to the mobile station, otherwise all uplink PDCH pairs assigned to the mobile station are assigned to the TBF. + +##### **USF\_C1, USF\_C2 (3 bit field)** + +These fields indicate the USF value assigned to a given TBF for all timeslots or PDCH pairs on the relevant carrier. + +If the Assignment Type field is present and indicates 'Dual Carrier assignment', USF\_C1 applies to carrier 1, otherwise it applies to the carrier identified by the Carrier ID field. + +If the Assignment Type field is present and indicates 'Dual Carrier assignment', and USF\_C1 is present and USF\_C2 is absent, the value specified by USF\_C1 applies to timeslots assigned on both carriers. + +These fields are encoded as a binary representation of the USF value as defined in sub-clause 10.4.1. + +##### **USF, USF\_2 (3 bit field)** + +These fields indicate the USF values assigned to a given TBF for the assigned timeslot or PDCH pair. + +In the case of RTTI mode with BTTI USF, the USF value specified in the USF field (respectively USF\_2 field) applies to the first two (respectively second two) TDMA frames of the following basic radio block period (see sub-clauses 8.1.1.1, 8.1.1.2.1). + +These fields are encoded as a binary representation of the USF value as defined in sub-clause 10.4.1. + +If no USF is specified for a given timeslot or PDCH pair assigned to a TBF, then the USF value is the same as the previously indicated USF value. + +The order in which USF assignments are encoded is described in Annex K. + +#### **MS\_TIMESLOT\_ALLOCATION\_C1, MS\_TIMESLOT\_ALLOCATION\_C2** + +See sub-clause 11.2.29a (Multiple TBF Uplink Assignment message). + +As the explicit power control parameters are omitted for the allocated timeslots in the new cell, the mobile station shall use the default values (see 3GPP TS 45.008) for the power control parameters. + +## 12.49 + +### E-UTRAN Target Cell + +The *E-UTRAN Target cell* information element contains the description of an E-UTRAN Target cell. + +**Table 12.49.1: E-UTRAN Target cell information element** + +``` +< E-UTRAN Target cell IE > ::= + < EARFCN : bit (16) > + { 0 | 1 < Measurement Bandwidth: bit (3) > } + < Physical Layer Cell Identity : bit (9) > ; +``` + +**Table 12.49.2: E-UTRAN Target cell information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EARFCN (16 bit field)
This information element is defined as the EARFCN in 3GPP TS 36.104. | +| Measurement Bandwidth (3 bit field)
This optional field describes the bandwidth of the E-UTRAN cell for measurement purposes. The coding of this field is as specified in sub-clause 12.53. | +| Physical Layer Cell Identity (9 bit field)
This field indicates the physical layer cell identity as defined in 3GPP TS 36.211. | + +## 12.50 + +### Individual Priorities + +This information element is sent to provide MS-specific priorities for priority-based cell reselection (see 3GPP TS 45.008). The individual priorities shall override the priorities received through system information or previously received individual priorities. The timer T3230 is used to control the validity of the individual priorities. + +**Table 12.50.1: Individual priorities information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < Individual priorities IE > ::=   { 0        -- delete all stored individual priorities     1        -- provide individual priorities     < GERAN_PRIORITY : bit(3) >     { 0   1 < 3G Individual Priority Parameters Description :         < 3G Individual Priority Parameters Description struct >> }     { 0   1 < E-UTRAN Individual Priority Parameters Description :         < E-UTRAN Individual Priority Parameters Description struct >> }     { 0   1 < T3230 timeout value : bit (3) > }   };    < 3G Individual Priority Parameters Description struct > ::=     { 0   1 < DEFAULT_UTRAN_PRIORITY : bit(3) > }     { 1 < Repeated Individual UTRAN Priority Parameters :         < Repeated Individual UTRAN Priority Parameters struct >> } ** 0 ;    < Repeated Individual UTRAN Priority Parameters struct > ::=     { 0 { 1 < FDD-ARFCN : bit (14) > } ** 0   1 { 1 < TDD-ARFCN : bit (14) > } ** 0 }     < UTRAN_PRIORITY : bit(3) > ;    < E-UTRAN Individual Priority Parameters Description struct > ::=     { 0   1 < DEFAULT_E-UTRAN_PRIORITY : bit(3) > }     { 1 < Repeated Individual E-UTRAN Priority Parameters :         < Repeated Individual E-UTRAN Priority Parameters struct >> } ** 0 ;    < Repeated Individual E-UTRAN Priority Parameters struct > ::=     { 1 < EARFCN : bit (16) > } ** 0     < E-UTRAN_PRIORITY : bit(3) > ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------------|-------|--------------------|-------|--------------------|-------|--------------------|-------|--------------------|-------|---------------------|-------|---------------------|-------|-----------------------------------------------------------------------------------------------| +|

GERAN_PRIORITY (3 bit field)
UTRAN_PRIORITY (3 bit field)
E-UTRAN_PRIORITY (3 bit field)
These fields are used for the inter-RAT cell re-selection algorithm based on priority information, see sub-clauses 12.51, 12.52 and 12.53.

DEFAULT_UTRAN_PRIORITY (3 bit field)
DEFAULT_E-UTRAN_PRIORITY (3 bit field)
The DEFAULT_UTRAN_PRIORITY field is encoded as the UTRAN_PRIORITY field; the DEFAULT_E-UTRAN_PRIORITY field is encoded as the E-UTRAN_PRIORITY field. Any UTRAN frequency contained in the 3G Frequency list and not explicitly listed in any occurrence of the Repeated Individual UTRAN Priority Parameters IE or any E-UTRAN frequency contained in the E-UTRAN Neighbour Cell list and not explicitly listed in any occurrence of the Repeated Individual E-UTRAN Priority Parameters IE shall be assigned the corresponding default value. If the Repeated Individual UTRAN Priority Parameters IE is not present, every UTRAN frequency in the 3G Frequency list for the serving cell shall be assigned the default value. If the Repeated Individual E-UTRAN Priority Parameters IE is not present, every E-UTRAN frequency in the E-UTRAN Neighbour Cell list for the serving cell shall be assigned the default value.

| | | | | | | | | | | | | | | | | +|

FDD-ARFCN (14 bit field)
TDD-ARFCN (14 bit field)
EARFCN (16 bit field)

These fields are used to indicate the frequencies for which priorities are provided, see sub-clauses 11.2.21b and 12.53.

| | | | | | | | | | | | | | | | | +|

T3230 timeout value (3 bit field)
The timer uses 3 bits to indicate the time for which the signalled individual priorities are valid:

0 0 05 minute timeout;
0 0 110 minute timeout;
0 1 020 minute timeout;
0 1 130 minute timeout;
1 0 060 minute timeout;
1 0 1120 minute timeout;
1 1 0180 minute timeout;
1 1 1reserved for future use; if received, it shall be interpreted by the mobile station as "110";

If this information element is not present, the mobile station shall consider the signalled individual priorities to be valid until the occurrence of one of the conditions specified in subclause 5.5.1.1c.3.

| 0 0 0 | 5 minute timeout; | 0 0 1 | 10 minute timeout; | 0 1 0 | 20 minute timeout; | 0 1 1 | 30 minute timeout; | 1 0 0 | 60 minute timeout; | 1 0 1 | 120 minute timeout; | 1 1 0 | 180 minute timeout; | 1 1 1 | reserved for future use; if received, it shall be interpreted by the mobile station as "110"; | +| 0 0 0 | 5 minute timeout; | | | | | | | | | | | | | | | | +| 0 0 1 | 10 minute timeout; | | | | | | | | | | | | | | | | +| 0 1 0 | 20 minute timeout; | | | | | | | | | | | | | | | | +| 0 1 1 | 30 minute timeout; | | | | | | | | | | | | | | | | +| 1 0 0 | 60 minute timeout; | | | | | | | | | | | | | | | | +| 1 0 1 | 120 minute timeout; | | | | | | | | | | | | | | | | +| 1 1 0 | 180 minute timeout; | | | | | | | | | | | | | | | | +| 1 1 1 | reserved for future use; if received, it shall be interpreted by the mobile station as "110"; | | | | | | | | | | | | | | | | + +## 12.51 + +### GSM Priority Parameters + +This information element is sent to provide priority information about the serving cell and other GSM cells. + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< GSM Priority Parameters IE > ::=   < GERAN_PRIORITY : bit(3) >   < THRESH_Priority_Search : bit(4) >   < THRESH_GSM_low : bit(4) >   < H_PRIO : bit(2) >   < T_Reselection : bit(2) > ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.51.2: GSM priority parameters information element details** + +**GERAN\_PRIORITY** (3 bit field) +**THRESH\_Priority\_Search** (4 bit field) +**THRESH\_GSM\_low** (4 bit field) +**H\_PRIO** (2 bit field) +**T\_Reselection** (2 bit field) + These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. + +## 12.52 + +### 3G Priority Parameters + +This information element is sent to provide priority information about neighbouring UTRAN cells. + +**Table 12.52.1: 3G priority parameters information element** + +``` +< 3G Priority Parameters IE > ::= + { 0 | 1 < DEFAULT_UTRAN_PRIORITY : bit(3) > + < DEFAULT_THRESH_UTRAN : bit(5) > + < DEFAULT_UTRAN_QRXLEVMIN : bit(5) > + { 1 < Repeated UTRAN Priority Parameters : < Repeated UTRAN Priority Parameters struct >> } ** 0 ; + +< Repeated UTRAN Priority Parameters struct > ::= + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 + { 0 | 1 < UTRAN_PRIORITY : bit(3) > + < THRESH_UTRAN_high : bit(5) > + { 0 | 1 < THRESH_UTRAN_low : bit(5) > } + { 0 | 1 < UTRAN_QRXLEVMIN : bit(5) > } ; +``` + +**Table 12.52.2: 3G priority parameters information element details** + +**DEFAULT\_UTRAN\_PRIORITY** (3 bit field) +**DEFAULT\_THRESH\_UTRAN** (5 bit field) +**DEFAULT\_UTRAN\_QRXLEVMIN** (5 bit field) + These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. Any UTRAN frequency added or modified in the Packet Measurement Order message (full set of instances) and not explicitly listed in the Repeated UTRAN Priority Parameters structure shall be assigned these default parameter values. The value of **DEFAULT\_THRESH\_UTRAN** shall apply to both **THRESH\_UTRAN\_high** and **THRESH\_UTRAN\_low**. + +### Repeated UTRAN Priority Parameters + +**UTRAN\_FREQUENCY\_INDEX** (5 bit field) + +This field is an index into the 3G Frequency list (see sub-clause 5.6.3.7b). + +**UTRAN\_PRIORITY** (3 bit field) + +**THRESH\_UTRAN\_high** (5 bit field) + +**THRESH\_UTRAN\_low** (5 bit field) + +**UTRAN\_QRXLEVMIN** (5 bit field) + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. These parameters apply to each UTRAN frequency indexed within the structure. + +If **THRESH\_UTRAN\_low** is not present, then **THRESH\_UTRAN\_low** shall take on the same value as **THRESH\_UTRAN\_high**. + +Any parameter present overwrites any old data held by the mobile station for these parameters. + +## 12.53 + +### E-UTRAN Parameters + +This information element is sent to provide information about E-UTRAN frequencies and priority information about neighbouring E-UTRAN cells. + +**Table 12.53.1: E-UTRAN parameters information element** + +``` + +< E-UTRAN Parameters IE > ::= + < E-UTRAN_CCN_ACTIVE : bit > + { 0 | 1 < GPRS E-UTRAN Measurement Parameters : + < GPRS E-UTRAN Measurement Parameters struct >> } + { 1 < Repeated E-UTRAN Neighbour Cells : < Repeated E-UTRAN Neighbour Cells struct >> } ** 0 + { 1 < Repeated E-UTRAN Not Allowed Cells : < Repeated E-UTRAN Not Allowed Cells struct >> } ** 0 + { 1 < Repeated E-UTRAN PCID to TA mapping : < Repeated E-UTRAN PCID to TA mapping struct >> } ** 0 ; + +< GPRS E-UTRAN Measurement Parameters struct > ::= + < Qsearch_P_E-UTRAN : bit(4) > + < E-UTRAN_REP_QUANT : bit > + < E-UTRAN_MULTIRAT_REPORTING : bit(2) > + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD : bit(3) > + { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD : bit(3) > + { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } + { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } ; + +< Repeated E-UTRAN Neighbour Cells struct > ::= + { 1 < EARFCN : bit (16) > + { 0 | 1 < Measurement Bandwidth : bit (3) > } } ** 0 + { 0 | 1 < E-UTRAN_PRIORITY : bit(3) > } + < THRESH_E-UTRAN_high : bit(5) > + { 0 | 1 < THRESH_E-UTRAN_low : bit(5) > } + { 0 | 1 < E-UTRAN_QRXLEVMIN : bit(5) > } ; + +< Repeated E-UTRAN Not Allowed Cells struct > ::= + < Not Allowed Cells : < PCID Group IE >> + { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 ; + +< Repeated E-UTRAN PCID to TA mapping struct > ::= + { 1 + < PCID to TA mapping : < PCID Group IE >> -- each repetition corresponds to a different TA + } ** 0 -- group of PCIDs belonging to the same TA + { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 ; + +``` + +**Table 12.53.2: E-UTRAN parameters information element details** + +### E-UTRAN\_CCN\_ACTIVE (1 bit field) + +This field indicates whether CCN is enabled towards E-UTRAN neighbouring cells. It is coded as follows: + +0 The broadcast E-UTRAN\_CCN\_ACTIVE parameter shall apply if available. Otherwise, CCN towards E-UTRAN cells is disabled in the cell. + +1 CCN towards E-UTRAN cells is enabled in the cell. + +#### GPRS E-UTRAN Measurement Parameters + +**Qsearch\_P\_E-UTRAN** (4 bit field) + +**E-UTRAN\_REP\_QUANT** (1 bit field) + +**E-UTRAN\_MULTIRAT\_REPORTING** (2 bit field) + +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD** (3 bit field) + +**E-UTRAN\_FDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +**E-UTRAN\_FDD\_REPORTING\_OFFSET** (3 bit field) + +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD** (3 bit field) + +**E-UTRAN\_TDD\_REPORTING\_THRESHOLD\_2** (6 bit field) + +**E-UTRAN\_TDD\_REPORTING\_OFFSET** (3 bit field) + +These fields control the measurement and reporting of E-UTRAN cells, as defined in 3GPP TS 45.008. + +If both TDD and FDD frequencies are provided in the Repeated E-UTRAN Neighbour Cells IE and the E-UTRAN reporting thresholds are present for only one mode (i.e. TDD or FDD), then the parameter values for both modes shall be interpreted as having the same values. + +If any of these parameters is included in more than one instance of the PACKET MEASUREMENT ORDER message, the value of the parameter in the instance with the highest PMO\_INDEX shall be used. + +--- + +#### Repeated E-UTRAN Neighbour Cells + +If E-UTRAN cells or frequencies are included in the neighbour cell list, this information element may be included in the message. + +**EARFCN** (16 bit field) + +This field specifies the E-UTRA Absolute Radio Frequency Channel Number as defined in 3GPP TS 36.104. + +**Measurement Bandwidth** (3 bit field) + +This field specifies the minimum value of the channel bandwidth of all valid E-UTRAN cells on the specified EARFCN. It is defined by the parameter Transmission Bandwidth Configuration, $N_{RB}$ (see 3GPP TS 36.104). The values indicate the number of resource blocks over which the mobile station could measure if the mobile station does not support wideband RSRQ measurements (see 3GPP TS 24.008). A mobile station supporting wideband RSRQ measurements shall measure over the indicated number of resource blocks. The field is coded according to the following table: + +| bit | | | | +|------------|---|---|-----------------------------------------------------------------------------------------------| +| 3 | 2 | 1 | | +| 0 | 0 | 0 | $N_{RB} = 6$ | +| 0 | 0 | 1 | $N_{RB} = 15$ | +| 0 | 1 | 0 | $N_{RB} = 25$ | +| 0 | 1 | 1 | $N_{RB} = 50$ | +| 1 | 0 | 0 | $N_{RB} = 75$ | +| 1 | 0 | 1 | $N_{RB} = 100$ | +| All others | | | Reserved for future use. If received by the mobile station, it shall be interpreted as '101'. | + +When missing, this indicates $N_{RB} = 6$ . + + + +**E-UTRAN\_PRIORITY** (3 bit field) + +**THRESH\_E-UTRAN\_high** (5 bit field) + +**THRESH\_E-UTRAN\_low** (5 bit field) + +If **THRESH\_E-UTRAN\_low** is not present, then **THRESH\_E-UTRAN\_low** shall take on the same value as **THRESH\_E-UTRAN\_high**. + +**E-UTRAN\_QRXLEVMIN** (5 bit field) + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. These values apply to each of the EARFCN values listed within this structure. + +### **Repeated E-UTRAN Not Allowed Cells struct** + +This structure identifies Not Allowed Cells with zero or more corresponding E-UTRAN frequency indices. If no E-UTRAN\_FREQUENCY\_INDEX is present, the Not Allowed Cells IE is applicable to all E-UTRAN frequencies specified in the Repeated E-UTRAN Neighbour Cells struct(s). + +### **E-UTRAN\_FREQUENCY\_INDEX (3 bit field)** + +This field contains the index into the frequencies specified as part of the E-UTRAN Neighbour Cell list. A value of 0 refers to the first E-UTRAN frequency (EARFCN) defined in the list. A value of 1 refers to the second defined frequency and so on. + +#### **Not Allowed Cells** + +This information element identifies one or more E-UTRAN cells by means of their physical layer cell identities (see 3GPP TS 36.211). The mobile station shall not perform measurements or attempt reselection to these cells. This information element is defined as the PCID Group IE described in subclause 12.57. + +### **PCID to TA mapping** + +This information element identifies, on the frequency or frequencies that this information element is associated with, one or more E-UTRAN cells by means of their physical layer cell identities (see 3GPP TS 36.211) that belong to the same Tracking Area. If no PCIDs or groups of PCIDs are indicated within this structure, then all PCIDs belong to the same Tracking Area. + +This information element is defined as the PCID Group IE described in 3GPP TS 44.060. + +## 12.54 + +### 3G CSG Description + +The 3G CSG *Description* information element contains the description of 3G CSG cells. The fields of this description are used for inter-RAT cell reselection to UTRAN CSG cells as defined in 3GPP TS 45.008. + +**Table 12.54.1: 3G CSG *Description* information element** + +``` +< 3G CSG Description IE > ::= + { 1 < CSG_PSC_SPLIT : < PSC Group IE >> + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 } ** 0 ; +``` + +**Table 12.54.2: 3G CSG *Description* information element details** + +### **UTRAN\_FREQUENCY\_INDEX (5 bit field)** + +Each instance of this field describes a UTRAN frequency in the 3G Neighbour Cell list where the CSG PSC SPLIT is valid. If the CSG\_PSC\_SPLIT IE is present but there are no instances of this field present in the message, then the CSG PSC SPLIT shall apply to all UTRAN frequencies in the 3G Neighbour Cell list. This field is described in sub-clause 12.52. + +### **CSG\_PSC\_SPLIT** + +This information element identifies one or more primary scrambling code values for UTRAN FDD cells (see 3GPP TS 25.213) or cell parameter values for UTRAN TDD cells (see 3GPP TS 25.223) as being reserved for CSG cells. The range of reserved primary scrambling codes or cell parameters applies to all UTRAN frequencies specified in the list of frequencies. + +This information element is defined as the PSC Group IE described in subclause 12.58. + +## 12.55 + +### E-UTRAN CSG Description + +The *E-UTRAN CSG Description* information element contains the description of E-UTRAN CSG cells. The fields of this description are used for inter-RAT cell reselection to E-UTRAN CSG cells as defined in 3GPP TS 45.008. + +**Table 12.55.1: E-UTRAN CSG description information element** + +``` +< E-UTRAN CSG Description IE > ::= + { 1 < CSG_PCI_SPLIT : < PCID Group IE >> + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 } ** 0 ; +``` + +**Table 12.55.2: E-UTRAN CSG description information element details** + +### E-UTRAN\_FREQUENCY\_INDEX (3 bit field) + +Each instance of this field describes an E-UTRAN frequency in the E-UTRAN Neighbour Cell list where the CSG PCI SPLIT is valid. If the CSG\_PCI\_SPLIT information element is present but there are no instances of this field present in the message, then the CSG PCI SPLIT shall apply to all E-UTRAN frequencies in the E-UTRAN Neighbour Cell list. This field is described in sub-clause 12.53. + +### CSG\_PCI\_SPLIT + +This information element identifies one or more E-UTRAN physical layer cell identities (see 3GPP TS 36.211) as being reserved for CSG cells. The range of reserved physical layer cell identities applies to all E-UTRAN frequencies specified in the list of frequencies. This information element is defined as the PCID Group IE in sub-clause 12.57. + +## 12.56 + +### Measurement Control Parameters Description + +This information element is sent to provide the measurement control information about UTRAN frequencies and E-UTRAN frequencies. The fields of this description are used for inter-RAT cell measurement. + +**Table 12.56.1: Measurement control parameters description information element** + +``` +< Measurement Control Parameters Description > ::= + { 0 | 1 < Measurement_Control_E-UTRAN : bit(1) > + < E-UTRAN_FREQUENCY_INDEX : bit (3) > + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 + } + { 0 | 1 < Measurement_Control_UTRAN : bit(1) > + < UTRAN_FREQUENCY_INDEX : bit (5) > + { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 + } ; +``` + +**Table 12.56.2: Measurement control parameters description information element details** + +### Measurement\_Control\_E-UTRAN (1 bit field) + +This field controls the measurement of E-UTRAN cells for the specified EARFCNs indicated by the E-UTRAN\_FREQUENCY\_INDEX values, as defined in 3GPP TS 45.008. If this field is not present, all EARFCNs in the E-UTRAN Neighbour Cell list shall behave according to the behaviour controlled by the Qsearch\_P\_E-UTRAN. + +All E-UTRAN frequency indices received in this instance of the information element shall take the value of parameter Measurement\_Control\_E-UTRAN. All other E-UTRAN frequency indices in the E-UTRAN Neighbour Cell list shall take the opposite value to that of the received Measurement\_Control\_E-UTRAN. + +### **E-UTRAN\_FREQUENCY\_INDEX** (3 bit field) + +This field is described in sub-clause 12.53. + +### **Measurement\_Control\_UTRAN** (1 bit field) + +This field controls the measurement of UTRAN cells for the specified UARFCNs indicated by the UTRAN\_FREQUENCY\_INDEX values, as defined in 3GPP TS 45.008. If this field is not present, all UARFCNs in 3G Neighbour Cell list shall behave according to the behaviour controlled by the Qsearch\_P. + +All UTRAN frequency indices received in this instance of the information element shall take the value of parameter Measurement\_Control\_UTRAN. All other UTRAN frequency indices in the 3G Neighbour Cell list shall take the opposite value to that of the received Measurement\_Control\_UTRAN. + +### **UTRAN\_FREQUENCY\_INDEX** (5 bit field) + +This field is described in sub-clause 12.52. + +## 12.57 + +### PCID Group + +The *PCID Group* information element contains the description of a group of one or more physical layer cell identities for E-UTRAN cells (see 3GPP TS 36.211). + +**Table 12.57.1: *PCID Group* information element** + +``` +< PCID Group IE > ::= + { 1 < PCID : bit (9) > } ** 0 -- explicit PCID coding + { 0 | 1 < PCID_BITMAP_GROUP : bit (6) > } + { 1 < PCID_Pattern_length : bit (3) > + < PCID_Pattern : bit (val(PCID_Pattern_length + 1)) > + < PCID_pattern_sense : bit (1) > + } ** 0 ; +``` + +**Table 12.57.2: *PCID Group* information element details** + +### **PCID** (9 bit field) + +This field specifies the physical layer cell identity of a single E-UTRAN cell. + +### **PCID\_BITMAP\_GROUP** (6 bit field) + +Each bit number n, where n can take the value from 1 to 6, represents the group of PCID values in the range (n-1) \* 84 to (n\*84)-1 inclusive. + +When this field is received as part of the Not Allowed Cells IE, if bit number n is set to '1', then all cells whose PCID belongs to the group identified by that bit are not allowed; correspondingly, if bit number n is set to '0', then all cells whose PCID belongs to that group are allowed. + +When this field is received as part of the CSG\_PCI\_SPLIT IE, if bit number n is set to '1', then all cells whose PCID belongs to the group identified by that bit are part of the CSG; correspondingly, if bit number n is set to '0', then all cells whose PCID belongs to that group are not part of the CSG. + +When this field is received as part of the PCID to TA mapping IE, if bit number n is set to '1', then all cells whose PCID belongs to the group identified by that bit are part of the same TA, correspondingly, if bit number n is set to '0', then all cells whose PCID belongs to that group are not part of the same TA. + +### **PCID\_Pattern\_length** (3 bit field) + +### **PCID\_Pattern** + +### **PCID\_pattern\_sense** (1 bit field) + +If the PCID\_pattern\_sense bit is equal to '0' then the group of identified cells are those where the most significant bits of the physical layer cell identity are equal to "PCID\_pattern". If the PCID\_pattern\_sense bit is equal to '1' then the group of identified cells is all those where the most significant bits of the physical layer cell identity are not equal to the PCID\_pattern. + +## 12.58 + +### PSC Group + +The *PSC Group* information element contains the description of a group of one or more primary scrambling codes for UTRAN FDD cells (see 3GPP TS 25.213) or a group of one or more cell parameters for UTRAN TDD cells (see 3GPP TS 25.223). + +**Table 12.58.1: PSC Group information element** + +``` +< PSC Group IE > ::= + { 1 < PSC : bit (9) > } ** 0 -- explicit PSC coding + { 1 < PSC_Pattern_length : bit (3) > + < PSC_Pattern : bit (val(PSC_Pattern_length + 1)) > + < PSC_pattern_sense : bit (1) > + } ** 0 ; +``` + +**Table 12.58.2: PSC Group information element details** + +### PSC (9 bit field) + +This field specifies the primary scrambling code of a single FDD cell or the cell parameter of a single TDD cell. For TDD cells, the Cell Parameter is contained in the 7 least significant bits of the field; the 2 most significant bits are ignored. + +### PSC\_Pattern\_length (3 bit field) + +### PSC\_Pattern + +### PSC\_pattern\_sense (1 bit field) + +If the PSC\_pattern\_sense bit is equal to '0' then the group of identified codes are those where the most significant bits of the primary scrambling code or the cell parameter are equal to "PSC\_pattern". If the PSC\_pattern\_sense bit is equal to '1' then the group of identified codes is all those where the most significant bits of the primary scrambling code or cell parameter are not equal to the PSC\_pattern. For TDD frequencies, if the pattern contains more than 6 bits only the most significant 6 bits shall be used. + +## 12.59 + +### Enhanced Cell Reselection Parameters + +This information element is sent to provide information about parameters for enhanced cell reselection procedures towards E-UTRAN cells, see 3GPP TS 45.008. + +**Table 12.59.1: Enhanced Cell Reselection Parameters information element** + +``` +< Enhanced Cell Reselection Parameters IE > ::= + { 1 < Repeated E-UTRAN Enhanced Cell Reselection Parameters : + < Repeated E-UTRAN Enhanced Cell Reselection Parameters struct >> } ** 0 ; + + < Repeated E-UTRAN Enhanced Cell Reselection Parameters struct > ::= + { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 + { 0 -- reselection based on target cell RSRP (RSRQ checked for suitability) + < E-UTRAN_Qmin : bit(4) > + | 1 -- reselection based on target cell RSRQ (RSRP checked for suitability) + < THRESH_E-UTRAN_high_Q : bit(5) > + { 0 | 1 < THRESH_E-UTRAN_low_Q : bit(5) > } + { 0 | 1 < E-UTRAN_QQUALMIN : bit(4) > } + { 0 | 1 < E-UTRAN_RSRPmin : bit(5) > } + } ; +``` + +**Table 12.59.2: Enhanced Cell Reselection Parameters information element details** + +### **Repeated E-UTRAN Enhanced Cell Reselection Parameters struct** + +**E-UTRAN\_FREQUENCY\_INDEX** (3 bit field) + +This field is defined in sub-clause 12.53. + +**E-UTRAN\_Qmin** (4 bit field)**E-UTRAN\_QQUALMIN** (4 bit field)**E-UTRAN\_RSRPmin** (5 bit field)**THRESH\_E-UTRAN\_high\_Q** (5 bit field)**THRESH\_E-UTRAN\_low\_Q** (5 bit field) + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. The parameters apply to each E-UTRAN frequency indexed within this structure. Any parameter present overwrites any old data held by the mobile station for these parameters. + +If **THRESH\_E-UTRAN\_low\_Q** is not present, then **THRESH\_E-UTRAN\_low\_Q** shall take on the same value as **THRESH\_E-UTRAN\_high\_Q**. + +## 12.60 E-UTRAN CSG Measurement Report + +The *E-UTRAN CSG Measurement Report* information element contains measurement results for one E-UTRAN CSG or hybrid neighbour cell identified via its Cell Identity. + +**Table 12.60.1: E-UTRAN CSG Measurement Report information element** + +``` +< E-UTRAN CSG Measurement Report IE > ::= + < E-UTRAN CI : bit (28) > + < Tracking Area Code : bit (16) > + { 0 | 1 < PLMN-ID : < PLMN-ID struct > > } + < CSG-ID : bit (27) > + < Access Mode : bit (1) > + < REPORTING_QUANTITY : bit (6) > ; + +< PLMN-ID struct > ::= + < MCC : bit (12) > + < MNC : bit (12) > ; +``` + +**Table 12.60.2: E-UTRAN CSG Measurement Report information element details** + +### **E-UTRAN CGI** (28 bit field) + +This field contains the E-UTRAN Cell Identity (as defined in 3GPP TS 23.003) of the cell being reported. + +### **Tracking Area Code** (16 bit field) + +This field contains the tracking area code (as defined in 3GPP TS 24.301) of the cell being reported. + +### **PLMN-ID** + +This information element contains the primary PLMN-ID of the cell being reported (as defined in 3GPP TS 36.331). If this field is not present then the PLMN-ID of the target cell is the same as that of the serving cell. + +### **CSG-ID** (27 bit field) + +This field contains the CSG identity (as defined in 3GPP TS 23.003) of the cell being reported. + +### **Access Mode** (1 bit field) + +This field indicates the access mode of the reported cell. It is coded as follows: + +- 0 The reported cell is a closed access mode cell. +- 1 The reported cell is a hybrid access mode cell. + +### **REPORTING\_QUANTITY** (6 bit field) + +This is the reporting quantity for E-UTRAN cell identified by the E-UTRAN Global Cell Identity. The quantities are defined in 3GPP TS 45.008 for the respective Radio Access mode. + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PLMN-ID struct

MCC (12 bit field)
This field contains the Mobile Country Code of the PLMN of the cell being reported.

MNC (12 bit field)
This field contains the Mobile Network Code of the PLMN of the cell being reported.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 12.61 UTRAN CSG Measurement Report + +The *UTRAN CSG Measurement Report* information element contains measurement results for a single UTRAN CSG or hybrid neighbour cell identified via its Cell Global Identity. + +**Table 12.61.1: UTRAN CSG Measurement Report information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< UTRAN CSG Measurement Report IE > ::=   < UTRAN CGI : bit (28) >   { 0   1 < PLMN-ID : < PLMN-ID struct > > }   < CSG-ID : bit (27) >   < Access Mode : bit (1) >   < REPORTING_QUANTITY : bit (6) > ;  < PLMN-ID struct > ::=   < MCC : bit (12) >   < MNC : bit (12) > ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.61.2: UTRAN CSG Measurement Report information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

UTRAN CI (28 bit field)
This field contains the Cell Identity (as defined in 3GPP TS 25.331) of the cell being reported.

PLMN-ID
This information element contains the primary PLMN-ID of the cell being reported (as defined in 3GPP TS 25.331). If this field is not present then the PLMN-ID of the target cell is the same as that of the serving cell.

CSG-ID (27 bit field)
This field contains the CSG identity (as defined in 3GPP TS 23.003) of the cell being reported.

Access Mode (1 bit field)
This field indicates the access mode of the reported cell. It is coded as follows:

  • 0 The reported cell is a closed access mode cell.
  • 1 The reported cell is a hybrid access mode cell.

REPORTING_QUANTITY (6 bit field)
This is the reporting quantity for UTRAN cell identified by the UTRAN Global Cell Identity. The quantities are defined in 3GPP TS 45.008 for the respective Radio Access mode.

PLMN-ID struct

MCC (12 bit field)
This field contains the Mobile Country Code of the PLMN of the cell being reported.

MNC (12 bit field)
This field contains the Mobile Network Code of the PLMN of the cell being reported.

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 12.62 E-UTRAN CSG Target cell + +The *E-UTRAN CSG Target cell* information element contains the description of an E-UTRAN CSG Target cell. + +**Table 12.62.1: E-UTRAN CSG Target cell information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< E-UTRAN CSG Target cell IE > ::=   < E- UTRAN CI : bit (28) >   < Tracking Area Code : bit (16) >   { 0   1 < PLMN-ID : < PLMN-ID struct > > } ;
| +| 
< PLMN-ID struct > ::=   < MCC : bit (12) >   < MNC : bit (12) > ;
| + +**Table 12.62.2: E-UTRAN CSG Target cell information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

E-UTRAN CI (28 bit field)
This field contains the E-UTRAN Cell Identity (as defined in 3GPP TS 23.003) of the target cell.

| +|

Tracking Area Code (16 bit field)
This field contains the tracking area code (as defined in 3GPP TS 24.301) of the target cell.

| +|

PLMN-ID
This information element contains the PLMN-ID of the target cell. If this field is not present then the PLMN-ID of the target cell is the same as that of the serving cell.

| +|

PLMN-ID struct

MCC (12 bit field)
This field contains the Mobile Country Code of the PLMN of the cell being reported.

MNC (12 bit field)
This field contains the Mobile Network Code of the PLMN of the cell being reported.

| + +## 12.63 UTRAN CSG Target cell + +The *UTRAN CSG Target cell* information element contains the description of a UTRAN CSG Target cell. + +**Table 12.63.1: UTRAN CSG Target cell information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------| +| 
< UTRAN CSG Target cell IE > ::=   < UTRAN CI : bit (28) >   { 0   1 < PLMN-ID : < PLMN-ID struct > > } ;
| +| 
< PLMN-ID struct > ::=   < MCC : bit (12) >   < MNC : bit (12) > ;
| + +**Table 12.63.2: UTRAN CSG Target cell information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

UTRAN CI (28 bit field)
This field contains the Cell Identity (as defined in 3GPP TS 25.331) of the target cell.

| +|

PLMN-ID
This information element contains the PLMN-ID of the target cell. If this field is not present then the PLMN-ID of the target cell is the same as that of the serving cell.

| + +### ***PLMN-ID struct*** + +### **MCC** (12 bit field) + +This field contains the Mobile Country Code of the PLMN of the cell being reported. + +### **MNC** (12 bit field) + +This field contains the Mobile Network Code of the PLMN of the cell being reported. + +## 12.64 DTM Handover PS Radio Resources 3 + +This information element provides the radio resources assigned for PS services in the new cell and is included within the DTM HANDOVER COMMAND message and can only be used when EMSR or extended TSC sets (see 3GPP TS 45.002 [32]) is supported by the mobile station. + +Table 12.64.1: DTM Handover PS Radio Resources 3 information element + +``` + +< DTM Handover PS Radio Resources 3 IE > ::= + < Cell Identification : < Cell Identification IE > > -- provided by SI/PSI for PS HO + < MAX_LAPDm : bit (3) > -- needed for DTM in new cell + < GPRS_MS_TXPWR_MAX_CCH : bit (5) > -- needed for DTM in new cell + < GPRS Cell Options : < GPRS Cell Options IE > > -- provided by SI/PSI for PS HO + < GPRS Power Control Parameters : < GPRS Power Control Parameters IE > > -- provided by SI/PSI for PS HO + < RLC_RESET : bit (1) > + { 0 < EGPRS mode : < EGPRS mode 2 IE > > + ! < TBF mode error: { 01 | 10 | 11 } bit(*) = < no string > > } -- reserved for future use + + -- Optional extension information: + { 0 | 1 < Extension Length : bit (8) > + < bit (val(Extension Length) + 1) + & { < Extension Information > ! { bit ** = < no string > } } > } ; + +< Extension Information > ::= + { { -- Rel-10 extension: + { 0 < EMST_NW_Capability : bit (1) > -- EMST is not used + | 1 -- EMST is used + { 0 + | 1 < Downlink RLC Entity 2 : < RLC Entity struct > + { 0 + | 1 < Downlink RLC Entity 3 : < RLC Entity struct > } + } + { 0 + | 1 < Uplink RLC Entity 2 : < RLC Entity struct > + { 0 + | 1 < Uplink RLC Entity 3 : < RLC Entity struct > } + } + } + { 0 | 1 MTTL_DOWNLINK_ASSIGNMENT_C1 : bit (1) } + { 0 | 1 MTTL_DOWNLINK_ASSIGNMENT_C2 : bit (1) } + { 0 | 1 MTTL_UPLINK_ASSIGNMENT_C1 : bit(1) } + { 0 | 1 MTTL_UPLINK_ASSIGNMENT_C2 : bit(1) } + { 0 -- EMSR is not enabled in downlink + | 1 -- EMSR is enabled in downlink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } + { 0 -- EMSR is not enabled in uplink + | 1 -- EMSR is enabled in uplink + { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 + { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 + } +} +{ -- Rel-11 extension: + < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > +} +{ -- Rel-12 extension: + { 0 | 1 -- Primary DL TSC Value assigned + < Primary TSC Set : bit (1) > + < Primary TSC Value : bit (3) > } + { 0 | 1 -- Secondary DL TSC Value assigned + < Secondary DL TSC Set : bit (1) > + < Secondary DL TSC Value : bit (3) > } +} +< spare bit > ** } // ; -- Extension information may be truncated between released versions of the protocol. +-- The receiver shall assume the value zero for any truncated bit. + +< RLC Entity struct > ::= + < TFI : bit (5) > + < RLC_MODE : bit (1) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } + < PFI : bit (7) > ; + +``` + +``` + +< Additional PFCs struct > ::= + < TFI : bit (5) > + { 0 | 1 < NPM Transfer Time : bit (5) > } + < PFI : bit (7) > ; + +``` + +**Table 12.64.2: DTM Handover PS Radio Resources 3 information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cell Identification (information element)
This information element is defined in sub-clause 12.23.

| +|

MAX_LAPDm (3 bit field)
This field indicates the maximum number of LAPDm frames into which a layer 3 message can be segmented sent on the main DCCH. It is coded as described in 3GPP TS 44.018.

| +|

GPRS_MS_TXPWR_MAX_CCH (5 bit field)
The GPRS_MS_TXPWR_MAX_CCH field is coded as the binary representation of the 'power control level' in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008.

| +|

GPRS Cell Options (information element)
The GPRS Cell Option information element is defined in sub-clause 12.24.

| +|

GPRS Power Control Parameters (information element)
The GPRS Power Control Parameters information element is defined in sub-clause 12.9a.

| +|

RLC_RESET (1 bit field)
This field is defined in sub-clause 12.42.

| +|

EGPRS mode 2 IE
This information element is defined in sub-clause 12.48a.1.

| +|

EMST_NW_Capability (1 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| +|

TFI (5 bit field)
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message).

| +|

RLC_MODE (1 bit field)
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message). If the RLC_RESET field indicates that any given RLC entity is not reset across PS handover then the mobile station shall ignore this field and use the same RLC mode that was used for the corresponding PFC in the old cell.

| +|

EGPRS Window Size
This information element is defined in sub-clause 12.5.2.

| +|

PFI (7 bit field)
See sub-clause 11.2.31 (Packet Timeslot Reconfigure message).

| +|

NPM Transfer Time (5 bit field)
This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode.

| +|

MTTI_DOWNLINK_ASSIGNMENT_C1 (1 bit field)
MTTI_DOWNLINK_ASSIGNMENT_C2 (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message).

| +|

MTTI_UPLINK_ASSIGNMENT_C1 (1 bit field)
MTTI_UPLINK_ASSIGNMENT_C2 (1 bit field)
See sub-clause 11.2.29 (Packet Uplink Assignment message).

| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EMSR Additional PFCs 1
EMSR Additional PFCs 2
EMSR Additional PFCs 3
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)
See sub-clause 11.2.7 (Packet Downlink Assignment message). | +| Primary TSC Set (1 bit field)
Secondary DL TSC Set (1 bit field)
See sub-clause 12.46. | +| Primary TSC Value (3 bit field)
See sub-clause 12.46. | +| Secondary DL TSC Value (3 bit field)
See sub-clause 12.46. | + +## 12.65 Dynamic Allocation 3 + +This information element provides the description of the uplink dynamic allocation information for a BTTI or an RTTI assignment in a DLMC configuration with or without power control parameters. + +**Table 12.65.1: Dynamic Allocation 3 information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < Dynamic Allocation 3 IE > ::=   < EXTENDED_DYNAMIC_ALLOCATION : bit (1) >   < USF_GRANULARITY : bit (1) >   { 0   1 < ALPHA : bit (4) > }   { 0   1 < TSC : bit (3) > }   { 0     { 1 { 0   1 < USF : bit (3) >           < GAMMA : bit (5) > } } ** 0      -- one instance provided for each assigned PDCH     1     { 1 { 0   1 < USF : bit (3) >           < GAMMA : bit (5) >           { 0             -- RTTI USF mode             1             -- BTTI USF mode             { 0               -- same BTTI USF for each RTTI block               1 < USF_2 : bit (3) > }      -- BTTI USF for the 2nd RTTI block           } } ** 0      -- one instance provided for each assigned PDCH-pair     }   } ;
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.65.2: Dynamic Allocation 3 information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EXTENDED_DYNAMIC_ALLOCATION (1 bit field)
This information field indicates the medium access mode to be used during the TBF.
0 Dynamic Allocation
1 Extended Dynamic Allocation | +| USF_GRANULARITY (1 bit field)
This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation.
0 the mobile station shall transmit one RLC/MAC block
1 the mobile station shall transmit four consecutive RLC/MAC blocks | +| ALPHA (4 bit field)
For encoding and description see the Global Power Control Parameters IE. | + +**TSC (3 bit field)** + +This field is the binary representation of the training sequence code, see 3GPP TS 45.002. Range: 0 to 7. In the absence of this field the applicable TSC shall be the same as the corresponding downlink carrier. + +--- + +**USF, USF\_2 (3 bit field)** + +These fields indicate the USF values assigned to a given TBF for the assigned timeslot or PDCH pair. + +In the case of RTTI mode with BTTI USF, the USF value specified in the USF field (respectively USF\_2 field) applies to the first two (respectively second two) TDMA frames of the following basic radio block period (see sub-clauses 8.1.1.1, 8.1.1.2.1). + +These fields are encoded as a binary representation of the USF value as defined in sub-clause 10.4.1. + +The order in which USF assignments are encoded and the meaning when the number of repetitions of the USF is lower than the maximum is described in Annex K. + +--- + +**GAMMA (5 bit field)** + +This field is the binary representation of the parameter $\Gamma$ CH for MS output power control in units of 2 dB, see 3GPP TS 45.008 [15]. The field is coded according to the following table: + +| bit | | +|-----------|---------------------| +| 5 4 3 2 1 | | +| 0 0 0 0 0 | $\Gamma$ CH = 0 dB | +| 0 0 0 0 1 | $\Gamma$ CH = 2 dB | +| : : : : | | +| 1 1 1 1 0 | $\Gamma$ CH = 60 dB | +| 1 1 1 1 1 | $\Gamma$ CH = 62 dB | + +In the case of RTTI mode with BTTI USF, exactly one GAMMA field shall be included for each PDCH pair for which either one or two USF values are assigned. + +## 12.66 DLMC Channel Quality Report + +This Information Element provides channel quality report information which may include UFPS, carrier or timeslot based measurement information for a mobile station in a DLMC configuration. The information to be included within this IE depends on the setting of the ES/P field and CES/P field (see sub-clause 9.1.8.2.1), the most recently received LINK\_QUALITY\_MEASUREMENT\_MODE field (see sub-clause 11.2.7) and the most recently received DLMC Measurement Type field (see sub-clause 11.2.7). + +**Table 12.66.1: DLMC Channel Quality Report information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < DLMC Channel Quality Report IE > ::=   C_VALUE : bit (6)   { 0   1 < DLMC Interference Measurements : < DLMC Interference Measurement Report struct >> }   { 1 < DLMC BEP Link Quality Measurements : < DLMC BEP Link Quality Measurements struct >>     { 0   1 < DLMC BEP_MEASUREMENTS : < DLMC BEP Measurements Struct >> } } ** 0; < DLMC Interference Measurement Report Struct > ::= { 0   1 < I_LEVEL_TN0 : bit (4) > } { 0   1 < I_LEVEL_TN1 : bit (4) > } { 0   1 < I_LEVEL_TN2 : bit (4) > } { 0   1 < I_LEVEL_TN3 : bit (4) > } { 0   1 < I_LEVEL_TN4 : bit (4) > } { 0   1 < I_LEVEL_TN5 : bit (4) > } { 0   1 < I_LEVEL_TN6 : bit (4) > } { 0   1 < I_LEVEL_TN7 : bit (4) > };  < DLMC BEP Link Quality Measurements struct > ::= { { 0   1 < GMSK_MEAN_BEP : bit (5) >     < GMSK_CV_BEP : bit (3) > }   { 0   1 < 8PSK_MEAN_BEP : bit (5) >     < 8PSK_CV_BEP : bit (3) > }   { 0   1 < 16QAM_NSR_MEAN_BEP : bit (5) >     < 16QAM_NSR_CV_BEP : bit (3) > }   { 0   1 < 32QAM_NSR_MEAN_BEP : bit (5) >     < 32QAM_NSR_CV_BEP : bit (3) > } };  < DLMC BEP Measurements Struct > ::= { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN0 : bit (4) > } { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN1 : bit (4) > } { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN2 : bit (4) > } { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN3 : bit (4) > } { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN4 : bit (4) > } { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN5 : bit (4) > } { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN6 : bit (4) > } { 0   1 < REPORTED_MODULATION : bit (2) >   < MEAN_BEP_TN7 : bit (4) > };
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 12.66.2: DLMC Channel Quality Report information element details** + +| | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--|---------|--|---------|-----------|---------|-----------|-----|--|---------|------------|---------|------------| +|

DLMC Interference Measurements

These information elements provide interference measurement information for a MS in a DLMC configuration. The MS provides this information for the downlink carrier indicated by the assignment message or the lowest numbered downlink carrier if carrier information for interference measurements is not provided by the assignment message.

| | | | | | | | | | | | | | | +|

C_VALUE

If the parameter PC_MEAS_CHAN (see sub-clause 12.9) indicates downlink measurements for power control shall be made on BCCH, a single instance of this field shall be reported using BCCH Carrier measurements (see 3GPP TS 45.008 [15] regarding C_VALUE determination). If PC_MEAS_CHAN indicates that the downlink measurements for power control shall be made on PDCH, a single instance of this field shall be reported for the carrier/UFPS on which the MS was polled.

| | | | | | | | | | | | | | | +|

DLMC BEP Link Quality Measurements

If the DLMC Measurement Type field (see sub-clause 11.2.7) in the last received assignment message indicates measurement information is to be reported on a per UFPS basis the measurements are reported starting with the UFPS on which the MS was polled followed by additional higher numbered UFPS (if any) beginning with the next in sequence UFPS.

If the DLMC Measurement Type field (see sub-clause 11.2.7) in the last received assignment message indicates measurement information is to be reported on a per carrier basis the measurements are reported starting with the carrier on which the MS was polled followed by additional higher numbered carriers (if any) beginning with the next in sequence carrier.

The number of UFPS/carriers reported is determined by the space available in the reporting message (see sub-clause 9.1.8.2.1). If RLC/MAC blocks have not been received on a given UFPS/carrier since the last reporting period it shall still be listed in but no measurement results shall be included.

| | | | | | | | | | | | | | | +|

DLMC BEP_MEASUREMENTS

This field is included when the DLMC Measurement Type field (see sub-clause 11.2.7) in the last received assignment message indicates measurement information is to be reported on a per carrier basis and the LINK_QUALITY_MEASUREMENT_MODE field (see sub-clause 11.2.7) received in the same assignment message indicates the mobile station shall report the mean BEP on each assigned time slot. When included it only provides information for each timeslot assigned to the carrier on which the MS was polled.

| | | | | | | | | | | | | | | +|

I_LEVEL_TN0 (4 bit field)
I_LEVEL_TN1 (4 bit field)
I_LEVEL_TN2 (4 bit field)
I_LEVEL_TN3 (4 bit field)
I_LEVEL_TN4 (4 bit field)
I_LEVEL_TN5 (4 bit field)
I_LEVEL_TN6 (4 bit field)
I_LEVEL_TN7 (4 bit field)

These fields contain the \gamma value calculated on timeslots 0 through 7, respectively. The \gamma value is defined in 3GPP TS 45.008. These fields are encoded relative to the applicable C_VALUE (see C_VALUE field description above) as defined for the mapping defined in 3GPP TS 45.008 [15] for interference level (I_LEVEL):

bit
4 3 2 1
0 0 0 0 I_LEVEL 0
0 0 0 1 I_LEVEL 1
...
1 1 1 0 I_LEVEL 14
1 1 1 1 I_LEVEL 15
| bit | | 4 3 2 1 | | 0 0 0 0 | I_LEVEL 0 | 0 0 0 1 | I_LEVEL 1 | ... | | 1 1 1 0 | I_LEVEL 14 | 1 1 1 1 | I_LEVEL 15 | +| bit | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | +| 0 0 0 0 | I_LEVEL 0 | | | | | | | | | | | | | | +| 0 0 0 1 | I_LEVEL 1 | | | | | | | | | | | | | | +| ... | | | | | | | | | | | | | | | +| 1 1 1 0 | I_LEVEL 14 | | | | | | | | | | | | | | +| 1 1 1 1 | I_LEVEL 15 | | | | | | | | | | | | | | + +**GMSK\_MEAN\_BEP** (5 bit field) +**8PSK\_MEAN\_BEP** (5 bit field) +**16QAM\_NSR\_MEAN\_BEP** (5 bit field) +**32QAM\_NSR\_MEAN\_BEP** (5 bit field) + +These fields contain the mean value of the Bit Error Probability of the channel averaged over all timeslots in the UFPS for the relevant modulation scheme, refer to 3GPP TS 45.008 [15]. + +**GMSK\_CV\_BEP** (3 bit field) +**8PSK\_CV\_BEP** (3 bit field) +**16QAM\_NSR\_CV\_BEP** (3 bit field) +**32QAM\_NSR\_CV\_BEP** (3 bit field) + +These fields contain the variation coefficient for the Bit Error Probability averaged over all timeslots of the UFPS for the relevant modulation scheme, refer to 3GPP TS 45.008 [15]. + +**REPORTED\_MODULATION** (2 bit field) + +The mobile station shall report the modulation scheme (indicated using the REPORTED\_MODULATION field) with which it has received the largest number of blocks since the last report and shall report the MEAN\_BEP\_TNx of that modulation scheme (see 3GPP TS 45.008). The mapping of the modulation scheme is as follows. + +| | | +|-----|-------| +| bit | | +| 2 1 | | +| 0 0 | GMSK | +| 0 1 | 8PSK | +| 1 0 | 16QAM | +| 1 1 | 32QAM | + +**MEAN\_BEP\_TN0** (4 bit field) +**MEAN\_BEP\_TN1** (4 bit field) +**MEAN\_BEP\_TN2** (4 bit field) +**MEAN\_BEP\_TN3** (4 bit field) +**MEAN\_BEP\_TN4** (4 bit field) +**MEAN\_BEP\_TN5** (4 bit field) +**MEAN\_BEP\_TN6** (4 bit field) +**MEAN\_BEP\_TN7** (4 bit field) + +These fields contain the mean bit error probability value calculated on timeslots 0 through 7 for the modulation scheme indicated using the REPORTED\_MODULATION field. For the calculation of the mean bit error probability, refer to 3GPP TS 45.008. These fields are transferred only when the mobile station is in packet transfer mode. In RTTI configuration, the mean bit error probability value calculated on per timeslot pair shall be reported on **MODULATION\_1\_MEAN\_BEP\_TNx / MODULATION\_2\_MEAN\_BEP\_TNx** where TNx is the lower numbered timeslot of each reported timeslot pair. + +## 12.67 DOWNLINK\_eTFI\_ASSIGNMENT + +This information element is only used for a DLMC configuration and identifies the extended TFI (eTFI) that along with the TFI is unique to the PDCHs resources assigned to a MS on a given downlink carrier of a downlink Temporary Block Flow (TBF). The eTFI and TFI values assigned for a given downlink carrier may be different from those assigned for any other carrier on which it has been assigned PDCH resources for its downlink TBF. + +**Table 12.67.1: DOWNLINK\_eTFI\_ASSIGNMENT information element details** + +**DOWNLINK\_eTFI\_ASSIGNMENT** (3 bit field) + This field is encoded as a binary number. + Range 0 to 7 + +## 12.68 E-UTRAN Target Cell with extended EARFCN + +The *E-UTRAN Target cell with extended EARFCN* information element contains the description of an E-UTRAN Target cell. + +**Table 12.68.1: E-UTRAN Target cell with extended EARFCN information element** + +``` +< E-UTRAN Target cell with extended EARFCN IE > ::= + < EARFCN_extended : bit (18) > + { 0 | 1 < Measurement Bandwidth: bit (3) > } + < Physical Layer Cell Identity : bit (9) > ; +``` + +**Table 12.68.2: E-UTRAN Target cell with extended EARFCN information element details** + +### EARFCN\_extended (18 bit field) + +This field is defined in sub-clause 12.70. + +#### Measurement Bandwidth (3 bit field) + +This optional field describes the bandwidth of the E-UTRAN cell for measurement purposes. The coding of this field is as specified in sub-clause 12.53. + +#### Physical Layer Cell Identity (9 bit field) + +This field indicates the physical layer cell identity as defined in 3GPP TS 36.211. + +## 12.69 E-UTRAN IPP with extended EARFCNs + +This information element is sent to provide MS-specific E-UTRAN priorities for priority-based cell reselection (see 3GPP TS 45.008). The MS-specific E-UTRAN priorities provided by this IE shall override the E-UTRAN priorities received through system information or previously received E-UTRAN individual priorities. + +**Table 12.69.1: E-UTRAN IPP with extended EARFCNs information element** + +``` +< E-UTRAN IPP with extended EARFCNs IE > ::= + { 0 | 1 < DEFAULT_E-UTRAN_PRIORITY : bit(3) > } + { 1 < Repeated Individual E-UTRAN PP with extended EARFCNs: + < Repeated Individual E-UTRAN PP with extended EARFCNs struct >> } ** 0 ; + +< Repeated Individual E-UTRAN PP with extended EARFCNs struct > ::= + { 1 < EARFCN_extended : bit (18) > } ** 0 + < E-UTRAN_PRIORITY : bit(3) > ; +``` + +**Table 12.69.2: E-UTRAN IPP with extended EARFCNs information element details** + +### **E-UTRAN\_PRIORITY** (3 bit field) + +This field is used for the inter-RAT cell re-selection algorithm based on priority information, see sub-clause 12.53. + +### **DEFAULT\_E-UTRAN\_PRIORITY** (3 bit field) + +The DEFAULT\_E-UTRAN\_PRIORITY field is encoded as the E-UTRAN\_PRIORITY field. Any E-UTRAN frequency contained in the E-UTRAN Neighbour Cell list and not explicitly listed in any occurrence of the *Repeated Individual E-UTRAN PP with extended EARFCNs* IE shall be assigned the corresponding default value. If the *Repeated Individual E-UTRAN PP with extended EARFCNs* IE is not present, every E-UTRAN frequency in the E-UTRAN Neighbour Cell list for the serving cell shall be assigned the default value. + +### **EARFCN\_extended** (18 bit field) + +This field is defined in sub-clause 12.70. + +## 12.70 E-UTRAN NC with extended EARFCNs + +This information element is sent to provide information about E-UTRAN frequencies and priority information for neighbouring E-UTRAN cells. + +**Table 12.70.1: E-UTRAN NC with extended EARFCNs information element** + +``` +< E-UTRAN NC with extended EARFCNs IE > ::= + { 1 < Repeated E-UTRAN NC with extended EARFCNs : + < Repeated E-UTRAN NC with extended EARFCNs struct >> } ** 0; + +< Repeated E-UTRAN NC with extended EARFCNs struct > ::= + { 1 < EARFCN_extended : bit (18) > + { 0 | 1 < Measurement Bandwidth : bit (3) > } ** 0 + { 0 | 1 < E-UTRAN_PRIORITY : bit(3) > } + < THRESH_E-UTRAN_high : bit(5) > + { 0 | 1 < THRESH_E-UTRAN_low : bit(5) > } + { 0 | 1 < E-UTRAN_QRXLEVMIN : bit(5) > }; +``` + +**Table 12.70.2: E-UTRAN NC with extended EARFCNs information element details** + +### **E-UTRAN NC with extended EARFCNs** + +This information element is included in the message to provide E-UTRAN frequencies and priority information for a mobile station supporting extended EARFCNs (see 3GPP TS 24.008). + +### **Repeated E-UTRAN NC with extended EARFCNs** + +#### **EARFCN\_extended** (18 bit field) + +This field specifies the E-UTRA Absolute Radio Frequency Channel Number as defined in 3GPP TS 36.104. For an E-UTRAN frequency for which the corresponding EARFCN has a value below 65535, the two most significant bits (bit 17 and 18) shall be set to 0. + +#### **Measurement Bandwidth** (3 bit field) + +This field specifies the minimum value of the channel bandwidth of all valid E-UTRAN cells on the specified EARFCN, as defined in sub-clause 12.53. + +### **E-UTRAN\_PRIORITY** (3 bit field) + +#### **THRESH\_E-UTRAN\_high** (5 bit field) + +#### **THRESH\_E-UTRAN\_low** (5 bit field) + +If THRESH\_E-UTRAN\_low is not present, then THRESH\_E-UTRAN\_low shall take on the same value as THRESH\_E-UTRAN\_high. + +#### **E-UTRAN\_QRXLEVMIN** (5 bit field) + +These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. These values apply to each of the EARFCN values listed within this structure. + +## 12.71 Used DL Coverage Class + +The Used DL Coverage Class indicates the DL Coverage Class, and thus the number of blind physical layer transmissions, that the current RLC/MAC message is being transmitted with. + +**Table 12.71.1: Used DL Coverage Class information element details** + +### **Used DL Coverage Class** (2 bit field) + +An RLC/MAC control message on the EC-PACCH is sent with one or several blind physical layer transmissions, depending on the assigned DL Coverage Class for the mobile station that the message is being sent to. The USED\_DL\_COVERAGE\_CLASS IE is included in order to inform other mobile stations about the DL Coverage Class, and thus the number of blind physical layer transmissions, that are being used when transmitting the current RLC/MAC message on the EC-PACCH. Other mobile stations, with a lower CC, can thus avoid monitoring the corresponding downlink resources while remaining transmissions of the message, if any, are being performed. + +If the field EC\_Reduced\_PDCH\_Allocation is set to 1 in the EC SYSTEM INFORMATION TYPE 2 message, (see 3GPP TS 44.018) and if the parameter Used DL Coverage Class is other than CC1, the mapping used for the DL control blocks (EC-PACCH/D) onto physical channels shall be as specified in 3GPP TS 45.002. + +The USED\_DL\_COVERAGE\_CLASS field is encoded according to the following table: + +| bit | | +|-----|---| +| 2 | 1 | +| 0 | 0 | +| 0 | 1 | +| 1 | 0 | +| 1 | 1 | + +## 12.72 EC Ack/Nack Description + +The EC Ack/Nack Description information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks. + +**Table 12.72.1: EC Ack/Nack Description information element details** + +``` +< EC Ack/Nack Description IE > ::= + < STARTING_SEQUENCE_NUMBER : bit (5) > + < RECEIVED_BLOCK_BITMAP : bit (16) > ; +``` + +## 12.73 EC Primary Ack/Nack Description + +The EC Primary Ack/Nack Description information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks in an EC Packet Uplink Ack/Nack message, including the TLLI or the rTLLI (for contention resolution), or in an EC Packet Uplink Ack/Nack and Contention Resolution message. + +**Table 12.73.1: EC Primary Ack/Nack Description information element details** + +``` +< EC Primary Ack/Nack Description IE > ::= + < STARTING_SEQUENCE_NUMBER : bit (5) > + < RECEIVED_BLOCK_BITMAP : bit (8) > ; +``` + +## 12.74 EC Packet Timing Advance + +The EC Packet Timing Advance field describes the timing advance value assigned to the mobile station for use during an uplink or downlink EC TBF. + +**Table 12.74.1: EC Packet Timing Advance information element details** + +``` +< EC Packet Timing Advance IE > ::= + < TIMING_ADVANCE_VALUE : bit (6) > ; +``` + +**Table 12.74.2: EC Packet Timing Advance information element details** + +### TIMING\_ADVANCE\_VALUE (6 bit field) + +The Timing Advance value field is encoded the same as the Timing Advance value of the Timing Advance information element defined in 3GPP TS 44.018, with the value range 0 to 63. + +## 12.75 EC Channel Quality Report + +The EC Channel Quality Report information element is defined in tables 12.75.1 and 12.75.2. + +**Table 12.75.1: EC Channel Quality Report Information elements** + +``` +< EC Channel Quality Report IE > ::= + { 0 | 1 < GMSK_MEAN_BEP : bit (5) > + < GMSK_CV_BEP : bit (3) > } + { 0 | 1 < 8PSK_MEAN_BEP : bit (5) > + < 8PSK_CV_BEP : bit (3) > } ; + < C_VALUE : bit (6) > ; +``` + +**Table 12.75.2: EC Channel Quality Report Information Elements details** + +### GMSK\_MEAN\_BEP (5 bit field) + +This field contains the mean value of the Bit Error Probability of the channel averaged over all time slots in the TBF for + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GMSK, refer to 3GPP TS 45.008. | +| GMSK_CV_BEP (3 bit field)
This field contains the variation co-efficient for the Bit Error Probability averaged over all time slots of the TBF for GMSK, refer to 3GPP TS 45.008. | +| 8PSK_MEAN_BEP (5 bit field)
This field contains the mean value of the Bit Error Probability of the channel averaged over all time slots in the TBF for 8 PSK, refer to 3GPP TS 45.008. | +| 8PSK_CV_BEP (3 bit field)
This field contains the variation co-efficient for the Bit Error Probability averaged over all time slots of the TBF for 8 PSK, refer to 3GPP TS 45.008. | +| C_VALUE (6 bits)
This field contains the value of the C parameter calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as the binary representation of the C value parameter value defined in 3GPP TS 45.008.
Range 0 to 63 | + +## 12.76 EC Channel Quality Report Higher CC + +The EC Channel Quality Report Higher CC information element is defined in tables 12.76.1 and 12.76.2. + +**Table 12.76.1: EC Channel Quality Report Higher CC Information elements** + +| | +|-----------------------------------------------| +| < EC Channel Quality Report Higher CC IE> ::= | +| { 0 1 < GMSK_MEAN_BEP : bit (5) > | +| < GMSK_CV_BEP : bit (3) > } | +| < C_VALUE : bit (6) > ; | + +**Table 12.76.2: EC Channel Quality Report Higher CC Information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GMSK_MEAN_BEP (5 bit field)
This field contains the mean value of the Bit Error Probability of the channel averaged over all time slots in the TBF for GMSK, refer to 3GPP TS 45.008. | +| GMSK_CV_BEP (3 bit field)
This field contains the variation co-efficient for the Bit Error Probability averaged over all time slots of the TBF for GMSK, refer to 3GPP TS 45.008. | +| C_VALUE (6 bits)
This field contains the value of the C parameter calculated by the mobile station (see 3GPP TS 45.008). This field is encoded as the binary representation of the C value parameter value defined in 3GPP TS 45.008.
Range 0 to 63 | + +# --- 13 Timers and counters + +The tables in sub-clause 13.1 and 13.2 specify the timers used in RLC/MAC protocol signalling. The denotation of columns is defined as follows: + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| timer ::= | name of the timer; | +| started ::= | under which conditions the timer is started; | +| stopped ::= | under which conditions the timer is stopped; | +| action at expiry ::= | which actions the GPRS entity shall perform at expiry; | +| value ::= | the duration between setting the timer and expiry of the timer ("s" denotes "second(s)" "xx - yy" means that any value between xx and yy is permitted). | + +## 13.1 Timers on the Mobile Station side + +For each timer, it is shown whether one timer instance is needed per MS, per TBF/MBMS radio bearer, per MS\_ID or per RLC/MAC control message. + +For EC-GSM-IoT, where blind physical layer transmissions are used, if a timer expires during an ongoing transmission opportunity, that transmission opportunity shall be considered as having occurred prior to the expiry of the timer. + +Error: + +251 + +Error: Reference source not + +**Table 13.1.1: Specification of timers used in GPRS on the Mobile Station side** + +| timer | started | stopped | action at expiry | value | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| T3158
(per MS) | Started when ordered by a NETWORK_CONTROL_ORDER and then restarted each time a Network Controlled (NC) Measurement is performed in MM Ready state and in packet idle or packet transfer mode in A/Gb mode and in RRC-Cell_Shared state and MAC-Idle or MAC-Shared state in Iu mode . | See 3GPP TS 45.008 | Restart the timer, perform the measurement and send a NC Measurement report. The timer shall be restarted with either of the parameters NC_REPORTING_PERIOD_I when in packet idle mode or MAC-Idle state or with the parameter NC_REPORTING_PERIOD_T when in packet transfer mode or MAC-Shared state | Defined by the parameter or by a random value (see 3GPP TS 45.008) | +| T3162
(per MS) | On receipt of a PACKET QUEUING NOTIFICATION | On receipt of a PACKET UPLINK ASSIGNMENT | Abort packet access procedure; indicate packet access failure to upper layers and return to packet idle mode or MAC-Idle state listening to its paging subchannel | 5 s | +| T3164
(per TBF) | On receipt of a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message. A separate instance of T3164 is started for each TBF for which resources were assigned. | At sending of the first RLC/MAC block | See sub-clause 7.1.4. ( A/Gb mode ). | 5 s | +| T3166
(per MS) | At sending of the first RLC/MAC block at one phase access | On receipt of a PACKET UPLINK ACK/NACK | Immediately stop transmitting on the assigned TBF; a TBF establishment failure has occurred or the contention resolution procedures has failed | 5 s | + +| timer | started | stopped | action at expiry | value | +|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T3168
(per TBF) | At sending the PACKET RESOURCE REQUEST message, (Extended) Channel Request Description IE in PACKET DOWNLINK ACK/NACK or the PACKET CONTROL ACKNOWLEDGEMENT message requesting new TBF. A separate instance of T3168 is started for each TBF for which resources were requested.

For an EC TBF, started at sending the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the EC Channel Request Description IE. | On receipt of a PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources to an uplink TBF for which T3168 is running. On receipt of a PACKET ACCESS REJECT or EC PACKET ACCESS REJECT message that rejects one or more uplink TBFs for which T3168 is running.

For an EC TBF, restarted at a new transmission of an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the EC Channel Request Description IE. | Reinitiate the packet access procedure or retransmit the PACKET RESOURCE REQUEST or PACKET DOWNLINK ACK/NACK for the TBFs that have not been assigned resources.

A mobile station in EC operation may again include the EC Channel Request Description IE in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message. The EC Channel Request Description IE may however be included in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to '1' even if timer T3168 is still running.

For a mobile station in EC operation that has included the EC Channel Request Description IE in an EC PACKET DOWNLINK ACK/NACK message with the Final Ack Indicator bit set to '1', release the TBF resources, unless timer T3192 is still running. The packet access procedure may then be reinitiated on the (EC-)CCCH. | Set to 2 times the value of T3168 sent as part of system broadcast information if the total number of TBFs requested is greater than 1. Otherwise, it shall be set to the value of T3168 sent as part of system broadcast information (on BCCH or EC-BCCH).

For a mobile station in EC operation, if the value of T3168 was not provided in the EC SI, the value 0 (500 ms) shall be used. | +| T3170
(per MS) | After having made M + 1 attempts to send a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST message (if at least one message was transmitted by the mobile station), or on receipt of a PACKET ACCESS REJECT message. | On receipt of a PACKET UPLINK ASSIGNMENT or PACKET DOWNLINK ASSIGNMENT or PACKET QUEUING NOTIFICATION message. | Abort packet access procedure. In case of the expiry after having made M+1 attempts to send a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST message, indicate a random access failure to upper layers and perform autonomous cell re-selection. In case of the expiry following the receipt of a PACKET ACCESS REJECT message, indicate a packet access failure to upper layers and return to packet idle mode or MAC-Idle state. | Defined by parameters TX_INT and S | +| T3172
(per TBF) | On receipt of an (EC) PACKET ACCESS REJECT message an instance of T3172 is started for each of the TBFs that have been rejected. | On receipt of a PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT message or MULTIPLE TBF UPLINK ASSIGNMENT that assigns resources to the TBF for which T3172 is running. | Packet Access in the cell no longer prohibited | assigned in message | +| T3174
(per MS) | On receipt of a PACKET CELL CHANGE ORDER message | On the successful completion or the occurrence of an abnormal condition in the network controlled cell reselection procedure | Return to old cell, perform cell update (or other GMM specific procedure) and send PACKET CELL CHANGE FAILURE | 15 s | + +| timer | started | stopped | action at expiry | value | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| +| T3176
(per MS) | Expiry of T3174 or other abnormal condition in the network controlled cell reselection procedure | After sending of PACKET CELL CHANGE FAILURE message | Stop handling of abnormal condition in the network controlled cell reselection procedure. | 15 s | +| T3180
(per TBF) | When transmitting an RLC/MAC block to the network an instance of T3180 is started for the TBF for which the block was intended. It is also started for each uplink TBF allocated by the PS HANDOVER COMMAND message/DTM HANDOVER COMMAND message upon successful completion of the PS handover/DTM handover from Iu mode to A/Gb mode . | When detecting an assigned USF value on assigned PDCH | Abnormal release with access retry may be performed under certain conditions (see sub-clause 8.1.1.1) | 5 s | +| T3182
(per TBF) | After sending the last data block (with CV = 0), or upon detecting a transmit window stall condition an instance of T3182 is started for the TBF for which the condition has occurred. | On receipt of the PACKET UPLINK ACK/NACK message | Abnormal release with access retry may be performed under certain conditions (see sub-clauses 9.3.2.3 and 9.3.3.3) | 5 s | +| T3184
(per TBF) | On receipt of a PACKET UPLINK ACK/NACK message (in exclusive allocation) | On receipt of PACKET UPLINK ACK/NACK message (T3184 is also restarted) | Abnormal release with access retry may be performed under certain conditions (see sub-clause 8.1.1.3a.2). | 5 s | +| T3186
(per MS) | When packet access procedure is started | Either stopped when receiving any message from the network in response to the (EGPRS) PACKET CHANNEL REQUEST message or after M+1 attempts to send (EGPRS) PACKET CHANNEL REQUEST messages on the PRACH channel or stopped when receiving any message from the network in response to the MPRACH PACKET CHANNEL REQUEST message or after M+1 attempts to send MPRACH PACKET CHANNEL REQUEST messages on the uplink PDCH channel | Abort packet access procedure. If at least one message was transmitted by the mobile station, indicate random access failure to upper layers and perform autonomous cell re-selection; otherwise, indicate packet access failure to upper layers and return to packet idle mode or MAC-Idle state. | 5 s | +| T3188 | When a mobile station that supports multiple TBF procedures requests two or more uplink TBFs in a Packet Resource Request message during a two-phase access. | When a mobile station that supports multiple TBF procedures receives a MULTIPLE TBF UPLINK ASSIGNMENT message. | A mobile station that supports multiple TBF procedures considers its' two-phase access to have failed | Set to the value of T3168 included as part of system broadcast information. | + +| timer | started | stopped | action at expiry | value | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T3190
(per TBF/
MBMS
radio
bearer) | At reception of a downlink assignment message an instance of T3190 is started for each TBF/MBMS radio bearer that has been assigned resources. It is also started for each downlink TBF allocated by the PS HANDOVER COMMAND message/DTM HANDOVER COMMAND message upon successful completion of the PS handover/DTM handover from Iu mode to A/Gb mode . | Restarted on receipt of data on the TBF/MBMS radio bearer | Abnormal release without retry may be performed under certain conditions (see sub-clauses 8.1.2.1 and 8.1.2.4).
The MBMS packet access procedure may be initiated as specified in sub-clause 7.7.1. | 5 s | +| T3192
(per TBF/
per RLC
(NOTE
1)) | At sending the (EC) PACKET DOWNLINK ACK/NACK with the Final Ack Indicator=1, or at sending the PACKET CONTROL ACK as a response to final RLC data block in unacknowledged mode. | Restarted at sending the (EC) PACKET DOWNLINK ACK/NACK with the Final Ack Indicator=1, or at sending the PACKET CONTROL ACK as a response to final RLC data block in unacknowledged mode.

Stopped at the reception of a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message that assigns resources to the TBF for which T3192 was started.

For an EC TBF, stopped at the reception of an EC PACKET DOWNLINK ASSIGNMENT or EC PACKET UPLINK ASSIGNMENT message. | If the mobile station is in packet transfer mode or MAC-Shared state it shall release the resources, stop monitoring the PDCHs, and begin to monitor the paging channel if there are no other ongoing TBFs. The mobile station in dual transfer mode respectively MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. (see sub-clauses 9.3.2.6 and 9.3.3.5).

A mobile station with an EC TBF shall release the resources, stop monitoring the EC-PDTCH(s)/EC-PACCH(s) and return to packet idle mode, unless timer T3168 is still running. | assigned in system information

For a mobile station in EC operation, if the value of T3192 was not provided in the EC SI, the timer shall be set to 0 ms. | +| T3194
(per TBF) | At the sending of a RLC data block on a radio block that has been stolen (i.e. intended for a different radio bearer). | On receipt of the USF for the radio bearer for which the radio block was stolen. | Restart the timer unless it has expired four times, in which case a link failure is reported to the RRC layer. | 200 ms | +| T3196 | When the RR connection request is received from the upper layer. | Upon receipt of the PACKET CS COMMAND message. | Release of all ongoing TBFs and start RR connection establishment as specified in 3GPP TS 44.018. | 1.5 s | +| T3200
(per
RLC/MAC
control
message) | On receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message | On receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message such that the mobile station now has the complete control message | Discard and ignore all segments of the partially received RLC/MAC control message | see sub-clause 9.1.12b
For EC-GSM-IoT: 1200ms | + +| timer | started | stopped | action at expiry | value | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| T3204
(per MS) | The first attempt to send a PACKET CHANNEL REQUEST during a packet access procedure. The PACKET CHANNEL REQUEST was attempted indicating 'Single block without TBF establishment' and the purpose of the packet access procedure is to send a PACKET PAUSE message. | Upon receipt of a PACKET UPLINK ASSIGNMENT. | The packet pause procedure (sub-clause 7.6) is aborted (A/Gb mode only). | 1 s | +| T3206
(per MS) | When entering CCN mode | When the PACKET CELL CHANGE NOTIFICATION message is transmitted or when CCN is no longer enabled. | Leave CCN mode and continue according to current NC mode | 400 ms | +| T3208
(per MS) | When the PACKET CELL CHANGE NOTIFICATION message is transmitted for the first time | Upon receipt of a PACKET CELL CHANGE CONTINUE or a PACKET CELL CHANGE ORDER message or when CCN is no longer enabled.. | Leave CCN mode and continue according to current NC mode | 0,96 s | +| T3210
(per MS) | When the PACKET CELL CHANGE NOTIFICATION message is transmitted for the first time | Upon receipt of a PACKET NEIGHBOUR CELL DATA message, or a PACKET CELL CHANGE CONTINUE message or a PACKET CELL CHANGE ORDER message or when CCN is no longer enabled. | Retransmit the PACKET CELL CHANGE NOTIFICATION message at the first uplink opportunity. | 0,3 s | +| T3214 | When the MBMS SERVICE REQUEST message is transmitted or when receiving MBMS notification, for an MBMS session the mobile station is required to receive, with no MBMS p-t-m channel description and indicating that no counting shall be performed. | Upon receipt of the MBMS ASSIGNMENT message addressing the same session that started this timer or any other procedure on (P)CCCH not related to MBMS is triggered or a notification is received for a higher priority session. | Mobile station in packet idle mode or MAC-Idle state: Return to DRX mode.

Mobile station in broadcast/multicast receive mode: Remain in broadcast/multicast receive mode | 60 s | +| T3216
(per MS) | Upon transmission of the PS HANDOVER ACCESS message (see sub-clause 8.10.4.4.4). | Upon receipt of the PACKET PHYSICAL INFORMATION message | The MS returns to the old cell and attempts to resume packet data transmission (see sub-clause 8.10.5). | 1 s | +| T3218
(per MS) | On receipt of PS HANDOVER COMMAND message or Handover from UTRAN Command message or MobilityFromEUTRACommand message. | Upon detecting of the first USF for any uplink TBF assigned to the MS in the new cell. | The MS returns to the old cell and attempts to resume packet data transmission (see sub-clause 8.10.5). | 1 s | +| T3220 | When the PACKET PAGING REQUEST message containing MBMS pre-notification parameters, for an MBMS session the mobile station is required to receive, is received. | Upon receipt of the PACKET PAGING REQUEST message containing MBMS notification parameters of the same session that started this timer or any other procedure on PCCCH not related to MBMS is triggered or a notification is received for a higher priority session. | Mobile station in packet idle mode or MAC-Idle state: Return to DRX mode.

Mobile station in broadcast/multicast receive mode: Remain in broadcast/multicast receive mode | 46 s | + +| timer | started | stopped | action at expiry | value | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------| +| T3222 | When the PACKET MBMS ANNOUNCEMENT message is received indicating an MBMS broadcast service or an MBMS multicast service to which the mobile station has subscribed and an MBMS session the mobile station has not received, and including the Restriction Timer or the Estimated Session Duration. | When the mobile station enters packet idle mode, if the PACKET MBMS ANNOUNCEMENT message included the Estimated Session Duration.

When the mobile station enters packet idle mode and completes the Transfer non-DRX mode period, if the PACKET MBMS ANNOUNCEMENT message included the Restriction Timer. | The MBMS related information stored upon receipt of the corresponding PACKET MBMS ANNOUNCEMENT message is deleted. | See sub-clause 6.3.2.2 | + +| timer | started | stopped | action at expiry | value | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| T3226 | When the last allocated RLC data block has been transmitted according to a fixed uplink allocation (as received in an EC IMMEDIATE ASSIGNMENT, EC PACKET UPLINK ACK/NACK, EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION or EC PACKET UPLINK ASSIGNMENT message). | None | Timer T3228 is started and the mobile station starts to continuously read the downlink EC-PACCH for reception of an RLC/MAC control message. | assigned in EC system information

If the value of T3226 was not provided in the EC SI, the timer shall be set to 0 ms in EC operation | +| T3228 | At expiry of timer T3226. | Upon receipt of an EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with the uplink TBF. | The TBF shall be released and abnormal release with access retry may be performed, unless T3248 is used, i.e. it has a value > 0.
If timer T3248 is used, it shall be started at expiry of T3228. The next higher CC shall then be used when monitoring the DL EC-PACCH, as long as T3248 is running. | 5 s minus the value for T3248 timer | +| T3238 | At reception of an EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1' and indicating that the mobile station shall continue monitoring the EC-PACCH. | At reception of an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station, or at reception of another RLC/MAC control message triggering the release of the uplink TBF. | The mobile station shall leave the uplink TBF and return to packet idle mode. | Assigned in message | +| T3248 | At expiry of timer T3228. | Upon receipt of an EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with the uplink TBF. | The TBF shall be released. Abnormal release with access retry may be performed. | assigned in EC system information (EC SI)

If assignment of timer value is not included in EC SI it has the value 0 and is thus not used | +| T3290
(per MS_ID on an MBMS radio bearer) | At reception of a downlink assignment (i.e. MBMS ASSIGNMENT, MBMS MS_ID ASSIGNMENT) message assigning an MS_ID to a mobile station receiving an MBMS radio bearer. | Restarted on receipt of an RLC/MAC block including the corresponding MBMS Bearer Identity and the MS_ID in the TFI field. | The mobile station considers the MS_ID as released, i.e. it no longer answers when polled with the MS_ID. | 5 s | +| T3230
(per MS) | When the PACKET CELL CHANGE ORDER or PACKET MEASUREMENT ORDER message containing individual priorities, is received. | Upon occurrence of one of the conditions specified in subclause 5.5.1.1c.3. | The MS shall delete the individual priorities value. | Assigned in message | + +| timer | started | stopped | action at expiry | value | +|-------------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-------| +| T3232
(per MS) | At reception of a PACKET PAGING REQUEST message on the PPCH carrying a segment of an ETWS Primary Notification message. | At reception of the complete ETWS Primary Notification message or upon initiating cell reselection or connection establishment procedures. | The mobile station shall enter DRX mode. | 5 s | + +NOTE 1: Timer per RLC entity if EMST is used. + +**T3158:** Wait for sending measurement reports for network controlled cell reselection. + +This timer is used on the mobile station side to define the period for performing NC-measurements and send measurement reports in either packet idle or packet transfer mode in *A/Gb mode* and MAC-Idle or MAC-Shared state in *Iu mode* (see 3GPP TS 45.008). + +**T3162:** Wait for Packet Uplink Assignment after reception of Packet Queuing Notification + +This timer is used on the mobile station side after received Packet Queuing Notification to define when to stop waiting for a Packet Uplink Assignment. + +**T3164:** Wait for Uplink State Flag After Assignment + +This timer is used on the mobile station side to define when to stop waiting for the USF determining the assigned portion of the uplink channel and repeat the procedure for random access. In multislot operation, it is enough that the assigned USF is noted on one of the uplink PDCHs. + +**T3166:** Wait for Packet Uplink ACK/NACK after sending of first data block + +This timer is used on the mobile station side to define when to stop waiting for a Packet Uplink ACK/NACK after sending of the first data block. + +**T3168:** Wait for PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message + +This timer is used on the mobile station side to define when to stop waiting for a PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message after sending of a PACKET RESOURCE REQUEST message, a PACKET DOWNLINK ACK/NACK message, an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message or a PACKET CONTROL ACKNOWLEDGEMENT message requesting new TBF. + +**T3170:** Wait for PACKET UPLINK ASSIGNMENT message after having done (M+1) Packet Channel Requests or after reception of a PACKET ACCESS REJECT message. + +This timer is used on the mobile station side when having made M + 1 attempts to send a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST message (if at least one message was transmitted by the mobile station) or after reception of a PACKET ACCESS REJECT message. At expiry of timer T3170 when having made M+1 attempts to send a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST message, the mobile station shall abort the packet + +access procedure, indicate a random access failure to upper layers and perform autonomous cell re-selection according to 3GPP TS 43.022. At expiry of timer T3170 after receiving a PACKET ACCESS REJECT message, the mobile station shall abort the packet access procedure, indicate a packet access failure to upper layers and return to packet idle mode or MAC-Idle state. + +The value of this timer is equal to the time taken by T+2S TDMA frames, T and S are defined in sub-clause 7.1.2.1.1. + +**T3172:** Prohibit packet access in the cell after (EC) PACKET ACCESS REJECT message has been received. + +This timer is used on the mobile station side on receipt of a PACKET ACCESS REJECT message corresponding to one of the mobile station's 3 last PACKET CHANNEL REQUEST messages. If T3172 expires before receiving an assignment message, the mobile station returns to packet idle mode or MAC-Idle state. + +After T3172 expiry packet Access is no longer prohibited in the cell but no Channel Request message shall be sent as a response to a page until a PAGING REQUEST message for the mobile station is received. + +**T3174:** Wait for successful packet access in new cell after Packet Cell Change Order. + +This timer is used on the mobile station side on receipt of a PACKET CELL CHANGE ORDER message. The timer is stopped upon successful completion of packet access in the new cell. On expiry, the mobile station returns to the old cell, performs cell update (or other GMM specific procedure) and sends PACKET CELL CHANGE FAILURE message. + +**T3176:** Stop handling of abnormal condition in the network controlled cell reselection procedure. + +This timer is started when T3174 expires or another abnormal condition occurs in the network controlled cell reselection procedure. The timer is stopped upon transmission of the PACKET CELL CHANGE FAILURE message. On expiry, the mobile station stops handling of abnormal condition in the network controlled cell reselection procedure. + +**T3180:** Wait for Uplink State Flag After Data Block + +This timer is used on the mobile station side to define when to stop waiting for the USF determining the assigned portion of the uplink channel after the previous RLC/MAC block is sent. In multislot operation, it is enough that the assigned USF is noted on one of the uplink PDCHs. If expired, the mobile station repeats the procedure for random access if there are no remaining TBFs. If it expires and there are one or more remaining TBFs the MS may reattempt the establishment of the corresponding uplink TBF. + +**T3182:** Wait for Acknowledgement + +This timer is used on the mobile station side to define when to stop waiting for temporary Packet Uplink Ack/Nack after the last RLC data block has been sent for the current send window or for the entire Temporary Block Flow. + +**T3184:** No Ack/Nack Received + +At exclusive allocation, this timer is used to detect a radio link failure condition. If expired, the mobile station performs an abnormal release with access retry. + +**T3186:** Supervision of the random access procedure + +This timer is used on the mobile station side to define the maximum allowed time to repeat the sending of all PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST messages. At expiry of timer T3186, the mobile station shall abort the packet access procedure. If at least one message was transmitted by the mobile station, it shall indicate a random access failure to upper layers and perform autonomous cell re-selection according to 3GPP TS 43.022; otherwise, it shall indicate a packet access failure to upper layers and return to packet idle mode or MAC-Idle state. + +**T3188:** This timer is used by a mobile station that supports multiple TBF procedures to define when to stop waiting for a MULTIPLE TBF UPLINK ASSIGNMENT message after sending a PACKET RESOURCE REQUEST message during a two-phase access that requests two or more uplink TBFs. + +**T3190:** Wait for Valid Downlink Data Received from the Network + +This timer is used on the mobile station side to stop waiting for the valid data from the network side either following the initial Packet Downlink Assignment/MBMS Assignment or after some previous downlink RLC data block. + +**T3192:** Wait for release of the TBF after reception of the final block + +This timer is used on the mobile station side when the mobile station has received all of the RLC data blocks. When timer T3192 expires the mobile station shall release the resources associated with the TBF (e.g. TFI) and begin to monitor its paging channel, except if the mobile station is in EC operation with timer T3168 running. + +**T3194:** Minimum time between stolen radio blocks for a given radio bearer. + +Following stealing a radio block for a given radio bearer, the mobile station shall expect to have this radio bearer scheduled via its USF within an interval defined by four times the duration of T3194, else link failure is reported to RRC. + +**T3196:** Wait for PACKET CS COMMAND message. + +This timer is used on the mobile station side to define when to stop waiting for the Packet CS COMMAND message. At expiry of timer T3196, the mobile station shall release all ongoing TBFs and start RR connection establishment as specified in 3GPP TS 44.018. + +**T3200:** RLC/MAC control message reassembly guard + +T3200 is used by the mobile station to control when it will discard segments of a partially received RLC/MAC control message. The mobile station shall have one instance of timer T3200 for each segmented RLC/MAC control message that the mobile station is capable of receiving in parallel. + +**T3204:** Wait for Packet Uplink Assignment after the first attempt to send a Packet Channel Request during a packet access procedure. The Packet Channel Request was attempted indicating 'Single block without TBF establishment' and the purpose of the packet access procedure is to send a PACKET PAUSE message. + +This timer is used by a mobile station with non-GSM capabilities to stop waiting for a PACKET UPLINK ASSIGNMENT message. At expiry of timer T3204, the Packet Pause procedure (sub-clause 7.6) is aborted. + +**T3206:** Wait for sending of the PACKET CELL CHANGE NOTIFICATION message after entering CCN mode + +This timer is used to control that the MS in CCN mode is not prevented to proceed with a cell re-selection for too long if it cannot send the PACKET CELL CHANGE NOTIFICATION message (e.g. T3192 is running and there is no uplink block granted to the MS). + +**T3208** Maximum delay of the MS initiated cell re-selection after the point in time when the MS has sent the PACKET CELL CHANGE NOTIFICATION message in CCN mode. + +T3208 is used by the mobile station in CCN mode to decide when to stop waiting for network assistance for the cell reselection (see sub-clause 5.5.1.1a). + +**T3210** Wait for retransmitting the PACKET CELL CHANGE NOTIFICATION message after having sent the PACKET CELL CHANGE NOTIFICATION message for the first time (see sub-clause 5.5.1.1a). + +This timer is used to request the mobile station to retransmit the PACKET CELL CHANGE NOTIFICATION message in the case it has not received any PACKET NEIGHBOUR CELL DATA message nor PACKET CELL CHANGE CONTINUE message nor PACKET CELL CHANGE ORDER message nor the PS HANDOVER COMMAND message in response to the sending of the PACKET CELL CHANGE NOTIFICATION message sent for the first time. It can reduce the cell re-selection delay implied by entering CCN mode in case the first PACKET CELL CHANGE NOTIFICATION message was not received by the network. + +**T3214** Wait for MBMS ASSIGNMENT message. + +This timer is used on the mobile station side to define when to stop waiting for the MBMS ASSIGNMENT message. At expiry of timer T3214, a mobile station in packet idle mode or MAC-Idle state shall return to DRX mode. A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode. + +**T3216** Wait for the PACKET PHYSICAL INFORMATION message. + +This timer is used on the mobile station side to define when to stop waiting for the PACKET PHYSICAL INFORMATION message in the non-synchronized cell PS handover case (see sub-clause 8.10.4.4). At expiry of timer T3216, the mobile station shall abort the PS handover procedure, return to the old cell, send a PACKET CELL CHANGE FAILURE message using the first available uplink transmission opportunity (if PS handover from *A/Gb mode* was attempted) and attempt to continue all TBFs/RABs that were ongoing prior to the reception of the PS HANDOVER COMMAND message/Handover from UTRAN Command message or *MobilityFromEUTRACommand* message (see sub-clause 8.10.5). + +**T3218** Wait for the first USF for any uplink TBF assigned to the MS after receiving the PS HANDOVER COMMAND message or Handover from UTRAN Command message or *MobilityFromEUTRACommand* message. + +This timer is used on the mobile station side to define when to stop waiting for a USF of any uplink TBF assigned to the MS in the new cell. + +At expiry of timer T3218, the mobile station shall abort the PS handover procedure, return to the old cell, send a PACKET CELL CHANGE FAILURE message using the first available uplink transmission opportunity (if PS handover from *A/Gb mode* was attempted) and attempt to continue all TBFs or RABs that were ongoing prior to the reception of the PS HANDOVER COMMAND message or Handover from UTRAN Command message or *MobilityFromEUTRACommand* message (see sub-clause 8.10.5). + +**T3220** Wait for PACKET PAGING REQUEST message. + +This timer is used to ensure that the mobile station stops waiting for a PACKET PAGING REQUEST message containing an MBMS notification part. At expiry of the T3220, the mobile station in packet idle mode or MAC-Idle state shall return to DRX mode unless it is already engaged in any other MBMS session and remaining in broadcast/multicast receive mode. + +### **T3222** + +An instance of the timer may be used during the notification of MBMS for mobile stations in packet transfer mode or in dual transfer mode. An instance of this timer may be started at the receipt of a PACKET MBMS ANNOUNCEMENT message when in packet transfer mode or in dual transfer mode. + +The instance of this timer is stopped either when the mobile station enters packet idle mode, if the PACKET MBMS ANNOUNCEMENT message included the Estimated Session Duration, or when the mobile station enters packet idle mode and completes the Transfer non-DRX mode period, if the PACKET MBMS ANNOUNCEMENT message included the Restriction Timer. + +At expiry of an instance of this timer, the mobile station discards the MBMS related information stored upon receipt of the corresponding PACKET MBMS ANNOUNCEMENT message. + +### **T3226** + +The timer is used to determine how long the mobile station may wait, after the last allocation in a fixed uplink allocation received in an uplink EC TBF, before starting to monitor the DL EC-PACCH for an RLC/MAC control message. + +At expiry the mobile station shall start timer T3228 and start monitoring the DL EC-PACCH for reception of an RLC/MAC control message. + +### **T3228** + +The timer is used to control the time period during which the mobile station shall monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, following a fixed uplink allocation. + +When the mobile station receives an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with its uplink TBF, it shall stop T3228. + +At expiry the mobile station shall release the ongoing uplink TBF and may perform an abnormal release with access retry, unless timer T3248 (sent in EC SI) is used. If T3248 is used, i.e. it has a timer value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH. The next higher DL Coverage Class shall then be used, if such exists. + +### **T3238** + +The timer is used to control the length of the period where the mobile station monitors the EC-PACCH of its uplink EC TBF after reception of the EC PACKET UPLINK ACK/NACK message with Final Ack Indicator set to '1', with an indication that the mobile station shall continue monitoring the EC-PACCH. The uplink EC TBF is then kept during this time interval. + +It is stopped at reception of an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station, or at reception of another RLC/MAC control message triggering the release of the uplink TBF. + +At expiry the mobile station shall leave the uplink TBF and return to packet idle mode. + +### **T3248** + +The timer is used to control the time period during which the mobile station shall monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, following a fixed uplink allocation. The next higher Coverage Class compared to the assigned DL CC shall then be used, if such exists. The timer is started at expiry of timer T3228. + +When the mobile station receives an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with its uplink TBF, it shall stop T3248. + +At expiry the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed. + +### **T3290** + +Wait for Downlink Data identified with the assigned MS\_ID during an MBMS radio bearer. + +This timer is used on the mobile station side to stop answering to polling during an MBMS radio bearer. + +T3290 has the same value as the one specified for T3190. + +### **T3230** + +The timer is used to control the validity period of the individual priorities. It is started on receipt of the individual priorities included in the PACKET CELL CHANGE ORDER or PACKET MEASUREMENT ORDER message for cell reselection or on inter-RAT reselection to GERAN if the corresponding timer in the source RAT (i.e, T320 in E-UTRA, T322 in UTRA) was running when reselection occurred. + +When one of the conditions specified in subclause 5.5.1.1c.3 is met, the MS shall stop T3230 and delete the corresponding individual priorities. + +At expiry the mobile station shall delete the corresponding individual priorities. + +### **T3232** + +The timer is used to control the length of the non-DRX mode period in which the mobile station is acquiring an ETWS Primary Notification message. It is started when receiving a PACKET PAGING REQUEST message on the PPCH carrying a segment of an ETWS Primary Notification message. + +It is stopped at reception of the complete ETWS Primary Notification message or upon initiating cell reselection or connection establishment procedures. + +At expiry the mobile station shall enter DRX mode. + +## 13.2 Timers on the network side + +For each timer, it is shown whether one timer instance is needed per MS, per TBF/MBMS radio bearer, per MS\_ID or per RLC/MAC control message. + +For EC-GSM-IoT, where blind physical layer transmissions are used, if a timer expires during an ongoing transmission opportunity, that transmission opportunity shall be considered as having occurred prior to the expiry of the timer. + +**Table 13.2.1: Specification of timers used in GPRS on the Network side** + +| timer | started | stopped | action at expiry | typical value | +|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------| +| T3169
(per TBF) | If counter N3101 = N3101_MAX, or if counter N3103 = N3103_MAX an instance of T3169 is started for this TBF | None | The network releases USF and TFI resources. | 5 s | +| T3191
(per TBF/ per RLC (NOTE 1)) | When the last RLC data block is sent with the FBI bit set to '1' an instance of T3191 is started for this TBF | When the final (EC) PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT is received

Restarted at the transmission of an RLC data block with the FBI bit set to '1'. | The network releases TFI resources. | 5 s | +| (per MBMS radio bearer) | When the PACKET TBF RELEASE message is sent | Restarted at the transmission of a further PACKET TBF RELEASE message | The network releases all the TFIs related to the MBMS radio bearer | | +| T3193
(per TBF/ per RLC (NOTE 1)) | When the final (EC) PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT is received an instance of T3193 is started for this TBF | Stopped when the network establishes a new downlink TBF using the same TFI value.

For an EC TBF, stopped when the network establishes a new downlink EC TBF or a new uplink EC TBF.

Restarted at the reception of the final (EC) PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT. | The network releases TFI resources. | Greater than T3192 | +| T3195
(per TBF) | If counter N3105 = N3105_MAX an instance of T3195 is started for this TBF | None | The network may reuse the TFI resources. | 5 s | +| (per MS_ID on an MBMS radio bearer) | If counter N3105 = N3105_MBMS_MAX an instance of T3195 is started | | The network may reuse the MS_ID on the corresponding MBMS radio bearer. | | +| T3197 | When PACKET CS RELEASE INDICATION message is transmitted. | On receipt of PACKET SI STATUS or PACKET PSI STATUS message indicating that the mobile station has received system information to maintain its radio resources after the release of the RR connection. | The network shall send CHANNEL RELEASE message (specified in 3GPP TS 44.018) to the mobile station. | 2 s | +| T3199
(per MS_ID on an MBMS radio bearer) | If counter N3109 = N3109_MAX an instance of T3199 is started for this MS_ID.

At the point in time denoted by the Current MS_ID Expiry Time while no PACKET CONTROL ACKNOWLEDGEMENT message has been received, an instance of T3199 is started for this MS_ID. | None | The network releases the MS_ID on the corresponding MBMS radio bearer. | 5 s | + +| | | | | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| T3227 | After the last allocated RLC data block of a fixed uplink allocation. In case more than one blind physical layer transmission is used on the uplink EC-PDTCH, the timer shall be started after the last of those transmissions. | None | Timer T3229 is started and the network may transmit DL RLC/MAC control messages to the mobile station on the EC-PACCH. | Same as T3226 | +| T3229 | At expiry of timer T3227. | On receipt of uplink data on the resources that are part of the fixed uplink allocation, which were allocated in an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message sent to the mobile station while timer T3229 was running. | If timer T3249 is not used, i.e. it has the value = 0, the network may release the TBF and reuse the TFI resource if no uplink data is received in fixed uplink allocations, which were allocated in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages sent to the mobile station before expiry of timer T3229.
If timer T3249 is used, i.e. it has a value > 0, the network shall start timer T3249 and use the next higher CC, if such exists, on the DL EC-PACCH, as long as T3249 is running. | Same as T3228 | +| T3237 | The timer shall be (re)started at transmission of an EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1' and indicating that the mobile station shall continue monitoring the EC-PACCH | None | The network may release the TBF and reuse the TFI resource. | 6 s | +| T3249 | At expiry of timer T3229. | On receipt of uplink data on the resources that are part of the fixed uplink allocation, which were allocated in an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message sent to the mobile station while timer T3249 (or preceding T3229) was running. | The network may release the TBF and reuse the TFI resource if no uplink data is received in fixed uplink allocations, which were allocated in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages sent to the mobile station before expiry of timer T3249 (or preceding T3229). | Same as T3248 | + +NOTE 1: Timer per RLC entity if EMST is used. + +**T3169:** Wait for Reuse of USF and TFI(s) after the mobile station uplink assignment for this TBF is invalid + +This timer is used on the network side to define when the current uplink assignment for this TBF is surely invalid on the mobile station side so that the assigned USF(s) and TFI can be reused on the uplink. During that period the corresponding USF(s) is not broadcast. + +Its value is network dependent. The value of T3169 should be greater than T3180, T3182 and (for exclusive allocation) T3184. + +**T3191:** Wait for reuse of TFI(s) after sending of the last RLC Data Block on this TBF. Wait for reuse of TFI(s) after sending the PACKET TBF RELEASE for an MBMS radio bearer. + +This timer is used on the network side to define when the current assignment for this TBF/MBMS is surely invalid on the mobile station side so that the TFI(s) can be reused. + +Its value is network dependent. + +**T3193:** Wait for reuse of TFI(s) after reception of the final (EC) PACKET DOWNLINK ACK/NACK from the mobile station for this TBF. + +This timer is used on the network side to define when timer T3192 on the mobile station side has surely expired so that the TFI can be reused. + +Its value is network dependent. + +**T3195:** Wait for reuse of TFI(s) when there is no response from the MS (radio failure or cell change) for this TBF/MBMS radio bearer. + +This timer is used on the network side to define when the current assignment for this TBF/MS\_ID on an MBMS radio bearer is surely invalid on the mobile station side so that the TFI can be reused. + +Its value is network dependent. + +**T3197:** Wait for the indication from the mobile station that it has received needed system information messages. + +This timer is used on the network side to delay the release of RR connection release in order to maintain radio resources before the mobile station has indicated the receipt of system information messages specified in sub-clause 5.5.1.2 or 5.5.1.3. + +**T3199:** Wait for reuse of MS\_ID on an MBMS radio bearer. + +This timer is used on the network side to define for a given MBMS radio bearer when a(n) (re)assigned MS\_ID is surely invalid on the mobile station side so that this MS\_ID can be reused. During that period the corresponding MS\_ID is not used. + +Its value is network dependent. + +**T3227:** Wait for mobile station to be reachable on the DL EC-PACCH. + +This timer is used on the network side to determine when the mobile station can be reached on the DL EC-PACCH following a fixed uplink allocation. The mobile station is not reachable while the timer is running. When the timer expires, timer T3229 is started and the network may transmit RLC/MAC control messages to the mobile station on the DL EC-PACCH. + +Its value is network dependent. + +**T3229:** This timer is used on the network side to determine how long the mobile station is reachable on the DL EC-PACCH following a fixed uplink allocation and the corresponding expiry of timer T3227. When the timer expires, the mobile station is no longer reachable on the DL EC-PACCH based on the corresponding fixed uplink allocation, unless timer T3249 is used, i.e. it has a timer value > 0. At transmission of an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, containing a new fixed uplink allocation, to the mobile station while timer T3229 is running, timers T3227 and T3229 will be started following that fixed uplink allocation. + +Its value is network dependent. + +**T3237:** Wait for reuse of the TFI for the uplink EC TBF. + +This timer is used on the network side to control the length of the period where the mobile station monitors the EC-PACCH of the uplink EC TBF after transmission of the EC PACKET UPLINK ACK/NACK message with Final Ack Indicator set to '1' and with an indication that the mobile station shall continue monitoring the EC-PACCH. The uplink EC TBF shall be kept during this time interval. + +Its value is network dependent. + +**T3249:** This timer is used on the network side to determine how long the mobile station is reachable on the DL EC-PACCH after expiry of timer T3229. The mobile station is then reachable using the next higher DL Coverage Class, compared to the assigned one, if such exists. When the timer expires, the mobile station is no longer reachable on the DL EC-PACCH based on the corresponding fixed uplink allocation. + +Its value is network dependent. + +## 13.3 Counters on the Mobile Station side + +**N3102** At each cell reselection the mobile station shall set the counter N3102 to the value defined by the optional broadcast parameter PAN\_MAX. Whenever the mobile station receives a Packet Ack/Nack that allows the advancement of V(S), the mobile station shall increment N3102 by the broadcast value PAN\_INC, however N3102 shall never exceed the value PAN\_MAX. Each time T3182 expires the mobile station shall decrement N3102 by the broadcast value PAN\_DEC. When $N3102 \leq 0$ is reached, the mobile station shall perform an abnormal release with cell re-selection. + +**N3104** When the mobile station sends the first RLC/MAC block the counter N3104 shall be initialized to 1. For each new RLC/MAC block the mobile station sends it shall increment N3104 by 1 until the first correct PACKET UPLINK ACK/NACK message is received. Then N3104 shall not be further incremented. If the N3104 counter is equal to N3104\_MAX and no correct PACKET UPLINK ACK/NACK message has been received, the contention resolution fails and the mobile station behaves as specified in sub-clause 7.1.2.3. + +N3104\_MAX shall have the value: + +$$N3104\_MAX = 3 * (BS\_CV\_MAX + 3) * \text{number of uplink timeslots assigned.}$$ + +**N3106** N3106 is used in *Iu mode* on the mobile station side to detect link failures that may occur for a given uplink RLC entity and shall be reported to the RRC layer. It is incremented each time a response to a given request is not received before a specified response time. It is reset upon reception of a response within the response time requirements. If the counter N3106 is equal to N3106max, a link failure has occurred that shall be reported to the RRC layer. There is one N3106 instance per uplink RLC entity in TCH or DCCH TBF mode. + +N3106max shall have the value: 5. + +## 13.4 Counters on the Network side + +**N3101:** When the network after setting USF for a given TBF, receives a valid data block of this TBF from the mobile station in a block assigned for this USF, it will reset counter N3101. If PS Handover is not ongoing, the network will increment counter N3101 for each USF for which no data is received for this TBF. N3101max shall be greater than 8. If $N3101 = N3101max$ , the network shall stop the scheduling of RLC/MAC blocks from the mobile station for this USF and start timer T3169. + +During extended uplink TBF mode, counter N3101 shall not be incremented if the network does not require a mobile station to send PACKET UPLINK DUMMY CONTROL BLOCK messages when there is no other RLC/MAC block ready to send for this TBF in uplink radio blocks allocated by the network (see sub-clause 9.3.1b.2). + +The use of N3101 during PS Handover is implementation specific. + +**N3103:** N3103 is reset when transmitting the final (EC) PACKET UPLINK ACK/NACK message within a TBF (final ack indicator set to 1). If the network does not receive the (EC) PACKET CONTROL ACKNOWLEDGEMENT message in the scheduled block for this TBF, it shall increment counter N3103 and retransmit the (EC) PACKET UPLINK ACK/NACK message. If counter N3103 exceeds its limit, the network shall start timer T3169. + +**N3105:** When the network after sending a RRBP field in the downlink RLC data block or in *Iu mode* also RLC/MAC control block, receives a valid RLC/MAC control message from the mobile station, it will reset counter N3105. The network will increment counter N3105 for each allocated data block + +for which no RLC/MAC control message is received for this TBF. The value of N3105max is network dependent. + +During an MBMS data transfer, whenever the network receives a valid RLC/MAC control message from a mobile station identified by a given MS\_ID value, it shall reset the counter N3105 for that MS\_ID. The network shall increment the counter N3105 for a given MS\_ID for each radio block, allocated via the polling procedure to the mobile station identified by that MS\_ID value, for which no RLC/MAC control message is received. The value of N3105\_MBMS\_MAX is network dependent + +**N3107** N3107 is used in *Iu mode* on the network side to detect link failures that may occur for a given RLC entity and that shall be reported to the RRC layer. It is incremented each time a response to a given request is not received before a specified response time. It is reset upon reception of a response within the response time requirements. If the counter N3107 is equal to N3107max, a link failure has occurred that shall be reported to the RRC layer. There is one N3107 instance per downlink RLC entity in TCH or DCCH TBF mode. The value of N3107max is network dependent. + +**N3109:** N3109 for a given MS\_ID on an MBMS radio bearer is reset when transmitting for the first time the MBMS MS\_ID ASSIGNMENT message including a polling request. If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the scheduled block, it shall increment counter N3109 for that MS\_ID and may retransmit the MBMS MS\_ID ASSIGNMENT message. If counter N3109 = N3109\_MAX, the network shall start timer T3199 for that MS\_ID. The value of N3109\_MAX is network dependent. + +# --- Annex A (informative): Bibliography + +- 1) ITU-T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN". +- 2) ITU-T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities". +- 3) ISO/IEC 8886: "Information technology - Open Systems Interconnection - Data link service definition". +- 4) ISO/IEC 10022: "Information technology - Open Systems Interconnection - Physical Service Definition". +- 5) ISO/IEC 10039: "Information technology - Open Systems Interconnection - Local area networks - Medium Access Control (MAC) service definition". +- 6) ISO/IEC 4335: "Information technology - Telecommunications and information exchange between systems - High-level data link control (HDLC) procedures - Elements of procedures". +- 7) ISO/IEC 7478: "Information processing systems - Data communication - Multilink procedures". +- 8) ISO/IEC 7498: "Information technology - Open Systems Interconnection - Basic Reference Model". + +# Annex B (informative): RLC data block encoding + +## B.1 Example 1 + +Figure B.1 provides an example of the use of the Length indicator in conjunction with the M and E bits. In the example, LLC PDU 1 continues from a previous RLC data block and ends in the RLC data block shown. LLC PDU 2 follows LLC PDU 1 and is completely contained within the RLC data block. LLC PDU 3 follows LLC PDU 2, beginning in the RLC data block shown, and continues into the next RLC data block. + +![Diagram of RLC data block encoding showing header fields and LLC PDUs (1, 2, 3) mapped to MAC octets.](06faefab7f20d05bf410e9a250268f64_img.jpg) + +The diagram illustrates the mapping of RLC data blocks to MAC layers. The RLC header is 8 bits wide, with bit 8 as Payload Type, bits 7-5 as RRBP, bit 4 as S/P, and bits 3-1 as USF. The header structure includes PR, TFI, FBI, BSN, and Length indicator fields. The Length indicator is shown for two cases: one where the indicator is 11 (M=1, E=0) and another where it is 26 (M=1, E=1). The LLC PDUs are mapped to MAC octets as follows: LLC PDU 1 (cont) from Octet 3 to Octet 15; LLC PDU 2 from Octet 16 to Octet 41; LLC PDU 3 from Octet 42 to Octet N. + +| Bit | | | | | | | | | | +|-----------------------|------|---|---|-----|-----|---|-------|------------|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| Payload Type | RRBP | | | S/P | USF | | | MAC header | | +| PR | TFI | | | | | | FBI | Octet 1 | | +| BSN | | | | | | | E = 0 | Octet 2 | | +| Length indicator = 11 | | | | | | | M = 1 | E = 0 | Octet 3 | +| Length indicator = 26 | | | | | | | M = 1 | E = 1 | Octet 4 | +| LLC PDU 1 (cont) | | | | | | | | Octet 5 | LLC PDU 1 | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet 15 | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet 16 | | +| | | | | | | | | Octet 17 | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| LLC PDU 2 | | | | | | | | Octet 41 | LLC PDU 2 | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet 42 | | +| | | | | | | | | Octet 43 | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet N-1 | | +| | | | | | | | | Octet N | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| LLC PDU 3 | | | | | | | | | LLC PDU 3 | +| | | | | | | | | | | + +Diagram of RLC data block encoding showing header fields and LLC PDUs (1, 2, 3) mapped to MAC octets. + +Figure B.1: Length indicator (LI) example + +## B.2 Example 2 + +Figure B.2 provides an example of the use of the Length indicator when the end of an LLC PDU would fit within an RLC data block but the addition of the length indicator octet (to indicate the LLC PDU boundary) causes the LLC PDU to extend into another RLC data block. In the example, LLC PDU 1 continues from a previous RLC data block and has 20 remaining octets. The first 19 octets are placed into RLC data block N, the Length Indicator is set to 0 (to indicate that the LLC PDU does not end within the current RLC data block), and the 20th octet is placed in RLC data block N+1. + +![Diagram showing the structure of RLC data blocks N and N+1. RLC data block N contains the MAC header (bits 8-1) and the first 19 octets of LLC PDU 1. The Length Indicator is set to 0. RLC data block N+1 contains the MAC header (bits 8-1), an optional Octet 3 (Length Indicator = 1, M=1, E=1), Octet 4, and the remaining octets of LLC PDU 1 (Octets 20-22) followed by LLC PDU 2. The diagram includes bit positions (8-1) and field names like Payload Type, RRBP, S/P, USF, PR, TFI, FBI, BSN, and Length indicator.](af01656e21a42c1d856cfb21185cd50e_img.jpg) + +**RLC data block N** + +| bit | | | | | | | | +|----------------------|------|---|-----|-----|-------|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | RRBP | | S/P | USF | | | | +| PR | TFI | | | | | | FBI | +| BSN | | | | | | | E = 0 | +| Length indicator = 0 | | | | | M = 0 | E = 1 | | +| LLC PDU 1 (cont) | | | | | | | | + +MAC header +Octet 1 +Octet 2 +Octet 3 +Octet 4 +. +. +Octet 22 +LLC PDU 1 + +**RLC data block N + 1** + +| bit | | | | | | | | +|----------------------|------|---|-----|-----|-------|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | RRBP | | S/P | USF | | | | +| TFI | | | | | | | FBI | +| BSN | | | | | | | E = 0 | +| Length indicator = 1 | | | | | M = 1 | E = 1 | | +| LLC PDU 1 (cont) | | | | | | | | +| LLC PDU 2 | | | | | | | | + +MAC header +Octet 1 +Octet 2 +Octet 3 (optional) +Octet 4 +. +. +Octet 22 +LLC PDU 2 + +Diagram showing the structure of RLC data blocks N and N+1. RLC data block N contains the MAC header (bits 8-1) and the first 19 octets of LLC PDU 1. The Length Indicator is set to 0. RLC data block N+1 contains the MAC header (bits 8-1), an optional Octet 3 (Length Indicator = 1, M=1, E=1), Octet 4, and the remaining octets of LLC PDU 1 (Octets 20-22) followed by LLC PDU 2. The diagram includes bit positions (8-1) and field names like Payload Type, RRBP, S/P, USF, PR, TFI, FBI, BSN, and Length indicator. + +Figure B.2: Length indicator (LI) example + +## B.3 Example 3 + +Figure B.3 provides an example of the use of the Length indicator when the end of an LLC PDU fits precisely into an RLC data block. In the example, LLC PDU 1 continues from a previous RLC data block and ends in the RLC data block shown. LLC PDU 2 follows LLC PDU 1 and fills precisely the RLC data block shown. + +![Diagram showing the structure of an RLC data block. The MAC header (bits 8-1) and the remaining octets of LLC PDU 1 (Octets 1-2) are shown. The Length Indicator is not present as the PDU ends precisely. LLC PDU 2 follows LLC PDU 1 and fills the rest of the block.](b1bb7109befc781cd95cf07248ad4b57_img.jpg) + +**Bit** + +| Bit | | | | | | | | +|--------------|------|---|-----|-----|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | RRBP | | S/P | USF | | | | +| PR | TFI | | | | | | FBI | +| BSN | | | | | | | E = 0 | + +MAC header +Octet 1 +Octet 2 +LLC PDU 1 + +Diagram showing the structure of an RLC data block. The MAC header (bits 8-1) and the remaining octets of LLC PDU 1 (Octets 1-2) are shown. The Length Indicator is not present as the PDU ends precisely. LLC PDU 2 follows LLC PDU 1 and fills the rest of the block. + +Error: +Reference + +274 + +Error: Reference source not +found + +![](9e47aa7528e713ae12a7739999286108_img.jpg) + +| | | | +|-----------------------|-------|-------| +| Length indicator = 7 | M = 1 | E = 0 | +| Length indicator = 11 | M = 0 | E = 1 | +| LLC PDU 1 (cont) | | | +| LLC PDU 2 | | | + +Octet 3 +Octet 4 +Octet 5 +. +. +Octet 11 +Octet 12 +. +. +Octet 22 + +| | +|-----------| +| | +| LLC PDU 2 | + +Figure B.3: Length indicator (LI) example + +## B.4 Example 4 + +Figure B.4 provides an example when the Length indicator is not used. As the example does not contain any LLC frame boundaries, no Length Indicator octets are needed. 20 octets is used for LLC data in each RLC data block. + +![Diagram showing two RLC data blocks (N and N+1) with their internal structure. Each block has a MAC header (bits 8-1) and a payload (LLC PDU 1). The MAC header includes Payload Type, RRBP, S/P, USF, PR, TFI, BSN, FBI, and E=1. The payload is 20 octets long (Octets 3-22).](dda72b6afeac47479e0746d4eaf6745a_img.jpg) + +**RLC data block N** + +| | | | | | | | | +|------------------|------|---|-----|-----|---|---|-------| +| bit | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | RRBP | | S/P | USF | | | | +| PR | TFI | | | | | | FBI | +| BSN | | | | | | | E = 1 | +| LLC PDU 1 (cont) | | | | | | | | + +MAC header + +Octet 1 + +Octet 2 + +Octet 3 + +. + +. + +. + +Octet 22 + +LLC PDU 1 + + + +**RLC data block N + 1** + +| | | | | | | | | +|------------------|------|---|-----|-----|---|-----|-------| +| bit | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | RRBP | | S/P | USF | | | | +| TFI | | | | | | FBI | | +| BSN | | | | | | | E = 1 | +| LLC PDU 1 (cont) | | | | | | | | + +MAC header + +Octet 1 + +Octet 2 + +Octet 3 + +. + +. + +. + +Octet 22 + +LLC PDU 1 + +Diagram showing two RLC data blocks (N and N+1) with their internal structure. Each block has a MAC header (bits 8-1) and a payload (LLC PDU 1). The MAC header includes Payload Type, RRBP, S/P, USF, PR, TFI, BSN, FBI, and E=1. The payload is 20 octets long (Octets 3-22). + +Figure B.4: Example when Length indicator (LI) can be omitted + +## B.5 Example 5 + +Figure B.5 provides an example when the final LLC PDU (FBI=1) of a *downlink* TBF fills the RLC data block precisely in which case the Length indicator can be omitted. In the example, LLC PDU 1 continues from a previous RLC data block and ends in and fills precisely the RLC data block shown. + +![Diagram of RLC MAC header and LLC PDU 1 for downlink. The header is 8 bits: Payload Type (PR), RRBP, S/P, and USF. Subsequent octets contain TFI, FBI=1, BSN, and E=1. The data portion is labeled LLC PDU 1 (cont) and spans from Octet 3 to Octet 22.](f609bd3fda53d5be094991a96addbf84_img.jpg) + +| | | | | | | | | +|------------------|------|---|-----|-----|---|---|-------| +| Bit | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | RRBP | | S/P | USF | | | | +| PR | TFI | | | | | | FBI=1 | +| BSN | | | | | | | E = 1 | +| LLC PDU 1 (cont) | | | | | | | | + +MAC header + +Octet 1 + +Octet 2 + +Octet 3 + +Octet 4 + +⋮ + +Octet 22 + +LLC PDU 1 + +Diagram of RLC MAC header and LLC PDU 1 for downlink. The header is 8 bits: Payload Type (PR), RRBP, S/P, and USF. Subsequent octets contain TFI, FBI=1, BSN, and E=1. The data portion is labeled LLC PDU 1 (cont) and spans from Octet 3 to Octet 22. + +Figure B.5: Example when Length indicator (LI) can be omitted + +## B.6 Example 6 + +Figure B.6 provides an example when the final LLC PDU (CV=0) of an *uplink* TBF fills the RLC data block precisely in which case the Length indicator can be omitted. In the example, LLC PDU 1 continues from a previous RLC data block and ends in and fills precisely the RLC data block shown. + +![Diagram of RLC MAC header and LLC PDU 1 for uplink. The header is 8 bits: Payload Type (spare), Countdown value = 0, SI, and R. Subsequent octets contain TFI, R, BSN, and E=1. The data portion is labeled LLC PDU 1 (cont) and spans from Octet 3 to Octet 22.](4e0a625d1c8db7dab805bf443c880129_img.jpg) + +| | | | | | | | | +|------------------|---------------------|---|---|----|---|---|-------| +| Bit | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | Countdown value = 0 | | | SI | R | | | +| spare | TFI | | | | | | TI | +| BSN | | | | | | | E = 1 | +| LLC PDU 1 (cont) | | | | | | | | + +MAC header + +Octet 1 + +Octet 2 + +Octet 3 + +Octet 4 + +⋮ + +Octet 22 + +LLC PDU 1 + +Diagram of RLC MAC header and LLC PDU 1 for uplink. The header is 8 bits: Payload Type (spare), Countdown value = 0, SI, and R. Subsequent octets contain TFI, R, BSN, and E=1. The data portion is labeled LLC PDU 1 (cont) and spans from Octet 3 to Octet 22. + +Figure B.6: Example when Length indicator (LI) can be omitted + +## B.7 Example 7 + +Figure B.7 provides an example when the Length indicator can be omitted. As the LLC PDU 1 begins in the RLC data block N and continues to the next one, no Length octet is needed. + +![](2d701e1404ebacb18f0b58713fe7d894_img.jpg) + +RLC data block N + +Bit + +| | | | | | | | | +|--------------|---|-----------------|---|---|---|----|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | | Countdown value | | | | SI | R | +| spare | | TFI | | | | | TI | +| BSN | | | | | | | E = 1 | +| LLC PDU 1 | | | | | | | | + + + +RLC data block N+1 + +Bit + +| | | | | | | | | +|------------------|---|-----------------|---|---|---|-----|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Payload Type | | Countdown value | | | | SI | R | +| spare | | TFI | | | | | TI | +| BSN | | | | | | | E = 0 | +| LI=10 | | | | | | M=1 | E=1 | +| LLC PDU 1 (cont) | | | | | | | | +| LLC PDU 2 | | | | | | | | + +--- + +MAC header + +Octet 1 + +Octet 2 + +Octet 3 + +Octet 4 + +. + +. + +. + +. + +Octet 22 + + + + +MAC header + +Octet 1 + +Octet 2 + +Octet 3 + +Octet 4 + +. + +Octet 13 + +. + +. + +Octet 22 + +LLC PDU 1 + +LLC PDU 2 + +**Figure B.7: Example when Length indicator (LI) can be omitted** + +## B.8 RLC data block delimitation for EGPRS + +### B.8.1 Example 1 + +Figure B.8 shows the first 2 RLC blocks of a TBF (Down-link). Only the last segment of a LLC PDU requires a length indicator. + +![](d09fda6826ea374ed615c22c3805dd94_img.jpg) + +1st RLC Block +LLC PDU + +Bit + +| | | | | | | | | | | +|-----------------------|---|---|---|---|---|-------|-------|----------|------------------------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| | | | | | | FBI=0 | E = 0 | | | +| Length indicator = 11 | | | | | | E = 0 | | Octet 1 | | +| Length indicator = 26 | | | | | | E = 1 | | Octet 2 | | +| LLC PDU 1 (cont) | | | | | | | | Octet 3 | LLC PDU 1
1 st PDU of the
TBF | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet 13 | | +| | | | | | | | | . | | +| | | | | | | | | Octet 14 | | +| | | | | | | | | Octet 15 | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet 39 | | +| LLC PDU 2 | | | | | | | | Octet 40 | LLC PDU 2 | +| | | | | | | | | Octet 41 | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet N2 | | +| LLC PDU 3 | | | | | | | | | LLC PDU 3 | +| | | | | | | | | | | +| | | | | | | | | | | + +2nd RLC block of the TBF + +Bit + +| | | | | | | | | | | +|-----------------------|---|---|---|---|---|-------|-------|----------|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| | | | | | | FBI=0 | E = 0 | | | +| Length indicator = 11 | | | | | | E = 0 | | Octet 1 | LLC PDU 3 | +| Length indicator = 26 | | | | | | E = 1 | | Octet 2 | | +| LLC PDU 3 (cont) | | | | | | | | Octet 3 | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet 13 | | +| | | | | | | | | | | + +![Diagram showing LLC PDUs spanning multiple RLC data blocks. LLC PDU 4 spans Octets 14-39, and LLC PDU 5 spans Octets 40 to N2.](e04a952ad587547899d15c77183a5b24_img.jpg) + +| | | | +|-----------|------------|-----------| +| LLC PDU 4 | Octet 14 | LLC PDU 4 | +| | Octet 15 | | +| LLC PDU 5 | ⋮ | LLC PDU 5 | +| | Octet 39 | | +| | Octet 40 | | +| | Octet 41 | | +| | ⋮ | | +| | Octet N2-1 | | +| | Octet N2 | | + +Diagram showing LLC PDUs spanning multiple RLC data blocks. LLC PDU 4 spans Octets 14-39, and LLC PDU 5 spans Octets 40 to N2. + +Figure B.8: Example for the case when a LLC PDU stretches over more than 2 consecutive in sequence RLC data blocks (LLC PDU 3 and LLC PDU 5). + +### B.8.2 Example 2 + +Figure B.9 shows the last 3 RLC blocks of a TBF consisting of N blocks (Downlink). When an LLC PDU fills an RLC data block precisely and adding an LI for it would push the LLC PDU into the next in sequence RLC data block, then the LLC PDU is present in this RLC data block without a corresponding length indicator. If this LLC PDU is not the last LLC PDU of the TBF, its delimitation is indicated by the first length indicator of the next in sequence RLC data block with value LI=0. In case when the LLC PDU, or the last segment of it, does not fill the RLC data block, a length indicator with value 127 is added as the last length indicator of the RLC data block. + +![Diagram of RLC Block with BSN=N-2 (mod SNS) showing LLC PDUs J+1 and J+2 across multiple octets with length indicators.](72445157c2c2b35e98cdc0d5b513f74b_img.jpg) + +RLC Block with BSN=N-2 (mod SNS) + +| Bit | | | | | | | | +|--------------------------|---|---|---|---|---|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| | | | | | | FBI=0 | E = 0 | +| Length indicator = N2-13 | | | | | | E = 1 | | +| LLC PDU J+1 (continue) | | | | | | | | +| LLC PDU J+2 | | | | | | | | + +Octet 1 +Octet 2 +Octet 3 +⋮ +Octet N2-11 +Octet N2-10 +⋮ +Octet N2 + +LLC PDU J+1 +LLC PDU J+2 + +Diagram of RLC Block with BSN=N-2 (mod SNS) showing LLC PDUs J+1 and J+2 across multiple octets with length indicators. + +#### RLC Block with BSN=N-1 (mod SNS) + +![](890973c123723e95fafd25e725668b4a_img.jpg) + +Bit + +8       7       6       5       4       3       2       1 + +| | | | | | | | | | +|--------------------------|--|--|--|--|--|-------|-------|----------| +| | | | | | | FBI=0 | E = 0 | Octet 1 | +| Length indicator = 0 | | | | | | | E = 0 | Octet 2 | +| Length indicator = 7 | | | | | | | E = 0 | Octet 3 | +| Length indicator = N2-11 | | | | | | | E = 1 | Octet 4 | +| LLC PDU J+3 | | | | | | | | Octet 5 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet 11 | +| LLC PDU J+4 | | | | | | | | Octet 12 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet N2 | + +LLC PDU J+3 + +LLC PDU J+4 + +#### RLC Block with BSN=N (mod SNS) + +![](b6783b3a83a0ade1dd26a3f176399cc2_img.jpg) + +Bit + +8       7       6       5       4       3       2       1 + +| | | | | | | | | | +|----------------------|--|--|--|--|--|-------|-----|----------| +| | | | | | | FBI=1 | E=0 | Octet 1 | +| Length indicator=6 | | | | | | | E=0 | Octet 2 | +| Length indicator=12 | | | | | | | E=0 | Octet 3 | +| Length indicator=127 | | | | | | | E=1 | Octet 4 | +| LLC PDU J+5 | | | | | | | | Octet 5 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet 10 | +| LLC PDU J+6 | | | | | | | | Octet 11 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet 22 | +| Filling Octets | | | | | | | | Octet N2 | + +LLC PDU J+5 + +LLC PDU J+6 + +**Figure B.9: Example for the case when the LLC PDU fills exactly the RLC data block (LLC PDU J+2 and LLC PDU J+4) and when the last LLC PDU cannot not fill the last RLC data block(LLC PDU J+6)** + +### B.8.3 Example 3 + +Figure B.10 shows a TBF of one LLC PDU which fills exactly the RLC data block (Downlink). + +![Diagram of an RLC data block structure showing 8 bits, FBI=1, E=1, and LLC PDU 1 across multiple octets.](a48ecbf3100ebf31b5d615267fa263c3_img.jpg) + +The diagram illustrates the structure of an RLC data block. At the top, a header is shown with 8 bits (labeled 8 to 1). Bit 2 is labeled FBI=1 and bit 1 is labeled E=1. Below the header, the data portion is labeled LLC PDU 1. To the right of the data portion, the octets are listed: Octet 1, Octet 2, ..., Octet N2. A box on the far right contains the text LLC PDU 1, indicating the data payload. + +| | | | | | | | | | | | | | | | | | | +|-----------|--|--|--|--|--|--|--|---|---|---|---|-------|-------|---|---|--|--| +| | | | | | | | | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| | | | | | | | | | | | | FBI=1 | E = 1 | | | | | +| LLC PDU 1 | | | | | | | | | | | | | | | | | | + +Octet 1 +Octet 2 +. +. +Octet N2 + +LLC PDU 1 + +Diagram of an RLC data block structure showing 8 bits, FBI=1, E=1, and LLC PDU 1 across multiple octets. + +Figure B.10: Example for the case when a LLC PDU fills the RLC data block precisely. + +### B.8.4 Example 4 + +Figure B.11 shows 2 RLC blocks of a TBF during RLC non-persistent mode of operation. When an LLC PDU ends in the previous RLC data block, a length indicator with value=126 is added in the next in sequence RLC data block to indicate the start of the next LLC PDU. + +![](ba532d6e6b5002f33ff2c93a98ee3d5f_img.jpg) + +RLC Block with BSN=N (mod SNS) + +| Bit | | | | | | | | +|-----------------------|---|---|---|---|---|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| | | | | | | FBI=0 | E = 0 | +| Length indicator= 7 | | | | | | | E =0 | +| Length indicator= 12 | | | | | | | E =0 | +| Length indicator= 127 | | | | | | | E=1 | +| LLC PDU J | | | | | | | | +| LLC PDU J+1 | | | | | | | | +| Filling Octets | | | | | | | | + +Octet 1 + +Octet 2 + +Octet 3 + +Octet 4 + +Octet 5 + +. . + +Octet 11 + +Octet 12 + +. . + +Octet 23 + +Octet 24 + +. . + +Octet N2 + +LLC PDU J + +LLC PDU J+1 + + + +RLC Block with BSN=N+1 (mod SNS) + +| Bit | | | | | | | | +|----------------------|---|---|---|---|---|-------|-----| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| | | | | | | FBI=0 | E=0 | +| Length indicator=126 | | | | | | | E=0 | +| Length indicator=19 | | | | | | | E=0 | +| Length indicator=127 | | | | | | | E=1 | +| LLC PDU J+2 | | | | | | | | +| Filling Octets | | | | | | | | + +Octet 1 + +Octet 2 + +Octet 3 + +Octet 4 + +Octet 5 + +. . + +Octet 23 + +. . + +Octet N2 + +LLC PDU J+2 + +**Figure B.11: Example for the case when the LLC PDU J+1 ends in the previous RLC data block and the start of the next LLC PDU J+2 is in the next RLC data block which is indicated using LI=126 as the first LI in that RLC data block.** + +# Annex C (informative): Message Sequence Diagrams + +The following figures illustrate message sequences for: + +- one phase mobile originated access (figure C.1); and +- network originated access (figure C.2). + +![Sequence diagram for one phase packet access between Mobile Station and Network.](1f1e9d5f20165c68490ae895ad73d5a7_img.jpg) + +``` + +sequenceDiagram + participant MS as Mobile Station + participant NW as Network + Note left of MS: Start T3186/T3170 * + MS->>NW: PACKET CHANNEL REQUEST + NW-->>MS: PACKET QUEUING NOTIFICATION + Note left of MS: Stop T3186/T3170, +Start T3162 + NW-->>MS: PACKET POLLING * + MS->>NW: PACKET CONTROL ACK * + NW-->>MS: PACKET UPLINK ASSIGNMENT + Note left of MS: Stop T3170/T3162/T3186, +Start T3164 + Note right of NW: Start N3101 + NW-->>MS: RLC/MAC block (USF) + Note left of MS: Stop T3164 + Note right of NW: Stop N3101 + Note left of MS: Start T3166 + MS->>NW: RLC/MAC data block (TLLI) + NW-->>MS: PACKET UPLINK ACK/NACK (TLLI) + Note left of MS: Stop T3166 + +``` + +\* Optional + +Sequence diagram for one phase packet access between Mobile Station and Network. + +**Figure C.1: Message Sequence Diagram for one phase packet access** + +![Sequence diagram for TBF establishment initiated by the network.](cd30974768c51b92c072e609be79501b_img.jpg) + +``` + +sequenceDiagram + participant MS as Mobile Station + participant NW as Network + Note left of MS: Start T3190 + NW-->>MS: PACKET DOWNLINK ASSIGNMENT + Note left of MS: Restart T3190 + NW-->>MS: RLC/MAC data block (TFI) + +``` + +Sequence diagram for TBF establishment initiated by the network. + +**Figure C.2: TBF establishment initiated by the network** + +# --- Annex D (informative): (void) + +# --- Annex E (informative): (void) + +# --- Annex F (informative): Examples of Countdown procedure operation + +This annex presents several examples of the countdown procedure operation. + +The following parameters are used in the following examples: + +TBC = total number of RLC data blocks that will be transmitted in the TBF; + +BSN' = absolute block sequence number of the RLC data block, with range from 0 to (TBC - 1); + +NTS = number of timeslots assigned to the uplink TBF in the assignment message, with range 1 to 8. + +## F.1 Example 1 + +In this example, shown in the first column, the total number of RLC data blocks in the TBF (TBC) is 155, the number of timeslots (NTS) is 1, and BS\_CV\_MAX is 15. The second column shows the same example with BS\_CV\_MAX = 6. + +| | | +|-----------|-----| +| TBC | 155 | +| NTS | 1 | +| BS_CV_MAX | 15 | + +| | | +|-----------|-----| +| TBC | 155 | +| NTS | 1 | +| BS_CV_MAX | 6 | + +| BSN' | CV | +|------|----| +| 137 | 15 | +| 138 | 15 | +| 139 | 15 | +| 140 | 14 | +| 141 | 13 | +| 142 | 12 | +| 143 | 11 | +| 144 | 10 | +| 145 | 9 | +| 146 | 8 | +| 147 | 7 | +| 148 | 6 | +| 149 | 5 | +| 150 | 4 | +| 151 | 3 | +| 152 | 2 | +| 153 | 1 | +| 154 | 0 | + +| BSN' | CV | +|------|----| +| 137 | 15 | +| 138 | 15 | +| 139 | 15 | +| 140 | 15 | +| 141 | 15 | +| 142 | 15 | +| 143 | 15 | +| 144 | 15 | +| 145 | 15 | +| 146 | 15 | +| 147 | 15 | +| 148 | 6 | +| 149 | 5 | +| 150 | 4 | +| 151 | 3 | +| 152 | 2 | +| 153 | 1 | +| 154 | 0 | + +Figure F.1: Example 1 + +## F.2 Example 2 + +In this example, shown in the first column, the total number of RLC data blocks in the TBF (TBC) is 155, the number of timeslots (NTS) is 3, and BS\_CV\_MAX is 6. Note that the RLC data block with BSN' = 154 arbitrarily occurs in timeslot 2. In the second column, the same example is shown with the RLC data block with BSN' = 154 occurring in timeslot 0. + +TBC 155 + +NTS 3 + +BS\_CV\_MAX 6 + +| TS0 | | TS1 | | TS2 | | TS0 | | TS1 | | TS2 | | +|------|----|------|----|------|----|------|----|------|----|------|----| +| BSN' | CV | BSN' | CV | BSN' | CV | BSN' | CV | BSN' | CV | BSN' | CV | +| 125 | 15 | 126 | 15 | 127 | 15 | 127 | 15 | 128 | 15 | 129 | 15 | +| 128 | 15 | 129 | 15 | 130 | 15 | 130 | 15 | 131 | 15 | 132 | 15 | +| 131 | 15 | 132 | 15 | 133 | 15 | 133 | 15 | 134 | 15 | 135 | 15 | +| 134 | 15 | 135 | 15 | 136 | 6 | 136 | 6 | 137 | 6 | 138 | 6 | +| 137 | 6 | 138 | 6 | 139 | 5 | 139 | 5 | 140 | 5 | 141 | 5 | +| 140 | 5 | 141 | 5 | 142 | 4 | 142 | 4 | 143 | 4 | 144 | 4 | +| 143 | 4 | 144 | 4 | 145 | 3 | 145 | 3 | 146 | 3 | 147 | 3 | +| 146 | 3 | 147 | 3 | 148 | 2 | 148 | 2 | 149 | 2 | 150 | 2 | +| 149 | 2 | 150 | 2 | 151 | 1 | 151 | 1 | 152 | 1 | 153 | 1 | +| 152 | 1 | 153 | 1 | 154 | 0 | 154 | 0 | | | | | + +Figure F.2: Example 2 + +## F.3 Example 3 + +In this example, the channel coding scheme is changed at BSN' = 149, resulting in more RLC data blocks being required to complete the TBF. The value of TBC is changed from 155 to 165 at BSN' = 149. + +TBC 155 + +NTS 3 + +BS\_CV\_MAX 6 + +| TS0 | | TS1 | | TS2 | | +|------|----|------|----|------|----| +| BSN' | CV | BSN' | CV | BSN' | CV | +| 125 | 15 | 126 | 15 | 127 | 15 | +| 128 | 15 | 129 | 15 | 130 | 15 | +| 131 | 15 | 132 | 15 | 133 | 15 | +| 134 | 15 | 135 | 15 | 136 | 6 | +| 137 | 6 | 138 | 6 | 139 | 5 | +| 140 | 5 | 141 | 5 | 142 | 4 | +| 143 | 4 | 144 | 4 | 145 | 3 | +| 146 | 3 | 147 | 3 | 148 | 2 | +| 149 | 5 | 150 | 5 | 151 | 5 | +| 152 | 4 | 153 | 4 | 154 | 4 | +| 155 | 3 | 156 | 3 | 157 | 3 | +| 158 | 2 | 159 | 2 | 160 | 2 | +| 161 | 1 | 162 | 1 | 163 | 1 | +| 164 | 0 | | | | | + +Figure F.3: Example 3 + +# Annex G (informative): Handling of erroneous protocol data, examples + +Procedures for the handling of erroneous protocol data are defined in sub-clause 11.1. These procedures define error labels for the treatment of syntactical errors in a received message. + +## G.1 Application of error labels + +An RLC/MAC control message description could have an error label included, as shown in the examples below. + +``` +< Packet XXX message content > ::= + < FIELD_1 : bit (3) > + < FIELD_2 : bit (16) > + ... + < padding bits > + ! < Ignore : bit (*) = < no string > > ; +``` + +In the case of a complete message, the contents of the received syntactically incorrect message can be ignored. + +Or + +``` +< PRECEDING_FIELD : bit (3) > + ... + { 00 < FIELD_1 : bit (10) > + | 01 < FIELD_2 : bit (10) > + ! < Ignore : bit (2+10) = < no string > > } + ... + < FOLLOWING_FIELD : bit (8) > +``` + +The syntactically incorrect description within the { } brackets can be ignored, the correctly received descriptions preceding and following the { } brackets shall be accepted. + +Or + +``` +< Structure 1 struct > ::= + < FIELD_1 : bit (3) > + { 1 < FIELD_2 : bit (8) > } ** 0 + ... + ! < Ignore : bit (*) = < no string > > ; +``` + +The above description indicates that the syntactically incorrect structure can be ignored. (Note: When this structure is included in the description of a message, any description following the structure must allow truncation.) + +## G.2 Application of the 'Message escape' error label + +The 'Message escape' branch protects the comprehension of the description following bit '0', as shown in the example below. + +``` +< Packet YYY message content > ::= -- Protocol version 1 + < FIELD_1 : bit (3) > + { 0 < FIELD_2 : bit (16) > + ... + < padding bits > + ! < Message escape : 1 bit (*) = > }; +``` + +The comprehension of 'FIELD\_2' is required. If the receiver detects bit '1', the 'Message escape' branch is called and the remaining part of the message can be ignored. + +The 'Message escape' branch may be used to introduce an new alternative coding of the message in a later version of the protocol. + +``` +< Packet YYY message content > ::= -- Protocol version 2 + < FIELD_1 : bit (3) > + { 0 < FIELD_2 : bit (16) > + ... + < padding bits > + | 1 -- New code option, replacing old 'Message escape': + { 00 < FIELD_3 : bit (12) > + ... + < padding bits > + ! < Message escape : { 01 | 10 | 11 } bit (*) = > } }; +``` + +An alternative coding, including 'FIELD\_3', is introduced following 'bit 1' in the former 'Message escape' branch. A new 'Message escape' is defined, this time using 3 control bits to allow future modification. + +A receiver implemented according to the original syntax will not accept the new coding. The original 'Message escape' branch will be called and the remaining part of the message, including 'FIELD\_3' is ignored. The content of 'FIELD\_1' (e.g. information to identify the receiver) is accepted and can be used to determine appropriate condition handling. + +## G.3 Application of truncated concatenation including 'padding bits' + +The truncated concatenation may include 'padding bits' at the end of a message. In that case, the resulting concatenation shall fit exactly with the received message length, otherwise the message is syntactically incorrect. + +The construction is useful, e.g. when a message ends with a sequence of optional components, where the transmitter may need to truncate tailing bits '0', indicating optional components not included in the message. + +``` +< Packet ZZZ message content > ::= +... +{ { 0 | 1 < Optional component 1 > } + { 0 | 1 < Optional component 2 > } +... + { 0 | 1 < Optional component N > } + < padding bits > } // ; +``` + +If the optional components from k to N are not needed in the message, the transmitter may use the full message length for the components up to optional component k - 1. The receiver accepts this message and assumes that the choice bits for optional components from k to N are all set to zero (i.e. these components are not present). + +However, if the receiver detects a syntactical error within one optional component which is indicated as present in the message, that results in a truncated concatenation which does not fit with the received message length. In this case, the receiver shall not accept the message as being syntactically correct. + +An error label may be provided within a truncated concatenation to allow the receiver to accept part of a concatenation in case of a syntactical error within it. This is useful for recurring components at the end of a message. + +``` +< Packet TTT message content > ::= +... +{ { 1 { < Recurring component > ! < Ignore : bit (*) = < no string > } } ** 0 + < padding bits > } // ; +``` + +If one of the recurring components is syntactically incorrect, the error branch is called. The error branch expands to the end of the message. The tail bit '0', terminating the recursion, and the 'spare padding' are truncated. The receiver accepts any syntactically correct instance of the recurring component preceding the syntactically incorrect one in the message. + +## G.4 Message extension using 'padding bits' + +The bit '0' in the first bit position of the 'padding bits', see sub-clause 11, may be altered into a bit '1' in future versions of the present document, in order to indicate an extension of the message content. When a message is received with bit '1' in this position, a receiver implemented according to the current version of the present document shall ignore the remaining part of the message. + +The example show how a message can be extended, relying on the fact that the 'padding bits' are defined with bit '0' in the first bit position. + +``` +< Packet UUU message content > ::= -- Current version of the present document + < contents defined in current version > + < padding bits > ; +``` + +The presence of the extension of the message content is indicated by bit '1'. The transmitter shall send a bit '1' in this position if any content is defined for the remaining part of the message. If a bit '0' is received in this position by a receiver in the new version, it shall ignore the remaining part of the message. + +``` +< Packet UUU message content > ::= -- Future version of the present document + < contents defined in current version > + { null | 0 bit** = < no string > -- Receiver backward compatible with earlier version + | 1 -- Bit '1' sent by transmitter in new version + < contents defined in a future version > + < padding bits > } ; -- New 'padding bits' allows further extension +``` + +## G.5 Message extension using the Extension Bits IE + +The Extension Bits IE defined in sub-clause 12.26 may be used in some messages or information elements as a placeholder for future extension when an extension at the end of the message is less suitable. The Extension Bits IE is usually included as an optional or conditional information element. When included, it provides a length indication and a corresponding set of 'spare bits', which may be used in future versions of the protocol to carry an extension of the message contents. + +When this extension mechanism is applied, the original Extension Bits IE shall be removed from the message and replaced by a new information element or a new construction, carrying an extension by up to 64 bits of the message contents. An example is given below. + +``` + +< Packet VVV message content > ::= -- Current (original) version of the present document +... +{ 0 | 1 < Extension Bits : Extension Bits IE > } -- sub-clause 12.26 +... +< padding bits > ; + +``` + +The Extension Bits IE is replaced by a new construction named 'VVV Extension Info'. The new construction includes extensions introduced in Rel-M and Rel-N. In order to enable backward compatibility, truncation of the extension information may occur between released versions of the protocol. The receiver shall assume the value zero of any truncated bits. In order to enable forward compatibility, additional 'spare bits' may occur after the defined extensions. + +``` + +< Packet VVV message content > ::= -- Future version of the present document; extensions in Rel-M and Rel-N +... +{ 0 | 1 < VVV Extension length : bit (6) > + < bit (val(VVV Extension length) + 1) + & { < VVV Extension Info > ! { bit** = } } > } +... +< padding bits > ; + +< VVV Extension Info > ::= +{ { -- Rel-M extension + < Extension in Rel-M > } + { -- Rel-N extension + < Extension in Rel-N > } + < spare bit >** } // ; -- Truncation may occur between released versions of the protocol + -- The receiver shall assume the value zero of any truncated bits + +``` + +# --- Annex H (informative): (void) + +# --- Annex I (informative): EGPRS RLC Window Sizes + +Although for each multislot allocation, the selected window size could preferably be the maximum, a smaller window size may be selected in order to optimize e.g. the number of (multislot) users and network memory consumption. + +However, for each MS, in order to meet a performance which corresponds to the number of timeslots assigned to this MS, the selected window size shall not be smaller than a minimum window size for this particular multislot allocation. + +For each network, the round-trip delay has a direct implication on the performance, hence on the definition of the minimum window sizes. Consequently, no generic minimum window sizes are suggested. However, for information, the table below lists the window size ranges recommended with a round-trip delay of about 120 ms. + +For a mobile station in DLMC configuration the downlink window size is the same as the supported buffer size (see Table 9.1.9.3.2) whereas uplink window sizes shall still be managed as per EGPRS TBF mode without a DLMC configuration (see sub-clause 9.1.9.3). + +| Window size | Coding | Timeslots assigned (Multislot capability) | | | | | | | | +|-------------|--------|-------------------------------------------|---|---|---|---|---|---|------| +| | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8-16 | + +| | | | | | | | | | | +|----------|-------|-----|-----|-----|-----|-----|-----|-----|-----| +| 64 | 00000 | Min | | | | | | | | +| 96 | 00001 | | Min | | | | | | | +| 128 | 00010 | | | | | | | | | +| 160 | 00011 | | | Min | Min | | | | | +| 192 | 00100 | Max | | | | | | | | +| 224 | 00101 | | | | | Min | | | | +| 256 | 00110 | | Max | | | | | | | +| 288 | 00111 | | | | | | | | | +| 320 | 01000 | | | | | | Min | | | +| 352 | 01001 | | | | | | | Min | | +| 384 | 01010 | | | Max | | | | | | +| 416 | 01011 | | | | | | | | | +| 448 | 01100 | | | | | | | | | +| 480 | 01101 | | | | | | | | | +| 512 | 01110 | | | | Max | | | | Min | +| 544 | 01111 | | | | | | | | | +| 576 | 10000 | | | | | | | | | +| 608 | 10001 | | | | | | | | | +| 640 | 10010 | | | | | Max | | | | +| 672 | 10011 | | | | | | | | | +| 704 | 10100 | | | | | | | | | +| 736 | 10101 | | | | | | | | | +| 768 | 10110 | | | | | | Max | | | +| 800 | 10111 | | | | | | | | | +| 832 | 11000 | | | | | | | | | +| 864 | 11001 | | | | | | | | | +| 896 | 11010 | | | | | | | Max | | +| 928 | 11011 | | | | | | | | | +| 960 | 11100 | | | | | | | | | +| 992 | 11101 | | | | | | | | | +| 1024 | 11110 | | | | | | | | Max | +| Reserved | 11111 | x | X | x | x | x | x | x | X | + +# Annex J (informative): An example of MCS-8 retransmission + +This example shows the radio blocks of an MCS-8 RLC data block retransmitted using MCS-6 (padding) and MCS-3 (padding). + +The following hypothesis are used: + +- Uplink block; +- The MCS-8 RLC data block contains three LLC PDU: last part of LLC1 (last 40 octets), the whole LLC2 (length 60 octets) and the first part of LLC3 (first 34 octets); +- No TLLI nor PFI is present. + +## J.1 Original MCS-8 RLC data block + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | | | +|-----------------------|-----------------|-----|-----|---|----|---|---|------------------|--|--|--|--| +| TFI | Countdown Value | | | | SI | R | | 1 (header) | | | | | +| BSN1 | | TFI | | | | | | 2 (header) | | | | | +| BSN 2 | BSN 1 | | | | | | | 3 (header) | | | | | +| BSN2 | | | | | | | | 4 (header) | | | | | +| Spare | PI | RSB | CPS | | | | | 5 (header) | | | | | +| Spare | | | | | | | | (See note | | | | | +| | | | | | TI | E | | below) | | | | | +| Length indicator = 40 | | | | | | E | | 1 (RLC data 1) | | | | | +| LLC1 (octet 1) | | | | | | | | 2 (RLC data 1) | | | | | +| LLC1 (octet 2) | | | | | | | | 3 (RLC data 1) | | | | | +| : | | | | | | | | : | | | | | +| LLC1 (octet 39) | | | | | | | | 40 (RLC data 1) | | | | | +| LLC1 (octet 40) | | | | | | | | 41 (RLC data 1) | | | | | +| LLC2 (octet 1) | | | | | | | | 42 (RLC data 1) | | | | | +| LLC2 (octet 2) | | | | | | | | 43 (RLC data 1) | | | | | +| : | | | | | | | | : | | | | | +| LLC2 (octet 26) | | | | | | | | 67 (RLC data 1) | | | | | +| LLC2 (octet 27) | | | | | | | | 68 (RLC data 1) | | | | | +| | | | | | TI | E | | (See note below) | | | | | +| Length indicator = 33 | | | | | | E | | 1 (RLC data 2) | | | | | +| LLC2 (octet 28) | | | | | | | | 2 (RLC data 2) | | | | | +| LLC2 (octet 29) | | | | | | | | 3 (RLC data 2) | | | | | +| : | | | | | | | | : | | | | | +| LLC2 (octet 59) | | | | | | | | 33 (RLC data 2) | | | | | +| LLC2 (octet 60) | | | | | | | | 34 (RLC data 2) | | | | | +| LLC3 (octet 1) | | | | | | | | 35 (RLC data 2) | | | | | +| LLC3 (octet 2) | | | | | | | | 36 (RLC data 2) | | | | | +| : | | | | | | | | : | | | | | +| LLC3 (octet 33) | | | | | | | | 67 (RLC data 2) | | | | | +| LLC3 (octet 34) | | | | | | | | 68 (RLC data 2) | | | | | + +NOTE: At this row, only a few bits are sent (not a full octet). + +## J.2 Retransmission in two MCS-6 RLC data blocks + +When this RLC data block is repeated using MCS-6 (padding), the two radio blocks have the following format: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | | | | | | +|-----------------------|-----------------|-------|---|-----|-----|---|---|------------------|--|--|--|--|--|--|--| +| TFI | Countdown value | | | | SI | R | | 1 (header) | | | | | | | | +| BSN 1 | | | | TFI | | | | 2 (header) | | | | | | | | +| CPS | BSN 1 | | | | | | | 3 (header) | | | | | | | | +| Spare | | PI | | RSB | CPS | | | 4 (header) | | | | | | | | +| | | Spare | | | | | | (See note below) | | | | | | | | +| Padding | | | | | | | | 1 (RLC data) | | | | | | | | +| : | | | | | | | | : | | | | | | | | +| Padding | | | | | | | | 6 (RLC data) | | | | | | | | +| | | | | TI | E | | | (See note below) | | | | | | | | +| Length indicator = 40 | | | | | | E | | 7 (RLC data) | | | | | | | | +| LLC1 (octet 1) | | | | | | | | 8 (RLC data) | | | | | | | | +| LLC1 (octet 2) | | | | | | | | 9 (RLC data) | | | | | | | | +| : | | | | | | | | : | | | | | | | | +| LLC1 (octet 39) | | | | | | | | 46 (RLC data) | | | | | | | | +| LLC1 (octet 40) | | | | | | | | 47 (RLC data) | | | | | | | | +| LLC2 (octet 1) | | | | | | | | 48 (RLC data) | | | | | | | | +| LLC2 (octet 2) | | | | | | | | 49 (RLC data) | | | | | | | | +| : | | | | | | | | : | | | | | | | | +| LLC2 (octet 26) | | | | | | | | 73 (RLC data) | | | | | | | | +| LLC2 (octet 27) | | | | | | | | 74 (RLC data) | | | | | | | | + + + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | | | | | | +|-----------------------|-----------------|-------|---|-----|-----|---|---|------------------|--|--|--|--|--|--|--| +| TFI | Countdown value | | | | SI | R | | 1 (header) | | | | | | | | +| BSN 1 | | | | TFI | | | | 2 (header) | | | | | | | | +| CPS | BSN 1 | | | | | | | 3 (header) | | | | | | | | +| Spare | | PI | | RSB | CPS | | | 4 (header) | | | | | | | | +| | | Spare | | | | | | (See note below) | | | | | | | | +| Padding | | | | | | | | 1 (RLC data) | | | | | | | | +| : | | | | | | | | : | | | | | | | | +| Padding | | | | | | | | 6 (RLC data) | | | | | | | | +| | | | | TI | E | | | (See note below) | | | | | | | | +| Length indicator = 33 | | | | | | E | | 7 (RLC data) | | | | | | | | +| LLC2 (octet 28) | | | | | | | | 8 (RLC data) | | | | | | | | +| LLC2 (octet 29) | | | | | | | | 9 (RLC data) | | | | | | | | +| : | | | | | | | | : | | | | | | | | +| LLC2 (octet 59) | | | | | | | | 39 (RLC data) | | | | | | | | +| LLC2 (octet 60) | | | | | | | | 40 (RLC data) | | | | | | | | +| LLC3 (octet 1) | | | | | | | | 41 (RLC data) | | | | | | | | +| LLC3 (octet 2) | | | | | | | | 42 (RLC data) | | | | | | | | +| : | | | | | | | | : | | | | | | | | +| LLC3 (octet 33) | | | | | | | | 73 (RLC data) | | | | | | | | +| LLC3 (octet 34) | | | | | | | | 74 (RLC data) | | | | | | | | + +NOTE: At this row, only a few bits are sent (not a full octet). + +## J.3 Retransmission in four MCS-3 RLC data blocks + +When the original RLC data block is repeated using MCS-3, the four radio blocks have the following format: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | | | +|-----------------------|-----------------|----|-----|-----|-----|-----|---|--------------------|--|--|--|--| +| TFI | Countdown value | | | | SI | R | | 1 (header) | | | | | +| BSN 1 | | | | | TFI | | | 2 (header) | | | | | +| CPS | BSN 1 | | | | | | | 3 (header) | | | | | +| | Spare | PI | RSB | SPB | | CPS | | (See note 1 below) | | | | | +| Padding | | | | | | | | 1 (RLC data) | | | | | +| : | | | | | | | | : | | | | | +| Padding | | | | | | | | 6 (RLC data) | | | | | +| | | | | | | TI | E | (See note 1 below) | | | | | +| Length indicator = 40 | | | | | | | E | 7 (RLC data) | | | | | +| LLC1 (octet 1) | | | | | | | | 8 (RLC data) | | | | | +| LLC1 (octet 2) | | | | | | | | 9 (RLC data) | | | | | +| : | | | | | | | | : | | | | | +| LLC1 (octet 29) | | | | | | | | 36 (RLC data) | | | | | +| LLC1 (octet 30) | | | | | | | | 37 (RLC data) | | | | | + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | +|-----------------|-----------------|----|-----|-----|-----|-----|---|--------------------|--|--| +| TFI | Countdown value | | | | SI | R | | 1 (header) | | | +| BSN 1 | | | | | TFI | | | 2 (header) | | | +| CPS | BSN 1 | | | | | | | 3 (header) | | | +| | Spare | PI | RSB | SPB | | CPS | | (See note 1 below) | | | +| | | | | | | TI | E | (See note 2 below) | | | +| LLC1 (octet 31) | | | | | | | | 1 (RLC data) | | | +| LLC1 (octet 32) | | | | | | | | 2 (RLC data) | | | +| : | | | | | | | | : | | | +| LLC1 (octet 39) | | | | | | | | 9 (RLC data) | | | +| LLC1 (octet 40) | | | | | | | | 10 (RLC data) | | | +| LLC2 (octet 1) | | | | | | | | 11 (RLC data) | | | +| LLC2 (octet 2) | | | | | | | | 12 (RLC data) | | | +| : | | | | | | | | : | | | +| LLC2 (octet 26) | | | | | | | | 36 (RLC data) | | | +| LLC2 (octet 27) | | | | | | | | 37 (RLC data) | | | + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | | | +|-----------------------|-----------------|----|-----|-----|-----|-----|---|--------------------|--|--|--|--| +| TFI | Countdown value | | | | SI | R | | 1 (header) | | | | | +| BSN 1 | | | | | TFI | | | 2 (header) | | | | | +| CPS | BSN 1 | | | | | | | 3 (header) | | | | | +| | Spare | PI | RSB | SPB | | CPS | | (See note 1 below) | | | | | +| Padding | | | | | | | | 1 (RLC data) | | | | | +| : | | | | | | | | : | | | | | +| Padding | | | | | | | | 6 (RLC data) | | | | | +| | | | | | | TI | E | (See note 1 below) | | | | | +| Length indicator = 33 | | | | | | | E | 7 (RLC data) | | | | | +| LLC2 (octet 28) | | | | | | | | 8 (RLC data) | | | | | +| LLC2 (octet 29) | | | | | | | | 9 (RLC data) | | | | | +| : | | | | | | | | : | | | | | +| LLC2 (octet 56) | | | | | | | | 36 (RLC data) | | | | | +| LLC2 (octet 57) | | | | | | | | 37 (RLC data) | | | | | + +Error: +Reference + +Error: Reference source not found + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | | | | +|-----------------|-----------------|----|-------|-----|----|-----|---|--------------------|--|--|--|--| +| TFI | Countdown value | | | | SI | R | | 1 (header) | | | | | +| BSN 1 | | | | TFI | | | | | | | | | +| CPS | | | BSN 1 | | | | | 2 (header) | | | | | +| | Spare | PI | RSB | SPB | | CPS | | 3 (header) | | | | | +| | | | | | | TI | E | (See note 1 below) | | | | | +| | | | | | | | | (See note 2 below) | | | | | +| LLC2 (octet 58) | | | | | | | | 1 (RLC data) | | | | | +| LLC2 (octet 59) | | | | | | | | 2 (RLC data) | | | | | +| LLC2 (octet 60) | | | | | | | | 3 (RLC data) | | | | | +| LLC3 (octet 1) | | | | | | | | 4 (RLC data) | | | | | +| LLC3 (octet 2) | | | | | | | | 5 (RLC data) | | | | | +| : : | | | | | | | | : | | | | | +| LLC3 (octet 33) | | | | | | | | 36 (RLC data) | | | | | +| LLC3 (octet 34) | | | | | | | | 37 (RLC data) | | | | | + +NOTE 1: At this row, only a few bits are sent (not a full octet). + +NOTE 2: In this radio block, the bits TI / E are meaningless. + +# Annex K (informative): Signalling uplink assignments for Downlink Dual Carrier and/or RTTI or MTI configurations + +In the PACKET UPLINK ASSIGNMENT and PACKET TIMESLOT RECONFIGURE, uplink assignments may include the Dynamic Allocation 2 struct. + +The maximum number of USFs, timeslots and PDCH pairs for which allocations are made (i.e. the maximum value of $N\_USF + 1$ , $N\_TS + 1$ and $N\_PAIRS + 1$ , respectively), and hence the maximum number of repetitions of the subsequent fields and structures, are as follows: + +| Assignment Type | RTTI/MTI configuration | USF mode (applicable to RTTI configurations only) | Maximum value of ( $N\_USF + 1$ ) | Maximum value of ( $N\_TS + 1$ ) | Maximum value of ( $N\_PAIRS + 1$ ) | +|------------------------------------|------------------------|---------------------------------------------------|-----------------------------------|----------------------------------|-------------------------------------| +| Single Carrier Assignment (Note 1) | No | | 8 | 8 | n/a | +| | Yes | RTTI | 4 | n/a | 4 | +| | Yes | BTTI | 8 | n/a | 4 | +| Dual Carrier Assignment | No | | 16 | 16 | n/a | +| | Yes | RTTI | 8 | n/a | 8 | +| | Yes | BTTI | 16 | n/a | 8 | + +NOTE 1: This applies when the Assignment Type field indicates "Assignment on single carrier only" or "Modification of Existing Assignment" + +The order of USF assignment for RTTI assignments is as shown in the table below. PNx stands for PDCH pair number x, where PDCH pairs are ordered according to the timeslot numbers of their constituent PDCHs. The prefixes C1 and C2 indicate the resources on carrier 1 and carrier 2 respectively. The subscript 'a' (respectively 'b') indicates that the USF applies to the first two (respectively second two) TDMA frames of the following basic radio block period (see sub-clauses 8.1.1.1, 8.1.1.2.1). + +| Assignment Type | RTTI configuration | Order of USF assignments | Order of USF assignments (RTTI mode with BTTI USF, without power control parameters) | +|------------------------------------|--------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| Single Carrier Assignment (Note 1) | No | TN0, ...TN7 | n/a | +| Single Carrier Assignment (Note 1) | Yes | PN0, ..PN3
(Note 2) | PN0a, PN0b, PN1a, ... PN3b
(Note 2) | +| Dual Carrier Assignment | No | C1/TN0, ...C1/TN7,
C2/TN0, ...C2/TN7 | n/a | +| Dual Carrier Assignment | Yes | C1/PN0, ...C1/PN3,
C2/PN0, ...C2/PN3
(Note 2) | C1/PN0a, C1/PN0b,
C1/PN1a, ... C1/PN3b,
C2/PN0a, C2/PN0b,
C2/PN1a, ... C2/PN3b
(Note 2) | + +NOTE 1: This applies when the Assignment Type field is included and indicates "Assignment on single carrier only" or "Modification of Existing Assignment" + +NOTE 2: In a RTTI configuration, the table assumes a default PDCH pair configuration on each carrier (see sub-clause 7.1.3.6). If fewer than four PDCH pairs are configured on a carrier the maximum value of $N\_USF$ or $N\_PAIRS$ is correspondingly reduced and the list contains only the PDCH pairs in the PDCH pair configuration, e.g. if there are 3 PDCH pairs configured on each carrier, the order of USF assignments for a Downlink Dual Carrier, RTTI configuration is C1/PN0 ... C1/PN2, C2/PN0 ... C2/PN2. + +If the value of ( $N\_USF + 1$ ), ( $N\_TS + 1$ ) or ( $N\_PAIRS + 1$ ) is lower than the maximum, then the list of USF assignments is truncated, and there is (implicitly) no assignment for the timeslots/PDCH pairs for which no corresponding value is present. + +For MTTC configurations, the order of USF assignments for PDCH-pairs is as shown above for RTTC assignments. In addition, the last assigned USF(s) applies to the PDCH on carrier 1 (if assigned) and then to the PDCH on carrier 2 (if assigned). + +# Annex L (informative): MultislotClassGroup in EGPRS Packet Channel Request + +In the EGPRS PACKET CHANNEL REQUEST message with cause "One Phase Access Request by Reduced Latency MS", the mobile station multislot class is signalled by the MultislotClassGroup. The MultislotClassGroup indicates the set of the EGPRS multislot classes to which the mobile station belongs. Supported multislot class configurations are limited by the maximum transition times ( $T_{ta}$ , $T_{tb}$ , $T_{ra}$ , $T_{rb}$ ) and the minimum number of RX, TX and SUM slots common to the multislot classes in each set as follows (see also 3GPP TS 45.002) + +| MultislotClassGroup | Maximum number of slots | | | Minimum number of slots | | | | +|---------------------|-------------------------|----|-----|-------------------------|----------|----------|----------| +| | Rx | Tx | Sum | $T_{ta}$ | $T_{tb}$ | $T_{ra}$ | $T_{rb}$ | +| 0 0 0 | 2 | 2 | 4 | 3 | 1 | 3 | 1 | +| 0 0 1 | 3 | 2 | 5 | 3 | 1 | 2 | 1 | +| 0 1 0 | 5 | 2 | 6 | 2 | 1 | $1+t_0$ | 1 | +| 0 1 1 | 4 | 3 | 5 | 2 | 1 | 2 | 1 | +| 1 0 0 | 5 | 4 | 6 | 2 | 1 | 1 | 1 | +| 1 0 1 | 5 | 4 | 6 | 2 | 1 | $1+t_0$ | 1 | +| 1 0 1 | 6 | 5 | 7 | 1 | 1 | 1 | $t_0$ | +| 1 1 1 | reserved | | | | | | | + +# Annex M (informative): MTTI Assignments and allocations + +MTTI assignments are described in sub-clause 7.1.3.7. Examples of valid MTTF assignments are shown in Figures M.1 and M.2. The examples shown in Figure M.1 may be used for either uplink or downlink TBFs. Examples of MTTF assignments that are not permitted and cannot be assigned are shown in Figure M.3. + +![Figure M.1: Valid MTTF assignments (single TBF). The diagram shows three examples of MTTF assignments on a timeline represented by a row of 8 cells. 1. The first example shows the second and third cells highlighted with a thick black border. 2. The second example shows the second, third, and fourth cells highlighted with a thick black border. 3. The third example shows two rows of 8 cells. In the top row, the first, second, and third cells are highlighted. In the bottom row, the first and second cells are highlighted. A large curly brace on the right side groups these two rows together, indicating they represent a single MTTF assignment across two frames.](9ecaf3842a06bb8defd6bea7de551283_img.jpg) + +Figure M.1: Valid MTTF assignments (single TBF). The diagram shows three examples of MTTF assignments on a timeline represented by a row of 8 cells. 1. The first example shows the second and third cells highlighted with a thick black border. 2. The second example shows the second, third, and fourth cells highlighted with a thick black border. 3. The third example shows two rows of 8 cells. In the top row, the first, second, and third cells are highlighted. In the bottom row, the first and second cells are highlighted. A large curly brace on the right side groups these two rows together, indicating they represent a single MTTF assignment across two frames. + +Figure M.1: Valid MTTF assignments (single TBF) + +![Figure M.2: Valid MTTF assignment (1 uplink TBF & 1 downlink TBF). The diagram shows two rows of 8 cells separated by a thick black horizontal bar. In the top row, the second and third cells are highlighted. In the bottom row, the fifth and sixth cells are highlighted. A double-headed arrow is positioned between the two rows, indicating the relationship between the uplink and downlink TBFs.](97474b58ccf5b5329b0b9ec637ab15d5_img.jpg) + +Figure M.2: Valid MTTF assignment (1 uplink TBF & 1 downlink TBF). The diagram shows two rows of 8 cells separated by a thick black horizontal bar. In the top row, the second and third cells are highlighted. In the bottom row, the fifth and sixth cells are highlighted. A double-headed arrow is positioned between the two rows, indicating the relationship between the uplink and downlink TBFs. + +Figure M.2: Valid MTTF assignment (1 uplink TBF & 1 downlink TBF) + +![Figure M.3: Invalid MTTC assignments. The diagram shows three rows of radio blocks. The first row has 6 blocks, with the 2nd and 3rd blocks highlighted. The second row has 6 blocks, with the 3rd, 4th, and 5th blocks highlighted. The third row has 6 blocks, with the 1st, 2nd, and 3rd blocks highlighted. These highlightings represent invalid MTTC assignments.](f2c8124b953b46b53423532cff4903e8_img.jpg) + +Figure M.3: Invalid MTTC assignments. The diagram shows three rows of radio blocks. The first row has 6 blocks, with the 2nd and 3rd blocks highlighted. The second row has 6 blocks, with the 3rd, 4th, and 5th blocks highlighted. The third row has 6 blocks, with the 1st, 2nd, and 3rd blocks highlighted. These highlightings represent invalid MTTC assignments. + +Figure M.3: Invalid MTTC assignments + +![Figure M.4: Example MTTC assignments. The diagram shows a large black bar representing a radio frame. Below it, there are two rows of radio blocks. The top row has 6 blocks, with the 1st, 2nd, and 3rd blocks highlighted. The bottom row has 6 blocks, with the 4th, 5th, and 6th blocks highlighted. These highlightings represent example MTTC assignments.](a0e4d56066bf089079b9b4d24f666b01_img.jpg) + +Figure M.4: Example MTTC assignments. The diagram shows a large black bar representing a radio frame. Below it, there are two rows of radio blocks. The top row has 6 blocks, with the 1st, 2nd, and 3rd blocks highlighted. The bottom row has 6 blocks, with the 4th, 5th, and 6th blocks highlighted. These highlightings represent example MTTC assignments. + +Figure M.4: Example MTTC assignments + +Figure M.4 shows two reduced radio block periods for each of two possible MTTC configurations, during which the mobile station may be allocated resources to transmit RTTC radio blocks (A,B,D,E for Assignment 1 and G,H,I and J for Assignment 2) and/or BTTC radio blocks (C for Assignment 1 and F for Assignment 2). Tables M.1 and M.2 show which radio block(s) are allocated, depending on the timeslot(s) in the previous basic radio block period on which assigned USF(s) were received. + +Table M.1: Example MTTC allocations – BTTC USF mode with EDA : Assignment 1 + +| Assigned USF received on TN: | Allocated blocks | | | | | +|------------------------------|------------------|---|---|---|---| +| | A | B | C | D | E | +| 1 | X | X | X | | | +| 2 | | | | X | X | +| 3 | | X | X | | | +| 4 | | | | | X | +| 5 | | | X | | | + +Table M.2: Example MTTC allocations – BTTC USF mode with EDA : Assignment 2 + +| Assigned USF received on TN | Allocated blocks | | | | | +|-----------------------------|------------------|---|---|---|---| +| | F | G | H | I | J | +| 1 | X | X | X | X | X | +| 2 | | X | X | | | +| 3 | | | | X | X | +| 4 | | | X | | | +| 5 | | | | | X | + +# Annex N (normative): Uplink Radio Block Transmission order for EFTA + +A mobile station with an uplink TBF operating in BTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCHs allocated by the USF. If the mobile station has P RLC/MAC blocks ready for transmission, then this subset is defined as the first P number of the allocated uplink PDCHs arranged according to the specific timeslot numbers order as specified in Table N.1 below. $T_{ra}$ or $T_{rb}$ , whichever is applicable, is the switching time from transmission to reception (see 3GPP TS 45.002). + +**Table N.1: Uplink timeslots transmission order for EFTA** + +| Lowest Numbered
Downlink Timeslot the MS
Needs to Monitor | $T_{ra}$ or $T_{rb}$ , whichever is applicable | | | +|-----------------------------------------------------------------|------------------------------------------------|-----------------|-----------------| +| | 0 | 1 | 2 | +| TN0 | 4,3,2,1,0,5,6,7 | 3,2,1,0,4,5,6,7 | 2,1,0,3,4,5,6,7 | +| TN1 | 5,4,3,2,1,0,6,7 | 4,3,2,1,0,5,6,7 | 3,2,1,0,4,5,6,7 | +| TN2 | 6,5,4,3,2,1,0,7 | 5,4,3,2,1,0,6,7 | 4,3,2,1,0,5,6,7 | +| TN3 | 7,6,5,4,3,2,1,0 | 6,5,4,3,2,1,0,7 | 5,4,3,2,1,0,6,7 | +| TN4 | 7,6,5,4,3,2,1,0 | 7,6,5,4,3,2,1,0 | 6,5,4,3,2,1,0,7 | +| TN5 | 7,6,5,4,3,2,1,0 | 7,6,5,4,3,2,1,0 | 7,6,5,4,3,2,1,0 | +| TN6 | 7,6,5,4,3,2,1,0 | 7,6,5,4,3,2,1,0 | 7,6,5,4,3,2,1,0 | +| TN7 | 7,6,5,4,3,2,1,0 | 7,6,5,4,3,2,1,0 | 7,6,5,4,3,2,1,0 | + +A mobile station with an uplink TBF operating in RTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCH-pairs allocated by the USF in the same manner as specified above. For this case the specific timeslot number order shall be seen as indicating the lowest numbered timeslot of the uplink PDCH-pair. + +NOTE: The above described rule determine the subset of the allocated uplink PDCHs or PDCH-pairs on which uplink transmissions shall be performed when EFTA is used. This procedure however, does not define which uplink PDCHs or PDCH-pairs that shall be allocated by the USF. Nor does the procedure define the individual ordering of any transmitted RLC/MAC blocks on these resources, which shall remain the same as for the case when EFTA is not used. + +A mobile station with an uplink TBF for which EFTA is used shall perform the transmission of any uplink PACCH message allocated via the polling mechanism (see sub-clauses 10.4.4b and 10.4.5) on the first of the assigned uplink PDCHs or PDCH-pairs arranged according to the specific timeslot number order as described by Table N.1 above, regardless of which resources are allocated by the USF. The switching time $T_{ra}$ or $T_{rb}$ shall be interpreted according to its value at the time the poll was received. + +The following example is considered for illustration of the above rules: + +- A mobile station is assigned an uplink TBF in BTTI configuration for which EFTA is used. +- This mobile station is allocated uplink PDCHs on TN0, TN1, TN2 and TN3 during the radio block period considered. +- This mobile station only has 3 RLC/MAC blocks available for transmission, out of which one is a PACCH message allocated via the polling mechanism. +- The lowest numbered downlink timeslot the mobile station has to monitor is TN0 and that the applicable switching time $T_{rb}$ is 1. + +According to the above description, the mobile station shall then transmit its PACCH message on TN3, whereas the remaining RLC/MAC blocks shall be transmitted on TN1 and TN2 respectively. + +# Annex O (informative): Change History + +| Date | TSG# | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|--------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------|--------| +| 2015-12 | | | | | | Generation of Rel-13 version based on version 12.5.0 | 13.0.0 | +| | GP-68 | GP-151192 | 1607 | 4 | | Introduction of Power Efficient Operation | 13.0.0 | +| | GP-68 | GP-151193 | 1618 | - | | Introduction of EC-EGPRS | 13.0.0 | +| 2016-02 | GP-69 | GP-160170 | 1619 | 3 | | EC-EGPRS Control Messages | 13.1.0 | +| | GP-69 | GP-160168 | 1610 | 6 | | EC-EGPRS - TBF Establishment procedures | 13.1.0 | +| | GP-69 | GP-160148 | 1611 | 4 | | EC-EGPRS - MAC procedures in packet transfer mode | 13.1.0 | +| | GP-69 | GP-160140 | 1612 | 5 | | EC-EGPRS - RLC procedures | 13.1.0 | +| | GP-69 | GP-160135 | 1615 | 2 | | EC-EGPRS - RLC/MAC block structure | 13.1.0 | +| | GP-69 | GP-160186 | 1622 | - | | Corrections to overlaid CDMA | 13.1.0 | +| | GP-69 | GP-160144 | 1621 | 1 | | Miscellaneous corrections to eDRX | 13.1.0 | +| 2016-06 | GP-70 | GP-160414 | 1625 | 1 | B | EC-GSM-IoT RLC/MAC Block Structure and Control Messages, Miscellaneous Corrections | 13.2.0 | +| 2016-06 | GP-70 | GP-160403 | 1624 | 1 | F | Miscellaneous corrections to eDRX_GSM | 13.2.0 | +| 2016-06 | GP-70 | GP-160420 | 1626 | 2 | F | EC-GSM-IoT Procedures and Timers, Miscellaneous Corrections | 13.2.0 | +| 2016-09 | RP-73 | RP-161392 | 1628 | 1 | F | Miscellaneous EC-GSM-IoT Changes | 13.3.0 | +| 2016-09 | RP-73 | RP-161393 | 1629 | 2 | F | Clarification of PEO Code Point Usage | 13.3.0 | +| 2016-09 | RP-73 | RP-161392 | 1630 | 4 | F | Miscellaneous corrections to EC-GSM-IoT | 13.3.0 | +| 2016-09 | | | | | | Editorial clean-up | 13.3.1 | +| 2016-12 | RP-74 | RP-162070 | 1634 | - | F | Miscellaneous corrections to EC-GSM-IoT | 13.4.0 | +| 2017-03 | RP-75 | RP-170063 | 1640 | - | F | Clarifying Order of B11 to B1 in in 11 Bit Access | 13.5.0 | +| 2017-03 | RP-75 | RP-170061 | 1635 | 2 | B | Introduction of Alternative Mappings for Higher Coverage Classes with 2 PDCHs | 14.0.0 | +| 2017-06 | RP-76 | RP-170923 | 1631 | 7 | B | Introduction of Multilayeration | 14.1.0 | +| 2017-06 | RP-76 | RP-170924 | 1639 | 4 | B | Introduction of new UL coverage class CC5 for UL MCL improvement | 14.1.0 | +| 2017-06 | RP-76 | RP-170925 | 1641 | 2 | F | Introduction of enhanced DECOR for GERAN | 14.1.0 | +| 2017-09 | RP-77 | RP-171593 | 1642 | 1 | F | Handling of PCCN message including a 3G CCN Measurement Report with no available 3G neighbour cell report | 14.2.0 | +| 2017-09 | RP-77 | RP-171597 | 1643 | - | A | Removing References to 44.160 and 44.118 (Iu mode) | 14.2.0 | +| 2017-09 | RP-77 | RP-171594 | 1646 | 1 | F | Corrections to Figures 10.3a.2.1.1 and 10.3a.2.2.1 | 14.2.0 | +| 2017-09 | RP-77 | RP-171593 | 1647 | 1 | F | Clarification of DL PACCH DRX in Extended Uplink TBF Mode | 14.2.0 | +| 2018-06 | RP-80 | RP-180822 | 1648 | 2 | B | Security enhancement for MTA in network configuration without LLC security | 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/44_series/44064/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-16/44_series/44064/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ce2785103f2cc0c981daeee6959a52a7d94dd10 --- /dev/null +++ b/marked/Rel-16/44_series/44064/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:430bac2f73f7d21451bc107c509c94194307740f43af6e9c81b5c98a1391aac9 +size 43135 diff --git a/marked/Rel-16/44_series/44064/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/Rel-16/44_series/44064/077f85b82901283b4657fd2b45fc0294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98e20c9e3566084553ae3b6d88e2224584121f7c --- /dev/null +++ b/marked/Rel-16/44_series/44064/077f85b82901283b4657fd2b45fc0294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:937263ee419adf7111d70d41892defac731fab4e715c213598799152394ac411 +size 34309 diff --git a/marked/Rel-16/44_series/44064/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-16/44_series/44064/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f68185704862b7d42dffd9809f44bf0b739dfde --- /dev/null +++ b/marked/Rel-16/44_series/44064/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4592d5e294d6ff92e917c376ff9933b96d4a20b9f19662a4fdbed752ca826625 +size 47075 diff --git a/marked/Rel-16/44_series/44064/08f6ace0c83e7394657fa372b47aec04_img.jpg b/marked/Rel-16/44_series/44064/08f6ace0c83e7394657fa372b47aec04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d59589f532c182ae6344957f4703dacbf9540952 --- /dev/null +++ b/marked/Rel-16/44_series/44064/08f6ace0c83e7394657fa372b47aec04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2459d9522c0624f2e99b75b3a0b9c6a0a2b56421161132483638c69ea5378af +size 36789 diff --git a/marked/Rel-16/44_series/44064/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/44_series/44064/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e54a10285cd86298109eebd8debe7cf64a0f902e --- /dev/null +++ b/marked/Rel-16/44_series/44064/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:631e0f9cfa80b66ce83c9813731f049d877a7a4dd195118cba484fa124586e06 +size 41385 diff --git a/marked/Rel-16/44_series/44064/1230eaa9d75a09d7e7b8509931e9190e_img.jpg b/marked/Rel-16/44_series/44064/1230eaa9d75a09d7e7b8509931e9190e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74e5782b1ec26c59d0866a12ca462cf5e6d8003a --- /dev/null +++ b/marked/Rel-16/44_series/44064/1230eaa9d75a09d7e7b8509931e9190e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7585c529cfec3599ddb4155e6a81a5058dd44888b06299f590148fcafc936922 +size 33788 diff --git a/marked/Rel-16/44_series/44064/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg b/marked/Rel-16/44_series/44064/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4616d3028efa8f1504273ce203fa29680e829a7e --- /dev/null +++ b/marked/Rel-16/44_series/44064/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab0f663faf02fb0ce031ebf5bb284069d621ced827fc440fcd3d207f1eeafa48 +size 32484 diff --git a/marked/Rel-16/44_series/44064/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/44_series/44064/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c4ee191b17e91161fa2cf98fad1fd1f169eec57 --- /dev/null +++ b/marked/Rel-16/44_series/44064/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9cc6de787d97ceff1ab1966ca524713f0e1c16dbc8a96ff521e8fb10f24f06c +size 29155 diff --git a/marked/Rel-16/44_series/44064/3191384ecc1531d40a00140dd21fd781_img.jpg b/marked/Rel-16/44_series/44064/3191384ecc1531d40a00140dd21fd781_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07f82e0fd39a3f4cd6b85d3dc63e9efae66b2504 --- /dev/null +++ b/marked/Rel-16/44_series/44064/3191384ecc1531d40a00140dd21fd781_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7d594cccebda688f593d341b220dbf9532cd1133aa41dacbc7405235d5bf03e +size 9274 diff --git a/marked/Rel-16/44_series/44064/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/marked/Rel-16/44_series/44064/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12c1237f9a5e2c9c6d694cf7f453c567821220e5 --- /dev/null +++ b/marked/Rel-16/44_series/44064/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec88949564709b5088a36f594025054bc35ab2cd2b2a8178c6c67664135bfc5a +size 14284 diff --git a/marked/Rel-16/44_series/44064/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/marked/Rel-16/44_series/44064/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7cb71f4bec186904d85e26e4419bc166def2667 --- /dev/null +++ b/marked/Rel-16/44_series/44064/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc272e98c42ad69ff6e218d6287a0e5858bde3bb8098e0cb01edad36a96689c1 +size 142425 diff --git a/marked/Rel-16/44_series/44064/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-16/44_series/44064/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ccbda1b969340002750adebb556831a862d8009 --- /dev/null +++ b/marked/Rel-16/44_series/44064/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a606e200c05dd44251f9e87d27b708b29fc46859055148be6b9fdd7a6f6e3e7 +size 33101 diff --git a/marked/Rel-16/44_series/44064/48952b53cfa7fc5afa57e46ca69abe1a_img.jpg b/marked/Rel-16/44_series/44064/48952b53cfa7fc5afa57e46ca69abe1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44a56d8959588a02d6b19f4973d9c79143bd49db --- /dev/null +++ b/marked/Rel-16/44_series/44064/48952b53cfa7fc5afa57e46ca69abe1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c20b040745d750418d410ae5696e68d2eaa0c10781fae0d913cd3762649337d +size 40024 diff --git a/marked/Rel-16/44_series/44064/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/44_series/44064/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f8b2c0c8a648f5e8f488352b5381a1e40c4673d --- /dev/null +++ b/marked/Rel-16/44_series/44064/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1912cd99016d8dcbd0c321398853ab2e669e54e15d61f1a678042db95f72a545 +size 89892 diff --git a/marked/Rel-16/44_series/44064/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/marked/Rel-16/44_series/44064/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad7a2d3cdf673a42802693097ce25c1e6e08cae1 --- /dev/null +++ b/marked/Rel-16/44_series/44064/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:900623d8f69f18dc0373e7a1c0a10fc3adfbca55bc87eb52ab117b7e291c0e24 +size 23410 diff --git a/marked/Rel-16/44_series/44064/745261f385368efa3f2259c8681874e9_img.jpg b/marked/Rel-16/44_series/44064/745261f385368efa3f2259c8681874e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c1f7d58b5b7107d1f64566f29022bffc03b6d72 --- /dev/null +++ b/marked/Rel-16/44_series/44064/745261f385368efa3f2259c8681874e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0afdfac3eb4b4e4606c6459e795a58c0e5f25233776c6497b249dd640ab8a643 +size 17207 diff --git a/marked/Rel-16/44_series/44064/7a0e8e669d4b836c1c1cc05dfb8de661_img.jpg b/marked/Rel-16/44_series/44064/7a0e8e669d4b836c1c1cc05dfb8de661_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8c34d3a57a970cdfdeacb0cabe6556086a91f15 --- /dev/null +++ b/marked/Rel-16/44_series/44064/7a0e8e669d4b836c1c1cc05dfb8de661_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:826b496079acf0ca178c90b527a574e90e55895f7cb4ba76ab59d6464c13e677 +size 27655 diff --git a/marked/Rel-16/44_series/44064/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/Rel-16/44_series/44064/82fbb97c1145cac89ac72dd080fad17a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62a02b1dd84818a264d6e77328a38d22f8c4c32c --- /dev/null +++ b/marked/Rel-16/44_series/44064/82fbb97c1145cac89ac72dd080fad17a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb787bd133f846c53485ea269be4e49a73d9aaae6bb3d6608809b1a9df15c764 +size 32597 diff --git a/marked/Rel-16/44_series/44064/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg b/marked/Rel-16/44_series/44064/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b066a0b8f808e37dd51642965962117532d3f3c --- /dev/null +++ b/marked/Rel-16/44_series/44064/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b03580f6eb050c0c452b6fb421c4d42556f144841754dc6b34e4fe134caf59da +size 30242 diff --git a/marked/Rel-16/44_series/44064/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg b/marked/Rel-16/44_series/44064/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7bc40a4620a3b72f755cac70d598745a1eefd6f --- /dev/null +++ b/marked/Rel-16/44_series/44064/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01d96516e5700d6ef8b48cbe17285b51798a40ea0d93509fe0af1a2c645b6b28 +size 34793 diff --git a/marked/Rel-16/44_series/44064/9e6a6c3e99aa474e3abbad752495d9e8_img.jpg b/marked/Rel-16/44_series/44064/9e6a6c3e99aa474e3abbad752495d9e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a44cab70efd28bcbea4887f27c274485a61fe355 --- /dev/null +++ b/marked/Rel-16/44_series/44064/9e6a6c3e99aa474e3abbad752495d9e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d70cd4d3352fe2ea9a036c706850fee8c19e52500692ee8a1a728bb15d4f721 +size 38031 diff --git a/marked/Rel-16/44_series/44064/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/44_series/44064/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64ff753ab08a70d47c3166b65e051493660a62cd --- /dev/null +++ b/marked/Rel-16/44_series/44064/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1151ee91293307d8be45d1f0c1e5609562f670772988e13036eb5d877d4f7bf2 +size 37883 diff --git a/marked/Rel-16/44_series/44064/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/44_series/44064/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a53643e797d6a06650ff7e2b7c7ca87299b8e8a --- /dev/null +++ b/marked/Rel-16/44_series/44064/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:614399441a52c02d38e943a4696162863820d4a76d31d829f048f32a96e2d91e +size 50959 diff --git a/marked/Rel-16/44_series/44064/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/44_series/44064/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e8aef78502fabe38cb590ee4860b0c6309f61ca --- /dev/null +++ b/marked/Rel-16/44_series/44064/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49d6f124d4f4323fd42c39941e3e1ec92e272f0051b6befbce4dbad367430bc6 +size 95612 diff --git a/marked/Rel-16/44_series/44064/raw.md b/marked/Rel-16/44_series/44064/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..04f6b51e6dcc7a5ff81a7f88f6ae5032d14ca2c9 --- /dev/null +++ b/marked/Rel-16/44_series/44064/raw.md @@ -0,0 +1,2687 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 9 | +| 3 Definitions and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations ..... | 11 | +| 4 Overview description of LLC functions and procedures ..... | 11 | +| 4.0 General ..... | 11 | +| 4.1 Reference model..... | 12 | +| 4.2 General description of the LLC protocol ..... | 13 | +| 4.2.0 LLC protocol functions ..... | 13 | +| 4.2.1 Services required by the lower layers..... | 13 | +| 4.3 Unacknowledged operation..... | 13 | +| 4.4 Acknowledged operation..... | 14 | +| 4.5 Establishment of information transfer modes ..... | 14 | +| 4.5.1 Data link connection identification..... | 14 | +| 4.5.2 Logical link states..... | 14 | +| 4.5.3 TLLI assignment ..... | 14 | +| 4.5.4 Establishment of ABM operation..... | 14 | +| 4.6 Data confidentiality ..... | 15 | +| 4.6a Integrity protection ..... | 15 | +| 4.7 LLC layer structure ..... | 16 | +| 4.7.0 General ..... | 16 | +| 4.7.1 Logical Link Entity..... | 16 | +| 4.7.2 Multiplex procedure ..... | 17 | +| 4.7.3 Logical Link Management ..... | 17 | +| 4.8 GPRS Mobility Management..... | 17 | +| 4.9 Short Message Service ..... | 17 | +| 4.10 Tunnelling Of Messages..... | 17 | +| 5 Frame structure ..... | 17 | +| 5.1 General ..... | 17 | +| 5.2 Address field ..... | 18 | +| 5.3 Control field ..... | 18 | +| 5.4 Information field ..... | 18 | +| 5.5 Frame Check Sequence (FCS) field..... | 19 | +| 5.5a Message Authentication Code (MAC) field..... | 19 | +| 5.6 Transparency ..... | 19 | +| 5.6.1 Bit transparency..... | 19 | +| 5.6.2 Information protection ..... | 19 | +| 5.6.3 Octet alignment ..... | 20 | +| 5.7 Format convention..... | 20 | +| 5.7.1 Numbering convention ..... | 20 | +| 5.7.2 Order of transmission ..... | 20 | +| 5.7.3 Field mapping convention ..... | 20 | +| 5.8 Invalid frames..... | 21 | +| 6 Elements of procedures and formats of fields..... | 21 | +| 6.1 General ..... | 21 | +| 6.2 Address field format and variables..... | 21 | +| 6.2.0 Address field format..... | 21 | +| 6.2.1 Protocol Discriminator bit (PD) ..... | 22 | +| 6.2.2 Command/Response bit (C/R)..... | 22 | +| 6.2.3 Service Access Point Identifier (SAPI) ..... | 22 | +| 6.3 Control field formats, parameters, and variables ..... | 23 | +| 6.3.0 Control field formats ..... | 23 | +| 6.3.1 Information transfer format - I..... | 24 | + +| | | | +|-----------|---------------------------------------------------------------|----| +| 6.3.2 | Supervisory format - S..... | 24 | +| 6.3.3 | Unconfirmed Information format - UI..... | 24 | +| 6.3.4 | Unnumbered format - U ..... | 25 | +| 6.3.5 | Control field parameters and associated state variables ..... | 25 | +| 6.3.5.1 | Poll/Final bit (P/F) ..... | 25 | +| 6.3.5.2 | Acknowledgement request bit (A)..... | 25 | +| 6.3.5.2a | Integrity Protection bit (IP)..... | 25 | +| 6.3.5.3 | Modulus ..... | 25 | +| 6.3.5.4 | ABM variables and sequence numbers..... | 25 | +| 6.3.5.4.1 | Send state variable V(S)..... | 25 | +| 6.3.5.4.2 | Acknowledge state variable V(A)..... | 25 | +| 6.3.5.4.3 | Send sequence number N(S) ..... | 26 | +| 6.3.5.4.4 | Receive state variable V(R)..... | 26 | +| 6.3.5.4.5 | Receive sequence number N(R)..... | 26 | +| 6.3.5.4.6 | SACK bitmap R(n)..... | 26 | +| 6.3.5.4.7 | I frame buffer variable B..... | 26 | +| 6.3.5.4.8 | Other parameters and variables..... | 26 | +| 6.3.5.5 | Unacknowledged operation variables and parameters..... | 27 | +| 6.3.5.5.1 | Encryption mode bit (E)..... | 27 | +| 6.3.5.5.2 | Protected Mode bit (PM)..... | 27 | +| 6.3.5.5.3 | Unconfirmed send state variable V(U)..... | 27 | +| 6.3.5.5.4 | Unconfirmed sequence number N(U) ..... | 27 | +| 6.3.5.5.5 | Unconfirmed receive state variable V(UR)..... | 27 | +| 6.3.5.5.6 | Other parameters and variables..... | 27 | +| 6.4 | Commands and responses ..... | 27 | +| 6.4.1 | General ..... | 27 | +| 6.4.1 | Unnumbered (U) frames..... | 28 | +| 6.4.1.1 | Set Asynchronous Balanced Mode (SABM) command ..... | 28 | +| 6.4.1.2 | Disconnect (DISC) command..... | 28 | +| 6.4.1.3 | Unnumbered Acknowledgement (UA) response ..... | 28 | +| 6.4.1.4 | Disconnected Mode (DM) response ..... | 29 | +| 6.4.1.5 | Frame Reject (FRMR) response ..... | 29 | +| 6.4.1.6 | Exchange Identification (XID) command/response ..... | 30 | +| 6.4.1.7 | NULL command ..... | 33 | +| 6.4.2 | Unconfirmed Information (UI) frame..... | 33 | +| 6.4.2.1 | Unconfirmed Information (UI) command ..... | 33 | +| 6.4.2.2 | Unconfirmed Information (UI) Dummy command ..... | 33 | +| 6.4.3 | Combined Information (I) and Supervisory (S) frames..... | 34 | +| 6.4.3.1 | Receive Ready (RR) command / response ..... | 34 | +| 6.4.3.2 | Acknowledgement (ACK) command / response ..... | 34 | +| 6.4.3.3 | Selective Acknowledgement (SACK) command / response ..... | 34 | +| 6.4.3.4 | Receive Not Ready (RNR) command / response..... | 35 | +| 7 | Elements for layer-to-layer communication ..... | 35 | +| 7.1 | Definition of service primitives and parameters ..... | 35 | +| 7.1.0 | General ..... | 35 | +| 7.1.1 | Primitives types ..... | 35 | +| 7.1.1.1 | Request..... | 35 | +| 7.1.1.2 | Indication ..... | 35 | +| 7.1.1.3 | Response ..... | 35 | +| 7.1.1.4 | Confirm..... | 36 | +| 7.1.2 | LLC layer service primitives ..... | 36 | +| 7.2 | Primitive procedures ..... | 37 | +| 7.2.1 | GMM - LLME primitives..... | 37 | +| 7.2.1.1 | LLGMM-ASSIGN..... | 37 | +| 7.2.1.2 | LLGMM-RESET ..... | 38 | +| 7.2.1.3 | LLGMM-TRIGGER..... | 38 | +| 7.2.1.4 | LLGMM-SUSPEND ..... | 38 | +| 7.2.1.5 | LLGMM-RESUME ..... | 39 | +| 7.2.1.6 | LLGMM-PAGE..... | 39 | +| 7.2.1.7 | LLGMM-IOV ..... | 39 | +| 7.2.1.8 | LLGMM-STATUS ..... | 39 | + +| | | | +|----------|-----------------------------------------------------------------|----| +| 7.2.1.9 | LLGMM-PSHO ..... | 39 | +| 7.2.1.10 | LLGMM-ASSIGN-USERPLANE ..... | 39 | +| 7.2.2 | Layer 3 - LLE primitives ..... | 40 | +| 7.2.2.1 | LL-RESET ..... | 40 | +| 7.2.2.2 | LL-ESTABLISH ..... | 40 | +| 7.2.2.3 | LL-RELEASE ..... | 40 | +| 7.2.2.4 | LL-XID ..... | 40 | +| 7.2.2.5 | LL-DATA ..... | 40 | +| 7.2.2.6 | LL-UNITDATA ..... | 40 | +| 7.2.2.7 | LL-STATUS ..... | 41 | +| 7.2.3 | LLE - RLC/MAC primitives ..... | 41 | +| 7.2.3.0 | General ..... | 41 | +| 7.2.3.1 | GRR-DATA ..... | 41 | +| 7.2.3.2 | GRR-UNITDATA ..... | 41 | +| 7.2.4 | LLE - BSSGP primitives ..... | 41 | +| 7.2.4.0 | General ..... | 41 | +| 7.2.4.1 | BSSGP-DL-UNITDATA ..... | 42 | +| 7.2.4.2 | BSSGP-UL-UNITDATA ..... | 42 | +| 7.2.5 | LLME - LLE primitives ..... | 42 | +| 8 | Definition of the LLC peer-to-peer protocol ..... | 42 | +| 8.1 | General ..... | 42 | +| 8.2 | Procedure for the use of the P/F bit ..... | 43 | +| 8.3 | TLLI assignment procedures ..... | 43 | +| 8.3.0 | General ..... | 43 | +| 8.3.1 | TLLI assignment ..... | 43 | +| 8.3.2 | TLLI change ..... | 43 | +| 8.3.3 | TLLI unassignment ..... | 44 | +| 8.4 | Procedures for unacknowledged information transfer ..... | 44 | +| 8.4.0 | General ..... | 44 | +| 8.4.1 | Transmission of unacknowledged information ..... | 44 | +| 8.4.2 | Receipt of unacknowledged information ..... | 44 | +| 8.5 | Procedures for establishment and release of ABM operation ..... | 45 | +| 8.5.1 | Establishment of ABM operation ..... | 45 | +| 8.5.1.1 | General ..... | 45 | +| 8.5.1.2 | Establishment procedures ..... | 45 | +| 8.5.1.3 | Procedure on expiry of timer T200 ..... | 46 | +| 8.5.2 | Termination of ABM operation ..... | 46 | +| 8.5.2.1 | General ..... | 46 | +| 8.5.2.2 | Release procedure ..... | 47 | +| 8.5.2.3 | Procedure on expiry of timer T200 ..... | 47 | +| 8.5.3 | Automatic negotiation of LLC layer and layer-3 parameters ..... | 47 | +| 8.5.3.0 | General ..... | 47 | +| 8.5.3.1 | Negotiation of parameter Reset ..... | 48 | +| 8.5.3.2 | Negotiation of parameter m ..... | 49 | +| 8.5.3.3 | Unsuccessful XID negotiation ..... | 49 | +| 8.5.3.4 | Procedure on expiry of timer T200 ..... | 50 | +| 8.5.4 | TLLI Assigned / ADM state ..... | 50 | +| 8.5.5 | Collision of unnumbered commands ..... | 51 | +| 8.5.5.0 | General ..... | 51 | +| 8.5.5.1 | Identical transmitted and received commands ..... | 51 | +| 8.5.5.2 | Different transmitted and received commands ..... | 52 | +| 8.5.6 | Unsolicited DM response and SABM or DISC command ..... | 52 | +| 8.6 | Procedures for information transfer in ABM operation ..... | 52 | +| 8.6.0 | General ..... | 52 | +| 8.6.1 | Transmitting I frames ..... | 53 | +| 8.6.2 | Receiving I frames ..... | 53 | +| 8.6.3 | Sending and receiving acknowledgements ..... | 54 | +| 8.6.3.0 | General ..... | 54 | +| 8.6.3.1 | Sending acknowledgements ..... | 54 | +| 8.6.3.2 | Receiving acknowledgements ..... | 54 | +| 8.6.3.3 | Requesting acknowledgements ..... | 55 | + +| | | | +|-------------------------------|---------------------------------------------------------------|-----------| +| 8.6.4 | Peer receiver busy condition ..... | 55 | +| 8.6.4.1 | Supervisory frame selection..... | 56 | +| 8.6.5 | Own receiver busy condition..... | 56 | +| 8.6.6 | Waiting for acknowledgement..... | 56 | +| 8.7 | Re-establishment of ABM operation..... | 56 | +| 8.7.1 | Criteria for re-establishment..... | 56 | +| 8.7.2 | Procedures ..... | 57 | +| 8.8 | Exception condition reporting and recovery ..... | 57 | +| 8.8.0 | General ..... | 57 | +| 8.8.1 | Invalid frame condition ..... | 57 | +| 8.8.2 | Frame rejection condition..... | 57 | +| 8.8.3 | Receipt of a FRMR response frame ..... | 57 | +| 8.8.4 | Unsolicited response frames..... | 58 | +| 8.9 | List of LLC layer parameters ..... | 58 | +| 8.9.0 | General ..... | 58 | +| 8.9.1 | LLC version number (Version) ..... | 58 | +| 8.9.2 | Input Offset Values (IOV)..... | 58 | +| 8.9.3 | Retransmission timers (T200 and T201)..... | 59 | +| 8.9.4 | Maximum number of retransmissions (N200) ..... | 59 | +| 8.9.5 | Maximum number of octets in an information field (N201) ..... | 59 | +| 8.9.6 | Maximum number of octets in the layer-3 header (N202)..... | 60 | +| 8.9.7 | Maximum I frame buffer size (m) ..... | 60 | +| 8.9.8 | Maximum number of outstanding I frames (k) ..... | 60 | +| 8.9.9 | LLC layer parameter default values ..... | 61 | +| Annex A (normative): | Ciphering..... | 62 | +| A.1 | General..... | 62 | +| A.2 | Ciphering algorithm interface ..... | 62 | +| A.2.0 | General ..... | 62 | +| A.2.1 | Generation of Input ..... | 63 | +| Annex B (normative): | Tunnelling of Messages (TOM)..... | 64 | +| B.1 | TOM Protocol Envelope structure ..... | 64 | +| B.1.0 | TOM Protocol Envelope format..... | 64 | +| B.1.1 | TOM Protocol Discriminator ..... | 65 | +| B.1.2 | Remaining Length of TOM Protocol Header..... | 65 | +| B.1.3 | Remaining Octets of TOM Protocol Header..... | 65 | +| B.1.4 | Message Capsule..... | 65 | +| Annex C (informative): | LLC layer states for peer-to-peer operation..... | 66 | +| C.1 | General..... | 66 | +| C.2 | An overview of the peer-to-peer LLC layer states..... | 66 | +| Annex D (informative): | Change History..... | 68 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the Logical Link Control (LLC) layer protocol to be used for packet data transfer between the Mobile Station (MS) and Serving GPRS Support Node (SGSN). + +It defines the frame structure, elements of procedure, format of fields, and procedures for the proper operation of the logical link control layer. It is based on ideas contained in IS-130 [21], ISO 3309 [16], ISO 4335 [17], and ISO 7809 [18, 19, 20] (HDLC of ISO), as well ITU-T Q.920 [13] and Q.921 [14] (LAPD). The concepts, the overview description of LLC layer functions and procedures, and the relationship with other Technical Specifications are described in general terms in 3GPP TS 23.060 [5]. + +LLC spans from the Mobile Station (MS) to the Serving GPRS Support Node (SGSN). LLC is intended for use with both acknowledged and unacknowledged data transfer. + +The frame formats defined for LLC are based on those defined for LAPD and RLP. However, there are important differences between LLC and other protocols, in particular with regard to frame delimitation methods and transparency mechanisms. These differences are necessary for independence from the radio path. + +The LLC procedures are modelled upon the concepts of HDLC as outlined in ISO 4335. Data sequence integrity between the data source and data sink is effected by means of a cyclic numbering scheme. An independent numbering scheme is used for each logical data link, as identified by the a data link connection identifier. LLC supports two modes of operation: + +- Unacknowledged peer-to-peer operation: + +A logical link entity may initiate transmissions to a peer entity without prior establishment of a logical connection with the peer entity. LLC does not guarantee in-order delivery. LLC can detect errors in a received frame, and, depending on whether the frame is sent in protected mode or not, either discard or deliver the erroneous frame. No error recovery procedures are defined at the LLC layer. Higher-layer protocols can be used to provide reliability, if needed. This mode of operation is known as Asynchronous Disconnected Mode (ADM). + +- Acknowledged peer-to-peer operation: + +A balanced data link involves two participating entities, and each entity assumes responsibility for the organisation of its data flow and for error recovery procedures associated with the transmissions that it originates. Each entity operates as both a data source and data sink in a balanced link, allowing information to flow in both directions. This mode of operation is known as Asynchronous Balanced Mode (ABM), and provides a reliable service with in-order delivery. + +In unacknowledged operation, LLC can provide integrity protection. + +The present document is organised as follows: + +- An overview of the LLC layer functions is given in clause 4. +- The frame structure for peer-to-peer communication is given in clause 5. +- The elements of procedure and formats of fields are given in clause 6. +- The elements of layer-to-layer communication are contained in clause 7. +- The details of the peer-to-peer ABM procedures are given in clause 8. +- The details of LLC frame ciphering are given in annex A. +- The details of the TOM protocol layer are contained in annex B. +- An overview of the LLC layer states is provided in annex C. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 41.061: "General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements". +- [3] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [3a] 3GPP TS 23.003: "Numbering, addressing and identification". +- [4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS); Point-to-Point (PP)". +- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [5a] 3GPP TS 23.251: "Network Sharing; Architecture and Functional Description". +- [6] 3GPP TS 43.064: "General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2". +- [7] 3GPP TS 44.001: "Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles". +- [8] 3GPP TS 44.018: "Mobile radio interface; Layer 3 specification; Radio Resource Control Protocol". +- [8a] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3". +- [9] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [10] 3GPP TS 24.022: "Radio Link Protocol (RLP) for circuit switched bearer and teleservices". +- [11] 3GPP TS 44.065: "General Packet Radio Service (GPRS); Mobile Station (MS) – Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)". +- [12] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [13] ITU-T Recommendation Q.920 (1988): "ISDN user-network interface data link layer - General aspects". +- [14] ITU-T Recommendation Q.921 (1988): "ISDN user-network interface - Data link layer specification". +- [15] ITU-T Recommendation Z.100 (1988): "CCITT specification and description language (SDL)". +- [16] ISO 3309 (1984): "Information processing systems - Data communications - High-level data link control procedure - Frame structure". +- [17] ISO 4335 (1987): "Information processing systems – Data communication – High-level logical link control procedures – Consolidation of elements of procedures". + +- [18] ISO 7809 (1984): "Information processing systems – Data communication – High-level logical link control procedures – Consolidation of classes of procedures". +- [19] ISO 7809 (1984): "Information processing systems – Data communication Add. 1: 1987 – High-level logical link control procedures – Consolidation of classes of procedures – Addendum 1". +- [20] ISO 7809 (1984): "Information processing systems – Data communication Add. 2: 1987 – High-level logical link control procedures – Consolidation of classes of procedures – Addendum 2: Description of optional functions". +- [21] TIA IS-130 (1995): "800 MHz Cellular System – TDMA Radio Interface – Radio Link Protocol 1" Arlington: Telecommunications Industry Association. +- [22] TIA/EIA-136 (1999): "TDMA Cellular / PCS"; Arlington: Telecommunications Industry Association. +- [23] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [23a] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) – Visitors Location Register (VLR); Gs interface layer 3 specification". +- [24] 3GPP TS 44.031: "Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP)". +- [25] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services (LCS) in GERAN". +- [26] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2". +- [27] 3GPP TS 43.020: "Security-related network functions" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 21.905 [1] and 3GPP TS 22.060 [3] and the following apply: + +**active LLE:** an LLE which SAPI is assigned to a layer-3 entity. + +**empty XID command:** an XID command sent by the SGSN which does not contain parameters to negotiate. + +**frame rejection condition:** a condition that results from the receipt of an undefined or incorrect frame. + +**inquiry process:** a process performed in the peer receiver busy condition in which the LLE checks that the peer LLE is still in the own receiver busy condition. + +**invalid frame condition:** a condition that results from the receipt of an invalid frame. + +**logical link connection:** the logical connection between two LLE peers. A logical link connection is identified with a Data Link Connection Identifier (DLCI). A logical link connection is always in one of three states: TLLI Unassigned, TLLI Assigned / ADM, or ABM. + +**logical link control layer:** the protocol layer between an MS and an SGSN consisting of one or more logical link management entities, one or more logical link entities, and a multiplex procedure. + +**logical link entity:** the LLC layer protocol state machine controlling one logical link connection. + +**own receiver busy condition:** a condition that results from the inability to accept additional I frames from the peer logical link entity. + +**peer receiver busy condition:** a condition that results from the reception in of a RNR frame from the peer logical link entity. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.251 [5a] apply: + +### Multi-Operator Core Network + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 [1] and 3GPP TS 23.060 [5], and the following apply: + +| | | +|-------------------|------------------------------------------------------| +| ABM | Asynchronous Balanced Mode | +| ACK | ACKnowledgement | +| ADM | Asynchronous Disconnected Mode | +| CNF | CoNFirm | +| DISC | DISConnect | +| DM | Disconnected Mode | +| FCS field | Frame Check Sequence field | +| FRMR | FRaMe Reject | +| GMM | GPRS Mobility Management | +| GRR | GPRS Radio Resources service access point | +| I | Information | +| IND | INDication | +| IOV | Input Offset Value | +| Kc | 64-bit ciphering key | +| Kc 128 | 128-bit ciphering key | +| LAPD | Link Access Procedure on the D-channel | +| LCS | Location Services | +| LL | Logical Link | +| LLC | Logical Link Control | +| LLE | Logical Link Entity | +| LLGMM | LLC to GPRS Mobility Management service access point | +| LLM | Logical Link Management | +| LLME | Logical Link Management Entity | +| MAC layer | Medium Access Control layer | +| MAC field | Message Authentication Code field | +| MOCN | Multi-Operator Core Network | +| REQ | REQuest | +| RES | RESponse | +| RLC layer | Radio Link Control layer | +| RNR | Receive Not Ready | +| RR | Receive Ready | +| RRLP | Radio Resource LCS Protocol | +| S | Supervisory | +| SABM | Set Asynchronous Balanced Mode | +| SACK | Selective ACKnowledgement | +| TIA | Telecommunications Industry Association | +| TOM | Tunnelling Of Messages | +| UA | Unnumbered Acknowledgement | +| UI | Unconfirmed Information | +| XID | eXchange IDEntification | + +# --- 4 Overview description of LLC functions and procedures + +## 4.0 General + +The requirements of the LLC layer can be summarised as follows: + +- LLC shall provide a highly reliable logical link between the MS and the SGSN. +- LLC shall be independent of the underlying radio interface protocols in order to allow introduction of alternative GPRS radio solutions with minimal change to the NSS. + +- LLC shall support variable-length information frames. +- LLC shall support peer-to-peer data transfers. +- LLC shall support both acknowledged and unacknowledged data transfers. +- LLC shall permit information transfer between the SGSN and one or more MSs using the same physical (e.g. radio) resources. Thus each LLC frame shall uniquely identify the MS sending (uplink) or receiving (downlink) the information. +- LLC shall allow information transfer with different service criteria, such that high-priority data transfers may take precedence over lower-priority transfers to the same MS. +- LLC shall provide user data confidentiality by means of a ciphering function. +- LLC shall support user identity confidentiality. +- LLC may support integrity protection. + +## 4.1 Reference model + +A model of layering the protocols in GPRS is illustrated in figure 1. + +![Figure 1: Protocol layering in GPRS. The diagram shows three main entities: MS (Mobile Station), BSS (Base Station System), and SGSN (SGSN). The MS has layers: TOM, GMM, SNDC, SMS at the top; LLC below; RLC below LLC; MAC below RLC; GSM RF at the bottom. The BSS has layers: Relay (containing RLC and BSSGP) at the top; MAC below Relay; GSM RF below MAC; L1 at the bottom. The SGSN has layers: TOM, GMM, SNDC, SMS at the top; LLC below; BSSGP below LLC; Network Service below BSSGP; L1 at the bottom. Interfaces are shown: Um between MS and BSS, and Gb between BSS and SGSN. Vertical dashed lines separate the entities.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +Figure 1: Protocol layering in GPRS. The diagram shows three main entities: MS (Mobile Station), BSS (Base Station System), and SGSN (SGSN). The MS has layers: TOM, GMM, SNDC, SMS at the top; LLC below; RLC below LLC; MAC below RLC; GSM RF at the bottom. The BSS has layers: Relay (containing RLC and BSSGP) at the top; MAC below Relay; GSM RF below MAC; L1 at the bottom. The SGSN has layers: TOM, GMM, SNDC, SMS at the top; LLC below; BSSGP below LLC; Network Service below BSSGP; L1 at the bottom. Interfaces are shown: Um between MS and BSS, and Gb between BSS and SGSN. Vertical dashed lines separate the entities. + +**Figure 1: Protocol layering in GPRS** + +The LLC layer operates above the RLC and BSSGP layers in the reference architecture to provide logical links between an MS and its SGSN. + +Above the LLC layer is located the SubNetwork Dependent Convergence (SNDC) layer, that controls the transfer of user data network layer PDUs (N-PDUs) between the MS and SGSN. The SNDC functionality is described in 3GPP TS 23.060 [5] and specified in 3GPP TS 44.065 [11]. + +The logical link control layer Service Access Points (SAPs) are the points at which the LLC layer provides services to the layer-3 protocols in figure 1. In addition to the SNDC protocol, LLC provides service to the GPRS Mobility Management (GMM) protocol, to the SMS protocol, and to the Tunnelling of Messages (TOM) protocol. + +An LLC layer connection is identified by the DLCI consisting of the SAP Identifier (SAPI) and the MS's Temporary Logical Link Identifier (TLLI). + +Each LLC frame consists of the header, trailer, and information field. The header and trailer fields contain information such as SAPI, frame number and checksum, that are used to identify the frame and to provide reliable transmission. The information field is variable length. Both transmission and retransmission of each frame are controlled by the LLC layer. + +Many of the formats and procedures are similar to the reference protocols, and differences are introduced only where needed to reflect the unique aspects of the GPRS architecture and requirements. + +## 4.2 General description of the LLC protocol + +### 4.2.0 LLC protocol functions + +LLC is considered to be a sublayer of layer 2 in the ISO 7-layer model. The purpose of LLC is to convey information between layer-3 entities in the MS and SGSN. Specifically, LLC shall support: + +- multiple MSs at the Um interface; +- multiple layer-3 entities within an MS. + +LLC includes functions for: + +- the provision of one or more logical link connections discriminated between by means of a DLCI; +- sequence control, to maintain the sequential order of frames across a logical link connection; +- detection of transmission, format and operational errors on a logical link connection; +- recovery from detected transmission, format, and operational errors; +- notification of unrecoverable errors; +- flow control; +- ciphering; and +- integrity protection. + +LLC layer functions provide the means for information transfer via peer-to-peer logical link connections between an MS and SGSN pair. + +### 4.2.1 Services required by the lower layers + +LLC requires the following services from the layers below: + +- LLC PDU delimitation to allow the LLC layer to determine the first octet and the last octet in each LLC PDU; and +- transport of the MS address (a TLLI) of each LLC PDU between the MS and the SGSN. + +To "transmit a frame" and "send a frame" refers to the delivery of a frame by the LLC layer to the layer below. + +## 4.3 Unacknowledged operation + +With this type of operation, layer-3 information is transmitted in numbered Unconfirmed Information (UI) frames. The UI frames are not acknowledged at the LLC layer. Neither error recovery nor reordering mechanisms are defined, but transmission and format errors are detected. Duplicate UI frames are discarded. + +Flow control procedures are not defined. + +Two modes of unacknowledged operation are defined: + +- protected mode in which the FCS field protects the frame header and information field, including the MAC field, if any; and +- unprotected mode in which the FCS field protects the frame header and only the first N202 octets of the information field, including the MAC field, if any. + +The MAC field, when used, protects the frame header and the information field. Unacknowledged operation is allowed for all SAPs that are not reserved (see table 2). + +## 4.4 Acknowledged operation + +With this type of operation, layer-3 information is transmitted in order in numbered Information (I) frames. The I frames are acknowledged at the LLC layer. Error recovery and reordering procedures based on retransmission of unacknowledged I frames are specified. Several I frames may be unacknowledged at the same time. In the case of errors that cannot be corrected by the logical link control layer, a report to GPRS mobility management shall be made. + +Flow control procedures are defined. + +Acknowledged operation requires that ABM operation has been initiated by an establishment procedure using the Set Asynchronous Balanced Mode (SABM) command. + +Acknowledged operation is allowed for all SAPIs that are not reserved (see table 2) except SAPIs 1, 2, 7, and 8. + +## 4.5 Establishment of information transfer modes + +### 4.5.1 Data link connection identification + +A logical link connection is identified by a DLCI consisting of two identifiers: a SAPI and a TLLI. + +The SAPI is used to identify the service access point on the SGSN side and the MS side of the LLC interface. SAPI is carried in the address field of each LLC frame. + +The TLLI is used to identify a specific MS. TLLI assignment is controlled by GMM. TLLI is not carried in LLC frames, but in BSSGP messages as defined in 3GPP TS 48.018 [12], and in RLC/MAC layer blocks as defined in 3GPP TS 44.018 [8]. + +### 4.5.2 Logical link states + +A logical link entity may be in one of three basic states: + +- TLLI Unassigned state: information transfer shall not be possible with the following exception: the SGSN shall be able to receive UI and XID frames for SAPI = 1; +- TLLI Assigned / ADM state: in this state a TLLI has been assigned. Unacknowledged information transfer and XID negotiation shall be possible on SAPIs that are assigned to a layer-3 entity; or +- ABM state: this state shall be established by means of an ABM establishment procedure. Both acknowledged and unacknowledged information transfer shall be possible. + +The basic states and additional states are shown in annex C. + +### 4.5.3 TLLI assignment + +TLLI assignment is controlled by GMM. TLLIs are assigned, changed, and unassigned with the LLGMM-ASSIGN-REQ primitive, as described in subclause 7.2.1.1. + +### 4.5.4 Establishment of ABM operation + +Before peer-to-peer acknowledged information transfer can start, an exchange of a SABM frame and an Unnumbered Acknowledgement (UA) frame shall take place. The ABM establishment procedure is specified in clause 8. + +## 4.6 Data confidentiality + +The LLC layer shall provide data confidentiality by ciphering the information and FCS fields of data frames: + +- The information and FCS fields of I frames shall be ciphered whenever ciphering information has been assigned to the TLLI. +- The information field (including the MAC field if integrity protection is used) and the FCS field of UI frames shall be ciphered whenever layer 3 indicates that the UI frame shall be ciphered and ciphering information has been assigned to the TLLI. + +For details and usage of ciphering, see Annex A. + +## 4.6a Integrity protection + +The LLC layer may provide integrity protection of the frame header and the information field of data frames: + +- The frame header and the information field of UI frames shall be integrity protected whenever layer 3 indicates that the UI frame shall be integrity protected and integrity protection information has been assigned to the TLLI. + +For details and usage of integrity protection, see 3GPP TS 43.020 [27]. + +## 4.7 LLC layer structure + +### 4.7.0 General + +The LLC layer structure is shown in figure 2. This figure is a model shown for illustrative purposes only, and does not constrain implementations. + +![Figure 2: Functional model of the LLC layer. The diagram shows the LLC layer structure between Layer 3 and the RLC/MAC layer. Layer 3 includes GPRS Mobility Management, SNDCP, TOM, and SMS. The LLC layer contains Logical Link Management Entity, Logical Link Entities (SAPI=1, 3, 5, 7, 8, 9, 11, 2), and a Multiplex Procedure. The RLC/MAC layer includes RLC/MAC and BSSGP. The diagram is split into MS (Mobile Station) and SGSN (Serving GPRS Support Node) sections. A legend indicates that dashed lines represent Signalling and solid lines represent Signalling and data transfer.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +The diagram illustrates the functional model of the LLC layer. At the top, Layer 3 protocols are shown: GPRS Mobility Management, SNDCP, TOM, and SMS. Below Layer 3, the LLC layer is depicted. On the left, the Logical Link Management Entity is shown. On the right, multiple Logical Link Entities (LLEs) are shown, each associated with a specific SAPI (Service Access Point Identifier): SAPI=1, SAPI=3, SAPI=5, SAPI=7, SAPI=8, SAPI=9, SAPI=11, and SAPI=2. These LLEs connect to a common Multiplex Procedure. Below the Multiplex Procedure, the LLC layer connects to the RLC/MAC layer. The diagram is divided into two main sections: MS (Mobile Station) on the left and SGSN (Serving GPRS Support Node) on the right. The MS section includes the RLC/MAC layer, and the SGSN section includes the BSSGP layer. A legend at the bottom indicates that dashed lines represent Signalling and solid lines represent Signalling and data transfer. + +Figure 2: Functional model of the LLC layer. The diagram shows the LLC layer structure between Layer 3 and the RLC/MAC layer. Layer 3 includes GPRS Mobility Management, SNDCP, TOM, and SMS. The LLC layer contains Logical Link Management Entity, Logical Link Entities (SAPI=1, 3, 5, 7, 8, 9, 11, 2), and a Multiplex Procedure. The RLC/MAC layer includes RLC/MAC and BSSGP. The diagram is split into MS (Mobile Station) and SGSN (Serving GPRS Support Node) sections. A legend indicates that dashed lines represent Signalling and solid lines represent Signalling and data transfer. + +Figure 2: Functional model of the LLC layer + +### 4.7.1 Logical Link Entity + +The logical link procedures consist of multiple Logical Link Entities (LLEs) that control the information flow of individual connections. There may be multiple LLEs per TLLI. Functions provided by each LLE are: + +- unacknowledged information transfer; + +- acknowledged information transfer; +- flow control in ABM operation; +- frame error detection; and +- integrity protection (in unacknowledged information transfer). + +The LLE analyses the control field of the received frame (see subclause 6.3) and provides appropriate responses and layer-to-layer indications. In addition, LLE analyses the LLC layer service primitives and transmits the appropriate command and response frames. There is one logical link entity for each DLCI. + +### 4.7.2 Multiplex procedure + +On frame transmission, the multiplex procedure generates and inserts the FCS field and the MAC field if integrity protection is used, performs the frame ciphering function, and provides SAPI-based logical link control layer contention resolution between the various LLEs. + +On frame reception, the multiplex procedure performs the frame decipher function and checks the FCS field and the MAC field if integrity protection is used. If the frame passes the FCS field and the MAC field checks, the multiplex procedure distributes the frame to the appropriate logical link entity based on the DLCI. + +3GPP TS 41.061 [2] contains the requirements for the GPRS ciphering algorithm. + +### 4.7.3 Logical Link Management + +The Logical Link Management Entity (LLME) manages the resources that have an impact on individual connections. There is one LLME per TLLI. Functions provided by the LLME are: + +- parameter initialisation; +- error processing; and +- connection flow control invocation. + +The RLC/MAC layer functions are described in 3GPP TS 43.064 [6]. BSSGP is specified in 3GPP TS 48.018 [12]. SNDPCP is specified in 3GPP TS 44.065 [11]. + +## 4.8 GPRS Mobility Management + +GPRS Mobility Management (GMM) uses the services of the LLC layer to transfer messages between the MS and the SGSN. GMM includes functions such as attach and authentication, and transport of session management messages for functions such as PDP context activation and deactivation. GMM procedures are defined in 3GPP TS 24.008 [8a] and are beyond the scope of the LLC layer. Interaction between GMM and LLC is defined in terms of service primitives, see clause 7. + +## 4.9 Short Message Service + +The Short Message Service (SMS) uses the services of the LLC layer to transfer short messages between the MS and the SGSN. SMS procedures are defined in 3GPP TS 23.040 [4] and 3GPP TS 24.011 [9] and are beyond of the scope of the LLC layer. Interaction between SMS and LLC is defined in terms of service primitives, see clause 7. + +## 4.10 Tunnelling Of Messages + +TOM is a generic protocol layer used for the exchange of TOM Protocol Envelopes between the MS and the SGSN. TOM procedures are defined in annex B. + +# 5 Frame structure + +## 5.1 General + +All logical link control layer peer-to-peer exchanges shall be in frames conforming to the format shown in figure 3 and figure 3a. The frame header shall consist of the address and control fields, and is a minimum of 2 octets and a maximum of 37 octets long. + +![](21ad58fee90f2be50708ff541d225507_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------------------------------------|---|---|---|---|---|---|---| +| Address field (1 octet) | | | | | | | | +| Control field
(variable length, max. 36 octets) | | | | | | | | +| Information field
(variable length, max. N201 octets) | | | | | | | | +| Frame Check Sequence field
(3 octets) | | | | | | | | + +**Figure 3: LLC frame format** + +![](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|------------------------------------------------------------|---|---|---|---|---|---|---| +| Address field (1 octet) | | | | | | | | +| Control field (2 octets) | | | | | | | | +| Information field
(variable length, max. N201-4 octets) | | | | | | | | +| Message Authentication Code field
(4 octets) | | | | | | | | +| Frame Check Sequence field
(3 octets) | | | | | | | | + +**Figure 3a: LLC frame format with integrity protection** + +NOTE: For an LLC frame with integrity protection, the MAC field is included in the information field. When the MAC field is included in the message, the maximum length of the integrity protected message is N201 – 4 octets. + +## 5.2 Address field + +The address field consists of a single octet. The address field contains the SAPI and identifies the DLCI for which a downlink frame is intended and the DLCI transmitting an uplink frame. The format of the address field is defined in subclause 6.2. + +## 5.3 Control field + +The control field typically consists of between one and three octets. The SACK supervisory frame also includes a variable-length bitmap field of up to 32 octets. The format of the control field is defined in subclause 6.3. + +## 5.4 Information field + +The information field of a frame, when present, follows the control field (see subclause 6.4). The maximum number of octets in the information field (N201) is defined in subclause 8.9.5. + +## 5.5 Frame Check Sequence (FCS) field + +The FCS field shall consist of a 24 bit cyclic redundancy check (CRC) code. The CRC-24 is used to detect bit errors in the frame header and information fields. + +The FCS field contains the value of a CRC calculation that is performed over the entire contents of the header and information field, except for UI frames transmitted in unprotected mode, in which case the FCS field contains the value of a CRC calculation that is performed over the frame header and the first N202 octets (see subclause 8.9.6) of the information field only (see subclause 6.3.5.5.2). The information over which the CRC is calculated is referred to as the dividend in this subclause. Bit (1, 1) of the dividend is the highest-order term in the calculation (see subclause 5.7.3). CRC calculation shall be done before ciphering at the transmitting side, and after deciphering at the receiving side. + +NOTE: The definition below is different from that in 3GPP TS 24.022 [10] only with respect to the variable dividend length $k$ of the LLC frames. In 3GPP TS 24.022, the RLP frame has a fixed dividend length, but the LLC frame has a variable dividend length. + +The CRC shall be the ones complement of the sum (modulo 2) of: + +- the remainder of $x^k (x^{23} + x^{22} + x^{21} + \dots + x^2 + x + 1)$ divided (modulo 2) by the generator polynomial, where $k$ is the number of bits of the dividend; and +- the remainder of the division (modulo 2) by the generator polynomial of the product of $x^{24}$ by the dividend. + +The CRC-24 generator polynomial is: + +$$G(x) = x^{24} + x^{23} + x^{21} + x^{20} + x^{19} + x^{17} + x^{16} + x^{15} + x^{13} + x^8 + x^7 + x^5 + x^4 + x^2 + 1$$ + +The result of the CRC calculation is placed within the FCS field as described in subclause 5.7.3. + +NOTE: As a typical implementation at the transmitter, the initial content of the register of the device computing the remainder of the division is pre-set to all "1's" and is then modified by division by the generator polynomial (as described above) of the dividend; the ones complement of the resulting remainder is put into the FCS field. + +As a typical implementation at the receiver, the initial content of the register of the device computing the remainder of the division is pre-set to all "1's". The final remainder, after multiplication by $x^{24}$ and then division (modulo 2) by the generator polynomial of the received frame, will be (in the absence of errors): + +$$C(x) = x^{22} + x^{21} + x^{19} + x^{18} + x^{16} + x^{15} + x^{11} + x^8 + x^5 + x^4$$ + +## 5.5a Message Authentication Code (MAC) field + +The MAC field, when present, shall contain the integrity protection information for the frame. The MAC field shall be included in the security protected frames when integrity protection has been activated. For usage and detailed coding of the MAC field, see 3GPP TS 43.020 [27]. + +MAC calculation shall be done before the CRC calculation at the transmitting side, and after CRC calculation at the receiving side. + +## 5.6 Transparency + +### 5.6.1 Bit transparency + +Because of the frame delimitation technique used in LLC, the frame can include any possible sequence of bits without the need for e.g., bit stuffing as defined in ITU-T Recommendation Q.921 [14]. + +### 5.6.2 Information protection + +The information carried within a UI frame may be considered as either "protected" or "unprotected" (see subclause 6.3.5.5.2). CRC error detection procedures are only used on the first N202 octets of the information content within unprotected UI frames, supporting applications that can tolerate bit errors. + +### 5.6.3 Octet alignment + +LLC provides only an octet-aligned service to layer 3. LLC requires that information exchanged with layer 3 contains an integral number of octets. + +## 5.7 Format convention + +### 5.7.1 Numbering convention + +The basic convention used in the present document is illustrated in figure 4. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to n. + +![](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|-----|---|---|---|---|---|---|---|-------| +| Bit | | | | | | | | | +| | | | | | | | | 1 | +| | | | | | | | | 2 | +| | | | | | | | | : | +| | | | | | | | | : | +| | | | | | | | | n-1 | +| | | | | | | | | n | + +Figure 4: Format convention + +### 5.7.2 Order of transmission + +Frames are transferred between the LLC layer and underlying protocol layers in units of octets, in ascending numerical octet order (i.e., octet 1, 2, ..., n-1, n). The order of bit transmission is specific to the underlying protocols used across the Um interface (e.g., RLC) and the Gb interface (BSSGP). + +### 5.7.3 Field mapping convention + +When a field is contained within a single octet, the lowest bit number of the field represents the lowest-order value. When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of the field contained in a given octet the lowest bit number represents the lowest-order value. + +For example, a bit number can be identified as a couple (o, b) where o is the octet number and b is the relative bit number within the octet. Figure 5 illustrates a field that spans from bit (1, 3) to bit (2, 7). The high-order bit of the field is mapped on bit (1, 3) and the low-order bit is mapped on bit (2, 7). + +![](3191384ecc1531d40a00140dd21fd781_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------|-------|---|---|---|-------|-------|-------|--------------------| +| Bit | | | | | | | | | +| | | | | | $2^4$ | $2^3$ | $2^2$ | 1st octet of field | +| $2^1$ | $2^0$ | | | | | | | 2nd octet of field | + +Figure 5: Field mapping convention + +An exception to the preceding field mapping convention is the FCS field. In this case bit 1 of the first octet is the high-order bit and bit 8 of the last octet is the low-order bit. The field mapping for a 24 bit FCS field is shown in figure 6. + +| Bit | | | | | | | | | +|----------|---|---|---|---|---|---|----------|--------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| $2^{16}$ | | | | | | | $2^{23}$ | 1st octet of field | +| $2^8$ | | | | | | | $2^{15}$ | 2nd octet of field | +| $2^0$ | | | | | | | $2^7$ | 3rd octet of field | + +**Figure 6: FCS field mapping convention** + +## 5.8 Invalid frames + +An invalid frame is a frame that: + +- contains fewer octets than necessary to include the address field, control field, information field (including the MAC field if integrity protection is used), and FCS field necessary to constitute a complete frame according to the contents of the control field; +- has the PD bit set to 1; +- contains a reserved SAPI or a SAPI that is not supported or not assigned to a layer-3 entity; +- contains an FCS field error (see subclause 6.3.5.5.2 for details on FCS field error) ; or +- contains a MAC field error (see subclause 6.3.5.5.2a for details on MAC field error). + +An invalid frame shall be discarded without notification to the sender. No action shall be taken as the result of that frame. + +# 6 Elements of procedures and formats of fields + +## 6.1 General + +The elements of procedures define the commands and responses that are used on the logical link connections between the MS and SGSN. + +Procedures are derived from these elements of procedures and are described in clause 8. + +If a bit position is marked as "spare", it shall be coded as 0. A spare bit is indicated with an 'X' in the format figures in this clause. For future compatibility reasons, an entity receiving frames, where spare bit positions are coded otherwise, shall ignore those values without notification of any error. + +## 6.2 Address field format and variables + +### 6.2.0 Address field format + +The address field consists of + +- the Protocol Discriminator bit PD; +- the Command/Response bit C/R; and +- the SAPI. + +The format of the address field is shown in figure 7. + +| Bit | | | | | | | | | +|-----|-----|---|---|------|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +| PD | C/R | X | X | SAPI | | | | 1 | + +**Figure 7: Address field format** + +#### 6.2.1 Protocol Discriminator bit (PD) + +The PD bit indicates whether a frame is an LLC frame or belongs to a different protocol. LLC frames shall have the PD bit set to 0. If a frame with the PD bit set to 1 is received, then it shall be treated as an invalid frame, see subclause 5.8. + +### 6.2.2 Command/Response bit (C/R) + +The C/R bit identifies a frame as either a command or a response. The MS side shall send commands with the C/R bit set to 0, and responses with the C/R bit set to 1. The SGSN side shall do the opposite; i.e., commands are sent with C/R set to 1, and responses are sent with C/R set to 0. The combinations for the SGSN side and MS side are shown in table 1. + +**Table 1: C/R field bit usage** + +| Type | Direction | C/R value | +|----------|----------------------|-----------| +| Command | SGSN side to MS side | 1 | +| Command | MS side to SGSN side | 0 | +| Response | SGSN side to MS side | 0 | +| Response | MS side to SGSN side | 1 | + +### 6.2.3 Service Access Point Identifier (SAPI) + +SAPI identifies a point at which LLC services are provided by an LLE to a layer-3 entity. Consequently, SAPI identifies an LLE that should process an LLC frame and also a layer-3 entity that is to receive information carried by the LLC frame. + +SAPI allows 16 service access points to be specified. The SAPI values are allocated as shown in table 2. + +**Table 2: Allocation of SAPI values** + +| SAPI | Related Service | SAP Name | +|------|--------------------------|----------| +| 0000 | Reserved | - | +| 0001 | GPRS Mobility Management | LLGMM | +| 0010 | Tunnelling of messages 2 | TOM2 | +| 0011 | User data 3 | LL3 | +| 0100 | Reserved | - | +| 0101 | User data 5 | LL5 | +| 0110 | Reserved | - | +| 0111 | SMS | LLSMS | +| 1000 | Tunnelling of messages 8 | TOM8 | +| 1001 | User data 9 | LL9 | +| 1010 | Reserved | - | +| 1011 | User data 11 | LL11 | +| 1100 | Reserved | - | +| 1101 | Reserved | - | +| 1110 | Reserved | - | +| 1111 | Reserved | - | + +## 6.3 Control field formats, parameters, and variables + +### 6.3.0 Control field formats + +The control field identifies the type of frame. Four types of control field formats are specified: + +- confirmed information transfer (I format); +- supervisory functions (S format); +- unconfirmed information transfer (UI format); and +- control functions (U format). + +The control field formats for LLC are shown in figure 8 and figure 9. For definition of values for supervisory function bits and unnumbered function bits, see table 4. + +| Format | Control Field Bits | | | | | | | | Octet | +|-------------------|--------------------|------|---|-----|----------------|----------------|----------------|----------------|-------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| I format
(I+S) | 0 | A | X | | | | | N(S) | 1 | +| | | N(S) | | | X | | | N(R) | 2 | +| | | | | | | N(R) | S 1 | S 2 | 3 | +| S format | 1 | 0 | A | X | X | | | N(R) | 1 | +| | | | | | | N(R) | S 1 | S 2 | 2 | +| UI format | 1 | 1 | 0 | IP | X | | | N(U) | 1 | +| | | | | | | N(U) | E | PM | 2 | +| U format | 1 | 1 | 1 | P/F | M 4 | M 3 | M 2 | M 1 | 1 | + +A Acknowledgement request bit +E Encryption function bit +IP Integrity Protection bit +Mn Unnumbered function bit +N(R) Transmitter receive sequence number +N(S) Transmitter send sequence number +N(U) Transmitter unconfirmed sequence number +P/F Poll bit, when issued as a command, +Final bit, when issued as a response +PM Protected Mode bit +Sn Supervisory function bit +X Spare bit + +**Figure 8: Control field format** + +![](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Control field bits + +| Format | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +|---------------------------|--------|--------|--------|--------|--------|--------|--------|----------|----------|--| +| I frame
SACK
format | 0 | A | X | N(S) | | | | | 1 | | +| | N(S) | | | X | N(R) | | | | 2 | | +| | N(R) | | | | | 1 | 1 | | 3 | | +| | X | X | X | K | | | | | 4 | | +| | R(1) | R(2) | R(3) | R(4) | R(5) | R(6) | R(7) | R(8) | 5 | | +| | R(9) | R(10) | R(11) | R(12) | R(13) | R(14) | R(15) | R(16) | 6 | | +| | ... | | | | | | | | : | | +| | R(249) | R(250) | R(251) | R(252) | R(253) | R(254) | R(255) | X | 36 (max) | | +| S frame
SACK
format | 1 | 0 | A | X | X | N(R) | | | 1 | | +| | N(R) | | | | | 1 | 1 | | 2 | | +| | R(1) | R(2) | R(3) | R(4) | R(5) | R(6) | R(7) | R(8) | 3 | | +| | R(9) | R(10) | R(11) | R(12) | R(13) | R(14) | R(15) | R(16) | 4 | | +| | ... | | | | | | | | : | | +| R(249) | R(250) | R(251) | R(252) | R(253) | R(254) | R(255) | X | 34 (max) | | | + +A Acknowledgement request bit +K Bitmap length indicator +Mn Unnumbered function bit +N(R) Transmitter receive sequence number +N(S) Transmitter send sequence number +R(n) Bitmap bit. +X Spare bit + +**Figure 9: SACK I and S frame control field format** + +#### 6.3.1 Information transfer format - I + +The I format shall be used to perform an information transfer between layer-3 entities with acknowledgement. The functions of N(S), N(R), and A are independent; that is, each I frame has an N(S) sequence number, an N(R) sequence number that may or may not acknowledge additional I frames received by the LLE, and an A bit that may be set to 0 or 1. The use of N(S), N(R), and A is defined in clause 8. + +Each I frame also contains supervisory information, in effect "piggy-backing" an S frame with each I frame, so that it may be considered to be an I+S frame. + +#### 6.3.2 Supervisory format - S + +The S format shall be used to perform logical link supervisory control functions such as acknowledge I frames and request a temporary suspension of I-frame transmission. The functions of N(R) and the A bit are independent; that is, each supervisory frame has an N(R) sequence number that may or may not acknowledge additional I frames received by the LLE, and an A bit that may be set to 0 or 1. The use of N(R) and the A bit is described in clause 8. + +#### 6.3.3 Unconfirmed Information format - UI + +The UI format shall be used to perform an information transfer between layer-3 entities without acknowledgement. No verification of sequence numbers is performed for UI frames. Therefore, a UI frame may be lost without notification to the layer-3 entity if a logical link exception occurs during transmission of the frame. The information field may be encrypted or not as indicated by the E bit (see subclause 6.3.5.5.1). The frame also includes a PM bit that allows the transfer of unprotected information (see subclause 6.3.5.5.2). If integrity protection is intended to be used, the frame may be integrity protected or not as indicated by the IP bit (see subclause 6.3.5.2a). + +### 6.3.4 Unnumbered format - U + +The U format shall be used to provide additional logical link control functions. This format contains no sequence number. The format includes a P/F bit that may be set to 0 or 1. + +### 6.3.5 Control field parameters and associated state variables + +The various parameters associated with the control field formats are described in this subclause. + +#### 6.3.5.1 Poll/Final bit (P/F) + +All U frames contain the Poll/Final (P/F) bit. The P/F bit serves a function in both command frames and response frames. In command frames the P/F bit is referred to as the P bit. In response frames it is referred to as the F bit. + +The P bit set to 1 is used by an LLE to solicit (poll) a response frame from the peer LLE. The F bit set to 1 is used by an LLE to indicate the response frame transmitted as a result of a soliciting (poll) command. + +The use of the P/F bit is described in clause 8. + +#### 6.3.5.2 Acknowledgement request bit (A) + +All I and S frames contain the Acknowledgement Request (A) bit. + +The A bit set to 1 is used by an LLE to solicit an acknowledgement (i.e., an I+S or S frame) from the peer LLE. The A bit set to 0 is used by an LLE to indicate that the peer LLE is not requested to send an acknowledgement. + +The use of the A bit is described in clause 8. + +##### 6.3.5.2a Integrity Protection bit (IP) + +UI frames contain the Integrity Protection (IP) bit. + +The IP bit set to 1 is used by an LLE to indicate integrity protected frames that include the 4 octet MAC field. The IP bit set to 0 is used by an LLE to indicate non-integrity protected frames. + +#### 6.3.5.3 Modulus + +Each I and UI frame is sequentially numbered by a sequence number that may have the value 0 through 511. + +Arithmetic acting on parameters and variables that are related to such sequence numbers operates modulo 512 (i.e. N(S), N(R), N(U), V(S), V(R), V(A), V(U), V(UR); see the following subclauses). + +NOTE: Modulo 512 operation on negative numbers is performed by adding multiples of 512 to the negative number until the result becomes non-negative. Then common modulo 512 operation is applied. + +#### 6.3.5.4 ABM variables and sequence numbers + +##### 6.3.5.4.1 Send state variable V(S) + +In Asynchronous Balanced Mode, each LLE peer shall have an associated send state variable V(S) when using I frames. V(S) denotes the sequence number of the next in-sequence I frame to be transmitted. V(S) can take on the value 0 through 511. The value of V(S) shall be incremented by 1 with each successive I frame transmission, and shall not exceed V(A) by more than the maximum number of outstanding I frames k. The value of k may be in the range $1 \leq k \leq 255$ , as defined in subclause 8.9.8. V(S) shall not be incremented when an I frame is retransmitted. + +##### 6.3.5.4.2 Acknowledge state variable V(A) + +In Asynchronous Balanced Mode, each LLE peer shall have an associated acknowledge state variable V(A) when using I frame and supervisory frame commands and responses. V(A) identifies the first I frame in the transmit window, so that $V(A) - 1$ equals N(S) of the last in-sequence acknowledged I frame. V(A) can take on the value 0 through 511. The value of V(A) shall be updated by the valid N(R) values received from its peer (see subclause 6.3.5.4.5). A valid N(R) value is one that is in the range $V(A) \leq N(R) \leq V(S)$ . + +These inequalities shall be interpreted in the following way: + +$N(R)$ is valid if, and only if, $( N(R) - V(A) ) \bmod 512 \leq ( V(S) - V(A) ) \bmod 512$ . + +Furthermore, from subclause 6.3.5.4.1, $( V(S) - V(A) ) \bmod 512 \leq k$ . + +##### 6.3.5.4.3 Send sequence number $N(S)$ + +In Asynchronous Balanced Mode, only I frames contain $N(S)$ , the send sequence number of transmitted I frames. At the time that an in-sequence I frame is designated for transmission, the value of $N(S)$ is set equal to the value of the send state variable $V(S)$ . + +##### 6.3.5.4.4 Receive state variable $V(R)$ + +In Asynchronous Balanced Mode, each LLE peer shall have an associated receive state variable $V(R)$ when using I frame and supervisory frame commands and responses. $V(R)$ denotes the sequence number of the next in-sequence I frame expected to be received. $V(R)$ can take on the value 0 through 511. The value of $V(R)$ shall be incremented by one with the receipt of an error-free, in-sequence I frame whose send sequence number $N(S)$ equals $V(R)$ . + +##### 6.3.5.4.5 Receive sequence number $N(R)$ + +In Asynchronous Balanced Mode, all I frames and supervisory frames contain $N(R)$ , the expected send sequence number of the next in-sequence received I frame. At the time that a frame of the above types is designated for transmission, the value of $N(R)$ is set equal to the value of the receive state variable $V(R)$ . $N(R)$ indicates that the LLE transmitting the $N(R)$ has correctly received all I frames numbered up to and including $N(R) - 1$ . + +##### 6.3.5.4.6 SACK bitmap $R(n)$ + +In Asynchronous Balanced Mode, all I+S and S SACK frames contain $R(n)$ , the SACK bitmap. At the time that a SACK frame is designated for transmission, the value of each bit $R(n)$ in the bitmap shall be set to 0 or 1 depending on whether I frame number $N(R) + n$ has been received or not. $R(n) = 1$ indicates that the LLE transmitting the SACK frame has correctly received I frame number $N(R) + n$ . $R(n) = 0$ indicates that the LLE transmitting the SACK frame has not correctly received I frame number $N(R) + n$ . + +The SACK bitmap contains a maximum of 255 bits, or 32 octets, as shown in figure 9. The bitmap shall be truncated so that only bitmap octets up to and including the last bitmap octet containing at least one bit set to 1 are transmitted. The trailing bitmap octets shall not be transmitted. + +The I+S SACK frame contains a bitmap length indicator $K$ . $K + 1$ indicates the number of octets in the bitmap. $K$ can take any value 0 through 31. + +##### 6.3.5.4.7 I frame buffer variable $B$ + +In Asynchronous Balanced Mode, each LLE peer shall have an associated I frame buffer variable $B$ when using I frame and supervisory frame commands and responses. The value of $B$ has a range of $0 \leq B \leq M$ , where $M$ is defined in subclause 8.9.7. + +Function $L(x)$ gives the total information field length in octets of the I frame with sequence number $x$ . $B$ shall be incremented with $L(x)$ of each transmitted I frame as defined in subclause 8.6.1. $B$ shall be decremented by $L(x)$ of each acknowledged I frame as defined in subclause 8.6.3.2. + +##### 6.3.5.4.8 Other parameters and variables + +For definition and values of additional parameters and variables, see subclause 8.9. + +#### 6.3.5.5 Unacknowledged operation variables and parameters + +##### 6.3.5.5.1 Encryption mode bit (E) + +The E bit is used to indicate whether the information and FCS fields of the UI frame are encrypted (ciphered) to provide user data confidentiality. The E bit is set to 1 to indicate an encrypted frame. The E bit is set to 0 to indicate a frame sent without encryption. + +##### 6.3.5.5.2 Protected Mode bit (PM) + +The PM bit is used to indicate whether the FCS field shall be calculated using both the frame header and information fields. + +The PM bit is set to 1 to indicate that the FCS field covers the frame header field and the information field (including the MAC field if any). + +The PM bit is set to 0 to indicate that the FCS field covers only the frame header field and the first N202 octets of the information field. If the length of the information field is less than N202 octets then the FCS field shall cover the complete information field. This permits UI frames to transport "unprotected" information, such that errors beyond the first N202 octets of the information field do not result in the frame being discarded. + +**Table 3: UI frame content, relationship between PM bit and E bit** + +| PM | E | UI frame information field | +|----|---|---------------------------------------| +| 0 | 0 | unprotected, non-ciphered information | +| 0 | 1 | unprotected, ciphered information | +| 1 | 0 | protected, non-ciphered information | +| 1 | 1 | protected, ciphered information | + +##### 6.3.5.5.3 Unconfirmed send state variable V(U) + +Each LLE peer shall have an associated unconfirmed send state variable V(U) when using UI frame commands. V(U) denotes the sequence number of the next UI frame to be transmitted. V(U) can take on the value 0 through 511. The value of V(U) shall be incremented by 1 with each successive UI frame transmission. + +##### 6.3.5.5.4 Unconfirmed sequence number N(U) + +Only UI frames contain N(U), the unconfirmed sequence number of transmitted UI frames. At the time that a UI frame is designated for transmission, the value of N(U) is set equal to the value of the unconfirmed send state variable V(U). + +##### 6.3.5.5.5 Unconfirmed receive state variable V(UR) + +Each LLE peer shall have an associated unconfirmed receive state variable V(UR) when using UI frame commands. V(UR) denotes the sequence number of the next in-sequence UI frame expected to be received. V(UR) can take on the value 0 through 511. + +##### 6.3.5.5.6 Other parameters and variables + +The only other parameter defined for unacknowledged operation is the number of octets (N201-U) in the information field of the UI frame. See subclause 8.9.4. + +## 6.4 Commands and responses + +### 6.4.1 General + +The following commands and responses are used by the MS and the SGSN LLEs and are represented in table 4. Each logical link connection shall support the appropriate set of commands and responses for the type of operation desired (see clause 8). + +Those frame types not identified in figure 8, figure 9, or table 4, shall be identified as having undefined command and/or response control fields, and shall be treated as defined in subclause 8.8.2. + +**Table 4: Commands and responses** + +| Format | Commands | Responses | Encoding | | | | | | +|---------------------------------------------------|----------|-----------|----------|----|----|----|----|----| +| | | | S1 | S2 | M4 | M3 | M2 | M1 | +| Supervisory | RR | RR | 0 | 0 | - | - | - | - | +| Supervisory | ACK | ACK | 0 | 1 | - | - | - | - | +| Supervisory | RNR | RNR | 1 | 0 | - | - | - | - | +| Supervisory
or
Information +
Supervisory | SACK | SACK | 1 | 1 | - | - | - | - | +| Unnumbered | - | DM | - | - | 0 | 0 | 0 | 1 | +| Unnumbered | DISC | - | - | - | 0 | 1 | 0 | 0 | +| Unnumbered | - | UA | - | - | 0 | 1 | 1 | 0 | +| Unnumbered | SABM | - | - | - | 0 | 1 | 1 | 1 | +| Unnumbered | - | FRMR | - | - | 1 | 0 | 0 | 0 | +| Unnumbered | XID | XID | - | - | 1 | 0 | 1 | 1 | +| Unnumbered | NULL | - | - | - | 0 | 0 | 0 | 0 | + +The commands and responses in table 4 are defined in the following subclauses. + +### 6.4.1 Unnumbered (U) frames + +#### 6.4.1.1 Set Asynchronous Balanced Mode (SABM) command + +The SABM unnumbered command shall be used to place the addressed MS or SGSN side into ABM acknowledged operation. + +An LLE shall confirm acceptance of a SABM command by the transmission at the first opportunity of a UA response. Upon acceptance of this command, the LLE's send state variable V(S), acknowledge state variable V(A), and receive state variable V(R), shall be set to 0. The transmission of a SABM command indicates the clearance of any exception condition, and a busy condition that was reported by the earlier transmission of an RNR frame by that same LLE. + +Previously transmitted I frames that are unacknowledged when this command is actioned shall be discarded. It is the responsibility of a higher layer to recover from the possible loss of the contents of such I frames. + +An information field is permitted with the SABM command. If included, the information field shall contain XID parameters. This allows the LLC peers to negotiate LLC layer parameters and layer-3 parameters with the SABM command and UA response, using the procedure (but not the XID frames) defined in subclauses 6.4.1.6 and 8.5.3. + +#### 6.4.1.2 Disconnect (DISC) command + +The DISC unnumbered command shall be transmitted in order to terminate the ABM operation. + +No information field is permitted with the DISC command. Prior to executing the command, the LLE receiving the DISC command shall confirm the acceptance of a DISC command by the transmission of a UA response. The LLE sending the DISC command shall terminate the ABM operation when it receives the acknowledging UA or DM response. + +Previously transmitted I frames that are unacknowledged when this command is executed shall remain unacknowledged and shall be discarded. It is the responsibility of a higher layer to recover from the possible loss of the contents of such I frames. + +#### 6.4.1.3 Unnumbered Acknowledgement (UA) response + +The UA unnumbered response shall be used by an LLE to acknowledge the receipt and acceptance of the mode-setting commands (SABM or DISC). Received mode-setting commands are not actioned until the UA response is transmitted. + +An information field is only permitted when UA is the response to a SABM command. The UA response shall in this case contain XID parameters with negotiated XID values, using the procedure (but not the XID frames) defined in subclauses 6.4.1.6 and 8.5.3. + +The transmission of the UA response indicates the clearance of any busy condition that was reported by the earlier transmission of an RNR frame by that same LLE. + +#### 6.4.1.4 Disconnected Mode (DM) response + +The DM unnumbered response shall be used by an LLE to report to its peer that the LLE is in a state such that ABM operation cannot be performed. An LLE shall transmit a DM response to any valid command received that it cannot action. + +No information field is permitted with the DM response. + +#### 6.4.1.5 Frame Reject (FRMR) response + +The FRMR unnumbered response may be received by an LLE as a report of a frame rejection condition not recoverable by retransmission of the identical frame: + +- 1) receipt of a command or response control field that is undefined or not implemented (see subclause 6.4, 2nd paragraph); +- 2) receipt of a supervisory or unnumbered frame with incorrect length; or +- 3) receipt of an I frame with an information field that exceeds the maximum established length. + +An undefined control field is any of the control field encodings that are not identified in figure 8, figure 9, or table 4. + +An information field that immediately follows the control field and that consists of 10 octets shall be returned with this response to provide the reason for the FRMR response. This information field format is given in figure 10. Only the first 6 octets of the control field of the rejected frame shall be sent. If the control field of the rejected frame is fewer than 6 octets, then the unused octets shall be set to 0. + +![Figure 10: FRMR frame information field format diagram showing the structure of the rejected frame control field and the subsequent information field octets.](68ea9310fb829dd6007635a6cd4ea2ad_img.jpg) + +The diagram illustrates the FRMR frame information field format. It shows the 'Rejected frame control field' (octets 1-6) and the 'Information field' (octets 7-10). The control field is shown as a large rectangle. The information field is shown as a series of octets, each containing bits. The bits are labeled 8, 7, 6, 5, 4, 3, 2, 1 from left to right. The fields are defined as follows: + +| Octet | Bit 8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | +|-------|------------------------------|-------|-------|-------|-------|-------|-------|-------| +| 1 | Rejected frame control field | | | | | | | | +| 2 | | | | | | | | | +| 3 | | | | | | | | | +| 4 | | | | | | | | | +| 5 | | | | | | | | | +| 6 | | | | | | | | | +| 7 | X | X | X | X | V(S) | | | | +| 8 | V(S) | | | | X | V(R) | | | +| 9 | V(R) | | | | | | C/R | | +| 10 | X | X | X | X | W4 | W3 | W2 | W1 | + +Figure 10: FRMR frame information field format diagram showing the structure of the rejected frame control field and the subsequent information field octets. + +Figure 10: FRMR frame information field format + +The information fields defined for the FRMR response are listed in table 5. + +Table 5: FRMR frame fields + +| Field | Description | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Rejected frame control field | The control field of the received frame that caused the frame reject. | +| V(S) | The current send state variable value of the LLE reporting the rejection condition. | +| V(R) | The current receive state variable value of the LLE reporting the rejection condition. V(R) shall not be treated as an acknowledgement of I frames. | +| C/R | Set to 1 if the frame rejected was a response and set to 0 if the frame rejected was a command. | +| W1 | Set to 1 to indicate that the control field received and returned in octets 1 and 2 was considered invalid because the frame contained an information field that is not permitted within this frame or is a supervisory or unnumbered frame with incorrect length. Bit W3 shall be set to 1 in conjunction with this bit. | +| W2 | Set to 1 to indicate that the information field received exceeded the maximum established information field length (N201) of the LLE reporting the rejection condition. | +| W3 | Set to 1 to indicate that the control field received and returned in octets 1 and 2 was undefined or not implemented. | +| W4 | Set to 1 to indicate that the LLE was in ABM when reporting the rejection condition. | + +#### 6.4.1.6 Exchange Identification (XID) command/response + +This frame shall be used to negotiate and re-negotiate LLC layer parameters and layer-3 parameters. XID frames can be transmitted in ADM and ABM. + +The negotiation procedure is one-step, i.e., one side shall start the process by sending an XID command, offering a certain set of parameters from the applicable parameter repertoire (see table 6) the sending entity wants to negotiate, proposing values within the allowed range. In return, the other side shall send an XID response, either confirming these parameter values by returning the requested values, or offering higher or lower ones in their place. As an optimisation, parameters confirming the requested values may be omitted from the XID response. See table 6 for sense of negotiation. This shall end the negotiation process. + +Parameters that are not included in neither the XID command nor in the XID response, shall retain their current values. + +The responding side may respond with parameters that were not included in the XID command. A parameter that was not included in the XID command shall in this case be treated as if the current value of the parameter was included in the XID command. The responding side shall include such a parameter in every XID response until the parameter has been explicitly negotiated, either by responding to an XID command that included the parameter, or by explicitly including the parameter the next time an XID command is transmitted. + +Both entities shall support the negotiated values, however under certain conditions one or more parameters may need to be re-negotiated (e.g., in the case of a change in SGSN). + +XID frames shall always be used with the P/F bit set to 1. + +Without any prior XID exchange, default values shall apply. + +Negotiated XID parameters shall apply to the LLE identified by the DLCI of the XID frames used, except Version, Reset, IOV-UI, i-IOV-UI, i-IOV-UI-cnt and MAC-IOV-UI that applies to an LLME (i.e., a TLLI), and except Layer-3 Parameters that apply to the layer 3 above the LLE. + +Table 6 lists the negotiable LLC layer parameters. Figure 11 shows the format of the XID parameter field. + +![](745261f385368efa3f2259c8681874e9_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|------------------|------|---|---|---|--------|---|---|--------| +| XL | Type | | | | Length | | | 1 | +| Length | | | | | X | X | | 2 | +| High-order octet | | | | | | | | 2 or 3 | +| ... | | | | | | | | ... | +| Low-order octet | | | | | | | | n | + +**Figure 11: XID parameter field format** + +A parameter item consists of one or two type/length octets followed by the value of that parameter. The XID Length (XL) bit indicates whether the Length field is 2 bits or 8 bits long. If XL is set to 0, then Length consists of 2 bits and type/length occupies one octet. If XL is set to 1 then Length consists of 8 bits and type/length occupies two octets. The length indicator gives the number of octets that the value actually occupies. Length shall be set to the value in table 6 for XID parameters that do not have a variable length. The parameter items can be arranged in arbitrary order. The parameter items shall begin in the first octet of the XID information field and follow on contiguously. + +**Table 6: LLC layer parameter negotiation** + +| Parameter Name | Type | Length | Format (87654321) | Range | Units | Sense of Negotiation | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------|----------------------------------------------|------------------------|-----------|----------------------| +| Version (LLC version number) | 0 | 1 | 0000bbbb | 0 through 15 | - | down | +| IOV-UI (ciphering Input offset value for UI frames), common for all SAPIs of a TLLI | 1 | 4 | bbbbbbbb
bbbbbbbb
bbbbbbbb
bbbbbbbb | 0 through $2^{32} - 1$ | - | - | +| IOV-I (ciphering Input offset value for I frames), for the SAPI under negotiation | 2 | 4 | bbbbbbbb
bbbbbbbb
bbbbbbbb
bbbbbbbb | 0 through $2^{32} - 1$ | - | - | +| T200 (retransmission time-out) | 3 | 2 | 0000bbbb
bbbbbbbb | 1 through 4 095 | 0,1 s | up | +| N200 (maximum number of retransmissions) | 4 | 1 | 0000bbbb | 1 through 15 | - | up | +| N201-U (maximum information field length for U and UI frames) | 5 | 2 | 00000bbb
bbbbbbbb | 140 through 1 520 | octets | down | +| N201-I (maximum information field length for I frames) | 6 | 2 | 00000bbb
bbbbbbbb | 140 through 1 520 | octets | down | +| mD (I frame buffer size in the downlink direction) | 7 | 2 | 0bbbbbbb
bbbbbbbb | 0, 9 through 24 320 | 16 octets | down | +| mU (I frame buffer size in the uplink direction) | 8 | 2 | 0bbbbbbb
bbbbbbbb | 0, 9 through 24 320 | 16 octets | down | +| kD (window size in the downlink direction) | 9 | 1 | bbbbbbbb | 1 through 255 | frames | down | +| kU (window size in the uplink direction) | 10 | 1 | bbbbbbbb | 1 through 255 | frames | down | +| Layer-3 Parameters | 11 | Variable | See 3GPP TS 44.065 [11] | | | | +| Reset | 12 | 0 | - | - | - | - | +| i-IOV-UI (integrity protection Input offset value for UI frames), common for all SAPIs of a TLLI | 13 | 4 | bbbbbbbb
bbbbbbbb
bbbbbbbb
bbbbbbbb | 0 through $2^{32} - 1$ | - | - | +| i-IOV-UI-cnt (i-IOV update counter) | 14 | 1 | bbbbbbbb | 1 through 255 | - | - | +| MAC-IOV-UI (MAC value created over i-IOV-UI and i-IOV-UI-cnt) | 15 | 4 | bbbbbbbb
bbbbbbbb
bbbbbbbb
bbbbbbbb | 0 through $2^{32} - 1$ | - | - | +|

NOTE 1: The Range for N201-U for SAPI 1 is 400 through 1 520 octets, and for SAPIs 2, 7, and 8 270 through 1 520 octets.

NOTE 2: All other Types and Ranges are reserved for future versions of the present document.

NOTE 3: The length for Layer-3 Parameters shall be set equal to the number of octets received from layer 3. If an empty XID block is received from layer 3, the LLE shall include a zero-length Layer-3 Parameters XID parameter in the XID parameter field to allow the receiving LLE to distinguish between LLC and layer-3 initiated procedures.

| | | | | | | + +Version shall not be negotiated while in ABM. + +Reset shall only be negotiated with an XID frame, and only be transmitted in the downlink direction. If Reset is present in an XID frame, then it shall be the first XID parameter in the XID information field. + +IOV-UI, i-IOV-UI, i-IOV-UI-cnt and MAC-IOV-UI shall only be negotiated in ADM. IOV-I shall only be negotiated with SABM and UA frames. IOV-UI, i-IOV-UI, i-IOV-UI-cnt, MAC-IOV-UI and IOV-I shall only be transmitted in the downlink direction. + +T200, N200, and N201-U can be negotiated in ADM and ABM. The new values of T200 shall only apply to timers set after the negotiation has been completed. If N201-U is negotiated to a lower value than previously used, then any queued or new U and UI frames that violate the new value of N201-U should be discarded and not transmitted. + +U or UI frames that violate the negotiated value of N201-U may be discarded by the receiver. + +If N201-U is negotiated to a lower value than previously used and the side originating the XID negotiation does not suspend the transfer of U and UI frames for the respective SAPI during the negotiation, then it should apply the proposed value for N201-U already to the U and UI frames transmitted during the negotiation. For received U and UI frames the side originating the XID negotiation shall apply the previous value of N201-U until the negotiation is completed. + +N201-I, mD, mU, kD, and kU can be negotiated to any value in Range in ADM. In ABM, N201-I, mD, mU, kD, and kU can only be negotiated to the same or higher value as previously used. + +#### 6.4.1.7 NULL command + +The NULL unnumbered command shall be used by an MS LLE to indicate a cell update. The NULL unnumbered command is only allowed if the Cell Notification is indicated by the SGSN (see 3GPP TS 23.060 [5] and 3GPP TS 24.008 [8a]). + +No information field is permitted with the NULL command. + +### 6.4.2 Unconfirmed Information (UI) frame + +#### 6.4.2.1 Unconfirmed Information (UI) command + +When a layer-3 entity requests unacknowledged information transfer, the UI command shall be used to send information to its peer. No verification of sequence numbers is performed for UI frames. Therefore, the UI frame may be lost without notification to the layer-3 entity if a logical link exception occurs during transmission of the command. + +#### 6.4.2.2 Unconfirmed Information (UI) Dummy command + +The UI Dummy command is a special UI command that shall never be transmitted by an LLC entity, but it can be received by the LLC entity at the MS. + +If the LLC entity at the MS receives a UI Dummy command, it shall discard it without any further actions. + +NOTE 1: The UI Dummy command may be used by the network for different purposes which are specified in 3GPP TS 44.060 [23] (e.g. to delay the release of a downlink TBF). + +The format of the UI Dummy command is illustrated in figure 11a. The length of the UI Dummy command is variable, with a minimum value of 6 octets and a maximum value of 79 octets. All octets from octet 4 to the last octet N shall be encoded with a hexadecimal value of 2B. + +NOTE 2: The format specified for the UI Dummy command ensures that a receiving LLC entity will always discard it, since the FCS field check always fails (no matter what the length of the UI Dummy command is). + +![](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +| Bit | | | | | | | | | +|---------|-------|-----|---|--------|---------|-----|------|---------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| PD=0 | C/R=1 | 0 | 0 | SAPI=3 | | | | Octet 1 | +| 1 | 1 | D=0 | 0 | 0 | N(U) =0 | | | Octet 2 | +| N(U) =0 | | | | | | E=0 | PM=1 | Octet 3 | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | Octet 4 | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | Octet 5 | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | Octet 6 | +| ⋮ | | | | | | | | | +| ⋮ | | | | | | | | | +| ⋮ | | | | | | | | | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | Octet N-2 (LLC FCS field) | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | Octet N-1 (LLC FCS field) | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | Octet N (LLC FCS field) | + +**Figure 11a: Format of the UI Dummy command** + +### 6.4.3 Combined Information (I) and Supervisory (S) frames + +The function of the information (I) frame is to transfer, across a logical link connection, sequentially-numbered frames containing information fields provided by layer 3. This frame shall only be used in the ABM operation. + +Numbered I frames shall also carry supervisory information, and are for this reason also called I+S frames. A separate S frame is sent when there is no information field to be transferred. Whether an I+S or S frame is transmitted as a command or as a response is insignificant in the ABM procedures. + +#### 6.4.3.1 Receive Ready (RR) command / response + +The receive ready (RR) supervisory frame is used by an LLE to: + +- indicate that it is ready to receive an I frame; and +- acknowledge previously received I frames numbered up to and including N(R) - 1 (as defined in clause 8). + +In addition to indicate the status of an LLE, the RR frame with the A bit set to 1 may be used by the LLE to request an acknowledgement from its peer LLE. + +The transmission of an RR frame shall also indicate the clearance of any busy condition within the sending LLE that was reported by the earlier transmission of an RNR frame by the same LLE. + +#### 6.4.3.2 Acknowledgement (ACK) command / response + +The ACK supervisory frame shall be used by an LLE to acknowledge a single or multiple I frames. Frames up to and including N(R) - 1, and frame N(R) + 1, have been received correctly. The procedures associated with the ACK control field are defined in subclause 8.6.3. + +In addition to indicate the status of an LLE, the ACK frame with the A bit set to 1 may be used by the LLE to request an acknowledgement from its peer LLE. + +The transmission of an ACK frame shall also indicate the clearance of any busy condition within the sending LLE that was reported by the earlier transmission of an RNR frame by the same LLE. + +#### 6.4.3.3 Selective Acknowledgement (SACK) command / response + +The SACK supervisory frame shall be used by an LLE to acknowledge a single or multiple I frames. Frames up to and including N(R) - 1, and frames indicated by the SACK bitmap, have been received correctly. The format of the SACK control field is shown in figure 9. The procedures associated with the SACK control field are defined in subclause 8.6.3. + +In addition to indicate the status of an LLE, the SACK frame with the A bit set to 1 may be used by the LLE to request an acknowledgement from its peer LLE. + +The transmission of a SACK frame shall also indicate the clearance of any busy condition within the sending LLE that was reported by the earlier transmission of an RNR frame by the same LLE. + +#### 6.4.3.4 Receive Not Ready (RNR) command / response + +The receive not ready (RNR) supervisory frame shall be used by an LLE to indicate a busy condition; that is, a temporary inability to accept additional incoming I frames. The value of N(R) in the RNR frame acknowledges I frames numbered up to and including N(R) - 1. Subsequent frames, if any, shall not be considered confirmed. The acceptance status of those is a matter of further status exchange. + +In addition to indicate the status of an LLE, the RNR frame with the A bit set to 1 may be used by the LLE to request an acknowledgement from its peer LLE. + +# --- 7 Elements for layer-to-layer communication + +## 7.1 Definition of service primitives and parameters + +### 7.1.0 General + +Communications between layers and between entities within the logical link control layer are accomplished by means of service primitives. Service primitives represent, in an abstract way, the logical exchange of information and control between the logical link control layer and adjacent layers. They do not specify or constrain implementations. + +Service primitives consist of commands and their respective responses associated with the services requested of another layer. The general syntax of a primitive is: + +XXX - Generic name - Type (Parameters) + +where XXX designates the service access point between the LLC layer and the layer providing or using the service. For the present document XXX is: + +- "LLGMM" for the SAP between the LLC layer and the GPRS mobility management function; +- "LL" for the SAPs between the LLEs and layer 3; +- "GRR" for the SAP between the LLC layer and the RLC/MAC layer; and +- "BSSGP" for the SAP between the LLC layer and the BSSGP layer. + +### 7.1.1 Primitives types + +The primitives types defined in the present document are: + +NOTE: For the action sequence of these primitive types, see 3GPP TS 44.001 [7]. + +#### 7.1.1.1 Request + +The Request primitive type is used when a higher layer is requesting a service from the next lower layer. + +#### 7.1.1.2 Indication + +The Indication primitive type is used by a layer providing a service to notify the next higher layer of activities related to the Request primitive type of the peer. + +#### 7.1.1.3 Response + +The Response primitive type is used by a layer to acknowledge receipt, from the next lower layer, of the Indication primitive type. + +#### 7.1.1.4 Confirm + +The Confirm primitive type is used by the layer providing the requested service to confirm that the activity has been completed (successfully or unsuccessfully). + +### 7.1.2 LLC layer service primitives + +A service primitive specifies the activity that the identified layer should perform. Table 7 lists the primitives defined in the present document. + +**Table 7: LLC layer service primitives** + +| Generic Name | Location | | Type | | | | Parameters | +|---------------------------------------------------------|----------|------|------|-----|-----|-----|---------------------------------------------------------------------------------------------------------------------| +| | MS | SGSN | REQ | IND | RES | CNF | | +| GMM ↔ LLME | | | | | | | | +| LLGMM-ASSIGN | X | X | X | | | | TLLI Old, TLLI New, Ciphering Key, Ciphering Algorithm, Integrity Key, Integrity Algorithm | +| LLGMM-RESET | | X | X | | | X | TLLI | +| LLGMM-TRIGGER | X | | X | | | | TLLI, Cause | +| LLGMM-SUSPEND | X | | X | | | | TLLI | +| LLGMM-SUSPEND | | X | X | | | | TLLI, Page | +| LLGMM-RESUME | X | X | X | | | | TLLI | +| LLGMM-PAGE | | X | | X | | | TLLI | +| LLGMM-IOV | | X | X | | | X | TLLI | +| LLGMM-STATUS | X | X | | X | | | TLLI, Cause | +| LLGMM-PSHO | X | | | X | | | TLLI, Ciphering Algorithm | +| LLGMM-PSHO | | X | X | | | | TLLI, Ciphering Key, Ciphering Algorithm | +| LLGMM-PSHO | | X | | | | X | TLLI, IOV-UI, old XID indicator | +| LLGMM-ASSIGN-USERPLANE | X | X | X | | | | TLLI | +| GMM ↔ LLE, SNDPC ↔ LLE, SMS ↔ LLE, and TOM ↔ LLE | | | | | | | | +| LL-RESET | X | X | | X | | | TLLI, old XID indicator | +| LL-ESTABLISH | X | X | X | | | | TLLI, XID Req | +| LL-ESTABLISH | X | X | | X | | | TLLI, XID Req, N201-U, N201-I | +| LL-ESTABLISH | X | X | | | X | | TLLI, XID Neg | +| LL-ESTABLISH | X | X | | | | X | TLLI, XID Neg, N201-U, N201-I | +| LL-RELEASE | X | X | X | | | | TLLI, Local | +| LL-RELEASE | X | X | | X | | | TLLI, Cause | +| LL-RELEASE | X | X | | | | X | TLLI | +| LL-XID | X | X | X | | | | TLLI, XID Req | +| LL-XID | X | X | | X | | | TLLI, XID Req, N201-U, N201-I | +| LL-XID | X | X | | | X | | TLLI, XID Neg | +| LL-XID | X | X | | | | X | TLLI, XID Neg, N201-U, N201-I | +| LL-DATA | X | | X | | | | TLLI, L3-PDU, Reference, QoS Parameters, Radio Priority | +| LL-DATA | | X | X | | | | TLLI, L3-PDU, Reference, QoS Parameters | +| LL-DATA | X | X | | X | | | TLLI, L3-PDU | +| LL-DATA | X | X | | | | X | TLLI, Reference | +| LL-UNITDATA | X | | X | | | | TLLI, L3-PDU, QoS Parameters, Radio Priority, Cipher, Integrity Protection | +| LL-UNITDATA | | X | X | | | | TLLI, L3-PDU, QoS Parameters, Cipher, Redirect indication, IMSI, GMM cause, Redirect complete, Integrity Protection | +| LL-UNITDATA | X | | | X | | | TLLI, L3-PDU, Cipher, Integrity Protection, MAC Verified, LLC-MAC | +| LL-UNITDATA | | X | | X | | | TLLI, L3-PDU, Cipher, Redirect attempt, IMSI, Integrity Protection, MAC Verified, LLC-MAC | +| LL-STATUS | X | X | | X | | | TLLI, Cause | +| LLE ↔ RLC/MAC | | | | | | | | +| GRR-DATA | X | | X | | | | TLLI, LL-PDU, SAPI, Cause, QoS Parameters, Radio Priority | +| GRR-DATA | X | | | X | | | TLLI, LL-PDU | +| GRR-UNITDATA | X | | X | | | | TLLI, LL-PDU, SAPI, QoS Parameters, Radio Priority | +| GRR-UNITDATA | X | | | X | | | TLLI, LL-PDU | +| LLE ↔ BSSGP | | | | | | | | + +| Generic Name | Location | | Type | | | | Parameters | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|------|------|-----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------| +| | MS | SGSN | REQ | IND | RES | CNF | | +| BSSGP-DL-UNITDATA | | X | X | | | | TLLI, LL-PDU, QoS Parameters, RLC Confirm, SAPI, Redirect indication, IMSI, GMM cause, V(U) for redirect, Redirect complete | +| BSSGP-UL-UNITDATA | | X | | X | | | TLLI, LL-PDU, Cell Id, Redirect attempt, IMSI, V(U) for redirect | +| NOTE: Parameters related to MOCN configuration, i.e. Redirect indication, IMSI, GMM cause, Redirect attempt, V(U) for redirect, and Redirect complete are applicable only to SAPI 1. | | | | | | | | + +## 7.2 Primitive procedures + +### 7.2.1 GMM - LLME primitives + +#### 7.2.1.1 LLGMM-ASSIGN + +The LLGMM-ASSIGN primitive shall be used by the GPRS mobility management entity to assign, change, or unassign the TLLI, the ciphering key ( $K_c$ or $K_{c128}$ ), the ciphering algorithm, the integrity key and the integrity algorithm. + +The TLLI Old and TLLI New parameters shall be interpreted as follows: + +- If TLLI Old = all 1's and TLLI New $\neq$ all 1's then TLLI New shall be assigned and used when (re-)transmitting LLC frames. If a TLLI Old $\neq$ all 1's was assigned to the LLME, then TLLI Old is unassigned. Only TLLI New shall be accepted when received from the peer. It shall be treated as a TLLI change according to subclause 8.3.2. If TLLI Old = all 1's was assigned to the LLME, then this shall be treated as a TLLI assignment according to subclause 8.3.1, and the LLGMM-ASSIGN-REQ shall be the first primitive sent by GMM in order to enable LLC to process requests from layer 3. +- If TLLI Old $\neq$ all 1's and TLLI New $\neq$ all 1's then TLLI Old and TLLI New are assigned, and TLLI New shall be used when (re-)transmitting LLC frames. Both TLLI Old and TLLI New shall be accepted when received from the peer. It shall be treated as a TLLI change according to subclause 8.3.2. +- If TLLI Old $\neq$ all 1's and TLLI New = all 1's then TLLI Old shall be unassigned. It shall be treated as a TLLI unassignment according to subclause 8.3.3, and the LLGMM-ASSIGN-REQ shall be the last primitive sent by GMM in order to disable LLC to not any longer process requests from layer 3. + +An LLC frame received with a DLCI belonging to an unassigned TLLI shall be discarded without any further actions, with the following exception: UI and XID frames with TLLI = unassigned and SAPI = 1 received in the SGSN shall be handled according to the LLC protocol. + +Ciphering Key and Ciphering Algorithm are associated with TLLI New (and with TLLI Old if assigned): + +- If Ciphering Algorithm indicates no ciphering, then the ciphering function shall be disabled. +- Otherwise, the ciphering function shall be enabled. If a Ciphering Algorithm was already associated with TLLI New or TLLI Old, then the new Ciphering Key shall replace the previous Ciphering Key, and Ciphering Algorithm shall replace the previous algorithm selection. All I frames, and UI frames with the E bit set to 1, shall use the new Ciphering Key and algorithm for ciphering. All unacknowledged I frames shall be ciphered using the new Ciphering Key and algorithm before retransmission. As an implementation option, the previous Ciphering Key and algorithm may be used to decipher received frames. + +Integrity Key and Integrity Algorithm are associated with TLLI New (and with TLLI Old if assigned). This is only applicable to a network supporting integrity protection in the LLC layer (see subclause 4.6a): + +- If Integrity Algorithm indicates no integrity protection, then the integrity protection function shall be disabled. +- Otherwise, the integrity protection function shall be enabled. If an Integrity Algorithm was already associated with TLLI New or TLLI Old, then the new Integrity Key shall replace the previous Integrity Key, and Integrity Algorithm shall replace the previous algorithm selection. All UI frames with the IP bit set to 1, shall use the new Integrity Key and algorithm for integrity protection. As an implementation option, the previous Integrity Key and algorithm may be used to integrity protect received frames. + +#### 7.2.1.2 LLGMM-RESET + +LLGMM-RESET-REQ shall be used to order LLC in the SGSN to perform an XID negotiation of Reset and IOV-UI (if ciphering is used) and i-IOV-UI (if integrity protection is used). The LLC layer shall randomly select the value of IOV-UI (if ciphering is used) and i-IOV-UI (if integrity protection is used). + +LLGMM-RESET-CNF shall be used to inform GMM in the SGSN that a successful XID negotiation of Reset and IOV-UI (if ciphering is used) and i-IOV-UI (if integrity protection is used) have been made. + +#### 7.2.1.3 LLGMM-TRIGGER + +LLGMM-TRIGGER-REQ shall be used in the MS to order LLC to transmit any single frame. + +If there is a frame waiting to be transmitted in the MS, then this frame shall be transmitted on the corresponding SAPI or optionally a UI frame with no information field shall be transmitted on any SAPI. Otherwise if Cause indicates Cell Update and if Cell Notification is indicated by the SGSN (see 3GPP TS 24.008 [8a]), then a NULL frame with P=0 shall be transmitted on any SAPI. Otherwise, and if the LLE is in ABM state, a supervisory frame shall be transmitted according to subclause 8.6.4.1 or optionally a UI frame with no information field shall be transmitted on any SAPI. Otherwise, and if the LLE is in ADM state a UI frame with no information field shall be transmitted. There is only need to transmit one frame on one SAPI. + +LLGMM-TRIGGER-REQ is normally used for cell updates or for page responses, and the reason shall be indicated in the Cause parameter. If Cause indicates page response, then the GRR-DATA-REQ Cause parameter shall also indicate page response. + +#### 7.2.1.4 LLGMM-SUSPEND + +LLGMM-SUSPEND-REQ shall be used to order LLC to suspend operation for an MS until LLGMM-RESUME-REQ is received. While suspended, LLC shall: + +- reset timer T201 if running and (in the SGSN) if the Page parameter is not set; and +- stop frame transmission. + +Frame reception shall still be possible. The Page parameter in the SGSN controls whether LLGMM-PAGE-IND shall be sent to GMM or not (see subclause 7.2.1.6). In the MS, and in the SGSN if the Page parameter is not set, ADM procedures for SAPI = 1 including UI frame transmission shall still be possible, and ABM (re-)establishment, ABM release, and XID negotiation procedures on all SAPIs including U frame transmission shall still be possible. + +L3-PDUs and unacknowledged I frames that are buffered shall be preserved while LLC operation is suspended, and may be deleted by procedures allowed while LLC operation is suspended. + +The state (e.g., ABM, ADM) and the state variables (e.g. the transmit and receive counters) shall be preserved while LLC operation is suspended, and may be changed by procedures allowed while LLC operation is suspended. + +#### 7.2.1.5 LLGMM-RESUME + +LLGMM-RESUME-REQ shall be used to order LLC to resume a suspended operation for an MS. LLC operation shall continue with the current set of buffered L3-PDUs, buffered unacknowledged I frames, the state, and the state variables. If timer T201 was reset upon reception of LLGMM-SUSPEND-REQ then timer T201 shall be set. + +#### 7.2.1.6 LLGMM-PAGE + +If the Page parameter received in the LLGMM-SUSPEND-REQ primitive is set to true, LLGMM-PAGE-IND shall be sent to GMM in the SGSN whenever LLC has an LL-PDU ready for transmission and LLC operation is suspended. The LL-PDU shall not be transmitted until LLGMM-RESUME-REQ has been received from GMM. + +If the Page parameter is set to false, LLGMM-PAGE-IND shall not be sent, and the LL-PDU shall not be transmitted until LLGMM-RESUME-REQ has been received from GMM. + +NOTE: LLGMM-PAGE-IND causes GMM to initiate paging of the MS. + +#### 7.2.1.7 LLGMM-IOV + +LLGMM-IOV-REQ shall be used to order LLC in the SGSN to perform an XID negotiation of IOV-UI (if ciphering is used) and i-IOV-UI (if integrity protection is used). The LLC layer shall randomly select the value of IOV-UI (if ciphering is used) and i-IOV-UI (if integrity protection is used). + +LLGMM-IOV-CNF shall be used to inform GMM in the SGSN that a successful XID negotiation of IOV-UI (if ciphering is used) and i-IOV-UI (if integrity protection is used) have been made. + +#### 7.2.1.8 LLGMM-STATUS + +LLGMM-STATUS-IND shall be used to inform GMM when an LLC error that cannot be corrected by the LLC layer has occurred. + +#### 7.2.1.9 LLGMM-PSHO + +The LLGMM-PSHO primitives shall be used in the SGSN during PS Handover (see 3GPP TS 43.129 [26]) as follows: + +- LLGMM-PSHO-REQ shall be used by GMM to provide LLC with the local TLLI to be associated with the mobile station in the new cell. It is used to order LLC in the SGSN to select an IOV-UI. The LLC layer shall randomly select the value of IOV-UI. It is further used to assign the ciphering key ( $K_c$ or $K_{c128}$ ) and the ciphering algorithm. +- LLGMM-PSHO-CNF shall be used by LLC to confirm the local TLLI allocation. It is used to indicate whether each LLE shall use the default configuration for the LLC layer parameters and layer-3 parameters or shall re-initialize the latest negotiated configuration for the LLC layer parameters and layer-3 parameters after PS Handover. It is further used to provide the selected IOV-UI value to use after PS Handover. + +The LLGMM-PSHO primitives shall be used in the MS during PS Handover (see 3GPP TS 43.129 [26]) as follows: + +- LLGMM-PSHO-IND shall be used by LLC to indicate the Ciphering Algorithm. + +#### 7.2.1.10 LLGMM-ASSIGN-USERPLANE + +The LLGMM-ASSIGN-USERPLANE primitive shall be used by the GPRS mobility management entity to request to start integrity protection of user plane data in the LLC layer. + +This is only applicable to a network supporting integrity protection in the LLC layer (see subclause 4.6a). + +### 7.2.2 Layer 3 - LLE primitives + +#### 7.2.2.1 LL-RESET + +LL-RESET-IND shall be used in the SGSN to indicate that the Reset XID parameter is transmitted to the MS. LL-RESET-IND shall be used in the MS to indicate that the Reset XID parameter has been received from the SGSN or that + +a Reset is requested in a PS handover. In case of a PS Handover the old XID indicator indicates whether to keep the configuration for the layer-3 parameters that was applicable before the receipt of the LL-RESET-IND + +#### 7.2.2.2 LL-ESTABLISH + +The LL-ESTABLISH primitives shall be used to request, indicate, respond to, and confirm establishment of ABM operation. XID Req and XID Neg are used to negotiate layer-3 XID parameters between the layer-3 peers, see 3GPP TS 44.065 [11]. + +#### 7.2.2.3 LL-RELEASE + +The LL-RELEASE primitives shall be used to request, indicate, and confirm termination of a previously established ABM operation. The Local parameter indicates whether the termination shall be local, i.e., a DISC frame shall not be transmitted, or not local, i.e. a DISC frame shall be transmitted. The Cause parameter indicates the cause for termination of ABM operation. + +#### 7.2.2.4 LL-XID + +The LL-XID primitives shall be used to request, indicate, respond to, and confirm negotiation of layer-3 XID parameters. + +#### 7.2.2.5 LL-DATA + +The LL-DATA primitives shall only be used for LLEs in ABM. The following operations are defined: + +- LL-DATA-REQ shall be used to request the confirmed transmission of an L3-PDU to the peer. QoS Parameters in the SGSN includes precedence class, delay class, and peak throughput. QoS Parameters in the MS includes peak throughput. QoS Parameters is defined as part of the Quality of Service information element in 3GPP TS 24.008 [8a]. Radio Priority indicates the radio priority level to be used by the RLC/MAC layer. +- LL-DATA-IND shall be used to deliver a correctly received L3-PDU to layer 3. +- LL-DATA-CNF shall be used to confirm the delivery of an L3-PDU to layer 3 in the peer. The Reference parameter shall be set to the same value as the Reference parameter received in the corresponding LL-DATA-REQ. + +#### 7.2.2.6 LL-UNITDATA + +LL-UNITDATA-REQ shall be used to request the unconfirmed transmission of an L3-PDU to the peer. QoS Parameters in the SGSN includes precedence class, delay class, reliability class, and peak throughput. QoS Parameters in the MS includes peak throughput and reliability class. Reliability class indicates whether the UI frame carrying the L3-PDU shall be transmitted in protected or unprotected mode, and whether the RLC/MAC layer acknowledged or unacknowledged mode shall be used. Radio Priority indicates the radio priority level to be used by the RLC/MAC layer. Cipher indicates whether the UI frame shall be ciphered or not. + +Redirect indication, if included, indicates that the SGSN in a multi-operator core network (MOCN) configuration (see 3GPP TS 23.251 [5b]) cannot serve the L3 request. IMSI indicates the IMSI of the UE that is associated with the LLE. GMM cause is the cause code in the L3 message. Redirect complete, if included, indicates that the SGSN will serve the L3 request. Redirect indication and redirect complete shall not both be included. + +Only applicable to a network supporting integrity protection in the LLC layer (see subclause 4.6a): + +- Integrity Protection indicates whether the GMM message was integrity protected with a MAC or not. + +LL-UNITDATA-IND shall be used to deliver an L3-PDU received in a UI frame to layer 3. Cipher indicates whether the received UI frame was ciphered or not. Redirect attempt and IMSI indicate parameters related to MOCN configuration that are to be forwarded with the L3-PDU received in the associated BSSGP-UL-UNITDATA-IND primitive. + +NOTE: The MOCN parameters map to BSSGP information elements as described in 3GPP TS 48.018 [12]. + +Only applicable to a network supporting integrity protection in the LLC layer (see subclause 4.6a): + +- Integrity Protection indicates whether the GMM message was integrity protected with a MAC or not. + +- MAC Verified indicates whether the MAC protecting the GMM message in LLC layer was successfully verified or not; and +- MAC-LCC contains the MAC protecting the GMM message in LLC layer which could not be verified in the LLC layer due to no integrity key or no integrity algorithm configured in the LLC layer. + +#### 7.2.2.7 LL-STATUS + +LL-STATUS-IND shall be used to inform layer 3 when an LLC error that cannot be corrected by the LLC layer has occurred. + +### 7.2.3 LLE - RLC/MAC primitives + +#### 7.2.3.0 General + +Although the GRR-DATA or GRR-UNITDATA primitives are used in all LLC frame transfer operations, for simplicity reasons they are not included in the procedure descriptions in clause 8. + +#### 7.2.3.1 GRR-DATA + +GRR-DATA-REQ shall be used by an LLE in an MS to request the reliable transmission of an LL-PDU. SAPI indicates the SAPI of the LLE. Cause indicates whether GRR-DATA-REQ is sent due to a page response. QoS Parameters includes peak throughput. For UI frames, peak throughput shall be set according to the QoS parameters of the layer-3 entity requesting the transmission of the UI frame. For all other LLC frames, peak throughput may be set according to the QoS parameters for any layer-3 entity that is using the SAPI. Radio Priority indicates the radio priority level to be used by the RLC/MAC layer. + +GRR-DATA-IND shall be used by the RLC/MAC layer in an MS to indicate the successful reception of an LL-PDU. The LL-PDU was completely received without errors detected by the RLC layer. + +All LLC frames except UI frames for SAPIs 3, 5, 9, and 11 shall be transferred with GRR-DATA primitives. All UI frames for SAPIs 3, 5, 9, and 11 shall be transferred with GRR-DATA or GRR-UNITDATA primitives. + +#### 7.2.3.2 GRR-UNITDATA + +GRR-UNITDATA-REQ shall be used by an LLE in an MS to request the unreliable transmission of a UI frame. SAPI indicates the SAPI of the LLE. QoS Parameters includes peak throughput. Peak throughput shall be set according to the QoS parameters of the layer-3 entity requesting the transmission of the UI frame. Radio Priority indicates the radio priority level to be used by the RLC/MAC layer. + +GRR-UNITDATA-IND shall be used by the RLC/MAC layer in an MS to indicate the reception of a UI frame. + +Only UI frames for SAPIs 3, 5, 9, and 11 shall be transferred with GRR-UNITDATA primitives. + +### 7.2.4 LLE - BSSGP primitives + +#### 7.2.4.0 General + +Although the BSSGP-UNITDATA primitives are used in all LLC frame transfer operations, for simplicity reasons they are not included in the procedure descriptions in clause 8. + +#### 7.2.4.1 BSSGP-DL-UNITDATA + +BSSGP-DL-UNITDATA-REQ shall be used by an LLE in an SGSN to request the transmission of an LL-PDU. QoS Parameters includes precedence class, delay class, and peak throughput. RLC Confirm indicates whether the request shall be mapped into a GRR-DATA-REQ or GRR-UNITDATA-REQ primitive in the BSS. SAPI indicates the SAPI of the LLE. + +All LLC frames except UI frames for SAPI 3, 5, 9 and 11 shall be transferred with RLC Confirm indicating mapping into GRR-DATA-REQ primitive. All UI frames for SAPIs 3, 5, 9, and 11 shall be transferred with RLC Confirm indicating mapping into a GRR-DATA-REQ or GRR-UNITDATA-REQ primitives. + +In a MOCN configuration, Redirect indication, IMSI, GMM cause, and Redirect complete indicate the values received for the same parameters in the associated LL-UNITDATA-IND primitive on SAPI 1, if included with the L3 PDU to be transferred. + +If Redirect indication is included with the L3 PDU to be transferred by the SAPI 1 LLE, the V(U) for redirect parameter value shall be set to N(U) + 1 where N(U) is the value included in the header of the LL-PDU. + +NOTE: The decision of whether to include MOCN parameters in the associated BSSGP PDU is taken in BSSGP (see 3GPP TS 48.018 [12]). + +#### 7.2.4.2 BSSGP-UL-UNITDATA + +BSSGP-UL-UNITDATA-IND shall be used by the BSSGP layer in an SGSN to indicate the reception of an LL-PDU. Cell Id indicates the location of the MS when the LL-PDU was transmitted. + +In a MOCN configuration, for SAPI 1, the Redirect attempt, IMSI, and V(U) for redirect parameters may apply. Redirect attempt indicates that the L3 PDU has been redirected by another SGSN. IMSI indicates the IMSI as defined in 3GPP TS 23.003 [3a] corresponding to the UE associated with the LLE. If the V(U) for redirect parameter is included, the SAPI 1 LLE in the SGSN shall set its value of V(U) equal to the value of the V(U) for redirect parameter received. Redirect attempt and IMSI are forwarded to GMM along with the L3 PDU. + +### 7.2.5 LLME - LLE primitives + +The primitives that co-ordinate activities between the LLM and LL entities are not described. Implementations shall perform the necessary co-ordination between GMM $\leftrightarrow$ LLME primitives and LLE operation. + +# --- 8 Definition of the LLC peer-to-peer protocol + +## 8.1 General + +In the following subclauses, a protocol for use by the GPRS logical link control layer between the SGSN and MS is specified, referred to as "LLC". + +The LLC elements of procedure (frame types) that apply are: + +- for unacknowledged information transfer: + - UI command; and +- for ABM acknowledged information transfer: + - SABM command; + - UA response; + - DM response; + - DISC command; + - RR command / response; + - RNR command / response; + - ACK command / response; + - SACK command / response; + - I command / response; and +- for both unacknowledged and acknowledged information transfer: + - FRMR response; and + - XID command / response. + +For handling of timers, the procedures and terminology of ITU-T Recommendation Z.100 [15] are used: + +Set means that: + +- a) if the timer is inactive, the timer becomes active, i.e., a timer value is associated with the timer and it starts running; and +- b) if the timer is active, the timer is first reset as in c) below, and then set as in a) above. + +Reset means that: + +- c) if the timer is active, the timer becomes inactive, i.e., the association with the timer value is lost and it stops running; and +- d) if the timer is inactive, it remains inactive. + +## 8.2 Procedure for the use of the P/F bit + +Timer T200 shall be set when a command frame with the P bit set to 1 is transmitted. An LLE receiving a command frame with the P bit set to 1 shall set the F bit to 1 in the next response frame it transmits. An LLE receiving a command frame with the P bit set to 0 shall discard the command frame with no further action. + +Only one frame with a P bit set to 1 shall be outstanding in a given direction at a given time. Before another frame with the P bit set to 1 can be transmitted, a response frame with the F bit set to 1 shall be received, N200 retransmissions of the outstanding frame shall occur, or the frame shall be discarded because of an unnumbered frame collision. + +## 8.3 TLLI assignment procedures + +### 8.3.0 General + +TLLI assignment and unassignment is further described in clause 7 and annex C. The following two subclauses illustrate the TLLI assignment and unassignment procedures. + +#### 8.3.1 TLLI assignment + +GMM shall assign a TLLI by sending an LLGMM-ASSIGN-REQ (TLLI New $\neq$ all 1's) primitive to LLME. Upon receiving LLGMM-ASSIGN-REQ, LLME shall enter the TLLI Assigned state, and set LLC layer parameters, states, and variables as defined in subclause 8.5.3.1. TLLI assignment is illustrated in figure 12. + +### 8.3.2 TLLI change + +This procedure is used to change from a previously assigned TLLI value to a new TLLI value. GMM shall change TLLI by sending an LLGMM-ASSIGN-REQ (TLLI Old $\neq$ all 1's, TLLI New $\neq$ all 1's) primitive to LLME. Upon receiving LLGMM-ASSIGN-REQ, LLME and all its LLEs shall not change their states. This is illustrated in figure 12. + +### 8.3.3 TLLI unassignment + +This procedure is used to unassign a previously assigned TLLI value. GMM shall unassign a TLLI by sending an LLGMM-ASSIGN-REQ (TLLI New = all 1's) primitive to LLME. Upon receiving LLGMM-ASSIGN-REQ, LLME and all its LLEs shall enter the TLLI Unassigned state. This is illustrated in figure 12. + +![Figure 12: TLLI assignment, change, and unassignment procedure diagram. The diagram shows two entities: MS (Mobile Station) and SGSN (Serving GPRS Support Node). The MS contains two sub-components: GMM and LLC. The SGSN also contains two sub-components: LLC and GMM. Arrows indicate the flow of LLGMM-ASSIGN-REQ primitives. On the MS side, an arrow points from GMM to LLC. On the SGSN side, an arrow points from GMM to LLC. Both arrows are labeled 'LLGMM-ASSIGN-REQ'.](7a0e8e669d4b836c1c1cc05dfb8de661_img.jpg) + +``` + +graph LR + subgraph MS + GMM_MS[GMM] -- "LLGMM-ASSIGN-REQ" --> LLC_MS[LLC] + end + subgraph SGSN + GMM_SGSN[GMM] -- "LLGMM-ASSIGN-REQ" --> LLC_SGSN[LLC] + end + +``` + +Figure 12: TLLI assignment, change, and unassignment procedure diagram. The diagram shows two entities: MS (Mobile Station) and SGSN (Serving GPRS Support Node). The MS contains two sub-components: GMM and LLC. The SGSN also contains two sub-components: LLC and GMM. Arrows indicate the flow of LLGMM-ASSIGN-REQ primitives. On the MS side, an arrow points from GMM to LLC. On the SGSN side, an arrow points from GMM to LLC. Both arrows are labeled 'LLGMM-ASSIGN-REQ'. + +Figure 12: TLLI assignment, change, and unassignment procedure + +## 8.4 Procedures for unacknowledged information transfer + +### 8.4.0 General + +The procedures that apply to the unacknowledged transmission of information are defined below. No LLC layer error recovery procedures are defined for unacknowledged operation. + +![Diagram illustrating unacknowledged information transmission between an Originator and a Receiver. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The flow is: Layer 3 (Originator) sends LL-UNITDATA-REQ to LLC (Originator), which sends a UI frame to LLC (Receiver), which sends LL-UNITDATA-IND to Layer 3 (Receiver).](82fbb97c1145cac89ac72dd080fad17a_img.jpg) + +``` + +sequenceDiagram + participant L3_O as Layer 3 (Originator) + participant LLC_O as LLC (Originator) + participant LLC_R as LLC (Receiver) + participant L3_R as Layer 3 (Receiver) + Note left of LLC_O: Originator + Note right of LLC_R: Receiver + L3_O->>LLC_O: LL-UNITDATA-REQ + LLC_O->>LLC_R: UI + LLC_R->>L3_R: LL-UNITDATA-IND + +``` + +Diagram illustrating unacknowledged information transmission between an Originator and a Receiver. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The flow is: Layer 3 (Originator) sends LL-UNITDATA-REQ to LLC (Originator), which sends a UI frame to LLC (Receiver), which sends LL-UNITDATA-IND to Layer 3 (Receiver). + +Figure 13: Unacknowledged information transmission + +### 8.4.1 Transmission of unacknowledged information + +Unacknowledged information shall be passed from layer 3 to the LLC layer with the LL-UNITDATA-REQ (L3-PDU, Protect, Cipher, Integrity Protection) primitive. The L3-PDU shall be transmitted in a UI command frame to the peer LLE. The PM, E and IP bits in the UI frame shall be set according to the Protect, Cipher and Integrity Protection parameters received from layer 3. + +### 8.4.2 Receipt of unacknowledged information + +On receipt of a UI command frame the contents of the information field shall be passed to the appropriate layer-3 entity with an LL-UNITDATA-IND (L3-PDU, Integrity Protection, MAC Verified, LLC-MAC) primitive, except: + +- if the DLCI of the received UI frame is not supported by the receiver; or +- if N(U) of the received UI frame is in the range $(V(UR) - 32) \leq N(U) < V(UR)$ and if a UI frame with the same N(U) has already been received, + +then the UI frame shall be discarded without any further actions. + +V(UR) shall be set to N(U) + 1 unless N(U) is in the range $(V(UR) - 32) \leq N(U) < V(UR)$ . + +## 8.5 Procedures for establishment and release of ABM operation + +### 8.5.1 Establishment of ABM operation + +#### 8.5.1.1 General + +These procedures shall be used to establish ABM operation between the SGSN and an MS for a single SAPI. + +Layer 3 shall request establishment of ABM operation by use of the LL-ESTABLISH-REQ service primitive. Re-establishment may be initiated as a result of the LLC layer procedures defined in subclause 8.7. All frames other than U and UI frames received during the establishment procedures shall be ignored. + +#### 8.5.1.2 Establishment procedures + +An LLE shall initiate a request for the ABM operation to be set by transmitting the SABM command. All existing exception conditions shall be cleared, the retransmission counter shall be reset, and timer T200 shall be set. All mode-setting commands shall be transmitted with the P bit set to 1. + +Layer 3-initiated establishment procedures imply the discard of all outstanding LL-DATA-REQ primitives and all queued I frames. + +An LLE receiving a SABM command, if it is able to enter the ABM state, shall: + +- inform layer 3 using the LL-ESTABLISH-IND primitive; + +- if the received SABM command contains a Layer-3 Parameters XID parameter, wait for the receipt of an LL-ESTABLISH-RES primitive from layer 3; +- respond with a UA response with the F bit set to the same binary value as the P bit in the received SABM command (i.e., F=1); +- reset timer T200 if active; +- set V(S), V(R), V(A), and B to 0; +- enter the ABM state; +- clear all existing exception conditions; and +- clear any existing peer receiver busy condition. + +Upon reception of the UA response with the F bit set to 1, the originator of the SABM command shall: + +- reset timer T200; +- set V(S), V(R), V(A), and B to 0; and +- enter the ABM state and inform layer 3 using the LL-ESTABLISH-CNF or LL-ESTABLISH-IND (see subclause 8.7.2) primitive. + +![Sequence diagram of Figure 14: Layer 3-initiated ABM establishment procedure. The diagram shows two entities: Originator and Receiver. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The sequence of messages is: 1. Layer 3 (Originator) sends LL-ESTABLISH-REQ to LLC (Originator). 2. LLC (Originator) sends SABM to LLC (Receiver). 3. LLC (Receiver) sends LL-ESTABLISH-IND to Layer 3 (Receiver). 4. Layer 3 (Receiver) sends LL-ESTABLISH-RES to LLC (Receiver). 5. LLC (Receiver) sends UA to LLC (Originator). 6. LLC (Originator) sends LL-ESTABLISH-CNF to Layer 3 (Originator).](030c758fd425016b03290c8f11bef69d_img.jpg) + +``` + +sequenceDiagram + participant L3_O as Layer 3 + participant LLC_O as LLC + participant LLC_R as LLC + participant L3_R as Layer 3 + + Note over L3_O, LLC_O: Originator + Note over LLC_R, L3_R: Receiver + + L3_O->>LLC_O: LL-ESTABLISH-REQ + LLC_O->>LLC_R: SABM + LLC_R->>L3_R: LL-ESTABLISH-IND + L3_R->>LLC_R: LL-ESTABLISH-RES + LLC_R->>LLC_O: UA + LLC_O->>L3_O: LL-ESTABLISH-CNF + +``` + +Sequence diagram of Figure 14: Layer 3-initiated ABM establishment procedure. The diagram shows two entities: Originator and Receiver. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The sequence of messages is: 1. Layer 3 (Originator) sends LL-ESTABLISH-REQ to LLC (Originator). 2. LLC (Originator) sends SABM to LLC (Receiver). 3. LLC (Receiver) sends LL-ESTABLISH-IND to Layer 3 (Receiver). 4. Layer 3 (Receiver) sends LL-ESTABLISH-RES to LLC (Receiver). 5. LLC (Receiver) sends UA to LLC (Originator). 6. LLC (Originator) sends LL-ESTABLISH-CNF to Layer 3 (Originator). + +**Figure 14: Layer 3-initiated ABM establishment procedure** + +If the receiving LLE is unable to enter the ABM state, it shall respond to the SABM command with a DM response with the F bit set to the same binary value as the P bit in the received SABM command. ABM operation for SAPIs 1, 2, 7, and 8 is not permitted while the support of ABM operation is optional for other non reserved SAPIs. The reception of a SABM command for SAPIs for which ABM operation is not permitted or not supported by the receiver shall be responded to with a DM response. + +Upon reception of a DM response with the F bit set to 1, the originator of the SABM command shall indicate this to layer 3 by means of the LL-RELEASE-IND (Cause = 'DM Received') primitive, and reset timer T200. It shall then enter the ADM state. DM responses with the F bit set to 0 shall be ignored in this case. + +![Sequence diagram of Figure 15: Layer 3-initiated ABM establishment procedure, unsuccessful. The diagram shows two entities: Originator and Receiver. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The sequence of messages is: 1. Layer 3 (Originator) sends LL-ESTABLISH-REQ to LLC (Originator). 2. LLC (Originator) sends SABM to LLC (Receiver). 3. LLC (Receiver) sends DM to LLC (Originator). 4. LLC (Originator) sends LL-RELEASE-IND to Layer 3 (Originator).](9e5d66cdb5112ad5cab89552b126e4b9_img.jpg) + +``` + +sequenceDiagram + participant L3_O as Layer 3 + participant LLC_O as LLC + participant LLC_R as LLC + participant L3_R as Layer 3 + + Note over L3_O, LLC_O: Originator + Note over LLC_R, L3_R: Receiver + + L3_O->>LLC_O: LL-ESTABLISH-REQ + LLC_O->>LLC_R: SABM + LLC_R->>LLC_O: DM + LLC_O->>L3_O: LL-RELEASE-IND + +``` + +Sequence diagram of Figure 15: Layer 3-initiated ABM establishment procedure, unsuccessful. The diagram shows two entities: Originator and Receiver. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The sequence of messages is: 1. Layer 3 (Originator) sends LL-ESTABLISH-REQ to LLC (Originator). 2. LLC (Originator) sends SABM to LLC (Receiver). 3. LLC (Receiver) sends DM to LLC (Originator). 4. LLC (Originator) sends LL-RELEASE-IND to Layer 3 (Originator). + +**Figure 15: Layer 3-initiated ABM establishment procedure, unsuccessful** + +An LL-RELEASE-REQ primitive received during LLC layer initiated re-establishment shall be serviced on completion of the establishment operation. + +#### 8.5.1.3 Procedure on expiry of timer T200 + +If timer T200 expires before the UA or DM response with the F bit set to 1 is received, the LLE shall: + +- retransmit the SABM command as defined above; +- set timer T200; and +- increment the retransmission counter. + +After retransmission of the SABM command N200 times, LLME shall indicate this to GMM by means of the LLGMM-STATUS-IND primitive, and the LLE shall send an LL-RELEASE-IND (Cause = 'No Peer Response') to layer 3 and enter ADM state. If XID parameters were included with the SABM command, then the status of these parameters in the peer is unknown and should be re-negotiated. + +### 8.5.2 Termination of ABM operation + +#### 8.5.2.1 General + +These procedures shall be used to terminate ABM operation between the SGSN and an MS. + +Layer 3 shall request termination of ABM operation by use of the LL-RELEASE-REQ service primitive. All frames other than U and UI frames received during the release procedures shall be ignored. + +All outstanding LL-DATA-REQ primitives and all queued I frames shall be discarded. + +If the Local parameter received in the LL-RELEASE-REQ primitive indicates local release, the LLE shall enter ADM state, reset timer T200, and notify layer 3 by means of the LL-RELEASE-CNF primitive. Otherwise, the procedures in subclauses 8.5.2.2 and 8.5.2.3 shall be followed. + +#### 8.5.2.2 Release procedure + +An LLE shall initiate a request for release of the ABM operation by transmitting the DISC command with the P bit set to 1. Timer T200 shall then be set and the retransmission counter reset. + +An LLE receiving a DISC command while in ABM state shall transmit a UA response with the F bit set to the same binary value as the P bit in the received DISC command. An LL-RELEASE-IND (Cause = 'Normal Release') primitive shall be passed to layer 3, and the ADM state shall be entered. + +If the originator of the DISC command receives either: + +- a UA response with the F bit set to 1; or +- a DM response with the F bit set to 1, indicating that the peer LLE is already in ADM state; + +it shall enter the ADM state and reset timer T200. + +The LLE that issued the DISC command is now in the ADM state and shall notify layer 3 by means of the LL-RELEASE-CNF primitive. The conditions relating to this state are defined in subclause 8.5.4. + +![Sequence diagram of the ABM release procedure between an Originator (Layer 3 and LLC) and a Receiver (LLC and Layer 3).](9e6a6c3e99aa474e3abbad752495d9e8_img.jpg) + +``` + +sequenceDiagram + participant L3_O as Layer 3 (Originator) + participant LLC_O as LLC (Originator) + participant LLC_R as LLC (Receiver) + participant L3_R as Layer 3 (Receiver) + + Note left of LLC_O: Originator + Note right of LLC_R: Receiver + + L3_O->>LLC_O: LL-RELEASE-REQ + LLC_O->>LLC_R: DISC + LLC_R->>LLC_O: UA or DM + LLC_R->>L3_R: LL-RELEASE-IND + LLC_O->>L3_O: LL-RELEASE-CNF + +``` + +The diagram illustrates the sequence of messages for the ABM release procedure. It shows two main entities: the Originator (consisting of Layer 3 and LLC) and the Receiver (consisting of LLC and Layer 3). The sequence starts with Layer 3 (Originator) sending an LL-RELEASE-REQ primitive to its LLC layer. The LLC layer (Originator) then transmits a DISC command to the LLC layer (Receiver). The LLC layer (Receiver) responds with a UA or DM command. Upon receiving the response, the LLC layer (Receiver) sends an LL-RELEASE-IND primitive to its Layer 3 layer. Finally, the LLC layer (Originator) sends an LL-RELEASE-CNF primitive to its Layer 3 layer. + +Sequence diagram of the ABM release procedure between an Originator (Layer 3 and LLC) and a Receiver (LLC and Layer 3). + +Figure 16: ABM release procedure + +#### 8.5.2.3 Procedure on expiry of timer T200 + +If timer T200 expires before a UA or DM response with the F bit set to 1 is received, the originator of the DISC command shall: + +- retransmit the DISC command as defined in subclause 8.5.2.2; +- set timer T200; and +- increment the retransmission counter. + +If the LLE has not received the correct response as defined in subclause 8.5.2.2 after N200 attempts to recover, then LLME shall indicate this to GMM by means of the LLGMM-STATUS-IND primitive, and the LLE shall enter the ADM state and notify layer 3 by means of the LL-RELEASE-CNF primitive. + +### 8.5.3 Automatic negotiation of LLC layer and layer-3 parameters + +#### 8.5.3.0 General + +Each LLE has an associated LLME that has the responsibility for initialising the LLC layer parameters necessary for correct peer-to-peer information transport. Initialisation of the parameters shall be done either according to the default values, or according to the values supplied by the peer entity. The latter method utilises the parameter negotiation procedure. The negotiable parameters are listed in table 6. + +LLC layer and layer-3 parameters may be negotiated in ADM or ABM modes of operation. LLC layer and layer-3 parameters may be negotiated with the exchange of XID frames, or with the exchange of SABM and UA frames. After successful negotiation with SABM and UA frames, the LLE shall be in ABM mode of operation, according to subclauses 8.5.1 and 8.7. + +The LLE shall issue an XID command containing the parameters that the LLE wants to negotiate, and set timer T200. The peer LLE shall, upon receipt of the XID command, return an XID response containing the list of parameter values that the peer can support. Timer T200 shall be reset when the XID response is received. XID frames shall be transmitted with the P/F bit set to 1. This is illustrated in figure 17. + +![Figure 17: XID negotiation procedure. The diagram shows two entities, Originator and Receiver, each containing Layer 3 and LLC components. The Originator's Layer 3 sends an LL-XID-IND primitive to its LLC component. The LLC component then transmits an XID command to the Receiver's LLC component. The Receiver's LLC component receives the XID command and returns an XID response. Upon receiving the response, the Receiver's LLC component sends an LL-XID-IND primitive to its Layer 3 component.](18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg) + +``` + +sequenceDiagram + participant L3_O as Layer 3 (Originator) + participant LLC_O as LLC (Originator) + participant LLC_R as LLC (Receiver) + participant L3_R as Layer 3 (Receiver) + + Note left of LLC_O: LL-XID-IND from Layer 3 + LLC_O->>LLC_R: XID command + LLC_R-->>LLC_O: XID response + Note right of LLC_R: LL-XID-IND to Layer 3 + +``` + +Figure 17: XID negotiation procedure. The diagram shows two entities, Originator and Receiver, each containing Layer 3 and LLC components. The Originator's Layer 3 sends an LL-XID-IND primitive to its LLC component. The LLC component then transmits an XID command to the Receiver's LLC component. The Receiver's LLC component receives the XID command and returns an XID response. Upon receiving the response, the Receiver's LLC component sends an LL-XID-IND primitive to its Layer 3 component. + +**Figure 17: XID negotiation procedure** + +LL-XID-IND shall be indicated to layer 3 if N201-U or N201-I have been changed. + +XID frames can be used to negotiate layer-3 parameters. In this case, layer 3 sends the parameters to an LLE with the LL-XID-REQ primitive. The LLE shall issue an XID command containing the layer-3 parameters, and LLC layer parameters if any LLC layer parameters shall be negotiated. The peer LLE shall, upon receipt of the XID command, indicate the layer-3 parameters to layer 3 and upon receipt of an LL-XID-RES primitive return an XID response containing the list of parameter values that the peer can support. The layer-3 parameters received from the peer is sent to layer 3 with the LL-XID-CNF primitive. The LLE issuing the XID command shall set timer T200 when the XID command is transmitted, and reset timer T200 when the XID response is received. This is illustrated in figure 18. + +![Sequence diagram of Layer 3 XID negotiation procedure between an Originator and a Receiver.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +sequenceDiagram + participant L3_O as Layer 3 (Originator) + participant LLC_O as LLC (Originator) + participant LLC_R as LLC (Receiver) + participant L3_R as Layer 3 (Receiver) + + Note left of L3_O: Originator + Note right of L3_R: Receiver + + L3_O->>LLC_O: LL-XID-REQ + LLC_O->>LLC_R: XID + LLC_R->>L3_R: LL-XID-IND + L3_R->>LLC_R: LL-XID-RES + LLC_R->>LLC_O: XID + LLC_O->>L3_O: LL-XID-CNF + +``` + +The diagram illustrates the interaction between Layer 3 and LLC at both the Originator and Receiver ends. At the Originator, Layer 3 sends an LL-XID-REQ primitive to its LLC entity. The LLC entity then transmits an XID command to the peer LLC at the Receiver. Upon receipt, the Receiver's LLC sends an LL-XID-IND primitive to its Layer 3 entity. Layer 3 at the Receiver responds with an LL-XID-RES primitive to its LLC entity. The Receiver's LLC then sends an XID response back to the Originator's LLC. Finally, the Originator's LLC sends an LL-XID-CNF primitive to its Layer 3 entity. + +Sequence diagram of Layer 3 XID negotiation procedure between an Originator and a Receiver. + +Figure 18: Layer 3 XID negotiation procedure + +#### 8.5.3.1 Negotiation of parameter Reset + +The Reset parameter shall be used, in the SGSN originating Reset and in the MS receiving Reset, to: + +- discard all requests pending from layer 3 to the LLEs with no further action; +- abort any ongoing ABM establishment, ABM release, and XID negotiation procedures, except the XID negotiation procedure used to negotiate the Reset parameter; +- if the old XID indicator is set, keep the LLC layer parameter values that were applicable before the receipt of the Reset. Otherwise, set all LLC layer parameters to the default values given in table 9; +- change any LLEs in ABM state to ADM state; +- set the unconfirmed state variable V(U) to 0; +- set the unconfirmed receive state variable V(UR) to 0; and +- set the OCs for unacknowledged information transfer to 0. + +The Reset parameter shall be treated before any additional XID parameters present in the same XID frame. + +If during PS handover the MS is requested to perform a Reset of LLC layer parameters and layer-3 parameters (see 3GPP TS 24.008 [8a]), the MS shall perform the actions described above and shall send the XID response on one of the active SAPIs once the PS handover procedure has been successfully completed (see 3GPP TS 44.060 [76]). + +If Reset of LLC layer parameters and layer-3 parameters without old XID indicator has been performed, following the sending of the XID response each active LLE in the MS shall: + +- set timer T100; and +- not initiate any XID negotiation procedure while T100 is running. + +If an LL-XID-REQ primitive is received from layer 3 at the time T100 is running, depending on implementation, the LLE shall abort or delay it until T100 expires or is reset. + +Upon receipt of an XID command, the LLE shall: + +- reset timer T100, and: +- the LLE shall proceed according to the negotiation of LLC layer and layer-3 parameters described in the subclause 8.5.3. + +NOTE: The reception of an empty XID command is an indication that the SGSN wishes to continue using default values (see 3GPP TS 43.129 [26]). + +If timer T100 expires, the LLE is again allowed to initiate XID negotiation procedure. + +#### 8.5.3.2 Negotiation of parameter m + +The following rules shall apply when mD and mU are negotiated: + +- If mD is negotiated to 0, then the LLEs shall not keep count of outstanding I frame octets in the downlink direction. If mU is negotiated to 0, then the LLEs shall not keep count of outstanding I frame octets in the uplink direction. +- If a SABM or XID command with $mD \neq 0$ is received in an LLE, and if the LLE does not want to apply the count of outstanding I frame octets in the downlink direction, then the LLE shall respond with $mD = 0$ and with N201-I and kD so that N201-I multiplied with kD is less than or equal to the received MD. +- If a SABM or XID command with $mU \neq 0$ is received in an LLE, and if the LLE does not want to apply the count of outstanding I frame octets in the uplink direction, then the LLE shall respond with $mU = 0$ and with N201-I and kU so that N201-I multiplied with kU is less than or equal to the received MU. +- mD and mU shall be negotiated to values that allow at least one I frame with information field length equal to the negotiated value of N201-I to be transmitted in each direction. + +#### 8.5.3.3 Unsuccessful XID negotiation + +If a SABM or XID command with an invalid XID information field is received, then the SABM or XID command, respectively, shall be ignored. + +If a UA or XID response with an invalid XID information field is received, then the UA or XID response shall be ignored, the SABM or XID command shall be retransmitted, and the retransmission counter shall be incremented. After retransmission of the SABM or XID command N200 times, LLME shall indicate this to GMM by means of the LLGMM-STATUS-IND primitive, and the LLE shall send an LL-RELEASE-IND (Cause = 'Invalid XID Response') to layer 3 if a UA response was received or if the LLE was in ABM state, and enter ADM state if not already in ADM state. If the LLE was in ADM state and the XID command frame contained a Layer-3 Parameters XID parameter, then the LLE shall send an LL-STATUS-IND (Cause = 'Invalid XID Response') to layer 3. + +An XID information field shall be treated as invalid if it: + +- contains an XID parameter field that violates the LLC frame format (see figure 3); +- contains the Reset, IOV-UI, i-IOV-UI, i-IOV-UI-cnt, MAC-IOV-UI or IOV-I parameter in the uplink direction; +- contains the IOV-I parameter in an XID frame; +- contains the Layer-3 Parameters parameter on a SAPI different from 3, 5, 9, and 11; +- in the SABM command case, contains the Reset parameter; +- contains the Reset parameter and this parameter is not the first parameter in the XID information field; or +- in the UA or XID response case: + - contains the Reset parameter; + - contains more than one instance of the same XID parameter type; + - contains an XID parameter with unrecognised Type field; + - contains an XID parameter with unsupported length; + - contains an XID parameter with a value that violates the sense of negotiation; or + - contains an XID parameter with a value that is out of range (see table 6). + +If a SABM or XID command with an XID parameter with an unrecognised Type field is received, then this parameter shall be ignored. If a SABM or XID command contains more than one instance of the same XID parameter type, then + +all instances except the first instance shall be ignored. If the received XID information field is valid, and if one or more XID parameters with recognised type but with unsupported lengths or out-of-range values are detected, then these parameters shall be responded to with lengths and values set according to the responder's preferences. + +#### 8.5.3.4 Procedure on expiry of timer T200 + +If timer T200 expires before the XID response with the F bit set to 1 is received, the LLE shall: + +- retransmit the XID command; +- set timer T200; and +- increment the retransmission counter. + +After retransmission of the XID command N200 times, LLME shall indicate this to GMM by means of the LLGMM-STATUS-IND primitive, and, if the LLE is in ABM state, then the LLE shall send an LL-RELEASE-IND (Cause = 'No Peer Response') to layer 3 and enter ADM state. If the LLE was in ADM state and the XID command frame contained a Layer-3 Parameters XID parameter, then the LLE shall send an LL-STATUS-IND (Cause = No Peer Response') to layer 3. The status of the XID parameters that were included in the XID command is unknown in the peer, and should be re-negotiated. If the XID command frame did not contain a Layer-3 Parameters XID parameter, then, as an implementation option, the LLE may wait for an implementation-specific amount of time and re-invoke the XID negotiation procedure. + +### 8.5.4 TLLI Assigned / ADM state + +While in the TLLI Assigned / ADM state: + +- the receipt of a DISC command shall result in the transmission of a DM response with the F bit set to the value of the received P bit; +- on receipt of a SABM command, the procedures defined in subclause 8.5.1 shall be followed; +- on receipt of UI commands, the procedures defined in subclause 8.4 shall be followed; +- on receipt of XID commands, the procedures defined in subclause 8.5.3 shall be followed; +- on receipt of any unsolicited UA response an LLGMM-STATUS-IND primitive indicating a possible multiple-assignment of a TLLI value shall be issued; +- the receipt of an S or I+S command frame shall result in the transmission of a DM response with the F bit set to 0; and +- all other frame types shall be discarded. + +### 8.5.5 Collision of unnumbered commands + +#### 8.5.5.0 General + +In the collision cases in this subclause, if the XID or SABM command that shall be ignored and treated as not transmitted contains one or more XID parameters that are not negotiated as part of the collision resolution, then negotiation of these XID parameters shall be performed at the earliest opportunity after conclusion of the collision resolution. + +If the MS receives an XID command with a valid XID information field that contains the Reset parameter, or if during a PS handover the MS receives a request from the lower layers to perform a Reset with or without old XID indicator, the MS shall abort any ongoing XID negotiation and treat the received XID command or request from the lower layers. This requirement takes precedence over the collision cases in this subclause. + +#### 8.5.5.1 Identical transmitted and received commands + +If the transmitted and received unnumbered commands are SABM commands and a Layer-3 Parameters XID parameter is present in both or in neither, then the SABM command transmitted by the SGSN shall be ignored and treated as not transmitted. The LLE in the SGSN shall send the UA response at the earliest possible opportunity if it is able to enter ABM. + +If the transmitted and received unnumbered commands are a SABM command with a Layer-3 Parameters XID parameter and a SABM command without a Layer-3 Parameters XID parameter, then the SABM command without Layer-3 Parameters shall be ignored and treated as not transmitted. This is illustrated in figure 19. + +![Sequence diagram illustrating a collision between LLE-initiated and layer 3-initiated ABM establishment procedure. The diagram shows two entities: Originator and Receiver. The Originator has Layer 3 and LLC components. The Receiver has LLC and Layer 3 components. The sequence of messages is: 1. Layer 3 of Originator sends LL-ESTABLISH-REQ to LLC of Originator. 2. LLC of Originator sends SABM to LLC of Receiver. 3. LLC of Receiver receives SABM and sends LL-ESTABLISH-IND to Layer 3 of Receiver. 4. Layer 3 of Receiver sends LL-ESTABLISH-RES to LLC of Receiver. 5. LLC of Receiver sends UA to LLC of Originator. 6. LLC of Originator receives UA and sends LL-ESTABLISH-CNF to Layer 3 of Originator.](0f1767577a073167eb9628d72034e083_img.jpg) + +``` + +sequenceDiagram + participant Originator + subgraph Originator + L3O[Layer 3] + LLO[LLC] + end + subgraph Receiver + LRR[LLC] + L3R[Layer 3] + end + L3O->>LLO: LL-ESTABLISH-REQ + LLO->>LRR: SABM + LRR->>L3R: LL-ESTABLISH-IND + L3R->>LRR: LL-ESTABLISH-RES + LRR->>LLO: UA + LLO->>L3O: LL-ESTABLISH-CNF + +``` + +Sequence diagram illustrating a collision between LLE-initiated and layer 3-initiated ABM establishment procedure. The diagram shows two entities: Originator and Receiver. The Originator has Layer 3 and LLC components. The Receiver has LLC and Layer 3 components. The sequence of messages is: 1. Layer 3 of Originator sends LL-ESTABLISH-REQ to LLC of Originator. 2. LLC of Originator sends SABM to LLC of Receiver. 3. LLC of Receiver receives SABM and sends LL-ESTABLISH-IND to Layer 3 of Receiver. 4. Layer 3 of Receiver sends LL-ESTABLISH-RES to LLC of Receiver. 5. LLC of Receiver sends UA to LLC of Originator. 6. LLC of Originator receives UA and sends LL-ESTABLISH-CNF to Layer 3 of Originator. + +**Figure 19: Collision between LLE-initiated and layer 3-initiated ABM establishment procedure** + +If the transmitted and received unnumbered commands are DISC commands, then the LLEs shall send the UA response at the earliest possible opportunity, and enter ADM state after receiving the UA response. The LLEs shall notify layer 3 by means of the LL-RELEASE-CNF primitive. + +If the transmitted and received unnumbered commands are XID commands and a Layer-3 Parameters XID parameter is present in both or in neither, then the XID command transmitted by the SGSN shall be ignored and treated as not transmitted. + +If the transmitted and received unnumbered commands are an XID command with a Layer-3 Parameters XID parameter and an XID command without a Layer-3 Parameters XID parameter, then the XID command without Layer-3 Parameters shall be ignored and treated as not transmitted. + +#### 8.5.5.2 Different transmitted and received commands + +If the transmitted and received unnumbered commands are a SABM and a DISC command, the LLEs shall issue a DM response at the earliest possible opportunity. Upon receipt of a DM response with the F bit set to 1, the LLE shall enter the ADM state and notify layer 3 by means of the appropriate primitive. The LLE receiving the DISC command shall issue an LL-RELEASE-IND (Cause = 'Normal Release') primitive, while the other LLE shall issue an LL-RELEASE-CNF primitive. + +If the transmitted unnumbered command is a SABM command, and the received unnumbered command is an XID command, then the LLE shall ignore the received XID command. + +If the transmitted unnumbered command is an XID command, and the received unnumbered command is a SABM command, then the LLE shall send the UA response at the earliest possible opportunity if it is able to enter ABM. The transmitted XID command shall be treated as not transmitted. + +If the transmitted and received unnumbered commands are a DISC and an XID command, then this shall not be considered a collision. + +### 8.5.6 Unsolicited DM response and SABM or DISC command + +When a DM response with the F bit set to 0 is received by an LLE, a collision between a transmitted SABM or DISC command and the unsolicited DM response may have occurred. + +In order to avoid misinterpretation of the DM response received, an LLE shall always send its SABM or DISC command with the P bit set to 1. + +A DM response with the F bit set to 0 colliding with a SABM or DISC command shall be ignored. + +## 8.6 Procedures for information transfer in ABM operation + +### 8.6.0 General + +Having either transmitted the UA response to a received SABM command or received the UA response to a transmitted SABM, I frames and supervisory frames may be transmitted and received. The procedures that apply to the transmission of I frames are defined below. + +NOTE: The term "transmission of an I frame" refers to the delivery of an I frame by the LLC layer to the RLC/MAC layer or BSSGP layer. + +Each LLE shall store the history of the transmitted I frames, i.e., the LLE shall remember the I-frame transmission sequence. The history is used to decide which I frames to retransmit. Due to retransmission, the history is not necessarily an in-order sequence. + +A frame within the receive window is either: + +- received: the frame has been correctly received; or +- not received: the frame has not been correctly received. + +A frame within the transmit window is either: + +- not yet transmitted: the frame has not yet been transmitted; +- transmitted: the frame has been (re-)transmitted, but the LLE does not know if the frame has been received in the peer LLE; +- acknowledged: the frame has been acknowledged by the peer LLE; or +- marked for retransmission: the LLE has decided to retransmit this I frame. + +I frames shall be transmitted in ascending N(S) order. When I frames are retransmitted, the frame with the lowest N(S) shall be retransmitted first. This is used by the receiving LLE to detect lost frames as described in subclause 8.6.3.1. + +### 8.6.1 Transmitting I frames + +Information received by the LLE from layer 3 by means of an LL-DATA-REQ primitive shall be transmitted in an I frame, provided that the LLE is not in the peer receiver busy condition. The control field parameters N(S) and N(R) shall be assigned the values V(S) and V(R), respectively. V(S) shall be incremented by 1 at the end of the transmission of the I frame. + +The I frame buffer variable B shall be incremented with the length of the information field of I frame number N(S), so that $B = B + L(N(S))$ . The value of B shall never exceed M. If $L(N(S)) > M - B$ (where M is the maximum buffer size – see subclause 8.9.7), then the LLE shall not transmit any new I frames, but may retransmit I frames as a result of the error recovery procedures as described in subclauses 8.6.3 and 8.6.6. + +When there is an opportunity to transmit a frame, then the LLE shall do one of the following in order of priority: + +- If there are any I frames marked for retransmission and if the LLE is not in the peer receive busy condition, then the LLE shall increment by 1 the retransmission count variable for the I frame with the lowest send sequence number N(S). If the retransmission count variable exceeds the value of N200, then the LLE shall initiate the re-establishment procedure as described in subclause 8.7.2. If the retransmission count variable does not exceed the value of N200, then the LLE shall retransmit the I frame. +- If the LLE has a new I frame to transmit, if $V(S) < V(A) + k$ (where k is the maximum number of outstanding I frames – see subclause 8.9.8), and if the LLE is not in the peer receiver busy condition, then the new I frame shall be transmitted. +- If the LLE has an acknowledgement to transmit (see subclause 8.6.3.1), then the LLE shall transmit an S frame. + +If the LLE wants to request an acknowledgement (see subclause 8.6.3.3), then the A bit of the transmitted frame shall be set to 1. + +When the SGSN or MS is in the own receiver busy condition, it may still transmit I frames, provided that a peer receiver busy condition does not exist. + +![Sequence diagram illustrating the interaction between an Originator and a Receiver for transmitting and receiving I frames. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The sequence of messages is: 1. LL-DATA-REQ from Layer 3 to LLC in the Originator. 2. LL-DATA SENT-IND from LLC to Layer 3 in the Originator. 3. I+S frame from LLC in the Originator to LLC in the Receiver. 4. S or I+S frame from LLC in the Receiver to LLC in the Originator. 5. LL-DATA IND from LLC in the Receiver to Layer 3 in the Receiver. 6. LL-DATA-CNF from Layer 3 to LLC in the Originator.](08f6ace0c83e7394657fa372b47aec04_img.jpg) + +Sequence diagram illustrating the interaction between an Originator and a Receiver for transmitting and receiving I frames. The Originator contains Layer 3 and LLC. The Receiver contains LLC and Layer 3. The sequence of messages is: 1. LL-DATA-REQ from Layer 3 to LLC in the Originator. 2. LL-DATA SENT-IND from LLC to Layer 3 in the Originator. 3. I+S frame from LLC in the Originator to LLC in the Receiver. 4. S or I+S frame from LLC in the Receiver to LLC in the Originator. 5. LL-DATA IND from LLC in the Receiver to Layer 3 in the Receiver. 6. LL-DATA-CNF from Layer 3 to LLC in the Originator. + +**Figure 20: Transmitting and receiving I frames** + +### 8.6.2 Receiving I frames + +When an LLE is not in the own receiver busy condition and receives a valid I frame whose N(S) is equal to the current V(R), the LLE shall: + +- pass the information field of this frame to layer 3 using the LL-DATA-IND primitive; +- increment by 1 its V(R); and +- if the A bit of the received I frame was set to 1, then the LLE shall respond to its peer with an RR, RNR, SACK, or ACK frame (see subclause 8.6.4.1). + +When an LLE receives a valid I frame whose N(S) is not in the range $V(R) \leq N(S) < V(R) + k$ , the LLE shall discard the frame as a duplicate. + +When an LLE is not in the own receiver busy condition and receives a valid I frame where $V(R) < N(S) < V(R) + k$ , then the LLE shall store the I frame until all frames from V(R) to N(S) - 1 inclusive are correctly received. The LLE shall use the control field information of the received I frame before storing the frame. The LLE shall then: + +- pass the information field of this I frame to layer 3 using the LL-DATA-IND primitive; and +- set its $V(R) = N(S) + 1$ . + +When an LLE receives a valid I frame and the LLE is in the own receiver busy condition, then the acceptance of the I frame is implementation dependent. + +### 8.6.3 Sending and receiving acknowledgements + +#### 8.6.3.0 General + +NOTE: Sending and receiving acknowledgements refer to the transmission and reception of frames carrying ABM acknowledgement information, i.e., I+S and S frames. + +#### 8.6.3.1 Sending acknowledgements + +Whenever an LLE receives a frame with the A bit set to 1, it shall transmit an I+S or S frame. Whenever an LLE detects an error in the sequence of received I frames, it shall transmit an I+S or S frame. The supervisory function bits of the transmitted frame shall be set according to subclause 8.6.4.1. + +The receiving LLE shall use the knowledge of the (re-)transmission strategy of its peer LLE (see subclause 8.6.1) to detect sequence errors. If the LLE receives an I frame with a higher N(S) than the N(S) of the previously received I frame, and if there are I frames missing between these two N(S) values, then the LLE shall assume that the missing I frames have been lost. If the LLE receives an I frame with a lower N(S) than the N(S) of the previously received I frame, it can assume that its peer LLE has (re-)started retransmission due to the reception of an acknowledgement. + +#### 8.6.3.2 Receiving acknowledgements + +On receipt of a valid I+S or S frame, the LLE shall, if N(R) is valid, treat the N(R) contained in this frame as an acknowledgement for all the I frames it has transmitted with an N(S) up to and including the received N(R) - 1. A valid N(R) value is one that is in the range $V(A) \leq N(R) \leq V(S)$ . If N(R) is not valid, then the received A bit shall be treated as defined in subclause 8.6.3.1, and N(R), and the SACK bitmap if received, shall be disregarded. + +For each I frame transmitted with N(S) in the range $V(A) \leq N(S) < N(R)$ : + +- the LLE shall issue an LL-DATA-CNF primitive to layer 3 to confirm the delivery of an L3-PDU to layer 3 in the peer; and +- the frame length L(N(S)) shall be subtracted from the I frame buffer variable B, so that $B = B - L(N(S))$ . The value of B shall never be less than 0. + +V(A) shall then be set to N(R). + +On receipt of a valid ACK frame, the LLE shall consider the I frame transmitted with sequence number N(R) + 1 as acknowledged. + +On receipt of a valid SACK frame, the LLE shall consider all I frames with the corresponding bit set to 1 in the SACK bitmap as acknowledged. + +If timer T201 is active and associated with an acknowledged I frame, then timer T201 shall be reset. + +The LLE shall determine which I frames to retransmit by analysing its I frame transmission sequence history and the acknowledgements received. An unacknowledged I frame that was transmitted prior to an acknowledged I frame shall be considered lost and shall be marked for retransmission. Acknowledged I frames shall be removed from the I frame transmission sequence history. + +#### 8.6.3.3 Requesting acknowledgements + +The LLE shall request an acknowledgement from the peer LLE by transmitting an I+S or S frame with the A bit set to 1. The LLE may request an acknowledgement at any time. An acknowledgement shall be requested when: + +- the last I frame in a sequence of one or more I frames is transmitted; or +- $B > M - N201$ as a result of the transmission of the I frame, unless the next I frame to be transmitted is available and has an information field length that is less than or equal to $M - B$ ; or +- $V(S) = V(A) + k$ as a result of the transmission of the I frame. + +When requesting an acknowledgement, the LLE shall set timer T201 and associate the timer with the I frame currently being transmitted, or, if the A bit is transmitted in an S frame, with the I frame last transmitted. + +### 8.6.4 Peer receiver busy condition + +After receiving a valid RNR frame, the LLE shall: + +- set a peer receiver busy condition; +- not transmit nor retransmit any I frames to the peer LLE; +- treat the N(R) contained in the received RNR frame as an acknowledgement for all the I frames that have been (re-)transmitted with an N(S) up to and including N(R) - 1, and set its V(A) to the value of the N(R) contained in the RNR frame; +- set timer T201 to initiate the inquiry process; and +- reset the retransmission count variable. + +If timer T201 expires, the LLE shall: + +- if the value of the retransmission count variable is less than N200: + - transmit an appropriate supervisory frame (see subclause 8.6.4.1) with an A bit set to 1; + - set timer T201; and + - add one to its retransmission count variable; +- if the value of the retransmission count variable is equal to N200, initiate a re-establishment procedure as defined in subclause 8.7. LLME shall indicate this by means of the LLGMM-STATUS-IND primitive to GMM. + +The LLE receiving the supervisory frame with the A bit set to 1 shall respond, at the earliest opportunity, with an appropriate supervisory frame (see subclause 8.6.4.1) to indicate whether or not its own receiver busy condition still exists. + +Upon receipt of the supervisory frame, the LLE shall reset timer T201, and: + +- if the frame is an RR, ACK or SACK frame: + - the peer receiver busy condition shall be cleared; + - if timer T201 was active before the peer receiver busy condition was set, and if the associated I frame is still not acknowledged, then timer T201 shall be set and associated with the same I frame; and + - the LLE may transmit new I frames or retransmit I frames as defined in subclauses 8.6.1 or 8.6.3, respectively; or +- if the frame is an RNR frame, then the LLE shall proceed according to subclause 8.6.4, first paragraph. + +Upon receipt of a SABM command, the LLE shall clear the peer receiver busy condition. + +#### 8.6.4.1 Supervisory frame selection + +If the LLE is in the own receiver busy condition, the appropriate supervisory frame is the RNR frame. + +Otherwise, if the highest-numbered I frame was received with $N(S) = V(R)$ , the appropriate supervisory frame is the RR frame. + +Otherwise, if the highest-numbered I frame was received with $N(S) = V(R) + 1$ , the appropriate supervisory frame is the ACK frame. + +Otherwise, the appropriate supervisory frame is the SACK frame. + +### 8.6.5 Own receiver busy condition + +When the LLE enters the own receiver busy condition, it shall transmit an RNR frame at the earliest opportunity. + +All received I frames may be discarded, after updating $V(A)$ . If the A bit of a received I frame was set to 1, then the LLE shall transmit an RNR frame. + +All received supervisory frames shall be processed, including updating $V(A)$ . If the A bit of a received S frame was set to 1, then the LLE shall transmit an RNR frame. + +To indicate to the peer LLE the clearance of the own receiver busy condition, the LLE shall transmit an appropriate supervisory frame (see subclause 8.6.4.1). + +The transmission of a SABM command or a UA response (in reply to a SABM command) also indicates to the peer LLE the clearance of the own receiver busy condition. + +### 8.6.6 Waiting for acknowledgement + +Frames may be lost any time during transmission due to e.g., transmission errors. An LLE that has not received acknowledgement for a transmitted I frame shall therefore on the expiry of timer T201 take appropriate recovery action. + +The LLE shall maintain an internal retransmission count variable for each transmitted I frame. + +If timer T201 expires, the LLE shall increment by 1 the retransmission count variable for the I frame associated with timer T201, and: + +- if the value of the retransmission count variable does not exceed N200, set timer T201, and retransmit the I frame with the A bit set to 1; or +- if the value of the retransmission count variable exceeds N200, initiate a re-establishment procedure as defined in subclause 8.7.2. LLME shall indicate this by means of the LLGMM-STATUS-IND primitive to GMM. + +## 8.7 Re-establishment of ABM operation + +### 8.7.1 Criteria for re-establishment + +The criteria for re-establishing the ABM mode of operation are defined in this clause by the following conditions: + +- the receipt, while in the ABM state, of a SABM; +- the receipt of an LL-ESTABLISH-REQ primitive from layer 3 (see subclause 8.5.1.1); +- the occurrence of N200 retransmission failures (see subclauses 8.6.4 and 8.6.6); +- the occurrence of a frame rejection condition as identified in subclause 8.8.2; and +- the receipt of an unsolicited DM response with the F bit set to 0 (see subclause 8.8.4) while in ABM state. + +### 8.7.2 Procedures + +In all re-establishment situations, the LLE shall follow the procedures defined in subclause 8.5.1. All locally-generated conditions for re-establishment shall cause the transmission of the SABM. + +In the case of LLC layer and peer-initiated re-establishment, the LLE shall issue an LL-ESTABLISH-IND primitive to layer 3 and discard all outstanding LL-DATA-REQ primitives and all queued I frames, and LLME shall issue an LLGMM-STATUS-IND primitive to GMM. + +In case of layer 3-initiated re-establishment, or if an LL-ESTABLISH-REQ primitive occurs pending re-establishment, the LL-ESTABLISH-CNF primitive shall be used. + +![Sequence diagram illustrating the LLC-initiated ABM re-establishment procedure. The diagram shows two entities: Originator (consisting of Layer 3 and LLC) and Receiver (consisting of LLC and Layer 3). The sequence of messages is: 1. LLC of Originator sends a SABM frame to LLC of Receiver. 2. LLC of Receiver sends a UA response to LLC of Originator. 3. LLC of Originator sends an LL-ESTABLISH-IND primitive to Layer 3 of Originator. 4. LLC of Receiver sends an LL-ESTABLISH-IND primitive to Layer 3 of Receiver.](1230eaa9d75a09d7e7b8509931e9190e_img.jpg) + +``` + +sequenceDiagram + participant L3_O as Layer 3 (Originator) + participant LLC_O as LLC (Originator) + participant LLC_R as LLC (Receiver) + participant L3_R as Layer 3 (Receiver) + + LLC_O->>LLC_R: SABM + LLC_R-->>LLC_O: UA + LLC_O->>L3_O: LL-ESTABLISH-IND + LLC_R->>L3_R: LL-ESTABLISH-IND + +``` + +Sequence diagram illustrating the LLC-initiated ABM re-establishment procedure. The diagram shows two entities: Originator (consisting of Layer 3 and LLC) and Receiver (consisting of LLC and Layer 3). The sequence of messages is: 1. LLC of Originator sends a SABM frame to LLC of Receiver. 2. LLC of Receiver sends a UA response to LLC of Originator. 3. LLC of Originator sends an LL-ESTABLISH-IND primitive to Layer 3 of Originator. 4. LLC of Receiver sends an LL-ESTABLISH-IND primitive to Layer 3 of Receiver. + +**Figure 21: LLC-initiated ABM re-establishment procedure** + +## 8.8 Exception condition reporting and recovery + +### 8.8.0 General + +Exception conditions may occur as the result of lower layer errors or LLC layer procedural errors. + +The error recovery procedures available to effect recovery following the detection of an exception condition at the LLC layer are defined in this subclause. + +### 8.8.1 Invalid frame condition + +Any received invalid frame shall be discarded, and no action shall be taken as a result of that frame. + +### 8.8.2 Frame rejection condition + +A frame rejection condition results from one of the conditions described in subclause 6.4.1.5 items 1) to 3). + +Upon occurrence of a frame rejection condition, the LLME shall issue an LLGMM-STATUS-IND primitive; and the LLE shall: + +- discard the frame causing the frame rejection condition; +- transmit a FRMR response frame; and +- if the LLE is in ABM operation, initiate re-establishment (see subclause 8.7.2). + +### 8.8.3 Receipt of a FRMR response frame + +Upon receipt of a FRMR response frame, the LLME shall issue an LLGMM-STATUS-IND primitive. + +### 8.8.4 Unsolicited response frames + +The action to be taken on the receipt of an unsolicited response frame is defined in table 8. Upon the receipt of an unsolicited UA response, the LLE shall assume a possible multiple-TLLI assignment, and LLME shall inform GMM by means of the LLGMM-STATUS-IND primitive. + +**Table 8: Actions taken on receipt of unsolicited response frames** + +| Unsolicited | State | | | | | +|----------------------|---------------------|---------------------|------------------|--------------------------------------|--------------------------------------| +| | TLLI Assigned / ADM | Local Establishment | Local Release | ABM | Timer Recovery | +| UA response
F = 1 | LLGMM-STATUS-IND | Solicited | Solicited | LLGMM-STATUS-IND | LLGMM-STATUS-IND | +| UA response
F = 0 | LLGMM-STATUS-IND | LLGMM-STATUS-IND | LLGMM-STATUS-IND | LLGMM-STATUS-IND | LLGMM-STATUS-IND | +| DM response
F = 1 | Ignore | Solicited | Solicited | LLGMM-STATUS-IND | LLGMM-STATUS-IND
Re-establish ABM | +| DM response
F = 0 | Ignore | Ignore | Ignore | LLGMM-STATUS-IND
Re-establish ABM | LLGMM-STATUS-IND
Re-establish ABM | +| Supervisory response | Ignore | Ignore | Ignore | Solicited | Solicited | + +A UA or XID response frame with the F bit set to 1, and that does not contain a Layer-3 Parameters XID parameter, received while a SABM or XID command respectively that does contain a Layer-3 Parameters XID parameter is outstanding, shall be ignored. + +A UA or XID response frame with the F bit set to 1, and that contains a Layer-3 Parameters XID parameter, received while a SABM or XID command respectively that does not contain a Layer-3 Parameters XID parameter is outstanding, shall be ignored. + +## 8.9 List of LLC layer parameters + +### 8.9.0 General + +The LLC layer parameters listed in this subclause are associated with each DLCI, except the LLC version number and IOV-UI, i-IOV-UI, i-IOV-UI-cnt and MAC-IOV-UI that are associated with a TLLI. + +A method of assigning these parameters is defined in subclauses 6.4.1.6 and 8.5.3. + +Table 9 provides an overview of the LLC layer parameters and summarises the recommended default values to be used in GSM networks. The term default implies that the value defined should be used in the absence of any negotiation of alternative values. + +Some of the parameters, e.g., T200, T201, and N200, may have the same name as parameters used in other GSM specifications. All the parameters listed here are local to the LLC layer protocol, and shall not impact or be impacted by parameters with the same name in other specifications. + +### 8.9.1 LLC version number (Version) + +The LLC version number (Version) is an LLC layer parameter. The default version number is given in table 9. + +### 8.9.2 Input Offset Values (IOV) + +The Input Offset Values (IOV) are LLC layer parameters used for ciphering and integrity protection. + +For ciphering, the IOV values are IOV-I and IOV-UI. The IOV-I and IOV-UI are random 32 bit values, generated by the SGSN. See also annex A. + +The value for IOV can be different for I frames and UI frames. IOV-UI is IOV for UI frames. IOV-I is IOV for I frames. + +The default values of IOV-I and IOV-UI are given in table 9. The following rules apply to the IOV values for ciphering: + +- After a change of ciphering key to a different value a random IOV-I value shall be negotiated. If ABM is re-established for an LLE, and ciphering key is not changed to a different value since ABM was last (re-)established for this LLE, then a random IOV-I value shall be negotiated. +- After a change of ciphering key to a different value, a random IOV-UI value shall be negotiated. If the unconfirmed send state variable V(U) is reset for an LLE, and ciphering key is not changed to a different value since V(U) was last reset for this LLE, then a random IOV-UI value shall be negotiated. + +For integrity protection, the IOV values are i-IOV-UI and i-IOV-UI-cnt. The i-IOV-UI is used for UI frames and is a random 32 bit value, generated by the SGSN. See also 3GPP TS 43.020 [27]. + +The default values of i-IOV-UI and i-IOV-UI-cnt are given in table 9. The following rules apply to the IOV values for integrity protection: + +- After a successful authentication, a random i-IOV-UI value shall be negotiated. If the unconfirmed send state variable V(U) is reset for an LLE, and integrity key is not changed to a different value since V(U) was last reset for this LLE, then a random i-IOV-UI value shall be negotiated. +- After a successful authentication, both the MS and the SGSN shall store a local counter i-IOV-UI-cnt showing the number of IOV updates since the previous authentication. The counter is incremented by 1 every time the SGSN updates the IOV values. The i-IOV-UI-cnt in the MS side represents the number of successful IOV updates, and shall have the same or a lower value than the value received from the SGSN. + +NOTE: The maximum acceptable difference between the value of the i-IOV-UI-cnt stored in the MS and the new value received from the SGSN is implementation specific. + +The default value of MAC-IOV-UI is given in table 9. The MAC-IOV-UI is calculated over the IOV values for ciphering and integrity protection that are included in the same XID command. See 3GPP TS 43.020 [27] annex H.9.1 for further details. + +### 8.9.3 Retransmission timers (T200 and T201) + +The retransmission timers (T200 and T201) are LLC layer parameters. Upon expiry of timer T200 or T201, retransmission of a frame may be initiated according to the procedures described in clause 8. The default value of timers T200 and T201 for each SAPI is given in table 9. The value of timer T200 shall be used when setting timer T201. + +### 8.9.4 Maximum number of retransmissions (N200) + +The maximum number of retransmissions of a frame (N200) is an LLC layer parameter. The default value of N200 for each SAPI is given in table 9. + +### 8.9.5 Maximum number of octets in an information field (N201) + +The maximum number of octets in an information field (N201) is an LLC layer parameter. See also subclause 5.4. The default value of N201 for each SAPI is given in table 9. The minimum value of N201 shall be 140 octets, and the maximum value shall be 1 520 octets. + +NOTE: For an LLC frame with integrity protection, the MAC field is included in the information field. When the MAC field is included in the message, the maximum length of the integrity protected message is N201 – 4 octets (see subclause 5.1). + +The value of N201 may be different for I frames and U and UI frames. N201-U is used for U and UI frames, and N201-I is used for I frames. + +### 8.9.6 Maximum number of octets in the layer-3 header (N202) + +The maximum number of octets in the layer-3 unitdata PDU header (N202) is an LLC layer parameter. The N202 value shall be 4 for LLC version number 0. + +NOTE: The N202 value of 4 octets coincides with the maximum-length SNDCP SN-UNITDATA PDU header. + +### 8.9.7 Maximum I frame buffer size (m) + +The maximum I frame buffer size (m) that may be used to buffer outstanding I frame information fields at any given time is an LLC layer parameter that shall be either 0 or from 9 through 24 320 in units of 16 octets. The default values of m are given in table 9. If the value of m equals 0, then the LLE shall not keep count of the number of outstanding I frame octets, i.e. the I frame buffer variable B shall not be used. M is the maximum buffer size expressed in octets, so that $M = m \times 16$ . + +The value of m can be different in each direction of transmission. mD is m in the downlink direction. mU is m in the uplink direction. + +### 8.9.8 Maximum number of outstanding I frames (k) + +The maximum number (k) of sequentially-numbered I frames that may be outstanding (i.e. unacknowledged) at any given time is an LLC layer parameter that shall not exceed 255. k is also denoted window size. The default values of k are given in table 9. + +The value of k can be different in each direction of transmission. kD is k in the downlink direction, and kU is k in the uplink direction. + +## 8.9.9 LLC layer parameter default values + +**Table 9: LLC layer parameter default values** + +| LLC Parameter | SAPI 1
GMM | SAPI 2
TOM 2 | SAPI 3
User
Data 3 | SAPI 5
User
Data 5 | SAPI 7
SMS | SAPI 8
TOM 8 | SAPI 9
User
Data 9 | SAPI 11
User
Data 11 | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------|-----------------------------|---------------|-----------------|-----------------------------|---------------------------------| +| Version | 0 | | | | | | | | +| IOV-UI | 0 | | | | | | | | +| i-IOV-UI | 0 | | | | | | | | +| i-IOV-UI-cnt | 0 | | | | | | | | +| MAC-IOV-UI | 0 | | | | | | | | +| IOV-I | Note 2 | Note 2 | $2^{27} \times \text{SAPI}$ | $2^{27} \times \text{SAPI}$ | Note 2 | Note 2 | $2^{27} \times \text{SAPI}$ | $2^{27} \times \text{SA}$
PI | +| T200 and
T201 | 5 s | 5 s | 5 s | 10 s | 20 s | 20 s | 20 s | 40 s | +| N200 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| N201-U | 400 | 270 | 500 | 500 | 270 | 270 | 500 | 500 | +| N201-I | Note 2 | Note 2 | 1 503 | 1 503 | Note 2 | Note 2 | 1 503 | 1 503 | +| mD | Note 2 | Note 2 | 1 520 | 760 | Note 2 | Note 2 | 380 | 190 | +| mU | Note 2 | Note 2 | 1 520 | 760 | Note 2 | Note 2 | 380 | 190 | +| kD | Note 2 | Note 2 | 16 | 8 | Note 2 | Note 2 | 4 | 2 | +| kU | Note 2 | Note 2 | 16 | 8 | Note 2 | Note 2 | 4 | 2 | +| T100 | 3s | 3s | 3s | 3s | 3s | 3s | 3s | 3s | +| NOTE 1: | Proper LLC operation requires that timer T200 be greater than the maximum time between transmission of command frames and the reception of their corresponding response or acknowledgement frames. | | | | | | | | +| NOTE 2: | This parameter applies to ABM procedures. ABM operation is not allowed for GMM, SMS, and TOM that use only UI frames for information transfer. | | | | | | | | +| NOTE 3: | The default values for SAPIs 3, 5, 9, and 11 have been chosen to correspond with the four GPRS quality of service delay classes, see 3GPP TS 22.060 [3]. However, there is no fixed relationship between SAPI and delay class. The LLC layer parameters for any SAPI can be negotiated to support any QoS profile, see 3GPP TS 23.060 [5]. | | | | | | | | +| NOTE 4: | Proper LLC operation requires that the values for N201-U and N201-I are not greater than the maximum number of octets in an information field that can be transmitted or retransmitted over the Gb interface, see 3GPP TS 48.018 [12]. It is the responsibility of the SGSN to negotiate N201-U and N201-I to values compatible with the usage of the Gb interface. | | | | | | | | + +## Annex A (normative): Ciphering + +### A.1 General + +This annex specifies how LLC shall interface with the GPRS ciphering algorithm. The requirements for the GPRS ciphering algorithm are contained in 3GPP TS 41.061 [2] (for GEA algorithms which require 64-bit ciphering key or $K_c$ ), and in 3GPP TS 43.020 [27] (for GEA algorithms which require 128-bit ciphering key or $K_{c128}$ ). + +### A.2 Ciphering algorithm interface + +#### A.2.0 General + +The ciphering algorithm has three input parameters: + +- the ciphering key ( $K_c$ or $K_{c128}$ ); +- the frame-dependent input (Input); and +- the transfer direction (Direction). + +The ciphering algorithm has one output parameter: + +- Output. + +The relationship between the input and output parameters and the ciphering algorithm is illustrated in figure A.1. + +![Diagram of the GPRS ciphering environment showing the flow from Unciphered Frame to Ciphered Frame and then to Deciphered Frame, with the Ciphering Algorithm and XOR operations involved.](48952b53cfa7fc5afa57e46ca69abe1a_img.jpg) + +The diagram illustrates the GPRS ciphering environment. It shows two main processes: encryption and decryption. + +**Encryption Process (Left):** An **Unciphered Frame** is input to an XOR operation (represented by a circle with an 'X'). The other input to the XOR operation is the **Output** of a **Ciphering Algorithm**. The **Ciphering Algorithm** takes three inputs: **Input**, **Direction**, and **Ciphering Key**. The output of the XOR operation is a **Ciphered Frame**. This process is labeled **MS or SGSN**. + +**Decryption Process (Right):** A **Ciphered Frame** is input to an XOR operation. The other input to the XOR operation is the **Output** of a **Ciphering Algorithm**. The **Ciphering Algorithm** takes three inputs: **Input**, **Direction**, and **Ciphering Key**. The output of the XOR operation is a **Deciphered Frame**. This process is labeled **SGSN or MS**. + +Diagram of the GPRS ciphering environment showing the flow from Unciphered Frame to Ciphered Frame and then to Deciphered Frame, with the Ciphering Algorithm and XOR operations involved. + +**Figure A.1: GPRS ciphering environment** + +The input and output parameters and the other elements from figure A.1 are defined in table A.1. + +**Table A.1: Ciphering parameters and frames** + +| Parameter | Length | Description | +|---------------------|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Kc | 64 bits | The LLGMM-ASSIGN-REQ Ciphering Key parameter received from GMM. | +| Kc 128 | 128 bits | The LLGMM-ASSIGN-REQ Ciphering Key parameter received from GMM. | +| Input | 32 bits | A modulo counter as defined in subclause A.2.1. | +| Direction | 1 bit | Set to 0 if the direction of LLC frame transmission is from the MS to the SGSN.
Set to 1 if the direction of LLC frame transmission is from the SGSN to the MS. | +| Ciphering Algorithm | - | A GPRS ciphering algorithm as determined by the LLGMM-ASSIGN-REQ Ciphering Algorithm parameter received from GMM. | +| Output | maximum 1 523 octets | The output of Ciphering Algorithm — a sequence of octets. | +| Unciphered Frame | maximum 1 523 octets | An LLC layer I or UI frame to be ciphered. | +| Ciphered Frame | maximum 1 523 octets | A ciphered LLC layer I or UI frame. Only the information field and the FCS field shall be ciphered. Ciphered Frame shall be generated by XORing the octets of Output and the information field and the FCS field of Unciphered Frame, starting with the lowest numbered octet of Unciphered Frame. | +| Deciphered Frame | maximum 1 523 octets | A deciphered LLC layer I or UI frame. Deciphered Frame shall be generated by XORing the octets of Output and the ciphered part of Ciphered Frame, starting with the lowest numbered octet of Ciphered Frame. When transmitting an LLC frame, Deciphered Frame shall be identical to Unciphered Frame if no transmission errors have occurred. | + +It is an implementation option to optimise the ciphering algorithm by for example producing only as many Output octets as is needed to cipher Unciphered Frame. + +## A.2.1 Generation of Input + +The Input parameter shall be generated according to the following algorithm if the frame is a UI frame: + +$$\text{Input} = ( ( \text{IOV-UI} \otimes \text{SX} ) + \text{LFN} + \text{OC} ) \text{ modulo } 2^{32}$$ + +The Input parameter shall be generated according to the following algorithm if the frame is an I frame: + +$$\text{Input} = ( \text{IOV-I} + \text{LFN} + \text{OC} ) \text{ modulo } 2^{32}$$ + +where: + +- IOV-UI is a 32 bit random value generated by the SGSN. +- IOV-I is a 32 bit random value generated by the SGSN. +- LFN is the LLC frame number in the LLC frame header. LFN is a binary value with a length of nine bits. For I frames, N(S) shall be used as the LFN. For UI frames, N(U) shall be used as the LFN. +- OC is a binary overflow counter that is calculated and maintained independently at the sending and receiving sides. The length of OC is 32 bits. There are four OC counters associated with each DLCI; two for unacknowledged information transfer (one for each direction of transmission), and two for acknowledged information transfer (one for each direction of transmission). An OC for acknowledged operation shall be set to 0 whenever ABM operation is (re-)established for the corresponding DLCI. OC shall be incremented by 512 every time when the corresponding LFN rolls over, i.e., when LFN exhausts its modulo and restarts counting from 0, so that OC and LFN when added together in effect is a 32 bit modulo $2^{32}$ counter. +- SX is a 32 bit SAPI XOR mask calculated as follows: $\text{SX} = 2^{27} \times \text{SAPI} + 2^{31}$ . +- + is the binary addition operation. +- $\otimes$ is the bitwise XOR operation. + +## Annex B (normative): Tunnelling of Messages (TOM) + +Tunnelling of Messages (TOM) is a generic protocol layer used for the exchange of TOM Protocol Envelopes (see figure B.1) between the MS and the SGSN. TOM uses two LLC SAPs, one for high-priority messages and another for low-priority messages. The TOM Protocol Envelope is composed of a TOM Protocol Header (containing one or more octets) and a Message Capsule. The TOM Protocol Header contains information about the specific application using the TOM protocol layer and any other TOM Protocol Discriminator-specific information. The Message Capsule is the actual payload of information in the TOM Protocol Envelope. One of the uses of the TOM protocol layer is to tunnel signalling messages between an MS and a non-GSM MSC/VLR when GPRS network elements are used in non-GSM networks. See 3GPP TS 23.060 [5] and 3GPP TS 29.018 [23a]. The TOM protocol layer is also used to tunnel Radio Resource LCS Protocol (RRLP) messages. See 3GPP TS 43.059[25] and 3GPP TS 44.031[24]. + +### B.1 TOM Protocol Envelope structure + +#### B.1.0 TOM Protocol Envelope format + +All TOM protocol peer-to-peer exchanges shall be in TOM Protocol Envelopes conforming to the format shown in figure B.1. The TOM Protocol Header shall consist of the TOM Protocol Discriminator, Remaining Length of TOM Protocol Header, and Remaining Octets of TOM Protocol Header fields, and is a minimum of 1 octet and a maximum of 15 octets long. + +![](077f85b82901283b4657fd2b45fc0294_img.jpg) + +| | | | | | | | | +|----------------------------------------------------------------------------------------------------------|---|---|---|-------------------------------|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Remaining Length
of TOM Protocol
Header | | | | TOM Protocol
Discriminator | | | | +| Remaining Octets of TOM Protocol
Header
(variable length, max. 14 octets) | | | | | | | | +| Message Capsule
(variable length, max. application
specific)
(variable length, max. 220 octets) | | | | | | | | + +**Figure B.1: TOM Protocol Envelope format** + +NOTE: When the TOM Protocol Discriminator indicates TIA/EIA-136, the maximum size of the message capsule is 220 octets (see TIA/EIA-136 [22]). +When the TOM Protocol Discriminator indicates RRLP, the maximum size of the message capsule is 242 octets (see 3GPP TS 44.031 [24]). + +#### B.1.1 TOM Protocol Discriminator + +TOM Protocol Discriminator indicates the specific protocol using TOM, and is coded as follows: + +| | | | | | | +|------|---|---|---|---|-------------------------------------| +| bits | 4 | 3 | 2 | 1 | | +| | 0 | 0 | 0 | 0 | Not specified | +| | 0 | 0 | 0 | 1 | TIA/EIA-136 (see TIA/EIA-136 ([22]) | +| | 0 | 0 | 1 | 0 | RRLP (see 3GPP TS 44.031 [24]) | +| | 1 | 1 | 1 | 1 | Reserved for extension | + +All other values are reserved + +If any other value than '0 0 0 1' or '0 0 1 0' is received, then the TOM Protocol Envelope shall be discarded with no further action. + +## B.1.2 Remaining Length of TOM Protocol Header + +Remaining Length of TOM Protocol Header indicates the number of octets remaining in the TOM-protocol-header part of the TOM Protocol Envelope, and is coded as follows: + +| bits | 8 | 7 | 6 | 5 | +|--------------------------------------------|---|---|---|---| +| 0 | 0 | 0 | 0 | 0 | +| octets remaining in TOM protocol header | | | | | +| 0 | 0 | 0 | 1 | 1 | +| octet remaining in TOM protocol header | | | | | +| 1 | 1 | 1 | 0 | 1 | +| 14 octets remaining in TOM protocol header | | | | | +| 1 | 1 | 1 | 1 | 1 | +| Reserved for extension | | | | | + +If the value 1 1 1 1 is received, then the TOM Protocol Envelope shall be discarded with no further action. + +## B.1.3 Remaining Octets of TOM Protocol Header + +This field contains the octets following the first octet in the TOM-protocol-header. If present, the interpretation of the information contained in this field is TOM Protocol Discriminator-specific. + +## B.1.4 Message Capsule + +This field contains TOM Protocol Discriminator-specific payload in the TOM Protocol Envelope. + +## Annex C (informative): LLC layer states for peer-to-peer operation + +### C.1 General + +The purpose of this annex is to provide a representative example of the peer-to-peer procedures of the LLC layer, to assist in the understanding of the present document. This representation does not describe all of the possible actions of the LLC layer. The representation does therefore not constrain implementations from exploiting the full scope of the procedures as presented within the text of the present document. The text description of the procedures is normative. + +The representation is a model of the peer-to-peer procedures of the LLC layer and is applicable to the LLC layers at both the MS and SGSN sides for all ranges of TLLI values. + +![Figure C.1: Model of the LLC layer peer-to-peer procedures. The diagram shows two 'Service user' entities (one on the MS side, one on the network side) connected via a 'PTP connection'. Each service user is connected to an 'LLC layer' box. Inside each LLC layer box, there are 'Management procedures' and 'Point-to-point procedures' boxes. Arrows indicate the flow of data and control between the service users, the LLC layers, and the procedures.](9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg) + +The diagram illustrates the model of the LLC layer peer-to-peer procedures. It features two 'Service user' entities, one labeled '(MS side)' and the other '(network side)'. Each service user is connected to an 'LLC layer' box. Inside each LLC layer box, there are two sub-components: 'Management procedures' and 'Point-to-point procedures'. Arrows indicate the flow of data and control: from the service user to the point-to-point procedures, from the point-to-point procedures to the management procedures, and from the management procedures to the point-to-point procedures. A 'PTP connection' line connects the point-to-point procedures of the MS side to those of the network side. + +Figure C.1: Model of the LLC layer peer-to-peer procedures. The diagram shows two 'Service user' entities (one on the MS side, one on the network side) connected via a 'PTP connection'. Each service user is connected to an 'LLC layer' box. Inside each LLC layer box, there are 'Management procedures' and 'Point-to-point procedures' boxes. Arrows indicate the flow of data and control between the service users, the LLC layers, and the procedures. + +**Figure C.1: Model of the LLC layer peer-to-peer procedures** + +### C.2 An overview of the peer-to-peer LLC layer states + +The state diagram representation of the peer-to-peer procedures is based on an expansion of the three basic states identified in subclause 4.5.2 to 7 states. An overview of the inter-relationship of these states is provided in figure C.2. + +An LLME and its LLEs are conceptually initiated in the TLLI Unassigned state (state 1). LLME interacts with GMM in order to be assigned a TLLI value. TLLI assignment causes LLME to transition to the TLLI Assigned state (state 2) and each of its LLEs to transition to the ADM state (state 2). + +The receipt of an LL-ESTABLISH-REQ primitive by an LLE in the ADM state (state 2) causes the initiation of the local establishment procedure and the transition to the Local Establishment state (state 3). Completion of the establishment procedure takes the LLE to the ABM state (state 5). + +Peer-initiated establishment causes a transition from the ADM state (state 2) to the Remote Establishment state (state 4). The receipt of an LL-ESTABLISH-RES primitive completes the establishment procedure and moves the LLE to the ABM state (state 5). In ABM state (state 5), LL-DATA-REQ primitives can be serviced directly subject to the restrictions of the procedures. + +Expiry of timer T200, that is used in both the flow control and data transfer aspects of each LLE's procedures initiates the transition to the Timer Recovery state (state 7). Completion of the timer recovery procedures returns the LLE to the ABM state (state 5). In states 5 and 7, the following conditions that are identified within the LLC specification are observed: + +- peer receiver busy; and +- own receiver busy. + +A peer-initiated release takes the LLE directly to the ADM state (state 2), whilst an LL-RELEASE-REQ returns the LLE state to the ADM state via the Local Release state (state 6). + +TLLI Unassignment causes a transition to the TLLI Unassigned state (state 1) from any other state (states 2-7). Reset causes a transition to the TLLI Assigned / ADM state (state 2) from any other state except state 1. + +In addition, all states should observe the suspended operation (reception of LLGMM-SUSPEND-REQ) restrictions, during which LLC frames may not be transmitted. + +![State transition diagram for peer-to-peer procedures. It shows states 1 (TLLI Unassigned), 2 (TLLI Assigned / ADM), 3 (Local Establishment), 4 (Remote Establishment), 5 (ABM), 6 (Local Release), and 7 (Timer Recovery). Transitions include TLLI Unassignment, TLLI Assignment, Reset, Release Confirm, Release Request, Release Indication, Establish Request, Establish Response, Establish Confirm, T200 Expiry, and Completion of Timer Recovery. The diagram is divided into 'Per TLLI' and 'Per DLCI' sections.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +The diagram illustrates the state transitions for peer-to-peer procedures, organized into two sections: 'Per TLLI' and 'Per DLCI'. + +- Per TLLI:** + - Any State** (Initial state) transitions to **1 TLLI Unassigned** via **TLLI Unassignment**. + - 1 TLLI Unassigned** has a self-loop for **SGSN only: Reception of XID or UI frame with SAPI=1**. + - 1 TLLI Unassigned** transitions to **2 TLLI Assigned / ADM** via **TLLI Assignment**. + - 2 TLLI Assigned / ADM** has a self-loop for **Reset** back to **Any State**. +- Per DLCI:** + - 2 TLLI Assigned / ADM** transitions to **3 Local Establishment** via **Establish Request**. + - 3 Local Establishment** transitions to **4 Remote Establishment** via **Establish Confirm**. + - 4 Remote Establishment** transitions to **5 ABM** via **Establish Response**. + - 5 ABM** transitions to **6 Local Release** via **Release Request**. + - 6 Local Release** transitions to **7 Timer Recovery** via **Release Indication**. + - 7 Timer Recovery** transitions to **2 TLLI Assigned / ADM** via **Completion of Timer Recovery**. + - 7 Timer Recovery** also has a self-loop for **T200 Expiry N200 Times**. + - 2 TLLI Assigned / ADM** transitions to **4 Remote Establishment** via **Establish Indication**. + - 5 ABM** transitions to **2 TLLI Assigned / ADM** via **Release Indication**. + - 5 ABM** transitions to **3 Local Establishment** via **Establish Confirm**. + - 5 ABM** transitions to **7 Timer Recovery** via **T200 Expiry**. + +State transition diagram for peer-to-peer procedures. It shows states 1 (TLLI Unassigned), 2 (TLLI Assigned / ADM), 3 (Local Establishment), 4 (Remote Establishment), 5 (ABM), 6 (Local Release), and 7 (Timer Recovery). Transitions include TLLI Unassignment, TLLI Assignment, Reset, Release Confirm, Release Request, Release Indication, Establish Request, Establish Response, Establish Confirm, T200 Expiry, and Completion of Timer Recovery. The diagram is divided into 'Per TLLI' and 'Per DLCI' sections. + +Figure C.2: Overview of the states of the peer-to-peer procedures + +## Annex D (informative): Change History + +| TSG Meeting | TSG Doc number | TSG WG doc number | Spec | CR | R v | Ph | Ca t | Vers Old | Vers New | Subject | Workitem | Remarks | +|-------------|----------------|-------------------|--------|------|-----|--------|------|----------|----------|-------------------------------------------------------------------------------|------------|-----------------------------------------| +| NP-09 | NP-000441 | N1-000987 | 04.64 | A143 | 1 | R99 | F | 8.4.0 | 8.5.0 | Corrections regarding NULL frame | GPRS | | +| NP-10 | NP-000670 | N1-001195 | 04.64 | A145 | | R99 | F | 8.5.0 | 8.6.0 | Correction in TOM protocol header | GPRS | | +| NP-10 | NP-000670 | N1-001199 | 04.64 | A148 | | R99 | A | 8.5.0 | 8.6.0 | Correction of IOV-UI negotiation | GPRS | | +| NP-11 | | | 44.064 | | | Rel-4 | | 8.6.0 | 4.0.0 | Release 4 version after CN#11 | | | +| NP-12 | NP-010271 | N1-010759 | 44.064 | 001 | | Rel-4 | B | 4.0.0 | 4.1.0 | Addition of UI Dummy command for use in RLC/MAC delayed TBF release procedure | TEI4 | | +| NP-14 | NP-010648 | N1-011849 | 44.064 | 004 | | Rel-4 | A | 4.1.0 | 4.2.0 | Conditions for IOV reset | GPRS | | +| NP-14 | NP-010658 | N1-012038 | 44.064 | 002 | 3 | Rel-5 | B | 4.2.0 | 5.0.0 | Introduction of a new TOM protocol discriminator for RRLP | LCS | | +| NP-15 | NP-020040 | N1-0202767 | 44.064 | 006 | | Rel-5 | A | 5.0.0 | 5.1.0 | Correction of references | TEI4 | Additional editorial clean-up from MCC. | +| NP-26 | NP-040515 | N1-041940 | 44.064 | 008 | | Rel-6 | F | 5.1.0 | 6.0.0 | Improvement of the suspension duration due to a cell update | TEI6 | | +| | | | | | | | | 6.0.0 | 6.0.1 | Word problem fixed | | | +| CP-29 | CP-050449 | C1-050920 | 44.064 | 013 | 2 | Rel-6 | B | 6.0.1 | 6.1.0 | Modifications for PS HO in A/Gb mode | SPSHA GB | | +| CP-34 | CP-060670 | C1-062406 | 44.064 | 016 | 1 | Rel-7 | C | 6.1.0 | 7.0.0 | Introduction of a safe timer for PS HO | TEI7 | | +| CP-35 | CP-070131 | C1-070502 | 44.064 | 018 | 1 | Rel-7 | A | 7.0.0 | 7.1.0 | Bit ordering of the key sequence in GEA3 | TEI6 | | +| CP-37 | CP-070599 | C1-072000 | 44.064 | 020 | 1 | Rel-7 | F | 7.1.0 | 7.2.0 | Use of the LLC UI dummy command | LATRE D | | +| CP-39 | CP-080128 | C1-080254 | 44.064 | 021 | | Rel-7 | F | 7.2.0 | 7.3.0 | Correction to the Table 4 | TEI7 | | +| CP-42 | | | | | | Rel-8 | | 7.3.0 | 8.0.0 | Upgrade to Rel-8 | | | +| CP-45 | CP-090692 | C1-093823 | 44.064 | 022 | 1 | Rel-9 | B | 8.0.0 | 9.0.0 | Introduction of 128-bit ciphering key | A5/4-GEA4 | | +| CP-51 | CP-110204 | C1-111514 | 44.064 | 023 | 2 | Rel-10 | B | 9.0.0 | 10.0.0 | Set N(u) for MOCN support | MOCN-GERAN | | +| CP-54 | CP-110862 | C1-114392 | 44.064 | 030 | 1 | Rel-10 | A | 10.0.0 | 10.1.0 | Remove default values for IOV-I, IOV-UI | TEI4 | | + +| TSG Meeting | TSG Doc number | TSG WG doc number | Spec | CR | R v | Ph | Ca t | Vers Old | Vers New | Subject | Workitem | Remarks | +|-------------|----------------|-------------------|--------|------|-----|--------|------|----------|----------|-----------------------------------------|----------------------|---------| +| CP-56 | CP-120309 | C1-122385 | 44.064 | 0031 | 1 | Rel-11 | F | 10.1.0 | 11.0.0 | LLC acknowledged mode optional | TEI11 | | +| CP-65 | | | 44.064 | | | Rel-12 | | 11.0.0 | 12.0.0 | Upgrade to Rel-12 | | | +| CP-70 | | | 44.064 | | | Rel-13 | | 12.0.0 | 13.0.0 | Upgrade to Rel-13 | | | +| CP-72 | CP-160310 | C1-162794 | 44.064 | 0032 | 3 | Rel-13 | | 13.0.0 | 13.1.0 | Addition of integrity protection to LLC | EASE_EC_GS M, TEI-13 | | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | CT#73 | CP-160491 | 0033 | 1 | B | Addition of primitives due to integrity protection | 13.2.0 | +| 2016-12 | CT#74 | CP-160725 | 0034 | 4 | F | Addition of IoV counter | 13.3.0 | +| 2016-12 | CT#74 | CP-160725 | 0035 | | F | Removal of the Editor's Note on the MAC field mapping | 13.3.0 | +| 2017-03 | CT#75 | CP-170110 | 0036 | | F | Correction to the LLC Frame format with integrity protection | 13.4.0 | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2017-06 | CT#76 | CP-171063 | 0039 | 1 | A | Removal of Editor's note on calculation of MAC-IOV-UI | 14.1.0 | +| 2017-09 | CT#77 | CP-172091 | 0041 | | A | Clarification of "currently available" IOV values for ciphering and integrity protection | 14.2.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88e | | | | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44065/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/marked/Rel-16/44_series/44065/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56c407b8318a9d18e3ea0f6e83f7921672f53bd6 --- /dev/null +++ b/marked/Rel-16/44_series/44065/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:166324b32b349e937856dd8f7e4b4bfa9ae45fd856d6ec4cf9aaaa8afe6c3a7c +size 44282 diff --git a/marked/Rel-16/44_series/44065/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-16/44_series/44065/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d6d760f0fde06b9cde131f8a5762d14bec234f2 --- /dev/null +++ b/marked/Rel-16/44_series/44065/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e571a58e50c570ec24eb21aa87683471176c135028dced80d1d7f8ad591a3a9e +size 68080 diff --git a/marked/Rel-16/44_series/44065/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/Rel-16/44_series/44065/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1d9afb52795fb143441c663f39a28c3f9289f76 --- /dev/null +++ b/marked/Rel-16/44_series/44065/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05270d3c6d2d9af5dfd7cdaccbe3c3a988515d827865c9fc5ed3f3676a17cc15 +size 37181 diff --git a/marked/Rel-16/44_series/44065/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/marked/Rel-16/44_series/44065/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51bd706a8892ddc8dec914a88a7d978fb9ab9835 --- /dev/null +++ b/marked/Rel-16/44_series/44065/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35147bc0438394e4c89c81da49ca1312474f07c9e859c6c450d6d4fbb4fca9b2 +size 44869 diff --git a/marked/Rel-16/44_series/44065/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/44_series/44065/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef7ce3d9c1d7c642d9a8b296a65d97efd30024db --- /dev/null +++ b/marked/Rel-16/44_series/44065/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9365f3b1ca520d698ea4af9dbd6dec0ebc3e46fa3e4c41c0659b72b30e59cfa7 +size 72639 diff --git a/marked/Rel-16/44_series/44065/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/44_series/44065/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd2904206cc8cdfcae73e2e384644a70855d86b1 --- /dev/null +++ b/marked/Rel-16/44_series/44065/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aba1009ae01dc45668d1b25562cbeb315a36ac90b5114590b3d6e719dbde690a +size 117813 diff --git a/marked/Rel-16/44_series/44065/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/44_series/44065/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee5d5c9a5b487e17b52622136c8400f1c75e5fa7 --- /dev/null +++ b/marked/Rel-16/44_series/44065/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7aa1ea3d9e261083ecfb541fba46333ef53832761255dff237a79f63e43bb74 +size 50754 diff --git a/marked/Rel-16/44_series/44065/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-16/44_series/44065/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b303ee0824cc934b8f1f6a131fff146b227b336c --- /dev/null +++ b/marked/Rel-16/44_series/44065/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c61eb2bba3171225472591dcdf6bf0d192f189622bd1ca66daf41f6bcea212d +size 39773 diff --git a/marked/Rel-16/44_series/44065/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/44_series/44065/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95c5e9fc0fa8aff509fce96e210d33dcda2fbc18 --- /dev/null +++ b/marked/Rel-16/44_series/44065/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ff21fa9ae4dcd67ed4062de246225157517f009842d378cd3d56e534a99541c +size 40013 diff --git a/marked/Rel-16/44_series/44065/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/44_series/44065/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2ceae6e21dc866a2590735743095e72df5cc6a8 --- /dev/null +++ b/marked/Rel-16/44_series/44065/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:478cb3bc5943a455f674d5ad19c931cb1ab66c348d4c93e0240d45ca23a7f6b5 +size 58204 diff --git a/marked/Rel-16/44_series/44065/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-16/44_series/44065/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da400ef44033ca84710bf5233d291e70bbce3dba --- /dev/null +++ b/marked/Rel-16/44_series/44065/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f1961ec7cdd8e7adc2a6d1254ec1892e5a922ea8b4e8a084ba89c13a889efd0 +size 41671 diff --git a/marked/Rel-16/44_series/44065/raw.md b/marked/Rel-16/44_series/44065/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0d1949785b94724b15fa8ee6495fb5092cf9d4d9 --- /dev/null +++ b/marked/Rel-16/44_series/44065/raw.md @@ -0,0 +1,1862 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 4 General..... | 9 | +| 5 Service primitives and functions..... | 11 | +| 5.1 Service primitives..... | 11 | +| 5.1.1 SNDPC service primitives..... | 11 | +| 5.1.1.1 SN-DATA.request ..... | 12 | +| 5.1.1.2 SN-DATA.indication..... | 12 | +| 5.1.1.3 SN-UNITDATA.request..... | 12 | +| 5.1.1.4 SN-UNITDATA.indication ..... | 12 | +| 5.1.1.5 SN-XID.request ..... | 12 | +| 5.1.1.6 SN-XID.indication ..... | 12 | +| 5.1.1.7 SN-XID.response..... | 12 | +| 5.1.1.8 SN-XID.confirm ..... | 12 | +| 5.1.2 Service primitives used by SNDPC layer..... | 12 | +| 5.1.2.1 LL-RESET.indication ..... | 13 | +| 5.1.2.2 LL-ESTABLISH.request ..... | 14 | +| 5.1.2.3 LL-ESTABLISH.indication..... | 14 | +| 5.1.2.4 LL-ESTABLISH.response..... | 14 | +| 5.1.2.5 LL-ESTABLISH.confirm ..... | 14 | +| 5.1.2.6 LL-RELEASE.request ..... | 14 | +| 5.1.2.7 LL-RELEASE.indication..... | 14 | +| 5.1.2.8 LL-RELEASE.confirm ..... | 15 | +| 5.1.2.9 LL-XID.request..... | 15 | +| 5.1.2.10 LL-XID.indication ..... | 15 | +| 5.1.2.11 LL-XID.response ..... | 15 | +| 5.1.2.12 LL-XID.confirm ..... | 15 | +| 5.1.2.13 LL-DATA.request..... | 15 | +| 5.1.2.14 LL-DATA.indication ..... | 15 | +| 5.1.2.15 LL-DATA.confirm ..... | 15 | +| 5.1.2.16 LL-UNITDATA.request..... | 15 | +| 5.1.2.17 LL-UNITDATA.indication..... | 16 | +| 5.1.2.18 LL-STATUS.indication ..... | 16 | +| 5.1.2.19 SNSM-ACTIVATE.indication ..... | 16 | +| 5.1.2.20 SNSM-ACTIVATE.response ..... | 16 | +| 5.1.2.21 SNSM-DEACTIVATE.indication..... | 16 | +| 5.1.2.22 SNSM-DEACTIVATE.response..... | 16 | +| 5.1.2.23 SNSM-MODIFY.indication ..... | 16 | +| 5.1.2.24 SNSM-MODIFY.response ..... | 17 | +| 5.1.2.25 SNSM-STATUS.request..... | 17 | +| 5.1.2.26 SNSM-SEQUENCE.indication ..... | 17 | +| 5.1.2.27 SNSM-SEQUENCE.response ..... | 18 | +| 5.1.2.28 SNSM-STOP-ASSIGN.indication..... | 18 | +| 5.2 Service functions..... | 18 | +| 6 Protocol functions ..... | 20 | +| 6.1 Multiplexing of N-PDUs..... | 20 | +| 6.2 Establishment and release of acknowledged peer-to-peer LLC operation..... | 20 | +| 6.2.1 Establishment of acknowledged peer-to-peer LLC operation..... | 20 | +| 6.2.1.1 Establishment criteria ..... | 20 | +| 6.2.1.2 Re-establishment of the acknowledged peer-to-peer LLC operation ..... | 21 | +| 6.2.1.3 Establishment procedure..... | 21 | + +| | | | +|-----------|--------------------------------------------------------------------------------|----| +| 6.2.1.4 | Exceptional situations ..... | 22 | +| 6.2.2 | Release of acknowledged peer-to-peer LLC operation ..... | 22 | +| 6.2.2.1 | Release criteria..... | 22 | +| 6.2.2.2 | Release procedure ..... | 23 | +| 6.2.2.3 | Release initiated by the LLC layer ..... | 23 | +| 6.3 | N-PDU buffering..... | 23 | +| 6.4 | Management of delivery sequence..... | 23 | +| 6.5 | Protocol control information compression..... | 23 | +| 6.5.1 | Negotiation of multiple protocol control information compression types ..... | 23 | +| 6.5.1.1 | Format of the protocol control information compression field..... | 24 | +| 6.5.1.1.1 | Spare bit (X)..... | 24 | +| 6.5.1.1.2 | Propose bit (P)..... | 24 | +| 6.5.1.1.3 | Entity number..... | 24 | +| 6.5.1.1.4 | Algorithm identifier..... | 25 | +| 6.5.1.1.5 | PCOMP ..... | 25 | +| 6.5.1.2 | Resetting compression entities following SNDPCP XID negotiation ..... | 26 | +| 6.5.1.3 | Parameters for compression entities ..... | 26 | +| 6.5.2 | TCP/IP header compression (RFC1144)..... | 26 | +| 6.5.2.1 | Parameters..... | 27 | +| 6.5.2.1.1 | Applicable NSAPIs ..... | 27 | +| 6.5.2.1.2 | S 0 ..... | 27 | +| 6.5.2.2 | Assignment of PCOMP values ..... | 27 | +| 6.5.2.3 | Error Recovery..... | 27 | +| 6.5.3 | TCP/IP and UDP/IP header compression (RFC 2507)..... | 27 | +| 6.5.3.1 | Parameters..... | 28 | +| 6.5.3.1.1 | Applicable NSAPIs ..... | 28 | +| 6.5.3.2 | Assignment of PCOMP values for RFC2507 ..... | 28 | +| 6.5.3.3 | Error Recovery..... | 28 | +| 6.5.4 | Robust Header Compression (ROHC) ..... | 28 | +| 6.5.4.1 | Parameters..... | 29 | +| 6.5.4.1.1 | Applicable NSAPIs ..... | 29 | +| 6.5.4.1.2 | MAX_CID..... | 29 | +| 6.5.4.1.3 | MAX_HEADER ..... | 29 | +| 6.5.4.1.4 | (Void)..... | 29 | +| 6.5.4.1.5 | PROFILE..... | 29 | +| 6.5.4.2 | Assignment of PCOMP values for ROHC ..... | 30 | +| 6.5.4.3 | Error Recovery and other feedback ..... | 30 | +| 6.5.5 | Pre-defined Protocol control information ROHC compression types for MBMS ..... | 30 | +| 6.6 | Data compression..... | 31 | +| 6.6.1 | Negotiation of multiple data compression types ..... | 31 | +| 6.6.1.1 | Format of the data compression field ..... | 32 | +| 6.6.1.1.1 | Spare bit (X)..... | 32 | +| 6.6.1.1.2 | Propose bit (P)..... | 32 | +| 6.6.1.1.3 | Entity number..... | 32 | +| 6.6.1.1.4 | Algorithm identifier..... | 32 | +| 6.6.1.1.5 | DCOMP..... | 32 | +| 6.6.1.2 | Resetting compression entities following SNDPCP XID negotiation ..... | 33 | +| 6.6.1.3 | Parameters for compression entities ..... | 33 | +| 6.6.2 | Management of V.42 bis data compression ..... | 33 | +| 6.6.2.1 | Parameters..... | 33 | +| 6.6.2.1.1 | Applicable NSAPIs ..... | 34 | +| 6.6.2.1.2 | P 0 ..... | 34 | +| 6.6.2.1.3 | P 1 ..... | 34 | +| 6.6.2.1.4 | P 2 ..... | 34 | +| 6.6.2.2 | Assignment of DCOMP values..... | 34 | +| 6.6.2.3 | Operation of V.42 bis data compression..... | 34 | +| 6.6.3 | Management of V.44 data compression ..... | 34 | +| 6.6.3.1 | Parameters..... | 34 | +| 6.6.3.1.1 | Applicable NSAPIs ..... | 35 | +| 6.6.3.1.2 | C 0 ..... | 35 | +| 6.6.3.1.3 | P 0 ..... | 35 | + +| | | | +|------------------------|-------------------------------------------------------------------------------------------------------|----| +| 6.6.3.1.4 | P1T ..... | 35 | +| 6.6.3.1.5 | P1R ..... | 36 | +| 6.6.3.1.6 | P3T ..... | 36 | +| 6.6.3.1.7 | P3R ..... | 36 | +| 6.6.3.2 | Assignment of DCOMP values..... | 36 | +| 6.6.3.3 | Operation of V.44 data compression ..... | 36 | +| 6.6.3.3.1 | Packet Method..... | 36 | +| 6.6.3.3.2 | Multi-Packet Method..... | 37 | +| 6.7 | Segmentation and reassembly ..... | 37 | +| 6.7.1 | General ..... | 37 | +| 6.7.1.1 | Segmentation ..... | 37 | +| 6.7.1.2 | Reassembly ..... | 38 | +| 6.7.2 | Segmentation and reassembly in acknowledged mode ..... | 38 | +| 6.7.3 | Segmentation and reassembly in unacknowledged mode ..... | 38 | +| 6.7.4 | Exception situations..... | 39 | +| 6.7.4.1 | Receive First Segment state ..... | 39 | +| 6.7.4.2 | Receive Subsequent Segment state..... | 39 | +| 6.7.4.3 | Discard state..... | 39 | +| 6.8 | XID parameter negotiation..... | 39 | +| 6.8.1 | Negotiation of compression entities ..... | 42 | +| 6.8.1a | Negotiation of SNDCP version ..... | 43 | +| 6.8.2 | Values of SNDCP XID parameters ..... | 43 | +| 6.8.3 | Exception handling ..... | 43 | +| 6.9 | Data transfer ..... | 44 | +| 6.9.1 | Acknowledged mode ..... | 44 | +| 6.9.2 | Unacknowledged mode ..... | 45 | +| 6.10 | Possible combinations of SNDCP protocol functions and their connection to service access points ..... | 46 | +| 7 | Definition of SN-PDU ..... | 47 | +| 7.1 | Format convention..... | 47 | +| 7.1.1 | Numbering convention ..... | 47 | +| 7.1.2 | Order of transmission ..... | 47 | +| 7.1.3 | Field mapping convention ..... | 47 | +| 7.2 | SN-PDU Formats ..... | 48 | +| 8 | SNDCP XID parameters ..... | 49 | +| Annex A (informative): | Change History..... | 51 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS). + +The user of the services provided by SNDCP is a packet data protocol (PDP) at the mobile Station (MS) or the Relay at the Serving GPRS Support Node (SGSN). Additionally, a control entity, e.g. AT command interpreter, may be an SNDCP user. SNDCP uses the services provided by the Logical Link Control (LLC) layer [4] and the Session Management (SM) sub-layer [2]. + +The main functions of SNDCP are: + +- Multiplexing of several PDPs. +- Compression / decompression of user data. +- Compression / decompression of protocol control information. +- Segmentation of a network protocol data unit (N-PDU) into Logical Link Control Protocol Data Units (LL-PDUs) and re-assembly of LL-PDUs into an N-PDU. + +3GPP TS 44.065 is applicable to GPRS MS and SGSN. + +# --- 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.060: "General Packet Radio Service (GPRS); Service Description; Stage 1". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [4] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [5] 3GPP TS 44.018: "Mobile radio interface; Layer 3 specification; Radio Resource Control Protocol". +- [5a] 3GPP TS 24.008: "Mobile radio interface; Layer 3 specification; Core Network Protocols; Stage 3". +- [6] 3GPP TS 44.064: "General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification". +- [7] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". +- [8] ITU-T Recommendation V.42 bis: "Data compression procedures for data circuit-terminating equipment (DCE) using error correcting procedures". +- [9] IETF RFC 1144: "Compressing TCP/IP headers for low-speed serial links". +- [10] IETF RFC 2507: "IP Header Compression". + +- [11] ITU-T Recommendation V.44: "Data compression procedures". +- [12] IETF RFC 5795: "RObust Header Compression (ROHC): Framework".. +- [13] IETF RFC 3241: "Robust Header Compression (ROHC) over PPP".. +- [14] "RObust Header Compression (ROHC) Profile Identifiers". IANA registry at: + + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 21.905 [1] and 3GPP TS 22.060 [2] and the following apply: + +**Feedback N-PDU:** an N-PDU which is generated by an SNDPCP protocol control information compression entity or data compression entity and contains only control information for its peer compression entity, but no payload from any SNDPCP user. + +**N201:** LLC layer parameter (see 3GPP TS 44.064 [6] for clarity). + +Defines maximum number of octets in the information field of LL-PDU. Separate values are applicable for I (see N201-I), U and UI (see N201-U) LL-PDUs. + +**N201-I:** LLC layer parameter (see 3GPP TS 44.064 [6] for clarity). + +Defines maximum number of octets available to a SN-DATA PDU for a specific SAPI. + +**N201-U:** LLC layer parameter (see 3GPP TS 44.064 [6] for clarity). + +Defines maximum number of octets available to a SN-UNITDATA PDU for a specific SAPI. If integrity protection is used, (N201-U - 4) defines maximum number of octets available to an SN-UNITDATA PDU for a specific SAPI. + +**N-PDU number:** a sequence number assigned to N-PDUs per NSAPI. + +**NSAPI:** for each SN-PDU the NSAPI is an index to the PDP context of the PDP that is using the services provided by the SNDPCP layer. + +**Receive N-PDU number:** the value of the N-PDU number expected in the next N-PDU received by an NSAPI using acknowledged peer-to-peer LLC operation. + +**Recovery state:** a state for an NSAPI in which duplicated received N-PDUs shall be detected and discarded. The recovery state only applies to NSAPIs using acknowledged peer-to-peer LLC operation. + +**SAPI:** identifies the Service Access Point that the SN-PDU is using at the LLC layer. + +**Segment number:** a sequence number assigned to SN-UNITDATA PDUs carrying segments of an N-PDU. + +**Send N-PDU number:** the value to be assigned as the N-PDU number to the next N-PDU received from the SNDPCP user by an NSAPI using acknowledged peer-to-peer LLC operation. + +**Send N-PDU number (unacknowledged):** the value to be assigned as the N-PDU number to the next N-PDU received from the SNDPCP user by an NSAPI using unacknowledged peer-to-peer LLC operation. + +**SNDPCP entity:** handles the service functions provided by the SNDPCP layer. The SNDPCP entity is temporary logical link identity specific. + +**SNDPCP management entity:** handles communication with SM sub-layer and controls the operation of the SNDPCP entity. + +**SNDPCP user:** protocol entity that is using the services provided by the SNDPCP layer. PDP entities and control entities, e.g. AT command interpreter, are the SNDPCP users at the MS. Relay entity is the SNDPCP user at the SGSN. + +**SNDPCP XID block:** the collection of SNDPCP XID parameters being negotiated. It is transferred by the LL-XID and LL-ESTABLISH primitives between SNDPCP and LLC. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 [1], 3GPP TS 22.060 [2], and 3GPP TS 23.060 [3], and the following apply: + +| | | +|-------|-----------------------------------------------------------------------------------------| +| CID | Context Identifier | +| DCOMP | Identifier of the user data compression algorithm used for the N-PDU | +| ESP | Encapsulating Security Payload | +| F | First segment indicator bit | +| GMM | GPRS Mobility Management | +| IP | Internet Protocol | +| LLC | Logical Link Control | +| LSB | Least Significant Bits | +| M | More bit used to indicate the last segment of N-PDU | +| N-PDU | Network Protocol Data Unit | +| MRRU | Maximum Reconstructed Reception Unit | +| MSB | Most Significant Bits | +| NSAPI | Network Layer Service Access Point Identifier | +| P | Propose bit | +| PCOMP | Identifier of the protocol control information compression algorithm used for the N-PDU | +| PDP | Packet Data Protocol (e.g. IPv4 or IPv6) | +| PDU | Protocol Data Unit | +| PID | Protocol Identifier | +| PTP | Point to Point | +| QoS | Quality of Service | +| ROHC | RObust Header Compression | +| RTP | Real Time Protocol | +| SAPI | Service Access Point Identifier | +| SDU | Service Data Unit | +| SGSN | Serving GPRS Support Node | +| SM | Session Management | +| SNDCP | Subnetwork Dependent Convergence Protocol | +| SNSM | SNDCP-SM | +| TCP | Transmission Control Protocol | +| TLLI | Temporary Logical Link Identifier | +| X | Spare bit | + +# 4 General + +The present document describes the functionality of the GPRS SNDCP. The overall GPRS logical architecture is defined in 3GPP TS 23.060 [3]. Location of the SNDCP in GPRS protocol stack can be seen in figure 1. + +![Figure 1: GPRS protocol stack diagram showing the layers for MS, BSS, and SGSN.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +The diagram illustrates the GPRS protocol stack across three entities: MS (Mobile Station), BSS (Base Station System), and SGSN (Serving GPRS Support Node), separated by the Um and Gb interfaces. + +- MS (Mobile Station) Stack:** From top to bottom: Application, IPv4 / IPv6, SNDCP, LLC, RLC, MAC, GSM RF. +- BSS (Base Station System) Stack:** From top to bottom: Relay (containing RLC and BSSGP), MAC, Network Service, GSM RF, L1bis. +- SGSN (Serving GPRS Support Node) Stack:** From top to bottom: Relay (containing SNDCP and GTP), LLC, UDP / TCP, BSSGP, IP, Network Service, L2, L1bis, L1. + +Vertical dashed lines indicate the interfaces: Um between MS and BSS, and Gb between BSS and SGSN. + +Figure 1: GPRS protocol stack diagram showing the layers for MS, BSS, and SGSN. + +Figure 1: GPRS protocol stack + +Network layer protocols are intended to be capable of operating over services derived from a wide variety of subnetworks and data links. GPRS supports several network layer protocols providing protocol transparency for the users of the service. Introduction of new network layer protocols to be transferred over GPRS shall be possible without any changes to GPRS. Therefore, all functions related to transfer of Network layer Protocol Data Units (N-PDUs) shall be carried out in a transparent way by the GPRS network entities. This is one of the requirements for GPRS SNDCP. + +Another requirement for the SNDCP is to provide functions that help to improve channel efficiency. This requirement is fulfilled by means of compression techniques. + +The set of protocol entities above SNDCP consists of commonly used network protocols. They all use the same SNDCP entity, which then performs multiplexing of data coming from different sources to be sent using the service provided by the LLC layer (figure 2). The Network Service Access Point Identifier (NSAPI) is an index to the PDP context (see 3GPP TS 23.060 [3]) of the PDP that is using the services provided by SNDCP. One PDP may have several PDP contexts and NSAPIs. However, it is possible that each allocated NSAPI is used by separate PDP. Each active NSAPI shall use the services provided by the Service Access Point Identifier (SAPI) in the LLC layer. Several NSAPIs may be associated with the same SAPI. + +Since the adaptation of different network layer protocols to SNDCP is implementation dependent, it is not defined in the present document. + +![Diagram illustrating the multiplexing of different network layer protocols over the SNDCP and LLC layers.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +The diagram shows three ovals at the top, each labeled 'Packet Data Protocol'. Lines from these ovals point down to a horizontal line representing the SNDCP layer. Each line has a small circle on it, labeled 'NSAPI' from left to right. An ellipsis is shown between the second and third circles. Below the SNDCP layer is another horizontal line representing the LLC layer. Lines from the NSAPI circles point down to this LLC layer, where they connect to circles labeled 'SAPI' from left to right. The label 'LLC' is at the bottom right of this layer. To the right of the diagram, there are two rectangular boxes. The top box is labeled 'N-PDU' and has a dashed line connecting it to the SNDCP layer. The bottom box is labeled 'SN-PDU' and has a dashed line connecting it to the LLC layer. + +Diagram illustrating the multiplexing of different network layer protocols over the SNDCP and LLC layers. + +Figure 2: Example for multiplexing of different protocols + +# 5 Service primitives and functions + +## 5.1 Service primitives + +This subclause explains the service primitives used for communication between the SNDCP layer and other layers. See also 3GPP TS 24.007 [4] to get an overall picture of the service primitives. Figure 3 illustrates the service access points through which the primitives are carried out. + +![Figure 3: Service Access Points provided and used by SNDCP. The diagram shows the SNDCP layer interacting with various entities. Above the SNDCP layer, 'Control Entity', 'MBMS', and two 'PDP or Relay' blocks are shown as SNDCP users. They connect to the SNDCP layer via NSAPIs (1, 5, 6, ..., 15). The SNDCP layer contains an 'SNDCP management entity' and an 'SNDCP entity'. Below the SNDCP layer, the 'SNDCP management entity' connects to a 'Session Management entity' via SNSM. The 'SNDCP entity' connects to the 'LLC layer' via SAPIs (LL3, LL5, LL9, LL11).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 3: Service Access Points provided and used by SNDCP. The diagram shows the SNDCP layer interacting with various entities. Above the SNDCP layer, 'Control Entity', 'MBMS', and two 'PDP or Relay' blocks are shown as SNDCP users. They connect to the SNDCP layer via NSAPIs (1, 5, 6, ..., 15). The SNDCP layer contains an 'SNDCP management entity' and an 'SNDCP entity'. Below the SNDCP layer, the 'SNDCP management entity' connects to a 'Session Management entity' via SNSM. The 'SNDCP entity' connects to the 'LLC layer' via SAPIs (LL3, LL5, LL9, LL11). + +**Figure 3: Service Access Points provided and used by SNDCP** + +### 5.1.1 SNDCP service primitives + +The primitives provided by the SNDCP layer are listed in table 1. + +**Table 1: SNDCP layer service primitives** + +| Generic Name | Type | | | | Parameters | +|---------------------------------------------------|---------|------------|----------|---------|---------------------------------| +| | Request | Indication | Response | Confirm | | +| SNDCP User (PDP or the SGSN Relay) ↔ SNDCP | | | | | | +| SN-DATA | X | - | - | - | N-PDU, NSAPI, N-PDU Number | +| SN-DATA | - | X | - | - | N-PDU, NSAPI | +| SN-UNITDATA | X | X | - | - | N-PDU, NSAPI | +| SN-XID | X | X | - | - | Requested SNDCP XID Parameters | +| SN-XID | - | - | X | X | Negotiated SNDCP XID Parameters | + +#### 5.1.1.1 SN-DATA.request + +Request used by the SNDCP user for acknowledged transmission of N-PDU. The successful transmission of SN-PDU shall be confirmed by the LLC layer. The SN-DATA.request primitive conveys NSAPI to identify the PDP using the service. N-PDU Number, if present, indicates the N-PDU number previously assigned to this N-PDU. + +**NOTE:** An N-PDU number may have been assigned to an N-PDU by the old SGSN before an inter-SGSN routing area update. + +#### 5.1.1.2 SN-DATA.indication + +Indication used by the SNDCP entity to deliver the received N-PDU to the SNDCP user. Successful reception has been acknowledged by the LLC layer. + +#### 5.1.1.3 SN-UNITDATA.request + +Request used by the SNDCP user for unacknowledged transmission of N-PDU. The SN-UNITDATA.request primitive conveys NSAPI to identify the PDP using the service. + +#### 5.1.1.4 SN-UNITDATA.indication + +Indication used by the SNDCP entity to deliver the received N-PDU to the SNDCP user. + +#### 5.1.1.5 SN-XID.request + +Request used by the SNDCP user at the initiating entity to deliver the list of requested XID parameters to the peer entity. + +#### 5.1.1.6 SN-XID.indication + +Indication used by the SNDCP entity to deliver the list of requested XID parameters to the SNDCP user. + +#### 5.1.1.7 SN-XID.response + +Response used by the SNDCP user to deliver the list of negotiated XID parameters to the peer entity. + +#### 5.1.1.8 SN-XID.confirm + +Confirm used by the SNDCP entity to deliver the list of negotiated XID parameters to the SNDCP user. + +### 5.1.2 Service primitives used by SNDCP layer + +The SNDCP layer uses the service primitives provided by the SM sublayer and the LLC layer (see table 2). SM is specified in 3GPP TS 24.008 [5a] and LLC in 3GPP TS 44.064 [6]. + +**Table 2: Service primitives used by the SNDPCP entity** + +| Generic Name | Type | | | | Parameters | +|---------------------|---------|------------|----------|---------|-----------------------------------------------------------------------------------------| +| | Request | Indication | Response | Confirm | | +| SNDPCP ↔ LLC | | | | | | +| LL-RESET | - | X | - | - | TLLI, old XID indicator | +| LL-ESTABLISH | X | - | - | - | TLLI, XID Requested | +| LL-ESTABLISH | - | X | - | - | TLLI, XID Requested, N201-I, N201-U | +| LL-ESTABLISH | - | - | X | - | TLLI, XID Negotiated | +| LL-ESTABLISH | - | - | - | X | TLLI, XID Negotiated, N201-I, N201-U | +| LL-RELEASE | X | - | - | - | TLLI, Local | +| LL-RELEASE | - | X | - | - | TLLI, Cause | +| LL-RELEASE | - | - | - | X | TLLI | +| LL-XID | X | - | - | - | TLLI, XID Requested | +| LL-XID | - | X | - | - | TLLI, XID Requested, N201-I, N201-U | +| LL-XID | - | - | X | - | TLLI, XID Negotiated | +| LL-XID | - | - | - | X | TLLI, XID Negotiated, N201-I, N201-U | +| LL-DATA | X | - | - | - | TLLI, SN-PDU, Reference, QoS Parameters, Radio Priority | +| LL-DATA | - | X | - | - | TLLI, SN-PDU | +| LL-DATA | - | - | - | X | TLLI, Reference | +| LL-UNITDATA | X | - | - | - | TLLI, SN-PDU, QoS Parameters, Radio Priority, Cipher | +| LL-UNITDATA | - | X | - | - | TLLI, SN-PDU | +| LL-STATUS | - | X | - | - | TLLI, Cause | +| SNDPCP ↔ SM | | | | | | +| SNSM-ACTIVATE | - | X | - | - | TLLI, NSAPI, QoS profile, SAPI, Radio Priority | +| SNSM-ACTIVATE | - | - | X | - | TLLI, NSAPI | +| SNSM-DEACTIVATE | - | X | - | - | TLLI, NSAPI(s), LLC Release Indicator, XID Negotiation Indicator | +| SNSM-DEACTIVATE | - | - | X | - | TLLI, NSAPI | +| SNSM-MODIFY | - | X | - | - | TLLI, NSAPI, QoS Profile, SAPI, Radio Priority, Send N-PDU Number, Receive N-PDU Number | +| SNSM-MODIFY | - | - | X | - | TLLI, NSAPI | +| SNSM-STATUS | X | - | - | - | TLLI, SAPI, Cause | +| SNSM-SEQUENCE | - | X | X | - | TLLI, NSAPI, Receive N-PDU Number | +| SNSM-STOP-ASSIGN | - | X | - | - | TLLI, NSAPI | + +#### 5.1.2.1 LL-RESET.indication + +Indication used by the LLC layer in the SGSN to indicate to the SNDPCP layer that the Reset XID parameter has been transmitted, and by the LLC layer in the MS to indicate to the SNDPCP layer that the Reset XID parameter has been received. + +Upon receipt of the LL-RESET.indication, the SNDPCP layer shall: + +- treat all outstanding SNDPCP ↔ LLC request type primitives as not sent; +- if the old XID indicator is set, keep the SNDPCP XID parameters that were applicable before the receipt of the LL-RESET.indication and re-initialize any negotiated compression entities . Otherwise, if the old XID indicator is not set, reset all SNDPCP XID parameters to their default values (for the definition of default values see subclause 6.8.2 and clause 8, table 8); + +- in the MS, for every NSAPI using unacknowledged peer-to-peer LLC operation, set the Send N-PDU number (unacknowledged) to 0; and +- for every NSAPI using acknowledged peer-to-peer LLC operation, enter the recovery state and suspend the transmission of SN-PDUs until an SNSM-SEQUENCE.indication primitive is received for the NSAPI. In the SGSN the SNDPCP layer shall re-establish acknowledged peer-to-peer operation for the affected SAPIs in the LLC layer. + +#### 5.1.2.2 LL-ESTABLISH.request + +Request used by the SNDPCP layer to establish or re-establish acknowledged peer-to-peer operation for a SAPI in the LLC layer. XID Requested is used to deliver the requested SNDPCP XID parameters to the LLC layer. + +#### 5.1.2.3 LL-ESTABLISH.indication + +Indication used by the LLC layer to inform the SNDPCP layer about establishment or re-establishment of acknowledged peer-to-peer operation for a SAPI in the LLC layer. XID Requested is used to deliver the requested SNDPCP XID parameters to the SNDPCP layer. In case of a re-establishment, all NSAPIs mapped to the affected SAPI shall enter the recovery state, and all buffered N-PDUs (i.e. the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet), except the feedback N-PDUs, shall be transmitted starting with the oldest N-PDU when the link is re-established. Also all compression entities using acknowledged peer-to-peer LLC operation on this SAPI are reset. + +Before the transmission of N-PDUs is resumed, any feedback N-PDUs shall be removed from the buffered N-PDUs. If feedback N-PDUs are removed, the SNDPCP layer shall reassign the N-PDU numbers of the remaining N-PDUs, so that consecutive numbering is restored and transmission is started with the N-PDU number expected by the peer SNDPCP entity. If the LL-ESTABLISH.indication primitive is used to re-establish acknowledged peer-to-peer LLC operation during an inter-SGSN routing area update, the N-PDU numbers shall be reassigned only after receipt of the SNSM-SEQUENCE.indication. + +#### 5.1.2.4 LL-ESTABLISH.response + +Response used by the SNDPCP layer after reception of the LL-ESTABLISH.indication. XID Negotiated is used to deliver the negotiated SNDPCP XID parameters to the LLC layer. + +#### 5.1.2.5 LL-ESTABLISH.confirm + +Confirmation used by the LLC layer to inform the SNDPCP layer about successful initiation of acknowledged peer-to-peer operation for a SAPI in the LLC layer. XID Negotiated is used to deliver the negotiated SNDPCP XID parameters to the SNDPCP layer. In case of a re-establishment, all NSAPIs mapped to the affected SAPI shall enter the recovery state, and all buffered N-PDUs (i.e. the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet), except the feedback N-PDUs, shall be transmitted starting with the oldest N-PDU when the link is re-established. Also all compression entities using acknowledged peer-to-peer LLC operation on this SAPI are reset. + +Before the transmission of N-PDUs is resumed, any feedback N-PDUs shall be removed from the buffered N-PDUs. If feedback N-PDUs are removed, the SNDPCP layer shall reassign the N-PDU numbers of the remaining N-PDUs, so that consecutive numbering is restored and transmission is started with the N-PDU number expected by the peer SNDPCP entity. If the LL-ESTABLISH.confirm primitive is used to re-establish acknowledged peer-to-peer LLC operation during an inter-SGSN routing area update, the N-PDU numbers shall be reassigned only after receipt of the SNSM-SEQUENCE.indication. + +#### 5.1.2.6 LL-RELEASE.request + +Request used by the SNDPCP layer to release acknowledged peer-to-peer operation for a SAPI in the LLC layer. The Local parameter indicates whether the termination shall be local (see 3GPP TS 44.064 [6] for details). + +#### 5.1.2.7 LL-RELEASE.indication + +Indication used by the LLC layer to inform the SNDPCP layer about termination of acknowledged peer-to-peer operation for a SAPI in the LLC layer. The Cause parameter indicates the cause for the termination. + +On receipt of LL-RELEASE.indication, compressed N-PDUs queuing to be forwarded to the affected SAPI are deleted from the SNDPCP layer. Also all compression entities using acknowledged peer-to-peer LLC operation on this SAPI are reset. + +#### 5.1.2.8 LL-RELEASE.confirm + +Confirmation used by the LLC layer to inform the SNDCP layer about termination of acknowledged peer-to-peer operation for a SAPI in the LLC layer. On receipt of LL-RELEASE.confirm, compressed N-PDUs queuing to be forwarded to the affected SAPI are deleted from the SNDCP layer. Also all compression entities using acknowledged peer-to-peer LLC operation on this SAPI are reset. + +#### 5.1.2.9 LL-XID.request + +Request used by the SNDCP layer to deliver the requested SNDCP XID parameters to the LLC layer. + +#### 5.1.2.10 LL-XID.indication + +Indication used by the LLC layer to deliver the requested SNDCP XID parameters to the SNDCP layer. + +#### 5.1.2.11 LL-XID.response + +Response used by the SNDCP layer to deliver the negotiated SNDCP XID parameters to the LLC layer. + +#### 5.1.2.12 LL-XID.confirm + +Confirm used by the LLC layer to deliver the negotiated SNDCP XID parameters to the SNDCP layer. + +#### 5.1.2.13 LL-DATA.request + +Request used by the SNDCP layer for acknowledged transmission of an SN-PDU. The SNDCP entity shall associate a reference parameter for each LL-DATA.request. QoS Parameters in the SGSN includes precedence class, delay class, and peak throughput. QoS Parameters in the MS includes peak throughput. QoS Parameters is defined as part of the Quality of Service information element in 3GPP TS 24.008 [5a]. Radio Priority is included only in the MS, and indicates the radio priority level to be used by RLC/MAC. + +Acknowledged peer-to-peer LLC operation for the SAPI used shall be established using the LL-ESTABLISH primitives, before the LL-DATA.request may be used. + +#### 5.1.2.14 LL-DATA.indication + +Indication used by the LLC layer to deliver the successfully received SN-PDU to the SNDCP layer. + +#### 5.1.2.15 LL-DATA.confirm + +Confirm used by the LLC layer to inform SNDCP layer about successful transmission of SN-PDU. The primitive includes a reference parameter from which the SNDCP entity shall identify the LL-DATA.request this confirmation was associated with. All buffered N-PDUs whose complete reception is confirmed are deleted. + +#### 5.1.2.16 LL-UNITDATA.request + +Request used by the SNDCP layer for unacknowledged transmission of a SN-PDU. Unconfirmed transmission shall be used by the LLC layer. + +Acknowledged peer-to-peer LLC operation does not need to be established before unacknowledged transmission is allowed. + +QoS Parameters in the SGSN includes precedence class, delay class, reliability class, and peak throughput. QoS Parameters in the MS includes peak throughput and reliability class. Reliability class indicates whether the LLC frame carrying the SN-PDU shall be transmitted in protected or unprotected mode, and whether RLC/MAC acknowledged or unacknowledged mode shall be used. Radio Priority is included only in the MS, and indicates the radio priority level to be used by RLC/MAC. + +#### 5.1.2.17 LL-UNITDATA.indication + +Indication used by the LLC layer to deliver the received SN-PDU to the SNDCP layer. There is no need for acknowledged peer-to-peer LLC operation for unacknowledged transmission of SN-PDU. + +#### 5.1.2.18 LL-STATUS.indication + +Indication used by the LLC layer to inform SNDPCP when an LLC error that cannot be corrected by the LLC layer has occurred. The Cause parameter indicates the cause of the failure. + +On receipt of LL-STATUS.indication, SNDPCP shall inform the SM sub-layer by means of the SNSM-STATUS.request primitive. + +#### 5.1.2.19 SNSM-ACTIVATE.indication + +Indication used by the SM entity to inform the SNDPCP entity that an NSAPI has been activated for data transfer. It also informs the SNDPCP entity about the negotiated QoS profile (see 3GPP TS 24.008 [5a]), the SAPI assigned for this NSAPI, and, in the MS, the radio priority level to be used by RLC/MAC. + +If the NSAPI activated uses the acknowledged peer-to-peer LLC operation, the NSAPI shall enter the recovery state. + +Upon reception of the SNSM-ACTIVATE.indication from the SM sublayer, the SNDPCP entity shall, if necessary, establish the acknowledged peer-to-peer LLC operation for the indicated SAPI. The establishment criteria and procedure are described in subclause 6.2.1. + +#### 5.1.2.20 SNSM-ACTIVATE.response + +Response used by the SNDPCP layer to inform SM entity that the indicated NSAPI is now in use and that the acknowledged peer-to-peer LLC operation for the indicated SAPI is established, if necessary. + +#### 5.1.2.21 SNSM-DEACTIVATE.indication + +Indication used by the SM entity to inform the SNDPCP entity that an NSAPI has been deallocated and cannot be used by the SNDPCP entity anymore. All buffered N-PDUs corresponding to this NSAPI are deleted. + +Upon reception of the SNSM-DEACTIVATE.indication, the SNDPCP entity shall, if necessary, release the acknowledged peer-to-peer LLC operation for the associated SAPI. The release criteria and procedure are described in subclause 6.2.2. If the XID Negotiation Indicator is included in the the SNSM-DEACTIVATE.indication and compression entities have been negotiated for the NSAPI, the NSAPI shall be removed from the Applicable NSAPIs of these compression entities by explicit XID negotiation. If no XID Negotiation Indicator is included, the NSAPI shall be removed locally, without XID negotiation (see subclause 6.8). + +#### 5.1.2.22 SNSM-DEACTIVATE.response + +Response used by the SNDPCP layer to inform SM entity that the NSAPI indicated is no longer in use and that the acknowledged peer-to-peer LLC operation for the associated SAPI is released, if necessary. + +#### 5.1.2.23 SNSM-MODIFY.indication + +Indication used by the SM entity to trigger change of the QoS profile (see 3GPP TS 24.008 [5a]) for an NSAPI and indication of the SAPI to be used. It is also used by the SM entity in the SGSN to inform the SNDPCP entity that an NSAPI shall be created, together with the (re-)negotiated QoS profile, the SAPI assigned, and, in the MS, the radio priority level to be used by RLC/MAC. + +NOTE: The latter is performed in the new SGSN during an Inter-SGSN Routeing Area Update. + +Upon reception of the SNSM-MODIFY.indication from the SM sublayer: + +- the SNDPCP entity shall, if necessary, establish the acknowledged peer-to-peer LLC operation for the indicated SAPI (the establishment criteria and procedure are described in subclause 6.2.1); and +- the SNDPCP entity shall also, if necessary, release the acknowledged peer-to-peer LLC operation for the originally-assigned SAPI (the release criteria and procedure are described in subclause 6.2.2). + +If the SNSM-MODIFY.indication applies to an existing NSAPI, and: + +- if the peer-to-peer LLC operation mode is changed from acknowledged to unacknowledged, then all buffered N-PDUs shall be deleted, and the Send N-PDU number (unacknowledged) shall be set to 0; and + +- if the peer-to-peer LLC operation mode is changed from unacknowledged to acknowledged, then the Send N-PDU number and Receive N-PDU number shall be set to 0. + +In addition, if the newly-assigned SAPI is different from the original SAPI: + +- LL-DATA.indication, LL-DATA.confirm and LL-UNITDATA.indication received on the old SAPI shall be ignored; +- LL-DATA.request and LL-UNITDATA.request shall be sent on the new SAPI; and +- if acknowledged peer-to-peer LLC operation is used both before and after the receipt of the SNSM-MODIFY.indication, then the NSAPI shall enter the recovery state, and all buffered N-PDUs (i.e. the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet) shall be transmitted starting from the oldest N-PDU. + +If the SNSM-MODIFY.indication signifies the creation of an NSAPI (i.e. the specified NSAPI does not exist), and: + +- if unacknowledged peer-to-peer LLC operation is specified in the QoS profile, then the Send N-PDU number (unacknowledged) shall be set to 0; and +- if acknowledged peer-to-peer LLC operation is specified in the QoS profile, then the Send N-PDU number and the Receive N-PDU number variables shall be set to the values stated in the primitive. + +#### 5.1.2.24 SNSM-MODIFY.response + +Response used by the SNDPCP entity to inform the SM entity that the indicated NSAPI and QoS profile are now in use and the acknowledged peer-to-peer LLC operations for the appropriate SAPIs are established and/or released, if necessary. + +#### 5.1.2.25 SNSM-STATUS.request + +This primitive is used by the SNDPCP layer to inform the SM sub-layer that SNDPCP cannot continue its operation due to errors at the LLC layer (as indicated with LL-RELEASE.indication) or at the SNDPCP layer. The Cause parameter indicates the cause of the error. + +#### 5.1.2.26 SNSM-SEQUENCE.indication + +This primitive is used during an inter-SGSN routeing area update and applies only to NSAPIs using acknowledged peer-to-peer LLC operation. When the primitive is used in the MS, the Receive N-PDU number parameter indicates the Receive N-PDU number in the SGSN. When the primitive is used in the SGSN, the Receive N-PDU number parameter indicates the Receive N-PDU number in the MS. If a buffered N-PDU is confirmed by the Receive N-PDU number parameter to have been received by the peer SNDPCP entity, the N-PDU shall be deleted from the buffer. In addition, the receipt of this primitive by the SNDPCP entity resumes the transmission of SN-PDUs for the NSAPI, and all buffered N-PDUs (i.e. the ones whose complete reception has not been acknowledged and the ones that have not been transmitted yet), except the feedback N-PDUs, shall be transmitted starting from the oldest N-PDU. Before the transmission is resumed, any feedback N-PDUs shall be removed from the buffered N-PDUs. If feedback N-PDUs are removed, the SNDPCP layer shall reassign the N-PDU numbers of the remaining N-PDUs, so that consecutive numbering is restored and transmission is started with the N-PDU number expected by the peer SNDPCP entity. If acknowledged peer-to-peer LLC operation has not yet been established for the SAPI used by this NSAPI, the transmission of the buffered N-PDUs shall begin only after the receipt of the LL-ESTABLISH.indication or LL-ESTABLISH.confirm primitive. + +#### 5.1.2.27 SNSM-SEQUENCE.response + +This primitive is used during an inter-SGSN routeing area update and applies only to NSAPIs using acknowledged peer-to-peer LLC operation. The primitive is used by the SNDPCP layer in the MS following receipt of an SNSM-SEQUENCE.indication, in order to return the Receive N-PDU number to the SGSN during an ongoing inter-SGSN routeing area update. + +#### 5.1.2.28 SNSM-STOP-ASSIGN.indication + +This primitive is used during an inter-SGSN routeing area update in the old SGSN by the SM entity to inform the SNDPCP entity to stop assigning N-PDU numbers to N-PDUs received through the SN-DATA.request primitive. The primitive is sent before the Send N-PDU number and the Receive N-PDU number are transferred to the new SGSN. + +## 5.2 Service functions + +SNDPCP shall perform the following functions (see figure 4): + +- Mapping of SN-DATA primitives onto LL-DATA primitives. +- Mapping of SN-UNITDATA primitives onto LL-UNITDATA primitives. +- Multiplexing of N-PDUs from one or several network layer entities onto the appropriate LLC connection. +- Establishment, re-establishment and release of acknowledged peer-to-peer LLC operation. +- Supplementing the LLC layer in maintaining data integrity for acknowledged peer-to-peer LLC operation by buffering and retransmission of N-PDUs. +- Management of delivery sequence for each NSAPI, independently. +- Compression of redundant protocol control information (e.g. TCP/IP header) at the transmitting entity and decompression at the receiving entity. The compression method is specific to the particular network layer or transport layer protocols in use. +- Compression of redundant user data at the transmitting entity and decompression at the receiving entity. Data compression is performed independently for each SAPI, and may be performed independently for each PDP context. Compression parameters are negotiated between the MS and the SGSN. +- Segmentation and reassembly. The output of the compressor functions is segmented to the maximum length of LL-PDU. These procedures are independent of the particular network layer protocol in use. +- Negotiation of the XID parameters between peer SNDPCP entities using XID exchange. + +Figure 4 shows the transmission flow through SNDPCP layer. The order of functions is the following: + +- Protocol control information compression. +- User data compression. +- Segmentation of compressed information into SN-DATA or SN-UNITDATA PDUs. + +The order of functions is vice versa in the reception flow: + +- Reassembly of SN-PDUs to N-PDUs. +- User data decompression. +- Protocol control information decompression. + +![Figure 4: SNDPC model diagram showing the flow of data from the Network Layer through SNDPC and LLC layers.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates the SNDPC model flow. At the top, an N-PDU is shown with a red 'header' and a yellow 'data' section. Two arrows, 'SN-DATA.request' and 'SN-UNITDATA.request', lead from the N-PDU to the NETWORK LAYER. Below the NETWORK LAYER is the SNDPC layer. The 'SN-DATA.request' path goes through a 'control compressor' (which compares the header to the previous one; if the difference is 'big', it outputs a red 'header'; if 'small', it outputs a red 'delta'), then a 'data compressor', and finally a 'segmentation' block. The 'SN-UNITDATA.request' path goes through a 'control compressor', then a 'data compressor', and finally a 'segmentation' block. The output of the 'SN-DATA.request' path is a 'Segmented N-PDU' consisting of multiple segments with M=0 or M=1 flags. The output of the 'SN-UNITDATA.request' path is 'Segmented dN-PDU 2' (segments #2, #1, #3) and 'Segmented dN-PDU 1' (segments #2, #1). These are then processed by 'LLC header' blocks to become 'SN-DATA PDU' and 'SN-UNITDATA PDU' respectively. The final output is 'LLC DATA.request' and 'LLC UNITDATA.request' to the LLC layer. + +Figure 4: SNDPC model diagram showing the flow of data from the Network Layer through SNDPC and LLC layers. + +**Figure 4: SNDPC model** + +The SNDPC layer expects the following services to be provided by the LLC layer. LLC layer functionality is defined in 3GPP TS 44.064 [6]: + +- Acknowledged and unacknowledged data transfer. +- Point-to-point and point-to-multipoint data transfer. +- In-order delivery of SN-PDUs per SAPI (i.e. SN-PDUs using the same SAPI shall appear at the receiving end in the same order as transmitted). This is required only for acknowledged service. +- QoS profile-based transfer of SN-PDUs. +- Support for variable length SN-PDUs. +- Transfer of SNDPC XID parameters. + +The SNDCP layer expects the following services to be provided by the SM sublayer. SM sublayer functionality is defined in 3GPP TS 24.008 [5a]: + +- Activation and deactivation of PDP Contexts and informing the SNDCP layer when change in PDP context has happened. +- Carrying out Inter SGSN Routing Area Update and informing the SNDCP layer in the SGSN when the N-PDUs shall be tunnelled to the new SGSN. +- Notifying the SNDCP layer when there is need to change the QoS profile parameters of the PDP contexts. + +# 6 Protocol functions + +## 6.1 Multiplexing of N-PDUs + +The NSAPI field shall be used for the identification of the specific PDP type and PDP address pair that is using the services provided by the SNDCP layer. The MS allocates NSAPIs dynamically at the PDP Context Activation. The NSAPI is delivered by the SM sub-layer to the SNDCP layer with the SNSM-ACTIVATE.indication primitive. The transmitting SNDCP entity shall insert the NSAPI value for each N-PDU. The peer SNDCP entity uses the NSAPI to identify the SNDCP user the N-PDU is targeted. Table 3 shows an example for the allocation of the NSAPIs. + +**Table 3: Example of the NSAPI allocation** + +| PDP type | Allocated NSAPI | PDP address | +|----------|-----------------|----------------------------------| +| IPv4 | 12 | 133.12.75.111 (4 octets) | +| IPv6 | 13 | 133.12. .... .11.123 (16 octets) | + +## 6.2 Establishment and release of acknowledged peer-to-peer LLC operation + +The SNDCP layer shall be responsible for establishing, re-establishing and releasing the acknowledged peer-to-peer LLC operation. + +Re-establishment and release of the acknowledged peer-to-peer LLC operation may also be initiated by the LLC layer. The conditions under which this may happen are described in 3GPP TS 44.064 [6]. + +Negotiation of SNDCP XID parameters may be carried out in conjunction with the establishment or re-establishment procedure. It is also possible to negotiate SNDCP XID parameters independently from the establishment or re-establishment procedure, by using the LL-XID primitives. + +### 6.2.1 Establishment of acknowledged peer-to-peer LLC operation + +#### 6.2.1.1 Establishment criteria + +If acknowledged peer-to-peer LLC operation is required by an NSAPI (as indicated by the QoS profile) but is not yet established for the SAPI used by the NSAPI, then the SNDCP layer shall initiate the establishment procedure. + +The SNDCP layer at the MS shall initiate the establishment, using the procedure in subclause 6.2.1.3, upon receipt of the SNSM-ACTIVATE.indication primitive. + +The SNDCP layer at the SGSN shall initiate the establishment upon receipt of the SNSM-MODIFY.indication primitive. + +#### 6.2.1.2 Re-establishment of the acknowledged peer-to-peer LLC operation + +The SNDCP layer may initiate re-establishment of the acknowledged peer-to-peer LLC operation for a SAPI under certain situations, for example when an error is detected by a V.42 bis data compression entity used for acknowledged data transfer. + +The LLC layer may also initiate re-establishment of the acknowledged peer-to-peer LLC operation for a SAPI under situations described in 3GPP TS 44.064 [6]. The LLC layer informs the SNDPCP layers of link re-establishment using the LL-ESTABLISH.indication primitive. This is shown in figure 5. + +![Figure 5: LLC-initiated re-establishment sequence diagram.](a3472689858b068ef469213682965325_img.jpg) + +A sequence diagram showing the interaction between an Originator and a Receiver for LLC-initiated re-establishment. The Originator contains three layers: SNDPCP user, SNDPCP, and LLC. The Receiver contains three layers: LLC, SNDPCP, and SNDPCP user. The sequence of messages is as follows: + + +- The LLC layer in the Originator sends a SABM message to the LLC layer in the Receiver. +- The LLC layer in the Receiver responds with a UA message to the LLC layer in the Originator. +- Upon receiving the UA message, the LLC layer in the Originator sends an LL-ESTAB.ind indication primitive to its SNDPCP layer. +- Simultaneously, the LLC layer in the Receiver sends an LL-ESTAB.ind indication primitive to its SNDPCP layer. + +Figure 5: LLC-initiated re-establishment sequence diagram. + +**Figure 5: LLC-initiated re-establishment** + +#### 6.2.1.3 Establishment procedure + +The SNDPCP layer shall initiate the establishment or re-establishment by sending an LL-ESTABLISH.request primitive to the relevant LLC SAP. SNDPCP XID parameters may be included in an SNDPCP XID block in the LL-ESTABLISH.request primitive. If no SNDPCP XID parameter is to be included, an empty SNDPCP XID block shall be included. + +Following the sending of the LL-ESTABLISH.request primitive, the SNDPCP layer shall suspend the transfer of LL-DATA and may continue the transfer of LL-UNITDATA primitives to the LLC SAP to which the LL-ESTABLISH.request is sent. Transfer of LL-DATA primitives shall be resumed when the establishment procedure has been successfully completed. + +The establishment procedure ends through one of the following means: + +- successful (receiving LL-ESTABLISH.confirm); +- failure (receiving LL-RELEASE.indication); or +- successful following collision resolution (receiving LL-ESTABLISH.indication and sending LL-ESTABLISH.response, see subclause 6.2.1.4). + +Upon receipt of an LL-ESTABLISH.indication primitive, if an SNDPCP XID block is present, the peer SNDPCP entity shall respond with an LL-ESTABLISH.response primitive. SNDPCP XID parameters may be included in an SNDPCP XID block in the LL-ESTABLISH.response primitive. If no SNDPCP XID parameter is to be included, an empty SNDPCP XID block shall be included. If there is no SNDPCP XID block in the LL-ESTABLISH.indication primitive, the peer SNDPCP entity shall not respond with an LL-ESTABLISH.response primitive. + +![Figure 6: SNDPCP-initiated establishment / re-establishment sequence diagram.](35127fe87029df6f5f0b2ee85f6193f1_img.jpg) + +A sequence diagram showing the interaction between an Originator and a Receiver for SNDPCP-initiated establishment/re-establishment. The Originator contains three layers: SNDPCP user, SNDPCP, and LLC. The Receiver contains three layers: LLC, SNDPCP, and SNDPCP user. The sequence of messages is as follows: + + +- The SNDPCP layer in the Originator sends an LL-ESTAB.req primitive to the LLC layer in the Originator. +- The LLC layer in the Originator then sends a SABM message to the LLC layer in the Receiver. +- The LLC layer in the Receiver receives the SABM and sends an LL-ESTAB.ind indication primitive to its SNDPCP layer. +- The SNDPCP layer in the Receiver then sends an LL-ESTAB.res response primitive to the LLC layer in the Receiver. +- The LLC layer in the Receiver receives the LL-ESTAB.res and sends a UA message to the LLC layer in the Originator. +- Upon receiving the UA message, the LLC layer in the Originator sends an LL-ESTAB.cnf confirmation primitive to its SNDPCP layer. + +Figure 6: SNDPCP-initiated establishment / re-establishment sequence diagram. + +**Figure 6: SNDPCP-initiated establishment / re-establishment** + +#### 6.2.1.4 Exceptional situations + +If the originator of the establishment procedure receives an LL-RELEASE.indication with Cause "DM received", it shall inform the SM sub-layer using the SNSM-STATUS.request primitive with Cause "DM received". SM shall then deactivate all PDP contexts for that SAPI requiring acknowledged peer-to-peer LLC operation. + +If the originator of the establishment procedure receives an LL-RELEASE.indication with Cause "invalid XID response" or an LL-STATUS.indication with Cause "invalid XID response", then it shall inform the SM sub-layer using the SNSM-STATUS.request primitive with Cause "invalid XID response". SM shall then deactivate all PDP contexts for that SAPI. + +If the originator of the establishment procedure receives an LL-RELEASE.indication with Cause "no peer response" or an LL-STATUS.indication with Cause "no peer response", then it shall inform the SM sub-layer using the SNSM-STATUS.request primitive with Cause "no peer response", wait for an implementation-specific amount of time, and re-invoke the establishment procedure. Before the establishment procedure is re-invoked, N-PDUs arriving at the SNDPCP layer for delivery to the LLC layer shall be buffered, if possible. + +If the SNDPCP layer receives an LL-RELEASE.indication with Cause "normal release", it shall buffer, if possible, all downlink N-PDUs for NSAPIs using the affected SAPI that requires acknowledged peer-to-peer LLC operation. Transfer of N-PDUs for NSAPIs that do not require acknowledged peer-to-peer LLC operation shall not be affected. + +If the originator of the establishment procedure detects a collision (receiving an LL-ESTABLISH.indication primitive after sending an LL-ESTABLISH.request or LL-XID.request primitive, or receiving an LL-XID.indication primitive after sending an LL-XID.request primitive), it shall treat the LL-ESTABLISH.request or LL-XID.request primitive sent as not transmitted, and process the LL-ESTABLISH.indication or LL-XID.indication primitive received. If the LL-ESTABLISH.request or LL-XID.request contains one or more XID parameters, or one or more compression fields in an XID parameter, or one or more parameters in a compression field, that are not negotiated as part of the collision resolution, then negotiation of these XID parameters shall be performed at the earliest opportunity after conclusion of the collision resolution. + +### 6.2.2 Release of acknowledged peer-to-peer LLC operation + +#### 6.2.2.1 Release criteria + +If acknowledged peer-to-peer LLC operation is established for the SAPI used by a PDP context that is going to be deactivated or mapped to another SAPI, and if there is no other NSAPIs that require acknowledged peer-to-peer LLC operation using the original SAPI, then the SNDPCP layer shall initiate the release procedure. + +The SNDPCP layer shall initiate the release, using the procedure described in subclause 6.2.2.2, upon receipt of the SNSM-DEACTIVATE.indication primitive. + +The SNDPCP layer at the SGSN shall also initiate the release upon receipt of the SNSM-MODIFY.indication primitive if an existing NSAPI is specified. + +#### 6.2.2.2 Release procedure + +The SNDPCP layer shall initiate the release by sending a LL-RELEASE.request primitive to the relevant LLC SAP. The Local parameter shall be set if the release is the result of receipt of the SNSM-DEACTIVATE.indication primitive, otherwise it shall not be set. + +#### 6.2.2.3 Release initiated by the LLC layer + +The LLC layer may initiate release of the acknowledged peer-to-peer LLC operation for a SAPI under situations described in 3GPP TS 44.064 [6]. The LLC layer shall inform the SNDPCP layers of the release of acknowledged peer-to-peer LLC operation using the LL-RELEASE.indication primitive. SNDPCP shall process the LL-RELEASE.indication primitive as described in subclause 6.2.1.4. + +## 6.3 N-PDU buffering + +The N-PDUs shall be buffered in the SNDPCP layer before they are compressed segmented and transmitted to the LLC layer. The reception of an SNSM-DEACTIVATE.indication shall trigger the deletion of the buffer for the related NSAPI. + +For acknowledged data transfer, the SNDPCP entity shall buffer an N-PDU until successful reception of all SN-PDUs carrying segments of the N-PDU have been confirmed. The confirmation is carried out using the LL-DATA.confirm primitive from the LLC layer or the SNSM-SEQUENCE.indication primitive from the SM layer. Buffered N-PDUs which have been completely received as indicated by the acknowledgements in an LL-DATA.confirm primitive shall be discarded. During the Inter-SGSN RA Update, buffered N-PDUs whose complete reception by the MS has been confirmed in the SNSM-SEQUENCE.indication primitive shall be discarded, as defined in 3GPP TS 29.060 [7] and 3GPP TS 23.060 [3]. + +For unacknowledged data transfer, the SNDPCP shall delete an N-PDU immediately after it has been delivered to the LLC layer. + +## 6.4 Management of delivery sequence + +The SNDPCP layer shall retain the delivery sequence of N-PDUs of each NSAPI between the peer entities. The delivery sequence of N-PDUs from different NSAPIs may be changed according to the QoS profiles. + +## 6.5 Protocol control information compression + +Protocol control information compression is an optional SNDPCP feature except for Multimedia Broadcast/Multicast Service (MBMS) where the support of ROHC decompression is mandatory in the MS. + +Negotiation of the supported algorithms and their parameters is carried out between MS and SGSN using the SNDPCP XID parameters (see clause 8). + +For MBMS, where no negotiation is possible, subclause 6.5.1 does not apply. Compression parameters are pre-configured as defined in subclause 6.5.5. + +### 6.5.1 Negotiation of multiple protocol control information compression types + +Each SNDPCP entity that supports protocol control information compression shall be able to negotiate one or several protocol control information compression entities with the compression field format shown in figure 7. The negotiation shall be carried out using the XID parameter negotiation specified in subclause 6.8. The initiating entity defines a set of requested compression entities, together with the algorithm and parameters for each compression entity. The set of entities and their algorithms and parameters shall be transmitted to the peer entity. The peer entity responds with the set of negotiated entities and their algorithms and parameters. The peer entity shall select the proposed parameter values or other appropriate values for the negotiated entities. If more than one protocol control information compression algorithm for a specific NSAPI is proposed during the XID negotiation then the receiving peer entity shall only choose one algorithm for that NSAPI. + +#### 6.5.1.1 Format of the protocol control information compression field + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|---------|------------------|---|---|----------------------|--------|---|---|---|--|--|--|--| +| Octet 1 | P | X | X | Entity number | | | | | | | | | +| Octet 2 | X | X | X | Algorithm identifier | | | | | | | | | +| Octet 3 | Length=n-3 | | | | | | | | | | | | +| Octet 4 | PCOMP1 | | | | PCOMP2 | | | | | | | | +| ... | ... | | | | ... | | | | | | | | +| Octet x | High-order octet | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | +| Octet n | Low-order octet | | | | | | | | | | | | + +NOTE: The two octets x and x+1, if included, contain the "Applicable NAPIDs" parameter (see subclause 7.1.3). + +Figure 7: Protocol control information compression field format for SNDPCP XID negotiation + +##### 6.5.1.1.1 Spare bit (X) + +The X bit shall be set to 0 by the transmitting SNDPCP entity and shall be ignored by the receiving SNDPCP entity. + +##### 6.5.1.1.2 Propose bit (P) + +The P bit shall be set to 1 if a new compression entity is being proposed, otherwise it shall be set to 0. If the P bit is set to 1, then all octets shall be included, otherwise octet 2 and octets 4 to x-1 shall not be included. If the P bit is set to 1, then only enough number of octets shall be included to contain the number of PCOMP values needed by the corresponding compression algorithm (e.g. PCOMP3 and PCOMP4 shall not be included if the number of PCOMP values needed by a compression algorithm is one or two). If an odd number of PCOMP values are used by a compression algorithm, then the last PCOMP value shall be set to 0 in the compression field by the transmitting SNDCP entity, and it shall be ignored by the receiving SNDCP entity. + +##### 6.5.1.1.3 Entity number + +The entity number shall be used to identify a protocol control information compression entity on a SAPI. The entity number shall be assigned using the following rules: + +- The entity number shall be an integer from 0 to 31. +- The entity number shall be assigned independently on each of the SAPIs. +- An entity number shall be in one of the three states: unassigned, selected, or assigned. +- When a new compression entity is to be proposed, an unassigned entity number shall become selected. If there is no unassigned entity number left, the compression entity shall not be proposed. +- A selected entity number shall become assigned if the corresponding proposed compression entity is created as a result of the XID negotiation, otherwise it shall become unassigned. +- An assigned entity number shall become unassigned when the corresponding compression entity is deleted as a result of an XID negotiation, or upon the receipt of the LL-RESET.indication primitive. +- In the case of a collision (see subclause 6.2.1.4) in which an entity number is currently selected: + - If the selected entity number is included with the P bit set to 0 in the incoming SNDCP XID block, then it shall be assumed that the peer SNDCP entity agreed to the creation of the proposed entity but the response was lost. Therefore the selected entity number shall become assigned, any selected PCOMP and DCOMP values for the algorithm of the entity shall become assigned, and the compression entity shall be created, before the incoming SNDCP XID block is processed. After the incoming SNDCP XID block is processed, the compression entity shall be negotiated again if necessary, as defined in subclause 6.2.1.4. + - Otherwise (i.e. if the selected entity number is not included, or is included with the P bit set to 1 in the incoming SNDCP XID block), the selected entity number shall become unassigned, and any selected PCOMP and DCOMP values for the algorithm of the entity shall become unassigned, before the incoming SNDCP XID block, if any, is processed. Following the collision resolution procedure, the originally-proposed compression entity shall be proposed again (i.e. the originally-proposed compression entity shall not be considered created even if the originally-selected entity number is proposed in the incoming SNDCP XID block) by sending the appropriate primitive (LL-ESTABLISH.request or LL-XID.request). The originally-selected entity number, PCOMP and DCOMP values shall be used for the compression entity being re-proposed if they are unassigned, otherwise a new entity number, PCOMP or DCOMP value shall be selected. +- In the case of a collision in which an entity number is currently assigned: + - If the peer SNDCP entity proposes a new compression entity with the same entity number, then it shall be assumed that the peer SNDCP entity negotiated the deletion of the entity but the response was lost, and the entity number is being reused. Therefore the original compression entity shall be deleted, the entity number shall become unassigned, PCOMP and DCOMP values shall be unassigned if necessary (see subclause 6.5.1.1.5), and then the proposed compression entity shall be responded to as usual. + - Otherwise (i.e. if the assigned entity number is not included, or is included with the P bit set to 0 in the incoming SNDCP XID block), the usual rules regarding collision handling shall apply. +- In the case of a collision in which a PCOMP or DCOMP value is currently assigned to a compression algorithm: + - If the peer SNDCP entity proposes a new compression entity with the same PCOMP or DCOMP assigned to a different algorithm, then it shall be assumed that the peer SNDCP entity negotiated the deletion of all + +entities using the algorithm to which the PCOMP or DCOMP value was assigned, but the response was lost, and the PCOMP or DCOMP value is being reused. Therefore, all compression entities using that algorithm shall be deleted, all corresponding entity numbers shall become unassigned, and all PCOMP or DCOMP values assigned to the algorithm shall become unassigned, and then the proposed compression entity shall be responded to as usual. + +- Otherwise (i.e. if the assigned PCOMP or DCOMP is not included, or is included and assigned to the same algorithm), the usual rules regarding collision handling shall apply. + +##### 6.5.1.1.4 Algorithm identifier + +Table 4 show the list of protocol control information compression algorithms supported by the SNDPCP layer. When new compression algorithms are needed for SNDPCP, table 4 shall be updated. + +**Table 4: List of protocol control information compression algorithms supported by SNDPCP** + +| Compression algorithm | Algorithm identifier (Range 0 to 31) | +|-----------------------|--------------------------------------| +| RFC 1144 | 0 | +| RFC 2507 | 1 | +| ROHC | 2 | +| - | Other values Reserved | + +##### 6.5.1.1.5 PCOMP + +One or more PCOMP values shall be assigned dynamically to a compression algorithm, based on the negotiation of the XID parameters for protocol control information compression. Each of the assigned PCOMP values denotes one compressed frame type of that compression algorithm. + +The assignment of the PCOMP values follows the following general rules: + +- PCOMP shall be an integer from 0 to 15. +- PCOMP value 0 is reserved permanently for no compression. +- PCOMP shall be assigned independently on each of the SAPIs. +- An assigned PCOMP value applies to all NSAPIs mapped to the same SAPI. +- PCOMP values shall be assigned to compression algorithms, not to compression entities (i.e. the same PCOMP value(s) shall be used by different compression entities on the same SAPI using the same compression algorithm). +- A PCOMP value shall be in one of the three states: unassigned, selected, or assigned. +- When a new compression entity is to be proposed, and if PCOMP values have not yet been assigned to the corresponding compression algorithm, then the appropriate number of unassigned PCOMP values shall be selected. If there is not enough unassigned PCOMP values left, the compression entity shall not be proposed. +- A selected PCOMP value shall become assigned if the corresponding proposed compression entity is created as a result of the XID negotiation, otherwise it shall become unassigned. +- An assigned PCOMP value shall become unassigned when the corresponding compression algorithm is no longer in use by any compression entity, or upon the receipt of the LL-RESET.indication primitive. +- In the case of a collision (see subclause 6.2.1.4), the handling of PCOMP values shall be in accordance with subclause 6.5.1.1.3. + +While transferring data, the compressed frame type for an N-PDU is conveyed in the PCOMP field of the SNDPCP header of the first SN-PDU belonging to the N-PDU. Any successfully negotiated algorithm may be used for compression of an N-PDU. + +#### 6.5.1.2 Resetting compression entities following SNDPCP XID negotiation + +The LL-Establish primitives shall be used for the negotiation of protocol control information compression if: + +- one or more parameters, excluding the applicable NSAPIs, of existing compression entities used with acknowledged peer-to-peer LLC operation are changed by the originator of the negotiation; or +- one or more NSAPIs are removed, by the originator of the negotiation, from existing compression entities used with acknowledged peer-to-peer LLC operation, except when all NSAPIs using the compression entity are removed, or when LLC is already in ADM. + +Otherwise, either the LL-Establish primitives or the LL-XID primitives may be used. + +If the LL-XID primitives are used for XID negotiation, then in addition to restrictions specified elsewhere in the present document, the following parameters of the protocol control information compression entities are non-negotiable by the responding SNDPCP entity: + +- any parameter of existing compression entities used with acknowledged peer-to-peer LLC operation. + +If one or more parameters, other than the applicable NSAPIs, of a compression entity used with unacknowledged peer-to-peer LLC operation are changed, the compression entity shall be reset locally upon completion of the SNDPCP XID negotiation. + +#### 6.5.1.3 Parameters for compression entities + +On negotiating a compression entity, not all the parameters of the entity have to be specified. If a parameter is to be included, all the preceding parameters shall also be specified, and the length field shall be set to the sum of the lengths of all the parameters specified. If any of the parameters is not specified, the rules in subclause 6.8.2 shall apply. + +### 6.5.2 TCP/IP header compression (RFC1144) + +The protocol control information compression method is specific for each network layer protocol type. TCP/IP (IPv4) header compression is specified in RFC 1144 [9]. + +#### 6.5.2.1 Parameters + +Table 5 contains the parameters defined for a compression entity using TCP/IP header compression. They may be negotiated during SNDPCP XID negotiation. + +**Table 5: RFC 1144 TCP/IP header compression parameters** + +| Algorithm Name | Algorithm Identifier | Length | Parameters | | | | | +|----------------|----------------------|---------------------------------------------------|--------------------|---------------------|-----------------------|----------------------------|---------------| +| | | | Parameter Name | Format | Range | Sense of Negotiation | Default Value | +| RFC 1144 | 0 | 0, 2 or 3 if P bit is 0, 1, 3 or 4 if P bit is 1. | Applicable NSAPIs | bbbbbbb
bbb00000 | 0, 32, 64, ..., 65504 | down (each bit separately) | 0 | +| | | | S 0 - 1 | bbbbbbb | 0 through 255 | down | 15 | + +##### 6.5.2.1.1 Applicable NSAPIs + +See subclause 7.1.3. + +##### 6.5.2.1.2 S0 + +The number of state slots, as defined in [9]. The S0 range is 1 through 256, with 16 as default value. + +#### 6.5.2.2 Assignment of PCOMP values + +The underlying service shall be able to distinguish the three types of compressed N-PDUs (i.e. Type IP, Uncompressed TCP, and Compressed TCP), as defined in RFC 1144 [9]. These three N-PDU types are differentiated by using different PCOMP values. + +Two PCOMP values shall be assigned to the TCP/IP header compression algorithm. PCOMP1 shall contain the PCOMP value for the frame type "Uncompressed TCP", and PCOMP2 shall contain the PCOMP value for the frame type "Compressed TCP". + +The PCOMP value of 0 shall be used for the frame type "Type IP". + +#### 6.5.2.3 Error Recovery + +When TCP/IP header compression is used with unacknowledged peer-to-peer LLC operation, the decompression entity shall be notified in case an N-PDU is dropped, so that error recovery procedure (see RFC 1144 [9]) can be invoked. + +### 6.5.3 TCP/IP and UDP/IP header compression (RFC 2507) + +Detailed operation of the RFC 2507 header compression for IPv4 and IPv6 is described in clause 3 of the IETF specification RFC 2507 [10]. + +#### 6.5.3.1 Parameters + +Table 6 contains the parameters defined for a compression entity using RFC2507 header compression. They may be negotiated during SNDPCP XID negotiation. + +**Table 6: RFC 2507 TCP/IP and UDP/IP header compression parameters** + +| Algorithm Name | Algorithm Identifier | Length | Parameters | | | | | +|----------------|----------------------|-----------------------------------------------------------------------------|-------------------|-------------------|------------------------|----------------------------|---------------| +| | | | Parameter Name | Format | Range | Sense of Negotiation | Default Value | +| RFC 2507 | 1 | 0, 2, 4, 5, 6, 7 or 9 if P bit is 0, 3, 5, 7, 8, 9, 10 or 12 if P bit is 1. | Applicable NSAPIs | bbbbbbbb bbb00000 | 0, 32, 64, ... , 65504 | down (each bit separately) | 0 | +| | | | F_MAX_PE | bbbbbbbb | 1-65535 | down | 256 | +| | | | RIOD | bbbbbbbb | | | | +| | | | F_MAX_TIME | bbbbbbbb | 1-255 | down | 5 | +| | | | MAX_HEADER | bbbbbbbb | 60-255 | down | 168 | +| | | | TCP_SPACE | bbbbbbbb | 3-255 | down | 15 | +| | | | NON_TCP_SPACE | bbbbbbbb bbbbbbbb | 3-65535 | down | 15 | + +The explanation of the individual parameters can be found in the clause 14 of the IETF specification RFC 2507 [10]. + +##### 6.5.3.1.1 Applicable NSAPIs + +See subclause 7.1.3. + +#### 6.5.3.2 Assignment of PCOMP values for RFC2507 + +The following PCOMP values shall be assigned to the RFC 2507 header compression. The PCOMP value 0 shall be used for regular IPv4 and IPv6 packets. + +**Table 7: PCOMP values assigned to RFC 2507 header compression algorithm** + +| PID value | Packet type | +|-----------|--------------------------| +| PCOMP1 | Full header | +| PCOMP2 | Compressed TCP | +| PCOMP3 | Compressed TCP non-delta | +| PCOMP4 | Compressed non-TCP | +| PCOMP5 | Context state | + +#### 6.5.3.3 Error Recovery + +The mechanisms related to error recovery and packet reordering are described in clauses 10 and 11 of the RFC 2507[10]. + +### 6.5.4 Robust Header Compression (ROHC) + +Robust Header Compression (ROHC) is a framework for header compression, on top of which compression schemes can be defined for the compression of various protocol headers. Both the SNDPCP ROHC negotiation mechanisms and the SN-PDU ROHC identifiers are generally defined for the ROHC framework, and therefore capable of handling both existing and future ROHC compression protocols (profiles). RFC 5795 [12] defines the ROHC framework, as well as the compression schemes and profiles for RTP/UDP/IP, UDP/IP, ESP/IP and uncompressed. + +#### 6.5.4.1 Parameters + +Table 10 contains the parameters defined for a compression entity using ROHC. They may be negotiated during SNDPCP XID negotiation. + +**Table 10: Robust Header Compression (ROHC) parameters** + +| Algorithm Name | Algorithm Identifier | Length | Parameters | | | | | +|----------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------|-----------------------|----------------------------|---------------| +| | | | Parameter Name | Format | Range | Sense of Negotiation | Default Value | +| ROHC | 2 | 0, 2, 4, 6, 8, 8+n*2 if P bit is 0, 1, 3, 5, 7, 9, 9+n*2 if P bit is 1. (where n is the number of profiles, the max. number of profiles is 16) | Applicable NSAPs | bbbbbbb bbb00000 | 0, 32, 64, ..., 65504 | down (each bit separately) | 0 | +| | | | MAX_CID | 00bbbbbb bbbbbbbb | 0-16383 | down | 15 | +| | | | MAX_HEADER | 00000000 bbbbbbbb | 60-255 | down | 168 | +| | | | PROFILE 1 | bbbbbbb bbbbbbbb | 0-65535 | (see 6.5.4.1.5) | 0 | +| | | | PROFILE 2 | bbbbbbb bbbbbbbb | 0-65535 | (see 6.5.4.1.5) | 0 | +| | | | ... | ... | ... | ... | ... | +| | | | PROFILE 16 | bbbbbbb bbbbbbbb | 0-65535 | (see 6.5.4.1.5) | 0 | + +NOTE: ROHC parameter MRRU is not negotiated and shall be set to 0, i.e. ROHC segmentation shall not be used. + +##### 6.5.4.1.1 Applicable NSAPs + +See subclause 7.1.3. + +##### 6.5.4.1.2 MAX\_CID + +The MAX\_CID parameter indicates the maximum context ID number the compressor is allowed to use. A MAX\_CID value of N means CID values of 0 through N are valid. Thus, the number of contexts allowed is N+1, e.g. MAX\_CID of 15 means 16 contexts are allowed. + +##### 6.5.4.1.3 MAX\_HEADER + +The MAX\_HEADER parameter indicates the maximum number of octets of the protocol control information that may be compressed. + +NOTE: The MAX\_HEADER parameter is neither defined nor used by RTP/UDP/IP, UDP/IP, ESP/IP and uncompressed profiles as defined in RFC 5795 [12]. For those profiles, this parameter is not used by SNDPCP when performing Robust Header Compression (ROHC). + +##### 6.5.4.1.4 (Void) + +##### 6.5.4.1.5 PROFILE + +The PROFILE parameter indicates the profile identifier. A list of up to 16 PROFILES, indicating which ROHC profiles [14] are supported may be included. The negotiated list which is used for compression consists of the list of profiles supported by both peer entities, reduced to include at most ONE profile identifier with the same 8-bit LSB part. If both peer entities support more than one profile with the same 8-bit LSB part in its profile identifier, the set of these profiles shall be reduced to the profile with the highest MSB-value in its profile identifier. + +Note: The reason for this is that the 8-bit MSB part of the profile identifier indicates the "variant" of the profile, and since only the 8-bit LSB part is sent in compressed headers, the set of available profiles must not include two profiles with the same 8-bit LSB part of the profile identifier. + +#### 6.5.4.2 Assignment of PCOMP values for ROHC + +As opposed to other header compression schemes, the whole ROHC framework has only one packet type that has to be identified by the PDU format, and this packet type can be used by any ROHC compression profile. However, ROHC has two different context identification (CID) sizes. To avoid having to negotiate and potentially re-negotiate CID size, the mechanism from ROHC-over-PPP [13] is adopted in SNDPCP, i.e. as shown in table 9, two packet types are defined for ROHC, one for small and one for large CIDs. + +This implies that all CIDs within one ROHC packet shall be of the same size as indicated by the PID value, either small or large. In particular, embedded feedback shall have a CID of the same size as indicated by the PID value. For piggybacking feedback, a compressor must be able to control the feedback CID size used by the associated decompressor, ensure that all CIDs are of the same size, and indicate this size with the appropriate PID value. + +**Table 9: PCOMP values assigned to Robust Header Compression (ROHC)** + +| PID value | Packet type | +|-----------|-----------------| +| PCOMP1 | ROHC small-CIDs | +| PCOMP2 | ROHC large-CIDs | + +#### 6.5.4.3 Error Recovery and other feedback + +ROHC has built-in robustness mechanisms to avoid error events, as well as error recovery mechanisms using decompressor to compressor feedback. Such ROHC feedback is carried according to alternative 6) in section 5.2.1 of RFC 5795 [12]. + +### 6.5.5 Pre-defined Protocol control information ROHC compression types for MBMS + +An SGSN supporting compression for MBMS shall not negotiate compression information with the MSes. An MS which is capable of MBMS shall support pre-defined compression types and associated configuration information. + +An SNDPCP entity performing Robust Header Compression (ROHC) for MBMS data traffic shall use the following parameter values: + +- Only Unidirectional mode (U-mode) as defined in RFC 5795 [12] shall be used. +- Only profiles for RTP/UDP/IP, UDP/IP and uncompressed as specified in RFC 5795 [12] shall be used. +- Applicable NSAPI = 1. +- MAX\_CID set to 511 (i.e. 512 contexts are allowed). The MS shall handle CIDs in the value range of 0 to 511 as used by the SGSN. However, the maximum number of ROHC decompressor contexts the MS simultaneously supports is implementation specific. + +The SNDPCP PCOMP values assigned to ROHC for MBMS are preconfigured to PCOMP = 0 which indicates that header compression is not used, PCOMP = 1: ROHC small-CIDs, and PCOMP = 2: ROHC large-CIDs. + +MAX\_CID, and PCOMP parameters are described in subclauses 6.5.4.1.2 and 6.5.4.2, respectively. + +If decompression fails, e.g. due to a cell change, the MS shall reconfigure and re-initialise the SNDPCP entity, reusing the static part of the header decompressor context previously used. Also, after receiving an IR-DYN or IR packet (see RFC 5795 [12]), the MS shall re-initialise header decompression. + +The compressor entity in the SGSN shall periodically transit to lower compression states in order for the decompressor entities in the MSes to synchronise with the compressor. For further details about this mechanism, please refer to RFC 5795 [12]. + +## 6.6 Data compression + +Data compression is an optional SNDPCP feature. Data compression applies to both SN-DATA and SN-UNITDATA primitives. + +Data compression, if used, shall be performed on the entire N-PDU, including the possibly compressed protocol control information. + +Figure 8 shows an example how the SNDPCP functions may be used. Several NSAPIs may use a common data compression entity, i.e. the same compression algorithm and the same dictionary. Separate data compression entities shall be used for acknowledged (SN-DATA) and unacknowledged (SN-UNITDATA) data transfer. Several NSAPIs may be associated with one SAPI, i.e. they may use the same QoS profile. + +![Diagram illustrating the usage of NSAPIs, SNDPCP functions, and SAPIs. At the top, four boxes labeled 'PDP or Relay' represent SNDPCP users. Below them, four ovals labeled 'NSAPI' (5, 6, 7, 8) and an ellipsis followed by '15' are shown. Lines connect each PDP or Relay to its corresponding NSAPI. Below the NSAPIs is a large box labeled 'SNDPCP layer'. Inside this layer, NSAPI 5 connects to a 'Protocol compr.' box, which then connects to a 'Data compr.' box. NSAPI 6 connects directly to a 'Data compr.' box. NSAPI 7 connects directly to a 'Data compr.' box. NSAPI 8 connects to another 'Protocol compr.' box, which then connects to a 'Data compr.' box. Dashed lines connect the 'Data compr.' boxes for NSAPIs 5, 6, and 7 to a common point. Below the SNDPCP layer, four ovals labeled 'SAPI' (LL 3, LL 5, LL 9, LL 11) are shown. Lines connect the 'Data compr.' boxes to these SAPIs: the 'Data compr.' box for NSAPI 5 connects to LL 3, the 'Data compr.' box for NSAPI 6 connects to LL 5, the 'Data compr.' box for NSAPI 7 connects to LL 9, and the 'Data compr.' box for NSAPI 8 connects to LL 11. At the bottom is a box labeled 'LLC layer entity', which receives connections from all four SAPIs.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +Diagram illustrating the usage of NSAPIs, SNDPCP functions, and SAPIs. At the top, four boxes labeled 'PDP or Relay' represent SNDPCP users. Below them, four ovals labeled 'NSAPI' (5, 6, 7, 8) and an ellipsis followed by '15' are shown. Lines connect each PDP or Relay to its corresponding NSAPI. Below the NSAPIs is a large box labeled 'SNDPCP layer'. Inside this layer, NSAPI 5 connects to a 'Protocol compr.' box, which then connects to a 'Data compr.' box. NSAPI 6 connects directly to a 'Data compr.' box. NSAPI 7 connects directly to a 'Data compr.' box. NSAPI 8 connects to another 'Protocol compr.' box, which then connects to a 'Data compr.' box. Dashed lines connect the 'Data compr.' boxes for NSAPIs 5, 6, and 7 to a common point. Below the SNDPCP layer, four ovals labeled 'SAPI' (LL 3, LL 5, LL 9, LL 11) are shown. Lines connect the 'Data compr.' boxes to these SAPIs: the 'Data compr.' box for NSAPI 5 connects to LL 3, the 'Data compr.' box for NSAPI 6 connects to LL 5, the 'Data compr.' box for NSAPI 7 connects to LL 9, and the 'Data compr.' box for NSAPI 8 connects to LL 11. At the bottom is a box labeled 'LLC layer entity', which receives connections from all four SAPIs. + +Figure 8: An example for the usage of NSAPIs, SNDPCP functions, and SAPIs + +### 6.6.1 Negotiation of multiple data compression types + +Each SNDPCP entity that supports data compression shall be able to negotiate one or several data compression entities with the compression field format shown in figure 9. The negotiation shall be carried out using the XID parameter negotiation specified in subclause 6.8. The initiating entity defines a set of requested compression entities, together with the algorithm and parameters for each compression entity. The set of entities and their algorithms and parameters shall be transmitted to the peer entity. The peer entity responds with the set of negotiated entities and their algorithms and parameters. The peer entity shall select the proposed parameter values or other appropriate values for the negotiated entities. If more than one data compression algorithm for a specific NSAPI is proposed during the XID negotiation then the receiving peer entity shall only choose one algorithm for that NSAPI. + +#### 6.6.1.1 Format of the data compression field + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|---------|------------------|---|---|----------------------|--------|---|---|---|--|--|--|--| +| Octet 1 | P | X | X | Entity number | | | | | | | | | +| Octet 2 | X | X | X | Algorithm identifier | | | | | | | | | +| Octet 3 | Length=n-3 | | | | | | | | | | | | +| Octet 4 | DCOMP1 | | | | DCOMP2 | | | | | | | | +| ... | ... | | | | ... | | | | | | | | +| Octet x | High-order octet | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | +| Octet n | Low-order octet | | | | | | | | | | | | + +NOTE: The two octets x and x+1, if included, contain the "Applicable NAPs" parameter (see subclause 7.1.3). + +**Figure 9: Data compression field format for SNDPCP XID negotiation** + +##### 6.6.1.1.1 Spare bit (X) + +The X bit shall be set to 0 by the transmitting SNDPCP entity and shall be ignored by the receiving SNDPCP entity. + +##### 6.6.1.1.2 Propose bit (P) + +The P bit shall be set to 1 if a new compression entity is being proposed, otherwise it shall be set to 0. If the P bit is set to 1, then all octets shall be included, otherwise octet 2 and octets 4 to x-1 shall not be included. If the P bit is set to 1, then only enough number of octets shall be included to contain the number of DCOMP values needed by the corresponding compression algorithm (e.g. DCOMP3 and DCOMP4 shall not be included if the number of DCOMP values needed by a compression algorithm is one or two). If an odd number of DCOMP values are used by a compression algorithm, then the last DCOMP value shall be set to 0 in the compression field by the transmitting SNDPCP entity, and it shall be ignored by the receiving SNDPCP entity. + +##### 6.6.1.1.3 Entity number + +The entity number shall be used to identify a data compression entity on a SAPI. See subclause 6.5.1.1.3 for the rules for assigning entity numbers. The assignment of entity numbers for protocol control information compression entities and data compression entities shall be independent. + +##### 6.6.1.1.4 Algorithm identifier + +Table 6a shows the list of data compression algorithms supported by the SNDPCP layer. When new compression algorithms are needed for SNDPCP, table 6a shall be updated. + +**Table 6a: List of data compression algorithms supported by SNDPCP** + +| Data compression algorithm | Algorithm identifier (Range 0-31) | +|----------------------------|-----------------------------------| +| V.42 bis | 0 | +| V.44 | 1 | +| - | Other values Reserved | + +##### 6.6.1.1.5 DCOMP + +One or more DCOMP values shall be assigned dynamically to a compression algorithm, based on the negotiation of the XID parameters for data compression. Each of the assigned DCOMP values denotes one compressed frame type of that compression algorithm. + +The assignment of the DCOMP values shall follow the rules for the assignment of PCOMP values in subclause 6.5.1.1.5. + +While transferring data, the compressed frame type for an N-PDU is conveyed in the DCOMP field of the SNDCP header of the first SN-PDU belonging to the N-PDU. Any successfully negotiated algorithm may be used for compression of an N-PDU. + +#### 6.6.1.2 Resetting compression entities following SNDCP XID negotiation + +The LL-Establish primitives shall be used for the negotiation of data compression if: + +- one or more parameters, excluding the applicable NSAPs, of existing compression entities used with acknowledged peer-to-peer LLC operation are changed by the originator of the negotiation; or +- one or more NSAPs are removed, by the originator of the negotiation, from existing compression entities used with acknowledged peer-to-peer LLC operation, except when all NSAPs using the compression entity are removed, or when LLC is already in ADM. + +Otherwise, either the LL-Establish primitives or the LL-XID primitives may be used. + +If the LL-XID primitives are used for XID negotiation, then in addition to restrictions specified elsewhere in the present document, the following parameters of the data compression entities are non-negotiable by the responding SNDCP entity: + +- any parameter of existing compression entities used with acknowledged peer-to-peer LLC operation. + +If one or more parameters, other than the applicable NSAPs, of a compression entity used with unacknowledged peer-to-peer LLC operation are changed, the compression entity shall be reset locally upon completion of the SNDCP XID negotiation. + +#### 6.6.1.3 Parameters for compression entities + +On negotiating a compression entity, not all the parameters of the entity have to be specified. If a parameter is to be included, all the preceding parameters shall also be specified, and the length field shall be set to the sum of the lengths of all the parameters specified. If any of the parameters is not specified, the rules in subclause 6.8.2 shall apply. + +### 6.6.2 Management of V.42 bis data compression + +ITU-T Recommendation V.42 bis [8] data compression may be used with SN-DATA primitives and SN-UNITDATA primitives. + +#### 6.6.2.1 Parameters + +Table 7a contains the parameters defined for a compression entity using ITU-T Recommendation V.42 bis data compression. They may be negotiated during SNDCP XID negotiation. + +**Table 7a: V.42 bis data compression parameters** + +| Algorithm Name | Algorithm Identifier | Length | Parameters | | | | | +|----------------|----------------------|-----------------------------------------------------------------|------------------|---------------------|-----------------------|----------------------------------|---------------| +| | | | Parameter Name | Format | Range | Sense of Negotiation | Default Value | +| V.42 bis | 0 | 0, 2, 3, 5, or 6 if P bit is 0, 1, 3, 4, 6, or 7 if P bit is 1. | Applicable NSAPs | bbbbbbb
bbb00000 | 0, 32, 64, ..., 65504 | down (each bit separately) | 0 | +| | | | P 0 | 000000bb | 0 through 3 | down (each direction separately) | 3 | +| | | | P 1 | bbbbbbb
bbbbbbb | 512 through 65535 | down | 2048 | +| | | | P 2 | bbbbbbb | 6 through 250 | down | 20 | + +##### 6.6.2.1.1 Applicable NSAPs + +See subclause 7.1.3. + +##### 6.6.2.1.2 $P_0$ + +Two bits are used to indicate the usage of compression, one bit for each direction. + +00 compress neither direction. + +01 compress MS-to-SGSN direction only. + +10 compress SGSN-to-MS direction only. + +11 compress both directions. + +##### 6.6.2.1.3 $P_1$ + +Maximum number of codewords in the compressor dictionary (see [8]). + +##### 6.6.2.1.4 $P_2$ + +Maximum number of characters in an uncompressed data string that is accepted to be encoded. + +#### 6.6.2.2 Assignment of DCOMP values + +One DCOMP value shall be assigned (as DCOMP1) to the V.42 bis data compression algorithm. + +#### 6.6.2.3 Operation of V.42 bis data compression + +When V.42 bis is used with SN-DATA primitives, the data in the compression entity shall be flushed (using the C-FLUSH primitive defined in [8]) and added to the compressed N-PDU before the compressed N-PDU is sent. + +When V.42 bis is used with SN-UNITDATA primitives, the compression entity shall be reset (using the C-INIT primitive defined in [8]) before an N-PDU is compressed or decompressed. After compression, the data in the compression entity shall be flushed (using the C-FLUSH primitive defined in [8]) and added to the compressed N-PDU before the compressed N-PDU is sent. The LLC protocol shall operate in the protected mode of operation. + +When V.42 bis is used with SN-DATA primitives and an error is detected by the decoder, the SNDPCP entity shall use LL-ESTABLISH.request primitive to reset the acknowledged peer-to-peer LLC operation for the SAPI used. + +### 6.6.3 Management of V.44 data compression + +ITU-T Recommendation V.44 data compression, as described in [11], may be used with SN-DATA primitives and SN-UNITDATA primitives. Annex B of ITU-T Recommendation V.44 describes two methods of implementation and operation of V.44 in packet networks: Packet Method and Multi-Packet Method. Multi-Packet Method is a superset of Packet Method and an MS or SGSN that supports Multi-Packet Method must also support Packet Method. + +#### 6.6.3.1 Parameters + +Table 7c contains the parameters defined for a compression entity using V.44 data compression. They may be negotiated during SNDPCP XID negotiation. During V.44 data compression negotiation, unless both the MS and SGSN support Multi-Packet Method, Packet Method is used. Parameter $C_0$ indicates support of Packet Method (10000000) or both methods (11000000). + +NOTE 1: V.44 data compression negotiation is not required. If V.44 is selected and no compression parameters are specified, then Packet Method with defaults as defined in subclauses 6.6.3.1.4 and 6.6.3.1.5 and in [11] annex B, clause B.1.2, is used. + +**Table 7c: V.44 data compression parameters** + +| Algorithm Name | Algorithm Identifier | Length | Parameters | | | | | +|----------------|----------------------|--------------------------------------------------------------------------------------|-------------------|---------------------|--------------------------|----------------------------------|------------------------------| +| | | | Parameter Name | Format | Range | Sense of Negotiation | Default Value | +| V.44 | 1 | 0, 2, 3, 4, 6, 8, 10, or 12 if P bit is 0, 1, 3, 4, 5, 7, 9, 11, or 13 if P bit is 1 | Applicable NSAPIs | bbbbbbb
bbb00000 | 0, 32, 64, ..., 65504 | down (each bit separately) | 0 | +| | | | C 0 | bb000000 | 10000000 or 11000000 | 11000000 down to 10000000 | 10000000 | +| | | | P 0 | 000000bb | 0 through 3 | down (each direction separately) | 3 | +| | | | P 1T | bbbbbbb
bbbbbbb | 256 through 65535 | down | Refer to subclause 6.6.3.1.4 | +| | | | P 1R | bbbbbbb
bbbbbbb | 256 through 65535 | down | Refer to subclause 6.6.3.1.5 | +| | | | P 3T | bbbbbbb
bbbbbbb | ≥ (2 × P 1T ) | down | 3 × P 1T | +| | | | P 3R | bbbbbbb
bbbbbbb | ≥ (2 × P 1R ) | down | 3 × P 1R | + +NOTE 2: V.44 parameters P2T and P2R are set to 255 and not negotiated in packet networks. + +##### 6.6.3.1.1 Applicable NSAPIs + +See subclause 7.1.3. + +##### 6.6.3.1.2 C0 + +Two bits are used to indicate the V.44 method of operation supported (refer to [11] Annex B). + +10 Packet Method supported. + +11 Packet Method and Multi-Packet Method supported. + +If parameter C0 is not specified then Packet Method is selected with its default parameter values (refer to subclauses 6.6.3.1.4 and 6.6.3.1.5 and in [11] annex B, clause B.1.2). + +##### 6.6.3.1.3 P0 + +Two bits are used to indicate the usage of compression, one bit for each direction. + +00 compress neither direction. + +01 compress MS-to-SGSN direction only. + +10 compress SGSN-to-MS direction only. + +11 compress both directions. + +##### 6.6.3.1.4 P1T + +Maximum number of codewords for the transmit direction (i.e. in the encoder dictionary). Refer to ITU-T Recommendation V.44 [11]. + +The Packet Method default is 1 600 codewords. + +The Multi-Packet Method default is 2 048 codewords. + +NOTE: Both defaults above are different from the defaults specified in ITU-T Recommendation V.44 [11] annex B. This is partially due to the fact that data compression in SNDPCP includes the control header as well as the information field. + +##### 6.6.3.1.5 $P_{1R}$ + +Maximum number of codewords for the receive direction (i.e. in the decoder dictionary). Refer to [11]. + +The Packet Method default is 1 600 codewords. + +The Multi-Packet Method default is 2 048 codewords. + +NOTE: Both defaults above are different from the defaults specified in ITU-T Recommendation V.44 [11] annex B. This is partially due to the fact that data compression in SNDPCP includes the control header as well as the information field. + +##### 6.6.3.1.6 $P_{3T}$ + +Number of characters in the history for the transmit direction. Refer to [11]. + +This parameter is not used in Packet Method. + +##### 6.6.3.1.7 $P_{3R}$ + +Number of characters in the history for the receive direction. Refer to [11]. + +This parameter is not used in Packet Method. + +#### 6.6.3.2 Assignment of DCOMP values + +The underlying service shall be able to distinguish three types of N-PDUs processed by V.44 data compression (i.e. not V.44 compressed, V.44 Packet Method compressed, and V.44 Multi-Packet Method compressed). These three V.44 processed N-PDU types are differentiated by using different DCOMP values. + +Two DCOMP values shall be assigned to the V.44 compression algorithm, the smaller one of which for Packet Method compressed, and the larger one for Multi-Packet Method compressed. + +The DCOMP value of 0 shall be used for SN-PDUs belonging to N-PDUs that expanded during V.44 compression and are sent in their original form (i.e. not V.44 compressed). + +#### 6.6.3.3 Operation of V.44 data compression + +V.44 data compression has two possible methods of operation in SNDPCP, Packet Method and Multi-Packet Method. + +##### 6.6.3.3.1 Packet Method + +Refer to [11] annex B, clause B.1, for a general description of the operation of V.44 packet method. + +When V.44 Packet Method is used with SN-DATA primitives: + +- the data in the compression entity shall be flushed (using the C-FLUSH primitive defined in [11]) after the last character of an N-PDU is passed to the encoder. +- If the length of the N-PDU after compression is greater or equal to the length of the original N-PDU, the original N-PDU is sent and the DCOMP field in the SN-PDU header of the first segment of the N-PDU is set to 0, not V.44 compressed. +- In between processing of N-PDU, the dictionary shall be re-initialised as defined in [11]. +- If an error is detected by the decoder, the SNDPCP entity shall use LL-ESTABLISH.request primitive to reset the acknowledged peer-to-peer LLC operation for the SAPI used. + +When V.44 Packet Method is used with SN-UNITDATA primitives: + +- the data in the compression entity shall be flushed (using the C-FLUSH primitive defined in [11]) after the last character of an N-PDU is passed to the encoder. +- If the length of the N-PDU after compression is greater or equal to the length of the original N-PDU, the original N-PDU is sent and the DCOMP field in the SN-PDU header of the first segment of the N-PDU is set to 0, not V.44 compressed. +- After an N-PDU is sent, the dictionary shall be re-initialised as defined in [11]. +- The LLC protocol shall operate in the protected mode of operation. + +##### 6.6.3.3.2 Multi-Packet Method + +Refer to [11] annex B, clause B.2, for a general description of the operation of V.44 multi-packet method. + +When V.44 Multi-Packet Method is used with SN-DATA primitive: + +- the data in the compression entity shall be flushed (using the C-FLUSH primitive defined in [11]) after the last character of an N-PDU is passed to the encoder. +- If the length of the N-PDU after compression is greater than the length of the original N-PDU, the original N-PDU is sent and the DCOMP field in the SN-PDU header of the first segment of the N-PDU is set to 0, not V.44 compressed. +- In the case above of not V.44 compressed where the original N-PDU is sent, after the N-PDU is sent the encoder dictionary shall be re-initialised as defined in [11]. The peer entity, upon receipt of an N-PDU with the DCOMP field set to 0, not V.44 compressed, shall re-initialise its decoder dictionary. +- If an error is detected by the decoder, the SNDPCP entity shall use LL-ESTABLISH.request primitive to reset the acknowledged peer-to-peer LLC operation for the SAPI used. + +When V.44 Multi-Packet Method is used with SN-UNITDATA primitives: + +- the data in the compression entity shall be flushed (using the C-FLUSH primitive defined in [11]) after the last character of an N-PDU is passed to the encoder. +- After an N-PDU is sent the dictionary shall be re-initialised as defined in [11]. +- If the length of the N-PDU after compression is greater or equal to the length of the original N-PDU, the original N-PDU is sent and the DCOMP field in the SN-PDU header of the first segment of the N-PDU is set to 0, not V.44 compressed. +- The LLC protocol shall operate in the protected mode of operation. + +## 6.7 Segmentation and reassembly + +Segmentation shall be performed by the SNDPCP entity to ensure that any SN-PDU transmitted is no longer than N201 (no longer than (N201-U – 4), if integrity protection is used) (see 3GPP TS 44.064 [6]). The receiving SNDPCP entity shall reassemble the segments back to the original (possibly compressed) N-PDU. + +The segmentation and reassembly procedures are different for acknowledged and unacknowledged mode of operation. + +### 6.7.1 General + +#### 6.7.1.1 Segmentation + +A (possibly compressed) N-PDU shall be segmented into one or more SN-PDUs. The length of each SN-PDU shall not be greater than N201-I (for acknowledged mode) or N201-U (N201-U – 4, if integrity protection is used) (for unacknowledged mode). + +The F bit in the SNDPCP header shall be set to 1 for the first segment, and 0 for all subsequent segments. + +For unacknowledged peer-to-peer LLC operation, DCOMP and PCOMP shall be included in the header when the F bit is set to 1, and shall not be included when the F bit is set to 0. + +For acknowledged peer-to-peer LLC operation, DCOMP, PCOMP and N-PDU number shall be included in the header when the F bit is set to 1, and shall not be included when the F bit is set to 0. + +If an SN-PDU is received with the F bit set to 1 when a non-first segment is expected, and if DCOMP, PCOMP and (in the acknowledged mode) the N-PDU number all remain unchanged comparing to the first segment, then the SN-PDU shall be processed as normal. + +The M bit in the SNDCP header shall be set to 0 for the last segment, and 1 for all previous segments. + +If only one SN-PDU is generated for an N-PDU, the F bit shall be set to 1 and the M bit set to 0. + +#### 6.7.1.2 Reassembly + +During reassembly, DCOMP and PCOMP for an N-PDU shall be retrieved from the first segment (F bit set to 1). For acknowledged peer-to-peer LLC operation, the N-PDU number shall also be retrieved from the first segment. + +The receiving SNDCP entity shall be in one of the following three receiving states: + +- the Receive First Segment state, in which the SNDCP entity shall expect the F bit set to 1 in the next received SN-PDU; +- the Receive Subsequent Segment state, in which the SNDCP entity shall expect the F bit set to 0 in the next received SN-PDU; or +- the Discard state, in which the SNDCP entity shall discard any SN-PDU received. + +The Receive First Segment state shall be entered: + +- upon receipt of an SNSM-ACTIVATE.indication; +- upon receipt of an SNSM-MODIFY.indication which indicates a change in SAPI or a change in peer-to-peer LLC operation mode; +- upon receipt of an LL-ESTABLISH.indication or an LL-ESTABLISH.confirm; or +- when the M bit is set to 0 in the received SN-PDU, except for situations specified in subclause 6.7.4. + +The Receive Subsequent Segment state shall be entered: + +- when the M bit is set to 1 in the received SN-PDU, except for situations specified in subclause 6.7.4. + +### 6.7.2 Segmentation and reassembly in acknowledged mode + +Segmentation and reassembly in acknowledged mode shall follow the general procedures stated in subclause 6.7.1. + +### 6.7.3 Segmentation and reassembly in unacknowledged mode + +In addition to the general procedure in subclause 6.7.1, a segment number shall be used due to the unreliable nature of the unacknowledged mode. + +The Segment number is a sequence number assigned to each SN-UNITDATA PDU. The sequence number shall be set to 0 in the first SN-UNITDATA PDU of an N-PDU, and incremented by 1 for each subsequent SN-UNITDATA PDU. Modulo 16 operation is applied. + +The received segments belonging to the same N-PDU shall be re-ordered, if possible. If a timer (implementation dependent) elapses before all segments are received, the segments shall be discarded. Reassembly operation described in subclauses 6.7.1 and 6.7.4 shall be performed after re-ordering. + +### 6.7.4 Exception situations + +#### 6.7.4.1 Receive First Segment state + +If an SN-UNITDATA PDU is received with the F bit set to 0, the SN-UNITDATA PDU shall be discarded. The Receive First Segment state shall be entered if the M bit is set to 0, otherwise the Discard state shall be entered. + +If an SN-DATA PDU is received with the F bit set to 0, the SN-DATA PDU shall be discarded, and the acknowledged LLC operation shall be re-established for the SAPI used. + +#### 6.7.4.2 Receive Subsequent Segment state + +If an SN-UNITDATA PDU is received with the F bit set to 1, and if DCOMP or PCOMP is different from those in the first segment, then the SN-UNITDATA PDU and all previous segments belonging to the same N-PDU shall be discarded. The Received First Segment state shall be entered if the M bit is set to 0, otherwise the Discard state shall be entered. + +If an SN-DATA PDU is received with the F bit set to 1, and if DCOMP, PCOMP or N-PDU number is different from those in the first segment, then the SN-DATA PDU and all previous segments belonging to the same N-PDU shall be discarded, and the acknowledged LLC operation shall be re-established for the SAPI used. + +#### 6.7.4.3 Discard state + +If an SN-PDU is received with the M bit set to 1, the SN-PDU shall be discarded and the SNDCP entity shall remain in the Discard state. + +If an SN-PDU is received with the M bit set to 0, the SN-PDU shall be discarded and the Receive First Segment state entered. + +## 6.8 XID parameter negotiation + +Negotiation of XID parameters between peer SNDCP entities may be carried out to ensure optimal information transfer. The parameters are called SNDCP exchange identity (XID) parameters. + +SNDCP XID parameter negotiation may be initiated by the SNDCP entity at the MS or at the SGSN. The MS shall initiate SNDCP XID negotiation upon receipt of SNSM-ACTIVATE.indication, if SNDCP XID parameters are to be changed. The SGSN shall initiate SNDCP XID negotiation upon receipt of the SNSM-MODIFY.indication primitive if an NSAPI has been put into use (in the case of an Inter-SGSN Routeing Area Update), or if the change in QoS profile to an existing NSAPI results in a change in compressor(s) used by the NSAPI. + +When an NSAPI no longer uses a compression entity due to a PDP context deactivation or a PDP context modification, an SNDCP XID negotiation shall be performed to remove the NSAPI from the Applicable NSAPIs of the compression entity. The negotiation shall be initiated by the MS upon receipt of the SNSM-DEACTIVATE.indication with XID Negotiation Indicator in the case of explicit PDP context deactivation by peer-to-peer signalling between the SM entities. The negotiation shall be initiated by the SGSN upon receipt of the SNSM-MODIFY.indication in the case of PDP context modification. If a PDP context is deactivated locally, without peer-to-peer signalling between the SM entities, the SM entity at the MS and the SM entity at the SGSN each shall send an SNSM-DEACTIVATE.indication without XID Negotiation Indicator to its respective SNDCP entity. Upon receipt of this primitive without XID Negotiation Indicator the SNDCP entity shall remove the NSAPI from the Applicable NSAPIs of the compression entity without any XID negotiation. + +The XID negotiation is a one-step procedure; i.e. the initiating end proposes parameter values, and the responding end either accepts these or offers different values in their place according to the XID negotiation rules described in the present document; the rules limit the range of parameter values as well as the sense of negotiation. The initiating end accepts (or rejects) the values in the response; this concludes the negotiation. + +The block format for the SNDCP XID parameter negotiation is shown in figure 10. Not all parameters have to be included in the XID block, only parameters that are negotiated. Parameters may be included in any order. Also it shall be possible to negotiate parameters for more than one NSAPI in one XID block since more than one NSAPI can use the same SAPI. + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-------------------------|------------------|---|---|---------------|---|---|---|---|--|--|--|--|--| +| Octet 1 | Parameter type=0 | | | | | | | | | | | | | +| Octet 2 | Length=1 | | | | | | | | | | | | | +| Octet 3 | Version number | | | | | | | | | | | | | +| Octet 4 | Parameter type=1 | | | | | | | | | | | | | +| Octet 5 | Length=n-5 | | | | | | | | | | | | | +| Octet 6 | P | X | X | Entity number | | | | | | | | | | +| Octet 7 (optional) | | | | | | | | | | | | | | +| Octet 8 | Length=k-8 | | | | | | | | | | | | | +| Octet 9 ... (optional) | | | | | | | | | | | | | | +| Octet j | High-order octet | | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | | +| Octet k | Low-order octet | | | | | | | | | | | | | +| Octet k+1 | P | X | X | Entity number | | | | | | | | | | +| Octet k+2 (optional) | | | | | | | | | | | | | | +| Octet k+3 | Length=m-(k+3) | | | | | | | | | | | | | +| Octet k+4... (optional) | | | | | | | | | | | | | | +| Octet k+y | High-order octet | | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | | +| Octet m | Low-order octet | | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | | +| Octet n | Low-order octet | | | | | | | | | | | | | +| Octet n+1 | Parameter type=2 | | | | | | | | | | | | | +| Octet n+2 | Length=r-(n+2) | | | | | | | | | | | | | +| Octet n+3 | P | X | X | Entity number | | | | | | | | | | +| Octet n+4 (optional) | | | | | | | | | | | | | | +| Octet n+5 | Length=p-(n+5) | | | | | | | | | | | | | +| Octet n+6... (optional) | | | | | | | | | | | | | | +| Octet n+w | High-order octet | | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | | +| Octet p | Low-order octet | | | | | | | | | | | | | +| Octet p+1 | P | X | X | Entity number | | | | | | | | | | +| Octet p+2 (optional) | | | | | | | | | | | | | | +| Octet p+3 | Length=q-(p+3) | | | | | | | | | | | | | +| Octet p+4... (optional) | | | | | | | | | | | | | | +| Octet p+v | High-order octet | | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | | +| Octet q | Low-order octet | | | | | | | | | | | | | +| ... | ... | | | | | | | | | | | | | +| Octet r | Low-order octet | | | | | | | | | | | | | + +Figure 10: Example of SNDPC XID block format + +The SNDPC user uses SN-XID.request to initiate the negotiation of the XID parameters. The SNDPC entity sends the proposed SNDPC XID parameters to the LLC SAP with the LL-XID.request or LL-ESTABLISH.request. The LLC SAP shall issue an XID command containing the SNDPC XID parameters (see 3GPP TS 44.064 [6]). The peer LLC SAP shall, upon receipt of the XID command, indicate the SNDPC XID parameters to SNDPC entity using LL-XID.indication or LL-ESTABLISH.indication. The peer SNDPC entity shall select appropriate values for the proposed parameters or negotiate the appropriate values with the SNDPC user entity with the SN-XID.indication and SN-XID.response primitives. When the appropriate parameter values are known by the peer SNDPC entity, it shall use the LL-XID.response or LL-ESTABLISH.response primitive to continue negotiation. Upon reception of the response, the LLC SAP shall send the received parameters to the SNDPC entity using the LL-XID.confirm or LL-ESTABLISH.confirm primitive. The SNDPC entity delivers the negotiated parameters to the SNDPC user. This is illustrated in figure 11. The originator of the negotiation shall apply the new parameter values after it has received the 'confirm' primitive. The responding end of the negotiation shall apply the new parameter values after it has sent the replying 'response' primitive. + +Following the sending of the LL-XID.request or LL-ESTABLISH.request primitive with requested SNDPC XID parameters, the SNDPC layer shall suspend the transfer of LL-DATA primitives to the LLC SAP to which the LL-XID.request or LL-ESTABLISH.request is sent, but may continue the transfer of LL-UNITDATA primitives to that LLC SAP with the following restrictions: + +- if the transfer of a compressed N-PDU is ongoing when the SN-XID.request is received, the SNDPC layer shall complete the transfer of this N-PDU before sending the LL-XID.request or LL-ESTABLISH.request primitive with requested SNDPC XID parameters; and +- the SN-PDUs transferred in the LL-UNITDATA primitives during the SNDPC XID negotiation shall be uncompressed. + +When the SNDPC XID negotiation has been successfully completed, the SNDPC layer shall resume the transfer of LL-DATA primitives. If the transfer of LL-UNITDATA primitives was suspended, it shall also be resumed. + +The SNDPC XID negotiation ends through one of the following means: + +- successful (receiving LL-XID.confirm or LL-ESTABLISH.confirm); +- failure (receiving LL-RELEASE.indication, or LL-STATUS.indication); or +- successful following collision resolution (receiving LL-ESTABLISH.indication and sending LL-ESTABLISH.response, or receiving LL-XID.indication and sending LL-XID.response, see subclause 6.2.1.4). + +LLC may also initiate LLC XID negotiation, in which case LLC may send an LL-XID.indication to inform SNDPC the values of N201-I and N201-U. This is illustrated in figure 12. If the SNDPC entity receives an LL-XID.indication without an SNDPC XID block, it shall not respond with the LL-XID.response primitive. + +Negotiation of SNDPC version number is always between the peer SNDPC entities. The version number is not known by the SNDPC user. However, negotiation of the parameters for compression algorithms may be carried out between the SNDPC user entities. + +Negotiation of SNDPC XID parameters for an NSAPI shall be carried out in the SAPI to which the NSAPI is mapped. + +![Figure 11: SNDPCP XID negotiation procedure. This sequence diagram shows the interaction between an Originator and a Receiver. The Originator contains SNDPCP user, SNDPCP, and LLC entities. The Receiver contains LLC, SNDPCP, and SNDPCP user entities. The sequence starts with SN-XID.req from SNDPCP user to SNDPCP, followed by LL-XID.req from SNDPCP to LLC. The LLC entity on the Originator side sends an XID message to the LLC entity on the Receiver side. The Receiver's LLC entity responds with LL-XID.ind to its SNDPCP entity, which then sends SN-XID.ind to its SNDPCP user entity. The SNDPCP user entity on the Receiver side sends SN-XID.res back to its SNDPCP entity, which sends LL-XID.res to its LLC entity. The LLC entity on the Receiver side sends an XID message back to the LLC entity on the Originator side. The Originator's LLC entity responds with LL-XID.cnf to its SNDPCP entity, which then sends SN-XID.cnf to its SNDPCP user entity.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Figure 11: SNDPCP XID negotiation procedure. This sequence diagram shows the interaction between an Originator and a Receiver. The Originator contains SNDPCP user, SNDPCP, and LLC entities. The Receiver contains LLC, SNDPCP, and SNDPCP user entities. The sequence starts with SN-XID.req from SNDPCP user to SNDPCP, followed by LL-XID.req from SNDPCP to LLC. The LLC entity on the Originator side sends an XID message to the LLC entity on the Receiver side. The Receiver's LLC entity responds with LL-XID.ind to its SNDPCP entity, which then sends SN-XID.ind to its SNDPCP user entity. The SNDPCP user entity on the Receiver side sends SN-XID.res back to its SNDPCP entity, which sends LL-XID.res to its LLC entity. The LLC entity on the Receiver side sends an XID message back to the LLC entity on the Originator side. The Originator's LLC entity responds with LL-XID.cnf to its SNDPCP entity, which then sends SN-XID.cnf to its SNDPCP user entity. + +Figure 11: SNDPCP XID negotiation procedure + +![Figure 12: LLC XID negotiation procedure. This sequence diagram shows the interaction between an Originator and a Receiver. The Originator contains SNDPCP user, SNDPCP, and LLC entities. The Receiver contains LLC, SNDPCP, and SNDPCP user entities. The sequence starts with an XID message from the LLC entity on the Originator side to the LLC entity on the Receiver side. The Receiver's LLC entity responds with an XID message back to the Originator's LLC entity. The Originator's LLC entity then sends LL-XID.ind to its SNDPCP entity, which in turn sends LL-XID.ind to its SNDPCP user entity. Simultaneously, the Receiver's LLC entity sends LL-XID.ind to its SNDPCP entity, which sends LL-XID.ind to its SNDPCP user entity.](34b047489058d6400b412cd0ae2334ba_img.jpg) + +Figure 12: LLC XID negotiation procedure. This sequence diagram shows the interaction between an Originator and a Receiver. The Originator contains SNDPCP user, SNDPCP, and LLC entities. The Receiver contains LLC, SNDPCP, and SNDPCP user entities. The sequence starts with an XID message from the LLC entity on the Originator side to the LLC entity on the Receiver side. The Receiver's LLC entity responds with an XID message back to the Originator's LLC entity. The Originator's LLC entity then sends LL-XID.ind to its SNDPCP entity, which in turn sends LL-XID.ind to its SNDPCP user entity. Simultaneously, the Receiver's LLC entity sends LL-XID.ind to its SNDPCP entity, which sends LL-XID.ind to its SNDPCP user entity. + +Figure 12: LLC XID negotiation procedure + +### 6.8.1 Negotiation of compression entities + +For parameter type 1 and 2, multiple compression fields (as shown in figure 7 and figure 9) may be specified. Each compression field corresponds to a compression entity. + +In each compression field, the "Applicable NSAPIs" parameter indicates the NSAPIs that uses the compression entity. The parameter, if included, shall consist of 2 octets. Multiple NSAPIs may share the same compression entity by setting multiple bits in the parameter. NSAPIs requiring acknowledged peer-to-peer LLC operation and unacknowledged peer-to-peer LLC operation shall not share the same compressor (see subclause 6.10). + +During SNDPCP XID negotiation or re-negotiation, if a parameter type is specified in the SNDPCP XID block, compression entities currently in use and compression entities proposed to be added may be included in the SNDPCP XID block. Not all entities need to be included in the SNDPCP XID block. If a compression entity is not included, the value of its parameters shall be determined by the rules defined in subclause 6.8.2. + +If, implicitly or explicitly (see subclause 6.8.2), a compression entity is specified in the responding SNDPCP XID block with one or more bits set to 1 in the "Applicable NSAPIs" parameter, the compression entity shall be created (if it does not exist yet). + +If, implicitly or explicitly, a compression entity is specified in the responding SNDPCP XID block with no bit set to 1 in the "Applicable NSAPIs" parameter, the compression entity shall be deleted (if it currently exists). + +If an SNDPCP entity receives a proposal for a compression entity containing an unknown algorithm, it shall reject this compression entity explicitly by setting the bits in the "Applicable NSAPIs" parameter in the responding SNDPCP XID block to 0. + +NOTE: Some legacy MS implementations of SDNCP version 0 will ignore a proposed compression entity containing an unknown algorithm and will not reply with an explicit rejection. + +If, implicitly or explicitly, one or more bits are set to 1 in the "Applicable NSAPIs" parameter of a compression entity in the responding SNDPCP XID block, the NSAPIs corresponding to these bits shall start using (or continue to use) the compression entity. + +If, implicitly or explicitly, one or more bits are set to 0 in the "Applicable NSAPIs" parameter of a compression entity in the responding SNDPCP XID block, the NSAPIs corresponding to these bits shall release the compression entity (if they have been using the compression entity). + +#### 6.8.1a Negotiation of SNDPCP version + +An SNDPCP entity supporting this version of SNDPCP shall set the version number in the originating SNDPCP XID block to 1. For the sense of negotiation of the version number see clause 8, table 8. + +### 6.8.2 Values of SNDPCP XID parameters + +In this subclause, the term "parameter" refers to an SNDPCP XID parameter, a compression field (for parameter type 1 or 2), or a parameter for a compression field. + +If an SNDPCP XID parameter has not been negotiated, default values shall apply. The default value for a compression field (entity) is "non-existing". + +If the originating SNDPCP XID block does not include a parameter (implicit command), it shall be treated as equivalent to requesting for the current value for the parameter. The responder may explicitly include this parameter in its response. If the responder explicitly includes the parameter in the response, then it shall also explicitly include this parameter in every SNDPCP XID response until the parameter has been explicitly negotiated, either by responding to an SNDPCP XID command that included the parameter, or by explicitly including the parameter the next time an SNDPCP XID command is transmitted. + +If a parameter is included in the originating SNDPCP XID block and the responder does not include the parameter in its response (implicit response), it shall be treated as equivalent to responding with the value proposed by the originator. + +If both the originator and the responder do not include a parameter in the negotiation, the value of the parameter is not changed. + +### 6.8.3 Exception handling + +In this subclause, the term "parameter" may refer, wherever applicable, to an SNDPCP XID parameter, a compression field (for parameter type 1 or 2), or a parameter for a compression field. + +If the originating SNDPCP XID block includes an SNDPCP XID parameter with unrecognised Parameter Type field (as specified in clause 8, table 8), the parameter shall be ignored by the responder. + +If the originating SNDPCP XID block includes a parameter with unsupported length or an out-of-range value, then the responder shall respond to the parameter with lengths and values set according to the responder's preference. + +If the originating SNDPCP XID block includes parameter type 1 or 2 which violates the rules in subclause 6.8.1, the responder shall treat the parameter as not transmitted by the originator, and responds according to subclause 6.8.2. + +If the originating SNDPCP XID block includes a parameter with duplicated instances, the subsequent instances of the duplicated parameter shall be ignored. + +If the originating SNDPCP XID block is sent on LL-XID primitives and contains prohibited changes (see subclauses 6.5.1.2 and 6.6.1.2) to the parameters of compression entities used with acknowledged peer-to-peer LLC operation, then the responder shall respond with these parameters set to their previously-negotiated values. + +In the originating SNDPCP XID block, excluding the collision scenarios described in subclause 6.5.1.1.3, when an assigned entity number is included with the P bit set to 1, the algorithm and the PCOMP and DCOMP fields shall be ignored if they are the same as the previously-assigned values. If the algorithm and PCOMP or DCOMP fields are not the same as the previously-assigned values, then the Applicable NSAPIs field of the compression field in question shall be set to 0 in the response, and an SNSM-STATUS.request primitive with Cause "invalid XID command" shall be sent to the SM sub-layer. SM shall then deactivate all PDP contexts for this SAPI. + +In the originating SNDCP XID block, if an unassigned entity number is included with the P bit set to 0, then the Applicable NSAPIs field in the response shall be set to 0. + +In the originating SNDCP XID block, excluding the collision scenarios described in subclause 6.5.1.1.3, if one or more of the PCOMP or DCOMP specified is already assigned to a different compression algorithm, then the Applicable NSAPIs field of the compression field in question shall be set to 0 in the response, and an SNSM-STATUS.request primitive with Cause "invalid XID command" shall be sent to the SM sub-layer. SM shall then deactivate all PDP contexts for this SAPI. + +In the originating SNDCP XID block, if one or more new PCOMP or DCOMP values are specified for an existing compression algorithm, then the Applicable NSAPIs field of the compression field in question shall be set to 0 in the response, and an SNSM-STATUS.request primitive with Cause "invalid XID command" shall be sent to the SM sub-layer. SM shall then deactivate all PDP contexts for this SAPI. + +If the responding SNDCP XID block includes an SNDCP XID parameter with unrecognised Parameter Type field (see clause 8, table 8), unsupported length, an out-of-range value or a value violating the sense of negotiation, a parameter type 1 or 2 which violates the rules in subclause 6.8.1, a parameter with duplicated instances, contains prohibited changes (see subclauses 6.5.1.2 and 6.6.1.2) to the parameters of compression entities used with acknowledged peer-to-peer LLC operation when the SNDCP XID block is sent on LL-XID primitives, or a compression field with the P bit set to 1, then the originator shall ignore the block and reinitiate the negotiation. If the renegotiation fails for an implementation-specific number of times, the originating SNDCP layer shall send an SNSM-STATUS.request primitive with Cause "invalid XID response" to the SM sub-layer. SM shall then deactivate all PDP contexts for this SAPI. + +If the LLC layer indicates that the XID parameter negotiation failed, by sending an LL-RELEASE.indication with Cause "no peer response" or an LL-STATUS.indication with Cause "no peer response", then, as an implementation option, the SNDCP layer may wait for an implementation-specific amount of time and re-invoke the XID negotiation procedure. + +## 6.9 Data transfer + +### 6.9.1 Acknowledged mode + +The SNDCP entity shall initiate acknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated and if acknowledged LLC operation has been established. + +The N-PDU number in acknowledged mode is a number assigned to each N-PDU received by SNDCP through an SN-DATA.request and to each feedback N-PDU generated by a local compression entity. N-PDU numbers for different NSAPIs shall be assigned independently. The N-PDU number shall be included in the SNDCP header of the first segment of an N-PDU. + +NOTE: A feedback N-PDU can be e.g. a context state packet generated by a protocol control information compression entity using RFC 2507 [10] or a standalone feedback packet generated by a protocol control information compression entity using RFC 5795 [12]. + +Two variables, the Send N-PDU number and the Receive N-PDU number, shall be maintained for each NSAPI using acknowledged peer-to-peer LLC operation. When an NSAPI using acknowledged peer-to-peer LLC operation is activated, the Send N-PDU number and the Receive N-PDU number shall be set to 0. The Send N-PDU number and Receive N-PDU number shall also be set as described in subclause 5.1.2.22. Modulo 256 operation shall be applied to the Send N-PDU number and the Receive N-PDU number. + +Upon reception of an SN-DATA.request, the SNDCP entity shall assign to the N-PDU received the current value of the Send N-PDU number as the N-PDU number, increment the Send N-PDU number by 1, perform the compression and segmentation functions, then forward the SN-PDU(s) in LL-DATA.request to the LLC layer. If an N-PDU number is already present in the SN-DATA.request, then no new N-PDU number shall be assigned to the N-PDU, and the Send N-PDU number shall not be incremented. The N-PDU shall be stored into a buffer in the SNDCP entity. The buffered N-PDU shall be deleted when the SN-DATA PDU carrying the last segment of the N-PDU is confirmed by an LL-DATA.confirm primitive, or when the entire N-PDU is confirmed by an SNSM-SEQUENCE.indication primitive. + +Upon reception of a feedback N-PDU generated by a local compression entity, the SNDCP entity shall assign to the feedback N-PDU the current value of the Send N-PDU number as the N-PDU number, increment the Send N-PDU number by 1, perform segmentation functions if required, then forward the SN-PDU(s) in LL-DATA.request to the LLC layer. + +During normal operation (i.e. not in the recovery state), when the peer SNDPCP entity receives the SN-PDU(s) in an LL-DATA.indication primitive, the SNDPCP entity shall reassemble and decompress the SN-PDU(s), increment the Receive N-PDU number by 1, and, if the decompression is successful, forward the N-PDU to the SNDPCP user with the SN-DATA.indication. The correct SNDPCP user is identified by the NSAPI field in the SN-PDU(s). + +In the recovery state, after reassembling and decompressing the SN-PDU(s): + +- if the N-PDU number of the received N-PDU is equal to the Receive N-PDU number, then the Receive N-PDU number shall be incremented by 1, the recovery state shall be exited and normal operation shall resume for the received N-PDU and all subsequently-received N-PDUs; and +- otherwise, the N-PDU shall be discarded. + +After the SNDPCP entity in the SGSN receives an SNSM-STOP-ASSIGN.indication primitive for an NSAPI using acknowledged peer-to-peer LLC operation, it shall stop assigning N-PDU number to N-PDUs received through the SN-DATA.request primitive. + +If an SN-DATA PDU (T bit set to 0) is received by an NSAPI that does not use acknowledged mode, the PDU shall be ignored without error notification. + +![Sequence diagram illustrating SNDPCP acknowledged data transfer between an Originator and a Receiver.](09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg) + +``` + +sequenceDiagram + participant Originator + participant Receiver + Note left of Originator: Originator components: SNDPCP user, SNDPCP, LLC + Note right of Receiver: Receiver components: LLC, SNDPCP, SNDPCP user + Originator->>Receiver: SN-DATA.req + Note left of Originator: SNDPCP + Originator->>Receiver: LL-DATA.req + Note right of Receiver: LLC + Receiver->>Originator: Acknowledgement + Note right of Receiver: SNDPCP + Receiver->>Originator: LL-DATA.cnf + Note left of Originator: LLC + Note right of Receiver: SNDPCP user + Receiver->>Receiver: SN-DATA.ind + +``` + +The diagram shows the interaction for acknowledged data transfer. On the Originator side, the SNDPCP user sends an SN-DATA.req to the SNDPCP entity, which then sends an LL-DATA.req to the LLC entity. The LLC entity transmits the data to the Receiver's LLC entity. The Receiver's LLC entity sends an Acknowledgement back to the Originator's LLC entity, which then sends an LL-DATA.cnf to the Originator's SNDPCP entity. Finally, the Receiver's LLC entity sends an LL-DATA.ind to the Receiver's SNDPCP entity, which then sends an SN-DATA.ind to the Receiver's SNDPCP user. + +Sequence diagram illustrating SNDPCP acknowledged data transfer between an Originator and a Receiver. + +**Figure 13: SNDPCP acknowledged data transfer** + +### 6.9.2 Unacknowledged mode + +The SNDPCP entity shall initiate unacknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated. The SNDPCP entity may initiate unacknowledged data transmission even if the acknowledged peer-to-peer operation is not established for that NSAPI. + +The N-PDU number in unacknowledged mode is a number assigned to each N-PDU received by SNDPCP through an SN-UNITDATA.request and to each feedback N-PDU generated by a local compression entity. N-PDU numbers for different NSAPIs shall be assigned independently. The N-PDU number shall be included in the SNDPCP header of every SN-UNITDATA PDU. + +**NOTE:** A feedback N-PDU can be e.g. a context state packet generated by a protocol control information compression entity using RFC 2507 [10] or a standalone feedback packet generated by a protocol control information compression entity using RFC 5795 [12]. + +A variable, the Send N-PDU number (unacknowledged), shall be maintained for each NSAPI using unacknowledged peer-to-peer LLC operation. When an NSAPI using unacknowledged peer-to-peer LLC operation is activated, the Send N-PDU number (unacknowledged) shall be set to 0. The Send N-PDU number (unacknowledged) shall also be set as described in subclauses 5.1.2.1 and 5.1.2.22. Modulo 4096 operation shall be applied to the Send N-PDU number (unacknowledged). + +Upon reception of an SN-UNITDATA.request, the SNDPCP entity shall assign the current value of the Send N-PDU number (unacknowledged) as the N-PDU number of the N-PDU received, increment Send N-PDU number (unacknowledged) by 1, compress and segment the information, then forward the SN-PDU(s) in LL-UNITDATA.request to the LLC layer. The N-PDU shall be deleted immediately after the data has been delivered to the LLC layer. + +Upon reception of a feedback N-PDU generated by a local compression entity, the SNDCP entity shall assign the current value of the Send N-PDU number (unacknowledged) as the N-PDU number of the feedback N-PDU, increment the Send N-PDU number (unacknowledged) by 1, perform segmentation functions if required, then forward the SN-PDU(s) in LL-UNITDATA.request to the LLC layer. The N-PDU shall be deleted immediately after the data has been delivered to the LLC layer. + +When the peer SNDCP entity receives the SN-PDU(s) in the LL-UNITDATA.indication primitive, the SNDCP entity shall reassemble and decompress the SN-PDU(s), then forwards the N-PDU to the SNDCP user with the SN-UNITDATA.indication. The correct SNDCP user is identified by the NSAPI field in the SN-PDU(s). + +If an SN-UNITDATA PDU (T bit set to 1) is received by an NSAPI that does not use unacknowledged mode, the PDU shall be ignored without error notification. + +The SNDCP entity shall detect lost SN-PDUs. The SNDCP entity shall discard duplicate SN-PDUs and re-order out-of-sequence SN-PDUs, if possible. + +![Sequence diagram illustrating SNDCP unacknowledged data transfer between an Originator and a Receiver.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +``` + +sequenceDiagram + participant SNDCP_user as SNDCP user + participant SNDCP + participant LLC + Note left of SNDCP_user: Originator + SNDCP_user->>SNDCP: SN-UNITDATA.req + SNDCP->>LLC: LL-UNITDATA.req + LLC->>LLC: + Note right of LLC: Receiver + LLC->>SNDCP: LL-UNITDATA.ind + SNDCP->>SNDCP_user: SN-UNITDATA.ind + +``` + +The diagram shows the interaction between an Originator and a Receiver for unacknowledged data transfer. On the Originator side, the SNDCP user sends an SN-UNITDATA.req to the SNDCP entity, which then sends an LL-UNITDATA.req to the LLC entity. The LLC entity then transmits the data to the Receiver's LLC entity. On the Receiver side, the LLC entity sends an LL-UNITDATA.ind to the SNDCP entity, which finally sends an SN-UNITDATA.ind to the SNDCP user. + +Sequence diagram illustrating SNDCP unacknowledged data transfer between an Originator and a Receiver. + +**Figure 14: SNDCP unacknowledged data transfer** + +## 6.10 Possible combinations of SNDCP protocol functions and their connection to service access points + +The following combinations of SNDCP protocol functions are allowed: + +- One or several NSAPIs may use one SAPI. +- Only one SAPI shall be used by one NSAPI. +- One or several NSAPIs may use the same protocol control information compression entity. +- One NSAPI may use zero or one protocol control information compression entities. +- One or several NSAPIs may use the same data compression entity. +- One NSAPI may use zero or one data compression entities. +- Separate data compression entities shall be used for SN-DATA and SN-UNITDATA PDUs. +- Separate protocol control information compression entities shall be used for SN-DATA and SN-UNITDATA PDUs. +- One data compression entity shall be connected to one SAPI. +- One protocol control information compression entity shall be connected to one SAPI. +- One or several protocol control information compression entities may be connected to the same data compression entity. +- One protocol control information compression entity shall be connected to zero, one, or several data compression entities. + +# 7 Definition of SN-PDU + +## 7.1 Format convention + +### 7.1.1 Numbering convention + +The convention used in the present document is illustrated in figure 15. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to N. + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------|---|---|---|---|---|---|---|---| +| Oct 1 | | | | | | | | | +| 2 | | | | | | | | | +| ... | | | | | | | | | +| N-1 | | | | | | | | | +| N | | | | | | | | | + +**Figure 15: Format convention** + +### 7.1.2 Order of transmission + +SN-PDUs are transferred between the SNDPC layer and LLC layer in units of octets, in ascending numerical octet order (i.e. octet 1, 2, ..., N-1, N). The order of bit transmission is specific to the underlying protocols used across the Um interface and the Gb interface. + +### 7.1.3 Field mapping convention + +When a field is contained within a single octet, the lowest bit number of the field represents the lowest order value. When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of the field contained in a given octet the lowest bit number represents the lowest order value. + +For example, a bit number can be identified as a couple (o, b) where o is the octet number and b is the relative bit number within the octet. Figure 16 illustrates a field that spans from bit (1, 3) to bit (2, 7). The high order bit of the field is mapped on bit (1, 3) and the low order bit is mapped on bit (2, 7). + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|-------|-------|---|---|---|-------|-------|-------| +| 1st octet of field | | | | | | $2^4$ | $2^3$ | $2^2$ | +| 2nd octet of field | $2^1$ | $2^0$ | | | | | | | + +**Figure 16: Field mapping convention** + +Figure 17 illustrates an NSAPI field that spans from bit (1,8) to bit (2,1). NSAPI 15 is mapped to bit (1,8) and the other NSAPIs are mapped in decreasing order until NSAPI 0 that is mapped to bit (2,1). A bit set to 0 means that the compression entity is not applicable to the corresponding NSAPI. A bit set to 1 means that the compression entity is applicable to the corresponding NSAPI. + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|----|----|----|----|----|----|---|---| +| 1st octet of field | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | +| 2nd octet of field | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | + +**Figure 17: NSAPI mapping convention** + +## 7.2 SN-PDU Formats + +Each SN-PDU shall contain an integral number of octets, and shall comprise a header part and a data part. An SN-PDU shall contain data from a single N-PDU only. Two different SN-PDU formats are defined. The SN-DATA PDU shall be used for acknowledged data transfer and SN-UNITDATA PDU for unacknowledged data transfer. + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|-------|----------------------------------|---|---|---|-------|---|---|---|--|--|--|--| +| Oct 1 | X | F | T | M | NSAPI | | | | | | | | +| 2 | DCOMP | | | | PCOMP | | | | | | | | +| 3 | N-PDU number - acknowledged mode | | | | | | | | | | | | +| ... | Data segment | | | | | | | | | | | | +| N | | | | | | | | | | | | | + +Figure 18: SN-DATA PDU format + +| Bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|-------|------------------------------------------------|---|---|---|------------------------------------|---|---|---|--|--|--|--| +| Oct 1 | X | F | T | M | NSAPI | | | | | | | | +| 2 | DCOMP | | | | PCOMP | | | | | | | | +| 3 | Segment number | | | | N-PDU number - unacknowledged mode | | | | | | | | +| 4 | N-PDU number - unacknowledged mode (continued) | | | | | | | | | | | | +| ... | Data segment | | | | | | | | | | | | +| N | | | | | | | | | | | | | + +Figure 19: SN-UNITDATA PDU format + +### More bit (M): + +- 0 Last segment of N-PDU. +- 1 Not the last segment of N-PDU, more segments to follow. + +### SN-PDU Type (T): + +- 0 SN-DATA PDU. +- 1 SN-UNITDATA PDU. + +### First segment indicator bit (F): + +- 0 This SN-PDU is not the first segment of an N-PDU. + +The octet including DCOMP and PCOMP is not included in the SN-DATA PDU or SN-UNITDATA PDU format. Also the octet for N-PDU number for acknowledged mode is not included in the SN-DATA PDU format. + +- 1 This SN-PDU is the first segment of an N-PDU. The octet for DCOMP and PCOMP is included in the SN-DATA PDU or SN-UNITDATA PDU format. Also the octet for N-PDU number for acknowledged mode is included in the SN-DATA PDU format. + +### Spare bit (X): + +- 0 Shall be set to 0 by the transmitting SNDPCP entity and ignored by the receiving SNDPCP entity. + +### **NSAPI:** + +- 0 Escape mechanism for future extensions. +- 1 Point-to-Multipoint Multicast (PTM-M) information for Multimedia Broadcast/Multicast Service (MBMS). +- 2-4 Reserved for future use. +- 5-15 Dynamically allocated NSAPI value (see subclause 6.1). + +The SGSN shall ignore any uplink data traffic of SN-PDUs with an NSAPI = 1. + +SN-PDU with an unallocated NSAPI value shall be ignored by the receiving SNDCP entity without error notification. + +### **Data compression coding (DCOMP):** + +- 0 No compression. +- 1-14 Points to the data compression identifier negotiated dynamically (see subclause 6.6). +- 15 Reserved for future extensions. + +SN-PDU with an unallocated DCOMP value shall be ignored by the receiving SNDCP entity without error notification. + +### **Protocol control information compression coding (PCOMP):** + +- 0 No compression. +- 1-14 Points to the protocol control information compression identifier negotiated dynamically (see subclause 6.5). +- 15 Reserved for future extensions. + +SN-PDU with an unallocated PCOMP value shall be ignored by the receiving SNDCP entity without error notification. + +### **Segment number:** + +- 0-15 Sequence number for segments carrying an N-PDU. + +### **N-PDU number - acknowledged mode:** + +- 0-255 N-PDU number of the N-PDU. + +### **N-PDU number - unacknowledged mode:** + +- 0-4095 N-PDU number of the N-PDU. + +# 8 SNDCP XID parameters + +The SNDCP XID parameters are shown in table 8: + +**Table 8: SNDCP XID parameters** + +| Parameter name | Parameter Type | Length | Format | Range | Default value | Units | Sense of negotiation | +|------------------------------------------|----------------|----------|---------------------|-------|---------------|-------|----------------------| +| Version number | 0 | 1 | 0000bbbb | 0-15 | 0 | - | down | +| Data Compression | 1 | variable | See subclause 6.6.1 | | | | | +| Protocol Control Information Compression | 2 | variable | See subclause 6.5.1 | | | | | + +NOTE: The current version of SNDCP is 1. The default value for the version number is 0. + +# --- Annex A (informative): Change History + +| SMG# | CR# | REV. | NEW REV. | SUBJECT | +|--------|-----|------|----------|-------------------------------------------------------| +| SMG#31 | | | 8.0.0 | Creation of the specification for R99 based on V7.3.0 | +| | | | | | + +| TSG Meeting | TSG Doc number | TSG WG doc number | Spec | CR | R v | Ph | C at | Vers Old | Vers New | Subject | Work item | Remarks | +|-------------|----------------|-------------------|--------|------|-----|-------|------|----------|----------|---------------------------------------------------------------------------------------------------------------|-----------|----------------------------------------------------------| +| NP-09 | | | | | | | | 8.0.0 | 8.1.0 | | | GSM to 3GPP format is changed | +| NP-09 | NP-000441 | N1-001019 | 04.65 | A070 | 1 | R99 | F | 8.0.0 | 8.1.0 | Deletion of PDP type X.25 | GPRS | GSM to 3GPP format is changed | +| NP-09 | NP-000441 | N1-001025 | 04.65 | A071 | 1 | R99 | F | 8.0.0 | 8.1.0 | Supporting RFC2507 Header Compression in SNDPCP | GPRS | | +| NP-10 | | | | | | | | 8.1.0 | 4.0.0 | | | This CR changes the specification to Release 4 as 44.065 | +| NP-10 | NP-000675 | N1-001178 | 04.65 | A072 | | Rel-4 | C | 8.1.0 | 4.0.0 | Support of V.44 Data Compression in SNDPCP | TEI4 | | +| NP-13 | NP-010492 | N1-011200 | 44.065 | 001 | | Rel-4 | A | 4.0.0 | 4.1.0 | Conditions for header compression | GPRS | | +| NP-16 | | | 44.065 | | | Rel-5 | | 4.1.0 | 5.0.0 | CN plenary decision to make this TS also for Release 5. Some editorials from ETSI secretariat are introduced. | | June 2002 | +| NP-20 | NP-030284 | N1-030934 | 44.065 | 004 | 4 | Rel-6 | B | 5.0.0 | 6.0.0 | Additional support of ROHC in SNDPCP | TEI6 | June 2003 | +| NP-20 | NP-030284 | N1-030833 | 44.065 | 005 | 1 | Rel-6 | C | 5.0.0 | 6.0.0 | Multiple header compression algorithms handling | TEI6 | June 2003 | +| NP-21 | NP-030416 | N1-031074 | 44.065 | 007 | | Rel-6 | A | 6.0.0 | 6.1.0 | Correction to References | TEI5 | Sept 2003 | +| NP-21 | NP-030420 | N1-031283 | 44.065 | 008 | 1 | Rel-6 | F | 6.0.0 | 6.1.0 | Corrections on Compression details | TEI6 | Sept 2003 | +| NP-22 | NP-030486 | N1-031652 | 44.065 | 012 | 1 | Rel-6 | F | 6.1.0 | 6.2.0 | Disabling of ROHC segmentation | TEI6 | December 2003 | +| NP-22 | NP-030486 | N1-031650 | 44.065 | 013 | 1 | Rel-6 | F | 6.1.0 | 6.2.0 | XID negotiation for IP compression | TEI6 | December 2003 | +| NP-25 | NP-040387 | N1-041408 | 44.065 | 014 | | Rel-6 | B | 6.2.0 | 6.3.0 | Update of SNDPCP - MBMS | MBMS | Sept 2004 | +| NP-25 | NP-040374 | N1-041636 | 44.065 | 017 | 2 | Rel-6 | A | 6.2.0 | 6.3.0 | Negotiation of compression entities with unknown algorithm type | TEI4 | Sept 2004 | +| CP-28 | CP-050062 | C1-050787 | 44.065 | 21 | 2 | Rel-6 | B | 6.3.0 | 6.4.0 | Pre-defined Protocol control information compression types for MBMS | MBMS | June 2005 | +| CP-29 | CP-050356 | C1-051205 | 44.065 | 025 | 4 | Rel-6 | F | 6.4.0 | 6.5.0 | Recommendation for FOHC context when used for MBMS ROHC | MBMS | Sept 2005 | +| CP-29 | CP-050356 | C1-050862 | 44.065 | 026 | | Rel-6 | F | 6.4.0 | 6.5.0 | MAX_HEADER is not used by ROHC as per RFC 3095 | MBMS | Sept 2005 | +| CP-29 | CP-050449 | C1-050921 | 44.065 | 027 | 2 | Rel-6 | B | 6.4.0 | 6.5.0 | Modifications for PS HO in A/Gb mode | SPSH AGB | Sept 2005 | +| CP-32 | CP-060267 | C1-060958 | 44.065 | 0030 | 1 | Rel-6 | F | 6.5.0 | 6.6.0 | Handling of feedback N-PDU | TEI6 | June 2006 | +| CP-32 | CP-060268 | C1-061035 | 44.065 | 0032 | 1 | Rel-6 | F | 6.5.0 | 6.6.0 | Correction of the XID parameter negotiation sub-clause for LL-UNITDATA | SCSA GB | June 2006 | + +| TSG Meeting | TSG Doc number | TSG WG doc number | Spec | CR | Rev | Ph | Cat | Vers Old | Vers New | Subject | Work item | Remarks | +|-------------|----------------|-------------------|--------|------|-----|--------|-----|----------|----------|--------------------------------|-----------|------------| +| CP-33 | CP-060506 | C1-061624 | 44.065 | 0034 | | Rel-7 | F | 6.6.0 | 7.0.0 | Clean-up for ROHC segmentation | TEI7 | Sept 2006 | +| CP-42 | | | | | | Rel-8 | | 7.0.0 | 8.0.0 | Upgrade to Rel-8 | | Dec 2008 | +| CP-46 | | | | | | Rel-9 | | 8.0.0 | 9.0.0 | Upgrade to Rel-9 | | Dec 2009 | +| CP-51 | | | | | | Rel-10 | | 9.0.0 | 10.0.0 | Upgrade to Rel-10 | | March 2011 | +| CP-57 | | | | | | Rel-11 | | 10.0.0 | 11.0.0 | Upgrade to Rel-11 | | Sept 2012 | +| CP-65 | | | | | | Rel-12 | | 11.0.0 | 12.0.0 | Upgrade to Rel-12 | | Sept 2014 | +| CP-70 | | | | | | Rel-13 | | 12.0.0 | 13.0.0 | Upgrade to Rel-13 | | Dec 2015 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | CT#73 | CP-160491 | 0035 | | F | Modification of N201-U due to the introduction of Integrity protection | 13.1.0 | +| 2016-11 | | | | | | Correction of typo in the change history | 13.1.1 | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2017-09 | CT#77 | CP-172114 | 0037 | | F | Update to ROHC RFCs | 14.1.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88e | | | | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44068/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/44_series/44068/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6f37e2c2f0f1f07acda12f914b16ca222ca7fe4 --- /dev/null +++ b/marked/Rel-16/44_series/44068/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:475f690d0c3dbc41cc799ce134d441af90417e399a5d8e09fc13eabe24f57e4e +size 174660 diff --git a/marked/Rel-16/44_series/44068/raw.md b/marked/Rel-16/44_series/44068/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a856edca8e72dfc2684ba13b31cbb252cfc8b0b0 --- /dev/null +++ b/marked/Rel-16/44_series/44068/raw.md @@ -0,0 +1,1294 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 Applicability..... | 7 | +| 5 Main concepts ..... | 7 | +| 6 Elementary procedures for Group Call Control ..... | 8 | +| 6.1 Overview ..... | 8 | +| 6.1.1 General ..... | 8 | +| 6.1.2 Group call control states..... | 10 | +| 6.1.2.1 Group call control states at the MS side of the interface ..... | 10 | +| 6.1.2.1.1 Attributes and parameters of GCC in the MS ..... | 10 | +| 6.1.2.1.2 NULL (U0)..... | 10 | +| 6.1.2.1.3 MM CONNECTION PENDING (U0.p)..... | 10 | +| 6.1.2.1.4 GROUP CALL INITIATED (U1) ..... | 10 | +| 6.1.2.1.5 GROUP CALL ACTIVE (U2)..... | 11 | +| 6.1.2.1.6 GROUP CALL PRESENT (U3)..... | 11 | +| 6.1.2.1.7 GROUP CALL CONNECTION REQUESTED (U4) ..... | 11 | +| 6.1.2.1.8 TERMINATION REQUESTED (U5) ..... | 11 | +| 6.1.2.1.9 Sub-states of the Group call active state ..... | 11 | +| 6.1.2.1.10 GCC Timers in the MS..... | 12 | +| 6.1.2.1.11 Consistency of parameters and states..... | 12 | +| 6.1.2.2 Group call control states at the network side of the interface..... | 13 | +| 6.1.2.2.1 NULL (State N0)..... | 13 | +| 6.1.2.2.2 GROUP CALL INITIATED (N1) ..... | 13 | +| 6.1.2.2.3 GROUP CALL ACTIVE (N2)..... | 13 | +| 6.1.2.2.4 GROUP CALL ESTABLISHMENT PROCEEDING (N3) ..... | 13 | +| 6.1.2.2.5 TERMINATION REQUESTED (N4) ..... | 13 | +| 6.2 Procedures for establishment of a group call ..... | 13 | +| 6.2.1 Activation of a group call by the network ..... | 13 | +| 6.2.2 Mobile originated establishment ..... | 13 | +| 6.2.2.1 Termination during mobile originated establishment..... | 14 | +| 6.2.2.2 Abnormal cases..... | 15 | +| 6.2.3 Mobile terminating group call establishment in the MS ..... | 15 | +| 6.3 Procedures during the active state of a group call..... | 15 | +| 6.3.1 Mobile station procedures in the active state..... | 15 | +| 6.3.1.1 Sub-state transitions in the MS ..... | 15 | +| 6.3.2 Network procedures in the active state..... | 16 | +| 6.4 Procedures for release, abortion, and termination of a group call..... | 16 | +| 6.4.1 Termination procedure ..... | 16 | +| 6.4.2 Abort and release procedures ..... | 17 | +| 6.5 Miscellaneous procedures ..... | 17 | +| 6.5.1 Status procedures..... | 17 | +| 6.5.1.1 Get status procedure..... | 17 | +| 6.5.1.2 Set parameter procedure ..... | 17 | +| 7 Handling of unknown, unforeseen, and erroneous protocol data ..... | 17 | +| 7.1 General ..... | 17 | +| 7.2 Message too short..... | 18 | +| 7.3 Unknown or unforeseen transaction identifier ..... | 18 | +| 7.4 Unknown or unforeseen message type..... | 18 | +| 7.5 Non-semantical mandatory information element errors..... | 18 | +| 7.6 Unknown and unforeseen information elements in the non-imperative message part ..... | 19 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------| +| 7.6.1 | Information elements unknown in the message ..... | 19 | +| 7.6.2 | Out of sequence information elements ..... | 19 | +| 7.6.3 | Repeated Information elements ..... | 19 | +| 7.7 | Non-imperative message part errors ..... | 19 | +| 7.7.1 | Syntactically incorrect optional Information elements ..... | 19 | +| 7.8 | Messages with semantically incorrect contents ..... | 19 | +| 8 | Message functional definitions and contents ..... | 20 | +| 8.1 | CONNECT ..... | 21 | +| 8.1.1 | SMS indications ..... | 21 | +| 8.2 | GET STATUS ..... | 21 | +| 8.2.1 | mobile identity ..... | 22 | +| 8.3 | IMMEDIATE SETUP ..... | 22 | +| 8.3.1 | Mobile identity ..... | 22 | +| 8.3a | IMMEDIATE SETUP 2 ..... | 23 | +| 8.3a.1 | TMSI ..... | 23 | +| 8.3a.2 | Compressed otdi ..... | 23 | +| 8.4 | SET PARAMETER ..... | 23 | +| 8.5 | SETUP ..... | 24 | +| 8.5.1 | Originator-to-dispatcher information ..... | 24 | +| 8.5.2 | Talker priority requested ..... | 24 | +| 8.6 | STATUS ..... | 24 | +| 8.6.1 | Call state ..... | 25 | +| 8.6.2 | State attributes ..... | 25 | +| 8.7 | TERMINATION ..... | 25 | +| 8.8 | TERMINATION REJECT ..... | 25 | +| 8.9 | TERMINATION REQUEST ..... | 26 | +| 8.9.1 | Talker priority ..... | 26 | +| 9 | Contents of information elements value parts ..... | 26 | +| 9.1 | Protocol Discriminator ..... | 26 | +| 9.2 | Transaction identifier ..... | 26 | +| 9.3 | Message Type ..... | 27 | +| 9.4 | Other information elements ..... | 27 | +| 9.4.1 | Call Reference ..... | 27 | +| 9.4.2 | Call state ..... | 28 | +| 9.4.3 | Cause ..... | 29 | +| 9.4.4 | Originator indication ..... | 30 | +| 9.4.5 | Not used ..... | 31 | +| 9.4.6 | Spare Half Octet ..... | 31 | +| 9.4.7 | State attributes ..... | 31 | +| 9.4.8 | Compressed otdi ..... | 32 | +| 9.4.9 | Talker priority ..... | 32 | +| 9.4.10 | SMS indications ..... | 32 | +| Annex A (informative): | Example of the coding of the user-user information after
decompression of the originator-to-dispatcher information ..... | 34 | +| Annex B (informative): | Change History ..... | 35 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the Group Call Control (GCC) protocol used by the Voice Group Call Service (VGCS) on the radio interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 42.068: "Voice Group Call Service (VGCS); Stage 1". +- [3] 3GPP TS 23.003: "Numbering, addressing and identification". +- [4] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2". +- [5] 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2". +- [6] 3GPP TS 44.006: "Mobile Station - Base Stations System (MS - BSS) Interface; Data Link (DL) Layer Specification". +- [7] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [8] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [9] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document the terms and definitions given in 3GPP TS 42.068 and the following apply: + +**attachment of the user connection:** See 3GPP TS 24.008, subclause 5.2. + +**calling user:** GCC entity in the Mobile Station (MS) initiating or having initiated a group call. + +**clearing the context related to the group call establishment:** all running GCC timers in the relevant GCC entity are stopped, all attributes in the relevant GCC entity are deleted. + +**downlink:** network to mobile station direction. + +**group call:** is used in the same sense as "voice group call". + +**group call channel:** combined uplink/downlink to be allocated in each cell of the group call area for a particular group call. The uplink can be used by the presently talking service subscriber only. All MSs of the listening service subscribers in one cell shall listen to the common downlink. + +**group receive mode:** See 3GPP TS 44.018. + +**originating mobile station:** mobile station initiating or having initiated the group call. + +NOTE 1: In certain situations, a MS assumes to be the originating MS of a group call without actually being the originating MS of that group call. + +NOTE 2: There may be one or none originating MS for a given group call. + +**uplink:** mobile station to network direction. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1a] and the following apply: + +| | | +|-------|---------------------------------------------------------| +| BSS | Base Station System | +| eMLPP | enhanced Multi-Level Precedence and Pre-emption service | +| GCC | Group Call Control | +| | GPRS General Packet Radio Service | +| MS | Mobile Station | +| VGCS | Voice Group Call Service | +| CM | Connection Management | +| TI | Transaction Identifier | + +# --- 4 Applicability + +Support of the group call protocol is optional in the MS and in the network. + +# --- 5 Main concepts + +The present document describes the group call control (GCC) protocol, which is one of the protocols of the Connection Management (CM) sublayer (see 3GPP TS 24.007). + +There is in general more than one MS engaged in a group call. Consequently, there is in general more than one MS with a GCC entity engaged in the same group call, and there is one GCC entity in the network engaged in that group call. + +Under which conditions a GCC message is passed from lower (sub-)layers to the GCC entity is defined in the specifications of the sub-layers. + +The MS shall ignore GCC messages that it receives which were sent in unacknowledged mode and which explicitly specify as destination a mobile identity which is not a mobile identity of the MS. + +Higher layers and the MM sub-layer decide when to accept parallel GCC transactions and when/whether to accept GCC transactions in parallel to other CM transactions. + +The group call may be initiated by a mobile user or by a dispatcher. Specification of a protocol for dispatchers is out of the scope of the present document. Hence, in the scope of the present document, there are: + +- one GCC entity in the network; and +- one or more than one GCC entities in different MSs; + +engaged in a group call, and one or none of the MSs is the originator of the group call (called the originating MS in the present document). Note that, in certain situations, a MS assumes to be the originator of a group call without being the originator. + +The originator of the GCC transaction chooses the Transaction Identifier (TI). A MS not assuming to be the originator of the transaction will choose the transaction identifier received from the network, setting the TI flag to $1+x \bmod 2$ where $x$ is the received TI flag. + +The present document describes the group call control protocol only with regard to two peer entities, one in a MS, the other one in the network. The call control entities are described as communicating finite state machines which exchange messages across the radio interface and communicate internally with other protocol (sub)layers. In particular, the GCC protocol uses the MM and RR sublayer specified in 3GPP TS 24.008 and 3GPP TS 44.018. This description is only normative as far as the consequential externally observable behaviour is concerned. For simplicity, instead of using the terms "GCC entity in the MS" and "GCC entity in the network", the present document often uses the terms "MS" and "network" if no confusion may arise. + +Certain sequences of actions of the two peer entities compose "elementary procedures" which are used as a basis for the description in the present document. These elementary procedures are defined in clause 6. + +The network should apply supervisory functions to verify that the GCC procedures are progressing and if not, take appropriate means to resolve the problems. This, however, is out of the scope of the present document. + +# --- 6 Elementary procedures for Group Call Control + +## 6.1 Overview + +### 6.1.1 General + +The elementary procedures may be grouped into the following classes: + +- group call establishment procedures; +- group call termination procedures; +- call information phase procedures; +- miscellaneous procedures. + +Figure 6.1 gives an overview of the main states and transitions on the MS side. + +![State transition diagram for the group call control protocol on the MS side. The diagram shows seven states: MM Connection pending (0.P), GC initiated (1), Termination requested (5), GC active, Null (0), GC present (3), and GC connection requested (4). Transitions are labeled with messages like EST-REQ, TERM-REQ, ABORT-REQ, and JOIN GC REQ, with conditions like 'if MS assumes to be the originator' or 'if not in RR connected mode'.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MM_Connection_pending_0_P : MM Connection pending 0.P + [*] --> GC_present_3 : GC present 3 + [*] --> GC_connection_requested_4 : GC connection requested 4 + [*] --> Null_0 : Null 0 + + MM_Connection_pending_0_P --> GC_initiated_1 : ?L: EST-CNF + MM_Connection_pending_0_P --> Null_0 : ?H: TERM-REQ, IL: ABORT-REQ, IH: TERM.CNF + MM_Connection_pending_0_P --> GC_present_3 : ?L: SETUP-REQ (g-id, prio), IL: EST-REQ (SETUP) + MM_Connection_pending_0_P --> GC_connection_requested_4 : ?H: JOIN GC REQ + + GC_initiated_1 --> Null_0 : ?H: IMM SETUP REQ (g-id, prio), IL: EST-REQ (IMM SETUP) + GC_initiated_1 --> Termination_requested_5 : ?H: TERM-REQ, IL: DR(TERM-REQ) + GC_initiated_1 --> GC_active : ?L: DI (CONNECT) IH: SETUP-CNF (mode) + + Termination_requested_5 --> Null_0 : ?L: DI (TERMINATION) or ?L: DI (TERM-REQ) or ? Time out, IH: TERM.CNF + Termination_requested_5 --> GC_active : ?H: TERM-REQ*, IL: DR(TERM-REQ) + + GC_active --> Null_0 : ?H: ABORT REQ, IL: ABORT REQ, ?Timeout exp + GC_active --> GC_initiated_1 : ?H: TERM-REQ*, IL: DR(TERM-REQ) + GC_active --> GC_connection_requested_4 : ?L: JOIN GC CNF (mode), IH: JOIN GC CNF (mode) + GC_active --> States_1_2_3_4 : ?L: DI (TERMINATION), IH: TERM-IND, IL: ABORT-REQ** + + GC_present_3 --> Null_0 : ?L: SETUP-IND (g-id, prio), IH: SETUP-IND (g-id, prio) + GC_present_3 --> GC_connection_requested_4 : ?H: ABORT REQ + + GC_connection_requested_4 --> Null_0 : ?H: ABORT REQ, IL: ABORT REQ + +``` + +State transition diagram for the group call control protocol on the MS side. The diagram shows seven states: MM Connection pending (0.P), GC initiated (1), Termination requested (5), GC active, Null (0), GC present (3), and GC connection requested (4). Transitions are labeled with messages like EST-REQ, TERM-REQ, ABORT-REQ, and JOIN GC REQ, with conditions like 'if MS assumes to be the originator' or 'if not in RR connected mode'. + +NOTE 1: \* if MS assumes to be the originator of the group call. + +NOTE 2: \*\* if not in RR connected mode. + +Figure 6.1: Overview group call control protocol/MS side + +### 6.1.2 Group call control states + +#### 6.1.2.1 Group call control states at the MS side of the interface + +The GCC entity of the MS is described as an extended finite state machine. It performs transitions between (main) states, and in main state GROUP CALL ACTIVE (U3) it performs transitions between sub-states. It has certain parameters and attributes, e.g. configuration parameters and behaviour parameters, which it sets and changes based on interaction with higher and lower (sub-)layers and on message exchange with its peer entity. If a configuration parameter is set to a certain value, the MS shall also adapt the configuration accordingly. Behaviour parameters decide on (part of) the behaviour of the GCC entity. When the GCC entity in the MS receives a message, it shall first analyse whether it shall ignore the message, see clauses 5 and 7. + +##### 6.1.2.1.1 Attributes and parameters of GCC in the MS + +For the following behaviour parameters, the description is informative. + +| Parameter | Description | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------| +| ORIG | Depending on the context, the MS assumes to be the originator of the call (ORIG = T) or not to be the originator of the call (ORIG = F). | +| COMM | Depending on the context, the MS assumes that communication with its peer entity is enabled in both directions (COMM = T) or not (COMM = F). | + +For the following configuration parameters the MS shall adapt its configuration according to the parameter value and parameter definition. + +| Parameter | Definition | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D-ATT | D-ATT = T means that the MS attaches the user connection for the group call in the downlink.
D-ATT = F means that the MS does not attach the user connection for the group call in the downlink. | +| U-ATT | U-ATT = T means that the MS attaches the user connection for the group call in the uplink.
U-ATT = F means that the MS does not attach the user connection for the group call in the uplink. | + +##### 6.1.2.1.2 NULL (U0) + +No group call exists for the GCC entity. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.3 MM CONNECTION PENDING (U0.p) + +The GCC entity has requested the explicit establishment of an MM connection. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.4 GROUP CALL INITIATED (U1) + +The GCC entity has requested the peer entity in the network to establish a group call. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = T, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.5 GROUP CALL ACTIVE (U2) + +The group call is established at least in one cell; depending on the sub-state, the MS has attached the user connection in the uplink and/or downlink. The following sub-states exist: + +- separate link (U2sl); +- wait for receive mode (U2wr); +- receive mode (U2r); +- wait for send and receive mode (U2ws); +- send and receive mode (U2sr); +- no channel (U2nc). + +##### 6.1.2.1.6 GROUP CALL PRESENT (U3) + +The MS has received a notification about an ongoing group call. Higher layers are requested to accept or reject the call. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.7 GROUP CALL CONNECTION REQUESTED (U4) + +The MS has received a notification about an ongoing group call. Higher layers have decided to accept the call. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.8 TERMINATION REQUESTED (U5) + +The MS (which assumes to be the originator of the group call) has been in state U1 or U2 and has sent a TERMINATION REQUEST message to the network. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = T, D-ATT = T, U-ATT = T. + +##### 6.1.2.1.9 Sub-states of the Group call active state + +NOTE: Control of the user connection attachment is seen as a group call control function. This is a reason why the sub-states are distinguished. + +###### 6.1.2.1.9.1 separate link (U2sl) + +A dedicated one to one RR connection exists between MS and network. When entering the sub-state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: COMM = T, D-ATT = T, U-ATT = T. + +##### 6.1.2.1.9.2 wait for receive mode (U2wr) + +The MS has asked the network to enter receive mode but a dedicated one-to-one channel is still assigned. When entering the sub-state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: COMM = T, D-ATT = T, U-ATT = F. + +##### 6.1.2.1.9.3 receive mode (U2r) + +The MS uses a group call channel. When entering the sub-state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: COMM = F, D-ATT = T, U-ATT = F. + +##### 6.1.2.1.9.4 wait for send and receive mode (U2ws) + +The MS (which was in U2r or U2wr) has asked for the uplink. When entering the sub-state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: COMM = F, D-ATT = T, U-ATT = T. + +##### 6.1.2.1.9.5 send and receive mode (U2sr) + +The MS has been informed by its peer entity that the uplink is granted. When entering the sub-state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: D-ATT = T, U-ATT = T. The parameter D-ATT may subsequently be set by the network for muting and unmuting purposes. + +##### 6.1.2.1.9.6 no channel (U2nc) + +The GCC entity has been informed that no channel is currently available. Timer $T_{\text{no channel}}$ is running. When entering the sub-state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: COMM = F, D-ATT = T, U-ATT = T. + +##### 6.1.2.1.10 GCC Timers in the MS + +Table 6.1 specifies the timers used in GCC. The denotation of columns is defined as follows: + +timer ::= name of the timer; + +set ::= under which conditions the timer is set (i.e. started); + +stopped ::= under which conditions the timer is stopped; + +running in state(s) ::= in which state(s) the timer may be running; + +action at expiry ::= which actions the GCC entity shall perform at expiry; + +value ::= the duration between setting the timer and expiry of the timer ("s" denotes "second(s)" "xx - yy" means that any value between xx and yy is permitted). + +**Table 6.1: Specification of timers used in GCC** + +| timer | set | stopped | running in state(s) | action at expiry | value | +|-------------------------|--------------------------------------------------------------------------------------------------------|----------------------------------------------------|---------------------|---------------------|---------| +| $T_{\text{no channel}}$ | when entering U2nc | when leaving U2nc | U2nc | see subclause 6.3.1 | 3 s | +| $T_{\text{MM-est}}$ | when entering U0.p using the set-up procedure
when entering U1 using the immediate set-up procedure | when leaving U0.p or U1 | U0.p, U1 | see subclause 6.2.1 | 7 s | +| $T_{\text{term}}$ | when sending a TERMINATION REQUEST | when receiving a TERMINATION or TERMINATION REJECT | U5 | abort group call | 10 s | +| $T_{\text{conn req}}$ | when entering state U4 | when leaving state U4 | U4 | abort group call | 10-30 s | + +##### 6.1.2.1.11 Consistency of parameters and states + +The MS shall consider the following parameter values as inconsistent with the state or sub-state: + +- ORIG = T is inconsistent with states U3 and U4. +- COMM = T is inconsistent with states U0, U3, U4, and with sub-states U2nc and U2r of state U2. + +All other values of parameters ORIG, COMM, D-ATT, and U-ATT shall not be considered by the MS as inconsistent with a state or sub-state. + +#### 6.1.2.2 Group call control states at the network side of the interface + +##### 6.1.2.2.1 NULL (State N0) + +No group call exists for the GCC entity. + +##### 6.1.2.2.2 GROUP CALL INITIATED (N1) + +The GCC entity has received the indication that a peer entity in a MS wants to establish a group call for a certain group identity or group identity with prefix. + +##### 6.1.2.2.3 GROUP CALL ACTIVE (N2) + +The group call is established in at least one cell; there may be a MS which has seized the uplink or not; there may be talking dispatchers or not. + +##### 6.1.2.2.4 GROUP CALL ESTABLISHMENT PROCEEDING (N3) + +The GCC entity wants to accept the group call, has initiated establishment of corresponding group call channels, and, if there is a calling user, has sent a CONNECT message to the calling user (if there is a calling user). + +##### 6.1.2.2.5 TERMINATION REQUESTED (N4) + +The GCC entity has asked lower sub-layers to terminate the group call in all cells and waits for a confirmation that the group call has been terminated in all cells. + +## 6.2 Procedures for establishment of a group call + +### 6.2.1 Activation of a group call by the network + +The GCC entity in the network may initiate the activation of a group call with a certain group call reference and priority in a list of cells by asking lower layers to establish the group call with that group call reference and priority in those cells. It then waits until it is informed by lower (sub-)layers that resource activation was sufficiently successful, and enters state N2, GC ACTIVE. + +### 6.2.2 Mobile originated establishment + +Higher layers in the MS may ask the GCC entity in state U0, NULL, to establish a group call, either using the immediate set-up procedure or using the set-up procedure. The request contains a group-identity and optionally a prefix for the group identity. The request may also contain a priority indication and a requested talker priority. + +A mobile station supporting the use of talker priorities shall check with the SIM/USIM whether the subscriber is allowed to use the requested talker priority for the respective group identity before signalling the talker priority to the network. If the subscriber is not allowed to use the requested talker priority, the MS shall reduce the talker priority to a value the subscriber is allowed to use. + +On request of higher layers to establish a group call using the set-up procedure, the GCC entity of the MS builds an appropriate SETUP message and asks lower (sub-)layers to establish an MM connection explicitly (i.e. by use of a CM SERVICE REQUEST message) and to transmit the SETUP message. It then enters state U0.p, MM CONNECTION PENDING. In state U0.p, when informed by lower sub-layers that an MM connection has been established, the GCC entity in the MS shall stop timer $T_{MM-est}$ and enter state U1, GC INITIATED. + +On request of higher layers to establish a group call using the immediate set-up procedure, the GCC entity of the MS builds an appropriate IMMEDIATE SETUP message and asks lower (sub-)layers to establish an MM connection implicitly (see 3GPP TS 24.008) and to transmit the IMMEDIATE SETUP message. It sets timer $T_{MM-est}$ and then enters state U1, GC INITIATED. + +The network GCC entity in state NULL may receive a set-up message from its peer entity in the originating MS. This set-up message is either a SETUP message or an IMMEDIATE SETUP message. The network enters state N1, GC INITIATED. + +In state N1, the network decides whether: + +- (a) the establishment is accepted; or +- (b) the establishment rejected; or +- (c) the MS is passed to an existing group call. + +In case (a), the GCC entity in the network considers the peer entity in the MS having sent the set-up message to be the calling user and asks lower layers to activate the appropriate resources. It then: + +- 1) waits until it is informed by lower (sub-)layers that resource activation was sufficiently successful, then sends a CONNECT message to the calling user, and enters state N2, GC ACTIVE; or +- 2) sends a CONNECT message to the calling user and enters N3, GC ESTABLISHMENT PROCEEDING. In state N3, the GCC entity is informed by lower layers whenever the status of resources for the group call is changed. When informed that activation of resources was sufficiently successful, the GCC entity in the network enters state N2, ACTIVE. + +The CONNECT message specifies the group call reference of the group call and indicates that the MS is the originator of the group call. If the network supports the use of talker priorities, it shall also include the talker priority used by the network for the setup of the group call. + +In case b), the further proceeding is as defined in subclause 6.2.2.1. + +In case c), the GCC entity in the network considers the peer entity in the MS having sent the SETUP message not to be the calling user; it may ask lower layers about the status of appropriate resources; it may ask lower layers to modify the resources for the group call. It then: + +- 1) waits until it is informed by lower (sub-)layers that resource modification was sufficiently successful, then sends a CONNECT message to the calling user, and enters state N2, GC ACTIVE; or +- 2) sends a CONNECT message to the calling user and enters N3, GC ESTABLISHMENT PROCEEDING. In state N3, the GCC entity is informed by lower layers whenever the status of resources for the group call is changed. When informed that activation of resources was sufficiently successful, the GCC entity in the network enters state N2, ACTIVE. + +The CONNECT message specifies the group call reference of the group call and indicates that the MS is not the originator of the group call. If the network supports the use of talker priorities, it shall also include the talker priority used by the network. + +In state U0.p or U1, the GCC entity in the MS shall, on receipt of a CONNECT message, establish the conditions defined for state U2, ACTIVE and the suitable sub-state (see subclause 6.1.2.1), stop timer $T_{MM-est}$ (if running) and enter state U2, ACTIVE. If the immediate set-up procedure has been used, the GCC entity in the MS shall inform lower sub-layers that the MM connection has been implicitly established. + +#### 6.2.2.1 Termination during mobile originated establishment + +At any time during the mobile originated establishment of a group call, the network may decide to terminate the connection between the two peer entities in the network and MS. In this case the network sends a TERMINATION message to the MS specifying the appropriate cause; it may ask lower (sub-)layers to release associated resources. The further actions are specified in subclause 6.4. + +During mobile originated establishment of a group call, the MS may abort the group call, see subclause 6.4. + +#### 6.2.2.2 Abnormal cases + +At expiry of $T_{MM-est}$ or radio link failure (see 3GPP TS 44.018), the GCC entity in the MS requests lower sub-layers to abort the MM connection establishment and returns to state U0, NULL (this includes clearing of the context related to the group call establishment). + +On receipt of an indication of lower sub-layers that the MM connection establishment was unsuccessful, the GCC entity in the MS returns to state U0, NULL (this includes clearing of the context related to the group call establishment). + +### 6.2.3 Mobile terminating group call establishment in the MS + +The GCC entity in the MS, being in state U0, NULL, may receive an indication of lower layers that a group call exists. This indication specifies the group identity and group call area identity, a priority, and optionally a talker priority and an emergency mode indication. The GCC entity shall then inform higher layers and enter state U3, GC present. This state may be supervised by a timer at expiry of which the GCC entity clears the context and returns to state U0, NULL. + +In state U3, on request of higher layers to join the group call, the GCC entity in the MS stops any running timer, asks lower sub-layers to join the group call, starts timer $T_{\text{conn req}}$ and enters state U4, GC CONNECTION REQUESTED. + +In state U4, on indication of lower sub-layers that the group call has been joint (his indication specifies the mode of the RR connection), the GCC entity in the MS stops any running timer, enters state U2, ACTIVE and appropriate sub-state, establishes the appropriate configurations (see subclause 6.1) and informs higher layers (this includes information about the sub-state). The MS assumes not to be the originator of the group call (ORIG = F). + +## 6.3 Procedures during the active state of a group call + +### 6.3.1 Mobile station procedures in the active state + +In the active state, the GCC entity in the MS performs, on receipt of messages from its peer entity, on request of higher layers, and on indication of lower sub-layers, sub-state transitions as defined below together with the necessary related actions. + +On request of higher layers, the MS initiates abort or termination of the group call, see subclause 6.4. + +If the network initiates group call abortion or termination, the MS reacts as specified in subclause 6.4. + +On radio link failure, the MS aborts the group call, see subclause 6.4. + +#### 6.3.1.1 Sub-state transitions in the MS + +When in sub-state U2sl or U2s of the GC ACTIVE state (U2), the GCC entity in the MS enters on request of higher layers sub-state U2wr and asks RR to enter RR receive mode. + +When in sub-state U2r or U2wr of the GC ACTIVE state, the GCC entity in the MS enters on request of higher layers sub-state U2ws and asks RR to enter group transmit mode. + +When in the GC ACTIVE state, the GCC entity in the MS may be informed by lower layers that the RR connection mode has changed. It shall then enter the appropriate sub-state and perform appropriate actions as specified below: + +- the appropriate sub-state is derived from the RR mode as specified in table 6.2; +- when no RR connection is available, the GCC entity in the MS starts timer $T_{\text{no channel}}$ and enters sub-state NO CHANNEL. In this sub-state, when $T_{\text{no channel}}$ expires, the GCC entity in the MS informs higher layers, asks lower sub-layers to abort resources and enters the idle state; +- further actions in the MS are defined in subclause of 6.1.2.1. + +**Table 6.2: RR mode** + +| RR mode | U2 sub-state | +|---------------------|--------------| +| Idle | U2nc | +| Group Receive mode | U2r | +| Group transmit mode | U2sr | +| Dedicated mode | U2sl | + +Having entered sub-state U2ws, the MS not considering itself as the originator of the group call (ORIG = F) shall consider the transaction identifier received in the next GCC message from the network to be the TI of the group call. + +### 6.3.2 Network procedures in the active state + +In the active state the GCC entity in the network performs supervisory functions, maintenance functions and resource modifications which are not further specified. (This includes through-connection of the application data stream(s), which is defined in 3GPP TS 43.068). + +The network may initiate abort or termination of the group call, see subclause 6.4. + +If the MS initiates group call abortion or termination, the network reacts as specified in subclause 6.4. + +The network may send a SET PARAMETER message to the MS in order to ask the MS to set parameters to certain values and take consequential actions. + +The GCC entity in the network may be informed by lower (sub-)layers that a MS has requested the uplink. It may accept this request; in this case it should send a SET PARAMETER message to the MS requesting the MS to set parameter COMM to the value T. + +## 6.4 Procedures for release, abortion, and termination of a group call + +### 6.4.1 Termination procedure + +The MS assuming to be the originator of the group call shall, on request of higher layers: + +- if COMM = T, initiate the termination procedure by sending a TERMINATION REQUEST message to its peer entity in the network and setting timer $T_{\text{term}}$ ; +- otherwise, the request is considered to be pending. If the MS is in sub-state U2r, it shall enter sub-state U2ws and ask RR to enter group transmit mode. While the request is pending, the request may be deleted by higher layers. While the request is pending, as soon as COMM = T, the MS shall send a TERMINATION REQUEST message to its peer entity in the network, set timer $T_{\text{term}}$ and no more consider the request as pending. + +The network either accepts the termination by sending a TERMINATION or rejects termination by sending a TERMINATION REJECT. These messages indicate an appropriate cause. + +In state U5, on receipt of a TERMINATION REJECT message, the GCC entity in the MS informs higher layers and stops $T_{\text{term}}$ . + +In state U5, on $T_{\text{term}}$ expiry, the GCC entity in the MS informs higher layers, asks lower sub-layers to abort the group call, clears the context related to the group call, and returns to state U0, NULL. + +In any state, on receipt of a TERMINATION message, the GCC entity in the MS informs higher layers, asks lower sub-layers to release the group call, clears the context related to the group call, and returns to state U0, NULL. + +At any time during a group call, the network may decide to terminate the connection between the two peer entities in the network and MS. In this case the network sends a TERMINATION message to the MS specifying the appropriate cause; it may ask lower (sub-)layers to release associated resources. The further actions are specified above in this subclause 6.4. + +### 6.4.2 Abort and release procedures + +The network may ask lower sub-layers to abort or release the group call. The MS will detect abort of the group call by detecting a radio link failure, and a group call release by release of the RR resources. The GCC entity in the MS shall then inform higher layers, ask lower sub-layers to abort the group call, clear the context related to the group call, and return to state U0, NULL. + +The MS shall, on request of higher layers, initiate the release procedure by asking lower sub-layers to release the group call, clearing the context related to the group call, and returning to state U0, NULL. + +The GCC entity in the MS shall when required by the GCC protocol, abort the group call by requesting lower layers to abort the group call, informing higher layers, clearing the context related to the group call, and returning to state U0, NULL. + +## 6.5 Miscellaneous procedures + +### 6.5.1 Status procedures + +#### 6.5.1.1 Get status procedure + +Upon receipt of a GET STATUS message, the MS shall: + +- if COMM = T, respond with a STATUS message reporting the current call state, the current values of configuration and behaviour parameters and cause value # 30 "Response to GET STATUS"; +- if COMM = F, consider the response to be pending. If the MS is in sub-state U2r, it shall enter sub-state U2ws and ask RR to enter group transmit mode. While the request is pending, as soon as COMM = T, the MS shall send a STATUS message, reporting the current call state, the current values of configuration and behaviour parameters and cause value # 30 "Response to GET STATUS" and no more consider the request as pending. + +#### 6.5.1.2 Set parameter procedure + +Upon receipt of a SET PARAMETER message the MS shall set the parameters to the indicated values and the configuration shall be adapted to the new values of configuration parameters, if they are consistent with the current GCC state and sub-state (see subclause 6.1.2). If they are not: + +- if COMM, before the message was received, is equal to T, it shall send a STATUS message specifying error cause "message incompatible with protocol state", the state and, if applicable, sub-state, and the *state attributes* IE; +- if COMM, before the message was received, is equal to F, it shall ignore the message. + +# --- 7 Handling of unknown, unforeseen, and erroneous protocol data + +## 7.1 General + +This subclause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving GCC protocol entity in the MS. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. Error handling procedures in the network are for further study. + +Subclauses 7.1 to 7.8 shall be applied in order of precedence. + +Most error handling procedures are mandatory for the MS. + +In this clause the following terminology is used: + +- an IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in clause 9, or if its value part violates rules of clause 9. However it is not a syntactical error that a TLV encoded IE specifies in its length indicator a greater length than defined in clause 9; +- a message is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part (i.e. clauses 6 and 7) of the present document. + +## 7.2 Message too short + +When a message is received that is too short to contain a complete message type information element, that message shall be ignored, see 3GPP TS 24.007. + +## 7.3 Unknown or unforeseen transaction identifier + +If COMM = T, the MS shall answer to a message received with TI value "111" by sending a STATUS message with same TI value, cause "invalid transaction identifier value", and including, if possible, as diagnostics the complete + +message received (this may not be possible, e.g. due to length restrictions). If COMM = F, the MS shall ignore a message received with TI value "111". + +For a group call control message received with TI different from "111", the following procedures shall apply. + +Whenever a message is received specifying a transaction identifier which is not recognized as relating to an active transaction, if COMM = F, the MS shall ignore the message; if COMM = T, the MS shall send a STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and including, if possible, as diagnostics the complete message received (this may not be possible, e.g. due to length restrictions). and remain idle. + +## 7.4 Unknown or unforeseen message type + +If the protocol entity in the MS receives a message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message except for the fact that, if COMM = T, it shall return a STATUS message with cause "message type non-existent or not implemented" and including as diagnostics the message type of the message received. + +NOTE: A message type not defined for the PD in the given direction is regarded by the receiver as a message type not defined for the PD, see 3GPP TS 24.007. + +If the protocol entity in the MS receives a message not compatible with the protocol state, the MS shall ignore the message except for the fact that, if COMM = T, it returns a STATUS message with cause "message type not compatible with protocol state" and including as diagnostics the message type of the message received. + +## 7.5 Non-semantical mandatory information element errors + +When on receipt of a message: + +- an "imperative message part" error; or +- a "missing mandatory IE" error; + +is diagnosed or when a message containing: + +- a syntactically incorrect mandatory IE; or +- an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.008, subclause 10.5); or +- an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.008, subclause 10.5); + +is received: + +- the MS shall, if COMM = F, ignore the message. Otherwise it shall proceed as follows: + - the MS shall ignore the message except for the fact that it shall return a STATUS message with cause "invalid mandatory information" and including, if possible, as diagnostics the complete message received (this may not be possible, e.g. due to length restrictions). + +## 7.6 Unknown and unforeseen information elements in the non-imperative message part + +### 7.6.1 Information elements unknown in the message + +The protocol entity in the MS shall ignore all information elements unknown in a message which are not encoded as "comprehension required". + +### 7.6.2 Out of sequence information elements + +The MS shall ignore all out of sequence Information elements in a message which are not encoded as "comprehension required". + +### 7.6.3 Repeated Information elements + +If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified in clause 8, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. + +## 7.7 Non-imperative message part errors + +This category includes: + +- syntactically incorrect optional Information elements; +- conditional IE errors. + +### 7.7.1 Syntactically incorrect optional Information elements + +The protocol entity shall treat all optional Information elements that are syntactically incorrect in a message as not present in the message. + +## 7.8 Messages with semantically incorrect contents + +When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part (i.e. of clauses 5 and 6) of the present document are performed. If however no such reactions are specified, the MS shall ignore the message except for the fact that, if COMM = T, it returns a STATUS message with cause value "semantically incorrect message" and including, if possible, as diagnostics the complete message received (this may not be possible, e.g. due to length restrictions). + +# --- 8 Message functional definitions and contents + +This subclause defines the structure of the messages of those layer 3 protocols defined in the present document, that is the GCC protocol. + +All messages are standard L3 messages as defined in 3GPP TS 24.007. + +Each definition given in the present subclause includes: + +- a brief description of the message direction and use; +- a definition in which direction the message is defined; +- a table listing the information elements permitted to be in that message and their order of their appearance in the message. All information elements that may be repeated are explicitly indicated. Neither the network nor the MS is allowed to include information elements in a message which are not specified for the message or to include the information elements in the message in an order different from the specified order. ( V and LV formatted IEs, which compose the imperative part of the message, occur before T, TV, and TLV formatted IEs which compose the non-imperative part of the message, cf. 3GPP TS 24.007.) In a (maximal) sequence of consecutive information elements with half octet length, the first information element with half octet length occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements. + +For each information element the table indicates: + +- 1) if the IE has format T, TV, or TLV, the IEI used by the IE at the indicated position in the message, in hexadecimal notation. If the IEI has half octet length, this is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-); +- 2) the name of the information element (which may give an idea of the semantics of the element). The name of the information element (usually written in *italics*) followed by "IE" or "information element" is used in 3GPP TS 24.008 as reference to the information element within a message; + +- 3) the name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced subclause of clause 9 describing the value part of the information element; +- 4) the presence requirement indication (M or O) for the IE as defined in 3GPP TS 24.007 (Presence requirement indication C is not used in the present document); +- 5) the format of the information element (T, V, TV, LV, TLV) as defined in 3GPP TS 24.007; +- 6) the length of the information element (or permissible range of lengths), in octets, in the message. This indication is normative. However, further restrictions to the length of an IE may be specified elsewhere. + +subclauses specifying, where appropriate; + +- the meaning of; and +- conditions for; + +absence, repeated occurrence, and/or presence for IEs with presence requirement O in the relevant message which together with other conditions specified in the present document define when the information elements shall be included or not, what presence, repeated occurrence, and absence of such IEs means. + +## 8.1 CONNECT + +This message is sent by the network to the calling MS in order to indicate establishment of the requested group call. + +See table 8.1. + +Message type: CONNECT; + +Significance: dual; + +Direction: network to MS. + +**Table 8.1: CONNECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|----------------------------------------------|------------------------------------------|----------|--------|--------| +| | Group Call control
protocol discriminator | Protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier
subclause 9.2 | M | V | 1/2 | +| | Connect
message type | Message type
subclause 9.3 | M | V | 1 | +| | Group call reference | Call reference
subclause 9.4.1 | M | V | 4 | +| | Originator indication | Originator indication
subclause 9.4.4 | M | V | 1/2 | +| | Talker priority used | Talker priority
subclause 9.4.9 | M | V | 1/2 | +| D- | SMS indications | SMS indications
subclause 9.4.10 | O | TV | 1 | + +### 8.1.1 SMS indications + +This IE shall be included if the network supports the transfer of mobile originated point-to-point short messages via the group call channel. If this IE is not received the MS shall assume the default settings “SMS guaranteed privacy required” and “SMS data confidentiality required”. + +## 8.2 GET STATUS + +This message is sent by the network at any time to solicit a STATUS message from the MS in acknowledged or unacknowledged mode. + +See table 8.2. + +Message type: GET STATUS; + +Significance: local; + +Direction: network to MS. + +**Table 8.2: GET STATUS message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------|----------------------------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
subclause 9.2 | M | V | 1/2 | +| | message type | message type
subclause 9.3 | M | V | 1 | +| 17 | mobile identity | mobile identity
3GPP TS 24.008, subclause
10.5.1.4 | O | TLV | 3-10 | + +### 8.2.1 mobile identity + +This IE is included if the network wishes so. If the message is received by the MS in acknowledged mode, it shall be ignored by the MS. If received in unacknowledged mode, it specifies the destination MS, see clause 5. + +## 8.3 IMMEDIATE SETUP + +This message is sent by the MS to the network in order to set-up a group call immediately, i.e. without previous establishment of an MM connection. See table 8.3. + +Message type: IMMEDIATE SETUP; + +Significance: dual; + +Direction: MS to network. + +**Table 8.3: IMMEDIATE SETUP message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-------------------------------|------------------------------------------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
subclause 9.2 | M | V | 1/2 | +| | message type | message type
subclause 9.3 | M | V | 1 | +| | Talker priority requested | Talker priority
subclause 9.4.9 | M | V | 1/2 | +| | Ciphering key sequence number | Ciphering key sequence number
3GPP TS 24.008, subclause
10.5.1.2 | M | V | 1/2 | +| | Mobile station classmark | Mobile station classmark 2
3GPP TS 24.008, subclause
10.5.1.6 | M | LV | 4 | +| | Mobile identity | Mobile identity
3GPP TS 24.008, subclause
10.5.1.4 | M | LV | 2-9 | +| | Group identity | Call reference
subclause 9.4.1 | M | V | 4 | + +### 8.3.1 Mobile identity + +This IE shall specify the TMSI, if available, and the IMSI else. + +### 8.3a IMMEDIATE SETUP 2 + +This message is sent by the MS to the network in order to set-up a group call immediately, i.e. without previous establishment of an MM connection, and to include compressed originator-to dispatcher information. The message shall only be used if the MS has a valid TMSI. See table 8.3a. + +Message type: IMMEDIATE SETUP 2; + +Significance: dual + +Direction: MS to network. + +**Table 8.3a: IMMEDIATE SETUP 2 message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-------------------------------|---------------------------------------------------------------------|----------|--------|--------| +| | Protocol discriminator | Protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier
subclause 9.2 | M | V | 1/2 | +| | Message type | Message type
subclause 9.3 | M | V | 1 | +| | Talker priority requested | Talker priority
subclause 9.4.9 | M | V | 1/2 | +| | Ciphering key sequence number | Ciphering key sequence number
3GPP TS 24.008, subclause 10.5.1.2 | M | V | 1/2 | +| | Mobile station classmark | Mobile station classmark 2
3GPP TS 24.008, subclause 10.5.1.6 | M | LV | 4 | +| | TMSI | TMSI/P-TMSI
3GPP TS 44.018, subclause 10.5.2.42 | M | V | 4 | +| | Group identity | Call reference
subclause 9.4.1 | M | V | 4 | +| | Compressed otdi | Compressed otdi
subclause 9.4.8 | M | V | 5 | + +#### 8.3a.1 TMSI + +The *TMSI* information element indicates the Temporary Mobile Subscriber Identity of the MS. + +### 8.3a.2 Compressed otdi + +This information element contains compressed originator-to-dispatcher information. + +## 8.4. SET PARAMETER + +This message is sent by the network at any time to ask the MS for setting of parameters and consequential actions. See table 8.4. + +Message type: SET PARAMETER; + +Significance: local; + +Direction: network to MS. + +**Table 8.4: SET PARAMETER message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------|-----------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
subclause 9.2 | M | V | 1/2 | +| | message type | message type
subclause 9.3 | M | V | 1 | +| | state attributes | state attributes
subclause 9.4.7 | M | V | 1/2 | +| | spare half octet | spare half octet
subclause 9.4.6 | M | V | 1/2 | + +## 8.5 SETUP + +This message is sent by the MS to the network in order to set-up a group call after establishment of an MM connection. See table 8.5. + +Message type: SETUP; + +Significance: dual; + +Direction: MS to network. + +**Table 8.5: SETUP message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|-----------------------------------------|-------------------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
subclause 9.2 | M | V | 1/2 | +| | message type | message type
subclause 9.3 | M | V | 1 | +| | Group identity | Call reference
subclause 9.4.1 | M | V | 4 | +| 7E | Originator-to-dispatcher
information | User-user
3GPP TS 24.008 subclause 10.5.4.25 | O | TLV | 3 - 35 | +| C- | Talker priority requested | Talker priority
subclause 9.4.9 | O | TV | 1 | + +### 8.5.1 Originator-to-dispatcher information + +The *Originator-to-dispatcher* IE specifies originator-to-dispatcher information. The coding of the IE is equal to the coding of User-user information defined in 3GPP TS 24.008 subclause 10.5.4.25. + +### 8.5.2 Talker priority requested + +This information element shall be included in the message, if the talker priority requested by the subscriber is higher than "normal priority" and the subscriber is allowed to use the requested talker priority for the respective group identity. + +## 8.6 STATUS + +This message is sent by the MS to the network at any time during a call to report certain error conditions listed in clause 8. It shall also be sent in response to a GET STATUS message. See table 8.6. + +Message type: STATUS; + +Significance: local; + +Direction: MS to network. + +**Table 8.6: STATUS message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------|--------------------------------------|----------|--------|---------| +| | protocol discriminator | protocol discriminator subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier subclause 9.2 | M | V | 1/2 | +| | message type | message type subclause 9.3 | M | V | 1 | +| | cause | cause subclause 9.4.3 | M | LV | 2 - 248 | +| A- | call state | call state subclause 9.4.2 | O | TV | 1 | +| B- | state attributes | state attributes subclause 9.4.7 | O | TV | 1 | + +### 8.6.1 Call state + +This IE may always be included in the message. In certain cases identified in the present document, the IE shall be included in the message, e.g.: when used in the get status procedure. + +### 8.6.2 State attributes + +This IE may always be included in the message. In certain cases identified in the present document, the IE shall be included in the message, e.g.: when used in the get status procedure. + +## 8.7 TERMINATION + +This message is sent by the network to the MS in order to indicate that the group call has been or will be terminated, e.g. as a response to a termination request. See table 8.7. + +Message type: TERMINATION; + +Significance: dual; + +Direction: network to MS. + +**Table 8.7: TERMINATION message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------|-----------------------------------------|----------|--------|---------| +| | protocol discriminator | protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
subclause 9.2 | M | V | 1/2 | +| | message type | message type
subclause 9.3 | M | V | 1 | +| | cause | cause
subclause 9.4.3 | M | LV | 2 - 248 | + +## 8.8 TERMINATION REJECT + +This message is sent by the network to the MS in order to reject a termination request, for example because the MS is not the originator of the group call. See table 8.8. + +Message type: TERMINATION REJECT; + +Significance: dual; + +Direction: network to MS. + +**Table 8.8: TERMINATION REJECT message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------|-----------------------------------------|----------|--------|---------| +| | protocol discriminator | protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
subclause 9.2 | M | V | 1/2 | +| | message type | message type
subclause 9.3 | M | V | 1 | +| | Reject cause | Cause
subclause 9.4.3 | M | LV | 2 - 248 | + +## 8.9 TERMINATION REQUEST + +This message is sent by the MS to the network in order to request termination of a group call which it had originated. See table 8.9. + +Message type: TERMINATION REQUEST; + +Significance: dual; + +Direction: MS to network. + +**Table 8.9: TERMINATION REQUEST message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|------------------------|-----------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
subclause 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
subclause 9.2 | M | V | 1/2 | +| | message type | message type
subclause 9.3 | M | V | 1 | +| | Group call reference | Call reference
subclause 9.4.1 | M | V | 4 | +| C- | Talker priority | Talker priority
subclause 9.4.9 | O | TV | 1 | + +### 8.9.1 Talker priority + +This information element shall be included in the message if the subscriber obtained the uplink with a priority higher than "normal priority". + +# 9 Contents of information elements value parts + +The figures and text in this clause describe the contents of Information Elements (IE) value parts. The structure of an IE as composed of Information Element Identifier (IEI), length, and value part is defined in 3GPP TS 24.007. + +## 9.1 Protocol Discriminator + +The Protocol Discriminator (PD) and its use are defined in 3GPP TS 24.007. + +## 9.2 Transaction identifier + +Bits 5 to 8 of the first octet of every message belonging to the GCC protocol contain the transaction identifier (TI). The transaction identifier and its use are defined in 3GPP TS 24.007. + +## 9.3 Message Type + +The message type IE and its use are defined in 3GPP TS 24.007. Table 9.1 defines the value part of the message type IE used in the GCC protocol. + +**Table 9.1: Message types for GCC** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|---------------------| +| 0 | x | 1 | 1 | 0 | 0 | 0 | 1 | IMMEDIATE SETUP | +| 0 | x | 1 | 1 | 0 | 0 | 1 | 0 | SETUP | +| 0 | x | 1 | 1 | 0 | 0 | 1 | 1 | CONNECT | +| 0 | x | 1 | 1 | 0 | 1 | 0 | 0 | TERMINATION | +| 0 | x | 1 | 1 | 0 | 1 | 0 | 1 | TERMINATION REQUEST | +| 0 | x | 1 | 1 | 0 | 1 | 1 | 0 | TERMINATION REJECT | +| 0 | x | 1 | 1 | 1 | 0 | 0 | 0 | STATUS | +| 0 | x | 1 | 1 | 1 | 0 | 0 | 1 | GET STATUS | +| 0 | x | 1 | 1 | 1 | 0 | 1 | 0 | SET PARAMETER | +| 0 | x | 1 | 1 | 1 | 0 | 1 | 1 | IMMEDIATE SETUP 2 | + +Bit 8 is reserved for possible future use as an extension bit, see 3GPP TS 24.007. + +Bit 7 is reserved for the send sequence number in GCC messages sent from the MS. In GCC messages sent from the network an, bit 7 is coded with a "0", see 3GPP TS 24.007. + +## 9.4 Other information elements + +For coding of other IEs, the rules defined in 3GPP TS 24.007 annex B apply. + +### 9.4.1 Call Reference + +The *Call Reference* information element identifies the group call reference, group identity or group identity with prefix of a group call. It is coded as shown below. It is a type 3 information element. + +` ::= reference { 0 spare_4 | 1 { priority spare_1 } }` + +#### Attributes + +The information element defines a reference which, depending on the situation, is to be interpreted as a group call reference, group identity, or as a group identity with prefix. If the **priority** field is present in ``, the information element also specifies a priority. + +If the *Call Reference* IE is included in the SETUP message and if the **priority** field is present in <*call reference*>, then the MS shall set the priority value to be the same as the priority value in the CM\_SERVICE\_REQUEST message. + +#### Field contents + +The field of the *call reference* information element are coded as shown in table 9.2. + +**Table 9.2: *call reference* information element** + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| reference (27 bits) | | +| This field contains the 27 bit binary encoding (with leading zeroes) of the number the decimal encoding of which (with leading zeroes) is the group call reference, the group identity (see 3GPP TS 23.003), or the group identity with prefix. | | +| priority (3 bits) | | +| This field encodes the priority level of the call (see 3GPP TS 23.067): | | +| Bits | | +| 0 0 0 | reserved | +| 0 0 1 | priority level 4 | +| 0 1 0 | priority level 3 | +| 0 1 1 | priority level 2 | +| 1 0 0 | priority level 1 | +| 1 0 1 | priority level 0 | +| 1 1 0 | priority level B | +| 1 1 1 | priority level A | +| spare_4 (4 bits) | This field shall be ignored | +| spare_1 (1 bit) | This field shall be ignored | + +### 9.4.2 Call state + +The *call state* information element identifies a state, and, if applicable, a sub-state of the group call protocol at the MS side. It is coded as defined below. It is a type 1 information element. + +<*call state*> ::= **state** + +#### Attributes + +The **state** field defines an integer N in the range 0..15. The *call state* information element defines a call state or a sub-state of state U2, ACTIVE, of the GCC protocol. + +#### Field contents + +See table 9.3. + +#### Static conditions + +The values 12 to 15 of integer N are reserved. + +**Table 9.3: *call* state information element** + +| state (4 bits) | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| This field contains the 4 bit encoding (with leading zeroes) of an integer N = 0, 15. The state or substate associated to integer N is defined below: | | +| N | state | +| 0 | U0 | +| 1 | U1 | +| 2 | U2sl | +| 3 | U3 | +| 4 | U4 | +| 5 | U5 | +| 6 | U0.p | +| 7 | U2wr | +| 8 | U2r | +| 9 | U2ws | +| 10 | U2sr | +| 11 | U2nc | + +### 9.4.3 Cause + +The purpose of the *cause* information element is to describe the reason for generating certain messages and to provide diagnostic information in the event of procedural errors. + +The *cause* information element is a type 4 information element. Its value part has a minimal length of 1 octet. The maximum length is given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +The value part is coded as shown below: + +``` + ::= 1 cause_part [ diagnostics ] + | 0 cause_part +``` + +#### Attributes + +The **cause\_part** field defines a non-negative integer N. If more than one **cause\_part** fields are present in , the information element indicates an unspecific cause; otherwise, it indicates a cause as defined by N. + +#### Field contents + +The fields of the information element are coded as shown in table 9.4. + +**Table 9.4: cause information element** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------| +| cause_part (7 bits) | | +| This field contains the 7 bit encoding (with leading zeroes) of a non-negative integer which specifies a cause as defined below: | | +| N | cause | +| 3 | Illegal MS | +| 5 | IMEI not accepted | +| 6 | Illegal ME | +| 8 | Service not authorized | +| 9 | Application not supported on the protocol | +| 10 | RR connection aborted | +| 16 | Normal call clearing | +| 17 | Network failure | +| 20 | Busy | +| 22 | Congestion | +| 23 | User not originator of call | +| 24 | Network wants to maintain call | +| 30 | Response to GET STATUS | +| 32 | Service option not supported | +| 33 | Requested service option not subscribed | +| 34 | Service option temporarily out of order | +| 38 | Call cannot be identified | +| 48 - 63 | retry upon entry into a new cell | +| 81 | Invalid transaction identifier value | +| 95 | Semantically incorrect message | +| 96 | Invalid mandatory information | +| 97 | Message type non-existent or not implemented | +| 98 | Message type not compatible with the protocol state | +| 99 | Information element non-existent or not implemented | +| 100 | Message type not compatible with the protocol state | +| 112 | Protocol error, unspecified | +| Any other value received shall be treated as an unspecific cause. | | +| Diagnostics | | +| This field contains a message or information element. | | + +### 9.4.4 Originator indication + +The *originator indication* information element informs the group call control entity in the MS whether it is the calling user. It is a type 1 information element. + +The value part is coded as shown below: + +* ::= spare\_3 OI* + +#### Attributes + +The IE defines whether the MS is the originator of the group call. + +#### Field contents + +The fields of the information element are coded as shown in table 9.5. + +**Table 9.5: *originator indication* information element fields** + +| | | | +|---------------------------------------------------------|----------|------------------------------------------| +| spare_3 (3 bits)
This field shall be ignored. | | | +| OI (1 bit) | 0 | The MS is not the originator of the call | +| | 1 | The MS is the originator of the call | + +### 9.4.5 Not used + +### 9.4.6 Spare Half Octet + +This element is used in the description of messages in clause 8 when an odd number of half octet type 1 information elements are used. This element consists of 4 bits set to zero and is placed in bits 5 to 8 of the octet unless otherwise specified. It is a type 1 information element. The contents of this element shall be ignored by the receiver. + +### 9.4.7 State attributes + +The *state attributes* information element contains information about parameter values of the MS. It is a type 1 information element. + +The value part is coded as shown below: + +<*state attributes*> ::= **DA UA COMM OI** + +#### Attributes + +The IE defines values of parameters D-ATT, U-ATT, ORIG, and COMM. + +#### Field contents + +The fields of the information element are coded as shown in table 9.7. + +**Table 9.7: *state attributes* information element fields** + +| | | | +|---------------------|----------|----------------------------------------------------------| +| DA (1 bit) | 0 | User connection in the downlink not attached (D-ATT = F) | +| | 1 | User connection in the downlink attached (D-ATT = T) | +| UA (1 bit) | 0 | User connection in the uplink not attached (U-ATT = F) | +| | 1 | User connection in the uplink attached (U-ATT = T) | +| COMM (1 bit) | 0 | COMM = F | +| | 1 | COMM = T | +| OI (1 bit) | 0 | The MS is not the originator of the call (ORIG = F) | +| | 1 | The MS is the originator of the call (ORIG = T) | + +### 9.4.8 Compressed otdi + +The *Compressed otdi* information element specifies an integer N in 40 bit binary representation; bit 8 of octet 1 is the most significant bit and bit 1 of octet 5 is the least significant bit. The integer denotes compressed originator-to-dispatcher information. The corresponding decompressed originator-to-dispatcher information is given by the following attributes: + +- User-user protocol discriminator: IA5 characters +- User-user information: The user-user information is a string of 12 digits which are the decimal representation of the integer N with leading zeros. Each digit after decompression is coded in one octet. The bits 1 to 7 are used for the coding of the IA5 character, and bit 8 is coded as "0". A coding example is given in annex A. + +### 9.4.9 Talker priority + +The *Talker priority* information element identifies the talker priority requested or used by the MS or the talker priority used by the network for the setup of the group call. It is a type 1 information element. + +The value part is coded as shown below: + +<*talker priority*> ::= **spare\_1 talker\_priority** + +#### Attributes + +The **talker\_priority** field defines the talker priority requested or used by the MS or the talker priority used by the network. + +#### Field contents + +The fields of the information element are coded as shown in table 9.8. + +**Table 9.8: *talker priority* information element** + +| | | +|----------------------------------------------------------------------------------------------------------------|---------------------| +| spare_1 (1 bit) | | +| This field shall be encoded as "0" and ignored by the receiver. | | +| priority (3 bits) | | +| This field encodes the talker priority requested or used by the MS or the talker priority used by the network. | | +| Bits | | +| 0 0 0 | Normal priority | +| 0 0 1 | Privileged priority | +| 0 1 0 | Emergency priority | +| 0 1 1 | Not used (Note) | +| to | | +| 1 1 1 | Not used (Note) | +| An MS or a network not supporting the use of talker priorities shall encode the priority as "000". | | +| Note: This value shall be interpreted by the receiver as "normal priority". | | + +### 9.4.10 SMS indications + +The *SMS indications* information element informs the group call control entity in the MS whether or not SMS data confidentiality and SMS guaranteed privacy are required for mobile originated short messages (see TS 43.068 for further details). It is a type 1 information element. + +The value part is coded as shown below: + +<*SMS indications*> ::= **spare\_2 DC GP** + +#### Attributes + +The IE defines values of parameters DC and GP. + +#### Field contents + +The fields of the information element are coded as shown in table 9.9. + +**Table 9.9: *SMS indications* information element fields** + +| | | | +|---------------------------------------------------------------------------------------------|----------|---------------------------------------| +| spare_2 (2 bits)
This field shall be encoded as "00" and ignored by the receiver. | | | +| DC (1 bit) | | | +| | 0 | SMS data confidentiality not required | +| | 1 | SMS data confidentiality required | +| GP (1 bit) | | | +| | 0 | SMS guaranteed privacy not required | +| | 1 | SMS guaranteed privacy required | + +# Annex A (informative): Example of the coding of the user-user information after decompression of the originator-to-dispatcher information + +If the originator-to-dispatcher information after the decompression in decimal representation with leading zeros is "000000009123", then the user-user information is coded in IA5 characters as follows: + +**Table A.1: Example of user-user information in IA5 characters after decompression** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | content | IA5 Code | +|----------|---|---|---|---|---|---|---|---|--------------|----------| +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 2. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 3. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 4. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 5. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 6. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 7. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 8. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | | 9. digit: 9 | 0x39 | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | 1 | | 10. digit: 1 | 0x31 | +| 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | | 11. digit: 2 | 0x32 | +| 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | | 12. digit: 3 | 0x33 | + +# Annex B (informative): Change History + +| TSG# | TSG doc | WG doc | Spec | CR | Rev | Ph | Cat | Old vers | New vers | Title | WI | +|------------|-----------|-----------|----------------|------|-----|--------|-----|--------------|---------------|------------------------------------------------------------------------------------|-----------| +| S#31 | | Feb 2000 | 04.68 | | | | | 7.1.0 | 8.0.0 | Specification version upgrade to Release 1999 version 8.0.0 | | +| CN#7 | | N1-000469 | 04.68 | A024 | | R99 | | 8.0.0 | 8.1.0 | Addition of cause values, Approved by TSGN#7 then SMG email approval before SMG#32 | | +| S#32, CN#8 | | N1-000677 | 04.68 | A025 | | R00 | | 8.1.0 | 9.0.0 | Introduction of Originator-to-dispatcher information into VGCS | | +| | | | 04.68 / 44.068 | | | | | 04.68 v9.0.0 | 44.068 v4.0.0 | Conversion to 3GPP TS format | - | +| CN#9 | NP-000449 | N1-001006 | 44.068 | 001 | 1 | R00 | C | 4.0.0 | 4.1.0 | The repetition of the priority in the Call Reference IE in the SETUP message | ASCI | +| | | | | | | | | 4.1.0 | 4.1.1 | Oct 2000: correction of references. | | +| NP-12 | NP-010269 | N1-010854 | 44.068 | 002 | 1 | Rel-4 | F | 4.1.1 | 4.2.0 | Clarification of the coding of otdi information in IA5 format | ASCI | +| NP-16 | NP-020224 | N1-021368 | 44.068 | 003 | 1 | Rel-4 | F | 4.2.0 | 4.3.0 | Various clean-up of wrong references, eg towards 44.018 | TEI4 | +| NP-16 | | | 44.068 | | | Rel-5 | | 4.3.0 | 5.0.0 | CN plenary decision to make this TS also for Release 5. | June 2002 | +| | | | 44.068 | | | Rel-5 | | 5.0.0 | 5.0.1 | Editorial update to remove corrupted headings and bullets | June 2002 | +| NP-22 | NP-030486 | N1-031546 | 44.068 | 004 | | Rel-6 | C | 5.0.1 | 6.0.0 | Clarification of the muting and unmuting of the downlink | TEI6 | +| CP-29 | CP-050365 | C1-050900 | 44.068 | 005 | | Rel-7 | B | 6.0.0 | 7.0.0 | Addition of talker priority | EVGCS | +| CP-33 | CP-060464 | C1-061467 | 44.068 | 011 | | Rel-7 | B | 7.0.0 | 7.1.0 | Talker Priority IEI in Termination Request Message | EVGCS | +| CP-33 | CP-060506 | C1-061468 | 44.068 | 012 | | Rel-7 | F | 7.0.0 | 7.1.0 | TC RT Increase VGCS setup timeout (MS timer TMM-est) | TEI7 | +| CP-35 | CP-070144 | C1-070524 | 44.068 | 014 | 1 | Rel-7 | B | 7.1.0 | 7.2.0 | Addition of SMS indications in GCC Connect Message | IVGCS | +| CP-42 | | | | | | Rel-8 | | 7.2.0 | 8.0.0 | Upgrade to Rel-8 | Dec 2008 | +| CP-46 | | | | | | Rel-9 | | 8.0.0 | 9.0.0 | Upgrade to Rel-9 | Dec 2009 | +| CP-50 | CP-100763 | C1-104238 | 44.068 | 0015 | 1 | Rel-10 | B | 9.0.0 | 10.0.0 | TC-RT: Introduction of group IDs with prefix | Dec 2010 | +| CP-57 | | | | | | Rel-11 | | 10.0.0 | 11.0.0 | Upgrade to Rel-11 | Sept 2012 | +| CP-65 | | | | | | Rel-12 | | 11.0.0 | 12.0.0 | Upgrade to Rel-12 | Sept 2014 | +| CP-70 | | | | | | Rel-13 | | 12.0.0 | 13.0.0 | Upgrade to Rel-13 | Dec 2015 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88e | | | | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44069/raw.md b/marked/Rel-16/44_series/44069/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f7460c9d32b1002a8331f9e626955e0d0f5c625f --- /dev/null +++ b/marked/Rel-16/44_series/44069/raw.md @@ -0,0 +1,1090 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 Applicability..... | 7 | +| 5 Main concepts ..... | 7 | +| 6 Elementary procedures for Broadcast Call Control ..... | 8 | +| 6.1 Overview ..... | 8 | +| 6.1.1 General ..... | 8 | +| 6.1.2 Broadcast call control states ..... | 8 | +| 6.1.2.1 Broadcast call control states at the MS side of the interface ..... | 8 | +| 6.1.2.1.1 Attributes and Parameters of BCC in the MS ..... | 8 | +| 6.1.2.1.2 NULL (U0)..... | 9 | +| 6.1.2.1.3 MM CONNECTION PENDING (U0.p)..... | 9 | +| 6.1.2.1.4 BROADCAST CALL INITIATED (U1)..... | 9 | +| 6.1.2.1.5 BROADCAST CALL ACTIVE (U2)..... | 9 | +| 6.1.2.1.6 BROADCAST CALL PRESENT (U3) ..... | 9 | +| 6.1.2.1.7 BROADCAST CALL CONNECTION REQUESTED (U4) ..... | 9 | +| 6.1.2.1.8 TERMINATION REQUESTED (U5) ..... | 9 | +| 6.1.2.1.9 RECEIVE MODE ACTIVE (U6)..... | 10 | +| 6.1.2.1.10 BCC TIMERS IN THE MS ..... | 10 | +| 6.1.2.1.11 CONSISTENCY OF PARAMETERS AND STATES ..... | 10 | +| 6.1.2.2 BROADCAST CALL CONTROL STATES AT THE NETWORK SIDE OF THE INTERFACE ..... | 10 | +| 6.1.2.2.1 NULL (State N0)..... | 10 | +| 6.1.2.2.2 BROADCAST CALL INITIATED (N1)..... | 11 | +| 6.1.2.2.3 BROADCAST CALL ACTIVE (N2)..... | 11 | +| 6.1.2.2.4 BROADCAST CALL ESTABLISHMENT PROCEEDING (N3) ..... | 11 | +| 6.1.2.2.5 TERMINATION REQUESTED (N4) ..... | 11 | +| 6.2 Procedures for establishment of a broadcast call ..... | 11 | +| 6.2.1 Activation of a broadcast call by the network ..... | 11 | +| 6.2.2 Mobile originated establishment ..... | 11 | +| 6.2.2.1 Termination during mobile originated establishment..... | 12 | +| 6.2.2.2 Abnormal cases..... | 12 | +| 6.2.3 Mobile terminating broadcast call establishment in the MS ..... | 12 | +| 6.3 Procedures during the active state and receive mode active state of a broadcast call..... | 13 | +| 6.3.1 Mobile station procedures in the active state..... | 13 | +| 6.3.2 Network procedures in the active state..... | 13 | +| 6.3.3 Mobile station procedures in the RECEIVE MODE ACTIVE state..... | 13 | +| 6.4 Procedures for release, abortion, and termination of a broadcast call..... | 13 | +| 6.4.1 Termination procedure ..... | 13 | +| 6.4.2 Abort and release procedures ..... | 14 | +| 6.5 Miscellaneous procedures ..... | 14 | +| 6.5.1 Status procedures..... | 14 | +| 6.5.1.1 Get status procedure..... | 14 | +| 6.5.1.2 Set parameter procedure ..... | 14 | +| 7 Handling of unknown, unforeseen, and erroneous protocol data ..... | 15 | +| 7.1 General ..... | 15 | +| 7.2 Message too short..... | 15 | +| 7.3 Unknown or unforeseen transaction identifier ..... | 15 | +| 7.4 Unknown or unforeseen message type..... | 15 | +| 7.5 Non-semantical mandatory information element errors..... | 16 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------| +| 7.6 | Unknown and unforeseen information elements in the non-imperative message part ..... | 16 | +| 7.6.1 | Information elements unknown in the message ..... | 16 | +| 7.6.2 | Out of sequence information elements ..... | 16 | +| 7.6.3 | Repeated Information elements ..... | 16 | +| 7.7 | Non-imperative message part errors ..... | 16 | +| 7.7.1 | Syntactically incorrect optional Information elements ..... | 16 | +| 7.8 | Messages with semantically incorrect contents ..... | 17 | +| 8 | Message functional definitions and contents ..... | 17 | +| 8.1 | CONNECT ..... | 18 | +| 8.2 | GET STATUS ..... | 18 | +| 8.2.1 | mobile identity ..... | 18 | +| 8.3 | IMMEDIATE SETUP ..... | 19 | +| 8.3.1 | Mobile identity ..... | 19 | +| 8.3a | IMMEDIATE SETUP 2 ..... | 19 | +| 8.3a.1 | TMSI ..... | 20 | +| 8.3a.2 | Compressed otdi ..... | 20 | +| 8.4 | SET PARAMETER ..... | 20 | +| 8.5 | SETUP ..... | 20 | +| 8.5.1 | Originator-to-dispatcher information ..... | 21 | +| 8.6 | STATUS ..... | 21 | +| 8.6.1 | Call state ..... | 21 | +| 8.6.2 | State attributes ..... | 22 | +| 8.7 | TERMINATION ..... | 22 | +| 8.8 | TERMINATION REJECT ..... | 22 | +| 8.9 | TERMINATION REQUEST ..... | 23 | +| 9 | Contents of information elements value parts ..... | 23 | +| 9.1 | Protocol Discriminator ..... | 23 | +| 9.2 | Transaction identifier ..... | 23 | +| 9.3 | Message Type ..... | 23 | +| 9.4 | Other information elements ..... | 24 | +| 9.4.1 | Call Reference ..... | 24 | +| 9.4.2 | Call state ..... | 25 | +| 9.4.3 | Cause ..... | 26 | +| 9.4.4 | Originator indication ..... | 27 | +| 9.4.5 | Spare Half Octet ..... | 28 | +| 9.4.6 | State attributes ..... | 28 | +| 9.4.7 | Compressed otdi ..... | 28 | +| Annex A (informative): | Example of the coding of the user-user information after
decompression of the originator-to-dispatcher information ..... | 29 | +| Annex B (informative): | Change History ..... | 30 | + +# --- 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 Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] Void. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 42.069: "Voice Broadcast Service (VBS); Stage 1". +- [3] 3GPP TS 23.003: "Numbering, addressing and identification". +- [4] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2". +- [5] 3GPP TS 43.069: "Voice Broadcast Call Service (VBCS); Stage 2". +- [6] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". +- [7] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [8] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". +- [9] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [10] 3GPP TS 44.068: "Group Call Control (GCC) protocol". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions defined in 3GPP TS 42.069 and the following apply: + +**Attachment of the user connection:** See 3GPP TS 24.008, subclause 5.2. + +**Broadcast call channel:** downlink channel to be allocated in each cell of the group call area for a particular broadcast call. All MSs of the listening service subscribers in one cell shall listen to the common downlink. + +**Broadcast call:** is used in the same sense as "voice broadcast call". + +**Calling user:** BCC entity in the Mobile Station (MS) initiating or having initiated a broadcast call. + +**Clearing the context related to the broadcast call establishment:** all running BCC timers in the relevant BCC entity are stopped, all attributes in the relevant BCC entity are deleted. + +**Downlink:** network to MS direction. + +**Group receive mode:** See 3GPP TS 44.018. + +**Originating mobile station:** MS initiating or having initiated the broadcast call. + +**Uplink:** Mobile station to network direction. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviation defined in 3GPP TR 21.905 [1a] and the following applies: + +| | | +|-----|------------------------| +| BCC | Broadcast Call Control | +|-----|------------------------| + +# 4 Applicability + +Support of the broadcast call protocol is optional in the MS and in the network. + +# 5 Main concepts + +The present document describes the broadcast call control (BCC) protocol, which is one of the protocols of the Connection Management (CM) sublayer (see 3GPP TS 24.007). + +There is in general more than one MS engaged in a broadcast call. Consequently, there is in general more than one MS with a BCC entity engaged in the same broadcast call, and there is one BCC entity in the network engaged in that broadcast call. + +Under which conditions a BCC message is passed from lower (sub-)layers to the BCC entity is defined in the specifications of the sub-layers. + +The MS shall ignore BCC messages that it receives which were sent in unacknowledged mode and which explicitly specify as destination a mobile identity which is not a mobile identity of the MS. + +Higher layers and the MM sub-layer decide when to accept parallel BCC transactions and when/whether to accept BCC transactions in parallel to other CM transactions. + +The broadcast call may be initiated by a mobile user or by a dispatcher. Specification of a protocol for dispatchers is out of the scope of the present document. Hence, in the scope of the present document, there are: + +- one BCC entity in the network; and +- one or more than one BCC entities in different MSs; + +engaged in a broadcast call, and one or none of the MSs is the originator of the broadcast call (called the originating MS in the present document). + +**NOTE:** Whereas for the Group Call Control (GCC) protocol (see 3GPP TS 44.068), in certain situations, the GCC entity in a MS assumes to be the originator of a broadcast call without being the originator, this is not the case for the BCC protocol. + +The originator of the BCC transaction chooses the Transaction Identifier (TI). A MS not assuming to be the originator of the transaction will choose the transaction identifier received from the network, setting the TI flag to $1+x \bmod 2$ where $x$ is the received TI flag. + +The present document describes the broadcast call control protocol only with regard to two peer entities, one in a MS, the other one in the network. The call control entities are described as communicating finite state machines which exchange messages across the radio interface and communicate internally with other protocol (sub)layers. In particular, the BCC protocol uses the MM and RR sublayer specified in 3GPP TS 24.008 and 3GPP TS 44.018. The BCC entity in a MS that is not the originator of the broadcast call shall not send messages to its peer entity. This description is only normative as far as the consequential externally observable behaviour is concerned. For simplicity, instead of using the terms "BCC entity in the MS" and "BCC entity in the network", the present document often uses the terms "MS" and "network" if no confusion may arise. + +Certain sequences of actions of the two peer entities compose "elementary procedures" which are used as a basis for the description in the present document. These elementary procedures are defined in clause 6. + +The network should apply supervisory functions to verify that the BCC procedures are progressing and if not, take appropriate means to resolve the problems. This, however, is out of the scope of the present document. + +# 6 Elementary procedures for Broadcast Call Control + +## 6.1 Overview + +### 6.1.1 General + +The elementary procedures may be broadcasted into the following classes: + +- broadcast call establishment procedures; +- broadcast call termination procedures; +- broadcast call information phase procedures; +- miscellaneous procedures. + +### 6.1.2 Broadcast call control states + +#### 6.1.2.1 Broadcast call control states at the MS side of the interface + +The BCC entity of the MS is described as an extended finite state machine. It performs transitions between states. It has certain parameters and attributes, e.g. configuration parameters and behaviour parameters, which it sets and changes based on interaction with higher and lower (sub-)layers and on message exchange with its peer entity. If a configuration parameter is set to a certain value, the MS shall also adapt the configuration accordingly. Behaviour parameters decide on (part of) the behaviour of the BCC entity. When the BCC entity in the MS receives a message, it shall first analyse whether it shall ignore the message, see clauses 5 and 7. + +##### 6.1.2.1.1 Attributes and Parameters of BCC in the MS + +For the following behaviour parameters, the description is informative. + +| Parameter | Description | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------| +| ORIG | Depending on the context, the MS assumes to be the originator of the call (ORIG=T) or not to be the originator of the call (ORIG=F). | +| COMM | Depending on the context, the MS assumes that communication with its peer entity is enabled in both directions (COMM = T) or not (COMM = F). | + +For the following configuration parameters the MS shall adapt its configuration according to the parameter value and parameter definition. + +| Parameter | Definition | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D-ATT | D-ATT = T means that the MS attaches the user connection for the broadcast call in the downlink.
D-ATT = F means that the MS does not attach the user connection for the broadcast call in the downlink. | +| U-ATT | U-ATT = T means that the MS attaches the user connection for the broadcast call in the uplink.
U-ATT = F means that the MS does not attach the user connection for the broadcast call in the uplink. | + +##### 6.1.2.1.2 NULL (U0) + +No broadcast call exists for the BCC entity. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.3 MM CONNECTION PENDING (U0.p) + +The BCC entity has requested the explicit establishment of an MM connection. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.4 BROADCAST CALL INITIATED (U1) + +The BCC entity has requested the peer entity in the network to establish a broadcast call. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = T, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.5 BROADCAST CALL ACTIVE (U2) + +The broadcast call is established at least in one cell. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = T, D-ATT = T, U-ATT = T. + +##### 6.1.2.1.6 BROADCAST CALL PRESENT (U3) + +The MS has received a notification about an ongoing broadcast call. Higher layers are requested to accept or reject the call. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.7 BROADCAST CALL CONNECTION REQUESTED (U4) + +The MS has received a notification about an ongoing broadcast call. Higher layers have decided to accept the call. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F. + +##### 6.1.2.1.8 TERMINATION REQUESTED (U5) + +The MS which is the originator of the broadcast call has been in state U1 or U2 and has sent a TERMINATION REQUEST message to the network. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = T, D-ATT = T, U-ATT = T. + +##### 6.1.2.1.9 RECEIVE MODE ACTIVE (U6) + +The BCC entity in the MS in state U4, BROADCAST CALL CONNECTION REQUESTED, has got an indication from lower (sub-)layers that RR has entered group receive mode (see 3GPP TS 44.018). When entering the state, parameters shall be set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = T, U-ATT = F. + +##### 6.1.2.1.10 BCC TIMERS IN THE MS + +Table 6.1 specifies the timers used in BCC. The denotation of columns is defined as follows: + +| | | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| timer ::= | name of the timer; | +| set ::= | under which conditions the timer is set (i.e., started); | +| stopped ::= | under which conditions the timer is stopped; | +| running in state(s) ::= | in which state(s) the timer may be running; | +| action at expiry ::= | which actions the BCC entity shall perform at expiry; | +| value ::= | the duration between setting the timer and expiry of the timer ("s" denotes "second(s)" "xx - yy" means that any value between xx and yy is permitted). | + +**Table 6.1: Specification of timers used in BCC** + +| timer | set | stopped | running in state(s) | action at expiry | value | +|-------------------------|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------|--------------| +| T no channel | in state U6 on receipt of an indication from lower (sub-)layers that no channel is currently available | when leaving U6 or when receiving in U6 an indication from lower (sub-)layers that a channel is available | in U6, depending on further conditions | see subclause 6.3.1 | 3 s | +| T MM-est | when entering U0.p using the set-up procedure
when entering U1 using the immediate set-up procedure | when leaving U0.p or U1 | U0.p, U1 | see subclause 6.2.1 | 7 s | +| T term | when sending a TERMINATION REQUEST | when receiving a TERMINATION or TERMINATION REJECT | U5 | abort broadcast call | 10 s | +| T conn req | when entering state U4 | when leaving state U4 | U4 | abort broadcast call | 10-30 s | + +##### 6.1.2.1.11 CONSISTENCY OF PARAMETERS AND STATES + +The MS shall consider the following parameter values as inconsistent with the state or sub-state: + +ORIG = T is inconsistent with states U3, U4, and U6. + +COMM = T is inconsistent with states U0, U3, U4, and U6. + +All other values of parameters ORIG, COMM, D-ATT, and U-ATT shall not be considered by the MS as inconsistent with a state. + +#### 6.1.2.2 BROADCAST CALL CONTROL STATES AT THE NETWORK SIDE OF THE INTERFACE + +##### 6.1.2.2.1 NULL (State N0) + +No broadcast call exists for the BCC entity. + +##### 6.1.2.2.2 BROADCAST CALL INITIATED (N1) + +The BCC entity has received the indication that a peer entity in a MS wants to establish a broadcast call for a certain broadcast identity. + +##### 6.1.2.2.3 BROADCAST CALL ACTIVE (N2) + +The broadcast call is established in at least one cell; there may be a MS which has seized the uplink or not; there may be talking dispatchers or not. + +##### 6.1.2.2.4 BROADCAST CALL ESTABLISHMENT PROCEEDING (N3) + +The BCC entity wants to accept the broadcast call, has initiated establishment of corresponding broadcast call channels, and, if there is a calling user, has sent a CONNECT message to the calling user. + +##### 6.1.2.2.5 TERMINATION REQUESTED (N4) + +The BCC entity has asked lower sub-layers to terminate the broadcast call in all cells and waits for a confirmation that the broadcast call has been terminated in all cells. + +## 6.2 Procedures for establishment of a broadcast call + +### 6.2.1 Activation of a broadcast call by the network + +The BCC entity in the network may initiate the activation of a broadcast call with a certain broadcast call reference and priority in a list of cells by asking lower layers to establish the broadcast call with that broadcast call reference and + +priority in those cells. It then waits until it is informed by lower (sub-)layers that resource activation was sufficiently successful, and enters state N2, BC ACTIVE. + +### 6.2.2 Mobile originated establishment + +Higher layers in the MS may ask the BCC entity in state U0, NULL, to establish a broadcast call, either using the immediate set-up procedure or using the set-up procedure. The request contains a group-id and may contain a priority indication. + +On request of higher layers to establish a broadcast call using the set-up procedure, the BCC entity of the MS builds an appropriate SETUP message and asks lower (sub-)layers to establish an MM connection explicitly (i.e. by use of a CM SERVICE REQUEST message) and to transmit the SETUP message. It then enters state U0.p, MM CONNECTION PENDING. In state U0.p, when informed by lower sub-layers that an MM connection has been established, the BCC entity in the MS shall stop timer $T_{MM-est}$ and enter state U1, BC INITIATED. + +On request of higher layers to establish a broadcast call using the immediate set-up procedure, the BCC entity of the MS builds an appropriate IMMEDIATE SETUP message and asks lower (sub-)layers to establish an MM connection implicitly (see 3GPP TS 24.008) and to transmit the IMMEDIATE SETUP message. It sets timer $T_{MM-est}$ and then enters state U1, BC INITIATED. + +The network BCC entity in state NULL may receive a set-up message from its peer entity in the originating MS. This set-up message is either a SETUP message or an IMMEDIATE SETUP message. The network enters state N1, BC INITIATED. + +In state N1, the network decides whether: + +- a) the establishment is accepted; or +- b) the establishment rejected. + +In case a), the BCC entity in the network considers the peer entity in the MS having sent the set-up message to be the calling user and asks lower layers to activate the appropriate resources. It then: + +- 1) waits until it is informed by lower (sub-)layers that resource activation was sufficiently successful, then sends a CONNECT message to the calling user, and enters state N2, BC ACTIVE; or +- 2) sends a CONNECT message to the calling user and enters N3, BC ESTABLISHMENT PROCEEDING. In state N3, the BCC entity is informed by lower layers whenever the status of resources for the broadcast call is changed. When informed that activation of resources was sufficiently successful, the BCC entity in the network enters state N2, ACTIVE. + +The CONNECT message specifies the broadcast call reference of the broadcast call and indicates that the MS is the originator of the broadcast call. + +In case b), the further proceeding is as defined in subclause 6.2.2.1. + +In state U0.p or U1, the BCC entity in the MS shall, on receipt of a CONNECT message, establish the conditions defined for state U2, ACTIVE and the suitable sub-state (see subclause 6.1.2.1), stop timer $T_{MM-est}$ (if running) and enter state U2, ACTIVE. If the immediate set-up procedure has been used, the BCC entity in the MS shall inform lower sub-layers that the MM connection has been implicitly established. + +#### 6.2.2.1 Termination during mobile originated establishment + +At any time during the mobile originated establishment of a broadcast call, the network may decide to terminate the connection between the two peer entities in the network and MS. In this case the network sends a TERMINATION message to the MS specifying the appropriate cause; it may ask lower (sub-)layers to release associated resources. The further actions are specified in subclause 6.4. + +During mobile originated establishment of a broadcast call, the MS may abort the broadcast call, see subclause 6.4. + +#### 6.2.2.2 Abnormal cases + +At expiry of $T_{MM-est}$ , or radio link failure (see 3GPP TS 44.018), the BCC entity in the MS requests lower sub-layers to abort the MM connection establishment and returns to state U0, NULL (this includes clearing of the context related to the broadcast call establishment). + +On receipt of an indication of lower sub-layers that the MM connection establishment was unsuccessful, the BCC entity in the MS returns to state U0, NULL (this includes clearing of the context related to the broadcast call establishment). + +### 6.2.3 Mobile terminating broadcast call establishment in the MS + +The BCC entity in the MS, being in state U0, NULL, may receive an indication of lower layers that a broadcast call exists. This indication specifies the broadcast-id and a priority. It shall then inform higher layers and enter state U3, BC present. This state may be supervised by a timer at expiry of which the BCC entity clears the context and returns to state U0, NULL. + +In state U3, on request of higher layers to join the broadcast call, the BCC entity in the MS stops any running timer, asks lower sub-layers to join the broadcast call, starts timer $T_{\text{conn req}}$ , and enters state U4, BC CONNECTION REQUESTED. + +In state U4, on indication of lower sub-layers that the broadcast call has been joint (this indication specifies the mode of the RR connection), the BCC entity in the MS stops any running timer, enters state U6, RECEIVE MODE ACTIVE, establishes the appropriate configurations (see subclause 6.1) and informs higher layers (this includes information about the sub-state). + +## 6.3 Procedures during the active state and receive mode active state of a broadcast call + +### 6.3.1 Mobile station procedures in the active state + +In the active state, the BCC entity in the MS performs, on receipt of messages from its peer entity, on request of higher layers, and on indication of lower sub-layers, actions as defined below. + +On request of higher layers, the MS initiates abort or termination of the broadcast call, see subclause 6.4. + +If the network initiates broadcast call abortion or termination, the MS reacts as specified in subclause 6.4. + +On radio link failure, the MS aborts the broadcast call, see subclause 6.4. + +### 6.3.2 Network procedures in the active state + +In the active state the BCC entity in the network performs supervisory functions, maintenance functions and resource modifications which are not further specified. (This includes through-connection of the application data stream(s), which is defined in 3GPP TS 43.069). + +The network may initiate abort or termination of the broadcast call, see subclause 6.4. + +If the MS initiates broadcast call abortion or termination, the network reacts as specified in subclause 6.4. + +The network may send a SET PARAMETER message to the MS in order to ask the MS to set parameters to certain values and to take consequential actions. + +### 6.3.3 Mobile station procedures in the RECEIVE MODE ACTIVE state + +In state U6, RECEIVE MODE ACTIVE, the BCC entity in the MS performs, on receipt of messages from its peer entity, on request of higher layers, and on indication of lower sub-layers, actions as defined below. + +On request of higher layers, the MS initiates abort of the broadcast call, see subclause 6.4. + +If the network initiates broadcast call abortion or termination, the MS reacts as specified in subclause 6.4. + +Upon indication from lower layers that no channel is available, the BCC entity in the MS informs higher layers and starts timer $T_{\text{no channel}}$ . Then: + +- if $T_{\text{no channel}}$ expires, the BCC entity in the MS informs higher layers, asks lower sub-layers to abort resources and enters the idle state; +- upon indication from lower layers that a channel is available, the BCC entity in the MS informs higher layers and stops timer $T_{\text{no channel}}$ . + +## 6.4 Procedures for release, abortion, and termination of a broadcast call + +### 6.4.1 Termination procedure + +The MS being the originator of the broadcast call (ORIG = T) shall, on request of higher layers, initiate the termination procedure by sending a TERMINATION REQUEST message to its peer entity in the network and setting timer $T_{\text{term}}$ . + +The network either accepts the termination by sending a TERMINATION or rejects termination by sending a TERMINATION REJECT. These messages indicate an appropriate cause. + +In state U5, on receipt of a TERMINATION REJECT message, the BCC entity in the MS informs higher layers and stops $T_{\text{term}}$ . + +In state U5, on $T_{\text{term}}$ expiry, the BCC entity in the MS informs higher layers, asks lower sub-layers to abort the broadcast call, clears the context related to the broadcast call, and returns to state U0, NULL. + +In any state, on receipt of a TERMINATION message, the BCC entity in the MS informs higher layers, asks lower sub-layers to release the broadcast call, clears the context related to the broadcast call, and returns to state U0, NULL. + +At any time during a broadcast call, the network may decide to terminate the connection between the two peer entities in the network and MS. In this case the network sends a TERMINATION message to the MS specifying the appropriate cause; it may ask lower (sub-)layers to release associated resources. The further actions are specified above in this subclause 6.4. + +### 6.4.2 Abort and release procedures + +The network may ask lower sub-layers to abort or release the broadcast call. The MS will detect abort of the broadcast call by detecting the abort of RR resources, and a broadcast call release by detecting the release of RR resources. The BCC entity in the MS shall then inform higher layers, ask lower sub-layers to abort the broadcast call, clear the context related to the broadcast call, and return to state U0, NULL. + +The MS shall, on request of higher layers, initiate the release procedure by asking lower sub-layers to release the broadcast call, clearing the context related to the broadcast call, and returning to state U0, NULL. + +The BCC entity in the MS shall when required by the BCC protocol, abort the broadcast call by requesting lower layers to abort the broadcast call, informing higher layers, clearing the context related to the broadcast call, and returning to state U0, NULL. + +## 6.5 Miscellaneous procedures + +### 6.5.1 Status procedures + +#### 6.5.1.1 Get status procedure + +Upon receipt of a GET STATUS message, the MS shall: + +- if COMM = T, respond with a STATUS message, reporting the current call state, the current values of configuration and behaviour parameters and cause value # 30 "Response to GET STATUS"; +- if COMM = F, ignore the message. + +#### 6.5.1.2 Set parameter procedure + +Upon receipt of a SET PARAMETER message the MS shall set the parameters to the indicated values and the configuration shall be adapted to the new values of configuration parameters, if they are consistent with the current BCC state and sub-state (see subclause 6.1.2). If they are not: + +- if COMM, before the message was received, is equal to T, it shall send a STATUS message specifying error cause "message incompatible with protocol state", the state and, if applicable, sub-state, and the *state attributes* IE; +- if COMM, before the message was received, is equal to F, it shall ignore the message. + +# --- 7 Handling of unknown, unforeseen, and erroneous protocol data + +## 7.1 General + +This subclause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving BCC protocol entity in the MS. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. Error handling procedures in the network are for further study. + +Subclauses 7.1 to 7.8 shall be applied in order of precedence. + +Most error handling procedures are mandatory for the MS. + +In this clause the following terminology is used: + +- an IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in clause 9, or if its value part violates rules of clause 9. However it is not a syntactical error that a TLV encoded IE specifies in its length indicator a greater length than defined in clause 9; +- a message is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part (i.e. clauses 6 and 7) of the present document. + +## 7.2 Message too short + +When a message is received that is too short to contain a complete message type information element, that message shall be ignored, cf. 3GPP TS 24.007. + +## 7.3 Unknown or unforeseen transaction identifier + +If COMM = T, the MS shall answer to a message received with TI value "111" by sending a STATUS message with same TI value, cause "invalid transaction identifier value", and including, if possible, as diagnostics the complete message received (this may not be possible, e.g., due to length restrictions). If COMM = F, the MS shall ignore a message received with TI value "111". + +For a broadcast call control message received with TI different from "111", the following procedures shall apply. + +Whenever a message is received specifying a transaction identifier which is not recognized as relating to an active transaction, if COMM = F, the MS shall ignore the message; if COMM = T, the MS shall send a STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and including, if possible, as diagnostics the complete message received (this may not be possible, e.g., due to length restrictions). + +## 7.4 Unknown or unforeseen message type + +If the protocol entity in the MS receives a message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message except for the fact that, if COMM = T, it shall return a STATUS message with cause "message type non-existent or not implemented" and including as diagnostics the message type of the message received. + +NOTE: A message type not defined for the PD in the given direction is regarded by the receiver as a message type not defined for the PD, see 3GPP TS 24.007. + +If the protocol entity in the MS receives a message not compatible with the protocol state, the MS shall ignore the message except for the fact that, if COMM = T, it returns a STATUS message with cause "message type not compatible with protocol state" and including as diagnostics the message type of the message received. + +## 7.5 Non-semantical mandatory information element errors + +When on receipt of a message: + +- an "imperative message part" error; or +- a "missing mandatory IE" error, + +is diagnosed or when a message containing + +- a syntactically incorrect mandatory IE; or +- an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.008, subclause 10.5); or +- an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.008, subclause 10.5), + +is received, + +- the MS shall, if COMM = F, ignore the message. Otherwise it shall proceed as follows: + +The MS shall ignore the message except for the fact that it shall return a STATUS message with cause "invalid mandatory information" and including, if possible, as diagnostics the complete message received (this may not be possible, e.g., due to length restrictions). + +## 7.6 Unknown and unforeseen information elements in the non-imperative message part + +### 7.6.1 Information elements unknown in the message + +The protocol entity in the MS shall ignore all information elements unknown in a message which are not encoded as "comprehension required". + +### 7.6.2 Out of sequence information elements + +The MS shall ignore all out of sequence Information elements in a message which are not encoded as "comprehension required". + +### 7.6.3 Repeated Information elements + +If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified in clause 8, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. + +## 7.7 Non-imperative message part errors + +This category includes: + +- syntactically incorrect optional Information elements; +- conditional IE errors. + +### 7.7.1 Syntactically incorrect optional Information elements + +The protocol entity shall treat all optional Information elements that are syntactically incorrect in a message as not present in the message. + +## 7.8 Messages with semantically incorrect contents + +When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part (i.e. of clauses 5 and 6) of the present document are performed. If however no such reactions are specified, the MS shall ignore the message except for the fact that, if COMM = T, it returns a STATUS message with cause value "semantically incorrect message" and including, if possible, as diagnostics the complete message received (this may not be possible, e.g.: due to length restrictions). + +# 8 Message functional definitions and contents + +This clause defines the structure of the messages of those layer 3 protocols defined in the present document, that is the BCC protocol. + +All messages are standard L3 messages as defined in 3GPP TS 24.007. + +Each definition given in the present clause includes: + +- a brief description of the message direction and use; +- a definition in which direction the message is defined; +- a table listing the information elements permitted to be in that message and their order of their appearance in the message. All information elements that may be repeated are explicitly indicated. Neither the network nor the MS is allowed to include information elements in a message which are not specified for the message or to include the information elements in the message in an order different from the specified order. (V and LV formatted IEs, which compose the imperative part of the message, occur before T, TV, and TLV formatted IEs which compose the non-imperative part of the message, cf. 3GPP TS 24.007.) In a (maximal) sequence of consecutive information elements with half octet length, the first information element with half octet length occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements. + +For each information element the table indicates: + +- 1) if the IE has format T, TV, or TLV, the IEI used by the IE at the indicated position in the message, in hexadecimal notation. If the IEI has half octet length, this is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-); + - 2) the name of the information element (which may give an idea of the semantics of the element). The name of the information element (usually written in italics) followed by "IE" or "information element" is used in 3GPP TS 24.008 as reference to the information element within a message; + - 3) the name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced subclause of clause 9 describing the value part of the information element; + - 4) the presence requirement indication (M or O) for the IE as defined in 3GPP TS 24.007 (Presence requirement indication C is not used in the present document.); + - 5) the format of the information element (T, V, TV, LV, TLV) as defined in 3GPP TS 24.007; + - 6) the length of the information element (or permissible range of lengths), in octets, in the message. This indication is normative. However, further restrictions to the length of an IE may be specified elsewhere. +- c) subclauses specifying, where appropriate: +- the meaning of and + - conditions for +- absence, repeated occurrence, and/or presence for IEs with presence requirement O in the relevant message which together with other conditions specified in the present document define when the information elements shall be included or not, what presence, repeated occurrence, and absence of such IEs means. + +TABLE 8.1 + +## 8.1 CONNECT + +This message is sent by the network to the calling MS in order to indicate establishment of the requested broadcast call. + +See table 8.1. + +Message type: CONNECT + Significance: dual + Direction: network to MS + +**Table 8.1: CONNECT message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|-----------------------------------------------|-----------------------------|----------|--------|--------| +| | Broadcast Call control protocol discriminator | Protocol discriminator 9.1 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier 9.2 | M | V | 1/2 | +| | Connect message type | Message type 9.3 | M | V | 1 | +| | Broadcast call reference | Call reference 9.4.1 | M | V | 4 | +| | Originator indication | Originator indication 9.4.4 | M | V | 1/2 | +| | Spare half octet | Spare half octet 9.4.5 | M | V | 1/2 | + +## 8.2 GET STATUS + +This message is sent by the network at any time to solicit a STATUS message from the MS in acknowledged or unacknowledged mode. + +See table 8.2. + +Message type: GET STATUS + Significance: local + Direction: network to MS + +**Table 8.2: GET STATUS message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|------------------------|------------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator 9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier 9.2 | M | V | 1/2 | +| | message type | message type 9.3 | M | V | 1 | +| | mobile identity | mobile identity 3GPP TS 24.008, 10.5.1.4 | O | TLV | 3-10 | + +### 8.2.1 mobile identity + +This IE is included if the network wishes so. If the message is received by the MS in acknowledged mode, it shall be ignored by the MS. If received in unacknowledged mode, it specifies the destination MS, see clause 5. + +## 8.3 IMMEDIATE SETUP + +This message is sent by the MS to the network in order to set-up a broadcast call immediately, i.e. without previous establishment of an MM connection. See table 8.3. + +Message type: IMMEDIATE SETUP + Significance: dual + Direction: MS to network + +**Table 8.3: IMMEDIATE SETUP message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|-------------------------------|-----------------------------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
9.2 | M | V | 1/2 | +| | message type | message type
9.3 | M | V | 1 | +| | Spare half octet | Spare half octet
9.4.5 | M | V | 1/2 | +| | Ciphering key sequence number | Ciphering key sequence number
3GPP TS 24.008, 10.5.1.2 | M | V | 1/2 | +| | Mobile station classmark | Mobile station classmark 2
3GPP TS 24.008, 10.5.1.6 | M | LV | 4 | +| | Mobile identity | Mobile identity
3GPP TS 24.008, 10.5.1.4 | M | LV | 2-9 | +| | Broadcast identity | Call reference | M | V | 4 | + +### 8.3.1 Mobile identity + +This IE shall specify the TMSI, if available, and the IMSI else. + +### 8.3a IMMEDIATE SETUP 2 + +This message is sent by the MS to the network in order to set-up a group call immediately, i.e. without previous establishment of an MM connection, and to include compressed originator-to dispatcher information. The message shall only be used if the MS has a valid TMSI. See table 8.3a. + +Message type: IMMEDIATE SETUP 2; + +Significance: dual + +Direction: MS to network. + +**Table 8.3a: IMMEDIATE SETUP 2 message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|-------------------------------|-----------------------------------------------------------|----------|--------|--------| +| | Protocol discriminator | Protocol discriminator
9.1 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier
9.2 | M | V | 1/2 | +| | Message type | Message type
9.3 | M | V | 1 | +| | Spare half octet | Spare half octet
9.4.6 | M | V | ½ | +| | Ciphering key sequence number | Ciphering key sequence number
3GPP TS 24.008, 10.5.1.2 | M | V | ½ | +| | Mobile station classmark | Mobile station classmark 2
3GPP TS 24.008, 10.5.1.6 | M | LV | 4 | +| | TMSI | TMSI/P-TMSI
3GPP TS 44.018, 10.5.2.42 | M | V | 4 | +| | Group identity | Call reference
9.4.1 | M | V | 4 | +| | Compressed otdi | Compressed otdi
9.4.7 | M | V | 5 | + +#### 8.3a.1 TMSI + +The *TMSI* information element indicates the Temporary Mobile Subscriber Identity of the MS. + +### 8.3a.2 Compressed otdi + +This information element contains compressed originator-to-dispatcher information. + +## 8.4 SET PARAMETER + +This message is sent by the network at any time to ask the MS for setting of parameters and consequential actions. + +See table 8.4. + +Message type: SET PARAMETER + +Significance: local + +Direction: network to MS + +**Table 8.4: SET PARAMETER message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|------------------------|-------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
9.2 | M | V | 1/2 | +| | message type | message type
9.3 | M | V | 1 | +| | state attributes | state attributes
9.4.6 | M | V | 1/2 | +| | spare half octet | spare half octet
9.4.6 | M | V | 1/2 | + +## 8.5 SETUP + +This message is sent by the MS to the network in order to set-up a broadcast call after establishment of an MM connection. + +See table 8.5. + +Message type: SETUP + +Significance: dual + +Direction: MS to network + +**Table 8.5: SETUP message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|--------------------------------------|----------------------------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
9.2 | M | V | 1/2 | +| | message type | message type
9.3 | M | V | 1 | +| | Broadcast identity | Call reference
9.4.1 | M | V | 4 | +| 7E | Originator-to-dispatcher information | User-user
3GPP TS 24.008
subclause 10.5.4.25 | O | TLV | 3-35 | + +### 8.5.1 Originator-to-dispatcher information + +The *Originator-to-dispatcher* IE specifies originator-to-dispatcher information. The coding of the IE is equal to the coding of User-user information defined in 3GPP TS 24.008 subclause 10.5.4.25. + +## 8.6 STATUS + +This message is sent by the MS to the network at any time during a call to report certain error conditions listed in subclause 8. It shall also be sent in response to a GET STATUS message. + +See table 8.6. + +Message type: STATUS + +Significance: local + +Direction: MS to network + +**Table 8.6: STATUS message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|------------------------|-------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
9.2 | M | V | 1/2 | +| | message type | message type
9.3 | M | V | 1 | +| | cause | cause
9.4.3 | M | LV | 2-248 | +| A- | call state | call state
9.4.2 | O | TV | 1 | +| B- | state attributes | state attributes
9.4.6 | O | TV | 1 | + +### 8.6.1 Call state + +This IE may always be included in the message. In certain cases identified in the present document, the IE shall be included in the message, e.g., when used in the get status procedure. + +### 8.6.2 State attributes + +This IE may always be included in the message. In certain cases identified in the present document, the IE shall be included in the message, e.g., when used in the get status procedure. + +## 8.7 TERMINATION + +This message is sent by the network to the MS in order to terminate the connection between the two peer entities in the network and MS and/or to indicate that the broadcast call has been or will be terminated, e.g. as a response to a termination request. + +See table 8.7. + +Message type: TERMINATION + Significance: dual + Direction: network to MS + +**Table 8.7: TERMINATION message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|------------------------|-------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
9.2 | M | V | 1/2 | +| | message type | message type
9.3 | M | V | 1 | +| | cause | cause
9.4.3 | M | LV | 2-248 | + +## 8.8 TERMINATION REJECT + +This message is sent by the network to the MS in order to reject a termination request. + +See table 8.8. + +Message type: TERMINATION REJECT + Significance: dual + Direction: network to MS + +**Table 8.8: TERMINATION REJECT message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|------------------------|-------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
9.2 | M | V | 1/2 | +| | message type | message type
9.3 | M | V | 1 | +| | Reject cause | Cause
9.4.3 | M | LV | 2-248 | + +## 8.9 TERMINATION REQUEST + +This message is sent by the MS to the network in order to request termination of a broadcast call which it had originated. + +See table 8.9. + +Message type: TERMINATION REQUEST + Significance: dual + Direction: MS to network + +**Table 8.9: TERMINATION REQUEST message content** + +| IEI | Information element | Type/Reference | Presence | Format | Length | +|-----|--------------------------|-------------------------------|----------|--------|--------| +| | protocol discriminator | protocol discriminator
9.1 | M | V | 1/2 | +| | transaction identifier | transaction identifier
9.2 | M | V | 1/2 | +| | message type | message type
9.3 | M | V | 1 | +| | Broadcast call reference | Call reference
9.4.1 | M | V | 4 | + +# 9 Contents of information elements value parts + +The figures and text in this clause describe the contents of Information Elements (IE) value parts. The structure of an IE as composed of Information Element Identifier (IEI), length, and value part is defined in 3GPP TS 24.007. + +## 9.1 Protocol Discriminator + +The Protocol Discriminator (PD) and its use are defined in 3GPP TS 24.007. + +## 9.2 Transaction identifier + +Bits 5 to 8 of the first octet of every message belonging to the BCC protocol contain the transaction identifier (TI). The transaction identifier and its use are defined in 3GPP TS 24.007. + +## 9.3 Message Type + +The message type IE and its use are defined in 3GPP TS 24.007. Table 9.1 define the value part of the message type IE used in the BCC protocol. + +**Table 9.1: Message types for BCC** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|---------------------| +| 0 | x | 1 | 1 | 0 | 0 | 0 | 1 | IMMEDIATE SETUP | +| 0 | x | 1 | 1 | 0 | 0 | 1 | 0 | SETUP | +| 0 | x | 1 | 1 | 0 | 0 | 1 | 1 | CONNECT | +| 0 | x | 1 | 1 | 0 | 1 | 0 | 0 | TERMINATION | +| 0 | x | 1 | 1 | 0 | 1 | 0 | 1 | TERMINATION REQUEST | +| 0 | x | 1 | 1 | 0 | 1 | 1 | 0 | TERMINATION REJECT | +| 0 | x | 1 | 1 | 1 | 0 | 0 | 0 | STATUS | +| 0 | x | 1 | 1 | 1 | 0 | 0 | 1 | GET STATUS | +| 0 | x | 1 | 1 | 1 | 0 | 1 | 0 | SET PARAMETER | +| 0 | x | 1 | 1 | 1 | 0 | 1 | 1 | IMMEDIATE SETUP 2 | + +Bit 8 is reserved for possible future use as an extension bit, see 3GPP TS 24.007. + +Bit 7 is reserved for the send sequence number in BCC messages sent from the MS. In BCC messages sent from the network an, bit 7 is coded with a "0". See 3GPP TS 24.007. + +## 9.4 Other information elements + +For coding of other IEs, the rules defined in 3GPP TS 24.007 annex B apply. + +### 9.4.1 Call Reference + +The *Call Reference* information element identifies the broadcast call reference or broadcast Id of a broadcast call. It is coded as shown below. It is a type 3 information element. + +` ::= reference { 0 spare_4 | { 1 priority spare_1 } }` + +#### Attributes + +The information element defines a reference which, depending on the situation, is to be interpreted as a broadcast call reference or as a broadcast id. If the **priority** field is present in **, the information element also specifies a priority. + +If the *Call Reference* IE is included in the SETUP message and if the **priority** field is present in **, then the MS shall set the priority value to be the same as the priority value in the CM\_SERVICE\_REQUEST message. + +#### Field contents + +The field of the *call reference* information element are coded as shown in table 9.2. + +**Table 9.2: *call reference* information element** + +| | | | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| reference (27 bits) | This field contains the 27 bit binary encoding (with leading zeroes) of the number the decimal encoding of which (with leading zeroes) is the broadcast call reference or the broadcast id (see 3GPP TS 23.003). | | +| priority (3 bits) | | | +| 3 | 2 | 1 | +| 0 | 0 | 0 reserved | +| 0 | 0 | 1 call priority level 4 | +| 0 | 1 | 0 call priority level 3 | +| 0 | 1 | 1 call priority level 2 | +| 1 | 0 | 0 call priority level 1 | +| 1 | 0 | 1 call priority level 0 | +| 1 | 1 | 0 call priority level B | +| 1 | 1 | 1 call priority level A | +| spare_4 (4 bits) | This field shall be ignored | | +| spare_1 (1 bit) | This field shall be ignored | | + +### 9.4.2 Call state + +The *call state* information element identifies a state, and, if applicable, a sub-state of the broadcast call protocol at the MS side. It is coded as defined below. It is a type 1 information element. + +** ::= **state** + +#### Attributes + +The **state** field defines an integer N in the range 0..15. The *call state* information element defines a call state or a sub-state of state U2, ACTIVE, of the BCC protocol. + +#### Field contents + +See table 9.3. + +#### Static conditions + +The values 12 to 15 of integer N are reserved. + +**Table 9.3: *call* state information element** + +| state (4 bits) | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--|--------------| +| This field contains the 4 bit encoding (with leading zeroes) of an integer N = 0, ..., 15. The state or substate associated to integer N is defined below: | | | | +| | N | | state | +| | 0 | | U0 | +| | 1 | | U1 | +| | 2 | | U2 | +| | 3 | | U3 | +| | 4 | | U4 | +| | 5 | | U5 | +| | 6 | | U0.p | +| | 7 | | U6 | +| All other values are reserved. | | | | + +### 9.4.3 Cause + +The purpose of the *cause* information element is to describe the reason for generating certain messages and to provide diagnostic information in the event of procedural errors. + +The *cause* information element is a type 4 information element. Its value part has a minimal length of 1 octet. The maximum length is given by the maximum number of octets in a L3 message (see 3GPP TS 44.006). + +The value part is coded as shown below: + +``` + ::= 1 cause_part [ diagnostics ] + | 0 cause_part +``` + +#### Attributes + +The **cause\_part** field defines a non-negative integer N. If more than one **cause\_part** fields are present in , the information element indicates an unspecified cause; otherwise, it indicates a cause as defined by N. + +#### Field contents + +The fields of the information element are coded as shown in table 9.4. + +**Table 9.4: cause information element** + +| cause_part (7 bits) | | | +|----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|--| +| This field contains the 7 bit encoding (with leading zeroes) of a non-negative integer which specifies a cause as defined below: | | | +| N | cause | | +| 3 | Illegal MS | | +| 5 | IMEI not accepted | | +| 6 | Illegal ME | | +| 8 | Service not authorized | | +| 9 | Application not supported on the protocol | | +| 10 | RR connection aborted | | +| 16 | Normal call clearing | | +| 17 | Network failure | | +| 20 | Busy | | +| 22 | Congestion | | +| 23 | User not originator of call | | +| 24 | Network wants to maintain call | | +| 30 | Response to GET STATUS | | +| 32 | Service option not supported | | +| 33 | Requested service option not subscribed | | +| 34 | Service option temporarily out of order | | +| 38 | Call cannot be identified | | +| 48 - 63 | retry upon entry into a new cell | | +| 81 | Invalid transaction identifier value | | +| 95 | Semantically incorrect message | | +| 96 | Invalid mandatory information | | +| 97 | Message type non-existent or not implemented | | +| 98 | Message type not compatible with the protocol state | | +| 99 | Information element non-existent or not implemented | | +| 100 | Message type not compatible with the protocol state | | +| 112 | Protocol error, unspecified | | +| Any other value received shall be treated as an unspecified cause. | | | +| Diagnostics | | | +| This field contains a message or information element. | | | + +### 9.4.4 Originator indication + +The *originator indication* information element informs the broadcast call control entity in the MS whether it is the calling user. It is a type 1 information element. + +The value part is coded as shown below: + +$\langle \text{originator indication} \rangle ::= \text{spare\_3 OI}$ + +#### Attributes + +The IE defines whether the MS is the originator of the broadcast call. + +#### Field contents + +The fields of the information element are coded as shown in table 9.5. + +**Table 9.5: *originator indication* information element fields** + +| | | | +|------------------------------|----------|------------------------------------------| +| This field shall be ignored. | | spare_3 (3 bits) | +| OI (1 bit) | 0 | The MS is not the originator of the call | +| | 1 | The MS is the originator of the call | + +### 9.4.5 Spare Half Octet + +This element is used in the description of messages in clause 8 when an odd number of half octet type 1 information elements are used. This element consists of 4 bits set to zero and is placed in bits 5 to 8 of the octet unless otherwise specified. It is a type 1 information element. + +### 9.4.6 State attributes + +The *state attributes* information element contains information about parameter values of the MS. It is a type 1 information element. + +The value part is coded as shown below: + +<*state attributes*> ::= **DA UA COMM OI** + +#### Attributes + +The IE defines values of parameters D-ATT, U-ATT, ORIG, and COMM. + +#### Field contents + +The fields of the information element are coded as shown in table 9.7. + +**Table 9.7: *state attributes* information element fields** + +| | | | +|---------------------|----------|----------------------------------------------------------| +| DA (1 bit) | | | +| | 0 | User connection in the downlink not attached (D-ATT = F) | +| | 1 | User connection in the downlink attached (D-ATT = T) | +| UA (1 bit) | 0 | User connection in the uplink not attached (U-ATT = F) | +| | 1 | User connection in the uplink attached (U-ATT = T) | +| COMM (1 bit) | 0 | COMM = F | +| | 1 | COMM = T | +| OI (1 bit) | 0 | The MS is not the originator of the call (ORIG = F) | +| | 1 | The MS is the originator of the call (ORIG = T) | + +### 9.4.7 Compressed otdi + +The *Compressed otdi* information element specifies an integer N in 40 bit binary representation; bit 8 of octet 1 is the most significant bit and bit 1 of octet 5 is the least significant bit. The integer denotes compressed originator-to-dispatcher information. The corresponding decompressed originator-to-dispatcher information is given by the following attributes: + +- User-user protocol discriminator: IA5 characters. +- User-user information: The user-user information is a string of 12 digits which are the decimal representation of the integer N with leading zeros. Each digit after decompression is coded in one octet. The bits 1 to 7 are used for the coding of the IA5 character, and bit 8 is coded as "0". A coding example is given in Annex A. + +# Annex A (informative): Example of the coding of the user-user information after decompression of the originator-to-dispatcher information + +If the originator-to-dispatcher information after the decompression in decimal representation with leading zeros is "000000009123", then the user-user information is coded in IA5 characters as follows: + +**Table A.1: Example of user-user information in IA5 characters after decompression** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | content | IA5 Code | +|----------|---|---|---|---|---|---|---|---|--------------|----------| +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 1. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 2. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 3. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 4. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 5. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 6. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 7. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 8. digit: 0 | 0x30 | +| 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 1 | 9. digit: 9 | 0x39 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 10. digit: 1 | 0x31 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 11. digit: 2 | 0x32 | +| 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 12. digit: 3 | 0x33 | + +# Annex B (informative): Change History + +| TSG# | TSG doc | WG doc | Spec | CR | Rev | Ph | Cat | Old vers | New vers | Title | WI | +|------------|-----------|-----------|----------------|------|-----|--------|-----|--------------|---------------|-----------------------------------------------------------------------------------|------------| +| S#31 | | Feb 2000 | 04.69 | | | | | 7.1.0 | 8.0.0 | Specification version upgrade to Release 1999 version 8.0.0 | | +| CN#7 | | N1-000472 | 04.69 | A021 | | R99 | | 8.0.0 | 8.1.0 | Addition of cause values, Approved at TSGN#7 and SMG email approved before SMG#32 | | +| S#32, CN#8 | | N1-000679 | 04.69 | A022 | | R00 | | 8.1.0 | 9.0.0 | Introduction of Originator-to-dispatcher information into VBS | | +| | | | 04.69 / 44.069 | | | | | 04.69 v9.0.0 | 44.069 v4.0.0 | Conversion to 3GPP TS format | - | +| CN#7 | NP-000449 | N1-001007 | 44.069 | 001 | 1 | R00 | C | 4.0.0 | 4.1.0 | The repetition of the priority in the Call Reference IE in the SETUP message | ASCI | +| | | | | | | | | 4.1.0 | 4.1.1 | Oct 2000: Correction of references. | | +| NP-12 | NP-010269 | N1-010855 | 44.069 | 002 | 1 | Rel-4 | F | 4.1.1 | 4.2.0 | Clarification of the coding of otdi information in IA5 format | ASCI | +| NP-16 | NP-020224 | N1-021369 | 44.069 | 003 | 1 | Rel-4 | F | 4.2.0 | 4.3.0 | Various clean-up of wrong references, eg towards 44.018 | TEI4 | +| NP-16 | | | 44.069 | | | Rel-5 | | 4.3.0 | 5.0.0 | CN plenary decision to make this TS also for Release 5. | June 2002 | +| NP-26 | | | 44.069 | | | Rel-6 | | 5.0.0 | 6.0.0 | CN plenary decision to make this TS also for Release 6. | Dec 2004 | +| CP-33 | CP-060506 | C1-061469 | 44.069 | 005 | | Rel-7 | | 6.0.0 | 7.0.0 | TC RT Increase VBS setup timeout (MS timer TMM-est) | Sept 2006 | +| CP-42 | | | | | | Rel-8 | | 7.0.0 | 8.0.0 | Upgrade to Rel-8. | Dec 2008 | +| CP-46 | | | | | | Rel-9 | | 8.0.0 | 9.0.0 | Upgrade to Rel-9 | Dec 2009 | +| CP-51 | | | | | | Rel-10 | | 9.0.0 | 10.0.0 | Upgrade to Rel-10 | March 2011 | +| CP-57 | | | | | | Rel-11 | | 10.0.0 | 11.0.0 | Upgrade to Rel-11 | Sept 2012 | +| CP-65 | | | | | | Rel-12 | | 11.0.0 | 12.0.0 | Upgrade to Rel-12 | Sept 2014 | +| CP-70 | | | | | | Rel-13 | | 12.0.0 | 13.0.0 | Upgrade to Rel-13 | Dec 2015 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88e | | | | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/44_series/44071/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-16/44_series/44071/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21f40f873f494e457d9a6e6091fc25c40f9f9f50 --- /dev/null +++ b/marked/Rel-16/44_series/44071/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c2e304ce3e2a39d730927f3cf41e1e223ab96efac6295243b92bc00e08dc513 +size 76344 diff --git a/marked/Rel-16/44_series/44071/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/marked/Rel-16/44_series/44071/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..856edbfaa1b61b367b745a8e559f8a804937d5cc --- /dev/null +++ b/marked/Rel-16/44_series/44071/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aae495b538908f0f4c813c7a98d0db714496510b37d413f606895f5d086afe77 +size 74638 diff --git a/marked/Rel-16/44_series/44071/raw.md b/marked/Rel-16/44_series/44071/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..41ff9a074fddcef2dade572f340170508a8c54de --- /dev/null +++ b/marked/Rel-16/44_series/44071/raw.md @@ -0,0 +1,2536 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Generic procedures for the control of location services ..... | 8 | +| 4.1 Overview of the generic protocol and its scope ..... | 8 | +| 4.2 Functional procedures for the control of location services ..... | 8 | +| 4.2.1 General ..... | 8 | +| 4.2.2 Common Information Element Category ..... | 9 | +| 4.2.3 Location service procedures..... | 9 | +| 4.2.3.1 Introduction..... | 9 | +| 4.2.3.2 Handling of protocol errors in LCS procedures..... | 9 | +| 4.2.3.3 Handling of other errors in LCS procedures..... | 9 | +| 4.2.4 Multiple location service invocations..... | 10 | +| 4.2.5 Recovery procedures ..... | 10 | +| 4.2.6 Generic protocol error handling for the component part of location services operations ..... | 10 | +| 4.2.6.1 Single component errors ..... | 10 | +| 4.2.6.2 Multiple component errors..... | 10 | +| 5 Location service support procedures..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Location service support establishment ..... | 10 | +| 5.2.1 Location service support establishment at the originating side..... | 10 | +| 5.2.2 Location service support establishment at the terminating side..... | 11 | +| 5.3 Location service support information transfer phase ..... | 11 | +| 5.4 Location service support release ..... | 11 | +| 5.5 Recovery procedures..... | 11 | +| 5.6 Message flow (single operation example)..... | 11 | +| 5.6.1 LMU initiated location service transaction ..... | 12 | +| 5.6.2 Network initiated location service transaction ..... | 13 | +| 5.7 Handling of unknown, unforeseen, and erroneous protocol data..... | 13 | +| 5.7.1 General ..... | 13 | +| 5.7.2 Message too short..... | 14 | +| 5.7.3 Unknown or unforeseen transaction identifier ..... | 14 | +| 5.7.4 Unknown or unforeseen message type..... | 14 | +| 5.7.5 Non-semantical mandatory Information Element Error ..... | 14 | +| 5.7.6 Unknown and Unforeseen IEs in the non-imperative part ..... | 15 | +| 5.7.6.1 IEs unknown in the message ..... | 15 | +| 5.7.6.2 Out of sequence IEs ..... | 15 | +| 5.7.6.3 Repeated IEs ..... | 15 | +| 5.7.7 Non-imperative message part errors..... | 15 | +| 5.7.7.1 Syntactically incorrect optional IEs (other than Facility) ..... | 15 | +| 5.7.7.2 Conditional IE errors ..... | 15 | +| 6 Message functional definitions and contents ..... | 16 | +| 6.1 General ..... | 16 | +| 6.2 Messages for location services control..... | 16 | +| 6.3 Facility..... | 17 | +| 6.4 Register..... | 17 | +| 6.4.1 Register (network to LMU direction)..... | 17 | +| 6.4.2 Register (LMU to network direction)..... | 17 | +| 6.5 Release complete..... | 18 | +| 6.5.1 Cause ..... | 18 | +| 6.5.2 Facility..... | 18 | + +| | | | +|-------------------------------|---------------------------------------------------------------|-----------| +| 7 | General message format and information elements coding ..... | 18 | +| 7.1 | Overview ..... | 18 | +| 7.2 | Protocol discriminator ..... | 19 | +| 7.3 | Transaction identifier ..... | 19 | +| 7.4 | Message type ..... | 19 | +| 7.5 | Facility information element ..... | 19 | +| 7.6 | Release forbidden ..... | 19 | +| 8 | Detailed message format and information elements coding ..... | 20 | +| 8.1 | Transparent LCS Information ..... | 20 | +| 8.1.1 | Operation Code ..... | 21 | +| 8.1.2 | Error Code ..... | 21 | +| 8.1.3 | Problem Code ..... | 22 | +| 9 | LMU LCS Protocol operation specifications ..... | 22 | +| 9.1 | General ..... | 22 | +| 9.2 | Operation types ..... | 23 | +| 9.2.1 | Operation types description ..... | 26 | +| 9.2.1.1 | StartRIT (network --> LMU) ..... | 26 | +| 9.2.1.2 | ReportRIT (LMU --> network) ..... | 26 | +| 9.2.1.3 | StopRIT (network --> LMU) ..... | 26 | +| 9.2.1.4 | IndicateRITError (LMU --> network) ..... | 26 | +| 9.2.1.5 | (void) ..... | 26 | +| 9.2.1.6 | StatusQuery (network --> LMU) ..... | 26 | +| 9.2.1.7 | StatusUpdate (LMU --> network) ..... | 26 | +| 9.2.1.8 | ResetRequest (network --> LMU) ..... | 26 | +| 9.2.1.9 | OMMngrRequest (network --> LMU) ..... | 26 | +| 9.2.1.10 | OMAgnRequest (LMU --> network) ..... | 26 | +| 10.3 | Error types ..... | 26 | +| 10.3.1 | Error types ASN.1 specification ..... | 26 | +| 10.3.2 | Error types description ..... | 27 | +| 10.3.2.1 | (void) ..... | 27 | +| 10.3.2.2 | (void) ..... | 27 | +| 10.3.2.3 | (void) ..... | 27 | +| 10.3.2.4 | SystemFailure ..... | 27 | +| 10.3.2.5 | DataMissing ..... | 27 | +| 10.3.2.6 | UnexpectedDataValue ..... | 27 | +| 10.3.2.7 | ResourcesNotAvailable ..... | 27 | +| 10.3.2.9 | UnDefinedError ..... | 27 | +| 10.4 | Operations and errors implementation ..... | 28 | +| 11 | LMU LCS Protocol (LLP) messages ..... | 29 | +| 11.1 | Messages, data types and identifiers ..... | 29 | +| 11.1.1 | General ..... | 29 | +| 11.1.2 | ASN.1 data types ..... | 29 | +| 11.1.3 | Identifiers definition ..... | 37 | +| Annex A (informative): | RIT messages ..... | 38 | +| A.1 | Introduction ..... | 38 | +| A.2 | Messages ..... | 38 | +| A.2.1 | RIT Measurement Request Message ..... | 38 | +| A.2.1.1 | RIT Measurement Request Message Information Elements ..... | 38 | +| A.2.1.1.1 | Message Type IE ..... | 38 | +| A.2.1.1.2 | Measurement Instructions IE ..... | 38 | +| A.2.1.1.3 | BTS List IE ..... | 40 | +| A.2.2 | RIT Measurement Response Message ..... | 41 | +| A.2.2.1 | RIT Measurement Response Message Information Elements ..... | 41 | +| A.2.2.1.1 | Message type IE ..... | 41 | +| A.2.2.1.2 | RIT Measurement IE ..... | 41 | +| A.2.3 | RIT Measurement Stop Message ..... | 46 | +| A.2.3.1 | RIT Measurement Stop Message Information Elements ..... | 46 | +| A.2.3.1.1 | Message type IE ..... | 46 | +| A.2.4 | RIT Measurement Error Message ..... | 46 | + +A.2.4.1 RIT Measurement Error Message Information Elements ..... 47 + +A.2.4.1.1 Message type IE ..... 47 + +A.2.4.1.2 RIT Error Type IE ..... 47 + +A.2.4.1.3 RIT Error IE ..... 47 + +**Annex B (informative): (void)..... 48** + +**Annex C (informative): Status Messages ..... 49** + +C.1 Introduction ..... 49 + +C.2 Messages ..... 49 + +C.2.1 Status Query Message ..... 49 + +C.2.1.1 Status Query Message Information Elements..... 49 + +C.2.1.1.1 Message Type IE..... 49 + +C.2.2 Status Query Result Message ..... 49 + +C.2.2.1 Status Query Result Message Information Elements ..... 49 + +C.2.2.1.1 Message Type IE..... 49 + +C.2.2.1.2 Time IE..... 50 + +C.2.2.1.3 RIT Status IE ..... 50 + +C.2.2.1.4 Reserved IE ..... 50 + +C.2.2.1.5 O&M Status IE..... 50 + +C.2.3 Status Update Message..... 51 + +C.2.3.1 Status Update Message Information Elements ..... 51 + +C.2.3.1.1 Message Type IE..... 51 + +C.2.3.1.2 Reason for Status Update IE ..... 51 + +Annex D (informative): Change history..... 52 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains the coding of information necessary for support of location service operation on the mobile radio interface layer 3 between the LMU and SMLC. + +Clause 4 defines generic procedures for the control of location services. In clause 5 location service support procedures are defined. Clause 6 gives the functional definitions and contents of messages for location service operations. Clause 7 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations. Clause 6 gives the detailed message format and information elements coding between the LMU and SMLC. + +Clause 8 gives the specification of the LMU LCS Protocol (LLP) operations. In clause 9 LMU - SMLC messages, data types and identifiers are given. + +This version does not support segmentation of 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". +- [3] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [4] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [5] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services (LCS) in GERAN". +- [6] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [7] ITU-T Recommendation X.691 (1997) | ISO/IEC 8825-2 (1998): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [8] ITU-T Recommendation X.690 (1997) | ISO/IEC 8825-1 (1998): "Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)". +- [9] ITU-T Recommendation X.680 (1997) | ISO/IEC 8824-1 (1998): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [10] ITU-T Recommendation Q.773: "Transaction capabilities formats and encoding". +- [11] (void) +- [12] 3GPP TS 44.004: "Layer 1; General requirements". +- [13] 3GPP TS 44.005: "Data Link (DL) layer General aspects". +- [14] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3". +- [15] 3GPP TS 45.002: "Multiplexing and Multiple Access on the Radio Path". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**E-OTD Assistance Data Message:** contains the RTD and BTS coordinates of the neighbours that should be used in E-OTD measurements. This E-OTD Assistance Data is broadcasted using CBCH channel using SMSCB DRX service. The reception of this broadcast message enables MS to calculate its own location. + +**GPS Assistance Data Message:** contains GPS differential corrections. The reception of this broadcast message enables MS to have calculate more accurate location estimate. + +**GANSS Assistance Data Message:** contains GANSS differential corrections. The reception of this broadcast message enables MS to have calculate more accurate location estimate. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and 3GPP TS 43.059. + +# --- 4 Generic procedures for the control of location services + +## 4.1 Overview of the generic protocol and its scope + +One generic protocol is defined for the control of location services at the radio interface. This protocol operates at layer 3 of the radio interface and assumes the use of layers 1 and 2 conform to 3GPP TS 45-series and 3GPP TS 44.004, 3GPP TS 44.005 and 3GPP TS 44.006. The generic protocol uses the acknowledged information transfer service available at the layer 2 - layer 3 interface. + +The Functional protocol is based on the use of the Facility information element and the FACILITY message as well as other specific functional messages specified in the present document. + +## 4.2 Functional procedures for the control of location services + +### 4.2.1 General + +This subclause specifies the functional signalling procedures for the control of location services at the radio interface. + +The functional protocol utilizes functions and services defined in 3GPP TS 24.008, 3GPP TS 44.018 and the functions of the data link layer as defined in 3GPP TS 44.006. This protocol utilizes also definitions in 3GPP TS 24.007. + +The Common Information Element Category utilizes the Facility information element to transport the protocol defined in the present document. The use of the Facility information element is common to many services, and its contents indicates what type of procedure is being requested. This category can be signalled both in the LMU to network and the network to LMU directions. + +The correlation of location service operations and their responses, is provided by the combination of the transaction identifier of the messages containing the Facility information element and the Invoke identifier present within the Facility information element itself. + +### 4.2.2 Common Information Element Category + +The Common Information Element Category uses operations defined in the present document for location services signalling. Procedures are initiated by sending an operation including an invoke component. The invoke component may yield a Return Error, Return Result or Reject component (also included in an operation) depending on the outcome of the procedure. + +The operation state machines, and procedures for management of Invoke IDs specified in ITU-T Recommendation Q.774 White Book are used. + +A REGISTER message, a FACILITY message or RELEASE COMPLETE message is used to carry the Facility information element which includes these operations. These operations request, acknowledge or reject the desired location service procedure. + +### 4.2.3 Location service procedures + +#### 4.2.3.1 Introduction + +For location service procedures independent of any call, the initiating side must establish a MM-connection between the network and the LMU according to the rules given in 3GPP TS 24.007 and 3GPP TS 24.008. The LMU or the network starts the transaction by transferring a REGISTER message across the radio interface. This transaction is identified by the transaction identifier associated with the REGISTER message present in the component part of the Facility information element. Following the REGISTER message one or more FACILITY messages may be transmitted, all of them related by the use of the same transaction identifier. If the transaction is no longer used, it shall be released by sending a RELEASE COMPLETE message. This procedure is specified in detail in clause 5, and the text in clause 5 takes precedence over this introduction. + +To convey the location service invocation, the Facility information element is used. The Facility information element present either in the REGISTER message or a subsequent message identifies the location service involved and the type of component (i.e. Invoke, Return result, Return error or Reject component). + +When the REGISTER or FACILITY message contains a Facility information element and the requested service is available, a FACILITY message containing a Facility information element may be returned. One or more exchanges of FACILITY messages may subsequently occur. To terminate the service interaction and release the transaction identifier value, a RELEASE COMPLETE message is sent as specified for the specific location service procedure. The RELEASE COMPLETE message may also contain the Facility information element. + +#### 4.2.3.2 Handling of protocol errors in LCS procedures + +Messages containing a Facility information element shall be checked for protocol errors before the contents of the Facility IE is acted on. The checks shall be performed in the following order: + +- 1) The message carrying the Facility IE shall be checked for protocol errors as specified in subclause 5.7. If a protocol error is found then the procedures in subclause 5.7 apply. +- 2) The contents of the Facility IE shall be checked for protocol errors as specified in subclause 4.2.6. If a protocol error is found then the procedures in subclause 4.2.6 apply. + +#### 4.2.3.3 Handling of other errors in LCS procedures + +If the tests specified in subclause 4.2.3.2 have been passed without the detection of a protocol error, the receiver will attempt to process the contents of the Facility Information Element. If errors occur during this processing (e.g. system failure, or information in the Facility IE is incompatible with the requested operation) then the procedures specified in the individual service specifications apply. + +An example of the behaviour that could occur in this case is: + +- the LMU or network sends a Facility information element containing a return error component in a FACILITY or RELEASE COMPLETE message. If the FACILITY message is used then the MM Connection may continue to be used for further signalling. + +### 4.2.4 Multiple location service invocations + +It is possible for several LCS transactions to be used simultaneously. LCS transactions can also exist in parallel with other CM-Layer and MM transactions. The handling of multiple MM connections is defined in 3GPP TS 24.007 and 3GPP TS 24.008. + +A single Facility Information Element shall not contain more than one component. + +### 4.2.5 Recovery procedures + +In case a transaction is not terminated according to the normal procedure as described in the present document the network side has to ensure that the transaction is terminated e.g. by a supervision timer. + +### 4.2.6 Generic protocol error handling for the component part of location services operations + +If a location service operation is to be rejected the operation will be denied, and provided the transaction is still in progress, an appropriate reject component will be returned in a Facility Information Element. + +#### 4.2.6.1 Single component errors + +The reject component shall be sent in a RELEASE COMPLETE message. + +If the component containing the error was itself sent in a RELEASE COMPLETE message then the contents of the component shall be ignored, and no reject component is sent. + +#### 4.2.6.2 Multiple component errors + +If a single Facility IE contains more than one component then a RELEASE COMPLETE message with the cause "Facility rejected" and without any component shall be sent. + +# --- 5 Location service support procedures + +## 5.1 General + +This clause describes the location service support procedures at the radio interface. These procedures are provided by the location service support entity defined in 3GPP TS 24.007. The location service support procedures provide the means to transfer messages for the location service procedures. These procedures are regarded as the user of the location service support. + +## 5.2 Location service support establishment + +At the beginning of each location service procedure a location service support must be established. + +### 5.2.1 Location service support establishment at the originating side + +If the entity that uses the location support procedures needs to send a REGISTER message, the location service support entity shall first request the establishment of an MM-connection. This MM-connection is established according to 3GPP TS 24.008 and 3GPP TS 24.007. If the network is the initiating side then MM-connection establishment may involve paging the LMU. + +The location service support entity shall send the REGISTER message as the first CM-message on the MM-connection. The REGISTER message is sent to the corresponding peer entity on the MM-connection and the location service support shall be regarded as being established. + +### 5.2.2 Location service support establishment at the terminating side + +At the terminating side a location service support is regarded as being established when an MM-connection is established. According 3GPP TS 24.008 this can be ascertained by the receipt of the first message, with a new transaction identifier. For successful establishment of location service support this message shall be a REGISTER message. + +If the terminating side needs to reject the establishment of location services support then it may be immediately initiate location services support release (see subclause 5.4). + +## 5.3 Location service support information transfer phase + +After the establishment of the location service support both users may exchange FACILITY messages by use of the location service support. + +## 5.4 Location service support release + +At the end of each location service procedure the established location service support is released, if a permanent connection is not used. + +The side closing the transaction shall release the transaction by sending the RELEASE COMPLETE message to its corresponding peer entity. + +Both location service support entities release the MM-connection locally. + +## 5.5 Recovery procedures + +The location service support does not provide recovery procedures, i.e. the operations are transparent to the location service support. + +## 5.6 Message flow (single operation example) + +This subclause contains examples of message flows for a single transaction consisting of a single operation. These examples may not show all possibilities. + +### 5.6.1 LMU initiated location service transaction + +![Sequence diagram showing LMU initiated location service transaction. The diagram shows message exchanges between LMU and Network. The sequence starts with a REGISTER message from LMU to Network. The Network responds with Facility (Invoke = Operation (Location service code, Parameter(s))). The LMU then sends a RELEASE COMPLETE or FACILITY message. The Network responds with Facility (Return result = Operation (Parameter(s))). The LMU then sends a RELEASE COMPLETE or FACILITY message. The Network responds with Facility (Return error (Error)). The LMU then sends a RELEASE COMPLETE message. The Network responds with Facility (Reject (Invoke_problem)). The LMU then sends a RELEASE COMPLETE (note) message. The Network responds with Facility (Reject (Invoke_problem)). The LMU then sends a RELEASE COMPLETE (note) message. The Network responds with Facility (Reject (Invoke_problem)).](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg) + +``` + +sequenceDiagram + participant LMU + participant Network + Note left of LMU: REGISTER + LMU->>Network: Facility (Invoke = Operation (Location service code, Parameter(s))) + Network-->>LMU: RELEASE COMPLETE or FACILITY + Network-->>LMU: Facility (Return result = Operation (Parameter(s))) + LMU-->>Network: RELEASE COMPLETE or FACILITY + Network-->>LMU: Facility (Return error (Error)) + LMU-->>Network: RELEASE COMPLETE + Network-->>LMU: Facility (Reject (Invoke_problem)) + LMU-->>Network: RELEASE COMPLETE (note) + Network-->>LMU: Facility (Reject (Invoke_problem)) + LMU-->>Network: RELEASE COMPLETE (note) + Network-->>LMU: Facility (Reject (Invoke_problem)) + +``` + +Sequence diagram showing LMU initiated location service transaction. The diagram shows message exchanges between LMU and Network. The sequence starts with a REGISTER message from LMU to Network. The Network responds with Facility (Invoke = Operation (Location service code, Parameter(s))). The LMU then sends a RELEASE COMPLETE or FACILITY message. The Network responds with Facility (Return result = Operation (Parameter(s))). The LMU then sends a RELEASE COMPLETE or FACILITY message. The Network responds with Facility (Return error (Error)). The LMU then sends a RELEASE COMPLETE message. The Network responds with Facility (Reject (Invoke\_problem)). The LMU then sends a RELEASE COMPLETE (note) message. The Network responds with Facility (Reject (Invoke\_problem)). The LMU then sends a RELEASE COMPLETE (note) message. The Network responds with Facility (Reject (Invoke\_problem)). + +NOTE: To prevent transactions being kept open following exceptional cases, either side of the transaction may release it by sending a RELEASE COMPLETE message without a Facility IE. + +Figure 5.6.1: LMU initiated location service transaction + +### 5.6.2 Network initiated location service transaction + +![](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Sequence diagram illustrating the Network initiated location service transaction between LMU and Network. + +``` + +sequenceDiagram + participant LMU + participant Network + Note over LMU, Network: REGISTER + Note left of Network: Facility (Invoke = Operation (Location service code, Parameter(s))) + Note right of Network: RELEASE COMPLETE or FACILITY (note 1) + Note left of Network: Facility (Return result = Operation (Parameter(s))) + Note right of Network: RELEASE COMPLETE or FACILITY (note 1) + Note left of Network: Facility (Return error (Error)) + Note right of Network: RELEASE COMPLETE (note 1) + Note left of Network: Facility (Reject (Invoke_problem)) + Note right of Network: RELEASE COMPLETE (note 1, note 2) + Note left of Network: RELEASE COMPLETE (note 2) + +``` + +NOTE 1: If the network initiated operation does not require a result, reject or error to be returned then the LMU may release the transaction by sending a RELEASE COMPLETE message without a Facility Information Element and release of transaction by LMU is allowed (i.e. Release Forbidden has not been present in Register message). If release is not allowed by LMU, the LMU sends the result using Facility message. + +NOTE 2: To prevent transactions being kept open following exceptional cases, either side of the transaction may release it by sending a RELEASE COMPLETE message without a Facility IE. + +**Figure 5.6.2: Network initiated location service transaction** + +## 5.7 Handling of unknown, unforeseen, and erroneous protocol data + +### 5.7.1 General + +These procedures only apply to messages where the protocol discriminator is set to indicate LCS operations according to the rules in 3GPP TS 24.007 and the present document. Messages that do not meet this criteria are treated according to other GSM technical specifications. + +This subclause specifies procedures for handling of unknown, unforeseen and erroneous protocol data by the receiving entity. The procedures are called "error handling procedures", but they also define a compatibility mechanism for future extension of the protocol. + +Most error handling procedures are mandatory in the LMU, but optional in the network. Detailed error handling procedures may vary from PLMN to PLMN. + +In this subclause, the following terminology is used: + +- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in the present document or 3GPP TS 44.018. However, it is not a syntactical error if a type 4 IE specifies a length indicator greater than that defined. The component part of the Facility information element is handled by a separate mechanism, and errors in the component part are not covered by this subclause. + +The following procedures are listed in order of precedence. + +Handling of errors in the contents of the Facility IE is described in subclause 4.2.6, and is outside the scope of this subclause. + +### 5.7.2 Message too short + +When a message is received that is too short to contain a complete message type information element, that message shall be ignored. + +### 5.7.3 Unknown or unforeseen transaction identifier + +The LMU shall ignore messages with the transaction identifier value set to "111". + +If the transaction identifier value is not "111" the following procedures shall apply to the LMU: + +- a) If a RELEASE COMPLETE message is received specifying a transaction identifier that is not recognized as relating to a LCS transaction that is in progress then the message shall be ignored. +- b) If a FACILITY message is received specifying a transaction identifier that is not recognized as relating to a LCS transaction that is in progress then a RELEASE COMPLETE message shall be sent. +- c) If a REGISTER message is received specifying a transaction identifier that is not recognized as relating to a LCS transaction that is in progress and with a transaction identifier flag incorrectly set to "1", this message shall be ignored. + +The network may follow the same procedures. + +### 5.7.4 Unknown or unforeseen message type + +If the LMU receives a message type not defined for the protocol discriminator or not implemented by the receiver, then a RELEASE COMPLETE message shall be sent with cause value #97 "message type non-existent or not implemented". + +If the LMU receives a message type not consistent with the transaction state then a RELEASE COMPLETE message shall be sent with cause value #98 "message not compatible with control state". + +The network may follow the same procedures. + +### 5.7.5 Non-semantical mandatory Information Element Error + +When on receipt of a message: + +- an "imperative message part" error; or +- a "missing mandatory IE" error; + +is diagnosed, or when a message containing: + +- a syntactically incorrect mandatory IE; or +- an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007); or +- an out of sequence IE encoded as "comprehension required"; + +is received, the LMU shall proceed as follows: + +- a) If the message is not RELEASE COMPLETE it shall send a RELEASE COMPLETE message with cause "#96 - Invalid mandatory information". +- b) If the message is RELEASE COMPLETE, it shall be treated as a normal RELEASE COMPLETE message. + +The network may follow the same procedures. + +### 5.7.6 Unknown and Unforeseen IEs in the non-imperative part + +#### 5.7.6.1 IEs unknown in the message + +The LMU shall ignore all IEs unknown in the message which are not encoded as "comprehension required". The network shall take the same approach. + +#### 5.7.6.2 Out of sequence IEs + +The LMU shall ignore all out of sequence IEs in a message which are not encoded as "comprehension required". + +The network may take the same approach. + +#### 5.7.6.3 Repeated IEs + +If an information element with format T, TV or TLV (see 3GPP TS 24.007) is repeated in a message in which repetition of the information element is not specified, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. + +The network may follow the same procedures. + +### 5.7.7 Non-imperative message part errors + +This category includes: + +- syntactically incorrect optional IEs; +- conditional IE errors. + +Errors in the content of the Facility IE are handled according to subclause 4.2.6. + +#### 5.7.7.1 Syntactically incorrect optional IEs (other than Facility) + +The LMU shall treat all optional IEs that are syntactically incorrect in a message as not present in the message + +The network shall take the same approach. + +#### 5.7.7.2 Conditional IE errors + +When the LMU upon receipt of a message diagnoses a "missing conditional IE" error, or an "unexpected conditional IE error", or when it receives a message containing at least one syntactically incorrect conditional IE (other than Facility), it shall send a RELEASE COMPLETE message with cause #100 "conditional IE error". + +The network may follow the same procedure. + +# --- 6 Message functional definitions and contents + +## 6.1 General + +This subclause defines the structure of the messages of the layer 3 protocol defined in 3GPP TS 43.059. These messages are standard L3 messages as defined in 3GPP TS 24.007. + +Each definition includes: + +- a) a brief description of the message; +- b) a table listing the information elements in the order of their appearance in the message. In a sequence of consecutive IEs with half octet length, the first IE occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N+1 etc.; + +For each IE the table indicates: + +- 1) the information element identifier, in hexadecimal notation, if the IE has format T, TV or TLV. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-); +- 2) the name of the IE (which gives an idea of the semantics of the element), which is used in this and other specifications as a reference to the IE within the message; + +- 3) the name of the type of the IE (which indicates the coding of the value part of the IE), and a reference to a description of the value part of the IE; + - 4) the presence requirement indication (M, C or O) for the IE, as defined in 3GPP TS 24.007; + - 5) the format of the IE (T, V, TV, LV, TLV) as defined in 3GPP TS 24.007; + - 6) the length of the IE (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by the link layer protocol, and in the case of the facility IE by possible further considerations specified in 3GPP TS 43.059. This indication is non-normative. +- c) subclauses specifying conditions for IEs with presence requirement C or O in the relevant message. Together with other conditions specified in the present document and 3GPP TS 43.059 defines when the IE shall be included or not, what non-presence of such IEs means, and (for IEs with presence requirement C) the static conditions for presence and/or non-presence of the IEs (see 3GPP TS 24.007). + +## 6.2 Messages for location services control + +Table 6.2 summarises the messages for location services control. + +The logical DTAP LCS Information Request and DTAP LCS Information Report messages, that are used in LCS Stage 2 (3GPP TS 43.059), are transported using REGISTER, FACILITY and RELEASE COMPLETE messages. + +If there exists no LCS transaction between LMU and SMLC, REGISTER message is used to deliver the logical message. If LCS transaction between LMU and SMLC exists, FACILITY message is used to deliver the logical message. RELEASE COMPLETE message is used to indicate that LCS transaction is not any more needed, LMU can also use this message to transport logical LCS Information Response message. + +**Table 6.2: Messages for location service control** + +| Messages for location service control | Reference | +|----------------------------------------------|------------------| +| FACILITY | 6.3 | +| REGISTER | 6.4 | +| RELEASE COMPLETE | 6.5 | + +## 6.3 Facility + +This message is sent by the Location Measurement Unit (LMU) or the network to request or acknowledge a location service. It is used when information is to be conveyed and the transaction already exists, but is not to be released. The location service to be invoked, and its associated parameters, are specified in the Facility information element (see table 6.3). + +**Table 6.3: FACILITY message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|------------|--------------------------------------------|-------------------------------|-----------------|---------------|---------------| +| | Location service
Protocol discriminator | Protocol discriminator
7.2 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier
7.3 | M | V | 1/2 | +| | Facility
Message type | Message type
7.4 | M | V | 1 | +| | Facility | Facility
7.5 | M | LV | 2-? | +| 90 | Release forbidden | Release forbidden
7.6 | O | T | 1 | + +## 6.4 Register + +### 6.4.1 Register (network to LMU direction) + +This message is sent by the network to the location measurement unit to assign a new transaction identifier for location service control and to request or acknowledge a location service (see table 6.4.1). + +**Table 6.4.1: REGISTER message content (network to LMU direction)** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|-------------------------------|----------|--------|--------| +| | Location service
Protocol discriminator | Protocol discriminator
7.2 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier
7.3 | M | V | 1/2 | +| | Register
Message type | Message type
7.4 | M | V | 1 | +| | Facility | Facility
7.5 | M | LV | 2-? | +| 90 | Release forbidden | Release forbidden
7.6 | O | T | 1 | + +### 6.4.2 Register (LMU to network direction) + +This message is sent by the location measurement unit to the network to assign a new transaction identifier for location service control and to request or acknowledge a location service (see table 6.4.2). + +**Table 6.4.2: REGISTER message content (LMU to network direction)** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|-------------------------------|----------|--------|--------| +| | Location service
Protocol discriminator | Protocol discriminator
7.2 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier
7.3 | M | V | 1/2 | +| | Register
Message type | Message type
7.4 | M | V | 1 | +| | Facility | Facility
7.5 | M | LV | 2-? | + +## 6.5 Release complete + +This message is sent by the location measurement unit or the network to release a transaction used for location service control. It may also request or acknowledge a location service (see table 6.5). + +**Table 6.5: RELEASE COMPLETE message content** + +| IEI | Information element | Type / Reference | Presence | Format | Length | +|-----|--------------------------------------------|-------------------------------|----------|--------|--------| +| | Location service
Protocol discriminator | Protocol discriminator
7.2 | M | V | 1/2 | +| | Transaction identifier | Transaction identifier
7.3 | M | V | 1/2 | +| | Release Complete
Message type | Message type
7.4 | M | V | 1 | +| 10 | Cause | Cause
3GPP TS 44.018 | O | TLV | 4-32 | +| 11 | Facility | Facility
7.5 | O | TLV | 2-? | + +### 6.5.1 Cause + +This information element shall be included when the functional handling of the Cause IE is specified in the service description. If the functional handling of the Cause IE is not specified, the receiving entity may ignore the IE. The Cause IE used in location services is defined in 3GPP TS 44.018 in subclause 10.5.4.11 (only applicable Cause values are used). + +### 6.5.2 Facility + +This information element shall be included as required by the service description and the procedures defined in the present document and in 3GPP TS 43.059. + +# 7 General message format and information elements coding + +The figures and text in this clause describe message contents. Within each octet, the bit designated "bit 1" is transmitted first, followed by bits 2, 3, 4, etc. Similarly, the octet shown at the top of each figure is sent first. + +## 7.1 Overview + +Within the layer 3 protocol defined in the present document, every message is a standard L3 message as defined in 3GPP TS 24.007. This means that the message consists of the following parts: + +- a) protocol discriminator; +- b) transaction identifier; +- c) message type; +- d) other information elements, as required. + +Unless specified otherwise, a particular information element may be present only once in a given message. + +When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. + +## 7.2 Protocol discriminator + +The Protocol Discriminator (PD) and its use are defined in 3GPP TS 24.007. The present document defines the protocols relating to the PD values: + +1 1 0 0 location services + +## 7.3 Transaction identifier + +For general rules, format and coding of transaction identifier values, see 3GPP TS 24.008. + +## 7.4 Message type + +The message type IE and its use are defined in 3GPP TS 24.007. Table 7.4 defines the value part of the message type IE used in the location service protocol. + +**Table 7.4: Message types** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Message types | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|----------------------------------------------------------|--|--|--|--|--|--|--|--| +| 0 | X | 1 | 0 | . | . | . | . | Clearing messages:
- RELEASE COMPLETE | | | | | | | | | +| 0 | X | 1 | 1 | . | . | . | . | Miscellaneous message group:
- FACILITY
- REGISTER | | | | | | | | | +| | | | | 0 | 0 | 0 | 1 | | | | | | | | | | +| | | | | 0 | 0 | 1 | 0 | | | | | | | | | | +| NOTE 1: Bit 8 is reserved for possible future use as an extension bit, see 3GPP TS 24.007. | | | | | | | | | | | | | | | | | +| NOTE 2: Bit 7 is reserved for the send sequence number in messages sent from the LMU. In messages sent from the SMLC, bit 7 is coded with a "0", see 3GPP TS 24.007. | | | | | | | | | | | | | | | | | + +## 7.5 Facility information element + +The purpose of the Facility information element is to indicate the invocation and operation of location services, identified by the corresponding operation code within the Facility information element. + +The Facility information element is coded as shown in figure 7.5 and clause 8. + +The Facility is a type 4 information element with no upper length limit except that given by the maximum number of octets in a L3 message, see 3GPP TS 44.006. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|--------------| +| Facility IEI | | | | | | | | octet 1 | +| Length of Facility contents | | | | | | | | octet 2 | +| Component(s) (note) | | | | | | | | octet 3 etc. | +| NOTE: | This component contains Transparent LCS Information. Encoding of this component is according to clause 8. | | | | | | | | + +Figure 7.5: Facility information element + +## 7.6 Release forbidden + +This information element is used only in SMLC to LMU messages. The presence of IE indicates that the release of LCS transaction is not allowed by LMU. + +# 8 Detailed message format and information elements coding + +## 8.1 Transparent LCS Information + +This clause provides the formats and encoding of Transparent LCS Information component in the Facility information element. The contents of this component are copied directly from Signal Info (defined in subclause 11.1). Encoding methods for the entire LLP component are based on BASIC-PER; unaligned variant is used. Format and encoding of the entire LLP component - part of which can be seen as a subset of ITU-T Recommendation Q.773 - is based on and consistent with the following ITU-T recommendations: + +- Abstract Syntax Notation One (ASN.1) "Specification of Basic Notation" ITU-T Recommendation X.680 | ISO/IEC 8824-1. +- ASN.1 encoding rules "Specification of Packed Encoding Rules (PER)" ITU-T Recommendation X.691 | ISO/IEC 8825-2. + +NOTE 1: Concerning the general rules for encoding (structure of encoding, identifier octets, length octets, etc.) see ITU-T Recommendations X.680 and ITU-T Recommendation X.691. For these general rules the same exceptions apply as stated in 3GPP TS 29.002. Following ASN.1 definitions are exactly same than in ITU-T Recommendation Q.773. + +NOTE 2: invokeNotLast component is added to the Component list. This change impacts to the coding of the Component type and thus to coding of the LLP messages. + +The Component portion of the TCAP used in this protocol, LLP, is a modification of the TCAP Component portion defined in ITU-T Recommendation, Q.773. Even though part of the LLP component can be seen as a subset of TCAP, BER encoding is not used. + +``` + +Component ::= CHOICE { + invoke [1] IMPLICIT Invoke, + returnResultLast [2] IMPLICIT ReturnResult, + returnError [3] IMPLICIT ReturnError, + reject [4] IMPLICIT Reject, + returnResultNotLast [7] IMPLICIT ReturnResult, + invokeNotLast [8] IMPLICIT Invoke } + +-- The Components are sequences of data elements. + +Invoke ::= SEQUENCE { + invokeID InvokeIdType, + linkedID [0] IMPLICIT InvokeIdType OPTIONAL, + operationCode OPERATION, + parameter ANY DEFINED BY operationCode OPTIONAL } + +-- ANY is filled by the single ASN.1 data type following the keyword PARAMETER or the keyword +-- ARGUMENT +-- in the type definition of a particular operation. + +ReturnResult ::= SEQUENCE { + invokeID InvokeIdType, + result SEQUENCE { + operationCode OPERATION, + parameter ANY DEFINED BY operationCode + } OPTIONAL +} + +-- ANY is filled by the single ASN.1 data type following the keyword RESULT in the type definition +-- of a particular operation. + +ReturnError ::= SEQUENCE { + invokeID InvokeIdType, + errorCode ERROR, + parameter ANY DEFINED BY errorCode OPTIONAL } + +-- ANY is filled by the single ASN.1 data type following the keyword PARAMETER in the type +-- definition +-- of a particular error. + +Reject ::= SEQUENCE { + invokeID CHOICE { + derivable InvokeIdType, + not-derivable NULL }, + problem CHOICE { + generalProblem [0] IMPLICIT GeneralProblem, + invokeProblem [1] IMPLICIT InvokeProblem, + returnResultProblem [2] IMPLICIT ReturnResultProblem, + returnErrorProblem [3] IMPLICIT ReturnErrorProblem } } + +InvokeIdType ::= INTEGER (-128..127) + +``` + +### 8.1.1 Operation Code + +Each Operation is assigned an Operation Code to identify it. The Operation Codes for the different Operations are defined in subclause 9.2. + +### 8.1.2 Error Code + +Each Error is assigned a value (Error Code) to identify it. The Error Codes for the different Errors are defined in subclause 10.3. + +### 8.1.3 Problem Code + +The Problem Code consists of one of the four elements: General Problem, Invoke Problem, Return Result Problem or Return Error Problem. ASN.1 definitions are presented below. + +``` +-- PROBLEMS + +GeneralProblem ::= INTEGER { + unrecognizedComponent (0), + mistypedComponent (1), + badlyStructuredComponent (2) } + +InvokeProblem ::= INTEGER { + duplicateInvokeID (0), + unrecognizedOperation (1), + mistypedParameter (2), + resourceLimitation (3), + initiatingRelease (4), + unrecognizedLinkedID (5), + linkedResponseUnexpected (6), + unexpectedLinkedOperation (7) } + +ReturnResultProblem ::= INTEGER { + unrecognizedInvokeID (0), + returnResultUnexpected (1), + mistypedParameter (2) } + +ReturnErrorProblem ::= INTEGER { + unrecognizedInvokeID (0), + returnErrorUnexpected (1), + unrecognizedError (2), + unexpectedError (3), + mistypedParameter (4) } +``` + +# 9 LMU LCS Protocol operation specifications + +## 9.1 General + +This clause specifies the abstract syntax for the LMU LCS Protocol using the Abstract Syntax Notation One (ASN.1), defined in ITU-T Recommendation X.680. + +The encoding rules which are applicable to the defined abstract syntax are the Packet Encoding Rules for Abstract Syntax Notation One, defined in ITU-T Recommendation X.691. For each Location Service parameter which has to be transferred by a Location Service message, there is a PDU field (an ASN.1 NamedType) whose ASN.1 identifier has the same name as the corresponding parameter, except for the differences required by the ASN.1 notation (blanks between words are removed, the first letter of the first word is lower-case and the first letter of the following words are capitalized (e.g. "bearer service" is mapped to "bearerService")). In addition some words may be abbreviated as follows: + +- lmu location measurement unit; +- lcs location services. + +The ASN.1 data type which follows the keywords ARGUMENT "PARAMETER" or "RESULT" (for OPERATION and ERROR) is always optional from a syntactic point of view. However, except specific mention, it has to be considered as mandatory from a semantic point of view. When in an invoke component, a mandatory element is missing in any component or inner data structure, a reject component is returned with the problem code "Mistyped Parameter". When an optional element is missing in an invoke component or in an inner data structure while it is required by the context, an error component is returned; the associated type of error is "DataMissing". + +In case an element is defined as mandatory in the protocol description (including imports from 3GPP TS 29.002), but is not present according to the service description (stage 1 to stage 3), the ASN.1 protocol description takes precedence over the diagrams in the 3GPP TS 24.08x and 3GPP TS 24.09x-series of technical specifications. + +When possible operations and errors are imported from 3GPP TS 29.002. + +Timer values for operations which require timers are shown as ASN.1 comments. + +Ellipsis Notation shall be used in the same way as described in 3GPP TS 29.002 and shall be supported on the radio interface by the LMU and the network for all operations defined in the present document including those imported from 3GPP TS 29.002. + +## 9.2 Operation types + +Table 9.2 summarizes the operations defined for LMU LCS Protocol in the present document, and shows which of these operations are Radio Interface Timing (RIT) related and general LMU procedures related. In this ASN.1 module, ASN.1/88 defined in ITU-T Recommendation X.680 (ASN.1 1997) is used. + +**Table 9.2: Relevance of location service operations** + +| Operation name | Direction | Response allowed | RIT | General LMU | +|------------------|-------------|-----------------------|-----|-------------| +| StartRIT | SMLC -> LMU | ReturnResult (empty). | X | | +| ReportRIT | LMU -> SMLC | No | X | | +| StopRIT | SMLC -> LMU | ReturnResult (empty). | X | | +| IndicateRITError | LMU -> SMLC | No | X | | +| StatusQuery | SMLC -> LMU | ReturnResult | | X | +| StatusUpdate | LMU -> SMLC | ReturnResult (empty) | | X | +| ResetRequest | SMLC -> LMU | ReturnResult (empty). | | X | +| OMMngrRequest | SMLC -> LMU | ReturnResult | | X | +| OMAgntRequest | LMU -> SMLC | ReturnResult | | X | + +The present document defines the following operations: + +- StartRIT. +- ReportRIT. +- StopRIT. +- IndicateRITError. +- StatusQuery. +- StatusUpdate. +- ResetRequest. +- OMMngrRequest. +- OMAgntRequest. + +-- LLP-Operations module defines the operations transparent to MSC + +LLP-Operations + +-- { LLP-Operations object identifier } + +DEFINITIONS ::= + +BEGIN + +IMPORTS + +OPERATION + +FROM TCAPMessages { + +ITU-T recommendation q 773 modules (2) messages (1) version2 (2) } + +SystemFailure, + +DataMissing, + +UnexpectedDataValue, + +FacilityNotSupported, + +UnknownSubscriber, + +FROM MAP-Errors { + +ITU-T identified-organization (4) etsi (0) mobileDomain (0) + +gsm-Network (1) modules (3) map-Errors (10) version4 (4) } + +UnDefinedError + +FROM LLP-Errors + +-- { } + +StartRITReq, + +StartRITRsp, + +ReportRITArg, + +StopRITReq, + +StopRITRsp, + +ErrorRITArg, + +PerformTOAReq, + +TOAResultRsp, + +StatusReq, + +StatusRsp, + +ResetReq, + +ResetRsp, + +StatusUpdateReq, + +StatusUpdateRsp + +FROM LLP-DataTypes { + +ITU-T identified-organization (4) etsi (0) mobileDomain (0) + +gsm-Network (1) modules (3) map-LCS-DataTypes (n) version4 (4) } + +OMMngrReq, + +OMMngrRsp, + +OMAgntReq, + +OMAgntRsp, + +NACKCauses + +FROM LLP-OM-Protocol --{ LLP-OM-Protocol Object identifier }-- + +; + +-- OPERATION definitions based on macro notation + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 StartRIT ::= OPERATION      -- identifier StartRIT-Measurement   ARGUMENT     startRITReq      StartRITReq   RESULT     startRITRsp      StartRITRsp   ERROR {      SystemFailure,     DataMissing,     UnexpectedDataValue,     ResourcesNotAvailable,     UnDefinedError   }
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------------| +| 
 ReportRIT ::= OPERATION      -- identifier ReportRIT-Measurement   ARGUMENT     reportRITArg      ReportRITArg
| +|-----------------------------------------------------------------------------------------------------------------------------| + +``` +StopRIT::= OPERATION -- identifier StopRIT-Measurement + ARGUMENT + stopRITReq StopRITReq + RESULT + StopRITRsp StopRITRsp +``` + +``` +IndicateRITError ::= OPERATION + ARGUMENT + errorRITArg ErrorRITArg +``` + +``` +PerformTOA::= OPERATION -- identifier PerformTOA-Measurment + ARGUMENT + performTOAReq PerformTOAReq + RESULT + toaResultRsp TOAResultRsp + ERROR { + SystemFailure, + DataMissing, + UnexpectedDataValue, + ResourcesNotAvailable, + UnDefinedError + } +``` + +``` +StatusQuery::= OPERATION + ARGUMENT + statusReq StatusReq + RESULT + statusRsp StatusRsp + ERROR { + } +``` + +``` +ResetRequest::= OPERATION + ARGUMENT + resetReq ResetReq + RESULT + resetRsp ResetRsp + ERROR { + SystemFailure, + UnDefinedError + } +``` + +``` +OMMngrRequest ::= OPERATION -- defined in LLP-OM, 52.071 + ARGUMENT + oMMngrReq OMMngrReq + RESULT + oMMngrRsp OMMngrRsp + ERROR + { + NACKCauses + } +``` + +``` +OMAgntRequest ::= OPERATION -- defined in LLP-OM, 52.071 + ARGUMENT + oMAgntReq OMAgntReq + RESULT + oMAgntRsp OMAgntRsp + ERROR + { + NACKCauses + } +``` + +``` +StatusUpdate ::= OPERATION -- identifier Status Update + ARGUMENT + statusUpdateReq StatusUpdateReq + RESULT + statusUpdateRsp StatusUpdateRsp + ERROR { + SystemFailure, + DataMissing, + UnexpectedDataValue, + ResourceNotAvailable, + UnDefinedError + } +``` + +END + +### 9.2.1 Operation types description + +For each operation type this subclause provides a brief prose description. + +#### 9.2.1.1 StartRIT (network --> LMU) + +This operation type is invoked by the network to request RIT measurement information from an LMU. + +#### 9.2.1.2 ReportRIT (LMU --> network) + +This operation type is invoked by an LMU to report to the network RIT measurement information. This operation is used to report periodical measurements. + +#### 9.2.1.3 StopRIT (network --> LMU) + +This operation type is invoked by the network to request an LMU to stop on-going RIT measurements and reporting. + +#### 9.2.1.4 IndicateRITError (LMU --> network) + +This operation type is invoked by an LMU to indicate error situations. + +#### 9.2.1.5 (void) + +#### 9.2.1.6 StatusQuery (network --> LMU) + +This operation type is invoked by the network to request status an LMU The status is returned using the return result component of the operation. + +#### 9.2.1.7 StatusUpdate (LMU --> network) + +This operation type is invoked by an LMU to report status of LMU, e.g. after reset or periodically. + +#### 9.2.1.8 ResetRequest (network --> LMU) + +This operation type is invoked by the network to reset an LMU. + +#### 9.2.1.9 OMMngrRequest (network --> LMU) + +This operation type is invoked by the network to request a specific O&M activity to LMU as defined in 3GPP TS 52.071. + +#### 9.2.1.10 OMAgentRequest (LMU --> network) + +This operation type is invoked by the LMU to report an O&M event to Network or asking for reporting O&M information from Network as defined in 3GPP TS 52.071. + +## 10.3 Error types + +### 10.3.1 Error types ASN.1 specification + +The following ASN.1 module provides an ASN.1 specification of errors. Errors from MAP are imported in the LCS-Protocol module in subclause 9.2. In this ASN.1 module, ASN.1/88 defined in ITU-T Recommendation X.680 recommendations (ASN.1 1997) is used. + +``` +LLP-Errors +-- { LLP-Errors object identifier } + +DEFINITIONS ::= +BEGIN +``` + +``` +IMPORTS +``` + +``` +ERROR FROM +``` + +``` +TCAPMessages FROM { +``` + +``` + ITU-T recommendation q 773 modules (2) messages (1) version2 (2) } +``` + +``` +; +``` + +``` +-- The MAP errors +``` + +``` +-- error types definition +``` + +``` +UnDefinedError ::=ERROR +``` + +``` +END +``` + +### 10.3.2 Error types description + +For each error type this subclause provides a brief prose description. + +10.3.2.1 (void) + +10.3.2.2 (void) + +10.3.2.3 (void) + +10.3.2.4 SystemFailure + +This error is returned by the LMU or the network, when it cannot perform an operation because of a failure. + +10.3.2.5 DataMissing + +This error is returned by the network or the LMU when an optional parameter is missing in an invoke component or an inner data structure, while it is required by the context of the request. + +10.3.2.6 UnexpectedDataValue + +This error is returned by the network or the LMU when it receives a parameter with an unexpected value, without type violation. + +10.3.2.7 ResourcesNotAvailable + +This error is returned by the network or the LMU if temporarily there are no resources. + +10.3.2.9 UnDefinedError + +This error is returned by the LMU or the network when any other error type is not applicable. + +## 10.4 Operations and errors implementation + +For the actual implementation of location services, operations and errors have to be defined by value. The following ASN.1 module, imports operation types from the ASN.1 module described in subclause 9.2 and operation and error types from MAP. It defines operations by allocating operations and errors a local value. For the involved operations and errors the same local values as in MAP are allocated. In this ASN.1 module, ASN.1/88 defined in ITU-T Recommendation X.680 (ASN.1 1997) is used. + +``` +LLP-Protocol +``` + +``` +-- { LLP-Protocol object identifier } +``` + +``` +DEFINITIONS ::= +``` + +``` +BEGIN +``` + +``` +IMPORTS +``` + +``` +SystemFailure, + DataMissing, + UnexpectedDataValue, +``` + +----- + +----- + +``` + + FacilityNotSupported, + UnknownSubscriber, +FROM MAP-Errors { + ccitt identified-organization (4) etsi (0) mobileDomain (0) + gsm-Network (1) modules (3) map-Errors (10) version4 (4)} + + UnDefinedError +FROM LLP-Errors +-- { LLP-Errors object identifier } + +StartRIT, + ReportRIT, + StopRIT, +IndicateRITError, + PerformTOA, + StatusQuery, + ResetRequest, + OMRequest, + OMReport, + StatusUpdate +FROM -LLP-Operations +-- { LLP-Operations object identifier } +-- allocate local values for errors + +systemFailure SystemFailure ::= localValue 10 +dataMissing DataMissing ::= localValue 11 +unexpectedDataValue UnexpectedDataValue ::= localValue 12 +facilityNotSupported FacilityNotSupported ::= localValue 13 +unknownSubscriber UnknownSubscriber ::= localValue 14 +unDefinedError UnDefinedError ::= localValue 50 + +startRIT StartRIT ::= localValue 10 +reportRIT ReportRIT ::= localValue 11 +stopRIT StopRIT ::= localValue 12 +indicateRITError IndicateRITError ::= localValue 13 +performTOA PerformTOA ::= localValue 20 +statusQuery statusQuery ::= localValue 30 +resetRequest ResetRequest ::= localValue 31 +omMngrRequest OMMngrRequest ::= LocalValue 32 +omAgntRequest OMAGntRequest ::= LocalValue 33 +StatusUpdate StatusUpdate ::= LocalValue 34 + +END + +``` + +# 11 LMU LCS Protocol (LLP) messages + +## 11.1 Messages, data types and identifiers + +### 11.1.1 General + +This clause defines the External Signal Info IE, that contains Signal Info string. Signal Info string contains the MLC-LMU messages defined by ASN.1 and coded by PER (ITU-T Recommendation X.691). In this ASN.1 module, ASN.1/94 defined in ITU-T Recommendation X.680 (ASN.1 1997) is used. + +### 11.1.2 ASN.1 data types + +``` + +LLP-DataTypes +-- { LLP-DataTypes object identifier } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + +ExtensionContainer + +FROM MAP-ExtensionDataTypes { + ccitt identified-organization (4) etsi (0) mobileDomain (0) + gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version4 (4)} +; + +``` + +``` + +StartRITReq ::= SEQUENCE { + rit-MeasurementType RIT-MeasurementType, + rit-ReportingType RIT-ReportingType, + rit-Environment RIT-Environment, + rit-NeighborNumber RIT-NeighborNumber, + rit-NeighborType RIT-NeighborType, + rit-CIMethod CIMethod, + rit-BTSInfo RIT-BTSInfo OPTIONAL, + extensionContainer ExtensionContainer OPTIONAL, + ... +} +StartRITRsp ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} +StopRITReq ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} +StopRITRsp ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} +ReportRITArg ::= SEQUENCE { + rit-ReferenceIDInfo RIT-ReferenceIDInfo, + rit-ResponseInfo SeqOfRIT-ResponseInfo, + extensionContainer ExtensionContainer OPTIONAL, + ... +} +StatusReq ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} +StatusRsp ::= SEQUENCE { + statusTime StatusTime, + rit-Status RIT-Status, + toa-Status TOA-Status, + omStatus OMStatus, + extensionContainer ExtensionContainer OPTIONAL, + ... +} +ErrorRITArg ::= SEQUENCE { + rit-ErrorType RIT-ErrorType, + rit-ErrorReason RIT-ErrorReason, + extensionContainer ExtensionContainer OPTIONAL, + ... +} +PerformTOA ::= SEQUENCE { + toa-MeasurementDeviceInfo TOA-MeasurementDeviceInfo, + toa-ChannelDescr TOA-ChannelDescr, + toa-SignalDescr TOA-SignalDescr, + toa-TimingDescr TOA-TimingDescr, + toa-MeasurementOpt TOA-MeasurementOpt OPTIONAL, + extensionContainer ExtensionContainer OPTIONAL, + ... +} +TOAResultRsp ::= SEQUENCE { + toa-TimingReferenceInfo TOA-TimingReferenceInfo, + toa-Measurements TOA-MeasurementInfo, + extensionContainer ExtensionContainer OPTIONAL, + ... +} +StatusUpdateReq ::= SEQUENCE { + statusReason StatusReason, + statusTime StatusTime, +} + +``` + +----- + +----- + +``` + + ritStatus RIT-Status, + toaStatus TOA-Status, + omStatus OMStatus, + extensionContainer ExtensionContainer OPTIONAL, + ... + } + + StatusUpdateRsp ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... + } + + ResetReq ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... + } + + ResetRsp ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... + } + + -- DATA TYPES DEFINITION + + -- RIT measurement Type information + RIT-MeasurementType ::= INTEGER { + atdMeasure (0), + atdOrOtdMeasure (1), + rtdMeasure (2) + } (0..7) + + -- RIT Reporting Type information + RIT-ReportingType ::= SEQUENCE { + rit-ReportingPeriodInfo RIT-ReportingPeriodInfo OPTIONAL, + rit-ChangeLimit INTEGER (1..255) OPTIONAL, + + rit-DeviationLimit INTEGER (1..255) OPTIONAL, + rit-MonitorPeriod INTEGER (1..64) OPTIONAL + } + + RIT-ReportingPeriodInfo ::= SEQUENCE { + rit-ReportingPeriodFormat ENUMERATED { + tensOfSeconds (0), + tensOfMinutes (1) }, + rit-ReportingPeriod INTEGER (1..120) + } + + -- RIT Environment Information + RIT-Environment ::= INTEGER { + heavyMultiPathAndNLOS (0), + -- bad urban or urban heavy multipath and NLOS conditions + lightMultiPathAndLOS (1), + -- suburban or rural light multipath and LOS conditions + mixedEnvironment (2) + -- not defined or mixed environment + } (0..7) + + RIT-NeighborNumber ::= INTEGER (0..15) + + RIT-NeighborType ::= INTEGER { + listedNeighbors (0), + listedAndSystemInfo2or5 (1), + systemInfoType2or5 (2), + allNeighbors (3) + } (0..7) + + CIMethod ::= INTEGER { + notCi (0), -- report ci and carrier instead of CI + ci (1) -- report CI if possible + } (0..3) + + -- element contains information of base stations + +``` + +``` + +-- to be measured +RIT-BTSInfo ::= SEQUENCE (SIZE(1..31)) OF RIT-BTSList -- list of btss + +RIT-BTSList ::= SEQUENCE { + rit-ListCi CI, + rit-TimeSlotScheme TimeSlotScheme, + rit-ListBSIC BSIC, + rit-ListBCCHCarrier BCCHCarrier +} + +CI ::= INTEGER (0..65535) + +TimeSlotScheme ::= INTEGER { + schemeUnknown (0), + equalLength (1), -- time slots are equal length + variousLength (2) -- the first time slot is 157b } (0..7) + +BSIC ::= INTEGER (0..63) + +BCCHCarrier ::= INTEGER (0..1023) + +RIT-ReferenceIDInfo ::= SEQUENCE { + rit-ReferenceLAC LAC, -- defined earlier + rit-ReferenceCI CI, -- defined earlier + rit-ReferenceFrameNbr FrameNumber, -- defined earlier + + -- If rit-ATReference is absent then there is not RIT AT reference value. + rit-ATReference RIT-ATReference OPTIONAL, + + rit-ReferenceTimeSlot TimeSlot, -- defined earlier + rit-ReferenceRXLevel RXLevel, -- defined earlier + + rit-ATDRDQualityRes INTEGER (0..3), -- defines the resolution for ATDRD values + rit-ATDRDChangeQualityRes INTEGER (0..3) -- defines the resolution for ATDRD change values +} + +RIT-ATReference ::= SEQUENCE { + rit-CommonClock CommonClock, + rit-ReferenceATValue ReferenceATValue, + -- This Quality information defines the quality of AT value + -- Resolution defines the resolution of Quality field as follows, + -- 0= 0.005 us, 1= 0.01 us, 2= 0.05 us + rit-RefATQuality SEQUENCE { + resolution INTEGER (0..3), + atQuality INTEGER (0..63) }, + + rit-ReferenceATChange INTEGER (-1000 .. 1000), + + -- This Quality information defines the quality of ATChange value + -- Resolution defines the resolution of Quality field as follows, + -- 0= 0.00005 ppm, 1= 0.0001 ppm, 2= 0.0005 + rit-RefATChangeQuality SEQUENCE { + resolution INTEGER (0..3), + atChangeQuality INTEGER (0..63) } +} + +-- Editor's note: ReferenceATValue was divided in two parts because 15 999 999 999 requires 34 bits. +-- In order to handle 34-bits values, IMU should support 64-bits calculation, which can cause +-- problems. +-- This solution can be handled with 32-bits and in addition it gives better resolution. +ReferenceATValue ::= SEQUENCE { + seconds INTEGER (0..59), + nseconds INTEGER (0..999999999) +} + +SeqOfRIT-ResponseInfo ::= SEQUENCE (SIZE (1..15)) OF RIT-ResponseInfo + +-- Measured RTD values from one neighbor +RIT-ResponseInfo ::= SEQUENCE { + rit-NeighborCellIDInfo RIT-CellIDInfo, + rit-NeighborTimeSlot TimeSlot, + rit-NeighborRxLevel RXLevel, + rit-NeighborFrameNumber FrameNumber OPTIONAL, +} + +``` + +----- + +----- + +``` + + rit-NeighborATDRD INTEGER (0..923200), + rit-NeighborATDRDQuality INTEGER (0..63), + rit-NeighborATDRDChange INTEGER (-2000..2000), + rit-NeighborATDRDChangeQuality INTEGER (0..63) + } + + RIT-CellIDInfo ::= CHOICE { + rit-NeighborCI CI, + rit-NeighborBTS RIT-NeighborBTS + } + + RIT-NeighborBTS ::= SEQUENCE { + rit-NeighborBSIC BSIC, + rit-NeighborBCCHCarrier BCCHCarrier + } + + FrameNumber ::= INTEGER (0..2715647) + + LAC ::= INTEGER (0..65535) + + CommonClock ::= INTEGER { + gpsClock (0), + glonass (1), + galileoClock (2), + qzssClock (3), + bdsClock (4) + } (0..7) + + TimeSlot ::= INTEGER (0..7) + + RXLevel ::= INTEGER (0..63) -- range -150 to -24 with 2dBm steps + + -- STATUS ELEMENTS + + StatusReason ::= ENUMERATED { + powerUp (0), -- no knowledge about previous states + unsucSWReset (1), -- unsuccessful recovery + sucSWReset (2), -- successful recovery + unknownError (3), -- unknown selfdiagnosis error + unrelTBError (4), -- unreliable timebase error + periodicReport (5), -- periodic status report + ... + } + + StatusTime ::= SEQUENCE { + referenceLAC LAC, -- defined earlier + referenceCI CI, -- defined earlier + referenceFrameNumber FrameNumber -- defined earlier + } + + RIT-Status ::= INTEGER (0..63) -- defines the number of RIT-Jobs + + TOA-Status ::= INTEGER (0..63) -- defines the number of TOA-Jobs + + OMStatus ::= INTEGER (0..63) -- defines the number of OM-Jobs + + -- ERROR RIT ELEMENTS + + RIT-ErrorType ::= INTEGER { + permanent (0), + temporary (1) + } (0..3) + + RIT-ErrorReason ::= INTEGER { + noNeighbors (0), + noReferenceClock (1), + notSupportedType (2), + undefinedError (3) + } (0..15) + + -- TOA DEFINITIONS + + -- MEASUREMENTDEVICE INFORMATION + TOA-MeasurementDeviceInfo ::= SEQUENCE + +``` + +``` + +-- A.5 + +(SIZE(1..6)) OF TOA-LMUMeasurementDevice -- list of measurement devices + +TOA-LMUMeasurementDevice ::= INTEGER (0..5) + +-- CHANNEL DESCRIPTION +TOA-ChannelDescr ::= SEQUENCE { + toa-FrequencyListType TOA-FrequencyListType, + toa-hopping TOA-Hopping OPTIONAL, + toa-channelType TOA-ChannelType, + toa-numberOfBursts TOA-NumberOfBurst +} + +TOA-FrequencyListType ::= CHOICE { + frequencyListOnly FrequencyListOnly, + frequencyListAndIndex FrequencyListAndIndex, + frequencyIndexOnly FrequencyIndexOnly +} + +FrequencyListOnly ::= SEQUENCE (SIZE(1..64)) OF TOA-ARFCNumber -- list of channels + +FrequencyListAndIndex ::= SEQUENCE { + toa-arfcnList TOA-ARFCList, + -- list of channels + frequencyIndex FrequencyIndex +} + +TOA-ARFCList ::= SEQUENCE (SIZE(1..64)) OF TOA-ARFCNumber + +FrequencyIndexOnly ::= SEQUENCE { + frequencyIndex FrequencyIndex +} + +FrequencyIndex ::= INTEGER (0..31) + +TOA-ARFCNumber ::= BCCHCarrier -- defined earlier + +TOA-Hopping ::= SEQUENCE { + toa-maio MAIO, + toa-hsn HSN, + toa-MsframeNumber ModuloFrameNumber +} + +MAIO ::= INTEGER (0..63) -- Mobile Allocation Index Offset + +HSN ::= INTEGER (0..63) -- Hopping Sequence Number + +ModuloFrameNumber ::= INTEGER (0..84863) + +TOA-ChannelType ::= INTEGER { + tchf(0), + tchhscn0 (1), + tchhscn1 (2) +} (0..7) + +TOA-NumberOfBurst ::= INTEGER (0..7) + +-- SIGNAL DESCRIPTION +TOA-SignalDescr ::= SEQUENCE { + toa-BurstType TOA-BurstType +} + +TOA-BurstType ::= CHOICE { + toa-AccessBurst TOA-AccessBurst, -- access burst + toa-TSC TSC -- normal burst +} + +TOA-AccessBurst ::= SEQUENCE { + toa-HOReference HOReference, + toa-BSIC BSIC -- defined earlier +} + +HOReference ::= INTEGER (0..255) + +TSC ::= INTEGER (0..7) + +``` + +#### -- TIMING DESCRIPTION + +``` + +TOA-TimingDescr ::= SEQUENCE { + toa-TimeReference TOA-TimeReference, + toa-timeUncertainty TimeUncertainty +} + +TOA-TimeReference ::= CHOICE { + toa-gpsTime TOA-GPSTime, + toa-gsmStartTime TOA-GSMStartTime +} + +TOA-GPSTime ::= SEQUENCE { + toa-GPSStartTime GPSStartTime, + toa-GPSSV GPSSV +} + +GPSStartTime ::= INTEGER (0..14999999) -- unit is microseconds + +GPSSV ::= INTEGER (0..31) + +TOA-GSMStartTime ::= SEQUENCE { + toa-arfcn BCCHCarrier, -- defined earlier + toa-bsic BSIC, -- defined earlier + toa-GSMStartTime GSMTime +} + +GSMTime ::= SEQUENCE { + toa-GSMTimeFrameNumber GSMTimeFrameNumber, + toa-timeSlot TimeSlot, + toa-bitNumber BitNumber +} + +GSMTimeFrameNumber ::= INTEGER (0..42323) + +BitNumber ::= INTEGER (0..156) + +TimeUncertainty ::= INTEGER (0..15) + +``` + +#### -- MEASUREMENT OPTIONS + +``` + +TOA-MeasurementOpt ::= SEQUENCE { + toa-LMUMethod TOA-Method, + toa-Environment TOA-Environment, + toa-MeasurementType TOA-MeasurementType +} + +TOA-Method ::= INTEGER (0..7) + +TOA-Environment ::= INTEGER { + heavyMpathAndNLOS (0), + lightMpathAndLOS (1), + mixed (2) +} (0..7) + +TOA-MeasurementType ::= INTEGER { + reportTOA-only (0), + reportAOA-only (1), + reportTOAandAOA (2) +} (0..3) + +``` + +#### -- TIMING INFO + +``` + +TOA-TimingReferenceInfo ::= CHOICE { + toa-GPSTimeInfo NULL, + toa-GSMTimeInfo TOA-GSMTimeInfo +} + +TOA-GSMTimeInfo ::= SEQUENCE { + toa-bcch BCCHCarrier, -- defined earlier + toa-bsic BSIC -- defined earlier +} + +-- THE ACTUAL TOA MEASUREMENTS + +``` + +``` + +TOA-MeasurementInfo ::= SEQUENCE(SIZE(1..6)) OF TOA-Measurements + -- list of measurementDevices + +TOA-Measurements ::= SEQUENCE { + toa-MeasurementDeviceID MeasurementDeviceID, + toa-AddMeasurementInfo TOA-AddMeasurementInfo, + toa-measuredPeakList TOA-MeasuredPeakList +} + +-- MEASUREMENT DEVICE ID IE + +MeasurementDeviceID ::= INTEGER (0..5) + +-- MEASUREMENT INFO IE IN RESULT MESSAGE + +TOA-AddMeasurementInfo ::= SEQUENCE { + toa-Method TOA-Method, -- defined earlier + toa-Diversity TOA-Diversity, + toa-NumberOfBurst TOA-NumberOfBurst, -- defined earlier + toa-AOA TOA-AOA OPTIONAL, + toa-AOAUncertainty TOA-AOAUncertainty OPTIONAL +} + +TOA-Diversity ::= INTEGER { + noDiversity (0), + diversity (1) +} (0..3) + +TOA-AOA ::= INTEGER (0..3599) + +TOA-AOAUncertainty ::= INTEGER (0..31) + +-- PEAKS LIST OF MEASURED TOAs + +TOA-MeasuredPeakList ::= SEQUENCE (SIZE(0..4)) OF TOA-MeasuredPeaks + -- list of peaks + +-- MEASURED TOA IE + +TOA-MeasuredPeaks ::= SEQUENCE { + toa-MeasuredTOA MeasuredTOA, + toa-QualityInfo TOA-QualityInfo +} + +MeasuredTOA ::= INTEGER (-131072..131071) + -- the absolute TOA value + +TOA-QualityInfo ::= SEQUENCE { + toa-Uncertainty TOA-Uncertainty OPTIONAL, + snrEstimate SNREstimate OPTIONAL, + toaSignalStrength TOASignalStrength OPTIONAL +} + +TOA-Uncertainty ::= INTEGER (0..63) + -- the uncertainty of the TOA estimate + +SNREstimate ::= INTEGER (-30..33) + -- the estimated value for Signal Noise Radio + +TOASignalStrength ::= INTEGER (0..63) + -- range -150 to -24 with 2dBm steps + +END + +-- The definition below will be imported from MAP specification. +-- +-- +-- MAP-ExtensionDataTypes { +-- ccitt identified-organization (4) etsi (0) mobileDomain (0) +-- gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version4 (4)} +-- +-- DEFINITIONS +-- +-- IMPLICIT TAGS + +``` + +``` + +-- +-- ::= +-- +-- BEGIN +-- +-- EXPORTS +-- +-- PrivateExtension, +-- ExtensionContainer; +-- +-- +-- MAP-EXTENSION ::= CLASS { +-- &ExtensionType OPTIONAL, +-- &extensionId OBJECT IDENTIFIER } +-- -- The length of the Object Identifier shall not exceed 16 octets and the +-- -- number of components of the Object Identifier shall not exceed 16 +-- +-- +-- data types +-- +-- ExtensionContainer ::= SEQUENCE { +-- privateExtensionList [0]PrivateExtensionList OPTIONAL, +-- pcs-Extensions [1]PCS-Extensions OPTIONAL, +-- ...} +-- +-- PrivateExtensionList ::= SEQUENCE SIZE (1..maxNumOfPrivateExtensions) OF +-- PrivateExtension +-- +-- PrivateExtension ::= SEQUENCE { +-- extId MAP-EXTENSION.&extensionId +-- ({ExtensionSet}), +-- +-- extType MAP-EXTENSION.&ExtensionType +-- ({ExtensionSet}{@extId}) OPTIONAL} +-- +-- maxNumOfPrivateExtensions INTEGER ::= 10 +-- +-- ExtensionSet MAP-EXTENSION ::= +-- { ... +-- -- ExtensionSet is the set of all defined private extensions +-- } +-- +-- Unsupported private extensions shall be discarded if received. +-- +-- +-- PCS-Extensions ::= SEQUENCE { +-- ...} +-- +-- END + +``` + +### 11.1.3 Identifiers definition + +In the informative annexes the contents of the identifiers used in operation and error types description are further discussed. + +# Annex A (informative): RIT messages + +## A.1 Introduction + +This annex describes the contents of Radio Interface Timing (RIT) related messages. + +## A.2 Messages + +The messages below are considered to be transported between the SMLC and the LMU. + +### A.2.1 RIT Measurement Request Message + +The RIT Measurement Request is a message from the SMLC to the LMU. As a response to it the LMU performs Real Time Difference (RTD) or Absolute Time Difference (ATD) measurements. It contains the following information elements. + +**Table A.2.1: RIT Measurement Request message content** + +| Information element | Type/Reference | Presence | +|--------------------------|------------------------------------|----------| +| Message Type | Message Type A.2.1.1.1 | M | +| Measurement Instructions | Measurement Instructions A.2.1.1.2 | M | +| BTS List | BTS List A.2.1.1.3 | C | + +#### A.2.1.1 RIT Measurement Request Message Information Elements + +##### A.2.1.1.1 Message Type IE + +This IE contains the type of the message. This IE is mandatory. + +##### A.2.1.1.2 Measurement Instructions IE + +The purpose of the Measurement Instructions IE is to inform the LMU about the measurement type (RTD/ATD), measurement result reporting rate, and tell which BTSs should be measured. This IE is mandatory, and it contains the following fields: + +###### Measurement Type + +This field indicates whether AT of reference BTS is required. + +'0': AT of reference BTS should be reported. If AT of reference BTS can not be measured, no ATD/RTD measurements are reported, but RIT Error IE is sent instead. + +'1': AT of reference BTS should be reported . If AT of reference BTS can not be measured, ATD/RTD measurements are reported anyhow. + +'2': ATD/RTD measurements timestamped with frame number of the reference BTS should be performed. + +###### Reporting Period Format + +This field describes the units of the Reporting Period field. This field is optional. If this field is included, RIT Measurement Responses shall be send with the period indicated in this and Reporting Period fields. + +'0': Reporting Period is told in tens of seconds. + +'1': Reporting Period is in tens of minutes. + +###### Reporting Period + +This field describes the value for the reporting period, i.e. the required time period between the RIT Measurement Response messages. Its units and multiplication factor are defined in the Reporting Period Format field. This field is conditional and included only if the Reporting Period Format is included. + +Range: 1-120. + +###### Change Limit + +This field indicates the limit for the change of AT or ATD /RTD values in units of 0.02 micro-seconds. If any AT or ATD/RTD value has changed more than the value in this field since the last RIT Measurement Response, a new RIT Measurement Response message is sent. This field is optional. If this field is included, RIT Measurement Responses shall be send when some RIT value has changed more than this limit. + +Range: 1-255. + +###### Deviation Limit + +This field indicates the limit for the deviation of the AT or ATD/RTD values. If any time the predicted AT or ATD/RTD value (based on reported AT or ATD/RTD values and changes in the last RIT Measurement Response) has deviated more than the value in this field compared to the current measurement result, a new RIT Measurement Response message is sent. This field is optional. If this field is included, RIT Measurement Responses shall be send when the first deviation of some RIT value is more than this limit. The values are in units of 0.02 micro-seconds. + +Range: 1-255. + +NOTE: Predicted AT or ATD/RTD value means the value that is calculated (extrapolated) based on AT or ATD/RTD value and AT or ATD/RTD Change value in last RIT Measurement Response message. + +###### Monitor Period + +This field indicates the requested time period for monitoring the time derivative of AT or ATD/RTD values, i.e. on how long monitor period the reported AT or ATD/RTD change is based. The value is in tens of seconds. This field is optional. + +Range: 1- 64. + +###### Environment Characterization + +Environment Characterization field gives a LMU information about expected multipath and NLOS in the area. + +'0': possibly heavy multipath and NLOS conditions (e.g. bad urban or urban). + +'1': no or light multipath and usually LOS conditions (e.g. suburban or rural). + +'2': not defined or mixed environment. + +'3': reserved. + +'4': reserved (i.e. several values should be reserved). + +###### Neighbor Number + +This field indicates the maximum number of neighbor BTSs that the LMU should try to report. + +Range: 0-15. + +###### Neighbor Type + +This field indicates which neighbor BTSs are used for RIT measurements. If the value of the Neighbor Number field is lower than the total number of BTSs in the required list, then the BTS are selected in the order of the list. + +'0': Neighbor BTSs listed in the BTS List IE are used for RIT measurements in the order of the list. + +'1': If possible, neighbor BTSs listed in the BTS List IE are used, otherwise neighbors received in SYSTEM INFORMATION 2 or 5 message are used in the order of received signal strength. + +'2': Neighbor BTSs indicated in SYSTEM INFORMATION TYPE 2 or 5 are used for RIT measurements (i.e. this is normal operation) in the order of received signal strength. + +'3': All neighbor BTSs that can be received (i.e. reported BTSs are not limited to BTSs listed in SYSTEM INFORMATION TYPE 2 or 5 or BTS List IE). Support of this option in LMU is optional. + +###### CellIdMethod + +CellIdMethod field indicates whether CI or BSIC and BCCH carrier is used to identify neighbor BTSs in RIT Measurement Responses. + +'0' = BSIC and BCCH carrier are used to identify the cell, even if CI is available. + +'1' = CI is used to identify the neighbor cell, if it is available, otherwise BSIC and BCCH carrier are used. + +##### A.2.1.1.3 BTS List IE + +This information element indicates neighbor BTSs that are used for RIT measurements. This IE is conditional. If Neighbor Type field in the Measurement Instructions IE is '0' or '1' this field must be included. The first BTS on the list is the reference BTS that should be used as reference when reporting the RTD or AT values. If this reference BTS is not available, the LMU can select the used reference BTS based on signal strength. + +This IE contains the following fields. + +###### Number of BTSs + +This field indicates, how many BTSs are included in this IE. + +Range: 1 to 31. + +The following fields are repeated the number of times included in Number of BTSs field. + +###### CI + +This field indicates the Cell Identity of the particular BTS. The purpose of the Cell Identity value is to identify a BTS within a location area. + +Range: 0 - 65535. + +NOTE: Here is assumed that when LMU starts to make measurements, it firsts goes to the requested frequencies, and starts to decode BSICs and CIs from those specific frequencies. Because of this procedure the risk that there would be two BTSs with same CIs and same Channel numbers is minimal (i.e. there is no need to transmit LAC). + +###### Time Slot Scheme + +The Time Slot Scheme field indicates what kind of transmission scheme the particular BTS is using. If the LMU measures signals from BTSs from other time slots than 0 or 4, and it is informed about the burst length schemes used by BTSs, then it can compensate for the possible error. (This is necessary if the LMU averages bursts from different time slots, and the BTS uses varying lengths of bursts.) + +'0' = the burst scheme is unknown (The time slot should remain the same). + +'1' = all time slots are 156.25 bits long. + +'2' = time slots 0 and 4 are 157 bits long and other time slots are 156 bits long. + +###### BSIC + +This field indicates the BSIC (Base Station Identity Code) of the particular BTS. + +Range: 0 - 63. + +###### BCCH Carrier + +This field indicates the absolute RF channel number of the particular BTS. + +Range: 0 - 1023. + +### A.2.2 RIT Measurement Response Message + +The RIT Measurement Response is a message from the LMU to the SMLC. It is the response to the RIT Measurement Request. It contains the following information elements. + +**Table A.2.2: RIT Measurement Response message content** + +| Information element | Type/Reference | Presence | +|---------------------|---------------------------|----------| +| Message Type | Message Type A.2.2.1.1 | M | +| RIT Measurement | RIT Measurement A.2.2.1.2 | M | + +#### A.2.2.1 RIT Measurement Response Message Information Elements + +##### A.2.2.1.1 Message type IE + +This IE contains the type of the message. This IE is mandatory. + +##### A.2.2.1.2 RIT Measurement IE + +This IE includes the required RIT measurements. The length of this IE depends on the number of measured neighbor BTSs. This IE is mandatory. + +###### Reference LAC + +This field indicates the Location Area Code of the reference BTS. The purpose of the Location Area Code is to identify a location area. + +Range: 0 - 65535. + +###### Reference CI + +This field indicates the Cell Identity value of the reference BTS. The purpose of the Cell Identity value is to identify a cell within a location area. + +Range: 0 - 65535. + +###### Reference Frame Number + +This field indicates the frame number of the last measured burst from the reference BTS. + +Range: 0 - 2715647. + +###### Response Type + +This field indicates whether AT of reference BTS is reported or not. + +'0': AT of reference BTS is not reported. + +'1': AT of reference BTS is reported. + +###### Common Clock + +This field indicates the type of the common reference clock for AT measurement. This field is included only if the Response Type field is '1'. + +'0': GPS clock is used. + +'1': glonass clock is used + +'2': Galileo clock is used + +'3': QZSS clock is used + +'4': BDS clock is used + +'5' to '7' : Reserved for future use (e.g. Synchronized atomic clocks). + +###### Reference AT + +This field indicates the measured AT value for the serving BTS. It is the starting moment of a time slot. It is counted in two parts: seconds after last minute change, and nanoseconds after last second change. This field is included only if the Response Type field is '1'. + +Range: + +seconds: 0-59. + +nanoseconds: 0-999,999,999. + +###### Reference AT Quality Resolution + +Reference AT Quality Resolution field includes the resolution used in Reference AT Quality field. Encoding on 2 bits as follows. + +| | | +|------|----------------------| +| '00' | 0.005 micro seconds. | +| '01' | 0.01 micro seconds. | +| '10' | 0.05 micro seconds. | +| '11' | Reserved. | + +This field is included only if the Response Type field is '1'. + +###### Reference AT Quality + +Reference AT Quality field includes the quality of reported RIT measurement. This Reference AT Quality field can be e.g. used to evaluate the reliability of AT measurements in the SMLC. Reference AT quality is defined as + +$$\text{Reference AT Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported AT value};$$ + +where $x$ is the reported Reference AT value and $\mu = E[x]$ is its expectation value. The reporting resolution of Reference AT Quality is defined by Reference AT Quality resolution field. + +Range: 0 to 63. + +Value 63 means that Reference AT Quality is greater than or equal to $R \cdot 63$ , where $R$ is the resolution defined in Reference AT Quality Resolution field. + +This field is included only if the Response Type field is '1'. + +###### Reference AT Change + +This field indicates the first time derivative of the AT value for the reference BTS. This value is based on measurements made during Monitor Period, if the monitoring period is provided. Otherwise it is the best estimate of AT Change value at the time of last AT measurement. This field is conditional and included if Response Type field is '1'. The range is -0.05 ... 0.05 ppm and resolution is 0,00005 ppm. + +Range: -1000 ... 1000. + +###### Reference AT Change Quality Resolution + +Reference AT Change Quality Resolution field includes the resolution used in Reference AT Change Quality field. Encoding on 2 bits as follows. + +| | | +|------|--------------| +| '00' | 0.00005 ppm. | +| '01' | 0.0001 ppm. | +| '10' | 0.0005 ppm. | + +'11' Reserved. + +This field is conditional and included if the Response Type field is '1'. + +###### Reference AT Change Quality + +Reference AT Change Quality field includes the quality of reported Reference AT Change. This Reference AT Change Quality field can be e.g. used to evaluate the reliability of RIT measurements in the SMLC. Reference AT Change Quality is defined as. + +$$\text{Reference AT Change Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported AT Change value;}$$ + +where $x$ is the reported Reference AT Change and $\mu = E[x]$ is its expectation value. The reporting resolution of Reference AT Change Quality is defined by Reference AT Change Quality Resolution field. + +Range: 0 to 63. + +This field is conditional and included if the Response Type field is '1'. + +###### Reference Time Slot + +Reference Time Slot indicates the time slot relative to which the LMU reports the reference BTS measurements. This field is mandatory. + +Range: 0 to 7 + +NOTE: If the LMU does not know timeslot scheme, the LMU reports the used timeslot. The LMU can only report results based on one time slot (N) or two time slots (N and N+4). If the LMU knows timeslot scheme, the LMU can make measurements from several timeslots and reports that the used timeslot is zero (and makes correction). + +###### Reference RX Level + +RX Level field includes the received signal strength of the reference BTS. + +The RX Level is expressed in 2 dBm steps within the range -150 .. -24 dBm. + +Range: 0 .. 63. + +###### ATD/RTD Quality Resolution + +ATD/RTD Quality Resolution field includes the resolution used in ATD/RTD Quality field. Encoding on 2 bits as follows. + +'00' 0.005 micro seconds. + +'01' 0.01 micro seconds. + +'10' 0.05 micro seconds. + +'11' Reserved. + +This field is mandatory. + +###### ATD/RTD Change Quality Resolution + +ATD/RTD Change Quality Resolution field includes the resolution used in ATD/RTD Change Quality field. Encoding on 2 bits as follows. + +'00' 0.00005 ppm. + +'01' 0.0001 ppm. + +'10' 0.0005 ppm. + +'11' Reserved. + +This field is mandatory. + +###### Number of Measured Neighbors + +This field indicates the number of different neighbor BTSs. + +NOTE: If the LMU can not measure any neighbor BTSs, then this value is set to '0'. + +Range: 0 - 15 + +The following fields are repeated the number of times included in Number of Measured Neighbors field. + +###### CellIdType + +This field indicates is the identity method of the cell. + +'0' = Cell identity is told using BSIC and BCCH carrier. + +'1' = Cell identity is told using CI. + +###### Neighbor CI + +This field indicates the Cell Identity of the particular neighbor cell. The purpose of the Cell Identity value is to identify a cell within a location area. + +Neighbor CI field is a conditional field and it is included only if CellIdType is set '1' and CI value of the given cell is available. + +Range: 0 - 65535. + +###### Neighbor BSIC + +This field indicates the BSIC (Base Station Identity Code of the base station). + +BSIC field is conditional and it is included only if CellIdType is set '0'. + +Range: 0 - 63. + +###### Neighbor BCCH Carrier + +This field indicates the absolute RF channel number of the neighbor base station. BCCH carrier field is conditional and it is included only if CellIdType is set '0'. + +Range: 0 - 1023 + +###### Neighbor RX Level + +RX Level field includes the received signal strength on the neighbor BTS. + +The RX Level is expressed in 2 dBm steps within the range -150 .. -24 dBm. + +Range: 0 .. 63. + +###### Neighbor Frame Number + +This field indicates the calculated value of the neighbor BTS's frame that would have been received at the same time or immediately after as the last measured frame from the reference BTS. This field is optional. + +Range: 0 - 2715647 + +###### Neighbor Time Slot + +Neighbor Time Slot indicates the time slot relative to which the LMU reports the serving BTS measurements. This field is mandatory. + +Range: 0 to 7 + +NOTE: If the LMU does not know timeslot scheme, the LMU reports the used timeslot. The LMU can only report results based on one time slot (N) or two time slots (N and N+4). If the LMU knows timeslot scheme, the LMU can make measurements from several timeslots and reports that the used timeslot is zero (and makes correction). + +###### ATD/RTD Value + +This field indicates the measured ATD/RTD value between the receptions of signals from the reference and the neighbor BTS. This ATD/RTD value is the difference in reception of signal (the starting moment of time slot) from reference BTS compared to the signal (next starting moment of a time slot) from the neighbor BTS (i.e. this value is always positive). This field is mandatory. The reporting resolution of ATD/RTD value is 0.005 micro-seconds. + +Range: 0 ... 923200. + +NOTE: The reported ATD/RTD value may be based on some filtering or estimation algorithm. I.e. the reported value is not the last measurement result, it is the best estimate of real RTD value at the time of last measurement. + +###### ATD/RTD Quality + +ATD/RTD Quality field includes the quality of reported RIT measurement. This ATD/RTD Quality field can be e.g. used to evaluate the reliability of RIT measurements in the SMLC. ATD/RTD quality is defined as + +$$\text{ATD/RTD Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported ATD/RTD value;}$$ + +where $x$ is the reported ATD/RTD value and $\mu = E[x]$ is its expectation value. The reporting resolution of ATD/RTD Quality is defined by ATD/RTD Quality resolution field. + +Range: 0 to 63 + +This field is mandatory. + +###### ATD/RTD Change + +This field indicates the first time derivative of the ATD/RTD value between the receptions of signals from the reference and the neighbor BTS. This value is based on measurements made during Monitor Period, if the monitoring period is provided. Otherwise it is the best estimate of the ATD/RTD Change value at the time of last ATD/RTD measurement. The range is -0.1 ... 0.1 ppm and resolution is 0,00005 ppm. + +Range: -2000 ... 2000 + +###### ATD/RTD Change Quality + +ATD/RTD Change Quality field includes the quality of reported ATD/RTD Change. This ATD/RTD Change Quality field can be e.g. used to evaluate the reliability of RIT measurements in the SMLC. ATD/RTD Change Quality is defined as + +$$\text{ATD/RTD Change Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported ATD/RTD Change value;}$$ + +where $x$ is the reported ATD/RTD Change and $\mu = E[x]$ is its expectation value. The reporting resolution of ATD/RTD Change Quality is defined by ATD/RTD Change Quality resolution field. + +Range: 0 to 63 + +This field is mandatory. + +### A.2.3 RIT Measurement Stop Message + +The RIT Measurement Stop is a message from the SMLC to the LMU. It is sent when the SMLC wants the LMU to stop doing RIT measurements and reporting them. It contains the following information elements. + +**Table A.2.3: RIT Measurement Stop message content** + +| Information element | Type/Reference | Presence | +|---------------------|------------------------|----------| +| Message Type | Message Type A.2.3.1.1 | M | + +#### A.2.3.1 RIT Measurement Stop Message Information Elements + +##### A.2.3.1.1 Message type IE + +This IE contains the type of the message. This IE is mandatory. + +### A.2.4 RIT Measurement Error Message + +The RIT Measurement Error is a message from the LMU to the SMLC. It is sent any time when the LMU can not perform RIT measurements asked for in the RIT Measurement Request. This message can be returned in return result (after reception of measurement command) or as separate message (during periodic measurement). It contains the following information elements. + +**Table A.2.4: RIT Measurement Error message content** + +| Information element | Type/Reference | Presence | +|---------------------|--------------------------|----------| +| Message Type | Message Type A.2.4.1.1 | M | +| Error Type | RIT Error Type A.2.4.1.2 | M | +| RIT Error | RIT Error A.2.4.1.3 | M | + +#### A.2.4.1 RIT Measurement Error Message Information Elements + +##### A.2.4.1.1 Message type IE + +This IE contains the type of the message. This IE is mandatory. + +##### A.2.4.1.2 RIT Error Type IE + +This IE indicates whether the error is temporarily (e.g. GNSS receiver reset) or permanent errors. Permanent error requires actions in SMLC, temporarily error informs that LMU can not send results temporarily (but it is expected to recover without any actions from SMLC). + +'0' = Permanent error. + +'1' = Temporarily error. + +##### A.2.4.1.3 RIT Error IE + +The purpose of the RIT Error IE is to provide the indication of error and the reason for it, when the LMU can not report required RIT results. This IE is mandatory. This IE has the following fields. + +###### Error Reason + +This field indicates the reason for error. + +'0': There were no neighbor BTSs to be received. + +'1': No ATD measurements were possible, since the common reference clock was not available. + +'2': Requested type of measurements is not supported. + +'3': Undefined error. + +# --- Annex B (informative): (void) + +# Annex C (informative): Status Messages + +## C.1 Introduction + +This annex describes the contents of messages related to the status of an LMU. + +## C.2 Messages + +The messages below are considered to be transported between the SMLC and the LMU. + +### C.2.1 Status Query Message + +The Status Query is a message from the SMLC to the LMU. It contains the following information elements. + +**Table C.2.1: Status Query message content** + +| Information element | Type/Reference | Presence | +|---------------------|------------------------|----------| +| Message Type | Message Type C.2.1.1.1 | M | + +#### C.2.1.1 Status Query Message Information Elements + +##### C.2.1.1.1 Message Type IE + +This IE contains the type of the message. This IE is mandatory. + +### C.2.2 Status Query Result Message + +The Status Query Result is a message from the LMU to the SMLC. It contains the following information elements. + +**Table C.2.2: Status Query Result message content** + +| Information element | Type/Reference | Presence | +|---------------------------------------------------------------------------------------------------------|-------------------------------|----------| +| Message Type | Message Type 5.2.1.1 | M | +| Time | Time C.2.2.1.2 | M | +| RIT Status | RIT Status C.2.2.1.3 | M | +| Reserved | Reserved (see note) C.2.2.1.4 | M | +| O&M Status | O&M Status C.2.2.1.5 | M | +| NOTE: This value was allocated in an earlier phase of the protocol and shall not be used in the future. | | | + +#### C.2.2.1 Status Query Result Message Information Elements + +##### C.2.2.1.1 Message Type IE + +This IE contains the type of the message. This IE is mandatory. + +##### C.2.2.1.2 Time IE + +This IE contains the time stamp for this message. This IE is mandatory, and it contains the following fields: + +###### Reference LAC + +This field indicates the Location Area Code of the reference BTS. The purpose of the Location Area Code is to identify a location area. + +Range: 0 - 65535. + +###### Reference CI + +This field indicates the Cell Identity value of the reference BTS. The purpose of the Cell Identity value is to identify a cell within a location area. + +Range: 0 - 65535. + +###### Reference Frame Number + +This field indicates the frame number of the last measured burst from the reference BTS. + +Range: 0 - 2715647. + +##### C.2.2.1.3 RIT Status IE + +The purpose of the RIT Status IE is to inform the SMLC about the status of on-going RIT related activity. This IE is mandatory, and it contains the following fields: + +###### RIT Jobs + +This field indicates the number of on-going RIT related jobs, i.e. the number of neighbor BTSs that are tried to be measured. Notice that 0 means that no RIT related activity is on-going. + +Range: 0 - 63. + +##### C.2.2.1.4 Reserved IE + +This IE is reserved and the value is 0. + +Range: 0 - 63. + +##### C.2.2.1.5 O&M Status IE + +The purpose of the O&M Status IE is to inform the SMLC about the status of on-going O&M related activity. This IE is mandatory, and it contains the following fields: + +###### O&M Jobs + +This field indicates the number of on-going O&M related jobs. + +Range: 0 - 63. + +### C.2.3 Status Update Message + +The Status Update is a message from the LMU to the SMLC. It contains the following information elements. + +**Table C.2.3: Status Response message content** + +| Information element | Type/Reference | Presence | +|--------------------------|---------------------------------------------------------------------------------------------------|----------| +| Message Type | Message Type C.2.3.1.1 | M | +| Reason for Status Update | Reason for Status Update C.2.3.1.2 | M | +| Time | Time C.2.2.1.2 | M | +| RIT Status | RIT Status C.2.2.1.3 | M | +| Reserved | Reserved (see note) C.2.2.1.4 | M | +| O&M Status | O&M Status C.2.2.1.5 | M | +| NOTE: | This value was allocated in an earlier phase of the protocol and shall not be used in the future. | | + +#### C.2.3.1 Status Update Message Information Elements + +##### C.2.3.1.1 Message Type IE + +This IE contains the type of the message. This IE is mandatory. + +##### C.2.3.1.2 Reason for Status Update IE + +This IE contains the reason for sending this Status Update Message. This IE is mandatory, and it contains the following fields: + +###### Reason Code + +This field indicates Reason code for sending this Status Update Message. + +- '0': power up (no knowledge about previous states). +- '1': SW reset, unsuccessful recovery. +- '2': SW reset, successful recovery. +- '3': unknown selfdiagnosis error. +- '4': unreliable timebase error. +- '5': periodic status report, normal operation. + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-01 | | - | - | - | - | Version 13.0.0 based on version 12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44118/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Rel-16/44_series/44118/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a18aa1a58b9fb7eb264fb1c2d7eb5cec0108d2bc --- /dev/null +++ b/marked/Rel-16/44_series/44118/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9af596137a4dee7322931d922efc8d30b05f2584072292035e0c8c78ba7bbb3 +size 14464 diff --git a/marked/Rel-16/44_series/44118/070352b751dd0711b8ac6ddfa6df1d98_img.jpg b/marked/Rel-16/44_series/44118/070352b751dd0711b8ac6ddfa6df1d98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fb17487c4604812a3fc6bc23ee59483ef357601 --- /dev/null +++ b/marked/Rel-16/44_series/44118/070352b751dd0711b8ac6ddfa6df1d98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3075f456c6dbefadec27b47dde8be7b562d8bec3f8465b57fa95e728adea8c7 +size 18722 diff --git a/marked/Rel-16/44_series/44118/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg b/marked/Rel-16/44_series/44118/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76939d10509d6626796c0641e8674dc29c006591 --- /dev/null +++ b/marked/Rel-16/44_series/44118/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c65bc0ef88836d9a919dcc4fb4a00737179eee5a43950f600be4e8d13761f100 +size 12430 diff --git a/marked/Rel-16/44_series/44118/0de91e9b714369b312bf3ab1853301ac_img.jpg b/marked/Rel-16/44_series/44118/0de91e9b714369b312bf3ab1853301ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cc7871deb3951fa8f849e5eb1459b114416c34f --- /dev/null +++ b/marked/Rel-16/44_series/44118/0de91e9b714369b312bf3ab1853301ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a7a29c9e73043fa08c04f354c980032a2602cb87de4441298ac41f45660fc41 +size 13185 diff --git a/marked/Rel-16/44_series/44118/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/44_series/44118/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0a99b686e639f3739978863c88a4f08f78ae604 --- /dev/null +++ b/marked/Rel-16/44_series/44118/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95bd59d6a7b5ed40ecc34054b98d45d78d17bc41be0c0349362bad9344fc66da +size 17309 diff --git a/marked/Rel-16/44_series/44118/1274805226c5a1f8b875aea0296b9f0f_img.jpg b/marked/Rel-16/44_series/44118/1274805226c5a1f8b875aea0296b9f0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dfdaf193a0ba7f71af97f3c6a77808e3b6545f8 --- /dev/null +++ b/marked/Rel-16/44_series/44118/1274805226c5a1f8b875aea0296b9f0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b7bd29a5f2b4c99d5b3f6740bfc759fdee9ba03b15e56f86257b0ee7ef3eb71 +size 17700 diff --git a/marked/Rel-16/44_series/44118/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/44_series/44118/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..195b58257ab62c2e227734cadaeb4950726b5de8 --- /dev/null +++ b/marked/Rel-16/44_series/44118/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9ea248fafd0ee4a8bc29c099088830b366005d1e03ef224fdd9327965790da6 +size 86583 diff --git a/marked/Rel-16/44_series/44118/29997432244f81212ee1e6c94f308f1b_img.jpg b/marked/Rel-16/44_series/44118/29997432244f81212ee1e6c94f308f1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9dc43caa904f4782b2f1178df625cb9239293fa --- /dev/null +++ b/marked/Rel-16/44_series/44118/29997432244f81212ee1e6c94f308f1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58fc15cc590054d492663d00381154607b02e407ac52038d66ee53c962875f08 +size 14138 diff --git a/marked/Rel-16/44_series/44118/333992a0b3b7a9d826f72f7bf199221b_img.jpg b/marked/Rel-16/44_series/44118/333992a0b3b7a9d826f72f7bf199221b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0292d544054938b6cb700818bbe8912d289e4d2e --- /dev/null +++ b/marked/Rel-16/44_series/44118/333992a0b3b7a9d826f72f7bf199221b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8a5e39076f28af1d16af661543526377eebe8743705cf2dc60ccba68d576777 +size 19727 diff --git a/marked/Rel-16/44_series/44118/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-16/44_series/44118/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3250dc599f2efa89324a3cf335d8a6cb3f311a09 --- /dev/null +++ b/marked/Rel-16/44_series/44118/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35caffc09ba99c2a506671f83c8269bdac87235424525bb191286c18c69b326b +size 16193 diff --git a/marked/Rel-16/44_series/44118/41fa90d03d7195caa162c74d289817a4_img.jpg b/marked/Rel-16/44_series/44118/41fa90d03d7195caa162c74d289817a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f7aa1b0f33f74a4ca08ad98d4ed1676593efeda --- /dev/null +++ b/marked/Rel-16/44_series/44118/41fa90d03d7195caa162c74d289817a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb964178aab8bcd1d034293b6e4c775f0b9d8777167a8e836024af234217b84a +size 15065 diff --git a/marked/Rel-16/44_series/44118/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-16/44_series/44118/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..734c995a43ba5b66196a0335947aafad784f19fb --- /dev/null +++ b/marked/Rel-16/44_series/44118/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dab7a46f04654b6995145c01be8d494e995b9e4c6e709c0a2cdf808b0eaef699 +size 18651 diff --git a/marked/Rel-16/44_series/44118/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/marked/Rel-16/44_series/44118/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5022b75c81bbd8a19ed38d4f0cfd12e5f22da811 --- /dev/null +++ b/marked/Rel-16/44_series/44118/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee1d402ed9093857011f9a7d7ded1b07e694acc434c60b064e33794314ef0cd2 +size 80766 diff --git a/marked/Rel-16/44_series/44118/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/44_series/44118/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c7e5b4076cd9c6a6ce4a706766b84e0367016c5 --- /dev/null +++ b/marked/Rel-16/44_series/44118/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32d6d1630c39a747a5ef04ce3ade7656b047284de3beabf05e947c17f59b96b5 +size 22578 diff --git a/marked/Rel-16/44_series/44118/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-16/44_series/44118/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..199bcacf5675df1a8e93433504d0be68b8b9e82f --- /dev/null +++ b/marked/Rel-16/44_series/44118/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:988011637c79aa304bbca12d3b218e941596eda3765e8ded0cf0ef54975005c4 +size 18433 diff --git a/marked/Rel-16/44_series/44118/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/Rel-16/44_series/44118/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84b4cc6e348470f58684a87f08e52dc5acbaf97e --- /dev/null +++ b/marked/Rel-16/44_series/44118/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fc1b6f535382177df34bb6b335b92069df7d16cfa77916b2798cd5b1f73d883 +size 24626 diff --git a/marked/Rel-16/44_series/44118/5e75237ea72c3a124febac3534aed999_img.jpg b/marked/Rel-16/44_series/44118/5e75237ea72c3a124febac3534aed999_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa193d5f3e51f212f445bcdc40a6eca0ea58e177 --- /dev/null +++ b/marked/Rel-16/44_series/44118/5e75237ea72c3a124febac3534aed999_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf93c6bf930bae57e9c15a43954b4b4193694e763ee1d1b5bb4eaebb1497b80d +size 20282 diff --git a/marked/Rel-16/44_series/44118/6116b1a533010c170fc526ec513ba0b8_img.jpg b/marked/Rel-16/44_series/44118/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d46a11bf606c378b80f26f2f81d9269fbdd79d --- /dev/null +++ b/marked/Rel-16/44_series/44118/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5004c420d0a4c6e5ed50cd82030aa389a857beee1609903f99968b0ce6f168b +size 19449 diff --git a/marked/Rel-16/44_series/44118/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/44_series/44118/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acc96a66ed0c7c9dd499ec1a2151d8f2f64488a3 --- /dev/null +++ b/marked/Rel-16/44_series/44118/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a194c88426af1f9198a4ff95fecf44d73a2190fa33dd2d757ffa1ed7e2d8b98f +size 20840 diff --git a/marked/Rel-16/44_series/44118/869c547c11ac7e123c51aba22289f2cd_img.jpg b/marked/Rel-16/44_series/44118/869c547c11ac7e123c51aba22289f2cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b064d1bfe8507080cca843837f235c8396a667d9 --- /dev/null +++ b/marked/Rel-16/44_series/44118/869c547c11ac7e123c51aba22289f2cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:020b41608bc702c95db9ca3ca5bf7bcf21ceeea89f492a8fbbd55025141602c8 +size 21210 diff --git a/marked/Rel-16/44_series/44118/886af5e2ffd5d8f11079c547675cf882_img.jpg b/marked/Rel-16/44_series/44118/886af5e2ffd5d8f11079c547675cf882_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..711300998720f5704e508e06b77ac1e703b24c5b --- /dev/null +++ b/marked/Rel-16/44_series/44118/886af5e2ffd5d8f11079c547675cf882_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3e02749189be255416a391d7735eede74fe7d6787bb2ed4da6dd07495fdf1b7 +size 12229 diff --git a/marked/Rel-16/44_series/44118/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg b/marked/Rel-16/44_series/44118/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5c51cda84e597acde86cde2964bb0ac9d05e330 --- /dev/null +++ b/marked/Rel-16/44_series/44118/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98abe30daefb58ffa426b2b49e613bb0c0d1bc5440fd0ee79f166b471a0e7134 +size 12108 diff --git a/marked/Rel-16/44_series/44118/9dc9f41d7d76c1add4b190d348cb1533_img.jpg b/marked/Rel-16/44_series/44118/9dc9f41d7d76c1add4b190d348cb1533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddf0b024e2b38b1b09fd1ac9aed2a2d8e9d37a47 --- /dev/null +++ b/marked/Rel-16/44_series/44118/9dc9f41d7d76c1add4b190d348cb1533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08cbfd9372b703b7a08e7022da0843493c5082a071f8154af87096e862117f41 +size 14528 diff --git a/marked/Rel-16/44_series/44118/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/Rel-16/44_series/44118/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15eb2ed17b4a80258a89f6b11e9150773ec88d1a --- /dev/null +++ b/marked/Rel-16/44_series/44118/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f88cd5aeabe30c0bb2c5346163abb71890b1b56a92a3c7b74086918fcd74919d +size 12583 diff --git a/marked/Rel-16/44_series/44118/a93de4c3f80bd4a972ab65510b09b68d_img.jpg b/marked/Rel-16/44_series/44118/a93de4c3f80bd4a972ab65510b09b68d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad9fea405dd078e13baaa08181e71a4f540abc31 --- /dev/null +++ b/marked/Rel-16/44_series/44118/a93de4c3f80bd4a972ab65510b09b68d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c52e7b1e93d274ff4ea0bb9eb815575668b2a8498cad10262498191ac40238e6 +size 21597 diff --git a/marked/Rel-16/44_series/44118/ae31c0503b477813f29e7f754dd7a9ed_img.jpg b/marked/Rel-16/44_series/44118/ae31c0503b477813f29e7f754dd7a9ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77adecd13eab5c6276c70e55637275e654691085 --- /dev/null +++ b/marked/Rel-16/44_series/44118/ae31c0503b477813f29e7f754dd7a9ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c731e222fc4c13885526a7bf868f4485c4590982a3ad8d40c33e91c9b6fad40e +size 21241 diff --git a/marked/Rel-16/44_series/44118/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-16/44_series/44118/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3953dd857666fe2e2a07da9526bda7bf52e128ee --- /dev/null +++ b/marked/Rel-16/44_series/44118/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:752db8ce7e235e2a1810455dc5d8af86d600079ab1b28eac0076a56e577ba775 +size 20802 diff --git a/marked/Rel-16/44_series/44118/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-16/44_series/44118/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9cf5a84106b3c2a2aaab8ee1db542db34ed253b --- /dev/null +++ b/marked/Rel-16/44_series/44118/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:844b0900c85b08542332092a37e2305a0a2c155a94555ecdfa516142277059b2 +size 16546 diff --git a/marked/Rel-16/44_series/44118/b97737027bd1b2effd7ca4dba8914877_img.jpg b/marked/Rel-16/44_series/44118/b97737027bd1b2effd7ca4dba8914877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e35f1f9a0a8a4eeb3cc7697611ade1ff36f0ee17 --- /dev/null +++ b/marked/Rel-16/44_series/44118/b97737027bd1b2effd7ca4dba8914877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4a9c223be9af2f1211b8eeeea9410422a3f2e42d03eb27ad9f3cfcdb9deba21 +size 17509 diff --git a/marked/Rel-16/44_series/44118/bbd36eba6bb7c4ba87608874c8c714ff_img.jpg b/marked/Rel-16/44_series/44118/bbd36eba6bb7c4ba87608874c8c714ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c3984a8b180960b1d3bf5492ac845a81513efeb --- /dev/null +++ b/marked/Rel-16/44_series/44118/bbd36eba6bb7c4ba87608874c8c714ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c026ed80f5b68847aff6e25ecd48d89f1469e2a0dd1537d7a8985945c71514b3 +size 16754 diff --git a/marked/Rel-16/44_series/44118/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/44_series/44118/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b34a7cffd43b12a8a07c9597c5071e9e8afc748d --- /dev/null +++ b/marked/Rel-16/44_series/44118/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9db2c6c28f77ce6a4a72bf63c6d3a438a149ab1d10b1d52a3ed650aad46f0033 +size 14575 diff --git a/marked/Rel-16/44_series/44118/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg b/marked/Rel-16/44_series/44118/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e70299e1b2609550e27dd9e12774ac84ee1ebd9 --- /dev/null +++ b/marked/Rel-16/44_series/44118/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:064c4ee828e243c677b1ffbcb6e28de6fb97e74d7e88e08713a007d860f4a666 +size 17394 diff --git a/marked/Rel-16/44_series/44118/d6015fcef74bce83d04acd2e17b4fc15_img.jpg b/marked/Rel-16/44_series/44118/d6015fcef74bce83d04acd2e17b4fc15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d89303a2ddebf10df312f30a1817b55a49d0ddc2 --- /dev/null +++ b/marked/Rel-16/44_series/44118/d6015fcef74bce83d04acd2e17b4fc15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a058e6c04760aa1342ae583ca847ea84810ca47a78d52a7be675687a141365e +size 13298 diff --git a/marked/Rel-16/44_series/44118/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/44_series/44118/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..744a8f77a0346d647b0ed6adf834ae564ed95187 --- /dev/null +++ b/marked/Rel-16/44_series/44118/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc38ae2ea000c128e2ce25af52d64f63adc4dfef0b5ef1a0da1a42de3f9de3ef +size 23332 diff --git a/marked/Rel-16/44_series/44118/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/44_series/44118/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdbe8f673cf8dc1e363bfcb9f8c3ebd48a65d11d --- /dev/null +++ b/marked/Rel-16/44_series/44118/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53d988b90600925e19396cda101c84ad3c0e5e7a60415089ad5e7882e9ca50b8 +size 70588 diff --git a/marked/Rel-16/44_series/44118/efcb2f9e7c89b033238d1021d3bd539f_img.jpg b/marked/Rel-16/44_series/44118/efcb2f9e7c89b033238d1021d3bd539f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59eabe0e9d5a84e3a3035c9e689565c30100e47f --- /dev/null +++ b/marked/Rel-16/44_series/44118/efcb2f9e7c89b033238d1021d3bd539f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cb3edb907125364256d3008e9505d3f104b221d73adf11012b1a5a3f93e87e2 +size 40397 diff --git a/marked/Rel-16/44_series/44118/faeab87eabc08d09a83cac8f66d1c126_img.jpg b/marked/Rel-16/44_series/44118/faeab87eabc08d09a83cac8f66d1c126_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78ebefaeed8858f77095b3cdcc79328a128e269a --- /dev/null +++ b/marked/Rel-16/44_series/44118/faeab87eabc08d09a83cac8f66d1c126_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:202e0c93607048390ff893eb85eed02f54a28fe817629d35c60febfaa6ca024c +size 13879 diff --git a/marked/Rel-16/44_series/44118/raw.md b/marked/Rel-16/44_series/44118/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..294331c080116eedb5dcdee852e5668c571b27f4 --- /dev/null +++ b/marked/Rel-16/44_series/44118/raw.md @@ -0,0 +1,15722 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword..... | 14 | +| 1 Scope..... | 15 | +| 1.1 General..... | 15 | +| 1.2 Scope of the Technical Specification..... | 15 | +| 1.3 Application to the interface structures..... | 15 | +| 1.4 Structure of layer 3 procedures..... | 15 | +| 1.5 Test procedures..... | 16 | +| 1.6 Applicability of implementations..... | 16 | +| 2 References..... | 16 | +| 3 Definitions, symbols and abbreviations..... | 18 | +| 3.1 Definitions..... | 18 | +| 3.2 Abbreviations..... | 19 | +| 3.3 Random values..... | 19 | +| 3.4 Specification Notations..... | 20 | +| 4 RRC Functions and Services provided to upper layers..... | 20 | +| 4.1 RRC Functions..... | 20 | +| 4.2 RRC Services provided to upper layers..... | 21 | +| 5 Services expected from lower layers..... | 21 | +| 5.1 Services required from layer 2 and physical layers..... | 21 | +| 5.2 Signalling Radio Bearers..... | 21 | +| 6 RRC Protocol modes and states..... | 21 | +| 6.1 General..... | 21 | +| 6.2 Relation between Iu mode and A/Gb mode..... | 22 | +| 6.2.1 Handover between Iu and A/Gb modes..... | 22 | +| 6.2.2 Cell reselection between Iu and A/Gb mode..... | 22 | +| 6.2a Relation between GERAN Iu mode RRC and UTRA RRC..... | 22 | +| 6.2a.1 Handover between GERAN Iu mode and UTRAN..... | 22 | +| 6.2a.2 Cell reselection between GERAN Iu mode and UTRAN..... | 23 | +| 6.3 RR modes of operation..... | 23 | +| 6.4 RRC modes and states..... | 23 | +| 6.4.1 RRC-Idle Mode..... | 23 | +| 6.4.1.1 General..... | 23 | +| 6.4.1.2 Transition from RRC-Idle Mode to RRC-Connected mode..... | 23 | +| 6.4.2 RRC-Connected mode: RRC-Cell_Shared state..... | 24 | +| 6.4.2.1 General..... | 24 | +| 6.4.2.2 Transition from RRC-Cell_Shared state to RRC-Idle Mode..... | 24 | +| 6.4.2.3 Transition from RRC-Cell_Shared state to RRC-Cell_Dedicated state..... | 24 | +| 6.4.2.4 Transition from RRC-Cell_Shared state to RRC-GRA_PCH state..... | 24 | +| 6.4.2.5 Radio resource allocation tasks..... | 24 | +| 6.4.2.6 RRC connection mobility tasks..... | 24 | +| 6.4.2.7 MS measurements..... | 25 | +| 6.4.3 RRC-Connected mode: RRC-Cell_Dedicated state..... | 25 | +| 6.4.3.1 General..... | 25 | +| 6.4.3.2 Transition from RRC-Cell_Dedicated state to RRC-Cell_Shared state..... | 25 | +| 6.4.3.3 Transition from RRC-Cell_Dedicated state to RRC-Idle Mode..... | 25 | +| 6.4.3.4 Transition from RRC-Cell_Dedicated state to RRC-GRA_PCH state..... | 25 | +| 6.4.3.5 Radio resource allocation tasks..... | 25 | +| 6.4.3.6 RRC connection mobility tasks..... | 25 | +| 6.4.3.7 MS measurements..... | 26 | +| 6.4.4 RRC-Connected mode: RRC-GRA_PCH state..... | 26 | +| 6.4.4.1 General..... | 26 | +| 6.4.4.2 Transition from RRC-GRA_PCH state to RRC-Cell_Shared state..... | 26 | +| 6.4.4.3 Transition from RRC-GRA_PCH state to RRC-Cell_Dedicated state..... | 26 | +| 6.4.4.4 Radio resource allocation tasks..... | 26 | +| 6.4.4.5 RRC connection mobility tasks..... | 26 | + +| | | | +|----------|---------------------------------------------------------------------------------------------------------------|----| +| 6.4.4.6 | MS measurements..... | 27 | +| 6.4.4.7 | Transfer and update of system information..... | 27 | +| 7 | Radio Resource Control procedures..... | 27 | +| 7.1 | General..... | 27 | +| 7.2 | Change of channels in case of handover..... | 27 | +| 7.2.1 | Change of channel serving SRB1..... | 27 | +| 7.2.2 | Change of channel serving SRB2..... | 27 | +| 7.2.3 | Change of channel serving SRB3..... | 28 | +| 7.2.4 | Change of channel serving SRB4..... | 28 | +| 7.3 | System information broadcasting..... | 28 | +| 7.3.1 | General..... | 28 | +| 7.3.2 | Broadcast of Iu mode specific System Information..... | 28 | +| 7.4 | Paging procedure..... | 30 | +| 7.4.1 | General..... | 30 | +| 7.4.2 | Paging initiation in RRC-Idle mode, RRC-Cell_Shared or RRC-GRA_PCH state..... | 30 | +| 7.4.2.1 | General..... | 30 | +| 7.4.2.2 | Initiation..... | 31 | +| 7.4.2.3 | Reception of a PAGING INDICATION service primitive..... | 32 | +| 7.4.3 | Paging initiation in RRC-Cell_Dedicated state..... | 33 | +| 7.4.3.1 | General..... | 33 | +| 7.4.3.2 | Initiation..... | 33 | +| 7.4.3.3 | Reception of a DEDICATED PAGING REQUEST message by the MS..... | 33 | +| 7.4.4 | Abnormal cases..... | 33 | +| 7.5 | RRC Connection management procedures..... | 34 | +| 7.5.1 | RRC connection establishment..... | 34 | +| 7.5.1.1 | General..... | 34 | +| 7.5.1.2 | Initiation..... | 34 | +| 7.5.1.3 | RRC CONNECTION REQUEST message contents to set..... | 35 | +| 7.5.1.4 | Reception of an RRC CONNECTION REQUEST message by the GERAN..... | 35 | +| 7.5.1.5 | Cell re-selection or T300 timeout..... | 35 | +| 7.5.1.6 | Abortion of RRC connection establishment..... | 36 | +| 7.5.1.7 | Reception of an RRC CONNECTION SETUP message by the MS..... | 36 | +| 7.5.1.8 | Cell re-selection..... | 37 | +| 7.5.1.9 | Invalid RRC CONNECTION SETUP message..... | 38 | +| 7.5.1.10 | Reception of an RRC CONNECTION REJECT message by the MS..... | 39 | +| 7.5.1.11 | Invalid RRC CONNECTION REJECT message..... | 39 | +| 7.5.2 | RRC connection release..... | 40 | +| 7.5.2.1 | General..... | 40 | +| 7.5.2.2 | Initiation..... | 40 | +| 7.5.2.3 | Reception of an RRC CONNECTION RELEASE message by the MS..... | 40 | +| 7.5.2.4 | Invalid RRC CONNECTION RELEASE message..... | 41 | +| 7.5.2.5 | Cell re-selection or radio link failure..... | 42 | +| 7.5.2.6 | Reception of an RRC CONNECTION RELEASE COMPLETE message by GERAN..... | 42 | +| 7.5.2.7 | Unsuccessful transmission of the RRC CONNECTION RELEASE COMPLETE message, acknowledged mode transmission..... | 42 | +| 7.5.2.8 | Detection of loss of dedicated physical channel by GERAN in RRC-Cell_Dedicated state..... | 43 | +| 7.5.2.9 | Failure to receive RRC CONNECTION RELEASE COMPLETE message by GERAN..... | 43 | +| 7.6 | Transmission of MS capability information..... | 43 | +| 7.6.1 | General..... | 43 | +| 7.6.2 | Initiation..... | 43 | +| 7.6.3 | Reception of an MS CAPABILITY INFORMATION message by the GERAN..... | 44 | +| 7.6.4 | Reception of the MS CAPABILITY INFORMATION CONFIRM message by the MS..... | 44 | +| 7.6.5 | Invalid MS CAPABILITY INFORMATION CONFIRM message..... | 45 | +| 7.6.6 | T304 timeout..... | 45 | +| 7.7 | MS capability enquiry..... | 46 | +| 7.7.1 | General..... | 46 | +| 7.7.2 | Initiation..... | 46 | +| 7.7.3 | Reception of an MS CAPABILITY ENQUIRY message by the MS..... | 46 | +| 7.7.4 | Invalid MS CAPABILITY ENQUIRY message..... | 46 | +| 7.8 | RRC Connection mobility procedures..... | 47 | +| 7.8.1 | Cell and GRA Update procedures..... | 47 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------|----| +| 7.8.1.1 | General..... | 48 | +| 7.8.1.2 | Initiation..... | 49 | +| 7.8.1.3 | CELL UPDATE / GRA UPDATE message contents to set..... | 52 | +| 7.8.1.4 | Reception of an CELL UPDATE/GRA UPDATE message by the GERAN..... | 53 | +| 7.8.1.5 | Reception of the CELL UPDATE CONFIRM/GRA UPDATE CONFIRM message by the MS..... | 54 | +| 7.8.1.6 | Transmission of a response message to GERAN..... | 58 | +| 7.8.1.7 | Physical channel failure..... | 62 | +| 7.8.1.8 | Unsupported configuration by the MS..... | 63 | +| 7.8.1.9 | Invalid configuration..... | 64 | +| 7.8.1.10 | Incompatible simultaneous reconfiguration..... | 66 | +| 7.8.1.10a | Security reconfiguration during Cell update procedure..... | 67 | +| 7.8.1.11 | Confirmation error of GRA ID list..... | 67 | +| 7.8.1.12 | Invalid CELL UPDATE CONFIRM/GRA UPDATE CONFIRM message..... | 69 | +| 7.8.1.13 | T302 expiry or cell reselection..... | 70 | +| 7.8.1.14 | T314 expiry..... | 72 | +| 7.8.1.15 | T315 expiry..... | 73 | +| 7.8.1.16 | Reception of the GERAN MOBILITY INFORMATION CONFIRM message by the GERAN..... | 74 | +| 7.8.1.17 | Inter-RAT cell reselection to GERAN Iu mode ..... | 74 | +| 7.8.1.17.1 | General..... | 74 | +| 7.8.1.17.2 | Initiation..... | 74 | +| 7.8.1.17.3 | MS fails to complete an inter-RAT cell reselection..... | 74 | +| 7.8.1.18 | Inter-RAT cell reselection from GERAN Iu mode ..... | 75 | +| 7.8.1.18.1 | General..... | 75 | +| 7.8.1.18.2 | Initiation..... | 75 | +| 7.8.1.18.3 | Successful cell reselection..... | 75 | +| 7.8.1.18.4 | MS fails to complete an inter-RAT cell reselection..... | 75 | +| 7.8.2 | GRA update..... | 75 | +| 7.8.3 | GERAN mobility information..... | 76 | +| 7.8.3.1 | General..... | 76 | +| 7.8.3.2 | Initiation..... | 76 | +| 7.8.3.3 | Reception of GERAN MOBILITY INFORMATION message by the MS..... | 76 | +| 7.8.3.4 | Reception of an GERAN MOBILITY INFORMATION CONFIRM message by the GERAN..... | 79 | +| 7.8.3.5 | Cell re-selection..... | 79 | +| 7.8.3.6 | Incompatible simultaneous security reconfiguration..... | 80 | +| 7.8.3.7 | Invalid GERAN MOBILITY INFORMATION message..... | 80 | +| 7.8.4 | Inter-mode handover from GERAN Iu mode ..... | 81 | +| 7.8.4.1 | General..... | 81 | +| 7.8.4.2 | Initiation..... | 81 | +| 7.8.4.3 | Reception of a HANDOVER FROM GERAN Iu COMMAND message by the MS..... | 81 | +| 7.8.4.4 | Successful completion of the inter-mode handover..... | 82 | +| 7.8.4.5 | Unsuccessful completion of the inter-mode handover at the MS side..... | 82 | +| 7.8.4.6 | Invalid HANDOVER FROM GERAN Iu COMMAND message..... | 82 | +| 7.8.4.7 | Reception of an HANDOVER FAILURE message by GERAN in Iu mode ..... | 83 | +| 7.8.4.8 | Unsupported configuration in HANDOVER FROM GERAN Iu COMMAND message..... | 83 | +| 7.8.4.9 | Reception of HANDOVER FROM GERAN Iu COMMAND message by MS in RRC-Cell_Shared state..... | 84 | +| 7.9 | Procedures for System Information transmission and Measurement reporting in RRC-Cell_Dedicated state..... | 84 | +| 7.9.1 | General..... | 84 | +| 7.9.2 | Measurement Report and Enhanced Measurement Report..... | 85 | +| 7.9.2.2 | Parameters for Measurements and Reporting..... | 85 | +| 7.9.2.2.1 | General..... | 85 | +| 7.9.2.2.2 | Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description..... | 85 | +| 7.9.2.2.3 | Deriving the GSM Neighbour Cell list from the BSICs and the BCCH Allocation..... | 86 | +| 7.9.2.2.4 | Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list..... | 86 | +| 7.9.2.2.5 | Real Time Differences..... | 86 | +| 7.9.2.2.6 | Report Priority Description..... | 86 | +| 7.9.2.2.7 | The 3G Cell Reselection list..... | 87 | +| 7.9.2.2.8 | CCN Support description..... | 87 | +| 7.9.3 | Extended measurement report..... | 87 | + +| | | | +|-------------|-------------------------------------------------------------------------------------------------------------------|-----| +| 7.10 | Handover to UTRAN procedure..... | 87 | +| 7.10.1 | General..... | 87 | +| 7.10.2 | Initiation..... | 88 | +| 7.10.3 | Reception of INTER SYSTEM TO UTRAN HANDOVER COMMAND message by the MS..... | 88 | +| 7.10.4 | Successful completion of the inter-RAT handover..... | 88 | +| 7.10.5 | Unsuccessful inter-rat handover at the MS side..... | 88 | +| 7.10.6 | Reception of an HANDOVER FAILURE message by GERAN in Iu mode..... | 89 | +| 7.11 | Handover to CDMA2000 procedure..... | 89 | +| 7.11.1 | General..... | 89 | +| 7.11.2 | Initiation..... | 90 | +| 7.11.3 | Reception of INTERSYSTEM TO CDMA2000 HANDOVER COMMAND message by the MS..... | 90 | +| 7.11.4 | Successful completion of the inter-RAT handover..... | 90 | +| 7.11.5 | Unsuccessful inter-rat handover at the MS side..... | 90 | +| 7.11.6 | Reception of an HANDOVER FAILURE message by GERAN in Iu mode..... | 91 | +| 7.12 | Mapping of user data substreams onto timeslots in a multislot configuration..... | 91 | +| 7.13 | Application Procedures..... | 92 | +| 7.13.1 | LCS transfer..... | 92 | +| 7.13.1.1 | General..... | 92 | +| 7.13.1.2 | Initiation of LCS transfer procedure in the GERAN..... | 92 | +| 7.13.1.3 | Reception of LCS DOWNLINK INFORMATION message by the MS..... | 92 | +| 7.13.1.4 | Transmission of a response message by the MS..... | 93 | +| 7.13.1.5 | Reception of a response message by the GERAN..... | 93 | +| 7.13.1.6 | Invalid LCS DOWNLINK INFORMATION message..... | 93 | +| 7.14 | Radio Bearer control procedures..... | 94 | +| 7.14.1 | Reconfiguration procedures..... | 94 | +| 7.14.1.1 | General..... | 95 | +| 7.14.1.2 | Initiation..... | 95 | +| 7.14.1.3 | Reception of RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or
RADIO BEARER RELEASE message by the MS..... | 96 | +| 7.14.1.4 | Transmission of a response message by the MS, normal case..... | 102 | +| 7.14.1.5 | Reception of a response message by the GERAN, normal case..... | 104 | +| 7.14.1.6 | Unsupported configuration in the MS..... | 105 | +| 7.14.1.7 | Physical channel failure..... | 106 | +| 7.14.1.8 | Cell re-selection..... | 107 | +| 7.14.1.9 | Transmission of a response message by the MS, failure case..... | 107 | +| 7.14.1.10 | Reception of a response message by the GERAN, failure case..... | 107 | +| 7.14.1.11 | Invalid configuration..... | 107 | +| 7.14.1.12 | Incompatible simultaneous reconfiguration..... | 108 | +| 7.14.1.12.1 | Incompatible simultaneous security reconfiguration..... | 108 | +| 7.14.1.12.2 | Cell Update procedure during security reconfiguration..... | 109 | +| 7.14.1.13 | Invalid received message..... | 109 | +| 7.14.1.14 | Abnormal cases..... | 110 | +| 7.14.2 | MS initiated DTM procedures while in RRC-Cell_Dedicated-MAC-Dedicated state..... | 112 | +| 7.14.2.1 | General..... | 112 | +| 7.14.2.2 | Initiation of the DTM Request procedure by the MS..... | 113 | +| 7.14.2.3 | Reception of a GERAN Iu mode DTM REQUEST message by the GERAN..... | 113 | +| 7.14.2.3.1 | General..... | 113 | +| 7.14.2.3.2 | SBPSCH assignment..... | 113 | +| 7.14.2.3.3 | DTM Request rejection..... | 113 | +| 7.14.2.3.4 | Reception of a GERAN Iu mode DTM REJECT message by the MS, normal case..... | 114 | +| 7.14.2.3.5 | Invalid GERAN Iu mode DTM REJECT message..... | 114 | +| 7.14.2.4 | Abnormal cases..... | 114 | +| 7.14.2.5 | T3148 expiry..... | 115 | +| 7.15 | Signalling flow procedures..... | 115 | +| 7.15.1 | Signalling connection release procedure..... | 115 | +| 7.15.1.1 | General..... | 115 | +| 7.15.1.2 | Initiation of SIGNALLING CONNECTION RELEASE by the GERAN..... | 115 | +| 7.15.1.3 | Reception of SIGNALLING CONNECTION RELEASE by the MS..... | 115 | +| 7.15.1.4 | Invalid SIGNALLING CONNECTION RELEASE message..... | 116 | +| 7.15.1.5 | Invalid configuration..... | 116 | +| 7.15.2 | Signalling connection release indication procedure..... | 117 | + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------------|-----| +| 7.15.2.1 | General..... | 117 | +| 7.15.2.2 | Initiation..... | 117 | +| 7.15.2.2a | RLC re-establishment, inter-mode handover or inter-RAT change..... | 117 | +| 7.15.2.3 | Reception of SIGNALLING CONNECTION RELEASE INDICATION by the GERAN..... | 118 | +| 7.16 | Security mode control..... | 118 | +| 7.16.1 | Security mode control..... | 118 | +| 7.16.1.1 | General..... | 118 | +| 7.16.1.2 | Initiation..... | 118 | +| 7.16.1.2.1 | Ciphering configuration change..... | 118 | +| 7.16.1.2.2 | Integrity protection configuration change..... | 119 | +| 7.16.1.2.3 | Reception of SECURITY MODE COMMAND message by the MS..... | 121 | +| 7.16.1.2.3.1 | New ciphering and integrity protection keys..... | 125 | +| 7.16.1.2.4 | Incompatible simultaneous security reconfiguration..... | 126 | +| 7.16.1.2.5 | Cell Update procedure during security reconfiguration..... | 127 | +| 7.16.1.2.6 | Invalid configuration..... | 128 | +| 7.16.1.2.7 | Reception of SECURITY MODE COMPLETE message by the GERAN..... | 128 | +| 7.16.1.2.8 | Invalid SECURITY MODE COMMAND message..... | 130 | +| 7.17 | Delivery of Non-Access stratum messages..... | 131 | +| 7.17.1 | Initial Direct transfer..... | 131 | +| 7.17.1.1 | General..... | 131 | +| 7.17.1.2 | Initiation of Initial direct transfer procedure in the MS..... | 131 | +| 7.17.1.3 | RLC re-establishment, inter-mode handover or inter-RAT change..... | 132 | +| 7.17.1.4 | Abortion of signalling connection establishment..... | 132 | +| 7.17.1.5 | Reception of INITIAL DIRECT TRANSFER message by the GERAN..... | 133 | +| 7.17.2 | Downlink Direct transfer..... | 133 | +| 7.17.2.1 | General..... | 133 | +| 7.17.2.2 | Initiation of downlink direct transfer procedure in the GERAN..... | 133 | +| 7.17.2.3 | Reception of a DOWNLINK DIRECT TRANSFER message by the MS..... | 134 | +| 7.17.2.4 | No signalling connection exists..... | 134 | +| 7.17.2.5 | Invalid DOWNLINK DIRECT TRANSFER message..... | 134 | +| 7.17.3 | Uplink Direct transfer..... | 135 | +| 7.17.3.1 | General..... | 135 | +| 7.17.3.2 | Initiation of uplink direct transfer procedure in the MS..... | 135 | +| 7.17.3.3 | RLC re-establishment, inter-mode handover or inter-RAT change..... | 135 | +| 7.17.3.4 | Reception of UPLINK DIRECT TRANSFER message by the GERAN..... | 136 | +| 7.18 | General procedures..... | 136 | +| 7.18.1 | Selection of initial MS identity..... | 136 | +| 7.18.2 | Actions when entering RRC-Idle mode from RRC-Connected mode..... | 136 | +| 7.18.2a | Actions when entering GERAN A/Gb mode or CDMA2000 from GERAN Iu mode , RRC-Connected mode..... | 137 | +| 7.18.3 | Maintenance of Hyper Frame Numbers..... | 138 | +| 7.18.4 | START value calculation..... | 139 | +| 7.18.5 | Integrity protection..... | 139 | +| 7.18.5.0 | General..... | 139 | +| 7.18.5.1 | Integrity protection in downlink..... | 140 | +| 7.18.5.2 | Integrity protection in uplink..... | 141 | +| 7.18.5.3 | Calculation of message authentication code..... | 142 | +| 7.18.6 | Physical channel establishment..... | 142 | +| 7.18.6.0 | General..... | 142 | +| 7.18.6.1 | Finely synchronized cell case..... | 143 | +| 7.18.6.2 | Non synchronized cell case..... | 143 | +| 7.18.6.3 | Pseudo-synchronized cell case..... | 144 | +| 7.18.6.4 | Pre-synchronized cell case..... | 144 | +| 7.18.7 | (void)..... | 145 | +| 7.18.8 | Link failure and Radio link failure criteria and actions upon link or radio link failure..... | 145 | +| 7.18.9 | Unsupported configuration..... | 145 | +| 7.18.10 | Invalid RLC/MAC control message notification..... | 145 | +| 7.18.11 | Actions related to Radio Bearer mapping..... | 145 | +| 7.18.12 | Network response times for DBPSCH allocation..... | 146 | +| 7.19 | Generic actions on receipt and absence of an information element..... | 146 | +| 7.19.1 | CN information info..... | 146 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------|-----| +| 7.19.2 | Signalling connection release indication..... | 146 | +| 7.19.3 | GERAN mobility information elements..... | 147 | +| 7.19.3.1 | GRA identity..... | 147 | +| 7.19.3.2 | Mapping info..... | 148 | +| 7.19.4 | MS information elements..... | 148 | +| 7.19.4.1 | Activation time..... | 148 | +| 7.19.4.2 | DRX parameters..... | 148 | +| 7.19.4.2.1 | CN domain specific DRX cycle length coefficients..... | 148 | +| 7.19.4.2.2 | GERAN DRX cycle length coefficient..... | 148 | +| 7.19.4.2.3 | Paging Group..... | 149 | +| 7.19.4.3 | Generic state transition rules depending on received information elements..... | 149 | +| 7.19.4.4 | Ciphering mode info..... | 150 | +| 7.19.4.5 | Integrity protection mode info..... | 153 | +| 7.19.4.5.1 | General..... | 153 | +| 7.19.4.5.2 | Initialization of Integrity ProtectionThe MS shall:..... | 153 | +| 7.19.4.5.3 | Integrity Protection Re-configuration for SBSS Relocation..... | 154 | +| 7.19.4.5.4 | Integrity Protection modification in case of new keys or initialisation of signalling connection. . | 155 | +| 7.19.4.6 | Integrity check info..... | 156 | +| 7.19.4.7 | New G-RNTI..... | 156 | +| 7.19.4.8 | RRC Transaction Identifier..... | 156 | +| 7.19.4.9 | Capability Update Requirement..... | 159 | +| 7.19.5 | Radio bearer information elements..... | 160 | +| 7.19.5.1 | Signalling RB information to setup list..... | 160 | +| 7.19.5.2 | RAB Information for Setup..... | 160 | +| 7.19.5.3 | RAB Information to Reconfigure..... | 161 | +| 7.19.5.4 | RB information to setup..... | 161 | +| 7.19.5.5 | RB information to be affected..... | 163 | +| 7.19.5.6 | RB information to reconfigure..... | 163 | +| 7.19.5.7 | RB Information to Release..... | 164 | +| 7.19.5.8 | RB with PDCP Information..... | 164 | +| 7.19.5.9 | (void)..... | 164 | +| 7.19.5.9a | RB Mapping Info..... | 164 | +| 7.19.5.10 | RLC Info..... | 165 | +| 7.19.5.11 | PDCP Info..... | 165 | +| 7.19.5.11a | PDCP context relocation info..... | 166 | +| 7.19.5.12 | PDCP SN Info..... | 166 | +| 7.19.5.13 | NAS Synchronisation Indicator..... | 166 | +| 7.19.5.14 | Physical Channel Configuration..... | 166 | +| 7.19.6 | Physical channel parameters..... | 167 | +| 7.19.6.1 | DBPSCH Description..... | 167 | +| 7.19.6.2 | SBPSCH parameters..... | 172 | +| 7.19.7 | Transport channel information elements..... | 173 | +| 7.19.7.1 | Transport Format Set..... | 173 | +| 7.19.7.2 | Transport format combination set..... | 174 | +| 7.19.7.3 | (void)..... | 175 | +| 7.19.7.4 | Added or Reconfigured UL TrCH information..... | 175 | +| 7.19.7.5 | Added or Reconfigured DL TrCH information..... | 175 | +| 7.19.7.6 | Deleted UL TrCH information..... | 175 | +| 7.19.7.7 | Deleted DL TrCH information..... | 175 | +| 7.19.7.8 | UL TrCH information common for all transport channels..... | 175 | +| 7.19.7.9 | DL TrCH information common for all transport channels..... | 175 | +| 7.19.7.10 | TFCS Reconfiguration/Addition Information..... | 176 | +| 7.19.7.11 | TFCS Removal Information..... | 176 | +| 7.19.7.12 | TFCS Explicit Configuration..... | 177 | +| 8 | Handling of unknown, unforeseen, and erroneous protocol data..... | 177 | +| 8.1 | General..... | 177 | +| 8.2 | CSN.1 violation or encoding error..... | 177 | +| 8.3 | Unknown or unforeseen message type..... | 178 | + +If the MS receives an RRC message on SRB2 with message type not defined for that SRB and if the RRC message is coded in ASN1 then MS shall follow the rules defined in 3GPP TS 25.331 for the DL messages sent on the DCCH.8.4 + +| | | +|-------------------------------------------------------------------------------------------------------|-----| +| Unsolicited received message | 178 | +| 8.5 Unexpected critical message extension..... | 179 | +| 8.6 Message with error label: 'Content part error'..... | 179 | +| 8.7 Unknown or unforeseen information element value, mandatory information element..... | 180 | +| 8.8 Unexpected non-critical message extension..... | 180 | +| 8.9 Message with error label: 'Message escape'..... | 181 | +| 8.10 Handling of errors in nested information elements..... | 181 | +| 8.11 Unknown or unforeseen information element value, optional information element coded in ASN1..... | 182 | +| 9 Message functional definitions and contents..... | 182 | +| 9.1 General..... | 182 | +| 9.1.1 Introduction..... | 182 | +| 9.1.2 Repetitions of Structure, IE or field:..... | 183 | +| 9.1.3 Message format and error labels..... | 183 | +| 9.1.3.1 General..... | 183 | +| 9.1.3.2 Message extension for new protocol version in RRC..... | 184 | +| 9.1.3.2.1 Non-Critical extension..... | 184 | +| 9.1.3.2.2 Critical extension..... | 185 | +| 9.1.3.2.3 Extension of IE's..... | 186 | +| 9.1.3.2.4 'Message escape' error label..... | 186 | +| 9.2 Messages for Radio Resources management..... | 186 | +| 9.2.1 General..... | 186 | +| 9.2.1.1 References..... | 187 | +| 9.2.1.2 Downlink RRC messages..... | 189 | +| 9.2.1.3 Uplink RRC messages..... | 190 | +| 9.2.1.3.1 Message definitions..... | 190 | +| 9.2.1.3.1.1 PDU definitions..... | 197 | +| 9.2.2 CELL UPDATE..... | 198 | +| 9.2.3 CELL UPDATE CONFIRM..... | 199 | +| 9.2.4 DEDICATED PAGING REQUEST..... | 203 | +| 9.2.5 DOWNLINK DIRECT TRANSFER..... | 203 | +| 9.2.6 EXTENDED MEASUREMENT ORDER..... | 204 | +| 9.2.7 EXTENDED MEASUREMENT REPORT..... | 204 | +| 9.2.7a ENHANCED MEASUREMENT REPORT..... | 205 | +| 9.2.8 GERAN MOBILITY INFORMATION..... | 205 | +| 9.2.9 GERAN MOBILITY INFORMATION CONFIRM..... | 206 | +| 9.2.10 GERAN MOBILITY INFORMATION FAILURE..... | 207 | +| 9.2.11 GRA UPDATE..... | 208 | +| 9.2.12 GRA UPDATE CONFIRM..... | 208 | +| 9.2.13 (void)..... | 209 | +| 9.2.14 HANDOVER COMPLETE..... | 209 | +| 9.2.15 HANDOVER FAILURE..... | 210 | +| 9.2.16 HANDOVER FROM GERAN Iu COMMAND..... | 210 | +| 9.2.17 INITIAL DIRECT TRANSFER..... | 211 | +| 9.2.18 INTER SYSTEM TO CDMA2000 HANDOVER COMMAND..... | 212 | +| 9.2.19 INTER SYSTEM TO UTRAN HANDOVER COMMAND..... | 214 | +| 9.2.20 LCS DOWNLINK INFORMATION..... | 215 | +| 9.2.21 LCS UPLINK INFORMATION..... | 215 | +| 9.2.22 MEASUREMENT INFORMATION..... | 216 | +| 9.2.23 MEASUREMENT REPORT..... | 216 | +| 9.2.24 MS CAPABILITY ENQUIRY..... | 216 | +| 9.2.25 MS CAPABILITY INFORMATION..... | 217 | +| 9.2.26 MS CAPABILITY INFORMATION CONFIRM..... | 218 | +| 9.2.27 (void)..... | 219 | +| 9.2.28 RADIO BEARER RECONFIGURATION..... | 219 | +| 9.2.29 RADIO BEARER RECONFIGURATION COMPLETE..... | 222 | +| 9.2.30 RADIO BEARER RECONFIGURATION FAILURE..... | 224 | + +| | | | +|--------|------------------------------------------------------|-----| +| 9.2.31 | RADIO BEARER RELEASE..... | 224 | +| 9.2.32 | RADIO BEARER RELEASE COMPLETE..... | 227 | +| 9.2.33 | RADIO BEARER RELEASE FAILURE..... | 229 | +| 9.2.34 | RADIO BEARER SETUP..... | 229 | +| 9.2.35 | RADIO BEARER SETUP COMPLETE..... | 232 | +| 9.2.36 | RADIO BEARER SETUP FAILURE..... | 233 | +| 9.2.37 | RR C CONNECTION REJECT..... | 234 | +| 9.2.38 | RR C CONNECTION RELEASE..... | 235 | +| 9.2.39 | RR C CONNECTION RELEASE COMPLETE..... | 236 | +| 9.2.40 | RR C CONNECTION REQUEST..... | 236 | +| 9.2.41 | RR C CONNECTION SETUP..... | 237 | +| 9.2.42 | RR C CONNECTION SETUP COMPLETE..... | 238 | +| 9.2.43 | RR C STATUS..... | 239 | +| 9.2.44 | RR C FAILURE INFO..... | 239 | +| 9.2.45 | SECURITY MODE COMMAND..... | 240 | +| 9.2.46 | SECURITY MODE COMPLETE..... | 241 | +| 9.2.47 | SECURITY MODE FAILURE..... | 241 | +| 9.2.48 | SIGNALLING CONNECTION RELEASE..... | 242 | +| 9.2.49 | SIGNALLING CONNECTION RELEASE INDICATION..... | 242 | +| 9.2.50 | (void)..... | 243 | +| 9.2.51 | SYSTEM INFORMATION 5..... | 243 | +| 9.2.52 | SYSTEM INFORMATION 5bis..... | 243 | +| 9.2.53 | SYSTEM INFORMATION 5ter..... | 243 | +| 9.2.54 | SYSTEM INFORMATION 6..... | 244 | +| 9.2.55 | (void)..... | 244 | +| 9.2.56 | UPLINK DIRECT TRANSFER..... | 244 | +| 9.2.57 | GERAN Iu mode DTM REQUEST..... | 245 | +| 9.2.58 | GERAN Iu mode DTM REJECT..... | 245 | +| 9.3 | Information Elements..... | 246 | +| 9.3.1 | Activation Time..... | 246 | +| 9.3.2 | BA List Pref..... | 246 | +| 9.3.3 | BA Range..... | 246 | +| 9.3.4 | Capability Update Requirement..... | 247 | +| 9.3.5 | CDMA2000 MS security capability..... | 247 | +| 9.3.6 | Cell Channel Description..... | 247 | +| 9.3.7 | Cell Description..... | 248 | +| 9.3.8 | Cell Update Cause..... | 248 | +| 9.3.9 | Channel Description..... | 248 | +| 9.3.10 | Channel Description 2..... | 249 | +| 9.3.11 | Channel Mode..... | 249 | +| 9.3.12 | Channel Mode 2..... | 249 | +| 9.3.13 | Ciphering Algorithm..... | 250 | +| 9.3.14 | Ciphering Mode Info..... | 250 | +| 9.3.15 | CN Domain Identity..... | 251 | +| 9.3.16 | CN Domain Specific DRX Cycle Length Coefficient..... | 251 | +| 9.3.17 | CN Information Info..... | 251 | +| 9.3.18 | CN Information Info Full..... | 252 | +| 9.3.19 | DBPSCH Description..... | 253 | +| 9.3.20 | Dynamic ARFCN Mapping..... | 257 | +| 9.3.21 | Establishment Cause..... | 257 | +| 9.3.22 | Expiration Time Factor..... | 258 | +| 9.3.23 | Extension..... | 258 | +| 9.3.24 | Failure Cause..... | 258 | +| 9.3.25 | Failure Cause and Error Information..... | 259 | +| 9.3.26 | Frequency Channel Sequence..... | 259 | +| 9.3.27 | Frequency List..... | 260 | +| 9.3.28 | Frequency Short List..... | 260 | +| 9.3.29 | GERAN DRX Cycle Length Coefficient..... | 260 | +| 9.3.30 | GRA Identity..... | 261 | +| 9.3.31 | GRA Update Cause..... | 261 | +| 9.3.32 | G-RNTI..... | 261 | + +| | | | +|--------|----------------------------------------------------|-----| +| 9.3.33 | GSM MS Security Capability..... | 262 | +| 9.3.34 | Handover Reference..... | 262 | +| 9.3.35 | Initial MS Identity..... | 262 | +| 9.3.36 | Integrity Check Info..... | 263 | +| 9.3.37 | Integrity Protection Activation Info..... | 264 | +| 9.3.38 | Integrity Protection Algorithm..... | 264 | +| 9.3.39 | Integrity Protection Mode Info..... | 265 | +| 9.3.40 | (void)..... | 265 | +| 9.3.41 | Intra Domain NAS Node Selector..... | 265 | +| 9.3.42 | Mobile Allocation..... | 266 | +| 9.3.43 | Mobile Time Difference..... | 266 | +| 9.3.44 | MS GERAN A/Gb mode Radio Access Capability..... | 266 | +| 9.3.45 | MS GERAN Iu mode Radio Access Capability..... | 267 | +| 9.3.46 | MS GERAN Iu mode RLC Capability..... | 268 | +| 9.3.47 | MS RF Capability GSM..... | 269 | +| 9.3.48 | MS Multi-Mode and Multi-RAT Capability..... | 272 | +| 9.3.49 | MS Measurement Capability..... | 273 | +| 9.3.50 | MS Positioning Capability..... | 273 | +| 9.3.51 | MS Timers and Constants in RRC-Connected mode..... | 274 | +| 9.3.52 | MultiRate Configuration..... | 275 | +| 9.3.53 | Multislot Allocation..... | 275 | +| 9.3.54 | NAS Message..... | 276 | +| 9.3.55 | NAS Synchronization Info..... | 276 | +| 9.3.56 | NAS System Information GSM-MAP..... | 276 | +| 9.3.57 | Paging Cause..... | 277 | +| 9.3.58 | Paging Record Type Identifier..... | 277 | +| 9.3.59 | PDCP Capability..... | 278 | +| 9.3.60 | PDCP Info..... | 279 | +| 9.3.61 | PDCP SN Info..... | 282 | +| 9.3.62 | Physical Channel Configuration..... | 283 | +| 9.3.63 | PLMN Identity..... | 283 | +| 9.3.64 | Power Command..... | 284 | +| 9.3.65 | Power Command and Access Type..... | 284 | +| 9.3.66 | (void)..... | 284 | +| 9.3.67 | (void)..... | 284 | +| 9.3.68 | (void)..... | 284 | +| 9.3.69 | Protocol Error Cause..... | 284 | +| 9.3.70 | Protocol Error Indicator..... | 285 | +| 9.3.71 | Protocol Error Information..... | 285 | +| 9.3.72 | RAB Identity..... | 285 | +| 9.3.73 | RAB Info..... | 286 | +| 9.3.74 | RAB Info Post..... | 286 | +| 9.3.75 | RAB Information for Setup..... | 287 | +| 9.3.76 | RAB Information to Reconfigure..... | 287 | +| 9.3.77 | RB Activation Time Info..... | 287 | +| 9.3.78 | RB COUNT-C Information..... | 288 | +| 9.3.79 | RB COUNT-C MSB Information..... | 289 | +| 9.3.80 | RB Identity..... | 289 | +| 9.3.81 | RB Information to Be Affected..... | 289 | +| 9.3.82 | RB Information to Reconfigure..... | 290 | +| 9.3.83 | RB Information to Release..... | 290 | +| 9.3.84 | RB Information to Setup..... | 291 | +| 9.3.85 | RB Timer Indicator..... | 291 | +| 9.3.86 | RB with PDCP Information..... | 292 | +| 9.3.87 | (void)..... | 292 | +| 9.3.88 | Re-Establishment timer..... | 292 | +| 9.3.89 | Rejection Cause..... | 292 | +| 9.3.90 | Release Cause..... | 293 | +| 9.3.91 | RLC Info..... | 293 | +| 9.3.92 | RLC HFN IE..... | 294 | +| 9.3.93 | RPLMN Information..... | 295 | + +| | | | +|----------|-----------------------------------------------------------------------------|-----| +| 9.3.94 | RRC Cause..... | 295 | +| 9.3.95 | RRC Packet Downlink Assignment..... | 296 | +| 9.3.95a | RRC Packet Downlink Assignment 2..... | 298 | +| 9.3.96 | RRC Packet Uplink Assignment..... | 298 | +| 9.3.96a | RRC Packet Uplink Assignment 2..... | 301 | +| 9.3.97 | RRC State Indicator..... | 303 | +| 9.3.98 | RRC Transaction Identifier..... | 303 | +| 9.3.99 | SBPSCH Description..... | 303 | +| 9.3.100 | Security Capability..... | 304 | +| 9.3.101 | Signalling RB Information To Setup..... | 305 | +| 9.3.102 | START..... | 306 | +| 9.3.103 | Starting Time..... | 306 | +| 9.3.104 | Synchronization Indication..... | 306 | +| 9.3.105 | Time Difference..... | 306 | +| 9.3.106 | Timing Advance..... | 307 | +| 9.3.107 | Transmission RLC Discard..... | 307 | +| 9.3.108 | UE UTRAN Radio Access Capability..... | 307 | +| 9.3.108a | UE UTRAN Predefined Configuration Status Information..... | 308 | +| 9.3.109 | UE UTRAN Radio Access Capability Extension..... | 308 | +| 9.3.110 | UE CDMA2000 Radio Access Capability..... | 309 | +| 9.3.111 | UTRAN Freq List..... | 309 | +| 9.3.112 | Wait Time..... | 309 | +| 9.3.113 | Iu mode Channel Request Description..... | 310 | +| 9.3.114 | Wait Indication..... | 310 | +| 9.3.115 | (void)..... | 310 | +| 9.3.116 | PDCP Context Relocation Info..... | 310 | +| 9.3.117 | RB mapping info..... | 311 | +| 9.3.118 | Interleaving..... | 312 | +| 9.3.119 | Mode..... | 313 | +| 9.3.120 | Modulation..... | 313 | +| 9.3.121 | Added or Reconfigured DL TrCH information..... | 313 | +| 9.3.122 | Added or Reconfigured UL TrCH information..... | 314 | +| 9.3.123 | Deleted DL TrCH information..... | 314 | +| 9.3.124 | Deleted UL TrCH information..... | 315 | +| 9.3.125 | DL TrCH Information Common For All Transport Channels..... | 315 | +| 9.3.126 | Semi-static Transport Format Information..... | 316 | +| 9.3.127 | TFCS Explicit Configuration..... | 316 | +| 9.3.128 | TFCS Reconfiguration/Addition Information..... | 317 | +| 9.3.129 | TFCS Removal Information..... | 318 | +| 9.3.130 | Transport Channel Identity..... | 318 | +| 9.3.131 | TFC..... | 318 | +| 9.3.132 | Transport Format Combination Set..... | 318 | +| 9.3.133 | Transport Format Set..... | 319 | +| 9.3.134 | UL TrCH Information Common For All Transport Channels..... | 319 | +| 9.3a | Information element definitions..... | 319 | +| 9.4 | Multiplicity values and type constraint values..... | 323 | +| 9.4a | Constant definitions..... | 324 | +| 10 | Protocol timers, counters, other parameters and default configurations..... | 325 | +| 10.1 | Timers for MS..... | 325 | +| 10.1a | Timers on the network side..... | 325 | +| 10.2 | Counters for MS..... | 326 | +| 10.3 | MS constants and parameters..... | 326 | +| 10.3a | Network constants and parameters..... | 326 | +| 10.4 | MS variables..... | 326 | +| 10.4.0 | General..... | 326 | +| 10.4.1 | CELL_UPDATE_STARTED..... | 328 | +| 10.4.2 | CIPHERING_STATUS..... | 328 | +| 10.4.3 | ESTABLISHED_SIGNALLING_CONNECTIONS..... | 329 | +| 10.4.4 | ESTABLISHMENT_CAUSE..... | 329 | +| 10.4.5 | ESTABLISHED_RABS..... | 330 | +| 10.4.6 | FAILURE_CAUSE..... | 331 | + +| | | | +|------------------------|--------------------------------------------------------------------------------|-----| +| 10.4.7 | FAILURE_INDICATOR..... | 331 | +| 10.4.8 | GRA_IDENTITY..... | 331 | +| 10.4.9 | G_RNTI..... | 332 | +| 10.4.10 | INITIAL_MS_IDENTITY..... | 332 | +| 10.4.11 | INCOMPATIBLE_SECURITY_RECONFIGURATION..... | 332 | +| 10.4.12 | INTEGRITY_PROTECTION_ACTIVATION_INFO..... | 332 | +| 10.4.13 | INTEGRITY_PROTECTION_INFO..... | 333 | +| 10.4.14 | INVALID_CONFIGURATION..... | 334 | +| 10.4.14a | LATEST_CONFIGURED_CN_DOMAIN..... | 334 | +| 10.4.15 | MS_CAPABILITY_REQUESTED..... | 335 | +| 10.4.16 | MS_CAPABILITY_TRANSFERRED..... | 335 | +| 10.4.17 | ORDERED_RECONFIGURATION..... | 336 | +| 10.4.18 | PDCP_SN_INFO..... | 336 | +| 10.4.19 | PROTOCOL_ERROR_INDICATOR..... | 336 | +| 10.4.20 | PROTOCOL_ERROR_INFORMATION..... | 337 | +| 10.4.21 | PROTOCOL_ERROR_REJECT..... | 337 | +| 10.4.22 | RB_TIMER_INDICATOR..... | 337 | +| 10.4.23 | RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO..... | 338 | +| 10.4.24 | START_THRESHOLD..... | 338 | +| 10.4.25 | START_VALUE_TO_TRANSMIT..... | 338 | +| 10.4.26 | TRANSACTIONS..... | 339 | +| 10.4.27 | TIMERS_AND_CONSTANTS..... | 339 | +| 10.4.28 | UNSUPPORTED_CONFIGURATION..... | 339 | +| 10.4.29 | SECURITY_MODIFICATION..... | 340 | +| 11 | Specific functions..... | 341 | +| 11.1 | Provision and reception of RRC information between network nodes..... | 341 | +| 11.1.1 | General..... | 341 | +| 11.1.2 | General error handling for RRC messages exchanged between network nodes..... | 341 | +| 11.1.3 | RRC Information to target GERAN Iu mode BSS..... | 342 | +| 11.1.4 | RRC information, target BSS to source BSS..... | 343 | +| 11.1.5 | RRC messages exchanged between network nodes..... | 343 | +| 11.1.5.0 | RADIO BEARER RECONFIGURATION..... | 343 | +| 11.1.5.1 | INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES..... | 343 | +| 11.1.5.2 | SBSS RELOCATION INFO..... | 344 | +| 11.1.5.3 | RFC 3095 CONTEXT INFO..... | 348 | +| 11.2 | Provision and reception of RRC security information between network nodes..... | 349 | +| 11.2.1 | General..... | 349 | +| 11.2.2 | RRC Security Information, from GERAN-A/Gb to GERAN-Iu..... | 349 | +| 11.2.3 | RRC Security Information, from GERAN Iu mode/UTRAN to GERAN Iu mode..... | 350 | +| 11.2.4 | RRC Security Information, from GERAN Iu to UTRAN..... | 352 | +| 11.3 | HCN mapping rules for radio bearer using non-transparent mode RLC..... | 352 | +| 11.4 | Calculated Transport Format Combination..... | 352 | +| 11.5 | Signalling TFC..... | 353 | +| Annex A (informative): | Change History..... | 354 | + +--- + +## 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 + +## 1.1 General + +The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002) for Radio Resource management. The Radio Resource Control Protocol (RRC) is specified. RRC is the Radio Resource control plane protocol for Radio Resource management that is used when a mobile station is operating in Iu mode. + +Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts. + +When the notations for "further study" or "FS" or "FFS" are present in this specification they mean that the indicated text is not a normative portion of this standard. + +These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPP TS 44.003. + +The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007. + +## 1.2 Scope of the Technical Specification + +The procedures currently described in the present document are for radio resource management for circuit switched and GPRS services. + +3GPP TS 24.010 contains functional procedures for support of supplementary services. + +3GPP TS 24.011 contains functional procedures for support of point-to-point short message services. + +3GPP TS 44.012 contains functional description of short message cell broadcast. + +3GPP TS 44.060 contains procedures for radio link control and medium access control (RLC/MAC) of packet data physical channels. + +3GPP TS 44.071 contains functional descriptions and procedures for support of location services. + +3GPP TS 24.008 contains the procedures for CN protocols. + +NOTE: "layer 3" includes the functions and protocols described in this Technical Specification. The terms "data link layer" and "layer 2" are used interchangeably to refer to the layer immediately below layer 3. + +## 1.3 Application to the interface structures + +The layer 3 procedures apply to the interface structures defined in 3GPP TS 44.003. They use the functions and services provided by layer 2 defined in 3GPP TS 44.005 and 3GPP TS 44.006. 3GPP TS 24.007 gives the general description of layer 3 including procedures, messages format and error handling. + +## 1.4 Structure of layer 3 procedures + +A building block method is used to describe the layer 3 procedures. + +The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer. + +Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences. + +## 1.5 Test procedures + +Test procedures of the GSM radio interface signalling are described in 3GPP TS 51.010 and 3GPP TS 51.02x series. + +## 1.6 Applicability of implementations + +NOTE: This sub-clause is FFS. + +## 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 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.011: "Service accessibility". +- [3] 3GPP TS 23.003: "Numbering, addressing and identification". +- [4] 3GPP TS 23.022: "Functions related to Mobile Station (MS) in idle mode". +- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [6] 3GPP TS 23.101: "General UMTS Architecture". +- [7] 3GPP TS 23.110: " UMTS Access Stratum; Services and Functions". +- [8] 3GPP TS 23.221: "Architectural requirements". +- [9] 3GPP TS 24.002: "GSM Public Land Mobile Network (PLMN) access reference configuration". +- [10] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [11] 3GPP TS 24.008: "Mobile radio interface layer 3 specification;Core Network Protocols - Stage 3" +- [12] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary services specification; General aspects". +- [13] 3GPP TS 24.011: "Point-to-point (PP) Short Message Service (SMS) support on mobile radio interface". +- [14] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding". +- [15] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) Specification". +- [16] 3GPP TS 25.331: "Radio Access Network; RRC Protocol Specification". +- [17] 3GPP TS 31.102: "Characteristics of the USIM Application". +- [18] 3GPP TS 33.102: "3G Security; Security Architecture". +- [19] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM system". +- [20] 3GPP TS 43.051: "Radio Access Network; Overall description Stage 2". +- [21] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services in GERAN". +- [22] 3GPP TS 44.004: "Layer 1 General requirements". +- [23] 3GPP TS 44.005: "Data Link (DL) layer General aspects". + +- [24] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". +- [25] 3GPP TS 44.003: "Mobile Station Base Station System (MS - BSS) interface Channel structures and access capabilities". +- [26] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [27] 3GPP TS 44.018: "GSM EDGE Radio Access Network, Mobile radio interface layer 3 specification, Radio Resource Control Protocol" +- [28] 3GPP TS 44.031: "Location Services;Mobile Station (MS) – Serving Mobile Location Centre (SMLC); Radio Resource LCS Protocol (RRLP)". +- [29] 3GPP TS 44.071: "Mobile radio interface layer 3 location services specification." +- [30] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station - Base Station System (MS-BSS) interface; Radio Link Control and Medium Access Control (RLC/MAC) layer specification". +- [31] 3GPP TS 44.160: "General Packet Radio Service (GPRS); Mobile Station - Base Station System (MS-BSS) interface; Radio Link Control and Medium Access Control (RLC/MAC) layer specification, Iu mode". +- [32] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [33] 3GPP TS 45.005: "Radio transmission and reception". +- [34] 3GPP TS 45.008: "Radio subsystem link control". +- [35] 3GPP TS 45.010: "Radio subsystem synchronization". +- [36] 3GPP TS 51.010: "Mobile Station (MS) conformity specification". +- [37] ITU-T Recommendation Q.931: ISDN user-network interface layer 3 specification for basic control". +- [38] TTA/EIA/IS-2000-5-A: "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems". +- [39] TTA/EIA/IS-833: "Multi-Carrier Specification for Spread Spectrum Systems on GSM MAP (MC-MAP) (Lower Layers Air Interface)". +- [40] TTA/EIA/IS-2000-4-A: "Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems". +- [41] Michel MOULY, "CSN.1 Specification, Version 2.0", Cell & Sys, ISBN: 2-9510062-0-9. Web: . +- [42] IANA ROHC profile identifier definition (). +- [43] 3GPP TR 45.902: "Flexible Layer One". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +The following terms are used in this Technical Specification: + +**A/Gb mode:** mode of operation of the MS when connected to the Core Network via GERAN and the A and/or Gb interfaces. + +**Access Stratum (AS):** defined in 3GPP TS 23.101. + +**Active Transport Channel:** a transport channel is active during a TTI if it carries a transport block. + +**"channel set":** is used to identify TCHs that carry related user information flows, e.g., in a multislot configuration used to support circuit switched connection(s), which therefore need to be handled together. + +**Dynamic attributes:** for one transport channel, the values of the dynamic attributes are different among transport formats. They are configured by Layer 3 and can change on a TTI basis under the control of the MAC sublayer. + +**Empty Transport Format:** a transport format such that no transport block is carried over the transport channel (i.e. the transport channel is inactive). + +**Empty Transport Format Combination:** a transport format combination that is made up only of empty transport formats. + +**Inactive Transport Channel:** a transport channel is inactive during a TTI if it does not carry a transport block (i.e. the transport block size is zero). + +**Iu mode:** mode of operation of the MS when connected to the Core Network via GERAN or UTRAN and the Iu interface. + +**Non Access Stratum (NAS):** defined in 3GPP TS 21.905. + +**RR idle:** defined in 3GPP TS 44.018. + +**RR:** Radio Resource control plane protocol for radio resource management that is used when a mobile station is operating in *A/Gb mode*. + +**RRC:** Radio Resource control plane protocol for radio resource management that is used when a mobile station is operating in Iu mode. + +**RRC Connection:** A point-to-point bi-directional connection between RRC peer entities in the MS and the GERAN characterised by the allocation of a G-RNTI. An MS has either zero or one RRC connection. + +**RRC-Idle mode:** In RRC-Idle mode, the MS has no established RRC connection. + +**RRC-Connected mode:** In RRC-Connected mode, the MS has an established RRC connection. + +**Inter-RAT handover:** indicates the transfer of the connection, under the control of the network, between the MS and two different radio access technologies (e.g. UMTS to GERAN Iu mode). + +**Inter-mode handover:** indicates the transfer of the connection, under the control of the network, between the MS and GERAN Iu mode to/from GERAN A/Gb mode. + +**R:** Retransmission number ( $R = 0$ for first transmission, $R = 1$ for first retransmission, ..., $R = n$ for the $n^{\text{th}}$ retransmission). When there is no retransmission, $R = 0$ always. + +**RR group receive mode:** defined in 3GPP TS 44.018. + +**RR dedicated mode:** defined in 3GPP TS 44.018. + +**RR group transmit mode:** defined in 3GPP TS 44.018. + +**RR packet idle mode:** defined in 3GPP TS 44.018. + +**RR packet transfer mode:** defined in 3GPP TS 44.018. + +**RR dual transfer mode:** defined in 3GPP TS 44.018. + +**RLC/MAC block:** A RLC/MAC block is the protocol data unit exchanged between RLC/MAC entities, see 3GPP TS 44.060. + +**Semi-static attributes:** for one transport channel, the values of the semi-static attributes are common to all transport formats. They are configured by Layer 3 and can only be changed by Layer 3 signalling. + +**Transport Block (TB):** block exchanged on a transport channel between the physical layer and the MAC sublayer. + +**Temporary block flow (TBF):** is defined in 3GPP TS 44.060. + +**Transport Channel (TrCH)**: a transport channel is offered by the physical layer to the MAC sublayer for exchange of transport blocks. A transport channel is used to carry with a certain quality of service, a data flow over the radio interface. + +**Transport Format (TF)**: configuration of a transport channel, including for instance channel coding, CRC size, etc. + +**Transport Format Combination (TFC)**: allowed combination of transport format(s) of the different transport channels that are multiplexed together on a basic physical subchannel. + +**Transport Format Combination Indicator (TFCI)**: layer one header that indicates the transport channel combination that has been selected for each radio packet. + +**Transport Format Combination Set (TFCS)**: set of allowed transport format combinations on a basic physical subchannel. + +**Transport Format Indicator (TFIN)**: index identifying a particular transport format within the transport format set. + +**Transport Format Set (TFS)**: set of all transport formats defined for a particular transport channel. + +**Transmission Time Interval (TTI)**: rate at which transport blocks are exchanged between the physical layer and the MAC sublayer on a transport channel. + +The network modes of operation for GERAN *Iu mode* are: + +- | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NMO I: | the network has a Gs interface. The network sends CS paging and PS paging messages for an attached MS via the SGSN and the Iu-ps interface to GERAN Iu. Paging co-ordination is achieved at the SGSN thanks to the Gs interface. GERAN Iu pages the MS on PACCH if available, else PCCH. MS can initiate combined procedures according to its capabilities. | +| NMO II: | the network has no Gs interface. For an attached MS, the network sends CS paging messages, via the MSC plus the Iu-cs interface, and sends PS paging messages, via the SGSN plus the Iu-ps interface to GERAN Iu. GERAN Iu performs paging co-ordination and pages the MS on PACCH if available, else PCCH. MSs cannot initiate combined procedures. | + +## 3.2 Abbreviations + +Abbreviations used in this specification are listed in 3GPP TS 21.905. + +NOTE: 3GPP TS 21.905 may need to be updated. + +## 3.3 Random values + +In a number of places in this Technical Specification, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. Such cases interest only the Mobile Station. + +It is required that there is a low probability that two MSs in the same conditions (including the case of two MSs of the same type from the same manufacturer) will choose the same value. Moreover, it is required that, if it happens that two MSs in similar conditions choose the same value, the probability of their choices being identical at the next occasion is the same as if their first choices had been different. + +The meaning of such a specification is that any statistical test for these values, done on a series of similar events, will obtain a result statistically compatible with the specified distribution. This shall hold even in the cases where the tests are conducted with a subset of possible events, with some common parameters. Moreover, basic tests of independence of the values within the series shall pass. + +Data against which correlation with the values shall not be found are the protocol state, or the IMSI, or identities or other unrelated information broadcast by the network, or the current TDMA frame number. + +## 3.4 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. RRC Establishment 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. CELL UPDATE 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 preceded by the abbreviation "IE", e.g. IE " Initial MS Identity ". | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in sub-clause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Geographical Coordinates" | + +--- + +## 4 RRC Functions and Services provided to upper layers + +### 4.1 RRC Functions + +RRC performs following functions. A more detailed description of the functions can be found in 3GPP TS 43.051. + +- Broadcast of information provided by the Non-Access stratum (Core Network) +- Broadcast of information related to the access stratum +- Establishment, re-establishment, maintenance and release of an RRC connection between the MS and GERAN +- Establishment, reconfiguration and release of Radio Bearers +- Assignment, reconfiguration and release of radio resources for the RRC connection +- RRC connection mobility functions +- Release of signalling connections +- Paging/notification +- Listening to BCCH +- Routing of higher layer PDUs +- Control of requested QoS +- MS measurement reporting and control of the reporting +- Power control +- Control of ciphering +- Integrity protection +- Support for Location Services +- Timing advance control + +## 4.2 RRC Services provided to upper layers + +The RRC offers the following services to upper layers (NAS), a description and primitives of these services are provided in 3GPP TS 43.051 and 3GPP TS 23.110. + +- General Control; +- Notification; +- Dedicated control. + +The RRC layer provides the MS GERAN portion of signalling connections to the upper layers to support the exchange of upper layer's information flow. The signalling connection is used between the mobile station and the core network to transfer upper layer information. For each core network domain, at most one signalling connection may exist at the same time. The RRC layer maps the signalling connections for one MS on a single RRC connection. For the upper layer data transfer on signalling connections, the RRC layer supports the discrimination between two different classes, named "High priority" (corresponding to "SAPI 0" when using RR) realised using SRB3 and "Low priority" (corresponding to "SAPI 3" when using RR) realised using SRB4. + +--- + +## 5 Services expected from lower layers + +### 5.1 Services required from layer 2 and physical layers + +RRC uses RLC/MAC as layer 2 in the control plane, except for operation on the BCCH, where the data link layer as specified in 3GPP TS 44.006 is used (see 3GPP TS 43.051). + +### 5.2 Signalling Radio Bearers + +The Radio Bearers used for transferring signalling messages are called Signalling Radio Bearers (SRBs). The SRBs are defined as: + +- SRB1 is used to carry RRC signaling performed in support of Access Stratum specific needs (RLC operates in unacknowledged mode). +- SRB2 is used to carry RRC signaling performed in support of Access Stratum specific needs (RLC operates in acknowledged mode). +- SRB3 is used to carry RRC signaling performed in support of Non-Access Stratum specific needs (RLC operates in acknowledged mode). +- SRB4 is used to carry RRC signaling performed in support of Non-Access Stratum specific needs (RLC operates in acknowledged mode). + +--- + +## 6 RRC Protocol modes and states + +### 6.1 General + +An overall picture of the transitions between RR modes of operation and RRC states and modes is in Figure 6.1.1. The RRC modes are RRC-Idle mode and RRC-Connected mode. RRC-Connected mode consists of three different RRC states RRC-Cell\_Shared, RRC-Cell\_Dedicated and RRC-GRA\_PCH. The RR modes of operation are RR Dedicated mode, RR Group receive mode, RR Group transmit mode, RR Packet Idle mode, RR Packet Transfer mode and RR DTM (see 3GPP TS 43.064). + +RR Group receive mode and RR Group transmit Mode are not described in Figure 6.1.1. + +![Figure 6.1.1: Transitions between RR modes of operation and RRC states and modes. The diagram is split into two main columns: 'Iu mode' on the left and 'A/Gb mode' on the right. In 'Iu mode', there is an 'RRC Connected Mode' box containing three states: 'RRC Cell_Dedicated' (top), 'RRC GRA_PCH' (left), and 'RRC Cell_Shared' (right). Arrows show transitions between these three states. Below this is an 'RRC Idle Mode' box. Arrows point from 'RRC Cell_Dedicated', 'RRC Cell_Shared', and 'RRC GRA_PCH' down to 'RRC Idle Mode'. In 'A/Gb mode', there is an 'RR Idle Mode/Packet Idle Mode' box at the bottom. Above it are three states: 'RR Dedicated Mode' (top), 'RR Packet Transfer Mode' (left), and 'RR Dual Transfer Mode' (right). Arrows show transitions between these three states. Arrows point from 'RR Dedicated Mode', 'RR Packet Transfer Mode', and 'RR Dual Transfer Mode' down to 'RR Idle Mode/Packet Idle Mode'. A dashed double-headed arrow labeled 'Handover' connects 'RRC Cell_Dedicated' in 'Iu mode' to 'RR Dedicated Mode' in 'A/Gb mode'. A dashed double-headed arrow labeled 'Cell reselection' connects 'RRC Idle Mode' in 'Iu mode' to 'RR Idle Mode/Packet Idle Mode' in 'A/Gb mode'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 6.1.1: Transitions between RR modes of operation and RRC states and modes. The diagram is split into two main columns: 'Iu mode' on the left and 'A/Gb mode' on the right. In 'Iu mode', there is an 'RRC Connected Mode' box containing three states: 'RRC Cell\_Dedicated' (top), 'RRC GRA\_PCH' (left), and 'RRC Cell\_Shared' (right). Arrows show transitions between these three states. Below this is an 'RRC Idle Mode' box. Arrows point from 'RRC Cell\_Dedicated', 'RRC Cell\_Shared', and 'RRC GRA\_PCH' down to 'RRC Idle Mode'. In 'A/Gb mode', there is an 'RR Idle Mode/Packet Idle Mode' box at the bottom. Above it are three states: 'RR Dedicated Mode' (top), 'RR Packet Transfer Mode' (left), and 'RR Dual Transfer Mode' (right). Arrows show transitions between these three states. Arrows point from 'RR Dedicated Mode', 'RR Packet Transfer Mode', and 'RR Dual Transfer Mode' down to 'RR Idle Mode/Packet Idle Mode'. A dashed double-headed arrow labeled 'Handover' connects 'RRC Cell\_Dedicated' in 'Iu mode' to 'RR Dedicated Mode' in 'A/Gb mode'. A dashed double-headed arrow labeled 'Cell reselection' connects 'RRC Idle Mode' in 'Iu mode' to 'RR Idle Mode/Packet Idle Mode' in 'A/Gb mode'. + +Figure 6.1.1: Transitions between RR modes of operation and RRC states and modes. + +## 6.2 Relation between Iu mode and A/Gb mode + +### 6.2.1 Handover between Iu and A/Gb modes + +When a handover which results in change from *Iu mode* (i.e. from the RRC-Cell\_Dedicated state) to *A/Gb mode* is performed, the RR dedicated mode of operation shall be entered. + +When a handover which results in change from *A/Gb mode* (i.e. from the RR dedicated mode of operation) to *Iu mode* is performed, the RRC-Cell\_Dedicated state shall be entered. If handover to *Iu mode* is triggered in RR dual transfer mode of operation, the RR dedicated mode of operation shall be entered before the handover is initiated. + +### 6.2.2 Cell reselection between Iu and A/Gb mode + +Cell reselection in this sub-clause refers to aborting the operation in the old cell and switching to the new selected cell. + +When a cell reselection which results in change from *Iu mode* (i.e. from the RRC-Idle Mode) to *A/Gb mode* is performed, the RR Idle/ RR Packet Idle mode of operation shall be entered. If cell reselection is triggered in RRC-Cell\_Shared or RRC-GRA\_PCH state, the RRC-Idle mode shall be entered before the cell reselection is initiated. + +When a cell reselection which results in change from *A/Gb mode* (i.e. from the RR Idle/RR packet Idle mode of operation) to *Iu mode*, is performed the RRC-Idle mode shall be entered. If cell reselection is triggered in RR Packet Transfer mode of operation, the RR packet Idle mode of operation shall be entered before the cell reselection is initiated. + +## 6.2a Relation between GERAN Iu mode RRC and UTRA RRC + +### 6.2a.1 Handover between GERAN Iu mode and UTRAN + +When a handover which results in change from GERAN *Iu mode* (i.e. RRC-Cell\_Dedicated state) to UTRAN is performed, the UTRAN RRC connected mode of operation shall be entered. + +When a handover which results in change from UTRAN (i.e. from the UTRA RRC Cell\_DCH state) to GERAN *Iu mode* is performed, the RRC-Cell\_Dedicated state shall be entered. + +### 6.2a.2 Cell reselection between GERAN Iu mode and UTRAN + +Cell reselection in this sub-clause refers to aborting the operation in the old cell and switching to the new selected cell. + +When a cell reselection which results in change from GERAN *Iu mode* to UTRAN is performed, when the MS is in RRC-Idle mode, the Idle mode of operation shall be entered. + +When a cell reselection which results in change from GERAN *Iu mode* to UTRAN is performed, when the MS is in GERAN RRC-Cell\_Shared state, the MS shall initiate the cell update procedure and enter the UTRAN RRC CELL\_FACH state. If the cell update is rejected by UTRAN, the MS shall release the RRC connection according to the cell update failure case and enter Idle mode. + +When a cell reselection which results in change from GERAN *Iu mode* to UTRAN is performed, when the MS is in GERAN RRC-GRA\_PCH state, the MS shall enter the UTRAN RRC URA\_PCH state. If the GRA identity which the MS had been assigned to in GERAN is not present in the list of URA identities broadcast in the UTRAN cell, the MS shall initiate the UTRAN URA update procedure. If the URA update is rejected by UTRAN, the MS shall release the RRC connection according to the URA update failure case and enter Idle mode. + +When a cell reselection which results in change from UTRAN to GERAN *Iu mode* is performed, when the MS is in UTRAN RRC-Cell\_FACH or Cell\_PCH state, the MS shall initiate the cell update procedure and enter the GERAN RRC Cell Shared state. If the cell update is rejected by GERAN, the MS shall release the RRC connection according to the cell update failure case and enter RRC Idle mode in GERAN *Iu mode*. + +When a cell reselection which results in change from UTRAN to GERAN *Iu mode* is performed, when the MS is in UTRAN RRC-URA\_PCH state, the MS shall enter the GERAN RRC GRA\_PCH state. . If the URA identity which the MS had been assigned to in UTRAN is not present in the list of GRA identities broadcast in the GERAN cell, the MS shall initiate the GERAN GRA update procedure. If the GRA update is rejected by GERAN, the MS shall release the RRC connection according to the GRA update failure case and enter RRC Idle mode in GERAN *Iu mode*. + +## 6.3 RR modes of operation + +The RR modes of operation are described in 3GPP TS 43.064. + +## 6.4 RRC modes and states + +### 6.4.1 RRC-Idle Mode + +#### 6.4.1.1 General + +After power on having selected the *Iu mode*, the MS enters RRC-Idle mode. The MS stays in RRC-Idle mode until a successful establishment of a RRC Connection. In RRC-Idle mode the connection of the MS is closed on all layers of the access stratum. In RRC-Idle mode the MS is identified by Non-Access stratum identities such as IMSI, TMSI and P-TMSI. In addition, the GERAN has no own information about the individual MS's in RRC-Idle mode, and it can only address e.g. all MS's in a cell (broadcasting) or all MS's monitoring a paging occasion. + +#### 6.4.1.2 Transition from RRC-Idle Mode to RRC-Connected mode + +The transition to the RRC-Connected mode from the RRC-Idle mode can only be initiated by the MS by transmitting a request for an RRC Connection. The event is triggered by a request from upper layers in the MS. + +At RRC connection establishment the MS is assigned a GERAN radio network temporary identity (G-RNTI) to be used as MS identity on both common control channels and traffic channels. + +When the MS receives a message from the network that confirms the RRC connection establishment, the MS enters the RRC-Connected mode. The RRC-Connected mode is characterised by three states: RRC-Cell\_Shared, RRC-Cell\_Dedicated and RRC-GRA\_PCH. + +### 6.4.2 RRC-Connected mode: RRC-Cell\_Shared state + +#### 6.4.2.1 General + +RRC-Cell\_Shared state is characterized by: + +- no dedicated basic physical subchannel (DBPSCH) is allocated to the MS. +- the position of the MS is known by GERAN on cell level according to the cell where the MS last made a cell update. + +In RRC-Cell\_Shared state the MS shall perform the following actions: + +- 1> initiate a Cell Update procedure on cell change to *Iu mode* in another GERAN or UTRAN cell; +- 1> transmit signalling messages and user data in the uplink and/or the downlink using PDTCH when the MS is assigned use of those resources; +- 1> the management of radio resources within the cell is handled at MAC level; +- 1> listen to the PBCCH control channel of the serving cell for the decoding of system information messages; +- 1> listen to neighbouring cells for neighbour cell measurements (see 3GPP TS 45.008); +- 1> use G-RNTI assigned in the current cell as the MS identity on common control channels. + +NOTE: In that state, if the network wants to initiate any activity, no paging request is required to be sent. The network can directly allocate radio resources to the MS. + +#### 6.4.2.2 Transition from RRC-Cell\_Shared state to RRC-Idle Mode + +The transition to RRC-Idle Mode is realised through the release of the RRC connection. + +#### 6.4.2.3 Transition from RRC-Cell\_Shared state to RRC-Cell\_Dedicated state + +The transition from RRC-Cell\_Shared state to RRC-Cell\_Dedicated state occurs when a DBPSCH is allocated to the MS. + +#### 6.4.2.4 Transition from RRC-Cell\_Shared state to RRC-GRA\_PCH state + +The transition occurs when GERAN orders the MS to move to RRC-GRA\_PCH state via explicit signaling. + +When such a transition occurs, the mobile station shall abort any TBF in progress by immediately ceasing to decode the downlink, ceasing to transmit on the uplink, stopping all RLC/MAC timers except for timers related to measurement reporting, prior to moving to RRC-GRA\_PCH state. + +#### 6.4.2.5 Radio resource allocation tasks + +RRC is in this state responsible for allocating dedicated basic physical subchannels, which causes the MS to enter the RRC-Cell\_Dedicated state. MAC is responsible for allocating / reallocating / releasing shared basic physical subchannels (SBPSCH) (see 3GPP TS 44.160). This allocation of the PDTCHs by MAC is done according to the QoS class of the radio bearer and multislot capability of the MS. The RRC provides the MAC with QoS class and indication of the MS multislot capability. + +#### 6.4.2.6 RRC connection mobility tasks + +In RRC-Cell\_Shared state the MS shall initiate a Cell Update procedure when: + +- 1> a new GERAN cell has been selected and the MS operates in *Iu mode*, or +- 1> a UTRAN cell has been selected. +- 1> when T305 in the MS expires and the MS is operating in *Iu mode*. + +When the GERAN cell has been selected that would require the MS to operate in the *A/Gb mode* then the MS shall enter the RRC-Idle Mode, enter RR Idle or RR Packet Idle Mode of operation. Access in the cell will then be made according to the *A/Gb mode* procedures. + +#### 6.4.2.7 MS measurements + +MAC is responsible for measurement reporting, using the procedures defined in 3GPP TS 44.060. + +### 6.4.3 RRC-Connected mode: RRC-Cell\_Dedicated state + +#### 6.4.3.1 General + +RRC-Cell\_Dedicated state is characterized by: + +- the MS is assigned one or more dedicated basic physical subchannels (see 3GPP TS 43.051) in the uplink and downlink, which it can use anytime. Furthermore, the MS may be assigned one or more shared basic physical subchannels. +- the position of the MS is known by GERAN on cell level. + +In RRC-Cell\_Dedicated state the MS shall perform the following actions: + +- 1> perform necessary procedures for measurement reporting; +- 1> listen to neighbouring cells for neighbouring cell measurements (see 3GPP TS 45.008); +- 1> perform a handover procedure of the dedicated basic physical subchannels on cell change of another GERAN or UTRAN cell; +- 1> transmit signalling message in the uplink using available signalling radio bearers. + +#### 6.4.3.2 Transition from RRC-Cell\_Dedicated state to RRC-Cell\_Shared state + +The transition occurs when all the dedicated basic physical subchannels are released and + +- 1> shared basic physical subchannels exist; or +- 1> no shared basic physical subchannels exist and the network indicates transition to the RRC-Cell\_Shared state. + +#### 6.4.3.3 Transition from RRC-Cell\_Dedicated state to RRC-Idle Mode + +The transition to RRC-Idle mode is realised through the release of the RRC connection. + +#### 6.4.3.4 Transition from RRC-Cell\_Dedicated state to RRC-GRA\_PCH state + +The transition occurs when GERAN orders the MS to move to the RRC-GRA\_PCH state via explicit signalling. + +When such a signalling is received, the mobile station shall release all the allocated dedicated basic physical subchannel(s) and, if any, all the shared basic physical subchannels, prior to moving to RRC-GRA\_PCH state. + +#### 6.4.3.5 Radio resource allocation tasks + +RRC is responsible for allocating new dedicated basic physical subchannels, while MAC or RRC are responsible for allocation of new shared basic physical subchannels depending on the MAC control state. RRC is also responsible for intra-cell handovers of dedicated basic physical sub-channels. + +#### 6.4.3.6 RRC connection mobility tasks + +RRC connection mobility tasks are realised in RRC-Cell\_Dedicated state using RRC handover procedures. + +#### 6.4.3.7 MS measurements + +MS measurement results are signaled using RRC measurement procedures. + +### 6.4.4 RRC-Connected mode: RRC-GRA\_PCH state + +#### 6.4.4.1 General + +The RRC-GRA\_PCH state is characterized by: + +- no physical subchannel is allocated to the MS. +- the MS may use DRX for monitoring a PCCH. +- no uplink activity is possible. +- the location of the MS is known on GERAN Registration area level. + +In this state the MS performs the following actions: + +- 1> monitor the paging occasions according to the DRX cycle and receive paging information on the PCCH; +- 1> listen to the PBCCH control channel of the serving cell for the decoding of system information messages; +- 1> initiate a GRA Update procedure upon GRA change. + +If the network wants to initiate any activity, it shall make a paging request on the PCCH logical channel within the GRA where the MS is. + +GRA updating is initiated by the MS, which, upon the detection of the new GERAN registration area, sends the network the registration area update information to the new cell. Any activity causes a transition to either the RRC-Cell\_Shared state or the RRC-Cell\_Dedicated state, depending on the activity. + +#### 6.4.4.2 Transition from RRC-GRA\_PCH state to RRC-Cell\_Shared state + +The transition can occur due to GRA update, cell update or answer to paging. If there has been a cell change since last GRA update, the MS has to do immediately a cell update except when GRA update is initiated. + +#### 6.4.4.3 Transition from RRC-GRA\_PCH state to RRC-Cell\_Dedicated state + +When the MS is in RRC-GRA\_PCH state, the MS may request a radio resource to answer to a paging message or to perform a GRA/Cell Update procedure. The network may choose to allocate a dedicated resource in which case the MS enters RRC-Cell\_Dedicated state. + +#### 6.4.4.4 Radio resource allocation tasks + +No radio resource allocation tasks are executed within this state. In case of transition to RRC-Cell\_Shared state is needed, the MAC is responsible for allocating the shared physical subchannels. In case of transition to RRC-Cell\_Dedicated state is needed, the RRC is responsible for allocating the physical subdedicated channel. + +#### 6.4.4.5 RRC connection mobility tasks + +In the RRC-GRA\_PCH state the location of a MS is known on GERAN Registration area level. + +In this state, the MS mobility is performed through Cell Reselection procedures. The MS shall perform cell reselection and upon selecting a new GERAN cell belonging to a GRA which does not match the GRA used by the MS, the MS shall move to RRC-Cell\_Shared state and initiate a GRA update towards the network. After the GRA Update procedure has been performed, the MS shall change its state back to RRC-GRA\_PCH state if neither the MS nor the network has any more data to transmit. + +In RRC-GRA\_PCH state the MS shall initiate: + +- 1> a GRA Update procedure when a new GERAN cell has been selected that does not belong to the current registration area and the MS operates in Iu mode, or +- 1> a GRA Update procedure when T305 in the MS expires and the MS is operating in Iu mode, or +- 1> a URA Update procedure when a UTRAN cell has been selected that does not belong to the current registration area (see 3GPP TS 25.331). + +When the GERAN cell has been selected that would require the MS to operate in the *A/Gb mode* then the MS shall enter the RRC-Idle mode, then enter RR Idle or RR Packet Idle Mode of operation. Access in the cell will then be made according to the *A/Gb mode* procedures. + +#### 6.4.4.6 MS measurements + +The MS monitors the broadcast channels on its own and neighbouring cells and identifies the need for GRA updating. No measurement reports are sent to the network in this state. + +#### 6.4.4.7 Transfer and update of system information + +The MS shall listen to the PBCCH to acquire a valid system information. + +## 7 Radio Resource Control procedures + +### 7.1 General + +The mobile station can operate either in *A/Gb mode* or in *Iu mode*. How mobile station selects the operation mode is specified in 3GPP TS 23.221. The behaviour of mobile stations operating in *A/Gb mode* is specified in 3GPP TS 44.018. + +After the reception of a message which invoked a procedure, the MS shall be prepared to receive and act on another message which invokes the second procedure. Whether this second invocation of a procedure (transaction) is accepted or rejected by the MS is specified in the sub-clauses that specifies the procedure. On receiving a message the MS shall first apply integrity check as appropriate and then proceed with error handling as specified in clause 8 and 9 before continuing on with the procedure as specified in the relevant sub-clause. The RRC entity in the MS shall consider PDUs to have been transmitted when they are submitted to the lower layers. If the RRC entity in the MS submits a message for transmission using AM RLC, it shall consider the message successfully transmitted when GERAN reception of all relevant PDUs is acknowledged by RLC. + +### 7.2 Change of channels in case of handover + +#### 7.2.1 Change of channel serving SRB1 + +The RLC procedures for unacknowledged mode, described in 3GPP TS 44.160, do not provide protection against message loss or duplication. No functionality for handling SRB1 during change of channels is defined, as SRB1 is used by RRC procedures that are not very sensitive to message loss or duplication. + +#### 7.2.2 Change of channel serving SRB2 + +The RLC procedures for acknowledged mode, described in 3GPP TS 44.160, provide delivery of received messages to the upper layers in the order they were originally transmitted, provide protection against message loss, but do not provide protection against message duplication. SRB2 is used by RRC procedures that need reliable transport service and are sensitive to message duplication. + +When changing channel, the RRC layer will request the RLC layer to suspend operation on SRB2 before the mobile station leaves the old channel. When the channel change has been completed, the RRC layer station will request the RLC layer to resume operation on SRB2. The RLC layer suspend/resume procedures are described in 3GPP TS 44.160. + +It may happen that the RLC layer duplicates a message, if it has been transmitted but not yet completely acknowledged within the RLC layer, before the mobile station leaves the old channel. However, the RRC layer controls the channels change in such a way that duplication of RRC messages does not occur. + +#### 7.2.3 Change of channel serving SRB3 + +The RLC procedures for acknowledged mode, described in 3GPP TS 44.160, provide delivery of received messages to the upper layers in the order they were originally transmitted, provide protection against message loss, but do not provide protection against message duplication. SRB3 is used for RRC messages carrying upper layer (NAS) signalling. If these messages are sensitive to message duplication, the upper layer protocol should define its own protection mechanism. + +#### 7.2.4 Change of channel serving SRB4 + +The RLC procedures for acknowledged mode, described in 3GPP TS 44.160, provide delivery of received messages to the upper layers in the order they were originally transmitted, provide protection against message loss, but do not provide protection against message duplication. SRB4 is used for RRC messages carrying upper layer (NAS) signalling. If these messages are sensitive to message duplication, the upper layer protocol should define its own protection mechanism. + +## 7.3 System information broadcasting + +### 7.3.1 General + +The purpose of this procedure is to broadcast SYSTEM INFORMATION (SI) messages from the GERAN to MSs in a cell. + +GERAN is required to broadcast SI messages on BCCH as specified in 3GPP TS 44.018. + +### 7.3.2 Broadcast of Iu mode specific System Information + +The support of *Iu mode* shall be indicated in SYSTEM INFORMATION TYPE 3 message sent on BCCH. In addition, the support of *Iu mode* shall be indicated in either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages. The SI3, SI4, SI7 and SI8 messages contain the CBQ3 parameter that indicates if *Iu mode* is supported in the cell (see 3GPP TS 44.018). + +If *Iu mode* is supported and Gb mode is not supported in the cell, SYSTEM INFORMATION TYPE 13alt message shall be sent and the mobile station shall read SI13alt message. SI 13 message is not sent in this case. SI13alt message shall not be sent if *Iu mode* is not supported. + +If Gb mode is supported, SYSTEM INFORMATION TYPE 13 message shall be sent and the mobile station shall read SI 13 message in this case. SI13alt message is not sent in this case. Additional requirements for the broadcast of system information in a cell supporting *Iu mode* and *Gb mode* are specified in 3GPP TSs 44.060 and 44.160. + +Figure 7.3.2.1 presents the behaviour of *Iu mode* only capable mobile station and figure 7.3.2.2 presents the behaviour of *A/Gb mode* and *Iu mode* capable mobile station on BCCH (see 3GPP TS 44.018). + +![Flowchart illustrating the behaviour of Iu mode only capable MS on BCCH. The process starts with 'MS Power-On' or 'MS reselects from PBCCH', leading to 'MS finds BCCH' or 'MS reselects a new cell'. Both lead to 'MS reads SI3 or SI4 or SI7 and SI8 to acquire GPRS INDICATOR and/or CBQ3'. From there, four paths emerge based on CBQ3 and GPRS INDICATOR values. If CBQ3 indicates Iu mode is not supported, 'No service' is reached. If CBQ3 indicates Iu mode capable MSs are barred, 'MS attempts to reselect a new cell' is reached. If GPRS INDICATOR is not present and CBQ3 indicates Iu mode is supported, an 'Iu mode' decision leads to 'MS reads SI13alt'. If GPRS INDICATOR is present and CBQ3 indicates Iu mode is supported, an 'Iu mode' decision leads to 'MS reads SI13'. Both 'MS reads SI13alt' and 'MS reads SI13' lead to 'MS leaves current BCCH, tunes to the indicated PBCCH'.](49a49278cad196bdfe0db6b4dd1be7fd_img.jpg) + +``` + +graph TD + A([MS Power-On]) --> B[MS finds BCCH] + C([MS reselects from PBCCH]) --> D[MS reselects a new cell] + B --> E[MS reads SI3 or SI4 or SI7 and SI8 to acquire GPRS INDICATOR and/or CBQ3] + D --> E + E --> F1[CBQ3 indicates Iu mode is not supported.] + E --> F2[CBQ3 indicates Iu mode capable MSs are barred] + E --> F3[GPRS INDICATOR is not present and CBQ3 indicates Iu mode is supported] + E --> F4[GPRS INDICATOR is present and CBQ3 indicates Iu mode is supported] + F1 --> G{No service} + F2 --> H[MS attempts to reselect a new cell] + F3 --> I{Iu mode} + F4 --> J{Iu mode} + I --> K[MS reads SI13alt] + J --> L[MS reads SI13] + K --> M[MS leaves current BCCH, tunes to the indicated PBCCH] + L --> M + +``` + +Flowchart illustrating the behaviour of Iu mode only capable MS on BCCH. The process starts with 'MS Power-On' or 'MS reselects from PBCCH', leading to 'MS finds BCCH' or 'MS reselects a new cell'. Both lead to 'MS reads SI3 or SI4 or SI7 and SI8 to acquire GPRS INDICATOR and/or CBQ3'. From there, four paths emerge based on CBQ3 and GPRS INDICATOR values. If CBQ3 indicates Iu mode is not supported, 'No service' is reached. If CBQ3 indicates Iu mode capable MSs are barred, 'MS attempts to reselect a new cell' is reached. If GPRS INDICATOR is not present and CBQ3 indicates Iu mode is supported, an 'Iu mode' decision leads to 'MS reads SI13alt'. If GPRS INDICATOR is present and CBQ3 indicates Iu mode is supported, an 'Iu mode' decision leads to 'MS reads SI13'. Both 'MS reads SI13alt' and 'MS reads SI13' lead to 'MS leaves current BCCH, tunes to the indicated PBCCH'. + +Figure 7.3.2.1: Behaviour of *Iu mode* only capable MS on BCCH. + +![Flowchart illustrating the behaviour of A/Gb and lu modes capable MS on BCCH. The process starts with three initial states: MS Power-On, MS is camping on BCCH, and MS reselects from PBCH. All three lead to a common step: MS reads SI3 or SI4 or SI7 and SI8 to acquire GPRS INDICATOR and/or CBQ3. From there, four paths emerge based on CBQ3 and GPRS INDICATOR values. Path 1: CBQ3 indicates lu mode is not supported -> A/Gb mode -> MS camps on BCCH. Path 2: CBQ3 indicates lu mode capable MSs are barred -> MS attempts to reselect a new cell. Path 3: GPRS INDICATOR is not present and CBQ3 indicates lu mode is supported -> lu mode -> MS reads SI13alt. Path 4: GPRS INDICATOR is present and CBQ3 indicates lu mode is supported -> lu mode -> MS reads SI13. Both SI13alt and SI13 lead to a final step: MS leaves current BCCH, tunes to the indicated PBCH.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +graph TD + A([MS Power-On]) --> B[MS finds BCCH] + C([MS is camping on BCCH]) --> D[MS reads SI3 or SI4 or SI7 and SI8 to acquire GPRS INDICATOR and/or CBQ3] + E([MS reselects from PBCH]) --> F[MS reselects a new cell] + B --> D + F --> D + D --> G[CBQ3 indicates lu mode is not supported] + D --> H[CBQ3 indicates lu mode capable MSs are barred] + D --> I[GPRS INDICATOR is not present and CBQ3 indicates lu mode is supported] + D --> J[GPRS INDICATOR is present and CBQ3 indicates lu mode is supported] + G --> K{A/Gb mode} + K --> L[MS camps on BCCH] + H --> M[MS attempts to reselect a new cell] + I --> N{lu mode} + N --> O[MS reads SI13alt] + J --> P{lu mode} + P --> Q[MS reads SI13] + O --> R[MS leaves current BCCH, tunes to the indicated PBCH] + Q --> R + +``` + +Flowchart illustrating the behaviour of A/Gb and lu modes capable MS on BCCH. The process starts with three initial states: MS Power-On, MS is camping on BCCH, and MS reselects from PBCH. All three lead to a common step: MS reads SI3 or SI4 or SI7 and SI8 to acquire GPRS INDICATOR and/or CBQ3. From there, four paths emerge based on CBQ3 and GPRS INDICATOR values. Path 1: CBQ3 indicates lu mode is not supported -> A/Gb mode -> MS camps on BCCH. Path 2: CBQ3 indicates lu mode capable MSs are barred -> MS attempts to reselect a new cell. Path 3: GPRS INDICATOR is not present and CBQ3 indicates lu mode is supported -> lu mode -> MS reads SI13alt. Path 4: GPRS INDICATOR is present and CBQ3 indicates lu mode is supported -> lu mode -> MS reads SI13. Both SI13alt and SI13 lead to a final step: MS leaves current BCCH, tunes to the indicated PBCH. + +Figure 7.3.2.2: Behaviour of A/Gb and lu modes capable MS on BCCH. + +## 7.4 Paging procedure + +### 7.4.1 General + +The GERAN will start a Paging Request procedure to trigger: + +- 1> an Initial Direct Transfer procedure for CN originated paging; or +- 1> a Cell Update procedure for GERAN initiated paging. + +Paging is done by the GERAN on the PCCH or PACCH (when available) when the MS is in RRC-Idle mode, RRC-Cell\_Shared state or RRC-GRA\_PCH state and on SRB2 when the MS is in RRC-Cell\_Dedicated state. + +### 7.4.2 Paging initiation in RRC-Idle mode, RRC-Cell\_Shared or RRC-GRA\_PCH state + +#### 7.4.2.1 General + +The paging initiation in RRC-Idle mode, RRC-Cell\_Shared state or RRC-GRA\_PCH state is done by sending a PAGING REQUEST service primitive to the GERAN MAC layer. + +![Sequence diagram of the Paging Request procedure. It shows four lifelines: MS RRC, MS MAC, GERAN MAC, and GERAN RRC. The sequence starts with a 'Paging Request Primitive' from GERAN RRC to GERAN MAC. GERAN MAC then sends a 'Packet Paging Request' to MS MAC. Finally, MS MAC sends a 'Paging Indication Primitive' to MS RRC.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant GERAN_RRC as GERAN RRC + participant GERAN_MAC as GERAN MAC + participant MS_MAC as MS MAC + participant MS_RRC as MS RRC + Note right of GERAN_RRC: Error: Reference source not + GERAN_RRC->>GERAN_MAC: Paging Request Primitive + GERAN_MAC->>MS_MAC: Packet Paging Request + MS_MAC->>MS_RRC: Paging Indication Primitive + +``` + +Sequence diagram of the Paging Request procedure. It shows four lifelines: MS RRC, MS MAC, GERAN MAC, and GERAN RRC. The sequence starts with a 'Paging Request Primitive' from GERAN RRC to GERAN MAC. GERAN MAC then sends a 'Packet Paging Request' to MS MAC. Finally, MS MAC sends a 'Paging Indication Primitive' to MS RRC. + +**Figure 7.4.2.1.1: Paging Request procedure** + +This procedure is used to initiate transmission of paging information by the GERAN MAC to an MS in RRC-Idle mode, RRC-Cell\_Shared state, or RRC-GRA\_PCH state. Upper layers in the network may request paging, to e.g. establish a signalling connection between a mobile station and the CN. The GERAN may initiate paging of an MS in RRC-GRA\_PCH state or {RRC-Cell\_Shared, MAC-Idle state} to trigger a Cell Update procedure in order to establish a signalling connection between the network and this MS. + +An MS may use Discontinuous Reception (DRX) to reduce its power consumption. An MS in non-DRX mode monitors all paging blocks on the monitored PCCCH. An MS in DRX mode needs only to monitor the blocks corresponding to its paging group in order to reduce its battery consumption, see 3GPP TS 44.160. + +#### 7.4.2.2 Initiation + +GERAN RRC initiates the Paging procedure by transmitting a PAGING REQUEST service primitive to the GERAN MAC sublayer. + +The GERAN shall set the IEs in the PAGING service primitive as follows: + +- 1> if the Paging procedure was initiated by the CN +- 2> if the MS is in RRC-Cell\_Shared or RRC-GRA\_PCH state, then + - 3> the *MS Identity* IE shall be set to G-RNTI; + - 3> the *Paging Record Type Identifier* IE shall be set to the value determined by the MS identity received in the CN paging request; + - 3> the *CN Domain identity* IE shall be set to the value received in the CN paging request; + - 3> if a value for Paging Cause is received from the CN, then the GERAN RRC shall: + - 4> set the *Paging Cause* IE in the PAGING service primitive to the value received in the CN paging request; . + - 3> if no value for Paging Cause is received from the CN then the GERAN RRC shall: + - 4> set the *Paging Cause* IE in the PAGING service primitive to the value "Terminating – cause unknown". +- 2> if the MS is in RRC-Idle mode then: + - 3> the *MS Identity* IE shall be set to the value received from the CN; + - 3> the *CN Domain Identity* IE shall be set to the value received in the CN paging request; + - 3> if a value for Paging Cause is received from the CN then the GERAN RRC shall: + - 4> set the *Paging Cause* IE in the PAGING service primitive to the value received in the CN paging request; + - 3> if no value for Paging Cause is received from the CN then the GERAN RRC shall: + - 4> set the *Paging Cause* IE in the PAGING service primitive to the value "Terminating – cause unknown". + +- 1> if the Paging procedure was initiated by the GERAN, the GERAN RRC shall: + - 2> set the *MS Identity* IE to G-RNTI; and + - 2> the procedure ends. + +NOTE: If the Paging procedure is initiated by the GERAN, the GERAN shall indicate this to the MS by the absence of any information in the PAGING message other than the G-RNTI IE. + +### 7.4.2.3 Reception of a PAGING INDICATION service primitive + +The MS RRC in RRC-Idle mode, RRC-GRA\_PCH state or RRC-Cell\_Shared state shall receive the paging information in a PAGING INDICATION service primitive from the MS MAC layer. + +If the MS is in RRC-Idle mode, for each MS paged in the PAGING INDICATION service primitive, the MS shall: + +- 1> if the *MS Identity* IE is present in the message and it is a CN identity + - 2> compare the *MS Identity* IE with all of its allocated CN MS identities; + - 2> if one match is found: + - 3> forward the *MS Identity* IE, the *CN Domain Identity* IE and the *Paging cause* IE to upper layers; and + - 3> ignore any other paging information that may be present in the PAGING service primitive; +- 1> otherwise: + - 2> ignore the PAGING service primitive. + +If the MS is in RRC-Cell\_Shared or RRC-GRA\_PCH state, for each MS paged in the PAGING INDICATION service primitive, the GERAN RRC shall: + +- 1> if the *MS Identity* IE is a GERAN identity; and + - 2> if this G-RNTI is the same as the G-RNTI allocated to the MS: + - 3> if paging request contains page info with CN domain identity + - 4> forward the *MS identity* IE, the *CN Domain Identity* IE and the *Paging Cause* IE to upper layers; + - 3> otherwise + - 4> initiate the Cell Update procedure with the cause 'paging response' as defined in sub-clause 7.8; and + - 4> forward the *CN Domain Identity* IE if present, the *Paging Record Type Identifier* IE if present and the *Paging cause* IE if present to upper layers; and + - 3> ignore any other paging information that may be present in the primitive; +- 1> otherwise + - 2> ignore the Paging primitive. + +## 7.4.3 Paging initiation in RRC-Cell\_Dedicated state + +![Sequence diagram showing the Dedicated Paging Request procedure. A GERAN node sends a DEDICATED PAGING REQUEST message to an MS node.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +``` + +sequenceDiagram + participant GERAN + participant MS + Note left of GERAN: Initiate Dedicated Paging Request + GERAN->>MS: DEDICATED PAGING REQUEST + +``` + +Sequence diagram showing the Dedicated Paging Request procedure. A GERAN node sends a DEDICATED PAGING REQUEST message to an MS node. + +Figure 7.4.3.1.1: Dedicated Paging Request procedure + +### 7.4.3.1 General + +This procedure is used to transmit dedicated paging information to one MS in RRC-Cell\_Dedicated state. + +### 7.4.3.2 Initiation + +For an MS in RRC-Cell\_Dedicated state the GERAN initiates the procedure by transmitting a DEDICATED PAGING REQUEST message on the SRB2 assigned to the MS. If not stated otherwise, the GERAN may initiate the Dedicated Paging Request when another RRC procedure is ongoing, and in this case the state of the latter procedure shall not be affected. + +In the DEDICATED PAGING REQUEST message, the GERAN RRC shall set the IE "*Paging Cause*", the IE "*CN Domain Identity*", the IE "*Paging Record Type Identifier*" respectively to the Paging Cause, the CN domain Indicator and the Paging Record Type Identifier received from upper layers. + +If no cause for paging is received from upper layers, GERAN RRC shall set the IE "*Paging Cause*" to the value "Terminating – cause unknown". + +### 7.4.3.3 Reception of a DEDICATED PAGING REQUEST message by the MS + +When the MS receives a DEDICATED PAGING REQUEST message on SRB 2, it shall not affect the state of any other ongoing RRC procedures, if not stated otherwise. + +Upon receipt of a DEDICATED PAGING REQUEST message the MS shall: + +- 1) forward the *Paging Cause* IE, the *CN Domain Identity* IE and the *Paging Record Type Identifier* IE to upper layers; +- 1) the procedure ends. + +## 7.4.4 Abnormal cases + +If the MS receives a DEDICATED PAGING REQUEST message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE, the MS shall perform procedure specific error handling as follows: + +- 1) transmit an RRC STATUS message on the uplink SRB2; +- 1) include the IE "*Identification of Received Message*"; +- 1) set the IE "*Received Message Type*" to DEDICATED PAGING REQUEST; +- 1) include the *Protocol Error Information* IE and set the content to the value of the variable PROTOCOL\_ERROR\_INFORMATION. +- 1) if the RRC STATUS message has been submitted to lower layers for transmission: + - 2) continue with any ongoing processes and procedures as if the invalid DEDICATED PAGING REQUEST message was not received. + +## 7.5 RRC Connection management procedures + +### 7.5.1 RRC connection establishment + +![Sequence diagram for RRC Connection Establishment where the network accepts the request. The diagram shows three messages between the MS (Mobile Station) and GERAN (GSM EDGE Radio Access Network): 1. MS sends RRC CONNECTION REQUEST to GERAN. 2. GERAN responds with RRC CONNECTION SETUP to MS. 3. MS completes the setup with RRC CONNECTION SETUP COMPLETE to GERAN.](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + Note left of MS: + MS->>GERAN: RRC CONNECTION REQUEST + GERAN-->>MS: RRC CONNECTION SETUP + MS->>GERAN: RRC CONNECTION SETUP COMPLETE + +``` + +Sequence diagram for RRC Connection Establishment where the network accepts the request. The diagram shows three messages between the MS (Mobile Station) and GERAN (GSM EDGE Radio Access Network): 1. MS sends RRC CONNECTION REQUEST to GERAN. 2. GERAN responds with RRC CONNECTION SETUP to MS. 3. MS completes the setup with RRC CONNECTION SETUP COMPLETE to GERAN. + +Figure 7.5.1.1: RRC Connection Establishment, network accepts RRC connection + +![Sequence diagram for RRC Connection Establishment where the network rejects the request. The diagram shows two messages between the MS (Mobile Station) and GERAN (GSM EDGE Radio Access Network): 1. MS sends RRC CONNECTION REQUEST to GERAN. 2. GERAN responds with RRC CONNECTION REJECT to MS.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + Note left of MS: + MS->>GERAN: RRC CONNECTION REQUEST + GERAN-->>MS: RRC CONNECTION REJECT + +``` + +Sequence diagram for RRC Connection Establishment where the network rejects the request. The diagram shows two messages between the MS (Mobile Station) and GERAN (GSM EDGE Radio Access Network): 1. MS sends RRC CONNECTION REQUEST to GERAN. 2. GERAN responds with RRC CONNECTION REJECT to MS. + +Figure 7.5.1.2: RRC Connection Establishment, network rejects RRC connection + +#### 7.5.1.1 General + +The purpose of this procedure is to establish an RRC connection. + +#### 7.5.1.2 Initiation + +The MS shall initiate the procedure when upper layers in the MS requests the establishment of a signalling connection and the MS is in RRC-Idle mode (no RRC connection exists), as specified in sub-clause 7.17. + +Upon initiation of the procedure, the MS shall: + +- 1> set the variable PROTOCOL\_ERROR\_INDICATOR to FALSE; +- 1> if the USIM is present: + - 2> set the value of "THRESHOLD" in the variable "START\_THRESHOLD" by the 20 MSBs of the value stored in the USIM (see 3GPP TS 31.102) for the maximum value of START for each CN Domain; +- 1> if the SIM is present: + - 2> set the value of "THRESHOLD" in the variable "START\_THRESHOLD" to the default value in 3GPP TS 33.102 for each CN Domain. +- 1> set the IE "*Initial MS Identity*" in the variable INITIAL\_MS\_IDENTITY according to sub-clause 7.18; +- 1> set the contents of the RRC CONNECTION REQUEST message according to sub-clause 7.5.1.3; +- 1> submit the RRC CONNECTION REQUEST message for transmission on the uplink SRB2; +- 1> set counter V300 to 1; and +- 1> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + +- 2> start timer T300; +- 1> if the RLC sub-layer indicates a link failure to the RRC layer: + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 2> consider the RRC Connection Establishment procedure to be unsuccessful; + - 2> the procedure ends. + +#### 7.5.1.3 RRC CONNECTION REQUEST message contents to set + +The MS shall, in the transmitted RRC CONNECTION REQUEST message: + +- 1> set the IE "*Establishment Cause*" to the value of the variable ESTABLISHMENT\_CAUSE; +- 1> set the IE "*Initial MS Identity*" to the value of the variable INITIAL\_MS\_IDENTITY; +- 1> set the IE "*Protocol Error Indicator*" to the value of the variable PROTOCOL\_ERROR\_INDICATOR. + +#### 7.5.1.4 Reception of an RRC CONNECTION REQUEST message by the GERAN + +Upon receiving an RRC CONNECTION REQUEST message, the GERAN shall either: + +- 1> submit an RRC CONNECTION SETUP message to the lower layers for transmission on the downlink SRB2; or +- 1> submit an RRC CONNECTION REJECT message on the downlink SRB2. In the RRC CONNECTION REJECT message, the GERAN may direct the MS to another GERAN cell. After the RRC CONNECTION REJECT message has been sent, all context information for the MS may be deleted in GERAN. + +#### 7.5.1.5 Cell re-selection or T300 timeout + +If the MS has not yet received an RRC CONNECTION SETUP message with the value of the IE "*Initial MS Identity*" equal to the value of the variable INITIAL\_MS\_IDENTITY and if cell re-selection or expiry of timer T300 occurs the MS shall: + +- 1> check the value of V300; and + - 2> if V300 is equal to or smaller than N300: + - 3> set the IEs in the RRC CONNECTION REQUEST message according to sub-clause 7.5.1.3; + - 3> submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink SRB2; + - 3> increment counter V300; + - 3> if the RLC sub-layer indicates to the RRC layer a successful transmission of the RRC CONNECTION REQUEST message: + - 4> restart timer T300; + - 3> if the RLC sub-layer indicates a link failure to the RRC layer: + - 4> enter RRC-Idle mode; + - 4> perform the actions specified in clause 6 and in sub sub-clause 7.18; + - 4> consider the RRC Connection Establishment procedure to be unsuccessful; + - 4> the procedure ends. + - 2> if V300 is greater than N300: + - 3> enter RRC-Idle mode. + +- 3> consider the procedure to be unsuccessful; +- 3> other actions the MS shall perform when MS is in RRC-Idle mode are specified in sub-clause 6; +- 3> the procedure ends. + +#### 7.5.1.6 Abortion of RRC connection establishment + +If the MS has not yet entered GERAN RRC-Connected mode and the RRC Connection Establishment is to be aborted as specified in sub-clause 7.17.1.4, the MS shall: + +- 1> consider the procedure to be unsuccessful; +- 1> perform the actions when MS is in RRC-Idle mode as specified in clause 6 and sub-clause 7.18. + +The procedure ends. + +#### 7.5.1.7 Reception of an RRC CONNECTION SETUP message by the MS + +On receipt of an RRC CONNECTION SETUP message with the value of the IE "*Initial MS Identity*" equal to the value of the variable INITIAL\_MS\_IDENTITY, the MS shall: + +- 1> stop timer T300, and act upon all received information elements as specified in sub-clause 7.19, unless specified otherwise in the following; +- 2> if the MS will be in the RRC-Cell\_Shared state at the conclusion of this procedure: + - 3> set the GERAN DRX cycle length coefficient as specified in sub-clause 7.19; +- 1> enter in RRC-Connected mode according to sub-clause 7.19; +- 1> submit an RRC CONNECTION SETUP COMPLETE message to the lower layers on the uplink SRB2 after successful state transition, with the contents set as specified below: + - 2> set the IE "*RRC Transaction Identifier*" to + - 3> the value of "*RRc transaction identifier*" in the entry for the RRC CONNECTION SETUP message in the table "*Accepted transactions*" in the variable TRANSACTIONS; and + - 3> clear that entry. + - 2> if the USIM or SIM is present: + - 3> set the "*START*" for each CN domain in the IE "*START List*" in the RRC CONNECTION SETUP COMPLETE message with the corresponding START value that is stored in the USIM (see 3GPP TS 31.102) if present, or as stored in the MS if the SIM is present; and then + - 3> set the START value stored in the USIM (see 3GPP TS 31.102) if present, and as stored in the MS if the SIM is present, for any CN domain to the value "*THRESHOLD*" of the variable START\_THRESHOLD; + - 2> if neither the USIM nor SIM is present: + - 3> set the "*START*" for each CN domain in the IE "*START List*" in the RRC CONNECTION SETUP message to zero; + - 3> set the value of "*THRESHOLD*" in the variable "*START\_THRESHOLD*" to the default value as specified in 3GPP TS 33.102. + - 2> retrieve its GERAN *Iu mode* MS radio access capability information elements from variable the MS\_CAPABILITY\_REQUESTED; and then + - 2> include this in IE "*MS GERAN Iu mode Radio Access Capability*", in the RRC CONNECTION SETUP COMPLETE message; + - 2> retrieve its inter-RAT specific MS and UE radio access capability information elements from the variable MS\_CAPABILITY\_REQUESTED; and then + +2> include this in structure "*Inter-RAT MS Radio Access Capability*". + +The RRC CONNECTION SETUP COMPLETE message is submitted to lower layers for transmission: + +1> If the RLC sub-layer indicates to the RRC layer a successful transmission of the RRC CONNECTION SETUP COMPLETE message the MS shall: + +2> if the MS has entered RRC-Cell\_Shared state: + +3> start timer T305 using its initial value if periodical update has been configured by T305 in the IE "*MS Timers and Constants in Connected mode*" set to any other value than "infinity" the variable TIMERS\_AND\_CONSTANTS ; + +2> store the contents of the variable MS\_CAPABILITY\_REQUESTED into the variable MS\_CAPABILITY\_TRANSFERRED + +2> initialise variables upon entering RRC-Connected mode as specified in sub-clause 10.4; + +2> consider the procedure to be successful; + +2> and the procedure ends. + +1> Else, the RLC sub-layer indicates to the RRC layer a link failure condition. The MS shall: + +2> enter RRC-Idle mode; + +2> perform the actions specified in clause 6 and in sub sub-clause 7.18; + +2> consider the RRC Connection Establishment procedure to be unsuccessful; + +2> the procedure ends. + +#### 7.5.1.8 Cell re-selection + +1> If the MS performs cell re-selection; or + +1> if the MS will be in the RRC-Cell\_Shared state at the conclusion of this procedure; and + +1> if the contents of the variable G\_RNTI is empty; + +1> after having received an RRC CONNECTION SETUP message; and + +1> before the RRC CONNECTION SETUP COMPLETE message is delivered to lower layers for transmission: + +the MS shall: + +1> clear the entry for the RRC CONNECTION SETUP message in the table "Accepted transactions" in the variable TRANSACTIONS; + +1> check the value of V300, and: + +2> if V300 is equal to or smaller than N300: + +3> set the IEs in the RRC CONNECTION REQUEST message according to sub-clause 7.5.1.3; + +3> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink SRB2; + +3> increment counter V300; and + +3> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + +4> restart timer T300; + +3> if the RLC sub-layer indicates a link failure to the RRC layer: + +4> enter RRC-Idle mode; + +- 4> perform the actions specified in clause 6 when MS is in RRC-Idle mode; +- 4> consider the RRC Connection Establishment procedure to be unsuccessful; +- 4> the procedure ends. +- 2> if V300 is greater than N300: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 MS is in RRC-Idle mode; + - 3> consider the RRC Establishment procedure to be unsuccessful; + - 3> the procedure ends. + +#### 7.5.1.9 Invalid RRC CONNECTION SETUP message + +If the MS receives an RRC CONNECTION SETUP message and the RRC CONNECTION SETUP message contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows: + +- 1> clear the entry for the RRC CONNECTION SETUP message in the table "Rejected transactions" in the variable TRANSACTIONS and proceed as below; +- 1> if V300 is equal to or smaller than N300: + - 2> set the variable PROTOCOL\_ERROR\_INDICATOR to TRUE; + - 2> set the IEs in the RRC CONNECTION REQUEST message according to sub-clause 7.5.1.3; + - 2> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink SRB2; + - 2> increment counter V300; and + - 2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 3> restart timer T300; + - 2> if the RLC sub-layer indicates a link failure to the RRC layer: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 3> consider the RRC Connection Establishment procedure to be unsuccessful; + - 3> the procedure ends. +- 1> if V300 is greater than N300: + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 2> consider the RRC Establishment procedure to be unsuccessful; + - 2> the procedure ends. + +#### 7.5.1.10 Reception of an RRC CONNECTION REJECT message by the MS + +When the MS receives an RRC CONNECTION REJECT message on the downlink SRB2 with the value of the IE "Initial MS Identity" equal to the value of the variable INITIAL\_MS\_IDENTITY, the MS shall stop timer T300 and: + +- 1> clear the entry for the RRC CONNECTION REJECT message in the table "Accepted transactions" in the variable TRANSACTIONS; + +- 1> if the IE "*Wait Time*" is not equal to '0'; + - 2> if V300 is equal to or smaller than N300: + - 3> set the IEs in the RRC CONNECTION REQUEST message according to 7.5.1.3; + - 3> then submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink SRB2. + - 3> increment counter V300; and + - 3> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 4> restart timer T300; + - 3> if the RLC sub-layer indicates a link failure to the RRC layer: + - 4> enter RRC-Idle mode; + - 4> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 4> consider the RRC Connection Establishment procedure to be unsuccessful; + - 4> the procedure ends. + - 2> if V300 is greater than N300: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 when entering RRC-Idle mode; + - 3> consider the RRC Establishment procedure to be unsuccessful; + - 3> the procedure ends. +- 1> if the IE "*Wait Time*" is equal to '0'; + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 2> consider the RRC Establishment procedure to be unsuccessful; + - 2> the procedure ends. + +#### 7.5.1.11 Invalid RRC CONNECTION REJECT message + +If the MS receives an RRC CONNECTION REJECT message which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows. + +The MS shall: + +- 1> clear the entry for the RRC CONNECTION REJECT message in the table "Rejected transactions" in the variable TRANSACTIONS; +- 1> if V300 is equal to or smaller than N300: + - 2> set the variable PROTOCOL\_ERROR\_INDICATOR to TRUE; + - 2> set the IEs in the RRC CONNECTION REQUEST message according to sub-clause 7.5.1.3; + - 2> submit a new RRC CONNECTION REQUEST message to the lower layers for transmission on the uplink SRB2; + - 2> increment counter V300; and + +- 2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 3> restart timer T300; +- 2> if the RLC sub-layer indicates a link failure to the RRC layer: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 3> consider the RRC Connection Establishment procedure to be unsuccessful; + - 3> procedure ends. +- 1> if V300 is greater than N300: + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 2> consider the RRC Establishment procedure to be unsuccessful; + - 2> the procedure ends. + +## 7.5.2 RRC connection release + +![Sequence diagram of the RRC Connection Release procedure between MS and GERAN.](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + Note right of GERAN: RRC CONNECTION RELEASE + GERAN->>MS: RRC CONNECTION RELEASE + Note left of MS: RRC CONNECTION RELEASE COMPLETE + MS->>GERAN: RRC CONNECTION RELEASE COMPLETE + +``` + +The diagram illustrates the RRC Connection Release procedure. It shows two vertical lifelines: MS (Mobile Station) on the left and GERAN (GSM EDGE Radio Access Network) on the right. The sequence of messages is as follows: + + +- The GERAN sends an **RRC CONNECTION RELEASE** message to the MS. +- The MS receives the message and responds with an **RRC CONNECTION RELEASE COMPLETE** message back to the GERAN. + +Sequence diagram of the RRC Connection Release procedure between MS and GERAN. + +Figure 7.5.2.1: RRC Connection Release procedure + +### 7.5.2.1 General + +The purpose of this procedure is to release the RRC connection and all radio bearers between the MS and the GERAN. By doing so, all established signalling connections will be released. + +### 7.5.2.2 Initiation + +When the MS is in state RRC-Cell\_Dedicated state or RRC-Cell\_Shared state, the GERAN may at anytime initiate an RRC connection release by transmitting an RRC CONNECTION RELEASE message using SRB2. + +### 7.5.2.3 Reception of an RRC CONNECTION RELEASE message by the MS + +The MS shall receive and act on an RRC CONNECTION RELEASE message in states RRC-Cell\_Dedicated state and RRC-Cell\_Shared state. Furthermore this procedure can interrupt any ongoing procedures with the MS in the above listed states. + +When the MS receives the RRC CONNECTION RELEASE message, it shall: + +- 1> in state RRC-Cell\_Dedicated state: + - 2> set the IE "*RRCTransactionIdentifier*" in the RRC CONNECTION RELEASE COMPLETE message to the value of "*RRCTransactionIdentifier*" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> if the IE "*RPLMN Information*" is present: + +- 3> the MS may: + - 4> store the IE on the ME together with the PLMN id for which it applies; +- 3> the MS may then: + - 4> utilise this information, typically indicating where a number of BCCH frequency ranges of a RAT may be expected to be found, during subsequent RPLMN selections of the indicated PLMN. +- 2> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission the SRB2 to the GERAN; +- 1> in state RRC-Cell\_Shared state: + - 2> set the IE "*RRC Transaction Identifier*" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using the SRB2; +- 1> when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been confirmed by the lower layers: + - 2> release all its radio resources; and + - 2> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; and + - 2> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> pass the value of the IE "*Release Cause*" received in the RRC CONNECTION RELEASE message to upper layers; + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in sub-clause 7.18 and clause 6 when entering RRC-Idle mode from RRC-Connected mode; + - 2> and the procedure ends. + +### 7.5.2.4 Invalid RRC CONNECTION RELEASE message + +If the RRC CONNECTION RELEASE message contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, and if the "protocol error cause" in PROTOCOL\_ERROR\_INFORMATION is set to any cause value except "CSN.1 violation or encoding error", the MS shall perform procedure specific error handling as follows. + +The MS shall: + +- 1> ignore any IE(s) causing the error but treat the rest of the RRC CONNECTION RELEASE message as normal according to sub-clause 7.5.2.3, with an addition of the following actions; +- 1> set the IE "*RRC Transaction Identifier*" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Rejected transactions" in the variable TRANSACTIONS; and +- 1> include the IE "*Error Indication*" in the RRC CONNECTION RELEASE COMPLETE message with: + - 2> the IE "*Failure Cause*" set to the cause value "Protocol error"; and + +2> the IE "*Protocol Error Information*" set to the value of the variable +PROTOCOL\_ERROR\_INFORMATION. + +### 7.5.2.5 Cell re-selection or radio link failure + +If the MS performs cell re-selection or the radio link failure criteria in sub-clause 7.18 is met at any time during the RRC connection release procedure and the MS has not yet entered idle mode, the MS shall: + +- 1> if cell re-selection occurred (RRC-Cell\_Shared state): + - 2> perform a Cell Update procedure according to sub-clause 7.8 using the cause "cell reselection"; +- 1> if radio link failure occurred (RRC-Cell\_Dedicated state): + - 2> release all its radio resources; + - 2> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 and sub-clause 7.18 when entering RRC-Idle mode from RRC-Connected mode; + - 2> and the procedure ends. + +### 7.5.2.6 Reception of an RRC CONNECTION RELEASE COMPLETE message by GERAN + +When GERAN receives an RRC CONNECTION RELEASE COMPLETE message from the MS, it shall: + +- 1> release all MS dedicated resources and the procedure ends on the GERAN side. + +### 7.5.2.7 Unsuccessful transmission of the RRC CONNECTION RELEASE COMPLETE message, acknowledged mode transmission + +When RLC does not succeed in transmitting the RRC CONNECTION RELEASE COMPLETE message, the MS shall: + +- 1> release all its radio resources; +- 1> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; +- 1> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; +- 1> clear the variable ESTABLISHED\_RABS; +- 1> enter RRC-Idle mode; +- 1> perform the actions specified in clause 6 and sub-clause 7.18 when entering RRC-Idle mode from RRC-Connected mode; +- 1> and the procedure ends. + +### 7.5.2.8 Detection of loss of dedicated physical channel by GERAN in RRC-Cell\_Dedicated state + +If the release is performed from the state RRC-Cell\_Dedicated state, and GERAN detects loss of the dedicated basic physical channel according to sub-clause 7.18, GERAN may release all MS dedicated resources, even if no RRC CONNECTION RELEASE COMPLETE message has been received. + +### 7.5.2.9 Failure to receive RRC CONNECTION RELEASE COMPLETE message by GERAN + +If GERAN does not receive any RRC CONNECTION RELEASE COMPLETE message, it shall release all MS dedicated resources. + +## 7.6 Transmission of MS capability information + +### 7.6.1 General + +![Sequence diagram showing the transmission of MS capability information between MS and GERAN. The MS sends an MS CAPABILITY INFORMATION message to the GERAN, and the GERAN responds with an MS CAPABILITY INFORMATION CONFIRM message.](43979979715bb3304389a0cb18f34444_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + Note right of MS: MS CAPABILITY INFORMATION + MS->>GERAN: MS CAPABILITY INFORMATION + Note left of GERAN: MS CAPABILITY INFORMATION CONFIRM + GERAN-->>MS: MS CAPABILITY INFORMATION CONFIRM + +``` + +Sequence diagram showing the transmission of MS capability information between MS and GERAN. The MS sends an MS CAPABILITY INFORMATION message to the GERAN, and the GERAN responds with an MS CAPABILITY INFORMATION CONFIRM message. + +**Figure 7.6.1.1 : Transmission of MS capability information, normal flow** + +The MS Capability Update procedure is used by the MS to convey MS specific capability information to the GERAN. + +### 7.6.2 Initiation + +The MS shall initiate the MS Capability Update procedure in the following situations: + +- 1> the MS receives a MS CAPABILITY ENQUIRY message from the GERAN; +- 1> while in RRC-Connected mode the MS capabilities change compared to those stored in the variable MS\_CAPABILITY\_TRANSFERRED. + +If the MS CAPABILITY INFORMATION message is sent in response to a MS CAPABILITY ENQUIRY message, the MS shall: + +- 1> include the IE "*RRC Transaction Identifier*"; and +- 1> set it to the value of "RRC Transaction Identifier" in the entry for the MS CAPABILITY ENQUIRY message in the table "Accepted transactions" in the variable TRANSACTIONS; +- 1> retrieve the GERAN *Iu mode* radio access capability information elements from variable MS\_CAPABILITY\_REQUESTED; and +- 1> include this in IE "*MS GERAN Iu mode Radio Access Capability*", provided this IE is included in variable MS\_CAPABILITY\_REQUESTED. +- 1> retrieve its inter-RAT and inter-mode specific MS radio access capability information elements from variable MS\_CAPABILITY\_REQUESTED; and +- 1> include this in IE "*MS GERAN A/Gb mode Radio Access Capability*", IE "*UE UTRAN Radio Access Capability*", IE "*UE UTRAN Predefined Configuration Status Information*" and in IE "*UE CDMA2000 Radio Access Capability*", provided this IE is included in variable MS\_CAPABILITY\_REQUESTED. + +If the MS CAPABILITY INFORMATION message is sent because one or more of the MS capabilities change compared to those stored in the variable MS\_CAPABILITY\_TRANSFERRED while in RRC-Connected mode, the MS shall include the information elements associated with the capabilities that have changed in the MS CAPABILITY INFORMATION message. + +If the MS is in RRC-GRAN\_PCH state, it shall first perform a Cell Update procedure using the cause "Uplink Data Transmission", see sub-clause 7.8. + +The MS RRC shall submit the MS CAPABILITY INFORMATION message to the lower layers for transmission on the uplink using SRB2. The MS RRC shall: + +- 1> set counter V304 to 1; +- 1> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 2> start timer T304; +- 1> if the RLC sub-layer indicates a link failure to the RRC layer: + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 2> consider the MS Capability Update procedure to be unsuccessful; + - 2> the procedure ends. + +### 7.6.3 Reception of an MS CAPABILITY INFORMATION message by the GERAN + +Upon reception of a MS CAPABILITY INFORMATION message, the GERAN should transmit a MS CAPABILITY INFORMATION CONFIRM message on the downlink SRB2. After the MS CAPABILITY INFORMATION CONFIRM message has been submitted to the lower layers for transmission, the procedure is complete. + +### 7.6.4 Reception of the MS CAPABILITY INFORMATION CONFIRM message by the MS + +Upon reception of a MS CAPABILITY INFORMATION CONFIRM message, the MS shall: + +- 1> stop timer T304; +- 1> if there is an entry for the MS CAPABILITY ENQUIRY message present in the table "Accepted transactions" in the variable TRANSACTIONS: + - 2> clear that entry. +- 1> update its variable MS\_CAPABILITY\_TRANSFERRED with the MS capabilities it has last transmitted to the GERAN during the current RRC connection; +- 1> clear the variable MS\_CAPABILITY\_REQUESTED; +- 1> and the procedure ends. + +### 7.6.5 Invalid MS CAPABILITY INFORMATION CONFIRM message + +If the MS receives a MS CAPABILITY INFORMATION CONFIRM message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows: + +- 1> stop timer T304; +- 1> transmit an RRC STATUS message on the uplink using SRB2; +- 1> include the IE "*Identification of Received Message*"; and +- 1> set the IE "*Received Message Type*" to MS CAPABILITY INFORMATION CONFIRM; and +- 1> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the MS CAPABILITY INFORMATION CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; and +- 1> clear that entry; + +- 1> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION; +- 1> when the RRC STATUS message has been submitted to lower layers for transmission: + - 2> restart timer T304 and continue with any ongoing procedures or processes as if the invalid MS CAPABILITY INFORMATION CONFIRM message has not been received. + +## 7.6.6 T304 timeout + +Upon expiry of timer T304, the MS shall check the value of V304 and: + +- 1> if V304 is smaller than or equal to N304: + - 2> prior to retransmitting the MS CAPABILITY INFORMATION message: + - 3> if the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started": + - 4> include the same IEs as in the last unsuccessful attempt of this message, except for the IE "*Integrity Check Info*", which is modified as follows: + - a) 5> increment the "Uplink RRC Message sequence number" for signalling radio bearer RB2 in the variable INTEGRITY\_PROTECTION\_INFO by one; + - b) 5> set the IE "*RRC Message Sequence Number*" in the IE "*Integrity Check Info*" by the value of the "Uplink RRC Message sequence number" for signalling radio bearer RB2 in the variable INTEGRITY\_PROTECTION\_INFO in this message; + - c) 5> recalculate the IE "*Message Authentication Code*" in the IE "*Integrity Check Info*" in this message, in accordance with sub-clause 7.18; + - 3> else: + - 4> include the same IEs as in the last unsuccessful attempt of this message. + - 2> send the MS CAPABILITY INFORMATION message on SRB2; + - 2> restart timer T304; + - 2> increment counter V304. +- 1> if V304 is greater than N304: + - 2> initiate the Cell Update procedure as specified in sub-clause 7.8 using the cause "radio link failure". + +## 7.7 MS capability enquiry + +### 7.7.1 General + +![Sequence diagram showing the MS Capability Enquiry procedure. A GERAN node sends an MS CAPABILITY ENQUIRY message to an MS node.](0d0897dd7f03672d186db9d56ea0d6f5_img.jpg) + +``` + +sequenceDiagram + participant GERAN + participant MS + Note right of GERAN: MS CAPABILITY ENQUIRY + GERAN->>MS: MS CAPABILITY ENQUIRY + +``` + +The diagram illustrates a sequence of interactions between two entities: MS (Mobile Station) and GERAN (GSM EDGE Radio Access Network). The GERAN entity is shown on the right, and the MS entity is on the left. A horizontal arrow labeled "MS CAPABILITY ENQUIRY" points from the GERAN entity to the MS entity, indicating the direction of the message flow. + +Sequence diagram showing the MS Capability Enquiry procedure. A GERAN node sends an MS CAPABILITY ENQUIRY message to an MS node. + +Figure 7.7.1.1: MS Capability Enquiry procedure, normal flow + +The MS Capability Enquiry procedure can be used to request the MS to transmit its capability information related to any radio access network that is supported by the MS. For a multi-RAT MS this procedure allows in addition to request UTRAN predefined configuration status information. + +## 7.7.2 Initiation + +The MS Capability Enquiry procedure is initiated by the GERAN by transmitting a MS CAPABILITY ENQUIRY message using SRB2. + +## 7.7.3 Reception of an MS CAPABILITY ENQUIRY message by the MS + +Upon reception of an MS CAPABILITY ENQUIRY message, the MS shall act on the received information elements as specified in sub-clause 7.19 and 7.18 and initiate the transmission of MS Capability Information procedure, which is specified in sub-clause 7.6. + +## 7.7.4 Invalid MS CAPABILITY ENQUIRY message + +If the MS receives a MS CAPABILITY ENQUIRY message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows: + +- 1> transmit an RRC STATUS message on the uplink using SRB2; +- 1> include the IE "*Identification of Received Message*"; and +- 1> set the IE "*Received Message Type*" to MS CAPABILITY ENQUIRY; and +- 1> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the MS CAPABILITY ENQUIRY message in the table "Rejected transactions" in the variable TRANSACTIONS; and +- 1> clear that entry; +- 1> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION; +- 1> when the RRC STATUS message has been submitted to lower layers for transmission: + - 2> continue with the ongoing processes and procedures as if the invalid MS CAPABILITY ENQUIRY message has not been received. + +## 7.8 RRC Connection mobility procedures + +### 7.8.1 Cell and GRA Update procedures + +![Sequence diagram of the Cell Update procedure. The diagram shows two vertical lifelines: MS (Mobile Station) on the left and GERAN (Radio Access Network) on the right. A horizontal arrow labeled 'CELL UPDATE' points from the MS to the GERAN. A horizontal arrow labeled 'CELL UPDATE CONFIRM' points from the GERAN back to the MS.](d6015fcef74bce83d04acd2e17b4fc15_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + Note left of MS: MS sends CELL UPDATE + MS->>GERAN: CELL UPDATE + Note right of GERAN: GERAN responds with CELL UPDATE CONFIRM + GERAN->>MS: CELL UPDATE CONFIRM +``` + +Sequence diagram of the Cell Update procedure. The diagram shows two vertical lifelines: MS (Mobile Station) on the left and GERAN (Radio Access Network) on the right. A horizontal arrow labeled 'CELL UPDATE' points from the MS to the GERAN. A horizontal arrow labeled 'CELL UPDATE CONFIRM' points from the GERAN back to the MS. + +Figure 7.8.1.1: Cell Update procedure, basic flow + +![Sequence diagram for Figure 7.8.1.2: Cell Update procedure with update of GERAN mobility information. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends CELL UPDATE CONFIRM to MS. 3. GERAN sends GERAN MOBILITY INFORMATION CONFIRM to MS.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + MS->>GERAN: CELL UPDATE + GERAN-->>MS: CELL UPDATE CONFIRM + GERAN-->>MS: GERAN MOBILITY INFORMATION CONFIRM +``` + +Sequence diagram for Figure 7.8.1.2: Cell Update procedure with update of GERAN mobility information. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends CELL UPDATE CONFIRM to MS. 3. GERAN sends GERAN MOBILITY INFORMATION CONFIRM to MS. + +Figure 7.8.1.2: Cell Update procedure with update of GERAN mobility information + +![Sequence diagram for Figure 7.8.1.3: Cell Update procedure with radio bearer release. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends CELL UPDATE CONFIRM to MS. 3. GERAN sends RADIO BEARER RELEASE COMPLETE to MS.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + MS->>GERAN: CELL UPDATE + GERAN-->>MS: CELL UPDATE CONFIRM + GERAN-->>MS: RADIO BEARER RELEASE COMPLETE +``` + +Sequence diagram for Figure 7.8.1.3: Cell Update procedure with radio bearer release. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends CELL UPDATE CONFIRM to MS. 3. GERAN sends RADIO BEARER RELEASE COMPLETE to MS. + +Figure 7.8.1.3: Cell Update procedure with radio bearer release + +![Sequence diagram for Figure 7.8.1.4: Cell Update procedure with radio bearer reconfiguration. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends CELL UPDATE CONFIRM to MS. 3. GERAN sends RADIO BEARER RECONFIGURATION COMPLETE to MS.](a93de4c3f80bd4a972ab65510b09b68d_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + MS->>GERAN: CELL UPDATE + GERAN-->>MS: CELL UPDATE CONFIRM + GERAN-->>MS: RADIO BEARER RECONFIGURATION COMPLETE +``` + +Sequence diagram for Figure 7.8.1.4: Cell Update procedure with radio bearer reconfiguration. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends CELL UPDATE CONFIRM to MS. 3. GERAN sends RADIO BEARER RECONFIGURATION COMPLETE to MS. + +Figure 7.8.1.4: Cell Update procedure with radio bearer reconfiguration + +![Sequence diagram for Figure 7.8.1.5: Cell Update procedure, failure case. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends RRC CONNECTION RELEASE to MS.](9dc9f41d7d76c1add4b190d348cb1533_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + MS->>GERAN: CELL UPDATE + GERAN-->>MS: RRC CONNECTION RELEASE +``` + +Sequence diagram for Figure 7.8.1.5: Cell Update procedure, failure case. The diagram shows two lifelines: MS and GERAN. The sequence of messages is: 1. MS sends CELL UPDATE to GERAN. 2. GERAN sends RRC CONNECTION RELEASE to MS. + +Figure 7.8.1.5: Cell Update procedure, failure case + +![Sequence diagram for Figure 7.8.1.6: GRA Update procedure, basic flow. The diagram shows two lifelines: MS and GERAN. The MS sends a GRA UPDATE message to the GERAN. The GERAN responds with a GRA UPDATE CONFIRM message back to the MS.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + MS->>GERAN: GRA UPDATE + GERAN-->>MS: GRA UPDATE CONFIRM +``` + +Sequence diagram for Figure 7.8.1.6: GRA Update procedure, basic flow. The diagram shows two lifelines: MS and GERAN. The MS sends a GRA UPDATE message to the GERAN. The GERAN responds with a GRA UPDATE CONFIRM message back to the MS. + +**Figure 7.8.1.6: GRA Update procedure, basic flow** + +![Sequence diagram for Figure 7.8.1.7: GRA Update procedure with update of GERAN mobility information. The diagram shows two lifelines: MS and GERAN. The MS sends a GRA UPDATE message to the GERAN. The GERAN responds with a GRA UPDATE CONFIRM message back to the MS. Finally, the MS sends a GERAN MOBILITY INFORMATION CONFIRM message to the GERAN.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + MS->>GERAN: GRA UPDATE + GERAN-->>MS: GRA UPDATE CONFIRM + MS->>GERAN: GERAN MOBILITY INFORMATION CONFIRM +``` + +Sequence diagram for Figure 7.8.1.7: GRA Update procedure with update of GERAN mobility information. The diagram shows two lifelines: MS and GERAN. The MS sends a GRA UPDATE message to the GERAN. The GERAN responds with a GRA UPDATE CONFIRM message back to the MS. Finally, the MS sends a GERAN MOBILITY INFORMATION CONFIRM message to the GERAN. + +**Figure 7.8.1.7: GRA Update procedure with update of GERAN mobility information** + +![Sequence diagram for Figure 7.8.1.8: GRA Update procedure, failure case. The diagram shows two lifelines: MS and GERAN. The MS sends a GRA UPDATE message to the GERAN. The GERAN responds with an RRC CONNECTION RELEASE message back to the MS.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + MS->>GERAN: GRA UPDATE + GERAN-->>MS: RRC CONNECTION RELEASE +``` + +Sequence diagram for Figure 7.8.1.8: GRA Update procedure, failure case. The diagram shows two lifelines: MS and GERAN. The MS sends a GRA UPDATE message to the GERAN. The GERAN responds with an RRC CONNECTION RELEASE message back to the MS. + +**Figure 7.8.1.8: GRA Update procedure, failure case** + +### 7.8.1.1 General + +The GRA Update and Cell Update procedures serve several main purposes: + +- to notify GERAN of an RLC unrecoverable error (see 3GPP TS 44.160) on an AM RLC entity; +- to be used as a supervision mechanism in the RRC-Cell\_Shared state or RRC-GRA\_PCH state by means of periodical update; + +In addition, the GRA Update procedure also serves the following purpose: + +- to retrieve a new GRA identity after cell re-selection to a cell not belonging to the current GRA assigned to the MS in RRC-GRA\_PCH state; + +In addition, the Cell Update procedure also serves the following purposes: + +- to update GERAN with the current cell the MS is camping on after cell reselection; +- to act on a radio link failure or notification of invalid RLC/MAC control message in the RRC-Cell\_Dedicated state; +- to act on the transmission failure of the MS CAPABILITY INFORMATION message; + +- when triggered in the RRC-GRA\_PCH state, to notify GERAN of a transition to the RRC-Cell\_Shared state due to the reception of GERAN originated paging or due to a request to transmit uplink data. + +The GRA Update and Cell Update procedures may: + +- include an update of mobility related information in the MS; +- cause a state transition from the RRC-Cell\_Shared state to the RRC-Cell\_Dedicated state, or from RRC-GRA\_PCH state to RRC-Idle mode. + +The Cell Update procedure may also include: + +- a re-establish of layer 2, AM RLC entities; +- a radio bearer release, or radio bearer reconfiguration; +- a DBPSCH assignment. + +### 7.8.1.2 Initiation + +A MS shall initiate the Cell Update procedure in the following cases: + +1> Uplink data transmission: + +- 2> if the MS is in RRC-GRA\_PCH state; and +- 2> if the MS has uplink signalling or data to transmit except a GRA UPDATE message; + - 3> perform cell update using the cause "uplink data transmission". + +1> Paging response: + +- 2> if the criteria for performing cell update with the cause specified above in the current sub-clause is not met; and +- 2> if the MS in RRC-GRA\_PCH state or RRC-Cell\_Shared state, receives paging information from the lower layers fulfilling the conditions for initiating a Cell Update procedure specified in 7.4: + - 3> perform cell update using the cause "paging response". + +1> Radio link failure: + +- 2> if none of the criteria for performing cell update with the causes specified above in the current sub-clause is met; and + - 3> if the MS is in RRC-Cell\_Dedicated state; and the criteria for radio link failure is met as specified in sub-clause 7.18; or + - 3> if the criteria for radio link failure is met as specified in sub-clause 7.18 the transmission of the MS CAPABILITY INFORMATION message fails as specified in sub-clause 7.6.6: + - 4> perform cell update using the cause "radio link failure". + +1> Invalid RLC/MAC control message: + +- 2> if none of the criteria for performing cell update with the causes specified above in the current sub-clause is met; and +- 2> if the MS is in RRC-Cell\_Dedicated state; and +- 2> if notification is received of the reception of an invalid RLC/MAC control message on DBPSCH: + - 3> act as specified in sub-clause 7.18.10: + - 4> perform cell update using the cause "invalid RLC/MAC control message". + +1> RLC unrecoverable error: + +- 2> if none of the criteria for performing cell update with the causes specified above in the current sub-clause is met; and +- 2> if the MS detects an RLC unrecoverable error (see 3GPP TS 44.160) in an AM RLC entity: + - 3> perform cell update using the cause "RLC unrecoverable error". + +1> Cell reselection: + +- 2> if none of the criteria for performing cell update with the causes specified above in the current sub-clause is met; and +- 2> if the MS is in RRC-Cell\_Shared state; and +- 2> if the MS performs cell re-selection: + - 3> perform cell update using the cause "cell reselection". + +1> Periodical cell update: + +- 2> if none of the criteria for performing cell update with the causes specified above in the current sub-clause is met; and +- 2> if the MS is in RRC-Cell\_Shared state; and +- 2> if the timer T305 expires; + - 3> perform cell update using the cause "periodical cell update". + +A MS in RRC-GRA\_PCH state shall initiate the GRA Update procedure in the following cases: + +1> GRA reselection: + +- 2> if the MS detects that the current GRA assigned to the MS, stored in the variable GRA\_IDENTITY, is not present in the list of GRA identities in packet system information 16; or +- 2> if the list of GRA identities in packet system information 16 is empty; or +- 2> if the packet system information 16 can not be found: + - 3> perform GRA update using the cause "change of GRA". + +1> Periodic GRA update: + +- 2> if the criteria for performing GRA update with the causes as specified above in the current sub-clause are not met; and +- 2> if the timer T305 expires while the MS is in RRC-GRA\_PCH; + - 3> perform GRA update using the cause "periodic GRA update". + +When initiating the GRA Update or Cell Update procedure, the MS shall: + +1> stop timer T305; + +1> if the MS is in RRC-Cell\_Dedicated state: + +- 2> in the variable RB\_TIMER\_INDICATOR, set the IE "*T314 Expired*" and the IE "*T315 Expired*" to FALSE; +- 2> if the stored values of the timer T314 and timer T315 are both equal to zero, or if the stored value of the timer T314 is equal to zero and there are no radio bearers associated with any radio access bearers for which in the variable ESTABLISHED\_RABS the value of the IE "*Re-establishment timer*" is set to "useT315": + - 3> release all its radio resources; + - 3> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + +``` +3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; +3> clear the variable ESTABLISHED_RABS; +3> enter RRC-Idle mode; +3> perform other actions when entering RRC-Idle mode from RRC-Connected mode as specified in +clause 6 and sub-clause 7.18; +3> and the procedure ends. +2> if the stored value of the timer T314 is equal to zero: +3> release all radio bearers, associated with any radio access bearers for which in the variable +ESTABLISHED_RABS the value of the IE "Re-establishment Timer" is set to "useT314"; +3> in the variable RB_TIMER_INDICATOR set the IE "T314 expired" to TRUE; +2> if the stored value of the timer T315 is equal to zero: +3> release all radio bearers associated with any radio access bearers for which in the variable +ESTABLISHED_RABS the value of the IE "Re-establishment Timer" is set to "useT315"; +3> in the variable RB_TIMER_INDICATOR set the IE "T315 expired" to TRUE; +2> if the stored value of the timer T314 is greater than zero: +3> if there are radio bearers associated with any radio access bearers for which in the variable +ESTABLISHED_RABS the value of the IE "Re-establishment Timer" is set to "useT314": +4> start timer T314. +2> if the stored value of the timer T315 is greater than zero: +3> if there are radio bearers associated with any radio access bearers for which in the variable +ESTABLISHED_RABS the value of the IE "Re-establishment timer" is set to "useT315": +4> start timer T315. +2> for the released radio bearer(s): +3> delete the information about the radio bearer from the variable ESTABLISHED_RABS; +3> when all radio bearers belonging to the same radio access bearer have been released: +4> indicate local end release of the radio access bearer to upper layers using the CN domain identity +together with the RAB identity stored in the variable ESTABLISHED_RABS; +4> delete all information about the radio access bearer from the variable ESTABLISHED_RABS; +2> set the variable ORDERED_RECONFIGURATION to FALSE; +1> set the variables PROTOCOL_ERROR_INDICATOR, FAILURE_INDICATOR, +UNSUPPORTED_CONFIGURATION and INVALID_CONFIGURATION to FALSE; +1> set the variable CELL_UPDATE_STARTED to TRUE; +1> in case of a Cell Update procedure: +2> set the contents of the CELL UPDATE message according to sub-clause 7.8.1.3; +2> submit the CELL UPDATE message for transmission on the SRB2; +1> in case of a GRA Update procedure: +2> set the contents of the GRA UPDATE message according to sub-clause 7.8.1.3; +2> submit the GRA UPDATE message for transmission on the SRB2; +``` + +- 1> set counter V302 to 1; +- 1> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 2> start timer T302; +- 1> if the RLC sub-layer indicates a link failure to the RRC layer: + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 2> consider the GRA Update procedure or Cell Update procedure to be unsuccessful; + - 2> the procedure ends. + +### 7.8.1.3 CELL UPDATE / GRA UPDATE message contents to set + +In case of Cell Update procedure the MS shall transmit a CELL UPDATE message. + +In case of GRA Update procedure the MS shall transmit a GRA UPDATE message. + +The MS shall set the IEs in the CELL UPDATE message as follows: + +- 1> set the IE "*Cell Update Cause*" corresponding to the cause specified in sub-clause 7.8.1.2 that is valid when the CELL UPDATE message is submitted to lower layers for transmission; + +NOTE: During the time period starting from when a cell update procedure is initiated by the MS until when the procedure ends, additional CELL UPDATE messages may be transmitted by the MS with different causes. + +- 1> set the IE "*G-RNTT*" to the value of the variable G-RNTT; +- 1> if the value of the variable PROTOCOL\_ERROR\_INDICATOR is TRUE: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 3> set it to the value of "RRC Transaction Identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 2> include and set the IE "*Failure Cause*" to the cause value "protocol error"; + - 2> set the IE "*Protocol Error Information*" set to the value of the variable PROTOCOL\_ERROR\_INFORMATION; +- 1> if the value of the variable FAILURE\_INDICATOR is TRUE: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 3> set it to the value of "RRC Transaction Identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; + - 2> include and set the IE "*Failure Cause*" to the value of the variable FAILURE\_CAUSE; +- 1> include the START values for each CN domain, calculated according to sub-clause 7.18; +- 1> if an unrecoverable error (see 3GPP TS 44.160) in any of the AM RLC entities for the signalling radio bearers SRB2, SRB3 or SRB4 is detected: + - 2> set the IE "*AM\_RLC error indication for c-plane*" to TRUE; +- 1> otherwise: + - 2> set the IE "*AM\_RLC error indication for c-plane*" to FALSE; +- 1> if an unrecoverable error (see 3GPP TS 44.160) in any of the AM RLC entities for the RB5 or upward is detected: + +- 2> set the IE "*AM\_RLC error indication for u-plane*" to TRUE; +- 1> otherwise: + - 2> set the IE "*AM\_RLC error indication for u-plane*" to FALSE; + - 1> set the IE "*RB Timer Indicator*" to the value of the variable RB\_TIMER\_INDICATOR; + +The MS shall set the IEs in the GRA UPDATE message as follows: + +- 1> set the IE "*G-RNTT*" to the value of the variable G-RNTT; +- 1> set the IE "*GRA Update Cause*" corresponding to which cause as specified in sub-clause 7.8.1.2 that is valid when the GRA UPDATE message is submitted to lower layers for transmission; +- 2> if the value of the variable PROTOCOL\_ERROR\_INDICATOR is TRUE: + - 3> include the IE "*RRC Transaction Identifier*"; and + - 4> set it to the value of "RRC Transaction Identifier" in the entry for the GRA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 3> set the IE "*Protocol Error Indicator*" to TRUE; + - 3> include the IE "*Protocol Error Information*" set to the value of the variable PROTOCOL\_ERROR\_INFORMATION. +- 2> if the value of the variable PROTOCOL\_ERROR\_INDICATOR is FALSE: + - 3> if the value of the variable INVALID\_CONFIGURATION is TRUE: + - 4> include the IE "*RRC Transaction Identifier*"; and + - d) 5> set it to the value of "RRC transaction identifier" in the entry for the GRA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; + - 4> set the IE "*Protocol Error Indicator*" to TRUE; + - 4> include the IE "*Protocol Error Information*" set to "Information element value not comprehended"; + - 3> if the value of the variable INVALID\_CONFIGURATION is FALSE: + - 4> set the IE "*Protocol Error Indicator*" to FALSE. + +#### 7.8.1.4 Reception of an CELL UPDATE/GRA UPDATE message by the GERAN + +When the GERAN receives a CELL UPDATE/GRA UPDATE message, the GERAN shall: + +- 1> in case the procedure was triggered by reception of a CELL UPDATE: + - 2> if SBSS relocation was performed: + - 3> transmit a CELL UPDATE CONFIRM message on the downlink SRB2. + - 2> if SBSS relocation was not performed: + - 3> update the START value for each CN domain as maintained in GERAN sub-clause 7.18 with "START" in the IE "*START List*" for the CN domain as indicated by "*CN Domain Identity*" IE in the IE "*START List*"; + - 3> transmit a CELL UPDATE CONFIRM message on the SRB2; + - 3> optionally set the IE "*RLC re-establish indicator (RB2, RB3 and RB4)*" and/or the IE "*RLC re-establish indicator (RB5 and upwards)*" to TRUE to request a RLC re-establishment in the MS, in which case the corresponding RLC entities shall also be re-established in GERAN; or +- 1> in case the procedure was triggered by reception of a GRA UPDATE: + +- 2> if SBSS relocation was performed: + - 3> transmit a GRA UPDATE CONFIRM message on the downlink SRB2; +- 2> if SBSS relocation was not performed: + - 3> transmit a GRA UPDATE CONFIRM message to the lower layers for transmission on SRB2 in which case the GERAN should include the IE "*GRA Identity*" in the GRA UPDATE CONFIRM message in a cell where multiple GRA identifiers are broadcast; or +- 1> initiate an RRC Connection Release procedure (see sub-clause 7.5.2) by transmitting an RRC CONNECTION RELEASE message on the SRB2. In particular GERAN shall: + - 2> if the CELL UPDATE message was sent because of an unrecoverable error in SRB2, SRB3 or SRB4: + - 3> initiate an RRC Connection Release procedure (sub-clause 7.5.2) by transmitting an RRC CONNECTION RELEASE message on the SRB2. + +### 7.8.1.5 Reception of the CELL UPDATE CONFIRM/GRA UPDATE CONFIRM message by the MS + +When the MS receives a CELL UPDATE CONFIRM/GRA UPDATE CONFIRM message the MS shall: + +- 1> stop timer T302; +- 1> in case of a Cell Update procedure and the CELL UPDATE CONFIRM message: + - 2> include one of the RB information elements (*RB Information to Release list*, *RB Information to Reconfigure list*, *RB Information to Be Affected list*); and/or + - 2> include one of the following Transport Channel information elements (IE "*Added or Reconfigured UL TrCH Information*", IE "*Added or Reconfigured DL TrCH Information*", IE "*Deleted DL TrCH Information*", IE "*Deleted DL TrCH Information*"); and/or + - 2> include the IE "*DBPSCH Description*" and structure "Network Response Times"; and + - 2> if the variable ORDERED\_RECONFIGURATION is set to FALSE: + - 3> set the variable ORDERED\_RECONFIGURATION to TRUE; +- 1> act upon all received information elements as specified in sub-clause 7.19 unless specified otherwise in the following; + - 2> if the field "*RLC Re-establish indicator SRB2-4*" in the CELL UPDATE CONFIRM message is set to one: + - 3> if the struct "Downlink counter synchronisation info" is not included in the CELL UPDATE CONFIRM message: + - 4> re-establish the RLC entities for signalling radio bearer SRB2, signalling radio bearer SRB3 and signalling radio bearer SRB4 (if established); + - 3> if the value of the IE "*Status*" in the variable CIPHERING\_STATUS of the CN domain stored in the variable LATEST\_CONFIGURED\_CN\_DOMAIN is set to "Started": + - 4> set the HFN component of the respective COUNT-C values for AM RLC entities SRB2, SRB3 and SRB4 (if established) equal to the START value included in the latest transmitted CELL UPDATE message for the CN domain stored in the variable LATEST\_CONFIGURED\_CN\_DOMAIN. + - 2> if the field "*RLC re-establish indicator RB5+*" in the CELL UPDATE CONFIRM message is set to one: + - 3> for radio bearers with RB identity larger than 4: + - 4> if the struct "Downlink counter synchronisation info" is not included in the CELL UPDATE CONFIRM message: + +- e) 5> re-establish the AM RLC entities; + - 4> if the value of the IE "*Status*" in the variable CIPHERING\_STATUS of the CN domain as indicated in the IE "*CN Domain Identity*" in the IE "*RAB Info*" in the variable ESTABLISHED\_RABS is set to "Started": +- f) 5> set the HFN component of the respective COUNT-C values for AM RLC entities equal to the START value included in the latest transmitted CELL UPDATE message for the CN domain as indicated in the IE "*CN domain identity*" in the IE "*RAB info*" in the variable ESTABLISHED\_RABS. + +1> if the CELL UPDATE CONFIRM / GRA UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*" or contained the IE "*Integrity Protection Mode Info*": + +2> set the IE "*Status*" in the variable SECURITY\_MODIFICATION for all the CN domains in the variable SECURITY\_MODIFICATION to "Affected"; + +1> enter a state according to sub-clause 7.19 applied on the CELL UPDATE CONFIRM / GRA UPDATE CONFIRM message. + +If the MS after state transition remains in RRC-Cell\_Shared state, it shall + +1> start the timer T305 using its initial value if timer T305 is not running and periodical cell update has been configured by T305 in the IE "*MS Timers and Constants in Connected mode*" set to any other value than "infinity"; + +1> if the CELL UPDATE CONFIRM / GRA UPDATE CONFIRM message contained the IE "*GERAN DRX Cycle Length Coefficient*": + +2> use the value in the IE "*GERAN DRX Cycle Length Coefficient*" for calculating Paging occasion as specified in sub-clause 7.19; + +If the MS after state transition enters RRC-GRA\_PCH state, it shall + +1> start the timer T305 using its initial value if timer T305 is not running and periodical update has been configured by T305 in the IE "*MS Timers and Constants in Connected mode*" set to any other value than "infinity"; + +The MS after state transition shall: + +1> if the CELL UPDATE CONFIRM / GRA UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + +2> include and set the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" in any response message transmitted below to the value of the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO. + +1> in case cell reselection interrupted an ongoing cell update procedure and a CELL UPDATE CONFIRM/GRA UPDATE CONFIRM was received with the IE "*Downlink counter synchronisation info*" present and the response to which was not submitted to the lower layers due to the cell re-selection: + +2> include the IE "*START list*" in the response message transmitted according to sub-clause 7.8.1.6; + +2> if the CELL UPDATE CONFIRM/GRA UPDATE CONFIRM, the response to which was not delivered to the lower layers, due to the cell re-selection, included the IE "*RB with PDCP information list*": + +3> include the IE "*RB with PDCP information list*" in the response message transmitted according to sub-clause 7.8.1.6; + +1> in case of a Cell Update procedure: + +2> set the IE "*RRC Transaction Identifier*" in any response message transmitted below to the value of "RRC transaction identifier" in the entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and + +2> clear that entry. + +1> in case of a GRA Update procedure: + +- 2> set the IE "*RRC Transaction Identifier*" in any response message transmitted below to the value of "RRC transaction identifier" in the entry for the GRA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; and +- 2> clear that entry; +- 1> if the variable PDCP\_SN\_INFO is non-empty: + - 2> include the IE "*RB with PDCP Information List*" in any response message transmitted below and set it to the value of the variable PDCP\_SN\_INFO; +- 1> if the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message included the structure "*Downlink Counter Synchronisation Info*": + - 2> if the variable PDCP\_SN\_INFO is empty: + - 3> configure the corresponding RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except SRB2 to "stop"; + - 2> else: + - 3> configure the RLC entity for signalling radio bearers SRB1, SRB3 and SRB4 to "stop"; + - 3> configure the RLC entity for UM and AM radio bearers for which the IE "*PDCP SN Info*" is not included to "stop"; + - 2> re-establish SRB2; + - 2> for the downlink and the uplink, apply the ciphering configuration as follows: + - 3> if the received re-configuration message included the IE "*Ciphering Mode Info*": + - 4> use the ciphering configuration in the received message when transmitting the response message; + - 3> if the ciphering configuration for SRB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the activation times not having been reached: + - 4> if the previous SECURITY MODE COMMAND was received due to new keys being received: + - g) 5> consider the new ciphering configuration to include the received new keys; + - h) 5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 as indicated in subclause 7.16.1.2.3.1. + - 4> if the ciphering configuration for SRB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the previous SECURITY MODE COMMAND caused a change in LATEST\_CONFIGURED\_CN\_DOMAIN: + - i) 5> consider the new ciphering configuration to include the keys associated with the LATEST\_CONFIGURED\_CN\_DOMAIN; + - j) 5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 to the most recently transmitted IE "*START List*" or IE "*START*" for the LATEST\_CONFIGURED\_CN\_DOMAIN at the reception of the previous SECURITY MODE COMMAND message. + - 4> apply the new ciphering configuration immediately following RLC re-establishment. + - 3> else: + - 4> continue using the current ciphering configuration; + - 2> set the new uplink and downlink HFN of SRB2 to MAX(uplink HFN of SRB2, downlink HFN of SRB2); + - 2> increment by one the downlink and uplink HFN values for SRB2; + +- 2> calculate the START value according to sub-clause 7.18; + - 2> include the calculated START values for each CN domain in the IE "*START List*" in the structure "*Uplink Counter Synchronisation Info*" in any response message transmitted below; + - 2> if the cell reselection from UTRAN is performed : + - 3> set the 20 most significant bits of the uplink and downlink HFN component of COUNT-C of SRB2 to MAX(uplink HFNU, downlink HFNU) where HFNU is the HFN component of COUNT-C of SRB2 in UTRAN; + - 3> set the remaining bits of the uplink and downlink HFN component of COUNT-C of SRB2 equal to zero; + - 3> calculate the START value according to sub-clause 7.18; + - 3> include the calculated START values for each CN domain in the IE "*START list*" in the GERAN MOBILITY INFORMATION CONFIRM message; + - 3> set the variable LATEST\_CONFIGURED\_CN\_DOMAIN equal to the corresponding UTRAN variable ; + - 3> set the variable MS\_CAPABILITY\_TRANSFERRED equal to the corresponding UTRAN variable ; + - 3> set the variable ESTABLISHED\_RABS equal to the corresponding UTRAN variable ; + - 3> set the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS equal to the corresponding UTRAN variable ; + - 3> set the variable CIPHERING\_STATUS equal to the corresponding UTRAN variable; + - 3> set the variable START\_THRESHOLD equal to the corresponding UTRAN variable ; + - 3> set the variable START\_VALUE\_TO\_TRANSMIT equal to the corresponding UTRAN variable; + - 3> set IE "*Status*" for the ciphering status in the the variable SECURITY\_MODIFICATION equal to the corresponding UTRAN variable; + - 3> set IE "*Status*" for the integrity protection in the variable INTEGRITY\_PROTECTION\_INFO equal to the corresponding UTRAN variable; +- 1> transmit a response message as specified in sub-clause 7.8.1.6; + - 1> if the IE "*Integrity Protection Mode Info*" was present in the CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message: + - 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer SRB2 from and including the transmitted response message; + - 1> if the variable ORDERED\_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure: + - 2> set the variable ORDERED\_RECONFIGURATION to FALSE; + - 1> clear the variable PDCP\_SN\_INFO; + - 1> when the response message transmitted per sub-clause 7.8.1.6 to the GERAN has been confirmed by RLC: + - 2> if the CELL UPDATE CONFIRM / GRA UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + - 3> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; + - 3> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - 3> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + +- 2> if the CELL UPDATE CONFIRM / GRA UPDATE CONFIRM message contained the IE "*Integrity Protection Mode Info*": + - 3> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; + - 3> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and +- 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; +- 1> in case of a Cell Update procedure: + - 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; +- 1> in case of a GRA update procedure: + - 2> clear the entry for the GRA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; +- 1> set the variable CELL\_UPDATE\_STARTED to FALSE; +- 1> clear the variable SECURITY\_MODIFICATION. + +The procedure ends. + +### 7.8.1.6 Transmission of a response message to GERAN + +If the CELL UPDATE CONFIRM message + +- includes the IE "*RB Information to Release List*": + +the MS shall: + +- 1> transmit a RADIO BEARER RELEASE COMPLETE as response message using SRB2. + +If the CELL UPDATE CONFIRM message + +- does not include the IE "*RB Information to Release List*"; and +- includes the IE "*RB Information to Reconfigure List*"; or +- includes the IE "*RB Information to Be Affected List*"; and +- does not include Transport channel information elements (IE "*Added or Reconfigured UL TrCH Information*", IE "*Added or Reconfigured DL TrCH Information*", IE "*Deleted DL TrCH Information*", IE "*Deleted UL TrCH Information*"); and +- does not include the IE "*DBPSCH Description*": + +the MS shall: + +- 1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message using SRB2. + +If the CELL UPDATE CONFIRM message: + +- does not include the IE "*RB Information to Release list*"; and +- does not include the IE "*RB Information to Be Affected list*"; and +- includes the IE "*RB Information to Reconfigure list*"; and +- does not include Transport channel information elements (IE "*Added or Reconfigured UL TrCH Information*", IE "*Added or Reconfigured DL TrCH Information*", IE "*Deleted DL TrCH Information*", IE "*Deleted UL TrCH Information*"); and +- includes the IE "*DBPSCH description*": + +the MS shall: + +1> transmit a RADIO BEARER SETUP COMPLETE as response message on SRB2. + +If the CELL UPDATE CONFIRM message + +- does not include RB Information Elements (*RB Information to Release list, RB Information to Reconfigure list, RB Information to Be Affected list*); and +- does not include Transport channel information elements (IE "*Added or Reconfigured UL TrCH Information*", IE "*Added or Reconfigured DL TrCH Information*", IE "*Deleted DL TrCH Information*", IE "*Deleted UL TrCH Information*"); and- includes the IE "*CN Information Info*"; or +- includes the IE "*Ciphering Mode Info*"; or +- includes the IE "*Integrity Protection Mode Info*"; or +- includes the IE "*New G-RNTT*", or +- includes the struct "Downlink Counter Synchronisation Info" and the IE "*New G-RNTT*": + +the MS shall: + +1> transmit a GERAN MOBILITY INFORMATION CONFIRM as response message on the SRB2. + +If the CELL UPDATE CONFIRM message: + +- does not include RB Information Elements (*RB Information to Release list, RB Information to Reconfigure list, RB Information to Be Affected list*); and +- includes at least one of the following Transport channel information (IE "*Added or Reconfigured UL TrCH Information*", IE "*Added or Reconfigured DL TrCH Information*", IE "*Deleted DL TrCH Information*", IE "*Deleted UL TrCH Information*"): + +the MS shall: + +1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message using SRB2. + +If the CELL UPDATE CONFIRM message: + +- does not include RB Information Elements (*RB Information to Release list, RB Information to Reconfigure list, RB Information to Be Affected list*); and +- does not include "*CN Information Info*"; and +- does not include the IE "*Ciphering Mode Info*"; and +- does not include Transport channel information elements (IE "*Added or Reconfigured UL TrCH Information*", IE "*Added or Reconfigured DL TrCH Information*", IE "*Deleted DL TrCH Information*", IE "*Deleted UL TrCH Information*"); and +- does not include the IE "*Integrity Protection Mode Info*"; and +- does not include the IE "*New G-RNTT*": + +the MS shall: + +1> transmit no response message. + +If the GRA UPDATE CONFIRM message: + +- includes the IEs "*CN Information Info*"; or +- includes the IE "*Ciphering Mode Info*"; or +- includes the IE "*Integrity Protection Mode Info*"; or +- includes the IE "*New G-RNTT*", or +- includes the struct "Downlink Counter Synchronisation Info" and the IE "*New G-RNTT*" + +the MS shall: + +1> transmit a GERAN MOBILITY INFORMATION CONFIRM as response message on SRB2. + +If the GRA UPDATE CONFIRM message: + +- does not include "*CN Information Info*" ; and +- does not include the IE "*Ciphering Mode Info*" ; and +- does not include the IE "*Integrity Protection Mode Info*" ; and +- does not include the IE "*New G-RNTT*" ; and + +the MS shall: + +1> transmit no response message. + +If the new state is RRC-Cell\_Dedicated or RRC-Cell\_Shared state, the response message shall be transmitted using the new configuration after the state transition, and the MS shall: + +1> if the structure "*Downlink Counter Synchronisation Info*" was included in the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message: + +2> when RLC has confirmed the successful transmission of the response message: + +3> if the variable PDCP\_SN\_INFO is empty: + +4> configure the RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except SRB2 to "continue"; + +3> else: + +4> configure the RLC entity for signalling radio bearers SRB1, SRB3 and SRB4 to "continue"; + +4> configure the RLC entity for UM and AM radio bearers for which the IE "*PDCP SN Info*" is not included to "continue"; + +3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; + +3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + +3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero; + +3> set the remaining bits of the HFN component of the COUNT-C values of all AM RLC entities to zero, for those bearers to which RLC entitie where re-established; + +3> if the IE "*PDCP Context Relocation Info*" is not present: + +4> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED\_RABS as specified in 3GPP TS 25.323;. + +3> if the IE "*PDCP Context Relocation Info*" is present: + +4> perform the actions as specified in 7.19. + +1> if the variable PDCP\_SN\_INFO is empty: + +2> if the CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + +3> when RLC has confirmed the successful transmission of the response message: + +4> continue with the remainder of the procedure; + +2> if the CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message did not contain the IE "*Ciphering Mode Info*": + +3> when RLC has been requested to transmit the response message, + +4> continue with the remainder of the procedure; + +1> if the variable PDCP\_SN\_INFO non-empty: + +2> when RLC has confirmed the successful transmission of the response message: + +3> for each radio bearer in the variable PDCP\_SN\_INFO: + +4> if the IE "*RB Started*" in the variable ESTABLISHED\_RABS is set to "started": + +k) 5> configure the RLC entity for that radio bearer to "continue"; + +3> continue with the remainder of the procedure. + +If the new RRC state is RRC-GRA\_PCH state, the response message shall be transmitted in RRC-Cell\_Shared state, and the MS shall: + +1> when RLC has confirmed the successful transmission of the response message: + +2> if the IE "*Downlink Counter Synchronisation Info*" was included in the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message: + +3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; + +3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + +3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero; + +3> set the remaining bits of the HFN component of the COUNT-C values of all AM RLC entities to zero, for those bearers to which RLC entitie where re-established; + +3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED\_RABS as specified in 3GPP TS 25.323. + +2> for each radio bearer in the variable PDCP\_SN\_INFO: + +3> if the IE "*RB Started*" in the variable ESTABLISHED\_RABS is set to "started": + +4> configure the RLC entity for that radio bearer to "continue"; + +2> enter the RRC-GRA\_PCH state; + +1> continue with the remainder of the procedure. + +### 7.8.1.7 Physical channel failure + +If the received CELL UPDATE CONFIRM message would cause the MS to transit to RRC-Cell\_Dedicated state; and + +1> if the MS failed to establish the physical channel(s) indicated in the received CELL UPDATE CONFIRM message according to the criteria defined in sub-clause 7.8.1.6 are not fulfilled; or + +1> the received CELL UPDATE CONFIRM message does not contain the IE "*DBPSCH Description*"; + +the MS shall: + +1> the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to TRUE; and/or + +1> the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to TRUE: + +- 2> abort the ongoing integrity and/or ciphering reconfiguration; +- 2> if the received CELL UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + - 3> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - 3> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; +- 2> if the received CELL UPDATE CONFIRM message contained the IE "*Integrity Protection Mode Info*": + - 3> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - 3> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; +- 1> if the variable ORDERED\_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message: + - 2> set the variable ORDERED\_RECONFIGURATION to FALSE; +- 1> if V302 is equal to or smaller than N302: + - 2> select a suitable GERAN cell according to 3GPP TS 45.008; + - 2> set the contents of the CELL UPDATE message according to sub-clause 7.8.1.3, except for the IE "*Cell Update Cause*" which shall be set to "radio link failure"; + - 2> submit the CELL UPDATE message for transmission on the uplink SRB2; + - 2> increment counter V302; and + - 2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 3> restart timer T302; + - 2> if the RLC sub-layer indicates a link failure to the RRC layer: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 3> consider the Cell Update procedure to be unsuccessful; + - 3> the procedure ends. +- 1> if V302 is greater than N302: + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> in case of a cell update procedure: + - 3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 2> release all its radio resources; + - 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> set the variable CELL\_UPDATE\_STARTED to FALSE; + - 2> enter RRC-Idle mode. + +### 7.8.1.8 Unsupported configuration by the MS + +If the MS does not support the configuration in the CELL UPDATE CONFIRM message and/or the variable UNSUPPORTED\_CONFIGURATION is set to TRUE, the MS shall: + +- 1) if V302 is equal to or smaller than N302, the MS shall: + - 2) if, caused by the received CELL UPDATE CONFIRM message + - 3) the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to TRUE; and/or + - 3) the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to TRUE: + - 4) abort the ongoing integrity and/or ciphering reconfiguration; + - 4) if the received CELL UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + - l) 5) set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - m) 5) clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 4) if the received CELL UPDATE CONFIRM message contained the IE "*Integrity Protection Mode Info*": + - n) 5) set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - o) 5) clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2) if the variable ORDERED\_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure: + - 3) set the variable ORDERED\_RECONFIGURATION to FALSE; + - 2) set the variable FAILURE\_INDICATOR to TRUE; + - 2) set the variable FAILURE\_CAUSE to "configuration unsupported"; + - 2) set the content of the CELL UPDATE message according to 7.8.1.3; + - 2) submit the CELL UPDATE message for transmission on the uplink SRB2; + - 2) increment counter V302; and + - 2) if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 3) restart timer T302; + - 2) if the RLC sub-layer indicates a link failure to the RRC layer: + - 3) enter RRC-Idle mode; + - 3) perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 3) consider the Cell Update procedure to be unsuccessful; + - 3) the procedure ends. +- 1) if V302 is greater than N302, the MS shall: + - 2) clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2) clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2) clear the variable PDCP\_SN\_INFO; + - 2) clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + +- 2> release all its radio resources; +- 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; +- 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; +- 2> clear the variable ESTABLISHED\_RABS; +- 2> set the variable CELL\_UPDATE\_STARTED to FALSE; +- 2> enter RRC-Idle mode; +- 2> other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified in sub-clause 7.18; +- 2> and the procedure ends. + +### 7.8.1.9 Invalid configuration + +If the variable INVALID\_CONFIGURATION is set to TRUE, the MS shall: + +- 1> if V302 is equal to or smaller than N302: + - 2> if, caused by the received CELL UPDATE CONFIRM message + - 3> the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to TRUE; and/or + - 3> the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to TRUE: + - 4> abort the ongoing integrity and/or ciphering reconfiguration; + - 4> if the received CELL UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + - p) 5> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - q) 5> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 4> if the received CELL UPDATE CONFIRM message contained the IE "*Integrity Protection Mode Info*": + - r) 5> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - s) 5> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> if the variable ORDERED\_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure: + - 3> set the variable ORDERED\_RECONFIGURATION to FALSE; + - 2> in case of a Cell Update procedure: + - 3> set the variable FAILURE\_INDICATOR to TRUE; + - 3> set the variable FAILURE\_CAUSE to "Invalid configuration"; + - 3> set the contents of the CELL UPDATE message according to sub-clause 7.8.1.3; + - 3> submit the CELL UPDATE message for transmission on the uplink SRB2; + - 2> in case of a GRA Update procedure: + - 3> set the contents of the GRA UPDATE message according to sub-clause 7.8.1.3; + - 3> submit the GRA UPDATE message for transmission on the uplink SRB2; + +``` + +2> increment counter V302; and +2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + 3> restart timer T302; +2> if the RLC sub-layer indicates a link failure to the RRC layer: + 3> enter RRC-Idle mode; + 3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + 3> consider the Cell Update procedure or GRA Update procedure to be unsuccessful; + 3> the procedure ends. +1> if V302 is greater than N302: + 2> clear the variable RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO; + 2> clear the variable INTEGRITY_PROTECTION_ACTIVATION_INFO; + 2> clear the variable PDCP_SN_INFO; + 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the + variable TRANSACTIONS; + 2> release all its radio resources; + 2> indicate release (abort) of the established signalling connections (as stored in the variable + ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the + variable ESTABLISHED_RABS) to upper layers; + 2> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS; + 2> clear the variable ESTABLISHED_RABS; + 2> set the variable CELL_UPDATE_STARTED to FALSE; + 2> enter RRC-Idle mode; + 2> other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified + in sub-clause 7.18; +1> the procedure ends. + +``` + +#### 7.8.1.10 Incompatible simultaneous reconfiguration + +In case of a cell update procedure and if the received CELL UPDATE CONFIRM message: + +- includes RB information elements (*RB Information to Release list, RB Information to Reconfigure list, RB Information to Be Affected list*) ; and +- if the variable ORDERED\_RECONFIGURATION is set to TRUE because of an ongoing Reconfiguration procedure; + +or + +- includes RB information elements (*RB Information to Release list, RB Information to Reconfigure list, RB Information to Be Affected list*) and Transport channel information elements (IE "*Added or Reconfigured UL TrCH Information*", IE "*Added or Reconfigured DL TrCH Information*", IE "*Deleted DL TrCH Information*", IE "*Deleted UL TrCH Information*") ; and +- if the variable ORDERED\_RECONFIGURATION is set to TRUE because of an ongoing Reconfiguration procedure; + +or + +- if the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION is set to TRUE due to the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message: + +the MS shall: + +- 1> if V302 is equal to or smaller than N302: + - 2> if, caused by the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message + - 3> the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to TRUE; and/or + - 3> the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to TRUE: + - 4> abort the ongoing integrity and/or ciphering reconfiguration; + - 4> if the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + - t) 5> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - u) 5> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 4> if the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message contained the IE "*Integrity Protection Mode Info*": + - v) 5> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - w) 5> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> if the variable ORDERED\_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a Cell Update procedure: + - 3> set the variable ORDERED\_RECONFIGURATION to FALSE; + - 2> set the variable FAILURE\_INDICATOR to TRUE; + - 2> set the variable FAILURE\_CAUSE to "Incompatible simultaneous reconfiguration"; + - 2> set the content of the CELL UPDATE message according to sub-clause 7.8.1.3; + - 2> submit the CELL UPDATE message for transmission on the uplink SRB2; + - 2> increment counter V302; and + - 2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 3> restart timer T302; + - 2> if the RLC sub-layer indicates a link failure to the RRC layer: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 3> consider the Cell Update procedure to be unsuccessful; + - 3> the procedure ends. +- 1> if V302 is greater than N302: + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> clear the variable PDCP\_SN\_INFO; + - 2> set the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION to FALSE; + +- 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 2> release all its radio resources; + - 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> set the variable CELL\_UPDATE\_STARTED to FALSE; + - 2> enter RRC-Idle mode; + - 2> other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified in clause 6 and sub-clause 7.18; +- 1> the procedure ends. + +#### 7.8.1.10a Security reconfiguration during Cell update procedure + +If: + +- the variable CELL\_UPDATE\_STARTED is set to TRUE; and +- the MS receives a SECURITY MODE COMMAND message: + +the MS shall: + +- 1> ignore the received SECURITY MODE COMMAND message and continue with any ongoing processes and procedures as if the SECURITY MODE COMMAND message had not been received. + +#### 7.8.1.11 Confirmation error of GRA ID list + +If the GRA UPDATE CONFIRM message causes a confirmation error of GRA identity list as specified in sub-clause 7.19.3 the MS shall: + +- 1> check the value of V302; and +- 1> if V302 is smaller or equal than N302: + - 2> if, caused by the received GRA UPDATE CONFIRM message + - 3> the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to TRUE; and/or + - 3> the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to TRUE: + - 4> abort the ongoing integrity and/or ciphering reconfiguration; + - 4> if the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + - x) 5> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - y) 5> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 4> if the received GRA UPDATE CONFIRM message contained the IE "*Integrity Protection Mode Info*" + - z) 5> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - aa) 5> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + +- 2> set the IEs in the GRA UPDATE message according to sub-clause 7.8.1.3; +- 2> submit the GRA UPDATE message for transmission on the uplink SRB2; +- 2> increment counter V302; and +- 2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 3> restart timer T302; +- 2> if the RLC sub-layer indicates a link failure to the RRC layer: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 3> consider the GRA Update procedure to be unsuccessful; + - 3> the procedure ends. +- 1> if V302 is greater than N302: + - 2> release all its radio resources; + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> clear the variable PDCP\_SN\_INFO; + - 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> set the variable CELL\_UPDATE\_STARTED to FALSE; + - 2> enter RRC-Idle mode; + - 2> perform the actions specified in clause 6 and sub-clause 7.18 when entering RRC-Idle mode from RRC-Connected mode; + - 2> the procedure ends. + +### 7.8.1.12 Invalid CELL UPDATE CONFIRM/GRA UPDATE CONFIRM message + +If the MS receives an CELL UPDATE CONFIRM/GRA UPDATE CONFIRM message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows: + +- 1> if V302 is equal to or smaller than N302, the MS shall: + - 2> set the variable PROTOCOL\_ERROR\_INDICATOR to TRUE; + - 2> in case of a Cell Update procedure: + - 3> set the contents of the CELL UPDATE message according to sub-clause 7.8.1.3; + - 3> submit the CELL UPDATE message for transmission on the uplink SRB2; + - 2> in case of a GRA Update procedure: + - 3> set the contents of the GRA UPDATE message according to sub-clause 7.8.1.3; + - 3> submit the GRA UPDATE message for transmission on the uplink SRB2; + +- 2> increment counter V302; and +- 2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + - 3> restart timer T302; +- 2> if the RLC sub-layer indicates a link failure to the RRC layer: + - 3> enter RRC-Idle mode; + - 3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + - 3> consider the Cell Update procedure or GRA update procedure to be unsuccessful; + - 3> the procedure ends. +- 1> if V302 is greater than N302, the MS shall: + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> in case of a Cell Update procedure: + - 3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 2> in case of a GRA Update procedure: + - 3> clear the entry for the GRA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> set the variable CELL\_UPDATE\_STARTED to FALSE; + - 2> release all its radio resources; + - 2> enter RRC-Idle mode; + - 2> other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified in clause 6 and sub-clause 7.18; + - 2> the procedure ends. + +### 7.8.1.13 T302 expiry or cell reselection + +If any or several of the following conditions are true: + +- expiry of timer T302; +- reselection to another GERAN cell (including the previously serving cell) before completion of the Cell Update or GRA Update procedure; + +the MS shall: + +- 1> stop T302 if it is running; +- 1> if the MS was in RRC-Cell\_Dedicated state prior to the initiation of the procedure; and +- 2> if timers T314 and T315 have elapsed while T302 was running: + - 3> enter RRC-Idle mode. + +- 3> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers. Other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified in clause 6 and sub-clause 7.18. +- 3> and the procedure ends. +- 2> if timer T314 has elapsed while T302 was running and, + - 3> if "*T314 Expired*" in the variable RB\_TIMER\_INDICATOR is set to FALSE and + - 3> if T315 is still running: + - 4> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED\_RABS the value of the IE "*Re-establishment Timer*" is set to "useT314"; + - 4> indicate release of those radio access bearers to upper layers; + - 4> delete all information about those radio access bearers from the variable ESTABLISHED\_RABS; + - 4> set "*T314 Expired*" in the variable RB\_TIMER\_INDICATOR to TRUE; +- 2> if timer T315 has elapsed while T302 was running and, + - 3> if "*T315 Expired*" in the variable RB\_TIMER\_INDICATOR is set to FALSE and, + - 3> if T314 is still running: + - 4> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED\_RABS the value of the IE "*Re-establishment Timer*" is set to "useT315"; + - 4> indicate release of those radio access bearers to upper layers; + - 4> delete all information about those radio access bearers from the variable ESTABLISHED\_RABS; + - 4> set "*T315 Expired*" in the variable RB\_TIMER\_INDICATOR to TRUE; +- 1> if, caused by the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to TRUE and/or the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to TRUE: + - 2> abort the ongoing integrity and/or ciphering reconfiguration; + - 2> if the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message contained the IE "*Ciphering Mode Info*": + - 3> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - 3> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> if the received CELL UPDATE CONFIRM or GRA UPDATE CONFIRM message contained the IE "*Integrity Protection Mode Info*": + - 3> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - 3> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; +- 1> if the variable ORDERED\_RECONFIGURATION is set to TRUE caused by the received CELL UPDATE CONFIRM message in case of a cell update procedure: + - 2> set the variable ORDERED\_RECONFIGURATION to FALSE; +- 1> in case of a Cell Update procedure: + - 2> clear any entry for the CELL UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; +- 1> in case of a GRA Update procedure: + +2> clear any entry for the GRA UPDATE CONFIRM message in the table "Accepted transactions" in the variable TRANSACTIONS; + +If the MS has not entered RRC-Idle mode, and: + +1> if V302 is equal to or smaller than N302, the MS shall: + +2> in case of a Cell Update procedure: + +3> set the contents of the CELL UPDATE message according to sub-clause 7.8.1.3; + +3> if a CELL UPDATE CONFIRM message was received and caused the IE "Reconfiguration" in the variable CIPHERING\_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable INTEGRITY\_PROTECTION\_INFO to be set to TRUE: + +4> if the IE "Downlink counter synchronization info" was included in the received CELL UPDATE CONFIRM message: + +bb) 5> apply the new security (integrity protection) configuration received in the CELL UPDATE CONFIRM on the CELL UPDATE message. + +3> submit the CELL UPDATE message for transmission on the uplink SRB2; + +2> in case of a GRA Update procedure: + +3> set the contents of the GRA UPDATE message according to sub-clause 7.8.1.3; + +3> if a GRA UPDATE CONFIRM message was received and caused the IE "Reconfiguration" in the variable CIPHERING\_STATUS to be set to TRUE and/or the IE "Reconfiguration" in the variable INTEGRITY\_PROTECTION\_INFO to be set to TRUE: + +4> if the IE "Downlink counter synchronization info" was included in the received GRA UPDATE CONFIRM message: + +cc) 5> apply the new security (integrity protection) configuration received in the GRA UPDATE CONFIRM on the GRA UPDATE message. + +3> submit the GRA UPDATE message for transmission on the uplink SRB2.; + +2> increment counter V302; + +2> if the RLC sub-layer indicates to the RRC layer a successful transmission of the message: + +3> restart timer T302; + +2> if the RLC sub-layer indicates a link failure to the RRC layer: + +3> enter RRC-Idle mode; + +3> perform the actions specified in clause 6 when MS is in RRC-Idle mode; + +3> consider the Cell Update procedure or GRA Update procedure to be unsuccessful; + +3> the procedure ends. + +1> if V302 is greater than N302, the MS shall: + +2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + +2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + +2> clear the variable PDCP\_SN\_INFO; + +2> in case of a Cell Update procedure: + +3> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + +- 2> in case of a GRA Update procedure: + - 3> clear the entry for the GRA UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; +- 2> release all its radio resources; +- 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; +- 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; +- 2> clear the variable ESTABLISHED\_RABS; +- 2> set the variable CELL\_UPDATE\_STARTED to FALSE; +- 2> enter RRC-Idle mode; +- 2> other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified in clause 6 and sub-clause 7.18; +- 2> and the procedure ends. + +#### 7.8.1.14 T314 expiry + +Upon expiry of timer T314 the MS shall: + +- 1> if timer T302 is running: + - 2> continue awaiting response message from GERAN; +- 1> if timer T302 is not running and timer T315 is running: + - 2> set IE "*T314 Expired*" in variable RB\_TIMER\_INDICATOR to TRUE; + - 2> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED\_RABS the value of the IE "*Re-establishment Timer*" is set to "use T314"; + - 2> indicate release of those radio access bearers to upper layers; + - 2> delete all information about those radio access bearers from the variable ESTABLISHED\_RABS; +- 1> if timers T302 and T315 are not running: + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> clear the variable PDCP\_SN\_INFO; + - 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 2> release all its radio resources; + - 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> set the variable CELL\_UPDATE\_STARTED to FALSE; + - 2> enter RRC-Idle mode; + +- 2> other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified in clause 6 and sub-clause 7.18; +- 2> and the procedure ends. + +### 7.8.1.15 T315 expiry + +Upon expiry of timer T315 the MS shall: + +- 1> if timer T302 is running: + - 2> continue awaiting response message from GERAN; +- 1> if timer T302 is not running and timer T314 is running: + - 2> set IE "*T315 Expired*" in variable RB\_TIMER\_INDICATOR to TRUE; + - 2> release locally all radio bearers which are associated with any radio access bearers for which in the variable ESTABLISHED\_RABS the value of the IE "*Re-establishment Timer*" is set to "use T315"; + - 2> indicate release of those radio access bearers to upper layers; + - 2> delete all information about those radio access bearers from the variable ESTABLISHED\_RABS; +- 1> if timers T302 and T314 are not running: + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> clear the variable PDCP\_SN\_INFO; + - 2> clear the entry for the CELL UPDATE CONFIRM message in the table "Rejected transactions" in the variable TRANSACTIONS; + - 2> release all its radio resources; + - 2> indicate release (abort) of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> set the variable CELL\_UPDATE\_STARTED to FALSE; + - 2> enter RRC-Idle mode; + - 2> other actions the MS shall perform when entering RRC-Idle mode from RRC-Connected mode are specified in clause 6 and sub-clause 7.18; + - 2> and the procedure ends. + +### 7.8.1.16 Reception of the GERAN MOBILITY INFORMATION CONFIRM message by the GERAN + +See sub-clause 7.8.1.6. + +### 7.8.1.17 Inter-RAT cell reselection to GERAN *Iu mode* + +#### 7.8.1.17.1 General + +The purpose of the inter-RAT cell reselection procedure to GERAN *Iu mode* is to transfer, under the control of the MS and to some extent the source radio access technology, a connection between the MS and another radio access technology (e.g. UTRAN) to GERAN *Iu mode*. + +#### 7.8.1.17.2 Initiation + +When the MS makes an inter-RAT cell reselection to GERAN *Iu mode* according to the criteria specified in 3GPP TS 44.160, it shall initiate this procedure. The inter-RAT cell reselection made by the MS may use system information broadcast from the source radio access technology or MS dedicated information. + +When the MS performs an inter-RAT cell reselection from a RAT other than UTRAN, the MS shall: + +- 1) set the variable ESTABLISHMENT\_CAUSE to "Inter-RAT cell reselection"; +- 1) initiate an RRC connection establishment procedure as specified in sub-clause 7.5; +- 1) after initiating an RRC connection establishment: + - 2) release all resources specific to the other radio access technology. + +When the MS performs an inter-RAT cell reselection from UTRAN Cell\_FACH or Cell\_PCH state to GERAN *Iu mode*, the MS shall: + +- 1) initiate the cell update procedure as specified in sub-clause 7.8, using the cause "cell reselection" and setting the U-RNTI in the IE "*G-RNTT*". + +When the MS performs an inter-RAT cell reselection from UTRAN URA\_PCH, the MS shall: + +- 1) compare the URA identity which the MS had been assigned to in UTRAN against the GRA identities which are broadcast in the GERAN cell. + - 2) If the assigned URA identity is not present in the list of GRA identities that are broadcast in the GERAN cell: + - 3) initiate the GRA update procedure as specified for the GRA reselection case in sub-clause 7.8, using the cause "change of GRA" and setting the U-RNTI in the IE "*G-RNTT*". + +#### 7.8.1.17.3 MS fails to complete an inter-RAT cell reselection + +When the MS performs an inter-RAT cell reselection from a RAT other than UTRAN, and if the inter-RAT cell reselection fails before the MS has initiated the RRC connection establishment, the MS may return back to the other radio access technology. + +When the MS performs an inter-RAT cell reselection from a RAT other than UTRAN, and if the RRC connection establishment fails, the MS shall enter RRC-Idle mode. + +When the MS performs an inter-RAT cell reselection from UTRAN to GERAN *Iu mode*, and the cell reselection fails, the MS may return back to the UTRAN RRC Connected state, from which it initiated the inter-RAT cell reselection. + +### 7.8.1.18 Inter-RAT cell reselection from GERAN *Iu mode* + +#### 7.8.1.18.1 General + +The purpose of the inter-RAT cell reselection procedure from GERAN *Iu mode* is to transfer, under the control of the MS and to some extent the GERAN, a connection between the MS and GERAN *Iu mode* to another radio access technology (e.g. UTRAN). + +#### 7.8.1.18.2 Initiation + +This procedure is applicable in states RRC-Cell\_Shared or RRC GRA\_PCH. + +When the MS based on received system information makes an inter-RAT cell reselection to a radio access technology other than UTRAN, according to the criteria specified in 3GPP TS 44.160, the MS shall: + +- 1) initiate the establishment of a connection to the target radio access technology according to its specifications. + +When the MS in RRC-Cell\_Shared state performs an inter-RAT cell reselection to UTRAN, according to the criteria specified in 3GPP TS 44.160, the MS shall: + +- 1> initiate the cell update procedure according to 3GPP TS 25.331, using the cause "cell reselection" and setting the G-RNTI in the IE "*U-RNTT*". When the MS in RRC-GERAN\_PCH state performs an inter-RAT cell reselection to UTRAN, according to the criteria specified in 3GPP TS 44.160, the MS shall: +- 1> compare the GRA identity which the MS had been assigned to in GERAN against the URA identities which are broadcast in the UTRAN cell. +- 2> If the assigned GRA identity is not present in the list of URA identities that are broadcast in the UTRAN cell: + - 3> initiate the URA update procedure as specified in 3GPP TS 25.331, using the cause "change of URA" and setting the G-RNTI in the IE "*U-RNTT*". + +#### 7.8.1.18.3 Successful cell reselection + +When the MS has succeeded in reselecting a cell in the target radio access technology other than UTRAN and has initiated the establishment of a connection, it shall release all GERAN specific resources. + +When the MS has succeeded in reselecting to a UTRAN cell, it shall release all GERAN specific radio resources. + +#### 7.8.1.18.4 MS fails to complete an inter-RAT cell reselection + +If the inter-RAT cell reselection to another radio access technology fails, the MS shall resume the connection to GERAN *Iu mode* using the resources used before initiating the inter-RAT cell reselection procedure. + +### 7.8.2 GRA update + +See sub-clause 7.8.1. + +### 7.8.3 GERAN mobility information + +![Sequence diagram for GERAN Mobility Information procedure, normal flow. The diagram shows two participants: MS and GERAN. The MS sends a 'GERAN MOBILITY INFORMATION' message to the GERAN. The GERAN responds with a 'GERAN MOBILITY INFORMATION CONFIRM' message back to the MS.](1274805226c5a1f8b875aea0296b9f0f_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + Note left of MS: MS requests GERAN Mobility Information + MS->>GERAN: GERAN MOBILITY INFORMATION + Note right of GERAN: GERAN confirms + GERAN-->>MS: GERAN MOBILITY INFORMATION CONFIRM +``` + +Sequence diagram for GERAN Mobility Information procedure, normal flow. The diagram shows two participants: MS and GERAN. The MS sends a 'GERAN MOBILITY INFORMATION' message to the GERAN. The GERAN responds with a 'GERAN MOBILITY INFORMATION CONFIRM' message back to the MS. + +Figure 7.8.3.1: GERAN Mobility Information procedure, normal flow + +![Sequence diagram for GERAN Mobility Information procedure, failure case. The diagram shows two participants: MS and GERAN. The MS sends a 'GERAN MOBILITY INFORMATION' message to the GERAN. The GERAN responds with a 'GERAN MOBILITY INFORMATION FAILURE' message back to the MS.](b97737027bd1b2effd7ca4dba8914877_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + Note left of MS: MS requests GERAN Mobility Information + MS->>GERAN: GERAN MOBILITY INFORMATION + Note right of GERAN: GERAN fails + GERAN-->>MS: GERAN MOBILITY INFORMATION FAILURE +``` + +Sequence diagram for GERAN Mobility Information procedure, failure case. The diagram shows two participants: MS and GERAN. The MS sends a 'GERAN MOBILITY INFORMATION' message to the GERAN. The GERAN responds with a 'GERAN MOBILITY INFORMATION FAILURE' message back to the MS. + +Figure 7.8.3.2: GERAN Mobility Information procedure, failure case + +#### 7.8.3.1 General + +The purpose of this procedure is to allocate any one or a combination of the following to a MS in Connected Mode: + +- a new G-RNTI; +- other mobility related information. + +### 7.8.3.2 Initiation + +To initiate the procedure GERAN transmits a GERAN MOBILITY INFORMATION message to the MS on the downlink SRB2. + +### 7.8.3.3 Reception of GERAN MOBILITY INFORMATION message by the MS + +When the MS receives a GERAN MOBILITY INFORMATION message, it shall: + +1> act on received information elements as specified in sub-clause 7.19; + +1> if the IE "*MS Timers and Constants in Connected Mode*" is present: + +2> store the values of the IE "*MS Timers and Constants in Connected Mode*" in the variable TIMERS\_AND\_CONSTANTS, replacing any previously stored value; and + +2> for each updated timer value: + +3> start using the new value next time the timer is started; + +NOTE: If a new value of timer T305 is included in the IE "*MS Timers and constants in connected mode*", and the old value of timer T305 is "infinity", the MS will not use the new value of the timer T305 until the next cell reselection. + +1> set the IE "*RRC Transaction Identifier*" in the GERAN MOBILITY INFORMATION CONFIRM message to the value of "*RRC transaction identifier*" in the entry for the GERAN MOBILITY INFORMATION message in the table "*Accepted transactions*" in the variable TRANSACTIONS; and + +1> clear that entry; + +1> if the GERAN MOBILITY INFORMATION message contained the IE "*Ciphering Mode Info*" or contained the IE "*Integrity Protection Mode Info*": + +2> set the IE "*Status*" in the variable SECURITY\_MODIFICATION for all the CN domains in the variable SECURITY\_MODIFICATION to "*Affected*"; + +1> if the GERAN MOBILITY INFORMATION message contained the IE "*Ciphering Mode Info*": + +2> include the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" in the GERAN MOBILITY INFORMATION CONFIRM message and set to the value of the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + +1> if the variable PDCP\_SN\_INFO is non-empty: + +2> include the IE "*RB with PDCP Information List*" in the GERAN MOBILITY INFORMATION CONFIRM message and set it to the value of the variable PDCP\_SN\_INFO; + +1> if the received GERAN MOBILITY INFORMATION message included the structure "*Downlink Counter Synchronisation Info*": + +2> if the variable PDCP\_SN\_INFO is empty: + +3> configure the corresponding RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except SRB2 to "*stop*"; + +2> else: + +3> configure the RLC entity for signalling radio bearers SRB1, SRB3 and SRB4 to "*stop*"; + +3> configure the RLC entity for UM and AM radio bearers for which the IE "*PDCP SN Info*" is not included to "*stop*"; + +2> re-establish SRB2; + +2> for the downlink and the uplink, apply the ciphering configuration as follows: + +3> if the received re-configuration message included the IE "*Ciphering Mode Info*": + +- 4> use the ciphering configuration in the received message when transmitting the response message; + - 3> if the ciphering configuration for SRB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the activation times not having been reached: + - 4> if the previous SECURITY MODE COMMAND was received due to new keys being received: + - dd)5> consider the new ciphering configuration to include the received new keys; + - ee)5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 as indicated in subclause 7.16.1.2.3.1. + - 4> if the ciphering configuration for SRB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the previous SECURITY MODE COMMAND caused a change in LATEST\_CONFIGURED\_CN\_DOMAIN: + - ff)5> initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 to the most recently transmitted IE "*START List*" or IE "*START*" for the LATEST\_CONFIGURED\_CN\_DOMAIN at the reception of the previous SECURITY MODE COMMAND message. + - gg)5> consider the new ciphering configuration to include the keys associated with the LATEST\_CONFIGURED\_CN\_DOMAIN; + - 4> apply the new ciphering configuration immediately following RLC re-establishment. + - 3> else: + - 4> continue using the current ciphering configuration; +- 2> set the new uplink and downlink HFN of SRB2 to MAX (uplink HFN of SRB2, downlink HFN of SRB2) + 1; +- 2> increment by one the downlink and uplink HFN values for SRB2; +- 2> calculate the START value according to sub-clause 7.18; +- 2> include the calculated START values for each CN domain in the IE "*START List*" in the structure "*Uplink Counter Synchronisation Info*" in the GERAN MOBILITY INFORMATION CONFIRM message; +- 1> transmit a GERAN MOBILITY INFORMATION CONFIRM message on the uplink SRB2; +- 1> if the IE "*Integrity Protection Mode Info*" was present in the GERAN MOBILITY INFORMATION message: + - 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer SRB2 from and including the transmitted GERAN MOBILITY INFORMATION CONFIRM message; +- 1> if the structure "*Downlink Counter Synchronisation Info*" was included in the received GERAN MOBILITY INFORMATION message: + - 2> when RLC has confirmed the successful transmission of the response message: + - 3> if the variable PDCP\_SN\_INFO is empty: + - 4> configure the RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except SRB2 to "continue"; + - 3> else: + - 4> configure the RLC entity for signalling radio bearers SRB1, SRB3 and SRB4 to "continue"; + - 4> configure the RLC entity for UM and AM radio bearers for which the IE "*PDCP SN Info*" is not included to "continue"; + +- 3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; + - 3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + - 3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero; + - 3> set the remaining bits of the HFN component of the COUNT-C values of all AM RLC entities to zero, for those bearers to which RLC entities were re-established; + - 3> if the IE "*PDCP Context Relocation Info*" is not present: + - 4> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED\_RABS as specified in 3GPP TS 25.323; + - 3> if the IE "*PDCP Context Relocation Info*" is present: + - 4> perform the actions as specified in 7.19. +- 1> if the variable PDCP\_SN\_INFO is empty; and + - 2> if the GERAN MOBILITY INFORMATION message contained the IE "*Ciphering Mode Info*": + - 3> when RLC has confirmed the successful transmission of the GERAN MOBILITY INFORMATION CONFIRM message, perform the actions below; + - 2> if the GERAN MOBILITY INFORMATION message did not contain the IE "*Ciphering Mode Info*": + - 3> when RLC has been requested to transmit the GERAN MOBILITY INFORMATION CONFIRM message, perform the actions below; + - 1> if the variable PDCP\_SN\_INFO is non-empty: + - 2> when RLC has confirmed the successful transmission of the GERAN MOBILITY INFORMATION CONFIRM message: + - 3> for each radio bearer in the variable PDCP\_SN\_INFO: + - 4> if the IE "*RB Started*" in the variable ESTABLISHED\_RABS is set to "started": + - 4> configure the RLC entity for that radio bearer to "continue"; + - 3> clear the variable PDCP\_SN\_INFO; + - 1> if the GERAN MOBILITY INFORMATION message contained the IE "*Ciphering Mode Info*": + - 2> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 1> if the GERAN MOBILITY INFORMATION message contained the IE "*Integrity Protection Mode Info*": + - 2> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; + - 2> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> clear the variable SECURITY\_MODIFICATION. + +The procedure ends. + +### 7.8.3.4 Reception of an GERAN MOBILITY INFORMATION CONFIRM message by the GERAN + +When the network receives GERAN MOBILITY INFORMATION CONFIRM message, GERAN may delete any old G-RNTI. The procedure ends. + +### 7.8.3.5 Cell re-selection + +If the MS performs cell re-selection, the MS shall: + +- 1> initiate a Cell Update procedure according to sub-clause 7.8.1; +- 1> if the MS has not yet submitted the GERAN MOBILITY INFORMATION CONFIRM message to lower layers for transmission; + - 2> transmit a GERAN MOBILITY INFORMATION FAILURE message on the uplink SRB2; + - 2> set the IE "*RRC Transaction Identifier*" in the GERAN MOBILITY INFORMATION FAILURE message to the value of "*RRC transaction identifier*" in the entry for the GERAN MOBILITY INFORMATION message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry. + - 2> set the IE "*Failure Cause*" to the cause value "cell reselection"; + - 2> when the GERAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for transmission: + - 3> continue with any ongoing processes and procedures as if the invalid GERAN MOBILITY INFORMATION message has not been received and the procedure ends. +- 1> otherwise: + - 2> continue the procedure normally. + +### 7.8.3.6 Incompatible simultaneous security reconfiguration + +If the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION becomes set to TRUE because of the received GERAN MOBILITY INFORMATION message, the MS shall: + +- 1> transmit a GERAN MOBILITY INFORMATION FAILURE message on the uplink SRB2; +- 1> set the IE "*RRC Transaction Identifier*" in the GERAN MOBILITY INFORMATION FAILURE message to the value of "*RRC transaction identifier*" in the entry for the GERAN MOBILITY INFORMATION message in the table "Accepted transactions" in the variable TRANSACTIONS; and +- 1> clear that entry; +- 1> set the IE "*Failure Cause*" to the cause value "incompatible simultaneous reconfiguration"; +- 1> when the GERAN MOBILITY INFORMATION FAILURE message has been delivered to lower layers for transmission: + - 2> set the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION to FALSE; + - 2> continue with any ongoing processes and procedures as if the GERAN MOBILITY INFORMATION message has not been received; + - 2> and the procedure ends. + +### 7.8.3.7 Invalid GERAN MOBILITY INFORMATION message + +If the GERAN MOBILITY INFORMATION message contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows. The MS shall: + +- 1> transmit a GERAN MOBILITY INFORMATION FAILURE message on the uplink SRB2; +- 1> set the IE "*RRC Transaction Identifier RRC*" in the GERAN MOBILITY INFORMATION FAILURE message to the value of "*RRC transaction identifier*" in the entry for the GERAN MOBILITY INFORMATION message in the table "*Rejected transactions*" in the variable *TRANSACTIONS*, and; +- 1> clear that entry. +- 1> set the IE "*Failure Cause*" to the cause value "protocol error"; +- 1> include the IE "*Protocol Error Information*" with contents set to the value of the variable *PROTOCOL\_ERROR\_INFORMATION*; +- 1> when the GERAN MOBILITY INFORMATION FAILURE message has been submitted to lower layers for transmission: + - 2> continue with any ongoing processes and procedures as if the invalid GERAN MOBILITY INFORMATION message has not been received; +- 1> and the procedure ends. + +## 7.8.4 Inter-mode handover from GERAN Iu mode + +### 7.8.4.1 General + +![Sequence diagram for successful inter-mode handover from GERAN Iu mode. The diagram shows two vertical lifelines: MS (Mobile Station) on the left and GERAN on the right. A horizontal arrow labeled 'HANDOVER FROM GERAN Iu COMMAND' points from the GERAN lifeline to the MS lifeline.](907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg) + +Sequence diagram for successful inter-mode handover from GERAN Iu mode. The diagram shows two vertical lifelines: MS (Mobile Station) on the left and GERAN on the right. A horizontal arrow labeled 'HANDOVER FROM GERAN Iu COMMAND' points from the GERAN lifeline to the MS lifeline. + +Figure 7.8.4.1.1: Inter-mode handover from GERAN, successful case + +![Sequence diagram for failed inter-mode handover from GERAN Iu mode. The diagram shows two vertical lifelines: MS (Mobile Station) on the left and GERAN on the right. A horizontal arrow labeled 'HANDOVER FROM GERAN Iu COMMAND' points from the GERAN lifeline to the MS lifeline. A second horizontal arrow labeled 'HANDOVER FAILURE' points from the MS lifeline back to the GERAN lifeline.](d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg) + +Sequence diagram for failed inter-mode handover from GERAN Iu mode. The diagram shows two vertical lifelines: MS (Mobile Station) on the left and GERAN on the right. A horizontal arrow labeled 'HANDOVER FROM GERAN Iu COMMAND' points from the GERAN lifeline to the MS lifeline. A second horizontal arrow labeled 'HANDOVER FAILURE' points from the MS lifeline back to the GERAN lifeline. + +Figure 7.8.4.1.2: Inter-mode handover from GERAN Iu mode, failure case + +The purpose of the Inter-Mode Handover from GERAN Iu procedure is to, under the control of the network, transfer a connection between the MS and GERAN *Iu mode* to GERAN *A/Gb mode*. This procedure may be used to request an intercell or intracell change of channel(s) by the network, in RRC-Cell\_Dedicated state. + +NOTE: This procedure is applicable to CS domain service. + +### 7.8.4.2 Initiation + +The procedure is initiated when GERAN *Iu mode* orders a MS in RRC-Cell\_Dedicated state, to make a handover to GERAN *A/Gb mode*. + +To initiate the procedure, GERAN sends a HANDOVER FROM GERAN Iu COMMAND message. + +Upon the receipt of HANDOVER FROM GERAN Iu COMMAND message, the mobile station shall: + +- 1> initiate reconfiguration of the layer 2 and disconnection of the DBPSCHs; +- 1> switch to the assigned cell(s) and establish the physical channels as described in 3GPP TS 44.018. + +#### 7.8.4.3 Reception of a HANDOVER FROM GERAN Iu COMMAND message by the MS + +The MS shall be able to receive a HANDOVER FROM GERAN Iu COMMAND message and perform an inter-mode handover, even if no prior MS measurements have been performed on the target cell. The connection is established in GERAN A/Gb mode by using the contents of encapsulated message HANDOVER COMMAND message (see 3GPP TS 44.018) + +If the IE "*RAB information List*" is included in the HANDOVER FROM GERAN Iu COMMAND message: + +- 1> if the IE "*RAB information List*" includes one IE "*RAB Info*" with the IE "*CN domain Identity*" set to "*CS domain*": + - 2> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the encapsulated HANDOVER COMMAND message. + - 2> and act upon received information element as specified 3GPP TS 44.018. + +NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "*RAB information List*" is limited to 1. + +#### 7.8.4.4 Successful completion of the inter-mode handover + +Upon successfully completing the handover, GERAN shall: + +- 1> release the radio connection; + +Upon successfully completing the handover, the MS shall: + +- 1> if inter-mode handover is performed and if there are any NAS messages with the IE "*CN domain identity*" set to "*CS domain*" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer SRB3 or signalling radio bearer SRB4 has not yet been confirmed by RLC: + - 2> retransmit those NAS messages to the network on the newly established radio connection to the system. + - 3> clear or set variables upon leaving GERAN RRC-Connected mode as specified in sub-clauses 7.19 and 10.4. + +#### 7.8.4.5 Unsuccessful completion of the inter-mode handover at the MS side + +If the MS does not succeed in establishing the connection to the target, it shall: + +- 1> revert back to the GERAN configuration; +- 1> establish the GERAN physical channel(s) used at the time for reception of HANDOVER FROM GERAN Iu COMMAND; +- 1> if the MS does not succeed to establish the GERAN physical channel(s): + - 2> select a suitable GERAN cell according to 3GPP TS 45.008. + - 2> perform a Cell Update procedure according to sub-clause 7.8 with cause "*radio link failure*"; + - 2> when the Cell Update procedure has completed successfully: + - 3> proceed as below; +- 1> transmit the HANDOVER FAILURE message setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + +- 2> set it to the value of "RRC Transaction Identifier" in the entry for the HANDOVER FROM GERAN Iu COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and +- 2> clear that entry; +- 2> set the IE "Failure Cause" to "physical channel failure"; +- 1> when the HANDOVER FAILURE message has been submitted to lower layer for transmission: + - 2> the procedure ends. + +#### 7.8.4.6 Invalid HANDOVER FROM GERAN Iu COMMAND message + +If the received HANDOVER FROM GERAN Iu COMMAND message does not include a valid encapsulated HANDOVER COMMAND message (see 3GPP TS 44.018), the MS shall perform procedure specific error handling as follows. The MS shall: + +- 1> set the IE "*Failure Cause*" to the cause value "Inter-mode Protocol Error"; +- 1> transmit a HANDOVER FAILURE message on the uplink SRB2; +- 1> when the transmission of the HANDOVER FAILURE message has been confirmed by RLC: + - 2> continue with any ongoing processes and procedures as if the invalid HANDOVER FROM GERAN Iu COMMAND message has not been received; + - 2> and the procedure ends. + +If the HANDOVER FROM GERAN Iu COMMAND message contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows. The MS shall: + +- 1> set the IE "*RRC Transaction Identifier*" in the HANDOVER FAILURE message to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM GERAN Iu COMMAND message in the table "Rejected transactions" in the variable TRANSACTIONS; and +- 1> clear that entry; +- 1> set the IE "Failure Cause" to the cause value "protocol error"; +- 1> include the IE "Protocol Error Information" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION; +- 1> transmit a HANDOVER FAILURE message on the uplink SRB2; +- 1> when the HANDOVER FAILURE message has been submitted to lower layers for transmission: + - 2> continue with any ongoing processes and procedures as if the invalid HANDOVER FROM GERAN Iu COMMAND message has not been received; + - 2> and the procedure ends. + +#### 7.8.4.7 Reception of an HANDOVER FAILURE message by GERAN in Iu mode + +Upon receiving an HANDOVER FAILURE message, GERAN may initiate the release of the resources in the GERAN A/Gb mode (see 3GPP TS 44.018 and 3GPP TS 25.413). + +#### 7.8.4.8 Unsupported configuration in HANDOVER FROM GERAN Iu COMMAND message + +If: + +- the GERAN instructs the MS to perform a non-supported handover scenario; or +- the GERAN instructs the MS to use a non-supported configuration; or + +- the IE "*RAB Information List*" is included in the HANDOVER FROM GERAN Iu mode COMMAND message and this IE does not include any IE "RAB Info" with the IE "CN domain Identity" set to "CS domain": + +the MS shall: + +- 1> transmit a HANDOVER FAILURE message, setting the information elements as specified below: + - 2> include the IE "RRC Transaction Identifier"; and + - 2> set it to the value of "RRC Transaction Identifier" in the entry for the HANDOVER FROM GERAN Iu COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "Failure Cause" to "configuration unsupported"; + - 2> when the HANDOVER FAILURE message has been submitted to lower layers for transmission: + - 3> resume normal operation as if the invalid HANDOVER FROM GERAN Iu COMMAND message has not been received; + - 3> and the procedure ends. + +#### 7.8.4.9 Reception of HANDOVER FROM GERAN Iu COMMAND message by MS in RRC-Cell\_Shared state + +If the MS receives HANDOVER FROM GERAN Iu COMMAND while in RRC-Cell\_Shared state, the MS shall: + +- 1> transmit a HANDOVER FAILURE message, setting the information elements as specified below: + - 2> include the IE "RRC Transaction Identifier"; and + - 2> set it to the value of "RRC Transaction Identifier" in the entry for the HANDOVER FROM GERAN Iu COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "Failure Cause" to "protocol error"; + - 3> include IE "Protocol Error Information"; + - 3> set the value of IE "Protocol Error Cause" to "Message not compatible with receiver state"; and + - 2> when the HANDOVER FAILURE message has been submitted to lower layers for transmission: + - 3> resume normal operation as if the invalid HANDOVER FROM GERAN Iu COMMAND message has not been received; + - 3> and the procedure ends. + +### 7.9 Procedures for System Information transmission and Measurement reporting in RRC-Cell\_Dedicated state + +NOTE: Any modification to this sub-clause may have impact on 3GPP TS 44.018. + +#### 7.9.1 General + +In RRC-Cell\_Dedicated state, the mobile station sends measurement report messages and receives system information on SRB1. + +In the uplink direction, measurement report messages are sent using SRB1 at each possible occasion when no other RRC message has to be sent (see sub-clause 7.9.2). Similarly, in the downlink direction, SYSTEM INFORMATION TYPE 5, 6 and optionally 5bis and 5ter messages are sent on SRB1 when no other RRC message has to be sent. The network may, in addition, send MEASUREMENT INFORMATION messages on SRB1 to a mobile station in RRC- + +Cell\_Dedicated state. This message may order the MS to use the enhanced measurement reporting. The mapping of SRB1 onto logical channels is specified in 3GPP TS 44.160. + +A mobile station with extended measurement capabilities, which receives EXTENDED MEASUREMENT ORDER messages on SRB1, shall perform and report extended measurements, see sub-clause 7.9.3. + +The SYSTEM INFORMATION TYPE 5bis message shall be sent if and only if the EXT IND bit in the *Neighbour Cell Description* information element in both the SYSTEM INFORMATION TYPE 5 and TYPE 5bis messages indicates that each information element only carries part of the BA. + +A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) may consider the EXT-IND bit in the *Neighbour Cell Description* IE in the SYSTEM INFORMATION TYPE 5 message bit as a spare bit, assume that the information element carries the complete BA, and ignore any SYSTEM INFORMATION TYPE 5bis messages. + +NOTE: The network should take into account limitations of certain mobile stations to understand SYSTEM INFORMATION TYPE 5ter and TYPE 5bis messages, the EXT-IND bit in the *Neighbour Cell Description* IE, and formats used in the *Neighbour Cell Description* information element and *Cell Channel Description* information element used in system information messages, see 3GPP TS 44.018. + +Problems occurring in the reception of SACCH frames are interpreted as a loss of communication means and appropriate procedures are then triggered as specified in 3GPP TS 45.008. + +## 7.9.2 Measurement Report and Enhanced Measurement Report + +### 7.9.2.2 Parameters for Measurements and Reporting + +#### 7.9.2.2.1 General + +Some parameters from the MEASUREMENT INFORMATION or PSI3quater messages allow an MS to build lists which are used for Measurement reporting and Enhanced Measurement reporting. + +Full sets of MEASUREMENT INFORMATION messages and PSI3quater messages are defined by a number of different instances indicated respectively by the parameters MI\_COUNT and PSI3\_QUATER\_COUNT. Two different instances of MEASUREMENT INFORMATION messages and PSI3quater messages are respectively distinguished by different MI\_INDEX and PSI3\_QUATER\_INDEX parameter values. + +If the MP\_CHANGE\_MARK parameter or the PSI3\_CHANGE\_MARK parameter is changed, the MS shall re-read the Real Time differences, REP\_PRIORITY, CCN\_SUPPORTED, Measurement Parameters and 3G Measurement Parameters in all instances of respectively MEASUREMENT INFORMATION messages or PSI3quater messages. The MS shall start using the parameters as soon as they have been received. In the case that not all the parameters have been received in a full set of instances, then the default values shall be used. If different values occur for the same parameter in different instances of a MEASUREMENT INFORMATION message or PSI3quater message, the instance with the highest index shall be used. + +#### 7.9.2.2.2 Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description + +A multi-RAT MS shall form a 3G Neighbour Cell list. + +In RRC-Idle mode, the MS obtains the 3G Neighbour Cell Description information on PBCCH by one or more instances of the PSI3quater message as specified in 3GPP TS 44.160 sub-clause 5.5.3. When the PSI3\_CHANGE\_MARK parameter is changed in a PSI3quater message, the MS shall re-read all instances and rebuild the 3G Neighbour Cell list. This 3G neighbour cell list shall then be used for measurement reporting when the MS enters RRC-Cell\_Dedicated state, until the MS has received a given number of instances of MEASUREMENT INFORMATION messages that contain 3G Neighbour Cell Description. This number of instances is defined by the 3G-WAIT parameter. + +In RRC-Cell\_Dedicated state, the MS obtains the 3G Neighbour Cell Description information on SRB1 by one or more instances of the MEASUREMENT INFORMATION message with the same 3G\_BA\_IND value as defined in this sub-clause. When the 3G\_BA\_IND parameter in the MEASUREMENT INFORMATION message is changed, the MS shall also re-read all instances of MEASUREMENT INFORMATION messages, rebuild the 3G Neighbour Cell list, and use the new list for measurement reporting based on the parameter 3G-WAIT. + +The 3G Neighbour Cell list may contain up to 96 3G Neighbour Cells. + +Each *3G Neighbour Cell Description* received is added to the 3G Neighbour Cell list, starting with the index equal to the parameter *Index\_Start\_3G*. If this parameter is not present then the value 0 shall be used. + +For each 3G Neighbour Cell Description, the cells are indexed in the following order: + +- 1) UTRAN FDD cells: FDD ARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. Then for each FDD ARFCN, the cells are indexed in the order of increasing values of the decoded *FDD\_CELL\_INFORMATION* parameters. +- 2) UTRAN TDD cells: TDD ARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. Then for each TDD ARFCN, the cells are indexed in the order of increasing values of the decoded *TDD\_CELL\_INFORMATION* parameters. +- 3) CDMA 2000 cells: the cells are indexed in the order of occurrence in the 3G Neighbour Cell description. + +If a *3G Neighbour Cell Description* includes non-supported frequencies or Radio Access Technologies, this shall not be considered as an error; indices in the 3G Neighbour Cell list shall be incremented accordingly. + +If more than one cell with the same index in the 3G Neighbour Cell list are provided by different instances of *3G Neighbour Cell Descriptions*, the cell from the message instance with the highest index shall be used. In case the same 3G Cell occurs more than once in the resulting 3G Neighbour Cell list, each occurrence shall be assigned an index but only the cell with the highest index in the 3G Neighbour Cell list shall be referred to in measurement reports. + +If a cell is provided for an index higher than 95 in the 3G Neighbour Cell list, this shall not be considered as an error; the cell shall not be included in the 3G Neighbour Cell list. + +#### 7.9.2.2.3 Deriving the GSM Neighbour Cell list from the BSICs and the BCCH Allocation + +In RRC-Idle mode, the MS shall derive the GSM Neighbour Cell from information received on PBCH, by one or more instances of the PSI3 or PSI3bis message as specified in 3GPP TS 44.160. In RRC-Cell\_Dedicated state, the GSM Neighbour Cell list shall be derived from information received, on SRB1, by one or more instances of the MEASUREMENT INFORMATION message as defined in this sub-clause. The GSM Neighbour Cell list may contain up to 96 Neighbour Cells. + +To obtain the GSM neighbour cell list, the MS shall combine the BA (list) received in SI5/SI5bis/SI5ter with the BSIC list received in one or more instances of the MEASUREMENT INFORMATION message with the same *BA\_IND* value as the BA (list). The BSICs may be received before the corresponding BA (list). The first BSIC in each instance applies to the frequency in the BA (list) referenced by the parameter *BA\_Index\_Start\_BSIC*. For each successive BSIC, one bit indicates if the BSIC applies to the same frequency as the previous BSIC or to the next frequency in the BA (list), as defined in 3GPP TS 44.018. When the *BA\_IND* is changed the MS shall rebuild the combined list and the BSIC list shall also be rebuilt. + +#### 7.9.2.2.4 Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list + +For report with the ENHANCED MEASUREMENT REPORT message, the Neighbour Cell list is the concatenation of the GSM Neighbour Cell list and the 3G Neighbour Cell list (if any). In this concatenation the value of the parameter *Absolute\_Index\_Start\_EMR* is added to the 3G Neighbour Cell list indices. The Neighbour Cell list may contain up to 96 Neighbour Cells. If the same index occurs for a GSM Cell and a 3G Cell, the GSM Cell shall be used. + +NOTE: For report with the MEASUREMENT REPORT message, the concatenated list is not used. Instead, the two lists are used separately, as defined in 3GPP TS 44.018. + +#### 7.9.2.2.5 Real Time Differences + +To obtain the Real Time Differences, the MS shall combine the BA (list) with the Real Time Differences parameters received in the MEASUREMENT INFORMATION message with the same *BA\_IND* value as the BA (list). The Real Time Difference list may contain up to 96 Real Time Difference parameters. Each frequency in the BA (list) may be associated to 0, 1 or more Real Time Difference parameters. The Real Time Difference parameters may be received before the corresponding BA (list). The parameter *BA\_Index\_Start\_RTD* in each structure indicates the index of the frequency in the BA (list) to be taken as a starting reference. A sub-structure is included for each frequency referenced. Each of those sub-structures indicates if 0, 1 or more RTD parameters are present for this frequency. If a frequency in the BA (list) is not provided with Real Time Difference information by any of the message instances with correct + +BA\_IND, it shall be assumed that no information is available for that frequency, see 3GPP TS 44.018. When the BA\_IND is changed the MS shall re-read the Real Time Differences parameters in all instances. + +The Real Time Difference may be received from the PSI3ter message in the GPRS Real Time Difference Description (see 3GPP TS 44.160). + +#### 7.9.2.2.6 Report Priority Description + +Report Priority information can be received in one instance of the MEASUREMENT INFORMATION message. The Report Priority information is associated with the Neighbour Cell list (see 7.9.2.2.4) having the same BA\_IND value and 3G\_BA\_IND value. Each REP\_PRIORITY bit of this field relates to indices of the Neighbour Cell list, starting with index 0. The Report Priority information may be received before the corresponding Neighbour Cell list. When the BA\_IND or 3G\_BA\_IND are changed the MS shall re-read the REP\_PRIORITY parameters in all instances. + +Indices exceeding the value 95 shall be ignored. If there are fewer indices than the number of Neighbour Cells, the value 0 shall be assumed for the missing bits. + +Report Priority Description for GSM cells may also be received from the PSI3ter message and Report Priority Description for 3G cells from the PSI3quarter message (see 3GPP TS 44.160). + +#### 7.9.2.2.7 The 3G Cell Reselection list + +This applies only to a multi-RAT MS. The 3G Cell Reselection list is defined in 3GPP TS 44.160. + +#### 7.9.2.2.8 CCN Support description + +The CCN Support description may be received from the PSI3 message or any instance of the PSI3bis or PSI3quater messages (see 3GPP TS 44.160). + +### 7.9.3 Extended measurement report + +Only applicable to mobile stations which support extended measurement. + +When in RRC-Cell\_Dedicated state, a mobile station may receive an EXTENDED MEASUREMENT ORDER message from the network. As defined in 3GPP TS 45.008, the mobile station shall then perform measurements on the frequencies specified by this EXTENDED MEASUREMENT ORDER message for one reporting period. The mobile station shall thereafter send an EXTENDED MEASUREMENT REPORT message. This message contains the measurement results as defined in 3GPP TS 45.008. + +If the mobile station has not started to send its EXTENDED MEASUREMENT REPORT message within 10 seconds after the reception of the EXTENDED MEASUREMENT ORDER message, no EXTENDED MEASUREMENT REPORT message shall be sent. The mobile station shall after a successful channel change abort any pending measurements or reporting related to an EXTENDED MEASUREMENT ORDER message received on the old channel. + +If a mobile station receives an EXTENDED MEASUREMENT ORDER message indicating the same value of the sequence code as an EXTENDED MEASUREMENT ORDER message received earlier on the same channel without having received any EXTENDED MEASUREMENT ORDER message indicating a different value of the sequence code in between, that EXTENDED MEASUREMENT ORDER message shall be ignored. If the mobile station, before the reporting related to an EXTENDED MEASUREMENT ORDER message has started, receives a new EXTENDED MEASUREMENT ORDER message with a different value of the sequence code, any pending measurements or reporting related to the earlier EXTENDED MEASUREMENT ORDER message shall be aborted and the new message treated. + +The EXTENDED MEASUREMENT ORDER message and the EXTENDED MEASUREMENT REPORT message are sent on SRB1. + +## 7.10 Handover to UTRAN procedure + +### 7.10.1 General + +This procedure is only valid for UTRAN capable MSs. A change to UTRAN channel(s) can be requested by the network RRC sublayer in RRC-Cell\_Dedicated state. + +The handover to UTRAN procedure includes: + +- 1> the reconfiguration of the layer 2 established for the DBPSCHs; +- 1> the disconnection and the deactivation of physical channels and their release (layer 1). +- 1> the establishment of UTRAN channel(s), see 3GPP TS 25.331. + +## 7.10.2 Initiation + +The network initiates the handover to UTRAN procedure by sending an INTER SYSTEM TO UTRAN HANDOVER COMMAND message to the mobile station on the SRB2 in GERAN in *Iu mode*. The INTER SYSTEM TO UTRAN HANDOVER COMMAND message shall contain encapsulated the RADIO BEARER RECONFIGURATION message. If the INTER SYSTEM TO UTRAN HANDOVER COMMAND refers to a not known cell (see 3GPP TS 25.133 and 3GPP TS 25.123), this shall not be considered as an error. + +## 7.10.3 Reception of INTER SYSTEM TO UTRAN HANDOVER COMMAND message by the MS + +Upon the receipt of INTER SYSTEM TO UTRAN HANDOVER COMMAND message, the mobile station shall: + +- 1> initiate reconfiguration of the layer 2 and disconnection of the DBPSCHs; +- 1> switch to the assigned cell(s) and establish the physical channels as described in 3GPP TS 25.331. +- 1> establish the connection to the UTRA cell, by using the contents of encapsulated RADIO BEARER RECONFIGURATION message. + +## 7.10.4 Successful completion of the inter-RAT handover + +When inter-RAT handover to UTRAN is performed, the MS shall: + +- 1> perform the actions on reception of RADIO BEARER RECONFIGURATION message as specified in 3GPP TS 25.331; +- 1> keep the ciphering and integrity keys that are stored in the USIM/SIM for that CN domain. +- 1> if inter-RAT handover to UTRAN is performed and if there are any NAS messages for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer SRB3 or signalling radio bearer SRB4 has not yet been confirmed by RLC: + - 2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology. +- 1> clear or set variables upon leaving GERAN RRC connected mode as specified in sub-clause 10.4. + +After lower layer connections are successfully established, the mobile station returns a RADIO BEARER RECONFIGURATION COMPLETE message on UTRAN channels(s), see 3GPP TS 25.331. + +When receiving the RADIO BEARER RECONFIGURATION COMPLETE message (see 3GPP TS 25.331), the network shall release the old channels (see 3GPP TS 25.413). + +## 7.10.5 Unsuccessful inter-rat handover at the MS side + +If the MS does not succeed in establishing the connection to the UTRA cell, it shall: + +- 1> revert back to the old configuration; +- 1> establish the GERAN physical channel(s) used at the time of reception of the INTERSYSTEM HANDOVER TO UTRAN COMMAND message; +- 1> if the lower layer failure happens while attempting to connect back to the old channels; + - 2> the PROTOCOL\_ERROR\_REJECT variable is set TRUE; +- 1> if the MS does not succeed to establish the GERAN physical channel(s): + +- 2> perform a Cell Update procedure according to sub-clause 7.8 with cause "radio link failure"; +- 2> when the Cell Update procedure has been completed successfully: + - 3> proceed as below. +- 1> transmit the HANDOVER FAILURE message setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 2> set it to the value of "RRC transaction identifier" in the entry for the INTER SYSTEM HANDOVER TO UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "*Failure Cause*" to "physical channel failure". +- 2> when the HANDOVER FAILURE message has been submitted to lower layer for transmission the procedure ends. + +If the INTER SYSTEM TO UTRAN HANDOVER COMMAND instructs the mobile to use a predefined configuration not implemented or if the INTER SYSTEM TO UTRAN HANDOVER COMMAND instructs the mobile to use a default configuration not supported by the MS, the MS shall: + +- 1> set the variable PROTOCOL\_ERROR\_REJECT to TRUE; and +- 1> if allowed by the source RAT: + - 2> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION; +- 1> then stay on the current channel(s) and return a HANDOVER FAILURE message on SRB2 with cause "UTRAN configuration unknown"; +- 1> clear all the UTRAN predefined configurations. + +When sending a HANDOVER FAILURE message in response to an INTERSYSTEM TO UTRAN HANDOVER COMMAND message, the mobile station shall erase all the UTRAN predefined configurations. + +If the INTER SYSTEM TO UTRAN HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall: + +- 1> stay on the current channel(s) and return a HANDOVER FAILURE message on SRB2 with cause "frequency not implemented". + +## 7.10.6 Reception of an HANDOVER FAILURE message by GERAN in Iu mode + +When HANDOVER FAILURE has been received, the network shall + +- 1> release the UTRAN channel(s), if they were dedicated channels; +- 1> if a HANDOVER FAILURE message is received on the old channels on SRB2; or +- 1> if the GERAN has received CELL UPDATE message with the cause "Radio link failure" then: + - 2> the old channels shall be released if they were DBPSCHs and all contexts related to the connections with that mobile station are cleared. + +## 7.11 Handover to CDMA2000 procedure + +### 7.11.1 General + +This procedure is only valid for CDMA2000 capable MSs. A change to CDMA2000 channel(s) can be requested by the network RRC sublayer in RRC-Cell\_Dedicated state. + +The handover to CDMA2000 procedure includes: + +- the disconnection and the deactivation of physical channels and their release (layer 1). +- the establishment of CDMA2000 channel(s), see TIA/EIA/IS-833 and TIA/EIA/IS-2000-5. + +### 7.11.2 Initiation + +The network initiates the handover to CDMA2000 procedure by sending an INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message to the mobile station on the SRB2 in GERAN in *Iu mode*. The INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message shall contain encapsulated the HANDOVER TO CDMA2000 COMMAND. If the INTER SYSTEM TO CDMA2000 HANDOVER COMMAND refers to a not known base station (see TIA/EIA/IS-98), this shall not be considered as an error. + +### 7.11.3 Reception of INTERSYSTEM TO CDMA2000 HANDOVER COMMAND message by the MS + +Upon the receipt of INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message, the mobile station shall: + +- 1> switch to the assigned cell(s) and establish the physical channels as described in TIA/EIA/IS-833 and TIA/EIA/IS-2000-5. +- 1> establish the connection to the CDMA cell, by using the contents of encapsulated message HANDOVER TO CDMA2000 COMMAND. +- 1> in case one or more IEs "*RAB Info*" is included in the INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message: + - 2> connect upper layer entities corresponding to indicated RABs to the radio resources indicated in the inter-RAT message. + - 2> and act upon received information element as specified in sub-clauses 7.18 and 7.19. + +### 7.11.4 Successful completion of the inter-RAT handover + +- NOTE: After lower layer connections are successfully established, the mobile station returns a Handoff Completion message on CDMA2000 channels(s), see TIA/EIA/IS-833. + +When receiving the Handoff Completion message (see TIA/EIA/IS-833 and 3GPP TS 25.413), the network shall release the old channels. + +### 7.11.5 Unsuccessful inter-rat handover at the MS side + +If the MS does not succeed in establishing the connection to the CDMA2000 cell (see TIA/EIA/IS-2000-5), it shall: + +- 1> revert back to the old configuration; +- 1> establish the GERAN physical channel(s) used at the time of reception of the INTER SYSTEM HANDOVER TO CDMA2000 COMMAND; +- 1> if the lower layer failure happens while attempting to connect back to the old channels; + - 2> the *PROTOCOL\_ERROR\_REJECT* variable is set TRUE; +- 1> if the MS does not succeed to establish the GERAN physical channel(s): + - 2> perform a Cell Update procedure according to sub-clause 7.8 with cause "radio link failure"; + - 2> when the Cell Update procedure has been completed successfully: + - 3> proceed as below. +- 1> transmit the HANDOVER FAILURE message setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + +- 2> set it to the value of "RRC transaction identifier" in the entry for the INTER SYSTEM HANDOVER TO CDMA2000 COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "*Failure Cause*" to "physical channel failure". +- 1> when the HANDOVER FAILURE message has been submitted to lower layer for transmission the procedure ends. + +If the INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall: + +- 1> stay on the current channel(s) and return a HANDOVER FAILURE message on SRB2 with cause "frequency not implemented". + +## 7.11.6 Reception of an HANDOVER FAILURE message by GERAN in Iu mode + +When HANDOVER FAILURE has been received, the network shall + +- 1> release the CDMA2000 channel(s); +- 1> if a HANDOVER FAILURE message is received on the old channels on SRB2; or +- 1> the mobile station has received CELL UPDATE with the cause "radio link failure" then: + - 2> the old channels shall be released and all contexts related to the connections with that mobile station are cleared. + +## 7.12 Mapping of user data substreams onto timeslots in a multislot configuration + +For multislot configurations the following rules for mapping of the user data substreams onto timeslots shall apply for each channel set: + +- 1> at initial assignment, the lowest numbered user data substream shall be mapped to the lowest numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n is the number of substreams) +- 1> at channel changes using handover procedure or radio bearer procedures, the lowest numbered user data substream shall be mapped to the lowest numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n is the number of substreams) +- 1> at channel changes using radio bearer procedures: + - 2> user data substream(s) mapped to timeslot(s) that are present in both the old and the new configuration shall continue to be mapped to the same timeslot(s) as before the channel change; and + - 2> possibly added timeslot(s) shall carry the lowest numbered available user data substream so that the lowest numbered data substream among the added is mapped to the lowest numbered added timeslot and so on in ascending order. + +NOTE: The user data substream number is a number that need not be the same as the inband number used for transparent services. The user data substream number is only used as a point of reference to a specific user data substream. + +## 7.13 Application Procedures + +### 7.13.1 LCS transfer + +![Sequence diagram showing LCS transfer between MS and GERAN. The GERAN sends an LCS DOWNLINK INFORMATION [RRLP PDU] to the MS, and the MS responds with an LCS UPLINK INFORMATION [RRLP PDU].](070352b751dd0711b8ac6ddfa6df1d98_img.jpg) + +``` + +sequenceDiagram + participant GERAN + participant MS + Note left of GERAN: LCS DOWNLINK INFORMATION [RRLP PDU] + GERAN->>MS: LCS DOWNLINK INFORMATION [RRLP PDU] + Note right of MS: LCS UPLINK INFORMATION [RRLP PDU] + MS->>GERAN: LCS UPLINK INFORMATION [RRLP PDU] + +``` + +Sequence diagram showing LCS transfer between MS and GERAN. The GERAN sends an LCS DOWNLINK INFORMATION [RRLP PDU] to the MS, and the MS responds with an LCS UPLINK INFORMATION [RRLP PDU]. + +Figure 7.13.1.1: LCS transfer + +#### 7.13.1.1 General + +The LCS Transfer procedure enables the SMLC on the network side and the MS to exchange RRLP Protocol Data Units (PDUs). Only the GERAN may initiate the exchange of RRLP PDU's (initiated by the SMLC). The MS only sends RRLP PDU's in the uplink direction in response to RRLP PDU's sent by the GERAN (SMLC). + +The maximum size of the RRLP PDU in the LCS DOWNLINK INFORMATION and LCS UPLINK INFORMATION messages is 242 octets. Since RRLP pseudo segmentation limits the length of RRLP PDUs, segmentation is not defined for the LCS Transfer procedure. + +#### 7.13.1.2 Initiation of LCS transfer procedure in the GERAN + +In the GERAN, the LCS transfer procedure is initiated when the the SMLC requests the transfer of an RRLP PDU after the initial signaling connection is established. The GERAN may also initiate the LCS transfer procedure when another RRC procedure is ongoing, and in that case the state of the latter procedure shall not be affected. The RRLP PDU in the LCS DOWNLINK INFORMATION message shall contain a complete RRLP PDU according to the RRLP protocol 3GPP TS 44.031. The GERAN shall transmit the LCS DOWNLINK INFORMATION message on the downlink using AM RLC on signalling radio bearer SRB3. + +The SMLC may be a "stand alone SMLC" (and therefore not tightly integrated to the GERAN). This can lead to message loss or truncation during the Handover procedure (during change of BPSCH). + +#### 7.13.1.3 Reception of LCS DOWNLINK INFORMATION message by the MS + +When the MS has received an LCS DOWNLINK INFORMATION message, the MS shall deliver the RRLP PDU to the LCS local application. + +The MS shall detect RRLP PDU truncation if an LCS DOWNLINK INFORMATION message is received carrying an RRLP PDU that is shorter than the indicated length. If a truncated RRLP PDU is received, RRLP PDU shall be discarded. + +#### 7.13.1.4 Transmission of a response message by the MS + +When the LCS local application has received and processed an RRLP PDU from the LCS DOWNLINK INFORMATION message, one or two RRLP PDU's shall be returned to the GERAN. The MS shall + +- 1> encapsulate the RRLP PDU received from the LCS local application in the LCS UPLINK INFORMATION message; +- 1> transmit the LCS UPLINK INFORMATION message on the uplink using AM RLC on signalling radio bearer SRB3; +- 1> if a second RRLP PDU is received from the LCS local application, repeat the previous two steps; + +Suspend/Resume functions of lower layers will prevent message loss on the uplink. If the BPSCH is changed before the RLC ACK is received in the MS, message duplication is possible in the uplink after change of the physical channel. + +### 7.13.1.5 Reception of a response message by the GERAN + +When the GERAN has received an LCS UPLINK INFORMATION message, the GERAN shall deliver the RRLP PDU to the SMLC. + +The GERAN shall detect RRLP PDU truncation if an LCS UPLINK INFORMATION message is received carrying an RRLP PDU that is shorter than the indicated length. If a truncated RRLP PDU is received, the RRLP PDU shall be discarded. + +### 7.13.1.6 Invalid LCS DOWNLINK INFORMATION message + +If the MS receives a LCS DOWNLINK INFORMATION message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows. The MS shall: + +- 1> transmit an RRC STATUS message on the SRB2; +- 1> include the IE "*Identification of Received Message*"; +- 1> set the IE "*Received Message Type*" to LCS DOWNLINK INFORMATION message; +- 1> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the LCS DOWNLINK INFORMATION message in the table "Rejected transactions" in the variable TRANSACTIONS; +- 1> clear that entry; +- 1> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION; +- 1> when the RRC STATUS message has been submitted to lower layers for transmission; + - 2> continue with any ongoing processes and procedures as if the invalid LCS DOWNLINK INFORMATION message has not been received. + +## 7.14 Radio Bearer control procedures + +### 7.14.1 Reconfiguration procedures + +![Sequence diagram showing Radio Bearer Establishment between MS and GERAN.](bbd36eba6bb7c4ba87608874c8c714ff_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + Note left of MS: + GERAN->>MS: RADIO BEARER SETUP + Note right of GERAN: + MS->>GERAN: RADIO BEARER SETUP COMPLETE +``` + +The diagram illustrates the interaction between a Mobile Station (MS) and a GERAN for radio bearer establishment. It consists of two vertical lifelines. The first message is a 'RADIO BEARER SETUP' message sent from the GERAN to the MS, indicated by a horizontal arrow pointing left. The second message is a 'RADIO BEARER SETUP COMPLETE' message sent from the MS to the GERAN, indicated by a horizontal arrow pointing right. + +Sequence diagram showing Radio Bearer Establishment between MS and GERAN. + +Figure 7.14.1.1: Radio Bearer Establishment, normal case + +![Sequence diagram for Radio Bearer Establishment showing a failure case where the MS reverts to old configuration.](38d82ffe820e339811b396206f40a201_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + GERAN->>MS: RADIO BEARER SETUP + MS->>GERAN: RADIO BEARER SETUP FAILURE + +``` + +This sequence diagram illustrates the interaction between a Mobile Station (MS) and a GERAN. The process begins with the GERAN sending a 'RADIO BEARER SETUP' message to the MS. In response, the MS sends a 'RADIO BEARER SETUP FAILURE' message back to the GERAN. + +Sequence diagram for Radio Bearer Establishment showing a failure case where the MS reverts to old configuration. + +**Figure 7.14.1.2: Radio Bearer Establishment, MS reverts to old configuration** + +![Sequence diagram for Radio Bearer Reconfiguration showing a normal flow.](333992a0b3b7a9d826f72f7bf199221b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + GERAN->>MS: RADIO BEARER RECONFIGURATION + MS->>GERAN: RADIO BEARER RECONFIGURATION COMPLETE + +``` + +This sequence diagram shows the normal flow for radio bearer reconfiguration. The GERAN sends a 'RADIO BEARER RECONFIGURATION' message to the MS, and the MS responds with a 'RADIO BEARER RECONFIGURATION COMPLETE' message. + +Sequence diagram for Radio Bearer Reconfiguration showing a normal flow. + +**Figure 7.14.1.3: Radio Bearer Reconfiguration, normal flow** + +![Sequence diagram for Radio Bearer Reconfiguration showing a failure case.](869c547c11ac7e123c51aba22289f2cd_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + GERAN->>MS: RADIO BEARER RECONFIGURATION + MS->>GERAN: RADIO BEARER RECONFIGURATION FAILURE + +``` + +This sequence diagram depicts a failure case for radio bearer reconfiguration. The GERAN sends a 'RADIO BEARER RECONFIGURATION' message to the MS, but the MS replies with a 'RADIO BEARER RECONFIGURATION FAILURE' message. + +Sequence diagram for Radio Bearer Reconfiguration showing a failure case. + +**Figure 7.14.1.4: Radio Bearer Reconfiguration, failure case** + +![Sequence diagram for Radio Bearer Release showing a normal case.](6116b1a533010c170fc526ec513ba0b8_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + GERAN->>MS: RADIO BEARER RELEASE + MS->>GERAN: RADIO BEARER RELEASE COMPLETE + +``` + +This sequence diagram shows the normal case for radio bearer release. The GERAN sends a 'RADIO BEARER RELEASE' message to the MS, and the MS responds with a 'RADIO BEARER RELEASE COMPLETE' message. + +Sequence diagram for Radio Bearer Release showing a normal case. + +**Figure 7.14.1.5: Radio Bearer Release, normal case** + +![Sequence diagram showing Radio Bearer Release and Failure between MS and GERAN.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + Note right of GERAN: RADIO BEARER RELEASE + GERAN->>MS: RADIO BEARER RELEASE + Note left of MS: RADIO BEARER RELEASE FAILURE + MS->>GERAN: RADIO BEARER RELEASE FAILURE + +``` + +The diagram illustrates a sequence of messages between a Mobile Station (MS) and a GERAN. The MS sends a 'RADIO BEARER RELEASE' message to the GERAN. The GERAN responds with a 'RADIO BEARER RELEASE FAILURE' message back to the MS. + +Sequence diagram showing Radio Bearer Release and Failure between MS and GERAN. + +**Figure 7.14.1.6: Radio Bearer Release, MS reverts to old configuration** + +### 7.14.1.1 General + +The reconfiguration procedures include the following procedures: + +- the Radio Bearer Establishment procedure; +- the Radio Bearer Reconfiguration procedure; +- the Radio Bearer Release procedure; + +The Radio Bearer Establishment procedure is used to establish new radio bearer(s). + +The Radio Bearer Reconfiguration procedure is used to reconfigure parameters for a radio bearer. + +The Radio Bearer Release procedure is used to release radio bearer(s). + +The Radio Bearer Reconfiguration procedure is used to reconfigure transport channel(s). + +### 7.14.1.2 Initiation + +To initiate any one of the reconfiguration procedures, the GERAN shall: + +- 1> configure new radio links in any new physical channel; +- 1> start transmission and reception on the new radio links; +- 1> for a Radio Bearer Establishment procedure: + - 2> transmit a RADIO BEARER SETUP message on the SRB2; + - 2> if signaling radio bearer SRB4 is setup with this procedure and signaling radio bearers SRB1-SRB3 were already established prior to the procedure: + - 3> if the variable "LATEST\_CONFIGURED\_CN\_DOMAIN" has been initialised: + - 4> any radio bearers setup by the same message as signalling radio bearer SRB4 shall be connected to the CN domain indicated in the variable "LATEST\_CONFIGURED\_CN\_DOMAIN"; +- 1> for a Radio Bearer Reconfiguration procedure: + - 2> transmit a RADIO BEARER RECONFIGURATION message on the SRB2; +- 1> for a Radio Bearer Release procedure: + - 2> transmit a RADIO BEARER RELEASE message on the SRB2; +- 1> for a transport channel reconfiguration (setup, reconfigure or release) procedure: + - 2> transmit a RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message on the SRB2. +- 1> if transport channels are setup, reconfigured or released in uplink and/or downlink: + +- 2> set TFCS according to the new transport channel(s). +- 1> if transport channels are added or deleted in uplink and/or downlink, and the IE "*RB Mapping Info*" applicable to the new configuration has not been previously provided to the MS, the GERAN shall: + - 2> send the IE "*RB Mapping Info*" for the new configuration. + +The RADIO BEARER RECONFIGURATION message shall include in case of SBSS relocation procedure the structure "*Downlink Counter Synchronisation Info*" and + +- 1> if ciphering and/or integrity protection are activated: + - 2> include new ciphering and/or integrity protection configuration information to be used after reconfiguration. + +If one of the reconfiguration messages is transmitted then the IE "*New G-RNTT*" may be present. + +NOTE 1: The RADIO BEARER RECONFIGURATION message always includes the IE "*RB Information to Reconfigure*", even if GERAN does not require the reconfiguration of any RB. In these cases, GERAN may include only the IE "*RB Identity*" within the IE "*RB Information to Reconfigure*". + +GERAN shall take the MS capabilities into account when setting the new configuration. If the message is used to initiate a transition from RRC-Cell\_Dedicated state to RRC-Cell\_Shared state, the RRC may allocate the new physical resources. + +### 7.14.1.3 Reception of RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message by the MS + +If the MS receives the one of the following reconfiguration messages: + +- RADIO BEARER SETUP; or +- RADIO BEARER RECONFIGURATION; or +- RADIO BEARER RELEASE; + +it shall: + +- 1> set the variable ORDERED\_RECONFIGURATION to TRUE; +- 1> act upon all received information elements as specified in sub-clause 7.18 and 7.19, unless specified in the following and perform the actions below. +- 1> if a complete reconfiguration, setup or release is indicated in the reconfiguration messages: + - 2> initiate the radio bearer, transport channel and physical channel reconfiguration in accordance with the received radio bearer, transport channel and physical channel information elements as is specified in sub-clauses 7.18 and 7.19. + +The MS may first release the physical channel used at reception of the reconfiguration message (i.e a RADIO BEARER SETUP message, a RADIO BEARER RECONFIGURATION message or a RADIO BEARER RELEASE message). The MS shall: + +- 1> then stop the RLC operation for the duration of the reconfiguration procedure; +- 1> establish a new physical channel and act upon all received information elements as specified in sub-clause 7.19; +- 1> enter a state according to sub-clause 7.19; +- 1> continue the RLC operation, if applicable. + +NOTE: The RADIO BEARER RECONFIGURATION message always includes the IE "*RB Information to Reconfigure*". GERAN has to include it even if it does not require the reconfiguration of any RB. + +If the MS is in RRC-Cell\_Dedicated state upon reception of the reconfiguration message and remains in RRC-Cell\_Dedicated state after that, the MS shall: + +- 1> stop the RLC operation for the duration of the reconfiguration procedure; + +- 1> then establish a new physical channel and act upon all received information elements as specified in sub-clause 7.19.6 and: +- 2> if the IE "*DBPSCH Description*" is present then set the network response times as specified in sub-clause 7.18.12;1> if the reconfiguration messages contain the transport channel information elements: + - 2> then establish, reconfigure or release a new transport channel and act upon all received information elements as specified in sub-clause 7.19.7; +- 1> if RADIO BEARER RECONFIGURATION message has been received; and if the IE "*DBPSCH Description*" is present and: + - 2> if the following IEs are present IE "*Handover Reference*", IE "*Power Command and Access Type*", IE "*Cell Description*" and IE "*Description of the First Channel After Time*", the MS shall: + - 3> if the IE "*Synchronization Indication*" is not present, establish new physical channel using non-synchronized method as specified in sub-clause 7.18.6 and act upon all received information elements and 7.19. + - 3> if the IE "*Synchronization Indication*" is present, establish new physical channel using one of the synchronized methods as specified below: + - 4> if IE "*Timing Advance*" is present and if the IE "*Synchronization Indication*" indicates pre-synchronized type of physical channel establishment, the MS shall: + - hh) 5> establish new physical channel using the pre-synchronized method as specified in sub-clause 7.18.6 and act upon all received information elements and 7.19. + - 4> if IE "*Real Time Difference*" is present and if the IE "*Synchronization Indication*" indicates pseudo-synchronized type of physical channel establishment, the MS shall: + - ii) 5> establish new physical channel using the pseudo-synchronized method as specified in sub-clause 7.18.6 and act upon all received information elements and 7.19; + - 4> if the IE "*Synchronization Indication*" is present and if it indicates finely synchronized type of physical channel establishment, the MS shall: + - jj) 5> establish new physical channel using the finely synchronized method as specified in sub-clause 7.18.6 and act upon all received information elements and 7.19; + - 2> if the following IEs, IE "*Handover Reference*", IE "*Power Command and Access Type*", IE "*Cell Description*" are not present, the MS shall: + - 3> not use the procedures specified in sub-clause 7.18.6; + - 2> if at least one of the following IEs, IE "*Handover Reference*", IE "*Power Command and Access Type*" and IE "*Cell Description*" and IE "*Description of the First Channel After Time*" is not present, the MS shall: + - 3> act as specified in sub-clause 7.14.1.14. +- 1> if RADIO BEARER RELEASE message has been received and is indicating the release of one or more channels, then: + - 2> deactivate the physical channel to be released; and + - 2> if at least one of the following Transport channel information elements (IE "*Deleted DL TrCH Information*", IE "*Deleted UL TrCH Information*") is present in the message then: + - 3> release the transport channels and act upon all received information elements as specified in sub-clause 7.19.7. + +If the RADIO BEARER RECONFIGURATION message refers to a cell to which the mobile station is not synchronised to (see 3GPP TS 45.008), this shall not be considered as an error. + +NOTE: The network takes into account limitations of certain mobile stations to understand formats used in the IE "Frequency List", IE "Frequency Short List", and IE "Cell Channel Description" used in the RADIO BEARER RECONFIGURATION message, see sub-clause 7.19. + +If the MS is in RRC-Cell\_Dedicated state when receives the one of the reconfiguration messages (i.e RADIO BEARER SETUP message, a RADIO BEARER RECONFIGURATION message or RADIO BEARER RELEASE message) and enters in RRC-Cell\_Shared state after state transition, the MS shall: + +- 1> release the dedicated basic physical resources; +- 1> act upon all received information elements as specified in sub-clause 7.19; +- 1> if RADIO BEARER RELEASE message has been received and is indicating the release of one or more channels, then: + - 2> deactivate the physical channel to be released; and + - 2> if at least one of the following Transport channel information elements (IE "Deleted DL TrCH Information", IE "Deleted UL TrCH Information") is present in the message then: + - 3> release the transport channels and act upon all received information elements as specified in sub-clause 7.19.7. + +If after state transition the MS enters RRC-Cell\_Shared state, the MS shall: + +- 1> if timer T305 is not running and if periodical update in the IE "MS Timers and Constants In Connected Mode" has been set to any other value than "infinity" in PACKET SYSTEM INFORMATION TYPE16 message; + - 2> start timer T305 using its initial value; +- 1> if the IE "GERAN DRX Cycle Length Coefficient" is included in the received message: + - 2> store this IE and apply this coefficient as specified in 3GPP TS 44.160. + +If the MS is in RRC-Cell\_Shared state when receives the one of the reconfiguration messages (i.e RADIO BEARER SETUP message or RADIO BEARER RECONFIGURATION message or RADIO BEARER RELEASE message) and enters in RRC-Cell\_Dedicated state after state transition, the MS shall: + +- 1> establish the dedicated basic physical resources as specified in 7.19.6.1 and set the network response times as specified in sub-clause 7.18.12; +- 1> act upon all received information elements as specified in sub-clause 7.19.6.1; +- 1> if RADIO BEARER RELEASE message has been received and is indicating the release of one or more channels, then: + - 2> deactivate the physical channel to be released. + +If the MS is in RRC-Cell\_Shared state upon reception of the reconfiguration message and remains in RRC-Cell\_Shared state after that, the MS shall: + +- 1> if IE "SBPSCH Description" is included then: + - 2> establish new physical channels for each RB identity included in the IE "RB Information to Reconfigure" and act upon all received information elements as specified in sub-clause 7.19. + +If after state transition the MS enters RRC-GRA\_PCH state, the MS shall: + +- 1> if timer T305 is not running and if periodical update in the IE "MS Timers And Constants In Connected Mode" has been set to any other value than "infinity" in PACKET SYSTEM INFORMATION TYPE 16 message; + - 2> start timer T305 using its initial value; +- 1> if the IE "GERAN DRX Cycle Length Coefficient" is included in the message: + - 2> use the value in the IE "GERAN DRX Cycle Length Coefficient" for calculating Paging occasion as specified in sub-clauses 7.18 and 7.19; + +- 1) if the IE "*GERAN DRX Cycle Length Coefficient*" is not included in the same message: + - 2) set the variable INVALID\_CONFIGURATION to TRUE. + +The MS shall transmit a response message as specified in 7.14.1.4, setting the information elements as specified below. +The MS shall: + +- 1) if the received reconfiguration message includes the structure "Downlink Counter Synchronisation Info"; or +- 1) if the received reconfiguration message includes the IE "*New G-RNTI*": + - 2) if the variable PDCP\_SN\_INFO is empty: + - 3) configure the corresponding RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except SRB2 to "stop"; + - 2) else: + - 3) configure the RLC entity for signalling radio bearers SRB1, SRB3 and SRB4 to "stop"; + - 3) configure the RLC entity for UM and AM radio bearers for which the IE "*PDCP SN Info*" is not included to "stop"; + - 2) re-establish SRB2; + - 2) for the downlink and the uplink, apply the ciphering configuration as follows: + - 3) if the received re-configuration message included the IE "*Ciphering Mode Info*": + - 4) use the ciphering configuration in the received message when transmitting the response message; + - 3) if the ciphering configuration for SRB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the activation times not having been reached: + - 4) if the previous SECURITY MODE COMMAND was received due to new keys being received: + - kk) 5) consider the new ciphering configuration to include the received new keys; + - ll) 5) initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 as indicated in subclause 7.16.1.2.3.1. + - 4) if the ciphering configuration for SRB2 from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the previous SECURITY MODE COMMAND caused a change in LATEST\_CONFIGURED\_CN\_DOMAIN: + - mm) 5) initialise the HFN component of the uplink COUNT-C and downlink COUNT-C of SRB2 to the most recently transmitted IE "*START List*" or IE "*START*" for the LATEST\_CONFIGURED\_CN\_DOMAIN at the reception of the previous SECURITY MODE COMMAND message. + - nn) 5) consider the new ciphering configuration to include the keys associated with the LATEST\_CONFIGURED\_CN\_DOMAIN; + - 4) apply the new ciphering configuration immediately following RLC re-establishment. + - 3) else: + - 4) continue using the current ciphering configuration; +- 2) set the new uplink and downlink HFN component of COUNT-C of SRB2 to MAX(uplink HFN component of COUNT-C of SRB2, downlink HFN component of COUNT-C of SRB2); +- 2) increment by one the downlink and uplink values of the HFN component of COUNT -C for SRB2; +- 2) calculate the START value according to sub-clause 7.18.4; + +- 2> include the calculated START values for each CN domain in the IE "*START List*" in the structure "*Uplink Counter Synchronisation Info*"; +- 1> if the handover is performed from UTRAN and RADIO BEARER RECONFIGURATION message is received: + - 2> set the 20 most significant bits of the uplink and downlink HFN component of COUNT-C of SRB2 to MAX (uplink HFNU, downlink HFNU) where HFNU is the HFN component of COUNT-C of SRB2 in UTRAN; + - 2> set the remaining bits of the uplink and downlink HFN component of COUNT-C of SRB2 equal to zero; + - 2> increment by one the downlink and uplink values of the HFN component of COUNT-C for SRB2; + - 2> calculate the START value according to sub-clause 7.18; + - 2> include the calculated START values for each CN domain in the IE "*START list*" in the RADIO BEARER RECONFIGURATION COMPLETE message; + - 2> set the variable LATEST\_CONFIGURED\_CN\_DOMAIN equal to the corresponding UTRAN variable; + - 2> set the variable MS\_CAPABILITY\_TRANSFERRED equal to the corresponding UTRAN variable ; + - 2> set the variable ESTABLISHED\_RABS equal to the corresponding UTRAN variable ; + - 2> set the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS equal to the corresponding UTRAN variable ; + - 2> set the variable CIPHERING\_STATUS equal to the corresponding UTRAN variable ; + - 2> set the variable START\_THRESHOLD equal to the corresponding UTRAN variable ; + - 2> set the variable START\_VALUE\_TO\_TRANSMIT equal to the corresponding UTRAN variable ; + - 2> set IE "*Status*" for the ciphering status in the the variable SECURITY\_MODIFICATION equal to the corresponding UTRAN variable; + - 2> set IE "*Status*" for the integrity protection in the the variable INTEGRITY\_PROTECTION\_INFO equal to the corresponding UTRAN variable; +- 1> if inter-mode handover is performed from A/Gb *mode* and RADIO BEARER RECONFIGURATION message is received: + - 2> store G-RNTI value (32 bits), which is derived by the IEs "*SRNC identity*" (12 bits) and "S-RNTI" (20 bits) shall be derived by padding the IE "S-RNTI " with 10 zero bits in the most significant positions; and + - 2> initialise the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS with the signalling connections that remains after the handover according to the specifications of the source; + - 2> initialise the variable MS\_CAPABILITIES\_TRANSFERRED with the MS capabilities that have been transferred to the network up to the point prior to the handover, if any; + - 2> initialise the variable TIMERS\_AND\_CONSTANTS to the default values and start to use values; + - 2> set the IE "*START*" for each CN domain, in the IE "*START list*" in the RADIO BEARER RECONFIGURATION COMPLETE message equal to the START value for each CN domain stored in the USIM if the USIM is present, or as stored in the MS for each CN domain if the SIM is present; and then; + - 2> set the value of "THRESHOLD" in the variable START\_THRESHOLD to the 20 MSBs of the value stored in the USIM (see 3GPP TS 31.102) for the maximum value of START for each CN Domain, or to the default value in 3GPP TS 33.102 if the SIM is present. + +Keys received while in A/Gb *mode* shall not be regarded as "new" (i.e not trigger the actions in 7.16.1.2.3.1) in a subsequent security control procedure in GERAN (*Iu mode*), irrespective of whether the keys are already being used in A/Gb *mode* or not. If the MS has received new keys in A/Gb *mode* before handover, then the START values in the USIM (sent in the RADIO BEARER RECONFIGURATION COMPLETE message to BSS) will not reflect the receipt of these new keys. At a subsequent Security Mode Control procedure in + +GERAN *Iu mode*, the MS shall activate ciphering and/or integrity protection using the key set stored in USIM/SIM. + +2> if ciphering has been activated and ongoing in *A/Gb mode* when the handover is performed: + +3> for the CN domain included in the IE "*CN Domain Identity*" which is included in the IE "*RAB Information to Reconfigure*", or the CS domain when these IEs are not present: + +4> set the variable LATEST\_CONFIGURED\_CN\_DOMAIN to the value indicated in the IE "*CN Domain Identity*", or to the CS domain when this IE is not present; + +4> set the 20 MSB of the HFN component of the COUNT-C variable for all radio bearers using RLC-TM and all signalling radio bearers to the "START" value included in the IE "*GERAN A/Gb Security Info*"; + +4> set the remaining LSBs of the HFN component of COUNT-C for all radio bearers using RLC-TM and all signalling radio bearers to zero; + +4> not increment the HFN component of COUNT-C for radio bearers using RLC-TM; + +4> set the IE "*Status*" in the variable CIPHERING\_STATUS to "Started"; + +4> apply the algorithm according to IE "*Ciphering Algorithm*" with the ciphering key set stored in the USIM/SIM and apply ciphering immediately upon reception of the RADIO BEARER RECONFIGURATION message. + +If ciphering has been activated and ongoing in the *A/Gb mode* from which inter mode handover is performed, GERAN *Iu mode* should not include the IE "*Ciphering Mode Info*" in the SECURITY MODE COMMAND message that starts Integrity protection. + +2> if ciphering has not been activated and ongoing in the source BSS: + +3> for the CN domain included in the IE "*CN Domain Identity*" which is included in the IE "*RAB Information To Reconfigure*", or the CS domain when these IEs are not present: + +4> set the IE "*Status*" in the variable CIPHERING\_STATUS to "*Not Started*". + +2> if the MS has successfully connected to GERAN *Iu mode* then + +3> Set the START value stored in the USIM (see 3GPP TS 31.102) if present, and as stored in the MS if the SIM is present for any CN domain to the value "THRESHOLD" of the variable START\_THRESHOLD; + +1> if the received reconfiguration message did not include the structure "*Downlink Counter Synchronisation Info*": + +2> if the variable START\_VALUE\_TO\_TRANSMIT is set: + +3> include and set the IE "*START*" to the value of that variable; + +2> if the variable START\_VALUE\_TO\_TRANSMIT is not set and the IE "*New G-RNTT*" is included: + +3> calculate the START value according to sub-clause 7.18.4; + +3> include the calculated START values for each CN domain in the IE "*START List*" in the structure "*Uplink Counter Synchronisation Info*"; + +2> if the received reconfiguration message caused a change in the RLC size for any RB using RLC-AM: + +3> calculate the START value according to sub-clause 7.18.4; + +3> include the calculated START values for the CN domain associated with the corresponding RB identity in the IE "*START List*" in the structure "*Uplink Counter Synchronisation Info*". + +1> if the received reconfiguration message contained the IE "*Ciphering Mode Info*" or contained the IE "*Integrity Protection Mode Info*": + +2> set the IE "*Status*" in the variable SECURITY\_MODIFICATION for all the CN domains in the variable SECURITY\_MODIFICATION to "Affected"; + +1> if the received reconfiguration message (contained the IE "*Ciphering Mode Info*"); + +2> include and set the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" to the value of the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + +1> if the received reconfiguration message did not contain the IE "*Ciphering Activation Time for DBPSCH*" in the IE "*Ciphering Mode Info*"; + +2> if prior to this procedure there exist no transparent mode RLC radio bearers for the CN domain indicated in the IE "*CN Domain Identity*" in the IE "*RAB info*"; + +3> if, at the conclusion of this procedure, the MS will be in RRC-Cell\_Dedicated state; and + +3> if, at the conclusion of this procedure, at least one transparent mode RLC radio bearer exists for the CN domain indicated in the IE "*CN Domain Identity*" in the IE "*RAB info*"; + +4> include the IE "*COUNT-C Activation Time*" and specify a TDMA frame number for this IE. + +NOTE: GERAN does not include the IE "*Ciphering Mode Info*" in any reconfiguration messages unless it is also used to perform an SBSS relocation with change of ciphering algorithm. + +1> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and + +1> clear that entry; + +1> if the variable PDCP\_SN\_INFO is not empty: + +2> include the IE "*RB with PDCP Information List*" and set it to the value of the variable PDCP\_SN\_INFO; + +1> if the IE "*Integrity Protection Mode Info*" was present in the received reconfiguration message + +2> start applying the new integrity protection configuration in the uplink for SRB2 from and including the transmitted response message. + +If after state transition the MS enters RRC-GRA\_PCH state, the MS shall, after the transmission of the response message: + +1> if the criteria for GRA Update caused by "GRA reselection" according to sub-clause 7.8 is fulfilled: + +2> initiate a GRA Update procedure according to sub-clause 7.8 using the cause "GRA reselection"; + +2> when the GRA Update procedure completed: + +3> the procedure ends. + +#### 7.14.1.4 Transmission of a response message by the MS, normal case + +In case the procedure was triggered by reception of a RADIO BEARER SETUP message, the MS shall: + +1> transmit a RADIO BEARER SETUP COMPLETE as response message on the uplink SRB2 + +In case the procedure was triggered by reception of a RADIO BEARER RECONFIGURATION message, the MS shall: + +1> transmit a RADIO BEARER RECONFIGURATION COMPLETE as response message on the uplink SRB2 ; + +In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the MS shall: + +1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink SRB2; + +If the new RRC state is RRC-Cell\_Dedicated state or RRC-Cell\_Shared state, the response message shall be transmitted using the new configuration after the state transition, and the MS shall: + +1> if the structure "*Downlink Counter Synchronization Info*" was included in the reconfiguration message; or + +- 1> if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "*New G-RNTT*" is included: + - 2> when RLC sub-layer has confirmed the successful transmission of the response message: + - 3> if the variable PDCP\_SN\_INFO is empty: + - 4> configure the RLC entity for all AM and UM radio bearers and AM and UM signalling radio bearers except SRB2 to "continue"; + - 3> else: + - 4> configure the RLC entity for signalling radio bearers SRB1, SRB3 and SRB4 to "continue"; + - 4> configure the RLC entity for UM and AM radio bearers for which the IE "*PDCP SN Info*" is not included to "continue"; + - 3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain; + - 3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all their HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + - 3> set the remaining bits of the HFN component of COUNT-C values of all UM RLC entities to zero; + - 3> set the remaining bits of the HFN component of the COUNT-C values of all AM RLC entities to zero, for those bearers to which RLC entitie where re-established; + - 3> if the IE "*PDCP Context Relocation Info*" is not present: + - 4> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED\_RABS as specified in 3GPP TS 25.323. + - 3> if the IE "*PDCP Context Relocation Info*" is present: + - 4> perform the actions as specified in 7.19. +- 1> if the variable PDCP\_SN\_INFO is empty: + - 2> if the received reconfiguration message contained the IE "*Ciphering Mode Info*": + - 3> when RLC sub-layer has confirmed the successful transmission of the response message: + - 4> notify upper layers upon change of the security configuration; + - 4> perform the actions below; + - 2> if the received reconfiguration message did not contain the IE "*Ciphering Mode Info*": + - 3> when RLC sub-layer has been requested to transmit the response message: + - 4> perform the actions below; +- 1> if the variable PDCP\_SN\_INFO is non-empty: + - 2> when RLC sub-layer has confirmed the successful transmission of the response message: + - 3> for each radio bearer in the variable PDCP\_SN\_INFO: + - 4> if the IE "*RB Started*" in the variable ESTABLISHED\_RABS is set to "started": + - 5> configure the RLC entity for that radio bearer to "continue"; + - 3> perform the actions below. + +If the IE "*Synchronization Indication*" is present in the RADIO BEARER RECONFIGURATION and if requested in the IE "*Synchronization Indication*", the mobile station shall: + +- 1> include the observed time difference which it has measured when performing reconfiguration of the physical channels, corrected by half the timing advance received in the IE "*Timing Advance*" in the RADIO BEARER RECONFIGURATION COMPLETE message (detailed specifications are given in 3GPP TS 45.010). + +If the new RRC state is RRC-GRA\_PCH state, the response message shall be transmitted using the old configuration before the state transition and the MS shall: + +- 1> when RLC sub-layer has confirmed the successful transmission of the response message: + - 2> for each radio bearer in the variable PDCP\_SN\_INFO: + - 3> if the IE "*RB Started*" in the variable ESTABLISHED\_RABS is set to "started": + - 4> configure the RLC entity for that radio bearer to "continue"; + - 2> enter the new RRC state (RRC-Cell\_Shared state or RRC-GRA\_PCH state, respectively); + - 2> perform the actions below. + +The MS shall: + +- 1> set the variable ORDERED\_RECONFIGURATION to FALSE; +- 1> if the received reconfiguration message contained the IE "*Ciphering Mode Info*": + - 2> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; + - 2> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; +- 1> if the received reconfiguration message contained the IE "*Integrity Protection Mode Info*": + - 2> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; + - 2> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; +- 1> clear the variable PDCP\_SN\_INFO; +- 1> clear the variable START\_VALUE\_TO\_TRANSMIT; +- 1> clear the variable SECURITY\_MODIFICATION; +- 1> continue RLC operation. + +#### 7.14.1.5 Reception of a response message by the GERAN, normal case + +When GERAN has received one of the following reconfiguration response messages: + +- RADIO BEARER SETUP COMPLETE message; or +- RADIO BEARER RECONFIGURATION COMPLETE message; or +- RADIO BEARER RELEASE COMPLETE message; + +GERAN shall delete the old configuration. + +If the IE "*START*" or the IE "*START List*" is included in reconfiguration response message, the GERAN shall: + +- 1> set the START value for each CN domain with the corresponding values as received in this response message; + +- 1> consequently, then use the START values to initialise the hyper frame numbers, in the same way as specified for the MS in sub-clause 7.14.1.3, for any new radio bearers that are established. + +If GERAN has ordered a ciphering reconfiguration by including the IE "*Ciphering Mode Info*", GERAN shall: + +- 1> For radio bearers using RLC-AM or RLC-UM: + - 2> use the old ciphering configuration for received RLC PDUs with RLC sequence number less than the RLC sequence number indicated in the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" sent by the MS; + - 2> use the new ciphering configuration for received RLC PDUs with RLC sequence number greater than or equal to the RLC sequence number indicated in the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" sent by the MS; + - 2> if an RLC reset or re-establishment occurs after the reconfiguration response message has been received by the GERAN before the activation time for the new ciphering configuration has been reached: + - 3> ignore the activation time; and + - 3> apply the new ciphering configuration immediately after the RLC reset or RLC re-establishment. +- 1> For radio bearers using RLC-TM: + - 2> use the new ciphering configuration and only begin incrementing the COUNT-C at the TDMA FRAME NUMBER as indicated in: + - 3> the IE "*Ciphering Activation Time for DBPSCH*" in the IE "*Ciphering Mode Info*", if included in the message that triggered the radio bearer control procedure; or + - 3> the IE "*COUNT-C Activation Time*", if included in the response message for this procedure. +- 1> the procedure ends on the GERAN side + +### 7.14.1.6 Unsupported configuration in the MS + +If the GERAN instructs the MS to use a configuration, which it does not support and/or if the received message causes the variable UNSUPPORTED\_CONFIGURATION to be set to TRUE, the MS shall: + +- 1> transmit a failure response as specified in sub-clause 7.14.1.9, setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 2> set it to the value of "*RRC Transaction Identifier*" in the entry for the received message in the table "*Accepted transactions*" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "*Failure Cause*" to "*configuration unsupported*"; +- 1> set the variable UNSUPPORTED\_CONFIGURATION to FALSE; +- 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. + +The procedure ends. + +### 7.14.1.7 Physical channel failure + +A physical channel failure occurs in case the criteria defined in 7.18 are not fulfilled. + +If the received message (a RADIO BEARER SETUP message, a RADIO BEARER RECONFIGURATION message or a RADIO BEARER RELEASE message) causes the MS to enter in RRC-Cell\_Dedicated state and the MS fails to establish the basic physical subchannel(s) indicated in the received message the MS shall: + +- 1> revert to the configuration prior to the reception of the message (old configuration); + +- 1> if the old configuration includes dedicated physical channels (RRC-Cell\_Dedicated state) and the MS is unable to revert to the old configuration: + - 2> initiate a Cell Update procedure according to sub-clause 7.8, using the cause "radio link failure"; + - 2> after the Cell Update procedure has completed successfully: + - 3> proceed as below; +- 1> if the old configuration does not include dedicated physical channels (RRC-Cell\_Shared state): + - 2> select a suitable GRA cell according to 7.8; + - 2> if the MS selects another cell than the cell the MS camped on upon reception of the reconfiguration message : + - 3> initiate a Cell Update procedure according to sub-clause 7.8, using the cause "cell reselection"; + - 3> after the Cell Update procedure has completed successfully: + - 4> proceed as below; +- 1> transmit a failure response message as specified in sub-clause 7.14.1.9, setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "*Failure Cause*" to "physical channel failure"; +- 1> set the variable ORDERED\_RECONFURATION to FALSE; +- 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received; + +The procedure ends. + +If the criteria for radio link failure is met in the old configuration during the reconfiguration procedure as specified in sub-clause 7.18.8 the MS shall: + +- 1> if MS would have entered in RRC-GRA\_PCH state as a successful completion of this reconfiguration procedure and MS has already submitted a response message to lower layers: + - 2> initiate a Cell Update procedure according to sub-clause 7.8.1.3, using the cause "radio link failure"; +- 2> the procedure ends.If the criteria for radio link failure is met in the new configuration during the reconfiguration procedure (i.e. while MS is waiting for RLC acknowledgement for a response message.) the MS shall act as specified in sub-clause 7.18.8 and in addition it shall: + - 1> if the received reconfiguration causes: + - the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to be set to TRUE; or + - the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to be set to TRUE + +- 2> perform the actions specified in sub-clause 7.14.1.12.2. + +#### 7.14.1.8 Cell re-selection + +If the MS performs cell re-selection during the reconfiguration procedure, the MS shall: + +- 1> initiate a Cell Update procedure, as specified in sub-clause 7.8; +- 1> continue with the Reconfiguration procedure. + +### 7.14.1.9 Transmission of a response message by the MS, failure case + +The MS shall: + +- 1> in case of reception of a RADIO BEARER SETUP message: + - 2> if the Radio Bearer Establishment procedure affects several radio bearers: + - 3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER SETUP FAILURE message; + - 2> transmit a RADIO BEARER SETUP FAILURE as response message on the SRB2; +- 1> in case of reception of a RADIO BEARER RECONFIGURATION message: + - 2> if the Radio Bearer Reconfiguration procedure affects several radio bearers: + - 3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER RECONFIGURATION FAILURE message; + - 2> transmit a RADIO BEARER RECONFIGURATION FAILURE as response message on the SRB2; +- 1> in case of reception of a RADIO BEARER RELEASE message: + - 2> if the Radio Bearer Release procedure affects several radio bearers: + - 3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER RELEASE FAILURE message; + - 2> transmit a RADIO BEARER RELEASE FAILURE as response message on the SRB2; +- 1> when the response message has been submitted to lower layers for transmission: + - 2> continue with any ongoing processes and procedures as if no reconfiguration attempt had occurred; + - 2> if a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied according to 7.19.4.5. + +### 7.14.1.10 Reception of a response message by the GERAN, failure case + +When the GERAN has received: + +- the RADIO BEARER SETUP FAILURE message; or +- the RADIO BEARER RECONFIGURATION FAILURE message; or +- the RADIO BEARER RELEASE FAILURE message + +the GERAN may restore the old and delete the new configuration. Upper layers shall be notified of the failure. + +The procedure ends on the GERAN side. + +### 7.14.1.11 Invalid configuration + +If the variable INVALID\_CONFIGURATION is set to TRUE the MS shall: + +- 1> keep the configuration existing before the reception of the message; +- 1> transmit a failure response message as specified in sub-clause 7.14.1.9, setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 3> set it to the value of "*RRC transaction identifier*" in the entry for the received message in the table "*Accepted transactions*" in the variable *TRANSACTIONS*; and + - 3> clear that entry; + +- 2> set the IE "*Failure Cause*" to "invalid configuration"; +- 1> set the variable INVALID\_CONFIGURATION to FALSE; +- 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received; + +The procedure ends. + +### 7.14.1.12 Incompatible simultaneous reconfiguration + +If the table "Rejected transactions" in the variable TRANSACTIONS is set due to the received message and the variable PROTOCOL\_ERROR\_REJECT is set to FALSE, the MS shall: + +- 1> not apply the configuration contained in the received reconfiguration message; +- 1> transmit a failure response message as specified in sub-clause 7.14.1.9, setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "*Failure Cause*" to "incompatible simultaneous reconfiguration"; +- 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received; + +The procedure ends. + +#### 7.14.1.12.1 Incompatible simultaneous security reconfiguration + +If the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION is set to TRUE due to the received reconfiguration message, the MS shall: + +- 1> transmit a failure response message as specified in sub-clause 7.14.1.9, setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "*Failure Cause*" to the cause value "incompatible simultaneous reconfiguration"; +- 1> set the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION to FALSE; +- 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. + +The procedure ends. + +#### 7.14.1.12.2 Cell Update procedure during security reconfiguration + +If: + +- a Cell Update procedure according to sub-clause 7.8.1 is initiated; and +- the received reconfiguration message causes either, +- the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to be set to TRUE; and/or +- the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to be set to TRUE; + +the MS shall: + +- 1> release all radio resources; +- 1> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; and +- 1> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS; +- 1> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; +- 1> clear the variable ESTABLISHED\_RABS; +- 1> if the received reconfiguration message contained the IE "*Ciphering Mode Info*": + - 2> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + - 2> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + - 2> clear the variable SECURITY\_MODIFICATION. +- 1> if the received reconfiguration message contained the IE "*Integrity Protection Mode Info*": + - 2> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + - 2> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; +- 1> enter RRC-Idle mode; +- 1> perform the actions specified in clause 6 and sub-clause 7.18 when entering RRC- Idle mode from RRC-Connected mode; +- 1> the procedure ends. + +NOTE: The GERAN shall use radio bearer control messages to perform an SBSS relocation only in case of state transitions from RRC-CELL\_Dedicated to RRC-Cell-CELL\_Dedicated state. + +#### 7.14.1.13 Invalid received message + +If the received reconfiguration message contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows. The MS shall: + +- 1> transmit a failure response message as specified in sub-clause 7.14.1.9, setting the information elements as specified below: + - 2> include the IE "*RRC Transaction Identifier*"; and + - 2> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> set the IE "*Failure Cause*" to the cause value "protocol error"; + - 2> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION. +- 1> continue with any ongoing processes and procedures as if the reconfiguration message was not received. + +#### 7.14.1.14 Abnormal cases + +If the mobile station has no current CA and if it needs a CA to analyse one of the messages RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION, or RADIO BEARER RELEASE the MS shall: + +- 1> stay on the current channel(s); and +- 1> send the failure message according to sub-clause 7.14.1.9 with cause "no cell allocation available"; and + +1> act and set the variables according with the sub-clauses 7.19 and 10.4. + +If the RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message instructs the MS to use a Channel Description or Channel Mode that it does not support, or if the Channel Mode to use is not defined for all channel sets, then the mobile station shall: + +1> send the failure message according to sub-clause 7.14.1.9 with cause "channel mode unacceptable"; and + +1> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +1> remain on the current channel(s) and use the old Channel Description or Channel Mode(s). + +If the RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message instructs the MS to use a Modulation or Interleaving for FLO configuration that it does not support, or if the Mode and Modulation to use is not defined for all channel sets, then the mobile station shall: + +1> send the failure message according to sub-clause 7.14.1.9 with cause "channel mode unacceptable"; and + +1> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +1> remain on the current channel(s) and use the old configuration. + +If the mobile station receives the RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message containing an inconsistent IE "*MultiRate Configuration*", then the mobile station shall: + +1> send the failure message according to sub-clause 7.14.1.9 with cause "channel mode unacceptable"; and + +1> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +1> remain on the current channel(s) and use the old Channel Description or Channel Mode(s). + +If during the initial assignment of the multirate speech the mobile station receives RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message and the IE "*MultiRate Configuration*" is not present, then the mobile station shall: + +1> send the failure message according to sub-clause 7.14.1.9 with cause "channel mode unacceptable"; and + +1> act and set the variables according with the sub-clause 7.19.; and + +1> remain on the current channel(s) and use the old Channel Description or Channel Mode(s). + +If the RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall: + +1> send the failure message according to sub-clause 7.14.1.9 with cause "frequency not implemented"; and + +1> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +1> remain on the current channel(s). + +If MS receives the RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message with a IE "*Frequency List*" indicating frequencies that are not all in one band, then the mobile station shall: + +1> send the failure message according to sub-clause 7.14.1.9 with cause "frequency not implemented"; and + +1> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +1> remain on the current channel(s). + +If the mobile station receives the RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message with a IE *Mobile Allocation* indexing frequencies that are not all in one band, then the mobile station shall: + +1> send the failure message according to sub-clause 7.14.1.9 with cause "frequency not implemented"; and + +1> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +l> remain on the current channel(s). + +NOTE: A RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message sent to a multi band mobile station shall not be considered invalid because it indicates frequencies that are all in a different frequency band to that of the current channel. + +If the mobile station receives RADIO BEARER RECONFIGURATION message with a IE *Mobile Allocation* indexing frequencies that are not all in one band and a IE *Starting Time* indicating a time that has not elapsed then the mobile station shall: + +l> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +l> remain on the current channel(s). + +l> send a RRC STATUS message with cause "frequency not implemented". + +If the mobile station receives a RADIO BEARER RECONFIGURATION message with a IE "*Mobile Allocation*" indexing frequencies that are not all in one band and a IE "*Starting Time*" indicating a time that has elapsed, then the mobile station shall act and set the variables according with the sub-clause 7.19. + +If the mobile station receives a RADIO BEARER RECONFIGURATION message with the IE "*Synchronization Indication*" and the IE "*Timing Advance*" included; and + +If synchronous or pseudo-synchronous (see sub-clause 7.18.6) physical channel establishment is performed, when using Radio Bearer Reconfiguration procedure; and + +If the mobile station knows that the timing advance with the new cell is out of range, i.e. is bigger than the maximum timing advance that can be coded as specified in 3GPP TS 44.004; and + +If the new cell does not accept out of range timing advance as indicated in the RADIO BEARER RECONFIGURATION message, the mobile station shall: + +l> send a failure message according with sub-clause 7.14.1.9 on the SRB2 and does not attempt that reconfiguration as defined in subclause 7.14.1.3; + +l> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +l> remain on the current channel(s). + +If the mobile station receives a RADIO BEARER RECONFIGURATION message with IE "*Frequency Short List*" indicating frequencies that are not all in one band, then the mobile station shall: + +l> send the failure message according to sub-clause 7.14.1.9 with cause "frequency not implemented"; and + +l> act and set the variables according with the sub-clauses 7.19 and 10.4; and + +l> remain on the current channel(s). + +If "*Synchronization Indication*" IE is present in RADIO BEARER RECONFIGURATION message and if it indicates non-synchronized type of physical channel establishment (see sub-clause 7.18.6), and if timer T3124 times out or if a lower layer failure happens on the new channel before the RADIO BEARER RECONFIGURATION COMPLETE message has been sent, the mobile station shall: + +l> deactivate the new channels, reactivates the old channels; + +l> reconnect the DBPSCHs if any; + +l> then send a failure message as specified in sub-clause 7.14.1.9; and + +l> resume normal operation as if no physical channel establishment (see sub-clause 7.18.6) attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the RADIO BEARER RECONFIGURATION message was received. + +If the mobile station receives a RADIO BEARER RECONFIGURATION message and if at least one of the following IEs, IE "*Handover Reference*", IE "*Power Command and Access Type*", IE "*Cell Description*" and IE "*Description of the first channel after time*" is not present, the MS shall: + +- 1> send a failure message according with subclause 7.14.1.9 on the SRB2 and does not attempt that reconfiguration as defined in subclause 7.14.3; +- 1> act and set the variables according with the sub-clauses 7.19 and 10.4; and +- 1> remain on the current channel(s). + +If the mobile station receives a RADIO BEARER RECONFIGURATION message and if only IE "*Power Command*" is present, the MS shall: + +- 1> send a failure message according with subclause 7.14.1.9 on the SRB2 and does not attempt that reconfiguration as defined in subclause 7.14.3 and 10.4; +- 1> act and set the variables according with the sub-clause 7.19 and 10.4. + +If IE "*SBPSCH Description*" is present in the reconfiguration messages and if RLC data blocks are not received in the T3190 seconds(as specified in TS 44.060), the mobile station shall: + +- 1> deactivate the new channels, reactivates the old channels; +- 1> reconnect the SBPSCHs if any; +- 1> then send a failure message as specified in sub-clause 7.14.1.9 with a cause "protocol error unspecified"; and +- 1> resume normal operation as if no physical channel establishment (see sub-clause 7.18.6) attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the reconfiguration message was received. + +If IE "*SBPSCH Description*" is present in the reconfiguration messages and if the mobile station has been assigned more PDCHs than it supports according to its MS multislot class or if the mobile station has been assigned a TBF in EGPRS TBF mode and the MS does not support EGPRS, or if the MS has been assigned an MCS (e.g. 8-PSK in the uplink) that the MS does not support or if the failure is due to any other reason, return to MAC-Idle state and cell reselection continues. + +The MS shall: + +- 1> then send a failure message as specified in sub-clause 7.14.1.9 with a cause "protocol error unspecified" + +## 7.14.2 MS initiated DTM procedures while in RRC-Cell\_Dedicated-MAC-Dedicated state + +### 7.14.2.1 General + +While in RRC-Cell\_Dedicated-MAC-Dedicated state, the establishment of one or more SBPSCHs may be initiated by the RRC entity of the mobile station using the DTM Request procedure. The procedure is used only for existing radio bearers and is triggered by a request from upper layers to transfer an upper layer PDU. + +### 7.14.2.2 Initiation of the DTM Request procedure by the MS + +The mobile station initiates the DTM Request procedure by sending a GERAN Iu mode DTM REQUEST message on the SRB2. + +The MS shall set the IEs in the GERAN Iu mode DTM REQUEST message as follows: + +- 1> calculate the START according to sub-clause 7.19.4 for the CN domain as set in the IE "*CN Domain Identity*"; and +- 2> include the calculated START value for that CN domain in the IE "*START*"; +- 1> include IE "*Iu mode RRC Channel RequestDescription*" to indicate the establishment cause, as applicable, a request to send user data, page response or a mobility management message; +- 1> may include "*Integrity Check Info*" IE. If the IE is included, act as is specified in sub-clause 7.19.4.6; + +The MS shall: + +- 1> transmit the GERAN Iu mode DTM REQUEST message on the uplink SRB 2; +- 1> start timer T3148. + +### 7.14.2.3 Reception of a GERAN Iu mode DTM REQUEST message by the GERAN + +#### 7.14.2.3.1 General + +Upon receiving a GERAN Iu mode DTM REQUEST message, GERAN shall either: + +- 1> transmit the RADIO BEARER RECONFIGURATION message on the downlink SRB 2 as specified in sub-clause 7.14.2.3.2; or +- 1> transmit the GERAN Iu mode DTM REJECT message on the downlink SRB 2 as specified in sub-clause 7.14.2.3.3. + +#### 7.14.2.3.2 SBPSCH assignment + +On receipt of a GERAN Iu mode DTM REQUEST message the network may allocate one or more uplink SBPSCH(s) for the mobile station. The SBPSCH(s) are assigned to the mobile station in the RADIO BEARER RECONFIGURATION message. + +The RADIO BEARER RECONFIGURATION is sent on SRB2 as specified in sub-clause 7.14.1. If frequency hopping is applied, the mobile station shall use the cell allocation defined for the cell to decode the mobile allocation. + +The allocation of the uplink SBPSCH(s) may imply the reallocation of the DBPSCH(s). The RADIO BEARER RECONFIGURATION message shall not be used to change to a dependent configuration. + +On receipt of a RADIO BEARER RECONFIGURATION message the mobile station shall stop T3148. + +If the received RADIO BEARER RECONFIGURATION message includes uplink SBPSCH(s), the mobile station shall proceed as specified in sub-clause 7.14.1.3. If the received RADIO BEARER RECONFIGURATION message includes downlink SBPSCH(s) and no uplink SBPSCH(s), the mobile station shall stop T3148, abort the DTM request procedure and proceed as specified in sub-clause 7.14.1.3, and then attempt an establishment of uplink TBF, using the applicable procedure specified in 3GPP TS 44.160. + +If the RADIO BEARER RECONFIGURATION includes allocation of one or more uplink SBPSCHs but the resources can not be allocated for all RBs requested by the mobile station, then failure is triggered for the radio bearers to which resources where not granted and T3148 is stopped. Request of resources for failed RBs is then done as specified in 3GPP TS 44.160. + +#### 7.14.2.3.3 DTM Request rejection + +If the network cannot allocate the requested SBPSCH(s) it may send to the mobile station a GERAN Iu mode DTM REJECT message on the SRB2. This message shall contain + +- 1> the "*Wait Indication*" IE; +- 1> the "*RB Identity*" IE set to the RB\_IDENTITY; +- 1> the "*RRC transaction identifier*" IE set to the the value of "RRC transaction identifier" in the entry for the GERAN Iu mode DTM REJECT message in the table "Rejected transactions" in the variable TRANSACTIONS; +- 1> the "*Failure Cause*" IE set to the cause value "protocol error"; +- 1> the "*Protocol Error Information*" IE with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION. + +#### 7.14.2.3.4 Reception of a GERAN Iu mode DTM REJECT message by the MS, normal case + +On receipt of the GERAN Iu mode DTM REJECT message, the mobile station shall: + +- 1> stop T3148; +- 1> notify upper layers of a SBPSCH establishment failure; + +1> start timer T3142 with the value given in the "*Wait Indication*" information element. + +The mobile station is not allowed to make a new attempt for a DTM request procedure in the same cell until T3142 expires. The value of the wait indication (i.e. T3142) relates to the cell from which it was received. + +After sending GERAN Iu mode DTM REQUEST message the MS shall wait for the response from the network or expiry of timer T3148 before it may initiate new DTM Request procedure. + +The GERAN Iu mode DTM Reject procedure rejects all pending requests that were sent in the previous GERAN Iu mode DTM Request message. + +#### 7.14.2.3.5 Invalid GERAN Iu mode DTM REJECT message + +If the MS receives an GERAN Iu mode DTM REJECT message which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows: + +The MS shall: + +- 1> set the variable PROTOCOL\_ERROR\_INDICATOR to TRUE; +- 1> set the IEs in the GERAN Iu mode DTM REQUEST message as specified in sub-clause 7.14.2.2; +- 1> transmit the GERAN Iu mode DTM REQUEST message on the uplink SRB 2; +- 1> start timer T3148. + +#### 7.14.2.4 Abnormal cases + +Abnormal cases related to radio bearer reconfiguration procedures are defined in sub-clause 7.14.1.14. + +In the following cases a GERAN Iu mode DTM Request failure has occurred: + +- At expiry of T3148; +- If a RADIO BEARER RECONFIGURATION message indicates resources in a non-supported frequency band. The cause value is "frequency not implemented". The actions are defined in sub-clause 7.14.1.14. +- If the information available in the mobile station after the reception of a RADIO BEARER RECONFIGURATION message does not satisfactorily define uplink packet resources. The cause value is "protocol error unspecified". The actions are defined in sub-clause 7.14.1.14. +- If a RADIO BEARER RECONFIGURATION message includes a mobile allocation or a frequency list that indexes frequencies in more than one frequency band. The cause value is "frequency not implemented". The actions are defined in sub-clause 7.14.1.14. +- If a RADIO BEARER RECONFIGURATION message assigns resources not compliant with the multislot capabilities of the mobile station. The cause value is "channel mode unacceptable". The actions are defined in sub-clause 7.14.1.14. +- If the mobile station has no current CA and if it needs a CA to analyse the RADIO BEARER RECONFIGURATION message. The cause value is "no cell allocation available". The actions are defined in sub-clause 7.14.1.14. +- If the RADIO BEARER RECONFIGURATION message instructs the mobile station to use a channel description or mode that it does not support. The cause value is "channel mode unacceptable". The actions are defined in sub-clause 7.14.1.14. +- If the RADIO BEARER RECONFIGURATION message does not include any uplink or downlink packet resources. The cause value is "protocol error unspecified ". The actions are defined in sub-clause 7.14.1.4. + +#### 7.14.2.5 T3148 expiry + +On expiry of timer T3148 DTM Request procedure has failed on the mobile station side. The mobile station shall then reinitiate DTM Request procedure unless it has already been reinitiated 4 times. In that case DTM Request procedure shall be aborted. + +## 7.15 Signalling flow procedures + +### 7.15.1 Signalling connection release procedure + +#### 7.15.1.1 General + +![Sequence diagram showing the Signalling Connection Release procedure. The diagram consists of two vertical lifelines labeled 'MS' (Mobile Station) on the left and 'GERAN' (GSM Edge Radio Access Network) on the right. A horizontal arrow points from the GERAN lifeline to the MS lifeline, labeled 'SIGNALLING CONNECTION RELEASE'.](29997432244f81212ee1e6c94f308f1b_img.jpg) + +``` + +sequenceDiagram + participant GERAN + participant MS + Note right of GERAN: SIGNALLING CONNECTION RELEASE + GERAN->>MS: SIGNALLING CONNECTION RELEASE + +``` + +Sequence diagram showing the Signalling Connection Release procedure. The diagram consists of two vertical lifelines labeled 'MS' (Mobile Station) on the left and 'GERAN' (GSM Edge Radio Access Network) on the right. A horizontal arrow points from the GERAN lifeline to the MS lifeline, labeled 'SIGNALLING CONNECTION RELEASE'. + +**Figure 7.15.1.1.1: Signalling Connection Release procedure, normal case** + +The Signalling Connection Release procedure is used to notify to the MS that one of its ongoing signalling connections has been released. The procedure does not initiate the release of the RRC connection. + +#### 7.15.1.2 Initiation of SIGNALLING CONNECTION RELEASE by the GERAN + +To initiate the procedure, the GERAN transmits a SIGNALLING CONNECTION RELEASE message on SRB 2 . + +#### 7.15.1.3 Reception of SIGNALLING CONNECTION RELEASE by the MS + +Upon reception of a SIGNALLING CONNECTION RELEASE message, the MS shall: + +- 1> indicate the release of the signalling connection and pass the value of the IE "*CN Domain Identity*" to upper layers; +- 1> remove the signalling connection with the identity indicated by the IE "*CN Domain Identity*" from the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; +- 1> clear the entry for the SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS; +- 1> the procedure ends. + +#### 7.15.1.4 Invalid SIGNALLING CONNECTION RELEASE message + +If the MS receives a SIGNALLING CONNECTION RELEASE message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause 8, the MS shall perform procedure specific error handling as follows: + +- 1> include the IE "*Identification of Received Message*"; and + - 2> set the IE "*Received Message Type*" to SIGNALLING CONNECTION RELEASE; + - 2> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the SIGNALLING CONNECTION RELEASE message in the table "Rejected transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; +- 1> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION; +- 1> transmit an RRC STATUS message on SRB 2 uplink; +- 1> when the RRC STATUS message has been submitted to lower layers for transmission: + +2> continue with any ongoing processes and procedures as if the invalid SIGNALLING CONNECTION RELEASE message has not been received. + +### 7.15.1.5 Invalid configuration + +If radio access bearers for the CN domain indicated by the IE "CN domain identity" exist in the variable ESTABLISHED\_RABS, the MS shall: + +- 1> transmit an RRC STATUS message on SRB 2 uplink using AM RLC; +- 1> include the IE "*Identification of Received Message*"; and +- 1> set the IE "*Received Message Type*" to SIGNALLING CONNECTION RELEASE; and +- 1> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the SIGNALLING CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS and clear that entry; +- 1> include the IE "*Protocol Error Information*" with contents set to the value "Message not compatible with receiver state"; +- 1> when the RRC STATUS message has been submitted to lower layers for transmission: + - 2> continue with any ongoing processes and procedures as if the invalid SIGNALLING CONNECTION RELEASE message has not been received. + +## 7.15.2 Signalling connection release indication procedure + +### 7.15.2.1 General + +![Sequence diagram showing the Signalling Connection Release Indication procedure. The MS (Mobile Station) sends a 'SIGNALLING CONNECTION RELEASE INDICATION' message to the GERAN (GSM EDGE Radio Access Network).](41fa90d03d7195caa162c74d289817a4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + Note right of MS: MS sends SIGNALLING CONNECTION RELEASE INDICATION to GERAN + MS->>GERAN: SIGNALLING CONNECTION RELEASE INDICATION + +``` + +Sequence diagram showing the Signalling Connection Release Indication procedure. The MS (Mobile Station) sends a 'SIGNALLING CONNECTION RELEASE INDICATION' message to the GERAN (GSM EDGE Radio Access Network). + +**Figure 7.15.2.1.1: Signalling Connection Release Indication procedure, normal case** + +The Signalling Connection Release Indication procedure is used by the MS to indicate to the GERAN that one of its signalling connections has been released. The procedure may in turn initiate the RRC connection release procedure. + +### 7.15.2.2 Initiation + +The MS shall, on receiving a request to release (abort) the signalling connection from upper layers: + +- 1> if a signalling connection in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS for the specific CN domain identified with the IE "*CN domain identity*" exists: + - 2> initiate the signalling connection release indication procedure. +- 1> otherwise: + - 2> abort any ongoing establishment of signalling connection for that specific CN domain as specified in 7.15.2.2a. + +Upon Initiation of the Signalling Connection Release Indication procedure in RRC-GERAN\_PCH state, the MS shall: + +- 1> perform a Cell Update procedure, according to sub-clause 7.8, using the cause "uplink data transmission"; +- 1> when the Cell Update procedure completed successfully: + +2> continue with the signalling connection release indication procedure as described below; + +The MS shall: + +- 1> set the IE "*CN Domain Identity*" to the value indicated by the upper layers. The value of the IE indicates the CN domain whose associated signalling connection the upper layers are indicating to be released; +- 1> remove the signalling connection with the identity indicated by upper layers from the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; +- 1> transmit a SIGNALLING CONNECTION RELEASE INDICATION message on SRB 2. + +When the successful delivery of the SIGNALLING CONNECTION RELEASE INDICATION message has been confirmed by RLC sub-layer the procedure ends. + +### 7.15.2.2a RLC re-establishment, inter-mode handover or inter-RAT change + +If a re-establishment of RLC on signalling radio bearer SRB2 occurs before the successful delivery of the SIGNALLING CONNECTION RELEASE INDICATION message has been confirmed by RLC sublayer, the MS shall: + +- 1> retransmit the SIGNALLING CONNECTION RELEASE INDICATION message on the uplink using signalling radio bearer SRB2. + +If an inter-RAT handover from GERAN procedure occurs before the successful delivery of the SIGNALLING CONNECTION RELEASE INDICATION message has been confirmed by RLC sublayer, the MS shall: + +- 1> abort the signalling connection while in the new RAT. + +If an inter-mode handover procedure occurs before the successful delivery of the SIGNALLING CONNECTION RELEASE INDICATION message has been confirmed by RLC sublayer, the MS shall: + +- 1> abort the signalling connection while in A/Gb mode. + +### 7.15.2.3 Reception of SIGNALLING CONNECTION RELEASE INDICATION by the GERAN + +Upon reception of a SIGNALLING CONNECTION RELEASE INDICATION message, the GERAN requests the release of the signalling connection from upper layers. Upper layers may then initiate the release of the signalling connection. + +## 7.16 Security mode control + +### 7.16.1 Security mode control + +![Sequence diagram of the security mode control procedure between MS and GERAN.](ae31c0503b477813f29e7f754dd7a9ed_img.jpg) + +``` +sequenceDiagram + participant MS + participant GERAN + Note right of GERAN: SECURITY MODE COMMAND + GERAN->>MS: SECURITY MODE COMMAND + Note left of MS: SECURITY MODE COMPLETE + MS->>GERAN: SECURITY MODE COMPLETE +``` + +The diagram illustrates the security mode control procedure between a Mobile Station (MS) and a GERAN. It consists of two main message exchanges. First, the GERAN sends a 'SECURITY MODE COMMAND' message to the MS, represented by a horizontal arrow pointing from the GERAN lifeline to the MS lifeline. Second, the MS responds with a 'SECURITY MODE COMPLETE' message, represented by a horizontal arrow pointing from the MS lifeline to the GERAN lifeline. The messages are shown within rectangular boxes on the respective lifelines. + +Sequence diagram of the security mode control procedure between MS and GERAN. + +Figure 7.16.1.1: Security mode control procedure + +### 7.16.1.1 General + +The purpose of this procedure is to trigger the start of ciphering or to command the restart of the ciphering with a new ciphering configuration, for the radio bearers of one CN domain and for all signalling radio bearers. + +It is also used to start integrity protection or to modify the integrity protection configuration for all signalling radio bearers. + +### 7.16.1.2 Initiation + +#### 7.16.1.2.1 Ciphering configuration change + +To start/restart ciphering, GERAN sends a SECURITY MODE COMMAND message on one downlink SRB2 using the most recent ciphering configuration. If no such ciphering configuration exists then the SECURITY MODE COMMAND message is not ciphered. The GERAN shall not transmit a SECURITY MODE COMMAND message to signal a change in ciphering algorithm. + +When configuring ciphering, GERAN shall ensure that the MS needs to store at most two different ciphering configurations (keyset and algorithm) per CN domain, in total over all radio bearers at any given time. For signalling radio bearers the total number of ciphering configurations that need to be stored is at most three. + +Prior to sending the SECURITY MODE COMMAND message, for the CN domain indicated in the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND message, the GERAN shall: + +- 1> suspend all radio bearers using RLC-AM or RLC-UM and suspend all signalling radio bearers using RLC-AM or RLC-UM, except the signalling radio bearer used to send the SECURITY MODE COMMAND message on the downlink SRB2 according to the following: + - 2> send an indication to lower layers: + - 3> not to transmit RLC PDUs with sequence number greater than or equal to the number in IE "*RB Downlink Ciphering Activation Time Info*" in the IE "*Ciphering Mode Info*" on all suspended radio bearers and all suspended signalling radio bearers; + - 3> set, for the signalling radio bearer used to send the SECURITY MODE COMMAND message, the "RLC sequence number" in IE "*RB Downlink Ciphering Activation Time Info*" in the IE "*Ciphering Mode Info*", at which time the new ciphering configuration shall be applied; +- 1> if a transparent mode radio bearer for this CN domain exists + - 2> include the "Ciphering Activation Time for DBPSCH" in IE "*Ciphering Mode Info*", at which time the new ciphering configuration shall be applied; + - 2> GERAN chooses the value for the " Ciphering Activation Time for DBPSCH " such that the new ciphering configuration will occur after all the pending ciphering activation times have been reached for the transparent mode radio bearers of this CN domain. +- 1> consider an ciphering activation time in downlink to be pending until the RLC sequence number of the next RLC PDU to be transmitted for the first time is equal to or larger than the selected activation time; +- 1> set, for each suspended radio bearer and signalling radio bearer that has no pending ciphering activation time set by a previous security mode control procedure, an "RLC sequence number" in IE "*RB Downlink Ciphering Activation Time Info*" in the IE "*Ciphering Mode Info*", at which time the new ciphering configuration shall be applied; +- 1> set, for each suspended radio bearer and signalling radio bearer that has a pending ciphering activation time set by a previous security mode control procedure, the "RLC sequence number" in IE "*RB Downlink Ciphering Activation Time Info*" in the IE "*Ciphering Mode Info*" to the value used in the previous security mode control procedure, at which time the latest ciphering configuration shall be applied. +- 1> if Integrity protection has already been started for the MS; and + - 2> if for the CN domain indicated in the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND message, a new security key set (new ciphering and integrity protection keys) has been received from upper layers since the transmission of the last SECURITY MODE COMMAND message for that CN domain: + +- 3> include the IE "*Integrity Protection Mode Info*" in the SECURITY MODE COMMAND message +- 1> if integrity protection has already been started for the MS; and +- 2> if the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND message is different from the IE "*CN Domain Identity*" that was sent in the previous SECURITY MODE COMMAND message to the MS: +- 3> include the IE "*Integrity Protection Mode Info*" in the SECURITY MODE COMMAND message +- 1> transmit the SECURITY MODE COMMAND message on the downlink SRB2. + +#### 7.16.1.2.2 Integrity protection configuration change + +To start or modify integrity protection, the GERAN sends a SECURITY MODE COMMAND message on the downlink SRB2 using the new integrity protection configuration. The GERAN shall not modify integrity protection for a CN domain for which a SECURITY MODE COMMAND message configuring integrity protection has been previously sent for an ongoing signalling connection unless the application of new integrity keys needs to be signalled to the MS. The GERAN shall not transmit a SECURITY MODE COMMAND message to signal a change in integrity protection algorithm. + +When configuring Integrity protection, the GERAN shall: + +- 1> ensure that the MS needs to store at most three different Integrity protection configurations (keysets) at any given time. This includes the total number of Integrity protection configurations for all signalling radio bearers. +- 1> if Ciphering has already been started for the MS for the CN domain to be set in the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND message; and +- 2> if for the CN domain indicated in the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND message, a new security key set (new ciphering and integrity protection keys) has been received from upper layers since the transmission of the last SECURITY MODE COMMAND message for that CN domain: +- 3> include the IE "*Ciphering Mode Info*" in the SECURITY MODE COMMAND message; +- 1> if Ciphering has already been configured for the MS for a CN domain different from the CN domain to be set in the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND; +- 2> include the IE "*Ciphering Mode Info*" in the SECURITY MODE COMMAND message; + +Prior to sending the SECURITY MODE COMMAND message, for the CN domain indicated in the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND message, the GERAN shall: + +- 1> if this is the first SECURITY MODE COMMAND message sent for this RRC connection: +- 2> if new keys have been received: +- 3> initialise the hyper frame numbers as follows: +- 4> set all bits of the hyper frame numbers of the COUNT-I values for all signalling radio bearers to zero; +- 2> else (if new keys have not been received): +- 3> use the value "START" in the most recently received IE "*START List*" or IE "*START*" that belongs to the CN domain indicated in the IE "*CN Domain Identity*" to initialise all hyper frame numbers of COUNT-I for all the signalling radio bearers; by: +- 4> setting the 20 most significant bits of the hyper frame numbers for all signalling radio bearers to the value "START" in the most recently received IE "*START List*" or IE "*START*" for that CN domain; +- 4> setting the remaining bits of the hyper frame numbers equal to zero; +- 1> else (this is not the first SECURITY MODE COMMAND message sent for this RRC connection): +- 2> if new keys have been received; + +- 3> initialise the hyper frame number for COUNT-I for SRB2 as follows: + - 4> set all bits of the HFN of the COUNT-I value for SRB2 to zero; +- 2> if new keys have not been received; + - 3> initialize the hyper frame number for COUNT-I for SRB2 as follows: + - 4> set the 20 most significant bits of the HFN of the downlink and uplink COUNT-I to the value of the most recently received IE "*START*" or IE "*START List*" for the CN domain to be set in the the IE "*CN Domain Identity*"; + - 4> set the remaining bits of the HFN of the downlink and uplink COUNT-I to zero; +- 1> if the IE "*Integrity Protection Mode Command*" has the value "Start": + - 2> prohibit the transmission of signalling messages with any RRC SN on all signalling radio bearers, except SRB2; + - 2> set the FRESH value in the IE "*Integrity Protection Initialisation Number*", included in the IE "*Integrity Protection Mode Info*"; +- 1> if the IE "*Integrity Protection Mode Command*" has the value "Modify": + - 2> for each signalling radio bearer SRBn, except SRB2: + - 3> prohibit the transmission of signalling messages with RRC SN greater or equal to the RRC sequence number in entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "*Downlink Integrity Protection Activation Info*", included in the IE "*Integrity Protection Mode Info*"; + - 2> consider an integrity protection activation time in downlink to be pending until the selected activation time is equal to the next RRC sequence number to be used, which means that the last RRC message using the old integrity protection configuration has been transmitted to lower layers; + - 2> set, for each signalling radio bearer SRBn, that has no pending integrity protection activation time set by a previous security mode control procedure, an RRC sequence number in entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "*Downlink Integrity Protection Activation Info*", included in the IE "*Integrity Protection Mode Info*", at which time the new integrity protection configuration shall be applied; + - 2> set, for each signalling radio bearer SRBn, that has a pending integrity protection activation time set by a previous security mode control procedure, the RRC sequence number in entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "*Downlink Integrity Protection Activation Info*", included in the IE "*Integrity Protection Mode Info*", to the value used in the previous security mode control procedure, at which time the latest integrity protection configuration shall be applied; +- 1> transmit the SECURITY MODE COMMAND message on SRB2 using the new integrity protection configuration. + +NOTE 1: In the case of re-initialisation of Integrity Protection at HFN wrap around, the network takes into account the MS actions as described in sub-clauses 7.18.5.1 and 7.18.5.2 + +NOTE 2: After the SECURITY MODE COMMAND message is transmitted, the network needs to ensure that it can revert back to the old integrity protection until it receives a SECURITY MODE COMPLETE message, and take into account the MS actions when the Security Mode Control procedure is unsuccessful. The network is also aware that the MS may revert to old configuration when waiting for the acknowledgement from layer 2 for SECURITY MODE COMPLETE message, and it has to act accordingly. + +### 7.16.1.2.3 Reception of SECURITY MODE COMMAND message by the MS + +Upon reception of the SECURITY MODE COMMAND message, the MS shall : + +- 1> if neither IE "*Ciphering Mode Info*" nor IE "*Integrity Protection Mode Info*" is included in the SECURITY MODE COMMAND: + +- 2> set the variable INVALID\_CONFIGURATION to TRUE. +- 1> if the IE "*Security Capability*" is the same as indicated by variable MS\_CAPABILITY\_TRANSFERRED, and the IE "*GSM MS Security Capability*" (if included in the SECURITY MODE COMMAND message) is the same as indicated by the variable MS\_CAPABILITY\_TRANSFERRED: + - 2> set the variable LATEST\_CONFIGURED\_CN\_DOMAIN equal to the IE "*CN Domain Identity*"; + - 2> set the IE "*Status*" in the variable SECURITY\_MODIFICATION message for the CN domain indicated in the IE "*CN domain identity*" in the received SECURITY MODE COMMAND message to the value "Affected"; + - 2> set the IE "*Status*" in the variable SECURITY\_MODIFICATION for all CN domains other than the CN domain indicated in the IE "*CN Domain Identity*" to "Not affected"; + - 2> set the IE "*RRC Transaction Identifier*" in the SECURITY MODE COMPLETE message to the value of "RRC transaction identifier" in the entry for the SECURITY MODE COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 2> clear that entry; + - 2> if the SECURITY MODE COMMAND message contained the IE "*Ciphering Mode Info*": + - 3> perform the actions as specified in sub-clause 7.19.4.4 "*Ciphering mode info*". + - 2> if the SECURITY MODE COMMAND message contained the IE "*Integrity Protection Mode Info*": + - 3> perform the actions as specified in sub-clause 7.19.4.5 "*Integrity Protection Mode Info*". +- 1> Prior to sending the SECURITY MODE COMPLETE message the MS shall: + - 2> use the old ciphering configuration for this message; + - 2> if the SECURITY MODE COMMAND message contains the IE "*Ciphering Mode Info*": + - 3> include and set the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" to the value of the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO. + - 3> for each radio bearer and signalling radio bearer that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN: + - 4> start or continue incrementing the COUNT-C values for all RLC-AM and RLC-UM signalling radio bearers at the ciphering activation time as specified in the Ciphering mode info procedure (see sub-clause 7.19.4.4); + - 4> start or continue incrementing the COUNT-C values common for all transparent mode radio bearers for this CN domain at the ciphering activation time as specified in the Ciphering mode info procedure (see sub-clause 7.19.4.4); + - 4> continue incrementing the COUNT-C values for all RLC-AM and RLC-UM radio bearers; + - 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers (see 3GPP TS 33.102) for the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN: + - 4> for ciphering on signalling radio bearers using RLC-AM and RLC-UM in the downlink, at the RLC sequence number indicated in IE "*RB Downlink Ciphering Activation Time Info*" in the IE "*Ciphering Mode Info*" included in the SECURITY MODE COMMAND message, for each signalling radio bearer: + - pp)5> set the 20 most significant bits of the HFN component of the downlink COUNT-C to the value "START" in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + - qq)5> set the remaining bits of the hyper frame numbers to zero; + +- 3> if new keys have been received perform the actions in sub-clause 7.16.1.2.3.1. +- 2> if the SECURITY MODE COMMAND message contained the IE "*Integrity Protection Mode Info*"; + - 3> include and set the IE "*Uplink Integrity Protection Activation Info*" to the value of the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO for each signalling radio bearer; + - 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers (see 3GPP TS 33.102) for the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN, for SRB2: + - 4> in the downlink, for the received SECURITY MODE COMMAND message : + - rr) 5> set the 20 most significant bits of the IE "*Downlink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the downlink COUNT-I to the value "START" in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + - ss) 5> set the remaining bits of the IE "*Downlink RRC HFN*" to zero; + - 4> in the uplink, for the transmitted response message, SECURITY MODE COMPLETE message: + - tt) 5> set the 20 most significant bits of the IE "*Uplink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the uplink COUNT-I to the value "START" in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + - uu) 5> set the remaining bits of the IE "*Uplink RRC HFN*" to zero; + - 3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers (3GPP TS 33.102) for the CN domain indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN, the MS shall for each signalling radio bearer other than SRB2: + - 4> if the IE "*Integrity Protection Mode Command*" has the value "start": + - vv) 5> in the downlink, for this signalling radio bearer, set the 20 most significant bits of IE "*Downlink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the downlink COUNT-I to the value START transmitted in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + - ww) 5> set the remaining bits of the IE "*Downlink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the downlink COUNT-I to zero; + - 4> else: + - xx) 5> in the downlink, for the first message for which the RRC sequence number in a received RRC message for this signalling radio bearer is equal to or greater than the activation time as indicated in IE "*Downlink Integrity Protection Activation Info*" as included in the IE "*Integrity Protection Mode Info*": + - 6> for this signalling radio bearer, set the 20 most significant bits of the IE "*Downlink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the downlink COUNT-I to the value "START" in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + - 6> set the remaining bits of the IE "*Downlink RRC HFN*" to zero; + - 3> if new keys have been received perform the actions in sub-clause 7.16.1.2.3.1; +- 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer SRB2 from and including the transmitted SECURITY MODE COMPLETE message; + +2> transmit the SECURITY MODE COMPLETE message on the uplink SRB2. + +After submission of the SECURITY MODE COMPLETE message to the lower layers, the MS shall accept messages received in the DL which require the new security configuration to be applied on them. If a received message is successfully integrity checked, the MS shall not discard the message due to lack of completion of the security procedure caused by the successful delivery of the SECURITY MODE COMPLETE message not having been confirmed by lower layers yet, unless the security configuration to be applied has been aborted and the message received requires integrity protection (see 3GPP TS 24.008). + +1> when the successful delivery of the SECURITY MODE COMPLETE message has been confirmed by RLC: + +2> if the SECURITY MODE COMMAND message contained the IE "*Ciphering Mode Info*": + +3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers (see 3GPP TS 33.102) for the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN: + +4> for ciphering on signalling radio bearers using RLC-AM and RLC-UM in the uplink, at the RLC sequence number indicated in IE "*Radio Bearer Uplink Ciphering Activation Time Info*" included in the SECURITY MODE COMPLETE message, for each signalling radio bearer: + +yy) 5> set the HFN component of the uplink COUNT-C to the value "START" in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN. + +zz) 5> set the remaining bits of the hyper frame numbers to zero; + +3> if new keys have been received perform the actions in sub-clause 7.16.1.2.3.1. + +3> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; + +3> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + +3> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO. + +2> if the SECURITY MODE COMMAND message contains the IE "*Integrity protection mode info*": + +3> if no new security key set (new ciphering and integrity protection keys) has been received from the upper layers (see 3GPP TS 33.102) for the CN domain indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN, the MS shall for each signalling radio bearer other than SRB2: + +4> if the IE "*Integrity Protection Mode Command*" has the value "start": + +aaa) 5> in the uplink, for this signalling radio bearer, set the 20 most significant bits of IE "*Uplink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the uplink COUNT-I to the value START transmitted in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + +bbb) 5> set the remaining bits of the IE "*Uplink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the uplink COUNT-I to zero; + +4> else: + +ccc) 5> in the uplink, for the first transmitted RRC message for this signalling radio bearer with RRC sequence number equal to the activation time as indicated in IE "*Uplink Integrity Protection Activation Info*" included in the transmitted SECURITY MODE COMPLETE message: + +6> for this signalling radio bearer, set the 20 most significant bits of the IE "*Uplink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the uplink COUNT-I to the value "START" in the most recently transmitted IE "*START List*" or IE "*START*", at the reception of the SECURITY MODE COMMAND message, that belongs to the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; + +- 6> set the remaining bits of the IE "*Uplink RRC HFN*" to zero; +- 3> if new keys have been received perform the actions in sub-clause 7.16.1.2.3.1; +- 3> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; +- 3> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and +- 3> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO. +- 2> clear the variable SECURITY\_MODIFICATION; +- 2> notify upper layers upon change of the security configuration; +- 2> and the procedure ends. +- 1> if the IE "*Security Capability*" is not the same as indicated by the variable MS\_CAPABILITY\_TRANSFERRED, or the IE "*GSM MS Security Capability*" (if included in the SECURITY MODE COMMAND message) is not the same as indicated by the variable MS\_CAPABILITY\_TRANSFERRED, or if the IE "*GSM MS Security Capability*" is not included in the SECURITY MODE COMMAND message and is included in the variable MS\_CAPABILITY\_TRANSFERRED: + - 2> release all its radio resources; + - 2> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED\_RABS) to upper layers; + - 2> clear the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + - 2> clear the variable ESTABLISHED\_RABS; + - 2> clear the variable SECURITY\_MODIFICATION; + - 2> enter RRC-Idle mode; + - 2> perform actions when entering RRC-Idle mode as specified in sub-clause 7.18 "Actions when entering RRC-Idle mode from RRC-Connected mode"; + - 2> and the procedure ends. + +#### 7.16.1.2.3.1 New ciphering and integrity protection keys + +The actions in this sub-clause are to be performed only if the new keys were received for an on-going signalling connection while in GERAN *Iu mode*. + +If a new security keyset (new ciphering and integrity protection keys) has been received from the upper layers (see 3GPP TS 33.102) for the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN, the MS shall: + +- 1> set the START value for the CN domain indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN to zero; +- 1> if the SECURITY MODE COMMAND message contained the IE "*Integrity Protection Mode Info*": + - 2> for integrity protection in the downlink on each signalling radio bearer except SRB2: + - 3> if IE "*Integrity Protection Mode Command*" has the value "start": + - 4> for the first received message on this signalling radio bearer: + - ddd) 5> start using the new integrity key; + - eee) 5> for this signalling radio bearer, set the IE "*Downlink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the downlink COUNT-I to zero. + - 3> else: + +- 4> for the first message for which the RRC sequence number in a received RRC message for this signalling radio bearer is equal to or greater than the activation time as indicated in IE "*Downlink Integrity Protection Activation Info*" as included in the IE "*Integrity Protection Mode Info*": + - fff) 5> start using the new integrity key; + - ggg) 5> for this signalling radio bearer, set the IE "*Downlink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the downlink COUNT\_I to zero. +- 2> for integrity protection in the uplink on each signalling radio bearer except SRB2: + - 3> for the first message for which the RRC sequence number in a to be transmitted RRC message for this signalling radio bearer is equal to the activation time as indicated in IE "*Uplink Integrity Protection Activation Info*" included in the transmitted SECURITY MODE COMPLETE message: + - 4> start using the new integrity key; + - 4> for this signalling radio bearer, set the IE "*Uplink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the uplink COUNT-I to zero. +- 2> for integrity protection in the downlink on signalling radio bearer SRB2: + - 3> at the received SECURITY MODECOMMAND: + - 4> start using the new integrity key; + - 4> set the IE "*Downlink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the downlink COUNT-I to zero; +- 2> for integrity protection in the uplink on signalling radio bearer SRB2 : + - 3> at the transmitted SECURITY MODE COMPLETE: + - 4> start using the new integrity key; + - 4> set the IE "*Uplink RRC HFN*" in the variable INTEGRITY\_PROTECTION\_INFO of the uplink COUNT-I to zero; +- 1> if the SECURITY MODE COMMAND message contained the IE "*Ciphering Mode Info*": + - 2> for each signalling radio bearer and for each radio bearer for the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN: + - 3> if the IE "*Status*" in the variable CIPHERING\_STATUS has the value "Started" for this CN domain, then for ciphering on the radio bearer using RLC-TM: + - 4> at the TDMA frame number as indicated in the IE "*Ciphering Activation Time for DBPSCH*" in the IE "*Ciphering Mode Info*"; + - hhh) 5> start using the new key in uplink and downlink; + - iii) 5> set the HFN component of the COUNT-C to zero. + - 3> if the IE "*Status*" in the variable CIPHERING\_STATUS has the value "Started" for this CN domain, then for ciphering on the radio bearers and signalling radio bearers using RLC-AM and RLC-UM: + - 4> in the downlink, at the RLC sequence number indicated in IE "*RB Downlink Ciphering Activation Time Info*" in the IE "*Ciphering Mode Info*": + - jjj) 5> start using the new key; + - kkk) 5> set the HFN component of the downlink COUNT-C to zero. + - 4> in the uplink, at and after the RLC sequence number indicated in IE "*Radio Bearer Uplink Ciphering Activation Time Info*": + - lll) 5> start using the new key; + +mmm) 5> set the HFN component of the uplink COUNT-C to zero. + +1> consider the value of the latest transmitted START value to be zero. + +#### 7.16.1.2.4 Incompatible simultaneous security reconfiguration + +If the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION becomes set to TRUE of the received SECURITY MODE COMMAND message, the MS shall: + +1> transmit a SECURITY MODE FAILURE message on the uplink SRB2, using the ciphering and integrity protection configurations prior to the reception of this SECURITY MODE COMMAND; + +1> set the IE "*RRC Transaction Identifier*" in the SECURITY MODE FAILURE message to the value of "RRC transaction identifier" in the entry for the SECURITY MODE COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and + +1> clear that entry; + +1> set the IE "*Failure Cause*" to the cause value "incompatible simultaneous reconfiguration"; + +1> when the response message has been submitted to lower layers for transmission: + +2> set the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION to FALSE; + +2> continue with any ongoing processes and procedures as if the invalid SECURITY MODE COMMAND message has not been received; + +2> only accept a message on SRB 2, with a COUNT-I that: + +3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and + +3> not take into account the HFN from the received SECURITY MODE COMMAND message. + +1> and the procedure ends. + +#### 7.16.1.2.5 Cell Update procedure during security reconfiguration + +If: + +- a cell update procedure according to sub-clause 7.6.1 is initiated; and +- the received SECURITY MODE COMMAND message causes, +- the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to be set to TRUE; and/or +- the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to be set to TRUE: + +the MS shall: + +1> abort the ongoing integrity and/or ciphering reconfiguration; + +1> resume data transmission on any suspended radio bearer and signalling radio bearer mapped on RLC-AM or RLC-UM; + +1> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; + +1> when the CELL UPDATE message has been submitted to lower layers for transmission: + +2> if the SECURITY MODE COMMAND message contained the IE "*Ciphering Mode Info*": + +3> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE; and + +3> clear the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; + +2> if the SECURITY MODE COMMAND message contained the IE "*Integrity Protection Mode Info*": + +3> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to FALSE; and + +- 3> clear the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO. +- 2> continue with any ongoing processes and procedures as if the SECURITY MODE COMMAND message had not been received; +- 2> only accept a message on SRB 2, with a COUNT-I that: + - 3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and + - 3> does not take into account the HFN from the received SECURITY MODE COMMAND message. +- 2> if the MS has already submitted the SECURITY MODE COMPLETE message, use a COUNT-I value for transmission of the next message on SRB2 as stated below: + - 3> take the COUNT-I used prior to the transmission of the SECURITY MODE COMPLETE message; + - 3> increment that COUNT-I with 2; + - 3> apply that COUNT-I on the next message to transmit. +- 2> clear the variable SECURITY\_MODIFICATION; +- 2> the procedure ends. + +#### 7.16.1.2.6 Invalid configuration + +If the variable INVALID\_CONFIGURATION is set to TRUE due to the received SECURITY MODE COMMAND message, the MS shall: + +- 1> transmit a SECURITY MODE FAILURE message on the uplink SRB2 after setting the IEs as specified below; + - 1> set the IE "*RRC Transaction Identifier*" in the SECURITY MODE FAILURE message to the value of "RRC transaction identifier" in the entry for the SECURITY MODE COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and + - 1> clear that entry; + - 1> set the IE "*Failure Cause*" to the cause value "invalid configuration". +- 1> when the response message has been submitted to lower layers for transmission: + - 2> set the variable INVALID\_CONFIGURATION to FALSE; + - 2> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to FALSE + - 2> continue with any ongoing processes and procedures as if the invalid SECURITY MODE COMMAND message has not been received; + - 2> only accept a message on SRB 2, with a COUNT-I that: + - 3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and + - 3> not take into account the HFN from the received SECURITY MODE COMMAND message. +- 1> and the procedure ends. + +#### 7.16.1.2.7 Reception of SECURITY MODE COMPLETE message by the GERAN + +The GERAN shall apply integrity protection on the received SECURITY MODE COMPLETE message and all subsequent messages with the new integrity protection configuration, if changed. When GERAN has received a SECURITY MODE COMPLETE message and the integrity protection has successfully been applied, GERAN shall: + +- 1> if the IE "*Ciphering Mode Info*" was included in the SECURITY MODE COMMAND message: + +- 2> if new keys were received for the CN domain set in the IE "*CN Domain Identity*" in the SECURITY MODE COMMAND: + - 3> at the downlink and uplink activation time set all the bits of the hyper frame numbers of the downlink and uplink COUNT-C values respectively for all radio bearers for this CN domain and all signalling radio bearers to zero; +- 2> else (if new keys were not received) + - 3> at the downlink and uplink activation time use the value "START" in the most recently received IE "*START List*" or IE "*START*" that belongs to the CN domain as indicated in the IE "*CN Domain Identity*" to initialise all hyper frame numbers of the downlink and uplink COUNT-C values respectively for all the signalling radio bearers by: + - 4> setting the 20 most significant bits of the hyper frame numbers of the COUNT-C for all signalling radio bearers to the value "START" in the most recently received IE "*START List*" or IE "*START*" for that CN domain; + - 4> setting the remaining bits of the hyper frame numbers equal to zero. +- 1> if the IE "*Integrity Protection Mode Info*" was included in the SECURITY MODE COMMAND message: + - 2> if this was not the first SECURITY MODE COMMAND message for this RRC connection: + - 3> if new keys have been received for the CN domain set in the IE "*CN Domain Identity*" included in the transmitted SECURITY MODE COMMAND message: + - 4> at the downlink and uplink activation time initialise all hyper frame numbers of the downlink and uplink COUNT-I values respectively for all the signalling radio bearers other than SRB2 as follows: + - nnn) 5> set all bits of the hyper frame numbers of the uplink and downlink COUNT-I to zero; + - 3> if no new keys have been received for the CN domain set in the IE "*CN Domain Identity*" included in the transmitted SECURITY MODE COMMAND message: + - 4> at the downlink and uplink activation time use the value "START" in the most recently received IE "*START List*" or IE "*START*" that belongs to the CN domain as indicated in the IE "*CN Domain Identity*" to initialise all hyper frame numbers of the downlink and uplink COUNT-I values respectively for all the signalling radio bearers other than SRB2 by: + - ooo) 5> setting the 20 most significant bits of the hyper frame numbers of the downlink and uplink COUNT-I respectively for all signalling radio bearers to the value "START" in the most recently received IE "*START List*" or IE "*START*" for that CN domain; + - ppp) 5> setting the remaining bits of the hyper frame numbers equal to zero. + - 1> send an indication to upper layers that the new integrity protection configuration has been activated; + - 1> resume in the downlink, all suspended radio bearers and all signalling radio bearers; + - 1> allow the transmission of RRC messages on all signalling radio bearers with any RRC SN; + - 1> if the IE "*Integrity Protection Mode Command*" included in the SECURITY MODE COMMAND had the value "Start": + - 2> start applying integrity protection in the downlink for all signalling radio bearers; + - 1> if the IE "*Integrity Protection Mode Command*" included in the SECURITY MODE COMMAND had the value "Modify": + - 2> start applying the new integrity protection configuration in the downlink at the RRC sequence number, for each signalling radio bearers SRBn, except for signalling radio bearer SRB2, indicated by the entry for signalling radio bearer n in the "RRC message sequence number list" in the IE "*Downlink Integrity Protection Activation Info*"; + +- 2> continue applying the new integrity configuration for signalling radio bearer SRB2; +- 2> apply the new integrity protection configuration on the received signalling messages with RRC SN greater than or equal to the number associated with the signalling radio bearer in IE "*Uplink Integrity Protection Activation Info*"; +- 1> apply the old ciphering configuration for the transmission of RLC PDUs with RLC sequence number less than the number indicated in the IE "*RB Downlink Ciphering Activation Time Info*" included in the IE "*Ciphering Mode Info*"; +- 1> apply the new ciphering configuration for the transmission of RLC PDUs with RLC sequence number greater than or equal to the number indicated in IE "*Radio Bearer Downlink Ciphering Activation Time Info*" included in the IE "*Ciphering Mode Info*"; +- 1> apply the old integrity protection configuration on the received signalling messages with RRC SN smaller than the number associated with the signalling radio bearer in IE "*Uplink Integrity Protection Activation Info*"; +- 1> for radio bearers and signalling radio bearers using RLC-AM or RLC-UM: + - 2> send an indication to lower layers: + - 2> use the old ciphering configuration for received RLC PDUs with RLC sequence number less than the RLC sequence number indicated in the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" sent by the MS; + - 2> use the new ciphering configuration for received RLC PDUs with RLC sequence number greater than or equal to the RLC sequence number indicated in the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" sent by the MS; + - 2> if an RLC reset or re-establishment occurs after the SECURITY MODE COMPLETE message has been received by GERAN before the activation time for the new ciphering configuration has been reached, ignore the activation time and apply the new ciphering configuration immediately after the RLC reset or RLC re-establishment; +- 1> for radio bearers using RLC-TM: + - 2> send an indication to lower layers: + - 2> use the old ciphering configuration for the received RLC PDUs before the TDMA frame number as indicated in the IE "*Ciphering Activation Time for DBPSCH*" in the IE "*Ciphering Mode Info*" as included in the SECURITY MODE COMMAND; + - 2> use the new ciphering configuration for the received RLC PDUs at the TDMA frame number as indicated in the IE "*Ciphering Activation Time for DBPSCH*" in the IE "*Ciphering Mode Info*" as included in the SECURITY MODE COMMAND; +- 1> and the procedure ends. + +#### 7.16.1.2.8 Invalid SECURITY MODE COMMAND message + +If the SECURITY MODE COMMAND message contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to sub-clause "General error handling", the MS shall perform procedure specific error handling as follows: + +- 1> transmit a SECURITY MODE FAILURE message on the uplink SRB2; +- 1> set the IE "*RRC Transaction Identifier*" in the SECURITY MODE FAILURE message to the value of "*RRC transaction identifier*" in the entry for the SECURITY MODE COMMAND message in the table "Rejected transactions" in the variable TRANSACTIONS; and +- 1> clear that entry; +- 1> set the IE "*Failure Cause*" to the cause value "protocol error"; +- 1> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION. + +- 1> when the response message has been submitted to lower layers for transmission: + - 2> continue with any ongoing processes and procedures as if the invalid SECURITY MODE COMMAND message has not been received; +- 2> only accept a message on SRB 2, with a COUNT-I that: + - 3> is higher than the COUNT-I used prior to receiving the SECURITY MODE COMMAND message incremented by one; and + - 3> not take into account the HFN from the received SECURITY MODE COMMAND message; +- 1> and the procedure ends. + +## 7.17 Delivery of Non-Access stratum messages + +### 7.17.1 Initial Direct transfer + +![Sequence diagram showing the Initial Direct Transfer in the uplink, normal flow. The diagram consists of two vertical lifelines: MS (Mobile Station) on the left and GERAN (GSM EDGE Radio Access Network) on the right. A horizontal arrow labeled 'INITIAL DIRECT TRANSFER' points from the MS lifeline to the GERAN lifeline. Vertical lines extend downwards from both boxes, indicating the timeline of the procedure.](0de91e9b714369b312bf3ab1853301ac_img.jpg) + +Sequence diagram showing the Initial Direct Transfer in the uplink, normal flow. The diagram consists of two vertical lifelines: MS (Mobile Station) on the left and GERAN (GSM EDGE Radio Access Network) on the right. A horizontal arrow labeled 'INITIAL DIRECT TRANSFER' points from the MS lifeline to the GERAN lifeline. Vertical lines extend downwards from both boxes, indicating the timeline of the procedure. + +**Figure 7.17.1.1: Initial Direct transfer in the uplink, normal flow** + +#### 7.17.1.1 General + +The Initial Direct Transfer procedure is used in the uplink to establish a signalling connection. It is also used to carry an initial upper layer (NAS) messages over the radio interface. + +#### 7.17.1.2 Initiation of Initial direct transfer procedure in the MS + +In the MS, the Initial Direct Transfer procedure shall be initiated, when the upper layers request establishment of a signalling connection. This request also includes a request for the transfer of a NAS message. + +Upon initiation of the Initial Direct Transfer procedure when the MS is in RRC-Idle mode, the MS shall: + +- 1> set the variable ESTABLISHMENT\_CAUSE to the cause for establishment indicated by upper layers; +- 1> perform an RRC Connection Establishment procedure, according to sub-clause 7.5; +- 1> if the RRC Connection Establishment procedure was not successful: + - 2> indicate failure to establish the signalling connection to upper layers and end the procedure; +- 1> when the RRC Connection Establishment procedure is completed successfully: + - 2> continue with the Initial Direct Transfer procedure as below; + +Upon initiation of the Initial Direct Transfer procedure when the MS is in RRC-GRA\_PCH state, the MS shall: + +- 1> perform a Cell Update procedure, according to sub-clause 7.8, using the cause "uplink data transmission"; +- 1> when the Cell Update procedure completed successfully: + - 2> continue with the Initial Direct Transfer procedure as below. + +The MS shall, in the INITIAL DIRECT TRANSFER message: + +- 1> set the IE "*NAS Message*" as received from upper layers; and +- 1> set the IE "*CN Domain Identity*" as indicated by the upper layers; and +- 2> set the IE "*Intra Domain NAS Node Selector*" as follows: +- 2> derive the IE "*Intra Domain NAS Node Selector*" from TMSI/PTMSI, IMSI, or IMEI; and +- 2> provide the coding of the IE "*Intra Domain NAS Node Selector*" according to the following priorities: + - 1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a valid TMSI/PTMSI is available; + - 2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available; + - 3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the MS. +- 1> calculate the START according to sub-clause 7.18.4 for the CN domain as set in the IE "*CN Domain Identity*"; and +- 2> include the calculated START value for that CN domain in the IE "*START*"; + +The MS shall: + +- 1> transmit the INITIAL DIRECT TRANSFER message on the uplink using AM RLC on signalling radio bearer SRB 3; +- 1> when the INITIAL DIRECT TRANSFER message has been submitted to lower layers for transmission: + - 2> confirm the establishment of a signalling connection to upper layers; and + - 2> add the signalling connection with the identity indicated by the IE "*CN Domain Identity*" in the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; and +- 1> when the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC sub-layer: + - 2> the procedure ends. + +When not stated otherwise elsewhere, the MS may also initiate the initial direct transfer procedure when another procedure is ongoing, and in that case the state of the latter procedure shall not be affected. + +A new signalling connection request may be received from upper layers subsequent to the indication of the release of a previously established signalling connection to upper layers. From the time of the indication of release to upper layers until the MS has entered RRC-Idle mode, any such upper layer request to establish a new signalling connection shall be queued. This request shall be processed after the MS has entered RRC-Idle mode. + +### 7.17.1.3 RLC re-establishment, inter-mode handover or inter-RAT change + +If a re-establishment of RLC on SRB3 occurs before the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC, the MS shall: + +- 1> retransmit the INITIAL DIRECT TRANSFER message on the uplink using SRB3. + +If inter-mode handover occurs before the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC, for messages with the IE "*CN Domain Identity*" set to "CS domain", the MS shall: + +- 1> retransmit the NAS message as specified in sub-clause 7.8.4.4 + +If inter-RAT handover occurs before the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC, the MS shall: + +- 1> retransmit the NAS message as specified in sub-clause 7.10.4. + +### 7.17.1.4 Abortion of signalling connection establishment + +If the MS receives a request from upper layers to release (abort) the signalling connection for the CN domain for which the initial direct transfer procedure is ongoing, the MS shall: + +- 1) if the MS has not yet entered GERAN RRC-Connected mode: + - 2) abort the RRC Connection Establishment procedure as specified in sub-clause 7.5.1.6; + +the procedure ends. + +### 7.17.1.5 Reception of INITIAL DIRECT TRANSFER message by the GERAN + +On reception of the INITIAL DIRECT TRANSFER message the NAS message should be routed using the IE "*CN Domain Identity*". GERAN may also use the IE "*Intra Domain NAS Node Selector*" for routing among the CN nodes for the addressed CN domain. + +If no signalling connection exists towards the chosen node, then a signalling connection is established. + +When the GERAN receives an INITIAL DIRECT TRANSFER message, it shall not affect the state of any other ongoing RRC procedures, when not stated otherwise elsewhere. + +The GERAN should: + +- 1) set the START value for the CN domain indicated in the IE "*CN Domain Identity*" to the value of the IE "*START*". + +## 7.17.2 Downlink Direct transfer + +![Sequence diagram showing Downlink Direct transfer from GERAN to MS. The diagram consists of two vertical lifelines labeled MS and GERAN. A horizontal arrow labeled 'DOWNLINK DIRECT TRANSFER' points from the GERAN lifeline to the MS lifeline.](faeab87eabc08d09a83cac8f66d1c126_img.jpg) + +``` + +sequenceDiagram + participant GERAN + participant MS + Note right of GERAN: DOWNLINK DIRECT TRANSFER + GERAN->>MS: DOWNLINK DIRECT TRANSFER + +``` + +Sequence diagram showing Downlink Direct transfer from GERAN to MS. The diagram consists of two vertical lifelines labeled MS and GERAN. A horizontal arrow labeled 'DOWNLINK DIRECT TRANSFER' points from the GERAN lifeline to the MS lifeline. + +Figure 7.17.2.1: Downlink Direct transfer, normal flow + +### 7.17.2.1 General + +The Downlink Direct Transfer procedure is used in the downlink direction to carry upper layer (NAS) messages over the radio interface. + +### 7.17.2.2 Initiation of downlink direct transfer procedure in the GERAN + +In the GERAN, the Direct Transfer procedure is initiated when the upper layers request the transfer of a NAS message after the initial signalling connection is established. The GERAN may also initiate the Downlink Direct Transfer procedure when another RRC procedure is ongoing, and in that case the state of the latter procedure shall not be affected. The GERAN shall transmit the DOWNLINK DIRECT TRANSFER message on the downlink using AM RLC on signalling radio bearer SRB 3 or signalling radio bearer SRB 4. The GERAN should: + +- 1) if upper layers indicate "low priority" for this message: + - 2) select signalling radio bearer SRB4, if available. Specifically, for a GSM-MAP based CN, signalling radio SRB4 should, if available, be selected when "SAPI 3" is requested; + - 2) select signalling radio SRB3 when signalling radio SRB 4 is not available; +- 1) if upper layers indicate "high priority" for this message: + +2> select signalling radio SRB3. Specifically, for a GSM-MAP based CN, signalling radio bearer RB3 should be selected when "SAPI 0" is requested. + +The GERAN sets the IE "*CN Domain Identity*" to indicate, which CN domain the NAS message is originated from. + +### 7.17.2.3 Reception of a DOWNLINK DIRECT TRANSFER message by the MS + +Upon reception of the DOWNLINK DIRECT TRANSFER message, the MS RRC shall, using the IE "*CN Domain Identity*", route the contents of the IE "*NAS Message*" and the value of the IE "*CN Domain Identity*" to the upper layers. + +The MS shall clear the entry for the DOWNLINK DIRECT TRANSFER message in the table "Accepted transactions" in the variable TRANSACTIONS. + +When the MS receives a DOWNLINK DIRECT TRANSFER message, it shall not affect the state of any other ongoing RRC procedures when not stated otherwise elsewhere. + +### 7.17.2.4 No signalling connection exists + +If the MS receives a DOWNLINK DIRECT TRANSFER message, and the signalling connection identified with the IE "*CN Domain Identity*" does not exist according to the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS, the MS shall: + +- 1> ignore the content of the DOWNLINK DIRECT TRANSFER message; +- 1> transmit an RRC STATUS message on the uplink SRB2; +- 1> include the IE "*Identification of Received Message*"; and +- 1> set the IE "*Received Message Type*" to DOWNLINK DIRECT TRANSFER message; and +- 1> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the DOWNLINK DIRECT TRANSFER message in the table "Accepted transactions" in the variable TRANSACTIONS; and +- 1> clear that entry; +- 1> include the IE "*Protocol Error Information*" with the IE "*Protocol Error Cause*" set to "Message not compatible with receiver state". + +When the RRC STATUS message has been submitted to lower layers for transmission, the MS shall: + +- 1> continue with any ongoing processes and procedures as if the DOWNLINK DIRECT TRANSFER message has not been received. + +### 7.17.2.5 Invalid DOWNLINK DIRECT TRANSFER message + +If the MS receives a DOWNLINK DIRECT TRANSFER message, which contains a protocol error causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE according to clause 8 the MS shall perform procedure specific error handling as follows: + +- 1> transmit an RRC STATUS message on the uplink SRB2; +- 1> include the IE "*Identification of Received Message*"; and +- 1> set the IE "*Received Message Type*" to DOWNLINK DIRECT TRANSFER; and +- 1> set the IE "*RRC Transaction Identifier*" to the value of "RRC transaction identifier" in the entry for the DOWNLINK DIRECT TRANSFER message in the table "Rejected transactions" in the variable TRANSACTIONS; and +- 1> clear that entry; +- 1> include the IE "*Protocol Error Information*" with contents set to the value of the variable PROTOCOL\_ERROR\_INFORMATION. + +When the RRC STATUS message has been submitted to lower layers for transmission, the MS shall: + +1> continue with any ongoing processes and procedures as if the invalid DOWNLINK DIRECT TRANSFER message has not been received. + +### 7.17.3 Uplink Direct transfer + +![Sequence diagram showing Uplink Direct transfer from MS to GERAN. The MS box is on the left and the GERAN box is on the right. A horizontal arrow labeled 'UPLINK DIRECT TRANSFER' points from the MS box to the GERAN box. Vertical lines extend downwards from both boxes.](886af5e2ffd5d8f11079c547675cf882_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GERAN + Note left of MS: Uplink Direct transfer procedure initiated + MS->>GERAN: UPLINK DIRECT TRANSFER + Note right of GERAN: Message received + +``` + +Sequence diagram showing Uplink Direct transfer from MS to GERAN. The MS box is on the left and the GERAN box is on the right. A horizontal arrow labeled 'UPLINK DIRECT TRANSFER' points from the MS box to the GERAN box. Vertical lines extend downwards from both boxes. + +Figure 7.17.3.1: Uplink Direct transfer, normal flow + +#### 7.17.3.1 General + +The Uplink Direct Transfer procedure is used in the uplink direction to carry all subsequent upper layer (NAS) messages over the radio interface belonging to a signalling connection. + +#### 7.17.3.2 Initiation of uplink direct transfer procedure in the MS + +In the MS, the Uplink Direct Transfer procedure shall be initiated when the upper layers request a transfer of a NAS message on an existing signalling connection. When not stated otherwise elsewhere, the MS may initiate the Uplink Direct Transfer procedure when another procedure is ongoing, and in that case the state of the latter procedure shall not be affected. + +Upon initiation of the Uplink Direct Transfer procedure in RRC-GRA\_PCH state, the MS shall: + +- 1> perform a Cell Update procedure, according to sub-clause 7.8, using the cause "uplink data transmission"; +- 1> when the Cell Update procedure has been completed successfully: + - 2> continue with the Uplink Direct Transfer procedure as below. + +The MS shall transmit the UPLINK DIRECT TRANSFER message on the uplink using AM RLC on signalling radio bearer SRB3 or signalling radio bearer SRB4. The MS shall: + +- 1> if upper layers indicates "low priority" for this message: + - 2> select signalling radio SRB4, if available. Specifically, for a GSM-MAP based CN, signalling radio bearer SRB4 shall, if available, be selected when "SAPI 3" is requested; + - 2> select signalling radio bearer SRB3 when signalling radio bearer SRB4 is not available; +- 1> if upper layers indicates "high priority" for this message: + - 2> select signalling radio bearer SRB3. Specifically, for a GSM-MAP based CN, signalling radio bearer SRB3 shall be selected when "SAPI 0" is requested. + +The MS shall set the IE "*NAS Message*" as received from upper layers and set the IE "*CN Domain Identity*" as indicated by the upper layers. + +When the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC sub-layer the procedure ends. + +#### 7.17.3.3 RLC re-establishment, inter-mode handover or inter-RAT change + +If SRB n (where n equals to 3 or 4) was used when transmitting the UPLINK DIRECT TRANSFER message and a re-establishment of RLC on the same SRB n occurs before the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, the MS shall: + +1> retransmit the UPLINK DIRECT TRANSFER message on the uplink SRB n. + +If inter-mode handover occurs before the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, for messages with the IE "CN Domain Identity" set to "CS domain", the MS shall: + +1> retransmit the NAS message as specified in sub-clause 7.8.4.4 + +If inter-RAT handover occurs before the successful delivery of the UPLINK DIRECT TRANSFER message has been confirmed by RLC, the MS shall: + +1> retransmit the NAS message as specified in sub-clause 7.10.4. + +### 7.17.3.4 Reception of UPLINK DIRECT TRANSFER message by the GERAN + +On reception of the UPLINK DIRECT TRANSFER message the NAS message should be routed using the value indicated in the IE "*CN Domain Identity*". + +When the GERAN receives an UPLINK DIRECT TRANSFER message, it shall not affect the state of any other ongoing RRC procedures, when not stated otherwise elsewhere. + +## 7.18 General procedures + +### 7.18.1 Selection of initial MS identity + +The purpose of the IE "*Initial MS Identity*" is to provide a unique MS identification at the establishment of an RRC connection. The MS shall choose "MS id type" in the IE "*Initial MS Identity*" with the following priority: + +1. TMSI (GSM-MAP): The TMSI (GSM-MAP) shall be chosen if available. The IE "*LAT*" in the IE "*Initial MS Identity*" shall also be present when TMSI (GSM-MAP) is used. +2. P-TMSI (GSM-MAP): The P-TMSI (GSM-MAP) shall be chosen if available and no TMSI (GSM-MAP) is available. The IE "*RAT*" in the IE "*Initial MS Identity*" shall in this case also be present when P-TMSI (GSM-MAP) is used. +3. IMSI (GSM-MAP): The IMSI (GSM-MAP) shall be chosen if no TMSI (GSM-MAP) or P-TMSI is available. +4. IMEI: The IMEI shall be chosen when none of the above three conditions are fulfilled. + +When being used, the IEs "*TMSI (GSM-MAP)*", "*P-TMSI (GSM-MAP)*", "*IMSI (GSM-MAP)*", "*LAT*" and "*RAT*" shall be set equal to the values of the corresponding identities stored in the USIM. + +If the variable SELECTED\_PLMN in the MS indicates "ANSI-41", the MS shall choose "*MS Id Type*" in the IE "*Initial MS Identity*" according to the procedure specified in the 3GPP2 document "3GPP2 C.P0004-A". + +### 7.18.2 Actions when entering RRC-Idle mode from RRC-Connected mode + +When entering RRC-Idle mode from RRC-Connected mode, the MS shall: + +- 1> clear or set variables upon leaving GERAN RRC-Connected mode as specified in sub-clause 10.4; +- 1> attempt to select a suitable cell to camp on. + +When leaving the RRC-Connected mode according to 3GPP TS 45.010, the MS shall: + +- 1> perform cell selection. + +While camping on a cell, the MS shall: + +- 1> acquire system information according to the system information procedure in sub-clause 7.3; +- 1> perform measurements according to the measurement control procedure specified in sub-clause 7.9; and +- 1> if the MS is registered: + - 2> be prepared to receive paging messages according to the Paging procedure in sub-clause 7.4. + +If IE "*PLMN Identity*" within variable *SELECTED\_PLMN* has the value "GSM-MAP", the MS shall: + +- 1> delete any NAS system information received in RRC-Connected Mode; +- 1> acquire the NAS system information in packet system information 16; and +- 1> proceed according to sub-clause 7.19. + +When entering RRC-Idle mode, the MS shall: + +- 1> if the USIM is present, for each CN domain: + - 2> if a new security key set was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: + - 3> set the "START" value for this domain to zero; and + - 3> store this "START" value for this domain in the USIM. + - 2> else: + - 3> if the current "START" value, according to sub-clause 7.18 for a CN domain, is greater than or equal to the value "THRESHOLD" of the variable *START\_THRESHOLD*: + - 4> delete the ciphering and integrity keys that are stored in the USIM for that CN domain; + - 4> inform the deletion of these keys to upper layers. + - 3> else: + - 4> store the current "START" value for this CN domain on the USIM. +- 1> else: + - 2> if the SIM is present, for each CN domain: + - 3> if a new security key set was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: + - 4> set the "START" value for this domain to zero; and + - 4> store this "START" value for this domain in the MS. + - 3> else, the MS shall: + - 4> if the current "START" value, according to sub-clause 7.18 for this CN domain, is greater than or equal to the value "THRESHOLD" of the variable *START\_THRESHOLD*: + - qqq) 5> delete the Kc key for this CN domain; + - rrr)5> delete the ciphering and integrity keys that are stored in the MS for that CN domain; + - 5> set the "START" value for this CN domain to zero and store it in the MS; + - 5> inform the deletion of the key to upper layers. + - 4> else: + - 4> store the current "START" value for this CN domain in the MS. + +## 7.18.2a Actions when entering GERAN *A/Gb mode* or CDMA2000 from GERAN *Iu mode*, RRC- Connected mode + +When entering GERAN *A/Gb mode* or CDMA2000 from GERAN *Iu mode*, RRC- Connected mode (due to Inter-mode handover from GERAN or Inter-system handover to CDMA2000), after successful completion of the procedure causing the transition to the GERAN *A/Gb mode* or CDMA2000 from GERAN *Iu mode*, the MS shall: + +- 1> if the USIM is present, for each CN domain: + - 2> if a new security key set was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: + - 3> set the "START" value for this domain to zero and; + - 3> store this "START" value for this domain in the USIM; + - 2> else + - 3> after calculating the "START" value according to sub-clause 7.18.4, store the current "START" value for every CN domain in the USIM; +- 1> if the SIM is present, for each CN domain: + - 2> if a new security key was received for this CN domain but was not used either for integrity protection or ciphering during this RRC connection: + - 3> set the "START" value for this domain to zero and; + - 3> store this "START" value for this domain in the MS; + - 2> else + - 3> after calculating the "START" value according to sub-clause 7.18.4, store the current "START" value for this CN domain in the MS. + +### 7.18.3 Maintenance of Hyper Frame Numbers + +The MSBs of both the ciphering sequence numbers (COUNT-C) and integrity sequence numbers (COUNT-I), for the ciphering and integrity protection algorithms, respectively (see 3GPP TS 33.102), are called the Hyper Frame Numbers (HFN). For TM RLC bearers an extended TDMA frame number is used, which is built by an HFN plus part of a TDMA frame number. + +For integrity protection, the MS shall: + +- 1> maintain COUNT-I as specified in sub-clause 7.18.5; + +The following hyper frame numbers types are defined: + +- 1> MAC HFN: +11 MSB of COUNT-C for data sent over RLC TM +- 1> RLC HFN: + - 2> if the RLC sequence number is of length 7 bits(GPRS TBF mode, see 3GPP TS 44.160), then the HFN + - 3> defines the 24 MSB of the COUNT-C parameter for data sent over RLC UM, and + - 3> defines the 24 MSB of the COUNT-C parameter for data sent over RLC AM. + - 2> if the RLC sequence number is of length 11bits ( EGPRS TBF mode, see 3GPP TS 44.160), then the HFN + - 3> defines the 20 MSB of the COUNT-C parameter for data sent over RLC UM, and + - 3> defines the 20 MSB of the COUNT-C parameter for data sent over RLC AM. + - 2> if the RLC sequence number is of length 4 bits (DCCH TBF mode, see 3GPP TS 44.160), then the HFN + - 3> defines the 27 MSB of the COUNT-C parameter for data sent over RLC UM, and + - 3> defines the 27 MSB of the COUNT-C parameter for data sent over RLC AM. + - 2> if the RLC sequence number is of length 8 bits (TCH TBF mode, see 3GPP TS 44.160), then the HFN + - 3> defines the 23 MSB of the COUNT-C parameter for data sent over RLC UM, and + +- 3> defines the 23 MSB of the COUNT-C parameter for data sent over RLC AM. +- 2> if the RLC sequence number is of length 10 bits (UDCH TBF mode, see 3GPP TS 44.160), then the HFN: + - 3> defines the 21 MSB of the COUNT-C parameter for data sent over RLC AM . +- 2> if the RLC sequence number is of length 4 bits (UDCH TBF mode, see 3GPP TS 44.160), then the HFN: + - 3> defines the 27 MSB of the COUNT-C parameter for data sent over RLC UM. +- 2> if the RLC sequence number is of length 4 bits (CDCH TBF mode, see 3GPP TS 44.160), then the HFN: + - 3> defines the 27 MSB of the COUNT-C parameter for data sent over RLC AM. +- 1> RRC HFN: + - 28 MSB of COUNT-I. + +For non-transparent mode RLC radio bearers, the MS shall: + +- 1> maintain one uplink and one downlink COUNT-C per radio bearer and one uplink and one downlink COUNT-I per signalling radio bearer. + +For all transparent mode RLC signalling radio bearers and radio bearers of the same CN domain, the MS shall: + +- 1> maintain one COUNT-C, common for all signalling radio bearers and radio bearers in uplink and downlink; +- 1> if the activation time for a new ciphering configuration set by an RRC procedure is equal to zero: + - 2> apply the configured MAC HFN at this activation time, i.e. the configured HFN is not incremented; +- 1> maintain one uplink and one downlink COUNT-I per signalling radio bearer. + +## 7.18.4 START value calculation + +In RRC connected mode, if a Security Mode Command procedure has been successfully completed for a CN domain during the current RRC connection, the "START" value for that CN domain is calculated as + +Let $START_x$ = the "START" value for CN domain 'X' prior to the calculation below: + +$$START_x' = MSB_{20} ( \text{MAX} \{ \text{COUNT-C, COUNT-I} \mid \text{radio bearers and signalling radio bearers using } CK_x \text{ and } IK_x \} ) + 2.$$ + +- if $START_x' = \text{the maximum value} = 20^2 - 1 = 1048575$ then $START_x = START_x'$ ; +- if the current $START_x < START_x'$ then $START_x = START_x'$ , otherwise $START_x$ is unchanged. + +NOTE: Here, "most recently configured" means that if there are more than one key in use for a CN domain, due to non expiry of the ciphering and/or integrity protection activation time for any signalling radio bearers and/or radio bearers, do not include the COUNT-I/COUNT-C for these signalling radio bearers and/or radio bearers in the calculation of the $START_x'$ . + +COUNT-C corresponding to non-ciphered radio bearers (i.e. RBs with ciphering status set to "not started") shall not be included in the calculation of the $START_x'$ . If a radio bearer is released and the radio bearer was ciphered, the values of the COUNT-C at the time the radio bearer is released shall be taken into account in the calculation of the $START_x'$ . + +If a Security Mode Command procedure has not been successfully completed for a CN domain during the current RRC connection, the MS shall use the latest transmitted "START" value for this CN domain. + +## 7.18.5 Integrity protection + +### 7.18.5.0 General + +If the "Status" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started" then the MS and the GERAN shall: + +- 1> perform integrity protection (and integrity checking) on all RRC messages, with the following exceptions: + +RRc CONNECTION REJECT +RRc CONNECTION SETUP +RRc CONNECTION REQUEST +RRc CONNECTION SETUP COMPLETE +SYSTEM INFORMATION TYPE 5, 5bis, 5ter, 6 +SYNCHRONIZATION CHANNEL INFORMATION +RRc STATUS +EXTENDED MEASUREMENT ORDER +EXTENDED MEASUREMENT REPORT +MEASURMENT REPORT +MEASUREMENT INFORMATION +ENHANCED MEASUREMENT REPORT + +If the "Status" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Not started" then integrity protection (and integrity checking) shall not be performed on any RRc message. + +For each signalling radio bearer, the MS shall use two RRc hyper frame numbers: + +- 1> "Uplink RRc HFN"; +- 1> "Downlink RRc HFN". + +and two message sequence numbers: + +- 1> "Uplink RRc Message sequence number"; +- 1> "Downlink RRc Message sequence number". + +The above information is stored in the variable INTEGRITY\_PROTECTION\_INFO per signalling radio bearer (RB1-RB4). + +Upon the first activation of integrity protection for an RRc connection, MS and GERAN initialise the "Uplink RRc Message sequence number" and "Downlink RRc Message sequence number" for all signalling radio bearers as specified in sub-clauses 7.18.5.2 and 7.18.5.1. + +The RRc message sequence number (RRc SN) is incremented for every integrity protected RRc message. + +If the IE "*Integrity Protection Mode Info*" is present in a received message, the MS shall: + +- 1> perform the actions in sub-clause 7.19.4.5 before proceeding with the integrity check of the received message. + +### 7.18.5.1 Integrity protection in downlink + +If the MS receives an RRc message on signalling radio bearer with RB identity n, the "Status" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started" and the IE '*Integrity Check Info*' is present the MS shall: + +- 1> check the value of the IE "*RRc Message Sequence Number*" included in the IE "*Integrity Check Info*"; +- 2> if the "Downlink RRc Message sequence number" for signalling radio bearer RBn is not present in the variable INTEGRITY\_PROTECTION\_INFO: + - 3> initialise the "Downlink RRc Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO with the value of the IE "*RRc Message Sequence Number*" included in the IE "*Integrity Check Info*" of the received message; +- 2> if the "Downlink RRc Message sequence number" is present in the variable INTEGRITY\_PROTECTION\_INFO: + +3> if the RRC message sequence number is lower than the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO: + +4> increment "Downlink RRC HFN" for signalling radio bearer SRBn in the variable INTEGRITY\_PROTECTION\_INFO with one. + +NOTE: The actions above imply that also for the case the "Downlink RRC HFN" is re-initialised by a security mode control procedure, this "Downlink RRC HFN" value is incremented by one before it is applied for the integrity protection of any received message if the conditions above are fulfilled. + +3> if the RRC message sequence number is equal to the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO: + +4> discard the message; + +1> calculate an expected message authentication code in accordance with sub-clause 7.18.5.3; + +1> compare the expected message authentication code with the value of the received IE "*Message Authentication Code*" contained in the IE "*Integrity Check Info*"; + +2> if the expected message authentication code and the received message authentication code are the same, the integrity check is successful: + +3> update the "Downlink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO with the value of the IE "*RRC Message Sequence Number*" included in the IE "*Integrity Check Info*" of the received RRC message; + +2> if the calculated expected message authentication code and the received message authentication code differ: + +3> act as though the message was not received. + +If the MS receives an RRC message on signalling radio bearer with identity n, the "Status" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started" and the IE "*Integrity Check Info*" is not present the MS shall: + +1> discard the message. + +## 7.18.5.2 Integrity protection in uplink + +Prior to sending an RRC message using the signalling radio bearer with radio bearer identity n, and the "Status" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started" the MS shall: + +1> increment "Uplink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO with 1, even if the message is a retransmission of a previously transmitted message. + +1> if the "Uplink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO equals zero : + +2> the MS shall increment "Uplink RRC HFN" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO by one; + +NOTE: The actions above imply that also for the case the "Uplink RRC HFN" is re-initialised by a security mode control procedure, this "Uplink RRC HFN" is incremented before it is applied in the integrity protection of any transmitted message if the conditions above are fulfilled. + +1> calculate the message authentication code in accordance with sub-clause 7.18.5.3; + +1> replace the "Message authentication code" in the IE "*Integrity Check Info*" in the message with the calculated message authentication code; + +1> replace the "RRC Message sequence number" in the IE "*Integrity Check Info*" in the message with contents set to the new value of the "Uplink RRC Message sequence number" for signalling radio bearer RBn in the variable INTEGRITY\_PROTECTION\_INFO; + +In the response message for the procedure ordering the security reconfiguration, the MS indicates the activation time, for each signalling radio bearer. When the new integrity configuration is to be applied in uplink, GERAN should then start to apply the new integrity protection configuration according to the activation time for each signalling radio bearer (except for the signalling radio bearer which is used to send the message that is reconfiguring the security configuration) where the new configuration is to be applied starting from and including reception of the response message. + +### 7.18.5.3 Calculation of message authentication code + +The MS shall calculate the message authentication code in accordance with 3GPP TS 33.102. The construction of the input parameter MESSAGE (see 3GPP TS 33.102) for the integrity algorithm is FFS. + +For usage on an RRC message transmitted or received on the radio bearer with identity n, the MS shall: + +1> construct the input parameter COUNT-I (see 3GPP TS 33.102) by appending the following IEs from the IE "Signalling Radio Bearer Specific Integrity Protection Information" for radio bearer n in the variable INTEGRITY\_PROTECTION\_INFO: + +2> for uplink: + +3> "Uplink RRC HFN", as the MSB, and "Uplink RRC Message sequence number", as LSB; + +2> for downlink: + +3> "Downlink RRC HFN", as the MSB, and the IE "RRC Message Sequence Number" included in the IE "Integrity Check Info", as LSB. + +## 7.18.6 Physical channel establishment + +### 7.18.6.0 General + +![Sequence diagram of the Handover Access procedure. The diagram shows four lifelines: MS RRC, MS-MAC/RLC, GERAN- MAC/RLC, and GERAN-RRC. The sequence of messages is: 1. MS RRC sends a HANDOVER-Req primitive to MS-MAC/RLC. 2. MS-MAC/RLC sends a MAC- HANDOVER ACCESS message to GERAN- MAC/RLC. 3. GERAN- MAC/RLC sends a HANDOVER-Ind primitive to GERAN-RRC. 4. GERAN-RRC sends a PHYSICAL INFO-Req primitive to GERAN- MAC/RLC. 5. GERAN- MAC/RLC sends a MAC- PHYSICAL INFORMATION message to MS-MAC/RLC. 6. MS-MAC/RLC sends a PHYSICAL INFO-Ind primitive to MS RRC.](efcb2f9e7c89b033238d1021d3bd539f_img.jpg) + +``` + +sequenceDiagram + participant MS_RRC as MS RRC + participant MS_MAC_RLC as MS-MAC/RLC + participant GERAN_MAC_RLC as GERAN- MAC/RLC + participant GERAN_RRC as GERAN-RRC + Note left of MS_RRC: + MS_RRC->>MS_MAC_RLC: HANDOVER-Req primitive + MS_MAC_RLC->>GERAN_MAC_RLC: MAC- HANDOVER ACCESS + GERAN_MAC_RLC->>GERAN_RRC: HANDOVER-Ind primitive + GERAN_RRC->>GERAN_MAC_RLC: PHYSICAL INFO-Req primitive + GERAN_MAC_RLC->>MS_MAC_RLC: MAC- PHYSICAL INFORMATION + MS_MAC_RLC->>MS_RRC: PHYSICAL INFO-Ind primitive + +``` + +Sequence diagram of the Handover Access procedure. The diagram shows four lifelines: MS RRC, MS-MAC/RLC, GERAN- MAC/RLC, and GERAN-RRC. The sequence of messages is: 1. MS RRC sends a HANDOVER-Req primitive to MS-MAC/RLC. 2. MS-MAC/RLC sends a MAC- HANDOVER ACCESS message to GERAN- MAC/RLC. 3. GERAN- MAC/RLC sends a HANDOVER-Ind primitive to GERAN-RRC. 4. GERAN-RRC sends a PHYSICAL INFO-Req primitive to GERAN- MAC/RLC. 5. GERAN- MAC/RLC sends a MAC- PHYSICAL INFORMATION message to MS-MAC/RLC. 6. MS-MAC/RLC sends a PHYSICAL INFO-Ind primitive to MS RRC. + +Figure 7.18.6.0.1: Handover Access procedure + +The Handover Access procedure initiation in RRC-Cell\_Dedicated state is done by sending a HANDOVER-Req primitive to the MS MAC layer as described in 3GPP TS 44.160. The MS MAC uses this procedure to initiate access in the new cell. The reception of a HANDOVER ACCESS message at GERAN MAC is indicated to GERAN RRC by sending the HANDOVER-Ind primitive as specified in 3GPP TS 44.160. + +The Physical Information procedure initiation is done by sending a PHYSICAL INFO-Req primitive to the GERAN MAC layer as specified in 3GPP TS 44.160 upon receipt of a HANDOVER-Ind primitive from the GERAN MAC layer. When the network has the necessary mobile station's RF characteristics it sends PHYSICAL INFORMATION message as specified in sub-clause 7.18.6.2. The reception of a PHYSICAL INFORMATION message at MS MAC is indicated to the MS RRC by sending the PHYSICAL INFO-Ind primitive. + +Four procedures are defined: Finely synchronized cell, Non-synchronized cell, Pseudo-synchronized cell and Pre-synchronized cell. The support of all of them except the pseudo-synchronized cell case is mandatory in the mobile station. A pseudo-synchronized establishment can be commanded only to a mobile station that can support it, as indicated in the classmark. + +### 7.18.6.1 Finely synchronized cell case + +When MS receives the RADIO BEARER RECONFIGURATION message and + +- 1> if the IE "*Timing Advance*" with the new cell is not out of range, i.e. smaller than or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004, or +- 1> if the new cell does accept out of range timing advance as indicated in the RADIO BEARER RECONFIGURATION message, the mobile station shall: + - 2> after having switched to the assigned channels, send the HANDOVER ACCESS message as specified in 3GPP TS 44.160 The transmission of this message is optional if so indicated by the network in the RADIO BEARER RECONFIGURATION message. + +The MS shall not transmit the HANDOVER ACCESS message in those cells that support extended TA values if TA value in the new cell is greater than 63 and the RADIO BEARER RECONFIGURATION message indicates that the transmission of the HANDOVER ACCESS messages is optional. + +Then the MS shall: + +- 1> activate the channels in sending and receiving mode. + +If applicable, ciphering is immediately started. + +### 7.18.6.2 Non synchronized cell case + +Upon reception of the RADIO BEARER RECONFIGURATION message and after having switched to the assigned channels, the mobile station shall: + +- 1> send repeatedly the HANDOVER ACCESS message as specified in 3GPP TS 44.160; +- 1> start timer T3124 at the start point of the timeslot in which the HANDOVER ACCESS message is sent the first time; +- 1> then, activate the channels in receiving mode; If applicable, deciphering is then immediately started. + +Upon receipt of a HANDOVER-ind primitive the GERAN RRC shall: + +- 1> set the value of the Timing Advance Value parameter in the PHYSICAL INFO-Req primitive to the timing advance value received from the GERAN MAC layer. +- 1> initiate the transmission of PHYSICAL INFORMATION message by transmitting a PHYSICAL INFO-Req service primitive to the GERAN MAC sublayer. + +When the network has the necessary mobile station's RF characteristics it shall send a PHYSICAL INFORMATION message to the mobile station as specified in 3GPP TS 44.160. If applicable, ciphering and deciphering is immediately started + +The network shall start timer T3143 immediately after having sent the PHYSICAL INFORMATION message. If this timer times out before the reception of the RADIO BEARER RECONFIGURATION COMPLETE message from the mobile station, the network shall send the PHYSICAL INFORMATION message once more and shall restart timer T3143. The network shall not send the PHYSICAL INFORMATION message more than N3143 times. The value of T3143 and N3143 is an implementation issue. + +At the mobile side, when the MAC layer indicates the reception of a PHYSICAL INFORMATION message, the MS shall: + +- 1> stop timer T3124; +- 1> stop sending HANDOVER ACCESS messages; +- 1> activate the physical channels in sending and receiving mode; + +If the allocated channel is a DBPSCH/S, the performance of the mobile station must enable the mobile station to accept a correct PHYSICAL INFORMATION message sent by the network in any block while T3124 is running. + +### 7.18.6.3 Pseudo-synchronized cell case + +The details of the use of this procedure are described in 3GPP TS 45.010. + +If the RADIO BEARER RECONFIGURATION message is received by the MS and if the IE "*Timing Advance*" and the IE "*Real Time Difference*" are included in the message, then MS shall: + +- 1> compute the timing advance to be used with the new cell from the real time difference value given in the RADIO BEARER RECONFIGURATION message. + +The mobile station shall switch to the new physical channel and proceed as follows: + +- 1> if the "*Timing Advance*" IE is received in the RADIO BEARER RECONFIGURATION; and +- 1> if the mobile station knows that the timing advance with the new cell is not out of range, i.e. smaller or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004; or +- 1> if the new cell accepts an out of range timing advance as indicated in the RADIO BEARER RECONFIGURATION message after having switched to the assigned channels, the mobile station shall: + - 2> send the HANDOVER ACCESS message as specified in 3GPP TS 44.160. The transmission of this message is optional if so indicated by the network in the RADIO BEARER RECONFIGURATION message. + +The MS shall not transmit the HANDOVER ACCESS message in those cells that support extended TA values if TA value in new cell is greater than 63 and the RADIO BEARER RECONFIGURATION message indicates that the transmission of the HANDOVER ACCESS messages is optional. Then MS shall: + +- 1> activate the channels in sending and receiving mode while sending the HANDOVER ACCESS message. + +If applicable, ciphering is immediately started. + +### 7.18.6.4 Pre-synchronized cell case + +The details of the use of this procedure are described in 3GPP TS 45.010. + +Upon reception of the RADIO BEARER RECONFIGURATION message, the mobile station shall: + +- 1> switch to the new channel; and +- 1> send the HANDOVER ACCESS message as specified in 3GPP TS 44.160. The transmission of this message is optional if so indicated by the network in the RADIO BEARER RECONFIGURATION message. + +The MS shall not transmit the HANDOVER ACCESS message in those cells that support extended TA values if TA value in new cell is greater than 63 and the RADIO BEARER RECONFIGURATION message indicates that the transmission of the HANDOVER ACCESS messages is optional. Then MS shall activate the channels in sending and receiving mode during the transmission of the HANDOVER ACCESS message. The timing advance value to be used with the new cell is: + +- 1> either the value contained in the RADIO BEARER RECONFIGURATION message if the timing advance information element is present; or +- 1> the default value for pre-synchronized handover as defined in 3GPP TS 45.010, if the timing advance information element is not included in the RADIO BEARER RECONFIGURATION message. The MS may activate the channels in receiving mode while sending HANDOVER ACCESS message. + +If applicable, ciphering is immediately started. + +### 7.18.7 (void) + +## 7.18.8 Link failure and Radio link failure criteria and actions upon link or radio link failure + +When a radio link failure is detected at L2, it is notified to RRC as specified in 3GPP TS 44.160. + +When a link failure is reported by a given RLC entity to RRC, RRC shall: + +- 1) stop the RLC entity + +When a radio link failure occurs signalled by the MAC sublayer or the physical layer (see 3GPP TS 45.008), the MS shall: + +- 1) clear the dedicated physical channel configuration; +- 1) perform actions as specified for the ongoing procedure; +- 1) if no procedure is ongoing or no actions are specified for the ongoing procedure: + - 2) perform a Cell Update procedure according to sub-clause 7.8 using the cause "radio link failure". + +## 7.18.9 Unsupported configuration + +The MS should set the variable UNSUPPORTED\_CONFIGURATION to TRUE if the received message is not according to the MS capabilities. + +## 7.18.10 Invalid RLC/MAC control message notification + +When notification is received of the reception of an invalid RLC/MAC acknowledgement message on DBPSCH, the MS shall: + +- 1) re-establish all RLC entities for the radio bearers currently established on the DBPSCH(s); +- 1) clear the dedicated physical channel configuration; +- 1) perform actions as specified for the ongoing procedure; +- 1) if no procedure is ongoing or no actions are specified for the ongoing procedure: + - 2) perform a Cell Update procedure according to sub-clause 7.8 using the cause "Invalid RLC/MAC control message" + +## 7.18.11 Actions related to Radio Bearer mapping + +When the MS receives the IE "*RB Mapping Info*" and/or the IE "*Transport Format Set*", when the MS performs a cell reselection or a state transition, or when the MS releases a RB, the MS shall for each of the configured Radio Bearers: + +- 1) configure the MAC with the appropriate transport format set (with computed transport block sizes) for the transport channel used by that RB; +- 1) determine the sets of RLC sizes that apply to the RLC entity used by that RB, based on the IE "*RLC Size List*" included in the applicable "*Transport format set*" (either the ones received in the same message or the ones stored if none were received); +- 1) if that RB is using RLC AM and the RLC size list applicable to the RLC entity transporting data PDUs is different from the one derived from the previously stored configuration: + - 2) if the old RLC size list is not contained in the new one then: + - 3) re-establish the RLC entity; + - 3) configure the corresponding RLC entity with the new RLC size list; + - 2) else configure the corresponding RLC entity with the new RLC size list; + - 2) for each RLC AM radio bearer in the CN domain as indicated in the IE "*CN Domain Identity*" in the IE "*RAB Info*" in the variable ESTABLISHED\_RABS whose RLC size is changed; and + - 2) for each RLC AM signalling radio bearer in the CN domain as indicated in the IE "*CN Domain Identity*" in the variable LATEST\_CONFIGURED\_CN\_DOMAIN whose RLC size is changed: + - 3) if the IE "*Status*" in the variable CIPHERING\_STATUS of this CN domain is set to "Started": + +4) set the HFN values for the corresponding RLC entity equal to the value of the IE "*START*" for this CN domain that will be included in the CELL UPDATE message following cell reselection. + +4) if the RLC re-establishment is caused by a CELL UPDATE CONFIRM: + +sss) 5) set the HFN values for the corresponding RLC entity equal to the value of the IE "*START*" included in the latest transmitted CELL UPDATE message for this CN domain. + +4) if the RLC re-establishment is caused by a reconfiguration message: + +ttt) 5) set the HFN values for the corresponding RLC entity equal to the value of the IE "*START*" that will be included in the reconfiguration complete message for this CN domain. + +1) if that RB is using RLC UM: + +2) indicate the largest applicable RLC size to the corresponding RLC entity. + +1) configure the MAC with the set of applicable RLC Sizes for each of the RLC entity used for that RB; + +1) if there is no RLC information applicable for the transport channels to be used: + +2) set the variable INVALID\_CONFIGURATION to TRUE. + +## 7.18.12 Network response times for DBPSCH allocation + +Upon reception of a CELL UPDATE CONFIRM message or one of the radio bearer reconfiguration messages (RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message) by the MS, and if the IE "*DBPSCH Description*" and the structure "Network Response Times" are included, the MS shall set the response times for layer 2 as specified in 3GPP TS 44.160. + +## 7.19 Generic actions on receipt and absence of an information element + +### 7.19.1 CN information info + +If the IE "*CN Information Info*" is present in a message, the MS shall: + +1) if present, forward the content of the IE "*PLMN Identity*" to upper layers; + +1) if present, forward the content of the IE "*CN Common GSM-MAP NAS System Information*" to upper layers; + +1) if the IE "*CN Domain Related Information*" is present: + +2) forward each occurrence of the IE "*CN Domain Specific GSM-MAP NAS System Info*" together with the IE "*CN Domain Identity*" to upper layers; + +2) if an IE "*CN Domain Specific GSM-MAP NAS System Info*" is not present for a particular CN domain: + +3) indicate to upper layers that no CN system information is available for that CN domain. + +### 7.19.2 Signalling connection release indication + +If the IE "*Signalling Connection Release Indication*" is present in a message, the MS shall: + +1) if all radio access bearers for the CN domain identified with the value of the IE "*Signalling Connection Release Indication*" would have been released in the variable ESTABLISHED\_RABS after processing of the received message: + +2) indicate release of the signalling connection identified with the value of the IE "*Signalling Connection Release Indication*" to the upper layers; + +2) remove the signalling connection identified with the value of the IE "*Signalling Connection Release Indication*" from the variable ESTABLISHED\_SIGNALLING\_CONNECTIONS; + +- 1> if radio access bearers for the CN domain identified with the value of the IE "*Signalling Connection Release Indication*" would remain in the variable ESTABLISHED\_RABS after processing of the received message: + - 2> set the variable INVALID\_CONFIGURATION to TRUE. + +## 7.19.3 GERAN mobility information elements + +### 7.19.3.1 GRA identity + +The MS shall: + +- 1> if the IE "*GRA Identity*" is included in a received message: + - 2> if the IE "*RRC State Indicator*" is included and set to "GRA\_PCH": + - 3> store this GRA identity in the variable GRA\_IDENTITY; + - 3> after sending a possible message to GERAN and entering GRA\_PCH state as specified elsewhere, read packet system information 16 in the selected cell; + - 3> if the stored GRA identity in the variable GRA\_IDENTITY is not included in the list of GRA identities in System Information 16 in the selected cell, the list of GRA identities in system information 16 is empty or if the packet system information 16 can not be found, a confirmation error of GRA identity list has occurred: + - 4> if no GRA Update procedure is ongoing: + - uuu) 5> initiate a GRA Update procedure after entering GRA\_PCH state; see sub-clause 7.8; + - 4> if a GRA Update procedure is ongoing: + - vvv) 5> take actions as specified in sub-clause 7.8; +- 1> if the IE "*GRA Identity*" is not included in a received message: + - 2> the IE "*RRC State Indicator*" is included and set to " GRA\_PCH": + - 3> after sending a possible message to GERAN and entering GRA\_PCH state as specified elsewhere, read System Information 16 in the selected cell; + - 3> if System Information 16 in the selected cell contains a single GRA identity: + - 4> store this GRA identity in the variable GRA\_IDENTITY; + - 3> if Packet system information 16 of the selected cell contains more than one GRA identity, the list of GRA identities in packet system information 16 is empty or if the system information 16 can not be found, a confirmation error of GRA identity list has occurred: + - 4> if no GRA Update procedure is ongoing: + - www) 5> initiate a GRA Update procedure after entering RRC-GRA\_PCH state see subsub-clause 7.8; + - 4> if a GRA Update procedure is ongoing: + - xxx) 5> take actions as specified in sub-clause 7.8. + +### 7.19.3.2 Mapping info + +If the IE "*Mapping Info*" is received, the MS shall in this version of the specification: + +- 1> ignore the contents of this IE. + +## 7.19.4 MS information elements + +### 7.19.4.1 Activation time + +If the MS receives a message containing the IE "*Activation time*" with a value other than 0, the MS shall: + +- 1> select the beginning of the FN (TDMA Frame Number) indicated by the IE "*Activation Time*" as the activation time T. +- 1> at the activation time T: + - 2> for a physical channel reconfiguration caused by the received message: + - 3> release the physical channel configuration, which was present before T; + - 3> initiate the establishment of the physical channel configuration as specified for the physical channel information elements in the received message as specified elsewhere. + - 2> for actions, other than a physical channel reconfiguration, caused by the received message: + - 3> perform the actions for the information elements in the received message as specified elsewhere. + +If the MS receives a message containing the IE "*Activation time*" with the value 0 meaning "Now", the MS shall: + +- 1> as an immediate reaction to the reception of the message (see 3GPP TS 45.010 for timing constraints): + - 2> perform the actions for the information elements in the received message as specified elsewhere, + +NOTE: If the MS was in RRC-Idle mode or RRC- CELL\_Shared state upon reception of the message, and the value of the IE "*Activation Time*" in the received message is different from "Now", regardless of the state the MS enters after reception of the message the MS behaviour is unspecified. + +### 7.19.4.2 DRX parameters + +#### 7.19.4.2.1 CN domain specific DRX cycle length coefficients + +The GERAN shall broadcast the CN domain specific DRX cycle length coefficients parameter on PBCCH. The MS may be attached to different CN domains with different CN domain specific DRX cycle lengths. The MS shall store each CN domain specific DRX cycle length for each CN domain the MS is attached to. + +For the CS CN domain, the CS CN specific DRX cycle length coefficient shall be updated locally in the MS using information given in system information. + +For the PS CN domain, the PS CN specific DRX cycle length coefficient may be updated after indication by the MS to the PS CN in NAS procedure. If no specific value is indicated, the MS and PS CN shall use the DRX cycle length given for PS CN domain in system information. + +NOTE: Broadcast of CN domain specific DRX cycle length coefficients shall be introduced with System Information broadcasting for GERAN *Iu mode*. + +#### 7.19.4.2.2 GERAN DRX cycle length coefficient + +In RRC-Connected mode, GERAN shall determine and it may send its GERAN specific DRX cycle length coefficients parameter to a given MS in the following RRC messages: + +- CELL UPDATE CONFIRM +- GRA UPDATE CONFIRM +- RADIO BEARER RECONFIGURATION +- RADIO BEARER RELEASE +- RADIO BEARER SETUP +- RRC CONNECTION SETUP + +### 7.19.4.2.3 Paging Group + +In DRX mode, the MS shall compute its paging group and the GERAN shall compute a paging group listened by the MS (see 3GPP TS 23.122) using the SPLIT\_PG\_CYCLE parameter obtained with the following equation: + +$$\text{SPLIT\_PG\_CYCLE} = 3 \times 2^{(9-\text{"main DRX cycle length coefficient"})}$$ + +In RRC-Idle mode, the "main DRX cycle length coefficient" is: + +- 1) for the MS, the smallest of the stored CN domain specific DRX cycle length coefficients corresponding to the CN domains to which the MS is attached; +- 1) for the GERAN, the smallest of: + - 2) the broadcast CN domain specific DRX cycle length coefficients corresponding to the CN domains to which the MS is attached, and + - 2) the DRX cycle length coefficient, if indicated in the PAGING message received via RANAP. + +In RRC-Connected mode, the "main DRX cycle length coefficient" is: + +- 1) for the MS, the smallest of: + - 2) the stored CN domain specific DRX cycle length coefficients corresponding to the CN domains to which the MS is attached, and, + - 2) the GERAN DRX cycle length coefficient, if previously received. +- 1) for the GERAN, the smallest of: + - 2) the broadcast CN domain specific DRX cycle length coefficients corresponding to the CN domains to which the MS is attached, + - 2) the GERAN DRX cycle length coefficient, if previously received, and + - 2) the DRX cycle length coefficient, if indicated in the PAGING message received via RANAP. + +The paging group is indicated to lower layers via primitives. + +NOTE: Primitives between RLC/MAC and RRC shall be described in 3GPP TS 44.160. + +### 7.19.4.3 Generic state transition rules depending on received information elements + +The IE "*RRC State Indicator*" indicates the state the MS shall enter. The MS shall enter the state indicated by the IE "*RRC State Indicator*" even if the received message includes other IEs relevant only for states other than indicated by the IE "*RRC State Indicator*". E.g. if the RRC state indicator is set to "RRC-Cell\_Shared" while other IEs provide information about a configuration including dedicated channels, the MS shall enter RRC-Cell\_Shared state. If however the MS has no information about the configuration corresponding to the state indicated by the IE "*RRC State Indicator*", it shall consider the requested configuration as invalid. + +The MS shall, if the IE "*RRC State Indicator*" in the received message has the value: + +- 1) "RRC-Cell\_Shared": + - 2) enter RRC-Cell\_Shared state as dictated by the procedure governing the message received; +- 1) "RRC-CELL\_Dedicated": + - 2) if neither DBPSCH is assigned in the message nor is the MS in RRC-CELL\_Dedicated state: + - 3) set the variable INVALID\_CONFIGURATION to TRUE; + - 2) else: + - 3) enter RRC-Cell\_Dedicated state as dictated by the procedure governing the message received; +- 1) "RRC-GRA\_PCH": + +- 2> if the received message is RRC CONNECTION SETUP and IE "*RRC State Indicator*" is set to RRC- +GRA\_PCH: + - 3> set the variable INVALID\_CONFIGURATION to TRUE; +- 2> else: + - 3> enter RRC-GRA\_PCH state as dictated by the procedure governing the message received. + +#### 7.19.4.4 Ciphering mode info + +The IE "*Ciphering Mode Info*" defines the new ciphering configuration. At any given time, the MS needs to store at most two different ciphering configurations (keyset and algorithm) per CN domain at any given time in total for all radio bearers, and three configurations in total for all signalling radio bearers. + +If the IE "*Ciphering Mode Info*" is present and if the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to TRUE, the MS shall: + +- 1> ignore this attempt to change the ciphering configuration; and +- 1> set the variable INCOMPATIBLE\_SECURITY\_CONFIGURATION to TRUE. + +If the IE "*Ciphering Mode Info*" is present and if the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to FALSE, the MS shall: + +- 1> if none of the IE "*Status*" in the variable CIPHERING\_STATUS has the value "Started", and this IE "*Ciphering Mode Info*" was included in a message that is not the message SECURITY MODE COMMAND message; or +- 1> if the IE "*Ciphering Mode Info*" was received in the message SECURITY MODE COMMAND message and there does not exist exactly one ciphering activation time in the IE "*Radio Bearer Downlink Ciphering Activation Time Info*" for each established RLC-AM and RLC-UM radio bearers included in the IE "*RB Information*" in the ESTABLISHED\_RABS for the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; or +- 1> if the IE "*Ciphering Mode Info*" was received in the message SECURITY MODE COMMAND message and the IE "*Ciphering Activation Time for DBPSCH*" is not included in the message, and there exist radio bearers using RLC-TM according to the IE "*RB Information*" in the IE "ESTABLISHED\_RABS" for the CN domain as indicated in the variable LATEST\_CONFIGURED\_CN\_DOMAIN; or +- 1> if the IE "*Ciphering Mode Info*" was received in the message SECURITY MODE COMMAND message and there does not exist exactly one ciphering activation time in the IE "*Radio Bearer Downlink Ciphering Activation Time Info*" for each established signalling radio bearer included in the IE "*Signalling Radio Bearer Information*" in the ESTABLISHED-RABS; +- 2> ignore this attempt to change the ciphering configuration; +- 2> set the variable INVALID\_CONFIGURATION to TRUE; +- 2> perform the actions as specified in sub-clause 7.16.1.2.6; + +If the IE "*Ciphering Mode Info*" is present and if the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS is set to FALSE, the MS shall: + +- 1> set the IE "*Reconfiguration*" in the variable CIPHERING\_STATUS to TRUE; +- 1> set the IE "*Status*" in the variable CIPHERING\_STATUS of the the CN domains for which the IE "*Status*" of the variable SECURITY\_MODIFICATION is set to "Affected" to "Started"; +- 1> apply the new ciphering configuration in the lower layers for all RBs that belong to a CN domain for which the IE "*Status*" of the variable SECURITY\_MODIFICATION is set to "Affected" and all signalling radio bearers: + - 2> using the ciphering algorithm (UEA (see 3GPP TS 33.102)) indicated by the IE "*Ciphering Algorithm*" as part of the new ciphering configuration; + - 2> for each radio bearer that belongs to a CN domain for which the IE "*Status*" of the variable SECURITY\_MODIFICATION is set to "Affected" and all signalling radio bearers: + +3> use the value of the IE "*RB Identity*" in the variable ESTABLISHED\_RABS minus one as the value of BEARER (see 3GPP TS 33.102) in the ciphering algorithm; + +1> for the downlink and the uplink, the new ciphering configuration shall be applied as follows: + +2> if the ciphering configuration for a radio bearer or signalling radio bearer from a previously received SECURITY MODE COMMAND message has not yet been applied because of the corresponding activation times not having been reached and the current received message includes the IE "*Downlink Counter Synchronization Info*" or the current received message is a RADIO BEARER RECONFIGURATION message and includes the IE "*New G-RNTI*": + +3> if the previous SECURITY MODE COMMAND message was received due to new keys being received: + +4> consider the new ciphering configuration to include the received new keys; + +3> else if the previous SECURITY MODE COMMAND caused a change in LATEST\_CONFIGURED\_CN\_DOMAIN + +4> consider the new ciphering configuration to include the keys associated with the LATEST\_CONFIGURED\_CN\_DOMAIN; + +2> apply the new ciphering configuration in uplink and downlink immediately following RLC re-establishment. + +2> if the IE "*Ciphering Activation Time for DBPSCH*" is present in the IE "*Ciphering Mode Info*" and the MS was in Cell\_Dedicated state prior to this procedure: + +3> for radio bearers using RLC-TM: + +4> apply the old ciphering configuration for the TDMA frame number less than the number indicated by the IE "*COUNT-C activation time*" in the IE "*Ciphering Activation Time for DBPSCH*"; + +4> apply the new ciphering configuration for the TDMA frame number greater than or equal to the number indicated in IE "*Ciphering Activation Time for DBPSCH*"; + +2> if the IE "*Radio Bearer Downlink Ciphering Activation Time Info*" is present: + +3> apply the following procedure for each radio bearer and signalling radio bearers using RLC-AM or RLC-UM indicated by the IE "*RB Identity*": + +4> suspend uplink transmission on the radio bearer or the signalling radio bearer (except for the SRB where the response message is transmitted) according to the following: + +yyy) 5> do not transmit RLC PDUs with sequence number greater than or equal to the uplink activation time, where the uplink activation time is selected according to the rules below; + +4> select an "RLC sequence number" at which (activation) time the new ciphering configuration shall be applied in uplink for that radio bearer according to the following: + +zzz) 5> consider a ciphering activation time in uplink to be pending until the RLC sequence number of the next RLC PDU to be transmitted for the first time is equal to or larger than the selected activation time; + +aaaa) 5> for each radio bearer and signalling radio bearer that has no pending ciphering activation time in the uplink as set by a previous procedure changing the security configuration: + +6> set a suitable value that would ensure a minimised delay in the change to the latest ciphering configuration; + +bbbb) 5> for each radio bearer and signalling radio bearer that has a pending ciphering activation time in uplink as set by a previous procedure changing the security configuration: + +6> for radio bearers and signalling radio bearers except SRB2, set the same value as the pending ciphering activation time; + +- 4> store the selected "RLC send sequence number" for that radio bearer in the entry for the radio bearer in the variable RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO; +- 4> switch to the new ciphering configuration according to the following: + - cccc) 5> use the old ciphering configuration for the transmitted and received RLC PDUs with RLC sequence number smaller than the corresponding RLC sequence number indicated in the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" sent to GERAN and the received IE "*Radio Bearer Downlink Ciphering Activation Time Info*" received from GERAN, respectively; + - dddd) 5> use the new ciphering configuration for the transmitted and received RLC PDUs with RLC sequence numbers greater than or equal to the corresponding RLC sequence number indicated in the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" sent to GERAN and in the received IE "*Radio Bearer Downlink Ciphering Activation Time Info*" received from GERAN, respectively; + - eeee) 5> for a radio bearer using RLC-AM, when the RLC sequence number indicated in the IE "*Radio Bearer Downlink Ciphering Activation Time Info*" falls below the RLC receiving window and the RLC sequence number indicated in the IE "*Radio Bearer Uplink Ciphering Activation Time Info*" falls below the RLC transmission window, the MS may release the old ciphering configuration for that radio bearer; + - ffff) 5> if an RLC reset or re-establishment occurs before the activation time for the new ciphering configuration has been reached, ignore the activation time and apply the new ciphering configuration both in uplink and downlink immediately after the RLC reset or RLC re-establishment. + +If the IE "*Ciphering Mode Info*" is not present, the MS shall: + +- 1> for the downlink and the uplink, apply the ciphering configuration as follows: + - 2> if the ciphering configuration for a AM or UM radio bearer or signalling radio bearer from a previously received SECURITY MODE COMMAND has not yet been applied because of the corresponding activation times not having been reached and the current received message includes the IE "*DL Counter Synch Info*" or the current received message is a RADIO BEARER RECONFIGURATION message and includes the IE "*New G-RNTT*": + - 3> if the previous SECURITY MODE COMMAND was received due to new keys being received: + - 4> consider the ciphering configuration to include the received new keys; + - 3> else if the previous SECURITY MODE COMMAND caused a change in LATEST\_CONFIGURED\_CN\_DOMAIN: + - 4> consider the ciphering configuration to include the keys associated with the LATEST\_CONFIGURED\_CN\_DOMAIN; + - 3> apply the ciphering configuration in uplink and downlink immediately following RLC re-establishment; + - 2> else: + - 3> not change the ciphering configuration. + +## 7.19.4.5 Integrity protection mode info + +### 7.19.4.5.1 General + +The IE "*Integrity Protection Mode Info*" defines the new integrity protection configuration. At any given time, the MS needs to store at most three different integrity protection configurations (keysets) in total for all signalling radio bearers for all CN domains. + +If the IE "*Integrity Protection Mode Info*" is present and if the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to TRUE, the MS shall: + +- 1> ignore this second attempt to change the integrity protection configuration; and + +1> set the variable INCOMPATIBLE\_SECURITY\_RECONFIGURATION to TRUE. + +If IE "*Integrity Protection Mode Command*" has the value "Start" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Not started", and the IE "*Integrity Protection Mode Command Info*" was not included in the message SECURITY MODE COMMAND message; or + +If IE "*Integrity Protection Mode Command*" has the value "Start" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Not started", and the IE "*Integrity Protection Mode Info*" was included in the message SECURITY MODE COMMAND message, and the IE "*Integrity Protection Algorithm*" is not included; or + +If the IE "*Integrity Protection Mode Command*" has the value "Modify" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Not Started"; or + +If IE "*Integrity Protection Mode Command*" has the value "Start" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started", and the IE "*Integrity protection mode command info*" was included in the message SECURITY MODE COMMAND message; or + +If the IE "*Integrity Protection Mode Command*" has the value "Modify" and there does not exist exactly one integrity protection activation time in the IE "*Downlink Integrity Protection Activation Info*" for each established signalling radio bearer included in the IE "*Signalling Radio Bearer Information*" in the variable ESTABLISHED\_RABS; or + +If IE "*Integrity Protection Mode Command*" has the value "Modify" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started", and the IE "*Integrity Protection Mode Info*" was not included in the message SECURITY MODE COMMAND message: + +the MS shall: + +1> ignore this attempt to change the integrity protection configuration; and + +1> set the variable INVALID\_CONFIGURATION to TRUE. + +If the IE "*Integrity protection mode info*" is not present, the MS shall: + +1> not change the integrity protection configuration. If the IE "*Integrity Protection Mode Info*" is present and if the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO is set to FALSE, the MS shall: + +1> set the IE "*Reconfiguration*" in the variable INTEGRITY\_PROTECTION\_INFO to TRUE; + +1> perform the actions in accordance with sub-clauses 7.19.4.5.2, 7.19.4.5.3 and 7.19.4.5.4.; + +#### 7.19.4.5.2 Initialization of Integrity Protection The MS shall: + +1> if IE "*Integrity Protection Mode Command*" has the value "start" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Not started", and this IE was included in the message SECURITY\_MODE\_COMMAND: + +2> initialise the information for all signalling radio bearers in the variable INTEGRITY\_PROTECTION\_INFO according to the following: + +3> set the IE "*Uplink RRC Message Sequence Number*" in the variable INTEGRITY\_PROTECTION\_INFO to zero; + +3> do not set the IE "*Downlink RRC Message Sequence Number*" in the variable INTEGRITY\_PROTECTION\_INFO; + +3> set the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO to zero for each signalling radio bearer in the variable ESTABLISHED\_RABS . + +NOTE: The IE "*Integrity Protection Activation Info*" and "*RRC Message Sequence Number*" included in the IE "*Integrity Check Info*" in the transmitted message do not have identical values, but integrity protection is applied from the first transmitted message. + +2> set the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO to the value "Started"; + +- 2> perform integrity protection on the received message, applying the new integrity protection configuration, as described in sub-clause 7.18.5 by: + - 3> using the algorithm (UIA (see 3GPP TS 33.102)) indicated by the IE "*Integrity Protection Algorithm*" contained in the IE "*Integrity Protection Mode Info*"; + - 3> using the IE "*Integrity Protection Initialisation Number*", contained in the IE "*Integrity Protection Mode Info*" as the value of FRESH (see 3GPP TS 33.102); +- 2> start applying the new integrity protection configuration in the downlink for each signalling radio bearer in the IE "*Established RABS*" except SRB2 at the next received RRC message; +- 2> start applying the new integrity protection configuration in the downlink for signalling radio bearer SRB2 from and including the received SECURITY MODE COMMAND message; +- 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer SRB2 from and including the transmitted SECURITY MODE COMPLETE message; +- 2> start applying the new integrity protection configuration in the uplink for signalling radio bearers other than SRB2 at the uplink activation time included in the IE "*Uplink Integrity Protection Activation Info*". + +### 7.19.4.5.3 Integrity Protection Re-configuration for SBSS Relocation + +The MS shall: + +- 1> if IE "*Integrity Protection Mode Command*" has the value "start" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started" and this IE was not included SECURITY MODE COMMAND: + +NOTE: This case is used in SBSS relocation + +- 2> perform integrity protection on the received message, applying the new integrity protection configuration, as described in sub-clause 7.18.5 by: + - 3> using the algorithm (UIA (see 3GPP TS 33.102)) indicated by the IE "*Integrity Protection Algorithm*" contained in the IE "*Integrity Protection Mode Info*"; + - 3> using the IE "*Integrity Protection Initialisation Number*", contained in the IE "*Integrity Protection Mode Info*" as the value of FRESH (see 3GPP TS 33.102); +- 2> let SRBm be the signalling radio bearer where the reconfiguration message was received and let SRBn be the signalling radio bearer where the response message is transmitted; +- 2> for the downlink, for each signalling radio bearer, if for the signalling radio bearer, a security configuration triggered by a previous SECURITY MODE COMMAND message has not yet been applied, due to the activation time for the signalling radio bearer not having been reached: + - 3> set "Down link RRC Message sequence number" for this signalling radio bearer in the variable INTEGRITY\_PROTECTION\_INFO to (activation time - 1), where the activation time is the corresponding activation time for this signalling radio bearer;; + - 3> if the previous SECURITY MODE COMMAND message was received due to new keys being received: + - 4> consider the new integrity protection configuration to include the received new keys; + - 3> else if the previous SECURITY MODE COMMAND caused a change in LATEST\_CONFIGURED\_CN\_DOMAIN: + - 4> consider the new Integrity Protection configuration to include the keys associated with the LATEST\_CONFIGURED\_CN\_DOMAIN associated with the previously received SECURITY MODE COMMAND message; +- 2> start applying the new integrity protection configuration in the downlink for each signalling radio bearer in the variable ESTABLISHED\_RABS except RBm at the next received RRC message for the corresponding signalling radio bearer; + +- 2> start applying the new integrity protection configuration in the downlink for signalling radio bearer RBm from and including the received configuration message; +- 2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RBn from and including the transmitted response message; +- 2> start applying the new integrity protection configuration in the uplink for signalling radio bearers other than RBn from the first message onwards. + +#### 7.19.4.5.4 Integrity Protection modification in case of new keys or initialisation of signalling connection + +The MS shall: + +- 1> if IE "*Integrity Protection Mode Command*" has the value "modify" and the IE "*Status*" in the variable INTEGRITY\_PROTECTION\_INFO has the value "Started" and this IE was included SECURITY\_MODE\_COMMAND: + - 2> store the (oldest currently used) integrity protection configuration until activation times have elapsed for the new integrity protection configuration to be applied on all signalling radio bearers; + - 2> start applying the new integrity protection configuration in the downlink at the RRC sequence number, for each radio bearer n, indicated by the entry for radio bearer n in the "RRC message sequence number list" in the IE "*Downlink Integrity Protection Activation Info*", included in the IE "*Integrity Protection Mode Info*"; + - 2> perform integrity protection on the received message, applying the new integrity protection configuration, as described in sub-clause 7.18.5: + - 3> if present, use the algorithm indicated by the IE "*Integrity Protection Algorithm*" (UIA (see 3GPP TS 33.102)); + - 2> set the content of the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO according to the following: + - 3> for each established signalling radio bearer, stored in the variable ESTABLISHED\_RABS: + - 4> select a value of the RRC sequence number at which (activation) time the new integrity protection configuration shall be applied in uplink for that signalling radio bearer according to the following: + - gggg) 5> for each signalling radio bearer: + - 6> set the activation time for the new integrity protection configuration to the next RRC SN; + - 4> prohibit the transmission of RRC messages on all signalling radio bearers, except for SRB2, with RRC SN greater than or equal to the value in the "RRC message sequence number list" for the signalling radio bearer in the IE "*Uplink Integrity Protection Activation Info*" of the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> start applying the new integrity protection configuration in the uplink at the RRC sequence number, for each SRBn, except for signalling radio bearer SRB2, indicated by the entry for radio bearer n in the "RRC message sequence number list" in the IE "*Uplink Integrity Protection Activation Info*", included in the variable INTEGRITY\_PROTECTION\_ACTIVATION\_INFO; + - 2> start applying the new integrity protection configuration in the uplink at the RRC sequence number for signalling radio bearer SRB2, as specified for the procedure initiating the integrity protection reconfiguration; + - 2> start applying the new integrity protection configuration in the downlink at the RRC sequence number, for each SRBn, except for signalling radio bearer SRB2, indicated by the entry for signalling radio bearer n in the "*RRC Message Sequence Number List*" in the IE "*Downlink Integrity Protection Activation Info*". + +NOTE: For signalling radio bearers that have a pending activation time as set for integrity protection by a previous procedure changing the integrity protection configuration, the GERAN shall set this value in IE "*Downlink Integrity Protection Activation Info*". + +- 2> start applying the new integrity protection configuration in the downlink at the RRC sequence number for signalling radio bearer SRB2, as specified for the procedure initiating the integrity protection reconfiguration. + +#### 7.19.4.6 Integrity check info + +If the IE "Integrity check info" is present the MS shall: + +1> act as described in sub-clause 7.18.4.1 . + +#### 7.19.4.7 New G-RNTI + +If the IE "*New G-RNTI*" is included in a received message, the MS shall: + +1> store the value in the variable G\_RNTI, replacing any old stored value. + +#### 7.19.4.8 RRC Transaction Identifier + +The IE "*RRC Transaction Identifier*" may be used, together with the message type, for identification of an invocation of a downlink procedure (transaction). The MS behaviour for accepting or rejecting transactions based on the message type and the IE "*RRC Transaction Identifier*" is specified below. + +If the IE "*RRC Transaction Identifier*" is included in a received message, the MS shall perform the actions below. The MS shall: + +If the received message is any of the messages: + +- RADIO BEARER SETUP; or +- RADIO BEARER RECONFIGURATION; or +- RADIO BEARER RELEASE; + +the MS shall: + +1> if the variable ORDERED\_RECONFIGURATION is set to FALSE; and + +1> if the variable CELL\_UPDATE\_STARTED is set to FALSE; and + +1> if the received message does not contain a protocol error according to clause 8 and the variable PROTOCOL\_ERROR\_REJECT is set to FALSE: + +2> accept the transaction; and + +2> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS; + +1> else: + +2> if the variable ORDERED\_RECONFIGURATION is set to TRUE; or + +2> if the variable CELL\_UPDATE\_STARTED is set to TRUE; or + +2> if the received message contains a protocol error according to clause 8 causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE: + +3> if the IE "*RRC Transaction Identifier*" of the received message is identical to the "*RRC Transaction Identifier*" stored for the same "*Message Type*" as the received message in the table "Accepted transactions" in the variable TRANSACTIONS: + +4> ignore the transaction; and + +4> continue with any ongoing processes and procedures as the message was not received; + +4> and end the procedure; + +3> else: + +4> reject the transaction; and + +4> if the IE "*Message Type*" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: + +hhhh) 5> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. + +Else: + +If the received message is any of the messages: + +- RRC CONNECTION SETUP; or +- CELL UPDATE CONFIRM; or +- GRA UPDATE CONFIRM; + +the MS shall: + +1> if the IE "*Message Type*" of the received message is not present in the table "Accepted transactions" in the variable TRANSACTIONS: + +2> if the received message does not contain a protocol error according to clause 8 and the variable PROTOCOL\_ERROR\_REJECT is set to FALSE: + +3> accept the transaction; and + +3> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS; + +2> else: + +2> if the received message contains a protocol error according to clause 8 causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE: + +3> reject the transaction; and + +3> if the IE "*Message Type*" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: + +3> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. + +1> else: + +1> if the IE "*Message Type*" of the received message is present in the table "Accepted transactions" in the variable TRANSACTIONS: + +2> if the IE "*RRC Transaction Identifier*" of the received message is identical to the "*RRC Transaction Identifier*" stored for the "*Message Type*" in the table "Accepted transactions" in the variable TRANSACTIONS: + +3> ignore the transaction; and + +3> continue with any ongoing processes and procedures as the message was not received; and + +3> end the procedure; + +2> else: + +2> if the IE "*RRC Transaction Identifier*" of the received message is different from the "*RRC transaction identifier*" stored for the "*Message Type*" in the table "Accepted transactions" in the variable TRANSACTIONS: + +3> if the received message does not contain a protocol error according to clause 8 and the variable PROTOCOL\_ERROR\_REJECT is set to FALSE: + +4> ignore the once accepted transaction and instead accept the new transaction; and + +4> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS, replacing the previous entry; + +NOTE 1: The MS is expected to process the first RRC CONNECTION SETUP/CELL UPDATE CONFIRM/GRA UPDATE CONFIRM message that it receives after transmitting an RRC CONNECTION REQUEST/CELL UPDATE/GRA UPDATE message. If the MS receives further RRC CONNECTION SETUP/CELL UPDATE CONFIRM/GRA UPDATE CONFIRM messages without having transmitted another RRC CONNECTION REQUEST/CELL UPDATE/GRA UPDATE message, the MS is not required to process these messages. + +3> else: + +3> if the received message contains a protocol error according to clause 8 causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE: + +4> reject the transaction; and + +4> if the IE "*Message Type*" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: + +iii) 5> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. + +Else: + +If the received message is any other message, the MS shall: + +1> if the IE "*Message Type*" of the received message is not present in the table "Accepted transactions" in the variable TRANSACTIONS: + +2> if the received message does not contain a protocol error according to clause 8 and the variable PROTOCOL\_ERROR\_REJECT is set to FALSE: + +3> accept the transaction; and + +3> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS; + +2> else: + +2> if the received message contains a protocol error according to clause 8 causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE: + +3> reject the transaction; and + +3> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. + +1> else: + +1> if the IE "*Message Type*" of the received message is present in the table "Accepted transactions" in the variable TRANSACTIONS: + +2> if the IE "*RRC Transaction Identifier*" of the received message is identical to the "*RRC transaction identifier*" stored in any entry for the "*Message Type*" in the table "Accepted transactions" in the variable TRANSACTIONS: + +3> ignore the transaction; and + +3> continue with any ongoing processes and procedures as the message was not received; and + +3> end the procedure; + +2> else: + +- 2> if the IE "*RRC Transaction Identifier*" of the received message is different from the "RRC transaction identifier" stored in all entries for the "Message Type" in the table "Accepted transactions" in the variable TRANSACTIONS: + - 3> if the received message does not contain a protocol error according to clause 9 and the variable PROTOCOL\_ERROR\_REJECT is set to FALSE: + - 4> accept the additional transaction; and + - 4> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Accepted transactions" in the variable TRANSACTIONS, in addition to the already existing entries; + - 3> else: + - 3> if the received message contains a protocol error according to clause 8 causing the variable PROTOCOL\_ERROR\_REJECT to be set to TRUE: + - 4> reject the transaction; and + - 4> store the IE "*Message Type*" and the IE "*RRC Transaction Identifier*" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS. + +#### 7.19.4.9 Capability Update Requirement + +If the IE "*Capability Update Requirement*" is included the MS shall: + +- 1> if the IE "*MS GERAN A/Gb mode Radio Acces Capability Update Requirement*" is set to "required": + - 2> if the MS supports the GERAN *A/Gb mode*: + - 3> include its GERAN *A/Gb mode* radio access capability in the IE "*MS GERAN A/Gb mode Radio Access Capability*" of the variable MS\_CAPABILITY\_REQUESTED; +- 1> if one or more of the 3 the IEs "*UE Radio Access FDD Capability Update Requirement*" or "*UE Radio Access 3,84 Mcps TDD Capability Update Requirement*" or "*UE Radio Access 1,28 Mcps TDD Capability Update Requirement*" is set to "required": + - 2> include its UE UTRAN Radio Access Capability in the IE "*UE UTRAN Radio Access Capability*" and its UE UTRAN Radio Access Capability Extension if present in the IE "*UE UTRAN Radio Access Capability Extension*" of the variable MS\_CAPABILITY\_REQUESTED as specified in of 3GPP TS 25.331. +- 1> if the IE "*UE CDMA2000 Radio Acces Capability Update Requirement List*" is set to "required": + - 2> if the MS supports the CDMA2000 RAT: + - 3> include its UE CDMA2000 radio acces capability in the IE "*UE CDMA2000 Radio Acces Capability*" of the variable MS\_CAPABILITY\_REQUESTED + +If the IE "*Capability Update Requirement*" is not present, the MS shall: + +- 1> assume no capabilities were required and act in accordance with the above. + +### 7.19.5 Radio bearer information elements + +#### 7.19.5.1 Signalling RB information to setup list + +If the IE "*Signalling RB Information To Setup List*" is included the MS shall: + +- 1> use the same START value to initialise the COUNT-C and COUNT-I variables for all the signalling radio bearers in the list; +- 1> if the IE "*Signalling RB Information To Setup List*" was included in the RADIO BEARER SETUP message: + - 2> if the variable "LATEST\_CONFIGURED\_CN\_DOMAIN" has been initialised: + +- 3> calculate the START value only once during this procedure according to sub-clause 7.18.4 for the CN domain indicated in the variable "LATEST\_CONFIGURED\_CN\_DOMAIN"; +- 3> store the calculated START value in the variable START\_VALUE\_TO\_TRANSMIT; +- 1> for each occurrence of the IE "*Signalling RB Information to Setup*": + - 2> use the value of the IE "*RB Identity*" as the identity of the signalling radio bearer to setup; + - 2> if the signalling radio bearer identified with the IE "*RB Identity*" does not exist in the variable ESTABLISHED\_RABS: + - 3> create a new entry for the signalling radio bearer in the variable ESTABLISHED\_RABS; + - 2> if the variable LATEST\_CONFIGURED\_CN\_DOMAIN has been initialised and the value "Status" of the variable "INTEGRITY\_PROTECTION\_INFO" of the CN domain stored in this variable is "Started": + - 3> initialise the 20 MSB of the hyper frame number component of COUNT-I for this signalling radio bearer with the START value in the variable START\_VALUE\_TO\_TRANSMIT + - 3> set the remaining LSB of the hyper frame number component of COUNT-I for this signalling radio bearer to zero; + - 3> for this signalling radio bearer, set the IE "*Uplink RRC Message Sequence Number*" in the variable INTEGRITY\_PROTECTION\_INFO to zero. + - 3> start performing integrity protection according to sub-clause 7.18.5.1 and 7.18.5.2; + - 2> perform the actions for the IE "*RB mapping info*" as specified in sub-clause 7.19.5.9a, applied for that signalling radio bearer; +- 1> apply a default value of the IE "*RB Identity*" equal to 1 for the first IE "*Signalling RB Information To Setup*"; and +- 1> increase the default value by 1 for each occurrence. + +## 7.19.5.2 RAB Information for Setup + +If the IE "*RAB Information For Setup*" is included, the procedure is used to establish radio bearers belonging to a radio access bearer, and the MS shall: + +- 1> if several IEs "*RAB Information For Setup*" are included and the included IEs "*CN domain identity*" in the IE "*RAB Info*" does not all have the same value: + - 2> set the variable INVALID\_CONFIGURATION to TRUE; +- 1> if the radio access bearer identified with the IE "*RAB Info*" does not exist in the variable ESTABLISHED\_RABS: + - 2> create a new entry for the radio access bearer in the variable ESTABLISHED\_RABS; + - 2> store the content of the IE "*RAB Info*" in the entry for the radio access bearer in the variable ESTABLISHED\_RABS; + - 2> indicate the establishment of the radio access bearer to the upper layer entity using the IE "*CN Domain Identity*", forwarding the content of the IE "*RAB Identity*"; + - 2> calculate the START value only once during this procedure (the same START value shall be used on all new radio bearers created for this radio access bearer) according to sub-clause 7.18 for the CN domain as indicated in the IE "*CN Domain Identity*" in the IE "*RAB Info*" part of the IE "*RAB Information To Setup*"; + - 2> store the calculated START value in the variable START\_VALUE\_TO\_TRANSMIT; +- 1> for each radio bearer in the IE "*RB Information To Setup*": + - 2> if the radio bearer identified with the IE "*RB Identity*" does not exist in the variable ESTABLISHED\_RABS for another radio access bearer than the one identified with the IE "*RAB Info*": + +- 3> perform the actions specified in sub-clause 7.19; +- 3> store information about the new radio bearer in the entry for the radio access bearer identified by "RAB info" in the variable ESTABLISHED\_RABS; +- 2> if the radio bearer identified with the IE "*RB Identity*" already exists in the variable ESTABLISHED\_RABS for another radio access bearer than the one identified with the IE "*RAB Info*": + - 3> set the variable INVALID\_CONFIGURATION to TRUE. + +### 7.19.5.3 RAB Information to Reconfigure + +If the IE "*RAB Information to Reconfigure*" is included then the MS shall: + +- 1> if the entry for the radio access bearer identified by the IE "*CN Domain Identity*" together with the IE "*RAB Identity*" in the variable ESTABLISHED\_RABS already exists: + - 2> perform the action for the IE "*NAS Synchronization Indicator*", according to sub-clause 7.19.13; +- 1> else: + - 2> set the variable INVALID\_CONFIGURATION to TRUE. + +### 7.19.5.4 RB information to setup + +If the IE "*RB Information To Setup*" is included, the MS shall apply the following actions on the radio bearer identified with the value of the IE "*RB identity*". The MS shall: + +- 1> use the same START value to initialise the hyper frame number components of COUNT-C variables for all the new radio bearers to setup; +- 1> perform the actions for the IE "*PDCP Info*", if present, according to sub-clause 7.19.5.10, applied for the radio bearer; +- 1> perform the actions for the IE "*RLC Info*", according to sub-clause 7.19.5.9, applied for the radio bearer; +- 1> perform the actions for the IE "*RB Mapping Info*", according to sub-clause 7.19.5.9a, applied for the radio bearer; +- 1> if IE "*Physical Channel Configuration*" is included + - 2> perform the actions as specified in sub-clause 7.19.5.14 applied for the radio bearer; +- 1> if the IE "*Downlink RLC mode*" either in the IE "*RLC info*" or referenced by the RB identity in the IE "*Same as RB*" is set to "TM RLC": + - 2> configure delivery of erroneous SDUs in lower layers according to indication from upper layer as in 3GPP TS 24.008. +- 1> if the IE "*Uplink RLC mode*" or the IE "*Downlink RLC mode*" either in the IE "*RLC info*" or referenced by the RB identity in the IE "*Same as RB*" is set to "AM RLC" or "UM RLC": + - 2> initialise the 20 MSB of the hyper frame number component of COUNT-C for this radio bearer with the START value in the variable START\_VALUE\_TO\_TRANSMIT; + - 2> set the remaining LSB of the hyper frame number component of COUNT-C for this radio bearer to zero; + - 2> start incrementing the COUNT-C values. +- 1> if the IE "*Uplink RLC mode*" and the IE "*Downlink RLC mode*" either in the IE "*RLC info*" or referenced by the RB identity in the IE "*Same as RB*" is set to "TM RLC": + - 2> if prior to this procedure there exists no transparent mode radio bearer for the CN domain included in the IE "*CN domain identity*" in the IE "*RAB info*" in the variable ESTABLISHED\_RABS and at least one transparent mode radio bearer is included in the IE "*RB information to setup*": + +- 3> if the IE "*Status*" in the variable CIPHERING\_STATUS of the CN domain as indicated in the IE "*CN domain identity*" in the IE "*RAB info*" in the variable ESTABLISHED\_RABS is set to "Not Started": + - 4> at the activation time as specified in the IE "*Ciphering activation time for DBPSCH*" if included in the IE "*Ciphering mode info*" in the command message or, if this IE is not included, as specified in the IE "*COUNT-C activation time*" included in the response message: + - jjjj) 5> initialise the 20 most significant bits of the hyper frame number component of COUNT-C common for all transparent mode radio bearers of this CN domain with the START value in the variable START\_VALUE\_TO\_TRANSMIT; + - kkkk) 5> set the remaining LSB of the hyper frame number component of COUNT-C to zero; + - llll) 5> do not increment the COUNT-C value common for all transparent mode radio bearers for this CN domain; +- 4> if the IE "*Status*" in the variable CIPHERING\_STATUS of the CN domain as indicated in the IE "*CN domain identity*" in the IE "*RAB info*" in the variable ESTABLISHED\_RABS is set to "Started": + - 4> at the activation time as specified in the IE "*Activation Time*" in the RADIO BEARER SETUP message: + - mmmm) 5> initialise the 20 most significant bits of the hyper frame number component of COUNT-C common for all transparent mode RLC radio bearer to the value of the latest transmitted START for this CN domain, while not incrementing the value of the HFN component of COUNT-C at each TDMA frame number cycle; and; + - nnnn) 5> set the remaining LSB of the hyper frame number component of COUNT-C to zero; + - oooo) 5> start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN; + - 4> at the activation time as specified in the IE "*Ciphering activation time for DBPSCH*" if included in the IE "*Ciphering mode info*" in the command message or, if this IE is not included, as specified in the IE "*COUNT-C activation time*" included in the response message: + - pppp) 5> initialise the 20 most significant bits of the hyper frame number component of COUNT-C common for all transparent mode radio bearers of this CN domain with the START value in the variable START\_VALUE\_TO\_TRANSMIT; + - qqqq) 5> set the remaining LSB of the hyper frame number component of COUNT-C to zero; + - rrrr) 5> start incrementing the COUNT-C value common for all transparent mode radio bearers of this CN domain as normal, at each TDMA frame number cycle value, i.e. the HFN component is no longer fixed in value but incremented at each TDMA frame number cycle. +- 2> if prior to this procedure there exists at least one transparent mode radio bearer for the CN domain included in the IE "*CN Domain Identity*" in the IE "*RAB info*" in the variable ESTABLISHED\_RABS: + - 3> if the IE "*Status*" in the variable CIPHERING\_STATUS of the CN domain as indicated in the IE "*CN Domain Identity*" in the IE "*RAB info*" in the variable ESTABLISHED\_RABS is set to "Not Started": + - 4> do not increment the COUNT-C value common for all transparent mode radio bearers for this CN domain. + - 3> if the IE "*Status*" in the variable CIPHERING\_STATUS of the CN domain as indicated in the IE "*CN Domain Identity*" in the IE "*RAB Info*" in the variable ESTABLISHED\_RABS is set to " Started": + - 4> continue incrementing the COUNT-C value common for all transparent mode radio bearers of this CN domain. +- 1> if the IE "*Status*" in the variable CIPHERING\_STATUS of the CN domain as indicated in the IE "*CN Domain Identity*" in the IE "*RAB Info*" in the variable ESTABLISHED\_RABS is set to "Started": + - 2> start to perform ciphering on the radio bearer in lower layers, using the value of the IE "*RB Identity*" minus one as the value of BEARER in the ciphering algorithm. + +NOTE: The GERAN does not use the IE "*RB Information To Setup*" to setup radio bearers with RB identity in the range 1-4. + +#### 7.19.5.5 RB information to be affected + +If the IE "*RB Information To Be Affected*" is included, the MS shall apply the actions on the radio bearer identified with the value of the IE "*RB Identity*". + +#### 7.19.5.6 RB information to reconfigure + +If the IE "*RB Information To Reconfigure*" is included, the MS shall apply the following actions on the radio bearer identified with the value of the IE "*RB Identity*". The MS shall: + +- 1> perform the actions for the IE "*PDCP Info*", if present, according to sub-clause 7.19.5.10, applied for the radio bearer; +- 1> perform the actions for the IE "*RLC Info*", according to sub-clause 7.19.5.9, applied for the radio bearer; +- 1> if IE "*Physical Channel Configuration*" is included + - 2> perform the actions as specified in sub-clause 7.19.5.14 applied for the radio bearer; +- 1> perform the actions for the IE "*RB Mapping Info*", according to sub-clause 7.19.5.9a, applied for the radio bearer; +- 1> if the IE "*PDCP SN Info*" is included: + - 2> perform the actions as specified in sub-clause 7.19.5.11 applied for the radio bearer; +- 1> if the IE "*RB Stop/Continue*" is included; and + - 2> if the "*RB Identity*" has a value greater than 2; and + - 3> if the value of the IE "*RB Stop/Continue*" is "stop": + - 4> configure the RLC entity for the radio bearer to stop; + - 4> set the IE "*RB Started*" in the variable ESTABLISHED\_RABS to "stopped" for that radio bearer; + - 3> if the value of the IE "*RB Stop/Continue*" is "continue": + - 4> configure the RLC entity for the radio bearer to continue; + - 4> set the IE "*RB Started*" in the variable ESTABLISHED\_RABS to "started" for that radio bearer; + - 2> if the IE "*RB Identity*" is set to a value less than 2: + - 3> set the variable INVALID\_CONFIGURATION to TRUE. + +#### 7.19.5.7 RB Information to Release + +If the IE "*RB Information to Release*" is included, the MS shall apply the following actions on the radio bearer identified with the value of the IE "*RB Identity*". The MS shall: + +- 1> release the PDCP and RLC entities dedicated for that radio bearer; +- 1> if IE "*Physical Channel Configuration*" is included + - 2> perform the actions as specified in sub-clause 7.19.5.14 applied for the radio bearer; +- 1> if the information about the radio bearer is stored in the variable ESTABLISHED\_RABS: + - 2> delete the information about the radio bearer from the variable ESTABLISHED\_RABS; + - 2> when all radio bearers belonging to the same radio access bearer have been released: + +- 3> indicate release of the radio access bearer to upper layers providing the "CN domain identity" together with the "*RAB Identity*" stored in the variable ESTABLISHED\_RABS; +- 3> delete all information about the radio access bearer from the variable ESTABLISHED\_RABS. + +#### 7.19.5.8 RB with PDCP Information + +If the IE "*RB with PDCP Information*" is included, the MS shall apply the following actions on the radio bearer identified with the value of the IE "*RB Identity*". The MS shall: + +- 1> for the IE "*PDCP SN Info*": + - 2> perform the actions as specified in sub-clause 7.19.5.11. + +#### 7.19.5.9 (void) + +#### 7.19.5.9a RB Mapping Info + +If the IE "*RB Mapping Info*" is included, the MS shall: + +- 1> for this RB: + - 2> if a transport channel that would not exist as a result of the message (i.e. removed in the same message in IE "*Deleted DL TrCH Information*" and IE "*Deleted UL TrCH Information*") is referred to: + - 3> set the variable INVALID\_CONFIGURATION to TRUE. + - 2> for each RLC entity: + - 3> if the value of the IE "*RLC Size List*" is set to "Explicit list": + - 4> if a "Transport format set" for the transport channel is included in the same message, and the value (index) of any IE "*RLC Size Index*" in the IE "*Explicit List*" does not correspond to an "RLC size" in the IE transport format set of that transport channel given in the message; or + - 4> if a "Transport format set" for that transport channel is not included in the same message, and the value (index) of any IE "*RLC Size Index*" in the IE "*Explicit List*" does not correspond to an "RLC size" in the stored transport format set of that transport channel: + - 5> set the variable INVALID\_CONFIGURATION to TRUE. + - 3> if the value of the IE "*RLC Size List*" is set to "All": + - 4> if a "Transport format set" for the transport channel is not included in the same message: + - 5> set the variable INVALID\_CONFIGURATION to TRUE. + - 3> if the value of the IE "*RLC Size List*" is set to "Configured": + - 4> if a "Transport format set" for the transport channel for this RLC entity is included in the same message, and for none of the RLC sizes defined for that transport channel in the "Transport format set", or + - 4> if a "Transport format set" for the transport channel for this RLC entity is not included in the same message, and for none of the RLC sizes defined in the transport format set stored for that transport channel: + - 5> set the variable INVALID\_CONFIGURATION to TRUE. + - 1> if the "*RB Mapping Info*" is considered as valid according to the rules above: + - 2> delete the previously stored configuration for that radio bearer; + - 2> store the new configuration for that radio bearer; + - 2> perform the actions as specified in sub-clause 7.18.11. + +As regards the IE "*Channel Type*", the following rule should be applied to derive the DL channel type from the UL channel included in the IE: + +| Channel used in UL | DL channel type implied by "same as" | +|--------------------|--------------------------------------| +| DCH | DCH | + +### 7.19.5.10 RLC Info + +If the IE "*RLC Info*" is included, the MS shall: + +- 1> configure the transmitting and receiving RLC entities in the MS for that radio bearer accordingly. + +### 7.19.5.11 PDCP Info + +For RFC 3095: + +- 1> the chosen MAX\_CID shall not be greater than the value "Maximum Number of ROHC Context Sessions" as indicated in the IE "*PDCP Capability*"; +- 1> the configuration for the PACKET\_SIZES\_ALLOWED governs which packet sizes RFC 3095 is allowed to use. + +If IE "*PDCP Info*" is included, the MS shall: + +- 1> if the radio bearer is connected to a CS domain radio access bearer: + - 2> set the variable INVALID\_CONFIGURATION to TRUE; +- 1> if the IE "*PDCP PDU Header*" is set to the value "absent": + - 2> if the IE "*Support for Lossless SBSS Relocation*" is true: + - 3> set the variable INVALID\_CONFIGURATION to TRUE; +- 1> if the IE "*PDCP PDU Header*" is set to the value "present": + - 2> if the IE "*Support for Lossless SBSS Relocation*" is false: + - 3> if the structure "Header Compression Information" is absent: + - 4> set the variable INVALID\_CONFIGURATION to TRUE; + - 1> if the structure "Header compression information" is absent: + - 2> not use Header compression after the successful completion of this procedure; + - 2> remove any stored configuration for the structure "Header compression information". +- > if the structure "Header compression information" is present: + - 2> if RFC 2507 is used: + - 3> if the MS capability "Maximum header compression context space", as specified in 3GPP TS 25.306, is exceeded with this configuration: + - 4> set the variable INVALID\_CONFIGURATION to TRUE. + - 1> if the structure "Header compression information" is present in the reconfiguration message: + - 2> only use header compression algorithms present in the structure "Header compression information" in that message for the configured radio bearer. + - 2> use the order in which the header compression algorithms are received in the message as the order that shall be used by PDCP for mapping of PID values (see 3GPP TS 25.323) +- 1> configure the PDCP entity for that radio bearer accordingly; +- 1> configure the RLC entity for that radio bearer according to the value of the IE "*Support for Lossless SBSS Relocation*". + +- 1) set the PROFILES parameter, used by inband ROHC profile negotiation, for this PDCP entity for both UL and DL equal to the list of ROHC profiles received in the IE "*PDCP info*". A MS complying with this version of the specification shall support ROHC profiles 0x0000 (ROHC uncompressed), 0x0001 (ROHC RTP), 0x0002 (ROHC UDP) and 0x0003 (ROHC ESP) (IANA ROHC profile identifier definition). + +#### 7.19.5.11a PDCP context relocation info + +If the IE "*PDCP context relocation info*" is included, the MS shall, for each radio bearer included in this IE: + +- 1) If the IE "*Downlink RFC3095 Context Relocation Indication*" is set to TRUE: + - 2) perform the actions as specified in 3GPP TS 25.323 for all RFC3095 contexts associated to that radio bearer in the downlink; +- 1) If the IE "*Uplink RFC3095 Context Relocation Indication*" is set to TRUE: + - 2) perform the actions as specified in 3GPP TS 25.323 for all RFC3095 contexts associated to that radio bearer in the uplink. + +#### 7.19.5.12 PDCP SN Info + +If the IE "*PDCP SN Info*" is included, the MS shall: + +- 1) transfer the sequence number to the PDCP entity for the radio bearer; +- 1) configure the RLC entity for the radio bearer to stop; +- 1) include the current PDCP receive sequence number and the radio bearer identity for the radio bearer in the variable PDCP\_SN\_INFO. + +#### 7.19.5.13 NAS Synchronisation Indicator + +If the IE "*NAS Synchronisation Indicator*" is present in a message, the MS shall: + +- 1) forward the content to upper layers along with the IE "*CN Domain Identity*" of the associated RAB stored in the variable ESTABLISHED\_RABS at the CFN indicated in the IE "*Activation Time*" in order to synchronise actions in NAS and AS. + +#### 7.19.5.14 Physical Channel Configuration + +If the IE "*Physical Channel Configuration*" is included, the MS shall: + +- 1) if the IE "*SBPSCH Description*" is included; + - 2) perform the action specified in 7.19.6.2; + - 2) start timer T3190. +- 1) if the IE "*DBPSCH Description*" is included; + - 1) perform the action specified in 7.19.6.1; + +### 7.19.6 Physical channel parameters + +#### 7.19.6.1 DBPSCH Description + +If the MS receives the one of the messages RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE or CELL UPDATE CONFIRM message and if IE "*Power Command*" is present, the MS shall: + +- 1) set the power level accordingly for the initial power on the new channel(s) and it shall not affect the power used on the old channel(s). + +else set the INVALID\_CONFIGURATION to TRUE, in case that MS enters the RRC-Cell\_Dedicate state-MAC-Dedicated state. + +If the IE "*Mode of the First Channel*" to be applied corresponds to a multi-rate speech codec in one of the messages RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE or CELL UPDATE CONFIRM message shall contain the MultiRate Configuration IE, then the MS shall: + +- 1> expect the IE *MultiRate Configuration* and ; +- 1> if it is initial establishment the MS shall: + - 2> use the Initial Codec Mode specified in the IE *MultiRate Configuration* +- 1> otherwise apply the implicit rule defined in 3GPP TS 45.009. + +else: + +- 1> set the INVALID\_CONFIGURATION to TRUE and; +- 1> remain on the current channel(s) and use the old Channel Description or Channel Mode(s). + +If the value of IE *MultiRate Configuration* is inconsistent the MS shall: + +- 1> set the INVALID\_CONFIGURATION to TRUE; +- 1> remain on the current channel(s) and use the old Channel Description or Channel Mode(s). + +The IE *MultiRate Configuration* shall be considered as inconsistent by the MS if: + +- the active set does not include any codec mode or the active set includes more than four codec modes; or +- one or more codec modes of the active codec set are not supported by the physical channel; or +- the threshold and hysteresis values are not set according to requirements given in 3GPP TS 45.009. + +If the MS receives one of the messages RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION RADIO BEARER RELEASE or CELL UPDATE CONFIRM and + +- 1> if the message contains only the description of a channel to be used after the starting time in the IE "*Description of the Channel After Time*", the MS shall: +- 1> wait until the starting time before accessing the channel: + +else: + +- 1> if the starting time already elapsed, the MS shall: + - 2> access the channel as an immediate reaction to the reception of the message (see 3GPP TS 45.010 for the timing constraints). +- 1> if the message contains both the description of a channel to be used after the indicated time and the description of a channel to be used before the indicated time, in the IEs "*Description of the Channel, After Time*" and "*Description of the Channel, Before Time*", the MS may: + - 2> access the channel immediately after the reception of the message. + - 2> if the moment, at which the mobile station is ready to access, is before the time indicated by the IE "*Description of the Channel, After Time*", the mobile station shall: + - 3> access the channels as described in the IE "*Description of the Channel, Before The Starting Time*". + - 3> then change to the channel described for after the starting time at the indicated time. New parameters shall be frequency list, MAIO and HSN. Other parameters describing the allocated channels must be identical to the parameters described in the IE "*Description of the Channel, Before The Starting Time*". If the moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described in the IE "*Description of the Channel, Before The After Time*". +- 1> if the IE "*Starting Time*" is not present and some of the information elements referring to before the starting time is present, these information elements shall be considered as IEs unnecessary in the message. + +- 1> if the IE "*Description of the Channel, Before Time*" is not present, the MS shall: + - 2> apply the channel description for before the time, if needed, given by the IE "*Description of the Channel, After Time*". +- 1> if the IE "*Starting Time*" is present and the IE "*Description of the Channel, before time*" indicates frequency hopping, one and only one of the following information elements may be present and the MS shall apply this before the starting time + - IE "*Mobile Allocation, Before Time*"; + - IE "*Frequency List, Before Time*"; + - IE "*Frequency Channel Sequence, Before Time*". +- 1> if the IE "*Starting Time*" is present and the IE "*Channel Description, Before The Starting Time*" indicates frequency hopping, and none of the above mentioned IE is present, + - 2> the IE "*Frequency List, After Time*" must be present, and this applies also for before the starting time. + - 2> if frequency hopping is applied, the cell allocation if present in the message is used to decode the mobile allocation. If the cell allocation is not included, the mobile station shall use its current cell allocation. +- 1> if the RADIO BEARER RECONFIGURATION message contains only the IE "*Description of the Channel, After Time*" and the handover is towards a GERAN cell to which the mobile station is not synchronised for the case of an intersystem handover to GERAN, the mobile station shall: + - 2> wait up to the starting time before accessing the new channel; + - 2> if the starting time has already elapsed, the mobile shall: + - 3> access the new channel as an immediate reaction to the reception of the message (see 3GPP TS 45.010 for the timing constraints). Between the reception of the RADIO BEARER RECONFIGURATION and the starting time there is no requirement for the mobile station to receive or transmit on the old channel. + +If MS receives the RADIO BEARER RECONFIGURATION and the IE "*Power Command and Access Type*" is present, the MS shall: + +- 1> set the initial power on the new channel (s) to the the power level defined in this power command (cf 3GPP TS 45.008). It shall not affect the power used on the old channel(s). + +else + +- 1> set the variable INVALID\_CONFIGURATION to TRUE. + +If MS receives the RADIO BEARER RECONFIGURATION and if the IE "*Handover Reference*" is present, the MS shall: + +- 1> use handover reference value used for access identification. The choice of the handover reference by the network is out of the scope of this specification and left to the manufacturers. + +else + +- 1> set the variables INVALID\_CONFIGURATION to TRUE. + +If MS receives the RADIO BEARER RECONFIGURATION and if the IE "*Synchronization Indication*" is not be present then, the MS shall: + +- 1> assume the handover type is non-synchronized. + +If MS receives the RADIO BEARER RECONFIGURATION and if the IE "*Timing Advance*" is present then the MS shall: + +- 1> use this in the new cell; + +- 1> if in the case of a synchronous or pseudo-synchronous handover the MS knows that the timing advance with the new cell is out of range, i.e. is bigger than the maximum timing advance that can be coded as specified in 3GPP TS 44.004, and if the new cell does not accept out of range timing advance as indicated in the RADIO BEARER RECONFIGURATION message, the mobile station shall: +- 2> set the variable INVALID\_CONFIGURATION to TRUE. + +If the mobile station receives a RADIO BEARER RECONFIGURATION message and if at least one of the following IEs, IE "*Handover Reference*", IE "*Power Command and Access Type*", IE "*Cell Description*" and IE "*Description of the first channel after time*" is not present, the MS shall: + +- 1> set the variable INVALID\_CONFIGURATION to TRUE. + +If the MS receives RADIO BEARER RECONFIGURATION and the IE "*Starting Time*" may be present, then the MS shall: + +- 1> change the frequency parameters of the channels more or less at the moment a change of channel occurs. In this case a number of parameters can be included. + +If the MS receives RADIO BEARER RECONFIGURATION and if the IE "*Starting Time*" is present and none of the information elements referring to before the starting time are present, the mobile station shall: + +- 1> wait and access the channels at the indicated time. + +If the MS receives RADIO BEARER RECONFIGURATION and if the IE "*Starting Time*" is present and at least one of the information elements referring to before the starting time is present, the mobile station shall: + +- 1> not wait for the indicated time and access the channel using the frequency parameters for before the starting time. + +If the MS receives RADIO BEARER RECONFIGURATION and if the IE "*Starting Time*" is not present and some of the information elements referring to before the starting time are present, these information elements shall be considered as IEs unnecessary in the message. + +If the MS receives RADIO BEARER RECONFIGURATION and if the IE "*Description of the First Channel, Before Time*" is not present, the MS shall: + +- 1> apply for the channel description the information given for before the time, if needed, in the IE "*Description of the First Channel, After Time*". + +If the MS receives RADIO BEARER RECONFIGURATION and if the IE "*Description of the Second Channel, After Time*" is present, and if the IE "*Description of the Second Channel, Before Time*" not present, and a description of the configuration for before the time needed, the MS shall: + +- 1> use the channel configuration before the starting time, and the channel description to apply to the second channel before the starting time is given by the IE "*Description of the Second Channel, After Time*". + +If the MS receives RADIO BEARER RECONFIGURATION and if the IE "*Starting Time*" is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, one and only one of the following information elements may be present and applies before the starting time to all assigned channels: + +- IE "*Mobile Allocation, Before Time*"; +- IE "*Frequency Short List, Before Time*"; +- IE "*Frequency List, Before Time*"; +- IE "*Frequency Channel Sequence, Before Time*". + +If the IE "*Starting Time*" is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, and if none of the above mentioned IE is present, the MS shall use: + +- 1> a frequency list for after the starting time must be present, and this list applies also for the channels before the starting time. + +If MS receives the RADIO BEARER RECONFIGURATION and if at least one of the channel descriptions for after time indicates frequency hopping, one and only one of the following information elements shall be present IE "Frequency Channel Sequence, After Time", IE "Frequency List, After Time", IE "Frequency Short List, After Time", IE "Mobile Allocation, After Time". + +If MS receives the RADIO BEARER RECONFIGURATION and if neither of the *Channel Description* IEs indicate frequency hopping, and if they are not required for the decoding of *Channel Description* IEs for before time, and if any of the four information elements are present they shall be considered as IEs unnecessary in the message. + +The IE "Frequency Channel Sequence" element shall not be used unless all the ARFCNs that it indicates are in the P-GSM band. + +If the RADIO BEARER RECONFIGURATION message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall: + +- l> set the variable UNSUPPORTED\_CONFIGURATION to TRUE; +- l> remain on the current channel(s). + +If the mobile station receives a RADIO BEARER RECONFIGURATION message with a IE "Frequency List" or IE "Frequency Short List" indicating frequencies that are not all in one band, then the mobile station shall: + +- l> stay on the current channel(s); and +- l> set the variable UNSUPPORTED\_CONFIGURATION to TRUE. + +If MS receives the one of the messages RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE or CELL UPDATE CONFIRM message and if the IE "Frequency List, After Time" or IE "Frequency List, Before Time" is present, then MS shall: + +- l> change the frequency according with the values of the IEs. + +If the MS receives the reconfiguration message and if IE "Cell Channel Description" is present in the message and if the frequency hopping is applied, the MS may decode the mobile allocation based on the cell allocation, if present in the message. + +The network shall include the IE "Cell Channel Description" in the RADIO BEARER RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RELEASE or CELL UPDATE CONFIRM message if no proper reference cell frequency list (CA) has been sent previously to the mobile station. + +If MS receives in the RADIO BEARER RECONFIGURATION message which contains the "Cell Channel Description" IE or "Channel Mode" IE which instruct the mobile station to use a Channel Description or Mode that it does not support, or the Channel Mode indicated for use is not defined for all channel sets, then the MS shall: + +- l> set the variable UNSUPPORTED\_CONFIGURATION to TRUE +- l> remain on the current channel(s) and use the old Channel Description or Mode(s). + +If the cell allocation is not included, the mobile station shall use its current cell allocation, the current CA is the last CA received. If the mobile station receives RADIO BEARER RECONFIGURATION message with a IE "Mobile Allocation" indexing frequencies that are not all in one band and a IE "Starting Time" indicating a time that has not elapsed then the mobile station shall: + +- l> remain on the current channel(s). +- l> send a RRC STATUS message with cause "frequency not implemented"; +- l> set the variable INVALID\_CONFIGURATION to TRUE. + +If the mobile station receives a RADIO BEARER RECONFIGURATION message with a IE "Mobile Allocation" indexing frequencies that are not all in one band and a "Starting Time" IE indicating a time that has elapsed, then the mobile station shall locally abort the radio connection and, if permitted, attempt Call Re-establishment. + +If the MS receives the RADIO BEARER RECONFIGURATION message and if IE "Cell Description" is included in the message then MS shall: + +1> use its pre-knowledge about synchronization acquired by the measurement process (i.e. BSIC + BCCH frequency) + +else + +1> set the variable INVALID\_CONFIGURATION to TRUE. + +If the MS receives the RADIO BEARER RECONFIGURATION and if the IE "*Real Time Difference*" is included then the MS shall: + +1> apply the pseudo-synchronous case type of handover. + +If the MS receives the RADIO BEARER RECONFIGURATION and if the IE "*Timing Advance*" is included then the MS shall: + +1> if IE "*Synchronization Indication*" indicates a presynchronized handover, use presynchronized type of handover. + +1> else + +2> if IE "*Synchronization Indication*" not indicates a presynchronized handover, use the default value as defined in 3GPP TS 45.010. The MS shall consider an unnecessary information element for other types of handover. + +The "*Dynamic ARFCN*" IE shall only be included if the network supports dynamic ARFCN mapping and there is a need to define new dynamic ARFCN mapping, e.g. at handover to another PLMN or from another RAT to GSM. This information replaces any previously received information about dynamic ARFCN mapping. After returning to idle mode or packet idle mode, the mobile station shall acquire new dynamic ARFCN mapping information, except for the cases specified in 3GPP TS 44.018 (SI15). This mapping shall apply to any ARFCN used in the RADIO BEARER RECONFIGURATION message. + +When one of the reconfiguration messages or CELL UPDATE CONFIRM message is received and IE "*PDTCH*" is included, the MS shall + +1> set the structure "Dynamic Allocation" as specified in 3GPP TS 44.160, and + +1> if the MS is EGPRS capable + +2> set the IE *EGPRS Window Size* as specified in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060 for each RB. + +If the MS receives one of the RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE or CELL UPDATE CONFIRM messages and if the structure "*FLO Basic Physical Channels Parameters*" is present in the IE "*DBPSCH*", the MS shall: + +1> not use "*Channel Mode*" IE and "*Channel Mode2*" IE; and + +1> apply the channel description given by the IE "*Mode*", IE "*Modulation*" and IE "*Interleaving*". + +If the MS receives one of the RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE or CELL UPDATE CONFIRM messages and if the structure "*FLO Basic Physical Channels Parameters*" is present in the IE "*DBPSCH*" and none of the IE "*Mode*", IE "*Modulation*" and IE "*Interleaving*" is present then the MS shall: + +1> set the variable INVALID\_CONFIGURATION to TRUE. + +If the MS receives one of the RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE or CELL UPDATE CONFIRM messages and if the struct "*FLO*" is present in the IE "*DBPSCH*", for each timeslot the MS shall: + +1> if one of the FLO IEs is present (IE "*UL TrCH Information Common For All Transport Channels*", IE "*Deleted UL TrCH Information*", IE "*Added or Reconfigured UL TrCH Information*", IE "*DL TrCH Information Common For All Transport Channels*", IE "*Deleted DL TrCH Information*" or IE "*Added or Reconfigured DL TrCH Information*"): + +2> set the transport channels parameters as defined in sub-clause 7.19. + +If the MS receives one of the RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE or CELL UPDATE CONFIRM messages and if the struct "FLO " is present in the IE "DBPSCH" and if one of the TrCH IEs ("UL TrCH Information Common For All Transport Channels", IE "Deleted UL TrCH Information", IE "Added or Reconfigured UL TrCH Information", IE "DL TrCH Information Common For All Transport Channels", IE "Deleted DL TrCH Information" or IE "Added or Reconfigured DL TrCH Information") instructs the MS to use a TrCH configuration not supported, the MS shall: + +1> set the variable INVALID\_CONFIGURATION to TRUE. + +If the MS receives one of the RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION RADIO BEARER RELEASE or CELL UPDATE CONFIRM messages and if the IE "FLO Basic Physical Channels Parameters" is present in the IE "DBPSCH" and if one of the FLO IEs ( IE "Mode", IE "Modulation" or IE "Interleaving") instructs the MS to use a configuration not supported, the MS shall: + +1> set the variable INVALID\_CONFIGURATION to TRUE. + +### 7.19.6.2 SBPSCH parameters + +The reconfiguration message can contain either the description of the uplink TBF or the downlink TBF. The information on the power to be used on the target TBF shall not affect the power used on the old channel(s). The network may assign a radio resource on one or more PDCHs to be used for the TBF. The amount of radio resource to be reserved is a network dependent choice. + +The IE "SBPSCH Description" message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions. + +If MS receives the one of the messages RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION RADIO BEARER RELEASE message and the message includes either IE "RRC Packet Uplink Assignment" or IE "RRC Packet Downlink Assignment" the MS shall: + +1> set the parameters for uplink or downlink TBF. The information on the power to be used on the target TBF shall not affect the power used on the old channel(s). + +else + +1> set the INVALID\_CONFIGURATION to TRUE. + +The RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions. If the MS is in RRC-Cell\_Dedicated state, MAC Dedicated or MAC DTM state and if MS receives the reconfiguration message and if the message contains only the description of a TBF to be used after the starting time, the mobile station shall + +1> wait until the starting time before using the TBF. + +1> if the starting time has already elapsed, the mobile shall: + +2> use the TBF immediately after the reception of the message (see 3GPP TS 45.010 for the timing constraints). + +1> if the message contains both the description of a TBF to be used after the indicated time and of a TBF to be used before, the mobile station shall: + +2> use the TBF as an immediate reaction to the reception of the message. + +1> if the moment the mobile station is ready to access is before the indicated time, the mobile station shall: + +2> use the TBF described for before the starting time. + +2> the mobile station shall then change to the TBF described for after the starting time at the indicated time. New parameters shall be frequency list, MAIO and HSN. Other parameters describing the allocated channels shall be identical to the parameters described for before the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station shall the TBF described for after the starting time. + +## 7.19.7 Transport channel information elements + +### 7.19.7.1 Transport Format Set + +If the IE "*Transport Format Set*" is included, the MS shall: + +- 1> if that RB is using AM and the set of RLC sizes applicable to the RLC entity transferring data PDUs has more than one element not equal to zero: + - 2> keep the transport format set if this exists for that transport channel; + - 2> set the variable INVALID\_CONFIGURATION to TRUE. +- 1> if the total number of configured transport formats for the transport channel exceeds maxTF: + - 2> keep the transport format set if this exists for that transport channel; + - 2> set the variable INVALID\_CONFIGURATION to TRUE. +- 1> if the IE "*Transport Format Set*" is considered as valid according to the rules above: + - 2> remove a previously stored transport format set if this exists for that transport channel; + - 2> store the transport format set for that transport channel; + - 2> if the IE "*Transport format Set*" has the choice "Transport channel type" set to "Dedicated transport channel": + - 3> calculate the transport block size for all transport formats in the TFS using the following + + +| | | +|------------------------------|-------------------------| +| TB size = RLC/MAC block size | if "RLC size" $\neq$ 0, | +| TB size = 0 | if "RLC size" = 0, | + + where: + - RLC/MAC block size is calculated according to 3GPP TS 44.160. + - 'RLC size' reflects the RLC PDU size. + - 2> if the IE "*Transport Format Set*" contains IE "*Semi-static Transport Format Information*" then: + - 3> set the values of CRC size to 0,6,12 or 18 and the Rate matching attribute any value between 1 and 256. + - 2> else: + - 3> set the variable INVALID\_CONFIGURATION to TRUE. + - 2> if the *Transport Block Size* $\neq$ 0 and IE "*RLC size*" = 0, no RLC PDU data exists but only parity bits exist for that transport format; + - 2> if the *Transport Block Size* = 0, neither RLC PDU neither data nor parity bits exist for that transport format; +- 1> perform the actions as specified in sub-clause 7.18.21. + +### 7.19.7.2 Transport format combination set + +If the IE "*Transport Format Combination Set*" is included, the MS shall for that direction (uplink or downlink): + +- 1> store the new transport format combination set, or (if this exists) modify a previously stored transport format combination set according to IEs included in IE "*Transport Format Combination Set*"; +- 1> start to respect those transport format combinations; + +If for a given TFCS in a given direction the size of the TFCI is changed during reconfiguration, the network shall assign a new DBPSCH where the TFCS will apply in the same direction after reconfiguration. A new DBPSCH is a DBPSCH on which the TFCS did not apply prior to reconfiguration. + +If the IE "*Transport Format Combination Set*" is included and the TFCI size is changed the MS shall: + +- 1) perform the TFCS reconfiguration of DBPSCH according to IEs included in IE "*Transport Format Combination Set*". + +If the IE "*Transport Format Combination Set*" is not included and if there is no addition, removal or reconfiguration of transport channels, the MS shall for that direction (uplink or downlink): + +- 1) use a previously stored transport format combination set if this exists. + +If the IE "*Transport Format Combination Set*" is not included; and + +- 1) if no transport format combination set is stored in the MS; or +- 1) if transport channels are added or removed in the message; or +- 1) if any transport channel is reconfigured in the message such that the size of the transport format set is changed: + +the MS shall: + +- 1) set the variable INVALID\_CONFIGURATION to TRUE. + +In the uplink TFCS the minimum set of TFCs is the set of TFCs that is needed for the TFC selection algorithm defined in 3GPP TS 44.160. The minimum set of TFCs consists of the following: + +- 1) for each RLC UM entity: + - 2) a TFC with one transport block for this transport channel and empty TFs for all the others. If more than one TFC fulfils this criteria, only the TFC with the lowest number of bits should be included in the minimum set of TFCs. +- 1) for each RLC AM entity: + - 2) a TFC with a non-empty TF for the corresponding transport channel and empty TFs for all other transport channels, where the non-empty TF includes one transport block with "Configured RLC Size" equal to the RLC PDU size. +- 1) for each RLC TM entity: + - 2) a TFC with non-empty TFs for the corresponding transport channel, and empty TFs for all other transport channels, where: + - 3) for RLC TM entity the non-empty TFs include, for the smallest SDU size that can be received in a single TTI from higher layer: + - 4) a TF with non-zero number of transport blocks with "Configured RLC Size" equal to the corresponding SDU size. If more than one TFC fulfils this criteria, only the TFC with the lowest number of bits in the TFC is included in the minimum set of TFCs. +- 1) an "empty" TFC. + +Furthermore, the GERAN should ensure that the uplink TFCS satisfies the following rules: + +- 1) for the TTI length with which at least one transport channel is configured: + - 2) for each combination of TFs for the transport channels configured with this TTI length included in the TFCS: + - 3) a TFC with these TFs for the transport channels configured with this TTI length and empty TFs on all transport channels configured with the TTI length is also included in the TFCS. + +### 7.19.7.3 (void) + +### 7.19.7.4 Added or Reconfigured UL TrCH information + +If the IE "*Added or Reconfigured UL TrCH Information*" is included then the MS shall: + +- 1) for the transport channel identified by the IE "*UL Transport Channel Identity*" and IE "*Uplink Transport Channel Type*": + +2> perform the actions for the IE "*Transport Format Set*" as specified in sub-clause 7.19.7.1. + +#### 7.19.7.5 Added or Reconfigured DL TrCH information + +If the IE "*Added or Reconfigured DL TrCH Information*" is included then for the transport channel identified by the IE "*DL Transport Channel Identity*" the MS shall: + +- 1> if the choice "DL parameters" is set to 'explicit': + - 2> perform the actions for the IE "*Transport Format Set*" as specified in sub-clause 7.19.7.1. +- 1> if the choice "DL parameters" is set to 'same as uplink': + - 2> if the IE "*UL Transport Channel Identity*" indicates an existing or a new UL Transport Channel: + - 3> store as transport format for this transport channel the transport format associated with the transport channel identified by the IE "*UL Transport Channel Identity*". + - 2> else: + - 3> set the variable INVALID\_CONFIGURATION to TRUE. + +#### 7.19.7.6 Deleted UL TrCH information + +If the IE "*Deleted UL TrCH Information*" is included the MS shall: + +- 1> delete any information about the transport channel identified by the IE "*UL TrCH Identity*" and IE "*Uplink Transport Channel Type*". + +#### 7.19.7.7 Deleted DL TrCH information + +If the IE "*Deleted DL TrCH Information*" is included the MS shall: + +- 1> delete any information about the transport channel identified by the IE "*DL TrCH Identity*" as applicable. + +#### 7.19.7.8 UL TrCH information common for all transport channels + +If the IE "*UL TrCH Information Common For All Transport Channels*" is included the MS shall: + +- 1> perform actions for the IE "*UL DCH TFCS*" as specified in sub-clause 7.19.7.2. + +#### 7.19.7.9 DL TrCH information common for all transport channels + +If the IE "*DL TrCH Information Common For All Transport Channels*" is included the MS shall: + +- 1> if the IE "*DL DCH TFCS*" is included: + - 2> perform actions as specified in sub-clause 7.19.7.2. + +The IE "*DL TrCH Information Common For All Transport Channels*" shall always include a DL DCH TFCS configuration, either by including the IE "*DL DCH TFCS*" or by specifying that the TFCS is the same as in UL. If GERAN does not require the reconfiguration of the concerned parameters, GERAN may replace one TFC with the value that is already assigned for this IE. + +#### 7.19.7.10 TFCS Reconfiguration/Addition Information + +If the IE "*TFCS Reconfiguration/Addition Information*" is included the MS shall: + +- 1> store the TFCs to be reconfigured/added indicated in the IE "*CTFC Information*" as specified below; + +In order to identify the TFCs included in this IE the MS shall calculate the CTFC as specified in clause 11. + +If the IE "*TFCS Reconfiguration/Addition Information*" is used in case of TFCS "Complete reconfiguration" the MS shall: + +- 1> remove a previously stored transport format combination set if this exists; + +- 1> consider the first instance of the IE "*CTFC Information*" as Transport Format Combination 0 (TFCI=0) + +If the IE "*TFCS Reconfiguration/Addition Information*" is used in case of TFCS "Addition" the MS shall insert the new additional(s) TFC into the first available position(s) in ascending TFCI order in the TFCS. + +#### 7.19.7.11 TFCS Removal Information + +If the IE "*TFCS Removal Information*" is included the MS shall: + +- 1> remove the TFCs indicated by the IE "*TFCI*" from the current TFCS, and mark these positions (TFCI) in the TFCS as vacant. +- 2> if "*Compression Algorithm*" flag is set to one and if the size of the TFCI can be reduced as a result of removing the vacant TFCIs, then the TFCI values shall be shifted as follows: + + +For $\text{TFCI}_{\text{loop}}=1$ on FR channels and 2 on HR channels, to (Number of non vacant positions in the TFCS - 1) + +If $\text{TFCI}_{\text{loop}}$ is vacant then + +Assign to $\text{TFCI}_{\text{loop}}$ the first remaining TFC for which the assigned TFCI > $\text{TFCI}_{\text{loop}}$ and then mark the position of that TFC (TFCI) as vacant. + +End if. + +End for. +- 2> if "*Compression Algorithm*" flag is set to zero then no shift shall be applied. + +NOTE: whether the size of the TFCI can be reduced or not can easily be assessed by: + +If TFC is used for SRB data transfer and layer 2 signalling as defined in section 11.5 it shall not be removed. + +If the MS receives one of the messages RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION or RADIO BEARER RELEASE and if the IE "*TFCS Removal Information*" is present and if the IE instructs the mobile station to remove a TFCI which is not existent or it is used for signalling as defined in subclause 11.5 then the MS shall: + +- 1> remain on the current channel(s). +- 1> set the variable INVALID\_CONFIGURATION to TRUE. +- 1> send failure message (RADIO BEARER SETUP FAILURE or RADIO BEARER RECONFIGURATION FAILURE or RADIO BEARER RELEASE FAILURE) as it is described in subclause 7.14.1.9. + +#### 7.19.7.12 TFCS Explicit Configuration + +If the IE "*TFCS Explicit Configuration*" is included the MS shall: + +- 1> if the IE choice "*TFCS Representation*" is set to 'complete reconfiguration': + - 2> perform the actions for the IE "*TFCS Reconfiguration/Addition Information*" as specified in sub-clause 7.19.7.10. +- 1> if the IE choice "*TFCS Representation*" is set to 'addition': + - 2> perform the actions for the IE "*TFCS Reconfiguration/Addition Information*" as specified in sub-clause 7.19.7.10. +- 1> if the IE choice "*TFCS Representation*" is set to 'removal': + - 2> perform the actions for the IE "*TFCS Removal Information*" as specified in sub-clause 7.19.7.11. +- 1> if the IE choice "*TFCS Representation*" is set to 'replace': + - 2> perform first the actions for the IE "*TFCS Removal Information*" as specified in sub-clause 7.19.7.11; and then + +2> perform the actions for the IE "*TFCS Reconfiguration/Addition Information*" as specified in sub-clause 7.19.7.10. + +--- + +## 8 Handling of unknown, unforeseen, and erroneous protocol data + +### 8.1 General + +This sub-clause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to provide recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocol. + +The error handling procedures specified in this sub-clause shall apply to all RRC messages. When there is a different handling for the same message received on different logical channels, this is specified. + +For system information, the error handling procedures applied on system information messages are specified below. + +When the MS receives an RRC message, it shall set the variable `PROTOCOL_ERROR_REJECT` to `FALSE` and then perform the checks in the order as defined below. + +The error cases specified in the following include handling upon reception of spare values. This behaviour also applies in case the actual value of the IE results from mapping the originally sent IE value. Moreover, in certain error cases, as specified in the following, default values apply. In this case, the default values specified within the procedure specifications apply. + +The procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity for the ASN1 coded messages (`CELL UPDATE`, `GRA UPDATE` and `GRA UPDATE CONFIRM`) sent on the `SRB2` and IEs are following the rules defined in 3GPP TS 25.331. + +### 8.2 CSN.1 violation or encoding error + +If the MS receives an RRC message on `SRB 2`, `SRB 3` or `SRB 4` for which the encoded message does not result in any valid syntax value (or "encoding error"), it shall perform the following. The MS shall: + +- 1> set the variable `PROTOCOL_ERROR_REJECT` to `TRUE`; +- 1> transmit an RRC `STATUS` message on `SRB2`. The IE "*Protocol Error Information*" shall contain an IE "*Protocol Error Cause*" set to "CSN.1 violation or encoding error"; +- 1> when RRC `STATUS` message has been submitted to lower layers for transmission: + - 2> continue with any ongoing processes and procedures as if the invalid message had not been received. + +If the MS receives an RRC message sent via a radio access technology other than `GERAN`, for which the encoded message does not result in any valid syntax, the MS shall: + +- 1> set the variable `PROTOCOL_ERROR_REJECT` to `TRUE`; +- 1> set the IE "*Protocol Error Cause*" in the variable `PROTOCOL_ERROR_INFORMATION` to "CSN.1 violation or encoding error"; +- 1> perform procedure specific error handling according to clause 7. + +If a set of system information message received on `SRB 1` does not result in any valid syntax value, the MS shall: + +- 1> ignore the set of system information message; +- 1> treat the other sets of this system information message as if those sets were not present. + +If the MS receives an RRC message on `SRB 1` for which the encoded message does not result in any valid syntax value, it shall ignore the message. + +If the MS receives an RRC message on SRB 2 and if the RRC message is coded in ASN1 then MS shall follow the rules defined in 3GPP TS 25.331 for the DL messages sent on the DCCH. + +If the MS receives an RRC message sent on SRB2 or via a radio access technology other than GERAN, and the RRC message is coded in ASN1 for which the encoded message does not result in any valid syntax, the MS shall: + +- 1> set the variable PROTOCOL\_ERROR\_REJECT to TRUE; +- 1> set the IE "*Protocol Error Cause*" in the variable PROTOCOL\_ERROR\_INFORMATION to "CSN.1 violation or encoding error"; +- 1> perform procedure specific error handling according to clause 7. + +## 8.3 Unknown or unforeseen message type + +If a MS receives an RRC message on a SRB 2, SRB 3 or SRB 4 with a message type not defined for that SRB it shall: + +- 1> set the variable PROTOCOL\_ERROR\_REJECT to TRUE; +- 1> transmit an RRC STATUS message on SRB 2. The IE "*Protocol Error Information*" shall contain an IE "*Protocol Error Cause*" set to "Message type non-existent or not implemented"; +- 1> when the RRC STATUS message has been submitted to lower layers for transmission: + - 2> continue with any ongoing processes and procedures as if the invalid message had not been received. + +If the MS receives an RRC message on SRB 1 with a message type not defined for the logical channel type the message was received on, it shall ignore the message. + +**If the MS receives an RRC message on SRB2 with message type not defined for that SRB and if the RRC message is coded in ASN1 then MS shall follow the rules defined in 3GPP TS 25.331 for the DL messages sent on the DCCH.** + +## 8.4 Unsolicited received message + +If the MS receives any of the following messages, on SRB 2: + +- an RRC CONNECTION SETUP message addressed to the MS; or +- an RRC CONNECTION REJECT message addressed to the MS; or +- a MS CAPABILITY INFORMATION CONFIRM message; or +- a CELL UPDATE CONFIRM message addressed to the MS; or +- a GRA UPDATE CONFIRM message addressed to the MS + +and no procedure is ongoing according to clause 7 which expects the message to be received: + +the MS shall: + +- 1> ignore the received message. + +## 8.5 Unexpected critical message extension + +If the MS receives an RRC message on SRB 2, SRB 3 or SRB 4, or sent via a radio access technology other than GERAN, containing an undefined critical message extension indicated with the error label: 'Critical extension', the MS shall: + +- 1> set the variable PROTOCOL\_ERROR\_REJECT to TRUE; +- 1> set the IE "*Protocol Error Cause*" in the variable PROTOCOL\_ERROR\_INFORMATION to "Message extension not comprehended"; + +- 1) if the IE "*Message Type*" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: + - 2) store the IE "*Message Type*" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and + - 2) set the IE "*RRC Transaction Identifier*" to zero in that table entry. +- 1) perform procedure specific error handling according to clause 7. + +If the MS receives an RRC message on the SRB 1, containing an undefined critical message extension, the MS shall: + +- 1) ignore the message. + +## 8.6 Message with error label: 'Content part error' + +If the MS receives an RRC message containing the error label: 'Content part error', the MS shall: + +- 1) set the variable PROTOCOL\_ERROR\_REJECT to TRUE; +- 1) set the IE "*Protocol Error Cause*" in the variable PROTOCOL\_ERROR\_INFORMATION to "Message content part error"; +- 1) if the IE "*Message Type*" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS: + - 2) store the IE "*Message Type*" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and + - 2) set the IE "*RRC Transaction Identifier*" to zero in that table entry; +- 1) ignore the data corresponding to the description following the error label; +- 1) perform procedure specific error handling according to clause 7. + +## 8.7 Unknown or unforeseen information element value, mandatory information element + +If the MS receives an RRC message on SRB 2, SRB 3 or SRB 4, or sent via a radio access technology other than GERAN, with a mandatory IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the MS shall: + +- 1) if a default value of the IE is defined in the procedure: + - 2) treat the rest of the message using the default value of the IE. +- 1) if no default value of the IE is defined in the procedure: + - 2) set the variable PROTOCOL\_ERROR\_REJECT to TRUE; + - 2) set the IE "*Protocol Error Cause*" in the variable PROTOCOL\_ERROR\_INFORMATION to "Information element value not comprehended"; + - 2) perform procedure specific error handling according to clause 7. + +If the MS receives a system information message on SRB 1 with a mandatory IE having a value reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the MS shall: + +- 1) if a default value of the IE is defined in the procedure: + - 2) treat the rest of the system information message using the default value of the IE. +- 1) if no default value of the IE is defined in the procedure: + - 2) ignore the system information message. + +If the MS receives an RRC message on SRB 1 with a mandatory IE having a value reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the MS shall: + +- 1) if a default value of the IE is defined in the procedure: + - 2) treat the rest of the message using the default value of the IE. +- 1) if no default value of the IE is defined in the procedure: + - 2) ignore the message. + +If the MS receives an RRC message on SRB 2 or sent via a radio access technology other than GERAN, with a mandatory IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value) and if the RRC message is coded in ASN1 then MS shall follow the rules defined in 3GPP TS 25.331 for the DL messages sent on the DCCH. + +## 8.8 Unexpected non-critical message extension + +If the MS receives an RRC message on the SRB 2, SRB 3 or SRB 4, or sent via a radio access technology other than GERAN, containing an undefined non-critical message extension, the MS shall: + +- 1) ignore the content of the extension and the message contents after the extension, but treat the parts of the message up to the extension normally. + +If the MS receives an RRC message on the SRB 1, containing an undefined non-critical message extension, the MS shall: + +- 1) ignore the content of the extension and the message contents after the extension, but treat the parts of the message up to the extension normally. + +If the MS receives an RRC message on the SRB 2, or sent via a radio access technology other than GERAN, containing an undefined non-critical message extension and if the RRC message is coded in the ASN1 then MS shall follow the rules defined in 3GPP TS 25.331 for the DL messages sent on the DCCH. + +## 8.9 Message with error label: 'Message escape' + +If the MS receives an RRC message containing the error label: 'Message escape' where the number of bits of the extension is not defined in clause 9, the MS shall: + +- 1) ignore the message. + +If the MS receives an RRC message containing the error label: 'Message escape' where the number of bits of the extension is defined in clause 9, the MS shall: + +- 1) ignore the extension by skipping the number of bits indicated in clause 9; +- 1) treat the rest of the message as if the extension was not present. + +## 8.10 Handling of errors in nested information elements + +This sub-clause specifies the handling of errors in mandatory IEs as well as for conditional IEs for which the specified conditions for presence are met, that are nested in another IE. + +In case the MS receives an IE (Information Element 1) that includes a mandatory IE (Information Field 1-1) having a value, including reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the MS shall: + +- 1) consider Information Element 1 to have an undefined value; and +- 1) apply the corresponding generic error handling to Information Element 1. + +In case there are many IE nesting levels, in all of which the IE is mandatory while no default value is defined, this treatment may need to be repeated several times. The following example illustrates the general principle. + +**Table 8.11.1: EXAMPLE MESSAGE information elements** + +``` +< EXAMPLE MESSAGE message content > ::= +{ + { 0 | 1 < Information Element 1 : < Information Element 1 IE > > } + < Information Element 2 : < Information Element 2 IE > > + ! < content part error : bit (*) = < no string > > }; +} +``` + +**Table 8.11.2: Information Element 1 information element** + +``` +< Information Element 1 IE > ::= +{ + { 0 | 1 < Information Field 1-1 : bit (4) > } + < Information Element 1-2 : < Information Element 1-2 IE > > + < Information Element 1-3 : < Information Element 1-3 IE > > +}; +``` + +**Table 8.11.3: Information Element 1 information element details****Information Field 1-1 (4 bit field)** + +``` +4 3 2 1 +0 0 0 0 1 +0 0 0 1 2 +: : : : +1 1 0 0 1 3 +1 1 0 1 reserved for future extension +1 1 1 0 reserved for future extension +1 1 1 1 reserved for future extension +``` + +**Information Element 1-2** + +Definition of Information Element 1-2. + +**Information Element 1-3** + +Definition of Information Element 1-3. + +If in the above example, GERAN would include Information Element 1 and set Information Field 1-1 to value 13, the MS experiences an error in a mandatory IE. The guideline outlined in the previous then means that the MS shall not discard the entire message but instead consider "Information Element 1" to have an unknown value. Since Information Element 1 is optional, the generic error handling would be to ignore "Information Element 1". + +In case the MS receives an IE (Information Element 1) that includes a list of another IE (Information Field 1-1) for which one or more entries in the list have a value, including reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the MS shall: + +1) consider the list as if these entries were not included. + +The rules of handling the errors for nested IE coded in ASN.1 are defined in 3GPP TS 25.331 + +## 8.11 Unknown or unforeseen information element value, optional information element coded in ASN.1 + +If the MS receives an RRC message coded in ASN.1 on the SRB2, or sent via a radio access technology other than GERAN, with an optional IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), it shall: + +1) ignore the value of the IE; + +1) treat the rest of the message as if the IE was not present. + +## 9 Message functional definitions and contents + +### 9.1 General + +#### 9.1.1 Introduction + +Padding is not needed for RRC messages since RRC is not a transmission protocol. + +For harmonization sake, it is assumed that GERAN RRC has to provide the same extension capability as UTRAN RRC. The management of extension for future releases is done at the message level or at Information Element (IE) level when the IE uses the { < Length of content > < Content > } format. The error handling is not defined at the IE level. + +An IE can be structured or simple. A structured IE consists of other IEs and/or fields. A simple IE consists of one field. A field defines itself. + +It was also agreed as working assumption that IEs in 3GPP TS 44.018 to be used in both modes (e.g. physical channel parameters) will not be copied from 3GPP TS 44.018 into 3GPP TS 44.118. Instead, in 3GPP TS 44.118, two fields will be defined: the length in octets, as bit(8), and a content placeholder with such length and whose definition points to the value part of the IE in 3GPP TS 44.018 should be included in the 3GPP TS 44.118. When the IE in 3GPP TS 44.018 is coded in CSN.1 (e.g. RR PACKET UPLINK ASSIGNMENT) and it already includes the length, a content placeholder with such length and whose definition points to the value part of the IE in 3GPP TS 44.018 should be included in 3GPP TS 44.118. + +Bit fields within RRC messages shall have the highest numbered bit of the bit field in the highest numbered bit of the lowest number octet. The mapping of an 11 bit field is illustrated in figure 9.1.1.1. + +![Figure 9.1.1.1: Field mapping within RRC messages. Diagram showing bit mapping across four octets N to N+3.](5e75237ea72c3a124febac3534aed999_img.jpg) + +| | | | | | | | | | | +|--|-------|-------|-------|-------|--------|--------|-------|-------|-----------| +| | | | | bit | | | | | | +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | | | | | | | | | Octet N | +| | | | | | bit 11 | bit 10 | bit 9 | bit 8 | Octet N+1 | +| | bit 7 | bit 6 | bit 5 | bit 4 | bit 3 | bit 2 | bit 1 | | Octet N+2 | +| | | | | | | | | | Octet N+3 | + +Figure 9.1.1.1: Field mapping within RRC messages. Diagram showing bit mapping across four octets N to N+3. + +**Figure 9.1.1.1: Field mapping within RRC messages** + +The encoding rules of the RRC messages (CELL UPDATE, GRA UPDATE and GRA UPDATE CONFIRM) coded in ASN1 are following the ones defined in 3GPP TS 25.331. + +#### 9.1.2 Repetitions of Structure, IE or field: + +The following coding shall be used for unbounded repetition: + +``` +{ { 1 < label : < IE > > } ** 0 } or, +{ { 1 < field : bit (integer) > } ** 0 } or, +{ { 1 < repeated struct > } ** 0 } +``` + +The following coding shall be used for bounded extension for optional structures, IE's or fields: + +``` +{ 0 | 1 < number of repetition : bit (integer) > + < label : < IE > > * (n+val(number of repetition)) } + +or + +{ 0 | 1 < number of repetition : bit (integer) > + < field : bit (integer) > * (n+val(number of repetition)) } + +or + +{ 0 | 1 < number of repetition : bit (integer) > + < repeated struct > * (n+val(number of repetition)) } +``` + +where $n \geq 1$ . + +The following coding shall be used for bounded extension for mandatory structures, IE's or fields: + +``` + +{ < number of repetition : bit (integer) > + < label : < IE > > * (n+val(number of repetition)) } + +or + +{ < number of repetition : bit (integer) > + < field : bit (integer) > * (n+val(number of repetition)) } + +or + +{ < number of repetition : bit (integer) > + < repeated struct > * (n+val(number of repetition)) } + +``` + +where $n \geq 1$ . + +## 9.1.3 Message format and error labels + +### 9.1.3.1 General + +The general format of messages, including these error labels, is: + +``` + +< General message format > ::= + < MESSAGE_TYPE : < bit (8) > > + { < contents > + ! < Content part error : bit (*) = < no string > > } + ! < Unknown message type : bit (8) = < no string > ; + +``` + +Message type shall be coded using 8 bits with separate message type for uplink and downlink, as follow: + +``` + +< Uplink RRC messages > ::= + < MESSAGE_TYPE : 00000000 > < MESSAGE NAME1 message content > | + < MESSAGE_TYPE : 00000001 > < MESSAGE NAME2 message content > ; + +``` + +The message content should be presented has follow: + +## 9.2.x MESSAGE NAME + +Explanation of the message use. + +Radio Bearer: SRBx + +Direction: GERAN→MS and/or MS →GERAN + +**Table 9.2.x.1: MESSAGE NAME information elements** + +``` + +< MESSAGE NAME message content > ::= + { + < IE1 : < IE1 > > + < IE2 : < IE2 > > + ! < Content part error : bit (*) = < no string > > } ; + +``` + +**Table 9.2.x.2: MESSAGE NAME information element details** + +| | +|-------------------------------------| +| IE1
Definition of the IE1 | +|-------------------------------------| + +| | +|-------------------------------------| +| IE2
Definition of the IE2 | +|-------------------------------------| + +The encoding rules of the RRC messages (CELL UPDATE, GRA UPDATE and GRA UPDATE CONFIRM) and the IEs coded in ASN.1 are following the ones defined in 3GPP TS 25.331. + +### 9.1.3.2 Message extension for new protocol version in RRC + +Non-Critical message extension and critical message extension mechanism from UTRAN RRC (3GPP TS 25.331) are duplicated in GERAN RRC. + +The extension mechanism for the RRC messages (CELL UPDATE, GRA UPDATE and GRA UPDATE CONFIRM) and the IEs coded in ASN.1 is following the one defined in 3GPP TS 25.331. + +#### 9.1.3.2.1 Non-Critical extension + +Non-critical extensions will be achieved by adding in the optional references at the end of the message definition. The new elements introduced to specify the extensions should be grouped together in a structure with a name showing the version of the release. + +**Table 9.1.3.2.1.1: Coding non-critical extension in CSN.1** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
{ null   0 bit ** = < no string > -- Receiver compatible with earlier release   1 -- Additions in Release xx < MessageLabel extension for R-XX: < Extension for R-XX struct > > }
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.1.3.2.1.2: Example message coding using non-critical extension in CSN.1** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< MESSAGE NAME message content > ::= {   < IE1 : < IE1 > >   < IE2 : < IE2 > >   { null   0 bit ** = < no string >     1   < R6 IE1 : < R6 IE1 > >   < R6 IE2 : < R6 IE2 > >   { null   0 bit ** = < no string >     1   < R7 IE1 : < R7 IE1 > >   < R7 IE2 : < R7 IE2 > > }   ! < Content part error : bit (*) = < no string > > }
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 9.1.3.2.2 Critical extension + +At the beginning of the message, which may require critical extensions, one bit is added for defining a choice of two branches. All Downlink messages shall enable critical extension with an escape bit at the beginning. One branch would include the message structure, the other branch would be an empty sequence with the comment 'Message escape critical extensions'. + +**Table 9.1.3.2.2.1: Coding of critical extension in CSN.1** + +| | +|------------------------------------------------------------------------------------------------------------------------------------| +| 
0 -- critical extension escape available < Content > ! < Message escape : 1 bit (*) = < no string > >
| +|------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.1.3.2.2.2: An example message coding containing critical extension bit in CSN.1** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< MESSAGE NAME message content > ::= { 0 -- critical extension escape available {   < IE1 : < IE1 > >   < IE2 : < IE2 > > ! < content part error : bit (*) = < no string > > } ! < Message escape critical extension: 1 bit (*) = < no string > > }
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +When a new release is introduced, the empty sequence with 'Message escape critical extensions' will be replaced by a new structure that includes a new type containing the message extensions, and the same extension mechanism recursively for further extensions. + +**Table 9.1.3.2.2.3: An example message coding using critical extension bit in CSN.1** + +``` +< MESSAGE NAME message content > ::= + { 0 -- critical extension escape available + { + < IE1 : < IE1 > > + < IE2 : < IE2 > > + ! < Content part error : bit (*) = < no string > > } + | 1 -- critical extension for R-7 + { 0 + { + < IE3 : < IE3 > > + < IE4 : < IE4 > > + ! < Content part error : bit (*) = < no string > > } + ! < Message escape critical extension: 1 bit (*) = < no string > > } + }; +}; +``` + +The critical extension escape should be used as scarcely as possible in order to preserve backward compatibility. + +### 9.1.3.2.3 Extension of IE's + +If an IE is expected to be extended, the addition of a fixed length extension length at the start of the IE, and \*\* at the end will allow for future extension of the information element. + +**Table 9.1.3.2.3.1: Coding of IE extension in CSN.1** + +``` +< IE NAME message content > ::= + < IE Name Length : bit (n) > + < IE1 : < IE1 > > + < IE2 : < IE2 > > + < spare bit >** ; +``` + +**Table 9.1.3.2.3.2: Example description of IE extension fields** + +**IE Name Length (n bit field)** +This field is the binary representation of the length in bits of the IE (excluding the length field) struct. Range 0-2... + +### 9.1.3.2.4 'Message escape' error label + +The 'Message escape' error label is used to provide an escape for, e.g. a future modification of the message syntax. The generic description is: + +``` +0 < Content > +! < Message escape : 1 bit (N) = < no string > > +``` + +An 'Message escape' error label shall be applied by the receiver of a downlink RRC message when specified in the message description. The description on the left of the error branch needs to be correctly recognised. Otherwise, the error branch 'Message escape' is called. N should be an integer to enable the receiver to skip the exact number of information bits in the message in case of error. N may also be '\*' when the number of bits are not defined. + +## 9.2 Messages for Radio Resources management + +### 9.2.1 General + +Each definition given in the sub-clause 9.2 includes: + +- a brief description of the message direction and use; + +- a CSN.1 description of the message, information elements and fields (see CSN.1 Specification, Version 2.0). Definition of information elements may immediately follow the definition of the message. If the definition of an information element immediately follows the message definition, the information element name ends with 'struct'. Otherwise the information element name ends with 'IE' and the definition of the information element is defined in sub-clause 9.3 or in 3GPP TS 44.160. The definition of a 'struct' is valid only within the table in which it is defined. No references shall be made to a 'struct' definition from outside of the table in which it is defined or from outside the present document. The definition of an information element is valid throughout clause 9. ; +- a table follows which contains a definition for each field referenced in the message definition or in an information element struct immediately following the message definition. Presence requirement for information elements or fields may be indicated in this table to define when the information elements shall be included or not, what non-presence of such information elements or fields means, and, for IEs with conditional presence requirement, the static conditions for presence and/or non-presence of the information elements or fields. However, the normative text for the presence requirement for information elements or fields is specified in the appropriate procedure sub-clause; + +### 9.2.1.1 References + +Table 9.2.1.1.1 summarizes the messages for Radio Resources management. + +NOTE: New messages will be added in this table. + +**Table 9.2.1.1.1: Messages for Radio Resources management** + +| Messages | Reference | +|-------------------------------------------|-------------------| +| RRC connection mobility | | +| CELL UPDATE | Sub-clause 9.2.2 | +| CELL UPDATE CONFIRM | Sub-clause 9.2.3 | +| GERAN MOBILITY INFORMATION | Sub-clause 9.2.8 | +| GERAN MOBILITY INFORMATION CONFIRM | Sub-clause 9.2.9 | +| GERAN MOBILITY INFORMATION FAILURE | Sub-clause 9.2.10 | +| GRA UPDATE | Sub-clause 9.2.11 | +| GRA UPDATE CONFIRM | Sub-clause 9.2.12 | +| Handover | | +| HANDOVER COMPLETE | Sub-clause 9.2.14 | +| HANDOVER FAILURE | Sub-clause 9.2.15 | +| HANDOVER FROM GERAN Iu COMMAND | Sub-clause 9.2.16 | +| INTER SYSTEM TO CDMA2000 HANDOVER COMMAND | Sub-clause 9.2.18 | +| INTER SYSTEM TO UTRAN HANDOVER COMMAND | Sub-clause 9.2.19 | +| LCS information | | +| LCS DOWNLINK INFORMATION | Sub-clause 9.2.20 | +| LCS UPLINK INFORMATION | Sub-clause 9.2.21 | +| MS Capability information | | +| MS CAPABILITY ENQUIRY | Sub-clause 9.2.24 | +| MS CAPABILITY INFORMATION | Sub-clause 9.2.25 | +| MS CAPABILITY INFORMATION CONFIRM | Sub-clause 9.2.26 | +| Measurement | | +| EXTENDED MEASUREMENT ORDER | Sub-clause 9.2.6 | +| EXTENDED MEASUREMENT REPORT | Sub-clause 9.2.7 | +| MEASUREMENT INFORMATION | Sub-clause 9.2.22 | +| MEASUREMENT REPORT | Sub-clause 9.2.23 | +| ENHANCED MEASUREMENT REPORT | Sub-clause 9.2.7a | +| Paging | | +| DEDICATED PAGING REQUEST | Sub-clause 9.2.4 | +| Radio bearer control | | +| RADIO BEARER RECONFIGURATION | Sub-clause 9.2.28 | +| RADIO BEARER RECONFIGURATION COMPLETE | Sub-clause 9.2.29 | +| RADIO BEARER RECONFIGURATION FAILURE | Sub-clause 9.2.30 | +| RADIO BEARER RELEASE | Sub-clause 9.2.31 | +| RADIO BEARER RELEASE COMPLETE | Sub-clause 9.2.32 | +| RADIO BEARER RELEASE FAILURE | Sub-clause 9.2.33 | +| RADIO BEARER SETUP | Sub-clause 9.2.34 | +| RADIO BEARER SETUP COMPLETE | Sub-clause 9.2.35 | +| RADIO BEARER SETUP FAILURE | Sub-clause 9.2.36 | +| GERAN Iu mode DTM REQUEST | Sub-clause 9.2.57 | +| GERAN Iu mode DTM REJECT | Sub-clause 9.2.58 | +| RRC Connection Management | | +| RRC CONNECTION REJECT | Sub-clause 9.2.37 | +| RRC CONNECTION RELEASE | Sub-clause 9.2.38 | +| RRC CONNECTION RELEASE COMPLETE | Sub-clause 9.2.39 | +| RRC CONNECTION REQUEST | Sub-clause 9.2.40 | +| RRC CONNECTION SETUP | Sub-clause 9.2.41 | +| RRC CONNECTION SETUP COMPLETE | Sub-clause 9.2.42 | +| Security mode control | | +| SECURITY MODE COMMAND | Sub-clause 9.2.45 | +| SECURITY MODE COMPLETE | Sub-clause 9.2.46 | +| SECURITY MODE FAILURE | Sub-clause 9.2.47 | +| Signalling flow | | +| SIGNALLING CONNECTION RELEASE | Sub-clause 9.2.48 | +| SIGNALLING CONNECTION RELEASE INDICATION | Sub-clause 9.2.49 | +| System information | | +| SYSTEM INFORMATION 13 | 3GPP TS 44.108 | +| SYSTEM INFORMATION 3 | 3GPP TS 44.108 | +| SYSTEM INFORMATION 5 | Sub-clause 9.2.51 | +| SYSTEM INFORMATION 5bis | Sub-clause 9.2.52 | +| SYSTEM INFORMATION 5ter | Sub-clause 9.2.53 | +| SYSTEM INFORMATION 6 | Sub-clause 9.2.54 | +| Delivery of NAS | | +| DOWNLINK DIRECT TRANSFER | Sub-clause 9.2.5 | + +| | | +|------------------------------------------------------|-------------------| +| INITIAL DIRECT TRANSFER | Sub-clause 9.2.17 | +| UPLINK DIRECT TRANSFER | Sub-clause 9.2.56 | +| Miscellaneous | | +| RRC STATUS | Sub-clause 9.2.43 | +| RRC FAILURE INFO | Sub-clause 9.2.44 | +| INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES | Sub-clause 11.1.5 | +| SBSS RELOCATION INFO | Sub-clause 11.1.5 | + +### 9.2.1.2 Downlink RRC messages + +The different types of messages are distinguished by the MESSAGE\_TYPE field. + +``` +< Downlink RRC messages > ::= +{ + < MESSAGE_TYPE : 00000000 > < CELL UPDATE CONFIRM message content > | + < MESSAGE_TYPE : 00000001 > < DEDICATED PAGING REQUEST message content > | + < MESSAGE_TYPE : 00000010 > < DOWNLINK DIRECT TRANSFER message content > | + < MESSAGE_TYPE : 00000011 > < EXTENDED MEASUREMENT ORDER message content > | + < MESSAGE_TYPE : 00000100 > < GERAN MOBILITY INFORMATION message content > | + < MESSAGE_TYPE : 00000111 > < HANDOVER FROM GERAN Iu COMMAND message content > | + < MESSAGE_TYPE : 00001000 > < INTERSYSTEM HANDOVER TO CDMA2000 message content > | + < MESSAGE_TYPE : 00001001 > < INTERSYSTEM HANDOVER TO UTRAN message content > | + < MESSAGE_TYPE : 00001010 > < LCS DOWNLINK INFORMATION message content > | + < MESSAGE_TYPE : 00001011 > < MEASUREMENT INFORMATION message content > | + < MESSAGE_TYPE : 00001100 > < MS CAPABILITY ENQUIRY message content > | + < MESSAGE_TYPE : 00001101 > < MS CAPABILITY INFORMATION CONFIRM message content > | + < MESSAGE_TYPE : 00001110 > < RADIO BEARER RECONFIGURATION message content > | + < MESSAGE_TYPE : 00010000 > < RADIO BEARER RELEASE message content > | + < MESSAGE_TYPE : 00010111 > < RADIO BEARER SETUP message content > | + < MESSAGE_TYPE : 00010001 > < RRC CONNECTION REJECT message content > | + < MESSAGE_TYPE : 00010010 > < RRC CONNECTION RELEASE message content > | + < MESSAGE_TYPE : 00010011 > < RRC CONNECTION SETUP message content > | + < MESSAGE_TYPE : 00010100 > < RRC STATUS message content > | + < MESSAGE_TYPE : 00010101 > < SECURITY MODE COMMAND message content > | + < MESSAGE_TYPE : 00010110 > < SIGNALLING CONNECTION RELEASE message content > | + < MESSAGE_TYPE : 00010111 > < GERAN Iu mode DTM REJECT message content > | + < MESSAGE_TYPE : 00011000 > < SYSTEM INFORMATION 5 message content > | + < MESSAGE_TYPE : 00011001 > < SYSTEM INFORMATION 5bis message content > | + < MESSAGE_TYPE : 00011010 > < SYSTEM INFORMATION 5ter message content > | + < MESSAGE_TYPE : 00011011 > < SYSTEM INFORMATION 6 message content > + < spare bit >** } +! < Unknown message type : { bit (8) = < no string > } < Default downlink message content > ; +``` + +### 9.2.1.3 Uplink RRC messages + +The different types of messages are distinguished by the MESSAGE\_TYPE field. + +``` +< Uplink RRC messages > ::= +{ + < MESSAGE_TYPE : 00000001 > < EXTENDED MEASUREMENT REPORT message content > | + < MESSAGE_TYPE : 00000010 > < GERAN MOBILITY INFORMATION CONFIRM message content > | + < MESSAGE_TYPE : 00000011 > < GERAN MOBILITY INFORMATION FAILURE message content > | + < MESSAGE_TYPE : 00000110 > < HANDOVER COMPLETE message content > | + < MESSAGE_TYPE : 00000111 > < HANDOVER FAILURE message content > | + < MESSAGE_TYPE : 00001000 > < INITIAL DIRECT TRANSFER message content > | + < MESSAGE_TYPE : 00001001 > < LCS UPLINK INFORMATION message content > | + < MESSAGE_TYPE : 00001010 > < MEASUREMENT REPORT message content > | + < MESSAGE_TYPE : 00001011 > < MS CAPABILITY INFORMATION message content > | + < MESSAGE_TYPE : 00001100 > < RADIO BEARER RECONFIGURATION COMPLETE message content > | + < MESSAGE_TYPE : 00001101 > < RADIO BEARER RECONFIGURATION FAILURE message content > | + < MESSAGE_TYPE : 00001110 > < RADIO BEARER RELEASE COMPLETE message content > | + < MESSAGE_TYPE : 00001111 > < RADIO BEARER RELEASE FAILURE message content > | + < MESSAGE_TYPE : 00010000 > < RADIO BEARER SETUP COMPLETE message content > | + < MESSAGE_TYPE : 00010001 > < RADIO BEARER SETUP FAILURE message content > | + < MESSAGE_TYPE : 00010010 > < RRC CONNECTION RELEASE COMPLETE message content > | + < MESSAGE_TYPE : 00010011 > < RRC CONNECTION REQUEST message content > | + < MESSAGE_TYPE : 00010100 > < RRC CONNECTION SETUP COMPLETE message content > | + < MESSAGE_TYPE : 00010101 > < RRC STATUS message content > | + < MESSAGE_TYPE : 00010110 > < SECURITY MODE COMPLETE message content > | + < MESSAGE_TYPE : 00010111 > < SECURITY MODE FAILURE message content > | + < MESSAGE_TYPE : 00011000 > < SIGNALLING CONNECTION RELEASE INDICATION message content > | + < MESSAGE_TYPE : 00011001 > < UPLINK DIRECT TRANSFER message content > | + < MESSAGE_TYPE : 00011010 > < ENHANCED MEASUREMENT REPORT message content > | + < MESSAGE_TYPE : 00011011 > < GERAN lu mode DTM REQUEST message content > | + < spare bits > ** }; +} +``` + +The 'Default downlink message contents' consists an unspecified bit string that expands to the end of the message. + +``` +< Default downlink message content > ::= +bit (*) = < no string > ; +``` + +#### 9.2.1.3.1 Message definitions + +If the abstract syntax of an IE is defined using the ASN.1 type "BIT STRING" then the encoding rules are defined in 3GPP TS 25.331. + +``` +Class-definitions DEFINITIONS AUTOMATIC TAGS ::= +BEGIN + IMPORTS + CellUpdate, + GRAUpdate, + GRAUpdateConfirm, + Reserved ::= NULL + FROM PDU-definitions + + -- Mobile Station IEs + IntegrityCheckInfo + + FROM InformationElements; + + --***** + -- + -- Uplink SRB2 messages + -- + --***** +``` + +``` +UL-Message ::= SEQUENCE { + integrityCheckInfo IntegrityCheckInfo OPTIONAL, + message UL-MessageType +} + +UL-MessageType ::= CHOICE { + cellUpdate CellUpdate -- 000000000, + reserved1 Reserved, + reserved2 Reserved, + reserved3 Reserved, + graUpdate GRAUpdate -- 00000100, + reserved5 Reserved, + reserved6 Reserved, + reserved7 Reserved, + reserved8 Reserved, + reserved9 Reserved, + reserved10 Reserved, + reserved11 Reserved, + reserved12 Reserved, + reserved13 Reserved, + reserved14 Reserved, + reserved15 Reserved, + reserved16 Reserved, + reserved17 Reserved, + reserved18 Reserved, + reserved19 Reserved, + reserved20 Reserved, + reserved21 Reserved, + reserved22 Reserved, + reserved23 Reserved, + reserved24 Reserved, + reserved25 Reserved, + reserved26 Reserved, + reserved27 Reserved, + reserved28 Reserved, + reserved29 Reserved, + reserved30 Reserved, + reserved31 Reserved, + reserved32 Reserved, + reserved33 Reserved, + reserved34 Reserved, + reserved35 Reserved, + reserved36 Reserved, + reserved37 Reserved, + reserved38 Reserved, + reserved39 Reserved, + reserved40 Reserved, + reserved41 Reserved, + reserved42 Reserved, + reserved43 Reserved, + reserved44 Reserved, + reserved45 Reserved, + reserved46 Reserved, + reserved47 Reserved, + reserved48 Reserved, + reserved49 Reserved, + reserved50 Reserved, + reserved51 Reserved, + reserved52 Reserved, + reserved53 Reserved, + reserved54 Reserved, + reserved55 Reserved, + reserved56 Reserved, + reserved57 Reserved, + reserved58 Reserved, + reserved59 Reserved, + reserved60 Reserved, + reserved61 Reserved, + reserved62 Reserved, + reserved63 Reserved, + reserved64 Reserved, + reserved65 Reserved, + reserved66 Reserved, + reserved67 Reserved, + reserved68 Reserved, + reserved69 Reserved, + reserved70 Reserved, + reserved71 Reserved, +``` + +reserved72 Reserved, +reserved73 Reserved, +reserved74 Reserved, +reserved75 Reserved, +reserved76 Reserved, +reserved77 Reserved, +reserved78 Reserved, +reserved79 Reserved, +reserved80 Reserved, +reserved81 Reserved, +reserved82 Reserved, +reserved83 Reserved, +reserved84 Reserved, +reserved84 Reserved, +reserved85 Reserved, +reserved86 Reserved, +reserved87 Reserved, +reserved88 Reserved, +reserved89 Reserved, +reserved90 Reserved, +reserved91 Reserved, +reserved92 Reserved, +reserved93 Reserved, +reserved94 Reserved, +reserved95 Reserved, +reserved96 Reserved, +reserved97 Reserved, +reserved98 Reserved, +reserved99 Reserved, +reserved100 Reserved, +reserved101 Reserved, +reserved102 Reserved, +reserved103 Reserved, +reserved104 Reserved, +reserved105 Reserved, +reserved106 Reserved, +reserved107 Reserved, +reserved108 Reserved, +reserved109 Reserved, +reserved110 Reserved, +reserved111 Reserved, +reserved112 Reserved, +reserved113 Reserved, +reserved114 Reserved, +reserved115 Reserved, +reserved116 Reserved, +reserved117 Reserved, +reserved118 Reserved, +reserved119 Reserved, +reserved120 Reserved, +reserved121 Reserved, +reserved122 Reserved, +reserved123 Reserved, +reserved124 Reserved, +reserved125 Reserved, +reserved126 Reserved, +reserved127 Reserved, +reserved128 Reserved, +reserved129 Reserved, +reserved130 Reserved, +reserved131 Reserved, +reserved132 Reserved, +reserved133 Reserved, +reserved134 Reserved, +reserved135 Reserved, +reserved136 Reserved, +reserved137 Reserved, +reserved138 Reserved, +reserved139 Reserved, +reserved140 Reserved, +reserved141 Reserved, +reserved142 Reserved, +reserved143 Reserved, +reserved144 Reserved, +reserved145 Reserved, +reserved146 Reserved, +reserved147 Reserved, +reserved148 Reserved, + +reserved149 Reserved, +reserved150 Reserved, +reserved151 Reserved, +reserved152 Reserved, +reserved153 Reserved, +reserved154 Reserved, +reserved155 Reserved, +reserved156 Reserved, +reserved157 Reserved, +reserved158 Reserved, +reserved159 Reserved, +reserved160 Reserved, +reserved161 Reserved, +reserved162 Reserved, +reserved163 Reserved, +reserved164 Reserved, +reserved165 Reserved, +reserved166 Reserved, +reserved167 Reserved, +reserved168 Reserved, +reserved169 Reserved, +reserved170 Reserved, +reserved171 Reserved, +reserved172 Reserved, +reserved173 Reserved, +reserved174 Reserved, +reserved175 Reserved, +reserved176 Reserved, +reserved177 Reserved, +reserved178 Reserved, +reserved179 Reserved, +reserved180 Reserved, +reserved181 Reserved, +reserved182 Reserved, +reserved183 Reserved, +reserved184 Reserved, +reserved185 Reserved, +reserved186 Reserved, +reserved187 Reserved, +reserved188 Reserved, +reserved189 Reserved, +reserved190 Reserved, +reserved191 Reserved, +reserved192 Reserved, +reserved193 Reserved, +reserved194 Reserved, +reserved195 Reserved, +reserved196 Reserved, +reserved197 Reserved, +reserved198 Reserved, +reserved199 Reserved, +reserved200 Reserved, +reserved201 Reserved, +reserved202 Reserved, +reserved203 Reserved, +reserved204 Reserved, +reserved205 Reserved, +reserved206 Reserved, +reserved207 Reserved, +reserved208 Reserved, +reserved209 Reserved, +reserved210 Reserved, +reserved211 Reserved, +reserved212 Reserved, +reserved213 Reserved, +reserved214 Reserved, +reserved215 Reserved, +reserved216 Reserved, +reserved217 Reserved, +reserved218 Reserved, +reserved219 Reserved, +reserved220 Reserved, +reserved221 Reserved, +reserved222 Reserved, +reserved223 Reserved, +reserved224 Reserved, +reserved225 Reserved, +reserved226 Reserved, + +``` + + reserved227 Reserved, + reserved228 Reserved, + reserved229 Reserved, + reserved230 Reserved, + reserved231 Reserved, + reserved232 Reserved, + reserved233 Reserved, + reserved234 Reserved, + reserved235 Reserved, + reserved236 Reserved, + reserved237 Reserved, + reserved238 Reserved, + reserved239 Reserved, + reserved240 Reserved, + reserved241 Reserved, + reserved242 Reserved, + reserved243 Reserved, + reserved244 Reserved, + reserved245 Reserved, + reserved246 Reserved, + reserved247 Reserved, + reserved248 Reserved, + reserved249 Reserved, + reserved250 Reserved, + reserved251 Reserved, + reserved252 Reserved, + reserved253 Reserved, + reserved254 Reserved, + reserved255 Reserved + } + ----- + -- + -- Downlink SRB2 messages + -- + ----- + + DL-Dedicated-Message ::= SEQUENCE { + integrityCheckInfo IntegrityCheckInfo OPTIONAL, + message DL-Dedicated-MessageType + } + + DL-Dedicated-MessageType ::= CHOICE { + reserved0 Reserved, + reserved1 Reserved, + reserved2 Reserved, + reserved3 Reserved, + reserved4 Reserved, + graUpdateConfirm GRAUpdateConfirm -- 00000101, + reserved6 Reserved, + reserved7 Reserved, + reserved8 Reserved, + reserved9 Reserved, + reserved10 Reserved, + reserved11 Reserved, + reserved12 Reserved, + reserved13 Reserved, + reserved14 Reserved, + reserved15 Reserved, + reserved16 Reserved, + reserved17 Reserved, + reserved18 Reserved, + reserved19 Reserved, + reserved20 Reserved, + reserved21 Reserved, + reserved22 Reserved, + reserved23 Reserved, + reserved24 Reserved, + reserved25 Reserved, + reserved26 Reserved, + reserved27 Reserved, + reserved28 Reserved, + reserved29 Reserved, + reserved30 Reserved, + reserved31 Reserved, + reserved32 Reserved, + reserved33 Reserved, + reserved34 Reserved, + reserved35 Reserved, + } + +``` + +reserved36 Reserved, +reserved37 Reserved, +reserved38 Reserved, +reserved39 Reserved, +reserved40 Reserved, +reserved41 Reserved, +reserved42 Reserved, +reserved43 Reserved, +reserved44 Reserved, +reserved45 Reserved, +reserved46 Reserved, +reserved47 Reserved, +reserved48 Reserved, +reserved49 Reserved, +reserved50 Reserved, +reserved51 Reserved, +reserved52 Reserved, +reserved53 Reserved, +reserved54 Reserved, +reserved55 Reserved, +reserved56 Reserved, +reserved57 Reserved, +reserved58 Reserved, +reserved59 Reserved, +reserved60 Reserved, +reserved61 Reserved, +reserved62 Reserved, +reserved63 Reserved, +reserved64 Reserved, +reserved65 Reserved, +reserved66 Reserved, +reserved67 Reserved, +reserved68 Reserved, +reserved69 Reserved, +reserved70 Reserved, +reserved71 Reserved, +reserved72 Reserved, +reserved73 Reserved, +reserved74 Reserved, +reserved75 Reserved, +reserved76 Reserved, +reserved77 Reserved, +reserved78 Reserved, +reserved79 Reserved, +reserved80 Reserved, +reserved81 Reserved, +reserved82 Reserved, +reserved83 Reserved, +reserved84 Reserved, +reserved84 Reserved, +reserved85 Reserved, +reserved86 Reserved, +reserved87 Reserved, +reserved88 Reserved, +reserved89 Reserved, +reserved90 Reserved, +reserved91 Reserved, +reserved92 Reserved, +reserved93 Reserved, +reserved94 Reserved, +reserved95 Reserved, +reserved96 Reserved, +reserved97 Reserved, +reserved98 Reserved, +reserved99 Reserved, +reserved100 Reserved, +reserved101 Reserved, +reserved102 Reserved, +reserved103 Reserved, +reserved104 Reserved, +reserved105 Reserved, +reserved106 Reserved, +reserved107 Reserved, +reserved108 Reserved, +reserved109 Reserved, +reserved110 Reserved, +reserved111 Reserved, +reserved112 Reserved, + +reserved113 Reserved, +reserved114 Reserved, +reserved115 Reserved, +reserved116 Reserved, +reserved117 Reserved, +reserved118 Reserved, +reserved119 Reserved, +reserved120 Reserved, +reserved121 Reserved, +reserved122 Reserved, +reserved123 Reserved, +reserved124 Reserved, +reserved125 Reserved, +reserved126 Reserved, +reserved127 Reserved, +reserved128 Reserved, +reserved129 Reserved, +reserved130 Reserved, +reserved131 Reserved, +reserved132 Reserved, +reserved133 Reserved, +reserved134 Reserved, +reserved135 Reserved, +reserved136 Reserved, +reserved137 Reserved, +reserved138 Reserved, +reserved139 Reserved, +reserved140 Reserved, +reserved141 Reserved, +reserved142 Reserved, +reserved143 Reserved, +reserved144 Reserved, +reserved145 Reserved, +reserved146 Reserved, +reserved147 Reserved, +reserved148 Reserved, +reserved149 Reserved, +reserved150 Reserved, +reserved151 Reserved, +reserved152 Reserved, +reserved153 Reserved, +reserved154 Reserved, +reserved155 Reserved, +reserved156 Reserved, +reserved157 Reserved, +reserved158 Reserved, +reserved159 Reserved, +reserved160 Reserved, +reserved161 Reserved, +reserved162 Reserved, +reserved163 Reserved, +reserved164 Reserved, +reserved165 Reserved, +reserved166 Reserved, +reserved167 Reserved, +reserved168 Reserved, +reserved169 Reserved, +reserved170 Reserved, +reserved171 Reserved, +reserved172 Reserved, +reserved173 Reserved, +reserved174 Reserved, +reserved175 Reserved, +reserved176 Reserved, +reserved177 Reserved, +reserved178 Reserved, +reserved179 Reserved, +reserved180 Reserved, +reserved181 Reserved, +reserved182 Reserved, +reserved183 Reserved, +reserved184 Reserved, +reserved185 Reserved, +reserved186 Reserved, +reserved187 Reserved, +reserved188 Reserved, +reserved189 Reserved, +reserved190 Reserved, + +``` + +reserved191 Reserved, +reserved192 Reserved, +reserved193 Reserved, +reserved194 Reserved, +reserved195 Reserved, +reserved196 Reserved, +reserved197 Reserved, +reserved198 Reserved, +reserved199 Reserved, +reserved200 Reserved, +reserved201 Reserved, +reserved202 Reserved, +reserved203 Reserved, +reserved204 Reserved, +reserved205 Reserved, +reserved206 Reserved, +reserved207 Reserved, +reserved208 Reserved, +reserved209 Reserved, +reserved210 Reserved, +reserved211 Reserved, +reserved212 Reserved, +reserved213 Reserved, +reserved214 Reserved, +reserved215 Reserved, +reserved216 Reserved, +reserved217 Reserved, +reserved218 Reserved, +reserved219 Reserved, +reserved220 Reserved, +reserved221 Reserved, +reserved222 Reserved, +reserved223 Reserved, +reserved224 Reserved, +reserved225 Reserved, +reserved226 Reserved, +reserved227 Reserved, +reserved228 Reserved, +reserved229 Reserved, +reserved230 Reserved, +reserved231 Reserved, +reserved232 Reserved, +reserved233 Reserved, +reserved234 Reserved, +reserved235 Reserved, +reserved236 Reserved, +reserved237 Reserved, +reserved238 Reserved, +reserved239 Reserved, +reserved240 Reserved, +reserved241 Reserved, +reserved242 Reserved, +reserved243 Reserved, +reserved244 Reserved, +reserved245 Reserved, +reserved246 Reserved, +reserved247 Reserved, +reserved248 Reserved, +reserved249 Reserved, +reserved250 Reserved, +reserved251 Reserved, +reserved252 Reserved, +reserved253 Reserved, +reserved254 Reserved, +reserved255 Reserved +} END +``` + +9.2.1.3.1.1 PDU definitions + +``` + +--************************************************************* +-- +-- NOTE: The message type and integrity check info are not +-- visible in this module as they are defined in the class module. +-- +--************************************************************* + +PDU-definitions DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN +``` + +``` + +--****************************************************************************** +-- +-- IE parameter types from other modules +-- +--****************************************************************************** + +IMPORTS + + ActivationTime, + CN-DomainIdentity, + CN-InformationInfo, + CellUpdateCause, + CipheringModeInfo, + FailureCauseWithProtErrTrId, + G-RNTI, + GRA-Identity, + GERAN-DRX-CycleLengthCoefficient, + GRA-UpdateCause, + DL-CounterSynchronisationInfo, + IntegrityProtectionModeInfo, + NAS-SystemInformationGSM-MAP, + ProtocolErrorIndicator, + PLMN-Identity, + PDCP-SN-Info, + RRC-StateIndicator, + RRC-TransactionIdentifier, + Rb-timer-indicator, + RB-WithPDCP-InfoList, + RB-PDCPContextRelocationList, + RB-Identity, + RB-PDCPContextRelocation, + START-Value, + STARTList +FROM InformationElements; + +``` + +## 9.2.2 CELL UPDATE + +This message is used by the MS to initiate a cell update procedure. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +``` + +-- ***************************************************************************** +-- +-- CELL UPDATE +-- +-- ***************************************************************************** + +CellUpdate ::= SEQUENCE { + -- User equipment IEs + g-RNTI G-RNTI, + startList STARTList, + am-RLC-ErrorIndicationRb2-3or4 BOOLEAN, + am-RLC-ErrorIndicationRb5orAbove BOOLEAN, + cellUpdateCause CellUpdateCause, + -- NOTE: RRC transaction identifier is nested in FailureCauseWithProtErrTrId, + failureCause FailureCauseWithProtErrTrId OPTIONAL, + rb-timer-indicator Rb-timer-indicator, + laterNonCriticalExtensions SEQUENCE { + -- Container for additional R5 extensions + cellUpdate-r5-add-ext BIT STRING OPTIONAL, + nonCriticalExtensions SEQUENCE {} OPTIONAL + } OPTIONAL +} + +-- ***************************************************************************** + +``` + +## 9.2.3 CELL UPDATE CONFIRM + +This message confirms the cell update procedure and can be used to reallocate new G-RNTI information for the MS valid in the new cell. + +Radio Bearer : SRB2 + +Direction : GERAN→MS + +**Table 9.2.3.1: CELL UPDATE CONFIRM information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < CELL UPDATE CONFIRM message content > ::=   { 0 -- Critical extension escape available     {       -- MS Information Elements       < RRC Transaction Identifier : < RRC Transaction Identifier IE > >       < Activation Time : < Activation Time IE > >       < RRC State Indicator : < RRC State Indicator IE > >       < GERAN DRX Cycle Length Coefficient : < GERAN DRX Cycle Length Coefficient IE > >       { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }       { 0   1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > }       { 0   1 < Ciphering Mode Info : < Ciphering Mode Info IE > > }       { 0   1 < New G-RNTI : < G-RNTI IE > > }       < RLC re-establishment indicator SRB2-4 : bit(1) >       < RLC re-establishment indicator RB5+ : bit(1) >       -- CN Information Elements       { 0   1 < CN Information Info : < CN Information Info IE > > }       -- GERAN Information Elements       { 0   1 < GRA Identity : < GRA Identity IE > > }       -- RB Information Elements       { 0   1 < RB Information to Release list : bit (5) >         { < RB Information to Release : < RB Information to Release IE > >           { 0   1 < DBPSCH Description : < DBPSCH Description IE > > }           0   1 < NETWORK_RESPONSE_TIMES : < Network Response Times struct > > }         }*(1 + val(RB Information to Release list) ) }       { 0   1 < RB Information to Reconfigure list : bit (5) >         { < RB Information to Reconfigure : < RB Information to Reconfigure IE > >           { 0   1 < DBPSCH Description : < DBPSCH Description IE > > }           0   1 < NETWORK_RESPONSE_TIMES : < Network Response Times struct > > }         }*(1 + val(RB Information to Reconfigure list) ) }       { 0   1 < RB Information to Be Affected list : bit (5) >         { < RB Information to Be Affected : < RB Information to Be Affected IE > >           { 0   1 < DBPSCH Description : < DBPSCH Description IE > > }           0   1 < NETWORK_RESPONSE_TIMES : < Network Response Times struct > > }         }*(1 + val(RB Information to Be Affected list) ) }       { 0   1 < Downlink Counter Synchronisation Info : < Downlink Counter Synchronisation info struct > > }       ! < Content part error : bit (*) = < no string > > }     ! < Message escape critical extensions : 1 bit (*) = < no string > > } ;
| +| 
 < Downlink Counter Synchronisation Info struct > ::=   < RB with PDCP Information List : bit (5) >   { { 0   1 < RB with PDCP Information : < RB with PDCP Information IE > > }     { 0   1 < PDCP context relocation info : < PDCP context relocation info IE > > } } * (1 + val(RB with PDCP   Information List) );
| +| 
 < Network Response Times struct > ::=   { 0 -- Network's response times on SDCCH     < RESPONSE_TIME_SDCCH : < Response Time SDCCH struct > >     1 -- Network's reponse times on the assigned DBPSCH     < RESPONSE_TIME_SACCH : < Response Time SACCH struct > > -- Network's response time on SACCH     { 00 -- Network's response time on FACCH/F       -- i.e. between a request sent on TCH/F or FACCH/F and the corresponding response sent on FACCH/F       < RESPONSE_TIME_FACCH_F : < Response Time struct > >       01 < RESPONSE_TIME_FACCH_H : < Response Time struct > > -- Network's reponse time on FACCH/H       10 < RESPONSE_TIME_FLO : < Response Time FLO struct > > } -- Network's response times with FLO   } ;
| +| 
 < Response Time SDCCH struct > ::=   < TRMIN_SDCCH : bit (1) > -- Network's minimum response time on SDCCH   < TRESP_SDCCH : bit (1) >;-- Network's maximum response time on SDCCH
| +| 
 < Response Time SACCH struct > ::=   < TRMIN_SACCH : bit (1) > -- Network's minimum response time on SACCH   < TRESP_SACCH : bit (1) >;-- Network's maximum response time on SACCH
| +| 
 < Response Time struct > ::=   < TRMIN : bit (6) >   < TRESP_MAC_DTM : bit (7) >   < TRESP_MAC_Dedicated : bit (7) > ;
| + +``` +< Response Time FLO struct > ::= -- Response times when FLO is used + < TRMIN_DCH : bit (6) > + < TRES_DCH_MAC_DTM : bit (7) > + < TRESP_DCH_MAC_Dedicated : bit (7) > ; +``` + +**Table 9.2.3.2: CELL UPDATE CONFIRM information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98.

| +|

Activation Time
This IE is defined in sub-clause 9.3.1.

| +|

RRC State Indicator
This IE is defined in sub-clause 9.3.97.

| +|

GERAN DRX cycle length coefficient
This IE is defined in sub-clause 9.3.29.

| +|

Integrity Check Info
This IE is defined in sub-clause 9.3.36. The integrity Check Info IE is included when integrity protection is applied

| +|

Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39. The GERAN does not include this IE unless it is performing an SBSS relocation

| +|

Ciphering Mode Info
This IE is defined in sub-clause 9.3.14. The GERAN does not include this IE unless it is performing an SBSS relocation and a change in ciphering algorithm.

| +|

New G-RNTI
This IE assigns a new G-RNTI to the MS. This IE is coded as the G-RNTI IE defined in sub-clause 9.3.32.

| +|

CN Information Info
This IE is defined in sub-clause 9.3.17.

| +|

RLC Re-establishment indicator SRB2-4 (1 bit field)
This field indicates to the MS to re-establish the RLC instances for SRB2-4 (see 3GPP TS 44.160).

bit
1
0 Do not re-establish the RLC instances for SRB2-4
1 Re-establish the RLC instances for SRB2-4

It shall not be set to 1 if struct "Downlink counter synchronisation info" is included.

| +|

RLC Re-establishment indicator RB5+ (1 bit field)
This field indicates to the MS to re-establish the RLC instances for RB5+ (see 3GPP TS 44.160).

bit
1
0 Do not re-establish the RLC instances for RB5+
1 Re-establish the RLC instances for RB5+

It shall not be set to 1 if struct "Downlink counter synchronisation info" is included.

| +|

GRA Identity
This field is defined in sub-clause 9.3.30.

| +|

DBPSCH Description
This IE is defined in sub-clause 9.3.19.

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

RB Information to Release list (5 bit field)

This field is used to repeat information on each RB to be released, where 0 enables one RB to be described. Range : 0 to maxRB-1.

| +|

RB Information to Release

This IE is defined in sub-clause 9.3.83.

| +|

RB Information to Reconfigure list (5 bit field)

This field is used to repeat information on each RB to be reconfigured, where 0 enables one RB to be described. Range: 0 to maxRB-1.

| +|

RB Information to Reconfigure

This IE is defined in sub-clause 9.3.82.

| +|

RB Information to Be Affected list (5 bit field)

This field is used to repeat information on each RB to be affected, where 0 enables one RB to be described. Range: 0 to maxRB-1.

| +|

RB Information to Be Affected

This IE is defined in sub-clause 9.3.81.

| +|

RB with PDCP Information list (5 bit field)

This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described. . Range: 0 to maxRBallRABs-1.

| +|

RB with PDCP Information

This IE is defined in sub-clause 9.3.86.

| +|

PDCP context relocation info

This IE is defined in sub-clause 9.3.116.

| +|

Downlink Counter Synchronisation Info struct

This structure contains information about PDCP synchronisation.

| +|

Network Response Times struct

This structure contains information about network response times.

| +|

TRMIN_SDCCH (1 bit field)

This field indicates the minimum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060.

| +|

TRESP_SDCCH (1 bit field)

This field indicates the maximum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060.

| +|

TRMIN_SACCH (1 bit field)

This field indicates the minimum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060.

| +|

TRESP_SACCH (1 bit field)

This field indicates the maximum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060.

| +|

TRMIN (6 bit field)

This field indicates the minimum response time of the network, expressed as a number of TDMA frames. See 3GPP TS 44.060.

| +|

TRESP_MAC_DTM (7 bit field)

TRESP_MAC_Dedicated (7 bit field)

These fields indicate for a given MAC state the maximum response time of the network expressed as a number of TDMA frames. See 3GPP TS 44.060.

| + +**TRMIN\_DCH** (6 bit field) + +This field indicates the minimum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. + +**TRES\_DCH\_MAC\_DTM** (7 bit field)**TRES\_DCH\_MAC\_Dedicated** (7 bit field) + +These fields indicate for a given MAC state the maximum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. + +## 9.2.4 DEDICATED PAGING REQUEST + +In *RRCell\_Dedicated state*, GERAN sends this message to signal a core-network-originated page. + +Radio Bearer : SRB2 + +Direction : GERAN → MS + +**Table 9.2.4.1: DEDICATED PAGING REQUEST information elements** + +``` +< DEDICATED PAGING REQUEST message content > ::= +{ 0 -- critical extension escape available +{ + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + < Paging Cause : < Paging Cause IE > > + < CN Domain Identity : < CN Domain Identity IE > > + < Paging Record Type Identifier : < Paging Record Type Identifier IE > > + ! < Content part error : bit (*) = < no string > > } + ! < Message escape critical extension : 1 bit (*) = < no string > > } ; +``` + +**Table 9.2.4.2: DEDICATED PAGING REQUEST information element details** + +**RRC Transaction Identifier** + +This IE is defined in sub-clause 9.3.98. + +**Integrity Check Info** + +This IE is defined in sub-clause 9.3.36. + +**Paging Cause** + +This IE is defined in sub-clause 9.3.57. + +**CN Domain Identity** + +This IE is defined in sub-clause 9.3.15. + +**Paging Record Type Identifier** + +This IE is defined in sub-clause 9.3.58. + +## 9.2.5 DOWNLINK DIRECT TRANSFER + +This message is sent by GERAN to transfer higher layer messages. + +Radio Bearer : SRB3 and SRB4 + +Direction : GERAN → MS + +**Table 9.2.5.1: DOWNLINK DIRECT TRANSFER information elements** + +``` + +< DOWNLINK DIRECT TRANSFER message content > ::= +{ 0 -- critical extension escape available +{ +-- MS Information Elements +< RRC Transaction Identifier : < RRC Transaction Identifier IE > > +{ 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } +-- CN Information Elements +< CN Domain Identity : < CN Domain Identity IE > > +< NAS Message : < NAS Message IE > > +! < Content part error : bit (*) = < no string > > } +! < Message escape critical extensions : 1 bit (*) = < no string > > } ; + +``` + +**Table 9.2.5.2: DOWNLINK DIRECT TRANSFER information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
The RRC Transaction Identifier IE is defined in sub-clause 9.3.98. | +| Integrity Check Info
The Integrity Check Info IE is defined in sub-clause 9.3.36.
The Integrity Check Info IE is included if integrity protection is applied. | +| CN Domain Identity
The CN Domain Identity IE is defined in sub-clause 9.3.15. | +| NAS Message
The NAS Message IE is defined in sub-clause 9.3.54. | + +## 9.2.6 EXTENDED MEASUREMENT ORDER + +This message is the same as the EXTENDED MEASUREMENT ORDER message defined in 3GPP TS 44.018 but shall not contain: + +- RR management Protocol Discriminator IE. +- Skip Indicator IE. +- L2 pseudo length IE. +- Extended Measurement Order IE. + +Radio Bearer : SRB1 + +Direction : GERAN → MS + +## 9.2.7 EXTENDED MEASUREMENT REPORT + +This message is the same as the EXTENDED MEASUREMENT REPORT message defined in 3GPP TS 44.018 but shall not contain: + +- RR management Protocol Discriminator IE. +- Skip Indicator IE. +- Extended Measurement Report Message Type IE. + +Radio Bearer : SRB1 + +Direction : MS → GERAN + +## 9.2.7a ENHANCED MEASUREMENT REPORT + +This message is the same as the ENHANCED MEASUREMENT REPORT message defined in 3GPP TS 44.018 but shall not contain: + +- RR short PD field. +- Message type field. +- Short layer 2 header field. + +Radio Bearer : SRB1 + +Direction : MS → GERAN + +## 9.2.8 GERAN MOBILITY INFORMATION + +This message is used by GERAN to allocate a new G-RNTI and to convey other GERAN mobility related information to a MS. + +Radio Bearer : SRB2 + +Direction : GERAN → MS + +**Table 9.2.8.1: GERAN MOBILITY INFORMATION information elements** + +``` +< GERAN MOBILITY INFORMATION message content > ::= +{ 0 -- Critical extension escape available +{ +-- MS Information Elements + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < MS Timers and Constants in Connected Mode : < MS Timers and Constants in Connected Mode IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + { 0 | 1 < Integrity protection mode info : < Integrity Protection Mode Info IE > > } + { 0 | 1 < Ciphering Mode Info : < Ciphering Mode Info IE > > } + { 0 | 1 < New G-RNTI : < G-RNTI IE > > } +-- CN Information Elements + { 0 | 1 < CN Information Info : < CN Information Info Full IE > > } +-- GERAN Information Elements + { 0 | 1 < GRA Identity : < GRA Identity IE > > } + { 0 | 1 < Downlink Counter Synchronisation Info : < Downlink Counter Synchronisation Info struct > > } + ! < Content part error : bit (*) = < no string > > } + ! < Message escape critical extensions : 1 bit (*) = < no string > > } ; +< Downlink Counter Synchronisation Info struct > ::= + < RB with PDCP Information List : bit (5) > + { { 0 | 1 < RB with PDCP Information : < RB with PDCP Information IE > > } + { 0 | 1 < PDCP context relocation info : < PDCP context relocation info IE > > } } * (1 + val(RB with PDCP +Information List) ); +``` + +**Table 9.2.8.2: GERAN MOBILITY INFORMATION information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98.

| +|

MS Timers and Constants in connected mode
This IE is defined in sub-clause 9.3.51.

| +|

Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included when integrity protection is applied

| +|

Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39. The GERAN does not include this IE unless it is performing an SBSS relocation

| + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ciphering mode info
This IE is defined in sub-clause 9.3.14. The GERAN does not include this IE unless it is performing an SBSS relocation and a change in ciphering algorithm | +| New G-RNTI
This IE assigns a new G-RNTI to the MS. The G-RNTI IE is defined in sub-clause 9.3.32. | +| CN Information Info Full
This IE is defined in sub-clause 9.3.18. | +| GRA Identity
This IE is defined in sub-clause 9.3.30. | +| Downlink Counter Synchronisation info
This structure contains information about PDCP synchronisation. | +| RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described.. Range: 0 to maxRBallRABs-1. Other values are reserved. | +| RB with PDCP Information
This IE is defined in sub-clause 9.3.86. | +| PDCP context relocation info
This IE is defined in sub-clause 9.3.116 | + +## 9.2.9 GERAN MOBILITY INFORMATION CONFIRM + +This message is used to confirm the new GERAN mobility information for the MS. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.9.1: GERAN MOBILITY INFORMATION CONFIRM information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < GERAN MOBILITY INFORMATION CONFIRM message content > ::= {   -- MS Information Elements   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   { 0   1 < Uplink Integrity Protection Activation Info : < Integrity Protection Activation Info IE > > }   -- RB Information Elements   { 0   1 < COUNT-C Activation Time : < Activation Time IE > > }   { 0   1 < Radio Bearer Uplink Ciphering Activation Time Info : < RB Activation Time Info IE > > }   { 0   1 < Uplink Counter Synchronisation Info : < Uplink Counter Synchronisation Info struct > > }   ! < Content part error : bit (*) = < no string > > };  < Uplink Counter Synchronisation Info struct > ::= {   < START List: bit (2) >   {     < START : < START IE > >     < CN Domain Identity : < CN Domain Identity IE > > } *(1+val(START list))   }   { 0   1 < RB with PDCP Information list : bit (5) >     < RB with PDCP Information : < RB with PDCP Information IE > > *(1 + val(RB with PDCP Information list) )} }
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.9.2: GERAN MOBILITY INFORMATION CONFIRM information element details** + +| | +|-------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +|-------------------------------------------------------------------------------| + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included when integrity protection is applied. | +| Uplink Integrity Protection Activation Info
The Integrity Protection Activation Info IE is defined in sub-clause 9.3.37. | +| COUNT-C Activation Time
This IE is used for radio bearers mapped on RLC-TM when the MS is moving to RRC-Cell_Dedicated state. The Activation Time IE is defined in sub-clause 9.3.1. | +| Radio Bearer Activation Time Info
The RB Activation Time Info IE is defined in sub-clause 9.3.77. | +| Uplink Counter Synchronisation info
This structure contains information about PDCP synchronisation. | +| START List (2 bit field)
This field is the binary representation of the number of CN domain START struct. Range : 0 to maxCNdomains-1. | +| START
This field is defined in sub-clause 9.3.102. | +| CN Domain Identity
The CN Domain Identity IE identifies the type of core network domain. This IE is defined in sub-clause 9.3.15. | +| RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described.. Range: 0 to maxRBallRABs-1. | +| RB with PDCP Information
This IE is defined in sub-clause 9.3.86. | + +## 9.2.10 GERAN MOBILITY INFORMATION FAILURE + +This message is sent to indicate a failure to act on a received GERAN MOBILITY INFORMATION message. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.10.1: GERAN MOBILITY INFORMATION FAILURE information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< GERAN MOBILITY INFORMATION FAILURE message content > ::= {   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   < Failure Cause : < Failure Cause and Error Information IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   ! < Content part error : bit (*) = < no string > > };
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.10.2: GERAN MOBILITY INFORMATION FAILURE information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Failure Cause and Error Information
The Failure Cause And Error Information IE is defined in sub-clause 9.3.25. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included when integrity protection is applied. | + +## 9.2.11 GRA UPDATE + +This message is used by the MS to initiate a GRA Update procedure. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +``` +-- ***** +-- +-- GRA UPDATE +-- +-- ***** + +GRAUpdate ::= SEQUENCE { + -- User equipment IEs + g-RNTI G-RNTI, + gra-UpdateCause GRA-UpdateCause, + protocolErrorIndicator ProtocolErrorIndicator, + laterNonCriticalExtensions SEQUENCE { + -- Container for additional R5 extensions + graUpdate-r5-add-ext BIT STRING OPTIONAL, + nonCriticalExtensions SEQUENCE {} OPTIONAL + } OPTIONAL +} +``` + +## 9.2.12 GRA UPDATE CONFIRM + +This message confirms the GRA update procedure and can be used to reallocate new G-RNTI information for the MS valid after the GRA update. + +Radio Bearer : SRB2 + +Direction : GERAN→MS + +``` +-- ***** +-- +-- GRA UPDATE CONFIRM +-- +-- ***** + +GRAUpdateConfirm ::= CHOICE { + r5 SEQUENCE { + graUpdateConfirm-r5 GRAUpdateConfirm-r5-IEs, + laterNonCriticalExtensions SEQUENCE { + -- Container for additional R5 extensions + graUpdateConfirm-r5-add-ext BIT STRING OPTIONAL, + nonCriticalExtensions SEQUENCE {} OPTIONAL + } OPTIONAL + }, + later-than-r5 SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + criticalExtensions SEQUENCE {} + } +} +``` + +``` +GRAUpdateConfirm-r5-IEs ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + integrityProtectionModeInfo IntegrityProtectionModeInfo OPTIONAL, + cipheringModeInfo CipheringModeInfo OPTIONAL, + new-G-RNTI G-RNTI OPTIONAL, + rrc-StateIndicator RRC-StateIndicator, + geran-DRX-CycleLengthCoeff GERAN-DRX-CycleLengthCoefficient OPTIONAL, + -- CN information elements + cn-InformationInfo CN-InformationInfo OPTIONAL, + -- GERAN mobility IEs + gra-Identity GRA-Identity OPTIONAL, + -- Radio bearer IEs + dl-CounterSynchronisationInfo DL-CounterSynchronisationInfo OPTIONAL +} +``` + +END + +## 9.2.13 (void) + +## 9.2.14 HANDOVER COMPLETE + +This message is sent from the MS when a physical channel reconfiguration has been done. + +Radio Bearer : SRB2 + +Direction : MS → GERAN + +**Table 9.2.14.1: HANDOVER COMPLETE information elements** + +``` + +< HANDOVER COMPLETE message content > ::= +{ + -- MS information elements + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < RRC Cause : < RRC Cause IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + { 0 | 1 < Uplink Integrity Protection Activation Info : < Integrity Protection Activation Info IE > > } + { 0 | 1 < Mobile Observed Time Difference : < Mobile Time Difference IE > > } + -- RB information elements + { 0 | 1 < COUNT-C Activation Time : < Activation Time IE > > } + { 0 | 1 < Radio Bearer Uplink Ciphering Activation Time Info : < RB Activation Time Info IE > > } + { 0 | 1 < Uplink Counter Synchronisation Info : < Uplink Counter Synchronisation Info struct > > + ! < Content part error : bit (*) = < no string > > } ; + +< Uplink Counter Synchronisation Info struct > ::= +{ + < START List : bit (2) > + { + < CN Domain Identity : < CN Domain Identity IE > > + < START : < START IE > > } * (1+val(START List)) + { 0 | 1 < RB with PDCP Information List : bit (5) > + < RB with PDCP Information : < RB with PDCP Information IE > > * (1+val(RB with PDCP Information List)) } +}; +``` + +**Table 9.2.14.2: HANDOVER COMPLETE information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98.

| +|

Integrity Check Info
This IE shall be set to the used signalling radio bearer identity when the encoded RRC message is used as the MESSAGE parameter in the integrity protection algorithm. This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included when integrity protection is applied.

| +|

Uplink Integrity Protection Activation Info
This IE contains the time, in terms of RRC sequence numbers, when a new integrity protection configuration shall be activated for the signalling radio bearers. The Integrity protection activation info IE is defined in sub-clause 9.3.36.

| +|

COUNT-C Activation Time
The Activation Time IE is defined in sub-clause 9.3.1

| +|

Radio Bearer Uplink Ciphering Activation Time info
The RB activation time info IE is defined in sub-clause 9.3.77

| +|

Uplink Counter Synchronisation Info struct
This structure enable to synchronise the Uplink security counters.

| +|

START List (2 bit field)
This field is used to repeat information on each RB to be affected, where 0 enables one RB to be described.. Range : 0 to maxCNdomains-1.

| +|

CN Domain Identity
This IE is defined in sub-clause 9.3.15.

| + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| START
This IE is defined in sub-clause 9.3.102. START value to be used in this CN domain. | +| RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described..
Range : 0 to maxRBallRABs-1. | +| RRC Cause
This IE is defined in sub-clause 9.3.94. | +| RB with PDCP Information
This IE is defined in sub-clause 9.3.86. | + +## 9.2.15 HANDOVER FAILURE + +Radio Bearer : SRB2 + +Direction : MS → GERAN + +**Table 9.2.15.1: HANDOVER FAILURE information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< HANDOVER FAILURE message content > ::= {   < Failure Cause : < Failure Cause and Error Information IE > >   < RRC Cause : < RRC Cause IE > >   { 0   1 < RRC Transaction Identifier : < RRC Transaction Identifier IE > > }   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   ! < Content part error : bit (*) = < no string > > ; }
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.15.2: HANDOVER FAILURE information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Integrity Check Info
This IE shall be set to the used signalling radio bearer identity when the encoded RRC message is used as the MESSAGE parameter in the integrity protection algorithm. This IE is defined in sub-clause 9.3.36. | +| RRC Cause
The RRC Cause IE is defined in sub-clause 9.3.94. | +| Failure Cause
The Failure Cause and Error Information IE is defined in sub-clause 9.3.25. | + +## 9.2.16 HANDOVER FROM GERAN Iu COMMAND + +This message is used for handover from GERAN Iu to GERAN A/Gb. + +Radio Bearer : SRB2 + +Direction : GERAN→MS + +**Table 9.2.16.1: HANDOVER FROM GERAN Iu COMMAND information elements** + +``` + +< HANDOVER FROM GERAN Iu COMMAND message content > ::= +{ 0 -- critical extension escape available +{ +-- MS Information Elements + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < Activation Time : < Activation Time IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + { 0 | 1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > } +-- RB Information Elements + { 0 | 1 < RAB Information List : bit (4) > + < RAB Info : < RAB Info IE > > * (1 + val(RAB Information List) ) } + < Handover Command : < Handover Command struct > > + ! < Content part error : bit (*) = < no string > > } + ! < Message escape critical extension : 1 bit (*) = < no string > > } ; + +< Handover Command struct > ::= +{ + < Handover Command Length : bit (8) > + < Handover Command : octet(val(Handover Command Length)) > +}; + +``` + +**Table 9.2.16.2: HANDOVER FROM GERAN Iu COMMAND information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Activation Time
This IE is defined in sub-clause 9.3.1. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included when integrity protection is applied. | +| Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39 | +| RAB Information List (4 bit field)
This field is used to repeat information on each RABto Setup, where 0 enables one RAB to be described. Range : 0 to maxRABsetup-1. Other values are reserved. | +| RAB Information List
The RAB Info IE is defined in sub-clause 9.3.73. | +| Handover Command struct
This structure contains the message HANDOVER COMMAND and the length of the message. The HANDOVER COMMAND message is defined in 3GPP TS 44.018. | + +## 9.2.17 INITIAL DIRECT TRANSFER + +This message is used to initiate a signalling connection based on indication from the upper layers, and to transfer a NAS message. + +Radio Bearer : SRB3 + +Direction : MS → GERAN + +**Table 9.2.17.1: INITIAL DIRECT TRANSFER information elements** + +``` + +< INITIAL DIRECT TRANSFER message content > ::= +{ + < CN Domain Identity : < CN Domain Identity IE > > + < Intra Domain NAS Node Selector : < Intra Domain NAS Node Selector IE > > + < NAS Message : < NAS Message IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + < Start : < Start IE > > + ! < Content part error : bit (*) = < no string > > } ; + +``` + +**Table 9.2.17.2 : INITIAL DIRECT TRANSFER information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

CN Domain Identity
The CN Domain Identity IE is defined in sub-clause 9.3.15.

| +|

Intra Domain NAS Node Selector
The Intra Domain NAS Node Selector IE is defined in sub-clause 9.3.41.

| +|

NAS Message
The NAS Message IE is defined in sub-clause 9.3.54.

| +|

Integrity Check Info
The Integrity Check Info IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied.

| +|

Start
This IE is defined in sub-clause 9.3.102.

| + +## 9.2.18 INTER SYSTEM TO CDMA2000 HANDOVER COMMAND + +This message is used for handover from GERAN *Iu mode* to another system e.g. CDMA2000. One or several messages from the other system can be included in the Inter-RAT message information element in this message. These messages are structured and coded according to that systems specification. + +Radio Bearer : SRB2 + +Direction : GERAN→MS + +**Table 9.2.18.1: INTER SYSTEM TO CDMA2000 HANDOVER COMMAND information elements** + +``` + +< INTER SYSTEM TO CDMA2000 HANDOVER COMMAND message content > ::= +{ 0 --critical extension escape available + { + --MS information elements + < RRC Transaction Identifier : bit (2) > + < Activation Time : < Activation Time IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + { 0 | 1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > } + -- RB information elements + { 0 | 1 < RAB Information List : bit (4) > + < RAB Info : < RAB Info IE > > * (1+val(RAB Information List))} + < Handover to CDMA2000 Command : < Handover to CDMA2000 Command struct > > + ! < Content part error : bit (*) = < no string > > } + ! < Message escape critical extension : 1 bit (*) = < no string > > } ; + +< Handover to CDMA2000 Command struct > ::= +{ + < Length of Handover to CDMA2000 Command contents : bit (8) > + < Handover to CDMA2000 Command : octet(val(Length of Handover to CDMA2000 Command contents)) > +} ; + +``` + +**Table 9.2.18.2 : INTER SYSTEM TO CDMA2000 HANDOVER COMMAND information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier (2 bit field)
This field is defined in sub-clause 9.3.98. | +| Activation Time
This IE is defined in sub-clause 9.3.1. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. | +| Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39 | +| RAB Information List (4 bit field)
This field is the binary representation of the number of Radio Access Bearers to setup. Range : 0 to maxRABsetup-1. Other values are reserved. | +| RAB Info
The RAB Info IE is defined in sub-clause 9.3.73. | +| Handover to CDMA2000 Command struct
This structure contains the message HANDOVER to CDMA2000 COMMAND and the length of the HANDOVER to CDMA2000 COMMAND message. The HANDOVER to CDMA2000 COMMAND message is defined in TTA/EIA/IS-833 and TTA/EIA/IS-2000-5. | + +NOTE: The MSG\_TYPE of the cdma2000 message used for the intersystem handover is included in the first octet of the Handover to CDMA2000 Command struct. It is specified in TTA/EIA/IS-2000 and in TTA/EIA/IS-833. (E.g. MSG\_TYPE ::= {00010001} if Extended Handoff Direction Message (EHDM) is used, MSG\_TYPE ::= {00011111} if General Handoff Direction Message is used, etc.). The order of the bits in this octet representing is given by the following example. If MSG\_TYPE ::= {00010001} (EHDM), the bit number 1 of 'cdma2000 MSG\_TYPE IET' is '0', the bit number 2 shall be '0', etc., and the bit number 8 is '1'. + +The remaining octets in the Handover to CDMA2000 Command struct is coded as the payload of the message used for the inter system handover, as specified in TTA/EIA/IS-2000-5 and in TTA/EIA/IS-833. The bit ordering is similar to the case described above. The bit number 1 of 'cdma2000 message payload' is coded as the first bit of the first record of the message defined in TTA/EIA/IS-2000-5 and in TTA/EIA/IS-833, reading the records defined in TTA/EIA/IS-2000-5 and in TTA/EIA/IS-833 from left to right. + +## 9.2.19 INTER SYSTEM TO UTRAN HANDOVER COMMAND + +This message is used for handover from GERAN *Iu mode* to another system e.g. UTRAN. One or several messages from the other system can be included in the Inter-RAT message information element in this message. These messages are structured and coded according to that systems specification. + +Radio Bearer : SRB2 + +Direction : GERAN→MS + +**Table 9.2.19.1: INTER SYSTEM TO UTRAN HANDOVER COMMAND information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < INTER SYSTEM TO UTRAN HANDOVER COMMAND message content > ::= { 0 -- critical extension escape available { -- MS information elements < RRC Transaction Identifier : < RRC Transaction Identifier IE > > < Activation Time : < Activation Time IE > > { 0   1 < Integrity Check Info : < Integrity Check Info IE > > } { 0   1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > } -- RB information elements < Handover to UTRAN Command : < Handover to UTRAN Command struct > > ! < Content part error : bit (*) = < no string > > } ! < Message escape critical extension : 1 bit (*) = < no string > > } ;  < Handover to UTRAN Command struct > ::= { < Radio Bearer Reconfiguration Length : bit (8) > < Handover to UTRAN Command : octet(val(Radio Bearer Reconfiguration Length)) > };
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.19.2: INTER SYSTEM TO UTRAN HANDOVER COMMAND information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Activation Time
This IE is defined in sub-clause 9.3.1. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The integrity Check Info IE is included when integrity protection is applied. | +| Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39 | +| Handover to UTRAN Command struct
This structure contains the RADIO BEARER RECONFIGURATION message and the length of the RADIO BEARER RECONFIGURATION message. The RADIO BEARER RECONFIGURATION message is defined in 3GPP TS 25.331. | + +## 9.2.20 LCS DOWNLINK INFORMATION + +This message is used by the GERAN to convey embedded LCS RRLP PDUs between the SMLC and the MS. + +Radio Bearer: SRB3 + +Direction: GERAN → MS + +**Table 9.2.20.1: LCS DOWNLINK INFORMATION information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < LCS DOWNLINK INFORMATION message content > ::= { 0 -- critical extension escape available { < RRC Transaction Identifier : < RRC Transaction Identifier IE > > { 0   1 < Integrity Check Info : < Integrity Check Info IE > > } < RRLP PDU Length : bit (8) > < RRLP PDU : octet(val(RRLP PDU Length)) > ! < Content part error : bit (*) = < no string > > } ! < Message escape critical extension : 1 bit (*) = < no string > > } ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.21.2: LCS DOWNLINK INFORMATION information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This field is defined in sub-clause 9.3.98. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied. | +| RRLP PDU Length (8 bit field)
This field is the binary representation of the length in octets of the following RRLP PDU field. Range: 0 to 241. All other values are reserved. | +| RRLP PDU (variable length octet string)
This field contains an RRLP PDU as defined in 3GPP TS 44.031. | + +## 9.2.21 LCS UPLINK INFORMATION + +This message is used by the MS to convey embedded LCS RRLP PDUs between the MS and the GERAN (SMLC). + +Radio Bearer: SRB3 + +Direction: MS → GERAN + +**Table 9.2.21.1: LCS UPLINK INFORMATION information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< LCS UPLINK INFORMATION message content > ::= {   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   < RRLP PDU Length : bit (8) >   < RRLP PDU : octet(val(RRLP PDU Length)) >   ! < Content part error : bit (*) = < no string > > };
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.21.2: LCS UPLINK INFORMATION information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This field is defined in sub-clause 9.3.98. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied. | +| RRLP PDU Length (8 bit field)
This field is the binary representation of the length in octets of the following RRLP PDU field. Range: 0 to 241. All other values are reserved. | +| RRLP PDU (variable length octet string)
This field contains an RRLP PDU as defined in 3GPP TS 44.031. | + +## 9.2.22 MEASUREMENT INFORMATION + +This message is the same as the MEASUREMENT INFORMATION message defined in 3GPP TS 44.018 sub-clause 9.1.54, but shall not contain: + +- RR short PD field. +- Message type field. +- Short layer 2 header field. + +Radio Bearer : SRB1 + +Direction : GERAN → MS + +## 9.2.23 MEASUREMENT REPORT + +This message is the same as the MEASUREMENT REPORT message defined in 3GPP TS 44.018 but shall not contain: + +- RR management Protocol Discriminator IE. +- Skip Indicator IE. +- Measurement Report Message Type IE. + +Radio Bearer : SRB1 + +Direction : MS → GERAN + +## 9.2.24 MS CAPABILITY ENQUIRY + +The MS CAPABILITY ENQUIRY is used by the GERAN to enquire GERAN A/Gb mode, UTRAN or CDMA2000 classmarks and UTRAN predefined configurations from the MS. + +Radio Bearer: SRB2 + +Direction: GERAN → MS + +**Table 9.2.24.1: MS CAPABILITY ENQUIRY information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < MS CAPABILITY ENQUIRY message content > ::=  { 0 -- critical extension escape available   {   -- MS Information Elements     < RRC Transaction Identifier : < RRC Transaction Identifier IE > >     { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }     < Capability Update Requirement : < Capability Update Requirement IE > >     { 0   1 < UTRAN predefined Configuration Requirement: bit (1) > }     ! < Content part error: bit(*) = < no string > > }     ! < Message escape critical extensions: 1 bit (*) = < no string > > } ;
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.24.2: MS CAPABILITY ENQUIRY information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This field is defined in sub-clause 9.3.98.

| +|

Integrity Check Info
This IE is defined in sub-clause 9.3.36.
Integrity check info is included if integrity protection is applied.

| +|

UTRAN predefined Configuration Requirement (1 bit field)
This field corresponds to the information whether the predefined configurations are requested by the network..

bit
1
0 UTRAN predefined configuration not requested by the network
1 UTRAN predefined configuration requested by the network

| +|

Capability Update Requirement
This IE is defined in sub-clause 9.3.4.

| + +## 9.2.25 MS CAPABILITY INFORMATION + +This message is sent by the MS to the GERAN to convey MS specific capability information to the GERAN. + +Radio Bearer: SRB2 + +Direction: MS → GERAN + +**Table 9.2.25.1: MS CAPABILITY INFORMATION information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < MS CAPABILITY INFORMATION message content > ::= {   -- MS Information Elements   { 0   1 < RRC Transaction Identifier : < RRC Transaction Identifier IE > > }   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   { 0   1 < MS GERAN Iu mode Radio Access Capability : < MS GERAN Iu mode Radio Access Capability IE > > } } { 0   1 < MS GERAN A/Gb mode Radio Access Capability : < MS GERAN A/Gb mode Radio Access Capability IE > > } { 0   1 < UE UTRAN Radio Access Capability : < UE UTRAN Radio Access Capability IE > > } { 0   1 < UE UTRAN Radio Access Capability Extension : < UE UTRAN Radio Access Capability Extension IE > > } } { 0   1 < UE UTRAN Predefined Configuration Status Information : < UE UTRAN Predefined Configuration Status Information IE > > } { 0   1 < UE CDMA2000 Radio Access Capability : < UE CDMA2000 Radio Access Capability IE > > } ! < Content part error: bit (*) = < no string > > } ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.25.2: MS CAPABILITY INFORMATION information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This field is defined in sub-clause 9.3.98. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36.
Integrity check info is included if integrity protection is applied. | +| MS GERAN Iu mode Radio Access Capability
This IE is defined in sub-clause 9.3.45. | +| MS GERAN A/Gb mode Radio Access Capability
This IE is defined in sub-clause 9.3.46. | +| UE UTRAN Radio Access Capability
This IE is defined in sub-clause 9.3.108. | +| UE UTRAN Radio Access Capability Extension
This IE is defined in sub-clause 9.3.109. | +| UE UTRAN Predefined Configuration Status Information
This IE is defined in sub-clause 9.3.108a. | +| UE CDMA2000 Radio Access Capability
This IE is defined in sub-clause 9.3.110. | + +## 9.2.26 MS CAPABILITY INFORMATION CONFIRM + +This message is sent by the GERAN to the MS to confirm that the MS capability information has been received. + +Radio Bearer: SRB2 + +Direction: GERAN → MS + +**Table 9.2.26.1: MS CAPABILITY INFORMATION CONFIRM information elements** + +``` + +< MS CAPABILITY INFORMATION CONFIRM message content > ::= +{ 0 -- critical extension escape available +{ +-- MS Information Elements + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } +! < Content part error : bit (*) = < no string > > } +! < Message escape critical extensions: 1 bit (*) = < no string > > } ; + +``` + +**Table 9.2.26.2: MS CAPABILITY INFORMATION CONFIRM information element details****RRC Transaction Identifier** + +This field is defined in sub-clause 9.3.98. + +**Integrity Check Info** + +This IE is defined in sub-clause 9.3.36. + +*Integrity Check Info* IE is included if integrity protection is applied. + +## 9.2.27 (void) + +## 9.2.28 RADIO BEARER RECONFIGURATION + +This message is sent from GERAN to reconfigure parameters related to a change of QoS or change of physical channel. + +Radio Bearer : SRB2 + +Direction : GERAN → MS + +**Table 9.2.28.1: RADIO BEARER RECONFIGURATION information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RADIO BEARER RECONFIGURATION message content > ::=    { 0 -- critical extension escape available     {     -- MS information elements     < RRC Transaction Identifier : < RRC Transaction Identifier IE > >     < Activation Time : < Activation Time IE > >     < RRC State Indicator : < RRC State Indicator IE > >     < GERAN DRX Cycle Length Coefficient : < GERAN DRX Cycle Length Coefficient IE > >     { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }     { 0   1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > }     { 0   1 < Ciphering Mode Info : < Ciphering Mode Info IE > > }     { 0   1 < New G-RNTI : < G-RNTI IE > > }     -- CN information elements     { 0   1 < CN Information Info : < CN Information Info IE > > }     -- GERAN information elements     { 0   1 < GRA Identity : < GRA Identity IE > > }     -- RB information elements     { 0   1 < RAB Information to Reconfigure List : bit (4) >         < RAB Information to Reconfigure : < RAB Information to Reconfigure IE > > * (1+val(RAB Information to  Reconfigure List)) }     { 0   1 < RB Information to Reconfigure List : bit (5) >         { < RB Information to Reconfigure : < RB Information to Reconfigure IE > >           { 0   1 < Physical Information : < Physical Channel Configuration IE > > }           0   1 < NETWORK_RESPONSE_TIMES : < Network Response Times struct > > }         }* (1+val(RB Information to Reconfigure List))     }     { 0   1 < Downlink Counter Synchronisation Info : < Downlink Counter Synchronisation info struct > > }     { 0   1 < RB Information to Be Affected List : bit (5) >         < RB Information to Be Affected : < RB Information to Be Affected IE > > * (1+val(RB Information to Be  Affected List)) }   ! < Content part error : bit (*) = < no string > > } ! < Message escape critical extension : 1 bit (*) = < no string > > } ;
| +| 
 < Downlink Counter Synchronisation Info struct > ::=   < RB with PDCP Information List : bit (5) >   { { 0   1 < RB with PDCP Information : < RB with PDCP Information IE > > }     { 0   1 < PDCP context relocation info : < PDCP context relocation info IE > > } } * (1 + val(RB with PDCP  Information List) );
| +| 
 < Network Response Times struct > ::=   { 0 -- Network's response times on SDCCH       < RESPONSE_TIME_SDCCH : < Response Time SDCCH struct > >     1 -- Network's response times on the assigned DBPSCH       < RESPONSE_TIME_SACCH : < Response Time SACCH struct > > -- Network's response time on SACCH       { 00 -- Network's response time on FACCH/F            -- i.e. between a request sent on TCH/F or FACCH/F and the corresponding response sent on FACCH/F            < RESPONSE_TIME_FACCH_F : < Response Time struct > >         01 < RESPONSE_TIME_FACCH_H : < Response Time struct > > -- Network's response time on FACCH/H         10 < RESPONSE_TIME_FLO : < Response Time FLO struct > > }}; -- Network's response times with FLO
| +| 
 < Response Time SDCCH struct > ::=   < TRMIN_SDCCH : bit (1) > -- Network's minimum response time on SDCCH   < TRESP_SDCCH : bit (1) >;-- Network's maximum response time on SDCCH
| +| 
 < Response Time SACCH struct > ::=   < TRMIN_SACCH : bit (1) > -- Network's minimum response time on SACCH   < TRESP_SACCH : bit (1) >;-- Network's maximum response time on SACCH
| +| 
 < Response Time struct > ::=   < TRMIN : bit (6) >   < TRESP_MAC_DTM : bit (7) >   < TRESP_MAC_Dedicated : bit (7) >;
| +| 
 < Response Time FLO struct > ::= -- Response times when FLO is used   < TRMIN_DCH : bit (6) >   < TRES_DCH_MAC_DTM : bit (7) >   < TRESP_DCH_MAC_Dedicated : bit (7) >;
| + +**Table 9.2.28.2: RADIO BEARER RECONFIGURATION information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Activation Time
The Activation Time IE is defined in sub-clause 9.3.1. | +| RRC State Indicator
This IE is defined in sub-clause 9.3.86. | +| GERAN DRX Cycle Length Coefficient
This IE is defined in sub-clause 9.3.29. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The integrity Check Info IE is included when integrity protection is applied. | +| Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39. The GERAN does not include this IE unless it is performing an SBSS relocation | +| Ciphering Mode Info
This IE is defined in sub-clause 9.3.14. The GERAN does not include this IE unless it is performing an SBSS relocation and a change in ciphering algorithm. | +| New G-RNTI
This IE assigns a new G-RNTI to the MS. This IE is coded as the G-RNTI IE defined in sub-clause 9.3.32. | +| CN Information Info
This IE is defined in sub-clause 9.3.17. | +| GRA Identity
This IE is defined in sub-clause 9.3.30. | +| RAB Information to Reconfigure List (4 bit field)
This field is used to repeat information on each RAB to reconfigure. Range: 0 to maxRABsetup-1, where 0 enables one RAB to be described. | +| RAB Information to Reconfigure
This IE is defined in sub-clause 9.3.76. | +| RB Information to Reconfigure List (5 bit field)
This field is used to repeat information on each RB to reconfigure, where 0 enables one RB to be described. Range : 0 to maxRB-1. | +| RB Information to Reconfigure
This IE is defined in sub-clause 9.3.82. | +| RB Information to Be Affected List (5 bit field)
This field is used to repeat information on each RB to be affected, where 0 enables one RB to be described. Range : 0 to maxRB-1. | +| RB Information to Be Affected
This IE is defined in sub-clause 9.3.81. | +| RB with PDCP Information list (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described. . Range: 0 to maxRBallRABs-1 | +| Downlink Counter Synchronisation Info struct
This structure contains information about PDCP synchronisation. | +| RB with PDCP Information
This IE is defined in sub-clause 9.3.86. | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCP context relocation info
This IE is defined in sub-clause 9.3.116. | +| Physical Information
The Physical Channel Configuration IE is defined in sub-clause 9.3.62. | +| Network Response Times struct
This structure contains information about network response times. | +| TRMIN_SDCCH (1 bit field)
This field indicates the minimum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_SDCCH (1 bit field)
This field indicates the maximum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN_SACCH (1 bit field)
This field indicates the minimum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_SACCH (1 bit field)
This field indicates the maximum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN (6 bit field)
This field indicates the minimum response time of the network, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_MAC_DTM (7 bit field)
TRESP_MAC_Dedicated (7 bit field)
These fields indicate for a given MAC state the maximum response time of the network expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN_DCH (6 bit field)
This field indicates the minimum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. | +| TRES_DCH_MAC_DTM (7 bit field)
TRES_DCH_MAC_Dedicated (7 bit field)
These fields indicate for a given MAC state the maximum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. | + +## 9.2.29 RADIO BEARER RECONFIGURATION COMPLETE + +This message is sent from the MS when a RB and/or a physical channel reconfiguration has been done. + +Radio Bearer : SRB2 + +Direction : MS→ GERAN + +**Table 9.2.29.1: RADIO BEARER RECONFIGURATION COMPLETE information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RADIO BEARER RECONFIGURATION COMPLETE message content > ::=  {   -- MS information elements   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   { 0   1 < Uplink Integrity Protection Activation Info : < Integrity Protection Activation Info IE > > }   { 0   1 < Mobile Observed Time Difference : < Mobile Time Difference IE > > }   -- RB information elements   { 0   1 < COUNT-C Activation Time : < Activation Time IE > > }   { 0   1 < Radio Bearer Uplink Ciphering Activation Time Info : < RB Activation Time Info IE > > }   { 0   1 < Uplink Counter Synchronisation Info : < Uplink Counter Synchronisation Info struct > > }   ! < Content part error : bit (*) = < no string > > } ;  < Uplink Counter Synchronisation Info struct > ::=  {   < START List : bit (2) >   {     < CN Domain Identity : < CN Domain Identity IE > >     < START : < START IE > > } * (1+val(START List))   { 0   1 < RB with PDCP Information List : bit (5) >     < RB with PDCP Information : < RB with PDCP Information IE > > * (1+val(RB with PDCP Information List)) } } ;
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.29.2: RADIO BEARER RECONFIGURATION COMPLETE information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98.

| +|

Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied.

| +|

Uplink Integrity Protection Activation Info
This IE contains the time, in terms of RRC sequence numbers, when a new integrity protection configuration shall be activated for the signalling radio bearers. The Integrity protection activation info IE is defined in sub-clause 9.3.37.

| +|

COUNT-C Activation Time
The Activation Time IE is defined in sub-clause 9.3.1.

| +|

Radio Bearer Uplink Ciphering Activation Time Info
This IE is coded as the RB activation time info IE defined in sub-clause 9.3.77.

| +|

Mobile Observed Time Difference
The Mobile Time Difference IE is defined in sub-clause 9.3.43.

| +|

Uplink Counter Synchronisation Info struct
This structure enable to synchronise the Uplink security counters.

| +|

START List (2 bit field)
START value to be used in this CN domain. This field is the binary representation of the number of RB to be affected. Range : 0 to maxCNdomains-1.

| +|

CN Domain Identity
This IE is defined in sub-clause 9.3.15.

| +|

START
This IE is defined in sub-clause 9.3.102.

| +|

RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB to reconfigure, where 0 enables one RB to be described. . Range : 0 to maxRBallRABs-1.

| +|

RB with PDCP Information
This IE is defined in sub-clause 9.3.86.

| + +## 9.2.30 RADIO BEARER RECONFIGURATION FAILURE + +This message is sent by MS if the configuration given by GERAN is unacceptable or if the MS failed to establish the physical channel(s). + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.30.1: RADIO BEARER RECONFIGURATION FAILURE information elements** + +``` +< RADIO BEARER RECONFIGURATION FAILURE message content > ::= +{ + -- MS information elements + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < RRC Cause : < RRC Cause IE > > + < Failure Cause : < Failure Cause and Error Information IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + -- RB information elements + { 0 | 1 < Potentially Successful RB List : bit (5) > + < RB Identity : < RB Identity IE >> *(1 + val(Potentially Successful RB List) ) } + ! < Content part error : bit (*) = < no string > > }; +``` + +**Table 9.2.30.2: RADIO BEARER RECONFIGURATION FAILURE information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. Integrity Check Info is included if integrity protection is applied. | +| Failure Cause
This Failure Cause and Error Information IE is defined in sub-clause 9.3.25. | +| RRC Cause
This RRC Cause IE is defined in sub-clause 9.3.94. | +| Potentially Successful RB List (5 bit field)
This field is the binary representation of the number of RB for which reconfiguration would have succeeded.
Range : 0 to maxRB-1. | +| RB Identity
This IE is defined in sub-clause 9.3.80. | + +## 9.2.31 RADIO BEARER RELEASE + +This message is used by GERAN to release a radio bearer. It can also include modifications to the configurations of physical channels. + +Radio Bearer : SRB2 + +Direction : GERAN → MS + +**Table 9.2.31.1: RADIO BEARER RELEASE information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RADIO BEARER RELEASE message content > ::=   { 0 -- critical extension escape available     {       -- MS information elements       < RRC Transaction Identifier : < RRC Transaction IdentifierIE > >       < Activation Time : < Activation Time IE > >       < RRC State Indicator : < RRC State Indicator IE > >       < GERAN DRX Cycle Length Coefficient : < GERAN DRX Cycle Length Coefficient IE > >       { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }       { 0   1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > }       { 0   1 < Ciphering Mode Info : < Ciphering Mode Info IE > > }       { 0   1 < New G-RNTI : < G-RNTI IE > > }       -- CN information elements       { 0   1 < Signalling Connection Release Indication : < CN Domain Identity IE > > }       { 0   1 < CN Information Info : < CN Information Info IE > > }       -- GERAN information elements       { 0   1 < GRA Identity : < GRA Identity IE > > }       -- RB information elements       { 0   1 < RAB Information to Reconfigure List : bit (4) >         < RAB Information to Reconfigure : < RAB Information to Reconfigure IE > > *(1+val(RAB Information to  Reconfigure List)) }       { 0   1 < RB Information to Release List : bit (5) >         { < RB Information to Release : < RB Information to Release IE > >           { 0   1 < Physical Information : < Physical Channel Configuration IE > > }           0   1 < NETWORK_RESPONSE_TIMES : < Network Response Times struct > > }         }*(1+val(RB Information to Release List))       }       { 0   1 < RB Information to Be Affected List : bit (5) >         < RB Information to Be Affected : < RB Information to Be Affected IE > > *(1+val(RB Information to Be  Affected List)) }       { 0   1 < Downlink Counter Synchronisation Info : < Downlink Counter Synchronisation info struct > > } ! <  Content part error : bit (*) = < no string > > }     ! < Message escape critical extension : 1 bit (*) = < no string > > } ;
| +| 
 < Downlink Counter Synchronisation Info struct > ::=   < RB with PDCP Information List : bit (5) >   { { 0   1 < RB with PDCP Information : < RB with PDCP Information IE > > }     { 0   1 < PDCP context relocation info : < PDCP context relocation info IE > > } } * (1 + val(RB with PDCP  Information List) );
| +| 
 < Network Response Times struct > ::=   { 0 -- Network's response times on SDCCH     < RESPONSE_TIME_SDCCH : < Response Time SDCCH struct > >     1 -- Network's reponse times on the assigned DBPSCH     < RESPONSE_TIME_SACCH : < Response Time SACCH struct > > -- Network's response time on SACCH     { 00 -- Network's response time on FACCH/F       -- i.e. between a request sent on TCH/F or FACCH/F and the corresponding response sent on FACCH/F       < RESPONSE_TIME_FACCH_F : < Response Time struct > >       01 < RESPONSE_TIME_FACCH_H : < Response Time struct > > -- Network's reponse time on FACCH/H       10 < RESPONSE_TIME_FLO : < Response Time FLO struct > > }}; -- Network's response times with FLO
| +| 
 < Response Time SDCCH struct > ::=   < TRMIN_SDCCH : bit (1) > -- Network's minimum response time on SDCCH   < TRESP_SDCCH : bit (1) >;-- Network's maximum response time on SDCCH
| +| 
 < Response Time SACCH struct > ::=   < TRMIN_SACCH : bit (1) > -- Network's minimum response time on SACCH   < TRESP_SACCH : bit (1) >;-- Network's maximum response time on SACCH
| +| 
 < Response Time struct > ::=   < TRMIN : bit (6) >   < TRESP_MAC_DTM : bit (7) >   < TRESP_MAC_Dedicated : bit (7) >;
| +| 
 < Response Time FLO struct > ::= -- Response times when FLO is used   < TRMIN_DCH : bit (6) >   < TRES_DCH_MAC_DTM : bit (7) >   < TRESP_DCH_MAC_Dedicated : bit (7) >;
| + +**Table 9.2.31.2: RADIO BEARER RELEASE information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Activation Time
The Activation Time IE is defined in sub-clause 9.3.1. | +| RRC State Indicator
This IE is defined in sub-clause 9.3.97. | +| GERAN DRX Cycle Length Coefficient
This IE is defined in sub-clause 9.3.29. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. Integrity Check Info is included if integrity protection is applied. | +| Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39. The GERAN does not include this IE unless it is performing an SBSS relocation | +| Ciphering Mode Info
This IE is defined in sub-clause 9.3.14. The GERAN does not include this IE unless it is performing an SBSS relocation and a change in ciphering algorithm | +| New G-RNTI
This IE assigns a new G-RNTI to the MS. This IE is coded as the G-RNTI IE defined in sub-clause 9.3.33. | +| Signalling Connection Release Indication
The CN Domain Identity IE is defined in sub-clause 9.3.15. | +| CN Information Info
This IE is defined in sub-clause 9.3.17. | +| GRA Identity
This IE is defined in sub-clause 9.3.30. | +| RAB Information to Reconfigure List (4 bit field)
This field is used to repeat information on each RAB to reconfigure, where 0 enables one RAB to be described. Range: 0 to maxRABsetup-1. | +| RAB Information to Reconfigure
This IE is defined in sub-clause 9.3.76. | +| RB Information to Release List (5 bit field)
This field is used to repeat information on each RB to reconfigure, where 0 enables one RB to be described. Range: 0 to maxRB-1. | +| RB Information to Release
This IE is defined in sub-clause 9.3.83. | +| RB Information to Be Affected List (5 bit field)
This field is used to repeat information on each RB to be affected, where 0 enables one RB to be described. Range: 0 to maxRB-1. | +| RB Information to Be Affected
This IE is defined in sub-clause 9.3.81. | +| Downlink Counter Synchronisation Info struct
This structure contains information about PDCP synchronisation. | +| RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described. Range: 0 to maxRBallRABs-1. | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RB with PDCP Information
This IE is defined in sub-clause 9.3.86. | +| PDCP context relocation info
This IE is defined in sub-clause 9.3.116. | +| Physical Information
The Physical Channel Configuration IE is defined in sub-clause 9.3.62. | +| Network Response Times struct
This structure contains information about network response times. | +| TRMIN_SDCCH (1 bit field)
This field indicates the minimum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_SDCCH (1 bit field)
This field indicates the maximum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN_SACCH (1 bit field)
This field indicates the minimum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_SACCH (1 bit field)
This field indicates the maximum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN (6 bit field)
This field indicates the minimum response time of the network, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_MAC_DTM (7 bit field)
TRESP_MAC_Dedicated (7 bit field)
These fields indicate for a given MAC state the maximum response time of the network expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN_DCH (6 bit field)
This field indicates the minimum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. | +| TRES_DCH_MAC_DTM (7 bit field)
TRES_DCH_MAC_Dedicated (7 bit field)
These fields indicate for a given MAC state the maximum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. | + +## 9.2.32 RADIO BEARER RELEASE COMPLETE + +This message is sent from the MS when radio bearer release has been completed. + +Radio Bearer : SRB2 + +Direction : MS → GERAN + +**Table 9.2.32.1: RADIO BEARER RELEASE COMPLETE information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RADIO BEARER RELEASE COMPLETE message content > ::= {   -- MS information elements   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   { 0   1 < Uplink Integrity Protection Activation Info : < Integrity Protection Activation Info IE > > }   -- RB information elements   { 0   1 < COUNT-C Activation Time : < Activation Time IE > > }   { 0   1 < Radio Bearer Uplink Ciphering Activation Time Info : < RB Activation Time Info IE > > }   { 0   1 < Uplink Counter Synchronisation Info : < Uplink Counter Synchronisation Info struct > > }   ! < Content part error : bit (*) = < no string > > } ;  < Uplink counter synchronisation Info struct > ::= {   { < START List : bit (2) >     { < CN Domain Identity : < CN Domain Identity IE > >       < START : < START IE > > } * (1+val(START List))     { 0   1 < RB with PDCP Information List : bit (5) >       < RB with PDCP Information : < RB with PDCP Information IE > > } * (1+val(RB with PDCP Information List)) } };
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.32.2: RADIO BEARER RELEASE COMPLETE information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98.

| +|

Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied.

| +|

Uplink Integrity Protection Activation Info
This IE contains the time, in terms of RRC sequence numbers, when a new integrity protection configuration shall be activated for the signalling radio bearers. The Integrity Protection Activation Info IE is defined in sub-clause 9.3.3. 37

| +|

COUNT-C Activation Time
The Activation Time IE is defined in sub-clause 9.3.1.

| +|

Radio Bearer Uplink Ciphering Activation Time Info
The RB Activation Time Info IE is defined in sub-clause 9.3.77.

| +|

Uplink Counter Synchronisation Info Struct
This structure enable to synchronise the Uplink security counters.

| +|

START List (2 bit field)
START value to be used in this CN domain. This field is the binary representation of the number of RB to be affected. Range : 0 to maxCNdomains-1.

| +|

CN Domain Identity
This IE is defined in sub-clause 9.3.15.

| +|

START
This IE is defined in sub-clause 9.3.102.

| +|

RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described. Range: 0 to maxRBallRABs-1.

| +|

RB with PDCP Information
This IE is defined in sub-clause 9.3.86.

| + +## 9.2.33 RADIO BEARER RELEASE FAILURE + +This message is sent by MS if the configuration given by GERAN is unacceptable or if radio bearer can not be released. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.33.1: RADIO BEARER RELEASE FAILURE information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< RADIO BEARER RELEASE FAILURE message content > ::= {   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   < RRC Cause : < RRC Cause IE > >   < Failure Cause : < Failure Cause and Error Information IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   { 0   1 < Potentially Successful RB List : bit (5) >     < RB Identity : < RB Identity IE > > *(1 + val(Potentially Successful RB List) ) }   ! < Content part error : bit (*) = < no string > > } ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.33.2: RADIO BEARER RELEASE FAILURE information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied. | +| Failure Cause
The Failure Cause and Error Information IE is defined in sub-clause 9.3.25. | +| RRC Cause
This RRC Cause IE is defined in sub-clause 9.3.94. | +| Potentially Successful RB List (5 bit field)
This field is the binary representation of the number of RB for which reconfiguration would have succeeded.
Range : 0 to maxRB-1. | +| RB Identity
This IE is defined in sub-clause 9.3.80. | + +## 9.2.34 RADIO BEARER SETUP + +This message is sent by GERAN to the MS to establish new radio bearer(s). + +Radio Bearer : SRB2 + +Direction : GERAN → MS + +**Table 9.2.34.1: RADIO BEARER SETUP information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RADIO BEARER SETUP message content > ::=    { 0 -- critical extension escape available     {       -- MS information elements       < RRC Transaction Identifier : < RRC Transaction Identifier IE > >       < Activation Time : < Activation Time IE > >       < RRC State Indicator : < RRC State Indicator IE > >       < GERAN DRX Cycle Length Coefficient : < GERAN DRX Cycle Length Coefficient IE > >       { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }       { 0   1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > }       { 0   1 < Ciphering Mode Info : < Ciphering Mode Info IE > > }       { 0   1 < New G-RNTI : < G-RNTI IE > > }       -- CN information elements       { 0   1 < CN Information Info : < CN Information Info IE > > }       -- GERAN information elements       { 0   1 < GRA identity : < GRA identity IE > > }       -- RB information elements       { 0   1 < RB Information to Setup List : bit (3) >         {           < RB Information to Setup : < Signalling RB Information to Setup IE > >           { 0   1 < Physical Information : < Physical Channel Configuration IE > > }           0   1 < NETWORK_RESPONSE_TIMES : < Network Response Times struct > > }         }*(1+val(RB Information to Setup List))       }       { 0   1 < RAB Information for Setup List : bit (4) >         < RAB Information for Setup : < RAB Information for Setup IE > > *(1+val(RAB Information for Setup List)) }       { 0   1 < RB Information to Be Affected List : bit (5) >         < RB Information to Be Affected : < RB Information to Be Affected IE > > *(1+val(RB Information to Be Affected List)) }       { 0   1 < Downlink Counter Synchronisation Info : < Downlink Counter Synchronisation info struct > > }       ! < Content part error : bit (*) = < no string > > }     ! < Message escape critical extension : 1 bit (*) = < no string > > ;
| +| 
 < Downlink Counter Synchronisation Info struct > ::=   < RB with PDCP Information List : bit (5) >   { { 0   1 < RB with PDCP Information : < RB with PDCP Information IE > > }     { 0   1 < PDCP context relocation info : < PDCP context relocation info IE > > } } * (1 + val(RB with PDCP Information List));
| +| 
 < Network Response Times struct > ::=   { 0 -- Network's response times on SDCCH       < RESPONSE_TIME_SDCCH : < Response Time SDCCH struct > >       1 -- Network's response times on the assigned DBPSCH       < RESPONSE_TIME_SACCH : < Response Time SACCH struct > > -- Network's response time on SACCH       { 00 -- Network's response time on FACCH/F            -- i.e. between a request sent on TCH/F or FACCH/F and the corresponding response sent on FACCH/F            < RESPONSE_TIME_FACCH_F : < Response Time struct > >           01 < RESPONSE_TIME_FACCH_H : < Response Time struct > > -- Network's response time on FACCH/H           10 < RESPONSE_TIME_FLO : < Response Time FLO struct > > } }; -- Network's response times with FLO
| +| 
 < Response Time SDCCH struct > ::=   < TRMIN_SDCCH : bit (1) > -- Network's minimum response time on SDCCH   < TRESP_SDCCH : bit (1) > ;-- Network's maximum response time on SDCCH
| +| 
 < Response Time SACCH struct > ::=   < TRMIN_SACCH : bit (1) > -- Network's minimum response time on SACCH   < TRESP_SACCH : bit (1) > ;-- Network's maximum response time on SACCH
| +| 
 < Response Time struct > ::=   < TRMIN : bit (6) >   < TRESP_MAC_DTM : bit (7) >   < TRESP_MAC_Dedicated : bit (7) > ;
| +| 
 < Response Time FLO struct > ::= -- Response times when FLO is used   < TRMIN_DCH : bit (6) >   < TRES_DCH_MAC_DTM : bit (7) >   < TRESP_DCH_MAC_Dedicated : bit (7) > ;
| + +**Table 9.2.34.2: RADIO BEARER SETUP information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Activation Time
The Activation Time IE is defined in sub-clause 9.3.1. | +| RRC State Indicator (2 bit field)
This IE is defined in sub-clause 9.3.97. | +| GERAN DRX Cycle Length Coefficient (3 bit field)
This IE is defined in sub-clause 9.3.29. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied. | +| Integrity Protection Mode Info
This IE is defined in sub-clause 9.3.39. The GERAN does not include this IE unless it is performing an SBSS relocation | +| Ciphering Mode Info
This IE is defined in sub-clause 9.3.14. The GERAN does not include this IE unless it is performing an SBSS relocation and a change in ciphering algorithm | +| New G-RNTI
This IE assigns a new G-RNTI to the MS. This IE is coded as the G-RNTI IE defined in sub-clause 9.3.32. | +| CN Information Info
This IE is defined in sub-clause 9.3.17. | +| GRA Identity
This IE is defined in sub-clause 9.3.30. | +| Signalling RB Information to Setup List (3 bit field)
This field is the binary representation of the number of SRB to setup. Range : 0 to maxSRBsetup-1. | +| Signalling RB Information to Setup
This IE is present for each SRB to establish. This IE is defined in sub-clause 9.3.101. | +| RAB Information for Setup List (4 bit field)
This field is used to repeat information on each RAB to reconfigure, where 0 enables one RAB to be described. Range: 0 to maxRABsetup-1. | +| RAB Information for Setup
This IE is present for each signalling RAB to establish. This IE is defined in sub-clause 9.3.75. | +| RB Information to Be Affected List (5 bit field)
This field is used to repeat information on each RB to reconfigure, where 0 enables one RB to be described. Range: 0 to maxRB-1. | +| RB Information to Be Affected
This IE is defined in sub-clause 9.3.72. | +| Downlink Counter Synchronisation Info struct
This structure contains information about PDCP synchronisation. | +| RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described. Range: 0 to maxRBallRABs-1. | +| RB with PDCP Information
This IE is defined in sub-clause 9.3.86. | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCP context relocation info
This IE is defined in sub-clause 9.3.116. | +| Network Response Times struct
This structure contains information about network response times. | +| TRMIN_SDCCH (1 bit field)
This field indicates the minimum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_SDCCH (1 bit field)
This field indicates the maximum response time of the network on SDCCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN_SACCH (1 bit field)
This field indicates the minimum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_SACCH (1 bit field)
This field indicates the maximum response time of the network on SACCH, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN (6 bit field)
This field indicates the minimum response time of the network, expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRESP_MAC_DTM (7 bit field)
TRESP_MAC_Dedicated (7 bit field)
These fields indicate for a given MAC state the maximum response time of the network expressed as a number of TDMA frames. See 3GPP TS 44.060. | +| TRMIN_DCH (6 bit field)
This field indicates the minimum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. | +| TRESP_DCH_MAC_DTM (7 bit field)
TRESP_DCH_MAC_Dedicated (7 bit field)
These fields indicate for a given MAC state the maximum response time of the network when FLO is used, expressed as a number of TDMA frames. See 3GPP TS 44.160. | + +## 9.2.35 RADIO BEARER SETUP COMPLETE + +This message is sent by MS to confirm the establishment of the radio bearer. + +Radio Bearer : SRB2 + +Direction : MS → GERAN + +**Table 9.2.35.1: RADIO BEARER SETUP COMPLETE information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RADIO BEARER SETUP COMPLETE message content > ::= {   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   { 0   1 < Uplink Integrity Protection Activation Info : < Integrity Protection Activation Info IE > > }   { 0   1 < COUNT-C Activation Time : < Activation Time : bit (8) > > }   { 0   1 < Radio Bearer Uplink Ciphering Activation Time info : < RB Activation Time info IE > > }   { 0   1 < Uplink Counter Synchronisation Info : < Uplink Counter Synchronisation Info struct > > }   ! < Content part error : bit (*) = < no string > > } ;  < Uplink Counter Synchronisation Info struct > ::= {   < START List : bit (2) >   {     < CN Domain Identity : < CN Domain Identity IE > >     < START : < START IE > > } * (1 + val(START List) )   { 0   1 < RB with PDCP Information List : bit (5) >     < RB with PDCP Information : < RB with PDCP Information IE > > } * (1 + val(RB with PDCP Information List) ) };
| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.35.2: RADIO BEARER SETUP COMPLETE information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98.

| +|

Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied.

| +|

Uplink Integrity Protection Activation Info
This IE contains the time, in terms of RRC sequence numbers, when a new integrity protection configuration shall be activated for the signalling radio bearers. The Integrity protection activation info IE is defined in sub-clause 9.3.36.

| +|

COUNT-C Activation Time
The Activation Time IE is defined in sub-clause 9.3.1.

| +|

Radio bearer uplink ciphering activation time info
The RB Activation Time Info IE is defined in sub-clause 9.3.77.

| +|

Uplink Counter Synchronisation Info struct
This structure enables the synchronisation of the Uplink security counters.

| +|

START List (2 bit field)
START value to be used in this CN domain. This field is the binary representation of the number of RB to be affected.
Range : 0 to maxCNdomains-1.

| +|

CN Domain Identity
This IE is defined in sub-clause 9.3.15.

| +|

START
This IE is defined in sub-clause 9.3.102.

| +|

RB with PDCP Information List (5 bit field)
This field is used to repeat information on each RB with PDCP Information, where 0 enables one RB to be described.
Range: 0 to maxRBallRABs-1.

| +|

RB with PDCP Information
This IE is defined in sub-clause 9.3.86.

| + +### 9.2.36 RADIO BEARER SETUP FAILURE + +This message is sent by MS, if it does not support the configuration given by GERAN. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.36.1: RADIO BEARER SETUP FAILURE information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RADIO BEARER SETUP FAILURE message content > ::= {   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   < RRC Cause : < RRC Cause IE > >   < Failure Cause : < Failure Cause and Error Information IE > >   { 0   1 < Integrity Check Info : < Integrity Check Info IE > > }   { 0   1 < Potentially Successful RB List : bit (5) >     < RB Identity : < RB Identity IE > > *(1+val(Potentially Successful RB List)) }   ! < Content part error : bit (*) = < no string > > } ;
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.36.2: RADIO BEARER SETUP FAILURE information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Integrity Check Info
This IE is defined in sub-clause 9.3.36. The Integrity Check Info IE is included if integrity protection is applied. | +| Failure Cause
The Failure Cause and Error Information IE is defined in sub-clause 9.3.25. | +| RRC Cause
This RRC Cause IE is defined in sub-clause 9.3.94. | +| Potentially Successful RB List (5 bit field)
This field is the binary representation of the number of RB for which setup would have succeeded.
Range : 0 to maxRB-1. | +| RB Identity
This IE is defined in sub-clause 9.3.80. | + +## 9.2.37 RRC CONNECTION REJECT + +The network transmits this message when the requested RRC connection cannot be accepted. + +Radio Bearer : SRB2 + +Direction : GERAN → MS + +**Table 9.2.37.1: RRC CONNECTION REJECT information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RRC CONNECTION REJECT message content > ::= { 0 -- critical extension escape available {   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   < Initial MS Identity : < Initial MS Identity IE > >   < RRC Rejection Cause : < RRC Rejection Cause IE > >   < Wait time : < Wait Time IE > >   ! < Content part error : bit (*) = < no string > > }   ! < Message escape critical extensions : 1 bit (*) = < no string > > } ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.2.37.2: RRC CONNECTION REJECT information element details** + +| | +|-------------------------------------------------------------------------------| +| RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98. | +| Initial MS Identity
This IE is defined in sub-clause 9.3.35. | + +**RRc Rejection Cause** + +This IE is defined in sub-clause 9.3.89. In this version of specification, the MS ignores the *Rejection Cause* IE. + +**Wait Time** + +This IE is defined in sub-clause 9.3.112. + +## 9.2.38 RRC CONNECTION RELEASE + +This message is sent by GERAN to release the RRC connection. The message also releases all radio bearers between the MS and GERAN. + +Radio Bearer : SRB 2 + +Direction : GERAN→MS + +**Table 9.2.38.1: RRC CONNECTION RELEASE information elements** + +``` +< RRC CONNECTION RELEASE message content > ::= +{ 0 -- critical extension escape available +{ + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < RRC Release Cause : < Release Cause IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + { 0 | 1 < N308 : bit (3) > } + { 0 | 1 < RPLMN Information : < RPLMN Information IE > > } + ! < Content part error : bit (*) = < no string > > } + ! < Message escape critical extensions : 1 bit (*) = < no string > > } ; +``` + +**Table 9.2.38.2: RRC CONNECTION RELEASE information element details** + +**RRc Transaction Identifier** + +This IE is defined in sub-clause 9.3.98. + +**Integrity Check Info** + +This IE is defined in sub-clause 9.3.36. The *Integrity Check Info* IE is included if integrity protection is applied. + +**N308 (3 bit field)** + +This IE is present when MS is in RRC-CELL\_DEDICATED state. + +N308 indicates the Maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE message. + +| bit | | | | +|-----|---|---|---| +| 3 | 2 | 1 | | +| 0 | 0 | 0 | 1 | +| 0 | 0 | 1 | 2 | +| 0 | 1 | 0 | 3 | +| 0 | 1 | 1 | 4 | +| 1 | 0 | 0 | 5 | +| 1 | 0 | 1 | 6 | +| 1 | 1 | 0 | 7 | +| 1 | 1 | 1 | 8 | + +**Release cause** + +This IE is defined in sub-clause 9.3.90. + +**RPLMN Information** + +This IE is defined in sub-clause 9.3.93. + +## 9.2.39 RRC CONNECTION RELEASE COMPLETE + +This message is sent by MS to confirm that the RRC connection has been released. + +Radio Bearer : SRB2 + +Direction : MS → GERAN + +**Table 9.2.39.1: RRC CONNECTION RELEASE COMPLETE information elements** + +``` + +< RRC CONNECTION RELEASE COMPLETE message content > ::= +{ + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + { 0 | 1 < Error Indication : < Failure Cause and Error Information IE > > } + ! < Content part error : bit (*) = < no string > > } + +``` + +**Table 9.2.39.2: RRC CONNECTION RELEASE COMPLETE information element details****RRC Transaction Identifier** + +This IE is defined in sub-clause 9.3.98. + +**Integrity Check Info**This IE is defined in sub-clause 9.3.36. The *Integrity Check Info* IE is included if integrity protection is applied**Error Indication**The *Failure Cause and Error Information* IE is defined in sub-clause 9.3.25. + +## 9.2.40 RRC CONNECTION REQUEST + +RRC Connection Request is the first message transmitted by the MS when setting up an RRC Connection to the network. + +Radio Bearer : SRB2 + +Direction : MS → GERAN + +**Table 9.2.40.1: RRC CONNECTION REQUEST information elements** + +``` + +< RRC CONNECTION REQUEST message content > ::= +{ + < Initial MS Identity : < Initial MS Identity IE > > + < Establishment Cause : < Establishment Cause IE > > + < Protocol Error Indicator : < Protocol Error Indicator IE > > + ! < Content part error : bit (*) = < no string > > }; + +``` + +**Table 9.2.40.2: RRC CONNECTION REQUEST information element details****Initial MS Identity** + +This IE is defined in sub-clause 9.3.35. + +**Establishment Cause** + +This IE is defined in sub-clause 9.3.21 + +**Protocol Error Indicator** + +This IE is defined in sub-clause 9.3.70. + +## 9.2.41 RRC CONNECTION SETUP + +This message is used by the network to accept the establishment of an RRC connection for an MS, including assignment of signalling link information and optionally physical channel information. + +Radio Bearer : SRB2 + +Direction : GERAN → MS + +**Table 9.2.41.1: RRC CONNECTION SETUP information elements** + +``` +< RRC CONNECTION SETUP message content > ::= +{ 0 -- critical extension escape available +{ +-- MS information elements + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < Initial MS Identity : < Initial MS Identity IE > > + < Activation Time : < Activation Time IE > > + < New G-RNTI : < G-RNTI IE > > + < RRC State Indicator : < RRC State Indicator IE > > + < GERAN DRX Cycle Length Coefficient : < GERAN DRX Cycle Length Coefficient > > + < Capability Update Requirement : < Capability Update Requirement IE > > +-- RB information elements +{ 0 | 1 < Signalling RB Information to Setup list : bit (3) > + < Signalling RB Information to Setup : < Signalling RB Information to Setup IE > > *(1+val(Signalling RB +Information to Setup list)) } +! < Content part error : bit (*) = < no string > > } +! < Message escape critical extensions : 1 bit (*) = < no string > > } ; +``` + +**Table 9.2.41.2: RRC CONNECTION SETUP information element details** + +**RRC Transaction Identifier (2 bit field)** + +This IE is defined in sub-clause 9.3.98. + +**Activation Time (8 bit field)** + +This IE is defined in sub-clause 9.3.1. + +**Initial MS Identity** + +This IE is defined in sub-clause 9.3.35. + +**New G-RNTI** + +This IE assigns a new G-RNTI to the MS. This IE is coded as the *G-RNTI* IE defined in sub-clause 9.3.32. + +**RRC State Indicator** + +This IE is defined in sub-clause 9.3.97. + +**GERAN DRX Cycle Length Coefficient** + +This IE is defined in sub-clause 9.3.29. + +**Capability Update Requirement** + +This IE is defined in sub-clause 9.3.4. + +**Signalling RB Information to Setup list (3 bit field)** + +This field is the binary representation of the number of SRB to setup. Range : 0 to maxSRBsetup-1. + +**Signalling RB Information to Setup** + +This IE is present for each SRB to establish. This IE is defined in sub-clause 9.3.101. + +## 9.2.42 RRC CONNECTION SETUP COMPLETE + +This message confirms the establishment of the RRC Connection by the MS. + +Radio Bearer : SRB2 + +Direction : MS → GERAN + +**Table 9.2.42.1: RRC CONNECTION SETUP COMPLETE information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RRC CONNECTION SETUP COMPLETE message content > ::= {   < RRC Transaction Identifier : < RRC Transaction Identifier IE > >   < START list : bit (2) >   {     < CN Domain Identity : < CN Domain Identity IE > >     < START : < START IE > > } *(1+val(START List))   }   { 0   1 < MS GERAN Iu mode Radio Access Capability : < MS GERAN Iu mode Radio Access Capability IE > > }   < Inter-RAT MS Radio Access Capability : < Inter-RAT MS Radio Access Capability struct > > }   ! < Content part error : bit (*) = < no string > > } ;  < Inter-RAT MS Radio Access Capability struct > ::=    < Inter-RAT MS Radio Access Capability Length : bit (15) >   { 0   1 < MS GERAN A/Gb mode Radio Access Capability : < MS GERAN A/Gb mode Radio Access Capability IE > > }   { 0   1 < UE UTRAN Radio Access Capability : < UE UTRAN Radio Access Capability IE > > }   { 0   1 < UE UTRAN Radio Access Capability Extension : < UE UTRAN Radio Access Capability Extension IE > > }   { 0   1 < UE CDMA2000 Radio Access Capability : < UE CDMA2000 Radio Access Capability IE > > }   < spare bits >**;
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +NOTE: Inter-RAT MS radio access capability are currently included in the MS radio access capability from 24.008. MS radio access capability extension is currently not defined. + +**Table 9.2.42.2: RRC CONNECTION SETUP COMPLETE information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
This IE is defined in sub-clause 9.3.98.

| +|

START List (2 bit field)
This field is the binary representation of the number of CN domains for which a START value is included.
Range : 0 to maxCNdomains-1.

| +|

CN Domain Identity
This field is defined in sub-clause 9.3.15.

| +|

START
This field is defined in sub-clause 9.3.102.

| +|

Inter-RAT MS Radio Access Capability Length
This field indicates the length of the structure excluding the 15 bits to indicate the length.
Range 0 – 32768.

| +|

MS GERAN Iu mode Radio Access Capability
This IE is defined in sub-clause 9.3.45.

| +|

MS GERAN A/Gb mode Radio Access Capability
This IE is defined in sub-clause 9.3.44.

| +|

UE UTRAN Radio Access Capability
This IE is defined in sub-clause 9.3.108

| +|

UE UTRAN Radio Access Capability Extension
This IE is defined in sub-clause 9.3.109.

| +|

UE CDMA2000 Radio Access Capability
This IE is defined in sub-clause 9.3.110.

| + +## 9.2.43 RRC STATUS + +This message is sent to indicate a protocol error. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.43.1: RRC STATUS information elements** + +``` + +< RRC STATUS message content > ::= +{ + < Protocol Error Information : < Protocol Error Information IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + { 0 | 1 < Identification of Received Message : < Identification of Received Message struct > > } + ! < Content part error : bit (*) = < no string > > ; +} + +< Identification of Received Message struct > ::= + < Received Message Type : < Message Type IE > > + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > ; + +``` + +**Table 9.2.43.2: RRC STATUS information element details****Protocol Error Information** + +The *Protocol Error Information* IE is defined in sub-clause 9.3.71. + +**Integrity Check Info** + +The Integrity Check Info IE is defined in sub-clause 9.3.36. + +The Integrity Check Info IE is included if integrity protection is applied. + +**Identification of Received Message struct** + +This structure is present if the *Protocol Error Cause* IE in the *Protocol Error Information* IE has any other value than "CSN.1 violation or encoding error" or "Message type non-existent or not implemented". + +**Received Message Type** + +The Message Type IE is defined in sub-clause 9.2.1. + +**RRC Transaction Identifier** + +The RRC Transaction Identifier IE is defined in sub-clause 9.3.98. + +## 9.2.44 RRC FAILURE INFO + +This message is sent between network nodes in order to provide information about the cause for failure to perform the requested operation. + +Radio Bearer: N/A + +Direction: GERAN/UTRAN→ GERAN + +**Table 9.2.44.1: RRC FAILURE INFO information elements** + +``` + +< RRC FAILURE Info message content > ::= +{ + < Failure cause : 0011 > + < Protocol Error Information : < Protocol Error Information IE > > + | < Failure cause : 0000 | 0001 | 0010 | 01 bit (2) | 1 bit(3) > } + ! < Content part error : bit (*) = < no string > > ; +} + +``` + +**Table 9.2.44.2: RRC FAILURE INFO information element details****Failure Cause** + +The *Failure Cause* IE indicates the cause of the failure in order to perform the required RRC procedure. This IE is defined in sub-clause 9.3.24. + +**Protocol Error Information** + +This IE is defined in sub-clause 9.3.71. + +## 9.2.45 SECURITY MODE COMMAND + +This message is sent by GERAN to start or reconfigure ciphering and/or integrity protection parameters. + +Radio Bearer : SRB2 + +Direction : GERAN→MS + +**Table 9.2.45.1: SECURITY MODE COMMAND information elements** + +``` +< SECURITY MODE COMMAND message content > ::= +{ 0 -- critical extension escape available +{ +-- MS information elements + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < Integrity Check Info : < Integrity Check Info IE > > + < Security Capability : < Security Capability IE > > + { 0 | 1 < Ciphering Mode Info : < Ciphering Mode Info IE > > } + { 0 | 1 < Integrity Protection Mode Info : < Integrity Protection Mode Info IE > > } +-- CN information elements + < CN Domain Identity : < CN Domain Identity IE > > +-- other information elements + { 0 | 1 < GSM MS Security Capability : < GSM MS Security Capability IE > > } +! < Content part error : bit (*) = < no string > > } +! < Message escape critical extensions : 1 bit (*) = < no string > > } ; +``` + +**Table 9.2.45.2: SECURITY MODE COMMAND information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RRC Transaction Identifier
The RRC Transaction Identifier IE is defined in sub-clause 9.3.98.

| +|

Integrity Check Info
The Integrity Check Info IE is defined in sub-clause 9.3.36.

| +|

Security Capability
The Security Capability IE is defined in sub-clause 9.3.100.

| +|

Ciphering Mode Info
Only present if ciphering shall be controlled. The Ciphering Mode Info IE is defined in sub-clause 9.3.14.

| +|

Integrity Protection Mode Info
Only present if integrity protection shall be controlled. The Integrity Protection Mode Info IE is defined in sub-clause 9.3.39.

| +|

CN Domain Identity
Indicates which cipher and integrity protection keys are applicable. The CN Domain Identity IE is defined in sub-clause 9.3.15.

| +|

GSM MS Security Capability
This IE is defined in sub-clause 9.3.33.

| + +## 9.2.46 SECURITY MODE COMPLETE + +This message is sent by MS to confirm the reconfiguration of ciphering and/or integrity protection. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.46.1: SECURITY MODE COMPLETE information elements** + +``` + +< SECURITY MODE COMPLETE message content > ::= +{ + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + < Integrity Check Info : < Integrity Check Info IE > > + { 0 | 1 < Uplink Integrity Protection Activation Info : < Integrity Protection Activation Info IE > > } + { 0 | 1 < Radio Bearer Uplink Ciphering Activation Time Info : < RB Activation Time Info IE > > } + ! < Content part error : bit (*) = < no string > > ; +}; + +``` + +**Table 9.2.46.2: SECURITY MODE COMPLETE information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
The RRC Transaction Identifier IE is defined in sub-clause 9.3.98. | +| Integrity Check Info
Th Integrity Check Info IE is defined in sub-clause 9.3.36. | +| Uplink Integrity Protection Activation Info
The Integrity Protection Activation Info IE contains the time, in terms of RRC sequence numbers, when a new integrity protection configuration shall be activated for the signalling radio bearers. The Integrity Protection Activation Info IE is defined in sub-clause 9.3.37. | +| Radio Bearer Uplink Ciphering Activation Time Info
The RB Activation Time Info IE is defined in sub-clause 9.3.77. | + +## 9.2.47 SECURITY MODE FAILURE + +This message is sent to indicate a failure to act on a received SECURITY MODE CONTROL message. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.47.1: SECURITY MODE FAILURE information elements** + +``` + +< SECURITY MODE FAILURE message content > ::= +{ + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + < Failure Cause : < Failure Cause and Error Information IE > > + ! < Content part error : bit (*) = < no string > > ; +}; + +``` + +**Table 9.2.47.2: SECURITY MODE COMPLETE information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
The RRC Transaction Identifier IE is defined in sub-clause 9.3.98. | +| Integrity Check Info
The Integrity Check Info IE is defined in sub-clause 9.3.36. Integrity Check Info is included if integrity protection is applied | +| Failure Cause
The Failure Cause and Error Information IE is defined in sub-clause 9.3.25 | + +## 9.2.48 SIGNALLING CONNECTION RELEASE + +This message is used to notify the MS that its ongoing signalling connection to a CN domain has been released. + +Radio Bearer : SRB 2 + +Direction : GERAN→ MS + +**Table 9.2.48.1: SIGNALLING CONNECTION RELEASE information elements** + +``` +< SIGNALLING CONNECTION RELEASE message content > ::= +{ 0 -- critical extension escape available +{ + < CN Domain Identity : < CN Domain Identity IE > > + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + ! < Content part error : bit (*) = < no string > > } + ! < Message escape critical extensions : 1 bit (*) = < no string > > } ; +``` + +**Table 9.2.48.2: SIGNALLING CONNECTION RELEASE information element details** + +**CN Domain Identity** + +The *CN Domain Identity* IE is defined in sub-clause 9.3.15. + +**RRC Transaction Identifier** + +The *RRC Transaction Identifier* IE is defined in sub-clause 9.3.98. + +**Integrity Check Info** + +The *Integrity Check Info* IE is defined in sub-clause 9.3.36. Integrity Check Info is included if integrity protection is applied + +## 9.2.49 SIGNALLING CONNECTION RELEASE INDICATION + +This message is used by the MS to indicate to GERAN the release of an existing signalling connection. + +Radio Bearer : SRB 2 + +Direction : MS→GERAN + +**Table 9.2.49.1: SIGNALLING CONNECTION RELEASE INDICATION information elements** + +``` +< SIGNALLING CONNECTION RELEASE INDICATION message content > ::= +{ + < CN Domain Identity : < CN Domain Identity IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + ! < Content part error : bit (*) = < no string > > ; +``` + +**Table 9.2.49.2: SIGNALLING CONNECTION RELEASE INDICATION information element details** + +**CN Domain Identity** + +The *CN Domain Identity* IE is defined in sub-clause 9.3.15. + +**Integrity Check Info** + +The *Integrity Check Info* IE is defined in sub-clause 9.3.36. *Integrity Check Info* IE is included if integrity protection is applied. + +## 9.2.50 (void) + +## 9.2.51 SYSTEM INFORMATION 5 + +This message is the same as the SYSTEM INFORMATION 5 message specified in 3GPP TS 44.018 but shall not contain: + +- RR management Protocol Discriminator IE. +- Skip Indicator IE. + +- L2 pseudo length IE +- System Information Type 5 Message Type IE. + +Radio Bearer : SRB 1 + +Direction : GERAN → MS + +## 9.2.52 SYSTEM INFORMATION 5bis + +This message is the same as the SYSTEM INFORMATION 5bis message specified in 3GPP TS 44.018 but shall not contain: + +- RR management Protocol Discriminator IE. +- Skip Indicator IE. +- L2 pseudo length IE. +- System Information Type 5bis Message Type IE. + +Radio Bearer : SRB 1 + +Direction : GERAN → MS + +## 9.2.53 SYSTEM INFORMATION 5ter + +This message is the same as the SYSTEM INFORMATION 5ter message specified in 3GPP TS 44.018 but shall not contain: + +- RR management Protocol Discriminator IE. +- Skip Indicator IE.. +- L2 pseudo length IE. +- System Information Type 5ter Message Type IE. + +Radio Bearer : SRB 1 + +Direction : GERAN → MS + +## 9.2.54 SYSTEM INFORMATION 6 + +This message is the same as the SYSTEM INFORMATION 6 message specified in 3GPP TS 44.018 but shall not contain: + +- RR management Protocol Discriminator IE. +- Skip Indicator IE.. +- L2 pseudo length IE. +- System Information Type 6 Message Type IE. + +Radio Bearer : SRB 1 + +Direction : GERAN → MS + +## 9.2.55 (void) + +## 9.2.56 UPLINK DIRECT TRANSFER + +This message is used to transfer NAS messages for an existing signalling connection. + +Radio Bearer : SRB3 and SRB4 + +Direction : MS → GERAN + +**Table 9.2.56.1: UPLINK DIRECT TRANSFER information elements** + +``` +< UPLINK DIRECT TRANSFER message content > ::= +{ + < CN Domain Identity : < CN Domain Identity IE > > + < NAS Message : < NAS Message IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + ! < Content part error : bit (*) = < no string > > }; +``` + +**Table 9.2.56.2: UPLINK DIRECT TRANSFER information element details** + +**CN Domain Identity** + +The *CN Domain Identity* IE is defined in sub-clause 9.3.15. + +**NAS Message** + +The *NAS Message* IE is defined in sub-clause 9.3.54. + +**Integrity Check Info** + +The Integrity Check Info IE is defined in sub-clause 9.3.36. *Integrity Check Info* IE is included if integrity protection is applied. + +## 9.2.57 GERAN Iu mode DTM REQUEST + +This message is used by the MS to initiate an allocation of SBPSCH(s) when the MS is in RRC-Cell\_Dedicated state-MAC-Dedicated state. + +Radio Bearer : SRB2 + +Direction : MS→GERAN + +**Table 9.2.57.1: GERAN Iu mode DTM REQUEST information elements** + +``` +< GERAN Iu mode DTM REQUEST message content > ::= +{ + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + < START List : bit (2) > + { + < CN Domain Identity : < CN Domain Identity IE > > + < START : < START IE > > } * (1+val(START List)) + < Iu mode RRC Channel Request Description : < Iu mode Channel Request Description IE > > + ! < Content part error : bit (*) = < no string > > }; +``` + +**Table 9.2.57.2: GERAN Iu mode DTM REQUEST information element details** + +**G-RNTI** + +This IE is defined in sub-clause 9.3.32. + +**Integrity Check Info** + +This IE is defined in sub-clause 9.3.36. The *Integrity Check Info* IE is included if integrity protection is applied. + +**START List (2 bit field)** + +START value to be used in this CN domain. This field is the binary representation of the number of RB to be affected. Range : 0 to maxCNdomains-1. + +**CN Domain Identity** + +This IE is defined in sub-clause 9.3.15. + +**START** + +This IE is defined in sub-clause 9.3.102. + +**Iu mode RRC Channel Request Description** + +This IE is defined in sub-clause 9.3.113. + +**9.2.58 GERAN Iu mode DTM REJECT** + +This message is used by the GERAN to reject the DTM request when the MS is in RRC-Cell\_Dedicated state- MAC-Dedicated state. + +Radio Bearer : SRB2 + +Direction : GERAN→MS + +**Table 9.2.58.1: GERAN Iu mode DTM REJECT information elements** + +``` +< GERAN Iu mode DTM REJECT message content > ::= +{ + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + { 0 | 1 < Integrity Check Info : < Integrity Check Info IE > > } + < Failure Cause : < Failure Cause and Error Information IE > > + < Wait Indication : < Wait Indication IE > > + ! < Content part error : bit (*) = < no string > > } ; +``` + +**Table 9.2.58.2: GERAN Iu mode DTM REJECT information element details** + +**Integrity Check Info** + +This IE is defined in sub-clause 9.3.36. The *Integrity Check Info* IE is included if integrity protection is applied. + +**RRC Transaction Identifier** + +This IE is defined in sub-clause 9.3.98. + +**Failure Cause** + +This *Failure Cause and Error Information* IE is defined in sub-clause 9.3.25. + +**Wait Indication** + +This *Wait Indication* IE is defined in sub-clause 9.3.114. + +**9.3 Information Elements****9.3.1 Activation Time** + +The *Activation Time* IE defines the frame number/time at which the operation/changes caused by the related message shall take effect. + +**Table 9.3.1.1: Activation Time information elements** + +``` +< Activation Time IE > ::= + < Activation Time : bit (22) > ; +``` + +**Table 9.3.1.2: Activation Time information element details** + +**Activation Time (22 bit field)** + +The *Activation Time* field defines the frame number/time at which the operation/changes caused by the related message shall take effect. This field is encoded as a binary number. TDMA Frame Number is defined in 3GPP TS 45.002. + +**9.3.2 BA List Pref** + +The purpose of the *BA List Pref* IE is to provide the mobile station with ARFCN information, which can be used in the cell selection/reselection procedure. This IE is defined in 3GPP TS 44.018. + +### 9.3.3 BA Range + +The purpose of the *BA Range* IE is to provide the mobile station with ARFCN range information which can be used in the cell selection procedure. + +**Table 9.3.3.1: *BA Range* information elements** + +``` +< BA Range IE > ::= + < BA Range Length : bit (8) > + < BA Range Value : octet(val(BA Range Length) ) > ; +``` + +**Table 9.3.3.2: *BA Range* information element details** + +#### **BA Range Length** (8 bit field) + +This field indicates the length of BA Range value in octets as defined in 3GPP TS 44.018. + +#### **BA Range Value** (octet string) + +This IE holds the Value part of the *BA Range* IE defined in 3GPP TS 44.018. + +### 9.3.4 Capability Update Requirement + +The *Capability Update Requirement* IE indicates to the MS which specific capabilities to transfer to the network. + +**Table 9.3.4.1: *Capability Update Requirement* information elements** + +``` +< Capability Update Requirement IE > ::= + < Capability Update Requirement length : bit (4) > + < MS GERAN Iu mode radio access capability update requirement : bit (1) > + < MS GERAN A/Gb mode radio access capability update requirement : bit (1) > + < UE radio capability FDD capability update requirement : bit (1) > + < UE radio capability 3,84 McpsTDD capability update requirement : bit(1) > + < UE radio capability 1,28 Mcps TDD capability update requirement : bit (1) > + < UE CDMA2000 radio access capability update requirement : bit (1) > + < spare bits >**; +``` + +**Table 9.3.4.2: *Capability Update Requirement* information element details** + +#### **Capability Update Requirement length** (4 bit field) + +This field indicates the number of capability updates requirements included in this IE in bits. It is encoded as the binary representation of the amount of capability updates included. Its value is 6 ('0110') in this version of the protocol. + +#### **MS GERAN Iu mode radio access capability update requirement** (1 bit field) + +#### **MS GERAN A/Gb mode radio access capability update requirement** (1 bit field) + +#### **UE radio capability FDD capability update requirement** (1 bit field) + +#### **UE radio capability 3,84 McpsTDD capability update requirement** (1 bit field) + +#### **UE radio capability 1,28 Mcps TDD capability update requirement** (1 bit field) + +#### **UE CDMA2000 radio access capability update requirement** (1 bit field) + +Each of these fields indicates the update requirement of the associated radio access capability. + +bit + +1 + +0 not required + +1 required + +### 9.3.5 CDMA2000 MS security capability + +The CDMA2000 MS security capability IE indicates the MS security capability for CDMA2000. + +### 9.3.6 Cell Channel Description + +The purpose of the *Cell Channel Description* IE is to provide the reference frequency list to be used to decode the mobile allocation information element. + +**Table 9.3.6.1: *Cell Channel Description* information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------| +| < Cell Channel Description IE > ::=
  < Cell Channel Description Value : octet (17) > ; | +|-----------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.6.2: *Cell Channel Description* information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cell Channel Description Value (17 octet field)
The Cell Channel Description Value is coded as the value part of the Cell Channel Description IE specified in 3GPP TS 44.018.

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.7 Cell Description + +The *Cell Description* IE provides a minimum description of a cell, e.g. to allow the mobile station to use its pre-knowledge about synchronization. + +**Table 9.3.7.1: *Cell Description* information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------| +| < Cell Description IE > ::=
  < Cell Description Value : octet(2) > > ; | +|----------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.7.2: *Cell Description* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cell Description Value (2 octet field)
This field indicates the Value part of the Cell Description IE defined in 3GPP TS 44.018.

| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.8 Cell Update Cause + +The *Cell Update Cause* IE indicates the cause for performing a Cell Update. + +**Table 9.3.8.1: *Cell Update Cause* information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------| +| < Cell Update Cause IE > ::=
  < Cell Update Cause : bit (3) > > ; | +|-----------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.8.2: *Cell Update Cause* information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cell Update Cause (3 bit field)

 bit 3 2 1 0 0 0  cell reselection 0 0 1  periodical cell update 0 1 0  uplink data transmission 0 1 1  paging response 1 0 0  radio link failure 1 0 1  RLC unrecoverable error 1 1 0  Invalid RLC/MAC control message
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|--------------------------------| +| All other values are reserved. | +|--------------------------------| + +### 9.3.9 Channel Description + +The *Channel Description* IE provides a description of an allocable channel together with its SACCH. + +**Table 9.3.9.1: *Channel Description* information elements** + +| | +|---------------------------------------------------------------------------------------| +| < Channel Description IE > ::=
< Channel Description Value : octet(3) > > ; | +|---------------------------------------------------------------------------------------| + +**Table 9.3.9.2: *Channel Description* information element details** + +#### **Channel Description Value** + +This IE holds the Value part of the *Channel Description* IE defined in 3GPP TS 44.018. + +### 9.3.10 Channel Description 2 + +The *Channel Description 2* IE is to provide a description of an allocable channel configuration together. + +**Table 9.3.10.1: *Channel Description 2* information elements** + +| | +|-------------------------------------------------------------------------------------------| +| < Channel Description 2 IE > ::=
< Channel Description 2 Value : octet(3) > > ; | +|-------------------------------------------------------------------------------------------| + +**Table 9.3.10.2: *Channel Description 2* information element details** + +#### **Channel Description 2 Value** + +This IE holds the Value part of the *Channel Description 2* IE defined in 3GPP TS 44.018. + +### 9.3.11 Channel Mode + +The *Channel Mode* IE gives information of the mode on coding/decoding and transcoding. The exact mode is determined by the contents of this field and the channel type. + +**Table 9.3.11.1: *Channel Mode* information elements** + +| | +|-------------------------------------------------------------------------| +| < Channel Mode IE > ::=
< Channel Mode Value : octet(1) > > ; | +|-------------------------------------------------------------------------| + +**Table 9.3.11.2: *Channel Mode* information element details** + +#### **Channel Mode Value** + +This IE holds the Value part of the *Channel Mode* IE defined in 3GPP TS 44.018. + +### 9.3.12 Channel Mode 2 + +The *Channel Mode 2* field gives information of the mode on coding/decoding and transcoding. + +**Table 9.3.12.1: *Channel Mode 2* information elements** + +| | +|-----------------------------------------------------------------------------| +| < Channel Mode 2 IE > ::=
< Channel Mode 2 Value : octet(1) > > ; | +|-----------------------------------------------------------------------------| + +**Table 9.3.12.2: Channel Mode 2 information element details****Channel Mode 2 Value** + +This IE holds the value part of the *Channel Mode 2* IE defined in 3GPP TS 44.018. + +## 9.3.13 Ciphering Algorithm + +The *Ciphering Algorithm* IE indicates which type of ciphering algorithm is used. This field is defined in 3GPP TS 33.102. + +**Table 9.3.13.1: Ciphering Algorithm information elements** + +``` +< Ciphering Algorithm IE > ::= + < Ciphering Algorithm : bit (4) > ; +``` + +**Table 9.3.13.2: Ciphering Algorithm information element details****Ciphering Algorithm (4 bit field)** + +bit + +4 3 2 1 + +0 0 0 0            UEA0 -- see 3GPP TS 33.102 + +0 0 0 1            UEA1 -- see 3GPP TS 33.102 + +All other values are reserved. + +## 9.3.14 Ciphering Mode Info + +The *Ciphering Mode Info* IE contains the ciphering specific security mode control information. + +**Table 9.3.14.1: Ciphering Mode Info information elements** + +``` +< Ciphering Mode Info IE > ::= + { + < Ciphering Mode Command : 0 > + | < Ciphering Mode Command : 1 > + { < Ciphering Algorithm : < Ciphering Algorithm IE > > + { 0 | 1 < Ciphering Activation Time for DBPSCH : < Activation Time IE > > } + { 0 | 1 < RB Downlink Ciphering Activation Time Info : < RB Activation Time Info IE > > } + } + }; +``` + +**Table 9.3.14.2: Ciphering Mode Info information element details****Ciphering Mode Command (1 bit field)** + +bit + +1 + +0 stop ciphering mode + +1 start/restart ciphering mode + +**Ciphering Algorithm (4 bit field)** + +The *Ciphering Algorithm* IE is defined in sub-clause 9.3.12 + +**Ciphering Activation Time for DBPSCH** + +The *Activation Time* IE is used for radio bearers mapped on RLC-TM. This IE is defined in sub-clause 9.3.1. + +**RB Downlink Ciphering Activation Time info** + +The *RB Activation Time Info* IE is used for radio bearers mapped on RLC-AM or RLC-UM. This IE is defined in sub-clause 9.3.77. + +### 9.3.15 CN Domain Identity + +The *CN Domain Identity* IE identifies the type of core network domain. + +**Table 9.3.15.1: CN Domain Identity information elements** + +``` +< CN Domain Identity IE > ::= + < CN Domain Identity : bit (2) > ; +``` + +**Table 9.3.15.2: CN Domain Identity information element details** + +#### CN Domain Identity (2 bit field) + +| | | +|-----|-----------| +| bit | | +| 2 1 | | +| 0 0 | CS domain | +| 0 1 | PS domain | +| 1 0 | Reserved | +| 1 1 | Reserved. | + +### 9.3.16 CN Domain Specific DRX Cycle Length Coefficient + +The *CN Domain Specific DRX Cycle Length Coefficient* IE determines the value of the CN domain specific DRX cycle length coefficient to use in DRX computations. The discontinuous reception computations determine the paging blocks to monitor on PCCCH for a specific MS. + +**Table 9.3.16.1: CN Domain Specific DRX Cycle Length Coefficient information elements** + +``` +< CN Domain Specific DRX Cycle Length Coefficient IE > ::= + < CN Domain Specific DRX Cycle Length Coefficient : bit (2) > ; +``` + +**Table 9.3.16.2: CN Domain Specific DRX Cycle Length Coefficient information element details** + +#### CN Domain Specific DRX Cycle Length Coefficient (2 bit field) + +This field is the binary representation of the CN domain specific DRX cycle length coefficient. Range : 6 to 9. + +| | | +|-----|-----------------------------------------------------| +| bit | | +| 2 1 | | +| 0 0 | CN domain specific DRX cycle length coefficient = 6 | +| 0 1 | CN domain specific DRX cycle length coefficient = 7 | +| 1 0 | CN domain specific DRX cycle length coefficient = 8 | +| 1 1 | CN domain specific DRX cycle length coefficient = 9 | + +### 9.3.17 CN Information Info + +The *CN Information Info* IE indicates information about the CN. + +**Table 9.3.17.1: CN Information Info information elements** + +``` +< CN Information info IE > ::= + { 0 | 1 < PLMN Identity : < PLMN Identity IE > > } + { 0 | 1 < CN Domain Specific GSM-MAP NAS System Info : < NAS System Information GSM-MAP IE > > } + { 0 | 1 < Length of CN Domain Related Information : bit (2) > + { < CN Domain Identity : < CN Domain Identity IE > > + < CN Domain Specific GSM-MAP NAS System Info : < NAS System Information GSM-MAP IE > > + } * ( 1 + val ( Length of CN Domain Related Information ) ) + } ; +``` + +**Table 9.3.17.2: CN Information Info information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity
This IE is defined in sub-clause 9.3.63. | +| CN Domain Specific GSM-MAP NAS System Info
The NAS system information GSM-MAP IE is defined in sub-clause 9.3.56. | +| Length of CN Domain Related Information (2 bit field)
This field is used to calculate the number of CN domains included in this IE. Range : 0 to MaxCNdomains-1. | +| CN Domain Identity
The CN Domain Identity IE is defined in sub-clause 9.3.15. | + +## 9.3.18 CN Information Info Full + +The *CN Information Info Full* IE indicates information about the CN. + +**Table 9.3.18.1: CN Information Info Full information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < CN Information Info Full IE > ::=   { 0   1 < PLMN Identity : < PLMN identity IE > > }   { 0   1 < CN Domain Specific GSM-MAP NAS System Info : < NAS System Information GSM-MAP IE > > }   { 0   1 < Length Of CN Domain Related Information : bit (2) >     { < CN Domain Identity : < CN Domain Identity IE > >       < CN Common GSM-MAP NAS System Info : < NAS System Information GSM-MAP IE > >       < CN Domain Specific DRX Cycle Length Coefficient : < CN Domain Specific DRX Cycle Length Coefficient IE     > >     } * 1 + val (Length of CN domain related information)   };
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.18.2: CN Information Info Full information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity
This IE is defined in sub-clause 9.3.63. | +| CN Common GSM-MAP NAS System Info
The NAS System Information GSM-MAP IE is defined in sub-clause 9.3.56. | +| CN Domain Specific GSM-MAP NAS System Info
The NAS System Information GSM-MAP IE is defined in sub-clause 9.3.56. | +| Length Of CN Domain Related Information (2 bit field)
This field is used to calculate the number of CN domains included in this IE. Range : 0 to MaxCNdomains-1. | +| CN Domain Identity
The CN Domain Identity IE is defined in sub-clause 9.3.15. | +| CN Domain Specific DRX Cycle Length Coefficient
The CN Domain Specific DRX Cycle Length Coefficient IE is defined in sub-clause 9.3.16. | + +## 9.3.19 DBPSCH Description + +The *DBPSCH Description* IE describes dedicated physical resources. + +**Table 9.3.19.1: DBPSCH Description information elements** + +``` + +< DBPSCH Description IE > ::= + +{ + -- Common parameters + { 0 | 1 < Starting Time : < Starting Time IE > > } + { 0 | 1 -- Conditional on presence of Mobile Allocation after time or before time + < Cell Channel Description : < Cell Channel Description IE > > } + { 0 | 1 -- Conditional on presence of Frequency Hopping in Description of the channel IEs + { 00 < Frequency Short List after time : < Frequency Short List IE > > + | 01 < Frequency List after time : < Frequency List IE > > + | 10 < Frequency Channel Sequence after time : < Frequency Channel Sequence IE > > + | 11 < Mobile Allocation after time : < Mobile Allocation IE > > }} + { 0 | 1 -- Conditional on Starting Time and at least one Channel Description before time + { 00 < Frequency Short List before time : < Frequency Short List IE > > + | 01 < Frequency List before time : < Frequency List IE > > + | 10 < Frequency Channel Sequence before time : < Frequency Channel Sequence IE > > + | 11 < Mobile Allocation before time : < Mobile Allocation IE > > }} + { 0 | 1 -- Conditional, not used for Handover + < Power Command : < Power Command IE > > } + { 0 | 1 -- Conditional, used for Handover + < Handover struct : < Handover struct > > } + -- Individual parameters + { 00 < TCH : < TCH struct > > + | 01 < PDTCH : < PDTCH struct > > + | 10 < FLO : < FLO struct > > + ! < Message escape : { 11 } bit** = < no string > > } + -- Reserved for future use +}; + +< TCH struct > ::= + +{ + { 0 | 1 < MultiRate Configuration : < MultiRate Configuration IE > > } + -- Description of the first channel + < Description of the first channel after time : < Channel Description 2 IE > > + { 0 | 1 < Description of the First Channel before time : < Channel Description 2 IE > > } + { 0 | 1 < Mode of the Channel Set 1 : < Channel Mode IE > > } + { 0 | 1 < Mode of the Channel Set 2 : < Channel Mode IE > > } + { 0 | 1 < Mode of the Channel Set 3 : < Channel Mode IE > > } + { 0 | 1 < Mode of the Channel Set 4 : < Channel Mode IE > > } + { 0 | 1 < Mode of the Channel Set 5 : < Channel Mode IE > > } + { 0 | 1 < Mode of the Channel Set 6 : < Channel Mode IE > > } + { 0 | 1 < Mode of the Channel Set 7 : < Channel Mode IE > > } + { 0 | 1 < Mode of the Channel Set 8 : < Channel Mode IE > > } + -- Description of the second channel + { 0 | 1 < Description of the Second Channel before time : < Channel Description IE > > } + { 0 | 1 < Description of the Second Channel after time : < Channel Description IE > > } + { 0 | 1 < Mode of the Second Channel : < Channel Mode 2 IE > > } + -- Conditional on value in Channel Description + { 0 | 1 -- Conditional on the value of Channel Description IE + < Description of the multislot configuration : < Multislot Allocation IE > > } +}; + +< PDTCH struct > ::= + +{ + < RRC Packet Uplink Assignment 2 : < RRC Packet Uplink Assignment 2 IE > > + < RRC Packet Downlink Assignment 2 : < RRC Packet Downlink Assignment 2 IE > > +}; + +``` + +``` + +< Handover struct > ::= +{ + < Handover Reference : < Handover Reference IE > > + < Power Command And Access Type : < Power Command And Access Type IE > > + + { 0 | 1 < Dynamic ARFCN Mapping : < Dynamic ARFCN Mapping IE > > } + { 0 | 1 < Synchronization Indication : < Synchronization Indication IE > > + { 0 | 1 -- Conditional on Synchronization Indication value + { 0 < Real Time Difference : < Time Difference IE > > + | 1 < Timing Advance : < Timing Advance IE > > } } } + -- Description of the cell + < Cell Description : < Cell Description IE > > +}; + +< FLO struct > ::= +{ + -- Conditional, present in Release 6, Channel Mode IE and Channel Mode 2 IE not used + { 0 | 1 < FLO Basic Physical Channels Parameters : < FLO Basic Physical Channels Parameters struct> > } + < DL_TIMESLOT_ALLOCATION : bit (8) > -- Downlink timeslot allocation + { + { 0 | 1 < DL TrCH information common for all transport channels : < DL TrCH + Information Common For All Transport Channels IE> > } + { 0 | 1 < Deleted TrCH information list : bit (3) > + { < Deleted DL TrCH information : < Deleted DL TrCH Information IE > > + } }*(1 + val(Deleted TrCH information list) ) + { 0 | 1 < Added or Reconfigured DL TrCH information list : bit (3) > + { < Added or Reconfigured DL TrCH information : < Added or Reconfigured DL TrCH Information IE > > } + }*(1 + val( Added or Reconfigured DL TrCH information list ) ) + }*(N) -- where N is the amount of downlink timeslots (i.e. amount of '1's) assigned in the + -- DL_TIMESLOT_ALLOCATION + { 0 -- Same uplink timeslot allocation as the downlink timeslot allocation provided in + -- DL_TIMESLOT_ALLOCATION + | 1 < UL_TIMESLOT_ALLOCATION : bit (8) > + { + { 0 | 1 < UL TrCH information common for all transport channels : < UL TrCH + Information Common For All Transport Channels IE> > } + { 0 | 1 < Deleted TrCH Information List : bit (3) > + { < Deleted UL TrCH Information : < Deleted UL TrCH Information IE > > + } }*(1 + val(Deleted TrCH Information List) ) + { 0 | 1 < Added or Reconfigured UL TrCH Information List : bit (3) > + { < Added or Reconfigured UL TrCH Information : < Added or Reconfigured UL TrCH Information IE > > } + }*(1 + val( Added or Reconfigured UL TrCH Information List ) ) + }*(M) -- where M is the amount of uplink timeslots (i.e. amount of '1's) assigned in the + -- UL_TIMESLOT_ALLOCATION, if present, else in the DL_TIMESLOT_ALLOCATION +}; + +< FLO Basic Physical Channels Parameters struct > ::= + < Interleaving : < Interleaving IE > > + < Mode : < Mode IE > > + < Modulation : < Modulation IE > > ; + +``` + +**Table 9.3.19.2: DBPSCH Description information element details** + +| | +|--------------------------------------------------------------------------------------------------------------| +|

Handover struct
This structure defines the physical parameters when handover is performed.

| +|

Cell Description
This IE is defined in sub-clause 9.3.7.

| +|

Handover Reference
This IE is defined in sub-clause 9.3.4

| +|

Power Command And Access Type
This IE is defined in sub-clause 9.3.65

| +|

Synchronization Indication

| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| This IE is defined in sub-clause 9.3.104 | +| Frequency Short List after time
The Frequency Short List IE is defined in sub-clause 9.3.28. This IE is conditional on presence of the frequency hopping in either Channel Description IE or Channel Description 2 IE, as indicated in 3GPP TS 44.018. | +| Real Time Difference
The Time Difference IE is defined in sub-clause 9.3.105. This IE is conditional on value of the Synchronization Indication IE, as indicated in 3GPP TS 44.018. | +| Timing Advance
This IE is defined in sub-clause 9.3.106. This IE is defined in sub-clause 9.3.93. This IE is conditional on value of the Synchronization Indication IE, as indicated in 3GPP TS 44.018. | +| Frequency Short List before time
The Frequency Short List IE is defined in sub-clause 9.3.28. This IE is conditional on presence of the Starting Time IE, as indicated in 3GPP TS 44.018. | +| Dynamic ARFCN Mapping
This IE is defined in sub-clause 9.3.20 | +| Description of the First Channel after time
The Channel Description 2 IE is defined in sub-clause 9.3.10. | +| Power Command
This IE is defined in sub-clause 9.3.64 | +| Frequency List after time
The Frequency List IE is defined in sub-clause 9.3.27. This IE is conditional on presence of the frequency hopping in either Channel Description IE or Channel Description 2 IE, as indicated in 3GPP TS 44.018. | +| Mobile Allocation after time
The Mobile Allocation IE is defined in sub-clause 9.3.42. The Mobile Allocation after time IE is conditional on presence of the frequency hopping in either Channel Description IE or Channel Description 2 IE, as indicated in 3GPP TS 44.018. | +| Cell Channel Description
This IE is defined in sub-clause 9.3.6. This IE is conditional on presence of either Mobile Allocation before time or Mobile Allocation after time IE, as indicated in 3GPP TS 44.018. | +| Description of the Multislot Configuration
The Multislot Allocation IE is defined in sub-clause 9.3.53. . | +| Mode of the Channel Set X
The Channel Mode IE is defined in sub-clause 9.3.11. The channel mode is defined for the channel set X, where X has a range from 1 to 8. | +| Description of the Second Channel after time
The Channel Description IE is defined in sub-clause 9.3.9. | +| Mode of the Second Channel
The Channel Mode2 IE is defined in sub-clause 9.3.12. | +| Starting Time
This IE is defined in sub-clause 9.3.103. | +| Frequency List before time
The Frequency List IE is defined in sub-clause 9.3.27. The Frequency List before time IE is conditional on presence of the Starting Time IE, as indicated in 3GPP TS 44.018. | +| Frequency Channel Sequence before time
The Frequency Channel Sequence IE is defined in sub-clause 9.3.26. The Frequency Channel Sequence before time IE is conditional on presence of the Starting Time IE, as indicated in 3GPP TS 44.018. | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Mobile Allocation before time
The Mobile Allocation IE is defined in sub-clause 9.3.42. This IE is conditional on presence of the Starting Time IE, as indicated in 3GPP TS 44.018.

| +|

Description of the First Channel before time
The Channel Description 2 IE is defined in sub-clause 9.3.10.

| +|

Description of the Second Channel before time
The Channel Description IE is defined in sub-clause 9.3.9.

| +|

MultiRate Configuration
This IE is defined in sub-clause 9.3.52.

| +|

RRC Packet Uplink Assignment
This IE is defined in sub-clause 9.3.96

| +|

RRC Packet Downlink Assignment
This IE is defined in sub-clause 9.3.95

| +|

Description of the Uplink Packet Channel Assignment2
The RRC Packet Uplink Assignment IE is defined in sub-clause 9.3.96a.

| +|

Description of the Downlink Packet Channel Assignment2
The RRC Packet Downlink Assignment IE is defined in sub-clause 9.3.95a.

| +|

FLO Basic Physical Channels Parameters struct
This structure defines the basic physical channel parameters when FLO is used.

| +|

Interleaving (2 bit field )
This IE is defined in sub-clause 9.3.118.

| +|

Mode (2 bit field)
This IE is defined in sub-clause 9.3.119.

| +|

Modulation (2 bit field)
This IE is defined in sub-clause 9.3.120.

| +|

FLO struct
This structure defines all the TrCHs parameters when FLO is configured for each timeslot.

| +|

DL_TIMESLOT_ALLOCATION (8 bit field)
This information field indicates the assigned downlink DBPSCH(s). Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least one timeslot must be assigned.

0 Timeslot is not assigned
1 Timeslot is assigned

| +|

UL_TIMESLOT_ALLOCATION (8 bit field)
This information field indicates the assigned uplink DBPSCH(s). Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least one timeslot must be assigned.

0 Timeslot is not assigned
1 Timeslot is assigned

| +|

UL TrCH Information Common For All Transport Channels
The IE UL TrCH Information Common For All Transport Channels is defined in sub-clause 9.3.134.

| +|

Deleted TrCH Information List (3 bit field)
This field is used to repeat information on each TrCH to be deleted, where 0 enables one TrCH to be described. Range: 0 to maxTrCH-1.

| +|

Deleted UL TrCH Information
This IE is defined in sub-clause 9.3.124.

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

Added or Reconfigured UL TrCH Information List (3 bit field)

This field is used to repeat information on each TrCH to be added or reconfigured in UL, where 0 enables one TrCH to be described. Range: 0 to maxTrCH-1.

| +|

Added or Reconfigured UL TrCH information

The IE Added or Reconfigured UL TrCH Information is defined in sub-clause 9.3.122.

| +|

DL TrCH Information Common For All Transport Channels

The IE DL TrCH Information Common For All Transport Channels is defined in sub-clause 9.3.125.

| +|

Deleted DL TrCH Information

This IE is defined in sub-clause 9.3.123.

| +|

Added or Reconfigured DL TrCH Information list (3 bit field)

This field is used to repeat information on each TrCH to be added or reconfigured in DL, where 0 enables one TrCH to be described. Range: 0 to maxTrCH-1.

| +|

Added or Reconfigured DL TrCH information

The IE Added or Reconfigured DL TrCH Information is defined in sub-clause 9.3.121.

| + +## 9.3.20 Dynamic ARFCN Mapping + +The purpose of the *Dynamic ARFCN Mapping* IE is to provide information on ARFCN mapping to physical frequencies (see 3GPP TS 45.005). This IE is coded as defined in 3GPP TS 44.018. + +## 9.3.21 Establishment Cause + +The *Establishment Cause* IE defines the cause for an RRC connection establishment request. + +**Table 9.3.21.1: Establishment Cause information elements** + +| | +|-----------------------------------------------------------------------------------------------------| +|

< Establishment Cause IE > ::=

< Establishment Cause : bit (5) > ;

| +|-----------------------------------------------------------------------------------------------------| + +**Table 9.3.21.2: Establishment Cause information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Establishment Cause (5 bit field)

bit

5 4 3 2 1

0 0 0 0 0 Originating Conversational Call

0 0 0 0 1 Originating Streaming Call

0 0 0 1 0 Originating Interactive Call

0 0 0 1 1 Originating Background Call

0 0 1 0 0 Originating Subscriber traffic Call

0 0 1 0 1 Terminating Conversational Call

0 0 1 1 0 Terminating Streaming Call

0 0 1 1 1 Terminating Interactive Call

0 1 0 0 0 Terminating Background Call

0 1 0 0 1 Emergency Call

0 1 0 1 0 Inter-RAT cell re-selection

0 1 0 1 1 Inter-RAT cell change order

0 1 1 0 0 Registration

0 1 1 0 1 Detach

0 1 1 1 0 Originating High Priority Signalling

0 1 1 1 1 Originating Low Priority Signalling

1 0 0 0 0 Call re-establishment

1 0 0 0 1 Terminating High Priority Signalling

1 0 0 1 0 Terminating Low Priority Signalling

1 0 0 1 1 Terminating – cause unknown

| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------| +| 1 0 1 0 0 Inter-mode cell re-selection | +|----------------------------------------| + +## 9.3.22 Expiration Time Factor + +The *Expiration Time Factor* IE defines the validity of physical channel information. + +**Table 9.3.22.1: *Expiration Time Factor* information elements** + +| | +|------------------------------------------------------------------------------------| +| < Expiration Time Factor IE > ::=
< Expiration Time Factor : bit (3) > ; | +|------------------------------------------------------------------------------------| + +**Table 9.3.22.2: *Expiration Time Factor* information element details** + +### Expiration Time Factor (3 bit field) + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bit
3 2 1
0 0 0 2 times
0 0 1 4 times
0 1 0 8 times
0 1 1 16 times
1 0 0 32 times
1 0 1 64 times
1 1 0 128 times
1 1 1 256 times | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 9.3.23 Extension + +The *Extension* IE indicates possible extension for empty choice branches. + +**Table 9.3.23.1: *Extension* information elements** + +| | +|-------------------------------| +| < Extension IE > ::=
null; | +|-------------------------------| + +## 9.3.24 Failure Cause + +The *Failure Cause* IE indicates the cause of the failure in order to perform the required RRC procedure. + +**Table 9.3.24.1: *Failure Cause* information elements** + +| | +|------------------------------------------------------------------| +| < Failure Cause IE > ::=
< Failure Cause : bit (4) > ; | +|------------------------------------------------------------------| + +**Table 9.3.24.2: Failure Cause information element details** + +| | | +|------------------------------------|-------------------------------------------| +| Failure Cause (4 bit field) | | +| bit | | +| 4 3 2 1 | | +| 0 0 0 0 | configuration unsupported | +| 0 0 0 1 | physical channel failure | +| 0 0 1 0 | incompatible simultaneous reconfiguration | +| 0 0 1 1 | protocol error | +| 0 1 0 0 | compressed mode runtime error | +| 0 1 0 1 | cell reselection | +| 0 1 1 0 | invalid configuration | +| 0 1 1 1 | configuration incomplete | +| 1 0 0 0 | unsupported measurement | +| 1 0 0 1 | Inter-mode Protocol Error | +| All others values are reserved | | + +## 9.3.25 Failure Cause and Error Information + +The *Failure Cause and Error Information* IE indicates the cause for failure to perform the requested procedure. + +**Table 9.3.25.1: Failure Cause and Error Information information elements** + +| | +|---------------------------------------------------------------------------| +| < Failure Cause and Error Information IE > ::= | +| { < Failure Cause : 0011> | +| < Protocol Error Information : < Protocol Error Information IE > > | +| < Failure cause : 0000 0001 0010 01 bit (2) 1 bit (3) > }; | + +**Table 9.3.25.2: Failure Cause and Error Information information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Failure Cause | +| The Failure Cause IE is defined in sub-clause 9.3.24. | +| Protocol Error Information | +| The IE indicates information about the protocol error when the IE " Failure Cause " has the value "Protocol error". This IE is defined in sub-clause 9.3.71. | + +## 9.3.26 Frequency Channel Sequence + +The purpose of the *Frequency Channel Sequence* IE is to provide the absolute radio frequency channel numbers used in the mobile hopping sequence. This information element shall only be used for radio frequency channels in the primary GSM band (see 3GPP TS 45.005). + +**Table 9.3.26.1: Frequency Channel Sequence information elements** + +| | +|----------------------------------------------------------| +| < Frequency Channel Sequence IE > ::= | +| < Frequency Channel Sequence Value : octet(9) > ; | + +**Table 9.3.26.2: Frequency Channel Sequence information element details** + +| | +|-----------------------------------------------------------------------------------------------------| +| Frequency Channel Sequence Value | +| This IE holds the Value part of the Frequency Channel Sequence IE defined in 3GPP TS 44.018. | + +### 9.3.27 Frequency List + +The purpose of the *Frequency List* IE is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence. + +**Table 9.3.27.1: *Frequency List* information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------| +| < Frequency List IE > ::=
< Frequency List Length : bit (8) >
< Frequency List Value : octet (val(Frequency List Length)) >; | +|--------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.27.2: *Frequency List* information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------| +| Frequency List Length (8 bit field)
This field indicates the length of the Frequency List Value in octets | +|---------------------------------------------------------------------------------------------------------------------| + +| | +|-----------------------------------------------------------------------------------------------------------------------| +| Frequency List Value
This IE holds the Value part of Frequency List IE as defined in 3GPP TS 44.018. | +|-----------------------------------------------------------------------------------------------------------------------| + +### 9.3.28 Frequency Short List + +The purpose of the *Frequency Short List* IE is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence, in a small fixed length information element to obtain when possible the HANDOVER COMMAND message in a single block. + +**Table 9.3.28.1: *Frequency Short List* information elements** + +| | +|---------------------------------------------------------------------------------------| +| < Frequency Short List IE > ::=
< Frequency Short List Value : octet(9) > ; | +|---------------------------------------------------------------------------------------| + +**Table 9.3.28.2: *Frequency Short List* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------| +| Frequency Short List Value
This IE holds the Value part of the Frequency Short List IE defined in 3GPP TS 44.018. | +|------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.29 GERAN DRX Cycle Length Coefficient + +The *GERAN DRX Cycle Length Coefficient* IE determines the value of the GERAN DRX cycle length coefficient to use in DRX computations. The discontinuous reception computations determine the paging blocks to monitor on PCCCH for a specific MS. + +**Table 9.3.29.1: *GERAN DRX Cycle Length Coefficient* information elements** + +| | +|-----------------------------------------------------------------------------------------------------------| +| < GERAN DRX Cycle Length Coefficient IE > ::=
< GERAN DRX Cycle Length Coefficient : bit (3) >; | +|-----------------------------------------------------------------------------------------------------------| + +**Table 9.3.29.2: *GERAN DRX Cycle Length Coefficient* information element details** + +| | +|---------------------------------------------------------| +| GERAN DRX Cycle Length Coefficient (3 bit field) | +|---------------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bit
3 2 1
0 0 0 GERAN DRX cycle length coefficient = 3
0 0 1 GERAN DRX cycle length coefficient = 4
0 1 0 GERAN DRX cycle length coefficient = 5
0 1 1 GERAN DRX cycle length coefficient = 6
1 0 0 GERAN DRX cycle length coefficient = 7
1 0 1 GERAN DRX cycle length coefficient = 8 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------| +| 1 1 0 GERAN DRX cycle length coefficient = 9
1 1 1 Reserved | +|----------------------------------------------------------------| + +### 9.3.30 GRA Identity + +The *GRA Identity* IE identifies a GERAN Registration Area (GRA). In case of overlapping GRAs in the cell, it can be used to indicate to the MS which GRA it shall use. + +**Table 9.3.30.1: *GRA Identity* information elements** + +| | +|-------------------------------------| +| < GRA Identity IE > ::= | +| < GRA Identity : bit(16) > ; | + +**Table 9.3.30.2: *GRA Identity* information element details** + +| | +|---------------------------------------------------------------------------------------------------------------| +| GRA Identity (16 bit field)
The GRA identity field is encoded as a binary number. Range 0 to 65535. | +|---------------------------------------------------------------------------------------------------------------| + +### 9.3.31 GRA Update Cause + +The *GRA Update Cause* IE indicates the cause for performing GRA Update. + +**Table 9.3.31.1: *GRA Update Cause* information elements** + +| | +|----------------------------------------| +| < GRA Update Cause IE > ::= | +| < GRA Update Cause : bit(2) > ; | + +**Table 9.3.31.2: *GRA Update Cause* information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GRA Update Cause (2 bit field)
bit
2 1
0 0            change of GRA
0 1            periodic GRA update
All others values are reserved | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.32 G-RNTI + +The *G-RNTI* (*GERAN Radio Network Temporary Identity*) IE is allocated to an MS having a RRC connection and identifies the MS within GERAN. + +**Table 9.3.32.1: *G-RNTI* information elements** + +| | +|--------------------------------------------| +| < G-RNTI IE > ::= | +| < Serving BSC identity : bit (12) > | +| < S-RNTI : bit (20) > ; | + +**Table 9.3.32.2: *G-RNTI* information element details** + +| | +|----------------------------------------------------------------------------------------------------------------| +| Serving BSC identity (12 bit field)
This field identifies the mobile station's serving BSC in GERAN. | +|----------------------------------------------------------------------------------------------------------------| + +| | +|----------------------------------------------------------------------------------------------------------| +| S-RNTI (20 bit field)
This field identifies the mobile station in the area of its serving BSC. | +|----------------------------------------------------------------------------------------------------------| + +### 9.3.33 GSM MS Security Capability + +The *GSM MS Security Capability* IE indicates the MS security capability for *A/Gb mode*. + +**Table 9.3.33.1: GSM MS Security Capability information elements** + +``` +< GSM MS Security Capability IE > ::= + < A5/1 support : bit (1) > + < A5/2 support : bit (1) > + < A5/3 support : bit (1) > + < A5/4 support : bit (1) > + < A5/5 support : bit (1) > + < A5/6 support : bit (1) > + < A5/7 support : bit (1) > + < spare bit >; -- Reserved +``` + +**Table 9.3.33.2: GSM MS Security Capability information element details** + +A5/1 support (1 bit field) + A5/2 support (1 bit field) + A5/3 support (1 bit field) + A5/4 support (1 bit field) + A5/5 support (1 bit field) + A5/6 support (1 bit field) + A5/7 support (1 bit field) + +These field indicates the support of the GSM encryption algorithm A5/X, where X has a range from 1 to 7. + +bit + 1 + 0 not supported + 1 supported + +### 9.3.34 Handover Reference + +The *Handover Reference* IE is to provide a handover reference value used for access identification. + +**Table 9.3.34.1: Handover Reference information elements** + +``` +< Handover Reference IE > ::= + < Handover Reference Value : octet(1) >; +``` + +**Table 9.3.34.2: Handover Reference information element details** + +**Handover Reference Value** (1 octet field) + +The Handover Reference content is coded as the value part of the *Handover Reference* IE defined in 3GPP TS 44.018. + +### 9.3.35 Initial MS Identity + +The *Initial MS Identity* IE identifies the MS at a request of an RRC connection. + +**Table 9.3.35.1: Initial MS Identity information elements** + +``` + +< Initial MS Identity IE > ::= +{ + < MS Identity Type : 0000 > -- GSM-MAP TMSI and LAI + < TMSI : bit (32) > + < LAI : octet (5) > +| < MS Identity Type : 0001 > -- GSM-MAP P-TMSI and RAI + < PTMSI : bit (32) > + < RAI : octet (6) > +| < MS Identity Type : 0010 > -- GSM-MAP IMSI or IMEI + < Length of Mobile Identity contents : bit (4) > + < Mobile Identity : octet (val (Length of Mobile Identity contents)) > +| < MS Identity Type : 0011 > -- ESN (DS-41) + < ESN : bit (32) > +| < MS Identity Type : 0100 > -- IMSI (DS-41) + < IMSI length : bit (2) > -- only allowed 0 - 2 + < IMSI : octet (5+val(IMSI Length)) > +| < MS Identity Type : 0101 > -- reserved for IMSI and ESN (DS-41) + < IMSI length : bit (2) > -- only allowed 0 - 2 + < IMSI : octet (5+val(IMSI Length)) > + < ESN : bit (32) > +| < MS Identity Type : 0110 > -- reserved for TMSI (DS-41) + < TMSI length : bit (4) > + < TMSI-DS-41 : octet (2+val(length)) > + +| < Message escape : { 1 bit(3) } bit** = < no string > > -- reserved +}; + +``` + +**Table 9.3.35.2: Initial MS Identity information element details***GSM-MAP TMSI and LAI structure***TMSI** (32 bit field) + +The Temporary Mobile Subscriber Identity (TMSI) is associated with the mobile subscriber and defined in 3GPP TS 23.003. This field is coded as a binary number. Range 0 to 4294967295. + +**LAI** (5 octet field) + +This field is coded using the V format of the type 3 information element *Location Area Identification* defined in 3GPP TS 44.018. + +*GSM-MAP P-TMSI and RAI structure***PTMSI** (32 bit field) + +The Packet Temporary Mobile Station Identity (PTMSI) is associated with the mobile subscriber and defined in 3GPP TS 23.003. This field is encoded as a binary number. Range 0 to 4294967295. + +**RAI** (48 bit field) + +This field contains the Routing Area identification. This field is described in 3GPP TS 44.018. + +*GSM-MAP IMSI or IMEI***Mobile Identity** (variable length octet string) + +This octet string is the representation of the Mobile Identity. The encoding of this octet string is the value part (starting with octet 3) of the type 4 information element *Mobile Identity* defined in 3GPP TS 24.008. + +Any value other than IMSI and IMEI for the type of identity in this octet string is spare. + +## 9.3.36 Integrity Check Info + +The *Integrity Check Info* IE contains the RRC message sequence number needed in the calculation of XMAC-I (see 3GPP TS 33.102) and the calculated MAC-I. + +**Table 9.3.36.1: Integrity Check Info information elements** + +``` +< Integrity Check Info IE > ::= + < Message Authentication Code : bit (32) > -- see 3GPP TS 33.102 + < RRC Message sequence number : bit (4) > ; +``` + +**Table 9.3.36.2: Integrity Check Info information element details****Message Authentication Code (32 bit field)** + +This field indicates authentication code of the message. The 27 MSB of the IE shall be set to zero and the 5 LSB of the IE shall be set to the used signalling radio bearer identity when the encoded RRC message is used as the MESSAGE parameter in the integrity protection algorithm. + +**RRC Message Sequence Number (4 bit field)** + +This field is the binary representation of the sequence number of the RRC message. Range 0 to 15. + +This field shall be set to zero when the encoded RRC message is used as the MESSAGE parameter in the integrity protection algorithm. + +## 9.3.37 Integrity Protection Activation Info + +The *Integrity Protection Activation Info* IE contains the time, in terms of RRC sequence numbers, when a new integrity protection configuration shall be activated for the signalling radio bearers. + +**Table 9.3.37.1: Integrity Protection Activation Info information elements** + +``` +< Integrity Protection Activation Info IE > ::= + < RRC message sequence number : bit (4) > * 4; +``` + +**Table 9.3.37.2: Integrity Protection Activation Info information element details****RRC Message Sequence Number (4 bit field)** + +These fields are binary representation of the RRC sequence number. Range 0 to 15. + +The RRC sequence number shall be applied for the signalling radio bearers in the order SRB4, SRB3, SRB2 and SRB1. + +## 9.3.38 Integrity Protection Algorithm + +The *Integrity Protection Algorithm* IE indicates which type of UMTS Integrity Algorithm is used. This field is defined in 3GPP TS 33.102. + +**Table 9.3.38.1: Integrity Protection Algorithm information elements** + +``` +< Integrity Protection Algorithm IE > ::= + < Integrity Protection Algorithm : bit (4) > ; +``` + +**Table 9.3.38.2: Integrity Protection Algorithm information element details****Integrity Protection Algorithm (4 bit field)** + +bit + +4 3 2 1 + +0 0 0 1 + +UIA1 -- see 3GPP TS 33.102 + +All other values are reserved. + +## 9.3.39 Integrity Protection Mode Info + +The *Integrity Protection Mode Info* IE contains information about the integrity protection. + +**Table 9.3.39.1: Integrity Protection Mode Info information elements** + +``` + +< Integrity Protection Mode Info IE > ::= +{ + < Integrity protection mode command : 0 > + < Integrity protection initialisation number : bit (32) > +| < Integrity protection mode command : 1 > + < Downlink integrity protection activation info : < Integrity protection activation info IE > > +} +{ 0 | 1 < Integrity protection algorithm : < Integrity protection algorithm IE > > } +}; + +``` + +**Table 9.3.39.2: Integrity Protection Mode Info information element details****Integrity protection mode command (1 bit field)** + +bit + 1 + 0 start + 1 modify + +**Downlink integrity protection activation info** + +The Integrity protection activation info IE is defined in sub-clause 9.3.37. + +**Integrity protection initialisation number (32 bit field)** + +This field is the FRESH random value generated by the network side as it is defined in 3GPP TS 33.102. + +**Integrity protection algorithm** + +This IE is defined in sub-clause 9.3.1.16. + +## 9.3.40 (void) + +## 9.3.41 Intra Domain NAS Node Selector + +This IE specifies information for routing a signalling connection to a CN node within a CN domain. + +**Table 9.3.41.1: Intra Domain NAS Node Selector information elements** + +``` + +< Intra Domain NAS Node Selector IE > ::= +{ 0 -- release 5 +{ 0 -- GSM-MAP-type PLMN + -- Routing basis +{ 000 < Routing Parameter TMSI-PTMSI : bit (10) > + -- TMSI allocated in current LA or PTMSI allocated in current RA +| 001 < Routing Parameter TMSI-PTMSI : bit (10) > + -- TMSI allocated in another LA of this PLMN or PTMSI allocated in another RA of this PLMN +| 010 < Routing Parameter TMSI-PTMSI : bit (10) > + -- TMSI or PTMSI allocated in another PLMN +| 011 < Routing Parameter IMSI : bit (10) > + -- NAS identity is IMSI (response to IMSI paging) +| 100 < Routing Parameter IMSI : bit (10) > + -- NAS identity is IMSI (MS-initiated event) +| 101 < Routing Parameter IMEI : bit (10) > + -- NAS parameter is IMEI +! < Message escape : { 11 bit(1) } bit(10) = < no string > > } -- Reserved +| 1 (0)*14 } -- ANSI-41 +! < Message escape : 1 bit(15) = < no string > > }; -- Reserved + +``` + +**Table 9.3.41.2: Intra Domain NAS Node Selector information element details****Routing parameter TMSI-PTMSI (10 bit field)** + +This field is the bitstring of bit(14) through bit(23) of the TMSI or PTMSI where bit(14) is the least significant. + +**Routing parameter IMSI** (10 bit field) + +This field is the binary representation of $[(\text{IMSI div } 10) \bmod 1000]$ . Range 0 to 999. + +**Routing parameter IMEI** (10 bit field) + +This field is the binary representation of $[(\text{IMEI div } 10) \bmod 1000]$ . Range 0 to 999. + +### 9.3.42 Mobile Allocation + +This IE specifies the RF channels used in the mobile hopping sequence. + +**Table 9.3.42.1: Mobile Allocation information elements** + +``` +< Mobile Allocation IE > ::= + < Mobile Allocation Length : bit(8) > + < Mobile Allocation Value : octet (val(Mobile Allocation Length)) > ; +``` + +**Table 9.3.42.2: Mobile Allocation information element details** + +**Mobile Allocation Length** (8 bit field) + +The Mobile Allocation Length is coded as the length part of the *Mobile Allocation* IE specified in 3GPP TS 44.018. + +**Mobile Allocation Value** (octet string) + +The Mobile Allocation Value is coded as the value part of the *Mobile Allocation* IE specified in 3GPP TS 44.018. + +### 9.3.43 Mobile Time Difference + +This IE encodes a time related to the synchronization difference between the time bases of two base stations. + +**Table 9.3.43.1: Mobile Time Difference information elements** + +``` +< Mobile Allocation IE > ::= + < Mobile Time Difference Length : bit (8) > + < Mobile Time Difference Value : octet (val(Mobile Time Difference Length)) > ; +``` + +**Table 9.3.43.2: Mobile Time Difference information element details** + +**Mobile Time Difference Length** (8 bit field) + +The Mobile Time Difference Length is coded as the length part of the *Mobile Time Difference* IE specified in 3GPP TS 44.018. + +**Mobile Time Difference Value** (octet string) + +The Mobile Time Difference Value is coded as the value part of the *Mobile Time Difference* IE specified in 3GPP TS 44.018. + +### 9.3.44 MS GERAN A/Gb mode Radio Access Capability + +This Information Element contains the MS GERAN A/Gb mode radio access capability that is structured and coded according to the specification used for the corresponding system type. + +This IE contains the Mobile station classmark 2 and 3 of the MS. + +**Table 9.3.44.1: MS GERAN A/Gb mode Radio Access Capability information elements** + +``` +< MS GERAN A/Gb mode Radio Access Capability IE > ::= +{ + < Mobile Station Classmark 2 length : bit(3) > + < Mobile Station Classmark 2: octet(val (Mobile Station Classmark 2 length)) > } +{ + < Mobile Station Classmark 3 length : bit(5) > + < Mobile Station Classmark 3: octet (val (Mobile Station Classmark 3 length)) > } ; +``` + +**Table 9.3.44.2: MS GERAN A/Gb mode Radio Access Capability information element details****Mobile Station Classmark 2 length** (3 bit field) + +This field is the binary representation of the length of the *Mobile Station Classmark 2* IE in octets excluding the bits used for this length field. Range 0 to 7 octets + +**Mobile Station Classmark 2** + +This IE is defined in 3GPP TS 24.008 + +**Mobile Station Classmark 3 length** (5 bit field) + +This field is the binary representation of the length of the *Mobile Station Classmark 3* IE in octets excluding the bits used for this length field. Range 0 to 31 octets + +**Mobile Station Classmark 3** + +This IE is defined in 3GPP TS 24.008 + +## 9.3.45 MS GERAN Iu mode Radio Access Capability + +This Information Element contains the MS GERAN Iu mode radio access capability that is structured and coded according to the specification used for the corresponding system type. + +**Table 9.3.45.1: MS GERAN Iu mode Radio Access Capability information elements** + +``` + ::= +{ + < MS GERAN Iu mode Radio Access Capability length : bit (10)> + < MS RF Capability GSM : < MS RF Capability GSM IE > > + < MS GERAN Iu mode RLC Capability : < MS GERAN Iu Mode RLC Capability IE > > + < PDCP Capability : < PDCP Capability IE > > + < MS Multi-Mode and Multi-RAT Capability : < MS Multi-Mode and Multi-RAT Capability IE > > + < Security Capability : < Security Capability IE > > + < MS Positioning Capability : < MS Positioning Capability IE > > + < MS Measurement Capability : < MS Measurement Capability IE > > + < FLO Iu Capability : bit > -- Release 6 + < spare bit >** ; -- Extension information may be truncated between released versions of the protocol + -- The receiver shall assume the value zero for any truncated bit +}; +``` + +**Table 9.3.45.2: MS GERAN Iu mode Radio Access Capability information element details****MS GERAN Iu mode Radio Access Capability length** (10 bit field) + +This field is the binary representation of the length of the *MS GERAN Iu Mode Radio Access Capability* IE in bits excluding the bits used for this length field. Range: 0 to 1023. + +**MS RF Capability GSM** + +This IE is defined in sub-clause 9.3.47. + +**MS GERAN Iu mode RLC Capability** + +This IE is defined in sub-clause 9.3.46. + +**PDCP Capability** + +This IE is defined in sub-clause 9.3.59. + +| | +|---------------------------------------------------------------------------------------------------------------------------| +| MS Multi-Mode and Multi-RAT Capability
This IE is defined in sub-clause 9.3.48. | +| Security Capability
This IE is defined in sub-clause 9.3.100. | +| MS Positioning Capability
This IE is defined in sub-clause 9.3.50. | +| MS Measurement Capability
This IE is defined in sub-clause 9.3.49. | +| FLO Iu Capability (1 bit field)
Bit
0 FLO in GERAN Iu mode not supported
1 FLO in GERAN Iu mode supported | + +### 9.3.46 MS GERAN Iu mode RLC Capability + +The *MS GERAN Iu mode RLC capability* IE describes the capabilities of the RLC layer of the MS in GERAN Iu mode. + +**Table 9.3.46.1: MS GERAN Iu mode RLC Capability information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< MS GERAN Iu mode RLC Capability IE > ::= {   < MS GERAN Iu mode RLC Capability Length : bit (4)>   < Maximum number of RLC-AM entities : bit (3) >   < Maximum number of RLC-UM entities : bit (3) >   < Maximum number of RLC-T entities : bit (3) >   < spare bit >**; -- Extension information may be truncated between released versions of the protocol                     -- The receiver shall assume the value zero for any truncated bit };
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.46.2: MS GERAN Iu mode RLC Capability information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MS GERAN Iu mode RLC Capability Length (4 bit field)
This field is the binary representation of the length of the MS GERAN Iu Mode RLC Capability IE in bits excluding the bits used for this length field. Range: 0 to 15. | +| Maximum number of RLC-AM entities (3 bits field)
This field defines the number of RLC entities operating in acknowledge mode in the MS.
bit
3 2 1
0 0 0 3 RLC-AM entities
0 0 1 4 RLC-AM entities
0 1 0 5 RLC-AM entities
0 1 1 6 RLC-AM entities
1 0 0 8 RLC-AM entities
All other values are reserved. | + +**Maximum number of RLC-UM entities (3 bits field)** + +This field defines the number of RLC entities operating in unacknowledge mode in the MS. + +bit + +3 2 1 + +0 0 0 3 RLC-UM entities + +0 0 1 4 RLC-UM entities + +0 1 0 5 RLC-UM entities + +0 1 1 6 RLC-UM entities + +1 0 0 8 RLC-UM entities + +All other values are reserved. + +**Maximum number of RLC-T entities (2 bits field)** + +This field defines the number of RLC entities operating in transparent mode in the MS. + +bit + +3 2 1 + +0 0 0 3 RLC-T entity + +0 0 1 4 RLC-T entities + +0 1 0 5 RLC-T entities + +0 1 1 6 RLC-T entities + +1 0 0 8 RLC-T entities + +All other values are reserved. + +## 9.3.47 MS RF Capability GSM + +The purpose of the *MS RF Capability GSM* information element is to provide the radio part of the network with information concerning radio aspects of the mobile station. The contents might affect the manner in which the network handles the operation of the mobile station. + +The *MS RF Capability GSM* information element is coded as shown in table 9.3.47.1. + +For the indication of the Access Technology Types the following conditions shall apply: + +- Among the three Access Type Technologies GSM 900-P, GSM 900-E and GSM 900-R only one shall be present. +- Due to shared radio frequency channel numbers between GSM 1800 and GSM 1900, the mobile station should provide the relevant radio access capability for either GSM 1800 band OR GSM 1900 band, not both. +- The MS shall indicate its supported Access Technology Types. + +For error handling the following shall apply: + +- If a received Access Technology Type is unknown to the receiver, it shall ignore all the corresponding fields. +- If within a known Access Technology Type a receiver recognizes an unknown field it shall ignore it. +- For more details about error handling of MS radio access capability see 3GPP TS 48.018. + +Table 9.3.47.1: MS RF Capability GSM information elements + +``` + +< MS RF Capability GSM IE > ::= +{ + < MS RF Capability GSM Length : bit (8) > + < RF Capability Group : < RF Capability Group struct > > + { 1 < Additional RF Capability Group : < RF Capability Group struct > > } ** 0 +}; + +< RF Capability Group struct > ::= +-- Access Technology using common capabilities +< Access Technology Type : bit (4) > +{ 1 < Additional Access Technology Type : bit (4) > } ** 0 +< Common Access Capabilities : < Access Capabilities struct > > +-- Access Technology using individual capabilities +{ 1 < Additional Access Technology : < Additional Access Technology struct > > } ** 0 ; + +< Access Capabilities struct > ::= +< Access Capabilities length : bit (6) > +< GMSK Power Capability : bit (3) > +{ 0 | 1 < 8PSK Power Capability : bit (2) > } +< Pseudo Synchronisation : bit (1) > +< Multislot capability : < Multislot capability struct > > +< spare bit >**; -- Extension information may be truncated between released versions of the protocol +-- The receiver shall assume the value zero for any truncated bit + +< Additional Access Technology struct > ::= +< Additional Access Technology length : bit (6) > +< Access Technology Type : bit (4) > +< GMSK Power Class : bit (3) > +< 8PSK Power Class : bit (2) > +< spare bit >**; -- Extension information may be truncated between released versions of the protocol +-- The receiver shall assume the value zero for any truncated bit + +< Multislot Capability struct > ::= + +{ 0 < Combined GMSK and 8-PSK Multislot Class : bit (6) > +| 1 + < GMSK Multislot Class : bit (6) > +{ 0 | 1 < 8-PSK Multislot Class : bit (6) > } }; + +``` + +**Table 9.3.47.2: *MS RF Capability GSM* information element details** + +**MS RF Capability GSM Length (8 bit field)** + +This field is the binary representation of the length of the MS RF Capability GSM IE in bits excluding the bits used for this length field. + +**Access Technology Type (4 bit field)** + +This field indicates the access technology type to be associated with the following access capabilities. + +bit + +4 3 2 1 + +0 0 0 0 GSM P + +0 0 0 1 GSM E *--note that GSM E covers GSM P* + +0 0 1 0 GSM R *--note that GSM R covers GSM E and GSM P* + +0 0 1 1 GSM 1800 + +0 1 0 0 GSM 1900 + +0 1 0 1 GSM 450 + +0 1 1 0 GSM 480 + +0 1 1 1 GSM 850 + +1 0 0 0 GSM 750 + +1 0 0 1 GSM 710 + +1 0 1 0 T-GSM 810 + +All other values are treated as unknown by the receiver. + +**Common Access Capabilities** + +This structure contains the access capabilities for the indicated access technology type and - if present - for the access technologies indicated by the optional List of additional access technologies. + +**Access Capabilities length (6 bit field)** + +This field is the binary representation of the length of the Access Capabilities struct in bits excluding the bits used for this length field. Range: 0 to 63. + +**GMSK Power Capability, GMSK Power Class (3 bit field)** + +This field contains the binary coding of the power class used for GMSK associated with the indicated Access Technology Type (see 3GPP TS 45.005). + +**8PSK Power Capability (2 bit field)** + +If 8-PSK modulation is supported for uplink, this field indicates the radio capability for 8-PSK modulation. The following coding is used (see 3GPP TS 45.005): + +bit + +2 1 + +0 0 Reserved + +0 1 Power class E1 + +1 0 Power class E2 + +1 1 Power class E3 + +**8PSK Power Class (2 bit field)** + +This field indicates the radio capability for 8-PSK modulation. The following coding is used (see 3GPP TS 45.005): + +bit + +2 1 + +0 0 8-PSK modulation not supported for uplink + +0 1 Power class E1 + +1 0 Power class E2 + +1 1 Power class E3 + +**Pseudo Synchronisation (1 bit field)** + +This field indicates the Pseudo Synchronisation (Handover) capability. + +0 Pseudo Synchronisation capability not present + +1 Pseudo Synchronisation capability present + +**RF Capability Group** + +This structure contains the Common access capabilities for the indicated access technology type. These access capabilities may be extended by an optional List of additional access technologies. + +**Additional Access Technologies** + +This structure contains the GMSK Power Class and 8PSK Power Class for additional access technologies. All other capabilities for this indicated access technologies are the same as the capabilities as indicated by the last previously included Common access capabilities. + +**Additional Access Technology length** (6 bit field) + +This field is the binary representation of the length of the Additional Access Technology struct in bits excluding the bits used for this length field. Range: 0 to 63. + +**Multislot Capability** + +This structure contains the multislot capability for GMSK and 8-PSK modulations. The multislot class capability for GMSK and 8-PSK modulations can be combined or it can be defined separately for the modulations. + +**Combined GMSK and 8-PSK Multislot Class** (6 bit field) + +This field indicates common multislot class for both GMSK and 8-PSK modulations. The field is coded as the binary representation of the multislot class defined in 3GPP TS 45.002. + +**GMSK Multislot Class** (6 bit field) + +This field indicates multislot class for GMSK modulation. The field is coded as the binary representation of the multislot class defined in 3GPP TS 45.002. + +**8-PSK Multislot Class** (6 bit field) + +This field indicates multislot class for 8-PSK modulation. The field is coded as the binary representation of the multislot class defined in 3GPP TS 45.002. + +### 9.3.48 MS Multi-Mode and Multi-RAT Capability + +The *MS Multi-Mode and Multi-RAT Capability* IE describes the RLC multi-mode and multi-RAT capabilities of the MS. + +**Table 9.3.48.1: *MS Multi-Mode and Multi-RAT Capability* information elements** + +``` +< MS Multi-Mode and Multi-RAT Capability IE > ::= + < Support of GERAN A/Gb : bit (1) > + < Support of Multi-Carrier : bit (1) > + < Support of UMTS FDD : bit (1) > + < Support of UMTS 1.28 Mcps TDD : bit (1) > + < Support of UMTS 3.84 Mcps TDD : bit (1) > + < Support of CDMA2000 : bit (1) > + < spare bit > *10; +``` + +**Table 9.3.48.2: *MS Multi-Mode and Multi-RAT Capability* information element details** + +**Support of GERAN A/Gb** (1 bit field)**Support of Multi-Carrier** (1 bit field)**Support of UMTS FDD** (1 bit field)**Support of UMTS FDD** (1 bit field)**Support of UMTS 1.28 Mcps TDD** (1 bit field)**Support of UMTS 3.84 Mcps TDD** (1 bit field)**Support of CDMA2000** (1 bit field) + +These fields indicates the support of the associated multi-mode/multi-RAT capability. +bit + +1 + +0 not supported + +1 supported + +### 9.3.49 MS Measurement Capability + +The *MS Measurement Capability* IE describes the measurement capability and SMS value of the MS. + +**Table 9.3.49.1: MS Measurement Capability information elements** + +``` +< MS Measurement Capability IE > ::= + { + < MS Measurement Capability Length : bit (4)> + < Extended Measurement Capability : bit (1) > + < SMS Value : bit (4) > + < SM Value : bit (4) > + < spare bit >**; -- Extension information may be truncated between released versions of the protocol + -- The receiver shall assume the value zero for any truncated bit + }; +``` + +**Table 9.3.49.2: MS Measurement Capability information element details** + +| | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|--|---------|--|---------|----------------------------------|---------|----------------------------------|---------|----------------------------------|-------|--|---------|------------------------------------| +|

MS Measurement Capability Length (4 bit field)

This field is the binary representation of the length of the MS Measurement Capability IE in bits excluding the bits used for this length field. Range: 0 to 15.

| | | | | | | | | | | | | | | +|

Extended Measurement Capability (1 bit field)

These field indicates the support of Extended Measurement.

bit
0 Extended Measurement is not supported
1 Extended Measurement is supported

| | | | | | | | | | | | | | | +|

SMS Value (4 bit field)

The SMS Value field indicates the time needed for the mobile station to switch from one radio channel to another, perform a neighbour cell power measurement, and the switch from that radio channel to another radio channel.

bits
4 3 2 1
0 0 0 0 1/4 timeslot (~144 microseconds)
0 0 0 1 2/4 timeslot (~288 microseconds)
0 0 1 0 3/4 timeslot (~433 microseconds)
. . .
1 1 1 1 16/4 timeslot (~2307 microseconds)
| bits | | 4 3 2 1 | | 0 0 0 0 | 1/4 timeslot (~144 microseconds) | 0 0 0 1 | 2/4 timeslot (~288 microseconds) | 0 0 1 0 | 3/4 timeslot (~433 microseconds) | . . . | | 1 1 1 1 | 16/4 timeslot (~2307 microseconds) | +| bits | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | +| 0 0 0 0 | 1/4 timeslot (~144 microseconds) | | | | | | | | | | | | | | +| 0 0 0 1 | 2/4 timeslot (~288 microseconds) | | | | | | | | | | | | | | +| 0 0 1 0 | 3/4 timeslot (~433 microseconds) | | | | | | | | | | | | | | +| . . . | | | | | | | | | | | | | | | +| 1 1 1 1 | 16/4 timeslot (~2307 microseconds) | | | | | | | | | | | | | | +|

SM Value (4 bit field)

The SM Value field indicates the time needed for the mobile station to switch from one radio channel to another and perform a neighbour cell power measurement.

bits
4 3 2 1
0 0 0 0 1/4 timeslot (~144 microseconds)
0 0 0 1 2/4 timeslot (~288 microseconds)
0 0 1 0 3/4 timeslot (~433 microseconds)
. . .
1 1 1 1 16/4 timeslot (~2307 microseconds)
| bits | | 4 3 2 1 | | 0 0 0 0 | 1/4 timeslot (~144 microseconds) | 0 0 0 1 | 2/4 timeslot (~288 microseconds) | 0 0 1 0 | 3/4 timeslot (~433 microseconds) | . . . | | 1 1 1 1 | 16/4 timeslot (~2307 microseconds) | +| bits | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | +| 0 0 0 0 | 1/4 timeslot (~144 microseconds) | | | | | | | | | | | | | | +| 0 0 0 1 | 2/4 timeslot (~288 microseconds) | | | | | | | | | | | | | | +| 0 0 1 0 | 3/4 timeslot (~433 microseconds) | | | | | | | | | | | | | | +| . . . | | | | | | | | | | | | | | | +| 1 1 1 1 | 16/4 timeslot (~2307 microseconds) | | | | | | | | | | | | | | + +### 9.3.50 MS Positioning Capability + +The *MS Positioning Capability* IE describes the supported positioning methods in GERAN *Iu mode*. + +**Table 9.3.50.1: *MS Positioning Capability* information elements** + +``` + +< MS Positioning Capability IE > ::= + { + < MS Positioning Capability Length : bit (4)> + < OTD-A support : bit (1) > + < OTD-B support : bit (1) > + < GPS-A support : bit (1) > + < GPS-B support : bit (1) > + < GPS-C support : bit (1) > + < RRLP Positioning Indication support : bit (1) > + < spare bit >**; -- Extension information may be truncated between released versions of the protocol + -- The receiver shall assume the value zero for any truncated bit + }; + +``` + +**Table 9.3.50.2: *MS Positioning Capability* information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

MS Positioning Capability Length (4 bit field)
This field is the binary representation of the length of the MS Positioning Capability IE in bits excluding the bits used for this length field. Range: 0 to 15.

| +|

OTD-A support (1 bit field)
MS assisted E-OTD.
OTD-B support (1 bit field)
MS based E-OTD.
GPS-A support (1 bit field)
MS assisted GPS.
GPS-B support (1 bit field)
MS based GPS.
GPS-C support (1 bit field)
Conventional GPS.
Each of these fields indicates the support of the associated positioning method.

bit
1
0 not supported
1 supported

| +|

RRLP Positioning Indication support (1 bit field)
This field indicates whether the MS supports transfer of its positioning capabilities using RRLP.

bit
1
0 not supported
1 supported

| + +### 9.3.51 MS Timers and Constants in RRC-Connected mode + +This IE specifies timer values and constant values used by the mobile station in RRC-Connected mode. + +**Table 9.3.51.1: *MS Timers And Constants in RRC-Connected Mode* information elements** + +``` + +< MS Timers and Constants in RRC-Connected mode IE > ::= + < MS Timers and Constants Length : bit (4) > + { 0 | 1 < T305 : GRA AND CELL UPDATE TIMER IE > } + { 0 | 1 < T314 : bit (3) > } + { 0 | 1 < T315 : bit (3) > } + < spare bits >** ; + +``` + +**Table 9.3.51.2: MS Timers And Constants in RRC-Connected Mode information element details** + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| MS Timers and Constants Length (4 bit field)
This field is the binary representation of the length of the MS Timers and Constants in RRC-Connected Mode IE in bits excluding the 4 bits used for this length field. | | +| T305 (3 bit field)
This field specifies the starting value of timer T305. This IE defined in 3GPP TS 44.160, PACKET SYSTEM INFORMATION 16 message. | | +| T315 (3 bit field)
This field specifies the starting value of timer T315. The following table specifies the coding :
bit
3 2 1
0 0 0 0s
0 0 1 10s
0 1 0 30s
0 1 1 60s
1 0 0 180s --default value
1 0 1 600s
1 1 0 1200s
1 1 1 1800s
| bit
3 2 1
0 0 0 0s
0 0 1 10s
0 1 0 30s
0 1 1 60s
1 0 0 180s --default value
1 0 1 600s
1 1 0 1200s
1 1 1 1800s | +| bit
3 2 1
0 0 0 0s
0 0 1 10s
0 1 0 30s
0 1 1 60s
1 0 0 180s --default value
1 0 1 600s
1 1 0 1200s
1 1 1 1800s | | + +## 9.3.52 MultiRate Configuration + +This IE specifies all parameters for a multirate speechcodec. + +**Table 9.3.52.1: MultiRate Configuration information elements** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| < MultiRate Configuration IE > ::=
< MultiRate Configuration Length : bit(8) >
< MultiRate Configuration Value : octet (val(MultiRate Configuration Length)) >;
| < MultiRate Configuration Length : bit(8) >
< MultiRate Configuration Value : octet (val(MultiRate Configuration Length)) >; | +| < MultiRate Configuration Length : bit(8) >
< MultiRate Configuration Value : octet (val(MultiRate Configuration Length)) >; | | + +**Table 9.3.52.2: MultiRate Configuration information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MultiRate Configuration Length (8 bit field)
The MultiRate Configuration Length is coded as the length part of the MultiRate Configuration IE specified in 3GPP TS 44.018 § 10.5.2.21aa. | +| MultiRate Configuration Value (octet string)
The MultiRate Configuration Value is coded as the value part of the MultiRate Configuration IE specified in 3GPP TS 44.018 § 10.5.2.21aa. | + +## 9.3.53 Multislot Allocation + +This IE specifies the downlink and uplink timeslots used in a multislot configuration. It also groups the timeslots into channel sets. + +**Table 9.3.53.1: Multislot Allocation information elements** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| < Multislot Allocation IE > ::=
< Multislot Allocation Length : bit(8) >
< Multislot Allocation Value : octet (val(Multislot Allocation Length)) >;
| < Multislot Allocation Length : bit(8) >
< Multislot Allocation Value : octet (val(Multislot Allocation Length)) >; | +| < Multislot Allocation Length : bit(8) >
< Multislot Allocation Value : octet (val(Multislot Allocation Length)) >; | | + +**Table 9.3.53.2: *Multislot Allocation* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Multislot Allocation Length (8 bit field)
The Multislot Allocation Length is coded as the length part of the Multislot Allocation IE specified in 3GPP TS 44.018. | +| Multislot Allocation Value (octet string)
The Multislot Allocation Value is coded as the value part of the Multislot Allocation IE specified in 3GPP TS 44.018. | + +## 9.3.54 NAS Message + +The *NAS Message* IE contains a non-access stratum message to be transferred transparently through GERAN. + +**Table 9.3.54.1: *NAS Message* information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------| +| < NAS Message IE > ::=
< Length of NAS Message : bit (12) >
< NAS Message : octet (1+val(Length of NAS Message) ) > ; | +|-------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.54.2: *NAS Message* information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Length of NAS Message (12 bit field)
This field is used to calculate the length of the NAS Message IE excluding the bits used for this length field. Range : 0 to 4095. | +| NAS Message (variable length octet string)
The first octet contains octet 1 of the NAS message, the second octet contains octet 2 of the NAS message and so on. See 3GPP TS 24.007. | + +## 9.3.55 NAS Synchronization Info + +The *NAS Synchronization Info* IE is a container for non-access stratum information to be transferred transparently through GERAN. + +**Table 9.3.55.1: *NAS Synchronization Info* information elements** + +| | +|------------------------------------------------------------------------------------------| +| < NAS Synchronization Info IE > ::=
< NAS Synchronization Info : bit ( 4 ) > ; | +|------------------------------------------------------------------------------------------| + +**Table 9.3.55.2: *NAS Synchronization Info* information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NAS Synchronization Info (4 bit field)
This field contains NAS information to be transferred transparently through GERAN. The bits are numbered b1-b4, where b1 is the least significant bit. | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 9.3.56 NAS System Information GSM-MAP + +This IE contains system information that belongs to the non-access stratum for a GSM-MAP type of PLMN. This information is transparent to RRC. It may contain either information specific to one CN domain (CS or PS) or information common for both CN domains. + +**Table 9.3.56.1: *NAS System Information GSM-MAP* information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < NAS System Information GSM-MAP IE > ::=
< Length of NAS System Information GSM-MAP : bit (3) >
< NAS System Information GSM-MAP : octet (1+val(Length of NAS System Information GSM-MAP)) > ; | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.56.2: NAS System Information GSM-MAP information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Length of NAS System Information GSM-MAP (3 bit field)
This field is used to calculate the length in octets of the NAS System Information GSM-MAP IE excluding the bits used for this length field. Range : 0...7. | +| NAS System Information GSM_MAP (octet string)
The first octet contains octet 1 of the NAS System Information element, the second octet contains octet 2 of the NAS system information element and so on. See 3GPP TS 24.008. | + +### 9.3.57 Paging Cause + +The *Paging Cause* IE indicates the cause of the paging request. + +**Table 9.3.57.1: Paging Cause information elements** + +| | +|-------------------------------------| +| < Paging Cause IE > ::= | +| < Paging Cause : bit (3) > ; | + +**Table 9.3.57.2: Paging Cause information element details** + +| | +|--------------------------------------------| +| Paging Cause (3 bit field) | +| bit | +| 3 2 1 | +| 0 0 0 Terminating Conversational Call | +| 0 0 1 Terminating Streaming Call | +| 0 1 0 Terminating Interactive Call | +| 0 1 1 Terminating Background Call | +| 1 0 0 Terminating High Priority Signalling | +| 1 0 1 Terminating Low Priority Signalling | +| 1 1 0 Terminating – cause unknown | +| 1 1 1 Reserved | + +### 9.3.58 Paging Record Type Identifier + +The *Paging Record Type Identifier* IE indicates the identifier used in the Core Network Paging. + +**Table 9.3.58.1: Paging Record Type Identifier information elements** + +| | +|------------------------------------------------------| +| < Paging Record Type Identifier IE > ::= | +| < Paging Record Type Identifier : bit (3) > ; | + +**Table 9.3.58.2: Paging Record Type Identifier information element details** + +| | +|----------------------------------------------------| +| Paging Record Type Identifier (3 bit field) | +| bit | +| 3 2 1 | +| 0 0 0 IMSI (GSM-MAP) | +| 0 0 1 TMSI/PTMSI (GSM/MAP) | +| 0 1 0 IMSI (DS-41) | +| 0 1 1 TMSI (DS-41) | +| 1 x x reserved | + +## 9.3.59 PDCP Capability + +Indicates which algorithms and which value range of their parameters are supported by the MS. + +The *PDCP Capability* IE indicates the algorithms and the value range of parameters supported by the MS PDCP. + +**Table 9.3.59.1: *PDCP Capability* information elements** + +``` +< PDCP Capability IE > ::= +{ + < PDCP Capability length : bit (8)> + < Support for lossless serving BSC relocation : bit (1) > + { + < Support for RFC2507 : 0 > + | < Support for RFC2507 : 1 > + < Max HC context space : bit (4) > } + { + < Support for RFC3095 : 0 > + | < Support for RFC3095 : 1 > + { 0 | 1 < Maximum number of ROHC context sessions : bit (4) > } + { 0 | 1 < Reverse decompression depth : bit (16) > } + { < Support for RFC 3095 context relocation: 0 > + | < Support for RFC 3095 context relocation: 1 > } } + < spare bit >**; -- Extension information may be truncated between released versions of the protocol + -- The receiver shall assume the value zero for any truncated bit +}; +``` + +**Table 9.3.59.2: *PDCP Capability* information element details** + +| | | | | | | | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|--|---------|-----------|---------|------------|---------|------------|---------|------------|---------|------------|---------|-------------|---------|-------------|---------|-------------|---------|--------------| +|

PDCP Capability Length (8 bit field)
This field is the binary representation of the length of the PDCP Capability IE in bits excluding the 8 bits used for this length field. Range: 0 to 255.

| | | | | | | | | | | | | | | | | | | | | +|

Support for lossless Serving BSC relocation (1 bit field)

bit
1
0 Lossless Serving BSC relocation not supported
1 Lossless Serving BSC relocation supported

| | | | | | | | | | | | | | | | | | | | | +|

Support for RFC2507 (1 bit field)
Support for RFC3095 (1 bit field)

bit
1
0 not supported
1 supported

| | | | | | | | | | | | | | | | | | | | | +|

Max HC context space (4 bit field)
This field indicates the maximum header compression context space supported by the MS, when RFC2507 is supported and is encoded as follows :

bit
4 3 2 1
0 0 0 0 512 bytes
0 0 0 1 1024 bytes
0 0 1 0 2048 bytes
0 0 1 1 4096 bytes
0 1 0 0 8192 bytes
0 1 0 1 16384 bytes
0 1 1 0 32768 bytes
0 1 1 1 65536 bytes
1 0 0 0 131072 bytes

All other values are reserved

| bit
4 3 2 1 | | 0 0 0 0 | 512 bytes | 0 0 0 1 | 1024 bytes | 0 0 1 0 | 2048 bytes | 0 0 1 1 | 4096 bytes | 0 1 0 0 | 8192 bytes | 0 1 0 1 | 16384 bytes | 0 1 1 0 | 32768 bytes | 0 1 1 1 | 65536 bytes | 1 0 0 0 | 131072 bytes | +| bit
4 3 2 1 | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 0 | 512 bytes | | | | | | | | | | | | | | | | | | | | +| 0 0 0 1 | 1024 bytes | | | | | | | | | | | | | | | | | | | | +| 0 0 1 0 | 2048 bytes | | | | | | | | | | | | | | | | | | | | +| 0 0 1 1 | 4096 bytes | | | | | | | | | | | | | | | | | | | | +| 0 1 0 0 | 8192 bytes | | | | | | | | | | | | | | | | | | | | +| 0 1 0 1 | 16384 bytes | | | | | | | | | | | | | | | | | | | | +| 0 1 1 0 | 32768 bytes | | | | | | | | | | | | | | | | | | | | +| 0 1 1 1 | 65536 bytes | | | | | | | | | | | | | | | | | | | | +| 1 0 0 0 | 131072 bytes | | | | | | | | | | | | | | | | | | | | + +**Maximum number of ROHC context sessions (4 bit field)** + +This field indicates the maximum number of ROHC context sessions when RFC3095 is supported and is encoded as shown below. If this field is not present, the MS shall use the default value of 16 : + +| bit | | +|---------|----------------| +| 4 3 2 1 | | +| 0 0 0 0 | 2 sessions | +| 0 0 0 1 | 4 sessions | +| 0 0 1 0 | 8 sessions | +| 0 0 1 1 | 12 sessions | +| 0 1 0 0 | 16 sessions | +| 0 1 0 1 | 24 sessions | +| 0 1 1 0 | 32 sessions | +| 0 1 1 1 | 48 sessions | +| 1 0 0 0 | 64 sessions | +| 1 0 0 1 | 128 sessions | +| 1 0 1 0 | 256 sessions | +| 1 0 1 1 | 512 sessions | +| 1 1 0 0 | 1024 sessions | +| 1 1 0 1 | 16384 sessions | +| 1 1 1 0 | reserved | +| 1 1 1 1 | reserved | + +**Reverse decompression depth (16 bit field)** + +This field describes the reverse compression depth as an integer from 0 - 65535. If the IE is not present, the default value of 0 (reverse decompression is not supported) is used. + +**Support for RFC 3095 context relocation (1 bit field)** + +| bit | | +|-----|-------------------------------------------------------| +| 1 | | +| 0 | Support for RFC 3095 context relocation not supported | +| 1 | Support for RFC 3095 context relocation supported | + +## 9.3.60 PDCP Info + +The *PDCP Info* IE contains information about the PDCP protocol. + +Table 9.3.60.1: PDCP Info information elements + +``` + +< PDCP Info IE > ::= +{ + < PDCP mode : bit (1) > + { < Lossless Serving BSS relocation support : 0 > + | < Lossless Serving BSS relocation support : 1 > + < Max PDCP SN : bit (1) > } + < PDCP PDU header : bit (1) > + { 0 | 1 < Header compression information List : bit(3) > + < Header compression information struct : < Header compression information struct > > } *(1+val(Header +compression information List)) +}; + +< Header compression information struct > ::= +< Header Compression Information struct length : bit (14) > +{ 000 -- Header compression according to IETF standard RFC2507 + < F_MAX_PERIOD : bit (16) > + < F_MAX_TIME : bit (8) > + < MAX_HEADER : bit (16) > + < TCP_SPACE : bit (8) > + < NON_TCP_SPACE : bit (16) > + < EXPECT_REORDERING : bit (1) > + | 001 -- Header compression according to IETF standard RFC3095 + + < Profiles List : bit (4) > + < Profile instance : bit (2) > * (1 + val (Profiles List)) + { 0 | 1 < UPLINK: bit (1) > + < CID inclusion info : bit (1) > + { 0 | 1 < Max_CID : bit (14) > } + { 0 | 1 < MRRU : bit (16) > } + < Packet Sizes Allowed List : bit (4) > + < PACKET_SIZES_ALLOWED: bit (11) > * (1 + val (Packet Sizes Allowed List)) } + { 0 | 1 < DOWNLINK: bit (1) > + < CID inclusion info : bit (1) > + { 0 | 1 < Max_CID : bit (14) > } + } + { 0 | 1 < Reverse Decompression Depth : bit (16) > } + ! < Message escape : { 01 bit(1) | 1 bit (2) } bit** = < no string > > ; +} + +``` + +Table 9.3.60.2: PDCP Info information element details + +**PDCP mode** (1 bit field) + +bit + +1 + +0 non-transparent + +1 transparent + +**Lossless Serving BSS relocation support** (1 bit field) + +Lossless Serving BSC relocation is supported when both the RLC is in Acknowledged mode meaning when the IE "RLC mode" is "Acknowledged" bit + +1 + +0 Lossless Serving BSS relocation not supported + +1 Lossless Serving BSS relocation supported + +**Max PDCP SN** (1 bit field) + +This field indicates the maximum PDCP Sequence Number supported, when the lossless Serving BSC relocation is supported. + +bit + +1 + +0 255 + +1 65535 + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCP PDU header (1 bit field)
bit
1
0 not present
1 present | +| Header compression information List (3 bit field)
This field is the binary representaion of the number of header compression information.

Range: 0 to maxPDCPAlgoType-1.
NOTE: Link with the PDCP instances to be clarified in the procedure. | +| Header compression information struct
The Header compression information struct is repeated up to maxPDCPAlgoType times. | +| Header Compression Information struct length (14 bit field)
This field is the binary representaion of the length of the Header Compression Information struct excluding the bits used for this length field.

Range: 0 to 4095. | +| F_MAX_PERIOD (16 bit field)
This field is a binary representation of the maximum number of compressed non-TCP headers that may be sent without sending a full header.

Range 1 to 65535. | +| F_MAX_TIME (8 bit field)
This field is a binary representation of the maximum time in seconds that a compressed headers may not be sent after sending last full header.

Range 1 to 255. | +| MAX_HEADER (16 bit field)
This field is a binary representation of the largest header size in octets that may be compressed.

Range 60 to 65535. | +| TCP_SPACE (8 bit field)
This field is a binary representation of the maximum CID value for TCP connections.

Range 3 to 255. | +| NON_TCP_SPACE (16 bit field)
This field is a binary representation of the maximum CID value for non-TCP connections.

Range 3 to 65535. | +| EXPECT_REORDERING (1 bit field)
bit
1
0 reordering not expected,
1 reordering expected | +| UPLINK (1 bit field)
bit
1
0 does not indicate the necessary information elements for UL
1 indicates the necessary information elements for UL | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

DOWNLINK (1 bit field)
bit
1
0 does not indicate the necessary information elements for DL
1 indicates the necessary information elements for DL

| +|

CID inclusion info
This field configures which method shall be used to carry RFC3095 CID values :

bit
1
0 PDCP Header
1 RFC3095 packet format

Max_CID
This field describes the highest context ID number to be used by the MS compressor. If this field is not present then the default value of 15 is used.
This field is encoded as a binary number.

Range 0 to 16383. A value of 0 shall be counted as reserved.

| +|

Profiles List (4 bit field)
This field is a binary representation of the number of ROHC profiles supported by the GERAN decompressor.

Range 0 to maxROHC-Profiles-1.

| +|

Profile instance
This field is a binary representation of the supported profile types.

Range 1 to 3. Any other value received shall be treated as reserved.

| +|

MRRU
This field describes the Maximum Reconstructed Reception Unit. When RLC is configured in non-transparent mode, this field is set to the 0 and the segmentation function of the RFC 3095 shall not be used by the MS.
The filed is encoded as a binary number.

Range 0 to 65535

| +|

Packet Sizes Allowed List (4 bit field)
This field is the binary representation of the list of packet sizes that are allowed to be produced by RFC 3095.

| +|

PACKET_SIZES_ALLOWED (11 bit field)
This field is the binary representation of the packets sizes in octets as defined by MS compressor.

Range 2 to 1500. Any other received values shall be treated as reserved.

| +|

Reverse decompression depth (16 bit field)
This field describes the reverse compression depth as an integer from 0 to 65535. Also it determines whether reverse decompression should be used or not and the maximum number of packets that can be reverse decompressed by the MS decompressor. If the IE is not present, the default value of 0 (reverse decompression shall not be used) is used.

Range 0 to 65535

| + +### 9.3.61 PDCP SN Info + +The *PDCP SN Info* IE indicates the PDCP sequence number that the sender of the message is expecting to be received next. + +**Table 9.3.61.1: PDCP SN Info information elements** + +| | +|----------------------------------------------------------------------------------------| +|

< PDCP SN Info IE > ::=
  < PDCP SN Info : bit (16) > ;

| +|----------------------------------------------------------------------------------------| + +**Table 9.3.61.2: PDCP SN Info information element details****PDCP SN Info** (16 bit field) + +The *PDCP SN Info* field is encoded as a binary number. Range 0 to 65535. + +## 9.3.62 Physical Channel Configuration + +The *Physical Channel Configuration* IE describes the dedicated and the shared physical resources. + +**Table 9.3.62.1: Physical Channel Configuration information elements** + +``` +< Physical Channel Configuration IE > ::= +{ 00 -- no physical resource allocated +| 01 < DBPSCH : < DBPSCH Description IE > > +| 10 < SBPSCH : < SBPSCH Description IE > > +| +! < Message escape : { 11 } bit** = < no string > > } +-- Reserved for future use; +``` + +**Table 9.3.62.2: Physical Channel Configuration information element details****DBPSCH Description** + +This IE is defined in sub-clause 9.3.19. + +**SBPSCH Description** + +This IE is defined in sub-clause 9.3.99. + +## 9.3.63 PLMN Identity + +The *PLMN Identity* IE identifies a Public Land Mobile Network for a GSM-MAP type of PLMN. The PLMN identity digits are defined in 3GPP TS 23.003. + +**Table 9.3.63.1: PLMN Identity information elements** + +``` +< PLMN Identity IE > ::= +< MCC_digit_1 : bit (4) > +< MCC_digit_2 : bit (4) > +< MCC_digit_3 : bit (4) > +< MNC_digit_1 : bit (4) > +< MNC_digit_2 : bit (4) > +{ 0 | 1 < MNC_digit_3 : bit (4) > }; +``` + +**Table 9.3.63.2: PLMN Identity information element details****MCC\_digit\_1** (4 bit field)**MCC\_digit\_2** (4 bit field)**MCC\_digit\_3** (4 bit field) + +These fields are the binary representation of the MCC digit number X, where X goes from 1 to 3. Range: 0 to 9. + +**MNC\_digit\_1** (4 bit field)**MNC\_digit\_2** (4 bit field)**MNC\_digit\_3** (4 bit field) + +These fields are the binary representation of the MNC digit number X, where X goes from 1 to 2 or 3. Range: 0 to 9. The presence of a third MNC digit depends on the value of the MCC. + +### 9.3.64 Power Command + +The *Power Command* IE is to provide the power level to be used by the mobile station. + +**Table 9.3.64.1: *Power Command* information elements** + +| | +|--------------------------------------------------------------------------| +| < Power Command IE > ::=
< Power Command Value : octet (1) > ; | +|--------------------------------------------------------------------------| + +**Table 9.3.64.2: *Power Command* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Power Command Value (1 octet field)
The Power Command Value is coded as the value part of the Power Command IE defined in 3GPP TS 44.018. | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.65 Power Command and Access Type + +The *Power Command and Access Type* IE is to provide the power level to be used by the mobile station. + +**Table 9.3.65.1: *Power Command and Access Type* information elements** + +| | +|----------------------------------------------------------------------------------------------------------| +| < Power Command and Access Type IE > ::=
< Power Command and Access Type Value : octet (1) > ; | +|----------------------------------------------------------------------------------------------------------| + +**Table 9.3.65.2: *Power Command and Access Type* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Power Command and Access Type Value (1 octet field)
The Power Command and Access Type Value is coded as the value part of the Power Command and Access Type IE defined in 3GPP TS 44.018. | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +9.3.66 (void) + +9.3.67 (void) + +9.3.68 (void) + +### 9.3.69 Protocol Error Cause + +The *Protocol Error Cause* IE indicates the cause of the incomprehension of a message or information. + +**Table 9.3.69.1: *Protocol Error Cause* information elements** + +| | +|--------------------------------------------------------------------------------| +| < Protocol Error Cause IE > ::=
< Protocol Error Cause : bit (3) > ; | +|--------------------------------------------------------------------------------| + +**Table 9.3.69.2: Protocol Error Cause information element details** + +| | +|----------------------------------------------------| +| Protocol Error Cause (3 bit field) | +| bit | +| 3 2 1 | +| 0 0 0 CSN.1 violation or encoding error | +| 0 0 1 Message type non-existent or not implemented | +| 0 1 0 Message not compatible with receiver state | +| 0 1 1 Information element value not comprehended | +| 1 0 0 Message content part error | +| 1 0 1 Message extension not comprehended | +| All other values are reserved. | + +## 9.3.70 Protocol Error Indicator + +The *Protocol Error Indicator* IE indicates whether a message was transmitted due to a protocol error or not. + +**Table 9.3.70.1: Protocol Error Indicator information elements** + +| | +|-------------------------------------------------| +| < Protocol Error Indicator IE > ::= | +| < Protocol Error Indicator : bit (1) > ; | + +**Table 9.3.70.2: Protocol Error Indicator information element details** + +| | +|-----------------------------------------------| +| Protocol Error Indicator (1 bit field) | +| bit | +| 1 | +| 0 False - no protocol error occurred | +| 1 True - protocol error occurred | + +## 9.3.71 Protocol Error Information + +The *Protocol Error Information* IE contains diagnostic information returned by the receiver of a message that was not completely understood. + +**Table 9.3.71.1: Protocol Error Information information elements** + +| | +|-------------------------------------------------------------------| +| < Protocol Error Information IE > ::= | +| { 0 < Protocol Error Cause : < Protocol Error Cause IE > > | +| 1 } ; -- reserved | + +**Table 9.3.71.2: Protocol Error Information information element details** + +| | +|------------------------------------------| +| Protocol Error Cause | +| This IE is defined in sub-clause 9.3.69. | + +## 9.3.72 RAB Identity + +The *RAB Identity* IE uniquely identifies a radio access bearer within a CN domain. + +**Table 9.3.72.1: RAB Identity information elements** + +``` +< RAB Identity IE > ::= + { 0 < RAB_Identity_GSM-MAP : bit (8) > + | 1 < RAB_Identity_ANSI-41 : bit (8) > }; +``` + +**Table 9.3.72.2: RAB Identity information element details****RAB\_Identity\_GSM-MAP (8 bit field)** + +This field indicates the RAB identity with a GSM-MAP-type PLMN. See 3GPP TS 24.008 + +**RAB\_Identity\_ANSI-41 (8 bit field)** + +This field indicates the RAB identity with a ANSI-41-type PLMN. See 3GPP TS 24.008 + +## 9.3.73 RAB Info + +The *RAB Info* IE contains information used to uniquely identify a radio access bearer. + +**Table 9.3.73.1: RAB Info information elements** + +``` +< RAB Info IE > ::= + < RAB Identity > : < RAB Identity IE > > + < CN Domain Identity > : < CN Domain Identity IE > > + { 0 | 1 < NAS Synchronization Indicator > : < NAS Synchronization Info IE > > } + < Re-Establishment Timer > : < Re-Establishment Timer IE > > ; +``` + +**Table 9.3.73.2: RAB Info information element details****RAB Identity** + +This IE is defined in sub-clause 9.3.72. + +**CN Domain Identity** + +This IE is defined in sub-clause 9.3.15. + +**NAS Synchronization Indicator** + +The *NAS Synchronization Info* IE is defined in sub-clause 9.3.55. + +**Re-Establishment Timer** + +This IE is defined in sub-clause 9.3.88. + +## 9.3.74 RAB Info Post + +The *RAB Info Post* IE contains information used to uniquely identify a radio access bearer. + +**Table 9.3.74.1: RAB Info Post information elements** + +``` +< RAB Info Post IE > ::= + < RAB Identity > : < RAB Identity IE > > + < CN Domain Identity > : < CN Domain Identity IE > > + { 0 | 1 < NAS Synchronization Indicator > : < NAS Synchronization Info : bit (4) > > }; +``` + +**Table 9.3.74.2: RAB Info Post information element details****RAB Identity** + +This IE is defined in sub-clause 9.3.72. + +**CN Domain Identity** + +This field is defined in sub-clause 9.3.15. + +**NAS Synchronization Indicator** + +The *NAS Synchronization Info* field is defined in sub-clause 9.3.55. + +## 9.3.75 RAB Information for Setup + +The *RAB Information for Setup* IE indicates the radio access bearer(s) to setup. + +**Table 9.3.75.1: RAB Information for Setup information elements** + +``` +< RAB Information for Setup IE > ::= + < RAB Info : < RAB info IE > > + < RB Information to Setup List : bit (3) > + < RB Information to Setup : < RB Information to Setup IE > > *(1+val(RB Information to Setup List)) }; +``` + +**Table 9.3.75.2: RAB Information for Setup information element details** + +**RAB Info** + +This IE is defined in sub-clause 9.3.73. + +**RB Information to Setup List (3 bit field)** + +This field is the binary representation of the number of RB to setup in a RAB. Range : 0 to maxRBperRAB-1. + +**RB Information to Setup** + +This IE is defined in sub-clause 9.3.84. This IE can be repeated up to maxRBperRAB times within one RAB information for setup IE. + +## 9.3.76 RAB Information to Reconfigure + +The *RAB Information to Reconfigure* IE indicates the radio access bearer(s) to reconfigure. + +**Table 9.3.76.1: RAB Information to Reconfigure information elements** + +``` +< RAB Information to Reconfigure IE > ::= + < RAB Identity : < RAB Identity IE > > + < CN Domain Identity : < CN Domain Identity IE > > + < NAS Synchronization Indicator : < NAS synchronization Info : bit (4) > > ; +``` + +**Table 9.3.76.2: RAB Information to Reconfigure information element details** + +**RAB Identity** + +This IE is defined in sub-clause 9.3.72. + +**CN Domain Identity** + +This IE is defined in sub-clause 9.3.15. + +**NAS Synchronization Indicator** + +The *NAS Synchronization Info* IE is defined in sub-clause 9.3.55. + +## 9.3.77 RB Activation Time Info + +The *RB Activation Time Info* IE contains the time, in terms of RLC sequence numbers, when a certain configuration shall be activated, for a number of radio bearers. + +**Table 9.3.77.1: RB Activation Time Info information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< RB Activation Time Info IE > ::=   { 0   1 < Repeated Radio Bearer Activation Time list : bit (5) >     < Repeated Radio Bearer Activation Time : < Radio Bearer Activation Time struct > > } *(1+val(Repeated Radio     Bearer Activation Time list));
| +| 
< Repeated Radio Bearer Activation Time struct > ::=   {     < RB Identity : < RB Identity IE > >     { 0   1 { 00 < GPRS RLC Sequence Number : bit (7) >               01 < EGPRS RLC Sequence Number : bit (11) >               10 < DCCH TBF mode RLC Sequence Number : bit (4) >               11 < TCH TBF RLC Sequence Number : bit (8) > }   } };
| + +**Table 9.3.77.2: RB Activation Time Info information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Repeated radio bearer activation time list (5 bit field)
This field is the binary representation of the number of RBs. Range : 0 to maxRB-1.

| +|

Repeated radio bearer activation time struct
The Repeated radio bearer activation time struct is repeated up to maxRB times.

| +|

RB Identity
This IE is defined in sub-clause 9.3.80.

| +|

GPRS RLC Sequence Number (7 bit field)
This field indicates the RLC send state variable for GPRS MS with radio bearers mapped on RLC AM and UM. This field is encoded as a binary number. Range : 0 to 127.

| +|

EGPRS RLC Sequence Number (11 bit field)
This field indicates the RLC send state variable for EGPRS MS with radio bearers mapped on RLC AM and UM. This field is encoded as a binary number. Range : 0 to 2047.

| +|

DCCH TBF RLC Sequence Number (4 bit field)
This field indicates the RLC send state variable for DCCH TBF mode MS (see 3GPP TS 44.160) with radio bearers mapped on RLC AM and UM. This field is encoded as a binary number. Range : 0 to 15.

| +|

TCH TBF RLC Sequence Number (8 bit field)
This field indicates the RLC send state variable for TCH TBF mode MS (see 3GPP TS 44.160) with radio bearers mapped on RLC AM and UM. This field is encoded as a binary number. Range : 0 to 255.

| + +## 9.3.78 RB COUNT-C Information + +The *RB COUNT-C Information* IE indicates RB COUNT-C values for a radio bearer. + +**Table 9.3.78.1: RB COUNT-C Information information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< RB COUNT-C Information IE > ::=   < RB Identity : < RB Identity IE > >   < COUNT-C-Uplink : bit (32) >   < COUNT-C-Downlink : bit (32) >;
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.78.2: RB COUNT-C Information information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RB Identity
This IE is defined in sub-clause 9.3.80.

| +|

COUNT-C-Uplink (32 bit field)
This field is the binary representation of the amount of data sent in Uplink. See 3GPP TS 33.102.

| + +**COUNT-C-Downlink** (32 bit field) + +This field is the binary representation of the amount of data sent in Downlink. See 3GPP TS 33.102. + +### 9.3.79 RB COUNT-C MSB Information + +The *RB COUNT-C MSB Information* IE indicates the MSB of the COUNT-C values of the radio bearer. + +**Table 9.3.79.1: RB COUNT-C MSB Information information elements** + +``` +< RB COUNT-C MSB Information IE > ::= + < RB Identity : bit (5) > + < COUNT-C-MSB-Uplink : bit (25) > + < COUNT-C-MSB-Downlink : bit (25) >; +``` + +**Table 9.3.79.2: RB COUNT-C MSB Information information element details** + +**RB Identity** + +This IE is defined in sub-clause 9.3.80. + +**COUNT-C-MSB-Uplink** (25 bit field) + +This field indicates 25 MSBs from the COUNT-C-uplink associated to this RB. See 3GPP TS 33.102. + +**COUNT-C-MSB-Downlink** (25 bit field) + +This field indicates 25 MSBs from the COUNT-C-downlink associated to this RB. See 3GPP TS 33.102. + +### 9.3.80 RB Identity + +The *RB Identity* IE indicates the identification number for the radio bearer affected by a certain message. + +**Table 9.3.80.1: RB Identity information elements** + +``` +< RB Identity IE > ::= + < RB Identity : bit (5) >; +``` + +**Table 9.3.80.2: RB Identity information element details** + +**RB Identity** (5 bit field) + +The *RB Identity* field is encoded as a binary number. Range: 0 to 31. Values 0-4 shall only be used for signalling radio bearers. + +### 9.3.81 RB Information to Be Affected + +The *RB Information to Be Affected* IE indicates identity of the RB to be affected by the message. + +**Table 9.3.81.1: RB Information to Be Affected information elements** + +``` +< RB Information to Be Affected IE > ::= + < RB Identity : < RB Identity IE > >; +``` + +**Table 9.3.81.2: RB Information to Be Affected information element details** + +**RB Identity** (5 bit field) + +This field is defined in sub-clause 9.3.80. + +## 9.3.82 RB Information to Reconfigure + +The *RB Information to Reconfigure* IE indicates the radio bearer to reconfigure. + +**Table 9.3.82.1: *RB Information to Reconfigure* information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RB Information to Reconfigure IE > ::=   < RB Information to Reconfigure length : bit ( 11 ) >   < RB Identity : < RB Identity IE > >   { 0   1 < PDCP Info : < PDCP Info IE > > }   { 0   1 < PDCP SN Info : < PDCP SN Info > > }   { 0   1 < RLC Info : < RLC info IE > > }   { 0   1 < RB Stop/Continue : bit (1) > }   { 0   1 < RB Mapping Info : < RB Mapping Info IE > > } -- Release 6 extension   < spare bits > **; -- reserved for future use
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.82.2: *RB Information to Reconfigure* information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RB Information to Reconfigure length (11 bit field)

This field is the binary representation of the length of the IE RB Information to Reconfigure in bits excluding the bits used for this length field. Range: 0 to 2047.

| +|

RB Identity

This IE is defined in sub-clause 9.3.80.

| +|

PDCP Info

This IE is defined in sub-clause 9.3.60.

| +|

PDCP SN Info

This IE is defined in sub-clause 9.3.61. The PDCP sequence number info from the network is present only in case of lossless SRNS relocation.

| +|

RLC Info

This IE is defined in sub-clause 9.3.91.

| +|

RB Stop/Continue (1 bit field)

bit

1

0 stop RB

1 continue RB

| +|

RB Mapping Info

This IE is defined in sub-clause 9.3.117.

| + +## 9.3.83 RB Information to Release + +The *RB Information to Release* IE indicates identity of the RB to be released. + +**Table 9.3.83.1: *RB Information to Release* information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------| +| 
 < RB Information to Release IE > ::=   < RB Identity : < RB Identity IE > > ;
| +|---------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.83.2: *RB Information to Release* information element details** + +| | +|------------------------------------------------------------------------------| +|

RB Identity

This field is defined in sub-clause 9.3.80.

| +|------------------------------------------------------------------------------| + +### 9.3.84 RB Information to Setup + +The *RB Information to Setup* IE contains information about the RB to setup. + +**Table 9.3.84.1: *RB Information to Setup* information elements** + +``` +< RB Information to Setup IE > ::= + < RB Information to Setup length : bit (11) > + < RB Identity : < RB Identity IE > > + { 0 | 1 < PDCP Info : < PDCP Info IE > > } + { 0 | 1 < RLC Info : < RLC Info IE > > } + { 0 | 1 < RB Mapping Info : < RB Mapping Info IE > > } -- Release 6 extension + < spare bits > **; -- reserved for future use +``` + +**Table 9.3.84.2: *RB Information to Setup* information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RB Information to Setup length (11 bit field)

This field is the binary representation of the length of the IE RB Information to Setup in bits excluding the bits used for this length field. Range: 0 to 2047.

| +|

RB Identity

This IE is defined in sub-clause 9.3.80.

| +|

PDCP Info

This IE is defined in sub-clause 9.3.60.

| +|

RLC Info

This IE is defined in sub-clause 9.3.91.

| +|

RB Mapping Info

This IE is defined in sub-clause 9.3.117.

| + +### 9.3.85 RB Timer Indicator + +This *RB Timer Indicator* IE indicates to GERAN if the timers T314 and T315 have expired in the MS. + +**Table 9.3.85.1: *RB Timer Indicator* information elements** + +``` +< RB Timer Indicator IE > ::= + < T314 Expired : bit (1) > + < T315 Expired : bit (1) > ; +``` + +**Table 9.3.85.2: *RB Timer Indicator* information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

T314 Expired (1 bit field)

bit

1

0 False - the timer has not expired

1 True - the timer has expired or the stored value is zero

| +|

T315 Expired (1 bit field)

bit

1

0 False - the timer has not expired

1 True - the timer has expired or the stored value is zero

| + +### 9.3.86 RB with PDCP Information + +The *RB with PDCP Information* IE identifies the RB and provides the PDCP sequence number info from the sender of the message for lossless Serving BSC relocation. + +**Table 9.3.86.1: *RB with PDCP Information* information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------| +| < RB with PDCP Information IE > ::=
< RB Identity : < RB Identity IE > >
< PDCP SN Info : < PDCP SN Info > > ; | +|------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.86.2: *RB with PDCP Information* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RB Identity
This IE is defined in sub-clause 9.3.80.

| +|

PDCP SN Info
This IE is defined in sub-clause 9.3.61. PDCP sequence number info from the sender of the message for lossless Serving BSC relocation.

| + +### 9.3.87 (void) + +### 9.3.88 Re-Establishment timer + +This *Re-Establishment Timer* IE indicates which timer to associate with RAB. + +**Table 9.3.88.1: *Re-Establishment Timer* information elements** + +| | +|------------------------------------------------------------------------------------| +| < Re-Establishment timer IE > ::=
< Re-Establishment timer : bit (1) > ; | +|------------------------------------------------------------------------------------| + +**Table 9.3.88.2: *Re-Establishment Timer* information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------| +|

Re-Establishment Timer (1 bit field)
bit
1
0 use T314
1 use T315

| +|----------------------------------------------------------------------------------------------------------------------------| + +### 9.3.89 Rejection Cause + +The *Rejection Cause* IE indicates the cause for rejection of RRC connection establishment request. + +**Table 9.3.89.1: *Rejection Cause* information elements** + +| | +|----------------------------------------------------------------------| +| < Rejection Cause IE > ::=
< Rejection Cause : bit (1) > ; | +|----------------------------------------------------------------------| + +**Table 9.3.89.2: *Rejection Cause* information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------| +|

Rejection Cause (1 bit field)
bit
1
0 congestion
1 unspecified

| +|--------------------------------------------------------------------------------------------------------------------------| + +### 9.3.90 Release Cause + +The *Release Cause* IE indicates the cause for releasing the RRC connection. + +**Table 9.3.90.1: Release Cause information elements** + +| | +|--------------------------------------------------------------------------------| +| 
< Release Cause IE > ::=   < Release Cause : bit (3) >;
| +|--------------------------------------------------------------------------------| + +**Table 9.3.90.2: Release Cause information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
Release Cause (3 bit field) bit 3 2 1 0 0 0 normal event 0 0 1 unspecified 0 1 0 pre-emptive release 0 1 1 congestion 1 0 0 re-establishment reject 1 0 1 directed signalling connection re-establishment 1 1 0 user inactivity 1 1 1 reserved
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.91 RLC Info + +The *RLC Info* IE contains information about the RLC protocol. + +**Table 9.3.91.1: RLC Info information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< RLC Info IE > ::=   < RLC Info length : bit (5) >   { 00 -- RLC in Acknowledged mode     { 0   1 < Resegment : bit (1) > }     { 0   1 < Transmission RLC Discard : < Transmission RLC Discard IE > > }     { 0   1 < EGPRS window size : bit (5) > }   }   { 01 -- RLC in Unacknowledged mode     { 0   1 < EGPRS Window Size : bit (5) > }   }   ! < Message escape : { 1 bit (1) } bit**= < no string > > } ; -- reserved
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.91.2: RLC Info information element details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RLC Info length (5 bit field)
This field is the binary representation of the RLC Info IE excluding the 5 bits used to define this field. Range 0 to 31.

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

Resegment
bit
1
0 Retransmitted RLC data blocks shall not be resegmented
1 Retransmitted RLC data blocks shall be resegmented according to commanded MCS

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

Transmission RLC Discard
This IE is defined in sub-clause 9.3.95.

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

EGPRS Window Size
This information element defines the window size to be used in an EGPRS TBF. The network sets the window size according to the number of timeslots allocated in the direction of the TBF. This Field is coded as defined in 3GPP TS 44.060.

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 9.3.92 RLC HFN IE + +This IE contains the RLC HFN used in ciphering for EGPRS, GPRS or UTRAN in AM or UM RLC. + +Table 9.3.92.1: *RLC HFN* information elements + +``` +< RLC HFN IE > ::= + < RLC HFN length : bit (5) > + { + 000 < RLC HFN : bit (20) > -- Used in the case of EGPRS and UTRAN AM RLC + | 001 < RLC HFN : bit (24) > -- Used in the case of GPRS + | 010 < RLC HFN : bit (25) > -- Used in the case of UTRAN UM RLC + | 011 < RLC HFN : bit (27) > -- Used in the case of GERAN DBPSCH + } + -- Release 6 RLC HFN -- + | 100 < RLC HFN : bit (21) > -- Used in the case of GERAN DBPSCH, AM RLC UDCH TBF mode + | 101 < RLC HFN : bit (27) > -- Used in the case of GERAN DBPSCH, UM RLC UDCH TBF mode + | 110 < RLC HFN : bit (27) > -- Used in the case of GERAN DBPSCH, AM RLC CDCH TBF mode + ! < Message escape : {111 } bit** = < no string > > } ; +``` + +Table 9.3.92.2: *RLC HFN* information element details + +### RLC HFN Length + +This field is the binary representation of the length in bits of the RLC HFN field in this IE. Range: 1+val(RLC HFN length) + +### RLC HFN (20..27 bit field) + +This field defines the RLC HFN used in the ciphering procedure at RLC/MAC. See 3GPP TS 44.160 + +## 9.3.93 RPLMN Information + +Table 9.3.93.1: *RPLMN Information* information elements + +``` +< RPLMN Information IE > ::= + { + -- GSM parameters, lower bound and upper bound of GSM BA freqs + { 0|1 < GSM BA Range : bit (6) > + { + + + } * (1+val(GSM BA Range)))} + } + { 0|1 < CDMA2000 UMTS Frequency list : bit (3) > + { + < BAND_CLASS : bit(5)> + < CDMA_FREQ : bit(11)> } * (1+val(CDMA2000 UMTS Frequency list)))} + }; +``` + +Table 9.3.93.2: *RPLMN Information* information element details + +### GSM BA Range (6 bit field) + +This field is the binary representation of maximum number of GSM Frequency Ranges to store. Range 0 to maxNumGSMFreqRanges-1. + +### GSM Lower Range (14 bit field) + +This field is the binary representation of lower bound for range of GSM BA frequencies, lower bound. + +### GSM Upper Range (14 bit field) + +This field is the binary representation of lower bound for range of GSM BA frequencies, upper bound. + +### UARFCN (14 bit field) + +This field is defined in 3GPP TS 25.102. + +**CDMA2000 UMTS Frequency list** (3 bit field) + +This field is the binary representation of maximum number of CDMA Frequency Ranges to store. Range 0 to maxNumCDMA2000FreqRanges-1. + +**BAND\_CLASS** (5 bit field) + +This field is the bit string representation of TIA/EIA/IS-2000 BAND\_CLASS. The bits are numbered b0 to b4, where b0 is the least significant bit. + +**CDMA\_FREQ** (11 bit field) + +This field is the bit string representation of CDMA\_FREQ TIA/EIA/IS-2000. The CDMA\_FREQ bits are numbered b0 to b10, where b0 is the least significant bit. + +### 9.3.94 RRC Cause + +The *RRC Cause* IE is to provide the reason for failure of the physical channel setup, reconfiguration, release or the reason for completion of handover. + +**Table 9.3.94.1: RRC Cause information elements** + +``` +< RRC Cause IE > ::= + < RRC Cause : bit (8) > +``` + +**Table 9.3.94.2: RRC Cause information element details** + +**RRC Cause** (8 field) + +## Bits + +8 7 6 5 4 3 2 1 + +| | | +|-----------------|--------------------------------------------------| +| 0 0 0 0 0 0 0 0 | Normal event | +| 0 0 0 0 0 0 0 1 | Abnormal release, unspecified | +| 0 0 0 0 0 0 1 0 | Abnormal release, channel unacceptable | +| 0 0 0 0 0 0 1 1 | Abnormal release, timer expired | +| 0 0 0 0 0 1 0 0 | Abnormal release, no activity on the radio path | +| 0 0 0 0 0 1 1 0 | UTRAN configuration unknown | +| 0 0 0 0 1 0 0 0 | Handover impossible, timing advance out of range | +| 0 0 0 0 1 0 0 1 | Channel mode unacceptable | +| 0 0 0 0 1 0 1 0 | Frequency not implemented | +| 0 0 0 0 1 1 0 0 | Lower layer failure | +| 0 1 0 0 0 0 0 1 | Call already cleared | +| 0 1 0 1 1 1 1 1 | Semantically incorrect message | +| 0 1 1 0 0 0 0 0 | Invalid mandatory information | +| 0 1 1 0 0 0 0 1 | Message type non-existent or not implemented | +| 0 1 1 0 0 0 1 0 | Message type not compatible with protocol state | +| 0 1 1 0 0 1 0 0 | Conditional IE error | +| 0 1 1 0 0 1 0 1 | No cell allocation available | +| 0 1 1 0 1 1 1 1 | Protocol error unspecified | + +All other cause values shall be treated as 0000 0000, 'normal event'. + +### 9.3.95 RRC Packet Downlink Assignment + +The *RRC Packet Downlink Assignment* IE is sent by the network to the mobile station to indicate the assigned downlink resources. The *RRC Packet Downlink Assignment* IE is coded as shown in 3GPP TS 44.018. + +**Table 9.3.95.1: RRC Packet Downlink Assignment information elements** + +``` + +< RRC Packet Downlink Assignment IE > ::= + < LENGTH_IN_OCTETS : bit (8) > + < MAC_MODE : bit (2) > + < RLC_MODE : bit (1) > + < TIMESLOT_ALLOCATION : bit (8) > + < Packet Timing Advance : < Packet Timing Advance IE > > + { 0 | 1 < P0 : bit (4) > + < BTS_PWR_CTRL_MODE : bit (1) > + < PR_MODE : bit (1) > } + { 0 | 1 < Power Control Parameters : < Power Control Parameters IE > > } + { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 | 1 < MEASUREMENT_STARTING_TIME : bit (16) > + < MEASUREMENT_INTERVAL : bit (5) > + < MEASUREMENT_BITMAP : bit (8) > } + { 0 | 1 + -- indicates EGPRS TBF mode, see 3GPP TS 44.060 + < EGPRS Window Size : < EGPRS Window Size IE > > + < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > } + { 0 | 1 < BEP_PERIOD2 : bit (4) > } + { 0 | 1 < Packet Extended timing Advance : bit (2) > } ; + +``` + +**Table 9.3.95.2: RRC Packet Downlink Assignment information element details****LENGTH\_IN\_OCTETS (8 bit field)** + +This field encodes (in binary) the number that is equal to one eighth of the number of bits in the *RR Packet Downlink Assignment* information element that follow the end of this field. + +**MAC\_MODE (2 bit field)** + +This field is encoded as the MAC\_MODE information field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +**RLC\_MODE (1 bit field)** + +This field is encoded as the RLC\_MODE field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +**TIMESLOT\_ALLOCATION (8 bit field)** + +This field is encoded as the TIMESLOT\_ALLOCATION field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +**Packet Timing Advance IE** + +This field is encoded as the *Packet Timing Advance* IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +***P0, BTS\_PWR\_CTRL\_MODE and PR\_MODE fields*** + +These fields are optional downlink power control parameters and are encoded as in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +**Power Control Parameters IE** + +This field is encoded as the Power Control Parameters IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +**DOWNLINK\_TFI\_ASSIGNMENT (5 bit field)** + +If present, this field is encoded as the DOWNLINK\_TFI\_ASSIGNMENT information element in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +**MEASUREMENT\_STARTING\_TIME (16 bit field)** + +If present, this field is encoded as the 16-bit *value part* of the *Starting Time* IE defined in sub-clause 10.5.2.38 (starting with bit 8 of octet 2 and ending with bit 1 of octet 3 of the *Starting Time* IE). MEASUREMENT\_STARTING\_TIME field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +The frame number shall be aligned to a PDTCH block period according to the requirements defined for the 'Absolute Frame Number Encoding' in the '*Starting Time Frame Number Description*' IE defined in 3GPP TS 44.060. + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

MEASUREMENT_BITMAP (8 bit field)

If present, this field is encoded as the MEASUREMENT_BITMAP information field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060.

| +|

MEASUREMENT_INTERVAL (5 bit field)

If present, this field is encoded as the MEASUREMENT_INTERVAL field in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060.

| +|

EGPRS Window Size IE

This field is encoded as the EGPRS Window Size IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060.

| +|

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)

This field is encoded as the LINK_QUALITY_MEASUREMENT_MODE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060.

| +|

Packet Extended Timing Advance (2 bit field)

This bit field is used for support of Extended Timing Advance.

Bit

  • 1 bit 7 of the Timing Advance IE defined in sub-clause 10.5.2.40
  • 2 bit 8 of the Timing Advance IE defined in sub-clause 10.5.2.40
| +|

BEP_PERIOD2 (4 bit field)

This field is described in 3GPP TS 44.060.

| + +### 9.3.95a RRC Packet Downlink Assignment 2 + +The *RRC Packet Downlink Assignment 2* IE is sent by the network to the mobile station to indicate the assigned downlink resources. The *RRC Packet Downlink Assignment 2* IE is coded as shown in the table below. + +**Table 9.3.95a.1: RRC Packet Downlink Assignment information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< RRC Packet Downlink Assignment 2 IE > ::=   < LENGTH_IN_OCTETS : bit (8) >   { 0   1 -- indicates EGPRS TBF mode, see 3GPP TS 44.060     < EGPRS Window Size : < EGPRS Window Size IE > >     < LINK_QUALITY_MEASUREMENT_MODE : bit (2) >     { 0   1 < BEP_PERIOD2 : bit (4) > } }
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.95a.2: RRC Packet Downlink Assignment 2 information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

LENGTH_IN_OCTETS (8 bit field)

This field encodes (in binary) the number that is equal to one eighth of the number of bits in the RR Packet Downlink Assignment 2 information element that follow the end of this field.

| +|

EGPRS Window Size IE

This field is encoded as the EGPRS Window Size IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060.

| +|

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)

This field is encoded as the LINK_QUALITY_MEASUREMENT_MODE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060.

| + +### 9.3.96 RRC Packet Uplink Assignment + +The *RRC Packet Uplink Assignment* IE is sent by the network to the mobile station to indicate the assigned uplink resources. The *RRC Packet Uplink Assignment* IE is coded as shown in 3GPP TS 44.018. + +**Table 9.3.96.1: RRC Packet Uplink Assignment information elements** + +``` + +< RRC Packet Uplink Assignment IE > ::= + < LENGTH_IN_OCTETS : bit (8) > + < G-RNTI_BLOCK_CHANNEL_CODING : bit (1) > + < Packet Timing Advance : < Packet Timing Advance IE > > + < Allocation : < Allocation struct > > + { 0 -- for MS operating in GPRS + < CHANNEL_CODING_COMMAND : bit (2) > + | 1 -- for MS operating in EGPRS + < EGPRS_MCS_MODE : bit (4) > + < RESEGMENT : bit (1) > + < EGPRS Window Size : < EGPRS Window Size IE > > } + { 0 | 1 < Packet Extended Timing Advance : bit (2) > } ; + +< Allocation struct > ::= + { 00 < Dynamic Allocation : < Dynamic Allocation struct > > + | 01 < Single Block Allocation : < Single Block Allocation struct > > + ! < Message escape : { 1 bit (1) } bit** = < no string > > } + +< Dynamic Allocation struct > ::= + < Extended Dynamic Allocation : bit (1) > + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit (1) > } + < USF_GRANULARITY : bit (1) > + { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } + { 0 | 1 < RLC_DATA_BLOCKS_GRANTED : bit (8) > + { 0 -- Timeslot Allocation + { 0 | 1 < USF_TN0 : bit (3) > } + { 0 | 1 < USF_TN1 : bit (3) > } + { 0 | 1 < USF_TN2 : bit (3) > } + { 0 | 1 < USF_TN3 : bit (3) > } + { 0 | 1 < USF_TN4 : bit (3) > } + { 0 | 1 < USF_TN5 : bit (3) > } + { 0 | 1 < USF_TN6 : bit (3) > } + { 0 | 1 < USF_TN7 : bit (3) > } + | 1 -- Timeslot Allocation with Power Control Parameters + < ALPHA : bit (4) > + { 0 | 1 < USF_TN0 : bit (3) > + < GAMMA_TN0 : bit (5) > } + { 0 | 1 < USF_TN1 : bit (3) > + < GAMMA_TN1 : bit (5) > } + { 0 | 1 < USF_TN2 : bit (3) > + < GAMMA_TN2 : bit (5) > } + { 0 | 1 < USF_TN3 : bit (3) > + < GAMMA_TN3 : bit (5) > } + { 0 | 1 < USF_TN4 : bit (3) > + < GAMMA_TN4 : bit (5) > } + { 0 | 1 < USF_TN5 : bit (3) > + < GAMMA_TN5 : bit (5) > } + { 0 | 1 < USF_TN6 : bit (3) > + < GAMMA_TN6 : bit (5) > } + { 0 | 1 < USF_TN7 : bit (3) > + < GAMMA_TN7 : bit (5) > } ; + +< Single Block Allocation struct > ::= + < TIMESLOT_NUMBER : bit (3) > + { 0 | 1 < ALPHA : bit (4) > + < GAMMA_TN : bit (5) > } + { 0 | 1 < P0 : bit (4) > + < BTS_PWR_CTRL_MODE : bit (1) > + < PR_MODE : bit (1) > } ; + +``` + +**Table 9.3.96.2: RRC Packet Uplink Assignment information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LENGTH_IN_OCTETS (8 bit field)
This field is the binary representation of the length of the RR Packet Uplink Assignment IE value part in octets. Range: 0 to 255 | +| CHANNEL_CODING_COMMAND (2 bit field)
This field is encoded as the CHANNEL_CODING_COMMAND field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| TLLI_BLOCK_CHANNEL_CODING (1 bit field)
This field is encoded as the TLLI_BLOCK_CHANNEL_CODING field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| Packet Timing Advance IE
This field is encoded as the Packet Timing Advance IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| Allocation struct
This structure indicates the type of radio resources allocation used and the parameters necessary to define the radio resources. | +| EGPRS_MCS_MODE (4 bit field)
This field is coded as the EGPRS Modulation and Coding Scheme IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| RESEGMENT (1 bit field)
This field is coded as the RESEGMENT bit in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| EGPRS Window Size IE
This field is encoded as the EGPRS window size IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. | +| TIMESLOT_ALLOCATION (8 bit field)
This field is encoded as the TIMESLOT_ALLOCATION field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| Dynamic Allocation struct
This structure contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation. | +| Extended Dynamic Allocation (1 bit field)
This information field indicates the medium access mode to be used during the TBF.
0 Dynamic Allocation
1 Extended Dynamic Allocation | +| UPLINK_TFI_ASSIGNMENT (5 bit field)
This field is encoded as the UPLINK_TFI_ASSIGNMENT information element in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| Power Control Parameters IE
This field is encoded as the Power Control Parameters IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +| RLC_DATA_BLOCKS_GRANTED (8 bit field)
This field is encoded as the RLC_DATA_BLOCKS_GRANTED field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | + +| | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|--|---------|--|---------|----------------|---------|----------------|-----|--|---------|----------------|---------|----------------| +|

USF for Timeslot Number 0 (TN0) (3 bit field)
USF for Timeslot Number 1 (TN1) (3 bit field)
USF for Timeslot Number 2 (TN2) (3 bit field)
USF for Timeslot Number 3 (TN3) (3 bit field)
USF for Timeslot Number 4 (TN4) (3 bit field)
USF for Timeslot Number 5 (TN5) (3 bit field)
USF for Timeslot Number 6 (TN6) (3 bit field)
USF for Timeslot Number 7 (TN7) (3 bit field)
These fields are encoded as the USF for Timeslot Number X field (where 0 ≤ X < 7) in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060.

| | | | | | | | | | | | | | | +|

Single Block Allocation struct
This structure contains parameters necessary to define the radio resources of a Single Block allocation. For example for sending of a PACKET RESOURCE REQUEST message in a two phase access or a Measurement report.

| | | | | | | | | | | | | | | +|

ALPHA (4 bit field)
The ALPHA Power control parameter field is coded according to the following table :

bit
4 3 2 1
0 0 0 0 \alpha = 0.0
0 0 0 1 \alpha = 0.1
: :
1 0 0 1 \alpha = 0.9
1 0 1 0 \alpha = 1.0

All other values are reserved in this version of the protocol and shall be interpreted by the mobile station as \alpha = 1.0.

| bit | | 4 3 2 1 | | 0 0 0 0 | $\alpha = 0.0$ | 0 0 0 1 | $\alpha = 0.1$ | : : | | 1 0 0 1 | $\alpha = 0.9$ | 1 0 1 0 | $\alpha = 1.0$ | +| bit | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | +| 0 0 0 0 | $\alpha = 0.0$ | | | | | | | | | | | | | | +| 0 0 0 1 | $\alpha = 0.1$ | | | | | | | | | | | | | | +| : : | | | | | | | | | | | | | | | +| 1 0 0 1 | $\alpha = 0.9$ | | | | | | | | | | | | | | +| 1 0 1 0 | $\alpha = 1.0$ | | | | | | | | | | | | | | +|

TIMESLOT_NUMBER (3 bit field)
If present, this field is encoded as the TIMESLOT_NUMBER field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060.

| | | | | | | | | | | | | | | +|

GAMMA_TN (5 bit field)
The GAMMA_TN field is the binary representation of the parameter \Gamma_{CH} for MS output power control in units of 2 dB, see 3GPP TS 45.008.

| | | | | | | | | | | | | | | +|

P0, BTS_PWR_CTRL_MODE and PR_MODE fields
These fields are optional downlink power control parameters and are encoded as in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060.

| | | | | | | | | | | | | | | + +## 9.3.96a RRC Packet Uplink Assignment 2 + +The *RRC Packet Uplink Assignment 2* IE is sent by the network to the mobile station to indicate the assigned uplink PDCTH on DBPSCH. The *RRC Packet Uplink Assignment 2* IE is coded as shown in the table below. + +**Table 9.3.96a.1: RRC Packet Uplink Assignment 2 information elements** + +``` + +< RRC Packet Uplink Assignment 2 IE > ::= + < LENGTH_IN_OCTETS : bit (8) > + < Dynamic Allocation : < Dynamic Allocation struct > > + { 0 -- for MS operating in GPRS + < CHANNEL_CODING_COMMAND : bit (2) > + | 1 -- for MS operating in EGPRS + < EGPRS_MCS_MODE : bit (4) > + < RESEGMENT : bit (1) > + < EGPRS Window Size : < EGPRS Window Size IE > > }; + +< Dynamic Allocation struct > ::= + < Extended Dynamic Allocation : bit (1) > + < USF_GRANULARITY : bit (1) > + { 0 | 1 < USF_TN0 : bit (3) > } + { 0 | 1 < USF_TN1 : bit (3) > } + { 0 | 1 < USF_TN2 : bit (3) > } + { 0 | 1 < USF_TN3 : bit (3) > } + { 0 | 1 < USF_TN4 : bit (3) > } + { 0 | 1 < USF_TN5 : bit (3) > } + { 0 | 1 < USF_TN6 : bit (3) > } + { 0 | 1 < USF_TN7 : bit (3) > }; + +``` + +**Table 9.3.96a.2: RRC Packet Uplink Assignment information element details****LENGTH\_IN\_OCTETS (8 bit field)** + +This field is the binary representation of the length of the *RR Packet Uplink Assignment IE* value part in octets. Range: 0 to 255 + +**CHANNEL\_CODING\_COMMAND (2 bit field)** + +This field is encoded as the CHANNEL\_CODING\_COMMAND field in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +**EGPRS\_MCS\_MODE (4 bit field)** + +This field is coded as the EGPRS Modulation and Coding Scheme IE in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +**RESEGMENT (1 bit field)** + +This field is coded as the RESEGMENT bit in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. + +**EGPRS Window Size IE** + +This field is encoded as the *EGPRS window size IE* in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. + +**Dynamic Allocation struct** + +This structure contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation. + +**Extended Dynamic Allocation (1 bit field)** + +This information field indicates the medium access mode to be used during the TBF. + +0 Dynamic Allocation + +1 Extended Dynamic Allocation + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| USF for Timeslot Number 0 (TN0) (3 bit field)
USF for Timeslot Number 1 (TN1) (3 bit field)
USF for Timeslot Number 2 (TN2) (3 bit field)
USF for Timeslot Number 3 (TN3) (3 bit field)
USF for Timeslot Number 4 (TN4) (3 bit field)
USF for Timeslot Number 5 (TN5) (3 bit field)
USF for Timeslot Number 6 (TN6) (3 bit field)
USF for Timeslot Number 7 (TN7) (3 bit field)
These fields are encoded as the USF for Timeslot Number X field (where $0 \leq X < 7$ ) in the PACKET UPLINK ASSIGNMENT message in 3GPP TS 44.060. | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.97 RRC State Indicator + +The *RRC State Indicator* IE is indicates to a MS the RRC state to be entered. + +**Table 9.3.97.1: *RRC State Indicator* information elements** + +| | +|-----------------------------------------------------------------------------| +| < RRC State Indicator IE > ::=
< RRC State Indicator : bit (2) >; | +|-----------------------------------------------------------------------------| + +**Table 9.3.97.2: *RRC State Indicator* information element details** + +| | | | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------------------------|--|-----|--|--|-----|--|--------------------------|-----|--|-----------------------|-----|--|-------------------|-----|--|----------| +| RRC State Indicator (2 bit field)
bit
2 1
0 0 RRC-Cell_Dedicated state
0 1 RRC-Cell_Shared state
1 0 RRC-GRA_PCH state
1 1 Reserved
| bit | | | 2 1 | | | 0 0 | | RRC-Cell_Dedicated state | 0 1 | | RRC-Cell_Shared state | 1 0 | | RRC-GRA_PCH state | 1 1 | | Reserved | +| bit | | | | | | | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | | | | | | | +| 0 0 | | RRC-Cell_Dedicated state | | | | | | | | | | | | | | | | | +| 0 1 | | RRC-Cell_Shared state | | | | | | | | | | | | | | | | | +| 1 0 | | RRC-GRA_PCH state | | | | | | | | | | | | | | | | | +| 1 1 | | Reserved | | | | | | | | | | | | | | | | | + +### 9.3.98 RRC Transaction Identifier + +The *RRC Transaction Identifier* IE identifies the RRC procedure transaction for the message this IE was included within. + +**Table 9.3.98.1: *RRC Transaction Identifier* information elements** + +| | +|-------------------------------------------------------------------------------------------| +| < RRC Transaction Identifier IE > ::=
< RRC Transaction Identifier : bit (2) >; | +|-------------------------------------------------------------------------------------------| + +**Table 9.3.98.2: *RRC Transaction Identifier* information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------| +| RRC Transaction Identifier
This field is the binary representation of the RRC Transaction Identifier . Range: 0 to 3 | +|--------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.99 SBPSCH Description + +The *SBPSCH Description* IE describes shared physical resources. + +**Table 9.3.99.1: SBPSCH Description information elements** + +``` + +< SBPSCH Description IE > ::= +{ + { 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > } + { 1 < TBF Information: < TBF Information struct > > } ** 0 +}; + +< TBF Information struct > ::= +{ + < TBF Starting Time : < Starting Time IE > > + { 0 < Description of the Uplink Packet Channel Assignment : < RRC Packet Uplink Assignment IE> > + | 1 < Description of the Downlink Packet Channel Assignment : < RRC Packet Downlink Assignment IE> > + { 0 | 1 < HFN_LSB : bit(1) > } +}; + +``` + +**Table 9.3.99.2: SBPSCH Description information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Frequency Parameters
This IE is defined in TS 3GPP 44.060 sub-clause 12.8. | +| TBF Information struct
This structure describe the information for a TBF. This structure may be repeated up to maxTBF times. | +| TBF Starting Time
The Starting Time IE is defined in sub-clause 9.3.103. | +| Description of the Uplink Packet Channel Assignment
The RRC Packet Uplink Assignment IE is defined in sub-clause 9.3.96. | +| Description of the Downlink Packet Channel Assignment
The RRC Packet Downlink Assignment IE is defined in sub-clause 9.3.95. | +| HFN_LSB (1 bit field)
This field contains the least significant bit of the HFN of the radio bearer for which the TBF is assigned, in the direction of the TBF. | + +## 9.3.100 Security Capability + +The *Security Capability* IE indicates the security capabilities of the MS. + +**Table 9.3.100.1: Security Capability information elements** + +``` + +< Security Capability IE > ::= + < Security Capability Length : bit (7)> + < lu mode Ciphering algorithm capability : < lu mode Ciphering algorithm capability struct > > + < lu mode Integrity protection algorithm capability : < lu mode Integrity protection algorithm capability struct > > ; + < spare bit > **; -- Extension information may be truncated between released versions of the protocol + -- The receiver shall assume the value zero for any truncated bit + +< lu mode Ciphering algorithm capability struct > ::= + < UEA0 support : bit (1) > + < UEA1 support : bit (1) > + < spare bit > *14; + +< lu mode Integrity protection algorithm capability struct > ::= + < UIA1 support : bit (1) > + < spare bit > *15; + +``` + +**Table 9.3.100.2: *Security Capability* information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Security Capability Length (7 bit field)
This field is the binary representation of the length of the Security Capability IE in bits excluding the bits used for this length field. Range: 0 to 127.

| +|

Iu mode Ciphering algorithm capability struct
This structure indicates the ciphering algorithms supported by the MS.
UEA0 support (1 bit field)
UEA1 support (1 bit field)

These fields indicate the support of the UEA encryption algorithm UEAx, where X has a range from 1 to 2. At least one Ciphering algorithm must be supported.
bit
0 Ciphering algorithm is not supported
1 Ciphering algorithm is supported

| +|

Iu mode Integrity protection algorithm capability struct
This structure indicates the Integrity protection algorithms supported by the MS.

| +|

UIA1 support (1 bit field)
These field indicates the support of the UIA integrity protection algorithm UIAx, where X has a range from 1 to 1. At least one integrity protection algorithm must be supported.

bit
0 Integrity protection algorithm is not supported
1 Integrity protection algorithm is supported

| + +## 9.3.101 Signalling RB Information To Setup + +The *Signalling RB Information To Setup* IE indicates information for setting up SRBs. + +**Table 9.3.101.1: *Signalling RB Information To Setup* information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Signalling RB Information To Setup IE > ::=   < Signalling RB Information to Setup length : bit (8) >   < SRB Identity : bit (2) >   { 0   1 < RB Mapping Info : < RB Mapping Info IE > > } -- Release 6 extension   < spare bits > **; -- reserved for future use
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.101.2: *Signalling RB Information To Setup* information element details** + +| | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--|-----|--|-----|------|-----|------|-----|------|-----|------| +|

SRB Identity (2 bit field)

bit
2 1
0 0 SRB1
0 1 SRB2
1 0 SRB3
1 1 SRB4
| bit | | 2 1 | | 0 0 | SRB1 | 0 1 | SRB2 | 1 0 | SRB3 | 1 1 | SRB4 | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | SRB1 | | | | | | | | | | | | +| 0 1 | SRB2 | | | | | | | | | | | | +| 1 0 | SRB3 | | | | | | | | | | | | +| 1 1 | SRB4 | | | | | | | | | | | | +|

Signalling RB Information To Setup length (8 bit field)
This field is the binary representation of the length of the IE Signalling RB Information To Setup in bits excluding the bits used for this length field. Range: 0 to 255.

| | | | | | | | | | | | | +|

RB Mapping Info
This IE is defined in sub-clause 9.3.117.

| | | | | | | | | | | | | + +### 9.3.102 START + +The *START* IE contains the START value used to initialise the 20 most significant bits of all hyper frame numbers (MAC HFN, RLC UM HFN, RLC AM HFN, RRC HFN) for a CN domain. This field is defined in 3GPP TS 33.102. + +**Table 9.3.102.1: *START* information elements** + +| | +|-----------------------------------------------------------------| +| 
< START IE > ::=   < START : bit(20) > ;
| +|-----------------------------------------------------------------| + +**Table 9.3.102.2: *START* information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------| +|

START (20 bit field)
The START bits are numbered b0-b19, where b0 is the least significant bit.

| +|----------------------------------------------------------------------------------------------------------------------------| + +### 9.3.103 Starting Time + +The *Starting Time* IE provides the start TDMA frame number, FN modulo 42432. + +**Table 9.3.103.1: *Starting Time* information elements** + +| | +|----------------------------------------------------------------------------------------| +| 
< Starting Time IE > ::=   < Starting Time Value : octet(2) > ;
| +|----------------------------------------------------------------------------------------| + +**Table 9.3.103.2: *Starting Time* information element details** + +| | +|----------------------------------------------------------------------------------------------------| +|

Starting Time Value
This field is encoded as defined in 3GPP TS 44.018.

| +|----------------------------------------------------------------------------------------------------| + +### 9.3.104 Synchronization Indication + +The *Synchronization Indication* IE is to indicate which type of handover is to be performed. + +**Table 9.3.104.1: *Synchronization Indication* information elements** + +| | +|----------------------------------------------------------------------------------------------------------------| +| 
< Synchronization Indication IE > ::=   < Synchronization Indication Value: bit (4) > ;
| +|----------------------------------------------------------------------------------------------------------------| + +**Table 9.3.104.2: *Synchronization Indication* information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------| +|

Synchronization Indication Value
This field is encoded as defined in 3GPP TS 44.018.

| +|-----------------------------------------------------------------------------------------------------------------| + +### 9.3.105 Time Difference + +The *Time Difference* IE is to provide information about the synchronization difference between the time bases of two Base Stations. This type of information element is used in relation with the pseudo-synchronization scheme, see 3GPP TS 45.010. The *Time Difference* IE is coded as shown in 3GPP TS 44.018. + +**Table 9.3.105.1: *Time Difference* information elements** + +| | +|-------------------------------------------------------------------------------------------| +| 
< Time Difference IE > ::=   < Time Difference Value : bit (8) > ;
| +|-------------------------------------------------------------------------------------------| + +**Table 9.3.105.2: *Time Difference* information element details** + +| | +|----------------------------------------------------------------------------------------| +| Time Difference Value (8 bit field)
This field is defined in 3GPP TS 44.018. | +|----------------------------------------------------------------------------------------| + +## 9.3.106 Timing Advance + +This *Timing Advance* IE is to provide the timing advance value. + +The *Timing Advance* IE is coded as shown in Figure 10.5.2.40.1/3GPP TS 44.018 and Table 10.5.2.40.1/3GPP TS 44.018. + +**Table 9.3.106.1: *Timing Advance* information elements** + +| | +|-------------------------------------------------------------------------| +| < Timing Advance IE > ::=
< Timing Advance Value : bit (8) >; | +|-------------------------------------------------------------------------| + +**Table 9.3.106.2: *Timing Advance* information element details** + +| | +|---------------------------------------------------------------------------------------| +| Timing Advance Value (8 bit field)
This field is defined in 3GPP TS 44.018. | +|---------------------------------------------------------------------------------------| + +## 9.3.107 Transmission RLC Discard + +The *Transmission RLC Discard* IE indicates SDU Discard mode. + +**Table 9.3.107.1: *Transmission RLC Discard* information elements** + +| | +|---------------------------------------------------------------------------------------| +| < Transmission RLC Discard IE > ::=
< Transmission RLC Discard : bit (1) >; | +|---------------------------------------------------------------------------------------| + +**Table 9.3.107.2: *Transmission RLC Discard* information element details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transmission RLC Discard (1 bit field)
This field indicates whether the discharge of RLC buffer on the transmitter side can occur. For UM RLC or TM RLC, RLC discard shall not be used for that radio bearer. | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | +|------------------------------------------------------------------------------------------------------------------------| +| bit
1
0 no discharge of the transmission RLC buffer
1 discharge of the transmission RLC buffer based on timer | +|------------------------------------------------------------------------------------------------------------------------| + +## 9.3.108 UE UTRAN Radio Access Capability + +This IE indicates the UTRAN radio access capability of the MS. + +**Table 9.3.108.1: *UE UTRAN Radio Access Capability* information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < UE UTRAN Radio Access Capability IE > ::=
{ < UE UTRAN Radio Access Capability length : bit(14) >
< UE UTRAN Radio Access Capability : bit (1+val( UE UTRAN Radio Access Capability length)) > } ; | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.108.2: UE UTRAN Radio Access Capability information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------| +| UE UTRAN Radio Access Capability length
This field indicates the length of the UE Radio Access capability field in bits. | +| UE UTRAN Radio Access Capability
This field is encoded as the UE Radio Access capability IE in 3GPP TS 25.331. | + +### 9.3.108a UE UTRAN Predefined Configuration Status Information + +This IE is valid only for UTRAN capable mobiles. The IE indicates UTRAN predefined configuration status information /UECapability/UTRANClassmark information. The IE includes the INTER RAT HANDOVER INFO (defined in 3GPP TS 25.331) which may give UTRAN related information to the network (target system) for intersystem handover. The INTER-RAT HANDOVER INFO message contains following information: + +- The Pre-defined configuration status information; and/or +- Security information to be used after handover to UTRAN, see 3GPP TS 31.102; and/or +- The UTRAN Capabilities of the MS. + +None, one, two or three of these three information may be present. The security information present in the message should be ignored. + +**Table 9.3.108a.1: UE UTRAN Predefined Configuration Status Information information elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< UE UTRAN Predefined configuration status information IE > ::= {   < UE UTRAN Predefined Configuration Status Information length : bit(14) >   < UE UTRAN Predefined Configuration Status Information : bit (1+val( UE UTRAN Predefined configuration status information length)) > ; }
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.108a.2: UE UTRAN Predefined Configuration Status Information information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE UTRAN Predefined Configuration Status Information length
This field indicates the length of the UE UTRAN Predefined Configuration Status Information field in bits. | +| UE UTRAN Predefined Configuration Status Information
This value part of this field is the INTER RAT HANDOVER INFO message as defined in 3GPP TS 25.331. | + +### 9.3.109 UE UTRAN Radio Access Capability Extension + +This IE indicates the UTRAN radio access capability extension of the MS. + +**Table 9.3.109.1: UE UTRAN Radio Access Capability Extension information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< UE UTRAN Radio access capability extension IE > ::= {   < UE UTRAN Radio Access Capability Extension length : bit(10) >   < UE UTRAN Radio Access Capability Extension : bit (1+val( UE UTRAN Radio Access Capability Extension length)) > ; }
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.109.2: UE UTRAN Radio Access Capability Extension information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------| +| UE UTRAN Radio Access Capability length
This field indicates the length of the UE UTRAN Radio access capability extension field in bits. | +| UE UTRAN Radio Access Capability Extension
This IE is defined in 3GPP TS 25.331 as Radio access capability extension. | + +### 9.3.110 UE CDMA2000 Radio Access Capability + +This Information Element contains the UE CDMA2000 radio access capability that is structured and coded according to the specification used for the corresponding system type. + +**Table 9.3.110.1: UE CDMA2000 Radio Access Capability information elements** + +``` +< UE CDMA2000 Radio Access Capability IE > ::= + < CDMA2000 Information length : bit(12) > + < CDMA2000 Information : bit(1+val(CDMA2000 Information length)) > ; +``` + +**Table 9.3.110.2: UE CDMA2000 Radio Access Capability information element details** + +#### CDMA2000 Information length (12 bit field) + +This field indicates the length of the CDMA2000 Information field in bits. + +#### CDMA2000 Information + +This field is encoded as the *CDMA2000 Radio Access Capability* IE defined in TTA/EIA/IS-2000 or later, TTA/EIA/IS-833 or later, TTA/EIA/IS-834 or later. + +### 9.3.111 UTRAN Freq List + +This variable length IE is coded as defined in 3GPP TS 44.018. + +### 9.3.112 Wait Time + +The *Wait Time* IE defines the time period the MS has to wait before repeating the rejected procedure. + +**Table 9.3.112.1: Wait Time information elements** + +``` +< Wait Time IE > ::= + < Wait Time : bit (4) > ; +``` + +**Table 9.3.112.2: Wait Time Capability information element details** + +#### Wait Time (4 bit field) + +| bit | | +|---------|-------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | -- repetition is not allowed | +| 0 0 0 1 | 1s | +| 0 0 1 0 | 2s | +| : | | +| : | | +| 1 1 1 0 | 14s | +| 1 1 1 1 | 15s | + +### 9.3.113 Iu mode Channel Request Description + +The *Iu mode Channel Request Description* IE is used by the mobile station to request uplink resources. + +**Table 9.3.113.1: Iu mode Channel Request Description information elements** + +``` + +< Iu mode Channel Request Description IE > ::= + < LENGTH_IN_OCTETS : bit(8) > -- Remaining length + < PACKET_ESTABLISHMENT_CAUSE : bit(2) > + < Iu mode RRC Channel Request Description : Iu mode Channel Request Description IE > -- Defined in +3GPP TS 44.060 + { 0 | 1 < HFN_LSB : bit(1) > } + < spare bit >**; + +``` + +**Table 9.3.113.2: Iu mode Channel Request Description information element details** + +**PACKET\_ESTABLISHMENT\_CAUSE** (2 bit field) +This field indicates the reason for requesting the access. + +| Bit | | +|-----|-------------------------------| +| 2 1 | | +| 0 0 | User Data | +| 0 1 | Page Response | +| 1 0 | Cell Update | +| 1 1 | Mobility Management procedure | + +**Iu mode Channel Request Description** +This IE is defined in 3GPP TS 44.060. + +**HFN\_LSB** (1 bit field) +This field contains the least significant bit of the HFN of the radio bearer for which the TBF is established, in the direction of the TBF. + +## 9.3.114 Wait Indication + +The *Wait Indication* IE element is used by the network to indicate the time the mobile station shall wait before attempting another channel request after the GERAN Iu mode DTM REJECT message is received. + +**Table 9.3.106.1: Wait Indication information elements** + +``` + +< Wait Indication IE > ::= + < Wait Indication : bit (8) >; + +``` + +**Table 9.3.106.2: Wait Indication information element details** + +**Wait Indication Value** (8 bit field) +This field is coded as the binary representation of the T3142 timeout value in seconds. This IE is defined in 3GPP TS 44.018. + +## 9.3.115 (void) + +## 9.3.116 PDCP Context Relocation Info + +The *PDCP Context Relocation Info* IE indicates that the header compression context relocation is to be performed during SBSS relocation for the given radio bearer. + +**Table 9.3.116.1: PDCP Context Relocation Info elements** + +``` + +< PDCP Context Relocation Info IE > ::= + < PDCP Context Relocation Info length: bit (2) > + { + < Downlink RFC3095 Context Relocation Indication: 0 > + | < Downlink RFC3095 Context Relocation Indication: 1 > } + { + < Uplink RFC3095 Context Relocation Indication: 0 > + | < Uplink RFC3095 Context Relocation Indication: 1 > } + ; + +``` + +**Table 9.3.116.2: PDCP Context Relocation Info information elements details****Downlink RFC3095 Context Relocation Indication (1 bit field)** + +``` + +bit +1 +0 RFC3095 context relocation is not performed in downlink +1 RFC3095 context relocation is performed in downlink + +``` + +**Uplink RFC3095 Context Relocation Indication (1 bit field)** + +``` + +bit +1 +0 RFC3095 context relocation is not performed in uplink +1 RFC3095 context relocation is performed in uplink + +``` + +## 9.3.117 RB mapping info + +The IE includes the transport channel information on which the RB can be mapped. + +**Table 9.3.117.1: RB Mapping Info information element** + +``` + +< RB Mapping Info IE > ::= + < RB Mapping Info length : bit (8) > + { 00 -- Uplink information + < Uplink Transport Channel Type : bit (1) > + < UL Transport Channel Identity : < Transport Channel Identity IE > > + { 00 -- All; RLC Sizes listed in TFS IE + | 01 -- Configured; RLC Sizes listed in TFS + | 10 -- RLC explicit List + < RLC Size Index List : bit (11) > + < RLC Size Index: bit (11) > } * (1+val(RLC Size Index List) ) + ! < Message escape : { 11 } bit** = < no string > > } + | 01 -- Downlink information + < Downlink Transport Channel Type : bit (1) > + < DL TrCH Identity : < Transport Channel Identity IE > > + ! < Message escape : { 10 | 11 } bit** = < no string > > } + < spare bits > **; -- Reserved for future use + +``` + +**Table 9.3.117.2: RB Mapping Info information element details****RB Mapping Info length (8 bit field)** + +This field is the binary representation of the length of the IE *RB Mapping Info* in bits excluding the bits used for this length field. Range: 0 to 256. + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Downlink Transport Channel Type (1 bit field)

This field is used to indicate the binary representation of the number of downlink TrCH used.

bit

1

0 DCH

All the other values are reserved

| +|

DL Transport Channel Identity

The IE Transport Channel Identity is defined in sub-clause 9.3.130.

| +|

TFS

The IE Transport Format Set is defined in sub-clause 9.3.133.

| +|

Uplink Transport Channel Type (1 bit field)

This field is used to indicate the binary representation of the number of uplink TrCH used.

bit

1

0 DCH

All the other values are reserved.

| +|

UL Transport Channel Identity

The IE Transport Channel Identity is defined in sub-clause 9.3.130.

| +|

RLC Size Index List (11 bit field)

This field is used to indicate the binary representation of the number RLC size. The integer number is a reference to the RLC size that arrived at that position in the IE Transport Format Set.

| +|

RLC Size Index (11 bit field)

The integer number is a reference to the RLC size position in the IE Transport Format Set.

| + +## 9.3.118 Interleaving + +The IE includes the information about interleaving used for FLO configuration on the basic physical channels. + +**Table 9.3.118.1: *Interleaving* information elements** + +| | +|--------------------------------------------------------------------------------------| +|

< Interleaving IE > ::=

< Interleaving: bit (2) > ;

| +|--------------------------------------------------------------------------------------| + +**Table 9.3.118.2: *Interleaving* information element details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Interleaving (2 bit field)

Bit

21

00 20 ms rectangular

01 40 ms diagonal

All the other values are reserved.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 9.3.119 Mode + +The IE includes the information about mode used for FLO configuration on the basic physical channels. + +**Table 9.3.119.1: *Mode* information elements** + +| | +|-----------------------------------------------------------------------| +|

< Mode IE > ::=

< Mode : bit (2) > ;

| +|-----------------------------------------------------------------------| + +**Table 9.3.119.2: Mode information element details****Mode** (2 bit field) + +This is the binary representation of the mode used for FLO configuration. + +bit + +21 + +00 FR + +01 HR. + +All the other values are reserved. + +## 9.3.120 Modulation + +The IE includes the information about modulation used for FLO configuration on the basic physical channels. + +**Table 9.3.119.1: Modulation information elements** + +``` +< Modulation IE > ::= + < Modulation : bit (2) > ; +``` + +**Table 9.3.119.2: Modulation information element details****Modulation** (2 bit field) + +This is the binary representation of the modulation used for FLO configuration. + +bit + +21 + +00 GMSK + +01 GMSK and 8PSK + +All the other values are reserved. + +## 9.3.121 Added or Reconfigured DL TrCH information + +**Table 9.3. 121.1: Added or Reconfigured DL TrCH Information information elements** + +``` +< Added or Reconfigured DL TrCH Information IE > ::= + < Downlink Transport Channel Type : bit (1) > + < DL Transport Channel Identity : < Transport Channel Identity IE > > + { 0 -- Explicit + < TFS : < Transport Format Set IE > > + | 1 -- SameAsUL + < UL Transport Channel Identity : < Transport Channel Identity IE > > } ; +``` + +**Table 9.3. 121.2: Added or Reconfigured DL TrCH Information information element details****Downlink Transport Channel Type** (1 bit field) + +This field is used to indicate the binary representation of the number of downlink TrCH used. + +bit + +1 + +0 DCH + +All the other values are reserved. + +**DL Transport Channel Identity** + +The IE *Transport Channel Identity* is defined in sub-clause 9.3.130. + +**UL Transport Channel Identity** + +The IE *Transport Channel Identity* is defined in sub-clause 9.3.130. + +**TFS** + +The IE *Transport Format Set* is defined in sub-clause 9.3.133. + +## 9.3.122 Added or Reconfigured UL TrCH information + +**Table 9.3.122.1: Added or Reconfigured UL TrCH information information element** + +``` +< Added or Reconfigured UL TrCH information IE > ::= + < Uplink Transport Channel Type : bit (1)> + < UL Transport Channel Identity : < Transport Channel Identity IE > > + < TFS : < Transport Format Set IE> > ; +``` + +**Table 9.3.122.2: Added or Reconfigured UL TrCH information information element details** + +### Uplink Transport Channel Type (1 bit field) + +This field is used to indicate the binary representation of the number of uplink TrCH used. + +bit + +1 + +0 DCH + +All the other values are reserved + +### UL Transport Channel Identity + +The *Transport Channel Identity IE* is defined in sub-clause 9.3.130. + +### TFS + +The IE *Transport Format Set* is defined in sub-clause 9.3.133. + +## 9.3.123 Deleted DL TrCH information + +**Table 9.3.123.1: Deleted DL TrCH Information information element** + +``` +< Deleted DL TrCH Information IE > ::= + < Downlink Transport Channel Type : bit (1)> + < DL Transport Channel Identity : < Transport Channel Identity IE > > ; +``` + +**Table 9.3. 123.2: Deleted DL TrCH Information information element details** + +### Downlink Transport Channel Type (1 bit field) + +This field is used to indicate the binary representation of the number of downlink TrCH used. + +bit + +1 + +0 DCH + +All the other values are reserved + +### DL Transport Channel Identity + +The *Transport Channel Identity IE* is defined in sub-clause 9.3.130. + +### 9.3.124 Deleted UL TrCH information + +**Table 9.3.124.1: Deleted UL TrCH Information information element** + +``` +< Deleted UL TrCH Information IE > ::= + < Uplink Transport Channel Type : bit (1)> + < UL Transport Channel Identity : < Transport Channel Identity IE > ; +``` + +**Table 9.3.124.2: Deleted UL TrCH Information information element details** + +#### Uplink Transport Channel Type (1 bit field) + +This field is used to indicate the binary representation of the number of uplink TrCH used. + +bit + +1 + +0 DCH + +All the other values are reserved + +#### UL Transport Channel Identity + +The IE *Transport Channel Identity* is defined in sub-clause 9.3.130. + +### 9.3.125 DL TrCH Information Common For All Transport Channels + +**Table 9.3.125.1: DL TrCH Information Common For All Transport Channels information elements** + +``` +< DL TrCH Information Common For All Transport Channels IE > ::= + { 0 -- Explicit + < DL DCH TFCS: < Transport Format Combination Set IE> > + | 1 }; -- SameAsUL-no data +``` + +**Table 9.3.125.2: DL TrCH Information Common For All Transport Channels information element details** + +#### DL DCH TFCS + +The IE *Transport Format Combination Set* is defined in sub-clause 9.3.132. This IE is used when the choice is to define the DL TrCH information common for all transport channels is "Explicit". + +### 9.3.126 Semi-static Transport Format Information + +**Table 9.3.123.1: Semi-static Transport Format Information information element** + +``` +< Semi-static Transport Format Information IE > ::= + < Rate Matching Attribute: bit (8) > + < CRC Size : bit (3) > ; +``` + +**Table 9.3.126.2: Semi-static Transport Format Information information element details** + +#### Rate Matching Attribute ( 8 bit field ) + +This field is the binary representation of the RMA attribute sent. Range : 1 to 256. + +**CRC size** (3 bit field ) + +bit + +3 2 1 + +0 0 0 0 bits + +0 0 1 6 bits + +0 1 0 12 bits + +0 1 1 18 bits + +All the other values are reserved + +## 9.3.127 TFCS Explicit Configuration + +This IE indicates the explicit configuration of TFCS sent for the TrCH. + +**Table 9.3.127.1: TFCS Explicit Configuration information elements** + +``` +< TFCS Explicit Configuration IE > ::= +{ 00 -- complete configuration + < TFCS Complete Reconfiguration Information : < TFCS Reconfiguration/Addition Information IE> > +| 01 -- Addition + < TFCS Addition Information : < TFCS Reconfiguration/Addition Information IE> > +| 10 -- Removal + < < TFCS Removal Information : < TFCS Removal Information IE> > + { 0 Compression Algorithm : 0 + | 1 Compression Algorithm : 1 } } +| 11 -- Replace + < TFCS Removal Information : < TFCS Removal Information IE> > + < TFCS Addition Information : < TFCS Reconfiguration/Addition Information IE> > +}; +``` + +**Table 9.3.127.2: TFCS Explicit Configuration information element details** + +### TFCS Complete Reconfiguration Information + +The *TFCS Reconfiguration/Addition Information IE* is defined in sub-clause 9.3.128. + +### TFCS Addition Information + +The *TFCS Reconfiguration/Addition Information IE* is defined in sub-clause 9.3.128. + +### TFCS Removal Information + +The *TFCS Removal Information IE* is defined in sub-clause 9.3.129. + +### Compression Algorithm + +This flag indicates if the compression algorithm can be applied. The value is boolean. + +## 9.3.128 TFCS Reconfiguration/Addition Information + +**Table 9.3.128.1: TFCS Reconfiguration/Addition Information information elements** + +``` + +< TFCS Reconfiguration/Addition Information IE > ::= + < TFCS Reconfiguration/Addition Information length : bit (3) > + { 000 -- 2bit CTFC + { < Length of CTFC Information: bit (5) > + < 2 bit CTFC : < bit (2) > > + } *( 1 + val ( Length of CTFC Information ) ) + | 001 -- 4bit CTFC + { < Length of CTFC Information: bit (5) > + < 4 bit CTFC : < bit (4) > > + } *( 1 + val ( Length of CTFC Information ) ) + | 010 -- 6bit CTFC + { < Length of CTFC Information: bit (5) > + < 6 bit CTFC : < bit (6) > > + } *( 1 + val ( Length of CTFC Information ) ) + | 011 -- 8bit CTFC + { < Length of CTFC Information: bit (5) > + < 8 bit CTFC : < bit (8) > > + } *( 1 + val ( Length of CTFC Information ) ) + | 100 -- 12bit CTFC + { < Length of CTFC Information: bit (5) > + < 12 bit CTFC : < bit (12) > > + } *( 1 + val ( Length of CTFC Information ) ) + | 101 -- 16bit CTFC + { < Length of CTFC Information: bit (5) > + < 16 bit CTFC : < bit (16) > > + } *( 1 + val ( Length of CTFC Information ) ) + ! < Message escape : { 110 | 111 } bit** = > }; + +``` + +**Table 9.3.128.2: TFCS Reconfiguration/Addition Information information element details** + +### Length of CTFC Information (5 bit field) + +This field is a binary representation of the CTFC Information. Range 0 to maxTFC-1. + +### 2 bit CTFC (2 bit field) + +This field is a binary representation of the CTFC when it is chosen 2 bits representation. Range 0 to 3. + +### 4 bit CTFC (4 bit field) + +This field is a binary representation of the CTFC when it is chosen 4 bits representation. Range 0 to 15. + +### 6 bit CTFC (6 bit field) + +This field is a binary representation of the CTFC when it is chosen 6 bits representation. Range 0 to 255. + +### 8 bit CTFC (8 bit field) + +This field is a binary representation of the CTFC when it is chosen 8 bits representation. Range 0 to 63. + +### 12 bit CTFC (12 bit field) + +This field is a binary representation of the CTFC when it is chosen 12 bits representation. Range 0 to 4095. + +### 16 bit CTFC (16 bit field) + +This field is a binary representation of the CTFC when it is chosen 16 bits representation. Range 0 to 65535. + +### 9.3.129 TFCS Removal Information + +**Table 9.3.129.1: TFCS Removal Information information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< TFCS Removal Information IE > ::=   < Removal TFCI Information : bit (5) >   { < TFCI : < Transport Format Combination IE> } * ( 1 + val ( TFCS Removal Information ) );
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.129.2: TFCS Removal Information information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +|

Removal TFCI information
This field is a binary representation of the removal of TFCs. Range: 1 to maxTFC.

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

TFCI
The IE Transport Format Combination is defined in 9.3.131.

| +|------------------------------------------------------------------------------------------| + +### 9.3.130 Transport Channel Identity + +This IE is used to distinguish transport channels. This also holds for uplink and downlink transport channel identities (i.e. for DCH). Depending on in which context a transport channel identity *n* that is sent, it will have different meaning. + +**Table 9.3.130.1: Transport Channel Identity information element** + +| | +|---------------------------------------------------------------------------------| +| 
< TrCH Identity IE > ::=   < TrCH Identity : bit (3) > ;
| +|---------------------------------------------------------------------------------| + +**Table 9.3.130.2: Transport Channel Identity information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

TrCH Identity (3 bit field)
The Transport Channel Identity field is encoded as a binary number. Range: 0 to maxTrCH-1. 0 enables the TrCH number 1.

| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.131 TFC + +**Table 9.3.131.1: Transport Format Combination information element** + +| | +|---------------------------------------------------------------------------------------------------------------| +| 
< Transport Format Combination IE > ::=   < Transport Format Combination : bit (5) > ;
| +|---------------------------------------------------------------------------------------------------------------| + +**Table 9.3.131.2: Transport Format Combination information element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Transport Format Combination (5 bit field)
The Transport Format Combination field is encoded as a binary number. Range: 0 to maxTFC-1.

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.3.132 Transport Format Combination Set + +This IE indicates the allowed combinations of already defined transport formats and the mapping between these allowed TFCs and the corresponding TFCI values. + +**Table 9.3.132.1: Transport Format Combination Set information elements** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Transport Format Combination Set IE > ::=   < TFCI Field Information : < TFCS Explicit Configuration IE> > ;
| +|---------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.132.2: *Transport Format Combination Set* information element details** + +| | +|---------------------------------------------------------------------------------------------------| +| TFCI Field Information
The TFCS Explicit Configuration IE is defined in 9.3.127. | +|---------------------------------------------------------------------------------------------------| + +## 9.3.133 Transport Format Set + +**Table 9.3.133.1: *Transport Format Set* information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< Transport Format Set IE > ::=   < Transport Format Set length: bit (4) >     -- Transport Channel type; Dedicated transport channels   {     < Dynamic Transport Format Information List: bit (5) >     < RLC Size : bit (11) >     < Transport Block Size : bit (11) > } * (1+val(Dynamic Transport Format Information List) )     < Semi-static Transport Format Information : < Semi-static Transport Format Information IE > > <spare bits> **; --reserved
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.133.2: *Transport Format Set* information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Dynamic Transport Format Information list (5 bit field)
This is the binary representation of the dynamic attribute of the transport channel that is configured with the TFS for the DCH. Range 1 to maxTF. | +| RLC Size (11 bit field)
This is the binary representation of the RLC size needed to configure layer 2. Range 1 to maxRLCSize. | +| Transport Block Size (11 bits field)
This is the binary representation of the transport block size corresponding to the RLC size. Range 1 to maxTBSize. | +| Semi-static Transport Format Information
This IE is described in sub-clause 9.3.126. | + +## 9.3.134 UL TrCH Information Common For All Transport Channels + +**Table 9.3.134.1: *UL TrCH Information Common For All Transport Channels* information elements** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< UL TrCH Information Common For All Transport Channels IE > ::=   < UL DCH TFCS : < Transport Format Combination Set IE > > ;
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 9.3.134.2: *UL TrCH Information Common For All Transport Channels* information element details** + +| | +|--------------------------------------------------------------------------------------------------------| +| DL DCH TFCS
The IE Transport Format Combination Set is defined in sub-clause 9.3.132. | +|--------------------------------------------------------------------------------------------------------| + +## 9.3a Information element definitions + +``` +InformationElements DEFINITIONS AUTOMATIC TAGS ::= + +-- *************************************************** +-- +-- CORE NETWORK INFORMATION ELEMENTS (9.3) +-- +-- *************************************************** + +BEGIN + +IMPORTS +``` + +``` + +maxCNDomains, +maxRBallRABs, +maxRB + +FROM Constant-definitions; + +-- NOTE : for ActivationTime, value 'now' always appear as default, and is encoded +-- by absence of the field + +ActivationTime ::= BIT STRING (SIZE (22)) + +CN-DomainIdentity ::= ENUMERATED { + cs-domain, + ps-domain } + +CN-InformationInfo ::= SEQUENCE { + plmn-Identity PLMN-Identity OPTIONAL, + cn-DomainGSM-MAP-NAS-SysInfo NAS-SystemInformationGSM-MAP OPTIONAL, + cn-DomainRelInfo CN-DomainRelInfo OPTIONAL +} + +CN-DomainRelInfo ::= SEQUENCE { + cn-DomainIdentity CN-DomainIdentity, + cn-DomainGSM-MAP-NAS-SysInfo NAS-SystemInformationGSM-MAP +} + +CellUpdateCause ::= ENUMERATED { + cellReselection, + periodicalCellUpdate, + uplinkDataTransmission, + geran-pagingResponse, + radiolinkFailure, + rlc-unrecoverableError, + invalidRLC-MACcontrolmessage, + spare1 } + +CipheringModeInfo ::= SEQUENCE { + -- NOTE: The ciphering algorithm is included in the CipheringModeCommand. + cipheringModeCommand CipheringModeCommand, + cipheringActivationTimeforDBPSCH ActivationTime OPTIONAL, + rb-DL-CiphActivationTimeInfo RB-ActivationTimeInfoList OPTIONAL +} + +CipheringModeCommand ::= CHOICE { + startRestart CipheringAlgorithm, + spare NULL +} + +CipheringAlgorithm ::= BIT STRING { + -- For each bit value "0" means false/ not supported + spare15(0), + spare14(1), + spare13(2), + spare12(3), + spare11(4), + spare10(5), + spare9(6), + spare8(7), + spare7(8), + spare6(9), + spare5(10), + spare4(11), + spare3(12), + spare2(13), + uea1(14), + uea0(15) +} (SIZE (16)) + +DL-CounterSynchronisationInfo ::= SEQUENCE { + rb-WithPDCP-InfoList RB-WithPDCP-InfoList OPTIONAL, + rb-PDCPContextRelocationList RB-PDCPContextRelocationList OPTIONAL +} + +Digit ::= INTEGER (0..9) + +``` + +``` +FailureCauseWithProtErrTrId ::= SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + failureCause FailureCauseWithProtErr +} + +FailureCauseWithProtErr ::= CHOICE { + configurationUnsupported NULL, + physicalChannelFailure NULL, + incompatibleSimultaneousReconfiguration + NULL, + protocolError ProtocolErrorInformation, + cellUpdateOccurred NULL, + invalidConfiguration NULL, + configurationIncomplete NULL, + spare7 NULL, + spare6 NULL, + spare5 NULL, + spare4 NULL, + spare3 NULL, + spare2 NULL, + spare1 NULL +} + +GRA-Identity ::= BIT STRING (SIZE (16)) + +GRA-UpdateCause ::= ENUMERATED { + changeOfGRA, + periodicGRAUpdate, + spare2, + spare1 } + +GERAN-DRX-CycleLengthCoefficient ::= INTEGER (3..9) + +G-RNTI ::= SEQUENCE { + sbsc-Identity SBSC-Identity, + s-RNTI S-RNTI +} + +IntegrityCheckInfo ::= SEQUENCE { + -- RRC-MessageSequenceNumberList includes RRC-MessageSequenceNumber. + messageAuthenticationCode MessageAuthenticationCode, + rrc-MessageSequenceNumberList RRC-MessageSequenceNumberList +} + +IntegrityProtActivationInfo ::= SEQUENCE { + -- RRC-MessageSequenceNumberList includes RRC-MessageSequenceNumber + rrc-MessageSequenceNumberList RRC-MessageSequenceNumberList +} + +IntegrityProtectionAlgorithm ::= ENUMERATED { + -- For each NULL means false/ not supported + uia1 BIT STRING (SIZE (16)), + spare1 NULL, + spare2 NULL, + spare3 NULL, + spare4 NULL, + spare5 NULL, + spare6 NULL, + spare7 NULL, + spare8 NULL, + spare9 NULL, + spare10 NULL, + spare11 NULL, + spare12 NULL, + spare13 NULL, + spare14 NULL, + spare15 NULL +} + +IntegrityProtectionModeCommand ::= CHOICE { + startIntegrityProtection SEQUENCE { + integrityProtInitNumber IntegrityProtInitNumber + }, + modify SEQUENCE { + dl-IntegrityProtActivationInfo IntegrityProtActivationInfo + } +} +``` + +``` + +IntegrityProtInitNumber ::= BIT STRING (SIZE (32)) + +IntegrityProtectionModeInfo ::= SEQUENCE { + -- NOTE: DL integrity protection activation info and Integrity + -- protection initialisation number have been nested inside + -- IntegrityProtectionModeCommand. + integrityProtectionModeCommand IntegrityProtectionModeCommand, + integrityProtectionAlgorithm IntegrityProtectionAlgorithm OPTIONAL +} + +MessageAuthenticationCode ::= BIT STRING (SIZE (32)) + +MCC ::= SEQUENCE (SIZE (3)) OF + Digit + +MNC ::= SEQUENCE (SIZE (2..3)) OF + Digit + +NAS-SystemInformationGSM-MAP ::= OCTET STRING (SIZE (1..8)) + +PLMN-Identity ::= SEQUENCE { + mcc MCC, + mnc MNC +} + +PDCP-SN-Info ::= INTEGER (0..65535) + +RB-PDCPContextRelocation ::= SEQUENCE { + dl-RFC3095-Context-Relocation BOOLEAN, + ul-RFC3095-Context-Relocation BOOLEAN +} + +RB-PDCPContextRelocationList ::= SEQUENCE (SIZE (1..maxRBallRABs)) OF + RB-PDCPContextRelocation + +ProtocolErrorCause ::= ENUMERATED { + csn1-ViolationOrEncodingError, + messageTypeNonexistent, + messageNotCompatibleWithReceiverState, + ie-ValueNotComprehended, + informationElementMissing, + messageContentPartError, + messageExtensionNotComprehended, + spare2, spare1 } + +ProtocolErrorIndicator ::= CHOICE { + noError NULL, + errorOccurred SEQUENCE { + rrc-TransactionIdentifier RRC-TransactionIdentifier, + protocolErrorInformation ProtocolErrorInformation + } +} + +ProtocolErrorInformation ::= SEQUENCE { + diagnosticsType CHOICE { + type1 SEQUENCE { + protocolErrorCause ProtocolErrorCause + }, + spare NULL + } +} + +Rb-timer-indicator ::= SEQUENCE { + t314-expired BOOLEAN, + t315-expired BOOLEAN } + +RB-ActivationTimeInfoList ::= SEQUENCE (SIZE (1..maxRB)) OF + RB-ActivationTimeInfo + +RB-ActivationTimeInfo ::= SEQUENCE { + rb-Identity RB-Identity, + rlc-SequenceNumber RLC-SequenceNumber } + +RLC-SequenceNumber ::= CHOICE { + rlc-GPRS-SequenceNumber BIT STRING (SIZE (7)), + rlc-EGPRS-SequenceNumber BIT STRING (SIZE (11)), +} + +``` + +``` + + rlc-DCCH-TBFMode-SequenceNumber BIT STRING (SIZE (4)), + rlc-TCH-TBF-SequenceNumber BIT STRING (SIZE (8)) + } + + RB-Identity := INTEGER (1..32) + + RB-WithPDCP-Info := SEQUENCE { + rb-Identity RB-Identity, + pdcp-SN-Info PDCP-SN-Info + } + + RB-WithPDCP-InfoList := SEQUENCE (SIZE (1..maxRBallRABs)) OF + RB-WithPDCP-Info + + RRC-MessageSequenceNumber := INTEGER (0..15) + + RRC-MessageSequenceNumberList := SEQUENCE (SIZE (4..5)) OF + RRC-MessageSequenceNumber + + RRC-TransactionIdentifier := INTEGER (0..3) + + RRC-StateIndicator := ENUMERATED { + rrc-Cell-Dedicated, rrc-Cell-Shared, rrc-GRAPCH} + + SBSC-Identity := BIT STRING (SIZE (12)) + + S-RNTI := BIT STRING (SIZE (20)) + + START-Value := BIT STRING (SIZE (20)) + + STARTList := SEQUENCE (SIZE (1..maxCNdomains)) OF + STARTSingle + + STARTSingle := SEQUENCE { + cn-DomainIdentity CN-DomainIdentity, + start-Value START-Value + } + +END + +``` + +## 9.4 Multiplicity values and type constraint values + +The following table includes constants that are either used as multi bounds (name starting with "max") or as high or low value in a type specification (name starting with "lo" or "hi"). Constants are specified only for values appearing more than once in the RRC specification. In case a constant is related to one or more other constants, an expression is included in the "value" column instead of the actual value. + +**Table 9.4.1: Multiplicity values and type constraint values** + +| Constant | Explanation | Value | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------| +| CN information | | | +| maxCNDomains | Maximum number of CN domains | 4 | +| MS information | | | +| maxTransactions | Maximum number of parallel RRC transactions in downlink | 25 | +| maxPDCPAlgoType | Maximum number of PDCP algorithm types | 8 | +| maxSystemCapability | Maximum number of system specific capabilities that can be requested in one message. | 16 | +| maxTBF | Maximum number of TBFs | 8 | +| GERAN mobility information | | | +| maxRAT | Maximum number of Radio Access Technologies | maxOtherRAT + 1 | +| maxOtherRAT | Maximum number of other Radio Access Technologies | 15 | +| maxGRA | Maximum number of GRAs in a cell | 8 | +| maxInterSysMessages | Maximum number of Inter System Messages | 4 | +| maxRABsetup | Maximum number of RABs to be established | 16 | +| RB information | | | +| maxRB | Maximum number of RBs | 32 | +| maxRBallRABs | Maximum number of non signalling RBs | 27 | +| maxRBperRAB | Maximum number of RBs per RAB | 8 | +| maxSRBsetup | Maximum number of signalling RBs to be established | 8 | +| maxRFC3095-CID | Maximum number of available CID values per radio bearer | 16384 | +| Transport Channel Information | | | +| maxTrCH | Maximum number of transport channels | 8 | +| maxTF | Maximum number of different transport formats that can be included in the Transport format set for one transport channel | 32 | +| maxTFC | Maximum number of Transport Format Combinations | 32 | +| maxTBSize | Maximum number of Transport Block Size | 1370 | +| maxRLCSize | Maximum number of RLC Size | 1370 | +| N | Maximum number of Timeslot Number in DL | 8 | +| M | Maximum number of Timeslot Number in UL | 8 | +| Other information | | | +| maxNumGSMFreqRanges | Maximum number of GSM Frequency Ranges to store | 32 | +| maxNumFDDFreqs | Maximum number of FDD centre frequencies to store | 8 | +| maxNumTDDFreqs | Maximum number of TDD centre frequencies to store | 8 | +| maxNumCDMA200Freqs | Maximum number of CDMA2000 centre frequencies to store | 8 | + +## 9.4a Constant definitions + +Constant-definitions DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` + +maxCNDomains INTEGER ::= 4 +maxRBallRABs INTEGER ::= 27 +maxRB INTEGER ::= 32 + +``` + +END + +## 10 Protocol timers, counters, other parameters and default configurations + +### 10.1 Timers for MS + +**Table 10.1.1: Timers for MS** + +| Timer | Start | Stop | At expiry | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T300 | Started when the transmission of RRC CONNECTION REQUEST is indicated as successfully delivered by RLC | Reception of RRC CONNECTION SETUP | Retransmit RRC CONNECTION REQUEST if V300 <= N300, else go to Idle mode. Its value is 7s. | +| T302 | Started when the transmission of CELL UPDATE/GRA UPDATE is indicated as successfully delivered by RLC | Reception of CELL UPDATE CONFIRM/URA UPDATE CONFIRM | Retransmit CELL UPDATE/GRA UPDATE if V302 <= N302, else, go to Idle mode. Its value is 7s. | +| T304 | Started when the transmission of MS CAPABILITY INFORMATION is indicated as successfully delivered by RLC | Reception of MS CAPABILITY INFORMATION CONFIRM | Retransmit MS CAPABILITY INFORMATION if V304 <= N304, else initiate a cell update procedure. Its value is 7s. | +| T305 | Entering RRC- CELL_Shared or GRA_PCH Reception of CELL UPDATE CONFIRM/URA UPDATE CONFIRM. | Entering another state. | Transmit CELL UPDATE or GRA UPDATE. See sub-clause 7.8 | +| T314 | When the criteria for radio link failure are fulfilled. The timer is started only if radio bearer(s) that are associated with T314 exist. | When the Cell Update procedure has been completed. | See sub-clause 7.8. | +| T315 | When the criteria for radio link failure are fulfilled. The timer is started only if radio bearer(s) that are associated with T315 exist. | When the Cell Update procedure has been completed. | See sub-clause 7.8. | +| T3124 | At the start point of the timeslot in which the HANDOVER ACCESS message is sent the first time | When PHYSICAL INFORMATION message has been received | Its value is set to 675 ms if the channel type of the channel allocated in the RADIO BEARER RECONFIGURATION COMPLETE message is a DBPSCH/S; otherwise its value is set to 320 ms. | +| T3148 | Started after the GERAN Iu mode DTM REQUEST message transmission is indicated as successfully delivered by RLC | When the RADIO BEARER RECONFIGURATION message or GERAN Iu mode DTM REJECT message is received | Its value is 4 seconds. At expiry the mobile station shall reinitiate DTM Request procedure. | + +### 10.1a Timers on the network side + +**Table 10.1a.1: Timers on the network side** + +| Timer | Start | Stop | Action at expiry | Typical Value | +|-------|------------------------------------------------------------|----------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------| +| T3143 | After having sent the sent of PHYSICAL INFORMATION message | Reception of the RADIO BEARER RECONFIGURATION COMPLETE message | Indicate to the RLC sublayer to send once more PHYSICAL INFORMATION message | Its value is network dependent | + +## 10.2 Counters for MS + +**Table 10.2.1: Counters for MS** + +| Counter | Reset | Incremented | When reaching max value | +|---------|------------------------------------------------------------|----------------------|-------------------------------------------------------------| +| V300 | When initiating the procedure RRC connection establishment | Upon expiry of T300. | When V300 > N300, the MS enters on RRC-Idle mode. | +| V302 | When initiating the procedure Cell update or GRA update | Upon expiry of T302 | When V302 > N302 the MS enters in RRC-Idle mode. | +| V304 | When sending the first MS CAPABILITY INFORMATION message. | Upon expiry of T304 | When V304 > N304 the MS initiates the Cell update procedure | + +## 10.3 MS constants and parameters + +**Table 10.3.1: MS constants and parameters** + +| Constant | Usage | +|----------|---------------------------------------------------------------------------------------------| +| N300 | Maximum number of retransmissions of the RRC CONNECTION REQUEST message. Its value is 3. | +| N302 | Maximum number of retransmissions of the CELL UPDATE / URA UPDATE message. Its value is 3. | +| N304 | Maximum number of retransmissions of the MS CAPABILITY INFORMATION message. Its value is 2. | + +## 10.3a Network constants and parameters + +**Table 10.3a.1: Network constants and parameters** + +| Constant | Usage | +|----------|-----------------------------------------------------------------------| +| N3143 | Maximum number of retransmissions of the PHYSICAL INFORMATION message | + +## 10.4 MS variables + +### 10.4.0 General + +**Table 10.4.0.1: MS variables** + +| Name of the Variable | Usage | +|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CELL_UPDATE_STARTED | This variable indicates whether a cell update or GRA update procedure is in progress. | +| CIPHERING_STATUS | This variable contains information about the current status of ciphering in the MS. | +| ESTABLISHED_SIGNALLING_CONNECTIONS | This variable is used to store information about established signalling connections. | +| ESTABLISHMENT_CAUSE | This variable is used to store the cause for establishment of a signalling connection received by upper layers, to be used at RRC connection establishment. | +| ESTABLISHED_RABS | This variable is used to store information about the established radio access bearers and signalling radio bearers in the MS. | + +| | | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FAILURE_CAUSE | This variable contains the cause for failure of a MS initiated procedure, to be reported in a retransmitted message. | +| FAILURE_INDICATOR | This variable indicates whether the procedure has failed for a MS initiated procedure. | +| GRA_IDENTITY | This variable stores the assigned GRA identity for this MS when in RRC-GRA_PCH state. | +| G_RNTI | This variable stores the assigned G-RNTI for this MS. | +| INITIAL_MS_IDENTITY | In this variable the identity used by the MS when establishing an RRC connection is stored. | +| INCOMPATIBLE_SECURITY_RECONFIGURATION | This variable indicates whether an incompatible simultaneous reconfiguration of a security function has been received | +| INTEGRITY_PROTECTION_ACTIVATION_INFO | This variable contains information to be sent to GERAN about when a new integrity protection configuration shall be activated in the uplink for signalling radio bearers in case of modification of integrity protection. | +| INTEGRITY_PROTECTION_INFO | This variable contains information about the current status of the integrity protection in the MS. | +| LATEST_CONFIGURED_CN_DOMAIN | This variable stores the CN-domain that was most recently configured to be used for ciphering and integrity protection. | +| MS_CAPABILITY_REQUESTED | This variable stores information about the MS capabilities that have been requested by GERAN but that have not yet been transferred to GERAN | +| INVALID_CONFIGURATION | This variable indicates whether a received message contained an invalid configuration, by means of invalid values or invalid combinations of information elements | +| MS_CAPABILITY_TRANSFERRED | This variable stores information about which UE capabilities that have been transferred to GERAN. | +| ORDERED_RECONFIGURATION | This variable stores information about an ongoing Reconfiguration procedure. | +| PDCP_SN_INFO | This variable contains PDCP receive sequence numbers for one or several radio bearers to be included in a response message to GERAN. | +| PROTOCOL_ERROR_INDICATOR | This variable indicates whether there exist a protocol error that is to be reported to GERAN. | +| PROTOCOL_ERROR_INFORMATION | This variable contains diagnostics to be reported to GERAN for a message that was not completely understood. | +| PROTOCOL_ERROR_REJECT | This variable indicates whether there has occurred a severe protocol error causing the ongoing procedure to fail. | +| RB_TIMER_INDICATOR | This variable contains information to be sent to GERAN if any of the timers T314 or T315 has expired when the MS sends a cell update with cause RL failure. | +| RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO | This variable contains information to be sent to GERAN about when a new ciphering configuration shall be activated in the uplink for radio bearers using RLC-AM or RLC-UM. | + +| | | +|---------------------------|---------------------------------------------------------------------------------------------------------------| +| SECURITY_MODIFICATION | This variable contains information on which CN domain is affected by the ongoing security reconfiguration. | +| START_THRESHOLD | This variable contains information about the maximum allowed value of the START for a CN domain. | +| START_VALUE_TO_TRANSMIT | This variable contains the value of START for new radio bearer(s) to be transmitted in a response message | +| TRANSACTIONS | This variable stores the identifications of the ongoing RRC procedure transactions. | +| TIMERS_AND_CONSTANTS | This variable contains the values for all timers and constants used in RRC-Connected mode. | +| UNSUPPORTED_CONFIGURATION | This variable indicates whether a received message contained a configuration that is not supported by the MS. | + +## 10.4.1 CELL\_UPDATE\_STARTED + +This variable indicates whether a cell update or GRA update procedure is in progress. + +**Table 10.4.1.1: CELL\_UPDATE\_STARTED Variable** + +``` +< CELL_UPDATE_STARTED VAR > ::= + < Cell Update Started : bit (1) > ; +``` + +**Table 10.4.1.2: CELL\_UPDATE\_STARTED Variable details** + +### Cell Update Started (1 bit field) + +bit + 1 + 0 False - when leaving or entering the RRC Connected Mode + 1 True - a Cell or GRA Update procedure is in progress + +## 10.4.2 CIPHERING\_STATUS + +This variable contains information about the current status of ciphering in the MS. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable. + +**Table 10.4.2.1: CIPHERING\_STATUS Variable** + +``` +< CIPHERING_STATUS VAR > ::= + < CN Domain Related Information List : bit (2) > + { < CN Domain Identity : < CN Domain Identity IE > > + < Status : bit (1) > + < Reconfiguration : bit (1) > + } * (1+val(CN Domain Related Information List)) ; +``` + +**Table 10.4.2.2: CIPHERING\_STATUS Variable details** + +### CN Domain Related Information List (2 bit field) + +This field is used to repeat information for each CN Domain. Range : 0 to maxCNdomains-1, where 0 enables one CN domain to be described. + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CN Domain Identity
The CN Domain Identity IE is defined in sub-clause 9.3.15. | +| Status (1 bit field)
bit
1
0 Not Started - when leaving the RRC-Connected mode
1 Started - when entering the RRC-Connected mode | +| Reconfiguration (1 bit field)
bit
1
0 False - when leaving or entering the RRC Connected Mode
1 True - an RRC procedure performing reconfiguration of ciphering is ongoing | + +## 10.4.3 ESTABLISHED\_SIGNALLING\_CONNECTIONS + +This variable is used to store information about established signalling connections. This variable is cleared when entering the RRC Connected Mode when not otherwise stated in the procedure or when leaving the RRC Connected Mode. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable. + +**Table 10.4.3.1: ESTABLISHED\_SIGNALLING\_CONNECTIONS Variable** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< ESTABLISHED_SIGNALLING_CONNECTIONS VAR > ::= { 0   1 < Signalling Connection List : bit (2) >   < CN Domain Identity : < CN Domain Identity IE > > * (1+ val(Signalling Connection List)) };
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.3.2: ESTABLISHED\_SIGNALLING\_CONNECTIONS Variable details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signalling Connection List (2 bit field)
This field is used to repeat the CN domain identity of CN domains with established signalling connection. Range : 0 to maxCNdomains-1, where 0 enables one CN domain with established signalling connection to be described. | +| CN Domain Identity
The CN Domain Identity IE is defined in sub-clause 9.3.15. | + +## 10.4.4 ESTABLISHMENT\_CAUSE + +This variable is used to store the cause for establishment of a signalling connection received by upper layers, to be used at RRC connection establishment. This variable is cleared when entering or leaving the RRC Connected Mode. + +**Table 10.4.4.1: ESTABLISHMENT\_CAUSE Variable** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------| +| 
< ESTABLISHMENT_CAUSE VAR > ::= { 0   1 < Establishment Cause : < Establishment Cause IE > > };
| +|-------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.4.2: ESTABLISHMENT\_CAUSE Variable details** + +| | +|------------------------------------------------------------------------| +| Establishment Cause
This IE is defined in sub-clause 9.3.21. | +|------------------------------------------------------------------------| + +## 10.4.5 ESTABLISHED\_RABS + +This variable is used to store information about the established radio access bearers and signalling radio bearers in the MS. This variable is cleared when entering or leaving the RRC Connected Mode. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable. + +**Table 10.4.5.1: ESTABLISHED\_RABS Variable** + +``` +< ESTABLISHED_RABS VAR > ::= +{ + { 0 -- Not present when entering or leaving the RRC-Connected mode when not otherwise stated in the procedure + | 1 < RAB Information List :bit (4) > + { + < RAB Info : < RAB Info IE > > + < RB Information List : bit (3) > + { + < RB Identity : < RB Identity IE > > + < RB Started : bit (1) > } * (1+val(RB Information List)) + } * (1+val (RAB Information List)) + } + { 0 -- Not present when leaving RRC-Connected mode + | 1 < Signalling RB Information List : bit (3) > + < Signalling RB Started : bit (1) >* (1+val(Signalling RB Information List)) } +}; +``` + +**Table 10.4.5.2: ESTABLISHED\_RABS Variable details** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RAB Information List (4 bit field)

This field is used to repeat information for each RAB established. Range : 0 to maxRABsetup-1, where 0 enables one established RAB to be described.

| +|

RAB Info

The RAB Info IE is defined in sub-clause 9.3.73.

| +|

RB Information List (3 bit field)

This field is used to repeat information for each RB of the RAB. Range : 0 to maxRBperRAB-1, where 0 enables one RB to be described.

| +|

RB Identity

This IE is defined in sub-clause 9.3.80.

| +|

RB Started ( 1 bit field)

bit
1
0 Stopped
1 Started – default value

| +|

Signalling RB Information List (3 bit field)

This field is used to repeat information for each SRB. Range : 0 to maxSRBsetup-1, where 0 enables one SRB to be described.

| +|

Signalling RB Started (1 bit field)

Field repeated in the order of Signalling RB1 and upwards.

bit
1
0 Stopped
1 Started – default value.

| + +## 10.4.6 FAILURE\_CAUSE + +This variable contains the cause for failure of a MS initiated procedure, to be reported in a retransmitted message. This variable is cleared when entering or leaving the RRC Connected Mode. + +**Table 10.4.6.1: FAILURE\_CAUSE Variable** + +| | +|------------------------------------------------------------------------------------------------------------| +| 
< FAILURE_CAUSE VAR > ::= { 0   1 < Failure Cause : < Failure Cause IE > > };
| +|------------------------------------------------------------------------------------------------------------| + +**Table 10.4.6.2: FAILURE\_CAUSE Variable details** + +| | +|----------------------------------------------------------------------------------------------| +|

Failure Cause
The Failure Cause IE is defined in sub-clause 9.3.24.

| +|----------------------------------------------------------------------------------------------| + +## 10.4.7 FAILURE\_INDICATOR + +This variable indicates whether the procedure has failed for a MS initiated procedure. + +**Table 10.4.7.1: FAILURE\_INDICATOR Variable** + +| | +|---------------------------------------------------------------------------------------| +| 
< FAILURE_INDICATOR VAR > ::= < Failure Indicator : bit(1) > ;
| +|---------------------------------------------------------------------------------------| + +**Table 10.4.7.2: FAILURE\_INDICATOR Variable details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Failure Indicator ( 1 bit field)

bit

1

0 False - when entering or leaving the RRC-Connected mode.

1 True - Procedure has failed.

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 10.4.8 GRA\_IDENTITY + +This variable stores the assigned GRA identity for this MS when in RRC-GRA\_PCH state. This variable is cleared when entering or leaving the RRC Connected Mode. + +**Table 10.4.8.1: GRA\_IDENTITY Variable** + +| | +|---------------------------------------------------------------------------------------------------------| +| 
< GRA_IDENTITY VAR > ::= { 0   1 < GRA Identity : < GRA Identity IE > > };
| +|---------------------------------------------------------------------------------------------------------| + +**Table 10.4.8.2: GRA\_IDENTITY Variable details** + +| | +|-------------------------------------------------------------------------| +|

GRA Identity
This IE is defined in sub-clause 9.3.30.

| +|-------------------------------------------------------------------------| + +## 10.4.9 G\_RNTI + +This variable stores the assigned G-RNTI for this MS. This variable is cleared when leaving the RRC-Connected mode. + +**Table 10.4.9.1: G\_RNTI Variable** + +| | +|---------------------------------------------------------------------------------------| +| 
< G_RNTI VAR > ::= { 0   1 < G-RNTI : < G-RNTI IE > > };
| +|---------------------------------------------------------------------------------------| + +**Table 10.4.9.2: G\_RNTI Variable details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

G-RNTI

This IE is defined in sub-clause 9.3.32. Not present when leaving the RRC-Connected mode.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**10.4.10 INITIAL\_MS\_IDENTITY** + +In this variable the identity used by the MS when establishing an RRC connection is stored. + +**Table 10.4.10.1: INITIAL\_MS\_IDENTITY Variable** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< INITIAL_MS_IDENTITY VAR > ::= { 0   1 < Initial MS Identity : < Initial MS Identity IE > > } ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.10.2: INITIAL\_MS\_IDENTITY Variable details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Initial MS Identity

This IE is defined in sub-clause 9.3.35. Not present when leaving the RRC-Connected mode.

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**10.4.11 INCOMPATIBLE\_SECURITY\_RECONFIGURATION** + +This variable indicates whether an incompatible simultaneous reconfiguration of a security function has been received. + +**Table 10.4.11.1: INCOMPATIBLE\_SECURITY\_RECONFIGURATION Variable** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< INCOMPATIBLE_SECURITY_RECONFIGURATION VAR > ::= < Incompatible Security Reconfiguration : bit(1) > ;
| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.11.2: INCOMPATIBLE\_SECURITY\_RECONFIGURATION Variable details** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Incompatible Security Reconfiguration (1 bit field)

bit

1

0 False - when entering or leaving the RRC-Connected mode.

1 True – when an incompatible simultaneous security reconfiguration has been detected.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**10.4.12 INTEGRITY\_PROTECTION\_ACTIVATION\_INFO** + +This variable contains information to be sent to GERAN about when a new integrity protection configuration shall be activated in the uplink for signalling radio bearers in case of modification of integrity protection. This variable is cleared when entering or leaving the RRC-Connected mode. When performing handover to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover from UTRAN the value of this variable is transferred from the corresponding UTRAN variable. + +**Table 10.4.12.1: INTEGRITY\_PROTECTION\_ACTIVATION\_INFO Variable** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< INTEGRITY_PROTECTION_ACTIVATION_INFO VAR > ::= { 0   1 < Uplink Integrity Protection Activation Info : < Integrity Protection Activation Info IE > > } ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.12.2: INTEGRITY\_PROTECTION\_ACTIVATION\_INFO Variable details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Integrity Protection Activation Info

This IE is defined in sub-clause 9.3.37.

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 10.4.13 INTEGRITY\_PROTECTION\_INFO + +This variable contains information about the current status of the integrity protection in the MS. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable. + +**Table 10.4.13.1: INTEGRITY\_PROTECTION\_INFO Variable** + +``` +< INTEGRITY_PROTECTION_INFO VAR > ::= +{ + < Historical Status : bit (1) > + < Status : bit (1) > + < Reconfiguration : bit (1) > + { 0 -- Cleared when entering or leaving the RRC-Connected mode + | 1 < Signalling RB Specific Integrity Protection Information List : bit (3) > + { -- Signalling SRB1 and upwards + < Uplink RRC HFN : bit (28) > + < Downlink RRC HFN : bit (28) > + < Uplink RRC Message Sequence Number : bit (4) > + { 0 | 1 < Downlink RRC Message Sequence Number : bit (4) > } + } * (1+val(Signalling RB Specific Integrity Protection Information List)) +} +}; +``` + +**Table 10.4.13.2: INTEGRITY\_PROTECTION\_INFO Variable details** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Historical Status (1 bit field)

bit

1

0 Never been active – set when entering the RRC-Connected mode

1 Has been active

| +|

Status (1 bit field)

bit

1

0 Not Started - when leaving the RRC-Connected mode

1 Started - when entering the RRC-Connected mode

| +|

Reconfiguration (1 bit field)

bit

1

0 False - when leaving or entering the RRC Connected Mode

1 True - an RRC procedure performing reconfiguration of ciphering is ongoing

| +|

Signalling RB Specific Integrity Protection Information List (3 bit field)

This field is used to repeat information for each SRB with specific integrity protection information. Range : 0 to maxSRBsetup-1, where 0 enables one SRB with specific integrity protection information to be described.

| +|

Uplink RRC HFN (28 bit field)

Downlink RRC HFN (28 bit field)

The field indicates the RRC HFN.

| +|

Uplink RRC Message Sequence Number (4 bit field)

Downlink RRC Message Sequence Number (4 bit field)

This field is the binary representation of the sequence number of the RRC message. Range 0 to 15.

| + +## 10.4.14 INVALID\_CONFIGURATION + +This variable indicates whether a received message contained an invalid configuration, by means of invalid values or invalid combinations of information elements. + +**Table 10.4.14.1: INVALID\_CONFIGURATION Variable** + +``` +< INVALID_CONFIGURATION VAR > ::= + < Invalid Configuration : bit(1) > ; +``` + +**Table 10.4.14.2: INVALID\_CONFIGURATION Variable details** + +### Invalid Configuration (1 bit field) + +bit + 1 + 0 False - when entering or leaving the RRC-Connected mode. + 1 True – an invalid configuration has been detected + +## 10.4.14a LATEST\_CONFIGURED\_CN\_DOMAIN + +This variable stores the CN-domain that was most recently configured to be used for ciphering and integrity protection. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable + +**Table 10.4.14a.1: LATEST\_CONFIGURED\_CN\_DOMAIN Variable** + +``` +< LATEST_CONFIGURED_CN_DOMAIN VAR > ::= + { 0 | 1 < Latest configured CN domain : < CN Domain Identity IE > > } ; +``` + +**Table 10.4.14a.2: LATEST\_CONFIGURED\_CN\_DOMAIN Variable details** + +### Latest configured CN domain + +The *CN Domain Identity* IE is defined in sub-clause 9.3.15. The variable is cleared when entering GERAN RRC connected mode when not stated otherwise in the procedure or when leaving GERAN RRC connected mode. + +## 10.4.15 MS\_CAPABILITY\_REQUESTED + +This variable stores information about the MS/UE capabilities that have been requested by GERAN but that have not yet been transferred to GERAN. This variable is cleared when entering or leaving the RRC-Connected mode. + +**Table 10.4.15.1: MS\_CAPABILITY\_REQUESTED Variable** + +``` +< MS_CAPABILITY_REQUESTED VAR > ::= + < MS GERAN Iu mode Radio Access Capability : < MS GERAN Iu mode Radio Access Capability IE > > + { 0 | 1 < MS GERAN A/Gb mode Radio Access Capability : < MS GERAN A/Gb mode Radio Access Capability IE > > } + { 0 | 1 < UE UTRAN Radio Access Capability : < UE UTRAN Radio Access Capability IE > > } + { 0 | 1 < UE UTRAN Radio Access Capability Extension : < UE UTRAN Radio Access Capability Extension IE > > } + { 0 | 1 < UE CDMA2000 Radio Access Capability : < UE CDMA2000 Radio Access Capability IE > > } ; +``` + +**Table 10.4.15.2: MS\_CAPABILITY\_REQUESTED Variable details** + +### MS GERAN Iu mode Radio Access Capability + +This IE is defined in sub-clause 9.3.45. + +### MS GERAN A/Gb mode Radio Access Capability + +This IE is defined in sub-clause 9.3.44. + +| | +|------------------------------------------------------------------------------------------------| +| UE UTRAN Radio Access Capability
This IE is defined in sub-clause 9.3.108. | +| UE UTRAN Radio Access Capability Extension
This IE is defined in sub-clause 9.3.109. | +| UE CDMA2000 Radio Access Capability
This IE is defined in sub-clause 9.3.110. | + +## 10.4.16 MS\_CAPABILITY\_TRANSFERRED + +This variable stores information about which UE/MS capabilities that have been transferred to GERAN. This variable is cleared when entering or leaving the RRC-Connected mode when not stated otherwise in the procedure. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable. + +**Table 10.4.16.1: MS\_CAPABILITY\_TRANSFERRED Variable** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < MS_CAPABILITY_TRANSFERRED VAR > ::=   < MS GERAN Iu mode Radio Access Capability : < MS GERAN Iu mode Radio Access Capability IE > >   { 0   1 < MS GERAN A/Gb mode Radio Access Capability : < MS GERAN A/Gb mode Radio Access Capability IE   > > }   { 0   1 < UE UTRAN Radio Access Capability : < UE UTRAN Radio Access Capability IE > > }   { 0   1 < UE UTRAN Radio Access Capability Extension : < UE UTRAN Radio Access Capability Extension IE > > }   { 0   1 < UE CDMA2000 Radio Access Capability : < UE CDMA2000 Radio Access Capability IE > > } ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.16.2: MS\_CAPABILITY\_TRANSFERRED Variable details** + +| | +|------------------------------------------------------------------------------------------------| +| MS GERAN Iu mode Radio Access Capability
This IE is defined in sub-clause 9.3.45. | +| MS GERAN A/Gb mode Radio Access Capability
This IE is defined in sub-clause 9.3.44. | +| UE UTRAN Radio Access Capability
This IE is defined in sub-clause 9.3.108. | +| UE UTRAN Radio Access Capability Extension
This IE is defined in sub-clause 9.3.109. | +| UE CDMA2000 Radio Access Capability
This IE is defined in sub-clause 9.3.110. | + +## 10.4.17 ORDERED\_RECONFIGURATION + +This variable stores information about an ongoing Reconfiguration procedure. + +**Table 10.4.17.1: ORDERED\_RECONFIGURATION Variable** + +| | +|--------------------------------------------------------------------------------------------------------| +| 
 < ORDERED_RECONFIGURATION VAR > ::=   < Ordered reconfiguration : bit (1) > ;
| +|--------------------------------------------------------------------------------------------------------| + +**Table 10.4.17.2: ORDERED\_RECONFIGURATION Variable details** + +| | +|------------------------------------------------------------------------| +| Ordered reconfiguration (1 bit field) | +| bit
1
0 False - when entering or leaving the RRC-Connected mode. | + +| | +|------------------------------------------------| +| 1 True – reconfiguration procedure is ongoing. | +|------------------------------------------------| + +## 10.4.18 PDCP\_SN\_INFO + +This variable contains PDCP receive sequence numbers for one or several radio bearers to be included in a response message to GERAN. This variable is cleared when entering or leaving the RRC-Connected mode. + +**Table 10.4.18.1: PDCP\_SN\_INFO Variable** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| < PDCP_SN_INFO VAR > ::=
{ 0 1 < RB with PDCP Information List : bit (5) >
  < RB with PDCP Information : < RB with PDCP Information IE > > * (1 + val(RB with PDCP Information List) ) }; | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.18.2: PDCP\_SN\_INFO Variable details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RB with PDCP Information List (5 bit field) | +| This field used to repeat information for each RB with PDCP Information. Range : 0 to maxRBallRABs-1, where 0 enables one RB with PDCP Information to be described. Other values are reserved. | +| RB with PDCP Information | +| This IE is defined in sub-clause 9.3.86. | + +## 10.4.19 PROTOCOL\_ERROR\_INDICATOR + +This variable indicates whether there exist a protocol error that is to be reported to GERAN. This variable is cleared when entering or leaving the RRC-Connected mode. + +**Table 10.4.19.1: PROTOCOL\_ERROR\_INDICATOR Variable** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------| +| < PROTOCOL_ERROR_INDICATOR VAR > ::=
< Protocol Error Indicator : < Protocol Error Indicator IE > > ; | +|-------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.19.2: PROTOCOL\_ERROR\_INDICATOR Variable details** + +| | +|------------------------------------------| +| Protocol Error Indicator | +| This IE is defined in sub-clause 9.3.70. | + +## 10.4.20 PROTOCOL\_ERROR\_INFORMATION + +This variable contains diagnostics to be reported to GERAN for a message that was not completely understood. This variable is cleared when entering or leaving the RRC-Connected mode. + +**Table 10.4.20.1: PROTOCOL\_ERROR\_INFORMATION Variable** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| < PROTOCOL_ERROR_INFORMATION VAR > ::=
{ 0 1 < Protocol Error Information: < Protocol Error Information IE > > }; | +|---------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 10.4.20.2: PROTOCOL\_ERROR\_INFORMATION Variable details** + +| | +|------------------------------------------| +| Protocol Error Information | +| This IE is defined in sub-clause 9.3.71. | + +## 10.4.21 PROTOCOL\_ERROR\_REJECT + +This variable indicates whether there has occurred a severe protocol error causing the ongoing procedure to fail. + +**Table 10.4.21.1: PROTOCOL\_ERROR\_REJECT Variable** + +``` +< PROTOCOL_ERROR_REJECT VAR > ::= + < Protocol Error Reject : bit (1) > ; +``` + +**Table 10.4.21.2: PROTOCOL\_ERROR\_REJECT Variable details****Protocol Error Reject (1 bit field)** + +bit + +1 + +0 False - when entering or leaving the RRC-Connected mode. + +1 True - a severe protocol error has occurred. + +## 10.4.22 RB\_TIMER\_INDICATOR + +This variable contains information to be sent to GERAN if any of the timers T314 or T315 has expired when the MS sends a cell update with cause RL failure. This variable is cleared when entering or leaving the RRC-Connected mode. + +**Table 10.4.22.1: RB\_TIMER\_INDICATOR Variable** + +``` +< RB_TIMER_INDICATOR VAR > ::= + { 0 | 1 < RB Timer Indicator : < RB Timer Indicator IE > > } ; +``` + +**Table 10.4.22.2: RB\_TIMER\_INDICATOR Variable details****RB Timer Indicator** + +This IE is defined in sub-clause 9.3.85. + +## 10.4.23 RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO + +This variable contains information to be sent to GERAN about when a new ciphering configuration shall be activated in the uplink for radio bearers using RLC-AM or RLC-UM. This variable is cleared when entering or leaving the RRC-Connected mode. + +**Table 10.4.23.1: RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO Variable** + +``` +< RB_UPLINK_CIPHERING_ACTIVATION_TIME_INFO VAR > ::= + { 0 | 1 < RB Uplink Ciphering Activation Time Info : < RB Uplink Ciphering Activation Time Info IE > > } ; +``` + +**Table 10.4.23.2: RB\_UPLINK\_CIPHERING\_ACTIVATION\_TIME\_INFO Variable details****RB Uplink Ciphering Activation Time Info** + +This IE is defined in sub-clause 9.3.77. + +## 10.4.24 START\_THRESHOLD + +This variable contains information about the maximum allowed value of the START for a CN domain. This variable is cleared when entering or leaving the RRC-Connected mode. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable + +**Table 10.4.24.1: START\_THRESHOLD Variable** + +``` +< START_THRESHOLD VAR > ::= + { 0 | 1 < Threshold : bit (20) > } ; +``` + +**Table 10.4.24.2: START\_THRESHOLD Variable details****Threshold** (20 bit field) + +This field is the binary representation of maximum allowed value of the START for a CN domain. Range: 0 to 1048575. + +## 10.4.25 START\_VALUE\_TO\_TRANSMIT + +This variable contains the value of START for new radio bearer(s) to be transmitted in a response message. This variable is cleared when entering or leaving the RRC-Connected mode. When performing handover or cell reselection to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover or cell reselection from UTRAN the value of this variable is transferred from the corresponding UTRAN variable + +**Table 10.4.25.1: START\_VALUE\_TO\_TRANSMIT Variable** + +``` +< START_VALUE_TO_TRANSMIT VAR > ::= +{ 0 | 1 < START : < START IE > > }; +``` + +**Table 10.4.25.2: START\_VALUE\_TO\_TRANSMIT Variable details****START** + +This IE is defined in sub-clause 9.3.102. + +## 10.4.26 TRANSACTIONS + +This variable stores the identifications of the ongoing RRC procedure transactions. This variable is cleared when leaving the RRC Connected mode. + +**Table 10.4.26.1: TRANSACTIONS Variable** + +``` +< TRANSACTIONS VAR > ::= +{ 0 | 1 < Accepted Transactions List : bit (5) > + { < Message Type : < Message Type IE > > + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + } * (1+val(Accepted Transactions List)) +} +{ 0 | 1 < Rejected Transactions List : bit (5) > + { < Message Type : < Message Type IE > > + < RRC Transaction Identifier : < RRC Transaction Identifier IE > > + } * (1+val(Rejected Transactions List)) +}; +``` + +**Table 10.4.26.2: TRANSACTIONS Variable details****Accepted Transactions List** (5 bit field)**Rejected Transactions List** (5 bit field) + +These fields are used to repeat information for each accepted or rejected transactions respectively. Range: 0 to maxTransactions-1, where 0 enables one transaction to be described. + +**Message Type** + +This IE is defined in sub-clause 9.2.1. + +**RRC Transaction Identifier** + +This IE is defined in sub-clause 9.3.98. + +## 10.4.27 TIMERS\_AND\_CONSTANTS + +This variable contains the values for all timers and constants used in RRC-Connected mode. + +**Table 10.4.27.1: TIMERS\_AND\_CONSTANTS Variable** + +``` +< TIMERS_AND_CONSTANTS VAR > ::= + < MS Timers and Constants In Connected Mode : < MS Timers and Constants In Connected Mode IE > > ; +``` + +**Table 10.4.27.2: TIMERS\_AND\_CONSTANTS Variable details** + +### MS Timers and Constants In Connected Mode + +This IE is defined in sub-clause 9.3.51. All parameters are set to the default value when leaving the GERAN Iu to another RAT. + +## 10.4.28 UNSUPPORTED\_CONFIGURATION + +This variable indicates whether a received message contained a configuration that is not supported by the MS. + +**Table 10.4.27.1: UNSUPPORTED\_CONFIGURATION Variable** + +``` +< UNSUPPORTED_CONFIGURATION VAR > ::= + < Unsupported Configuration : bit (1) > ; +``` + +**Table 10.4.27.2: UNSUPPORTED\_CONFIGURATION Variable details** + +### Unsupported Configuration + +bit + 1 + 0 False - when entering or leaving the RRC-Connected mode. + 1 True - an unsupported configuration has been detected. + +## 10.4.29 SECURITY\_MODIFICATION + +This variable contains information on which CN domain is affected by the ongoing security reconfiguration. When performing handover to UTRAN the value of this variable is transferred to the corresponding UTRAN variable. When performing handover from UTRAN the value of this variable is transferred from the corresponding UTRAN variable. + +**Table 10.4.29.1: SECURITY\_MODIFICATION Variable** + +``` +< SECURITY_MODIFICATION VAR > ::= + { 0 | 1 < Status for each CN domain : bit (2) > + { < CN Domain Identity : < CN Domain Identity IE > > + < Status : bit (1) > + } * (1+val(Status for each CN domain)) + } ; +``` + +**Table 10.4.29.2: SECURITY\_MODIFICATION Variable details** + +### Status for each CN domain (2 bit field) + +This field is used to repeat the status for each CN domain. Range : 0 to maxCNdomains-1, where 0 enables one status of CN domain to be described. + +### CN Domain Identity + +This IE is defined in sub-clause 9.3.15. + +**Status (1 bit field)** + +bit + +1 + +0 Not affected + +1 Affected + +## 11 Specific functions + +### 11.1 Provision and reception of RRC information between network nodes + +#### 11.1.1 General + +In certain cases, e.g., when performing handover to GERAN or when performing SBSS relocation, RRC information may need to be transferred between GERAN nodes, between GERAN and another RAT, between nodes within another RAT or between the MS and another RAT. + +The RRC information exchanged between network nodes or between the MS and another RAT is typically transferred by means of RRC information containers. An RRC information container is a self-contained and extensible RRC information unit that may be used to transfer a number of different RRC messages, one at a time. As stated before, RRC information containers may be used to transfer RRC messages across interfaces other than the Um interface. The RRC messages that may be included in RRC information containers have similar characteristics as the RRC messages that are transferred across the Um interface. + +The RRC messages that are sent to/ from the MS, e.g RADIO BEARER RECONFIGURATION, INTER SYSTEM TO UTRAN HANDOVER COMMAND HANDOVER FROM GERAN Iu MODE COMMAND are covered by (sub)clauses 7 and 9 of this specification. The following sub-clauses concern RRC messages exchanged between network nodes. + +In future versions of this specification, it is possible to extend the RRC messages transferred across interfaces other than Um. For these RRC messages the same extension mechanism applies as defined for RRC messages transferred across the Um interface, as is specified in sub-clause 9, i.e., both critical and non-critical extensions may be added. + +The transfer syntax for RRC information containers and RRC messages transferred between network nodes is derived from the description used in the target node. The resulting bit or octet string is, carried in a container, transferred between the network nodes. + +When using a separate RRC information container for each endpoint, the receiving RRC protocol entity is able to interpret the received container; this means that the receiver need not take into account information about the (network interface) message used in transferring the container. + +#### 11.1.2 General error handling for RRC messages exchanged between network nodes + +The error handling for RRC messages that are exchanged between network nodes applies the same principles as defined for other RRC messages. + +Although the same principles apply for network nodes receiving unknown, unforeseen and erroneous RRC messages received in RRC information containers, the notification of the error should be done in a different manner, as specified in the following: + +The network node receiving an invalid RRC message from another network node should: + +1> if the received RRC message was unknown, unforeseen or erroneous: + +2> prepare an RRC FAILURE INFO message, including the IE "*Failure Cause*" set to "Protocol error" and the IE "Protocol error information" including an IE "*Protocol Error Cause*" which should be set as follows: + +- 3> to "CSN.1 violation or encoding error" upon receiving an RRC message for which the encoded message does not result in any valid c syntax value; +- 3> to "Message type non-existent or not implemented" upon receiving an unknown RRC message type; +- 3> to "Message extension not comprehended" upon receiving an RRC message including an undefined critical message extension; +- 3> to "Information element value not comprehended" upon receiving an RRC message including an mandatory IE for which no default value is defined and for which either the value is set to spare or for which the encoded IE does not result in a valid transfer syntax. The same applies for conditional IEs, for which the conditions for presence are met, the IE is present but has a value set to spare or for which the encoded IE does not result in a valid transfer syntax; +- 3> to "Information element missing" upon receiving an RRC information container with an absent conditional IE for which the conditions for presence are met. + +1> if there was another failure to perform the operation requested by the received RRC message: + +- 2> prepare an RRC FAILURE INFO message, including the IE "*Failure Cause*" set to a value that reflects the failure cause. + +1> send the RRC FAILURE INFO message to the network node from which the invalid RRC protocol information was received. + +NOTE 1: The appropriate (failure) messages used across the network interfaces may not support the inclusion of a RRC information container. In this case, the information contained in the RRC FAILURE INFO message may need to be transferred otherwise e.g. by mapping to a cause value (e.g. a cause value in the RR-HANDOVER FAILURE message when there is a error associated with the RRC-RADIO BEARER RECONFIGURATION message). + +NOTE 2 In case the RRC procedure used to perform SBSS relocation fails e.g. due to non comprehension, the source BSS may notify the target BSS by including the diagnostics information (IEs "Protocol error" and "Protocol error information") in the "RRC message "SBSS Relocation" Info sent in the RRC information container" used for a subsequent relocation request. + +### 11.1.3 RRC Information to target GERAN Iu mode BSS + +The RRC information container "RRC Information to target GERAN Iu mode BSS" may either be sent from source GERAN Iu mode BSS or from another RAT. In case of Handover to GERAN, this information originates from another RAT, while in case of SBSS relocation the RRC information originates from the source BSS. In case of handover to GERAN, the RRC information transferred may provide GERAN specific information, as defined in the INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES message, that the target BSS needs when preparing the handover command message. In case of SBSS relocation, the RRC information transferred specifies the configuration of RRC and the lower layers it controls, e.g., including the radio bearer and RLC configuration. It is used by the target BSS to initialise RRC and the lower layer protocols to facilitate SBSS relocation in a manner transparent to the MS. + +**Table 11.1.3.1: RRC INFORMATION TO TARGET GERAN IU MODE BSS information elements** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RRC INFORMATION TO TARGET GERAN IU MODE BSS message content > ::= { 0 -- critical extension escape available {   { 00 <Handover to GERAN: < INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES Message > >     01 < SBSS Relocation : < SBSS RELOCATION INFO > >     10 < RFC3095 Context Info : < RFC3095 CONTEXT INFO >    ! < Message escape : { 11 } bit** = < no string > > } -- reserved for future extension   ! < Content part error : bit (*) = < no string > > }   ! < Message escape critical extension : 1 bit (*) = < no string > > } ;
| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.1.3.2: RRC INFORMATION TO TARGET GERAN IU MODE BSS information element details** + +| | +|--------------------------------------------------------------------------------------------------------------| +| INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES
This message is defined in sub-clause 11.1.5. | +| SBSS RELOCATION INFO
This message is defined in sub-clause 11.1.5. | +| RFC3095 CONTEXT INFO
This message is defined in sub-clause 11.1.5.3 | + +## 11.1.4 RRC information, target BSS to source BSS + +There are 2 possible cases for BSS relocation: + +- 1 The MS is already under control of target BSS; and +- 2 The SBSS Relocation with Handover (MS still under control of SBSS), but MS is moving to a location controlled by the target BSS (based on measurement information). + +In case 1 the relocation is transparent to the MS and there is no "reverse" direction container. The SBSS just assigns the 'serving' function to the target BSS, which then becomes the Serving BSS. + +In case 2 the relocation is initiated by SBSS, which also provides the RRC INFORMATION TO TARGET GERAN IU MODE BSS Container to the target BSS. Based upon this information, the target BSS prepares the RADIO BEARER RECONFIGURATION Message. + +The source BSS then transmits the Handover Message to the MS, which then performs the handover. + +In the successful case, the MS transmits a RADIO BEARER RECONFIGURATION COMPLETE message, using the new configuration, to the target BSS. + +In case of failure, the MS transmits an RADIO BEARER RECONFIGURATION FAILURE, using the old configuration, to the source BSS and the RRC context remains unchanged (has to be confirmed and checked with the SBSS relocation procedure). + +**Table 11.1.4.1: RRC Information Target BSS To Souce BSS information elements** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < RRC Information Target BSS To Souce BSS message content > ::= { 0 -- critical extension escape available   { 00 < RADIO BEARER RECONFIGURATION : < RADIO BEARER RECONFIGURATION message > >     01 < RRC FAILURE INFO : < RRC FAILURE INFO message > >   ! < Message escape : {10   11} bit (*) = <no string> > } -- reserved for future extension   ! < Content part error : bit (*) = < no string > > }   ! < Message escape critical extension : 1 bit (*) = < no string > > } ;
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.1.4.2: RRC Information Target BSS To Souce BSS information element details** + +| | +|-------------------------------------------------------------------------------------| +| RADIO BEARER RECONFIGURATION
This message is defined in sub-clause 9.3.28 | +| RRC FAILURE INFO
This message is defined in sub-clause 9.3.44 | + +## 11.1.5 RRC messages exchanged between network nodes + +### 11.1.5.0 RADIO BEARER RECONFIGURATION + +This RRC message is sent between network nodes to transfer the actual RADIO BEARER RECONFIGURATION message including the details of the radio configuration to be used upon handover to GERAN as compiled by the target BSS. + +Direction: target BSS → source RAT + +The message is exactly the same as the RADIO BEARER RECONFIGURATION defined in sub-clause 9.2.29. + +### 11.1.5.1 INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES + +This RRC message is sent between network nodes when preparing for an inter RAT handover to GERAN. + +Direction: source RAT→target BSS + +**Table 11.1.5.1.1: INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES elements** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
 < INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES message content > ::= {   -- MS Information Elements   { 0   1 < MS GERAN Iu mode Radio Access Capability : < MS GERAN Iu mode radio access capability IE > > }   { 0   1 < MS GERAN A/Gb mode Radio Access Capability : < MS GERAN A/Gb mode radio access capability IE > > }   { 0   1 < UE UTRAN Radio Access Capability : < UE UTRAN radio access capability IE > > }   { 0   1 < UE UTRAN Radio Access Capability Extension : < UE UTRAN radio access capability extension IE >> }   { 0   1 < UE CDMA2000 Radio Access Capability : < UE CDMA2000 radio access capability IE > > }   { 0   1 < Failure Cause and Error Information : < Failure Cause and Error Information IE > > }   { 0   1 < Multirate configuration : < Multirate configuration IE > > } ! < Content part error : bit (*) = < no string > > } ;
| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.1.5.1.2: INTER RAT or MODE HANDOVER INFO WITH MS CAPABILITIES element details** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

MS GERAN Iu mode Radio Access Capability
This IE is defined in sub-clause 9.3.45.

| +|

MS GERAN A/Gb mode Radio Access Capability
This IE is defined in sub-clause 9.3.44.

| +|

UE UTRAN Radio Access Capability
This IE is defined in sub-clause 9.3.108.

| +|

UE UTRAN Radio Access Capability Extension
This IE is defined in sub-clause 9.3.109.

| +|

UE CDMA2000 Radio Access Capability
This IE is defined in sub-clause 9.3.110.

| +|

MultiRate configuration IE
This IE is defined in sub-clause 9.3.52. If the present speech codec is a multi-rate speech codec, the old BSS may inform the new BSS of the current multi-rate codec configuration by including the MultiRate configuration information element in the RRC INFORMATION TO TARGET GERAN IU MODE BSS message.

| + +### 11.1.5.2 SBSS RELOCATION INFO + +This RRC message is sent between network nodes when preparing for an SBSS relocation or a handover from UTRAN to GERAN *Iu mode*. + +Direction: source RAT→target BSS. + +Table 11.1.5.2.1: SBSS RELOCATION INFO information elements + +``` + +< SBSS Relocation Information message content > ::= +{ + -- MS Information Elements + < RRC State Indicator : < RRC State Indicator IE > > + < State of RRC procedure : bit (4) > + -- Ciphering related information + { 00 < GERAN A/Gb Security Info : < GERAN A/Gb Security Info IE > > + | 01 < GERAN Iu Security Info : < GERAN Iu Security Info IE > > + | 10 < Extension : < Extension IE > > + | 11 < Extension : < Extension IE > > } + < G-RNTI : < G-RNTI IE > > + < START : < START IE > > + { 0 | 1 < MS GERAN Iu mode Radio Access Capability : < MS GERAN Iu mode Radio Access Capability IE > > } + { 0 | 1 < MS GERAN A/Gb mode Radio Access Capability : < MS GERAN A/Gb mode Radio Access Capability IE +> > } + { 0 | 1 < UE UTRAN Radio Access Capability : < UE UTRAN Radio Access Capability IE > > } + { 0 | 1 < UE UTRAN Radio Access Capability Extension : < UE UTRAN Radio Access Capability Extension IE > > } + { 0 | 1 < UE CDMA2000 Radio Access Capability : < UE CDMA2000 Radio Access Capability IE > > } + + < GRA Id : < GRA Id > > + < CN Common GSM-MAP NAS System Info : < NAS System Information GSM-MAP IE > > + < Length of CN Domain Related Information : bit (2) > + { + < CN Domain Identity : < CN Domain Identity IE > > + < CN Domain Specific GSM-MAP NAS System Info : < NAS System Information GSM-MAP IE > > + < CN Domain Specific DRX Cycle Length Coefficient : < CN Domain Specific DRX Cycle Length Coefficient IE +> > } + { 0 | 1 < Signalling RB Information to Setup List : bit (3) > + < Signalling RB Information to Setup : < Signalling RB Information to Setup IE > > *(1+val(Signalling RB +Information to Setup List)) + { 0 | 1 < RAB Information for Setup List : bit (4) > + < RAB Information for Setup : < RAB Information for Setup IE > > *(1+val(RAB Information for Setup List)) } + { 0 | 1 < RAB Information to Reconfigure List : bit (4) > + < RAB Information to Reconfigure : < RAB Information to Reconfigure IE > > *(1+val(RAB Information to +Reconfigure List)) } + { 0 | 1 < RB Information to Reconfigure List : bit (5) > + < RB Information to Reconfigure : < RB Information to Reconfigure IE > > *(1+val(RB Information to +Reconfigure List)) + { 0 | 1 < Multirate configuration : < Multirate Configuration IE > > } + { 0 | 1 < TDMAFN : < bit(22) > } + { 0 | 1 < Failure Cause and Error Information : < Failure Cause and Error Information IE > > } + { null | 0 bit** = < no string > + | 1--Release 6 additions, non-critical extention + { + { 0 | 1 < UL TrCH Information Common For All Transport Channels : < UL TrCH Information Common +For All Transport Channels IE > > } + { 0 | 1 < Added or Reconfigured UL TrCH Information List : bit (3) > + { + < Added or Reconfigured UL TrCH Information : < Added or Reconfigured UL TrCH Information IE > +> }*(1 + val( Added or Reconfigured UL TrCH information list ) ) + } + { 0 | 1 < DL TrCH Information Common For All Transport Channels : < DL TrCH Information Common +For All Transport Channels IE > > } + { 0 | 1 < Added or Reconfigured DL TrCH Information List : bit (3) > + { + < Added or Reconfigured DL TrCH Information : < Added or Reconfigured DL TrCH Information IE > +> }*(1 + val( Added or Reconfigured DL TrCH information list ) ) + } + } + } + ! < Content part error : bit (*) = < no string > > } ; + +``` + +Table 11.1.5.2.2: SBSS RELOCATION INFO information element details + +**RRC State Indicator** + +This IE is defined in sub-clause 9.3.97. + +| | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--|---------|--|---------|----------------------|---------|------------------------|---------|-------------------------|---------|-----------------------------------|---------|---------------------------|---------|--------------------------|---------|-------------------------|-------------------------------|--| +|

State of RRC procedure (4 bit field)
This IE describes the state of the RRC procedure started in the source cell (i.e. RB reconfiguration) as follows:

bit
4 3 2 1
0 0 0 0 Await no RRC message
0 0 0 1 Complete
0 0 1 0 Await RB Setup Complete
0 0 1 1 Await RB Reconfiguration Complete
0 1 0 0 Await RB Release Complete
0 1 0 1 Send Cell Update Confirm
0 1 1 0 Send URA Update Confirm
All other values are reserved
| bit | | 4 3 2 1 | | 0 0 0 0 | Await no RRC message | 0 0 0 1 | Complete | 0 0 1 0 | Await RB Setup Complete | 0 0 1 1 | Await RB Reconfiguration Complete | 0 1 0 0 | Await RB Release Complete | 0 1 0 1 | Send Cell Update Confirm | 0 1 1 0 | Send URA Update Confirm | All other values are reserved | | +| bit | | | | | | | | | | | | | | | | | | | | | +| 4 3 2 1 | | | | | | | | | | | | | | | | | | | | | +| 0 0 0 0 | Await no RRC message | | | | | | | | | | | | | | | | | | | | +| 0 0 0 1 | Complete | | | | | | | | | | | | | | | | | | | | +| 0 0 1 0 | Await RB Setup Complete | | | | | | | | | | | | | | | | | | | | +| 0 0 1 1 | Await RB Reconfiguration Complete | | | | | | | | | | | | | | | | | | | | +| 0 1 0 0 | Await RB Release Complete | | | | | | | | | | | | | | | | | | | | +| 0 1 0 1 | Send Cell Update Confirm | | | | | | | | | | | | | | | | | | | | +| 0 1 1 0 | Send URA Update Confirm | | | | | | | | | | | | | | | | | | | | +| All other values are reserved | | | | | | | | | | | | | | | | | | | | | +|

GERAN A/Gb Security Info
This IE is defined in sub-clause 11.2.

| | | | | | | | | | | | | | | | | | | | | +|

GERAN Iu or UTRAN Security Info
This IE is defined in sub-clause 11.2.

| | | | | | | | | | | | | | | | | | | | | +|

MS GERAN Iu mode Radio Access Capability
This IE is defined in sub-clause 9.3.45.

| | | | | | | | | | | | | | | | | | | | | +|

MS GERAN A/Gb mode Radio Access Capability
This IE is defined in sub-clause 9.3.44.

| | | | | | | | | | | | | | | | | | | | | +|

UE UTRAN Radio Access Capability
This IE is defined in sub-clause 9.3.108.

| | | | | | | | | | | | | | | | | | | | | +|

UE UTRAN Radio Access Capability Extension
This IE is defined in sub-clause 9.3.109.

| | | | | | | | | | | | | | | | | | | | | +|

UE CDMA2000 Radio Access Capability
This IE is defined in sub-clause 9.3.110.

| | | | | | | | | | | | | | | | | | | | | +|

Ciphering status for each CN domain (2 bit field)
This field is the binary representation of the number of CN domains. Range : 0 to maxCNdomains-1.

| | | | | | | | | | | | | | | | | | | | | +|

Ciphering Status (1 bit field)
This field indicates the status of ciphering for the CN domain

bit
1
1 Ciphering started
0 Ciphering not started.
| bit | | 1 | | 1 | Ciphering started | 0 | Ciphering not started. | | | | | | | | | | | | | +| bit | | | | | | | | | | | | | | | | | | | | | +| 1 | | | | | | | | | | | | | | | | | | | | | +| 1 | Ciphering started | | | | | | | | | | | | | | | | | | | | +| 0 | Ciphering not started. | | | | | | | | | | | | | | | | | | | | +|

START
This IE is defined in sub-clause 9.3.102.

| | | | | | | | | | | | | | | | | | | | | +|

TDMAFN (22 bit field)
This field is the binary representation of the TDMA Frame Number. The description of the TDMA Frame Number is in 3GPP TS 45.002.

| | | | | | | | | | | | | | | | | | | | | +|

CN Domain Identity
This IE is defined in sub-clause 9.3.15.

| | | | | | | | | | | | | | | | | | | | | +|

Calculation time for ciphering related information (??? bit field)
This field contains the time when the ciphering information of the message were calculated, relative to the intended target cell of the target BSS

| | | | | | | | | | | | | | | | | | | | | +|

G-RNTI IE
This IE is defined in sub-clause 9.3.32.

| | | | | | | | | | | | | | | | | | | | | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GRA Identity
This IE indicates the GRA ID as defined in sub-clause 9.3.30. | +| CN Common GSM-MAP NAS System Info
The NAS System Information GSM-MAP IE is defined in sub-clause 9.3.55. | +| Length of CN Domain Related Information (2 bit field)
This field is used to calculate the number of CN domains included in this IE. Range : 0 to MaxCNdomains-1. | +| CN Domain Specific GSM-MAP NAS System Info
The NAS System Information GSM-MAP IE is defined in sub-clause 9.3.55. | +| CN Domain Specific DRX Cycle Length Coefficient
The CN Domain Specific DRX Cycle Length Coefficient IE is defined in sub-clause 9.3.16. | +| Signalling RB Information to Setup List (3 bit field)
This field is the binary representation of the number of SRB to setup. Range : 0 to maxSRBsetup-1. | +| Signalling RB Information to Setup
This IE is present for each SRB to establish. This IE is defined in sub-clause 9.3.101. | +| RAB Information for Setup List (4 bit field)
This field is the binary representation of the number of RAB to setup. Range : 0 to maxRABsetup-1. | +| RAB Information for Setup
This IE is present for each signalling RAB to establish. This IE is defined in sub-clause 9.3.75. | +| RAB Information to Reconfigure List (4 bit field)
This field is the binary representation of the number of RAB to reconfigure. Range : 0 to maxRABsetup-1. | +| RAB Information to Reconfigure
This IE is defined in sub-clause 9.3.76. | +| RB Information to Reconfigure List (5 bit field)
This field is the binary representation of the number of RB to reconfigure. Range : 0 to maxRB-1. | +| RB Information to Reconfigure
This IE is defined in sub-clause 9.3.82. | +| MultiRate Configuration IE
This IE is defined in sub-clause 9.3.52. If the present speech codec is a multi-rate speech codec, the old BSS may inform the new BSS of the current multi-rate codec configuration by including the MultiRate configuration information Field Element in the RRC INFORMATION TO TARGET GERAN IU MODE BSS message. | +| Failure Cause and Error Information
The Failure Cause and Error Information IE is defined in sub-clause 9.3.25. | +| UL TrCH Information Common For All Transport Channels
The IE UL TrCH Information Common For All Transport Channels is defined in sub-clause 9.3.134. | +| Added or Reconfigured UL TrCH information List (3 bit field)
This field is used to repeat information on each TrCH to be added or reconfigured in UL. Range: 0 to maxTrCH-1, where 0 enables one TrCH to be described. | +| Added or Reconfigured UL TrCH Information
The IE Added or Reconfigured UL TrCH information IE is defined in sub-clause 9.3.122. | +| DL TrCH Information Common For All Transport Channels
The IE DL TrCH Information Common For All Transport Channels is defined in sub-clause 9.3.125. | +| Added or Reconfigured DL TrCH information List (3 bit field)
This field is used to repeat information on each TrCH to be added or reconfigured in DL. Range: 0 to maxTrCH-1, where 0 enables one TrCH to be described. | + +**Added or Reconfigured DL TrCH Information** + The IE *Added or Reconfigured DL TrCH information* is defined in sub-clause 9.3.121. + +### 11.1.5.3 RFC 3095 CONTEXT INFO + +This RRC message is sent between network nodes in SBSS/SRNS or SBSS/SBSS relocation. It is used to transfer the compressor and decompressor context information of the RFC 3095 protocol. + +Direction: source BSS → target BSS/RNC + +**Table 11.1.5.3.1: RFC 3095 CONTEXT INFO information elements** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< RFC 3095 Context Info IE > ::=    < RB with RFC 3095 Context List : bit(5) >   {     < RB Identity : < RB Identity IE > >     < RFC 3095 Context List : bit(14) >     {       { 0   1 -- Downlink RFC 3095 context         < Downlink RFC 3095 Context Identity: bit(14) >         < DL_MODE: bit(2) >         < REF_IR: octet(3000) >         { 0   1 < REF_TIME: bit(32) > }         { 0   1 < SYN_OFFSET_ID : bit(16) > }         { 0   1 < SYN_SLOPE_TS : bit(32) > }         { < DYN_CHANGED : 0 >           < DYN_CHANGED : 1 > }       }       { 0   1 -- Uplink RFC 3095 context         < Uplink RFC 3095 Context Identity: bit(14) >         < UL_MODE: bit(2) >         < REF_IR: octet(3000) >         { 0   1 < REF_TIME: bit(32) > }         { 0   1 < SYN_OFFSET_ID : bit(16) > }         { 0   1 < SYN_SLOPE_TS : bit(32) > }         { 0   1 < REF_SN_1 : bit(15) > }       }     }*(1 + val(RFC 3095 Context List))   }* (1 + val(RB with RFC 3095 Context List));
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Table 11.1.5.3.2: RFC 3095 CONTEXT INFO information elements details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RB with RFC 3095 Context List (5 bit field)
This field is the binary representation of the number of Radio Bearers with RFC 3095 context information.

Range: 0 to maxRBallRABs - 1.

RB Identity
This IE is defined in sub-clause 9.3.80.

RFC 3095 Context List (14 bit field)
This field is the binary representation of the number of the RFC 3095 contexts for this Radio Bearer.

Range: 0 to maxRFC3095-CID - 1.

Downlink RFC 3095 Context Identity (14 bit field)
Uplink RFC 3095 Context Identity (14 bit field)
This field represents the identity of the RFC 3095 in respectively Downlink and Uplink.

REF_IR (3000 octet string field)
This field corresponds to the RTP IR header (see sub-clause 5.7.7 of RFC3095 for detailed format) corresponding to the oldest header in the compressor sliding window.

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**RF\_TIME** (32 bit field) + +This field corresponds to the arrival time (at the compressor) of REF\_IR in milliseconds. See sub-clauses 4.5.4 and 6.5.1 of IETF RFC3095. + +**SYN\_SLOPE\_TS** (32 bit field) + +This field corresponds to the last synchronized slope of TS. See sub-clauses 5.5.1.2 and 5.7 of IETF RFC3095. In SO state, $TS(n) = TS(m) + (n-m) * SYN\_SLOPE\_TS$ , where n and m is the RTP SN of current packet and the reference packet. Note that the unit of SYN\_SLOPE\_TS depends on whether TS is scaled before compression or not. + +**DYN\_CHANGED** (1 bit field) + +This field corresponds to the information whether dynamic fields other than RTP SN, RTP TS and IP-ID have changed in the headers that are stored in the sliding window. Set to TRUE if changed and FALSE if not changed. + +bit + +1 + +0 DYN\_CHANGED not supported + +1 DYN\_CHANGED supported + +**SYN\_OFFSET\_ID** (16 bit field) + +This field corresponds to the RTP Sequence Number of the predecessor of the latest RTP packet. This could be used to perform local repair of context by decompressor in U or O mode (see "ref - 1" in sub-clause 5.3.2.2.5 in IETF RFC3095 for further explanation). + +**DL\_MODE** (2 bit field)**UL\_MODE** (2 bit field) + +This field represents the RFC 3095 mode in respectively Downlink and Uplink before the SBSS relocation. The optimal mode to operate in depends on the characteristics of the environment of the compression protocol, such as feedback abilities, error probabilities and distributions, effects of header size variation, etc. + +bit + +1 0 + +0 0 U-mode -- Unidirectional mode + +0 1 O-mode -- Bidirectional Optimistic mode + +1 0 R-mode -- Bidirectional Reliable mode + +1 1 reserved + +## 11.2 Provision and reception of RRC security information between network nodes + +### 11.2.1 General + +In certain cases, e.g., when performing handover or when performing SBSS relocation, RRC security related information shall be transferred between other RATs and GERAN or between GERAN nodes within GERAN. + +The lengths of the RLC counters of non-transparent radio bearers are different between GPRS (24bits) and EGPRS (20bits). The BSC shall set the HFN values according the source cell (GPRS or EGPRS) and independent from the target cell (UTRAN, GPRS or EGPRS). + +In the following, the RRC security information to be transferred is separated into the three scenarios: + +- GERAN A/Gb mode to GERAN Iu mode. +- GERAN Iu mode to GERAN Iu mode or UTRAN to GERAN Iu mode. + +### 11.2.2 RRC Security Information, from GERAN-A/Gb to GERAN-Iu + +The START value is used to initialise the most significant bits of all the HFN counters (MAC HFN, RLC AM HFN, RLC UM HFN, RRC HFN). + +Direction: source: GERAN A/Gb mode BSC → target GERAN Iu mode BSC + +Table 11.2.2.1: *GERAN A/Gb Security Info* information elements + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< GERAN A/Gb Security Info IE > ::= {   < Start-CS : < START IE > >   < Start-PS : < START IE > >   ! < Content part error : bit (*) = < no string > > };
| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Table 11.2.2.2: *GERAN A/Gb Security Info* information element details + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Start-CS
The START IE is used to intialise the most significant bits of all the HFN counters (MAC HFN, RLC AM HFN, RLC UM HFN, RRC HFN) for the CS domain. The START IE is defined in sub-clause 9.3.102.

| +|

Start-PS
The START IE is used to intialise the most significant bits of all the HFN counters (MAC HFN, RLC AM HFN, RLC UM HFN, RRC HFN) for the PS domain. The START IE is defined in sub-clause 9.3.102.

| + +## 11.2.3 RRC Security Information, from GERAN Iu mode/UTRAN to GERAN Iu mode + +This IE contains security information required for continued communication between the MS and GERAN after a handover or SRNS/SBSS relocation + +Direction: source: BSC/RNC → target BSC + +Table 11.2.3.1: *GERAN Iu or UTRAN Security Info* information elements + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 
< GERAN Iu or UTRAN Security Info IE > ::= {   < Ciphering status for each CN domain : bit (2) >   {     < CN domain identity : < CN domain identity > >     < Ciphering Status : bit (1) > }*(1+val(Ciphering status for each CN domain))   < Latest configured CN Domain : bit (2) >   < Ciphering info for transparent RB : bit (2) >   {     < CN domain identity : < CN domain identity > >     < MAC-HFN : bit (11) > }*(1+val(Ciphering info for transparent RB))   < Ciphering info for non-transparent RB : bit (5) >   {     < RB Id : < RB Identity IE > >     < DL HFN : < RLC HFN IE > >     < UL HFN : < RLC HFN IE > > }*(1+val(Ciphering info for non-transparent RB))   {     < Integrity Protection status : 1 >     {       < SRB-Id : bit (2) >       < UL RRC HFN : bit (28) >       < DL RRC HFN : bit (28) >       < Uplink RRC Message Sequence number : bit (4) > }*4     < Downlink RRC Message Sequence number : bit (4) > }*4     < Integrity Protection status : 0 > }   ! < Content part error : bit (*) = < no string > > };
| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Table 11.2.3.2: *GERAN Iu or UTRAN Security Info* information element details + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Ciphering status for each CN domain (2 bit field)
This field is the binary representation of the number of repeated groups of fields and IEs. Range : 0 to maxCNdomains-1.

| +|

CN Domain Identity
This IE is defined in sub-clause 9.3.115.

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

Ciphering status (1 bit field)
This field indicates the ciphering status of the indicated CN Domain.
Bit
1
0 Ciphering not started
1 Ciphering started

| | | | | | | | | | | | | +|

Last Configuered CN Domain (2 bit field)
This field indicates the last configured CN Domain. This field is encoded as the CN Domain Identity in sub-clause 9.3.15

| | | | | | | | | | | | | +|

Ciphering info for transparent RB (2 bit field)
This field is the binary representation of the number of instances of ciphering info which is provided for transparent mode RLC RBs. Range : 0 to maxCNDomains-1.

| | | | | | | | | | | | | +|

MAC-HFN (11 bit field)
This field contains the MAC-HFN. The MAC-HFN is defined as the 11 MSB of the COUNT-C value.

| | | | | | | | | | | | | +|

Ciphering info for non-transparent RB (5 bit field)
This field is the binary representation of the number of non-transparent mode RLC RBs for which ciphering info is provided. Range : 0 to maxRB-1.

| | | | | | | | | | | | | +|

DL HFN / UL HFN
The RLC HFN IE is defined in 9.3.92.

| | | | | | | | | | | | | +|

Integrity Protection status (1 bit field)
This field indicates the status of integrity protection in the current cell. The field is encoded:
Bit
1
0 Integrity Protection not started
1 Integrity Protection started.

| | | | | | | | | | | | | +|

SRB-Id (2 bit field)
This field defines the SRB Id for which the following integrity protection information applies:

bit
2 1
0 0 SRB1
0 1 SRB2
1 0 SRB3
1 1 SRB4.
| bit | | 2 1 | | 0 0 | SRB1 | 0 1 | SRB2 | 1 0 | SRB3 | 1 1 | SRB4. | +| bit | | | | | | | | | | | | | +| 2 1 | | | | | | | | | | | | | +| 0 0 | SRB1 | | | | | | | | | | | | +| 0 1 | SRB2 | | | | | | | | | | | | +| 1 0 | SRB3 | | | | | | | | | | | | +| 1 1 | SRB4. | | | | | | | | | | | | +|

UL / DL RRC HFN (28 bit field)
This field contains the RRC HFN in the indicated direction. For each SRB, in case the activation times for the next Integrity Protection configuration to be applied on this SRB have already been reached, this IE corresponds to the last value used. Else this value corresponds to the value the source would have initialized the HFN to at the activation time. Increment of HFN due to RRC SN roll over is taken care of by target based on the value sent by the source

| | | | | | | | | | | | | +|

Uplink RRC Message Sequence Number (4 bit field)
This field is the binary representation of the RRC Sequence number for the indicated SRB. For each SRB, this IE corresponds to the last value received or in case the activation time was not reached for a configuration the value equals (activation time -1). Range 0-15.

| | | | | | | | | | | | | +|

Downlink RRC Message Sequence Number (4 bit field)
This field is the binary representation of the RRC Sequence number for the indicated SRB. For each SRB, this IE corresponds to the last value used or in case the activation time was not reached for a configuration, to the value (activation time -1). In particular, for SRB2, this IE should not take into account the RRC message that will trigger the relocation. Range 0-15.

| | | | | | | | | | | | | + +### 11.2.4 RRC Security Information, from GERAN Iu to UTRAN + +NOTE: This information should be specified in 25.331 since UTRAN is the target RAT. + +## 11.3 HFN mapping rules for radio bearer using non-transparent mode RLC + +The length of RLC counters in UTRAN (RLC-AM 20bits, RLC-UM 25bits) and GERAN-Iu are different. In GERAN-Iu there are additional differences between GPRS (RLC-AM and RLC-UM 24bits) and EGPRS (RLC-AM and RLC-UM 20bits). + +The network nodes shall use the following HFN mapping rules when sending or receiving HFN values within the RRC information containers: + +- 1> the source network node shall set the HFN value as used in the source cell, +- 1> if the target network node receives an HFN value with the same length as used in the target cell; + - 2> increment this HFN by 1; and + - 2> use this value as HFN in the target cell; +- 1> if the target network node receives an HFN which is longer than the one used in the target cell; + - 2> take the MSBs as needed for the target cell; + - 2> increment this value by 1; and + - 2> use this value as HFN in the target cell; +- 1> if the target network node receives an HFN which is shorter than the one used in the target cell; + - 2> increment this HFN by 1; + - 2> add a number of least significant zero bits as needed; and + - 2> use this value as HFN in the target cell. + +## 11.4 Calculated Transport Format Combination + +The CTFCs are used to signal the transport format combination set. Every possible transport format combination shall uniquely be identified by one CTFC, including transport format combinations, which are not members of the transport format combination set. + +Two formulas shall be used to define the CTFC. Let $I$ be the number of transport channels that shall be included in the transport format combination. Each transport channel $TrCH_i$ , $i = 1, 2, \dots, I$ , shall have $L_i$ transport formats, i.e. the transport format indicator $TFIN_i$ can take $L_i$ values, . For each transport channel, the transport format such that $TFIN_i = 0$ is the empty transport format. + +Define , where $i = 1, 2, \dots, I$ , and $L_0 = 1$ + +Let $TFC(TFIN_1, TFIN_2, \dots, TFIN_I)$ be the transport format combination for which $TrCH_1$ shall transport format $TFIN_1$ , $TrCH_2$ shall transport format $TFIN_2$ , etc. The corresponding $CTFC(TFIN_1, TFIN_2, \dots, TFIN_I)$ is then computed as: + +The transport format combination such that $CTFC = 0$ is the empty transport format combination. + +After computing the CTFC value for all allowed transport format combinations (a CTFC is defined for all transport format combinations, but it is only necessary to compute the CTFC for the allowed transport format combinations), the CTFCs are signalled in order. The TFCIs are then assigned in the same order, i.e. the first TFC signalled by its CTFC will correspond to $TFCI = 0$ , the next corresponds to $TFCI = 1$ , etc. + +In a Layer 3 signalling message, the CTFC values shall be encoded using a variable size field, the size of which is the same for all values and depends on the highest value to be signalled. The possible sizes are: 2 bits, 4 bits, 6 bits, 8 bits, 12 bits and 16 bits. The size of the fields is signalled in the Layer 3 message. + +## 11.5 Signalling TFC + +One TFC shall be defined that shall be used for SRB data transfer and layer 2 signalling (see 3GPP TS 44.160). That TFC shall be the first one in the TFCS, for which the TFCI equals 0. In that TFC, only one TrCH shall be active and shall have the following transport format: + +- 184 bits transport blocks; +- 18 bits CRC; +- 256 for the RMA. + +NOTE: The value of the RMA does not matter since there is only one active TrCH. + +--- + +## Annex A (informative): Change History + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|-----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-01 | | - | - | - | - | Release 13 version created based on version 12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version created based on version 13.0.0 | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version created based on version 14.0.0 | 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/44_series/44160/0a595a22e0d1a1be020b49afa71bef55_img.jpg b/marked/Rel-16/44_series/44160/0a595a22e0d1a1be020b49afa71bef55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9ab9b83dc42eefdf78ddbb6ab0eba0f231d8746 --- /dev/null +++ b/marked/Rel-16/44_series/44160/0a595a22e0d1a1be020b49afa71bef55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cce538cf025909ff3936722ad4824547740d88c4a2fcc91e27abdda94f472cd +size 54256 diff --git a/marked/Rel-16/44_series/44160/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg b/marked/Rel-16/44_series/44160/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..316895b63d1e041b5ad460f2cfac4d95fc951ed4 --- /dev/null +++ b/marked/Rel-16/44_series/44160/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f185273f3266fdadd6d63026b01b55638d619cbbe3f04710e44fae26c37593a +size 17914 diff --git a/marked/Rel-16/44_series/44160/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/44_series/44160/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8eb1baa6adc557904651b8566f84e3ae7bc6ea8e --- /dev/null +++ b/marked/Rel-16/44_series/44160/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09c2b50c0823dd6ac77c5b854c68fc0b11cf603369a491c3a88765d80fb12b11 +size 79245 diff --git a/marked/Rel-16/44_series/44160/1e3d887bf7a660e3cb6374a0d2d6bf6b_img.jpg b/marked/Rel-16/44_series/44160/1e3d887bf7a660e3cb6374a0d2d6bf6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43ba6981fdd62179d467aae001362e71fdfb8e7c --- /dev/null +++ b/marked/Rel-16/44_series/44160/1e3d887bf7a660e3cb6374a0d2d6bf6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1ed08b2fb15e649e35f08c2176653213cfe4a1d32fe205008c74e4106de220b +size 12762 diff --git a/marked/Rel-16/44_series/44160/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-16/44_series/44160/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3090765fd1c8f2a80b4612a11b8b702c9d455dc --- /dev/null +++ b/marked/Rel-16/44_series/44160/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a646ecafd2645ab01cdd82f2a43067da7d91480f916b040fd9fbebcd6820019 +size 56277 diff --git a/marked/Rel-16/44_series/44160/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/44_series/44160/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..280d871710aa976e296d474f290f2a5ea30d4119 --- /dev/null +++ b/marked/Rel-16/44_series/44160/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a14dbc8f78804df81a89bcb02a4b9244a17329e581cd348b2ecbb7097ecd82a +size 68599 diff --git a/marked/Rel-16/44_series/44160/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-16/44_series/44160/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fe9d7d4e151f9fa516b5dc2b3771b7b3ebbe330 --- /dev/null +++ b/marked/Rel-16/44_series/44160/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df8bbb358b1b5bc024e8c2b9495d1a7b644d7ff0d9aaf5d7bb3119dae7b4ceec +size 48283 diff --git a/marked/Rel-16/44_series/44160/2f2911db53fbb1b2624f83a51555eb81_img.jpg b/marked/Rel-16/44_series/44160/2f2911db53fbb1b2624f83a51555eb81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2946bde64779cd54eb7d9c68862a6da6ad4f916f --- /dev/null +++ b/marked/Rel-16/44_series/44160/2f2911db53fbb1b2624f83a51555eb81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a34f77421124ac46346ab60ceaaa79b97ee3f7de8e3b995029c2ef11dfe664d9 +size 37734 diff --git a/marked/Rel-16/44_series/44160/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-16/44_series/44160/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37428dcb437bcc3cf6da5575390df8b062c7e96a --- /dev/null +++ b/marked/Rel-16/44_series/44160/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca80450175bf66406ad02f813f0db554f897167377523b9f5e1618991a6f464c +size 60291 diff --git a/marked/Rel-16/44_series/44160/4bc9150c673850f31328befa6ca768ac_img.jpg b/marked/Rel-16/44_series/44160/4bc9150c673850f31328befa6ca768ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69d747ae085b3899da4d0205d0eeb597e8c0c170 --- /dev/null +++ b/marked/Rel-16/44_series/44160/4bc9150c673850f31328befa6ca768ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54ed9f8fd9559a02bf8b41238a3b216aaa83049d73c16c4f0199ddb31ebb2e60 +size 54148 diff --git a/marked/Rel-16/44_series/44160/4e8d58baf485af1a077dbfc627a665a9_img.jpg b/marked/Rel-16/44_series/44160/4e8d58baf485af1a077dbfc627a665a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7660cb684ae514fe4fb7bae8ee6170b356beff5 --- /dev/null +++ b/marked/Rel-16/44_series/44160/4e8d58baf485af1a077dbfc627a665a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cf5068accda8a305316ceaf1774e4c557db8cd5ce08d0dd3f78b30b731ed365 +size 38799 diff --git a/marked/Rel-16/44_series/44160/58e07d355a649f1fbd8a041b88207829_img.jpg b/marked/Rel-16/44_series/44160/58e07d355a649f1fbd8a041b88207829_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeeb01b4999ad418b8d127dc4fe2386a924823b3 --- /dev/null +++ b/marked/Rel-16/44_series/44160/58e07d355a649f1fbd8a041b88207829_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:606c444d5cb8c819d0465f4ef7310ef3cbca19333cf9b7f80ed5da792734faf2 +size 45324 diff --git a/marked/Rel-16/44_series/44160/6a91a6df50795695b71693ad679a4f31_img.jpg b/marked/Rel-16/44_series/44160/6a91a6df50795695b71693ad679a4f31_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21c70fc73f8e3dfc4453edd31f76b08a4bd9fc51 --- /dev/null +++ b/marked/Rel-16/44_series/44160/6a91a6df50795695b71693ad679a4f31_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2052b63153f9f11ae49d8cf5d21b342e46b991d2c015ed87cdd99e2d7e5afe7 +size 18881 diff --git a/marked/Rel-16/44_series/44160/6e612452d995bb03cc3f3d004493f7bf_img.jpg b/marked/Rel-16/44_series/44160/6e612452d995bb03cc3f3d004493f7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db511c2f0ac49b1c9c2d01f20bd8f957447bfedd --- /dev/null +++ b/marked/Rel-16/44_series/44160/6e612452d995bb03cc3f3d004493f7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e58c34e188b6885f2a2830558d37ecde42ceefbcf4913ed1543411fda5cc6db7 +size 37872 diff --git a/marked/Rel-16/44_series/44160/796d2e601722450d6456085e0a801e1e_img.jpg b/marked/Rel-16/44_series/44160/796d2e601722450d6456085e0a801e1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..388cb2870bc68f345ba1ba5a9b9d2a6a9e1e6172 --- /dev/null +++ b/marked/Rel-16/44_series/44160/796d2e601722450d6456085e0a801e1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1c812fd37e799e153095956afd851fa330680458a67200077cfad46da80217c +size 15069 diff --git a/marked/Rel-16/44_series/44160/986e77e2df3c318680a569774888f4aa_img.jpg b/marked/Rel-16/44_series/44160/986e77e2df3c318680a569774888f4aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..848d37b7356f28c92620111dcb8005073da16a9d --- /dev/null +++ b/marked/Rel-16/44_series/44160/986e77e2df3c318680a569774888f4aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:306f56cb97d23c9425866b63a13cca430d4f54e15cefa565578b21f3da198338 +size 20883 diff --git a/marked/Rel-16/44_series/44160/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg b/marked/Rel-16/44_series/44160/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88344e81a3586701766603cad0759a3f443b98dc --- /dev/null +++ b/marked/Rel-16/44_series/44160/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65aeddf06a09d0688c4c097ea7f270c988728f0452597f6c6a992f39b8e62232 +size 18033 diff --git a/marked/Rel-16/44_series/44160/b47f393ea2c781f313367435c7166abb_img.jpg b/marked/Rel-16/44_series/44160/b47f393ea2c781f313367435c7166abb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0e10d422d479b7c36f8896c72627e9b7f155651 --- /dev/null +++ b/marked/Rel-16/44_series/44160/b47f393ea2c781f313367435c7166abb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:119fcb7b0448452c6d02ba7569789a95635708f45ca6c5d35c20cfc0a4e9cfd4 +size 18672 diff --git a/marked/Rel-16/44_series/44160/c09b8a811aa8d56401cfa959cf953640_img.jpg b/marked/Rel-16/44_series/44160/c09b8a811aa8d56401cfa959cf953640_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b24cbce3d641e94280dd87919ece58bc6523b9b2 --- /dev/null +++ b/marked/Rel-16/44_series/44160/c09b8a811aa8d56401cfa959cf953640_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a43eef99fd89dadf1017ac307271cb5859f6e94199b077f7c52bb2d6aba3dbaa +size 8862 diff --git a/marked/Rel-16/44_series/44160/d197b6ded14ea918198a280ff07122b8_img.jpg b/marked/Rel-16/44_series/44160/d197b6ded14ea918198a280ff07122b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aba0a6571beada98fc282ab62df143a8f27a188f --- /dev/null +++ b/marked/Rel-16/44_series/44160/d197b6ded14ea918198a280ff07122b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:301b996641b40a264820cd3b09814b616e813290f48ce0c5fd2f256b7d1a891a +size 53267 diff --git a/marked/Rel-16/44_series/44160/e60c2d24a97a2855d98671d27ea43d0f_img.jpg b/marked/Rel-16/44_series/44160/e60c2d24a97a2855d98671d27ea43d0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..538a02623c2d99d389af85cc74ad7068bb138049 --- /dev/null +++ b/marked/Rel-16/44_series/44160/e60c2d24a97a2855d98671d27ea43d0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:278f6e596a9399f23bebb474dc648c66b98fb563ea0efb408ba902bb91884f83 +size 21504 diff --git a/marked/Rel-16/44_series/44160/e64106d52dee350a3439ff0d396d26fc_img.jpg b/marked/Rel-16/44_series/44160/e64106d52dee350a3439ff0d396d26fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c35b65adb7cb7edfcb3c700197b39c213afd6f22 --- /dev/null +++ b/marked/Rel-16/44_series/44160/e64106d52dee350a3439ff0d396d26fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d66bbb2c8be615bf879e3d6a3a15398a71eae0297f43e0a3845a92d401b8ad3a +size 13530 diff --git a/marked/Rel-16/44_series/44160/e85b1c059513af5ec342d3f0caffc034_img.jpg b/marked/Rel-16/44_series/44160/e85b1c059513af5ec342d3f0caffc034_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b40732b14a2f8e4befa9c79a2275c97b8189e4d9 --- /dev/null +++ b/marked/Rel-16/44_series/44160/e85b1c059513af5ec342d3f0caffc034_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1683c51b9bbf597d5dd1fc971fe90abbb3e47526e77eeb4c0682db38c843f18c +size 9296 diff --git a/marked/Rel-16/44_series/44160/f05fd39478edccadc1227955d092e28b_img.jpg b/marked/Rel-16/44_series/44160/f05fd39478edccadc1227955d092e28b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2291bd3a60b89d5b1f7811b2de4046d217248cf9 --- /dev/null +++ b/marked/Rel-16/44_series/44160/f05fd39478edccadc1227955d092e28b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ca79bd7b349a123b0e57d7e0858b3ba15a6d4afd7ee678ed55ed0be41af063d +size 15030 diff --git a/marked/Rel-16/44_series/44160/f502d41e990d86acbbd785962f2af138_img.jpg b/marked/Rel-16/44_series/44160/f502d41e990d86acbbd785962f2af138_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8a3f28caa7dfcbb9497b5c783545faa0fd88985 --- /dev/null +++ b/marked/Rel-16/44_series/44160/f502d41e990d86acbbd785962f2af138_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7cb15b1713a239d52485e6343200e3e9b67a26b273cf9c12322511644ee6827 +size 9036 diff --git a/marked/Rel-16/44_series/44160/raw.md b/marked/Rel-16/44_series/44160/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..836994cc0f8b682adac745df0fd2877fe4e19665 --- /dev/null +++ b/marked/Rel-16/44_series/44160/raw.md @@ -0,0 +1,4643 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 11 | +| 1 Scope..... | 12 | +| 1.1 General ..... | 12 | +| 1.2 Related documents ..... | 12 | +| 1.3 Use of logical control channels ..... | 12 | +| 1.4 Use of logical traffic channels..... | 13 | +| 1.4a Use of transport channels ..... | 13 | +| 1.5 Conventions..... | 13 | +| 2 References..... | 13 | +| 3 Definitions, symbols and abbreviations..... | 15 | +| 3.1 Definitions..... | 15 | +| 3.2 Symbols..... | 15 | +| 3.3 Abbreviations ..... | 16 | +| 4 Layered overview of radio interface ..... | 17 | +| 4.0 Protocol architecture ..... | 17 | +| 4.1 Layer services..... | 19 | +| 4.2 Layer functions..... | 19 | +| 4.2.1 RLC function ..... | 19 | +| 4.2.2 MAC layer function..... | 20 | +| 4.3 Service primitives..... | 21 | +| 4.3.1 MAC to Physical Layer Primitives..... | 21 | +| 4.3.2 PDCP to RLC Primitives..... | 21 | +| 4.3.2.1 Primitives ..... | 21 | +| 4.3.2.2 Primitive parameters ..... | 22 | +| 4.3.3 RRC to RLC Primitives..... | 22 | +| 4.3.3.1 Primitives ..... | 22 | +| 4.3.3.2 Primitive parameters ..... | 23 | +| 4.3.4 RRC to MAC Primitives ..... | 24 | +| 4.3.4.1 Primitives ..... | 24 | +| 4.3.4.2 Primitive Parameters..... | 25 | +| 4.4 Services required from lower layers..... | 25 | +| 5 Introduction to the Medium Access Control (MAC) procedures ..... | 26 | +| 5.1 General ..... | 26 | +| 5.2 Multiplexing principles ..... | 26 | +| 5.2.1 Temporary Block Flow..... | 26 | +| 5.2.2 Temporary Flow Identity..... | 27 | +| 5.2.2.1 Temporary Flow Identity for SBPSCH ..... | 27 | +| 5.2.2.2 Temporary Flow Identity for DBPSCH..... | 27 | +| 5.2.3 Uplink State Flag..... | 27 | +| 5.2.4 Medium Access modes..... | 28 | +| 5.2.4.1 Medium Access modes for SBPSCH..... | 28 | +| 5.2.4.2 Medium Access modes for DBPSCH..... | 28 | +| 5.2.5 Multiplexing of GPRS and EGPRS TBF mode capable mobile stations ..... | 28 | +| 5.3 MAC States ..... | 28 | +| 5.3.1 MAC-Idle state ..... | 28 | +| 5.3.1.1 General..... | 28 | +| 5.3.1.2 Establishment of a SBPSCH..... | 28 | +| 5.3.1.3 Establishment of a DBPSCH..... | 28 | +| 5.3.2 MAC-Shared state ..... | 28 | +| 5.3.2.1 General..... | 28 | +| 5.3.2.2 Release of all SBPSCHs ..... | 28 | +| 5.3.2.3 Establishment of a DBPSCH..... | 29 | +| 5.3.2.4 Radio bearer reconfiguration ..... | 29 | +| 5.3.3 MAC-DTM state ..... | 29 | +| 5.3.3.1 General..... | 29 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------|----| +| 5.3.3.2 | Release of all SBPSCHs ..... | 29 | +| 5.3.3.3 | Release of all DBPSCHs..... | 29 | +| 5.3.3.4 | Release of all SBPSCHs and DBPSCHs ..... | 29 | +| 5.3.4 | MAC-Dedicated state ..... | 29 | +| 5.3.4.1 | General ..... | 29 | +| 5.3.4.2 | Release of all DBPSCHs..... | 29 | +| 5.3.4.3 | Radio bearer reconfiguration ..... | 29 | +| 5.3.5 | MAC state machine ..... | 30 | +| 5.4 | General MAC procedures in MAC-Idle state and MAC-Shared state..... | 30 | +| 5.4.1 | Mobile station side ..... | 30 | +| 5.4.1.1 | General ..... | 30 | +| 5.4.1.2 | Cell reselection ..... | 30 | +| 5.4.1.3 | Network Assisted Cell Change ..... | 31 | +| 5.4.1.4 | Release of DBPSCHs..... | 31 | +| 5.4.1.4.1 | General ..... | 31 | +| 5.4.1.4.2 | Continuation of PBCCH information..... | 31 | +| 5.4.1.4.3 | Receipt of PSI14 message in MAC-DTM state ..... | 32 | +| 5.4.1.5 | System information on PBCCH..... | 32 | +| 5.4.1.6 | System information on BCCH..... | 32 | +| 5.4.1.6.1 | General ..... | 32 | +| 5.4.1.6.2 | Establishment of PBCCH..... | 32 | +| 5.4.1.6.3 | (void) ..... | 32 | +| 5.4.1.7 | (void)..... | 32 | +| 5.4.1.8 | Discontinuous reception (DRX) ..... | 32 | +| 5.4.1.9 | Page mode procedures on PCCCH..... | 33 | +| 5.4.1.10 | Frequency Parameters..... | 33 | +| 5.4.1.11 | G-RNTI Management..... | 33 | +| 5.4.2 | Network side..... | 33 | +| 5.4.2.1 | System Information broadcasting ..... | 33 | +| 5.4.2.1.1 | System information on PBCCH ..... | 33 | +| 5.4.2.1.2 | System information on BCCH ..... | 34 | +| 5.4.2.1.3 | System information on PACCH (and other logical channels) ..... | 34 | +| 5.4.2.1.4 | Consistent sets of system information messages..... | 34 | +| 5.4.2.2 | Paging ..... | 35 | +| 5.4.2.3 | Network Assisted Cell Change ..... | 35 | +| 5.5 | Measurement reports ..... | 35 | +| 5.5.1 | General ..... | 35 | +| 5.5.2 | Network Control (NC) measurement reporting..... | 35 | +| 5.5.3 | (void) ..... | 36 | +| 5.5.4 | Additional measurement and reporting parameters ..... | 36 | +| 5.6 | Mapping of Signalling Radio Bearers (SRB) onto logical channels / transport channels ..... | 36 | +| 5.6.1 | Downlink ..... | 36 | +| 5.6.2 | Uplink..... | 36 | +| 5.6.2.1 | MAC-Dedicated State..... | 36 | +| 5.6.2.2 | MAC-Shared State..... | 37 | +| 5.6.2.3 | MAC-DTM State..... | 37 | +| 5.7 | Multiplexing principles with Flexible Layer One ..... | 38 | +| 5.7.1 | General ..... | 38 | +| 5.7.2 | Multiplexing between user-plane and control-plane ..... | 39 | +| 6 | Paging procedures ..... | 39 | +| 6.1 | General ..... | 39 | +| 6.2 | Paging initiation in MAC-Idle state ..... | 40 | +| 6.3 | Paging initiation in MAC-Shared state ..... | 40 | +| 6.4 | Reception of PACKET PAGING REQUEST by an MS ..... | 40 | +| 7 | Medium Access Control (MAC) procedures on PCCCH ..... | 40 | +| 7.1 | General ..... | 40 | +| 7.2 | TBF establishment initiated by the mobile station on PCCCH..... | 41 | +| 7.2.1 | General ..... | 41 | +| 7.2.2 | Permission to access the network ..... | 41 | +| 7.2.3 | Initiation of a TBF establishment ..... | 41 | + +| | | | +|-------------|--------------------------------------------------------------------------------------|----| +| 7.2.3.1 | Initiation of the packet access procedure..... | 41 | +| 7.2.3.1.1 | General ..... | 41 | +| 7.2.3.1.2 | Access persistence control on PRACH..... | 42 | +| 7.2.3.2 | Packet assignment procedure..... | 42 | +| 7.2.3.2.1 | On receipt of a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message ..... | 42 | +| 7.2.3.2.1.2 | Allocation of resource on SBPSCH(s) ..... | 42 | +| 7.2.3.2.1.3 | Allocation of resource on DBPSCH(s)..... | 43 | +| 7.2.3.3 | Contention resolution at one phase access..... | 44 | +| 7.2.3.3.1 | Contention resolution at one phase access on SBPSCHs..... | 44 | +| 7.2.3.3.2 | Contention resolution at one phase access on DBPSCH..... | 45 | +| 7.2.3.4 | RLC/MAC procedures during contention resolution..... | 46 | +| 7.2.3.4.1 | RLC/MAC procedures during contention resolution on SBPSCHs..... | 46 | +| 7.2.3.4.2 | RLC/MAC procedures during contention resolution on DBPSCHs..... | 46 | +| 7.2.3.5 | One phase packet access completion..... | 47 | +| 7.2.3.5.1 | One phase packet access completion on SBPSCHs..... | 47 | +| 7.2.3.5.2 | One phase packet access completion on DBPSCHs ..... | 47 | +| 7.2.3.6 | Timing Advance ..... | 47 | +| 7.2.3.6.1 | Timing advance on SBPSCHs..... | 47 | +| 7.2.3.6.2 | Timing advance on DBPSCHs..... | 47 | +| 7.2.4 | TBF establishment using two phase access..... | 47 | +| 7.2.4.1 | Initiation of the Packet resource request procedure..... | 47 | +| 7.2.4.2 | Packet resource assignment for uplink procedure ..... | 48 | +| 7.2.4.2.1 | (void) ..... | 48 | +| 7.2.4.2.2 | On receipt of a PACKET RESOURCE REQUEST message ..... | 48 | +| 7.2.4.3 | Contention resolution at two phase access ..... | 48 | +| 7.2.4.4 | Two phase packet access completion ..... | 49 | +| 7.2.4.5 | Timing Advance ..... | 49 | +| 7.2.5 | Abnormal cases ..... | 49 | +| 7.3 | TBF establishment initiated by the network on PCCCH ..... | 50 | +| 7.3.1 | General ..... | 50 | +| 7.3.2 | Entering the MAC-Shared state..... | 50 | +| 7.3.2.1 | General..... | 50 | +| 7.3.2.2 | Packet downlink assignment procedure..... | 50 | +| 7.3.2.2.1 | Packet downlink assignment procedure ..... | 50 | +| 7.3.2.2.2 | HFN synchronization ..... | 50 | +| 7.3.2.3 | Packet downlink assignment procedure completion..... | 50 | +| 7.3.2.4 | Packet polling procedure ..... | 51 | +| 7.3.2.5 | Abnormal cases..... | 51 | +| 7.3.3 | Entering the MAC-Dedicated state..... | 51 | +| 7.3.3.1 | General..... | 51 | +| 7.3.3.2 | Packet DBPSCH assignment procedure ..... | 51 | +| 7.3.3.3 | Packet DBPSCH assignment procedure completion ..... | 52 | +| 7.3.3.4 | Packet polling procedure ..... | 52 | +| 7.3.3.5 | Abnormal cases..... | 52 | +| 7.4 | Procedure for measurement report sending in MAC-Idle state..... | 52 | +| 7.4.1 | General ..... | 52 | +| 7.4.2 | Measurement report sending procedure initiated on PCCCH ..... | 52 | +| 7.4.2.1 | General..... | 52 | +| 7.4.2.2 | On receipt of a PACKET CHANNEL REQUEST message ..... | 52 | +| 7.4.2.3 | On receipt of a PACKET UPLINK ASSIGNMENT message..... | 52 | +| 7.4.2.4 | On receipt of a PACKET ACCESS REJECT message ..... | 53 | +| 7.4.2.5 | Abnormal cases..... | 53 | +| 7.5 | Cell Change Order procedures in MAC-Idle state..... | 53 | +| 7.5.1 | General ..... | 53 | +| 7.6 | Measurement Order procedures in MAC-Idle state..... | 53 | +| 7.6.1 | General ..... | 53 | +| 7.6.2 | Measurement Order procedures initiated on PCCCH ..... | 54 | +| 8 | Medium Access Control (MAC) procedures on SBPSCH ..... | 54 | +| 8.1 | General ..... | 54 | +| 8.1a | Resource stealing (SFACCH) ..... | 54 | + +| | | | +|-------------|--------------------------------------------------------------------------|----| +| 8.2 | Transfer of RLC data blocks ..... | 55 | +| 8.2.1 | Medium access mode ..... | 55 | +| 8.2.2 | Uplink RLC data block transfer ..... | 55 | +| 8.2.2.0 | General ..... | 55 | +| 8.2.2.0.1 | General ..... | 55 | +| 8.2.2.0.2 | Establishment of additional uplink TBF(s) ..... | 55 | +| 8.2.2.0.3 | Uplink resource reallocation / reconfiguration ..... | 55 | +| 8.2.2.0.4 | Establishment of downlink TBF(s) ..... | 56 | +| 8.2.2.1 | Dynamic Allocation uplink RLC data block transfer ..... | 56 | +| 8.2.2.1.1 | PACCH operation ..... | 56 | +| 8.2.2.1.2 | Resource Allocation / Reallocation for Uplink ..... | 56 | +| 8.2.2.1.2.2 | On receipt of the PACKET RESOURCE REQUEST ..... | 56 | +| 8.2.2.1.3 | Establishment of downlink TBF ..... | 58 | +| 8.2.2.1.3.1 | General ..... | 58 | +| 8.2.2.1.3.2 | Abnormal cases ..... | 59 | +| 8.2.2.2 | Extended Dynamic Allocation uplink RLC data block transfer ..... | 59 | +| 8.2.2.2.0 | General ..... | 59 | +| 8.2.2.2.1 | Uplink PDCH Allocation ..... | 59 | +| 8.2.2.2.2 | PACCH operation ..... | 59 | +| 8.2.2.2.3 | Neighbour cell power measurements ..... | 60 | +| 8.2.2.2.4 | Shifted USF operation ..... | 60 | +| 8.2.2.3 | Exclusive Allocation uplink RLC data block transfer ..... | 60 | +| 8.2.2.3.1 | (void) ..... | 60 | +| 8.2.2.3.2 | (void) ..... | 60 | +| 8.2.2.3.3 | (void) ..... | 60 | +| 8.2.2.3.4 | (void) ..... | 60 | +| 8.2.2.3.5 | (void) ..... | 60 | +| 8.2.2.3.6 | (void) ..... | 60 | +| 8.2.2.4 | Network initiated release of uplink TBF ..... | 60 | +| 8.2.2.5 | Abnormal cases ..... | 60 | +| 8.2.3 | Downlink RLC data block transfer ..... | 60 | +| 8.2.3.1 | General ..... | 60 | +| 8.2.3.1.0 | General ..... | 60 | +| 8.2.3.1.1 | Downlink resource reallocation ..... | 61 | +| 8.2.3.1.2 | (void) ..... | 61 | +| 8.2.3.2 | Downlink RLC data block transfer procedure ..... | 61 | +| 8.2.3.2.0 | General ..... | 61 | +| 8.2.3.2.1 | Abnormal cases ..... | 61 | +| 8.2.3.3 | Polling for Packet Downlink Ack/Nack ..... | 63 | +| 8.2.3.4 | Resource Reassignment for downlink ..... | 63 | +| 8.2.3.5 | Establishment of uplink TBF ..... | 64 | +| 8.2.3.5.0 | General ..... | 64 | +| 8.2.3.5.1 | Abnormal cases ..... | 65 | +| 8.2.3.6 | Network initiated abnormal release of downlink TBF ..... | 66 | +| 8.3 | Packet PDCH Release ..... | 66 | +| 8.4 | Procedure for measurement report sending in MAC-Shared state ..... | 66 | +| 8.5 | Network Controlled cell reselection procedures in MAC-Shared state ..... | 66 | +| 8.6 | Measurement Order procedures in MAC-Shared state ..... | 66 | +| 8.7 | PACKET CONTROL ACKNOWLEDGEMENT ..... | 66 | +| 8.8 | Abnormal cases ..... | 66 | +| 8.8.1 | General ..... | 66 | +| 8.8.2 | Abnormal release without retry ..... | 66 | +| 8.8.3 | Abnormal release with access retry ..... | 67 | +| 8.8.4 | Abnormal release with system information ..... | 67 | +| 8.8.5 | Abnormal release of an Uplink TBF with access retry ..... | 67 | +| 8.8.6 | Abnormal release of a Downlink TBF ..... | 67 | +| 8.9 | Network Assisted Cell Change procedures in MAC-Shared state ..... | 67 | +| 9 | Medium Access Control (MAC) procedures on DBPSCH ..... | 68 | +| 9.1 | General ..... | 68 | +| 9.2 | Transfer of RLC/MAC blocks ..... | 68 | +| 9.2.0 | General ..... | 68 | + +| | | | +|-------------|----------------------------------------------------------------------------|----| +| 9.2.1 | Dedicated allocation ..... | 69 | +| 9.2.1.1 | General..... | 69 | +| 9.2.1.2 | Performance requirements for TCH and DCCH TBF modes..... | 69 | +| 9.2.1.3 | Performance requirements for UDCH and CDCH TBF modes ..... | 70 | +| 9.2.2 | Transfer of RLC/MAC blocks on TCH..... | 71 | +| 9.2.3 | Transfer of RLC/MAC blocks on FACCH, SACCH and SDCCH ..... | 71 | +| 9.2.4 | Transfer of RLC/MAC blocks on PDTCH and PACCH..... | 72 | +| 9.2.4.1 | General..... | 72 | +| 9.2.4.1.1 | Downlink transfer..... | 72 | +| 9.2.4.1.1.1 | General ..... | 72 | +| 9.2.4.1.1.2 | Polling for Packet Downlink Ack/Nack ..... | 72 | +| 9.2.4.1.2 | Uplink transfer..... | 73 | +| 9.2.4.1.2.1 | General ..... | 73 | +| 9.2.4.1.2.2 | On receipt of a Packet Uplink Assignment message..... | 73 | +| 9.2.4.1.2.3 | Release of the USF ..... | 74 | +| 9.2.4.2 | Scheduling an inactive TBF on a DBPSCH ..... | 74 | +| 9.2.4.3 | Further USF handling ..... | 75 | +| 9.2.5 | Transfer of RLC/MAC blocks on UDCH, CDCH and ADCH ..... | 75 | +| 9.2.5.1 | General..... | 75 | +| 9.2.5.2 | Transport format combination (TFC) selection..... | 76 | +| 9.2.5.2.1 | General requirements ..... | 76 | +| 9.2.5.2.2 | Downlink..... | 76 | +| 9.2.5.2.3 | Uplink..... | 76 | +| 9.2.5.3 | Polling for PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 ..... | 76 | +| 9.3 | PACKET CONTROL ACKNOWLEDGEMENT ..... | 76 | +| 9.3a | Handover Access and Physical Information ..... | 77 | +| 9.3a.1 | Handover Access ..... | 77 | +| 9.3a.2 | Physical Information ..... | 77 | +| 9.4 | Abnormal cases ..... | 77 | +| 10 | Radio Link Control (RLC) procedures on PDTCH and PACCH ..... | 78 | +| 10.1 | General ..... | 78 | +| 10.2 | Procedures and parameters for peer-to-peer operation ..... | 78 | +| 10.2.1 | Send state variable V(S)..... | 78 | +| 10.2.2 | Control send state variable V(CS)..... | 78 | +| 10.2.3 | Acknowledge state variable V(A) ..... | 78 | +| 10.2.4 | Acknowledge state array V(B) ..... | 78 | +| 10.2.5 | Block sequence number BSN..... | 78 | +| 10.2.6 | Receive state variable V(R)..... | 78 | +| 10.2.7 | Receive window state variable V(Q)..... | 78 | +| 10.2.8 | Receive state array V(N) ..... | 78 | +| 10.2.9 | Starting sequence number (SSN) and received block bitmap (RBB)..... | 78 | +| 10.2.10 | Window Size ..... | 78 | +| 10.2.10a | RLC buffer..... | 78 | +| 10.2.11 | Compression..... | 79 | +| 10.2.12 | Segmentation of upper layer PDUs into RLC data units..... | 79 | +| 10.2.13 | Re-assembly of upper layer PDUs from RLC data units ..... | 79 | +| 10.2.14 | Segmentation of RLC/MAC control messages into RLC/MAC control blocks ..... | 79 | +| 10.2.15 | Re-assembly of RLC/MAC control messages from RLC/MAC control blocks ..... | 79 | +| 10.3 | Operation during RLC/MAC control message transfer ..... | 80 | +| 10.4 | Operation during RLC data block transfer..... | 80 | +| 10.4.1 | General ..... | 80 | +| 10.4.2 | Countdown procedure ..... | 80 | +| 10.4.3 | Delayed release of downlink Temporary Block Flow..... | 80 | +| 10.4.4 | Extended uplink TBF mode..... | 80 | +| 10.4.5 | Acknowledged mode operation..... | 80 | +| 10.4.5.1 | General..... | 80 | +| 10.4.5.2 | Additional functionality in acknowledged EGPRS TBF Mode..... | 80 | +| 10.4.5.3 | Establishment of Temporary Block Flow ..... | 80 | +| 10.4.5.4 | Operation of uplink Temporary Block Flow ..... | 80 | +| 10.4.5.5 | Release of uplink Temporary Block Flow..... | 81 | +| 10.4.5.6 | Operation of downlink Temporary Block Flow ..... | 81 | + +| | | | +|------------|--------------------------------------------------------------------------------|----| +| 10.4.5.7 | Release of downlink Temporary Block Flow ..... | 81 | +| 10.4.6 | Unacknowledged mode operation ..... | 81 | +| 10.4.6.1 | General ..... | 81 | +| 10.4.6.2 | Establishment of Temporary Block Flow ..... | 81 | +| 10.4.6.3 | Operation of uplink Temporary Block Flow ..... | 81 | +| 10.4.6.4 | Release of uplink Temporary Block Flow ..... | 81 | +| 10.4.6.5 | Operation of downlink Temporary Block Flow ..... | 81 | +| 10.4.6.6 | Release of downlink Temporary Block Flow ..... | 81 | +| 10.5 | Abnormal release cases ..... | 82 | +| 10.5.1 | Abnormal release with access retry ..... | 82 | +| 10.5.2 | Abnormal release with cell reselection ..... | 82 | +| 10.6 | Uplink TBF release in extended uplink TBF mode ..... | 82 | +| 11 | Radio Link Control (RLC) procedures on TCH, FACCH, SACCH, SDCCH and CDCH ..... | 83 | +| 11.1 | General ..... | 83 | +| 11.2 | Procedures and parameters for peer-to-peer operation ..... | 83 | +| 11.2.1 | Send state variable V(S) ..... | 83 | +| 11.2.2 | Control send state variable V(CS) ..... | 83 | +| 11.2.3 | Acknowledge state variable V(A) ..... | 84 | +| 11.2.4 | Acknowledge state array V(B) ..... | 84 | +| 11.2.5 | Block sequence number BSN ..... | 84 | +| 11.2.5.1 | Block sequence number for TCH TBF mode ..... | 84 | +| 11.2.5.2 | Block sequence number for DCCH TBF mode and CDCH TBF mode ..... | 84 | +| 11.2.6 | Reduced block sequence number RBSN ..... | 84 | +| 11.2.7 | Receive state variable V(R) ..... | 84 | +| 11.2.8 | Receive window state variable V(Q) ..... | 85 | +| 11.2.9 | Receive state array V(N) ..... | 85 | +| 11.2.10 | Starting sequence number (SSN) and received block bitmap (RBB) ..... | 85 | +| 11.2.11 | Window Size ..... | 85 | +| 11.2.11.1 | TCH ..... | 85 | +| 11.2.11.2 | FACCH, SACCH, SDCCH and CDCH ..... | 86 | +| 11.2.11a | RLC buffer ..... | 86 | +| 11.2.12 | Segmentation of upper layer PDUs into RLC data units ..... | 86 | +| 11.2.13 | Re-assembly of upper layer PDUs from RLC data units ..... | 86 | +| 11.2.14 | Segmentation of RLC/MAC control messages into RLC/MAC control blocks ..... | 86 | +| 11.2.15 | Re-assembly of RLC/MAC control messages from RLC/MAC control blocks ..... | 86 | +| 11.3 | Operation during RLC/MAC control message transfer ..... | 87 | +| 11.4 | Operation during RLC data block transfer ..... | 87 | +| 11.4.1 | General ..... | 87 | +| 11.4.2 | Acknowledged mode operation ..... | 88 | +| 11.4.2.1 | General ..... | 88 | +| 11.4.2.2 | On TCH ..... | 88 | +| 11.4.2.2.1 | General ..... | 88 | +| 11.4.2.2.2 | Uplink ..... | 88 | +| 11.4.2.2.3 | Downlink ..... | 88 | +| 11.4.2.3 | On FACCH, SACCH, SDCCH or CDCH ..... | 89 | +| 11.4.2.3.1 | General ..... | 89 | +| 11.4.2.3.2 | Uplink ..... | 89 | +| 11.4.2.3.3 | Downlink ..... | 89 | +| 11.4.3 | Unacknowledged mode operation ..... | 90 | +| 11.4.3.1 | General ..... | 90 | +| 11.4.3.2 | On TCH ..... | 90 | +| 11.4.3.2.1 | Uplink ..... | 90 | +| 11.4.3.2.2 | (void) ..... | 90 | +| 11.4.3.3 | On FACCH, SACCH, SDCCH or CDCH ..... | 90 | +| 11.4.3.3.1 | Uplink ..... | 90 | +| 11.4.3.3.2 | Downlink ..... | 90 | +| 11.4.4 | Transparent mode operation (TCH TBF mode only) ..... | 90 | +| 11a | Radio Link Control (RLC) procedures for FLO on UDCH, ADCH ..... | 91 | +| 11a.1 | General ..... | 91 | +| 11a.2 | Procedures and parameters for peer-to-peer operation ..... | 91 | + +| | | | +|-------------|----------------------------------------------------------------------------|-----| +| 11a.2.1 | Send state variable V(S) ..... | 91 | +| 11a.2.2 | Control send state variable V(CS)..... | 91 | +| 11a.2.3 | Acknowledge state variable V(A) ..... | 91 | +| 11a.2.4 | Acknowledge state array V(B) ..... | 91 | +| 11a.2.5 | Block sequence number BSN..... | 91 | +| 11a.2.6 | Reduced block sequence number RBSN ..... | 91 | +| 11a.2.7 | Receive state variable V(R)..... | 91 | +| 11a.2.8 | Receive window state variable V(Q)..... | 92 | +| 11a.2.9 | Receive state array V(N) ..... | 92 | +| 11a.2.10 | Starting sequence number (SSN) and received block bitmap (RBB)..... | 92 | +| 11a.2.10.1 | General..... | 92 | +| 11a.2.10.2 | Polling ..... | 92 | +| 11a.2.10.3 | Determination of SSN and generation of the reported bitmap ..... | 92 | +| 11a.2.10.4 | Interpretation of the bitmap ..... | 93 | +| 11a.2.11 | Window Size ..... | 94 | +| 11a.2.11a | RLC buffer..... | 94 | +| 11a.2.12 | Segmentation of upper layer PDUs into RLC data units..... | 94 | +| 11a.2.13 | Re-assembly of upper layer PDUs from RLC data units ..... | 94 | +| 11a.2.14 | Segmentation of RLC/MAC control messages into RLC/MAC control blocks ..... | 94 | +| 11a.2.15 | Re-assembly of RLC/MAC control messages from RLC/MAC control blocks ..... | 94 | +| 11a.3 | Operation during RLC/MAC control message transfer ..... | 95 | +| 11a.4 | Operation during RLC data block transfer..... | 95 | +| 11a.4.1 | General ..... | 95 | +| 11a.4.2 | Acknowledged mode operation..... | 96 | +| 11a.4.2.1 | General..... | 96 | +| 11a.4.2.2 | Uplink ..... | 96 | +| 11a.4.2.3 | Downlink ..... | 96 | +| 11a.4.3 | Unacknowledged mode operation..... | 97 | +| 11a.4.3.1 | General..... | 97 | +| 11a.4.3.2 | Uplink..... | 97 | +| 11a.4.3.3.2 | Downlink..... | 97 | +| 11a.4.4 | Transparent mode operation ..... | 97 | +| 12 | RLC/MAC block structure ..... | 97 | +| 12.1 | RLC/MAC block structure ..... | 97 | +| 12.2 | RLC/MAC block format conventions ..... | 97 | +| 12.3 | Spare bits..... | 97 | +| 12.4 | GPRS RLC data blocks (PDTCH) ..... | 97 | +| 12.4.1 | Downlink RLC data block..... | 97 | +| 12.4.2 | Uplink RLC data block..... | 98 | +| 12.5 | RLC/MAC control blocks (PACCH)..... | 98 | +| 12.6 | EGPRS RLC data blocks and RLC/MAC headers (PDTCH)..... | 99 | +| 12.6.1 | General ..... | 99 | +| 12.6.2 | EGPRS downlink RLC data block ..... | 99 | +| 12.6.3 | EGPRS uplink RLC data block ..... | 99 | +| 12.6.4 | EGPRS downlink RLC/MAC header..... | 99 | +| 12.6.5 | EGPRS uplink RLC/MAC header..... | 99 | +| 12.7 | RLC/MAC block formats on FACCH, SACCH, SDCCH and CDCH ..... | 100 | +| 12.7.1 | RLC/MAC block ..... | 100 | +| 12.7.2 | Downlink RLC/MAC block for data transfer..... | 100 | +| 12.7.3 | Uplink RLC/MAC block for data transfer..... | 101 | +| 12.7.4 | RLC/MAC block for control message transfer ..... | 101 | +| 12.8 | RLC/MAC block format on TCH (NT-RLC) ..... | 101 | +| 12.8.1 | RLC/MAC block ..... | 101 | +| 12.8.1.1 | General..... | 101 | +| 12.8.1.2 | RLC/MAC block for E-TCH/F28.8 coding scheme..... | 102 | +| 12.8.1.3 | RLC/MAC block for E-TCH/F32.0 coding scheme..... | 102 | +| 12.8.1.4 | RLC/MAC block for E-TCH/F43.2 coding scheme..... | 102 | +| 12.8.2 | Downlink RLC/MAC block for data transfer..... | 103 | +| 12.8.3 | Uplink RLC/MAC block for data transfer..... | 103 | +| 12.8.4 | RLC/MAC block for control message transfer ..... | 103 | +| 12.8a | RLC/MAC block for control message transfer on ADCH..... | 103 | + +| | | | +|------------------------|---------------------------------------------------------------------------------|-----| +| 12.8a.1 | Downlink RLC/MAC control block format ..... | 103 | +| 12.8a.2 | Uplink RLC/MAC control block format ..... | 104 | +| 12.8b | RLC/MAC blocks for URB data transfer on UDCH ..... | 104 | +| 12.8b.1 | Downlink RLC/MAC block for data transfer..... | 104 | +| 12.8b.1.1 | RLC unacknowledged mode..... | 104 | +| 12.8b.1.2 | RLC acknowledged mode..... | 104 | +| 12.8b.1.3 | RLC transparent mode ..... | 105 | +| 12.8b.2 | Uplink RLC/MAC block for data transfer..... | 105 | +| 12.8b.2.1 | RLC unacknowledged mode..... | 105 | +| 12.8b.2.2 | RLC acknowledged mode..... | 105 | +| 12.8b.2.3 | RLC transparent mode ..... | 105 | +| 12.9 | Header fields ..... | 106 | +| 12.9.1 | General ..... | 106 | +| 12.9.2 | Payload Type (PT) field ..... | 106 | +| 12.9.3 | Polling (P) bit ..... | 106 | +| 12.9.4 | Reduced Radio Bearer identity (RRBid) field..... | 106 | +| 12.9.5 | More (M) bit and Extension (E) bit ..... | 107 | +| 12.9.6 | Extension bits (Ebis) bit ..... | 107 | +| 12.9.7 | Stall Indicator (SI) bit ..... | 107 | +| 12.9.8 | Ack Indicator (AI) field ..... | 107 | +| 12.9.9 | Ack/Nack Description field ..... | 108 | +| 12.9.10 | G-RNTI indicator (GI) bit ..... | 108 | +| 12.9.11 | Segmentation (S) bit ..... | 108 | +| 12.9.12 | Reduced Block Sequence Number (RBSN) bit..... | 108 | +| 12.9.13 | (void) ..... | 109 | +| 12.9.14 | Radio Transaction Identifier (RTI) field ..... | 109 | +| 12.9.15 | Block Sequence Number (BSN) field ..... | 109 | +| 12.9.16 | Radio Bearer Identity (RB Id) field..... | 109 | +| 12.9.17 | Signalling Radio Bearer Identity (SRB Id) field ..... | 109 | +| 12.9.18 | GERAN Radio Network Temporary Identity Extension (G-RNTI Extension) field ..... | 109 | +| 12.9.19 | Length Indicator (LI) field..... | 109 | +| 12.9.20 | PFI Indicator (PI) field ..... | 110 | +| 12.9.21 | HFN Least Significant Bit (HFN_LSB) field..... | 110 | +| 13 | Ciphering..... | 111 | +| 13.1 | General ..... | 111 | +| 13.2 | Applicability of ciphering ..... | 111 | +| 13.3 | Ciphering at RLC sublayer..... | 111 | +| 13.3.1 | General ..... | 111 | +| 13.3.2 | Parameter settings..... | 111 | +| 13.3.2.1 | Input parameters to the ciphering algorithm..... | 111 | +| 13.3.2.2 | Handling of the HFN ..... | 112 | +| 13.3.3 | Ciphering of RLC PDUs in non-transparent RLC mode..... | 112 | +| 13.4 | Ciphering at MAC sublayer ..... | 113 | +| 13.4.1 | General ..... | 113 | +| 13.4.2 | Parameter settings..... | 113 | +| 13.4.2.1 | Input parameters to the ciphering algorithm..... | 113 | +| 13.4.2.2 | Handling of the HFN ..... | 114 | +| 13.4.2.2.1 | Ciphering in transparent RLC mode ..... | 114 | +| 13.4.2.2.2 | Ciphering of RLC/MAC control messages ..... | 115 | +| 13.4.3 | Ciphering of RLC/MAC control messages ..... | 115 | +| 13.4.4 | Ciphering of RLC PDUs in transparent RLC mode..... | 116 | +| 14 | RLC suspension, stop and re-establishment procedures..... | 116 | +| 14.1 | General ..... | 116 | +| 14.2 | Local suspend/resume function (NT-RLC)..... | 116 | +| 14.3 | Stop/continue function (NT-RLC) ..... | 117 | +| 14.4 | RLC re-establishment function (NT-RLC)..... | 118 | +| Annex A (informative): | Change History ..... | 119 | + +--- + +## 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 + +## 1.1 General + +The present document specifies procedures for the following layers of the radio interface (*Um* reference point), the interface between the GSM/EDGE Radio Access Network (GERAN) and the Mobile Station (MS) in GERAN *Iu mode*: + +- Radio Link Control (RLC). +- Medium Access Control (MAC), including Physical Link Control functions. + +## 1.2 Related documents + +The following documents provide information related to the present document: + +- 3GPP TS 43.051 is an overall description of the GSM/EDGE Radio Access Network (GERAN) in *Iu mode*. +- 3GPP TS 44.003 specifies channel types, access capabilities and channel configurations at the *Um* reference point. +- 3GPP TS 44.004 specifies services offered by the physical layer of the *Um* reference point. It also specifies control channels. RLC and MAC use these services and control channels. +- 3GPP TS 24.007 specifies, in general terms, this protocol's structured functions, its procedures and its relationship with other layers and entities. It also specifies the basic message format and error handling applied by layer 3 protocols. +- 3GPP TS 44.118 specifies the RRC procedures when operating in *Iu mode*. +- 3GPP TS 44.060 specifies RLC/MAC procedures specific to *A/Gb mode* as well as the procedures that are common to both *A/Gb mode* and *Iu mode*. It also specifies the messages and Information Elements for both modes. +- 3GPP TS 51.010 specifies test procedures for radio-interface signalling. + +## 1.3 Use of logical control channels + +3GPP TS 45.002 defines the following logical control channels: + +- Broadcast Control Channel (BCCH): downlink only, used to broadcast Cell specific information. +- Packet Broadcast Control Channel (PBCCH): downlink only, used to broadcast Cell specific information. +- Packet Paging Channel (PPCH): downlink only, used to send page requests to Mobile Stations (MSs). +- Packet Random Access Channel (PRACH): uplink only, used to request GPRS resources. +- Packet Access Grant Channel (PAGCH): downlink only, used to allocate GPRS resources. +- Packet Associated Control Channel (PACCH): bi-directional, associated with a Temporary Block Flow (TBF). +- Packet Timing advance control channel uplink (PTCCH/U): used to transmit random access bursts to allow estimation of the timing advance for one MS in transfer state. +- Packet Timing advance control channel downlink (PTCCH/D): used to transmit timing advance updates for several MS. One PTCCH/D is paired with several PTCCH/U's. + +## 1.4 Use of logical traffic channels + +3GPP TS 45.002 defines the following logical traffic channels used by RLC and MAC: + +- Traffic Channel (TCH): bidirectional, carries encoded speech or user data using GMSK on a dedicated basic physical subchannel (DBPSCH). TCH can be full-rate (TCH/F) or half-rate (TCH/H). + +- Octal Traffic Channel (O-TCH): bidirectional, carries encoded speech using 8-PSK on a DBPSCH. O-TCH can be full-rate (O-TCH/F) or half-rate (O-TCH/H). +- Enhanced Traffic Channel (E-TCH): bidirectional, carries user data using 8-PSK on a DBPSCH. +- Packet Data Traffic Channel (PDTCH): downlink or uplink, carries user data using GMSK or 8-PSK on a shared basic physical subchannel (SBPSCH) or a DBPSCH. PDTCHs can be full-rate (PDTCH/F) or half-rate (PDTCH/H). + +## 1.4a Use of transport channels + +For the flexible layer one (FLO) 3GPP TS 45.002 defines the following transport channel type: + +- Dedicated Channel (DCH): carries user or control data using GMSK or 8-PSK on a DBPSCH. A mobile station may have one or more transport channels of type DCH active at the same time in each direction. + +In the present document, the following notations are used: + +- UDCH: refers to a transport channel of type DCH used exclusively for carrying RLC/MAC blocks for data transfer belonging to user-plane; +- CDCH: refers to a transport channel of type DCH used exclusively for carrying RLC/MAC blocks for data transfer belonging to control-plane. The signalling TFC (see 3GPP TS 44.118) shall be used when CDCH is active; +- ADCH: refers to a transport channel of type DCH used exclusively for carrying RLC/MAC blocks for control message transfer. The signalling TFC (see 3GPP TS 44.118) shall be used when ADCH is active. + +## 1.5 Conventions + +Unless explicitly stated otherwise, the following conventions apply: + +- The notations "further study", "FS" or "FFS" indicate the annotated text is not normative. +- References to "PDCH" also apply to "SBPSCH" and vice-versa. + +--- + +## 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.003: "Numbering, addressing and identification". +- [3] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM system". +- [4] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [5] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". +- [6] 3GPP TS 44.004: "Layer 1 - General requirements". + +- [7] 3GPP TS 44.118: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol Iu mode". +- [8] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [9] 3GPP TS 45.003: "Channel coding". +- [10] 3GPP TS 45.008: "Radio subsystem link control". +- [11] 3GPP TS 45.010: "Radio subsystem synchronization". +- [12] 3GPP TS 51.010-1: "Mobile Station (MS) conformance specification; Part 1: Conformance specification". +- [13] 3GPP TS 51.021: "GSM radio aspects base station system equipment specification". +- [14] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [15] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)". +- [16] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [17] 3GPP TS 43.051: "GSM/EDGE Radio Access Network (GERAN); Overall Description; Stage 2". +- [18] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC) protocol". +- [19] 3GPP TS 51.010-2: "Mobile Station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (ICS) proforma specification". +- [20] 3GPP TS 51.010-3: "Mobile Station (MS) conformance specification; Part 3: Layer 3 (L3) Abstract Test Suite (ATS)". +- [21] 3GPP TS 51.010-4: "Mobile Station (MS) conformance specification; Part 4: SIM application toolkit conformance specification". +- [22] 3GPP TS 35.201: "Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specifications". +- [23] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [24] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [25] 3GPP TS 45.005: "Radio transmission and reception". +- [26] 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2". +- [27] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General Aspects". +- [28] 3GPP TR 45.902: "Flexible Layer One". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 44.060 and the following apply: + +**Active transport channel:** a transport channel is active during a TTI if it carries an RLC/MAC block. This definition applies to FLO only. + +**Block period:** sequence of timeslots on a SBPSCH or a DBPSCH used to convey one radio block. There are 4 timeslots in this sequence for PDTCH, PACCH, SACCH, SDCCH, TCH/AHS, E-FACCH. There are 6 timeslots in this sequence for FACCH/H. There are 8 timeslots in this sequence for TCH/AFS and FACCH/F. There are 22 timeslots in this sequence for (E-)TCH/F. + +**CDCH TBF Mode:** refers to a TBF belonging to a signalling radio bearer and using FLO. + +**DCCH TBF mode:** refers to a TBF mapped onto a FACCH, SACCH or SDCCH. + +**Radio block:** sequence of normal bursts carrying one RLC/MAC protocol data unit (see 3GPP TS 44.004). (The one exception is a radio block occasionally used on PACCH consisting of a sequence of four access bursts, each carrying a repetition of one short RLC/MAC block.). There are 4 normal bursts in this sequence for PDTCH, PACCH, SACCH, SDCCH, TCH/AHS, E-FACCH. There are 6 normal bursts in this sequence for FACCH/H. There are 8 normal bursts in this sequence for TCH/AFS and FACCH/F. There are 22 normal bursts in this sequence for (E-)TCH/F. + +**RLC non-transparent mode:** refers to either RLC acknowledged mode or RLC unacknowledged mode. + +**TCH TBF mode:** refers to a TBF mapped onto a TCH. + +**Transport format:** configuration of a transport channel, including for instance block size and CRC. This definition applies to FLO only. + +**Transport format combination:** allowed combination of transport format(s) of the different transport channels that are multiplexed together on a basic physical subchannel + +**Signalling TFC:** transport format combination that shall be used for signalling (ADCH, CDCH). It may also be used for user-plane data (UDCH). On each DBPSCH, the signalling TFC is the lowest TFC in the TFCS of this DBPSCH (see 3GPP TS 44.118). + +**Transport format combination set:** set of allowed transport format combinations on a basic physical subchannel + +**Transport format set:** set of all transport formats defined for a particular transport channel. + +**Transmission time interval:** rate at which RLC/MAC blocks are exchanged between the physical layer and the MAC sublayer on a transport channel: 20ms. This definition applies to FLO only. + +**UDCH TBF mode:** refers to a TBF belonging to a user-plane radio bearer and using FLO. + +NOTE: *Iu mode* specific definitions that are not used in 3GPP TS 44.060 should be added here. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|--------------|-------------------------------------------------------------| +| A | Interface between a BSS and a 2G MSC | +| Gb | Interface between a BSS and a 2G SGSN | +| Iu | Interface between a BSS or an RNC and a 3G MSC or a 3G SGSN | +| Iu-cs | Interface between a BSS or an RNC and a 3G MSC | +| Iu-ps | Interface between a BSS or an RNC and a 3G SGSN | +| Um | Interface between an MS and the GERAN | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and 3GPP TS 43.064, and the following apply: + +| | | +|--------------|--------------------------------------| +| ADCH | Associated DCH | +| ARQ | Automatic Repeat reQuest | +| BCCH | Broadcast Control CHannel | +| BSS | Base Station Subsystem | +| CBCH | Cell Broadcast CHannel | +| CCN | Cell Change Notification | +| CDCH | Control-plane DCH | +| CN | Core Network | +| CS- i | GPRS Coding Scheme i | +| DBPSCH | Dedicated Basic Physical Sub CHannel | +| DCH | Dedicated CHannel | +| ECSD | Enhanced Circuit Switched Data | + +| | | +|---------------|---------------------------------------------| +| EDGE | Enhanced Data rates for Global Evolution | +| EGPRS | Enhanced General Packet Radio Service | +| FACCH | Fast Associated Control CHannel | +| FLO | Flexible Layer One | +| GERAN | GSM/EDGE Radio Access Network | +| GPRS | General Packet Radio Service | +| GRA | GERAN Registration Area | +| G-RNTI | GERAN Radio Network Temporary Identity | +| GSM | Global System for Mobile communications | +| HFN | Hyper Frame Number | +| IMSI | International Mobile Subscriber Identity | +| LCS | LoCation Services | +| MAC | Medium Access Control | +| MCS- i | EGPRS Modulation and Coding Scheme i | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| NAS | Non Access Stratum | +| NSAPI | Network-layer SAPI | +| NT-RLC | RLC non-transparent mode | +| PBCCH | Packet BCCH | +| PDCH | Packet Data CHannel | +| PDCP | Packet Data Convergence Protocol | +| PDP | Packet Data Protocol | +| PDTCH | Packet Data TCH | +| PDU | Protocol Data Unit | +| PLMN | Public Land Mobile Network | +| PTCCH | Packet Timing-advance Control CHannel | +| P-TMSI | Packet TMSI | +| QoS | Quality of Service | +| RB | Radio Bearer | +| RBid | Radio bearer identity | +| RLC | Radio Link Control | +| RNC | Radio Network Controller | +| RR | Radio Resource | +| RRBid | Reduced RBid | +| RRC | Radio Resource Control | +| SACCH | Slow Associated Control CHannel | +| SAP | Service Access Point | +| SAPI | Service Access Point Identifier | +| SBPSCH | Shared Basic Physical Sub CHannel | +| SDCCH | Stand-alone Dedicated Control CHannel | +| SDU | Service Data Unit | +| SGSN | Serving GPRS Support Node | +| SRB | Signalling Radio Bearer | +| TBF | Temporary Block Flow | +| TCH | Traffic Channel | +| TF | Transport Format | +| TFC | Transport Format Combination | +| TFCS | Transport Format Combination Set | +| TFS | Transport Format Set | +| TMSI | Temporary Mobile Subscriber Identity | +| TrCH | Transport CHannel | +| T-RLC | RLC transparent mode | +| TTI | Transport Time Interval | +| UDCH | User-plane DCH | +| UMTS | Universal Mobile Telecommunication System | +| URB | User Radio Bearer | +| USF | Uplink State Flag | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# 4 Layered overview of radio interface + +## 4.0 Protocol architecture + +The protocol architecture for the radio interface is shown in figure 4.1 where the flexible layer one (FLO) is not represented. Figure 4.2 represents the protocol architecture in relation to FLO only. + +The RLC/MAC function provides a service to PDCP for User plane data, to RRC for Control plane data and to the application layer of the CS User plane. + +![Figure 4.1: Radio Interface Protocol architecture. This diagram shows a layered protocol stack. At the top is the RRC layer. Below it, the User plane consists of two PDCP units, which connect to four RLC units. The Control plane consists of the RRC layer connecting to two RLC units. All RLC units connect to a single MAC layer. The MAC layer is associated with a set of logical channels: FACCH, SACCH, SDCCH, TCH, PBCCH, PCCCH, PACCH, PDTCH, and 'Logical channels ...'. All logical channels connect to the bottom PHY layer.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +Figure 4.1: Radio Interface Protocol architecture. This diagram shows a layered protocol stack. At the top is the RRC layer. Below it, the User plane consists of two PDCP units, which connect to four RLC units. The Control plane consists of the RRC layer connecting to two RLC units. All RLC units connect to a single MAC layer. The MAC layer is associated with a set of logical channels: FACCH, SACCH, SDCCH, TCH, PBCCH, PCCCH, PACCH, PDTCH, and 'Logical channels ...'. All logical channels connect to the bottom PHY layer. + +Figure 4.1: Radio Interface Protocol architecture + +![Figure 4.2: Radio Interface Protocol architecture with FLO only. This diagram shows a layered protocol stack. At the top, the Control-plane contains the RRC layer, and the User-plane contains two PDCP units. Both connect to four RLC units. The RLC units connect to Transport Channels (represented by ovals), which then connect to the MAC layer. The MAC layer connects to Transport Block Functions (TBFs), which finally connect to the PHY layer containing the FLO (Flexible Layer One) unit. Blue lines on the left indicate control signaling from the RRC layer down through the stack.](29f586959675cafdf81cf934954908eb_img.jpg) + +Figure 4.2: Radio Interface Protocol architecture with FLO only. This diagram shows a layered protocol stack. At the top, the Control-plane contains the RRC layer, and the User-plane contains two PDCP units. Both connect to four RLC units. The RLC units connect to Transport Channels (represented by ovals), which then connect to the MAC layer. The MAC layer connects to Transport Block Functions (TBFs), which finally connect to the PHY layer containing the FLO (Flexible Layer One) unit. Blue lines on the left indicate control signaling from the RRC layer down through the stack. + +Figure 4.2: Radio Interface Protocol architecture with FLO only + +## 4.1 Layer services + +The RLC/MAC sublayer provides services for the transfer over the physical layer between the network and mobile station of upper layer PDUs for one mobile station when operating on a dedicated basic physical subchannel, or for one or more mobile stations when operating on a shared basic physical subchannel. + +The RLC function provides the following services to the upper layers: + +- **Transparent data transfer:** This service transmits higher layer PDUs without adding any protocol information. +- **Acknowledged data transfer:** This service transmits higher layer PDUs and guarantees delivery to the peer entity. +- **Unacknowledged data transfer:** This service transmits higher layer PDUs without guaranteeing delivery to the peer entity. +- **Notification of unrecoverable errors:** RLC notifies the upper layer of errors that cannot be resolved by RLC itself by normal exception handling procedures. +- **Notification of discard:** RLC notifies the upper layer of the higher layer PDUs (RLC SDUs) it discards. +- **Suspend:** The RLC entity does not transmit any new RLC PDUs to the lower layer. +- **Resume:** The RLC entity resumes data transmission. +- **Stop:** The RLC entity does not transmit any RLC PDUs to the lower layer and does not receive any PDUs from the lower layer. +- **Continue:** The RLC entity resumes data transmission and reception. +- **Re-establishment:** The RLC entity is re-established. + +The MAC function provides the following service to the upper layer: + +- **Data transfer.** + +## 4.2 Layer functions + +### 4.2.1 RLC function + +The functions provided by the RLC are given in table 4.2.1.1. Transparent RLC mode provides no functionality. + +**Table 4.2.1.1: RLC Functions** + +| | Acknowledged mode RLC | Unacknowledged mode RLC | Transparent mode RLC | +|--------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------|----------------------| +| Segmentation of upper layer PDUs into RLC data blocks | X | X | | +| Concatenation of upper layer PDUs into RLC data blocks | X | X | | +| Padding to fill out RLC data block | X | X | | +| Backward Error Correction (BEC) procedure enabling the selective retransmission of RLC data blocks | X | | | +| Discard of RLC SDUs not yet segmented into RLC PDUs, according to the delay requirements of the associated Radio Bearers | X | | | +| Reassembly of RLC data blocks into upper layer PDUs | X | X | | +| In-sequence delivery of upper layer PDUs | X | X | | +| Link Adaptation | X | X | | +| Ciphering | X | X | | +| Sequence number check to detect lost RLC blocks | X | X | | + +## 4.2.2 MAC layer function + +The functions of the MAC layer include: + +- **Configuring the mapping between logical channels and basic physical subchannels:** The MAC layer is responsible for configuring the mapping of logical channel(s) onto the appropriate basic physical subchannel(s). +- **Mapping between TBFs and transport channels.** When FLO is used, the MAC layer is responsible for mapping TBF(s) onto the appropriate transport channel(s). +- **Selecting logical channels to be used for each signalling radio bearer service:** The MAC layer is responsible for mapping SRBs onto logical channels. There are a set of rules defined for this mapping (see sub-clause 5.6) which shall be used in the uplink and should be used in the downlink. The mapping is dependent on the SRB to be sent, the MAC state, and the logical channels available. The SFACCH may be selected in preference to the PDTCH if a TBF is not already established for the SRB. In the downlink there is an additional requirement that the PHYSICAL INFORMATION message is always sent on the FACCH. +- **Selecting transport channel to be used for signalling radio bearer service:** When FLO is used, the MAC layer is responsible for mapping some SRBs onto transport channels. There is a set of rules defined for this mapping (see sub-clause 5.6) which shall be used in the uplink and should be used in the downlink. The mapping is dependent on the SRB to be sent, the MAC state, and the logical channels and transport channels available. When SRB data is sent using FLO on a DBPSCH/F, the signalling TFC shall be used. When SRB data is sent using FLO on a DBPSCH/H, the MAC layer shall send every RLC/MAC block for data transfer twice in a row. The corresponding first and second transport blocks shall use the signalling TFC. +- **Selecting logical channels to be used for each user radio bearer service:** The logical channels used by the MAC for user radio bearers are set up by configuration from RRC. +- **Selecting transport channels to be used for each user radio bearer service:** When FLO is used, the transport channels used by the MAC for user radio bearers are set up by configuration from RRC. +- **Selection of the appropriate transport format per transport channel.** When FLO is used, the MAC layer is responsible for selecting the appropriate transport format for each transport channel within the transport format set configured by RRC for each transport channel so that the resulting transport format combination belongs to the transport format combination set configured by RRC. +- **Assignment, reconfiguration and release of shared radio resources for a TBF:** The MAC layer may handle the assignment of radio resources needed for a TBF including needs from both the control and user plane. The MAC layer may reconfigure radio resources of a TBF. +- **MS measurement reporting and control of the reporting:** The MAC layer is responsible for sending information that control the MS measurement reporting when using PBCCH or PACCH channels. The MAC layer also performs the reporting of the measurements from the MS to the network using PACCH. +- **Broadcasting/listening of/to PBCCH and PCCCH:** The MAC layer broadcasts/listens (to) the PBCCH of the serving cell for the sending/decoding of packet system information messages. The MAC layer also sends paging information on the PCCCH or and monitors the paging occasions according to the DRX cycle. Within the Mobile Station, the MAC layer notifies the RRC layer when receiving a paging message; within the network, it is responsible for aggregating and sending paging messages addressed to one or more Mobile Stations when received from the RRC layer. +- **Timing advance control:** The MAC layer controls the operation of timing advance on shared basic physical subchannels. +- **Ciphering and deciphering** (only in combination with transparent RLC mode). +- **Priority handling between data flows of one MS.** When FLO is used, the MAC layer is responsible for prioritization between data flows of one MS on DBPSCH. + +When the MAC layer is providing services to a non-transparent RLC mode entity, the MAC layer supports the following additional functions: + +- **Ciphering.** +- **Identification of different traffic flows of one or more MSs on the basic physical subchannels:** Inband identification is needed to address a flow to an MS in the downlink or identify a flow from an MS in the uplink. +- **Multiplexing/demultiplexing of higher layer PDUs:** This may include priority handling between data flows of one or more mobile stations, e.g. by attributes of Radio Bearer services. +- **Multiplexing/demultiplexing user and control plane data to/from the physical layer for PDTCHs:** The MAC layer is responsible for multiplexing/demultiplexing RLC data blocks carried on PDTCH and RLC/MAC control blocks carried on PACCH. +- **Scheduling of RLC/MAC data and control PDUs delivered to the physical layer on shared basic physical subchannels:** This includes USF and RRBP field monitoring for uplink transfer and sharing radio resources on the downlink. +- **Splitting/recombining:** This includes splitting/recombining of the RLC/MAC PDU flow belonging to one or more TBF(s) onto/from several shared logical channels. This function does not apply for RLC/MAC control blocks. + +## 4.3 Service primitives + +### 4.3.1 MAC to Physical Layer Primitives + +These are defined in 3GPP TS 44.004. + +### 4.3.2 PDCP to RLC Primitives + +#### 4.3.2.1 Primitives + +The primitives between PDCP and RLC are shown in table 4.3.2.1.1. + +**Table 4.3.2.1.1: Primitives between RLC and upper layers** + +| Generic Name | Parameters | | | | +|--------------------|----------------|-----------------------|-------------|-------------| +| | Req. | Ind. | Resp. | Conf. | +| RLC-AM-DATA | Data, CNF, MUI | Data | Not Defined | Status, MUI | +| RLC-UM-DATA | Data | Data | Not Defined | Not Defined | +| RLC-TM-DATA | Data | Data, Error_Indicator | Not Defined | Not Defined | + +Each Primitive is defined as follows: + +#### **RLC-AM-DATA-Req/Ind/Conf** + +- RLC-AM-DATA-Req is used by upper layers to request transmission of an RLC SDU in acknowledged mode. +- RLC-AM-DATA-Ind is used by the AM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in acknowledged mode. +- RLC-AM-DATA-Conf is used by the AM RLC entity to confirm to upper layers the reception of an RLC SDU by the peer-RLC AM entity or to inform the upper layers of a discarded RLC SDU. + +#### **RLC-UM-DATA-Req/Ind/Conf** + +- RLC-UM-DATA-Req is used by upper layers to request transmission of an RLC SDU in unacknowledged mode. +- RLC-UM-DATA-Ind is used by the UM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in unacknowledged mode. + +#### **RLC-TM-DATA-Req/Ind/Conf** + +- RLC-TM-DATA-Req is used by upper layers to request transmission of an RLC SDU in transparent mode. +- RLC-TM-DATA-Ind is used by the TM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in transparent mode. + +#### 4.3.2.2 Primitive parameters + +The following parameters are used in the primitives: + +- 1) The parameter Data is the RLC SDU that is mapped onto the Data field in RLC PDUs. +- 2) The parameter Confirmation Request (CNF) indicates whether the transmitting side of the AM RLC entity needs to confirm the reception of the RLC SDU by the peer-RLC AM entity. If required, once all AMD PDUs that make up the RLC SDU are positively acknowledged by the receiving AM RLC entity, the transmitting AM RLC entity notifies upper layers. +- 3) The parameter Message Unit Identifier (MUI) is an identity of the RLC SDU, which is used to indicate which RLC SDU that is confirmed with the RLC-AM-DATA-Conf. Primitive. +- 4) The Error\_Indicator parameter indicates that the RLC SDU is erroneous. +- 5) The parameter Status is only applicable for AM operation. This parameter indicates whether a RLC SDU is successfully transmitted or discarded. + +#### 4.3.3 RRC to RLC Primitives + +##### 4.3.3.1 Primitives + +The primitives between RRC and RLC are shown in table 4.3.3.1. + +**Table 4.3.3.1: Primitives between RRC and RLC** + +| Generic Name | Parameters | | | | +|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------------| +| | Req. | Ind. | Resp. | Conf. | +| RLC-AM-DATA | Data, CNF, MUI, DiscardReq | Data | Not Defined | Status, MUI | +| RLC-UM-DATA | Data | Data | Not Defined | Not Defined | +| CRLC-CONFIG | E/R, Stop (UM/AM only), Continue (UM/AM only), Ciphering Elements (UM/AM only), TM_parameters (TM only), UM_parameters (UM only-SDU discard, EGPRS window size), AM_parameters (AM only –SDU discard, resegment bit, EGPRS window size) | Not Defined | Not Defined | Not Defined | +| CRLC-SUSPEND
(UM/AM only) | N | Not Defined | Not Defined | V(S) (AM/UM only) | +| CRLC-RESUME
(UM/AM only) | No Parameter | Not Defined | Not Defined | Not Defined | + +Each Primitive is defined as follows: + +##### **RLC-AM-DATA-Req/Ind/Conf** + +- RLC-AM-DATA-Req is used by upper layers to request transmission of an RLC SDU in acknowledged mode. +- RLC-AM-DATA-Ind is used by the AM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in acknowledged mode. +- RLC-AM-DATA-Conf is used by the AM RLC entity to confirm to upper layers the reception of an RLC SDU by the peer-RLC AM entity. + +##### **RLC-UM-DATA-Req/Ind/Conf** + +- RLC-UM-DATA-Req is used by upper layers to request transmission of an RLC SDU in unacknowledged mode. +- RLC-UM-DATA-Ind is used by the UM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in unacknowledged mode. + +#### **CRLC-CONFIG-Req** + +This primitive is used by upper layers to establish, re-establish, release, stop, continue or modify the RLC. Ciphering elements are included for UM and AM operation. + +#### **CRLC-SUSPEND-Req/Conf** + +- CRLC-SUSPEND-Req is used by upper layers to suspend the UM or AM RLC entity. +- CRLC-SUSPEND-Conf is used by the UM or AM RLC entity to confirm that the entity is suspended. + +#### **CRLC-RESUME-Req** + +This primitive is used by upper layers to resume the UM or AM RLC entity after the UM or AM RLC entity has been suspended. + +### **4.3.3.2 Primitive parameters** + +Following parameters are used in the primitives: + +- 1) The parameter Data is the RLC SDU that is mapped onto the Data field in RLC PDUs. +- 2) The parameter Confirmation Request (CNF) indicates whether the transmitting side of the AM RLC entity needs to confirm the reception of the RLC SDU by the peer-RLC AM entity. If required, once all AMD PDUs that make up the RLC SDU are positively acknowledged by the receiving AM RLC entity, the transmitting AM RLC entity notifies upper layers. +- 3) The parameter Message Unit Identifier (MUI) is an identity of the RLC SDU, which is used to indicate which RLC SDU that is confirmed with the RLC-AM-DATA-Conf. Primitive. +- 4) The parameter E/R indicates establishment, re-establishment, release or modification of an RLC entity, where re-establishment is applicable to AM and UM RLC entities only. +- 5) The parameter Ciphering Elements are only applicable for UM and AM operations. These parameters are Ciphering Key, Activation Time (Sequence Number (BSN) to activate a new ciphering configuration) and HFN (Hyper Frame Number). +- 6) The AM\_parameters are only applicable for AM operation. +- 7) The Stop parameter is applicable to AM and UM RLC entities only and indicates to the RLC entity to not transmit nor receive any RLC PDUs. +- 8) The Continue parameter is applicable to AM and UM RLC entities only and indicates to the RLC entity to continue transmission and reception of RLC PDUs. +- 9) The UM\_parameters are only applicable for UM operation. +- 10) The TM\_parameters are only applicable for TM operation. +- 11) The N parameter indicates that an RLC entity will not send a PDU with "Sequence Number" $\geq V(S)+N$ for UM/AM RLC entities where N is a non-negative integer. +- 12) The V(S) parameter indicates the value of the Send State Variable for the case of the AM/UM RLC entities. +- 13) The parameter Status is only applicable for AM operation. This parameter indicates whether a RLC SDU is successfully transmitted or discarded. +- 14) The parameter DiscardReq indicates whether the transmitting RLC entity needs to inform the upper layers of the discarded RLC SDU. If required, the transmitting RLC entity notifies upper layers when the RLC SDU is discarded.. + +## 4.3.4 RRC to MAC Primitives + +### 4.3.4.1 Primitives + +The primitives between MAC and RRC are shown in table 4.3.4.1. + +**Table 4.3.4.1: Primitives between RRC sub-layer and MAC** + +| Generic Name | Parameter | | | | +|----------------------|------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------|---------| +| | Request | Indication | Response | Confirm | +| CMAC-CONFIG | MS information elements,
RB information elements,
Ciphering elements, | | | | +| CMAC-SYS-INFO | System Information Elements | | | | +| PAGING | MS Identity, CN Domain Identity,
Paging Cause, Paging Record Type
Identifier | MS Identity, CN Domain
Identity, Paging Cause,
Paging Record Type
Identifier | NA | NA | +| HANDOVER | Handover Reference Value | Handover Reference Value | NA | NA | +| PHYSICAL-INFO | Timing Advance Value | Timing Advance Value | NA | NA | + +#### CMAC-CONFIG-Req + +- CMAC-CONFIG-Req is used to request for setup, release and configuration of a logical channel, G-RNTI allocation, mapping between radio bearer and logical channel, setup, release and configuration of transport channels and mapping between radio bearers and transport channels. + +#### CMAC-SYS-INFO-Req + +- CMAC-SYS-INFO-Req is used to pass information elements needed for the generation of system information messages within the MAC entity. + +#### PAGING-Req/Ind: + +- PAGING-Req is used by RRC to page a MS. +- PAGING-Ind is used by the MS to inform the RRC of the reception of a PACKET PAGING REQUEST message. + +#### HANDOVER-Req/Ind: + +- HANDOVER-Req is used by the mobile station's RRC to trigger the transmission of the HANDOVER ACCESS message to the network +- HANDOVER-Ind is used by the network to inform the RRC of the reception of a HANDOVER ACCESS message + +#### PHYSICAL-INFO-Req/Ind: + +- PHYSICAL-INFO-Req is used by the network's RRC to trigger the transmission of the PHYSICAL INFORMATION message to the mobile station +- PHYSICAL-INFO-Ind is used by the mobile station to inform the RRC of the reception of the PHYSICAL INFORMATION message + +### 4.3.4.2 Primitive Parameters + +The MAC configuration primitives use the following parameters. See 3GPP TS 44.118 for a detailed description of the MS, and RB information elements. + +- 1) MS information elements +G-RNTI +SRNC identity +Activation time + +- 2) RB information elements +RB multiplexing info (Logical channel identity, radio priority, mapping of reduced radio bearer id to radio bearer id, transport channel identity) +- 3) Ciphering elements +Ciphering key +Activation Time (TDMA Frame Number) HFN + +The system information primitives use the following parameter: + +- 1) System Information elements +See 3GPP TS 44.118 + +The paging primitives use the following parameters: + +- 1) The *MS Identity* parameter is the IMSI, TMSI, PTMSI, or G-RNTI. +- 2) The *CN Domain Identity* parameter indicates whether a CN-initiated page is from the packet domain or circuit domain. +- 3) The *Paging Cause* parameter indicates the reason for the page. +- 4) The *Paging Record Type Identifier* parameter indicates the type of MS identity used by the CN in a CN-initiated page, e.g. IMSI (GSM), IMSI (DS-41), TMSI/PTMSI (GSM). + +The handover primitives use the following parameter: + +- 1) The *Handover Reference Value* parameter indicates the handover reference value used for access identification in the HANDOVER ACCESS message + +The physical info primitives use the following parameter: + +- 1) The *Timing Advance Value* parameter indicates the timing advance value in the PHYSICAL INFORMATION message to be applied by the mobile station + +## 4.4 Services required from lower layers + +The RLC/MAC function uses the services provided by the physical link layer as defined in 3GPP TS 44.004. + +The following services are required of the physical layer: + +- **Access capabilities:** In configurations where FLO is not used, the physical layer offers logical channels and the transmission services associated to higher layers. Logical channels are multiplexed either in a fixed predefined manner (multiframe structure) or dynamically by the MAC layer on basic physical subchannels. In configurations where FLO is used, the physical layer offers transport channels and the transmission services associated to higher layers. Transport channels are multiplexed in a dynamic manner on dedicated basic physical subchannels. Basic physical subchannels are the units scheduled on the radio medium. Some are reserved by the network for common use (e.g. for use by a combination of CCCH and BCCH), others are assigned to dedicated connections with MSs (dedicated basic physical subchannels), or are assigned to a shared usage between MSs (shared basic physical subchannels). +- **Error detection:** The physical layer offers an error protected transmission service, it includes error detection functions and to a lower level, error correction functions. Erroneous received frames may be notified to upper layers and, depending on the need of the upper layer, offered to it. The probability of one or more errors in a physical block transferred by the physical layer is defined in 3GPP TS 45.005. Due to non-specified methods of quality detection, the probability of residual errors in transferred blocks may vary between implementations. +- **Measurement of the signal strength of neighbouring base stations.** Measurements are transferred to RRC. +- **Measurement of the signal quality of the basic physical subchannel used.** Measurements are transferred to the MAC layer for reporting to the base station. +- **Cell/PLMN selection in MAC-Idle state.** In MAC-Idle state the physical layer selects the best cell with its BCCH in close co-operation with layer 3, meeting requirements for PLMN selection specified in 3GPP TS 42.011. + +## 5 Introduction to the Medium Access Control (MAC) procedures + +### 5.1 General + +The Medium Access Control procedures include the functions related to the management of the shared transmission resources (e.g. the packet data physical channels and the radio link connections on packet data physical channels) and dedicated transmission resources (e.g. the multiplexing of logical channels onto DBPSCHs). + +The Medium Access Control procedures support the provision of Temporary Block Flows that allow the point-to-point transfer of signalling and user data within a cell between the network and a mobile station. + +Moreover, the Medium Access Control procedures include the procedures for reception of PBCH and PCCH, which permits autonomous cell reselection performed by the mobile station (see 3GPP TS 45.008). + +### 5.2 Multiplexing principles + +#### 5.2.1 Temporary Block Flow + +A TBF is a logical connection used by two MAC entities to support the unidirectional transfer of upper-layer PDUs on basic physical sub-channels. A mobile station shall support eight TBFs in each direction (uplink and downlink). The network shall not assign more than eight TBFs to a mobile station. The total amount of TBFs assigned to a mobile station in a given direction shall always be lower than or equal to eight. + +The TBF is allocated radio resources on one or more BPSCHs of the same type (i.e. either SBPSCH(s) or DBPSCH(s)) and may only be mapped on one logical channel type at a time. A TBF shall not be mapped on more than one DBPSCH/S. The TBF comprises a number of RLC/MAC blocks carrying one or more upper-layer PDUs. + +A TBF mapped on PDTCH(s) may operate in either GPRS TBF mode or EGPRS TBF mode. If this TBF is operating on SBPSCH(s), the network sets the TBF mode in the PACKET UPLINK ASSIGNMENT message, MULTIPLE TBF UPLINK ASSIGNMENT message, PACKET DOWNLINK ASSIGNMENT message, MULTIPLE TBF DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF TIMESLOT RECONFIGURE message. If this TBF is operating on DBPSCH(s), the network sets the TBF mode using RRC procedures (see 3GPP TS 44.118). The EGPRS TBF mode is only supported by EGPRS capable MSs. + +A TBF mapped on FACCH, SACCH or SDCCH operates implicitly in DCCH TBF mode. + +A TBF mapped on TCH operates implicitly in TCH TBF mode. + +A TBF mapped on UDCH(s) operates in UDCH TBF mode. UDCH TBF mode is applicable only when FLO is used. + +A TBF mapped on CDCH(s) operates in CDCH TBF mode. CDCH TBF mode is applicable only when FLO is used. + +A TBF associated with a URB may operate in either GPRS TBF mode, EGPRS TBF mode, DCCH TBF mode, TCH TBF mode or UDCH TBF mode. + +A TBF associated with a SRB may operate in either GPRS TBF mode (CS-1 coding only), DCCH TBF mode or CDCH TBF mode. It shall not operate in EGPRS TBF mode. + +#### 5.2.2 Temporary Flow Identity + +##### 5.2.2.1 Temporary Flow Identity for SBPSCH + +See 3GPP TS 44.060 sub-clause 5.2.2. + +Global\_TFI is used in an uplink or a downlink RLC/MAC control message to unambiguously identify the mobile station or one of its TBFs on SBPSCH. If present, the Global\_TFI addresses the mobile station using either an uplink TFI or a downlink TFI. The TFI used shall obey the rules below: + +- If the TFI is used to identify the mobile station, any TFI may be used provided: + +- The timeslot number (TN) of the SBPSCH on which the RLC/MAC control message is sent corresponds to a timeslot assigned to the TBF in the direction of the TBF. +- If the TFI is used to identify a TBF, the TFI of this TBF shall be used. Additionally if the RLC/MAC control message is sent in uplink, and the TBF is a downlink TBF: +- If the timeslot number (TN) of the SBPSCH on which the RLC/MAC control message is sent is different from the TN of each of the timeslots assigned to the TBF in the direction of the TBF, the TN of the TBF shall be included in the RLC/MAC control message to uniquely identify this TBF. + +### 5.2.2.2 Temporary Flow Identity for DBPSCH + +A TBF mapped on DBPSCH(s) may operate in either GPRS, EGPRS, DCCH, TCH, CDCH or UDCH TBF mode. A TBF mapped on DBPSCH/S shall operate in DCCH TBF mode. + +A TBF in either GPRS TBF mode, EGPRS TBF mode or UDCH TBF mode (NT-RLC) is implicitly assigned a TFI that equals the identity (RBid) of the radio bearer it carries. An RLC/MAC block associated with such TBF shall contain a TFI. The TBF to which a RLC data block belongs is identified by the TFI and the direction (uplink or downlink) in which this RLC data block is sent. The TBF to which a RLC/MAC control message belongs is identified by the TFI, the direction in which this RLC/MAC control message is sent and the message type. + +A TBF in TCH TBF mode is not assigned a TFI. This TBF is in its direction the only user of the TCH on which it is mapped, as described in sub-clause 9.2.2. + +A TBF in UDCH TBF mode running in T-RLC is not assigned a TFI. + +A TBF in DCCH TBF mode is implicitly assigned a Reduced Radio Bearer identity (RRBid) that provides a one-to-one mapping with the RBid of the radio bearer it carries. In case this radio bearer is a User-plane Radio Bearer (URB), the mapping between RRBid and RBid is given at radio bearer set-up of this URB by means of primitive exchange between RRC and MAC (CMAC-CONFIG). An RLC/MAC block associated with a DCCH TBF mode shall contain a RRBid. The TBF to which a RLC data block belongs is identified by the RRBid and the direction (uplink or downlink) in which this RLC data block is sent. The TBF to which a RLC/MAC control message belongs is identified by the RRBid, the direction in which this RLC/MAC control message is sent and the message type. + +A TBF in CDCH TBF mode is implicitly assigned a Reduced Radio Bearer identity (RRBid) that provides a one-to-one mapping with the RBid of the signalling radio bearer it carries. An RLC/MAC block associated with a CDCH TBF mode shall contain a RRBid. The TBF to which a RLC data block belongs is identified by the RRBid and the direction (uplink or downlink) in which this RLC data block is sent. The TBF to which a RLC/MAC control message belongs is identified by the TFI or RRBid, the direction in which this RLC/MAC control message is sent and the message type. + +### 5.2.3 Uplink State Flag + +See 3GPP TS 44.060 sub-clause 5.2.3. + +### 5.2.4 Medium Access modes + +#### 5.2.4.1 Medium Access modes for SBPSCH + +See 3GPP TS 44.060 sub-clause 5.2.4. + +#### 5.2.4.2 Medium Access modes for DBPSCH + +The dedicated allocation is applicable exclusively on a dedicated channel (i.e. mapped onto a DBPSCH). No other MAC mode may apply on DBPSCH. If the mobile station is assigned a DBPSCH (e.g. PACKET DBPSCH ASSIGNMENT), dedicated allocation shall be used in both uplink and downlink directions on this DBPSCH. + +### 5.2.5 Multiplexing of GPRS and EGPRS TBF mode capable mobile stations + +See 3GPP TS 44.060 sub-clause 5.2.4a. + +## 5.3 MAC States + +### 5.3.1 MAC-Idle state + +#### 5.3.1.1 General + +In MAC-Idle state no TBF exists and the mobile station monitors relevant paging subchannels on the PCCCH. The mobile station may use DRX for monitoring the PCCCH. + +#### 5.3.1.2 Establishment of a SBPSCH + +In MAC-Idle state, upper layers may require the transfer of an upper-layer PDU, which may trigger the establishment of a TBF on SBPSCH(s) and the transition to MAC-Shared state. + +#### 5.3.1.3 Establishment of a DBPSCH + +In MAC-Idle state upper layers may require the transfer of an upper-layer PDU, which may trigger the establishment of a TBF on DBPSCH(s) either through RRC procedures (see 3GPP TS 44.118) or RLC/MAC procedures, in which case the mobile station leaves MAC-Idle state and enters the MAC-Dedicated state immediately after assignment of the DBPSCH(s). A mobile station shall not be assigned more than one DBPSCH/S. + +### 5.3.2 MAC-Shared state + +#### 5.3.2.1 General + +In MAC-Shared state, the mobile station is allocated radio resources providing a TBF for a point-to-point connection on one or more SBPSCHs. The TBF is used for the unidirectional transfer of upper-layer PDUs between the network and the mobile station. In MAC-Shared state the following services are offered: + +- transfer of upper-layer PDUs in RLC acknowledged mode; +- transfer of upper-layer PDUs in RLC unacknowledged mode. + +#### 5.3.2.2 Release of all SBPSCHs + +In MAC-Shared state, when all TBFs have been released in the downlink and uplink direction, the mobile station returns to MAC-Idle state. + +#### 5.3.2.3 Establishment of a DBPSCH + +In MAC-Shared state upper layers may require the transfer of an upper-layer PDU, which may trigger the establishment of a TBF on a DBPSCH through RRC procedures (see 3GPP TS 44.118), in which case the mobile station leaves MAC-Shared state and enters the MAC-DTM state. + +#### 5.3.2.4 Radio bearer reconfiguration + +Upon reconfiguration of all Radio Bearers from SBPSCH(s) to DBPSCH(s), the mobile station shall leave the MAC-Shared state and enter the MAC-Dedicated state after release of all TBFs on SBPSCH(s) and set-up of the first DBPSCH. See 3GPP TS 44.118. + +### 5.3.3 MAC-DTM state + +#### 5.3.3.1 General + +In MAC-DTM state a mobile station has been allocated radio resources providing one or more DBPSCHs and one or more SBPSCHs. A mobile station shall not be allocated radio resources providing a DBPSCH/S with any other BPSCH(s). The allocation of radio resources is co-ordinated by the network, in agreement with the capabilities of the mobile station. + +The transfer of upper-layer PDUs in RLC acknowledged, RLC unacknowledged mode or RLC transparent mode is provided. + +### 5.3.3.2 Release of all SBPSCHs + +In MAC-DTM state, when all TBFs on SBPSCHs have been released, in downlink and uplink directions, the mobile station enters MAC-Dedicated state. + +### 5.3.3.3 Release of all DBPSCHs + +In MAC-DTM state, upon release of all DBPSCHs, the mobile station enters the MAC-Shared state. + +### 5.3.3.4 Release of all SBPSCHs and DBPSCHs + +In MAC-DTM state, upon release of all SBPSCHs and DBPSCHs, the mobile station enters the MAC-Idle state. + +## 5.3.4 MAC-Dedicated state + +### 5.3.4.1 General + +In MAC-Dedicated state a mobile station has been allocated radio resources providing one or more DBPSCHs. A mobile station shall not be allocated more than one DBPSCH/S. The allocation of radio resources is co-ordinated by the network, in agreement with the capabilities of the mobile station. + +The transfer of upper-layer PDUs in RLC acknowledged, RLC unacknowledged mode or RLC transparent mode is provided. + +### 5.3.4.2 Release of all DBPSCHs + +In MAC-Dedicated state, upon release of all DBPSCHs, the mobile station shall enter the MAC-Idle state. + +### 5.3.4.3 Radio bearer reconfiguration + +Upon reconfiguration of all Radio Bearers from DBPSCH(s) to SBPSCH(s), the mobile station shall leave the MAC-Dedicated state and enter the MAC-Shared state after release of all DBPSCH(s) and set-up of the first TBF on SBPSCH(s) (see 3GPP TS 44.118). + +## 5.3.5 MAC state machine + +Figure 5.3.5.1 represents the state machine of the MAC sublayer. + +![Figure 5.3.5.1: MAC state machine diagram showing four states: MAC-DTMs State, MAC-Dedicated State, MAC-Shared State, and MAC-Idle State. Transitions are triggered by events like 'Set-up of the first TBF on SBPSCH', 'Release of the last DBPSCH', and 'RB Reconfiguration'.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +stateDiagram-v2 + [*] --> MAC-DTMs State + MAC-DTMs State --> MAC-Dedicated State : Set-up of the first TBF on SBPSCH + MAC-Dedicated State --> MAC-DTMs State : Release of the last TBF on SBPSCH + MAC-Dedicated State --> MAC-Shared State : Set-up of the first DBPSCH + MAC-Shared State --> MAC-Dedicated State : Release of the last DBPSCH + MAC-Shared State --> MAC-DTMs State : Release of the last DBPSCH + MAC-Shared State --> MAC-Idle State : Set-up of the first TBF on SBPSCH + MAC-Idle State --> MAC-Dedicated State : Set-up of the first DBPSCH + MAC-Idle State --> MAC-Shared State : Release of the last TBF on SBPSCH + MAC-Idle State --> MAC-DTMs State : Release of all BPSCHs + MAC-DTMs State --> MAC-DTMs State : Additional set-up/release of DBPSCH or TBF on SBPSCH + MAC-Dedicated State --> MAC-Dedicated State : Additional set-up/release of DBPSCH + MAC-Shared State --> MAC-Shared State : Additional set-up/release of TBF on SBPSCH + MAC-Dedicated State --> MAC-Shared State : RB Reconfiguration + MAC-Shared State --> MAC-Dedicated State : RB Reconfiguration + +``` + +Figure 5.3.5.1: MAC state machine diagram showing four states: MAC-DTMs State, MAC-Dedicated State, MAC-Shared State, and MAC-Idle State. Transitions are triggered by events like 'Set-up of the first TBF on SBPSCH', 'Release of the last DBPSCH', and 'RB Reconfiguration'. + +Figure 5.3.5.1: MAC state machine + +## 5.4 General MAC procedures in MAC-Idle state and MAC-Shared state + +### 5.4.1 Mobile station side + +#### 5.4.1.1 General + +A mobile station in MAC-Idle state or MAC-Shared state shall monitor the system information broadcast in the cell. + +In MAC-Idle state, the mobile station shall monitor the radio blocks on PCCCH as defined in sub-clauses 5.4.1.8 and 5.4.1.9. The determination of the paging group for the mobile station is defined in 3GPP TS 45.002. + +#### 5.4.1.2 Cell reselection + +Cell reselection in MAC-Idle state and MAC-Shared state is specified in 3GPP TS 45.008. The MAC entity on the mobile station side indicates to the RRC layer the availability of a cell and a cell change when decided by the MAC sublayer. RRC is advised of system information broadcast in the cell when a new cell has been selected or when a relevant part of this information changes. + +If the new cell supports *Iu mode* the mobile station shall operate in *Iu mode* unless ordered to operate in *A/Gb mode* by the network. If the new cell does not support *Iu mode*, a mobile station which supports *A/Gb mode* shall operate in *A/Gb mode* as described in 3GPP TS 44.060. If operating in *Iu mode*, the mobile station shall perform packet access in *Iu mode* otherwise the mobile station shall perform packet access in *A/Gb mode*. + +When a cell reselection is determined by the mobile station or ordered by the network, the mobile station may continue its operation in MAC-Idle state or MAC-Shared state in the old serving cell, while acquiring certain system information for the target cell. + +If the old cell does not support CCN, the operation in the old cell shall be aborted when one of the following conditions are met: + +- the mobile station starts to receive information on PBCCH in the target cell; +- the mobile station has received the SI13 message (see 3GPP TS 44.018) and there is no PBCCH present in the target cell; or +- the criteria for camping on the old cell are no longer fulfilled (see 3GPP TS 45.008). + +If PBCCH is present in the target cell, the mobile station shall delay the start of receiving information on PBCCH until the first occurrence of PSI1 in block B0. If the reception of PSI1 or PSI2 messages fails (see sub-clause 5.4.1.5) the mobile station may re-establish and continue its operation in the old cell, until the next occurrence of PSI1 in block B0. + +While the operation is maintained in the old cell, the mobile station may suspend its TBF(s) or suspend the monitoring of radio blocks on PCCCH, in order to receive necessary information on BCCH in the target cell. Such suspension may be required in MAC-Idle state and MAC-Shared state. It is performed without notification to the network. + +Suspension of the operation in the old cell for this purpose is allowed during the time required, for each message and according to the mobile station's multislot class, to receive the required messages on BCCH in the target cell. The allowable suspension of an uplink TBF may be extended with one block period, in case of dynamic or extended dynamic allocation, if the mobile station is unable to receive the corresponding USF due to the suspension of downlink operation. + +When the conditions are fulfilled to switch to the new cell, the mobile station shall abort any TBF in progress by immediately ceasing to decode the downlink, ceasing to transmit on the uplink, stopping all RLC/MAC timers except for timers related to measurement reporting. The mobile station shall then switch to the identified specified new cell and shall obey the relevant RLC/MAC procedures on this new cell. + +If the old cell supports CCN, a mobile station shall, when the cell reselection has been determined, follow the procedures for Network Assisted Cell Change as specified in 3GPP TS 44.060 sub-clauses 5.5.1.1a.2 and 8.8.2. + +Under no circumstances and independent of whether CCN mode is supported, operations in the old cell shall be continued more than 5 seconds after a cell reselection has been determined. + +### 5.4.1.3 Network Assisted Cell Change + +See 3GPP TS 44.060 sub-clause 5.5.1.1a. + +### 5.4.1.4 Release of DBPSCHs + +#### 5.4.1.4.1 General + +The mobile station shall acquire system information broadcast in the serving cell when in MAC-Idle state, after the release of all DBPSCHs if the mobile station had been unable to monitor the system information broadcast on PBCCH while one or more DBPSCHs were allocated: + +- The acquisition of system information shall be performed according to the requirements in sub-clause 5.4.1.5. +- The mobile station shall not attempt a packet access or accept a packet downlink assignment before these requirements are fulfilled. + +The following exceptions, stated in sub-clauses 5.4.1.4.2 and 5.4.1.4.3, may apply. + +#### 5.4.1.4.2 Continuation of PBCCH information + +At the allocation of a DBPSCH, the mobile station may keep the PSI messages received on PBCCH before the allocation of the DBPSCH. If all DBPSCHs are released in the same serving cell within 30 s after the PSI1 message was last received, the mobile station may resume the supervision of PBCCH\_CHANGE\_MARK and update of PBCCH information, defined in 3GPP TS 44.060 sub-clause 5.5.1.2.1, and need not initiate a *complete acquisition* of PBCCH information, as specified in sub-clause 5.4.1.5. + +#### 5.4.1.4.3 Receipt of PSI14 message in MAC-DTM state + +In MAC-DTM state, the mobile station may receive the PSI14 message on PACCH in the serving cell. If all DBPSCHs are released in the same serving cell within 30 s after the PSI14 message was last received, the mobile station may use the PSI14 message as a substitute for the SI13 or SI13-Alt message after the release of all DBPSCHs, until either the SI13 or SI13-Alt message has been received or the mobile station starts to receive information on PBCCH. + +The presence of a PBCCH in the cell is indicated by a PBCCH description in the PSII4 message. If the message does not contain the PBCCH description, the mobile station shall assume that PBCCH is not present in the cell. + +After the release of all of DBPSCHs, the mobile station shall perform a *complete acquisition* of PBCCH information, as defined in sub-clause 5.4.1.5. + +#### 5.4.1.5 System information on PBCCH + +See 3GPP TS 44.060 sub-clause 5.5.1.2. + +#### 5.4.1.6 System information on BCCH + +##### 5.4.1.6.1 General + +The support of *Iu mode* shall be indicated in SI3 message sent on BCCH. In addition, the support of *Iu mode* shall be indicated in either SI4 or SI7 and 8 messages. The SI3, SI4, SI7 and SI8 messages contain the CBQ3 parameter that indicates if *Iu mode* is supported in the cell (see 3GPP TS 44.018). + +If CBQ3 parameter sent on BCCH indicates that *Iu mode* is supported in the cell then a mobile station shall acquire a PBCCH description from either SI13 or SI13-Alt and shall operate in *Iu mode* (see 3GPP TS 44.118). + +If CBQ3 indicates that *Iu mode* is not supported in the cell then a mobile station may operate in *A/Gb mode* as described in 3GPP TS 44.060. + +When a new cell has been selected where PBCCH is not present, the mobile station shall operate as described in 3GPP TS 44.060. + +##### 5.4.1.6.2 Establishment of PBCCH + +The mobile station may receive an SI13, SI13-Alt or PSII3 message providing a PBCCH description indicating that PBCCH is present in the cell. The mobile station shall then perform a *complete acquisition* of PBCCH messages using the indicated PBCCH (see sub-clause 5.4.1.7). + +##### 5.4.1.6.3 (void) + +##### 5.4.1.7 (void) + +#### 5.4.1.8 Discontinuous reception (DRX) + +A mobile station in MAC-Idle state may use Discontinuous Reception (DRX) to reduce its power consumption. + +In DRX mode, the MAC layer receives the paging group relevant for the mobile station from the RRC layer via the CMAC-CONFIG primitive. The computation of the paging group is defined in 3GPP TS 44.118. The mobile station shall only monitor the blocks corresponding to its paging group. The GERAN shall initiate paging procedures for this mobile station on the blocks corresponding to its paging group. + +In non-DRX mode, the mobile station shall monitor all paging blocks on the monitored PCCCH (see 3GPP TS 45.002). + +There are three cases when the mobile station enters a non-DRX mode period: + +- 1) When entering the MAC-Idle state, the mobile station shall enter the non-DRX mode period. + +The duration of the non-DRX mode period is determined by the value of the DRX\_TIMER\_MAX parameter broadcast in the cell. + +If the mobile station receives a new value of the DRX\_TIMER\_MAX parameter during the non-DRX mode period, the mobile station may wait to apply the new value until the next time the non-DRX mode period is entered. + +- 2) When the network operates in NC2 mode and the MS sends a NC measurement report, both the MS and the network shall enter the NC2 non-DRX mode period. The duration of this period is defined by the NC\_NON\_DRX\_PERIOD parameter. +- 3) When initiating the MM procedures for GPRS attach and routeing area update defined in 3GPP TS 24.008, the mobile station shall enter the MM non-DRX mode period. This period ends when either of the messages GPRS ATTACH ACCEPT, GPRS ATTACH REJECT, ROUTING AREA UPDATE ACCEPT or ROUTING AREA + +UPDATE REJECT is received by the mobile station. This period also ends after timeout when waiting for any of these messages. + +The non-DRX mode periods defined above run independent of each other and may overlap. In RRC-Idle mode, the mobile station shall be in non-DRX mode during any of the non-DRX mode periods. + +#### 5.4.1.9 Page mode procedures on PCCCH + +See 3GPP TS 44.060 sub-clause 5.5.1.6. + +#### 5.4.1.10 Frequency Parameters + +See 3GPP TS 44.060 sub-clause 5.5.1.7. + +#### 5.4.1.11 G-RNTI Management + +G-RNTI is used to identify a mobile station during contention resolution and is allocated by RRC in the GERAN. If a mobile station does not possess a GERAN allocated G-RNTI when making a contention access it shall use a Random G-RNTI. Upon receiving a G-RNTI allocation from the GERAN a mobile station shall use it for subsequent contention accesses for as long as it remains valid. + +### 5.4.2 Network side + +#### 5.4.2.1 System Information broadcasting + +##### 5.4.2.1.1 System information on PBCCH + +If PBCCH is present in the cell, the network regularly broadcasts PACKET SYSTEM INFORMATION TYPE (PSI) 1, 2, 3, 3bis and PSI16 messages, and optionally PSI3ter, PSI3quater and some types of PSI messages on the PBCCH. The PSI 2, PSI 3bis, PSI3 ter, PSI3quater messages and some further types of PSI messages may be broadcast in multiple number of instances. Based on the information broadcast in PSI messages, a mobile station is able to decide whether and how it may gain access to the system via the current cell. + +NOTE: The network should take into account the limitations of earlier version of mobile equipments to understand the 3-digit MNC format of the location area identification, see 3GPP TS 44.060 sub-clause 12.23 and 3GPP TS 44.018, table "Location Area Identification information element". + +Instances of the PSI 5 message are broadcast on PBCCH if the mobile stations camping on the cell shall perform measurement reporting (see 3GPP TS 45.008). + +Instances of the PSI6 and PSI7 message may be broadcast on the PBCCH if non-GSM broadcast information is transmitted. + +The PSI8 message may be broadcast on the PBCCH if additional information (i.e. CBCH configuration and dynamic ARFCN mapping) shall be provided to the mobile station camping on the cell. + +The PSI16 message shall be broadcast on the PBCCH to provide mobile stations with additional information required for *Iu mode* operation. + +The PSI1 message contains the PBCCH\_CHANGE\_MARK and PSI\_CHANGE\_FIELD parameters. The value of the PBCCH\_CHANGE\_MARK may be incremented by one, modulo 8, each time the network makes a change in the PBCCH information. Such change includes any addition, removal or replacement of PSI messages, contents of PSI messages, or change in the scheduling of PSI messages on PBCCH. A change in the contents of the PSI1 message alone shall not be reflected in the PBCCH\_CHANGE\_MARK. When the PBCCH\_CHANGE\_MARK is incremented, the PSI\_CHANGE\_FIELD parameter shall be set to an appropriate value to indicate the nature of the latest change in the PBCCH information. + +The network may increment the PBCCH\_CHANGE\_MARK value by more than one, modulo 8, in order to enforce a complete acquisition of PBCCH information of all mobile stations. + +In order to avoid extensive TBF suspensions following an increment of the PBCCH\_CHANGE\_MARK parameter, the network may send PSI messages on PACCH to mobile stations in MAC-Shared state. + +The network indicates the support of the PACKET PSI STATUS and EGPRS PACKET CHANNEL REQUEST messages in the PSI1 message. + +#### 5.4.2.1.2 System information on BCCH + +In addition to the requirements in 3GPP TS 44.018, a SYSTEM INFORMATION TYPE 13 (SI13) message or a SYSTEM INFORMATION TYPE 13 Alt (SI13-Alt) message is regularly broadcast by the network on the BCCH to support *Iu mode*. Note that either the SI13 message or the SI13-Alt message is required on BCCH to support *Iu mode*. + +#### 5.4.2.1.3 System information on PACCH (and other logical channels) + +See 3GPP TS 44.060 sub-clause 5.5.2.1.3. + +#### 5.4.2.1.4 Consistent sets of system information messages + +Certain types of PSI messages are sent on PBCCH in a multiple number of instances. If such a PSI message type is sent on (P)BCCH, a mobile station shall receive a consistent set of that type of PSI message. In some cases, more than one type of PSI messages may be joined into one consistent set, see table 5.4.2.1.4.1. + +**Table 5.4.2.1.4.1: Consistent sets of system information messages** + +| Consistent set / Message Type(s) | Broadcast Channel | Number of instances | PSI change mark parameter | PSI index parameter | PSI count parameter | +|----------------------------------|-------------------|---------------------|---------------------------|---------------------|---------------------| +| PSI2 | PBCCH | 1 – 8 | PSI2 CHANGE MARK | PSI2 INDEX | PSI2 COUNT | +| PSI3 | PBCCH | 1 | PSI3 CHANGE MARK | | | +| PSI3 bis | PBCCH | 1 – 16 | PSI3 CHANGE MARK | PSI3bis INDEX | PSI3bis COUNT | +| PSI3 ter | PBCCH | 0 – 16 | PSI3 CHANGE MARK | PSI3ter INDEX | PSI3ter COUNT | +| PSI3 quater | PBCCH | 0 – 16 | PSI3 CHANGE MARK | PSI3quater INDEX | PSI3quater COUNT | +| PSI5 | PBCCH | 0 – 8 | PSI5 CHANGE MARK | PSI5 INDEX | PSI5 COUNT | +| PSI6 | PBCCH | 0 – 8 | PSI6 CHANGE MARK | PSI6 INDEX | PSI6 COUNT | +| PSI7 | PBCCH | 0 – 8 | PSI7 CHANGE MARK | PSI7 INDEX | PSI7 COUNT | +| PSI8 | PBCCH | 0 – 8 | PSI8 CHANGE MARK | PSI8 INDEX | PSI8 COUNT | +| PSI16 | PBCCH | 0 – 8 | PSI16 CHANGE MARK | PSI16 INDEX | PSI16 COUNT | + +A consistent set of system information messages is identified by a PSI *change mark* parameter included in each message in the set. All messages within a consistent set shall have the same value of this parameter. + +The total number of system information messages of a certain type within a consistent set is indicated by a PSI *count* parameter included in each message in the set. The position of a certain message instance within the consistent set of system information messages is indicated by a PSI *index* parameter. + +The PSI *count* parameter shall have the value N–1, where N is the number of instances of the particular message type present in the consistent set. The PSI *index* parameter shall have a range from zero to N–1. Different instances of a particular message type in a consistent set shall have different values of the PSI *index* parameter. + +#### 5.4.2.2 Paging + +See 3GPP TS 44.060 sub-clause 5.5.2.2. + +#### 5.4.2.3 Network Assisted Cell Change + +See 3GPP TS 44.060 sub-clause 5.5.2.3. + +### 5.5 Measurement reports + +#### 5.5.1 General + +See 3GPP TS 44.060 sub-clause 5.6.0. + +#### 5.5.2 Network Control (NC) measurement reporting + +The behaviour of the mobile station is controlled by the parameter NETWORK\_CONTROL\_ORDER broadcast in the PSI5 message on PBCCH, in the SI13, SI13-Alt and SI2quater messages on the BCCH and in the PSI13 message on PACCH. Alternatively, the network may send the NETWORK\_CONTROL\_ORDER parameters in a PACKET MEASUREMENT ORDER or in a PACKET CELL CHANGE ORDER message on PCCCH or PACCH to a particular + +mobile station. The parameter NETWORK\_CONTROL\_ORDER may have one of the values NC0, NC1, NC2 or RESET (see 3GPP TS 45.008). + +When in mode NC1 or NC2, the mobile station shall perform the NC measurements as defined in 3GPP TS 45.008. The reporting periods are indicated in the NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T field of the PSI5, the SI2quater, the PACKET CELL CHANGE ORDER or the PACKET MEASUREMENT ORDER message. If NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I or NC\_REPORTING\_PERIOD\_T have not been received by the mobile station the default values shall be used. The mobile station shall apply to the timer T3158 either the NC\_REPORTING\_PERIOD\_I when in MAC-Idle state or the NC\_REPORTING\_PERIOD\_T when in MAC-Shared state. The measurement results shall be sent to the network using the procedures specified in sub-clause 7.4 for MAC Idle state, and in sub-clause 8.4 for MAC-Shared state. + +On expiry of timer T3158, the mobile station shall restart timer T3158 with the indicated reporting period, perform the measurements and send either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT to the network. The condition for sending the PACKET ENHANCED MEASUREMENT REPORT message instead of the PACKET MEASUREMENT REPORT message is based on the REPORT\_TYPE parameter and if the MS has received BSIC information for all cells. For the detailed conditions see 3GPP TS 44.060 sub-clause 11.2.23, sub-clause 11.2.4 and sub-clause 11.2.9b and also 3GPP TS 44.018 sub-clause 10.5.2.33b. + +A mobile station in mode NC1 or NC2 may receive a new indicated reporting period while timer T3158 is active. If the new indicated reporting period is less than the time to expiry of timer T3158, the mobile station shall immediately restart timer T3158 with the new indicated reporting period. Otherwise, the timer T3158 shall continue to run. + +When changing from MAC-Shared state to MAC-Idle state, a mobile station in mode NC1 or NC2 shall restart the timer T3158 with the reporting period determined by the NC\_REPORTING\_PERIOD\_I parameter if at least one PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message was sent in MAC-Shared state. Otherwise the timer T3158 shall continue to run. + +When changing from MAC-Idle state to MAC-Shared state, a mobile station in mode NC1 or NC2 shall restart the timer T3158 with the reporting period determined by the NC\_REPORTING\_PERIOD\_T parameter if the reporting period is less than the time to expiry of timer T3158. Otherwise the timer T3158 shall continue to run. + +When a mobile station in *Iu mode* leaves RRC-Cell Shared state and enters RRC-GRA\_PCH state or RRC-Idle mode, the timer T3158 shall be stopped and no more measurement reports shall be sent to the network. + +A mobile station may reselect a new cell or may be ordered to reselect a new cell with mode NC1 or NC2 while timer T3158 is active. If time to expiry of timer T3158 is greater than the indicated reporting period for the new cell, the mobile station shall immediately restart timer T3158 with the indicated reporting period for the new cell. Otherwise, the timer T3158 shall continue to run. + +At cell reselection the NC measurement parameters valid for the mobile station in the new cell (NETWORK\_CONTROL\_ORDER, NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T) are either: + +- brought from the old cell (if received in a PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER message); or +- received in a broadcast PSI5, SI13, SI13-Alt, PSI13 or SI2quater message in the new cell. If no parameters have been brought from the old cell, and until individual measurement parameters are received in the new cell, the mobile station shall use the broadcast measurement parameters from PSI5 or use the default parameter values. + +The default frequency list to be applied in the new cell shall be the BA(GPRS) list of that cell until a new PACKET MEASUREMENT ORDER message is received. The BA(GPRS) list could also have been modified by frequency parameters received in a PACKET CELL CHANGE ORDER message in the old cell. + +For (NC) measurement reporting, the Mobile Station shall use PACKET ENHANCED MEASUREMENT REPORT messages instead of PACKET MEASUREMENT REPORT messages if that is indicated by the parameter REPORT\_TYPE and if at least one BSIC is allocated to each frequency in the BA(GPRS) list. + +For a multi-RAT mobile station, reports on 3G cells may also be included in the reporting. For report with the PACKET MEASUREMENT REPORT message, reporting is performed on two separate lists: the BA(GPRS) and the 3G Neighbour Cell List (for a multi-RAT MS). For report with the PACKET ENHANCED MEASUREMENT REPORT message, reporting is performed on the Neighbour Cell List (defined in 3GPP TS 44.060 sub-clause 5.6.3.3). + +A mobile station that has been allocated one or more DBPSCHs, shall not send Network Control measurement reports to the network during that period. The mobile station shall return to the previous reporting mode when all the DBPSCHs have been released. + +### 5.5.3 (void) + +### 5.5.4 Additional measurement and reporting parameters + +See 3GPP TS 44.060 sub-clause 5.6.4. + +## 5.6 Mapping of Signalling Radio Bearers (SRB) onto logical channels / transport channels + +### 5.6.1 Downlink + +In downlink direction, the mapping of SRBs onto logical channels or, in case of FLO, transport channels is left up to network implementation. The rules defined in sub-clause 5.6.2 should be used. The MS shall be able to receive SRB data on any of the following logical channels if available: SDCCH, SACCH, FACCH, PDTCH and SFACCH. Additionally, a MS supporting FLO shall be able to receive SRB data on CDCH. + +### 5.6.2 Uplink + +#### 5.6.2.1 MAC-Dedicated State + +Table 5.6.2.1.1 represents the alternatives for mapping a given SRB onto a given logical channel or, in case of FLO, transport channel when the MS is in MAC-Dedicated state. The MS shall obey the rules given in this table. Only the logical channels or transport channels available for SRBs are listed. + +In case more than one DBPSCHs are assigned, with a mixed allocation of TCH(s) and PDTCH(s) (e.g. TCH on one DBPSCH, and PDTCH on the other DBPSCH), any ongoing transfer of a given SRB shall continue in the same TBF mode. + +**Table 5.6.2.1.1: Mapping of SRBs onto logical channels or transport channels in MAC-Dedicated State** + +| | MAC-Dedicated State | | | | +|-------------|---------------------|---------------|---------------|--------------| +| | SDCCH + SACCH | FACCH + SACCH | PDTCH + SACCH | CDCH + SACCH | +| SRB1 | SACCH | SACCH | SACCH | SACCH | +| SRB2 | SDCCH | FACCH | PDTCH | CDCH | +| SRB3 | SDCCH | FACCH | PDTCH | CDCH | +| SRB4 | SDCCH | SACCH | PDTCH | SACCH | + +#### 5.6.2.2 MAC-Shared State + +Table 5.6.2.2.1 represents the alternatives for mapping a given SRB onto a given logical channel when the MS is in MAC-Shared state. The MS shall obey the rules given in this table. Only the logical channels available for SRBs are listed. + +**Table 5.6.2.2.1: Mapping of SRBs onto logical channels in MAC-Shared State** + +| | MAC-Shared State | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | PDTCH + SFACCH | +| SRB1 | PDTCH xor SFACCH ( i ) | +| SRB2 | PDTCH xor SFACCH ( i ) | +| SRB3 | PDTCH xor SFACCH ( i ) | +| SRB4 | PDTCH xor SFACCH ( i ) | +| Rule i : | PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for this SRB, otherwise SFACCH shall be used. | + +### 5.6.2.3 MAC-DTM State + +Table 5.6.2.3.1 represents the alternatives for mapping a given SRB onto a given logical channel or, in case of FLO, transport channel when the MS is in MAC-DTM state. The MS shall obey the rules given in this table. Only the logical channels or transport channel available for SRBs are listed. + +**Table 5.6.2.3.1: Mapping of SRBs onto logical channels or transport channels in MAC-DTM State** + +| | MAC-DTM State | +|-------------|--------------------------------------------------------------| +| | (FACCH/H + SACCH/H) + (PDTCH/H (see note) + SFACCH/H) | +| SRB1 | SACCH/H | +| SRB2 | PDTCH/H xor FACCH/H (ii) | +| SRB3 | PDTCH/H xor SFACCH/H (i) | +| SRB4 | PDTCH/H xor SFACCH/H (i) | + + + +| | MAC-DTM State | +|-------------|-----------------------------------------------------------| +| | (CDCH + SACCH/H) + (PDTCH/H (see note) + SFACCH/H) | +| SRB1 | SACCH/H | +| SRB2 | PDTCH/H xor CDCH (iv) | +| SRB3 | PDTCH/H xor SFACCH/H (i) | +| SRB4 | PDTCH/H xor SFACCH/H (i) | + + + +| | MAC-DTM State | +|-------------|---------------------------------------------------| +| | (FACCH/F + SACCH/F) + (PDTCH/F + SFACCH/F) | +| SRB1 | SACCH/F | +| SRB2 | FACCH/F xor PDTCH/F (ii) | +| SRB3 | PDTCH/F xor SFACCH/F (i) | +| SRB4 | PDTCH/F xor SFACCH/F (i) | + + + +| | MAC-DTM State | +|-------------|------------------------------------------------| +| | (CDCH + SACCH/F) + (PDTCH/F + SFACCH/F) | +| SRB1 | SACCH/F | +| SRB2 | CDCH xor PDTCH/F (iv) | +| SRB3 | PDTCH/F xor SFACCH/F (i) | +| SRB4 | PDTCH/F xor SFACCH/F (i) | + + + +| | MAC-DTM State | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | (PDTCH + SACCH) + (PDTCH + SFACCH) | +| SRB1 | SACCH | +| SRB2 | PDTCH (iii) | +| SRB3 | PDTCH xor SFACCH (i) | +| SRB4 | PDTCH xor SFACCH (i) | +| Rule i : | PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for this SRB, otherwise SFACCH shall be used. | +| Rule ii : | PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for SRB2, else FACCH shall be used. In case more than one DBPSCHs are assigned, with a mixed allocation of TCH(s) and PDTCH(s) (e.g. TCH on one DBPSCH, and PDTCH on the other DBPSCH), any ongoing SRB2 transfer shall continue in the same TBF mode. | +| Rule iii : | PDTCH on SBPSCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for SRB2, else PDTCH on DBPSCH shall be used. | +| Rule iv : | PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for SRB2, else CDCH shall be used. | +| NOTE: | Single-slot operation with exclusive allocation. | + +## 5.7 Multiplexing principles with Flexible Layer One + +### 5.7.1 General + +The Flexible Layer One may only be used on DBPSCH in MAC-Dedicated and MAC-DTM states. The allowed channel combinations are defined in 3GPP TS 45.002. + +Multiplexing of TBFs in UDCH TBF mode or CDCH TBF mode with TBFs in GPRS TBF mode, EGPRS TBF mode, TCH TBF mode or DCCH TBF mode on the same DBPSCH is not allowed with the exceptions of TBFs on SACCH and half-rate configurations. + +A mobile station may have up to four simultaneous active transport channels in the same TTI on a DBPSCH (see 3GPP TS 45.002) + +### 5.7.2 Multiplexing between user-plane and control-plane + +The figure below illustrates the multiplexing between user-plane and control-plane onto transport channels. + +A TBF may send data onto one transport channel at a time per TTI per DBPSCH, following the rules below: + +- RLC/MAC blocks for data transfer associated with an SRB shall be sent on CDCH. +- RLC/MAC blocks for data transfer associated with a URB shall be sent on UDCH. +- RLC/MAC blocks for control message transfer shall be sent on ADCH. + +There may be up to four simultaneous UDCHs active during the same TTI on a DBPSCH, allowing for transfer of data from four different TBFs during the same TTI. + +On a DBPSCH, when either CDCH or ADCH is active during a TTI, no other transport channel may be active at the same time. + +NOTE: User-plane and control-plane data are effectively multiplexed on the same DBPSCH on a TTI-basis. + +![Diagram illustrating control-plane and user-plane multiplexing on transport channels. The diagram shows data flow from Control-plane data and User-plane data through RLC layers, then through Transport Channel Functions (TBFs) into the MAC layer. In the MAC layer, Control-plane data is multiplexed onto CDCH or ADCH, while User-plane data is multiplexed onto UDCH. All transport channels (CDCH, ADCH, UDCH) are then multiplexed into the DCH, which is finally processed by the FLO (Flexible Layer One).](6e612452d995bb03cc3f3d004493f7bf_img.jpg) + +The diagram illustrates the multiplexing process at the MAC layer. At the top, 'Control-plane data' and 'User-plane data' are shown entering RLC blocks. Below the RLC blocks, the data is processed by Transport Channel Functions (TBFs). The MAC layer contains three transport channels: CDCH (for control-plane data), ADCH (for control-plane data), and UDCH (for user-plane data). The CDCH and ADCH channels are multiplexed together, and the UDCH channel is also multiplexed. The output of the MAC layer is the DCH (Dedicated Channel), which is then processed by the FLO (Flexible Layer One). + +Diagram illustrating control-plane and user-plane multiplexing on transport channels. The diagram shows data flow from Control-plane data and User-plane data through RLC layers, then through Transport Channel Functions (TBFs) into the MAC layer. In the MAC layer, Control-plane data is multiplexed onto CDCH or ADCH, while User-plane data is multiplexed onto UDCH. All transport channels (CDCH, ADCH, UDCH) are then multiplexed into the DCH, which is finally processed by the FLO (Flexible Layer One). + +Figure 5.7.2.1: Control-plane and user-plane multiplexing on transport channels + +## 6 Paging procedures + +### 6.1 General + +The Packet Paging procedure is always initiated upon request by RRC. RRC shall provide all the necessary information to construct a PACKET PAGING REQUEST message. The MAC layer shall include in the PACKET PAGING REQUEST message all information received from the RRC layer. A number of mobile stations can be paged in the same paging message. + +On receipt of a PACKET PAGING REQUEST message, the MAC shall forward all received information for this mobile station to RRC. + +### 6.2 Paging initiation in MAC-Idle state + +In MAC-Idle state and upon request from RRC, the MAC layer initiates the Packet Paging procedure by transmitting a PACKET PAGING REQUEST message on an appropriate paging subchannel on the PCCCH, taking into account the DRX parameters valid for each targeted mobile station (see sub-clause 5.4.1.8). + +The following IEs shall be included in the in the PACKET PAGING REQUEST message. RRC determines the values of the IEs (see 3GPP TS 44.118). + +- MS Identity (IMSI, TMSI, P-TMSI or G-RNTI). + +The following IEs may be included in the in the PACKET PAGING REQUEST message. RRC determines which IEs to include and their values (see 3GPP TS 44.118). + +- CN domain identity. +- Paging cause. +- Paging Record Type Identifier. + +### 6.3 Paging initiation in MAC-Shared state + +In MAC-Shared state and upon request from RRC, the MAC layer initiates the paging procedure by transmitting a PACKET PAGING REQUEST message on the PACCH. + +The following IEs shall be included in the in the PACKET PAGING REQUEST message. RRC determines the values of the IEs (see 3GPP TS 44.118). + +- MS Identity (IMSI, TMSI, P-TMSI or G-RNTI). + +The following IEs may be included in the in the PACKET PAGING REQUEST message. RRC determines which IEs to include and their values (see 3GPP TS 44.118). + +- CN domain identity. +- Paging cause. +- Paging Record Type Identifier. + +### 6.4 Reception of PACKET PAGING REQUEST by an MS + +Upon reception of a PACKET PAGING REQUEST message on either PCCCH or PACCH, the MAC shall forward all received information for this mobile station to RRC. + +## 7 Medium Access Control (MAC) procedures on PCCCH + +### 7.1 General + +The establishment of a Temporary Block Flow (TBF) can be initiated by either the mobile station or the network. + +The request for establishment of a TBF using the PCCCH is described in this sub-clause. For mobile stations in MAC-Idle state measurement reports messages are sent on temporary fixed allocations without the establishment of an uplink TBF (see sub-clause 7.4). + +### 7.2 TBF establishment initiated by the mobile station on PCCCH + +#### 7.2.1 General + +The purpose of the packet access procedure is to establish a TBF to support the transfer of upper-layer PDUs in the direction from the mobile station to the network. Packet access shall be done on PCCCH, as defined in this sub-clause. The packet access can be done in either one phase (sub-clause 7.2.3) or in two phases (sub-clauses 7.2.3 and 7.2.4). + +TBF establishment can also be done on PACCH if a TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station is already established (see sub-clause 8.2.2.1.3). TBF establishment can also be done on PACCH if the mobile station is releasing its last TBF for transfer of upper-layer PDUs in the direction from the mobile station to the network and TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station is not established (see sub-clause 10.4.5.5 and sub-clause 10.4.6.4). + +If the mobile station is in MAC-Dedicated state the establishment of a TBF shall be performed by the procedures specified in 3GPP TS 44.118. + +The packet access procedure is initiated by the mobile station. Initiation is triggered by a request from upper layers to transfer an upper-layer PDU using the primitives that are defined in sub-clause 4.3. + +Upon such a request: + +- if access to the network is allowed (sub-clause 7.2.2), the mobile station shall initiate the packet access procedure as defined in sub-clause 7.2.3.1.1; +- otherwise, the MAC sublayer in the mobile station shall reject the request. + +#### 7.2.2 Permission to access the network + +See 3GPP TS 44.060 sub-clause 7.1.1. + +#### 7.2.3 Initiation of a TBF establishment + +##### 7.2.3.1 Initiation of the packet access procedure + +###### 7.2.3.1.1 General + +The mobile station shall initiate the packet access procedure by scheduling the sending of (EGPRS) PACKET CHANNEL REQUEST messages on the PRACH corresponding to its PCCCH\_GROUP. The mobile station shall use the last access parameters received on PBCCH. At sending of the first (EGPRS) PACKET CHANNEL REQUEST message, the mobile station shall store the value for the Retry (R) bit to be transmitted in all the subsequent MAC headers for this TBF as 'MS sent channel request message once'. If a second (EGPRS) PACKET CHANNEL REQUEST message is sent, the mobile station shall change the value for the Retry (R) bit to 'MS sent channel request message once or more'. + +While waiting for a response to the (EGPRS) PACKET CHANNEL REQUEST message, the mobile station shall monitor the full PCCCH corresponding to its PCCCH\_GROUP. The mobile station shall perform signal strength measurements as they are defined for MAC-Idle state (see 3GPP TS 45.008). + +While monitoring the full PCCH, the mobile station shall decode any occurrence of the PERSISTENCE\_LEVEL parameter included in a message received on PCCH. When the mobile station receives the PERSISTENCE\_LEVEL parameter, the value of the PERSISTENCE\_LEVEL parameter shall be taken into account at the next (EGPRS) PACKET CHANNEL REQUEST attempt that follows. + +The (EGPRS) PACKET CHANNEL REQUEST messages are sent on PRACH and contain an indication of the type of access and parameters required to indicate the mobile station's demand of radio resource. + +There are two formats of the PACKET CHANNEL REQUEST message containing either 8 bits or 11 bits of information. The format to be applied on PRACH is controlled by the parameter ACC\_BURST\_TYPE which is broadcast on PBCCH. The cause value to be used in the PACKET CHANNEL REQUEST message for a non-EGPRS TBF mode capable MS depends on the purpose of the packet access procedure as follows: + +- If the mobile station intends to use the TBF to send user data it shall determine the RLC mode from the configuration of the radio bearer for which the TBF is to be established. If the requested RLC mode is acknowledged mode, the mobile station shall request either one phase access or two phase access. If the requested RLC mode is unacknowledged mode, the mobile station shall indicate in the PACKET CHANNEL REQUEST message either One phase Access Request in RLC unacknowledged mode or two phase access. +- If the purpose of the packet access procedure is to send a message on SRB1; in this case, the mobile station shall indicate either 'Single Block Without TBF Establishment' or 'One phase Access Request in RLC unacknowledged mode' in the PACKET CHANNEL REQUEST message. +- If the purpose of the packet access procedure is to send a message on SRB2-4 and a dedicated channel is not needed; in this case the mobile station shall indicate 'MM Procedure' in the PACKET CHANNEL REQUEST message. +- If the purpose of the packet access procedure is to send a message on SRB2-4 and a dedicated channel is needed; in this case, the mobile station shall indicate 'Dedicated channel request' in the PACKET CHANNEL REQUEST message +- If the purpose of the packet access procedure is to initiate an Emergency Call; in this case, the mobile station shall indicate 'Emergency Call' in the PACKET CHANNEL REQUEST message. +- If the purpose of the packet access procedure is to request multiple TBFs, the mobile station shall request a two phase access. + +EGPRS TBF mode capable MSs shall monitor the GPRS Cell Options IE on the PBCCH(PSI1/PSI13) for the cell's EGPRS capability. In the GPRS Cell Options IE it is also indicated if the EGPRS PACKET CHANNEL REQUEST is supported in the cell. + +- If the cell is EGPRS TBF mode capable and EGPRS PACKET CHANNEL REQUEST is supported in the cell the EGPRS PACKET CHANNEL REQUEST messages shall be used at one-phase access attempts (in RLC acknowledged or unacknowledged mode), two-phase access attempts, sending of a message on SRB2-4 if a dedicated channel is needed or initiation of an emergency call. The corresponding cause value shall be used. +- If the cell is EGPRS TBF mode capable and EGPRS PACKET CHANNEL REQUEST messages are not supported in the cell or if the cell is not EGPRS TBF mode capable, the EGPRS TBF mode capable mobile station shall use the PACKET CHANNEL REQUEST message as for non-EGPRS TBF mode capable MSs (see above). + +#### 7.2.3.1.2 Access persistence control on PRACH + +See 3GPP TS 44.060 sub-clause 7.1.2.1.1. + +#### 7.2.3.2 Packet assignment procedure + +##### 7.2.3.2.1 On receipt of a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message + +###### 7.2.3.2.1.1 General + +On receipt of a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message, the network may assign to the mobile station a radio resource on either one or more SBPSCHs or on one or more DBPSCHs, based + +on the cause field in the received message. The network shall not assign more than one DBPSCH/S to the mobile station. + +#### 7.2.3.2.1.2 Allocation of resource on SBPSCH(s) + +See 3GPP TS 44.060 sub-clause 7.1.2.2.1 + +#### 7.2.3.2.1.3 Allocation of resource on DBPSCH(s) + +When the mobile station has been allocated a resource on one or more DBPSCHs, the allocated dedicated resource is assigned to the mobile station in a PACKET DBPSCH ASSIGNMENT message, sent on any PAGCH block on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. The *Packet Request Reference* information element shall be used to address the mobile station and frequency parameters shall be included. + +The mobile station may use information received on PBCCH or a previous assignment message to decode the frequency parameters contained in the assignment message. If the mobile station detects an invalid *Frequency Parameters* information element in the assignment message, it shall abort the procedure, if required initiate a partial acquisition of PBCCH information, and may then re-initiate this procedure. + +In case the allocated channel type is PDTCH+PACCH+SACCH (see 3GPP TS 44.060), the network shall include the USF value to be used on PDTCH and PACCH in the PACKET DBPSCH ASSIGNMENT message. + +On receipt of a PACKET DBPSCH ASSIGNMENT message corresponding to one of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages the mobile station shall stop timers T3186 and T3170 if running and stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages. The mobile station shall then switch to the assigned DBPSCH(s), enter the MAC-Dedicated state and proceed with contention resolution of the one phase packet access procedure according to sub-clause 7.2.3.3.2. + +When the mobile station switches to the assigned DBPSCH(s), it shall take into account the power control parameters received in downlink SACCH blocks, perform signal strength measurements and apply output power control procedures as they are defined for MAC-Dedicated state (see 3GPP TS 45.008). The mobile station shall not send any measurement reports until contention resolution is complete. It shall follow the procedures in sub-clauses 9 and 11. + +#### 7.2.3.2.1.4 Packet access queuing notification procedure + +See 3GPP TS 44.060 sub-clause 7.1.2.2.2. + +#### 7.2.3.2.1.5 Packet polling procedure + +See 3GPP TS 44.060 sub-clause 7.1.2.2.3. + +#### 7.2.3.2.1.6 Packet access reject procedure + +The network may, as response to a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message, send to the mobile station a PACKET ACCESS REJECT message on any PAGCH block on the same PCCCH on which the channel-request message was received. This message contains the request reference with time of reception of the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message and optionally a WAIT\_INDICATION field in the *Reject structure* of the PACKET ACCESS REJECT message. + +On receipt of a PACKET ACCESS REJECT message containing a *Reject structure* addressed to the mobile station, where the *Packet Request Reference* in the *Reject structure* corresponds to one of the mobile station's last 3 PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages: + +- The mobile station shall stop T3186, stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, start T3172 with the value indicated in the WAIT\_INDICATION field, start T3170 if it has not already been started, and listen to the downlink PCCCH until T3170 expires. During this time, the mobile station shall ignore additional PACKET ACCESS REJECT messages, but on reception of any PACKET UPLINK ASSIGNMENT or PACKET DBPSCH ASSIGNMENT message corresponding to any other of its last 3 PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, the mobile station shall stop T3170, stop T3172, and follow the procedure defined in sub-clause 7.2.3.2.1. +- If no PACKET UPLINK ASSIGNMENT or PACKET DBPSCH ASSIGNMENT message is received before expiration of T3170, the mobile station shall indicate a packet access failure to upper layer and return to *MAC-* + +*Idle state.* As an option, the mobile station may stop T3170, indicate a packet access failure to upper layer and return to *MAC-Idle state* as soon as it has received responses from the network on all, or in case more than 3 were sent, the last 3 of its PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages. + +- If an erroneous PACKET UPLINK ASSIGNMENT or PACKET DBPSCH ASSIGNMENT message (e.g., the mobile station has been assigned more PDCHs than it supports according to its multislot class) addressed to the mobile station is received before expiration of T3170, the mobile station shall stop T3170 and act as stated in sub-clause 7.2.5. +- If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall stop T3170 and respond to the message (see sub-clause 7.3.2). +- If the mobile station receives a PACKET DBPSCH ASSIGNMENT message, it shall stop T3170 and respond to the message (see sub-clause 7.3.3). +- The mobile station shall not make a new attempt for packet access in the same cell until T3172 expires, but may attempt packet access in another cell after successful cell reselection for radio-conditions reasons (see 3GPP TS 45.008). +- The value of the WAIT\_INDICATION field (i.e., T3172) relates to the cell from which it was received. + +### 7.2.3.3 Contention resolution at one phase access + +#### 7.2.3.3.1 Contention resolution at one phase access on SBPSCHs + +The G-RNTI is used to uniquely identify the mobile station when sending on uplink. The Radio bearer Id is used to identify the RLC instance to which the RLC/MAC block belongs. Every RLC data block that is sent on the TBF shall include the G-RNTI of the mobile station and the RB Id of the RLC instance being addressed, until the contention resolution is completed on the mobile station side. If MCS-7, MCS-8 or MCS-9 is used for the transmission of the G-RNTI and RB Id in EGPRS TBF mode (i.e. the RLC/MAC block is carrying two RLC data blocks), the G-RNTI and RB Id shall be inserted in both RLC data blocks. The G-RNTI and RB Id shall also be included in the PACKET RESOURCE REQUEST message, if sent during the contention resolution. If ciphering is used, the least significant bit of the uplink HFN of this radio bearer shall be inserted in each RLC data block sent on the TBF and if applicable in the PACKET RESOURCE REQUEST message until the contention resolution is completed on the mobile station side. If the least significant bit of the HFN in the network for the same radio bearer in the same direction is different from the one received from the mobile station, the network shall increase its HFN by one unit. + +The retransmission of an RLC data block shall include the G-RNTI and RB Id if the RLC data block was originally transmitted including these fields, also if the retransmission occurs after the completion of the contention resolution. + +At sending of the first RLC data block, the mobile station shall stop timer T3164, set counter N3104 to 1, and start timer T3166. The counter N3104 shall be stepped each time the mobile station sends an RLC data block. + +The network shall respond by including the G-RNTI in the PACKET UPLINK ACK/NACK message after the first correctly received RLC data block that comprises the G-RNTI and RB Id. In EGPRS TBF mode, the network may instead respond by addressing the mobile station with the TFI of the assigned TBF and including the G-RNTI (in the CONTENTION\_RESOLUTION\_TLLI field) in a PACKET UPLINK ASSIGNMENT message, if the resources allocated for the TBF need to be reallocated (see sub-clause 8.2.2.1.2). + +The contention resolution is completed on the network side when the network receives an RLC data block that comprises the G-RNTI value that identifies the mobile station, the RB Id that identifies the RLC instance being addressed and the TFI value associated with the TBF. + +The contention resolution is successfully completed on the mobile station side when the mobile station receives a PACKET UPLINK ACK/NACK message addressing the mobile station with the TFI value associated with the uplink TBF and including the same G-RNTI value that the mobile station has included in the RLC header of the first RLC data blocks, or alternatively, in EGPRS TBF mode, a PACKET UPLINK ASSIGNMENT message addressing the mobile station with the TFI value associated with the uplink TBF and including the same G-RNTI value that the mobile station included in the RLC header of the first RLC data blocks. The mobile shall then stop timer T3166 and counter N3104. + +The contention resolution has failed on the mobile station side when the counter N3104 reaches its maximum value, or timer T3166 expires. The contention resolution also fails, if the mobile station receives a PACKET UPLINK ACK/NACK message or in EGPRS TBF mode alternatively a PACKET UPLINK ASSIGNMENT message addressing + +the mobile station with the TFI associated with the uplink TBF and including a G-RNTI value other than that the mobile station included in the RLC header of the first RLC data blocks; in such a case, the mobile station shall not transmit a PACKET CONTROL ACKNOWLEDGEMENT in the uplink radio block specified if a valid RRBP field is received as part of the PACKET UPLINK ACK/NACK message or in EGPRS TBF mode alternatively as part of the PACKET UPLINK ASSIGNMENT message. + +In case of a contention resolution failure on the mobile station side, the mobile station shall reset the counter N3104 and stop timer T3166. The mobile station shall stop transmitting on the TBF and reinitiate the packet access procedure, unless the packet access procedure has already been attempted four times. In that case, a TBF failure has occurred, see sub-clause 7.2.5. + +### 7.2.3.3.2 Contention resolution at one phase access on DBPSCH + +#### 7.2.3.3.2.1 General + +During contention resolution the mobile station shall only send on the RB for which packet access was initiated via the PCCH. The RB may be mapped onto a PDTCH, SDCCH or FACCH logical channel. + +#### 7.2.3.3.2.2 Contention resolution at one phase access on PDTCH + +The G-RNTI is used to identify uniquely the mobile station when sending on uplink. The Radio bearer Id is used to identify the RLC instance to which the RLC/MAC block belongs. Every RLC data block that is sent on any of the mobile station's TBFs, shall include the G-RNTI of the mobile station, until the contention resolution is completed on the mobile station side. + +The retransmission of an RLC data block shall include the G-RNTI if the RLC data block was originally transmitted including this field, also if the retransmission occurs after the completion of the contention resolution. + +At sending of the first RLC data block, the mobile station shall set counter N3104 to 1, and start timer T3166. The counter N3104 shall be incremented each time the mobile station sends a RLC data block. + +The network shall respond by including the G-RNTI in the PACKET UPLINK ACK/NACK message after the first correctly received RLC data block that comprises the G-RNTI and valid RB Id. + +The contention resolution is completed on the network side when the network receives an RLC data block that comprises the G-RNTI value that identifies the mobile station, and a valid RB Id that identifies the RLC instance to which the RLC/MAC block belongs. + +The contention resolution is successfully completed on the mobile station side when the mobile station receives a PACKET UPLINK ACK/NACK message addressing the mobile station with a valid RBId (contained in the UPLINK\_TFI field, see 3GPP TS 44.060) and including the same G-RNTI value that the mobile station included in the RLC header of the first RLC data blocks. The mobile station shall then stop timer T3166 and counter N3104. + +The contention resolution has failed on the mobile station side when the counter N3104 reaches its maximum value, or timer T3166 expires. The contention resolution also fails, if the mobile station receives a PACKET UPLINK ACK/NACK message addressing the mobile station with a G-RNTI value other than that the mobile station included in the RLC header of the first RLC data blocks; in such a case, the mobile station shall not transmit a PACKET CONTROL ACKNOWLEDGEMENT in the uplink radio block specified if a valid RRBP field is received as part of the PACKET UPLINK ACK/NACK message. + +In case of a contention resolution failure on the mobile station side, the mobile station shall reset the counter N3104 and stop timer T3166. The mobile station shall stop transmitting on the TBF and reinitiate the packet access procedure, unless the packet access procedure has already been attempted four times. In that case, a TBF failure has occurred, see sub-clause 7.2.5. + +#### 7.2.3.3.2.3 Contention resolution at one phase access on SDCCH or FACCH + +The G-RNTI is used to identify uniquely the mobile station when sending on uplink. The Reduced Radio bearer Id is used to identify the RLC instance to which the RLC/MAC block belongs. Every RLC data block that is sent on any of the mobile station's TBFs, shall include the G-RNTI of the mobile station, until the contention resolution is completed on the mobile station side. + +The retransmission of an RLC data block shall include the G-RNTI if the RLC data block was originally transmitted including this field, also if the retransmission occurs after the completion of the contention resolution. + +At sending of the first RLC data block, the mobile station shall set counter N3104 to 1, and start timer T3166. The counter N3104 shall be incremented each time the mobile station sends a RLC data block. + +The network shall respond by including the G-RNTI in the PACKET DBPSCH UPLINK ACK/NACK message after the first correctly received RLC data block that comprises the G-RNTI and valid RRB Id. + +The contention resolution is completed on the network side when the network receives an RLC data block that comprises the G-RNTI value that identifies the mobile station, and a valid RRB Id that identifies the RLC instance to which the RLC/MAC block belongs. + +The contention resolution is successfully completed on the mobile station side when the mobile station receives a PACKET DBPSCH UPLINK ACK/NACK message addressing the mobile station with a valid RbId (i.e. associated with an assigned RRB Id) and including the same G-RNTI value that the mobile station included in the RLC header of the first RLC data blocks. The mobile station shall then stop timer T3166 and counter N3104. + +The contention resolution has failed on the mobile station side when the counter N3104 reaches its maximum value, or timer T3166 expires. The contention resolution also fails, if the mobile station receives a PACKET DBPSCH UPLINK ACK/NACK message addressing the mobile station with a G-RNTI value other than that the mobile station included in the RLC header of the first RLC data blocks; in such a case, the mobile station shall not transmit a PACKET CONTROL ACKNOWLEDGEMENT even if the poll bit is set in the received message. + +In case of a contention resolution failure on the mobile station side, the mobile station shall reset the counter N3104 and stop timer T3166. The mobile station shall stop transmitting on the TBF and reinitiate the packet access procedure, unless the packet access procedure has already been attempted four times. In that case, a TBF failure has occurred, see sub-clause 7.2.5. + +### 7.2.3.4 RLC/MAC procedures during contention resolution + +#### 7.2.3.4.1 RLC/MAC procedures during contention resolution on SBPSCHs + +During the contention resolution, the mobile station may receive a non-distribution RLC/MAC control message addressing the mobile station by G-RNTI or the TFI value associated with the uplink TBF. The mobile station shall act on that message using the procedure defined for the message when it is received in MAC-Shared state during operation on an uplink TBF (see sub-clause 8), with the following restrictions: + +- The mobile station shall not accept a PACKET MEASUREMENT ORDER message, a PACKET CELL CHANGE ORDER message and a PACKET POWER CONTROL/TIMING ADVANCE message addressing the mobile station with the TFI value associated with the uplink TBF. +- The mobile station shall not accept a PACKET DOWNLINK ASSIGNMENT, a MULTIPLE TBF DOWNLINK ASSIGNMENT, a PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message. + +If a valid RRBp field is received as part of the RLC/MAC control block and the mobile station acts on the message, then it shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified (see 3GPP TS 44.060 sub-clause 10.4.5); The mobile station shall not transmit a PACKET CONTROL ACKNOWLEDGEMENT message if it does not act on the received message. + +In either case, the mobile station shall continue with the contention resolution on the uplink TBF, till it either completes successfully or fails, or that the uplink TBF is released as a result of the procedure defined for the message that is received. + +During the contention resolution at one phase access, the mobile station shall not send a Packet Resource Request message to request the establishment of additional UL TBFs. + +#### 7.2.3.4.2 RLC/MAC procedures during contention resolution on DBPSCHs + +During the contention resolution, the mobile station may receive a non-distribution RLC/MAC control message addressing the mobile station by G-RNTI, RB Id (PACCH) or the RRB Id (SDCCH or FACCH) value associated with one its uplink TBFs. The mobile station shall act on that message using the procedure defined for the message in sub-clause 9. + +If a RLC/MAC control block is received with the poll bitset or with valid RRBp field and the mobile station acts on the message, then it shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the next possible uplink occurrence on the same logical channel. The mobile station shall continue with the contention resolution on the uplink + +TBF, until it either completes successfully or fails, or that the uplink TBF is released through release of the dedicated resource using the CRLC-CONFIG primitive (see sub-clause 4.3.3.1) + +### 7.2.3.5 One phase packet access completion + +#### 7.2.3.5.1 One phase packet access completion on SBPSCHs + +See 3GPP TS 44.060 sub-clause 7.1.2.4. + +#### 7.2.3.5.2 One phase packet access completion on DBPSCHs + +The one phase packet access procedure is completed upon a successful contention resolution. + +### 7.2.3.6 Timing Advance + +#### 7.2.3.6.1 Timing advance on SBPSCHs + +See 3GPP TS 44.060 sub-clause 7.1.2.5. + +#### 7.2.3.6.2 Timing advance on DBPSCHs + +Initial timing advance may be provided in the PACKET DBPSCH ASSIGNMENT message in the TIMING\_ADVANCE\_VALUE field. + +## 7.2.4 TBF establishment using two phase access + +### 7.2.4.1 Initiation of the Packet resource request procedure + +In the first phase of a two-phase access, the same procedures as for one-phase access shall be used until the network sends to the mobile station a PACKET UPLINK ASSIGNMENT message including a *Single Block Allocation struct* or a *Multi Block Allocation struct*. The network may only include a *Multi Block Allocation struct* if it sends the PACKET UPLINK ASSIGNMENT message in response to an EGPRS PACKET CHANNEL REQUEST. + +A two-phase access may be initiated: + +- by the network, by ordering the mobile station to send a PACKET RESOURCE REQUEST message. The order shall be sent implicitly to the mobile station in the PACKET UPLINK ASSIGNMENT message by including a *Single Block Allocation struct* or a *Multi Block Allocation struct*; +- by a mobile station, by requiring a two-phase access in the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. If access is granted, the network shall order the mobile station to send a PACKET RESOURCE REQUEST message. The order shall be sent implicitly to the mobile station in the PACKET UPLINK ASSIGNMENT message by including a *Single Block Allocation struct* or a *Multi Block Allocation struct*. + +When the mobile station has received the PACKET UPLINK ASSIGNMENT message, it shall respond with a PACKET RESOURCE REQUEST message in the first allocated radio block. If the network allocated more than a single radio block, the mobile station shall send any of the following in each additional block: + +- Another control block (e.g., a PACKET UPLINK DUMMY CONTROL BLOCK or a PACKET MEASUREMENT REPORT message); however, the mobile station shall not send an ADDITIONAL MS RADIO ACCESS CAPABILITIES message or a PACKET RESOURCE REQUEST message. +- Nothing. + +The mobile station may request the establishment of multiple UL TBFs in the PACKET RESOURCE REQUEST message. The *MS Radio Access Capability* IE shall not be included in the PACKET RESOURCE REQUEST message. If ciphering is used, the least significant bit of the uplink HFN of the radio bearer for which radio resources are requested, shall be inserted in the PACKET RESOURCE REQUEST message. If the least significant bit of the HFN in the network for the same radio bearer in the same direction is different from the one received from the mobile station, the network shall increase its HFN by one unit. + +When the mobile station switches to the assigned PDCH, it shall take the power control parameters received in the PACKET UPLINK ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for MAC-Shared state (see 3GPP TS 45.008). + +At sending of the PACKET RESOURCE REQUEST message, the mobile station shall start timer T3168 for each of the radio bearers for which resources were requested. Furthermore, the mobile station shall not respond to PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT messages - but may acknowledge such messages if they contain a valid RRBP field - while timer T3168 is running, before contention resolution is completed on the mobile station side. + +The mobile station may indicate in the PACKET RESOURCE REQUEST message the number of octets of user data it has to transfer. + +#### 7.2.4.2 Packet resource assignment for uplink procedure + +7.2.4.2.1 (void) + +##### 7.2.4.2.2 On receipt of a PACKET RESOURCE REQUEST message + +On receipt of a PACKET RESOURCE REQUEST message, the network shall respond by sending a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message (radio resources assignment on one or more PDCHs to be used by the mobile station for the TBF in EGPRS or GPRS TBF mode) or a PACKET ACCESS REJECT message to the mobile station on PACCH on the same PDCH on which the mobile station has sent the PACKET RESOURCE REQUEST message. These messages may only be for a subset of the resources requested in the PACKET RESOURCE REQUEST message. For the resource requests that have not been processed by the first assignment or reject message, additional PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT or PACKET ACCESS REJECT messages may be sent to the mobile station on the PACCH to which the mobile station has been assigned. + +On receipt of a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message the mobile station shall switch to the assigned PDCHs. If dynamic or extended dynamic allocation is assigned then start timer T3164 for each of the TBFs that have been assigned resources. + +At sending of the first RLC data block on a TBF, the mobile station shall stop timer T3164 for that TBF. + +The mobile station may use information received on PBCCH or a previous assignment message to decode the frequency parameters contained in the assignment message. If the mobile station detects an invalid Frequency Parameters information element in the assignment message, it shall abort the procedure, if required initiate a *partial acquisition* of PBCCH information, and may then re-initiate the access on the PRACH. + +On receipt of a PACKET ACCESS REJECT message that contains a Reject structure addressed to the mobile station, the mobile station shall stop timer T3168 and indicate a packet access failure to upper layer for those TBFs identified as rejected in the message. + +If the PACKET ACCESS REJECT message contains a WAIT\_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall start timer T3172 with the indicated value (Wait Indication). The mobile station is not allowed to make a new attempt for packet access in the same cell until all instances of timer T3172 expires, but may attempt packet access in another cell after successful cell reselection. + +#### 7.2.4.3 Contention resolution at two phase access + +The contention resolution is completed on the network side when the network receives a G-RNTI value identifying the mobile station, as part of the contention resolution procedure on the TBF. + +The contention resolution is completed on the mobile station side when the mobile station receives a PACKET UPLINK ASSIGNMENT message or MULTIPLE TBF UPLINK ASSIGNMENT message with the same G-RNTI as the mobile station has included in the PACKET RESOURCE REQUEST message and assigning resource to at least one radio bearer that requested resource in the PACKET RESOURCE REQUEST message. The mobile station shall then stop timer T3168 for each radio bearer for which resource is granted. It does not include its G-RNTI in any RLC data block. + +The contention resolution has failed on the mobile station side when the mobile station does not receive a PACKET UPLINK ASSIGNMENT message or MULTIPLE TBF UPLINK ASSIGNMENT message with its G-RNTI, assigning resource to at least one radio bearer that requested resource in the PACKET RESOURCE REQUEST message, before expiry of timer T3168. The mobile station shall then reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred for all of the requested TBF(s) and an RLC/MAC error should be reported to the higher layer for each of the radio bearers that requested resources. + +On expiry of an instance of timer T3168 after contention resolution is completed on the mobile station side, TBF establishment for the corresponding radio bearer has failed. In that case the mobile station shall reinitiate resource request for that radio bearer using the procedures described in sub-clause 8.2.2.1.2 + +#### 7.2.4.4 Two phase packet access completion + +See 3GPP TS 44.060 sub-clause 7.1.3.4. + +#### 7.2.4.5 Timing Advance + +See 3GPP TS 44.060 sub-clause 7.1.3.5. + +### 7.2.5 Abnormal cases + +If a failure occurs on the mobile station side of the new TBF before the mobile station has successfully completed contention resolution, the newly reserved resources are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the failure is due to a G-RNTI mismatch, or to the expiry of timers T3166 or T3168, or to the fact that the counter N3104 reaches its maximum value in the contention resolution procedure, and repetition as described in sub-clauses 7.2.3.3, 3GPP TS 44.060 sub-clause 7.1.3.2.1 or sub-clause 7.1.3.3 has been performed, the mobile station shall return to MAC-Idle state, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection may take place, unless the failure takes place during a Packet Cell Change Order procedure, in which case the mobile behaviour shall be as described in the Abnormal cases of the Network controlled cell reselection procedure in 3GPP TS 44.060 sub-clause 8.4.2. +- If the mobile station has been assigned more PDCHs than it supports according to its MS multislot class, the mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred. +- If the information in the PACKET UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or violates the mobile station's multislot capabilities, the mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred. +- If the mobile station has been assigned more than one DBPSCH/S, the mobile station shall reinitiate the packet access procedure unless the packet access procedure has been attempted four times. In that case, TBF failure has occurred. +- If the information in the PACKET DBPSCH ASSIGNMENT message does not properly specify a DBPSCH or violates the mobile station's multislot capabilities, the mobile station shall reinitiate the packet access procedure (i.e. using access cause "dedicated channel request") unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred. +- If the mobile station has been assigned a TCH that it does not support (e.g. using 8-PSK), the mobile station shall return to MAC-Idle state and notify higher layers (TBF establishment failure). +- If the information in the MULTIPLE TBF UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or violates the mobile station's multislot capabilities, the mobile station shall reinitiate the packet access procedure for each of the TBFs for which there is an error unless the procedure has already been attempted 4 times for the TBF. In that case, TBF failure has occurred. +- If the MULTIPLE TBF UPLINK ASSIGNMENT message contains assignments for radio bearers for which a TBF was not requested, the mobile station shall not act upon these assignments. The mobile station shall act upon the valid assignments. +- If the MULTIPLE TBF UPLINK ASSIGNMENT message contains assignments such that more than one RB is mapped onto one TBF, then TBF failure has occurred for each of the RBs that are mapped onto the same TBF. +- If the mobile station has been assigned a TBF in EGPRS mode and the MS does not support EGPRS, or has been assigned an MCS (e.g. 8-PSK in the Uplink) that the MS does not support, the MS shall return to MAC-Idle state and notify higher layers (TBF establishment failure). +- On expiry of timer T3164, the mobile station shall reinitiate the packet access procedure for the related RB unless the packet access procedure has already been attempted four times for this RB, in which case the mobile + +station shall notify higher layers of TBF establishment failure. If the mobile station has no remaining TBFs it shall return to MAC-Idle state. + +- If the failure is due to any other reason, the mobile station shall return to MAC-Idle state, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continues. + +## 7.3 TBF establishment initiated by the network on PCCCH + +### 7.3.1 General + +The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of upper layer PDUs in the direction from the network to the mobile station. The procedure may be entered when the mobile station is in MAC-Idle state. Network initiated TBF establishment can also be done on PACCH if a TBF for transfer of upper layer PDUs in the direction from the mobile station to the network is already established (sub-clause 8.2.3.5). + +If the mobile station is in MAC-Dedicated state the establishment of a TBF shall be performed by procedures that are specified in 3GPP TS 44.118. + +### 7.3.2 Entering the MAC-Shared state + +#### 7.3.2.1 General + +The procedure is triggered by a request from upper layers on the network side to transfer an upper layer PDU to a mobile station in MAC-Idle state. The request is implicit when receiving an upper layer PDU to a mobile station not already having any assigned radio resources. Upon such a request, the network shall initiate a packet downlink assignment procedure as defined in sub-clause 7.3.2.2. + +#### 7.3.2.2 Packet downlink assignment procedure + +##### 7.3.2.2.1 Packet downlink assignment procedure + +See 3GPP TS 44.060 sub-clause 7.2.1.1. + +##### 7.3.2.2.2 HFN synchronization + +If ciphering is used, the least significant bit of the downlink HFN of this radio bearer shall be inserted in the PACKET DOWNLINK ASSIGNMENT message sent in the packet downlink assignment procedure (see sub-clause 7.3.2.2.1). If the least significant bit of the HFN in the mobile station for the same radio bearer in the same direction is different from the one received from the network, the mobile station shall increase its HFN by one unit. + +#### 7.3.2.3 Packet downlink assignment procedure completion + +See 3GPP TS 44.060 sub-clause 7.2.1.2. + +#### 7.3.2.4 Packet polling procedure + +See 3GPP TS 44.060 sub-clause 7.2.1.3. + +#### 7.3.2.5 Abnormal cases + +See 3GPP TS 44.060 sub-clause 7.2.2. + +### 7.3.3 Entering the MAC-Dedicated state + +#### 7.3.3.1 General + +The procedure is triggered by a request from upper layers on the network side to transfer an upper layer PDU to a mobile station in MAC-Idle state. The request is implicit when receiving an upper layer PDU to a mobile station not already having any assigned radio resources and the request requires dedicated resources. Upon such a request, the network shall initiate a packet DBPSCH assignment procedure as defined in sub-clause 7.3.3.2. + +### 7.3.3.2 Packet DBPSCH assignment procedure + +The network may assign a radio resource on one or more DBPSCHs to be used for the TBF. The amount of radio resources to be reserved is a network dependent choice. The network shall not assign radio resources on more than one DBPSCH/S to the TBF. + +The allocated radio resource is assigned to the mobile station in a PACKET DBPSCH ASSIGNMENT message to the mobile station. The PACKET DBPSCH ASSIGNMENT message is transmitted on the PCCCH timeslot corresponding to the PCCCH group the mobile station belongs to. The appropriate PCCCH group is calculated from the IMSI (see 3GPP TS 45.002). The behaviour of the network when the IMSI is not provided by the upper layers is implementation dependent for the calculation of the PCCCH group where the PACKET DBPSCH ASSIGNMENT message has to be sent. If the mobile station is in non-DRX mode or if the IMSI or the DRX parameters are not provided by the upper layers, there is no further restriction on what part of the downlink PCCCH timeslot this PACKET DBPSCH ASSIGNMENT message can be sent, provided that this part corresponds to one or more blocks where paging may appear. If the mobile station applies DRX, this message shall be sent in one or more PCCCH block(s) corresponding to a paging group determined for the mobile station in MAC-Idle state (see 3GPP TS 45.002). The multislot capabilities of the mobile station shall be considered. + +Initial timing advance can be provided in the PACKET DBPSCH ASSIGNMENT message as Timing Advance Value field. For the case where Timing Advance Value is not provided in the assignment message, the mobile station is not allowed to send normal bursts (e.g. PACKET DOWNLINK ACK/NACK message) on the uplink until it receives a valid timing advance on the SACCH. + +The mobile station shall use information received on the PBCCH to decode the channel descriptions contained in the assignment. If frequency hopping is applied, the mobile station shall use the last CA received on PBCCH to decode the Mobile Allocation. Alternatively, the network may provide a Mobile Allocation in the assignment. The radio resource is assigned to the mobile station in a PACKET DBPSCH ASSIGNMENT message. On receipt of a PACKET DBPSCH ASSIGNMENT message, the mobile station shall switch to the assigned DBPSCHs. + +If the mobile station receives more than one PACKET DBPSCH ASSIGNMENT message while it monitors the PCCCH, it shall act upon the most recently received message and shall ignore the previous message. + +When the PACKET DBPSCH ASSIGNMENT message is received the mobile station shall switch to the assigned DBPSCH(s), start timer T3190 and enters the MAC-Dedicated state. The timer T3190 is restarted when receiving the first valid RLC data block addressed to itself. + +When the mobile station switches to the assigned DBPSCHs, it shall take the power control parameters received in the PACKET DBPSCH ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for MAC-Dedicated state (see 3GPP TS 45.008). + +On expiry of timer T3190, the mobile station shall abort the procedure and return to MAC-Idle state. + +### 7.3.3.3 Packet DBPSCH assignment procedure completion + +The Packet DBPSCH assignment procedure is completed when the mobile station receives a valid RLC/MAC block. + +### 7.3.3.4 Packet polling procedure + +On receipt of a control message with the poll bit set, the mobile station shall respond to the network with the PACKET CONTROL ACKNOWLEDGEMENT message. + +### 7.3.3.5 Abnormal cases + +If a failure occurs on the mobile station side of the new TBF before mobile station has successfully entered the MAC-Dedicated state, the newly reserved resources are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the mobile station has been assigned more DBPSCHs than it supports according to its MS multislot class, the mobile station shall ignore the assignment and return to MAC-Idle state. +- If the mobile station has been assigned more than one DBPSCH/S, the mobile station shall ignore the assignment and return to MAC-Idle state +- On expiry of timer T3190, the mobile station shall return to MAC-Idle state. + +- If the failure is due to any other reason, the mobile station shall ignore the assignment and return to MAC-Idle state and cell reselection continues. + +## 7.4 Procedure for measurement report sending in MAC-Idle state + +### 7.4.1 General + +The procedure for measurement report sending shall be initiated by the mobile station at expiry the NC measurement report interval timer T3158. At expiry of the timer T3158 shall restart the expired timer T3158, perform the measurements and initiate the packet access. + +The procedure for measurement report sending is initiated by the mobile station on PCCCH (sub-clause 7.4.2). + +If the mobile station initiates the establishment of a DBPSCH, the timer T3158 shall be stopped and no measurement reports shall be sent. When the last DBPSCH is released and if the mobile station has not changed cell, the measurement reporting procedure shall be restarted. + +If a cell change has occurred while the mobile station had one or more DBPSCHs allocated, the measurements shall be cancelled until new NC orders have been received (see sub-clause 5.5). + +### 7.4.2 Measurement report sending procedure initiated on PCCCH + +#### 7.4.2.1 General + +The packet access procedure is initiated by the MAC entity in the mobile station as specified in sub-clauses 7.2.3.1 and 7.2.3.2 but with access type "Single block without TBF establishment" indicated in the PACKET CHANNEL REQUEST message. + +#### 7.4.2.2 On receipt of a PACKET CHANNEL REQUEST message + +See 3GPP TS 44.060 sub-clause 7.3.1.1. + +#### 7.4.2.3 On receipt of a PACKET UPLINK ASSIGNMENT message + +See 3GPP TS 44.060 sub-clause 7.3.1.2. + +#### 7.4.2.4 On receipt of a PACKET ACCESS REJECT message + +See 3GPP TS 44.060 sub-clause 7.3.1.3. + +#### 7.4.2.5 Abnormal cases + +See 3GPP TS 44.060 sub-clause 7.3.1.4. + +## 7.5 Cell Change Order procedures in MAC-Idle state + +### 7.5.1 General + +For an individual mobile station in MAC-Idle state, the network may initiate the cell change order procedure on PCCCH. + +The network may initiate the cell change order procedure by sending a PACKET CELL CHANGE ORDER message in a PCCCH block monitored by the mobile station. No TBF shall be established. + +The PACKET CELL CHANGE ORDER message contains: + +- The characteristics of the new cell that are necessary to identify it (i.e. BSIC + BCCH frequency). +- The NC measurement parameters valid for the mobile station in the new cell (NETWORK\_CONTROL\_ORDER and optionally: NC\_NON\_DRX\_PERIOD, NC\_REPORTING\_PERIOD\_I and NC\_REPORTING\_PERIOD\_T). + +For a multi-RAT mobile station, the PACKET CELL CHANGE ORDER message may contain information on a 3G target cell; in the case of UTRAN, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 25.331. + +Upon receipt of the PACKET CELL CHANGE ORDER message, the mobile station shall stop all relevant RLC/MAC timers except for timers related to measurement reporting and start timer T3174. The mobile station shall then switch to the specified new cell and obey the relevant RLC/MAC procedures on this new cell. If a valid RRBP field was received in the PACKET CELL CHANGE ORDER message then the MS shall send a PACKET CONTROL ACKNOWLEDGMENT message in the reserved uplink radio block specified by the RRBP field before switching to the new cell. If the timers related to measurement reporting expire while the reselection procedure has not yet been completed, these timers shall be restarted so that the mobile station resumes the measurement reporting procedures once camped on the new cell. The mobile station shall obey the PACKET CELL CHANGE ORDER message irrespective of whether or not the mobile station has any knowledge of the relative synchronisation of the target cell to the serving cell. A UTRAN capable mobile station shall obey the command irrespective of whether the cell is known or not known (see 3GPP TS 25.133 and 3GPP TS 25.123). + +The procedure for completion of the cell change order is defined in 3GPP TS 44.060 sub-clause 8.4.1 and abnormal procedures are defined in 3GPP TS 44.060 sub-clause 8.4.2. + +## 7.6 Measurement Order procedures in MAC-Idle state + +### 7.6.1 General + +To send the NC Measurement order to an individual mobile station in MAC-Idle state, the network may establish a connection on PCCCH. + +### 7.6.2 Measurement Order procedures initiated on PCCCH + +See 3GPP TS 44.060 sub-clause 7.5.1. + +--- + +## 8 Medium Access Control (MAC) procedures on SBPSCH + +### 8.1 General + +The MAC procedures defined in this sub-clause are applicable in MAC-Shared state and MAC-DTM state. + +The full set of downlink assignment messages comprises the PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT and MULTIPLE TBF TIMESLOT RECONFIGURE messages. + +The full set of uplink assignment messages comprises the PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF UPLINK ASSIGNMENT and MULTIPLE TBF TIMESLOT RECONFIGURE messages. + +The network may choose to send either single assignment messages (PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE) or multiple TBF assignment messages (MULTIPLE TBF DOWNLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE) on the PACCH. The network shall only use the multiple TBF assignment messages when assigning or reallocating the mobile station with more than one uplink TBF and/or more than one downlink TBF. + +### 8.1a Resource stealing (SFACCH) + +The use of SFACCH in MAC-Shared state for SRBs 1 through 4 is specified in sub-clause 5.6.2.2. + +The use of SFACCH in MAC-DTM state for SRBs 3 and 4 is specified in sub-clause 5.6.2.3. SFACCH shall not be used for SRBs 1 and 2 in MAC-DTM state. + +If the mobile station has data to send for an SRB that can be sent on SFACCH, and neither a TBF nor a TBF establishment request is ongoing for this SRB, the following procedure applies: + +- The mobile station may select a current TBF on an SBPSCH, construct an uplink RLC data block that includes octet 3 (this octet contains the SRBid), and send the SRB data at the TBF's next scheduled transmission + +opportunity for an RLC data block. GERAN shall use the SRBid to route the SRB data to the correct RLC instance. + +- Otherwise, the mobile station shall initiate a new TBF operating on an SBPSCH (see sub-clause 8.2.2.0.2). + +If the mobile station has data to send for an SRB, and a TBF exists for this SRB, the following procedure applies: + +- The mobile station shall construct an uplink RLC data block that does not include octet 3 and send the SRB data on the TBF. + +If GERAN has data to send for an SRB that can be sent on SFACCH, and no TBF exists for this SRB, the following procedure applies: + +- GERAN may select a current TBF on an SBPSCH, construct a downlink RLC data block that includes octet 3, and send the SRB data at the TBF's next scheduled transmission opportunity for an RLC data block. The mobile station shall use the SRBid to route the SRB data to the correct RLC instance. +- Otherwise, GERAN shall establish a new TBF operating on an SBPSCH (see sub-clause 8.2.2.0.2). + +If GERAN has data to send for an SRB, and a TBF exists for this SRB, the following procedure applies: + +- GERAN shall construct a downlink RLC data block that does not include octet 3 and send the SRB data on the TBF. + +## 8.2 Transfer of RLC data blocks + +### 8.2.1 Medium access mode + +The transfer of RLC data blocks on SBPSCH is governed by different principles on both uplink and downlink for each of the defined medium access modes: dynamic allocation, extended dynamic allocation, and exclusive allocation. + +The medium access mode the mobile station is to use, except when exclusive allocation is applied in MAC-DTM state, is given by the MAC\_MODE parameter. The MAC\_MODE parameter is included in the downlink assignment (e.g. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) message, whereas in the uplink the MAC\_MODE parameter is given by the EXTENDED\_DYNAMIC\_ALLOCATION parameter. The value of the MAC\_MODE parameter shall not be changed while the mobile station is in MAC-Shared state or MAC-DTM state. + +Exclusive allocation is applicable only in MAC-DTM state when a single TBF is allocated on a half-rate PDCH. + +When the conditions for exclusive allocation are fulfilled, the mobile station shall store the value of the MAC\_MODE parameter. The MAC\_MODE parameter has no effect as long as exclusive allocation is used. When the conditions for exclusive allocation are not fulfilled, the mobile station shall use the medium access mode given by the value of the MAC\_MODE parameter. + +### 8.2.2 Uplink RLC data block transfer + +#### 8.2.2.0 General + +##### 8.2.2.0.1 General + +See 3GPP TS 44.060 sub-clause 8.1.1. + +##### 8.2.2.0.2 Establishment of additional uplink TBF(s) + +When the mobile station has data to send that does not have the same radio bearer identity as (any of) the uplink TBF(s) or TBF request(s) in progress, the mobile station shall request uplink resources through one of the following procedures: + +- If the data belongs to a signalling radio bearer + - Use the SFACCH (see sub-clause 8.1a) + - Establish an additional TBF (sub-clause 8.2.2.1.2) + +- If the mobile station cannot support the establishment of an additional TBF, then the network may release an on-going TBF in order to establish a new TBF (sub-clause 8.2.2.1.2) +- If the data belongs to a user radio bearer +- Establish an additional TBF (sub-clause 8.2.2.1.2) +- If the mobile station cannot support the establishment of an additional TBF, then the network may release an on-going TBF in order to establish a new TBF (sub-clause 8.2.2.1.2) + +#### 8.2.2.0.3 Uplink resource reallocation / reconfiguration + +Neither the mobile station nor the network are allowed to modify the RLC mode, TBF mode or radio bearer identity of an already established TBF. If the mobile station has data to send that requires a modification of existing uplink resources, an uplink resource request shall be sent, see sub-clause 8.2.2.0.2. + +If no modifications to the uplink resources are required, the network may reallocate existing resources through one of the following procedures: + +- The network may send a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message to the mobile station on the PACCH to reallocate uplink (and also downlink) resources, see sub-clause 8.2.2.1.2.2. +- The network may send a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message to the mobile station on the PACCH to reallocate uplink resources, see sub-clause 8.2.2.1.2.2. + +#### 8.2.2.0.4 Establishment of downlink TBF(s) + +During uplink data transfer, the network may initiate downlink data transfer for one or more TBFs by sending a downlink assignment message to the mobile station on the downlink PACCH. + +The network initiates assignment of a single downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message. The network initiates assignment of more than one downlink TBF by sending a MULTIPLE TBF DOWNLINK ASSIGNMENT or a MULTIPLE TBF TIMESLOT RECONFIGURE message. + +The procedure to be followed is described in sub-clause 8.2.2.1.3. + +### 8.2.2.1 Dynamic Allocation uplink RLC data block transfer + +See 3GPP TS 44.060 sub-clause 8.1.1.1. + +#### 8.2.2.1.1 PACCH operation + +See 3GPP TS 44.060 sub-clause 8.1.1.1.1. + +#### 8.2.2.1.2 Resource Allocation / Reallocation for Uplink + +##### 8.2.2.1.2.1 General + +The mobile station shall initiate the uplink resource (re)allocation procedure by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168 for each TBF request included in the Iu mode Channel Request Description IE. + +##### 8.2.2.1.2.2 On receipt of the PACKET RESOURCE REQUEST + +On receipt of the PACKET RESOURCE REQUEST message the network shall respond by sending one or more uplink assignment messages (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET TIMESLOT RECONFIGURE) and/or a PACKET ACCESS REJECT message and/or a PACKET TBF RELEASE message to the mobile station on the downlink PACCH. + +When the mobile station has already been allocated the maximum number of TBFs in the uplink direction that it can support, the network shall respond with either a PACKET ACCESS REJECT message, or a PACKET TBF RELEASE message followed by an uplink assignment message. + +On receipt of an uplink assignment message the mobile station shall stop timer T3168 for each uplink TBF assigned in the assignment message and switch to the assigned SBPSCHs. A new assignment shall not terminate the previous assignment unless the uplink assignment message explicitly contains a reassignment for an on-going TBF. + +On expiry of timer T3168 the mobile station shall retransmit the PACKET RESOURCE REQUEST message for the TBF(s) for which T3168 has expired unless the PACKET RESOURCE REQUEST message has already been transmitted four times for this TBF in which case the mobile station shall indicate a packet access failure to upper layer and perform an abnormal release without retry (see sub-clause 8.7.1). + +If no uplink assignment message is received for a TBF for which timer T3168 is running before the mobile station has completed its currently assigned TBF(s), the mobile station shall stop timer T3168 for that TBF, return to MAC-Idle state and start the packet access procedure on the PCCH. + +The network may at any time during an uplink TBF initiate a change of resources or allocation of new resources by sending on the downlink PACCH monitored by the MS, an unsolicited uplink assignment message to the mobile station. + +On receipt of a PACKET ACCESS REJECT message, the mobile station shall stop timer T3168, if running, for each TBF request rejected in the PACKET ACCESS REJECT message and indicate a packet access failure to the upper layer. If no other uplink or downlink TBFs exist, the mobile station in MAC-Shared state shall return to MAC-Idle state; the mobile station in MAC-DTM state shall return to MAC-Dedicated state. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5. + +If the PACKET ACCESS REJECT message contains a WAIT\_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall + +- start timer T3172 for each TBF request rejected in the message (listed by radio bearer identity). The mobile station is not allowed to make a new attempt for an uplink TBF establishment for this radio bearer in the same cell until this instance of timer T3172 expires. It may attempt a TBF establishment for another radio bearer while T3172 is running. It may attempt an uplink TBF establishment in another cell after successful cell reselection. While T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages. + +The value of the WAIT\_INDICATION field (i.e. timer T3172) relates to the cell from which it was received. + +#### 8.2.2.1.2.3 Abnormal cases + +The following abnormal cases apply: + +- If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message and detects an invalid Frequency Parameters information element in the message, the mobile station shall perform an abnormal release with system information (see sub-clause 8.8.4), performing a partial acquisition of system information messages containing frequency information. +- If the information in the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message incorrectly specifies one or more uplink PDCHs, the mobile station shall perform an abnormal release with access retry of the uplink TBF(s) with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments. +- If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message incorrectly specifies one or more uplink and/or downlink PDCHs, the mobile station shall perform an abnormal release with access retry of the uplink TBF(s) with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments. +- If the information in the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message violates the mobile station's multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message specifying frequencies that are not all in one frequency band then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If the mobile station receives a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message containing a Frequency Parameters information element specifying a + +frequency that is in a frequency band not supported by the mobile station then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). + +- If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message containing assignments such that more than one radio bearer is mapped onto one TBF, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, or MULTIPLE TBF TIMESLOT RECONFIGURE message assigns the same USF to more than one TBF on the same timeslot, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message specifies a RB Id that is not assigned to the mobile station, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If a mobile station in MAC-DTM state receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If the MULTIPLE TBF UPLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE message does not specify a Channel Coding scheme for one or more of the uplink TBFs that it is assigning, then the mobile station shall perform an abnormal release with access retry of the uplink TBFs with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments. +- If the PACKET ACCESS REJECT message does not specify a G-RNTI\_extension field in the Iu mode Reject structure for each G-RNTI included in the TLLI / G-RNTI field in the Reject structure, then the mobile station shall ignore the message. +- If the PACKET ACCESS REJECT message includes one or more RB Id fields in the Iu mode Reject structure which were not included by the mobile station in the Iu mode Channel Request Description structure, then the mobile station shall perform abnormal release with access retry (see sub-clause 8.8.3). +- If a failure in the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). + +A PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message received by a multi-band mobile station shall not be considered invalid if it indicates new frequencies that are all in a different frequency band to that of the PDCH(s) on which the assignment was received. The assignment may however be rendered invalid for some other reason. + +### 8.2.2.1.3 Establishment of downlink TBF + +#### 8.2.2.1.3.1 General + +During uplink transfer, the network may initiate one or more downlink TBFs by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE) to the mobile station on the PACCH. + +If a PACKET TIMESLOT RECONFIGURE message is sent, then the message shall contain the DOWNLINK\_TFI\_ASSIGNMENT field. The multislot restrictions of the mobile station shall be observed. + +A mobile allocation or reference frequency list, received as part of a downlink assignment, replaces the previous parameters and shall be used until a new assignment is received or the mobile station has released all TBFs. + +On receipt of a downlink assignment message, and after the TBF starting time, if present, the mobile station shall switch to the assigned SBPSCHs, and start timer T3190 for each TBF. The operation of the downlink TBF follows the procedures in sub-clause 8.2.3 and 3GPP TS 44.060 sub-clause 8.1.2 with the following additions: + +- the mobile station shall prioritise transmission of RLC/MAC control blocks associated with the downlink TBF over RLC/MAC control blocks associated with the uplink TBF; +- if a timer or counter expiry causes the uplink TBF to be aborted in the mobile station triggering an abnormal release with access retry on PCCH (see sub-clause 8.8.3), the mobile station shall also abort all downlink TBF(s). The mobile station shall not abort the downlink TBF(s) in case an abnormal release with access retry on PACCH is triggered; +- If both uplink and downlink TBFs are already established and if more than one TBF is already established in either/both direction(s), then the network may send a MULTIPLE TBF TIMESLOT RECONFIGURE message. If this message contains a change in frequency in the frequency parameters and does not contain a reassignment for one or more of the mobile station's TBFs, these TBFs are to be released upon moving to the new frequency. If no change in frequency parameters is included, the TBFs not explicitly reconfigured shall continue according to their original assignment. + +#### 8.2.2.1.3.2 Abnormal cases + +In the following abnormal cases it is assumed that at least one uplink TBF exists. The subsequent behaviour of the mobile station depends on the type of failure and previous actions: + +- If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message incorrectly specifies an uplink and/or downlink PDCH, the mobile station shall perform an abnormal release of the downlink TBF(s) with erroneous assignments (see sub-clause 8.8.6). The mobile station shall act upon the valid assignments. +- If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message violates the mobile station's multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If a downlink TBF is not already established and the PACKET TIMESLOT RECONFIGURE message does not include a DOWNLINK\_TFI\_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If a downlink TBF is not already established and the MULTIPLE TBF TIMESLOT RECONFIGURE message does not assign any downlink TBFs, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If the mobile station receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message containing assignments such that more than one radio bearer is mapped onto a TBF, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message specifies a RB Id not assigned to the mobile station, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If a mobile station in MAC-DTM state receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall abort the procedure. If other uplink TBFs exist, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). If only downlink TBFs exist, the mobile station shall continue the normal operation of these TBFs. If no other TBFs exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2). + +#### 8.2.2.2 Extended Dynamic Allocation uplink RLC data block transfer + +##### 8.2.2.2.0 General + +The Extended Dynamic Allocation medium access method extends the Dynamic Allocation medium access method to allow higher uplink throughput. + +This sub-clause defines the extensions to the Dynamic Allocation medium access method. All procedures defined in sub-clause 8.2.2.1 apply, except where this sub-clause defines a new procedure. In cases where this sub-clause conflicts with sub-clause 8.2.2.1, this sub-clause takes precedence. + +#### 8.2.2.2.1 Uplink PDCH Allocation + +See 3GPP TS 44.060 sub-clause 8.1.1.2.1. + +#### 8.2.2.2.2 PACCH operation + +See 3GPP TS 44.060 sub-clause 8.1.1.2.2. + +#### 8.2.2.2.3 Neighbour cell power measurements + +See 3GPP TS 44.060 sub-clause 8.1.1.2.3. + +#### 8.2.2.2.4 Shifted USF operation + +See 3GPP TS 44.060 sub-clause 8.1.1.2.4. + +### 8.2.2.3 Exclusive Allocation uplink RLC data block transfer + +See 3GPP TS 44.060 sub-clause 8.1.1.3a. + +#### 8.2.2.3.1 (void) + +#### 8.2.2.3.2 (void) + +#### 8.2.2.3.3 (void) + +#### 8.2.2.3.4 (void) + +#### 8.2.2.3.5 (void) + +#### 8.2.2.3.6 (void) + +#### 8.2.2.4 Network initiated release of uplink TBF + +See 3GPP TS 44.060 sub-clause 8.1.1.4. + +#### 8.2.2.5 Abnormal cases + +The following additional abnormal cases are applicable to an uplink transfer:- + +- if the mobile station receives a PACKET UPLINK ACK/NACK message with missing mandatory fields, the mobile station shall perform an abnormal release with access retry of the uplink TBF (sub-clause 8.8.5) associated with this message. +- if the mobile station receives a PACKET UPLINK ACK/NACK message that contains a RB Id that is not assigned to the mobile station or that is assigned to the mobile station but without any corresponding uplink TBF, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). + +### 8.2.3 Downlink RLC data block transfer + +#### 8.2.3.1 General + +##### 8.2.3.1.0 General + +The network initiates assignment of a single downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message on the downlink PACCH. The network initiates assignment of more than one downlink TBF by sending a MULTIPLE TBF DOWNLINK ASSIGNMENT or a MULTIPLE TBF TIMESLOT RECONFIGURE message on the downlink PACCH. Prior to the initiation of RLC data block transfer on the downlink, the network assigns the following parameters to the downlink TBF in the downlink assignment message: + +- a Temporary Flow Identity (TFI). The TFI applies to all radio blocks transferred in regards to the downlink Temporary Block Flow (TBF). +- a radio bearer identity (RB Id). There is a one-to-one mapping between the TFI and the RB Id of the radio bearer for which the downlink TBF is established. +- a set of PDCHs to be used for the downlink transfer; +- optionally, a TBF starting time indication. + +For each TBF, the network shall prioritise RLC/MAC control blocks, not containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message, to be transmitted ahead of RLC data blocks for that TBF. If the network has no other RLC/MAC block to transmit, but wishes to transmit on the downlink, the network shall transmit an RLC/MAC control block containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message. + +#### 8.2.3.1.1 Downlink resource reallocation + +Neither the mobile station nor the network are allowed to modify the RLC mode, TBF mode or radio bearer identity of an already established TBF. + +If no modifications to the downlink resources are required, the network may reallocate existing resources through one of the following procedures: + +- The network may send a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message to the mobile station on the PACCH to reallocate downlink (and also uplink) resources, see sub-clause 8.2.3.2. +- The network may send a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message to the mobile station on the PACCH to reallocate downlink resources, see sub-clause 8.2.3.2. + +#### 8.2.3.1.2 (void) + +#### 8.2.3.2 Downlink RLC data block transfer procedure + +##### 8.2.3.2.0 General + +Upon reception of a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE) that does not contain a TBF starting time the mobile station shall start timer T3190 for each downlink TBF assigned in the downlink assignment message and, within the reaction time defined in 3GPP TS 45.010, it shall attempt to decode every downlink block on its assigned SBPSCH(s). If the downlink assignment message contains a TBF starting time information element and there are no downlink TBFs in progress, but one or more uplink TBFs are in progress, the mobile station shall remain on the assigned SBPSCHs until the TDMA frame number indicated by the TBF starting time, at which time the mobile station shall start timer T3190 for each downlink TBF assigned in the downlink assignment message and immediately begin decoding the assigned downlink SBPSCH(s). + +If the downlink assignment message contains a TBF starting time and there are one or more downlink TBFs already in progress, the mobile station shall continue to use the parameters of the downlink TBFs in progress until the TDMA frame number indicated in the TBF starting time occurs, at which time the mobile station shall immediately begin to use the new assigned downlink TBF parameters. If, while waiting for the frame number indicated by the TBF starting time, the mobile station receives another downlink assignment for the same TBF, the mobile station shall act upon the most recently received downlink assignment and shall ignore the previous downlink assignment. Procedures on receipt of a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT message) while no TBF is in progress are specified in sub-clause 7.3.2.1 and 3GPP TS 44.060 sub-clause 7.2.1.1. + +If the mobile station receives a valid RLC data block addressed to (one of) its TBF(s), the mobile station shall restart timer T3190 for that TBF. If timer T3190 expires for a TBF and if one or more uplink TBFs are in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3, 3GPP TS 44.060 sub-clause 8.7.2). If no other TBFs are in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1). + +Upon receipt of a PACKET TBF RELEASE message referring to the downlink TBF, the mobile station shall follow the procedure in sub-clause 8.2.3.6. + +### 8.2.3.2.1 Abnormal cases + +The following abnormal cases apply: + +- If a mobile station receives a PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message and detects an invalid Frequency Parameters information element in the message, it shall perform an abnormal release with system information (see sub-clause 8.8.4), performing a partial acquisition of system information messages containing frequency information. +- If the information in the PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message incorrectly specifies one or more downlink PDCHs, the mobile station shall perform an abnormal release of the downlink TBF(s) with erroneous assignments (see sub-clause 8.8.6). The mobile station shall act upon the valid assignments. +- If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message incorrectly specifies one or more uplink and/or downlink PDCHs, the mobile station shall perform an abnormal release of the downlink TBF(s) with erroneous assignments (see sub-clause 8.8.6). The mobile station shall act upon the valid assignments. +- If the information in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message violates the mobile station's multislot capabilities, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2). +- If a mobile station in MAC-DTM state receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message including the Frequency Parameters information element, the mobile station shall abort the procedure. If another TBF exists on a SBPSCH, the mobile station shall continue the normal operation of these TBFs. If no other TBF exists, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2). +- If a mobile station in MAC-DTM state receives a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2). +- If one or more uplink TBFs are already established and the mobile station receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for the uplink TBF(s), the mobile station shall ignore the received message and continue normal operation of the existing TBFs. +- If a downlink TBF is not already established and the PACKET TIMESLOT RECONFIGURE message does not include a DOWNLINK\_TFI\_ASSIGNMENT field, then the mobile station shall perform an abnormal release without retry (sub-clause 8.8.2). +- If a downlink TBF is not already established and the MULTIPLE TBF TIMESLOT RECONFIGURE message does not assign any downlink TBFs, then the mobile station shall perform an abnormal release without retry (sub-clause 8.8.2). +- If the mobile station receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message containing assignments such that more than one radio bearer is mapped onto a TBF, then the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2). +- If the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message specifies an RB Id that is not assigned to the mobile station, then the mobile station shall perform an abnormal release without retry (sub-clause 8.8.2). +- If the mobile station receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT message so that the total amount of downlink TBFs assigned to the mobile station (i.e. new and existing TBFs) is larger than the maximum number of downlink TBFs the mobile station supports, the mobile station shall ignore the message and continue normal operation of the existing TBFs. + +- If the mobile station receives a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message so that the total amount of TBFs assigned to the mobile station (i.e. new and existing TBFs) in any direction is larger than the maximum number of TBFs the mobile station supports in any direction, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall abort the procedure. If other uplink TBFs exist, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). If only downlink TBFs exist, the mobile station shall continue the normal operation of these TBFs. If no other TBFs exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2). + +### 8.2.3.3 Polling for Packet Downlink Ack/Nack + +Whenever the mobile station receives an RLC data block addressed to (one of) its TBF(s) with a valid RRBP field in the RLC data block header (i.e. is polled), the mobile station may transmit one of the following messages in the uplink radio block specified by the RRBP field whatever the BSN value of the received RLC data block, according to the subsequent decreasing order of priority: + +- 1) (EGPRS) PACKET DOWNLINK ACK/NACK message containing a Final Ack Indicator, +- 2) PACKET CELL CHANGE NOTIFICATION, if such a message is waiting to be transmitted, +- 3) (EGPRS) PACKET DOWNLINK ACK/NACK message containing a Channel Request Description IE, +- 4) any other RLC/MAC control message, if such a message is waiting to be transmitted, other than a (EGPRS) PACKET DOWNLINK ACK/NACK, +- 5) (EGPRS) PACKET DOWNLINK ACK/NACK message not containing a Final Ack Indicator or a Channel Request Description IE. + +However, the mobile station shall transmit an RLC/MAC control message other than a (EGPRS) PACKET DOWNLINK ACK/NACK message at most every second time it is polled for that TBF. + +The mobile station shall not send a PACKET CONTROL ACKNOWLEDGEMENT message unless otherwise specified. + +In EGPRS TBF mode the mobile station shall react on a poll inside an erroneously received RLC data block for which the header is correctly received and which addresses the mobile station. + +Whenever the network receives a valid RLC/MAC control message from the TBF, it shall reset counter N3105. The network shall increment counter N3105 for each radio block allocated to that TBF with the RRBP field, for which no RLC/MAC control message is received. If N3105 = N3105max, the network shall release the downlink TBF internally and start timer T3195 for that TBF. When T3195 expires, the network may reuse the TFI. + +The PACKET DOWNLINK ACK/NACK message contains a Channel Quality Report (see 3GPP TS 45.008). The optional I\_LEVEL measurement results shall be included in at least every other PACKET DOWNLINK ACK/NACK message. + +The EGPRS PACKET DOWNLINK ACK/NACK message may contain an EGPRS Channel Quality Report (see 3GPP TS 45.008). + +In the case of simultaneous uplink and downlink TBFs, the transmission of the polling response takes precedence over the transmission of allocated uplink radio blocks. + +A mobile station of multislot class 1 to 12 need not respond to the poll if it is not compliant with the mobile station's multislot class (see 3GPP TS 45.002). + +A mobile station of multislot class 13 to 18 shall always respond to the poll. + +NOTE: The mobile station is required to make neighbour cell measurements while transmitting the polling response (see 3GPP TS 45.008). + +### 8.2.3.4 Resource Reassignment for downlink + +The network initiates downlink resource reassignment by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE) to the mobile station on the PACCH. + +If the mobile station has a TBF for which T3192 is running, the network may choose to reallocate this existing TBF and reuse the TFI value for the new data by setting the Control Ack bit to '1' as specified in 3GPP TS 44.060 sub-clauses 9.3.2.6 and 9.3.3.5. + +On receipt of a downlink assignment message and after the TBF starting time, if present, the mobile station shall switch to the assigned SBPSCHs. Upon switching to the new SBPSCHs the mobile station shall restart timer T3190 for each newly assigned downlink TBF. + +When the mobile station receives an RLC/MAC block addressed to (one of) its TBF(s) on any of the new assigned resources it shall restart timer T3190 for the TBF. If timer T3190 expires, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1). + +### 8.2.3.5 Establishment of uplink TBF + +#### 8.2.3.5.0 General + +The mobile station initiates the packet access procedure by sending the Iu mode Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message on the PACCH and starting timer T3168 for each TBF requested. + +On receipt of an Iu mode Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message, the network may assign radio resources to the mobile station on one or more SBPSCHs by transmitting an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF UPLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE) message on the PACCH, or may reject the request by sending a PACKET ACCESS REJECT message on the PACCH. If the PACKET TIMESLOT RECONFIGURE message is sent, then the message shall contain the UPLINK\_TFI\_ASSIGNMENT field. + +A mobile allocation or reference frequency list, when received in the Frequency Parameters IE, as part of an uplink assignment, replaces the previous parameters and shall be used until a new assignment is received or the mobile station has released all TBFs. + +On receipt of an uplink assignment message the mobile station shall follow the procedure below. On reception of an uplink assignment message the mobile station shall stop timer T3168 for each TBF assigned in the message. + +The mobile station shall, after expiry of the TBF starting time, if present, act upon the uplink assignment. + +The mobile station shall then switch to the assigned uplink SBPSCHs and begin to send RLC data blocks on the assigned SBPSCH(s). The G-RNTI shall not be included in any of the uplink RLC data blocks. + +On receipt of a PACKET ACCESS REJECT message that contains a Reject structure addressed to the mobile station, the mobile station shall stop timer T3168 for each TBF rejected in the PACKET ACCESS REJECT message and indicate a packet access failure to the upper layer. + +If the PACKET ACCESS REJECT message contains a WAIT\_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall start timer T3172 for each TBF rejected with the indicated value (Wait Indication). The mobile station is not allowed to make a new attempt for an uplink TBF establishment in the same cell until all instances of timer T3172 expire, but it may attempt uplink TBF establishment in another cell after successful cell reselection. + +If timer T3168 expires for a TBF, the mobile station shall: + +- if the mobile station has no existing uplink TBF: +- retransmit the Iu mode Channel Request Description information element in the next (EGPRS) PACKET DOWNLINK ACK/NACK message unless the Iu mode Channel Request Description has already been transmitted four times for that TBF in which case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3, 3GPP TS 44.060 sub-clause 8.7.2). + +- if the mobile station has at least one uplink TBF: + - proceed with uplink TBF establishment as defined in sub-clause 8.2.2.1.2. + +If the downlink TBF is released, including expiry of timer T3192, before expiry of timer T3168, the mobile station shall stop timer T3168 for each TBF and perform an abnormal release with access retry (see sub-clause 8.8.3, 3GPP TS 44.060 sub-clause 8.7.2). + +#### 8.2.3.5.1 Abnormal cases + +In the following abnormal cases it is assumed that at least one downlink TBF exists. The subsequent behaviour of the mobile station depends on the type of failure and previous actions. + +- If the information in the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message incorrectly specifies one or more uplink PDCHs, the mobile station shall perform an abnormal release with access retry of the uplink TBF(s) with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments. +- If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message incorrectly specifies one or more uplink and/or downlink PDCHs, the mobile station shall perform an abnormal release with access retry of the uplink TBF(s) with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments. +- If the information in the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message violates the mobile station's multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If the mobile station receives a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for its existing TBFs, the mobile station shall ignore the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message, continue normal operation of the existing TBFs, and reinitiate the establishment of the new uplink TBFs unless the establishment of any of these TBFs has already been attempted four times, in which case, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If a mobile station in MAC-DTM state receives a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If an uplink TBF is not already established and the PACKET TIMESLOT RECONFIGURE message does not include a UPLINK\_TFI\_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If an uplink TBF is not already established and the MULTIPLE TBF TIMESLOT RECONFIGURE message does not assign any uplink TBFs, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message contains assignments such that more than one radio bearer is mapped onto a TBF, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If the MULTIPLE TBF UPLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE message does not specify a Channel Coding scheme for all of the uplink TBFs that it is assigning, then the mobile station shall perform an abnormal release with access retry of the uplink TBFs with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments. +- If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE message assigns the same USF to more than one TBF on the same timeslot, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). +- If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE message specifies a RB Id that is not + +assigned to the mobile station, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). + +- If the PACKET ACCESS REJECT message does not specify a G-RNTI\_extension field in the Iu mode Reject structure for each G-RNTI included in the TLLI / G-RNTI field in the Reject structure, then the mobile station shall ignore the message. +- If the PACKET ACCESS REJECT message includes one or more RB Id fields in the Iu mode Reject structure which were not included by the mobile station in the Iu mode Channel Request Description structure, then the mobile station shall perform abnormal release with access retry (see sub-clause 8.8.3).- If a mobile station in MAC-DTM state receives a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). +- If a failure in the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3). + +### 8.2.3.6 Network initiated abnormal release of downlink TBF + +See 3GPP TS 44.060 sub-clause 8.1.2.8. + +## 8.3 Packet PDCH Release + +See 3GPP TS 44.060 sub-clause 8.2. + +## 8.4 Procedure for measurement report sending in MAC-Shared state + +See 3GPP TS 44.060 sub-clause 8.3. + +## 8.5 Network Controlled cell reselection procedures in MAC-Shared state + +See 3GPP TS 44.060 sub-clause 8.4. + +## 8.6 Measurement Order procedures in MAC-Shared state + +See 3GPP TS 44.060 sub-clause 8.5. + +## 8.7 PACKET CONTROL ACKNOWLEDGEMENT + +See 3GPP TS 44.060 sub-clause 8.6. + +## 8.8 Abnormal cases + +### 8.8.1 General + +See 3GPP TS 44.060 sub-clause 8.7.0. + +### 8.8.2 Abnormal release without retry + +See 3GPP TS 44.060 sub-clause 8.7.1. + +### 8.8.3 Abnormal release with access retry + +The mobile station shall abort all TBFs in progress. The mobile station in MAC-Shared state shall return to MAC-Idle state and initiate the establishment of a new uplink TBF on SBPSCH(s), using the procedures on PCCCH, as defined in sub-clause 7.2. + +The mobile station in MAC-DTM state shall return to MAC-Dedicated state and initiate the establishment of a new uplink TBF on SBPSCH(s) using DTM procedures on SRB2, as defined in 3GPP TS 44.118. + +In case the mobile station fails to establish a new uplink TBF on SBPSCH(s), the mobile station shall report an RLC/MAC failure to upper layers. The DRX mode procedures shall be applied, as specified in sub-clause 5.4.1.8. + +#### 8.8.4 Abnormal release with system information + +See 3GPP TS 44.060 sub-clause 8.7.3. + +#### 8.8.5 Abnormal release of an Uplink TBF with access retry + +The mobile station shall abort the uplink TBF. + +If there are no remaining TBFs on SBPSCHs and the mobile station was in MAC-Shared state, then it shall return to MAC-Idle state and reinitiate the establishment of the uplink TBF on SBPSCH(s) using the procedures on PCCCH, as defined in sub-clause 7.2. In the case that this TBF was not the last remaining TBF on SBPSCHs, the mobile station shall reinitiate the establishment of the TBF on SBPSCHs, using the procedures defined on PACCH, as defined in sub-clauses 8.2.3 and 8.3.3. + +If there are no remaining TBFs on SBPSCHs and the mobile station was in MAC-DTM state, then it shall return to MAC-Dedicated state and initiate the establishment of the uplink TBF on SBPSCH(s) using DTM procedures on SRB2, as defined in 3GPP TS 44.118. In the case that this TBF was not the last remaining TBF on SBPSCHs, the mobile station shall initiate the establishment of the TBF on SBPSCHs, using the procedures defined on PACCH, as defined in sub-clauses 8.2.3 and 8.3.3. + +In case the mobile station fails to establish the new uplink TBF on SBPSCH(s), the mobile station shall report an RLC/MAC failure to upper layers. The DRX mode procedures shall be applied, as specified in sub-clause 5.4.1.8. + +#### 8.8.6 Abnormal release of a Downlink TBF + +The mobile station shall abort the downlink TBF. + +If there are no remaining TBFs on SBPSCHs and the mobile station was in MAC-Shared state, then it shall return to MAC-Idle state. + +If there are no remaining TBFs on SBPSCHs and the mobile station in MAC-DTM state, then it shall return to MAC-Dedicated state. + +If there is a TBF remaining on SBPSCHs, then the mobile station shall remain in its current state. + +The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5, 3GPP TS 44.160 sub-clause 5.4.1.8. + +### 8.9 Network Assisted Cell Change procedures in MAC-Shared state + +See 3GPP TS 44.060 sub-clause 8.8. + +--- + +## 9 Medium Access Control (MAC) procedures on DBPSCH + +### 9.1 General + +The MAC procedures defined in this sub-clause are applicable in MAC-Dedicated state and in MAC-DTM state on DBPSCH only. When a radio bearer is set-up on DBPSCH(s) (see 3GPP TS 44.118) the corresponding TBF is implicitly established, on this DBPSCH(s), on the logical channel (when FLO is not used) on which this TBF is mapped. This TBF shall use the TBF mode as specified in sub-clause 5.2.2.2 and according to the radio bearer attributes as may be indicated in the CMAC-CONFIG primitive received from RRC. + +## 9.2 Transfer of RLC/MAC blocks + +### 9.2.0 General + +Tables 9.2.0.1 to 9.2.0.3 summarise the RLC/MAC control messages that may be sent on a DBPSCH. + +**Table 9.2.0.1: RLC/MAC control messages sent on PACCH or ADCH when mapped on DBPSCH** + +| RLC messages: | Reference | +|----------------------------------------|------------------------------------| +| Packet Downlink Ack/Nack | 3GPP TS 44.060 sub-clause 11.2.6 | +| EGPRS Packet Downlink Ack/Nack | 3GPP TS 44.060 sub-clause 11.2.6a | +| Packet DBPSCH Downlink Ack/Nack Type 2 | 3GPP TS 44.060 sub-clause 11.2.6b | +| Packet Uplink Ack/Nack | 3GPP TS 44.060 sub-clause 11.2.28 | +| Packet DBPSCH Uplink Ack/Nack Type 2 | 3GPP TS 44.060 sub-clause 11.2.28a | +| Miscellaneous messages: | Reference | +| Packet Control Acknowledgement | 3GPP TS 44.060 sub-clause 11.2.2 | +| Packet Downlink Dummy Control Block | 3GPP TS 44.060 sub-clause 11.2.8 | +| Packet Uplink Dummy Control Block | 3GPP TS 44.060 sub-clause 11.2.8b | +| Packet Polling Request | 3GPP TS 44.060 sub-clause 11.2.12 | +| Packet Uplink Assignment | 3GPP TS 44.060 sub-clause 11.2.29 | +| Handover Access | 3GPP TS 44.060 sub-clause 11.2.33 | +| Physical Information | 3GPP TS 44.060 sub-clause 11.2.34 | + +**Table 9.2.0.2: RLC/MAC control messages on SDCCH, SACCH, FACCH (PT="01")** + +| RLC messages: | Reference | +|-------------------------------------|------------------------------------| +| Packet DBPSCH Downlink Ack/Nack | 3GPP TS 44.060 sub-clause 11.2.6b | +| Packet DBPSCH Uplink Ack/Nack | 3GPP TS 44.060 sub-clause 11.2.28a | +| Miscellaneous messages: | Reference | +| Packet Control Acknowledgement | 3GPP TS 44.060 sub-clause 11.2.2 | +| Packet Downlink Dummy Control Block | 3GPP TS 44.060 sub-clause 11.2.8 | +| Packet Uplink Dummy Control Block | 3GPP TS 44.060 sub-clause 11.2.8b | +| Handover Access | 3GPP TS 44.060 sub-clause 11.2.33 | +| Physical Information (not on SACCH) | 3GPP TS 44.060 sub-clause 11.2.34 | + +**Table 9.2.0.3: RLC/MAC control messages on FACCH (PT="10")** + +| RLC messages: | Reference | +|---------------------------------|------------------------------------| +| Packet DBPSCH Downlink Ack/Nack | 3GPP TS 44.060 sub-clause 11.2.6b | +| Packet DBPSCH Uplink Ack/Nack | 3GPP TS 44.060 sub-clause 11.2.28a | +| Miscellaneous messages: | Reference | +| Packet Control Acknowledgement | 3GPP TS 44.060 sub-clause 11.2.2 | + +### 9.2.1 Dedicated allocation + +#### 9.2.1.1 General + +On DBPSCH, the transfer of RLC/MAC blocks is governed by the principles of the dedicated allocation. Dedicated allocation is applicable to GPRS TBF mode, EGPRS TBF mode, TCH TBF mode, DCCH TBF mode, UDCH TBF mode and CDCH TBF mode. No other medium access mode shall apply for TCH TBF mode, DCCH TBF mode, UDCH TBF mode and CDCH TBF mode. + +A mobile station in dedicated allocation shall monitor the assigned DBPSCH(s). The mobile station shall attempt to decode every downlink RLC/MAC block on the assigned DBPSCH(s). Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein and act upon it. + +Except for TCH TBF mode in T-RLC mode, PACKET UPLINK DUMMY CONTROL block(s) (respectively PACKET DOWNLINK DUMMY CONTROL block(s)) shall be sent in periods when no RLC/MAC block is scheduled for + +transmission in uplink direction (respectively downlink direction, following the scheduling requirements defined in 3GPP TS 45.008). For TCH TBF mode and UDCH TBF mode in T-RLC mode, DTX may apply. + +### 9.2.1.2 Performance requirements for TCH and DCCH TBF modes + +When the mobile station receives a DBPSCH assignment, the mobile station shall switch to the assigned DBPSCH(s) and be ready to transmit within the reaction time defined in 3GPP TS 45.010. + +The network (NW) and the mobile station (MS) shall follow the performance requirements defined in the table below. These performance requirements are given on a logical channel and MAC state basis, and define the response time of the network and the mobile station upon receipt of a request from the remote peer entity, where: + +- Trmin and Tresp denote respectively the minimum and maximum response times following the reception of a given request, expressed in TDMA frames, as follows: + - if a polling request is received whose last burst has been physically transmitted in the TDMA frame number FNcomm, then the first burst carrying a segment of the corresponding response shall be physically transmitted in the TDMA frame number FNresp where: + +$$FNcomm + Trmin + 1 \leq FNresp \leq FNcomm + Tresp + 1$$ + +- following the mapping of logical channels onto physical channels and the arithmetics on TDMA frame numbers specified in 3GPP TS 45.002. + +**Table 9.2.1.2.1: Response time** + +| Request sent on | Response sent on | Trmin | Tresp (see note 1) | | +|--------------------------------|--------------------------------|---------------------------------------|-----------------------------------------------------------|-----------------------------------------------------| +| | | | MAC-Dedicated state | MAC-DTM state | +| SDCCH | SDCCH | MS: 11
NW: TRMIN_SDCCH (32 or 83) | MS: 113
NW: TRESP_SDCCH (134 or 185, respectively) | Not applicable | +| SACCH | SACCH | MS: 11
NW: 83 | MS: 11
NW: 83 | | +| SACCH
(with a TCH or PDTCH) | SACCH
(with a TCH or PDTCH) | MS: 25
NW: TRMIN_SACCH (25 or 129) | MS: 129
NW: TRESP_SACCH (129 or 233, respectively) | MS: 25
NW: TRMIN_SACCH | +| FACCH/Full rate | FACCH/Full rate | MS: 9
NW: TRMIN | MS: 18 (max between 18 and 17)
NW: TRESP_MAC_Dedicated | MS: 14 (max between 13 and 14)
NW: TRESP_MAC_DTM | +| TCH/Full rate | FACCH/Full rate | MS: 9
NW: TRMIN | MS: 18 (max between 18 and 17)
NW: TRESP_MAC_Dedicated | MS: 14 (max between 13 and 14)
NW: TRESP_MAC_DTM | +| FACCH/Half rate | FACCH/Half rate | MS: 10
NW: TRMIN | MS: 28 (max between 28 and 27)
NW: TRESP_MAC_Dedicated | MS: 19 (max between 18 and 19)
NW: TRESP_MAC_DTM | + +NOTE 1: these values account for the maximum amount of Radio Bearers multiplexed on a given logical channel, and the priorities of associated RLC/MAC blocks. For FACCH, it also accounts for the RLC/MAC control signalling related to the traffic on the TCH. + +NOTE 2: The combination TCH/H – FACCH/H is not supported. + +NOTE 3: "max between n and m" is to account for the shift of the start of the FACCH block where the response is sent, that occurs depending on the end of the TCH/FACCH block where the request was sent. (due to a different number of idle/SACCH frames included in the counts). + +### 9.2.1.3 Performance requirements for UDCH and CDCH TBF modes + +On a DBPSCH where FLO is used, the network (NW) and the mobile station (MS) shall follow the performance requirements defined in the table below. These performance requirements are given on a transport channel and MAC state basis, and define the response time of the network and the mobile station upon receipt of a request from the remote peer entity, where: + +- Trmin and Tresp denote respectively the minimum and maximum response times following the reception of a given request, expressed in TDMA frames, as follows: + +- if a polling request is received whose last burst has been physically transmitted in the TDMA frame number FNcomm, then the first burst carrying a segment of the corresponding response shall be physically transmitted in the TDMA frame number FNresp where: + +$$FNcomm + Trmin + 1 \leq FNresp \leq FNcomm + Tresp + 1$$ + +- following the mapping of transport channels onto physical channels and the arithmetics on TDMA frame numbers specified in 3GPP TS 45.002. + +**Table 9.2.1.3.1: Response time** + +| Request sent on | Response sent on | Trmin | Tresp (see note 1) | | +|-----------------|------------------|-----------|--------------------------------|--------------------------------| +| | | | MAC-Dedicated state | MAC-DTM state | +| UDCH/Full rate | ADCH/Full rate | MS: 9 | MS: 31 (max between 31 and 30) | MS: 27 (max between 27 and 26) | +| CDCH/Full rate | ADCH/Full rate | NW: | NW: | | +| ADCH/Full rate | ADCH/Full rate | TRMIN_DCH | TRESP_DCH_MAC_Dedicated | NW: TRESP_DCH_MAC_DTM | +| UDCH/Half rate | ADCH/Half rate | MS: 10 | MS: 54 (max between 54 and 53) | MS: 45 (max between 45 and 44) | +| CDCH/Half rate | ADCH/Half rate | NW: | NW: | | +| ADCH/Half rate | ADCH/Half rate | TRMIN_DCH | TRESP_DCH_MAC_Dedicated | NW: TRESP_DCH_MAC_DTM | + +NOTE 1: these values account for the maximum amount of Radio Bearers multiplexed on DBPSCH, and the priorities of associated RLC/MAC blocks. For ADCH, it also accounts for the RLC/MAC control signalling related to TBFs in CDCH or UDCH TBF modes. + +NOTE 2: "max between n and m" is to account for the shift of the start of the FACCH block where the response is sent, that occurs depending on the end of the TCH/FACCH block where the request was sent. (due to a different number of idle/SACCH frames included in the counts). + +NOTE 3: these requirements are valid for both interleaving alternatives i.e. 20ms and 40ms. + +## 9.2.2 Transfer of RLC/MAC blocks on TCH + +One and only one TBF in TCH TBF mode may be mapped onto a TCH. + +No RLC/MAC control blocks shall be sent on TCH. RLC/MAC control blocks belonging to a TBF in TCH TBF mode operating in NT-RLC mode shall be sent on FACCH with Payload Type (PT) = "10". No RLC/MAC control block shall be sent on FACCH if the corresponding TCH is occupied by a TBF operating in T-RLC mode unless this RLC/MAC control block belongs to a TBF in DCCH TBF mode mapped on this FACCH or carries a PHYSICAL INFORMATION message. The HANDOVER ACCESS message shall be sent on FACCH irrespective of the TBF mapped on TCH, following the rules defined in sub-clause 9.2.3. + +An RLC/MAC control block carrying a PHYSICAL INFORMATION message on FACCH shall be sent with Payload Type (PT) = "01". + +RLC/MAC blocks shall be transmitted with the following priority (highest priority first): + +- RLC/MAC blocks on FACCH, except Packet Uplink/Downlink Dummy Control Blocks; +- RLC data blocks on TCH; +- RLC/MAC control blocks on FACCH containing Packet Uplink/Downlink Dummy Control Blocks. + +## 9.2.3 Transfer of RLC/MAC blocks on FACCH, SACCH and SDCCH + +A TBF associated with a URB may operate in DCCH TBF mode but shall not be mapped on SACCH. + +On SACCH, MAC shall ensure the following as long as there is data to send for SRB1, and SRB3 and/or SRB4: + +- every second RLC/MAC block sent on SACCH shall belong to SRB1, and the other to SRB3 or SRB4, and +- every second RLC/MAC block belonging to SRB1 shall be discarded, the other shall be sent on SACCH. + +All RLC data blocks belonging to a TBF in DCCH TBF mode shall be encoded using CS-1. + +The mobile station shall attempt to decode every downlink RLC/MAC block on FACCH, SACCH or SDCCH. Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein, and shall act on it. + +Each RLC data block sent on FACCH, SACCH or SDCCH shall contain a Reduced Radio Bearer identity (RRBid) field corresponding to the radio bearer to which the RLC data block belongs. + +On SDCCH, all the RLC data blocks of an uplink TBF shall each contain a G-RNTI field in the RLC data block header until contention resolution is completed on the mobile station side (see sub-clause 7.2.3.3.2.3). After the reaction time specified in 3GPP TS 45.010 no other RLC data blocks shall contain a G-RNTI field, except for those retransmitted RLC data blocks that originally contained a G-RNTI, which will be repeated including the same G-RNTI. + +RLC/MAC blocks and HANDOVER ACCESS message shall be transmitted with the following priority (highest priority first): + +- HANDOVER ACCESS message +- RLC/MAC control blocks with a Payload Type (PT) = "01" i.e. related to a TBF in DCCH TBF mode or carrying a PHYSICAL INFORMATION message, except Packet Uplink/Downlink Dummy Control blocks; +- RLC data blocks containing a piggy-backed acknowledgement; +- RLC/MAC control blocks with a Payload Type (PT) = "10" i.e. related to a TBF in TCH TBF mode, except Packet Uplink/Downlink Dummy Control blocks; +- RLC data blocks not containing a piggy-backed acknowledgement; +- RLC/MAC control blocks containing Packet Uplink/Downlink Dummy Control Blocks. + +## 9.2.4 Transfer of RLC/MAC blocks on PDTCH and PACCH + +### 9.2.4.1 General + +#### 9.2.4.1.1 Downlink transfer + +##### 9.2.4.1.1.1 General + +RLC/MAC blocks shall be transmitted in the downlink with the following priority (highest priority first): + +- RLC/MAC control blocks except Packet Downlink Dummy Control blocks; +- RLC data blocks; +- RLC/MAC control blocks containing Packet Downlink Dummy Control Blocks. + +If the network has no other RLC/MAC block to transmit, but wishes to transmit on the downlink (e.g. to provide USF), the network shall transmit an RLC/MAC control block containing a Packet Downlink Dummy Control block. + +##### 9.2.4.1.1.2 Polling for Packet Downlink Ack/Nack + +Whenever the mobile station receives an RLC data block addressed to (one of) its TBF(s) with a valid RRB field in the RLC data block header (i.e. is polled), the mobile station may transmit a (EGPRS) PACKET DOWNLINK ACK/NACK message in the uplink radio block specified by the RRB field whatever the BSN value of the received RLC data block, unless another RLC/MAC control message is waiting to be transmitted, in which case the other RLC/MAC control message shall be sent. The mobile station shall transmit an RLC/MAC control message other than a (EGPRS) PACKET DOWNLINK ACK/NACK message at most every second time it is polled for that TBF. Furthermore the mobile station shall not transmit an RLC/MAC control message on this TBF other than a (EGPRS) PACKET DOWNLINK ACK/NACK message if the (EGPRS) PACKET DOWNLINK ACK/NACK message contains a Final Ack Indicator set to '1' and shall not start T3192. The mobile station shall not send a PACKET CONTROL ACKNOWLEDGEMENT message unless otherwise specified (see sub-clause 9.3). The mobile station shall not send the Iu mode channel request description field in the (EGPRS) PACKET DOWNLINK ACK/NACK message. + +In EGPRS TBF mode the mobile station shall react on a poll inside an erroneously received RLC data block for which the header is correctly received. + +Whenever the network receives a valid RLC/MAC control message from the TBF, it shall reset counter N3105. The network shall increment counter N3105 for each radio block allocated to that TBF with the RRB field, for which no RLC/MAC control message is received. If N3105 = N3105max, the network shall start timer T3195. When T3195 expires, the network shall notify a link failure to the RRC layer. + +The PACKET DOWNLINK ACK/NACK message contains a Channel Quality Report (see 3GPP TS 45.008). The optional I\_LEVEL measurement results shall be included in at least every other PACKET DOWNLINK ACK/NACK message. + +The EGPRS PACKET DOWNLINK ACK/NACK message may contain an EGPRS Channel Quality Report (see 3GPP TS 45.008). + +In the case of simultaneous uplink and downlink TBFs, the transmission of the polling response takes precedence over the transmission of allocated uplink radio blocks. + +A mobile station of multislot class 1 to 12 need not respond to the poll if it is not compliant with the mobile station's multislot class (see 3GPP TS 45.002). + +A mobile station of multislot class 13 to 18 shall always respond to the poll. + +#### 9.2.4.1.2 Uplink transfer + +##### 9.2.4.1.2.1 General + +RLC/MAC blocks and HANDOVER ACCESS message shall be transmitted with the following priority (highest priority first): + +- HANDOVER ACCESS message +- RLC/MAC control blocks except Packet Uplink Dummy Control blocks; +- RLC data blocks; +- RLC/MAC control blocks containing Packet Uplink Dummy Control Blocks. + +Uplink TBFs are scheduled with USF. USF is assigned as described in sub-clause 9.2.4.1.2.2. + +Whenever the mobile station detects an assigned USF value on an assigned DBPSCH, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same DBPSCH and, in case there are more DBPSCHs assigned in uplink than in downlink, also on all higher numbered assigned DBPSCHs. The time relation between an uplink block, which the mobile station shall use for transmission, and the occurrence of the USF value is defined in 3GPP TS 45.002. The number of RLC/MAC blocks to transmit is controlled by the USF\_GRANULARITY parameter characterising the uplink TBF. + +When the mobile station transmits an RLC/MAC block to the network, it shall start timer T3180 for the uplink TBF on which the block was sent. When the mobile station detects an assigned USF value on an assigned DBPSCH for the TBF, the mobile station shall restart timer T3180. If timer T3180 expires, the mobile station shall notify a link failure to the RRC layer. + +Whenever the network receives a valid RLC/MAC block from the TBF, it shall reset counter N3101. The network shall increment counter N3101 for each radio block, allocated to that TBF, for which no data is received. If N3101 = N3101max, the network shall stop the scheduling of RLC/MAC blocks from the TBF and start timer T3169. When T3169 expires, the network shall notify a link failure to the RRC layer. + +The mobile station shall attempt to decode every downlink RLC/MAC block on all assigned DBPSCHs. Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein and act on the message. + +Whenever the mobile station detects an assigned USF value on any assigned DBPSCH, the mobile station may transmit a PACCH block on the same DBPSCH in the next block period (see 3GPP TS 45.002). The mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see 3GPP TS 44.060 sub-clause 10.4.4). + +In case there are more DBPSCHs assigned in uplink than in downlink, the network shall transmit all PACCH messages on the DBPSCH carried on the lowest numbered timeslot in the allocation. + +##### 9.2.4.1.2.2 On receipt of a Packet Uplink Assignment message + +The USF of a TBF belonging to a URB is initially assigned by RRC using radio bearer control procedures (see 3GPP TS 44.118). The USF of a TBF belonging to a SRB is assigned by RLC/MAC. + +The network may send a PACKET UPLINK ASSIGNMENT message to the mobile station on the PACCH on DBPSCH addressing a particular TBF on DBPSCH (identified in the Global\_TFI field) in order to: + +- assign a USF to this TBF only in case this TBF does not already have any assigned USF and/or to +- change one or more of the following parameters of this TBF: (EGPRS) channel coding command field, resegment bit, BEP\_PERIOD2 field. All other parameters may only be changed through radio bearer control procedures (see 3GPP TS 44.118) + +The network shall include a valid RRBG field in the RLC/MAC control block header and clear counter N3105. + +In case the mobile station receives a PACKET UPLINK ASSIGNMENT message on PACCH (DBPSCH) addressing a particular uplink TBF on DBPSCH (identified in the Global\_TFI field), the mobile station shall only act on the following fields: + +- USF granularity and USF value per timeslot fields in the message (see 3GPP TS 44.060) if the mobile station does not already have a USF assigned to this TBF, +- starting time (if included), +- (EGPRS) Channel coding command, +- Resegment bit (if included), and +- BEP\_PERIOD2 field (if included) and ignore other fields. + +When the mobile station receives an uplink assignment that does not contain a TBF starting time, the mobile station shall begin to use the newly assigned parameters immediately for this TBF. If a TBF starting time information element is present the mobile station shall wait until the starting time before beginning to use these parameters for this TBF. If while waiting for the frame number indicated by the TBF starting time the mobile station receives another uplink assignment for the same TBF, the mobile station shall act upon the most recently received uplink assignment and shall ignore the previous uplink assignment. + +When the mobile station receives the PACKET UPLINK ASSIGNMENT message, it shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message in the radio block indicated by the RRBG field. + +If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the radio block indicated by the RRBG field, it shall increment counter N3105 and retransmit the PACKET UPLINK ASSIGNMENT message. If counter N3105 exceeds its limit, the network shall stop scheduling new uplink resources for the TBF, stop sending the PACKET UPLINK ASSIGNMENT message to the mobile station and start timer T3195. + +When timer T3195 expires the network shall notify a link failure to the RRC layer. + +#### 9.2.4.1.2.3 Release of the USF + +The network may initiate the release of the USF of a particular TBF by sending a PACKET UPLINK ACK/NACK message with the Final Ack Indicator set to '1'. The network shall include a valid RRBG field in the RLC/MAC control block header and clear counter N3103. The release of the USF, using this procedure, may be initiated at a point determined by the network. + +If the mobile station receives a PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', it shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the radio block indicated by the RRBG field and release the USF. + +When the network receives the PACKET CONTROL ACKNOWLEDGEMENT message in the radio block indicated by the RRBG field, it may reuse the USF resource. + +If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the radio block indicated by the RRBG field, it shall increment counter N3103 and retransmit the PACKET UPLINK ACK/NACK message. If counter N3103 exceeds its limit, the network shall stop scheduling new uplink resources for the TBF, stop sending the PACKET UPLINK ACK/NACK message to the mobile station and start timer T3169. + +When timer T3169 expires the network shall notify a link failure to the RRC layer. + +#### 9.2.4.2 Scheduling an inactive TBF on a DBPSCH + +When a previously inactive TBF (i.e. for which the latest transmitted CV was equal to 0 and for which no USF is assigned) has data to send, the mobile station shall send one RLC data block for this TBF the next time the network schedules any of the mobile station's TBFs using the assigned USFs. This TBF shall be considered inactive until a USF is assigned to it. This RLC data block shall not be sent in a block that has been reserved for sending a RLC/MAC control message via the RRBP field. On sending a RLC data block on a radio block that has been stolen by this mechanism, the mobile station start timer T3194 for the associated radio bearer. The mobile station shall stop timer T3194 on receipt of the USF for this radio bearer (see sub-clause 9.2.4.1.2.2). The mobile station shall be able to steal further blocks from any of its scheduled TBFs, provided that no more than one block is stolen for a particular radio bearer during an interval defined by the duration of timer T3194. On expiry of timer T3194 the mobile station shall restart the timer unless it has expired four times, in which case the mobile station shall notify a link failure to the RRC layer. + +#### 9.2.4.3 Further USF handling + +If the mobile station has more than one active TBF with data to send, the mobile station shall send data for the TBF corresponding to the received USF, with the exception given in sub-clause 9.2.4.2. If the mobile station has no data to send for the scheduled TBF (i.e. no RLC data block or no RLC/MAC control message other than PACKET UPLINK DUMMY CONTROL BLOCK message), and if the MS has data to send for one or more other TBFs mapped onto the same DBPSCH, the mobile station may send data from one of these other TBFs. + +If the mobile station has only one TBF with data to send, the mobile station shall ignore the USF and shall transmit data for this TBF. + +### 9.2.5 Transfer of RLC/MAC blocks on UDCH, CDCH and ADCH + +#### 9.2.5.1 General + +On the DBPSCH(s) where FLO is used, the transfer of RLC/MAC blocks on transport channels shall follow the rules below: + +- RLC/MAC blocks for data transfer belonging to a SRB shall only be sent on CDCH, with Payload Type = '00'; +- RLC/MAC blocks for data transfer belonging to a URB operating in NT-RLC mode shall only be sent on UDCH, with Payload Type = '01'; +- RLC/MAC blocks for data transfer belonging to a URB operating in T-RLC mode shall only be sent on UDCH. No RLC/MAC overhead is used (see sub-clauses 12.8b.1.3 and 12.8b.2.3); +- RLC/MAC blocks for control message transfer shall only be sent on ADCH, with Payload Type = '10'. + +RLC/MAC blocks shall be transmitted with the following priority (highest priority first): + +- HANDOVER ACCESS message; +- RLC/MAC blocks for control message transfer on ADCH, except Packet Uplink/Downlink Dummy Control blocks; +- RLC/MAC blocks for SRB data transfer on CDCH containing a piggy-backed acknowledgement; +- RLC/MAC blocks for SRB data transfer on CDCH not containing a piggy-backed acknowledgement; +- RLC/MAC blocks for URB data transfer on UDCH; +- RLC/MAC blocks for control message transfer on ADCH containing Packet Uplink/Downlink Dummy Control blocks. + +In addition, on DBPSCH/H where FLO is used, the transfer of RLC/MAC blocks on transport channels shall follow the rule below: + +- Every RLC/MAC block for data transfer belonging to a SRB shall be sent twice in a row. The first and second transport blocks used for the RLC/MAC block shall be sent with the signalling TFC. + +- Every RLC/MAC block for control message transfer shall be sent twice in a row. The first and second transport blocks used for the RLC/MAC block shall be sent with the signalling TFC. In case ciphering is used, the RLC/MAC block shall only be ciphered with the parameters used with the first transport block, in both transport blocks. + +The mobile station shall attempt to decode every downlink RLC/MAC block on DBPSCH. Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein, and shall act on it. + +### 9.2.5.2 Transport format combination (TFC) selection + +#### 9.2.5.2.1 General requirements + +On each DBPSCH where FLO is used, the MAC layer shall select a TF for each TrCH within the TFS configured by RRC for each TrCH so that the resulting TFC belongs to the TFCS configured by RRC. + +For RLC/MAC block for data transfer belonging to a TBF in CDCH TBF mode, the MAC layer shall always select the signalling TFC(s) specified in 3GPP TS 44.118. + +For RLC/MAC block for data transfer belonging to a TBF in UDCH TBF mode, the MAC layer shall select a TF within the TFS of the TrCH on which the corresponding radio bearer is mapped. It shall not select a TF that does not belong to this TFS. + +For RLC/MAC block for control message transfer, the MAC layer shall always select the signalling TFC specified in 3GPP TS 44.118. + +#### 9.2.5.2.2 Downlink + +The selection of the TFC in the downlink is left up to network implementation. The network shall follow the requirements defined in sub-clause 9.2.5.2.1. + +#### 9.2.5.2.3 Uplink + +The mobile station shall be notified of the highest allowed TFC in the TFCS, that may be used for uplink transmission. The mobile station shall not select any TFC of which the TFCI is higher than the TFCI of the highest allowed TFC. If no highest allowed TFC is notified to the mobile station, the highest allowed TFC shall be the highest TFC in the TFCS. All the TFCs up to and including the highest allowed TFC are valid TFCs. All other TFCs are invalid. + +Every TTI, the mobile station shall select a valid TFC as follows: + +- No other TFC shall allow the transmission of more highest priority data than the selected TFC +- No other TFC shall allow the transmission of more data from the next lower priority TBF. This shall be applied for each TBF for the remaining priority levels. + +#### 9.2.5.3 Polling for PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 + +Upon receipt by the mobile station of a polling request within an RLC/MAC block for data transfer, the mobile station shall send a PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 message within the next possible uplink occurrence on ADCH, following the requirements defined in sub-clause 9.2.1.3. + +## 9.3 PACKET CONTROL ACKNOWLEDGEMENT + +Upon receipt by the mobile station of a polling request (see sub-clauses 12.7.4 and 12.9.3) within an RLC/MAC control message sent on a given logical channel, the mobile station shall send a corresponding PACKET CONTROL ACKNOWLEDGEMENT message within the next possible uplink occurrence on the same logical channel or ADCH (FLO only). The PACKET CONTROL ACKNOWLEDGEMENT message shall be formatted using the normal burst format. The next possible uplink occurrence is defined following the rules below: + +- If the RLC/MAC control message is received on PACCH with a valid RRBG field as part of this RLC/MAC control message, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified (see 3GPP TS 44.060 sub-clause 10.4.5) +- Otherwise, the mobile station shall send the PACKET CONTROL ACKNOWLEDGEMENT message following the requirements defined in sub-clauses 9.2.1.2 and 9.2.1.3, considering the PACKET CONTROL + +ACKNOWLEDGEMENT message has higher priority than any other RLC/MAC control messages, and any RLC data block. Upon reception by the network of a PACKET CONTROL ACKNOWLEDGEMENT message that does not target a specific RLC entity, within the requirements defined in sub-clauses 9.2.1.2 and 9.2.1.3, the network shall reset counter N3105. If the network does not receive a PACKET CONTROL ACKNOWLEDGEMENT message before the response time specified in sub-clauses 9.2.1.2 and 9.2.1.3, it shall increment counter N3105. If counter N3105=N3105max, the network shall indicate a link failure to the RRC layer. + +## 9.3a Handover Access and Physical Information + +### 9.3a.1 Handover Access + +During a handover, upon trigger from RRC through the HANDOVER-Req primitive, the mobile station shall send a HANDOVER ACCESS message containing the necessary handover reference value (see sub-clause 4.3.4) to the network on either FACCH, PACCH (on DBPSCH), ADCH (FLO only) or SDCCH. While the HANDOVER ACCESS message is being sent on FACCH, PACCH (on DBPSCH), ADCH (FLO only) or SDCCH, the mobile station may send additional HANDOVER ACCESS messages on SACCH. In this case, the HANDOVER ACCESS message may be sent on any TDMA frame block (Bn) belonging to the allocated SACCH (see 3GPP TS 45.002). The mobile station shall not send any HANDOVER ACCESS message on SACCH if no HANDOVER ACCESS message is being sent on FACCH, PACCH, ADCH (FLO only) or SDCCH. + +Upon reception of a HANDOVER ACCESS message by the network, the RRC shall be notified through the HANDOVER-Ind primitive (see sub-clause 4.3.4) and the network shall then proceed as specified in 3GPP TS 44.118. + +In case of non-synchronized cells (see 3GPP TS 44.118), no other RLC/MAC block than those containing the HANDOVER ACCESS message shall be sent by the mobile station while the PHYSICAL INFORMATION message has not been received by this mobile station. + +### 9.3a.2 Physical Information + +During a handover, upon trigger from RRC layer through the PHYSICAL-INFO-Req primitive, the network shall send a PHYSICAL INFORMATION message containing the necessary timing advance value (see sub-clause 4.3.4) to the mobile station, on FACCH, PACCH (on DBPSCH), ADCH (FLO only) or SDCCH. The PHYSICAL INFORMATION message shall be ciphered if applicable i.e. if ciphering is started (see 3GPP TS 44.118). + +Upon reception of a PHYSICAL INFORMATION message, the RRC shall be notified through the PHYSICAL-INFO-Ind primitive and the mobile station shall then proceed as specified in 3GPP TS 44.118. + +## 9.4 Abnormal cases + +- If the mobile station receives an RLC/MAC control message on a logical channel where this RLC/MAC control message is not allowed (see sub-clause 9.2.0), the mobile station shall ignore the message. +- If the mobile station receives an acknowledgement message (PACKET UPLINK ACK/NACK, PACKET DBPSCH UPLINK ACK/NACK, PACKET DBPSCH UPLINK ACK/NACK TYPE 2) with missing mandatory fields, the mobile station shall notify the RRC layer, which shall in turn re-establish all RLC entities for the radio bearers currently established on the DBPSCH(s) and release the DBPSCH(s), as specified in 3GPP TS 44.118. +- If the mobile station receives an acknowledgement message (PACKET UPLINK ACK/NACK, PACKET DBPSCH UPLINK ACK/NACK, PACKET DBPSCH UPLINK ACK/NACK TYPE 2) for a radio bearer that is either not established on the DBPSCH(s) or for which no data has been sent in the direction of the acknowledgement on the DBPSCH(s), the mobile station shall notify the RRC layer, which shall in turn re-establish all RLC entities for the radio bearers currently established on the DBPSCH(s) and release the DBPSCH(s), as specified in 3GPP TS 44.118. + +--- + +## 10 Radio Link Control (RLC) procedures on PDTCH and PACCH + +### 10.1 General + +See 3GPP TS 44.060 sub-clause 9.0. + +### 10.2 Procedures and parameters for peer-to-peer operation + +#### 10.2.1 Send state variable V(S) + +See 3GPP TS 44.060 sub-clause 9.1.1. + +#### 10.2.2 Control send state variable V(CS) + +See 3GPP TS 44.060 sub-clause 9.1.1a. + +#### 10.2.3 Acknowledge state variable V(A) + +See 3GPP TS 44.060 sub-clause 9.1.2. + +#### 10.2.4 Acknowledge state array V(B) + +See 3GPP TS 44.060 sub-clause 9.1.3. + +#### 10.2.5 Block sequence number BSN + +See 3GPP TS 44.060 sub-clause 9.1.4. + +#### 10.2.6 Receive state variable V(R) + +See 3GPP TS 44.060 sub-clause 9.1.5. + +#### 10.2.7 Receive window state variable V(Q) + +See 3GPP TS 44.060 sub-clause 9.1.6. + +#### 10.2.8 Receive state array V(N) + +See 3GPP TS 44.060 sub-clause 9.1.7. + +#### 10.2.9 Starting sequence number (SSN) and received block bitmap (RBB) + +See 3GPP TS 44.060 sub-clause 9.1.8. + +#### 10.2.10 Window Size + +See 3GPP TS 44.060 sub-clause 9.1.9. + +#### 10.2.10a RLC buffer + +See 3GPP TS 44.060 sub-clause 9.1.9.3. + +#### 10.2.11 Compression + +See 3GPP TS 44.060 sub-clause 9.1.10. + +#### 10.2.12 Segmentation of upper layer PDUs into RLC data units + +See 3GPP TS 44.060 sub-clause 9.1.11. + +If so ordered by RRC for a given signalling radio bearer using RLC acknowledged mode, in order to assure duplication avoidance at higher layer, RLC shall guarantee that no more than three upper layer PDUs shall be outstanding in the transmit window at any given time: there may be at most three upper layer PDUs that are being transmitted i.e. that have been segmented and for which the RLC PDUs are being transferred to the receiving end. + +If so ordered by RRC (CRLC-CONFIG-Req primitive), the RLC transmitter may discard: + +- in RLC acknowledged mode, RLC SDU(s) not yet segmented into RLC PDUs. The RLC transmitter shall notify the higher layer of all discarded RLC SDUs, if indicated (RLC-AM-DATA-DiscardReq primitive). +- in RLC unacknowledged mode, RLC SDU(s). + +### 10.2.13 Re-assembly of upper layer PDUs from RLC data units + +See 3GPP TS 44.060 sub-clause 9.1.12. + +### 10.2.14 Segmentation of RLC/MAC control messages into RLC/MAC control blocks + +See 3GPP TS 44.060 sub-clause 9.1.12a. + +### 10.2.15 Re-assembly of RLC/MAC control messages from RLC/MAC control blocks + +RLC/MAC control blocks shall be collected at the receiver until all RLC/MAC control blocks comprising an RLC/MAC control message have been received. + +In MAC-Idle state, the mobile station shall be capable of receiving eight RLC/MAC control messages in parallel. If the mobile station receives RLC/MAC control blocks containing part of a ninth RLC/MAC control message while it still has RLC/MAC control blocks for eight partially received RLC/MAC control messages, the mobile station shall discard the RLC/MAC control block of the oldest partially received message. + +In MAC-Shared state, MAC-Dedicated state or MAC-DTM state, the mobile station shall be capable of receiving sixteen RLC/MAC control messages in parallel. If the mobile station receives RLC/MAC control blocks containing part of a seventeenth RLC/MAC control message while it still has RLC/MAC control blocks for sixteen partially received RLC/MAC control messages, the mobile station shall discard the RLC/MAC control block of the oldest partially received message. + +The mobile station shall start an instance of timer T3200 following the receipt of an RLC/MAC control block whose RTI value does not correspond to the RTI value of a partially received RLC/MAC control message or if the RLC/MAC control blocks were received on different SBPSCHs (respectively DBPSCHs). In non-DRX mode the duration of timer T3200 shall be four BS\_CV\_MAX block periods. In DRX mode the duration of timer T3200 shall be four times the DRX period (see 3GPP TS 43.064). + +On receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message such that the mobile station now has the complete RLC/MAC control message, the mobile station shall stop the corresponding instance of timer T3200. + +If the mobile station discards a partially received RLC/MAC control message while the corresponding instance of timer T3200 is running, the mobile station shall stop the corresponding instance of timer T3200. + +On expiry of an instance of timer T3200, the mobile station shall discard and ignore all segments of the corresponding partially received RLC/MAC control message. + +Upon successful change of SBPSCH (respectively DBPSCH) allocation, the mobile station shall discard all partially received RLC/MAC control messages on SBPSCH (respectively DBPSCH) and stop the corresponding instances of timer T3200. + +The mobile station shall discard any control message segment that contains an unknown TFI. + +## 10.3 Operation during RLC/MAC control message transfer + +See 3GPP TS 44.060 sub-clause 9.2. + +## 10.4 Operation during RLC data block transfer + +### 10.4.1 General + +See 3GPP TS 44.060 sub-clause 9.3.0. + +### 10.4.2 Countdown procedure + +See 3GPP TS 44.060 sub-clause 9.3.1. + +The countdown value that is included in each uplink RLC data block by the mobile station shall correspond to the RLC instance to which the RLC data block belongs. In case SFACCH is used, a TBF shall have a countdown value for each of the RLC instances multiplexed onto the TBF. + +### 10.4.3 Delayed release of downlink Temporary Block Flow + +This procedure is applicable in MAC-Shared state and in MAC-DTM state, on SBPSCH only. See 3GPP TS 44.060 sub-clause 9.3.1a. + +### 10.4.4 Extended uplink TBF mode + +This procedure is applicable in MAC-Shared state and in MAC-DTM state, on SBPSCH only. + +See 3GPP TS 44.060 sub-clause 9.3.1b. + +### 10.4.5 Acknowledged mode operation + +#### 10.4.5.1 General + +See 3GPP TS 44.060 sub-clause 9.3.2.0. + +#### 10.4.5.2 Additional functionality in acknowledged EGPRS TBF Mode + +See 3GPP TS 44.060 sub-clause 9.3.2.1. + +#### 10.4.5.3 Establishment of Temporary Block Flow + +The establishment of a TBF occurs as described in clause 7. RLC functions related to the ARQ function shall not operate until RLC data block transfer has been initiated. + +If for a given radio bearer, the uplink TBF ended with an incompletely transmitted upper layer PDU or any unacknowledged upper layer PDUs, the mobile station shall begin transmission on the new TBF corresponding to this radio bearer with the oldest unacknowledged upper layer PDU. + +#### 10.4.5.4 Operation of uplink Temporary Block Flow + +See 3GPP TS 44.060 sub-clause 9.3.2.3. + +#### 10.4.5.5 Release of uplink Temporary Block Flow + +See 3GPP TS 44.060 sub-clause 9.3.2.4. + +#### 10.4.5.6 Operation of downlink Temporary Block Flow + +See 3GPP TS 44.060 sub-clause 9.3.2.5. + +#### 10.4.5.7 Release of downlink Temporary Block Flow + +See 3GPP TS 44.060 sub-clause 9.3.2.6. + +## 10.4.6 Unacknowledged mode operation + +### 10.4.6.1 General + +See 3GPP TS 44.060 sub-clause 9.3.3.0. + +### 10.4.6.2 Establishment of Temporary Block Flow + +If for a given radio bearer, the uplink TBF ended with an incompletely transmitted upper layer PDU, the mobile station shall begin transmission on the new TBF corresponding to this radio bearer with the last incompletely transmitted upper layer PDU. + +### 10.4.6.3 Operation of uplink Temporary Block Flow + +The network shall send PACKET UPLINK ACK/NACK messages when needed. + +The mobile station shall set the Stall indicator (SI) bit to '0' in all RLC data blocks of the TBF. + +On SBPSCH, if the mobile station transmits the number of RLC data blocks corresponding to the RLC window size (WS), without receiving a Packet Ack/Nack message the mobile station shall start timer T3182 for the TBF. Timer T3182 shall be stopped upon reception of a PACKET UPLINK ACK/NACK message for this TBF. If timer T3182 expires, the mobile station shall decrement counter N3102 by PAN\_DEC, and perform an abnormal release with access retry (see sub-clause 8.7.2). + +On SBPSCH, whenever the mobile station receives a PACKET UPLINK ACK/NACK message, the mobile station shall increment N3102 by PAN\_INC, however N3102 shall never exceed the value PAN\_MAX. Upon cell reselection the mobile station shall set counter N3102 to the value PAN\_MAX. When $N3102 \leq 0$ is reached, the mobile station shall perform an abnormal release with cell re-selection (see sub-clause 9.4.2). If PAN\_DEC, PAN\_INC, or PAN\_MAX are set to the value 0, counter N3102 shall be disabled. + +On SBPSCH, a mobile station operating with an exclusive allocation shall start or restart timer T3184 upon reception of a PACKET UPLINK ACK/NACK message. If timer T3184 expires, the mobile station shall perform an abnormal release with access retry (see sub-clause 9.4.1). + +### 10.4.6.4 Release of uplink Temporary Block Flow + +See 3GPP TS 44.060 sub-clause 9.3.3.3. + +### 10.4.6.5 Operation of downlink Temporary Block Flow + +See 3GPP TS 44.060 sub-clause 9.3.3.4. + +### 10.4.6.6 Release of downlink Temporary Block Flow + +See 3GPP TS 44.060 sub-clause 9.3.3.5. + +## 10.5 Abnormal release cases + +### 10.5.1 Abnormal release with access retry + +Abnormal release with access retry is described in sub-clause 8.8.3. It is applicable in MAC-Shared state and in MAC-DTM state, on SBPSCH only. + +### 10.5.2 Abnormal release with cell reselection + +Abnormal release with cell reselection is applicable in MAC-Shared state only. + +See 3GPP TS 44.060 sub-clause 9.4.2. + +## 10.6 Uplink TBF release in extended uplink TBF mode + +This procedure is applicable in MAC-Shared state and in MAC-DTM state, on SBPSCH only. + +In the extended uplink TBF mode (see sub-clause 10.4.4), the network may initiate the release an uplink TBF by sending a PACKET UPLINK ACK/NACK message with the Final Ack Indicator set to '1'. The network shall include a valid RRBP field in the RLC/MAC control block header and clear counter N3103. The network may use the TBF Est field in the PACKET UPLINK ACK/NACK message to allow the mobile station to request the establishment of new TBF. The release of the uplink TBF, using this procedure, may be initiated at a point determined by the network. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the following conditions are fulfilled: TBF Est field is set to '1'; the mobile station has new data to transmit; the mobile station has no ongoing downlink TBF, the mobile station shall release the TBF and may request the establishment of new TBF using one of the following procedures: + +- If Control Ack Type parameter in System Information indicates acknowledgement is access burst, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message with the Ctrl Ack bits set to '00'. The mobile station shall start timer T3168 and continue to monitor the PDCH used for transmitting the PACKET CONTROL ACKNOWLEDGEMENT message. The mobile station shall stop timer T3168 upon reception of the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.2.4 starting from the point where the mobile station receives the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. +- If Control Ack Type parameter in System Information indicates acknowledgement is RLC/MAC control block, the mobile station shall transmit the PACKET RESOURCE REQUEST message and start timer T3168. The mobile station shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.2.4 starting from the point where the mobile station transmits the PACKET RESOURCE REQUEST message. + +If the PACKET UPLINK ACK/NACK message has the Final Ack Indicator bit set to '1' and the mobile station does not initiate the establishment of a new uplink TBF according to one of the procedures described above, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message and release the TBF. If there is no ongoing downlink TBF, the mobile station in MAC-Shared state shall return to respectively MAC-Idle state; the mobile station in MAC-DTM state shall return to MAC-Dedicated state. The DRX mode procedures shall be applied as specified in sub-clause 5.4.1.8. + +When the network receives the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field, it may reuse the TFI and USF resources. + +If the network receives the PACKET CONTROL ACKNOWLEDGEMENT message with Ctrl Ack bits set to '00' or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field and the network has set the TBF Est field to '1' in the PACKET UPLINK ACK/NACK message, the network shall follow one of the following procedures: + +- In case the mobile station requested the establishment of new TBF with the PACKET CONTROL ACKNOWLEDGEMENT message, the network shall respond to the mobile station with the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message on the same PDCH as the mobile station has sent the PACKET CONTROL ACKNOWLEDGEMENT message. The G-RNTI shall be used to identify the mobile station. The network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.2.4 starting from the point where the network transmits the PACKET UPLINK ASSIGNMENT message including Single Block Allocation structure or the PACKET ACCESS REJECT message. +- In case the mobile station requested the establishment of new TBF with the PACKET RESOURCE REQUEST message, the network shall use the same procedures as are used for TBF establishment using two phase access described in sub-clause 7.2.4 starting from the point where the network has received the PACKET RESOURCE REQUEST message. The G-RNTI shall be used to identify the mobile station. + +If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message or the PACKET RESOURCE REQUEST message in the radio block indicated by the RRBP field, it shall increment counter N3103 and retransmit the PACKET UPLINK ACK/NACK message. If counter N3103 exceeds its limit, the network shall stop scheduling new uplink resources for the TBF, stop sending the PACKET UPLINK ACK/NACK message to the mobile station and start timer T3169. + +When timer T3169 expires, the network may reuse the TFI and USF resources. + +If for a given radio bearer the uplink TBF was operating in RLC acknowledged mode and there is an incompletely transmitted upper layer PDU or an upper layer PDU, which is not fully acknowledged, it shall be transmitted after establishing a new uplink TBF for this radio bearer. + +--- + +## 11 Radio Link Control (RLC) procedures on TCH, FACCH, SACCH, SDCCH and CDCH + +### 11.1 General + +This sub-clause describes the RLC procedures in TCH TBF mode, DCCH TBF mode and CDCH TBF mode applicable in MAC-Dedicated state and MAC-DTM state. Unless explicitly stated otherwise, the procedures and parameters in this sub-clause are not applicable in T-RLC mode. + +In TCH TBF mode, the following definitions apply in NT-RLC mode only: + +- Sequence Number Space (SNS): 256. +- Window Size (WS): 128. + +In DCCH TBF mode and CDCH TBF mode, the following definitions apply: + +- Sequence Number Space (SNS): 16. +- Window Size (WS): 8. + +### 11.2 Procedures and parameters for peer-to-peer operation + +#### 11.2.1 Send state variable V(S) + +See 3GPP TS 44.060 sub-clause 9.1.1. + +#### 11.2.2 Control send state variable V(CS) + +See 3GPP TS 44.060 sub-clause 9.1.1a. + +#### 11.2.3 Acknowledge state variable V(A) + +See 3GPP TS 44.060 sub-clause 9.1.2. + +#### 11.2.4 Acknowledge state array V(B) + +In RLC acknowledged mode, each RLC endpoint transmitter shall have an associated acknowledge state array (V(B)). V(B) is an array of SNS elements indicating the acknowledgement status of WS previous RLC data blocks. The array is indexed relative to the acknowledge state variable V(A) modulo SNS. The values of V(B) shall be updated from the latest values received from its peer in the received block bitmap (RBB) of either the piggy-backed acknowledgement (DCCH TBF mode and CDCH TBF mode only) or the Packet Ack/Nack message (DCCH TBF mode, CDCH TBF mode or TCH TBF mode) (see sub-clause 11.2.10). + +The transmitter shall transmit the oldest RLC data block whose corresponding element in V(B) indexed relative to V(A) has the value NACKED. As each RLC data block is transmitted the corresponding element in V(B) is set to the value PENDING\_ACK. + +If $[ V(S) < V(A) + WS ]$ modulo SNS and no RLC data blocks have a corresponding element in V(B) with the value NACKED, the RLC data block with BSN = V(S) shall be transmitted and the corresponding element in V(B) shall be set to the value PENDING\_ACK. If there are no further RLC data blocks available for transmission (i.e. the RLC data block with BSN = V(S) does not exist), the sending side shall transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING\_ACK, then the next oldest block whose corresponding element in V(B) has the value PENDING\_ACK, etc. If all RLC data blocks whose corresponding element in V(B) has the value PENDING\_ACK have been transmitted once, the process shall be repeated beginning with the oldest RLC data block. + +If $V(S) = V(A) + WS$ modulo SNS (i.e. the transmit window is stalled), the sending side shall transmit the oldest RLC data block whose corresponding element in $V(B)$ has the value PENDING\_ACK, then the next oldest RLC data block whose corresponding element in $V(B)$ has the value PENDING\_ACK, etc. If all RLC data blocks whose corresponding element in $V(B)$ has the value PENDING\_ACK have been transmitted once, the process shall be repeated beginning with the oldest RLC data block. This process of transmitting the oldest RLC data blocks whose value in $V(B)$ has the value PENDING\_ACK shall continue, as long as equation $[V(S)=V(A)+WS]$ modulo SNS holds. + +When an element in $V(B)$ falls outside of the active transmit window, i.e. $[ V(A) \leq BSN < V(S) ]$ modulo SNS, the element shall be set to the value INVALID. + +If $V(S) = V(A)$ and there is no RLC data block with $BSN = V(S)$ available, the mobile station shall stop sending RLC data blocks. The mobile station shall continue sending RLC data blocks when a RLC data block with $BSN = V(S)$ is available. + +## 11.2.5 Block sequence number BSN + +### 11.2.5.1 Block sequence number for TCH TBF mode + +Each RLC data block contains a block sequence number (BSN) field that is 8 bits in length. At the time that an in-sequence RLC data block is designated for transmission, the value of BSN is set equal to the value of the send state variable $V(S)$ . + +### 11.2.5.2 Block sequence number for DCCH TBF mode and CDCH TBF mode + +Each RLC data block contains a block sequence number (BSN) field that is 4 bits in length. At the time that an in-sequence RLC data block is designated for transmission, the value of BSN is set equal to the value of the send state variable $V(S)$ . + +## 11.2.6 Reduced block sequence number RBSN + +See 3GPP TS 44.060 sub-clause 9.1.4a. + +## 11.2.7 Receive state variable $V(R)$ + +See 3GPP TS 44.060 sub-clause 9.1.5. + +## 11.2.8 Receive window state variable $V(Q)$ + +See 3GPP TS 44.060 sub-clause 9.1.6. + +## 11.2.9 Receive state array $V(N)$ + +See 3GPP TS 44.060 sub-clause 9.1.7.1. + +## 11.2.10 Starting sequence number (SSN) and received block bitmap (RBB) + +The Ack/Nack description IE contains a starting sequence number (SSN) and a received block bitmap (RBB). The Ack/Nack description IE is sent by the RLC receiver in a Packet Ack/Nack message (TCH TBF mode, DCCH TBF mode and CDCH TBF mode) or by piggy-backing within RLC data blocks (DCCH TBF mode and CDCH TBF mode) and is received by the RLC transmitter. The SSN and RBB are determined as defined in this sub-clause and transmitted in both RLC acknowledged and RLC unacknowledged mode. The SSN and RBB may be ignored by the RLC transmitter in unacknowledged mode. + +The RBB is defined as a binary valued array of WS elements, where the index of each element takes value 0, 1, 2, ..., WS-1 in the given order, respectively. The BSN values specified in the RBB are interpreted by subtracting the bit position in the bitmap from the starting sequence number (SSN) modulo SNS. + +A valid BSN value in the RBB is one that is in the range $[ V(A) \leq BSN < V(S) ]$ modulo SNS. + +These inequalities shall be interpreted in the following way: + +BSN is valid if, and only if, $[ BSN - V(A) ]$ modulo SNS $< [ V(S) - V(A) ]$ modulo SNS. + +At the RLC transmitter: + +- For each bit in the RBB whose corresponding BSN value is within the transmit window, if the bit contains the value '1', the corresponding element in V(B) indexed relative to SSN shall be set to the value ACKED. If the bit contains the value '0', the element in V(B) shall be set to the value NACKED. A bit within the RBB whose corresponding BSN is not within the transmit window, shall be ignored. If the bit contains the value '0', the last burst of the corresponding RLC data block has been physically transmitted in the TDMA frame number FNcomm, and the first burst carrying a segment of the PACKET DBPSCH UPLINK ACK/NACK or PACKET DBPSCH DOWNLINK ACK/NACK messages or of the piggy-backed acknowledgement has been physically transmitted in the TDMA frame number FNresp where $FNresp < FNcomm + Trmin + 1$ (i.e. the RLC data block was recently (re)transmitted and thus can not be validly negatively acknowledged in this particular acknowledgement), the element in V(B) shall not be modified. See sub-clauses 9.2.1.2 and 9.2.1.3 for the definition of Trmin. + +At the RLC receiver: + +- The starting sequence number (SSN) is assigned the value of the receive state variable V(R). The received block bitmap (RBB) is assigned the WS elements whose indices, with incrementing order, correspond to elements in the receive state array V(N) at the receiver whose indices, with decrementing order, range backwards from $[V(R) - 1]$ to $[V(R) - WS]$ (modulo SNS). For each bit in the bitmap, the bit is assigned the value '1' if the corresponding element in V(N) indexed relative to SSN has the value RECEIVED. The bit is assigned the value '0' if the element in V(N) has the value INVALID. +- When polled within a downlink RLC data block, the mobile station shall acknowledge all the RLC data blocks that have been correctly received up to and including the radio block where the mobile station is polled. +- As an implementation option, the mobile station may also acknowledge as many as possible of the RLC data blocks that are correctly received after the radio block where the mobile station is polled. + +## 11.2.11 Window Size + +### 11.2.11.1 TCH + +For TCH TBF mode, the window size (WS) shall be 128. + +### 11.2.11.2 FACCH, SACCH, SDCCH and CDCH + +For DCCH TBF mode and CDCH TBF mode, the window size (WS) shall be 8. + +### 11.2.11a RLC buffer + +See 3GPP TS 44.060 sub-clause 9.1.9.3. + +## 11.2.12 Segmentation of upper layer PDUs into RLC data units + +See 3GPP TS 44.060 sub-clause 9.1.11. + +Once an RLC data block has been transmitted over the physical link, should it be necessary to re-transmit the RLC data block, it shall be re-transmitted using the same channel coding scheme and BSN as it had in the previous transmission. + +NOTE: The only coding scheme available in DCCH TBF mode is CS-1 coding. + +If so ordered by RRC for a given signalling radio bearer using RLC acknowledged mode, in order to assure duplication avoidance at higher layer, RLC shall guarantee that no more than three upper layer PDUs shall be outstanding in the transmit window at any given time: there may be at most three upper layer PDUs that are being transmitted i.e. that have been segmented and for which the RLC PDUs are being transferred to the receiving end. + +If so ordered by RRC (CRLC-CONFIG-Req primitive), the RLC transmitter may discard: + +- in RLC acknowledged mode, RLC SDU(s) not yet segmented into RLC PDUs. The RLC transmitter shall notify the higher layer of all discarded RLC SDUs, if indicated (RLC-AM-DATA-DiscardReq primitive). +- in RLC unacknowledged mode, RLC SDU(s). + +### 11.2.13 Re-assembly of upper layer PDUs from RLC data units + +See 3GPP TS 44.060 sub-clause 9.1.12. + +### 11.2.14 Segmentation of RLC/MAC control messages into RLC/MAC control blocks + +See 3GPP TS 44.060 sub-clause 9.1.12a. + +### 11.2.15 Re-assembly of RLC/MAC control messages from RLC/MAC control blocks + +See 3GPP TS 44.160 sub-clause 10.2.15: + +The duration of timer T3200 shall be so that, if the last burst of the RLC/MAC control block that triggered the start of timer T3200 has been physically transmitted in the TDMA frame number FNcomm, then the first burst carrying a segment of the RLC/MAC control block that triggered the stop of timer T3200 shall at the latest be physically transmitted in the TDMA frame number FNresp where: + +$$FN_{resp} = FN_{comm} + T_{rmax} + 1, \text{ with } T_{rmax} \text{ defined as shown in the table below}$$ + +**Table 11.2.15.1: Maximum difference between two segments of the same RLC/MAC control message** + +| Logical channel | Trmax | +|--------------------------------|------------------| +| SDCCH | Four TRMIN_SDCCH | +| SACCH | 332 | +| SACCH
(with a TCH or PDTCH) | Four TRMIN_SACCH | +| FACCH/Full rate | Four TRMIN | +| FACCH/Half rate | Four TRMIN | +| ADCH/Full rate | Four TRMIN_DCH | +| ADCH/Half rate | Four TRMIN_DCH | + +## 11.3 Operation during RLC/MAC control message transfer + +RLC/MAC control blocks shall be used to transport RLC/MAC control messages. Segments of only one RLC/MAC control message shall be transported per RLC/MAC control block. + +RLC/MAC control blocks shall be sent at a higher priority than RLC data blocks. + +The receiving side shall determine the length of the RLC/MAC control message contents by interpreting the RLC/MAC control block contents. + +No general acknowledgement shall be made as part of the transfer of RLC/MAC control blocks or RLC/MAC control messages. The receiver shall not acknowledge an RLC/MAC control block except when it is polled by the transmitter as indicated by the polling (P) bit in the MAC header of this RLC/MAC control block. The receiver shall not acknowledge an RLC/MAC control message except when the RLC/MAC procedures explicitly specify an acknowledgement. Upon reception of a polling request, the receiver shall respond following the rules defined in sub-clause 9.2.3 and the requirements defined in sub-clauses 9.2.1.2 and 9.2.1.3. + +A RLC/MAC control block header, may contain a Radio Transaction Identifier (RTI) field that is 2 bits in length and performs in effect a modulo 4 count of the downlink RLC/MAC control messages sent on FACCH or ADCH. The RTI field shall be used to group the RLC/MAC control blocks that make up an RLC/MAC control message. The RTI field allows the transmitting and receiving entities to distinguish between up to 4 RLC/MAC control messages in a single transmit direction therefore allowing up to 4 parallel transactions per FACCH or ADCH. + +The network shall not use the same RTI value at the same time on the same FACCH for two separate RLC/MAC control messages. The network shall transmit both segments of a segmented control message on the same FACCH. When FLO is used on a given DBPSCH, the network shall not use the same RTI value at the same time on this same DBPSCH for two separate RLC/MAC control messages. The network shall transmit both segments of a segmented control message on the same DBPSCH. + +## 11.4 Operation during RLC data block transfer + +### 11.4.1 General + +The RLC ARQ functions are applicable in NT-RLC mode only and support two modes of operation: RLC acknowledged mode and RLC unacknowledged mode. RLC acknowledged mode operation uses retransmission of RLC data blocks to achieve high reliability. RLC unacknowledged mode operation does not utilize retransmission of RLC data blocks. No ARQ function shall apply in T-RLC mode. + +A TBF may operate in either RLC acknowledged mode, RLC unacknowledged mode or RLC transparent mode. + +For a URB, the RLC mode of the corresponding TBF is set to either RLC acknowledged mode, RLC unacknowledged mode or RLC transparent mode at set-up of this particular URB by means of primitive exchange between RRC and RLC (CRLC-CONFIG) (see 3GPP TS 44.118). + +For a SRB, the RLC mode of the corresponding TBF is set implicitly to the proper RLC mode, according to the identity of this particular SRB as follows: + +- SRB1: RLC unacknowledged mode. +- SRB2, SRB3, SRB4: RLC acknowledged mode. + +### 11.4.2 Acknowledged mode operation + +#### 11.4.2.1 General + +The transfer of RLC data blocks in RLC acknowledged mode uses retransmissions of RLC data blocks. The transmitting side numbers the RLC data blocks via the block sequence number (BSN). The BSN is used for retransmission and for reassembly. The receiving side sends acknowledgement in order to request retransmission of RLC data blocks. The operation in RLC acknowledged mode shall be as described in sub-clause 11.2. + +#### 11.4.2.2 On TCH + +##### 11.4.2.2.1 General + +In TCH TBF mode, the transfer of RLC data blocks in RLC acknowledged mode is controlled by a selective type I ARQ mechanism coupled with the numbering of the RLC data blocks. + +##### 11.4.2.2.2 Uplink + +The selection of the proper channel coding scheme (E-TCH/F28.8, E-TCH/F32.0 and E-TCH/F43.2) is controlled by the network and ordered by RRC during radio bearer set-up and reconfiguration procedures (see 3GPP TS 44.118). The RLC/MAC block format used shall be the one corresponding to this channel coding scheme (see sub-clause 12.8). + +The network shall send PACKET DBPSCH UPLINK ACK/NACK messages on FACCH when needed. The mobile station may poll the network for sending a PACKET DBPSCH UPLINK ACK/NACK message by setting the polling (P) bit in an uplink RLC data block. Upon reception by the network of a polling request, the network shall send a PACKET DBPSCH UPLINK ACK/NACK message for the corresponding RLC entity to the mobile station in the next possible downlink radio block on FACCH following the rules described in sub-clause 9.2.3 and the requirements defined in sub-clause 9.2.1.2. Upon reception by the mobile station of a PACKET DBPSCH UPLINK ACK/NACK message for this RLC entity, the mobile station shall reset counter N3106. If the mobile station does not receive any PACKET DBPSCH UPLINK ACK/NACK message for this RLC entity before the response time specified in sub-clause 9.2.1.2, the mobile station shall increment counter N3106. If counter N3106=N3106max, the mobile station shall indicate a link failure to the RRC layer which in turn shall stop the corresponding RLC entity (see sub-clause 14.3 and 3GPP TS 44.118). + +The mobile station shall indicate a transmit window stall condition when $V(S)=V(A) + WS$ . Upon detecting a transmit window stall condition the mobile station shall set the Stall Indicator (SI) bit in all subsequent uplink RLC data block until the stall condition ceases to exist. + +Upon detecting the stall condition the mobile station shall also start timer T3182. Timer T3182 shall be stopped upon reception of a PACKET DBPSCH UPLINK ACK/NACK message that makes $V(S) < V(A) + WS$ . If timer T3182 expires, + +the mobile station shall notify a link failure to the RRC layer which in turn shall stop the corresponding RLC entity (see sub-clause 14.3 and 3GPP TS 44.118). + +#### 11.4.2.2.3 Downlink + +The mobile station receives RLC/MAC blocks for data transfer on TCH. + +The selection of the proper channel coding scheme (E-TCH/F28.8, E-TCH/F32.0 and E-TCH/F43.2) is controlled by the network and ordered by RRC during radio bearer set-up and reconfiguration procedures (see 3GPP TS 44.118). The RLC/MAC block format used shall be the one corresponding to this channel coding scheme (see sub-clause 12.8). The network may poll the mobile station for sending a PACKET DBPSCH DOWNLINK ACK/NACK message by setting the polling (P) bit in a downlink RLC data block. Upon reception by the mobile station of a polling request, the mobile station shall send a PACKET DBPSCH DOWNLINK ACK/NACK message to the network for the corresponding RLC entity in the next possible uplink radio block on FACCH following the rules described in sub-clause 9.2.3 and the requirements defined in sub-clause 9.2.1.2. Upon reception by the network of a PACKET DBPSCH DOWNLINK ACK/NACK message for this RLC entity, the network shall reset counter N3107. If the network does not receive any PACKET DBPSCH DOWNLINK ACK/NACK message for this RLC entity before the response time specified in sub-clause 9.2.1.2, the network shall increment counter N3107. If counter N3107=N3107max, the network shall indicate a link failure to the RRC layer which shall in turn stop the corresponding RLC entity (see sub-clause 14.3 and 3GPP TS 44.118). + +#### 11.4.2.3 On FACCH, SACCH, SDCCH or CDCH + +##### 11.4.2.3.1 General + +In DCCH TBF mode and CDCH TBF mode, the transfer of RLC Data Blocks in RLC acknowledged mode is controlled by a selective type I ARQ mechanism coupled with the numbering of the RLC data blocks. + +##### 11.4.2.3.2 Uplink + +The mobile station shall transmit an RLC/MAC block in each assigned uplink radio block following the rules described in sub-clause 9.2.3. The network shall send acknowledgement when needed. The mobile station may poll the network for sending an acknowledgement by setting the polling (P) bit in an uplink RLC data block. Upon reception by the network of a polling request, the network shall send an acknowledgement (PACKET DBPSCH UPLINK ACK/NACK message, PACKET DBPSCH UPLINK ACK/NACK TYPE 2 message or piggy-backed acknowledgement) to the mobile station for the corresponding RLC entity in the next possible downlink radio block following the rules defined in sub-clause 9.2.3 and the requirements defined in sub-clause 9.2.1.2. Piggy-backing of acknowledgement is possible following the rules below: + +- If on the corresponding logical channel or transport channel an RLC data block is scheduled for transmission in the next radio block: + - if this RLC data block is an initial transmission, the acknowledgement shall be piggy-backed within this RLC data block; + - if this RLC data block is a retransmission of an RLC data block wherein an acknowledgement was initially piggy-backed, the acknowledgement shall be piggy-backed within this retransmitted RLC data block. +- Otherwise a PACKET DBPSCH UPLINK ACK/NACK message or PACKET DBPSCH UPLINK ACK/NACK TYPE 2 message shall be sent. + +Upon reception by the mobile station of an acknowledgement for this RLC entity, the mobile station shall reset counter N3106. If the mobile station does not receive any acknowledgement for this RLC entity before the response time specified in sub-clause 9.2.1.2, the mobile station shall increment counter N3106. If N3106=N3106max, the mobile station shall indicate a link failure to the RRC layer which in turn shall stop the corresponding RLC entity (see sub-clause 14.3 and 3GPP TS 44.118). + +The mobile station shall indicate a transmit window stall condition when $V(S) = V(A) + WS$ . Upon detecting a transmit window stall condition, the mobile station shall set the Stall indicator (SI) bit in all subsequent uplink RLC data block until the stall condition ceases to exist. + +Upon detecting the stall condition the mobile station shall also start timer T3182. Timer T3182 shall be stopped upon reception of a PACKET DBPSCH UPLINK ACK/NACK message or PACKET DBPSCH UPLINK ACK/NACK + +TYPE 2 message that makes $V(S) < V(A) + WS$ . If timer T3182 expires, the mobile station shall notify a link failure to the RRC layer which in turn shall stop the corresponding RLC entity (see sub-clause 14.3 and 3GPP TS 44.118). + +#### 11.4.2.3.3 Downlink + +The mobile station shall be able to receive RLC/MAC blocks in RLC acknowledged mode on FACCH, SACCH and SDCCH. The mobile station shall, in the RLC/MAC header, identify the RRBid and decode the RLC data blocks belonging to the corresponding radio bearer. + +The network may poll the mobile station for sending an acknowledgement by setting the polling (P) bit in a downlink RLC data block. Upon reception by the mobile station of a polling request, the mobile station shall send an acknowledgement (PACKET DBPSCH DOWNLINK ACK/NACK message or PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 message or piggy-backed acknowledgement) for the corresponding RLC entity to the network in the next possible uplink radio block following the rules defined in sub-clause 9.2.3 and the requirements defined in sub-clause 9.2.1.2. Piggy-backing of acknowledgement is possible following the rules below: + +- If on the corresponding logical channel or transport channel an RLC data block is scheduled for transmission in the next radio block: + - if this RLC data block is an initial transmission, the acknowledgement shall be piggy-backed within this RLC data block. + - if this RLC data block is a retransmission of an RLC data block wherein an acknowledgement was initially piggy-backed, the acknowledgement shall be piggy-backed within this retransmitted RLC data block. +- Otherwise a PACKET DBPSCH DOWNLINK ACK/NACK message or PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2 message shall be sent. + +Upon reception by the network of an acknowledgement for this RLC entity, the network shall reset counter N3107. If the network does not receive any acknowledgement for this RLC entity before the response time specified in sub-clauses 9.2.1.2 and 9.2.1.3, the network shall increment counter N3107. If counter N3107=N3107max, the network shall indicate a link failure to the RRC layer which shall in turn stop the corresponding RLC entity (see sub-clause 14.3 and 3GPP TS 44.118). + +### 11.4.3 Unacknowledged mode operation + +#### 11.4.3.1 General + +The transfer of RLC data blocks in RLC unacknowledged mode does not include any retransmissions. The block sequence number (BSN) in the RLC data block header is used to number the RLC data blocks for reassembly. The operation in RLC unacknowledged mode shall be as described in sub-clause 11.2. + +#### 11.4.3.2 On TCH + +##### 11.4.3.2.1 Uplink + +The network shall send acknowledgements when needed. + +The mobile station shall set the Stall Indicator (SI) bit to "0" in all RLC data blocks. + +##### 11.4.3.2.2 (void) + +#### 11.4.3.3 On FACCH, SACCH, SDCCH or CDCH + +##### 11.4.3.3.1 Uplink + +The network shall send acknowledgements when needed. + +The mobile station shall set the Stall indicator (SI) bit to '0' in all RLC data blocks. + +##### 11.4.3.3.2 Downlink + +The mobile station shall be able to receive RLC/MAC blocks in RLC unacknowledged mode on FACCH, SACCH and SDCCH. The mobile station shall, in the RLC/MAC header, identify the RRBid and decode the RLC data blocks belonging to the corresponding radio bearer. + +#### 11.4.4 Transparent mode operation (TCH TBF mode only) + +When operating in transparent mode, the RLC protocol has no functionality. The incoming RLC SDUs are transferred to the MAC layer without being altered. No upper layer protocol information is removed. No RLC protocol information is added. + +--- + +## 11a Radio Link Control (RLC) procedures for FLO on UDCH, ADCH + +### 11a.1 General + +This sub-clause describes the RLC procedures in UDCH TBF mode applicable in MAC-Dedicated state and MAC-DTM state. + +In UDCH TBF mode, the following definitions apply in NT-RLC only: + +RLC acknowledged mode + +- Sequence Number Space (SNS): 1024. +- Window Size (WS): 512. + +RLC unacknowledged mode + +- Sequence Number Space (SNS): 16. +- Window Size (WS): 8. + +### 11a.2 Procedures and parameters for peer-to-peer operation + +#### 11a.2.1 Send state variable V(S) + +See 3GPP TS 44.060 sub-clause 9.1.1. + +#### 11a.2.2 Control send state variable V(CS) + +See 3GPP TS 44.060 sub-clause 9.1.1a. + +#### 11a.2.3 Acknowledge state variable V(A) + +See 3GPP TS 44.060 sub-clause 9.1.2. + +#### 11a.2.4 Acknowledge state array V(B) + +See 3GPP TS 44.060 sub-clause 9.1.3.1. + +#### 11a.2.5 Block sequence number BSN + +Each RLC data block contains a block sequence number (BSN) field that is 10 bits in length in RLC-AM and 4 bits in length in RLC-UM. At the time that an in-sequence RLC data block is designated for transmission, the value of BSN is set equal to the value of the send state variable V(S). + +#### 11a.2.6 Reduced block sequence number RBSN + +See 3GPP TS 44.060 sub-clause 9.1.4a. + +#### 11a.2.7 Receive state variable V(R) + +See 3GPP TS 44.060 sub-clause 9.1.5. + +### 11a.2.8 Receive window state variable V(Q) + +See 3GPP TS 44.060 sub-clause 9.1.6. + +### 11a.2.9 Receive state array V(N) + +See 3GPP TS 44.060 sub-clause 9.1.7.1. + +### 11a.2.10 Starting sequence number (SSN) and received block bitmap (RBB) + +#### 11a.2.10.1 General + +The Packet Ack/Nack message (PACKET DBPSCH UPLINK/DOWNLINK ACK/NACK TYPE 2 message) contains a starting sequence number (SSN) and a reported bitmap. The Packet Ack/Nack message is sent by the RLC receiver and is received by the RLC transmitter. The SSN and reported bitmap are determined as defined in this sub-clause 11a.2.10 and transmitted in RLC acknowledged mode. + +The BSN values specified in the reported bitmap are interpreted by subtracting the bit position in the bitmap to the starting sequence number (SSN), modulo SNS (where the bit in first position in the bitmap has the bit position '1'). + +A valid BSN value in the reported bitmap is one that is in the range $[V(A) \le BSN < V(S)]$ modulo SNS. These inequalities shall be interpreted in the following way: BSN is valid if, and only if, $[BSN - V(A)] \bmod SNS < [V(S) - V(A)] \bmod SNS$ . + +#### 11a.2.10.2 Polling + +Upon reception of polling in uplink (respectively downlink) TBFs, the network (respectively mobile station) may select any composition (first partial bitmap or next partial bitmap) of the Packet Ack/Nack message to send to the mobile station (respectively network). + +#### 11a.2.10.3 Determination of SSN and generation of the reported bitmap + +If the receiving side is the network, the network may select any SSN within the receive window. If the receiving side is the mobile station, SSN shall be determined as follows: let PBSN represent a partial bitmap sequence number variable stored at the receiver which helps to determine the SSN for the next partial bitmap to be transmitted. SSN and PBSN shall be determined as follows. + +First, a Full Received Bitmap (FRB) is built from the receive state array V(N) by extracting the part between V(Q) and V(R) similar to the GPRS case: it is assigned the elements whose indices in the receive state array V(N) at the receiver range from $[V(Q) + 1]$ to $[V(R) - 1]$ (modulo SNS). For each bit in the bitmap, the bit is assigned the value '1' if the corresponding element in V(N) indexed relative to SSN has the value RECEIVED. The bit is assigned the value '0' if the element in V(N) has the value INVALID. + +![Figure 11a.2.10.3.1: Representation of bitmaps and variables. The diagram illustrates the relationship between state variables and bitmaps. At the top, a horizontal axis represents the receive state array. It starts with V(Q) at position 0, followed by several segments labeled '0/1', a break indicated by '//', and ending with '0/1' and '1' at V(R). A double-headed arrow spanning from V(Q) to V(R) is labeled 'FRB'. Below this, a box labeled 'First Partial Bitmap' extends from V(Q) to a vertical line marked 'SSN'. Further down, a box labeled 'Next Partial Bitmap' starts at a point marked 'PBSN' and extends to a vertical line also marked 'SSN'.](b47f393ea2c781f313367435c7166abb_img.jpg) + +Figure 11a.2.10.3.1: Representation of bitmaps and variables. The diagram illustrates the relationship between state variables and bitmaps. At the top, a horizontal axis represents the receive state array. It starts with V(Q) at position 0, followed by several segments labeled '0/1', a break indicated by '//', and ending with '0/1' and '1' at V(R). A double-headed arrow spanning from V(Q) to V(R) is labeled 'FRB'. Below this, a box labeled 'First Partial Bitmap' extends from V(Q) to a vertical line marked 'SSN'. Further down, a box labeled 'Next Partial Bitmap' starts at a point marked 'PBSN' and extends to a vertical line also marked 'SSN'. + +**Figure 11a.2.10.3.1: Representation of bitmaps and variables** + +From the FRB, a reported bitmap shall be generated. The FRB shall be recalculated before each reported bitmap is generated. For uplink TBFs, the network may transmit any reported bitmap size to the mobile station. For downlink TBFs, the mobile station shall follow the rules given in this sub-clause 11a.2.10.3. The reported bitmap is either uncompressed or compressed. + +If the compressed reported bitmap covers more RLC data blocks than the uncompressed reported bitmap, the receiver shall send the compressed reported bitmap, otherwise the receiver shall send the uncompressed reported bitmap. If FRB can be reported uncompressed, the receiver shall send the uncompressed reported bitmap without attempting compression (see below). The compression algorithm is defined in 3GPP TS 44.060 sub-clause 9.1.10. + +Let N be the maximum possible size in bits of the uncompressed reported bitmap in the acknowledgement message when no compressed bitmap is included. + +If $[V(R)-V(Q)] \bmod \text{SNS} \leq N$ (i.e. FRB can be reported uncompressed), then $\text{SSN}=V(R)$ and the reported bitmap covers N RLC data blocks (with a BSN smaller than SSN). PBSN shall then be set to $V(Q)$ . The reported bitmap shall be uncompressed. The bits corresponding to RLC data blocks that may fall outside the FRB shall be set to '1', except for $V(Q)$ which shall be set to '0'. + +If $[V(R) - V(Q)] \bmod \text{SNS} > N$ (i.e. FRB cannot be reported uncompressed), the mobile station shall determine whether a first partial bitmap or a next partial bitmap is transmitted, as follows: + +- If $[\text{PBSN}-V(Q)] \bmod \text{SNS} < \text{WS}$ and if $[V(R) - (\text{PBSN} + \text{PBSN\_Threshold})] \bmod \text{SNS} < \text{WS}$ , then a next partial bitmap is sent. +- Otherwise a first partial bitmap is sent. + +NOTE: The PBSN\_Threshold value intends at identifying a limit for the difference between PBSN and $V(R)$ beyond which a next partial bitmap is generated. Its value is MS implementation dependent. + +If a first partial bitmap is determined, then SSN shall be set to the last sequence number + 1 ( $\bmod \text{SNS}$ ) for which the Ack/Nack status can be indicated in the reported bitmap. The reported bitmap covers the RLC data blocks having a BSN within the interval $[V(Q), \text{SSN}]$ . PBSN shall then be set to the last sequence number for which the Ack/Nack status can be indicated in the reported bitmap i.e. $\text{SSN}-1$ . + +NOTE: The first partial bitmap may cover the entire FRB when compression is used + +If a next partial bitmap is determined, then + +- If $[V(R) - (\text{PBSN} + 1)] \bmod \text{SNS} > N$ then SSN shall be set to the last sequence number + 1 ( $\bmod \text{SNS}$ ) for which the Ack/Nack status can be indicated in the reported bitmap and the reported bitmap covers the RLC data blocks having a BSN within the interval $[\text{PBSN}+1, \text{SSN}-1]$ . PBSN shall then be set to the last sequence number for which the Ack/Nack status can be indicated in the reported bitmap i.e. $\text{SSN}-1$ . +- If $[V(R) - (\text{PBSN}+1)] \bmod \text{SNS} \leq N$ , then $\text{SSN} = V(R)$ and the reported bitmap covers as many RLC data blocks having a BSN smaller than the SSN as can fit in the reported bitmap. PBSN shall then be set to $V(Q)$ . + +NOTE: The next partial bitmap may cover the entire FRB when compression is used + +The beginning of window (BOW) bit shall be set to '0' when the reported bitmap does not cover $V(Q)$ , and to '1' otherwise. The end of window (EOW) bit shall be set to '0' when the reported bitmap does not cover $[V(R)-1]$ , and to '1' otherwise. + +If $V(Q)$ equals $V(R)$ , then SSN shall be set to the value $\text{SSN} = V(R)$ , BOW bit shall be set to the value '1', EOW shall be set to the value '1' and the reported bitmap size shall equal 0 bits. + +#### 11a.2.10.4 Interpretation of the bitmap + +If a compressed bitmap is received, the bitmap shall first be decompressed according to the one-dimensional run length coding algorithm specified in 3GPP TS 44.060 sub-clause 9.1.10. The uncompressed bitmap shall be treated as follows: + +The first bit in the uncompressed bitmap corresponds to the block $\text{SSN}-1 \bmod \text{SNS}$ . The second bit in the uncompressed bitmap corresponds to the block $\text{SSN}-2 \bmod \text{SNS}$ , and so on. + +If the BOW bit in the Packet Ack/Nack message has the value '1', then the bitmap acknowledges all blocks between $V(A)$ and the block corresponding to $V(Q)-1$ (the block corresponding to $V(Q)$ corresponds to the first '0' starting from the end of the bitmap), and the corresponding elements in $V(B)$ shall be set to the value ACKED. + +If the EOW bit in the Packet Ack/Nack message has the value '1', then bitmap value '0' shall be assumed for all RLC blocks with a BSN value higher than the last entry in the bitmap but less than $V(S)$ (i.e. $[V(R) - 1 < \text{BSN} < V(S)] \bmod \text{SNS}$ ). + +For each bit in the uncompressed bitmap whose corresponding BSN value is within the transmit window, if the bit contains the value '1', the corresponding element in $V(B)$ indexed relative to SSN shall be set to the value ACKED. If the bit contains the value '0', the element in $V(B)$ shall be set to the value NACKED. A bit within the uncompressed bitmap whose corresponding BSN is not within the transmit window, shall be ignored. If the bit contains the value '0', + +the last burst of the corresponding RLC data block has been physically transmitted in the TDMA frame number FNcomm, and the first burst carrying a segment of the Packet Ack/Nack message has been physically transmitted in the TDMA frame number FNresp where $FNresp < FNcomm + Trmin + 1$ (i.e. the RLC data block was recently (re)transmitted and thus can not be validly negatively acknowledged in this particular acknowledgement), the element in V(B) shall not be modified. See sub-clause 9.2.1.3 for the definition of Trmin. + +### 11a.2.11 Window Size + +The window size (WS) shall be 512 in RLC acknowledged mode. + +The window size (WS) shall be 8 in RLC unacknowledged mode. + +### 11a.2.11a RLC buffer + +See 3GPP TS 44.060 sub-clause 9.1.9.3. + +### 11a.2.12 Segmentation of upper layer PDUs into RLC data units + +See 3GPP TS 44.060 sub-clause 9.1.11. + +Once an RLC data block has been transmitted over the physical link, should it be necessary to re-transmit the RLC data block, it shall be re-transmitted using the same payload and BSN as it had in the previous transmission. + +If so ordered by RRC (CRLC-CONFIG-Req primitive), the RLC transmitter may discard: + +- in RLC acknowledged mode, RLC SDU(s) not yet segmented into RLC PDUs. The RLC transmitter shall notify the higher layer of all discarded RLC SDUs, if indicated (RLC-AM-DATA-DiscardReq primitive). +- in RLC unacknowledged mode, RLC SDU(s). + +### 11a.2.13 Re-assembly of upper layer PDUs from RLC data units + +See 3GPP TS 44.060 sub-clause 9.1.12. + +### 11a.2.14 Segmentation of RLC/MAC control messages into RLC/MAC control blocks + +See 3GPP TS 44.060 sub-clause 9.1.12a. + +### 11a.2.15 Re-assembly of RLC/MAC control messages from RLC/MAC control blocks + +See 3GPP TS 44.160 sub-clause 10.2.15: + +The duration of timer T3200 shall be so that, if the last burst of the RLC/MAC control block that triggered the start of timer T3200 has been physically transmitted in the TDMA frame number FNcomm, then the first burst carrying a segment of the RLC/MAC control block that triggered the stop of timer T3200 shall at the latest be physically transmitted in the TDMA frame number FNresp where: + +$FNresp = FNcomm + Trmax + 1$ , with Trmax defined as shown in the table below + +**Table 11.2.15.1: Maximum difference between two segments of the same RLC/MAC control message** + +| Logical channel | Trmax | +|--------------------------------|------------------| +| SDCCH | Four TRMIN_SDCCH | +| SACCH | 332 | +| SACCH
(with a TCH or PDTCH) | Four TRMIN_SACCH | +| FACCH/Full rate | Four TRMIN | +| FACCH/Half rate | Four TRMIN | +| ADCH/Full rate | Four TRMIN_DCH | +| ADCH/Half rate | Four TRMIN_DCH | + +## 11a.3 Operation during RLC/MAC control message transfer + +RLC/MAC control blocks shall be used to transport RLC/MAC control messages. Segments of only one RLC/MAC control message shall be transported per RLC/MAC control block. + +RLC/MAC control blocks shall be sent at a higher priority than RLC data blocks. + +RLC/MAC control blocks shall be sent on ADCH. + +The receiving side shall determine the length of the RLC/MAC control message contents by interpreting the RLC/MAC control block contents. + +No general acknowledgement shall be made as part of the transfer of RLC/MAC control blocks or RLC/MAC control messages. The receiver shall not acknowledge an RLC/MAC control block except when it is polled by the transmitter as indicated by the polling (P) bit in the MAC header of this RLC/MAC control block. The receiver shall not acknowledge an RLC/MAC control message except when the RLC/MAC procedures explicitly specify an acknowledgement. Upon reception of a polling request, the receiver shall respond following the rules defined in sub-clause 9.2.3 and the requirements defined in sub-clauses 9.2.1.2 and 9.2.1.3. + +A RLC/MAC control block header, may contain a Radio Transaction Identifier (RTI) field that is 2 bits in length and performs in effect a modulo 4 count of the downlink RLC/MAC control messages sent on ADCH. The RTI field shall be used to group the RLC/MAC control blocks that make up an RLC/MAC control message. The RTI field allows the transmitting and receiving entities to distinguish between up to 4 RLC/MAC control messages in a single transmit direction therefore allowing up to 4 parallel transactions per ADCH. + +The network shall not use the same RTI value at the same time on the same DBPSCH for two separate RLC/MAC control messages. The network shall transmit both segments of a segmented control message on the same DBPSCH. + +## 11a.4 Operation during RLC data block transfer + +### 11a.4.1 General + +The RLC ARQ functions are applicable in NT-RLC mode only and support two modes of operation: RLC acknowledged mode and RLC unacknowledged mode. RLC acknowledged mode operation uses retransmission of RLC data blocks to achieve high reliability. RLC unacknowledged mode operation does not utilize retransmission of RLC data blocks. No ARQ function shall apply in T-RLC mode. + +A TBF may operate in either RLC acknowledged mode, RLC unacknowledged mode or RLC transparent mode. + +For a URB, the RLC mode of the corresponding TBF is set to either RLC acknowledged mode, RLC unacknowledged mode or RLC transparent mode at set-up of this particular URB by means of primitive exchange between RRC and RLC (CRLC-CONFIG) (see 3GPP TS 44.118). + +### 11a.4.2 Acknowledged mode operation + +#### 11a.4.2.1 General + +The transfer of RLC data blocks in RLC acknowledged mode uses retransmissions of RLC data blocks. The transmitting side numbers the RLC data blocks via the block sequence number (BSN). The BSN is used for retransmission and for reassembly. The receiving side sends acknowledgement in order to request retransmission of RLC data blocks. The operation in RLC acknowledged mode shall be as described in sub-clause 11.2. + +The transfer of RLC data blocks in RLC acknowledged mode is controlled by a selective type I ARQ mechanism coupled with the numbering of the RLC data blocks. + +#### 11a.4.2.2 Uplink + +The selection of the transport format set is under control of the network and ordered by RRC during radio bearer set-up and reconfiguration procedures (see 3GPP TS 44.118). + +The network shall send PACKET DBPSCH UPLINK ACK/NACK TYPE 2 messages on ADCH when needed. The mobile station may poll the network for sending a PACKET DBPSCH UPLINK ACK/NACK TYPE 2 message by setting the polling (P) bit in an uplink RLC data block. Upon reception by the network of a polling request, the network + +shall send a PACKET DBPSCH UPLINK ACK/NACK TYPE 2 message for the corresponding RLC entity to the mobile station in the next possible downlink occurrence following the rules described in sub-clause 9.2.3 and the requirements defined in sub-clauses 9.2.1.2 and 9.2.1.3. Upon reception by the mobile station of a PACKET DBPSCH UPLINK ACK/NACK TYPE 2 message for this RLC entity, the mobile station shall reset counter N3106. If the mobile station does not receive any PACKET DBPSCH UPLINK ACK/NACK TYPE 2 message for this RLC entity before the response time specified in sub-clause 9.2.1.2, the mobile station shall increment counter N3106. If counter N3106=N3106max, the mobile station shall indicate a link failure to the RRC layer which in turn shall stop the corresponding RLC entity (see sub-clause 14.3 and 3GPP TS 44.118). + +The mobile station shall indicate a transmit window stall condition when $V(S)=V(A) + WS$ . Upon detecting a transmit window stall condition the mobile station shall set the Stall Indicator (SI) bit in all subsequent uplink RLC data block until the stall condition ceases to exist. + +Upon detecting the stall condition the mobile station shall also start timer T3182. Timer T3182 shall be stopped upon reception of a PACKET DBPSCH UPLINK ACK/NACK TYPE 2 message that makes $V(S)(184 bits - 23 octets) | | | | | | | | 1 | +| . | | | | | | | | . | +| . | | | | | | | | 23 | + +**Figure 12.7.1.1: FACCH/SDCCH/CDCH block** + +| Bit | | | | | | | | Octet | +|--------------------------------------------|---|---|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Physical Layer header (see 3GPP TS 44.003) | | | | | | | | 1 | +| | | | | | | | | 2 | +| RLC/MAC block
(168 bits - 21 octets) | | | | | | | | 3 | +| | | | | | | | | ... | +| | | | | | | | | 23 | + +**Figure 12.7.1.2: SACCH block** + +## 12.7.2 Downlink RLC/MAC block for data transfer + +| Bit | | | | | | | | Octet | | | | | | | +|-------------------------|----|---|-------|---|---|-----|---|------------------------|--|--|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | +| PT | P | | RRBid | | | BSN | | 1 | | | | | | | +| BSN | AI | | spare | | | E | | ... | | | | | | | +| Length Indicator | | | | M | | E | | Extension | | | | | | | +| Length Indicator | | | | M | | E | | Optional
(2 octets) | | | | | | | +| Ack/Nack Description | | | | | | | | ... | | | | | | | +| RLC Data (byte aligned) | | | | | | | | 21(see note)/23 | | | | | | | + +NOTE: 21 octets apply only in case of SACCH. + +**Figure 12.7.2.1: Downlink RLC/MAC block for data transfer on FACCH, SACCH, SDCCH and CDCH (PT=00)** + +## 12.7.3 Uplink RLC/MAC block for data transfer + +| Bit | | | | | | | | Octet | | | | | | | +|-------------------------|----|---|-------|----|-------|-----|---|------------------------|--|--|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | +| PT | P | | RRBid | | | BSN | | 1 | | | | | | | +| BSN | AI | | SI | GI | spare | | E | ... | | | | | | | +| Length Indicator | | | | M | | E | | Extension | | | | | | | +| Length Indicator | | | | M | | E | | Optional
(2 octets) | | | | | | | +| Ack/Nack Description | | | | | | | | Optional
(4 octets) | | | | | | | +| G-RNTI | | | | | | | | ... | | | | | | | +| RLC Data (byte aligned) | | | | | | | | 21(see note)/23 | | | | | | | + +NOTE: 21 octets apply only in case of SACCH. + +**Figure 12.7.3.1: Uplink RLC/MAC block for data transfer on FACCH, SACCH, SDCCH and CDCH (PT=00)** + +## 12.7.4 RLC/MAC block for control message transfer + +The RLC/MAC block formats for control message transfer are applicable in both uplink and downlink directions. + +Figure 12.7.4.1 represents the RLC/MAC block for control message transfer related to an on-going temporary block flow on FACCH, SACCH or SDCCH. + +| Bit | | | | | | | | Octet | +|-------------------------|---|---|-------|---|---|-------|---|------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| PT | P | | RRBid | | | spare | | 1 | +| Control Message Content | | | | | | | | 21 (see note)/23 | + +NOTE: 21 octets apply only in case of SACCH. + +**Figure 12.7.4.1: RLC/MAC block for control message transfer on FACCH, SACCH and SDCCH (PT=01)** + +Figure 12.7.4.2 represents the RLC/MAC block for control message transfer on FACCH related to an on-going temporary block flow on TCH. This message may be used for e.g. acknowledgement of the data transfer on TCH. + +![](a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg) + +| Bit | | | | | | | | Octet | +|-------------------------|---|---|---|------|---|-----|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| PT | | P | S | RBSN | | RTI | spare | 1 | +| Control Message Content | | | | | | | | ... | +| | | | | | | | | 23 | + +**Figure 12.7.4.2: RLC/MAC block for control message transfer on FACCH (PT=10)** + +## 12.8 RLC/MAC block format on TCH (NT-RLC) + +### 12.8.1 RLC/MAC block + +#### 12.8.1.1 General + +Each TCH block shall contain an RLC/MAC block followed by a 24-bit frame check sequence (FCS), as illustrated in figures 12.8.1.1.1, 12.8.1.1.2 and 12.8.1.1.3. + +![](f502d41e990d86acbbd785962f2af138_img.jpg) + +| | | +|---------------|---------| +| RLC/MAC block | FCS | +| 556 bits | 24 bits | + +**Figure 12.8.1.1.1: E-TCH/F28.8 block structure** + +![](c09b8a811aa8d56401cfa959cf953640_img.jpg) + +| | | +|---------------|---------| +| RLC/MAC block | FCS | +| 616 bits | 24 bits | + +**Figure 12.8.1.1.2: E-TCH/F32.0 block structure** + +![](e85b1c059513af5ec342d3f0caffc034_img.jpg) + +| | | +|---------------|---------| +| RLC/MAC block | FCS | +| 846 bits | 24 bits | + +**Figure 12.8.1.1.3: E-TCH/F43.2 block structure** + +#### 12.8.1.2 RLC/MAC block for E-TCH/F28.8 coding scheme + +Figure 12.8.1.2.1 represents the RLC/MAC block for E-TCH/F28.8 coding scheme. + +![](f05fd39478edccadc1227955d092e28b_img.jpg) + +| Bit | | | | | | | | Octet | +|--------------------------|---|---|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| RLC/MAC block (556 bits) | | | | | | | | 1 | +| | | | | | | | | ... | +| | | | | | | | | 69 | +| | | | | | | | | N=70 | + +**Figure 12.8.1.2.1: RLC/MAC block for E-TCH/F28.8** + +#### 12.8.1.3 RLC/MAC block for E-TCH/F32.0 coding scheme + +Figure 12.8.1.3.1 represents the RLC/MAC block for E-TCH/F32.0 coding scheme. + +![](1e3d887bf7a660e3cb6374a0d2d6bf6b_img.jpg) + +| Bit | | | | | | | | Octet | +|--------------------------|---|---|---|---|---|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| RLC/MAC block (616 bits) | | | | | | | | 1 | +| | | | | | | | | ... | +| | | | | | | | | N=77 | + +**Figure 12.8.1.3.1: RLC/MAC block for E-TCH/F32.0** + +### 12.8.1.4 RLC/MAC block for E-TCH/F43.2 coding scheme + +Figure 12.8.1.4.1 represents the RLC/MAC block for E-TCH/F43.2 coding scheme. + +![](796d2e601722450d6456085e0a801e1e_img.jpg) + +| 8 | 7 | 6 | 5 | Bit
4 | 3 | 2 | 1 | Octet | +|-----------------------------|---|---|---|----------|---|---|---|-------| +| RLC/MAC block
(846 bits) | | | | | | | | 1 | +| | | | | | | | | ... | +| | | | | | | | | 105 | +| | | | | | | | | N=106 | + +Figure 12.8.1.4.1: RLC/MAC block for E-TCH/F43.2 + +### 12.8.2 Downlink RLC/MAC block for data transfer + +Figure 12.8.2.1 represents the RLC/MAC block for data transfer for E-TCH/F28.8, E-TCH/F32.0 and E-TCH/F43.2 coding schemes, achieving bit rates of 27,8 kbits/s, 30,8 kbits/s and 42,3 kbits/s respectively. + +![](2f2911db53fbb1b2624f83a51555eb81_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | +|------------------|---|---|---|---|---|---|---|--------------| +| BSN | | | | | | | | 1 | +| spare | | | | | | P | E | 2 | +| Length indicator | | | | | | | E | 3 (optional) | +| ... | | | | | | | | optional | +| Length indicator | | | | | | | E | M (optional) | +| RLC data | | | | | | | | M+1 | +| | | | | | | | | N | + +Figure 12.8.2.1: Downlink RLC/MAC block for data transfer on TCH + +### 12.8.3 Uplink RLC/MAC block for data transfer + +Figure 12.8.3.1 represents the RLC/MAC block for data transfer for E-TCH/F28.8, E-TCH/F32.0 and E-TCH/F43.2 coding schemes, achieving bit rates of 27,8 kbits/s, 30,8 kbits/s and 42,3 kbits/s respectively. + +![](4e8d58baf485af1a077dbfc627a665a9_img.jpg) + +| 8 | 7 | 6 | 5 | Bit
4 | 3 | 2 | 1 | Octet | +|------------------|-------|---|---|----------|---|---|---|--------------| +| BSN | | | | | | | | 1 | +| SI | spare | | | | | P | E | 2 | +| Length indicator | | | | | | | E | 3 (optional) | +| ... | | | | | | | | optional | +| Length indicator | | | | | | | E | M (optional) | +| RLC data | | | | | | | | M+1 | +| | | | | | | | | N | + +Figure 12.8.3.1: Uplink RLC/MAC block for data transfer on TCH + +### 12.8.4 RLC/MAC block for control message transfer + +RLC/MAC blocks for control message transfer shall be sent on FACCH with Payload Type = "10" as described in sub-clause 12.7.4. + +## 12.8a RLC/MAC block for control message transfer on ADCH + +### 12.8a.1 Downlink RLC/MAC control block format + +![](e60c2d24a97a2855d98671d27ea43d0f_img.jpg) + +| Bit | | | | | | | | | +|-------------------------|---|---|---|------|-----|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| PT | | P | S | RBSN | RTI | | | Octet 1 | +| Control message content | | | | | | | | Octet 2 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet N=23 | + +Figure 12.8a.1.1: Downlink RLC/MAC control block together with its MAC header (PT=10) + +### 12.8a.2 Uplink RLC/MAC control block format + +![](986e77e2df3c318680a569774888f4aa_img.jpg) + +| Bit | | | | | | | | | +|-------------------------|---|---|---|---|---|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| PT | | P | | | | | | Octet 1 | +| Control message content | | | | | | | | Octet 2 | +| | | | | | | | | . | +| | | | | | | | | . | +| | | | | | | | | Octet N=23 | + +Figure 12.8a.2.1: Uplink RLC/MAC control block together with its MAC header (PT=10) + +## 12.8b RLC/MAC blocks for URB data transfer on UDCH + +### 12.8b.1 Downlink RLC/MAC block for data transfer + +#### 12.8b.1.1 RLC unacknowledged mode + +![](58e07d355a649f1fbd8a041b88207829_img.jpg) + +| Bit | | | | | | | | | | +|------------------|---|--------------|---|------------------|-----|----|---|--------------------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| PT | | TFI (=RB Id) | | | | | P | Octet 1 | | +| BSN | | | E | Length Indicator | | | | Octet 2 | | +| Length Indicator | | | E | | ... | | | Octet 3 | | +| ... | | | | | E | LI | | | | +| Length Indicator | | | | | | | E | | Octet M | +| RLC data | | | | | | | | Octet M + 1 | | +| | | | | | | | | . | | +| | | | | | | | | . | | +| | | | | | | | | Octet N (see note) | | + +NOTE: the RLC data may contain a non-integer number of octets. + +Figure 12.8b.1.1.1: Downlink RLC/MAC block for data transfer in RLC unacknowledged mode (PT=01) + +### 12.8b.1.2 RLC acknowledged mode + +![](d197b6ded14ea918198a280ff07122b8_img.jpg) + +| Bit | | | | | | | | | | | +|------------------|---|--------------|---|---|---|------------------|---|----|---------|--------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| PT | | TFI (=RB Id) | | | | | P | | Octet 1 | | +| BSN | | | | | | | | | Octet 2 | | +| BSN | | SPB | | E | | Length Indicator | | | Octet 3 | | +| Length Indicator | | | | E | | ... | | | | | +| ... | | | | | | E | | LI | | | +| Length Indicator | | | | | | | | E | | Octet M | +| RLC data | | | | | | | | | | Octet M+1 | +| | | | | | | | | | | . | +| | | | | | | | | | | . | +| | | | | | | | | | | . | +| | | | | | | | | | | Octet N (see note) | + +NOTE: the RLC data may contain a non-integer number of octets. + +**Figure 12.8b.1.2.1: Downlink RLC/MAC block for data transfer in RLC acknowledged mode (PT=01)** + +### 12.8b.1.3 RLC transparent mode + +![](0f5c79ad7c317f14f16aa5a2c036e406_img.jpg) + +| Bit | | | | | | | | | | +|----------|---|---|---|---|---|---|---|--|--------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +| RLC data | | | | | | | | | Octet 1 | +| | | | | | | | | | . | +| | | | | | | | | | . | +| | | | | | | | | | . | +| | | | | | | | | | Octet N (see note) | + +NOTE: the RLC data may contain a non-integer number of octets. $N \geq 1$ . + +**Figure 12.8b.1.3.1: Downlink RLC/MAC block for data transfer in RLC transparent mode** + +NOTE: No payload type allows for making the distinction between an RLC/MAC block for data transfer in T-RLC and other RLC/MAC blocks. The identification of such an RLC/MAC block shall be done through the TFCI, i.e. some transport formats shall be reserved exclusively for using in T-RLC mode. + +## 12.8b.2 Uplink RLC/MAC block for data transfer + +### 12.8b.2.1 RLC unacknowledged mode + +The uplink RLC/MAC block format for data transfer in RLC unacknowledged mode is the same as for downlink, as specified in sub-clause 12.8b.1.1. + +### 12.8b.2.2 RLC acknowledged mode + +![](4bc9150c673850f31328befa6ca768ac_img.jpg) + +| Bit | | | | | | | | | | | +|------------------|---|--------------|---|----|---|-----|---|------------------|---------|--------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| PT | | TFI (=RB Id) | | | | | P | | Octet 1 | | +| BSN | | | | | | | | | Octet 2 | | +| BSN | | SPB | | SI | | E | | Length Indicator | Octet 3 | | +| Length Indicator | | | | E | | ... | | | | | +| ... | | | | | | E | | LI | | | +| Length Indicator | | | | | | | | E | | Octet M | +| E | | RLC data | | | | | | | | Octet M+1 | +| | | | | | | | | | | . | +| | | | | | | | | | | . | +| | | | | | | | | | | . | +| | | | | | | | | | | Octet N (see note) | + +NOTE: the RLC data may contain a non-integer number of octets + +**Figure 12.8b.2.2.1: Uplink RLC/MAC block for data transfer in RLC acknowledged mode (PT=01)** + +### 12.8b.2.3 RLC transparent mode + +![Diagram of an RLC transparent mode block. It shows a rectangular block labeled 'RLC data'. Above the block, bits 8 through 1 are indicated, with a 'Bit' label above bit 5. To the right of the block, 'Octet 1' is at the top, followed by vertical dots, and 'Octet N (see note)' at the bottom. A vertical dashed line runs through the center of the block, aligning with bit 5.](6a91a6df50795695b71693ad679a4f31_img.jpg) + +Diagram of an RLC transparent mode block. It shows a rectangular block labeled 'RLC data'. Above the block, bits 8 through 1 are indicated, with a 'Bit' label above bit 5. To the right of the block, 'Octet 1' is at the top, followed by vertical dots, and 'Octet N (see note)' at the bottom. A vertical dashed line runs through the center of the block, aligning with bit 5. + +NOTE: the RLC data may contain a non-integer number of octets. $N \geq 1$ + +**Figure 12.8b.2.3.1: Uplink RLC/MAC block for data transfer in RLC transparent mode** + +NOTE: No payload type allows for making the distinction between an RLC/MAC block for data transfer in T-RLC and other RLC/MAC blocks. The identification of such an RLC/MAC block shall be done through the TFCI, i.e. some transport formats shall be reserved exclusively for using in T-RLC mode. + +## 12.9 Header fields + +### 12.9.1 General + +The header fields described in this sub-clause are applicable only for the blocks described in the present TS. + +### 12.9.2 Payload Type (PT) field + +The Payload Type field shall indicate the type of data contained in remainder of the RLC/MAC block. The encoding of the Payload Type field is shown in table 12.9.2.1 and in table 12.9.2.2. + +**Table 12.9.2.1: Payload Type (PT) field (PDTCH, PACCH, FACCH, SACCH, SDCCH)** + +| Bit
2 1 | PT: Payload Type | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 | RLC Data block | +| 0 1 | RLC Control block related to an on-going RLC Data flow on the same logical channel (The corresponding RB is referred to with Reduced RBid field) | +| 1 0 | RLC Control block on FACCH related to an on-going RLC Data flow on TCH | +| 1 1 | Reserved | + +**Table 12.9.2.2: Payload Type (PT) field for FLO (CDCH, UDCH, ADCH)** + +| Bit
2 1 | PT: Payload Type | +|------------|--------------------------------------------| +| 0 0 | RLC Data block - SRB | +| 0 1 | RLC Data block – URB | +| 1 0 | RLC/MAC block for control message transfer | +| 1 1 | Reserved | + +### 12.9.3 Polling (P) bit + +The polling bit indicates whether or not the transmitter is polling for acknowledgement. With FLO, when included in an RLC/MAC block for data transfer, it also allows the reporting of link quality measurements along with the requested acknowledgement. It is encoded as shown in table 12.9.3.1. + +**Table 12.9.3.1: Polling (P) bit** + +| Bit | P: Polling Bit | +|-----|-----------------------------------| +| 0 | No polling | +| 1 | Polling: acknowledgement required | + +## 12.9.4 Reduced Radio Bearer identity (RRBid) field + +The reduced radio bearer identity field provides a one-to-one mapping with the RBid of the RB to which either the RLC data block belongs, or the RLC/MAC control block relates. This field is used in the same way as is the TFI in (E)GPRS RLC/MAC blocks. It is encoded as shown in table 12.9.4.1. + +**Table 12.9.4.1: Reduced Radio Bearer identity (RRBid) field** + +| Bit
3 2 1 | RRBid: Reduced Radio Bearer identity | +|--------------|-----------------------------------------------------------------------------------------------------------------------| +| 0 0 0 | Signalling Radio Bearer 1 | +| 0 0 1 | Signalling Radio Bearer 2 | +| 0 1 0 | Signalling Radio Bearer 3 | +| 0 1 1 | Signalling Radio Bearer 4 | +| 1 x x | User-plane Radio Bearer
The correspondence between Reduced RBid and the RBid in this case is provided at RB setup. | + +## 12.9.5 More (M) bit and Extension (E) bit + +These bits are used in the same way as is described in 3GPP TS 44.060 sub-clauses 10.4.11 and 10.4.13 for GPRS TBF mode. + +## 12.9.6 Extension bis (Ebis) bit + +The Extension bis (Ebis) bit is used to indicate the presence of an optional octet in the RLC data block header. + +**Table 12.9.6.1: Extension bis (Ebis) bit** + +| bit 1 | Ebis bit | +|-------|-------------------------------------| +| 0 | Extension octet follows immediately | +| 1 | No extension octet follows | + +## 12.9.7 Stall Indicator (SI) bit + +The Stall Indicator bit is used as is described in 3GPP TS 44.060 sub-clause 10.4.3. + +## 12.9.8 Ack Indicator (AI) field + +The Ack Indicator field indicates whether or not an acknowledgement bitmap is piggy-backed in the RLC/MAC block. It is encoded as shown in table 12.9.8.1. + +**Table 12.9.8.1: Ack Indicator (AI) field** + +| Bit
2 1 | AI: Ack Indicator | +|------------|------------------------------------------------------------------------------------------------------------------------------| +| 0 0 | Ack/Nack description field not included – Reserved | +| 0 1 | Ack/Nack description not included. No retransmission requested (all RLC blocks received, similar to FINAL_ACK_INDICATION==1) | +| 1 0 | Ack/Nack description field included | +| 1 1 | Reserved | + +## 12.9.9 Ack/Nack Description field + +**Table 12.9.9.1: Ack/Nack Description field** + +| Ack/Nack Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

< Ack/Nack Description IE> ::=

<Reduced RBid : bit(3)>

<STARTING_SEQUENCE_NUMBER : bit(4)>

<RECEIVED_BLOCK_BITMAP : bit(8)>

Reduced Rbid

The reduced radio bearer identity field provides a one-to-one mapping with the RBid of the RB in the opposite direction to which the acknowledgement bitmap is targetted. It is encoded as shown in table 12.3, sub-clause 12.9.4.

STARTING_SEQUENCE_NUMBER (SSN):

The SSN contains the value of V(R) when this field was transmitted. This field is encoded as the binary representation of V(R).

Range 0 to 15

RECEIVED_BLOCK_BITMAP (RBB):

The RBB is a bitmap representing Block Sequence Numbers. The bitmap is indexed relative to SSN as follows:

BSN=(SSN – bit_number) modulo 16 for bit_number=1 to 8.

The BSN values represented range from (SSN-1) mod 16 to (SSN-8) mod 16.

The value of each bit is encoded as:

0: Negative acknowledgement of the RLC data block with BSN=(SSN-bit_number) mod 16

1: Positive acknowledgement of the RLC data block with BSN=(SSN-bit_number) mod 16.

Mapping of the bitmap is defined in sub-clause 11.

| + +## 12.9.10 G-RNTI indicator (GI) bit + +The G-RNTI indicator bit indicates the presence of an optional G-RNTI field within the RLC data block, when on SDCCH. It is encoded as shown in table 12.9.10.1. + +**Table 12.9.10.1: G-RNTI indicator (GI) bit** + +| Bit | GI: G-RNTI indicator bit | +|------------|---------------------------------| +| 0 | G-RNTI field is not present | +| 1 | G-RNTI field is present | + +## 12.9.11 Segmentation (S) bit + +The Segmentation bit indicates whether or not the RLC/MAC control block is a segment of an RLC/MAC control message. It is encoded as shown in table 12.9.11.1. + +**Table 12.9.11.1: Segmentation (S) bit** + +| Bit | S: Segmentation bit | +|------------|----------------------------------------------------------------------| +| 0 | The RLC/MAC control block contains an entire RLC/MAC control message | +| 1 | The RLC/MAC control block is a segment of an RLC/MAC control message | + +## 12.9.12 Reduced Block Sequence Number (RBSN) bit + +The Reduced Block Sequence Number (RBSN) bit carries the sequence number of the RLC/MAC control blocks. The RBSN bit is encoded as a binary number with range 0 to 1. The RBSN bit is present if and only if the S bit is set (see sub-clause 12.9.11). + +## 12.9.13 (void) + +## 12.9.14 Radio Transaction Identifier (RTI) field + +The Radio Transaction Identifier (RTI) field is used to group the RLC/MAC control blocks that make up an RLC/MAC control message and identifies the segmented control message sequence with which the RLC/MAC control block is associated. The RTI field is 2 bits in length with range 0 to 3. The RTI field is present if and only if the S bit is set (see sub-clause 12.9.11). The RTI is unique on a given logical channel in a given direction. + +NOTE: An RTI value may be repeated in both directions on a given logical channel (e.g. FACCH uplink and FACCH downlink), and across logical channels (e.g., FACCH and SACCH). + +## 12.9.15 Block Sequence Number (BSN) field + +The Block Sequence Number (BSN) field carries the sequence absolute Block Sequence Number (BSN') modulo Sequence Number Space (SNS) (16 in DCCH TBF mode, 256 in TCH TBF mode (NT-RLC)) of each RLC data block within the TBF. + +In DCCH TBF mode and CDCH TBF mode, the BSN is 4 bits in length and is encoded as a binary number with range 0 to 15. + +In TCH TBF mode (NT-RLC), the BSN is 8 bits in length and is encoded as a binary number with range 0 to 255. + +In UDCH TBF mode, in RLC unacknowledged mode, the BSN is 4 bits in length and is encoded as a binary number with range 0 to 15. + +In UDCH TBF mode, in RLC acknowledged mode, the BSN is 10 bits in length and is encoded as a binary number with range 0 to 1023. + +## 12.9.16 Radio Bearer Identity (RB Id) field + +The Rb Id uniquely identifies a Radio Bearer. This field is encoded as a binary number with range 0-31. + +## 12.9.17 Signalling Radio Bearer Identity (SRB Id) field + +The Signalling Radio Bearer Identity (SRB Id) field is used to identify the SRB to which the RLC data block belongs. It is encoded as shown in table 12.9.17.1. + +**Table 12.9.17.1: Signalling Radio Bearer Identity (SRB Id) field** + +| Bit
2 1 | SRB Id: Signalling Radio Bearer Identity | +|------------|------------------------------------------| +| 0 0 | SRB1 | +| 0 1 | SRB2 | +| 1 0 | SRB3 | +| 1 1 | SRB4 | + +## 12.9.18 GERAN Radio Network Temporary Identity Extension (G-RNTI Extension) field + +This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field. + +## 12.9.19 Length Indicator (LI) field + +In GPRS TBF mode, EGPRS TBF mode, TCH TBF mode, DCCH TBF mode and CDCH TBF mode, the Length Indicator bit is used as is described in 3GPP TS 44.060 sub-clauses 10.4.14 and 10.4.14a. + +In UDCH TBF mode, the Length Indicator is used as described in 3GPP TS 44.060 sub-clauses 10.4.14 and 10.4.14a, with the following exceptions: + +- The Length Indicator field is 8 bits in length and shall be encoded as a binary number. +- The valid values are the values ranging from 0 to 171, and the value 255. All other values are reserved. + +- An 8-bit Length Indicator of value 255 shall be treated as described in 3GPP TS 44.060 for a 7-bit Length Indicator of value 127 +- An 8-bit Length Indicator of value 127 shall be treated as a length indication of 127 octets, and not as a 7-bit Length Indicator of value 127 + +The interpretation of the value contained in the length indicator with corresponding E bit in UDCH TBF mode is summarized in table 12.9.19.1. + +**Table 12.9.19.1: Interpretation of values of LI field and E bit in UDCH TBF mode** + +| Value of LI in a RLC data block | Value of the following E bit | Interpretation | +|------------------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| k-th LI:
0 < value < 172
(k > 0 integer) | | The value of the k-th LI is the number of octets of the k-th Upper Layer PDU, or the last segment of it, in the current RLC data block. | +| | 0 | There is at least one Upper Layer PDU following the k-th Upper Layer PDU in the current RLC data block. | +| | 1 | There is no more than one Upper Layer PDU following the k-th Upper Layer PDU in the current RLC data block. | +| 1 st LI: value = 0 | 0 | The last Upper Layer PDU of the previous in sequence RLC data block ends at the boundary of that RLC data block and it has no LI in the header of that RLC data block. | +| k-th LI:
0 < value < 172
(k > 1 integer) | | The k-th LI contains the number of octets of the (k-1)-th Upper Layer PDU in the current RLC data block. | +| | 0 | There is at least one Upper Layer PDU following the (k-1)-th Upper Layer PDU in the current RLC data block. | +| | 1 | There is no more than one Upper Layer PDU following the (k-1)-th Upper Layer PDU in the current RLC data block. | +| k-th LI: value = 255 | 1 | The octets between the end of the Upper Layer PDU indicated by the (k-1)-th LI and the end of the current RLC data block are filling octets, or the octets contain part of an Upper Layer PDU that cannot be transmitted completely in the current RLC data block and will not be continued in the next in-sequence RLC data block. | +| 1 st LI: value = 0 | 1 | The previous RLC data block contains a Upper Layer PDU, or a part of it, that fills precisely the previous data block and for which there is no length indicator in that RLC data block. The current RLC data block contains a Upper Layer PDU that either fills the current RLC data block precisely or continues in the next RLC data block. | +| 1 st LI: value = 255 | 1 | All octets of the RLC Data block contain filling information. | +| No LI field present | n.a. | The Upper Layer PDU that starts with the current RLC data block either fills the current RLC data block precisely or continues in the following in-sequence RLC data block | + +## 12.9.20 PFI Indicator (PI) field + +The PFI Indicator is not used in *Iu mode*. + +## 12.9.21 HFN Least Significant Bit (HFN\_LSB) field + +The HFN Least Significant Bit (HFN\_LSB) field contains the least significant bit of the HFN of the radio bearer to which the RLC/MAC block belongs, in the direction where this RLC/MAC block is sent. + +# 13 Ciphering + +## 13.1 General + +The ciphering function is performed either in the RLC sublayer or in the MAC sublayer according to the following rules: + +- The RLC sublayer is responsible for ciphering/deciphering RLC data blocks in case of non-transparent RLC mode (unacknowledged or acknowledged). + +- The MAC sublayer is responsible for ciphering/deciphering user data in case of transparent RLC mode. It is also responsible for ciphering/deciphering some RLC/MAC control messages. + +The ciphering function shall use the ciphering algorithm f8 specified in 3GPP TS 35.201. Four input parameters are necessary to configure the ciphering algorithm: + +- *Ciphering key*: the 128-bit *ciphering key* is received from RRC by means of interlayer primitive. +- *Bearer*: the 5-bit *bearer* indicates, when available, the radio bearer identity of the radio bearer to cipher. It is received from RRC by means of interlayer primitive. +- *Direction*: the 1-bit *direction* indicates the direction of transmission, uplink or downlink, of the flow to cipher. +- *Count*: the 32-bit *count* is used to ensure that the blocks of a same flow are all ciphered differently. + +A fifth parameter, *Length*, is used to indicate the length in bits of the plain data to cipher. Plain, ciphered and deciphered data are of the same length. Length is not input to the ciphering algorithm. + +## 13.2 Applicability of ciphering + +Ciphering may apply only between the mobile station and the serving BSS when contention resolution is successfully completed, i.e. uplink data (respectively downlink data) between the mobile station and the serving BSS may be ciphered after contention is successfully completed on mobile station side (respectively serving BSS side). + +## 13.3 Ciphering at RLC sublayer + +### 13.3.1 General + +The RLC sublayer is responsible for ciphering/deciphering RLC data blocks in case of non-transparent RLC mode (unacknowledged or acknowledged). + +For a given radio bearer, ciphering/deciphering is ordered by RRC by means of the CRLC-CONFIG-Req primitive containing the necessary ciphering elements (see sub-clause 4.3.3). Upon receipt of the CRLC-CONFIG-Req primitive containing the ciphering elements, ciphering shall be performed at RLC sublayer according to these ciphering elements for the corresponding radio bearer. Ciphering shall not be performed at RLC sublayer otherwise. + +### 13.3.2 Parameter settings + +#### 13.3.2.1 Input parameters to the ciphering algorithm + +Table 13.3.2.1.1 defines how to set the input parameters to the ciphering algorithm. + +**Table 13.3.2.1.1: Input parameters to the ciphering algorithm** + +| Input parameters | Size in bits | Settings | | | | | +|------------------|--------------|--------------------------------------------|-------------------------------------|-------------------------------|--------------------------------|-------------------------------| +| | | TBF mode
(see note 1) | DCCH | TCH | GPRS | EGPRS | +| Count | 32 MSB | HFN (see note 2) | 27 bits
0...134217727 | 23 bits
0...8388607 | 24 bits
0...16777215 | 20 bits
0...1048575 | +| | LSB | RBid indicator | 1 bit
1 (RBid available) | | | | +| | | BSN | 4 bits
0...15 | 8 bits
0...255 | 7 bits
0...127 | 11 bits
0...2047 | +| Direction | 1 | Direction | 1 bit
0 (uplink)
1 (downlink) | | | | +| Bearer | 5 | RBid | 5 bits
0...31 | | | | +| Length | 10 | Length in bits of the plain data to cipher | 10 bits
0...592 | | | | + +NOTE 1: Four cases are distinguished as per the format of the BSN used in the RLC data block to cipher, according to the TBF mode: DCCH TBF mode, TCH TBF mode, GPRS TBF mode and EGPRS TBF mode. + +NOTE 2: The handling of the HFN is described in sub-clause 13.3.2.2. + +NOTE 3: The values in italic represent the range for a given parameter. + +**Table 13.3.2.1.2: Input parameters to the ciphering algorithm (FLO)** + +| Input parameters | Size in bits | Settings | | | | +|------------------|--------------|--------------------------------------------|-------------------------------------|-------------------|------| +| | | TBF mode
(see note 1) | UDCH (RLC AM) | UDCH (RLC UM) | CDCH | +| Count | 32 MSB | HFN (see note 2) | 21 bits
0...2097171 | See DCCH TBF Mode | | +| | LSB | RBid indicator | 1 bit
1 (RBid available) | | | +| | | BSN | 10 bits
0...1023 | | | +| Direction | 1 | Direction | 1 bit
0 (uplink)
1 (downlink) | | | +| Bearer | 5 | RBid | 5 bits
0...31 | | | +| Length | 10 | Length in bits of the plain data to cipher | 11 bits
0...1370 | | | + +NOTE 1: Four cases are distinguished as per the format of the BSN used in the RLC data block to cipher, according to the TBF mode: UDCH TBF mode, CDCH TBF mode. + +NOTE 2: The handling of the HFN is described in sub-clause 13.3.2.2. + +NOTE 3: The values in italic represent the range for a given parameter. + +### 13.3.2.2 Handling of the HFN + +The HFN is radio bearer specific. + +In RLC acknowledged mode, the HFN used at retransmission of an RLC data block shall be the same as the one used at original transmission of this RLC data block. + +The HFN shall be increased by one at every cycle of the BSN, when the BSN reaches 0. + +Further handling of the HFN is described in 3GPP TS 44.118. + +### 13.3.3 Ciphering of RLC PDUs in non-transparent RLC mode + +Ciphering may only apply on the payload of the RLC PDUs. For instance, if MCS-9 is used, only the 592 bits of the payload of each of the two RLC data blocks in the RLC/MAC block may be ciphered. + +## 13.4 Ciphering at MAC sublayer + +### 13.4.1 General + +The MAC sublayer is responsible for ciphering/deciphering user data in case of transparent RLC mode. It is also responsible for ciphering some RLC/MAC control messages. + +For a given radio bearer, ciphering/deciphering is ordered by RRC by means of the CMAC-CONFIG-Req primitive containing the necessary ciphering elements (see sub-clause 4.3.4). Upon receipt of the CMAC-CONFIG-Req primitive containing the ciphering elements, ciphering/deciphering shall be performed at MAC sublayer according to these ciphering elements for the corresponding radio bearer. Ciphering shall not be performed at MAC sublayer otherwise. + +### 13.4.2 Parameter settings + +#### 13.4.2.1 Input parameters to the ciphering algorithm + +Table 13.4.2.1.1 defines how to set the input parameters to the ciphering algorithm in case of transparent RLC mode. + +**Table 13.4.2.1.1: Input parameters to the ciphering algorithm for layer 2 data in transparent RLC mode** + +| Input parameters | Size in bits | Settings | | +|------------------|--------------|--------------------------------------------|---------------------------------------------------| +| Count | 32 MSB | HFN (see note 1) | 11 bits
0...2047 | +| | | TDMA Frame Number (see note 2) | 17 bits | +| | LSB | RBid indicator | 1 bit
1 (RBid available) | +| | | Timeslot number | 3 bits
0...7 | +| Direction | 1 | Direction | 1 bit
0 (uplink)
1 (downlink) | +| Bearer | 5 | RBid | 5 bits
0...31 | +| Length | N | Length in bits of the plain data to cipher | Size of the RLC PDU (see note 3) | + +NOTE 1: The handling of the HFN is described in sub-clause 13.4.2.2.1. +NOTE 2: The 17-bit TDMA Frame Number is described below. +NOTE 3: In transparent RLC mode, the size of an RLC PDU equals that of the RLC SDU it carries. +NOTE 4: The values in *italic* represent the range for a given parameter. + +Table 13.4.2.1.2 defines how to set the input parameters to the ciphering algorithm for ciphering of RLC/MAC control messages. The rules for ciphering RLC/MAC control messages are given in sub-clause 13.4.3. + +**Table 13.4.2.1.2: Input parameters to the ciphering algorithm for RLC/MAC control messages** + +| Input parameters | Size in bits | Settings | | +|------------------|--------------|--------------------------------------------|---------------------------------------------------| +| Count | 32 MSB | HFN (see note 1) | 11 bits
0...2047 | +| | | TDMA Frame Number (see note 2) | 17 bits | +| | LSB | RBid indicator | 1 bit
0 (RBid not available) | +| | | Timeslot number | 3 bits
0...7 | +| Direction | 1 | Direction | 1 bit
0 (uplink)
1 (downlink) | +| Bearer | 5 | RBid | 5 bits
"00000" | +| Length | 9 | Length in bits of the plain data to cipher | 9 bits
0...368 (see note 3) | + +NOTE 1: The handling of the HFN is described in sub-clause 13.4.2.2.2. +NOTE 2: The 17-bit TDMA Frame Number is described below. +NOTE 3: The length in bits of the plain data to cipher can be derived from the rules given in sub-clause 13.4.3 on a per RLC/MAC control message basis. +NOTE 4: The values in *italic* represent the range for a given parameter. + +The 17-bit TDMA Frame Number is constructed as follows: + +| Bit | | | | | | | | | | | | | | | | | +|-----|----|----|----|----|----|----|----|---|---|---|----|---|---|---|---|---| +| 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| T1' | | | | | | T2 | | | | | T3 | | | | | | + +**Figure 13.4.2.1.1: 17-bit TDMA Frame Number** + +| | | | +|--------------|---------------|-------------------------------------------| +| T1' (6 bits) | range 0 to 63 | = T1 mod 64. | +| T2 (5 bits) | range 0 to 25 | = FN mod 26 as defined in 3GPP TS 45.002. | +| T3 (6 bits) | range 0 to 50 | = FN mod 51 as defined in 3GPP TS 45.002. | + +where + +T1 = FN div (26 x 51) as defined in 3GPP TS 45.002. + +and + +FN = TDMA frame number as defined in 3GPP TS 45.002. + +## 13.4.2.2 Handling of the HFN + +### 13.4.2.2.1 Ciphering in transparent RLC mode + +The HFN is radio bearer specific. It shall obey the following rules for the lifetime of the corresponding radio bearer: + +- It shall be incremented by 1 every time the TDMA Frame Number is smaller than the previous one. +- It shall also be incremented by 1 at every cell change. + +Further handling of the HFN is described in 3GPP TS 44.118. + +### 13.4.2.2.2 Ciphering of RLC/MAC control messages + +The HFN presented in table 13.3 shall obey the following rules: + +- It shall be reset to START value every time a new authentication is made. +- During an RRC connection: + - It shall be incremented by 1 every time the TDMA Frame Number is smaller than the previous one. + - It shall also be incremented by 1 at every cell change. +- It shall be incremented by 1 at every new RRC connection and notified to the network at RRC connection set-up see 3GPP TS 44.118. + +### 13.4.3 Ciphering of RLC/MAC control messages + +The following RLC/MAC control messages may be ciphered: + +- PACKET RESOURCE REQUEST, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET DBPSCH ASSIGNMENT, PACKET UPLINK ACK/NACK, PACKET DBPSCH UPLINK ACK/NACK, PACKET DBPSCH UPLINK ACK/NACK TYPE 2, PACKET DOWNLINK ACK/NACK, EGPRS PACKET DOWNLINK ACK/NACK, PACKET DBPSCH DOWNLINK ACK/NACK, PACKET DBPSCH DOWNLINK ACK/NACK TYPE 2, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET TBF RELEASE and PACKET CELL CHANGE ORDER, PHYSICAL INFORMATION. + +NOTE 1: This list should be updated according to the RLC/MAC development i.e. if new messages are created or if some of the messages in this list are no more applicable to *Iu mode*. The list of Fields and IEs in the table below will also be updated according to the RLC/MAC development. + +Within these messages, all CSN-1 syntax bits shall be kept unciphered. Furthermore, the ciphering of these messages shall obey the rules given in table 13.4.3.1. + +NOTE 2: An informative annex will be introduced to illustrate an example of ciphering of an RLC/MAC control message. + +**Table 13.4.3.1: Ciphering of RLC/MAC control messages** + +| RLC/MAC Control Message | Direction | Fields and IEs that shall be kept unciphered | +|-------------------------|-----------|----------------------------------------------| +|-------------------------|-----------|----------------------------------------------| + +| | | | +|----------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Packet Resource Request | Uplink | Message type, GLOBAL_TFI, Length of MS RA capabilities, Length | +| Packet Uplink Assignment | Downlink | Message type, PAGE_MODE, PERSISTENCE_LEVEL, GLOBAL_TFI, TLLI/G-RNTI, G-RNTI extension, TQI, Length of MA Frequency List contents, MA_LENGTH | +| Multiple TBF Uplink Assignment | Downlink | Message type, PAGE_MODE, PERSISTENCE_LEVEL, GLOBAL_TFI, TLLI/G-RNTI, G-RNTI extension | +| Packet Downlink Assignment | Downlink | Message type, PAGE_MODE, PERSISTENCE_LEVEL, GLOBAL_TFI, TLLI/G-RNTI, G-RNTI extension, Length of MA Frequency List contents, MA_LENGTH | +| Multiple TBF Downlink Assignment | Downlink | Message type, PAGE_MODE, PERSISTENCE_LEVEL, GLOBAL_TFI, TLLI/G-RNTI, G-RNTI extension | +| Packet DBPSCH Assignment | Downlink | Message type, PAGE_MODE, PERSISTENCE_LEVEL, GLOBAL_TFI, G-RNTI | +| Packet Uplink Ack/Nack | Downlink | Message type, PAGE_MODE, UPLINK_TFI, CONTENTION_RESOLUTION_G-RNTI, G-RNTI extension, Extension length, COMPRESSED_BITMAP_LENGTH | +| Packet DBPSCH Uplink Ack/Nack | Downlink | Message type, RBId | +| Packet DBPSCH Uplink Ack/Nack Type 2 | Downlink | Message type, RBId | +| Packet Downlink Ack/Nack | Uplink | Message type, DOWNLINK_TFI | +| EGPRS Packet Downlink Ack/Nack | Uplink | Message type, DOWNLINK_TFI, Extension length, COMPRESSED_BITMAP_LENGTH | +| Packet DBPSCH Downlink Ack/Nack | Uplink | Message type, RBId | +| Packet DBPSCH Downlink Ack/Nack Type 2 | Downlink | Message type, RBId | +| Packet Timeslot Reconfigure | Downlink | Message type, PAGE_MODE, GLOBAL_TFI, Length of MA Frequency List contents, MA_LENGTH | +| Multiple TBF Timeslot Reconfigure | Downlink | Message type, PAGE_MODE, GLOBAL_TFI | +| Packet TBF Release | Downlink | Message type, PAGE_MODE, GLOBAL_TFI | +| Packet Cell Change Order | Downlink | Message type, PAGE_MODE, GLOBAL_TFI, TLLI/G-RNTI, G-RNTI extension, NR_OF_REMOVED_FREQ, NR_OF_FREQUENCIES, FREQ_DIFF_LENGTH | +| Physical Information | Downlink | Message type | + +### 13.4.4 Ciphering of RLC PDUs in transparent RLC mode + +Ciphering applies on the complete RLC PDUs. + +## 14 RLC suspension, stop and re-establishment procedures + +### 14.1 General + +This sub-clause describes the following RLC procedures: suspend/resume, stop/continue and re-establishment. These procedures are requested by RRC (see 3GPP TS 44.118), and are applicable in NT-RLC only. Suspend/resume is used when e.g. ciphering parameters are changed. Stop/continue and re-establishment are used during e.g. RB reconfiguration. + +### 14.2 Local suspend/resume function (NT-RLC) + +The upper layers may suspend/resume a RLC entity. Suspension of a RLC entity is ordered through the CRLC-SUSPEND-Req primitive (see sub-clause 4.3.3). Resumption is ordered through the CRLC-RESUME-Req primitive (see sub-clause 4.3.3). + +When a RLC entity operating in unacknowledged mode is suspended by upper layers with the parameter N, the RLC entity shall: + +- acknowledge the suspend request through the CRLC-SUSPEND-Conf primitive containing the current value of the send-state variable V(S); +- not send any RLC data block with a "Block Sequence Number" BSN $\geq$ (V(S)+N) modulo SNS; +- send Packet Uplink/Downlink Dummy control blocks on allocated radio resources if there is no other RLC/MAC control message to be sent. + +When a RLC entity operating in acknowledged mode is suspended by upper layers with the parameter N, the RLC entity shall: + +- acknowledge the suspend request through the CRLC-SUSPEND-Conf primitive containing the current value of the send-state variable V(S); +- not send any RLC data block with "Block Sequence Number" BSN $\geq$ (V(S) + N) modulo SNS; +- proceed with retransmission procedures for RLC data blocks with BSN $<$ (V(S) + N) modulo SNS as defined in sub-clauses 10.4.5 and 11.4.2; +- send Packet Uplink/Downlink Dummy control blocks on allocated radio resources if there is no other RLC/MAC control message or RLC data block to be sent. + +When a RLC entity operating in unacknowledged mode is resumed by upper layers, the RLC entity shall: + +- resume data transfer procedure. + +When a RLC entity operating in acknowledged mode is resumed by upper layers, the RLC entity shall: + +- resume data transfer procedure. + +## 14.3 Stop/continue function (NT-RLC) + +The RLC stop/continue procedure is applicable on DBPSCHs only. + +The upper layer may stop/continue a RLC entity. Stop of a RLC entity is ordered through the CRLC-CONFIG-Req primitive (see sub-clause 4.3.3). Continuation of a RLC entity is ordered through the CRLC-CONFIG-Req primitive (see sub-clause 4.3.3). + +When a uplink RLC entity is stopped, the mobile station shall pause the timers T3180 and T3182 if running. When a downlink RLC entity is stopped, the mobile station shall pause timer T3190 if running. + +When an uplink RLC entity is continued, the mobile station shall continue the timers T3180 and T3182 if paused. When a downlink RLC entity is continued, the mobile station shall start timer T3190 if paused. + +When a RLC entity is stopped by upper layers, the RLC entity shall: + +- not submit any RLC data blocks to lower layer or accept any RLC data blocks; +- not submit any RLC/MAC control message to lower layer or accept any RLC/MAC control message; +- save all state variables. + +When a RLC entity is continued by upper layers, the RLC entity shall: + +- if the RLC entity is stopped: + - continue the data transmission and reception from the stored state variables. +- otherwise, if the RLC is not stopped: + - take no action. + +## 14.4 RLC re-establishment function (NT-RLC) + +The RLC re-establishment function is applicable in NT-RLC only, on DBPSCHs only. + +The upper layers may re-establish a RLC entity. Re-establishment of a RLC entity is ordered through the RLC-CONFIG-Req primitive (see sub-clause 4.3.3). + +When a RLC entity is re-established by upper layers, the RLC entity shall: + +- reset the state variables to their initial value; +- set the configurable parameters (e.g. EGPRS RLC window size) to their configured value; +- set the hyper frame number (HFN) in UL and DL to the value configured by upper layers; +- if the RLC entity is operating in unacknowledged mode: + - if it is a receiving RLC entity: + - discard all RLC data blocks (PDUs). + - if it is a transmitting RLC entity: + - discard the RLC SDUs for which one or more segments have been submitted to the MAC layer. +- otherwise if the RLC entity is operating in acknowledged mode: + - discard all RLC data blocks (PDUs) and RLC/MAC control messages for this RLC entity. + +--- + +## Annex A (informative): Change History + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-01 | | - | - | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | - | Rel-14 version created based on v13.0.0 | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Rel-15 version created based on v14.0.0 | 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/44_series/44318/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-16/44_series/44318/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec8450478ea27c1712ad52e7982ea5aff965b98e --- /dev/null +++ b/marked/Rel-16/44_series/44318/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9c975315321d3c369c54e72d18ee28c8874507a62f9513bccaa78b3773ba93a +size 25414 diff --git a/marked/Rel-16/44_series/44318/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-16/44_series/44318/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb5cbd079b941225cd357b03e0ab06326c4434d0 --- /dev/null +++ b/marked/Rel-16/44_series/44318/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7ccbde7417b9224149abfc93780ce330a249143e4e1f6fbd4a881761e1f4139 +size 22716 diff --git a/marked/Rel-16/44_series/44318/0549ab3c68ad94e7e1bb6ec6aa6b5373_img.jpg b/marked/Rel-16/44_series/44318/0549ab3c68ad94e7e1bb6ec6aa6b5373_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daa423ca941eeb6b90ef1fbffb9756bdca16fb25 --- /dev/null +++ b/marked/Rel-16/44_series/44318/0549ab3c68ad94e7e1bb6ec6aa6b5373_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14b2537afd79ad393719357ebce9e2ec6109ee4280a3b0709377059dd4c21bfe +size 18949 diff --git a/marked/Rel-16/44_series/44318/0a595a22e0d1a1be020b49afa71bef55_img.jpg b/marked/Rel-16/44_series/44318/0a595a22e0d1a1be020b49afa71bef55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb1207dc4e9bc858609c1662f16f766a2ff1d351 --- /dev/null +++ b/marked/Rel-16/44_series/44318/0a595a22e0d1a1be020b49afa71bef55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6fb2b14989549d60ad1cb335ea8578a20602962f080f333ec6e4dc0771dc265 +size 17144 diff --git a/marked/Rel-16/44_series/44318/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/44_series/44318/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..295fe92f85503f3c4ff1b7a6e73ee25d7248317f --- /dev/null +++ b/marked/Rel-16/44_series/44318/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8fda11ca2cdc8ce46035b2d757abf073dc62016dfe6c5d85a4894e9b26ef3da +size 39351 diff --git a/marked/Rel-16/44_series/44318/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/44_series/44318/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d78db2fbf182f6d2b284374217a3c8519bec976 --- /dev/null +++ b/marked/Rel-16/44_series/44318/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14e8ae421eeafd67706591b016a34140f86be0319b9b153fe02eb125fec1bbbd +size 25900 diff --git a/marked/Rel-16/44_series/44318/0bdf45f8598420cf51abdd73300adc83_img.jpg b/marked/Rel-16/44_series/44318/0bdf45f8598420cf51abdd73300adc83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..376dd50a2f8ab7823d32b109a9af8706f4e50dea --- /dev/null +++ b/marked/Rel-16/44_series/44318/0bdf45f8598420cf51abdd73300adc83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90c2b2f558c103a809481a4629bab30e07a23a329f6c2301a78ea04011bde896 +size 16438 diff --git a/marked/Rel-16/44_series/44318/0c5f3d0d14479b9e784d595fecd6dba5_img.jpg b/marked/Rel-16/44_series/44318/0c5f3d0d14479b9e784d595fecd6dba5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f162a5e13b4ce003f70f3ab012ea63a0e862d985 --- /dev/null +++ b/marked/Rel-16/44_series/44318/0c5f3d0d14479b9e784d595fecd6dba5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:036306eb001cd4233da551da3076a27eee6cb75c83b517b469793515b4b2b857 +size 32867 diff --git a/marked/Rel-16/44_series/44318/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-16/44_series/44318/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf598c9b0c95f29c0ac8c5f161beb27a01d94fe9 --- /dev/null +++ b/marked/Rel-16/44_series/44318/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4e12b2c84c7401d830bb16a19bb999c42293139bc00d5ca4a6b7f3a340658c9 +size 35213 diff --git a/marked/Rel-16/44_series/44318/0fa5b60804100c3aead10404f9f226f9_img.jpg b/marked/Rel-16/44_series/44318/0fa5b60804100c3aead10404f9f226f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70da9a13e85bfdc58a85e70dc9d4580fb0cf8b81 --- /dev/null +++ b/marked/Rel-16/44_series/44318/0fa5b60804100c3aead10404f9f226f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adeb0ef9830155cc81a6c684ee7a1c53a5faaf6092205c28867f60b9e1a2ce64 +size 26513 diff --git a/marked/Rel-16/44_series/44318/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Rel-16/44_series/44318/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c74da96742a9e0413548cb8c407c28e7462be8b0 --- /dev/null +++ b/marked/Rel-16/44_series/44318/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7098fb91ff2e31426ba55abae852a29af2b5c27d4e6b511143ecce82a0cf52b4 +size 49259 diff --git a/marked/Rel-16/44_series/44318/133d09b09892b9fa5e84cfaa627e11a2_img.jpg b/marked/Rel-16/44_series/44318/133d09b09892b9fa5e84cfaa627e11a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3720ea21a8f871410e445b17ad047d14cec9edcc --- /dev/null +++ b/marked/Rel-16/44_series/44318/133d09b09892b9fa5e84cfaa627e11a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7161c57007829bb8620929a3606db051a2122fc9770d085af7ffc3689d1be269 +size 6984 diff --git a/marked/Rel-16/44_series/44318/19127cc2db2eb92d1134a2244b47cddc_img.jpg b/marked/Rel-16/44_series/44318/19127cc2db2eb92d1134a2244b47cddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8a11b5cb261760dc609e384d4c559884d9cac66 --- /dev/null +++ b/marked/Rel-16/44_series/44318/19127cc2db2eb92d1134a2244b47cddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f1321a23678e31d043667364ea799d6e2cd1a9396faa87a18df26b98b9da20e +size 17777 diff --git a/marked/Rel-16/44_series/44318/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg b/marked/Rel-16/44_series/44318/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85a83daeb68babf75ecf2947b5fa54cac876ca17 --- /dev/null +++ b/marked/Rel-16/44_series/44318/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8e85d6cb732f133bbe89b3461404949cf71bc7a7e731d6e46d1abc88c27d64c +size 19462 diff --git a/marked/Rel-16/44_series/44318/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/marked/Rel-16/44_series/44318/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..732b1253427cd390867bf1c7553fde42beffc6a6 --- /dev/null +++ b/marked/Rel-16/44_series/44318/215165a27ad7d72bd39fdf55a3cb7486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:027936d60d44c15482b3d7dfe2156edda2376a06ae8c67fdc0cd0061fdf5b2f2 +size 37361 diff --git a/marked/Rel-16/44_series/44318/2232c471414cb1ca6484a5a1d0a2dd27_img.jpg b/marked/Rel-16/44_series/44318/2232c471414cb1ca6484a5a1d0a2dd27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8280cf5e049256884530b122111721eab9976449 --- /dev/null +++ b/marked/Rel-16/44_series/44318/2232c471414cb1ca6484a5a1d0a2dd27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7699039197f960144f689d250b2fd49e2fbf51127b0cddf16ccf5513a3b548f7 +size 19737 diff --git a/marked/Rel-16/44_series/44318/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/44_series/44318/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a97f8f129ea3b0d0ec18648b26ff8f70551c32f --- /dev/null +++ b/marked/Rel-16/44_series/44318/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eef3ea5e6ad25c596be040ef4537ef017e1c63de63944105e117e06b395ac325 +size 41602 diff --git a/marked/Rel-16/44_series/44318/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/44_series/44318/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..576a71009b289519e1e80abe7e5fb1420d1e5f8a --- /dev/null +++ b/marked/Rel-16/44_series/44318/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86a434dd82c480bcf8fba9e01342bb2935034b98ff3f7ebfa394c15f2a5e5ce1 +size 18304 diff --git a/marked/Rel-16/44_series/44318/2c38051409fe1c92ed774b445a768886_img.jpg b/marked/Rel-16/44_series/44318/2c38051409fe1c92ed774b445a768886_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68bee1e4d1951566eb6547c018508b344af1786a --- /dev/null +++ b/marked/Rel-16/44_series/44318/2c38051409fe1c92ed774b445a768886_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7cf28970938dd41e9e4fed821e474d03845cfb65564a2582754de9f68fa5a99 +size 38121 diff --git a/marked/Rel-16/44_series/44318/315e87b80426782bb6e06222d653f515_img.jpg b/marked/Rel-16/44_series/44318/315e87b80426782bb6e06222d653f515_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81fde85b2b464ee65f5667a2cf651e95e2e06fb3 --- /dev/null +++ b/marked/Rel-16/44_series/44318/315e87b80426782bb6e06222d653f515_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9c275ce12b4835fabd26c8043244e861b269ba74e6d7c4abed3502b0b23f7d6 +size 31119 diff --git a/marked/Rel-16/44_series/44318/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/44_series/44318/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1933a87bc77638eb3a9809a0661ac3fa0c7fc80 --- /dev/null +++ b/marked/Rel-16/44_series/44318/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac42f55c79f30f27b98929992947b3ad87271371f24c4787389f49ebde8cf0dd +size 16717 diff --git a/marked/Rel-16/44_series/44318/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/44_series/44318/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07dbb6a2d88e540ba03cb7e13d38142caeb56aff --- /dev/null +++ b/marked/Rel-16/44_series/44318/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83097b83478151f794660982db86efdf4607e8509f5925e1486f56222bf167bd +size 26504 diff --git a/marked/Rel-16/44_series/44318/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/44_series/44318/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bc5c928941823dca950bd6e3e8c6ef16505c313 --- /dev/null +++ b/marked/Rel-16/44_series/44318/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75dac96d724bba5aa1498a7b8daa9ef595b3f964c38edc9975b9442daa5880fc +size 42283 diff --git a/marked/Rel-16/44_series/44318/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-16/44_series/44318/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77ce5fadb4405aa1e30cd84e9f2ffe7ffdbaa113 --- /dev/null +++ b/marked/Rel-16/44_series/44318/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51a007d3da1eb10ffea9eefa8e1e77e34588f8ccc60c2a529fbb5b103755dc3e +size 13318 diff --git a/marked/Rel-16/44_series/44318/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-16/44_series/44318/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e20df166515c21d43fd9c61f1ddafd644f0fedd --- /dev/null +++ b/marked/Rel-16/44_series/44318/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05fa868ce1ef83fd520c9cea09a0aa36eccd5f38cba83f3bd1c90f9afbc5d642 +size 24897 diff --git a/marked/Rel-16/44_series/44318/38a51baf4d5b8857d162e5d9a0645269_img.jpg b/marked/Rel-16/44_series/44318/38a51baf4d5b8857d162e5d9a0645269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e012a0c86a7c6e7b2d2680a724e6a906ee63ddb --- /dev/null +++ b/marked/Rel-16/44_series/44318/38a51baf4d5b8857d162e5d9a0645269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5e9b0993d00610a4517a19b38e710ddff9a671d875dddc42e98673f6090cefb +size 26668 diff --git a/marked/Rel-16/44_series/44318/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-16/44_series/44318/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..089ef7d0f23d531683c8e0ee39f2be98b22bfb03 --- /dev/null +++ b/marked/Rel-16/44_series/44318/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ecaae5b4ec3f63eb2d31c0b88f9af336d673e52ae538747d5e77edac09dba7a +size 19793 diff --git a/marked/Rel-16/44_series/44318/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg b/marked/Rel-16/44_series/44318/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c22f19ea1cacdd8b5d04dfbb3905ccb35a20367 --- /dev/null +++ b/marked/Rel-16/44_series/44318/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc7b6ee96c3b7c8dec296e3c1f9956da4ad0e6a5f9b59fbb906ef9bc7947f900 +size 17856 diff --git a/marked/Rel-16/44_series/44318/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/Rel-16/44_series/44318/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70e7783704a471f07632407d085388887c5cd630 --- /dev/null +++ b/marked/Rel-16/44_series/44318/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5acba91ecb5bb806315c5779ed1bc319761896f2371f92ac816f9f1e760f426 +size 13022 diff --git a/marked/Rel-16/44_series/44318/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg b/marked/Rel-16/44_series/44318/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a57a897f73e9e122d30018c31d7cc74a123577cf --- /dev/null +++ b/marked/Rel-16/44_series/44318/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:759995436a21e98b6dca2441c313e08d7d4a58d286c2c59cb504af2ce985b820 +size 16174 diff --git a/marked/Rel-16/44_series/44318/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-16/44_series/44318/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..118fc1e09274b9e10d24f966addd777490a1a3ab --- /dev/null +++ b/marked/Rel-16/44_series/44318/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:141525fb48f280e8841847eacf2e7f7cc93db0d15a582c48ca695b97f6b7d054 +size 39285 diff --git a/marked/Rel-16/44_series/44318/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/Rel-16/44_series/44318/4842f073775fb1e84d101c02fd74e59e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55744b1fff20342a4c36259a3b7d41eefdedacda --- /dev/null +++ b/marked/Rel-16/44_series/44318/4842f073775fb1e84d101c02fd74e59e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:025acd6da6e5f016a521e31be67fa529319b8cae9a3caef80cbeee0ca1d24e7e +size 26493 diff --git a/marked/Rel-16/44_series/44318/497d7e14540664a2914557cad79f3791_img.jpg b/marked/Rel-16/44_series/44318/497d7e14540664a2914557cad79f3791_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37e1dd9eaaa59b7023e40a7c1a995e05fd20776e --- /dev/null +++ b/marked/Rel-16/44_series/44318/497d7e14540664a2914557cad79f3791_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:661c290559869313edaf6dbbbfbf3ee45978b351c8f4a0bca98b89314da29057 +size 28450 diff --git a/marked/Rel-16/44_series/44318/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg b/marked/Rel-16/44_series/44318/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dc683ca869b3ed84fef58f2acb25606b7d02ee0 --- /dev/null +++ b/marked/Rel-16/44_series/44318/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52ff3446cf83e0399eba44ee41c1c9f98620d1fe48901ed6773d01b9b42e879e +size 13865 diff --git a/marked/Rel-16/44_series/44318/4bb56f4af58f9d5daab52d98c984d8d5_img.jpg b/marked/Rel-16/44_series/44318/4bb56f4af58f9d5daab52d98c984d8d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80293f7e231a9f6e38d608120349b333ebf1b13c --- /dev/null +++ b/marked/Rel-16/44_series/44318/4bb56f4af58f9d5daab52d98c984d8d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5ebe7ab6725ad198bf3b4791846948a35595c92dfbf89e483d32903929f3d5d +size 13424 diff --git a/marked/Rel-16/44_series/44318/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/marked/Rel-16/44_series/44318/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2779060a8e076a9fd935e4d0c41b526ac4819735 --- /dev/null +++ b/marked/Rel-16/44_series/44318/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45316fd89c46ab4297126b3643b5a520beb6fab953c1f967fcfd04ebb0822417 +size 24231 diff --git a/marked/Rel-16/44_series/44318/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/44_series/44318/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b0532b814d0595fca8c1bb8c1a2cb9ed9c84e8e --- /dev/null +++ b/marked/Rel-16/44_series/44318/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39b2fc42af8f6f7871a355bcefde0548468867aaeb9373db484cfba9a0af5403 +size 47024 diff --git a/marked/Rel-16/44_series/44318/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Rel-16/44_series/44318/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7e8829a15a1bb1810d8162f40de33a364db4fe9 --- /dev/null +++ b/marked/Rel-16/44_series/44318/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f0da601b84f89fd016b03dff5ce7caebf5420c676924759d456fda04fbdcc04 +size 24577 diff --git a/marked/Rel-16/44_series/44318/52f68e21acc86c9aaab2f5abc51a9748_img.jpg b/marked/Rel-16/44_series/44318/52f68e21acc86c9aaab2f5abc51a9748_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0cffd3220972f163aa214c97ec14597514e2a85 --- /dev/null +++ b/marked/Rel-16/44_series/44318/52f68e21acc86c9aaab2f5abc51a9748_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d8d5d42c0594ff44c3db8e4c8ec6146d65af2560c208c4a516d4acbaf700e5f +size 42066 diff --git a/marked/Rel-16/44_series/44318/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg b/marked/Rel-16/44_series/44318/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e68364484e0ff5bd642c9137ca8772e481c6b356 --- /dev/null +++ b/marked/Rel-16/44_series/44318/54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96301cec158b3a7ba9eba319bc3c4e1625dc751c28d07949e7bf6e2ccfcba23d +size 20430 diff --git a/marked/Rel-16/44_series/44318/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-16/44_series/44318/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8357fe65fbbb52730c6626c862b93fc59e1a2cc --- /dev/null +++ b/marked/Rel-16/44_series/44318/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d06bdf0743515772efae45f201c34a6f5e75c6c3bbfea433e3e22d5c843e8f4 +size 32065 diff --git a/marked/Rel-16/44_series/44318/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/44_series/44318/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a96f989c45addae21d5975c1f3da18c3a5863b6 --- /dev/null +++ b/marked/Rel-16/44_series/44318/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:541da5a3fc957e888a1fb634a37917d45e6057d76ccc63ab993c86c52a775213 +size 21497 diff --git a/marked/Rel-16/44_series/44318/5dca16cd6224cb81fefbd38274e5eb80_img.jpg b/marked/Rel-16/44_series/44318/5dca16cd6224cb81fefbd38274e5eb80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d8cc4a733c40b13ec0fb5533d454ac63ece5860 --- /dev/null +++ b/marked/Rel-16/44_series/44318/5dca16cd6224cb81fefbd38274e5eb80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd1299ca07a1e5f15351c445ffc1d9f27c98593a6f7dcfb0626df4ab28ffad2e +size 25205 diff --git a/marked/Rel-16/44_series/44318/6116b1a533010c170fc526ec513ba0b8_img.jpg b/marked/Rel-16/44_series/44318/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a74219967c3bef07961cb617e2141748a6db0029 --- /dev/null +++ b/marked/Rel-16/44_series/44318/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8147b16ff709820d402bd11645b9fa5228763aee29eeab1819d881eb9e2d37ea +size 35060 diff --git a/marked/Rel-16/44_series/44318/63d04fb1a19cac79b0f4705d931094e2_img.jpg b/marked/Rel-16/44_series/44318/63d04fb1a19cac79b0f4705d931094e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dba4128be9a563478a0f2b143cfa440f84c7638 --- /dev/null +++ b/marked/Rel-16/44_series/44318/63d04fb1a19cac79b0f4705d931094e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2b6523e968ba5a743a743436bf8089e5831f1d9cffe600281f69437dcf5d3e3 +size 31308 diff --git a/marked/Rel-16/44_series/44318/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/44_series/44318/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48aeaabe46d15a8718d1d850d48cd9767e88d576 --- /dev/null +++ b/marked/Rel-16/44_series/44318/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ba7f2a7cf98940411b8311cb0e9abdc9fdc096fe43fe1002f23c89e223a5c61 +size 27517 diff --git a/marked/Rel-16/44_series/44318/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/44_series/44318/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e9b8a9dac2d8f0b8b5f646d7450254fba614bf9 --- /dev/null +++ b/marked/Rel-16/44_series/44318/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f65b91e094a58af90c87ae85147ab2edf640d9a29bcbc02bccc21031daf7da7 +size 27917 diff --git a/marked/Rel-16/44_series/44318/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/44_series/44318/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a43a77c235f83b66d667af3d8be708129b66e094 --- /dev/null +++ b/marked/Rel-16/44_series/44318/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66222e2a4c4c4b78dd89f6ee6ca6757f2ecbb9502f86fa107da3c364a29f5cce +size 39318 diff --git a/marked/Rel-16/44_series/44318/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-16/44_series/44318/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2df0b0033e59712c39bdc203cd13da974e8c6be --- /dev/null +++ b/marked/Rel-16/44_series/44318/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f9c40b276ed375a71783dd70acee6b857a82176af3dda111b2ec3a0f23f591a +size 40689 diff --git a/marked/Rel-16/44_series/44318/6bc05e56e8453678a84fa6bdba3fd903_img.jpg b/marked/Rel-16/44_series/44318/6bc05e56e8453678a84fa6bdba3fd903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..817859470cc349867e81addb4b30b87a0bc96e3e --- /dev/null +++ b/marked/Rel-16/44_series/44318/6bc05e56e8453678a84fa6bdba3fd903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d61a2b03aebabb6880fac6c042396e834052464bd3b16976307dd02eec006b3 +size 34580 diff --git a/marked/Rel-16/44_series/44318/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/marked/Rel-16/44_series/44318/708e4c9a044ef61f586126676eb2eeb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c353c1041a034bc54e5f0f4dc7f314ea24bd788 --- /dev/null +++ b/marked/Rel-16/44_series/44318/708e4c9a044ef61f586126676eb2eeb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9587c9024fd7a665f1e2158343c579f2fc77c0b2933ed6d276677182bd27580d +size 26299 diff --git a/marked/Rel-16/44_series/44318/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg b/marked/Rel-16/44_series/44318/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce7c48c9d19f6ffd085944be4997646ef898b8af --- /dev/null +++ b/marked/Rel-16/44_series/44318/73da53f7da73c0e2ead71eb1e2f746fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d5cbdd3758eb1f8b2cdff08c2013d9efb462386a79951d8844bcc843738a638 +size 20361 diff --git a/marked/Rel-16/44_series/44318/762a17cd79880dbca172bcbbe9375223_img.jpg b/marked/Rel-16/44_series/44318/762a17cd79880dbca172bcbbe9375223_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37e06c1ada36efe7eabff16a9fe8e0a373e032a2 --- /dev/null +++ b/marked/Rel-16/44_series/44318/762a17cd79880dbca172bcbbe9375223_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:050e82bff867e4d63dc90f887c642f50fcef59324e9cd9f54e020884c58ac5d2 +size 32082 diff --git a/marked/Rel-16/44_series/44318/77542b335b92de8277e86dbe7190f361_img.jpg b/marked/Rel-16/44_series/44318/77542b335b92de8277e86dbe7190f361_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcffa0c3167432b2abcbd482d610298ebff23e51 --- /dev/null +++ b/marked/Rel-16/44_series/44318/77542b335b92de8277e86dbe7190f361_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce4ba7510688a160ba3e5a3627934df17c6fb6a73d085a73253ef52993cecf1d +size 25647 diff --git a/marked/Rel-16/44_series/44318/78de09c382ab51b5c3e87979204228c8_img.jpg b/marked/Rel-16/44_series/44318/78de09c382ab51b5c3e87979204228c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb82f5eb8d7e7b88da66039cf69a4278d845f9dd --- /dev/null +++ b/marked/Rel-16/44_series/44318/78de09c382ab51b5c3e87979204228c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd36ed9b94af2923adc6b1903a177e03f4107b875ef1627db09b507550c4b922 +size 27911 diff --git a/marked/Rel-16/44_series/44318/7913c315e0db8233cb1ac2455e4a0a81_img.jpg b/marked/Rel-16/44_series/44318/7913c315e0db8233cb1ac2455e4a0a81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cd5c6fcb6e4379ec1ab54743948e88f30eb24fa --- /dev/null +++ b/marked/Rel-16/44_series/44318/7913c315e0db8233cb1ac2455e4a0a81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32ba6a0475532cc579c47b1e2b6d6c2cb26ad145779bb905dfff24e8a3f3deb8 +size 30017 diff --git a/marked/Rel-16/44_series/44318/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg b/marked/Rel-16/44_series/44318/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5d27e9023525da225507821d64f290b37193860 --- /dev/null +++ b/marked/Rel-16/44_series/44318/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6ca173aff5bdc5b1788e04b17c1bfa1ac92ae2eafb80999548f926ce3b6e2d4 +size 19185 diff --git a/marked/Rel-16/44_series/44318/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/44_series/44318/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32c93a607619856be4864a61a8d07e239811cdf0 --- /dev/null +++ b/marked/Rel-16/44_series/44318/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab4dd0b126295e4ce7b721bd1ca38f03b999846ca85a3f3ffe96a04154387e51 +size 41176 diff --git a/marked/Rel-16/44_series/44318/802707b774f2d2973b49cea2020e8453_img.jpg b/marked/Rel-16/44_series/44318/802707b774f2d2973b49cea2020e8453_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9809d6f317c57a7a2294f1dfbe0f7210c86dfdb1 --- /dev/null +++ b/marked/Rel-16/44_series/44318/802707b774f2d2973b49cea2020e8453_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7322898871c55fb1a5180a3ca59ce5e0004cc94883da3ee61641a4aa0a047e1 +size 26688 diff --git a/marked/Rel-16/44_series/44318/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/44_series/44318/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6063d977695568a815a746ac666951e964909c2b --- /dev/null +++ b/marked/Rel-16/44_series/44318/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc23fb3cdfa91859a611ae2b46dac2c86bed61b5d82402009fa46c162bb36634 +size 25753 diff --git a/marked/Rel-16/44_series/44318/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Rel-16/44_series/44318/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0661f6d68cbabba64bcae514c940dbb96841fe86 --- /dev/null +++ b/marked/Rel-16/44_series/44318/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:433a864b36b620fd082644d6f350c36b1ecc41b43f0724aa6a0a267c779ab1d5 +size 24507 diff --git a/marked/Rel-16/44_series/44318/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-16/44_series/44318/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58c9e5e46983e25f908fc45ba9fc9ebb24d49f21 --- /dev/null +++ b/marked/Rel-16/44_series/44318/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed9f480d231a1c291ffdf33f845c64be9309bd50397fc3379cf0f1a98eea9501 +size 14212 diff --git a/marked/Rel-16/44_series/44318/85b53faf49a839f512153285c78fbbdb_img.jpg b/marked/Rel-16/44_series/44318/85b53faf49a839f512153285c78fbbdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a456700db9fede989be95b5a03656be60819d13f --- /dev/null +++ b/marked/Rel-16/44_series/44318/85b53faf49a839f512153285c78fbbdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c392e530ce17d52da24c5aff0efc966a8f2195a4acbecf8d2f2f6f260b95d1cf +size 40495 diff --git a/marked/Rel-16/44_series/44318/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-16/44_series/44318/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..597908aea96ef7c730fe27c218206b4bb542ee00 --- /dev/null +++ b/marked/Rel-16/44_series/44318/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b641be08ff5ab0e6df7bd85e752dee4f3682d9d016d23fdafa255883efec3a8 +size 13496 diff --git a/marked/Rel-16/44_series/44318/86f61404a19a384d06a7b0b2c4e6937a_img.jpg b/marked/Rel-16/44_series/44318/86f61404a19a384d06a7b0b2c4e6937a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e0fdecc123a4081c08722612117105b4afe88da --- /dev/null +++ b/marked/Rel-16/44_series/44318/86f61404a19a384d06a7b0b2c4e6937a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1668a29b62e3ab757846b8515a558adbdb881f89f1d31a990242126208db22dd +size 38420 diff --git a/marked/Rel-16/44_series/44318/91c33f8e1713989e8192322ec2d1212b_img.jpg b/marked/Rel-16/44_series/44318/91c33f8e1713989e8192322ec2d1212b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1c919e42872be1a5cfdfea07a263b25f257d6a7 --- /dev/null +++ b/marked/Rel-16/44_series/44318/91c33f8e1713989e8192322ec2d1212b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6be63fb2a269d19f6d5b8da681857c9dbba68c322d8f29cc75db5af457c20210 +size 17068 diff --git a/marked/Rel-16/44_series/44318/9874e3ac6f14360133f8e1674f79824f_img.jpg b/marked/Rel-16/44_series/44318/9874e3ac6f14360133f8e1674f79824f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e56e24061aabb09f4e3aa04a6fa78e3f089f1621 --- /dev/null +++ b/marked/Rel-16/44_series/44318/9874e3ac6f14360133f8e1674f79824f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:530252f365447963e00190dab7adcd6ecc7903c01c20bab23e79fd570d08ea62 +size 127390 diff --git a/marked/Rel-16/44_series/44318/98a45dd7d474e067b7533cc966c11e95_img.jpg b/marked/Rel-16/44_series/44318/98a45dd7d474e067b7533cc966c11e95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0afd467657939cb2f4f76700589f835a7c142eb --- /dev/null +++ b/marked/Rel-16/44_series/44318/98a45dd7d474e067b7533cc966c11e95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d2d4664e46c87a3ed014da3ccf703293707a07f5a8f2db7f7416b31ac211d8e +size 15828 diff --git a/marked/Rel-16/44_series/44318/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/44_series/44318/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e46b14020e0aa311c6fe803e15f3cc176bfe5510 --- /dev/null +++ b/marked/Rel-16/44_series/44318/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a072b0e14ef2d989d2164cf1860311d596eb7bdab45edb18fab4b0dba6ad060 +size 13819 diff --git a/marked/Rel-16/44_series/44318/9ddc2a6358c46a4717ceaed7183b6a46_img.jpg b/marked/Rel-16/44_series/44318/9ddc2a6358c46a4717ceaed7183b6a46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3891cb1c20f0b5a0cab046f87d70f0fd2a45f1b5 --- /dev/null +++ b/marked/Rel-16/44_series/44318/9ddc2a6358c46a4717ceaed7183b6a46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54a1de6e7a85f67240fb9fcf6b5c79f64aa0b541c9902c9ac27d76b697e27103 +size 21311 diff --git a/marked/Rel-16/44_series/44318/9eba62b255ea4757497c72582d0fa54e_img.jpg b/marked/Rel-16/44_series/44318/9eba62b255ea4757497c72582d0fa54e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f8c904d50164d2d6d3590ffd8b602a5fe2dc613 --- /dev/null +++ b/marked/Rel-16/44_series/44318/9eba62b255ea4757497c72582d0fa54e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acbb77f1fdfa9f5a09bece0f5d3c932f9501dcf0d77a57b3e9af11334e33159b +size 20795 diff --git a/marked/Rel-16/44_series/44318/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Rel-16/44_series/44318/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c2750b8dc0600ceda145352177e812333b4b367 --- /dev/null +++ b/marked/Rel-16/44_series/44318/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:640d1000dd9e39b5b6da6e3a0a5fd54b85342507fd52294354aadd71ff7784bf +size 16043 diff --git a/marked/Rel-16/44_series/44318/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/44_series/44318/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1bb72e9967f245f4ed47de9a4b926cf296f97da --- /dev/null +++ b/marked/Rel-16/44_series/44318/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6b58c2eaea0caf29b538cf8399737a531f9829dc95640177f9a4714db045ed9 +size 31416 diff --git a/marked/Rel-16/44_series/44318/a2586540d49d5665489c8b5a273f86d3_img.jpg b/marked/Rel-16/44_series/44318/a2586540d49d5665489c8b5a273f86d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4543d8a9b5ee4f3b7430e39ecad091388ef69a48 --- /dev/null +++ b/marked/Rel-16/44_series/44318/a2586540d49d5665489c8b5a273f86d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4dbcae9a910ae684aa463ef84e3ff52695e10eda75df0b83f4b7c60f0878835 +size 17261 diff --git a/marked/Rel-16/44_series/44318/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-16/44_series/44318/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27ccb42f6d0025903b27c5e74a435a76bf1fa697 --- /dev/null +++ b/marked/Rel-16/44_series/44318/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:495243f0b79e2722d9b6cf5fc9c35d3c66f7992cab1e607ba4e2fa1574c03aab +size 19461 diff --git a/marked/Rel-16/44_series/44318/ae375ead8aa673286b534e079e9a8533_img.jpg b/marked/Rel-16/44_series/44318/ae375ead8aa673286b534e079e9a8533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df765f39a373e9c339724769d1390579d388ed22 --- /dev/null +++ b/marked/Rel-16/44_series/44318/ae375ead8aa673286b534e079e9a8533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5fa7cddcfa2e343f96d449465d37a77b4f08a51a993ef44046d027237ac8b9a +size 37645 diff --git a/marked/Rel-16/44_series/44318/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg b/marked/Rel-16/44_series/44318/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bea2a3c57a2dff190a3e25af36778ae9c58d9f7 --- /dev/null +++ b/marked/Rel-16/44_series/44318/ae9b822eaafef535b7a0fbb97a7c713b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6772a6422fd1f59c0ad0593ab5d9d7731f4b104454ecb3d29f9c423fe3b2c4e4 +size 28182 diff --git a/marked/Rel-16/44_series/44318/aff7d03f930d62115362cc026be487ed_img.jpg b/marked/Rel-16/44_series/44318/aff7d03f930d62115362cc026be487ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a4d722ca9a6c912cce834103d6d6c594bccf7a6 --- /dev/null +++ b/marked/Rel-16/44_series/44318/aff7d03f930d62115362cc026be487ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e08d8bb14925526d503f5a091dae9b78f32a9650062962999826a834d9c8dc8a +size 20008 diff --git a/marked/Rel-16/44_series/44318/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-16/44_series/44318/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f73ddb61b2f07e397ad2747487dbd0eeccecc2fe --- /dev/null +++ b/marked/Rel-16/44_series/44318/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5054df385b2f0b3bea3217834b0b409b3c0f714f28c40328cc5568bd7610a9cb +size 25751 diff --git a/marked/Rel-16/44_series/44318/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/marked/Rel-16/44_series/44318/bb3063a33c89b248574f64b6d8dfc404_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05fb0a160a47a5b621b859bad04609ade0799ce4 --- /dev/null +++ b/marked/Rel-16/44_series/44318/bb3063a33c89b248574f64b6d8dfc404_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7dbc6550e2605057b3612eb76a96d61bb9146ae4efdf49a34eb116e29c5f5ab +size 19546 diff --git a/marked/Rel-16/44_series/44318/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/Rel-16/44_series/44318/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cc0682372a5f95196a2d2b264c1e68f3cf7f6c9 --- /dev/null +++ b/marked/Rel-16/44_series/44318/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44df7bf17f27f4dd8014f80b742ad46083cffeda744e3168312a6b2fe1064d82 +size 26594 diff --git a/marked/Rel-16/44_series/44318/bd57a547bec253d4179e5c4491c53dbb_img.jpg b/marked/Rel-16/44_series/44318/bd57a547bec253d4179e5c4491c53dbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..375484585a56241495dd920875f028ddcd63cb1c --- /dev/null +++ b/marked/Rel-16/44_series/44318/bd57a547bec253d4179e5c4491c53dbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc3e5520dbaf0a04b24b5b747796b770ca5ea4b6c4a1d130a45b2c12f6b801a9 +size 20318 diff --git a/marked/Rel-16/44_series/44318/bde7d337de2e08bf548b40ef6a35ae33_img.jpg b/marked/Rel-16/44_series/44318/bde7d337de2e08bf548b40ef6a35ae33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c7489d73347586293417a177f84decf011f55a1 --- /dev/null +++ b/marked/Rel-16/44_series/44318/bde7d337de2e08bf548b40ef6a35ae33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91b389fb7f7366bdd7da4ee8e29cd0ef4ed214be755513e284f5c0accd91b7a1 +size 23129 diff --git a/marked/Rel-16/44_series/44318/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-16/44_series/44318/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a879801d14bbf78aaa6daae5efe77f0acc43503 --- /dev/null +++ b/marked/Rel-16/44_series/44318/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:885bf6ecf553bd76c07843b593279fc5537fb2c74b62e688f5379cf248271569 +size 20636 diff --git a/marked/Rel-16/44_series/44318/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg b/marked/Rel-16/44_series/44318/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3d0ad7544831dd06c9310473d0c7968a14d65b9 --- /dev/null +++ b/marked/Rel-16/44_series/44318/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:733b454193b9558647492d746808e15e61bddb4d10c443544aa5c76c9c4bae82 +size 37307 diff --git a/marked/Rel-16/44_series/44318/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/Rel-16/44_series/44318/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0c9b8274538c4dad2b2992a6a2ebcbb23cd44bb --- /dev/null +++ b/marked/Rel-16/44_series/44318/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58e2ca34182e63b81a225ed127da10bfd36af6c2cfe9e138be622e462b0a50d7 +size 35039 diff --git a/marked/Rel-16/44_series/44318/c6e0b9030f9fb81435eaf9cb71532614_img.jpg b/marked/Rel-16/44_series/44318/c6e0b9030f9fb81435eaf9cb71532614_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99fc703cea5571e1871ce1ae0f2d0dc48f4d0b89 --- /dev/null +++ b/marked/Rel-16/44_series/44318/c6e0b9030f9fb81435eaf9cb71532614_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a6f4b6c74c59fc6312892e570a5f74fe42e078621c335c54d596200d5cb724b +size 17982 diff --git a/marked/Rel-16/44_series/44318/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg b/marked/Rel-16/44_series/44318/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3244d76e54b91932aa2d558fa3867b9e2b6de739 --- /dev/null +++ b/marked/Rel-16/44_series/44318/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:563cc8b4d1c358e012e0c192260adbe9bafebd4a428c6c9c9c12d28f2b6d3faf +size 40002 diff --git a/marked/Rel-16/44_series/44318/c9c3a80790995f4e292bcb457d3e1686_img.jpg b/marked/Rel-16/44_series/44318/c9c3a80790995f4e292bcb457d3e1686_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7b48f3934d32c4d623098df040335a27fe7ddfe --- /dev/null +++ b/marked/Rel-16/44_series/44318/c9c3a80790995f4e292bcb457d3e1686_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f643d20d87ad67fba947ed0ff0e9902d11b8f877fb29171d2f24ad155b611bf8 +size 29551 diff --git a/marked/Rel-16/44_series/44318/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg b/marked/Rel-16/44_series/44318/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a81fded2f4f3d2086125596e7c277d9a2545543 --- /dev/null +++ b/marked/Rel-16/44_series/44318/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eae9adb76a313e237e022e6d0129542eb899c620a8f376dc07eeaa692cff353f +size 29131 diff --git a/marked/Rel-16/44_series/44318/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-16/44_series/44318/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e42aeb296886ce154c8bde83ae7ee779a3e44c6a --- /dev/null +++ b/marked/Rel-16/44_series/44318/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37b7d7853a60ae30065477ae8100476acf4a04e081d5708cec0d556a164ef6ee +size 23711 diff --git a/marked/Rel-16/44_series/44318/d116934392360da963e91d840d1e45a8_img.jpg b/marked/Rel-16/44_series/44318/d116934392360da963e91d840d1e45a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d51e72262a8aa666a1f03f136bc64bf3a9f8bb5 --- /dev/null +++ b/marked/Rel-16/44_series/44318/d116934392360da963e91d840d1e45a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2786d96dc3eab8e3fc95142c4cf030fd9828736284012bcde8620d5bb1fffca +size 12360 diff --git a/marked/Rel-16/44_series/44318/d48a71a2e72db63c807a4c4ea8d82d2e_img.jpg b/marked/Rel-16/44_series/44318/d48a71a2e72db63c807a4c4ea8d82d2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45ee25186f1fc62da98c69dafa1962c45f361a12 --- /dev/null +++ b/marked/Rel-16/44_series/44318/d48a71a2e72db63c807a4c4ea8d82d2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:830d07f86dac2ac8287f6bd6933b129ec08ea5c8dabbae5e31c4626e1e73ad8a +size 26343 diff --git a/marked/Rel-16/44_series/44318/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-16/44_series/44318/d7948c38a18636aefecdd95388196460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de2c2f620141f07a90d8f89c089b052e79d8b4a7 --- /dev/null +++ b/marked/Rel-16/44_series/44318/d7948c38a18636aefecdd95388196460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49f69a7cb83d5efb8c9e6950e67d766bc89c81fcb0cd8d424bb0e043d059ddd8 +size 36670 diff --git a/marked/Rel-16/44_series/44318/d9b929d9bc834c1b396d8319d61ce1cf_img.jpg b/marked/Rel-16/44_series/44318/d9b929d9bc834c1b396d8319d61ce1cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..822c5ef7c6af3205339b2da2b914548607a82ff7 --- /dev/null +++ b/marked/Rel-16/44_series/44318/d9b929d9bc834c1b396d8319d61ce1cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59a175f3286581eecb5cf490c0ea87a209827286016f9a031841fc40d9cb14c6 +size 24603 diff --git a/marked/Rel-16/44_series/44318/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/44_series/44318/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d30f58381b16db0edff6c780865447aafbc89ef --- /dev/null +++ b/marked/Rel-16/44_series/44318/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2267aea0108c56ec37dbcc8027d709928d3d9e35d05ae2640b294b2eb4a7a84e +size 25625 diff --git a/marked/Rel-16/44_series/44318/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Rel-16/44_series/44318/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..222227650e5e1c5c42f6415ab8da31a2c92e8e8d --- /dev/null +++ b/marked/Rel-16/44_series/44318/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:790b6b90a5772dddce3c0fed04bf4caa2bbf834489c730a28d92437e186c0664 +size 27026 diff --git a/marked/Rel-16/44_series/44318/e04013719a8410d8f37a6bd8fae3f45b_img.jpg b/marked/Rel-16/44_series/44318/e04013719a8410d8f37a6bd8fae3f45b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9169abf197df459bf4faa7068ff7eae92ab53f8b --- /dev/null +++ b/marked/Rel-16/44_series/44318/e04013719a8410d8f37a6bd8fae3f45b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:432515c60285ca7a1e873b0723bc9bddc26b078b22d167e0a9b7c25349646f3a +size 11623 diff --git a/marked/Rel-16/44_series/44318/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Rel-16/44_series/44318/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb54e338cfe6a43266eeaf008917dc06df55bdd --- /dev/null +++ b/marked/Rel-16/44_series/44318/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d93ecfbb897df5d7f38c6cb03d9cbd6b6dd512f781810d28f1a3d03fc6c8ca1 +size 32165 diff --git a/marked/Rel-16/44_series/44318/ec035e97a11ce40541dec6d88d54c7cb_img.jpg b/marked/Rel-16/44_series/44318/ec035e97a11ce40541dec6d88d54c7cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77892579d0d68eb1ccf06026898a3f091660692d --- /dev/null +++ b/marked/Rel-16/44_series/44318/ec035e97a11ce40541dec6d88d54c7cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5628bdc406e1b6c388e1b80e690b730eb3b73d0b74f3ee57b40abade909f0acf +size 28659 diff --git a/marked/Rel-16/44_series/44318/f36118fd962bd69a26082021de657b71_img.jpg b/marked/Rel-16/44_series/44318/f36118fd962bd69a26082021de657b71_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d55190b794a6784267ca2d432ae0f42e918d5c68 --- /dev/null +++ b/marked/Rel-16/44_series/44318/f36118fd962bd69a26082021de657b71_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c91c493215341e8d3c376b2ed9f67a807ab45ed4a7b31ba633b2391c2ff3a7b +size 27776 diff --git a/marked/Rel-16/44_series/44318/f5698523df298c80a0c6b5d4ca657993_img.jpg b/marked/Rel-16/44_series/44318/f5698523df298c80a0c6b5d4ca657993_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a091e3f9e6d912f142ce277e6bc6ed1a590ea0f0 --- /dev/null +++ b/marked/Rel-16/44_series/44318/f5698523df298c80a0c6b5d4ca657993_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7473825092fca756f09456bd01e97b731fc26ec09b922752ffcc588ceebb77c5 +size 92078 diff --git a/marked/Rel-16/44_series/44318/f7d969388c4f7e30cd04a061314bfa0e_img.jpg b/marked/Rel-16/44_series/44318/f7d969388c4f7e30cd04a061314bfa0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1a14897353fdde46ade38c5489e379b2c99bb32 --- /dev/null +++ b/marked/Rel-16/44_series/44318/f7d969388c4f7e30cd04a061314bfa0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3bbf140be76fe449e5db7661c30853817bfda440e7619dea3b84fa9919f9582 +size 15799 diff --git a/marked/Rel-16/44_series/44318/f8d508872d762c83336443cfd20c5412_img.jpg b/marked/Rel-16/44_series/44318/f8d508872d762c83336443cfd20c5412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4817b453472887d2604edea1db6926746b92fe44 --- /dev/null +++ b/marked/Rel-16/44_series/44318/f8d508872d762c83336443cfd20c5412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96134980919e72b8f8450516c027b63c3f5b110a009f3483c43346ee7e0a6e75 +size 76072 diff --git a/marked/Rel-16/44_series/44318/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/44_series/44318/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91f9beeeffec6e2773becf0a9e35ba4b9b26c828 --- /dev/null +++ b/marked/Rel-16/44_series/44318/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3757979eff15744f5421aa3e132a0dad13afa003ece147abf110ab3e02353da3 +size 9462 diff --git a/marked/Rel-16/44_series/44318/raw.md b/marked/Rel-16/44_series/44318/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..97445e71364fe12daff465cd3885b8b36919df24 --- /dev/null +++ b/marked/Rel-16/44_series/44318/raw.md @@ -0,0 +1,10608 @@ +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|----------------------------------------------------------------|----| +| Foreword ..... | 16 | +| 1 Scope..... | 17 | +| 2 References..... | 17 | +| 3 Definitions, symbols and abbreviations..... | 19 | +| 3.1 Definitions..... | 19 | +| 3.2 Symbols..... | 19 | +| 3.3 Abbreviations ..... | 19 | +| 4 Elementary procedures for handling of secure connection..... | 21 | +| 4.1 General ..... | 21 | +| 4.2 Establishment of the secure connection ..... | 21 | +| 4.2.1 General ..... | 21 | +| 4.2.2 Identities ..... | 22 | +| 4.2.3 Crypto negotiation ..... | 22 | +| 4.2.4 NAT traversal ..... | 23 | +| 4.2.5 Certificate Handling and Authentication..... | 23 | +| 4.2.6 Abnormal cases ..... | 23 | +| 4.3 EAP-SIM authentication ..... | 23 | +| 4.3.1 General ..... | 23 | +| 4.3.2 EAP-SIM Identity ..... | 24 | +| 4.3.3 EAP-SIM Fast Re-authentication ..... | 24 | +| 4.3.4 Abnormal cases ..... | 24 | +| 4.4 EAP-AKA authentication..... | 24 | +| 4.4.1 General ..... | 24 | +| 4.4.2 EAP-AKA Identity ..... | 24 | +| 4.4.3 EAP-AKA Fast Re-authentication ..... | 24 | +| 4.4.4 Abnormal cases ..... | 25 | +| 4.5 Release of the secure connection ..... | 25 | +| 5 GA-RC elementary procedures for GANC Discovery ..... | 25 | +| 5.1 Purpose of the Discovery Procedure ..... | 25 | +| 5.2 Discovery procedure..... | 25 | +| 5.3 Discovery Request initiation by the MS..... | 25 | +| 5.4 Discovery Request processing by the network..... | 26 | +| 5.4.1 Discovery accepted..... | 27 | +| 5.4.2 Discovery rejected ..... | 27 | +| 5.5 Discovery response processing by the MS..... | 27 | +| 5.5.1 Discovery accepted..... | 27 | +| 5.5.2 Discovery rejected ..... | 27 | +| 5.6 Abnormal cases ..... | 28 | +| 5.6.1 TU3901 expiry..... | 28 | +| 5.6.2 Lower layer failure in the MS..... | 28 | +| 5.6.3 TU3902 expiry..... | 28 | +| 5.6.4 TU3903 expiry..... | 28 | +| 6 GA-RC elementary procedures for Registration..... | 29 | +| 6.1 Purpose of GAN Registration ..... | 29 | +| 6.2 Registration procedure ..... | 29 | +| 6.2.1 Registration initiation by the MS ..... | 29 | +| 6.2.2 Registration processing by the network ..... | 31 | +| 6.2.2.1 General..... | 31 | +| 6.2.2.2 Registration accepted..... | 31 | +| 6.2.2.3 Registration redirected..... | 31 | +| 6.2.2.4 Registration rejected ..... | 32 | +| 6.2.3 Registration response processing by the MS..... | 32 | +| 6.2.3.1 Registration accepted..... | 32 | +| 6.2.3.2 Registration redirected..... | 34 | + +| | | | +|---------|-------------------------------------------------------------------------|----| +| 6.2.3.3 | Registration rejected ..... | 35 | +| 6.2.4 | Abnormal cases ..... | 36 | +| 6.2.4.1 | TU3904 expiry ..... | 36 | +| 6.2.4.2 | Lower layer failure in the MS ..... | 36 | +| 6.2.4.3 | TU3905 expiry ..... | 36 | +| 6.2.4.4 | TU3907 expiry ..... | 36 | +| 6.2.4.5 | Registration Failure ..... | 37 | +| 6.2.4.6 | GAN mode selection related failures ..... | 37 | +| 6.3 | Registration Update procedure ..... | 37 | +| 6.3.1 | Register Update initiation by the MS ..... | 38 | +| 6.3.2 | Register Update processing by the network ..... | 39 | +| 6.3.2.1 | Register Update Accepted ..... | 39 | +| 6.3.2.2 | Register Update Rejected ..... | 39 | +| 6.3.2.3 | Register Update results in redirection ..... | 39 | +| 6.3.3 | Register Update Response handling in the MS ..... | 39 | +| 6.3.3.1 | Register Update Rejected ..... | 39 | +| 6.3.3.2 | Register Update results in redirection ..... | 39 | +| 6.3.4 | Register Update initiation by the network ..... | 39 | +| 6.3.5 | Register Update handling in the MS ..... | 40 | +| 6.4 | MS deregistration ..... | 40 | +| 6.4.1 | Deregistration initiated by the MS ..... | 40 | +| 6.4.2 | Reception of GA-RC DEREGISTER by GANC ..... | 40 | +| 6.4.3 | Deregistration initiated by the network ..... | 40 | +| 6.4.4 | Reception of GA-RC DEREGISTER by MS ..... | 40 | +| 6.5 | Keep alive mechanism and TU3906 handling ..... | 42 | +| 6.6 | MS Initiated Synchronization after TCP connection reestablishment ..... | 42 | +| 6.6.1 | Initiation of the Synchronization Procedure by the MS ..... | 43 | +| 6.6.2 | Processing of the Synchronization Information message by the GANC ..... | 43 | +| 6.7 | Transmission of Cell Broadcast Information ..... | 43 | +| 7 | GA-CSR elementary procedures ..... | 43 | +| 7.1 | GA-CSR Connection establishment ..... | 43 | +| 7.1.1 | Initiation of GA-CSR connection establishment by the MS ..... | 44 | +| 7.1.2 | Reception of GA-CSR REQUEST by GANC ..... | 44 | +| 7.1.2.1 | GA-CSR connection establishment request accepted ..... | 44 | +| 7.1.2.2 | GA-CSR connection establishment request rejected ..... | 45 | +| 7.1.3 | GA-CSR connection establishment response handling in the MS ..... | 45 | +| 7.1.3.1 | GA-CSR connection establishment request accepted ..... | 45 | +| 7.1.3.2 | GA-CSR connection establishment request rejected ..... | 45 | +| 7.1.4 | Failure cases ..... | 45 | +| 7.1.4.1 | Timer TU3908 expiry ..... | 45 | +| 7.2 | Upper layer message transmission ..... | 45 | +| 7.2.1 | Upper layer message forwarding by the MS ..... | 46 | +| 7.2.2 | Reception of GA-CSR UPLINK DIRECT TRANSFER by GANC ..... | 46 | +| 7.2.3 | Upper layer message forwarding by the GANC ..... | 46 | +| 7.2.4 | Reception of GA-CSR DOWNLINK DIRECT TRANSFER by the MS ..... | 46 | +| 7.2.4.1 | Invalid GA-CSR DOWNLINK DIRECT TRANSFER ..... | 47 | +| 7.3 | Paging for CS domain ..... | 47 | +| 7.3.1 | Initiation of Paging ..... | 47 | +| 7.3.2 | Reception of GA-CSR PAGING REQUEST by the MS ..... | 47 | +| 7.3.3 | Reception of GA-CSR PAGING RESPONSE by the GANC ..... | 48 | +| 7.3.4 | Abnormal Cases ..... | 48 | +| 7.4 | Traffic Channel assignment ..... | 48 | +| 7.4.1 | Initiation of Channel Assignment ..... | 48 | +| 7.4.2 | Reception of GA-CSR ACTIVATE CHANNEL by MS ..... | 48 | +| 7.4.3 | Reception of GA-CSR ACTIVATE CHANNEL ACK by GANC ..... | 49 | +| 7.4.4 | Reception of GA-CSR ACTIVATE CHANNEL COMPLETE by MS ..... | 49 | +| 7.4.5 | Failure to establish channel by MS ..... | 50 | +| 7.5 | Release of GA-CSR ..... | 50 | +| 7.5.1 | Initiation of GA-CSR connection release by MS ..... | 50 | +| 7.5.2 | Reception of GA-CSR CLEAR REQUEST by GANC ..... | 50 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------|----| +| 7.5.3 | Initiation of GA-CSR connection release by GANC ..... | 50 | +| 7.5.4 | Reception of GA-CSR RELEASE by MS..... | 51 | +| 7.5.5 | Failure cases ..... | 51 | +| 7.5.5.1 | Timer TU3909 expiry ..... | 51 | +| 7.6 | Classmark Indication..... | 52 | +| 7.6.1 | Initiation of classmark interrogation by GANC ..... | 52 | +| 7.6.2 | Transmission of classmark information by MS..... | 52 | +| 7.7 | CS handover to GAN A/Gb mode..... | 53 | +| 7.7.2 | Reception of GA-CSR HANDOVER ACCESS by the GANC ..... | 53 | +| 7.7.3 | Successful completion of the CS handover to GAN A/Gb mode ..... | 53 | +| 7.7.4 | Reception of GA-CSR HANDOVER COMPLETE by the GANC ..... | 54 | +| 7.7.5 | MS fails to complete requested handover..... | 54 | +| 7.8 | CS handover from GAN A/Gb mode..... | 54 | +| 7.8.1 | Initiation ..... | 55 | +| 7.8.2 | Reception of GA-CSR HANDOVER INFORMATION by the GANC ..... | 55 | +| 7.8.3 | Reception of GA-CSR HANDOVER COMMAND by the MS ..... | 55 | +| 7.8.4 | Successful completion of the CS handover from GAN A/Gb mode..... | 55 | +| 7.8.5 | MS fails to complete requested handover..... | 56 | +| 7.8.6 | Reception of GA-CSR HANDOVER FAILURE by the GANC ..... | 56 | +| 7.8.7 | Abnormal Cases..... | 56 | +| 7.9 | Ciphering configuration procedure ..... | 56 | +| 7.9.1 | Ciphering configuration initiation ..... | 57 | +| 7.9.2 | Ciphering configuration completion..... | 57 | +| 7.10 | Channel mode modify procedure ..... | 57 | +| 7.10.1 | Normal channel mode modify procedure..... | 58 | +| 7.10.1.1 | Initiation of the channel mode modify procedure..... | 58 | +| 7.10.1.2 | Completion of channel mode modify procedure ..... | 58 | +| 7.10.1.3 | Abnormal cases..... | 58 | +| 8 | GA-PSR elementary procedures ..... | 59 | +| 8.1 | GA-PSR Transport Channel (GA-PSR TC) Overview ..... | 59 | +| 8.2 | MS Initiated GA-PSR Transport Channel (GA-PSR TC) Activation..... | 59 | +| 8.2.1 | Initiation of the GA-PSR TC Activation by the MS ..... | 59 | +| 8.2.2 | Processing of the GA-PSR TC Activation Request by the GANC ..... | 59 | +| 8.2.3 | Processing of the GA-PSR TC Activation Acknowledgment by the MS ..... | 60 | +| 8.2.4 | Abnormal Cases..... | 60 | +| 8.2.4.1 | GA-PSR TC Activation Collision..... | 60 | +| 8.2.4.2 | Timer TU4002 Expires during GA-PSR TC Activation ..... | 60 | +| 8.2.4.3 | GANC Receives Duplicate GA-PSR TC Activation Request..... | 60 | +| 8.2.4.4 | GANC Rejects GA-PSR TC Activation ..... | 60 | +| 8.2.4.5 | MS Aborts GA-PSR TC Activation due to Lower Layer Failure..... | 61 | +| 8.3 | Network Initiated GA-PSR Transport Channel (GA-PSR TC) Activation..... | 61 | +| 8.3.1 | Initiation of the GA-PSR TC Activation by the GANC..... | 61 | +| 8.3.2 | Processing of the GA-PSR TC Activation Request by the MS..... | 61 | +| 8.3.3 | Processing of the GA-PSR TC Activation Acknowledgment by the GANC..... | 62 | +| 8.3.4 | Abnormal Cases..... | 62 | +| 8.3.4.1 | GA-PSR TC Activation Collision..... | 62 | +| 8.3.4.2 | MS Rejects GA-PSR TC Activation when the GPRS Service is suspended..... | 62 | +| 8.3.4.3 | MS Receives GA-PSR TC Activation Request while GA-PSR TC active ..... | 62 | +| 8.4 | MS Initiated Deactivation of GA-PSR Transport Channel..... | 62 | +| 8.4.1 | GA-PSR TC Deactivation Initiation by the MS ..... | 63 | +| 8.4.2 | Processing of GA-PSR TC Deactivation Request by the GANC..... | 63 | +| 8.4.3 | Processing of GA-PSR TC Deactivation Acknowledgment by the MS..... | 63 | +| 8.4.4 | Abnormal Cases..... | 63 | +| 8.4.4.1 | Timer TU4002 Expires during GA-PSR TC Deactivation..... | 63 | +| 8.4.4.2 | GANC Rejects GA-PSR TC Deactivation..... | 63 | +| 8.4.4.3 | Uplink User Data Transfer is initiated while GA-PSR TC Deactivation is in Progress..... | 64 | +| 8.4.4.4 | Downlink User Data Transfer is received while the GA-PSR TC Deactivation is in Progress ..... | 64 | +| 8.4.4.5 | Unexpected GA-PSR-DEACTIVATE-UTC-ACK response ..... | 64 | +| 8.4.4.6 | Unexpected GA-PSR-ACTIVATE-UTC-REQ ..... | 64 | +| 8.4.4.7 | MS Aborts GA-PSR TC Deactivation due to Lower Layer Failure ..... | 64 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------------|----| +| 8.5 | GANC Initiated Deactivation of GA-PSR Transport Channel ..... | 64 | +| 8.5.1 | GA-PSR TC Deactivation Initiation by the GANC ..... | 65 | +| 8.5.2 | Processing of GA-PSR TC Deactivation Request by the MS ..... | 65 | +| 8.5.3 | Processing of GA-PSR TC Deactivation Acknowledgment by the GANC ..... | 65 | +| 8.5.4 | Abnormal Cases..... | 65 | +| 8.5.4.1 | MS Rejects GA-PSR TC Deactivation ..... | 65 | +| 8.5.4.2 | Uplink User Data Transfer is received while GA-PSR TC Deactivation is in Progress ..... | 65 | +| 8.5.4.3 | Downlink User Data Transfer is initiated while the GA-PSR TC Deactivation is in Progress ..... | 65 | +| 8.6 | Implicit Deactivation of GA-PSR Transport Channel ..... | 65 | +| 8.7 | GA-PSR GPRS User Data Transport..... | 66 | +| 8.7.1 | MS Initiates Uplink GPRS User Data Transfer..... | 66 | +| 8.7.2 | Processing of the Uplink GPRS User Data Message by the GANC ..... | 66 | +| 8.7.3 | GANC Initiates Downlink GPRS User Data Transfer ..... | 66 | +| 8.7.4 | Processing of the Downlink GPRS User Data Message by the MS ..... | 66 | +| 8.7.5 | Abnormal Cases..... | 67 | +| 8.7.5.1 | GANC Receives an Uplink User Data Message while the GA-PSR TC Activation Procedure is in progress..... | 67 | +| 8.7.5.2 | GANC Receives an Uplink User Data Message and the GA-PSR TC is not active ..... | 67 | +| 8.7.5.3 | Handling of out-of-sequence packets ..... | 67 | +| 8.7.5.4 | MS Receives a Downlink User Data Message while the GA-PSR TC Activation Procedure is in progress ..... | 67 | +| 8.7.5.5 | Uplink User Data Transfer Failed due to Lower Layer Failure ..... | 67 | +| 8.8 | GA-PSR GPRS Signalling and SMS Messages Transport ..... | 67 | +| 8.8.1 | MS Initiates Uplink GPRS Signalling/SMS Message Transfer ..... | 68 | +| 8.8.2 | Processing of the Uplink GA-PSR DATA Message by the GANC ..... | 68 | +| 8.8.3 | GANC Initiates Downlink GA-PSR DATA Transfer..... | 68 | +| 8.8.4 | Processing of the Downlink GA-PSR DATA Message by the MS..... | 68 | +| 8.8.5 | Abnormal Cases..... | 68 | +| 8.8.5.1 | Downlink or Uplink User Data Transfer Failed due to Lower Layer Failure ..... | 68 | +| 8.9 | Packet paging for packet service..... | 68 | +| 8.9.1 | PS Paging Request Processing by the GANC ..... | 68 | +| 8.9.2 | PS Paging Request Processed by the MS ..... | 69 | +| 8.9.3 | Processing of the PS Paging Response by the GANC ..... | 69 | +| 8.10 | GPRS Suspend Procedure ..... | 69 | +| 8.10.1 | GPRS Suspension Initiation by the MS..... | 69 | +| 8.10.2 | GPRS Suspend Request Processing by the GANC ..... | 69 | +| 8.11 | MS Initiated Downlink Flow Control ..... | 69 | +| 8.11.1 | Initiation of the Downlink Flow Control by the MS ..... | 70 | +| 8.11.2 | Processing of the Downlink Flow Control Request by the GANC ..... | 70 | +| 8.11.3 | Processing of the TU4003 Timer Expiry by the MS ..... | 70 | +| 8.12 | Uplink Flow Control ..... | 70 | +| 8.12.1 | Initiation of the Uplink Flow Control by the GANC ..... | 71 | +| 8.12.2 | Processing of the Uplink Flow Control Request by the MS ..... | 71 | +| 8.12.3 | Resetting of the Uplink Flow Control Condition by the GANC ..... | 71 | +| 8.12.4 | Abnormal Cases..... | 71 | +| 8.12.4.1 | GA-PSR TC Deactivation is in Progress ..... | 71 | +| 8.13 | PS handover to GAN A/Gb mode ..... | 71 | +| 8.13.1 | Initiation ..... | 71 | +| 8.13.2 | Successful completion of the PS handover to GAN A/Gb mode ..... | 71 | +| 8.13.3 | Abnormal Cases..... | 72 | +| 8.14 | PS handover from GAN A/Gb mode ..... | 72 | +| 8.14.1 | Initiation ..... | 72 | +| 8.14.2 | Reception of GA-PSR HANDOVER INFORMATION by the GANC ..... | 73 | +| 8.14.3 | Reception of GA-PSR HANDOVER CONTINUE by the MS..... | 73 | +| 8.14.4 | Reception of GA-PSR HANDOVER COMMAND by the MS ..... | 74 | +| 8.14.5 | Successful completion of the PS Handover from GAN A/Gb mode ..... | 74 | +| 8.14.6 | Abnormal Cases..... | 75 | +| 8.14.7 | Reception of GA-PSR HANDOVER FAILURE by the GANC ..... | 75 | +| 8a | GA-RRC elementary procedures ..... | 75 | +| 8a.1 | GA-RRC connection establishment ..... | 75 | + +| | | | +|----------|-----------------------------------------------------------------------|----| +| 8a.1.1 | Initiation of GA-RRC connection establishment by the MS..... | 76 | +| 8a.1.2 | Reception of GA-RRC REQUEST by GANC ..... | 76 | +| 8a.1.2.1 | GA-RRC connection establishment request accepted ..... | 76 | +| 8a.1.2.2 | GA-RRC connection establishment request rejected..... | 76 | +| 8a.1.3 | GA-RRC connection establishment response handling in the MS..... | 77 | +| 8a.1.3.1 | GA-RRC connection establishment request accepted ..... | 77 | +| 8a.1.3.2 | GA-RRC connection establishment request rejected..... | 77 | +| 8a.1.4 | Failure cases ..... | 77 | +| 8a.1.4.1 | Timer TU5908 expiry ..... | 77 | +| 8a.2 | Upper layer message transmission..... | 77 | +| 8a.2.1 | Initial upper layer message forwarding by the MS..... | 78 | +| 8a.2.2 | Reception of GA-RRC INITIAL DIRECT TRANSFER by GANC..... | 78 | +| 8a.2.3 | Subsequent upper layer message forwarding by the MS..... | 78 | +| 8a.2.4 | Reception of GA-RRC UPLINK DIRECT TRANSFER by GANC..... | 78 | +| 8a.2.5 | Upper layer message forwarding by the GANC..... | 79 | +| 8a.2.6 | Reception of GA-RRC DOWNLINK DIRECT TRANSFER by the MS ..... | 79 | +| 8a.2.6.1 | Invalid GA-RRC DOWNLINK DIRECT TRANSFER ..... | 79 | +| 8a.3 | Paging..... | 79 | +| 8a.3.1 | Initiation of paging ..... | 80 | +| 8a.3.2 | Reception of GA-RRC PAGING REQUEST by the MS..... | 80 | +| 8a.3.3 | Abnormal Cases..... | 80 | +| 8a.4 | Transport channel activation ..... | 80 | +| 8a.4.1 | Circuit transport channel activation..... | 81 | +| 8a.4.1.1 | Initiation of circuit transport channel activation..... | 81 | +| 8a.4.1.2 | Reception of GA-RRC ACTIVATE CHANNEL (CS domain) by the MS ..... | 81 | +| 8a.4.1.3 | Reception of GA-RRC ACTIVATE CHANNEL ACK (CS domain) by GANC ..... | 82 | +| 8a.4.1.4 | Reception of GA-RRC ACTIVATE CHANNEL COMPLETE (CS domain) by MS ..... | 82 | +| 8a.4.2 | Packet transport channel activation..... | 83 | +| 8a.4.2.1 | Initiation of packet transport channel activation..... | 83 | +| 8a.4.2.2 | Reception of GA-RRC ACTIVATE CHANNEL (PS domain) by the MS..... | 83 | +| 8a.4.2.3 | Reception of GA-RRC ACTIVATE CHANNEL ACK (PS domain) by GANC ..... | 83 | +| 8a.4.2.4 | Reception of GA-RRC ACTIVATE CHANNEL COMPLETE (PS domain) by MS ..... | 84 | +| 8a.5 | GA-RRC connection release ..... | 84 | +| 8a.5.1 | GA-RRC connection release request by MS ..... | 84 | +| 8a.5.2 | Reception of GA-RRC RELEASE REQUEST by GANC..... | 84 | +| 8a.5.3 | Initiation of GA-RRC connection release by GANC ..... | 84 | +| 8a.5.4 | Reception of GA-RRC RELEASE by MS ..... | 85 | +| 8a.5.5 | Failure cases ..... | 85 | +| 8a.5.5.1 | Timer TU5909 expiry ..... | 85 | +| 8a.6 | Security mode control ..... | 85 | +| 8a.6.1 | Security mode control initiation ..... | 86 | +| 8a.6.2 | Security mode control completion..... | 86 | +| 8a.7 | Transport channel modification ..... | 87 | +| 8a.7.1 | Circuit transport channel modification..... | 87 | +| 8a.7.1.1 | Initiation of circuit transport channel modification ..... | 87 | +| 8a.7.1.2 | Reception of GA-RRC MODIFY CHANNEL (CS domain) by the MS..... | 87 | +| 8a.7.1.3 | Reception of GA-RRC MODIFY CHANNEL ACK (CS domain) by GANC..... | 88 | +| 8a.7.2 | Packet transport channel modification ..... | 88 | +| 8a.7.2.1 | Initiation of packet transport channel modification ..... | 88 | +| 8a.7.2.2 | Reception of GA-RRC MODIFY CHANNEL (PS domain) by the MS ..... | 88 | +| 8a.7.2.3 | Reception of GA-RRC MODIFY CHANNEL ACK (PS domain) by GANC ..... | 89 | +| 8a.8 | Transport channel deactivation ..... | 89 | +| 8a.8.1 | Transport channel deactivation request by MS ..... | 89 | +| 8a.8.2 | Reception of GA-RRC DEACTIVATE CHANNEL REQUEST by GANC..... | 89 | +| 8a.8.3 | Initiation of transport channel deactivation by GANC..... | 89 | +| 8a.8.4 | Reception of GA-RRC DEACTIVATE CHANNEL by MS ..... | 90 | +| 8a.8.5 | Failure cases ..... | 90 | +| 8a.8.5.1 | Timer TU5002 expiry ..... | 90 | +| 8a.9 | PS domain user plane data transfer ..... | 90 | +| 8a.9.1 | MS initiates uplink PS domain user plane data transfer..... | 91 | +| 8a.9.2 | Processing of the received GA-RRC PDU message by the GANC ..... | 91 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------|-----| +| 8a.9.3 | GANC initiates downlink PS domain user plane data transfer ..... | 91 | +| 8a.9.4 | Processing of the received GA-RRC PDU message by the MS..... | 91 | +| 8a.9.5 | Abnormal Cases..... | 91 | +| 8a.9.5.1 | TU4001 timer expiry ..... | 91 | +| 8a.9.5.2 | GANC receives a GA-RRC PDU message while the GA-RRC PTC activation procedure is in progress..... | 91 | +| 8a.9.5.3 | GANC receives a GA-RRC PDU message and the GA-RRC PTC is not active ..... | 92 | +| 8a.9.5.4 | Handling of out-of-sequence packets ..... | 92 | +| 8a.9.5.5 | MS receives a GA-RRC PDU message while the GA-RRC PTC activation procedure is in progress..... | 92 | +| 8a.9.5.6 | Uplink PS domain user data transfer failed due to lower layer failure..... | 92 | +| 8a.10 | Handover to GAN Iu mode ..... | 92 | +| 8a.10.1 | Reception of GA-RRC RELOCATION REQUEST by the MS ..... | 92 | +| 8a.10.2 | Reception of GA-RRC RELOCATION REQUEST ACK by the GANC ..... | 94 | +| 8a.10.3 | Normal execution ..... | 94 | +| 8a.10.4 | Reception of GA-RRC RELOCATION COMPLETE by the GANC..... | 95 | +| 8a.10.5 | Exception case: No IMSI in CS domain Relocation Request ..... | 95 | +| 8a.11 | Handover from GAN Iu mode ..... | 96 | +| 8a.11.1 | Initiation ..... | 96 | +| 8a.11.2 | Reception of GA-RRC RELOCATION INFORMATION by the GANC..... | 97 | +| 8a.11.3 | Reception of GA-RRC RELOCATION COMMAND by the MS..... | 97 | +| 8a.11.4 | Successful completion of the handover from GAN Iu mode ..... | 97 | +| 8a.11.5 | MS fails to complete requested handover..... | 97 | +| 8a.11.6 | Reception of GA-RRC RELOCATION FAILURE by the GANC..... | 98 | +| 8a.11.7 | Abnormal Cases..... | 98 | +| 9 | Error handling procedures..... | 98 | +| 9.1 | General ..... | 98 | +| 9.2 | Message too short..... | 98 | +| 9.3 | Invalid Message Header..... | 98 | +| 9.4 | Invalid Information Elements..... | 99 | +| 9.5 | Handling of lower layer faults..... | 99 | +| 9.6 | Out of sequence IEs..... | 99 | +| 10 | Message functional definitions and contents ..... | 100 | +| 10.1 | GA-RC and GA-CSR Messages ..... | 100 | +| 10.1.1 | (void) ..... | 101 | +| 10.1.2 | GA-RC DISCOVERY REQUEST ..... | 101 | +| 10.1.2.1 | AP Radio Identity ..... | 102 | +| 10.1.2.2 | GERAN Cell Identity..... | 102 | +| 10.1.2.3 | Location Area Identification..... | 102 | +| 10.1.2.4 | Routing Area Code ..... | 102 | +| 10.1.2.5 | Register Reject Cause..... | 102 | +| 10.1.2.6 | Redirection Counter..... | 102 | +| 10.1.2.7 | Default GANC-SEGW IP address..... | 102 | +| 10.1.2.8 | Default GANC-SEGW FQDN..... | 102 | +| 10.1.2.9 | Default GANC IP address..... | 103 | +| 10.1.2.10 | Default GANC FQDN ..... | 103 | +| 10.1.2.11 | 3G Cell Identity ..... | 103 | +| 10.1.2.12 | Tracking Area Identity..... | 103 | +| 10.1.2.13 | E-UTRAN Camping Indicator..... | 103 | +| 10.1.2.14 | E-UTRAN Cell Identity..... | 103 | +| 10.1.3 | GA-RC DISCOVERY ACCEPT ..... | 103 | +| 10.1.3.1 | Default GANC-SEGW IP address..... | 104 | +| 10.1.3.2 | Default GANC-SEGW FQDN..... | 104 | +| 10.1.3.3 | Default GANC IP address..... | 104 | +| 10.1.3.4 | Default GANC FQDN ..... | 104 | +| 10.1.4 | GA-RC DISCOVERY REJECT..... | 104 | +| 10.1.4.1 | TU3902 Timer ..... | 105 | +| 10.1.5 | GA-RC REGISTER REQUEST..... | 105 | +| 10.1.5.1 | GERAN Cell Identity..... | 107 | + +| | | | +|-----------|-------------------------------------|-----| +| 10.1.5.2 | Location Area Identification..... | 107 | +| 10.1.5.3 | Routing Area Code ..... | 107 | +| 10.1.5.4 | Register Reject Cause ..... | 107 | +| 10.1.5.5 | Redirection Counter..... | 107 | +| 10.1.5.6 | Last GANC-SEGW IP address ..... | 108 | +| 10.1.5.7 | Last GANC-SEGW FQDN..... | 108 | +| 10.1.5.8 | Last GANC IP address..... | 108 | +| 10.1.5.9 | Last GANC FQDN ..... | 108 | +| 10.1.5.10 | AP Radio Identity ..... | 108 | +| 10.1.5.11 | AP Service Name..... | 108 | +| 10.1.5.12 | Registration Indicators..... | 108 | +| 10.1.5.13 | GAN PLMN List ..... | 108 | +| 10.1.5.14 | 3G Cell Identity ..... | 108 | +| 10.1.5.15 | 3G UARFCN ..... | 108 | +| 10.1.5.16 | 3G Security Capability..... | 108 | +| 10.1.5.17 | Tracking Area Identity..... | 109 | +| 10.1.5.18 | E-UTRAN Camping Indicator..... | 109 | +| 10.1.5.19 | E-UTRAN Cell Identity..... | 109 | +| 10.1.6 | GA-RC REGISTER ACCEPT ..... | 109 | +| 10.1.6.1 | TU4001 and TU4003 ..... | 110 | +| 10.1.6.2 | GAN Service Zone Information ..... | 110 | +| 10.1.6.3 | Serving GANC Table Indicator ..... | 111 | +| 10.1.6.4 | GAN Band ..... | 111 | +| 10.1.6.5 | TU4004 Timer ..... | 111 | +| 10.1.6.6 | GAN Mode Indicator ..... | 111 | +| 10.1.6.7 | GAN Cell Description ..... | 111 | +| 10.1.6.8 | GAN Iu Mode Cell Description..... | 111 | +| 10.1.7 | GA-RC REGISTER REDIRECT ..... | 111 | +| 10.1.7.1 | Serving GANC-SEGW IP address ..... | 112 | +| 10.1.7.2 | Serving GANC-SEGW FQDN ..... | 112 | +| 10.1.7.3 | Serving GANC IP address ..... | 112 | +| 10.1.7.4 | Serving GANC FQDN..... | 112 | +| 10.1.7.5 | Serving GANC TCP port number..... | 112 | +| 10.1.7.5a | Serving GANC Table Indicator ..... | 112 | +| 10.1.7.6 | GAN PLMN List ..... | 113 | +| 10.1.8 | GA-RC REGISTER REJECT ..... | 113 | +| 10.1.8.1 | TU3907 Timer ..... | 113 | +| 10.1.8.2 | Location Black List indicator ..... | 113 | +| 10.1.8.3 | Location Area Identification..... | 113 | +| 10.1.9 | GA-RC DEREGISTER ..... | 113 | +| 10.1.9.1 | Location Black List indicator ..... | 114 | +| 10.1.9.2 | Location Area Identification..... | 114 | +| 10.1.9.3 | TU3907 Timer ..... | 114 | +| 10.1.10 | GA-RC REGISTER UPDATE UPLINK ..... | 114 | +| 10.1.10.1 | GERAN Cell Identity..... | 115 | +| 10.1.10.2 | Location Area Identification..... | 115 | +| 10.1.10.3 | Routing Area Code ..... | 116 | +| 10.1.10.4 | 3G Cell Identity ..... | 116 | +| 10.1.10.5 | AP Service Name..... | 116 | +| 10.1.10.6 | 3G UARFCN ..... | 116 | +| 10.1.10.7 | Tracking Area Identity..... | 116 | +| 10.1.10.8 | E-UTRAN Camping Indicator..... | 117 | +| 10.1.10.9 | E-UTRAN Cell Identity..... | 117 | +| 10.1.11 | GA-RC REGISTER UPDATE DOWNLINK..... | 117 | +| 10.1.11.1 | GAN Service Zone Information ..... | 118 | +| 10.1.11.2 | GAN Cell Description ..... | 118 | +| 10.1.11.3 | GAN Iu Mode Cell Description..... | 118 | +| 10.1.12 | GA-CSR REQUEST ..... | 118 | +| 10.1.13 | GA-CSR REQUEST ACCEPT ..... | 118 | +| 10.1.14 | GA-RC KEEP ALIVE..... | 118 | +| 10.1.14a | GA-RC CELL BROADCAST INFO ..... | 119 | + +| | | | +|-----------|-------------------------------------------------------|-----| +| 10.1.15 | GA-CSR ACTIVATE CHANNEL ..... | 119 | +| 10.1.15.1 | Payload Type ..... | 120 | +| 10.1.15.2 | Multi-rate Configuration ..... | 120 | +| 10.1.15.3 | RTP Redundancy Configuration ..... | 120 | +| 10.1.15.4 | RTCP UDP Port ..... | 120 | +| 10.1.15.5 | Bandwidth-efficient Mode Indicator ..... | 120 | +| 10.1.16 | GA-CSR ACTIVATE CHANNEL ACK ..... | 121 | +| 10.1.16.1 | Payload Type ..... | 121 | +| 10.1.16.2 | RTCP UDP Port ..... | 121 | +| 10.1.16.3 | Sample Size ..... | 121 | +| 10.1.17 | GA-CSR ACTIVATE CHANNEL FAILURE ..... | 121 | +| 10.1.18 | GA-CSR ACTIVATE CHANNEL COMPLETE ..... | 122 | +| 10.1.19 | GA-CSR RELEASE ..... | 122 | +| 10.1.20 | GA-CSR RELEASE COMPLETE ..... | 123 | +| 10.1.21 | GA-CSR PAGING REQUEST ..... | 123 | +| 10.1.22 | GA-CSR PAGING RESPONSE ..... | 123 | +| 10.1.23 | GA-CSR UPLINK DIRECT TRANSFER ..... | 124 | +| 10.1.24 | GA-CSR REQUEST REJECT ..... | 124 | +| 10.1.25 | GA-CSR DOWNLINK DIRECT TRANSFER ..... | 125 | +| 10.1.26 | GA-CSR CLASSMARK ENQUIRY ..... | 125 | +| 10.1.27 | GA-CSR CLASSMARK CHANGE ..... | 126 | +| 10.1.27.1 | Additional Mobile Station Classmark Information ..... | 126 | +| 10.1.28 | GA-CSR STATUS ..... | 126 | +| 10.1.29 | GA-CSR HANDOVER ACCESS ..... | 126 | +| 10.1.29.1 | Handover To GAN Command ..... | 127 | +| 10.1.30 | GA-CSR HANDOVER COMPLETE ..... | 127 | +| 10.1.31 | GA-CSR UPLINK QUALITY INDICATION ..... | 127 | +| 10.1.32 | GA-CSR HANDOVER INFORMATION ..... | 128 | +| 10.1.32.1 | GERAN Cell Identifier List ..... | 128 | +| 10.1.32.2 | GERAN Received Signal Level List ..... | 128 | +| 10.1.32.3 | UTRAN Cell Identifier List ..... | 128 | +| 10.1.32.4 | UTRAN Received Signal Level List ..... | 128 | +| 10.1.33 | GA-CSR HANDOVER COMMAND ..... | 129 | +| 10.1.33.1 | Handover From GAN Command ..... | 129 | +| 10.1.34 | GA-CSR HANDOVER FAILURE ..... | 129 | +| 10.1.34.1 | RR Cause ..... | 129 | +| 10.1.35 | GA-CSR CIPHERING MODE COMMAND ..... | 129 | +| 10.1.36 | GA-CSR CIPHERING MODE COMPLETE ..... | 130 | +| 10.1.36.1 | Mobile Equipment Identity ..... | 130 | +| 10.1.37 | GA-CSR CLEAR REQUEST ..... | 130 | +| 10.1.38 | GA-CSR GPRS SUSPENSION REQUEST ..... | 131 | +| 10.1.39 | GA-RC SYNCHRONIZATION INFORMATION ..... | 131 | +| 10.1.40 | GA-CSR CHANNEL MODE MODIFY ..... | 132 | +| 10.1.40.1 | Channel Mode ..... | 132 | +| 10.1.40.2 | Multi-rate Configuration ..... | 132 | +| 10.1.40.3 | RTP Redundancy Configuration ..... | 133 | +| 10.1.40.4 | Sample Size ..... | 133 | +| 10.1.40.5 | IP Address ..... | 133 | +| 10.1.40.6 | RTP UDP Port ..... | 133 | +| 10.1.40.7 | RTCP UDP Port ..... | 133 | +| 10.1.41 | GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE ..... | 133 | +| 10.1.41.1 | Channel Mode ..... | 133 | +| 10.1.41.2 | Sample Size ..... | 134 | +| 10.1.42 | GA-CSR UTRAN CLASSMARK CHANGE ..... | 134 | +| 10.2 | GA-PSR Messages ..... | 134 | +| 10.2.1 | GA-PSR-ACTIVATE-UTC-REQ ..... | 134 | +| 10.2.1.1 | IP address for GPRS user data transport ..... | 135 | +| 10.2.1.2 | UDP Port for GPRS user data transport ..... | 135 | +| 10.2.2 | GA-PSR-ACTIVATE-UTC-ACK ..... | 135 | +| 10.2.2.1 | IP address for GPRS user data transport ..... | 136 | +| 10.2.2.2 | UDP Port for GPRS user data transport ..... | 136 | + +| | | | +|-----------|------------------------------------------|-----| +| 10.2.3 | GA-PSR-DEACTIVATE-UTC-REQ..... | 136 | +| 10.2.4 | GA-PSR-DEACTIVATE-UTC-ACK..... | 136 | +| 10.2.5 | GA-PSR-DATA ..... | 137 | +| 10.2.5.1 | Requested QoS..... | 137 | +| 10.2.5.2 | Packet Flow Identifier..... | 137 | +| 10.2.6 | GA-PSR-UNITDATA ..... | 137 | +| 10.2.6.1 | Requested QoS..... | 138 | +| 10.2.6.2 | Packet Flow Identifier..... | 138 | +| 10.2.7 | GA-PSR-PS-PAGE ..... | 138 | +| 10.2.7.1 | Mobile Identity ..... | 138 | +| 10.2.8 | GA-PSR-UFC-REQ ..... | 138 | +| 10.2.8.1 | Packet Flow Identifier..... | 139 | +| 10.2.8.2 | Reset Indicator ..... | 139 | +| 10.2.9 | GA-PSR-DFC-REQ ..... | 139 | +| 10.2.9.1 | Packet Flow Identifier..... | 139 | +| 10.2.10 | GA-PSR STATUS..... | 139 | +| 10.2.11 | GA-PSR HANDOVER COMPLETE ..... | 140 | +| 10.2.12 | GA-PSR UPLINK QUALITY INDICATION ..... | 140 | +| 10.2.13 | GA-PSR HANDOVER INFORMATION ..... | 141 | +| 10.2.13.1 | GERAN Cell Identifier List..... | 141 | +| 10.2.13.2 | GERAN Received Signal Level List ..... | 141 | +| 10.2.13.3 | UTRAN Cell Identifier List..... | 141 | +| 10.2.13.4 | UTRAN Received Signal Level List ..... | 141 | +| 10.2.14 | GA-PSR HANDOVER COMMAND ..... | 141 | +| 10.2.14.1 | PS Handover to GERAN Command..... | 142 | +| 10.2.14.2 | PS Handover to UTRAN Command..... | 142 | +| 10.2.14.3 | PS Handover to GERAN PSI..... | 142 | +| 10.2.14.4 | PS Handover to GERAN SI..... | 142 | +| 10.2.15 | GA-PSR HANDOVER CONTINUE ..... | 142 | +| 10.2.16 | GA-PSR HANDOVER FAILURE..... | 143 | +| 10.3 | GA-RRC control plane messages..... | 143 | +| 10.3.1 | GA-RRC REQUEST ..... | 144 | +| 10.3.2 | GA-RRC REQUEST ACCEPT ..... | 144 | +| 10.3.3 | GA-RRC REQUEST REJECT ..... | 146 | +| 10.3.4 | GA-RRC RELEASE REQUEST ..... | 146 | +| 10.3.5 | GA-RRC RELEASE ..... | 147 | +| 10.3.6 | GA-RRC RELEASE COMPLETE ..... | 147 | +| 10.3.7 | GA-RRC PAGING REQUEST ..... | 148 | +| 10.3.8 | GA-RRC ACTIVATE CHANNEL ..... | 148 | +| 10.3.8.1 | CTC Activation List..... | 148 | +| 10.3.8.2 | PTC Activation List..... | 148 | +| 10.3.9 | GA-RRC ACTIVATE CHANNEL ACK ..... | 149 | +| 10.3.9.1 | CTC Activation Ack List..... | 149 | +| 10.3.9.2 | PTC Activation Ack List ..... | 149 | +| 10.3.10 | GA-RRC ACTIVATE CHANNEL COMPLETE ..... | 149 | +| 10.3.11 | GA-RRC MODIFY CHANNEL ..... | 150 | +| 10.3.11.1 | CTC Modification List..... | 150 | +| 10.3.11.2 | PTC Modification List..... | 150 | +| 10.3.12 | GA-RRC MODIFY CHANNEL ACK..... | 150 | +| 10.3.12.1 | CTC Modification Ack List..... | 151 | +| 10.3.12.2 | PTC Modification Ack List ..... | 151 | +| 10.3.13 | GA-RRC DEACTIVATE CHANNEL REQUEST ..... | 152 | +| 10.3.14 | GA-RRC DEACTIVATE CHANNEL..... | 152 | +| 10.3.15 | GA-RRC DEACTIVATE CHANNEL COMPLETE ..... | 152 | +| 10.3.16 | GA-RRC SECURITY MODE COMMAND ..... | 153 | +| 10.3.17 | GA-RRC SECURITY MODE COMPLETE..... | 153 | +| 10.3.18 | GA-RRC INITIAL DIRECT TRANSFER ..... | 154 | +| 10.3.19 | GA-RRC UPLINK DIRECT TRANSFER ..... | 154 | +| 10.3.20 | GA-RRC DOWNLINK DIRECT TRANSFER ..... | 156 | +| 10.3.21 | GA-RRC RELOCATION INFORMATION ..... | 157 | +| 10.3.21.1 | GERAN Cell Identifier List..... | 157 | + +| | | | +|-----------|--------------------------------------------------------------|-----| +| 10.3.21.2 | GERAN Received Signal Level List ..... | 157 | +| 10.3.21.3 | UTRAN Cell Identifier List ..... | 158 | +| 10.3.21.4 | UTRAN Received Signal Level List ..... | 158 | +| 10.3.21.5 | Mobile Station Classmark 2 ..... | 158 | +| 10.3.21.6 | Mobile Station Classmark 3 ..... | 158 | +| 10.3.21.7 | MS Radio Access Capability ..... | 158 | +| 10.3.21.8 | UTRAN Classmark ..... | 158 | +| 10.3.22 | GA-RRC RELOCATION COMMAND ..... | 158 | +| 10.3.22.1 | UTRAN RRC Message ..... | 159 | +| 10.3.22.2 | SRNS Relocation Info ..... | 159 | +| 10.3.23 | GA-RRC RELOCATION ACCESS ..... | 159 | +| 10.3.23.1 | UTRAN RRC Message ..... | 160 | +| 10.3.24 | GA-RRC RELOCATION COMPLETE ..... | 160 | +| 10.3.25 | GA-RRC RELOCATION FAILURE ..... | 160 | +| 10.3.26 | GA-RRC RELOCATION REQUEST ..... | 161 | +| 10.3.26.1 | CTC Activation List ..... | 161 | +| 10.3.26.2 | PTC Activation List ..... | 161 | +| 10.3.27 | GA-RRC RELOCATION REQUEST ACK ..... | 161 | +| 10.3.27.1 | CTC Activation Ack List ..... | 162 | +| 10.3.27.2 | PTC Activation Ack List ..... | 162 | +| 10.3.28 | GA-RRC UPLINK QUALITY INDICATION ..... | 163 | +| 10.3.29 | GA-RRC STATUS ..... | 163 | +| 10.4 | GA-RRC PS user plane messages ..... | 163 | +| 10.4.1 | GA-RRC PDU ..... | 164 | +| 11 | General message format and information elements coding ..... | 164 | +| 11.1 | Message coding principles ..... | 164 | +| 11.1.1 | GA-RC and GA-CSR message header information elements ..... | 164 | +| 11.1.1.1 | Length Indicator (LI) ..... | 165 | +| 11.1.1.2 | Protocol Discriminator (PD) ..... | 165 | +| 11.1.1.3 | Skip Indicator ..... | 166 | +| 11.1.1.4 | Message Type ..... | 166 | +| 11.1.2 | GA-PSR message header information elements over TCP ..... | 167 | +| 11.1.2.1 | GA-PSR Message Type ..... | 168 | +| 11.1.2.2 | Temporary Logical Link Identity (TLLI) ..... | 168 | +| 11.1.3 | GA-PSR message header information elements over UDP ..... | 168 | +| 11.1.3.1 | GA-PSR Message Type ..... | 168 | +| 11.1.3.2 | Temporary Logical Link Identity (TLLI) ..... | 169 | +| 11.1.3.3 | Sequence Number ..... | 169 | +| 11.1.3a | GA-RRC message header information elements over TCP ..... | 169 | +| 11.1.3a.1 | GA-RRC Message Type ..... | 169 | +| 11.1.3b | GA-RRC message header over UDP ..... | 170 | +| 11.1.3b.1 | GA-RRC PTC Message Type ..... | 172 | +| 11.1.3b.2 | GA-RRC Sequence Number Handling ..... | 172 | +| 11.1.4 | Information Element Coding principles ..... | 172 | +| 11.1.5 | Network Byte order ..... | 173 | +| 11.2 | IE Type and Identifiers ..... | 174 | +| 11.2.1 | Mobile Identity ..... | 176 | +| 11.2.2 | GAN Release Indicator ..... | 176 | +| 11.2.3 | Access Identity ..... | 176 | +| 11.2.4 | GERAN Cell Identity ..... | 177 | +| 11.2.5 | Location Area Identification ..... | 177 | +| 11.2.6 | GERAN/UTRAN coverage Indicator ..... | 177 | +| 11.2.7 | GAN Classmark ..... | 178 | +| 11.2.8 | Geographical Location ..... | 179 | +| 11.2.9 | IP Address ..... | 180 | +| 11.2.10 | Fully Qualified Domain/Host Name (FQDN) ..... | 180 | +| 11.2.11 | Redirection Counter ..... | 181 | +| 11.2.12 | Discovery Reject Cause ..... | 181 | +| 11.2.13 | GAN Cell Description ..... | 181 | +| 11.2.14 | GAN Control Channel Description ..... | 182 | + +| | | | +|----------|----------------------------------------|-----| +| 11.2.15 | Cell Identifier List ..... | 184 | +| 11.2.16 | TU3907 Timer ..... | 184 | +| 11.2.17 | GSM RR/UTRAN RRC State ..... | 185 | +| 11.2.18 | Routing Area Identification ..... | 185 | +| 11.2.19 | GAN Band ..... | 185 | +| 11.2.20 | GAN State ..... | 186 | +| 11.2.21 | Register Reject Cause ..... | 187 | +| 11.2.22 | TU3906 Timer ..... | 188 | +| 11.2.23 | TU3910 Timer ..... | 188 | +| 11.2.24 | TU3902 Timer ..... | 188 | +| 11.2.25 | Communication Port Identity ..... | 189 | +| 11.2.26 | L3 Message ..... | 189 | +| 11.2.27 | Channel Mode ..... | 189 | +| 11.2.28 | Mobile Station Classmark 2 ..... | 190 | +| 11.2.29 | RR Cause ..... | 190 | +| 11.2.30 | Cipher Mode Setting ..... | 190 | +| 11.2.31 | GPRS Resumption ..... | 191 | +| 11.2.32 | Handover From GAN Command ..... | 191 | +| 11.2.33 | UL Quality Indication ..... | 191 | +| 11.2.34 | TLLI ..... | 191 | +| 11.2.35 | Packet Flow Identifier ..... | 192 | +| 11.2.36 | Suspension Cause ..... | 192 | +| 11.2.37 | TU3920 Timer ..... | 192 | +| 11.2.38 | QoS ..... | 193 | +| 11.2.39 | GA-PSR Cause ..... | 193 | +| 11.2.40 | User Data Rate ..... | 194 | +| 11.2.41 | Routing Area Code ..... | 194 | +| 11.2.42 | AP Location ..... | 195 | +| 11.2.43 | TU4001 Timer ..... | 195 | +| 11.2.44 | Location Status ..... | 195 | +| 11.2.45 | Cipher Response ..... | 196 | +| 11.2.46 | Ciphering Command RAND ..... | 196 | +| 11.2.47 | Ciphering Command MAC ..... | 196 | +| 11.2.48 | Ciphering Key Sequence Number ..... | 196 | +| 11.2.49 | SAPI ID ..... | 197 | +| 11.2.50 | Establishment Cause ..... | 197 | +| 11.2.51 | Channel Needed ..... | 198 | +| 11.2.52 | PDU in Error ..... | 198 | +| 11.2.53 | Sample Size ..... | 199 | +| 11.2.54 | Payload Type ..... | 199 | +| 11.2.55 | Multirate Configuration ..... | 199 | +| 11.2.56 | Mobile Station Classmark 3 ..... | 200 | +| 11.2.57 | LLC-PDU ..... | 200 | +| 11.2.58 | Location Black List indicator ..... | 201 | +| 11.2.59 | Reset Indicator ..... | 201 | +| 11.2.60 | TU4003 Timer ..... | 201 | +| 11.2.61 | AP Service Name ..... | 202 | +| 11.2.62 | GAN Service Zone Information ..... | 202 | +| 11.2.63 | RTP Redundancy Configuration ..... | 203 | +| 11.2.64 | UTRAN Classmark ..... | 204 | +| 11.2.65 | Classmark Enquiry Mask ..... | 204 | +| 11.2.66 | UTRAN Cell Identifier List ..... | 205 | +| 11.2.67 | Serving GANC table indicator ..... | 206 | +| 11.2.68 | Registration indicators ..... | 206 | +| 11.2.69 | GAN PLMN List ..... | 206 | +| 11.2.70 | GERAN Received Signal Level List ..... | 208 | +| 11.2.70b | UTRAN Received Signal Level List ..... | 209 | +| 11.2.71 | Required GAN Services ..... | 210 | +| 11.2.72 | Broadcast Container ..... | 210 | +| 11.2.73 | 3G Cell Identity ..... | 210 | +| 11.2.74 | PS Handover to GERAN Command ..... | 211 | + +| | | | +|-------------------------------|----------------------------------------------------|------------| +| 11.2.75 | PS Handover to UTRAN Command ..... | 211 | +| 11.2.76 | PS Handover to GERAN PSI ..... | 211 | +| 11.2.77 | PS Handover to GERAN SI ..... | 212 | +| 11.2.78 | TU4004 Timer ..... | 212 | +| 11.2.79 | GAN Mode Indicator ..... | 213 | +| 11.2.80 | CN Domain Identity ..... | 213 | +| 11.2.81 | GAN Iu Mode Cell Description ..... | 213 | +| 11.2.82 | 3G UARFCN ..... | 214 | +| 11.2.83 | RAB ID ..... | 214 | +| 11.2.84 | RAB ID List ..... | 214 | +| 11.2.85 | GA-RRC Establishment Cause ..... | 215 | +| 11.2.86 | GA-RRC Cause ..... | 215 | +| 11.2.87 | GA-RRC Paging Cause ..... | 216 | +| 11.2.88 | Intra Domain NAS Node Selector ..... | 216 | +| 11.2.89 | CTC Activation List ..... | 217 | +| 11.2.90 | CTC Description ..... | 217 | +| 11.2.91 | CTC Activation Ack List ..... | 219 | +| 11.2.92 | CTC Activation Ack Description ..... | 221 | +| 11.2.93 | CTC Modification List ..... | 222 | +| 11.2.94 | CTC Modification Ack List ..... | 222 | +| 11.2.95 | CTC Modification Ack Description ..... | 222 | +| 11.2.96 | PTC Activation List ..... | 224 | +| 11.2.97 | PTC Description ..... | 224 | +| 11.2.98 | PTC Activation Ack List ..... | 225 | +| 11.2.99 | PTC Activation Ack Description ..... | 225 | +| 11.2.100 | PTC Modification List ..... | 226 | +| 11.2.101 | PTC Modification Ack List ..... | 227 | +| 11.2.102 | PTC Modification Ack Description ..... | 227 | +| 11.2.103 | RAB Configuration ..... | 229 | +| 11.2.104 | Multi-rate Configuration 2 ..... | 232 | +| 11.2.105 | Selected Integrity Protection Algorithm ..... | 233 | +| 11.2.106 | Selected Encryption Algorithm ..... | 233 | +| 11.2.107 | CN Domains to Handover ..... | 234 | +| 11.2.108 | 3G Security Capability ..... | 234 | +| 11.2.109 | NAS Synchronisation Indicator ..... | 234 | +| 11.2.110 | TEID ..... | 235 | +| 11.2.111 | UTRAN RRC Message ..... | 235 | +| 11.2.112 | MS Radio Access Capability ..... | 235 | +| 11.2.113 | Handover Reporting Control ..... | 236 | +| 11.2.114 | Tracking Area Identity ..... | 236 | +| 11.2.115 | E-UTRAN Cell Identity ..... | 236 | +| 11.2.116 | E-UTRAN Camping Indicator ..... | 237 | +| 11.2.117 | Bandwidth-efficient Mode Indicator ..... | 237 | +| 12 | List of system parameters ..... | 237 | +| 12.1 | Timers and counters ..... | 237 | +| 12.1.1 | Timers on the mobile station side ..... | 237 | +| 12.1.2 | Timers on the network side ..... | 239 | +| 12.2 | Other system parameters ..... | 239 | +| 12.2.1 | TCP related parameters and system parameters ..... | 239 | +| 12.2.2 | (void) ..... | 240 | +| 12.2.3 | MS system parameters ..... | 240 | +| Annex A (informative): | RTP Framing for CS-domain Services..... | 241 | +| A.1 | RFC 4867 Framing ..... | 241 | +| A.1.1 | (void) ..... | 241 | +| A.1.1a | Codec and Redundancy Mode Example ..... | 241 | +| A.1.2 | RFC 4867 Octet-aligned Frame Examples ..... | 242 | + +| | | +|------------------------------------------------------------------------------------------------------------|------------| +| A.2 (HS)CSD Framing over RTP ..... | 244 | +| Annex B (normative): Network QoS..... | 245 | +| B.1 Introduction..... | 245 | +| B.2 Network behaviour..... | 245 | +| B.3 MS behaviour..... | 245 | +| B.3.1 Receiving of data..... | 245 | +| B.3.1.1 Outer IP packet..... | 245 | +| B.3.1.2 Inner IP packet..... | 246 | +| B.3.2 Sending of data..... | 246 | +| Annex C (normative): (Source-RAT) Measurement Report for Handover and Cell Change Order to GAN..... | 246 | +| C.1 Measurement Report for Handover and Cell Change Order to GAN A/Gb mode ..... | 246 | +| C.2 Measurement Report for Handover and Cell Change Order to GAN Iu mode..... | 247 | +| Annex D (normative): RFC 4867 Framing Parameters for GAN..... | 248 | +| D.1 RFC 4867 Framing Parameters for GAN ..... | 248 | +| Annex E (normative): GAN Specific Requirements for Interworking with UTRAN ..... | 249 | +| E.1 GAN A/Gb Mode Specific Requirements for Interworking with UTRAN ..... | 249 | +| E.2 GAN Iu Mode Specific Requirements for Interworking with UTRAN..... | 250 | +| Annex F (normative): 3G Cell Identity coding..... | 251 | +| F.1 3G Cell Identity coding – 28 bitstring ..... | 251 | +| F.2 3G Cell Identity coding – RNC-Id + C-Id ..... | 251 | +| F.3 3G Cell Identity coding – Extended RNC-Id + C-Id..... | 251 | +| Annex G (informative): Change History..... | 252 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +x the first digit: + +- 1 presented to TSG for information; +- 2 presented to TSG for approval; +- 3 or greater indicates TSG approved document under change control. + +y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. + +z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document describes the procedures used over the Generic Access Network (GAN) interface (i.e., the Up interface). The procedures are defined in terms of messages exchanged over the Up interface. + +A building block method is used to describe the procedures. + +The basic building blocks are "elementary procedures" provided by the Generic Access (GA) protocol control entities. + +Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences. + +--- + +# 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 23.002: "Network Architecture". +- [3] 3GPP TS 23.003: "Numbering, Addressing and identification". +- [4] 3GPP TS 23.009: "Handover procedures". +- [5] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [6] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description". +- [7] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [8] 3GPP TS 24.008: "Mobile radio interface layer 3 specification". +- [9] 3GPP TS 26.103: "Speech codec list for GSM and UMTS". +- [10] Void. +- [11] 3GPP TS 43.020: "Security related network functions". +- [12] 3GPP TS 44.018: "Mobile radio interface layer 3 specification, Radio Resource Control (RRC) protocol" +- [13] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System, (MS - BSS) Interface" +- [14] 3GPP TS 48.004: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Layer 1 specification". +- [15] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". + +- [16] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [17] 3GPP TS 48.014: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Gb interface Layer 1". +- [18] 3GPP TS 48.016: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Network Service". +- [19] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; BSS GPRS Protocol (BSSGP)". +- [20] 3GPP TS 23.271: "Location Services (LCS); Functional Description; Stage 2". +- [21] Void. +- [22] Void. +- [23] RFC 4186, January 2006: "Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM)". +- [24] RFC 2104, February 1997: "HMAC: Keyed-Hashing for Message Authentication". +- [25] RFC 4776, October 2006: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information". +- [26] Void. +- [27] RFC 5996, September 2010: "Internet Key Exchange Protocol Version 2 (IKEv2)". +- [28] Void. +- [29] Void. +- [30] Void. +- [31] Void. +- [32] RFC 768, August 1980: "User Datagram Protocol". +- [33] RFC 791, September 1981: "Internet Protocol". +- [34] RFC 793, September 1981: "Transmission Control Protocol". +- [35] RFC 3550, July 2003: "RTP: A Transport Protocol for Real-Time Applications". +- [36] Void. +- [37] 3GPP TS 43.318: "Generic Access Network - Stage 2". +- [38] Void. +- [39] Void. +- [40] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification". +- [41] RFC 4187, January 2006: "Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)". +- [42] RFC 2486, January 1999: "The Network Access Identifier". +- [43] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [44] 3GPP TS 43.055: "Dual Transfer Mode (DTM), Stage 2". +- [45] 3GPP TS 44.060, "Radio Link Control/Medium Access Control (RLC/MAC) protocol". + +- [46] 3GPP TS 25.133, "Requirements for support of radio resource management (FDD)". +- [47] 3GPP TS 45.009, "Link adaptation". +- [48] RFC 4867, April 2007: "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". +- [49] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2". +- [50] RFC 3629, November 2003: "UTF-8 a transformation format of ISO 10646". +- [51] RFC 4040, April 2005: "RTP Payload Format for a 64 kbit/s Transparent Call". +- [52] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [53] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [54] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [55] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification". +- [56] 3GPP TR 33.402: "Security aspects of non-3GPP accesses". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions in 3GPP TS 43.318 and the following apply. + +**Access Point ID:** The AP-ID is the physical identity (e.g. MAC address) of the generic IP access network point through which the MS is accessing GAN service. This identifier is provided by the MS (obtained via broadcast from the AP) to the GANC via the Up interface, when it requests GAN service. The AP-ID may be used by the GANC to support location services. The AP-ID may also be used by the service provider to restrict GAN service access via only authorized APs. + +**Blind Transmission:** refers to the decision made by the SGSN to start the transmission of downlink N-PDUs or by the target BSS/GANC to start the transmission of downlink LLC PDUs for a given mobile station before receiving confirmation that the PS handover procedure has been successfully completed. + +### 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +Wm Reference point between a Security Gateway and a 3GPP AAA Server or 3GPP AAA proxy. + +### 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-------------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| AKA | Authentication and Key Agreement | +| AP | Access Point | +| BSC | Base Station Controller | +| BSS | Base Station Subsystem | +| BSSGP | Base Station System GPRS Protocol | +| BSSMAP | Base Station System Management Application Part | +| BTS | Base Transceiver Station | +| CBS | Cell Broadcast Service | + +| | | +|---------|-----------------------------------------------------------------------------| +| CC | Call Control | +| CGI | Cell Global Identification | +| CM | Connection Management | +| CN | Core Network | +| CPE | Customer Premises Equipment | +| CS | Circuit Switched | +| CSD | Circuit Switched Data | +| CTC | Circuit Transport Channel | +| CTM | Cellular Text Telephone Modem | +| DNS | Domain Name System | +| DTM | Dual Transfer Mode | +| E-UTRAN | Evolved UTRAN | +| EAP | Extensible Authentication Protocol | +| ECGI | Evolved Cell Global Identifier | +| ESP | Encapsulating Security Payload | +| ETSI | European Telecommunications Standards Institute | +| FCC | US Federal Communications Commission | +| FEC | Forward Error Correction | +| FLR | Frame Loss Ratio | +| FQDN | Fully Qualified Domain Name | +| GA | Generic Access | +| GAN | Generic Access Network | +| GANC | Generic Access Network Controller | +| GA-RC | Generic Access Resource Control | +| GA-CSR | Generic Access Circuit Switched Resources | +| GA-PSR | Generic Access Packet Switched Resources | +| GA-RRC | Generic Access Radio Resource Control | +| GERAN | GSM EDGE Radio Access Network | +| GGSN | Gateway GPRS Support Node | +| GMM/SM | GPRS Mobility Management and Session Management | +| GPRS | General Packet Radio Service | +| GSM | Global System for Mobile communications | +| GSN | GPRS Support Node | +| HLR | Home Location Register | +| HPLMN | Home PLMN | +| IETF | Internet Engineering Task Force | +| IMEISV | International Mobile Station Equipment Identity and Software Version Number | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| ISP | Internet Service Provider | +| LA | Location Area | +| LAI | Location Area Identity | +| LLC | Logical Link Control | +| MAC | Medium Access Control | +| MAC | Message Authentication Code | +| MM | Mobility Management | +| MS | Mobile Station | +| MSC | Mobile Switching Center | +| MSRN | Mobile Station Roaming Number | +| MTP1 | Message Transfer Part Layer 1 | +| MTP2 | Message Transfer Part Layer 2 | +| MTP3 | Message Transfer Part Layer 3 | +| NAS | Non-Access Stratum | +| NAT | Network Address Translation | +| NSS | Network SubSystem | +| PDP | Packet Data Protocol | +| PDU | Protocol Data Unit | +| PLMN | Public Land Mobile Network | +| PSAP | Public Safety Answering Point | +| PSTN | Public Switched Telephone Network | +| PTC | Packet Transport Channel | + +| | | +|--------|---------------------------------------------| +| P-TMSI | Packet TMSI | +| QoS | Quality of Service | +| RA | Routing Area | +| RAC | Routing Area Code | +| RAI | Routing Area Identity | +| RAT | Radio Access Technology | +| RLC | Radio Link Control | +| RRC | Radio Resource Control | +| RTCP | Real Time Control Protocol | +| RTP | Real Time Protocol | +| SA | Security Association | +| SCCP | Signalling Connection Control Part | +| SGSN | Serving GPRS Support Node | +| SEGW | Security Gateway | +| SMS | Short Message Service | +| SNDPC | Sub-Network Dependent Convergence Protocol | +| TAI | Tracking Area Identity | +| TBF | Temporary Block Flow | +| TC | Transport Channel | +| TCP | Transmission Control Protocol | +| TEID | Tunnel Endpoint Identifier | +| TFO | Tandem Free Operation | +| TMSI | Temporary Mobile Subscriber Identity | +| TrFO | Transcoder Free Operation | +| TTY | Text telephone or teletypewriter | +| UDP | User Datagram Protocol | +| UMTS | Universal Mobile Telecommunication System | +| UTRAN | Universal Terrestrial Radio Access Networks | +| VLR | Visited Location Register | + +--- + +## 4 Elementary procedures for handling of secure connection + +### 4.1 General + +All traffic over the Up interface shall be sent through the IPsec tunnel that is established as a result of the authentication procedure. + +### 4.2 Establishment of the secure connection + +#### 4.2.1 General + +The MS and GANC-SEGW shall set up one IKE Secure Association (SA) and one CHILD\_SA for IPsec ESP according to the profiles defined in [37]. The MS shall act as initiator, and the GANC-SEGW as responder. For MS with SIM only, the MS and GANC-SEGW shall use EAP-SIM for mutual authentication of the MS and the core network according to sub-clause 4.3. For MS with USIM, the MS and GANC-SEGW shall use EAP-AKA for mutual authentication of the MS and the core network according to sub-clause 4.4. + +The MS shall use certificates for authentication of the GANC-SEGW according to sub-clause 4.2.5. + +Furthermore, the MS shall: + +- use Configuration Payload according to [27] to acquire/renew an internal IP address in the network protected by the GANC-SEGW +- act as initiator in the Traffic Selector (TS) negotiation. The MS shall use the following value for the traffic selector-initiator and traffic selector-responder payloads: + +TSi = (0, 0-65535, 0.0.0.0-255.255.255.255) + +TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) + +The GANC-SEGW shall use the following value for the traffic selector-initiator and traffic selector-responder payloads: + +TSi = (0, 0-65535, *ms\_internal\_address - ms\_internal\_address*), where *ms\_internal\_address* is the IP address in the network protected by the GANC-SEGW that is assigned to the MS + +TSr = (0, 0-65535, 0.0.0.0-255.255.255.255) + +Either the MS or GANC-SEGW may initiate re-keying of the SA based on their individual lifetime policy on the SA. + +## 4.2.2 Identities + +The MS shall send its EAP-SIM or EAP-AKA identity (composed according to sub-clauses 4.3.2 and 4.4.2) as initiator identity IDi. + +The MS shall include the GANC-SEGW identity that it wishes to communicate with in the Identity Responder (IDr) payload in the IKE\_SA\_AUTH Request (message 3) as follows: + +- If the MS derived the FQDN of the Provisioning GANC-SEGW from the IMSI (as described in [3]), it shall include the derived FQDN in the Identification Data field of the IDr payload and indicate Identity Type 2 (ID\_FQDN) in the ID Type field of the IDr payload; +- If the MS was provisioned with an IPv4 address of the Provisioning GANC-SEGW, or received it in the GA-RC DISCOVERY ACCEPT message or GA-RC REGISTER REDIRECT message for the Default or a Serving GANC-SEGW, it shall include that IPv4 address in the Identification Data field of the IDr payload and indicate Identity Type 1 (ID\_IPV4\_ADDR) in the ID Type field of the IDr payload; +- If the MS was provisioned with an IPv6 address of the Provisioning GANC-SEGW, or received it in the GA-RC DISCOVERY ACCEPT message or GA-RC REGISTER REDIRECT message for the Default or a Serving GANC-SEGW, it shall include that IPv6 address in the Identification Data field of the IDr payload and indicate Identity Type 5 (ID\_IPV6\_ADDR) in the ID Type field of the IDr payload; +- If the MS was provisioned with a FQDN of the Provisioning GANC-SEGW, or received it in the GA-RC DISCOVERY ACCEPT message or GA-RC REGISTER REDIRECT message for the Default or a Serving GANC-SEGW, it shall include that FQDN in the Identification Data field of the IDr payload and indicate Identity Type 2 (ID\_FQDN) in the ID Type field of the IDr payload; + +The GANC-SEGW shall provide the GANC-SEGW identity in the Identity Payload (IDr) as following: + +Identity Type = 2 (ID\_FQDN) or 1 (ID\_IPV4\_ADDR) or 5 (ID\_IPV6\_ADDR) + +Identity Data = GANC-SEGW FQDN or IPv4 address or IPv6 address, respectively + +Identity Type shall match the Type of the SubjectAltName contained in the GANC-SEGW certificate as well as what was provisioned in the MS for Provisioning GANC-SEGW or provided in GA-RC DISCOVERY ACCEPT for Default GANC-SEGW or GA-RC REGISTER REDIRECT for Serving GANC-SEGW. + +## 4.2.3 Crypto negotiation + +The MS and GANC-SEGW negotiate the cryptographic suite to use for the SA, as per [27]. + +The MS shall include all the algorithms for integrity and confidentiality (defined in the profile for IPsec ESP in [37]) that it supports in the proposal. The GANC-SEGW signals back the selected algorithms that will be used for confidentiality and integrity protection, based on core network policy. + +## 4.2.4 NAT traversal + +The MS and GANC-SEGW shall use the IKEv2 mechanisms for detection of NAT, NAT traversal and keep-alive (as specified in [27]). If NAT is detected, the MS and GANC-SEGW shall use the UDP encapsulation of ESP packets mechanism (as specified in [30]). + +## 4.2.5 Certificate Handling and Authentication + +As the MS and GANC-SEGW use EAP-SIM or EAP-AKA for mutual authentication, IKEv2 mandates that this is used in conjunction with a public key signature based authentication of the GANC-SEGW to the MS. + +The MS requirements for certificate authentication and handling are listed in 3GPP TS 33.402 [56]. + +In addition to the requirements listed in 3GPP TS 33.402 [56], the MS shall take the following actions for received GANC-SEGW certificates: + +- match the SubjectAltName in the end entity certificate with the IDr payload, and with GANC-SEGW identity obtained from derivation of the Provisioning GANC-SEGW FQDN, provisioning, discovery or register redirect. +- If the MS was provisioned with an IP address of the GANC-SEGW, (or received it in the GA-RC DISCOVERY ACCEPT or GA-RC REGISTER REDIRECT message), then the certificate shall contain an IPAddress SubjectAltName that matches that address. +- If the MS was provisioned with an FQDN of the GANC-SEGW, or received it in the GA-RC DISCOVERY ACCEPT or GA-RC REGISTER REDIRECT message, then the certificate shall contain a DNSName SubjectAltName that matches that FQDN. +- If the MS derived the FQDN of the Provisioning GANC-SEGW, then the certificate shall contain a DNSName SubjectAltName that matches that FQDN. +- If a single SubjectAltName extension contains several IPAddress or DNSName components, at least one of them shall match the expected value. + +## 4.2.6 Abnormal cases + +If the MS and GANC-SEGW are not able to set up the SA for any other reason than EAP-SIM or EAP-AKA authentication failure, and the current GANC-SEGW is the SEGW associated to the Default GANC or a Serving GANC, the MS shall act as if a "Lower layer failure in the MS" has occurred and act as defined in sub-clause 6.2.4.2. + +If the MS and GANC-SEGW are not able to set up the SA for any other reason than EAP-SIM or EAP-AKA authentication failure, and the current GANC-SEGW is the SEGW associated to the Provisioning GANC, the MS shall act as if a "Lower layer failure in the MS" has occurred and act as defined in sub-clause 5.6.2. + +## 4.3 EAP-SIM authentication + +### 4.3.1 General + +After the initial IKEv2 exchanges, EAP-SIM authentication is invoked by deferring the sending of the AUTH payload, as per [27]. + +The GANC-SEGW shall: + +- compose an EAP Response/Identity message containing the IDi of the MS and send this message to the AAA server. This will trigger the EAP-SIM authentication procedure. +- communicate with the local AAA server over the Wm interface, and relay traffic between the local AAA server and MS. + +After the MS has received the EAP Success message (i.e. EAP-SIM authentication procedure was successful), the MS and GANC-SEGW complete the setup of the SA. + +### 4.3.2 EAP-SIM Identity + +The MS sends its identity as part of the initial IKE exchanges, and this also serves as identify for the EAP-SIM exchange. The identity is composed compliant with the Network Access Identifier (NAI) format specified in [42] and [3]. + +### 4.3.3 EAP-SIM Fast Re-authentication + +The MS may use the re-authentication identity that was provided during the previous EAP-SIM authentication procedure to authenticate using EAP-SIM fast re-authentication instead of the full authentication procedure. The MS shall use the realm part provided by the EAP-SIM server as part of the fast re-authentication identity, as specified in [23]. + +The MS may attempt to use the fast re-authentication procedure when it has an unused re-authentication identity available. The MS shall not use one re-authentication identity more than once. The fast re-authentication procedure shall not be used for the first authentication after the MS has powered up, in that case it shall use the full authentication procedure. + +### 4.3.4 Abnormal cases + +If the EAP-SIM authentication procedure fails, and the current GANC-SEGW is the SEGW associated to the Default GANC or a Serving GANC fails, the MS shall act as if it had received GA-RC REGISTER REJECT with the Reject Cause value 'IMSI not allowed' as defined in sub-clause 6.2.3.3. + +If the EAP-SIM authentication procedure fails, and the current GANC-SEGW is the SEGW associated to the Provisioning GANC, the MS shall act as if it had received GA-RC DISCOVERY REJECT with the Reject Cause value 'IMSI not allowed' as defined in sub-clause 5.5.2. + +## 4.4 EAP-AKA authentication + +### 4.4.1 General + +After the initial IKEv2 exchanges, EAP-AKA authentication is invoked by deferring the sending of the AUTH payload, as per [27]. + +The GANC-SEGW shall: + +- compose an EAP Response/Identity message containing the IDi of the MS and send this message to the AAA server. This will trigger the EAP-AKA authentication procedure. +- communicate with the local AAA server over the Wm interface, and relay traffic between the local AAA server and MS.- + +After the MS has received the EAP Success message (i.e. EAP-AKA authentication procedure was successful), the MS and GANC-SEGW complete the setup of the SA. + +### 4.4.2 EAP-AKA Identity + +The MS sends its identity as part of the initial IKE exchanges, and this also serves as identify for the EAP-AKA exchange. The identity is composed compliant with the Network Access Identifier (NAI) format specified in [42] and [3]. + +### 4.4.3 EAP-AKA Fast Re-authentication + +The MS may use the re-authentication identity that was provided during the previous EAP-AKA authentication procedure to authenticate using EAP-AKA fast re-authentication instead of the full authentication procedure. The MS shall use the realm part provided by the EAP-AKA server as part of the fast re-authentication identity, as specified in [41]. + +The MS may attempt to use the fast re-authentication procedure when it has an unused re-authentication identity available. The MS shall not use one re-authentication identity more than once. The fast re-authentication procedure shall not be used for the first authentication after the MS has powered up, in that case it shall use the full authentication procedure. + +#### 4.4.4 Abnormal cases + +If the EAP-AKA authentication procedure fails, and the current GANC-SEGW is the SEGW associated to the Default GANC or a Serving GANC fails, the MS shall act as if it had received GA-RC REGISTER REJECT with the Reject Cause value 'IMSI not allowed' as defined in sub-clause 6.2.3.3. + +If the EAP-AKA authentication procedure fails, and the current GANC-SEGW is the SEGW associated to the Provisioning GANC, the MS shall act as if it had received GA-RC DISCOVERY REJECT with the Reject Cause value 'IMSI not allowed' as defined in sub-clause 5.5.2. + +### 4.5 Release of the secure connection + +The SA is closed according the procedures defined in [27]. + +## 5 GA-RC elementary procedures for GANC Discovery + +### 5.1 Purpose of the Discovery Procedure + +The purpose of the Discovery procedure is to allow the network to allocate a Default GANC to a MS. This allocation consists of the IP address or FQDN of the Default GANC-SEGW, and the IP address or FQDN and TCP port of the Default GANC to be used for the Registration procedure. As long as the Default GANC is available in the network the MS shall not perform Discovery procedure again. The Discovery procedure is performed using the IPsec tunnel that is established between the MS and the Provisioning GANC-SEGW as defined in sub-clause 4.2. + +### 5.2 Discovery procedure + +The Discovery procedure is performed between the MS and the Provisioning GANC. The Discovery procedure is initiated by the MS in order to receive information about the Default GANC to be used for future instances of the Registration Procedure. + +![Sequence diagram of the Discovery procedure between MS and GANC.](c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + GANC-->>MS: GA-PSR HANDOVER FAILURE +``` + +The diagram illustrates the Discovery procedure between a Mobile Station (MS) and a GANC. The MS initiates the procedure with a 'GA-PSR HANDOVER INFORMATION' message. The GANC responds with 'GA-PSR UPLINK QUALITY INDICATION', 'GA-PSR HANDOVER COMMAND', and 'GA-PSR HANDOVER FAILURE' messages. The MS also sends 'GA-PSR ACTIVE' and 'GA-PSR HANDOVER INFORMATION' messages. The procedure is triggered by 'Start TU4004' and 'Stop TU4004' events on the MS side. + +Sequence diagram of the Discovery procedure between MS and GANC. + +Figure 5.2: Discovery procedure + +### 5.3 Discovery Request initiation by the MS + +This procedure shall be triggered after the MS has gained IP connectivity (i.e. an IP address is allocated to the MS in the "transport IP" layer) and the MS has either no stored information about a Default GANC or if the previous Registration procedure towards the Default GANC was unsuccessful. + +The MS may initially be provisioned with information (i.e. an IP address or a FQDN) about the Provisioning GANC and the corresponding Provisioning SEGW related to that GANC. The provisioning of this information in the MS is out of the scope of this document. This information can be in the format of either a FQDN or an IP-address or any combination of these. + +The MS shall: + +- If the MS holds an IP address of the Provisioning SEGW, the MS establishes the secure connection towards the Provisioning SEGW according to sub-clause 4.2; +- If the MS holds a FQDN of the Provisioning SEGW, the MS performs a public DNS query to retrieve the IP-address of the Provisioning SEGW and establish the secure connection towards the Provisioning SEGW according to sub-clause 4.2. The MS shall not store the IP address retrieved from DNS for subsequent procedures (apart from DNS resolver caching); +- In case the MS is not provisioned with information about the Provisioning SEGW, derive a FQDN of the Provisioning SEGW from the IMSI (as described in [3]); + +The MS performs a public DNS Query to retrieve the IP-address of the Provisioning SEGW and establish the secure connection towards the Provisioning SEGW according to sub-clause 4.2. The MS shall not store the IP address retrieved from DNS for subsequent procedures (apart from DNS resolver caching); + +- Following successful establishment of secure connection to the Provisioning SEGW: + - If the MS holds an IP address of the Provisioning GANC, the MS shall establish a TCP connection to the Provisioning GANC using the well-known TCP port for Discovery as defined in sub-clause 12.2.1 + - If the MS holds a FQDN of the Provisioning GANC, the MS shall perform a DNS query "inside the secure connection" to retrieve the IP-address of the Provisioning GANC. The MS shall establish a TCP connection to the Provisioning GANC using this IP address and a TCP port defined for Discovery (see sub-clause 12.2.1). The MS shall not store the IP address retrieved from DNS for subsequent procedures (apart from DNS resolver caching). + - In cases where the MS is not provisioned with information about the Provisioning GANC, the MS derives a FQDN of the Provisioning GANC from the IMSI (as described in [3]). + +A DNS query is performed "inside the secure connection" to retrieve the IP-address of the Provisioning GANC. The MS shall not store the IP address retrieved from DNS for subsequent procedures (apart from DNS resolver caching). A TCP connection is then established inside the IPsec tunnel, to the Provisioning GANC using the TCP port defined for Discovery procedure (see sub-clause 12.2.1). + +- In all cases the MS shall establish only a single TCP connection to the GANC over the IPsec tunnel. +- After successful establishment of a secure connection to the SEGW and a TCP connection to the GANC the MS shall proceed as follows: + - If the Discovery Procedure is due to the MS failing to register with a GANC, the MS includes the following information elements in the GA-RC DISCOVERY REQUEST message: Register Reject Cause IE, Redirection Counter IE and Default GANC IE, + - Send a GA-RC DISCOVERY REQUEST message to the Provisioning GANC on the established TCP connection. + - When GA-RC layer has submitted the GA-RC DISCOVERY REQUEST message to the TCP layer, it shall start timer TU3901. + +## 5.4 Discovery Request processing by the network + +When receiving the GA-RC DISCOVERY REQUEST message the Provisioning GANC may either accept or reject the Discovery request from the MS. + +### 5.4.1 Discovery accepted + +If the Provisioning GANC accepts the Discovery request from the MS, it shall send the GA-RC DISCOVERY ACCEPT message to the MS. When the GA-RC layer in the Provisioning GANC has submitted the GA-RC DISCOVERY ACCEPT message to the TCP layer, it may initiate release of its half of the bidirectional TCP connection. + +The Provisioning GANC may use the Redirect Counter IE, Register Reject Cause Value IE and Default GANC IE received in the GA-RC DISCOVERY REQUEST message to assign a different Default GANC for the MS. + +## 5.4.2 Discovery rejected + +If the Provisioning GANC rejects the Discovery request from the MS, it shall send the GA-RC DISCOVERY REJECT message to the MS. When the GA-RC layer in the Provisioning GANC has submitted the GA-RC DISCOVERY REJECT message to the TCP layer and the value of the Discovery Reject Cause IE included in the message was not 'Network Congestion', it may initiate release of its half of the bidirectional TCP connection. + +The Provisioning GANC may use the Redirect Counter IE, Register Reject Cause Value IE and Default GANC IE received in the GA-RC DISCOVERY REQUEST message to detect a problem and reject the MS. + +# 5.5 Discovery response processing by the MS + +## 5.5.1 Discovery accepted + +When the MS receives GA-RC DISCOVERY ACCEPT message, it shall: + +- stop the timer TU3901. +- set the timer value for TU3903 to the default value, +- store the information about Default GANC in persistent storage: + - The Default GANC information consists of the Default GANC, SEGW associated with the Default GANC and optionally a TCP port to be used with that Default GANC. If a specific TCP Port is not received in the message, the defined port for Registration is used (see sub-clause 12.2.1) +- release the TCP connection towards the Provisioning GANC +- the secure connection to the Provisioning SEGW can be reused as follows; + - If the MS is provisioned with an IP address of the Provisioning GANC-SEGW and it matches the received Default GANC-SEGW IP address IE, the MS shall reuse the existing secure connection. + - If the MS is provisioned with a FQDN of the Provisioning GANC-SEGW or derived a FQDN for the Provisioning GANC-SEGW and it matches the received Default GANC-SEGW FQDN IE, the MS shall reuse the existing secure connection. +- otherwise the MS shall release the existing secure connection towards the SEGW of the Provisioning GANC as defined in sub-clause 4.5 +- initiate the registration procedure towards the Default GANC as defined in sub-clause 6.2. + +## 5.5.2 Discovery rejected + +When the MS receives GA-RC DISCOVERY REJECT message it shall: + +- stop the timer TU3901, +- set the timer value for TU3903 to the default value, +- If the value of the Reject Cause IE indicates 'Network Congestion' , the MS shall: + - Maintain the secure connection to the GANC-SEGW and the TCP connection to the GANC. + - Create a random value between zero and the received value in TU3902 Timer IE, and + - Add this value to the received value in TU3902 Timer IE, this becomes the new value for TU3902. + - Start timer TU3902 according to the new calculated value. +- If the value of the Reject Cause IE indicates 'IMSI not allowed' or "Unspecified", then the MS shall: + - Release the TCP connection established to the Provisioning GANC, if still established. + +- Release the secure connection towards the SEGW associated with the Provisioning GANC as defined in sub-clause 4.5. +- Not initiate a new Discovery procedure until the next power-on. + +## 5.6 Abnormal cases + +### 5.6.1 TU3901 expiry + +If timer TU3901 has expired in the MS, the MS shall: + +- release the TCP connection towards the Provisioning GANC, +- release the secure connection towards SEGW of the Provisioning GANC as defined in sub-clause 4.5, +- double the current value for timer TU3903 but not exceeding the maximum value defined for this timer as defined in sub-clause 12.1.1 and +- start timer TU3903 and wait for it to expire. + +### 5.6.2 Lower layer failure in the MS + +Lower layer failure in the MS can be for example related to DNS, IPsec or TCP. If any lower layer failure happens in the MS, the MS shall: + +- release the TCP connection towards the Provisioning GANC, if established, +- release the secure connection towards SEGW of the Provisioning GANC, if established, as defined in sub-clause 4.5, +- double the current timer value for TU3903 but not exceeding the maximum value defined in sub-clause 12.1.1, +- stop timer TU3901 if running and +- start timer TU3903 and wait for it to expire. + +### 5.6.3 TU3902 expiry + +If timer TU3902 has expired in the MS, the MS shall: + +- if the TCP connection to the Provisioning GANC is still established: + - send a GA-RC DISCOVERY REQUEST message and + - start timer TU3901 +- otherwise, restart the Discovery procedure as defined in sub-clause 5.3. + +### 5.6.4 TU3903 expiry + +If timer TU3903 has expired in the MS, the MS shall restart the Discovery procedure as defined in sub-clause 5.3. + +--- + +## 6 GA-RC elementary procedures for Registration + +### 6.1 Purpose of GAN Registration + +The Registration procedure is performed between the MS and the GANC (Default or Serving GANC). The purpose of this procedure is to allow the MS to register for GAN services on the most suitable GANC for the network. The MS as part of the Registration procedure provides the GANC with information relating to the current connectivity of the MS. The GANC, as part of a successful Registration, indicates the GAN mode (i.e., GAN A/Gb mode or GAN Iu mode) that the MS shall operate in while registered with the GANC and provides the MS with the "System Information" message content that is applicable in GAN mode. The Registration procedure is performed using the IPsec tunnel that is established between the MS and the Default or the Serving GANC-SEGW as defined in sub-clause 4.2. + +## 6.2 Registration procedure + +![Sequence diagram of the Registration procedure between MS and GANC.](474a819357587e34949a3e110ff19b30_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR HANDOVER INFORMATION (Start TU4004) + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER COMMAND (Stop TU4004) + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +The diagram illustrates the registration procedure between a Mobile Station (MS) and a GANC. The MS is initially in a 'GA-PSR ACTIVE' state. The procedure begins with the MS sending a 'GA-PSR HANDOVER INFORMATION' message to the GANC, marked as 'Start TU4004'. The GANC responds with a 'GA-PSR UPLINK QUALITY INDICATION' message. The GANC then sends a 'GA-PSR HANDOVER COMMAND' message to the MS, marked as 'Stop TU4004'. Finally, the MS sends a 'GA-PSR HANDOVER FAILURE' message to the GANC. + +Sequence diagram of the Registration procedure between MS and GANC. + +Figure 6.2.1: Registration procedure + +### 6.2.1 Registration initiation by the MS + +This procedure shall be triggered by the MS under the following conditions: + +- the MS has gained IP connectivity (i.e. an IP address is allocated to the MS in the "transport IP" layer); and +- the MS has stored information about a Default GANC. + +The Registration procedure is initiated towards the Default GANC after a successful Discovery procedure or after a failed Registration towards a Serving GANC, where no GAN PLMN list was provided to the MS from the Default GANC. The Registration procedure is also initiated towards the Default GANC when no more PLMNs can be selected from the GAN PLMN List received from the Default GANC. + +As part of the Registration procedure, the MS may receive a list of PLMN identities when trying to register towards the Default GANC. This list of PLMN identities is passed to the GANC selection process. Following PLMN selection by the GANC selection process, and if registered to a Serving GANC, the MS shall first deregister from the current Serving GANC as defined in sub-clause 6.4.1, and then attempt the registration procedure towards the Serving GANC-SEGW and GANC associated with the selected PLMN. + +This procedure is also triggered towards the Default GANC, if the MS at any time wishes to perform manual PLMN selection or "User reselection" irrespective of whether the MS is in manual or automatic PLMN selection mode. If the MS is already successfully registered to a Serving GANC, and a manual PLMN selection or "User reselection" is initiated, the MS shall first deregister from the current Serving GANC as defined in sub-clause 6.4.1 and then initiate registration towards the Default GANC and include an indication that a list of PLMN identities is requested for manual PLMN selection or user reselection. After receiving the requested PLMN list from the Default GANC the MS shall then re-register on the last registered Serving GANC. + +GANC information required to initiate the Registration procedure consists of a GANC-SEGW address, a GANC address and a GANC TCP port number. The MS shall initiate the Registration procedure towards a Serving GANC if the corresponding GANC information is available in the stored Serving GANC table. If successful, the stored Serving GANC table in the MS may be updated to contain address information of the successfully registered Serving GANC and the corresponding GSM-CGI, UTRAN cell identity or E-UTRAN cell identity, if available, or AP-ID, if no GSM CGI, UTRAN cell identity or E-UTRAN cell identity is available (see sub-clause 6.2.3.1). UTRAN cell identity consists of the Location Area Identity (LAI) and Cell Identity (defined in [40]). E-UTRAN cell identity consists of the Tracking Area Identity (TAI) and Cell Identity (defined in [55]). The Default GANC is in control of whether or not the MS is allowed to store GANC information in the stored Serving GANC table. + +If the MS is in GERAN, UTRAN or E-UTRAN coverage, it shall check if it has stored Serving GANC information for the current GSM CGI in case of GERAN coverage, UTRAN cell identity in case of UTRAN Coverage, or E-UTRAN cell identity in case of E-UTRAN coverage, or if the MS is not in GERAN/UTRAN/E-UTRAN coverage, it shall check if it has stored Serving GANC information for the current AP-ID: + +- if found, the MS shall initiate the GAN Registration procedure towards the stored Serving GANC +- if not found, the MS shall initiate the GAN Registration procedure towards the Default GANC + +The Location Black List contains information about forbidden Locations acquired while attempting GAN registration and is only valid if the MS is in GERAN or UTRAN coverage. It can contain Location information on 3 different levels: Country (i.e. MCC), PLMN (i.e. MCC and MNC) and Location Area (i.e. MCC, MNC and LAC). If the MS is in a location identified by an entry in the Location Black List, the MS shall not initiate the GAN Registration procedure. The Location Black List shall be deleted upon power cycle. + +The AP Black List contains information about denied APs. If the MS is being provided IP connectivity by an AP that is on the AP Black List, the MS shall not initiate discovery or GAN registration, until the relevant AP has been removed from the AP Black List. The AP Black List shall be deleted upon power cycle. + +To initiate the GAN registration procedure the MS shall: + +- If the MS has stored an IP address of the GANC-SEGW, and the MS does not already have an established secure connection to this GANC-SEGW, the MS establishes a secure connection towards the GANC-SEGW according to sub-clause 4.2; +- If the MS has stored a FQDN of the GANC-SEGW, the MS performs a public DNS query to retrieve the IP-address of the GANC-SEGW, if the MS does not already have an established secure connection to this GANC-SEGW, the MS establishes the secure connection towards the GANC-SEGW according to sub-clause 4.2. The MS shall not store the IP address retrieved from DNS for subsequent procedures (apart from DNS resolver caching). + +Following successful establishment of secure tunnel: + +- If the MS holds an IP address of the GANC, the MS establishes a TCP connection to the GANC at the stored TCP port to be used for Registration with this GANC. If no TCP port has been stored for this GANC, the default TCP port (see sub-clause 12.2.1) shall be used; +- If the MS holds a FQDN of the GANC, the MS performs a DNS query "inside the secure tunnel" to retrieve the IP-address of the GANC. The MS establishes a TCP connection to the GANC at the stored TCP port to be used for Registration with this GANC. If no TCP port has been stored for this GANC, the default TCP port (see sub-clause 12.2.1) shall be used. The MS shall not store the retrieved IP address for subsequent procedures (apart from DNS resolver caching); +- The MS shall only establish a single TCP connection to the GANC over the IPsec tunnel. + +After successful establishment of a secure connection to the SEGW and a TCP connection to the GANC, the MS sends a GA-RC REGISTER REQUEST message to the GANC on the TCP connection, including the following information elements: + +- The Geographical Location IE, if available; +- AP Location IE, if available; +- Required GAN Services IE, if required; +- If a GAN PLMN list was received during the last registration attempt with the Default GANC and the GANC selection process is finished unsuccessfully (i.e. the MS was not successfully registered to a Serving GANC and to the associated PLMN in the GAN PLMN List IE), then the MS includes the received GAN PLMN List information in the GAN PLMN List IE in the GA-RC REGISTER REQUEST message; +- Else if the MS failed to register during the last registration it attempted with a GANC (Default or Serving), then Register reject Cause IE, Redirection Counter IE and address information (i.e. IP Address or the Fully Qualified Domain/Host Name IE) of the last GANC and last GANC-SEGW; +- Else if the MS was redirected during the last registration it attempted with a GANC (Default or Serving): + - Redirection Counter IE and address information (i.e. IP address or FQDN) of the last GANC and last GANC-SEGW + +When GA-RC layer has submitted the GA-RC REGISTER REQUEST message to the TCP layer, it shall start a timer TU3904 + +## 6.2.2 Registration processing by the network + +### 6.2.2.1 General + +When receiving the GA-RC REGISTER REQUEST message the GANC may either accept or reject the Registration request from the MS. The GANC may also redirect the MS to another GANC or provide a list of PLMN identities that may provide GAN service to the MS. + +The GANC should verify that the binding (IMSI, inner IP address) as received in the GA-RC REGISTER REQUEST is the same as the one that the MS used during authentication to the GANC-SEGW. + +### 6.2.2.2 Registration accepted + +If the GANC accepts the Registration request from the MS, it shall send the GA-RC REGISTER ACCEPT message to the MS and store information relating to the GAN service requirements of the mobile station. + +If the Default GANC indicator is included in the GA-RC REGISTER REQUEST message received from the MS, then the GANC shall include the Serving GANC Table indicator to indicate to the MS whether or not the MS is allowed to store the GANC information in the stored Serving GANC table. + +The GANC shall include the IE "GAN Mode Indicator" if the IE "GAN Classmark" received by the GANC in the GA-RC REGISTER REQUEST message included the GAN Mode Support Indicator field with value other than Unspecified. The IE "GAN Mode Indicator" indicates the GAN mode (i.e., GAN A/Gb mode or GAN Iu mode) that the MS shall operate in while registered with the GANC. + +### 6.2.2.3 Registration redirected + +If the GANC decides to redirect the MS to another GANC, the network shall send the GA-RC REGISTER REDIRECT message to the MS and act as follows: + +- If the MS attempts to register with the Default GANC as indicated by the presence of the Registration Indicators IE in the GA-RC REGISTER REQUEST message and the MS is not in manual PLMN selection mode, user reselection was not triggered and the MS is being redirected to a Serving GANC in the HPLMN, the GANC shall not include the GAN PLMN List information element. +- If the MS attempts to register with the Default GANC as indicated by the presence of the Registration Indicators IE in the GA-RC REGISTER REQUEST message, and the MS is not in manual PLMN selection mode, user reselection was not triggered and based on the current MS location and operator policies, the MS needs to perform a GANC selection, the GANC shall include the GAN PLMN List information element. +- If the MS attempts to register with the Default GANC as indicated by the presence of the Registration Indicators IE in the GA-RC REGISTER REQUEST message and that the MS is in manual PLMN selection mode or user reselection was triggered and requests a list of PLMNs, the GANC shall include the GAN PLMN List information element. +- If the MS attempts to register with a Serving GANC as indicated by the absence of the Registration Indicators IE in the GA-RC REGISTER REQUEST message, the GANC shall not include the GAN PLMN List information. + +When the GA-RC layer in the network has submitted the GA-RC REGISTER REDIRECT message to the TCP layer, it may initiate release of its half of the bidirectional TCP connection. + +The GANC can send this message at any time, but it shall not be sent to an MS in GA-CSR-DEDICATED or GA-PSR-ACTIVE state. + +The GANC may use the Redirect Counter IE, Register Failure Cause IE, Register Reject Cause Value IE and Last GANC IE to detect a problem and redirect the MS to a different Serving GANC. + +If the Default GANC indicator is included in the GA-RC REGISTER REQUEST message received from the MS, then the GANC may include the Serving GANC Table indicator to indicate to the MS whether or not the MS is allowed to store the GANC information in the stored Serving GANC table. + +#### 6.2.2.4 Registration rejected + +If the GANC decides to reject the registration from the MS, it shall send the GA-RC REGISTER REJECT message to the MS. When the GA-RC layer in the network has submitted the GA-RC REGISTER REJECT message to the TCP layer and the value of the Register Reject Cause IE included in the message was not 'Network Congestion', it may initiate release of its half of the bidirectional TCP connection. + +The GANC may use the Redirect Counter IE, Register Failure Cause IE, Register Reject Cause Value IE and Last GANC IE to detect a problem and reject the MS. + +### 6.2.3 Registration response processing by the MS + +#### 6.2.3.1 Registration accepted + +When the MS receives GA-RC REGISTER ACCEPT message, it shall: + +- stop the timer TU3904, +- reset the Redirection Counter, +- retrieve the GAN Mode Indicator IE (if included) and: + - if no GAN Mode Indicator IE is included or if the GAN Mode Indicator IE is included and indicates that the MS shall operate in GAN A/Gb mode, and the MS supports GAN A/Gb mode, then the MS shall operate in GAN A/Gb mode while registered with the GANC. + - if the GAN Mode Indicator IE is included and indicates that the MS shall operate in GAN Iu mode, and the MS supports GAN Iu mode, then the MS shall operate in GAN Iu mode while registered with the GANC. +- if GAN A/Gb mode is selected, then retrieve the GAN System Information parameters and: + - send the contents of GAN Cell Description IE (if received) to the GSM RR layer or UTRAN RRC to be used for Measurement Reports in GSM RR dedicated mode or GSM RR packet transfer mode or UTRAN RRC connected mode + - store the received GAN System Information and when GA-RC becomes the serving layer send the following information to the upper layers either immediately or upon entering the GA-CSR-IDLE state if the MS is currently in GA-CSR-DEDICATED state: + - from GAN Control Channel Description IE + - Network Mode of Operation, + - GPRS availability Indicator, + - Dual Transfer Mode Indicator, + - IMSI Detach/Attach indicator, + - MSC Release Indicator, + - SGSN Release Indicator, + - T3212 timer value, + - Routing Area Code, + - Emergency Call Mode Preference and + - Emergency Call indicator. + - GAN Location Area Identity. + - Store the Early Classmark Sending Indicator from GAN Control Channel Description IE. + - Store the Call Re-establishment bit from GAN Control Channel Description IE. +- if GAN Iu mode is selected, then retrieve the GAN System Information parameters and: + - send the contents of GAN Iu Mode Cell Description IE (if received) to the GSM RR layer or UTRAN RRC to be used for Measurement Reports in GSM RR dedicated mode or GSM RR packet transfer mode or UTRAN RRC connected mode + +- store the received GAN System Information and when GA-RC becomes the serving layer send the following information to the upper layers either immediately or upon entering the GA-RRC-IDLE state if the MS is currently in GA-RRC-CONNECTED state: + - from GAN Control Channel Description IE + - Network Mode of Operation, + - IMSI Detach/Attach indicator, + - MSC Release Indicator, + - SGSN Release Indicator, + - T3212 timer value, + - Routing Area Code, + - Emergency Call Mode Preference and + - Emergency Call indicator. + - GAN Location Area Identity. +- Store the Call Re-establishment bit from GAN Control Channel Description IE. +- Start Keep alive mechanism as defined in sub-clause 6.5 using the received TU3906 Timer IE. +- Use the received TU3910 Timer value as follows: + - When the MS roves out (i.e. leaves GAN mode and enters GERAN/UTRAN mode), it shall start timer TU3910 and shall not rove in (i.e. leave GERAN/UTRAN mode and enter GAN mode) until this timer has expired, unless the MS has detected loss of GERAN or UTRAN coverage. + - If timer TU3910 is running and MS is in GA-RC-REGISTERED state and; + - MS receives GA-RC REGISTER UPDATE DOWNLINK message, the MS shall restart the timer TU3910 using the new value if included in the message. +- If the GA-RC REGISTER ACCEPT was received from the Default GANC, the MS shall store the received Serving GANC table indicator and shall consider the Default GANC to be the Serving GANC. +- If the stored Serving GANC Table indicator is set to "store", update the stored Serving GANC table as follows (the SEGW and GANC address information type, i.e. FQDN or IP address, stored depends on the address type held by the MS when initiating registration i.e. if the MS held an IP address, then that IP-address shall be stored and if the MS held an FQDN, then that FQDN shall be stored): + - If the MS is in GERAN/UTRAN/E-UTRAN coverage and this was indicated in the GA-RC REGISTER REQUEST by including a current GSM CGI, UTRAN cell identity (i.e., LAI and Cell Identity which is defined in [40]), or E-UTRAN cell identity (i.e., TAI and Cell Identity which is defined in [55]): + - if the stored Serving GANC table does not contain the GSM CGI, UTRAN cell identity, or E-UTRAN cell identity, add the GSM CGI, UTRAN cell identity or E-UTRAN cell identity to the table with the information about the Serving GANC: SEGW FQDN or IP-address, GANC FQDN or IP-address and the TCP port to be used (if received in the message, otherwise the TCP port for Registration as defined in sub-clause 12.2.1). + - if the stored Serving GANC table contains the GSM CGI, UTRAN cell identity or E-UTRAN cell identity, update the information about the Serving GANC for this GSM CGI, UTRAN cell identity or E-UTRAN cell identity: SEGW FQDN or IP-address, GANC FQDN or IP-address and the TCP port to be used, as described above. + - If the MS is not in GERAN/UTRAN/E-UTRAN coverage and this was indicated in the GA-RC REGISTER REQUEST: + - if the stored Serving GANC table does not contain the AP-ID, add the AP-ID with the information about the Serving GANC: SEGW FQDN or IP-address, GANC FQDN or IP-address and the TCP port to be used (if received in the message, otherwise the TCP port for Registration as defined in sub-clause 12.2.1). + +- if the stored Serving GANC table contains the AP-ID, update the information about the Serving GANC for this AP-ID: SEGW FQDN or IP-address, GANC FQDN or IP-address and the TCP port to be used, as described above. +- If the stored Serving GANC Table indicator is set to "Do not store", the MS should not store the new registered serving GANC information in the stored Serving GANC table but should still maintain the related serving GANC information, if existing in the stored Serving GANC table. + +### 6.2.3.2 Registration redirected + +When the MS receives GA-RC REGISTER REDIRECT message, it shall: + +- stop the timer TU3904, +- Increment the Redirection counter, +- release the TCP connection towards the GANC, +- if timer TU3910 is running and MS is in GA-RC-REGISTERED state the MS shall stop the timer TU3910, +- if the GA-RC REGISTER REDIRECT was received from the Default GANC, the MS shall; + - store the received Serving GANC table indicator; + - if the GA-RC REGISTER REDIRECT contains the GAN PLMN List information element; + - store the information received in the GAN PLMN List information element , + - pass the received list of PLMN identities to the GANC selection process; + - release the secure connection towards SEGW of the Default GANC as defined in sub-clause 4.5; and; + - following PLMN selection by the GANC selection process, initiate the registration procedure towards the GANC associated with the selected PLMN as defined in sub-clause 6.2. Each GANC selected in this manner shall be considered as a Serving GANC by the MS; +- if the returned SEGW is the same as the one used for the connection towards the previous GANC, +- if the GA-RC-REGISTER REDIRECT was received from the Default GANC, then: + - if the stored Default GANC-SEGW address information is in an IP address format and the received GA-RC REGISTER REDIRECT message contains the Serving GANC-SEGW IP address IE, and these two IP addresses match, the MS shall reuse the secure connection; + - or if the stored Default GANC-SEGW address information is a FQDN and the received GA-RC REGISTER REDIRECT message contains the Serving GANC-SEGW FQDN IE, and these identifiers match, the MS shall reuse the secure connection. +- if the GA-RC-REGISTER REDIRECT was received from a Serving GANC, then: + - if the MS held a Serving GANC-SEGW IP address for the current Serving GANC (either in the Serving GANC store or received in a previous GA-RC REGISTER REDIRECT) and the received GA-RC REGISTER REDIRECT contains the Serving GANC-SEGW IP address IE, and these two IP addresses match, the MS shall reuse the secure connection, or + - if the MS held a Serving GANC-SEGW FQDN identifier (either in the Serving GANC store or received in a previous GA-RC REGISTER REDIRECT) and the received GA-RC REGISTER REDIRECT contains the Serving GANC-SEGW FQDN IE, and these identifiers match, the MS shall reuse the secure connection +- otherwise release the secure connection towards SEGW of the previous GANC as defined in sub-clause 4.5 +- initiate the registration procedure towards the returned GANC as defined in sub-clause 6.2. + +### 6.2.3.3 Registration rejected + +When the MS receives GA-RC REGISTER REJECT message it shall: + +- stop the timer TU3904, +- if the MS is in the process of GANC selection; + - ignore the received Register Reject Cause Information Element; and; + - proceed as defined in sub-clause 6.2.4.5. +- else extract the Register Reject Cause information element and act as following depending on the value of the Reject Cause IE: + - 'Network Congestion' + - create a random value between zero and the received value in IE 'TU3907 Timer' and + - add this value to the received value in IE 'TU3907 Timer', and use this as the new value for TU3907 + - start timer TU3907 according to the new calculated value and wait for it to expire. + - 'AP not allowed' + - release the TCP connection established to the GANC, if still established, + - release the secure connection towards the SEGW associated with the GANC, as defined in sub-clause 4.5 + - store the AP-ID in the AP Black List and not initiate a new Register Request from this AP, until the AP-ID is removed from the AP Black List i.e. as a result of power-cycle. + - 'Location not allowed' + - release the TCP connection established to the GANC, if still established, + - release the secure connection towards the SEGW associated with the GANC, as defined in sub-clause 4.5 + - update the Location Black List according to the received information elements Location Black List indicator and Location Area Identification (i.e. the same as that included in the GA-RC REGISTER REQUEST message) and not initiate a new Register Request from the locations indicated by the updated Location Black List, until they are removed from the Location Black List i.e. as a result of power-cycle. + - 'IMSI not allowed' + - release the TCP connection established to the GANC, if still established. + - release the secure connection towards the SEGW associated with the GANC, as defined in sub-clause 4.5 + - not initiate a new GAN Registration procedure until the next power-on. + - 'Invalid GANC' or 'Unspecified' + - release the TCP connection established to the GANC, if still established. + - release the secure connection towards the SEGW associated with the GANC, as defined in sub-clause 4.5 + - act as defined in sub-clause 6.2.4.5 + - 'Geo Location not known' + - release the TCP connection established to the GANC, if still established. + - release the secure connection towards the SEGW associated with the GANC, as defined in sub-clause 4.5 + - not retry registration from this AP until the location is provided or until the next power-on. + +The MS shall also: + +- Update the stored Serving GANC table as follows if the received Reject cause was not 'Network Congestion' or 'Geo Location not known': + - If the MS is in GERAN/UTRAN/E-UTRAN coverage it shall remove information related to the current GSM CGI, UTRAN cell identity or E-UTRAN cell identity, if it exists in the table. + - If the MS is not in GERAN/UTRAN/E-UTRAN coverage it shall remove information related to the AP-ID, if exists in the table. + +## 6.2.4 Abnormal cases + +### 6.2.4.1 TU3904 expiry + +If timer TU3904 expires in the MS, the MS shall: + +- release the TCP connection towards the GANC, +- release the secure connection towards SEGW of the GANC as defined in sub-clause 4.5, +- If GAN registration is unsuccessful after a number of attempts defined by the MS parameter "Up Register Max Retries" (defined in sub-clause 12.2.3), the MS shall act as defined in sub-clause 6.2.4.5. +- Otherwise, if GAN Registration can be re-attempted according to the MS parameter "Up Register Max Retries", start timer TU3905 and wait for it to expire. + +### 6.2.4.2 Lower layer failure in the MS + +Lower layer failure in the MS can be for example related to DNS, IPsec or TCP. If any lower layer failure happens in the MS, the MS shall: + +- release the TCP connection towards the current GANC, if established, +- Stop timer TU3904 if running, +- release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5, and +- If registration is still unsuccessful after a number of attempts defined by the MS parameter "Up Connect Attempt Count" (defined in sub-clause 12.2.3), the MS shall act as defined in sub-clause 6.2.4.5. +- otherwise, stop timer TU3907 if running and +- start timer TU3905 and wait for it to expire. + +### 6.2.4.3 TU3905 expiry + +If timer TU3905 has expired in the MS, the MS shall restart the Registration procedure as defined in sub-clause 6.2.1. + +### 6.2.4.4 TU3907 expiry + +If timer TU3907 expires in the MS, the MS shall: + +- If GAN registration is unsuccessful after a number of attempts defined by the MS parameter "Up Register Max Retries" (defined in sub-clause 12.2.3), the MS shall act as if a "Lower layer failure in the MS" has occurred as defined in sub-clause 6.2.4.2 +- else, if the TCP connection to the GANC is still established, + - send a GA-RC REGISTER REQUEST that includes information elements as described in sub-clause 6.2.1 and + - start timer TU3904 +- else, restart the GAN Registration procedure towards the GANC as defined in sub-clause 6.2.1 + +### 6.2.4.5 Registration Failure + +The MS shall; + +- If the GANC selection is ongoing: + - act on upper layer indications as follows; + +- If no more PLMNs/GANCs are available for GANC selection or the GANC selection is finished unsuccessfully; + - stop all ongoing registration procedures; + - release the TCP connection towards the current GANC, if established, + - release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5 + - initiate registration towards the Default GANC as defined in sub-clause 6.2.1; +- else if the GANC selection process indicates new PLMN/GANC selection: + - initiate registration procedure towards the GANC associated with the selected PLMN as defined in sub-clause 6.2. +- else if the MS attempted the registration towards the Default GANC + - delete the stored information about the Default GANC, + - delete the contents of the stored Serving GANC table + - Increment Redirection Counter + - initiate Discovery Procedure as defined in sub-clause 5.3 +- else if the MS attempted the registration towards current GANC is a Serving GANC + - Update the stored Serving GANC table as defined in the end of sub-clause 6.2.3.3 (i.e. delete information about this Serving GANC in the table) and + - Increment Redirection Counter + - initiate Registration Procedure towards the Default GANC as defined in sub-clause 6.2.1 + +#### 6.2.4.6 GAN mode selection related failures + +If no GAN Mode Indicator IE is included in the GA-RC REGISTER ACCEPT message or if the GAN Mode Indicator IE is included and indicates that the MS shall operate in GAN A/Gb mode, but the MS does not support GAN A/Gb mode, then the MS shall immediately initiate GAN deregistration per sub-clause 6.4.1 and then proceed according to the registration reject procedures defined for the case of 'Invalid GANC' in sub-clause 6.2.3.3. + +If the GAN Mode Indicator IE is included in the GA-RC REGISTER ACCEPT message and indicates that the MS shall operate in GAN Iu mode, but the MS does not support GAN Iu mode, then the MS shall immediately initiate GAN deregistration per sub-clause 6.4.1 and then proceed according to the registration reject procedures defined for the case of 'Invalid GANC' in sub-clause 6.2.3.3. + +### 6.3 Registration Update procedure + +After the MS has successfully registered to a GANC, the MS shall update the GANC as a result of the conditions described in sub-clause 6.3.1: This update is performed using the Registration Update procedure. + +The GANC may also use the Registration Update procedure towards the MS. + +![Sequence diagram of Registration Update procedure initiated by the MS. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RRC-IDLE state. It sends a '1. GA-RRC REQUEST' message to the GANC. The GANC responds with '2. GA-RRC REQUEST ACCEPT'. The MS then transitions to the GA-RRC-CONNECTED state. The procedure is triggered by 'Start TU5908' and ends with 'Stop TU5908'.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-IDLE + Note left of MS: Start TU5908 + MS->>GANC: 1. GA-RRC REQUEST + GANC-->>MS: 2. GA-RRC REQUEST ACCEPT + Note left of MS: Stop TU5908 + Note left of MS: GA-RRC-CONNECTED + +``` + +Sequence diagram of Registration Update procedure initiated by the MS. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RRC-IDLE state. It sends a '1. GA-RRC REQUEST' message to the GANC. The GANC responds with '2. GA-RRC REQUEST ACCEPT'. The MS then transitions to the GA-RRC-CONNECTED state. The procedure is triggered by 'Start TU5908' and ends with 'Stop TU5908'. + +**Figure 6.3.1: Registration Update procedure initiated by the MS** + +![Sequence diagram of Registration Update procedure initiated by the network. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-PSR ACTIVE state. The GANC sends a 'GA-PSR UPLINK QUALITY INDICATION' message to the MS. The MS responds with 'GA-PSR HANDOVER INFORMATION'. The GANC then sends a 'GA-PSR HANDOVER COMMAND' to the MS. The MS responds with 'GA-PSR HANDOVER FAILURE'. The procedure is triggered by 'Start TU4004' and ends with 'Stop TU4004'.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR UPLINK QUALITY INDICATION + MS-->>GANC: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + MS-->>GANC: GA-PSR HANDOVER FAILURE + Note left of MS: Stop TU4004 + +``` + +Sequence diagram of Registration Update procedure initiated by the network. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-PSR ACTIVE state. The GANC sends a 'GA-PSR UPLINK QUALITY INDICATION' message to the MS. The MS responds with 'GA-PSR HANDOVER INFORMATION'. The GANC then sends a 'GA-PSR HANDOVER COMMAND' to the MS. The MS responds with 'GA-PSR HANDOVER FAILURE'. The procedure is triggered by 'Start TU4004' and ends with 'Stop TU4004'. + +**Figure 6.3.2: Registration Update procedure initiated by the network** + +### 6.3.1 Register Update initiation by the MS + +MS initiates this procedure when it has registered successfully to GANC and any of the following occurs: + +- The MS acquires GERAN/UTRAN/E-UTRAN coverage for the first time after reporting no coverage during its last GAN registration. +- An MS registered for GAN Iu mode establishes a new UTRAN serving cell as a result of Intra-RAT handover while in GERAN/UTRAN/E-UTRAN mode and the UARFCN of the new UTRAN serving cell is different from the UARFCN indicated during its last GAN Registration or GAN Registration Update. +- An MS registered for GAN Iu mode establishes a new serving cell as a result of Inter-RAT handover to UTRAN while in GERAN/UTRAN/E-UTRAN mode. +- An MS registered for GAN Iu mode enters connected mode in a UTRAN cell while in GERAN/UTRAN/E-UTRAN mode and the UARFCN of the serving UTRAN cell is different from the UARFCN indicated during its last GAN Registration/GAN Registration Update or a UARFCN was not provided during its last GAN Registration/GAN Registration Update. +- An MS operating in GERAN/UTRAN/E-UTRAN preferred mode and registered for GAN Iu mode enters dedicated/Packet Transfer mode in a GERAN cell while in GERAN/UTRAN/E-UTRAN mode and the GERAN serving cell is different from the one indicated during its last GAN Registration/GAN Registration Update. +- An MS operating in GERAN/UTRAN/E-UTRAN preferred mode and registered for GAN A/Gb mode establishes a new GERAN serving cell as a result of Intra-RAT/inter-RAT handover while in GERAN/UTRAN/E-UTRAN mode. +- An MS operating in GERAN/UTRAN/E-UTRAN preferred mode and registered for GAN A/Gb mode establishes a new UTRAN serving cell as a result of intra-RAT/inter-RAT handover while in GERAN/UTRAN/E-UTRAN mode. +- An MS operating in GERAN/UTRAN/E-UTRAN preferred mode and registered for GAN A/Gb mode enters dedicated/Packet Transfer mode in a GERAN cell, or enters connected mode in a UTRAN cell or enters connected mode in a E-UTRAN cell while in GERAN/UTRAN/E-UTRAN mode and the GERAN/UTRAN/E- + +UTRAN serving cell is different from the one indicated during its last GAN Registration/GAN Registration Update. + +- Changes to the generic IP access network point of attachment (i.e. a new radio link is established). +- When the mobile station requires a change to the list of GAN services previously requested within the Required GAN Services IE of a GAN Registration. + +The MS shall: + +- send a GA-RC REGISTER UPDATE UPLINK message to the GANC on the established TCP connection and include the changed information in the message. + +## 6.3.2 Register Update processing by the network + +When receiving the GA-RC REGISTER UPDATE UPLINK message, the network may either accept or reject the Registration Update. The network may also redirect the MS to another GANC. + +### 6.3.2.1 Register Update Accepted + +If the network accepts the Registration Update, no message is returned to the MS. + +### 6.3.2.2 Register Update Rejected + +If the network rejects the Registration Update, it shall send the GA-RC DEREGISTER message to the MS. This message shall contain the Register Reject Cause information element. + +### 6.3.2.3 Register Update results in redirection + +If the network decides to redirect the MS to another GANC, it shall send the GA-RC REGISTER REDIRECT message to the MS. This message shall contain valid information about another GANC, so that the MS is able to initiate the Registration procedure towards that GANC. + +The GANC can send the GA-RC REGISTER REDIRECT message at any time, but it shall not be sent to an MS in GA-CSR-DEDICATED or GA-PSR-ACTIVE state. + +## 6.3.3 Register Update Response handling in the MS + +### 6.3.3.1 Register Update Rejected + +When the MS receives the GA-RC DEREGISTER message, it shall act as defined in sub-clause 6.4.4 "Reception of GA-RC DEREGISTER by MS". + +### 6.3.3.2 Register Update results in redirection + +When the MS receives GA-RC REGISTER REDIRECT message, it shall act as defined in sub-clause 6.2.3.2 "Registration redirected". + +## 6.3.4 Register Update initiation by the network + +The network may at any time send the GA-RC REGISTER UPDATE DOWNLINK message to a MS that is registered. This could happen e.g. because of change in the GANC System Information. The network may include all information in this message (i.e. not necessarily only the changed information). + +## 6.3.5 Register Update handling in the MS + +When the MS receives GA-RC REGISTER UPDATE DOWNLINK message, it shall process the received information elements as defined in sub-clause 6.2.3.1. + +## 6.4 MS deregistration + +The MS should attempt to perform deregistration procedure before leaving the AP. Optionally, the network could also initiate deregistration of a MS. + +![Sequence diagram for Figure 6.4.1: Deregistration procedure initiated by the MS. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS sends a GA-PSR UPLINK QUALITY INDICATION and GA-PSR HANDOVER INFORMATION to the GANC. The GANC responds with a GA-PSR HANDOVER COMMAND. The MS then sends a GA-PSR HANDOVER FAILURE. The process is triggered by 'Start TU4004' and 'Stop TU4004' events on the MS side. The GA-PSR ACTIVE state is shown on the MS side.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Figure 6.4.1: Deregistration procedure initiated by the MS. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS sends a GA-PSR UPLINK QUALITY INDICATION and GA-PSR HANDOVER INFORMATION to the GANC. The GANC responds with a GA-PSR HANDOVER COMMAND. The MS then sends a GA-PSR HANDOVER FAILURE. The process is triggered by 'Start TU4004' and 'Stop TU4004' events on the MS side. The GA-PSR ACTIVE state is shown on the MS side. + +**Figure 6.4.1: Deregistration procedure initiated by the MS** + +![Sequence diagram for Figure 6.4.2: Deregistration procedure initiated by the network. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The GANC sends a GA-PSR UPLINK QUALITY INDICATION and GA-PSR HANDOVER INFORMATION to the MS. The MS responds with a GA-PSR HANDOVER COMMAND. The GANC then sends a GA-PSR HANDOVER FAILURE. The process is triggered by 'Start TU4004' and 'Stop TU4004' events on the MS side. The GA-PSR ACTIVE state is shown on the MS side.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC->>MS: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER INFORMATION + MS->>GANC: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Figure 6.4.2: Deregistration procedure initiated by the network. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The GANC sends a GA-PSR UPLINK QUALITY INDICATION and GA-PSR HANDOVER INFORMATION to the MS. The MS responds with a GA-PSR HANDOVER COMMAND. The GANC then sends a GA-PSR HANDOVER FAILURE. The process is triggered by 'Start TU4004' and 'Stop TU4004' events on the MS side. The GA-PSR ACTIVE state is shown on the MS side. + +**Figure 6.4.2: Deregistration procedure initiated by the network** + +### 6.4.1 Deregistration initiated by the MS + +When the MS is leaving or about to leave the GAN coverage and the MS has successfully registered with a GANC, it should: + +- send the GA-RC DEREGISTER message (with Register Reject Cause = Unspecified) using the currently established TCP-connection, +- release the TCP connection towards the GANC, +- release the secure connection towards the SEGW, as defined in sub-clause 4.5 and +- release all resources related to GAN + +### 6.4.2 Reception of GA-RC DEREGISTER by GANC + +When the network receives the GA-RC DEREGISTER message, it shall release all resources associated with the MS. + +### 6.4.3 Deregistration initiated by the network + +The GANC may at any time initiate the deregistration of a successfully registered MS by sending the GA-RC DEREGISTER message to the MS. When the GA-RC layer in the network has submitted the GA-RC DEREGISTER message to the TCP layer, it may initiate release of its half of the bidirectional TCP connection. + +### 6.4.4 Reception of GA-RC DEREGISTER by MS + +When the MS receives the GA-RC DEREGISTER message, it shall: + +- if the MS is in the process of PLMN selection; + - ignore the received Register Reject Cause Information Element, and + - proceed as defined in sub-clause 6.2.4.5. +- else extract the Reject Cause information element and act as following depending on the value of the Reject Cause IE: +- 'Network Congestion' + - release all local GAN resources (e.g. MS is in active call over GAN) + - release the TCP connection towards the current GANC and + +- release the secure connection towards the GANC-SEGW, as defined in sub-clause 4.5 +- create a random value between zero and the received value in IE 'TU3907 Timer' and +- add this value to the received value in IE 'TU3907 Timer', and use this as the new value for TU3907 +- start timer TU3907 according to the new calculated value +- 'AP not allowed' + - release the TCP connection established to the GANC, if still established, + - release the secure connection towards the SEGW associated with the GANC, as defined in sub-clause 4.5, + - store the AP-ID in the AP Black List of and not initiate a new Register Request from this AP, until the AP-ID is removed from the AP black list i.e. as a result of power-cycle. +- 'Location not allowed' + - release the TCP connection established to the GANC, if still established, + - release the secure connection towards the SEGW associated with the GANC, as defined in sub-clause 4.5, + - update the Location Black List according to the received information elements Location Black List indicator and Location Area Identification and not initiate a new Register Request from that Location, until the Location is removed from the Location Black List i.e. as a result of power-cycle. +- 'IMSI not allowed' + - release the TCP connection established to the GANC, if still established. + - release the secure connection towards the SEGW associated with the GANC as defined in sub-clause 4.5, + - not initiate a new Registration procedure until the next power-on. +- 'Unspecified' + - release the TCP connection established to the GANC, if still established. + - release the secure connection towards the SEGW associated with the GANC as defined in sub-clause 4.5, + - act as if a "Lower layer failure in the MS" has occurred as defined in sub-clause 6.2.4.2 +- 'Invalid GANC' + - release the TCP connection established to the GANC, if still established. + - release the secure connection towards the SEGW associated with the GANC as defined in sub-clause 4.5, + - act as defined in sub-clause 6.2.4.5 "Registration Failure" +- 'Geo Location not known' + - release the TCP connection established to the GANC, if still established. + - release the secure connection towards the SEGW associated with the GANC as defined in sub-clause 4.5, + - not retry registration from this AP until the location is provided or until the next power-on. + +The MS shall also, + +- Update the stored Serving GANC table as following if the received Reject cause was not 'Network Congestion' or 'Geo Location not known' +- If the MS is in GERAN/UTRAN/E-UTRAN coverage + +- Remove information related to the current GSM CGI, UTRAN cell identity or E-UTRAN cell identity, if exists in the table +- If the MS is not in GERAN/UTRAN/E-UTRAN coverage +- Remove information related to the AP-ID, if exists in the table. + +## 6.5 Keep alive mechanism and TU3906 handling + +When the MS receives the GA-RC REGISTER ACCEPT message, it shall initiate the GA-RC Keep Alive -mechanism by starting timer TU3906 using the TU3906 Timer value received in that message. + +When timer TU3906 expires in the MS, the MS shall send the GA-RC KEEP ALIVE -message to the GANC and start timer TU3906. + +If the MS releases the TCP connection (e.g. because of receiving GA-RC REGISTER REDIRECT, GA-RC REGISTER REJECT and GA-RC DEREGISTER message), then it shall stop timer TU3906. + +![Sequence diagram for Figure 6.5.1: Keep Alive procedure. The diagram shows the interaction between MS and GANC. The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE. The MS starts timer TU4004 upon receiving the first message and stops it upon receiving the last message.](50214d232017279410e9c9db8eb75119_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Figure 6.5.1: Keep Alive procedure. The diagram shows the interaction between MS and GANC. The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE. The MS starts timer TU4004 upon receiving the first message and stops it upon receiving the last message. + +Figure 6.5.1: Keep Alive procedure + +If the MS detects, that it is not able to send the GA-RC KEEP ALIVE message to the network due to lower layer failure, it shall act according to sub-clause 9.5. + +## 6.6 MS Initiated Synchronization after TCP connection reestablishment + +When MS receives TCP RST after TCP connection failure, it shall try to re-establish the signalling connection using GA-RC Synchronization procedure. The following message flow depicts the messages associated with this procedure: + +![Sequence diagram for Figure 6.6.1: MS initiated synchronization procedure. The diagram shows the interaction between MS and GANC. The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE. The MS starts timer TU4004 upon receiving the first message and stops it upon receiving the last message.](5dca16cd6224cb81fefbd38274e5eb80_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Figure 6.6.1: MS initiated synchronization procedure. The diagram shows the interaction between MS and GANC. The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE. The MS starts timer TU4004 upon receiving the first message and stops it upon receiving the last message. + +Figure 6.6.1 MS initiated synchronization procedure + +### 6.6.1 Initiation of the Synchronization Procedure by the MS + +When MS receives TCP RST indicating a TCP connection failure, it shall attempt to re-establish TCP connection once. After successfully re-establishing TCP connection, the MS shall send GA-RC SYNCHRONIZATION INFORMATION to the GANC to synchronize the state information. If TCP connection re-establishment is unsuccessful, the MS shall release the related local GA-CSR and GA-PSR resources (if the MS is operating in GAN A/Gb mode) or GA-RRC resources (if the MS is operating in GAN Iu mode), and continue as per section 9.5 as if a TCP failure other than TCP RST has occurred. + +### 6.6.2 Processing of the Synchronization Information message by the GANC + +Upon receiving the GA-RC SYNCHRONIZATION INFORMATION message from the MS, the GANC updates the MS state information as specified in the request. + +Moreover, the GANC should verify that the binding (IMSI, inner IP address) as received in the GA-RC SYNCHRONIZATION INFORMATION is the same as the one that the MS used as identity for authentication to the GANC-SEGW. + +## 6.7 Transmission of Cell Broadcast Information + +If the GANC has previously received the indication that the mobile station requires to receive the CBS, the GANC may pass the GA-RC CELL BROADCAST INFO message to a mobile station including one or more pages of Cell Broadcast messages. + +![Sequence diagram showing the transmission of Cell Broadcast Information by the network. The diagram illustrates the interaction between the MS (Mobile Station) and the GANC (GSM Access Network Controller). The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE messages. The MS also sends Start TU4004 and Stop TU4004 messages to the GANC.](030c758fd425016b03290c8f11bef69d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram showing the transmission of Cell Broadcast Information by the network. The diagram illustrates the interaction between the MS (Mobile Station) and the GANC (GSM Access Network Controller). The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE messages. The MS also sends Start TU4004 and Stop TU4004 messages to the GANC. + +Figure 6.7.1: Transmission of Cell Broadcast Information by the network + +# 7 GA-CSR elementary procedures + +## 7.1 GA-CSR Connection establishment + +The GA-CSR connection is a logical connection between the MS and the GANC. It is established when the upper layers in the MS request GA-CSR to enter dedicated mode. The MS initiates GA-CSR connection establishment by sending the GA-CSR REQUEST message to the network. When a successful response is received from the network, GA-CSR replies to the upper layer that it has entered dedicated mode. The upper layers have then the possibility to request transmission of messages to the network. These messages are sent to the network using GA-CSR UPLINK DIRECT TRANSFER messages as defined in sub-clause 7.2.1. + +Note that in the case of a network-initiated CS session, the GA-CSR connection is implicitly established when the MS responds to the GA-CSR PAGING REQUEST message from the GANC with the GA-CSR PAGING RESPONSE message (see sub-clause 7.3). + +Also, in the case of CS handover from GERAN or UTRAN to GAN A/Gb mode, the GA-CSR connection is implicitly established when the MS sends the GA-CSR HANDOVER ACCESS message to the GANC (see sub-clause 7.7). + +Two service access points are defined which are discriminated by their Service Access Point Identifiers (SAPI): + +- SAPI 0: supports the transfer of signalling information including user-user information; +- SAPI 3: supports the transfer of user short messages. + +![Sequence diagram for Figure 7.1.1: Initiation of GA-CSR connection, successful case. The diagram shows the interaction between MS (Mobile Station) and GANC (GAN Controller).](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note over MS: GA-PSR +ACTIVE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Figure 7.1.1: Initiation of GA-CSR connection, successful case. The diagram shows the interaction between MS (Mobile Station) and GANC (GAN Controller). + +**Figure 7.1.1 Initiation of GA-CSR connection, successful case** + +![Sequence diagram for Figure 7.1.2: Initiation of GA-CSR connection, failure case. This diagram shows the same sequence of messages as Figure 7.1.1.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note over MS: GA-PSR +ACTIVE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Figure 7.1.2: Initiation of GA-CSR connection, failure case. This diagram shows the same sequence of messages as Figure 7.1.1. + +**Figure 7.1.2 Initiation of GA-CSR connection, failure case** + +### 7.1.1 Initiation of GA-CSR connection establishment by the MS + +The MS initiates the establishment of the GA-CSR connection when the upper layers request the GA-CSR to enter dedicated state. + +Before initiation of GA-CSR connection establishment request, the MS shall check for access permission based on Access Control Class bits returned within GA-RC REGISTER ACCEPT message as defined in [12]. + +If it is allowed for the MS to access the network, it shall send a GA-CSR REQUEST message to the GANC on the established TCP connection and include the Establishment Cause IE and start timer TU3908 + +### 7.1.2 Reception of GA-CSR REQUEST by GANC + +When GANC receives GA-CSR REQUEST message, the GANC may either accept or reject the GA-CSR connection establishment request. + +#### 7.1.2.1 GA-CSR connection establishment request accepted + +If the GANC accepts the GA-CSR connection establishment request, it shall send the GA-CSR REQUEST ACCEPT message to the MS. + +#### 7.1.2.2 GA-CSR connection establishment request rejected + +If the GANC rejects the GA-CSR connection establishment request, it shall send the GA-CSR REQUEST REJECT message to the MS. + +### 7.1.3 GA-CSR connection establishment response handling in the MS + +#### 7.1.3.1 GA-CSR connection establishment request accepted + +When the MS receives the GA-CSR REQUEST ACCEPT message, it shall: + +- if timer TU3908 is active: + - stop timer TU3908, + - move into GA-CSR-DEDICATED state, + - indicate to upper layers that GA-CSR has entered dedicated state and + - send the initial GA-CSR UPLINK DIRECT TRANSFER message to the network +- if timer TU3908 is not active: + - ignore the GA-CSR REQUEST ACCEPT message and + - continue with any ongoing procedure as if the GA-CSR REQUEST ACCEPT message was not received + +#### 7.1.3.2 GA-CSR connection establishment request rejected + +When the MS receives the GA-CSR REQUEST REJECT message, it shall: + +- if timer TU3908 is active: + - stop timer TU3908, + - remain in GA-CSR-IDLE state and + - indicate to upper layers that GA-CSR was not able to enter dedicated state +- if timer TU3908 is not active: + - ignore the GA-CSR REQUEST REJECT message and + - continue with any ongoing procedure as if the GA-CSR REQUEST REJECT message was not received + +### 7.1.4 Failure cases + +#### 7.1.4.1 Timer TU3908 expiry + +If timer TU3908 expires in the MS, the MS shall remain in GA-CSR-IDLE state and indicate to upper layers that GA-CSR was not able to enter dedicated state + +## 7.2 Upper layer message transmission + +The GA-CSR UPLINK DIRECT TRANSFER message is used for the transfer of upper layer messages from the MS to the GANC while the GA-CSR DOWNLINK DIRECT TRANSFER message is used for the transfer of upper layer messages from the GANC to the MS. The first GA-CSR UPLINK DIRECT TRANSFER message received by the GANC triggers the establishment of the signalling connection to the CN for that MS. + +### 7.2.1 Upper layer message forwarding by the MS + +![Sequence diagram for Uplink Direct Transfer, normal flow. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC), 2. GA-PSR HANDOVER INFORMATION (GANC to MS, triggered by Start TU4004), 3. GA-PSR HANDOVER COMMAND (MS to GANC, triggered by Stop TU4004), 4. GA-PSR HANDOVER FAILURE (GANC to MS).](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION (Start TU4004) + MS->>GANC: GA-PSR HANDOVER COMMAND (Stop TU4004) + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Uplink Direct Transfer, normal flow. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC), 2. GA-PSR HANDOVER INFORMATION (GANC to MS, triggered by Start TU4004), 3. GA-PSR HANDOVER COMMAND (MS to GANC, triggered by Stop TU4004), 4. GA-PSR HANDOVER FAILURE (GANC to MS). + +Figure 7.2.1.1 Uplink Direct Transfer, normal flow + +The MS shall initiate the Uplink Direct Transfer procedure in GA-CSR-DEDICATED state when the upper layers request a transfer of a non-access stratum message. + +The MS shall include the contents of the received upper layer message in the IE "L3 Message" and set the SAPI used in the IE "SAPI ID". + +### 7.2.2 Reception of GA-CSR UPLINK DIRECT TRANSFER by GANC + +When the GANC receives GA-CSR UPLINK DIRECT TRANSFER message from an MS in GA-CSR-DEDICATED state for which there is no signalling connection to the core network (i.e. this is the first GA-CSR UPLINK DIRECT TRANSFER after GA-CSR Connection establishment) the GANC should trigger the normal A-interface procedures towards the Core network to establish a signalling connection. GANC should transfer the contents of the IE "L3 Message" to the CN. The GANC should transfer the contents of the IE "SAPI ID" to the CN. + +### 7.2.3 Upper layer message forwarding by the GANC + +![Sequence diagram for Downlink Direct Transfer, normal flow. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC), 2. GA-PSR HANDOVER INFORMATION (GANC to MS, triggered by Start TU4004), 3. GA-PSR HANDOVER COMMAND (MS to GANC, triggered by Stop TU4004), 4. GA-PSR HANDOVER FAILURE (GANC to MS).](762a17cd79880dbca172bcbbe9375223_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION (Start TU4004) + MS->>GANC: GA-PSR HANDOVER COMMAND (Stop TU4004) + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Downlink Direct Transfer, normal flow. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC), 2. GA-PSR HANDOVER INFORMATION (GANC to MS, triggered by Start TU4004), 3. GA-PSR HANDOVER COMMAND (MS to GANC, triggered by Stop TU4004), 4. GA-PSR HANDOVER FAILURE (GANC to MS). + +Figure 7.2.3.1 Downlink Direct Transfer, normal flow + +The Downlink Direct Transfer procedure is initiated by the GANC, when the GANC receives a request from the upper layers to transfer a non-access stratum message, after the establishment of the GA-CSR connection to the MS. + +On receiving a request from the upper layers the GANC should include the contents of the upper layer message in the IE "L3 Message". + +### 7.2.4 Reception of GA-CSR DOWNLINK DIRECT TRANSFER by the MS + +When the MS receives the GA-CSR DOWNLINK DIRECT TRANSFER message it shall forward the contents of the message to the upper layers. + +#### 7.2.4.1 Invalid GA-CSR DOWNLINK DIRECT TRANSFER + +If the MS receives a GA-CSR DOWNLINK DIRECT TRANSFER message and MS is not in GA-CSR-DEDICATED state, the MS shall: + +- ignore the contents of the GA-CSR DOWNLINK DIRECT TRANSFER message; +- transmit a GA-CSR STATUS message as follows: + - set the IE "RR Cause" to "Message type not compatible with protocol state" + - include the received message contents in the IE "PDU in error" +- continue with any ongoing procedure and act as if the GA-CSR DOWNLINK DIRECT TRANSFER message was not received. + +## 7.3 Paging for CS domain + +![Sequence diagram showing the normal flow of paging for the CS domain between an MS and a GANC. The MS is in the GA-PSR ACTIVE state. The sequence starts with the GANC sending a GA-PSR UPLINK QUALITY INDICATION to the MS. The MS responds with GA-PSR HANDOVER INFORMATION. The GANC then sends a GA-PSR HANDOVER COMMAND to the MS, which starts timer TU4004. The MS responds with GA-PSR HANDOVER FAILURE, which stops timer TU4004.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC->>MS: GA-PSR UPLINK QUALITY INDICATION + MS-->>GANC: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Start TU4004 + MS-->>GANC: GA-PSR HANDOVER FAILURE + Note left of MS: Stop TU4004 + +``` + +Sequence diagram showing the normal flow of paging for the CS domain between an MS and a GANC. The MS is in the GA-PSR ACTIVE state. The sequence starts with the GANC sending a GA-PSR UPLINK QUALITY INDICATION to the MS. The MS responds with GA-PSR HANDOVER INFORMATION. The GANC then sends a GA-PSR HANDOVER COMMAND to the MS, which starts timer TU4004. The MS responds with GA-PSR HANDOVER FAILURE, which stops timer TU4004. + +Figure 7.3.1 Paging, normal flow + +### 7.3.1 Initiation of Paging + +The GANC initiates this procedure when it receives a PAGING REQUEST message over the A-interface or a Paging CS message over the Gb-interface. The MS to be paged is identified by the identity received in the request from the CN. If the request includes the TMSI then the GANC should include the TMSI as the mobile identity else it should include the IMSI received in the request. + +### 7.3.2 Reception of GA-CSR PAGING REQUEST by the MS + +If the mobile identity in the GA-CSR PAGING REQUEST message matches any of the valid identities of the MS and the MS is in GA-CSR-IDLE state, the MS shall: + +- if timer TU3908 is not active and access to the network is allowed; + - send a GA-CSR PAGING RESPONSE message to the GANC and + - enter GA-CSR-DEDICATED state. +- if timer TU3908 is active; +- discard the received GA-CSR PAGING REQUEST message. + +### 7.3.3 Reception of GA-CSR PAGING RESPONSE by the GANC + +On receiving the GA-CSR PAGING RESPONSE message the GANC should establish the signalling connection to the MSC and forward the contents of the GA-CSR PAGING RESPONSE message to the MSC. + +### 7.3.4 Abnormal Cases + +If the MS receives a GA-CSR PAGING REQUEST message and MS is in GA-CSR-DEDICATED state or GA-RC-REGISTERED state, the MS shall: + +- ignore the GA-CSR PAGING REQUEST message +- continue with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received. + +If the MS receives a GA-CSR PAGING REQUEST and the mobile identity included in the message does not match any of the valid identities assigned to the MS, the MS shall: + +- ignore the GA-CSR PAGING REQUEST message +- continue with any ongoing procedure as if the GA-CSR PAGING REQUEST message was not received. + +## 7.4 Traffic Channel assignment + +![Sequence diagram showing the successful case of channel activation between MS and GANC. The MS is in GA-PSR ACTIVE state. The sequence starts with 'Start TU4004' at the MS, followed by 'GA-PSR HANDOVER INFORMATION' from MS to GANC, 'GA-PSR HANDOVER COMMAND' from GANC to MS, 'Stop TU4004' at the MS, and finally 'GA-PSR HANDOVER FAILURE' from MS to GANC. A dashed arrow labeled 'GA-PSR UPLINK QUALITY INDICATION' points from GANC to MS.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR HANDOVER INFORMATION (Start TU4004) + GANC-->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + +``` + +Sequence diagram showing the successful case of channel activation between MS and GANC. The MS is in GA-PSR ACTIVE state. The sequence starts with 'Start TU4004' at the MS, followed by 'GA-PSR HANDOVER INFORMATION' from MS to GANC, 'GA-PSR HANDOVER COMMAND' from GANC to MS, 'Stop TU4004' at the MS, and finally 'GA-PSR HANDOVER FAILURE' from MS to GANC. A dashed arrow labeled 'GA-PSR UPLINK QUALITY INDICATION' points from GANC to MS. + +Figure 7.4.1 Channel Activation, successful case + +### 7.4.1 Initiation of Channel Assignment + +The GANC configures a traffic channel by transmitting the GA-CSR ACTIVATE CHANNEL message on receiving an Assignment Request from the MSC. The GA-CSR ACTIVATE CHANNEL message can be sent to the MS only in GA-CSR-DEDICATED state. The Channel Assignment procedure is always activated by the network. + +### 7.4.2 Reception of GA-CSR ACTIVATE CHANNEL by MS + +The MS shall act on the received GA-CSR ACTIVATE CHANNEL message when in GA-CSR-DEDICATED state as follows: + +- Code and decode the CS payload samples according to the IE "Channel Mode"; +- If the IE "Bandwidth-efficient Mode Indicator" is received, use the RFC 4867 [48] bandwidth-efficient payload format to code and decode the CS payload samples; otherwise, use the RFC 4867 [48] octet-aligned payload format. +- Use the value indicated by the IE "Sample Size" as the minimum sampling size for the coding and decoding of the CS payload samples, if the MS is not able to use the indicated value. If AMR is used with FEC by sending redundant frames, the sample size is defined as the size of the new speech sample in each RTP packet, not including any redundant speech sample. +- Configure the uplink CS payload stream to be transmitted to the UDP port identified by the IE "UDP Port"; +- Configure the uplink CS payload stream to be transmitted to the IP address identified by the IE "IP address"; + +- If received, use the configuration included in the IE 'Multi-rate Configuration' for the CS payload stream; +- If received, use the configuration included in the IE "RTP Redundancy Configuration" for the CS payload stream. The redundancy policy is defined for each of the AMR modes to use. The level of redundancy can span from no redundancy to double redundancy. In the same active codec set, a lower codec mode shall not be associated with a lower redundancy level than a higher codec mode. For example, the highest mode in the set is used with no redundancy, the next lower with single redundancy and rest of the modes with double redundancy; +- If received, use the Payload Type included in the IE 'Payload Type' for the PT field in the RTP header for the CS downlink and uplink payload streams; + +On successful configuration of the channel, the MS shall: + +- Start timer TU3911. +- Transmit a GA-CSR ACTIVATE CHANNEL ACK message and include the UDP port number in the IE 'UDP Port' for the downlink CS payload stream to be used by the GANC. +- Include the selected RTP sample size, to be used uplink and downlink, in the IE Sample Size. +- if the IE 'RTCP UDP Port' was received in the GA-CSR ACTIVATE CHANNEL message and the MS is capable of supporting RTCP, activate the uplink RTCP stream and include the IE 'RTCP UDP Port' for the downlink RTCP stream to be used by the GANC. + +### 7.4.3 Reception of GA-CSR ACTIVATE CHANNEL ACK by GANC + +If the call uses a TDM-based A-interface: The GANC shall configure itself for transmission of RTP packets to the MS to the indicated UDP port and RTCP packets to the MS, if the IE 'RTCP UDP Port' is included by the MS, and transmit a GA-CSR ACTIVATE CHANNEL COMPLETE message to the MS. + +If the call uses a TDM-based A-interface: To enable downlink quality measurements in the MS, the GANC shall send at least one RTP frame each 480 ms. During periods of discontinuous transmission (DTX), each RTP frame transmitted by the GANC shall bear a format in the AMR payload Table of Contents that either (a) omits all NO\_DATA indications and contains only the next AMR speech or SID frame that is available, or (b) includes a single NO\_DATA frame should no AMR speech or SID frame become available for 480 ms. The RTP timestamp shall indicate the time of that speech or SID or NO\_DATA frame. See Section A.1.2 of Annex A for examples of the RFC 4867 [48] octet-aligned payload format. + +If the call uses a IP-based A-interface: The GANC sends a GA-CSR ACTIVATE CHANNEL COMPLETE message to the UE. + +### 7.4.4 Reception of GA-CSR ACTIVATE CHANNEL COMPLETE by MS + +The RTP channel is available for use by upper layers. To enable uplink quality measurements in the GANC, the MS shall send at least one RTP frame each 480 ms. During periods of discontinuous transmission (DTX), each RTP frame transmitted by the MS shall bear a format in the AMR payload Table of Contents that either (a) omits all NO\_DATA indications and contains only the next AMR speech or SID frame that is available, or (b) includes a single NO\_DATA frame should no AMR speech or SID frame become available for 480 ms. The RTP timestamp shall indicate the time of that speech or SID or NO\_DATA frame. See Section A.1.2 of Annex A for examples of the RFC 4867 [48] octet-aligned payload format. + +Stop timer TU3911. + +### 7.4.5 Failure to establish channel by MS + +If the MS fails to establish the channel indicated in the GA-CSR ACTIVATE CHANNEL message or timer TU3911 expires the MS shall: + +- transmit a GA-CSR ACTIVATE CHANNEL FAILURE message; +- act as if the GA-CSR ACTIVATE CHANNEL message was not received. + +## 7.5 Release of GA-CSR + +### 7.5.1 Initiation of GA-CSR connection release by MS + +If the MS needs to release the GA-CSR connection and signalling connection to the core network, it shall send the GA-CSR CLEAR REQUEST message to the GANC and start timer TU3909. The MS shall include the 'RR Cause' IE. + +![Sequence diagram for Initiation of GA-CSR connection release by MS. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from MS to GANC); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS); 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC). The start of the sequence is marked 'Start TU4004' and the end is marked 'Stop TU4004'.](552328a9daaf3bc0069424b500025880_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Initiation of GA-CSR connection release by MS. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from MS to GANC); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS); 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC). The start of the sequence is marked 'Start TU4004' and the end is marked 'Stop TU4004'. + +Figure 7.5.1.1 Initiation of GA-CSR connection release by MS + +### 7.5.2 Reception of GA-CSR CLEAR REQUEST by GANC + +The GANC will request core network to initiate the procedure to release of dedicated resources. + +### 7.5.3 Initiation of GA-CSR connection release by GANC + +![Sequence diagram for Initiation of GA-CSR connection release by network. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from MS to GANC); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS); 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC). The start of the sequence is marked 'Start TU4004' and the end is marked 'Stop TU4004'.](215165a27ad7d72bd39fdf55a3cb7486_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Initiation of GA-CSR connection release by network. The diagram shows the MS (Mobile Station) and GANC (GAN Controller) interacting. The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from MS to GANC); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS); 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC). The start of the sequence is marked 'Start TU4004' and the end is marked 'Stop TU4004'. + +Figure 7.5.3.1 Initiation of GA-CSR connection release by network + +The GANC initiates this procedure to command the MS to release the GA-CSR and any traffic channel resources and instruct the MS to leave GA-CSR-DEDICATED state. + +The GA-CSR RELEASE message will include an RR cause indication as follows: + +- #0: normal release, e.g. at the end of a call. +- #1: unspecified abnormal release. +- #65: if e.g. a handover procedure is stopped because the call has been cleared. + +### 7.5.4 Reception of GA-CSR RELEASE by MS + +When the MS receives the GA-CSR RELEASE message, it shall: + +- transmit a GA-CSR RELEASE COMPLETE message to the GANC and release all GA-CSR and any traffic channel resources, + +- stop timer TU3909 (if running), and +- enter GA-CSR-IDLE state. + +A mobile station not supporting "GPRS" shall consider the IE "GPRS Resumption" as unknown in the GA-CSR RELEASE message and perform the GA-CSR Release procedure as normal. + +For a MS supporting the "GPRS" option: + +- if the GA-CSR RELEASE message includes the IE "GPRS Resumption": + - if the GPRS Resumption information element indicates that the network has resumed GPRS services, the GA-CSR sub-layer of the mobile station shall indicate a GA-CSR GPRS resumption complete to the MM sub-layer. + - if the GPRS Resumption information element indicates that the network has not successfully resumed GPRS services, the GA-CSR sub-layer of the mobile station shall indicate a GPRS resumption failure to the MM sub-layer. +- if the mobile station has performed the GPRS suspension procedure (sub-clause 8.10) and the GPRS Resumption information element is not included in the message, the GA-CSR sub-layer of the mobile station shall indicate a GPRS resumption failure to the MM sub-layer. +- if the mobile station has not performed the GPRS suspension procedure and the GPRS Resumption information element is not included in the message, the mobile station shall perform the channel release procedure as normal + +## 7.5.5 Failure cases + +### 7.5.5.1 Timer TU3909 expiry + +If timer TU3909 expires in the MS, the MS shall release all GA-CSR and any traffic channel resources and enter GA-CSR-IDLE state. + +## 7.6 Classmark Indication + +### 7.6.1 Initiation of classmark interrogation by GANC + +![Sequence diagram showing the initiation of classmark interrogation by GANC. The diagram shows interactions between MS (GA-PSR ACTIVE) and GANC. The sequence starts with GA-PSR UPLINK QUALITY INDICATION from MS to GANC, followed by GA-PSR HANDOVER INFORMATION from GANC to MS (triggered by Start TU4004), then GA-PSR HANDOVER COMMAND from GANC to MS (triggered by Stop TU4004), and finally GA-PSR HANDOVER FAILURE from MS to GANC.](ae375ead8aa673286b534e079e9a8533_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION (Start TU4004) + GANC->>MS: GA-PSR HANDOVER COMMAND (Stop TU4004) + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram showing the initiation of classmark interrogation by GANC. The diagram shows interactions between MS (GA-PSR ACTIVE) and GANC. The sequence starts with GA-PSR UPLINK QUALITY INDICATION from MS to GANC, followed by GA-PSR HANDOVER INFORMATION from GANC to MS (triggered by Start TU4004), then GA-PSR HANDOVER COMMAND from GANC to MS (triggered by Stop TU4004), and finally GA-PSR HANDOVER FAILURE from MS to GANC. + +Figure 7.6.1.1 Classmark change + +The GANC initiates the classmark interrogation procedure by transmitting the GA-CSR CLASSMARK ENQUIRY message to the MS when it desires more information about the MS's capabilities. The GA-CSR CLASSMARK ENQUIRY message can be sent to a MS only in GA-CSR-DEDICATED state. + +## 7.6.2 Transmission of classmark information by MS + +On receipt of the GA-CSR CLASSMARK ENQUIRY message or in case of "early classmark sending" procedure based on the system information indication received in GA-RC REGISTER ACCEPT message, the mobile station sends a GA-CSR CLASSMARK CHANGE message to the GANC. + +The MS shall include the IE "Mobile Classmark 2" in the GA-CSR CLASSMARK CHANGE message. It may also contain a IE "Mobile Classmark 3" depending on the MS capabilities. + +In addition a MS supporting UTRAN sends a GA-CSR UTRAN CLASSMARK CHANGE message. + +The Classmark Enquiry Mask information element in the GA-CSR CLASSMARK ENQUIRY message indicates the type of request. If the Classmark Enquiry Mask information element is not included in the GA-CSR CLASSMARK ENQUIRY message, this indicates a request for GA-CSR CLASSMARK CHANGE message. + +In the "early classmark sending" case the GA-CSR UTRAN CLASSMARK CHANGE message shall not be sent by the MS if prohibited by the 3G Early Classmark Sending Restriction received as system information in GA-RC REGISTER ACCEPT message. + +The GA-CSR UTRAN CLASSMARK CHANGE and GA-CSR CLASSMARK CHANGE message shall only be sent by a MS in GA-CSR-DEDICATED state + +When an GA-CSR CLASSMARK CHANGE message and an GA-CSR UTRAN CLASSMARK CHANGE message are to be sent, the GA-CSR CLASSMARK CHANGE message shall be sent first. + +## 7.7 CS handover to GAN A/Gb mode + +![Sequence diagram for CS handover to GAN A/Gb mode, successful case 7.7.1 Initiation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC, labeled 'Start TU4004'); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, labeled 'Stop TU4004'); 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC).](2c38051409fe1c92ed774b445a768886_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + MS->>GANC: GA-PSR HANDOVER INFORMATION (Start TU4004) + GANC->>MS: GA-PSR HANDOVER COMMAND (Stop TU4004) + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for CS handover to GAN A/Gb mode, successful case 7.7.1 Initiation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC, labeled 'Start TU4004'); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, labeled 'Stop TU4004'); 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC). + +**Figure 7.7.1: CS handover to GAN A/Gb mode, successful case 7.7.1 Initiation** + +The procedure is initiated when the source radio access technology (e.g. GERAN) orders the MS to make CS handover to GAN A/Gb mode. + +The procedure is applicable in GA-RC-REGISTERED state provided the conditions described in Annex C.1: "(Source-RAT) Measurement Report for Handover and Cell Change Order to GAN A/Gb mode" are met. + +The handover order in the source radio access technology mode is sent via the (RR) HANDOVER COMMAND message. If the ARFCN and BSIC parameters included in the Cell Description IE in the (RR) HANDOVER COMMAND message (specified in [12]) match those of the GAN cell, the MS shall: + +- send a GA-CSR HANDOVER ACCESS message to the network including the complete (RR) HANDOVER COMMAND message in the *Handover To GAN Command* IE and enter GA-CSR-DEDICATED state; + +NOTE: sending the complete (RR) HANDOVER COMMAND message in the *Handover To GAN Command* IE instead of the *Handover Reference* IE allows for more than 256 concurrent handover requests + +- if non-signalling mode is indicated in *Channel Mode* IE, the MS shall: + +- start timer TU3920; +- otherwise, the MS shall: + - immediately send a GA-CSR HANDOVER COMPLETE message to the network; + - switch to GAN A/Gb mode; i.e. attach the GA-CSR entity to the RR-SAP. + +## 7.7.2 Reception of GA-CSR HANDOVER ACCESS by the GANC + +If non-signalling mode is indicated in the *Channel Mode* IE, the GANC shall initiate traffic channel assignment as specified in sub-clause 7.4. + +## 7.7.3 Successful completion of the CS handover to GAN A/Gb mode + +If the traffic channel assignment was successfully completed within timer TU3920, the MS shall: + +- stop timer TU3920; +- send a GA-CSR HANDOVER COMPLETE message to the network; +- switch to GAN A/Gb mode; i.e. attach the GA-CSR entity to the RR-SAP. + +In addition the MS shall send upper layer messages for which LAPDm has not yet received acknowledgement from the network to the network using the GA-CSR entity. + +## 7.7.4 Reception of GA-CSR HANDOVER COMPLETE by the GANC + +The GANC should indicate handover detection and completion to CN. + +## 7.7.5 MS fails to complete requested handover + +If the traffic channel assignment procedure fails or the timer TU3920 expires before traffic channel assignment is completed, the MS shall: + +- terminate the procedure including release of the associated GA-CSR resources; +- resume the connection in the source radio access technology used before the handover; +- indicate the failure to the source radio access technology. + +## 7.8 CS handover from GAN A/Gb mode + +![Sequence diagram showing the handover process from GAN A/Gb mode. The diagram involves two main entities: MS (Mobile Station) and GANC (GAN Controller). The MS has a sub-entity 'GA-PSR ACTIVE'. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS). 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC, triggered by 'Start TU4004'). 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, triggered by 'Stop TU4004'). 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC).](52f68e21acc86c9aaab2f5abc51a9748_img.jpg) + +``` +sequenceDiagram + participant MS + subgraph MS + GA-PSR ACTIVE + end + participant GANC + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + MS->>GANC: GA-PSR HANDOVER FAILURE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION +``` + +Sequence diagram showing the handover process from GAN A/Gb mode. The diagram involves two main entities: MS (Mobile Station) and GANC (GAN Controller). The MS has a sub-entity 'GA-PSR ACTIVE'. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS). 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC, triggered by 'Start TU4004'). 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, triggered by 'Stop TU4004'). 4. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC). + +Figure 7.8.1: Handover from GAN, successful case + +![Sequence diagram showing a handover failure case between MS and GANC. The MS is in GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC, labeled 'Start TU4004'); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, labeled 'Stop TU4004'); 4. GA-PSR HANDOVER FAILURE (solid arrow from GANC to MS).](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + MS->>GANC: GA-PSR HANDOVER INFORMATION (Start TU4004) + GANC->>MS: GA-PSR HANDOVER COMMAND (Stop TU4004) + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram showing a handover failure case between MS and GANC. The MS is in GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS); 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC, labeled 'Start TU4004'); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, labeled 'Stop TU4004'); 4. GA-PSR HANDOVER FAILURE (solid arrow from GANC to MS). + +Figure 7.8.2: Handover from GAN, failure case + +### 7.8.1 Initiation + +The purpose of this procedure is to transfer, upon request from the MS (and under the control of the GAN), a connection between MS and GAN to another radio access technology (e.g. GERAN). + +The procedure is applicable in GA-CSR-DEDICATED state. + +The procedure may be initiated by the MS based on: + +- local measurements of GAN coverage signal quality; +- reception of a GA-CSR UPLINK QUALITY INDICATION message indicating poor uplink quality in the *UL Quality Indication* IE; If the UL Quality Indication IE indicates "Network problem" a handover out to GERAN or UTRAN should be attempted. In case the UL Quality Indication information element shows "Radio problem" or "Undetermined problem" a search for a new access point should be done before the handover out is initiated; +- reception of RTCP packets indicating poor uplink quality; +- excessive loss or delay in the received RTP packets + +When the MS decides to trigger the handover from GAN A/Gb mode, it shall: + +- send a GA-CSR HANDOVER INFORMATION message to the network including a list of candidate/ target cell identifiers ranked in order of preference which is the most recent list available from the other radio access technology (e.g. GSM RR) and including the received signal strength for each identified GERAN or UTRAN cell. The MS may include GERAN cells, UTRAN cells or both, as permitted by the Handover Reporting Control IE (see sub-clause 11.2.113). If no Handover Reporting Control IE was included in the most recently received GA-RC REGISTER ACCEPT message, there is no restriction on the cells that may be listed. + +### 7.8.2 Reception of GA-CSR HANDOVER INFORMATION by the GANC + +The GANC should signal the need for handover to the CN. + +If the CN grants the handover request, GANC should send a GA-CSR HANDOVER COMMAND message to the MS. + +The GA-CSR HANDOVER COMMAND message should only indicate a target cell which was reported by the MS in the GA-CSR HANDOVER INFORMATION message. + +### 7.8.3 Reception of GA-CSR HANDOVER COMMAND by the MS + +The MS shall: + +- suspend all NAS layer signalling transmissions; + +- start the connection establishment to the target radio access technology (e.g. GERAN) by using the contents of the *Handover From GAN Command* IE. This message carries information about the candidate/ target cell identifier and radio parameters relevant for the target radio access technology; + +A MS that is simultaneously operating in GPRS and CS modes over GAN shall follow the procedure as outlined in 3GPP TS 43.055 when it switches to target cell. + +NOTE: The requirements concerning the establishment of the radio connection towards the target radio access technology (e.g. GERAN) and the signalling procedure are outside of the scope of this specification. + +#### 7.8.4 Successful completion of the CS handover from GAN A/Gb mode + +Upon successfully completing the CS handover from GAN A/Gb mode, the GANC should: + +- release all radio resources associated with the GAN connection. + +Upon successfully completing the CS handover, the MS shall: + +- switch to target radio access technology (e.g. GERAN) mode i.e. detach the GA-RR entity from the RR-SAP; +- enter GA-RC-REGISTERED state. + +NOTE: The release of the GAN radio resources is initiated from the target RAT. The MS may deregister from the GANC (as defined in sub-clause 6.4) after successfully completing the handover. If the MS chooses to deregister from the GANC, it may do so either immediately after successfully completing the handover or after sending the GA-CSR RELEASE COMPLETE message to the GANC in response to the GA-CSR RELEASE message from the GANC. + +#### 7.8.5 MS fails to complete requested handover + +If the MS does not succeed in establishing a connection to the target radio access technology, the MS shall: + +- revert back to the GAN configuration; +- return a GA-CSR HANDOVER FAILURE message and resume normal operation as if the GA-CSR HANDOVER COMMAND message has not been received. The cause shall be set as specified in 3GPP TS 44.018. + +#### 7.8.6 Reception of GA-CSR HANDOVER FAILURE by the GANC + +The GANC may initiate the release of resources in the target radio access technology. + +#### 7.8.7 Abnormal Cases + +If the GA-CSR HANDOVER COMMAND message instructs the MS: + +- to perform a non-supported scenario, or +- to use a non-supported configuration, + +the MS shall return a GA-CSR HANDOVER FAILURE message with cause as defined in 3GPP TS 44.018 and resume normal operation as if the GA-CSR HANDOVER COMMAND message has not been received. + +### 7.9 Ciphering configuration procedure + +The ciphering configuration procedure is used by the network to set the ciphering mode, i.e. whether or not the transmission is ciphered, and if so which algorithm to use. This information is not used when the GA-CSR-layer is the serving entity in the MS, but shall be stored in the MS for possible future use after a handover from GAN during the same upper layer transaction (i.e. RR-layer becomes the serving entity during this upper layer transaction). + +This procedure applies only for a MS in GA-CSR-DEDICATED state. + +The procedure shall only be used to change from "not ciphered" mode to "ciphered" mode, or vice-versa, or to pass a GA-CSR CIPHERING MODE COMMAND message to the mobile station while remaining in the "not ciphered" mode. The ciphering mode setting procedure is always triggered by the network. + +![Sequence diagram showing the ciphering configuration procedure between MS and GANC. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS); 2. GA-PSR HANDOVER INFORMATION (solid arrow from GANC to MS, labeled 'Start TU4004'); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, labeled 'Stop TU4004'); 4. GA-PSR HANDOVER FAILURE (solid arrow from GANC to MS).](c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION + Note right of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + Note right of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram showing the ciphering configuration procedure between MS and GANC. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS); 2. GA-PSR HANDOVER INFORMATION (solid arrow from GANC to MS, labeled 'Start TU4004'); 3. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS, labeled 'Stop TU4004'); 4. GA-PSR HANDOVER FAILURE (solid arrow from GANC to MS). + +Figure 7.9.1 Ciphering configuration + +### 7.9.1 Ciphering configuration initiation + +The network initiates the ciphering mode setting procedure by sending a GA-CSR CIPHERING MODE COMMAND message to the mobile station, indicating whether ciphering shall be used or not, and if yes which algorithm to use. + +Additionally, the network may, by the use of the cipher response information element, request the mobile station to include its IMEISV in the GA-CSR CIPHERING MODE COMPLETE message. + +### 7.9.2 Ciphering configuration completion + +Whenever the mobile station receives a valid GA-CSR CIPHERING MODE COMMAND message, it shall, if a SIM is present and considered valid and the ciphering key sequence number stored on the SIM indicates that a ciphering key is available, save information about the ciphering key to use if the MS is later performing Handover from GAN. A valid GA-CSR CIPHERING MODE COMMAND message is defined to be one of the following: + +- one that indicates "start ciphering" and is received by the mobile station in the "not ciphered" mode; +- one that indicates "no ciphering" and is received by the MS in the "not ciphered" mode; or +- one that indicates "no ciphering" and is received by the mobile station in the "ciphered" mode. + +Other GA-CSR CIPHERING MODE COMMAND messages shall be regarded as erroneous, and a GA-CSR STATUS message with cause "Protocol error unspecified" shall be returned, and no further action taken. + +The MS shall also calculate a MAC (Message Authentication Code). The MAC shall be calculated over the following data: + +RAND | IMSI + +using "HMAC-SHA1-96" algorithm, as specified in [24] with Kc as authentication key. + +In the formulas above, the "|" character denotes concatenation. RAND is the 16-octet random number received from the GANC in the GA-CSR CIPHERING MODE COMMAND message. IMSI is the MS IMSI, in the same format as defined for the Mobile Identity IE as defined in [8] i.e. as a variable-length sequence of digits in BCD format (e.g. the IMSI "123456789098765" is encoded as the following octets (in hexadecimal): "21 43 65 87 09 89 67 F5"). Network byte order is used. + +The Kc key is the Kc that has been derived during the last authentication. The length of the MAC is 12 octets. + +When the appropriate action on the GA-CSR CIPHERING MODE COMMAND message has been taken, the mobile station sends back a GA-CSR CIPHERING MODE COMPLETE message. If the "cipher response" field of the cipher response information element in the GA-CSR CIPHERING MODE COMMAND message specified "IMEISV must be included" the mobile station shall include its IMEISV in the GA-CSR CIPHERING MODE COMPLETE message. + +## 7.10 Channel mode modify procedure + +In dedicated mode, the GANC can request a modification of the channel mode, multi-rate configuration, RTP redundancy configuration, sample size, GANC IP address, GANC RTP UDP port and GANC RTCP UDP port used for an active traffic channel. + +The channel mode modify procedure allows the network to request the mobile station to modify configuration used for an active channel. The channel mode covers the coding, decoding and transcoding mode as well as the redundancy policy used on the active channel. + +This procedure is always initiated by the network. + +![Sequence diagram of the Channel mode modify procedure between MS and GANC.](d7948c38a18636aefecdd95388196460_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note over MS: GA-PSR ACTIVE + GANC->>MS: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +The diagram shows a sequence of messages between the MS (Mobile Station) and the GANC (GAN Controller). The MS is in the GA-PSR ACTIVE state. The messages shown are GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE. Timers Start TU4004 and Stop TU4004 are also indicated. + +Sequence diagram of the Channel mode modify procedure between MS and GANC. + +Figure 7.10.1 Channel mode modify + +### 7.10.1 Normal channel mode modify procedure + +#### 7.10.1.1 Initiation of the channel mode modify procedure + +The network initiates the procedure by sending a GA-CSR CHANNEL MODE MODIFY message to the mobile station. + +#### 7.10.1.2 Completion of channel mode modify procedure + +When the MS has received the GA-CSR CHANNEL MODE MODIFY message, the mobile station modifies the configuration, sets the mode and/or the RTP redundancy configuration for the active channel and then replies by a GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the ordered channel mode. + +This applies whether the mode and/or redundancy policy commanded by the GA-CSR CHANNEL MODE MODIFY message is different from the one used by the mobile station or whether it is already in use. + +When the MS has sent the GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message, it shall start transmit RTP packets with the new size. Until RTP packets with the new sample size have been received, the MS should handle the reception of RTP packets with the old sample size. The MS shall also use changed configurations for all other parameters (channel mode, multi-rate configuration, RTP redundancy configuration, etc.) in uplink RTP frames immediately after sending GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message. In the downlink direction, MS shall be able to receive RTP packets with the old parameters, until the first RTP packet using the new parameters is received. + +The GANC shall only start using the new configuration in downlink RTP frames as of receiving GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message. In the uplink direction, the GANC shall be able to receive RTP packets with the old parameters, until the first RTP packet using the new parameters is received. + +#### 7.10.1.3 Abnormal cases + +If the GA-CSR CHANNEL MODE MODIFY message includes IE "RTP Redundancy Configuration" and MS has indicated that it does not support RTP Redundancy through the GAN Classmark, it shall ignore the IE "RTP Redundancy Configuration". + +If the mobile station does not support the indicated channel mode or sample size modifications, it shall retain the old mode and return the used configuration in the GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message. + +## 8 GA-PSR elementary procedures + +### 8.1 GA-PSR Transport Channel (GA-PSR TC) Overview + +The GA-PSR Transport Channel is defined as a UDP based point to point GA-PSR connection between the MS and the GANC utilized for GPRS user data transfer. The life-time of the GA-PSR TC is controlled by the TU4001 timer. The duration of the TU4001 timer is provided to the MS as one of the GAN system parameters in the GA-RC REGISTER ACCEPT message. In the same way as other GAN system parameters, the GANC can update the TU4001 timer using the standard mechanism for GAN system parameters update. The MS shall store the TU4001 timer for future use and updates the value when requested. + +### 8.2 MS Initiated GA-PSR Transport Channel (GA-PSR TC) Activation + +The MS initiated GA-PSR TC activation is triggered by the uplink GPRS user data request when the GA-PSR is in the GA-PSR-STANDBY state. The following message flow depicts the messages and timers involved in this procedure: + +![Sequence diagram showing MS initiated GA-PSR TC Activation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE. The MS starts the TU4004 timer before sending the GA-PSR ACTIVE message and stops it upon receiving the GA-PSR HANDOVER COMMAND.](85b53faf49a839f512153285c78fbbdb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR ACTIVE + Note left of MS: Start TU4004 + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + GANC-->>MS: GA-PSR HANDOVER INFORMATION + GANC-->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + GANC-->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram showing MS initiated GA-PSR TC Activation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS sends a GA-PSR ACTIVE message to the GANC. The GANC responds with GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE. The MS starts the TU4004 timer before sending the GA-PSR ACTIVE message and stops it upon receiving the GA-PSR HANDOVER COMMAND. + +Figure 8.2.1: MS initiated GA-PSR TC Activation + +#### 8.2.1 Initiation of the GA-PSR TC Activation by the MS + +Upon receiving the uplink user data transfer request from the LLC for LLC SAPI 3, 5, 9 or 11 and while the MS GA-PSR is in the GA-PSR-STANDBY state, the MS shall, + +- send a GA-PSR-ACTIVATE-UTC-REQ message, +- start timer TU4002, +- set the uplink packet sequence number to 0, +- set the expected downlink packet sequence number to 0 and + +#### 8.2.2 Processing of the GA-PSR TC Activation Request by the GANC + +Upon receiving the GA-PSR-ACTIVATE-UTC-REQ message from the MS, if the GANC accepts this request, it: + +- allocates the IP address and the UDP port number to be used by the MS for GPRS user data transport, +- sends the GA-PSR-ACTIVATE-UTC-ACK message to the MS with the cause indicating successful activation, + +- sets downlink packet sequence number to 0 and +- sets the expected uplink packet sequence number to 0. + +### 8.2.3 Processing of the GA-PSR TC Activation Acknowledgment by the MS + +Upon receiving the GA-PSR-ACTIVATE-UTC-ACK message while the MS initiated GA-PSR TC activation is in progress, the MS shall stop timer TU4002, create and store the corresponding GA-PSR TC information and the MS GA-PSR shall transition into GA-PSR-ACTIVE state. The MS GA-PSR shall start TU4001 timer and forward any outstanding uplink user data packets. The TU4001 timer is restarted whenever any user data packet is sent to or received from the GANC. + +### 8.2.4 Abnormal Cases + +#### 8.2.4.1 GA-PSR TC Activation Collision + +If the GANC receives a GA-PSR-ACTIVATE-UTC-REQ message from the MS while the network initiated GA-PSR TC activation procedure is in progress, the GANC aborts the network initiated activation procedure and responds to the MS with the GA-PSR-ACTIVATE-UTC-ACK message including the cause indicating successful activation. The message includes GANC IP address and GANC UDP port to be used for the uplink GPRS user data transport. + +If the MS receives a GA-PSR-ACTIVATE-UTC-REQ message from the GANC while the MS initiated GA-PSR TC activation procedure is in progress, the MS shall silently discard the request and wait for the acknowledgment related to the MS initiated activation already in progress. + +#### 8.2.4.2 Timer TU4002 Expires during GA-PSR TC Activation + +If timer TU4002 expires in the MS, the MS shall remain in GA-PSR-STANDBY state and declare the procedure as failed to the upper layers. + +#### 8.2.4.3 GANC Receives Duplicate GA-PSR TC Activation Request + +If the GANC receives a GA-PSR TC activation message from the MS with an active GA-PSR TC, it responds with the GA-PSR-ACTIVATE-UTC-ACK message to the MS and the cause indicates successful activation. The message includes GANC IP address and GANC UDP port allocated to the existing GA-PSR TC. In parallel, if the MS provided new UDP port number, the GANC updates the GA-PSR TC attributes accordingly. + +After sending the GA-PSR-ACTIVATE-UTC-ACK message, the GANC + +- sets the downlink packet sequence number to 0 and +- sets the expected uplink packet sequence number to 0 + +#### 8.2.4.4 GANC Rejects GA-PSR TC Activation + +If the GANC decides to reject GA-PSR TC activation, it shall send a GA-PSR-ACTIVATE-UTC-ACK message to the MS with the failure cause code and shall not include GANC IP address and UDP port number. The following rejection cause values are supported: + +- "No available resources" indicates that the GANC failed to allocate required resources. +- "GANC failure" indicates internal GANC failure. +- "Not authorized for data service" indicates that the MS is not authorized to use data services via GAN. + +Upon receiving the GA-PSR-ACTIVATE-UTC-ACK message indicating failure, the MS shall declare the procedure as failed to the upper layers. + +#### 8.2.4.5 MS Aborts GA-PSR TC Activation due to Lower Layer Failure + +If a lower layer failure is detected while waiting for GA-PSR-ACTIVATE-UTC-ACK message, the MS shall declare the procedure as failed and send the corresponding indication to upper layers. Further, the MS shall act according to sub-clause 9.5. + +## 8.3 Network Initiated GA-PSR Transport Channel (GA-PSR TC) Activation + +The GANC initiated GA-PSR TC activation is triggered by the downlink GPRS user data request when the corresponding GA-PSR TC does not exist or as a result of PS handover from a GERAN/UTRAN cell to a GAN cell if PS handover is supported by the GANC. The following message flow depicts the messages and timers associated with this procedure: + +![Sequence diagram showing Network initiated GA-PSR TC Activation between MS and GANC. The MS transitions to GA-PSR ACTIVE state. The GANC sends GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE messages. The MS starts TU4004 timer upon receiving GA-PSR HANDOVER INFORMATION and stops it upon receiving GA-PSR HANDOVER COMMAND.](c2ddad56c1553f2499aaf7ef8cef6777_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC->>MS: GA-PSR UPLINK QUALITY INDICATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram showing Network initiated GA-PSR TC Activation between MS and GANC. The MS transitions to GA-PSR ACTIVE state. The GANC sends GA-PSR UPLINK QUALITY INDICATION, GA-PSR HANDOVER INFORMATION, GA-PSR HANDOVER COMMAND, and GA-PSR HANDOVER FAILURE messages. The MS starts TU4004 timer upon receiving GA-PSR HANDOVER INFORMATION and stops it upon receiving GA-PSR HANDOVER COMMAND. + +Figure 8.3.1: Network initiated GA-PSR TC Activation + +### 8.3.1 Initiation of the GA-PSR TC Activation by the GANC + +Upon receiving the downlink user data transfer request associated with LLC SAPI 3, 5, 9 or 11 and if there is no GA-PSR TC associated with the specific MS or upon receiving a PS Handover Request message from the SGSN and if PS handover is supported, the GANC allocates the IP address and the UDP port number to be used by the MS for GPRS user data transport and sends a GA-PSR-ACTIVATE-UTC-REQ message to the MS. The GANC also: + +- sets the downlink packet sequence number to 0 and +- sets the expected uplink packet sequence number to 0 + +### 8.3.2 Processing of the GA-PSR TC Activation Request by the MS + +Upon receiving the GA-PSR-ACTIVATE-UTC-REQ message from the GANC, the MS shall verify the following: + +- the GA-PSR is in GA-PSR-STANDBY state +- the GA-PSR TC does not exist +- the GPRS service is not suspended + +Assuming successful verification, the MS shall allocate UDP port number for the MS GPRS user data transport and store the associated information. In parallel, the MS GA-PSR shall transition to GA-PSR-ACTIVE state and start TU4001 timer. Subsequently, the MS shall send the GA-PSR-ACTIVATE-UTC-ACK message to the GANC with the cause indicating successful activation. The message includes the MS UDP port to be used for the downlink GPRS user data transport. + +After the MS has sent the GA-PSR-ACTIVATE-UTC-ACK message, it shall: + +- set the uplink packet sequence number to 0 and + +- set the expected downlink packet sequence number to 0 + +### 8.3.3 Processing of the GA-PSR TC Activation Acknowledgment by the GANC + +Upon receiving the GA-PSR-ACTIVATE-UTC-ACK message while the GANC initiated GA-PSR TC activation is in progress as a result of a downlink user data transfer request, the GANC forwards any outstanding downlink user data packets. + +Upon receiving the GA-PSR-ACTIVATE-UTC-ACK message while the GANC initiated GA-PSR TC activation is in progress as a result of receiving a PS Handover Request message from the SGSN, the GANC sends a PS Handover Request Ack message to the SGSN and may start blind transmission of downlink user data. + +Both uplink and downlink packet sequence number for user data are set to 0 after successful GA-PSR TC activation. + +### 8.3.4 Abnormal Cases + +#### 8.3.4.1 GA-PSR TC Activation Collision + +If the MS receives a GA-PSR-ACTIVATE-UTC-REQ message from the GANC while the MS initiated GA-PSR TC activation procedure is in progress, the MS shall silently discard the request and wait for the acknowledgment related to the MS initiated activation already in progress. + +#### 8.3.4.2 MS Rejects GA-PSR TC Activation when the GPRS Service is suspended + +If the MS determines that the GPRS service is suspended when the GA-PSR-ACTIVATE-UTC-REQ is received, it shall send a GA-PSR-ACTIVATE-UTC-ACK message to the GANC with the failure cause code set to "GPRS Suspended". + +Upon receiving the GA-PSR-ACTIVATE-UTC-ACK message indicating that the GPRS service is suspended, the GANC aborts the activation procedure. + +#### 8.3.4.3 MS Receives GA-PSR TC Activation Request while GA-PSR TC active + +If the MS receives a GA-PSR TC activation message from the GANC while the GA-PSR TC is active, it shall send the GA-PSR-ACTIVATE-UTC-ACK message to the GANC. The message shall include MS UDP port allocated to the existing GA-PSR TC. In parallel, if the GANC provided new IP Address and UDP port number, the MS shall update the GA-PSR TC attributes accordingly. + +After sending the GA-PSR-ACTIVATE-UTC-ACK message, the MS shall: + +- set uplink packet sequence number to 0 and +- set the expected downlink packet sequence number to 0 + +## 8.4 MS Initiated Deactivation of GA-PSR Transport Channel + +When the TU4001 expires, the MS GA-PSR initiates deactivation of the GA-PSR TC by sending the request to the GANC as per following message flow: + +![Sequence diagram illustrating MS initiated GA-PSR TC Deactivation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS). 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC). 3. Start TU4004 (action on MS side). 4. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS). 5. Stop TU4004 (action on MS side). 6. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC).](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC-->>MS: GA-PSR UPLINK QUALITY INDICATION + MS->>GANC: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram illustrating MS initiated GA-PSR TC Deactivation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS is in the GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (dashed arrow from GANC to MS). 2. GA-PSR HANDOVER INFORMATION (solid arrow from MS to GANC). 3. Start TU4004 (action on MS side). 4. GA-PSR HANDOVER COMMAND (solid arrow from GANC to MS). 5. Stop TU4004 (action on MS side). 6. GA-PSR HANDOVER FAILURE (solid arrow from MS to GANC). + +**Figure 8.4.1: MS initiated GA-PSR TC Deactivation** + +### 8.4.1 GA-PSR TC Deactivation Initiation by the MS + +When the TU4001 timer expires and if there are no outstanding uplink GPRS user data messages to be transferred, the MS GA-PSR shall send the GA-PSR-DEACTIVATE-UTC-REQ message to the GANC to request the deactivation of the transport channel. In parallel, the MS shall start TU4002 timer to wait for the confirmation. + +### 8.4.2 Processing of GA-PSR TC Deactivation Request by the GANC + +Upon receipt of a GA-PSR-DEACTIVATE-UTC-REQ message from the MS, the GANC releases the GA-PSR TC and sends the GA-PSR-DEACTIVATE-UTC-ACK message to the MS indicating successful deactivation; i.e. the cause IE is set to "success". + +### 8.4.3 Processing of GA-PSR TC Deactivation Acknowledgment by the MS + +Upon receipt of a GA-PSR-DEACTIVATE-UTC-ACK message from the GANC, the MS GA-PSR shall stop TU4002 timer, and release the GA-PSR TC. In parallel, the MS GA-PSR shall transition to GA-PSR-STANDBY state. + +### 8.4.4 Abnormal Cases + +#### 8.4.4.1 Timer TU4002 Expires during GA-PSR TC Deactivation + +If timer TU4002 expires in the MS, the MS shall transit to GA-PSR-STANDBY state and declare the procedure as failed to the upper layers. + +#### 8.4.4.2 GANC Rejects GA-PSR TC Deactivation + +The following scenarios cover the cases when the GANC rejects GA-PSR TC Deactivation: + +- If the corresponding GA-PSR TC does not exist on the network side, the GANC responds with a GA-PSR-DEACTIVATE-UTC-ACK message indicating successful deactivation. +- If there is outstanding downlink GPRS user data for the specified MS, the GANC forwards the data packets instead and ignores the deactivation request. + +#### 8.4.4.3 Uplink User Data Transfer is initiated while GA-PSR TC Deactivation is in Progress + +If the MS LLC initiates the uplink user data transfer after the MS GA-PSR has sent the deactivation request to the GANC, the MS GA-PSR shall complete the deactivation procedure first and then initiate a new GA-PSR TC activation procedure to enable data transfer. + +#### 8.4.4.4 Downlink User Data Transfer is received while the GA-PSR TC Deactivation is in Progress + +If the MS receives any downlink user data packets while waiting for the GA-PSR-DEACTIVATE-UTC-ACK message response, it shall abort the deactivation procedure (i.e. stop timer TU4002) and restart TU4001 timer. + +#### 8.4.4.5 Unexpected GA-PSR-DEACTIVATE-UTC-ACK response + +If the MS receives an unexpected GA-PSR-DEACTIVATE-UTC-ACK message response while the GA-PSR is in GA-PSR-ACTIVE state, the MS GA-PSR shall stop TU4001 timer, and release the GA-PSR TC. In parallel, the MS GA-PSR shall transition to GA-PSR-STANDBY state. + +If the MS receives an unexpected GA-PSR-DEACTIVATE-UTC-ACK message response while the GA-PSR is in GA-PSR-STANDBY state, the message is silently discarded. + +#### 8.4.4.6 Unexpected GA-PSR-ACTIVATE-UTC-REQ + +If the MS receives an unexpected GA-PSR-ACTIVATE-UTC-REQ message while waiting for GA-PSR-DEACTIVATE-UTC-ACK message response, the MS ignores the request and continues waiting for deactivation response. + +#### 8.4.4.7 MS Aborts GA-PSR TC Deactivation due to Lower Layer Failure + +If a lower layer failure is detected while waiting for GA-PSR-DEACTIVATE-UTC-ACK message, the MS shall declare the procedure as failed and send the corresponding indication to upper layers. Further, the MS shall act according to sub-clause 9.5. + +## 8.5 GANC Initiated Deactivation of GA-PSR Transport Channel + +The GANC may initiate the deactivation of the GA-PSR TC by sending the request to the MS as per following message flow: + +![Sequence diagram showing network initiated GA-PSR TC Deactivation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS is initially in the GA-PSR ACTIVE state. The GANC sends a GA-PSR HANDOVER INFORMATION message to the MS. The MS starts timer TU4004 and responds with GA-PSR HANDOVER COMMAND. The GANC then sends a GA-PSR HANDOVER FAILURE message to the MS, which stops timer TU4004.](86f61404a19a384d06a7b0b2c4e6937a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + MS-->>GANC: GA-PSR HANDOVER COMMAND + GANC-->>MS: GA-PSR HANDOVER FAILURE + Note left of MS: Stop TU4004 + +``` + +Sequence diagram showing network initiated GA-PSR TC Deactivation. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS is initially in the GA-PSR ACTIVE state. The GANC sends a GA-PSR HANDOVER INFORMATION message to the MS. The MS starts timer TU4004 and responds with GA-PSR HANDOVER COMMAND. The GANC then sends a GA-PSR HANDOVER FAILURE message to the MS, which stops timer TU4004. + +Figure 8.5.1: Network initiated GA-PSR TC Deactivation + +### 8.5.1 GA-PSR TC Deactivation Initiation by the GANC + +When the GANC decides to deactivate GA-PSR TC channel, it shall send GA-PSR-DEACTIVATE-UTC-REQ message to the MS to request the deactivation. + +### 8.5.2 Processing of GA-PSR TC Deactivation Request by the MS + +Upon receipt of a GA-PSR-DEACTIVATE-UTC-REQ message from the GANC, the MS shall release the GA-PSR TC and send the GA-PSR-DEACTIVATE-UTC-ACK message to the GANC indicating successful deactivation; i.e. the cause IE is set to "success". In parallel, the MS GA-PSR shall transition to GA-PSR-STANDBY state. + +### 8.5.3 Processing of GA-PSR TC Deactivation Acknowledgment by the GANC + +Upon receipt of a GA-PSR-DEACTIVATE-UTC-ACK message from the MS, the GANC shall release the GA-PSR TC. + +### 8.5.4 Abnormal Cases + +#### 8.5.4.1 MS Rejects GA-PSR TC Deactivation + +The following scenarios cover the cases when the MS rejects GA-PSR TC Deactivation: + +- If the corresponding GA-PSR TC does not exist on the MS side, the MS shall respond with a GA-PSR-DEACTIVATE-UTC-ACK message indicating successful deactivation. +- If there is outstanding uplink GPRS user data, the MS forwards the data packets instead and ignores the deactivation request. + +#### 8.5.4.2 Uplink User Data Transfer is received while GA-PSR TC Deactivation is in Progress + +If the MS LLC initiates the uplink user data transfer after the MS has received a deactivation request from the GANC, the MS shall complete the deactivation procedure first and then initiate a new GA-PSR TC activation procedure to enable data transfer. + +If the MS LLC initiates the uplink user data transfer before the MS has received a deactivation request from the GANC, the MS shall treat that as normal uplink user data transfer as defined in sub-clause 8.7.1. + +#### 8.5.4.3 Downlink User Data Transfer is initiated while the GA-PSR TC Deactivation is in Progress + +If the GANC receives any downlink user data packets while waiting for the GA-PSR-DEACTIVATE-UTC-ACK response, it shall complete the deactivation procedure first and then initiate a new GA-PSR TC activation procedure to enable data transfer. + +## 8.6 Implicit Deactivation of GA-PSR Transport Channel + +If the GAN deregistration is performed for a mobile station with an active GA-PSR TC, the GANC automatically releases the associated GA-PSR TC. The MS shall release the GA-PSR TC upon GAN deregistration. + +This includes the scenarios where an implicit GAN deregistration is performed by either the MS or GANC due to lower layer failures. + +## 8.7 GA-PSR GPRS User Data Transport + +While the corresponding GA-PSR TC is available, both mobile station and GANC can initiate GPRS user data transfer automatically using GA-PSR UNITDATA service as illustrated in the following figure: + +![Sequence diagram illustrating GA-PSR GPRS User Data transport between MS and GANC. The MS has a box labeled 'GA-PSR ACTIVE'. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC); 2. GA-PSR HANDOVER INFORMATION (GANC to MS); 3. GA-PSR HANDOVER COMMAND (GANC to MS, triggered by 'Start TU4004'); 4. GA-PSR HANDOVER FAILURE (MS to GANC, triggered by 'Stop TU4004').](c9c3a80790995f4e292bcb457d3e1686_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram illustrating GA-PSR GPRS User Data transport between MS and GANC. The MS has a box labeled 'GA-PSR ACTIVE'. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC); 2. GA-PSR HANDOVER INFORMATION (GANC to MS); 3. GA-PSR HANDOVER COMMAND (GANC to MS, triggered by 'Start TU4004'); 4. GA-PSR HANDOVER FAILURE (MS to GANC, triggered by 'Stop TU4004'). + +Figure 8.7.1: GA-PSR GPRS User Data transport + +The GPRS user data packets are tunnelled using UDP transport as specified for GA-PSR Transport Channel. Each packet is assigned a sequence number in the range of 0 to 65535 sequentially. The sequence number is set to 0 after reaching the maximum - 65535. + +### 8.7.1 MS Initiates Uplink GPRS User Data Transfer + +Assuming that the GA-PSR TC has been already activated as specified in sub-clauses 8.2 or 8.3, the MS GA-PSR is able to immediately forward any uplink GPRS user data packets to the GANC. Upon the request from the LLC to transfer an uplink LLC PDU with GPRS user data identified with LLC SAPI 3, 5, 9 or 11, the MS GA-PSR shall restart TU4001 timer and encapsulate the complete LLC PDU within a GA-PSR UNITDATA message. + +Subsequently, the MS shall send the GA-PSR UNITDATA message to the GANC using the existing GA-PSR TC; i.e. using the corresponding GANC IP address and UDP port number. + +The MS shall increment the uplink packet sequence number for each GA-PSR-UNITDATA message sent to the GANC. + +### 8.7.2 Processing of the Uplink GPRS User Data Message by the GANC + +Upon receiving the uplink user data message from the MS, the GANC extracts the received LLC PDU and available message parameters, relays the PDU to the SGSN via the Gb interface using the BSSGP uplink unitdata procedure as per standard GPRS. + +The GANC increments the expected uplink packet sequence number for each GA-PSR-UNITDATA message received from the MS. + +### 8.7.3 GANC Initiates Downlink GPRS User Data Transfer + +Assuming that the GA-PSR TC has been already activated as specified in sub-clause 8.2 or 8.3, the GANC is able to immediately forward any downlink GPRS user data packets to the MS. Upon receiving a downlink packet for the MS, the GANC sends the GA-PSR UNITDATA message to the MS using the existing GA-PSR TC; i.e. using the corresponding MS IP address and UDP port number. + +The GANC increments the downlink packet sequence number for each GA-PSR-UNITDATA message sent to the MS. + +### 8.7.4 Processing of the Downlink GPRS User Data Message by the MS + +Upon receiving the downlink user data message from the GANC, the MS GA-PSR shall restart TU4001 timer, extract the received LLC PDU and TLLI and forward the PDU to the LLC layer via the GRR SAP as per standard GPRS. + +The MS shall increment the expected downlink packet sequence number for each GA-PSR-UNITDATA message received from the GANC. + +### 8.7.5 Abnormal Cases + +#### 8.7.5.1 GANC Receives an Uplink User Data Message while the GA-PSR TC Activation Procedure is in progress + +Upon receiving an uplink message while the GA-PSR TC activation procedure is in progress (TU4002 timer is still running), the GANC will process the request as if the GA-PSR TC was active. + +#### 8.7.5.2 GANC Receives an Uplink User Data Message and the GA-PSR TC is not active + +Upon receiving an uplink message that is associated with a GA-PSR TC that does not exist, the GANC will process the message as defined in sub-clause 8.7.2. The GANC may disregard the uplink packet sequence number in this case. Further, the GANC initiates GA-PSR TC activation procedure as defined in sub-clause 8.3. + +#### 8.7.5.3 Handling of out-of-sequence packets + +Packets received out-of-sequence should be dropped. + +#### 8.7.5.4 MS Receives a Downlink User Data Message while the GA-PSR TC Activation Procedure is in progress + +Upon receiving a downlink message while the GA-PSR TC activation procedure is in progress (TU4002 timer is still running), the MS GA-PSR shall process the request as if the transport channel was active. The MS shall not initiate uplink GPRS user data transfer until the GA-PSR TC activation procedure is successfully completed (as specified in the subclause 8.2). The MS shall use the IP address and UDP port number received in the GA-PSR ACTIVATE UTC ACK message for sending uplink GPRS user data packets to the GANC on that transport channel. + +#### 8.7.5.5 Uplink User Data Transfer Failed due to Lower Layer Failure + +If a lower layer failure is detected while attempting to send an uplink user data packet, the MS shall declare the procedure as failed and send the corresponding indication to upper layers. + +## 8.8 GA-PSR GPRS Signalling and SMS Messages Transport + +While the MS is registered for GAN services, the corresponding TCP session for signalling transport is always available and, assuming that the MS GA-CSR and GA-PSR are attached to GSM/GPRS SAPs, both mobile station and GANC can initiate GPRS signalling message transfer using GA-PSR DATA service as illustrated in the following figure. The GA-PSR-DATA transport mechanism is utilized for all GPRS GMM/SM signalling and SMS messages. + +![Sequence diagram illustrating GA-PSR GPRS Signalling and SMS Messages transport between MS and GANC. The MS contains a GA-PSR ACTIVE block. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC); 2. GA-PSR HANDOVER INFORMATION (MS to GANC) - triggered by 'Start TU4004'; 3. GA-PSR HANDOVER COMMAND (GANC to MS); 4. GA-PSR HANDOVER FAILURE (GANC to MS) - triggered by 'Stop TU4004'.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +``` + +sequenceDiagram + participant MS + subgraph MS [MS] + GA-PSR ACTIVE + end + participant GANC + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + MS->>GANC: GA-PSR HANDOVER INFORMATION + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram illustrating GA-PSR GPRS Signalling and SMS Messages transport between MS and GANC. The MS contains a GA-PSR ACTIVE block. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC); 2. GA-PSR HANDOVER INFORMATION (MS to GANC) - triggered by 'Start TU4004'; 3. GA-PSR HANDOVER COMMAND (GANC to MS); 4. GA-PSR HANDOVER FAILURE (GANC to MS) - triggered by 'Stop TU4004'. + +Figure 8.8.1: GA-PSR GPRS Signalling and SMS Messages transport + +### 8.8.1 MS Initiates Uplink GPRS Signalling/SMS Message Transfer + +Upon the request from the LLC to transfer an uplink LLC PDU carrying GPRS signalling message (identified with LLC SAPI 1) or GPRS SMS message (LLC SAPI 7), the MS GA-PSR shall encapsulate the complete LLC PDU within a GA-PSR DATA message and send the message to the GANC using the existing signalling TCP session. + +### 8.8.2 Processing of the Uplink GA-PSR DATA Message by the GANC + +Upon receiving the uplink GA-PSR DATA message from the MS, the GANC extracts the received LLC PDU and available message parameters and, relays the PDU to the SGSN via the Gb interface using the BSSGP uplink unitdata procedure as per standard GPRS. + +### 8.8.3 GANC Initiates Downlink GA-PSR DATA Transfer + +Upon receiving a downlink LLC PDU with GPRS signalling (identified with LLC SAPI 1) or SMS message (LLC SAPI 7), the GANC encapsulates the complete LLC PDU within a GA-PSR DATA message and sends the message to the MS using the existing signalling TCP session. + +### 8.8.4 Processing of the Downlink GA-PSR DATA Message by the MS + +Upon receiving the GA-PSR-DATA message that includes the downlink GPRS signalling or SMS LLC PDU from the GANC, the MS shall extract the received LLC PDU and TLLI and forward the PDU to the LLC layer via the GRR SAP as per standard GPRS. + +### 8.8.5 Abnormal Cases + +#### 8.8.5.1 Downlink or Uplink User Data Transfer Failed due to Lower Layer Failure + +If a lower layer failure is detected while attempting to send an uplink GPRS signalling or SMS message, the MS GA-PSR shall act according to sub-clause 9.5. + +## 8.9 Packet paging for packet service + +The following figure depicts interactions involved in the packet paging procedure via GAN. + +![Sequence diagram for Packet Paging procedure. The diagram shows interactions between MS (Mobile Station) and GANC (GAN Controller). The MS has a state 'GA-PSR ACTIVE'. The GANC sends 'GA-PSR UPLINK QUALITY INDICATION' and 'GA-PSR HANDOVER INFORMATION' to the MS. The MS responds with 'Start TU4004' and 'Stop TU4004' messages. The GANC then sends 'GA-PSR HANDOVER COMMAND' and 'GA-PSR HANDOVER FAILURE' to the MS.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + GANC->>MS: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION + MS-->>GANC: Start TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + MS-->>GANC: Stop TU4004 + GANC->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Packet Paging procedure. The diagram shows interactions between MS (Mobile Station) and GANC (GAN Controller). The MS has a state 'GA-PSR ACTIVE'. The GANC sends 'GA-PSR UPLINK QUALITY INDICATION' and 'GA-PSR HANDOVER INFORMATION' to the MS. The MS responds with 'Start TU4004' and 'Stop TU4004' messages. The GANC then sends 'GA-PSR HANDOVER COMMAND' and 'GA-PSR HANDOVER FAILURE' to the MS. + +Figure 8.9.1: Packet Paging + +### 8.9.1 PS Paging Request Processing by the GANC + +Upon receiving a Paging PS request from the SGSN for GAN registered MS, the GANC sends the GA-PSR-PS-PAGE message to the MS via the signalling TCP session. + +### 8.9.2 PS Paging Request Processed by the MS + +Upon receiving a GA-PSR-PS-PAGE message from the GANC, the MS GA-PSR shall forward the indication to the GMM layer using the GMMRR SAP as per standard GPRS. Subsequently, the MS shall send an uplink LLC PDU as a page response per standard GPRS. The MS may either send GA-PSR-DATA or GA-PSR-UNITDATA message as described in sub-clauses 8.7 and 8.8. + +### 8.9.3 Processing of the PS Paging Response by the GANC + +Since the MS responds to a PS Paging with any LLC PDU encapsulated within the standard GA-PSR-DATA or GA-PSR-UNITDATA message, the GANC will process the message as any other GPRS signalling/SMS or user data message. The processing of uplink GPRS data messages is described in sub-clause 8.7 and for the uplink GPRS signalling messages in sub-clause 8.8. + +## 8.10 GPRS Suspend Procedure + +The following figure depicts interaction involved in the GPRS Suspend procedure. + +![Sequence diagram for GPRS Suspend procedure. The diagram shows interactions between MS (Mobile Station) and GANC (GAN Controller). The MS has a state 'GA-RR-IDLE'. The MS sends '1. GA-RR REQUEST' to the GANC. The GANC responds with '2. GA-RR REQUEST ACCEPT'. The MS then transitions to state 'GA-RR CONNECTED'.](98a45dd7d474e067b7533cc966c11e95_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RR-IDLE + MS->>GANC: 1. GA-RR REQUEST + GANC-->>MS: 2. GA-RR REQUEST ACCEPT + Note left of MS: GA-RR CONNECTED + +``` + +Sequence diagram for GPRS Suspend procedure. The diagram shows interactions between MS (Mobile Station) and GANC (GAN Controller). The MS has a state 'GA-RR-IDLE'. The MS sends '1. GA-RR REQUEST' to the GANC. The GANC responds with '2. GA-RR REQUEST ACCEPT'. The MS then transitions to state 'GA-RR CONNECTED'. + +Figure 8.10.1 GPRS Suspend + +### 8.10.1 GPRS Suspension Initiation by the MS + +While transitioning to dedicated mode and if unable to support simultaneous CS and PS services, the MS shall request the suspension of the downlink GPRS data transfer by sending a GA- CSR GPRS SUSPENSION REQUEST message to the GANC + +### 8.10.2 GPRS Suspend Request Processing by the GANC + +Upon receiving a GA- CSR GPRS SUSPENSION REQUEST message from the MS, the GANC completes the GPRS suspend procedure via the Gb interface as defined in [19]. + +## 8.11 MS Initiated Downlink Flow Control + +The MS initiated downlink flow control procedure is based on standard GPRS downlink flow control mechanism enhanced for GAN service. The MS implements the flow control algorithm to monitor and calculate the data rate that could be supported based on the current conditions. When the flow control condition is detected (e.g. the utilization of the buffers reaches a high watermark level), the MS re-calculates the estimated data rate that could be supported and sends the flow control request to the GANC to adjust the data rate accordingly. The following message flow depicts the messages and timers associated with this procedure: + +![Sequence diagram showing MS initiated Downlink Flow Control. The diagram shows interactions between MS and GANC. The MS has a state 'GA-PSR ACTIVE'. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC). 2. GA-PSR HANDOVER INFORMATION (GANC to MS). 3. GA-PSR HANDOVER COMMAND (GANC to MS). 4. GA-PSR HANDOVER FAILURE (GANC to MS). Timers TU4004 are shown: 'Start TU4004' before the second message and 'Stop TU4004' before the third message.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC-->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + GANC-->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + GANC-->>MS: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram showing MS initiated Downlink Flow Control. The diagram shows interactions between MS and GANC. The MS has a state 'GA-PSR ACTIVE'. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC). 2. GA-PSR HANDOVER INFORMATION (GANC to MS). 3. GA-PSR HANDOVER COMMAND (GANC to MS). 4. GA-PSR HANDOVER FAILURE (GANC to MS). Timers TU4004 are shown: 'Start TU4004' before the second message and 'Stop TU4004' before the third message. + +Figure 8.11.1: MS initiated Downlink Flow Control + +Initially, before detecting a flow control condition, the flow control condition does not exist in the MS. In this state, the MS GA-PSR monitors the average downlink data rate and the utilization of resources (e.g. downlink buffers), and when utilization exceeds a certain threshold, a downlink flow control condition is detected. + +When the downlink flow control condition is detected, the MS sends the GA-PSR-DFC-REQ message to the GANC and starts the TU4003 timer. Whenever the timer expires, the MS checks the downlink flow control condition, and if it continues to exist, the MS restarts the timer, and sends another GA-PSR-DFC-REQ message to the GANC. The MS remains in this state while the flow control condition persists. As soon as the flow control condition is resolved, the MS deactivates the TU4003 timer and transitions to the default state in which no downlink flow control condition exists. + +In case TU4003 is running and the CS traffic channel is activated or released or in case of GA-CSR state transition, MS may request the GANC flow control parameters to adjust existing flow control by sending GA-PSR-DFC-REQ message to the GANC and if so it shall restart the timer TU4003. + +### 8.11.1 Initiation of the Downlink Flow Control by the MS + +Upon detecting the downlink flow control condition, the MS shall initiate a downlink flow control procedure by sending a GA-PSR-DFC-REQ message to the GANC via the existing GA-PSR TC. The message includes new estimated data rate that can be supported. At the same time the MS shall start timer TU4003 to continue monitoring the flow control condition. The timer TU4003 is specified in sub-clause 12. + +### 8.11.2 Processing of the Downlink Flow Control Request by the GANC + +Upon receiving the GA-PSR-DFC-REQ message from the MS, the GANC initiates downlink flow control procedure over the Gb interface as per standard GPRS. + +### 8.11.3 Processing of the TU4003 Timer Expiry by the MS + +When the TU4003 timer expires, the MS shall re-evaluate the flow control condition and perform the following based on the outcome of the evaluation: + +- If the flow control condition still exists (e.g. downlink buffer utilization is still above the low watermark level), the MS shall calculate a new data rate that can be supported and forward the corresponding GA-PSR-DFC-REQ message to the GANC via the existing GA-PSR TC. Simultaneously, the MS shall start timer TU4003 to continue monitoring the downlink data transfer. +- If the flow condition has been resolved (e.g. buffer utilization is below the low mark level), the MS shall not restart the TU4003 timer and shall stop sending flow control requests to the GANC. + +## 8.12 Uplink Flow Control + +The uplink flow control procedure is used to dynamically manage sharing of the available Gb interface bandwidth. The following message flow depicts the messages and timers associated with this procedure: + +![Sequence diagram for Uplink Flow Control between MS and GANC. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC), 2. GA-PSR HANDOVER INFORMATION (GANC to MS), 3. GA-PSR HANDOVER COMMAND (GANC to MS), 4. GA-PSR HANDOVER FAILURE (MS to GANC). Timers TU4004 are started and stopped by the MS during the process.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + GANC->>MS: GA-PSR HANDOVER COMMAND + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for Uplink Flow Control between MS and GANC. The MS has a GA-PSR ACTIVE state. The sequence of messages is: 1. GA-PSR UPLINK QUALITY INDICATION (MS to GANC), 2. GA-PSR HANDOVER INFORMATION (GANC to MS), 3. GA-PSR HANDOVER COMMAND (GANC to MS), 4. GA-PSR HANDOVER FAILURE (MS to GANC). Timers TU4004 are started and stopped by the MS during the process. + +Figure 8.12.1: Uplink Flow Control + +Upon receiving the request, the MS GA-PSR adjusts the uplink data rate as per request. + +### 8.12.1 Initiation of the Uplink Flow Control by the GANC + +Upon detecting the uplink flow control condition, the GANC initiates an uplink flow control procedure by sending a GA-PSR-UFC-REQ message to the MS via the existing GA-PSR TC. The request is PFC based if the packet flow management procedures are supported. + +The GANC shall never request the uplink data rate that is lower than the guaranteed uplink bit rate specified for that PFC. The guaranteed bit rate can be ignored by the GANC if the Traffic Class is Interactive class or Background class. + +### 8.12.2 Processing of the Uplink Flow Control Request by the MS + +Upon receiving the GA-PSR-UFC-REQUEST message from the GANC, the MS adjusts the uplink data rate accordingly. + +### 8.12.3 Resetting of the Uplink Flow Control Condition by the GANC + +After the uplink flow control condition is resolved and the current conditions allow the uplink data rate to be reset to normal level, the GANC initiates an uplink flow control condition reset by sending a GA-PSR-UFC-REQUEST message to the MS via the existing GA-PSR TC. This message includes the reset indicator. + +### 8.12.4 Abnormal Cases + +#### 8.12.4.1 GA-PSR TC Deactivation is in Progress + +If the MS receives a GA-PSR-UFC-REQUEST message while the GA-PSR TC deactivation is in progress, the MS shall ignore the flow control request. + +## 8.13 PS handover to GAN A/Gb mode + +### 8.13.1 Initiation + +If PS handover to GAN A/Gb mode is supported by both the MS and the source BSS/RNC it may be used to prevent an MS from performing an autonomous rove-in to GAN A/Gb mode in favour of using PS handover to perform a cell change. PS handover from a GERAN cell to a GAN A/Gb mode cell may be triggered as described in 3GPP TS 44.060 [45]. PS handover from a UTRAN cell to a GAN A/Gb mode cell may be triggered as described in 3GPP TS 25.331 [40]. + +The procedure for PS handover to a GAN A/Gb mode cell results in the target GANC allocating the MS a GA-PSR Transport Channel in response to receiving a **PS Handover Request** message from the SGSN (see sub-clause 8.3 and 3GPP TS 43.129 [49]). When the source BSS/RNC is informed about the successful allocation of the GA-PSR Transport Channel it responds by sending the MS a **PS Handover Command** message (source BSS) or a **Handover from UTRAN Command** message (source RNC). + +If the target GANC supports blind transmission it may begin transmitting downlink data on the allocated GA-PSR Transport Channel prior to determining that PS handover to the GAN A/Gb mode cell has been successfully completed. Otherwise, it may discard downlink data that becomes available prior to detecting the successful completion of the PS handover to the GAN A/Gb mode cell. An MS that supports blind transmission enables the reception of downlink data upon being allocated a GA-PSR Transport Channel (i.e. prior to switching to GAN A/Gb mode). + +### 8.13.2 Successful completion of the PS handover to GAN A/Gb mode + +From the MS perspective the procedure for PS handover to a GAN A/Gb mode cell is started upon reception of the **PS HANDOVER COMMAND** message or the **HANDOVER FROM UTRAN COMMAND** message and completed upon sending a **GA-PSR HANDOVER COMPLETE** message to the GANC. + +From the source BSS/RNC perspective the procedure for PS handover to a GAN A/Gb mode cell is started upon deciding to perform PS handover of an MS to a GAN A/Gb mode cell and completed upon being told by the SGSN to release all ongoing radio resources. + +From the target GANC perspective the procedure for PS handover to a GAN A/Gb mode cell is started upon receiving a **PS HANDOVER REQUEST** message and completed upon receiving a **GA-PSR HANDOVER COMPLETE** message from the MS. Upon receiving this message the GANC shall indicate PS handover completion to the SGSN. + +### 8.13.3 Abnormal Cases + +Upon receiving a **PS HANDOVER COMMAND** message or a **HANDOVER FROM UTRAN COMMAND** message in the source cell the MS may experience the following abnormal conditions: + +- If connectivity has been lost on the GA-PSR Transport Channel before the MS has transmitted a GA-PSR **HANDOVER COMPLETE** message it shall abort the PS handover to GAN A/Gb mode. The MS shall remain in the source cell and provide a failure notification as described in 3GPP TS 44.060 [45] for a GERAN cell or in 3GPP TS 25.331 [40] for a UTRAN cell. + +## 8.14 PS handover from GAN A/Gb mode + +### 8.14.1 Initiation + +If PS handover from GAN A/Gb mode is supported by both the MS and the GANC it may be used to prevent an MS from performing an autonomous rove-out from GAN A/Gb mode in favour of using PS handover to perform a cell change. + +![Sequence diagram for PS handover from GAN A/Gb mode, successful case. The diagram shows the interaction between an MS (Mobile Station) and a GANC (GAN Controller). The MS sends a GA-PSR UPLINK QUALITY INDICATION to the GANC. The GANC responds with GA-PSR HANDOVER INFORMATION. The MS then sends a GA-PSR HANDOVER COMMAND to the GANC. The GANC responds with GA-PSR HANDOVER FAILURE. The MS then sends a GA-PSR HANDOVER FAILURE to the GANC. The sequence is triggered by 'Start TU4004' and 'Stop TU4004' events.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC-->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER COMMAND + GANC-->>MS: GA-PSR HANDOVER FAILURE + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for PS handover from GAN A/Gb mode, successful case. The diagram shows the interaction between an MS (Mobile Station) and a GANC (GAN Controller). The MS sends a GA-PSR UPLINK QUALITY INDICATION to the GANC. The GANC responds with GA-PSR HANDOVER INFORMATION. The MS then sends a GA-PSR HANDOVER COMMAND to the GANC. The GANC responds with GA-PSR HANDOVER FAILURE. The MS then sends a GA-PSR HANDOVER FAILURE to the GANC. The sequence is triggered by 'Start TU4004' and 'Stop TU4004' events. + +Figure 8.14.1: PS handover from GAN A/Gb mode, successful case + +![Sequence diagram for PS handover from GAN A/Gb mode, failure case. The diagram shows the interaction between an MS (Mobile Station) and a GANC (GAN Controller). The MS sends a GA-PSR UPLINK QUALITY INDICATION to the GANC. The GANC responds with GA-PSR HANDOVER INFORMATION. The MS then sends a GA-PSR HANDOVER COMMAND to the GANC. The GANC responds with GA-PSR HANDOVER FAILURE. The MS then sends a GA-PSR HANDOVER FAILURE to the GANC. The sequence is triggered by 'Start TU4004' and 'Stop TU4004' events.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR ACTIVE + MS->>GANC: GA-PSR UPLINK QUALITY INDICATION + GANC-->>MS: GA-PSR HANDOVER INFORMATION + Note left of MS: Start TU4004 + MS->>GANC: GA-PSR HANDOVER COMMAND + GANC-->>MS: GA-PSR HANDOVER FAILURE + Note left of MS: Stop TU4004 + MS->>GANC: GA-PSR HANDOVER FAILURE + +``` + +Sequence diagram for PS handover from GAN A/Gb mode, failure case. The diagram shows the interaction between an MS (Mobile Station) and a GANC (GAN Controller). The MS sends a GA-PSR UPLINK QUALITY INDICATION to the GANC. The GANC responds with GA-PSR HANDOVER INFORMATION. The MS then sends a GA-PSR HANDOVER COMMAND to the GANC. The GANC responds with GA-PSR HANDOVER FAILURE. The MS then sends a GA-PSR HANDOVER FAILURE to the GANC. The sequence is triggered by 'Start TU4004' and 'Stop TU4004' events. + +Figure 8.14.2: PS handover from GAN A/Gb mode, failure case + +The MS and the GANC inform each other of whether or not they support PS handover during GAN registration. If supported, PS handover may be triggered by the MS based on: + +- local measurements of GAN coverage signal quality; +- user initiated change of operational mode to GERAN/UTRAN preferred or GERAN/UTRAN only; +- reception of a **GA-PSR UPLINK QUALITY INDICATION** message from the GANC indicating one of the following in the UL Quality Indication IE: + - Radio problem (unacceptable uplink performance). + - Network problem. + - Unknown problem. + +Upon experiencing any of these trigger conditions an MS may at any point trigger the PS handover procedure in the source GANC by sending a **GA-PSR HANDOVER INFORMATION** message. + +A **GA-PSR HANDOVER INFORMATION** message sent by an MS shall include a list of candidate GERAN/UTRAN cells ranked in order of preference based on the most recent lists available from the candidate radio access technologies and including the received signal strength for each identified GERAN or UTRAN cell. The list of candidate cells may include only GERAN cells, only UTRAN cells or both, as permitted by the Handover Reporting Control IE (see sub-clause 11.2.113). If no Handover Reporting Control IE was included in the most recently received GA-RC REGISTER + +ACCEPT message, there is no restriction on the cells that may be listed. Upon sending this message the MS shall start timer TU4004. + +### 8.14.2 Reception of GA-PSR HANDOVER INFORMATION by the GANC + +Upon reception of a **GA-PSR HANDOVER INFORMATION** message the source GANC triggers PS handover to a GERAN/UTRAN target cell by sending a **PS Handover Required** message to the SGSN. This results in the allocation of radio resources/RABs in the target cell (see 3GPP TS 43.129 [49]). When the source GANC is informed by the SGSN about the successful allocation of radio resources/RABs in the target cell it responds by sending the MS a **GA-PSR HANDOVER COMMAND** message. While the PS handover procedure is ongoing but prior to sending the MS a **GA-PSR HANDOVER COMMAND** message, the GANC may send the MS one or more instances of the **GA-PSR HANDOVER CONTINUE** message to prevent timer TU4004 from expiring in the MS. + +### 8.14.3 Reception of GA-PSR HANDOVER CONTINUE by the MS + +Upon reception of a **GA-PSR HANDOVER CONTINUE** message from the GANC the MS shall proceed as follows: + +- If timer TU4004 is running it shall be restarted. +- If timer TU4004 is not running the MS shall discard the **GA-PSR HANDOVER CONTINUE** message. + +### 8.14.4 Reception of GA-PSR HANDOVER COMMAND by the MS + +The **GA-PSR HANDOVER COMMAND** message should only indicate a target cell which was reported by the MS in the **GA-PSR HANDOVER INFORMATION** message. + +- For the case of PS handover to a GERAN cell, the GA-PSR Handover Command message shall include the set of PSI or SI messages required for mobile station to operate in the new cell within the *PS Handover to GERAN PSI IE* or *PS Handover to GERAN SI IE* (see A/Gb mode to A/Gb mode PS handover described in 3GPP TS 44.060 [45]). +- For the case of PS handover to a GERAN cell the MS shall ignore the value of the Page Mode, Global TFI and Container ID information elements included in the PS HANDOVER COMMAND message carried within the GA-PSR Handover Command message. +- For the case of PS Handover to a GERAN cell, the PS Handover Command message created by the target BSS shall always indicate the PS Handover type as being non-synchronized (see 3GPP TS 44.060 [45]). + +Upon reception of a **GA-PSR HANDOVER COMMAND** message from the GANC the MS shall: + +- stop timer TU4004. +- suspend all NAS layer signalling transmissions; +- start the connection establishment to the target BSS/RNC by using the contents of the *PS Handover to GERAN Command IE* or *PS Handover to UTRAN Command IE* (included in the **GA-PSR HANDOVER COMMAND** message) which contains either a **PS Handover Command** message (see 3GPP TS 44.060 [45]) created by the target BSS (for PS handover to a GERAN cell) or a **Handover to UTRAN Command** message (see 3GPP TS 25.331 [40]) created by the target RNC (for PS handover to a UTRAN cell). These encapsulated messages carry information about the target cell identifier and radio parameters relevant for the target radio access technology. + +### 8.14.5 Successful completion of the PS Handover from GAN A/Gb mode + +From the MS perspective the procedure for PS handover from a GAN A/Gb mode cell is started upon reception of the **GA-PSR HANDOVER COMMAND** message from the GANC and completed using procedures applicable to the target radio access technology (see Note 1). Upon successfully completing the PS handover from a GAN A/Gb mode cell the MS shall: + +- switch to GERAN/UTRAN mode (i.e. switch the serving RR to GSM RR or UTRAN RRC). +- enter GA-RC-REGISTERED state. + +- either deregister from GAN A/Gb mode as defined in sub-clause 6.4 or remain in the GA-RC-REGISTERED state but consider the GA-PSR Transport Channel previously used in the GAN A/Gb mode cell as implicitly released. + +From the source GANC perspective the procedure for PS handover from a GAN A/Gb mode cell is started upon receiving a **GA-PSR HANDOVER INFORMATION** message from the MS and deciding to perform PS handover to a GERAN/UTRAN cell. It is completed upon being told by the SGSN to delete the packet flow contexts corresponding to that MS (see Note 2). + +From the target BSS/RNC perspective the procedure for PS handover from a GAN A/Gb mode cell is started upon receiving a **PS Handover Request** message (target BSS) or a **Relocation Request** message (target RNC) from the SGSN and completed upon receiving confirmation from the MS that it has arrived in the target cell (see Note 1). + +NOTE 1: The requirements concerning the establishment of the radio connection towards the target radio access technology and the corresponding signalling procedures are outside of the scope of this specification. + +NOTE 2: The target RAT informs the source RAT (e.g. by sending a **Forward Relocation Complete** message) that PS handover was successful so that the local release of the GA-PSR Transport Channel can be triggered. + +### 8.14.6 Abnormal Cases + +If timer TU4004 expires the MS shall either move-out to GERAN/UTRAN mode or remain in GAN A/Gb mode if the conditions that caused the MS to initiate PS handover have been resolved. In the latter case, the MS may subsequently re-initiate PS handover based on the triggering events described in clause 8.14.1. + +If the MS is unable to act on the **GA-PSR HANDOVER COMMAND** message it shall discard it, send the source GANC a **GA-PSR HANDOVER FAILURE** message and resume normal operation as if the **GA-PSR HANDOVER COMMAND** message had not been received. The GA-PSR cause value in the **GA-PSR HANDOVER FAILURE** message shall be set to "PS handover failure - incorrect handover command". + +If the MS is able to act on the **GA-PSR HANDOVER COMMAND** message but is unable to establish the radio connection towards the target radio access technology it shall return to the old cell, send the source GANC a **GA-PSR HANDOVER FAILURE** message and resume normal operation as if the **GA-PSR HANDOVER COMMAND** message had not been received. The GA-PSR cause value in the **GA-PSR HANDOVER FAILURE** message shall be set to "PS handover failure - target RAT access failure". + +For the case of PS handover to a GERAN cell, if the **GA-PSR HANDOVER COMMAND** message does not contain the minimum set of PSI or SI messages required for mobile station to operate in the new cell (see A/Gb mode to A/Gb mode PS handover described in 3GPP TS 44.060 [45]), the MS shall send the source GANC a **GA-PSR HANDOVER FAILURE** message and resume normal operation as if the **GA-PSR HANDOVER COMMAND** message had not been received. The GA-PSR cause value in the **GA-PSR HANDOVER FAILURE** message shall be set to "PS handover failure - missing SI/PSI information". + +For the case of PS handover to a GERAN cell, if the **PS HANDOVER COMMAND** message carried within the **GA-PSR HANDOVER COMMAND** message does not provide resources for at least one uplink TBF in the new cell, the MS shall send the source GANC a **GA-PSR HANDOVER FAILURE** message and resume normal operation as if the **GA-PSR HANDOVER COMMAND** message had not been received. The GA-PSR cause value in the **GA-PSR HANDOVER FAILURE** message shall be set to "PS handover failure - no uplink TBF allocation". + +### 8.14.7 Reception of GA-PSR HANDOVER FAILURE by the GANC + +Upon reception of a **GA-PSR HANDOVER FAILURE** message from an MS the GANC shall initiate the release of resources in the target radio access technology. + +# --- 8a GA-RRC elementary procedures + +## 8a.1 GA-RRC connection establishment + +The GAN Iu mode GA-RRC CS and PS connections are logical connections between the MS and the GANC. As described in 3GPP TS 43.318, the GA-RRC sub-layer in the MS contains two entities, the CS domain GA-RRC sublayer entity and the PS domain GA-RRC sublayer entity. These entities operate independently and in parallel; e.g., two GA-RRC connections are established in the case of simultaneous CS and PS services, one GA-RRC connection for each domain. Each GA-RRC sub-layer entity in the MS can be in one of two states, GA-RRC-IDLE or GA-RRC- + +CONNECTED. Figures showing state changes (e.g., from GA-RRC-IDLE to GA-RRC-CONNECTED) in this sub-clause refer to changes for a single GA-RRC sub-layer entity, either CS or PS. + +A GA-RRC connection is established when the upper layers in the MS request the establishment of a signalling connection for either CS or PS domain and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for that domain; i.e., no GA-RRC connection exists. When a successful response is received from the network, GA-RRC replies to the upper layer that the GA-RRC sub-layer entity in the MS has entered the RRC connected mode (i.e., the GA-RRC-CONNECTED state). The upper layers then have the possibility to request transmission of NAS messages to the network (as described in sub-clause 8a.2). + +Note that in the case of a network-initiated CS or PS session, the GA-RRC connection is implicitly established when the MS responds to the GA-RRC PAGING REQUEST message from the GANC with the GA-RRC INITIAL DIRECT TRANSFER message containing the paging response (see sub-clause 8a.3). + +Also, in the case of handover from GERAN or UTRAN to GAN Iu mode, the GA-RRC connection is implicitly established when the MS sends the GA-RRC RELOCATION ACK message to the GANC (normal case) or the GA-RRC RELOCATION ACCESS message to the GANC (exception case), as described in sub-clause 8a.10. + +![Sequence diagram showing the successful initiation of a GA-RRC connection by the MS.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-IDLE + MS->>GANC: 1. GA-RRC REQUEST + Note left of MS: Start TU5908 + GANC-->>MS: 2. GA-RRC REQUEST ACCEPT + Note left of MS: Stop TU5908 + Note left of MS: GA-RRC-CONNECTED +``` + +The diagram illustrates the successful initiation of a GA-RRC connection. It starts with the MS in the GA-RRC-IDLE state. The MS sends a '1. GA-RRC REQUEST' message to the GANC and starts timer TU5908. The GANC responds with '2. GA-RRC REQUEST ACCEPT'. Upon receiving this, the MS stops timer TU5908 and transitions to the GA-RRC-CONNECTED state. + +Sequence diagram showing the successful initiation of a GA-RRC connection by the MS. + +**Figure 8a.1.1 MS initiation of GA-RRC connection, successful case** + +![Sequence diagram showing the failure of the initiation of a GA-RRC connection by the MS.](a7c51c18111139f9aca2805114108565_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-IDLE + MS->>GANC: 1. GA-RRC REQUEST + Note left of MS: Start TU5908 + GANC-->>MS: 2. GA-RRC REQUEST REJECT + Note left of MS: Stop TU5908 + Note left of MS: GA-RRC-IDLE +``` + +The diagram illustrates the failure of the initiation of a GA-RRC connection. It starts with the MS in the GA-RRC-IDLE state. The MS sends a '1. GA-RRC REQUEST' message to the GANC and starts timer TU5908. The GANC responds with '2. GA-RRC REQUEST REJECT'. Upon receiving this, the MS stops timer TU5908 and remains in the GA-RRC-IDLE state. + +Sequence diagram showing the failure of the initiation of a GA-RRC connection by the MS. + +**Figure 8a.1.2 MS initiation of GA-RRC connection, failure case** + +### 8a.1.1 Initiation of GA-RRC connection establishment by the MS + +The MS initiates the establishment of the GA-RRC connection when the upper layers in the MS request the establishment of a signalling connection for either CS or PS domain and the GA-RRC sub-layer entity in the MS is in GA-RRC-IDLE state for that domain. + +Before initiation of the GA-RRC connection establishment request, the MS shall check for access permission based on Access Control Class bits returned within GA-RC REGISTER ACCEPT message as defined in [12]. + +If it is allowed for the MS to access the network, the MS shall send a GA-RRC REQUEST message to the GANC on the established TCP connection, including the IE "CN Domain Identity" and the IE "Establishment Cause", and start timer TU5908 for the domain (i.e., the MS may have up to two instances of the TU5908 timer running at the same time, one for each domain). + +### 8a.1.2 Reception of GA-RRC REQUEST by GANC + +When the GANC receives the GA-RRC REQUEST message, the GANC may either accept or reject the GA-RRC connection establishment request. + +#### 8a.1.2.1 GA-RRC connection establishment request accepted + +If the GANC accepts the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST ACCEPT message to the MS including the IE "CN Domain Identity". + +#### 8a.1.2.2 GA-RRC connection establishment request rejected + +If the GANC rejects the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST REJECT message to the MS including the IE "CN Domain Identity". + +### 8a.1.3 GA-RRC connection establishment response handling in the MS + +#### 8a.1.3.1 GA-RRC connection establishment request accepted + +When the MS receives the GA-RRC REQUEST ACCEPT message, it shall: + +- if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity": + - stop timer TU5908 for that domain, + - move into the GA-RRC-CONNECTED state for that domain, + - indicate to upper layers that GA-RRC has entered the connected state for that domain, and + - send the GA-RRC INITIAL DIRECT TRANSFER message to the network; +- if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity": + - ignore the GA-RRC REQUEST ACCEPT message, and + - continue with the procedure as if the GA-RRC REQUEST ACCEPT message was not received. + +#### 8a.1.3.2 GA-RRC connection establishment request rejected + +When the MS receives the GA-RRC REQUEST REJECT message, it shall: + +- if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity": + - stop timer TU5908 for that domain, + - remain in the GA-RRC-IDLE state for that domain, and + - indicate to upper layers that GA-RRC was not able to enter the connected state for that domain; +- if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity": + - ignore the GA-RRC REQUEST REJECT message, and + - continue with the procedure as if the GA-RRC REQUEST REJECT message was not received. + +### 8a.1.4 Failure cases + +#### 8a.1.4.1 Timer TU5908 expiry + +If timer TU5908 expires in the MS, the GA-RRC sub-layer entity in the MS shall remain in the GA-RRC-IDLE state and indicate to upper layers that GA-RRC was not able to enter the connected state for the domain. + +## 8a.2 Upper layer message transmission + +The GA-RRC INITIAL DIRECT TRANSFER message is used to transfer the "initial" upper layer message for the domain (i.e., the first NAS message after GA-RRC connection establishment for the domain) from the MS to the GANC. Receipt of the GA-RRC INITIAL DIRECT TRANSFER message by the GANC triggers the establishment of the signalling connection to the indicated CN domain for the MS. The GA-RRC UPLINK DIRECT TRANSFER message is used to transfer all subsequent upper layer messages for the signalling connection from the MS to the GANC. + +The GA-RRC DOWNLINK DIRECT TRANSFER message is used to transfer upper layer messages from the GANC to the MS. + +### 8a.2.1 Initial upper layer message forwarding by the MS + +![Sequence diagram showing the initial direct transfer from MS to GANC.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 1. GA-RRC INITIAL DIRECT TRANSFER +``` + +The diagram illustrates the initial direct transfer process. It shows two entities: MS (Mobile Station) and GANC (GAN Controller). The MS is in the GA-RRC-CONNECTED state. A message labeled "1. GA-RRC INITIAL DIRECT TRANSFER" is sent from the MS to the GANC. + +Sequence diagram showing the initial direct transfer from MS to GANC. + +Figure 8a.2.1.1 Initial direct transfer, normal flow + +The GA-RRC sub-layer entity in the MS shall initiate the initial direct transfer procedure in the GA-RRC-CONNECTED state when the upper layers request the transfer of the first non-access stratum (NAS) message associated with the signalling connection. + +The MS shall include the IE "CN Domain Identity" and the contents of the received NAS message in the L3 Message IE. The MS also includes the Intra Domain NAS Node Selector (IDNNS) IE which may be used by the GANC to route the establishment of a signalling connection to a CN node within the indicated CN domain (i.e., using IuFlex). + +### 8a.2.2 Reception of GA-RRC INITIAL DIRECT TRANSFER by GANC + +When the GANC receives the GA-RRC INITIAL DIRECT TRANSFER message from a GA-RRC sub-layer entity in MS in the GA-RRC-CONNECTED state and there is no signalling connection to the indicated CN domain, the GANC shall establish an Iu signalling connection between the GANC and the indicated CN domain and transfer the initial NAS message to the CN. + +### 8a.2.3 Subsequent upper layer message forwarding by the MS + +![Sequence diagram showing the subsequent uplink direct transfer from MS to GANC.](4aa740e8119817a3f9b9f72d06eaa53d_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 1. GA-RRC UL DIRECT TRANSFER +``` + +The diagram illustrates the subsequent uplink direct transfer process. It shows two entities: MS (Mobile Station) and GANC (GAN Controller). The MS is in the GA-RRC-CONNECTED state. A message labeled "1. GA-RRC UL DIRECT TRANSFER" is sent from the MS to the GANC. + +Sequence diagram showing the subsequent uplink direct transfer from MS to GANC. + +Figure 8a.2.3.1 Uplink direct transfer, normal flow + +The GA-RRC sub-layer entity in the MS shall initiate the uplink direct transfer procedure in the GA-RRC-CONNECTED state when the upper layers request the transfer of a subsequent NAS message associated with the signalling connection (i.e., after the initial NAS message). + +The MS shall include the IE "CN Domain Identity" and the contents of the received NAS message in the IE "L3 Message". + +### 8a.2.4 Reception of GA-RRC UPLINK DIRECT TRANSFER by GANC + +When the GANC receives the GA-RRC UPLINK DIRECT TRANSFER message from a GA-RRC sub-layer entity in the MS in the GA-RRC-CONNECTED state, the GANC shall transfer the NAS message to the CN using the existing signalling connection. + +### 8a.2.5 Upper layer message forwarding by the GANC + +![Sequence diagram for Downlink direct transfer, normal flow. The diagram shows a Mobile Station (MS) and a GANC. The MS has a GA-RRC-CONNECTED state. A message labeled '1. GA-RRC DL DIRECT TRANSFER' is sent from the GANC to the MS.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + GANC->>MS: 1. GA-RRC DL DIRECT TRANSFER + +``` + +Sequence diagram for Downlink direct transfer, normal flow. The diagram shows a Mobile Station (MS) and a GANC. The MS has a GA-RRC-CONNECTED state. A message labeled '1. GA-RRC DL DIRECT TRANSFER' is sent from the GANC to the MS. + +Figure 8a.2.5.1 Downlink direct transfer, normal flow + +The downlink direct transfer procedure is initiated by the GANC when the GANC receives a NAS message from a CN domain (i.e., after the establishment of the GA-RRC connection to the MS for the domain). + +The GANC shall include the IE "CN Domain Identity" and the contents of the received NAS message in the IE "L3 Message". + +### 8a.2.6 Reception of GA-RRC DOWNLINK DIRECT TRANSFER by the MS + +When the MS receives the GA-RRC DOWNLINK DIRECT TRANSFER message it shall, using the IE "CN Domain Identity", route the contents of the IE "NAS message" and the value of the IE "CN Domain Identity" to upper layers. + +#### 8a.2.6.1 Invalid GA-RRC DOWNLINK DIRECT TRANSFER + +If the MS receives a GA-RRC DOWNLINK DIRECT TRANSFER message and GA-RRC sub-layer entity in the MS is not in GA-RRC-CONNECTED state for the indicated domain, the MS shall: + +- ignore the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message; +- transmit a GA-RRC STATUS message to the GANC as follows: + - set the IE "GA-RRC Cause" to "Message type not compatible with protocol state" + - include the received message contents in the IE "PDU in Error" +- continue with any ongoing procedure and act as if the GA-RRC DOWNLINK DIRECT TRANSFER message was not received. + +## 8a.3 Paging + +The GANC uses the paging procedure to transmit paging information received from the CN to the MS. The procedure also results in GA-RRC connection establishment between the MS and the GANC for the indicated domain. + +![Sequence diagram for Paging, normal flow. The diagram shows a Mobile Station (MS) and a GANC. The MS starts in GA-RRC-IDLE state. The GANC sends a '1. GA-RRC PAGING REQUEST' to the MS. The MS responds with '2. GA-RRC INITIAL DIRECT TRANSFER (Paging Response)' and transitions to GA-RRC-CONNECTED state.](9ddc2a6358c46a4717ceaed7183b6a46_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-IDLE + GANC->>MS: 1. GA-RRC PAGING REQUEST + MS->>GANC: 2. GA-RRC INITIAL DIRECT TRANSFER (Paging Response) + Note left of MS: GA-RRC-CONNECTED + +``` + +Sequence diagram for Paging, normal flow. The diagram shows a Mobile Station (MS) and a GANC. The MS starts in GA-RRC-IDLE state. The GANC sends a '1. GA-RRC PAGING REQUEST' to the MS. The MS responds with '2. GA-RRC INITIAL DIRECT TRANSFER (Paging Response)' and transitions to GA-RRC-CONNECTED state. + +Figure 8a.3.1 Paging, normal flow + +### 8a.3.1 Initiation of paging + +The GANC sends the GA-RRC PAGING REQUEST message to the MS when the GANC receives a PAGING message over the Iu interface from a CN domain. The IMSI of the MS to be paged is identified by the IE "Permanent NAS UE Identity" received in the request from the CN. If the request also includes the (P-)TMSI then the GANC shall include the (P-)TMSI in the IE "Mobile Identity"; else the GANC shall include the IMSI in the IE "Mobile Identity". The GANC also includes the IE "CN Domain Identity" and the IE "GA-RRC Paging Cause", if a cause is received from the CN. + +### 8a.3.2 Reception of GA-RRC PAGING REQUEST by the MS + +If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall: + +- if timer TU5908 is not active for the domain and access to the network is allowed: + - indicate reception of paging to upper layers, and + - forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers; + - Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1. +- if timer TU5908 is active for the domain: + - ignore the GA-RRC PAGING REQUEST message, and + - continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received. + +### 8a.3.3 Abnormal Cases + +If the MS receives a GA-RRC PAGING REQUEST message and the GA-RRC sublayer entity in the MS is in GA-RRC-CONNECTED state for the indicated domain or the MS is in the GA-RC-REGISTERED state but in GERAN/UTRAN/E-UTRAN mode, the MS shall: + +- ignore the GA-RRC PAGING REQUEST message, and +- continue with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. + +If the MS receives a GA-RRC PAGING REQUEST and the mobile identity included in the message does not match any of the valid identities assigned to the MS, the MS shall: + +- ignore the GA-RRC PAGING REQUEST message, and +- continue with any ongoing procedure as if the GA-RRC PAGING REQUEST message was not received. + +## 8a.4 Transport channel activation + +There are two versions of the transport channel activation procedure, the circuit transport channel (i.e., the "RTP channel") activation procedure and the packet transport channel activation procedure. As illustrated in the following sub-clauses, these two procedures use the same messages and the same basic message flows (as illustrated in the following figure), but differ in the content of the messages. + +![Sequence diagram showing the normal flow of transport channel activation between MS and GANC. The MS is in the GA-RRc-CONNECTED state. The sequence is: 1. GA-RRc ACTIVATE CHANNEL (GANC to MS), 2. GA-RRc ACTIVATE CHANNEL ACK (MS to GANC), 3. GA-RRc ACTIVATE CHANNEL COMPLETE (GANC to MS). The process is triggered by 'Start TU5911' and completed by 'Stop TU5911'.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRc-CONNECTED + Note left of MS: Start TU5911 + GANC->>MS: 1. GA-RRc ACTIVATE CHANNEL + MS-->>GANC: 2. GA-RRc ACTIVATE CHANNEL ACK + GANC-->>MS: 3. GA-RRc ACTIVATE CHANNEL COMPLETE + Note left of MS: Stop TU5911 + +``` + +Sequence diagram showing the normal flow of transport channel activation between MS and GANC. The MS is in the GA-RRc-CONNECTED state. The sequence is: 1. GA-RRc ACTIVATE CHANNEL (GANC to MS), 2. GA-RRc ACTIVATE CHANNEL ACK (MS to GANC), 3. GA-RRc ACTIVATE CHANNEL COMPLETE (GANC to MS). The process is triggered by 'Start TU5911' and completed by 'Stop TU5911'. + +**Figure 8a.4.1 Transport channel activation, normal flow** + +### 8a.4.1 Circuit transport channel activation + +#### 8a.4.1.1 Initiation of circuit transport channel activation + +The following are the possible triggers for initiation of the circuit transport channel (CTC) activation procedure: + +- If the MS is in the GA-RRc-CONNECTED state for the CS domain and the GANC receives the RAB Assignment Request message from the MSC; +- If the MS is in the GA-RRc-CONNECTED state for the CS domain and the GANC receives the GA-RRc RELOCATION ACCESS message from the MS during the CS handover to GAN Iu mode process (see sub-clause 8a.10.5). + +One or more CTCs may be activated using a single instance of the channel activation procedure; however, it is not possible to activate both circuit and packet transport channels using a single instance of the channel activation procedure. + +The GANC begins the activation of the CTC(s) by transmitting the GA-RRc ACTIVATE CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating CS domain) and IE "CTC Activation List" which includes the parameters necessary to describe each circuit transport channel. + +#### 8a.4.1.2 Reception of GA-RRc ACTIVATE CHANNEL (CS domain) by the MS + +The MS shall act on the received GA-RRc ACTIVATE CHANNEL message indicating the CS domain as follows: + +- for each CTC specified in the IE "CTC Activation List": +- store the RAB ID; +- if the IE "RAB Configuration" indicates that the CTC is for AMR or AMR-WB speech, use the format specified in Annex A.1 and Annex D to code and decode the RTP packets; +- if the IE "RAB Configuration" indicates that the CTC is for circuit switched data, use the format specified in Annex A.2 to code and decode the RTP packets; +- use the value indicated by the IE "Sample Size" as the minimum sample size for the coding and decoding of the RTP packets, if the MS is not able to use the indicated value. If the circuit transport channel is for AMR or AMR-WB speech with RTP redundancy, the sample size is defined as the size of the new speech sample in each RTP packet, not including any redundant speech samples; +- configure the uplink RTP packets to be transmitted to the UDP port and IP address identified by the IE "RTP UDP Port" and the IE "GANC IP address", respectively; +- use the Payload Type included in the IE "Payload Type" for the PT field in the RTP header for the RTP packets; +- if received, use the configuration included in the IE "Multi-rate Configuration 2" for the circuit transport channel that is for AMR or AMR-WB speech; +- if received, use the configuration included in the IE "RTP Redundancy Configuration" for the circuit transport channel that is for AMR or AMR-WB speech. The redundancy policy is defined for each of the AMR modes specified in the IE "Multi-rate Configuration 2". The level of redundancy can span from no redundancy to double + +redundancy. In the same active codec set, a lower codec mode shall not be associated with a lower redundancy level than a higher codec mode. For example, the highest mode in the set is used with no redundancy, the next lower with single redundancy and rest of the modes with double redundancy. + +- if received, pass the contents of the NAS Synchronisation Indicator to upper layers. + +On completing the above procedure, the MS shall: + +- start timer TU5911 for the CS domain; +- transmit a GA-RRC ACTIVATE CHANNEL ACK message including the IE "CN Domain Identity" and the IE "CTC Activation Ack List". For each CTC specified in the IE "CTC Activation Ack List": +- include the IE "RAB ID" for the CTC with the same value as received in the GA-RRC ACTIVATE CHANNEL message in the IE "RAB ID"; +- include the IE "GA-RRC Cause" indicating either success (i.e., value '0') or a failure cause value; +- for each CTC that is successfully configured (i.e., GA-RRC Cause value is '0'): +- include the allocated UDP port number in the IE "RTP UDP Port" for the downlink RTP packets to be sent from the GANC to the MS; +- include the selected RTP sample size, to be used for uplink and downlink RTP packets, in the IE "Sample Size"; +- include the Payload Type in the IE "Payload Type"; +- if the IE "RTCP UDP Port" was received in the GA-RRC ACTIVATE CHANNEL message and the MS is capable of supporting RTCP, activate the uplink RTCP stream and include the IE "RTCP UDP Port" for the downlink RTCP packets to be sent from the GANC to the MS. + +#### 8a.4.1.3 Reception of GA-RRC ACTIVATE CHANNEL ACK (CS domain) by GANC + +On reception of the GA-RRC ACTIVATE CHANNEL ACK message indicating the CS domain, the GANC shall configure itself for transmission of RTP packets to the "RTP UDP Port" indicated in the message and RTCP packets to the "RTCP UDP Port" indicated in the message (if included) for each successfully activated CTC, and transmit a GA-RRC ACTIVATE CHANNEL COMPLETE message to the MS. + +To enable downlink quality measurements in the MS, the GANC shall send at least one RTP frame each 480 ms for each active CTC. During periods of discontinuous transmission (DTX), if the CTC is for AMR or AMR-WB speech, each RTP frame transmitted by the GANC shall bear a format in the AMR/AMR-WB payload Table of Contents that either (a) omits all NO\_DATA indications and contains only the next AMR speech or SID frame that is available, or (b) includes a single NO\_DATA frame should no AMR speech or SID frame become available for 480 ms. The RTP timestamp shall indicate the time of that speech or SID or NO\_DATA frame. See Section A.1.2 of Annex A for examples. + +#### 8a.4.1.4 Reception of GA-RRC ACTIVATE CHANNEL COMPLETE (CS domain) by MS + +On reception of the GA-RRC ACTIVATE CHANNEL COMPLETE message indicating the CS domain, the MS shall stop timer TU5911 for the CS domain and consider the successfully activated CTC(s) to be available for use by upper layers. To enable uplink quality measurements in the GANC, the MS shall send at least one RTP frame each 480 ms for each active CTC. During periods of discontinuous transmission (DTX), each RTP frame transmitted by the MS shall bear a format in the AMR/AMR-WB payload Table of Contents that either (a) omits all NO\_DATA indications and contains only the next AMR speech or SID frame that is available, or (b) includes a single NO\_DATA frame should no AMR speech or SID frame become available for 480 ms. The RTP timestamp shall indicate the time of that speech or SID or NO\_DATA frame. See Section A.1.2 of Annex A for examples. + +### 8a.4.2 Packet transport channel activation + +#### 8a.4.2.1 Initiation of packet transport channel activation + +The following is the possible trigger for initiation of the packet transport channel activation procedure: + +- If the MS is in the GA-RRC-CONNECTED state for the PS domain and the GANC receives the RAB Assignment Request message from the SGSN. + +One or more packet transport channels may be activated using a single instance of the channel activation procedure; however, it is not possible to activate both circuit and packet transport channels using a single instance of the channel activation procedure. + +The GANC begins the activation of the PTC(s) by transmitting the GA-RRC ACTIVATE CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating PS domain) and IE "PTC Activation List" which includes the parameters necessary to describe each packet transport channel. + +#### 8a.4.2.2 Reception of GA-RRC ACTIVATE CHANNEL (PS domain) by the MS + +The MS shall act on the received GA-RRC ACTIVATE CHANNEL message indicating the PS domain as follows: + +- for each PTC specified in the IE "PTC Activation List": +- store the RAB ID; +- allocate local PTC resources based on the values in the IE "RAB Configuration"; +- use the TEID value included in the IE "GANC TEID" for the TEID field in the GA-RRC PDU messages to be sent to the GANC; +- use the TEID value included in the IE "MS TEID" to verify the TEID field in the GA-RRC PDU messages to be received from the GANC; +- configure the uplink GA-RRC PDU messages to be transmitted to the UDP port and IP address identified by the IE "GANC UDP Port" and the IE "GANC IP address", respectively. + +On completing the above procedure, the MS shall: + +- start timer TU5911 for the PS domain; +- transmit a GA-RRC ACTIVATE CHANNEL ACK message including the IE "CN Domain Identity" and the IE "PTC Activation Ack List". For each PTC specified in the IE "PTC Activation Ack List": +- include the IE "RAB ID" for the PTC with the same value as received in the GA-RRC ACTIVATE CHANNEL message in the IE "RAB ID"; +- include the IE "GA-RRC Cause" indicating either success (i.e., value '0') or a failure cause value; +- for each PTC that is successfully configured (i.e., GA-RRC Cause value is '0'): +- include the allocated UDP port number in the IE "MS UDP Port" for the downlink GA-RRC PDU messages to be sent from the GANC to the MS. + +#### 8a.4.2.3 Reception of GA-RRC ACTIVATE CHANNEL ACK (PS domain) by GANC + +On reception of the GA-RRC ACTIVATE CHANNEL ACK message indicating the PS domain, the GANC shall configure itself for transmission of GA-RRC PDU messages to the "MS UDP Port" indicated in the message for each successfully activated PTC, and transmit a GA-RRC ACTIVATE CHANNEL COMPLETE message to the MS. + +#### 8a.4.2.4 Reception of GA-RRC ACTIVATE CHANNEL COMPLETE (PS domain) by MS + +On reception of the GA-RRC ACTIVATE CHANNEL COMPLETE message indicating the PS domain, the MS shall stop timer TU5911 for the PS domain, and start timer TU4001 for each of the successfully activated PTC(s) which are now available for use by upper layers. + +## 8a.5 GA-RRC connection release + +### 8a.5.1 GA-RRC connection release request by MS + +If the MS needs to release the GA-RRC connection and signalling connection to a particular CN domain, it shall send the GA-RRC RELEASE REQUEST message to the GANC and start timer TU5909 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following: + +- #40: UE generated signalling connection release +- #115: unspecified failure + +![Sequence diagram for GA-RRC connection release request by MS](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +A sequence diagram showing the interaction between a Mobile Station (MS) and a GANC. The MS is initially in the GA-RRC-CONNECTED state. It sends a '1. GA-RRC RELEASE REQUEST' message to the GANC and starts timer TU5909. The GANC receives the request. + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 1. GA-RRC RELEASE REQUEST + Note left of MS: Start TU5909 +``` + +Sequence diagram for GA-RRC connection release request by MS + +Figure 8a.5.1.1 GA-RRC connection release request by MS + +### 8a.5.2 Reception of GA-RRC RELEASE REQUEST by GANC + +When the GANC receives the GA-RRC RELEASE REQUEST message, it shall request the selected CN domain to release the Iu connection for the MS, including all active RABs for that domain. The GANC selects the CN domain based on the value of the received IE "CN Domain Identity". + +### 8a.5.3 Initiation of GA-RRC connection release by GANC + +The GANC initiates the GA-RRC connection release procedure to command the MS to release the GA-RRC connection and any user plane resources for a particular domain and instruct the GA-RRC sub-layer entity of the MS to leave the GA-RRC-CONNECTED state and return to the GA-RRC-IDLE state for the domain. The GANC normally initiates this procedure when it receives the Iu Release Command from the CN; however, the GANC may also initiate this procedure under certain failure conditions. + +![Sequence diagram for GA-RRC connection release, normal flow](bd57a547bec253d4179e5c4491c53dbb_img.jpg) + +A sequence diagram showing the interaction between a Mobile Station (MS) and a GANC. The MS is initially in the GA-RRC-CONNECTED state. The GANC sends a '1. GA-RRC RELEASE' message to the MS, which stops timer TU5909. The MS then sends a '2. GA-RRC RELEASE COMPLETE' message back to the GANC and transitions to the GA-RRC-IDLE state. + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + GANC->>MS: 1. GA-RRC RELEASE + Note left of MS: Stop TU5909 + MS->>GANC: 2. GA-RRC RELEASE COMPLETE + Note left of MS: GA-RRC-IDLE +``` + +Sequence diagram for GA-RRC connection release, normal flow + +Figure 8a.5.3.1 GA-RRC connection release, normal flow + +The GANC initiates the GA-RRC connection release procedure by sending the GA-RRC RELEASE message to the MS. + +The GA-RRC RELEASE message includes the IE "GA-RRC Cause". The GA-RRC Cause value should be one of the following: + +- #83: normal release; e.g., at the end of a call + +#115: unspecified failure + +Other values, if received, should be treated as "unspecified failure". + +### 8a.5.4 Reception of GA-RRC RELEASE by MS + +When the GA-RRC sublayer entity in the MS receives the GA-RRC RELEASE message, it shall: + +- send a GA-RRC RELEASE COMPLETE message to the GANC, +- release the GA-RRC connection and any user plane resources for the indicated domain, +- stop timer TU5002 for the domain (if running) (see sub-clause 8a.8), +- stop timer TU5909 for the domain (if running), and +- enter the GA-RRC-IDLE state for the domain. + +### 8a.5.5 Failure cases + +#### 8a.5.5.1 Timer TU5909 expiry + +If timer TU5909 expires in the MS, the GA-RRC sublayer entity in the MS shall release the GA-RRC connection and any user plane resources and enter the GA-RRC-IDLE state for the domain associated with the TU5909 timer. + +## 8a.6 Security mode control + +The security mode control procedure is used by the network to set the security mode; i.e., the settings for integrity protection and encryption, including the algorithms to use. This information is not used when GA-RRC is the serving entity in the MS, but shall be stored in the MS for possible future use after a handover from GAN Iu mode to UTRAN during the same upper layer transaction (i.e., the UTRAN RRC layer becomes the serving entity during this upper layer transaction). + +The security mode control procedure also proves that the MS identity that is authenticated to the GANC is the same as the MS identity authenticated to the core network. + +The security mode control procedure applies only for a MS in the GA-RRC-CONNECTED state for either the CS domain or the PS domain. + +The security mode control procedure is always triggered by the network. + +![Sequence diagram of Security mode control, normal flow](73da53f7da73c0e2ead71eb1e2f746fb_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + GANC->>MS: 1. GA-RRC SECURITY MODE COMMAND + MS->>GANC: 2. GA-RRC SECURITY MODE COMPLETE + Note right of GANC: Verify MAC +``` + +The diagram illustrates the normal flow of the security mode control procedure. It starts with the MS in the GA-RRC-CONNECTED state. The GANC sends a '1. GA-RRC SECURITY MODE COMMAND' message to the MS. The MS responds with a '2. GA-RRC SECURITY MODE COMPLETE' message to the GANC. Finally, the GANC performs a 'Verify MAC' operation. + +Sequence diagram of Security mode control, normal flow + +Figure 8a.6.1 Security mode control, normal flow + +### 8a.6.1 Security mode control initiation + +The GANC initiates the security mode control procedure by sending a GA-RRC SECURITY MODE COMMAND message to the MS. This message includes the IE "Selected Integrity Protection Algorithm", the IE "Selected Encryption Algorithm" (optional), and the IE "Random Number". The GANC selects the algorithms based on the + +permitted algorithms received from the CN and the MS security capabilities indicated in the IE "3G Security Capability" received from the MS in the GA-RC REGISTER REQUEST message. + +### 8a.6.2 Security mode control completion + +Whenever the MS receives a valid GA-RRC SECURITY MODE COMMAND message, it shall, if a (U)SIM is present and considered valid and the key set identifier (KSI) stored on the (U)SIM indicates that an integrity key and cipher key are available for the domain indicated in the IE "CN Domain Identity", store the selected integrity protection algorithm and (if received) the selected encryption algorithm for possible future use after a handover from GAN Iu mode to UTRAN during the same upper layer transaction. If handover from GAN Iu mode to UTRAN occurs, encryption is enabled if the IE "Selected Encryption Algorithm" is present in the message and disabled otherwise. + +The MS shall also calculate a MAC (Message Authentication Code). The MAC shall be calculated over the following data: + +RAND | IMSI + +using "HMAC-SHA1-96" algorithm, as specified in [24] with the integrity key (IK) for the domain indicated in the IE "CN Domain Identity" used as the authentication key. + +In the formulas above, the "|" character denotes concatenation. RAND is the 16-octet random number received from the GANC in the GA-RRC SECURITY MODE COMMAND message. IMSI is the MS IMSI, in the same format as defined for the Mobile Identity IE as defined in [8]; i.e. as a variable-length sequence of digits in BCD format (e.g. the IMSI "123456789098765" is encoded as the following octets (in hexadecimal): "21 43 65 87 09 89 67 F5"). Network byte order is used. + +The IK key is the IK that has been derived during the last authentication for the domain indicated in the IE "CN Domain Identity". The length of the MAC is 12 octets. + +When the appropriate action on the GA-RRC SECURITY MODE COMMAND message has been taken, the MS sends a GA-RRC SECURITY MODE COMPLETE message to the GANC. The MS includes the calculated MAC value in the IE "Ciphering Command MAC". + +## 8a.7 Transport channel modification + +There are two versions of the transport channel modification procedure, the circuit transport channel modification procedure and the packet transport channel modification procedure. As illustrated in the following sub-clauses, these two procedures use the same messages and the same basic message flows (as illustrated in the following figure), but differ in the content of the messages. + +![Sequence diagram showing the normal flow of transport channel modification between MS and GANC. The MS is in a GA-RRC-CONNECTED state. The GANC sends a GA-RRC MODIFY CHANNEL message to the MS, and the MS responds with a GA-RRC MODIFY CHANNEL ACK message.](f7d969388c4f7e30cd04a061314bfa0e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + GANC->>MS: 1. GA-RRC MODIFY CHANNEL + MS-->>GANC: 2. GA-RRC MODIFY CHANNEL ACK + +``` + +Sequence diagram showing the normal flow of transport channel modification between MS and GANC. The MS is in a GA-RRC-CONNECTED state. The GANC sends a GA-RRC MODIFY CHANNEL message to the MS, and the MS responds with a GA-RRC MODIFY CHANNEL ACK message. + +Figure 8a.7.1 Transport channel modification, normal flow + +### 8a.7.1 Circuit transport channel modification + +#### 8a.7.1.1 Initiation of circuit transport channel modification + +The GANC initiates the circuit transport channel (CTC) modification procedure when it determines that one or more active CTCs require modification; e.g., based on information received from the MSC in the RAB Assignment Request message or based on local GANC logic. + +The following CTC parameters may be modified: + +- RAB Configuration + +- Sample Size +- GANC RTP UDP Port +- GANC IP Address +- Multi-rate Configuration 2 +- RTP Redundancy Configuration +- GANC RTCP UDP Port +- NAS Synchronisation Indicator + +The GANC only includes the IEs which specify modifications to the existing CTC parameters. + +One or more CTCs may be modified using a single instance of the channel modification procedure; however, it is not possible to modify both circuit and packet transport channels using a single instance of the channel modification procedure. + +The GANC begins the modification of the CTC(s) by transmitting the GA-RRC MODIFY CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating CS domain) and IE "CTC Modification List" which includes the parameters necessary to describe the modifications to each circuit transport channel. + +#### 8a.7.1.2 Reception of GA-RRC MODIFY CHANNEL (CS domain) by the MS + +On receipt of the GA-RRC MODIFY CHANNEL message indicating the CS domain, the MS shall process the specified CTC modifications. + +On completion of the modification of the CTC(s), the MS shall: + +- transmit a GA-RRC MODIFY CHANNEL ACK message including the IE "CN Domain Identity" and the IE "CTC Modification Ack List". For each CTC specified in the IE "CTC Modification Ack List": +- include the IE "RAB ID" for the CTC with the same value as received in the GA-RRC MODIFY CHANNEL message in the IE "RAB ID"; +- include the IE "GA-RRC Cause" indicating either success (i.e., value '0') or a failure cause value; +- for each CTC that is successfully modified (i.e., GA-RRC Cause value is '0'): +- include the modified parameter values currently used by the MS. + +When the MS has sent the GA-RRC MODIFY CHANNEL ACK message, it shall start transmitting RTP packets based on the successful parameter modifications. The MS shall be able to receive RTP packets with the old parameters until the MS determines that the first RTP packet using the new parameters has been received. + +#### 8a.7.1.3 Reception of GA-RRC MODIFY CHANNEL ACK (CS domain) by GANC + +On reception of the GA-RRC MODIFY CHANNEL ACK message indicating the CS domain, the GANC shall configure itself for transmission of RTP packets to the MS using the new parameter values for the successfully modified CTC(s). The GANC shall be able to receive RTP packets with the old parameters until the GANC determines that the first RTP packet using the new parameters has been received. + +### 8a.7.2 Packet transport channel modification + +#### 8a.7.2.1 Initiation of packet transport channel modification + +The GANC initiates the packet transport channel (PTC) modification procedure when it determines that one or more active PTCs require modification; e.g., based on information received from the SGSN in the RAB Assignment Request message or based on local GANC logic. + +The following PTC parameters may be modified: + +- RAB Configuration + +- GANC UDP Port +- GANC IP Address + +The GANC only includes the IEs which specify modifications to the existing PTC parameters. + +One or more PTCs may be modified using a single instance of the channel modification procedure; however, it is not possible to modify both circuit and packet transport channels using a single instance of the channel modification procedure. + +The GANC begins the modification of the PTC(s) by transmitting the GA-RRC MODIFY CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating PS domain) and IE "PTC Modification List" which includes the parameters necessary to describe the modifications to each packet transport channel. + +#### 8a.7.2.2 Reception of GA-RRC MODIFY CHANNEL (PS domain) by the MS + +On receipt of the GA-RRC MODIFY CHANNEL message indicating the PS domain, the MS shall process the specified PTC modifications. + +On completion of the modification of the PTC(s), the MS shall: + +- transmit a GA-RRC MODIFY CHANNEL ACK message including the IE "CN Domain Identity" and the IE "PTC Modification Ack List". For each PTC specified in the IE "PTC Modification Ack List": +- include the IE "RAB ID" for the PTC with the same value as received in the GA-RRC MODIFY CHANNEL message in the IE "RAB ID"; +- include the IE "GA-RRC Cause" indicating either success (i.e., value '0') or a failure cause value; +- for each PTC that is successfully modified (i.e., GA-RRC Cause value is '0'): +- include the modified parameter values currently used by the MS. + +When the MS has sent the GA-RRC MODIFY CHANNEL ACK message, it shall start transmitting GA-RRC PDU messages based on the successful parameter modifications. The MS shall be able to receive GA-RRC PDU messages with the old parameters until the MS determines that the first GA-RRC PDU message using the new parameters has been received. + +#### 8a.7.2.3 Reception of GA-RRC MODIFY CHANNEL ACK (PS domain) by GANC + +On reception of the GA-RRC MODIFY CHANNEL ACK message indicating the PS domain, the GANC shall configure itself for transmission of GA-RRC PDU messages to the MS using the new parameter values for the successfully modified PTC(s). The GANC shall be able to receive GA-RRC PDU messages with the old parameters until the GANC determines that the first GA-RRC PDU message using the new parameters has been received. + +## 8a.8 Transport channel deactivation + +### 8a.8.1 Transport channel deactivation request by MS + +If the MS needs to deactivate one or more transport channels for a particular domain, it shall send the GA-RRC DEACTIVATE CHANNEL REQUEST message to the GANC and start timer TU5002 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following: + +- #0: normal release (e.g., due to inactivity timer timeout) +- #115: unspecified failure + +![Sequence diagram showing the transport channel deactivation request by MS. The MS (GA-RRC-CONNECTED) sends a '1. GA-RRc DEACTIVATE CHANNEL REQUEST' message to the GANC. The process starts with 'Start TU5002'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: Start TU5002 + MS->>GANC: 1. GA-RRc DEACTIVATE CHANNEL REQUEST + +``` + +Sequence diagram showing the transport channel deactivation request by MS. The MS (GA-RRC-CONNECTED) sends a '1. GA-RRc DEACTIVATE CHANNEL REQUEST' message to the GANC. The process starts with 'Start TU5002'. + +**Figure 8a.8.1 Transport channel deactivation request by MS** + +### 8a.8.2 Reception of GA-RRc DEACTIVATE CHANNEL REQUEST by GANC + +When the GANC receives the GA-RRc DEACTIVATE CHANNEL REQUEST message, it shall request the selected CN domain to release the identified RABs associated with the MS. The GANC selects the CN domain based on the value of the received IE "CN Domain Identity". Note that the GANC may also request the selected CN domain to release the Iu connection for the MS in this case, based on local policy settings. + +### 8a.8.3 Initiation of transport channel deactivation by GANC + +The GANC normally initiates this procedure when it receives the RAB Assignment message from the CN indicating RAB release; however, the GANC may also initiate this procedure under certain failure conditions. + +![Sequence diagram showing the normal flow of transport channel deactivation. The GANC sends '1. GA-RRc DEACTIVATE CHANNEL' to the MS, which starts 'Stop TU5002'. The MS responds with '2. GA-RRc DEACTIVATE CHANNEL COMPLETE'.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: Stop TU5002 + GANC->>MS: 1. GA-RRc DEACTIVATE CHANNEL + MS->>GANC: 2. GA-RRc DEACTIVATE CHANNEL COMPLETE + +``` + +Sequence diagram showing the normal flow of transport channel deactivation. The GANC sends '1. GA-RRc DEACTIVATE CHANNEL' to the MS, which starts 'Stop TU5002'. The MS responds with '2. GA-RRc DEACTIVATE CHANNEL COMPLETE'. + +**Figure 8a.8.3 Transport channel deactivation, normal flow** + +One or more circuit or packet transport channels may be deactivated using a single instance of the channel deactivation procedure; however, it is not possible to deactivate both circuit and packet transport channels using a single instance of the channel deactivation procedure. + +The GA-RRc DEACTIVATE CHANNEL message includes the IE "GA-RRc Cause" with value as follows: + +- #0: normal event, e.g. deactivate due to RAB release request from CN +- #115: unspecified failure +- #10: relocation cancelled (e.g., the handover procedure is stopped because the call has been cleared) + +### 8a.8.4 Reception of GA-RRc DEACTIVATE CHANNEL by MS + +When the MS receives the GA-RRc DEACTIVATE CHANNEL message, it shall: + +- deactivate the CTC(s) or PTC(s) identified in the IE "RAB ID List"; +- send a GA-RRc DEACTIVATE CHANNEL COMPLETE message to the GANC. + +### 8a.8.5 Failure cases + +#### 8a.8.5.1 Timer TU5002 expiry + +If timer TU5002 expires in the MS, the MS shall release the associated transport channel(s). + +## 8a.9 PS domain user plane data transfer + +When the corresponding GA-RRc PTC has been activated, both the MS and the GANC can transfer PS domain user data using the GA-RRc PDU message as illustrated in the following figure: + +![Sequence diagram showing GA-RRC PS domain user data transfer. The diagram shows a Mobile Station (MS) and a GANC. The MS is connected to the GANC via a GA-RRC-CONNECTED state. The GA-RRC PTC is activated. The MS sends a GA-RRC PDU to the GANC, and the GANC sends a GA-RRC PDU back to the MS.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note over MS, GANC: GA-RRC PTC is activated + MS->>GANC: GA-RRC PDU + GANC->>MS: GA-RRC PDU +``` + +Sequence diagram showing GA-RRC PS domain user data transfer. The diagram shows a Mobile Station (MS) and a GANC. The MS is connected to the GANC via a GA-RRC-CONNECTED state. The GA-RRC PTC is activated. The MS sends a GA-RRC PDU to the GANC, and the GANC sends a GA-RRC PDU back to the MS. + +Figure 8a.9.1 GA-RRC PS domain user data transfer + +### 8a.9.1 MS initiates uplink PS domain user plane data transfer + +Assuming that the GA-RRC PTC associated with the identified RAB has been activated as specified in sub-clause 8a.4.2, the MS is able to immediately forward any uplink PS domain user data packets for the RAB to the GANC using the PTC. Upon request from the upper layers to transfer an uplink PS domain user data packet associated with a RAB to the GANC, the PS domain GA-RRC sublayer entity in the MS shall restart the TU4001 timer for the PTC, encapsulate the complete PS domain user data packet within a GA-RRC PDU message, and send the GA-RRC PDU message to the GANC using the associated GA-RRC PTC. + +If sequencing has been activated for the PTC (i.e., Delivery Order is requested in the IE "RAB Configuration" associated with the PTC), the MS shall include GA-RRC PDU sequence number information in the GA-RRC PDU message sent to the GANC using the PTC. The GA-RRC PDU sequence number information handling is specified in sub-clause 11.1.3b.2. + +Note: The GTP-U G-PDU messages from the CN may include GTP-U sequence number information even though Delivery Order is not requested in the RAB Assignment (e.g., the GGSN implementation may always include GTP-U sequence number information). However, GTP-U messages from the GANC to the CN may not include sequence number information in this case (i.e., even though sequence number information is included from CN to GANC). + +### 8a.9.2 Processing of the received GA-RRC PDU message by the GANC + +Upon receiving the GA-RRC PDU message from the MS, the GANC shall relay the GA-RRC PDU payload within a GTP-U G-PDU message to the SGSN via the Iu-ps interface using the GTP-U protocol as defined in [53]. + +Note that all uplink GA-RRC PDU messages sent by the MS terminate at the GANC. + +### 8a.9.3 GANC initiates downlink PS domain user plane data transfer + +Assuming that the GA-RRC PTC associated with the identified RAB has been activated as specified in sub-clause 8a.4.2, the GANC is able to immediately forward any downlink PS domain user data packets for the RAB to the MS using the PTC. Upon receiving a downlink GTP-U G-PDU message for the MS from the CN, the GANC shall relay the GTP-U G-PDU payload within a GA-RRC PDU message to the MS using the associated GA-RRC PTC. + +### 8a.9.4 Processing of the received GA-RRC PDU message by the MS + +Upon receiving the GA-RRC PDU message from the GANC, the MS shall restart the TU4001 timer for the PTC, extract the received PS domain user data packet and forward the contents to the upper layers in the MS via the PDCP SAP as per standard UMTS. + +If sequencing has been activated for the PTC, the MS shall increment the expected downlink GA-RRC PDU sequence number for each GA-RRC PDU message received from the GANC using the PTC. + +Note that all downlink GA-RRC PDU messages received by the MS are sent from the GANC. + +### 8a.9.5 Abnormal Cases + +#### 8a.9.5.1 TU4001 timer expiry + +If timer TU4001 expires, the MS shall request deactivation of the PTC as specified in sub-clause 8a.8.1. + +#### 8a.9.5.2 GANC receives a GA-RRC PDU message while the GA-RRC PTC activation procedure is in progress + +Upon receiving an uplink GA-RRC PDU message while the GA-RRC PTC activation procedure for the PTC is in progress, the GANC will process the request as if the GA-RRC PTC was active. + +#### 8a.9.5.3 GANC receives a GA-RRC PDU message and the GA-RRC PTC is not active + +Upon receiving an uplink GA-RRC PDU message that is associated with a GA-RRC PTC that does not exist, the GANC shall discard the message and initiate PTC deactivation as defined in sub-clause 8a.8. + +#### 8a.9.5.4 Handling of out-of-sequence packets + +Packets received out-of-sequence by the MS shall be processed as described in sub-clause 11.1.3b.2. + +#### 8a.9.5.5 MS receives a GA-RRC PDU message while the GA-RRC PTC activation procedure is in progress + +Upon receiving a downlink GA-RRC PDU message before sending the response to a received PTC activation request, the MS shall queue the received GA-RRC PDU message and process the message immediately after completing the PTC activation. + +#### 8a.9.5.6 Uplink PS domain user data transfer failed due to lower layer failure + +If a lower layer failure is detected while attempting to send an uplink PS domain user data packet, the MS shall declare the procedure as failed and send the corresponding indication to upper layers. + +## 8a.10 Handover to GAN Iu mode + +The handover to GAN Iu mode procedure is applicable when the MS is in the GA-RC-REGISTERED state. + +The preparation phase of the handover to GAN Iu mode procedure is normally initiated when the GANC sends the GA-RRC RELOCATION REQUEST message to the MS, as illustrated in Figure 8a.10.1. + +The exception is when the GANC receives a Relocation Request message that does not include the IMSI parameter from a MSC. This exception case is described in sub-clause 8a.10.5. + +![Sequence diagram illustrating the successful case of handover to GAN Iu mode. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RC-REGISTERED state. The GANC sends a GA-RRC RELOCATION REQUEST (1) to the MS. The MS responds with a GA-RRC RELOCATION REQUEST ACK (2). The MS then transitions to the GA-RRC-CONNECTED state and sends a GA-RRC RELOCATION COMPLETE (3) to the GANC.](d48a71a2e72db63c807a4c4ea8d82d2e_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RC-REGISTERED + GANC->>MS: 1. GA-RRC RELOCATION REQUEST + MS->>GANC: 2. GA-RRC RELOCATION REQUEST ACK + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 3. GA-RRC RELOCATION COMPLETE +``` + +Sequence diagram illustrating the successful case of handover to GAN Iu mode. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RC-REGISTERED state. The GANC sends a GA-RRC RELOCATION REQUEST (1) to the MS. The MS responds with a GA-RRC RELOCATION REQUEST ACK (2). The MS then transitions to the GA-RRC-CONNECTED state and sends a GA-RRC RELOCATION COMPLETE (3) to the GANC. + +Figure 8a.10.1: Handover to GAN Iu mode, successful case + +### 8a.10.1 Reception of GA-RRC RELOCATION REQUEST by the MS + +The GA-RRC RELOCATION REQUEST message contains the IE "CN Domains to Handover" indicating the CS domain, the PS domain or both CS and PS domains. If the CS domain or both CS and PS domains is indicated, the message includes the IE "CTC Activation List". If the PS domain or both CS and PS domains is indicated, the message includes the IE "PTC Activation List". + +The MS shall act on the received GA-RRC RELOCATION REQUEST message containing the IE "CTC Activation List" as follows: + +- for each CTC specified in the IE "CTC Activation List": +- store the RAB ID; +- if the IE "RAB Configuration" indicates that the CTC is for AMR or AMR-WB speech, use the format specified in Annex A.1 and Annex D to code and decode the RTP packets; +- if the IE "RAB Configuration" indicates that the CTC is for circuit switched data, use the format specified in Annex A.2 to code and decode the RTP packets; +- use the value indicated by the IE "Sample Size" as the minimum sample size for the coding and decoding of the RTP packets, if the MS is not able to use the indicated value. If the circuit transport channel is for AMR or AMR-WB speech with RTP redundancy, the sample size is defined as the size of the new speech sample in each RTP packet, not including any redundant speech samples; +- configure the uplink RTP packets to be transmitted to the UDP port and IP address identified by the IE "RTP UDP Port" and the IE "GANC IP address", respectively; +- use the Payload Type included in the IE "Payload Type" for the PT field in the RTP header for the RTP packets; +- if received, use the configuration included in the IE "Multi-rate Configuration 2" for the circuit transport channel that is for AMR or AMR-WB speech; +- if received, use the configuration included in the IE "RTP Redundancy Configuration" for the circuit transport channel that is for AMR or AMR-WB speech. The redundancy policy is defined for each of the AMR modes specified in the IE "Multi-rate Configuration 2". The level of redundancy can span from no redundancy to double redundancy. In the same active codec set, a lower codec mode shall not be associated with a lower redundancy level than a higher codec mode. For example, the highest mode in the set is used with no redundancy, the next lower with single redundancy and rest of the modes with double redundancy. +- if received, pass the contents of the NAS Synchronisation Indicator to upper layers. + +The MS shall act on the received GA-RRC RELOCATION REQUEST message containing the IE "PTC Activation List" as follows: + +- for each PTC specified in the IE "PTC Activation List": +- store the RAB ID; +- allocate local PTC resources based on the values in the IE "RAB Configuration"; +- use the TEID value included in the IE "GANC TEID" for the TEID field in the GA-RRC PDU messages to be sent to the GANC; +- use the TEID value included in the IE "MS TEID" to verify the TEID field in the GA-RRC PDU messages to be received from the GANC; +- configure the uplink GA-RRC PDU messages to be transmitted to the UDP port and IP address identified by the IE "GANC UDP Port" and the IE "GANC IP address", respectively. + +On completing the above procedures, the MS shall: + +- transmit a GA-RRC RELOCATION REQUEST ACK message including the IE "CN Domains to Handover" with value the same as received in the GA-RRC RELOCATION REQUEST message. If the CS domain or both + +CS and PS domains is indicated, the message shall include the IE "CTC Activation Ack List". If the PS domain or both CS and PS domains is indicated, the message shall include the IE "PTC Activation Ack List". + +- For each CTC specified in the IE "CTC Activation Ack List" (if included): +- include the IE "RAB ID" for the CTC with the same value as received in the GA-RRC RELOCATION REQUEST message in the IE "RAB ID"; +- include the IE "GA-RRC Cause" indicating either success (i.e., value '0') or a failure cause value; +- for each CTC that is successfully configured (i.e., GA-RRC Cause value is '0'): +- include the allocated UDP port number in the IE "RTP UDP Port" for the downlink RTP packets to be sent from the GANC to the MS; +- include the selected RTP sample size, to be used for uplink and downlink RTP packets, in the IE "Sample Size"; +- include the Payload Type in the IE "Payload Type"; +- if the IE "RTCP UDP Port" was received in the GA-RRC RELOCATION REQUEST message and the MS is capable of supporting RTCP, activate the uplink RTCP stream and include the IE "RTCP UDP Port" for the downlink RTCP packets to be sent from the GANC to the MS. +- For each PTC specified in the IE "PTC Activation Ack List" (if included): +- include the IE "RAB ID" for the PTC with the same value as received in the GA-RRC RELOCATION REQUEST message in the IE "RAB ID"; +- include the IE "GA-RRC Cause" indicating either success (i.e., value '0') or a failure cause value; +- for each PTC that is successfully configured (i.e., GA-RRC Cause value is '0'): +- include the allocated UDP port number in the IE "MS UDP Port" for the downlink GA-RRC PDU messages to be sent from the GANC to the MS. + +After transmitting the GA-RRC RELOCATION REQUEST ACK message to the GANC, the GA-RRC sub-layer entity (if only one of CS and PS domains is subject to handover) or entities (if both CS and PS domains are subject to handover) in the MS transitions to the GA-RRC CONNECTED state. + +### 8a.10.2 Reception of GA-RRC RELOCATION REQUEST ACK by the GANC + +On reception of the GA-RRC RELOCATION REQUEST ACK message, the GANC shall do the following: + +- If the IE "CN Domains to Handover" indicates either the CS domain or both domains, the GANC shall configure itself for transmission of RTP packets to the "RTP UDP Port" indicated in the message and RTCP packets to the "RTCP UDP Port" indicated in the message (if included) for each successfully activated CTC. +- If the IE "CN Domains to Handover" indicates either the PS domain or both domains, the GANC shall configure itself for transmission of GA-RRC PDU messages to the "MS UDP Port" indicated in the message for each successfully activated PTC. +- The GANC then continues with the relocation preparation process with the CN. + +### 8a.10.3 Normal execution + +The normal execution phase of the handover to GAN Iu mode procedure is initiated when the source radio access technology (e.g. GERAN or UTRAN) orders the MS to handover (GERAN) or relocate (UTRAN) to GAN Iu mode. + +- The exception is when the GANC receives a Relocation Request message that does not include the IMSI parameter from a MSC. This exception case is described in sub-clause 8a.10.5. + +The execution procedure is applicable when the MS is in the GA-RC-REGISTERED state provided the conditions described in Annex C.2: "(Source-RAT) Measurement Report for Handover and Cell Change Order to GAN Iu mode" are met. + +The handover order in GERAN is sent via the INTER SYSTEM TO UTRAN HANDOVER COMMAND message which contains a HANDOVER TO UTRAN message. The handover order in UTRAN is sent via the PHYSICAL CHANNEL RECONFIGURATION message. If the UARFCN and PSC parameters included in either of the HANDOVER TO UTRAN message or the PHYSICAL CHANNEL RECONFIGURATION message (both are specified in [40]) match those of the GAN Iu mode cell, the MS shall: + +- send a GA-RRC RELOCATION COMPLETE message to the GANC; +- in the case of PS domain handover, start timer TU4001 for each of the successfully activated PTC(s); +- switch the serving RR to GAN Iu mode; i.e. attach the GA-RRC sub-layer entities to the RR-SAP. + +### 8a.10.4 Reception of GA-RRC RELOCATION COMPLETE by the GANC + +On reception of the GA-RRC RELOCATION COMPLETE message, the GANC shall indicate handover detection and completion to the CN. + +### 8a.10.5 Exception case: No IMSI in CS domain Relocation Request + +The following exception procedures are applicable if the handover is for the CS domain only and the GANC did not receive the IMSI parameter in the Relocation Request message from the MSC. The procedure is illustrated in Figure 8a.10.5. + +![Sequence diagram illustrating the handover to GAN Iu mode exception case. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RC-REGISTERED state. Upon receiving a handover command, it starts timer TU3920 and sends a '1. GA-RRC RELOCATION ACCESS' message to the GANC. The GANC responds with '2. CTC Activation' (dashed arrow). The MS then enters the GA-RRC-CONNECTED state, stops timer TU3920, and sends a '3. GA-RRC RELOCATION COMPLETE' message to the GANC.](dfaa8b98082261913dac00eae86b2889_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RC-REGISTERED + Note left of MS: Start TU3920 + MS->>GANC: 1. GA-RRC RELOCATION ACCESS + Note left of MS: GA-RRC-CONNECTED + GANC-->>MS: 2. CTC Activation + Note left of MS: Stop TU3920 + MS->>GANC: 3. GA-RRC RELOCATION COMPLETE + +``` + +Sequence diagram illustrating the handover to GAN Iu mode exception case. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RC-REGISTERED state. Upon receiving a handover command, it starts timer TU3920 and sends a '1. GA-RRC RELOCATION ACCESS' message to the GANC. The GANC responds with '2. CTC Activation' (dashed arrow). The MS then enters the GA-RRC-CONNECTED state, stops timer TU3920, and sends a '3. GA-RRC RELOCATION COMPLETE' message to the GANC. + +**Figure 8a.10.5: Handover to GAN Iu mode, exception case** + +In this case, the MS will not receive the GA-RRC RELOCATION REQUEST message from the GANC before receiving the handover order from the source radio access technology, as described in sub-clause 8a.10.3. + +If the UARFCN and PSC parameters included in either of the HANDOVER TO UTRAN message or the PHYSICAL CHANNEL RECONFIGURATION message match those of the GAN Iu mode cell, the GA-RRC CS domain sub-layer entity in the MS shall: + +- if the handover is not for a signalling channel only, the MS shall: + - send a GA-RRC RELOCATION ACCESS message to the network including the complete UTRAN RRC handover command message in the IE "UTRAN RRC Message" and enter the GA-RRC-CONNECTED state for the CS domain (Note: The MS shall extract the UTRAN RRC *Handover to UTRAN Command* message from the GERAN RRC Handover to UTRAN Command IE that is present in the GERAN RRC *Inter System to UTRAN Command* message); + - start timer TU3920; +- otherwise, the MS shall: + - immediately send a GA-RRC RELOCATION COMPLETE message to the GANC; + - enter the GA-RRC-CONNECTED state for the CS domain; + - switch the serving RR to GAN Iu mode; i.e. attach the GA-RRC sub-layer entities to the RR-SAP. + +On receipt of the GA-RRC RELOCATION ACCESS message, the GANC shall initiate CTC activation as specified in sub-clause 8a.4.1. + +On receipt of the GA-RRC ACTIVATE CHANNEL COMPLETE message, the MS shall: + +- stop timer TU3920; +- send a GA-RRC RELOCATION COMPLETE message to the GANC; +- switch to GAN Iu mode; i.e. attach the GA-RRC sub-layer entities to the RR-SAP. + +On reception of the GA-RRC RELOCATION COMPLETE message, the GANC shall indicate handover detection and completion to the CN. + +If the CTC activation procedure fails or the timer TU3920 expires before CTC activation is completed, the MS shall: + +- terminate the procedure including release of the associated GA-RRC resources; +- resume the connection in the source radio access technology used before the handover; +- indicate the failure to the source radio access technology. + +## 8a.11 Handover from GAN Iu mode + +The purpose of this procedure is to transfer, upon request from the MS (and under the control of the GANC), a connection between the MS and the GANC to another radio access technology (e.g. GERAN or UTRAN). + +The procedure is applicable when one or both of the GA-RRC sub-layer entities in the MS are in GA-RRC-CONNECTED state. + +![Sequence diagram for successful handover from GAN Iu mode](0fa5b60804100c3aead10404f9f226f9_img.jpg) + +Sequence diagram illustrating the successful handover from GAN Iu mode. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RRC-CONNECTED state and transitions to the GA-RC-REGISTERED state. The GANC sends three messages to the MS: 1. GA-RRC UPLINK QUALITY INDICATION (dashed line), 2. GA-RRC RELOCATION INFORMATION (solid line), and 3. GA-RRC RELOCATION COMMAND (solid line). + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 1. GA-RRC UPLINK QUALITY INDICATION + GANC->>MS: 2. GA-RRC RELOCATION INFORMATION + GANC->>MS: 3. GA-RRC RELOCATION COMMAND + Note left of MS: GA-RC-REGISTERED +``` + +Sequence diagram for successful handover from GAN Iu mode + +Figure 8a.11.1: Handover from GAN Iu mode, successful case + +![Sequence diagram for failed handover from GAN Iu mode](ae9b822eaafef535b7a0fbb97a7c713b_img.jpg) + +Sequence diagram illustrating the failed handover from GAN Iu mode. The diagram shows the interaction between the MS (Mobile Station) and the GANC (GAN Controller). The MS starts in the GA-RRC-CONNECTED state. The GANC sends four messages to the MS: 1. GA-RRC UPLINK QUALITY INDICATION (dashed line), 2. GA-RRC RELOCATION INFORMATION (solid line), 3. GA-RRC RELOCATION COMMAND (solid line), and 4. GA-RRC RELOCATION FAILURE (solid line). + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 1. GA-RRC UPLINK QUALITY INDICATION + GANC->>MS: 2. GA-RRC RELOCATION INFORMATION + GANC->>MS: 3. GA-RRC RELOCATION COMMAND + GANC->>MS: 4. GA-RRC RELOCATION FAILURE +``` + +Sequence diagram for failed handover from GAN Iu mode + +Figure 8a.11.2: Handover from GAN Iu mode, failure case + +### 8a.11.1 Initiation + +The procedure may be initiated by the MS based on: + +- local measurements of GAN coverage signal quality; +- reception of a GA-RRC UPLINK QUALITY INDICATION message indicating poor uplink quality in the *UL Quality Indication* IE; If the UL Quality Indication IE indicates "Network problem" a handover out to GERAN or UTRAN should be attempted. In case the UL Quality Indication information element shows "Radio problem" or "Undetermined problem" a search for a new access point should be done before the handover out is initiated; +- reception of RTCP packets indicating poor uplink quality (i.e., in the CS case); +- excessive loss or delay in the received RTP packets (i.e., in the CS case). + +When the MS decides to trigger the handover from GAN Iu mode, it shall: + +- send a GA-RRC RELOCATION INFORMATION message to the GANC including a list of candidate/ target cell identifiers ranked in order of preference which is the most recent list available from the other radio access technology (e.g. GSM RR) and including the received signal strength for each identified GERAN or UTRAN cell. The MS may include GERAN cells, UTRAN cells or both. + +### 8a.11.2 Reception of GA-RRC RELOCATION INFORMATION by the GANC + +The GANC should signal the need for handover to the CN. + +If the CN grants the handover request, the GANC should send a GA-RRC RELOCATION COMMAND message to the MS. + +The GA-RRC RELOCATION COMMAND message should only indicate a target cell which was reported by the MS in the GA-RRC RELOCATION INFORMATION message. + +### 8a.11.3 Reception of GA-RRC RELOCATION COMMAND by the MS + +The MS shall: + +- suspend all NAS layer signalling transmissions; +- start the connection establishment to the target radio access technology (e.g. GERAN or UTRAN) by using the contents of the IE "UTRAN RRC Message". This message carries information about the candidate/ target cell identifier and radio parameters relevant for the target radio access technology. + +A MS with simultaneously active PS and CS sessions in GAN Iu mode shall follow the procedure as outlined in [40] when it switches to the target cell. + +NOTE: The requirements concerning the establishment of the radio connection towards the target radio access technology (e.g. GERAN) and the signalling procedure are outside of the scope of this specification. + +### 8a.11.4 Successful completion of the handover from GAN Iu mode + +Upon successfully completing the handover from GAN Iu mode, the GANC should: + +- release all radio resources associated with the GAN connection. + +Upon successfully completing the handover from GAN Iu mode, the MS shall: + +- switch to the target radio access technology (e.g. GERAN or UTRAN) mode; i.e. detach the GA-RRC sub-layer entities from the RR-SAP; +- enter the GA-RC-REGISTERED state (but in GERAN/UTRAN mode). + +NOTE: The release of the GAN radio resources is initiated from the target RAT. The MS may deregister from the GANC (as defined in sub-clause 6.4) after successfully completing the handover. If the MS chooses to deregister from the GANC, it may do so either immediately after successfully completing the handover or after sending the GA-RRC RELEASE COMPLETE message to the GANC in response to the GA-RRC RELEASE message from the GANC. + +### 8a.11.5 MS fails to complete requested handover + +If the MS does not succeed in establishing a connection to the target radio access technology, the MS shall: + +- revert back to the GAN Iu mode configuration; +- return a GA-RRC RELOCATION FAILURE message to the GANC and resume normal operation as if the GA-RRC RELOCATION COMMAND message has not been received. The GA-RRC Cause value shall be set to value 'Relocation Failure In Target CN/RNC Or Target System' as specified in [52]. + +### 8a.11.6 Reception of GA-RRC RELOCATION FAILURE by the GANC + +The GANC may initiate the release of resources in the target radio access technology. + +### 8a.11.7 Abnormal Cases + +If the GA-RRC RELOCATION COMMAND message instructs the MS: + +- to perform a non-supported scenario, or +- to use a non-supported configuration, + +the MS shall return a GA-RRC RELOCATION FAILURE message with GA-RRC Cause value set to 'Unspecified failure' or other appropriate cause as defined in [52] and resume normal operation as if the GA-RRC RELOCATION COMMAND message has not been received. + +# --- 9 Error handling procedures + +## 9.1 General + +The procedures specified in this specification apply to those messages which pass the checks described in this sub-clause. + +This sub-clause also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. + +Sub-clauses 9.2 to 9.4 shall be applied in order of precedence. + +In this sub-clause the following terminology is used: + +- An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as "reserved" in sub-clause 11, or if its value part violates rules of clause 11. However it is not a syntactical error that an IE specifies in its length indicator a greater length than defined in clause 11. +- A message is defined to have semantically incorrect contents if it contains information which, possibly dependent on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part of this specification. + +The procedures below apply to GA-RC/GA-CSR, GA-PSR, and GA-RRC messages, unless explicitly specified otherwise. The MS shall use the GA-CSR STATUS message to indicate problems with the GA-RC and GA-CSR protocols, the GA-PSR STATUS message to indicate problems with the GA-PSR protocol, and the GA-RRC STATUS message to indicate problems with the GA-RRC protocol. + +## 9.2 Message too short + +When a message is received that is too short to contain a complete message header and all the mandatory information elements, that message shall be ignored. + +## 9.3 Invalid Message Header + +If the MS receives a message over UDP with message type not defined or not implemented, it shall ignore the message. + +If the MS receives a message over TCP with protocol discriminator not defined or not implemented, it shall ignore the message. + +If the MS receives a message with Skip Indicator IE not encoded as 0000 or Length IE greater than 2048, it shall ignore the message. + +If the MS receives a message over TCP with message type not defined for the specific PD (GA-RC/GA-CSR, GA-PSR or GA-RRC) or not implemented, it shall return a GA-CSR STATUS, GA-PSR STATUS or GA-RRC STATUS message, respectively, with cause "message type non-existent or not implemented". + +If the MS receives a message not compatible with the protocol state, the MS shall ignore the message and shall return a (GA-CSR, GA-PSR or GA-RRC) STATUS message with cause "Message type not compatible with protocol state". + +## 9.4 Invalid Information Elements + +If the MS receives a GA-RC/GA-CSR, GA-PSR or GA-RRC message with a missing or syntactically incorrect mandatory IE, the MS shall ignore the message and shall return a (GA-CSR, GA-PSR or GA-RRC) STATUS message with cause "Invalid mandatory information". In addition, if the message was a GA-CSR RELEASE message or GA-RRC RELEASE message, the actions taken shall be the same as specified in sub-clause 7.5 or sub-clause 8a.5, respectively. + +The MS shall ignore all unknown IEs in received messages. + +The MS shall treat all optional IEs that are syntactically incorrect in a message as not present in the message. + +If the MS diagnoses a missing or unexpected conditional IE or when it receives at least one syntactically incorrect conditional IE, it shall ignore the message and shall return a (GA-CSR, GA-PSR or GA-RRC) STATUS message with cause value "conditional IE error". + +If the MS receives a message with semantically incorrect contents, it shall ignore the message and shall return a (GA-CSR, GA-PSR or GA-RRC) STATUS message with cause value "semantically incorrect message". + +## 9.5 Handling of lower layer faults + +The handling of lower layer failures in the MS while in the GA-RC-DEREGISTERED state is described in sub-clauses 5.6.2 and 6.2.4.2. + +The handling of lower layer failures in the MS while not in the GA-RC-DEREGISTERED state is described below: + +For all lower layer failures in the MS (for example related to DNS, IPsec or TCP failures other than RST), the MS shall: + +- release the TCP connection towards the current GANC, if established, +- stop timer TU3906, +- release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5, +- start timer TU3905, and +- enter GA-RC-DEREGISTERED state. + +## 9.6 Out of sequence IEs + +The MS shall ignore all out of sequence IEs in a message. The network should take the same approach. + +# 10 Message functional definitions and contents + +## 10.1 GA-RC and GA-CSR Messages + +Table 10.1.1 summarizes the GA-RC and GA-CSR messages. + +**Table 10.1.1: GA-RC and GA-CSR Messages** + +| | | +|--------------------------------------------------|------------------| +| Discovery messages: | Reference | +| GA-RC DISCOVERY REQUEST | 10.1.2 | +| GA-RC DISCOVERY ACCEPT | 10.1.3 | +| GA-RC DISCOVERY REJECT | 10.1.4 | +| Registration messages: | Reference | +| GA-RC REGISTER REQUEST | 10.1.5 | +| GA-RC REGISTER ACCEPT | 10.1.6 | +| GA-RC REGISTER REDIRECT | 10.1.7 | +| GA-RC REGISTER REJECT | 10.1.8 | +| GA-RC DEREGISTER | 10.1.9 | +| GA-RC REGISTER UPDATE UPLINK | 10.1.10 | +| GA-RC REGISTER UPDATE DOWNLINK | 10.1.11 | +| GA-CSR connection establishment messages: | Reference | +| GA-CSR REQUEST | 10.1.12 | +| GA-CSR REQUEST ACCEPT | 10.1.13 | +| GA-CSR REQUEST REJECT | 10.1.24 | +| Ciphering messages: | Reference | +| GA-CSR CIPHERING MODE COMMAND | 10.1.35 | +| GA-CSR CIPHERING MODE COMPLETE | 10.1.36 | +| Traffic Channel establishment messages: | Reference | +| GA-CSR ACTIVATE CHANNEL | 10.1.15 | +| GA-CSR ACTIVATE CHANNEL ACK | 10.1.16 | +| GA-CSR ACTIVATE CHANNEL COMPLETE | 10.1.18 | +| GA-CSR ACTIVATE CHANNEL FAILURE | 10.1.17 | +| GA-CSR CHANNEL MODE MODIFY | 10.1.40 | +| GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE | 10.1.41 | +| Channel release messages: | Reference | +| GA-CSR RELEASE | 10.1.19 | +| GA-CSR RELEASE COMPLETE | 10.1.20 | +| GA-CSR CLEAR REQUEST | 10.1.37 | +| Handover messages: | Reference | +| GA-CSR HANDOVER ACCESS | 10.1.29 | +| GA-CSR HANDOVER COMPLETE | 10.1.30 | +| GA-CSR UPLINK QUALITY INDICATION | 10.1.31 | +| GA-CSR HANDOVER INFORMATION | 10.1.32 | +| GA-CSR HANDOVER COMMAND | 10.1.33 | +| GA-CSR HANDOVER FAILURE | 10.1.34 | +| Paging messages: | Reference | +| GA-CSR PAGING REQUEST | 10.1.21 | +| GA-CSR PAGING RESPONSE | 10.1.22 | +| Miscellaneous message: | Reference | +| GA-CSR UPLINK DIRECT TRANSFER | 10.1.23 | +| GA-CSR DOWNLINK DIRECT TRANSFER | 10.1.25 | +| GA-CSR CLASSMARK ENQUIRY | 10.1.26 | +| GA-CSR CLASSMARK CHANGE | 10.1.27 | +| GA-CSR STATUS | 10.1.28 | +| GA-RC KEEP ALIVE | 10.1.14 | +| GA-CSR GPRS SUSPENSION REQUEST | 10.1.38 | +| GA-RC SYNCHRONIZATION INFORMATION | 10.1.39 | +| GA-RC CELL BROADCAST INFO | 10.1.14a | +| GA-CSR UTRAN CLASSMARK CHANGE | 10.1.42 | + +### 10.1.1 (void) + +### 10.1.2 GA-RC DISCOVERY REQUEST + +The MS transmits this message to the Provisioning GANC in order to obtain the address information of a Default GANC. + +Direction: MS to GANC + +**Table 10.1.2.1: GA-RC DISCOVERY REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------|---------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC DISCOVERY REQUEST Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| 1 | IMSI | Mobile Identity
11.2.1 | M | TLV | 10 | | | +| 2 | GAN Release Indicator | GAN Release Indicator
11.2.2 | M | TLV | 3 | | | +| 7 | GAN Classmark | GAN Classmark
11.2.7 | M | TLV | 4 | | | +| 3 | AP Radio Identity | Radio Identity
11.2.3 | C | TLV | 9 | | | +| 6 | GERAN/UTRAN coverage Indication | GERAN/UTRAN coverage Indicator
11.2.6 | M | TLV | 3 | | | +| 4 | GERAN Cell Identity | GERAN Cell Identity
11.2.4 | C | TLV | 4 | | | +| 5 | Location Area Identification | Location Area Identification
11.2.5 | C | TLV | n | | | +| 41 | Routing Area Code | Routing Area Code
11.2.41 | C | TLV | n | | | +| 21 | Register Reject Cause | Register reject Cause
11.2.21 | C | TLV | 3 | | | +| 11 | Redirection Counter | Redirection Counter
11.2.11 | C | TLV | 3 | | | +| 9 | Default GANC-SEGW IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 10 | Default GANC-SEGW FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 97 | Default GANC IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 98 | Default GANC FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 73 | 3G Cell Identity | 3G Cell Identity
11.2.73 | C | TLV | 6 | | | +| 130 | Tracking Area Identity | Tracking Area Identity
11.2.114 | O | TLV | 8 | | | +| 132 | E-UTRAN Camping Indicator | E-UTRAN Camping Indicator
11.2.116 | O | TLV | 4 | | | +| 131 | E-UTRAN Cell Identity | E-UTRAN Cell Identity
11.2.115 | C | TLV | 7 | | | + +#### 10.1.2.1 AP Radio Identity + +The AP Radio identity shall be included if the MS connects via an AP over the unlicensed radio. + +#### 10.1.2.2 GERAN Cell Identity + +The GERAN Cell Identity shall be included, if the MS is in an area with GSM Coverage. The GERAN Cell Identity is retrieved from the GSM System information. If the GERAN Cell Identity information element is included, it is not permitted to include the 3G Cell Identity information element or the E-UTRAN Cell Identity information element. + +#### 10.1.2.3 Location Area Identification + +The most recent Location Area Identification shall be included, if available in the MS. Following cases are identified: + +- Normal service or limited service over GERAN/UTRAN. +In this case the LAI received in the GERAN or UTRAN System Information is included. +- Normal service or limited service over E-UTRAN. +In this case the LAI is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage. +In this case the LAI is taken from the SIM, if available. + +#### 10.1.2.4 Routing Area Code + +The Routing Area Code (RAC) shall be included, if available in the MS. Following cases are identified: + +- Normal service over GERAN/UTRAN with GPRS support +In this case the RAC received in the GERAN or UTRAN System Information is included. +- Normal service or limited service over E-UTRAN. +In this case the RAC is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage +In this case the RAC is taken from the SIM, if available. +- Normal service over GERAN/UTRAN without GPRS support or limited service +The RAC is not included. + +#### 10.1.2.5 Register Reject Cause + +The Register Reject Cause shall be included if + +The MS reattempts GA-RC Discovery Request after failing to connect to the default GANC. + +#### 10.1.2.6 Redirection Counter + +The Redirection Counter IE shall be included if Register Reject Cause IE is included. + +#### 10.1.2.7 Default GANC-SEGW IP address + +The conditional IE Default GANC-SEGW IP address shall be included if the conditional IE Default GANC-SEGW FQDN is not included. It is not permitted to include both Default GANC-SEGW IP address and Default GANC-SEGW FQDN in the same message. One of these IEs shall be included if Register Reject Cause IE is included. + +#### 10.1.2.8 Default GANC-SEGW FQDN + +The conditional IE Default GANC-SEGW FQDN shall be included if the conditional IE Default GANC-SEGW IP address is not included. It is not permitted to include both Default GANC-SEGW IP address and Default GANC-SEGW FQDN in the same message. One of these IEs shall be included if Register Reject Cause IE is included. + +#### 10.1.2.9 Default GANC IP address + +The conditional IE Default GANC IP address shall be included if the conditional IE Default GANC FQDN is not included. It is not permitted to include both Default GANC IP address and Default GANC FQDN in the same message. One of these IEs shall be included if Register Reject Cause IE is included. + +#### 10.1.2.10 Default GANC FQDN + +The conditional IE Default GANC FQDN shall be included if the conditional IE Default GANC IP address is not included. It is not permitted to include both Default GANC IP address and Default GANC FQDN in the same message. One of these IEs shall be included if Register Reject Cause IE is included. + +#### 10.1.2.11 3G Cell Identity + +The 3G Cell Identity shall be included, if the MS is in an area with UTRAN Coverage. The 3G Cell Identity is retrieved from the UTRAN System information. If the 3G Cell Identity information element is included, it is not permitted to include the GERAN Cell Identity information element. + +#### 10.1.2.12 Tracking Area Identity + +The most recent Tracking Area Identity shall be included, if the MS supports E-UTRAN and the TAI is available in the MS. Following cases are identified: + +- Normal service or limited service over E-UTRAN. +In this case the TAI received in the E-UTRAN System Information is included. +- Normal service or limited service over GERAN/UTRAN. +In this case the TAI is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage. +In this case the TAI is taken from the USIM, if available. + +#### 10.1.2.13 E-UTRAN Camping Indicator + +The E-UTRAN Camping Indicator IE shall be included if the MS is camped on a E-UTRAN cell. + +#### 10.1.2.14 E-UTRAN Cell Identity + +The E-UTRAN Cell Identity IE shall be included if the MS is camped on a E-UTRAN cell, as indicated by the E-UTRAN Camping Indicator. The MS obtains the E-UTRAN Cell Identity value from the E-UTRAN System information. If the E-UTRAN Cell Identity information element is included, it is not permitted to include the GERAN Cell Identity information element or the 3G Cell Identity information element. + +### 10.1.3 GA-RC DISCOVERY ACCEPT + +The Provisioning GANC sends information of the Default GANC and SEGW associated with the Default GANC the MS should use. + +Direction: GANC to MS + +**Table 10.1.3.1: GA-RC DISCOVERY ACCEPT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------|---------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC DISCOVERY ACCEPT Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| 9 | Default GANC-SEGW IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 10 | Default GANC-SEGW FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 97 | Default GANC IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 98 | Default GANC FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 103 | GANC TCP port number | Communication port
11.2.25 | O | TLV | 4 | | | + +#### 10.1.3.1 Default GANC-SEGW IP address + +The conditional IE Default GANC-SEGW IP address shall be included if the conditional IE Default GANC-SEGW FQDN is not included. It is not permitted to include both Default GANC-SEGW IP address and Default GANC-SEGW FQDN in the same message. + +#### 10.1.3.2 Default GANC-SEGW FQDN + +The conditional IE Default GANC-SEGW FQDN shall be included if the conditional IE Default GANC-SEGW IP address is not included. It is not permitted to include both Default GANC-SEGW IP address and Default GANC-SEGW FQDN in the same message. + +#### 10.1.3.3 Default GANC IP address + +The conditional IE Default GANC IP address shall be included if the conditional IE Default GANC FQDN is not included. It is not permitted to include both Default GANC IP address and Default GANC FQDN in the same message. + +#### 10.1.3.4 Default GANC FQDN + +The conditional IE Default GANC FQDN shall be included if the conditional IE Default GANC IP address is not included. It is not permitted to include both Default GANC IP address and Default GANC FQDN in the same message. + +### 10.1.4 GA-RC DISCOVERY REJECT + +The Provisioning GANC rejects the Discovery Request from the MS. + +Direction: GANC to MS + +**Table 10.1.4.1: GA-RC DISCOVERY REJECT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC DISCOVERY REJECT Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| 12 | Discovery Reject Cause | Discovery Reject Cause
11.2.12 | M | TLV | 3 | | | +| 24 | TU3902 Timer | TU3902 Timer
11.2.24 | C | TLV | 4 | | | + +#### 10.1.4.1 TU3902 Timer + +The TU3902 Timer IE shall be included if the Discovery Reject Cause 'Network Congestion' is returned to the MS. + +### 10.1.5 GA-RC REGISTER REQUEST + +The MS registers with the GANC in order to establish a MS context in the GANC and receive the needed GAN system information. The MS also uses this message to request a list of PLMN identities, when the MS is in manual PLMN selection mode. + +Direction: MS to GANC + +**Table 10.1.5.1: GA-RC REGISTER REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------|---------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC REGISTER REQUEST message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 1 | IMSI | Mobile Identity
11.2.1 | M | TLV | 10 | | | +| 2 | GAN Release Indicator | GAN Release Indicator
11.2.2 | M | TLV | 3 | | | +| 7 | GAN Classmark | GAN Classmark
11.2.7 | M | TLV | 4 | | | +| 3 | AP Radio Identity | Radio Identity
11.2.3 | C | TLV | 9-n | | | +| 96 | MS Radio identity | Radio Identity
11.2.3 | M | TLV | 9-n | | | +| 17 | GSM RR/UTRAN RRC State | GSM RR/ UTRAN RRC State
11.2.17 | M | TLV | 3 | | | +| 6 | Coverage Indication | GERAN/UTRAN coverage Indicator
11.2.6 | M | TLV | 3 | | | +| 4 | GERAN Cell Identity | GERAN Cell Identity
11.2.4 | C | TLV | 4 | | | +| 5 | Location Area Identification | Location Area Identification
11.2.5 | C | TLV | 7 | | | +| 41 | Routing Area Code | Routing Area Code
11.2.41 | C | TLV | 3 | | | +| 8 | Geographic Location | Geographical Location
11.2.8 | O | TLV | 9-n | | | +| 42 | AP location | AP Location
11.2.42 | O | TLV | 7-n | | | +| 21 | Register Reject Cause | Register reject Cause
11.2.21 | C | TLV | 3 | | | +| 11 | Redirection Counter | Redirection Counter
11.2.11 | C | TLV | 3 | | | +| 9 | Last GANC-SEGW IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 10 | Last GANC-SEGW FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 97 | Last GANC IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 98 | Last GANC FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 61 | AP Service Name | AP Service Name
11.2.61 | C | TLV | 4-260 | | | +| 68 | Registration indicators | Registration Indicators
11.2.68 | C | TLV | 3 | | | +| 69 | GAN PLMN List | GAN PLMN List
11.2.69 | C | TLV | n | | | +| 71 | Required GAN Services | Required GAN Services
11.2.71 | O | TLV | 3 | | | +| 73 | 3G Cell Identity | 3G Cell Identity
11.2.73 | C | TLV | 6 | | | +| 82 | 3G UARFCN | 3G UARFCN
11.2.82 | O | TLV | 4 | | | + +| | | | | | | | | +|-----|---------------------------|---------------------------------------|---|-----|---|--|--| +| 74 | 3G Security Capability | 3G Security Capability
11.2.111 | C | TLV | 6 | | | +| 130 | Tracking Area Identity | Tracking Area Identity
11.2.114 | O | TLV | 8 | | | +| 132 | E-UTRAN Camping Indicator | E-UTRAN Camping Indicator
11.2.116 | O | TLV | 4 | | | +| 131 | E-UTRAN Cell Identity | E-UTRAN Cell Identity
11.2.115 | C | TLV | 7 | | | + +#### 10.1.5.1 GERAN Cell Identity + +The GERAN Cell Identity shall be included, if the MS is in an area with GSM Coverage. The GERAN Cell Identity is retrieved from the GSM System information. If the GERAN Cell Identity information element is included, it is not permitted to include the 3G Cell Identity information element or the E-UTRAN Cell Identity information element. + +#### 10.1.5.2 Location Area Identification + +The most recent Location Area Identification shall be included, if available in the MS. Following cases are identified: + +- Normal service or limited service over GERAN/UTRAN +In this case the LAI received in the GERAN/UTRAN System Information is included. +- Normal service or limited service over E-UTRAN. +In this case the LAI is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage +In this case the LAI is taken from the SIM, if available. + +#### 10.1.5.3 Routing Area Code + +The Routing Area Code (RAC) shall be included, if available in the MS. Following cases are identified: + +- Normal service over GERAN/UTRAN with GPRS support +In this case the RAC received in the GSM System Information is included. +- Normal service or limited service over E-UTRAN. +In this case the RAC is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage +In this case the RAC is taken from the SIM, if available. +- Normal service over GERAN/UTRAN without GPRS support or limited service +The RAC is not included. + +#### 10.1.5.4 Register Reject Cause + +The Register Reject Cause shall be included if the MS reattempts GA-RC Register Request after failing to connect to a Serving GANC. + +#### 10.1.5.5 Redirection Counter + +The Redirection Counter IE shall be included if Register Reject Cause IE is included. + +#### 10.1.5.6 Last GANC-SEGW IP address + +The conditional IE Last GANC-SEGW IP address shall be included if the conditional IE Last GANC-SEGW FQDN is not included. It is not permitted to include both Last GANC-SEGW IP address and Last GANC-SEGW FQDN in the same message. One of these IEs shall be included if Register Reject Cause is included. + +#### 10.1.5.7 Last GANC-SEGW FQDN + +The conditional IE Last GANC-SEGW FQDN shall be included if the conditional IE Last GANC-SEGW IP address is not included. It is not permitted to include both Last GANC-SEGW IP address and Last GANC-SEGW FQDN in the same message. One of these IEs shall be included if Register Reject Cause is included. + +#### 10.1.5.8 Last GANC IP address + +The conditional IE Last GANC IP address shall be included if the conditional IE Last GANC FQDN is not included. It is not permitted to include both Last GANC IP address and Last GANC FQDN in the same message. One of these IEs shall be included if Register Reject Cause is included. + +#### 10.1.5.9 Last GANC FQDN + +The conditional IE Last GANC FQDN shall be included if the conditional IE Last GANC IP address is not included. It is not permitted to include both Last GANC IP address and Last GANC FQDN in the same message. One of these IEs shall be included if Register Reject Cause is included. + +#### 10.1.5.10 AP Radio Identity + +The AP Radio identity shall be included if the MS connects via an AP over the unlicensed radio. + +#### 10.1.5.11 AP Service Name + +The AP Service Name shall be included, if available, and if the MS connects via an AP over the unlicensed radio. + +#### 10.1.5.12 Registration Indicators + +The MS shall include this information element when attempting to register to the Default GANC. The presence of this Information Element indicates to the GANC that it is the Default GANC for that MS. + +#### 10.1.5.13 GAN PLMN List + +The GAN PLMN List information element shall be included only when attempting to register with the Default GANC and if no more PLMNs can be selected from the GAN PLMN List received from the Default GANC. + +#### 10.1.5.14 3G Cell Identity + +The 3G Cell Identity IE shall be included if the MS is in an area with UTRAN Coverage. The 3G Cell Identity is retrieved from the UTRAN System information. If the 3G Cell Identity information element is included, it is not permitted to include the GERAN Cell Identity information element. + +#### 10.1.5.15 3G UARFCN + +The 3G UARFCN IE shall be included if the MS is currently camped on a UTRAN cell and the MS indicates support for GAN Iu mode in the GAN Classmark IE. + +#### 10.1.5.16 3G Security Capability + +The 3G Security Capability IE shall be included if the MS indicates support for GAN Iu mode in the GAN Classmark IE. + +#### 10.1.5.17 Tracking Area Identity + +The most recent Tracking Area Identity shall be included, if the MS supports E-UTRAN and the TAI is available in the MS. Following cases are identified: + +- Normal service or limited service over E-UTRAN. +In this case the TAI received in the E-UTRAN System Information is included. +- Normal service or limited service over GERAN/UTRAN. +In this case the TAI is not included. + +- MS has not found GERAN/UTRAN/E-UTRAN coverage. +In this case the TAI is taken from the USIM, if available. + +#### 10.1.5.18 E-UTRAN Camping Indicator + +The E-UTRAN Camping Indicator IE shall be included if the MS is camped on a E-UTRAN cell. + +#### 10.1.5.19 E-UTRAN Cell Identity + +The E-UTRAN Cell Identity IE shall be included if the MS is camped on a E-UTRAN cell, as indicated by the E-UTRAN Camping Indicator. The MS obtains the E-UTRAN Cell Identity value from the E-UTRAN System information. If the E-UTRAN Cell Identity information element is included, it is not permitted to include the GERAN Cell Identity information element or the 3G Cell Identity information element. + +### 10.1.6 GA-RC REGISTER ACCEPT + +The GANC provides system information to the MS using this message. The contents of this message are a collection of IEs from system information 3 and 13 of GERAN specifications plus some additions. + +Direction: GANC to MS + +**Table 10.1.6.1: GA-RC REGISTER ACCEPT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|--------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC REGISTER ACCEPT message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 4 | Cell Identity | Cell Identity
11.2.4 | M | TLV | 4 | | | +| 5 | Location Area Identification | Location Area Identification
11.2.5 | M | TLV | 7 | | | +| 14 | GAN Control Channel Description | GAN Control Channel Description
11.2.14 | M | TLV | 8 | | | +| 23 | TU3910 Timer | TU3910 Timer
11.2.23 | M | TLV | 4 | | | +| 22 | TU3906 Timer | TU3906 Timer
11.2.22 | M | TLV | 4 | | | +| 19 | GAN Band | GAN Band
11.2.19 | M | TLV | 3 | | | +| 37 | TU3920 Timer | TU3920 Timer
11.2.37 | M | TLV | 4 | | | +| 13 | GAN Cell Description | GAN Cell Description
11.2.13 | O | TLV | 4 | | | +| 43 | TU4001 Timer | TU4001 Timer
11.2.43 | C | TLV | 4 | | | +| 60 | TU4003 Timer | TU4003 Timer
11.2.60 | C | TLV | 4 | | | +| 44 | Location Status | Location Status
11.2.44 | O | TLV | 3 | | | +| 62 | GAN Service Zone Information | GAN Service Zone Information
11.2.62 | O | TLV | 5-133 | | | +| 67 | Serving GANC table indicator | Serving GANC table indicator
11.2.67 | O | TLV | 3 | | | +| 112 | TU4004 Timer | TU4004 Timer
11.2.78 | C | TLV | 3 | | | +| 79 | GAN Mode Indicator | GAN Mode Indicator
11.2.79 | O | TLV | 3 | | | +| 81 | GAN Iu Mode Cell Description | GAN Iu Mode Cell Description
11.2.81 | O | TLV | 6 | | | +| 129 | Handover Reporting Control | Handover Reporting Control
11.2.113 | O | TLV | 4 | | | + +#### 10.1.6.1 TU4001 and TU4003 + +These information elements are included in the message, if GPRS is supported by the GANC. + +#### 10.1.6.2 GAN Service Zone Information + +This information element is included by the HPLMN, if the network is configured with GAN Service Zone information. + +#### 10.1.6.3 Serving GANC Table Indicator + +The optional IE Serving GANC Table Indicator shall be included when the GA-RC REGISTRATION ACCEPT is sent from the Default GANC. + +NOTE: the GANC knows from the presence of IE Registration Indicators in GA-RC REGISTER REQUEST, whether it is the Default GANC. + +#### 10.1.6.4 GAN Band + +This information element is applicable if and only if the MS is directed to operate in GAN A/Gb mode; otherwise, the contents of this IE shall be disregarded. + +#### 10.1.6.5 TU4004 Timer + +This information element shall be included if the IE "GANC Control Channel Description" indicates that the GANC supports PS handover. + +#### 10.1.6.6 GAN Mode Indicator + +This information element shall be included if the IE "GAN Classmark" received by the GANC in the GA-RC REGISTER REQUEST message included the GAN Mode Support Indicator field with value other than 'Unspecified'. + +#### 10.1.6.7 GAN Cell Description + +This information element may be included if the IE "GAN Mode Indicator" is included and has value 'The MS shall operate in GAN A/Gb mode' or if the IE "GAN Mode Indicator" is not included. + +#### 10.1.6.8 GAN Iu Mode Cell Description + +This information element may be included if the IE "GAN Mode Indicator" is included and has value 'The MS shall operate in GAN Iu mode'. + +### 10.1.7 GA-RC REGISTER REDIRECT + +The GANC may use this message to redirect the MS to another GANC. In this case the message will contain the Serving GANC-SEGW and Serving GANC information. The message may also contain information about one or more PLMN identities where the MS may be served while in GAN coverage. + +Direction: GANC to MS + +**Table 10.1.7.1: GA-RC REGISTER REDIRECT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------|---------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC REGISTER REDIRECT Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| 9 | Serving GANC-SEGW IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 10 | Serving GANC-SEGW FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 97 | Serving GANC IP address | IP Address
11.2.9 | C | TLV | 7-19 | | | +| 98 | Serving GANC FQDN | Fully Qualified Domain/Host Name
11.2.10 | C | TLV | 5-258 | | | +| 103 | Serving GANC TCP port number | Communication port
11.2.25 | O | TLV | 4 | | | +| 67 | Serving GANC table indicator | Serving GANC table indicator
11.2.67 | O | TLV | 3 | | | +| 69 | GAN PLMN List | GAN PLMN List
11.2.69 | C | TLV | n | | | + +#### 10.1.7.1 Serving GANC-SEGW IP address + +The conditional IE Serving GANC-SEGW IP address shall be included if neither the IE Serving GANC-SEGW FQDN nor the IE GAN PLMN List is included. + +#### 10.1.7.2 Serving GANC-SEGW FQDN + +The conditional IE Serving GANC-SEGW FQDN shall be included if neither the IE Serving GANC-SEGW IP address nor the IE GAN PLMN List is included. + +#### 10.1.7.3 Serving GANC IP address + +The conditional IE Serving GANC IP address shall be included if neither the IE Serving GANC FQDN nor the IE GAN PLMN List is included. + +#### 10.1.7.4 Serving GANC FQDN + +The conditional IE Serving GANC FQDN shall be included if neither the IE Serving GANC IP address nor the IE GAN PLMN List is included. + +#### 10.1.7.5 Serving GANC TCP port number + +The optional IE Serving GANC TCP port number is included if the network is configured to use another than the default TCP port (as defined in sub-clause 12.1.2) for registrations. If this information element is included, then it is not permitted to include the GAN PLMN List information element. + +#### 10.1.7.5a Serving GANC Table Indicator + +The optional IE Serving GANC Table Indicator shall be included when the GA-RC REGISTRATION REDIRECT is sent from the Default GANC. + +NOTE: The GANC knows from the presence of IE Registration Indicators in GA-RC REGISTER REQUEST, whether it is the Default GANC. + +#### 10.1.7.6 GAN PLMN List + +The conditional IE GAN PLMN List contains information about 1 or more PLMNs that may provide GAN service to the MS in its current location. If this information element is included, then it is not permitted to include any of the following information elements: Serving GANC-SEGW IP address, Serving GANC-SEGW FQDN, Serving GANC IP address, Serving GANC FQDN and Serving GANC TCP port number. + +### 10.1.8 GA-RC REGISTER REJECT + +The GAN uses this message to reject the registration request from a MS. + +Direction: GANC to MS + +**Table 10.1.8.1: GA-RC REGISTER REJECT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------|------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC REGISTER REJECT Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| 21 | Register Reject Cause | Register Reject Cause
11.2.21 | M | TLV | 3 | | | +| 16 | TU3907 Timer | TU3907 Timer
11.2.16 | C | TLV | 4 | | | +| 58 | Location Black List indicator | Location Black List indicator
11.2.58 | C | TLV | 3 | | | +| 5 | Location Area Identification | Location Area Identification
11.2.5 | C | TLV | 7 | | | + +#### 10.1.8.1 TU3907 Timer + +The TU3907 Timer IE shall be included if the Register Reject Cause 'Network Congestion' is returned to the MS. + +#### 10.1.8.2 Location Black List indicator + +The Location Black List indicator IE shall be included if the Register Reject Cause 'Location not allowed' is returned to the MS. + +#### 10.1.8.3 Location Area Identification + +The Location Area Identification IE shall be included if the Register Reject Cause 'Location not allowed' is returned to the MS. + +### 10.1.9 GA-RC DEREGISTER + +The GANC on receiving this message removes all contexts associated with the MS in the GANC. The MS on receiving this message releases all GA-RC, GA-CSR and GA-PSR resources. + +Direction: MS to GANC, GANC to MS + +**Table 10.1.9.1: GA-RC DEREGISTER message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------|------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC DEREGISTER Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| 21 | Deregister Cause | Register Reject Cause
11.2.21 | M | TLV | 3 | | | +| 58 | Location Black List indicator | Location Black List indicator
11.2.58 | C | TLV | 3 | | | +| 5 | Location Area Identification | Location Area Identification
11.2.5 | C | TLV | 7 | | | +| 16 | TU3907 Timer | TU3907 Timer
11.2.16 | C | TLV | 4 | | | + +#### 10.1.9.1 Location Black List indicator + +The Location Black List indicator IE shall be included if the Register Reject Cause 'Location not allowed' is returned to the MS. + +#### 10.1.9.2 Location Area Identification + +The Location Area Identification IE shall be included if the Register Reject Cause 'Location not allowed' is returned to the MS. + +#### 10.1.9.3 TU3907 Timer + +The TU3907 Timer IE shall be included if the Register Reject Cause 'Network Congestion' is returned to the MS. + +### 10.1.10 GA-RC REGISTER UPDATE UPLINK + +The MS shall send this message when it needs to update the GAN with the updated AP and GSM cell identities. + +Direction: MS to GAN + +**Table 10.1.10.1: GA-RC REGISTER UPDATE UPLINK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------------|------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC REGISTER UPDATE UPLINK message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 3 | AP Radio Identity | Radio Identity
11.2.3 | O | TLV | 9 | | | +| 6 | Coverage Indication | GERAN/UTRAN coverage Indicator
11.2.6 | O | TLV | 3 | | | +| 4 | GERAN Cell Identity | GERAN Cell Identity
11.2.4 | C | TLV | 4 | | | +| 5 | Location Area Identification | Location Area Identification
11.2.5 | C | TLV | 7 | | | +| 41 | Routing Area Code | Routing Area Code
11.2.41 | C | TLV | 3 | | | +| 8 | Geographic Location | Geographical Location
11.2.8 | O | TLV | 9-n | | | +| 42 | AP Location | AP Location
11.2.42 | O | TLV | 7-n | | | +| 71 | Required GAN Services | Required GAN Services
11.2.71 | O | TLV | 3 | | | +| 73 | 3G Cell Identity | 3G Cell Identity
11.2.73 | C | TLV | 6 | | | +| 61 | AP Service Name | AP Service Name
11.2.61 | C | TLV | 4-260 | | | +| 82 | 3G UARFCN | 3G UARFCN
11.2.82 | O | TLV | 4 | | | +| 130 | Tracking Area Identity | Tracking Area Identity
11.2.114 | O | TLV | 8 | | | +| 132 | E-UTRAN Camping Indicator | E-UTRAN Camping Indicator
11.2.116 | O | TLV | 4 | | | +| 131 | E-UTRAN Cell Identity | E-UTRAN Cell Identity
11.2.115 | C | TLV | 7 | | | + +#### 10.1.10.1 GERAN Cell Identity + +The GERAN Cell Identity shall be included, if GERAN/UTRAN Coverage Indication IE is included and the MS is in an area with GSM Coverage. The GERAN Cell Identity is retrieved from the GSM System information. If the GERAN Cell Identity information element is included, it is not permitted to include the 3G Cell Identity information element or the E-UTRAN Cell Identity information element. + +#### 10.1.10.2 Location Area Identification + +The most recent Location Area Identification shall be included, if available in the MS and if GERAN/UTRAN Coverage Indication IE is included. Following cases are identified: + +- Normal service or limited service over GERAN or UTRAN +In this case the LAI received in the GERAN/UTRAN System Information is included. +- Normal service or limited service over E-UTRAN. +In this case the LAI is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage +In this case the LAI is taken from the SIM, if available. + +#### 10.1.10.3 Routing Area Code + +The Routing Area Code (RAC) shall be included, if available in the MS and if "Coverage Indication" is included. Following cases are identified: + +- Normal service over GERAN/UTRAN with GPRS support +In this case the RAC received in the GERAN/UTRAN System Information is included. +- Normal service or limited service over E-UTRAN. +In this case the RAC is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage +In this case the RAC is taken from the SIM, if available. +- Normal service over GERAN/UTRAN without GPRS support or limited service +The RAC is not included. + +#### 10.1.10.4 3G Cell Identity + +The 3G Cell Identity shall be included, if GERAN/UTRAN Coverage Indication IE is included and the MS is in an area with UTRAN Coverage. The 3G Cell Identity is retrieved from the UTRAN System information. If the 3G Cell Identity information element is included, it is not permitted to include the GERAN Cell Identity information element or the E-UTRAN Cell Identity information element. + +#### 10.1.10.5 AP Service Name + +The AP Service Name information element shall be included, if available, and if the AP Radio Identity information element is included. + +#### 10.1.10.6 3G UARFCN + +The 3G UARFCN IE shall be included if the MS experiences any of the following while registered for GAN Iu mode: + +- The MS acquires UTRAN coverage for the first time after reporting no coverage during its last GAN registration. +- The MS establishes a new UTRAN serving cell as a result of Intra-RAT handover while in GERAN/UTRAN/E-UTRAN mode and the UARFCN of the new UTRAN serving cell is different from the UARFCN indicated during its last GAN Registration or GAN Registration Update. +- The MS establishes a new UTRAN serving cell as a result of Inter-RAT handover to UTRAN while in GERAN/UTRAN/E-UTRAN mode. +- The MS enters connected mode in a UTRAN cell while in GERAN/UTRAN/E-UTRAN mode and the UARFCN of the serving UTRAN cell is different from the UARFCN indicated during its last GAN Registration/GAN Registration Update or a UARFCN was not provided during its last GAN Registration/GAN Registration Update. + +#### 10.1.10.7 Tracking Area Identity + +The most recent Tracking Area Identity shall be included, if the MS supports E-UTRAN and the TAI is available in the MS. Following cases are identified: + +- Normal service or limited service over E-UTRAN. +In this case the TAI received in the E-UTRAN System Information is included. +- Normal service or limited service over GERAN/UTRAN. +In this case the TAI is not included. +- MS has not found GERAN/UTRAN/E-UTRAN coverage. +In this case the TAI is taken from the USIM, if available. + +#### 10.1.10.8 E-UTRAN Camping Indicator + +The E-UTRAN Camping Indicator IE shall be included if the MS is camped on a E-UTRAN cell. + +#### 10.1.10.9 E-UTRAN Cell Identity + +The E-UTRAN Cell Identity IE shall be included if the MS is camped on a E-UTRAN cell, as indicated by the E-UTRAN Camping Indicator. The MS obtains the E-UTRAN Cell Identity value from the E-UTRAN System information. If the E-UTRAN Cell Identity information element is included, it is not permitted to include the GERAN Cell Identity information element or the 3G Cell Identity information element. + +### 10.1.11 GA-RC REGISTER UPDATE DOWNLINK + +The network sends this message to the MS to indicate change in GAN system information or MS location status. + +Direction: GANC to MS + +**Table 10.1.11.1: GA-RC REGISTER UPDATE DOWNLINK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------|--------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC REGISTER UPDATE DOWNLINK message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 4 | Cell Identity | Cell Identity
11.2.4 | O | TLV | 4 | | | +| 5 | Location Area Identification | Location Area Identification
11.2.5 | O | TLV | 7 | | | +| 14 | GAN Control Channel Description | GAN Control Channel Description
11.2.14 | O | TLV | 8 | | | +| 23 | TU3910 Timer | TU3910 Timer
11.2.23 | O | TLV | 4 | | | +| 22 | TU3906 Timer | TU3906 Timer
11.2.22 | O | TLV | 4 | | | +| 19 | GAN Band | GAN Band
11.2.19 | O | TLV | 3 | | | +| 37 | TU3920 Timer | TU3920 Timer
11.2.37 | O | TLV | 4 | | | +| 13 | GAN Cell Description | GAN Cell Description
11.2.13 | O | TLV | 4 | | | +| 43 | TU4001 Timer | TU4001 Timer
11.2.43 | O | TLV | 4 | | | +| 60 | TU4003 Timer | TU4003 Timer
11.2.60 | O | TLV | 4 | | | +| 44 | Location Status | Location Status
11.2.44 | O | TLV | 3 | | | +| 62 | GAN Service Zone Information | GAN Service Zone Information
11.2.62 | O | TLV | 5-133 | | | +| 81 | GAN Iu Mode Cell Description | GAN Iu Mode Cell Description
11.2.81 | O | TLV | 6 | | | + +#### 10.1.11.1 GAN Service Zone Information + +This information element is included from the HPLMN, if the network is configured with UMA Service Zone information. + +#### 10.1.11.2 GAN Cell Description + +This information element may be included if and only if the MS is operating in GAN A/Gb mode. + +#### 10.1.11.3 GAN Iu Mode Cell Description + +This information element may be included if and only if the MS is operating in GAN Iu mode. + +### 10.1.12 GA-CSR REQUEST + +The MS sends this message to the network to establish the GA-CSR Connection. + +Direction: MS to GANC + +**Table 10.1.12.1: GA-CSR REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR REQUEST message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 50 | Establishment Cause | Establishment Cause
11.2.50 | M | TLV | 3 | | | + +### 10.1.13 GA-CSR REQUEST ACCEPT + +The GANC sends this message to the MS to indicate that it has accepted the establishment of the GA-CSR Connection. + +Direction: GANC to MS + +**Table 10.1.13.1: GA-CSR REQUEST ACCEPT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR REQUEST ACCEPT message identity | Message Type
11.1.1.4 | M | V | 1 | | | + +### 10.1.14 GA-RC KEEP ALIVE + +The MS sends this message to the GANC. + +Direction: MS to GANC + +**Table 10.1.14.1: GA-RC KEEP ALIVE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC KEEP ALIVE Message Type | Message Type
11.1.1.4 | M | V | 1 | | | + +### 10.1.14a GA-RC CELL BROADCAST INFO + +The GANC sends this message to the MS. + +Direction: GANC to MS + +**Table 10.1.14a.1: GA-RC CELL BROADCAST INFO message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC CELL BROADCAST INFO Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| 72 | Broadcast Container | Broadcast container
11.2.72 | M | TLV | n-m | | | + +### 10.1.15 GA-CSR ACTIVATE CHANNEL + +The GANC uses this message to establish a traffic channel on GAN. + +Direction: GANC to MS + +**Table 10.1.15.1: GA-CSR ACTIVATE CHANNEL message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------------------|----------|--------|--------|-------|------------------------------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR ACTIVATE CHANNEL message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 27 | Channel Mode | Channel Mode
11.2.27 | M | TLV | 3 | | | +| 53 | Sample Size | Sample Size
11.2.53 | M | TLV | 3 | | CS payload sample size in ms | +| 97 | IP Address | IP Address
11.2.9 | M | TLV | 7-19 | | | +| 104 | RTP UDP Port | Communication Port
11.2.25 | M | TLV | 4 | | | +| 54 | Payload Type | Payload Type
11.2.54 | O | TLV | 3 | | | +| 55 | Multi-rate Configuration | Multi-rate Configuration
11.2.55 | C | TLV | 3-n | | | +| 63 | RTP Redundancy Configuration | RTP Redundancy Configuration
11.2.63 | C | TLV | 3-6 | | | +| 105 | RTCP UDP Port | Communication Port
11.2.25 | O | TLV | 4 | | | +| 133 | Bandwidth-efficient Mode Indicator | Bandwidth-efficient Mode Indicator
11.2.117 | O | TLV | 4 | | | + +#### 10.1.15.1 Payload Type + +The Payload Type information Element is included when the speech codec signaled uses dynamic Payload Type. + +#### 10.1.15.2 Multi-rate Configuration + +The Multi-rate Configuration information element is included when the Channel Mode is speech with a speech version using AMR. + +#### 10.1.15.3 RTP Redundancy Configuration + +The RTP Redundancy Configuration information element is included when the Channel Mode is speech with a speech version using AMR, and the MS has indicated support for RTP Redundancy through the GAN Classmark IE. The redundancy level is defined for each of the AMR modes in the Multi-rate Configuration. The level of redundancy can span from no redundancy to double redundancy. + +#### 10.1.15.4 RTCP UDP Port + +The RTCP UDP port information element is used to indicate the UDP port for RTCP, if RTCP shall be used towards the network. + +#### 10.1.15.5 Bandwidth-efficient Mode Indicator + +The Bandwidth-efficient Mode Indicator information element is included if RFC 4867 [48] bandwidth-efficient mode shall be used to code and decode the CS payload samples on the traffic channel. + +### 10.1.16 GA-CSR ACTIVATE CHANNEL ACK + +The MS indicates the communication port information for the downlink stream to the Serving GANC. + +Direction: MS to GANC + +**Table 10.1.16.1: GA-CSR ACTIVATE CHANNEL ACK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------------|------------------------------------|----------|--------|--------|-------|------------------------------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR ACTIVATE CHANNEL ACK message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 104 | RTP UDP Port | Communication Port
11.2.25 | M | TLV | 4 | | | +| 53 | Sample Size | Sample Size
11.2.53 | M | TLV | 3 | | CS payload sample size in ms | +| 54 | Payload Type | Payload Type
11.2.54 | O | TLV | 3 | | | +| 105 | RTCP UDP Port | Communication Port
11.2.25 | O | TLV | 4 | | | + +#### 10.1.16.1 Payload Type + +The Payload Type IE is included when the speech codec signaled uses dynamic Payload Type. It shall be set to the same value as the Payload Type IE of the GA-CSR CHANNEL ACTIVATE message. + +#### 10.1.16.2 RTCP UDP Port + +The RTCP UDP port information element is used to indicate the UDP port for RTCP, if RTCP shall be used towards the mobile station. + +#### 10.1.16.3 Sample Size + +The MS shall indicate what sample size it is using and what the network shall use in the downlink. The MS shall follow the minimum sample size indication sent by the network in GA-CSR ACTIVATE CHANNEL. + +### 10.1.17 GA-CSR ACTIVATE CHANNEL FAILURE + +The MS indicates failure to establish the channel to the GANC. + +Direction: MS to GANC + +**Table 10.1.17.1: GA-CSR ACTIVATE CHANNEL FAILURE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR ACTIVATE CHANNEL FAILURE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 29 | RR cause | RR cause
11.2.29 | M | TLV | 3 | | | + +### 10.1.18 GA-CSR ACTIVATE CHANNEL COMPLETE + +The Serving GANC acknowledges completion of the traffic channel establishment. + +Direction: GANC to MS + +**Table 10.1.18.1: GA-CSR ACTIVATE CHANNEL COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR ACTIVATE CHANNEL COMPLETE message identity | Message Type
11.1.1.4 | M | V | 1 | | | + +### 10.1.19 GA-CSR RELEASE + +This message is used to instruct the MS to release all GA-CSR related resources associated with the connection to the Serving GANC. + +Direction: GANC to MS + +**Table 10.1.19.1: GA-CSR RELEASE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR RELEASE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 29 | RR cause | RR cause
11.2.29 | M | TLV | 3 | | | +| 31 | GPRS Resumption | GPRS Resumption
11.2.31 | O | TLV | 3 | | | + +### 10.1.20 GA-CSR RELEASE COMPLETE + +The MS acknowledges release of all GA-CSR related resources to the Serving GANC. + +Direction: MS to GANC + +**Table 10.1.20.1: GA-CSR RELEASE COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR RELEASE COMPLETE message identity | Message Type
11.1.1.4 | M | V | 1 | | | + +### 10.1.21 GA-CSR PAGING REQUEST + +Direction: GANC to MS + +**Table 10.1.21.1: GA-CSR PAGING REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR PAGING REQUEST message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 51 | Channel Needed | Channel Needed
11.2.51 | M | TLV | 3 | | | +| 1 | TMSI or IMSI | Mobile Identity
11.2.1 | M | TLV | 7-10 | | | + +### 10.1.22 GA-CSR PAGING RESPONSE + +The MS responds to the page using this message. + +Direction: MS to GANC + +**Table 10.1.22.1: GA-CSR PAGING RESPONSE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------|------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR PAGING RESPONSE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 48 | Ciphering Key Sequence Number | Ciphering Key Sequence Number
11.2.48 | M | TLV | 3 | | | +| 28 | Mobile Station Classmark 2 | Mobile Station Classmark 2
11.2.28 | M | TLV | 5 | | | +| 1 | Mobile Identity | Mobile Identity
11.2.1 | M | TLV | 7-10 | | | +| 50 | Establishment Cause | Establishment Cause
11.2.50 | M | TLV | 3 | | | + +### 10.1.23 GA-CSR UPLINK DIRECT TRANSFER + +The MS communicates with the CN by encapsulating CC/MM/SS/SMS messages in this container. + +Direction: MS to GANC + +**Table 10.1.23.1: GA-CSR UPLINK DIRECT TRANSFER message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------------|------------------------------------|----------|--------|-------------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR UPLINK DIRECT TRANSFER message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 26 | L3 message | L3 Message
11.2.26 | M | TLV | Var. Length | | | +| 49 | SAPI ID | SAPI ID
11.2.49 | M | TLV | 3 | | | + +### 10.1.24 GA-CSR REQUEST REJECT + +The GANC sends this message to the MS to indicate that it has rejected the establishment of the GA-CSR Connection. + +Direction: GANC to MS + +**Table 10.1.24.1: GA-CSR REQUEST REJECT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR REQUEST REJECT message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 29 | RR cause | RR cause
11.2.29 | M | TLV | 3 | | | + +### 10.1.25 GA-CSR DOWNLINK DIRECT TRANSFER + +The CN communicates with the MS by encapsulating CC/MM/SS/SMS messages in this container. + +Direction: GANC to MS + +**Table 10.1.25.1: GA-CSR DOWNLINK DIRECT TRANSFER message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------------|------------------------------------|----------|--------|-------------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR DOWNLINK DIRECT TRANSFER message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 26 | L3 message | L3 Message
11.2.26 | M | TLV | Var. Length | | | + +### 10.1.26 GA-CSR CLASSMARK ENQUIRY + +The CN obtains classmark information of the mobile through this enquiry message. + +Direction: GANC to MS + +**Table 10.1.26.1: GA-CSR CLASSMARK ENQUIRY message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR CLASSMARK ENQUIRY message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 65 | Classmark Enquiry Mask | Classmark Enquiry Mask
11.2.65 | O | TLV | 3 | | | + +### 10.1.27 GA-CSR CLASSMARK CHANGE + +The MS sends classmark information indicating its capabilities to the network using this message. + +Direction: MS to GANC + +**Table 10.1.27.1: GA-CSR CLASSMARK CHANGE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------|---------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR CLASSMARK CHANGE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 28 | Mobile Station Classmark 2 | Mobile Station Classmark 2
11.2.28 | M | TLV | 5 | | | +| 56 | Additional Mobile Station Classmark Information | Mobile Station Classmark 3
11.2.56 | C | TLV | 3-34 | | | + +#### 10.1.27.1 Additional Mobile Station Classmark Information + +This IE shall be included if and only if the CM3 bit in the *Mobile Station Classmark 2* IE is set to 1. + +### 10.1.28 GA-CSR STATUS + +The MS communicates to the GANC various error conditions. + +Direction: MS to GANC + +**Table 10.1.28.1: GA-CSR STATUS message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------|------------------------------------|----------|--------|---------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR STATUS message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 29 | RR Cause | RR Cause
11.2.29 | M | TLV | 3 | | | +| 52 | PDU in Error | PDU in Error
11.2.52 | M | TLV | 6 - 257 | | | + +### 10.1.29 GA-CSR HANDOVER ACCESS + +Direction: MS to GANC + +**Table 10.1.29.1: GA-CSR HANDOVER ACCESS message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------|------------------------------------|----------|--------|-------------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR HANDOVER ACCESS message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 26 | Handover To GAN Command | L3 Message
11.2.26 | M | TLV | Var. Length | | | + +#### 10.1.29.1 Handover To GAN Command + +This information element contains the entire (RR) HANDOVER COMMAND message received via the source radio access technology. + +### 10.1.30 GA-CSR HANDOVER COMPLETE + +Direction: MS to GANC + +**Table 10.1.30.1: GA-CSR HANDOVER COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR HANDOVER COMPLETE message identity | Message Type
11.1.1.4 | M | V | 1 | | | + +### 10.1.31 GA-CSR UPLINK QUALITY INDICATION + +The GANC indicates changes in the uplink quality, which may be used by the MS to trigger the handover from GAN procedure. + +Direction: GANC to MS + +**Table 10.1.31.1: GA-CSR UPLINK QUALITY INDICATION message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR UL QUALITY INDICATION message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 33 | UL Quality Indication | UL Quality Indication
11.2.33 | M | V | 3 | | | + +### 10.1.32 GA-CSR HANDOVER INFORMATION + +The MS triggers the handover from GAN procedure indicating the list of cell identifiers in the target radio access technology. + +Direction: MS to GANC + +**Table 10.1.32.1: GA-CSR HANDOVER INFORMATION message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------------|----------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR HANDOVER INFORMATION message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 15 | GERAN Cell Identifier List | Cell Identifier List
11.2.15 | O | TLV | n | | | +| 106 | GERAN Received Signal Level List | GERAN Received Signal Level List
11.2.70 | C | TLV | n | | | +| 66 | UTRAN Cell Identifier List | UTRAN Cell Identifier List
11.2.66 | O | TLV | n | | | +| 107 | UTRAN Received Signal Level List | UTRAN Received Signal Level List
11.2.70b | C | TLV | n | | | + +#### 10.1.32.1 GERAN Cell Identifier List + +The GERAN Cell Identifier List information element shall be included if Handover to a GERAN cell is requested by the mobile station. The cells are ranked in descending order of preference according to measured value. + +#### 10.1.32.2 GERAN Received Signal Level List + +The GERAN Received Signal Level List information element shall be included if the GERAN Cell Identifier List information element is included. It contains the Received signal quality for each cell included in the GERAN Cell Identifier List information element. The order of the measurements in the GERAN Received Signal Level List shall be the same as the order of the Cell identifiers included in the GERAN Cell Identifier List information element. + +#### 10.1.32.3 UTRAN Cell Identifier List + +The UTRAN Cell Identifier List information element shall be included if Handover to an UTRAN cell is requested by the mobile station. The cells are ranked in descending order according to measured Ec/No value. + +#### 10.1.32.4 UTRAN Received Signal Level List + +The UTRAN Received Signal Level List information element shall be included if the UTRAN Cell Identifier List information element is included. It contains the Received signal quality for each cell included in the UTRAN Cell Identifier List information element. The order of the measurements in the UTRAN Received Signal Level List shall be the same as the order of the Cell identifiers included in the UTRAN Cell Identifier List information element. + +NOTE: At least one of the cell identifier list IEs must be present. + +### 10.1.33 GA-CSR HANDOVER COMMAND + +The GANC orders the MS to handover from GAN. + +Direction: GANC to MS + +**Table 10.1.33.1: GA-CSR HANDOVER COMMAND message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|--------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR HANDOVER COMMAND message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 32 | Handover From GAN Command | Handover From GAN Command
11.2.32 | M | TLV | n | | | + +#### 10.1.33.1 Handover From GAN Command + +If the target radio access technology is GERAN, the value part of the Handover From GAN Command IE is coded as the HANDOVER COMMAND message specified in [12]. If the target RAT is UTRAN, the value part of the Handover From GAN Command IE is coded as the INTER SYSTEM TO UTRAN HANDOVER COMMAND message specified in [12]. + +### 10.1.34 GA-CSR HANDOVER FAILURE + +The MS indicates a failure to complete the requested handover from GAN. + +Direction: MS to GANC + +**Table 10.1.34.1: GA-CSR HANDOVER FAILURE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR HANDOVER FAILURE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 29 | RR Cause | RR Cause
11.2.29 | M | TLV | 3 | | | + +#### 10.1.34.1 RR Cause + +If the target radio access technology is GERAN/UTRAN, this information element is coded as the RR Cause IE in [12]. + +### 10.1.35 GA-CSR CIPHERING MODE COMMAND + +The network sends this message to the MS to indicate the ciphering configuration for future handover to GERAN. + +Direction: GANC to MS + +**Table 10.1.35.1: GA-CSR CIPHERING MODE COMMAND message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR CIPHERING MODE COMMAND message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 30 | Ciphering Mode Setting | Cipher Mode Setting
11.2.30 | M | TLV | 3 | | | +| 45 | Cipher Response | Cipher Response
11.2.45 | M | TLV | 3 | | | +| 46 | Random number | Ciphering Command RAND
11.2.46 | M | TLV | 18 | | | + +### 10.1.36 GA-CSR CIPHERING MODE COMPLETE + +The MS sends this message to the GANC to acknowledge the ciphering configuration as well as to authenticate that the MS holds the correct Kc. + +Direction: MS to GANC + +**Table 10.1.36.1: GA-CSR CIPHERING MODE COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR CIPHERING MODE COMPLETE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 47 | Message Authentication Code | Ciphering Command MAC
11.2.47 | M | TLV | 14 | | | +| 1 | Mobile Equipment Identity | Mobile Identity
11.2.1 | C | TLV | 11 | | | + +#### 10.1.36.1 Mobile Equipment Identity + +This information element is included according the value of the Mobile Equipment Identity Request of the GA-CSR CIPHERING MODE COMMAND. + +### 10.1.37 GA-CSR CLEAR REQUEST + +The MS sends this message to the network to indicate that the network should release the signalling connection and related resources. + +Direction: MS to GANC + +**Table 10.1.37.1: GA-CSR CLEAR REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR CLEAR REQUEST message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 29 | RR cause | RR cause
11.2.29 | M | TLV | 3 | | | + +### 10.1.38 GA-CSR GPRS SUSPENSION REQUEST + +This message is used by the MS to request the suspension of the GPRS downlink data transfer when transitioning to dedicated mode. + +Direction: MS to GANC. + +**Table 10.1.38.1: GA-CSR GPRS SUSPENSION REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------|----------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR GPRS SUSPENSION REQUEST message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 34 | TLLI | TLLI
11.2.34 | M | TLV | 6 | | | +| 36 | Suspension cause | Suspension Cause
11.2.36 | M | TLV | 3 | | | +| 18 | Routing Area Identification | Routing Area Identification
11.2.18 | M | TLV | 8 | | | + +### 10.1.39 GA-RC SYNCHRONIZATION INFORMATION + +This message is sent by the MS after successful re-establishment of the TCP connection as defined in sub-clause 9.5. + +Direction: MS to GANC. + +**Table 10.1.39.1: GA-RC SYNCHRONIZATION INFORMATION message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0000 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC SYNCHRONIZATION INFORMATION message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 1 | IMSI | Mobile Identity
11.2.1 | M | TLV | 10 | | | +| 20 | GAN State | GAN State
11.2.20 | M | TLV | 3 | | | + +### 10.1.40 GA-CSR CHANNEL MODE MODIFY + +This message is sent by the network to the mobile station to request the setting of the mode for the indicated channel(s). + +**Table 10.1.40.1: GA-CSR CHANNEL MODE MODIFY message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------------------|-----------------------------------------|----------|--------|--------|-------|------------------------------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR CHANNEL MODE MODIFY message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 27 | Channel Mode | Channel Mode
11.2.27 | O | TLV | 3 | | | +| 55 | Multi-rate Configuration | Multi-rate Configuration
11.2.55 | C | TLV | 3-n | | | +| 63 | RTP Redundancy Configuration | RTP Redundancy Configuration
11.2.63 | C | TLV | 3-6 | | | +| 53 | Sample Size | Sample Size
11.2.53 | O | TLV | 3 | | CS payload sample size in ms | +| 97 | IP Address | IP Address
11.2.9 | O | TLV | 7-19 | | | +| 104 | RTP UDP Port | Communication Port
11.2.25 | O | TLV | 4 | | | +| 105 | RTCP UDP Port | Communication Port
11.2.25 | O | TLV | 4 | | | + +#### 10.1.40.1 Channel Mode + +The Channel Mode IE shall be included if the GANC is changing the current Channel Mode. + +#### 10.1.40.2 Multi-rate Configuration + +The Multi-rate Configuration information element is included when the Channel Mode is speech with a speech version using AMR. + +#### 10.1.40.3 RTP Redundancy Configuration + +The Redundancy Configuration information element is included when the Channel Mode is speech with a speech version using AMR, and the MS has indicated support for RTP Redundancy through the GAN Classmark IE. The redundancy level is defined for each of the AMR modes in the Multi-rate Configuration. The level of redundancy can span from no redundancy to double redundancy. + +#### 10.1.40.4 Sample Size + +The Sample Size IE shall be included if the GANC is changing the current Sample Size. The MS should use the value indicated by the IE "Sample Size" as the minimum sampling size for the coding and decoding of the CS payload samples, if the MS is not able to use the indicated value. + +#### 10.1.40.5 IP Address + +The IP Address IE shall be included if the GANC is changing the local IP address used for an active user plane session. + +#### 10.1.40.6 RTP UDP Port + +The RTP UDP Port IE shall be included if the GANC is changing the local UDP Port used for RTP for an active user plane session. + +#### 10.1.40.7 RTCP UDP Port + +The RTCP UDP Port IE shall be included if the GANC is changing the local UDP Port used for RTCP for an active user plane session. + +### 10.1.41 GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE + +This message is sent by the mobile station to the network to indicate the successful or unsuccessful execution of a channel mode modify request + +**Table 10.1.41.1: GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------------------------------|------------------------------------|----------|--------|--------|-------|------------------------------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 27 | Channel Mode | Channel Mode
11.2.27 | M | TLV | 3 | | | +| 53 | Sample Size | Sample Size
11.2.53 | O | TLV | 3 | | CS payload sample size in ms | + +#### 10.1.41.1 Channel Mode + +The Channel Mode IE shall always be included by the MS. It contains the currently used Channel Mode. + +#### 10.1.41.2 Sample Size + +The Sample Size IE shall be included by the MS if it was included in the GA-CSR CHANNEL MODE MODIFY. It contains the currently used Sample Size. + +### 10.1.42 GA-CSR UTRAN CLASSMARK CHANGE + +The MS sends UTRAN Classmark information indicating its UTRAN capabilities to the network using this message. + +Direction: MS to GANC + +**Table 10.1.42.1: GA-CSR UTRAN CLASSMARK CHANGE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-CSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-CSR UTRAN CLASSMARK CHANGE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 64 | UTRAN Classmark | UTRAN Classmark
11.2.64 | M | TLV | n | | | + +## 10.2 GA-PSR Messages + +Table 10.2.1 summarizes the GA-PSR messages. + +**Table 10.2.1: GA-PSR Messages** + +| GA-PSR TC Management messages: | Reference | Transport Layer used | +|-----------------------------------|-----------|----------------------| +| GA-PSR-ACTIVATE-UTC-REQ | 10.2.1 | TCP | +| GA-PSR-ACTIVATE-UTC-ACK | 10.2.2 | TCP | +| GA-PSR-DEACTIVATE-UTC-REQ | 10.2.3 | TCP | +| GA-PSR-DEACTIVATE-UTC-ACK | 10.2.4 | TCP | +| GPRS Tunnelling messages: | Reference | | +| GA-PSR-DATA | 10.2.5 | TCP | +| GA-PSR-UNITDATA | 10.2.6 | UDP | +| GAN Specific Signalling messages: | Reference | | +| GA-PSR-PS-PAGE | 10.2.7 | TCP | +| GA-PSR-DFC-REQ | 10.2.9 | UDP | +| GA-PSR-UFC-REQ | 10.2.8 | UDP | +| GA-PSR-STATUS | 10.2.10 | TCP | +| GA-PSR HANDOVER COMPLETE | 10.2.11 | TCP | +| GA-PSR UPLINK QUALITY INDICATION | 10.2.12 | TCP | +| GA-PSR HANDOVER INFORMATION | 10.2.13 | TCP | +| GA-PSR HANDOVER COMMAND | 10.2.14 | TCP | +| GA-PSR HANDOVER CONTINUE | 10.2.15 | TCP | +| GA-PSR HANDOVER FAILURE | 10.2.16 | TCP | + +### 10.2.1 GA-PSR-ACTIVATE-UTC-REQ + +This message is sent either by the MS or GANC to initiate GA-PSR Transport Channel activation. + +Direction: GANC to MS, MS to GANC. + +**Table 10.2.1.1: GA-PSR-ACTIVATE-UTC-REQ message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR-ACTIVATE-UTC-REQ message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 100 | UDP Port for GPRS user data transport | Communication Port
11.2.25 | M | TLV | 4 | | | +| 99 | IP address for GPRS user data transport | IP Address
11.2.9 | O | TLV | 7-19 | | | + +#### 10.2.1.1 IP address for GPRS user data transport + +This IE shall be included by the GANC and shall not be included by the MS. It contains GANC IP address for GPRS user data transport if GANC initiates activation. + +#### 10.2.1.2 UDP Port for GPRS user data transport + +This information element contains MS UDP port for GPRS user data transport if MS initiates activation. It contains GANC UDP port for GPRS user data transport if GANC initiates activation. + +### 10.2.2 GA-PSR-ACTIVATE-UTC-ACK + +This message is sent either by the MS or GANC to confirm GA-PSR Transport Channel activation. + +Direction: GANC to MS, MS to GANC. + +**Table 10.2.2.1: GA-PSR-ACTIVATE-UTC-ACK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|----------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR-ACTIVATE-UTC-ACK message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 99 | IP address for GPRS user data transport | IP Address
11.2.9 | O | TLV | 7-19 | | | +| 100 | UDP Port for GPRS user data transport | Communication Port Identity
11.2.25 | C | TLV | 4 | | | +| 39 | GA-PSR TC Activation Status | GA-PSR Cause
11.2.39 | M | TLV | 3 | | | + +#### 10.2.2.1 IP address for GPRS user data transport + +This IE shall be included by the GANC and shall not be included by the MS. It contains GANC IP address for GPRS user data transport if MS initiates successful activation. + +#### 10.2.2.2 UDP Port for GPRS user data transport + +This information element must be included if the GA-PSR cause indicates success (0) and contains the following: + +GANC UDP port for GPRS user data transport if MS initiates activation. + +MS UDP port for GPRS user data transport if GANC initiates activation. + +### 10.2.3 GA-PSR-DEACTIVATE-UTC-REQ + +This message is sent by the MS or by the GANC to initiate GA-PSR Transport Channel deactivation. + +Direction: MS to GANC, GANC to MS. + +**Table 10.2.3.1: GA-PSR-DEACTIVATE-UTC-REQ message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR-DEACTIVATE-UTC-REQ message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 39 | GA-PSR TC Deactivation Cause | GA-PSR Cause
11.2.39 | M | TLV | 3 | | | + +### 10.2.4 GA-PSR-DEACTIVATE-UTC-ACK + +This message is sent by the GANC or by the MS to confirm GA-PSR Transport Channel deactivation. + +Direction: GANC to MS, MS to GANC. + +**Table 10.2.4.1: GA-PSR-DEACTIVATE-UTC-ACK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR-DEACTIVATE-UTC-ACK message identity | Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | + +### 10.2.5 GA-PSR-DATA + +This message is used both in uplink and downlink direction to tunnel GPRS signalling and SMS messages. + +Direction: GANC to MS and MS to GANC. + +**Table 10.1.5.1: GA-PSR-DATA message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR-DATA message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 38 | Requested QoS | QoS
11.2.38 | C | TLV | 3 | | | +| 35 | Packet Flow Identifier | Packet Flow Identifier
11.2.35 | O | TLV | 3 | | | +| 57 | LLC PDU | LLC-PDU
11.2.57 | M | TLV | 2-1562 | | | + +#### 10.2.5.1 Requested QoS + +This Information Element is Mandatory for uplink packets only i.e. in the direction from MS to GANC. This IE shall not be included in downlink packets i.e. in the direction from GANC to MS. + +#### 10.2.5.2 Packet Flow Identifier + +This Information Element is present only if packet flow management procedures are supported. + +### 10.2.6 GA-PSR-UNITDATA + +This message is used to tunnel uplink and downlink GPRS user data messages (on the GA-PSR TC over UDP) between the MS and GANC. + +Direction: GANC to MS and MS to GANC. + +**Table 10.2.6.1: GA-PSR-UNITDATA message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------|-----------------------------------|----------|--------|--------|-------|-------| +| | GA-PSR-UNITDATA message identity | GA-PSR Message Type
11.1.3.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.3.2 | M | V | 4 | | | +| | Sequence Number | Sequence Number
11.1.3.3 | M | V | 2 | | | +| 38 | Requested QoS | QoS
11.2.38 | C | TLV | 3 | | | +| 35 | Packet Flow Identifier | Packet Flow Identifier
11.2.35 | O | TLV | 3 | | | +| 57 | LLC PDU | LLC-PDU
11.2.57 | M | TLV | 2-1562 | | | + +#### 10.2.6.1 Requested QoS + +This Information Element is Mandatory for uplink packets only i.e. in the direction from MS to GANC. This IE shall not be included in downlink packets i.e. in the direction from GANC to MS. + +#### 10.2.6.2 Packet Flow Identifier + +This Information Element is present only if packet flow management procedures are supported. + +### 10.2.7 GA-PSR-PS-PAGE + +This message is used by the GANC to forward the packet page for PS services to the MS. + +Direction: GANC to MS. + +**Table 10.2.7.1: GA-PSR-PS-PAGE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------|------------------------------------|----------|--------|--------|-------|------------------------------------------------------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR-PS-PAGE message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | Reserved | TLLI
11.1.2.2 | M | V | 4 | 0 | To keep GA-PSR-signalling message header consistent. | +| 1 | Mobile Identity | Mobile Identity
11.2.1 | M | TLV | 7-10 | | | + +#### 10.2.7.1 Mobile Identity + +The mobile identity IE contains either IMSI or P-TMSI based on the request from SGSN. + +### 10.2.8 GA-PSR-UFC-REQ + +This message is sent by the GANC to the MS (on the GA-PSR TC over UDP) to initiate uplink flow control procedure. + +Direction: GANC to MS. + +**Table 10.2.8.1: GA-PSR-UFC-REQ message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------|-----------------------------------|----------|--------|--------|-------|-------| +| | GA-PSR-UFC-REQ message identity | GA-PSR Message Type
11.1.3.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.3.2 | M | V | 4 | | | +| | Sequence Number | Sequence Number
11.1.3.3 | M | V | 2 | | | +| 40 | Requested Uplink User Data Rate | User Data Rate
11.2.40 | M | TLV | 5 | | | +| 35 | Packet Flow Identifier | Packet Flow Identifier
11.2.35 | O | TLV | 3 | | | +| 59 | Reset Indicator | Reset Indicator
11.2.59 | O | TLV | 3 | | | + +#### 10.2.8.1 Packet Flow Identifier + +This Information Element is included if the request is related to a specific PFC (e.g. not included when PFM procedures are not supported). + +#### 10.2.8.2 Reset Indicator + +This information element is included if the GANC initiates an uplink flow control condition reset. + +### 10.2.9 GA-PSR-DFC-REQ + +This message is sent by the MS to the GANC (on the GA-PSR TC over UDP) to initiate downlink flow control procedure. + +Direction: MS to GANC. + +**Table 10.2.9.1: GA-PSR-DFC-REQ message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------|-----------------------------------|----------|--------|--------|-------|-------| +| | GA-PSR-DFC-REQ message identity | GA-PSR Message Type
11.1.3.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.3.2 | M | V | 4 | | | +| | Sequence Number | Sequence Number
11.1.3.3 | M | V | 2 | | | +| 40 | Requested Downlink User Data Rate | User Data Rate
11.2.40 | M | TLV | 5 | | | +| 35 | Packet Flow Identifier | Packet Flow Identifier
11.2.35 | O | TLV | 3 | | | + +#### 10.2.9.1 Packet Flow Identifier + +This Information Element is included if the request is related to a specific PFC (e.g. not included when PFM procedures are not supported). + +### 10.2.10 GA-PSR STATUS + +This message is used to indicate protocol errors. + +Direction: MS to GANC. + +**Table 10.2.10.1: GA-PSR STATUS message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------|------------------------------------|----------|--------|---------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR-STATUS message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 39 | GA-PSR Cause | GA-PSR Cause
11.2.39 | M | TLV | 3 | | | +| 52 | PDU in Error | PDU in Error
11.2.52 | M | TLV | 6 - 257 | | | + +### 10.2.11 GA-PSR HANDOVER COMPLETE + +Direction: MS to GANC + +**Table 10.2.11.1: GA-PSR HANDOVER COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR HANDOVER COMPLETE message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | + +### 10.2.12 GA-PSR UPLINK QUALITY INDICATION + +The GANC indicates changes in the uplink quality, which may be used by the MS to trigger the PS handover from GAN procedure. + +Direction: GANC to MS + +**Table 10.2.12.1: GA-PSR UPLINK QUALITY INDICATION message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR UL QUALITY INDICATION message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 33 | UL Quality Indication | UL Quality Indication
11.2.33 | M | TLV | 3 | | | + +### 10.2.13 GA-PSR HANDOVER INFORMATION + +The MS triggers the PS handover from GAN procedure indicating the list of cell identifiers in the target radio access technology. + +Direction: MS to GANC + +**Table 10.2.13.1: GA-PSR HANDOVER INFORMATION message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------------|----------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR HANDOVER INFORMATION message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 15 | GERAN Cell Identifier List | Cell Identifier List
11.2.15 | C | TLV | n | | | +| 106 | GERAN Received Signal Level List | GERAN Received Signal Level List
11.2.70 | C | TLV | n | | | +| 66 | UTRAN Cell Identifier List | UTRAN Cell Identifier List
11.2.66 | C | TLV | n | | | +| 107 | UTRAN Received Signal Level List | UTRAN Received Signal Level List
11.2.70b | C | TLV | n | | | + +#### 10.2.13.1 GERAN Cell Identifier List + +See sub-clause 10.1.32.1. + +#### 10.2.13.2 GERAN Received Signal Level List + +See sub-clause 10.1.32.2. + +#### 10.2.13.3 UTRAN Cell Identifier List + +See sub-clause 10.1.32.3. + +#### 10.2.13.4 UTRAN Received Signal Level List + +See sub-clause 10.1.32.4. + +### 10.2.14 GA-PSR HANDOVER COMMAND + +The GANC orders the MS to perform PS handover from GAN. + +Direction: GANC to MS + +**Table 10.2.14.1: GA-PSR HANDOVER COMMAND message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|-----------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR HANDOVER COMMAND message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 108 | PS Handover to GERAN Command | PS Handover to GERAN Command
11.2.74 | C | TLV | n | | | +| 109 | PS Handover to UTRAN Command | PS Handover to UTRAN Command
11.2.75 | C | TLV | n | | | +| 110 | PS Handover to GERAN PSI | PS Handover to GERAN PSI
11.2.76 | C | TLV | n | | | +| 111 | PS Handover to GERAN SI | PS Handover to GERAN SI
11.2.77 | C | TLV | n | | | + +#### 10.2.14.1 PS Handover to GERAN Command + +If the target radio access technology is GERAN, the value part of the *PS Handover to GERAN Command* IE shall be included and coded as the PS HANDOVER COMMAND message specified in 3GPP TS 44.060 [45]. If this IE is present then the *PS Handover to UTRAN Command* IE shall not be present. + +#### 10.2.14.2 PS Handover to UTRAN Command + +If the target radio access technology is UTRAN, the value part of the PS Handover to UTRAN Command IE shall be included and coded as the INTER SYSTEM TO UTRAN HANDOVER COMMAND message specified in 3GPP TS 25.331 [40]. If this IE is present then the *PS Handover to GERAN Command* IE, the *PS Handover to GERAN PSI* IE and the *PS Handover to GERAN SI* IE shall not be present. + +#### 10.2.14.3 PS Handover to GERAN PSI + +If the target radio access technology is GERAN and PBCCH is present in the target cell, the value part of the *PS Handover to GERAN PSI* IE shall be included and coded as per the minimum set of PSI messages required for operation in A/Gb mode as defined for A/Gb mode to A/Gb mode PS handover (see 3GPP TS 44.060 [45]). When this IE is included the *PS Handover to GERAN SI* IE shall not be present. + +#### 10.2.14.4 PS Handover to GERAN SI + +If the target radio access technology is GERAN and PBCCH is not present in the target cell, the value part of the *PS Handover to GERAN SI* IE shall be included and coded as per the minimum set of SI messages required for operation in A/Gb mode as defined for A/Gb mode to A/Gb mode PS handover (see 3GPP TS 44.060 [45]). When this IE is included the *PS Handover to GERAN PSI* IE shall not be present. + +### 10.2.15 GA-PSR HANDOVER CONTINUE + +The GANC indicates that the MS shall continue to wait for a **GA-PSR HANDOVER COMMAND** message instead of performing a rove-out. + +Direction: GANC to MS + +**Table 10.2.15.1: GA-PSR HANDOVER CONTINUE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR HANDOVER CONTINUE message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | + +### 10.2.16 GA-PSR HANDOVER FAILURE + +The MS indicates that a handover from GAN A/Gb mode (attempted as a result of receiving a **GA-PSR HANDOVER COMMAND** message) failed. + +Direction: MS to GANC + +**Table 10.2.16.1: GA-PSR HANDOVER FAILURE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR HANDOVER FAILURE message identity | GA-PSR Message Type
11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI
11.1.2.2 | M | V | 4 | | | +| 39 | GA-PSR Cause | GA-PSR Cause
11.2.39 | M | TLV | 3 | | | + +## 10.3 GA-RRC control plane messages + +Table 10.3.1 summarizes the GA-RRC control plane messages. + +**Table 10.1.1: GA-RRC control plane messages** + +| GA-RRC control plane messages: | Reference | +|---------------------------------------|------------------| +| GA-RRC REQUEST | 10.3.1 | +| GA-RRC REQUEST ACCEPT | 10.3.2 | +| GA-RRC REQUEST REJECT | 10.3.3 | +| GA-RRC RELEASE REQUEST | 10.3.4 | +| GA-RRC RELEASE | 10.3.5 | +| GA-RRC RELEASE COMPLETE | 10.3.6 | +| GA-RRC PAGING REQUEST | 10.3.7 | +| GA-RRC ACTIVATE CHANNEL | 10.3.8 | +| GA-RRC ACTIVATE CHANNEL ACK | 10.3.9 | +| GA-RRC ACTIVATE CHANNEL COMPLETE | 10.3.10 | +| GA-RRC MODIFY CHANNEL | 10.3.11 | +| GA-RRC MODIFY CHANNEL ACK | 10.3.12 | +| GA-RRC DEACTIVATE CHANNEL REQUEST | 10.3.13 | +| GA-RRC DEACTIVATE CHANNEL | 10.3.14 | +| GA-RRC DEACTIVATE CHANNEL COMPLETE | 10.3.15 | +| GA-RRC SECURITY MODE COMMAND | 10.3.16 | +| GA-RRC SECURITY MODE COMPLETE | 10.3.17 | +| GA-RRC INITIAL DIRECT TRANSFER | 10.3.18 | +| GA-RRC UPLINK DIRECT TRANSFER | 10.3.19 | +| GA-RRC DOWNLINK DIRECT TRANSFER | 10.3.20 | +| GA-RRC RELOCATION INFORMATION | 10.3.21 | +| GA-RRC RELOCATION COMMAND | 10.3.22 | +| GA-RRC RELOCATION ACCESS | 10.3.23 | +| GA-RRC RELOCATION COMPLETE | 10.3.24 | +| GA-RRC RELOCATION FAILURE | 10.3.25 | +| GA-RRC RELOCATION REQUEST | 10.3.26 | +| GA-RRC RELOCATION REQUEST ACK | 10.3.27 | +| GA-RRC UPLINK QUALITY INDICATION | 10.3.28 | +| GA-RRC STATUS | 10.3.29 | + +### 10.3.1 GA-RRC REQUEST + +The MS sends this message to the GANC to establish the GA-RRC Connection for the indicated domain. + +Direction: MS to GANC + +**Table 10.3.1.1: GA-RRC REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|------------|---------------------------------|---------------------------------------|-----------------|---------------|---------------|--------------|--------------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC REQUEST message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 85 | GA-RRC Establishment Cause | GA-RRC Establishment Cause
11.2.85 | M | TLV | 3 | | | + +### 10.3.2 GA-RRC REQUEST ACCEPT + +The GANC sends this message to the MS to indicate that it has accepted the establishment of the GA-RRC Connection. + +Direction: GANC to MS + +**Table 10.3.2.1: GA-RRC REQUEST ACCEPT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC REQUEST ACCEPT message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | + +### 10.3.3 GA-RRC REQUEST REJECT + +The GANC sends this message to the MS to indicate that it has rejected the establishment of the GA-RRC Connection. + +Direction: GANC to MS + +**Table 10.3.3.1: GA-RRC REQUEST REJECT message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC REQUEST REJECT message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 86 | GA-RRC Cause | GA-RRC Cause
11.2.86 | M | TLV | 4 | | | + +### 10.3.4 GA-RRC RELEASE REQUEST + +The MS sends this message to the GANC to indicate that the GANC should initiate release of the signalling connection and related resources for the indicated domain. + +Direction: MS to GANC + +**Table 10.3.4.1: GA-RRC RELEASE REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELEASE REQUEST message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 86 | GA-RRC Cause | GA-RRC Cause
11.2.86 | M | TLV | 4 | | | + +### 10.3.5 GA-RRC RELEASE + +The GANC sends this message to the MS to instruct the MS to release all GA-RRC related resources for the indicated domain. + +Direction: GANC to MS + +**Table 10.3.5.1: GA-RRC RELEASE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELEASE message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 86 | GA-RRC Cause | GA-RRC Cause
11.2.86 | M | TLV | 4 | | | + +### 10.3.6 GA-RRC RELEASE COMPLETE + +The MS sends this message to the GANC to acknowledge the release of all GA-RRC related resources for the indicated domain. + +Direction: MS to GANC + +**Table 10.3.6.1: GA-RRC RELEASE COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELEASE COMPLETE message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | + +### 10.3.7 GA-RRC PAGING REQUEST + +The GANC uses this message to transmit paging information received from the CN to the MS. + +Direction: GANC to MS + +**Table 10.3.7.1: GA-RRC PAGING REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC PAGING REQUEST message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 1 | IMSI or (P)-TMSI | Mobile Identity
11.2.1 | M | TLV | 7-10 | | | +| 87 | GA-RRC Paging Cause | GA-RRC Paging Cause
11.2.87 | O | TLV | 3 | | | + +### 10.3.8 GA-RRC ACTIVATE CHANNEL + +The GANC sends this message to the MS to initiate channel activation. + +Direction: GANC to MS + +**Table 10.3.8.1: GA-RRC ACTIVATE CHANNEL message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC ACTIVATE CHANNEL message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 89 | CTC Activation List | CTC Activation List
11.2.89 | C | TLV | n | | | +| 115 | PTC Activation List | PTC Activation List
11.2.96 | C | TLV | n | | | + +#### 10.3.8.1 CTC Activation List + +The CTC (Circuit Transport Channel) Activation List information element shall be included if the IE "CN Domain Identity" indicates the CS domain. + +#### 10.3.8.2 PTC Activation List + +The PTC (Packet Transport Channel) Activation List information element shall be included if the IE "CN Domain Identity" indicates the PS domain. + +### 10.3.9 GA-RRC ACTIVATE CHANNEL ACK + +The MS sends this message to the GANC to acknowledge the channel activation request. + +Direction: MS to GANC + +**Table 10.3.9.1: GA-RRC ACTIVATE CHANNEL ACK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC ACTIVATE CHANNEL ACK message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 91 | CTC Activation Ack List | CTC Activation Ack List
11.2.91 | C | TLV | n | | | +| 117 | PTC Activation Ack List | PTC Activation Ack List
11.2.98 | C | TLV | n | | | + +#### 10.3.9.1 CTC Activation Ack List + +The CTC Activation Ack List information element shall be included if the IE "CN Domain Identity" indicates the CS domain. + +#### 10.3.9.2 PTC Activation Ack List + +The PTC Activation Ack List information element shall be included if the IE "CN Domain Identity" indicates the PS domain. + +### 10.3.10 GA-RRC ACTIVATE CHANNEL COMPLETE + +The GANC sends this message to the MS to indicate the completion of the channel activation. + +Direction: GANC to MS + +**Table 10.3.10.1: GA-RRC ACTIVATE CHANNEL COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC ACTIVATE CHANNEL COMPLETE message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | + +### 10.3.11 GA-RRC MODIFY CHANNEL + +The GANC sends this message to the MS to initiate channel modification. + +Direction: GANC to MS + +**Table 10.3.11.1: GA-RRC MODIFY CHANNEL message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC MODIFY CHANNEL message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 93 | CTC Modification List | CTC Modification List
11.2.93 | C | TLV | n | | | +| 119 | PTC Modification List | PTC Modification List
11.2.100 | C | TLV | n | | | + +#### 10.3.11.1 CTC Modification List + +The CTC (Circuit Transport Channel) Modification List information element shall be included if the IE "CN Domain Identity" indicates the CS domain. + +#### 10.3.11.2 PTC Modification List + +The PTC (Packet Transport Channel) Modification List information element shall be included if the IE "CN Domain Identity" indicates the PS domain. + +### 10.3.12 GA-RRC MODIFY CHANNEL ACK + +The MS sends this message to the GANC to acknowledge the successful channel modification. + +Direction: MS to GANC + +**Table 10.3.12.1: GA-RRC MODIFY CHANNEL ACK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------|---------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC MODIFY CHANNEL ACK message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 94 | CTC Modification Ack List | CTC Modification Ack List
11.2.94 | C | TLV | n | | | +| 120 | PTC Modification Ack List | PTC Modification Ack List
11.2.101 | C | TLV | n | | | + +#### 10.3.12.1 CTC Modification Ack List + +The CTC (Circuit Transport Channel) Modification Ack List information element shall be included if the IE "CN Domain Identity" indicates the CS domain. + +#### 10.3.12.2 PTC Modification Ack List + +The PTC (Packet Transport Channel) Modification Ack List information element shall be included if the IE "CN Domain Identity" indicates the PS domain. + +### 10.3.13 GA-RRC DEACTIVATE CHANNEL REQUEST + +The MS sends this message to the GANC to request the GANC to deactivate the channel(s) identified in the message for the indicated domain. + +Direction: MS to GANC + +**Table 10.3.13.1: GA-RRC DEACTIVATE CHANNEL REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|----------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC DEACTIVATE CHANNEL REQUEST message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 84 | RAB ID List | RAB ID List
11.2.84 | M | TLV | n | | | +| 86 | GA-RRC Cause | GA-RRC Cause
11.2.86 | M | TLV | 4 | | | + +### 10.3.14 GA-RRC DEACTIVATE CHANNEL + +The GANC sends this message to the MS to instruct the MS to deactivate the channel(s) identified in the message for the indicated domain. + +Direction: GANC to MS + +**Table 10.3.14.1: GA-RRC DEACTIVATE CHANNEL message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC DEACTIVATE CHANNEL message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 84 | RAB ID List | RAB ID List
11.2.84 | M | TLV | n | | | + +### 10.3.15 GA-RRC DEACTIVATE CHANNEL COMPLETE + +The MS sends this message to the GANC to indicate the completion of the channel deactivation. + +Direction: MS to GANC + +**Table 10.3.15.1: GA-RRC DEACTIVATE CHANNEL COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC DEACTIVATE CHANNEL COMPLETE message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | + +### 10.3.16 GA-RRC SECURITY MODE COMMAND + +The GANC sends this message to the MS to indicate the selected integrity algorithm and (optionally) the selected encryption algorithm. The message also includes a random number used to authenticate the MS. + +Direction: GANC to MS + +**Table 10.3.16.1: GA-RRC SECURITY MODE COMMAND message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-----------------------------------------------|-----------------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC SECURITY MODE COMMAND message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 124 | Selected Integrity Protection Algorithm | Selected Integrity Protection Algorithm
11.2.105 | M | TLV | 3 | | | +| 46 | Random Number | Ciphering Command RAND
11.2.46 | M | TLV | 18 | | | +| 125 | Selected Encryption Algorithm | Selected Encryption Algorithm
11.2.106 | O | TLV | 3 | | | + +### 10.3.17 GA-RRC SECURITY MODE COMPLETE + +The MS sends this message to the GANC to provide the MS response to the authentication challenge. + +Direction: MS to GANC + +**Table 10.3.17.1: GA-RRC SECURITY MODE COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC SECURITY MODE COMPLETE message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 47 | Message Authentication Code | Ciphering Command MAC
11.2.47 | M | TLV | 14 | | | + +### 10.3.18 GA-RRC INITIAL DIRECT TRANSFER + +The MS sends this message to the GANC to transfer the initial NAS PDU from the MS to the indicated core network domain. + +Direction: MS to GANC + +**Table 10.3.18.1: GA-RRC INITIAL DIRECT TRANSFER message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------|-------------------------------------------|----------|--------|-------------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC INITIAL DIRECT TRANSFER message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 88 | Intra Domain NAS Node Selector | Intra Domain NAS Node Selector
11.2.88 | M | TLV | 5 | | | +| 26 | L3 Message | L3 Message
11.2.26 | M | TLV | Var. Length | | | + +### 10.3.19 GA-RRC UPLINK DIRECT TRANSFER + +The MS sends this message to the GANC to transfer a subsequent (i.e., other than the initial) NAS PDU from the MS to the indicated core network domain. + +Direction: MS to GANC + +**Table 10.3.19.1: GA-RRC UPLINK DIRECT TRANSFER message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------------|------------------------------------|----------|--------|-------------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC UPLINK DIRECT TRANSFER message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 26 | L3 Message | L3 Message
11.2.26 | M | TLV | Var. Length | | | + +### 10.3.20 GA-RRC DOWNLINK DIRECT TRANSFER + +The GANC sends this message to the MS to transfer a NAS PDU from the indicated core network domain to the MS. + +Direction: GANC to MS + +**Table 10.3.20.1: GA-RRC DOWNLINK DIRECT TRANSFER message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------------|------------------------------------|----------|--------|-------------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC DOWNLINK DIRECT TRANSFER message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 80 | CN Domain Identity | CN Domain Identity
11.2.80 | M | TLV | 3 | | | +| 26 | L3 Message | L3 Message
11.2.26 | M | TLV | Var. Length | | | + +### 10.3.21 GA-RRC RELOCATION INFORMATION + +The MS triggers the handover from GAN Iu mode procedure indicating the list of cell identifiers in the target radio access technology. + +Direction: MS to GANC + +**Table 10.3.21.1: GA-RRC RELOCATION INFORMATION message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------------|----------------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELOCATION INFORMATION message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 126 | CN Domains to Handover | CN Domains to Handover
11.2.107 | M | TLV | 3 | | | +| 15 | GERAN Cell Identifier List | Cell Identifier List
11.2.15 | O | TLV | n | | | +| 106 | GERAN Received Signal Level List | GERAN Received Signal Level List
11.2.70 | C | TLV | n | | | +| 66 | UTRAN Cell Identifier List | UTRAN Cell Identifier List
11.2.66 | O | TLV | n | | | +| 107 | UTRAN Received Signal Level List | UTRAN Received Signal Level List
11.2.70b | C | TLV | n | | | +| 28 | Mobile Station Classmark 2 | Mobile Station Classmark 2
11.2.28 | O | TLV | 5 | | | +| 56 | Mobile Station Classmark 3 | Mobile Station Classmark 3
11.2.56 | O | TLV | 3-34 | | | +| 128 | MS Radio Access Capability | MS Radio Access Capability
11.2.112 | O | TLV | 4-67 | | | +| 64 | UTRAN Classmark | UTRAN Classmark
11.2.64 | C | TLV | n | | | + +#### 10.3.21.1 GERAN Cell Identifier List + +The GERAN Cell Identifier List information element shall be included if handover to a GERAN cell is requested by the mobile station. The cells are ranked in descending order of preference according to measured value. + +#### 10.3.21.2 GERAN Received Signal Level List + +The GERAN Received Signal Level List information element shall be included if the GERAN Cell Identifier List information element is included. It contains the received signal quality for each cell included in the GERAN Cell Identifier List information element. The order of the measurements in the GERAN Received Signal Level List shall be the same as the order of the cell identifiers included in the GERAN Cell Identifier List information element. + +#### 10.3.21.3 UTRAN Cell Identifier List + +The UTRAN Cell Identifier List information element shall be included if handover to an UTRAN cell is requested by the mobile station. The cells are ranked in descending order according to measured Ec/No value. + +#### 10.3.21.4 UTRAN Received Signal Level List + +The UTRAN Received Signal Level List information element shall be included if the UTRAN Cell Identifier List information element is included. It contains the received signal quality for each cell included in the UTRAN Cell Identifier List information element. The order of the measurements in the UTRAN Received Signal Level List shall be the same as the order of the cell identifiers included in the UTRAN Cell Identifier List information element. + +NOTE: At least one of the cell identifier list IEs must be present. + +#### 10.3.21.5 Mobile Station Classmark 2 + +The Mobile Station Classmark 2 information element shall be included if the GERAN Cell Identifier List information element is included. It shall also be included if the MS is GERAN capable and the UTRAN Cell Identifier List information element is included. + +#### 10.3.21.6 Mobile Station Classmark 3 + +The Mobile Station Classmark 3 information element shall be included if the GERAN Cell Identifier List information element is included. It shall also be included if the MS is GERAN capable and the UTRAN Cell Identifier List information element is included. + +#### 10.3.21.7 MS Radio Access Capability + +The MS Radio Access Capability information element shall be included if the GERAN Cell Identifier List information element is included. It shall also be included if the MS is GERAN capable and the UTRAN Cell Identifier List information element is included. + +#### 10.3.21.8 UTRAN Classmark + +The UTRAN Classmark information element shall be included if the UTRAN Cell Identifier List information element is included. This IE includes the INTER RAT HANDOVER INFO message defined in TS 25.331 [40]. The INTER RAT HANDOVER INFO message shall include the UE security information IE and the UE security information2 IE, in addition to the mandatory content of the message. + +### 10.3.22 GA-RRC RELOCATION COMMAND + +The GANC sends this message to the MS to order the MS to handover from GAN Iu mode. + +Direction: GANC to MS + +**Table 10.3.22.1: GA-RRC RELOCATION COMMAND message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELOCATION COMMAND message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 126 | CN Domains to Handover | CN Domains to Handover
11.2.107 | M | TLV | 3 | | | +| 78 | UTRAN RRC Message | UTRAN RRC Message
11.2.111 | M | TLV | n | | | +| 127 | SRNS Relocation Info | UTRAN RRC Message
11.2.111 | C | TLV | N | | | + +#### 10.3.22.1 UTRAN RRC Message + +If the target radio access technology is GERAN, the value part of the UTRAN RRC Message IE is coded as the HANDOVER FROM UTRAN COMMAND message specified in [40]. If the target RAT is UTRAN, the value part of the UTRAN RRC Message IE is coded as the UTRAN reconfiguration message received from the target RNS as specified in [40]; e.g., PHYSICAL CHANNEL RECONFIGURATION. + +#### 10.3.22.2 SRNS Relocation Info + +The SRNS Relocation Info information element includes the SRNS RELOCATION INFO message defined in TS 25.331 [40]. This IE shall be included if the target radio access technology is UTRAN. The content is the same as the SRNS RELOCATION INFO message content sent by the GANC to the target RNC in the Source RNC to Target RNC Transparent Container. Note that the type of this IE is the same as the UTRAN RRC Message defined in sub-clause 11.2.111, with the exception that the IEI is 2-octets in length. + +### 10.3.23 GA-RRC RELOCATION ACCESS + +The MS sends this message to the GANC to indicate that the MS has been commanded to handover a CS domain session to GAN Iu mode but the GA-RRC CS domain sub-layer entity in the MS is not yet in the GA-RRC CONNECTED state. + +Direction: MS to GANC + +**Table 10.3.23.1: GA-RRC RELOCATION ACCESS message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELOCATION ACCESS message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 78 | UTRAN RRC Message | UTRAN RRC Message
11.2.111 | M | TLV | n | | | + +#### 10.3.23.1 UTRAN RRC Message + +This information element contains the entire UTRAN RRC handover message received via the source radio access technology. If the source radio access technology is GERAN, the value part of the UTRAN RRC Message IE is coded as the HANDOVER TO UTRAN COMMAND message specified in [40]. If the source RAT is UTRAN, the value part of the UTRAN RRC Message IE is coded as the UTRAN reconfiguration message received from the target RNS as specified in [40]; e.g., PHYSICAL CHANNEL RECONFIGURATION. + +### 10.3.24 GA-RRC RELOCATION COMPLETE + +The MS sends this message to the GANC to indicate that the handover to GAN Iu mode is complete. + +Direction: MS to GANC + +**Table 10.3.24.1: GA-RRC RELOCATION COMPLETE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELOCATION COMPLETE message identity | Message Type
11.1.1.4 | M | V | 1 | | | +| 126 | CN Domains to Handover | CN Domains to Handover
11.2.107 | M | TLV | 3 | | | + +### 10.3.25 GA-RRC RELOCATION FAILURE + +The MS sends this message to the GANC to indicate failure to complete the handover from GAN Iu mode procedure. + +Direction: MS to GANC + +**Table 10.3.25.1: GA-RRC RELOCATION FAILURE message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELOCATION FAILURE message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 86 | GA-RRC Cause | GA-RRC Cause
11.2.86 | M | TLV | 4 | | | + +### 10.3.26 GA-RRC RELOCATION REQUEST + +The GANC sends this message to the MS to request activation of one or more CTCs, one or more PTCs or a combination of CTCs and PTCs, for the purpose of handover to GAN Iu mode. + +Direction: GANC to MS + +**Table 10.3.26.1: GA-RRC RELOCATION REQUEST message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELOCATION REQUEST message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 126 | CN Domains to Handover | CN Domains to Handover
11.2.107 | M | TLV | 3 | | | +| 89 | CTC Activation List | CTC Activation List
11.2.89 | C | TLV | n | | | +| 115 | PTC Activation List | PTC Activation List
11.2.96 | C | TLV | n | | | + +#### 10.3.26.1 CTC Activation List + +The CTC (Circuit Transport Channel) Activation List information element shall be included if the IE "CN Domains to Handover" indicates the CS domain or both CS and PS domains. + +#### 10.3.26.2 PTC Activation List + +The PTC (Packet Transport Channel) Activation List information element shall be included if the IE "CN Domains to Handover" indicates the PS domain or both CS and PS domains. + +### 10.3.27 GA-RRC RELOCATION REQUEST ACK + +The MS sends this message to the GANC to acknowledge the relocation request. + +Direction: MS to GANC + +**Table 10.3.27.1: GA-RRC RELOCATION REQUEST ACK message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC RELOCATION REQUEST ACK message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 126 | CN Domains to Handover | CN Domains to Handover
11.2.107 | M | TLV | 3 | | | +| 91 | CTC Activation Ack List | CTC Activation Ack List
11.2.91 | C | TLV | n | | | +| 117 | PTC Activation Ack List | PTC Activation Ack List
11.2.98 | C | TLV | n | | | + +#### 10.3.27.1 CTC Activation Ack List + +The CTC Activation Ack List information element shall be included if the IE "CN Domains to Handover" indicates the CS domain or both CS and PS domains. + +#### 10.3.27.2 PTC Activation Ack List + +The PTC Activation Ack List information element shall be included if the IE "CN Domains to Handover" indicates the PS domain or both CS and PS domains. + +### 10.3.28 GA-RRC UPLINK QUALITY INDICATION + +The GANC sends this message to the MS to indicate changes in the uplink quality, which may be used by the MS to trigger the handover from GAN Iu mode procedure. + +Direction: GANC to MS + +**Table 10.3.28.1: GA-RRC UPLINK QUALITY INDICATION message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|---------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC UPLINK QUALITY INDICATION message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 33 | UL Quality Indication | UL Quality Indication
11.2.33 | M | V | 3 | | | + +### 10.3.29 GA-RRC STATUS + +The MS sends this message to the GANC to communicate various error conditions. + +Direction: MS to GANC + +**Table 10.3.29.1: GA-RRC STATUS message content** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|--------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC STATUS message identity | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| 86 | GA-RRC Cause | GA-RRC Cause
11.2.86 | M | TLV | 4 | | | +| 52 | PDU Error | PDU in Error
11.2.52 | M | TLV | 6-257 | | | + +## 10.4 GA-RRC PS user plane messages + +Table 10.4.1 summarizes the GA-RRC PS user plane messages. + +**Table 10.4.1: GA-RRC PS user plane messages** + +| GA-RRC control plane messages: | Reference | +|--------------------------------|-----------| +| GA-RRC PDU | 10.4.1 | + +### 10.4.1 GA-RRC PDU + +This message is used to tunnel uplink and downlink PS domain user data between the MS and the GANC. See sub-clause 11.1.3b for a description of the fields in this message. + +![](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +**Direction: MS to GANC and GANC to MS** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------|---|----|-------|---|---|----|---|------------| +| Version | | PT | spare | E | S | PN | | octet 1 | +| Message Type | | | | | | | | octet 2 | +| Length | | | | | | | | octet 3-4 | +| TEID | | | | | | | | octet 5-8 | +| Sequence Number | | | | | | | | octet 9-10 | +| N-PDU Number | | | | | | | | octet 11 | +| Next Extension Header Type | | | | | | | | octet 12 | +| PS Domain User Data | | | | | | | | | + +**Figure 10.4.1.1: GA-RRC PDU message contents** + +# 11 General message format and information elements coding + +## 11.1 Message coding principles + +Five different message headers are defined in this specification: + +- Message header for the GA-RC and GA-CSR messages (defined in sub-clause 11.1.1) +- Message header for the GA-PSR messages sent over the TCP-based signalling channel (defined in sub-clause 11.1.2) +- Message header for the GA-PSR messages sent over the UDP-based GA-PSR Transport Channel (defined in sub-clause 11.1.3) +- Message header for the GA-RRC messages sent over the TCP-based signalling channel (defined in sub-clause 11.1.3a) +- Message header for the GA-RRC messages sent over the UDP-based GA-RRC Packet Transport Channel (defined in sub-clause 11.1.3b) + +The principles for information element coding are described in sub-clause 11.1.4. + +### 11.1.1 GA-RC and GA-CSR message header information elements + +Each GA-RC and GA-CSR message begins with a 4-octet message header, as shown in Table 11.1.1.1. This message header consists of the following information elements: Length Indicator, Protocol Discriminator, Skip Indicator and Message Type. These IEs are described in the following sub-clauses. + +Note that these information elements are also present in both the GA-PSR message header and the GA-RRC message header defined in sub-clauses 11.1.2 and 11.1.3a, respectively. However, the GA-PSR and GA-RRC message headers include additional information elements. + +**Table 11.1.1.1: GA-RC and GA-CSR message header contents** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RC and GA-CSR
Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0001 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RC and GA-CSR
Message Type | Message Type
11.1.1.4 | M | V | 1 | | | +| | Here continues the list of IE's using TLV coding format and depending on Protocol Discriminator and Message Type as defined in clause 10. | | | | | | | + +#### 11.1.1.1 Length Indicator (LI) + +The first two octets of the message header contains the Length Indicator (LI) information element. The LI is needed as each message is transported using TCP, which provides a 'stream-of-bytes' transmission i.e. no message concept, or message length concept is provided by TCP and this has to be handled in the application layer. + +This field specifies the total length of the message **excluding** the 2 octets for Length Indicator. + +Minimum value for LI is 2 and maximum value is defined as 2048. + +For example: For a message of total length of 20 octets, this field is coded with the decimal value of 18. Then there follows 18 octets of message (i.e. total length of TCP-data is 20 octets). + +![](d116934392360da963e91d840d1e45a8_img.jpg) + +| | | | | | | | | | +|--------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| LI MSB | | | | | | | | octet 1 | +| LI LSB | | | | | | | | octet 2 | + +**Figure 11.1.1.1.1. Length Indicator message header field****Table 11.1.1.1.1: Length Indicator message header field** + +| | +|--------------------------------------------------------------------------------------------------------------------| +| LI value, Length Indicator value (octet 1 and 2) | +| In the LI value field bit 8 of octet 1 is the most significant bit and bit 1 of octet 2 the least significant bit. | +| The Length Indicator consists of 2 octets. | + +#### 11.1.1.2 Protocol Discriminator (PD) + +Bits 1 to 4 of the third octet in the message header contain the Protocol Discriminator (PD) information element. The PD identifies the upper layer protocol to which the message belongs. + +The following Protocol Discriminator values are defined: + +**Table 11.1.1.2.1: Protocol Discriminator Values** + +| Protocol | PD Value | +|----------|----------| +| GA-RC | 0 | +| GA-CSR | 1 | +| GA-PSR | 2 | +| GA-RRC | 3 | + +#### 11.1.1.3 Skip Indicator + +Bits 5 to 8 of the third octet in the message header contain the Skip Indicator information element. A message received with Skip Indicator different from 0000 shall be ignored. A message received with Skip Indicator encoded as 0000 shall not be ignored (unless it is ignored for other reasons). A protocol entity sending any message shall encode the Skip Indicator as 0000. + +#### 11.1.1.4 Message Type + +The Message Type IE is the fourth octet in the message header. Bit 8 of the Message Type value is the most significant bit and bit 1 is the least significant bit. + +The following message types are defined for GA-RC and GA-CSR: + +**Table 11.1.1.4.1: Message Type values for GA-RC** + +| GA-RC message name | Message Type value (decimal) | Message Type value (hex) | +|-----------------------------------|------------------------------|--------------------------| +| GA-RC DISCOVERY REQUEST | 1 | H'01 | +| GA-RC DISCOVERY ACCEPT | 2 | H'02 | +| GA-RC DISCOVERY REJECT | 3 | H'03 | +| GA-RC REGISTER REQUEST | 16 | H'10 | +| GA-RC REGISTER ACCEPT | 17 | H'11 | +| GA-RC REGISTER REDIRECT | 18 | H'12 | +| GA-RC REGISTER REJECT | 19 | H'13 | +| GA-RC DEREGISTER | 20 | H'14 | +| GA-RC REGISTER UPDATE UPLINK | 21 | H'15 | +| GA-RC REGISTER UPDATE DOWNLINK | 22 | H'16 | +| GA-RC CELL BROADCAST INFO | 23 | H'17 | +| GA-RC KEEP ALIVE | 116 | H'74 | +| GA-RC SYNCHRONIZATION INFORMATION | 120 | H'78 | + +**Table 11.1.1.4.2: Message Type values for GA-CSR** + +| GA-CSR message name | Message Type value (decimal) | Message Type value (hex) | +|----------------------------------------|------------------------------|--------------------------| +| GA-CSR CIPHERING MODE COMMAND | 32 | H'20 | +| GA-CSR CIPHERING MODE COMPLETE | 33 | H'21 | +| GA-CSR ACTIVATE CHANNEL | 48 | H'30 | +| GA-CSR ACTIVATE CHANNEL ACK | 49 | H'31 | +| GA-CSR ACTIVATE CHANNEL COMPLETE | 50 | H'32 | +| GA-CSR ACTIVATE CHANNEL FAILURE | 51 | H'33 | +| GA-CSR CHANNEL MODE MODIFY | 52 | H'34 | +| GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE | 53 | H'35 | +| GA-CSR RELEASE | 64 | H'40 | +| GA-CSR RELEASE COMPLETE | 65 | H'41 | +| GA-CSR CLEAR REQUEST | 66 | H'42 | +| GA-CSR HANDOVER ACCESS | 80 | H'50 | +| GA-CSR HANDOVER COMPLETE | 81 | H'51 | +| GA-CSR UPLINK QUALITY INDICATION | 82 | H'52 | +| GA-CSR HANDOVER INFORMATION | 83 | H'53 | +| GA-CSR HANDOVER COMMAND | 84 | H'54 | +| GA-CSR HANDOVER FAILURE | 85 | H'55 | +| GA-CSR PAGING REQUEST | 96 | H'60 | +| GA-CSR PAGING RESPONSE | 97 | H'61 | +| GA-CSR UPLINK DIRECT TRANSFER | 112 | H'70 | +| GA-CSR DOWNLINK DIRECT TRANSFER | 114 | H'72 | +| GA-CSR STATUS | 115 | H'73 | +| GA-CSR CLASSMARK ENQUIRY | 117 | H'75 | +| GA-CSR CLASSMARK CHANGE | 118 | H'76 | +| GA-CSR GPRS SUSPENSION REQUEST | 119 | H'77 | +| GA-CSR UTRAN CLASSMARK CHANGE | 121 | H'79 | +| GA-CSR REQUEST | 128 | H'80 | +| GA-CSR REQUEST ACCEPT | 129 | H'81 | +| GA-CSR REQUEST REJECT | 130 | H'82 | + +### 11.1.2 GA-PSR message header information elements over TCP + +Each GA-PSR message sent over the TCP-based signalling channel begins with an 8-octet message header. This message header consists of the following information elements: Length Indicator, Protocol Discriminator, Skip Indicator, Message Type and TLLI. These IEs are described in the following sub-clauses. + +**Table 11.1.2.1: GA-PSR (TCP) message header contents** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator 11.1.1.1 | M | V | 2 | | | +| | GA-PSR Protocol Discriminator | Protocol Discriminator 11.1.1.2 | M | V | ½ | 0010 | | +| | Skip Indicator | Skip Indicator 11.1.1.3 | M | V | ½ | 0000 | | +| | GA-PSR Message Type | GA-PSR Message Type 11.1.2.1 | M | V | 1 | | | +| | TLLI | TLLI 11.1.2.2 | M | V | 4 | | | +| | Here continues the list of IE's using TLV coding format and depending on Protocol Discriminator and Message Type as defined in clause 10. | | | | | | | + +#### 11.1.2.1 GA-PSR Message Type + +The GA-PSR Message Type IE is the fourth octet in the GA-PSR (TCP) message header. Bit 8 of the GA-PSR Message Type value is the most significant bit and bit 1 is the least significant bit. + +The following GA-PSR Message Type values are defined: + +**Table 11.1.2.1.1: GA-PSR Message Type values (TCP)** + +| GA-PSR message name | GA-PSR Message Type value (decimal) | +|----------------------------------|-------------------------------------| +| GA-PSR-DATA | 1 | +| GA-PSR-PS-PAGE | 3 | +| GA-PSR-ACTIVATE-UTC-REQ | 8 | +| GA-PSR-ACTIVATE-UTC-ACK | 9 | +| GA-PSR-DEACTIVATE-UTC-REQ | 10 | +| GA-PSR-DEACTIVATE-UTC-ACK | 11 | +| GA-PSR STATUS | 12 | +| GA-PSR HANDOVER COMPLETE | 13 | +| GA-PSR UPLINK QUALITY INDICATION | 14 | +| GA-PSR HANDOVER INFORMATION | 15 | +| GA-PSR HANDOVER COMMAND | 16 | +| GA-PSR HANDOVER CONTINUE | 17 | +| GA-PSR HANDOVER FAILURE | 18 | + +#### 11.1.2.2 Temporary Logical Link Identity (TLLI) + +Octets 5 to 8 of the GA-PSR (TCP) message header contain the Temporary Logical Link Identity (TLLI) information element. The TLLI identifies the MS this message was sent by or sent to. + +### 11.1.3 GA-PSR message header information elements over UDP + +Each GA-PSR message sent over the UDP-based GA-PSR Transport Channel begins with a 7-octet message header. This message header consists of the following information elements: GA-PSR Message Type, TLLI, and Sequence Number. These IEs are described in the following sub-clauses. + +**Table 11.1.3.1: GA-PSR (UDP) message header contents** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----------|--------|--------|-------|-------| +| | GA-PSR Message Type | GA-PSR Message Type 11.1.3.1 | M | V | 1 | | | +| | TLLI | TLLI 11.1.3.2 | M | V | 4 | | | +| | Sequence Number | Sequence Number 11.1.3.3 | M | V | 2 | | | +| | Here continues the list of IE's using TLV coding format and depending on Protocol Discriminator and Message Type as defined in clause 10. | | | | | | | + +#### 11.1.3.1 GA-PSR Message Type + +The GA-PSR Message Type IE is the first octet in the GA-PSR (UDP) message header. Bit 8 of the GA-PSR Message Type value is the most significant bit and bit 1 is the least significant bit. + +The following GA-PSR Message Type values are defined: + +**Table 11.1.3.1.1: GA-PSR Message Type values (UDP)** + +| GA-PSR message name | GA-PSR Message Type value (decimal) | +|---------------------|-------------------------------------| +| GA-PSR UNITDATA | 2 | +| GA-PSR-UFC-REQ | 6 | +| GA-PSR-DFC-REQ | 7 | + +#### 11.1.3.2 Temporary Logical Link Identity (TLLI) + +Octets 2 to 5 of the GA-PSR (UDP) message header contain the Temporary Logical Link Identity (TLLI) information element. The TLLI identifies the MS this message was sent by or sent to. + +#### 11.1.3.3 Sequence Number + +Octets 6 to 7 of the GA-PSR (UDP) message header contain the Sequence Number information element with value in the range of 0 to 65535. + +### 11.1.3a GA-RRC message header information elements over TCP + +Each GA-RRC message sent over the TCP-based signalling channel begins with a 4-octet message header. This message header consists of the following information elements: Length Indicator, Protocol Discriminator, Skip Indicator, and GA-RRC Message Type. These IEs are described in the following sub-clauses. + +**Table 11.1.3a.1: GA-RRC (TCP) message header contents** + +| IEI | Information Element | Type/Reference | Presence | Format | Length | Value | Notes | +|-----|------------------------------------------|------------------------------------|----------|--------|--------|-------|-------| +| | Length Indicator | Length Indicator
11.1.1.1 | M | V | 2 | | | +| | GA-RRC Protocol Discriminator | Protocol Discriminator
11.1.1.2 | M | V | ½ | 0011 | | +| | Skip Indicator | Skip Indicator
11.1.1.3 | M | V | ½ | 0000 | | +| | GA-RRC Message Type | GA-RRC Message Type
11.1.3a.1 | M | V | 1 | | | +| | Other IEs as defined in sub-clause 10.3. | | | | | | | + +#### 11.1.3a.1 GA-RRC Message Type + +The GA-RRC Message Type IE is the fourth octet in the GA-RRC (TCP) message header. Bit 8 of the GA-RRC Message Type value is the most significant bit and bit 1 is the least significant bit. + +The following GA-RRC (TCP) Message Type values are defined: + +**Table 11.1.3a.1.1: GA-RRC Message Type values (TCP)** + +| GA-RRC message name | GA-RRC Message Type value (decimal) | +|------------------------------------|-------------------------------------| +| GA-RRC REQUEST | 1 | +| GA-RRC REQUEST ACCEPT | 2 | +| GA-RRC REQUEST REJECT | 3 | +| GA-RRC RELEASE REQUEST | 4 | +| GA-RRC RELEASE | 5 | +| GA-RRC RELEASE COMPLETE | 6 | +| GA-RRC PAGING REQUEST | 7 | +| GA-RRC ACTIVATE CHANNEL | 8 | +| GA-RRC ACTIVATE CHANNEL ACK | 9 | +| GA-RRC ACTIVATE CHANNEL COMPLETE | 10 | +| GA-RRC MODIFY CHANNEL | 11 | +| GA-RRC MODIFY CHANNEL ACK | 12 | +| GA-RRC DEACTIVATE CHANNEL REQUEST | 13 | +| GA-RRC DEACTIVATE CHANNEL | 14 | +| GA-RRC DEACTIVATE CHANNEL COMPLETE | 15 | +| GA-RRC SECURITY MODE COMMAND | 16 | +| GA-RRC SECURITY MODE COMPLETE | 17 | +| GA-RRC INITIAL DIRECT TRANSFER | 18 | +| GA-RRC UPLINK DIRECT TRANSFER | 19 | +| GA-RRC DOWNLINK DIRECT TRANSFER | 20 | +| GA-RRC RELOCATION INFORMATION | 21 | +| GA-RRC RELOCATION COMMAND | 22 | +| GA-RRC RELOCATION ACCESS | 23 | +| GA-RRC RELOCATION COMPLETE | 24 | +| GA-RRC RELOCATION FAILURE | 25 | +| GA-RRC RELOCATION REQUEST | 26 | +| GA-RRC RELOCATION REQUEST ACK | 27 | +| GA-RRC UPLINK QUALITY INDICATION | 28 | +| GA-RRC STATUS | 29 | + +### 11.1.3b GA-RRC message header over UDP + +Each GA-RRC message sent over the UDP-based Packet Transport Channel begins with a message header that is as defined for the G-PDU message in the GTP-U protocol in [53]. The message header is shown below for information. See [53] for a description of each field. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------|---|---|----|-------|---|---|----|------------| +| Version | | | PT | spare | E | S | PN | octet 1 | +| Message Type | | | | | | | | octet 2 | +| Length | | | | | | | | octet 3-4 | +| TEID | | | | | | | | octet 5-8 | +| Sequence Number | | | | | | | | octet 9-10 | +| N-PDU Number | | | | | | | | octet 11 | +| Next Extension Header Type | | | | | | | | octet 12 | + +**Figure 11.1.3b.1: GA-RRC (PTC) message header contents** + +**Table 11.1.3b.1: GA-RRC (PTC) message header description** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Version (octet 1)
The Version field shall be set to value '001'.

PT, Payload Type (octet 1)
The Payload Type field shall be set to value '1'.

E, Extensions Header Flag (octet 1)
The use of the Extensions Header Flag is described in [53]. The MS shall set the E field to value '0' for all messages sent to the GANC and disregard all extension fields if present in messages received from the GANC.

S, Sequence Number Flag (octet 1)
Bit
2
0 The Sequence Number field is not present or is present but not meaningful
1 The Sequence Number field is present
See sub-clause 11.1.3b.2 for the handling of this field.

PN, N-PDU Number Flag (octet 1)
Bit
1
0 The N-PDU Number field is not present or is present but not meaningful
1 The N-PDU Number field is present
The MS shall set PN to value '0' for all messages sent to the GANC.

Message Type (octet 2)
The GTP-U Message Type field carries the GA-RRC PTC Message Type value as defined in sub-clause 11.1.3b.1.

Length (octet 3-4)
This field indicates the length in octets of the payload; i.e., the rest of the message following the mandatory part of the header (that is the first 8 octets).
The MSB is octet 3 and the LSB is octet 4.

TEID, Tunnel Endpoint ID (octet 5-8)
This field contains the TEID value that has been assigned to the MS (for downlink messages) or the GANC (for uplink messages) for the PTC to which this message belongs. The format is as defined in sub-clause 11.2.110, "TEID" but with no IEI and no length fields.

Sequence Number (octet 9-10)
This field shall be present if and only if any one or more of the S, PN and E flags are set. This field is meaningful if and only if the Sequence Number Flag is set to 1. The handling of this field is specified in sub-clause 11.1.3b.2.

N-PDU Number (octet 11)
This field shall be present if and only if any one or more of the S, PN and E flags are set. This field is meaningful if and only if the N-PDU Number Flag is set to 1. If the Sequence Number field shall be included in messages sent to the GANC, the MS shall fill the N-PDU Number field with the value '00000000' for all messages sent to the GANC and disregard all N-PDU Number fields if present in messages received from the GANC.

Next Extension Header Type (octet 11)
This field shall be present if and only if any one or more of the S, PN and E flags are set. This field is meaningful if and only if the Extensions Header Flag is set to 1. If the Sequence Number field shall be included in messages sent to the GANC, the MS shall fill the Next Extensions Header Type field with the value '00000000' for all messages sent to the GANC and disregard all extension fields if present in messages received from the GANC.

| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 11.1.3b.1 GA-RRC PTC Message Type + +The GA-RRC PTC Message Type field is the second octet in the GA-RRC (PTC) message header. Bit 8 of the GA-RRC PTC Message Type value is the most significant bit and bit 1 is the least significant bit. + +The following GA-RRC PTC message types are defined: + +**Table 11.1.3a.1.1: Message types for GA-RRC (UDP)** + +| GA-RRC PTC message name | GA-RRC PTC Message Type value (decimal) | +|-------------------------|-----------------------------------------| +| GA-RRC PDU | 255 | + +#### 11.1.3b.2 GA-RRC Sequence Number Handling + +The following describes the use of GA-RRC PDU message sequence numbering assuming sequencing has been activated for the PTC (i.e., Delivery Order is requested in the IE "RAB Configuration" associated with the PTC). + +The sending MS shall use 0 for the value of the Sequence Number of the first GA-RRC PDU message in a tunnel, only during the PDP context activation, and shall increment the Sequence Number for each following GA-RRC PDU message. The value shall wrap to zero after 65535. + +The receiving MS shall set the content of a counter to zero, only during the PDP context activation. When the receiving MS receives a valid GA-RRC PDU message, it shall increment this counter by one. This counter shall wrap to zero after 65535. It defines the 'Expected Sequence Number'. + +Based on the received and Expected Sequence Number values, the receiving MS may decide whether or not to discard the received GA-RRC PDU message. + +The receiving MS shall reorder the incoming T-PDUs in sequence if the Reordering Required flag in the PDP context is set. In this case, if needed, the receiving MS shall take into account a maximum number of valid received frames and a maximum elapsed time to assume that a GA-RRC PDU message was lost. + +The sequence numbers allocated by the CN (down-link) and MS (uplink) are kept unchanged irrespective of the number of GA-RRC and GTP tunnels the PDU is transferred over. Therefore, GANC shall use on the Up interface for down-link PDUs the G-PDU sequence number received from the SGSN, and shall use on the Iu interface for uplink PDUs the GA-RRC PDU sequence number received from the MS. In case of SRNS relocation and intersystem change, the GANC shall tunnel PDUs without changing the G-PDU sequence numbers. + +### 11.1.4 Information Element Coding principles + +Each information element after the relevant message header is coded using the TLV principle as following: + +- The first part of each IE is the *Type* field identifying the Information Element. The *Type* field is coded using either 1 or 2 octets. The *ext* field in octet 1 of the Information Element is the field extension bit and defines if the 2nd *Type* field octet is included: +- if set to 0, then the *Type* field consists of one octet with a value less than or equal to 127 (see Figure 11.1.4.1); + +![](133d09b09892b9fa5e84cfaa627e11a2_img.jpg) + +| | | | | | | | | | +|-------|-------------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| ext=0 | Type value | | | | | | | octet 1 | + +**Figure 11.1.4.1: Type field structure (coding using one octet)** + +- if set to 1, then the *Type* field consists of two octets with a value greater than 127 (see Figure 11.1.4.2). + +![](e04013719a8410d8f37a6bd8fae3f45b_img.jpg) + +| | | | | | | | | | +|-------|---------------------------|---|---|---|---|---|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| ext=1 | Type value | | | | | | | octet 1 | +| | Type value (cont.) | | | | | | | octet 1a | + +**Figure 11.1.4.2: Type field structure (coding using two octets)** + +- The second part of each IE is the *Length* field identifying the length of the *Value* field of the Information Element. The *Length* field is coded using either 1 or 2 octets. The *ext* field in octet 2 of the information element is the field extension bit and defines if the 2nd *Length* field octet is included: +- if set to 0, then the *Length* field consists of one octet with a value less than or equal to 127 (see Figure 11.1.4.3); + +![](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +| | | | | | | | | | +|-------|--------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| ext=0 | Length value | | | | | | | octet 2 | + +**Figure 11.1.4.3: *Length* field structure (coding using one octet)** + +- if set to 1, then the *Length* field consists of two octets with a value greater than 127 (see Figure 11.1.4.4). + +![](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +| | | | | | | | | | +|----------------------|--------------|---|---|---|---|---|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| ext=1 | Length value | | | | | | | octet 2 | +| Length value (cont.) | | | | | | | | octet 2a | + +**Figure 11.1.4.4: *Length* field structure (coding using two octets)** + +- The third part of each IE is the *Value* field of the Information Element. The length of the *Value* field depends on the *Type* field of the IE and is defined in the sub-clauses below 11.2. + +When the *Type* field or the *Length* field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. + +### 11.1.5 Network Byte order + +The Network byte order shall be Big-Endian. + +## 11.2 IE Type and Identifiers + +**Table 11.2.1: IE type and identifiers for Unlicensed Radio Resources management** + +| IE | Identifier | Reference | +|--------------------------------------------|------------|-----------| +| Mobile Identity | 1 | 11.2.1 | +| GAN Release Indicator | 2 | 11.2.2 | +| Radio Identity | 3 | 11.2.3 | +| GERAN Cell Identity | 4 | 11.2.4 | +| Location Area Identification | 5 | 11.2.5 | +| GERAN/UTRAN coverage Indicator | 6 | 11.2.6 | +| GAN Classmark | 7 | 11.2.7 | +| Geographical Location | 8 | 11.2.8 | +| GANC-SEGW IP Address | 9 | 11.2.9 | +| GANC-SEGW Fully Qualified Domain/Host Name | 10 | 11.2.10 | +| Redirection Counter | 11 | 11.2.11 | +| Discovery Reject Cause | 12 | 11.2.12 | +| GAN Cell Description | 13 | 11.2.13 | +| GAN Control Channel Description | 14 | 11.2.14 | +| Cell Identifier List | 15 | 11.2.15 | +| TU3907 Timer | 16 | 11.2.16 | +| GSM RR/UTRAN RRC State | 17 | 11.2.17 | +| Routing Area Identification | 18 | 11.2.18 | +| GAN Band | 19 | 11.2.19 | +| GA-RC/GA-CSR/GA-PSR State | 20 | 11.2.20 | +| Register Reject Cause | 21 | 11.2.21 | +| TU3906 Timer | 22 | 11.2.22 | +| TU3910 Timer | 23 | 11.2.23 | +| TU3902 Timer | 24 | 11.2.24 | +| L3 Message | 26 | 11.2.26 | +| Channel Mode | 27 | 11.2.27 | +| Mobile Station Classmark 2 | 28 | 11.2.28 | +| RR Cause | 29 | 11.2.29 | +| Cipher Mode Setting | 30 | 11.2.30 | +| GPRS Resumption | 31 | 11.2.31 | +| Handover From GAN Command | 32 | 11.2.32 | +| UL Quality Indication | 33 | 11.2.33 | +| TLLI | 34 | 11.2.34 | +| Packet Flow Identifier | 35 | 11.2.35 | +| Suspension Cause | 36 | 11.2.36 | +| TU3920 Timer | 37 | 11.2.37 | +| QoS | 38 | 11.2.38 | +| GA-PSR Cause | 39 | 11.2.39 | +| User Data Rate | 40 | 11.2.40 | +| Routing Area Code | 41 | 11.2.41 | +| AP Location | 42 | 11.2.42 | +| TU4001 Timer | 43 | 11.2.43 | +| Location Status | 44 | 11.2.44 | +| Cipher Response | 45 | 11.2.45 | +| Ciphering Command RAND | 46 | 11.2.46 | +| Ciphering Command MAC | 47 | 11.2.47 | +| Ciphering Key Sequence Number | 48 | 11.2.48 | +| SAPI ID | 49 | 11.2.49 | +| Establishment Cause | 50 | 11.2.50 | +| Channel Needed | 51 | 11.2.51 | +| PDU in Error | 52 | 11.2.52 | +| Sample Size | 53 | 11.2.53 | +| Payload Type | 54 | 11.2.54 | +| Multi-rate Configuration | 55 | 11.2.55 | +| Mobile Station Classmark 3 | 56 | 11.2.56 | +| LLC-PDU | 57 | 11.2.57 | +| Location Black List indicator | 58 | 11.2.58 | +| Reset Indicator | 59 | 11.2.59 | +| TU4003 Timer | 60 | 11.2.60 | +| AP Service Name | 61 | 11.2.61 | +| GAN Service Zone Information | 62 | 11.2.62 | + +| IE | Identifier | Reference | +|--------------------------------------------|------------|-----------| +| RTP Redundancy Configuration | 63 | 11.2.63 | +| UTRAN Classmark | 64 | 11.2.64 | +| Classmark Enquiry Mask | 65 | 11.2.65 | +| UTRAN Cell Identifier List | 66 | 11.2.66 | +| Serving GANC table indicator | 67 | 11.2.67 | +| Registration indicators | 68 | 11.2.68 | +| GAN PLMN List | 69 | 11.2.69 | +| Required GAN Services | 71 | 11.2.71 | +| Broadcast Container | 72 | 11.2.72 | +| 3G Cell Identity | 73 | 11.2.73 | +| MS Radio Identity | 96 | 11.2.3 | +| GANC IP Address | 97 | 11.2.9 | +| GANC Fully Qualified Domain/
Host Name | 98 | 11.2.10 | +| IP address for GPRS user data
transport | 99 | 11.2.9 | +| UDP Port for GPRS user data
transport | 100 | 11.2.25 | +| GANC TCP port | 103 | 11.2.25 | +| RTP UDP port | 104 | 11.2.25 | +| RTCP UDP port | 105 | 11.2.25 | +| GERAN Received Signal Level List | 106 | 11.2.70 | +| UTRAN Received Signal Level List | 107 | 11.2.70b | +| PS Handover to GERAN Command | 108 | 11.2.74 | +| PS Handover to UTRAN Command | 109 | 11.2.75 | +| PS Handover to GERAN PSI | 110 | 11.2.76 | +| PS Handover to GERAN SI | 111 | 11.2.77 | +| TU4004 Timer | 112 | 11.2.78 | +| GAN Mode Indicator | 79 | 11.2.79 | +| CN Domain Identity | 80 | 11.2.80 | +| GAN Iu Mode Cell Description | 81 | 11.2.81 | +| 3G UARFCN | 82 | 11.2.82 | +| RAB ID | 83 | 11.2.83 | +| RAB ID List | 84 | 11.2.84 | +| GA-RRC Establishment Cause | 85 | 11.2.85 | +| GA-RRC Cause | 86 | 11.2.86 | +| GA-RRC Paging Cause | 87 | 11.2.87 | +| Intra Domain NAS Node Selector | 88 | 11.2.88 | +| CTC Activation List | 89 | 11.2.89 | +| CTC Description | 90 | 11.2.90 | +| CTC Activation Ack List | 91 | 11.2.91 | +| CTC Activation Ack Description | 92 | 11.2.92 | +| CTC Modification List | 93 | 11.2.93 | +| CTC Modification Ack List | 94 | 11.2.94 | +| CTC Modification Ack Description | 95 | 11.2.95 | +| PTC Activation List | 115 | 11.2.96 | +| PTC Description | 116 | 11.2.97 | +| PTC Activation Ack List | 117 | 11.2.98 | +| PTC Activation Ack Description | 118 | 11.2.99 | +| PTC Modification List | 119 | 11.2.100 | +| PTC Modification Ack List | 120 | 11.2.101 | +| PTC Modification Ack Description | 121 | 11.2.102 | +| RAB Configuration | 122 | 11.2.103 | +| Multi-rate Configuration 2 | 123 | 11.2.104 | +| Selected Integrity Protection
Algorithm | 124 | 11.2.105 | +| Selected Encryption Algorithm | 125 | 11.2.106 | +| CN Domains to Handover | 126 | 11.2.107 | +| 3G Security Capability | 74 | 11.2.108 | +| NAS Synchronisation Indicator | 75 | 11.2.109 | +| GANC TEID | 76 | 11.2.110 | +| MS TEID | 77 | 11.2.110 | +| UTRAN RRC Message | 78 | 11.2.111 | + +| IE | Identifier | Reference | +|------------------------------------|------------|-----------| +| SRNS Relocation Info | 127 | 11.2.111 | +| MS Radio Access Capability | 128 | 11.2.112 | +| Handover Reporting Control | 129 | 11.2.113 | +| Tracking Area Identity | 130 | 11.2.114 | +| E-UTRAN Cell Identity | 131 | 11.2.115 | +| E-UTRAN Camping Indicator | 132 | 11.2.116 | +| Bandwidth-efficient Mode Indicator | 133 | 11.2.117 | + +### 11.2.1 Mobile Identity + +The purpose of the *Mobile Identity* information element is to provide either the international mobile subscriber identity, IMSI, the temporary mobile subscriber identity, TMSI/P-TMSI, the international mobile equipment identity, IMEI or the international mobile equipment identity together with the software version number, IMEISV. + +![](4842f073775fb1e84d101c02fd74e59e_img.jpg) + +| | | | +|---------------------------------------------------------------------------------|--|-------------| +| 8   7   6   5   4   3   2   1 | | | +| Mobile Identity IEI | | octet 1 | +| Length of mobile identity contents | | octet 2, 2a | +| The rest of the IE is coded as in [8] not including IEI and length, if present. | | octet 3 | +| | | .... | +| | | octet n | + +**Figure 11.2.1.1: Mobile Identity information element** + +### 11.2.2 GAN Release Indicator + +This information element is used to indicate the GAN Release supported. + +![](7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg) + +| | | | +|---------------------------------------------|-----|---------| +| 8   7   6   5   4   3   2   1 | | | +| GAN Release Indicator IEI | | octet 1 | +| Length of GAN Release Indicator IE contents | | octet 2 | +| spare | URI | octet 3 | + +**Figure 11.2.2.1: GAN Release Indicator information element** + +**Table 11.2.2.1: GAN Release Indicator information element** + +| URI, GAN Release Indicator (octet 3) | | | +|--------------------------------------|---|-----------------------------------| +| Bits | | | +| 3 | 2 | 1 | +| 0 | 0 | 1 Release 1 (i.e. 3GPP Release-6) | +| 0 | 1 | 0 Release 2 (i.e. 3GPP Release-7) | +| 0 | 1 | 1 Release 3 (i.e. 3GPP Release-8) | +| All other values are reserved. | | | + +### 11.2.3 Access Identity + +The Access Identity IE is used for transmission of identifiers of the Access Technologies e.g. the Bluetooth Device Address (BD\_ADDR) or WLAN MAC Address. + +![](63d04fb1a19cac79b0f4705d931094e2_img.jpg) + +| | | | +|------------------------------------|------------------|---------| +| 8   7   6   5   4   3   2   1 | | | +| Access Identity IEI | | octet 1 | +| Length of Access Identity contents | | octet 2 | +| Spare | Type of identity | octet 3 | +| Access Identity MSB value | | octet 4 | +| ... | | | +| Access Identity LSB value | | octet 9 | + +**Figure 11.2.3.1: Access Identity information element** + +**Table 11.2.3.1: Access Identity information element** + +| Type of Identity (octet 3) | | | | Bits | +|----------------------------|---|---|---|--------------------------------------| +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | IEEE MAC-address format | +| 0 | 0 | 0 | 1 | | +| to | | | | | +| 1 | 1 | 1 | 1 | All other values are for future use. | + +### 11.2.4 GERAN Cell Identity + +The purpose of the *Cell Identity* information element is to identify a cell within a location area. + +![](802707b774f2d2973b49cea2020e8453_img.jpg) + +| | | | +|---------------------------------------------------------------------------------|--|-------------| +| 8      7      6      5      4      3      2      1 | | | +| GERAN Cell Identity IEI | | octet 1 | +| Length of GERAN Cell Identity IE contents | | octet 2, 2a | +| The rest of the IE is coded as in [8] not including IEI and length, if present. | | octet 3 | +| | | .... | +| | | octet n | + +**Figure 11.2.4.1 GERAN *Cell Identity* information element** + +### 11.2.5 Location Area Identification + +The purpose of the *Location Area Identification* information element is to provide an unambiguous identification of location areas within the area covered by the GSM system. + +![](ec035e97a11ce40541dec6d88d54c7cb_img.jpg) + +| | | | +|---------------------------------------------------------------------------------|--|-------------| +| 8      7      6      5      4      3      2      1 | | | +| Location Area Identification IEI | | octet 1 | +| Length of Location Area Identification IE contents | | octet 2, 2a | +| The rest of the IE is coded as in [8] not including IEI and length, if present. | | octet 3 | +| | | .... | +| | | octet n | + +**Figure 11.2.5.1: Location Area Identification information element** + +### 11.2.6 GERAN/UTRAN coverage Indicator + +This information element is used to indicate the presence of GERAN/UTRAN coverage in the current MS location. + +![](aff7d03f930d62115362cc026be487ed_img.jpg) + +| | | | +|----------------------------------------------------|--|---------| +| 8      7      6      5      4      3      2      1 | | | +| GERAN/UTRAN coverage Indicator IEI | | octet 1 | +| Length of GERAN/UTRAN coverage Identity contents | | octet 2 | +| GCI | | octet 3 | + +**Figure 11.2.6.1 GERAN/UTRAN coverage Indicator information element****Table 11.2.6.1: GERAN/UTRAN coverage Indicator information element** + +| GCI, GERAN/UTRAN coverage Indicator (octet 3) | | +|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Normal Service in the GERAN/UTRAN | +| 1 | Limited Service in the GERAN/UTRAN | +| 2 | MS has not found GERAN/UTRAN coverage (LAI information taken from SIM, if available). This value shall be used if the MS is camped on a E-UTRAN cell. | +| 3 | MS has found GERAN/UTRAN coverage, service state unknown | +| 4-255 | All other values are for future use | + +### 11.2.7 GAN Classmark + +The purpose of the *GAN Classmark* information element is to provide the network with information concerning aspects of both the cellular and generic access interfaces, as well as the support for RTP redundancy of the mobile station equipment. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------|----|---|------|------|---|----------|-----|---------| +| GAN Classmark IEI | | | | | | | | octet 1 | +| Length of GAN Classmark IE contents | | | | | | | | octet 2 | +| spare | UC | | GC | TGA | | | | octet 3 | +| spare | | | BMSI | GMSI | | PS
HO | RRS | octet 4 | + +**Figure 11.2.7.1: GAN Classmark information element** + +**Table 11.2.7.1: GAN Classmark information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

TGA, Type of Generic Access (octet 3)
This field is used to indicate the current Generic Access type used by the mobile station to access the GAN.
Bit
4 3 2 1
0 0 0 0 no radio
0 0 0 1 Bluetooth
0 0 1 0 WLAN 802.11
1 1 1 1 unspecified
All other values are reserved in Release 1.

| +|

GC, GERAN Capable (octet 3)
Bit
5
0 The MS is not GERAN capable.
1 The MS is GERAN capable.

| +|

UC, UTRAN Capable (octet 3)
Bit
6
0 The MS is not UTRAN capable.
1 The MS is UTRAN capable.

| +|

RRS, RTP Redundancy Support (octet 4)
Bit 1
0 RTP Redundancy not supported
1 RTP Redundancy supported

| +|

PS HO, PS Handover Capable (octet 4)
Bit
2
0 The MS does not support PS handover to/from GAN A/Gb mode.
1 The MS supports PS handover to/from GAN A/Gb mode.

| +|

GMSI, GAN Mode Support Indicator (octet 4)
Bits
4 3
0 0 Unspecified
0 1 The MS supports GAN A/Gb mode only
1 0 The MS supports GAN Iu mode only
1 1 The MS supports GAN A/Gb mode and GAN Iu mode

| +|

BMSI, Bandwidth-efficient Mode Support Indicator (octet 4)
Bit
5
0 The MS does not support RFC 4867 [48] bandwidth-efficient mode.
1 The MS supports RFC 4867 [48] bandwidth-efficient mode.

| + +### 11.2.8 Geographical Location + +This is a variable length information element providing an estimate of a geographic location of a target MS. + +It is coded as follows: + +![](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Geographical Location Indicator IEI | | | | | | | | octet 1 | +| Length of Geographical Location value contents | | | | | | | | octet 2, 2a | +| Location estimate | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +**Figure 11.2.8.1: Geographical Location information element** + +The Location Estimate field is composed of 1 or more octets with an internal structure according to section 7 in [5]. + +### 11.2.9 IP Address + +The IP Address information element contains one IP address. + +![](7913c315e0db8233cb1ac2455e4a0a81_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|---|---|---|---|---|---|---|-------------| +| IP address IEI | | | | | | | | octet 1 | +| Length of IP address IE contents | | | | | | | | octet 2, 2a | +| IP Address type | | | | | | | | octet 3 | +| Address information MSB | | | | | | | | octet 4 | +| | | | | | | | | ... | +| Address information LSB | | | | | | | | octet n | + +**Figure 11.2.9.1: IP address information element** + +**Table 11.2.9.1: IP address information element** + +| | | | +|----------------------------------------------------------------------------------------|---|--------------------------| +| IP address type number value (octet 3) | | | +| Bits | | | +| 8 | 7 | 6 5 4 3 2 1 | +| 0 | 0 | 1 0 0 0 0 1 IPv4 address | +| 0 | 1 | 0 1 0 1 1 1 IPv6 address | +| All other values shall be interpreted as IPv4 address in this version of the protocol. | | | + +If PDP type number indicates IPv4, the Address information in octet 4 to octet 7 contains the IPv4 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 7 the least significant bit. + +If PDP type number indicates IPv6, the Address information in octet 4 to octet 19 contains the IPv6 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 19 the least significant bit. + +### 11.2.10 Fully Qualified Domain/Host Name (FQDN) + +The Fully Qualified Domain/Host Name (FQDN) information element contains the name of a network element (i.e. SEGW or a GANC). The information element is coded in string format. + +![](d9b929d9bc834c1b396d8319d61ce1cf_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------|---|---|---|---|---|---|---|-------------| +| FQDN IEI | | | | | | | | octet 1 | +| Length of FQDN IE contents | | | | | | | | octet 2, 2a | +| FQDN 1 st character | | | | | | | | octet 3 | +| | | | | | | | | ... | +| FQDN last character | | | | | | | | octet n | + +**Figure 11.2.10.1: FQDN information element** + +**Table 11.2.10.1: FQDN information element** + +FQDN, Fully Qualified Domain/Host Name value (octet 3 to octet n) + +The FQDN is coded as a string. This means that the 1st character of the string is coded in octet 3 and the last character of the string is coded in the last octet of this IE (octet n). + +### 11.2.11 Redirection Counter + +The purpose of this information element is to indicate to the GANC the number of times the MS has been redirect and still has not obtained service. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------|---|---|---|---|---|---|---|---------| +| Redirection Counter IEI | | | | | | | | octet 1 | +| Length of Redirection Counter contents | | | | | | | | octet 2 | +| Redirection Counter value | | | | | | | | octet 3 | + +**Figure 11.2.11.1: Redirection Counter information element****Table 11.2.11.1: Redirection Counter information element** + +Redirection Counter value (octet 3 ) + +In the Redirection Counter value field bit 8 of octet 3 is the most significant bit + +The value is given in number redirections + +The Redirection Counter value consists of 1 octets. + +### 11.2.12 Discovery Reject Cause + +The Discovery reject Cause information element contains information to the MS about the reason for a Discovery Reject. The MS shall act according to the cause value received. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|---|---------| +| Discovery Reject Cause IEI | | | | | | | | octet 1 | +| Length of Discovery Reject Cause IE contents | | | | | | | | octet 2 | +| Discovery Reject Cause Value | | | | | | | | octet 3 | + +**Figure 11.2.12.1: Discovery Reject Cause information element****Table 11.2.12.1: Discovery Reject Cause information element** + +| Discovery Reject Cause (octet 3) | | | | +|----------------------------------|---|---|--------------------------| +| Bits | | | | +| 3 | 2 | 1 | | +| 0 | 0 | 0 | Network Congestion | +| 0 | 0 | 1 | Unspecified | +| 0 | 1 | 0 | IMSI not allowed | +| 1 | 0 | 0 | to | +| 1 | 1 | 1 | Reserved for future use. | + +### 11.2.13 GAN Cell Description + +The purpose of the *GAN Cell Description* information element is to provide a minimum description of a GAN A/Gb mode cell, e.g. to identify the GAN A/Gb mode cell in order to be handed over from GERAN/UTRAN. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| GAN Cell Description IEI | | | | | | | | octet 1 | +| Length of GAN Cell Description value contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [12], Cell Description IE, not including IEI and length, if present. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +Figure 11.2.13.1: **GAN Cell Description** information element + +### 11.2.14 GAN Control Channel Description + +The purpose of the *Control Channel Description* information element is to provide a variety of information about the GAN service. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +|----------------------------------------------------|--------|--------|--------|--------|--------|--------|--------|---------|--|--| +| GAN Control Channel Description IEI | | | | | | | | octet 1 | | | +| Length of GAN Control Channel Description contents | | | | | | | | octet 2 | | | +| MSCR | ATT | DTM | GPRS | NMO | ECMC | | spare | octet 3 | | | +| T3212 timeout value | | | | | | | | octet 4 | | | +| RAC | | | | | | | | octet 5 | | | +| spare | PS HO | 3GECS | PFCFM | RE | ECMP | SGSNR | | octet 6 | | | +| AC C15 | AC C14 | AC C13 | AC C12 | AC C11 | AC C10 | AC C09 | AC C08 | octet 7 | | | +| AC C07 | AC C06 | AC C05 | AC C04 | AC C03 | AC C02 | AC C01 | AC C00 | octet 8 | | | + +Figure 11.2.14.1: **GAN Control Channel Description** information element + +Table 11.2.14.1: **GAN Control Channel Description** information element + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

ECMC, Early Classmark Sending Control (octet 3)

Bit

2

0 Early Classmark Sending is allowed

1 Early Classmark Sending is forbidden

This field shall be disregarded in GAN lu mode.

| +|

NMO, Network Mode of Operation (octet 3)

Bit

4 3

0 0 Network Mode of Operation I

0 1 Network Mode of Operation II

1 0 Network Mode of Operation III (this value is not valid in GAN lu mode)

1 1 Reserved

| +|

GPRS, GPRS Availability (octet 3)

Bit

5

0 GPRS available

1 GPRS not available

This field shall be disregarded in GAN lu mode.

| +|

DTM, Dual Transfer Mode of Operation by network (octet 3)

Bit

6

0 Network does not support dual transfer mode

1 Network supports dual transfer mode

This field shall be disregarded in GAN lu mode.

| + +#### **ATT**, Attach-detach allowed (octet 3) + +Bit + +7 + +- 0 MSs in the cell are not allowed to apply IMSI attach and detach procedure. +- 1 MSs in the cell shall apply IMSI attach and detach procedure. + +#### **MSCR**, MSC Release (octet 3) + +Bit + +8 + +- 0 MSC is Release '98 or older +- 1 MSC is Release '99 onwards + +This field shall be disregarded in GAN lu mode. + +#### **T3212 timeout value** (octet 4) + +The T3212 timeout value field is coded as the binary representation of the timeout value for periodic updating in decihours. + +Range: 1 to 255 + +The value 0 is used for infinite timeout value i.e. periodic updating shall not be used within the cell. + +#### **RAC, Routing Area Code** (octet 5) + +This field is the binary representation of the Routing Area Code, see [3]. Bit 8 is the most significant bit and bit 1 is the least significant bit. + +#### **SGSNR**, SGSN Release (octet 6) + +Bit + +1 + +- 0 SGSN is Release '98 or older +- 1 SGSN is Release '99 onwards + +This field shall be disregarded in GAN lu mode. + +#### **ECMP**, Emergency Call Mode Preference (octet 6) + +Bit + +2 + +- 0 GERAN/UTRAN is preferred for Emergency calls +- 1 GAN is preferred for Emergency calls + +#### **RE**, Call re-establishment allowed (octet 6) + +Bit + +3 + +- 0 Call Re-establishment allowed in the cell +- 1 Call Re-establishment not allowed in the cell + +When call re-establishment is allowed, the mobile station may initiate call re-establishment if rove-in follows the RR/RRC connection failure in GSM/UMTS. + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PFCFM, PFC_FEATURE_MODE (octet 6)
Bit
4
0 The network does not support packet flow context procedures.
1 The network supports packet flow context procedures.
This field shall be disregarded in GAN Iu mode.

3GECS, 3G Early Classmark Sending Restriction (octet 6)
Bit
5
0 UTRAN classmark change message shall not be sent with the Early classmark sending
1 The sending of UTRAN Classmark Sending messages is controlled by the Early Classmark Sending Control parameter
This field shall be disregarded in GAN Iu mode.

PS HO, PS Handover indicator (octet 6)
Bit
6
0 The network does not support PS handover between GERAN/UTRAN mode and GAN A/Gb mode.
1 The network supports PS handover between GERAN/UTRAN mode and GAN A/Gb mode.
This field shall be disregarded in GAN Iu mode.

AC CN, Access Control Class N (octet 7 and octet 8)

These fields are specified and described in 3GPP TS 44.018 and 3GPP TS 22.011.

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.15 Cell Identifier List + +The Cell Identifier List information element is used to transfer multiple Cell Global Identifications in GAN. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| GAN Cell Identifier List IEI | | | | | | | | octet 1 | +| Length of GAN Cell Identifier List value contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [16], not including IEI and length, if present. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +Figure 11.2.15.1: **Cell Identifier List** information element + +NOTE: Cell identification discriminator "The whole Cell Global Identification, CGI" as defined in [16] shall be used. + +### 11.2.16 TU3907 Timer + +The purpose of this information element is to indicate to the MS the minimum period of time it should wait before attempting Registration at the current GANC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU3907 Timer IEI | | | | | | | | octet 1 | +| Length of TU3907 Timer IE contents | | | | | | | | octet 2 | +| TU3907 Timer value MSB | | | | | | | | octet 3 | +| TU3907 Timer value LSB | | | | | | | | octet 4 | + +Figure 11.2.16.1: **TU3907 Timer** information element + +**Table 11.2.16.1: TU3907 Timer information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +| TU3907 Timer value (octet 3 and 4) | +| In the TU3907 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. | +| The value is given in number of seconds. | +| The TU3907 Timer value consists of 2 octets. | + +### 11.2.17 GSM RR/UTRAN RRC State + +This information element is used to indicate the state of the GSM RR or UTRAN RRC entity when the MS is registering for GAN service. If GSM-RR is the current serving RR entity, information about GSM RR shall be included and if UTRAN-RRC is the current serving RR entity, information about UTRAN RRC shall be included. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------|---|---|---|---|---|-----|---|---------| +| GSM RR/UTRAN RRC State IEI | | | | | | | | octet 1 | +| Length of GSM RR/ UTRAN RRC State contents | | | | | | | | octet 2 | +| spare | | | | | | GRS | | octet 3 | + +**Figure 11.2.17.1 GSM RR/UTRAN RRC State information element****Table 11.2.17.1: GSM RR/UTRAN RRC State information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GRS, GSM RR/UTRAN RRC State (octet 3)
Bits 1-3 | +| 0 0 0 GSM RR is in IDLE state.
0 0 1 GSM RR is in DEDICATED state.
0 1 0 UTRAN RRC is in IDLE STATE
0 1 1 UTRAN RRC is in CELL_DCH STATE
1 0 0 UTRAN RRC is in CELL_FACH STATE
1 0 1 UTRAN RRC is in CELL_PCH STATE
1 1 0 UTRAN RRC is in URA_PCH STATE
1 1 1 Unknown | +| All other values are reserved for future use. | + +### 11.2.18 Routing Area Identification + +The purpose of the *routing area identification* information element is to provide an unambiguous identification of routing areas within the GPRS coverage area. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------|---|---|---|---|---|---|---|---------| +| Routing Area Identification IEI | | | | | | | | octet 1 | +| Length of Routing Area Identification contents | | | | | | | | octet 2 | +| The rest of the IE is coded as in [8] not including IEI and length, if present. | | | | | | | | octet 3 | +| .... | | | | | | | | octet 8 | + +**Figure 11.2.18.1: Routing Area Identification information element** + +### 11.2.19 GAN Band + +The GAN Band information element is used to indicate to the mobile station the GSM Band that is associated with the GANC. The mobile station uses this information to construct the MS Classmark 2 information element. The GAN Band is applicable in GAN A/Gb mode only. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------|---|---|---|----------|---|---|---|---------| +| GAN Band IEI | | | | | | | | octet 1 | +| Length of GAN Band contents | | | | | | | | octet 2 | +| spare | | | | GAN Band | | | | octet 3 | + +**Figure 11.2.19.1: GAN Band information element** + +**Table 11.2.19.1: GAN Band information element** + +GAN Band (4 bit field) + This field indicates the band applicable for the parameters in this structure. + +Bits 4 - 1 + 4 3 2 1 + +0 0 0 0 E-GSM is supported + 0 0 0 1 P-GSM is supported + 0 0 1 0 GSM 1800 is supported + 0 0 1 1 GSM 450 is supported + 0 1 0 0 GSM 480 is supported + 0 1 0 1 GSM 850 is supported + 0 1 1 0 GSM 1900 is supported + 0 1 1 1 GSM 700 is supported + +All other values are reserved for future use and shall not be interpreted as an error. + +### 11.2.20 GAN State + +This information element is used to indicate the state of the GAN protocol sub-layer entities in the MS to the GANC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|---|-----------|-----------|-----|-----|---------| +| GAN State IEI | | | | | | | | octet 1 | +| Length of GAN State contents | | | | | | | | octet 2 | +| spare | | | | GA-RRC-PS | GA-RRC-CS | UPS | URS | octet 3 | + +**Figure 11.2.20.1 GAN State information element** + +**Table 11.2.20.1: GAN State information element** + +| | | +|-----------------------------------------------|------------------------------------------------------------------| +| URS, GA-RC/GA-CSR State (octet 3)
Bits 2-1 | | +| 2 1 | | +| 0 0 | GA-CSR is in GA-CSR-IDLE state. | +| 0 1 | GA-CSR is in GA-CSR-DEDICATED state. | +| 1 0 | GA-RC is in GA-RC-REGISTERED state
while in GERAN/UTRAN mode. | +| UPS, GA-PSR State (octet 3)
Bit | | +| 3 | | +| 0 | GA-PSR is in GA-PSR-STANDBY state. | +| 1 | GA-PSR is in GA-PSR-ACTIVE state. | +| GA-RRC-CS, GA-RRC (CS) State (octet 3)
Bit | | +| 4 | | +| 0 | GA-RRC (CS) is in GA-RRC-IDLE state. | +| 1 | GA-RRC (CS) is in GA-RRC-CONNECTED
state. | +| GA-RRC-PS, GA-RRC (PS) State (octet 3)
Bit | | +| 5 | | +| 0 | GA-RRC (PS) is in GA-RRC-IDLE state. | +| 1 | GA-RRC (PS) is in GA-RRC-CONNECTED
state. | + +### 11.2.21 Register Reject Cause + +This information element contains the reason for Register reject or deregistration. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------|---|---|---|---|---|---|---|---------| +| Register Reject Cause IEI | | | | | | | | octet 1 | +| Length of Register Reject Cause IE contents | | | | | | | | octet 2 | +| RRC | | | | | | | | octet 3 | + +**Figure 11.2.21.1: Register Reject Cause information element****Table 11.2.21.1: Register Reject Cause information element** + +| Register Reject Cause (octet 3) | | +|---------------------------------|---------------------------------| +| 0 | Network Congestion | +| 1 | AP not allowed | +| 2 | Location not allowed | +| 3 | Invalid GANC | +| 4 | Geo Location not known | +| 5 | IMSI not allowed | +| 6 | Unspecified | +| 7 | GANC-SEGW certificate not valid | +| 8 | EAP_SIM authentication failed | +| 9 | TCP establishment failed | +| 10 | Redirection | +| 11 | EAP-AKA Authentication failed | +| 12 to 255 | Reserved for future use. | + +### 11.2.22 TU3906 Timer + +The TU3906 Timer information element contains the value for the GA-RC Keep Alive mechanism, as described in section 5.5. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU3906 Timer IEI | | | | | | | | octet 1 | +| Length of TU3906 Timer IE contents | | | | | | | | octet 2 | +| TU3906 Timer value MSB | | | | | | | | octet 3 | +| TU3906 Timer value LSB | | | | | | | | octet 4 | + +**Figure 11.2.22.1: TU3906 Timer information element** + +**Table 11.2.22.1: TU3906 Timer information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +| TU3906 Timer value (octet 3 and 4) | +| In the TU3906 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. | +| The value is given in number of seconds. | +| The TU3906 Timer value consists of 2 octets. | + +### 11.2.23 TU3910 Timer + +When the MS roves out, it shall start timer TU3910 and shall not rove in until this timer has expired, unless the MS has detected loss of GERAN coverage. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU3910 Timer IEI | | | | | | | | octet 1 | +| Length of TU3910 Timer IE contents | | | | | | | | octet 2 | +| TU3910 Timer value MSB | | | | | | | | octet 3 | +| TU3910 Timer value LSB | | | | | | | | octet 4 | + +**Figure 11.2.23.1: TU3910 Timer information element** + +**Table 11.2.23.1: TU3910 Timer information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +| TU3910 Timer (octet 3 and 4) | +| In the TU3910 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. | +| The value is given in number of seconds. | +| The TU3910 value consists of 2 octets. | + +### 11.2.24 TU3902 Timer + +The purpose of this information element is to indicate to the MS the minimum period of time it should wait before attempting the Discovery procedure again. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU3902 Timer IEI | | | | | | | | octet 1 | +| Length of TU3902 Timer IE contents | | | | | | | | octet 2 | +| TU3902 Timer value MSB | | | | | | | | octet 3 | +| TU3902 Timer value LSB | | | | | | | | octet 4 | + +**Figure 11.2.24.1: TU3902 Timer information element** + +**Table 11.2.24.1: TU3902 Timer information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +| TU3902 Timer value (octet 3 and 4) | +| In the TU3902 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. | +| The value is given in number of seconds. | +| The TU3902 Timer value consists of 2 octets. | + +### 11.2.25 Communication Port Identity + +The Communication Port Identity information element is used to identify the TCP or UDP port for the connection. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------|---|---|---|---|---|---|---|---------| +| Communication Port Identity IEI | | | | | | | | octet 1 | +| Length of Communication Port Identity IE contents | | | | | | | | octet 2 | +| Communication Port MSB value | | | | | | | | octet 3 | +| Communication Port LSB value | | | | | | | | octet 4 | + +**Figure 11.2.25.1: Communication Port information element** + +Even though it is only recommended in [35], RTP shall use an even destination UDP port number and the corresponding RTCP stream shall use the next higher (odd) destination UDP port number. E.g. UDP ports 49170 and 49171 form one RTP/RTCP UDP port pair. + +### 11.2.26 L3 Message + +The L3 Message information element contains the upper layer message to be transported using the GA-CSR protocol or the GA-RRC protocol between the MS and the core network. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|---|---|---|---|---|---|---|-------------| +| L3 Message IEI | | | | | | | | octet 1 | +| Length of L3 Message IE contents | | | | | | | | octet 2, 2a | +| L3 Message contents, 1st octet | | | | | | | | octet 3 | +| ... | | | | | | | | ... | +| L3 Message contents, last octet | | | | | | | | octet n | + +**Figure 11.2.26.1: L3 Message information element** + +### 11.2.27 Channel Mode + +The *Channel Mode* information element gives information of the mode on coding/decoding and transcoding. The exact mode is determined by the contents of this IE and the channel type. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Channel Mode IEI | | | | | | | | octet 1 | +| Length of Channel Mode IE contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [12], not including IEI and length, if present. | | | | | | | | octet 3 | +| ... | | | | | | | | ... | +| | | | | | | | | octet n | + +**Figure 11.27.1: Channel Mode information element** + +NOTE 1: Support for AMR FR codec, as specified in 3GPP TS 26.071 [7], is mandatory when operating in GAN A/Gb mode, with support for other codecs being optional. + +### 11.2.28 Mobile Station Classmark 2 + +The purpose of the *Mobile Station Classmark 2* information element is to provide the network with information concerning aspects of both high and low priority of the mobile station equipment. This affects the manner in which the network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on. + +![](38a51baf4d5b8857d162e5d9a0645269_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------------|---|---|---|---|---|---|---|----------------------------| +| Mobile station classmark 2 IEI | | | | | | | | octet 1 | +| Length of mobile station classmark 2 contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [8], not including IEI and length, if present. | | | | | | | | octet 3
....
octet n | + +Figure 11.2.28.1: Mobile Station Classmark 2 information element + +### 11.2.29 RR Cause + +The purpose of the *RR Cause* information element is to provide the reason for release or the reason for completion of an assignment or handover. + +![](854cb86f664ff62fd23e7607cfeb5727_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|----------------------------| +| RR Cause IEI | | | | | | | | octet 1 | +| Length of RR Cause contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [12], not including IEI and length, if present. | | | | | | | | octet 3
....
octet n | + +Figure 11.2.29.1: RR Cause information element + +### 11.2.30 Cipher Mode Setting + +The purpose of the *Cipher Mode Setting* information element is to indicate whether stream ciphering shall be started or not and if it is to be started, which algorithm to use. It is not used for ciphering when the MS is in GAN A/Gb mode or GAN Iu mode, but after handover from GAN A/Gb mode in the target RAT. + +![](54bf8ae3f6e425085a2ce5fbb2c56267_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------|---|---|---|----------------------|---|---|----|---------| +| Cipher Mode Setting IEI | | | | | | | | octet 1 | +| Length of Cipher Mode Setting IE contents | | | | | | | | octet 2 | +| spare | | | | algorithm identifier | | | SC | octet 3 | + +Figure 11.2.30.1: Cipher Mode Setting information element + +NOTE: The coding of fields SC and algorithm identifier is defined in [12] as part of the Cipher Mode Setting IE. + +### 11.2.31 GPRS Resumption + +The purpose of the *GPRS Resumption* information element is to indicate whether the network has successfully resumed GPRS services or not. + +![](77542b335b92de8277e86dbe7190f361_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|----------------------------| +| GPRS Resumption IEI | | | | | | | | octet 1 | +| Length of GPRS Resumption contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [12], not including IEI and length, if present. | | | | | | | | octet 3
....
octet n | + +Figure 11.2.31.1: GPRS Resumption information element + +### 11.2.32 Handover From GAN Command + +The purpose of Handover From GAN Command information element is to provide information to the MS of handover from GAN. The Handover From GAN Command information element contains all information needed by the MS for handover from GAN. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Handover from GAN Command IEI | | | | | | | | octet 1 | +| Length of Handover from GAN Command value contents | | | | | | | | octet 2, 2a | +| If the target RAT is GERAN, the rest of the IE is coded as HANDOVER COMMAND message in [12]. If the target RAT is UTRAN, the rest of the IE is coded as INTER SYSTEM TO UTRAN HANDOVER COMMAND message in [12]. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +Figure 11.2.32.1: Handover From GAN Command information element + +### 11.2.33 UL Quality Indication + +This information element provides an indication to the MS that the GAN has detected insufficient signal quality on the uplink or is unable to support the service on the broadband network, thereby requiring the MS to trigger a Handover by providing the necessary information regarding the potential target cells in the other RAT. Handover from GAN can be triggered by GAN only if the MS has indicated presence of GSM coverage previously in the Register or Register Update messages. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|------|---|---|---|---------| +| UL Quality Indication IEI | | | | | | | | octet 1 | +| Length of UL Quality Indication contents | | | | | | | | octet 2 | +| spare | | | | ULQI | | | | octet 3 | + +Figure 11.2.33.1: UL Quality Indication information element + +Table 11.2.33.1: UL Quality Indication information element + +| ULQI, UL Quality Indication (octet 3) | | | | | +|-------------------------------------------|---|---|---|----------------------| +| Bits | | | | | +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | Quality ok | +| 0 | 0 | 0 | 1 | Radio problem | +| 0 | 0 | 1 | 0 | Network problem | +| 0 | 1 | 0 | 0 | Undetermined problem | +| Other values are reserved for future use. | | | | | + +### 11.2.34 TLLI + +The purpose of the *TLLI* information element is to provide the Temporary Logical Link Identifier. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| TLLI IEI | | | | | | | | octet 1 | +| Length of TLLI value contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [12], not including IEI and length, if present. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +Figure 11.2.34.1: TLLI information element + +### 11.2.35 Packet Flow Identifier + +The *Packet Flow Identifier (PFI)* information element indicates the Packet Flow Identifier for a Packet Flow Context. + +![](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Packet Flow Identifier IEI | | | | | | | | octet 1 | +| Length of Packet Flow Identifier value contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [8], not including IEI and length, if present. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +**Figure 11.2.35.1: Packet Flow Identifier information element** + +### 11.2.36 Suspension Cause + +The purpose of the *Suspension Cause* information element is to provide the reason for the GPRS suspension. + +![](708e4c9a044ef61f586126676eb2eeb8_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Suspension Cause IEI | | | | | | | | octet 1 | +| Length of Suspension Cause value contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [12], not including IEI and length, if present. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +**Figure 11.2.36.1: Suspension Cause information element** + +### 11.2.37 TU3920 Timer + +The purpose of this information element is to indicate to the MS the maximum period of time it should wait before aborting the Handover to GAN (A/Gb mode or Iu mode) procedure. + +![](4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU3920 Timer IEI | | | | | | | | octet 1 | +| Length of TU3920 Timer IE contents | | | | | | | | octet 2 | +| TU3920 Timer value MSB | | | | | | | | octet 3 | +| TU3920 Timer value LSB | | | | | | | | octet 4 | + +**Figure 11.2.37.1: TU3920 Timer information element** + +**Table 11.2. 37.1: TU3920 Timer information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +| TU3920 Timer value (octet 3 and 4) | +| In the TU3920 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. | +| The value is given in number of hundreds of milliseconds. | +| The TU3920 Timer value consists of 2 octets. | + +### 11.2.38 QoS + +This information element indicates the QoS Profile associated with a PDU. + +![](bde7d337de2e08bf548b40ef6a35ae33_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|-----------------|--------------------|---|-----------------------|---|---|---|---------| +| QoS IEI | | | | | | | | octet 1 | +| Length of QoS value contents | | | | | | | | octet 2 | +| spare | RLC
MOD
E | RADIO_PRIO
RITY | | PEAK_THROUGHPUT_CLASS | | | | octet 3 | + +**Figure 11.2.38.1: QoS information element** + +**Table 11.2.38.1: QoS information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

PEAK_THROUGHPUT_CLASS (octet 3, bits 1-4)

This field is coded as PEAK_THROUGHPUT_CLASS field in the Channel Request Description information element specified in [45]

RADIO_PRIORITY (octet 3, bits 5-6)

This field is coded as RADIO_PRIORITY field in the Channel Request Description information element specified in [45]

RLC_MODE (octet 3, bit 7)

This field is coded as RLC_MODE field in the Channel Request Description information element specified in [45]

.

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.39 GA-PSR Cause + +This information element indicates the status related to GAN specific signalling procedures. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------|---|---|---|---|---|---|---|---------| +| GA-PSR Cause IEI | | | | | | | | octet 1 | +| Length of GA-PSR Cause value contents | | | | | | | | octet 2 | +| GA-PSR Cause value | | | | | | | | octet 3 | + +**Figure 11.2.39.1: GA-PSR Cause information element****Table 11.2.39.1 GA-PSR Cause value** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

GA-PSR Cause (octet 3)

Value

0 "success"

2 "no available resources"

3 "GANC failure"

4 "not authorized for data service"

5 "message type non existent or not implemented"

6 "message type not compatible with the protocol state"

7 "invalid mandatory information"

8 "syntactically incorrect message"

9 "GPRS suspended"

10 "normal deactivation"

12 "conditional IE error"

13 "semantically incorrect message"

14 "PS handover failure - incorrect handover command"

15 "PS handover failure - target RAT access failure"

16 "PS handover failure - missing SI/PSI information"

17 "PS handover failure - no uplink TBF allocation"

All other values are for future use.

| +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.40 User Data Rate + +This information element indicates the User Data Rate used in flow control procedures: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------|---|---|---|---|---|---|---|---------| +| User Data Rate IEI | | | | | | | | octet 1 | +| Length of User Data Rate value contents | | | | | | | | octet 2 | +| R Value (MSB) | | | | | | | | octet 3 | +| | | | | | | | | octet 4 | +| R Value (LSB) | | | | | | | | octet 5 | + +Figure 11.2.40.1: User Data Rate IE + +Table 11.2.40.1: User Data Rate IE + +R value (octets 3, 4 and 5) + +In the R value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 5 the least significant bit. + +The R field is the binary encoding of the rate information expressed in 100 bits/sec increments, starting from 0 x 100 bits/sec until 16777215 x 100 bits/sec (1.6 Gbps). + +### 11.2.41 Routing Area Code + +The purpose of the *Routing Area Code IE* is to provide an unambiguous identification of routing areas within a location area. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------|---|---|---|---|---|---|---|---------| +| Routing Area Code IEI | | | | | | | | octet 1 | +| Length of the Routing Area Code value contents | | | | | | | | octet 2 | +| The rest of the IE is coded as in [3] not including IEI and length, if present. | | | | | | | | octet 3 | + +Figure 11.2.41.1: Routing Area Code information element + +### 11.2.42 AP Location + +The AP Location information element is to indicate the location of the MS or AP to the network. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| AP Location IEI | | | | | | | | octet 1 | +| Length of AP Location contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [25], not including IEI and length, if present. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +Figure 11.2.42.1: AP Location information element + +### 11.2.43 TU4001 Timer + +The purpose of this information element is to indicate to the MS the minimum period of time it should wait before deactivating an idle GAN A/Gb mode GA-PSR Transport Channel or GAN Iu mode Packet Transport Channel. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU4001 Timer IEI | | | | | | | | octet 1 | +| Length of TU4001 Timer IE contents | | | | | | | | octet 2 | +| TU4001 Timer value MSB | | | | | | | | octet 3 | +| TU4001 Timer value LSB | | | | | | | | octet 4 | + +Figure 11.2.43.1: TU4001 Timer information element + +**Table 11.2.43.1: TU4001 Timer information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +| TU4001 Timer value (octet 3 and 4) | +| In the TU4001 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. | +| The value is given in number of seconds. | +| The TU4001Timer value consists of 2 octets. | + +### 11.2.44 Location Status + +This information element indicates whether the GANC is able to identify the location for the specific MS. Based on network or operator policy, the network may accept a Registration Request from a MS, even if the location of the MS (or AP) is not known in the network. This IE may be used by the MS to provide an indication to the user as to whether the MS's location is known. + +![](91c33f8e1713989e8192322ec2d1212b_img.jpg) + +| | | | | | | | | | +|------------------------------------------|---|---|---|----|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Location Status IEI | | | | | | | | octet 1 | +| Length of Location Status value contents | | | | | | | | octet 2 | +| spare | | | | LS | | | | octet 3 | + +**Figure 11.2.44.1 Location Status information element****Table 11.2.44.1: Location Status information element** + +| | +|-------------------------------------| +| LS, Location Status (octet 3) | +| Bit | +| 2 1 | +| 0 0 MS location known | +| 0 1 MS location unknown | +| All other value are for future use. | + +### 11.2.45 Cipher Response + +The purpose of the *Cipher Response* information element is to indicate to the mobile station which information the mobile station has to include in the GA-CSR CIPHERING MODE COMPLETE message. + +![](a2586540d49d5665489c8b5a273f86d3_img.jpg) + +| | | | | | | | | | +|------------------------------------|---|---|---|----|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Cipher Response IEI | | | | | | | | octet 1 | +| Length of Cipher Response contents | | | | | | | | octet 2 | +| spare | | | | CR | | | | octet 3 | + +**Figure 11.2.45.1: Cipher Response information element****Table 11.2.45.1: Cipher Response information element** + +| | +|--------------------------------| +| CR Cipher Response (octet 3) | +| Bit | +| 1 | +| 0 IMEISV shall not be included | +| 1 IMEISV shall be included | + +### 11.2.46 Ciphering Command RAND + +The Ciphering Command RAND information element contains the random number to be used for computing the MAC by the MS, to authenticate that the MS has the correct key Kc. + +| | | +|-------------------------------------------|----------| +| Ciphering Command RAND IEI | octet 1 | +| Length of Ciphering Command RAND contents | octet 2 | +| Ciphering Command RAND value part | octet 3 | +| | .... | +| | octet 18 | + +**Figure 11.2.46.1: Ciphering Command RAND information element** + +The GANC generates the random number using the same pseudo-random function as first cryptographic suite as defined in the profile for IKEv2 in [37]. + +### 11.2.47 Ciphering Command MAC + +The Ciphering Command MAC information element contains the Message Authentication Code computed by the MS, to authenticate that the MS has the correct key Kc. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|----------| +| Ciphering Command MAC IEI | | | | | | | | octet 1 | +| Length of Ciphering Command MAC contents | | | | | | | | octet 2 | +| Ciphering Command MAC value part | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet 14 | + +**Figure 11.2.47.1: Ciphering Command MAC information element** + +The MAC is computed as defined in sub-clause 7.9.2. + +### 11.2.48 Ciphering Key Sequence Number + +The purpose of the *Ciphering Key Sequence Number* information element is to make it possible for the network to identify the ciphering key Kc which is stored in the mobile station without invoking the authentication procedure. + +The ciphering key sequence number is allocated by the network and sent with the AUTHENTICATION REQUEST message to the mobile station where it is stored together with the calculated ciphering key Kc. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|--------------|---|---|---|---------| +| Ciphering Key Sequence IEI | | | | | | | | octet 1 | +| Length of Ciphering Key Sequence IE contents | | | | | | | | octet 2 | +| spare | | | | Key sequence | | | | octet 3 | + +**Figure 11.2.48.1: Ciphering Key Sequence Number information element** + +**Table 11.2.48.1: Ciphering Key Sequence Number information element** + +| Key sequence (octet 3) | | | +|--------------------------------------|---|---------------------------------------| +| Bits | | | +| 3 | 2 | 1 | +| 0 | 0 | 0 | +| through | | Possible values for the ciphering key | +| 1 | 1 | 0 | +| sequence number | | | +| 1 | 1 | 1 | +| No key is available (MS to network); | | Reserved (network to MS) | + +### 11.2.49 SAPI ID + +The SAPI ID IE is used by the MS to indicate the SAPI value for the upper layer message. + +![](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +| | | | | | | | | | +|-------------------------------|---|---|---|---------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| SAPI ID IEI | | | | | | | | octet 1 | +| Length of SAPI ID IE contents | | | | | | | | octet 2 | +| spare | | | | SAPI ID | | | | octet 3 | + +Figure 11.2.49.1: SAPI ID information element + +Table 11.2.49.1: SAPI ID information element + +| | | | | +|----------------------------------------------|----------|----------|-------------------------------| +| SAPI ID, SAPI Identifier (octet 3) | | | | +| Bits | | | | +| 3 | 2 | 1 | | +| 0 | 0 | 0 | SAPI 0 (all other except SMS) | +| 0 | 1 | 1 | SAPI 3 (SMS) | +| All other values are undefined in Release 1. | | | | + +### 11.2.50 Establishment Cause + +The Establishment Cause IE is used by the MS to indicate the type of the transaction being initiated to the network. + +![](bb3063a33c89b248574f64b6d8dfc404_img.jpg) + +| | | | | | | | | | +|-------------------------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Establishment Cause IEI | | | | | | | | octet 1 | +| Length of Establishment Cause IE contents | | | | | | | | octet 2 | +| Establishment Cause | | | | | | | | octet 3 | + +Figure 11.2.50.1: Establishment Cause information element + +Table 11.2.50.1: Establishment Cause information element + +| | | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Establishment Cause (octet 3) | | +| Bits 8 ... 1 | | +| 1010 0000 | Emergency | +| 1100 0000 | Call re-establishment | +| 0000 0000 | Location Update | +| 0001 0000 | Other SDCCH procedures including IMSI Detach, SMS, SS, paging response
// note: Paging response for "SDCCH needed" is using codepoint "0001 0000" | +| 0010 0000 | Paging response (TCH/F needed) | +| 0011 0000 | Paging response (TCH/F or TCH/H needed) | +| 1000 0000 | Paging response ("any channel" needed) | +| 0100 0000 | Originating speech call from dual-rate mobile station when TCH/H is sufficient | +| 0101 0000 | Originating data call from dual-rate mobile station when TCH/H is sufficient | +| 1110 0000 | Originating speech call and TCH/F is needed | +| 1111 0000 | Originating data call and TCH/F is needed | +| All other values are undefined in Release 1. | | + +### 11.2.51 Channel Needed + +The Channel Needed IE is equivalent to the Channel Needed IE specified in [12] and is coded as per following definition: + +![](0549ab3c68ad94e7e1bb6ec6aa6b5373_img.jpg) + +| | | | | | | | | | +|--------------------------------------|---|---|---|-----------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Channel Needed IEI | | | | | | | | octet 1 | +| Length of Channel Needed IE contents | | | | | | | | octet 2 | +| spare | | | | CHANNEL (first) | | | | octet 3 | + +Figure 11.2.51.1: Channel Needed information element + +**Table 11.2.51.1: Channel Needed information element** + +| | | | +|-------------------|---|-----------------------------| +| CHANNEL (octet 3) | | | +| Bits | | | +| 2 | 1 | | +| 0 | 0 | Any channel. | +| 0 | 1 | SDCCH. | +| 1 | 0 | TCH/F (Full rate). | +| 1 | 1 | TCH/H or TCH/F (Dual rate). | + +### 11.2.52 PDU in Error + +The PDU in Error IE contains a faulty message returned to the sender of the message. + +![](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|---|---|---|---|-------------| +| PDU in Error IEI | | | | | | | | octet 1 | +| Length of PDU in Error contents | | | | | | | | octet 2, 2a | +| PDU in Error, 1st octet | | | | | | | | octet 3 | +| ... | | | | | | | | | +| PDU in Error, last octet | | | | | | | | octet n | + +**Figure 11.2.52.1: PDU in Error information element** + +NOTE: If the faulty message included in the *PDU in Error* IE is larger than 255 octets then only the first 255 octets of the message are to be included and the *Length of the PDU in Error* field shall indicate that 255 octets are included. + +### 11.2.53 Sample Size + +The Sample Size IE is used by the network to indicate the minimum size of the CS payload frames to be included in each RTP/UDP packet. It is also used by the MS to indicate to the network the sample size used by the MS and to be applied by the network in the downlink. + +![](3dea2a7c8e1120f769d0bc8ee347340d_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------|---|---|---|---|---|---|---|---------| +| Sample Size IEI | | | | | | | | octet 1 | +| Length of Sample Size IE contents | | | | | | | | octet 2 | +| Sample Size | | | | | | | | octet 3 | + +**Figure 11.2.53.1: Sample Size information element****Table 11.2.53.1: Sample Size information element** + +| | | +|----------------------------------------------|-----------------------------------------------------| +| Sample Size (octet 3) | | +| 20 | 20 ms of CS payload included in each RTP/UDP packet | +| 40 | 40 ms of CS payload included in each RTP/UDP packet | +| 60 | 60 ms of CS payload included in each RTP/UDP packet | +| 80 | 80 ms of CS payload included in each RTP/UDP packet | +| All other values are undefined in Release 1. | | + +### 11.2.54 Payload Type + +The Payload Type IE is used to indicate the RTP Payload Type for dynamically assigned Payload Type. + +![](19127cc2db2eb92d1134a2244b47cddc_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| Payload Type IEI | | | | | | | | octet 1 | +| Length of Payload Type IE contents | | | | | | | | octet 2 | +| Payload Type | | | | | | | | octet 3 | + +**Figure 11.2.54.1: Payload Type information element** + +**Table 11.2.54.1: Payload Type information element** + +| | +|----------------------------------------------| +| Payload Type (octet 3) | +| Allowed values are between 96 and 127. | +| All other values are undefined in Release 1. | + +### 11.2.55 Multirate Configuration + +The *MultiRate configuration* information element gives parameters related to the multi-rate speech codec used in GAN A/Gb mode. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Multirate Configuration IEI | | | | | | | | octet 1 | +| Length of Multirate Configuration contents | | | | | | | | octet 2, 2a | +| The rest of the IE, except the Threshold and Hysteresis values, is coded as in [12], not including IEI and length, if present. The included Threshold and Hysteresis values shall be coded according to Table 11.2.55.1 and Annex D.1. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +**Figure 11.2.55.1: Multirate Configuration information element** + +**Table 11.2.55.1: MultiRate configuration information element** + +| Octet 3 - n | | | | +|-------------|------------------|------------|------------------| +| Threshold | | Hysteresis | | +| value | Frame Loss Ratio | value | Frame Loss Ratio | +| 0 | = 0 % | 0 | = 0 % | +| 1 | = 0.25 % | 1 | = 0.25 % | +| ... | | 2 | = 0.5 % | +| 19 | = 4.75 % | 3 | = 0.75 % | +| 20 | = 5 % | 4 | = 1 % | +| 21 | = 5.5 % | 5 | = 1.5 % | +| ... | | 6 | = 2 % | +| 39 | = 14.5 % | 7 | = 2.5 % | +| 40 | = 15 % | 8 | = 3 % | +| 41 | = 16 % | 9 | = 4 % | +| ... | | 10 | = 5 % | +| 50 | = 25 % | 11 | = 6 % | +| 51 | = 26 % | 12 | = 8 % | +| 52 | = 28 % | 13 | = 10 % | +| ... | | 14 | = 13 % | +| 62 | = 48 % | 15 | = 17 % | +| 63 | = 50 % | | | + +The Frame Loss Ratio (FLR) is the number of missing speech frames at the receiver, divided by the total number of expected speech frames for the speech signal during the actual measurement period. When there are redundant speech frames, these shall also be counted both when missing and as included in the complete speech signal respectively. In missing RTP packets, the number of redundant speech frames shall be assumed to follow the used RTP Redundancy Configuration and the latest Codec Mode Request value, CMR, signalled to the sending part. (For CMR, see annex A.) For example, when RTP sample size is 20 ms, single redundancy is used and two RTP packets are missing during the last second, the frame loss ratio is $(2+2)/(2*50) = 4\%$ . + +A filter shall be applied to the frame loss ratio before comparing it with the threshold and hysteresis values according to Annex D.1. + +### 11.2.56 Mobile Station Classmark 3 + +The purpose of the *Mobile Station Classmark 3* information element is to provide the network with information concerning aspects of the mobile station. The contents might affect the manner in which the network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on. + +![](78de09c382ab51b5c3e87979204228c8_img.jpg) + +| | | | +|----------------------------------------------------------------------------------|--|-------------| +| 8      7      6      5      4      3      2      1 | | | +| Mobile station classmark 3 IEI | | octet 1 | +| Length of mobile station classmark 3 contents | | octet 2, 2a | +| The rest of the IE is coded as in [8], not including IEI and length, if present. | | octet 3 | +| | | .... | +| | | octet n | + +**Figure 11.2.56.1: Mobile Station Classmark 3 information element** + +### 11.2.57 LLC-PDU + +This information element contains an LLC-PDU. The element coding is: + +![](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| LLC-PDU IEI | | | | | | | | octet 1 | +| Length of LLC-PDU contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as in [19], not including IEI and length, if present. | | | | | | | | octet 3 | +| .... | | | | | | | | .... | +| | | | | | | | | octet n | + +**Figure 11.2.57.1: LLC-PDU information element** + +### 11.2.58 Location Black List indicator + +The Location Black List indicator information element is used to indicate which part of the Location Area Identification is to be added in the Location Black List. + +![](20809e79dee38f3d6e03e1ad565a9cf5_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------|---|---|---|---|------|---|---|---------| +| Location Black List indicator IEI | | | | | | | | octet 1 | +| Length of Location Black List indicator contents | | | | | | | | octet 2 | +| spare | | | | | LBLI | | | octet 3 | + +**Figure 11.2.58.1: Location Black List indicator information element** + +**Table 11.2.58.1: Location Black List indicator information element** + +| | | | | +|-----------------------------------------------|----------|----------|------------------| +| LBLI, Location Black List indicator (octet 3) | | | | +| Bits | | | | +| 3 | 2 | 1 | | +| 0 | 0 | 0 | MCC | +| 0 | 0 | 1 | MCC and MNC | +| 0 | 1 | 0 | MCC, MNC and LAC | +| All other values are undefined in Release 1. | | | | + +### 11.2.59 Reset Indicator + +The Reset Indicator information element is used to signal to the MS when the flow control procedure is complete and the MS can reset the maximum uplink data rate to normal level. + +![](0bdf45f8598420cf51abdd73300adc83_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|----|---------| +| Reset Indicator IEI | | | | | | | | octet 1 | +| Length of Reset Indicator contents | | | | | | | | octet 2 | +| spare | | | | | | | RI | octet 3 | + +**Figure 11.2.59.1 Reset Indicator information element** + +**Table 11.2.59.1: Reset Indicator information element** + +| | | +|-------------------------------|-------------------------------------------------| +| RI, Reset Indicator (octet 3) | | +| Bit | | +| 1 | | +| 0 | The flow control condition continues to exist.. | +| 1 | The flow control condition no longer exists. | + +### 11.2.60 TU4003 Timer + +The purpose of this information element is to indicate to the MS how often it is allowed to send flow control messages. In case of CS traffic channel is activated or released or in case of GA-CSR state transition, MS is allowed to update Flow Control condition by sending GA-PSR-DFC-REQ message while TU4003 is running. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU4003 Timer IEI | | | | | | | | octet 1 | +| Length of TU4003 Timer IE contents | | | | | | | | octet 2 | +| TU4003 Timer value MSB | | | | | | | | octet 3 | +| TU4003 Timer value LSB | | | | | | | | octet 4 | + +**Figure 11.2.60.1: TU4003 Timer information element** + +**Table 11.2.60.1: TU4003 Timer information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------| +| TU4003 Timer value (octet 3 and 4) | +| In the TU4003 Timer value field bit 8 of octet 3 is the most significant bit and bit 1 of octet 4 the least significant bit. | +| The value is given in number of seconds. | +| The TU4003 Timer value consists of 2 octets. | + +### 11.2.61 AP Service Name + +The AP Service Name element contains either the SSID or the PAN Service Name of the unlicensed AP being used. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------|---|---|---|---|---|---|---|-------------| +| AP Service Name IEI | | | | | | | | octet 1 | +| Length of AP Service Name IE contents | | | | | | | | octet 2, 2a | +| AP Service Name type | | | | | | | | octet 3 | +| AP Service Name MSB | | | | | | | | octet 4 | +| ... | | | | | | | | ... | +| AP Service Name LSB | | | | | | | | octet n | + +**Figure 11.2.61.1: AP Service Name information element** + +**Table 11.2.61.1: AP Service Name information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AP Service Name type number value (octet 3) | +| Bits | +| 8 7 6 5 4 3 2 1 | +| 0 0 0 0 0 0 0 1 SSID | +| 0 0 0 0 0 0 1 0 PAN Service Name | +| All other values are undefined in Release 1. | +| AP Service Name value (octet 4 to octet n) | +| The AP Service Name is coded as a string according to UTF-8 format defined in RFC 3629 [50]. This means that the 1 st octet of the UTF-8 string is coded in octet 4 and the last octet of the UTF-8 string is coded in the last octet of this IE (octet n). | + +### 11.2.62 GAN Service Zone Information + +The purpose of the *GAN Service Zone Information* information element is to provide the mobile station with GAN Service Zone related information applicable to the current location of the user. It consists of two fields. *GAN Service Zone Name* string can be used by the GANC to indicate textual information related to the location. *GAN Service Zone Icon Indicator* can be used by the GANC to turn on various indicators in the mobile station. + +| | | +|-------------------------------------------------------|-------------| +| GAN Service Zone Information IEI | octet 1 | +| Length of GAN Service Zone Information value contents | octet 2, 2a | +| GAN Service Zone Icon Indicator | octet 3 | +| Length of GAN Service Zone string | octet 4 | +| GAN Service Zone string, 1 st character | octet 5 | +| | | +| GAN Service Zone string, last character | octet n | + +**Figure 11.2.62.1: GAN Service Zone Information information element** + +**Table 11.2.62.1: GAN Service Zone Information information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GAN Service Zone Icon Indicator, octet 3 | +| Value | +| 1 Unlimited Calls | +| 128-254 Operator specific values | +| All other values are reserved. | +| GAN Service Zone Name, octets 4-n | +| Octet 4 defines the length (i.e. number of octets) of the GAN Service Zone Name string starting in octet 5. Maximum length of the GAN Service Zone Name string is 32 characters and as each character can be presented using 1 to 4 octets the maximum number of octets is 128. | +| The GAN Service Zone Name string (octets 5 to n) is coded as a string according to UTF-8 format defined in RFC 3629 [50]. This means the 1st octet of the UTF-8 string is coded in octet 5 and the last octet of the UTF-8 string is coded in the last octet of this field (octet n). | + +### 11.2.63 RTP Redundancy Configuration + +The *RTP Redundancy configuration* information element provides the parameters related to redundancy policy for the AMR active codec set. For each mode of the AMR codec set, the redundancy level is indicated i.e. no redundancy (window size 1), single redundant frame (window size 2), double redundant frames (window size 3). The mode for encoding redundant frames can be equal to or lower than the mode for the primary encoding. + +For each mode of the AMR Active Mode Set, as signaled in the Multi-rate Configuration IE, the window size for including redundant frames is indicated. So if e.g. the Active Mode Set contains four active modes, then the RTP Redundancy Configuration IE consists of six octets, of which four indicate the Codec Mode to Window Size mapping. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------|-------------|---|---|-------------|---|---|---|-------------| +| RTP Redundancy Configuration IEI | | | | | | | | octet 1 | +| Length of RTP Redundancy Configuration IE contents | | | | | | | | octet 2, 2a | +| GAN A/Gb | GAN Iu Mode | | | Window Size | | | | octet 3 | +| Mode | Codec Mode | | | | | | | .... | +| Codec Mode | | | | | | | | octet n | + +**Figure 11.2.63.1: Redundancy Configuration information element** + +**Table 11.2.63.1: Redundancy configuration IE** + +| | | +|-------------------------------------------------------------------|------------------------------------------------------------------------------| +| Window Size (octet 3 to octet n) | | +| Bits | | +| 2 | 1 | +| 0 0 | Window size 1, No redundancy | +| 0 1 | Window size 2 (single redundancy) | +| 1 0 | Window size 3 (double redundancy) | +| All other values are reserved | | +| GAN A/Gb Mode Codec Mode (octet 3 to octet n) | | +| Bits | | +| 8 | 7 | +| The GAN A/Gb Mode Codec Mode is coded as in [47] sub-clause 3.4.1 | | +| GAN Iu Mode Codec Mode (octet 3 to octet n) | | +| Bits | | +| 6 | 5 4 3 | +| 0 0 0 0 | Represents the lowest codec mode (lowest bit-rate) of the ACS | +| 0 0 0 1 | Represents the second lowest mode, if the ACS includes more than one mode | +| 0 0 1 0 | Represents the third lowest mode, if the ACS includes more than two modes | +| 0 0 1 1 | Represents the fourth lowest mode, if the ACS includes more than three modes | +| 0 1 0 0 | Represents the fifth lowest mode, if the ACS includes more than four modes | +| 0 1 0 1 | Represents the sixth lowest mode, if the ACS includes more than five modes | +| 0 1 1 0 | Represents the seventh lowest mode, if the ACS includes more than six modes | +| 0 1 1 1 | Represents the highest mode, if the ACS includes eight modes | + +### 11.2.64 UTRAN Classmark + +The *UTRAN Classmark* information element includes the INTER RAT HANDOVER INFO (defined in [40]) which gives UTRAN related information to the network (target system) for the purpose of intersystem handover. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|----------------------------| +| UTRAN Classmark IEI | | | | | | | | octet 1 | +| Length of UTRAN Classmark contents | | | | | | | | octet 2, 2a | +| The rest of the IE is the INTER RAT HANDOVER INFO coded as in [40], not including IEI and length, if present. | | | | | | | | octet 3
....
octet n | + +**Figure 11.2.64.1: UTRAN Classmark information element** + +### 11.2.65 Classmark Enquiry Mask + +The Classmark Enquiry mask defines the information to be returned to the network. The bit mask defines the specific information to be returned, such as UTRAN specific information and/or requests the sending of the GA-CSR CLASSMARK CHANGE message. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Classmark Enquiry Mask IEI | | | | | | | | octet 1 | +| Length of Classmark Enquiry Mask contents | | | | | | | | octet 2, 2a | +| The rest of the IE is the Classmark Enquiry Mask coded as in [12], not including IEI and length, if present. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +**Figure 11.2.65.1: Classmark Enquiry Mask information element** + +### 11.2.66 UTRAN Cell Identifier List + +The UTRAN Cell Identifier List information element is used to transfer multiple UTRAN target cell identifiers from the MS to the GANC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----------------------------------------------------|---|---|---|-----------------------------------------|---|---|---|-------------|--|--|--|--| +| UTRAN Cell Identifier List IEI | | | | | | | | octet 1 | | | | | +| Length of UTRAN Cell Identifier List value contents | | | | | | | | octet 2, 2a | | | | | +| spare | | | | UTRAN Cell Identification Discriminator | | | | octet 3 | | | | | +| UTRAN Cell Identification 1 | | | | | | | | | | | | | +| : | | | | | | | | | | | | | +| UTRAN Cell Identification n | | | | | | | | | | | | | + +**Figure 11.2.66.1: UTRAN Cell Identifier List information element** + +The length of the UTRAN Cell Identifier List information element depends on the UTRAN Cell Identification Discriminator (octet 3). + +The "UTRAN Cell Identification Discriminator" is coded as follows: + +0000 PLMN-ID, LAC and a 28-bit Cell Id are used to identify the target UTRAN cell. + +All other values are reserved. + +The coding of the UTRAN Cell Identifications 1 to n depends on the Cell identification discriminator (octet 3). Below the coding is shown for each UTRAN Cell Identification Discriminator: + +Coding of UTRAN Cell Identification for UTRAN Cell Identification Discriminator = 0000 + +**Table 11.2.66.1: Coding of UTRAN Cell Identification Discriminator = 0000** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|------------------------|---|---|---|-------------|---|---|---|-----------|--|--|--|--| +| MCC digit 2 | | | | MCC digit 1 | | | | octet m | | | | | +| MNC digit 3 | | | | MNC digit 3 | | | | octet m+1 | | | | | +| MNC digit 2 | | | | MNC digit 1 | | | | octet m+2 | | | | | +| LAC | | | | | | | | octet m+3 | | | | | +| LAC cont. | | | | | | | | octet m+4 | | | | | +| 3G Cell identity | | | | | | | | octet m+5 | | | | | +| 3G Cell identity cont. | | | | | | | | octet m+6 | | | | | +| 3G Cell identity cont. | | | | | | | | octet m+7 | | | | | +| 3G Cell identity cont. | | | | Spare | | | | octet m+8 | | | | | + +#### LAC, Location Area Code (2 octet field) + +This field is the binary representation of the Location Area Code, see [3]. The LAC field consists of 16 bits. Bit 8 in octet m+3 is the most significant bit and bit 1 in octet m+4 is the least significant bit. + +#### 3G Cell Identity (4 octet field). + +The octets (m+5)-(m+8) are coded as octets 3-6 in sub-clause 11.2.73. + +### 11.2.67 Serving GANC table indicator + +The purpose of the *Serving GANC table indicator* is to indicate to the mobile station if it is allowed to store information in the stored Serving GANC table after a successful registration. + +![](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +| | | | | | | | | | +|-------------------------------------------------------|---|---|---|---|---|---|------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Serving GANC table indicator IEI | | | | | | | | octet 1 | +| Length of Serving GANC table indicator value contents | | | | | | | | octet 2 | +| spare | | | | | | | SUTI | octet 3 | + +**Figure 11.2.67.1 Serving GANC table indicator information element** + +**Table 11.2.67.1: Serving GANC table indicator information element** + +| | | +|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SUTI, Serving GANC table indicator (octet 3) | | +| Bit | | +| 1 | | +| 0 | The MS is not allowed to store information in the stored Serving GANC table but should still maintain the existing content of the serving GANC table - "Do Not Store". | +| 1 | The MS is allowed to store information in the stored Serving GANC table "Store". | + +### 11.2.68 Registration indicators + +The *Registration indicators* information element is used by the mobile station to indicate status information related to the registration request to the network. This information element is included only when attempting to register to the Default GANC. + +![](c6e0b9030f9fb81435eaf9cb71532614_img.jpg) + +| | | | | | | | | | +|--------------------------------------------|---|---|---|---|---|-----|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Registration indicators IEI | | | | | | | | octet 1 | +| Length of Registration indicators contents | | | | | | | | octet 2 | +| spare | | | | | | MPS | | octet 3 | + +**Figure 11.2.68.1 Registration indicators information element** + +**Table 11.2.68.1: Registration indicators information element** + +| | | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MPS, Manual PLMN Selection indicator (octet 3) | | +| Bit | | +| 2 | 1 | +| 0 0 | The MS is in Automatic PLMN selection mode and user reselection was not triggered. | +| 0 1 | The MS is in Manual PLMN selection mode and/or user reselection was triggered. The MS requests the list of PLMN identities that may provide GAN service in the current location. | +| All other values are reserved for future use. | | + +### 11.2.69 GAN PLMN List + +The GAN PLMN List information element is used by the network to indicate possible PLMNs that may provide GAN service to the MS in its current location. The information element contains the PLMN identifier and the associated GANC and GANC-SEGW address information for each PLMN in the list. It may also contain PLMN specific GAN Service Zone Information. + +![](0c5f3d0d14479b9e784d595fecd6dba5_img.jpg) + +| | | | | | | | | | +|----------------------------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| GAN PLMN List IEI | | | | | | | | octet 1 | +| Length of GAN PLMN List value contents | | | | | | | | octet 2, 2a | +| Number of PLMNs | | | | | | | | octet 3 | +| PLMN information, PLMN 1 | | | | | | | | | +| PLMN information, PLMN n | | | | | | | | | + +**Figure 11.2.69.1: PLMN List information element** + +The "Number of PLMNs" (octet 3) contains the number of PLMN information items in the list. Bit 8 of octet 3 is the most significant bit and bit 1 of octet 3 the least significant bit. + +Coding of PLMN information for each PLMN is the following: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | +|-------------------------------|-----------|------|-------------|-----------|---|---|---|-----------|--|--|--|--|--| +| MCC digit 2 | | | MCC digit 1 | | | | | octet m | | | | | | +| MNC digit 3 | | | MNC digit 3 | | | | | octet m+1 | | | | | | +| MNC digit 2 | | | MNC digit 1 | | | | | octet m+2 | | | | | | +| Spare | GAN Modes | GSZI | GANC-ADDR | SEGW-ADDR | | | | octet m+3 | | | | | | +| GANC-SEGW Address information | | | | | | | | | | | | | | +| GANC Address information | | | | | | | | | | | | | | +| GAN Service Zone information | | | | | | | | | | | | | | + +**Figure 11.2.69.2: PLMN information part of PLMN List information element** + +**Table 11.2.69.1: PLMN information part of PLMN List information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

MCC, Mobile country code (octet m, octet m+1 bits 1 to 4)
The MCC field is coded as in ITU-T Rec. E212, Annex A.

MNC, Mobile network code (octet m+2, octet m+1 bits 5 to 8).
The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. For PCS 1900 for North America, Federal Regulation mandates that a 3-digit MNC shall be used. However a network operator may decide to use only two digits in the MNC over the radio interface. In this case, bits 5 to 8 of octet m+1 shall be coded as "1111". Mobile equipment shall accept MNC coded in such a way.

SEGW-ADDR, GANC-SEGW address type indicator (octet m+3)
Bits
2 1
0 0 GANC-SEGW Address Information for this PLMN is coded as IP-address. The format is as defined in sub-clause 11.2.9, "IP Address" excluding the IP address IEI, but including Length Indicator, IP Address Type and Address Information.

1 0 GANC-SEGW Address Information for this PLMN is coded as FQDN. The format is as defined in sub-clause 11.2.10, "Fully Qualified Domain/Host Name (FQDN)" excluding the FQDN IEI, but including Length Indicator and FQDN.

GANC-ADDR, GANC address type indicator (octet m+3)
Bits
4 3
0 0 GANC Address Information is coded as IP-address. The format is as defined in sub-clause 11.2.9, "IP Address" excluding the IP address IEI, but including Length Indicator, IP Address Type and Address Information.

1 0 GANC Address Information is coded as FQDN. The format is as defined in sub-clause 11.2.10, "Fully Qualified Domain/Host Name (FQDN)" excluding the FQDN IEI, but including Length Indicator and all characters of FQDN.

GSZI, GAN Service Zone Information Indicator (octet m+3)
Bit
5
0 GAN Service Zone Information is not included for this PLMN.
1 GAN Service Zone Information is included for this PLMN.

GAN Modes
Bit
7 6
0 0 Unknown
0 1 The PLMN can only be accessed using GAN A/Gb mode
1 0 The PLMN can only be accessed using GAN Iu mode
1 1 The PLMN can be accessed using GAN A/Gb mode or GAN Iu mode

GANC-SEGW Address information and GANC Address information for each PLMN are coded as defined by GANC-SEGW and GANC address type indicators (for each PLMN).

GAN Service Zone Information is of variable length and the format is as defined in the sub-clause 11.2.62, for the octets 3 to n (GAN Service Zone Icon Indicator, length of GAN Service Zone Name and GAN Service Zone Name). The inclusion of this field is optional for each PLMN and is defined by the GSZI bit.

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.70 GERAN Received Signal Level List + +The GERAN Received Signal Level List information element contains the received signal level for each cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---------------|---|---|---|---|---|-------------| +| GERAN Received Signal Level List IEI | | | | | | | | octet 1 | +| Length of GERAN Received Signal Level List value contents | | | | | | | | octet 2, 2a | +| spare | | RXLEV-NCELL 1 | | | | | | octet 3 | +| spare | | RXLEV-NCELL 2 | | | | | | octet 4 | +| spare | | | | | | | | | +| spare | | RXLEV-NCELL n | | | | | | octet n+2 | + +**Figure 11.2.70.1: *GERAN Received Signal Level List* information element** + +**Table 11.2.70.1: *GERAN Received Signal Level List* information element** + +**RXLEV-NCELL i**, Result of measurement on the i'th neighbour cell (octet i+2), i ranges from 1 to n. + +The RXLEV-NCELL field is coded as the binary representation of a value N. N corresponds according to the mapping defined in 3GPP TS 45.008 to the received signal strength on the i'th neighbouring cell. + +Range: 0 to 63. + +### 11.2.70b UTRAN Received Signal Level List + +The UTRAN Received Signal Level List information element contains the received signal level CPICH Ec/No and CPICH RSCP [46] value for each cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---------------|---|---|---|---|---|-------------| +| UTRAN Received Signal Level List IEI | | | | | | | | octet 1 | +| Length of UTRAN Received Signal Level List value contents | | | | | | | | octet 2, 2a | +| spare | | Ec/No-NCELL 1 | | | | | | octet 3 | +| spare | | RSCP-NCELL 1 | | | | | | octet 4 | +| spare | | Ec/No-NCELL 2 | | | | | | octet 5 | +| spare | | RSCP-NCELL 2 | | | | | | octet 6 | +| spare | | | | | | | | | +| spare | | Ec/No-NCELL n | | | | | | octet 2*n+1 | +| spare | | RSCP-NCELL n | | | | | | octet 2*n+2 | + +**Figure 11.2.70b.1: *UTRAN Received Signal Level List* information element** + +**Table 11.2.70b.1: *UTRAN Received Signal Level List* information element** + +**Ec/No-NCELL i**, Result of Ec/No measurement on the i'th neighbour cell is contained in octet 2\*i+1, i ranges from 1 to n. + +**RSCP-NCELL i**, Result of RSCP measurement on the i'th neighbour cell is contained in octet 2\*i+2, i ranges from 1 to n. + +The mapping is defined in [46]. For RSCP the range from "-116 dBm $\leq$ CPICH RSCP $<$ -115 dBm" (reported as 0) to "-53 dBm $\leq$ CPICH RSCP $<$ -52 dBm" (reported as 63) is used. RSCP values below -116 dBm shall be reported as 0 and values -52 dBm and above shall be reported as 63. For Ec/No the range from "-24 dB $\leq$ CPICH Ec/No $<$ -23.5 dB" (reported as 1) to "-0.5 $\leq$ CPICH Ec/No $<$ 0" (reported as 48) is used. Ec/No values below -24 dB shall be reported as 0 and values 0 dB and above shall be reported as 49. + +### 11.2.71 Required GAN Services + +The purpose of the *Required GAN Services* information element is to indicate to the GANC that the mobile station requires a GAN specific service and which of the GAN services the mobile station requires. + +![](38d82ffe820e339811b396206f40a201_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|-----|---------| +| Required GAN Services IEI | | | | | | | | octet 1 | +| Length of Required GAN Services contents | | | | | | | | octet 2 | +| spare | | | | | | | CBS | octet 3 | + +**Figure 11.2.71.1: Required GAN Services information element** + +**Table 11.2.71.1: Required GAN Services information element** + +| | +|---------------------------------------------| +| CBS Cell Broadcast Service (octet 3) | +| Bit | +| 1 | +| 0 CBS is not required by the mobile station | +| 1 CBS is required by the mobile station. | + +### 11.2.72 Broadcast Container + +The Broadcast Container information element is used by the network to encapsulate Cell Broadcast information being passed to a mobile station. + +![](6116b1a533010c170fc526ec513ba0b8_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|---|----------------| +| Broadcast Container IEI | | | | | | | | octet 1 | +| Length of Broadcast Container value contents | | | | | | | | octet 2, 2a | +| Number of CBS Frames | | | | | | | | octet 3 | +| CBS Frames 1 | | | | | | | | octet 4-91 | +| CBS Frames n | | | | | | | | octet m-(m+87) | + +**Figure 11.2.72.1: Broadcast Container information element** + +The "Number of CBS Frames" (octet 3) contains the number of CBS Frames in the list. Bit 8 of octet 3 is the most significant bit and bit 1 of octet 3 the least significant bit. + +Coding of CBS Frame is the following: + +![](0a595a22e0d1a1be020b49afa71bef55_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------|---|---|---|---|---|---|---|-------------------| +| Page from a CBS Message MSB | | | | | | | | octet | +| Page from a CBS Message LSB | | | | | | | | x...octet
x+87 | + +**Figure 11.2.72.2: CBS Frame part of Broadcast Container information element** + +The coding of the page of the CBS message is defined in sub-clause 9.4.1 in TS 23.041. + +### 11.2.73 3G Cell Identity + +The purpose of the 3G *Cell Identity* information element is to identify a cell within a PLMN. + +![](2232c471414cb1ca6484a5a1d0a2dd27_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------|---|---|---|---|---|---|---|-------------| +| 3G Cell Identity IEI | | | | | | | | octet 1 | +| Length of 3G Cell Identity IE contents | | | | | | | | octet 2, 2a | +| See Annex F for coding | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet 6 | + +**Figure 11.2.73.1 3G Cell Identity information element** + +### 11.2.74 PS Handover to GERAN Command + +The purpose of the PS Handover to GERAN Command information element is to provide the MS with Radio Resource and Non-Access Stratum information required for performing PS handover to a GERAN cell. The PS Handover to GERAN Command information element and either the PS Handover to GERAN PSI or the PS Handover to GERAN SI information element together contain all of the information needed by the MS to perform PS handover to a GERAN cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PS Handover to GERAN Command IEI | | | | | | | | octet 1 | +| Length of PS Handover to GERAN Command value contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as the PS HANDOVER COMMAND message defined in [45]. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +Figure 11.2.74.1: PS Handover to GERAN Command information element + +### 11.2.75 PS Handover to UTRAN Command + +The purpose of the PS Handover to UTRAN Command information element is to provide the MS with information required for performing PS handover to a UTRAN cell. The PS Handover to UTRAN Command information element contains all information needed by the MS for performing PS handover to a UTRAN cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PS Handover to UTRAN Command IEI | | | | | | | | octet 1 | +| Length of PS Handover to UTRAN Command value contents | | | | | | | | octet 2, 2a | +| The rest of the IE is coded as the INTERSYSTEM HANDOVER TO UTRAN COMMAND message defined in [40]. | | | | | | | | octet 3 | +| | | | | | | | | .... | +| | | | | | | | | octet n | + +Figure 11.2.75.1: PS Handover to UTRAN Command information element + +### 11.2.76 PS Handover to GERAN PSI + +The purpose of the PS Handover to GERAN PSI information element is to provide the MS with packet system information (corresponding to the target GERAN cell) required for performing PS handover to a GERAN cell where PBCCH is present. The PS Handover to GERAN Command information element and the PS Handover to GERAN PSI information element together contain all of the information needed by the MS for performing PS handover to a GERAN cell where PBCCH is present. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PS Handover to GERAN PSI IEI | | | | | | | | octet 1 | +| Length of PS Handover to GERAN PSI value contents | | | | | | | | octet 2, 2a | +| Length of PSI1 payload | | | | | | | | octet 3 | +| The same system information sent using a PSI1 on a PBCCH (see 3GPP TS 44.060 [45]). | | | | | | | | octet 4 | +| | | | | | | | | .... | +| | | | | | | | | octet n | +| Length of PSI2 payload | | | | | | | | octet n+1 | +| The same system information sent using one or more instances of the PSI2 message on a PBCCH (see 3GPP TS 44.060 [45]). | | | | | | | | octet n+2 | +| | | | | | | | | .... | +| | | | | | | | | octet k | +| Length of PSI14 payload | | | | | | | | octet k+1 | +| The same system information sent using a PSI14 message on a PBCCH (see 3GPP TS 44.060 [45]). | | | | | | | | octet k+2 | +| | | | | | | | | .... | +| | | | | | | | | octet p | + +Figure 11.2.76.1: PS Handover to GERAN PSI information element + +### 11.2.77 PS Handover to GERAN SI + +The purpose of the PS Handover to GERAN SI information element is to provide the MS with system information (corresponding to the target GERAN cell) required for performing PS handover to a GERAN cell where PBCCH is not present. The PS Handover to GERAN Command information element and the PS Handover to GERAN SI information element together contain all of the information needed by the MS for performing PS handover to a GERAN cell where PBCCH is not present. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PS Handover to GERAN SI IEI | | | | | | | | octet 1 | +| Length of PS Handover to GERAN SI value contents | | | | | | | | octet 2, 2a | +| Length of S1 payload | | | | | | | | octet 3 | +| The same system information sent using an SI1 on a BCCH (see 3GPP TS 44.018 [12]). | | | | | | | | octet 4 | +| | | | | | | | | .... | +| | | | | | | | | octet n | +| Length of SI3 payload | | | | | | | | octet n+1 | +| The same system information sent using an SI3 message on a BCCH (see 3GPP TS 44.018 [12]). | | | | | | | | octet n+2 | +| | | | | | | | | .... | +| | | | | | | | | octet k | +| Length of SI13 payload | | | | | | | | octet k+1 | +| The same system information sent using an SI13 message on a BCCH (see 3GPP TS 44.018 [12]). | | | | | | | | octet k+2 | +| | | | | | | | | .... | +| | | | | | | | | octet p | + +Figure 11.2.77.1: PS Handover to GERAN SI information element + +### 11.2.78 TU4004 Timer + +The purpose of this information element is to indicate to the MS how long it should wait for a GA-PSR HANDOVER COMMAND message after sending a GA-PSR HANDOVER INFORMATION message to the network or receiving a GA-PSR HANDOVER CONTINUE message from the network. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| TU4004 Timer IEI | | | | | | | | octet 1 | +| Length of TU4004 Timer IE contents | | | | | | | | octet 2 | +| TU4004 Timer value | | | | | | | | octet 3 | + +Figure 11.2.78.1: TU4004 Timer information element + +Table 11.2.78.1: TU4004 Timer information element + +| | +|--------------------------------------------------------------------------| +| TU4004 Timer value (octet 3)
The value is given in number of seconds. | +|--------------------------------------------------------------------------| + +### 11.2.79 GAN Mode Indicator + +The GAN Mode Indicator information element indicates the GAN mode that the MS shall operate in for the current registration. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------|---|---|---|---|---|---|---|---------| +| GAN Mode Indicator IEI | | | | | | | | octet 1 | +| Length of GAN Mode Indicator value contents | | | | | | | | octet 2 | +| GMI | | | | | | | | octet 3 | + +Figure 11.2.79.1: GAN Mode Indicator information element + +**Table 11.2.79.1: GAN Mode Indicator information element** + +| | | +|-------------------------------------------|---------------------------------------| +| GMI , GAN Mode Indicator (octet 3) | | +| 0 | Reserved | +| 1 | The MS shall operate in GAN A/Gb mode | +| 2 | The MS shall operate in GAN Iu mode | +| 3 to 255 | Reserved | + +### 11.2.80 CN Domain Identity + +The CN Domain Identity information element indicates the type of core network domain (CS or PS) to which the message applies. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------|---|---|---|---|---|---|---|---------| +| CN Domain Identity IEI | | | | | | | | octet 1 | +| Length of CN Domain Identity value contents | | | | | | | | octet 2 | +| CNDI | | | | | | | | octet 3 | + +**Figure 11.2.80.1: CN Domain Identity information element****Table 11.2.80.1: CN Domain Identity information element** + +| | | +|--------------------------------------------|-----------| +| CNDI , CN Domain Identity (octet 3) | | +| 0 | Reserved | +| 1 | CS domain | +| 2 | PS domain | +| 3 to 255 | Reserved | + +### 11.2.81 GAN Iu Mode Cell Description + +The GAN Iu Mode Cell Description information element provides a minimum description of a GAN Iu mode cell, e.g. to identify the GAN Iu mode cell in order to perform handover from GERAN/UTRAN. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------|---|---|---|---|---|---|---|---------| +| GAN Iu Mode Cell Description IEI | | | | | | | | octet 1 | +| Length of GAN Iu Mode Cell Description value contents | | | | | | | | octet 2 | +| UARFCN | | | | | | | | octet 3 | +| UARFCN | | | | | | | | octet 4 | +| PSC | | | | | | | | octet 5 | +| PSC | | | | | | | | octet 6 | + +**Figure 11.2.81.1: GAN Iu Mode Cell Description information element****Table 11.2.81.1: GAN Iu Mode Cell Description information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

UARFCN, UTRA Absolute RF Channel Number (octet 3, 4)
Allowed values are between 0 and 16383. This is a 14-bit quantity with the first bit (most significant bit) in octet 3 bit 6 and the last bit (least significant bit) in octet 4 bit 1. Octet 3 bits 7-8 are filled by '00'

PSC, Primary Scrambling Code (octet 5, 6)
Allowed values are between 0 and 511. This is a 9-bit quantity with the first bit (most significant bit) in octet 5 bit 1 and the last bit (least significant bit) in octet 6 bit 1. Octet 5 bits 2-8 are filled by '0000000'.

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.82 3G UARFCN + +The 3G UARFCN information element indicates the UARFCN value of the current UTRAN serving cell, if the current serving cell is a UTRAN cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------|---|---|---|---|---|---|---|---------| +| 3G UARFCN IEI | | | | | | | | octet 1 | +| Length of 3G UARFCN value contents | | | | | | | | octet 2 | +| UARFCN | | | | | | | | octet 3 | +| UARFCN | | | | | | | | octet 4 | + +Figure 11.2.82.1: 3G UARFCN information element + +Table 11.2.82.1: 3G UARFCN information element + +**UARFCN**, UTRA Absolute RF Channel Number (octet 3, 4) +Allowed values are between 0 and 16383. This is a 14-bit quantity with the first bit (most significant bit) in octet 3 bit 6 and the last bit (least significant bit) in octet 4 bit 1. Octet 3 bits 7-8 are filled by '00' + +### 11.2.83 RAB ID + +The RAB ID information element is used by the GANC to identify a circuit transport channel or packet transport channel. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|---|---|---|---|---|---|---------| +| RAB ID IEI | | | | | | | | octet 1 | +| Length of RAB ID value contents | | | | | | | | octet 2 | +| RABID | | | | | | | | octet 3 | + +Figure 11.2.83.1: RAB ID information element + +Table 11.2.83.1: RAB ID information element + +**RABID**, RAB ID (octet 3) +Allowed values are between 0 and 255. + +### 11.2.84 RAB ID List + +The RAB ID List information element is used by the GANC to identify a set of circuit transport channel(s) or packet transport channel(s). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|---|---|-------------| +| RAB ID List IEI | | | | | | | | octet 1 | +| Length of RAB ID List value contents | | | | | | | | octet 2, 2a | +| Number of RAB IDs | | | | | | | | octet 3 | +| RAB ID 1 | | | | | | | | | +| RAB ID n | | | | | | | | | + +Figure 11.2.84.1: RAB ID List information element + +Table 11.2.84.1: RAB ID List information element + +**Number of RAB IDs** (octet 3) +The number of RAB IDs in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. + +**RAB ID 1..n** +The format is as defined in sub-clause 11.2.83, "RAB ID" but without the RAB ID IEI and length fields. + +### 11.2.85 GA-RRC Establishment Cause + +The GA-RRC Establishment Cause information element indicates the cause for the GA-RRC connection establishment request. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------|---|---|---|---|---|---|---|---------| +| GA-RRC Establishment Cause IEI | | | | | | | | octet 1 | +| Length of GA-RRC Establishment Cause value contents | | | | | | | | octet 2 | +| Cause | | | | | | | | octet 3 | + +**Figure 11.2.85.1: GA-RRC Establishment Cause information element** + +**Table 11.2.85.1: GA-RRC Establishment Cause information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cause (octet 3)
The GA-RRC Establishment Cause IE is aligned with the "Establishment cause" IE defined in section 10.3.3.11 of [TS 25.331]. A Cause value of 1 is assigned to the first value in the RRC "Establishment cause" enumerated list (i.e., "Originating Conversational Call") and the Cause value is incremented by one for each subsequent "Establishment cause" value.

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.86 GA-RRC Cause + +The GA-RRC Cause information element indicates the cause associated with the GA-RRC procedure (e.g., release, reject, etc.). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------|---|---|---|---|---|---|---|---------| +| GA-RRC Cause IEI | | | | | | | | octet 1 | +| Length of GA-RRC Cause value contents | | | | | | | | octet 2 | +| Cause MSB | | | | | | | | octet 3 | +| Cause LSB | | | | | | | | octet 4 | + +**Figure 11.2.86.1: GA-RRC Cause information element** + +**Table 11.2.86.1: GA-RRC Cause information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Cause (octet 3)
The GA-RRC Cause IE is aligned with the "Cause" IE defined in section 9.2.1.4 of 3GPP TS 25.413 [52]. The Cause value is coded per the values defined in section 9.2.1.4 of [52]. In addition, a value of 0 (zero) is considered a normal event or indicating success.

| +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.87 GA-RRC Paging Cause + +The GA-RRC Paging Cause information element indicates the cause for paging. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|---|---------| +| GA-RRC Paging Cause IEI | | | | | | | | octet 1 | +| Length of GA-RRC Paging Cause value contents | | | | | | | | octet 2 | +| Paging Cause | | | | | | | | octet 3 | + +**Figure 11.2.87.1: GA-RRC Paging Cause information element** + +**Table 11.2.87.1: GA-RRC Paging Cause information element** + +| Paging Cause (octet 3) | | +|-------------------------------|--------------------------------------| +| 0 | Terminating Conversational Call | +| 1 | Terminating Streaming Call | +| 2 | Terminating Interactive Call | +| 3 | Terminating Background Call | +| 4 | Terminating Low Priority Signalling | +| 5 | Terminating High Priority Signalling | +| 6 to 255 | Reserved for future use | + +### 11.2.88 Intra Domain NAS Node Selector + +The Intra Domain NAS Node Selector information element carries information to be used to route the establishment of a signalling connection to a CN node within a CN domain. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------|---|---|---|---|---|---|---|---------| +| Intra Domain NAS Node Selector IEI | | | | | | | | octet 1 | +| Length of Intra Domain NAS Node Selector value contents | | | | | | | | octet 2 | +| IDNSS Type | | | | | | | | octet 3 | +| Routing Parameter | | | | | | | | octet 4 | +| Routing Parameter | | | | | | | | octet 5 | + +**Figure 11.2.88.1: Intra Domain NAS Node Selector information element****Table 11.2.88.1: Intra Domain NAS Node Selector information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IDNSS Type (octet 3) | +| Value | +| 0 Reserved | +| 1 Local (P)TMSI | +| 2 (P)TMSI of same PLMN, different (RA)LA | +| 3 (P)TMSI of different PLMN | +| 4 IMSI (response to IMSI paging) | +| 5 IMSI (cause UE initiated event) | +| 6 IMEI | +| 7-255 Reserved | +| All other values are reserved. | +| Routing Parameter (octet 4, 5) | +| This is a 10-bit quantity with the first bit (most significant bit) in octet 4 bit 2 and the last bit (least significant bit) in octet 5 bit 1. Octet 4 bits 3-8 are filled by '000000'. | +| Refer to the Intra Domain NAS Node Selector information element definition in sub-clause 10.3.1.6 of [40] for a description of the above IDNSS Type and Routing Parameter values. | + +### 11.2.89 CTC Activation List + +The CTC Activation List information element is used by the GANC to describe the circuit transport channel(s) that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|---|-------------| +| CTC Activation List IEI | | | | | | | | octet 1 | +| Length of CTC Activation List value contents | | | | | | | | octet 2, 2a | +| Number of CTCs | | | | | | | | octet 3 | +| CTC Description, CTC 1 | | | | | | | | | +| CTC Description, CTC n | | | | | | | | | + +**Figure 11.2.89.1: CTC Activation List information element** + +**Table 11.2.89.1: CTC Activation List information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of CTCs
The number of CTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. | +| CTC Description
The format is as defined in sub-clause 11.2.90, "CTC Description". | + +### 11.2.90 CTC Description + +The CTC Description information element is used by the GANC to describe the circuit transport channel that shall be activated or modified between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|-------------| +| CTC Description IEI | | | | | | | | octet 1 | +| Length of CTC Description value contents | | | | | | | | octet 2, 2a | +| RAB ID | | | | | | | | | +| RAB Configuration | | | | | | | | | +| Sample Size | | | | | | | | | +| RTP UDP Port | | | | | | | | | +| GANC IP Address | | | | | | | | | +| Payload Type | | | | | | | | | +| Multi-rate Configuration 2 | | | | | | | | | +| RTP Redundancy Configuration | | | | | | | | | +| RTCP UDP Port | | | | | | | | | +| NAS Synchronisation Indicator | | | | | | | | | + +**Figure 11.2.90.1: CTC Description information element** + +**Table 11.2.90.1: CTC Description information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RAB ID
The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. | +| RAB Configuration
The format is as defined in sub-clause 11.2.103, "RAB Configuration". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. | +| Sample Size
The format is as defined in sub-clause 11.2.53, "Sample Size". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. | +| RTP UDP Port
The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTP UDP Port". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. | +| GANC IP Address
The format is as defined in sub-clause 11.2.9, "IP Address" but with IEI as specified in Table 11.2.1 for "GANC IP Address". This field shall be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. | +| Payload Type
The format is as defined in sub-clause 11.2.54, "Payload Type". This field shall be included in the case of CTC activation. It shall not be included in the case of CTC modification. | +| Multi-rate Configuration 2
The format is as defined in sub-clause 11.2.104, "Multi-rate Configuration 2". This field shall be included in the case of CTC activation if the RAB Configuration specifies speech. It shall only be included in the case of CTC modification if modification of this parameter is requested. | +| RTP Redundancy Configuration
The format is as defined in sub-clause 11.2.63, "RTP Redundancy Configuration". This field shall be included in the case of CTC activation if the RAB Configuration specifies speech and the MS has indicated support for RTP redundancy in the GAN Classmark IE. It shall only be included in the case of CTC modification if modification of this parameter is requested. | +| RTCP UDP Port
The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTCP UDP Port". This field may be included in the case of CTC activation. It shall only be included in the case of CTC modification if modification of this parameter is requested. | +| NAS Synchronisation Indicator
The format is as defined in sub-clause 11.2.109, "NAS Synchronisation Indicator". This field shall be included in the case of CTC activation if received by the GANC from the CN. It shall only be included in the case of CTC modification if modification of this parameter is requested. | + +### 11.2.91 CTC Activation Ack List + +The CTC Activation Ack List information element is used by the MS to describe certain parameters of the circuit transport channel(s) that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------|---|---|---|---|---|---|---|-------------| +| CTC Activation Ack List IEI | | | | | | | | octet 1 | +| Length of CTC Activation Ack List value contents | | | | | | | | octet 2, 2a | +| Number of CTCs | | | | | | | | octet 3 | +| CTC Activation Ack Description, CTC 1 | | | | | | | | | +| CTC Activation Ack Description, CTC n | | | | | | | | | + +**Figure 11.2.91.1: CTC Activation Ack List information element** + +**Table 11.2.91.1: CTC Activation Ack List information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Number of CTCs
The number of CTC Activation Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit.

| +|

CTC Activation Ack Description
The format is as defined in sub-clause 11.2.92, "CTC Activation Ack Description".

| + +### 11.2.92 CTC Activation Ack Description + +The CTC Activation Ack Description information element is used by the MS to indicate CTC activation success or failure and, in the successful case, to describe certain parameters of the circuit transport channel that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| CTC Activation Ack Description IEI | | | | | | | | octet 1 | +| Length of CTC Activation Ack Description value contents | | | | | | | | octet 2, 2a | +| RAB ID | | | | | | | | | +| GA-RRC Cause | | | | | | | | | +| RTP UDP Port | | | | | | | | | +| Sample Size | | | | | | | | | +| Payload Type | | | | | | | | | +| RTCP UDP Port | | | | | | | | | + +Figure 11.2.92.1: CTC Activation Ack Description information element + +Table 11.2.92.1: CTC Activation Ack Description information element + +#### RAB ID + +The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. + +#### GA-RRC Cause + +The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than 'success' (i.e., value '0') then the following fields shall not be present in the CTC Activation Ack Description IE. + +#### RTP UDP Port + +The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTP UDP Port". This field shall be included if the GA-RRC Cause value is '0'. + +#### Sample Size + +The format is as defined in sub-clause 11.2.53, "Sample Size". This field shall be included if the GA-RRC Cause value is '0' and shall indicate what sample size the MS is using and what the network shall use in the downlink. The MS shall follow the minimum sample size for the channel sent by the network in the GA-RRC ACTIVATE CHANNEL message. + +#### Payload Type + +The format is as defined in sub-clause 11.2.54, "Payload Type". This field shall be included if the GA-RRC Cause value is '0'. It shall be set to the same value as the Payload Type for the channel in the GA-RRC ACTIVATE CHANNEL message. + +#### RTCP UDP Port + +The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "RTCP UDP Port". This field shall be included if the GA-RRC Cause value is '0' and RTCP shall be used towards the MS. It is used to indicate the UDP port for RTCP sent to the MS. + +### 11.2.93 CTC Modification List + +The CTC Modification List information element is used by the GANC to describe the circuit transport channel(s) that shall be modified between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------------|---|---|---|---|---|---|---|-------------| +| CTC Modification List IEI | | | | | | | | octet 1 | +| Length of CTC Modification List value contents | | | | | | | | octet 2, 2a | +| Number of CTCs | | | | | | | | octet 3 | +| CTC Description, CTC 1 | | | | | | | | | +| CTC Description, CTC n | | | | | | | | | + +Figure 11.2.93.1: CTC Modification List information element + +Table 11.2.93.1: CTC Modification List information element + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Number of CTCs
The number of CTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit.

CTC Description
The format is as defined in sub-clause 11.2.90, "CTC Description".

| +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.94 CTC Modification Ack List + +The CTC Modification Ack List information element is used by the MS to describe certain parameters of the circuit transport channel(s) that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------|---|---|---|---|---|---|---|-------------| +| CTC Modification Ack List IEI | | | | | | | | octet 1 | +| Length of CTC Modification Ack List value contents | | | | | | | | octet 2, 2a | +| Number of CTCs | | | | | | | | octet 3 | +| CTC Modification Ack Description, CTC 1 | | | | | | | | | +| CTC Modification Ack Description, CTC n | | | | | | | | | + +Figure 11.2.94.1: CTC Modification Ack List information element + +Table 11.2.94.1: CTC Modification Ack List information element + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Number of CTCs
The number of CTC Modification Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit.

CTC Modification Ack Description
The format is as defined in sub-clause 11.2.95, "CTC Modification Ack Description".

| +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.95 CTC Modification Ack Description + +The CTC Modification Ack Description information element is used by the MS to describe certain parameters of the circuit transport channel that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| CTC Modification Ack Description IEI | | | | | | | | octet 1 | +| Length of CTC Modification Ack Description value contents | | | | | | | | octet 2, 2a | +| RAB ID | | | | | | | | | +| GA-RRC Cause | | | | | | | | | +| Sample Size | | | | | | | | | + +###### **Figure 11.2.95.1: CTC Modification Ack Description information element** + +##### **Table 11.2.95.1: CTC Modification Ack Description information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

RAB ID

The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included.

| +|

GA-RRC Cause

The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than 'success' (i.e., value '0') then the following fields shall not be present in the CTC Modification Ack Description IE.

| +|

Sample Size

The format is as defined in sub-clause 11.2.53, "Sample Size". This field shall be included if the GA-RRC Cause value is '0' and this parameter has been modified.

| + +### 11.2.96 PTC Activation List + +The PTC Activation List information element is used by the GANC to describe the packet transport channel(s) that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|----------------------------------------------| +| | | | | | | | | PTC Activation List IEI | +| | | | | | | | | Length of PTC Activation List value contents | +| | | | | | | | | Number of PTCs | +| | | | | | | | | PTC Description, PTC 1 | +| | | | | | | | | PTC Description, PTC n | + +octet 1 +octet 2, 2a +octet 3 + +**Figure 11.2.96.1: PTC Activation List information element** + +**Table 11.2.96.1: PTC Activation List information element** + +#### Number of PTCs + +The number of PTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. + +#### PTC Description + +The format is as defined in sub-clause 11.2.97, "PTC Description". + +### 11.2.97 PTC Description + +The PTC Description information element is used by the GANC to describe the packet transport channel that shall be activated or modified between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|------------------------------------------| +| | | | | | | | | PTC Description IEI | +| | | | | | | | | Length of PTC Description value contents | +| | | | | | | | | RAB ID | +| | | | | | | | | RAB Configuration | +| | | | | | | | | GANC TEID | +| | | | | | | | | MS TEID | +| | | | | | | | | GANC UDP Port | +| | | | | | | | | GANC IP Address | + +octet 1 +octet 2, 2a + +**Figure 11.2.97.1: PTC Description information element** + +**Table 11.2.97.1: PTC Description information element** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RAB ID
The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. | +| RAB Configuration
The format is as defined in sub-clause 11.2.103, "RAB Configuration". This field shall be included. | +| GANC TEID
The format is as defined in sub-clause 11.2.110, "TEID" but with IEI as specified in Table 11.2.1 for "GANC TEID". This field shall be included. | +| MS TEID
The format is as defined in sub-clause 11.2.110, "TEID" but with IEI as specified in Table 11.2.1 for "MS TEID". This field shall be included. | +| GANC UDP Port
The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "UDP Port for GPRS user data transport". This field shall be included. | +| GANC IP Address
The format is as defined in sub-clause 11.2.9, "IP Address" but with IEI as specified in Table 11.2.1 for "IP Address for GPRS user data transport". This field shall be included. | + +### 11.2.98 PTC Activation Ack List + +The PTC Activation Ack List information element is used by the MS to describe certain parameters of the packet transport channel(s) that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PTC Activation Ack List IEI | | | | | | | | octet 1 | +| Length of PTC Activation Ack List value contents | | | | | | | | octet 2, 2a | +| Number of PTCs | | | | | | | | octet 3 | +| PTC Activation Ack Description, PTC 1 | | | | | | | | | +| PTC Activation Ack Description, PTC n | | | | | | | | | + +**Figure 11.2.98.1: PTC Activation Ack List information element****Table 11.2.98.1: PTC Activation Ack List information element** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of PTCs
The number of PTC Activation Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. | +| PTC Activation Ack Description
The format is as defined in sub-clause 11.2.99, "PTC Activation Ack Description". | + +### 11.2.99 PTC Activation Ack Description + +The PTC Activation Ack Description information element is used by the MS to describe certain parameters of the packet transport channel that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PTC Activation Ack Description IEI | | | | | | | | octet 1 | +| Length of PTC Activation Ack Description value contents | | | | | | | | octet 2, 2a | +| RAB ID | | | | | | | | | +| GA-RRC Cause | | | | | | | | | +| MS UDP Port | | | | | | | | | + +**Figure 11.2.99.1: PTC Activation Ack Description information element****Table 11.2.99.1: PTC Activation Ack Description information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RAB ID
The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. | +| GA-RRC Cause
The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than 'success' (i.e., value '0') then the following fields shall not be present in the PTC Activation Ack Description IE. | +| MS UDP Port
The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "UDP Port for GPRS user data transport". This field shall be included if the GA-RRC Cause value is '0'. | + +### 11.2.100 PTC Modification List + +The PTC Modification List information element is used by the GANC to describe the circuit transport channel(s) that shall be modified between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PTC Modification List IEI | | | | | | | | octet 1 | +| Length of PTC Modification List value contents | | | | | | | | octet 2, 2a | +| Number of PTCs | | | | | | | | octet 3 | +| PTC Description, PTC 1 | | | | | | | | | +| PTC Description, PTC n | | | | | | | | | + +**Figure 11.2.100.1: PTC Modification List information element****Table 11.2.100.1: PTC Modification List information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of PTCs
The number of PTC Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit. | +| PTC Description
The format is as defined in sub-clause 11.2.97, "PTC Description". | + +### 11.2.101 PTC Modification Ack List + +The PTC Modification Ack List information element is used by the MS to describe certain parameters of the packet transport channel(s) that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PTC Modification Ack List IEI | | | | | | | | octet 1 | +| Length of PTC Modification Ack List value contents | | | | | | | | octet 2, 2a | +| Number of PTCs | | | | | | | | octet 3 | +| PTC Modification Ack Description, PTC 1 | | | | | | | | | +| PTC Modification Ack Description, PTC n | | | | | | | | | + +Figure 11.2.101.1: PTC Modification Ack List information element + +Table 11.2.101.1: PTC Modification Ack List information element + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Number of PTCs
The number of PTC Modification Ack Descriptions in the IE. Bit 8 of octet 3 is the most significant bit and bit 1 is the least significant bit.

PTC Modification Ack Description
The format is as defined in sub-clause 11.2.102, "PTC Modification Ack Description".

| +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.102 PTC Modification Ack Description + +The PTC Modification Ack Description information element is used by the MS to describe certain parameters of the packet transport channel that shall be activated between the GANC and MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| PTC Modification Ack Description IEI | | | | | | | | octet 1 | +| Length of PTC Modification Ack Description value contents | | | | | | | | octet 2, 2a | +| RAB ID | | | | | | | | | +| GA-RRC Cause | | | | | | | | | +| RAB Configuration | | | | | | | | | +| GANC UDP Port | | | | | | | | | +| GANC IP Address | | | | | | | | | + +Figure 11.2.102.1: PTC Modification Ack Description information element + +**Table 11.2.102.1: PTC Modification Ack Description information element** + +#### **RAB ID** + +The format is as defined in sub-clause 11.2.83, "RAB ID". This field shall be included. + +#### **GA-RRC Cause** + +The format is as defined in sub-clause 11.2.86, "GA-RRC Cause". This field shall be included. If the GA-RRC Cause value is other than 'success' (i.e., value '0') then the following fields shall not be present in the PTC Activation Ack Description IE. + +#### **RAB Configuration** + +The format is as defined in sub-clause 11.2.103, "RAB Configuration". This field shall be included if the GA-RRC Cause value is '0' and this parameter has been modified. + +##### **GANC UDP Port** + +The format is as defined in sub-clause 11.2.25, "Communication Port Identity" but with IEI as specified in Table 11.2.1 for "UDP Port for GPRS user data transport". This field shall be included if the GA-RRC Cause value is '0' and this parameter has been modified. + +##### **GANC IP Address** + +The format is as defined in sub-clause 11.2.9, "IP Address" but with IEI as specified in Table 11.2.1 for "IP Address for GPRS user data transport". This field shall be included if the GA-RRC Cause value is '0' and this parameter has been modified. + +### 11.2.103 RAB Configuration + +The purpose of the RAB Configuration information element is to specify the UMTS RAB parameter values that are associated with a circuit transport channel or packet transport channel and that are applicable in the GAN Iu mode context. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | +|--------------------------------------------|---------------------------|-----|----|----|-------|---------------|---|-----------------------|--|--|--|--|--|--| +| RAB Configuration IEI | | | | | | | | octet 1 | | | | | | | +| Length of RAB Configuration value contents | | | | | | | | octet 2 | | | | | | | +| spare | SI | SSD | DO | AI | | Traffic Class | | octet 3 | | | | | | | +| spare | Traffic Handling Priority | | | | spare | | | octet 4 | | | | | | | +| Maximum DL Bit Rate | | | | | | | | octet 5
-octet 8 | | | | | | | +| Maximum UL Bit Rate | | | | | | | | octet 9
-octet 12 | | | | | | | +| Guaranteed DL Bit Rate (if present) | | | | | | | | octet 13
-octet 16 | | | | | | | +| Guaranteed UL Bit Rate (if present) | | | | | | | | octet 17
-octet 20 | | | | | | | + +Figure 11.2.103.1: RAB Configuration information element + +**Table 11.2.103.1: RAB Configuration information element** + +##### **Traffic Class** (octet 3) + +Bits + +2 1 + +0 0 conversational + +0 1 streaming + +1 0 interactive + +1 1 background + +Note: The value 'conversational' shall be used for AMR/AMR-WB CS domain speech. + The values 'conversational' or 'streaming' shall be used for CS domain data. + +##### **AI**, Asymmetry Indicator (octet 3) + +Bits + +4 3 + +0 0 symmetric bi-directional + +0 1 asymmetric uni-directional downlink + +1 0 asymmetric uni-directional uplink + +1 1 asymmetric bi-directional + +Note: The value 'symmetric bi-directional' shall be used for AMR/AMR-WB CS domain speech. + +##### **DO**, Delivery Order (octet 3) + +Bit + +5 + +0 delivery order requested + +1 delivery order not requested + +Note: The value 'delivery order requested' shall be used for AMR/AMR-WB CS domain speech. + +##### **SSD**, Source Statistics Descriptor (octet 3) + +Bit + +6 + +0 speech + +1 unknown + +Note: The value 'speech' shall be used for AMR/AMR-WB speech. + +##### **SI**, Signalling Indication (octet 3) + +Bit + +7 + +0 signalling Indication is set + +1 signalling Indication is not set + +Note: The value 'signalling Indication is not set' shall be used for AMR/AMR-WB speech. + +##### **Traffic Handling Priority** (octet 4) + +Bits + +7 6 5 4 Bit 7 is the most significant bit and bit 4 the least significant bit. + +0 0 0 0 spare + +0 0 0 1 highest + +.. + +.. + +1 1 1 0 lowest + +1 1 1 1 no priority + +Values between 1 and 14 are ordered in decreasing order of priority. + +##### **Maximum DL Bit Rate**, (octets 5-8) + +The MSB is octet 5 and the LSB is octet 8. Unit is bits/s. + +##### **Maximum UL Bit Rate**, (octets 9-12) + +The MSB is octet 9 and the LSB is octet 12. If Asymmetry Indicator indicates "Symmetric bi-directional" then this value shall be the same as Maximum DL Bit Rate value. Unit is bits/s. + +#### **Guaranteed DL Bit Rate**, (octets 13-16) + +The MSB is octet 13 and the LSB is octet 16. + +Included only if the Traffic Class indicates conversational or streaming. Unit is bits/s. + +##### **Guaranteed UL Bit Rate**, (octets 17-20) + +The MSB is octet 17 and the LSB is octet 20. + +Included only if the Traffic Class indicates conversational or streaming. If included and the Asymmetry Indicator indicates "Symmetric bi-directional" then this value shall be the same as Guaranteed DL Bit Rate value. Unit is bits/s. + +### 11.2.104 Multi-rate Configuration 2 + +The Multi-rate Configuration 2 information element gives parameters related to the multi-rate speech codec used in GAN Iu mode. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----------------| +| Multi-rate Configuration 2 IEI | | | | | | | | octet 1 | +| Length of Multi-rate Configuration 2 contents | | | | | | | | octet 2, 2a | +| If no more than four modes are present in the active codec set, the rest of the IE is coded the same as the Multi-rate Configuration IE in sub-clause 11.2.55, not including IEI and length. | | | | | | | | octet 3 | +| If five, six, seven or eight modes are present in the active codec set, the rest of the IE is coded as shown in Figure 11.2.104.2. The included Threshold and Hysteresis values shall be coded according to Table 11.2.55.1 and Annex D.1. | | | | | | | | ....
octet n | + +**Figure 11.2.104.1: Multi-rate Configuration 2 information element** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|------------------------|--------------|-------------|---|--------------|-------------|------------|---|----------|--|--|--| +| Set of AMR codec modes | | | | | | | | octet 4 | | | | +| Spare
0 | 0 | Threshold 1 | | | | | | octet 5 | | | | +| Hysteresis 1 | | | | Threshold 2 | | | | octet 6 | | | | +| Threshold
2 (cont.) | Hysteresis 2 | | | | Threshold 3 | | | octet 7 | | | | +| Threshold 3 (cont.) | | | | Hysteresis 3 | | | | octet 8 | | | | +| Spare
0 | 0 | Threshold 4 | | | | | | octet 9 | | | | +| Hysteresis 4 | | | | 0 | 0 | Spare
0 | 0 | octet 10 | | | | +| Spare
0 | 0 | Threshold 5 | | | | | | octet 11 | | | | +| Hysteresis 5 | | | | 0 | 0 | Spare
0 | 0 | octet 12 | | | | +| Spare
0 | 0 | Threshold 6 | | | | | | octet 13 | | | | +| Hysteresis 6 | | | | 0 | 0 | Spare
0 | 0 | octet 14 | | | | +| Spare
0 | 0 | Threshold 7 | | | | | | octet 15 | | | | +| Hysteresis 7 | | | | 0 | 0 | Spare
0 | 0 | octet 16 | | | | + +**Figure 11.2.104.2: Parameters for multirate speech field for the Multi-rate speech versions 1 & 2 when more than four modes is chosen** + +**Table 11.2.104.1: Multi-rate Configuration 2 information element** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Set of AMR codec modes
This field is coded the same as in the Multi-rate Configuration IE in sub-clause 11.2.55. | +| Threshold n, Hysteresis n (n = 1, 2 or 3)
These fields are included based on the rules for the Multi-rate Configuration IE in sub-clause 11.2.55. | +| Threshold 4, Hysteresis 4
Included when five, six, seven or eight modes are present in the active codec set. | +| Threshold 5, Hysteresis 5
Included when six, seven or eight modes are present in the active codec set. | +| Threshold 6, Hysteresis 6
Included when seven or eight modes are present in the active codec set. | +| Threshold 7, Hysteresis 7
Included when eight modes are present in the active codec set. | + +### 11.2.105 Selected Integrity Protection Algorithm + +The Selected Integrity Protection Algorithm information element specifies the integrity protection algorithm selected by the GANC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------------------------------|---|---|---|---|---|---|---|---------| +| Selected Integrity Protection Algorithm IEI | | | | | | | | octet 1 | +| Length of Selected Integrity Protection Algorithm value contents | | | | | | | | octet 2 | +| Selected Integrity Protection Algorithm | | | | | | | | octet 3 | + +**Figure 11.2.105.1: Selected Integrity Protection Algorithm information element****Table 11.2.105.1: Selected Integrity Protection Algorithm information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Selected Integrity Protection Algorithm
The Selected Integrity Protection Algorithm field consists of one octet with allowed values from 0 to 15. The values are as defined for the "Integrity Protection Algorithm" in [52]. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.106 Selected Encryption Algorithm + +The Selected Encryption Protection Algorithm information element specifies the encryption algorithm selected by the GANC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------|---|---|---|---|---|---|---|---------| +| Selected Encryption Algorithm IEI | | | | | | | | octet 1 | +| Length of Selected Encryption Algorithm value contents | | | | | | | | octet 2 | +| Selected Encryption Algorithm | | | | | | | | octet 3 | + +**Figure 11.2.106.1: Selected Encryption Algorithm information element****Table 11.2.106.1: Selected Encryption Algorithm information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Selected Encryption Algorithm
The Selected Encryption Algorithm field consists of one octet with allowed values from 0 to 15. The values are as defined for the "Encryption Algorithm" in [52]. | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.107 CN Domains to Handover + +The CN Domains to Handover information element indicates the core network domains (CS, PS or both CS and PS) that need to be handed over. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------|---|---|---|---|---|------|---|---------| +| CN Domains to Handover IEI | | | | | | | | octet 1 | +| Length of CN Domains to Handover value contents | | | | | | | | octet 2 | +| spare | | | | | | CNDH | | octet 3 | + +Figure 11.2.107.1: CN Domains to Handover information element + +Table 11.2.107.1: CN Domains to Handover information element + +| | +|-----------------------------------------------| +| CNDH, CN Domains to Handover (octet 3) | +| Bits | +| 2 1 | +| 0 0 Reserved | +| 0 1 CS domain only | +| 1 0 PS domain only | +| 1 1 Both CS and PS domains | + +### 11.2.108 3G Security Capability + +The 3G Security Capability information element indicates the 3G integrity protection and encryption algorithms that are supported by the MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------|---|---|---|---|---|---|---|-------------| +| 3G Security Capability IEI | | | | | | | | octet 1 | +| Length of 3G Security Capability value contents | | | | | | | | octet 2 | +| Ciphering Algorithm Capability | | | | | | | | octets 3, 4 | +| Integrity Protection Algorithm Capability | | | | | | | | octets 5, 6 | + +Figure 11.2.108.1: 3G Security Capability information element + +Table 11.2.108.1: 3G Security Capability information element + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ciphering Algorithm Capability | +| The coding of this field is as specified for the Ciphering Algorithm Capability in sub-clause 10.3.3.37 in [40]. For example, octet 3 bit 1 indicates support for the UEA0 algorithm, octet 3 bit 2 indicates support for the UEA1 algorithm, etc. | +| Integrity Protection Algorithm Capability | +| The coding of this field is as specified for the Integrity Protection Algorithm Capability in sub-clause 10.3.3.37 in [40]. For example, octet 3 bit 1 indicates support for the UIA1 algorithm, octet 3 bit 2 indicates support for the UIA2 algorithm, etc. | + +### 11.2.109 NAS Synchronisation Indicator + +The purpose of NAS Synchronisation Indicator IE is to provide the "Speech Codec Selection" information, as described in [8], to the MS. This information element contains transparent NAS information that is transferred from the CN to the MS without interpretation in the GANC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------|---|---|---|---|---|-----|---|---------| +| NAS Synchronisation Indicator IEI | | | | | | | | octet 1 | +| Length of NAS Synchronisation Indicator value contents | | | | | | | | octet 2 | +| spare | | | | | | NSI | | octet 3 | + +Figure 11.2.109.1: NAS Synchronisation Indicator information element + +**Table 11.2.109.1: NAS Synchronisation Indicator information element** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NSI , NAS Synchronisation Indicator Value (octet 3)
The coding of this field is as specified in the sub-clause "Speech Codec Selection" in [8].
The most significant bit is octet 3, bit 4. The least significant bit is octet 3, bit 1. | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.110 TEID + +The TEID information element identifies a GA-RRC packet transport channel tunnel endpoint. + +![](3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg) + +| | | | +|----------------------------------------------------|--|-----------| +| 8      7      6      5      4      3      2      1 | | | +| TEID IEI | | octet 1 | +| Length of TEID value contents | | octet 2 | +| TEID | | octet 3-6 | + +**Figure 11.2.110.1: TEID information element****Table 11.2.110.1: TEID information element** + +| | +|--------------------------------------------------------------------------| +| TEID , (octets 3-6)
The MSB is octet 3 and the LSB is octet 6. | +|--------------------------------------------------------------------------| + +### 11.2.111 UTRAN RRC Message + +The UTRAN RRC Message information element contains a UTRAN RRC message to be transported using the GA-RRC protocol between the MS and the GANC. + +![](315e87b80426782bb6e06222d653f515_img.jpg) + +| | | | +|----------------------------------------------------|--|-------------| +| 8      7      6      5      4      3      2      1 | | | +| UTRAN RRC Message IEI | | octet 1 | +| Length of UTRAN RRC Message IE contents | | octet 2, 2a | +| UTRAN RRC Message contents, 1st octet | | octet 3 | +| ... | | | +| UTRAN RRC Message contents, last octet | | octet n | + +**Figure 11.2.111.1: UTRAN RRC Message information element** + +### 11.2.112 MS Radio Access Capability + +The MS Radio Access Capability information element provides the GANC with information concerning radio aspects of the mobile station. + +![](9eba62b255ea4757497c72582d0fa54e_img.jpg) + +| | | | +|-----------------------------------------------------|--|-------------| +| 8      7      6      5      4      3      2      1 | | | +| MS Radio Access Capability IEI | | octet 1, 1a | +| Length of MS Radio Access Capability value contents | | octet 2 | +| MS RAC | | octet 3-n | + +**Figure 11.2.112.1: MS Radio Access Capability information element****Table 11.2.112.1: MS Radio Access Capability information element** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MS RAC , (octets 3-n)
The value is coded in the same way as the value part in the MS Radio Access Capability information element in TS 24.008 [8]. | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.113 Handover Reporting Control + +The Handover Reporting Control information element provides the MS with information concerning which cells/RATs may be reported during handover initiation.. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------|---|---|---|-------|---|-------|---|-------------| +| Handover Reporting Control IEI | | | | | | | | octet 1, 1a | +| Length of Handover Reporting Control value contents | | | | | | | | octet 2 | +| spare | | | | HO_3G | | HO_2G | | octet 3 | + +**Figure 11.2.113.1: Handover Reporting Control information element** + +The HO\_2G and HO\_3G indications specify whether a mobile may indicate a 2G (respectively 3G) cell as part of a handover initiation procedure (see sub-clauses 7.8.1, 8.14.1). If both of these bits are set to '1' the mobile station shall treat these bits as set to '0'. + +**Table 11.2.113.2: HO\_2G, HO\_3G** + +| HO_2G, HO_3G (octet 3, bits 1,2) | | +|----------------------------------|---------------------------| +| 0 | MS may report cells | +| 1 | MS shall not report cells | + +### 11.2.114 Tracking Area Identity + +The Tracking Area Identity (TAI) information element consists of a TAC, MNC and MCC (see [54]). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|-----------|---|---|---|-------------| +| Tracking Area Identity IEI | | | | | | | | octet 1, 1a | +| Length of Tracking Area Identity IE contents | | | | | | | | octet 2 | +| MCC dig 2 | | | | MCC dig 1 | | | | octet 3 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 4 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 5 | +| Tracking Area Code | | | | | | | | octet 6-7 | + +**Figure 11.2.114.1: Tracking Area Identity information element** + +**Table 11.2.114.1: Tracking Area Identity information element** + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Tracking Area Code, (octets 6-7)
This is a 16-bit value, with the most significant bit is octet 7 bit 8 and the least significant bit is octet 8 bit 1. | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.115 E-UTRAN Cell Identity + +The E-UTRAN Cell Identity information element consists of a 28-bit Cell ID (see [55]). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------|---|---|---|---|---|---|---|-------------| +| E-UTRAN Cell Identity IEI | | | | | | | | octet 1, 1a | +| Length of E-UTRAN Cell Identity IE contents | | | | | | | | octet 2 | +| E-UTRAN Cell ID | | | | | | | | octet 3-6 | + +**Figure 11.2.115.1: E-UTRAN Cell Identity information element** + +**Table 11.2.115.1: E-UTRAN Cell Identity information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRAN Cell ID, (octets 3-6)
This is a 28-bit value, with the most significant bit in octet 4 bit 8 and the least significant bit in octet 7 bit 5. Octet 7 bits 1-4 are spare. | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.2.116 E-UTRAN Camping Indicator + +The E-UTRAN Camping Indicator information element is used to indicate that the MS is camped on a E-UTRAN cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------|---|---|---|---|---|---|---|-------------| +| E-UTRAN Camping Indicator IEI | | | | | | | | octet 1, 1a | +| Length of E-UTRAN Camping Indicator IE contents | | | | | | | | octet 2 | +| ECI | | | | | | | | octet 3 | + +**Figure 11.2.116.1: E-UTRAN Camping Indicator information element** + +**Table 11.2.116.1: E-UTRAN Camping Indicator information element** + +| ECI, (octet 3) | | +|----------------|---------------------------------------------------------| +| 0 | MS is camped on a E-UTRAN cell in Normal Service state | +| 1 | MS is camped on a E-UTRAN cell in Limited Service state | +| 2 | MS is camped on a E-UTRAN cell in unknown service state | +| 3-255 | All other values are reserved. | + +### 11.2.117 Bandwidth-efficient Mode Indicator + +The Bandwidth-efficient Mode Indicator information element indicates that RFC 4867 [11] bandwidth-efficient mode shall be used for the GA-CSR traffic channel. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Bandwidth-efficient Mode Indicator IEI | | | | | | | | octet 1, 1a | +| Length of Bandwidth-efficient Mode Indicator value contents | | | | | | | | octet 2 | +| BMI | | | | | | | | octet 3 | + +**Figure 11.2.117.1: Bandwidth-efficient Mode Indicator information element** + +**Table 11.2.117.1: Bandwidth-efficient Mode Indicator information element** + +| BMI, Bandwidth-efficient Mode Indicator (octet 3) | | +|---------------------------------------------------|--------------------------------------------| +| 0 | Reserved | +| 1 | Use RFC 4867 [11] bandwidth-efficient mode | +| 2 to 255 | Reserved | + +# 12 List of system parameters + +The information provided in sub-clauses 12.1 and 12.2 shall be treated as informative. The normative text is specified in the relevant sub-clauses and shall prevail. + +## 12.1 Timers and counters + +### 12.1.1 Timers on the mobile station side + +All the timers listed below except TU3910 and TU3906 shall be stopped when the MS exits GAN mode. + +**Table 12.1.1.1: Timer on the mobile station side** + +| Timer | Start | Stop | At expiry | Value Setting | +|--------------|----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| TU3901 | Sending of GA-RC DISCOVERY REQUEST | Reception of GA-RC DISCOVERY ACCEPT or GA-RC DISCOVERY REJECT or Lower layer failure as defined in section 5.6.2. | See sub-clause 5.6.1. | 30 seconds. | +| TU3902 | Reception of GA-RC DISCOVERY REJECT with Reject Cause value 'network congestion' | -. | See sub-clause 5.6.3. | Received from the GANC as TU3902 Timer IE. Value in TU3902 Timer IE + a random value between 0 and the value in TU3902 Timer IE | +| TU3903 | TU3901 expiry or Lower layer failure as defined in section 5.6.2. | -. | See sub-clause 5.6.4. | Initial value is 1 minute.

Maximum value is 32 minutes. | +| TU3904 | Sending of GA-RC REGISTER REQUEST | Reception of GA-RC REGISTER ACCEPT or GA-RC REGISTER REJECT or GA-RC REGISTER REDIRECT or Lower layer failure as defined in section 6.2.4.2. | See sub-clause 6.2.4.1. | 30 seconds. | +| TU3905 | TU3904 expiry or Lower layer failure as defined in sections 6.2.4.2 and 9.5 or reception of GA-RC DEREGISTER | -. | See sub-clause 6.2.4.3. | 10 seconds. | +| TU3906 | Reception of GA-RC REGISTER ACCEPT and at TU3906 expiry | See sub-clauses 6.5 and 9.5. | Send GA-RC KEEP ALIVE and restart TU3906 | Received from the GANC as TU3906 Timer IE. | +| TU3907 | Reception of GA-RC REGISTER REJECT or GA-RC DEREGISTER with Reject Cause value 'network congestion' | Lower layer failure as defined in section 6.2.4.2. | See sub-clause 6.2.4.4. | Received from the GANC as TU3907 Timer IE. Value in TU3907 Timer IE + a random value between 0 and value in TU3907 Timer IE | +| TU3908 | Sending of GA-CSR REQUEST | Reception of GA-CSR REQUEST ACCEPT or GA-CSR REQUEST REJECT | See sub-clause 7.1.4.1. | 5 seconds. | +| TU3909 | Sending of GA-CSR CLEAR REQUEST | Reception of GA-CSR RELEASE | See sub-clause 7.5.5. | 5 seconds. | +| TU3910 | At rove out or at reception of GA-RC REGISTER UPDATE DOWNLINK | When MS detects loss of GERAN coverage or reception of GA-RC REGISTER UPDATE DOWNLINK or GA-RC REGISTER REDIRECT | The MS is allowed to rove-in | Received from the GANC as TU3910 Timer IE. | +| TU3911 | Sending of GA-CSR ACTIVATE CHANNEL ACK | Reception of GA-CSR ACTIVATE CHANNEL COMPLETE | See sub-clause 7.4.5. | 5 seconds. | +| TU3920 | GAN A/Gb mode:
Sending of GA-CSR HANDOVER ACCESS

GAN Iu mode:
Sending of GA-RRC RELOCATION ACCESS | GAN A/Gb mode:
Reception of GA-CSR ACTIVATE CHANNEL COMPLETE

GAN Iu mode:
Reception of GA-RRC ACTIVATE CHANNEL COMPLETE | GAN A/Gb mode:
See sub-clause 7.7.5.

GAN Iu mode:
See sub-clause 8a.10.5. | Received from the GANC as TU3920 Timer IE. | + +| Timer | Start | Stop | At expiry | Value Setting | +|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|--------------------------------------------| +| TU4001 | GAN A/Gb mode:
Reception of GA-PSR-ACTIVATE-UTC-ACK or at sending or receiving of GA-PSR-UNITDATA

GAN Iu mode:
Reception of GA-RRC ACTIVATE CHANNEL COMPLETE (for PS domain) or at sending or receiving of GA-RRC PDU for a particular PTC | GAN A/Gb mode: Sending or receiving of GA-PSR-UNITDATA (and restart the timer)

GAN Iu mode:
Sending or receiving of GA-RRC PDU for the same PTC (and restart the timer) | GAN A/Gb mode: See sub-clause 8.4.1.

GAN Iu mode:
See sub-clause 8a.9. | Received from the GANC as TU4001 Timer IE. | +| TU4002 | Sending of GA-PSR-ACTIVATE-UTC-REQ or sending GA-PSR-DEACTIVATE-UTC-REQ | Reception of GA-PSR-ACTIVATE-UTC-ACK or reception of GA-PSR-DEACTIVATE-UTC-ACK | See sub-clause 8.2.4.2 and sub-clause 8.4.4.1 | 5 seconds. | +| TU4003 | Sending of GA-PSR-DFC-REQ | - | See sub-clause 8.11.3 | Received from the GANC as TU4003 Timer IE. | +| TU4004 | Sending of GA-PSR HANDOVER INFORMATION message to the network or receiving a GA-PSR HANDOVER CONTINUE message from the network | Reception of a GA-PSR HANDOVER COMMAND message. | Rove-out to GERAN/UTRAN mode or remain in GAN mode. | Received from the GANC as TU4004 Timer IE. | +| TU5002 | Sending of GA-RRC DEACTIVATE CHANNEL REQUEST for a particular domain (CS or PS) | Reception of GA-RRC RELEASE or GA-RRC DEACTIVATE CHANNEL for the same domain | See sub-clause 8a.8. | 5 seconds. | +| TU5908 | Sending of GA-RRC REQUEST | Reception of GA-RRC REQUEST ACCEPT or GA-RRC REQUEST REJECT | See sub-clause 8a.1. | 5 seconds. | +| TU5909 | Sending of GA-RRC RELEASE REQUEST | Reception of GA-RRC RELEASE | See sub-clause 8a.5. | 5 seconds. | +| TU5911 | Sending of GA-RRC ACTIVATE CHANNEL ACK | Reception of GA-RRC ACTIVATE CHANNEL COMPLETE | See sub-clause 8a.4. | 5 seconds. | + +### 12.1.2 Timers on the network side + +No timers are defined on the network side in this version of this specification. + +## 12.2 Other system parameters + +### 12.2.1 TCP related parameters and system parameters + +TCP port for Discovery is port number 14001. + +TCP port for Registration is port number 14001. + +The MS should ensure that the small packets containing each signalling message are sent immediately. For example, this can be done by using the standard TCP socket options (e.g., TCP\_NODELAY to disable Nagle's algorithm). + +The MS shall not normally release the TCP connection to the GANC, while it is registered with a GANC. + +Once the TCP connection is released, the IPsec tunnel can also be released unless this tunnel will be used for subsequent registration. + +### 12.2.2 (void) + +### 12.2.3 MS system parameters + +| Parameter Name | Value | +|----------------------------------|-------| +| Up Register Max Retries | 3 | +| Up Connect Attempt Count | 3 | +| AP Black list size minimum | 1 | +| Location Black List size minimum | 1 | + +| Parameter Name | Initial Value | +|------------------------------|----------------| +| Serving GANC Table indicator | "Do Not Store" | + +# Annex A (informative): RTP Framing for CS-domain Services + +## A.1 RFC 4867 Framing + +RFC 4867 [48] defines the RTP payload format for AMR and AMR-WB codecs. There are two operation modes for the payload format referred to as: bandwidth-efficient mode and octet-aligned mode. Only octet-aligned mode is applicable to GAN. + +### A.1.1 (void) + +#### A.1.1a Codec and Redundancy Mode Example + +![Diagram showing the relationship between CODEC_MODE (No redundancy, Single Redundancy, Double Redundancy) and thresholds (THR_2 - HYST_2, THR_2, THR_1 - HYST_1, THR_1) for increasing FLR. CODEC_MODE_3 (No redundancy) is associated with THR_2 - HYST_2 and THR_2. CODEC_MODE_2 (Single Redundancy) is associated with THR_1 - HYST_1 and THR_1. CODEC_MODE_1 (Double Redundancy) is associated with THR_1. An arrow points downwards indicating increasing FLR.](497d7e14540664a2914557cad79f3791_img.jpg) + +Diagram showing the relationship between CODEC\_MODE (No redundancy, Single Redundancy, Double Redundancy) and thresholds (THR\_2 - HYST\_2, THR\_2, THR\_1 - HYST\_1, THR\_1) for increasing FLR. CODEC\_MODE\_3 (No redundancy) is associated with THR\_2 - HYST\_2 and THR\_2. CODEC\_MODE\_2 (Single Redundancy) is associated with THR\_1 - HYST\_1 and THR\_1. CODEC\_MODE\_1 (Double Redundancy) is associated with THR\_1. An arrow points downwards indicating increasing FLR. + +**Figure A1.1a.1: Codec and Redundancy Mode example** + +The receiver is currently using Codec Mode 3 with no redundancy. + +If the frame loss rate increases over Threshold 2, then the receiver indicates this to the sender by requesting an AMR mode for which single redundancy is used (as signaled in the Redundancy Configuration IE). This configuration is kept until frame loss rate is again lower than Threshold 2 - Hysteresis 2. The receiver indicates this by again requesting a higher AMR mode. By this redundancy mode is also implicitly requested to be no redundancy. + +If instead network conditions degrade even more and frame loss rate increases over Threshold 1, the receiver indicates this to sender by requesting an AMR mode for which double redundancy is used (as signaled in the Redundancy Configuration IE). The sender then switches to double redundancy and the requested AMR mode. This configuration is kept until frame success rate is again better than Threshold 1 - Hysteresis 1. The receiver indicates this by again requesting a higher AMR mode. By this redundancy mode is also implicitly requested to be single redundancy. + +### A.1.2 RFC 4867 Octet-aligned Frame Examples + +With RFC 4867 the RTP payload begins with a Codec Mode Request (CMR) field, followed by a number of Table of Content (ToC) entries, and speech data representing one or more speech frame-blocks. In octet-aligned mode, the CMR and ToC fields are padded to an octet. The following diagram shows the general payload format layout: + +![Diagram showing the general payload format layout for octet-aligned mode. It shows a sequence of octets (0-15) with fields: CMR (octet 0), FT (octets 1-2), ToC (octets 3-4), FT (octets 5-6), ToC (octets 7-8), and speech data (octets 9-15).](f36118fd962bd69a26082021de657b71_img.jpg) + +``` + +0 1 2 3 +0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| CMR |R|R|R|R|F| FT |Q|P|P|F| FT |Q|P|P| speech data | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + ToC ToC +|<----->|<----->| + +``` + +Diagram showing the general payload format layout for octet-aligned mode. It shows a sequence of octets (0-15) with fields: CMR (octet 0), FT (octets 1-2), ToC (octets 3-4), FT (octets 5-6), ToC (octets 7-8), and speech data (octets 9-15). + +**CMR (Codec Mode Request):** is used for rate adaptation. The value of the CMR field is set to the frame type index of the corresponding speech mode being requested. The frame type index may be 0-7 for AMR, or 0-8 for AMR-WB, as defined in [48]. CMR value 15 indicates that no mode request is present, and other values are for future use. + +**FT (Frame Type index):** indicates either the AMR or AMR-WB speech coding mode or comfort noise (SID) mode of the corresponding frame carried in this payload. E.g. in case of AMR speech, a value of FT=7 indicates that this frame carries AMR 12.2 sample(s). + +**Q (frame Quality indicator):** if set to 0, indicates that the corresponding frame is severely damaged. + +The **F** bit indicates whether another speech frame follows in the same payload (F=1) or if this frame is the last frame in the payload (F=0). + +**R** and **P** stand for reserved and padding bits, respectively. + +The following diagram shows an octet-aligned AMR payload carrying one AMR 12.2 speech frame-block: + +![Diagram of an octet-aligned AMR payload structure showing fields like CMR, FT, Q, P, and f1 across four octets (0-3).](f8d508872d762c83336443cfd20c5412_img.jpg) + +The diagram illustrates the structure of an octet-aligned AMR payload. It is divided into four octets, labeled 0, 1, 2, and 3 at the top. Each octet contains 8 bits, numbered 0 through 7. The payload is shown as a series of bytes, with the first byte (Octet 0, bits 0-7) containing the following fields: CMR=15 (bits 0-4), R (bit 5), R (bit 6), R (bit 7), and F (bit 8, which is part of the next octet). The second byte (Octet 1, bits 0-7) contains FT=7 (bits 0-3), Q (bit 4), P (bit 5), P (bit 6), and P (bit 7). The remaining bytes (Octets 2 and 3, and subsequent octets) contain the f1 field, which represents the speech data. The f1 field is shown in segments: f1(0..7), f1(8..15), f1(16..23), followed by several ellipses (....) indicating more data, and finally f1(232..239) and f1(243). The payload ends with four padding bits (P P P P). + +Diagram of an octet-aligned AMR payload structure showing fields like CMR, FT, Q, P, and f1 across four octets (0-3). + +The following diagram shows an octet-aligned AMR payload carrying two AMR 12.2 speech frame-blocks: + +![](9874e3ac6f14360133f8e1674f79824f_img.jpg) + +``` + + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| CMR=15|R|R|R|R|1| FT=7 |Q|P|P|0| FT=7 |Q|P|P| f1(0..7) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| f1(8..15) | f1(16..23) | .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| f1(232..239) |f1(243)|P|P|P|P| f2(0..7) | f2(8..15) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| .... | f1(232..239) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +|f2(243)|P|P|P|P| ++-+-+-+-+-+-+-+-+ + +``` + +NOTE: The last octet in both speech frames is padded with four 0s to make it octet-aligned. + +The following diagram shows an octet-aligned AMR payload carrying one AMR 12.2 speech frame-block (FT=7) and one AMR SID frame (FT=8; 39 bits): + +![Diagram of an octet-aligned AMR payload with 4 octets. It shows fields for CMR, R, FT, Q, P, and speech frames f1 and f2 with bit ranges.](f5698523df298c80a0c6b5d4ca657993_img.jpg) + +``` + +0 1 2 3 +0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| CMR=15| R| R| R| R| 1| FT=7 | Q| P| P| 0| FT=8 | Q| P| P| f1(0..7) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| f1(8..15) | f1(16..23) | . . . . | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| . . . . | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| . . . . | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| . . . . | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| . . . . | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| . . . . | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| f1(232..239) | f1(243) | P| P| P| P| f2(0..7) | f2(8..15) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| f2(16..23) | f2(24..31) | f2(32..38) | P| ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +``` + +Diagram of an octet-aligned AMR payload with 4 octets. It shows fields for CMR, R, FT, Q, P, and speech frames f1 and f2 with bit ranges. + +The following diagram shows an octet-aligned AMR payload carrying one AMR SID frame (FT=8; 39 bits) as defined in Sections 7.4.3 and 7.4.4 of the main body of this specification for Discontinuous Transmission (DTX): + +![Diagram of an octet-aligned AMR payload for DTX with 4 octets. It shows fields for CMR, R, FT, Q, P, and speech frames f1 and f2 with bit ranges.](6bc05e56e8453678a84fa6bdba3fd903_img.jpg) + +``` + +0 1 2 3 +0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| CMR=15| R| R| R| R| 0| FT=8 | Q| P| P| f1(0..7) | f2(8..15) | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| f2(16..23) | f2(24..31) | f2(32..38) | P| ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +``` + +Diagram of an octet-aligned AMR payload for DTX with 4 octets. It shows fields for CMR, R, FT, Q, P, and speech frames f1 and f2 with bit ranges. + +The following diagram shows an octet-aligned AMR payload carrying one AMR NO\_DATA frame (FT=15; 0 bits) as defined in Sections 7.4.3 and 7.4.4 of the main body of this specification when no speech or SID frame is available for a period of 480 ms: + +![Diagram of an octet-aligned AMR payload for NO_DATA with 2 octets. It shows fields for CMR, R, FT, Q, and P.](4bb56f4af58f9d5daab52d98c984d8d5_img.jpg) + +``` + +0 1 +0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +| CMR=15| R| R| R| R| 0| FT=15 | Q| P| P| ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +``` + +Diagram of an octet-aligned AMR payload for NO\_DATA with 2 octets. It shows fields for CMR, R, FT, Q, and P. + +Note that the preceding format shown above that results when no speech or SID frame is received for 480 ms is necessary per Section 7.4.3 and Section 7.4.4. But this formatting is an intentional deviation from Section 4.3.2 of RFC 3267, which says a packet containing only NO\_DATA frames should not be transmitted. + +## A.2 (HS)CSD Framing over RTP + +For radio interface rate of 3.6 kbps, the Terminal Adaptation Function (TAF) in the MS produces a 72-bit frame every 20 ms. For transmission in RTP [35], this 72-bit frame is packed into a 9 octet payload. The format of this 72-bit frame is defined in [13]. + +For radio interface rate of 6 kbps, the Terminal Adaptation Function (TAF) in the MS produces a 120-bit frame every 20 ms. For transmission in RTP [35], this 120-bit frame is packed into a 15 octet payload. The format of this 120-bit frame is defined in [13]. + +For radio interface rate of 12 kbps, the Terminal Adaptation Function (TAF) in the MS produces a 240-bit frame every 20 ms. For transmission in RTP [35], this 240-bit frame is packed into a 30 octet payload. The format of this 240-bit frame is defined in [13]. + +For radio interface rate of 14.5 kbps, the Terminal Adaptation Function (TAF) in the MS produces a 290-bit frame every 20 ms. For transmission in RTP [35], this 290-bit frame is packed into a 37 octet payload beginning with a 6-bit signature (binary 001100). The format of this 290-bit frame is defined in [13]. + +For radio interface rate of 29 kbps, the Terminal Adaptation Function (TAF) in the MS produces a 580-bit frame every 20 ms. For transmission in RTP [35], this 580-bit frame is packed into a 73 octet payload beginning with a 4-bit signature (binary 1100). The format of this 580-bit frame is defined in [13]. + +For radio interface rate of 43.5 kbps, the Terminal Adaptation Function (TAF) in the MS produces a 870-bit frame every 20 ms. For transmission in RTP [35], this 870-bit frame is packed into a 109 octet payload beginning with a 2-bit signature (binary 01). The format of this 870-bit frame is defined in [13]. + +Radio interface rate of 32kbps is FFS. + +The IETF has defined RFC 4040 ("RTP Payload Format for a 64 kbit/s Transparent Call") [51]. This RFC shall be used for the 64 kbps circuit switched bearer required (for example) for a CS video call supported in GAN mode. + +# --- Annex B (normative): Network QoS + +## B.1 Introduction + +The GAN-MS shall check DSCP/ToS information in incoming IP packets from the GANC and if different from what currently used, copy received DSCP/ToS and use it for outgoing IP packets. + +For a tunnel mode SA, there is an "outer" IP header that specifies the IPsec processing destination, plus an "inner" IP header that specifies the ultimate destination for the packet. + +## --- B.2 Network behaviour + +When the GANC-SEGW receives an IP packet from the GANC, it shall make sure that the DSCP (DiffServ Code Point) values from the 'inner' IP header are mapped to the 'outer' IP header (according to operator configuration) before forwarding the packet to the MS using the established SA. When several flows are using the same IPsec tunnel and have a different QoS, e.g. a PS streaming class flow and a PS background flow, the GANC may decide to assign a specific DSCP value for each flow identified by its Packet Flow Identifier. + +## --- B.3 MS behaviour + +### B.3.1 Receiving of data + +#### B.3.1.1 Outer IP packet + +When the MS receives an encrypted IP packet, it shall store the DSCP value from the 'outer' IP header in the context of this IPsec SA for this inner DSCP value. + +#### B.3.1.2 Inner IP packet + +Furthermore, the MS shall perform the following actions when handling the received IP packet and UDP datagram or TCP data in the application layer (i.e. GA-RC, GA-CSR or GA-PSR layers): + +- For a received RTP/UDP packet, read the DSCP value from the 'inner' IP header (i.e. using the UDP socket for the traffic channel). If this value is different from what is currently being used for this RTP/UDP stream, then save the received DSCP value and use it for all outgoing RTP/UDP packets for this traffic channel (one way to achieve this is to set the DSCP value for the UDP socket). +- For a received GA-PSR-UNITDATA message, read the DSCP value from the 'inner' IP header. If this value is different from what is currently being used for this flow within the GA-PSR TC, then save the received DSCP value and use it for all outgoing GA-PSR-UNITDATA messages on this flow within the GA-PSR TC. +- For a received GA-RC message, GA-CSR message or GA-PSR message containing signalling or SMS, read the DSCP value from the 'inner' IP header (i.e. using the TCP socket for the TCP connection to the GANC). If this value is different from what is currently being used for this TCP connection, then save the received DSCP value and use it for all outgoing GA-RC messages, GA-CSR messages and GA-PSR messages containing signalling or SMS (one way to achieve this is to set the DSCP value for the TCP socket). + +### B.3.2 Sending of data + +When the MS is sending an IP packet to the GANC, it shall make sure that the DSCP (DiffServ Code Point) values for the 'inner' IP header are computed from the received IP packets, as described in B.3.1.2 above. Further, the DSCP value for the 'outer' IP header is obtained from the stored value in the IPSec SA context for this inner DSCP value, as described in B.3.1.1 above, before forwarding the packet to the GANC-SEGW using the established SA. + +# --- Annex C (normative): (Source-RAT) Measurement Report for Handover and Cell Change Order to GAN + +## C.1 Measurement Report for Handover and Cell Change Order to GAN A/Gb mode + +The MS uses the (Source-RAT) measurement report procedure to "request" handover to GANA/Gb mode for voice call or signalling session. It also uses it to "request" a Cell Change Order to GAN A/Gb mode for packet data session. + +The procedure is initiated after the MS has successfully registered with the GANC, provided the following conditions are met: + +- the MS stays registered with GANC; +- the GANC directs the MS to operate in GAN A/Gb mode; +- the GANC includes the IE "GAN Cell Description" in the GA-RC REGISTER ACCEPT message; +- if the source RAT is GERAN/UTRAN, and the MS is in dedicated mode (signalling only or speech mode), network has requested reports according to NETWORK\_CONTROL\_ORDER or in DTM mode (simultaneous dedicated mode and packet transfer mode) or UTRA RRC Connected Mode for CS domain services; +- the ARFCN provided by the GANC (i.e. the GAN-ARFCN) is within the cell info list used for measurement reporting in the source RAT; +- no GSM neighbour cell matching the {GAN-ARFCN, GAN-BSIC} couple has been detected by the MS. + +The MS shall not be connected to more than one GANC at any one time, and therefore shall not report more than one {GAN-ARFCN, GAN-BSIC} couple during the period of the connection to the GANC. + +The RR entity in the source RAT shall report that the cell associated with the {GAN-ARFCN, GAN-BSIC} couple has the best possible receiving level (i.e., RxLev = 63). + +## --- C.2 Measurement Report for Handover and Cell Change Order to GAN Iu mode + +The MS uses the (Source-RAT) measurement report procedure to "request" handover to GAN Iu mode for CS, PS or both CS and PS sessions. It also uses it to "request" a Cell Change Order from GERAN to GAN Iu mode for PS sessions. + +The procedure is initiated after the MS has successfully registered with GANC, provided the following conditions are met: + +- the MS stays registered with GANC; +- the GANC directs the MS to operate in GAN Iu mode; +- the GANC includes the IE "GAN Iu Mode Cell Description" in the GA-RC REGISTER ACCEPT message; +- if the source RAT is GERAN, the MS is in dedicated mode and the network has requested reports according to NETWORK\_CONTROL\_ORDER or in DTM mode (simultaneous dedicated mode and packet transfer mode); +- if the source RAT is UTRAN, the MS is in UTRA RRC Connected Mode (i.e., for CS domain, PS domain or both CS and PS domain services); +- the UARFCN and Primary Scrambling Code provided by GANC in the IE "GAN Iu Mode Cell Description" (i.e. the GAN-UARFCN and GAN-PSC) are within the cell info list used for measurement reporting in the source RAT; +- no UTRAN neighbour cell matching the {GAN-UARFCN, GAN-PSC} couple has been detected by the MS. + +The MS shall not be connected to more than one GANC at any one time, and therefore shall not report more than one {GAN-UARFCN, GAN-PSC} couple during the period of the connection to the GANC. + +The RR entity in the source RAT shall report that the cell associated with the {GAN-UARFCN, GAN-PSC} couple has the best possible receiving level (i.e., RSCP = 91 or Ec/No=63). + +# --- Annex D (normative): RFC 4867 Framing Parameters for GAN + +## D.1 RFC 4867 Framing Parameters for GAN + +When carrying AMR or AMR-WB voice in GAN, the following RTP framing parameters shall be used: + +- Octet-aligned +- No frame CRCs +- No robust sorting +- No frame interleaving +- Single channel per session +- Mode-change-period = 2 i.e. mode can change every 2nd speech frame +- Mode-change-neighbor = 1 i.e. mode can only change to neighbouring mode in the active mode set +- Mode-set: signalled in *Multirate Configuration IE* +- Forward error correction: single or double retransmission of the previously transmitted frame (s) (i.e. window size of 2 or 3). To request a concurrent AMR and redundancy mode adaptation, the decoder (speech receiver) signals the encoder (speech sender) the new AMR mode it prefers in Codec Mode Request (CMR). The redundancy mode for each mode of the Active Codec Set is signaled in the Redundancy Configuration IE. This way the preferred redundancy mode is also implicitly requested with the CMR. (Triple redundancy is not used, as it would add too much network load. When the third redundant frame has to be used, there would also be too long delays.) + +The frame loss rate for the received speech data is continuously monitored by the MS and the network. If the sender is currently using codec mode N where increasing N means a codec mode with higher bitrate, the following applies. + +- When the frame loss rate goes above Threshold N-1, the receiver signals the sender to change to codec mode N-1 and thereby also to the redundancy mode associated with codec mode N-1. +- When the frame loss rate goes below Threshold N - Hysteresis N, the receiver signals the sender to change to codec mode N+1 and thereby also to the redundancy mode associated with codec mode N+1. + +The frame loss rate threshold and hysteresis values used for triggering a switch in AMR mode shall be given by the network in a consistent order, i.e. such that: + +- $THR\_1 \geq THR\_2 \geq THR\_3$ , and +- $THR\_1 - HYST\_1 \geq THR\_2 - HYST\_2 \geq THR\_3 - HYST\_3$ . + +The initial codec mode, and associated redundancy mode, to use, is signaled in Multirate Configuration IE, at channel activation or at channel mode modify. + +# --- Annex E (normative): GAN Specific Requirements for Interworking with UTRAN + +## E.1 GAN A/Gb Mode Specific Requirements for Interworking with UTRAN + +The UE shall include the *Support of Handover to GAN* indication in the UE Radio Access Capabilities provided to the RNC. + +NOTE: The RNC support of functionality for UTRAN to GAN Handover is implied by the inclusion of the ARFCN for GAN in the neighbour cell list of the UE. + +The GAN and GERAN capable UE shall conform to all the requirements for Inter-RAT events as defined in TS 25.331 for reporting GERAN cells. + +W.r.t. reporting GAN cells, the UE can be in one of two modes: + +GAN preferred: the UE prefers to stay in GAN rather than GERAN or UTRAN. + +GERAN/UTRAN preferred: the UE prefers to stay in GERAN/UTRAN rather than GAN; + +Reporting of GAN cells is only performed with event 3A; GAN cells are never reported by events 3B, 3C, 3D or periodic reporting. + +The GAN capable UE shall conform to all the requirements for Inter-RAT measurement reporting as defined in TS 25.331 for reporting of GAN cells, except when stated below: + +- For the reporting of a GAN cell in case of configured event 3A, the UE shall act on the information originally received in the Measurement Control message as follows: + - Treat the value of the "Hysteresis" parameter as 0. + - Ignore the "Threshold other system" parameter. + - Treat the value of the "Time to trigger" parameter as 0ms. +- When the UE is in GAN preferred mode and an event 3A has been configured, the UE shall in addition act on the information originally received in the Measurement Control message, as follows: + - Treat the value of the "Threshold own system" parameter as 0. + +As a result, the UE can report a GAN cell whenever it has successfully registered on a GANC; + +- When the UE is in GERAN/UTRAN preferred mode and an event 3A has been configured, the UE shall only send a measurement about the GAN cell to trigger handover when no GERAN cells from the Inter-RAT measurement object list satisfy the triggering condition of the configured Event (as described in TS 25.331). +- When the UE is in GAN preferred mode and an event 3A has been configured, the UE may send a measurement about the GAN cell to trigger handover immediately following successful registration on the GANC. +- When the UE is sending an event 3A related measurement report about a GAN cell in order to trigger handover, the UE shall report that the GAN cell has the best possible receiving level (i.e., GSM carrier RSSI = 63) and therefore complies with the "threshold other system" signalled in the information originally received in the Measurement Control message. + +NOTE: If the UE is in GAN preferred mode and an event 3A has been configured, it does not need to make inter-RAT measurements prior to including GAN cell information in the Measurement Report message sent to the UTRAN to trigger handover to GAN. + +- The UE shall not include GAN cells in other Inter-RAT measurement reporting than when triggered by event 3A. + +- If an event 3A is configured only with Inter-RAT cells not within any of the GERAN bands supported by the UE (as specified by the IE "Inter-RAT measurements object list" and taking into account any restriction configured by the IE "cell for measurement") this event shall not be counted as an Inter-RAT reporting criterion with respect to the UE capability for the Inter-RAT measurement category. +- If the UE fails to complete the handover to GAN as requested by the Handover From UTRAN Command message (e.g. UE loses connection to GAN), it shall act as in the handover failure case specified in TS 25.331. + +The selection of the RF channel number (ARFCN) used for the UTRAN to GAN handover procedure should not correspond to a channel from any frequency band defined in TS 45.005, to avoid UEs not requiring compressed mode for GSM measurements from unnecessarily powering up their GSM receivers. + +## E.2 GAN Iu Mode Specific Requirements for Interworking with UTRAN + +When operating in GAN Iu mode, the GANC emulates a UTRAN RNC to the rest of the network. Therefore, the UTRAN to GAN and GAN to UTRAN handovers are considered to be intra-system (UTRAN-to-UTRAN) handovers. This differs from the GAN A/Gb mode case where UTRAN to GAN and GAN to UTRAN handovers are considered to be inter-system (i.e., inter-RAT) handovers. + +In addition to the procedures described in sub-clauses 8a.10 and 8a.11, the following procedures shall be followed with respect to GAN Iu mode handover to and from UTRAN: + +1. When a UTRAN to GAN Iu mode to UTRAN handover sequence occurs: + - The GANC shall retain the Chosen Integrity Protection Algorithm (CIPA), Chosen Encryption Algorithm (CEA), Integrity Key (IK), Ciphering Key (CK) and COUNT parameters received from the source RNC. The GAN shall relay these parameters to the target RNC. + - The MS shall store the START values that are in effect when entering GAN Iu mode. The MS shall provide the START values to the GANC (i.e., in the GA-RRc RELOCATION INFORMATION message) and the GANC shall forward the START values with the other parameters (described above) to the target RNC. +2. When a UTRAN to GAN Iu mode handover occurs (i.e., other than described in bullet 1 above): + - The MS shall store the START values that are in effect when entering GAN Iu mode. When the MS transitions to the idle state (i.e., GA-RRc IDLE state for both CS and PS domains) while in GAN Iu mode, then the MS shall compare the START values with THRESHOLD and set the START values and key status as described in TS 25.331 [40] (i.e., behave as if the connection was released in UTRAN). +3. When a GAN Iu mode to UTRAN handover occurs (i.e., other than described in bullet 1 above): + - The GANC relays the RRC message (e.g., Physical Channel Reconfiguration) provided by the target RNC in the Relocation Request Ack message to the MS in the GA-RRc RELOCATION COMMAND. This message includes the Integrity Protection Activation Info which includes the FRESH value. + - The GANC shall include the current settings for the security algorithms and keys (e.g., CIPA, IK, CEA, and CK parameters) in the Source RNC to Target RNC Transparent Container. + - The GANC shall obtain the START value(s) from the MS (i.e., in the GA-RRc RELOCATION INFORMATION message) and include them in the RRC Container sent to the target RNC in the Source RNC to Target RNC Transparent Container parameter. + - The GANC shall initialize the relevant COUNT value(s) to zero and include them in the RRC Container sent to the target RNC in the Source RNC to Target RNC Transparent Container parameter. + +# Annex F (normative): 3G Cell Identity coding + +## F.1 3G Cell Identity coding – 28 bitstring + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|---|---|---|-------|---|---|---|-----------| +| 3G Cell Identity | | | | | | | | octet n | +| 3G Cell Identity cont. | | | | | | | | octet n+1 | +| 3G Cell Identity cont. | | | | | | | | octet n+2 | +| 3G Cell Identity cont. | | | | Spare | | | | octet n+3 | + +Figure F1.1.1: 3G Cell Identity information element + +The 3G Cell Identity is defined in 3GPP TS 25.331 and further clarified in 3GPP TS 25.401 as a 28 bit variable, which in the Up protocol has to be included in 4 octets. Consequently 4 spare bits have to be placed within these 4 octets. Bit 8 in octet n is the most significant bit and bit 5 in octet n+3 is the least significant bit. + +## F.2 3G Cell Identity coding – RNC-Id + C-Id + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------|---|---|---|-------|---|---|---|-----------| +| RNC-Id. | | | | | | | | octet n | +| RNC-Id cont. | | | | C-Id | | | | Octet n+1 | +| C-Id cont. | | | | | | | | octet n+2 | +| C-Id cont. | | | | Spare | | | | octet n+3 | + +Figure F1.2.1: 3G Cell Identity information element + +3GPP TS 25.401 indicates that the 28 bit 3G Cell Identity consist of a RNC-Id. (12 bit) and a C-Id (16 bit). + Bit 8 in octet n is the most significant bit and bit 5 in octet n+1 is the least significant bit of the RNC-Id. + Bit 4 in octet n +1 is the most significant bit and bit 5 in octet n+3 is the least significant bit of the C-Id. + +## F.3 3G Cell Identity coding – Extended RNC-Id + C-Id + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|-------|---|---|---|-----------| +| Extended RNC-Id. | | | | | | | | octet n | +| Extended RNC-Id cont. | | | | | | | | Octet n+1 | +| C-Id | | | | | | | | octet n+2 | +| C-Id cont. | | | | Spare | | | | octet n+3 | + +Figure F1.2.1: 3G Cell Identity information element + +With introduction of the Extended RNC-Id the 28 bit 3G Cell Identity consist of a Extended RNC-Id. (16 bit) and a C-Id (12 bit). + +Bit 8 in octet n is the most significant bit and bit 1 in octet n+1 is the least significant bit of the Extended RNC-Id. + +Bit 8 in octet n +2 is the most significant bit and bit 5 in octet n+3 is the least significant bit of the C-Id. + +# --- Annex G (informative): Change History + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-01 | | - | - | - | - | Release 13 version based on version 12.0.0 | 13.0.0 | +| 2016-12 | RP-74 | RP-162068 | 0127 | - | C | Alignment according to withdrawal of I-WLAN feature | 13.1.0 | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/44_series/44901/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/marked/Rel-16/44_series/44901/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6dd02c2380899d51b7769bf32a33bca877d9a81 --- /dev/null +++ b/marked/Rel-16/44_series/44901/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ba3e793ae5e5069b5d433f4b5975eea221b1cf614df959918a77a4e73c62ac7 +size 10287 diff --git a/marked/Rel-16/44_series/44901/57f8e374b0e99c488f68c46b713ffc64_img.jpg b/marked/Rel-16/44_series/44901/57f8e374b0e99c488f68c46b713ffc64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..083d9c387b9d12ffdce1506d46053c577f68e874 --- /dev/null +++ b/marked/Rel-16/44_series/44901/57f8e374b0e99c488f68c46b713ffc64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71c8aecabfb43153120abf78986d32e89b1ae79db8c066e6cedabd55d642edc3 +size 13849 diff --git a/marked/Rel-16/44_series/44901/ef7a88e04d1939ee09bafd5c3072adf8_img.jpg b/marked/Rel-16/44_series/44901/ef7a88e04d1939ee09bafd5c3072adf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf3a31886d45eaddc7fcff9887d4f0a45e7d507c --- /dev/null +++ b/marked/Rel-16/44_series/44901/ef7a88e04d1939ee09bafd5c3072adf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97ba112b456743f8eb13182394867629abd149a1963eaf4faed0c73d6ffd8ff5 +size 29181 diff --git a/marked/Rel-16/44_series/44901/raw.md b/marked/Rel-16/44_series/44901/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a9abeb8b47cc0bdab46db21a0101f7618e4e620f --- /dev/null +++ b/marked/Rel-16/44_series/44901/raw.md @@ -0,0 +1,690 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 Introduction and Motivation ..... | 7 | +| 4.1 Task Description ..... | 7 | +| 4.2 GPRS Cell Reselection pre-Release 4..... | 7 | +| 4.3 NACC in GERAN Release 4, Short description..... | 7 | +| 4.3.1 System Information Reception..... | 8 | +| 4.3.2 Cell Change Notification (CCN) Mode Procedures..... | 8 | +| 4.4 Extension of NACC in Release 5..... | 8 | +| 4.4.1 General ..... | 8 | +| 4.4.2 Short Technical Description ..... | 10 | +| 5 Requirements ..... | 10 | +| 5.1 Architectural Requirements..... | 10 | +| 5.1.1 Case 16 - Intra-UTRAN case ..... | 11 | +| 5.1.2 Case 4, 8, 12: GERAN → UTRAN..... | 12 | +| 5.1.3 Case 13 - 15: UTRAN → GERAN ..... | 12 | +| 5.2 Node Requirements..... | 12 | +| 5.2.1 BSC..... | 12 | +| 5.2.2 RNC..... | 12 | +| 5.2.3 SGSN..... | 13 | +| 5.2.4 MSC..... | 13 | +| 5.3 Interface Requirements ..... | 13 | +| 5.3.1 Gb interface ..... | 13 | +| 5.3.2 A interface ..... | 13 | +| 5.3.3 Iu interface..... | 13 | +| 5.3.4 Iur-g (Iur) interface..... | 14 | +| 5.3.5 Gn interface ..... | 14 | +| 5.3.6 Uu interface ..... | 14 | +| 5.3.7 Um interface ..... | 14 | +| 6 Generic mechanism for exchange of RAN information ..... | 14 | +| 6.1 General ..... | 14 | +| 6.2 Generic RIM procedures for exchange of RAN information..... | 15 | +| 6.2.1 General ..... | 15 | +| 6.2.2 RAN Information Request procedure..... | 15 | +| 6.2.3 RAN Information Send procedure..... | 15 | +| 6.2.4 RIM support in CN/RAN nodes..... | 16 | +| 6.3 Messages for RAN information ..... | 16 | +| 6.3.1 Message format ..... | 16 | +| 6.3.2 Message Type..... | 17 | +| 6.3.3 Addressing and routeing..... | 17 | +| 6.3.4 Container Prefix and Container Units ..... | 18 | +| 6.3.4.1 General..... | 18 | +| 6.3.4.2 Container Prefix..... | 18 | +| 6.3.4.3 Container Unit..... | 18 | +| 7 Exchange of RAN information for external NACC..... | 18 | +| 7.1 Principles for use of the generic mechanism for exchange of RAN information for NACC application..... | 18 | +| 7.1.1 General ..... | 18 | +| 7.1.2 Container Unit Disposition for NACC..... | 19 | +| 7.1.3 Error Handling..... | 19 | +| 7.1.4 External NACC software support in RAN nodes..... | 19 | + +| | | | +|----------|------------------------------------------------------------------|----| +| 8 | Interface load..... | 19 | +| 9 | Phased approach for the implementation ..... | 20 | +| 10 | Open Issues ..... | 20 | +| 11 | Specification Impact and Associated Change Requests ..... | 20 | +| 11.1 | General ..... | 20 | +| 11.2 | 3GPP TS 23.060 GPRS; Stage 2 description ..... | 20 | +| 11.3 | 3GPP TS 44.018 Mobile radio interface layer 3 specification..... | 21 | +| 11.4 | 3GPP TS 44.060 GPRS RLC/MAC Protocol..... | 21 | +| 11.5 | 3GPP TS 48.018 BSS GPRS Protocol (BSSGP) ..... | 21 | +| 11.6 | 3GPP TS 29.060 GPRS Tunneling Protocol (GTP)..... | 21 | +| 11.7 | 3GPP TS 25.41x UTRAN Iu interface..... | 21 | +| Annex A: | Change History ..... | 22 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This Technical Report provides background information, motivations, concepts and requirements regarding an extended Network Assisted Cell Change (NACC) feature for external cell change support. Cell change between GERAN and UTRAN cells is outside the scope of this report, although consideration has been taken in order to allow an easier extensibility to that case. The extension is based on the Release 4 version of the NACC feature where the mobile station is only supported by the NACC when performing internal cell re-selection, i.e. within a BSC. The extension of the feature is for GERAN just affecting BSS and for the core network the SGSN and signalling links between these network nodes. To support cell changes between GERAN and UTRAN, also the Um and the Uu interfaces are affected. + +The evolved Release 4 NACC proposal as described in this TR provides the basis for the detailed Stage 2 and stage 3 specification work. The feature will be developed in a phased approach and a longer-term vision is presented in the report. + +The focus of the TR is to: + +- Define the requirements on different nodes +- Specify the requirements for the interfaces +- Propose a plan for the work item project +- Evaluation of what does and does not need to be standardised + +# --- 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 TD GP-010361, "Network Assisted Cell Change; Concept document" + +[2] 3GPP TS 48.018: "General Packet Radio Service (GPRS); BSS GPRS Protocol (BSSGP)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following definitions apply: + +**External cell change:** Change of cells where old and new cell do not belong to the same BSC. + +**External neighbouring cells:** Cells listed in the BA-lists within a BSC that belongs to other BSCs. + +**Extended neighbouring cell list:** List of System information received from the external neighbour cells to be used in the Network Assisted Cell Change procedure. + +**Service outage time:** The time between the last received uplink RLC block from the mobile station in the old cell and the mobile station's first uplink RLC block received in the new cell. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------------------| +| CCN | Cell Change Notification | +| EDGE | Enhanced Data rates for GSM Evolution | +| GERAN | GSM/EDGE Radio Access Network | +| GPRS | General Packet Radio Service | +| NACC | Network Assisted Cell Change | +| NC | Network Control mode (can be NC0, NC1 or NC2) | +| O&M | Operations and Maintenance | +| PACCH | Packet Associated Common Control Channel | +| PS | Packet Switched | +| QoS | Quality of Service | +| RN | Radio Network | +| RAN | Radio Access Network | +| RIM | RAN Information Management | +| UE | User Equipment | +| UTRAN | Universal Terrestrial Radio Access Network | + +# --- 4 Introduction and Motivation + +## 4.1 Task Description + +The purpose of this new work task is to shorten the service outage time at cell reselection in packet transfer mode when the originating and the target cells belong to different BSCs/RNCs. This will improve the delivered quality of service for most QoS classes. + +## 4.2 GPRS Cell Reselection pre-Release 4 + +A pre-Release 4 GPRS/EDGE mobile station shall in modes NC0 and NC1 perform cell reselection purely based on neighbour cell measurements and independent of whether a packet transfer is ongoing or not. The cell change is performed without notifying the network. The MS is then not allowed to make random access in order to restart the data transfer in the new cell until a consistent set of system information for that cell has been correctly received. This behaviour is also used in Release 4 for the cases when a GPRS mobile station moves between GSM cells belonging to different BSCs or from a GSM to a UMTS cell. + +If the MS is trying to collect the target cell system information before the cell change, the MS may lose downlink data, which then has to be retransmitted in the new cell. If on the other hand the system information is collected after entering the target cell, the MS must first synchronise to the system information broadcast cycle and then collect the required system information before starting to re-establish the data transfer. In both cases the MS will lose a certain amount of time and downlink data when collecting the system information. There is also a risk that one or more RLC SDUs have to be completely retransmitted in the new cell as the cell change can be performed anytime during an ongoing transfer. + +For these reasons the Network Assisted Cell Change feature was introduced in Release 4 for MSs performing cell changes between cells belonging to the same BSC. The feature reduced the service outage time for an MS in packet transfer mode from a couple of seconds down to 300-700 ms by giving the network a possibility to assist the MS before and during the cell change. The assistance is given both as sending of neighbouring cell system information and with introduction of new procedures. + +## 4.3 NACC in GERAN Release 4, Short description + +NACC, the Network Assisted Cell Change feature introduced in Release 4 is a tool to minimize the service outage time for all QoS classes when a GPRS MS in packet transfer mode moves between GSM cells belonging to the same BSC. An overview of the Release 4 behaviour is described in GP-010361. + +NOTE: In the Release 4, NACC is not implemented to support cell reselections between GERAN and UTRAN or between BSCs. In this technical report a possible introduction of these cases is outlined. + +The NACC procedures are introduced as a mandatory feature for an Release 4 MS to speed up the cell re-selection. There are two main set of procedures specified for NACC, independent from each other: + +- One set which supports the mobile station with neighbouring cell system information and + +- One set which prepares the MS and puts the MS into Cell Change Notification mode (CCN mode) during a short period of time before the cell change. + +### 4.3.1 System Information Reception + +In the first set of procedures the network may - independent of the NC and the CCN modes - send neighbouring cell system information to an MS. The information is sent on the PACCH and is required for initial access after a cell change. An MS in Packet Transfer mode, which receives this information, shall store the information for 30 seconds. The MS may then use this information in the new cell. In the new cell the MS may then initiate access and receive missing system information from BCCH or PBCCH on PACCH by using the Packet PSI/SI Status procedures. + +### 4.3.2 Cell Change Notification (CCN) Mode Procedures + +In the second set of procedures a Release 4 MS in packet transfer mode enters CCN mode when a cell reselection is determined and if the network has ordered the MS to use CCN within the cell and towards the target cell. This order can either be generally given by the network in system information or be individually addressed to a certain mobile. + +When in CCN mode the MS informs the network with a Cell Change Notification message that the MS wants to reselect cell. The message contains the identity of the target cell. After sending the message to the network the mobile station continues the ongoing packet transfer for either a maximum time of about 1 second or until the network responds with a Packet Cell Change Continue or Packet Cell Change Order message. The Packet Cell Change Order message may indicate another target cell than the one proposed by the mobile station. After the delay, the MS leaves CCN mode. The MS also leaves CCN mode if it returns to Packet Idle mode, if it enters NC2 mode or if the criteria for camping on the old cell are no longer fulfilled. + +In CCN mode the network also has an opportunity to send neighbouring cell system information required for immediate initial access in the new cell when the re-selection has been performed. In CCN mode, the network may also terminate the ongoing packet transfer before sending the Packet Cell Change Continue or the Packet Cell Change Order message to the MS. + +## 4.4 Extension of NACC in Release 5 + +### 4.4.1 General + +In Release 4 of the GERAN specifications, the NACC procedures cover only cell re-selection to other GERAN cells within the same BSC where the BSC has system information available for the target cell. + +This limits the value of NACC, as external BSC cell changes and also cell changes between GERAN and UTRAN cells in some network configurations are of frequent occurrence. Extensions of the NACC feature to handle also external cell changes will therefore be of a certain value. For cell changes between Gb and Iu mode within GERAN and between GERAN *A/Gb mode* and UTRAN *Iu-mode* it is not obvious that the service for the user is improved by NACC. These cases might require rather heavy signalling to re-establish the RRC, the radio access bearers and the MM connections before the user service can be restarted in the target cell. + +A rough estimation of the occurrence of inter BSC cell changes in an assumed scenario where the BSC area consists of a regular hexagonal area surrounded by other BSC areas (Figure 4.1.1.a) and subdivided into smaller, hexagonal clusters is shown in Table 4.1.1.a. The traffic between these areas is then assumed to be equal distributed. + +![Diagram of a hexagonal grid representing a BSC area. The central part is a 3x3 cluster of dark yellow hexagons, representing internal cells. This central cluster is surrounded by a ring of white hexagons, representing external cells belonging to other BSCs. To the right of the diagram is a legend: 'White = External cells belonging to other BSCs' and 'Dark = Internal cells within a BSC Area'.](ef7a88e04d1939ee09bafd5c3072adf8_img.jpg) + +White = External cells belonging to other BSCs +Dark = Internal cells within a BSC Area + +Diagram of a hexagonal grid representing a BSC area. The central part is a 3x3 cluster of dark yellow hexagons, representing internal cells. This central cluster is surrounded by a ring of white hexagons, representing external cells belonging to other BSCs. To the right of the diagram is a legend: 'White = External cells belonging to other BSCs' and 'Dark = Internal cells within a BSC Area'. + +Figure 4.1.1.a: Example of internal/external cells for a BSC + +**Table 4.1.1.a: Relation between External to Total number of cell changes** + +| BSC Area Size
(in # of cells) | No of possible
external cell changes | Relation External/Total no of cell
changes (in %) | +|------------------------------------------|-----------------------------------------|------------------------------------------------------| +| 1 | 6 | 100 | +| 7 | 18 | 43 | +| 19 | 30 | 26 | +| 37 | 42 | 19 | +| 61 | 54 | 15 | +| 91 | 66 | 12 | +| 127 | 78 | 10 | +| 169 | 90 | 9 | +| 271 | 114 | 7 | +| 397 | 138 | 6 | +| 547 | 162 | 5 | +| 721 | 186 | 4 | +| 1141 | 234 | 3 | + +The case with a network composed of a mixture of BTSs and BSCs from different vendors will also give much higher figures (approximately 30 - 50% of external cell changes) as the cell clusters for a certain BSC will look like islands among cell clusters from other vendors BSCs. This will also be the case having overlapping GERAN and UTRAN coverage. + +This is a simplified network where cell reselection is assumed to be possible only to the 6 closest neighbours. In normal case the neighbouring cell lists can contain cells not directly close to the serving cell. So the figures for external cell changes will probably be higher. + +There is also the case when UTRAN and GERAN overlay, which means that the two access technologies have different nodes in the access network. + +Based on the reasons described above this study considers an extension of NACC to cover also cell changes to a cell managed by another BSC/RNC where the origin BSC/RNC does not have system information available for the target cell. This requires new signalling between BSCs/RNCs. The signalling may then be performed via the A, Gb, Iu and/or Iur-g interfaces to inform each BSC/RNC of the neighbouring cell system information. + +NOTE: the exchange of information between BSCs/RNCs via A and Iu-cs interfaces is out of the scope of this document, although care has been taken in order to allow an easy extension for other features using inter BSC/RNC communication. + +The Table 4.1.1.b below indicates scenarios to be considered for cell reselection between different BSCs/RNCs and the possibility to add the NACC feature to each case is then further discussed in this document. GERAN Gb indicates a BSC connected to SGSN only via Gb; GERAN Iu indicates a BSC connected to SGSN only via Iu and GERAN Iu/Gb indicates a BSC connected to SGSN via both Iu and Gb. This paper does not consider cell reselection scenarios involving CDMA 2000 cells. + +**Table 4.1.1.b: Possible combinations of cell changes** + +| Case No | From | To | Traffic via | +|---------|-------------|-------------|---------------| +| 1 | GERAN Gb | GERAN Gb | SGSN | +| 2 | GERAN Gb | GERAN Iu/Gb | SGSN | +| 3 | GERAN Gb | GERAN Iu | SGSN | +| 4 | GERAN Gb | UTRAN | SGSN | +| 5 | GERAN Iu | GERAN Gb | SGSN | +| 6 | GERAN Iu | GERAN Iu/Gb | SGSN or Iur-g | +| 7 | GERAN Iu | GERAN Iu | SGSN or Iur-g | +| 8 | GERAN Iu | UTRAN | SGSN or Iur | +| 9 | GERAN Iu/Gb | GERAN Gb | SGSN | +| 10 | GERAN Iu/Gb | GERAN Iu/Gb | SGSN or Iur-g | +| 11 | GERAN Iu/Gb | GERAN Iu | SGSN or Iur-g | +| 12 | GERAN Iu/Gb | UTRAN | SGSN or Iur | +| 13 | UTRAN | GERAN Gb | SGSN | +| 14 | UTRAN | GERAN Iu/Gb | SGSN or Iur | +| 15 | UTRAN | GERAN Iu | SGSN or Iur | +| 16 | UTRAN | UTRAN | SGSN or Iur | + +### 4.4.2 Short Technical Description + +For fast reselection of cells, the MS needs to have knowledge of certain system information of the target cell before performing the cell change. If the cells then belong to different BSCs/RNCs, the required system information has to be transported between BSCs/RNCs when updated to be made available to the MSs when re-selecting cells. The required system information is proposed to be packed into a container within a new RAN-INFORMATION message that may be sent on the Iur-g interface or routed via the Core Network (by one or more SGSNs) from the origin to the target RAN node. The information in the container shall be transparent for the Core Network. + +When system information is received, the target BSC/RNC can be ordered to acknowledge the information. If the acknowledgement is requested but not received by the source BSC/RNC, it is an implementation option how to perform retransmission. When system information is received, the information can optionally be associated with a validity timer. After the validity timer expiration the associated system information shall not be used for immediate initial access in the new cell. + +A BSC/RNC may request another BSC/RNC to respond with one or multiple RAN-INFORMATION messages or to stop transmission of event driven messages. + +# --- 5 Requirements + +## 5.1 Architectural Requirements + +In order to fulfil all the traffic cases as listed in Table 4.1.1.b, the BSC, the RNC and the SGSN nodes are all affected. The interfaces which requires update are Um, Uu, Gb, Iu, Gn and Iur-g. The Table 5.1.a below lists the required changes for the different cases. + +**Table 5.1.a: Required changes for the different cell changes.** + +| Case No | From | To | Affected nodes | Affected Network Interface | Affected Radio Interface | +|---------|-------------|-------------|----------------|---------------------------------------|--------------------------| +| 1 | GERAN Gb | GERAN Gb | BSC, SGSN | Gb, Gn | - | +| 2 | GERAN Gb | GERAN Iu/Gb | BSC, SGSN | Gb, Gn and opt Iu | - | +| 3 | GERAN Gb | GERAN Iu | BSC, SGSN | Gb, Gn and Iu | - | +| 4 | GERAN Gb | UTRAN | BSC, RNC, SGSN | Gb, Gn and Iu | Um and Uu | +| 5 | GERAN Iu | GERAN Gb | BSC, SGSN | Gb, Gn and Iu | - | +| 6 | GERAN Iu | GERAN Iu/Gb | BSC, SGSN | Iu, Gn and opt (Gb and Iur-g) | - | +| 7 | GERAN Iu | GERAN Iu | BSC, SGSN | Iu, Gn and opt Iur-g | - | +| 8 | GERAN Iu | UTRAN | BSC, RNC, SGSN | Iu, Gn and opt Iur-g | Um and Uu | +| 9 | GERAN Iu/Gb | GERAN Gb | BSC, SGSN | Gb, Gn and opt Iu | - | +| 10 | GERAN Iu/Gb | GERAN Iu/Gb | BSC, SGSN | Gb, Gn or alternatively (Iu or Iur-g) | - | +| 11 | GERAN Iu/Gb | GERAN Iu | BSC, SGSN | Iu, Gn and opt (Gb or Iur-g) | - | +| 12 | GERAN Iu/Gb | UTRAN | BSC, RNC, SGSN | Iu, Gn and opt (Gb and Iur-g) | Um and Uu | +| 13 | UTRAN | GERAN Gb | BSC, RNC, SGSN | Iu, Gn and Gb | Uu | +| 14 | UTRAN | GERAN Iu/Gb | BSC, RNC, SGSN | Iu, Gn and opt (Gb and Iur-g) | Uu | +| 15 | UTRAN | GERAN Iu | BSC, RNC, SGSN | Iu, Gn and opt Iur-g | Uu | +| 16 | UTRAN | UTRAN | RNC, SGSN | Iu, Gn and opt Iur | Uu | + +NOTE: The introduction of NACC for the different cases where UTRAN is a part might be of various importance. If any of these seven cases shall be covered is a decision to be taken together with the RAN subgroups. + +### 5.1.1 Case 16 - Intra-UTRAN case + +In Case 16 fast cell re-selection is already available when the neighbouring cells are operating on same frequency which is assumed to be the normal case in UTRAN. A single-RX UE will then be able to read the broadcast information from the new cell while still listening to the PICH/FACH in the old cell. Since this means that the UE can read broadcast information before actually moving to the new cell, the service interruption for the cell re-selection in CELL-PCH or CELL-FACH state is already faster than the NACC supported intra-BCS Cell change specified for Release 4. Conclusion: No improvements are required for the intra frequency cell change within UTRAN. + +There will also be inter-frequency cell-reselection case. Then the UE will not have read the system information broadcast yet (comparable to pre-release 4 GERAN situation) and the service interruption time is not so predictable since the scheduling of system broadcast information is not standardized. 3GPP TS 34.108 does specify a system - broadcast schedule for testing purposes. The more important information is only transmitted every 2.5 seconds, which would mean that the service interruption could take to at most something like 2.6 seconds (including reading Master Information Block which is scheduled every 80ms). In an implementation, the system information broadcast schedule can be assumed to be something around 2 seconds. + +2 seconds service outage time in this case is probably not severe since: + +- 1) Most of the time the UE will perform the intra-frequency case; +- 2) When the UE is in CELL-PCH state, the probability of requesting service should be quite low. + +So the service interruption is mainly a problem for CELL-FACH state. Then the question is how often the UE is in CELL-FACH state when having PS services. If the UTRAN keeps the UE in Cell-DCH quite long (where handover is performed instead of cell reselections), the UE might not be in CELL-FACH state that often. + +Conclusion: The inter-frequency cell change is not a relevant issue in UTRAN. + +### 5.1.2 Case 4, 8, 12: GERAN → UTRAN + +Cases 4, 8 and 12 where the UTRAN is the target cell might be of limited value as the service interrupt for the user will be significant due to complex and time consuming procedures to read system information and to and re-establish the + +layer 2 and layer 3 in the target cell. + +Conclusion: It is questionable if it is important that the inter-RAT cell re-selection has the same or better performance than the intra-RAT inter frequency cell reselection. + +### 5.1.3 Case 13 - 15: UTRAN → GERAN + +The cases 13-15 will imply introduction of the same NACC procedures in UTRAN as specified for GERAN Release 4. + +## 5.2 Node Requirements + +### 5.2.1 BSC + +The BSC is involved in all cases of Table 5.1.a except case 16. The following functionality has to be added in the BSC: + +- An origin BSC shall immediately when changed or, in case of periodic refresh (implementation option), at certain time intervals put in a container and distribute over the Gb, Iu or Iur-g interfaces part of the system information for a certain cell to all BSCs and RNCs parenting neighbouring cells.. +- At start up, restart or deletion of a cell the system information shall also be sent to all external neighbouring BSCs/RNCs affected. +- There may be one or more RAN information messages for each target BSC/RNC. A container message may contain multiple container units each carrying updated system information for one source cell and addressed to one destination BSC/RNC. +- The origin BSC can choose any of the available interfaces and CN domain for the transport of the RAN information messages. It is up to the BSC to analyze if the used interface and the first receiving node allows the transport. If not, the RAN information message shall not be sent over that interface. When using the Gb interface the origin BSC will via the Feature bitmap mechanism in the BSSGP protocol be informed whether the RIM procedures are supported. +- A BSC/RNC shall be able to request information from any BSC/RNC with neighbouring cells. +- A target BSC/RNC shall be able order another BSC/RNC to stop event driven transmission of information to the target BSC/RNC. +- The originating RAN node is required to keep information regarding the addressing method to use for each external neighboring cell. +- When using a 2G address only one CI of any valid cell is required by the core network for routing purposes in order to find the route to a certain BSC/RNC. +- The External NACC procedure requires consistent software in several nodes to operate properly. There will be occasions when the complete set of network nodes is not all updated with the required software. As an implementation option an algorithm can be used to detect whether the destination BSC node support external NACC. Such an algorithm can e.g. draw conclusions when not receiving external NACC procedure response messages and after loss of several response messages in a row during a specified time period it could be concluded that the External NACC procedure is not supported in a remote node. + +### 5.2.2 RNC + +The RNC is involved in cases 4, 8 and 12-16 of Table 5.1.a. In addition to the requirements listed above for the BSC, the following requirements has to be added if all cases shall be covered: + +- If required for optimised cell reselection from GERAN to UTRAN or within UTRAN, procedures for optimised access have to be introduced. +- For support of optimised cell re-selection from UTRAN to GERAN (cases 13-15) and internally within UTRAN (case 16) for inter-frequency cell change, the RNC has to include the functionality of NACC specified for BSC in Release 4 which mainly affects the Uu interface. That includes support for the Cell Change Notification mode procedures and distribution of neighbouring cell system information to mobile stations in packet transfer mode. +- All changes affecting the RNC is outside the responsibility of TSG GERAN. + +### 5.2.3 SGSN + +The SGSN is involved in all cases where the Gb, Iu and the Gn interface is used. The following main requirements concern the SGSN node: + +- The RAN information messages shall be routed to target BSC/RNC either over Iu or Gb or for the inter SGSN case tunnelled over the Gn interface to another SGSN +- The SGSN shall be able to identify from the addresses in the RAN specific information messages whether it is connected directly to the RAN node for which the message is intended. From the Routeing Area Identity (MCC+MNC+LAC+RAC) of the destination cell address, the SGSN shall decide whether or not it is connected to the destination BSS. If the SGSN is not connected to the destination BSS, then it shall use the RAI to route the message to the correct SGSN via the Gn interface. The SGSN connected to the destination BSS decides which BSS to send it to based on the CI of the destination address. +- The SGSN shall perform relaying between BSSGP messages and GTP messages to support the end-to-end transport between BSCs. +- The SGSN shall not interpret the information contained in the payload of the RAN information messages. + +### 5.2.4 MSC + +NOTE: The use of the MSC is for further study. + +## 5.3 Interface Requirements + +### 5.3.1 Gb interface + +The Gb interface may be used for transmission of the RAN information messages between the BSC and the SGSN when it exists. The following main requirements concerns the Gb interface: + +- The RAN Information Management (RIM) procedure shall transport information between BSCs/RNCs via one or more SGSNs. The SGSNs shall perform a simple relay of the messages from the Gb interface to the Gn interface and vice versa. +- The RAN Information Management procedure may provide end-to-end acknowledgements between BSCs. +- The RAN Information Management procedure shall provide end-to-end error handling between BSCs. +- The origin BSC will at the Gb interface from the Feature bitmap mechanism in the BSSGP protocol check whether the RIM procedures are supported. + +### 5.3.2 A interface + +NOTE: The use of the A-interface is for further study. + +### 5.3.3 Iu interface + +The Iu interface can be used for transmission of the RAN information messages between the BSC/RNC and the SGSN when it exists. The requirements concerning the Iu interface are the same as for the Gb interface above. + +NOTE: The use of the Iu-interface is for further study. + +### 5.3.4 Iur-g (Iur) interface + +The Iur-g interface is an optional interface which, if available, may be used instead of routing the information via the CN. The requirements concerning the Iur-g interface are the same as for the Gb interface above. + +NOTE: The use of the Iur-g (Iur)-interface is for further study. + +### 5.3.5 Gn interface + +The Gn interface (GTP protocol) shall be used by the SGSN for transfer of RAN information messages between two SGSNs. The requirements concerning the Gn interface are the following: + +- The SGSNs shall perform a simple relay of the messages from the Gb interface to the Gn interface and vice versa. +- The required service from GTP for the transfer between SGSN nodes is the unconfirmed type (i.e. no request/response message pair should be required on GTP). Ran Information Management will include the option for confirmed service operating end-to-end between the BSCs. +- Requirement for error handling in SGSN are as follows. When the SGSN receives a GTP message related to some RIM functionality and this message contains a protocol error, it is an implementation choice to log the error in the SGSN node. It would be possible to include mapping in the Relay function in the SGSN of GTP cause codes to BSSGP cause codes, and vice versa. This mapping of cause codes will however complicate both standardization and implementation. Very limited improvements on the overall functionality will be achieved via cause code mapping. Therefore no mapping function of cause codes is required. +- The SGSN node needs to be able to cope with communication between inconsistent releases of GTP without system failure. The requirement on the GTP entity which receives an unsupported PDU is to discard the PDU. No notification is required back to the sending node. + +### 5.3.6 Uu interface + +If cases 4, 8 and 12-16 shall be supported the Uu interface has to be updated with the NACC feature as specified for Release 4 of the GERAN specifications. + +For the cases 4, 8 and 12 where the mobile station reselects from a GERAN to a UTRAN cell, changes has to be done to support fast access (distribution of UTRAN system information to the MS after the transfer has been re-established in the UTRAN cell). For the cases 13-15 where the mobile station reselects from a UTRAN to a GERAN cell, the CCN mode procedures as specified in Release 4 for GERAN has to be added. That includes distribution of GSM system information on UTRAN associated channels. + +All changes affecting the Uu interface are outside the responsibility of TSG GERAN. + +### 5.3.7 Um interface + +If cases 4, 8 and 12 shall be supported, the Um interface (GPRS RLC/MAC protocol) has to be updated to distribute also the UTRAN system information to the MS before the MS reselects from a GERAN to a UTRAN cell. These are the only cases which requires update of the NACC feature in the GPRS mobile stations. + +# --- 6 Generic mechanism for exchange of RAN information + +## 6.1 General + +These clauses describe generic RAN Information Management (RIM) procedures for the exchange of RAN information between RAN nodes. In order to make it transparent for the Core Network, the message(s) conveying the RAN information include a container that shall not be interpreted by the Core Network nodes. For future extensibility of this generic mechanism to features other than external NACC, the container includes independent Container Units which can be customised for different applications. + +## 6.2 Generic RIM procedures for exchange of RAN information + +### 6.2.1 General + +The following RIM procedures are defined in order to allow the exchange of information between RAN nodes: + +- **RAN Information Request procedure:** This procedure is initiated by a BSC/RNC when it requires information from another BSC/RNC or when it requires stop of event driven reports from another BSC/RNC. +- **RAN Information Send procedure:** This procedure is initiated by a BSC/RNC when it has information to be sent to another BSC/RNC. The procedure may be event triggered (e.g. change of System Information) or scheduled (e.g. by a request procedure). Event driven reports may be stopped by the RAN Information Request procedure. + +These procedures are defined in detail in the following clauses. The description of the procedures assumes a means of communication between the two RAN nodes involved. The messages may go directly if there is an Iur-g interface between the two RAN nodes. Alternatively, they shall be routed via the Core Network. + +NOTE: Which CN domain the BSC/RNC shall choose to send the information to the other BSC/RAN is implementation dependent. + +The RAN Information Send procedure shall be completed using the same CN domain and set of interfaces used by the RAN Information Request procedure that triggered it. + +Multiple procedures can exist in parallel. + +### 6.2.2 RAN Information Request procedure + +This procedure is initiated by a BSC/RNC when it requires to start or stop the RAN information flow from another BSC/RNC. + +The BSC/RNC starts the procedure by sending the RAN INFORMATION REQUEST message to the BSC/RNC from which information is required. In the message is indicated if single or multiple reports are requested, or if the transmission of multiple reports shall be stopped. If single or multiple reports are requested, the receiving BSC/RNC shall immediately initiate a RAN Information Send procedure containing the requested information. If the transmission of multiple reports shall be stopped, the application in the receiving BSC shall initiate a RAN Information Send Procedure to send one single RAN INFORMATION message and thereafter immediately stop sending of further reports. If the RAN INFORMATION message is not received, it is an implementation option if and how to perform periodic retransmission of the RAN INFORMATION REQUEST message to the target BSC/RNC. + +![Sequence diagram for RAN Information Request procedure](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +A sequence diagram illustrating the RAN Information Request procedure. It features three entities: BSC/RNC 1, CN (Core Network), and BSC/RNC 2. BSC/RNC 1 is on the left, CN is in the center (represented by a dashed box), and BSC/RNC 2 is on the right. A solid horizontal arrow labeled 'RAN Information Request' originates from BSC/RNC 1 and points to BSC/RNC 2, passing through the CN box. + +Sequence diagram for RAN Information Request procedure + +Figure 6.2.2.a: RAN Information Request procedure. + +### 6.2.3 RAN Information Send procedure + +The RAN Information Send procedure is initiated by a BSC/RNC when it has information to be sent to another BSC/RNC. This procedure may be event triggered (e.g. change of System Information) or scheduled (e.g. by a RAN Information Request procedure). The procedure is initiated by sending a RAN INFORMATION message to another BSC/RNC. The RAN INFORMATION message also contains an indication of whether or not acknowledgement is needed. If such indication is not present, the procedure concludes. + +If the RAN INFORMATION message contains a request for acknowledgement, the receiving BSC/RNC shall send a RAN INFORMATION ACK. If the acknowledgement is not received, it is an implementation option if and how to perform periodic retransmissions of the RAN INFORMATION message to the target BSC/RNC. + +![Sequence diagram for RAN Information Send procedure](57f8e374b0e99c488f68c46b713ffc64_img.jpg) + +A sequence diagram illustrating the RAN Information Send procedure. It features three entities: BSC/RNC 1, CN (Core Network), and BSC/RNC 2. BSC/RNC 1 is on the left, CN is in the center (represented by a dashed box), and BSC/RNC 2 is on the right. A solid horizontal arrow labeled 'RAN Information' originates from BSC/RNC 1 and points to BSC/RNC 2, passing through the CN box. A dashed horizontal arrow labeled 'RAN Information Ack' originates from BSC/RNC 2 and points back to BSC/RNC 1, also passing through the CN box. + +Sequence diagram for RAN Information Send procedure + +Figure 6.2.3.a: RAN Information Send procedure. + +### 6.2.4 RIM support in CN/RAN nodes. + +The end-to-end support of the RIM procedures require Core Network nodes, source and destination BSC's to provide support for RIM. The following functions may discover if nodes support or not the RIM procedures: + +- The BSSGP protocol will via the Feature bitmap indicate if RIM procedures are supported between 2 specific BSC/SGSN nodes. +- The reception of a RAN INFORMATION or a RAN INFORMATION REQUEST PDU indicates that the BSC identified by the source cell address is supporting the RIM procedures. +- As an implementation option an algorithm can be used to detect whether the destination BSC node parenting the addressed cell supports the RIM procedures. Such an algorithm can draw conclusions from not receiving RIM response messages. After loss of several response messages in a row during a specified time period it could be concluded that the RIM procedures are not supported by the BSC parenting the addressed cell. +- Operation and Maintenance procedures can be used to configure whether or not the BSC parenting the external neighbouring cells support the RIM procedures. + +NOTE: The functions in the first two bullets are based on standardised mechanism and functions in bullets 3 and 4 are examples of implementation options. + +## 6.3 Messages for RAN information + +### 6.3.1 Message format + +All the messages for the exchange of information between RAN nodes have the format which is shown in figure 4. The message type identifies the message and how the payload is coded. All messages contain a source address and a destination address that are used for the routing between the RAN nodes. The Container Units are optional and not included for all message types. + +| | | | +|------------------------|--------------------------|-------------------------| +| Message Header | Message Type | | +| | Destination Address | | +| | Source Address | | +| Message Payload | RIM Application Identity | Container Prefix | +| | PDU specific IEs | | +| | Container Unit 1 | Container Units | +| | Container Unit 2 | | +| | ⋮ | | +| | Container Unit N | | + +Figure 6.3.1.a: Generic format of a RIM message. + +### 6.3.2 Message Type + +The following messages are defined: + +- RAN INFORMATION REQUEST message, +- RAN INFORMATION message, +- RAN INFORMATION ACK message and +- RAN INFORMATION ERROR message + +### 6.3.3 Addressing and routing + +The RAN information shall be transferred to and from GERAN and UTRAN. This information may be routed directly within GERAN or between GERAN and UTRAN if the Iur-g interface is present. Alternatively, it may be routed via the Core Network using different interfaces: potentially A, Gb, Iu, Gn and E interfaces. + +For the direct routing case via the Iur-g interface, no addressing mechanism at Layer 3 is necessary. When the information is sent via the Core Network, addressing information is needed in order to route the information to the correct destination RAN node. In this case the routing is performed in three stages: + +1. **Routing to a source CN node:** the source RAN node sends the message to a parenting CN node (MSC or SGSN). No address evaluation is needed for this routing. +2. **Routing to a destination CN node:** the CN node parenting the source RAN node shall route the information towards the CN node parenting the destination RAN node. There are two cases: + +If the *Circuit Switched* domain of the Core Network is used, the LAI (i.e. MCC, MNC and LAC) shall be used to identify the source and destination MSC. + +If the *Packet Switched* domain of the Core Network is used, the RAI (i.e. MCC, MNC, LAC and RAC) shall be used to identify the source and destination SGSN. + +This step is not present when source and destination RAN nodes are parented by the same CN node. + +3. **Routing to a destination RAN node:** the address shall contain information to help the destination CN node route the information to its correct RAN node. This information is different depending on whether the destination RAN node supports *A/Gb mode* and/or *Iu mode*: + - In A/Gb mode, the Cell Identity (CI) is known by both domains of the core network and shall be used to address the target RAN node. In A/Gb mode, there is no specific RAN node identity available. + - In Iu mode the cell identity is not known by the core network. Instead, the address contains a BSC-Id/RNC-Id that shall be used for routing of RAN information from the CN node to a 3G BSC/RNC. + +NOTE: If the destination RAN node supports both *A/Gb mode* and *Iu mode*, it is an implementation issue which interface shall be used. + +Consequently RAN information messages have to be addressed differently by the originating RAN node depending on: + +- the CN domain used. +- whether the destination RAN node supports *A/Gb mode*, *Iu mode* or both. + +The addresses used shall contain the Information Fields listed in table 6.3.3.a. + +**Table 6.3.3.a: Generic format of a RAN node address.** + +| Information Field | Presence | Length | Comments | +|-------------------|-------------|----------|--------------------------------| +| MCC+MNC | Mandatory | 3 octets | =PLMN-code; see 3GPP TS 24.008 | +| LAC | Mandatory | 2 octets | | +| RAC | Optional | 1 octet | See note 1 | +| BSC-Id/RNC-Id | Conditional | 12 bits | See note 2 | + +NOTE 1: This Information Field is required if the message or the response to the message has to be sent via the Packet Switched domain of the Core Network. + +NOTE 2: This Information Field may be used to address a 3G RAN node (i.e. that supports *Iu mode*). + +NOTE 3: This Information Field may be used to address a 2G RAN node (i.e. that supports *A/Gb mode*). + +### 6.3.4 Container Prefix and Container Units + +#### 6.3.4.1 General + +Only the message type and destination address information elements of the RAN INFORMATION messages are to be interpreted by CN nodes. The rest of the information is routed by the CN without interpretation. The payload is collected in the form of containers. For an easier reuse of this transport mechanism for different features, the information is defined in a *Container Prefix* and in one or more *Container Unit IEs*. + +#### 6.3.4.2 Container Prefix + +The *Container Prefix* consists of: + +- RIM Application Identity (e.g. NACC), +- Message specific information (e.g. optional Sequence Number, Acknowledgement required in the RAN INFORMATION message, Multiple Report Indication in the RAN INFORMATION REQUEST message). + +**Table 6.3.4.2.a: Generic format of the Container prefix.** + +| Information Field | Presence | Length | Comments | +|------------------------------------------------------------------|-----------|---------|-----------------------------------| +| RIM Application Identity | Mandatory | 1 octet | 0=NACC; All other values reserved | +| Message specific Information
Optional sequence number
.... | Optional | | For sequence number see NOTE 1, | + +NOTE 1: End-to-end transport can be supervised by the ACK mechanism. Anyhow the need for having an acknowledged service shall be based on the probability of losing messages. The sequence number is valuable to avoid duplicates and to reorder messages in the destination node. The sequence number is also required for the ACK handling and reports the correct reception of the RAN INFORMATION message sent with the same sequence number. The sequence number is not included in the error message. + +#### 6.3.4.3 Container Unit + +One message may carry zero, one or more Container Units all related to the same application (e.g. NACC). Each Container Unit carries information related to one entity (e.g. cell). The coding of a Container Unit is specific to the application using it. + +# 7 Exchange of RAN information for external NACC + +## 7.1 Principles for use of the generic mechanism for exchange of RAN information for NACC application + +### 7.1.1 General + +The rules specified below apply when the Container Unit Type is NACC: + +- The RAN INFORMATION message is used to send system information for one or more cells (one container unit is used per source cell) from a source BSC to a destination BSC/RNC. +- The RAN INFORMATION REQUEST message is used to let a source BSC/RNC request or stop transmission of system information from a destination BSC. +- The RAN INFORMATION ACK message is used to send acknowledgement for a correctly received RAN INFORMATION message back from the destination BSC/RNC to the source BSC. +- The RAN INFORMATION ERROR message is used to indicate that a PDU could not be successfully decoded. + +### 7.1.2 Container Unit Disposition for NACC + +Each Container Unit includes a 'Container Unit Length'. The coding of the rest of the Container Unit depends on the Message Type and the *Container Unit Type IEs* as defined in the 3GPP TS 48.018. + +### 7.1.3 Error Handling + +The BSSGP entity in the destination BSC will send the following type of error message to the source BSC under the following circumstances: + +- The RAN INFORMATION ERROR message, including a relevant cause code, will be sent when the destination BSC is unable to comply with part of or all information elements in any of the RAN INFORMATION message types. + +### 7.1.4 External NACC software support in RAN nodes + +The end-to-end support of the external NACC procedure requires Core Network nodes to support the RIM procedures and source and destination BSC's to provide support for external NACC. The following functions may discover if nodes support or not the external NACC procedure: + +- The reception of a RAN INFORMATION or a RAN INFORMATION REQUEST PDU with RIM Application Identity equal to NACC indicates that the BSC identified by the source cell address is supporting the external NACC procedure. +- As an implementation option an algorithm can be used to detect whether the destination BSC node support or not external NACC. Such an algorithm can draw conclusions from not receiving external NACC procedure response messages. After loss of several response messages in a row during a specified time period it could be concluded that the External NACC procedure is not supported for all nodes. +- Operation and Maintenance procedures can be used to configure whether or not the BSCs parenting the external neighbouring cells supports external NACC. + +NOTE: The functions in the first bullet are based on standardised mechanisms and functions in bullets 2 and 3 are examples of implementation options. + +# 8 Interface load + +The signalling load on interfaces between the BSCs is depending on the frequency of the system information updates in each cell with external neighbours. + +If the same assumptions as in clause 4.4.1 are used and the following assumptions are added + +- there is 3 external cells which has to be informed if system information is changed in a cell, +- the system information for a cell is updated N times per hour and each update generates 3 container messages, +- each container message sent to an external cell consists of 250 octets ( based on an estimated need to send 11 system information messages (instances)), +- there is only one SGSN serving the 2 BSCs. + +the resulting load on the Iu/Gb interface between the BSC and SGSN will be as shown in table 4. As seen from the table the reduction of a 2Mbit Gb (Iu) capacity for the container transport will for the largest BSC be $N \cdot 5 \cdot 10^{-5}$ . Note that it is assumed here that there is one message sent to each external neighbouring cell and not only one to each external BSC. + +**Table 8.a: Iu/Gb load for external NACC.** + +| BSC Area Size
(in # of cells) | No of cells with
external
neighbours | No of octets transmitted over
Gb(Iu)/hour (one direction) | +|----------------------------------|--------------------------------------------|--------------------------------------------------------------| +| 1 | 1 | $N \cdot 750$ | +| 7 | 6 | $N \cdot 4500$ | +| 19 | 12 | $N \cdot 9000$ | +| 37 | 18 | $N \cdot 13500$ | +| 61 | 24 | $N \cdot 18000$ | +| 91 | 30 | $N \cdot 22500$ | +| 127 | 36 | $N \cdot 27000$ | +| 169 | 42 | $N \cdot 31500$ | +| 271 | 48 | $N \cdot 36000$ | +| 397 | 60 | $N \cdot 45000 = N \cdot 100 \text{ bits/sec}$ | + +# --- 9 Phased approach for the implementation + +The distribution of neighbouring cell system information between BSC/RNC nodes to support the mobile stations at inter BSC/RNC cell change can be developed in a phased approach: + +- Phase 1: distribution of neighbouring cell system information between BSCs over the Gb interface. +- Phase 2: distribution of neighbouring cell system information between BSCs over the Iu and the Iur-g interfaces. The phase 2 is required first when 'Iu-only' cells not supporting pre-REL5 mobile stations will be introduced. +- Phase 3: distribution of neighbouring cell system information for cell changes from UTRAN to GERAN. + +# --- 10 Open Issues + +NOTE: This section will list issues where agreement and/or solutions have not been reached. It may be removed before a final decision(s) is made. + +- Behaviour of the BSC/RNC after a re-start is proposed to be an implementation option. +- Is inter-RAN NACC needed? RAN2 and GERAN2 agree that there are no clear benefits for the GERAN→UTRAN direction; the UTRAN→GERAN direction is for further study. + +# --- 11 Specification Impact and Associated Change Requests + +## 11.1 General + +This section will discuss the impact of the external NACC Work Item on current GERAN/UTRAN specifications as identified at present. It may be the case that this WI impacts other specifications not identified as yet, or after study the specifications listed below are not impacted upon. There may be a sub-section for each specification impacted. + +## 11.2 3GPP TS 23.060 GPRS; Stage 2 description + +A new clause – 'External Network Assisted Cell Change' shall be added describing the procedures in chapter 7. + +## 11.3 3GPP TS 44.018 Mobile radio interface layer 3 specification + +It shall be updated if the cell reselection cases from GERAN to UTRAN in table 4.1.1.b shall be included in the work Item.. It might be affected if new system information essential for access in the new cell has to be added for GERAN Release 5. + +## 11.4 3GPP TS 44.060 GPRS RLC/MAC Protocol + +It shall be updated if the cell reselection cases from GERAN to UTRAN in table 2 shall be included in the work Item.. It might be affected if new system information essential for access in the new cell has to be added for GERAN Release 5. + +## 11.5 3GPP TS 48.018 BSS GPRS Protocol (BSSGP) + +It shall be updated for all traffic cases in table 4.1.1.b where the Gb interface is involved. + +## 11.6 3GPP TS 29.060 GPRS Tunneling Protocol (GTP) + +It shall be updated for all traffic cases in table 4.1.1.b where the Gn interface is involved. + +## 11.7 3GPP TS 25.41x UTRAN Iu interface + +It shall be updated for all traffic cases in table 4.1.1.b where the Iu interface is involved. + +# --- Annex A: Change History + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-01 | | - | - | - | - | Release 13 version created based on v12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | - | Release 14 version (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Release 15 version (frozen at TSG-80) | 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/48_series/48001/raw.md b/marked/Rel-16/48_series/48001/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..789b59b9e95781d44ba191d6a2132d2cb5640907 --- /dev/null +++ b/marked/Rel-16/48_series/48001/raw.md @@ -0,0 +1,221 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 Abbreviations..... 7 + +4 A-Interface capabilities ..... 7 + +5 A-Interface specification objectives..... 7 + +6 A-Interface characteristics ..... 7 + +7 Other specifications on the MSC-BSS interface..... 8 + +7.1 3GPP TS 48.002 Interface Principles..... 8 + +7.2 3GPP TS 48.004 Layer 1 - Specification ..... 8 + +7.3 3GPP TS 48.006 Signalling Transport Mechanism - Specification..... 8 + +7.4 3GPP TS 48.008 Layer 3 Specification ..... 8 + +7.5 3GPP TS 48.020 Rate adaption on the BSS-MSC interface ..... 9 + +Annex A (informative): Change History..... 10 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the 3GPP TS 48.0xx series of Technical Specifications and deals with the definition of the base station system (BSS) to mobile switching centre (MSC) (referred to as the A-interface) defined for the GSM system. + +It also introduces Technical Specifications in the 3GPP TS 48.020 series, dealing with the support of data services on this interface. + +The present document gives an overview of the content of the 3GPP TS 48.0xx and 3GPP TS 48.020 series of Technical Specifications explaining how the detailed content of the Technical Specifications is partitioned and how the Technical Specifications can be used to support a full BSS-MSC interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] Void. +- [3] Void. +- [4] Void. +- [5] Void. +- [6] Void. +- [7] Void. +- [8] Void. +- [9] Void. +- [10] Void. +- [11] Void. +- [12] Void. +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. +- [18] Void. +- [19] Void. + +- [20] Void. +- [21] Void. +- [22] Void. +- [23] Void. +- [24] Void. +- [25] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [26] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [27] 3GPP TS 48.002: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Interface principles". +- [28] 3GPP TS 48.004: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Layer 1 specification". +- [29] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [30] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [31] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-service Switching Centre (BSS - MSC) interface". +- [32] Void. +- [33] Void. +- [34] Void. +- [35] Void. +- [36] Void. +- [37] Void. +- [38] Void. +- [39] Void. +- [40] Void. +- [41] Void. +- [42] Void. +- [43] Void. +- [44] Void. +- [45] Void. +- [46] Void. +- [47] ITU-T Recommendation G.703: "Physical/electrical characteristics of hierarchical digital interfaces". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# --- 4 A-Interface capabilities + +The BSS-MSC interface shall be capable of supporting all the services offered to GSM users and subscribers. In addition it also allows for the allocation of suitable radio resources within the PLMN, and the operation and maintenance of those resources. + +# --- 5 A-Interface specification objectives + +The MSC to BSS interface specifications shall allow the following: + +- i) Connection of various manufacturers BSSs to the same MSC; +- ii) The use of several manufacturers MSCs to the same type of BSS; +- iii) The use of the same BSS in any PLMN; +- iv) The use of the same MSC in any PLMN; +- v) The separate evolution of MSC and BSS technology, and; +- vi) The separate evolution of O&M facilities; +- vii) Evolution towards lower speech coding rates; +- viii) Support of all services defined in the 3GPP TS 02.series. + +# --- 6 A-Interface characteristics + +The interface is defined to be at the boundary of the MSC. + +The MSC to BSS interface is specified by a set of characteristics, including: + +- i) Physical and electromagnetic parameters; +- ii) Channel structures; +- iii) Network operating procedures; +- iv) Operation and Maintenance information support. + +The definition of the MSC to BSS interface follows a layered approach similar to that in the ISDN. Layer 3 is for the most part based on 3GPP TS 44.018 with additional procedures added for the control of radio resources and the identification of transactions using the SCCP. Layer 2 is based on the Signalling System No.7 (SS7) Message Transfer Part (MTP), or in the case of IP-based signalling transport - M3UA and SCTP. In case of SS7 MTP, layer 1 is either digital (at 2 048 kbit/s, based on ITU-T Recommendation G.703 clause 6) or analogue with the data being passed by the use of modems (this latter case is a national option). + +# --- 7 Other specifications on the MSC-BSS interface + +The full structure of the Technical Specifications specifying the MSC to BSS link are as follows. + +## 7.1 3GPP TS 48.002 Interface Principles + +The present document deals with the functional split between the BSS and the MSC. This functional split is then supported by the other Technical Specifications in the 3GPP TS 48.0xx series. + +3GPP TS 48.002 also contains some information on the placement of transcoders/rate adapters, these being functionally part of the BSS though a degree of freedom is allowed in their geographical location. + +In the case of A interface user plane over IP, transcoders in the BSS may not be needed. + +Lastly 3GPP TS 48.002 explains the use of transparent and non transparent signalling information across the interface. The key point is that the majority of call related signalling from the MS is passed in a fairly transparent way through the BSS. + +## 7.2 3GPP TS 48.004 Layer 1 - Specification + +The present document defines the physical layer at the BSS-MSC interface point. The physical interface chosen is either a 2 Mbits/s (32 x 64kbits/s) interface according to the standard ITU-T recommendations or an IP transport based interface according to the standard IETF RFCs. + +The speech coding called up in the present document is either according to ITU-T G.711 or according to Codecs listed in 3GPP TS 26.103. The coding of the traffic bit streams for data calls is dealt with in 3GPP TS 44.021 and 3GPP TS 48.020. + +## 7.3 3GPP TS 48.006 Signalling Transport Mechanism - Specification + +In order to pass the signalling information between BSS and MSC some reliable transport mechanism has to be used. The basis of the transport mechanism is an internationally agreed protocol known as signalling system No.7. + +Several services are required from this protocol but two key requirements are that messages can be transferred between the BSS and MSC without corruption, and secondly that a transaction with a particular mobile can be identified. + +The correct transfer of messages without corruption is handled by the "Message Transfer Part", or in the case of IP-based signalling transport - M3UA and SCTP, of SS7 and this is documented in 3GPP TS 48.006 which is an exceptions document to the ITU-T, ANSI and IETF specifications. The subset so formed is designed so that it is compatible with a "full" MTP (M3UA/SCTP) such as might be provided at an MSC. + +For IP-based signalling transport, the involved nodes may take the role of a client or a server with respect to establishing the end-to-end communication. The particular role of the nodes is either determined by configuration or is depending on which peer is acting first in establishing the communication, by that acting as the client. + +The identification of the transaction involved implies some form of logical connection. This is achieved by using the Signalling Connection Control Part (SCCP) of SS7. Again a minimum subset is formed in order to ease implementation. + +## 7.4 3GPP TS 48.008 Layer 3 Specification + +In the present document the application parts are described. There are two currently identified in the BSS to MSC interface protocol, these are the: + +- BSSOMAP; +- BSSAP. + +The BSSAP is further subdivided into two subprotocols, the BSSMAP and the DTAP. + +The BSSMAP and DTAP are fully defined, the BSSOMAP is only supported in terms of a signalling transport ability. + +The DTAP text is split between 3GPP TS 48.006 and 3GPP TS 48.008 but the text in 3GPP TS 48.008 defines which layer 3 air interface messages are passed transparently through the BSS and which are analysed at the BSS. + +The BSSMAP (base station system management application part) is that part of the protocol responsible for all aspects of the radio resource handling at the BSS. The text is structured as a set of procedures which are defined separately and can be employed as felt appropriate by the operator/manufacturer to meet the requirements of the application in which it is being used. The procedures themselves can be driven in different modes depending upon the input parameters received from the MSC or sent from the OMC. + +The BSSOMAP (base station system operation and maintenance application part) supports all of the O and M communications for the BSS with either the MSC or the BSS. The actual detailed protocol at layer 3 is defined in the 3GPP TS 52.xxx-series. + +## 7.5 3GPP TS 48.020 Rate adaption on the BSS-MSC interface + +The present document describes the means by which the radio interface data rates are adapted to the 64 kbits/s needed at the MSC and vice versa, down to the bit level. + +# Annex A (informative): Change History + +| TSG # | Doc. | CR | Rev | Subject/Comment | New | +|--------------|------|----|-----|----------------------------------------|--------| +| January 2016 | - | - | - | Version 13.0.0 based on version 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48002/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/48_series/48002/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a9b36f2b523f15cbc2d81963472c41a9682da66 --- /dev/null +++ b/marked/Rel-16/48_series/48002/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62f7cc120f24a676fb882cb33815eafd810e01e5bd4b6497d82f0a851a5d5f42 +size 89461 diff --git a/marked/Rel-16/48_series/48002/raw.md b/marked/Rel-16/48_series/48002/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0f13d075219816853e7d8705bf0847715b64b0a0 --- /dev/null +++ b/marked/Rel-16/48_series/48002/raw.md @@ -0,0 +1,570 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|---------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 4 Functional division between Base Station System (BSS) and MSC ..... | 8 | +| 4.1 Terrestrial channel management ..... | 8 | +| 4.1.1 Terrestrial channel allocation ..... | 8 | +| 4.1.2 Blocking of terrestrial channels..... | 9 | +| 4.2 Radio channel management ..... | 9 | +| 4.2.1 Channel configuration management..... | 9 | +| 4.2.2 Radio TCH management..... | 9 | +| 4.2.2.1 Radio channel allocation..... | 9 | +| 4.2.2.2 TCH radio link supervision..... | 9 | +| 4.2.2.3 Frequency hopping management..... | 9 | +| 4.2.2.4 Idle channel observation..... | 9 | +| 4.2.2.5 TCH power control ..... | 10 | +| 4.2.2.6 TCH channel release..... | 10 | +| 4.2.3 BCCH CCCH management..... | 10 | +| 4.2.3.1 Scheduling of BCCH and CCCH messages ..... | 10 | +| 4.2.4 DCCH Management ..... | 10 | +| 4.2.4.1 DCCH link supervision..... | 10 | +| 4.2.4.2 DCCH channel release..... | 10 | +| 4.2.4.3 DCCH power control..... | 10 | +| 4.2.4.4 Radio Channel Allocation..... | 10 | +| 4.3 Resource indication..... | 10 | +| 4.4 Channel coding decoding..... | 10 | +| 4.5 Transcoding/rate adaptation..... | 11 | +| 4.6 Interworking function (data calls)..... | 11 | +| 4.7 Measurement information ..... | 11 | +| 4.7.1 Measurement information reported from the MS..... | 11 | +| 4.7.2 Uplink measurement information..... | 11 | +| 4.7.3 Traffic information ..... | 11 | +| 4.8 Handover ..... | 11 | +| 4.8.1 Internal handover within one cell..... | 11 | +| 4.8.2 Internal handover between cells ..... | 11 | +| 4.8.3 External handover..... | 12 | +| 4.8.3.1 Recognition that a handover is required for a radio reason ..... | 12 | +| 4.8.3.2 Recognition that a handover is required for a traffic reason..... | 12 | +| 4.8.3.3 Decision of Target Cell..... | 12 | +| 4.8.3.4 Execution ..... | 12 | +| 4.9 Mobility management ..... | 12 | +| 4.10 Call control..... | 12 | +| 4.11 Security features..... | 12 | +| 4.11.1 User data confidentiality..... | 12 | +| 4.11.2 User identity confidentiality ..... | 13 | +| 4.11.3 Signalling information confidentiality ..... | 13 | +| 4.11.4 Authentication of users..... | 13 | +| 4.12 Global Text Telephony..... | 13 | +| 4.13 NAS Node Selection Function..... | 13 | +| 5 Transcoder/rate adapter integration ..... | 13 | +| 5.1 TDM based A-Interface ..... | 13 | +| 5.2 IP based A-Interface..... | 13 | + +6 Multiplexing of common and dedicated control channels..... 14 + +7 Classes of signalling messages ..... 14 + +8 Support of services and features other than speech ..... 14 + +8.1 Data services ..... 14 + +8.2 Supplementary services..... 14 + +9 Interface structures..... 14 + +10 Operation and maintenance..... 15 + +**Annex A (informative): Remote Mobile Switching Unit (RMSU)..... 16** + +A.1 Introduction ..... 16 + +A.2 Functions provided by the RMSU..... 16 + +A.3 General requirements ..... 16 + +**Annex B: (void)..... 17** + +Annex C (informative): Change History..... 18 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document gives the principles on which the detailed interface specifications in the rest of the 3GPP TS 48.0xx series of Technical Specifications are based. + +The set of fixed equipment accessed from the MSC through one particular instance of the interface will be later referred to as a Base Station System (BSS). A BSS ensures the coverage of n cells, where n can be 1 or more. + +The function of a BSS may be further subdivided into a control function, performed by one Base Station Controller (BSC) and a transceiving function, performed by "n" Base Transceiver Station equipments (BTS), one for each cell. However, the study of such a split is outside the scope of the 48.0xx series of Technical Specifications, where the BSS will be considered as a whole. + +The BSS-MSC interface defined in the 3GPP TS 48 series of Technical Specifications is designed to support a wide range of possible architectures on both sides. Characteristics like location of the transcoders/rate adaptation to the MSS or inside the BSS (either physically integrated into the transceivers or very near to the MSC) or the use of traffic or signalling concentration at either side are left to the operators' choice. Annex A to the present document contains guidance information concerning the use of remote mobile switching units, which for the purposes of the present document are considered as part of the MSC. + +The BSS-MSC interface is commonly called "A-Interface". It is subdivided into the Control Plane (signalling) and the User Plane (traffic). Throughout this document the term "MSC" is used to reflect both planes of the Mobile Core Network, although in some architecture the Mobile Core Network is split into MSC-Server (MSC-S) and Media Gateway (MGW). + +Direct connection between two BSSs is not supported by this A-Interface. + +This A-Interface may be based on + +- TDM using 1 or more 2 048 kbit/s digital transmission system interfaces. Each 2 048 kbit/s interface provides 31\*64 kbit/s channels which can be used for traffic (User Plane) or signalling (Control Plane) as the operator requires, and/or +- IP supporting User Plane and/or Control Plane (SIGTRAN). The signalling is layered, terminology similar to that in the OSI reference model is used in this series, however the layers referred to are not identical to the equivalently named layer in the OSI model. + +This A-Interface User Plane is defined at the boundary of the MSC and + +- in case of TDM, it has a per channel bit rate of 64 kbit/s, but the net radio path traffic channel is at a rate of less than 16 kbit/s. A speech transcoder or data rate adapter function is thus needed for the rate conversion. The interface is designed such that the transcoding or rate adaptation function may be geographically situated at either the MSC site or the BSS site, however the transcoder is considered to be part of the BSS +- in case of IP, it has a flexible channel bit rate, adapted to the payload size. The speech transcoding function can be part of either the BSS or the Core Network or can be omitted (transcoding free operation), allowing e.g. for use of both, PCM encoded speech and compressed speech, over the A-Interface. The data rate adapter function is always located inside the BSS, using a 64kbit/s unrestricted digital interface (Clearmode) over IP. + +The A-Interface has been designed around the aims of 3GPP TS 48.001 allowing each component and the system as a whole to evolve. + +# 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 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.009: "Handover procedures". +- [3] 3GPP TS 23.910: "Circuit switched data bearer services". +- [4] 3GPP TS 43.020: "Security related network functions". +- [5] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [6] 3GPP TS 48.001: Base Station System - Mobile services Switching Centre (BSS - MSC) interface; General aspects". +- [7] Void. +- [8] 3GPP TS 48.006: "Signaling transport specification mechanism for the Base Station Subsystem – Mobile-services Switching Centre (BSS - MSC) interface". +- [9] 3GPP TS 48.008: "Mobile-services Switching Centre – Base Station System (MSC-BSS) interface; Layer 3 specification". +- [10] Void. +- [11] Void. +- [12] Void. +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. +- [18] 3GPP TS 52.001: "Common aspects of GSM Network Management (NM)". +- [19] 3GPP TS 23.236: " Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ". + +# --- 3 Definitions and abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905. + +# 4 Functional division between Base Station System (BSS) and MSC + +Table 4: Functional split + +| Item/Task | BSS | MSC,MGW,VLR,HLR | +|-----------------------------------------|-----|---------------------------------------| +| Terrestrial Channel Management | | | +| channel allocation | X | X | +| blocking indication | X | X | +| Radio channel management | | | +| Radio channel configuration | | | +| management | X | | +| frequency hopping management | X | | +| idle channel observation | X | | +| power control | X | | +| TCH management | | | +| channel allocation (choice) | X | | +| link supervision | X | | +| channel release | X | X (Invoked by MSC) | +| BCCH/CCCH management | | | +| scheduling of messages | X | | +| DCCH management | | | +| link supervision | X | | +| channel release | X | X (Invoked by MSC) | +| DCCH allocation | X | | +| Radio resource indication | | | +| report status of idle channels | X | | +| Channel coding decoding | | | +| on the basis of call type | X | MSC defines call type | +| Speech Transcoding | X | X | +| Data rate adaptation | X | | +| Interworking Function (data calls) | | X | +| Measurements | | | +| reported from MS | X | | +| uplink | X | | +| traffic | | X | +| Handover | | | +| internal (within one cell){if provided} | X | MSC informed | +| internal (between cells) {if provided} | X | MSC informed | +| external recognition radio reason | X | | +| external recognition traffic reason | X | X | +| decision | X | X | +| execution | | X | +| Mobility Management | | | +| authentication | | X | +| location updating | | X | +| paging | | X | +| DRX paging (scheduling) | X | | +| Call control | | X | +| User data encryption | X | Key and permitted algorithms from MSC | +| Signalling element encryption | X | Key and permitted algorithms from MSC | +| NNSF (NAS Node Selection Function) | X | | + +## 4.1 Terrestrial channel management + +### 4.1.1 Terrestrial channel allocation + +Terrestrial channel allocation will be handled in the following manner. + +In case of TDM links, the link between the MSC and the BSS will be considered by the BSS and the MSC as a route on "n" circuits. Within this route, certain of the circuits may not be able to support all types of traffic (e.g., data calls or half + +rate connections). This can be managed, according to the configuration, either by the MSC or by the BSS for a given route. The entity in charge of circuit allocation chooses the terrestrial circuit, whilst ensuring that the chosen circuit is able to support the type of connection needed. + +In case of IP links, the IP-link for the User Plane traffic is negotiated between BSS and MSC by exchange of IP Transport Layer addresses and necessary User Plane information (e.g. Codec Type, Codec Configuration, RTP Redundancy, A-Interface Type). + +If an IP based A-Interface User Plane is supported by the MSC and/or the BSS and a terrestrial circuit is needed, then always the MSC, never the BSS, shall provide the terrestrial circuit (CIC). + +### 4.1.2 Blocking of terrestrial channels + +The entity not allocating the circuits shall be able to remotely block the terrestrial channel and remove it from service. This is signalled across the BSS/MSC interface using the appropriate signalling exchange as defined in 3GPP TS 48.008. + +Local blocking of terrestrial channels on the side allocating the circuits may be supported and will result in the concerned channels not being chosen, no information need flow across the interface in these cases. + +Blocking for IP-links is not explicitly needed, because no fixed relation between both endpoints of an IP link exists. + +## 4.2 Radio channel management + +### 4.2.1 Channel configuration management + +The channel configuration management will be controlled between BSS and maintenance centre, the MSC holding no direct data concerning the allocation of radio timeslots etc. + +### 4.2.2 Radio TCH management + +#### 4.2.2.1 Radio channel allocation + +The BSS shall choose the radio channel to be used on the appropriate cell, based on information received from the MSC, which defines the radio channel type, speech codec type (if necessary), channel coding and all other parameters relevant to defining channel type. The chosen radio channel shall be connected to the terrestrial channel in order to support the call. This connection mechanism is not further defined in these Technical Specifications, except the negotiation of the A-Interface Type (TDM or IP), defined in 3GPP TS 48.008. + +#### 4.2.2.2 TCH radio link supervision + +Radio link supervision of dedicated radio resources shall be the responsibility of the BSS. If communication with the mobile is lost then the BSS can request that the call be cleared. + +#### 4.2.2.3 Frequency hopping management + +Frequency hopping management shall be performed by the BSS. That is the BSS shall store and transmit all hopping parameters for the cell(s) that it controls, the hopping shall be performed such that it is not visible on the BSS/MSC interface. + +#### 4.2.2.4 Idle channel observation + +The quality of idle radio channels shall be measured by the BSS and a condensed form of the information passed back to the MSC. + +#### 4.2.2.5 TCH power control + +All power control functions shall be performed between MS and BSS. No real time power control commands shall be sent across the BSS/MSC interface. + +#### 4.2.2.6 TCH channel release + +The release of a dedicated resource is primarily controlled by the MSC. However for radio propagation reasons the BSS can request of the MSC that a call be released. The necessary protocols are defined in 3GPP TS 48.008. + +### 4.2.3 BCCH CCCH management + +All BCCH data shall be either stored at or derived locally by the BSS. + +CCCH random accesses shall be controlled autonomously by the BSS, paging messages shall be received from the MSC via the BSS/MSC interface. + +#### 4.2.3.1 Scheduling of BCCH and CCCH messages + +The scheduling for all BCCH and CCCH messages shall be performed by the BSS. + +### 4.2.4 DCCH Management + +#### 4.2.4.1 DCCH link supervision + +Radio link supervision of dedicated radio resources shall be the responsibility of the BSS. If communication with the mobile is lost then the BSS can request that the call be cleared. + +#### 4.2.4.2 DCCH channel release + +The release of a dedicated resource is primarily controlled by the MSC. However for radio propagation reasons the BSS can request of the MSC that a call be released. The necessary protocols are defined in 3GPP TS 48.008. + +#### 4.2.4.3 DCCH power control + +All power control functions shall be performed between MS and BSS. No real time power control commands shall be sent across the BSS/MSC interface. + +#### 4.2.4.4 Radio Channel Allocation + +The BSS shall choose the DCCH to be used on the appropriate cell. This shall be performed initially after the random access to the CCCH has been made by the MS. The chosen DCCH may at a later stage in the call be connected to the terrestrial channel in order to support the service, this is controlled by the appropriate indications in an assignment message from the MSC. + +## 4.3 Resource indication + +The status of idle radio channels is reported to the MSC using the protocol described in 3GPP TS 48.008. + +## 4.4 Channel coding decoding + +The encoding decoding and interleaving shall be performed by the BSS. The type of channel coding and interleaving is derived from the information in the assignment message from the MSC. + +## 4.5 Transcoding/rate adaptation + +Data rate adaptation shall be performed by the BSS. Speech transcoding may be performed by the BSS or may be omitted by the BSS, depending on the A-Interface Type negotiated between MSC and BSS. The selection of the appropriate function shall be based on information received from the MSC. + +## 4.6 Interworking function (data calls) + +The interworking function required for data calls to other networks shall be performed on the MSC side of the MSC/BSS interface. + +## 4.7 Measurement information + +### 4.7.1 Measurement information reported from the MS + +Measurement information reported from MSs with dedicated radio resources shall be processed by the BSS. + +### 4.7.2 Uplink measurement information + +The BSS shall process uplink information. + +The results of the processing of the "Measurement information reported from the MS" and the "Uplink measurement information" may be transmitted to the MSC as described in 3GPP TS 48.008. + +### 4.7.3 Traffic information + +Traffic information concerning the traffic environment outside a BSS is not passed from MSC to BSS. + +## 4.8 Handover + +Handovers (both internal and external) can occur for one of several reasons e.g. radio propagation, traffic distribution, O and M activity, equipment failure. + +### 4.8.1 Internal handover within one cell + +Internal handover within one cell can be supported within a BSS. It is optional for a BSS to be able to perform autonomous internal handover. + +The MSC will be informed when an autonomous internal handover has been completed (see 3GPP TS 48.008). + +### 4.8.2 Internal handover between cells + +Intra-BSS Handover between cells on the same BSS can be supported within a BSS. Multi cell BSSs would normally be expected to support internal inter cell handover, however it is optional that they do so. + +Intra-BSS handover may be performed autonomously by the BSS as long as neither the A-Interface Type is changed (e.g. from TDM to IP) nor the Codec Type nor the Codec Configuration are changed on the A-Interface to incompatible ones. The MSC will be informed when an autonomous internal handover has been completed (see 3GPP TS 48.008). + +If the Intra-BSS handover needs a modification of the A-Interface Type (e.g. a change from TDM to IP) or a change of the Codec Type or Codec Configuration on the A-Interface, then the MSC shall be involved before the handover is executed. + +### 4.8.3 External handover + +This type of handover includes inter-BSS handover as discussed in 3GPP TS 48.008 and inter-MSC handover as discussed in 3GPP TS 23.009. In all external handover cases the MSC is involved. + +#### 4.8.3.1 Recognition that a handover is required for a radio reason + +The BSS shall be able to generate an indication that a handover is required to the MSC using the protocols defined in 3GPP TS 48.008. + +No additional guidance is given in the 3GPP TS 48.0xx series concerning the algorithm within the BSS that generates either an internal handover, or an indication to the MSC that an external handover is required. + +#### 4.8.3.2 Recognition that a handover is required for a traffic reason + +The BSS shall be able to generate an indication to the MSC that a handover is required for traffic reason (e.g. directed retry) using the protocols defined in 3GPP TS 48.008. + +Within a multi BSS area only the MSC has a perspective of the overall traffic loading. The MSC may therefore originate inter BSS traffic handovers due to traffic reasons. + +#### 4.8.3.3 Decision of Target Cell + +The choice of the target cell in an external traffic handover shall be made by the MSC, based on information received from the BSS. + +#### 4.8.3.4 Execution + +Having received an indication from a BSS that an external handover is required, the decision of when and whether an external handover should take place shall be made by the MSC. + +## 4.9 Mobility management + +All transactions concerning mobility management (as specified in 3GPP TS 44.018) shall take place transparently between the MS and MSC/VLR/HLR, using the protocols described in Technical Specifications 3GPP TS 48.008 and 3GPP TS 48.006. The only exception to this rule is that of paging which is scheduled by the BSS on the appropriate cell. + +## 4.10 Call control + +Call control will be the responsibility of the MSC/HLR/VLR. + +## 4.11 Security features + +Information on security aspects are found in 3GPP TS 43.020. The BSS/MSC interface supports all of the required interchange of encryption keys. + +### 4.11.1 User data confidentiality + +Encryption and decryption of user data (e.g. speech) takes place within the mobile station and within the BSS. In order to decrypt/encrypt user data the encryption device used for the call must be loaded with the relevant key and algorithm. The key and the permitted algorithms are supplied by the MSC. + +### 4.11.2 User identity confidentiality + +This feature is supported by using a TMSI rather than an IMSI, over the radio path. The translation between TMSI and IMSI is performed at the MSC and within the mobile. Both TMSI and IMSI are carried transparently by the BSS-MSC interface as far as possible. + +### 4.11.3 Signalling information confidentiality + +As for user data. + +### 4.11.4 Authentication of users + +Authentication is carried out at the mobile and at the MSC/VLR/HLR. The MSC to BSS interface is required to transport the necessary challenge and response messages. + +## 4.12 Global Text Telephony + +Interworking between cellular text telephone modem (CTM) and text telephony standards (e.g. V.18) used in external networks can be performed by the BSS. It can also be performed by separate entities in the core network. + +## 4.13 NAS Node Selection Function + +The optional NAS Node Selection Function (NNSF) enables the BSC to initially assign a MSC to serve a MS and subsequently setup a signalling connection to the assigned MSC. + +The method by which the BSC initially assigns a MSC is implementation dependent. + +The NAS Node Selection Function is needed when the feature Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes is used. + +The NNSF is described in detail in [19]. + +# 5 Transcoder/rate adapter integration + +## 5.1 TDM based A-Interface + +The speech transcoder and the data rate adaptor will be functionally integrated into the BSS. It is not considered to be a stand alone piece of equipment. The control of the transcoder or rate adaptor will therefore take place directly via the BSS, an explicit control interface between BSS and transcoder and rate adaptor will not be defined. + +Dependent on the relative costs of transmission plant for a particular administration, there is an economic benefit, for larger cells and certain network topologies, in having the transcoder or rate adaptor positioned geographically at the MSC site. However, for smaller cells there may actually be a cost penalty due to special multiplexing. + +When the transcoder or rate adaptor is geographically sited at the MSC site, it shall still be considered part of the BSS, and as such is on the BSS side of the BSS-MSC interface. + +## 5.2 IP based A-Interface + +The speech transcoder can be functionally integrated either into the BSS or the core network. It is not considered to be a stand alone piece of equipment. If the speech transcoder is within the BSS, then it is controlled by the BSS, regardless of its geographical location. If the speech transcoder is within the core network, then it is controlled by the MSC. In certain call cases speech transcoders are not necessary at all. + +The data rate adaptor is always part of the BSS and therefore always controlled by the BSS. + +# 6 Multiplexing of common and dedicated control channels + +Common and dedicated control channels will be used for the same call on the radio path. These control channels will be multiplexed onto one or more common signalling channel(s) between the BSS and MSC. This multiplexing function will reside at the BSS. + +It should be noted therefore that the data links across the air interface are terminated at the BSS. + +All scheduling of messages via the air interface is controlled by the base station, flow control is therefore required from BSS to MSC to prevent overload of the transmission buffers, this is further detailed in Technical Specifications 3GPP TS 48.008 and 3GPP TS 48.006. + +# 7 Classes of signalling messages + +The signals between BSS and MSC are classified under three headings: + +- i) DTAP messages ----- BSSAP messages +- ii) BSS management ----+ +- iii) BSS O&M + +Where DTAP BSSMAP and BSSAP are as defined in 3GPP TS 48.008. + +Layer 3 call control messages will as far as possible pass transparently through the BSS. The discrimination between BSSMAP and DTAP messages is detailed in Technical Specification 3GPP TS 48.006. + +# --- 8 Support of services and features other than speech + +## 8.1 Data services + +In order to ensure that the requirements of 3GPP TS 23.910 are met, the support of data services will entail the following 7 actions being taken: + +- i) the speech coder being deactivated in the mobile; +- ii) a rate adaptation function being activated in the mobile; +- iii) an appropriate channel coding being activated in the mobile radio subsystem; +- iv) an appropriate channel coder being activated in the BSS; +- v) a rate adaptation function being activated in the BSS; +- vi) any echo control in the MSC being by-passed or disabled; +- vii) an appropriate network interworking function being invoked. + +The MSC to BSS interface will support all necessary signalling for this to be achieved. + +## 8.2 Supplementary services + +All signalling concerned with supplementary services is passed transparently through the BSS via the DTAP. + +# --- 9 Interface structures + +The definition of the MSC to BSS interface follows a layered approach. This is shown in figure 10.1. + +In the case of a digital link being used between the BSS and MSC, the signalling will be carried in one of the 64 kbits/s timeslots. + +# --- 10 Operation and maintenance + +Operation and maintenance information is required to flow between the BSS and O & M functions. The BSS to MSC interface provides for this type of information see 3GPP TS 52.001. + +![Signalling protocol reference model diagram showing layers for BSS-SIDE, A-INTERFACE, and MSC-SIDE. The diagram illustrates the protocol stack for the A-interface, including layers like BSSAP, DTAP, BSS MAP, Distribution Function, BSS OMAP, SCCP, MTP, and PHYSICAL LAYER. It also shows connections to other processes, air interface equipment, and applications.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the signalling protocol reference model for the A-interface, divided into three main sections: BSS-SIDE, A-INTERFACE, and MSC-SIDE. + +- BSS-SIDE:** + - Top level: Connections to "other processes within the BSS" and "air interface transmission equipment". + - BSSAP block: Contains DTAP and BSS MAP, which connect to a "Distribution Function". + - BSS OMAP block: Positioned to the right of the BSSAP block. + - SCCP block: Below the BSSAP and BSS OMAP blocks. + - MTP block: Below the SCCP block. + - PHYSICAL LAYER: The bottom-most layer. +- A-INTERFACE:** The central vertical section, labeled "A-INTERFACE" at the top and "LAYER" at the bottom. +- MSC-SIDE:** + - Top level: Connection to "other applications eg. call control". + - BSSAP block: Contains DTAP and BSS MAP, which connect to a "Distribution Function". + - Operation and Maintenance information to PLMN O&M centre block: Positioned to the right of the BSSAP block. + - BSS OMAP block: Below the O&M information block. + - SCCP block: Below the BSSAP and BSS OMAP blocks. + - MTP block: Below the SCCP block. + - PHYSICAL LAYER: The bottom-most layer, shared with the BSS-SIDE. + +To the right of the MSC-SIDE section, there is a label: "To other users of SCCP and MTP". + +Signalling protocol reference model diagram showing layers for BSS-SIDE, A-INTERFACE, and MSC-SIDE. The diagram illustrates the protocol stack for the A-interface, including layers like BSSAP, DTAP, BSS MAP, Distribution Function, BSS OMAP, SCCP, MTP, and PHYSICAL LAYER. It also shows connections to other processes, air interface equipment, and applications. + +## Terminology: + +- DTAP - Direct Transfer Application Part +- BSSMAP - BSS Management Application Part +- BSS OMAP - BSS Operation and Maintenance Application Part +- SCCP - Signalling Connection and Control Part +- MTP - Message Transfer Part +- BSS - Base Station System +- MSC - Mobile services Switching Centre + +NOTE: X.25 can be used for transferring O and M information. + +Figure 10.1: Signalling protocol reference model + +# --- Annex A (informative): Remote Mobile Switching Unit (RMSU) + +## A.1 Introduction + +Between the MSC and some of the BSS sites served by this MSC , it may be advantageous to include a line concentrator, an RMSU. The main purpose of introducing this unit is to reduce the number of terrestrial circuits needed between BSS site and MSCs (signalling and traffic circuits). The benefits of introducing an RMSU will depend on: + +- relative costs of the transmission plant for the particular administrations; +- the costs involved in operating the RMSU; +- the complexity of the RMSU, i.e. if it allows interworking with the ISDN or the PSTN for mobile originated calls. + +In the GSM Technical Specifications the RMSU will be regarded as a remotely controlled part of the MSC, and therefore no detailed specification of the RMSU or the signalling functions needed between the RMSU and the MSC will be given. + +## A.2 Functions provided by the RMSU + +Below is listed some examples of functions which may be provided by the RMSU: + +- setting up and clearing of circuits to the BSS and the MSC (remotely controlled by the MSC); +- switching of the circuits between MSC and the various BSSs; +- blocking and unblocking of circuits; +- possibly interworking with the PSTN or ISDN for mobile originated calls, including information exchange with remote control from the MSC; +- Operation and maintenance functions of the RMSU. + +## A.3 General requirements + +In order to be able to establish a BSS configuration without using an RMSU, and then later on introducing this unit, the interface between the BSSs and the RMSU should have the same characteristics as the interface between a BSS and an MSC. + +The number of subscribers served by an RMSU will be large compared to the number of subscribers served by a single BSS. Therefore, if the RMSU or the signalling links between the RMSU and the MSC go down, this will have a serious impact on the mobile service in a large geographical area. + +The implementation of the RMSU and the signalling between the RMSU and the MSC therefore has to be made in such a way that the overall reliability requirements specified for the MSC are fulfilled. + +Some O and M facilities may be required in the RMSU, and the necessary signalling between the RMSU and the O and M functions has to be provided. + +# --- Annex B: (void) + +# Annex C (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|----------|----|-----|---------------------------------------------|--------| +| January 2016 | - | - | - | Release 13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48004/raw.md b/marked/Rel-16/48_series/48004/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..314cab27acdc86d5d799346c1a7bb191feff3f26 --- /dev/null +++ b/marked/Rel-16/48_series/48004/raw.md @@ -0,0 +1,104 @@ + + + + + + +# Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 Abbreviations..... 5 + +4 Layer 1 Specification ..... 6 + +Annex A (informative): Change History..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the structure of the physical layer (layer 1) of the BSS-MSC interface for supporting traffic channels. Use of the physical layer for supporting Signalling System No.7 signalling links is covered in Technical Specification 3GPP TS 48.006. + +The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium. + +For the present document only digital transmission will be considered, the use of analogue transmission is a national concern. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ITU-T Recommendation G.705: "Characteristics of plesiochronous digital hierarchy (PDH) equipment functional blocks". +- [3] ITU-T Recommendation G.709: "Interfaces for the Optical Transport Network (OTN)". +- [4] ITU-T Recommendation G.711: "Pulse Code Modulation (PCM) of voice frequencies". +- [5] ITU-T Recommendation G.732: "Characteristics of primary PCM multiplex equipment operating at 2 048 kbit/s". +- [6] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [7] ANSI T1.102-1993: "Digital Hierarchy - Electrical Interface". +- [8] ANSI T1.403.01-1999: "Title: Network and Customer Installation Interfaces - (ISDN) Primary Rate Layer 1 Electrical Interfaces Specification (Includes revision of ANSI T1.408-1990 and partial revision of ANSI T1.403-1995)". +- [9] ANSI T1.107-1995: "Digital Hierarchy - Formats Specifications". +- [10] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] apply. + +# 4 Layer 1 Specification + +All ITU-T recommendations referred to are Blue Book. + +Layer 1 shall utilise digital transmission: + +- at a rate of 2 048 kbit/s with a frame structure of 32 x 64kbit/s time slots, as specified in ITU-T Recommendation G.705 clause 3 for E1 interface; or +- at a rate of 1 544 kbit/s with a frame structure of 24 x 64 kbit/s time slots, as specified in T1.102 specification for T1 interface. + +Therefore the physical/electrical characteristics are defined in ITU-T Recommendation G.703 for E1 interface or ANSI T1.403 specification T1 interface. + +The functional characteristics are defined in ITU-T Recommendation G.732 clauses 2 and 3 for E1 interface or ANSI T1.107 specification for T1 interface. + +Fault conditions should be treated in accordance with ITU-T Recommendation G.732 clause 4 for E1 interface or ANSI T1.403 specification for T1 interface. + +Speech encoding shall be the A-law or Mu-law (for North America) as defined in ITU-T Recommendation G.711. + +The idle pattern must be transmitted on every timeslot that is not assigned to a channel, and to every timeslot of a channel that is not allocated to a call. The idle pattern shall be 01010100 in ITU-T based systems and 01111111 in ANSI based systems. + +Synchronisation at the BSS for the transmitted 2 048/1544 kbit/s bit stream shall be derived from the received 2 048/1 544 kbit/s bit stream. + +Data encoding is covered in Technical Specification 3GPP TS 48.020. + +NOTE: A predetermined number of the 56/64kbit/s time slots may be used for signalling, to one or more base station systems. 56kbit/s is applicable to T1 interface only. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New version | +|--------------|-----------------|-----------|------------|---------------------------------------------|--------------------| +| January 2016 | - | - | - | Release 13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|----------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | | | | | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48006/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-16/48_series/48006/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c122f46057f6047037e5b27ac6549191cddcde --- /dev/null +++ b/marked/Rel-16/48_series/48006/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cf3f7d47768df837a489e8010af50c9e13b22a4aa1b52f1b2eaedccd20f0ae2 +size 65856 diff --git a/marked/Rel-16/48_series/48006/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-16/48_series/48006/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05729ec0a5e8951ae4125d2dba8883f6cdb3dcdc --- /dev/null +++ b/marked/Rel-16/48_series/48006/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:659796e881c9f455896dd8dfff2c74e378a1880f0f4b74c06e80971c03c25a21 +size 35917 diff --git a/marked/Rel-16/48_series/48006/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-16/48_series/48006/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2969f9659f6f0904559582c94940d3256171e4d --- /dev/null +++ b/marked/Rel-16/48_series/48006/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa00ff32dc8869224f446119f8c30da1c5a6f849dfd7738c8ff5d34e7621b93e +size 16595 diff --git a/marked/Rel-16/48_series/48006/4aecd812144e7d8c5264d03046f16dfb_img.jpg b/marked/Rel-16/48_series/48006/4aecd812144e7d8c5264d03046f16dfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55e4f2f40558aa5c7a1dc8339accc6f754ffa3a8 --- /dev/null +++ b/marked/Rel-16/48_series/48006/4aecd812144e7d8c5264d03046f16dfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e3f765171646a37c8b19b308708c135c01df40fc16e4dd461203f375f1ff839 +size 31290 diff --git a/marked/Rel-16/48_series/48006/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/48_series/48006/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bef7e48b14bd7cd0af8101975ad74aadbbfddeb7 --- /dev/null +++ b/marked/Rel-16/48_series/48006/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:716447be04bd44cf30bb43fd355fe3bafc9760e8144b1bfb3f2916bba0a85bf6 +size 33847 diff --git a/marked/Rel-16/48_series/48006/raw.md b/marked/Rel-16/48_series/48006/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..addb2a06019729371e91b93f39efa9f6ac063d4d --- /dev/null +++ b/marked/Rel-16/48_series/48006/raw.md @@ -0,0 +1,1728 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 Field of application ..... | 9 | +| 5 Functional content..... | 9 | +| 6 Message transfer part (MTP) functions ..... | 10 | +| 6.1 General ..... | 10 | +| 6.2 Level 1..... | 10 | +| 6.2.1 E1 link (ITU-T Recommendation Q.702) ..... | 10 | +| 6.2.2 T1 link (ANSI Specification T1.111.2)..... | 11 | +| 6.3 Level 2..... | 11 | +| 6.3.1 E1 link (ITU-T Recommendation Q.703) ..... | 11 | +| 6.3.2 T1 link (ANSI Specification T1.111.3)..... | 12 | +| 6.4 Level 3..... | 12 | +| 6.4.1 E1 link (ITU-T Recommendation Q.704) ..... | 12 | +| 6.4.2 T1 link (ANSI Specification T1.111.4)..... | 16 | +| 6.5 Testing and Maintenance ..... | 19 | +| 6.5.1 E1 link (ITU-T Recommendation Q.707) ..... | 19 | +| 6.5.2 T1 link (ANSI Specification T1.111.7)..... | 19 | +| 6a Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA) functions ..... | 20 | +| 6a.1 Introduction ..... | 20 | +| 6a.2 Protocol Stack ..... | 20 | +| 6a.3 Data Link Layer ..... | 21 | +| 7 Interface functions..... | 21 | +| 8 SCCP functions ..... | 21 | +| 8.1 Overview ..... | 21 | +| 8.2 Primitives ..... | 22 | +| 8.2.1 E1 link (ITU-T Recommendation Q.711) ..... | 22 | +| 8.2.2 T1 link (ANSI Specification T1.112.1)..... | 22 | +| 8.3 SCCP messages..... | 23 | +| 8.3.1 E1 link (ITU-T Recommendation Q.712) ..... | 23 | +| 8.3.2 T1 link (ANSI Specification T1.112.2)..... | 24 | +| 8.4 SCCP formats and codes..... | 25 | +| 8.4.1 E1 link (ITU-T Recommendation Q.713) ..... | 25 | +| 8.4.2 T1 link (ANSI Specification T1.112.3)..... | 26 | +| 8.5 SCCP procedures..... | 26 | +| 8.5.1 E1 link (ITU-T Recommendation Q.714) ..... | 26 | +| 8.5.2 T1 link (ANSI Specification T1.112.4)..... | 28 | +| 9 Use of the SCCP ..... | 29 | +| 9.1 Connection establishment ..... | 29 | +| 9.1.1 Establishment procedure in case i)..... | 31 | +| 9.1.2 Establishment procedure in case ii)..... | 31 | +| 9.1.3 Establishment procedure in case iii)..... | 31 | +| 9.1.4 Establishment procedure in case iv)..... | 32 | +| 9.2 Connection release ..... | 32 | +| 9.3 Transfer of DTAP and BSSMAP data ..... | 32 | +| 9.3.1 Distribution function ..... | 32 | +| 9.3.1.1 ITU-T Recommendation..... | 32 | +| 9.3.1.2 ANSI Specification ..... | 33 | + +| | | | +|------------------------|------------------------------------------------------|----| +| 9.3.2 | Transfer of DTAP messages..... | 33 | +| 9.3.3 | Transfer of BSSMAP messages ..... | 34 | +| 9.4 | Connectionless services..... | 34 | +| 9.4.1 | Discrimination parameter (ITU-T Recommendation)..... | 34 | +| 9.4.2 | Discrimination parameter (ANSI Specification) ..... | 35 | +| 9.4.3 | User Data Field Structure ..... | 35 | +| 10 | Use of the SCCP for operations and maintenance ..... | 35 | +| 10.1 | Connectionless service..... | 35 | +| 10.2 | Connection oriented services ..... | 36 | +| 10.3 | BSS failure ..... | 36 | +| Annex A (informative): | Change History..... | 37 | + +# --- 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 split into four parts, clauses 4 to 6 dealing with the MTP, clause 6a dealing with M3UA/SCTP, clause 7 dealing with interface functions towards higher layers and clauses 8 to 10 dealing with the SCCP and its use. + +The MTP provides a mechanism giving reliable transfer of signalling messages. Clauses 4 to 7 of the present document deal with the subset of the MTP that can be used between an BSS and an MSC, which is compatible with a full MTP. + +The M3UA/SCTP provides a mechanism giving reliable transfer of signalling messages over an IP network. + +The SCCP is used to provide a referencing mechanism to identify a particular transaction relating to for instance a particular call. Clauses 8 to 10 identify the SCCP subset that should be used between a BSS and an MSC. The SCCP can also be used to enhance the message routing for (for instance) operations and maintenance information. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] Void. +- [3] Void. +- [4] Void. +- [5] Void. +- [6] Void. +- [7] Void. +- [8] Void. +- [9] Void. +- [10] Void. +- [11] Void. +- [12] Void. +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. +- [18] Void. +- [19] Void. + +- [20] Void. +- [21] Void. +- [22] Void. +- [23] Void. +- [24] Void. +- [25] Void. +- [26] Void. +- [27] Void. +- [28] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". +- [29] Void. +- [30] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [31] Void. +- [32] Void. +- [33] Void. +- [34] Void. +- [35] Void. +- [36] Void. +- [37] Void. +- [38] Void. +- [39] Void. +- [40] Void. +- [41] Void. +- [42] Void. +- [43] Void. +- [44] Void. +- [45] Void. +- [46] 3GPP TS 48.008: "Mobile Switching Centre – Base Station System (MSC-BSS) interface; Layer 3 specification". +- [47] Void. +- [48] Void. +- [49] Void. +- [50] Void. +- [51] Void. +- [52] Void. +- [53] Void. + +- [54] Void. +- [55] Void. +- [56] Void. +- [57] Void. +- [58] ITU-T Recommendation Q.702: "Signalling data link". +- [59] ITU-T Recommendation Q.703: "Signalling link". +- [60] ITU-T Recommendation Q.704: "Signalling network functions and messages". +- [61] ITU-T Recommendation Q.707: "Testing and maintenance". +- [62] ITU-T Recommendation Q.711: "Functional description of the signalling connection control part". +- [63] ITU-T Recommendation Q.712: "Definition and function of signalling connection control part messages". +- [64] ITU-T Recommendation Q.713: "Signalling connection control part formats and codes". +- [65] ITU-T Recommendation Q.714: "Signalling connection control part procedures". +- [66] 3GPP TS 23.003: "Numbering, addressing and identification". +- [67] ANSI T1.110-1999: "Signaling System No.7; General Information". +- [68] ANSI T1.111-2000: "Signalling System No. 7; Message Transfer Part". +- [69] ANSI T1.112-1996: "Signalling System No. 7; Signalling Connection Control Part Functional Description". +- [70] TIA/EIA/IS-104-A: "Personal Communications Service Descriptions for 1 800 MHz". +- [71] ITU-T Recommendation Q.701: "Functional description of the message transfer part (MTP) of Signalling System No. 7". +- [72] IETF RFC 2960(10/2000): "Stream Control Transmission Protocol". +- [73] IETF RFC 3332(09/2002): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)". +- [74] IETF STD 51, RFC 1661(07/1994): "The Point-To-Point Protocol (PPP)". +- [75] IETF STD 51, RFC 1662(07/1994): "PPP in HDLC-like Framing". +- [76] IETF RFC 2507(02/1999): "IP header compression". +- [77] IETF RFC 1990(07/1994): "The PPP Multilink Protocol (MP)". +- [78] IETF RFC 2686(09/1999): "The Multi-Class Extension to Multi-Link PPP". +- [79] IETF RFC 2509(02/1999): "IP Header Compression over PPP". +- [80] IETF RFC 2474 (12/1998): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [81] RFC 3309: "SCTP Checksum Change". +- [82] IETF RFC 791 (09/1981): "Internet Protocol". +- [83] IETF RFC 2460: "Internet Protocol, Version 6 (Ipv6) Specification". +- [84] 3GPP TS 29.202: "SS7 Signalling Transport in Core Network; Stage 3" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**E1:** link employs 32 Pulse Code Modulation signals (timeslots) at 64 kbits/s. The 32 timeslots consist of 30 voice (or signalling) channels and 2 common signalling channels. The output bit rate is 2 048 Mbits/s. + +**T1:** link employs 24 Pulse Code Modulation signals (timeslots) at 64 kbits/s. (T1 interface can alternatively use signalling at 56 kbits/s). The output bit rate is 1 544 Mbits/s. (A frame consists of 193 bits, $(8 \times 24) + 1$ , as one bit is used for synchronization. The frame repeats 8,000 times per second.). + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# --- 4 Field of application + +- a) The present document is applicable to the signalling between radio subsystems (BSS) and mobile switching centres (MSCs) in GSM PLMNs. It provides a minimum set of MTP, or in the case of IP-based signalling transport - M3UA and SCTP, requirements that may be implemented at a BSS or MSC, whilst maintaining compatibility with the implementation of a full specification of the MTP (M3UA/SCTP). +- b) For MTP signalling transport usage, the Technical Specification defines the interface at the 64 kbits/s boundary to the BSS or MSC and applies primarily for digital access arrangements, the use of analogue arrangements is an option for PLMN operator. + +Also, the Technical Specification defines the interface at the 56 kbits/s boundary to the BSS or MSC for T1 links. + +- c) The security of signalling links is a PLMN operator concern, however it is recommended that in the case where more than one multiplex system is required and security reasons dictate the use of a multiple link linkset, then each signalling link should be assigned in a different multiplex system. It is however noted that this is of little benefit if diversity of routing of the multiplexes is not used. +- d) Both associated and quasi-associated modes of signalling between the BSS and the MSC are allowed. In case of quasi-associated mode the STP functionality is provided outside the BSS. Future evolution or economic reasons applicable to the interface may however make the use of STP working at the BSS attractive, in which case some of the simplifications in this paper will not apply. +- e) A variety of information types may be supported by the signalling system, e.g. relating to circuit switched call control and packet communication. These are fully defined in the service series of Technical Specifications (the 3GPP TS 02.xx series and in [70] for PCS 1900). +- f) For E1 link usage, the ITU-T recommendations concerning the MTP shall be taken as being requirements unless covered by a statement in the present document. +- g) For T1 link usage, the ANSI recommendations concerning the MTP [68] shall be taken as being requirements unless covered by a statement in the present document. +- h) For IP-based signaling transport usage, 3GPP TS 29.202 [84] shall be taken as being requirements unless covered by a statement in the present document. + +# --- 5 Functional content + +The functional requirements are as follows: + +- a) the network call control functions are as specified in 3GPP TS 48.008 and 3GPP TS 44.018; + +- b) the minimum set of Message Transfer Part functions are specified in Blue Book ITU-T Recommendations Q.702, Q.703, Q.704 and Q.707, with the qualifications specified in the present document; + +The functions are specified in ANSI T1.111 [68] for T1 links. + +- c) the additional interface functions required for the proper operation of the layer 3 control functions in combination with the Message Transfer Part, or in the case of IP-based signalling transport - M3UA and SCTP, functions, are specified in clause 7 of the present document. +- d) the minimum set of Message Transfer Part 3 – User Adaptation (M3UA) functions are specified in 3GPP TS 29.202 [84]. + +# --- 6 Message transfer part (MTP) functions + +## 6.1 General + +For E1 links, the MTP functions as specified in ITU-T Recommendations Q.702, Q.703, Q.704 and Q.707 are applicable. For T1 links, the MTP functions as specified in ANSI specifications T1.110 clause 5, and T1.112 clause 5 are applicable. However, the following exceptions and modifications to those Recommendations may be applied for the MSC to BSS signalling, see clauses 6.2 to 6.4. + +Some form of policing could be included at the MSC in order to ensure that no signalling messages received from the BSS can be routed further than the MSC if an administration requires. This is necessary to prevent fraudulent use of the signalling network for implementations of the GSM system. The manner in which this is achieved will be dependent on local agreements or regulations and system implementations. + +Where load sharing is used, all messages to do with a given SCCP connection should be passed down a given link. + +## 6.2 Level 1 + +### 6.2.1 E1 link (ITU-T Recommendation Q.702) + +#### **Q.702 figure 2** + +These figures should be treated as for information only. For the standard application of GSM, interface point C is appropriate. + +#### **Q.702 clause 4.4** + +The use of analogue circuits to support the signalling link is a national matter. + +#### **Q.702 clause 5** + +A signalling rate of 64 kbits/s is assumed. Lower rates (e.g. using analogue bearers) are a national concern. + +#### **Q.702 clause 6** + +Error characteristics and availability are a national concern. Care should be taken as excessive errors could lead to inefficient use of the signalling links. + +#### **Q.702 clause 8** + +The standard arrangement will be to derive the signalling link from a 2 048 kbits/s digital path. + +#### **Q.702 clause 9** + +Only digital signalling data links are relevant. + +The use of analogue bearers to support this interface is considered a national concern. However it should be noted that there will be potential problems with the following areas: + +- the signalling load may exceed that which can be carried by a single low rate analogue link, this may lead to an excessive number of signalling links and more complex changeover/changeback procedures; + +- the performance of the analogue lines used to carry the signalling link will have a major impact on the throughput of signalling information that can be achieved; +- message delay may degrade the quality of service. + +### 6.2.2 T1 link (ANSI Specification T1.111.2) + +#### T1.111.2 figure 2 + +These figures should be treated as for information only. For the standard application, interface point C is appropriate. + +#### T1.111.2 clause 4.4 - Analogue Signalling Link + +The use of analogue circuits to support the signalling link is a service provider option. + +#### T1.111.2 clause 5 - General + +A signalling rate of 56/64 kbits/s is assumed. Lower bit rates (e.g. using analogue bearers) are a service provider option. + +#### T1.111.2 clause 6 - Error Characteristics and Availability + +Error characteristics and availability are an operator concern. Care should be taken as excessive errors could lead to inefficient use of the signalling link. + +#### T1.111.2 clause 8 - Digital Signalling Data Link + +The standard arrangement will be to derive a signalling link from a 1 544 kbits/s digital path. + +#### T1.111.2 clause 9 - Analogue Signalling Data Link + +Only digital signalling data links are required. + +The use of Analogue bearers to support this interface is considered a service provider option. However, it should be noted that there will be potential problems with the following areas: + +- the signalling load may exceed that which can be carried by a single low rate Analogue link, which may lead to an excessive number of signalling links and more complex changeover/change back procedures; +- the performance of the Analogue lines used to carry the signalling link will have a major impact on the throughput of signalling information that can be achieved; +- message delay may degrade the quality of service. + +## 6.3 Level 2 + +### 6.3.1 E1 link (ITU-T Recommendation Q.703) + +#### Q.703 clause 4.4 + +Only the basic error correction protocol is required. + +#### Q.703 clause 4.7 + +Only the emergency proving period and status indications should be used by the BSS. + +#### Q.703 clause 9 + +Not applicable, only basic error correction is required. + +#### Q.703 clause 40 + +In the initial alignment procedure specified in ITU-T Recommendation Q.703, only the emergency proving is applicable for the BSS. Thus, in states 02 and 03 of the initial alignment procedure status indication "N" is not sent from the BSS. The BSS should be capable of recognising status indication "N" if received in order for the alignment procedure to complete. + +#### Q.703 clause 8 + +The processor outage status indicator shall be recognised at the BSS and the procedures defined in ITU-T Recommendation Q.703 clause 8 supported. + +The BSS shall support the generation of the processor outage indication towards the MSC if this is appropriate. + +#### **Q.703 clause 40** + +Only the emergency alignment procedures are required. + +### **6.3.2 T1 link (ANSI Specification T1.111.3)** + +#### **T1.111.3 clause 4.4 - Signal Unit Error Correction** + +Only the basic error correction protocol is required. + +#### **T1.111.3 clause 4.7** + +Only the emergency proving period and status indications should be used by the BSS. + +#### **T1.111.3 clause 9 - Preventive Cyclic Retransmission Error Correction Method** + +Only basic error correction is required for the A-Interface. + +#### **T1.111.3 clause 40 - Signalling Link Initial Alignment Procedure** + +In the initial alignment procedure, only the emergency proving is required for the BSS. Thus, in states 02 and 03 of the initial alignment procedure status indication "N" is not sent from the BSS. The BSS should be capable of recognizing status indication "N" if received in order for the alignment procedure to complete. + +##### **T1.113 clause 8** + +The processor outage status indicator shall be recognised at the BSS and the procedures defined in ANSI standards T1.113 clause 8 supported. + +The BSS shall support the generation of the processor outage indication towards the MSC if this is appropriate. + +##### **T1.113 clause 40** + +Only the emergency alignment procedures are required. + +## **6.4 Level 3** + +### **6.4.1 E1 link (ITU-T Recommendation Q.704)** + +#### **Q.704 clause 4.1.2.** + +It should be noted that for point to point working, there will be no signalling transfer point network management features which need to be considered. + +#### **Q.704 clause 4.3** + +Signalling link management is required. Load sharing is required, and changeover/back between links within a single linkset are required. + +#### **Q.704 clause 5** + +Since STP working at the BSS is not required the discrimination and routing functions of the MTP used for GSM application can be significantly simplified. + +#### **Q.704 clause 5.2 - Routing label** + +Load sharing will be performed on BSS s with more than one signalling link by means of the signalling link selection field (SLS). + +#### **Q.704 clause 5.3 - Message routing function** + +It should be noted that for point to point working, load sharing between linksets is not required since there will only be one linkset between BSS and MSC. + +#### **Q.704 clause 5.3.5** + +Either of the two methods of congestion control is acceptable. The most appropriate method is dependent on national ITU-T No. 7 implementations. + +#### **Q.704 clause 5.4 - Message discrimination** + +At the BSS only messages with a correctly checking DPC will be accepted. Others will be discarded. It is recommended that discarding a message because of an incorrectly set point code causes an incident report to be generated. + +At an MSC (which has the capability of acting as an STP) the messages not destined to it may be directed to the routing function. + +The signalling point code for an BSS may be included in the national signalling point code scheme or in a separate signalling network. In the case where the signalling point code is in the national network the MSC need have only one point code, in the case where the signalling point code is in a separate "PLMN" signalling network, the MSC will be required to have two signalling point codes, one for each network. + +##### **Q.704 clause 6.1.3 c)** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **Q.704 clause 6.3.1.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **Q.704 clause 6.3.2.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **Q.704 clause 6.3.3.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **Q.704 clause 6.3.4.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **Q.704 clause 6.3.5.2** + +It should be noted that for point to point working, there is no requirement for signalling route management or signalling link blocking initiated by a management system. + +##### **Q.704 clause 6.3.6.2** + +It should be noted that for point to point working, there is no requirement for signalling route management or signalling link blocking initiated by a management system. + +##### **Q.704 clause 6.4.1** + +It should be noted that for point to point working, the signalling route will become unavailable when the associated link set fails. + +##### **Q.704 clause 6.4.2** + +It should be noted that for point to point working, the signalling route will become available when the associated link set is restored. + +#### **Q.704 clause 6.4.3** + +Not applicable. + +#### **Q.704 clause 6.5.1** + +It should be noted that for point to point working the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ITU-T Recommendation Q.704 clause 40.2.1. + +#### **Q.704 clause 6.5.2** + +It should be noted that for point to point interworking the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ITU-T Recommendation Q.704 clause 40.2.2. + +#### **Q.704 clause 6.5.3** + +Not applicable. + +#### **Q.704 clause 6.8.2** + +There are two acceptable methods of congestion control defined in ITU-T Recommendation Q.704, in clauses 3.6.2.1 a) and b). The most appropriate method is dependent on national ITU-T No. 7 implementations. Each administration should specify its congestion threshold setting algorithm and nodal congestion abatement procedures at system procurement. + +#### **Q.704 clause 6.8.5.2** + +It should be noted that for point to point working, the signalling-route-set-congestion-test procedure is not required. + +##### **Q.704 clause 7.1.2** + +It should be noted that for point to point working, signalling routes are not applicable. + +#### **Q.704 clause 7.2** + +The normal routing situation will be that there are 1 or more signalling links available between a BSS and MSC, these will constitute a link set. They will be run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links. + +Furthermore, in case of more than one link set (not for point to point working), load sharing between link sets is also allowed. + +#### **Q.704 clause 7.3.3** + +It should be noted that for point to point working, there will be no alternative linkset. + +#### **Q.704 clause 7.4.3** + +Not applicable in case of point to point working. + +#### **Q.704 clause 7.5** + +Not applicable in case of point to point working. + +#### **Q.704 clause 7.6** + +Not applicable in case of point to point working. + +#### **Q.704 clause 7.7** + +Not applicable. + +#### **Q.704 clause 8 - Changeover** + +It should be noted that for point to point working, changeover between link sets is not applicable. + +#### **Q.704 clause 9 - Changeback** + +It should be noted that for point to point working, changeover between link sets is not applicable. + +#### **Q.704 clause 40** + +It should be noted that for point to point working, forced re-routing is not applicable since there is only one signalling route existing between BSS and MSC. + +##### **Q.704 clause 8** + +Not applicable in case of point to point working since there is only one signalling route existing between BSS and MSC. + +##### **Q.704 clause 41** + +It should be noted that for point to point working the signalling route set will consist of one associated signalling route only. + +##### **Q.704 clause 42 - Signalling link management** + +Only basic link management procedures are applicable. + +##### **Q.704 clause 42.3.4 - Link set activation** + +Link set normal activation defined in clause 41.2.4.1 is not applicable. Link set emergency restart at the BSS is used in all cases. + +##### **Q.704 clause 43.2 - Transfer prohibited** + +It should be noted that for point to point working, the transfer prohibited function is not applicable. + +##### **Q.704 clause 43.3 - Transfer allowed** + +It should be noted that for point to point working, the transfer allowed function is not applicable. + +##### **Q.704 clause 43.4 - Transfer restricted** + +It should be noted that for point to point working, the transfer restricted function is not applicable. + +##### **Q.704 clause 43.5 - Signalling-route-set-test** + +It should be noted that for point to point working, the signalling-route-set-test procedure is not applicable. + +##### **Q.704 clauses 13.6, 13.7 and 13.8 - Transfer controlled** + +It should be noted that for point to point working, the transfer controlled function is not applicable. **Q.704 clause 43.9 - Signalling route-set-congestion-test** + +It should be noted that for point to point working, the signalling route-set-congestion-test function is not applicable. + +##### **Q.704 clause 44.2.1** + +Since all messages are passed using the SCCP, the service indicator will be: + +| | | | | | +|------|---|---|---|---| +| bits | D | C | B | A | +| | 0 | 0 | 1 | 1 | + +##### **Q.704 clause 44.2.2** + +The sub service field will always be set to one of the following values: + +| | | | +|------|------------------|--| +| bits | | | +| D C | | | +| 1 0 | national network | | +| 1 1 | local network | | + +##### **Q.704 clause 44.3** + +This information for SCCP is defined in ITU-T Recommendation Q.713. + +##### **Q.704 clause 45** + +The formats and codes listed are only relevant to the messages that are required, i.e. those not excluded in the rest of this recommendation. + +### 6.4.2 T1 link (ANSI Specification T1.111.4) + +#### **T1.111.4 clause 4.1.2** + +Signalling Transfer Point network management procedures are not required in case of point to point working. + +#### **T1.111.4 clause 4.3** + +Signalling link management is required. Load sharing is required, and changeover/back between links within a single linkset are required. + +#### **T1.111.4 clause 5 - Signalling Message Handling** + +Since STP functionality is not required at the BSS the discrimination and routing functions of the MTP can be significantly simplified. + +#### **T1.111.4 clause 5.2 - Routing Label** + +Load sharing will be performed on BSSs with more than one signalling link by means of the Signalling Link Selection (SLS) field. + +#### **T1.111.4 clause 5.3 - Message Routing Function** + +It should be noted that for point to point working, load sharing between linksets is not required since only one linkset between the BSS and the MSC is required for the A-Interface. + +#### **T1.111.4 clause 5.4 - Message Discrimination** + +It is recommended that discarding a message at the BSS because of an incorrectly set point code should cause an incident report to be generated. + +At an MSC (which has the capability of acting as an STP) the messages not destined to it may be directed to the routing function. + +The signalling point code for an BSS may be included in the national signalling point code scheme or in a separate signalling network. In the case where the signalling point code is in the national network the MSC need have only one point code, in the case where signalling point code is in a separate PLMN signalling network, the MSC will be required to have two signalling point codes, one for each network. + +The User Part Unavailable message is not required for the A-Interface. + +#### **T1.111.4 clause 5.3.5** + +Support of ANSI specific Signalling Link Congestion Control as specified in this clause is required. + +#### **T1.111.4 clause 6 - Signalling Network Management** + +It should be noted that for point to point working, Signalling Route Management, including the status of signalling routes, signalling route restricted, signalling route unavailability and availability, is not required. + +#### **T1.111.4 clause 6.1.3 c)** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +#### **T1.111.4 clause 6.3.1.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **T1.111.4 clause 6.3.2.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **T1.111.4 clause 6.3.3.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **T1.111.4 clause 6.3.4.3** + +It should be noted that for point to point working, there is no requirement for signalling route management. + +##### **T1.111.4 clause 6.3.5.2** + +It should be noted that for point to point working, there is no requirement for signalling route management or signalling link blocking initiated by a management system. + +##### **T1.111.4 clause 6.3.6.2** + +It should be noted that for point to point working, there is no requirement for signalling route management or signalling link unblocking initiated by a management system. + +##### **T1.111.4 clause 6.4.1** + +It should be noted that for point to point working, the signalling route will become unavailable when the associated link set fails. + +#### **T1.111.4 clause 6.4.2** + +It should be noted that for point to point working, the signalling route will become available when the associated link set is restored. + +#### **T1.111.4 clause 6.4.3** + +Not applicable. + +#### **T1.111.4 clause 6.5.1** + +It should be noted that for point to point working the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in T1.111.4 clause 40.2.1. + +#### **T1.111.4 clause 6.5.2** + +It should be noted that for point to point interworking the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ANSI standard T1.111.4 clause 40.2.2. + +#### **T1.111.4 clause 6.5.3** + +Not applicable. + +#### **T1.111.4 clause 6.8.2** + +Support of ANSI specific Signalling Link Congestion Control as specified in this clause is required. + +#### **T1.111.4 clause 6.8.5.2** + +It should be noted that for point to point working, the signalling-route-set-congestion-test procedure is not required. + +#### **T1.111.4 clause 7 - Signalling Traffic Management** + +It should be noted that for point to point working, the Traffic Management procedures supporting signalling routes, including signalling route restricted, signalling route unavailability and availability, are not required. + +#### **T1.111.4 clause 7.1.2** + +It should be noted that for point to point working, signalling routes are not applicable. + +#### **T1.111.4 clause 7.2** + +The normal routing situation will be that there are one or more signalling links available between the BSS and the MSC, which will constitute a link set. They will be run in a load sharing mode and changeover, change back procedures will be supported between these signalling links. + +Furthermore, in case of more than one link set (not for point to point working), load sharing between link sets is also allowed. + +#### **T1.111.4 clause 7.3.3** + +It should be noted that for point to point working, alternative linksets are not required. + +#### **T1.111.4 clause 7.4.3** + +Not Applicable in case of point to point working. + +#### **T1.111.4 clause 7.5** + +Not Applicable in case of point to point working. + +#### **T1.111.4 clause 7.6** + +Not Applicable in case of point to point working. + +#### **T1.111.4 clause 7.7** + +Not Applicable. + +#### **T1.111.4 clause 8 - Changeover** + +It should be noted that for point to point working, the changeover procedure between linksets is not applicable. + +#### **T1.111.4 clause 9 - Changeback** + +It should be noted that for point to point working, the changeback procedure between linksets is not applicable. + +#### **T1.111.4 clause 40 - Forced Rerouting** + +It should be noted that for point to point working, forced rerouting is not applicable. + +#### **T1.111.4 clause 8 - Controlled Rerouting** + +It should be noted that for point to point working, controlled rerouting is not applicable. + +#### **T1.111.4 clause 9 - MTP Restart** + +The MTP Restart procedure is not required for the A-Interface. + +#### **T1.111.4 clause 41 - Signalling Traffic Flow Control** + +It should be noted that for point to point working, the signalling route procedures supporting signalling traffic flow control including signalling-route-unavailability, signalling-route availability and signalling-route-set-congestion are not applicable. + +#### **T1.111.4 clause 42 - Signalling Link Management** + +Only basic link management procedures are required for the A-Interface. + +#### **T1.111.4 clause 42.3.4 - Link set activation** + +Link set normal activation is not applicable. Link set emergency restart at the BSS is used in all cases. + +#### **T1.111.4 clause 43 - Signalling Route Management** + +It should be noted that for point to point working, signalling route management is not applicable. No action is required upon reception of a TFP, TFR, TFA, signalling-route-set-test, signalling-route-set-congestion-test or transfer controlled message in case of point to point working. + +#### **T1.111.4 clause 43.3 - Transfer allowed** + +It should be noted that for point to point working, the transfer allowed function is not applicable. **T1.111.4 clause 43.4 - Transfer restricted** + +It should be noted that for point to point working, the transfer restricted function is not applicable. + +#### **T1.111.4 clause 43.5 - Signalling-route-set-test** + +It should be noted that for point to point working, the signalling-route-set-test procedure is not applicable. + +#### **T1.111.4 clauses 13.6, 13.7 and 13.8 - Transfer controlled** + +It should be noted that for point to point working, the transfer controlled function is not applicable. + +#### **T1.111.4 clause 43.9 - Signalling route-set-congestion-test** + +It should be noted that for point to point working, the signalling route-set-congestion-test function is not applicable. + +#### **T1.111.4 clause 44.2.1 - Service Indicator** + +The values for the service indicator shall conform to clause 44.2.1. + +#### **T1.111.4 clause 44.2.2** + +The sub-service field will always be set to one of the following values: + +bits + +DC + +1 0     national network + +1 1     local network + +NOTE:    Local network value is not used for PCS 1900 in North America. + +#### **T1.111.4 clause 44.3** + +This information for SCCP is defined in ANSI T1.112.3. + +#### **T1.111.4 clause 45** + +The formats and codes listed are only relevant to the messages that are required for the A-Interface, i.e. those not excluded in the rest of this recommendation. + +## **6.5 Testing and Maintenance** + +### **6.5.1 E1 link (ITU-T Recommendation Q.707)** + +#### **Q.707 clause 5.2** + +The MSC and the BSS shall be capable of responding with an acknowledgement message to a SLTM received at any time as specified in ITU-T Recommendation Q.707 clause 5.2. + +### **6.5.2 T1 link (ANSI Specification T1.111.7)** + +#### **T1.111.7 clause 5.1 - Signalling Data Link Test** + +The signalling data link test is not required for the A-Interface. + +#### **T1.111.7 clause 5.2** + +The generation of a SLTM is not required; however, the MSC and the BSS shall be capable of responding with an acknowledgement message to a SLTM that is received at any time as specified in T1.111.7, clause 5.2. + +# --- **6a       Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA) functions** + +## **6a.1 Introduction** + +This subclause specifies the transport protocol stack that supports the transfer of BSSAP messages over an IP transport. + +The following requirements can be stated: + +- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode; + +- provide separate independent connections for distinguishing transactions with individual MS's; +- supervise the 'MS connections' and provide connection status information to the Upper Layers for individual MS's; +- provide networking and routing functions; +- provide redundancy in the signalling network; +- provide load sharing. + +## 6a.2 Protocol Stack + +Figure 1a below shows the point at which the service primitives are invoked. A single SAP is defined independently of the signalling bearer. The SAP provides the SCCP primitives. The figure is not intended to constrain the architecture. + +![Diagram of the Protocol Stack showing the Control Plane at the top, followed by BSSAP, SCCP-SAP (Service Access Point), SCCP, M3UA, SCTP, IP, and Data Link layers.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +The diagram illustrates the protocol stack for the Control Plane. At the top is a box labeled 'Control Plane'. Below it is a box labeled 'BSSAP'. A vertical line connects 'BSSAP' to a horizontal oval labeled 'SCCP-SAP'. Below the oval is another box labeled 'SCCP'. This is followed by a box labeled 'M3UA', then 'SCTP', then 'IP', and finally 'Data Link' at the bottom. All boxes are connected by a central vertical line. + +Diagram of the Protocol Stack showing the Control Plane at the top, followed by BSSAP, SCCP-SAP (Service Access Point), SCCP, M3UA, SCTP, IP, and Data Link layers. + +**Figure 6a.2.a: SAP between BSSAP and its transport over IP** + +1. **SCCP** [62] provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis. +2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " [73] also developed by the Sigtran working group of the IETF. +3. **SCTP** refers to the Stream Control Transmission Protocol [72] developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. The checksum method specified in RFC 3309 [81] shall be used instead of the method specified in RFC 2960 [72]. +4. **IP**. IPv6 should be supported according to [83]. IPv4 support [82] is optional. + +**NOTE:** This does not preclude the single implementation and use of IPv4. Due to the possible transition from IPv4 to IPv6 the IP dual stack support is recommended. + +A BSC/MSC using IP transport shall support Diffserv code point marking [80]. The Diffserv code point may be determined from the application parameters. + +## 6a.3 Data Link Layer + +It is recommended that a BSC/MSC using IP transport implement the data link layer using Ethernet. + +**NOTE:** This does not preclude the single implementation and use of any other data link layer protocol fulfilling the GERAN requirements toward the upper layers. + +A BSC/MSC using IP transport having interfaces connected via low bandwidth PPP links like E1/T1 shall also support IP Header Compression [76] and the PPP extensions ML/MC-PPP [77], [78]. In this case, the negotiation of header compression [76] over PPP shall be performed according to [79]. + +# --- 7 Interface functions + +The method of interfacing to the higher layers will be by the primitives defined in ITU-T Recommendation Q.701 clause 8 of the Blue Book for E1 links and T1.111 for T1 links. + +The primitives defined are: + +- MTP Pause indication; +- MTP Resume indication; +- MTP Status indication; +- MTP Transfer request; +- MTP Transfer indication. + +# --- 8 SCCP functions + +## 8.1 + +Ov + +###### erview + +The purpose of this clause is to identify the subset of the SCCP functions which are necessary to achieve the management of the MS references in the BSS to MSC interface, and to provide addressing facilities. If this subset of SCCP functions is implemented, compatibility with a full ITU-T SCCP (ANSI SCCP if T1 links are used) must be maintained for E1 links (T1 links). Only the needs of the BSSAP are taken into account in clause 8: the operations and maintenance requirements about SCCP functions are discussed in clause 40. + +These simplifications are applicable to the signalling between BSS and MSC in GSM PLMNs. + +In order to limit the complexity of the procedures, a BSS exchanges signalling messages only with its MSC, where a protocol conversion may be needed in some cases. Therefore no SCCP translation function is required in the MSC between the national and the local MTP. The Destination Point Code and Subsystem Number allow direct routing by the local SCCP and MTP within the MSC area. Therefore, no SCCP Global Title Translation (GTT) function is required. + +Several functions of the SCCP are not used on the MSC/BSS interface: error detection, receipt confirmation, flow control. + +The segmenting/reassembling function shall be used if the total message length exceeds the maximum allowed message length that can be carried by the MTP. + +For E1 links, the minimum set of SCCP functions which apply are specified in the Blue Book ITU-T Recommendations Q.711, Q.712, Q.713 and Q.714, with the qualifications specified in this Recommendation. + +For T1 links, the minimum set of SCCP functions which apply are specified in ANSI T1.112 with the qualifications specified in this Recommendation. + +## 8.2 Primitives + +### 8.2.1 E1 link (ITU-T Recommendation Q.711) + +#### Q.711 table 1 + +Three primitives of the table 1/Q.711 are not used: + +- N-EXPEDITED DATA; +- N-DATA ACKNOWLEDGE; + +- N-RESET. + +#### **Q.711 table 2** + +The following parameters of the N-CONNECT primitive are not used: + +- responding address; +- receipt confirmation selection; +- expedited data selection. + +#### **Q.711 table 3** + +The following parameter of the N-DATA primitive is not used: + +- confirmation request. + +#### **Q.711 table 6** + +The following parameter of the N-DISCONNECT primitive is not used: + +- responding address. + +#### **Q.711 clause 5.1.2** + +Permanent signalling connections: not applicable. + +##### **Q.711 table 9** + +The primitive N-NOTICE is not used. + +##### **Q.711 table 10** + +The following parameter of the N-UNITDATA is not used: + +- return option. + +##### **Q.711 clause 7.1.2** + +Functions for permanent signalling connections: not applicable. + +### **8.2.2 T1 link (ANSI Specification T1.112.1)** + +#### **T1.111.1 table 1** + +Two primitives of the table are not used: + +- N-INFORM DATA; +- N-RESET. + +#### **T1.112.1 table 2** + +The following parameters of the N-CONNECT primitive are not used: + +- responding address; +- receipt confirmation selection; +- expedited data selection. + +#### **T1.112.1 table 3** + +The following parameter of the N-DATA primitive is not used: + +- confirmation request. + +#### **T1.112.1 table 6** + +The following parameter of the N-DISCONNECT primitive is not used: + +- responding address. + +#### **T1.112.1 clause 2.1.2** + +Permanent signalling connections are not applicable. + +#### **T1.112.1 table 8** + +The primitive N-NOTICE is not used. + +#### **T1.112.1 table 8A** + +The following parameter of the N-UNITDATA is not used: + +- return option. + +#### **T1.112.1 clause 4.1.2** + +Functions for permanent signalling connections are not applicable. + +## **8.3 SCCP messages** + +### **8.3.1 E1 link (ITU-T Recommendation Q.712)** + +#### **Q.712 clause 4.4** + +The Data Acknowledgement (AK) message is not used. + +#### **Q.712 clause 4.6** + +The Data Form 2 (DT2) message is not used. + +#### **Q.712 clause 4.7** + +The Expedited Data (ED) message is not used. + +#### **Q.712 clause 4.8** + +The Expedited Data Acknowledgement (EA) message is not used. + +#### **Q.712 clause 4.10** + +The Protocol Data Unit Error (ERR) message is not used: the inconsistent messages of the SCCP protocol are discarded. + +##### **Q.712 clause 4.13** + +The Reset Confirm (RSC) message is not used. + +##### **Q.712 clause 4.14** + +The Reset Request (RSR) message is not used. + +##### **Q.712 clause 4.16** + +The Subsystem-Out-Of-Service-Grant (SOG) message is not used. + +##### **Q.712 clause 4.17** + +The Subsystem-Out-Of-Service-Request (SOR) message is not used. + +##### **Q.712 clause 4.21** + +The Unitdata Service (UDTS) message is not used. + +#### **Q.712 clause 5.4** + +The "credit" parameter field is not used for protocol class 2. However the parameter must still be included in the IT message for syntax reasons. + +##### **Q.712 clause 5.7** + +The "error cause" parameter field is not used. + +#### **Q.712 clause 5.11** + +The "receive sequence number" parameter is not used. + +#### **Q.712 clause 5.14** + +The "reset cause" parameter field should not be used. + +#### **Q.712 clause 5.16** + +The "sequencing/segmenting" parameter field is not used for protocol class 2. However the parameter must still be included in the IT message for syntax reasons. + +### **8.3.2 T1 link (ANSI Specification T1.112.2)** + +#### **T1.112.2 clause 5.4** + +The Data Acknowledgement (AK) message is not used. + +#### **T1.112.2 clause 5.6** + +The Data Form 2 (DT2) message is not used. + +#### **T1.112.2 clause 5.7** + +The Expedited Data (ED) message is not used. + +#### **T1.112.2 clause 5.8** + +The Expedited Data Acknowledgement (EA) message is not used. + +#### **T1.112.2 clause 5.10** + +The Protocol Data Unit Error (ERR) message is not used. Inconsistent messages of the SCCP protocol are discarded. + +#### **T1.112.2 clause 5.13** + +The Reset Confirm (RSC) message is not used. + +#### **T1.112.2 clause 5.14** + +The Reset Request (RSR) message is not used. + +#### **T1.112.2 clause 5.16** + +The Unitdata Service (UDTS) message is not used. + +#### **T1.112.2 clause 6.4** + +The Subsystem-Out-Of-Service-Request (SOR) message is not used. + +#### **T1.112.2 clause 6.5** + +The Subsystem-Out-Of-Service-Grant (SOG) message is not used. + +#### **T1.112.2 clause 7.2** + +The "credit" parameter field is not used for protocol class 2. However, the parameter must still be included in the Inactivity Test (IT) message for syntax reasons. + +#### **T1.112.2 clause 7.6** + +The "error cause" parameter field is not used. + +#### **T1.112.2 clause 7.10** + +The "receive sequence number" parameter is not used. + +#### **T1.112.2 clause 7.13** + +The "reset cause" parameter field should not be used. + +#### **T1.112.2 clause 7.16** + +The "sequencing/segmenting" parameter field is not used for protocol class 2. However, the parameter must still be included in the IT message for syntax reasons. + +## **8.4 SCCP formats and codes** + +### **8.4.1 E1 link (ITU-T Recommendation Q.713)** + +#### **Q.713 clause 6.4** + +For point-to-point network structures (i.e. direct connections between MSC and BSS) the called party address may consist of the single element: + +- sub-system number. + +No global title is used. The signalling point code which is coded in the MTP routing label and the subsystem number in the called party address allow the routing of the message. + +Then the following encoding of the address indicator may be chosen: **X1000010**. + +If a non point-to-point network structure is used then the global title may be required. This is a national concern. + +#### **Q.713 clause 6.4.2.2** + +The SSN values used on the MSC - BSS interface are specified in 3GPP TS 23.003. + +Use of alternative values is a national concern. + +##### **Q.713 clause 6.4.2.3** + +Global title: refer to ITU-T Recommendation Q.713 clause 6.4. + +##### **Q.713 clause 6.6** + +Protocol class: the classes 1 and 3 are not used. + +##### **Q.713 clauses 3.8, 3.9, 3.10, 3.13 and 3.14** + +Parameters not used. + +##### **Q.713 clauses 4.8, 4.9, 4.11, 4.12, 4.13, 4.14, 4.15 and 4.16** + +Messages not used. + +##### **Q.713 clause 8.1.1** + +SOR and SOG not needed. + +### **8.4.2 T1 link (ANSI Specification T1.112.3)** + +#### **T1.112.3 clause 3.4** + +For point-to-point network structures (i.e., direct connections between the MSC and the BSS) the called party address may consist of the single element: + +- subsystem number. + +No global title is used. The signalling point code which is coded in the MTP routing label and the subsystem number in the called party address allow the routing of the message. Then the following encoding of the address indicator may be chosen: **x1000001**. + +Separate SSNs are needed to distinguish BSSAP and MAP; the chosen SSNs are network specific and may need to differ from those assigned to other applications (e.g. TCAP applications). + +#### **T1.112.3 clause 6.4.2.2** + +Allocation of the subsystem number is an operator concern. + +#### **T1.112.3 clause 6.4.2.3** + +#### **T1.112.3 clause 6.4** + +#### **T1.112.3 clause 6.6** + +Protocol class: the classes 1 and 3 are not used. + +#### **T1.112.3 clauses 3.8, 3.9, 3.10, 3.13 and 3.14** + +Parameters are not used. + +#### **T1.112.3 clauses 4.8, 4.9, 4.11, 4.12, 4.13, 4.14, 4.15 and 4.16** + +Messages are not used. + +#### **T1.112.3 clause 8.1.1** + +Subsystem-out-of-service-request (SOR) and Subsystem-out-of-service-grant (SOG) are not needed. + +## **8.5 SCCP procedures** + +### **8.5.1 E1 link (ITU-T Recommendation Q.714)** + +#### **Q.714 clauses 1.1.2.2 and 1.1.2.4** + +Protocol classes 1 and 3 not used. + +##### **Q.714 clause 4.1.3** + +A signalling connection consists of a single connection clause. No intermediate nodes are defined in the MSC/BSS protocol. + +The use of multiple connection clauses is a national concern. + +##### **Q.714 clause 4.2.1 (b)** + +Not applicable for single connections. + +##### **Q.714 clause 5.1 (1.)** + +Global title not used for single connections. + +##### **Q.714 clause 5.2.1** + +Subsystem (SSN) only is present in the called party address for single connections. + +##### **Q.714 clause 5.2.2** + +The addressing information may take the following form in the N-CONNECT request primitive: DPC+SSN (for single connections). + +#### **Q.714 clause 5.2.2.2** + +No SCCP translation function is required for single connections. + +##### **Q.714 clause 5.3.1 (3)** + +Not applicable for single connections. + +##### **Q.714 clause 5.3.2 (4)** + +Not applicable for single connections. + +##### **Q.714 clause 6.1.3** + +Not applicable: no protocol class and flow control negotiations. + +##### **Q.714 clause 6.1.5** + +Not applicable. + +##### **Q.714 clause 6.2.2** + +Not applicable. + +##### **Q.714 clause 6.3.4** + +Not applicable. + +##### **Q.714 clause 6.5.1.2** + +Not applicable. + +##### **Q.714 clause 6.5.2** + +Not applicable. + +##### **Q.714 clauses 3.6, 3.7, 3.9 and 3.10** + +Not applicable. + +##### **Q.714 clause 7.2** + +Message return not applicable. + +##### **Q.714 clause 8** + +Only those messages and procedures relating to non-replicated subsystems or nodes are required. At the BSS the concerned point will be the parent MSC. The subsystems involved are the BSSAP and the OMAP. + +### 8.5.2 T1 link (ANSI Specification T1.112.4) + +#### **T1.112.4 clauses 1.1.2.2 and 1.1.2.4** + +Protocol classes 1 and 3 are not used. + +##### **T1.112.4 clause 4.1.3** + +A signalling connection consists of a single connection clause. No intermediate nodes are defined in the MSC to BSS interface. + +The use of multiple connection clauses is a operator option. + +##### **T1.112.4 clause 4.2.1 (b)** + +Not applicable for single connections. + +##### **T1.112.4 clause 5.1 (1.)** + +Global title is not used for single connections. + +##### **T1.112.4 clause 5.2.1** + +Subsystem number (SSN) only is present in the called party address for single connections. + +#### **T1.112.4 clause 5.2.2** + +The addressing information may take the following form in the N-CONNECT request primitive: DPC+SSN (for single connections). + +##### **T1.112.4 clause 5.2.2.2** + +No SCCP translation function is required for single connections. + +##### **T1.112.4 clause 5.3.1 (3)** + +Not applicable for single connections. + +##### **T1.112.4 clause 5.3.2 (4)** + +Not applicable for single connections. + +##### **T1.112.4 clause 6.1.3** + +Not applicable. No protocol class and flow control negotiations. + +##### **T1.112.4 clause 6.1.5** + +Not applicable. + +##### **T1.112.4 clause 6.2.2** + +Not applicable. + +#### **T1.112.4 clause 6.3.4** + +Not applicable. + +##### **T1.112.4 clause 6.5.1.2** + +Not applicable. + +##### **T1.112.4 clause 6.5.2** + +Not applicable. + +##### **T1.112.4 clauses 3.6, 3.7, 3.9 and 3.10** + +Not applicable. + +#### **T1.112.4 clause 7.2** + +Message return is not applicable. + +#### **T1.112.4 clause 8** + +Only those messages and procedures relating to non-replicated subsystems or nodes are required. At the BSS the concerned point will be the parent MSC. The subsystems involved are the BSSAP and the MAP. + +# 9 Use of the SCCP + +The MTP and the SCCP are used to support signalling messages between the MSC and the BSS. One user function of the SCCP, called BSS Application Part (BSSAP) is defined. In the case of point-to-point calls the BSSAP uses one signalling connection per active Mobile Station having one or more active transactions for the transfer of layer 3 messages. In the case of a voice group or broadcast call there is always one connection per cell involved in the call and one additional connection per BSS for the transmission of layer 3 messages. There is an additional connection for the speaker in a broadcast call or the first speaker in a voice group call up to the point at which the network decides to transfer them to a common channel. Additional connections may also be required for any mobile stations in the voice group or broadcast call which the network decides to place on a dedicated connection. The BSSAP user function is further subdivided into two separate functions: + +- the Direct Transfer Application sub-Part (DTAP) is used to transfer messages between the MSC and the MS; the layer-3 information in these messages is not interpreted by the BSS. The descriptions of the layer 3 protocols for the MS-MSC information exchange are contained in the 04-series of 3GPP TS Technical Specifications; +- the BSS Management Application sub-Part (BSSMAP) supports other procedures between the MSC and the BSS related to the MS (resource management, handover control), or to a cell within the BSS, or to the whole BSS. The description of the layer 3 protocol for the BSSMAP information exchange is contained in 3GPP TS 48.008. + +Both connectionless and connection-oriented procedures are used to support the BSSMAP. 3GPP TS 48.008 explains whether connection oriented or connectionless services should be used for each layer 3 procedure. Connection oriented procedures are used to support the DTAP. Clause 9.4 deals with the use of connectionless services of the SCCP. + +A distribution function located in BSSAP, which is reflected in the protocol specification by the layer 3 header defined in clause 9.3, performs the discrimination between the data related to those two subparts, as illustrated in 3GPP TS 48.008, figure 1. + +The error handling for the BSSAP header is specified in 3GPP TS 48.008. + +This clause describes the use of SCCP connections for MS transactions. Clause 9.1 describes the connection establishment procedures. Clause 9.2 describes the connection release procedures. Clause 9.3 describes the distribution between BSSMAP and DTAP messages and the data transfer over a SCCP connection. The structure of the user data field in the SCCP message is described in clauses 9.3 and 9.4 and in figure 3. + +## 9.1 Connection establishment + +A new SCCP connection is established when information related to the communication between an MS and the network on a dedicated radio resource has to be exchanged between BSS and MSC, and no such SCCP connection exists between the MSC and the BSS involved for the concerned mobile station. A new SCCP connection for each cell, an additional connection for each BSS, and optionally connections for particular participants in a voice group or broadcast call are established when a voice group or broadcast call is established. A new SCCP connection is also established in the case of an external handover between the cells of one BSS for a point-to-point call, or for participants in a voice group or broadcast call who are supported on a dedicated channel. + +Various SCCP connection establishment cases have to be distinguished: + +- i) following an Access Request made by the MS on the Random Access Channel, a dedicated radio resource has been successfully allocated and a layer-2 connection has been established on the allocated resource. The SCCP connection establishment is then initiated by the BSS; +- ii) the MSC decides to perform an external handover and a new dedicated radio resource has to be reserved in the new BSS. The SCCP connection establishment is then initiated by the MSC; + +NOTE: The old BSS and the new BSS may be the same. + +- iii) following a request for a voice group or broadcast call received at a MSC, SCCP connections are established between the MSC and BSS. This is initiated by the MSC. Note that a SCCP connection for the originator has already been established via case i); +- iv) during a voice group or broadcast call the network may decide to place some participants on a dedicated channel and will perform SCCP connection establishment to support this channel. + +The above cases are the only cases currently identified for SCCP connection establishment. Others may emerge in the future. + +![Sequence diagram for SCCP connection setup on the first BSS/MSC interface. The diagram shows a Connection Request (CR) from BSS to MSC, followed by a Connection Confirm (CC) or Connection Refused (CREF) from MSC to BSS. Definitions for a1 and a2 are provided at the bottom.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + +sequenceDiagram + participant BSS + participant MSC + Note right of BSS: BSS + Note right of MSC: MSC + BSS->>MSC: CR {SSN=BSSAP, a1, BSSMAP message} + MSC-->>BSS: CC {a1,a2, BSSMAP or DTAP message or no user data} + Note right of MSC: or + Note right of MSC: CREF{a2, DTAP message or no user data} + MSC-->>BSS: CREF{a2, DTAP message or no user data} + Note right of BSS: a1 = source local reference, +a2 = destination local reference + +``` + +Sequence diagram for SCCP connection setup on the first BSS/MSC interface. The diagram shows a Connection Request (CR) from BSS to MSC, followed by a Connection Confirm (CC) or Connection Refused (CREF) from MSC to BSS. Definitions for a1 and a2 are provided at the bottom. + +- CC: Connection Confirm. +- CR: Connection Request. +- CREF: Connection Refused. + +**Figure 1: Set-up of SCCP connections on the first BSS/MSC interface** + +![Sequence diagram for SCCP connection setup on a new BSS/MSC interface (handover) or for a voice group or broadcast call initiation. The diagram shows a Connection Request (CR) from BSS to MSC, followed by a Connection Confirm (CC) or Connection Refused (CREF) from MSC to BSS. Definitions for a1 and a2 are provided at the bottom.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +``` + +sequenceDiagram + participant BSS + participant MSC + Note right of BSS: BSS + Note right of MSC: MSC + BSS->>MSC: CR {SSN=BSSAP, a1, BSSMAP message or no user data} + MSC-->>BSS: CC {a1, a2, BSSMAP message or no user data} + Note right of MSC: or + Note right of MSC: CREF{a2, BSSMAP message or no user data} + MSC-->>BSS: CREF{a2, BSSMAP message or no user data} + Note right of BSS: a1 = source local reference, +a2 = destination local reference + +``` + +Sequence diagram for SCCP connection setup on a new BSS/MSC interface (handover) or for a voice group or broadcast call initiation. The diagram shows a Connection Request (CR) from BSS to MSC, followed by a Connection Confirm (CC) or Connection Refused (CREF) from MSC to BSS. Definitions for a1 and a2 are provided at the bottom. + +- CC: Connection Confirm. +- CR: Connection Request. +- CREF: Connection Refused. + +**Figure 2: Set-up of SCCP connections on a new BSS/MSC (handover) interface or for a voice group or broadcast call initiation** + +### 9.1.1 + +Esta + +#### blishment procedure in case i) + +In this case, the connection establishment is performed at the reception by the BSS of the first layer-3 message from the MS (piggybacked on the SABM frame). This message (LOCATION UPDATING REQUEST, CM-SERVICE REQUEST, CM REESTABLISHMENT REQUEST, IMSI DETACH, PAGING RESPONSE, or IMMEDIATE SETUP) which contains the identity of the MS is transferred to the MSC together with a cell identification, in a BSSMAP message (COMPLETE L3 INFORMATION) included in the user data field of the SCCP Connection Request message (see figure 1). + +After the reception of the Connection Request message, the MSC may check, based on the received identity, whether another association already exists for the same Mobile Subscriber. Two options among others are described hereafter: + +- after the reception of the Connection Request message, the MSC sends a Connection Confirm message and checks based on the received identity, whether another connection already exists for the same Mobile Subscriber. If another connection exists for the same Mobile Subscriber, the resources assigned for this previous connection are released after the identity of the Mobile Subscriber using the new connection has been successfully checked, e.g. by authentication or by ciphering procedure; +- if such an association exists, the connection establishment is refused by sending a Connection Refused message; + +NOTE: The first option allows the new establishments and the reestablishments. + +- when the SCCP connection is to be established, a Connection Confirm message is sent back to the BSS. This message may optionally contain a BSSMAP or DTAP message in the user data field. + +If the connection establishment is refused for any reason, a SCCP Connection Refused message is sent back to the BSS. This message may optionally contain, in the user data field, a DTAP message which is forwarded to the MS. + +The procedures in case of connection establishment failure are specified in 3GPP TS 48.008. + +### 9.1.2 + +Esta + +#### blishment procedure in case ii) + +In this case, the connection establishment is undertaken by the MSC as soon as the MSC decides to perform an external handover to a new cell for a point-to-point call or for participants in a voice group or broadcast call who are supported on a dedicated channel. + +A Connection Request message is sent to the BSS. The user data field of this message may contain the BSSMAP HANDOVER REQUEST message (see figure 2). It is preferable to transfer the layer 3 messages in the user data field of the Connection Request in order to complete the establishment of the relation between the radio channel requested and the SCCP connection as soon as possible. However, the MSC shall not piggyback the BSSMAP HANDOVER REQUEST message in the SCCP Connection Request message if that would result in the maximum length of the user data field being exceeded. + +When receiving the Connection Request message, containing the BSSMAP HANDOVER REQUEST message, the BSS allocates the necessary resources for the requested handover. A Connection Confirm message is also returned to the MSC and may contain the BSSMAP HANDOVER REQUEST ACKNOWLEDGEMENT or QUEUEING INDICATION message in the user data field. + +If the handover resource allocation fails (see 3GPP TS 48.008) before the SCCP connection is established then the SCCP Connection Refused message may contain the BSSMAP HANDOVER FAILURE message in the user data field. + +The procedures in case of connection establishment failure are specified in 3GPP TS 48.008. + +### 9.1.3 + +Esta + +#### blishment procedure in case iii) + +In this case connection establishment is undertaken by the MSC on the reception of a voice group or broadcast call initiation request. + +At the reception of the voice group or broadcast call establishment request message, the MSC will determine that a voice group or broadcast call is required and retrieve the required information concerning, inter alia, the affected cells. If A-interface link sharing does not apply, SCCP connections are then established by the MSC to the BSS for each of these cells. Otherwise, if A-interface link sharing applies, only one SCCP connection is established by the MSC to the BSS. Additionally, a separate SCCP connection is established by the MSC to each BSS in the call. + +For each SCCP connection to be established, a Connection Request message is sent to the BSS. The user data field of this message may contain the VGCS/VBS SETUP or VGCS/VBS ASSIGNMENT REQUEST message (see figure 2). It is preferable to transfer the layer 3 messages in the user data field of the Connection Request in order to complete the establishment of the relation between the radio channel requested and the SCCP connection as soon as possible. + +When receiving the Connection Request message, containing the VGCS/VBS SETUP or VGCS/VBS ASSIGNMENT REQUEST message, the BSS allocates the necessary resources for the requested call. A Connection Confirm message is also returned to the MSC and may contain the VGCS/VBS SETUP ACK, VGCS/VBS ASSIGNMENT RESULT or VGCS/VBS QUEUEING INDICATION message in the user data field. + +If the resource allocation fails (see 3GPP TS 48.008) before the SCCP connection is established then the SCCP Connection Refused message may contain the VGCS/VBS SETUP REFUSE or VGCS/VBS ASSIGNMENT FAILURE message in the user data field. + +The procedures in case of connection establishment failure are specified in 3GPP TS 48.008. + +### 9.1.4 + +Esta + +#### blishment procedure in case iv) + +In this case, the connection establishment may be performed at the request of the MSC. + +The procedures in case of connection establishment failure are specified in 3GPP TS 48.008. + +## 9.2 + +Co + +## nnection release + +This procedure is always initiated at the MSC side. + +A connection is released when the MSC realizes that a given signalling connection is no longer required. That may occur, in normal cases: + +- when a BSSAP release procedure is terminated; +- when a handover resource allocation procedure has failed and a signalling connection was established; +- when a VGCS/VBS set-up procedure has failed and a call controlling SCCP signalling connection was established; +- when a VGCS/VBS assignment procedure has failed and a resource controlling SCCP signalling connection was established. + +The MSC sends a SCCP released message. This message shall not contain any user data field. + +Abnormal cases: a connection failure may be detected by the connection supervision service provided by SCCP. The procedures in that case are specified in 3GPP TS 48.008. + +## 9.3 + +Tra + +### nsfer of DTAP and BSSMAP data + +The DTAP and BSSMAP Layer 3 messages between the MSC and the BSS are contained in the user data field of the exchanged SCCP frames. This field is optional for the Connection Request (CR) (except for BSS originated connections, see clause 9.1); Connection Confirm (CC) and Connection Refused (CREF). The use of this field in such frames in the various establishment cases, which allows reduction in delay and improves efficiency, is described in clause 9.1. The user data field is a mandatory parameter of the Data frames (DT); the user data field always contains either a DTAP or a BSSMAP message. + +### 9.3.1 + +Dist + +#### ribution function + +#### 9.3.1.1 ITU-T Recommendation + +The distribution of messages between the BSSMAP and DTAP functions and the distribution/multiplexing of DTAP messages to/from the various radio link layer 2 access points are performed in an intermediate layer of protocol between SCCP and Layer 3 later referred as the distribution sublayer. + +The protocol for this sublayer simply consists of the management of a one or two octet Distribution Data Unit. Each SCCP User Data field necessarily contains such a distribution Data Unit as a header, followed by the length indicator and the actual Layer 3 BSSMAP or DTAP message. + +#### 9.3.1.2 ANSI Specification + +The distribution of messages between the BSSMAP and DTAP functions and the distribution/multiplexing of DTAP messages to/from the various radio link layer 2 access points are performed by a function of BSSAP referred to as a distribution function. The distribution of messages is performed based on a distribution data unit. + +The distribution data unit includes a Discrimination Parameter (DP) field, which is coded on one octet. One bit (i.e. least significant bit) of the octet referred as a bit D indicates whether it is a DTAP (value D=1) or a BSSMAP (value D=0) message. The other bits of the octet can be used to separate message groups for different air interfaces (Figure below). + +If a single radio system supports one air interface, the A-interface includes only one message group and no separation between message groups is needed. The case is different when radio system supports multiple air interfaces, and the A-interface includes several message groups. In that case, there must be a mechanism which facilitates the selection of the right message group according to the used air interface. + +![Diagram showing the distribution of message groups (DTAP and RS MAP) across three air interfaces (air interface 1, 2, and 3) through a Distribution function, which is part of the RSAP layer above SCCP and MTP.](4aecd812144e7d8c5264d03046f16dfb_img.jpg) + +The diagram illustrates the RSAP (Radio System Application Part) layer structure. At the top, three boxes represent 'air interface 1', 'air interface 2', and 'air interface 3'. Each box contains two sub-components: 'DTAP' and 'RS MAP'. Below each box is a specific Discrimination Parameter (DP) value: 'DP = 0000000D' for air interface 1, 'DP = 1000000D' for air interface 2, and 'DP = 0100000D' for air interface 3. Arrows from these DP values point down to a central horizontal line labeled 'Distribution function'. Below this line is a box for 'SCCP', and at the bottom is a box for 'MTP'. + +Diagram showing the distribution of message groups (DTAP and RS MAP) across three air interfaces (air interface 1, 2, and 3) through a Distribution function, which is part of the RSAP layer above SCCP and MTP. + +Figure 2a: Distribution of message groups according to examples of the air interface types + +### 9.3.2 + +Tra + +#### nsfer of DTAP messages + +The DTAP function is in charge of transferring layer 3 messages from the MS (resp from the MSC) to the MSC (resp to the MS) without any analysis of the message contents. The interworking between the layer 2 protocol on the radio side and signalling system 7 at the landside is based on the use of individual SCCP connections for each MS and on the distribution function. + +The structure of the user data field is given in figure 3. The user data field contains a distribution data unit, a length indicator, and the actual layer 3 message. + +The Distribution Data Unit consists of two parameters: the Discrimination parameter and the Data Link Connection Identification (DLCI) parameter. + +The Discrimination parameter, which is set to the "Transparent" value, is coded on one octet, as follows: + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | D | + +The discrimination bit D is set to the "Transparent" value 1. + +The DLCI parameter is used for MSC to BSS messages to indicate the type of data link connection to be used over the radio interface. In the direction BSS to MSC the DLCI parameter is used to indicate the type of originating data link connection over the radio interface. The DLCI parameter is coded in one octet, as follows: + +| | | | | | | | | +|----|----|---|---|---|----|----|----| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| C2 | C1 | 0 | 0 | 0 | S3 | S2 | S1 | + +C2 C1 represents the control channel identification; + +C2=0; C1=0 indicates that the control channel is not further specified; + +C2=1; C1=0 represents the FACCH or the SDCCH; + +C2=1; C1=1 represents the SACCH; + +other values are reserved. + +S3 S2 S1 represents the SAPI value used on the radio link, which coding is specified in 3GPP TS 44.006. + +Bits 4, 5 and 6 are spare. + +The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter. + +### 9.3.3 Transfer of BSSMAP messages + +The transfer of BSSMAP messages over a SCCP connection allows the BSSMAP functions in both the MSC and the BSS to identify to which particular Mobile Station association the exchanged message (e.g. assign, handover request, etc..) applies. + +The structure of the user data field is given in figure 3. The user data field contains a distribution data unit, a length indicator, and the actual layer 3 message. + +The Distribution Data Unit only consists of the Discrimination parameter, which is set to the "Not Transparent" value. + +This parameter is coded on one octet, as follows: + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | D | + +The discrimination bit D is set to the "Not Transparent" value 0. + +The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter. + +The coding of the BSSMAP layer 3 messages is specified in 3GPP TS 48.008. + +## 9.4 + +Co + +## nnectionless services + +Some BSSMAP procedures described in 3GPP TS 48.008 use the connectionless services of the SCCP. + +The structure of the user data field of the unit data message (UDT) is given in figure 3. The user data field contains a distribution data unit, a length indicator, and the actual layer 3 message. + +The Distribution Data Unit only consists of the Discrimination parameter, which is set to the "Not Transparent" value. + +### 9.4.1 Discrimination parameter (ITU-T Recommendation) + +This parameter is coded on one octet, as follows: + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | D | + +The discrimination bit D is set to the "Not Transparent" value 0. + +The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter. + +The coding of the BSSMAP layer 3 messages is specified in 3GPP TS 48.008. + +### 9.4.2 Discrimination parameter (ANSI Specification) + +This parameter is coded on one octet, as follows: + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| X | x | X | x | x | x | x | D | + +The discrimination bit D is set to the "BSSMAP" value 0. + +The bits indicated with X values denote to air interface message groups as shown in the table "Coding Of The Discrimination Parameter for PCS 1900" (see clause 9.3.2.2). + +The length indicator is coded in one octet, and is the binary representation of the number of octets of the subsequent layer 3 message parameter. + +### 9.4.3 User Data Field Structure + +![](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +| DTAP | | BSSMAP | | +|----------------------------------|----------------|---------|----------------| +| 1 | DISCRIMINATION | 1 | DISCRIMINATION | +| +-----+ | | +-----+ | | +| 2 | DLCI | | | +| +-----+ | | | | +| -----Distribution Data Unit----- | | | | +| 3 | LENGTH IND L | 2 | LENGTH IND L | +| +-----+ | | +-----+ | | +| -----Length Indicator----- | | | | +| 4 | LAYER 3 | 3 | LAYER 3 | +| +-----+ | | +-----+ | | +| : | | : | | +| : | | : | | +| L+3 | MESSAGE | L+2 | MESSAGE | +| +-----+ | | +-----+ | | +| -----Layer 3 message----- | | | | + +Figure 3: Structure of the User Data Field + +# 10 Use of the SCCP for operations and maintenance + +O&M messages have to be passed between the O&M functions and the BSS. + +If the O&M functions use the MSC-BSS interface to transport messages to the BSS, then the SCCP of No.7 should be used. + +X25 may also be used for the transfer of O&M messages between BSS and OMC, this is not further considered in the present document. + +## 10.1 + +Co + +## nnectionless service + +The connectionless service of the SCCP is supported at the BSS for management purposes and can be used for the transport of O&M information. Addressing should be decided by the operator and manufacturer (e.g. by E164 number, this may require additional addressing capability at the BSS). + +Further information is given concerning the coding of the higher levels of the O&M information in the 3GPP TS 12.xx series of Technical Specifications. + +## 10.2 + +Co + +## nnection oriented services + +Connection oriented services are also supported by the BSS for management and call control. Connection oriented services can also be used for the transport of O&M information. In order to set up the connection additional addressing capability may be required at the BSS. To use a signalling connection between the BSS and the OMC via the MSC requires the same BSSOMAP-SCCP interface at both the BSS and the OMC. + +## 10.3 + +**BS** + +## S failure + +If a system failure at the BSS occurs then sufficient MTP functions to allow message transmission and reception should be maintained. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|-----------------|-----------|------------|----------------------------------------|------------| +| January 2016 | - | - | - | Version 13.0.0 based on version 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|----------------------------------------------------|--------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48008/0036103c276f2dbcea4dccf73e47a2ff_img.jpg b/marked/Rel-16/48_series/48008/0036103c276f2dbcea4dccf73e47a2ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c856bc0bffb7dd2c69ae60d708f1282a9d9f230 --- /dev/null +++ b/marked/Rel-16/48_series/48008/0036103c276f2dbcea4dccf73e47a2ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5275e16748ca1c4bdf476466cdaa55a5b34c3582c3a32960a857e6214c0232c +size 24436 diff --git a/marked/Rel-16/48_series/48008/09cef6267096187ea2ec3fa61909d695_img.jpg b/marked/Rel-16/48_series/48008/09cef6267096187ea2ec3fa61909d695_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0eea79d1eeba350260f15d09a495ea8b17248099 --- /dev/null +++ b/marked/Rel-16/48_series/48008/09cef6267096187ea2ec3fa61909d695_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82bdfd2f6ba3174088a7fe0759a27ed065887e2f56493e8ad7bb1893e2edaec1 +size 18715 diff --git a/marked/Rel-16/48_series/48008/14af2781d0bd19b98b10672b74daaca2_img.jpg b/marked/Rel-16/48_series/48008/14af2781d0bd19b98b10672b74daaca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a4293a7f91599043a67f563947b53a5d73e3eea --- /dev/null +++ b/marked/Rel-16/48_series/48008/14af2781d0bd19b98b10672b74daaca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92f4dfb11dafc13c9ede855005456bcdb156cb4747202e7c682239af6a36e12e +size 42566 diff --git a/marked/Rel-16/48_series/48008/1e8845a639705010d5cda27146b8827f_img.jpg b/marked/Rel-16/48_series/48008/1e8845a639705010d5cda27146b8827f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71708618761e5e86076bf45400c704bb0d3806a9 --- /dev/null +++ b/marked/Rel-16/48_series/48008/1e8845a639705010d5cda27146b8827f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c81b11978dc3b561819432588f35310b1d9e1c338ab30d34ce9c8e6a5a7eb54d +size 10908 diff --git a/marked/Rel-16/48_series/48008/31f5b6310f831ca3ea4f18453980c070_img.jpg b/marked/Rel-16/48_series/48008/31f5b6310f831ca3ea4f18453980c070_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0d34e1c6fb45d5191b5fe822900107e5a23fbba --- /dev/null +++ b/marked/Rel-16/48_series/48008/31f5b6310f831ca3ea4f18453980c070_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6191c79bec58295b2a4eaeb42cc1077f24d6d1d8eebff57495eda135086bc4c +size 20032 diff --git a/marked/Rel-16/48_series/48008/34fccd22313e0b3b2350c8689f2de9e2_img.jpg b/marked/Rel-16/48_series/48008/34fccd22313e0b3b2350c8689f2de9e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb5df445739222869b9f00feb8dddba1ed8f6937 --- /dev/null +++ b/marked/Rel-16/48_series/48008/34fccd22313e0b3b2350c8689f2de9e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9547e349cec76056a3a31543fbeead44ee0a037b36786179c5cdbe4528cb143c +size 18336 diff --git a/marked/Rel-16/48_series/48008/3e87cc59cb02fbac8840c659c41f2645_img.jpg b/marked/Rel-16/48_series/48008/3e87cc59cb02fbac8840c659c41f2645_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa4b4420d8dc23763892727967277a285db2a4c3 --- /dev/null +++ b/marked/Rel-16/48_series/48008/3e87cc59cb02fbac8840c659c41f2645_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f079c99655f1106476cc4421a5b4abaabc5101785cb2d61dbc51f67ed5e82e67 +size 31243 diff --git a/marked/Rel-16/48_series/48008/52f7a3277fa444ec8818ec7328aa498e_img.jpg b/marked/Rel-16/48_series/48008/52f7a3277fa444ec8818ec7328aa498e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a06fb0efefa1391f90692387da914cd15197a167 --- /dev/null +++ b/marked/Rel-16/48_series/48008/52f7a3277fa444ec8818ec7328aa498e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20fbdd773f6de7fd21176df4ec6fc771a001b7887bf8856e194998babdb88155 +size 14930 diff --git a/marked/Rel-16/48_series/48008/5d819f259411162c4e3371915818ae22_img.jpg b/marked/Rel-16/48_series/48008/5d819f259411162c4e3371915818ae22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef3b537f510d3e421c6363b8cf010a4e7e4bb6a2 --- /dev/null +++ b/marked/Rel-16/48_series/48008/5d819f259411162c4e3371915818ae22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27fb134b1c848b932ea13540aef042bbd79a950ea0553e56b6f8b59a5c2ae8ff +size 107963 diff --git a/marked/Rel-16/48_series/48008/5ed662a589ef8a6d08d67ae2fd275216_img.jpg b/marked/Rel-16/48_series/48008/5ed662a589ef8a6d08d67ae2fd275216_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e8e6d03577df538f355b70bcc70bbbf66eb9aa1 --- /dev/null +++ b/marked/Rel-16/48_series/48008/5ed662a589ef8a6d08d67ae2fd275216_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94b24a0d810c3d00295789537a3f2727f38481838f9d967c41948f6c3e8b3e42 +size 44314 diff --git a/marked/Rel-16/48_series/48008/700f2fb63fbb87c933cd81ca42fb890f_img.jpg b/marked/Rel-16/48_series/48008/700f2fb63fbb87c933cd81ca42fb890f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be2ffe7026e6abf0a57814379eadd7f748a09d8b --- /dev/null +++ b/marked/Rel-16/48_series/48008/700f2fb63fbb87c933cd81ca42fb890f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72a20d789a946a7e3f613c931a327dac60b1196d01e99585e4a4c22fff095242 +size 22361 diff --git a/marked/Rel-16/48_series/48008/7109096552c3464c931b0b39109b9b41_img.jpg b/marked/Rel-16/48_series/48008/7109096552c3464c931b0b39109b9b41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..280d8269111df864765506c204a85b32c24fb8ed --- /dev/null +++ b/marked/Rel-16/48_series/48008/7109096552c3464c931b0b39109b9b41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7888dc4b7806d4d24b87c22e7298a450d12eff44b99276ce1bde7e7a3934783c +size 19314 diff --git a/marked/Rel-16/48_series/48008/728a02fe4a04e7f91835147194997cd4_img.jpg b/marked/Rel-16/48_series/48008/728a02fe4a04e7f91835147194997cd4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f97937422183b7d6ea35e13c011b2880cbeb4568 --- /dev/null +++ b/marked/Rel-16/48_series/48008/728a02fe4a04e7f91835147194997cd4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:744e5c5f453862e24f4ad2a579790a5dfd736871272b7d596fe959c07c504d3f +size 19376 diff --git a/marked/Rel-16/48_series/48008/739d9761cdbb47394f979141864a8de6_img.jpg b/marked/Rel-16/48_series/48008/739d9761cdbb47394f979141864a8de6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c696d09151a0e9c2a48e33552f585b66b3bab9da --- /dev/null +++ b/marked/Rel-16/48_series/48008/739d9761cdbb47394f979141864a8de6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dafaecf94d6629ad2d5b4996ffda4a55d2ff8b086a5531727f3d8ee145493a84 +size 20190 diff --git a/marked/Rel-16/48_series/48008/74b47701fe8a059c632b40e009c57a96_img.jpg b/marked/Rel-16/48_series/48008/74b47701fe8a059c632b40e009c57a96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ec8da84eb2b623e3d1dabe609f3211bba180fc3 --- /dev/null +++ b/marked/Rel-16/48_series/48008/74b47701fe8a059c632b40e009c57a96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da009882f5b909d1c15ba1ba0c30208a051e2396ce7c4c3189cd1421fdeaf12a +size 28988 diff --git a/marked/Rel-16/48_series/48008/8450f105f39b5cb87eddb44d739cb1b2_img.jpg b/marked/Rel-16/48_series/48008/8450f105f39b5cb87eddb44d739cb1b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1bf452cef9f243ecf8152ef72f4a67f65af5ca3 --- /dev/null +++ b/marked/Rel-16/48_series/48008/8450f105f39b5cb87eddb44d739cb1b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12d40a9486c2dd9839ca7836e43cf6328483b4cc14b642afe53553d5090c94c1 +size 20607 diff --git a/marked/Rel-16/48_series/48008/8c05782074bb11421b43f2d5d6799b62_img.jpg b/marked/Rel-16/48_series/48008/8c05782074bb11421b43f2d5d6799b62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05e8372b9f1ca4b203bc76daae80ce00e23dfd79 --- /dev/null +++ b/marked/Rel-16/48_series/48008/8c05782074bb11421b43f2d5d6799b62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71a91d460e578829cc4845c39c57fdef6b42c0c38b9fd2e6110d63313bd703ac +size 22706 diff --git a/marked/Rel-16/48_series/48008/8cbda1d7454ec4dfa612ae7cf5afac7d_img.jpg b/marked/Rel-16/48_series/48008/8cbda1d7454ec4dfa612ae7cf5afac7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa223748f67cc51b77ba39aec75b519cc698280d --- /dev/null +++ b/marked/Rel-16/48_series/48008/8cbda1d7454ec4dfa612ae7cf5afac7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:298895e45e56b559b11f6b207da9b3ef9638070c67951e762b96bcbfe042a212 +size 27259 diff --git a/marked/Rel-16/48_series/48008/8db92c2d49f464fdd3e01aad57bfda53_img.jpg b/marked/Rel-16/48_series/48008/8db92c2d49f464fdd3e01aad57bfda53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da15a94287fbfa92c9aeb5a455a6ac18d85c10d2 --- /dev/null +++ b/marked/Rel-16/48_series/48008/8db92c2d49f464fdd3e01aad57bfda53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40f30c79375a22c693c3484b1a165f09a270d671bb4e50ed5b3719e02fd8f360 +size 18992 diff --git a/marked/Rel-16/48_series/48008/931bd52904f67b17796a38b47af51e30_img.jpg b/marked/Rel-16/48_series/48008/931bd52904f67b17796a38b47af51e30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03cedde74168ff7288117a566d43ce8993a128e0 --- /dev/null +++ b/marked/Rel-16/48_series/48008/931bd52904f67b17796a38b47af51e30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d294d76338813067c4ab020bf5fdccc2eb522aaa278cdca9bd4131ebef0321c8 +size 27289 diff --git a/marked/Rel-16/48_series/48008/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg b/marked/Rel-16/48_series/48008/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bca60b99e66f752883fd294cfa554c8b15d23dd7 --- /dev/null +++ b/marked/Rel-16/48_series/48008/af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3af5493a4df643a9e1a1cbada44720041bab64757d9b3055a9d26e149d878c6b +size 18115 diff --git a/marked/Rel-16/48_series/48008/b0b07599997175149ac03e26e3247c9a_img.jpg b/marked/Rel-16/48_series/48008/b0b07599997175149ac03e26e3247c9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c613025078651d43a6faee1604dbf77bbe4e07c1 --- /dev/null +++ b/marked/Rel-16/48_series/48008/b0b07599997175149ac03e26e3247c9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1feb45e030c5ffa0ae335bb448f6d18969b6c90fa970ea4319f902c70771059f +size 19441 diff --git a/marked/Rel-16/48_series/48008/b61dbe0a8b7ddc6b7fa6550a7ff9d2df_img.jpg b/marked/Rel-16/48_series/48008/b61dbe0a8b7ddc6b7fa6550a7ff9d2df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3362fbf21f2f3c23c91d937feb90cfc338646d1 --- /dev/null +++ b/marked/Rel-16/48_series/48008/b61dbe0a8b7ddc6b7fa6550a7ff9d2df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98ecb6173e3af2ec3f9075aa14a0da1233854c095ccc661adb5a0e87f1a4eb47 +size 31826 diff --git a/marked/Rel-16/48_series/48008/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg b/marked/Rel-16/48_series/48008/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa65969642df3ceec38545ed4dcc69e1912bba9b --- /dev/null +++ b/marked/Rel-16/48_series/48008/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ccdd1c136632cc4d0785ca1cc8e40d533d4dee96ad165105e8479de8f13a4e3 +size 85778 diff --git a/marked/Rel-16/48_series/48008/e002d1b87dc447584fd9829eac949a12_img.jpg b/marked/Rel-16/48_series/48008/e002d1b87dc447584fd9829eac949a12_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e10ef3c63b37a08840e5cfd4b22e7fd69354f9c2 --- /dev/null +++ b/marked/Rel-16/48_series/48008/e002d1b87dc447584fd9829eac949a12_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8511318e9b92f65515319674e4ea88ad7331a834e1a22315f3c54effa79b3a1e +size 45149 diff --git a/marked/Rel-16/48_series/48008/eb5c5bacf91c6062b2d5ba64a50b1a43_img.jpg b/marked/Rel-16/48_series/48008/eb5c5bacf91c6062b2d5ba64a50b1a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f356a4dd1cb1f6ec78875ac0575622bb83fd3ec1 --- /dev/null +++ b/marked/Rel-16/48_series/48008/eb5c5bacf91c6062b2d5ba64a50b1a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0ac3ef15f7362cd47c0c38d15092a529fec103019414bc7540f95c5f507307a +size 20621 diff --git a/marked/Rel-16/48_series/48008/fa849f3297b46a8d257e718ba0720135_img.jpg b/marked/Rel-16/48_series/48008/fa849f3297b46a8d257e718ba0720135_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a068ed35129ab1c37748a2f996173ffc30e8504c --- /dev/null +++ b/marked/Rel-16/48_series/48008/fa849f3297b46a8d257e718ba0720135_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55a3e10de6d3985e6b593ed412d2080fbbaa641c12b1be4183c713beb636dbc1 +size 14791 diff --git a/marked/Rel-16/48_series/48008/raw.md b/marked/Rel-16/48_series/48008/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1aa6a950d28ce5b433621b782032c81893443434 --- /dev/null +++ b/marked/Rel-16/48_series/48008/raw.md @@ -0,0 +1,10538 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword..... | 11 | +| 1 Scope..... | 12 | +| 1.1 References..... | 12 | +| 1.2 Definitions and Abbreviations..... | 14 | +| 2 Application to interface structures..... | 15 | +| 2.1 The BSS Operation and Maintenance Application Part..... | 15 | +| 2.2 The Direct Transfer Application Part..... | 15 | +| 2.3 The BSS Management Application Part..... | 16 | +| 2.4 Handling of abnormal events related to the BSSAP Header..... | 16 | +| 3 The BSS Management Application Part..... | 17 | +| 3.1 BSSMAP Procedures..... | 17 | +| 3.1.1 Assignment..... | 17 | +| 3.1.1.1 Successful Operation..... | 18 | +| 3.1.1.2 Assignment Failure..... | 21 | +| 3.1.1.3 Abnormal Conditions..... | 22 | +| 3.1.2 Blocking and Unblocking..... | 22 | +| 3.1.2.1 Successful Operation..... | 23 | +| 3.1.2.2 Abnormal Conditions..... | 24 | +| 3.1.2.2.1 Applying to the Single Circuit Block Procedure..... | 24 | +| 3.1.2.2.2 Applying to the Circuit Group Block Procedure..... | 24 | +| 3.1.3 Resource Indication..... | 25 | +| 3.1.3.1 Successful Operation..... | 26 | +| 3.1.4 Reset..... | 27 | +| 3.1.4.1 Global Reset Procedure..... | 27 | +| 3.1.4.1.1 Reset at the BSS..... | 27 | +| 3.1.4.1.2 Reset at the MSC..... | 27 | +| 3.1.4.1.3 Abnormal Conditions..... | 28 | +| 3.1.4.1.3.1 Abnormal Condition at the BSS..... | 28 | +| 3.1.4.1.3.2 Abnormal Condition at the MSC..... | 28 | +| 3.1.4.2 Reset Circuit..... | 28 | +| 3.1.4.2.1 Reset Circuit at the BSS..... | 28 | +| 3.1.4.2.2 Reset Circuit at the MSC..... | 28 | +| 3.1.4.2.3 Abnormal conditions..... | 28 | +| 3.1.4.3 Reset IP Resource..... | 29 | +| 3.1.4.3.1 Reset IP Resource procedure initiated by the BSS..... | 29 | +| 3.1.4.3.2 Reset IP Resource procedure initiated by the MSC..... | 29 | +| 3.1.4.3.3 Abnormal conditions..... | 29 | +| 3.1.5 External Handover..... | 30 | +| 3.1.5.1 Handover Required Indication..... | 30 | +| 3.1.5.1.1 Generation of the HANDOVER REQUIRED message..... | 31 | +| 3.1.5.1.2 Abnormal conditions for DTM Handover..... | 33 | +| 3.1.5.2 Handover Resource allocation..... | 34 | +| 3.1.5.2.1 Operation of the procedure..... | 34 | +| 3.1.5.2.2 Handover Resource Allocation Failure..... | 38 | +| 3.1.5.2.3 Abnormal conditions..... | 39 | +| 3.1.5.3 Handover execution..... | 39 | +| 3.1.5.3.1 Operation of the procedure..... | 40 | +| 3.1.5.3.2 Handover Failure..... | 41 | +| 3.1.5.3.3 Abnormal Conditions..... | 42 | +| 3.1.5a Handover from GSM to another System..... | 42 | +| 3.1.5a.1 Generation of the HANDOVER REQUIRED message for intersystem handover..... | 43 | +| 3.1.5a.2 Inter-System Handover Resource Allocation Failure..... | 44 | +| 3.1.5a.3 Intersystem handover Execution..... | 45 | +| 3.1.5a.4 Inter System Handover Failure..... | 46 | +| 3.1.5a.5 Abnormal Conditions..... | 46 | +| 3.1.5b Handover from another system to GSM..... | 46 | +| 3.1.5b.1 General..... | 46 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------|----| +| 3.1.5b.2 | Inter-System Handover Resource Allocation..... | 47 | +| 3.1.5c | BSS Internal Handover with MSC support..... | 47 | +| 3.1.5c.1 | Internal Handover Preparation..... | 47 | +| 3.1.5c.1.1 | Internal Handover Required Reject..... | 48 | +| 3.1.5c.2 | Internal Handover Execution..... | 48 | +| 3.1.5c.2.1 | Internal Handover failure..... | 49 | +| 3.1.5c.2.2 | Abnormal Conditions..... | 49 | +| 3.1.5c.3 | Internal Handover Enquiry..... | 50 | +| 3.1.6 | Internal Intra-Cell Handover Procedure..... | 50 | +| 3.1.7 | Internal Inter-Cell Handover Procedure..... | 51 | +| 3.1.8 | Handover Candidate Enquiry..... | 51 | +| 3.1.8.1 | Successful Operation..... | 52 | +| 3.1.8.2 | Abnormal conditions..... | 52 | +| 3.1.9 | Release of Radio Resource And Terrestrial Resource..... | 52 | +| 3.1.9.1 | Release Due To Transaction Completion..... | 52 | +| 3.1.9.1a | Release of radio resources and the terrestrial resources for VGCS/VBS calls:..... | 53 | +| 3.1.9.2 | Release due to BSS generated reason..... | 53 | +| 3.1.9.3 | Release due to successful handover..... | 55 | +| 3.1.9.4 | Release due to uplink release..... | 55 | +| 3.1.10 | Paging..... | 55 | +| 3.1.11 | Trace Invocation..... | 55 | +| 3.1.12 | Flow Control..... | 56 | +| 3.1.12.1 | Philosophy..... | 56 | +| 3.1.12.2 | Processor Overload at the MSC..... | 56 | +| 3.1.12.3 | Processor/CCCH overload at the BSS..... | 57 | +| 3.1.12.4 | Message throughput congestion..... | 57 | +| 3.1.13 | Classmark Handling Procedures..... | 57 | +| 3.1.13.1 | Classmark request procedure..... | 57 | +| 3.1.13.2 | Classmark updating procedure..... | 57 | +| 3.1.14 | Cipher Mode Control..... | 57 | +| 3.1.14.1 | Successful Operation..... | 57 | +| 3.1.14.2 | Abnormal Conditions..... | 58 | +| 3.1.15 | General SCCP Abnormal Conditions..... | 58 | +| 3.1.16 | Initial MS message..... | 59 | +| 3.1.17 | Queuing Indication..... | 59 | +| 3.1.17.1 | Operation of the procedure in case of assignment procedure..... | 59 | +| 3.1.17.2 | Operation of the procedure in case of hand-over resource allocation procedure..... | 60 | +| 3.1.18 | Data Link Control SAPI not Equal to "0"..... | 60 | +| 3.1.18.1 | Data link set up across the radio interface..... | 60 | +| 3.1.18.1.1 | MS to MSC direction..... | 60 | +| 3.1.18.1.2 | MSC to MS Direction..... | 60 | +| 3.1.18.2 | Choice of the signalling link..... | 60 | +| 3.1.19 | BSSMAP Error Handling..... | 61 | +| 3.1.19.1 | Definitions of Types of Information Elements..... | 61 | +| 3.1.19.2 | Erroneous Events..... | 62 | +| 3.1.19.3 | Non-erroneous Events..... | 62 | +| 3.1.19.4 | Other Events..... | 62 | +| 3.1.19.5 | Appropriate Error Message and Cause Value..... | 63 | +| 3.1.19.6 | Unequipped Circuit Identification Code..... | 63 | +| 3.1.19.7 | Field Elements..... | 64 | +| 3.1.20 | Load Indication Procedure..... | 64 | +| 3.1.20.1 | Operation of the procedure..... | 65 | +| 3.1.21 | Voice group call service and voice broadcast service call set-up and resource assignment..... | 65 | +| 3.1.21.1 | Successful operation..... | 66 | +| 3.1.21.2 | VGCS/VBS call set-up abnormal cases..... | 66 | +| 3.1.21.3 | VGCS/VBS call set-up failure..... | 66 | +| 3.1.22 | Voice group call service and voice broadcast service Assignment procedure..... | 66 | +| 3.1.22.1 | Successful operation..... | 66 | +| 3.1.22.2 | VGCS/VBS Assignment abnormal cases..... | 69 | +| 3.1.22.3 | VGCS/VBS Assignment failure..... | 70 | +| 3.1.22.4 | VGCS/VBS Queuing Indication..... | 71 | + +| | | | +|---------------|-----------------------------------------------------------------------------------------------|----| +| 3.1.23 | (void)..... | 71 | +| 3.1.24 | Voice group call uplink control procedure - talker priority not supported by the network..... | 71 | +| 3.1.24.1 | Uplink allocation procedure..... | 71 | +| 3.1.24.1.1 | Successful uplink allocation operation..... | 72 | +| 3.1.24.1.2 | Unsuccessful uplink allocation operation..... | 72 | +| 3.1.24.2 | Uplink release procedure..... | 72 | +| 3.1.24.3 | Uplink seize procedure..... | 72 | +| 3.1.24a | Voice group call uplink control procedure - talker priority supported by the network..... | 72 | +| 3.1.24.a.1 | General..... | 72 | +| 3.1.24a.2 | Uplink allocation procedure..... | 73 | +| 3.1.24a.2.1 | Successful uplink allocation operation..... | 73 | +| 3.1.24a.2.1.1 | Normal Priority Request..... | 73 | +| 3.1.24a.2.1.2 | Privileged or Emergency Priority Request via Uplink Access procedure..... | 73 | +| 3.1.24a.2.1.3 | Privileged or Emergency Priority Request via Priority Uplink Request procedure..... | 73 | +| 3.1.24a.2.2 | Unsuccessful uplink allocation operation..... | 74 | +| 3.1.24a.2.2.1 | Normal Priority Uplink Request..... | 74 | +| 3.1.24a.2.2.2 | Privileged or Emergency Uplink Request via Uplink Access procedure..... | 74 | +| 3.1.24a.2.2.3 | Privileged or Emergency Uplink Request via Priority Uplink Request procedure..... | 74 | +| 3.1.24a.3 | Uplink release procedure..... | 75 | +| 3.1.24a.4 | Uplink seize procedure..... | 75 | +| 3.1.24a.5 | Emergency Reset procedure via UPLINK ACCESS message..... | 75 | +| 3.1.24a.5.1 | Unsuccessful..... | 75 | +| 3.1.24a.6 | Emergency Reset procedure via PRIORITY UPLINK REQUEST message..... | 75 | +| 3.1.24a.6.1 | Unsuccessful..... | 75 | +| 3.1.24b | Talker Information..... | 75 | +| 3.1.24c | SMS to ongoing VGCS call all..... | 76 | +| 3.1.24d | Distributing application-specific data to ongoing VGCS call..... | 76 | +| 3.1.25 | PDSS1 flow control..... | 76 | +| 3.1.26 | Circuit re-selection procedure..... | 76 | +| 3.1.27 | LSA handling..... | 77 | +| 3.1.28 | Location Acquisition..... | 77 | +| 3.1.28.1 | (void)..... | 77 | +| 3.1.28.2 | Location request..... | 77 | +| 3.1.28.2.1 | Successful Operation..... | 77 | +| 3.1.28.2.2 | Unsuccessful Operation..... | 78 | +| 3.1.28.2.3 | Abnormal cases..... | 78 | +| 3.1.28.2.4 | Overload..... | 79 | +| 3.1.29 | Connectionless Information Transfer procedure..... | 79 | +| 3.1.29.1 | Unsuccessful Operation..... | 79 | +| 3.1.29.2 | Abnormal cases..... | 79 | +| 3.1.29.3 | Segmentation..... | 79 | +| 3.1.30 | Common ID..... | 80 | +| 3.1.31 | VGCS/VBS Cell Re-established - no A-interface link sharing..... | 80 | +| 3.1.32 | Rerouting procedure in case of MOCN configuration for network sharing..... | 80 | +| 3.1.32.1 | General..... | 80 | +| 3.1.32.2 | Reroute command..... | 81 | +| 3.1.32.3 | Reroute complete..... | 82 | +| 3.1.32.4 | Abnormal Conditions..... | 82 | +| 3.1.32a | Rerouting procedure in case of GWCN configuration for network sharing..... | 82 | +| 3.1.32a.1 | General..... | 82 | +| 3.1.32a.2 | Reroute command..... | 83 | +| 3.1.32a.3 | Reroute complete..... | 84 | +| 3.1.32a.4 | Abnormal Conditions..... | 84 | +| 3.1.33 | Local Call Local Switch..... | 84 | +| 3.1.33.1 | General..... | 84 | +| 3.1.33.2 | Local switch establishment..... | 84 | +| 3.1.33.2.1 | Call Leg Correlation..... | 84 | +| 3.1.33.2.2 | Successful Operation..... | 85 | +| 3.1.33.2.3 | Unsuccessful Operation..... | 85 | +| 3.1.33.3 | Local switch break..... | 86 | +| 3.1.33.3.1 | Local switching break request from MSC..... | 86 | + +| | | | +|------------|---------------------------------------------|-----| +| 3.1.33.3.2 | Local switching break initiated by BSS..... | 86 | +| 3.1.33.3.3 | Local Switching break at Handover..... | 86 | +| 3.1.33.4 | Local switch prevention..... | 87 | +| 3.1.33.5 | LCLS Notification..... | 87 | +| 3.1.34 | MS Registration Enquiry..... | 87 | +| 3.1.34.1 | General..... | 87 | +| 3.1.34.2 | Registration enquiry..... | 87 | +| 3.1.34.3 | Registration response..... | 87 | +| 3.2 | Message Formats and Coding..... | 88 | +| 3.2.1 | Message Contents..... | 91 | +| 3.2.1.1 | ASSIGNMENT REQUEST..... | 91 | +| 3.2.1.2 | ASSIGNMENT COMPLETE..... | 92 | +| 3.2.1.3 | ASSIGNMENT FAILURE..... | 94 | +| 3.2.1.4 | BLOCK..... | 95 | +| 3.2.1.5 | BLOCKING ACKNOWLEDGE..... | 95 | +| 3.2.1.6 | UNBLOCK..... | 95 | +| 3.2.1.7 | UNBLOCKING ACKNOWLEDGE..... | 95 | +| 3.2.1.8 | HANDOVER REQUEST..... | 96 | +| 3.2.1.9 | HANDOVER REQUIRED..... | 99 | +| 3.2.1.10 | HANDOVER REQUEST ACKNOWLEDGE..... | 101 | +| 3.2.1.11 | HANDOVER COMMAND..... | 102 | +| 3.2.1.12 | HANDOVER COMPLETE..... | 102 | +| 3.2.1.13 | HANDOVER SUCCEEDED..... | 103 | +| 3.2.1.14 | HANDOVER CANDIDATE ENQUIRE..... | 103 | +| 3.2.1.15 | HANDOVER CANDIDATE RESPONSE..... | 103 | +| 3.2.1.16 | HANDOVER FAILURE..... | 103 | +| 3.2.1.17 | RESOURCE REQUEST..... | 105 | +| 3.2.1.18 | RESOURCE INDICATION..... | 105 | +| 3.2.1.19 | PAGING..... | 106 | +| 3.2.1.20 | CLEAR REQUEST..... | 106 | +| 3.2.1.21 | CLEAR COMMAND..... | 107 | +| 3.2.1.22 | CLEAR COMPLETE..... | 107 | +| 3.2.1.23 | RESET..... | 107 | +| 3.2.1.24 | RESET ACKNOWLEDGE..... | 108 | +| 3.2.1.25 | HANDOVER PERFORMED..... | 109 | +| 3.2.1.26 | OVERLOAD..... | 110 | +| 3.2.1.27 | MSC INVOKE TRACE..... | 110 | +| 3.2.1.28 | BSS INVOKE TRACE..... | 110 | +| 3.2.1.29 | CLASSMARK UPDATE..... | 111 | +| 3.2.1.30 | CIPHER MODE COMMAND..... | 111 | +| 3.2.1.31 | CIPHER MODE COMPLETE..... | 111 | +| 3.2.1.32 | COMPLETE LAYER 3 INFORMATION..... | 112 | +| 3.2.1.33 | QUEUEING INDICATION..... | 112 | +| 3.2.1.34 | SAPI "n" REJECT..... | 113 | +| 3.2.1.35 | (void)..... | 113 | +| 3.2.1.36 | (void)..... | 113 | +| 3.2.1.37 | HANDOVER REQUIRED REJECT..... | 113 | +| 3.2.1.38 | RESET CIRCUIT..... | 114 | +| 3.2.1.39 | RESET CIRCUIT ACKNOWLEDGE..... | 114 | +| 3.2.1.40 | HANDOVER DETECT..... | 114 | +| 3.2.1.41 | CIRCUIT GROUP BLOCK..... | 114 | +| 3.2.1.42 | CIRCUIT GROUP BLOCKING ACKNOWLEDGE..... | 115 | +| 3.2.1.43 | CIRCUIT GROUP UNBLOCK..... | 115 | +| 3.2.1.44 | CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE..... | 115 | +| 3.2.1.45 | CONFUSION..... | 115 | +| 3.2.1.46 | CLASSMARK REQUEST..... | 116 | +| 3.2.1.47 | UNEQUIPPED CIRCUIT..... | 116 | +| 3.2.1.48 | CIPHER MODE REJECT..... | 116 | +| 3.2.1.49 | LOAD INDICATION..... | 117 | +| 3.2.1.50 | VGCS/VBS SETUP..... | 117 | +| 3.2.1.51 | VGCS/VBS SETUP ACK..... | 117 | + +| | | | +|-----------|----------------------------------------|-----| +| 3.2.1.52 | VGCS/VBS SETUP REFUSE..... | 118 | +| 3.2.1.53 | VGCS/VBS ASSIGNMENT REQUEST..... | 118 | +| 3.2.1.54 | VGCS/VBS ASSIGNMENT RESULT..... | 119 | +| 3.2.1.55 | VGCS/VBS ASSIGNMENT FAILURE..... | 119 | +| 3.2.1.56 | VGCS/VBS QUEUING INDICATION..... | 120 | +| 3.2.1.57 | UPLINK REQUEST..... | 120 | +| 3.2.1.58 | UPLINK REQUEST ACKNOWLEDGE..... | 121 | +| 3.2.1.59 | UPLINK REQUEST CONFIRMATION..... | 121 | +| 3.2.1.59a | UPLINK APPLICATION DATA..... | 121 | +| 3.2.1.60 | UPLINK RELEASE INDICATION..... | 121 | +| 3.2.1.61 | UPLINK REJECT COMMAND..... | 122 | +| 3.2.1.62 | UPLINK RELEASE COMMAND..... | 122 | +| 3.2.1.63 | UPLINK SEIZED COMMAND..... | 122 | +| 3.2.1.64 | SUSPEND..... | 122 | +| 3.2.1.65 | RESUME..... | 123 | +| 3.2.1.66 | CHANGE CIRCUIT..... | 123 | +| 3.2.1.67 | CHANGE CIRCUIT ACKNOWLEDGE..... | 123 | +| 3.2.1.68 | Common ID..... | 123 | +| 3.2.1.69 | LSA INFORMATION..... | 124 | +| 3.2.1.70 | (void)..... | 124 | +| 3.2.1.71 | PERFORM LOCATION REQUEST..... | 124 | +| 3.2.1.72 | PERFORM LOCATION RESPONSE..... | 125 | +| 3.2.1.73 | PERFORM LOCATION ABORT..... | 125 | +| 3.2.1.74 | CONNECTIONLESS INFORMATION..... | 125 | +| 3.2.1.75 | CHANNEL MODIFY REQUEST..... | 126 | +| 3.2.1.76 | EMERGENCY RESET INDICATION..... | 126 | +| 3.2.1.77 | EMERGENCY RESET COMMAND..... | 126 | +| 3.2.1.78 | VGCS ADDITIONAL INFORMATION..... | 126 | +| 3.2.1.79 | VGCS/VBS AREA CELL INFO..... | 127 | +| 3.2.1.80 | VGCS/VBS ASSIGNMENT STATUS..... | 127 | +| 3.2.1.81 | VGCS SMS..... | 128 | +| 3.2.1.82 | NOTIFICATION DATA..... | 128 | +| 3.2.1.83 | INTERNAL HANDOVER REQUIRED..... | 128 | +| 3.2.1.84 | INTERNAL HANDOVER REQUIRED REJECT..... | 129 | +| 3.2.1.85 | INTERNAL HANDOVER COMMAND..... | 129 | +| 3.2.1.86 | INTERNAL HANDOVER ENQUIRY..... | 130 | +| 3.2.1.87 | RESET IP RESOURCE..... | 130 | +| 3.2.1.88 | RESET IP RESOURCE ACKNOWLEDGE..... | 131 | +| 3.2.1.89 | REROUTE COMMAND..... | 131 | +| 3.2.1.90 | REROUTE COMPLETE..... | 131 | +| 3.2.1.91 | LCLS-CONNECT-CONTROL..... | 131 | +| 3.2.1.92 | LCLS-CONNECT-CONTROL-ACK..... | 132 | +| 3.2.1.93 | LCLS-NOTIFICATION..... | 132 | +| 3.2.1.94 | MS REGISTRATION ENQUIRY..... | 132 | +| 3.2.1.95 | MS REGISTRATION ENQUIRY RESPONSE..... | 132 | +| 3.2.2 | Signalling element coding..... | 132 | +| 3.2.2.0 | General..... | 132 | +| 3.2.2.1 | Message Type..... | 137 | +| 3.2.2.2 | Circuit Identity Code..... | 138 | +| 3.2.2.3 | Connection Release Requested..... | 139 | +| 3.2.2.4 | Resource Available..... | 139 | +| 3.2.2.5 | Cause..... | 140 | +| 3.2.2.6 | IMSI..... | 142 | +| 3.2.2.7 | TMSI..... | 143 | +| 3.2.2.8 | Number Of MSs..... | 143 | +| 3.2.2.9 | Layer 3 Header Information..... | 143 | +| 3.2.2.10 | Encryption Information..... | 144 | +| 3.2.2.11 | Channel Type..... | 144 | +| 3.2.2.12 | Periodicity..... | 150 | +| 3.2.2.13 | Extended Resource Indicator..... | 151 | +| 3.2.2.14 | Total Resource Accessible..... | 151 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------|-----| +| 3.2.2.15 | LSA Identifier..... | 152 | +| 3.2.2.16 | LSA Identifier List..... | 152 | +| 3.2.2.17 | Cell Identifier..... | 153 | +| 3.2.2.18 | Priority..... | 156 | +| 3.2.2.19 | Classmark Information Type 2..... | 156 | +| 3.2.2.20 | Classmark Information Type 3..... | 157 | +| 3.2.2.21 | Interference Band To Be Used..... | 157 | +| 3.2.2.22 | RR Cause..... | 157 | +| 3.2.2.23 | LSA Information..... | 158 | +| 3.2.2.24 | Layer 3 Information..... | 158 | +| 3.2.2.25 | DLCI..... | 159 | +| 3.2.2.26 | Downlink DTX Flag..... | 159 | +| 3.2.2.27 | Cell Identifier List..... | 159 | +| 3.2.2.27a | Cell Identifier List Segment..... | 162 | +| 3.2.2.27b | Cell Identifier List Segment for established cells..... | 165 | +| 3.2.2.27c | Cell Identifier List Segment for cells to be established..... | 168 | +| 3.2.2.27d | (void)..... | 169 | +| 3.2.2.27e | Cell Identifier List Segment for released cells - no user present..... | 169 | +| 3.2.2.27f | Cell Identifier List Segment for not established cells - no establishment possible..... | 169 | +| 3.2.2.28 | Response Request..... | 169 | +| 3.2.2.29 | Resource Indication Method..... | 170 | +| 3.2.2.30 | Classmark Information Type 1..... | 170 | +| 3.2.2.31 | Circuit Identity Code List..... | 170 | +| 3.2.2.32 | Diagnostics..... | 171 | +| 3.2.2.33 | Chosen Channel..... | 172 | +| 3.2.2.34 | Cipher Response Mode..... | 173 | +| 3.2.2.35 | Layer 3 Message Contents..... | 173 | +| 3.2.2.36 | Channel Needed..... | 174 | +| 3.2.2.37 | Trace Type..... | 174 | +| 3.2.2.38 | TriggerID..... | 174 | +| 3.2.2.39 | Trace Reference..... | 174 | +| 3.2.2.40 | TransactionID..... | 174 | +| 3.2.2.41 | Mobile Identity..... | 175 | +| 3.2.2.42 | OMCID..... | 175 | +| 3.2.2.43 | Forward Indicator..... | 175 | +| 3.2.2.44 | Chosen Encryption Algorithm..... | 175 | +| 3.2.2.45 | Circuit Pool..... | 176 | +| 3.2.2.46 | Circuit Pool List..... | 181 | +| 3.2.2.47 | Time Indication..... | 181 | +| 3.2.2.48 | Resource Situation..... | 181 | +| 3.2.2.49 | Current Channel Type 1..... | 183 | +| 3.2.2.50 | Queuing Indicator..... | 184 | +| 3.2.2.51 | Speech Version..... | 184 | +| 3.2.2.52 | Assignment Requirement..... | 184 | +| 3.2.2.53 | (void)..... | 185 | +| 3.2.2.54 | Talker Flag..... | 185 | +| 3.2.2.55 | Group Call Reference..... | 185 | +| 3.2.2.56 | eMLPP Priority..... | 185 | +| 3.2.2.57 | Configuration Evolution Indication..... | 185 | +| 3.2.2.58 | Old BSS to New BSS information..... | 186 | +| 3.2.2.59 | (void)..... | 187 | +| 3.2.2.60 | LCS QoS..... | 187 | +| 3.2.2.61 | LSA Access Control Suppression..... | 187 | +| 3.2.2.62 | LCS Priority..... | 187 | +| 3.2.2.63 | Location Type..... | 187 | +| 3.2.2.64 | Location Estimate..... | 188 | +| 3.2.2.65 | Positioning Data..... | 188 | +| 3.2.2.66 | LCS Cause..... | 188 | +| 3.2.2.67 | LCS Client Type..... | 188 | +| 3.2.2.68 | APDU..... | 189 | +| 3.2.2.69 | Network Element Identity..... | 189 | + +| | | | +|-----------|------------------------------------------------------------------|-----| +| 3.2.2.70 | GPS Assistance Data..... | 190 | +| 3.2.2.71 | Deciphering Keys..... | 190 | +| 3.2.2.72 | Return Error Request..... | 190 | +| 3.2.2.73 | Return Error Cause..... | 190 | +| 3.2.2.74 | Segmentation..... | 191 | +| 3.2.2.75 | Service Handover..... | 191 | +| 3.2.2.76 | Source RNC to target RNC transparent information (UMTS)..... | 192 | +| 3.2.2.77 | Source RNC to target RNC transparent information (cdma2000)..... | 192 | +| 3.2.2.78 | GERAN Classmark..... | 192 | +| 3.2.2.79 | GERAN BSC Container..... | 193 | +| 3.2.2.80 | New BSS to Old BSS Information..... | 194 | +| 3.2.2.81 | Inter-System Information..... | 195 | +| 3.2.2.82 | SNA Access Information..... | 195 | +| 3.2.2.83 | VSTK_RAND Information..... | 196 | +| 3.2.2.84 | VSTK information..... | 196 | +| 3.2.2.85 | Paging Information..... | 196 | +| 3.2.2.86 | IMEI..... | 197 | +| 3.2.2.87 | Velocity Estimate..... | 197 | +| 3.2.2.88 | VGCS Feature Flags..... | 197 | +| 3.2.2.89 | Talker Priority..... | 198 | +| 3.2.2.90 | Emergency Set Indication..... | 199 | +| 3.2.2.91 | Talker Identity..... | 199 | +| 3.2.2.92 | SMS to VGCS..... | 199 | +| 3.2.2.93 | VGCS talker mode..... | 199 | +| 3.2.2.94 | VGCS/VBS Cell Status..... | 200 | +| 3.2.2.95 | GANSS Assistance Data..... | 200 | +| 3.2.2.96 | GANSS Positioning Data..... | 201 | +| 3.2.2.97 | GANSS Location Type..... | 201 | +| 3.2.2.98 | Application Data..... | 201 | +| 3.2.2.99 | Data Identity..... | 201 | +| 3.2.2.100 | Application Data Information..... | 202 | +| 3.2.2.101 | MSISDN..... | 202 | +| 3.2.2.102 | AoIP Transport Layer Address..... | 202 | +| 3.2.2.103 | Speech Codec List..... | 203 | +| 3.2.2.104 | Speech Codec..... | 206 | +| 3.2.2.105 | Call Identifier..... | 207 | +| 3.2.2.106 | Call Identifier List..... | 208 | +| 3.2.2.107 | A-Interface Selector for RESET..... | 208 | +| 3.2.2.108 | (void)..... | 208 | +| 3.2.2.109 | KC 128 ..... | 208 | +| 3.2.2.110 | CSG Identifier..... | 208 | +| 3.2.2.111 | Redirect Attempt Flag..... | 209 | +| 3.2.2.112 | Reroute Reject Cause..... | 209 | +| 3.2.2.113 | Send Sequence Number..... | 210 | +| 3.2.2.114 | Reroute complete outcome..... | 210 | +| 3.2.2.115 | Global Call Reference..... | 210 | +| 3.2.2.116 | LCLS-Configuration..... | 211 | +| 3.2.2.117 | LCLS-Connection-Status-Control..... | 211 | +| 3.2.2.118 | LCLS-Correlation-Not-Needed..... | 212 | +| 3.2.2.119 | LCLS-BSS-Status..... | 212 | +| 3.2.2.120 | LCLS-Break-Request..... | 212 | +| 3.2.2.121 | CSFB Indication..... | 212 | +| 3.2.2.122 | CS to PS SRVCC..... | 212 | +| 3.2.2.123 | Source eNB to target eNB transparent information (E-UTRAN)..... | 213 | +| 3.2.2.124 | CS to PS SRVCC Indication..... | 213 | +| 3.2.2.125 | CN to MS transparent information..... | 213 | +| 3.2.2.126 | Selected PLMN ID..... | 213 | +| 3.2.2.127 | Last used E-UTRAN PLMN ID..... | 213 | +| 3.2.2.128 | Old Location Area Identification..... | 214 | +| 3.2.2.129 | Attach Indicator..... | 214 | +| 3.2.2.130 | Selected Operator..... | 214 | + +| | | | +|------------------------|---------------------------------------------------------|-----| +| 3.2.2.131 | PS Registered Operator..... | 214 | +| 3.2.2.132 | CS Registered Operator..... | 215 | +| 3.2.2.133 | Temporary logical link Identity (TLLI)..... | 215 | +| 3.2.2.134 | Multilateration Timing Advance..... | 215 | +| 3.2.2.135 | MS Synchronization Accuracy..... | 215 | +| 3.2.2.136 | BTS Reception Accuracy Level..... | 216 | +| 3.2.2.137 | Random ID..... | 216 | +| 3.2.3 | Signalling Field Element Coding..... | 216 | +| 3.2.3.1 | Extra information..... | 217 | +| 3.2.3.2 | Current Channel type 2..... | 218 | +| 3.2.3.3 | Target cell radio information..... | 218 | +| 3.2.3.4 | GPRS Suspend Information..... | 219 | +| 3.2.3.5 | MultiRate configuration Information..... | 219 | +| 3.2.3.6 | Dual Transfer Mode information..... | 219 | +| 3.2.3.7 | Inter RAT Handover Info..... | 220 | +| 3.2.3.8 | cdma2000 Capability Information..... | 220 | +| 3.2.3.9 | Downlink Cell Load Information..... | 220 | +| 3.2.3.10 | Uplink Cell Load Information..... | 221 | +| 3.2.3.11 | Cell Load Information Group..... | 221 | +| 3.2.3.12 | Cell Load Information..... | 221 | +| 3.2.3.13 | PS Indication..... | 222 | +| 3.2.3.14 | DTM Handover Command Indication..... | 222 | +| 3.2.3.15 | D-RNTI..... | 222 | +| 3.2.3.16 | IRAT Measurement Configuration..... | 223 | +| 3.2.3.17 | Source Cell ID..... | 223 | +| 3.2.3.18 | IRAT Measurement Configuration (extended E-ARFCNs)..... | 224 | +| 3.2.4 | List of Timers in the BSSMAP Procedures..... | 225 | +| 3.3 | SDL Representation Of The Procedures At The BSS..... | 225 | +| 4 | Broadcast Information Control Channel..... | 225 | +| 5 | Definitions..... | 225 | +| 6 | List of diagrams..... | 227 | +| Annex A (informative): | Change History..... | 238 | + +--- + +## 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 layer 3 procedures used on the Base Station System (BSS) to Mobile-services Switching Centre (MSC) interface for control of GSM services. + +For the purposes of call control and mobility management, messages are not interpreted at the Base Station System (BSS) which acts as a relay function. These messages and procedures are documented in 3GPP TS 24.008, the only relevant issues covering these messages in the present document are those concerned with error conditions at the interface, and the headers that are required for the correct addressing of the messages. This is specified in more detail in 3GPP TS 48.002. + +The functional split between MSC and BSS is defined in 3GPP TS 48.002 and states that the BSS is responsible for local radio resource allocation and in order to support this the required procedures between BSS and MSC are defined in detail in the present document. + +3GPP TS 48.002 also states that the BSS is responsible for the scheduling of all CCCH/BCCH messages and therefore some procedures for providing the BSS with the necessary information to be passed on these channels for individual calls (i.e. paging) are defined in the present document, but the scheduling is not discussed. + +This interface and consequently these layer 3 procedures are designed to support BSSs providing one or more cells. + +## 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.003: "Numbering, addressing and identification". +- [3] 3GPP TS 23.009: "Handover procedures". +- [3a] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [4] (void) +- [5] 3GPP TS 43.059: "Functional stage 2 description of Location Services (LCS) in GERAN". +- [6] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [7] (void). +- [8] (void). +- [9] (void). +- [10] (void). +- [11] (void). +- [12] (void). +- [13] (void). +- [14] (void). + +- [15] (void). +- [16] 3GPP TS 48.002: "Base Station System - Mobile-services Switching Centre (BSS-MSC) interface; Interface principles". +- [17] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS-MSC) interface". +- [18] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS-MSC) interface". +- [18a] (void). +- [19] 3GPP TS 48.071: "Location Services (LCS); Serving Mobile Location Center - Base Station System (SMLC-BSS) interface; Layer 3 specification". +- [19a] 3GPP TS 49.031: "Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". +- [20] (void). +- [21] (void). +- [22] (void). +- [23] (void). +- [24] (void). +- [25] (void). +- [26] (void). +- [27] (void). +- [28] 3GPP TS 52.021: "Network Management (NM) procedures and messages on the A-bis Interface". +- [29] (void). +- [30] (void). +- [31] 3GPP TS 25.413: "UTRAN Iu Interface RANAP signalling". +- [32] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [33] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [34] (void). +- [35] (void). +- [36] (void). +- [37] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [38] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". +- [39] 3GPP TS 43.020: "Security-related network functions". +- [40] 3GPP TS 43.073: "Support of Localised Service Area (SoLSA); Stage 2". +- [41] 3GPP TS 52.008: "Telecommunication management; GSM subscriber and equipment trace". +- [42] (void). +- [43] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". + +- [44] 3GPP TS 26.103: "Speech codec list for GSM and UMTS". +- [45] 3GPP TS 43.051: "GSM/EDGE Radio Access Network (GERAN) overall description; Stage 2". +- [46] 3GPP TS 23.172: " Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2". +- [47] 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2". +- [48] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [49] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [50] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs". +- [51] 3GPP TS 23.153: "Out of band transcoder control; Stage 2". +- [52] 3GPP TS 23.251: "Network sharing - Architecture and functional description". +- [53] 3GPP TS 29.280: "3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC". +- [54] 3GPP TS 23.284: "Local Call Local Switch; Stage 2". +- [55] 3GPP TS 29.205: "Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3". +- [56] 3GPP TS 43.130: "Iur-g interface; Stage 2". +- [57] 3GPP TS 36.413: "S1 Application Protocol (S1AP)". +- [58] 3GPP TS 45.008: "Radio subsystem link control". +- [59] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [60] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification" +- [61] 3GPP TS 24.237: "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) Service Continuity; Stage 3" +- [62] 3GPP TS 33.102: "3G Security; Security architecture". +- [63] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)". +- [64] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3" + +## 1.2 Definitions and Abbreviations + +For the purposes of the present document, the definitions and abbreviations given in 3GPP TR 21.905 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. + +- **CS/PS coordination enhancements:** refers to an improved CS/PS domain registration coordination function when rerouting is performed in a MOCN or in a GWCN configuration for network sharing. The improved CS/PS domain registration coordination is achieved by extended signalling between the BSS and the CN nodes (see 3GPP TS 23.251 [52]). +- **Network sharing:** network sharing is an optional feature that allows different core network operators to connect to the same shared radio access network in a MOCN configuration, and to the same shared radio access network and core network nodes in a GWCN configuration (see 3GPP TS 23.251 [52]). When network sharing is in use within a given cell, the network broadcasts within system information the PLMN identities of the PLMNs sharing the cell. A mobile station supporting network sharing uses this information for its PLMN (re)selection processes and indicates the selected PLMN to the BSS. + +| | | +|----------------|----------------------------------------------------------------------------------------------| +| AoIP | A over IP, using IP as the bearer of the user plane of A interface. | +| AoTDM | A over TDM, using TDM as the bearer of the user plane of A interface. | +| CSFB | Circuit Switched Fallback | +| CSG | Closed Subscriber Group | +| CSG Cell | A cell for which the reported access mode indicates "Closed access mode" as defined in [50]. | +| EPS | Evolved Packet System | +| E-UTRAN | Evolved UTRAN | +| eNB | E-UTRAN NodeB | +| GCR | Global Call Reference | +| HSPA | High Speed Packet Access | +| GWCN | GateWay Core Network as defined in 3GPP TS 23.251 [52] | +| Intra-BSS call | A mobile to mobile voice call involving two mobile stations connected to the same BSS. | +| LCLS | Local Call Local Switch | +| Local call | An Intra-BSS call that can be locally switched by the BSS. | +| Hybrid Cell | A cell for which the reported access mode indicates "Hybrid access Mode" as defined in [50]. | +| MOCN | Multi Operator Core Network as defined in 3GPP TS 23.251 [52]. | +| SRVCC | Single Radio Voice Call Continuity. | +| UTRAN | Universal Terrestrial Radio Access Network | + +## 2 Application to interface structures + +The underlying transport mechanism defined to carry signalling information between the BSS and the MSC is the Message Transfer Part (MTP), and the Signalling Connection Control Part (SCCP) of Signalling System No.7. + +The MTP and SCCP are used to support communication between the MSC and two conceptual entities within the BSS, these are: + +- the BSS Operation and Maintenance Application Part (BSSOMAP); +- the BSS Application Part (BSSAP). + +The BSS Application Part is split into two sub application parts, these are: + +- the BSS Management Application Part (BSSMAP); +- the Direct Transfer Application Part (DTAP). + +Distribution of messages between the two sub application parts is described in 3GPP TS 48.002. + +Figure 1 is a diagrammatical representation of these conceptual entities. It should be noted that this is not intended to imply a particular implementation and is only for the purposes of specifying the interface. + +Differentiation between BSSAP and BSSOMAP is by addressing mechanisms within the SCCP, using the subsystem number (see 3GPP TS 48.002). + +### 2.1 The BSS Operation and Maintenance Application Part + +If operation and maintenance messages are transferred by means of this interface then they shall use SCCP messages. The application protocol for the Operation and Maintenance Application Part is defined in the 3GPP TS 52 series Technical Specifications. The routing and addressing is provided by the SCCP and allows the MSC and the O&M centre to be addressed directly by the BSS using, for example, two E.164 numbers. The operator may also use an X.25 connection for the transfer of O&M messages between the BSS and the OMC. This option is not further discussed in the present document. + +### 2.2 The Direct Transfer Application Part + +The Direct Transfer Application Part (DTAP) is used to transfer call control and mobility management messages between the MSC and the MS. The DTAP information in these messages is not interpreted by the BSS. 3GPP TS 48.002 contains more detail relating to the handling of DTAP messages at the BSS, the multiplexing of the messages onto the relevant signalling channels of the radio interface, and the use of the SCCP services. + +Messages received from the MS are identified as DTAP by the Protocol Discriminator Information Element as described in 3GPP TS 24.008, except for Initial Layer 3 messages (see sub-clause 3.1.16). The majority of radio interface messages are transferred across the BSS MSC interface by the DTAP, the exceptions being messages belonging to the Radio Resource (RR) management protocol. + +## 2.3 The BSS Management Application Part + +The BSSMAP supports all of the procedures between the MSC and the BSS that require interpretation and processing of information related to single calls, and resource management. + +Some of the BSSMAP procedures result in, or are triggered by, Radio Resource (RR) management messages defined in 3GPP TS 24.008. The BSSMAP procedures are described in sub-clause 3. + +## 2.4 Handling of abnormal events related to the BSSAP Header + +The BSSAP header is specified in 3GPP TS 48.002. Several abnormal events may be detected by the receiver: + +- use of a reserved value in the DLCI or discriminator; +- length octet with value zero; +- length octet with a value inconsistent with that indicated by the SCCP. + +In these cases the receiver may send a BSSMAP CONFUSION message as specified in sub-clause 3.2.1. If so, depending on the error in the BSSAP header, the error pointer shall be set to one of the values reserved for the BSSAP header in sub-clause 3.2.2.32. + +Spare bits in the BSSAP header shall not be checked by the receiving entity. + +# 3 The BSS Management Application Part + +## 3.1 BSSMAP Procedures + +This sub-clause describes the procedures used in the BSS Management Application Part. There are the following main procedures: + +| | | | +|---|-------------------------------------|-------------------| +| * | Assignment | figure 2 | +| # | Blocking | figures 10 and 25 | +| # | Resource indication | figure 12 | +| # | Reset | figure 11 | +| * | Handover required indication | figure 4 | +| * | Handover resource allocation | figure 5 | +| * | Handover execution | figure 3 | +| # | Handover candidate enquiry | figure 13 | +| * | Release | figures 6 and 7 | +| # | Paging | figure 15 | +| # | Flow control | figure 14 | +| * | Classmark update | figure 9 | +| * | Cipher mode control | figure 17 | +| * | Trace invocation | | +| * | Initial MS message | | +| * | Queuing indication | | +| * | Data link control SAPI not | | +| | equal to 0 | figure 18 | +| # | Reset circuit | | +| * | PDSS1 flow control | | +| * | Circuit re-selection | figure 26 | +| * | Location Acquisition | | +| # | Connectionless Information Transfer | | +| * | Common ID | | +| # | Reset IP Resource | | + +These procedures are documented separately and are intended to be used by the operators/manufacturers to build up complete call sequences, in a flexible manner. Any sequences given where more than one procedure is shown concatenated are only for illustrative purposes. + +Each of the above procedures is qualified by either an asterisk (\*) or a hash symbol (#). The hash symbol (#) denotes a global procedure which concerns a complete cell or BSS, or specific terrestrial circuits. The asterisk symbol (\*) denotes a dedicated procedure which concerns a single dedicated radio resource on the radio interface, or in the case of a multislot configuration, all radio resources allocated to one mobile station. + +Messages used to support global procedures are sent using the connectionless services of the SCCP. + +Messages used to support dedicated procedures are sent using the connection oriented services of the SCCP, on the connection which has been set up to support that call or transaction. The establishment of SCCP connections is detailed in 3GPP TS 48.002. + +In the following description of each procedure it is explicitly stated whether the procedure is global or not, and hence the type of SCCP service used to support the procedure is defined. + +The handling of unknown terrestrial circuits is defined in sub-clause 3.1.19.6 and the procedures of sub-clause 3.1.19.6 take precedence over those of the rest of sub-clause 3.1. The procedures of the rest of sub-clause 3.1 assume that the terrestrial circuit is known by the entity concerned. + +### 3.1.1 Assignment + +The purpose of the assignment procedure is to ensure that the correct dedicated radio resource(s) can be allocated or reallocated to a MS that requires it. However, the initial random access by the MS and "Immediate Assignment" to a DCCH is handled autonomously by the BSS without reference to the MSC. + +#### 3.1.1.1 Successful Operation + +The initial conditions are assumed to be that the MS is in contact with the fixed infrastructure of a PLMN by means of one or more dedicated radio resources (and possibly a terrestrial resource) and that the MSC has analysed any relevant call control information and wishes to allocate or reallocate to the MS one or more radio resources (and possibly a terrestrial resource). + +The MSC is the entity that carries out the necessary analysis on the call control information received from the MS or fixed network customer. If an IP based user plane interface is supported, the Codec List (BSS supported) shall be taken into account, considering the Codec capabilities of the core network, aiming for true end-to-end Codec negotiation and for common supported Codec(s). + +If an IP based user plane interface is supported, then the MSC shall consider the CSData Codec Type within the Codec List (BSS supported) for data and fax calls. The purpose of the CSData Codec Type negotiation is to determine the A-Interface Type (TDM or IP) and the Redundancy Level (option only for IP). The Redundancy Level affects only the A-Interface IP link and not the air interface. For data and fax call, there is no end-to-end negotiation of this CSData Codec Type. The Codec negotiation just happens between the BSS and the MSC. + +On the basis of this analysis a resource request is made to the appropriate BSS by sending it an ASSIGNMENT REQUEST message. This message contains details of the resource(s) required (for instance channel rate, channel type, data adaptation, priority level etc.). If the requested resource(s) is/are for speech or data it also may indicate the terrestrial resource that shall be used between the MSC and BSS. The description of the resource(s) can either be a complete specification, or give the BSS some freedom in the selection (for instance channel rate selection, speech version, Codec Type and Codec Configuration selection, Interface Type selection, Redundancy Level selection, etc.). If an IP based user plane interface is supported, the Codec List (MSC Preferred), see subclause 3.2.2.103, shall be included in the ASSIGNMENT REQUEST message. The ASSIGNMENT REQUEST message may also contain CLASSMARK information in case such information is available in the MSC, but assumed not to be available in the BSS. A full description of the message is given in sub-clause 3.2.1.1. + +In this specification a "pool" is a group of circuits supporting the same channel types. + +The ASSIGNMENT REQUEST message is sent via the BSSMAP and is analysed within the BSS. Based on this analysis, which is not defined further in the present document, the BSS chooses the appropriate radio resource(s) and allocates the appropriate resources for transcoding, rate adaptation etc. On the terrestrial route connecting the BSS and MSC, certain circuits can be used for different combinations of bearer capabilities. This can be modelled by grouping the circuits into "pools" supporting the same channel types. The MSC holds this information as route data. If the MSC + +allocates an A interface circuit, it should only ever ask for resources from the BSS that it knows are not totally incompatible with the nominated circuit. The BSS will construct and send the appropriate radio assignment messages, if required (i.e. if the radio resource(s) has/have to be changed), as described in 3GPP TS 44.018 and start timer T10. The ASSIGNMENT REQUEST message includes sufficient information to allow the BSS to construct the necessary layer 3 radio messages. If the BSS allocates the A interface circuits, and such a circuit is needed, the BSS shall allocate a circuit. + +In the case where several circuit pools (groups of circuits supporting the same channel types) are available on the BSS MSC interface, the terrestrial circuit allocated by the MSC, if any, is chosen taking into account the circuit pool the circuit belongs to and the required channel type. + +The management of priority levels is implementation dependent, under operator control. + +If queuing is managed, new requests which cannot be served immediately are put in the queuing file according to the indicated priority levels. + +The priority levels and the preemption indicators may (singularly or in combination) be used to determine whether the assignment has to be performed unconditionally and immediately. This would lead to triggering of the preemption procedure which may then cause the forced release or forced handover of a lower priority connection if no free resource is immediately available. + +Whilst the process and the extent of the preemption procedure is operator dependent, the preemption indicators (refer to sub-clause 3.2.2.18.), if given in the ASSIGNMENT REQUEST, shall be treated on a per connection basis as follows: + +- The last received "Preemption Vulnerability indicator" and priority levels shall prevail. +- If the "Preemption Capability indicator" bit is set to 1, then this allocation request can trigger the running of the preemption procedure. +- If the "Preemption Capability indicator" bit is set to 0, then this allocation request cannot trigger the preemption procedure. +- If the "Preemption Vulnerability" bit is set to 1, then this connection is vulnerable and shall be included in the preemption process or procedure and as such may be subject to forced release or forced handover. +- If the "Preemption Vulnerability" bit is set to 0, then this connection is not vulnerable to preemption and shall not be included in the preemption process and as such may not be subject to forced release or forced handover. +- If no priority Information Element has been received, both "Preemption Capability" and "Preemption Vulnerability" bits shall be regarded as set to 0. + +The BSS shall ignore the classmark information included in the ASSIGNMENT REQUEST message if such information has already been received from the MS. + +The radio assignment procedure on the radio path is described in 3GPP TS 44.018. When the BSS is satisfied that the radio assignment procedure has been successfully accomplished (e.g. by receipt of a radio interface ASSIGNMENT COMPLETE message) it will stop timer T10 and return an ASSIGNMENT COMPLETE message over the BSS MSC interface. This will implicitly release the old dedicated radio resource(s) at the BSS. If an intra-BSS cell change has occurred during the assignment, the new cell identity is included in the ASSIGNMENT COMPLETE message and a HANDOVER PERFORMED message is not required. If the MSC gave the BSS some freedom in resource type selection, the choices made by the BSS are indicated in the ASSIGNMENT COMPLETE message. If an IP based user plane interface is supported, the "Speech Codec (Chosen)" shall be included in the ASSIGNMENT COMPLETE message. If the BSS has to allocate a circuit or an IP based user plane connection, the ASSIGNMENT COMPLETE message includes the identity of the circuit or the local IP endpoint included in the "AoIP Transport Layer Address" allocated by the BSS. + +If an IP based user plane interface is supported, the BSC should preferentially accept the preferred codec proposed by the MSC; the selection of an alternative codec may entail transcoding in the Network. + +When several circuit pools are present on the BSS MSC interface, and when the circuit is allocated by the MSC, the "circuit pool" information element shall be included in the ASSIGNMENT COMPLETE. The "circuit pool" field will indicate to the MSC the circuit pool of the CIC given in the ASSIGNMENT REQUEST message. + +If the assignment did not require a change of radio resource(s), and consequently no 3GPP TS 44.018 radio assignment procedure had been invoked, then the ASSIGNMENT COMPLETE message shall be returned to the MSC as soon as the requested resources have been allocated within the BSS. + +If the assignment requires a change of terrestrial circuit or in the case of assignment for signalling the release of a previously used terrestrial circuit, the change or release shall be performed before the ASSIGNMENT COMPLETE message is sent and the BSS shall consider that the old terrestrial circuit is idle. + +After the completion of the assignment procedure, until the connection is released or the MSC performs a new assignment, any dedicated resource assigned to the mobile station, e.g. at internal handover, must be in accordance with the description in the ASSIGNMENT REQUEST message. + +If the MS is a talker or listener in a voice group call, the MSC shall inform the BSS to which voice group call the MS belongs to and whether the MS is a talker or a listener. The BSS may then decide to allocate and assign dedicated channel or move the MS to a voice group call channel relating to the group call reference. If the BSS moves the MS to a voice group call channel it will send the ASSIGNMENT COMPLETE message and then immediately afterwards send a CLEAR REQUEST cause "Joined group call channel". If the assignment procedure is used to transfer the talker from a group call channel to a dedicated channel and the ASSIGNMENT REQUEST message contains a Group Call Reference IE with group key number other than 'no ciphering', the MSC shall provide the BSS with the permitted ciphering algorithms and the ciphering key to use in case the BSS assigns a dedicated channel. + +In the case where localised service area is supported the MSC may inform the BSS as to which LSA identities that the mobile has preferences by sending the LSA INFORMATION message. The BSS stores this information and uses it when determining the target cell list for handover. The algorithm for determining the target cell list for handover is not defined further in the present document. The reception of another message containing LSA identities for the connection will replace the LSA identities previously received. The BSS, in the case where localised service area is supported, will indicate the LSA identity of the serving cell in the ASSIGNMENT COMPLETE if it corresponds to one of the LSA identities received in the latest LSA INFORMATION or the HANDOVER REQUEST messages. + +In the case where Intersystem handover to other RAT's is supported, the MSC may inform the BSS, if preference for other radio access technologies (Service based handover) shall be applied to the MS connection. In such cases the MSC sets the Service Handover Information Element accordingly in the ASSIGNMENT REQUEST message. The Service Handover information is stored in the BSS throughout the connection and is used in the Handover evaluation process. + +If the Service Handover information element indicates that "handover to UTRAN or cdma2000 should be performed", the BSS should perform an Intersystem handover via directed retry instead of the assignment. If this is not possible, the BSS shall proceed with the assignment procedure as specified above. + +NOTE 1: If, due to limitations of the mobile station or the network it is attached to, the service requested by the subscriber cannot be provided in GSM, but by another RAT, then the MSC may include in the ASSIGNMENT REQUEST message a Service Handover information element indicating that "handover to UTRAN or cdma2000 should be performed" and the required channel type coded according to NOTE 4 in subclause 3.2.2.11. The MSC may under these circumstances omit allocating a terrestrial circuit. In such a case, if the BSC cannot initiate a directed retry, the assignment will fail. + +If local switching is requested by the core network, the MSC includes the Global Call Reference IE, LCLS-Configuration IE, and optionally the LCLS-Connection-Status-Control IE and the LCLS-Correlation-Not-Needed IE in the ASSIGNMENT REQUEST message. + +If the BSS supports Local Call Local Switch (LCLS) and receives the ASSIGNMENT REQUEST message containing the Global Call Reference IE and the LCLS-Configuration IE, then the BSS shall store the Global Call Reference (GCR) value (or replace the previously stored GCR value) and check if the requested LCLS configuration included in the LCLS-Configuration IE is supported. + +- If the requested LCLS configuration is not supported, then the BSS shall indicate this to the MSC in the LCLS-BSS-Status IE included in the ASSIGNMENT COMPLETE message, see sub-clause 3.1.33.2.3. +- If the BSS supports the requested LCLS configuration, then the BSS shall perform call leg correlation as described in sub-clause 3.1.33.2.1 and report the outcome to the MSC in LCLS-BSS-Status IE included in the ASSIGNMENT COMPLETE message. + +If BSS determines that the call is an intra-BSS call and therefore can be locally switched it shall not through-connect the two parties unless explicitly indicated to do so in the ASSIGNMENT REQUEST message by receiving the LCLS-Connection-Status-Control IE set to "Connect" on both call legs. + +NOTE 2: If not included in the ASSIGNMENT REQUEST message, the LCLS-Connection-Status-Control IE may be received in the LCLS-CONNECT-CONTROL message after completion of the assignment procedure. + +The BSS shall inform the MSC of the local switch establishment outcome by including the LCLS-BSS-Status IE with the correct LCLS connection status value according to sub-clause 3.2.2.119 in the ASSIGNMENT COMPLETE message. The BSS shall also notify the MSC serving the other call leg if the LCLS connection status is changed for this call leg, see sub-clause 3.1.33.5. + +NOTE 3: If the BSS does not support LCLS then the Global Call Reference IE and the LCLS-Configuration IE in the ASSIGNMENT REQUEST message will be ignored by the BSS and no LCLS-BSS-Status IE will be returned in the ASSIGNMENT COMPLETE message. + +If the MSC determines that CS to PS SRVCC is allowed for this particular connection, the MSC includes the CS to PS SRVCC IE in the ASSIGNMENT REQUEST message. + +Upon reception of an ASSIGNMENT REQUEST message including the CS to PS SRVCC IE, the BSS may trigger the CS to PS SRVCC procedure (see 3GPP TS 44.018) according to the reported capabilities of the MS. + +### 3.1.1.2 Assignment Failure + +The following failure conditions may occur: + +The BSS may not be able to use the terrestrial resource that the MSC has indicated in which case an ASSIGNMENT FAILURE message will be returned to the MSC with the cause set to "requested terrestrial resource unavailable". + +The BSS may not be able to support any of the permitted ciphering algorithms. In this case a ASSIGNMENT FAILURE message shall be returned to the MSC with the failure cause set to "ciphering algorithm not supported". + +If the requested channel type or resource (e.g. channel rate, speech version, Codec Type or Codec Configuration, Redundancy Level, A-Interface Type, etc.) indicated in the ASSIGNMENT REQUEST message is not temporarily available (e.g. due to overload) or not supported in the BSS, then an ASSIGNMENT FAILURE message shall be returned to the MSC. The appropriate failure cause will be included in the message (Cause value: "requested transcoding/rate adaptation unavailable" or "requested speech version unavailable" or "Requested Codec Type or Codec Configuration unavailable" or "Requested Redundancy Level not supported" or "Requested Redundancy Level not available" or "Requested Codec Type or Codec Configuration not supported" or "Requested A-Interface Type unavailable" or "Requested A-Interface Type not supported"). + +If the MSC requested an IP-bearer for the A-Interface by providing the AoIP Transport Layer Address and not providing a Circuit Identity Code, but the BSS is not able to use an IP-bearer, then the BSS shall not allocate a Circuit Identity Code on its own, even if the Codec List (MSC Preferred) included a Codec Type with the PT bit set to "1", but shall return an ASSIGNMENT FAILURE message to the MSC with the Cause value "Requested A-Interface Type unavailable". + +If, on reception by the BSS of an ASSIGNMENT REQUEST message allocating a circuit, the circuit pool implied by the CIC information element is incompatible with the channel type indicated (that is, the pool does not support any of the radio resources indicated by the channel type) an ASSIGNMENT FAILURE shall be returned to the MSC with the failure cause set to "circuit pool mismatch". + +If, on reception by the BSS of an ASSIGNMENT REQUEST message modifying an already allocated circuit, the circuit pool implied by the CIC information element is incompatible with the channel type indicated (that is, the pool does not support any of the radio resources indicated by the channel type) the BSS shall return to the MSC either : + +- an ASSIGNMENT FAILURE message with the failure cause set to "circuit pool mismatch", or +- an ASSIGNMENT FAILURE message with the failure cause "directed retry" before sending a HANDOVER REQUIRED message with the cause "switch circuit pool" and the "circuit pool list" information element . The "circuit pool list" information element will allow the BSS to indicate to the MSC from which circuit pool or pools the new CIC should be chosen, or +- a HANDOVER REQUIRED message with the cause "switch circuit pool" and the "circuit pool list" information element . The "circuit pool list" information element will allow the BSS to indicate to the MSC from which circuit pool or pools the new CIC should be chosen. + +If, on reception by the BSS of an ASSIGNMENT REQUEST message allocating a circuit, the circuit pool implied by the CIC is compatible with the channel type indicated (that is, the pool supports at least one of the radio resource types + +indicated by the channel type), but the BSS still wishes to change the circuit pool, it sends an ASSIGNMENT FAILURE with the cause "switch circuit pool" and the "circuit pool list" information element. + +The "circuit pool" information element, when present in the ASSIGNMENT FAILURE, indicates to the MSC which circuit pool the CIC indicated in the ASSIGNMENT REQUEST belongs to. This can be used by the MSC to correct its tables (CIC/circuit pool). The "circuit pool list" information element, when present in the ASSIGNMENT FAILURE, is used when the BSS wishes to indicate to the MSC its preferred circuit pools. The circuit pools in the "circuit pool list" information element shall be given in order of preference. In the case of an ASSIGNMENT FAILURE with the cause "circuit pool mismatch", the MSC may decide to block the circuit and to send an O & M notification. + +The BSS may not receive a radio interface ASSIGNMENT COMPLETE message from the MS in which case the timer T10 will expire. In this case an ASSIGNMENT FAILURE message is returned to the MSC and the assignment procedure is terminated (cause value: radio interface message failure). + +If the cell for which the assignment is intended is congested or in case of a Service Handover indication received from the MSC, the BSS may indicate an impending directed retry attempt by sending ASSIGNMENT FAILURE (Cause value: directed retry). + +If the radio channel assignment fails for any other reason then an ASSIGNMENT FAILURE message will be returned to the MSC, the procedure will terminate, and the associated references concerning the old dedicated resource(s) should be maintained until explicitly released by the MSC. It should be noted that if the MS fails to assign after receiving a radio interface ASSIGNMENT COMMAND and returns to the old channels as detailed in 3GPP TS 24.008, then the radio interface ASSIGNMENT FAILURE message received from the MS will cause an ASSIGNMENT FAILURE message to be returned to the MSC (cause value: "Radio interface failure, reversion to old channel"). + +If the BSS has received LSA INFORMATION or HANDOVER REQUEST message indicating LSA only access and all available radio resources are outside the allowed LSAs, assignment may fail and ASSIGNMENT FAILURE message may be sent to the MSC (cause value: "LSA not allowed"). + +If all available radio resources are defined for exclusive access and the connection is not allowed to access these resources, assignment may fail and ASSIGNMENT FAILURE message may be sent to the MSC (cause value: "LSA not allowed"). + +Other possible Cause values which may be returned with the ASSIGNMENT FAILURE message are: "equipment failure", "no radio resource available", "O&M intervention". If an unrecognised cause value is received, the Class of the cause value should be used to determine the MSC's action. + +In the case where the MSC has attempted to assign a terrestrial circuit and an ASSIGNMENT FAILURE message has been returned then both the MSC and the BSS shall consider that the terrestrial circuit is idle (except as described below in sub-clause 3.1.1.3) and therefore no explicit clearing sequence is needed. + +The MSC may not be able to use the terrestrial resource that the BSS has indicated. In this case, the procedure is nevertheless considered terminated successfully, and it is up to the MSC to correct the situation, e.g. by a circuit re-selection procedure (not relevant for an IP based user plane interface). + +All messages concerned with an assignment are sent using the connection oriented mode of the SCCP. + +### 3.1.1.3 Abnormal Conditions + +If the BSS receives an ASSIGNMENT REQUEST message calling up a terrestrial circuit for the user plane interface that is already assigned to another call then an ASSIGNMENT FAILURE message will be returned with a Cause value of: "terrestrial circuit already allocated" and no action will be taken on the radio interface. + +If the BSS receives an ASSIGNMENT REQUEST message allocating a terrestrial circuit which has been blocked by a global block message, then an ASSIGNMENT FAILURE message shall be sent (Cause value: "requested terrestrial resource unavailable"). A single global BLOCK message (not repeated and not guarded by timer T1) shall be sent for that concerned terrestrial circuit. + +If an external handover becomes necessary during an assignment, for reasons of radio conditions, congestion or following the reception of a Service Handover indication from the MSC, the BSS may initiate the handover (directed retry) whilst the assignment is in progress. In this situation, if a HANDOVER COMMAND is received by the BSS, it must not be ignored. + +### 3.1.2 Blocking and Unblocking + +The Blocking and Unblocking procedures are not applied for an IP based user plane interface. + +As described in sub-clause 3.1.1 the assignment procedure depends upon one side, the MSC or the BSS, choosing the terrestrial resource to be used. If the entity on one side puts out of service any terrestrial circuit, it needs to inform the peer entity on the other side of the interface. This is performed by using a simple blocking/unblocking procedure. The block messages used to support this procedure are sent as global messages (i.e. using the SCCP connectionless mode). Each message refers to one or more terrestrial circuits accessed through the BSS MSC interface. The circuit is identified by its Circuit Identity Code. + +The support of blocking/unblocking procedures is dependent on which side allocates the circuits. + +A circuit is said to be "locally blocked" on a given side if it has been put out of service for a local reason, and to be "remotely blocked" if a BLOCK message about this circuit has been received from the peer entity. + +#### 3.1.2.1 Successful Operation + +The procedure operates as follows: + +Initial conditions are assumed to be that all circuits are remotely unblocked. + +An entity may locally block a terrestrial circuit because: + +- Operation and Maintenance intervention makes the circuit unavailable for use (Cause value: "O and M intervention"). +- An equipment failure makes the circuit unavailable (Cause value: "equipment failure"). +- Radio resource is not accessible from the terrestrial circuit (Cause value: "no radio resource available"). + +When and if the party that does not allocate the circuits (the Circuit Slave) decides to locally block a terrestrial circuit, it shall immediately mark that terrestrial circuit as "blocked" (to stop any future allocation of that terrestrial circuit) and shall then send a block message to the peer entity allocating the circuits (the Circuit Master) and start timer T1 (T20, T21, T22). + +The BLOCK message contains the Circuit Identity Code indicating the terrestrial circuit that is to be remotely blocked and a Cause Information Element indicating the reason for blocking. Typical Cause values are: "no radio resources available", "O and M intervention", "equipment failure". + +A BLOCK message in the MSC to BSS direction may also contain an indication that the connection using the circuit, if any, must be released; in such a case the circuit master shall check if the circuit is in use and shall release the connection(s) that use it. + +NOTE: This allows the MSC to simultaneously block the circuit and to release the connection(s) using the circuit, if any, and then to prevent use of the circuit by the BSS between connection(s) release and blocking. + +If the CIRCUIT GROUP BLOCK message is applied by the circuit slave the circuits to be remotely blocked are indicated in the status field of the Circuit Identity Code List (sub-clause 3.2.2.31). + +Receipt of a block message (BLOCK or CIRCUIT GROUP BLOCK) at the circuit master from the circuit slave will indicate to the circuit master that the identified circuits are unavailable for reselection. If a call is in progress on any of the identified terrestrial circuits then it will be unaffected by this procedure unless explicitly requested, the circuits will however be "camp on blocked". Such circuits shall be remotely blocked as soon as that call is no longer in progress, or active. + +On receipt of a BLOCK message asking for the release of the connection(s) using the circuit if any, and if the BSS detects that there exists a connection using the indicated circuit, the BSS shall attempt to release the connection(s), e.g., by sending a CLEAR REQUEST message on each of the corresponding SCCP connections. As specified in sub-clause 3.1.17, if the SCCP connection has been lost, the BSS will detect it when attempting to release the connection and the whole connection is released as a consequence. + +An appropriate blocking acknowledge message (BLOCKING ACKNOWLEDGE or CIRCUIT GROUP BLOCKING ACKNOWLEDGE) will be returned to the circuit slave by the circuit master to acknowledge receipt of the block message and to indicate that any necessary action has been taken. + +The CIRCUIT GROUP BLOCKING ACKNOWLEDGEMENT message is accepted as the appropriate acknowledgement only if the indicated Circuit Identity Code and the returned Range field of the Circuit Identity Code List match the corresponding parameter values of the respective initiating message. Otherwise the message is considered as not expected. + +On receipt of the blocking acknowledge the circuit slave shall stop timer T1 (T20, T21, T22). + +The resource involved will be assumed to be remotely blocked by the circuit master until either an unblock (UNBLOCK or CIRCUIT GROUP UNBLOCK) or RESET message is received relevant to that resource. + +If the circuit slave wishes to unblock a blocked circuit and return it to service then it shall immediately mark the circuit as "locally unblocked" and then send an unblock message, and start timer T1 (T20, T21, T22). + +If an unblock message (UNBLOCK or CIRCUIT GROUP UNBLOCK) is received at the circuit master for a blocked resource then the resource will be marked as not remotely blocked and an unblocking acknowledge message (UNBLOCKING ACKNOWLEDGE or CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE) will be returned to the circuit slave. The circuit slave shall stop timer T1 (T20, T21, T22) on receipt of this unblocking acknowledge. + +The CIRCUIT GROUP UNBLOCKING ACKNOWLEDGEMENT message is accepted as the appropriate acknowledgement only if the indicated Circuit Identity Code and the returned Range field of the Circuit Identity Code List match the corresponding parameter values of the respective initiating message. Otherwise the message is considered as not expected. + +Figure 10 shows an overview of the blocking procedure in the case the circuit slave is the BSS. + +NOTE: Timer T1 is used to supervise a single circuit block/unblock procedure on the BSS side, whilst T20 is used to supervise the circuit group block/unblock procedure on the BSS side, timer T21 is used to supervise a single circuit block/unblock procedure on the MSC side, and T22 is used to supervise the circuit group block/unblock procedure on the MSC side. + +### 3.1.2.2 Abnormal Conditions + +If a blocking acknowledge message is not received for a block message within T1 (T20, T21, T22) seconds then the block message will be repeated. If this occurs a second time the circuits will be kept marked as locally blocked, and the situation must then be resolved internally within the circuit slave or by O&M procedures. + +If an unblocking acknowledge message is not received for an unblock message before expiry of timer T1(T20, T21, T22) then the unblock message will be repeated. If this occurs a second time, this situation may be reflected to the O&M, which shall resolve the possible conflict. The unblock message is repeated at most one time. Whatever the outcome of possible repetitions, the concerned circuits remain locally "unblocked". + +If the MSC allocates the circuits, and an ASSIGNMENT REQUEST or HANDOVER REQUEST message is received by the BSS allocating a circuit which is marked at the BSS as blocked then an ASSIGNMENT FAILURE message or a HANDOVER FAILURE message (respectively) followed by a BLOCK message shall be sent to the MSC. + +If the BSS allocates the circuits, and an ASSIGNMENT COMPLETE, HANDOVER REQUEST ACKNOWLEDGE or CHANGE CIRCUIT ACKNOWLEDGE message is received by the MSC allocating a circuit which is marked at the MSC as blocked, it is up to the MSC how to correct the situation, e.g., by performing a circuit re-selection procedure and sending a BLOCK message. + +#### 3.1.2.2.1 Applying to the Single Circuit Block Procedure + +- i) If a BLOCK message is received for a circuit already remotely blocked, a BLOCKING ACKNOWLEDGE message will be sent. +- ii) If an UNBLOCK message is received for a remotely unblocked circuit, an UNBLOCKING ACKNOWLEDGE message will be sent. +- iii) If a BLOCKING ACKNOWLEDGE message, which is not expected as an acknowledgement for a BLOCK message, is received: + +- a) Relating to a circuit which is locally blocked, the BLOCKING ACKNOWLEDGE message is discarded. + - b) Relating to a circuit, which is not locally blocked, then an UNBLOCK message will be sent. +- iv) If an UNBLOCKING ACKNOWLEDGE message, which is not expected as an acknowledgement for an UNBLOCK message, is received: +- a) Relating to a circuit which is not locally blocked, the received UNBLOCKING ACKNOWLEDGE message is discarded. + - b) Relating to a circuit, which is locally blocked, then a BLOCK message will be sent. + +### 3.1.2.2.2 Applying to the Circuit Group Block Procedure + +- v) If a CIRCUIT GROUP BLOCK message is received relating to remotely blocked circuits then blocking acknowledgement indications for those circuits are given in the status field of the corresponding CIRCUIT GROUP BLOCKING ACKNOWLEDGE message which will be sent in response. +- vi) If a CIRCUIT GROUP UNBLOCK message is received relating to circuits which are not remotely blocked then unblocking acknowledgement indications for those circuits are given in the status field of the corresponding CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message which will be sent in response. +- vii) When the circuit master upon receipt of a CIRCUIT GROUP BLOCK (UNBLOCK) message is not able to give an appropriate blocking (unblocking) acknowledgement indication for each Circuit Identification Code (e.g. because that/those Circuit Identification Code(s) is (are) not allocated to any circuit at the receiving entity) for which a block (unblock) indication is given in the status field of the received CIRCUIT GROUP BLOCK (UNBLOCK) message, then no blocking (unblocking) acknowledgement relating to that/those Circuit Identification Code(s) will be given in the status field of the corresponding CIRCUIT GROUP BLOCKING (UNBLOCKING) ACKNOWLEDGE message which will be sent in response. +- viii) If a CIRCUIT GROUP BLOCKING ACKNOWLEDGE message in response to a CIRCUIT GROUP BLOCK message is received by the circuit slave containing in the status field no blocking acknowledgement for circuits which are to be blocked due to the previously sent CIRCUIT GROUP BLOCK message, then the CIRCUIT GROUP BLOCK message will be repeated for the circuit(s) concerned. + +If this occurs a second time the concerned circuit(s) will be kept marked as locally blocked, and the situation must then be resolved internally within the circuit slave or by O&M procedures. + +- ix) The same rule applies to the Circuit Group Unblocking procedure with the only difference that the involved terrestrial circuits are kept marked as locally "not blocked". +- x) If a CIRCUIT GROUP BLOCKING ACKNOWLEDGE message in response to a CIRCUIT GROUP BLOCK message is received by the circuit slave containing in the status field blocking acknowledgement indications for circuits which are not to be blocked, then an appropriate unblock message will be sent for the circuit(s) concerned. +- xi) If a CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message in response to a CIRCUIT GROUP UNBLOCK message is received by the circuit slave containing in the status field unblocking acknowledgement indications for circuits which have to remain marked as locally blocked then an appropriate block message will be sent for the circuit(s) concerned. +- xii) If a CIRCUIT GROUP BLOCKING ACKNOWLEDGE message which is not expected and not accepted as an acknowledgement for a CIRCUIT GROUP BLOCK message is received: + - a) relating to circuits which all are in the status locally blocked, then the received CIRCUIT GROUP BLOCKING ACKNOWLEDGE message will be discarded; + - b) related to circuits part or all of which are not in the status locally blocked then an appropriate unblock message will be sent for the relevant circuit(s). +- xiii) If a CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message which is not expected and not accepted as an acknowledgement for a CIRCUIT GROUP UNBLOCK message is received: + - a) relating to circuits none of which is in the status locally blocked, then the received CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message will be discarded; + +- b) related to circuits part or all of which are locally blocked then an appropriate block message will be sent for the relevant circuit(s). + +### 3.1.3 Resource Indication + +The purpose of the resource indication procedure is: + +- To inform the MSC of the amount: + - of radio resource that is spare at the BSS and available for traffic carrying purposes; and + - of the total amount of the accessible radio resource (i.e. available for service or currently assigned). + +This cannot easily be derived from the traffic that the MSC is carrying. The MSC may take these pieces of information into account for the external handover decision. + +#### 3.1.3.1 Successful Operation + +The procedure relates to a single cell. + +The MSC determines the resource information (i.e. the resource available information and optionally the total resource accessible information) and the manner in which the BSS transfers this resource information to the MSC by sending a RESOURCE REQUEST message to the BSS. This message shall contain a Resource Indication Method Information Element which can be set to one of the following values: + +- i) (Spontaneous resource information expected): The BSS shall send the first RESOURCE INDICATION message without any resource information to the MSC immediately as an acknowledgement to the RESOURCE REQUEST message and then any further RESOURCE INDICATION messages spontaneously every time conditions, defined by O&M, are met in the BSS for the considered cell (e.g. traffic thresholds, or time interval between two messages). If the O&M conditions for sending RESOURCE INDICATION messages are met, the BSS may use the Periodicity IE received in the RESOURCE REQUEST message to determine the time interval between indications, except that, if the MSC sets the Periodicity IE to zero then the BSS shall ignore the Periodicity IE. The BSS stays in this mode until the receipt of a new RESOURCE REQUEST message for the same cell, or a reset occurs. +- ii) (One single resource information expected): The BSS shall return a single RESOURCE INDICATION message with some resource information immediately. If the RESOURCE REQUEST message does not contain an Extended Resource indicator IE the BSS shall then cease any resource information transfer related to the cell until the receipt of either a new RESOURCE REQUEST message or a reset. If the RESOURCE REQUEST message contains an Extended Resource Indicator IE the BSS shall obey the 'Subsequent Mode' field. +- iii) (Periodic resource information expected): The BSS shall return a RESOURCE INDICATION message with some resource information immediately, and then periodically, with a period set by MSC (note), until the receipt of either a new RESOURCE REQUEST message for the same cell or a reset. + +NOTE: (The period shall equal the value of the periodicity parameter times 100 ms. If the value of the periodicity parameter is zero, then the message should be treated as one containing an incorrect value according to sub-clause 3.1.19.4, case 2.) + +- iv) (No resource information expected): The BSS shall immediately return a single RESOURCE INDICATION message without any resource information as an acknowledgement to the RESOURCE REQUEST message and then the BSS to MSC transfer of resource information related to the cell is disabled until the receipt of either a new RESOURCE REQUEST message for the same cell or a reset. + +The default mode is iv); after a reset, this mode is set for all the cells of a BSS. + +The transfer of resource information related to a given cell from the BSS to the MSC occurs when the Resource Indication Method Information Element is set to one of the values i) to iii) in the BSS. The BSS sends RESOURCE INDICATION messages to the MSC, under the conditions explained above. The RESOURCE INDICATION message shall contain the Resource Indication Method Information Element with the same value as it was requested by the MSC, i.e. the BSS is not allowed to select a method different from the one requested by the MSC. + +Furthermore, the RESOURCE INDICATION message may contain the Resource Available IE and the Total Resource Accessible IE dependent on the selected method and, in case of the Total Resource Accessible IE, also dependent on the request from the MSC. If the RESOURCE INDICATION message is just taken as a simple acknowledgement as stated + +in method i) and iv), the Total Resource Accessible IE shall not be returned independent of whether it was requested by the MSC or not. + +For each idle channel the level of interference will be averaged over a period of Intave. (Intave is a parameter set by O&M command on a per cell basis). This averaging will be performed immediately before the transmission of the RESOURCE INDICATION message. The result of this averaging will be used to classify the average interference level on the idle channels into five interference bands. + +The Resource Available Information Element contains two pieces of information for each of the five interference bands: + +- The number of half rate TCHs available in that band. +- The number of full rate TCHs available in that band. + +The levels of the five bands are defined by O&M. + +### 3.1.4 Reset + +#### 3.1.4.1 Global Reset Procedure + +The purpose of the reset procedure is to initialise the BSS and MSC in the event of a failure. The procedure is a global procedure applying to a whole BSS, and therefore all messages relating to the reset procedure are sent as global messages using the connectionless mode of the SCCP. + +If only a limited part of the MSC or BSS has suffered a failure then clearing procedures can be used to clear only those affected calls. + +##### 3.1.4.1.1 Reset at the BSS + +In the event of a failure at the BSS which has resulted in the loss of transaction reference information, a RESET message is sent to the MSC or, if the network supports "Intra domain connection of RAN nodes to multiple CN nodes" (see 3GPP TS 23.236 [48]) to all the MSCs towards which the BSS has signalling connections established. This message is used by the MSC to release affected calls and erase all affected references, and to put all circuits into the idle state. + +After a guard period of T2 seconds a RESET ACKNOWLEDGE message is returned by the MSC(s) to the BSS indicating that all references have been cleared. + +After the sending of the RESET to the MSC(s) a BSS that does not allocate the circuits shall initiate blocking procedures (Block or Circuit group block procedures) for all circuits that are locally blocked on the BSS side, the MSC(s) shall respond as specified in sub-clause 3.1.2. The sending of block messages shall be done without waiting for the acknowledgement to the RESET message. + +Upon receipt of a RESET message from the BSS an MSC that does not allocate the circuits shall send block messages (BLOCK or CIRCUIT GROUP BLOCK) for all circuits that are locally blocked on the MSC side, the BSS shall respond to these with blocking acknowledge messages as described in sub-clause 3.1.2. + +If a RESET message is received with the information element "A-Interface Selector for RESET" indicating both TDM and IP or if the "A-Interface Selector for RESET" is not present in the RESET message, then the RESET message shall have precedence over all other procedures. + +##### 3.1.4.1.2 Reset at the MSC + +In the event of a failure at the MSC which has resulted in the loss of transaction reference information, a RESET message is sent to the BSS. This message is used by the BSS to release affected calls and erase all affected references and to put all circuits into the idle state. + +After the sending of the RESET to the BSS, an MSC that does not allocate the circuits shall initiate blocking procedures (Block or Circuit group block procedures) for all circuits that are locally blocked on the MSC side, the BSS shall respond as specified in sub-clause 3.1.2. The sending of block messages shall be done without waiting for the acknowledgement to the RESET message. + +Upon receipt of a RESET message from the MSC a BSS that does not allocate the circuits shall send block messages (BLOCK or CIRCUIT GROUP BLOCK) for all circuits that were previously locally blocked on the BSS side, the MSC shall respond to these with blocking acknowledge messages as described in sub-clause 3.1.2. + +After a guard period of T13 seconds a RESET ACKNOWLEDGE message is returned to the MSC, indicating that all MSs which were involved in a call are no longer transmitting and that all references at the BSS have been cleared. + +If a RESET message is received with the information element "A-Interface Selector for RESET" indicating both TDM and IP or if the "A-Interface Selector for RESET" is not present in the RESET message, then the RESET message shall have precedence over all other procedures. + +### 3.1.4.1.3 Abnormal Conditions + +#### 3.1.4.1.3.1 Abnormal Condition at the BSS + +If the BSS sends a RESET message to the MSC and receives no RESET ACKNOWLEDGE message within a period T4 then it shall repeat the entire reset procedure. The sending of the RESET message is repeated a maximum of "n" times where n is an operator matter. After the n-th unsuccessful repetition the procedure is stopped and the maintenance system is informed. + +#### 3.1.4.1.3.2 Abnormal Condition at the MSC + +If the MSC sends a RESET message to the BSS and receives no RESET ACKNOWLEDGE message within a period T16 then it shall repeat the entire reset procedure. The sending of the RESET message is repeated a maximum of "n" times where n is an operator matter. After the nth unsuccessful repetition the procedure is stopped and the maintenance system is informed. + +### 3.1.4.2 Reset Circuit + +The purpose of the reset circuit procedure is to restore the information in MSC/BSS in the case of a failure which has affected only a small part of the equipment (e.g. abnormal SCCP connection release). + +#### 3.1.4.2.1 Reset Circuit at the BSS + +If a circuit has to be put to idle at the BSS due to either an abnormal release of the SCCP-connection for a resource that is not configured for A-interface circuit sharing, or an abnormal release of an SCCP connection for a terrestrial resource that is configured for A-interface circuit sharing for which there are no remaining SCCP connections on the resource, a RESET CIRCUIT message will be sent to the MSC. When the MSC receives this message, it clears the possible call and puts the circuit, if known, to the idle state. If the circuit is known, a RESET CIRCUIT ACKNOWLEDGE message is returned to the BSS. If circuit allocation is done by the BSS and if the circuit is locally blocked at the MSC a BLOCK message shall be returned to the BSS. The BSS shall then respond with a BLOCKING ACKNOWLEDGE message, as described in sub-clause 3.1.2. If the circuit is unknown in the MSC, an UNEQUIPPED CIRCUIT message is returned to the BSS. + +Timer T19 is used at the BSS to supervise the reset circuit procedure. If the timer elapses before a response (RESET, RESET CIRCUIT ACKNOWLEDGE or UNEQUIPPED CIRCUIT) is returned to the BSS, the procedure is repeated. + +#### 3.1.4.2.2 Reset Circuit at the MSC + +If a circuit has to be put to idle at the MSC due to either an abnormal release of the SCCP-connection for a resource that is not configured as a shared resource, or an abnormal release of an SCCP connection for a terrestrial resource that is configured for A-interface circuit sharing for which there are no remaining SCCP connections for the resource, a RESET CIRCUIT message will be sent to the BSS. When the BSS receives a RESET CIRCUIT message, it shall respond with a RESET CIRCUIT ACKNOWLEDGE message in case the circuit can be put to idle. If circuit allocation is done by the MSC and if the circuit is locally blocked at the BSS a BLOCK message shall be returned to the MSC. The MSC shall then respond with a BLOCKING ACKNOWLEDGE message, as described in sub-clause 3.1.2. If the circuit is unknown at the BSS, the BSS shall return an UNEQUIPPED CIRCUIT message to the MSC. + +Timer T12 is used at the MSC to supervise the reset circuit procedure. If the Timer elapses before a response (RESET, RESET CIRCUIT ACKNOWLEDGE, UNEQUIPPED CIRCUIT or BLOCK) the reset circuit procedure is repeated. + +#### 3.1.4.2.3 Abnormal conditions + +If a RESET message is received with the information element "A-Interface Selector for RESET" indicating TDM or if the "A-Interface Selector for RESET" is not present in the RESET message, after sending of a RESET CIRCUIT message and before receipt of the corresponding response the respective reset circuit procedure is stopped, i.e. reception of the corresponding RESET CIRCUIT ACKNOWLEDGE message is not required and no repetition is necessary. + +If a RESET CIRCUIT message is received immediately after a RESET CIRCUIT message has been sent for the same circuit, the corresponding acknowledgement messages are returned. + +The sending of the RESET CIRCUIT message is repeated a maximum of "n" times where n is an operator matter. After the n-th unsuccessful repetition the procedure is stopped and the maintenance system is informed. + +### 3.1.4.3 Reset IP Resource + +This procedure is relevant when a Call Identifier has been previously sent/received for the concerned connection, i.e. when an IP bearer has been selected for this call. + +The purpose of the Reset IP Resource procedure is to initialise part of the resources in the BSS in the event of an abnormal failure in the MSC or vice versa (e.g. Signalling Transport processor reset). The procedure uses connectionless signalling. + +#### 3.1.4.3.1 Reset IP Resource procedure initiated by the BSS + +The BSS initiates the procedure by sending a RESET IP RESOURCE message to the MSC. + +The RESET IP RESOURCE message shall include the Call Identifier List and the Cause with the appropriate cause value (e.g. "abnormal SCCP connection release"). + +On reception of this message the MSC shall release locally the resources and references associated to the Call Identifiers indicated in the received message. The MSC shall always return the RESET IP RESOURCE ACKNOWLEDGE message to the BSS after all Call Identifier related resources and references have been released and the MSC shall include the list of Call Identifiers. The list of Call Identifiers within the RESET IP RESOURCE ACKNOWLEDGE message shall be in the same order as received in the RESET IP RESOURCE message. Unknown Call Identifiers shall be reported as released. + +The MSC shall provide means to prevent the immediate re-assignment of released Call Identifiers to minimise the risk that the Reset IP Resource procedure releases the same Call Identifiers re-assigned to new calls. + +Timer Trbss is used at the BSS to supervise the Reset IP Resource procedure. If the timer elapses before a response message (RESET, RESET IP RESOURCE ACKNOWLEDGE) is returned to the BSS, then the RESET IP RESOURCE message may be repeated by the BSS. + +#### 3.1.4.3.2 Reset IP Resource procedure initiated by the MSC + +The MSC initiates the procedure by sending a RESET IP RESOURCE message to the BSS. + +The RESET IP RESOURCE message shall include the Call Identifier List and the Cause with the appropriate cause value (e.g. "abnormal SCCP connection release"). + +On reception of this message the BSS shall release locally the resources and references associated to the specific Call Identifiers indicated in the received message. The BSS shall always return the RESET IP RESOURCE ACKNOWLEDGE message to the MSC after all Call Identifier related resources and references have been released and the BSS shall include the list of Call Identifiers. The list of Call Identifiers within the RESET IP RESOURCE ACKNOWLEDGE message shall be in the same order as received in the RESET IP RESOURCE message. Unknown Call Identifiers shall be reported as released. + +The MSC shall provide means to prevent the immediate re-assignment of released Call Identifiers to minimise the risk that the Reset IP Resource procedure releases the same Call Identifiers re-assigned to new calls. + +Timer Trmsc is used at the MSC to supervise the Reset IP Resource procedure. If the Timer elapse before a response message (RESET, RESET IP RESOURCE ACKNOWLEDGE) is returned to the MSC, then the RESET IP RESOURCE message may be repeated by the MSC. + +#### 3.1.4.3.3 Abnormal conditions + +If a RESET message is received with the information element "A-Interface Selector for RESET" indicating IP or if the "A-Interface Selector for RESET" is not present in the RESET message, after sending of a RESET IP RESOURCE message and before receipt of the corresponding RESET IP RESOURCE ACKNOWLEDGE message, then the respective Reset IP Resource procedure is stopped, i.e. the reception of the corresponding RESET IP RESOURCE ACKNOWLEDGE message is not required and no repetition is necessary. + +If a RESET IP RESOURCE message is received immediately after a RESET IP RESOURCE message has been sent for the same Call Identifier, then the corresponding RESET IP RESOURCE ACKNOWLEDGE message is returned after the resources has been released. + +The sending of the RESET IP RESOURCE message is repeated a maximum of n times, where n is an operator defined value. After the n-th unsuccessful repetition the procedure is stopped and local resources associated to the specified Call Identifiers shall be considered as released. + +If a RESET IP RESOURCE ACKNOWLEDGE message does not contain exactly the same Call Identifiers in the Call Identifier List as sent in the related RESET IP RESOURCE message, the RESET IP RESOURCE message may be repeated. + +### 3.1.5 External Handover + +The details of the radio information as far as handover is concerned are given in 3GPP TS 24.008. The relevant network information is given in 3GPP TS 23.009. + +Using this protocol the BSS should support handover transitions to and from any combinations of the following: + +- Channel. +- SDCCH. +- Full Rate TCH. +- Half Rate TCH. +- Multiple Full Rate TCHs. + +In this specification three procedures are defined which can be used for handover. They are: + +- Handover Required Indication. +- Handover Resource Allocation. +- Handover Execution. + +(Figure 16 shows an example of a complete handover procedure.) + +For any HANDOVER REQUIRED message at most one HANDOVER COMMAND message may be sent. + +In the case of inter-MSC handover the term "the MSC" in this sub-clause is taken to mean the relevant MSC in the handover operation. + +The handover procedures are specified in the following sub-clauses. + +All messages concerned with handover, with the exception of HANDOVER CANDIDATE ENQUIRE and HANDOVER CANDIDATE RESPONSE messages, are sent using the connection oriented mode of the SCCP. + +#### 3.1.5.1 Handover Required Indication + +If an IP based user plane interface is supported, this procedure shall not be used when the target BSS and serving BSS are the same. + +The handover required indication procedure allows a BSS to request the handover for a particular MS if it is currently allocated one or more dedicated resources or currently allocated one dedicated resource and one or more packet resources (in which case DTM handover is indicated). This is done by generating a HANDOVER REQUIRED message and sending it from the BSS to the MSC. If so required by the BSS, the MSC informs the BSS if the handover cannot be carried out. This is done by a HANDOVER REQUIRED REJECT message. The HANDOVER REQUIRED message is sent using the BSSAP SCCP connection already set up for that transaction. As part of the BSS's functions, the BSS continually monitors all radio information and compares it with parameters such that if the transmission quality of a given parameter (or set of parameters) passes a predetermined threshold (set by O&M) then a HANDOVER REQUIRED message is generated and sent to the MSC. + +The BSS shall not initiate the handover required indication procedure in the case of an MOCN or a GWCN configuration if the Rerouting procedure is ongoing. + +### 3.1.5.1.1 Generation of the HANDOVER REQUIRED message + +Generation of the HANDOVER REQUIRED message can be for the following reasons: + +- The BSS has detected that a radio reason exists for a handover to occur. +- The MSC has initiated a handover candidate enquiry procedure, and this MS is currently a candidate. +- A cell change is required at call setup due to congestion, e.g. directed retry. +- A cell change is required at call setup if the indication of Service Handover to another RAT has been received from the MSC (directed retry initiation). + +The HANDOVER REQUIRED message contains the following information elements: + +- Message Type. +- Cause. +- Cell Identifier List (preferred). + +It should also contain the information elements: "Current channel type 1", "Old BSS to New BSS information" and, in case the current channel mode is speech, "Speech version (used)". If an IP based user plane interface is supported, the information element "Speech Codec (used)" is included. + +The "Old BSS to New BSS information" is used to pass Field Elements from the old BSS to the new BSS. The information in the "Old BSS to New BSS information" is transparent for the MSC. When the "Old BSS to New BSS information" is present in the HANDOVER REQUIRED message the MSC shall pass it unchanged to any BSS associated to "Cell Identifier List (preferred)" when initiating the Handover resource allocation procedure. The old BSS must ensure that the information contained in the "Old BSS to New BSS information" information element is valid for all cells in the "Cell Identifier List (preferred)". + +Sub-clause 3.2.1.9 gives coding details of the above message. + +The "Cause" field indicates the reason for the HANDOVER REQUIRED message e.g. "uplink quality poor" or "response to MSC invocation" in the case of traffic reasons indicated by the MSC. + +The Cause value sent should be an indication which can be taken into account at the target BSS in future handover decision processes, e.g. to reduce oscillations between BSSs due to the fact that some information (on which the old BSS decided to initiate the handover) is not available at the target BSS (e.g. distance, traffic...). + +If present the "Response Request" Information Element indicates, that the BSS requires an indication if the HANDOVER REQUIRED message does not result in a HANDOVER COMMAND message. + +If the BSS wants to change the CIC due to a channel change, the BSS sends a HANDOVER REQUIRED message with the cause "switch circuit pool" and the "circuit pool list" information element. The "circuit pool list" information element will allow the BSS to indicate to the MSC from which circuit pool or pools the new CIC should be chosen. + +Except in the case of DTM Handover, the "Cell Identifier List (preferred)" shall identify "n" preferred cells. The identified cells are given in order of preference. The algorithm by which the BSS produces this list is Operator dependent and is not addressed in the present document. The "n" number of preferred cells is a parameter set by O&M and shall range from 1 to 16. If "n" number of cells cannot be identified, then only as many as are available shall be encoded and sent (as specified in sub-clause 3.2.2.27). If a LSA information element has been received for a mobile subscriber indicating LSA only access, the "Cell Identifier List" shall contain only cells that are allowed for the subscriber. Exclusive access cells are included into the "Cell Identifier List (preferred)" only if they are allowed for the subscriber or if the connection is an emergency call. + +It is mandatory for the BSS to be able to produce this "Cell Identifier List (preferred)". The sending of this list is controlled by the O&M parameter "n". It is mandatory for the MSC to be able to receive and interpret this Information Element. + +For the case of DTM Handover (i.e. where both dedicated and packet resources are required in the target cell), the "Cell Identifier List (preferred)" shall identify a single cell, which is the same as the cell identified in the corresponding PS-HANDOVER-REQUIRED PDU (see 3GPP TS 48.018). + +The BSS may recommend to the MSC to allow queuing or not in the handover resource allocation procedure by indication in the "Queuing indicator" information element within the HANDOVER REQUIRED message. + +The old BSS may inform the new BSS of the presently configured channel in the Current Channel Type 1 information element and in the Current Channel type 2 Field Element. The information contained may be used by the new BSS (e.g. when building the radio interface HANDOVER COMMAND message). Where discrepancies occur between the Current Channel Type 1 and the Current Channel Type 2 then the information in the Current Channel Type 2 shall take precedence if understood by the new BSS. + +If, for this mobile station, the old BSS has received a Gb interface SUSPEND ACK PDU, then the old BSS shall include the GPRS Suspend information field in the Old BSS to New BSS IE in the HANDOVER REQUIRED message. + +If the old BSS received a GPRS Suspend information field in the Old BSS to New BSS IE in any preceding HANDOVER REQUEST message received by the old BSS, then, the old BSS shall include the GPRS Suspend information field in the Old BSS to New BSS IE in the HANDOVER REQUIRED message. + +The old BSS may recommend to the new BSS to allow pre-emption or not allow pre-emption by sending the "prec" bit. The new BSS may take this information into account when performing the Handover resource allocation procedure. + +The old BSS may inform the new BSS of radio information pertaining to the target cell in the "Target cell radio information" field element. The old BSS shall only send the "Target cell radio information" field element when it sends a single cell in the "Cell Identifier List (preferred)". This field element may be used by the new BSS (e.g. for radio channel selection). + +NOTE 1: It is not recommended that this information element is included if more than one cell is sent in the "Cell Identifier List (preferred)". + +The old BSS may inform the new BSS of the presently configured channel in the Current Channel Type 1 information element and in the Current Channel type 2 Field Element. The information contained may be used by the new BSS (e.g. when building the radio interface HANDOVER COMMAND message). Where discrepancies occur between the Current Channel Type 1 and the Current Channel Type 2 then the information in the Current Channel Type 2 shall take precedence if understood by the new BSS. + +If the present speech codec is a multi-rate speech codec, the old BSS may inform the new BSS of the current multi-rate codec configuration by including the MultiRate configuration information Field Element in the "Old BSS to New BSS information" information element. If the new BSS assigns a multi-rate speech codec this information may be used by the new BSS, to determine whether or not to include a MultiRate Configuration IE when building the radio interface HANDOVER COMMAND message. If an IP based user plane interface is supported in BSS, the "Speech Codec (used)" shall be included in the HANDOVER REQUIRED message. The MSC determines the speech Codec Type and Codec Configuration and informs the target BSS by the "Codec List (MSC Preferred)". + +The old BSS shall inform the new BSS of the MS's last used E-UTRAN PLMN in the "*Last used E-UTRAN PLMN ID*" information element included in the "*Old BSS to New BSS information*" Information Element if this information is present. + +If the old BSS supports dual transfer mode and the mobile station is in dual transfer mode in the old cell, the old BSS may provide information about the current resources by including the *Dual Transfer Mode information* field element in the "*Old BSS to New BSS information*" Information Element. The new BSS may use this information to determine the resources for the mobile station in the new cell (e.g. half rate traffic channel, adjacent resources available, EGPRS-capable resource). + +For the DTM Handover procedure, the old BSS shall include the *PS Indication* information element within the "*Old BSS to New BSS Information*" Information Element. The contents of the *PS Indication IE* shall uniquely identify, for this MS, the handover attempt, and shall be identical to the contents of the *CS Indication IE* included in the PS-HANDOVER-REQUIRED PDU (see 3GPP TS 48.018). + +The old BSS may provide information about the traffic load of the old cell by including the *Downlink Cell Load Information* and/or the *Uplink Cell Load Information* field elements in the "*Old BSS to New BSS information*" Information Element. This information shall represent the current traffic load in the cell, that is, prior to the handover procedure. The new BSS may use the information: + +- prior to a cell load based handover procedure, to determine whether or not to initiate the handover procedure; and + +- in any handover procedure, to update in the new BSS the information about the load on the old cell, which may be used in the initiation of future handover procedures. + +NOTE 2: The old BSS should not initiate a cell load based handover procedure if it has knowledge of the load in the target cell and, after a successful completion of the handover procedure, this load would be higher than in the old cell. + +In case of handover of a VGCS talking subscriber, the BSS may provide information about the current VGCS talker mode (ie dedicated or group transmit) if the group call is ciphered. + +The old BSS may recommend the new BSS not to attempt handovers of this mobile station to UMTS by sending the "UE-prob" bit. The new BSS may take this information into account before starting an Inter-System Handover Required Indication procedure towards UMTS. + +Except when sent as part of a DTM Handover procedure, the HANDOVER REQUIRED message shall be updated and repeated by the BSS with a periodicity of T7 until: + +- A HANDOVER COMMAND message is received from the MSC; or +- A RESET message is received; or +- The reason for the original HANDOVER REQUIRED message disappears e.g. the MS transmission improves; or +- All communication is lost with the MS as defined in 3GPP TS 24.008, and the transaction is abandoned; or +- The transaction ends, e.g. call clearing. + +On sending the HANDOVER REQUIRED message as part of a DTM Handover procedure, the old BSS shall start timer T23. + +The old BSS shall stop timer T23 when it has received responses from both the MSC and the SGSN: + +- from the MSC, a response consisting of either a HANDOVER REQUIRED REJECT or a BSSMAP HANDOVER COMMAND message; and, +- from the SGSN, a response consisting of either a PS-HANDOVER-REQUIRED-ACK PDU or a PS-HANDOVER-REQUIRED-NACK PDU. + +The old BSS shall stop timer T23 if it receives from the MSC a BSSMAP HANDOVER COMMAND message containing a (RR) HANDOVER COMMAND message and chooses to proceed with the handover of the dedicated resource only or if it receives from the MSC a BSSMAP HANDOVER COMMAND message containing an (RLC/MAC) DTM HANDOVER COMMAND message and chooses to begin transmission of the radio interface message to the MS without first waiting for the PS-HANDOVER-REQUIRED-ACK PDU (see sub-clause 3.1.5.3.1). + +### 3.1.5.1.2 Abnormal conditions for DTM Handover + +If timer T23 expires, no message shall be sent to the MS. The subsequent action by the old BSS depends on the messages received prior to the expiry of T23 relating to this handover attempt: + +- If the old BSS has received a PS-HANDOVER-REQUIRED-ACK PDU, it shall initiate a PS Handover Cancel procedure (see 3GPP TS 48.018). +- If the old BSS has received a BSSMAP HANDOVER COMMAND message it shall send a HANDOVER FAILURE message to the MSC with cause "DTM Handover - Timer Expired". +- If the old BSS has received neither a BSSMAP HANDOVER COMMAND message nor a PS-HANDOVER-REQUIRED-ACK PDU, then the handover procedure is terminated and no message is sent to either the MSC or the SGSN. +- Any message or PDU relating to this handover attempt which is received from the MSC or the SGSN after the expiry of timer T23 is discarded. + +If the old BSS receives a PS-HANDOVER-REQUIRED-NACK PDU and a HANDOVER REQUIRED REJECT message then the DTM Handover procedure is terminated and no message shall be sent to either the MSC or the SGSN or the MS. + +If the old BSS receives a PS-HANDOVER-REQUIRED-NACK PDU (with cause e.g. "Equipment Failure") and a BSSMAP HANDOVER COMMAND message which contains a *DTM Handover Command Indication* field element within the *New BSS to Old BSS Information* IE then the old BSS shall send a HANDOVER FAILURE message to the MSC with cause "DTM Handover - SGSN failure". No message shall be sent to the MS. + +If the old BSS receives a PS-HANDOVER-REQUIRED-NACK PDU (with cause e.g. "DTM Handover - PS Allocation Failure") and a BSSMAP HANDOVER COMMAND message which does not contain a *DTM Handover Command Indication* field element within the *New BSS to Old BSS Information* IE and the old BSS has chosen not to proceed with Handover Execution, then the BSS shall send a HANDOVER FAILURE message to the MSC with cause "DTM Handover - PS Allocation Failure". No message shall be sent to the MS. + +If the old BSS receives a PS-HANDOVER-REQUIRED-ACK PDU and a HANDOVER REQUIRED REJECT message then the BSS shall initiate a PS Handover Cancel procedure (see 3GPP TS 48.018). No message shall be sent to the MS. + +### 3.1.5.2 Handover Resource allocation + +This procedure has been defined to allow the MSC to request resources from a BSS in a manner similar to that used for the assignment case. However it does not result in the transmission of any messages over the radio interface, only in the reservation of the resource(s) identified at the BSS, which awaits access of a MS on the reserved channel(s). These reserved resources are then indicated back to the MSC. + +In order to support this procedure the MSC sets up a BSSAP SCCP connection to the BSS. This connection is then used to support all BSSAP messages related to the dedicated resource(s). + +In case of Voice Group Call, the MSC may reuse the existing Resource Controlling SCCP connection which has been previously set-up with the new BSS. + +#### 3.1.5.2.1 Operation of the procedure + +The correct operation of the handover resource allocation procedure is as follows: + +The MSC sends a HANDOVER REQUEST message to the new BSS (note) from which it requires radio resources. This message contains details of the resource(s) required. If the MSC allocates the A interface circuits, and if the requested resource(s) is/are for speech or data the message also indicates the terrestrial resource that shall be used between the MSC and the BSS. The MSC should only ever ask for resources from the BSS that it knows are not totally incompatible with the nominated circuit. The type of channel(s) required can be different from the type of channel(s) in use, e.g. in the case of directed retry. The description of the resource(s) can either be a complete specification, or give the BSS some freedom in the selection (for instance channel rate selection, speech version selection etc.). The message may also specify the channel(s) in use, and, in case current channel mode is speech, the speech version used. If an IP based user plane interface is supported, the "Codec List (MSC Preferred)" shall be included in the message. + +In case of Voice Group Call, the MSC need not allocate a new A interface circuit. In such a case, the terrestrial resource which has been allocated during the VBS/VGCS assignment procedure is used as the new terrestrial resource. The MSC shall not send a HANDOVER REQUEST message to the BSS to handover a VGCS talker to a cell that has been reported as released through the VGCS/VBS ASSIGNMENT STATUS message for that group call. + +On receipt of this message the new BSS shall choose suitable idle radio resources and, if the BSS allocates the A interface circuits and if needed, a terrestrial resource. + +In case of Voice Group Call, the new BSS need not allocate new radio resources. In such a case, the radio resource which has been allocated during the VBS/VGCS assignment procedure is used as the new radio resource. + +The management of priority levels - relating to the Information Element "Priority" within the HANDOVER REQUEST message - is implementation dependent, under operator control. + +If queuing is managed, new requests which cannot be served immediately are put in the queuing file according to the indicated priority levels. + +(Refer to sub-clause 3.1.17 for Queuing Procedure.) + +As a further operator option, the pre-emption indicators may (alone or along with the priority levels) be used to manage the pre-emption process, which may lead to the forced release or forced handover of lower priority connections. + +However, the pre-emption indicators (refer to sub-clause 3.2.2.18), if given in the HANDOVER REQUEST, shall be treated on a per connection basis as follows: + +- The last received "Pre-emption Vulnerability" indicator and priority levels shall prevail. +- If the "Pre-emption Capability" bit is set to 1, then this allocation request can trigger the running of the pre-emption procedure. +- If the "Pre-emption Recommendation" bit indicates that pre-emption is recommended by the old BSS, then the new BSS may obey the recommendation and act appropriately based on "Pre-emption Capability Indication" bit. +- If the "Pre-emption Recommendation" bit indicates that pre-emption is not recommended by the old BSS, then the new BSS may obey this recommendation and ignore the "Pre-emption Capability" bit if it is set to 1. +- If the "Pre-emption Recommendation" bit is not present then the pre-emption procedure can be run. +- If the "Pre-emption Capability" bit is set to 0, then this allocation request cannot trigger the pre-emption procedure. +- If the "Pre-emption Vulnerability" bit is set to 1, then this connection is vulnerable and shall be included in the pre-emption process or procedure and as such may be subject to forced release or forced handover. +- If the "Pre-emption Vulnerability" bit is set to 0, then this connection is not vulnerable to pre-emption and shall not be included in the pre-emption process and as such may not be subject to forced release or forced handover. +- If no Priority Information Element has been received, both "Pre-emption Capability" and "Pre-emption Vulnerability" bits shall be regarded as set to 0. + +In the case where localised service area is supported, the MSC may inform the BSS as to which LSA identities that the mobile has preferences by sending the LSA INFORMATION message. The BSS stores this information and uses it when determining the target cell list for handover. The algorithm for determining the target cell list for handover is not defined further in the present document. + +In the case where Intersystem handover to other RATs is supported, the MSC may inform the target BSS, if preference for other radio access technologies (Service based handover) shall be applied to the MS connection. In such cases the MSC sets the Service Handover Information Element accordingly in the HANDOVER REQUEST message. The Service Handover information is stored in the BSS throughout the connection and is used in Handover evaluation process. + +If the MSC determines that CS to PS SRVCC is allowed for this particular connection, the MSC includes the CS to PS SRVCC IE in the HANDOVER REQUEST message. + +Upon reception of a HANDOVER REQUEST message including the CS to PS SRVCC IE, the BSS may trigger the CS to PS SRVCC procedure (see 3GPP TS 44.018) according to the reported capabilities of the MS. + +Upon reception of a HANDOVER REQUEST message containing a *PS Indication* IE within the *Old BSS to New BSS Information* information element (i.e. a DTM Handover procedure is ongoing), then the new BSS shall proceed as follows: + +- If timer T24 is not running, then the new BSS shall start timer T24. +- When a HANDOVER REQUEST message and PS-HANDOVER-REQUEST PDU have been received and the contents of the *PS Indication* and *CS Indication* IEs are identical, the new BSS shall stop timer T24 and attempt to allocate a dedicated resource and, conditional on the allocation of a the dedicated resource, packet resources (see 3GPP TS 48.018) in accordance with the capabilities of the MS. + +If a dedicated radio resource is available then this will be reflected back to the MSC in a HANDOVER REQUEST ACKNOWLEDGE message. If the MSC gave the BSS some freedom in resource type selection, the choices made by the BSS are indicated in the HANDOVER REQUEST ACKNOWLEDGE message. If the BSS allocates the A interface circuits and such a circuit is needed, the circuit allocated by the BSS is indicated in the HANDOVER ACKNOWLEDGE message. + +If only dedicated resources are allocated, the HANDOVER REQUEST ACKNOWLEDGE message sent by the new BSS shall contain the radio interface message HANDOVER COMMAND within its "Layer 3 Information" Information Element. + +If, in the case of DTM Handover, both dedicated and packet resources are allocated, the HANDOVER REQUEST ACKNOWLEDGE message sent by the new BSS shall contain the radio interface message DTM HANDOVER COMMAND within its "Layer 3 Information" Information Element. + +The "Layer 3 Information" (which is in fact either a RR-Layer 3 HANDOVER COMMAND or a RLC/MAC-Layer 2 DTM HANDOVER COMMAND) is transferred by the controlling MSC to the old BSS using the BSSMAP message HANDOVER COMMAND also within the Information Element "Layer 3 Information" of that BSSMAP message. The new BSS shall indicate that the *Layer 3 Information* IE contains an RLC/MAC DTM HANDOVER COMMAND by including the *DTM Handover Command Indication* field element within the *New BSS to Old BSS Information* IE. + +Information about the appropriate new channels and a handover reference number chosen by the new BSS are contained in the HANDOVER COMMAND or DTM HANDOVER COMMAND. Knowledge of the channel in use at the old BSS allows the new BSS to minimize the size of the HANDOVER COMMAND or DTM HANDOVER COMMAND message (i.e. to decide whether the mode of the first channel IE need not be included in the HANDOVER COMMAND). Furthermore, in the case of handover of a VGCS talking subscriber, knowledge of the VGCS talker mode at the old BSS also allows the new BSS to optimise the size of the HANDOVER COMMAND message. + +NOTE 1: The new BSS and the old BSS may be the same. If an IP based user plane interface is supported, this procedure can not be used when the target BSS and serving BSS are the same. + +In the case of external handover the BSS, when localised service area is supported, will indicate the LSA identity of the target cell in the HANDOVER REQUEST ACKNOWLEDGE message if it corresponds to one of the LSA identities received in the HANDOVER REQUEST message. + +When several circuit pools are present on the BSS MSC interface, and a circuit has been allocated by the HANDOVER REQUEST message, the "circuit pool" information field shall be included in the HANDOVER REQUEST ACKNOWLEDGE. The "circuit pool" field will indicate to the MSC the circuit pool of the CIC given in the HANDOVER REQUEST message. + +In the case of a handover from *A/Gb mode* to *A/Gb mode*, the *New BSS to Old BSS Information* information element is used to pass Field Elements from the new BSS to the old BSS. The information in the *New BSS to Old BSS information* information element is transparent for the MSC. When the *New BSS to Old BSS information* information element is present in the HANDOVER REQUEST ACKNOWLEDGE message, the MSC may pass it to the old BSS when initiating the Handover Execution procedure. + +In the case of a handover from *Iu mode* (GERAN or UTRAN) to *A/Gb mode*, the *Inter-System Information* information element is used to pass Field Elements from the new BSS to the old system. The information in the *Inter-System Information* information element is transparent for the MSC. When the *Inter-System Information* information element is present in the HANDOVER REQUEST ACKNOWLEDGE message, the MSC may pass it to the old system. + +The new BSS may provide information about the traffic load of the target cell by including the *Downlink Cell Load Information* and/or the *Uplink Cell Load Information* field elements in the *New BSS to Old BSS information* or in the *Inter-System Information* information elements. This information shall represent the traffic load in the cell assuming a successful completion of the handover procedure in progress. The old BSS may use the information to update the information about the load on the new cell, which may be used in the initiation of future cell load based handover procedures. + +If local switching is requested by the core network, the MSC includes the Global Call Reference IE, LCLS-Configuration IE and the LCLS-Connection-Status-Control IE in the HANDOVER REQUEST message. + +If the BSS supports Local Call Local Switch (LCLS) and receives the HANDOVER REQUEST message containing the Global Call Reference IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE, then the BSS shall store the Global Call Reference (GCR) value and check if the requested LCLS configuration included in the LCLS-Configuration IE is supported. + +- If the requested LCLS configuration is not supported, then the BSS shall indicate this to the MSC in the LCLS-BSS-Status IE included in the HANDOVER REQUEST ACKNOWLEDGE message, see sub-clause 3.1.33.2.3. +- If the BSS supports the requested LCLS configuration, then the BSS shall perform call leg correlation as described in sub-clause 3.1.33.2.1 and report the outcome to the MSC in LCLS-BSS-Status IE included in the HANDOVER REQUEST ACKNOWLEDGE message. +- If the call becomes local, then the BSS shall notify the MSC serving the other call leg, see sub-clause 3.1.33.5. + +NOTE 2: The BSS shall during the handover procedure indicate the final LCLS connection status value within the HANDOVER COMPLETE message, see sub-clause 3.1.5.3.1. + +NOTE 3: If the BSS does not support LCLS then the Global Call Reference IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE in the HANDOVER REQUEST message will be ignored by the BSS and no LCLS-BSS-Status IE will be returned in the HANDOVER REQUEST ACKNOWLEDGE message and in the HANDOVER COMPLETE message. + +If the target BSS supports DTM and network sharing and the Classmark Type 3 IE received in the HANDOVER REQUEST message indicates a MS supporting network sharing and DTM, then the new BSS shall include the PLMN Index (see 3GPP TS 44.018) corresponding to the PLMN received in the Cell Identifier (Target) IE in the HANDOVER REQUEST message either in the HANDOVER COMMAND or DTM HANDOVER COMMAND message if DTM handover procedure is used (see 3GPP TS 44.018). + +The sending of the HANDOVER REQUEST ACKNOWLEDGE by the new BSS to the MSC ends the Handover Resource Allocation procedure. The Handover Execution procedure can now proceed and this is given in sub-clause 3.1.5.3. + +The new BSS shall then take all necessary action to allow the MS to access the radio resource(s) that the new BSS has chosen, this is detailed in the 3GPP TS 45 series of Technical Specifications. If the radio resource(s) is a traffic channel or a group of traffic channels, then the new BSS shall at this point switch it through to the terrestrial resource indicated in the HANDOVER REQUEST message, and the necessary transcoding/rate adaption/encryption equipment enabled as detailed in 3GPP TS 24.008. + +The optimum procedure for switching through to the target cell at the MSC is not defined in these Technical Specifications. + +If either: + +- a CLEAR COMMAND is received from the MSC; or +- a reset is received from the MSC, + +then the Handover Resource Allocation procedure shall be cancelled and the possibly already allocated radio resources shall be released and the terrestrial resources marked as idle. + +### 3.1.5.2.2 Handover Resource Allocation Failure + +The following failure conditions of this procedure may occur: + +The BSS may not be able to use the terrestrial resource (that is, a terrestrial circuit or an IP based user plane interface) that the MSC has indicated in which case a HANDOVER FAILURE message will be returned with the Cause value set to: "requested terrestrial resource unavailable". + +The BSS may not be able to support the requested ciphering algorithm and in this case a HANDOVER FAILURE message shall be returned to the MSC with the Cause value "Ciphering algorithm not supported". + +If the requested channel type or resource (e.g. channel rate, speech version, Codec Type, Codec Configuration, Interface Type, etc.) indicated in the HANDOVER REQUEST message is temporarily not available (e.g. due to overload) or not supported in the BSS, then a HANDOVER FAILURE message shall be returned to the MSC. The appropriate failure cause will be included in the message (Cause value: "requested transcoding/rate adaptation unavailable" or "requested speech version unavailable" or "Requested Codec Type or Codec Configuration unavailable" or "Requested Codec Type or Codec Configuration not supported" or "Requested A-Interface Type unavailable" or "Requested A-Interface Type not supported"). + +If the MSC requested an IP-bearer for the A-Interface by providing the AoIP Transport Layer Address and not providing a Circuit Identity Code, but the BSS is not able to use an IP-bearer, then the BSS shall not allocate a Circuit Identity Code on its own, even if the Codec List (MSC Preferred) included a Codec Type with the PT bit set to "1", but shall return a HANDOVER FAILURE message to the MSC with the Cause value "Requested A-Interface Type unavailable". + +If, on reception of the HANDOVER REQUEST by the BSS, the circuit pool implied by the CIC information element is incompatible with the channel type indicated (that is, the pool does not support any of the radio resources indicated by the channel type) a HANDOVER FAILURE shall be returned to the MSC with the failure cause set to "circuit pool mismatch". + +If, on reception of the HANDOVER REQUEST by the BSS, the circuit pool implied by the CIC is compatible with the channel type indicated (that is, the pool supports at least one of the radio resource types indicated by the channel type), but the BSS still wishes to change the circuit pool, it sends a HANDOVER FAILURE with the cause "switch circuit pool" and the "circuit pool list" information element. + +The "circuit pool" information element, when present in the HANDOVER FAILURE, indicates to the MSC which circuit pool the CIC indicated in the HANDOVER REQUEST belongs to. This can be used by the MSC to correct its tables (CIC/circuit pool). The "circuit pool list" information element, when present in the HANDOVER FAILURE, is used when the BSS wishes to indicate to the MSC its preferred circuit pools. The circuit pools in the "circuit pool list" information element shall be given in order of preference. In the case of a HANDOVER FAILURE with the cause "circuit pool mismatch", the MSC may decide to block the circuit and to send an O & M notification. + +Other possible cause values which may be returned with the HANDOVER FAILURE message are: "equipment failure", "no radio resource available", "O&M intervention". + +The MSC may not be able to use the terrestrial resource that the BSS has indicated. In this case, the procedure is nevertheless considered terminated successfully, and it is up to the MSC to correct the situation, e.g. by a circuit re-selection procedure. + +If a DTM Handover is ongoing and the allocation of the packet resources fails (i.e. the PS Handover Request procedure (see 3GPP TS 48.018) fails at the new BSS), then the new BSS shall send a PS-HANDOVER-REQUEST-NACK PDU with cause "DTM Handover - PS Allocation failure" to the SGSN (see 3GPP TS 48.018) and either terminate the Handover Resource Allocation procedure and send a HANDOVER FAILURE message with cause "DTM Handover - PS Allocation failure" to the MSC, or proceed with the Handover Resource Allocation procedure allocating only a dedicated resource (see sub-clause 3.1.5.2.3). + +If a DTM Handover is ongoing, then a failure in the allocation of the dedicated resource for any of the reasons described above shall implicitly cause the allocation of PS resources as part of the corresponding PS Handover Request procedure to fail in the new BSS (see 3GPP TS 48.018). In this case the new BSS shall terminate the Handover Resource Allocation procedure by sending a HANDOVER FAILURE message (with appropriate cause e.g. "No radio resource available") to the MSC and a PS-HANDOVER-REQUEST-NACK PDU with cause "DTM Handover - No CS Resource" to the SGSN (see 3GPP TS 48.018). + +The *New BSS to Old BSS information* information element is used to pass Field Elements from the new BSS to the old BSS. The information in the *New BSS to Old BSS information* information element is transparent for the MSC. When the *New BSS to Old BSS information* information element is present in the HANDOVER FAILURE message, the MSC may pass it to the old BSS in the HANDOVER REQUIRED REJECT message. + +The new BSS may provide information about the traffic load of the target cell by including the *Downlink Cell Load Information* and/or the *Uplink Cell Load Information* field elements in the *New BSS to Old BSS information* information element. This information shall represent the current traffic load in the cell. The old BSS may use the information to update the information about the load on the new cell, which may be used in the initiation of future cell load based handover procedures. + +NOTE: The new BSS may reject the attempt of a cell load based handover procedure if the load in the target cell after a successful completion of the handover procedure would be higher than in the old cell. + +The generation of the HANDOVER FAILURE message terminates the procedure and allows all references in the new BSS to be released. + +Further actions in the MSC concerning handover depend upon the handover algorithm which is operator dependent. If an unrecognised Handover Failure cause value is received, the Class of the cause value should be used to determine the MSC's action. + +### 3.1.5.2.3 Abnormal conditions + +If after receipt of a HANDOVER REQUEST message, the new BSS receives another HANDOVER REQUEST message on the same SCCP connection, then the later message will be discarded. + +If the BSS receives a HANDOVER REQUEST message allocating a terrestrial circuit which the BSS has marked as blocked by a previous blocking procedure, then a HANDOVER FAILURE message shall be returned to the MSC with the Cause set to "requested terrestrial resource unavailable". A single global BLOCK message (not repeated and not guarded by timer T1) shall be sent for that concerned terrestrial circuit. + +If the BSS receives a HANDOVER REQUEST message indicating a target cell which is not controlled by the BSS, then a HANDOVER FAILURE message shall be returned to the MSC with the cause set to "invalid cell". + +If timer T24 expires and the new BSS has received a HANDOVER REQUEST message (i.e. no corresponding PS HANDOVER REQUEST PDU has been received), the new BSS may either abort the Handover Resource Allocation procedure by sending a HANDOVER FAILURE message to the MSC with cause "DTM Handover - Timer Expiry", or continue with the Handover Resource Allocation procedure, allocating only a dedicated resource. In the latter case, the new BSS sends a HANDOVER REQUEST ACKNOWLEDGE message to the MSC with the *Layer 3 Information IE* containing an RR HANDOVER COMMAND message, does not include the *DTM Handover Command Indication* field element within the *New BSS to Old BSS Information IE* and no longer considers the DTM Handover procedure to be ongoing. In either case, the new BSS shall store the contents of the *PS Indication IE* and the identity of the MS. + +If timer T24 expires and the new BSS has received a PS HANDOVER REQUEST PDU (i.e. no corresponding HANDOVER REQUEST message has been received), the ongoing PS Handover Request procedure implicitly fails and the new BSS shall send a PS-HANDOVER-REQUEST-NACK PDU to the SGSN with cause "DTM Handover - Timer expiry" (see 3GPP TS 48.018). If the new BSS receives a HANDOVER REQUEST containing a *PS Indication IE* which corresponds to a handover procedure which has previously been terminated due to the expiry of timer T24, then it shall send a HANDOVER FAILURE message to the MSC with cause "DTM Handover - Invalid PS Indication". Any ongoing Handover Resource Allocation procedure corresponding to the same mobile station (i.e. one identified by a different PS Indication Contents in the *PS Indication IE*) should continue. + +### 3.1.5.3 Handover execution + +If a DTM Handover procedure is not ongoing, handover execution in the context of the BSS/MSC interface is the process whereby an MSC instructs an MS to tune to a new dedicated radio resource or to a group of radio resources, which may be on a different cell. + +If a DTM Handover procedure is ongoing, then Handover Execution is the process whereby the radio interface DTM HANDOVER COMMAND message is transmitted to the MS by the old BSS. + +#### 3.1.5.3.1 Operation of the procedure + +The correct operation of the procedure is as follows: + +The BSSMAP HANDOVER COMMAND message is generated by the MSC and transmitted over the BSSAP connection to the old BSS which is currently supporting the concerned MS. + +Except in the case of DTM Handover, the radio interface HANDOVER COMMAND message is sent by the old BSS, to the concerned MS once the old BSS has received the BSSMAP HANDOVER COMMAND message. + +If, in the case of DTM Handover, the old BSS receives from the MSC a BSSMAP HANDOVER COMMAND message and the *DTM Handover Command Indication* field element is included within the *New BSS to Old BSS Information IE*, the old BSS should wait until it receives a PS-HANDOVER-REQUIRED-ACK PDU (if it has not already), then stop timer T23 and transmit the (RLC/MAC) DTM HANDOVER COMMAND radio interface message to the MS (see 3GPP TS 44.060). Alternatively, the old BSS may transmit the (RLC/MAC) DTM HANDOVER COMMAND and stop timer T23 without waiting for a PS-HANDOVER-REQUIRED-ACK PDU. If, in this case, the old BSS subsequently receives a PS-HANDOVER-REQUIRED-NACK PDU before it has completed transmission of the (RLC/MAC) DTM HANDOVER COMMAND message it should abort the transmission of the message and proceed as described in sub-clause 3.1.5.1.2. + +If, in the case of DTM Handover, the old BSS receives from the MSC a BSSMAP HANDOVER COMMAND message and the *DTM Handover Command Indication* field element is not included within the *New BSS to Old BSS Information IE* and the old BSS chooses to proceed with the Handover Execution procedure, it shall stop T23 and send the RR HANDOVER COMMAND message to the MS. + +NOTE: If the old BSS chooses not to proceed with the Handover Execution in this case, then it shall proceed as specified in sub-clause 3.1.5.1.2. + +In the case of DTM Handover, the old BSS shall start timer T8 when it sends the DTM HANDOVER COMMAND (or RR HANDOVER COMMAND message, if it proceeds with the Handover Execution procedure when only a dedicated resource was allocated) to the mobile. Otherwise, the old BSS shall start timer T8 on receipt of the BSSMAP HANDOVER COMMAND message. + +The air interface message (either DTM HANDOVER COMMAND or RR HANDOVER COMMAND) contains a handover reference number, previously allocated by the new BSS. + +The BSSMAP HANDOVER COMMAND message generated by the MSC may contain a *Cell Identifier* IE which indicates to the old BSS the target cell identity to which the handover is to be performed. In case of failure, this information allows the old BSS to know on which cell the handover failed. + +The BSSMAP HANDOVER COMMAND message may contain information about the traffic load of the new cell by including the *Downlink Cell Load Information* and/or the *Uplink Cell Load Information* field elements in the *New BSS to Old BSS information* information element. The old BSS may use the information to update the information about the load on the new cell, which may be used in the initiation of future cell load based handover procedures. + +When the MS accesses the radio resource(s) of the new BSS with a HANDOVER ACCESS burst which contains the received handover reference number then: + +- The new BSS checks the handover reference number to ensure that it is the same as expected, and hence that there is a high probability that the correct MS has been captured (if the handover reference is not as expected then the new BSS shall wait for an access by the correct MS). +- If the handover reference number is as expected, the new BSS shall send a HANDOVER DETECT message to the MSC. +- When the MS is successfully in communication with the network, i.e. the RR message HANDOVER COMPLETE has been received from the MS, then the new BSS will immediately send a BSSMAP message HANDOVER COMPLETE to the MSC and, in the case of DTM Handover, a PS-HANDOVER-COMPLETE PDU to the SGSN (see 3GPP TS 48.018), and terminate the procedure. + +If LCLS is supported in the BSS and the BSS determines that the call is an intra-BSS call which can be locally switched it shall not through-connect the two parties unless explicitly indicated to do so in the HANDOVER REQUEST message by receiving the LCLS-Connection-Status-Control IE set to "Connect" and the other call leg has previously received LCLS-Connection-Status-Control IE set to "Connect". + +If local switching is requested by the core network and LCLS is supported in the BSS, the BSS shall inform the MSC of the local switch establishment outcome by including the LCLS-BSS-Status IE with the correct LCLS connection status value according to sub-clause 3.2.2.119 within the BSSMAP HANDOVER COMPLETE message. The BSS shall also notify the MSC serving the other call leg if the LCLS connection status is changed for this call leg, see sub-clause 3.1.33.5. + +In the case where the new BSS hands the MS to a Group call channel, the BSS shall send a CLEAR REQUEST with cause "Joined group call channel" directly after having sent the HANDOVER COMPLETE message. + +In the case of point to point calls the MSC shall terminate the procedure with the old BSS by sending a CLEAR COMMAND with cause "Handover successful". + +In the case of a handover from a Group call channel the MSC shall terminate the procedure by sending a HANDOVER SUCCEEDED message. On receipt of a HANDOVER SUCCEEDED from the MSC, the old BSS shall stop timer T8. + +The old dedicated radio resource(s) and connected terrestrial resource shall remain assigned until either the MSC instructs the old BSS to release the resource(s) by a CLEAR COMMAND or a reset occurs. + +After the completion of the handover procedure, until the connection is released or the MSC performs an assignment, any dedicated resource assigned to the mobile station, e.g. at internal handover, must be in accordance with the description in the HANDOVER REQUEST message. + +If either: + +- a CLEAR COMMAND is received from the MSC; or +- a reset is received from the MSC, + +before an MS with the correct handover reference accesses the new BSS then the radio resources shall be released and the terrestrial resources marked as idle + +The relevant radio interface layer 3 procedures are described in 3GPP TS 24.008. + +The MSC always terminates this procedure by use of a clear sequence as follows: + +- The MSC sends a CLEAR COMMAND to the old BSS. On receipt of a CLEAR COMMAND from the MSC the old BSS shall stop timer T8 and release all involved resources that were allocated to the MS that had been handed over and returns a CLEAR COMPLETE message to the MSC. +- On receipt of the CLEAR COMPLETE, the MSC shall initiate the release of the SCCP connection to the old BSS and thereby terminate association with the old BSS for this process. + +### 3.1.5.3.2 Handover Failure + +If a HANDOVER FAILURE message radio interface message is received from the MS on the old (main) channel by the old BSS, the old BSS shall then send to the MSC the BSSMAP HANDOVER FAILURE message and, in the case of DTM Handover, the old BSS shall also start the PS Handover Cancel procedure (see 3GPP TS 48.018). If the radio interface HANDOVER FAILURE message is the result of the MS returning to the old BSS after failing to establish on the new BSS, then the cause value "radio interface failure, reversion to old channel" shall be included in the BSSMAP HANDOVER FAILURE message. Furthermore, it is recommended that the air interface RR cause be included as well in this message. + +If the MSC receives the BSSMAP HANDOVER FAILURE message from the old BSS (with any cause value) and if the target channel is not a Group Call Channel, the handover procedure at the target new BSS is then terminated by the MSC using a clear sequence as follows: + +- The MSC sends a CLEAR COMMAND message with the cause "Radio interface failure, reversion to old channel" to the new BSS. On receipt of a CLEAR COMMAND message from the MSC, the new BSS shall release all involved resources that were allocated during the handover resource allocation procedure and return a CLEAR COMPLETE message to the MSC. +- On receipt of the CLEAR COMPLETE message, the MSC shall initiate the release of the SCCP connection to the new BSS and thereby terminate the association with the new BSS for this process. + +The call between the MS and the old BSS and between the old BSS and the MSC shall continue as if there had been no handover attempt. + +Further actions in the MSC concerning handover depends on the handover algorithm which is operator dependent. + +In the case of a talker on a group call channel the MS may release the uplink whilst the handover is being performed, in this case the old BSS shall cancel the handover internally, the MSC should cancel the handover and initiate the release of the A interface resources allocated in the new BSS. + +### 3.1.5.3.3 Abnormal Conditions + +Whilst the handover execution procedure is in operation, any other messages received at the old BSS relating to this connection and concerning assignment, handover, or cipher mode control should be discarded. + +Whilst the handover execution procedure is in operation the old BSS should not attempt to invoke any other procedure related to this call e.g. handover required indication. + +If at the old BSS a CLEAR COMMAND message from the MSC or a HANDOVER FAILURE message from the MS is not received before the expiry of timer T8 then the old BSS shall release the dedicated radio resources. A BSSMAP message CLEAR REQUEST is also sent to the MSC with a cause "Radio Interface Message Failure". The terrestrial resource in the old BSS shall remain assigned until a CLEAR COMMAND message is received from the MSC, at which point the old BSS shall mark the terrestrial resources as IDLE and return a CLEAR COMPLETE message to the MSC. The MSC shall subsequently release the SCCP connection to the old BSS and thereby terminate association with the old BSS for this process. + +In case DTM Handover is ongoing, if T8 expires, the old BSS shall also release the allocated PS resources and initiate a PS Handover Cancel procedure. The cause value in the PS-HANDOVER-CANCEL PDU shall be set to "Radio contact lost with MS" (see 3GPP TS 48.018). + +In the case of a handover from a Group call channel, if at the old BSS a CLEAR COMMAND or HANDOVER SUCCEEDED message from the MSC or a HANDOVER FAILURE message from the MS is not received before the expiry of timer T8 then the old BSS shall release the uplink and send a UPLINK RELEASE INDICATION to the MSC. + +The MSC shall also initiate release of the resources allocated by the new BSS during the handover resource allocation procedure by sending a CLEAR COMMAND message to the new BSS. The new BSS shall release all the resources that were assigned for that aborted handover and return a CLEAR COMPLETE message to the MSC. The MSC shall + +subsequently release the SCCP connection to the new BSS and thereby terminate association with the new BSS for this process. + +### 3.1.5a Handover from GSM to another System + +Using this protocol the BSS should support handover transitions to other systems from an SDCCH, a Full Rate TCH a Half Rate TCH and Multiple Full Rate TCHs. + +There are three procedures which are used for inter-system handover. They are: + +- Inter-System Handover Required Indication. +- Inter-System Handover Resource Allocation. +- Inter-System Handover Execution. + +The first and part of the third of these procedures are specified in this specification. The second and other part of the third procedures are specified in the relevant specification of the target system. + +For any HANDOVER REQUIRED message at most one HANDOVER COMMAND message may be sent. + +If so required by the BSS, the MSC shall inform the BSS if the handover cannot be carried out. This is done by a HANDOVER REQUIRED REJECT message. + +In the case of inter- MSC handover the term "the MSC" in this sub-clause is taken to mean the relevant MSC in the handover operation. + +The inter-system handover procedures are specified in the following sub-clauses. All messages concerned with inter-system handover are sent using the connection oriented mode of the SCCP. + +#### 3.1.5a.1 Generation of the HANDOVER REQUIRED message for intersystem handover + +The HANDOVER REQUIRED message contains the following information elements: + +- Message Type. +- Cause. +- Cell Identifier List. + +In case of Inter System Handover to UTRAN or CS to PS SRVCC to UTRAN (HSPA) it contains the information element: "Source RNC to target RNC transparent information". + +The "Source RNC to target RNC transparent information" is used to pass information from the old BSS to the target RNC. The information in the "Source RNC to target RNC transparent information" is transparent for the MSC. At presence of the "Source RNC to target RNC transparent information" in the HANDOVER REQUIRED message the MSC shall pass it unchanged to the Target RNC when initiating the Handover resource allocation procedure. The Target RNC is identified by the Target ID information contained in the Cell Identifier List IE. The Target ID information is structured routing information as required by the core network (see 3GPP TS 25.413). The information contained in the "Source RNC to target RNC transparent information" information element is coded as required by the target system. + +In case of CS to PS SRVCC to E-UTRAN it contains the information element "Source eNB to target eNB transparent information (E-UTRAN)" + +The "Source eNB to target eNB transparent information (E-UTRAN)" is used to pass information from the old BSS to the target eNB. The information in the "Source eNB to target eNB transparent information (E-UTRAN)" is transparent for the MSC. When the "Source eNB to target eNB transparent information (E-UTRAN)" is present in the HANDOVER REQUIRED message the MSC shall pass it unchanged to the Target eNB when initiating the Handover resource allocation procedure. The Target eNB is identified by the Corresponding RNC-ID information contained in the Cell Identifier List IE. The Corresponding RNC-ID information is structured routing information as required by the core network (see 3GPP TS 36.413). The information contained in the "Source eNB to target eNB transparent information (E-UTRAN)" information element is coded as required by the target system. + +In case of CS to PS SRVCC to UTRAN (HSPA) or to E-UTRAN, the BSS shall include the *CS to PS SRVCC Indication* IE in the HANDOVER REQUIRED message. + +Sub-clause 3.2.1.9 gives coding details of the above message. + +The "Cause" field indicates the reason for the HANDOVER REQUIRED message e.g. "downlink quality". + +The Cell Identification Discriminator field within the Cell Identifier List IE in the HANDOVER REQUIRED message can be used to deduce that this is an intersystem handover. + +If present the "Response Request" Information Element indicates, that the BSS requires an indication if the HANDOVER REQUIRED message does not result in a HANDOVER COMMAND message. + +The Cell Identifier List IE contains the RNC-ID (or the Extended RNC-ID or the Corresponding RNC-ID) (and additionally the LAC (or TAC) or LAC and PLMN-ID (or TAC and PLMN-ID) depending on the configuration of the network) of the target for intersystem handover. In case of DTM Handover to UTRAN, the RNC-ID (or the Extended RNC-ID) shall be as same as the RNC Identifier specified in the corresponding PS HANDOVER REQUIRED PDU (see 3GPP TS 48.018). + +It is mandatory for BSS to produce the RNC-ID (or the Extended RNC-ID or the Corresponding RNC-ID). It is mandatory for the MSC to be able to receive and interpret this Information Element for routing purpose. + +The BSS may recommend to the target RNC to allow pre-emption or not allow pre-emption by sending the "prec" bit. The target RNC may take this information into account when performing the Handover resource allocation procedure. + +In case of handover to a UTRAN CSG cell or a hybrid cell, the source BSS shall include the *CSG Identifier* information element in the HANDOVER REQUIRED message. The source BSS shall set the value of the *Cell Access Mode* field in the *CSG Identifier* information element according to the information received from the MS through measurement reporting as defined in 3GPP TS 44.018. + +In case of handover to GERAN *Iu mode* the BSS may include the "GERAN Classmark" Information Element, indicating the supported CS services of the target cell in the HANDOVER REQUIRED message (see 3GPP TS 43.051). In case the serving and the target cells provide the same capabilities with regard to CS services the exchange of the "GERAN Classmark" between RAN and CN is not required during the handover procedure. In case the serving and the target cells do not provide the same capabilities with regard to CS services, the exchange of the "GERAN Classmark" between RAN and CN is required during the handover procedure to avoid that the CN has to store cell related information and to be able to reuse the existing handover procedure inside the CN. + +In case of DTM Handover to UTRAN, the old BSS shall set the *Number of Iu Instances* IE equal to 2 in the *Source RNC to Target RNC Transparent Container* IE (see 3GPP TS 25.413) + +The old BSS may provide information about the traffic load of the old cell by including the *Cell Load Information Group* field elements in the *Source RNC to Target RNC Transparent Information* information element. This information shall represent the current traffic load in the cell, that is, prior to the handover procedure. This information shall also include the source cell identifier to which the included traffic load values corresponds. The target RNC may use the information to update the information about the load on the old cell, which may be used in the initiation of future cell load based handover procedures. + +NOTE: The old BSS should not initiate a cell load based handover procedure if it has knowledge of the load in the target cell and, after a successful completion of the handover procedure, this load would be higher than in the old cell. + +Except when sent as part of an intersystem DTM Handover procedure, the HANDOVER REQUIRED message shall be updated and repeated by the BSS with a periodicity of T7 until: + +- A HANDOVER COMMAND message is received from the MSC; or +- A RESET message is received; or +- The reason for the original HANDOVER REQUIRED message disappears e.g. the MS transmission improves; or +- All communication is lost with the MS as defined in 3GPP TS 44.018, and the transaction is abandoned; or +- The transaction ends, e.g. call clearing. + +On sending the HANDOVER REQUIRED message as part of a DTM Handover to UTRAN procedure, the old BSS shall start timer T23. The old BSS shall stop timer T23 as described in sub-clauses 3.1.5.1.1. In case of T23 expiry or the failure of resource allocation, the old BSS shall behave as described in sub-clause 3.1.5.1.2. + +In case of handover to a UTRAN CSG cell, if the MSC receives in the HANDOVER REQUIRED message the *CSG Identifier* IE with the *Cell Access Mode* field set to "CSG cell", it shall perform access control. If the result indicates that the MS is allowed to access the target cell the MSC shall continue the handover to the target side. + +In case of handover to a UTRAN Hybrid cell, if the MSC receives in the HANDOVER REQUIRED message the *CSG Identifier* IE with the *Cell Access Mode* field set to "Hybrid cell", it shall provide the CSG membership status of the MS and the *CSG Id* to the target side. + +### 3.1.5a.2 Inter-System Handover Resource Allocation Failure + +If the MSC receives a HANDOVER REQUIRED message indicating an unknown target RNC or unknown target eNB then, if so required by the BSS, the MSC shall send a HANDOVER REQUIRED REJECT message to the old BSS with a cause value indicating 'invalid cell'. + +If the MSC receives a HANDOVER REQUIRED message with the *CSG Identifier* information element with the *Cell Access Mode* field set to "CSG cell", and the access control indicates that the MS is not allowed to access the target cell, the MSC shall send a HANDOVER REQUIRED REJECT message to the old BSS with a cause value indicating "Invalid CSG cell". + +If the MSC receives a HANDOVER REQUIRED message with the *CS to PS SRVCC Indication* information element present, and the MSC determines that CS to PS SRVCC to E-UTRAN or to UTRAN (HSPA) is not possible, the MSC shall send a HANDOVER REQUIRED REJECT message to the old BSS with an appropriate cause value. + +If the MSC or the target system is unable to allocate resources for the handover attempt then, if so required by the BSS, the MSC shall send a HANDOVER REQUIRED REJECT message to the old BSS with an appropriate cause value. + +If the target system establishes that the mobile station being handed over does not support the inter-system procedure correctly and if so required by the BSC, then the MSC shall send a HANDOVER REQUIRED REJECT message to the old BSS with a cause value indicating 'Incoming Relocation Not Supported Due To PUESBINE Feature'. The old BSS should not attempt further inter-system handovers for this mobile station. + +The *New BSS to Old BSS information* information element is used to pass Field Elements from the new system to the old BSS. The information in the *New BSS to Old BSS information* information element is transparent for the MSC. When the *New BSS to Old BSS information* information element is present in the message received from target RNC, the MSC may pass it to the old BSS in the HANDOVER REQUIRED REJECT message. + +The new BSS may provide information about the traffic load of the target cell by including the *Downlink Cell Load Information* and/or the *Uplink Cell Load Information* field elements in the *New BSS to Old BSS information* information element. This information shall represent the current traffic load in the cell. The old BSS may use the information to update the information about the load on the new cell, which may be used in the initiation of future cell load based handover procedures. + +### 3.1.5a.3 Intersystem handover Execution + +The correct operation of the procedure is as follows: + +The BSSMAP HANDOVER COMMAND message is generated by the MSC and transmitted over the BSSAP connection to the old BSS which is currently supporting the concerned MS. + +If DTM Handover to UTRAN is not ongoing, then the old BSS shall start timer T8 on the receipt of the BSSMAP HANDOVER COMMAND message which contains the Layer 3 Information IE including radio interface handover command message. An intersystem handover command radio interface message (e.g. INTER SYSTEM TO UTRAN HANDOVER COMMAND) is then sent by the old BSS, to the concerned MS. + +In case of DTM Handover to UTRAN, the old BSS shall start timer T8 when it sends the (RLC/MAC) DTM HANDOVER COMMAND message containing a (RRC) HANDOVER TO UTRAN COMMAND message to the concerned MS. + +The BSSMAP HANDOVER COMMAND message may contain information about the traffic load of the new cell by including the *Downlink Cell Load Information* and/or the *Uplink Cell Load Information* field elements in the *New BSS* + +to *Old BSS information* information element. The old BSS may use the information to update the information about the load on the new cell, which may be used in the initiation of future cell load based handover procedures. + +In case of CS to PS SRVCC to E-UTRAN or to UTRAN (HSPA), the old BSS shall start timer T8 on the receipt of the BSSMAP HANDOVER COMMAND message containing the CN to MS transparent information IE. An intersystem handover command radio interface message (e.g. INTER SYSTEM TO UTRAN HANDOVER COMMAND or INTER SYSTEM TO E-UTRAN HANDOVER COMMAND) is then sent by the old BSS, to the concerned MS. + +When the MS accesses the radio resource(s) of the new RNC or the new eNB then: + +- the new RNC or the new eNB shall cause a Handover Detect indication to be sent to the MSC; +- when the MS is successfully in communication with the network, then the new RNC or the new eNB shall cause a Handover Complete indication to be sent to the MSC and terminate the procedure. + +The relevant radio interface layer 3 procedures are described in 3GPP TS 25.331, 3GPP TS 44.018 and 3GPP TS 36.331. + +The MSC always terminates this procedure by use of a clear sequence as follows: + +- The MSC sends a CLEAR COMMAND to the old BSS. On receipt of a CLEAR COMMAND from the MSC the old BSS shall stop timer T8 and release all involved resources that were allocated to the MS that had been handed over and returns a CLEAR COMPLETE message to the MSC. +- On receipt of the CLEAR COMPLETE, the MSC shall initiate the release of the SCCP connection to the old BSS and thereby terminate association with the old BSS for this process. + +### 3.1.5a.4 Inter System Handover Failure + +If a HANDOVER FAILURE radio interface message is received from the MS on the old (main) channel by the old BSS, the old BSS shall then send to the MSC the BSSMAP HANDOVER FAILURE message and in the case of DTM Handover to UTRAN, the old BSS shall also start the PS Handover Cancel procedure (see 3GPP TS 48.018). + +If the radio interface HANDOVER FAILURE message is the result of the MS returning to the old BSS after failing to establish on the new channel in the new RNC or in the new eNB, then the cause value "radio interface failure, reversion to old channel" shall be included in the BSSMAP message HANDOVER FAILURE. Furthermore, it is recommended that the air interface RR cause be included as well in this message. + +If the MSC receives the BSSMAP HANDOVER FAILURE message from the old BSS (with any cause value, the handover procedure at the target is then terminated by the MSC. + +The call between the MS and the old BSS and between the old BSS and the MSC shall continue as if there had been no handover attempt. + +### 3.1.5a.5 Abnormal Conditions + +Whilst the handover execution procedure is in operation, any other messages received at the old BSS relating to this connection and concerning assignment, handover, or cipher mode control should be discarded. + +Whilst the handover execution procedure is in operation the old BSS should not attempt to invoke any other procedure related to this call e.g. handover required indication. + +If at the old BSS a CLEAR COMMAND message from the MSC or a HANDOVER FAILURE message from the MS is not received before the expiry of timer T8 then the old BSS shall release the dedicated radio resources. A BSSMAP message CLEAR REQUEST is also sent to the MSC with a cause "Radio Interface Message Failure". The terrestrial resource in the old BSS shall remain assigned until a CLEAR COMMAND is received from the MSC, at which point the old BSS shall mark the terrestrial resources as IDLE and return a CLEAR COMPLETE message to the MSC. The MSC shall subsequently release the SCCP connection to the old BSS and thereby terminate association with the old BSS for this process. + +In case of DTM Handover to UTRAN is ongoing, if T8 expires, the old BSS shall also release the allocated PS resources and initiate a PS Handover Cancel procedure. The cause value in the PS-HANDOVER-CANCEL PDU shall be set to "Radio contact lost with MS" (see 3GPP TS 48.018). + +In the case of a handover from a Group call channel, if at the old BSS a CLEAR COMMAND or HANDOVER SUCCEEDED message from the MSC or a HANDOVER FAILURE message from the MS is not received before the expiry of timer T8 then the old BSS shall release the uplink and send a UPLINK RELEASE INDICATION to the MSC. + +The MSC shall also initiate release of the resources allocated by the new BSS during the handover resource allocation procedure by sending a CLEAR COMMAND to the new BSS. The new BSS shall release all the resources that were assigned for that aborted handover and return a CLEAR COMPLETE to the MSC. The MSC shall subsequently release the SCCP connection to the new BSS and thereby terminate association with the new BSS for this process. + +In case of CS to PS SRVCC, the MSC shall also initiate release of the resources allocated by the new RNC or by the new eNB during the handover resource allocation procedure by sending a release message to the target system. The new RNC or eNB shall release all the resources that were assigned for that aborted handover and indicate this to the MSC. The MSC shall subsequently release the dedicated connection to the new RNC or the new eNB and thereby terminate the association with the new RNC or eNB for this process. + +### 3.1.5b Handover from another system to GSM + +#### 3.1.5b.1 General + +Using this protocol the BSS should support handover transitions from other systems to an SDCCH, a Full Rate TCH a Half Rate TCH and Multiple Full Rate TCHs. + +There are three procedures which are used for handover from another system to GSM. They are: + +- Inter-System Handover Required Indication. +- Inter-System Handover Resource Allocation. +- Inter-System Handover Execution. + +The second part of these procedures is specified in this specification. The first and third parts procedures are specified in the relevant specification of the source system. + +In the case of inter-MSC handover the term "the MSC" in this sub-clause is taken to mean the relevant MSC in the handover operation. + +The inter-system handover procedures are specified in the following sub-clause. All messages concerned with inter-system handover are sent using the connection oriented mode of the SCCP. + +#### 3.1.5b.2 Inter-System Handover Resource Allocation + +In the case of a handover from *Iu mode* (GERAN or UTRAN) to *A/Gb mode*, the *Inter-System Information* information element is used to pass Field Elements from the new BSS to the old system. The information in the *Inter-System Information* information element is transparent for the MSC. When the *Inter-System Information* information element is present in the HANDOVER REQUEST ACKNOWLEDGE message or the HANDOVER FAILURE message, the MSC may pass it to the old system. + +The new BSS may provide information about the traffic load of the target cell by including the *Downlink Cell Load Information* and/or the *Uplink Cell Load Information* field elements in the *Inter-System Information* information element. The old system may use the information to update the information about the load on the new cell, which may be used in the initiation of future cell load based handover procedures. This information shall represent the traffic load in the cell assuming a successful completion of the handover procedure in progress. + +### 3.1.5c BSS Internal Handover with MSC support + +This section is relevant only if an IP based user plane interface is supported. The three internal handover procedures (Internal Handover Preparation, Internal Handover Execution and Internal Handover Enquiry), described in the following sections, use the existing SCCP connection. + +#### 3.1.5c.1 Internal Handover Preparation + +The details of the radio information as far as handover is concerned are given in 3GPP TS 24.008. + +When the BSS detects that e.g. a radio reason exists for an internal handover, but a compatible Codec Type or Codec Configuration (see 3GPP TS 28.062) can not be allocated in the target cell or the A-Interface Type has to be changed, or the Redundancy Level on the A-Interface of an ongoing data or fax call has to be changed or the Transport Layer Address has to be changed, then an Internal Handover Preparation procedure is initiated by BSS. + +This Internal Handover Preparation is initiated by generating an INTERNAL HANDOVER REQUIRED message and sending it from the BSS to the MSC. + +The INTERNAL HANDOVER REQUIRED message contains the following information elements: + +- Message Type. +- Cause. +- Cell Identifier (target cell) +- Codec List (BSS Supported) (in target cell) +- AoIP Transport Layer Address (target cell), if the BSS prefers an IP-based target A-Interface Type + +The "Cause" field indicates the reason for the INTERNAL HANDOVER REQUIRED message e.g. "uplink quality poor", "Redundancy Level not adequate" indicated by BSS. + +The "Cell Identifier" indicates a target cell controlled by the same BSS. The target cell can be the same as the source cell. + +The "Codec List (BSS Supported)" contains the up-to-date codec capabilities in the target cell. + +The "AoIP Transport Layer Address" contains the UDP/IP termination at the BSS corresponding to the radio channel in the target cell. It is only included, if the BSS prefers an IP-based target A-Interface Type. The new AoIP Transport Layer Address may be identical to the old AoIP Transport Layer Address. + +The Internal Handover Preparation procedure terminates, if one of the following conditions is met: + +- An INTERNAL HANDOVER COMMAND message is received from the MSC; or +- A RESET message (or RESET CIRCUIT message or RESET IP RESOURCE message) is received; or +- An INTERNAL HANDOVER REQUIRED REJECT is received; or +- An ASSIGNMENT REQUEST is received; or +- The Timer T25 expires without any answer from the MSC, or +- All communication is lost with the MS as defined in 3GPP TS 44.018, and the transaction is abandoned; or +- The transaction ends, e.g. due to call clearing. + +If the Internal Handover Execution procedure cannot be carried out, then the MSC shall inform the BSS by sending an INTERNAL HANDOVER REQUIRED REJECT message. + +To continue with the Internal Handover Execution procedure, the MSC generates the INTERNAL HANDOVER COMMAND message as a response to the INTERNAL HANDOVER REQUIRED message. + +The Internal Handover Execution procedure can now proceed and this is given in sub-clause 3.1.5c.2. + +### 3.1.5c.1.1 Internal Handover Required Reject + +If the requested resource (e.g. Codec Type or Codec Configuration, A-Interface Type, etc.) indicated in the INTERNAL HANDOVER REQUIRED message is not available, then an INTERNAL HANDOVER REQUIRED REJECT message shall be returned to the BSS. The appropriate failure cause will be included in the message (Cause value: "Requested Codec Type or Codec Configuration unavailable", "Requested A-Interface Type unavailable", "Requested Codec Type or Codec Configuration not supported" or "Requested A-Interface Type not supported", "Requested Redundancy Level not supported" or "Requested Redundancy Level not available"). + +### 3.1.5c.2 Internal Handover Execution + +The Internal Handover Execution procedure in the context of the BSS/MSC interface is the procedure whereby an MSC instructs an MS to tune to a new dedicated radio resource or to a group of radio resources, which may be on a different cell. + +The MSC generates the INTERNAL HANDOVER COMMAND message as a response to the INTERNAL HANDOVER REQUIRED message. The INTERNAL HANDOVER COMMAND message generated by the MSC shall contain the "Speech Codec (MSC Chosen)" and if an IP based user plane A-Interface is chosen, also the "AoIP Transport Layer Address (MGW)". The "Speech Codec (MSC Chosen)" shall contain one Codec Type (or, in case of AMR-NB or AMR-WB, possibly more compatible Codec Types) included in the "Speech Codec List (BSS Supported)" received in the INTERNAL HANDOVER REQUIRED message, with one Codec Configuration (or the same or compatible Codec Configuration(s) in case of more compatible Codec Types) and with one A-Interface Type, that exactly correspond to the indication in the "Speech Codec List (BSS Supported)". + +If Local Call Local Switch (LCLS) is supported by the core network, the MSC may include the LCLS-Connection-Status-Control IE in the INTERNAL HANDOVER COMMAND message. + +Upon reception of the INTERNAL HANDOVER COMMAND message, the BSS shall only through-connect the two parties if either: + +- indicated to do so in the INTERNAL HANDOVER COMMAND message by receiving the LCLS-Connection-Status-Control IE set to "Connect" and the other call leg has previously received LCLS-Connection-Status-Control IE set to "Connect". +- or the LCLS-Connection-Status-Control IE is not present in the INTERNAL HANDOVER COMMAND message and the BSS previously in another BSSAP message received the LCLS-Connection-Status-Control IE set to "Connect" for this call leg and the other call leg has previously received LCLS-Connection-Status-Control IE set to "Connect". + +The BSS will construct and send the appropriate radio assignment or handover messages, if required (i.e. if the radio resource(s) has/have to be changed), as described in 3GPP TS 44.018. The INTERNAL HANDOVER COMMAND message includes sufficient information to allow the BSS to construct the necessary layer 3 radio messages. + +The radio interface HANDOVER COMMAND or ASSIGNMENT COMMAND message is sent by the BSS to the concerned MS, once the BSS has received the INTERNAL HANDOVER COMMAND message and the remaining resources are allocated in the BSS. + +When the MS accesses the radio resource(s) of the new channel with a HANDOVER ACCESS burst, or anyway as soon as the main signalling link is established then the BSS may send a HANDOVER DETECT message to the MSC. + +When the MS is successfully in communication with the network, i.e. the RR message HANDOVER COMPLETE or ASSIGNMENT COMPLETE has been received from the MS, the BSS shall immediately send a HANDOVER COMPLETE message to the MSC and terminate the procedure. Changes of the chosen encryption algorithm shall be indicated in the HANDOVER COMPLETE message in case of an "Internal Handover Execution" procedure, if the encryption algorithm has been changed by the BSS. The Information Elements "Speech Codec (Chosen)" shall be included in case of an "Internal Handover Execution" procedure. The Information Element "Codec List (BSS Supported)" may be included in case of an "Internal Handover Execution" procedure to indicate up-to-date BSS capabilities after the handover. + +If local switching is requested by the MSC, then the BSS shall inform the MSC of the local switch establishment outcome by including the LCLS-BSS-Status IE with the correct LCLS connection status value according to sub-clause 3.2.2.119 within the HANDOVER COMPLETE message. The BSS shall also notify the MSC serving the other call leg if the LCLS connection status is changed for this call leg, see sub-clause 3.1.33.5. + +The sending of the HANDOVER COMPLETE message will implicitly release the old dedicated resource(s) at the BSS and old resources in the MSC. + +The Internal Handover Execution procedure shall not be interrupted by a Handover Required message. + +The relevant radio interface layer 3 procedures are described in 3GPP TS 24.008. + +### 3.1.5c.2.1 Internal Handover failure + +The BSS may not be able to use the terrestrial resource (that is either a terrestrial circuit or an IP based user plane interface) that the MSC has indicated in the Internal Handover Command. In this case a BSSAP HANDOVER FAILURE message will be returned with the Cause value set to: "requested terrestrial resource unavailable". + +If a radio interface HANDOVER FAILURE message is received from the MS on the old channel, the BSS shall then send to the MSC the BSSMAP HANDOVER FAILURE message. If the radio interface HANDOVER FAILURE message is the result of the MS returning to the old channel after failing to establish on the new channel, then the cause value "radio interface failure, reversion to old channel" shall be included in the BSSMAP HANDOVER FAILURE message. Furthermore, it is recommended that the air interface RR cause be included as well in this message. + +The BSSMAP HANDOVER FAILURE message from the BSS (with any cause value) terminates the Internal Handover Execution procedure. The call between the MS and the BSS and between the BSS and the MSC shall continue as if there had been no handover attempt. + +Further actions in the MSC or in the BSS concerning handover depend on the handover algorithms which is operator dependent. + +### 3.1.5c.2.2 Abnormal Conditions + +Whilst the Internal Handover Execution procedure is in operation, any other messages received at the BSS relating to this connection and concerning assignment, handover, or cipher mode control should be discarded. + +Whilst the Internal Handover execution procedure is in operation the BSS should not attempt to invoke any other procedure related to this call, e.g. not send HANDOVER REQUIRED or INTERNAL HANDOVER REQUIRED. + +### 3.1.5c.3 Internal Handover Enquiry + +The MSC may trigger the "Internal Handover Execution" procedure to ensure that the best fit of dedicated resource(s) (Codec Type, Codec Configuration, Redundancy Level and A-Interface Type) are allocated to the ongoing call (e.g. to re-establish TrFO). The decision in the MSC to trigger this procedure is linked to implementation dependent strategies, based on the information received from the MS and from the network. + +The Internal Handover Preparation procedure is triggered by the MSC with the transmission of an INTERNAL HANDOVER ENQUIRY message to the BSS. + +The INTERNAL HANDOVER ENQUIRY message shall contain in the "Speech Codec (MSC Chosen)" Information Element the details of the resource(s) (Codec Type, Codec Configuration and Interface Type) preferred by the MSC. The BSS shall use the information provided in the "Speech Codec (MSC Chosen)" Information Element to decide a possible target cell that meets such indications. + +NOTE: The target cell can be the cell where the voice call is ongoing. + +Upon reception of the INTERNAL HANDOVER ENQUIRY message, if the BSS finds an appropriate target cell that meets the needed radio requirements and is compatible with the preferences in the "Speech Codec (MSC Chosen)" Information Element, the BSS shall initiate the Internal Handover Preparation procedure by sending the INTERNAL HANDOVER REQUIRED message as described in sub-clause 3.1.5c.1, with Cause "Response to an INTERNAL HANDOVER ENQUIRY message". + +The BSS may respond to an INTERNAL HANDOVER ENQUIRY message with an HANDOVER FAILURE message with cause value "INTERNAL HANDOVER ENQUIRY reject". For example the BSS cannot find an appropriate target cell that meets the needed radio requirements and is compatible with the preferences in the "Speech Codec (MSC Chosen)" Information Element contained in the INTERNAL HANDOVER ENQUIRY message. + +## 3.1.6 Internal Intra-Cell Handover Procedure + +The definition of internal intra cell handover is given in sub-clause 5. + +It is optional that a BSS support internal intra-cell handover. However if it is supported, it should be as follows: + +It should be possible to inhibit internal intra-cell handover at an BSS that supports it by operation and maintenance command. + +Internal intra-cell handover occurs between channels on the same cell. It is decided and executed autonomously by the BSS, so that no message is generated at the BSS-MSC interface, until the completion of the handover execution, when the BSS sends a HANDOVER PERFORMED message over the SCCP and terrestrial resources that are presently assigned to that call. Changes in type of resources (for instance channel rate change, speech version change, ciphering algorithm change) are indicated in the HANDOVER PERFORMED message. + +If an IP based user plane A-interface is supported and compressed speech over IP is in use, then the BSS shall not perform any autonomous "internal intra-cell handover" procedure with a change of Codec Type or Codec Configuration or Redundancy Level to an incompatible one. When the speech transcoder resources are not allocated within the BSS or the Redundancy Level or the A-Interface Type has to be changed, then the BSS shall use the "BSS Internal Handover" Procedure. The decision process in the BSS is based on the internally available radio and resource parameters taking into account the previously received information from the MSC in the ASSIGNMENT REQUEST or HANDOVER REQUEST. + +The relevant radio interface layer 3 procedures (dedicated channel assignment) are described in 3GPP TS 24.008. + +In the case of group calls the BSS may perform an intra-cell handover for a talker from a dedicated channel to a group call channel, in this case the HANDOVER PERFORMED message is sent by the BSS over the SCCP connection that was previously assigned to the talker, followed by a CLEAR REQUEST with the cause "Joined group call channel", the MSC shall release the dedicated A interface resources. + +In the case of group calls the BSS may perform an Intra-cell handover for a talker from a Group call channel to a dedicated channel, in this case the BSS performs external handover. + +If local switching was requested by the MSC before the initiation of the internal intra-cell handover procedure, then the BSS shall maintain local switching on the new channel according to the most recently received LCLS-Configuration IE and (if received) LCLS-Connection-Status-Control IE and inform the MSC of the local switch outcome by including the LCLS-BSS-Status IE with the correct LCLS connection status value according to sub-clause 3.2.2.119 within the HANDOVER PERFORMED message. The BSS shall also notify the MSC serving the other call leg if the LCLS connection status is changed for this call leg, see sub-clause 3.1.33.5. + +### 3.1.7 Internal Inter-Cell Handover Procedure + +The definition of internal inter-cell handover is given in sub-clause 5. + +It should be possible to inhibit internal inter-cell handover at a BSS that supports it by operation and maintenance command. + +Multi cell BSSs would normally be expected to support internal inter-cell handover, however it is optional that they do so. However if it is supported, it should be as follows: + +Internal inter-cell handover occurs between channels pertaining to different cells of the same BSS. It is decided and executed autonomously by the BSS, so that no message is generated at the BSS-MSC interface, until the completion of the handover execution, when the BSS sends a HANDOVER PERFORMED message over the SCCP and terrestrial resources that are presently assigned to that call. Changes in type of resources (for instance channel rate change, speech version change, ciphering algorithm change) are indicated in the HANDOVER PERFORMED message. + +If an IP based user plane A-interface is supported and compressed speech over IP is in use, then the BSS shall not perform any autonomous "Internal inter-cell handover" procedure with a change of Codec Type or Codec Configuration or Redundancy Level to an incompatible one. When the speech transcoder resources are not allocated within the BSS or the Interface Type has to be changed, then the BSS shall use the "BSS Internal Handover" procedure. + +A special case of internal handover occurs when the handover is triggered by the assignment procedure, e.g. directed retry. In this case the HANDOVER PERFORMED message need not be sent as the equivalent response is provided by the ASSIGNMENT COMPLETE message. + +The decision process in the BSS is based on the internally available radio and resource parameters taking into account the previously received information from the MSC in the ASSIGNMENT REQUEST or HANDOVER REQUEST. + +The relevant radio interface layer 3 procedures (for handover) are described in 3GPP TS 24.008. + +Internal inter-cell handover for group calls may be performed from either dedicated to dedicated channels, or dedicated to group call channels, or group call to group call channels. + +In the case of group calls, the BSS may perform an internal inter-cell handover for a talker from a dedicated channel to a Group call channel, in this case the HANDOVER PERFORMED message is sent by the BSS over the SCCP connection that was previously assigned to the talker. The BSS will send a CLEAR REQUEST with the cause "Joined group call channel". + +In the case of group calls, the BSS may perform an internal inter-cell handover for a talker from a group call channel to a Group call channel, in this case the HANDOVER PERFORMED message is sent by the BSS over the SCCP connection that was previously assigned to the talker. + +In the case of internal inter-cell handover the BSS, when localised service area is supported, will indicate the LSA identity of the target cell in the HANDOVER PERFORMED message if it corresponds to one of the LSA identities received in the latest LSA INFORMATION or the HANDOVER REQUEST messages. + +If local switching was requested by the MSC before the initiation of the internal inter-cell handover procedure, then the BSS shall maintain local switching on the new channel according to the most recently received LCLS-Configuration IE and (if received) LCLS-Connection-Status-Control IE and inform the MSC of the local switch outcome by including the LCLS-BSS-Status IE with the correct LCLS connection status value according to sub-clause 3.2.2.119 within the HANDOVER PERFORMED message. The BSS shall also notify the MSC serving the other call leg if the LCLS connection status is changed for this call leg, see sub-clause 3.1.33.5. + +### 3.1.8 Handover Candidate Enquiry + +The purpose of this procedure is to allow the MSC to ascertain if it is possible to handover any MSs that are currently being served by a particular cell to another nominated cell. The procedure uses both global and dedicated resource messages, and is relevant to an individual cell. + +The algorithm in which a MSC decides on starting a handover enquiry procedure is operator dependent. + +#### 3.1.8.1 Successful Operation + +The procedure operates as follows: + +The MSC sends a HANDOVER CANDIDATE ENQUIRE message to a BSS. The message indicates that the MSC wishes the BSS to identify handover candidates in a particular cell, that can be handed over to other nominated cells. The maximum number of candidates is also indicated to the BSS. + +For each selected MS candidate the BSS will send to MSC a single, once only, HANDOVER REQUIRED message (not guarded by timer T7), over each of the appropriate SCCP connections. If the BSS was already generating HANDOVER REQUIRED messages for a selected MS then the BSS will continue to do so. However the Cause IE of the next HANDOVER REQUIRED message (at the expiry of timer T7) will be set to "Response to MSC invocation" to indicate that the message is generated in response to a HANDOVER CANDIDATE ENQUIRE message. But as this HANDOVER REQUIRED was already being generated before the handover enquiry procedure was started, that HANDOVER REQUIRED would be guarded by timer T7. So in the instance of next expiry of timer T7, the BSS shall continue sending HANDOVER REQUIRED message but the Cause IE value shall revert back to the original Cause IE value. + +When the last HANDOVER REQUIRED message has been sent for all the selected MS candidates, the BSS returns to the MSC a HANDOVER CANDIDATE RESPONSE message giving the number of candidates identified, and terminating the handover enquiry procedure. + +Only one handover enquiry procedure may be invoked on any given cell at any one time. + +#### 3.1.8.2 Abnormal conditions + +If at the BSS a HANDOVER CANDIDATE ENQUIRE message is received when a handover enquiry procedure has already been invoked then the new HANDOVER CANDIDATE ENQUIRE message shall be discarded. + +### 3.1.9 Release of Radio Resource And Terrestrial Resource + +#### 3.1.9.1 Release Due To Transaction Completion + +NOTE: This sub-clause does not apply to group call channels and their related terrestrial resources. For the release of these resources due to the completion of a VGCS/VBS call, see sub-clause 3.1.9.1a. + +For a dedicated connection, the release of assigned radio resources at the end of a transaction will take place as follows: + +Release negotiation will take place directly between the MS and MSC using transparent messages via the DTAP in the BSS (see 3GPP TS 24.008). The MSC will then send a BSSMAP CLEAR COMMAND, indicating that the radio resource(s) should be released. After the BSSMAP CLEAR COMMAND has been sent, the MSC shall not send further BSSAP connection oriented messages on this particular connection, except CLEAR COMMAND. + +When BSC receives a BSSMAP CLEAR COMMAND message at the reroute procedure, see sub-clause 3.1.32 for a MOCN configuration and sub-clause 3.1.32a for a GWCN configuration, following the reception of the REROUTE COMMAND message from the MSC which is not the last attempted, no radio resources are released. + +If the BSS allocates the A interface circuits, the MSC shall release the circuit allocated to the connection, if any, before sending the CLEAR COMMAND. + +When the BSS receives the CLEAR COMMAND: + +- the guard timer defined in 3GPP TS 24.008 is started and clearing on the radio interface initiated. +- the BSS marks any assigned terrestrial resources as idle and returns a CLEAR COMPLETE message to the MSC. (The BSS need not wait for the radio channel release to be completed or for the guard timer to expire before returning the CLEAR COMPLETE message.) +- the BSS marks any assigned terrestrial resources as idle and returns a CLEAR COMPLETE message to the MSC. (The BSS need not wait for the radio channel release to be completed or for the guard timer to expire before returning the CLEAR COMPLETE message.) + +During the release of an RR connection the MSC should indicate to the BSS whether the RR connection was established as a result of CS fallback if such knowledge is available in the MSC. + +If the MSC allocates A interface circuits, on receipt of CLEAR COMPLETE, the MSC releases any assigned terrestrial resources. + +### 3.1.9.1a Release of radio resources and the terrestrial resources for VGCS/VBS calls: + +When a VGCS/VBS call is to be released, the MSC shall send a BSSMAP CLEAR COMMAND message via each VGCS/VBS Resource Controlling SCCP connection to the BSS. + +When the BSS receives the CLEAR COMMAND on a VGCS/VBS resource controlling SCCP connection, the guard timer defined in 3GPP TS 44.018 is started and clearing on the radio interface initiated. The BSS returns a CLEAR COMPLETE message to the MSC. (The BSS need not wait for the radio channel release to be completed or for the guard timer to expire before returning the CLEAR COMPLETE message.) If A-interface circuit sharing is used, the BSS marks the assigned terrestrial resources as idle only after it has sent a CLEAR COMPLETE message on each resource controlling SCCP connection associated with the call. + +When all terrestrial resources associated with the VGCS/VBS resource controlling SCCP connections towards a particular BSS have been released, the MSC shall send the BSSMAP CLEAR COMMAND message via the VGCS/VBS Call Controlling SCCP connection to the BSS to release the associated call controlling resources. When the BSS receives the CLEAR COMMAND it shall release the associated resources, it shall mark them as idle and return a CLEAR COMPLETE message to the MSC. + +After sending a BSSMAP CLEAR COMMAND on an SCCP connection, the MSC shall not send further BSSAP connection oriented messages on that connection except CLEAR COMMAND messages. + +If the BSS allocates the A interface circuits, the MSC shall release the circuit allocation to the connection, if any, before sending the CLEAR COMMAND. + +If the MSC allocates A-interface circuits, the MSC releases the circuit allocation to the connection on receipt of a CLEAR COMPLETE message. + +### 3.1.9.2 Release due to BSS generated reason + +If a radio channel release for a radio resource that is not related to a voice group or broadcast call is required because of a BSS generated reason (e.g. "O and M intervention", "equipment failure"), then the BSS shall generate a CLEAR REQUEST message towards the MSC. This message shall include a Cause Information Element, indicating the reason for the failure. + +If transmission from the non VGCS/VBS MS is lost then a CLEAR REQUEST message shall be sent to the MSC. + +On receipt of a CLEAR REQUEST for a dedicated resource the MSC shall initiate the release, as defined above, by sending a CLEAR COMMAND message. On receipt of the CLEAR COMMAND the related radio resources shall be released by the BSC. The procedure is always terminated with a CLEAR COMPLETE to the MSC. + +If the release of a radio resource that is associated with a voice group or broadcast call is required due to a BSS generated reason other than due to loss of contact of the VGCS talker or VBS originator, and the network does not support either group call re-establishment by the BSS or A-interface link sharing, then + +- if the radio resource to be released is that of the group channel in a cell other than that of the current VGCS talker or that of the VBS originator, the BSS shall send a CLEAR REQUEST message to the MSC indicating the reason for the failure. +- if the radio resource to be released is that of the group channel in the cell of the VGCS talker which is on a dedicated channel or in the cell of the VBS originator, the BSS shall send a CLEAR REQUEST message to the MSC indicating the reason for the failure. +- if the radio resource to be released is that of the current VGCS talker which is on a dedicated channel, BSS shall send an UPLINK RELEASE INDICATION message to the MSC indicating the reason for the failure. On receipt of an UPLINK RELEASE INDICATION message with a cause value other than "Call control" or "Radio interface failure", the MSC shall initiate the release of the radio and terrestrial resources by sending a CLEAR COMMAND message on the dedicated SCCP connection. +- if the radio resource to be released is that of the current VGCS talker which is on a group channel, the BSS shall send an UPLINK RELEASE INDICATION message to the MSC indicating the reason for the failure. On receipt of an UPLINK RELEASE INDICATION message with a cause value other than "Call control" or "Radio interface failure", the MSC shall initiate the release of the radio and terrestrial resources by sending a CLEAR COMMAND message on the VGCS/VBS resource controlling SCCP connection. +- if the radio resource to be released is that of the VBS originator, the BSS shall send a CLEAR REQUEST message to the MSC indicating the reason for the failure. On receipt of a CLEAR REQUEST message the MSC shall initiate clearing of the broadcast call. + +If a radio channel release of the radio resource that is associated to a voice group or broadcast call is required due to a BSS generated reason other than due to loss of contact of the VGCS talker or VBS originator, and the network supports group call re-establishment by the BSS or A-interface link sharing, then: + +- if the radio resource to be released is that of the group channel in a cell other than that of the current VGCS talker or that of the VBS originator, the BSS shall send a VGCS/VBS ASSIGNMENT STATUS message to the MSC indicating cell released for the group call, and then releases the radio resource. If A-interface link sharing is being used the VGCS/VBS ASSIGNMENT STATUS message is sent after expiry of timer Tast. +- if the radio resource to be released is that of the group channel in the cell of the VGCS talker which is on a dedicated channel or in the cell of the VBS originator, the BSS shall send a VGCS/VBS ASSIGNMENT STATUS message to the MSC indicating cell released for the group call, and then releases the radio resource. If A-interface link sharing is being used the VGCS/VBS ASSIGNMENT STATUS message is sent after expiry of timer Tast. +- if the radio resource to be released is that of the current VGCS talker which is on a dedicated channel, the BSS shall send an UPLINK RELEASE INDICATION message to the MSC indicating the reason for the failure. On receipt of an UPLINK RELEASE INDICATION message with a cause value other than "Call control" or "Radio interface failure", the MSC shall initiate the release of the radio and terrestrial resources by sending a CLEAR COMMAND message on the dedicated SCCP connection. +- if the radio resource to be released is that of the current VGCS talker which is on a group channel, the BSS shall send an UPLINK RELEASE INDICATION message with an appropriate cause value. The BSS shall also send a VGCS/VBS ASSIGNMENT STATUS message to the MSC indicating cell released for the voice group or broadcast call, and then release the radio resource for the group channel. When A-interface link sharing is being used the VGCS/VBS ASSIGNMENT STATUS message is sent after expiry of timer Tast. +- if the radio resource to be released is that of the VBS originator, the BSS shall send a CLEAR REQUEST message to the MSC indicating the reason for the failure. On receipt of a CLEAR REQUEST message the MSC shall initiate clearing of the broadcast call. + +On receipt of a CLEAR REQUEST on the VGCS/VBS resource controlling SCCP connection, the MSC shall initiate the release, as defined above, by sending a CLEAR COMMAND message. On receipt of the CLEAR COMMAND the radio resources related to this cell shall be released by the BSS. If the terrestrial resource is not configured for A-interface circuit sharing then the resource shall be released by the MSC or marked as idle by the BSS. For the case that the terrestrial resource is configured for A-interface circuit sharing then it will only be released by the MSC or marked as idle by the BSS if there are no other VGCS/VBS resource controlling SCCP connections that are sharing this resource. The resource controlling SCCP connection for the cell shall be released. The procedure is always terminated with a CLEAR COMPLETE to the MSC. + +If transmission from a VGCS talker that was on the group call channel is lost then the BSS shall indicate the uplink being released by sending an UPLINK RELEASE INDICATION message with cause value "Radio interface failure". the MSC shall not start the clearing sequence, and the resources at the BSS are not released. + +If transmission from a VGCS talker that was on a dedicated channel is lost, then the BSS shall indicate the uplink being released by sending an UPLINK RELEASE INDICATION message with cause value "Radio interface failure". The MSC shall initiate the release of the resources associated with the talker by sending a CLEAR COMMAND message, as described above. + +If transmission from a VBS originator is lost then the BSS shall send a CLEAR REQUEST message with cause value "Radio interface failure". On receipt of a CLEAR REQUEST message the MSC shall initiate clearing of the broadcast call. + +In the case of a group call talker the BSS may move the mobile on to a group call channel, in this case the BSS shall initiate a release of A interface resources by sending a CLEAR REQUEST with the cause "Joined group call channel". The MSC in its turn shall release the dedicated resources associated with the talker. + +If the BSS sends a CLEAR REQUEST with the cause different than "Joined group call channel" for resources associated with the uplink, then the MSC shall assume uplink indicated as released. + +### 3.1.9.3 Release due to successful handover + +If a radio channel release is required because of a handover being successfully completed on another BSS, then the resources at the old BSS are released by the MSC using the clearing sequence with cause value "handover successful". + +In the case of handover of a group call talker from a group call channel the MSC shall send a HANDOVER SUCCEEDED message to the old BSS. + +### 3.1.9.4 Release due to uplink release + +If a talker on dedicated connection releases its uplink the BSS shall inform the MSC by an UPLINK RELEASE INDICATION message with cause value "Call control". Then the resources at the BSS are released by the MSC using the clearing sequence. The BSS is allowed to release the radio resources before the MSC initiates the clearing procedure. + +If a talker on group call channel releases its uplink, the BSS shall inform the MSC by an UPLINK RELEASE INDICATION message with cause value "Call control". In this case the MSC shall not start the clearing sequence, and the resources at the BSS are not released. The BSS shall initiate the radio interface uplink free procedure. + +## 3.1.10 Paging + +PAGING messages for all MSs shall be sent via the BSSMAP as a connectionless message. These will include the IMSI of the MS to allow derivation of the paging population number; they may also include an indication of which combination of channels will be needed for the subsequent transaction related to the paging. This type of PAGING message will then be stored and a corresponding radio interface paging message transmitted over the radio interface at the appropriate time. + +It should be noted that each PAGING message on the MSC-BSS interface relates to only one MS and therefore the BSS has to pack the pages into the relevant 3GPP TS 24.008 radio interface paging message. + +If a radio interface PAGING RESPONSE message is received then the relevant connection is set up towards the MSC as described in 3GPP TS 48.002 and the radio interface PAGING RESPONSE message is passed to the MSC in a COMPLETE LAYER 3 INFORMATION message. + +If an IP based user plane interface is supported the COMPLETE LAYER 3 INFORMATION message shall contain the Information Element "Codec List (BSS Supported)". + +A single PAGING message across the MSC to BSS interface contains information on the cells in which the page shall be broadcast. + +If the VGCS/VBS flag is set to zero, this indicates that the mobile station to be paged is not a member of any VGCS/VBS group and it is thus not necessary to perform in band paging for this mobile station over the FACCH channel for any VGCS/VBS group. + +If the mobile station is a member of at least one VBS/VGCS group, then the MSC shall indicate the paging cause in the Paging Information IE and shall include this IE in the PAGING message. + +### 3.1.11 Trace Invocation + +The purpose of the trace invocation procedure is to inform the receiving entity that it should begin producing a trace record on this particular transaction. + +The trace is invoked either by the MSC sending a MSC INVOKE TRACE message to the BSS or by the BSS sending a BSS INVOKE TRACE message. + +The events and parameters to be recorded are indicated in the "Trace type" information element. + +A "Forwarding indicator" element may be used in the BSS INVOKE TRACE to indicate if the trace is to be continued after handover to another BSS. If thus indicated, The MSC should forward the BSS INVOKE TRACE to the BSS-B and also store it to send to any subsequent BSS during the lifetime of the call. + +The remaining elements, when received, are to be passed transparently to the OMC receiving the trace record. + +The element "OMCId", if present, indicates the OMC to which the record is destined. + +In sending the BSS INVOKE TRACE message, the BSS may allocate and include a "BSS transaction reference". Similarly in the MSC INVOKE TRACE message, the MSC may allocate and include an "MSC transaction reference" (typically a call reference). The transaction reference is contained in the information element "TransactionId". + +The message includes a trace reference which is allocated by the entity which triggered the trace. + +The element "TriggerId", if present, indicates the entity which triggered the trace. + +The trace reference, triggerId and transactionId Information Elements are used to tag the trace record to allow simpler construction of the total record by the entity which combines trace records. + +The messages are not acknowledged and are sent as a connection oriented message on the connection on which a trace is required. + +### 3.1.12 Flow Control + +These procedures are defined to give some degree of flow control. At the BSS processor overload and CCCH scheduler overload are catered for, and at the MSC processor overload is catered for. + +#### 3.1.12.1 Philosophy + +The philosophy used is to stem the traffic at source with known effect on the service. The algorithm used is: + +- On receipt of the first OVERLOAD message or signalling point congested information, the traffic is reduced by one step. At the same time, timers T5 (T17) and T6 (T18) are started. During T5 (T17) all received overload messages or signalling point congested information are ignored in order not to reduce the traffic too rapidly. Reception of an OVERLOAD message or signalling point congested information after expiry of T5 (T17) but still during T6 (T18) , will decrease the traffic load by one more step, and restart T5 (T17) and T6 (T18). +- This step by step reduction of traffic is continued until maximum reduction is obtained by arriving at the last step. If T6 (T18) expires (i.e. no OVERLOAD message or signalling point congested information is received during T6 (T18)) the traffic will be increased by one step and T6 (T18) will be started, unless full load has been resumed. + +NOTE: Timers T5 and T6 are running in the MSC whilst Timers T17 and T18 are running in the BSS. + +- The number of steps and the method of reducing the load is considered to be an implementation specific function. + +There may be other traffic control mechanisms from O and M activities occurring simultaneously. + +### 3.1.12.2 Processor Overload at the MSC + +The MSC can indicate to the BSS that it is in a congested state by sending an OVERLOAD message. This is sent as a connectionless global message. + +At the BSS receipt of this message causes the reduction of random access traffic using the method described in sub-clause 3.1.12.1. + +For example, the amount of random access traffic could be reduced by using the access control class in the system information message of 3GPP TS 24.008. + +### 3.1.12.3 Processor/CCCH overload at the BSS + +If the CCCH scheduler at the BSS is overloaded (queue passed a predefined threshold) then the BSS sends an OVERLOAD message to the MSC (or, if the network supports "Intra domain connection of RAN nodes to multiple CN nodes" (see 3GPP TS 23.236 [48]) to the appropriate MSCs) with the appropriate cause (Cause value: "CCCH overload") and indicating the cell in question. + +If the BSS processing is overloaded then the BSS sends an OVERLOAD message with the Cause value: "processor overload". + +The MSC originated traffic is reduced in accordance with the method described in sub-clause 3.1.12.1. + +### 3.1.12.4 Message throughput congestion + +If the lower layers of the protocol become congested then it is assumed that the MTP congestion indication will take place (see 3GPP TS 48.002) and the source of the traffic will receive primitives from the transport protocols resulting in it reducing the generated load. + +A suitable method to achieve this reduction could be based on that given in sub-clause 3.1.12.1. + +## 3.1.13 Classmark Handling Procedures + +### 3.1.13.1 Classmark request procedure + +The purpose of this procedure is to allow the MSC to trigger a classmark updating procedure. This is done by sending a CLASSMARK REQUEST message to the BSS on the appropriate SCCP connection. When receiving this message the BSS shall initiate the appropriate actions on the radio path. + +### 3.1.13.2 Classmark updating procedure + +The purpose of the classmark updating procedure is to inform the receiving entity about classmark information received from the MS. + +At any point when an SCCP connection has been established for BSSAP messages, the BSS must be able to send to the MSC a CLASSMARK UPDATE message if a classmark update is received from the MS. This message contains information on several transmission parameters relevant to the MS in communication with the network. + +If the MSC has already initiated a handover for the concerned MS by sending a HANDOVER REQUEST message when the CLASSMARK UPDATE message is received, the MSC shall send a CLASSMARK UPDATE message to the target BSS when the MS is successfully in communication with the network on the new (main) channel. If this CLASSMARK UPDATE message is received in the target BSS after a new classmark has been received from the Mobile Station the CLASSMARK UPDATE message from the MSC shall be ignored. + +This message is sent as a BSSAP message over the appropriate SCCP connection. + +This procedure will be used where the power class of the MS changes or if the network requests the MS to send the classmark information whilst the MS has one or more dedicated resources. + +The procedure will also be used to send classmark information to the MSC if the MS immediately after initial L3 message sends additional classmark information. In this case the BSS may as an option suppress or delay the sending of the CLASSMARK UPDATE message to the MSC. + +### 3.1.14 Cipher Mode Control + +#### 3.1.14.1 Successful Operation + +The cipher mode control procedure allows the MSC to pass cipher mode information to the BSS to select and load the user data and signalling encryption device with the appropriate key. + +This is achieved by sending the BSS a CIPHER MODE COMMAND message. Receipt of the message at the BSS will cause the generation of a radio interface CIPHERING MODE COMMAND message and, if applicable, invoke the encryption device and start stream ciphering as described in 3GPP TS 24.008 and 3GPP TS 43.020. + +If within the CIPHER MODE COMMAND, the signalling element "Cipher response mode" is present and indicates "IMEI must be included by the Mobile Station", then the BSS shall request in the radio interface message CIPHERING MODE COMMAND the Mobile Station to include its IMEI in the radio interface CIPHERING MODE COMPLETE message (see 3GPP TS 24.008). + +In the CIPHER MODE COMMAND the MSC specifies which of the ciphering algorithms may be used by the BSS. The BSS then selects an appropriate algorithm, taking into account the MS ciphering capabilities. The CIPHER MODE COMPLETE message returned to the MSC indicates the chosen ciphering algorithm. The set of permitted ciphering algorithms specified in the CIPHER MODE COMMAND shall remain applicable for subsequent Assignments and Intra-BSS Handovers. + +The CIPHER MODE COMMAND and CIPHER MODE COMPLETE messages are sent as connection oriented messages via the appropriate SCCP connection. + +Receipt of the radio interface CIPHERING MODE COMPLETE message (or other correctly deciphered layer 2 frame) from the radio interface is used internally within the BSS to achieve radio interface ciphering synchronisation (see 3GPP TS 24.008). When the BSS receives the radio interface CIPHERING MODE COMPLETE from the MS a CIPHER MODE COMPLETE message is returned to the MSC. If the CIPHERING MODE COMPLETE message received on the radio interface contained more than two octets, then the BSS shall include in the BSSMAP CIPHER MODE COMPLETE message a "Layer 3 message contents" signalling element containing octets 3 up to n (where n is the length of that CIPHERING MODE COMPLETE radio interface message) of that radio interface CIPHERING MODE COMPLETE message. + +#### 3.1.14.2 Abnormal Conditions + +If the BSS is unable to support the ciphering algorithm specified in the CIPHER MODE COMMAND message then it shall return a CIPHER MODE REJECT message with Cause value "Ciphering algorithm not supported". A CIPHER MODE REJECT message shall also be returned if the MSC requests a change of ciphering algorithm when ciphering is already active. + +### 3.1.15 General SCCP Abnormal Conditions + +If a user-out-of-service information or signalling-point-inaccessible information is received by the BSSAP or BSSOMAP 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 BSS 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 BSSAP procedures are being performed or while a dedicated resource is still allocated the following actions are taken: + +#### At BSS: + +The radio resources associated with the SCCP connection are cleared by an appropriate radio procedure. + +Any BSS procedure relating to that connection is abandoned. + +The resources allocated to the call associated to the connection are released. + +#### At MSC: + +The call associated with the SCCP connection is cleared as soon as possible. + +At the BSS, communication over assigned radio channels shall be assumed to be continuing until either the SCCP connection is lost, a clearing sequence is received, or no signal is received from an MS for longer than the guard time defined in 3GPP TS 24.008. If the BSS recognises that a call has terminated then a CLEAR REQUEST message should be generated. + +If a 2Mbit/s system fails and one of the standard alarms is received, no action is taken at the BSS on the calls associated with the traffic channels involved. + +At the MSC, calls or VGCS talker dedicated connection and associated uplink or resource controlling connection should be cleared if either subscriber clears, or if the BSS sends a CLEAR REQUEST message. Clearing of affected calls by the MSC may take place after loss of the traffic channels for a period defined by the operator. + +For the procedures controlled by the MSC, and in particular procedures where the MSC sends a request for resources at the BSS and waits for an acknowledge, the implementation in the MSC must provide means for avoiding deadlock situations at the BSS as e.g. hanging resources. + +### 3.1.16 Initial MS message + +When the SCCP connection establishment is performed by the BSS, the radio interface initial L3 message received from the MS (piggybacked on the SABM frame) is processed as follows: + +The BSS shall analyse the protocol discriminator of the message. + +If the BSS does not support the protocol, reactions of the BSS are specified in 3GPP TS 44.018. If the BSS supports the protocol, it shall analyse the message to a level which allows the extraction by the BSS of the Classmark information and, if the network supports "Intra domain connection of RAN nodes to multiple CN nodes", the Mobile Identity (see 3GPP TS 23.236 [48]). However, except for the NOTIFICATION RESPONSE, the entire radio interface initial L3 message (e.g. CM SERVICE REQUEST, PAGING RESPONSE, CM REESTABLISHMENT REQUEST, LOCATION UPDATING REQUEST, IMSI DETACH, IMMEDIATE SETUP) is also passed to the MSC, using a COMPLETE LAYER 3 INFORMATION message. The BSS does not analyse the contents of the initial layer 3 message, other than the Classmark information and, if the network supports "Intra domain connection of RAN nodes to multiple CN nodes", the Mobile Identity. If an IP based user plane interface is supported, the COMPLETE LAYER 3 INFORMATION message shall include the Information Element "Codec List (BSS Supported)". + +If an IP based user plane interface is supported, the BSS shall predict to its best possible knowledge, which Codec Types, Codec Configurations, A-Interface Types and transcoder resources in the BSS could be used at this point in time. The BSS shall only include elements within the Codec List (BSS Supported) that are currently available. + +The BSS may also give the MSC a description of the channel on which the initial layer 3 message was received. + +When network sharing is in use in a cell, the initial Layer 3 message has to be managed as follows: + +- In the case of LOCATION UPDATING REQUEST and for a PLMN index indicator equal to zero (which corresponds to a mobile station non supporting network sharing): the rerouting procedure shall be applied, as described in sub-clause 3.1.32 in case of a MOCN configuration and as described in sub-clause 3.1.32a in case of a GWCN configuration. +- In the case of LOCATION UPDATING REQUEST, CM SERVICE REQUEST, PAGING RESPONSE and for a PLMN index indicator different from zero (which corresponds to a mobile station supporting network sharing): the BSS shall include the selected PLMN ID within the COMPLETE LAYER3 INFORMATION message, as described within sub-clause 3.2.1.32. In such a case the selected PLMN ID shall be derived by the BSS from the PLMN index indicator provided within the initial Layer3 message as described within 3GPP TS 24.008 [6]. + +### 3.1.17 Queuing Indication + +The purpose of the QUEUING INDICATION message is to inform the MSC about a delay in the allocation of the necessary dedicated radio resources. The procedure is only relevant if the system is using a queuing procedure for traffic channels in the BSS, (sub-clause 3.1.17.1) and/or for handover of traffic channels (sub-clause 3.1.17.2). + +### 3.1.17.1 Operation of the procedure in case of assignment procedure + +After the ASSIGNMENT REQUEST message without having the necessary TCH available the ASSIGNMENT REQUEST message shall be put into a queue; the QUEUING INDICATION message shall be returned to the MSC and the timer T11 shall be started. The timer value T11 specifies the maximum queuing delay and is determined by the operator. + +The procedure shall be terminated with a successful or unsuccessful assignment of the required traffic channel(s) by sending an ASSIGNMENT COMPLETE or an ASSIGNMENT FAILURE message, respectively, to the MSC. + +If the timer T11 expires the ASSIGNMENT REQUEST message shall be removed from the queue and a CLEAR REQUEST message shall be sent to the MSC, with the Cause "no radio resource available". + +### 3.1.17.2 Operation of the procedure in case of hand-over resource allocation procedure + +After the HANDOVER REQUEST message without having the necessary TCH available the HANDOVER REQUEST shall be put into a queue; the QUEUING INDICATION message shall be returned to the MSC and the timer Tqho shall be started. The timer value Tqho specifies the maximum queuing delay and is determined by the operator. + +The procedure shall be terminated with a successful or unsuccessful reservation of the required traffic channel(s) by sending a HANDOVER REQUEST ACKNOWLEDGE or a HANDOVER FAILURE message, respectively, to the MSC. + +If the timer Tqho expires the HANDOVER REQUEST shall be removed from the queue and a HANDOVER FAILURE message shall be sent to the MSC with the Cause value "no radio resource available". + +## 3.1.18 Data Link Control SAPI not Equal to "0" + +The radio interface can support data links with the SAPI not equal to "0". + +### 3.1.18.1 Data link set up across the radio interface + +This sub-clause deals with the impact of data link establishment (SAPI not equal to "0") on the MSC to BSS interface. + +#### 3.1.18.1.1 MS to MSC direction + +In the MS to MSC direction the receipt of a layer 3 message via a data link where SAPI does not equal "0" at the BSS will be transferred to the MSC as a DTAP message with the DLCI (Data Link Connection Identification) octet set appropriately. + +#### 3.1.18.1.2 MSC to MS Direction + +Receipt of a layer 3 (DTAP) message from the MSC with the SAPI (indicated in the DLCI) not equal to "0" will cause one of the following actions: + +- the triggering of a data link set up to support the message transfer across the radio interface if no suitable link exists; +- the transmission of the message to the MS if a suitable link has already been established; +- the sending of a BSSMAP SAPI "N" REJECT message to the MSC if for any reason the data link cannot be established, A Cause Information Element is included; typical Cause values are: "O&M intervention", "processor overload", "BSS not equipped", "MS not equipped". + +### 3.1.18.2 Choice of the signalling link + +When the BSS relays a message of the PDSS1 protocol received on the air interface to the MSC, it shall indicate in the DLCI (see 3GPP TS 48.002) on which control channel and SAPI the message was received. + +When the MSC sends a DTAP message to the BSS, it shall: + +- if the protocol of the corresponding air interface layer 3 message is PDSS1, specify on which control channel and SAPI of the air interface the L3 message shall be sent; + +- otherwise not further specify the control channel on the air interface. + +When the BSS relays an air interface L3 message received in a DTAP message on the A interface to the MS, it shall: + +- if the DLCI does not further specify the signalling channel of the air interface, send it on the appropriate signalling link; +- if the BSS supports PDSS1 and the DLCI specifies which control channel is to be used for transmission on the air interface, the BSS shall transfer the air interface L3 message on the specified control channel. + +NOTE: If the BSS does not support PDSS1, it considers the part of the DLCI possibly indicating the control channel to be used on the air interface as spare bits, see 3GPP TS 48.002. + +### 3.1.19 BSSMAP Error Handling + +To allow for the introduction of new functions the following rules shall be used to determine the actions of a receiving entity when it receives a message, part or all of which it is unable to understand. As the recipient is unable to tell the difference between a new, previously unspecified coding and an erroneous coding, the recipient also uses the same rules for error handling. + +The robustness of a recipient in handling erroneous messages does not relax the requirement that the transmitter shall obey the present document. However, it is intended that functionality can be gradually added to an entity, and no obstacle to intermediate phase equipment is intended. + +With the exception of sub-clause 3.1.19.6, the specific 'abnormal case' handling in other sub-clauses of the present document take precedence over this sub-clause. + +#### 3.1.19.1 Definitions of Types of Information Elements + +The following definitions shall be used in sub-clause 3.1.19 and only in this sub-clause. + +##### Essential Elements + +These are the conditional elements when the condition for their reception is fulfilled, plus the Mandatory elements excluding the Cause value information element (sub-clause 3.2.2.5). + +##### Mandatory Elements + +These are the Information Elements marked as 'M' in sub-clause 3.2.1. + +##### Non-Essential Elements + +Non-essential elements are all the information elements that are not defined as essential. + +##### Conditional Elements + +In the indicated messages the following elements are conditional: + +- Circuit identity code in sub-clauses 3.2.1.1 and 3.2.1.8. +- Circuit pool list in sub-clauses 3.2.1.3, 3.2.1.9, 3.2.1.16 and 3.2.1.55. + +NOTE: A conditional IE is an IE whose presence or absence in a message can be determined by information contained in the rest of the message. + +##### Transparent Elements + +The following elements are defined as transparent: + +- for the BSS: TMSI; +- RR cause; +- Layer 3 information in the BSSMAP HANDOVER COMMAND message; and +- Layer 3 message contents; and for the MSC: Resource situation. +- Layer 3 information in the BSSMAP HANDOVER REQUEST ACKNOWLEDGE message; and +- "Old BSS to new BSS information" in the BSSMAP HANDOVER REQUIRED message; + +- "Source RNC to target RNC transparent information (UMTS)" in the BSSMAP HANDOVER REQUIRED message; +- "Source RNC to target RNC transparent information (cdma2000)" in the BSSMAP HANDOVER REQUIRED message. + +## Non-Transparent Elements + +Non-transparent elements are all the information elements that are not defined as transparent. + +### 3.1.19.2 Erroneous Events + +The following events shall be regarded as errors by the recipient: + +- a message whose type is non-existent, unrecognisable, not consistent with the recipient's state, or, that is sent in the wrong direction. This includes messages that should use the SCCP connectionless service but that are received on an SCCP connection, and vice versa; +- a missing essential information element; +- use of a reserved codepoint in an information element that is both essential and non-transparent; and +- an essential and non-transparent information element which is too short (the contents of any 'Length' octet shall be used to determine the boundary of the element). + +When a recipient detects one or more of these events it shall return the appropriate error message with a suitable Cause value and the message shall be discarded. + +### 3.1.19.3 Non-erroneous Events + +The following events shall not be regarded as errors by the recipient: + +- spare bits with an unexpected value in any information element; +- the use of additional octets in any information element with a length octet; +- a missing non-essential information element; +- use of reserved codepoints in any non-essential information element or in any transparent information element; and +- a non-essential information element or a transparent information element whose length is too short. + +When the recipient detects one or more of these events the receiving entity shall ignore the information that it is unable to understand and treat the message on the basis of the information that remains. + +Additionally: + +- all information in a message that is received after the start of an information element with an unrecognisable identifier shall be ignored. The message shall be accepted or rejected solely on the basis of the information received before the start of the unrecognisable element; and +- when more information elements of a particular type are received than are expected, the last one(s) shall be ignored. + +### 3.1.19.4 Other Events + +The following events should be treated on a case by case basis and the outcome may depend upon the capabilities of the recipient. + +- 1 The recipient may accept messages that contain information elements that do not appear to be in the correct sequence. Elements that occur more than once in a message shall be assumed to have been transmitted in the correct order. Recipients that do not accept out of sequence information elements shall regard the message as containing unexpected and/or missing information elements and follow the procedures of sub-clauses 3.1.19.1 and/or 3.1.19.2. + +- 2 Where a field in an information element contains a value, which the recipient knows to be incorrect, the recipient shall either reject the message or it shall ignore that field, and treat the information that remains in the message. + +(e.g. if the 'Number of MSs' in a Handover Candidate Response message is greater than the number of Handover Required messages received). + +### 3.1.19.5 Appropriate Error Message and Cause Value + +The choice of error message depends upon the received message type: + +| Received message type | Error Message | +|--------------------------------------------------------------------------------------------------------------|---------------------------------------| +| ASSIGNMENT REQUEST | ASSIGNMENT FAILURE | +| HANDOVER REQUEST | HANDOVER FAILURE | +| HANDOVER REQUIRED:
- if "Response Request" i.e. is present
- if "Response Request" i.e. is not present | HANDOVER REQUIRED REJECT
CONFUSION | +| CIPHER MODE COMMAND | CIPHER MODE REJECT | +| VGCS/VBS SETUP | VGCS/VBS SETUP REFUSE | +| VGCS/VBS ASSIGNMENT REQUEST | VGCS/VBS ASSIGNMENT FAILURE | +| CONFUSION | an error message shall not be used | +| all other message types | CONFUSION | + +When a problem is experienced with a message sent over an SCCP connection, the error message is returned over that connection. When a problem occurs in a message sent using the SCCP connectionless service, the error message is returned using the SCCP connectionless service. + +To avoid overload of the A-interface, transmission of error messages may be inhibited. (However, the transmission of Assignment Failure, Handover Failure, Handover Required Reject and Cipher Mode Reject messages in the cases required by sub-clauses 3.1.1, 3.1.5, 3.1.5a and 3.1.14 shall not be inhibited.) When the transmission of error messages is inhibited, they shall be replaced by some kind of notification to O&M. Several settings may be used to allow various subsets of 'error events' to trigger error messages while the remaining events only lead to O&M notification. + +The Error pointer in the Diagnostics information element should be used to indicate the position of a detected error in the received message. Typical Causes are: + +| Cause | Usage | +|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Invalid cell | Indicated cell not controlled by the BSS or not reachable through the MSC. May also be used for handover outside group call area. | +| Invalid message contents | May be used in any error message. | +| Protocol error between BSS and MSC | The received message is not consistent with the receiver's state, or the message has been sent in the wrong direction, or the message uses the wrong SCCP service (connection oriented instead of connectionless or vice versa). | +| Information element or field missing | Data missing from the area indicated by the error pointer. | +| Incorrect value | A field (that should be indicated by the error pointer) contains an incorrect or incompatible value, or uses a reserved codepoint. | +| Unknown message type | The received message was of an unknown type. | +| Unknown information element | An information element identifier (that should be indicated by the error pointer) contains an unknown value. | + +### 3.1.19.6 Unequipped Circuit Identification Code + +If a MSC or BSS receives a message indicating one or more circuit which are unknown the following actions shall be taken: + +- If an ASSIGNMENT REQUEST, a VGCS/VBS ASSIGNMENT REQUEST or a HANDOVER REQUEST message is received containing a circuit identity code which is unknown to the BSS the appropriate failure message is returned to the MSC. In addition the UNEQUIPPED CIRCUIT message is sent to the MSC for the circuit concerned. +- If an ASSIGNMENT COMPLETE, a VGCS/VBS ASSIGNMENT RESULT, a HANDOVER REQUEST ACKNOWLEDGE or a CHANGE CIRCUIT ACKNOWLEDGE Message is received containing a circuit identity code which is unknown to the MSC, it is up to the MSC to correct the situation, e.g. by performing a circuit re-selection procedure and sending an UNEQUIPPED CIRCUIT Message to the BSS. + +- If a circuit supervision message (BLOCK, UNBLOCK or RESET CIRCUIT) is received containing a circuit identity code which is not known no respective acknowledgement is returned. Instead an UNEQUIPPED CIRCUIT Message is sent to the peer entity for the circuit concerned. +- If a circuit supervision acknowledgement message (BLOCKING ACKNOWLEDGE, UNBLOCKING ACKNOWLEDGE or RESET CIRCUIT ACKNOWLEDGE) is received containing a circuit identity code which is not known, an UNEQUIPPED CIRCUIT message is sent to the peer entity for the circuit concerned. +- If a circuit group supervision message (GROUP BLOCK, GROUP UNBLOCK) is received which affects one or more circuits which are unknown to the own entity the returned acknowledgement message shall not contain any information about these circuit(s), i.e. the respective status bit(s) in the status field shall not be set. Instead an UNEQUIPPED CIRCUIT Message is sent to the peer entity for the circuit(s) concerned. +- If a circuit group supervision acknowledgement message (CIRCUIT GROUP BLOCKING ACKNOWLEDGE or CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE) is received which affects one or more circuits which are unknown to the own entity an UNEQUIPPED CIRCUIT message is sent to the peer entity for the circuit(s) concerned. +- If an UNEQUIPPED CIRCUIT Message is received indicating a circuit which is unknown in the own entity no UNEQUIPPED CIRCUIT Message will be returned. + +If an UNEQUIPPED CIRCUIT Message is received indicating a circuit(s) that is known to the recipient, the indicated circuit(s) should be removed from service and the situation should be reported to the maintenance system for further intervention. The UNEQUIPPED CIRCUIT message is not to be acknowledged by the recipient. + +### 3.1.19.7 Field Elements + +This sub-clause defines the generic error handling to be applied to the field elements found in the *Old BSS to New BSS Information*, *New BSS to Old BSS Information* and *Inter-System Information* information elements. + +All field elements shall be treated as non-essential. + +The following events shall not be regarded as errors by the recipient: + +- spare bits with an unexpected value in any field element; +- the use of additional octets in any field element; +- a missing field element; +- a field element whose length is either too short or too long. + +When the recipient detects one or more of these events the receiving entity shall ignore the information that it is unable to understand and treat the message on the basis of the information that remains: + +- when an unknown field element identifier is encountered, the unknown field element shall be skipped and the receiver shall continue processing any remaining field elements; +- when more field elements of a particular type are received than are expected, the last one(s) shall be ignored; +- when a sub-field in a field element contains a value, which the recipient knows to be incorrect, the recipient shall either ignore that sub-field or ignore the entire field (treating it as if the field element had not been received); and +- when a sub-field in a field element contains a reserved value, the recipient shall ignore the entire field element (treating it as if the field element had not been received). + +### 3.1.20 Load Indication Procedure + +The purpose of the load indication procedure is to inform all neighbour BSS's about the traffic situation of a cell. + +The philosophy is to control the incoming handover traffic at the source, i.e. the BSS of the concerned cell informs all of its neighbour BSS's about the load situation. This is achieved by sending a LOAD INDICATION message to the neighbour BSS's. On receipt of the LOAD INDICATION message the BSS may analyse the load information and take the traffic load into consideration when deciding a handover. + +The algorithm in which the BSS decides on starting a Load Indication procedure is operator dependent. + +The implementation of the Load Indication procedure shall be regarded as optional, that means, if this procedure is not used, the Load Indication message may be ignored by these network elements. + +### 3.1.20.1 Operation of the procedure + +The procedure operates as follows: + +The BSS shall send the LOAD INDICATION message to the MSC with the following information: + +- Cell Identifier of the cell where the traffic load situation takes place (Cell Identifier information element). +- The Time indication information element contains the time where the traffic load information shall be valid on the receiving side. +- The Cell identifier list information element contains the cell identifier of the affected neighbour cells. +- The information about the total number of channels accessible or in use, and the information about the current number of channels available for each reported channel type on the indicated cell (Resource situation information element). +- The reason for sending this message (Cause information element). + +On receipt of the LOAD INDICATION message, the MSC transmits this message to all BSS's as derived from the Cell identifier list Information Element. + +NOTE: In the case where more than one indicated cells in the cell identifier list IE belong to the same BSS, the MSC should try to send the LOAD INDICATION message only once to this BSS. + +With each reception of a LOAD INDICATION message from the MSC the target BSS shall analyse the resource information and adapt the handover traffic either from all cells of the BSS-area or only from the cells contained in the Cell identifier list Information Element to the cell indicated in the Cell identifier Information Element. The BSS shall ignore all Cell identifiers for cells which do not belong to its area. + +In the case where the BSS receives a LOAD INDICATION message without the Resource situation information element, that means the indicated cell is not able to perform incoming handover requests and the receiving BSS may stop the whole handover traffic to this cell. + +The traffic load information shall only be valid the time as indicated in the Time indication Information Element. The control timer shall be stopped with the receipt of a new LOAD INDICATION message and restarted with the new value. If the Time field contains the value 0, the load information is no longer valid. + +### 3.1.21 Voice group call service and voice broadcast service call set-up and resource assignment + +To set-up a VGCS/VBS call the MSC initiates the VGCS/VBS set-up procedure to the BSS. The MSC can then allocate resources to the VGCS/VBS call by initiating the VGCS/VBS Assignment procedure. If a priority IE is included in the VGCS/VBS ASSIGNMENT REQUEST message then the priority level in this Priority IE takes precedence over any priority level that may have been included in the VGCS/VBS SETUP message. + +The BSS and MSC may indicate the support of some optional features through the VGCS/VBS SETUP and VGCS/VBS SETUP ACK messages. To support an optional feature both the VGCS/VBS SETUP and VGCS/VBS SETUP ACK messages must indicate that the feature is supported. The BSS shall only indicate the support of a given optional feature in the VGCS/VBS SETUP ACK message if the MSC had indicated its support of this feature in the VGCS/VBS SETUP message. Support of the following features may be indicated through these messages: + +- A-interface circuit sharing; +- A-interface link sharing; +- Talker priority; +- Group call re-establishment by the BSS; +- Talker channel parameter. + +### 3.1.21.1 Successful operation + +To initiate a VGCS/VBS call set-up procedures the MSC sends to the BSS a VGCS/VBS SETUP message across VGCS/VBS call controlling SCCP connection. This connection is established for the life time of the VGCS/VBS call. + +The BSS allocates resources to the call and returns VGCS/VBS SETUP ACK message to the MSC. + +When the MSC supports talker priority it shall indicate its support in each VGCS/VBS SETUP message. If the VGCS/VBS SETUP message indicates support of talker priority and the BSS supports talker priority, then the VGCS/VBS SETUP ACK message shall indicate support of talker priority. The network supports talker priority if both the MSC and BSS indicate their support in the VGCS/VBS SETUP and VGCS/VBS SETUP ACK messages, respectively. + +If the BSS supports one of the requested types of A-interface resource sharing (that are indicated by the MSC in the VGCS/VBS SETUP message) it includes the supported type (i.e. either A-interface circuit sharing or A-interface link sharing) in the VGCS/VBS SETUP ACK. + +An MSC or BSS supporting A-interface link sharing shall also support the procedures for group call re-establishment by the BSS. The network supports Group call re-establishment by the BSS if both the MSC and BSS indicate their support of this feature in the VGCS/VBS SETUP and VGCS/VBS SETUP ACK messages respectively, or if both the MSC and BSS indicate that they support A-interface link sharing in the VGCS/VBS SETUP or VGCS/VBS SETUP ACK messages, respectively. An MSC or BSS shall explicitly indicate support of the feature "group call re-establishment by the BSS" in the VGCS Feature Flags IE only, if the feature is supported in a configuration without A-interface link sharing. + +When the MSC supports talker channel parameter and requires a dedicated channel to be established for any talker in the cell for a specific group call it shall explicitly indicate its configuration in each VGCS/VBS SETUP message. If the VGCS/VBS SETUP message indicates configuration of talker channel parameter and the BSS supports talker channel parameter, then the VGCS/VBS SETUP ACK message shall indicate its support and the BSS shall establish and maintain a dedicated traffic channel for any talker in that group call in the cell. + +### 3.1.21.2 VGCS/VBS call set-up abnormal cases + +If the BSS detects that the VGCS/VBS call is already set-up it will clear all resources associated with the previous call and proceed with the new call. + +If the VGCS Feature Flags IE in the VGCS/VBS SETUP ACK message indicates the support of an optional feature that was not indicated as supported in the VGCS Feature Flags IE in the VGCS/VBS SETUP message, then the MSC shall send a CLEAR COMMAND via the VGCS/VBS call controlling SCCP connection to the BSS and release the call control SCCP connection. + +### 3.1.21.3 VGCS/VBS call set-up failure + +If the BSS can not set-up the VGCS/VBS call then it will send a VGCS/VBS SETUP REFUSE message to the MSC. + +## 3.1.22 Voice group call service and voice broadcast service Assignment procedure + +The purpose of the VGCS/VBS Assignment procedure is to ensure that the correct dedicated radio resources are allocated to the VGCS/VBS call on a per cell basis. In case of A-interface link sharing the procedure has to ensure that the correct dedicated resources are allocated to the VGCS/VBS call on a per BSS basis. In order to support this procedure the MSC sets up a VGCS/VBS resource controlling SCCP connection to the BSS. This connection is then used to support all BSSAP messages related to the dedicated resource(s). + +The MSC can command that the radio resources are either allocated immediately or delayed. + +### 3.1.22.1 Successful operation + +The VGCS/VBS call controlling SCCP connection shall be established before the VGCS/VBS Assignment procedure takes place. + +The MSC initiates the VGCS/VBS Assignment procedure to the BSS by sending a VGCS/VBS ASSIGNMENT REQUEST on a VGCS/VBS resource controlling SCCP connection. If an IP based user plane interface is supported, the Codec List (MSC Preferred), shall be included in the VGCS/VBS ASSIGNMENT REQUEST message. If the MSC + +requests an IP based user plane connection, the VGCS/VBS ASSIGNMENT REQUEST message shall include the "AoIP Transport Layer Address" allocated by the MGW and a Call Identifier. In the case of a ciphered group call the MSC shall provide the BSS with the VSTK and VSTK\_RAND. These parameters are used to derive the voice group or broadcast group ciphering key as described in 3GPP TS 43.020. + +If the MSC and BSS have indicated the support of a A-interface circuit sharing in the VGCS/VBS SETUP and VGCS/VBS SETUP ACK messages respectively, the MSC shall include the same CIC or the same Call Identifier, AoIP Transport Layer Address and Codec List (MSC Preferred) in case of AoIP, Channel type and Downlink DTX flag in all of the VGCS/VBS ASSIGNMENT REQUEST messages that are sent to the BSS for a given group call. + +The management of priority levels is implementation dependent and under operator control. Priority rules to handle VBS and VGCS calls are defined in TS 23.067 and 24.067. + +If queuing applies and neither A-interface link sharing nor group call re-establishment are being used, new requests which cannot be assigned immediately are put in the queue according to the indicated priority levels (see sub-clause 3.1.22.4). + +The priority levels and the preemption indicators may (singularly or in combination) be used to determine whether the assignment has to be performed unconditionally and immediately. This may lead to triggering of the preemption procedure which may then cause the forced release or forced handover of a lower priority connection if no free resource is immediately available. + +The process and the extent of the preemption procedure is operator dependent, however, the preemption indicators (refer to sub-clause 3.2.2.18.), if given in the VGCS/VBS ASSIGNMENT REQUEST shall be treated on a per connection basis as follows: + +- if the "Preemption Capability indicator" bit is set to 1, then this allocation request can trigger the running of the preemption procedure. +- if the "Preemption Capability indicator" bit is set to 0, then this allocation request cannot trigger the preemption procedure. +- if the "Preemption Vulnerability" bit is set to 1, then this connection is vulnerable and shall be included in the preemption process or procedure and as such may be subject to forced release or forced handover of a talker in group transmit mode. +- if the "Preemption Vulnerability" bit is set to 0, then this connection is not vulnerable to preemption and shall not be included in the preemption process and as such may not be subject to forced release or forced handover of a talker in group transmit mode. +- if no Priority Information Element has been received, both "Preemption Capability" and "Preemption Vulnerability" bits shall be regarded as set to 0. + +The MSC shall control VGCS/VBS radio resource allocation on demand to be enabled or disabled by including "Assignment Requirement" IE in VGCS/VBS ASSIGNMENT REQUEST and optionally in VGCS/VBS AREA CELL INFO. The MSC uses the "Assignment Requirement" IE to control whether the BSS is allowed to de-allocate the VGCS/VBS radio resources before the end of the call. If the *Assignment Requirement* IE is not included in the VGCS/VBS AREA CELL INFO message, the method of radio resource allocation for the cells in the *Cell Identifier List Segment* IE shall be the same as the one last indicated in VGCS/VBS ASSIGNMENT REQUEST or VGCS/VBS AREA CELL INFO. + +When the MSC and BSS have indicated the support of a A-interface circuit sharing, the BSS shall select one channel rate and one speech version for use in all cells for the group call that are using the same shared circuit or shared IP address and UDP port value in case of AoIP, based on the first accepted VGCS/VBS ASSIGNMENT REQUEST message that is using this circuit or IP address and UDP port value in case of AoIP. + +The BSS will return VGCS/VBS ASSIGNMENT RESULT to the MSC to inform the MSC of the resources allocated by the BSS for the concerned cell. The BSS shall include a Circuit Identity Code information element in the VGCS/VBS ASSIGNMENT RESULT message indicating the terrestrial circuit which is used for the VGCS/VBS call, if the BSS allocates the circuit. If the circuit was allocated by the MSC, the BSS may include the Circuit Identity Code information element (containing the same value as sent by the MSC) in the VGCS/VBS ASSIGNMENT RESULT message. If AoIP is used, the BSS shall include AoIP Transport Layer Address, Call Identifier (containing the same value as sent by the MSC in the VGCS/VBS ASSIGNMENT REQUEST message) and Speech Codec (BSC-Chosen) information elements. + +In case of A-interface circuit sharing and AoIP is used, AoIP Transport Layer Address, Call Identifier and Speech Codec (BSC-Chosen) information elements shall have the same value for all VGCS/VBS ASSIGNMENT RESULT messages. + +If the MSC and BSS have indicated the support of a A-interface circuit sharing, the BSS shall return a VGCS/VBS ASSIGNMENT RESULT message for each received VGCS/VBS ASSIGNMENT REQUEST message that indicates the use of the same CIC or AoIP Transport Layer Address and Call Identifier in case of AoIP, Channel Type and Downlink DTX flag. The SCCP connections shall be handled in the same manner irrespective of whether A-interface circuit sharing is used. + +In case of A-interface link sharing a list of the cells belonging to the group call area is included in the VGCS/VBS ASSIGNMENT REQUEST. If the list does not completely fit into the VGCS/VBS ASSIGNMENT REQUEST message or if different methods of radio resource allocation are to be used for different cells controlled by the BSS or the list is segmented because the cell identities could not be contained in one message for the chosen cell discriminator, the remaining part of the list is sent in VGCS/VBS AREA CELL INFO messages. The VGCS/VBS ASSIGNMENT REQUEST message is sent first followed by one or more VGCS/VBS AREA CELL INFO messages until the complete list of cells has been transferred to the BSS. The Cell Identifier IE of the VGCS/VBS ASSIGNMENT REQUEST message shall indicate the cell of origin, if controlled by that BSS. In the other case no further information shall be included in this IE. The Cell identification discriminator shall be set to indicate that no cell is associated with the transaction. See subclause 3.2.2.17. The *Cell Identifier List Segment* IE shall be included in the VGCS/VBS ASSIGNMENT REQUEST message if one or more cells have to be identified by this IE or one or more VGCS/VBS AREA CELL INFO messages is to follow. The BSS is responsible for the establishment and re-establishment of the radio resources for the different cells. + +In case of A-interface link sharing, if the originating cell is served by the BSS, the VGCS/VBS ASSIGNMENT RESULT message shall be returned once the resource for this cell is established. + +In the case of A-interface link sharing, if the originating cell is not served by the BSS the, the BSS shall return the VGCS/VBS ASSIGNMENT RESULT message even if no resource can be established. If resources could not be established in any cell, the Channel field in the *Chosen Channel* IE shall be set to "none" and a VGCS/VBS ASSIGNMENT STATUS message shall be sent to the MSC as soon as the first cell is established. + +Timer Tast is (re-)started after sending either a VGCS/VBS ASSIGNMENT RESULT or a VGCS/VBS ASSIGNMENT STATUS message to the MSC. The timer is stopped when the associated A-interface link is released. The A-interface link established by this procedure is not pre-emptable and will only be released if the call is released. This A-interface link is shared by the control and user plane of all group call channels involved in the VGCS/VBS call at the given BSS. + +In case of A-interface link sharing and when the network supports uplink access option (i) as defined in 3GPP TS 43.068 (i.e. an indication in the uplink busy instructs the MS to use the group call channel to send the uplink access message if the talker on the group call channel is not in the same cell as the MS) the BSS and MSC shall include talker priority information in A-interface messages on the resource controlling SCCP connection as specified in subclause 3.2.1. The Talker Priority information may be used to distinguish between messages related to the current talker and messages related to another subscriber requesting the uplink. + +The BSS shall initiate the radio interface notification procedure on the NCH of the cell in which the call is to take place, this may continue at regular intervals until the call is released or the cell has been reported as released for the voice group or broadcast call. The BSS may on SACCH indicate that a change of notification has occurred and/or initiate notification on FACCH. + +In the case where the BSS deallocates/allocates resources to the cell and neither A-interface link sharing or group call re-establishment by the network are supported, the BSS sends an VGCS/VBS ASSIGNMENT RESULT message on the VGCS/VBS resource controlling SCCP connection associated to the cell. + +In the case where the BSS deallocates resources to the cell and group call re-establishment by the BSS is supported by the network and A-interface link sharing is not being used, then the BSS sends an VGCS/VBS ASSIGNMENT STATUS message on the VGCS/VBS resource controlling SCCP connection associated to the cell indicating the reason for the release. + +In case of A-interface link sharing the BSS waits for timer Tast to expire before it sends to the MSC a report of the cells whose status has changed since the most recently sent VGCS/VBS ASSIGNMENT STATUS message (or group of VGCS/VBS ASSIGNMENT STATUS messages) or VGCS/VBS ASSIGNMENT RESULT message was generated. This report is sent using one or, if needed, more VGCS/VBS ASSIGNMENT STATUS messages. If no change occurred the message shall not be sent. Timer Tast shall be re-started each time it expires. A report (comprising one or, + +if needed, more VGCS/VBS ASSIGNMENT STATUS messages) shall be sent immediately and timer Tast shall be re-started when the group call is established in all cells served by this A-Interface link for the first time. + +The VGCS/VBS ASSIGNMENT STATUS message shall indicate to the MSC cells where + +- the call is established; or +- the BSS will attempt to establish the call; or +- the call is released because there is no user present in that cell; or +- the BSS will not attempt to establish the call. + +NOTE: These lists may not be applicable in all cases. The usage of the lists varies according to the features supported by the network. + +A cell shall appear in at most one list within a given VGCS/VBS ASSIGNMENT STATUS message and shall appear at most once within a report comprising a group of VGCS/VBS ASSIGNMENT STATUS messages. + +In the case of voice group calls, if the MSC has informed the BSS to which voice group call the originator MS belongs to, the BSS may decide to modify the originator dedicated channel into a voice group call channel relating to the group call reference. If the BSS modifies the channel it will send the VGCS/VBS ASSIGNMENT RESULT message on the resource controlling SCCP connection and then immediately afterwards send a CLEAR REQUEST cause "Joined group call channel" on the originator dedicated connection. + +### 3.1.22.2 VGCS/VBS Assignment abnormal cases + +In the abnormal case, where a BSS detects that a voice broadcast or voice group call already exists with the same group call reference in a cell (this may occur due to SCCP problems), the BSS shall release the radio resources associated with the cell for the present existing voice broadcast or voice group call and shall allocate resources to the new call. + +If the requested channel type indicated in the VGCS/VBS ASSIGNMENT REQUEST message is not available in the BSS, then an VGCS/VBS ASSIGNMENT FAILURE message shall be returned to the MSC. The appropriate failure cause will be included in the message (Cause value: "requested transcoding/rate adaptation unavailable" or "requested speech version unavailable" or "Requested Codec Type or Codec Configuration unavailable" or "Requested Codec Type or Codec Configuration not supported" or "Requested A-Interface Type unavailable" or "Requested A-Interface Type not supported"). + +If the MSC requested an IP-bearer for the A-Interface by providing the AoIP Transport Layer Address and not providing a Circuit Identity Code, but the BSS is not able to use an IP-bearer, then the BSS shall not allocate a Circuit Identity Code on its own, even if the Codec List (MSC Preferred) included a Codec Type with the PT bit set to "1", but shall return an VGCS/VBS ASSIGNMENT FAILURE message to the MSC with the Cause value "Requested A-Interface Type unavailable". + +If the BSS receives a VGCS/VBS ASSIGNMENT REQUEST message calling up a terrestrial circuit that is already assigned to another call then a VGCS/VBS ASSIGNMENT FAILURE message will be returned with a Cause value of: "terrestrial circuit already allocated" and no action will be taken on the radio interface. + +If the BSS receives a VGCS/VBS ASSIGNMENT REQUEST message allocating a terrestrial circuit which has been blocked by a previous blocking procedure, then an VGCS/VBS ASSIGNMENT FAILURE message shall be sent (Cause value: "requested terrestrial resource unavailable"). A BLOCK message (not repeated and not guarded by timer T1) shall be sent for that concerned terrestrial circuit. + +If the BSS receives a VGCS/VBS ASSIGNMENT REQUEST message that contains an Encryption Information IE that indicates that the radio resource is to be ciphered, but the message does not contain both the VSTK\_RAND and VSTK information elements, then a VGCS/VBS ASSIGNMENT FAILURE message shall be sent (Cause value of: "invalid message contents"). + +When the voice group call has been configured to use A-interface circuit sharing and either the VGCS/VBS ASSIGNMENT REQUEST message does not contain a CIC or AoIP Transport Layer Address, Call Identifier and Codec List (MSC preferred) in case of AoIP, or the VGCS/VBS ASSIGNMENT REQUEST messages contains a different CIC or different AoIP Transport Layer Address, Call Identifier and Codec List (MSC preferred) in case of AoIP, Channel Type or Downlink DTX flag from that sent in a previous VGCS/VBS ASSIGNMENT REQUEST message for a given group call within a given BSS, then the BSS shall reply with VGCS ASSIGNMENT FAILURE message (Cause value: "invalid message contents"). Also, if the cell identified in the VGCS/VBS ASSIGNMENT + +message does not support the selected channel rate and speech version, then the BSS shall reply with VGCS ASSIGNMENT FAILURE message (Cause value: "requested transcoding/rate adaptation unavailable" or "requested speech version unavailable" or "Requested Codec Type or Codec Configuration unavailable" or "Requested Codec Type or Codec Configuration not supported" or "Requested A-Interface Type unavailable" or "Requested A-Interface Type not supported"). + +If the BSS receives, in the case of A-interface link sharing, more than one VGCS/VBS ASSIGNMENT REQUEST message with the same group call reference, the BSS shall release the radio resources and terrestrial resources associated with the present existing voice broadcast or voice group call and shall allocate resources to the new call and the BSS shall stop timer Tast. (The timer will be started again after the VGCS/VBS ASSIGNMENT RESULT message is sent.) + +If, in the case of A-interface link sharing, the BSS receives in the Cell Identifier List Segment IEs (contained within VGCS/VBS ASSIGNMENT REQUEST or VGCS/VBS AREA CELL INFO messages) multiple references to the same cell (either within a single IE or within multiple IEs), the BSS shall send either a CLEAR REQUEST (if a VGCS/VBS ASSIGNMENT RESULT message has already been sent) or a VGCS/VBS ASSIGNMENT FAILURE message (if no VGCS/VBS ASSIGNMENT RESULT message has been sent) with cause value "Invalid Message Contents" to the MSC. + +If, in the case of A-interface link sharing, the BSS receives a VGCS/VBS AREA CELL INFO message with a sequence number higher than the sequence length (as indicated in the VGCS/VBS ASSIGNMENT REQUEST message), the BSS shall send either a CLEAR REQUEST (if a VGCS/VBS ASSIGNMENT RESULT message has already been sent) or a VGCS/VBS ASSIGNMENT FAILURE message (if no VGCS/VBS ASSIGNMENT RESULT message has been sent) with cause value "Invalid Message Contents" to the MSC. If, in case of A-interface circuit sharing and AoIP, the MSC receives different Speech Codec information element value within VGCS/VBS ASSIGNMENT RESULT messages, the MSC shall send CLEAR COMMAND message with cause value "Requested Codec Type or Codec Configuration not supported" to the BSC. + +### 3.1.22.3 VGCS/VBS Assignment failure + +In the case where the VGCS/VBS call is unknown by the BSS, the BSS shall return the VGCS/VBS ASSIGNMENT FAILURE message (cause "VGCS/VBS call non existent"). + +In the case where no radio resource can be allocated to the VGCS/VBS call, the BSS shall return the VGCS/VBS ASSIGNMENT FAILURE message (cause "No radio resource available"). + +In case of A-interface link sharing, the BSS shall return the VGCS/VBS ASSIGNMENT FAILURE message (cause "No radio resource available") if the originating service subscriber is served by the BSS and resources for the cell of origin cannot be allocated. + +In the case where no radio resource can be allocated to the VGCS/VBS call for channel establishment on demand and A-interface link sharing is not being used, the BSS shall return the CLEAR REQUEST message (cause "No radio resource available"). + +NOTE: In the case of A-interface link sharing, the BSS is responsible for the re-establishment and does not send the CLEAR REQUEST message. + +In the case where the MSC has attempted to assign a terrestrial circuit and an VGCS/VBS ASSIGNMENT FAILURE message has been returned then both the MSC and the BSS shall consider that the terrestrial circuit is idle (except already allocated to another call or to another connection in the same VGCS/VBS call if A-interface circuit sharing has been configured or blocked terrestrial circuit) and therefore no explicit clearing sequence is needed. + +If the BSS is unable to allocate any resources for a cell not serving the originating subscriber when it receives a VGCS/VBS ASSIGNMENT REQUEST message and group call re-establishment by the BSS is supported by the network but A-interface link sharing is not being used, then the BSS shall send a VGCS/VBS ASSIGNMENT RESULT message with a *Chosen Channel* IE in which the channel field is set to "none". Additionally the BSS shall send a VGCS/VBS ASSIGNMENT STATUS message to the MSC. + +NOTE: In case of A-interface link sharing the procedure in case the call cannot be established in any cell and the cell serving the originating subscriber is not parented by the BSS is described in sub-clause 3.1.22.1. + +In the case that group call re-establishment by the BSS is supported by the network but A-interface link sharing is not being used and the BSS receives a VGCS/VBS ASSIGNMENT REQUEST message for the cell serving the originating + +subscriber that requires resources that use failed equipment or resources that cannot be allocated because of congestion, then the BSS shall send to the MSC a VGCS/VBS ASSIGNMENT FAILURE message. + +### 3.1.22.4 VGCS/VBS Queuing Indication + +This subclause is not applicable if A-Interface link sharing or group call re-establishment by BSS is used. + +In a BSS supporting the VGCS/VBS message queuing, the purpose of the VGCS/VBS QUEUING INDICATION message is to inform the MSC about a delay in the allocation of the necessary dedicated radio resources. + +When a VGCS/VBS ASSIGNMENT REQUEST message is received which cannot be served immediately due to lack of available resources and if the "Queuing Allowed" bit in the Priority Information Element indicates that queuing is allowed, then the request shall be put into a queue and timer T14 shall be started. The timer value T14 specifies the maximum queuing delay and is determined by the operator. The VGCS/VBS QUEUING INDICATION message shall be returned to the MSC. + +The queuing procedure shall be terminated with a successful or unsuccessful assignment of the required traffic channel(s) by sending a VGCS/VBS ASSIGNMENT RESULT or a VGCS/VBS ASSIGNMENT FAILURE message, respectively, to the MSC. + +If the timer T14 expires the VGCS/VBS ASSIGNMENT REQUEST message shall be removed from the queue and a VGCS/VBS ASSIGNMENT FAILURE message shall be sent to the MSC, with the Cause "no radio resource available" (refer to sub-clause 3.1.22.3). + +If a resource in a queue could be successfully established, the timer T14 is stopped. + +### 3.1.23 (void) + +### 3.1.24 Voice group call uplink control procedure - talker priority not supported by the network + +In the case of voice group calls the uplink resource allocated to the call is controlled by the uplink control procedure. The uplink control procedure uses messages sent on the VGCS/VBS controlling SCCP connection set-up by the VGCS/VBS call set-up procedure. + +The procedure is split into three procedures: uplink allocation; uplink release; & uplink seize. + +The uplink allocation is controlled by the BSSs and group call anchor MSC. The BSS controls the uplink access for the cells in the group call area which are under its control. The group call anchor MSC controls the uplink access for the complete service area. Any allocation of the uplink access by a BSS may be refused later by the group call anchor MSC (due to the allocation of the uplink by other BSSs involved in the same voice group call). + +The uplink release & uplink seize procedure is controlled and initiated by the MSC, the BSS obeys the MSC's requests. + +When the voice group call is initially set-up the state of the uplink in each BSS is such that the uplink is seized. The MSC will control the state of the uplink in each BSS by use of the uplink release and uplink seize procedures. Before an uplink may be allocated by the BSS, the MSC must have released the uplink by initiating the uplink release procedure. + +#### 3.1.24.1 Uplink allocation procedure + +The uplink allocation procedure allows a listening user in a voice group call to talk on the uplink of the TCH dedicated to the voice group call in the cell. + +The uplink allocation procedure can only occur once the group call anchor MSC has released the uplink (by use of the uplink release procedure). + +When a mobile relinquishes the uplink or the BSS detects that the MS is no longer connected, the BSS sends to the MSC an UPLINK RELEASE INDICATION message with cause value "Call control" or "Radio interface failure" respectively. Then the BSS shall initiate the radio interface uplink free procedure. + +### 3.1.24.1.1 Successful uplink allocation operation + +On reception of a request to talk, the BSS sends an UPLINK REQUEST message to the MSC. The MSC sends the UPLINK REQUEST ACKNOWLEDGE message to confirm to the BSS that the uplink is granted to the requesting MS. The MSC also sends to all the other BSSs in the voice group call an UPLINK SEIZED COMMAND message. + +The BSS sends UPLINK REQUEST CONFIRMATION message with the complete layer information, once the radio link has been established. The layer information may include the ciphering key sequence number. + +### 3.1.24.1.2 Unsuccessful uplink allocation operation + +In the case that the radio link could not be established the BS sends the Uplink release indication with the cause "Radiolink interface message failure". + +In the case the MSC does not want to grant the uplink, the MSC will send an UPLINK REJECT COMMAND message to the appropriate BSS. On reception of this the BSS will release the uplink for the requesting MS. + +### 3.1.24.2 Uplink release procedure + +This procedure shall be used in one of the following cases: + +- the group call anchor MSC detects that none of the parties involved in a voice group call are talking . The Uplink release procedure is then used to allow the listening subscribers to talk; +- the group call anchor or relay MSC detects that the talker has left the Group Call Area. + +To initiate this procedure the group call anchor MSC sends the UPLINK RELEASE COMMAND message to each BSS involved in the voice group call. When the BSS receives the Uplink release request command, the BSS shall initiate the radio interface uplink release procedure. + +### 3.1.24.3 Uplink seize procedure + +This procedure shall be used by the MSC to inform a given BSS that the uplink has been successfully granted to a talking subscriber in another BSS area. To initiate the procedure the MSC sends UPLINK SEIZED COMMAND message to that given BSS. On reception of the UPLINK SEIZED COMMAND message the BSS will initiate the radio interface uplink busy procedure. + +## 3.1.24a Voice group call uplink control procedure - talker priority supported by the network + +### 3.1.24.a.1 General + +Each network node that is involved in the group call shall maintain a record of the current call talker priority setting. The priority setting may be one of the following: + +- normal subscriber request; +- privileged subscriber request; +- emergency subscriber request. + +In the case of voice group calls the uplink resource allocated to the call is controlled by the uplink control procedure. The uplink control procedure uses messages sent on the VGCS/VBS controlling SCCP connection set-up by the VGCS/VBS call set-up procedure. + +The procedure is split into five procedures: uplink allocation; uplink release; uplink seize, emergency reset and talker information. + +The uplink allocation is controlled by the BSSs and group call anchor MSC. The BSS controls the uplink access for the cells in the group call area which are under its control. The group call anchor MSC controls the uplink access for the complete service area. Any allocation of the uplink by a BSS may be refused later by the group call anchor or relay MSC (due to the allocation of the uplink by other BSSs involved in the same voice group call or because the mobile station was not permitted to use the talker priority in the uplink request). + +The uplink release, uplink seize and emergency reset procedure is controlled and initiated by the MSC. The BSS obeys the MSC's requests. + +When the voice group call is initially set-up the state of the uplink in each BSS is such that the uplink is seized. The MSC will control the state of the uplink in each BSS by use of the uplink release and uplink seize procedures. + +### 3.1.24a.2 Uplink allocation procedure + +The uplink allocation procedure allows a listening user in a voice group call to talk on the uplink of the TCH dedicated to the voice group call in the cell. + +The uplink allocation procedure can occur in the following situations: + +- once the group call anchor MSC has released the uplink (by use of the uplink release procedure); +- or when there is a talker request with a higher priority than that of the current talker. + +When a mobile relinquishes the uplink or the BSS detects that the MS is no longer connected, the BSS sends to the MSC an UPLINK RELEASE INDICATION message with cause value "Call control" or "Radio interface failure" respectively. Then the BSS shall initiate the radio interface uplink free procedure if there is no current talker. + +#### 3.1.24a.2.1 Successful uplink allocation operation + +##### 3.1.24a.2.1.1 Normal Priority Request + +Behaviour is as defined in sub-clause 3.1.24.1. + +##### 3.1.24a.2.1.2 Privileged or Emergency Priority Request via Uplink Access procedure + +On reception of a request to talk with privileged or emergency priority, the BSS sends an UPLINK REQUEST message to the MSC. The BSS sends UPLINK REQUEST message with the Layer 3 information once the link has been established on the radio interface. The Layer 3 information shall include the MS identity and may include the ciphering key sequence number. + +The MSC sends the UPLINK REQUEST ACKNOWLEDGE message to confirm to the BSS that the uplink is granted to the requesting MS. This message shall contain the talker priority so that the BSS is able to determine which uplink request is being acknowledged. It shall also contain the status of the emergency mode. The BSS shall update the current talker priority when the priority in the UPLINK REQUEST ACKNOWLEDGE message is greater than the current talker priority, and releases the uplink for an MS being pre-empted if it is served by this BSS. + +The MSC also sends to all the other BSSs in the voice group call an UPLINK SEIZED COMMAND message, containing the talker priority. Additionally, if the uplink priority was 'Emergency', then the UPLINK SEIZED COMMAND message shall also contain the Emergency set indication IE. + +The BSS shall compare the talker priority received in an UPLINK SEIZED COMMAND message with the current talker priority. The BSS shall update the current talker priority when the priority in the UPLINK SEIZED COMMAND message is greater than the current talker priority, and releases the uplink for an MS being pre-empted if it is served by this BSS. The BSS shall discard an UPLINK SEIZED COMMAND message that contains a talker priority that is less than or equal to the current talker priority. + +When the uplink request pre-empts the current talker, the MSC shall send a CLEAR COMMAND to the talker that is being pre-empted, if the current talker is on a dedicated channel. The cause field shall be set to 'Call Control'. + +##### 3.1.24a.2.1.3 Privileged or Emergency Priority Request via Priority Uplink Request procedure + +On reception of a request to talk with privileged or emergency priority, the BSS sends an UPLINK REQUEST message to the MSC. The UPLINK REQUEST message shall include the MS identity. + +The MSC sends the UPLINK REQUEST ACKNOWLEDGE message to confirm to the BSS that the uplink is granted to the requesting MS. This message shall contain the talker priority so that the BSS is able to determine which uplink request is being acknowledged. It shall also contain the status of the emergency mode. The BSS shall update the current talker priority when the priority in the UPLINK REQUEST ACKNOWLEDGE message is greater than the current talker priority, and release the uplink for an MS being pre-empted if it is served by this BSS. + +The MSC also sends to all the other BSSs in the voice group call an UPLINK SEIZED COMMAND message, containing the talker priority. Additionally, if the uplink priority was 'Emergency', then the UPLINK SEIZED COMMAND message shall also contain the Emergency Set Indication IE. + +The BSS shall compare the talker priority received in an UPLINK SEIZED COMMAND message with the current talker priority. The BSS shall update the current talker priority when the priority in the UPLINK SEIZED COMMAND message is greater than the current talker priority, and release the uplink for an MS being pre-empted if it is served by this BSS. The BSS shall discard an UPLINK SEIZED COMMAND message that contains a talker priority that is less than or equal to the current talker priority. + +The BSS sends the UPLINK CONFIRM message with the Layer 3 information once the link to the requesting MS has been established on the radio interface. The Layer 3 information shall include the MS identity and may include the ciphering key sequence number. + +### 3.1.24a.2.2 Unsuccessful uplink allocation operation + +#### 3.1.24a.2.2.1 Normal Priority Uplink Request + +Behaviour is as defined in 3.1.24.1.2. + +Additionally, in the case the UPLINK REQUEST message contained a talker priority that was less than or equal to the current talker priority that is stored in the MSC, the MSC sends an UPLINK REJECT COMMAND message to the appropriate BSS, containing the priority that was in the UPLINK REQUEST message that was being rejected and the current talker priority. The cause field shall be set to 'Call Control'. On reception of this message the BSS will release the uplink for the requesting MS that is being rejected, if not already released. The BSS shall set its current talker priority to the current talker priority that was received in the UPLINK REJECT COMMAND message. + +The BSC shall compare the talker priority received in an UPLINK SEIZED COMMAND message with the current talker priority. If the priority is less than the current priority, then the BSC shall discard the command. + +#### 3.1.24a.2.2.2 Privileged or Emergency Uplink Request via Uplink Access procedure + +In the case that the radio link could not be established the BSS sends the Uplink release indication with the cause "Radiolink interface message failure". + +In the case the MSC does not want to grant the uplink, the MSC will send an UPLINK REJECT COMMAND message to the appropriate BSS. The UPLINK REJECT COMMAND message shall contain the talker priority of the request that is being rejected together with the current talker priority so that the BSS is able to determine which uplink request is rejected. On reception of this the BSS will release the uplink for the requesting MS, if not already released, and set the current talker priority to the value of the priority in the Current Talker Priority IE received in the UPLINK REJECT COMMAND message. + +In the case the UPLINK REQUEST message contained a talker priority that was less than or equal to the current talker priority that is stored in the MSC, the MSC sends an UPLINK REJECT COMMAND message to the appropriate BSS, containing the priority that was in the UPLINK REQUEST that was being rejected and the current talker priority. The cause field shall be set to 'Call Control'. On reception of this the BSS will release the uplink for the requesting MS and set the current talker priority to the value of the priority in the Current Talker Priority IE received in the UPLINK REJECT COMMAND message. + +If an MSC receives an UPLINK REQUEST message, but either no mobile station identity is provided in the Layer 3 information or the mobile station is not permitted to send the requested priority, then the MSC shall send an UPLINK REJECT COMMAND message to the appropriate BSS, containing the requested priority and the current talker priority. The cause field shall be set to 'Requested option not authorised'. On reception of this the BSS will release the uplink for the requesting MS and set the current talker priority to the value of the priority in the Current Talker Priority IE received in the UPLINK REJECT COMMAND message. + +#### 3.1.24a.2.2.3 Privileged or Emergency Uplink Request via Priority Uplink Request procedure + +All other cases are as per sub-clause 3.1.24a.2.2.2, with the exception that there is no uplink for the BSS to release. + +### 3.1.24a.3 Uplink release procedure + +Behaviour is as defined in 3.1.24.2. + +### 3.1.24a.4 Uplink seize procedure + +This procedure shall be used by the MSC to inform a given BSS that the uplink has been successfully granted to a talking subscriber in another BSS area. To initiate the procedure the MSC sends UPLINK SEIZED COMMAND message to that given BSS. The UPLINK SEIZED COMMAND message shall contain the current talker priority and the status of the emergency mode. On reception of the UPLINK SEIZED COMMAND message the BSS will initiate the radio interface uplink busy procedure. + +### 3.1.24a.5 Emergency Reset procedure via UPLINK ACCESS message + +#### 3.1.24a.5.0 Successful + +On reception a request to reset the emergency mode, the BSS sends an EMERGENCY RESET INDICATION message to the MSC. The BSS sends the EMERGENCY RESET INDICATION message with the Layer 3 information once the link has been established on the radio interface. The Layer 3 information shall include the MS identity and may include the ciphering key sequence number. + +When the MSC receives a EMERGENCY RESET INDICATION message and the emergency mode is set, the MSC shall check that the mobile is allowed to issue the command. If the emergency mode is set and the mobile is allowed to issue the command, then the MSC shall send an EMERGENCY RESET COMMAND message to each BSS involved in the group call. + +The BSS on receipt of the EMERGENCY RESET COMMAND message shall reset the emergency mode. + +#### 3.1.24a.5.1 Unsuccessful + +The MSC shall discard the EMERGENCY RESET INDICATION message if the emergency mode is not set or the mobile station is not allowed to issue the command. + +### 3.1.24a.6 Emergency Reset procedure via PRIORITY UPLINK REQUEST message + +#### 3.1.24a.6.0 Successful + +On reception of a request to reset the emergency mode, the BSS sends an EMERGENCY RESET INDICATION message to the MSC. The EMERGENCY RESET INDICATION message shall include the MS identity. + +When the MSC receives an EMERGENCY RESET INDICATION message and the emergency mode is set, the MSC shall check that the mobile is allowed to issue the command. If the emergency mode is set and the mobile is allowed to issue the command, then the MSC shall send an EMERGENCY RESET COMMAND message to each BSS involved in the group call. + +The BSS on receipt of the EMERGENCY RESET COMMAND message shall reset the emergency mode. + +#### 3.1.24a.6.1 Unsuccessful + +As per subclause 3.1.24a.5.1 + +### 3.1.24b Talker Information + +The MSC may send a VGCS ADDITIONAL INFORMATION message containing information regarding the identity of the current talker to each BSS in the group call area. Each of these VGCS ADDITIONAL INFORMATION messages is sent on the group call's call controlling SCCP connection. In the case that the VGCS talker that is being pre-empted is on a dedicated channel, the MSC sends a VGCS ADDITIONAL INFORMATION message on the VGCS talker's dedicated SCCP connection. + +On reception of the VGCS ADDITIONAL INFORMATION message on the group call's call controlling SCCP connection, the BSS will initiate the transmission of the additional information on the radio interface in each cell in which the group call is active. + +On reception of the VGCS ADDITIONAL INFORMATION message on the VGCS talker's dedicated SCCP connection, the BSS will initiate the transmission of the additional information on the VGCS talker's dedicated channel. + +The MSC may also send the talker information (talker identity IE) in the UPLINK SEIZED COMMAND, UPLINK REQUEST ACKNOWLEDGE or UPLINK REJECT COMMAND messages. On reception of an UPLINK SEIZED + +COMMAND, UPLINK REQUEST ACKNOWLEDGE or UPLINK REJECT COMMAND message containing the talker identity IE, the BSC will initiate the transmission of the additional information on the radio interface in each cell in which the group call is active. + +### 3.1.24c SMS to ongoing VGCS call all + +The MSC may send a short message to the members that are participating in the voice group call by sending one or more VGCS SMS messages to each BSS that is in the group call area. Each VGCS SMS message transports a RP-Data message (see 3GPP TS 24.011) containing all or part of the short message. The VGCS SMS message is sent on the group call's call controlling SCCP connection. + +On reception of the VGCS SMS message on the group call's call controlling SCCP connection, the BSS will initiate the transmission of the RP-Data message on the VGCS group channel in each cell in which the group call is active. In the case that the VGCS talker is on a dedicated channel the BSC will also initiate the transmission of the RP-Data message on the VGCS talker's dedicated channel. + +### 3.1.24d Distributing application-specific data to ongoing VGCS call + +On reception of a Data Indication message or Data Indication 2 message (see 3GPP TS 44.018) an UPLINK APPLICATION DATA message may be sent from the BSS to the MSC on the group call's call controlling SCCP connection. + +On reception of an UPLINK APPLICATION DATA message from a BSS, the MSC may send a NOTIFICATION DATA message containing application-specific data and optionally the sender's mobile identity to each BSS in the group call area. Each of these NOTIFICATION DATA messages is sent on the group call's call controlling SCCP connection. + +On reception of a NOTIFICATION DATA message on the group call's call controlling SCCP connection, the BSS shall broadcast the notification data to all listeners and the talker by initiating the transmission of the data on the radio interface to each cell in which the group call is active (see 3GPP TS 44.018). + +Optionally the BSS may distribute the application-specific data immediately, upon receiving the application data from the MS. The application data will then be distributed to the cells within the BSS area belonging to the group call area the BSS shall indicate this in the Application Data Information IE to the MSC. In this case, the MSC shall not send the NOTIFICATION DATA message to that BSS. + +### 3.1.25 PDSS1 flow control + +The purpose of the PDSS1 flow control procedure is to inform the MSC that it should stop or resume transmission of PDSS1 data on this particular transaction. + +The BSS may on the relevant SCCP connection associated with an MS transaction send a SUSPEND message to the MSC to ask the MSC not to transmit DTAP messages carrying air interface layer 3 messages of the PDSS1 protocol. A typical reason is that too many messages are scheduled for transmission on the air interface. + +The BSS may on the relevant SCCP connection associated with an MS transaction send a RESUME message to the MSC to indicate to the MSC that DTAP messages carrying air interface layer 3 messages of the PDSS1 protocol may be transmitted (the typical reason is that congestion on the air interface signalling channel does no more exist). + +### 3.1.26 Circuit re-selection procedure + +This procedure has to be supported by a BSS if and only if it allocates the A interface circuits. + +The MSC can request the BSS to change the circuit allocated to a connection by sending a CHANGE CIRCUIT message to the BSS on the corresponding SCCP connection. The MSC releases the allocated circuit at the sending of the CHANGE CIRCUIT message. + +The MSC shall not start the circuit re-selection procedure if another procedure is on-going that may result in the change of the circuit (e.g. circuit re-selection, handover or clearing). + +At the reception of a CHANGE CIRCUIT message, and if the BSS is not already engaged in a procedure that normally results in the release of the allocated circuit (e.g. handover or clearing), the BSS allocates a new circuit and indicates it in CHANGE CIRCUIT ACKNOWLEDGE message sent back to the MSC. The BSS releases the previously allocated circuit after the sending of the CHANGE CIRCUIT ACKNOWLEDGE message. + +If the MSC receives a message from the BSS indicating the start of a procedure that may result in the change of the circuit (e.g. reception of HANDOVER REQUIRED or CLEAR REQUEST), the MSC shall abort the circuit re-selection procedure. + +The MSC may not be able to use the terrestrial resource that the BSS has indicated. In this case, the procedure is nevertheless considered terminated successfully, and it is up to the MSC to correct the situation, e.g., by a new circuit re-selection procedure. + +### 3.1.27 LSA handling + +The MSC may send the LSA INFORMATION message at any time during the lifetime of the relevant SCCP connection. The message is not acknowledged. + +The BSS shall store the LSA identity list internally for the connection and use it for the control of internal and external handover. + +In the case of overlapping LSAs, the LSA identity signalled in messages by the BSS towards the MSC shall be the LSA identity with the highest priority. + +Upon reception of a new lists of LSA identities the BSS will discard the previous LSA identity list and use the new LSA identity list. The BSS shall always accept the LSA identity list, but shall ignore LSA identities, which are not known. + +If the subscriber has LSA only access this has to be taken into account in the "Cell Identifier List (preferred)" in the HANDOVER REQUIRED message (see sub-clause "Generation of the HANDOVER REQUIRED message"). If the subscriber has LSA only access the LSA only access indicator is set to zero at an emergency call. + +Exclusive access cells may be included into "Cell Identifier List (preferred)" in the HANDOVER REQUIRED message (see sub-clause "Generation of the HANDOVER REQUIRED message") if at least one LSA identity defined in the exclusive access cell corresponds to any LSA identity received in the HANDOVER REQUEST or the latest LSA INFORMATION message. Exclusive access cells may also be included if the connection is an emergency call. + +### 3.1.28 Location Acquisition + +This procedure is utilized to support Location Services (see 3GPP TS 43.071). It is used to pass information transparently between the SMLC and BSS and request location of the target MS from the BSS. + +#### 3.1.28.1 (void) + +#### 3.1.28.2 Location request + +##### 3.1.28.2.1 Successful Operation + +PERFORM LOCATION REQUEST message may be sent in order to perform location procedure for the target MS. This message may be sent from the MSC to the BSS. This message may contain the following information: + +- Location type; +- GANSS Location type +- Cell Identifier; +- Classmark Information Type 3; +- LCS Client Type; +- Chosen Channel; +- LCS Priority; +- Quality of service; +- GPS Assistance Data; +- GANSS Assistance Data; + +- APDU, variable length octet string of which content is defined in 3GPP TS 49.031 and 3GPP TS 48.071; +- IMSI; +- IMEI. + +On receipt of the PERFORM LOCATION REQUEST message for positioning of the target MS, the BSS transfers the positioning request to the SMLC according to the procedures defined in 3GPP TS 43.059 and 3GPP TS 49.031 and awaits the result. The BSS then returns the result of positioning to the MSC in the PERFORM LOCATION RESPONSE message. This message contains following information: + +- Location estimate; +- Velocity estimate; +- Positioning data; +- GANSS positioning data. + +If assistance data was instead requested by the MSC for an MS, the BSS transfers the request to the SMLC according to the procedures defined in 3GPP TS 43.059 and 3GPP TS 49.031 and awaits the result. If the SMLC was able successfully to transfer this to the MS, the BSS shall return a PERFORM LOCATION RESPONSE message to the MSC. This message shall contain no parameters. The absence of an LCS Cause parameter in this case implies that the transfer was successful. + +Otherwise, if a deciphering keys were requested for LCS broadcast assistance data, the BSS transfers the request to the SMLC according to the procedures defined in 3GPP TS 43.059 and 3GPP TS 49.031 and awaits the result. If the SMLC has access to the appropriate keys, the BSS shall return a PERFORM LOCATION RESPONSE message to MSC. This message contains following information: + +- Deciphering Keys. + +### 3.1.28.2.2 Unsuccessful Operation + +If the BSS fails to respond to the PERFORM LOCATION REQUEST message it returns a PERFORM LOCATION RESPONSE message with a LCS cause value indicating the failure cause. Possible failure causes are listed in 3GPP TS 49.031. + +### 3.1.28.2.3 Abnormal cases + +The following condition may occur: + +If the MSC needs to abort previously initiated location request, it shall send the PERFORM LOCATION ABORT message to the BSS. As a result of reception of this message the BSS shall abort activities related to positioning of the target MS or assistance data delivery. The BSS shall return a PERFORM LOCATION RESPONSE with a cause value indicating the abortion of location request. + +### 3.1.28.2.4 Overload + +For location requests initiated by the MSC, the BSC may employ the same procedures defined for an SMLC in 3GPP TS 49.031 to alleviate an overload condition in the BSS. + +## 3.1.29 Connectionless Information Transfer procedure + +The SMLC may send information to another SMLC transparently via the BSS, or via BSS and MSC. + +The CONNECTIONLESS INFORMATION message shall be sent via the BSSMAP as a connectionless message. + +The BSS shall send the CONNECTIONLESS INFORMATION message to the MSC with the following information: + +- Network Element Identity (source), which define the source SMLC for the message; +- Network Element Identity (target), which define the target SMLC for the message; +- Variable length octet string (APDU IE), of which content is defined in 3GPP TS 49.031; + +- Segmentation IE containing segmentation and message identification: included only with a segmented APDU; +- The Return Error Request may be included to request notification in the event of unsuccessful transfer. + +On receipt of the CONNECTIONLESS INFORMATION message, the MSC transmits this message to another MSC or BSS on a direct path to the target SMLC, as derived from the Network Element Identity (target) IE. The contents of APDU IE is transparent to the MSC. + +If the source SMLC and the target SMLC are associated with different MSCs, then the CONNECTIONLESS INFORMATION message shall be forwarded between MSCs via the BSSMAP-LE as a connectionless message (see 3GPP TS 49.031). + +### 3.1.29.1 Unsuccessful Operation + +Unsuccessful operation is specified within Connectionless Information Transfer procedure in 3GPP TS 49.031. + +### 3.1.29.2 Abnormal cases + +Abnormal cases are specified within Connectionless Information Transfer procedure in 3GPP TS 49.031. + +### 3.1.29.3 Segmentation + +The Segmentation parameter shall not be included if the APDU is not segmented. + +If the size of an embedded SMLCPP message is too large to fit into one CONNECTIONLESS INFORMATION message, the sending entity divides the SMLCPP message to a necessary number of CONNECTIONLESS INFORMATION messages each containing an APDU IE and a Segmentation IE. In the APDU IE it includes as many octets as possible. + +The segmentation IE contains a segment number, an indication of the final segment and the message ID. The order number of a segment in the Segment Number field in the SEGMENTATION IE is incremented by one starting from zero, i.e. the value is 0 for the first segment, 1 for the next and so on. The receiving entity recognizes that a segment is missing or duplicated, when: + +- There is more than one segment with the same segment number and same Message ID; +- The segment number does not increase by steps of one starting from zero. + +If the recipient recognizes a missing or duplicated element, it shall discard the entire message (i.e. all received segments with the message ID). + +The message identity in the Message ID field in the SEGMENTATION IE is used to recognize a particular message to which the segment belongs. The sending entity can select any of the available values (0 - 65535) that is not currently used between it and the receiving entity. + +If an APDU segment is received with Return Error cause IE (due to invocation of the return error option), reassembly does not apply and the APDU segment and error cause may be returned to the original source application. + +## 3.1.30 Common ID + +The purpose of the Common ID procedure is to inform the BSC about the IMSI of a user. This may be used by the BSC to e.g. create a reference between the user and the RR and SCCP connections of that user for paging co-ordination. The procedure uses connection oriented signalling. + +An MSC may send a COMMON ID message as soon as the SCCP connection has been established. + +If the MS, the BSS and the MSC support DTM and as soon as the IMSI is available at the MSC, the MSC shall send the COMMON ID message to the BSS. + +If the SCCP connection is established due to CSFB from E-UTRAN and the MSC supports return to the last used PLMN after CS fallback, then it should send the COMMON ID message to the BSS including the *Last used E-UTRAN PLMN ID* information element if available at the MSC immediately following the successful SCCP connection setup. + +If the MSC is configured to use GWCN network sharing and the BSS indicates that the MS did not select a PLMN (i.e. the MS **did not send an initial Layer 3 message that included a PLMN index**), then the MSC shall send the COMMON ID message to the BSS indicating the Selected PLMN ID. + +The BSC associates the permanent identity to the RR and SCCP connections of that user for the duration of the RR connection. + +### 3.1.31 VGCS/VBS Cell Re-established - no A-interface link sharing + +If the condition is removed, that caused the sending of the VGCS/VBS ASSIGNMENT STATUS message indicating that the cell is released for the voice group or broadcast call, the BSS shall inform the MSC of the recovery by sending it a VGCS/VBS ASSIGNMENT STATUS message, indicating that the voice group or broadcast call has been established in the cell. + +The BSS shall reallocate a radio resource for the group channel and initiate the radio interface notification procedure on the NCH of the cell in which the call is to take place. The notification procedure may continue at regular intervals until the call is released or the cell has been released for the voice group or broadcast call. + +When the MSC receives a VGCS/VBS ASSIGNMENT STATUS message it shall update its record of the status of the cell. + +### 3.1.32 Rerouting procedure in case of MOCN configuration for network sharing + +#### 3.1.32.1 General + +This procedure shall be supported by a BSS if and only if it supports the MOCN configuration (see [52]). The rerouting procedure in a GWCN configuration is described in sub-clause 3.1.32a. + +In the MOCN configuration the radio access part of the network is shared. There may be more than one A-Interface towards the CS domain of different CN operators from the BSS. + +Rerouting procedure is a mechanism used as part of the assignment of CN operator in shared networks with MOCN configuration or GWCN configuration (see sub-clause 3.1.32a) when a MS not supporting network sharing performs initial attach/registration. In this case BSS may not know towards which MSC to route the initial MS request message and the latter may be rerouted to another MSC by BSS. + +More precisely, in case of MOCN configuration, the selection of MSC in BSS is based on the NRI (valid or invalid) or by random selection. In case where the MSC cannot be deduced from the NRI and a LOCATION UPDATING REQUEST initial layer 3 message shall be transferred in COMPLETE LAYER 3 INFORMATION message towards an MSC, BSC shall choose an MSC and initiate a rerouting procedure. + +To trigger a rerouting procedure in MOCN configuration, the BSS adds the Redirect Attempt Flag to the COMPLETE LAYER 3 INFORMATION message, in order to indicate that the MSC supporting MOCN shall respond with a REROUTE COMMAND message or a REROUTE COMPLETE message. + +#### 3.1.32.2 Reroute command + +If the COMPLETE LAYER 3 INFORMATION message does not contain the *PS Registered Operator* IE and the MSC cannot serve the request and reroute is possible (error causes are related to subscription options - defined in [6]), the reject Layer 3 Information (e.g. Location Updating Reject) shall be included in the REROUTE COMMAND message for the downlink direction. + +When the IMSI, or in case the BSS supports CS/PS coordination enhancements, the *PS Registered Operator* IE or the *Selected Operator* IE, is not included in the COMPLETE LAYER 3 INFORMATION message and CS/PS domain registration coordination is required (see [52]), the Initial Layer 3 Information shall be included in the REROUTE COMMAND message for the downlink direction and Reroute Reject Cause shall be set to "CS/PS domain registration coordination required". CS/PS domain registration coordination may not be performed for the operator's own subscribers by the MSC. + +In addition the REROUTE COMMAND message shall contain: + +- The Initial Layer 3 Information received from the MS; +- The Reroute Reject Cause; +- The Send Sequence Number, if available; + +- The IMSI, if available. + +If the MSC supports CS/PS coordination enhancements, the REROUTE COMMAND message shall also contain: + +- The Old Location Area Identification as indicated by the MS in the Initial Layer 3 Information or, +- The Attach Indicator in case the Initial Layer 3 Information contains a location update with IMSI attach (see [6]). + +The REROUTE COMMAND message shall always be followed by a CLEAR COMMAND message, which is also the case when CS/PS domain registration coordination is required and a new Initial MS message could be initiated towards the same MSC. At reception of the CLEAR COMMAND message received from the MSC which is not the last attempted, no radio resources are released. + +In a MOCN configuration, if the BSS does not support CS/PS coordination enhancements and the REROUTE COMMAND message is received from an MSC which is not the last attempted, then the BSS shall initiate the Initial MS Message procedure towards another CN operator when possible (or possibly to the same CN in case when CS/PS domain registration coordination is required), with the following additional information in the COMPLETE LAYER 3 INFORMATION message: + +- Redirect Attempt Flag; +- The Send Sequence Number, if received from previously attempted CN operator; +- IMSI, if received from one of previously attempted CN operators. + +If the BSS supports CS/PS coordination enhancements and it receives the REROUTE COMMAND message from an MSC which is not the last attempted, it shall proceed as follows: + +- if the REROUTE COMMAND message contains the Old Location Area Identification and the BSS from this information (and from BSS internal configuration) is able to uniquely identify one of the CN operators in the shared network, then the BSS shall initiate the Initial MS Message procedure towards the MSC of the identified CN operator with the Selected Operator, Redirect Attempt Flag, IMSI and Send Sequence Number (if received from one of previously attempted CN operators) included in the COMPLETE LAYER 3 INFORMATION message; +- if the REROUTE COMMAND message contains the Old Location Area Identification and the BSS from this information (and from BSS internal configuration) cannot identify one of the CN operators in the shared network, then the BSS shall initiate the MS Registration Enquiry procedure in the PS domain (see 3GPP TS 48.018); +- if the REROUTE COMMAND message contains the Attach Indicator then the BSS shall initiate the MS Registration Enquiry procedure in the PS domain (see 3GPP TS 48.018). + +NOTE: The configuration by means the BSS identifies a CN operator from the received Old Location Area Identification is implementation dependent and under operator control. + +If, as a result of the MS Registration Enquiry procedure in the PS domain, the MS is found to be registered with one of the shared CN operators, then the BSS shall initiate the Initial MS Message procedure towards the MSC of the same CN operator with the PS Registered Operator, Redirect Attempt Flag, IMSI and Send Sequence Number (if received from one of previously attempted CN operators) included in the COMPLETE LAYER 3 INFORMATION message. + +If the MS is not found to be registered in the PS domain with any of the shared CN operators, then the BSS shall perform CS/PS domain registration coordination based on the received IMSI and initiate the Initial MS Message procedure towards the MSC of the identified CN operator with the Selected Operator, Redirect Attempt Flag, IMSI and Send Sequence Number (if received from one of previously attempted CN operators) included in the COMPLETE LAYER 3 INFORMATION message. + +Upon reception of the downlink REROUTE COMMAND message, the BSC shall store as part of the Rerouting Function the associated Reroute Reject Cause and Layer 3 Information related to this MSC. + +In case the Reroute Reject Cause is set to "CS/PS domain registration coordination required" and the BSC does not support CS/PS coordination enhancements, then the BSC shall perform CS/PS domain registration coordination based on the received IMSI. In this case the Reroute Reject Cause value and the associated Layer 3 Information shall not be stored. + +In case all attempted CN operators have replied with REROUTE COMMAND message, the BSC shall select the most appropriate Layer 3 Information received from the attempted CN nodes based on the stored information as part of the Rerouting procedure and send it back to the MS (see [6]). + +### 3.1.32.3 Reroute complete + +If the MSC can serve the request, the Layer 3 Information (e.g. Location Updating Accept) shall be sent to the mobile station as a DTAP message and the REROUTE COMPLETE message with the reroute complete outcome IE set to "MS is accepted" or "MS is already registered" shall be sent to the BSS to complete the Rerouting procedure. + +Upon reception of the COMPLETE LAYER 3 INFORMATION message containing the *PS Registered Operator* IE, the MSC supporting CS/PS coordination enhancements shall conclude the Rerouting procedure and include the *Redirection Completed* IE in the REROUTE COMMAND message. + +Upon reception of the downlink REROUTE COMPLETE message, the BSC shall terminate the Rerouting procedure. + +### 3.1.32.4 Abnormal Conditions + +If the MSC cannot serve the request and rerouting is not possible, the MSC shall send to the mobile station the DTAP layer 3 information (e.g. Location Updating Reject) message and the MSC shall send to the BSS the REROUTE COMPLETE message with the reroute complete outcome IE set to "MS is not accepted". + +If, as a result of the analysis of the REROUTE COMMAND message, the MS Registration Enquiry procedure is initiated in the PS domain and the SGSN does not support CS/PS coordination enhancements, then the BSS shall behave as if the MS is not registered with the CN operator of that SGSN. + +## 3.1.32a Rerouting procedure in case of GWCN configuration for network sharing + +### 3.1.32a.1 General + +This procedure shall be supported by a BSS if and only if it supports the GWCN configuration (see [52]). The rerouting procedure in a MOCN configuration is described in sub-clause 3.1.32. + +In the GWCN configuration the radio access part of the network as well as the core network nodes (MSC and SGSN) are shared between the different CN operators. + +Rerouting procedure is a mechanism used as part of the assignment of a CN operator in a shared network when a MS not supporting network sharing performs initial attach/registration. Upon reception of the initial MS request message, the BSS may not know which CN operator to select and thus which CN operator to forward the initial MS request message to. If the initial MS request is not accepted by the CN operator selected by the BSS, a reroute of the initial MS request message to another CN operator within the shared network may be needed. + +More precisely, the selection of a CN operator in the BSS is based on the NRI (valid or invalid) or by random selection. In case the CN operator cannot be deduced from the NRI and a LOCATION UPDATING REQUEST initial layer 3 message (see [6]) shall be transferred in the COMPLETE LAYER 3 INFORMATION message, the BSS shall select a CN operator and initiate the rerouting procedure. + +To trigger a rerouting procedure in a GWCN configuration, the BSS includes the Redirect Attempt Flag in the COMPLETE LAYER 3 INFORMATION message. By including the Redirect Attempt Flag in the COMPLETE LAYER 3 INFORMATION message, the MSC supporting GWCN shall respond with either a REROUTE COMMAND message or a REROUTE COMPLETE message. + +### 3.1.32a.2 Reroute command + +If the COMPLETE LAYER 3 INFORMATION message does not contain the *PS Registered Operator* IE and the CN operator selected by the BSS cannot serve the MS and rerouting is possible (error causes are related to subscription options - defined in [6]), the reject Layer 3 Information (e.g. Location Updating Reject) shall be included in the REROUTE COMMAND message for the downlink direction. + +When neither the *PS Registered Operator* IE nor the *Selected Operator* IE is included in the COMPLETE LAYER 3 INFORMATION message and CS/PS domain registration coordination is required (see [52]), the Initial Layer 3 Information shall be included in the REROUTE COMMAND message for the downlink direction and Reroute Reject + +Cause shall be set to "CS/PS domain registration coordination required". CS/PS domain registration coordination may not be performed by the MSC for the operator's own subscribers. + +In addition the REROUTE COMMAND message shall contain: + +- The Initial Layer 3 Information received from the MS; +- The Reroute Reject Cause; +- The Send Sequence Number, if available; +- The IMSI, if available. +- The Old Location Area Identification as indicated by the MS in the Initial Layer 3 Information or, +- The Attach Indicator in case the Initial Layer 3 Information contains a location update with IMSI attach (see 3GPP TS 24.008 [6]). + +The REROUTE COMMAND message shall always be followed by a CLEAR COMMAND message. Upon reception of the CLEAR COMMAND message not related to the last attempted CN operator, the radio resources associated to the MS shall not be released. + +If the REROUTE COMMAND message is not related to the last attempted CN operator, then the BSS shall proceed as follows: + +- if the REROUTE COMMAND message contains the Old Location Area Identification and the BSS from this information (and from BSS internal configuration) is able to uniquely identify one of the CN operators in the shared network, then the BSS shall initiate the Initial MS Message procedure towards the identified CN operator with the Selected Operator, Redirect Attempt Flag, IMSI and Send Sequence Number (if received from previously attempted CN operators) included in the COMPLETE LAYER 3 INFORMATION message; +- if the REROUTE COMMAND message contains the Old Location Area Identification and the BSS from this information (and from BSS internal configuration) cannot identify one of the CN operators in the shared network, then the BSS shall initiate the MS Registration Enquiry procedure in the PS domain (see 3GPP TS 48.018); +- if the REROUTE COMMAND message contains the Attach Indicator then the BSS shall initiate the MS Registration Enquiry procedure in the PS domain (see 3GPP TS 48.018). + +NOTE: The configuration by means the BSS identifies a CN operator from the received Old Location Area Identification is implementation dependent and under operator control. + +If, as a result of the MS Registration Enquiry procedure in the PS domain, the MS is found to be registered with one of the shared CN operators, then the BSS shall initiate the Initial MS Message procedure towards the same CN operator with the PS Registered Operator, Redirect Attempt Flag, IMSI and Send Sequence Number (if received from previously attempted CN operators) included in the COMPLETE LAYER 3 INFORMATION message. + +If the MS is not found to be registered in the PS domain with any of the shared CN operators, then the BSS shall perform CS/PS domain registration coordination based on the received IMSI and initiate the Initial MS Message procedure towards the SGSN of the identified CN operator with the Selected Operator, Redirect Attempt Flag, IMSI and Send Sequence Number (if received from previously attempted CN operators) included in the COMPLETE LAYER 3 INFORMATION message. + +Upon reception of the REROUTE COMMAND message, the BSS shall store as part of the Rerouting Function the associated Reroute Reject Cause and Layer 3 Information related to this CN operator. + +In case all attempted CN operators have replied with REROUTE COMMAND message, the BSS shall select the most appropriate Layer 3 Information received from the attempted CN operators based on the stored information as part of the Rerouting procedure and send it back to the MS (see [6]). + +### 3.1.32a.3 Reroute complete + +If the selected CN operator accepts the initial request from the MS, then the MSC shall send the DTAP Layer 3 Information message (e.g. Location Updating Accept) to the MS and the REROUTE COMPLETE message to the BSS with the Reroute complete outcome IE set to "MS is accepted" or "MS is already registered". + +Upon reception of the COMPLETE LAYER 3 INFORMATION message containing the *PS Registered Operator* IE, the MSC shall conclude the Rerouting procedure and include the *Redirection Completed* IE in the DL-UNITDATA message. + +Upon reception of the REROUTE COMPLETE message, the BSC shall terminate the Rerouting procedure. + +### 3.1.32a.4 Abnormal Conditions + +If the selected CN operator cannot serve the initial request from the MS and rerouting to another CN operator is not possible, then the MSC shall send the DTAP Layer 3 Information message (e.g. Location Updating Reject) to the MS and the REROUTE COMPLETE message to the BSC with the Reroute complete outcome IE set to "MS is not accepted". + +If, as a result of the analysis of the REROUTE COMMAND message, the MS Registration Enquiry procedure is initiated in the PS domain and the SGSN does not support CS/PS coordination enhancements, then the BSS shall behave as if the MS is not registered with any of the CN operators of that SGSN. + +## 3.1.33 Local Call Local Switch + +### 3.1.33.1 General + +Local Call Local Switch (LCLS) provides the capability for the user plane to be locally switched within the BSS for calls that are generated and terminated by users served by the same BSS (see 3GPP TS 23.284). + +### 3.1.33.2 Local switch establishment + +#### 3.1.33.2.1 Call Leg Correlation + +Call Leg Correlation is the process of determining if another call leg exists in the BSS with the same Global Call Reference (GCR) value. The BSS may perform call leg correlation in a number of steps as described in 3GPP TS 23.284. + +If the BSS receives the LCLS-Correlation-Not-Needed IE in the ASSIGNMENT REQUEST message during the assignment procedure (see sub-clause 3.1.1), it may act upon this and just store the GCR value, or it may ignore the LCLS-Correlation-Not-Needed IE and perform a full call leg correlation. + +If the BSS successfully correlates two call legs it shall indicate this to the core network by setting the LCLS-BSS-Status IE to "Call not yet locally switched". If the call leg correlation is not successful the BSS shall return the LCLS-BSS-Status IE with "Call not possible to be locally switched". + +#### 3.1.33.2.2 Successful Operation + +The BSS may only establish local switching when following conditions are met: + +- the BSS has successfully correlated two call legs, see sub-clause 3.1.33.2.1. +- the BSS has received LCLS-Configuration IE on both call legs of the local call, and the requested LCLS configuration is supported in the BSS. +- the BSS has received LCLS-Connection-Status-Control IE with value "Connect" on both call legs of the local call. + +The LCLS-Configuration IE defines the user data connectivity for the given call leg as follows: + +- if the LCLS configuration requested by the MSC indicates "Connect both-way", then the BSS shall pass user data between the locally switched call legs without sending any user data to the core network or expecting to receive any user data from the core network. +- if the LCLS configuration requested by the MSC indicates "Connect both-way and bi-cast UL to the core network", then the BSS shall pass user data between the locally switched call legs and send UL user data to the core network but not expect to receive any user data from the core network. +- if the LCLS configuration requested by the MSC indicates "Connect both-way and send access DL from the core network", then the BSS shall pass user data between the locally switched call legs, detect incoming user data from the core network and insert the user data into the user data stream towards the served user. Any local DL + +user data received may be pre-empted while delivering DL user data from the core network. How this is performed is implementation dependent. The BSS shall not send UL user data to the core network. + +- if the LCLS configuration requested by the MSC indicates "Connect both-way and send access DL from the core network, block local DL user data", then the BSS shall send user data to the locally switched call leg and pass incoming user data from the core network towards the served user while blocking local DL user data. The BSS shall not send UL user data to the core network. +- if the LCLS configuration requested by the MSC indicates "Connect both-way and bi-cast UL to the core network with send access DL from the core network", then the BSS shall pass user data between the locally switched call legs, detect incoming user data from the core network and insert the user data into the user data stream towards the served user and send UL user data to the core network. Any local DL user data received may be pre-empted while delivering DL user data from the core network. How this is performed is implementation dependent. +- if the LCLS configuration requested by the MSC indicates "Connect both-way and bi-cast UL to the core network with send access DL from the core network, block local DL user data", then the BSS shall send user data UL both to the core network and to the locally switched call leg and pass incoming user data from the core network towards the served user while blocking local DL user data. + +The BSS shall inform the MSC of a successful local switch connection by setting the LCLS-BSS-Status IE to "Call is locally switched with requested LCLS configuration" in the LCLS-CONNECT-CONTROL-ACK message or in the appropriate BSSAP message (see sub-clause 3.1.1, 3.1.5, 3.1.6 and 3.1.7). The BSS shall also inform the MSC serving the other call leg of the locally switched call using the LCLS-NOTIFICATION message, see sub-clause 3.1.33.5. + +If at any time the LCLS connection status for a call leg is changed in the BSS, the new LCLS connection status value shall be reported to the MSC according to sub-clause 3.1.33.5. + +### 3.1.33.2.3 Unsuccessful Operation + +If a message which includes LCLS-Configuration IE is received in the BSS, the BSS shall check whether it can support the requested LCLS configuration. If the BSS does not support the requested LCLS configuration, then the BSS shall indicate this to the MSC by setting the LCLS-BSS-Status IE to "Requested LCLS configuration is not supported" in the LCLS-CONNECT-CONTROL-ACK message or in the appropriate BSSAP response message (see sub-clause 3.1.1 and 3.1.5). + +However, even if the BSS does not support the requested LCLS configuration the BSS shall store the received GCR value (or replace the previously stored GCR value) included in the Global Call Reference IE since the MSC may renegotiate the LCLS configuration without re-sending the Global Call Reference IE. + +If the MSC has granted the permission to apply local switching, the BSS makes the final decision whether or not to establish local switching. If the BSS is not able to establish local switching it shall indicate this to the MSC by setting the LCLS-BSS-Status IE to value "Call not yet locally switched" in the LCLS-CONNECT-CONTROL-ACK message or in the appropriate BSSAP message (see sub-clause 3.1.1, 3.1.5, 3.1.6 and 3.1.7). + +### 3.1.33.3 Local switch break + +#### 3.1.33.3.1 Local switching break request from MSC + +If the MSC initiates break of local switching, the MSC sends the LCLS-CONNECT-CONTROL message with the LCLS-Connection-Status-Control IE set to "Release LCLS" on both call legs of the locally switched call. + +On receipt of the LCLS-CONNECT-CONTROL message with the LCLS-Connection-Status-Control IE set to "Release LCLS" the BSS shall only break local switching if the message is received on both call legs of the locally switched call. At reception of the LCLS break request for the first call leg (i.e. before the LCLS break request is received for the second call leg) the BSS shall report to the MSC by sending the LCLS-CONNECT-CONTROL-ACK message with the present LCLS connection status value included in the message. At reception of the LCLS break request for the second call leg (and a corresponding LCLS break request is already received for the first call leg associated to the locally switched call), the BSS shall break local switching and report the LCLS disconnection to the MSC by sending the LCLS-CONNECT-CONTROL-ACK message on this call leg, and the LCLS-NOTIFICATION message on the other call leg (see sub-clause 3.1.33.5), with the LCLS-BSS-Status IE set to "Call is no longer locally switched" included in both messages. + +### 3.1.33.3.2 Local switching break initiated by BSS + +If the BSS determines that local switching should be disconnected, the BSS may: + +- immediately break local switching and then inform the MSC on both call legs by sending the LCLS-NOTIFICATION message (see sub-clause 3.1.33.5) with the LCLS-BSS-Status IE set to "Call is no longer locally switched" included in the message, or +- first request the MSC to prepare for LCLS break (see sub-clause 3.1.33.5) and on the reception of LCLS break request on both call legs the BSS breaks local switching, see sub-clause 3.1.33.3.1. + +### 3.1.33.3.3 Local Switching break at Handover + +If a call is locally switched and an inter-BSS handover or an inter-system handover is performed for one of the call legs then local switching is broken and normal core network switched user plane is resumed. The locally switched call may also be broken as a result of an internal handover within the BSS. + +When, during the handover procedure, the BSS receives the LCLS-CONNECT-CONTROL message with the LCLS-Connection-Status-Control IE set to "Bi-cast UL at Handover", the BSS shall acknowledge the LCLS-CONNECT-CONTROL message with LCLS-CONNECT-CONTROL-ACK and initiate UL user data transmission to this call leg in addition to sending user data to the other locally switched call leg. The BSS shall continue to send user data to the other locally switched call leg until local switching is released. + +When, during the handover procedure, the BSS receives the LCLS-CONNECT-CONTROL message with the LCLS-Connection-Status-Control IE set to "Bi-cast UL and receive DL data at Handover", the BSS shall acknowledge the LCLS-CONNECT-CONTROL message with LCLS-CONNECT-CONTROL-ACK, continue to send user data UL both to the core network and to the other locally switched call leg, and if the BSS is unable to detect inband user data itself, receive user data DL from the core network originating from the MS in the new cell. + +NOTE: Inband detection of user data from the core network is not standardised and can only be ensured through proprietary common solutions between the core network and the BSS. + +When the locally switched call is released, the BSS shall for the call leg not being part in the handover procedure revert to the previously defined LCLS connection status value requested by the MSC (i.e. which was valid before receiving the LCLS-CONNECT-CONTROL message with the LCLS-Connection-Status-Control IE set to "Bi-cast UL at Handover") and maintain the LCLS configuration setting to be able to resume local switching if e.g. the distant call leg (in case of an inter-BSS or an inter-system handover) performs a subsequent handover back to the same BSS. + +A locally switched call may be resumed as a result of the MS returning to the old channel at handover failure (see sub-clauses 3.1.5.3.2, 3.1.5a.4 and 3.1.5c.2.1). If the radio interface HANDOVER FAILURE message is received after the BSS has started UL user data transmission to the core network, then the BSS shall autonomously stop the UL transmission, end user data reception DL from the core network (if active) and revert to the previously defined LCLS connection status value which was valid prior to the handover. + +Bi-casting of user data, which may have been activated prior to the handover with the LCLS-Configuration IE, shall still be applied if local switching is resumed after the handover failure. + +### 3.1.33.4 Local switch prevention + +The MSC may at any time prevent the BSS from establishing local switching by setting the LCLS-Connection-Status-Control IE to "Do not connect". + +### 3.1.33.5 LCLS Notification + +When the LCLS connection status is changed in the BSS for a call leg for which the BSS has reported that it supports the LCLS configuration requested from the MSC, the new LCLS connection status value shall be explicitly reported to the MSC in the LCLS-NOTIFICATION message (unless the changed LCLS connection status can be returned in another BSSAP response message). Valid LCLS connection status values are defined in sub-clause 3.2.2.119. + +In the event of disconnecting local switching in the BSS, a request for LCLS break may be sent to the MSC. The BSS sends the LCLS-NOTIFICATION message to the MSC on both call legs with the LCLS-Break-Request IE present in the message. + +## 3.1.34 MS Registration Enquiry + +### 3.1.34.1 General + +This procedure shall be supported by a BSS if it supports CS/PS coordination enhancements in a MOCN configuration (see sub-clause 3.1.32) or in a GWCN configuration (see sub-clause 3.1.32a). + +The purpose of the MS Registration Enquiry procedure is to acquire registration information for a given MS from the core network. More precisely, triggered e.g. by the Rerouting procedure in the PS domain (see 3GPP TS 48.018), the BSS sends an enquiry to the MSC(s) whether a given MS is already registered with any of the core network operators in the shared network. + +### 3.1.34.2 Registration enquiry + +The MS Registration Enquiry procedure is triggered by the BSS sending the MS REGISTRATION ENQUIRY message to the MSC containing the IMSI for the MS for which the registration enquiry concerns. The MS REGISTRATION ENQUIRY message is sent to each MSC connected to the BSS using the connectionless mode of the SCCP. + +The MSC responds with the MS REGISTRATION ENQUIRY RESPONSE message indicating whether the MS is served by (one of) the CN operator(s) sharing the network. + +### 3.1.34.3 Registration response + +If the MS is found to be registered with (one of) the CN operator(s) sharing the network, the MSC shall return the MS REGISTRATION ENQUIRY RESPONSE message to the BSS with the IMSI and the *CS Registered Operator* IE (containing the serving CN operator) included in the message. + +If the MS is not registered with (any of) the CN operator(s), the MSC excludes the *CS Registered Operator* IE from the MS REGISTRATION ENQUIRY RESPONSE message. + +Upon reception of the MS REGISTRATION ENQUIRY RESPONSE message with the *CS Registered Operator* IE included in the message, the BSS may terminate the MS Registration Enquiry procedure regardless if one or more MSCs have not yet responded to the MS REGISTRATION ENQUIRY message. + +## 3.2 Message Formats and Coding + +This sub-clause defines the coding and format of the messages required for the BSSMAP. + +For each message there is, in sub-clause 3.2.1, a table listing the signalling elements in their order of appearance in the transmitted message. + +There is no general rule for the order of signalling elements: it happens that the same elements appear in various orders depending on the message. + +All the BSSMAP messages are listed in the following table. + +| Message name | Reference | +|--------------------------------------|-----------| +| ASSIGNMENT REQUEST | 3.2.1.1 | +| ASSIGNMENT COMPLETE | 3.2.1.2 | +| ASSIGNMENT FAILURE | 3.2.1.3 | +| CHANNEL MODIFY REQUEST | 3.2.1.75 | +| BLOCK | 3.2.1.4 | +| BLOCKING ACKNOWLEDGE | 3.2.1.5 | +| CIRCUIT GROUP BLOCK | 3.2.1.41 | +| CIRCUIT GROUP BLOCKING ACKNOWLEDGE | 3.2.1.42 | +| CIRCUIT GROUP UNBLOCK | 3.2.1.43 | +| CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE | 3.2.1.44 | +| CLEAR COMMAND | 3.2.1.21 | +| CLEAR COMPLETE | 3.2.1.22 | +| CLEAR REQUEST | 3.2.1.20 | +| UNBLOCK | 3.2.1.6 | +| UNBLOCKING ACK | 3.2.1.7 | +| HANDOVER CANDIDATE ENQUIRE | 3.2.1.14 | +| HANDOVER CANDIDATE RESPONSE | 3.2.1.15 | +| HANDOVER REQUEST | 3.2.1.8 | +| HANDOVER REQUIRED | 3.2.1.9 | +| HANDOVER REQUIRED REJECT | 3.2.1.37 | +| HANDOVER REQUEST ACKNOWLEDGE | 3.2.1.10 | +| HANDOVER COMMAND | 3.2.1.11 | +| HANDOVER COMPLETE | 3.2.1.12 | +| HANDOVER SUCCEEDED | 3.2.1.13 | +| HANDOVER FAILURE | 3.2.1.16 | +| HANDOVER PERFORMED | 3.2.1.25 | +| HANDOVER DETECT | 3.2.1.40 | +| RESOURCE REQUEST | 3.2.1.17 | +| RESET | 3.2.1.23 | +| RESET ACK | 3.2.1.24 | +| RESOURCE INDICATION | 3.2.1.18 | +| PAGING | 3.2.1.19 | +| OVERLOAD | 3.2.1.26 | +| MSC INVOKE TRACE | 3.2.1.27 | +| BSS INVOKE TRACE | 3.2.1.28 | +| CLASSMARK UPDATE | 3.2.1.29 | +| CLASSMARK REQUEST | 3.2.1.46 | +| CIPHER MODE COMMAND | 3.2.1.30 | +| CIPHER MODE COMPLETE | 3.2.1.31 | +| CIPHER MODE REJECT | 3.2.1.48 | +| COMPLETE LAYER 3 INFORMATION | 3.2.1.32 | +| QUEUING INDICATION | 3.2.1.33 | +| SAPI "N" REJECT | 3.2.1.34 | +| RESET CIRCUIT | 3.2.1.38 | +| RESET CIRCUIT ACKNOWLEDGE | 3.2.1.39 | +| CONFUSION | 3.2.1.45 | +| UNEQUIPPED CIRCUIT | 3.2.1.47 | +| LOAD INDICATION | 3.2.1.49 | +| VGCS/VBS SETUP | 3.2.1.50 | +| VGCS/VBS SETUP ACK | 3.2.1.51 | +| VGCS/VBS SETUP REFUSE | 3.2.1.52 | +| VGCS/VBS ASSIGNMENT REQUEST | 3.2.1.53 | +| VGCS/VBS ASSIGNMENT RESULT | 3.2.1.54 | +| VGCS/VBS ASSIGNMENT FAILURE | 3.2.1.55 | +| VGCS/VBS QUEUING INDICATION | 3.2.1.56 | +| UPLINK REQUEST | 3.2.1.57 | +| UPLINK REQUEST ACKNOWLEDGE | 3.2.1.58 | +| UPLINK REQUEST CONFIRMATION | 3.2.1.59 | +| UPLINK RELEASE INDICATION | 3.2.1.60 | +| UPLINK REJECT COMMAND | 3.2.1.61 | +| UPLINK RELEASE COMMAND | 3.2.1.62 | +| UPLINK SEIZED COMMAND | 3.2.1.63 | +| SUSPEND | 3.2.1.64 | +| RESUME | 3.2.1.65 | + +| Message name | Reference | +|-----------------------------------|------------------| +| CHANGE CIRCUIT | 3.2.1.66 | +| CHANGE CIRCUIT ACKNOWLEDGE | 3.2.1.67 | +| COMMON ID | 3.2.1.68 | +| LSA INFORMATION | 3.2.1.69 | +| CONNECTION ORIENTED INFORMATION | 3.2.1.70 | +| PERFORM LOCATION REQUEST | 3.2.1.71 | +| PERFORM LOCATION RESPONSE | 3.2.1.72 | +| PERFORM LOCATION ABORT | 3.2.1.73 | +| CONNECTIONLESS INFORMATION | 3.2.1.74 | +| EMERGENCY RESET INDICATION | 3.2.1.76 | +| EMERGENCY RESET COMMAND | 3.2.1.77 | +| VGCS ADDITIONAL INFORMATION | 3.2.1.78 | +| VGCS/VBS AREA CELL INFO | 3.2.1.79 | +| VGCS/VBS ASSIGNMENT STATUS | 3.2.1.80 | +| VGCS SMS | 3.2.1.81 | +| NOTIFICATION DATA | 3.2.1.82 | +| INTERNAL HANDOVER REQUIRED | 3.2.1.83 | +| INTERNAL HANDOVER REQUIRED REJECT | 3.2.1.84 | +| INTERNAL HANDOVER COMMAND | 3.2.1.85 | +| INTERNAL HANDOVER ENQUIRY | 3.2.1.86 | +| RESET IP RESOURCE | 3.2.1.87 | +| RESET IP RESOURCE ACKNOWLEDGE | 3.2.1.88 | +| REROUTE COMMAND | 3.2.1.89 | +| REROUTE COMPLETE | 3.2.1.90 | +| LCLS-CONNECT-CONTROL | 3.2.1.91 | +| LCLS-CONNECT-CONTROL-ACK | 3.2.1.92 | +| LCLS-NOTIFICATION | 3.2.1.93 | +| MS REGISTRATION ENQUIRY | 3.2.1.94 | +| MS REGISTRATION ENQUIRY RESPONSE | 3.2.1.95 | + +## 3.2.1 Message Contents + +### 3.2.1.1 ASSIGNMENT REQUEST + +This message is sent from the MSC to the BSS via the relevant SCCP connection in order to request the BSS to assign radio resource(s), the attributes of which are defined within the message. + +The message may also include the terrestrial circuit to be used. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------|-----------|-----------|-------------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Channel Type | 3.2.2.11 | MSC-BSS | M | 5-13 | +| Layer 3 Header Information | 3.2.2.9 | MSC-BSS | O (note 3) | 4 | +| Priority | 3.2.2.18 | MSC-BSS | O | 3 | +| Circuit Identity Code | 3.2.2.2 | MSC-BSS | O
(note 1, 12) | 3 | +| Downlink DTX Flag | 3.2.2.26 | MSC-BSS | O (note 2) | 2 | +| Interference Band To Be Used | 3.2.2.21 | MSC-BSS | O | 2 | +| Classmark Information 2 | 3.2.2.19 | MSC-BSS | O (note 4) | 4-5 | +| Group Call Reference | 3.2.2.55 | MSC-BSS | O (note 5) | 7 | +| Talker Flag | 3.2.2.54 | MSC-BSS | O (note 6) | 1 | +| Configuration Evolution Indication | 3.2.2.57 | MSC-BSS | O (note 7) | 2 | +| LSA Access Control Suppression | 3.2.2.61 | MSC-BSS | O (note 8) | 2 | +| Service Handover | 3.2.2.75 | MSC-BSS | O (note 9) | 3 | +| Encryption Information | 3.2.2.10 | MSC-BSS | O (note 10) | 3-n | +| Talker Priority | 3.2.2.89 | MSC-BSS | O (note 11) | 2 | +| AoIP Transport Layer Address (MGW) | 3.2.2.102 | MSC-BSS | O (note 12) | 8-20 | +| Codec List (MSC Preferred) | 3.2.2.103 | MSC-BSS | O (note 13) | 3-n | +| Call Identifier | 3.2.2.105 | MSC-BSS | O (note 12) | 5 | +| Kc 128 | 3.2.2.109 | MSC-BSS | C (note 15) | 17 | +| Global Call Reference | 3.2.2.115 | MSC-BSS | O (note 16) | 3-n | +| LCLS-Configuration | 3.2.2.116 | MSC-BSS | O (note 16) | 2 | +| LCLS-Connection-Status-Control | 3.2.2.117 | MSC-BSS | O (note 17) | 2 | +| LCLS-Correlation-Not-Needed | 3.2.2.118 | MSC-BSS | O (note 18) | 1 | +| CS to PS SRVCC | 3.2.2.122 | MSC-BSS | O (note 19) | 1 | + +- NOTE 1: This element (Circuit Identity Code) is included, if the MSC allocates the A interface TDM-circuits and the channel type Information Element indicates speech or data, and only in those cases. +- NOTE 2: This element may be included in the case of a speech TCH, and only in this case. If not included, this has no impact on the DTX function in the BSS. This element shall be neglected by the BSS, if an IP A-Interface type is finally selected and speech transcoder resources are not allocated within the BSS. +- NOTE 3: This information element doesn't serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of the present document, this information element will be deleted from this message. +- NOTE 4: These elements may be included if the information is known by the MSC. +- NOTE 5: This information element is included by the MSC if the subscriber is a talker or a listener in a group call. +- NOTE 6: This information element is included by the MSC if the subscriber is a talker in a group call. +- NOTE 7: The information is indicated by the MSC if known. +- NOTE 8: This information element is included if LSA access control function shall be suppressed in the BSS. +- NOTE 9: This information element is included if a preference for other radio access technologies shall be applied to the MS connection. +- NOTE 10: This information is only included for ciphered VGCS/VBS calls. It is only included if the assignment procedure is used to transfer the talker from a group call channel to a dedicated channel, the Group Call Reference is present, and the Group Key Number within this field is set to a value other than 'no ciphering'. +- NOTE 11: This information element is included if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing and the Assignment Request is used to transfer the talker from a group call channel to a dedicated channel. +- NOTE 12: These IEs are not included, if the Channel Type IE indicates "signalling". The Circuit Identity Code may be included, if at least one alternative for a TDM connection is included in Codec List (MSC Preferred). The AoIP Transport Layer Address (MGW) and Call Identifier may be included, if at least one alternative for an IP connection is included in Codec List (MSC Preferred). The ASSIGNMENT REQUEST message may include both, a Circuit Identity Code and an AoIP Transport Layer Address (MGW) simultaneously. At least one of the two IEs shall be included (except if the Channel Type IE indicates "signalling"). If the Codec List (MSC Preferred) is included in Assignment Request, then the BSS shall not allocate a Circuit Identity Code on its own. +- NOTE 13: This IE is not included, if the Channel Type IE indicates "signalling". Codec List (MSC Preferred) shall be included if the core network supports an IP based user plane interface. The information in Codec List (MSC Preferred) shall be consistent with the information in Channel Type IE. +- NOTE 14: Void +- NOTE 15: This IE is included if the encryption algorithm A5/4 is indicated as permitted in the Encryption Information IE. +- NOTE 16: This IE is included if local switching is requested by the MSC. +- NOTE 17: This IE may be included if local switching is requested by the MSC to explicitly indicate the LCLS connection status requested. If this IE is not included then through-connection of the two call legs is not permitted. +- NOTE 18: This IE may be included if local switching is requested by the MSC and one of the options "intra-Network Call Detection" or "intra-BSS Call Detection" are supported by the MSC (see 3GPP TS 23.284). This IE is optional for the BSS to support. +- NOTE 19: This IE is included if the MSC determines that CS to PS SRVCC is allowed for this connection. + +### 3.2.1.2 ASSIGNMENT COMPLETE + +The ASSIGNMENT COMPLETE message is sent from the BSS to the MSC and indicates that the requested assignment has been completed correctly. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------|-----------|-----------|-------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| RR Cause | 3.2.2.22 | BSS-MSC | O | 2 | +| Circuit Identity Code | 3.2.2.2 | BSS-MSC | O (note 4) | 3 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | O (note 1) | 3-10 | +| Chosen Channel | 3.2.2.33 | BSS-MSC | O (note 3) | 2 | +| Chosen Encryption Algorithm | 3.2.2.44 | BSS-MSC | O (note 5) | 2 | +| Circuit Pool | 3.2.2.45 | BSS-MSC | O (note 2) | 2 | +| Speech Version (Chosen) | 3.2.2.51 | BSS-MSC | O (note 6) | 2 | +| LSA Identifier | 3.2.2.15 | BSS-MSC | O (note 7) | 5 | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 8) | 2 | +| AoIP Transport Layer Address (BSS) | 3.2.2.102 | BSS-MSC | O (note 9) | 8-20 | +| Speech Codec (Chosen) | 3.2.2.104 | BSS-MSC | O (note 10) | 3-5 | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | O (note 11) | 3-n | +| LCLS-BSS-Status | 3.2.2.119 | BSS-MSC | O (note 12) | 2 | + +NOTE 1: The cell identifier is used to indicate a new cell, if during the assignment the serving cell has changed. When sent from 3G\_MSC-B over MAP/E interface this information element contains indication of Cell Identifier (e.g. CGI) if the new serving cell is GSM or indication of either RNC-ID (or Extended RNC-ID) or SAI (if known) if the new serving cell is UMTS. Note: RNC-ID (or Extended RNC-ID) or SAI are only provided in the ASSIGNMENT COMPLETE message over the MAP-E interface. + +NOTE 2: Shall be included when several circuit pools are present on the BSS MSC interface and a circuit was allocated by the ASSIGNMENT REQUEST message. + +NOTE 3: Included at least when the channel rate/type choice was done by the BSS. + +NOTE 4: The Circuit Identity Code information element is included mandatorily by the BSS if the BSS allocates the A interface circuits and a circuit is needed. If the Codec List (MSC Preferred) was included in Assignment Request, then the BSS shall not allocate a Circuit Identity Code on its own. + +NOTE 5: Included at least when the encryption algorithm has been changed by the BSS. + +NOTE 6: Included at least when the speech version choice was done by the BSS. + +NOTE 7: Shall be included if current LSA in the serving cell has been identified (see 3GPP TS 43.073). Not included means that there is no current LSA in the serving cell. + +NOTE 8: This information element is included if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing and the BSS has completed the transfer of the talker from a group call channel to a dedicated channel. + +NOTE 9: AoIP Transport Layer Address (BSS) shall be included if and only if the BSS has chosen an IP connection for the user plane interface. AoIP Transport Layer Address (BSS) shall not be modified if the ASSIGNMENT COMPLETE message is a response to a sub-sequent ASSIGNMENT REQUEST MESSAGE which modifies the radio interface data rate. + +NOTE 10: Speech Codec (Chosen) shall be included if the radio access network supports an IP user plane interface. This information element shall be consistent with the information in Chosen Channel, if included, and with the information in Speech Version (Chosen), if included. + +NOTE 11: Codec List (BSS Supported) may be included, if an intra-BSS cell change has occurred during the assignment. + +NOTE 12: This IE shall be included if LCLS is supported by BSS and both Global Call Reference IE and LCLS-Configuration IE were included in the ASSIGNMENT REQUEST message. + +### 3.2.1.3 ASSIGNMENT FAILURE + +The ASSIGNMENT FAILURE message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that there has been a failure in the assignment process at the BSS and that the assignment procedure has been aborted. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | +| RR Cause | 3.2.2.22 | BSS-MSC | O | 2 | +| Circuit Pool | 3.2.2.45 | BSS-MSC | O (note 1) | 2 | +| Circuit Pool List | 3.2.2.46 | BSS-MSC | O (note 2) | V | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 3) | 2 | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | O (note 4) | 3-n | +| NOTE 1: Shall be included when several circuit pools are present on the BSS MSC interface. | | | | | +| NOTE 2: May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences. | | | | | +| NOTE 3: This information element is included if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing and the BSS has failed to transfer the talker from a group call channel to a dedicated channel. | | | | | +| NOTE 4: Codec List (BSS Supported) should be included, if the radio access network supports an IP based user plane interface. | | | | | + +Typical Cause values are: + +- radio interface message failure; + - O and M intervention; + - equipment failure; + - no radio resource available; + - requested terrestrial resource unavailable; + - requested transcoding/rate adaption unavailable; + - Requested Redundancy Level not supported; + - Requested Redundancy Level not available; + - terrestrial resource already allocated; + - Call Identifier already allocated; + - invalid message contents; + - radio interface failure - reversion to old channel; + - ciphering algorithm not supported; + - directed retry; + - circuit pool mismatch; + - switch circuit pool; + - requested speech version unavailable; +- Requested A-Interface Type not supported; +- Requested Codec Type or Codec Configuration not supported; +- Requested A-Interface Type unavailable; + +Requested Codec Type or Codec Configuration unavailable; + +- relocation triggered (NOTE). + +NOTE: This cause value is only sent by 3G\_MSC-B over the MAP/E interface (see 3GPP TS 29.010). + +### 3.2.1.4 BLOCK + +This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a particular terrestrial resource (i.e. a particular timeslot within a 2Mbit system) must be remotely blocked at the circuit master, and cannot therefore be used for traffic. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | both | M | 3 | +| Cause | 3.2.2.5 | both | M | 3-4 | +| Connection Release Requested | 3.2.2.3 | MSC-BSS | O | 1 | + +Typical Cause values are: + +- no radio resource available; +- O and M intervention; +- equipment failure. + +### 3.2.1.5 BLOCKING ACKNOWLEDGE + +This message is sent from the MSC to the BSS or from the BSS to the MSC to acknowledge the receipt of an earlier BLOCK message, and to indicate that the circuit concerned has been removed from service. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | both | M | 3 | + +### 3.2.1.6 UNBLOCK + +This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a particular terrestrial resource (ie a particular timeslot within a 2 Mbit system) should not be remotely blocked any more on the receiver side. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | both | M | 3 | + +### 3.2.1.7 UNBLOCKING ACKNOWLEDGE + +This message is sent from the MSC to the BSS or from the BSS to the MSC to acknowledge the receipt of an earlier UNBLOCK message. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | both | M | 3 | + +### 3.2.1.8 HANDOVER REQUEST + +This message is sent from the MSC to the BSS via the relevant SCCP connection to indicate that the MS is to be handed over to that BSS. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------|----------------------|--------------------|------------------|----------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Channel Type | 3.2.2.11 | MSC-BSS | M | 5-13 | +| Encryption Information | 3.2.2.10 | MSC-BSS | M (note 1) | 3-n | +| Classmark Information 1
or
Classmark Information 2 | 3.2.2.30
3.2.2.19 | MSC-BSS
MSC-BSS | M#
M (note 6) | 2
4-5 | +| Cell Identifier (Serving) | 3.2.2.17 | MSC-BSS | M (note 20) | 5-10 | +| Priority | 3.2.2.18 | MSC-BSS | O | 3 | +| Circuit Identity Code | 3.2.2.2 | MSC-BSS | O (note 7, 24) | 3 | +| Downlink DTX Flag | 3.2.2.26 | MSC-BSS | O (note 3) | 2 | +| Cell Identifier (Target) | 3.2.2.17 | MSC-BSS | M (note 17) | 3-10 | +| Interference Band To Be Used | 3.2.2.21 | MSC-BSS | O | 2 | +| Cause | 3.2.2.5 | MSC-BSS | O (note 9) | 3-4 | +| Classmark Information 3 | 3.2.2.20 | MSC-BSS | O (note 4) | 3-34 | +| Current Channel type 1 | 3.2.2.49 | MSC-BSS | O (note 8) | 2 | +| Speech Version (Used) | 3.2.2.51 | MSC-BSS | O (note 10) | 2 | +| Group Call Reference | 3.2.2.55 | MSC-BSS | O (note 5) | 7 | +| Talker Flag | 3.2.2.54 | MSC-BSS | O (note 11) | 1 | +| Configuration Evolution Indication | 3.2.2.57 | MSC-BSS | O (note 12) | 2 | +| Chosen Encryption Algorithm (Serving) | 3.2.2.44 | MSC-BSS | O (note 2) | 2 | +| Old BSS to New BSS Information | 3.2.2.58 | MSC-BSS | O (note 13) | 2-n | +| LSA Information | 3.2.2.23 | MSC-BSS | O (note 14) | 3+4n | +| LSA Access Control Suppression | 3.2.2.61 | MSC-BSS | O (note 15) | 2 | +| Service Handover | 3.2.2.75 | MSC-BSS | O (note 21) | 3 | +| IMSI | 3.2.2.6 | MSC-BSC | O (note 16) | 3-10 | +| Source RNC to target RNC transparent information (UMTS) | 3.2.2.76 | MSC-BSS | O (note 18) | n-m | +| Source RNC to target RNC transparent information (cdma2000) | 3.2.2.77 | MSC-BSS | O (note 19) | n-m | +| SNA Access Information | 3.2.2.82 | MSC-BSC | O (note 22) | 2+n | +| Talker Priority | 3.2.2.89 | MSC-BSC | O (note 23) | 2 | +| AoIP Transport Layer Address (MGW) | 3.2.2.102 | MSC-BSS | O (note 24) | 8-20 | +| Codec List (MSC Preferred) | 3.2.2.103 | MSC-BSS | O (note 25) | 3-n | +| Call Identifier | 3.2.2.105 | MSC-BSS | O (note 24) | 5 | +| Kc 128 | 3.2.2.109 | MSC-BSS | C (note 27) | 17 | +| Global Call Reference | 3.2.2.115 | MSC-BSS | O (note 28) | 3-n | +| LCLS-Configuration | 3.2.2.116 | MSC-BSS | O (note 28) | 2 | +| LCLS-Connection-Status-Control | 3.2.2.117 | MSC-BSS | O (note 28) | 2 | +| CS to PS SRVCC | 3.2.2.122 | MSC-BSS | O (note 29) | 1 | + +NOTE 1: Except in the case of a VGCS talker, if neither a CIPHER MODE COMMAND has been sent (to a BSS) nor a SECURITY MODE COMMAND has been sent (to an RNC) for this RR/RRC connection (or if all such CIPHER MODE COMMAND messages (resp. SECURITY MODE COMMAND messages) have been rejected with CIPHER MODE REJECT messages (resp. SECURITY MODE REJECT messages)) then the MSC shall indicate that the only "permitted algorithm" is "no encryption". +In the case of a VGCS talker, if the Group Key Number within the Group Call Reference is set to a value other than 'no ciphering', the MSC shall indicate the permitted algorithms and the ciphering key to use on a dedicated channel, irrespective of whether a CIPHER MODE COMMAND has been previously sent on the RR connection. + +NOTE 2: If this information element is included, it shall be equal to the last received "Chosen Encryption Algorithm" information element. The information should be indicated by the MSC if known. + +NOTE 3: This element may be included in the case of a speech TCH, and only in this case. If not included, this has no impact on the DTX function in the BSS. This element shall be neglected by the BSS, if an IP A-Interface type is finally selected and speech transcoder resources are not allocated within the BSS. + +NOTE 4: This element is included if the MSC has received such information. + +NOTE 5: This element is included if the MS is in a voice broadcast or voice group call. + +NOTE 6: One of these two elements is sent. + +NOTE 7: This element (Circuit Identity Code) is included, if the MSC allocates the A interface TDM- + +| | | +|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | circuits and the channel type Information Element indicates speech or data, and only in those cases. In case of Voice Group Call talker handover, this element may contain the Circuit Identity Code already allocated during the VBS/VGCS assignment procedure, meaning that the already allocated terrestrial resource of the new cell is used. | +| NOTE 8: | This element is included at least when the message is sent as a reaction to reception of a HANDOVER REQUIRED message containing a "Current channel type 1" information element. In this case it shall be equal to the received element. | +| NOTE 9: | This information element should always be included. Its cause value should be the same as indicated in the corresponding Handover Required message. | +| NOTE 10: | This element is included at least when the message is sent as a reaction to reception of a HANDOVER REQUIRED message containing a "Speech version (used)" information element. In this case it shall be equal to the received element. | +| NOTE 11: | This information element is included for voice group call, when this is included it indicates that the mobile is a talker in the call else the mobile is a listener. | +| NOTE 12: | The information is indicated by the MSC if known | +| NOTE 13: | This element is included if and only if the message is sent as a reaction to the reception of a HANDOVER REQUIRED message or a RELOCATION REQUIRED message (see 3GPP TS 25.413) or an SRVCC PS to CS REQUEST message (see 3GPP TS 29.280) containing an "old BSS to new BSS information" information element. Its contents shall be equal to the received element. | +| NOTE 14: | This information element is included when the subscriber has localised service area support. | +| NOTE 15: | This information element is included if LSA access control function shall be suppressed in the BSS. | +| NOTE 16: | This information element is included at least when the MS is dual transfer mode capable and the IMSI is available at the MSC. | +| NOTE 17: | If intersystem handover from GSM to UMTS or to cdma 2000 is performed, this information element indicates the target RNC-ID (or Extended RNC-ID). | +| NOTE 18: | This information element shall be included when intersystem handover (UMTS) is performed. This element is included if and only if the message is sent as a reaction to the reception of a HANDOVER REQUIRED message containing an "Source RNC to Target RNC transparent information (UMTS)" IE. Its contents shall be equal to the received element. Only provided in the HANDOVER REQUEST message on the MAP-E interface. | +| NOTE 19: | This information element shall be included when intersystem handover (cdma2000) is performed. This element is included if and only if the message is sent as a reaction to the reception of a HANDOVER REQUIRED message containing a "Source RNC to Target RNC transparent information (cdma2000)" IE. Its contents shall be equal to the received element. Only provided in the HANDOVER REQUEST message on the MAP-E interface. | +| NOTE 20: | In intersystem handover from UMTS (or cdma2000) to GSM this IE indicates the serving area of the UE. In case of intersystem handover from EPS to GSM (SRVCC), this IE indicates that the source is E-UTRAN (see 3GPP TS 23.216). | +| NOTE 21: | This information element is included if a preference for other radio access technologies shall be applied to the MS connection. | +| NOTE 22: | This information element may be included to provide UE's SNA Access Information. This IE is provided in the HANDOVER REQUEST message only on the MAP-E interface. SNA Access Information is included in HANDOVER REQUEST message if HANDOVER REQUEST message including SNA Access Information does not exceed the maximum length defined for BSSMAP message. | +| NOTE 23: | This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. | +| NOTE 24: | These IEs are not included, if the Channel Type IE indicates "signalling". The Circuit Identity Code may be included, if at least one alternative for a TDM connection is included in Codec List (MSC Preferred). The AoIP Transport Layer Address (MGW) and Call Identifier may be included, if at least one alternative for an IP connection is included in Codec List (MSC Preferred). The HANDOVER REQUEST message may include both, a Circuit Identity Code and an AoIP Transport Layer Address (MGW) simultaneously. If the Codec List (MSC Preferred) is included in Handover Request, then the BSS shall not allocate a Circuit Identity Code on its own. For HANDOVER REQUEST messages sent on the A-Interface, at least one of Circuit Identity Code or AoIP Transport Layer Address (MGW) plus Call Identifier shall be included (except if the Channel Type IE indicates "signalling")(the same requirement does not apply for HANDOVER REQUEST messages sent on the MAP/E interface) | +| NOTE 25: | This IE is not included, if the Channel Type IE indicates "signalling". Codec List (MSC Preferred) shall be included if the core network supports an IP based user plane interface. The information in Codec List (MSC Preferred) shall be consistent with the information in Channel Type and with the information in Speech Version (Used), if included. | +| NOTE 26: | Void | +| NOTE 27: | This IE is included if the encryption algorithm A5/4 is indicated as permitted in the Encryption Information IE. | + +| | +|--------------------------------------------------------------------------| +| NOTE 28: This IE is included if local switching is requested by the MSC. | +|--------------------------------------------------------------------------| + +| | +|--------------------------------------------------------------------------------------------------------| +| NOTE 29: This IE is included if the MSC determines that CS to PS SRVCC is allowed for this connection. | +|--------------------------------------------------------------------------------------------------------| + +Typical Cause values are: + +- uplink quality; +- uplink strength; +- downlink quality; +- downlink strength; +- distance; +- better cell; +- response to MSC invocation; +- O and M intervention; +- directed retry; +- switch circuit pool; +- traffic; +- preemption; +- reduce load in serving cell. + +### 3.2.1.9 HANDOVER REQUIRED + +This message is sent from the BSS to the MSC to indicate that for a given MS which already has dedicated radio resource(s) assigned, a handover is required for the reason given by the cause element. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------|-----------|-----------|-------------|--------------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | +| Response Request | 3.2.2.28 | BSS-MSC | O (note 8) | 1 | +| Cell Identifier List (Preferred) | 3.2.2.27 | BSS-MSC | M (note 4) | 2n+3 to 7n+3 | +| Circuit Pool List | 3.2.2.46 | BSS-MSC | O (note 1) | V | +| Current Channel Type 1 | 3.2.2.49 | BSS-MSC | O (note 2) | 2 | +| Speech Version (Used) | 3.2.2.51 | BSS-MSC | O (note 3) | 2 | +| Queueing Indicator | 3.2.2.50 | BSS-MSC | O | 2 | +| Old BSS to New BSS Information | 3.2.2.58 | BSS-MSC | O | 2-n | +| Source RNC to target RNC transparent information (UMTS) | 3.2.2.76 | BSS-MSC | O (note 5) | 3-m | +| Source RNC to target RNC transparent information (cdma2000) | 3.2.2.77 | BSS-MSC | O (note 6) | n-m | +| GERAN Classmark | 3.2.2.78 | BSS-MSC | O (note 7) | V | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 9) | 2 | +| Speech Codec (Used) | 3.2.2.104 | BSS-MSC | O (note 10) | 3-5 | +| CSG Identifier | 3.2.2.110 | BSS-MSC | O (note 11) | 7 | +| Source eNB to target eNB transparent information (E-UTRAN) | 3.2.2.123 | BSS-MSC | O (note 12) | 3-m | +| CS to PS SRVCC Indication | 3.2.2.124 | BSS-MSC | O (note 13) | 1 | + +NOTE 1: Shall be included when the cause is "switch circuit pool" and the MSC allocates the A interface circuit. + +NOTE 2: This information element should always be included. + +NOTE 3: This information element should always be included when the channel mode is speech, and only in this case. + +NOTE 4: If intersystem handover from GSM to UMTS or to cdma2000 or SRVCC to E-UTRAN or UTRAN (HSPA) is performed, this information element indicates the target. Only one RNC identity is included for Intersystem Handover to UTRAN or to cdma2000 or when performing SRVCC to UTRAN (HSPA). Only one eNB Identifier is included when performing SRVCC to E-UTRAN. + +NOTE 5: This information element shall be included when intersystem handover to UMTS or SRVCC to UTRAN (HSPA) is to be performed. Source RNC to target RNC transparent information is a general container to carry Inter RAT Handover Info (UTRAN specific information) and Inter RAT UE radio access capability (Classmark Information Type 2 and Classmark Information Type 3) from BSS to RNC. The Inter RAT Handover Info and the Inter RAT UE radio access capability is conveyed in the RRC container INTER RAT HANDOVER INFO WITH INTER RAT CAPABILITIES as defined in 3GPP TS 25.331. + +NOTE 6: This information element shall be included when intersystem handover (cdma2000) is performed. Source RNC to target RNC transparent information is a general container to carry cdma2000 specific information from BSS to RNC. + +NOTE 7: This information element may be included when handover of CS services from GERAN A/Gb mode to GERAN Iu mode is performed (see sub-clause 3.1.5a.1). + +NOTE 8: This information element shall be included in the case of DTM Handover. + +NOTE 9: This information element is included for a talker or a new subscriber requesting the uplink in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. + +NOTE 10: Speech Codec (Used) shall be included if the radio access network supports an IP based user plane interface. This information element shall be consistent with the information in "Current Channel Type 1", if included, and with the information in Speech Version (Used), if included. + +NOTE 11: This information element shall be included when the target cell is a CSG cell or a Hybrid cell. + +NOTE 12: This information element shall be included when CS to PS SRVCC to E-UTRAN is to be performed. + +NOTE 13: This information element shall be included when CS to PS SRVCC to E-UTRAN or to UTRAN (HSPA) is required. + +Typical Cause values are: + +- uplink quality; + +- uplink strength; +- downlink quality; +- downlink strength; +- distance; +- better cell; +- response to MSC invocation; +- O&M intervention; +- directed retry; +- switch circuit pool; +- traffic; +- preemption; +- reduce load in serving cell. + +### 3.2.1.10 HANDOVER REQUEST ACKNOWLEDGE + +This message is sent from the BSS to the MSC and indicates that the request to support a handover at the target BSS can be supported by the BSS, and also to which radio channel(s) the MS should be directed. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------|-----------|-----------|-------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Layer 3 Information | 3.2.2.24 | BSS-MSC | M (note 1) | 11-n | +| Chosen Channel | 3.2.2.33 | BSS-MSC | O (note 4) | 2 | +| Chosen Encryption Algorithm | 3.2.2.44 | BSS-MSC | O (note 5) | 2 | +| Circuit Pool | 3.2.2.45 | BSS-MSC | O (note 2) | 2 | +| Speech Version (Chosen) | 3.2.2.51 | BSS-MSC | O (note 6) | 2 | +| Circuit Identity Code | 3.2.2.2 | BSS-MSC | O (note 3) | 3 | +| LSA Identifier | 3.2.2.15 | BSS-MSC | O (note 7) | 5 | +| New BSS to Old BSS Information | 3.2.2.80 | BSS-MSC | O (note 8) | 2-n | +| Inter-System Information | 3.2.2.81 | BSS-MSC | O (note 9) | 2-n | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 10) | 2 | +| AoIP Transport Layer Address (BSS) | 3.2.2.102 | BSS-MSC | O (note 11) | 8-20 | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | O (note 12) | 3-n | +| Speech Codec (Chosen) | 3.2.2.104 | BSS-MSC | O (note 12) | 3-5 | +| LCLS-BSS-Status | 3.2.2.119 | BSS-MSC | O (note 13) | 2 | + +NOTE 1: This information element carries a radio interface message. In the case of an Intersystem handover to UMTS this information element contains (on MAP-E interface) a HANDOVER TO UTRAN COMMAND message as defined in 3GPP TS 25.331. In the case of an Inter BSC handover or in the case of an Intersystem Handover from UTRAN to GSM or in the case of an Intersystem Handover from EPS to GSM (SRVCC), it contains a HANDOVER COMMAND message as defined in 3GPP TS 44.018. In the case of an Intersystem Handover from cdma2000, it contains a HANDOVER COMMAND message as defined in 3GPP TS 44.018. In the case of an Intersystem handover to cdma2000, this information element contains (on MAP-E interface) the HANDOVER TO CDMA2000 COMMAND message, as defined in 3GPP TS 44.018. + +NOTE 2: Shall be included when several circuit pools are present on the BSS MSC interface and a circuit was allocated by the HANDOVER REQUEST message. + +NOTE 3: The Circuit identity code information element is included mandatorily by the BSS if the BSS allocates the A interface circuits and a circuit is needed. If the Codec List (MSC Preferred) was included in Handover Request, then the BSS shall not allocate a Circuit Identity Code on its own. + +NOTE 4: Included at least when the channel rate/type choice was done by the BSS. + +NOTE 5: Included at least when the encryption algorithm has been selected by the BSS. + +NOTE 6: Included at least when the speech version choice was done by the BSS. + +NOTE 7: Shall be included if a potential current LSA in the target cell has been identified (see 3GPP TS 43.073). Not included means that there is no potential current LSA in the target cell. + +NOTE 8: In the case of an external handover, this information element may be included by the target BSS when traffic load information of the target cell is to be sent to the source BSS. + +NOTE 9: In the case of an inter-system handover from UTRAN or from cdma2000 to GSM, this information element may be included by the target BSS when traffic load information of the target cell is to be sent to the source system. + +NOTE 10: This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. + +NOTE 11: AoIP Transport Layer Address (BSS) shall be included if and only if the BSS has chosen an IP connection for the user plane interface. Included is the IP Transport Layer information of the BSS. + +NOTE 12: Codec List (BSS Supported) and Speech Codec (Chosen) shall be included if the radio access network supports an IP based user plane interface. The information in Codec List (BSS Supported) and the information in Speech Codec (Chosen) shall be consistent with the information in Chosen Channel, if included, and with the information in Speech Version (Chosen), if included. + +NOTE 13: This IE shall be included if LCLS is supported by BSS and Global Call Reference IE, LCLS-Configuration IE and LCLS-Connection-Status-Control IE were included in the HANDOVER REQUEST message. + +### 3.2.1.11 HANDOVER COMMAND + +This message is sent from the MSC to the BSS via the relevant SCCP connection and contains the target channel to which the MS should retune. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Layer 3 Information | 3.2.2.24 | MSC-BSS | M (note 1) | 11-n | +| Cell Identifier | 3.2.2.17 | MSC-BSS | O | 3-10 | +| New BSS to Old BSS Information | 3.2.2.80 | MSC-BSS | O (note 2) | 2-n | +| Talker Priority | 3.2.2.89 | MSC-BSS | O (note 3) | 2 | +| CN to MS transparent information | 3.2.2.125 | MSC-BSS | O (note 4) | 19-n | + +NOTE 1: This information element carries a radio interface message. In the case of an Intersystem handover to UMTS or CS to PS SRVCC to UTRAN (HSPA), this information element contains a HANDOVER TO UTRAN COMMAND message as defined in 3GPP TS 25.331. In the case of an Inter BSC handover, it contains an RR HANDOVER COMMAND message as defined in 3GPP TS 44.018. In the case of an Intersystem handover to cdma2000, this information element contains the HANDOVER TO CDMA2000 COMMAND message, as defined in 3GPP TS 44.018. In the case of a CS to PS SRVCC to E-UTRAN it contains a complete DL-DCCH-Message including a complete RRCConnectionReconfiguration radio interface message as defined in 3GPP TS 36.331. + +NOTE 2: This information element may be included if received from the target BSS or the target system. Its contents shall be equal to the received element. + +NOTE 3: This information element is included for a talker or a new subscriber requesting the uplink in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. + +NOTE 4: In case of CS to PS SRVCC to UTRAN (HSPA) or to E-UTRAN, this information element shall be included, + +### 3.2.1.12 HANDOVER COMPLETE + +This message is sent from the BSS to the MSC via the relevant SCCP connection. It is used in the Inter-BSS Handover Execution procedure and the Internal Handover Execution procedure with different contents in these two cases. + +It indicates that the correct MS has successfully accessed the target cell. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| RR Cause | 3.2.2.22 | BSS-MSC | O | 2 | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 1) | 2 | +| Speech Codec (Chosen) | 3.2.2.104 | BSS-MSC | O (note 2) | 3-5 | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | O (note 3) | 3-n | +| Chosen Encryption Algorithm | 3.2.2.44 | BSS-MSC | O (note 4) | 2 | +| Chosen Channel | 3.2.2.33 | BSS-MSC | O (note 5) | 2 | +| LCLS-BSS-Status | 3.2.2.119 | BSS-MSC | O (note 6) | 2 | + +NOTE 1: "Talker Priority" is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing in case of the Inter-BSS Handover procedure. + +NOTE 2: "Speech Codec (Chosen)" shall be included in case of the Internal Handover Execution procedure. + +NOTE 3: "Codec List (BSS Supported)" may be included in case of the Internal Handover Execution procedure. + +NOTE 4: "Chosen Encryption Algorithm" shall be included in case of the Internal Handover Execution procedure, if the encryption algorithm has been changed by the BSS. + +NOTE 5: "Chosen Channel" shall be included in case of the Internal Handover Execution procedure, if the channel count or the bit rate has changed for a CS data call. + +NOTE 6: This IE shall be included if LCLS is supported by BSS and if local switching was previously requested for this call leg by the MSC. + +### 3.2.1.13 HANDOVER SUCCEEDED + +This message is sent from the MSC to the old BSS via the relevant SCCP connection. + +It indicates that the correct MS has successfully accessed the target cell. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Talker Priority | 3.2.2.89 | MSC-BSS | O (note 1) | 2 | +| NOTE 1: This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. | | | | | + +### 3.2.1.14 HANDOVER CANDIDATE ENQUIRE + +This message is sent from the MSC to the BSS, using the connectionless services of the SCCP. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------|-----------|-----------|------|--------------------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Number Of Mss | 3.2.2.8 | MSC-BSS | M | 2 | +| Cell Identifier List | 3.2.2.27 | MSC-BSS | M | 2n+3
to
7n+3 | +| Cell Identifier | 3.2.2.17 | MSC-BSS | M | 3-10 | + +### 3.2.1.15 HANDOVER CANDIDATE RESPONSE + +This message is sent from the BSS to the MSC in response to receipt of a HANDOVER CANDIDATE ENQUIRE message. It contains the number of MSs for which HANDOVER REQUIRED messages have been sent. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Number Of Mss | 3.2.2.8 | BSS-MSC | M | 2 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M | 3-10 | + +### 3.2.1.16 HANDOVER FAILURE + +This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates to the MSC that there has been a failure in the resource allocation process on handover, and that the handover has been aborted. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | +| RR Cause | 3.2.2.22 | BSS-MSC | O | 2 | +| Circuit Pool | 3.2.2.45 | BSS-MSC | O (note 1) | 2 | +| Circuit Pool List | 3.2.2.46 | BSS-MSC | O (note 2) | V | +| GERAN Classmark | 3.2.2.78 | BSS-MSC | O (note 3) | V | +| New BSS to Old BSS Information | 3.2.2.80 | BSS-MSC | O (note 4) | 2-n | +| Inter-System Information | 3.2.2.81 | BSS-MSC | O (note 5) | 2-n | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 6) | 2 | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | O (note 7) | 3-n | +| NOTE 1: Shall be included when several circuit pools are present on the BSS MSC interface. | | | | | +| NOTE 2: May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences. | | | | | +| NOTE 3: May be included in case of inter-system handover to GERAN lu-mode via the E interface, if the "GERAN Classmark" IE was provided by the target BSC (see 3GPP TS 43.051). | | | | | +| NOTE 4: In the case of an external handover, this information element may be included by the target BSS when traffic load information of the target cell is to be sent to the source BSS. | | | | | +| NOTE 5: In the case of an inter-system handover from UTRAN or cdma2000 to GSM, this information element may be included by the target BSS when traffic load information of the target cell is to be sent to the source system. | | | | | +| NOTE 6: This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. | | | | | +| NOTE 7: This information element may be included if the radio access network supports an IP based user plane interface. | | | | | + +Typical Cause values are: + +- radio interface message failure; +- O and M intervention; +- Equipment failure; +- no radio resource available; +- requested terrestrial resource unavailable; +- requested transcoding/rate adaption unavailable; +- terrestrial resource already allocated; +- Call Identifier already allocated; +- invalid message contents; +- radio interface failure - reversion to old channel; +- ciphering algorithm not supported; +- circuit pool mismatch; +- switch circuit pool; +- requested speech version unavailable; +- traffic load in the target cell higher than in the source cell; +- incoming relocation not supported due to PUESBINE feature (This cause value is only sent by 3G\_MSC-B over the MAP/E interface); + +Requested A-Interface Type not supported; + +Requested Codec Type or Codec Configuration not supported; + +- Requested Codec Type or Codec Configuration unavailable; +- Requested A-Interface Type unavailable; +- Requested Redundancy Level not supported; +- Requested Redundancy Level not available; +- INTERNAL HANDOVER ENQUIRY reject. + +### 3.2.1.17 RESOURCE REQUEST + +This message is sent from the MSC to the BSS and requests the current spare and optionally the total accessible resource on a particular cell. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Periodicity | 3.2.2.12 | MSC-BSS | M | 2 | +| Resource Indication Method | 3.2.2.29 | MSC-BSS | M | 2 | +| Cell Identifier | 3.2.2.17 | MSC-BSS | M | 3-10 | +| Extended Resource Indicator | 3.2.2.13 | MSC-BSS | O | 2 | + +### 3.2.1.18 RESOURCE INDICATION + +This message is sent from the BSS to the MSC in response to a resource request message, the message includes an explicit indication of the cell concerned. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Resource Indication Method | 3.2.2.29 | BSS-MSC | M | 2 | +| Resource Available | 3.2.2.4 | BSS-MSC | O (note 1) | 21 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M | 3-10 | +| Total Resource Accessible | 3.2.2.14 | BSS-MSC | O (note 2) | 5 | + +NOTE 1: This element is not included if the message is sent only as an acknowledgement to the reception of a RESOURCE REQUEST message. + +NOTE 2: This element has to be included if requested by the Extended Resource Indicator, except when the message is sent only as an acknowledgement to the reception of the RESOURCE REQUEST message. + +### 3.2.1.19 PAGING + +This message is sent from the MSC to the BSS and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------|-----------|-----------|------------|-----------------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| IMSI | 3.2.2.6 | MSC-BSS | M | 3-10 | +| TMSI | 3.2.2.7 | MSC-BSS | O (note 1) | 6 | +| Cell Identifier List | 3.2.2.27 | MSC-BSS | M (note 4) | 3
to
3+7n | +| Channel Needed | 3.2.2.36 | MSC-BSS | O (note 2) | 2 | +| eMLPP Priority | 3.2.2.56 | MSC-BSS | O (note 3) | 2 | +| Paging Information | 3.2.2.85 | MSC-BSS | O | 2 | + +NOTE 1: This element is omitted in the exceptional case where the IMSI is used instead of the TMSI as a paging address at the radio interface. + +NOTE 2: If the channel needed element is not present, the default value is assumed to be 00 (any channel). + +NOTE 3: If the BSS implements the eMLPP feature it should use this information element to build the radio interface Paging request messages, otherwise the information may be considered as an unrecognisable information element. + +NOTE 4: When network sharing is supported, the PLMN included in the Location Area Identification field can be either the Common PLMN or an Additional PLMN (see 3GPP TS 44.018 [32]). + +### 3.2.1.20 CLEAR REQUEST + +This message is sent from the BSS to the MSC to indicate to the MSC that the BSS wishes to release the associated dedicated resource(s). + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | + +Typical Cause values are: + +- radio interface message failure; +- O and M intervention; +- equipment failure; +- Joined group call channel; +- protocol error between BSS and MSC; +- preemption; +- access restricted due to shared networks. + +### 3.2.1.21 CLEAR COMMAND + +This message is sent from the MSC to the BSS to instruct the BSS to release the associated dedicated resource(s). + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +This message is also sent from the MSC to the BSS to instruct the BSS to release the VGCS/VBS call controlling resources. In this case the message is sent via the VGCS/VBS call controlling SCCP connection. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|----------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Layer 3 Header Information | 3.2.2.9 | MSC-BSS | O (note) | 4 | +| Cause | 3.2.2.5 | MSC-BSS | M | 3-4 | +| CSFB Indication | 3.2.2.121 | MSC-BSS | O | 1 | +| NOTE: This information element doesn't serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of the present document, this information element will be deleted from this message. | | | | | + +Typical Cause values are: + +- call control; +- O and M intervention; +- equipment failure; +- requested terrestrial resource unavailable; +- handover successful; +- protocol error between BSS and MSC. + +### 3.2.1.22 CLEAR COMPLETE + +This message is sent from the BSS to the MSC to inform the MSC that the associated dedicated resource(s) has been successfully cleared. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +This message is also sent from the BSS to the MSC to inform the MSC that the VGCS/VBS call controlling resources have been successfully cleared. In this case the message is sent via the VGCS/VBS call controlling SCCP connection. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | + +### 3.2.1.23 RESET + +This message can be sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the transmitting entity has suffered a failure and has lost memory of the calls in progress, calls set up, and associated references. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Cause | 3.2.2.5 | Both | M | 3-4 | +| A-Interface Selector for RESET | 3.2.2.107 | Both | O | 2 | + +The optional A-Interface Selector for RESET IE allows selecting all calls associated to TDM circuits and/or all calls associated to IP links. If the A-Interface Selector for RESET IE is not present in the RESET message, then all calls shall be cleared (TDM and IP). + +Typical Cause values are: + +- O and M intervention; +- equipment failure. + +### 3.2.1.24 RESET ACKNOWLEDGE + +This message can be sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the transmitting entity has cleared all calls and reset all references, and is ready to resume service. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| A-Interface Selector for RESET | 3.2.2.107 | Both | O | 2 | + +The optional A-Interface Selector for RESET IE shall be included in RESET ACKNOWLEDGE as received in RESET. + +### 3.2.1.25 HANDOVER PERFORMED + +This message is sent from the BSS to the MSC in order to indicate that the BSS has performed an internal handover. + +The cell identifier and (if required for O and M reasons) optionally the new channel identity is included. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M (note 5) | 3-10 | +| Chosen Channel | 3.2.2.33 | BSS-MSC | O (note 1) | 2 | +| Chosen Encryption Algorithm | 3.2.2.44 | BSS-MSC | O (note 2) | 2 | +| Speech Version (Chosen) | 3.2.2.51 | BSS-MSC | O (note 3) | 2 | +| LSA Identifier | 3.2.2.15 | BSS-MSC | O (note 4) | 5 | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 6) | 2 | +| Codec List (BSS Supported) (serving cell) | 3.2.2.103 | BSS-MSC | O (note 7) | 3-n | +| Speech Codec (Chosen) | 3.2.2.104 | BSS-MSC | O (note 8) | 3-5 | +| LCLS-BSS-Status | 3.2.2.119 | BSS-MSC | O (note 9) | 2 | +| NOTE 1: Included at least when the channel rate/type has changed during the handover. | | | | | +| NOTE 2: Included at least when the encryption algorithm has been changed by the BSS. | | | | | +| NOTE 3: Included at least when the speech version has been changed by the BSS. | | | | | +| NOTE 4: Shall be included if current LSA in the new serving cell has been identified (see 3GPP TS 43.073). Not included means that there is no current LSA in the new serving cell. | | | | | +| NOTE 5: When sent from MSC-B over MAP/E interface this information element contains indication of Cell Identifier (e.g. CGI).
When sent from 3G_MSC-B over MAP/E interface this information element contains indication of Cell Identifier (e.g. CGI) if the handover target is GSM or indication of either RNC-ID (or Extended RNC-ID) or SAI (if known) if the handover target is UMTS (when indication of relocation complete is received from RNC) or indication of SAI when an indication of location report is received (intra UMTS relocation). Note: RNC-ID (or Extended RNC-ID) or SAI are only provided in the HANDOVER PERFORMED message over the MAP-E interface. | | | | | +| NOTE 6: This information element is included for a talker or a new subscriber requesting the uplink in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. | | | | | +| NOTE 7: Codec List (BSS Supported) (serving cell) may be included, if the radio access network supports an IP based user plane interface. The information in Codec List (BSS Supported) shall be consistent with the information in Chosen Channel, if included, and with the information in Speech Version (Chosen), if included. | | | | | +| NOTE 8: Speech Codec (Chosen) shall be included, if the radio access network supports an IP based user plane interface and if the speech Codec has been changed by the BSS. The information in Speech Codec (Chosen) shall be consistent with the information in Chosen Channel, if included, and with the information in Speech Version (Chosen), if included. | | | | | +| NOTE 9: This IE shall be included if LCLS is supported by BSS and if local switching was previously requested for this call leg by the MSC. | | | | | + +Typical Cause values: + +- as for the handover required message, except response to MSC invocation. + +### 3.2.1.26 OVERLOAD + +This message is sent from the BSS to the MSC or from the MSC to the BSS. When sent from the BSS to the MSC it indicates either processor overload of the whole BSS (cell identifier field not present) or overload of a CCCH downlink in which case the relevant cell is identified. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Cause | 3.2.2.5 | Both | M | 3-4 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | O | 3-10 | + +Typical Cause values are: + +- Processor overload; +- CCCH overload; +- O&M intervention. + +### 3.2.1.27 MSC INVOKE TRACE + +This message is sent from the MSC to the BSS in order to start production of a trace record at the BSS. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Trace Type | 3.2.2.37 | MSC-BSS | M | 2 | +| Triggerid | 3.2.2.38 | MSC-BSS | O | 3-22 | +| Trace Reference | 3.2.2.39 | MSC-BSS | M | 3 | +| Transactionid | 3.2.2.40 | MSC-BSS | O | 4 | +| Mobile Identity | 3.2.2.41 | MSC-BSS | O | 3-10 | +| OMCId | 3.2.2.42 | MSC-BSS | O | 3-22 | + +### 3.2.1.28 BSS INVOKE TRACE + +This message is sent from the BSS to the MSC in order to start production of a trace record at the MSC and/or from the MSC to BSS to target BSSs after a handover. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Trace Type | 3.2.2.37 | Both | M | 2 | +| Forward Indicator | 3.2.2.43 | Both | O | 2 | +| Triggerid | 3.2.2.38 | Both | O | 3-22 | +| Trace Reference | 3.2.2.39 | Both | M | 3 | +| TransactionId | 3.2.2.40 | Both | O | 4 | +| OMCId | 3.2.2.42 | Both | O | 3-22 | + +### 3.2.1.29 CLASSMARK UPDATE + +This message is sent from the BSS to the MSC or from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It updates the classmark parameters for the concerned MS. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Classmark Information Type 2 | 3.2.2.19 | Both | M | 4-5 | +| Classmark Information Type 3 | 3.2.2.20 | Both | O (note 1) | 3-34 | +| Talker Priority | 3.2.2.89 | Both | O (note 2) | 2 | +| NOTE 1: This element shall be included by the BSS if it was received from the MS. It shall be included by the MSC if this information element has previously been received by the MSC. | | | | | +| NOTE 2: This information element is included for a talker or a new subscriber requesting the uplink in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. | | | | | + +### 3.2.1.30 CIPHER MODE COMMAND + +This message is sent from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It updates the encryption parameters for the concerned MS. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Layer 3 Header Information | 3.2.2.9 | MSC-BSS | O (note 1) | 4 | +| Encryption Information | 3.2.2.10 | MSC-BSS | M | 3-n | +| Cipher Response Mode | 3.2.2.34 | MSC-BSS | O | 2 | +| KC 128 | 3.2.2.109 | MSC-BSS | C (note 2) | 17 | +| NOTE 1: This information element doesn't serve any useful purpose. MSCs should not send the information element unless it is required by the recipients (due to the need to interwork with older versions of the protocol). It is expected that in future versions of the present document, this information element will be deleted from this message. | | | | | +| NOTE 2: This IE is included if the encryption algorithm A5/4 is indicated as permitted in the Encryption Information IE. | | | | | + +### 3.2.1.31 CIPHER MODE COMPLETE + +This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that a successful cipher synchronisation has been achieved across the radio interface. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------------------------------|-----------|-----------|----------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Layer 3 Message Contents | 3.2.2.35 | BSS-MSC | O | 2-n | +| Chosen Encryption Algorithm | 3.2.2.44 | BSS-MSC | O (note) | 2 | +| NOTE: Included at least when the encryption algorithm has been selected by the BSS. | | | | | + +### 3.2.1.32 COMPLETE LAYER 3 INFORMATION + +The message is sent from the BSS to the MSC as described in sub-clause 3.1.16 (on receipt of the initial layer 3 message on a dedicated channel, e.g. PAGING RESPONSE, LOCATION UPDATING REQUEST, CM REESTABLISHMENT REQUEST, CM SERVICE REQUEST, IMSI DETACH, IMMEDIATE SETUP). + +The message is sent via the BSSAP SCCP connection established for the associated dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|----------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M (note 8) | 3-10 | +| Layer 3 Information | 3.2.2.24 | BSS-MSC | M | 3-n | +| Chosen Channel | 3.2.2.33 | BSS-MSC | O (note 1) | 2 | +| LSA Identifier List | 3.2.2.16 | BSS-MSC | O (note 2) | 3+3n | +| PADU | 3.2.2.68 | BSS-MSC | O (note 3) | 3-n | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | O (note 4) | 3-n | +| Redirect Attempt Flag | 3.2.2.111 | BSS-MSC | O (note 5) | 1 | +| Send Sequence Number | 3.2.2.113 | BSS-MSC | O (note 6) | 2 | +| IMSI | 3.2.2.6 | BSS-MSC | O (note 7) | 3-10 | +| Selected PLMN ID | 3.2.2.126 | BSS-MSC | O (note 8) | 4 | +| Selected Operator | 3.2.2.130 | BSS-MSC | O (note 9, 10) | 4 | +| PS Registered Operator | 3.2.2.131 | BSS-MSC | O (note 9, 11) | 4 | +| NOTE 1: This element is optionally used by the BSS to give the MSC a description of the channel rate/type on which the initial layer 3 message was received. | | | | | +| NOTE 2: This element shall be included at least when the current cell belongs to one or more LSAs. | | | | | +| NOTE 3: This element is optionally used by the BSS to provide Location Services related information to MSC. | | | | | +| NOTE 4: Codec List (BSS Supported) shall be included, if the radio access network supports an IP based user plane interface. | | | | | +| NOTE 5: This element indicates that the core network shall respond with a REROUTE COMMAND or REROUTE COMPLETE message. | | | | | +| NOTE 6: Send Sequence Number shall be included if received in REROUTE COMMAND. | | | | | +| NOTE 7: IMSI shall be included if received in REROUTE COMMAND. | | | | | +| NOTE 8: The selected PLMN ID shall be included in the case of a mobile station sending an initial Layer 3 message including a PLMN index (see 3GPP TS 24.008 [6]); in such a case the Common PLMN ID shall be included within the Cell Identifier IE. | | | | | +| NOTE 9: Only one of these two optional IEs shall be present in the message. | | | | | +| NOTE 10: This IE indicates the BSS selected CN operator. It is only included if the BSS supports CS/PS coordination enhancements. | | | | | +| NOTE 11: This IE is included if the BSS supports CS/PS coordination enhancements and if the mobile station is served by one of the shared CN operators in the PS domain. | | | | | + +### 3.2.1.33 QUEUEING INDICATION + +This message is sent from the BSS to the MSC in order to indicate a delay in the assignment of the required TCH. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | + +### 3.2.1.34 SAPI "n" REJECT + +This message is sent from the BSS to the MSC in order to indicate that a message with a SAPI value other than "0" has been rejected. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| DLCI | 3.2.2.25 | BSS-MSC | M | 2 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | + +Typical Cause values are: + +- O&M intervention; +- processor overload; +- BSS not equipped; +- MS not equipped. + +### 3.2.1.35 (void) + +### 3.2.1.36 (void) + +### 3.2.1.37 HANDOVER REQUIRED REJECT + +This message is sent from the MSC to the BSS via the relevant SCCP connection. It indicates to the BSS that the HANDOVER REQUIRED message has not resulted in handover. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Cause | 3.2.2.5 | MSC-BSS | M | 3-4 | +| New BSS to Old BSS Information | 3.2.2.78 | MSC-BSS | O (note 1) | 2-n | +| Talker Priority | 3.2.2.89 | MSC-BSS | O (note 2) | 2 | + +NOTE 1: This information element may be included if received from the target BSS or target system. Its contents shall be equal to the received element. + +NOTE 2: This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. + +Typical Cause values are: + +- equipment failure; +- no radio resource available; +- requested terrestrial resource unavailable; +- invalid message contents; +- requested transcoding/rate adaptation unavailable; +- O and M intervention; +- traffic load in target cell higher than in source cell; +- incoming relocation not supported due to PUESBINE feature. + +### 3.2.1.38 RESET CIRCUIT + +This message is sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the state of the circuit indicated in the message is unknown, due to a failure. This message is not relevant for an IP based user plane interface. + +This message is sent as a SCCP connectionless message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | Both | M | 3 | +| Cause | 3.2.2.5 | Both | M | 3-4 | + +Typical Cause values are: + +- for the RESET message. + +### 3.2.1.39 RESET CIRCUIT ACKNOWLEDGE + +This message is sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the transmitting entity has cleared a possible call using the circuit, and is ready to resume service. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Circuit Identity | 3.2.2.2 | Both | M | 3 | + +### 3.2.1.40 HANDOVER DETECT + +This message is sent from the BSS to the MSC via the relevant SCCP connection. It indicates that the correct MS has successfully accessed the target cell. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 1) | 2 | + +NOTE 1: This information element is included for a talker in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. + +### 3.2.1.41 CIRCUIT GROUP BLOCK + +This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a set of terrestrial resources (ie some timeslots within a system of 2Mbit PCM multiplex) must be remotely blocked at the circuit master, and cannot therefore be used for traffic. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Cause | 3.2.2.5 | Both | M | 3-4 | +| Circuit Identity Code | 3.2.2.2 | Both | M | 3 | +| Circuit Identity Code List | 3.2.2.31 | Both | M | 4-35 | + +Typical Cause values: + +- O & M intervention; +- equipment failure. + +### 3.2.1.42 CIRCUIT GROUP BLOCKING ACKNOWLEDGE + +This message is sent from the MSC to the BSS or from the BSS to the MSC to acknowledge the receipt of an earlier CIRCUIT GROUP BLOCK message, and to indicate that the circuits indicated in the status subfield of the Circuit Identity Code List have been remotely blocked. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | Both | M | 3 | +| Circuit Identity Code List | 3.2.2.31 | Both | M | 4-35 | + +### 3.2.1.43 CIRCUIT GROUP UNBLOCK + +This message is sent from the BSS to the MSC or from the MSC to the BSS to indicate that a set of terrestrial resources (ie some timeslots within a system of 2Mbit PCM multiplex) may be returned to service at the circuit master. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | Both | M | 3 | +| Circuit Identity Code List | 3.2.2.31 | Both | M | 4-35 | + +### 3.2.1.44 CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE + +This message is sent from the MSC to the BSS or from the MSC to the BSS to acknowledge the receipt of an earlier CIRCUIT GROUP UNBLOCK message, and to indicate that the circuits indicated in the status subfield of the Circuit Identity Code List are remotely unblocked. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | Both | M | 3 | +| Circuit Identity Code List | 3.2.2.31 | Both | M | 4-35 | + +### 3.2.1.45 CONFUSION + +This message is sent in either direction in response to a message which cannot be treated correctly for some reason, and for which another failure message cannot substitute. The use of this message may be under operator control. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Cause | 3.2.2.5 | Both | M | 3-4 | +| Diagnostics | 3.2.2.32 | Both | M | 4-n | + +Typical Cause values are: + +- invalid message contents; +- information element or field missing; +- incorrect value; +- unknown message type; +- unknown information element; +- protocol error between BSS and MSC; and + +- invalid cell. + +### 3.2.1.46 CLASSMARK REQUEST + +This message is sent from the MSC to the BSS via the relevant SCCP connection associated with that MS transaction. It requests an update of the classmark parameters for the concerned MS. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Talker Priority | 3.2.2.89 | MSC-BSS | O (note 1) | 2 | +| NOTE 1: This information element is included for a talker or a new subscriber requesting the uplink in a voice group call, if the network supports talker priority and uplink access option (i) (as defined in 3GPP TS 43.068) and A-interface link sharing. | | | | | + +### 3.2.1.47 UNEQUIPPED CIRCUIT + +This message is sent from the BSS to the MSC or vice versa to indicate to the partner entity that it is utilising one or several circuit identity codes which are unknown and which therefore should be locally blocked immediately and taken out of service. This message is not relevant for an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Circuit Identity Code | 3.2.2.2 | Both | M | 3 | +| Circuit Identity Code List | 3.2.2.31 | Both | O | 4-35 | + +### 3.2.1.48 CIPHER MODE REJECT + +This message is sent from the BSS to the MSC via the relevant SCCP connection associated with that MS transaction. It indicates that the BSS is unable to perform the requested ciphering. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | + +Typical Cause values are: + +- Ciphering algorithm not supported; +- Invalid message contents;- relocation triggered (NOTE). + +NOTE: This cause value is only sent by 3G\_MSC-B over the MAP/E interface (see 3GPP TS 29.010). + +### 3.2.1.49 LOAD INDICATION + +The LOAD INDICATION message is sent from the BSS to the MSC and from the MSC to the BSS. It indicates to the receiving entity that the transmitting BSS has detected a load situation in the concerned cell. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----------------| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Time Indication | 3.2.2.47 | Both | M | 2 | +| Cell Identifier | 3.2.2.17 | Both | M | 3-10 | +| Cell Identifier List (Target) | 3.2.2.27 | Both | M | 3
to
3+7n | +| Resource Situation | 3.2.2.48 | Both | O (note 1) | 4-N | +| Cause | 3.2.2.5 | Both | O (note 2) | 4-5 | +| NOTE 1: This information element can only be omitted, if the sending BSS wants to stop the whole incoming handover traffic to the indicated cell. | | | | | +| NOTE 2: Included at least when the reason for sending this message is other than traffic load. | | | | | + +Typical Cause values: + +- O & M intervention; +- Equipment failure; +- No radio resource available; +- Processor overload; +- Traffic load. + +### 3.2.1.50 VGCS/VBS SETUP + +This message is sent from the MSC to the BSS via the newly created SCCP connection in order to request the BSS to support a VGCS/VBS call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------|-----------|----------------|----------|----------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Group Call Reference | 3.2.2.55 | MSC-BSS | M | 7 | +| Priority | 3.2.2.18 | MSC-BSS | O | 3 | +| VGCS Feature Flags | 3.2.2.88 | MSC-BSS | O | 3 | + +### 3.2.1.51 VGCS/VBS SETUP ACK + +This message is sent from the BSS to the MSC via the newly created SCCP connection in order to confirm that the BSS will support the VGCS/VBS call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|-----------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| VGCS Feature Flags | 3.2.2.88 | BSS-MSC | O(note 1) | 3 | +| NOTE 1: This information shall only be included if the VGCS Feature Flags IE was present in the VGCS/VBS SETUP and the BSS supports the IE | | | | | + +### 3.2.1.52 VGCS/VBS SETUP REFUSE + +This message is sent from the BSS to the MSC via the newly created SCCP connection in order to reject the SETUP of the VGCS/VBS call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | + +### 3.2.1.53 VGCS/VBS ASSIGNMENT REQUEST + +This message is sent from the MSC to the BSS via the newly created VGCS/VBS resource controlling SCCP connection in order to request the BSS to assign radio resources in a cell to support a VGCS/VBS call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------|-----------|-----------|---------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Channel Type | 3.2.2.11 | MSC-BSS | M (note 2) | 5-13 | +| Assignment Requirement | 3.2.2.52 | MSC-BSS | M | 2 | +| Cell Identifier | 3.2.2.17 | MSC-BSS | M | 3-10 | +| Group Call Reference | 3.2.2.55 | MSC-BSS | M | 7 | +| Priority | 3.2.2.18 | MSC-BSS | O | 3 | +| Circuit Identity Code | 3.2.2.2 | MSC-BSS | O (note 4, 5) | 3 | +| Downlink DTX Flag | 3.2.2.26 | MSC-BSS | O (note 2, 4) | 2 | +| Encryption Information | 3.2.2.10 | MSC-BSS | O | 3-n | +| VSTK RAND | 3.2.2.83 | MSC-BSS | O (note 1) | 7 | +| VSTK | 3.2.2.84 | MSC-BSS | O (note 1) | 18 | +| Cell Identifier List Segment | 3.2.2.27a | MSC-BSS | O (note 3) | 4-? | +| AoIP Transport Layer Address (MGW) | 3.2.2.102 | MSC-BSS | O (note 6, 7) | 8-20 | +| Call Identifier | 3.2.2.105 | MSC-BSS | O (note 6, 7) | 5 | +| Codec List (MSC Preferred) | 3.2.2.103 | MSC-BSS | O (note 6, 7) | 3-n | + +NOTE 1: This information element is included for ciphered VGCS/VBS calls. +NOTE 2: If A-interface circuit sharing is used for a given VGCS/VBS call, the MSC shall include the same value for this information element in each VGCS/VBS ASSIGNMENT REQUEST message sent for this VGCS/VBS call to a specific BSS. +NOTE 3: This information element shall be included when A-interface link sharing is used if one or more cells have to be identified by this IE or one or more VGCS/VBS AREA CELL INFO messages is to follow. +NOTE 4: This information element shall be included when the MSC allocates the A-interface circuits. +NOTE 5: If A-interface circuit sharing is used and the MSC is responsible for allocating A-interface circuits the MSC shall include the same value for this information element in each VGCS/VBS ASSIGNMENT REQUEST sent to a given BSS relating to a given VGCS/VBS call. +NOTE 6: This information element shall be included if the core network supports an IP based user plane interface +NOTE 7: If A-interface circuit sharing is used for a given VGCS/VBS call, the MSC shall include the same value for this information element in each VGCS/VBS ASSIGNMENT REQUEST message sent for this VGCS/VBS call to a specific BSS. + +### 3.2.1.54 VGCS/VBS ASSIGNMENT RESULT + +The VGCS/VBS ASSIGNMENT RESULT message when received indicates the assignment/deassignment of radio resource for the indicated cell. + +The message is sent by the BSS via the BSSAP VGCS/VBS resource controlling SCCP connection associated with the dedicated resource. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|---------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Channel Type | 3.2.2.11 | BSS-MSC | M (note 3, 4) | 5 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M | 3-10 | +| Chosen Channel | 3.2.2.33 | BSS-MSC | O (note 2) | 2 | +| Circuit Identity Code | 3.2.2.2 | BSS-MSC | O (note 5) | 3 | +| Circuit Pool | 3.2.2.45 | BSS-MSC | O (note 1) | 2 | +| AoIP Transport Layer Address (BSS) | 3.2.2.102 | BSS-MSC | O (note 6, 7) | 8-20 | +| Speech Codec (Chosen) | 3.2.2.104 | BSS-MSC | O (note 6, 7) | 3-5 | +| Call Identifier | 3.2.2.105 | BSS-MSC | O (note 6, 7) | 5 | +| NOTE 1: Shall be included when several circuit pools are present on the BSS-MSC interface and a circuit was allocated by the VGCS/VBS ASSIGNMENT REQUEST message. | | | | | +| NOTE 2: Included at least when the channel choice was done by the BSS. | | | | | +| NOTE 3: Included even if BSS does not allocate radio resource immediately or de-allocate radio resource following VBS/VGCS uplink reply procedure. | | | | | +| NOTE 4: If A-interface circuit sharing is used for a given VGCS/VBS call, the BSS shall include the same Channel Type in each VGCS/VBS ASSIGNMENT RESULT message sent for this VGCS/VBS call. | | | | | +| NOTE 5: This information element shall be included by the BSS if the BSS allocates the A-interface circuits. If the BSS is responsible for allocating A-interface circuits and A-interface circuit sharing is used for a given VGCS/VBS call, this information element shall be set to the same value in each VGCS/VBS ASSIGNMENT RESULT message sent for this VGCS/VBS call. | | | | | +| NOTE 6: This information element shall be included if and only if the BSS has chosen an IP connection for the user plane interface. | | | | | +| NOTE 7: If A-interface circuit sharing is used for a given VGCS/VBS call, this information element shall be set to the same value in each VGCS/VBS ASSIGNMENT RESULT message sent for this VGCS/VBS call. | | | | | + +### 3.2.1.55 VGCS/VBS ASSIGNMENT FAILURE + +The VGCS/VBS ASSIGNMENT FAILURE message is sent from the BSS to the MSC via the relevant VGCS/VBS resource controlling SCCP connection. It indicates that there has been a failure in an assignment process at the BSS and that the VGCS/VBS Assignment procedure has been aborted for the concerned cell. + +In case of A-interface link sharing this message is only sent when the resource for the cell of origin could not be established, if the originating service subscriber is served by the BSC, or if no resource could be established. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | +| Circuit Pool | 3.2.2.45 | BSS-MSC | O (note 1) | 2 | +| Circuit Pool List | 3.2.2.46 | BSS-MSC | O (note 2) | V | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | O (note 3) | 3-n | +| NOTE 1: Shall be included when several circuit pools are present on the BSS-MSC interface. | | | | | +| NOTE 2: May be included when cause is "circuit pool mismatch" or "switch circuit pool" to indicate circuit pool preferences. | | | | | +| NOTE 3: Codec List (BSS Supported) should be included, if the radio access network supports an IP based user plane interface. | | | | | + +Typical Cause values are: + +- VGCS/VBS call non existent; +- O and M intervention; + +- equipment failure; +- no radio resource available; +- requested terrestrial resource unavailable; +- requested transcoding/rate adaptation unavailable; +- terrestrial resource already allocated; +- invalid message contents; +- circuit pool mismatch; +- switch circuit pool; +- ciphering algorithm not supported; +- requested speech version unavailable; +- requested A-Interface Type not supported; +- requested Codec Type or Codec Configuration not supported; +- requested A-Interface Type unavailable; +- requested Codec Type or Codec Configuration unavailable. + +### 3.2.1.56 VGCS/VBS QUEUING INDICATION + +The VGCS/VBS QUEUING INDICATION message is sent from the BSS to the MSC via the relevant VGCS/VBS resource controlling SCCP connection. It indicates that there is a delay in the assignment of radio resources for the cell. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | + +### 3.2.1.57 UPLINK REQUEST + +This message is sent from the BSS to the MSC in order to indicate that a mobile has requested to access the uplink of a voice group call channel. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|--------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 1) | 2 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | O (note 1) | 3-10 | +| Layer 3 Information | 3.2.2.24 | BSS-MSC | O (note 1,3) | 3-n | +| Mobile Identity | 3.2.2.41 | BSS-MSC | O (note 1,2) | 3-n | + +NOTE 1: This information is only included if the network supports talker priority. +NOTE 2: This element is only included when the talker priority request was made on the RACH +NOTE 3: This element is only included when the talker priority request was made on the group call channel + +### 3.2.1.58 UPLINK REQUEST ACKNOWLEDGE + +This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink allocation of the voice group call channel has been granted by the MSC. The message may also indicate the identity of the current talker + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Talker Priority | 3.2.2.89 | MSC-BSS | O (note 1) | 2 | +| Emergency set indication | 3.2.2.90 | MSC-BSS | O (note 1) | 1 | +| Talker Identity | 3.2.2.91 | MSC-BSS | O | 3-20 | + +NOTE 1: This information is only included if the network supports talker priority. + +### 3.2.1.59 UPLINK REQUEST CONFIRMATION + +This message is sent from the BSS to the MSC in order to indicate to the MSC that the uplink of the voice group call channel has been successfully established. The message may also indicate the identity of the current talker. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M | 3-10 | +| Talker Identity | 3.2.2.91 | BSS-MSC | O | 3-20 | +| Layer 3 Information | 3.2.2.24 | BSS-MSC | M | 3-n | + +### 3.2.1.59a UPLINK APPLICATION DATA + +This message is sent from the BSS to the MSC in order to pass to the MSC the layer 3 information which has been transmitted by a talker or listener of a group call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M | 3-10 | +| Layer 3 Information | 3.2.2.24 | BSS-MSC | M | 3-n | +| Application Data information | 3.2.2.100 | BSS-MSC | M | 3 | + +### 3.2.1.60 UPLINK RELEASE INDICATION + +This message is sent from the BSS to the MSC in order to indicate to the MSC that the uplink of the voice group call has been released. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | +| Talker Priority | 3.2.2.89 | BSS-MSC | O (note 1) | 2 | +| NOTE 1: This information is only included if the network supports talker priority. | | | | | + +Typical cause values: + +- radio interface failure; +- Call control; +- O and M intervention. + +### 3.2.1.61 UPLINK REJECT COMMAND + +This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink of the voice group call channel is not available for allocation to mobiles that have requested the use of the uplink. The message may also indicate the identity of the current talker. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Cause | 3.2.2.5 | MSC-BSS | M | 3-4 | +| Current Talker Priority | 3.2.2.89 | MSC-BSS | O (note 1) | 2 | +| Rejected Talker Priority | 3.2.2.89 | MSC-BSS | O (note 1) | 2 | +| Talker Identity | 3.2.2.91 | MSC-BSS | O | 3-20 | +| NOTE 1: This information is only included if the network supports talker priority. If talker priority is supported then both Current Talker Priority and Rejected Talker Priority shall be included. | | | | | + +Typical cause values: + +- radio interface message failure; +- Call control; + +- O and M intervention; +- Requested option not authorised. + +### 3.2.1.62 UPLINK RELEASE COMMAND + +This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink of the voice group call channel is available for allocation. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Cause | 3.2.2.5 | MSC-BSS | M | 3-4 | + +Typical cause values: + +- Call control; +- Invalid cell (in case the talker has left the Group Call Area). + +### 3.2.1.63 UPLINK SEIZED COMMAND + +This message is sent from the MSC to the BSS in order to indicate to the BSS that the uplink of the voice group call channel is no longer available for allocation. The message may also indicate the identity of the current talker. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Cause | 3.2.2.5 | MSC-BSS | M | 3-4 | +| Talker Priority | 3.2.2.89 | MSC-BSS | O (note 1) | 2 | +| Emergency set indication | 3.2.2.90 | MSC-BSS | O (note 1) | 1 | +| Talker Identity | 3.2.2.91 | MSC-BSS | O | 3-20 | + +NOTE 1: This information is only included if the network supports talker priority. + +Typical cause values: + +- Call control. + +### 3.2.1.64 SUSPEND + +The SUSPEND message is sent from the BSS to the MSC on the SCCP connection associated to an MS transaction. It indicates to the receiving entity that the transmitting BSS has detected an overload situation in the corresponding connection. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| DLCI | 3.2.2.25 | BSS-MSC | M | 2 | + +NOTE: The SUSPEND message may be only useful for PDSS1. + +### 3.2.1.65 RESUME + +The RESUME message is sent from the BSS to the MSC on the SCCP connection associated to an MS transaction. It indicates to the receiving entity that the overload situation in the corresponding connection does no more exist. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| DLCI | 3.2.2.25 | BSS-MSC | M | 2 | + +NOTE: The RESUME message may be only useful for PDSS1. + +### 3.2.1.66 CHANGE CIRCUIT + +This message is sent from the MSC to the BSS. It requests a change of the circuit allocated to a connection. This message is not relevant for an IP based user plane interface. + +This message is sent on the relevant SCCP connection. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Cause | 3.2.2.5 | MSC-BSS | M | 3-4 | + +Typical Cause values are: + +- Requested terrestrial resource unavailable; +- Terrestrial circuit already allocated. + +### 3.2.1.67 CHANGE CIRCUIT ACKNOWLEDGE + +This message is sent from the BSS to the MSC. It allocates a new circuit. This message is not relevant for an IP based user plane interface. + +This message is sent on the relevant SCCP connection. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Circuit identity | 3.2.2.2 | BSS-MSC | M | 3 | + +### 3.2.1.68 Common ID + +This message is sent from the MSC to the BSS in order to inform the BSS of the IMSI associated with this SCCP connection. + +This message is sent over the relevant SCCP connection, or, in the SCCP Connection Confirm message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| IMSI | 3.2.2.6 | MSC-BSS | M | 3-10 | +| SNA Access Information | 3.2.2.82 | MSC-BSC | O (note 1) | 2+n | +| Selected PLMN ID | 3.2.2.126 | MSC-BSC | O (note 3) | | +| Last used E-UTRAN PLMN ID | 3.2.2.127 | MSC-BSC | O (note 4) | 4 | +| NOTE 1: This information element may be included to provide UE's SNA Access Information. This IE is provided in the COMMON ID message only on the MAP-E interface. In association with inter MSC handover, SNA Access Information may be included in COMMON ID message if the SNA Access Information exceeded the remaining octets available in the HANDOVER REQUEST message.
NOTE 2: Void
NOTE 3: An MSC configured to use GWCN shall include this IE when the BSS indicates that the MS did not select a PLMN (MS non supporting network sharing)
NOTE 4: This information element should be included when the MSC supports return to the last used PLMN after CS fallback. | | | | | + +### 3.2.1.69 LSA INFORMATION + +This message is sent from the MSC to the BSS via the relevant SCCP connection in order to inform the BSS as to which LSA identities the mobile subscriber has subscription. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| LSA Information | 3.2.2.23 | MSC-BSS | M | 3+4n | + +## 3.2.1.70 (void) + +## 3.2.1.71 PERFORM LOCATION REQUEST + +This message is sent from the serving MSC to BSS via the relevant SCCP connection. It indicates to the receiving entity that actions related to Location Services needs to be performed. + +| INFORMATION ELEMENT | REFERENCE | TYPE | LEN | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------|------| +| Message Type | 3.2.2.1 | M | 1 | +| Location Type | 3.2.2.63 | M | 3-n | +| Cell Identifier | 3.2.2.17 | O | 5-10 | +| Classmark Information Type 3 | 3.2.2.20 | O | 3-34 | +| LCS Client Type | 3.2.2.67 | C (note 3) | 3-n | +| Chosen Channel | 3.2.2.33 | O | 2 | +| LCS Priority | 3.2.2.62 | O | 3-n | +| LCS QoS | 3.2.2.60 | C (note 1) | 3-n | +| GPS Assistance Data | 3.2.2.70 | C (note 2) | 3-n | +| APDU | 3.2.2.68 | O | 3-n | +| IMSI | 3.2.2.6 | O (note 4) | 5-10 | +| IMEI | 3.2.2.86 | O (note 4) | 10 | +| GANSS Location Type | 3.2.2.97 | C | 3 | +| GANSS Assistance Data | 3.2.2.95 | C (note 5) | 3-n | +| NOTE 1: The IE is present if location of the target MS is requested. | | | | +| NOTE 2: The IE is present if the GPS assistance data is requested. | | | | +| NOTE 3: The IE is present if the location type indicates a request for a location estimate and is optional otherwise. | | | | +| NOTE 4: The IMSI should be sent preferably if known. The IMEI could be sent if the IMSI is not known, or in addition to the IMSI for the purpose of allowing correlation between the two identities. | | | | +| NOTE 5: The IE is present if the GANSS assistance data is requested. | | | | + +## 3.2.1.72 PERFORM LOCATION RESPONSE + +This message is sent from the serving BSS to the MSC via the relevant SCCP connection in response to the PERFORM LOCATION REQUEST. It contains information related to result of positioning of the target MS. + +| INFORMATION ELEMENT | REFERENCE | TYPE | LEN | +|---------------------------------------------------------------------------------------------------|-----------|------------|-----| +| Message Type | 3.2.2.1 | M | 1 | +| Location Estimate | 3.2.2.64 | C (note 1) | 3-n | +| Positioning Data | 3.2.2.65 | O | 3-n | +| Deciphering Keys | 3.2.2.71 | C (note 2) | 3-n | +| LCS Cause | 3.2.2.66 | C (note 3) | 3-n | +| Velocity Estimate | 3.2.2.87 | O | 3-n | +| GANSS Positioning Data | 3.2.2.96 | O | 3-n | +| NOTE 1: The IE is present if location of the target MS was requested and the procedure succeeded. | | | | +| NOTE 2: These IEs are present if deciphering key was requested and the procedure succeeded | | | | +| NOTE 3: The IE is present if the procedure failed. | | | | + +## 3.2.1.73 PERFORM LOCATION ABORT + +This message is sent from the serving MSC to BSS via the relevant SCCP connection. It indicates to the receiving entity that actions related to Location Services needs to be aborted. + +| INFORMATION ELEMENT | REFERENCE | TYPE | LEN | +|---------------------|-----------|------|-----| +| Message Type | 3.2.2.1 | M | 1 | +| LCS Cause | 3.2.2.66 | M | 3-n | + +### 3.2.1.74 CONNECTIONLESS INFORMATION + +This message is sent from the BSS to the MSC or from the MSC to the BSS. The MSC forwards the CONNECTIONLESS INFORMATION message to the BSS as to which cell is indicated in the message. The message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Network Element Identity (source) | 3.2.2.69 | Both | M | 3-n | +| Network Element Identity (target) | 3.2.2.69 | Both | M | 3-n | +| APDU | 3.2.2.68 | Both | M | 3-n | +| Segmentation | 3.2.2.74 | Both | C (note 1) | 5 | +| Return Error Request | 3.2.2.72 | Both | C (note 2) | 3-n | +| Return Error Cause | 3.2.2.73 | Both | C (note 3) | 3-n | +| TLLI | 3.2.2.133 | Both | O (note 4) | 5 | +| MultilaterationTiming Advance | 3.2.2.134 | Both | O (note 5) | 3 | +| MS Synchronization Accuracy | 3.2.2.135 | Both | O (note 5) | 2 | +| BTS Reception Accuracy Level | 3.2.2.136 | Both | O (note 5) | 2 | +| Random ID | 3.2.2.137 | Both | O (note 4) | 3 | +| NOTE 1: This IE is present if and only if the APDU contains a message segment. | | | | | +| NOTE 2: The IE is present when the source of a message requests for an error response if the message cannot be delivered to its final destination. If this IE is present, then Return Error Cause shall not be present. | | | | | +| NOTE 3: The IE is present when an error is indicated that the message was not delivered to its final destination. If this IE is present, then Return Error Request shall not be present. Refer to 3GPP TS 49.031 [19a] for cause values | | | | | +| NOTE 4: The TLLI and Random ID are both included when the radio access part of the MTA procedure is performed using the RLC Data Block method. Only the Random ID is included when the radio access part of the MTA procedure is performed using the Extended Access Burst method. | | | | | +| NOTE 5: This IE is included when this message is sent during the MTA procedure. | | | | | + +### 3.2.1.75 CHANNEL MODIFY REQUEST + +This message is sent from the BSS to the MSC via the relevant SCCP connection in order to request the MSC to start the assignment procedure for changing the channel configuration according to assignment procedure defined in 3GPP TS 23.172 and 3GPP TS 25.413. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | + +The following cause value is applicable to this message: + +- Alternative channel configuration requested. + +NOTE: In this version of the protocol this message is supported only on the MAP E-interface in case of network-initiated SCUDIF 3GPP TS 23.172. With all other cause values the anchor MSC may ignore this message. + +### 3.2.1.76 EMERGENCY RESET INDICATION + +This message is sent from the BSS to the MSC to indicate that the BSS has received a request to reset the Emergency mode. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | O | 3-10 | +| Layer 3 Information | 3.2.2.24 | BSS-MSC | O (note 2) | 3-n | +| Mobile Identity | 3.2.2.41 | BSS-MSC | O (note 1) | 3-n | +| NOTE 1: This element is only included when the talker priority request was made on the RACH | | | | | +| NOTE 2: This element is only included when the talker priority request was made on the group call channel | | | | | + +### 3.2.1.77 EMERGENCY RESET COMMAND + +This message is sent from the MSC to the BSS in order to clear the Emergency mode in the BSS. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | + +### 3.2.1.78 VGCS ADDITIONAL INFORMATION + +This message is sent from the MSC to the BSS in order to transfer additional information regarding the identity of the current talker. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Talker Identity | 3.2.2.91 | MSC-BSS | M | 3-20 | + +### 3.2.1.79 VGCS/VBS AREA CELL INFO + +This message is sent from the MSC to the BSS via the VGCS/VBS resource controlling SCCP connection in order to transfer information about additional cells for a given group call that could not be sent in the VGCS/VBS ASSIGNMENT REQUEST or previous VGCS/VBS AREA CELL INFO messages. The VGCS/VBS ASSIGNMENT REQUEST and VGCS/VBS AREA CELL INFO messages are sent one after the other until the complete set of cells of that group call area is transferred to the BSS. + +This message is only sent in case of A-interface link sharing. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Cell Identifier List Segment | 3.2.2.27a | MSC-BSS | M | 4-? | +| Assignment Requirement | 3.2.2.52 | MSC-BSS | O | 2 | + +### 3.2.1.80 VGCS/VBS ASSIGNMENT STATUS + +The VGCS/VBS ASSIGNMENT STATUS message is sent from the BSS to the MSC via the VGCS/VBS resource controlling SCCP connection in order to indicate to the MSC for each cell belonging to a group call area that is controlled by this SCCP connection, whether the radio resources for the indicated cells have been assigned, not assigned/released or optionally waiting to be established. + +In the case of A-interface link sharing, one or more instances of the message are sent after expiry of timer Tast if there is a change in the channel allocation for this group call. Timer Tast shall be re-started each time it expires until the A-interface link is released. The message shall be sent immediately when the group call is established in all cells for the first time. + +In the case of group call re-establishment by the BSS and no A-interface link sharing, the message is sent if there is a change in the channel allocation. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cell Identifier List Segment for established cells | 3.2.2.27b | BSS-MSC | O (note 1) | 3-? | +| Cell Identifier List Segment for cells to be established | 3.2.2.27c | BSS-MSC | O (note 1) | 3-? | +| Cell Identifier List Segment for released cells - no user present | 3.2.2.27e | BSS-MSC | O (note 1) | 3-? | +| Cell Identifier List Segment for not established cells - no establishment possible | 3.2.2.27f | BSS-MSC | O (note 1) | 3-? | +| VGCS/VBS Cell Status | 3.2.2.94 | BSS-MSC | O (note 2) | 3 | +| NOTE 1: .These elements are only included in case of A-interface link sharing.
NOTE 2: .This element is only included in case of no A-interface link sharing. | | | | | + +The different Cell Identifier List IEs shall contain only those cells whose status has changed since the last VGCS/VBS ASSIGNMENT STATUS message (or group of VGCS/VBS ASSIGNMENT STATUS messages) was sent. + +The *Cell Identifier List Segment for established cells* IE contains the established cells. + +The *Cell Identifier List Segment for cells to be established* IE contains the cells where the call has not been established or has been released. Re-establishment by the BSS is being attempted. + +The *Cell Identifier List Segment for released cells - no user present* IE contains the cells in which the call was released because no user responded to the latest uplink access request. + +The *Cell Identifier List Segment for not established cells - no establishment possible* IE contains the cells in which the call has not been established or where the call was released and (in either case) no establishment by the BSS is possible. + +### 3.2.1.81 VGCS SMS + +This message is sent from the MSC to the BSS in order to transfer a short message to the VGCS group call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| SMS to VGCS | 3.2.2.92 | MSC-BSS | M | 2-250 | + +### 3.2.1.82 NOTIFICATION DATA + +This message is sent from the MSC to the BSS in order to transfer Application data to the listeners and the talker of an on-going group call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Application Data | 3.2.2.98 | MSC-BSS | M | 11 | +| Data Identity | 3.2.2.99 | MSC-BSS | M | 3 | +| MSISDN | 3.2.2.101 | MSC-BSS | O | 2-12 | + +### 3.2.1.83 INTERNAL HANDOVER REQUIRED + +This message may be sent if and only if both the BSS and the MSC support an IP based user plane A-interface. + +This message is sent from the BSS to the MSC to indicate that for a given MS, which already has dedicated radio resource(s) assigned, a handover is required to a cell in the same BSS, for the reason given by the cause element. + +This message is used when the intra-BSS handover implies a Codec Type or a Codec Configuration or an A-interface Type in the target cell, which is incompatible with the one used in the source cell. The source cell and target cell can be the same cell. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| Cause | 3.2.2.5 | BSS-MSC | M | 3-4 | +| Cell Identifier | 3.2.2.17 | BSS-MSC | M | 4-10 | +| AoIP Transport Layer Address (BSS) | 3.2.2.102 | BSS-MSC | C (Note 1) | 8-20 | +| Codec List (BSS Supported) | 3.2.2.103 | BSS-MSC | M | 3-n | +| NOTE 1: This information elements shall be included only if the support of an IP based user plane interface is indicated in the Codec List (BSS Supported) IE. | | | | | + +Typical Cause values are: + +- uplink quality; +- uplink strength; +- downlink quality; +- downlink strength; +- distance; + +- better cell; +- O&M intervention; +- traffic; +- preemption; +- reduce load in serving cell; +- response to an INTERNAL HANDOVER ENQUIRY message; +- Redundancy Level not adequate. + +### 3.2.1.84 INTERNAL HANDOVER REQUIRED REJECT + +This message may be sent if and only if both the BSS and the MSC support an IP based user plane interface. + +This message is sent from the MSC to the BSS via the relevant SCCP connection. It indicates to the BSS that the handover required by the previous INTERNAL HANDOVER REQUIRED message can not be supported, because none of the options indicated in the Codec List (BSS supported) can be fulfilled by the MSC. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Cause | 3.2.2.5 | MSC-BSS | M | 3-4 | +| Codec List (MSC Preferred) | 3.2.2.103 | MSC-BSS | O | 3-n | + +Typical Cause values are: + +- Requested A-Interface Type not supported; +- Requested Codec Type or Codec Configuration not supported; +- Requested A-Interface Type unavailable; +- Requested Codec Type or Codec Configuration unavailable; +- Requested terrestrial resource unavailable; +- Requested Redundancy Level not supported. +- Requested Redundancy Level not available; + +### 3.2.1.85 INTERNAL HANDOVER COMMAND + +This message may be sent if and only if both the BSS and the MSC support an IP based user plane interface. + +This message is sent from the MSC to the BSS. + +The message is sent via the BSSAP SCCP connection associated with the dedicated resource(s). + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Speech Codec (MSC Chosen) | 3.2.2.104 | MSC-BSS | M (note 1) | 3-n | +| Circuit Identity Code | 3.2.2.2 | MSC-BSS | C (note 2) | 3 | +| AoIP Transport Layer Address (MGW) | 3.2.2.102 | MSC-BSS | C (note 3) | 8-20 | +| Call Identifier | 3.2.2.105 | MSC-BSS | C (note 4) | 5 | +| Downlink DTX Flag | 3.2.2.26 | MSC-BSS | O (note 5) | 2 | +| LCLS-Connection-Status-Control | 3.2.2.117 | MSC-BSS | O (note 6) | 2 | +| NOTE 1: "Speech Codec (MSC Chosen)" contains in general only one Codec Type, one Codec Configuration and always only one A-Interface Type (TDM or IP). The exception is for compatible Codec Types, when more than one compatible Codec Type(s) can be included, with the same or compatible Codec Configuration(s). | | | | | +| NOTE 2: Circuit Identity Code shall be included, if and only if the A-Interface Type in Speech Codec (MSC Chosen) is TDM. | | | | | +| NOTE 3: AoIP Transport Layer Address (MGW) shall be included, if and only if the A-Interface Type in Speech Codec (MSC Chosen) is IP. | | | | | +| NOTE 4: Call Identifier shall be included, if and only if the (new) A-Interface Type in Speech Codec (MSC Chosen) is IP and the old A-Interface Type was not IP. | | | | | +| NOTE 5: Downlink DTX Flag may be included in the case of a speech TCH, and only in this case. If not included, this has no impact on the DTX function in the BSS. This element shall be neglected by the BSS, if an IP A-Interface type is finally selected and speech transcoder resources are not allocated within the BSS. | | | | | +| NOTE 6: This IE is included if local switching is requested by the MSC and if the MSC has not previously (in another BSSAP message) included this IE with indication to "Connect" this particular call leg. | | | | | + +### 3.2.1.86 INTERNAL HANDOVER ENQUIRY + +This message may be sent if and only if both the BSS and the MSC support an IP based user plane A-interface. + +This message is sent from the MSC to the BSS via the relevant SCCP connection to trigger a "BSS Internal Handover" procedure to ensure that the best fit of dedicated resource(s) (Codec Type, Codec Configuration and A-Interface Type indicated in the Speech Codec (MSC Chosen)) are allocated to the ongoing call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Speech Codec (MSC Chosen) | 3.2.2.104 | MSC-BSS | M | 3-n | + +### 3.2.1.87 RESET IP RESOURCE + +This message is sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the sending entity requests the receiving entity to release resources and references associated to the Call Identifiers included in the Call Identifier List. This message shall only be used for connections using an IP based user plane interface. + +This message is sent as a SCCP connectionless message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Cause | 3.2.2.5 | Both | M | 3-4 | +| Call Identifier List | 3.2.2.106 | Both | M | 6-n | + +Typical Cause values are: + +- O & M intervention; +- equipment failure. + +### 3.2.1.88 RESET IP RESOURCE ACKNOWLEDGE + +This message is sent either from the BSS to the MSC or from the MSC to the BSS. It indicates to the receiving entity that the transmitting entity has released resources and references associated to the Call Identifiers included in the Call Identifier List. This message shall only be used for connections using an IP based user plane interface. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | Both | M | 1 | +| Call Identifier List | 3.2.2.106 | Both | M | 6-n | + +### 3.2.1.89 REROUTE COMMAND + +This message is sent from the MSC to the BSS via the relevant SCCP connection in order to request rerouting by the BSC to another CN operator. It is only used in MOCN and GWCN configurations for network sharing. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Initial Layer 3 Information | 3.2.2.24 | MSC-BSS | M (note 1) | 3-n | +| Reroute Reject Cause | 3.2.2.112 | MSC-BSS | M (note 2) | 2 | +| Layer 3 Information | 3.2.2.24 | MSC-BSS | O (note 3) | 3-n | +| Send Sequence Number | 3.2.2.113 | MSC-BSS | O (note 4) | 2 | +| IMSI | 3.2.2.6 | MSC-BSS | O (note 5) | 3-10 | +| Old Location Area Identification | 3.2.2.128 | MSC-BSS | O (note 6) | 6 | +| Attach Indicator | 3.2.2.129 | MSC-BSS | O (note 7) | 1 | + +NOTE 1: The initial Layer 3 Information received from MS. +NOTE 2: This IE lists cause values which meaning is defined in [6] with the exception of "CS/PS domain registration coordination required" that will never be forwarded to the MS. +NOTE 3: This information element contains a mobility management message (e.g. Location Updating Reject). This information element is not needed when CS/PS coordination is indicated but shall be included in all other cases. +NOTE 4: Contains the value of the N(SD) as defined in [6]. +NOTE 5: This IE shall be included if available in the MSC. +NOTE 6: This IE is only included if the MSC supports CS/PS coordination enhancements. +NOTE 7: This IE indicates an IMSI attach request from the MS. It may only be included if the MSC supports CS/PS coordination enhancements. + +### 3.2.1.90 REROUTE COMPLETE + +This message is sent from the MSC to the BSS via the relevant SCCP connection in order to indicate that the redirection is completed. It is only used in MOCN and GWCN configurations for network sharing. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|--------------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| Reroute complete outcome | 3.2.2.114 | MSC-BSS | M | 2 | + +### 3.2.1.91 LCLS-CONNECT-CONTROL + +This message may be sent if and only if both the BSS and the MSC support LCLS. + +This message is sent from the MSC to the BSS to request a change of the LCLS connection preference and/or the LCLS connection status for a call leg in the BSS. It is sent for each call leg, associated to the relevant SCCP connection. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------------------------------------------------------|-----------|-----------|-----------|-----| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| LCLS-Configuration | 3.2.2.116 | MSC-BSS | O (note1) | 2 | +| LCLS-Connection-Status-Control | 3.2.2.117 | MSC-BSS | O (note1) | 2 | +| NOTE 1: At least one of these IE's shall be present in the message. | | | | | + +### 3.2.1.92 LCLS-CONNECT-CONTROL-ACK + +This message may be sent if and only if both the BSS and the MSC support LCLS. + +This message is sent from the BSS to the MSC via the relevant SCCP connection to acknowledge the LCLS-CONNECT-CONTROL message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| LCLS-BSS-Status | 3.2.2.119 | BSS-MSC | M | 2 | + +### 3.2.1.93 LCLS-NOTIFICATION + +This message may be sent if and only if both the BSS and the MSC support LCLS. + +This message is sent from the BSS to the MSC via the relevant SCCP connection to inform the MSC about a change in the LCLS connection status for the associated call leg. This message may also be sent as a request to release the locally switched call. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|-----------------------------------------------------------------|-----------|-----------|------------|-----| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| LCLS-BSS-Status | 3.2.2.119 | BSS-MSC | O (note 1) | 2 | +| LCLS-Break-Request | 3.2.2.120 | BSS-MSC | O (note 1) | 1 | +| NOTE 1: Only one of these IE's shall be present in the message. | | | | | + +### 3.2.1.94 MS REGISTRATION ENQUIRY + +This message is sent from the BSS to the MSC to retrieve registration information for a given mobile station. It is used in MOCN and GWCN configurations for network sharing. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|---------------------|-----------|-----------|------|------| +| Message Type | 3.2.2.1 | BSS-MSC | M | 1 | +| IMSI | 3.2.2.6 | BSS-MSC | M | 3-10 | + +### 3.2.1.95 MS REGISTRATION ENQUIRY RESPONSE + +This message is sent from the MSC to the BSS to provide registration information for a given mobile station. It is used in MOCN and GWCN configurations for network sharing. + +This message is sent as a connectionless SCCP message. + +| INFORMATION ELEMENT | REFERENCE | DIRECTION | TYPE | LEN | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|------------|------| +| Message Type | 3.2.2.1 | MSC-BSS | M | 1 | +| IMSI | 3.2.2.6 | MSC-BSS | M | 3-10 | +| CS Registered Operator | 3.2.2.132 | MSC-BSS | O (note 1) | 4 | +| NOTE 1: This IE identifies the serving CN operator for the mobile station associated to the IMSI.
Omitting this IE from the message has the significance of no serving CN operator for the mobile station (IMSI). | | | | | + +## 3.2.2 Signalling element coding + +### 3.2.2.0 General + +This sub-clause contains the coding of the signalling elements used. + +The following conventions are assumed for the sequence of transmission of bits and bytes: + +- Each bit position is marked as 1 to 8. Bit 1 is the least significant bit and is transmitted first; +- In an element octets are identified by number, octet 1 is transmitted first, then octet 2, etc. + +When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. + +- For variable length elements a length indicator is included, this indicates the number of octets following in the element; +- All fields within Information Elements are mandatory unless otherwise specified. The Information Element Identifier shall always be included. + +All spare bits are set to 0. + +**Table 3.2.2.1: Signalling elements used and their coding** + +| Element Identifier Coding | Element name | Reference | +|---------------------------|------------------------------------|-----------| +| 0000 0001 | Circuit Identity Code | 3.2.2.2 | +| 0000 0010 | Reserved (see note 2) | * | +| 0000 0011 | Resource Available | 3.2.2.4 | +| 0000 0100 | Cause | 3.2.2.5 | +| 0000 0101 | Cell Identifier | 3.2.2.17 | +| 0000 0110 | Priority | 3.2.2.18 | +| 0000 0111 | Layer 3 Header Information | 3.2.2.9 | +| 0000 1000 | IMSI | 3.2.2.6 | +| 0000 1001 | TMSI | 3.2.2.7 | +| 0000 1010 | Encryption Information | 3.2.2.10 | +| 0000 1011 | Channel Type | 3.2.2.11 | +| 0000 1100 | Periodicity | 3.2.2.12 | +| 0000 1101 | Extended Resource Indicator | 3.2.2.13 | +| 0000 1110 | Number Of MSs | 3.2.2.8 | +| 0000 1111 | Reserved (see note 2) | * | +| 0001 0000 | Reserved (see note 2) | * | +| 0001 0001 | Reserved (see note 2) | * | +| 0001 0010 | Classmark Information Type 2 | 3.2.2.19 | +| 0001 0011 | Classmark Information Type 3 | 3.2.2.20 | +| 0001 0100 | Interference Band To Be Used | 3.2.2.21 | +| 0001 0101 | RR Cause | 3.2.2.22 | +| 0001 0110 | Reserved (see note 2) | * | +| 0001 0111 | Layer 3 Information | 3.2.2.24 | +| 0001 1000 | DLCI | 3.2.2.25 | +| 0001 1001 | Downlink DTX Flag | 3.2.2.26 | +| 0001 1010 | Cell Identifier List | 3.2.2.27 | +| 0001 1011 | Response Request | 3.2.2.28 | +| 0001 1100 | Resource Indication Method | 3.2.2.29 | +| 0001 1101 | Classmark Information Type 1 | 3.2.2.30 | +| 0001 1110 | Circuit Identity Code List | 3.2.2.31 | +| 0001 1111 | Diagnostic | 3.2.2.32 | +| 0010 0000 | Layer 3 Message Contents | 3.2.2.35 | +| 0010 0001 | Chosen Channel | 3.2.2.33 | +| 0010 0010 | Total Resource Accessible | 3.2.2.14 | +| 0010 0011 | Cipher Response Mode | 3.2.2.34 | +| 0010 0100 | Channel Needed | 3.2.2.36 | +| 0010 0101 | Trace Type | 3.2.2.37 | +| 0010 0110 | Triggerid | 3.2.2.38 | +| 0010 0111 | Trace Reference | 3.2.2.39 | +| 0010 1000 | Transactionid | 3.2.2.40 | +| 0010 1001 | Mobile Identity | 3.2.2.41 | +| 0010 1010 | OMCId | 3.2.2.42 | +| 0010 1011 | Forward Indicator | 3.2.2.43 | +| 0010 1100 | Chosen Encryption Algorithm | 3.2.2.44 | +| 0010 1101 | Circuit Pool | 3.2.2.45 | +| 0010 1110 | Circuit Pool List | 3.2.2.46 | +| 0010 1111 | Time Indication | 3.2.2.47 | +| 0011 0000 | Resource Situation | 3.2.2.48 | +| 0011 0001 | Current Channel type 1 | 3.2.2.49 | +| 0011 0010 | Queueing Indicator | 3.2.2.50 | +| 0100 0000 | Speech Version | 3.2.2.51 | +| 0011 0011 | Assignment Requirement | 3.2.2.52 | +| 0011 0101 | Talker Flag | 3.2.2.54 | +| 0011 0110 | Connection Release Requested | 3.2.2.3 | +| 0011 0111 | Group Call Reference | 3.2.2.55 | +| 0011 1000 | eMLPP Priority | 3.2.2.56 | +| 0011 1001 | Configuration Evolution Indication | 3.2.2.57 | +| 0011 1010 | Old BSS to New BSS Information | 3.2.2.58 | +| 0011 1011 | LSA Identifier | 3.2.2.15 | +| 0011 1100 | LSA Identifier List | 3.2.2.16 | +| 0011 1101 | LSA Information | 3.2.2.23 | +| 0011 1110 | LCS QoS | 3.2.2.60 | +| 0011 1111 | LSA access control suppression | 3.2.2.61 | +| 0100 0011 | LCS Priority | 3.2.2.62 | + +| Element Identifier Coding | Element name | Reference | +|---------------------------|------------------------------------------------------------------------------------|-----------| +| 0100 0100 | Location Type | 3.2.2.63 | +| 0100 0101 | Location Estimate | 3.2.2.64 | +| 0100 0110 | Positioning Data | 3.2.2.65 | +| 0100 0111 | LCS Cause | 3.2.2.66 | +| 0100 1000 | LCS Client Type | 3.2.2.67 | +| 0100 1001 | APDU | 3.2.2.68 | +| 0100 1010 | Network Element Identity | 3.2.2.69 | +| 0100 1011 | GPS Assistance Data | 3.2.2.70 | +| 0100 1100 | Deciphering Keys | 3.2.2.71 | +| 0100 1101 | Return Error Request | 3.2.2.72 | +| 0100 1110 | Return Error Cause | 3.2.2.73 | +| 0100 1111 | Segmentation | 3.2.2.74 | +| 0101 0000 | Service Handover | 3.2.2.75 | +| 0101 0001 | Source RNC to target RNC transparent information (UMTS) | 3.2.2.76 | +| 0101 0010 | Source RNC to target RNC transparent information (cdma2000) | 3.2.2.77 | +| 0101 0011 | GERAN Classmark | 3.2.2.78 | +| 0101 0100 | GERAN BSC Container | 3.2.2.79 | +| 0110 0001 | New BSS to Old BSS Information | 3.2.2.80 | +| 0110 0011 | Inter-System Information | 3.2.2.81 | +| 0110 0100 | SNA Access Information | 3.2.2.82 | +| 0110 0101 | VSTK RAND Information | 3.2.2.83 | +| 0110 0110 | VSTK Information | 3.2.2.84 | +| 0110 0111 | Paging Information | 3.2.2.85 | +| 0110 1000 | IMEI | 3.2.2.86 | +| 0101 0101 | Velocity Estimate | 3.2.2.87 | +| 0110 1001 | VGCS Feature Flags | 3.2.2.88 | +| 0110 1010 | Talker Priority | 3.2.2.89 | +| 0110 1011 | Emergency Set Indication | 3.2.2.90 | +| 0110 1100 | Talker Identity | 3.2.2.91 | +| 0110 1101 | Cell Identifier List Segment | 3.2.2.27a | +| 0110 1110 | SMS to VGCS | 3.2.2.92 | +| 0110 1111 | VGCS Talker Mode | 3.2.2.93 | +| 0111 0000 | VGCS/VBS Cell Status | 3.2.2.94 | +| 0111 0001 | Cell Identifier List Segment for established cells | 3.2.2.27b | +| 0111 0010 | Cell Identifier List Segment for cells to be established | 3.2.2.27c | +| 0111 0011 | Cell Identifier List Segment for released cells - no user present | 3.2.2.27e | +| 0111 0100 | Cell Identifier List Segment for not established cells - no establishment possible | 3.2.2.27f | +| 0111 0101 | GANSS Assistance Data | 3.2.2.95 | +| 0111 0110 | GANSS Positioning Data | 3.2.2.96 | +| 0111 0111 | GANSS Location Type | 3.2.2.97 | +| 0111 1000 | Application Data | 3.2.2.98 | +| 0111 1001 | Data Identity | 3.2.2.99 | +| 0111 1010 | Application Data Information | 3.2.2.100 | +| 0111 1011 | MSISDN | 3.2.2.101 | +| 0111 1100 | AoIP Transport Layer Address | 3.2.2.102 | +| 0111 1101 | Speech Codec List | 3.2.2.103 | +| 0111 1110 | Speech Codec | 3.2.2.104 | +| 0111 1111 | Call Identifier | 3.2.2.105 | +| 1000 0000 | Call Identifier List | 3.2.2.106 | +| 1000 0001 | A-Interface Selector for RESET | 3.2.2.107 | +| 1000 0010 | Reserved | # | +| 1000 0011 | Kc 128 | 3.2.2.109 | +| 1000 0100 | CSG Identifier | 3.2.2.110 | +| 1000 0101 | Redirect Attempt Flag | 3.2.2.111 | +| 1000 0110 | Reroute Reject Cause | 3.2.2.112 | +| 1000 0111 | Send Sequence Number | 3.2.2.113 | +| 1000 1000 | Reroute complete outcome | 3.2.2.114 | +| 1000 1001 | Global Call Reference | 3.2.2.115 | +| 1000 1010 | LCLS-Configuration | 3.2.2.116 | +| 1000 1011 | LCLS-Connection-Status-Control | 3.2.2.117 | + +| Element Identifier Coding | Element name | Reference | +|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|------------------| +| 1000 1100 | LCLS-Correlation-Not-Needed | 3.2.2.118 | +| 1000 1101 | LCLS-BSS-Status | 3.2.2.119 | +| 1000 1110 | LCLS-Break-Request | 3.2.2.120 | +| 1000 1111 | CSFB Indication | 3.2.2.121 | +| 1001 0000 | CS to PS SRVCC | 3.2.2.122 | +| 1001 0001 | Source eNB to target eNB transparent information (E-UTRAN) | 3.2.2.123 | +| 1001 0010 | CS to PS SRVCC Indication | 3.2.2.124 | +| 1001 0011 | CN to MS transparent information | 3.2.2.125 | +| 1001 0100 | Selected PLMN ID | 3.2.2.126 | +| 1001 0101 | Last used E-UTRAN PLMN ID | 3.2.2.127 | +| 1001 0110 | Old Location Area Identification | 3.2.2.128 | +| 1001 0111 | Attach Indicator | 3.2.2.129 | +| 1001 1000 | Selected Operator | 3.2.2.130 | +| 1001 1001 | PS Registered Operator | 3.2.2.131 | +| 1001 1010 | CS Registered Operator | 3.2.2.132 | +| 0100 0001 | Reserved (see note 3) | # | +| 0100 0010 | Reserved (see note 3) | # | +| NOTE 1: (void) | | | +| NOTE 2: Information Element codes marked as "reserved" are reserved for use by previous versions of this interface specification. | | | +| NOTE 3: Information Element codes marked as "reserved" are reserved for use by ANSI version of this interface specification. | | | + +### 3.2.2.1 Message Type + +Message Type uniquely identifies the message being sent. It is a single octet element, mandatory in all messages. + +Bit 8 is reserved for future extension of the code set. All unassigned codes are spare. + +| | 8 7 6 5 4 3 2 1 | | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 0 0 0 0 0 0 0 0 | Reserved. | +| ASSIGNMENT MESSAGES | 0 0 0 0 0 0 0 1
0 0 0 0 0 0 1 0
0 0 0 0 0 1 1
0 0 0 0 1 0 0 0 | ASSIGNMENT REQUEST
ASSIGNMENT COMPLETE
ASSIGNMENT FAILURE
CHANNEL MODIFY REQUEST | +| HANDOVER MESSAGES | 0 0 0 1 0 0 0 0
0 0 0 1 0 0 0 1
0 0 0 1 0 0 1 0
0 0 0 1 0 0 1 1
0 0 0 1 0 1 0 0
0 0 0 1 0 1 0 1
0 0 0 1 0 1 1 0
0 0 0 1 0 1 1 1
0 0 0 1 1 0 0 0
0 0 0 1 1 0 0 1
0 0 0 1 1 0 1 0
0 0 0 1 1 0 1 1
0 1 1 1 0 0 0 0
0 1 1 1 0 0 0 1
0 1 1 1 0 0 1 0
0 1 1 1 0 0 1 1 | HANDOVER REQUEST
HANDOVER REQUIRED
HANDOVER REQUEST ACKNOWLEDGE
HANDOVER COMMAND
HANDOVER COMPLETE
HANDOVER SUCCEEDED
HANDOVER FAILURE
HANDOVER PERFORMED
HANDOVER CANDIDATE ENQUIRE
HANDOVER CANDIDATE RESPONSE
HANDOVER REQUIRED REJECT
HANDOVER DETECT
INTERNAL HANDOVER REQUIRED
INTERNAL HANDOVER REQUIRED REJECT
INTERNAL HANDOVER COMMAND
INTERNAL HANDOVER ENQUIRY | +| RELEASE MESSAGES | 0 0 1 0 0 0 0 0
0 0 1 0 0 0 0 1
0 0 1 0 0 0 1 0
0 0 1 0 0 0 1 1
0 0 1 0 0 1 0 0
0 0 1 0 0 1 0 1
0 0 1 0 0 1 1 0 | CLEAR COMMAND
CLEAR COMPLETE
CLEAR REQUEST
RESERVED
RESERVED
SAPI "N" REJECT
CONFUSION | +| OTHER CONNECTION RELATED MESSAGES | 0 0 1 0 1 0 0 0
0 0 1 0 1 0 0 1
0 0 1 0 1 0 1 0
0 0 1 0 1 0 1 1
0 0 1 0 1 1 0 0
0 0 1 0 1 1 0 1
0 0 1 0 1 1 1 0
0 0 1 0 1 1 1 1
0 1 1 1 1 0 0 0
0 1 1 1 1 0 0 1 | SUSPEND
RESUME
Reserved (See note)
PERFORM LOCATION REQUEST
LSA INFORMATION
PERFORM LOCATION RESPONSE
PERFORM LOCATION ABORT
COMMON ID
REROUTE COMMAND
REROUTE COMPLETE | +| GENERAL MESSAGES | 0 0 1 1 0 0 0 0
0 0 1 1 0 0 0 1
0 0 1 1 0 0 1 0
0 0 1 1 0 0 1 1
0 0 1 1 0 1 0 0
0 0 1 1 0 1 0 1
0 0 1 1 0 1 1 0
0 0 1 1 0 1 1 1
0 0 1 1 1 0 1 0
0 0 1 1 1 1 0 1
0 0 1 1 1 1 1 0
0 0 1 1 1 1 1 1
0 0 1 1 1 0 0 0 | RESET
RESET ACKNOWLEDGE
OVERLOAD
RESERVED
RESET CIRCUIT
RESET CIRCUIT ACKNOWLEDGE
MSC INVOKE TRACE
BSS INVOKE TRACE
CONNECTIONLESS INFORMATION
RESET IP RESOURCE
RESET IP RESOURCE ACKNOWLEDGE
MS REGISTRATION ENQUIRY
MS REGISTRATION ENQUIRY RESPONSE | +| TERRESTRIAL RESOURCE MESSAGES | 0 1 0 0 0 0 0 0
0 1 0 0 0 0 0 1
0 1 0 0 0 0 1 0
0 1 0 0 0 0 1 1
0 1 0 0 0 1 0 0
0 1 0 0 0 1 0 1
0 1 0 0 0 1 1 0
0 1 0 0 0 1 1 1 | BLOCK
BLOCKING ACKNOWLEDGE
UNBLOCK
UNBLOCKING ACKNOWLEDGE
CIRCUIT GROUP BLOCK
CIRCUIT GROUP BLOCKING ACKNOWLEDGE
CIRCUIT GROUP UNBLOCK
CIRCUIT GROUP UNBLOCKING | + +| | 8 7 6 5 4 3 2 1 | | +|---------------------------------------------------------------------------------------------------------|------------------------|------------------------------| +| | 0 1 0 0 1 0 0 0 | ACKNOWLEDGE | +| | 0 1 0 0 1 1 1 0 | UNEQUIPPED CIRCUIT | +| | 0 1 0 0 1 1 1 1 | CHANGE CIRCUIT | +| | 0 1 0 0 1 1 1 1 | CHANGE CIRCUIT ACKNOWLEDGE | +| RADIO RESOURCE MESSAGES | | | +| | 0 1 0 1 0 0 0 0 | RESOURCE REQUEST | +| | 0 1 0 1 0 0 0 1 | RESOURCE INDICATION | +| | 0 1 0 1 0 0 1 0 | PAGING | +| | 0 1 0 1 0 0 1 1 | CIPHER MODE COMMAND | +| | 0 1 0 1 0 1 0 0 | CLASSMARK UPDATE | +| | 0 1 0 1 0 1 0 1 | CIPHER MODE COMPLETE | +| | 0 1 0 1 0 1 1 0 | QUEUING INDICATION | +| | 0 1 0 1 0 1 1 1 | COMPLETE LAYER 3 INFORMATION | +| | 0 1 0 1 1 0 0 0 | CLASSMARK REQUEST | +| | 0 1 0 1 1 0 0 1 | CIPHER MODE REJECT | +| | 0 1 0 1 1 0 1 0 | LOAD INDICATION | +| VGCS/VBS | | | +| | 0 0 0 0 0 1 0 0 | VGCS/VBS SETUP | +| | 0 0 0 0 0 1 0 1 | VGCS/VBS SETUP ACK | +| | 0 0 0 0 0 1 1 0 | VGCS/VBS SETUP REFUSE | +| | 0 0 0 0 0 1 1 1 | VGCS/VBS ASSIGNMENT REQUEST | +| | 0 0 0 1 1 1 0 0 | VGCS/VBS ASSIGNMENT RESULT | +| | 0 0 0 1 1 1 0 1 | VGCS/VBS ASSIGNMENT FAILURE | +| | 0 0 0 1 1 1 1 0 | VGCS/VBS QUEUING INDICATION | +| | 0 0 1 1 1 0 1 1 | VGCS/VBS ASSIGNMENT STATUS | +| | 0 0 1 1 1 1 0 0 | VGCS/VBS AREA CELL INFO | +| | 0 0 0 1 1 1 1 1 | UPLINK REQUEST | +| | 0 0 1 0 0 1 1 1 | UPLINK REQUEST ACKNOWLEDGE | +| | 0 1 0 0 1 0 0 1 | UPLINK REQUEST CONFIRMATION | +| | 0 1 0 0 1 0 1 0 | UPLINK RELEASE INDICATION | +| | 0 1 0 0 1 0 1 1 | UPLINK REJECT COMMAND | +| | 0 1 0 0 1 1 0 0 | UPLINK RELEASE COMMAND | +| | 0 1 0 0 1 1 0 1 | UPLINK SEIZED COMMAND | +| | 0 1 1 0 0 0 0 0 | VGCS ADDITIONAL INFORMATION | +| | 0 1 1 0 0 0 0 1 | VGCS SMS | +| | 0 1 1 0 0 0 1 0 | NOTIFICATION DATA | +| | 0 1 1 0 0 0 1 1 | UPLINK APPLICATION DATA | +| LOCAL SWITCHING | | | +| | 0 1 1 1 0 1 0 0 | LCLS-CONNECT-CONTROL | +| | 0 1 1 1 0 1 0 1 | LCLS-CONNECT-CONTROL-ACK | +| | 0 1 1 1 0 1 1 0 | LCLS-NOTIFICATION | +| NOTE: This value was allocated in an earlier phase of the protocol and shall not be used in the future. | | | + +### 3.2.2.2 Circuit Identity Code + +This element defines the terrestrial channel over which the call will pass. + +If a 2 048 kbits/s digital path is used then the circuit identification code contains in the five least significant bits a binary representation of the actual number of the timeslot which is assigned to the circuit. The remaining bits in the CIC are used where necessary to identify one among several systems interconnecting an originating and destination point. + +The element is 2 octets in length: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| a | b | c | d | e | f | g | h | octet 2 | +| i | j | k | X | X | X | X | X | octet 3 | + +a-k defines the PCM multiplex in use. + +XXXXX define the actual timeslot in use. + +The circuit identity code defines the PCM multiplex and timeslot in use at the MSC. In cases where remultiplexing takes place between the MSC and BSS a translation may be necessary at the BSS. + +If a 1544 kbit/s digital path is used, then the format of the circuit identity code (CIC) shall be as shown below: + +The element is 2 octets in length: + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| CIC (least significant bits) | | | | | | | | octet 2 | +| CIC (most significant bits) | | | | | | | | octet 3 | + +### 3.2.2.3 Connection Release Requested + +The element has a fixed length of one octet. + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | + +### 3.2.2.4 Resource Available + +This element gives the number of full and half rate channels available on any given cell at the time of construction of the message. + +It defines these parameters in terms of the number of channels available in five interference bands, the boundaries of these bands being set by O and M as follows: + +Interference level: 0 ----- + +Band 1 + +X1 ----- + +Band 2 + +X2 ----- + +Band 3 + +X3 ----- + +Band 4 + +X4 ----- + +Band 5 + +X5 ----- + +The element is coded as follows: + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Number of full rate | | | | | | | | octet 2 | +| channels available in band 1 | | | | | | | | octet 3 | +| Number of half rate | | | | | | | | octet 4 | +| channels available in band 1 | | | | | | | | octet 5 | +| Number of full rate | | | | | | | | octet 18 | +| channels available in band 5 | | | | | | | | octet 19 | +| Number of half rate | | | | | | | | octet 20 | +| channels available in band 5 | | | | | | | | octet 21 | + +Octets (2, 3, 4, 5) are then repeated for each of the other interference bands giving a total message length of 21 octets. + +Octets 2 and 3 give a 16 bit binary representation of the number of full rate channels available for service but not currently assigned. + +Octets 4 and 5 give a 16 bit binary representation of the number of half rate channels available for service but not currently assigned. This will include half rate channels already counted in octets 2 and 3, if these correspond to full rate channels that can be used as half rate channels. + +(e.g. If there is a spare half rate channel and a spare full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3). + +Octets 3 and 5 are the least significant octets, and bit 1 is the least significant bit. + +### 3.2.2.5 Cause + +The cause element is used to indicate the reason for a particular event to have occurred and is coded as shown below. + +The cause value is a single octet element if the extension bit (bit 8) is set to 0. If it is set to 1 then the cause value is a 2 octet field. If the value of the first octet of the cause field is 1XXX 0000 then the second octet is reserved for national applications (XXX will still indicate the class). + +| | | | | | | | | | +|--------------------|-------------|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| 0/1 ext | Cause Value | | | | | | | octet 3 | +| | | | | | | | | (octet 4) | + +The length indicator is a binary representation of the length of the following element. + +Cause Value: + +| | | +|--------------|-----------------------------------------------------------------------------| +| Class (000): | Normal event | +| Class (001): | Normal event | +| Class (010): | Resource unavailable | +| Class (011): | Service or option not available, but implemented | +| Class (100): | Service or option not implemented or currently disabled, i.e. not supported | +| Class (101): | invalid message (eg parameter out of range) | +| Class (110): | protocol error | +| Class (111): | interworking | + +In the following table, "reserved for international use" means that this codepoint should not be used until a meaning has been assigned to it following the process of international standardisation. "Reserved for national use" indicates codepoints that may be used by operators without the need for international standardization. + +| Cause value | | | | | | | Cause
Number | | | | +|-------------|---|-------|---|---|---|---|-----------------|---------------------------------------------------------|--|--| +| Class | | Value | | | | | | | | | +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | | Radio interface message failure | | | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | | Radio interface failure | | | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | | Uplink quality | | | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | | Uplink strength | | | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | | Downlink quality | | | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | | Downlink strength | | | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | | Distance | | | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | | O and M intervention | | | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | | Response to MSC invocation | | | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | | Call control | | | +| 0 | 0 | 0 | 1 | 0 | 1 | 0 | | Radio interface failure, reversion to old channel | | | +| 0 | 0 | 0 | 1 | 0 | 1 | 1 | | Handover successful | | | +| 0 | 0 | 0 | 1 | 1 | 0 | 0 | | Better Cell | | | +| 0 | 0 | 0 | 1 | 1 | 0 | 1 | | Directed Retry | | | +| 0 | 0 | 0 | 1 | 1 | 1 | 0 | | Joined group call channel | | | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | | Traffic | | | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | | Reduce load in serving cell | | | +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | | Traffic load in target cell higher than in source cell | | | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | | Relocation triggered NOTE | | | +| 0 | 0 | 1 | 0 | 1 | 0 | 0 | | Requested option not authorised | | | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | | Alternative channel configuration requested (NOTE) | | | +| 0 | 0 | 1 | 0 | 1 | 1 | 0 | | Response to an INTERNAL HANDOVER ENQUIRY message | | | +| 0 | 0 | 1 | 0 | 1 | 1 | 1 | | INTERNAL HANDOVER ENQUIRY reject | | | +| 0 | 0 | 1 | 1 | 0 | 0 | 0 | | Redundancy Level not adequate | | | +| 0 | 0 | 1 | 1 | 0 | 0 | 1 | | }
to
} Reserved for national use | | | +| 0 | 0 | 1 | 1 | 1 | 1 | 1 | | }
} | | | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | | Equipment failure | | | +| 0 | 1 | 0 | 0 | 0 | 0 | 1 | | No radio resource available | | | +| 0 | 1 | 0 | 0 | 0 | 1 | 0 | | Requested terrestrial resource unavailable | | | +| 0 | 1 | 0 | 0 | 0 | 1 | 1 | | CCCH overload | | | +| 0 | 1 | 0 | 0 | 1 | 0 | 0 | | Processor overload | | | +| 0 | 1 | 0 | 0 | 1 | 0 | 1 | | BSS not equipped | | | +| 0 | 1 | 0 | 0 | 1 | 1 | 0 | | MS not equipped | | | +| 0 | 1 | 0 | 0 | 1 | 1 | 1 | | Invalid cell | | | +| 0 | 1 | 0 | 1 | 0 | 0 | 0 | | Traffic Load | | | +| 0 | 1 | 0 | 1 | 0 | 0 | 1 | | Preemption | | | +| 0 | 1 | 0 | 1 | 0 | 1 | 0 | | DTM Handover - SGSN Failure | | | +| 0 | 1 | 0 | 1 | 0 | 1 | 1 | | DTM Handover - PS Allocation failure | | | +| 0 | 1 | 0 | 1 | 1 | 0 | 0 | | }
to
} Reserved for national use | | | +| 0 | 1 | 0 | 1 | 1 | 1 | 1 | | }
} | | | +| 0 | 1 | 1 | 0 | 0 | 0 | 0 | | Requested transcoding/rate adaption unavailable | | | +| 0 | 1 | 1 | 0 | 0 | 0 | 1 | | Circuit pool mismatch | | | +| 0 | 1 | 1 | 0 | 0 | 1 | 0 | | Switch circuit pool | | | +| 0 | 1 | 1 | 0 | 0 | 1 | 1 | | Requested speech version unavailable | | | +| 0 | 1 | 1 | 0 | 1 | 0 | 0 | | LSA not allowed | | | +| 0 | 1 | 1 | 0 | 1 | 0 | 1 | | Requested Codec Type or Codec Configuration unavailable | | | +| 0 | 1 | 1 | 0 | 1 | 1 | 0 | | Requested A-Interface Type unavailable | | | +| 0 | 1 | 1 | 0 | 1 | 1 | 1 | | Invalid CSG cell | | | +| 0 | 1 | 1 | 1 | 0 | 0 | 0 | | }
to
} Reserved for international use | | | + +| Cause value | | | | | | | Cause | | +|---------------------------------------------------------------------------|---|---|---|-------|---|---|--------|-----------------------------------------------------------| +| Class | | | | Value | | | Number | | +| 0 | 1 | 1 | 1 | 1 | 1 | 0 | | } | +| 0 | 1 | 1 | 1 | 1 | 1 | 1 | | Requested Redundancy Level not available | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | | Ciphering algorithm not supported | +| 1 | 0 | 0 | 0 | 0 | 0 | 1 | | GERAN Iu-mode failure | +| 1 | 0 | 0 | 0 | 0 | 1 | 0 | | Incoming Relocation Not Supported Due To PUESBINE Feature | +| 1 | 0 | 0 | 0 | 0 | 1 | 1 | | Access Restricted Due to Shared Networks (NOTE) | +| 1 | 0 | 0 | 0 | 1 | 0 | 0 | | Requested Codec Type or Codec Configuration not supported | +| 1 | 0 | 0 | 0 | 1 | 0 | 1 | | Requested A-Interface Type not supported | +| 1 | 0 | 0 | 0 | 1 | 1 | 0 | | Requested Redundancy Level not supported | +| | | | | | | | | | +| 1 | 0 | 0 | 0 | 1 | 1 | 1 | | } Reserved for international use | +| 1 | 0 | 0 | 1 | 0 | 0 | 0 | | }
to
} Reserved for national use | +| 1 | 0 | 0 | 1 | 1 | 1 | 1 | | } | +| 1 | 0 | 1 | 0 | 0 | 0 | 0 | | Terrestrial circuit already allocated | +| 1 | 0 | 1 | 0 | 0 | 0 | 1 | | Invalid message contents | +| 1 | 0 | 1 | 0 | 0 | 1 | 0 | | Information element or field missing | +| 1 | 0 | 1 | 0 | 0 | 1 | 1 | | Incorrect value | +| 1 | 0 | 1 | 0 | 1 | 0 | 0 | | Unknown Message type | +| 1 | 0 | 1 | 0 | 1 | 0 | 1 | | Unknown Information Element | +| 1 | 0 | 1 | 0 | 1 | 1 | 0 | | DTM Handover - Invalid PS Indication | +| 1 | 0 | 1 | 0 | 1 | 1 | 1 | | Call Identifier already allocated | +| | | | | | | | | | +| 1 | 0 | 1 | 1 | 0 | 0 | 0 | | }
to
} Reserved for national use | +| 1 | 0 | 1 | 1 | 1 | 1 | 1 | | } | +| 1 | 1 | 0 | 0 | 0 | 0 | 0 | | Protocol Error between BSS and MSC | +| 1 | 1 | 0 | 0 | 0 | 0 | 1 | | VGCS/VBS call non existent | +| 1 | 1 | 0 | 0 | 0 | 1 | 0 | | DTM Handover - Timer Expiry | +| 1 | 1 | 0 | 0 | 0 | 1 | 1 | | }
to
} Reserved for international use | +| 1 | 1 | 0 | 0 | 1 | 1 | 1 | | } | +| 1 | 1 | 0 | 1 | 0 | 0 | 0 | | }
to
} Reserved for national use | +| 1 | 1 | 0 | 1 | 1 | 1 | 1 | | } | +| 1 | 1 | 1 | 0 | 0 | 0 | 0 | | }
to
} Reserved for international use | +| 1 | 1 | 1 | 0 | 1 | 1 | 1 | | } | +| 1 | 1 | 1 | 1 | 0 | 0 | 0 | | }
to
} Reserved for national use | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | | } | +| NOTE: This cause value is only sent by 3G_MSC-B over the MAP/E interface. | | | | | | | | | + +### 3.2.2.6 IMSI + +This information element identifies the International Mobile Subscriber Identity (see 3GPP TS 23.003). The IMSI is coded as a sequence of BCD digits, compressed two into each octet. This is a variable length element, and includes a length indicator. + +The element coding is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| IMSI coded as the value part of the Mobile Identity IE defined in 3GPP TS 24.008 (NOTE 1) | | | | | | | | octet 3-n | +| NOTE 1: The Type of identity field in the Mobile Identity IE shall be ignored by the receiver. | | | | | | | | | + +### 3.2.2.7 TMSI + +The TMSI is a fixed length element. The TMSI is an unstructured number of 4 octets in length. + +The coding is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| TMSI | | | | | | | | octet 3-6 | + +The TMSI field is unstructured. + +### 3.2.2.8 Number Of MSs + +This is a fixed length element which indicates the number of handover candidates that have been sent to the MSC. + +The coding is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Number of handover candidates | | | | | | | | octet 2 | + +Octet 2 is a binary indication of the number of handover candidates. Bit 1 is the least significant bit. + +### 3.2.2.9 Layer 3 Header Information + +This element is used to supply the BSS with information that needs to be included in the header of layer 3 messages over the radio interface. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Protocol discriminator | | | | | | | | octet 3 | +| Transaction identifier | | | | | | | | octet 4 | + +The length indicator is a binary indication of the number of octets following in the element. + +The transaction identifier and protocol discriminator fields are coded as defined in 3GPP TS 24.008. The protocol discriminator occupies bit 1 to 4 in octet 3 of Layer 3 header information, the Transaction identifier occupies bit 1 to 4 in octet 4 of the Layer 3 header information. + +### 3.2.2.10 Encryption Information + +This element contains the user data encryption information used to control any encryption equipment at the BSS. + +It is a variable length element. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Permitted algorithms | | | | | | | | octet 3 | +| Key | | | | | | | | octet 4-n | + +The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet. + +The permitted algorithms octet is a bit map indicating the A5 encryption algorithms and no encryption. From this bit map the BSS may select an A5 algorithm or no encryption to be used. + +| Bit No | meaning | +|--------|---------------| +| 1 | No encryption | +| 2 | GSM A5/1 | +| 3 | GSM A5/2 | +| 4 | GSM A5/3 | +| 5 | GSM A5/4 | +| 6 | GSM A5/5 | +| 7 | GSM A5/6 | +| 8 | GSM A5/7 | + +A bit position encoded as 1 indicates that the BSS may use the option represented by that bit position. A bit position encoded as 0 indicates that the BSS shall not use the option represented by that bit position. A permitted algorithms octet containing all bits encoded as 0 shall not be used. + +The key shall be present if at least one of the A5/1 or A5/3 encryption algorithms is permitted. Over MAP/E interface to 3G\_MSC-B the key shall be present if available. For VGCS/VBS calls, the key shall not be present unless the Encryption Information is being provided for when a VGCS talker communicates on a dedicated channel. When present, the key shall be 8 octets long. + +### 3.2.2.11 Channel Type + +This element contains all of the information that the BSS requires to determine the required radio resource(s). + +The channel type information element has a minimum length of 5 octets and a maximum length of 13 octets. It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|-------------------------|---|---|---|---------------------------------------------------|--|--|--|--| +| Element identifier | | | | | | | | octet 1 | | | | | +| Length | | | | | | | | octet 2 | | | | | +| Spare | | | | Speech / data indicator | | | | octet 3 | | | | | +| Channel rate and type | | | | | | | | octet 4 | | | | | +| Permitted speech version indication /
data rate + transparency indicator | | | | | | | | octet 5
or
octet 5 with
extension (note) | | | | | +| NOTE: If the speech / data indicator (octet 3) indicates "speech" or "data" or "CTM Text Telephony", octet 5 may optionally be extended.
Otherwise octet 5 shall not be extended. | | | | | | | | | | | | | + +The "speech / data indicator" field is coded as follows: + +| code | meaning | +|------|---------| +| 0001 | Speech | + +| | | +|------|-----------------------------| +| 0010 | Data | +| 0011 | Signalling | +| 0100 | Speech + CTM Text Telephony | + +All other values are reserved. + +For values 0001 and 0010 a dedicated terrestrial resource is also required. For value 0100 a CTM Text Telephony capable terrestrial resource is required. + +The "channel rate and type" is coded as follows: + +If octet 3 indicates data then octet 4 shall be coded as: + +| code | meaning | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 1000 | Full rate TCH channel Bm. | +| 0000 1001 | Half rate TCH channel Lm. | +| 0000 1010 | Full or Half rate TCH channel, Full rate preferred, changes allowed also after first channel allocation as a result of the request. | +| 0000 1011 | Full or Half rate TCH channel, Half rate preferred, changes allowed also after first channel allocation as a result of the request. | +| 0001 1010 | Full or Half rate TCH channel, Full rate preferred, changes not allowed after first channel allocation as a result of the request. | +| 0001 1011 | Full or Half rate TCH channel. Half rate preferred, changes not allowed after first channel allocation as a result of the request. | +| 0010 0xxx | Full rate TCH channels in a multislot configuration, changes by the BSS of the the number of TCHs and if applicable the used radio interface rate per channel allowed after first channel allocation as a result of the request. | +| 0011 0xxx | Full rate TCH channels in a multislot configuration, changes by the BSS of the number of TCHs or the used radio interface rate per channel not allowed after first channel allocation as a result of the request. | + +xxx (bits 3-1) indicates maximum number of traffic channels; + +| | | +|------------|----------------| +| bits | | +| 321 | meaning | +| 000 | 1 TCHs | +| 001 | 2 TCHs | +| 010 | 3 TCHs | +| 011 | 4 TCHs | +| 100 | 5 TCHs | +| 101 | 6 TCHs | +| 110 | 7 TCHs | +| 111 | 8 TCHs | + +All other values are reserved. + +If octet 3 indicates speech or speech + CTM Text Telephony then octet 4 shall be coded as: + +| code | meaning | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 1000 | Full rate TCH channel Bm. Preference between the permitted speech versions for full rate TCH as indicated in octet 5, 5a etc. | +| 0000 1001 | Half rate TCH channel Lm. Preference between the permitted speech versions for half rate TCH as indicated in octet 5, 5a etc. | +| 0000 1010 | Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. | +| 0000 1011 | Full or Half rate TCH channel, Half rate preferred, changes between full rate and half rate allowed also after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. | +| 0001 1010 | Full or Half rate TCH channel, Full rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. | + +- 0001 1011 Full or Half rate TCH channel. Half rate preferred, changes between full rate and half rate not allowed after first channel allocation as a result of the request. Preference between the permitted speech versions for the respective channel rates as indicated in octet 5, 5a etc. +- 0000 1111 Full or Half rate TCH channel. Preference between the permitted speech versions as indicated in octet 5, 5a etc., changes between full and half rate allowed also after first channel allocation as a result of the request. +- 0001 1111 Full or Half rate TCH channel. Preference between the permitted speech versions as indicated in octet 5, 5a etc., changes between full and half rate not allowed after first channel allocation as a result of the request. + +All other values are reserved. + +If octet 3 indicates signalling then octet 4 shall be coded as: + +| code | meaning | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------| +| 0000 0000 | SDCCH or Full rate TCH channel Bm or Half rate TCH channel Lm
0000 0001 SDCCH. | +| 0000 0010 | SDCCH or Full rate TCH channel Bm. | +| 0000 0011 | SDCCH or Half rate TCH channel Lm. | +| 0000 1000 | Full rate TCH channel Bm. | +| 0000 1001 | Half rate TCH channel Lm. | +| 0000 1010 | Full or Half rate TCH channel, Full rate preferred, changes allowed also after first channel allocation as a result of the request. | +| 0000 1011 | Full or Half rate TCH channel, Half rate preferred, changes allowed also after first channel allocation as a result of the request. | +| 0001 1010 | Full or Half rate TCH channel, Full rate preferred, changes not allowed after first channel allocation as a result of the request. | +| 0001 1011 | Full or Half rate TCH channel. Half rate preferred, changes not allowed after first channel allocation as a result of the request. | + +All other values are reserved. + +The "permitted speech version indication / data rate + transparency indicator" octet is coded as follows: + +- If octet 3 indicates speech or speech + CTM Text Telephony then octet 5 shall be coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|---|---|---|---|---|---|---|----------------------------------------------| +| ext | | | | | | | | permitted speech version identifier Octet 5 | +| ext | | | | | | | | permitted speech version identifier Octet 5a | +| ext | | | | | | | | permitted speech version identifier Octet 5b | +| ext | | | | | | | | permitted speech version identifier Octet 5c | +| ext | | | | | | | | permitted speech version identifier Octet 5d | +| ext | | | | | | | | permitted speech version identifier Octet 5e | +| ext | | | | | | | | Permitted speech version identifier Octet 5f | +| ext | | | | | | | | Permitted speech version identifier Octet 5g | +| 0 | | | | | | | | Permitted speech version identifier Octet 5h | + +Bit 8 indicates extension of octet 5. + +0 no extension, i.e. value "0" indicates that this octet is the last octet. + +1 extension, i.e. value "1" indicates that at least one additional octet is included. + +- If more than one permitted speech version is indicated by octet 5 (with extension), then the speech version choice is left to the BSS. + +Bits 7-1 indicate the permitted speech version identifier; + +| bits | meaning | +|-----------------|---------------------------------| +| 765 4321 | | +| 000 0001 | GSM speech full rate version 1. | +| 001 0001 | GSM speech full rate version 2. | +| 010 0001 | GSM speech full rate version 3. | +| 100 0001 | GSM speech full rate version 4. | +| 100 0010 | GSM speech full rate version 5. | + +| | | +|----------|---------------------------------| +| 000 0101 | GSM speech half rate version 1. | +| 001 0101 | GSM speech half rate version 2. | +| 010 0101 | GSM speech half rate version 3. | +| 100 0110 | GSM speech half rate version 4. | +| 100 0101 | GSM speech half rate version 6. | + +The GSM speech versions are also referred as follows (see 3GPP TS 26.103): + +| | | +|---------------------------------|----------------------------------------------| +| GSM speech full rate version 1: | GSM FR. | +| GSM speech full rate version 2: | GSM EFR. | +| GSM speech full rate version 3: | FR AMR. | +| GSM speech full rate version 4: | OFR AMR-WB. | +| GSM speech full rate version 5: | FR AMR-WB. | +| GSM speech half rate version 1: | GSM HR. | +| GSM speech half rate version 2: | not defined in this version of the protocol. | +| GSM speech half rate version 3: | HR AMR. | +| GSM speech half rate version 4: | OHR AMR-WB. | +| GSM speech half rate version 6: | OHR AMR. | + +All other values of permitted speech version identifiers are for future use. If an unknown value is received and more than one octet 5 is received the sender expects the receiver to behave as if it has made a choice of speech version. + +The rules for coding preferences in octet 5, 5a - 5h are the following: + +- In those cases when one specific channel rate is indicated in octet 4, the non-empty set of permitted speech versions is included. Within this set the permitted speech versions are included in order of speech version preferences. +- In those cases when a preference for a channel rate is indicated in octet 4, the non-empty sets of permitted speech versions for the respective channel rate are included in order of the channel rate preferences indicated in octet 4. Within a set of permitted speech versions for a channel rate, the permitted speech versions are included in order of speech version preferences. +- In those cases when no preference or specific channel rate is indicated in octet 4, the permitted speech versions are included in order of speech version preferences. + +Always octet 5 has the highest preference followed by octet 5a and so on. For each channel rate allowed by octet 4 at least one speech version shall be present. + +If octet 5 indicates no extension and bits 7-1 is coded "000 0001", then the preference is interpreted based upon the octet 4 value as follows: + +- in those cases when octet 4 indicates one specific channel rate, then "speech version 1" for the indicated channel rate is permitted; +- in those cases when octet 4 indicates a preference for a channel rate, then "speech version 1" for any of the allowed channel rates is permitted; +- in those cases when octet 4 does neither indicate a preference for a channel rate nor a specific channel rate, then "speech version 1" for any of the allowed channel rates is permitted and speech full rate version 1 is preferred. + +If octet 3 indicates data, and octet 4 does not indicate multislot configuration, then octet 5 shall be coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|-------------------------|-------|---|---|---|---|---|----------| +| ext | T/NT | Rate | | | | | | octet 5 | +| ext | allowed
r i/f rates | | | | | | | octet 5a | +| ext | asymmetry
indication | spare | | | | | | octet 5b | + +Bit 8 indicates extension of octet 5. + +0 no extension, i.e. value "0" indicates that this octet is the last octet. + +1 extension, i.e. value "1" indicates that at least one additional octet is included. + +Bit 7: + +| | | +|---|--------------------------| +| 0 | Transparent service | +| 1 | Non-transparent service. | + +For non-transparent service bits 6-1 indicate the radio interface data rate; + +| 65 4321 | meaning | +|----------------|-----------------------------------------------------------------------------------------------| +| 00 0000 | 12 kbit/s if the channel is a full rate TCH; or
6 kbit/s if the channel is a half rate TCH | +| 11 0100 | 43,5 kbit/s | +| 11 0001 | 29 kbit/s | +| 01 1000 | 14,5 kbit/s | +| 01 0000 | 12 kbits/s | +| 01 0001 | 6 kbits/s | + +If bit 7 in octet 5 indicates non-transparent service and octet 5a is included the 'rate' in octet 5 indicates the wanted air interface data rate and the 'allowed r i/f rates' indicates all possible data rates allowed. + +All other values are reserved. + +For transparent service bits 6-1 indicate the data rate; + +| 65 4321 | meaning | +|----------------|---------------------------------------------------------| +| 11 1010 | 32,0 kbit/s | +| 11 1001 | 28,8 kbit/s | +| 01 1000 | 14,4 kbit/s | +| 01 0000 | 9,6 kbit/s | +| 01 0001 | 4,8 kbit/s | +| 01 0010 | 2,4 kbit/s | +| 01 0011 | 1,2 kbit/s | +| 01 0100 | 600 bit/s | +| 01 0101 | 1 200/75 bit/s (1 200 network-to-MS / 75 MS-to-network) | + +If bit 7 in octet 5 indicates transparent service octet 5 shall not be extended. + +All other values are reserved. + +Octet 5a shall be coded as follows; + +| | | +|-------|-----------------------------------------------------------------| +| Bit 8 | reserved for extension.
A coding of 0 indicates no extension | +|-------|-----------------------------------------------------------------| + +Bits 7 to 1 indicate allowed radio interface data rate, per channel; + +| | | +|--------|----------------------------------------------------------------------------| +| Bit 7: | 0 43,5 kbit/s (TCH/F43.2) not allowed
1 43,5 kbit/s (TCH/F43.2) allowed | +| Bit 6: | 0 32,0 kbit/s (TCH/F32.0) not allowed
1 32,0 kbit/s (TCH/F32.0) allowed | +| Bit 5: | 0 29,0 kbit/s (TCH/F28.8) not allowed
1 29,0 kbit/s (TCH/F28.8) allowed | +| Bit 4: | 0 14,5 kbit/s (TCH/F14.4) not allowed
1 14,5 kbit/s (TCH/F14.4) allowed | +| Bit 3: | Spare | +| Bit 2: | 0 12,0 kbit/s (TCH/F9.6) not allowed
1 12,0 kbit/s (TCH/F9.6) allowed | +| Bit 1: | 0 6,0 kbit/s (TCH/F4.8) not allowed
1 6,0 kbit/s (TCH/F4.8) allowed | + +Octet 5b shall be coded as follows: + +Bit 8 reserved for extension. +A coding of 0 indicates no extension + +Bits 7 and 6 indicate the asymmetry preference: + +Bit 76 +00 Not applicable +10 Downlink biased asymmetry is preferred +01 Uplink biased asymmetry is preferred +11 Spare + +Bits 5 to 1 are spare + +NOTE 1: "Not applicable" means that a symmetric service is preferred. + +If octet 5b is not included, symmetry shall be presumed. + +If octet 3 indicates data and octet 4 indicates Full rate TCH channels in a multislot configuration, octet 5 and 5a shall be coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|----------------------|---|---|---|---|---|---|------------------------------| +| ext | T/NT | | | | | | | Rate octet 5 | +| ext | | | | | | | | allowed r i/f rates octet 5a | +| ext | asymmetry indication | | | | | | | spare octet 5b | + +Octet 5 shall be coded as follows; + +Bit 8: extension bit +0 indicates no extension +1 indicates that at least one additional octet is included + +Bit 7: 0 Transparent service +1 Non-transparent service. + +For non-transparent service bits 6-1 indicates wanted total radio interface data rate: + +| 65 4321 | meaning | +|----------------|---------------------------------------------------------------------------------| +| 01 0110 | 58 / 58 kbit/s (4 x 14,5 kbit/s or 2 x 29,0 kbit/s) | +| 01 0100 | 48,0 / 43,5 / 43,5 kbit/s (4 x 12 kbit/s or 3 x 14,5 kbit/s or 1 x 43,5 kbit/s) | +| 01 0011 | 36,0 / 29,0 / 29,0 kbit/s (3 x 12 kbit/s or 2 x 14,5 kbit/s or 1 x 29,0 kbit/s) | +| 01 0010 | 24,0 / 24,0 (4 x 6 kbit/s or 2 x 12 kbit/s) | +| 01 0001 | 18,0 / 14,5 kbit/s (3 x 6 kbit/s or 1 x 14,5 kbit/s) | +| 01 0000 | 12,0 / 12,0 kbit/s (2 x 6 kbit/s or 1 x 12 kbit/s) | + +All other values are reserved. + +For transparent service bits 6-1 indicates requested air interface user rate: + +| 65 4321 | meaning | +|----------------|----------------------------| +| 01 1111 | 64 kbit/s, bit transparent | +| 01 1110 | 56 kbit/s, bit transparent | +| 01 1101 | 56 kbit/s | +| 01 1100 | 48 kbit/s | +| 01 1011 | 38,4 kbit/s | +| 01 0001 | 32 kbit/s | +| 01 1010 | 28,8 kbit/s | +| 01 1001 | 19,2 kbit/s | +| 01 1000 | 14,4 kbit/s | +| 01 0000 | 9,6 kbit/s | + +All other values are reserved. + +Octet 5a shall be coded as follows: + +Bit 8 reserved for extension. +A coding of 0 indicates no extension + +Bits 7 to 1: indicates allowed radio interface data rate, per channel: + +Bit 7:     0  43,5 kbit/s (TCH/F43.2) not allowed +           1  43,5 kbit/s (TCH/F43.2) allowed + +Bit 6:     0  32,0 kbit/s (TCH/F32.0) not allowed +           1  32,0 kbit/s (TCH/F32.0) allowed + +Bit 5:     0  29,0 kbit/s (TCH/F28.8) not allowed +           1  29,0 kbit/s (TCH/F28.8) allowed + +Bit 4:     0  14,5/14,4 kbit/s (TCH/F14.4) not allowed +           1  14,5/14,4 kbit/s (TCH/F14.4) allowed + +Bit 3:     Spare + +Bit 2:     0  12,0/9,6 kbit/s (TCH F/9.6) not allowed +           1  12,0/9,6 kbit/s (TCH F/9.6) allowed + +Bit 1:     0  6,0/4,8 kbit/s (TCH F/4.8) not allowed +           1  6,0/4,8 kbit/s (TCH F/4.8) allowed + +If octet 5a is not included, allowance of radio interface data rates of 12.0 and 6.0 shall be presumed. + +NOTE 2: For data services, the information in the channel type Information Element is used to set the "E-bits" and map the "D-bits" (as described in 3GPP TS 44.002 and 3GPP TS 48.020) and to select the correct channel coding. + +NOTE 3: 43,5 kbit/s is used only for nontransparent services. + +NOTE 4: If octet 5 bits 6-1 indicates requested air interface user rate but octet 5a indicates no allowed radio interface data rate in multislot configuration, then the service requested by the subscriber cannot, due to limitations of the mobile station or the network it is attached to, be provided in GSM, but by another RAT. + +Octet 5b is coded as follows: + +Bit 8 reserved for extension. +A coding of 0 indicates no extension + +Bits 7 and 6 indicate the asymmetry preference: + +| | | +|------------|----------------------------------------| +| Bit | | +| 7 6 | meaning | +| 0 0 | Not applicable | +| 1 0 | Downlink biased asymmetry is preferred | +| 0 1 | Uplink biased asymmetry is preferred | +| 1 1 | Spare | + +Bits 5 to 1 are spare + +NOTE 5: "Not applicable" means that a symmetric service is preferred. + +If octet 5b is not included, symmetry shall be presumed. + +If octet 3 indicates signalling then octet 5 is spare. + +### 3.2.2.12 Periodicity + +This element defines the periodicity of a particular procedure. It is fixed length, 2 octets. + +The coding is as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Periodicity | | | | | | | | octet 2 | + +When the Resource Indication Method IE is set to either "method i) of sub-clause 3.1.3.1" or "method iii) of sub-clause 3.1.3.1" and the periodicity parameter is not 0000 0000 then the coding of the periodicity parameter is: + +| | | +|-----------|--------| +| 0000 0001 | Period | +| 1111 1111 | - | + +where the period is the binary value of octet 2 x 100 ms (ie 100 ms to 25,500 ms). + +When the Resource Indication Method IE is set to "method i) of sub-clause 3.1.3.1" and the periodicity parameter is 0000 0000 then the BSS shall ignore this IE. + +When the Resource Indication Method IE is set to "method iii) of sub-clause 3.1.3.1" and the periodicity parameter is 0000 0000 then the BSS shall treat the message according to sub-clause 3.1.19.4, case 2. + +When the Resource Indication Method IE is set to either "method ii) of sub-clause 3.1.3.1" or "method iv) of sub-clause 3.1.3.1" then the Periodicity IE shall be ignored. + +### 3.2.2.13 Extended Resource Indicator + +This element defines which additional resource information related to a given cell the BSS shall transfer to the MSC. It may also indicate the subsequent reporting mode for that cell. + +The coding is as follows: + +| | | | | | | | | | | | +|--------------------------------------------|---|---|---|----|------|---|---|---------|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +| Element identifier | | | | | | | | octet 1 | | | +| spare | | | | SM | TARR | | | octet 2 | | | +| SM: Subsequent mode. | | | | | | | | | | | +| TARR: Total Accessible Resource Requested. | | | | | | | | | | | + +The coding of the Total Accessible Resource Requested field is as follows: + +- 0 No extra Resource Information is requested. +- 1 The total number of accessible channels is requested. + +If the Resource Indication Method is not set to "method ii) of sub-clause 3.1.3.1" then the Subsequent Mode field is ignored. + +If the Resource Indication Method is set to "method ii) of sub-clause 3.1.3.1" then the Subsequent Mode field is decoded as follows: + +- 0 method iv) of sub-clause 3.1.3.1. +- 1 if the reporting mode prior to receipt of this IE was i) or iii) of sub-clause 3.1.3.1 then the subsequent mode shall be respectively i) or iii); otherwise the subsequent mode shall be method iv) of sub-clause 3.1.3.1. + +### 3.2.2.14 Total Resource Accessible + +This element gives the total number of full and half rate channels accessible on any given cell at the time of construction of the message. + +It defines these parameters in terms of the number of channels which are accessible or in use. No separation between the defined interference bands is made. + +The element is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------|---|---|---|---|---|---|---|--------------------| +| Element identifier | | | | | | | | octet 1 | +| Total number of accessible full rate channels | | | | | | | | octet 2
octet 3 | +| Total number of accessible half rate channels | | | | | | | | octet 4
octet 5 | + +Octets 2 and 3 give a 16 bit binary representation of the total number of full rate channels accessible (i.e. available for service or currently assigned). + +Octets 4 and 5 give a 16 bit binary representation of the number of half rate channels accessible (i.e. available for service or currently assigned). This will include half rate channels already counted in octets 2 and 3, if these correspond to full rate channels that can be used as half rate channels. + +(eg. If there is an accessible half rate channel and an accessible full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3). + +Octets 3 and 5 are the least significant octets, and bit 1 is the least significant bit. + +### 3.2.2.15 LSA Identifier + +This element uniquely identifies a LSA and is of fixed length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| LSA ID | | | | | | | | octet 3 | +| LSA ID cont. | | | | | | | | octet 4 | +| LSA ID cont. | | | | | | | | octet 5 | + +The octets 3-5 are coded as specified in 3GPP TS 23.003, 'Identification of Localised Service Area'. Bit 8 of octet 3 is the MSB. + +### 3.2.2.16 LSA Identifier List + +This element uniquely identifies LSAs and is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +|----------------------|---|---|---|---|---|----|---|------------|--|--| +| Element identifier | | | | | | | | octet 1 | | | +| Length | | | | | | | | octet 2 | | | +| Spare | | | | | | EP | | octet 3 | | | +| LSA identification 1 | | | | | | | | octet 4-6 | | | +| LSA identification n | | | | | | | | .. to 3+3n | | | + +The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the number of LSAs to be identified. If the escape PLMN (see 3GPP TS 43.073) is broadcast the EP bit (bit 1 of octet 3) is set to 1, otherwise it is set to 0. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------|---|---|---|---|---|---|---|-----------| +| LSA ID | | | | | | | | octet x+1 | +| LSA ID cont. | | | | | | | | octet x+2 | +| LSA ID cont. | | | | | | | | octet x+3 | + +Where $x = 3 + 3(i-1)$ + +The octets (x+1)-(x+3) are coded as shown in 3GPP TS 23.003, 'Identification of Localised Service Area'. Bit 8 of octet (x+1) is the MSB. + +### 3.2.2.17 Cell Identifier + +This element uniquely identifies a cell within a BSS and is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|-----------------------------------|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | | Cell identification discriminator | | | | octet 3 | +| Cell identification | | | | | | | | octet 4-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the Cell identification discriminator (octet 3). + +The coding of "Cell identification discriminator" (bits 1 to 4 of octet 3) is a binary number indicating if the whole or a part of Cell Global Identification, CGI, according to 3GPP TS 23.003 is used for cell identification in octet 4-n. The "Cell identification discriminator" is coded as follows: + +| | | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cell. | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell. | +| 0010 | Cell Identity, CI, is used to identify the cell. | +| 0011 | No cell is associated with the transaction. | +| 1000 | Intersystem Handover to UTRAN or cdma2000 or E-UTRAN (CS to PS SRVCC to E-UTRAN). PLMN-ID, LAC (or TAC) and RNC-ID (or Extended RNC-ID or Corresponding RNC-ID), is used to identify the target RNC or the target eNB. | +| 1001 | Intersystem Handover to UTRAN or cdma2000 or E-UTRAN (CS to PS SRVCC to E-UTRAN). The RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) is used to identify the target RNC or the target eNB. | +| 1010 | Intersystem Handover to UTRAN or cdma2000 or E-UTRAN (CS to PS SRVCC to E-UTRAN). LAC (or TAC) and RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) are used to identify the target RNC or the target eNB. | +| 1011 | Serving Area Identity, SAI, is used to identify the Serving Area of UE within UTRAN or cdma2000 or to indicate an E-UTRAN source. | +| 1100 | LAC, RNC-ID (or Extended RNC-ID) and Cell Identity, CI, is used to identify a UTRAN cell for cell load information. | + +All other values are reserved. + +The coding of octet 4-n depends on the Cell identification discriminator (octet 3). Below the coding is shown for each Cell identification discriminator: + +NOTE: no coding is specified for a Cell identification discriminator value of "0011" as no additional information is required. + +**Coding of Cell Identification for Cell identification discriminator = 0000** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|---------------|---|---|---|-----------|---|---|---|----------|--|--|--|--| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 4 | | | | | +| MNC dig 3 | | | | MNC dig 3 | | | | octet 5 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 6 | | | | | +| LAC | | | | | | | | octet 7 | | | | | +| LAC cont. | | | | | | | | octet 8 | | | | | +| CI value | | | | | | | | octet 9 | | | | | +| CI value cont | | | | | | | | octet 10 | | | | | + +The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used. + +The octets 9-10 are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +**Coding of Cell Identification for Cell identification discriminator = 0001** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|---------| +| LAC | | | | | | | | octet 4 | +| LAC cont. | | | | | | | | octet 5 | +| CI value | | | | | | | | octet 6 | +| CI value cont | | | | | | | | octet 7 | + +Coding of Cell Identification for Cell identification discriminator = 0010 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|---------| +| CI value | | | | | | | | octet 4 | +| CI value cont | | | | | | | | octet 5 | + +The octets 4-5 are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element' + +#### Coding of Cell Identification for Cell identification discriminator = 1000 + +For intersystem handover from GSM to UMTS or to cdma2000 or to UTRAN (CS to PS SRVCC to UTRAN) or to E-UTRAN (CS to PS SRVCC to E-UTRAN): + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----------------------------------------------------------|---|---|---|-----------|---|---|---|----------|--|--|--|--| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 4 | | | | | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 5 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 6 | | | | | +| LAC (or TAC) | | | | | | | | octet 7 | | | | | +| LAC (or TAC) cont. | | | | | | | | octet 8 | | | | | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) | | | | | | | | octet 9 | | | | | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) cont. | | | | | | | | octet 10 | | | | | + +The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element' in case of intersystem handover from GSM to cdma2000 or to UTRAN. In case of intersystem handover from GSM to E-UTRAN (CS to PS SRVCC to E-UTRAN) the coding is done as shown in 3GPP TS 24.301, Table 'Tracking Area Identity information element'. + +The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used. + +The octets 9-10 are coded as the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) or the Corresponding RNC-ID (0..4095) specified in 3GPP TS 25.413 [31]: + +- The least significant bit of RNC-ID or Corresponding RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 4. In the octet 9 bits 5-8 are filled by '0000'. +- The least significant bit of Extended RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 8. + +#### Coding of Cell Identification for Cell identification discriminator = 1001 + +For intersystem handover from GSM to UMTS or to cdma2000 or to UTRAN (CS to PS SRVCC to UTRAN) or to E-UTRAN (CS to PS SRVCC to E-UTRAN): + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---|---|---|---|---|---|---------| +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) | | | | | | | | octet 4 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) cont. | | | | | | | | octet 5 | + +The octets 4-5 are coded as the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) or Corresponding RNC-ID (0..4095) specified in 3GPP TS 25.413 [31]: + +- The least significant bit of RNC-ID or Corresponding RNC-ID is octet 5 bit 1 and most significant bit is octet 4 bit 4. In the octet 4 bits 5-8 are filled by '0000'. +- The least significant bit of Extended RNC-ID is octet 5 bit 1 and most significant bit is octet 4 bit 8. + +#### Coding of Cell Identification for Cell identification discriminator = 1010 + +For intersystem handover from GSM to UMTS or to cdma2000 or to UTRAN (CS to PS SRVCC to UTRAN) or to E-UTRAN (CS to PS SRVCC to E-UTRAN): + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---|---|---|---|---|---|---------| +| LAC (or TAC) | | | | | | | | octet 4 | +| LAC (or TAC) cont. | | | | | | | | octet 5 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) | | | | | | | | octet 6 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) cont. | | | | | | | | octet 7 | + +The octets 4-5 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element' in case of intersystem handover from GSM to cdma2000 or to UTRAN. In case of intersystem handover from GSM to E-UTRAN (CS to PS SRVCC to E-UTRAN) the coding is done as shown in 3GPP TS 24.301, Table 'Tracking Area Identity information element'. + +The octets 6-7 are coded as the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) or Corresponding RNC-ID (0..4095) specified in 3GPP TS 25.413 [31]: + +- The least significant bit of RNC-ID or Corresponding RNC-ID is octet 7 bit 1 and most significant bit is octet 6 bit 4. In the octet 6 bits 5-8 are filled by '0000'. +- The least significant bit of Extended RNC-ID is octet 7 bit 1 and most significant bit is octet 6 bit 8. + +#### Coding of Cell Identification for Cell identification discriminator = 1011 + +The coding of SAI is defined in 3GPP TS 25.413, without the protocol extension container. + +NOTE: A default value of SAI can be defined in the MSC Server enhanced for SRVCC to be used as identifier of an E-UTRAN source in case of SRVCC. + +#### Coding of Cell Identification for Cell identification discriminator = 1100 + +For identification of a UTRAN cell for cell load information: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----------------------------------|---|---|---|-----------|---|---|---|----------|--|--|--|--| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 4 | | | | | +| MNC dig 3 | | | | MNC dig 3 | | | | octet 5 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 6 | | | | | +| LAC | | | | | | | | octet 7 | | | | | +| LAC cont. | | | | | | | | octet 8 | | | | | +| RNC-ID (or Extended RNC-ID) | | | | | | | | octet 9 | | | | | +| RNC-ID (or Extended RNC-ID) cont. | | | | | | | | octet 10 | | | | | +| CI value | | | | | | | | octet 11 | | | | | +| CI value cont | | | | | | | | octet 12 | | | | | + +The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used. + +The octets 9-10 are coded as the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) specified in 3GPP TS 25.413 [31]: + +- The least significant bit of RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 4. In the octet 9 bits 5-8 are filled by '0000'. +- The least significant bit of Extended RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 8. + +The octets 11-12 are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +### 3.2.2.18 Priority + +This element indicates the priority of the request. It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Priority | | | | | | | | octet 3 | + +Octet 2 is a binary indication of the length of the rest of the element. + +Octet 3 is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 3 | +|-------|-----|----------------|---|---|---|----|-----|---------| +| spare | pci | priority level | | | | qa | pvi | | + +Bit 8 is spare, set to 0 + +pci = Preemption Capability indicator (see note) + +| | | +|---|-------------------------------------------------------------------| +| 0 | this allocation request shall not preempt an existing connection. | +| 1 | this allocation request may preempt an existing connection. | + +priority level: + +| | | +|---------|--------------------------------------------| +| 6 5 4 3 | | +| 0 0 0 0 | spare | +| 0 0 0 1 | priority level 1 = highest priority | +| 0 0 1 0 | priority level 2 = second highest priority | +| ⋮ ⋮ ⋮ | | +| 1 1 1 0 | priority level 14 = lowest priority | +| 1 1 1 1 | priority not used | + +qa = queuing allowed indicator + +| | | +|---|---------------------| +| 0 | queuing not allowed | +| 1 | queuing allowed | + +pvi = Preemption Vulnerability indicator (see note) + +| | | +|---|----------------------------------------------------------------------| +| 0 | this connection shall not be preempted by another allocation request | +| 1 | this connection might be preempted by another allocation request | + +NOTE: Preemption Capability indicator applies to the allocation of resources for an event and as such it provides the trigger to the preemption procedures/processes of the BSS. Preemption Vulnerability indicator applies for the entire duration of a connection and as such indicates whether the connection is a target of the preemption procedures/processes of the BSS. + +### 3.2.2.19 Classmark Information Type 2 + +The classmark information type 2 defines certain attributes of the mobile station equipment in use on a particular transaction. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1
octet 2
octet 3-5 | | +|--------------------|---|---|---|---|---|---|---|---------------------------------|--| +| Element identifier | | | | | | | | | | +| Length | | | | | | | | | | +| Classmark | | | | | | | | | | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. The length shall be determined by the length of the Mobile Station Classmark 2 element of 3GPP TS 24.008. + +The classmark octets 3, 4 and 5 are coded in the same way as the equivalent octets in the Mobile station classmark 2 element of 3GPP TS 24.008. + +### 3.2.2.20 Classmark Information Type 3 + +The classmark information type 3 defines certain attributes of the mobile station equipment in use on a particular transaction. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Classmark | | | | | | | | octet 3-34 | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. The length octet has a minimum value of 1 and a maximum of 32. The length shall be determined by the length of the Mobile Station Classmark 3 element of 3GPP TS 24.008. + +The classmark octets 3 to 34 are coded in the same way as the equivalent octets in the Mobile station classmark 3 element of 3GPP TS 24.008. + +### 3.2.2.21 Interference Band To Be Used + +This fixed length element is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Band to be used | | | | | | | | octet 2 | + +Octet 2 is coded as: + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------|--| +| Bits 876 | Spare | | +| Bits 54321 | A bit map indicating which interference bands are acceptable, the LSB represents the least level of interference. | | + +### 3.2.2.22 RR Cause + +This fixed length element is passed from the radio interface to the MSC transparently, when received in a 3GPP TS 24.008 message. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| RR cause | | | | | | | | octet 2 | + +Octet 2 is coded as the equivalent field from 3GPP TS 24.008. + +### 3.2.2.23 LSA Information + +This element uniquely identifies LSAs, the priority, the preferential access indicator and the active mode support indicator of each LSA. The access right outside these LSAs is also defined. The element is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +|-------------------------------------|---|---|---|---|---|----------|---|------------|--|--| +| Element identifier | | | | | | | | octet 1 | | | +| Length | | | | | | | | octet 2 | | | +| Spare | | | | | | LSA only | | octet 3 | | | +| LSA identification and attributes 1 | | | | | | | | octet 4-7 | | | +| LSA identification and attributes n | | | | | | | | .. to 3+4n | | | + +The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the number of LSAs to be identified. + +If the LSA only access indicator (bit 1 of octet 3) is set to 1 the subscriber has only access to the LSAs that are defined by the LSA Information element. The LSA only access indicator is set to 0 for allowing an emergency call. + +Coding of the i-th LSA identification with attributes: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------|---|-----|------|----------|---|---|---|-----------| +| spare | | act | pref | priority | | | | octet x+1 | +| LSA ID | | | | | | | | octet x+2 | +| LSA ID cont. | | | | | | | | octet x+3 | +| LSA ID cont. | | | | | | | | octet x+4 | + +Where $x = 3 + 4(i-1)$ + +Bits 1 to 4 of octet (x+1) define the priority of the LSA identification. + +Bit 4321 + +0000 priority 1 = lowest priority + 0001 priority 2 = second lowest priority + : : : : + 1111 priority 16= highest priority + +If the preferential access indicator (bit 5 of octet (x+1)) is set to 1 the subscriber has preferential access in the LSA. If the active mode support indicator (bit 6 of octet (x+1)) is set to 1 the subscriber has active mode support in the LSA. + +The octets (x+2)-(x+4) are coded as specified in 3GPP TS 23.003, 'Identification of Localised Service Area'. Bit 8 of octet (x+2) is the MSB. + +### 3.2.2.24 Layer 3 Information + +This is a variable length element used to pass radio interface messages from one network entity to another. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Layer 3 information | | | | | | | | octet 3-n | + +Octet 1 identifies the element. Octet 2 gives the length of the following layer 3 information. + +Octet j ( $j = 3, 4, \dots, n$ ) is the unchanged octet j-2 of either: + +- a radio interface layer 3 message as defined in 3GPP TS 44.018; or +- Handover To UTRAN Command as defined in 3GPP TS 25.331, where n-2 is equal to the length of that radio interface layer 3 message; or +- a complete RRCConnectionReconfiguration radio interface message as defined in 3GPP TS 36.331, where n-2 is equal to the length of that radio interface layer 3 message. + +### 3.2.2.25 DLCI + +This is a fixed length element indicating the radio interface SAPI. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| DLCI | | | | | | | | octet 2 | + +Octet 2 is coded as the DLCI octet described in 3GPP TS 48.006. + +### 3.2.2.26 Downlink DTX Flag + +A fixed length element indicating whether the DTX function in the BSS is to be disabled on a particular radio channel. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Downlink DTX flag | | | | | | | | octet 2 | + +The Downlink DTX Flag is coded as follows: + +- bits 8 to 2 are spare; +- bit 1 is set to one if the MSC forbids the BSS to activate DTX in the downlink direction; it is set to 0 otherwise. + +In case of compressed speech over RTP/UDP/IP or TFO on the A-Interface the Downlink DTX flag shall be neglected by the BSS. Independent of the Downlink DTX flag the speech payload stream may contain SID frames, indicating the start of a silence period and (not contain) missing RTP frames during the silence period, i.e. DTX may be active in downlink. The BSS shall be able to cope with that. The BSS may treat these calls as if DTX in downlink is activated. + +### 3.2.2.27 Cell Identifier List + +This element uniquely identifies cells and is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|-----------------------------------|---|---|---|-------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | | Cell identification discriminator | | | | octet 3 | +| Cell identification 1 | | | | | | | | octet 4-3+m | +| Cell identification n | | | | | | | | .. to 3+nm | + +The coding of octet 2 is a binary number indicating the Length of the remaining element. The Length depends on the Cell identification discriminator (bits 1 to 4 of octet 3) as well as the number of cells to be identified. + +The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to 3GPP TS 23.003 is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: + +- | | | +|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cells. | +| 0001 | Location Area Code, LAC, and Cell Identify, CI, is used to identify the cells. | +| 0010 | Cell Identity, CI, is used to identify the cells. | +| 0011 | No cell is associated with the transaction. | +| 0100 | Location Area Identification, LAI, is used to identify all cells within a Location Area. | +| 0101 | Location Area Code, LAC, is used to identify all cells within a location area. | +| 0110 | All cells on the BSS are identified. | +| 1000 | Intersystem Handover to UTRAN or cdma2000 or E-UTRAN (CS to PS SRVCC to E-UTRAN). PLMN-ID, LAC (or TAC), and RNC-ID (or Extended RNC-ID or Corresponding RNC-ID), are encoded to identify the target RNC or the target eNB. | +| 1001 | Intersystem Handover to UTRAN or cdma2000 or E-UTRAN (CS to PS SRVCC to E-UTRAN). The RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) is coded to identify the target RNC or the target eNB. | +| 1010 | Intersystem Handover to UTRAN or cdma2000 or E-UTRAN (CS to PS SRVCC to E-UTRAN). LAC (or TAC) and RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) are encoded to identify the target RNC or the target eNB. | + +All other values are reserved. + +Values 0100, 0101 and 0110 are only applicable for page message. + +The coding of the Cell Identifications 1 to n (octets 4 to 4+nm) depends on the Cell identification discriminator (octet 3). Below the coding of the i-th Cell Identification is shown for each Cell identification discriminator (with "i" in the range 1 to n): + +NOTE: No coding is specified for Cell identification discriminator values of "0011" and "0110" as no additional information is required. + +**Coding of the i-th Cell Identification for Cell identification discriminator = 0000** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|-----------|---|---|---|-----------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet x+2 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | +| LAC | | | | | | | | octet x+4 | +| LAC cont. | | | | | | | | octet x+5 | +| CI value | | | | | | | | octet x+6 | +| CI value cont | | | | | | | | octet x+7 | + +Where $x = 3 + 7(i-1)$ . + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+6)-(x+7) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +**Coding of i-th Cell Identification for Cell identification discriminator = 0001** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | +| CI value | | | | | | | | octet x+3 | +| CI value cont | | | | | | | | octet x+4 | + +Where $x = 3 + 4(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+3)-(x+4) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +**Coding of i-th Cell Identification for Cell identification discriminator = 0010** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|-----------| +| CI value | | | | | | | | octet x+1 | +| CI value cont | | | | | | | | octet x+2 | + +Where $x = 3 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +**Coding of i-th Cell Identification for Cell identification discriminator = 0100** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------|---|---|---|-----------|---|---|---|-----------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet x+2 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | +| LAC | | | | | | | | octet x+4 | +| LAC cont. | | | | | | | | octet x+5 | + +Where $x = 3 + 5(i-1)$ + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +**Coding of i-th Cell Identification for Cell identification discriminator = 0101** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | + +Where $x = 3 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The appropriate coding for not identified cells is "0" for all bits of LAC and CI for all possible Cell Identification Discriminator values. + +#### Coding of the Target ID for Cell identification discriminator = 1000 + +For intersystem handover from GSM to UMTS or to cdma2000 or to UTRAN (CS to PS SRVCC to UTRAN) or to E-UTRAN (CS to PS SRVCC to E-UTRAN): + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---|---|-----------|---|---|---|----------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 4 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 5 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 6 | +| LAC (or TAC) | | | | | | | | octet 7 | +| LAC (or TAC) cont. | | | | | | | | octet 8 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) | | | | | | | | octet 9 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) cont. | | | | | | | | octet 10 | + +The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element' in case of intersystem handover from GSM to cdma2000 or to UTRAN. In case of intersystem handover from GSM to E-UTRAN (CS to PS SRVCC to E-UTRAN) the coding is done as shown in 3GPP TS 24.301, Table 'Tracking Area Identity information element'. + +The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used. + +The octets 9-10 are coded as the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) or the Corresponding RNC-ID (0..4095) specified in 3GPP TS 25.413 [31]: + +- The least significant bit of RNC-ID or the Corresponding RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 4. In the octet 9 bits 5-8 are filled by '0000'. +- The least significant bit of Extended RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 8. + +#### Coding of the Target ID for Cell identification discriminator = 1001 + +For intersystem handover from GSM to UMTS or to cdma2000 or to UTRAN (CS to PS SRVCC to UTRAN) or to E-UTRAN (CS to PS SRVCC to E-UTRAN): + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---|---|---|---|---|---|---------| +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) | | | | | | | | octet 4 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) cont. | | | | | | | | octet 5 | + +The octets 4-5 are coded as the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) or the Corresponding RNC-ID (0..4095) specified in 3GPP TS 25.413 [31]: + +- The least significant bit of RNC-ID or the Corresponding RNC-ID is octet 5 bit 1 and most significant bit is octet 4 bit 4. In the octet 4 bits 5-8 are filled by '0000'. +- The least significant bit of Extended RNC-ID is octet 5 bit 1 and most significant bit is octet 4 bit 8. + +#### Coding of the Target ID for Cell identification discriminator = 1010 + +For intersystem handover from GSM to UMTS or to cdma2000 or to UTRAN (CS to PS SRVCC to UTRAN) or to E-UTRAN (CS to PS SRVCC to E-UTRAN): + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------|---|---|---|---|---|---|---|---------| +| LAC (or TAC) | | | | | | | | octet 4 | +| LAC (or TAC) cont. | | | | | | | | octet 5 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) | | | | | | | | octet 6 | +| RNC-ID (or Extended RNC-ID or Corresponding RNC-ID) cont. | | | | | | | | octet 7 | + +The octets 4-5 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element' in case of intersystem handover from GSM to cdma2000 or to UTRAN. In case of intersystem handover from GSM to E-UTRAN (CS to PS SRVCC to E-UTRAN) the coding is done as shown in 3GPP TS 24.301, Table 'Tracking Area Identity information element'. + +The octets 6-7 are coded as the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) or Corresponding RNC-ID (0..4095) specified in 3GPP TS 25.413 [31]: + +- The least significant bit of RNC-ID or the Corresponding RNC-ID is octet 7 bit 1 and most significant bit is octet 6 bit 4. In the octet 6 bits 5-8 are filled by '0000'. +- The least significant bit of Extended RNC-ID is octet 7 bit 1 and most significant bit is octet 6 bit 8. + +### 3.2.2.27a Cell Identifier List Segment + +In the VGCS/VBS Assignment procedure, the entire list of cells in the group call area is communicated to the BSS in one VGCS/VBS ASSIGNMENT REQUEST message and a sequence of (N) VGCS/VBS AREA CELL INFO messages (each message containing one CELL Identifier List Segment IE). The CELL Identifier List Segment IE is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | +|-----------------------|---|---|-----------------------------------|---|---|---|---|------------|--|--|--|--|--| +| Element identifier | | | | | | | | octet 1 | | | | | | +| Length | | | | | | | | octet 2 | | | | | | +| Sequence Length | | | Sequence Number | | | | | octet 3 | | | | | | +| Spare | | | Cell identification discriminator | | | | | octet 4 | | | | | | +| Cell identification 1 | | | | | | | | octet 5 | | | | | | +| ... | | | | | | | | to | | | | | | +| Cell identification n | | | | | | | | octet 4+nm | | | | | | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. + +Octet 3 bits 1-4 represent the sequence number (i), 0 being the sequence number of the segment carried in the VGCS/VBS ASSIGNMENT REQUEST message, 1 to N the sequence numbers of the segments carried in the following VGCS/VBS AREA CELL INFO messages. + +Octet 3 bits 5-8 represent the Sequence Number (N) of the last segment to be sent. + +Octet 4 bits 1-4, contains the Cell Identification Discriminator that is used for the cell identifiers in this Cell Identifier List Segment. The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to 3GPP TS 23.003 is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: + +| | | +|------|----------------------------------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cells | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, is used to identify the cells within a given MCC and MNC | +| 0010 | Cell Identity, CI, is used to identify the cells within a given MCC and MNC and LAC | +| 0011 | No cell is associated with the transaction | +| 0100 | Location Area Identification, LAI, is used to identify all cells within a Location Area | +| 0101 | Location Area Code, LAC, is used to identify all cells within a location area | +| 0110 | All cells on the BSS are identified | +| 0111 | MCC and MNC, is used to identify all cells within the given MCC and MNC | + +All other values are reserved. + +Octet 5-4+nm contains the Cell Identification List. The coding of the Cell Identification List depends on the Cell identification discriminator (octet 4). Below is the coding of the Cell Identification List and the *i*-th Cell Identification is shown for each Cell identification discriminator (with "*i*" in the range 1 to n): + +NOTE: No coding is specified for Cell identification discriminator values of "0011" and "0110" as no additional information is required. + +Coding of the Cell Identification List for Cell identification discriminator = 0000 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|---|---|---|---|------------| +| Cell identification 1 | | | | | | | | octet 5 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 4+7n | + +Coding of the *i*-th Cell Identification for Cell identification discriminator = 0000 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|-----------|---|---|---|-----------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet x+2 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | +| LAC | | | | | | | | octet x+4 | +| LAC cont. | | | | | | | | octet x+5 | +| CI value | | | | | | | | octet x+6 | +| CI value cont | | | | | | | | octet x+7 | + +Where $x = 4 + 7(i-1)$ . + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+6)-(x+7) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +Coding of the Cell Identification List for Cell identification discriminator = 0001 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|-----------|---|---|---|------------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 5 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 6 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 7 | +| Cell identification 1 | | | | | | | | octet 8 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 7+4n | + +Coding of *i*-th Cell Identification for Cell identification discriminator = 0001 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | +| CI value | | | | | | | | octet x+3 | +| CI value cont | | | | | | | | octet x+4 | + +Where $x = 7 + 4(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+3)-(x+4) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +Coding of the Cell Identification List for Cell identification discriminator = 0010 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----------------------|---|---|---|-----------|---|---|---|------------|--|--|--|--| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 5 | | | | | +| MNC dig 3 | | | | MNC dig 3 | | | | octet 6 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 7 | | | | | +| LAC | | | | | | | | octet 8 | | | | | +| LAC cont | | | | | | | | octet 9 | | | | | +| Cell identification 1 | | | | | | | | octet 10 | | | | | +| ... | | | | | | | | to | | | | | +| Cell identification n | | | | | | | | octet 9+2n | | | | | + +Coding of i-th Cell Identification for Cell identification discriminator = 0010: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|-----------| +| CI value | | | | | | | | octet x+1 | +| CI value cont | | | | | | | | octet x+2 | + +Where $x = 9 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +Coding of the Cell Identification List for Cell identification discriminator = 0100 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|---|---|---|---|------------| +| Cell identification 1 | | | | | | | | octet 5 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 4+5n | + +Coding of i-th Cell Identification for Cell identification discriminator = 0100 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----------|---|---|---|-----------|---|---|---|-----------|--|--|--|--| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | | | | | +| MNC dig 3 | | | | MNC dig 3 | | | | octet x+2 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | | | | | +| LAC | | | | | | | | octet x+4 | | | | | +| LAC cont. | | | | | | | | octet x+5 | | | | | + +Where $x = 4 + 5(i-1)$ + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +Coding of the Cell Identification List for Cell identification discriminator = 0101 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|---|---|---|---|------------| +| Cell identification 1 | | | | | | | | octet 5 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 4+2n | + +Coding of i-th Cell Identification for Cell identification discriminator = 0101 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | + +Where $x = 4 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +Coding of the Cell Identification List for Cell identification discriminator = 0111 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|---|---|---|---|------------| +| Cell identification 1 | | | | | | | | octet 5 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 4+3n | + +Coding of i-th Cell Identification for Cell identification discriminator = 0111 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------|---|---|---|-----------|---|---|---|-----------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet x+2 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | + +Where $x = 4 + 3(i-1)$ + +The octets (x+1)-(x+3) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +The list of cells shall contain only those cells in the group call area that can be accessed through this BSS. + +### 3.2.2.27b Cell Identifier List Segment for established cells + +This information element contains a list of cells that have been established or re-established. + +The *Cell Identifier List Segment for established cells* IE is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|-----------------------------------|---|---|---|------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | | Cell identification Discriminator | | | | octet 3 | +| Cell identification List | | | | | | | | octet 4 | +| | | | | | | | | to | +| | | | | | | | | octet 3+nm | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. + +Octet 3 bits 1-4 contain the Cell Identification Discriminator that is used for the cell identifiers in this Cell Identifier List Segment. The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to 3GPP TS 23.003 is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: + +| | | +|------|----------------------------------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cells. | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, is used to identify the cells within a given MCC and MNC | +| 0010 | Cell Identity, CI, is used to identify the cells within a given MCC and MNC and LAC. | +| 0100 | Location Area Identification, LAI, is used to identify all cells within a Location Area | +| 0101 | Location Area Code, LAC, is used to identify all cells within a location area | +| 0110 | All cells on the BSS are identified | +| 0111 | MCC and MNC, is used to identify all cells within the given MCC and MNC | + +All other values are reserved. + +Octets $4-3+nm$ contain the Cell Identification List. The coding of the Cell Identification List depends on the Cell identification discriminator (octet 3). Below is the coding of the Cell Identification List and the i-th Cell Identification is shown for each Cell identification discriminator (with "i" in the range 1 to n): + +NOTE: No coding is specified for Cell identification discriminator value "0110" as no additional information is required. + +Coding of the Cell Identification List for Cell identification discriminator = 0000 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|---|---|---|---|------------| +| Cell identification 1 | | | | | | | | octet 4 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 3+7n | + +Coding of the i-th Cell Identification for Cell identification discriminator = 0000 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|-----------|---|---|---|-----------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet x+2 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | +| LAC | | | | | | | | octet x+4 | +| LAC cont. | | | | | | | | octet x+5 | +| CI value | | | | | | | | octet x+6 | +| CI value cont | | | | | | | | octet x+7 | + +Where $x = 3 + 7(i-1)$ . + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+6)-(x+7) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +Coding of the Cell Identification List for Cell identification discriminator = 0001 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|-----------|---|---|---|------------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 4 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 5 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 6 | +| Cell identification 1 | | | | | | | | octet 7 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 6+4n | + +Coding of i-th Cell Identification for Cell identification discriminator = 0001 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | +| CI value | | | | | | | | octet x+3 | +| CI value cont | | | | | | | | octet x+4 | + +Where $x = 6 + 4(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+3)-(x+4) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +Coding of the Cell Identification List for Cell identification discriminator = 0010 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|-----------|---|---|---|------------| +| MCC dig 2 | | | | MCC dig 1 | | | | octet 4 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 5 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 6 | +| LAC | | | | | | | | octet 7 | +| LAC cont | | | | | | | | octet 8 | +| Cell identification 1 | | | | | | | | octet 9 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 8+2n | + +Coding of *i*-th Cell Identification for Cell identification discriminator = 0010: + +| | | | | | | | | | +|---------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| CI value | | | | | | | | octet x+1 | +| CI value cont | | | | | | | | octet x+2 | + +Where $x = 8 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +Coding of the Cell Identification List for Cell identification discriminator = 0100 + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Cell identification 1 | | | | | | | | octet 4 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 3+5n | + +Coding of *i*-th Cell Identification for Cell identification discriminator = 0100 + +| | | | | | | | | | +|-----------|---|---|---|-----------|---|---|---|-----------| +| 08 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet x+2 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | +| LAC | | | | | | | | octet x+4 | +| LAC cont. | | | | | | | | octet x+5 | + +Where $x = 3 + 5(i-1)$ + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +Coding of the Cell Identification List for Cell identification discriminator = 0101 + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Cell identification 1 | | | | | | | | octet 4 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 3+2n | + +Coding of *i*-th Cell Identification for Cell identification discriminator = 0101 + +| | | | | | | | | | +|-----------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | + +Where $x = 3 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +Coding of the Cell Identification List for Cell identification discriminator = 0111 + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Cell identification 1 | | | | | | | | octet 4 | +| ... | | | | | | | | to | +| Cell identification n | | | | | | | | octet 3+3n | + +Coding of *i*-th Cell Identification for Cell identification discriminator = 0111 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------|---|---|-----------|---|---|---|---|-----------| +| MCC dig 2 | | | MCC dig 1 | | | | | octet x+1 | +| MNC dig 3 | | | MCC dig 3 | | | | | octet x+2 | +| MNC dig 2 | | | MNC dig 1 | | | | | octet x+3 | + +Where $x = 3 + 3(i-1)$ + +The octets (x+1)-(x+3) are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +The list of cells shall contain only those cells in the group call area that can be accessed through this BSS. + +### 3.2.2.27c Cell Identifier List Segment for cells to be established + +This information element contains a list of cells that have been released or have not yet been established and (in either case) are to be established by the BSS. + +The *Cell Identifier List Segment for cells to be established* IE is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|-----------------------------------|---|---|---|---|-----------------------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | Cell identification Discriminator | | | | | octet 3 | +| Cell identification List | | | | | | | | octet 4
to
octet 3+nm | + +The Cell Identification Discriminator and Cell Identification List fields are coded as in the *Cell Identifier List Segment for established cells* IE (see sub-clause 3.2.2.27b). + +### 3.2.2.27d (void) + +### 3.2.2.27e Cell Identifier List Segment for released cells - no user present + +This information element contains a list of cells in which the call was released because no user responded to the latest uplink access request. + +The *Cell Identifier List Segment for released cells - no users present* IE is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|-----------------------------------|---|---|---|---|-----------------------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | Cell identification Discriminator | | | | | octet 3 | +| Cell identification List | | | | | | | | octet 4
to
octet 3+nm | + +The Cell Identification Discriminator and Cell Identification List fields are coded as in the *Cell Identifier List Segment for established cells* IE (see sub-clause 3.2.2.27b). + +### 3.2.2.27f Cell Identifier List Segment for not established cells - no establishment possible + +This information element contains a list of cells in which the call has not been established or where the call was released and (in either case) establishment by the BSS is not possible. + +The *Cell Identifier List Segment for not established cells - no establishment possible* IE is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|-----------------------------------|---|---|---|-----------------------------------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | | Cell identification Discriminator | | | | octet 3 | +| Cell identification List | | | | | | | | octet 4
to
octet 3+n m | + +The Cell Identification Discriminator and Cell Identification List fields are coded as in the *Cell Identifier List Segment for established cells* IE (see sub-clause 3.2.2.27b). + +### 3.2.2.28 Response Request + +The presence of this element indicates that a Handover Required Reject message is required by the BSS, if the Handover Required message does not result in a handover. + +The element has a fixed length of one octet: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | + +### 3.2.2.29 Resource Indication Method + +This element defines the way the BSS shall transfer the resource information related to a cell to the MSC. The coding is as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|----------------------------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | Resource indication method | | | | octet 2 | + +The coding of the Resource Indication parameter is: + +| | | +|--------------------------------|----------------------------------------------------| +| 0000 | the method i) of sub-clause 3.1.3.1 is selected; | +| 0001 | the method ii) of sub-clause 3.1.3.1 is selected; | +| 0010 | the method iii) of sub-clause 3.1.3.1 is selected; | +| 0011 | the method iv) of sub-clause 3.1.3.1 is selected. | +| All other values are reserved. | | + +### 3.2.2.30 Classmark Information Type 1 + +The classmark information type 1 defines certain attributes of the mobile station equipment in use on a particular transaction. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Classmark | | | | | | | | octet 2 | + +The classmark octet 2 is coded in the same way as the equivalent octet in the classmark 1 element of 3GPP TS 24.008. + +### 3.2.2.31 Circuit Identity Code List + +This element defines in conjunction with a Circuit Identity Code (sub-clause 3.2.2.2) a list of terrestrial channels. + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Range | | | | | | | | octet 3 | +| Status | | | | | | | | octet 4-35 | + +The following codes are used in the range and status fields: + +#### Range: + +A number in pure binary representation ranging from 0 to 255. The number represented by the range code +1 indicates the range of circuits affected by the message. + +#### Status: + +The Status subfield contains up to 256 Status bits numbered from 0 up to 255. Status bit 0 is located in bit position 1 of the first Status subfield octet and refers to the circuit indicated in the CIC subfield {should be "associated Circuit Identity Code Information Element" not "CIC subfield"} itself. Other Status bits follow in numerical order. + +Each Status bit is associated with a circuit identification code such that Status bit n is associated with CIC m+n, where m is the CIC contained in the message. {"where m is the CIC identified in the associated Circuit Identity Code Information Element in the message"}. + +Status bit n is located in bit position nb of the no-th octet of the Status subfield with: + +- $nb = (n \bmod 8) + 1$ ; and +- $no = (n \bdiv 8) + 1$ . + +The number of relevant Status bits in a given Status subfield is equal to the range value +1. + +The Status bits are coded as follows: + +- in the CIRCUIT GROUP BLOCK message: + - 0 no indication. + - 1 block. +- in the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message: + - 0 no indication. + - 1 blocking acknowledgement. +- in the CIRCUIT GROUP UNBLOCK message: + - 0 no indication. + - 1 unblock. +- in the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message: + - 0 no indication. + - 1 unblocking acknowledgement. +- in the UNEQUIPPED CIRCUIT message: + - 0 no indication. + - 1 unequipped. + +### 3.2.2.32 Diagnostics + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Error pointer | | | | | | | | octet 3-4 | +| Message received | | | | | | | | octet 5-n | + +The coding of the error pointer field is as follows: + +Octet 3 gives the number of octets between octet 4 (not included) and the first octet (included) of the part of the message received which provoked the error. Thus: + +| | | +|-----------|-----------------------------------------------------------------------------------------------| +| 0000 0000 | Error location not determined | +| 0000 0001 | The first octet of the message received (i.e. the message type) was found erroneous (unknown) | +| 0000 0010 | The second octet of the message received was found erroneous | +| 0000 0011 | The third octet of the message received was found erroneous | +| etc. | | + +The last three values are reserved for the BSSAP header: + +| | | +|-----------|-----------------------------------------------------------------------------| +| 1111 1101 | The first octet of the BSSAP header (Discrimination) was found erroneous | +| 1111 1110 | (DTAP only) The DLCI (second) octet of the BSSAP header was found erroneous | +| 1111 1111 | The last octet of the BSSAP header (length indicator) was found erroneous | + +Octet 4 is coded as follows: + +| bit | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----|-------|---|---|---|-------------|---|---|---| +| | 0 | 0 | 0 | 0 | | | | | +| | spare | | | | bit pointer | | | | + +The bit pointer field is coded as follows: + +| | | +|-------------|------------------------------------------------------------------------------------| +| bits | | +| 4321 | | +| 0000 | No particular part of the octet is indicated | +| 0001 | An error was provoked by the field whose most significant bit is in bit position 1 | +| 0010 | An error was provided by the field whose most significant bit is in bit position 2 | +| 0011 | An error was provided by the field whose most significant bit is in bit position 3 | +| 0100 | An error was provided by the field whose most significant bit is in bit position 4 | +| 0101 | An error was provided by the field whose most significant bit is in bit position 5 | +| 0110 | An error was provided by the field whose most significant bit is in bit position 6 | +| 0111 | An error was provided by the field whose most significant bit is in bit position 7 | +| 1000 | An error was provided by the field whose most significant bit is in bit position 8 | + +All other values are reserved. + +The "message received" field should be the contents, as far as can be determined, of the received message which provoked the error. + +### 3.2.2.33 Chosen Channel + +This Information Element contains a description of the channel allocated to the MS. + +For VGCS/VBS calls this Information Element contains a description of the channel allocated for the call in the cell. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Channel mode | | | | Channel | | | | octet 2 | + +The channel mode field is coded as follows: + +| Bit | meaning | +|-------------|---------------------------------------------------| +| 8765 | | +| 0000 | no channel mode indication | +| 1001 | speech (full rate or half rate) | +| 1110 | data, 14.5 kbit/s radio interface rate | +| 1011 | data, 12.0 kbit/s radio interface rate | +| 1100 | data, 6.0 kbit/s radio interface rate | +| 1101 | data, 3.6 kbit/s radio interface rate | +| 1000 | signalling only | +| 0001 | data, 29.0 kbit/s radio interface rate | +| 0010 | data, 32.0 kbit/s radio interface rate | +| 0011 | data, 43.5 kbit/s radio interface rate | +| 0100 | data, 43.5 kbit/s downlink and 14.5 kbit/s uplink | +| 0101 | data, 29.0 kbit/s downlink and 14.5 kbit/s uplink | +| 0110 | data, 43.5 kbit/s downlink and 29.0 kbit/s uplink | +| 0111 | data, 14.5 kbit/s downlink and 43.5 kbit/s uplink | +| 1010 | data, 14.5 kbit/s downlink and 29.0 kbit/s uplink | +| 1111 | data, 29.0 kbit/s downlink and 43.5 kbit/s uplink | + +All other values are reserved. + +The channel field is coded as follows: + +| Bit | meaning | +|-------------|------------------| +| 4321 | | +| 0000 | None (see note) | +| 0001 | SDCCH | +| 1000 | 1 Full rate TCH | +| 1001 | 1 Half rate TCH | +| 1010 | 2 Full Rate TCHs | +| 1011 | 3 Full Rate TCHs | +| 1100 | 4 Full Rate TCHs | +| 1101 | 5 Full Rate TCHs | +| 1110 | 6 Full Rate TCHs | +| 1111 | 7 Full Rate TCHs | +| 0100 | 8 Full Rate TCHs | + +NOTE: This value may be returned in the chosen channel information for VGCS/VBS calls in the case where the BSS has decided to de-allocate resources or allocate no resources for the call. + +All other values are reserved. + +### 3.2.2.34 Cipher Response Mode + +This information element is used by the MSC to indicate whether the IMEI is to be included in the CIPHERING MODE COMPLETE message to be sent by the Mobile Station. + +| | | | | | | | | | +|----------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Cipher response mode | | | | | | | | octet 2 | + +Octet 2 is coded as: + +Bits 8, 7, 6, 5, 4, 3, 2 - Spare; + +Bit 1 = 0 - IMEISV must not be included by the Mobile Station; + +Bit 1 = 1 - IMEISV must be included by the Mobile Station. + +### 3.2.2.35 Layer 3 Message Contents + +This is a variable length element used to pass the contents (from octet 3 up to the last octet) of radio interface messages from one network entity to another. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Layer 3 message contents | | | | | | | | octet 3-n | + +The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet. + +Octet j (j = 3, 4, ..., n) is the unchanged octet j of a radio interface layer 3 message as defined in 3GPP TS 24.008, n is equal to the length of that radio interface layer 3 message. + +### 3.2.2.36 Channel Needed + +This information element contains an indication for the mobile station of which channel is needed for the transaction linked to the paging procedure. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---------|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | | Channel | | | octet 2 | + +The Channel field is coded as follows: + +| Bit | 2 | 1 | | +|-----|---|---|----------------------------| +| | 0 | 0 | Any channel | +| | 0 | 1 | SDCCH | +| | 1 | 0 | TCH/F (Full rate) | +| | 1 | 1 | TCH/H or TCH/F (Dual rate) | + +### 3.2.2.37 Trace Type + +A fixed length element indicating the type of trace information to be recorded. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Trace type | | | | | | | | octet 2 | + +Octet 2 contains the trace type. + +Octet 2 is coded as the MSC/BSS Trace Type specified in 3GPP TS 52.008. + +### 3.2.2.38 TriggerID + +A variable length element indicating the identity of the entity which initiated the trace. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Entity identity | | | | | | | | octets 3-22 | + +Octets 3-22 may be typically an OMC identity. + +### 3.2.2.39 Trace Reference + +A fixed length element providing a trace reference number allocated by the triggering entity. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| TraceReference | | | | | | | | octet 2-3 | + +### 3.2.2.40 TransactionID + +A potentially variable length element indicating a particular transaction within a trace. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Transaction number | | | | | | | | octet 3-4 | + +### 3.2.2.41 Mobile Identity + +A variable length element. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Mobile identity | | | | | | | | octet 3-n | + +Octet 3-n contain either the IMSI, IMEISV or IMEI as coded in 3GPP TS 24.008, not including 3GPP TS 24.008 element identifier or 3GPP TS 24.008 octet length value. + +### 3.2.2.42 OMCID + +A variable length element indicating the destination OMC to which trace information is to be sent. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------|---|---|---|---|---|---|---|-------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| OMC identity | | | | | | | | octets 3-22 | +| NOTE: For the OMC identity, see 3GPP TS 52.021. | | | | | | | | | + +### 3.2.2.43 Forward Indicator + +A fixed length element indicating whether the trace is to be continued in a BSS to which the call has been handed over. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-------------------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| spare | | | | Forward indicator | | | | octet 2 | + +Octet 2 is coded as follows: + +| bit | 4 | 3 | 2 | 1 | | +|-----|---|---|---|---|---------------------------------------------| +| | 0 | 0 | 0 | 1 | forward to subsequent BSS, no trace at MSC | +| | 0 | 0 | 1 | 0 | forward to subsequent BSS, and trace at MSC | + +All other values are reserved. + +Bits 5-8 are spare. + +### 3.2.2.44 Chosen Encryption Algorithm + +This element indicates the encryption algorithm being used by the BSS. + +It is coded as follows: + +| | | | | | | | | | +|----------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Algorithm identifier | | | | | | | | octet 2 | + +The algorithm identifier caters for the possible future introduction of different user data encryption algorithms. It is coded as: + +| | | +|-----------|-------------------------------------------| +| 0000 0001 | No encryption used | +| 0000 0010 | GSM user data encryption version 1(A5/1). | +| 0000 0011 | GSM A5/2 | +| 0000 0100 | GSM A5/3 | +| 0000 0101 | GSM A5/4 | +| 0000 0110 | GSM A5/5 | +| 0000 0111 | GSM A5/6 | +| 0000 1000 | GSM A5/7 | + +All other values are Reserved for future international use. + +### 3.2.2.45 Circuit Pool + +This element indicates the circuit pool of a circuit or group of circuits. + +It is coded as follows: + +| | | | | | | | | | +|---------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Circuit pool number | | | | | | | | octet 2 | + +Predefined circuit pools are currently Circuit pool number 1 to Circuit pool number 50. + +The circuit pool element is coded as follows (along with the definition of the predefined circuit pools): + +| Coding | Pool | Supported channels and speech coding algorithms | +|---------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 0001 | Circuit pool number 1 | FR speech version 1
FR data (12, 6, 3.6 kbit/s) | +| 0000 0010 | Circuit pool number 2 | HR speech version 1
HR data (6, 3.6 kbit/s) | +| 0000 0011 | Circuit pool number 3 | FR speech version 1
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s) | +| 0000 0100 | Circuit pool number 4 | FR speech version 2
FR data (12, 6, 3.6 kbit/s) | +| 0000 0101 | Circuit pool number 5 | FR speech version 1
FR speech version 2
FR data (12, 6, 3.6 kbit/s) | +| 0000 0110 | Circuit pool number 6 | FR speech version 2
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s) | +| 0000 0111 | Circuit pool number 7 | FR speech version 1
FR speech version 2
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s) | +| 0000 1000 | Circuit pool number 8 | HSCSD max 2 x FR data (12, 6 kbit/s) | +| 0000 1001 | Circuit pool number 9 | FR data (12, 6, 3.6 kbit/s)
HR data (6, 3.6 kbit/s)
HSCSD max 2 x FR data (12, 6 kbit/s) | +| 0000 1010 | Circuit pool number 10 | FR speech version 1
FR speech version 2
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s)
HSCSD max 2 x FR data (12, 6 kbit/s) | +| 0000 1011 | Circuit pool number 11 | HSCSD max 4 x FR data (12, 6 kbit/s) | +| 0000 1100 | Circuit pool number 12 | FR data (12, 6, 3.6 kbit/s)
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (12, 6 kbit/s) | +| 0000 1101 | Circuit pool number 13 | FR speech version 1
FR speech version 2
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (12, 6 kbit/s) | +| 0000 1110 | Circuit pool number 14 | HSCSD max 6 x FR data (12, 6 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s) | +| 0000 1111 | Circuit pool number 15 | FR data (14.5 kbit/s) | +| 0001 0000 | Circuit pool number 16 | HSCSD max 2 x FR data (14.5 kbit/s)
EDGE FR data (29.0 kbit/s) | +| 0001 0001 | Circuit pool number 17 | HSCSD max 4 x FR data (14.5 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s) | +| 0001 0010 | Circuit pool number 18 | FR data (14.5, 12, 6, 3.6 kbit/s)
HR data (6, 3.6 kbit/s)
HSCSD max 2 x FR data (14.5, 12, 6 kbit/s)
EDGE FR data (29.0 kbit/s) | +| 0001 0011 | Circuit pool number 19 | FR data (14.5, 12, 6, 3.6 kbit/s)
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s) | +| 0001 0100 | Circuit pool number 20 | FR speech version 1
FR speech version 2
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s) | + +| Coding | Pool | Supported channels and speech coding algorithms | +|---------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0001 0101 | Circuit pool number 21 | FR speech version 1
FR speech version 2
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s)
HSCSD max 2 x FR data (14.5, 12, 6 kbit/s)
EDGE FR data (29.0 kbit/s) | +| 0001 0110 | Circuit pool number 22 | FR speech version 1
FR speech version 2
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s) | +| 0001 0111 | Circuit pool number 23 | FR speech version 3
HR speech version 3 | +| 0001 1000 | Circuit pool number 24 | FR speech version 3
FR data (12, 6, 3.6 kbit/s)
HR speech version 3 | +| 0001 1001 | Circuit pool number 25 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (12, 6, 3.6 kbit/s)
HR speech version 3
HR speech version 6 | +| 0001 1010 | Circuit pool number 26 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 3
HR speech version 6 | +| 0001 1011 | Circuit pool number 27 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 6
HR data (6, 3.6 kbit/s) | +| 0001 1100 | Circuit pool number 28 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 6
HR data (6, 3.6 kbit/s) | +| 0001 1101 | Circuit pool number 29 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 2 x FR data (12, 6 kbit/s) | +| 0001 1110 | Circuit pool number 30 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 2 x FR data (14.5, 12, 6 kbit/s)
EDGE FR data (29.0 kbit/s) | + +| Coding | Pool | Supported channels and speech coding algorithms | +|---------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0001 1111 | Circuit pool number 31 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (12, 6 kbit/s) | +| 0010 0000 | Circuit pool number 32 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s) | +| 0010 0001 | Circuit pool number 33 | FR data (14.5, 12, 6, 3.6 kbit/s)
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s) | +| 0010 0010 | Circuit pool number 34 | FR speech version 1
FR speech version 2
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s) | +| 0010 0011 | Circuit pool number 35 | FR speech version 1
FR speech version 2
FR speech version 3
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s) | +| 0010 0100 | Circuit pool number 36 | FR speech version 4
FR speech version 5
HR speech version 4 | +| 0010 0101 | Circuit pool number 37 | FR speech version 3
FR speech version 4
FR speech version 5
HR speech version 3
HR speech version 4
HR speech version 6 | +| 0010 0110 | Circuit pool number 38 | FR speech version 1
FR speech version 2
FR speech version 3
FR speech version 4
FR speech version 5
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 3
HR speech version 4
HR speech version 6 | + +| Coding | Pool | Supported channels and speech coding algorithms | +|---------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0010 0111 | Circuit pool number 39 | FR speech version 1
FR speech version 2
FR speech version 3
FR speech version 4
FR speech version 5
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 4
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 2 x FR data (14.5, 12, 6 kbit/s)
EDGE FR data (29.0 kbit/s) | +| 0010 1000 | Circuit pool number 40 | FR speech version 1
FR speech version 2
FR speech version 3
FR speech version 4
FR speech version 5
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 4
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s) | +| 0010 1001 | Circuit pool number 41 | FR speech version 1
FR speech version 2
FR speech version 3
FR speech version 4
FR speech version 5
FR data (14.5, 12, 6, 3.6 kbit/s)
HR speech version 1
HR speech version 3
HR speech version 4
HR speech version 6
HR data (6, 3.6 kbit/s)
HSCSD max 4 x FR data (14.5, 12, 6 kbit/s)
EDGE max 2 x FR data (29.0 kbit/s)
EDGE FR data (43.5 kbit/s)
EDGE max 2 x FR data (32.0 kbit/s) | +| 0010 1010 | Circuit pool number 42 | FR speech version 1 + CTM | +| 0010 1011 | Circuit pool number 43 | FR speech version 2 + CTM | +| 0010 1100 | Circuit pool number 44 | FR speech version 1 + CTM
FR speech version 2 + CTM | +| 0010 1101 | Circuit pool number 45 | FR speech version 1 + CTM
FR speech version 2 + CTM
HR speech version 1 + CTM | +| 0010 1110 | Circuit pool number 46 | FR speech version 3 + CTM
HR speech version 3 + CTM
HR speech version 6 + CTM | +| 0010 1111 | Circuit pool number 47 | FR speech version 1 + CTM
FR speech version 2 + CTM
FR speech version 3 + CTM
HR speech version 3 + CTM
HR speech version 6 + CTM | +| 0011 0000 | Circuit pool number 48 | FR speech version 1 + CTM
FR speech version 2 + CTM
FR speech version 3 + CTM
HR speech version 1 + CTM
HR speech version 3 + CTM
HR speech version 6 + CTM | +| 0011 0001 | Circuit pool number 49 | FR speech version 3
HR speech version 3
HR speech version 6 | + +| Coding | Pool | Supported channels and speech coding algorithms | +|-----------|------------------------|--------------------------------------------------------------------------------------------------| +| 0011 0010 | Circuit pool number 50 | FR speech version 3
FR data (12, 6, 3.6 kbit/s)
HR speech version 3
HR speech version 6 | +| 1000 xxxx | For national/local use | | +| | | All other values are reserved for future international use | + +### 3.2.2.46 Circuit Pool List + +This element defines a list of BSS preferred circuit pools in order of preference. + +It is coded as follows: + +| | | | | | | | | | +|-------------------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Circuit pool number (1st preferred) | | | | | | | | octet 3 | +| | | | | | | | | | +| Circuit pool number (nth preferred) | | | | | | | | octet n+2 | + +The Circuit pool number is coded as specified in sub-clause 3.2.2.45. + +### 3.2.2.47 Time Indication + +This element defines the period where the information shall be valid. It is fixed length, 2 octets. + +The coding is as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Time | | | | | | | | octet 2 | + +The Time field of this Information Element message in octet 2 is coded as follows: + +| | | +|-----------|--------| +| 0000 0000 | (note) | +| 0000 0001 | | +| : | : | +| 1111 1110 | Time, | + +where the time is the binary value of octet 2 x 10 s (ie 10 s to 2 540 s). + +If the Time field contains the value 255 (1111 1111), the receiving entity shall consider the time as infinite. + +NOTE: The value 0 has a special meaning in the Load indication procedure (refer to sub-clause 3.1.20). + +### 3.2.2.48 Resource Situation + +This element gives, for respective indicated channel type, the total number of channels accessible and the number of channels available on any given cell at the time of construction of the message. + +The number of channels available may be defined in up to five interference bands, the boundaries of these bands being set by O and M as follows: + +``` + +Interference level: 0 -------------------- + Band 1 + X1 -------------------- + Band 2 + X2 -------------------- + Band 3 + X3 -------------------- + Band 4 + X4 -------------------- + Band 5 + X5 -------------------- + +``` + +The element is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|--------------------|---|---|--------------|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Resource and interference band indicator | | | | Channel type | | | | octet 3 | +| 7/15 ind. | Number of channels | | | | | | | octet 4 | +| | | | | | | | | octet 4a | +| Resource and interference band indicator | | | | Channel type | | | | octet 5 | +| 7/15 ind. | Number of channels | | | | | | | octet 6 | +| | | | | | | | | octet 6a | +| ... | | | | | | | | octet N-1 | +| Resource and interference band indicator | | | | Channel type | | | | octet N | +| 7/15 ind. | Number of channels | | | | | | | octet Na | + +The length indicator is a binary representation of the length of the following element. + +The Resource type octet (octets 3, 5, etc.) is coded as follows: + +The Channel type field (bits 1-4 of octets 3, 5, etc.) is coded as follows: + +| Bit | | | | meaning | +|--------------------------------|---|---|---|----------------| +| 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 1 | SDCCH | +| 1 | 0 | 0 | 0 | Full Rate TCH | +| 1 | 0 | 0 | 1 | Half Rate TCH | +| All other values are reserved. | | | | | + +The Resource and interference band indicator field (bits 5-8 of octets 3, 5, etc.) is coded as follows: + +| Bit | | | | meaning | +|--------------------------------|---|---|---|----------------------------------------------------------------------------------------| +| 8 | 7 | 6 | 5 | | +| 0 | 0 | 0 | 0 | Total number of channels accessible (i.e. available for service or currently assigned) | +| 0 | 0 | 0 | 1 | Number of channels available in interference band 1 | +| 0 | 0 | 1 | 0 | Number of channels available in interference band 2 | +| 0 | 0 | 1 | 1 | Number of channels available in interference band 3 | +| 0 | 1 | 0 | 0 | Number of channels available in interference band 4 | +| 0 | 1 | 0 | 1 | Number of channels available in interference band 5 | +| 1 | 1 | 1 | 0 | Number of channels available without supplied interference band classification | +| All other values are reserved. | | | | | + +The Number of channels octets (octets 4, 6, etc.) is coded as follows: + +The Number of channels is a single octet element if the 7/15 indication bit (bit 8 of octets 4, 6, etc.) is set to 0. If the 7/15 indication bit is set to 1 then it is a 2 octet field. It give a 7 (or 15) bit binary representation of the number of channels with resource type as indicated in the nearest preceding resource type octet. The coding convention used when a field extends over more than one octet is defined in sub-clause 3.2.2. + +The number of half rate channels will include half rate channels counted as full rate channels, if these correspond to full rate channels that can be used as half rate channels. + +(e.g. If there is one idle half rate channel and one idle full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3). + +The Resource type octet and the Number of channels octet(s) are repeated for each of the resource type reported. + +For each of the channel type reported, the total number of channels accessible and at least one indication of available channels shall be included. + +The number of channels available without supplied interference band classification is included only in case the interference band definition is not available for the reported channel type. + +### 3.2.2.49 Current Channel Type 1 + +This Information Element contains a description of the channel allocated to the MS. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Channel mode | | | | Channel | | | | octet 2 | + +The channel mode field is coded as follows: + +| Bit | meaning | +|-------------|---------------------------------------------------| +| 8765 | | +| 0000 | signalling only | +| 0001 | speech (full rate or half rate) | +| 0110 | data, 14.5 kbit/s radio interface rate | +| 0011 | data, 12.0 kbit/s radio interface rate | +| 0100 | data, 6.0 kbit/s radio interface rate | +| 0101 | data, 3.6 kbit/s radio interface rate | +| 0111 | data, 29 kbit/s radio interface rate | +| 1000 | data, 32 kbit/s radio interface rate | +| 1001 | data, 43.5 kbit/s radio interface rate | +| 0010 | data, 43.5 kbit/s downlink and 14.5 kbit/s uplink | +| 1010 | data, 29.0 kbit/s downlink and 14.5 kbit/s uplink | +| 1011 | data, 43.5 kbit/s downlink and 29.0 kbit/s uplink | +| 1100 | data, 14.5 kbit/s downlink and 43.5 kbit/s uplink | +| 1101 | data, 14.5 kbit/s downlink and 29.0 kbit/s uplink | +| 1110 | data, 29.0 kbit/s downlink and 43.5 kbit/s uplink | +| 1111 | is reserved | + +All other values are for future use. If the receiver receives an unknown channel mode it shall not be rejected but the receiver shall assume that the channel mode is to be changed. + +The channel field is coded as follows: + +| Bit | meaning | +|------|------------------| +| 0001 | SDCCH | +| 1000 | 1 Full rate TCH | +| 1001 | 1 Half rate TCH | +| 1010 | 2 Full Rate TCHs | +| 1011 | 3 Full Rate TCHs | +| 1100 | 4 Full Rate TCHs | +| 1101 | 5 Full Rate TCHs | +| 1110 | 6 Full Rate TCHs | +| 1111 | 7 Full Rate TCHs | +| 0100 | 8 Full Rate TCHs | +| 0000 | is reserved | + +All other values are for future use. If the receiver receives a unknown channel field it shall not be rejected but the receiver shall assume that the channel is to be changed. + +Consistencies between channel fields and channel modes shall not be checked. + +### 3.2.2.50 Queuing Indicator + +This element contains a recommendation of the BSS concerning application of queuing. + +The element has a fixed length of two octets. + +| | | | | | | | | | +|--------------------|---|---|---|---|---|-----|-------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| spare | | | | | | qri | spare | octet 2 | + +Octet 2 is coded as follows: + +qri = queuing recommendation indicator + +| | | +|---|----------------------------------------| +| 0 | it is recommended not to allow queuing | +| 1 | it is recommended to allow queuing | + +### 3.2.2.51 Speech Version + +This element indicates the speech version being used by the BSS. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---------------------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| spare | Speech version identifier | | | | | | | octet 2 | + +The bits 7-1 of octet 2 are coded in the same way as the permitted speech version identifier in the Channel type information element. + +### 3.2.2.52 Assignment Requirement + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Assignment requirement | | | | | | | | octet 2 | + +## Octet 2 + +| | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------| +| 00000000 | Delay allowed. | +| 00000001 | Immediate and the resources shall not be de-allocated until the end of the call (channel establishment on demand forbidden by the MSC). | +| 00000010 | Immediate and the resources may further be de-allocated by the BSS (channel establishment on demand permitted by the MSC). | + +All other values are reserved. + +## 3.2.2.53 (void) + +## 3.2.2.54 Talker Flag + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | + +## 3.2.2.55 Group Call Reference + +It is coded as follows: + +| | | | | | | | | | | +|-----------------------------------------------|---|---|---|---|---|---|------------|---------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | | +| Element identifier | | | | | | | | | | +| Length | | | | | | | octet 2 | | | +| Descriptive group or broadcast call reference | | | | | | | octets 3-7 | | | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. + +The octets 3-7 are coded in the same way as the octets 2-6 in the Descriptive group or broadcast call reference information element as defined in 3GPP TS 24.008. + +## 3.2.2.56 eMLPP Priority + +This Information Element contains the eMLPP priority of the call. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---------------|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | +| spare | | | | | call priority | | | octet 2 | + +The call priority field (bit 3 to 1 of octet 2) is coded in the same way as the call priority field (bit 3 to 1 of octet 5) in the Descriptive group or broadcast call reference information element as defined in 3GPP TS 24.008. + +## 3.2.2.57 Configuration Evolution Indication + +This information element indicates whether subsequent assignment requests should be expected and the limitation for these subsequent assignments. + +| | | | | | | | | | +|--------------------|-----------------------------------------------------------------------------------------------------------------------------------|---|---|-----|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | +| spare | | | | SMI | | | | octet 2 | +| SMI: | Subsequent Modification Indication. This indicates the maximum number of TCH/F that could be requested in subsequent assignments. | | | | | | | | + +The SMI field is coded as follows: + +| | | +|------|----------------------------------------------------------| +| Bit | 4321 | +| 0000 | No Modification is allowed | +| 0001 | Modification is allowed and maximum number of TCH/F is 1 | +| 0010 | Modification is allowed and maximum number of TCH/F is 2 | +| 0011 | Modification is allowed and maximum number of TCH/F is 3 | +| 0100 | Modification is allowed and maximum number of TCH/F is 4 | + +All other values are reserved. + +### 3.2.2.58 Old BSS to New BSS information + +This information element is defined as a general container for passing Field Elements transparently from an old BSS/RNC/eNB to a new BSS via the MSC. + +These Field Elements are passed in the "Old BSS to New BSS information elements" octets field. The error handling performed by the receiving entity for the "Old BSS to New BSS information elements" field is that specified in sub-clause 3.1.19.7. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Old BSS to New BSS information elements | | | | | | | | octet 3-n | + +The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet and may be set to zero. + +The Old BSS to New BSS information elements field is made up of 0 or more Field Elements listed in the table shown below. + +Field elements may occur in any order in the Old BSS to New BSS information elements field. + +The construction of the Field Elements allows the receiver to ignore unknown Field Elements. + +Due to backward compatibility issues Field Elements in the "Old BSS to New BSS information" may duplicate information from Information Elements in the HANDOVER REQUEST, when this occurs and the new BSS detects an inconsistency between this information then the information contained in the "Old BSS to New BSS information" shall take precedence as long as the coding is understood by the new BSS. + +Reception of an erroneous "Old BSS to New BSS information" shall not cause a rejection of the HANDOVER REQUEST message; the "Old BSS to New BSS information" information element shall be discarded and the handover resource allocation procedure shall continue. + +| FIELD ELEMENT | REFERENCE | LEN | +|----------------------------------------------------|-----------|-----| +| Extra information | 3.2.3.1 | 3 | +| Current Channel Type 2 | 3.2.3.2 | 4 | +| Target cell radio information | 3.2.3.3 | 3 | +| GPRS Suspend information | 3.2.3.4 | 19 | +| MultiRate configuration information | 3.2.3.5 | 3-8 | +| Dual Transfer Mode information | 3.2.3.6 | 3 | +| Inter RAT Handover Info | 3.2.3.7 | 3-n | +| cdma2000 Capability Information | 3.2.3.8 | n | +| Cell Load Information Group | 3.2.3.11 | 3-n | +| VGCS talker mode | 3.2.2.93 | 3 | +| PS Indication | 3.2.3.13 | 3 | +| D-RNTI | 3.2.3.15 | 5 | +| IRAT Measurement Configuration | 3.2.3.16 | 3-n | +| IRAT Measurement Configuration (extended E-ARFCNs) | 3.2.3.18 | 3-n | +| Last used E-UTRAN PLMN ID | 3.2.2.127 | 4 | +| Source Cell ID | 3.2.3.17 | 8-n | + +The D-RNTI field element shall only be present when a Radio Resource Reserve Handover procedure is applied over the Iur-g interface (see 3GPP TS 43.130). + +The Source Cell ID field element shall only be present in the case either the IRAT Measurement Configuration field element or the the IRAT Measurement Configuration (extended E-ARFCNs) field element is present. + +### 3.2.2.59 (void) + +### 3.2.2.60 LCS QoS + +This element indicates the Quality of Service requirements for the location request. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| QoS | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The QoS octets 3 to n are coded in the same way as the equivalent octets in the LCS QoS element of 3GPP TS 49.031. + +### 3.2.2.61 LSA Access Control Suppression + +This information element is included if LSA access control function shall be suppressed in the BSS. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|----|---|---------| +| Element identifier | | | | | | | | octet 1 | +| spare | | | | | | EM | | octet 2 | + +If the connection is an emergency call the MSC shall set the emergency field (bit 1 of octet 2) to 1. If the emergency field is set to 1, the BSS shall suppress exclusive access, LSA only access and preferential access functionality. + +### 3.2.2.62 LCS Priority + +The LCS Priority defines the priority of the location request. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Priority | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Priority octets 3 to n are coded in the same way as the equivalent octets in the LCS Priority element of 3GPP TS 49.031. + +### 3.2.2.63 Location Type + +The Location Type information element indicates the type of location request. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Location Type | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Location Type octets 3 to n are coded in the same way as the equivalent octets in the Location Type element of 3GPP TS 49.031. + +### 3.2.2.64 Location Estimate + +This is a variable length information element providing an estimate of a geographic location of a target MS. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Location estimate | | | | | | | | octet 3-n | + +The length indicator is a binary indication of the number of octets following in the element. + +The Location Estimate field is composed of 1 or more octets with an internal structure according to 3GPP TS 23.032. + +### 3.2.2.65 Positioning Data + +This element indicates the data on the positioning process for possible use in billing in location method evaluation. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Positioning data | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Positioning Data octets 3 to n are coded in the same way as the equivalent octets in the Positioning Data element of 3GPP TS 49.031. + +### 3.2.2.66 LCS Cause + +This element indicates the data on the positioning process for possible use in billing in location method evaluation. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| LCS Cause | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The LCS Cause octets 3 to n are coded in the same way as the equivalent octets in the LCS Cause element of 3GPP TS 49.031. + +### 3.2.2.67 LCS Client Type + +This element identifies the type of LCS Client. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| LCS Client Type | | | | | | | | octet 3-n | + +The LCS Client Type octets 3 to n are coded in the same way as the equivalent octet in the LCS Client Type element of 3GPP TS 49.031. + +### 3.2.2.68 APDU + +This information element is defined as a general container for passing information transparently between BSSs or between BSS and SMLC via the MSC. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2-3 | +| APDU | | | | | | | | octet 4-n | + +The length indicator is a binary indication of the number of octets following in the element. + +The APDU octets 4 to n are coded in the same way as the equivalent octet in the APDU element of 3GPP TS 49.031. When the BSSAP-LE CONNECTIONLESS INFORMATION message is sent from a BSS to a MSC or from a MSC to a BSS during the MTA procedure this information element is not used (i.e. the “Protocol ID” field shall indicate “reserved”). + +### 3.2.2.69 Network Element Identity + +This is a variable length information element identifying a network element, by association with either a designated cell site or a designated location area. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Network Element Identity | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Network Element Identity octets 3 to n are coded in the same way as the equivalent octets in the Network Element Identity element of 3GPP TS 49.031 [19a]. + +When the radio access part of the MTA procedure is performed by a MS in a given cell managed by a non-serving BSS (see 3GPP TS 43.059 [5]) it results in the BSSAP-LE CONNECTIONLESS INFORMATION message being sent from a BSS to the MSC. In this case the “Network Element Identity (target)” information element provides the MSC with information it needs to identify the BSS managing the cell the MS was in when it received the RRLP Multilateration Timing Advance Request message (i.e. the serving BSS) commanding it to perform the radio access part of the MTA procedure (see 3GPP TS 44.031): + +- If the MS performs the radio access part of the MTA procedure in that cell using the RLC Data Block method (see 3GPP TS 44.060) the “Network Element Identity (target)” information element is coded using the Cell Identity (coded as described in 3GPP TS 24.008 [6]) and Routing Area Identification (coded as described in 3GPP TS 24.008 [6]) information corresponding to the cell it was in when it received the RRLP Multilateration Timing Advance Request message. +- If the MS performs the radio access part of the MTA procedure in that cell using the Extended Access Burst method (see 3GPP TS 44.018 [32] and 3GPP TS 44.060) the “Network Element Identity (target)” information element is coded by translating the Short BSS ID received from the MS during the radio access part of the MTA procedure (conveyed to the MS as part of the assistance information) to the known network identity of the BSS managing the cell the MS was in when it received the RRLP Multilateration Timing Advance Request message. +- The “Network Element Identity (source)” information element is configured using the Cell Identity of the cell in which the MS performs the radio access part of the MTA procedure (coded as described in 3GPP TS 24.008 [6]). + +### 3.2.2.70 GPS Assistance Data + +This is a variable length information element indicating the requested GPS assistance data. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| GPS Assistance Data | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The GPS Assistance Data octets 3 to n are coded in the same way as the equivalent octets in the Requested GPS Data element of 3GPP TS 49.031. + +### 3.2.2.71 Deciphering Keys + +This is a variable length information element indicating the requested GPS assistance data. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Deciphering Keys | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Deciphering Key octets 3 to n are coded in the same way as the equivalent octets in the Deciphering Key element of 3GPP TS 49.031. + +### 3.2.2.72 Return Error Request + +This is a variable length information element indicating a request from the source for an error response if the message cannot be delivered to its final destination. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Return Error Type | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Return Error Type octets from 3 to n are coded in the same way as the equivalent octets in the Return Error Request element of 3GPP TS 49.031. + +### 3.2.2.73 Return Error Cause + +This is a variable length information element indicating the reason for unsuccessful delivery of a message to its final destination. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Cause Value | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Cause Value octets from 3 to n are coded in the same way as the equivalent octets in the Return Error Cause element of 3GPP TS 49.031. + +### 3.2.2.74 Segmentation + +This is a variable length information element containing segmentation and message information for a segmented APDU. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Segmentation and Message Information | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Segmentation and Message information octets from 3 to n are coded in the same way as the equivalent octets in the Segmentation element of 3GPP TS 49.031. + +### 3.2.2.75 Service Handover + +The Service Handover defines information to use for handover to UTRAN or cdma2000. It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Service Handover information | | | | | | | | octet 3 | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. + +Service Handover information is coded as follows: + +Bits 4-8: Spare. + +Bits 1 - 3: + +3 2 1 + +- 0 0 0 Handover to UTRAN or cdma2000 should be performed +Handover to UTRAN or cdma2000 is preferred. The handover evaluation of the target cell for handovers shall take into account the preference for UTRAN or cdma2000. +- 0 0 1 Handover to UTRAN or cdma2000 should not be performed +Handover to GSM is preferred. The handover evaluation of the target cell for handovers shall take into account the preference for GSM. +- 0 1 0 Handover to UTRAN or cdma2000 shall not be performed +Handover to UTRAN or cdma2000 is not allowed. + +All other values are interpreted as no information available for service based handover. + +### 3.2.2.76 Source RNC to target RNC transparent information (UMTS) + +This information element is defined as a general container for passing (e.g. UE Capability Information, Target Cell ID) RNC specific information transparently through the core network from BSS to RNC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Source RNC to target RNC transparent information value | | | | | | | | octet 3-n | + +The Source RNC to Target RNC transparent Information value is encoded as the *Source RNC to Target RNC Transparent Container* IE as defined in relevant RANAP specification 3GPP TS 25.413, excluding RANAP tag. + +### 3.2.2.77 Source RNC to target RNC transparent information (cdma2000) + +This information element is defined as a general container for passing (e.g. cdma2000 Capability Information, Target Cell ID) RNC specific information transparently through the core network from BSS to RNC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Source RNC to target RNC transparent information value | | | | | | | | octet 3-n | + +The Source RNC to Target RNC transparent Information value (structure and encoding) for cdma2000 is defined in relevant specifications. + +### 3.2.2.78 GERAN Classmark + +This information element is used to convey cell related information to the MSC. The GERAN classmark information element is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|----------------------------|---|------------------------------------|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Codec List | | | | | | | | octet 3+n | +| Spare | | | | Maximum Number of Traffic Channels | | | | Octet n+1 | +| Spare | | Acceptable Channel Codings | | | | | | Octet n+2 | + +The maximum number of traffic channels in octet n+1 specifies the maximum number of traffic channels supported by the serving cell or, in case of handover, by the target cell. The maximum number of traffic channels field in octet n+1 is coded as follows: + +| bits | meaning | +|------------|---------| +| 321 | | +| 000 | 1 TCHs | +| 001 | 2 TCHs | +| 010 | 3 TCHs | +| 011 | 4 TCHs | +| 100 | 5 TCHs | +| 101 | 6 TCHs | + +All other values are reserved. + +The acceptable channel codings in octet n+2 specifies which channel codings are supported by the serving cell or, in case of handover, by the target cell. The acceptable channel codings field in octet n+2 is coded as follows: + +| | | | +|--------|---|--------------------------| +| Bit 5: | 0 | TCH/F43.2 not acceptable | +| | 1 | TCH/F43.2 acceptable | +| Bit 4: | 0 | TCH/F32 not acceptable | +| | 1 | TCH/F32 acceptable | +| Bit 3: | 0 | TCH/F28.8 not acceptable | +| | 1 | TCH/F28.8 acceptable | +| Bit 2: | 0 | TCH/F14.4 not acceptable | +| | 1 | TCH/F14.4 acceptable | +| Bit 1: | 0 | TCH/F9.6 not acceptable | +| | 1 | TCH/F9.6 acceptable | + +All other values are reserved. + +The codec list specifies which codec types are supported by the serving cell or, in case of handover, by the target cell, and is coded as specified in 3GPP TS 26.103, with the following restrictions: + +- In case of adaptive multi-rate codecs or adaptive multi-rate wideband codecs, the Active Code Set (ACS) octet(s) is (are) not used and shall be ignored by the MSC. +- The Maximal Number of Codec Modes (MACS), if included, shall be set to four. +- The SCS shall indicate the supported codecs within a GERAN cell in case of an adaptive codec type. + +### 3.2.2.79 GERAN BSC Container + +This element is used to convey the selected codec type to the BSC. The GERAN BSC Container information element is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|---|---|---|------------------------------------------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Codec Type | | | | | | | | octet 3 | +| allowed
r i/f rates | | | | Maximum Number
of
Traffic Channels | | | | octet 4 | + +The codec type is coded as specified in 3GPP TS 26.103. + +For CS Speech services octet 4 shall not be present. + +For CS Data services octets 3 and 4 shall be present and the Codec Type 'MuMe' (as specified in 3GPP TS 26.103) shall be used. + +The allowed radio interface data rates indicates the channel coding which is supported by the MS, BSC and MSC. + +Octet 4 shall be coded as follows: + +Bits 8 to 4 indicate the allowed radio interface data rate, per channel; + +- Bit 8: 0 43.5 kbit/s (TCH/F43.2) not allowed +1 43.5 kbit/s (TCH/F43.2) allowed +- Bit 7: 0 32.0 kbit/s (TCH/F32.0) not allowed +1 32.0 kbit/s (TCH/F32.0) allowed +- Bit 6: 0 29.0 kbit/s (TCH/F28.8) not allowed +1 29.0 kbit/s (TCH/F28.8) allowed +- Bit 5: 0 14.5/14.4 kbit/s (TCH/F14.4) not allowed +1 14.5/14.4 kbit/s (TCH/F14.4) allowed +- Bit 4: 0 12.0/9.6 kbit/s (TCH F/9.6) not allowed +1 12.0/9.6 kbit/s (TCH F/9.6) allowed + +In this version of the protocol the MSC shall indicate only one radio interface data rate as allowed. + +The Maximum number of traffic channels is the maximum, which is supported by the MS, BSC and MSC. + +Bits 3-1 specify the maximum number of traffic channels which the BSS may allocate for the call. The maximum number of traffic channels field is coded as follows: + +| bits | meaning | +|------|---------| +| 000 | 1 TCHs | +| 001 | 2 TCHs | +| 010 | 3 TCHs | +| 011 | 4 TCHs | +| 100 | 5 TCHs | +| 101 | 6 TCHs | + +All other values are reserved. + +### 3.2.2.80 New BSS to Old BSS Information + +This information element is defined as a general container for passing field elements transparently between BSSs via the MSC. + +These field elements are passed in the *New BSS to Old BSS information elements* field. The error handling performed by the receiving entity for the *New BSS to Old BSS information elements* field is that specified in sub-clause 3.1.19.7. + +| | | | | | | | | | +|-----------------------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| New BSS to Old BSS information elements | | | | | | | | octet 3-n | + +The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet and may be set to zero. + +The *New BSS to Old BSS information elements* field is made up of 0 or more field elements listed in the table shown below. Field elements may occur in any order in the Old BSS to New BSS information elements field. The construction of the Field Elements allows the receiver to ignore unknown Field Elements. + +Reception of an erroneous *New BSS to Old BSS information* IE shall not cause a rejection of the HANDOVER COMMAND or HANDOVER FAILURE messages. In that case, the *New BSS to Old BSS information* IE shall be discarded and the handover procedure shall continue. + +| FIELD ELEMENT | REFERENCE | LEN | +|---------------------------------|-----------|-----| +| Downlink Cell Load Information | 3.2.3.9 | 6 | +| Uplink Cell Load Information | 3.2.3.10 | 6 | +| DTM Handover Command Indication | 3.2.3.14 | 3 | + +The DTM Handover Command Indication field element shall be included in this information element if the *Layer 3 Information IE* included in a (BSSMAP) HANDOVER REQUEST ACKNOWLEDGE message or (BSSMAP) HANDOVER COMMAND message contains an (RLC/MAC) DTM HANDOVER COMMAND message. + +### 3.2.2.81 Inter-System Information + +This information element is defined as a general container for passing RNC specific information transparently through the core network from a BSS to an RNC. + +| | | | | | | | | | +|------------------------------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Inter-System Information Transparent Container | | | | | | | | octet 3-n | + +The container structure and encoding of the *Inter-System Information Transparent Container* is defined in the RANAP specification (see 3GPP TS 25.413), excluding the RANAP tag. + +### 3.2.2.82 SNA Access Information + +This element identifies the Shared Network Areas (SNA(s)) the UE is authorised to access. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | Octet 1 | +| Length | | | | | | | | Octet 2 | +| Authorised PLMN 1 (1 st octet of Authorised PLMN 1) | | | | | | | | Octet 3 | +| Authorised PLMN n (last octet of Authorised PLMN n) | | | | | | | | .. to | + +Where $m_i$ is the number of Authorised SNAs in the $i^{\text{th}}$ Authorized PLMN. + +$m_i = 0 \dots m$ and may be different in all Authorized PLMNs. +Note that if $n = 1$ , $0 \leq m_i \leq 125$ . + +The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the number of Authorised PLMNs to be identified. + +Coding of the $i^{\text{th}}$ Authorised PLMN: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|---|---|---|-----------|---|---|---|---------------------| +| Length of Authorised PLMN $i$ | | | | | | | | Octet 1 | +| MCC dig 2 | | | | MCC dig 1 | | | | Octet 2 | +| MNC dig 3 | | | | MCC dig 3 | | | | Octet 3 | +| MNC dig 2 | | | | MNC dig 1 | | | | Octet 4 | +| Authorised SNA 1 | | | | | | | | Octet 5 | +| Authorised SNA 1 (cont.) | | | | | | | | Octet 6 | +| Authorised SNA m | | | | | | | | ... to 4 + (2m - 1) | +| Authorised SNA m (cont.) | | | | | | | | ... to 4 + 2m | + +The coding of octet 1 is a binary number indicating the length of the Authorised PLMNi. The length of the Authorised PLMNi depends on the number of Authorised SNAs to be identified. + +The octet 3 bits 5-8 are filled with '1111' if 2 digit MNC is used. + +The Authorised PLMNi contains at least the PLMN identity (octets 2 - 4) of the Authorised PLMNi. The octets 2 - 4 of the Authorised PLMNi are coded as octets 2 - 4 shown in 3GPP TS 24.008 [6], Table 'Location Area Identification information element'. Authorised PLMNi may also include 0 to $m$ Authorised SNAs. + +Coding of the Authorised SNA: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------|---|---|---|---|---|---|---|---------| +| SNAC | | | | | | | | Octet 1 | +| SNAC cont. | | | | | | | | Octet 2 | + +The Shared Network Area Code (SNAC) in octets 1 - 2 is coded as specified in 3GPP TS 23.003 [2]. The least significant bit of SNAC is octet 2 bit 1 and most significant bit is octet 1 bit 8. + +### 3.2.2.83 VSTK\_RAND Information + +This element contains the VSTK\_RAND that is to be used to generate the short term ciphering keys for the given group call. The VSTK\_RAND is defined in 3GPP TS 43.020. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|-------|---|---|---|---|---------| +| Element identifier | | | | | | | | Octet 1 | +| Length | | | | | | | | Octet 2 | +| VSTK RAND | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| | | | | | | | | | +| | | | spare | | | | | Octet 7 | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. + +The length of the VSTK RAND is 36 bits and it is encoded in octets 3,4,5,6 and bits 8 to 5 of octet 7. Bit 8 of octet 3 contains the most significant bit of VSTK RAND, and bit 5 of octet 7 the least significant bit + +### 3.2.2.84 VSTK information + +This element contains the short term key VSTK that is to be used to generate the VGCS ciphering keys for the given group call. The short term key VSTK is defined in 3GPP TS 43.020. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|----------| +| Element identifier | | | | | | | | Octet 1 | +| Length | | | | | | | | Octet 2 | +| VSTK | | | | | | | | Octet 3 | +| | | | | | | | | | +| | | | | | | | | Octet 18 | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. + +The length of the VSTK is 128 bits and it is encoded in octets 3-18. Bit 8 of octet 3 contains the most significant bit of VSTK, and bit 1 of octet 18 the least significant bit + +### 3.2.2.85 Paging Information + +This information element is included if the MSC has some extra information on how to perform the paging. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|--------------|---|----------|---|---------| +| Element identifier | | | | | | | | octet 1 | +| spare | | | | Paging Cause | | VGCS/VBS | | octet 2 | + +If the VGCS/VBS flag is set to zero, the mobile station to be paged is not a member of any VGCS/VBS-group. If the VGCS/VBS flag is set to one, the mobile station to be paged is a member of a VGCS/VBS-group. + +For mobile stations that are members of at least one VBS/VGCS group (i.e. bit 1 of octet 2 is set to 1), the paging cause indicates whether the paging is for a mobile terminating call, USSD or a short message. The paging cause is coded as follows. + +| Bit | | | +|-----|---|---------------------------------------| +| 3 | 2 | | +| 0 | 0 | Paging is for mobile terminating call | +| 0 | 1 | Paging is for a short message | +| 1 | 0 | Paging is for a USSD | +| 1 | 1 | Spare | + +### 3.2.2.86 IMEI + +This information element identifies the International Mobile Station Equipment Identity of the mobile station (see 3GPP TS 23.003). + +The element coding is: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| IMEI coded as the value part of the Mobile Identity IE defined in 3GPP TS 24.008 (NOTE 1) | | | | | | | | octet 3-10 | +| NOTE 1: The Type of identity field in the Mobile Identity IE shall be ignored by the receiver. | | | | | | | | | + +### 3.2.2.87 Velocity Estimate + +This is a variable length information element providing an estimate of the speed and bearing of a target MS. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Velocity estimate | | | | | | | | octet 3-n | + +The length indicator is a binary indication of the number of octets following in the element. + +The Velocity Estimate field is composed of 1 or more octets with an internal structure according to 3GPP TS 23.032. + +### 3.2.2.88 VGCS Feature Flags + +This BSSMAP information element is used by the MSC and BSS to indicate the support of some optional features for a VBS or VGCS group call. + +The VGCS Feature Flags IE is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---------|------------|-----------|---|-----------|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | TC
P | Bss
Res | AS
Ind | | TP
Ind | | octet 3 | + +Octet 3 is coded as follows: + +Bit 1 is the talker priority indicator (TP Ind). + +| Bit | | +|----------|-------------------------------| +| 1 | | +| 0 | Talker Priority not supported | +| 1 | Talker Priority supported | + +Bits 2 and 3 are the A-interface resource sharing indicator (AS Ind). + +| Bit | | +|----------|--------------------------------| +| 2 | | +| 0 | No A-interface circuit sharing | +| 1 | A-interface circuit sharing | + +| Bit | | +|----------|-----------------------------| +| 3 | | +| 0 | No A-interface link sharing | +| 1 | A-interface link sharing | + +The BSS shall never set bit 2 and bit 3 to 1. If it does the MSC should clear the call. + +Bit 4 is the group or broadcast call re-establishment by the BSS indicator (Bss Res). + +| Bit | | +|----------|--| +| 4 | | + +| | | +|---|---------------------------------------------------------------| +| 0 | No re-establishment of the group or broadcast call by the BSS | +| 1 | Re-establishment of the group or broadcast call by the BSS | + +The BSS shall only set bit 4 of the VGCS Features Flags IE to 1 in the VGCS/VBS SETUP ACK message if: + +- the MSC has also set bit 4 of this IE to 1 in the VGCS/VBS SETUP message, and +- the BSS has also set bit 3 of this IE to 0 in the VGCS/VBS SETUP ACK message + +Bit 5 is the Talker Channel Parameter (TCP). + +| | | +|-----|------------------------------------------------------------------------------------------------------------------------| +| Bit | | +| 5 | | +| 0 | talker channel parameter is not applicable to this call | +| 1 | talker channel parameter is applicable to this call, talker shall be established and maintained on a dedicated channel | + +The BSS shall set bit 5 of the VGCS Flags IE to 1 in the VGCS/VBS SETUP ACK message only if: + +- the MSC has also set bit 5 of this IE to 1 in the VGCS/VBS SETUP message, and +- the BSS supports the option of Talker Channel Parameter. + +### 3.2.2.89 Talker Priority + +This information element contains the talker priority. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|----------|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | | | Priority | | octet 2 | + +**Table 3.2.2.90.1: Talker Priority information element format** + +| | | | +|--------------------|---|-------------------------| +| Priority (octet 2) | | | +| Bits | | | +| 2 | 1 | | +| 0 | 0 | Normal Priority | +| 0 | 1 | Privileged Priority | +| 1 | 0 | Emergency Priority | +| 1 | 1 | reserved for future use | + +### 3.2.2.90 Emergency Set Indication + +This information element is included to set the Emergency mode. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | + +### 3.2.2.91 Talker Identity + +This information element contains additional information regarding the identity of the talker. + +It is coded as follows: + +| | | | | | | | | | +|-----------------------|---|---|---|---|---|-------------|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | Octet 1 | +| Length | | | | | | | | Octet 2 | +| spare | | | | | | Filler Bits | | Octet 3 | +| Talker Identity field | | | | | | | | Octet 4-20 | + +Octet 3 is coded as follows: + +- Filler Bits (Bits 1-3). This field contains the binary representation of the number of unused bits in the last octet of the Talker Identity field. The filler bits are situated in the val(Filler Bits) least significant bits of the last octet of the Talker Identity field; +- Bits 4 to 8 are spare Octets 4, etc. contain the Talker Identity field. Bit 8 of octet 4 contains the most significant bit. + +### 3.2.2.92 SMS to VGCS + +This information element contains a short message for the on going VGCS group call. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|-------------| +| SMS_to on going VGCS IEI | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| SMS content | | | | | | | | Octet 3-250 | + +Octet 2 is a binary indication of the length of the remainder of the element in octets. + +The SMS content field is coded as follows + +- this field contains the RP-DATA message as defined in 3GPP TS 24.011. + +### 3.2.2.93 VGCS talker mode + +The *VGCS talker mode* information element contains the RR mode of the VGCS talker and the Group cipher key number in use on the voice group channel. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|-------------------------|---|---|---|------------|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| RR mode | Group cipher key number | | | | 0
spare | | | | + +Octet 3 is coded as follows: + +| | | +|-------------------------------------------|--------------------------------------------------| +| RR mode | | +| Bit | | +| 8 | 7 | +| 0 | 0 dedicated mode (i.e. dedicated channel) | +| 0 | 1 group transmit mode (i.e. voice group channel) | +| Other values are reserved for future use. | | +| Group cipher key number | | +| Bit | | +| 6 | 5 4 3 | +| 0 | 0 0 0 no ciphering | +| 0 | 0 0 1 cipher key number 1 | +| 0 | 0 1 0 cipher key number 2 | +| 0 | 0 1 1 cipher key number 3 | +| 0 | 1 0 0 cipher key number 4 | +| 0 | 1 0 1 cipher key number 5 | +| 0 | 1 1 0 cipher key number 6 | +| 0 | 1 1 1 cipher key number 7 | +| 1 | 0 0 0 cipher key number 8 | +| 1 | 0 0 1 cipher key number 9 | +| 1 | 0 1 0 cipher key number A | +| 1 | 0 1 1 cipher key number B | +| 1 | 1 0 0 cipher key number C | +| 1 | 1 0 1 cipher key number D | +| 1 | 1 1 0 cipher key number E | +| 1 | 1 1 1 cipher key number F | + +### 3.2.2.94 VGCS/VBS Cell Status + +This BSSMAP information element is used by the BSS to indicate to the MSC the status of an individual cell for the voice group or broadcast call. + +The VGCS/VBS Cell Status IE is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------|---|--------------------|---|--------|---|---|---|---------| +| | | Element identifier | | | | | | octet 1 | +| | | Length | | | | | | octet 2 | +| Spare | | | | Status | | | | octet 3 | + +Octet 3 is coded as follows: + +Bit 1-3 is the cell's status for the voice group or broadcast call (Status). + +| | | | +|----------|----------|-----------------------------------------------------------------------------------------------------------------| +| Bit | | | +| 3 | 2 | 1 | +| 0 | 0 | 0 Cell is established for the voice group or broadcast call | +| 0 | 0 | 1 Cell is not established for the voice group or broadcast call. Establishment by the BSS is to be attempted | +| 0 | 1 | 0 Cell is released for the voice group or broadcast call because no user is present | +| 0 | 1 | 1 Cell is not established for the voice group or broadcast call. No establishment by the BSS is to be attempted | +| 1 | 0 | 0 Reserved | +| 1 | 0 | 1 Reserved | +| 1 | 1 | 0 Reserved | +| 1 | 1 | 1 Reserved | + +### 3.2.2.95 GANSS Assistance Data + +This is a variable length information element indicating the requested GANSS assistance data. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|--------------------|---|---|---|---|---|-----------| +| | | Element identifier | | | | | | octet 1 | +| | | Length | | | | | | octet 2 | +| GANSS Assistance Data | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The GANSS Assistance Data octets 3 to n are coded as the Requested GANSS Data element of 3GPP TS 49.031. + +### 3.2.2.96 GANSS Positioning Data + +This element indicates the data on the positioning process for possible use in billing in location method evaluation. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| GANSS Positioning data | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The GANSS Positioning Data octets 3 to n are coded as the GANSS Positioning Data element of 3GPP TS 49.031. + +### 3.2.2.97 GANSS Location Type + +The GANSS Location Type information element indicates the type of GANSS location request. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| GANSS Location Type | | | | | | | | octet 3-n | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The GANSS Location Type octets 3 to n are coded as the GANSS Location Type element of 3GPP TS 49.031. + +### 3.2.2.98 Application Data + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Application Data | | | | | | | | octet 3-11 | + +Octets 3-11 contain the Application Data as coded in 3GPP TS 44.018, not including the 3GPP TS 44.018 element identifier. + +### 3.2.2.99 Data Identity + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Data Identity | | | | | | | | octet 3 | + +Octet 3 contains the Data Identity as coded in 3GPP TS 44.018, not including the 3GPP TS 44.018 element identifier. + +### 3.2.2.100 Application Data Information + +This information element is used by the BSS to provide information associated with application data which has been received from a mobile station and is being forwarded to the MSC.. + +The Application Data Information IE is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|-----------|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | | | | BT
Ind | | octet 3 | + +Octet 3 is coded as follows: + +Bit 1 is the BSS transmission indication (BT Ind) and indicates whether the BSS has already transmitted the application data to cells in the group call area with which it is associated. + +| | | +|-----|-----------------------------------------------------------| +| Bit | | +| 1 | | +| 0 | BSS has not transmitted the application data to cells | +| 1 | BSS has already transmitted the application data to cells | + +### 3.2.2.101 MSISDN + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| MSISDN | | | | | | | | octet 3-12 | + +Octets 3-12 contain the digits of an MSISDN, coded as in 3GPP TS 24.008, Calling party BCD number, octets 4 – 13. + +### 3.2.2.102 AoIP Transport Layer Address + +This Information Element provides either an IPv4 or and IPv6 Address and UDP port value for the Transport Layer information of the connection end point. The Length differentiates between IPv4 and IPv6. + +In case of an IPv4 Address it is coded as follows: + +| | | | | | | | | | +|---------------------------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length = 6 | | | | | | | | octet 2 | +| IPv4 Address (MSByte first – LSByte last) | | | | | | | | octet 3-6 | +| UDP Port Value (MSByte first – LSByte last) | | | | | | | | octet 7-8 | + +In case of an IPv6 Address it is coded as follows: + +| | | | | | | | | | +|---------------------------------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length = 18 | | | | | | | | octet 2 | +| IPv6 Address (MSByte first – LSByte last) | | | | | | | | octet 3-18 | +| UDP Port Value (MSByte first – LSByte last) | | | | | | | | octet 19-20 | + +### 3.2.2.103 Speech Codec List + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---|-------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Speech Codec Element 1 | | | | | | | | octet 3-
(3+m) | +| Speech Codec Element n | | | | | | | | octet p-
(p+k) | + +The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator. The length depends on the number and type of Speech Codec Elements to be included. The minimum length of one Speech Codec Element is 1 octet and the maximum length is 3 octets. The maximum number of Speech Codec Elements within the Speech Codec List is not defined. + +The coding of one "Speech Codec Element" is in general: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|----|----|----|---------------------|---|---|---|---|------------|-------------| +| FI | PI | PT | TF | | | | | Codec Type | octet z m | +| | | | Extended Codec Type | | | | | | octet z+1 c | +| | | | Configuration | | | | | | octet z+2 c | +| | | | Configuration | | | | | | octet z+3 c | + +The "Codec Type" field specifies the Codec Type for the radio interface. It may contain a certain 3GPP Speech Codec Type directly (see below) or it may contain the so called "Codec Extension" = 0xFh, in which case the real Codec Type follows in the next octet as "Extended Codec Type". This extension mechanism is necessary in order to allow more than 16 different Codec Types in future. None, one or two "Configuration" octets may follow after the "(Extended) Codec Type" octet, depending on the specified Codec Type. Each Codec Type is in addition associated with 4 bits to specify the A-Interface Type and the transcoder resource location (FI = "full IP", PI = "PCM over IP", PT = "PCM over TDM", TF = "TFO Flag"). + +In order to support also Circuit Switched Data and Fax services a so called "CSData Codec" is used, see below. + +This "Speech Codec List" Information Element is used for "Codec List (BSS Supported)" and "Codec List (MSC Preferred)". + +Each Speech Codec Element in a Speech Codec List contains a Codec Type, supported on the radio interface by the BSS (in the "Codec List (BSS Supported)") or preferred (on the radio interface) by the MSC (in the "Codec List (MSC Preferred)"). + +The "**Codec List (BSS Supported)**" contains all the codecs for which the BSS wants to indicate support, not depending on the "Codec List (MSC Preferred)" and the MS capabilities. The "Codec List (BSS Supported)" is not in priority order and may include any number of Codec Types and any number of Codec Configurations per Codec Type and any A-Interface Type per Codec Type. The same Codec Type can be listed more than once, e.g. for AMR Codec Types, to indicate TFO/TrFO support for some combinations of AMR configurations and A-Interface Types only. The mandatory GSM\_FR may be excluded from the list (e.g. in overload conditions, when half rate Codecs are preferred). + +The "**Codec List (MSC Preferred)**" contains all the codecs for which the MSC wants to indicate support, by taking into account BSS and MS capabilities as well. This is the list of codecs allowed by the MSC for this assignment or handover (see [51] for more information). The "Codec List (MSC Preferred)" may include codecs that are not included in the "Codec List (BSS Supported)". The "Codec List (MSC Preferred)" shall not include codecs that are not supported by the MS. The codecs in the "Codec List (MSC Preferred)" shall be listed in priority order as set by the MSC, with the most preferred Codec Type first (e.g. the one that may enable TrFO or TFO). The "Codec List (MSC Preferred)" may contain any number of Codec Types and any number of Codec Configurations per Codec Type and any A-Interface Type per Codec Type. If more than one A-Interface Type is indicated for one Codec Type, then FI has higher priority than PI and this has higher priority than PT, see below. The same Codec Type can be listed more than once, e.g. it can be included at the top of the list (most preferred Codec Type) with one Codec Configuration or A-interface type only, and then with all the possible configurations further down in the list. If there are no common codecs between Codec List (BSS Supported) and the codecs supported by MS, then GSM-FR shall always be included in the Codec List (MSC Preferred) as a default option. + +For true Speech Codec Types (not the CSData Codec Type) these four bits have the following meaning for the A-Interface Type: + +**FI** indicates Full IP + +- '1' means: AoIP with compressed speech via RTP/UDP/IP is supported by the BSS (in the "Codec List (BSS Supported)") or preferred by the MSC (in the "Codec List (MSC Preferred)") for this Codec Type. A Transcoder Resource is not necessary in BSS. +- '0' means: Compressed speech via RTP/UDP/IP is not supported by the BSS or not preferred by the MSC for this Codec Type. + +**PI indicates PCMoIP** + +- ‘1’ means: Transport of PCM over A-Interface via RTP/UDP/IP is supported by the BSS (i.e. a Transcoder Resource may be located in BSS) or preferred by the MSC (i.e. a Transcoder Resource needs to be located in BSS) for this (radio) Codec Type. +- ‘0’ means: PCM over A interface with IP as transport is not supported by the BSS or not preferred by the MSC for this Codec Type + +**PT indicates PCMoTDM** + +- ‘1’ means: Transport of PCM over A-Interface via TDM is supported by the BSS (i.e. a Transcoder Resource may be located in BSS) or preferred by the MSC (i.e. a Transcoder Resource needs to be located in BSS) for this (radio) Codec Type. +- ‘0’ means: PCM over A-Interface with TDM as transport is not supported by the BSS or not preferred by the MSC for this Codec Type. + +**TF indicates TFO support** + +- ‘1’ means: TFO supported by the BSS or TFO support is preferred by the MSC for this Codec Type +- ‘0’ means: TFO is not supported by the BSS or TFO support is not preferred by the MSC for this Codec Type + +The TF bit is valid only if either the PI or the PT bit are set to ‘1’ and indicates whether the sender supports the TFO functionality for the corresponding call. TF bits in the "Codec List (MSC Preferred)" do not mandate the establishment of TFO, which may only be performed through in-band TFO procedures. + +The Codec Type is valid if at least one of FI, PI or PT is set to ‘1’. If the Codec Type is not valid the Speech Codec Element shall be ignored. + +For the CSData Codec Type these four bits have the following meaning for the A-Interface Type : + +**FI** is undefined and reserved for future use. It is coded with zero. + +**PI indicates CSDoIP** + +- ‘1’ means: Transport of Circuit Switched Data over the A-Interface via RTP/UDP/IP is supported by the BSS or preferred by the MSC. The Rate Adaptation Ressource needs to be located in BSS for this. +- ‘0’ means: Transport of Circuit Switched Data over A interface via RTP/UDP/IP is not supported by the BSS or not preferred by the MSC. + +**PT indicates CSDoTDM** + +- ‘1’ means: Transport of Circuit Switched Data over the A-Interface via TDM is supported by the BSS or preferred by the MSC. The Rate Adaptation Ressource needs to be located in BSS for this. +- ‘0’ means: Transport of Circuit Switched Data over A interface via TDM is not supported by the BSS or not preferred by the MSC. + +**TF** is undefined and reserved for future use. It is coded with zero. + +The Codec Type is valid if at least one of FI, PI or PT is set to ‘1’. If the Codec Type is not valid the Speech Codec Element shall be ignored. + +The coding of Speech Codec Element for GSM\_FR, GSM\_HR or GSM\_EFR: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet x | +|----|----|----|----|---|---------------------------------------------------|---|---|---------| +| FI | PI | PT | TF | | Codec Type
(GSM_FR or
GSM_HR or
GSM_EFR) | | | | + +The Codec Type: + +**GSM\_FR** is coded ‘0000’. + +**GSM\_HR** is coded ‘0001’. + +**GSM\_EFR** is coded '0010'. + +The coding of Speech Codec Element for FR\_AMR, HR\_AMR and OHR\_AMR: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|-----|-----|-----|---------------------------------------------------|-----|----|----|-----------| +| FI | PI | PT | TF | Codec Type
(FR_AMR or
HR_AMR or
OHR_AMR) | | | | octet y | +| S7 | S6 | S5 | S4 | S3 | S2 | S1 | S0 | octet y+1 | +| S15 | S14 | S13 | S12 | S11 | S10 | S9 | S8 | octet y+2 | + +The Codec Type and the Codec Configuration: + +**S0 – S15** indicates the supported Codec Configurations (Config-NB-Code) by the BSS or preferred Codec Configurations by the MSC, see TS 28.062, Table 7.11.3.1.3-2: Preferred Configurations for the Adaptive Multi-Rate Codec Types. + +NOTE: One of these Codec Configurations, "Config-NB-Code 1" = S1, is recommended for TrFO. + +If AMR-NB is supported for compressed speech on the A-Interface, then Config-NB-Code 1 shall be supported by BSS and Core Network to guarantee interoperation, see also TS 26.103 [44]. The other preferred AMR-NB Configurations (Config-NB-Code 0, 2..15) are optional. + +**FR\_AMR** is coded '0011'. + +**S11, S13 and S15** are reserved and coded with zeroes. + +**HR\_AMR** is coded '0100'. + +**S6 - S7 and S11 – S15** are reserved and coded with zeroes. + +**OHR\_AMR** is coded '1011'. + +**S11, S13 and S15** are reserved and coded with zeroes. + +The coding of Speech Codec Element for FR\_AMR-WB, OFR\_AMR-WB and OHR\_AMR-WB: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----|----|----|----|-------------------------------------------------------------|----|----|----|-----------| +| FI | PI | PT | TF | Codec Type
(FR_AMR-WB or
OFR_AMR-WB or
OHR_AMR-WB) | | | | octet z | +| S7 | S6 | S5 | S4 | S3 | S2 | S1 | S0 | octet z+1 | + +The Codec Type and the Codec Configuration: + +**S0 – S7** indicates the supported Allowed Codec Configuration (Config-WB-Code) by the BSS or preferred Allowed Codec Configurations by the MSC, see TS 26.103, Table 5.7-1: Allowed Configurations for the Adaptive Multi-Rate – Wideband Codec Types. + +If AMR-WB is supported, Config-WB-Code 0 shall be supported (as stated in TS 26.103). The others, Config-WB-Code 2 and 4 are optional. + +**FR\_AMR-WB** is coded '1001'. + +**S0** is set to '1'. **S1 - S7** are reserved and coded with zeroes. + +**OFR\_AMR-WB** is coded '1100'. + +**S0, S2, S4** indicates the supported Codec Configurations. **S1, S3, S5, S6, S7** are reserved and coded with zeroes. + +**OHR\_AMR-WB** is coded '1101'. + +**S0** is set to '1'. **S1 - S7** are reserved and coded with zeroes. + +The coding of Speech Codec Element for the **CSData** Codec Type is: + +| | | | | | | | | | | | | | +|------------------------------|----|-------|---|------|---|---|---|-----------|--|--|--|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +| - | PI | PT | - | 0xFh | | | | octet y | | | | | +| Extended Codec Type (CSData) | | | | | | | | octet y+1 | | | | | +| R2 | R3 | spare | | | | | | octet y+2 | | | | | + +The Codec Type and the Codec Configuration: + +In order to reduce data loss caused by single or double lost RTP packets in IP transport, several redundant (i.e. repeated) data blocks may be packed into one RTP packet after this redundancy has been negotiated between BSS and MSC. "Redundancy Level" is a bitmap indicating the values of the redundancy level related to the RTP packet. "Redundancy Level" could be considered as the Configuration of CSData Codec Type. This octet is always included (even if PI = 0), although Redundancy Level is not defined for the legacy A-Interface (PT = 1). + +**R2** and **R3** indicate the support of the Redundancy Level 2 (optional) and 3 (optional), while support of Redundancy Level 1 (one data block is contained in one RTP packet, i.e., no redundancy is used) is mandatory. The redundancy levels are not depending on each other, it is for example allowed to support redundancy level 1 and 3 without supporting redundancy level 2. + +**R2** indicates Redundancy Level = 2 (two successive data blocks are contained in one RTP packet): + +'1' means: Redundancy Level = 2 is supported; +'0' means: Redundancy Level = 2 is not supported. + +**R3** indicates Redundancy Level = 3 (three successive data blocks are contained in one RTP packet): + +'1' means: Redundancy Level = 3 is supported; +'0' means: Redundancy Level = 3 is not supported. + +In Codec List (BSS Supported) and Codec List (MSC Preferred) more than one of these A-Interface Types and Redundancy Levels may be flagged to allow an open negotiation and to restrict the negotiation as far as necessary. But in "Speech Codec (Used)", "Speech Codec (Chosen)" and "Speech Codec (MSC Chosen)" exactly one A-Interface Type and exactly one Redundancy Level shall be specified. Redundancy Level 1 is specified by flagging neither R2 nor R3. + +The existing "Channel Type" IE contains all the other parameters for fax and data calls. This Channel Type IE and the CSData Codec Type shall contain consistent data. + +Spare bits are reserved and coded with zeroes. + +**CSData** is coded with 0xFDh or '1111 1101' (see also TS 26.103). + +### 3.2.2.104 Speech Codec + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---|-------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Speech Codec Element 1 | | | | | | | | octet 3-
(3+m) | +| Speech Codec Element n | | | | | | | | octet p-
(p+k) | + +The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator. The length depends on the number and type of Speech Codec Elements to be included. The minimum length of one Speech Codec Element is 1 octet and the maximum length is 3 octets. + +This Information Element is used for "Speech Codec (Used)", "Speech Codec (Chosen)" and "Speech Codec (MSC Chosen)". In all three cases exactly one Codec Type, exactly one Codec Configuration and exactly one A-Interface Type (and whether compressed speech via RTP/UDP/IP is used or not in case of IP user plane transport) shall be indicated, i.e. only one of the bits FI, PI or PT shall be set to 1 (see below). As an exception, in "Speech Codec (MSC Chosen)", in case of AMR-NB, there can be both, FR\_AMR, HR\_AMR and OHR Codec Types included and in case of AMR-WB, there can be both, FR\_AMR-WB, OHR\_AMR-WB and OFR\_AMR-WB Codec Types included, with the same or compatible Codec Configurations. + +The Codec Type and the Codec Configuration are coded as specified in clause 3.2.2.103. + +The A-Interface Type is coded as follows: + +**FI** indicates Full IP + +- ‘1’ means: AoIP with compressed speech via RTP/UDP/IP is selected for this Codec Type. +- ‘0’ means: Compressed speech via RTP/UDP/IP is not selected for this Codec Type. + +This bit is not defined for the CSData Codec Type. + +**PI** indicates PCMoIP + +- ‘1’ means: PCM over A-Interface via RTP/UDP/IP is selected for this Codec Type. +- ‘0’ means: PCM over A interface with RTP/UDP/IP is not selected for this Codec Type. + +**PT** indicates PCMoTDM + +- ‘1’ means: PCM over A-Interface with TDM as transport is selected for this Codec Type. +- ‘0’ means: PCM over A-Interface with TDM as transport is not selected for this Codec Type. + +**TF** indicates TFO Support + +- ‘1’ means: TFO Support is selected for this Codec Type. +- ‘0’ means: TFO Support is not selected for this Codec Type. + +This bit is not defined for the CSData Codec Type. + +The TF bit is valid only if either the PI or the PT bit are set to ‘1’ and indicates whether the sender supports the TFO functionality for the corresponding call. The establishment of TFO is not mandated and may only be performed through in-band TFO procedures. + +The Codec Type is valid if at least one of FI, PI or PT is set to ‘1’. If the Codec Type is not valid the Speech Codec Element shall be ignored. + +### 3.2.2.105 Call Identifier + +The Call Identifier information element is a value defined on a per MSC basis by which a call in the MSC and the BSS could be identified. The Call Identifier shall not be changed as long as an IP interface is used and the call is served by the same MSC and the same SCCP connection. The Call Identifier information element is included if the core network supports an IP based User Plane interface. + +The Call Identifier is a logical concept. It is used to identify an IP based call in control plane. + +Call Identifier shall only be allocated by MSC. + +The element is 4 octets in length: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Call Identifier (least significant bits) | | | | | | | | octet 2 | +| Call Identifier | | | | | | | | octet 3 | +| Call identifier | | | | | | | | octet 4 | +| Call Identifier (most significant bits) | | | | | | | | octet 5 | + +### 3.2.2.106 Call Identifier List + +This IE identifies a list of Call Identifiers. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|--------------------|---|---|---|---|---|---|---------| +| | Element identifier | | | | | | | Octet 1 | + +| | | +|-------------------|------------------| +| Length | Octet 2 | +| Call Identifier 1 | Octet 3-6 | +| ... | | +| Call Identifier n | n*4-1 -
n*4+2 | + +The coding of octet 2 is a binary number indicating the length of the remaining element. + +The Call Identifier List may include from one up to 62 Call Identifiers. + +NOTE: The upper limit of 62 Call Identifiers keeps the RESET IP RESOURCE message below 255 octets. + +### 3.2.2.107 A-Interface Selector for RESET + +This optional IE may identify the calls that shall be cleared. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|-----|-----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | Octet 1 | +| spare | | | | | | RIP | RTD | Octet 2 | + +**RIP** indicates "Reset all calls associated to IP links": + +'1' means: all calls associated to IP links shall be cleared; + '0' means: calls associated to IP links shall not be cleared. + +**RTD** indicates "Reset all calls associated to TDM circuits": + +'1' means: all calls associated to TDM links shall be cleared; + '0' means: calls associated to TDM links shall not be cleared. + +### 3.2.2.108 (void) + +### 3.2.2.109 $KC_{128}$ + +This element contains the 128 bit long encryption key used in connection with the encryption algorithm A5/4. + +It is a fixed length element. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| $KC_{128}$ | | | | | | | | octet 2-17 | + +### 3.2.2.110 CSG Identifier + +This element indicates the identifier of the Closed Subscriber Group within the PLMN, as defined in [2] and the cell access mode of the cell as defined in [32],[50]. It contains the following fields: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|------------------|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| CSG Id | | | | | | | | octet 3-6 | +| Spare | | | | | | | Cell Access Mode | octet 7 | + +Octets 3 to 6 contain the *CSG Identity (CSG-ID)* of the cell (defined in 3GPP TS 23.003) as reported by the mobile station (see 3GPP TS 44.018). Bits 4 to 8 of octet 6 are spare and set to zero. + +The Cell Access Mode (bit 1 of octet 7) field indicates whether a cell is a Closed access mode, i.e. a CSG cell, or in a Hybrid access mode, i.e. a hybrid cell (see 3GPP TS22.220, 3GPP TS 44.018). It is coded as follows: + +Bit + +1 + +0 CSG cell + +1 Hybrid cell + +Spare bits are reserved and coded with zeroes. + +### 3.2.2.111 Redirect Attempt Flag + +This IE indicates that the CN shall respond with a REROUTE COMMAND or a REROUTE COMPLETE message. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | + +### 3.2.2.112 Reroute Reject Cause + +This IE indicates the cause of the reject of the Initial MS message in case of MOCN and GWCN configurations for network sharing. + +It is coded as follows: + +| | | | | | | | | | | +|----------------------------|---|---|---|---|---|---|---|---------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | | +| Element identifier | | | | | | | | | | +| Reroute Reject cause value | | | | | | | | | | + +| Reroute Reject cause value (octet 2) | | | | | | | | | +|---------------------------------------------|---|---|---|---|---|---|---|---------------------------------------------------------------------------| +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Reserved | +| | | | " | | | | " | | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | Reserved | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | PLMN not allowed (meaning is defined in [6]) | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | location area not allowed (meaning is defined in [6]) | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | roaming not allowed in this location area (meaning is defined in [6]) | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | GPRS services not allowed in this PLMN (meaning is defined in [6]) | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | no suitable cell in location area (meaning is defined in [6]) | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | CS/PS domain registration coordination required (meaning defined in [51]) | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | Network failure (meaning is defined in [6]) | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | Reserved | +| | | | " | | | | " | | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Reserved | + +### 3.2.2.113 Send Sequence Number + +This IE indicates the value of the Send Sequence Number as defined in [6]. + +It is coded as follows: + +| | | | | | | | | | | +|----------------------|-------|---|---|---|---|---|---|---------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | | +| Element identifier | | | | | | | | | | +| Send Sequence Number | spare | | | | | | | | | + +Octet 2 is coded as in message type IE defined in [6]. + +### 3.2.2.114 Reroute complete outcome + +This IE indicates the outcome of the reroute procedure in case of MOCN and GWCN configurations for network sharing. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Outcome value | | | | | | | | octet 2 | + +| Outcome value (octet 2) | | | | | | | | | +|--------------------------------|---|---|---|---|---|---|---|--------------------------| +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Reserved | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | MS is accepted | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | MS is not accepted | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | MS is already registered | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Reserved | +| " | " | " | " | " | " | " | " | " | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Reserved | + +### 3.2.2.115 Global Call Reference + +The Global Call Reference IE contains a globally unique call identifier valid for the duration of the call, consisting of a Network ID, a Node ID and a Call Reference ID. + +This is a variable length information element coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Global Call Reference Identifier | | | | | | | | octet 3-n | + +The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet. + +The Global Call Reference Identifier field is coded as the LCLS Global Call Reference Identifier as specified in 3GPP TS 29.205. + +### 3.2.2.116 LCLS-Configuration + +This information element indicates the LCLS connection preference that shall persist in the BSS while local switching is established. + +The information element has a fixed length of two octets and is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|--------------------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | LCLS-Configuration | | | | octet 2 | + +Bits 1 to 4 of octet 2 contain the LCLS-Configuration field indicating the requested LCLS connection preference on a call leg basis. + +The LCLS-Configuration field is coded as follows: + +Bit + +**4 3 2 1** + +| | | +|---------|-------------------------------------------------------------------------------------------------------------------------| +| 0 0 0 0 | Connect both-way | +| 0 0 0 1 | Connect both-way and bi-cast UL to the core network | +| 0 0 1 0 | Connect both-way and send access DL from the core network | +| 0 0 1 1 | Connect both-way and send access DL from the core network, block local DL user data | +| 0 1 0 0 | Connect both-way and bi-cast UL to the core network with send access DL from the core network | +| 0 1 0 1 | Connect both-way and bi-cast UL to the core network with send access DL from the core network, block local DL user data | + +All other values are reserved for future use. + +For details of the different LCLS configuration values, see sub-clause 3.1.33.2.2. + +If the requested LCLS configuration is not supported in BSS this shall be indicated via the LCLS-BSS-Status IE, see sub-clause 3.2.2.119. + +### 3.2.2.117 LCLS-Connection-Status-Control + +This information element indicates the requested LCLS connection status for a call leg associated to a local call in the BSS to, e.g. establish local switching, do not establish local switching or release an already established locally switched call. + +The information element has a fixed length of two octets and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|--------------------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | LCLS-Connection-Status-Control | | | | | +| | | | | | | | | octet 2 | + +Bits 1 to 4 of octet 2 contain the LCLS-Connection-Status-Control field indicating the requested LCLS connection status on a call leg basis. + +The LCLS-Connection-Status-Control field is coded as follows: + +Bit + +**4 3 2 1** + +| | | +|-----------------------------------------------|--------------------------------------------| +| 0 0 0 0 | Connect | +| 0 0 0 1 | Do not connect | +| 0 0 1 0 | Release LCLS | +| 0 0 1 1 | Bi-cast UL at Handover | +| 0 1 0 0 | Bi-cast UL and receive DL data at Handover | +| All other values are reserved for future use. | | + +### 3.2.2.118 LCLS-Correlation-Not-Needed + +This information element indicates that call leg correlation is not needed in the BSS. + +The information element has a fixed length of one octet and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | + +### 3.2.2.119 LCLS-BSS-Status + +This information element indicates the LCLS connection status for a call leg in the BSS. + +The information element has a fixed length of two octets and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|-----------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | LCLS-BSS-Status | | | | | +| | | | | | | | | octet 2 | + +Bits 1 to 4 of octet 2 contain the LCLS-BSS-Status field indicating the LCLS connection status on a call leg basis. + +The LCLS-BSS-Status field is coded as follows: + +| Bit | | | +|----------------|--|------------------------------------------------------------| +| 4 3 2 1 | | | +| 0 0 0 0 | | Call not yet locally switched | +| 0 0 0 1 | | Call not possible to be locally switched | +| 0 0 1 0 | | Call is no longer locally switched | +| 0 0 1 1 | | Requested LCLS configuration is not supported | +| 0 1 0 0 | | Call is locally switched with requested LCLS configuration | + +All other values are reserved for future use. + +### 3.2.2.120 LCLS-Break-Request + +This information element indicates a request to break the locally switched call. + +The information element has a fixed length of one octet and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | + +### 3.2.2.121 CSFB Indication + +This information element indicates that the connection was established as a result of a CSFB procedure. + +The information element has a fixed length of one octet and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | + +### 3.2.2.122 CS to PS SRVCC + +This information element indicates that CS to PS SRVCC operation is permitted for this particular connection. + +The information element has a fixed length of one octet and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | + +### 3.2.2.123 Source eNB to target eNB transparent information (E-UTRAN) + +This information element is defined as a general container for passing eNB specific information transparently through the core network from BSS to eNB when CS to PS SRVCC to E-UTRAN is performed. + +| | | | | | | | | | +|--------------------------------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | +| Length | | | | | | | | octet 2 | +| Source eNB to target eNB transparent information | | | | | | | | octet 3-n | + +The Source eNB to target eNB transparent information field is encoded as the *Source eNB to Target eNB Transparent Container* IE as defined in 3GPP TS 36.413. + +### 3.2.2.124 CS to PS SRVCC Indication + +This information element indicates a CS to PS SRVCC to E-UTRAN or to UTRAN (HSPA) is required. + +The information element has a fix length of one octet and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | + +### 3.2.2.125 CN to MS transparent information + +This information element is defined as a general container for passing CN specific information transparently through the BSS from the CN to the MS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------|---|---|---|---|---|---|---|------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| NONCE | | | | | | | | octet 3-18 | +| ATGW transfer details | | | | | | | | octet 19-n | + +NONCE field is encoded as the *NONCEMSC* IE as defined in 3GPP TS 33.102. + +ATGW transfer details field is encoded as the *ATGW transfer details* IE as defined in 3GPP TS 24.237. + +### 3.2.2.126 Selected PLMN ID + +This information element provides the MSC with the PLMN ID selected by a mobile station supporting network sharing when network sharing is in use in a cell. + +The information element has a fixed length of four octets and is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-----------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| MCC dig 2 | | | | MCC dig 1 | | | | octet 2 | +| MNC dig 3 | | | | MNC dig 3 | | | | octet 3 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 4 | + +NOTE: The MCC and MNC value field is coded as specified within 3GPP TS 24.008 [6]. + +### 3.2.2.127 Last used E-UTRAN PLMN ID + +This information element provides the BSS with the last used E-UTRAN PLMN used by a CSFB MS before CSFB took place. This information element can help to redirect the MS back to the last used E-UTRAN PLMN by selecting the suitable dedicated target E-UTRAN frequencies/cells if applicable. + +The information element has a fixed length of four octets and is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-----------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| MCC dig 2 | | | | MCC dig 1 | | | | octet 2 | +| MNC dig 3 | | | | MNC dig 3 | | | | octet 3 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 4 | + +NOTE: The MCC and MNC value field is coded as specified within 3GPP TS 24.008 [6]. + +### 3.2.2.128 Old Location Area Identification + +This information element provides the BSS with the old Location Area Identification (LAI) as reported by the MS in the initial Layer 3 message. It is used in MOCN and GWCN configurations for network sharing. + +The information element has a fixed length of six octets and is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|--------------------|---|---|---|-----------|---|---|---|---------|--|--|--|--| +| Element identifier | | | | | | | | octet 1 | | | | | +| MCC dig 2 | | | | MCC dig 1 | | | | octet 2 | | | | | +| MNC dig 3 | | | | MNC dig 3 | | | | octet 3 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 4 | | | | | +| LAC | | | | | | | | octet 5 | | | | | +| LAC cont. | | | | | | | | octet 6 | | | | | + +The MCC, MNC and LAC value fields are coded as specified within 3GPP TS 24.008 [6]. + +### 3.2.2.129 Attach Indicator + +This information element provides the BSS with the information of an ongoing IMSI attach for a given mobile station. It is used in MOCN and GWCN configurations for network sharing. + +The information element has a fix length of one octet and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | + +### 3.2.2.130 Selected Operator + +This information element identifies the BSS selected CN operator for a given mobile station (IMSI). It is used in MOCN and GWCN configurations for network sharing. + +The information element has a fixed length of four octets and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|-----------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| MCC dig 2 | | | | MCC dig 1 | | | | octet 2 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 3 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 4 | + +The MCC and MNC value fields are coded as specified within 3GPP TS 24.008 [6]. + +### 3.2.2.131 PS Registered Operator + +This information element identifies the serving CN operator for a given mobile station (IMSI) in the PS domain. It is used in MOCN and GWCN configurations for network sharing. + +The information element has a fixed length of four octets and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|-----------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| MCC dig 2 | | | | MCC dig 1 | | | | octet 2 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 3 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 4 | + +The MCC and MNC value fields are coded as specified within 3GPP TS 24.008 [6]. + +### 3.2.2.132 CS Registered Operator + +This information element identifies the serving CN operator for a given mobile station (IMSI) in the CS domain. It is used in MOCN and GWCN configurations for network sharing. + +The information element has a fixed length of four octets and is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|-----------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| MCC dig 2 | | | | MCC dig 1 | | | | octet 2 | +| MNC dig 3 | | | | MCC dig 3 | | | | octet 3 | +| MNC dig 2 | | | | MNC dig 1 | | | | octet 4 | + +The MCC and MNC value fields are coded as specified within 3GPP TS 24.008 [6]. + +### 3.2.2.133 Temporary logical link Identity (TLLI) + +This information element is defined as a general container for passing information transparently between BSSs via the MSC. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| TLLI | | | | | | | | octet 2-5 | + +The TLLI octets are coded as the value part of the TLLI information element in 3GPP TS 44.018 [32], not including 3GPP TS 44.018 IEI. + +### 3.2.2.134 Multilateration Timing Advance + +This information element is defined as a general container for passing information transparently between BSSs via the MSC. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|----------|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| spare | | | | | | MTA High | | octet 2 | +| MTA Low | | | | | | | | octet 3 | + +The MTA field is coded according to the value part of the Multilateration Timing Advance information element described in 3GPP TS 49.031 [19a] (i.e. not including 3GPP TS 49.031 IEI). + +### 3.2.2.135 MS Synchronization Accuracy + +This information element is defined as a general container for passing information transparently between BSSs via the MSC. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|-----------------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| spare | | | | MS Synchronization Accuracy | | | | octet 2 | + +The MS Synchronization Accuracy field is coded according to the value part of the MS Synchronization Accuracy information element described in 3GPP TS 49.031 [19a] (i.e. not including 3GPP TS 49.031 IEI). + +### 3.2.2.136 BTS Reception Accuracy Level + +This information element is defined as a general container for passing information transparently between BSSs via the MSC. + +It is coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|------------------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| spare | | | | BTS Reception Accuracy Level | | | | octet 2 | + +The BTS Reception Accuracy Level field is coded according to the value part of the BTS Reception Accuracy Level information element described in 3GPP TS 49.031 [19a] (i.e. not including 3GPP TS 49.031 IEI). + +### 3.2.2.137 Random ID + +This information element is defined as a general container for passing information transparently between BSSs via the MSC. It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Random ID – Low | | | | | | | | octet 2 | +| Random ID – High | | | | | | | | octet 3 | + +When a non-serving BSS receives a Random ID from a MS during the radio access part of the MTA procedure performed using the Extended Access Burst method (see 3GPP TS 44.018 [32] and 3GPP TS 44.060) it forwards it to the serving BSS transparently via the MSC (see sub-clause 3.2.2.69). It allows the serving BSS to identify the applicable SCCP connection between the BSS and the serving SMLC (see 3GPP TS 49.031 [19a] and 3GPP TS 44.031). + +### 3.2.3 Signalling Field Element Coding + +The coding rules for signalling field elements are the same as the signalling element coding rules which are defined in sub-clause 3.2.2. + +Signalling field elements shall always include a Field Length indicator. A Field Length indicator with a value of zero shall not be considered as an error. + +| Field Element Identifier Coding | Field Element name | Reference | +|---------------------------------|----------------------------------------------------|-----------| +| 0000 0001 | Extra information | 3.2.3.1 | +| 0000 0010 | Current Channel Type 2 | 3.2.3.2 | +| 0000 0011 | Target cell radio information | 3.2.3.3 | +| 0000 0100 | GPRS Suspend information | 3.2.3.4 | +| 0000 0101 | MultiRate configuration information | 3.2.3.5 | +| 0000 0110 | Dual Transfer Mode information | 3.2.3.6 | +| 0000 0111 | Inter RAT Handover Info | 3.2.3.7 | +| 0000 1000 | cdma2000 Capability Information | 3.2.3.8 | +| 0000 1001 | Downlink Cell Load Information | 3.2.3.9 | +| 0000 1010 | Uplink Cell Load Information | 3.2.3.10 | +| 0000 1011 | Cell Load Information Group | 3.2.3.11 | +| 0000 1100 | Cell Load Information | 3.2.3.12 | +| 0000 1101 | PS Indication | 3.2.3.13 | +| 0000 1110 | DTM Handover Command Indication | 3.2.3.14 | +| 1111 1110 | D-RNTI | 3.2.3.15 | +| 0000 1111 | IRAT Measurement Configuration | 3.2.3.16 | +| 0001 0000 | Source Cell ID | 3.2.3.17 | +| 0001 0001 | IRAT Measurement Configuration (extended E-ARFCNs) | 3.2.3.18 | + +All other values are for future use. + +#### 3.2.3.1 Extra information + +This field element provides a general flag mechanism that allows the old BSS to indicate to the new BSS flag information. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|---------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| | | | | | | | | octet 3 | + +Octet 2 is a binary indication of the length of the rest of the field element. + +Octet 3 is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 3 | +|-------|---|---|---|---|---------|-----|------|---------| +| spare | | | | | UE-prob | lcs | prec | | + +Bit 8 to 4 are flags that indicate no information. + +prec = Pre-emption Recommendation: + +- 0 The old BSS recommends that this allocation request should not cause a pre-emption an existing connection; +- 1 The old BSS recommends that this allocation request is allowed to preempt an existing connection based on the information supplied in the Priority information element, if available. + +In the case the "prec" bit is not present or the Extra Information field element is not present then the new BSS should run pre-emption as specified by the Priority information element, if available. + +In the case where the Priority information element is not present in the request then the "prec" element, if present, shall be ignored. + +lcs = Location Services (LCS) information: + +- 0 No ongoing LCS procedure; +- 1 An ongoing LCS procedure was interrupted by handover. The new BSS may notify the SMLC when the handover is completed. + +UE-prob = support of handover to UMTS for this MS: + +- 0 This MS supports handover to UMTS; +- 1 This MS does not support handover to UMTS. + +### 3.2.3.2 Current Channel type 2 + +This Field Element contains a description of the channel allocated to the MS. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|---------| +| Field Element identifier | | | | | | | | | +| Length | | | | | | | | octet 2 | +| Channel mode | | | | | | | | octet 3 | +| Channel field | | | | | | | | octet 4 | + +The channel mode field is coded as follows: + +| Bit | | +|------|----------------------------------------| +| 4321 | | +| 0000 | signalling only | +| 0001 | speech (full rate or half rate) | +| 0110 | data, 14.5 kbit/s radio interface rate | +| 0011 | data, 12.0 kbit/s radio interface rate | +| 0100 | data, 6.0 kbit/s radio interface rate | +| 0101 | data, 3.6 kbit/s radio interface rate | +| 1111 | is reserved | + +All other values indicate that no information is provided. + +Bits 8 to 5 are spare. + +The channel field is coded as follows: + +**Bit:** + +**4321** + +| | | +|------|------------------| +| 0001 | SDCCH | +| 1000 | 1 Full rate TCH | +| 1001 | 1 Half rate TCH | +| 1010 | 2 Full Rate TCHs | +| 1011 | 3 Full Rate TCHs | +| 1100 | 4 Full Rate TCHs | +| 1101 | 5 Full Rate TCHs | +| 1110 | 6 Full Rate TCHs | +| 1111 | 7 Full Rate TCHs | +| 0100 | 8 Full Rate TCHs | +| 0000 | is reserved | + +All other values indicate that no information is provided. + +Bits 8 to 5 are spare. + +### 3.2.3.3 Target cell radio information + +It is coded as follows: + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| | | | | | | | | octet 3 | + +Octet 2 is a binary indication of the length of the rest of the element. + +Octet 3 is coded as follows: + +| | | | | | | | | | +|-------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| RXLEV-NCELL | | | | | | | | octet 3 | + +Bit 8 to 7 is spare, set to 0 + +Bit 6 to 1 is the RXLEV-NCELL field. + +The RXLEV-NCELL field is coded as the binary representation of a value N. N corresponds according to the mapping defined in TS. 3GPP TS 45.008 to the received signal strength on the target cell. + +### 3.2.3.4 GPRS Suspend Information + +This Field Element contains the contents of the Gb interface SUSPEND ACK PDU. + +It is coded as follows: + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Gb interface TLLI IEI | | | | | | | | octet 3 | +| Length of TLLI | | | | | | | | octet 4 | +| TLLI | | | | | | | | octet 5-5+m | +| Gb interface RAI IEI | | | | | | | | octet 6+m | +| Length of RAI | | | | | | | | octet 7+m | +| RAI | | | | | | | | octet 7+m-n | +| Gb interface SRN IEI | | | | | | | | octet n+1 | +| Length of SRN | | | | | | | | octet n+2 | +| Suspend reference number | | | | | | | | octet n+3-p | + +The coding of the fields are not relevant to 3GPP TS 24.008. + +### 3.2.3.5 MultiRate configuration Information + +This Field Element contains a description of the multi-rate speech codec configuration currently used. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Rest of element coded as in 3GPP TS 44.018, not including 3GPP TS 44.018 element identifier or 3GPP TS 44.018 octet length value | | | | | | | | octet 3-n | + +### 3.2.3.6 Dual Transfer Mode information + +This Field Element contains information about a mobile in dual transfer mode. This information may be used for the target BSS to allocate the resources for the RR connection (e.g. TCH/H, TCH in an EGPRS transceiver). + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|-----------|---------|---------|---------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | | | EGPRS ind | STO ind | DTM ind | octet 3 | + +Octet Bit 1 is the dual transfer mode indicator. It indicates whether the MS is in dedicated mode or in dual transfer mode. This bit shall also be used in the case of handover to GERAN from another RAT to indicate the allocation of resources for the CS and PS domain in the old cell. It is coded as follows: + +| Bit | | +|----------|-------------------------------------------------------------------------------| +| 1 | | +| 0 | The MS has resources allocated exclusively for the CS domain in the old cell | +| 1 | The MS has resources allocated for both the CS and PS domains in the old cell | + +Bit 2 is the single timeslot operation indicator. It indicates whether the MS has a TCH/H and a PDCH/H; see 3GPP TS 45.002. It is coded as follows: + +| Bit | | +|----------|--------------------------------------------------------| +| 2 | | +| 0 | The MS is in multislot operation in the old cell | +| 1 | The MS is in single timeslot operation in the old cell | + +Bit 3 is the EGPRS indicator. It is coded as follows: + +| Bit | | +|----------|------------------------------------------------| +| 3 | | +| 0 | The MS has no TBF using E-GPRS in the old cell | +| 1 | The MS has a TBF using E-GPRS in the old cell | + +Bits 8 to 4 of octet 3 are spare. + +### 3.2.3.7 Inter RAT Handover Info + +The Inter RAT Handover Info information element is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|-----------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Inter RAT Handover Info | | | | | | | | octet 3-n | + +Octets 3-n are encoded as Inter RAT Handover Info as defined in 3GPP TS 25.331. + +### 3.2.3.8 cdma2000 Capability Information + +The cdma2000 Capability Information element is coded as follows: + +| | | | | | | | | | +|---------------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| cdma2000 capability information | | | | | | | | octet 3-n | + +Octets 3-n are encoded as octets 3-n of the cdma2000 Classmark Change message defined in 3GPP TS 44.018. + +### 3.2.3.9 Downlink Cell Load Information + +This field element contains information about the downlink traffic load of a cell during a handover procedure. It refers either to the source or target cell depending on the direction of the message containing the Information Element where this field element is present. It is coded as follows: + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Cell Load Information | | | | | | | | octet 3-n | + +The container structure and encoding of the *Cell Load Information* is defined in sub-clause 3.2.3.12. + +### 3.2.3.10 Uplink Cell Load Information + +This field element contains information about the uplink traffic load of a cell during a handover procedure. It refers either to the source or target cell depending on the direction of the message containing the Information Element where this field element is present. It is coded as follows: + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|-----------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Cell Load Information | | | | | | | | octet 3-n | + +The container structure and encoding of the *Cell Load Information* is defined in sub-clause 3.2.3.12. + +### 3.2.3.11 Cell Load Information Group + +This field element contains the load information of the source cell for either the Downlink or the Uplink or both as well as the source cell identifier the included cell load information corresponds to during a handover procedure. It is coded as follows: + +| | | | | | | | | | +|--------------------------------------|---|---|---|---|---|---|---|-------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Cell Identifier | | | | | | | | octet 3-n | +| Cell Load Information Group elements | | | | | | | | octet (n+1)-(n+m) | + +The *Cell Identifier* identifies the source cell. The structure and encoding of *Cell Identifier* is described in sub-clause 3.2.2.17. For a GERAN source cell, Cell identification discriminator = 0000. For a UTRAN source cell, Cell identification discriminator = 1100. + +The *Cell Load Information Group elements* field is made up of zero or more of the field elements listed below. + +| FIELD ELEMENT | REFERENCE | LEN | +|--------------------------------|-----------|-----| +| Downlink Cell Load Information | 3.2.3.9 | 8 | +| Uplink Cell Load Information | 3.2.3.10 | 8 | + +### 3.2.3.12 Cell Load Information + +This field element contains the load information of a specific (serving or target) cell for either the Downlink or the Uplink. It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------|---|---|---|---|---|---|---|---------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Cell Capacity Class Value | | | | | | | | octet 3 | +| Load Value | | | | | | | | octet 4 | +| RT Load Value | | | | | | | | octet 5 | +| NRT Load Information Value | | | | | | | | octet 6 | + +*Cell Capacity Class Value* is the value that classifies the cell capacity with regards to the other cells. It only indicates resources that are configured for traffic purposes. *Cell Capacity Class Value* may take binary coded integer values from and including 1 up to and including 100. Other values shall be considered as an error. Value 1 shall indicate the minimum cell capacity, and 100 shall indicate the maximum cell capacity. There should be linear relation between cell capacity and *Cell Capacity Class Value*. + +*Load Value* contains the total cell load relative to the maximum planned load. It is defined as the load percentage of the Cell Capacity Class. *Load Value* may take binary coded integer values from and including 0 up to and including 100. Other values shall be considered as an error. Value 0 shall indicate the minimum load, and 100 shall indicate the maximum load. *Load Value* should be measured on a linear scale. + +*RT Load Value* indicates in percents the ratio of the load generated by Real Time traffic relative to the measured Load Value. Real Time traffic corresponds to the Conversational and Streaming traffic classes. *RT Load Value* may take binary coded integer values from and including 0 up to and including 100. Other values shall be considered as no information. + +*NRT Load Information Value* indicates the load situation on the cell for Non Real-Time traffic. Non Real-Time traffic corresponds to the Interactive and Background traffic classes. *NRT Load Information Value* may take binary coded integer values from and including 0 up to and including 3. Other values shall be considered as no information. The values shall be interpreted as: + +- Value 0: NRT load is low. +- Value 1: NRT load is medium. +- Value 2: NRT load is high. (Probability to admit a new user is low.) +- Value 3: NRT overload. (Probability to admit a new user is low, packets are discarded and the source is recommended to reduce the data flow.) + +### 3.2.3.13 PS Indication + +This field element indicates that a handover is part of a DTM Handover procedure. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|---------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| PS Indication Contents | | | | | | | | octet 3 | + +*PS Indication Contents* identifies a particular handover attempt for this MS. This shall be identical to the *CS Indication Contents* value in the corresponding *Source BSS to Target BSS Transparent Container* IE (see 3GPP TS 48.018). The choice of the contents of this field is implementation specific, with the requirement that consecutive handover attempts for the same mobile station shall not have the same *PS Indication Contents* value. + +### 3.2.3.14 DTM Handover Command Indication + +The presence of this field element in the *New BSS to Old BSS Information* IE indicates that an (RLC/MAC) DTM HANDOVER COMMAND message is included within the *Layer 3 Information* IE carried within the same BSSMAP message. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|---------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Spare | | | | | | | | octet 3 | + +### 3.2.3.15 D-RNTI + +This field element contains the Drift-Radio Network Temporary Identity used for identifying the MS during a handover via the Iur-g interface (see 3GPP TS 43.130). It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|--------------------------|---|---|---|--------------------|---|---|---|---------|--|--|--|--| +| Field Element identifier | | | | | | | | octet 1 | | | | | +| Length | | | | | | | | octet 2 | | | | | +| Spare | | | | D-RNTI (high part) | | | | octet 3 | | | | | +| D-RNTI (middle part) | | | | | | | | octet 4 | | | | | +| D-RNTI (low part) | | | | | | | | octet 5 | | | | | + +### 3.2.3.16 IRAT Measurement Configuration + +The *IRAT Measurement Configuration* IE is used to indicate to the BSS which frequency measurement results of the source RAT shall be collected after a successful inter-system handover. The *IRAT Measurement Configuration* IE is used by the source RAT to specify the E-UTRA frequencies for which the corresponding EARFCN is less than 65535 to be reported back to the source RAT (each of them associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements should last before triggering a *HO Report* for unnecessary handover to another RAT. + +NOTE 1: *HO Report* is defined in 3GPP TS 36.413 [57]. + +NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [59]. + +NOTE 3: E-UTRA frequencies corresponding to E-ARFCNs in the value range from 65536 to 262143 shall be indicated using the *IRAT Measurement Configuration (extended E-ARFCNs)* IE (see subclause 3.2.3.18); in such a case, E-UTRA frequencies corresponding to E-ARFCNs in the value range from 0 to 65534 (value 65535 is reserved and shall not be used) shall be indicated using the *IRAT Measurement Configuration* IE. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | +|--------------------------|---------------------------|---------------------|---|-----------------------|---|---|---|----------------|--|--|--|--|--|--| +| Field Element identifier | | | | | | | | octet 1 | | | | | | | +| Length | | | | | | | | octet 2 | | | | | | | +| Spare | RE
P_
QU
AN
T | REPORTING_THRESHOLD | | | | | | octet 3 | | | | | | | +| Measurement_Duration | | | | | | | | octet 4 | | | | | | | +| E-ARFCN | | | | | | | | octets 5-6 | | | | | | | +| Spare | | | | Measurement Bandwidth | | | | octet 7 | | | | | | | +| E-ARFCN | | | | | | | | octets 8-9 | | | | | | | +| Spare | | | | Measurement Bandwidth | | | | octet 10 | | | | | | | +| " | | | | | | | | " | | | | | | | +| E-ARFCN | | | | | | | | octets m-(m+1) | | | | | | | +| Spare | | | | Measurement Bandwidth | | | | octet m+2 | | | | | | | + +**REPORTING\_THRESHOLD:** defines the reporting threshold to be used for measurement results analysis according to REP\_QUANT. This threshold is used to compare against the measurement results received from the MS. It is a value between 0 and 63 encoded on 6 bits according to 3GPP TS 45.008 [58] sub-section 8.1.5.4. + +**REP\_QUANT:** indicates the measurement quantity for E-UTRAN cells coded as follows: 0=RSRP 1=RSRQ. + +**Measurement\_Duration:** defines (in seconds) how long the BSS shall collect the measurements results received from the MS after a successful inter-RAT handover. It is a number in binary representation ranging from 1 to 100 + +**E- ARFCN:** designates a specific E-UTRA frequency for which the target RAT should continue to collect the measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from 0 to 65534 (value 65535 is reserved and shall not be used). + +**Measurement Bandwidth:** defines the measurement bandwidth of the E-UTRA frequency signalled in the two previous octets. It is coded on 3 bits according to 3GPP TS 44.018 [32]. + +### 3.2.3.17 Source Cell ID + +The *Source Cell ID* IE is used to indicate to the BSS the identification of both the source cell and the source eNB, e.g. in the Unnecessary IRAT HO case (see *IRAT Measurement Configuration IE* description, subclause 3.2.3.16). + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|---|---|---|---|-----------------| +| Field Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Tracking Area Identity | | | | | | | | octet 3-7 | +| E-UTRAN CGI | | | | | | | | octet 8 - m | +| Global eNB ID | | | | | | | | octet (m+1) - n | + +**Tracking Area Identity:** Octets 3 to 7 contain the value part of the *Tracking Area Identity* IE defined in 3GPP TS 24.301, not including 3GPP TS 24.301 IEI. + +**E-UTRAN CGI:** Octets 8 - m contain the value part of the *E-UTRAN CGI* IE defined 3GPP TS 36.413 for the source cell. + +**Global eNB ID:** Octets (m+1) – n contain the value part of the *Global eNB ID* IE defined 3GPP TS 36.413 for the source eNB. + +### 3.2.3.18 IRAT Measurement Configuration (extended E-ARFCNs) + +The *IRAT Measurement Configuration (extended E-ARFCNs)* IE is used to indicate to the BSS which frequency measurement results of the source RAT shall be collected after a successful inter-system handover. The *IRAT Measurement Configuration (extended E-ARFCNs)* IE is used by the source RAT to specify the E-UTRA frequencies for which the corresponding E-ARFCN is greater than 65535 to be reported back to the source RAT (each of them associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements should last before triggering a *HO Report* for unnecessary handover to another RAT. + +NOTE 1: *HO Report* is defined in 3GPP TS 36.413 [57]. + +NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [59]. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | +|--------------------------|-----------|---------------------|---|-----------------------|---|---|---|----------------|--|--|--|--|--|--|--| +| Field Element identifier | | | | | | | | octet 1 | | | | | | | | +| Length | | | | | | | | octet 2 | | | | | | | | +| Spare | REP_QUANT | REPORTING_THRESHOLD | | | | | | octet 3 | | | | | | | | +| Measurement_Duration | | | | | | | | octet 4 | | | | | | | | +| E-ARFCN | | | | | | | | octets 5-6 | | | | | | | | +| E-ARFCN | Spare | | | Measurement Bandwidth | | | | octet 7 | | | | | | | | +| E-ARFCN | | | | | | | | octets 8-9 | | | | | | | | +| E-ARFCN | Spare | | | Measurement Bandwidth | | | | octet 10 | | | | | | | | +| " | | | | | | | | " | | | | | | | | +| E-ARFCN | | | | | | | | octets m-(m+1) | | | | | | | | +| E-ARFCN | Spare | | | Measurement Bandwidth | | | | octet m+2 | | | | | | | | + +**REPORTING\_THRESHOLD:** see subclause 3.2.3.16. + +**REP\_QUANT:** see subclause 3.2.3.16. + +**Measurement\_Duration:** see subclause 3.2.3.16 + +**E-ARFCN:** designates a specific E-UTRA frequency for which the target RAT should continue to collect the measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from 65536 to 262143, in which bit 8 octet m is the most significant bit while bit 7 octet (m+2) is the least significant bit. + +**Measurement Bandwidth:** see subclause 3.2.3.16. + +### 3.2.4 List of Timers in the BSSMAP Procedures + +| Timer | Title | Time | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| T1 | Time to receipt of BLOCKING ACKNOWLEDGE at the BSS | O&M | +| T2 | Reset guard period at the MSC | O&M | +| T4 | Time to receipt of RESET ACKNOWLEDGE at the BSS | O&M | +| T5 | Overload timer in the MSC, see sub-clause 3.1.12.1 | O&M | +| T6 | Overload timer in the MSC, see sub-clause 3.1.12.1 | O&M | +| T7 | Handover required periodicity | O&M | +| T8 | Time to receipt of successful handover information | O&M | +| T10 | Time to return of ASSIGNMENT COMPLETE; or ASSIGNMENT FAILURE from MS (note) | O&M | +| T11 | Maximum allowed queuing time for assignment | O&M | +| T12 | Time to receipt of RESET CIRCUIT ACKNOWLEDGE at the MSC | O&M | +| T14 | Maximum allowed queuing time for VGCS/VBS assignment | O&M | +| T13 | Reset guard period at the BSS | O&M | +| T16 | Time to receipt of RESET ACKNOWLEDGE at the MSC | O&M | +| T17 | Overload timer in the BSS, see sub-clause 3.1.12.1 | O&M | +| T18 | Overload timer in the BSS, see sub-clause 3.1.12.1 | O&M | +| T19 | Time to receipt of RESET CIRCUIT ACKNOWLEDGE at the BSS | O&M | +| T20 | Time to receipt of CIRCUIT GROUP BLOCKING ACKNOWLEDGE at the BSS | O&M | +| T21 | Time to receipt of BLOCKING ACKNOWLEDGE at the MSC | O&M | +| T22 | Time to receipt of CIRCUIT GROUP BLOCKING ACKNOWLEDGE at the MSC | O&M | +| T23 | Time to receipt at the old BSS of either i) a HANDOVER COMMAND (containing a (RR) HANDOVER COMMAND message) or ii) both a HANDOVER COMMAND or HANDOVER REQUIRED REJECT from the MSC and a PS HANDOVER REQUIRED ACK or PS HANDOVER REQUIRED NACK from the SGSN | O&M | +| T24 | Time to receipt of both the HANDOVER REQUEST and PS HANDOVER REQUEST messages at the new BSS for DTM Handover | O&M
(Note 2) | +| T25 | Internal Handover Required guard time | O&M | +| Tqho | Maximum allowed queuing time for handover | O&M | +| Tast | Time to send assignment status of VGCS/ VBS resources to the MSC | O&M | +| Trmsc | Time to receipt of RESET IP RESOURCE ACKNOWLEDGE at the MSC | O&M | +| Trbss | Time to receipt of RESET IP RESOURCE ACKNOWLEDGE at the BSS | O&M | + +NOTE 1: T10 is not the same as T3107 as defined in 3GPP TS 24.008. +NOTE 2: T23 shall be longer than T24 + +## 3.3 SDL Representation Of The Procedures At The BSS + +The SDL diagrams may be inserted at a later stage after updating and carefully checking of consistency with the main text. + +## 4 Broadcast Information Control Channel + +Information that is transferred in the Broadcast Control Channel is stored locally at the BSS. The scheduling of this information on the BCCH is controlled autonomously by the BSS. + +The set of information that is transmitted in the BCCH is derived locally or downloaded to the BSS via the BSS Operation and Maintenance Application Part. + +## 5 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Base Station System (BSS):** equipment which is accessed through the interface defined in the 3GPP TS 08-series. It contains the functionality described in 3GPP TS 48.002, and supports one or more cells. See 3GPP TS 41.004. + +**Base Station System Application Part (BSSAP):** subsystem that contains the process dealing with radio resource control and management known as the Base Station System Management Application Part (BSSMAP) and transparent transfer of call control and mobility management information known as the Direct Transfer Application Part (DTAP). The BSSAPs at the BSS and the MSC are connected by means of SCCP connections. + +**Base Station System Management Application Part (BSSMAP):** process within the BSS that controls radio resources in response to instructions from the MSC. + +**cell load based handover:** takes place in order to avoid congestion in the old cell by handing traffic off to another cell, typically less loaded. A cell load based handover is initiated with the handover cause set to "reduce load in serving cell". + +**directed retry:** process of assigning a Mobile Station to a TCH in a cell other than the serving cell, e.g. in situations of congestion. It is triggered by the assignment procedure and employs internal or external handover procedures. + +**Direct Transfer Application Part (DTAP):** process which allows the direct transfer of messages between individual MSs and the MSC with no interpretation of layer 3 information at the BSS. + +**IP based user plane interface is supported:** The related nodes support and can set up connections over an IP based user plane if appropriate. That is, PCM over IP or compressed speech over IP is supported over the user plane. + +**internal handover:** takes place between channels on a cell or cells controlled by a single BSS. This handover operates without reference to the MSC (although the MSC will be informed on completion). Handovers of this type in one cell are called internal intra cell handovers and between cells are called internal inter cell handovers. + +Handovers between channels on the same cell or between cells on the same BSS which are controlled by the MSC are external handovers and use identical procedures to those for inter-BSS handovers. + +**intersystem handover:** takes place between different radio access systems (e.g. GSM BSS and UTRAN or GSM BSS and cdma2000 RAN or GSM BSS and E-UTRAN (CS to PS SRVCC to E-UTRAN)). + +**Terrestrial resource:** Resource related to a TDM or an IP based connection for the user plane. + +**VGCS/VBS call controlling SCCP connection:** is an SCCP connection which supports the signalling for call SETUP of a VGCS/VBS call and the signalling for uplink control of a VGCS call. One of these connections is needed to support each instance of a VGCS/VBS call within a BSS. + +**VGCS/VBS resource controlling SCCP connection:** is an SCCP connection which supports the allocation of resources for a VGCS/VBS call. One or more of these connections is needed to support each instance of a VGCS/VBS call. The exact number of these SCCP connections is equal to the number of cells to which the VGCS/VBS call is to be supported or in case of A-interface sharing equal to the number of BSCs involved in the VGCS/VBS call. + +## 6 List of diagrams + +| Figure | Title | +|--------------|------------------------------------------------------------------| +| 1 | Signalling protocol reference model | +| 2 | Assignment | +| 3 | Handover execution | +| 4 | Handover required indication | +| 5 | Handover resource allocation | +| 6 | Release | +| 7 | Release due to reason at the BSS | +| 8 (not used) | | +| 9 | Classmark updating | +| 10 | Blocking of terrestrial circuits | +| 11 | Reset | +| 12 | Resource indication | +| 13 | Handover candidate enquiry | +| 14 | Flow control | +| 15 | Paging | +| 16 | Overview of handover procedure between two BSS's on the same MSC | +| 17 | Cipher mode control | +| 18 | SAPI "n" rejection | +| 19 | Load indication | +| 20 | SUCCESSFUL UPLINK ALLOCATION | +| 21 | UNSUCCESSFUL UPLINK ALLOCATION | +| 22 | UPLINK RELEASE INDICATION | +| 23 | UPLINK SEIZE COMMAND | +| 24 | UPLINK RELEASE COMMAND | +| 25 | Blocking of terrestrial circuits, MSC initiated | +| 26 | Circuit re-selection | +| 27 | Internal Handover procedure | +| 28 | Rerouting | + +![Figure 1: SIGNALLING PROTOCOL REFERENCE MODEL. A diagram showing the protocol stack for the A-interface between a BSS and an MSC. The stack consists of five layers: PHYSICAL, MTP, SCCP, BSSAP, and an upper layer containing DTAP, BSS MAP, Distribution Function, and BSS OMAP. On the BSS side, BSSAP connects to other processes and air interface equipment. On the MSC side, BSSAP connects to other applications like call control and O&M. A note at the bottom states that X.25 can be used for transferring O and M information.](5d819f259411162c4e3371915818ae22_img.jpg) + +**Terminology:** + +- DTAP - Direct Transfer Application Part +- BSSMAP - BSS Management Application Part +- BSS OMAP - BSS Operation and Maintenance Application Part +- SCCP - Signalling Connection and Control Part +- MTP - Message Transfer Part +- BSS - Base Station System +- MSC - Mobile services Switching Centre + +**NOTE:** X.25 can be used for transferring O and M information + +Figure 1: SIGNALLING PROTOCOL REFERENCE MODEL. A diagram showing the protocol stack for the A-interface between a BSS and an MSC. The stack consists of five layers: PHYSICAL, MTP, SCCP, BSSAP, and an upper layer containing DTAP, BSS MAP, Distribution Function, and BSS OMAP. On the BSS side, BSSAP connects to other processes and air interface equipment. On the MSC side, BSSAP connects to other applications like call control and O&M. A note at the bottom states that X.25 can be used for transferring O and M information. + +Figure 1: SIGNALLING PROTOCOL REFERENCE MODEL + +![Figure 2: ASSIGNMENT. A sequence diagram showing the assignment procedure between a Mobile Station (MS), Base Station System (BSS), and Mobile Services Switching Centre (MSC). The sequence is: MSC sends ASSIGNMENT REQUEST to BSS; BSS sends ASSIGNMENT COMMAND to MS; MS sends ASSIGNMENT COMPLETE to BSS; BSS sends ASSIGNMENT COMPLETE to MSC.](700f2fb63fbb87c933cd81ca42fb890f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note over BSS, MSC: ASSIGNMENT + MSC->>BSS: ASSIGNMENT REQUEST + BSS->>MS: ASSIGNMENT COMMAND + MS->>BSS: ASSIGNMENT COMPLETE + BSS->>MSC: ASSIGNMENT COMPLETE + +``` + +Figure 2: ASSIGNMENT. A sequence diagram showing the assignment procedure between a Mobile Station (MS), Base Station System (BSS), and Mobile Services Switching Centre (MSC). The sequence is: MSC sends ASSIGNMENT REQUEST to BSS; BSS sends ASSIGNMENT COMMAND to MS; MS sends ASSIGNMENT COMPLETE to BSS; BSS sends ASSIGNMENT COMPLETE to MSC. + +Figure 2 + +![Figure 3: HANDOVER EXECUTION. A sequence diagram showing the handover execution procedure between a Mobile Station (MS), Base Station System (BSS), and Mobile Services Switching Centre (MSC). The sequence is: MSC sends HANDOVER COMMAND to BSS; BSS sends HANDOVER COMMAND to MS; MSC sends CLEAR COMMAND to BSS. A note indicates that a timer T8 is started to protect the overall procedure.](09cef6267096187ea2ec3fa61909d695_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note over BSS, MSC: HANDOVER EXECUTION + MSC->>BSS: HANDOVER COMMAND + BSS->>MS: HANDOVER COMMAND + Note right of BSS: note + MSC->>BSS: CLEAR COMMAND + +``` + +Figure 3: HANDOVER EXECUTION. A sequence diagram showing the handover execution procedure between a Mobile Station (MS), Base Station System (BSS), and Mobile Services Switching Centre (MSC). The sequence is: MSC sends HANDOVER COMMAND to BSS; BSS sends HANDOVER COMMAND to MS; MSC sends CLEAR COMMAND to BSS. A note indicates that a timer T8 is started to protect the overall procedure. + +NOTE: A timer T8 is started to protect the overall procedure. + +Figure 3 + +![Sequence diagram titled 'HANDOVER REQUIRED INDICATION' showing interactions between MS, BSS, and MSC. The BSS sends two 'HANDOVER REQUIRED' messages to the MSC, and the MSC responds with a 'HANDOVER COMMAND'.](728a02fe4a04e7f91835147194997cd4_img.jpg) + +**HANDOVER REQUIRED INDICATION** + +The diagram shows three lifelines: MS, BSS, and MSC. The BSS lifeline has a vertical bar labeled 'T7' with '+' signs above and below it. The sequence of messages is: 1. BSS to MSC: HANDOVER REQUIRED (solid line with arrow). 2. BSS to MSC: HANDOVER REQUIRED (solid line with arrow). 3. MSC to BSS: HANDOVER COMMAND (dashed line with arrow). + +Sequence diagram titled 'HANDOVER REQUIRED INDICATION' showing interactions between MS, BSS, and MSC. The BSS sends two 'HANDOVER REQUIRED' messages to the MSC, and the MSC responds with a 'HANDOVER COMMAND'. + +Figure 4 + +![Sequence diagram titled 'HANDOVER RESOURCE ALLOCATION' showing interactions between MS, BSS, and MSC. The MSC sends a 'HANDOVER REQUEST' to the BSS, which responds with 'HANDOVER REQUEST ACKNOWLEDGE'. The MS sends '(HANDOVER COMPLETE)' to the BSS, which then sends 'HANDOVER COMPLETE' to the MSC and a 'note'.](8cbda1d7454ec4dfa612ae7cf5afac7d_img.jpg) + +**HANDOVER RESOURCE ALLOCATION** + +The diagram shows three lifelines: MS, BSS, and MSC. The sequence of messages is: 1. MSC to BSS: HANDOVER REQUEST (solid line with arrow). 2. BSS to MSC: HANDOVER REQUEST ACKNOWLEDGE (solid line with arrow). 3. MS to BSS: (HANDOVER COMPLETE) (solid line with arrow). 4. BSS to MSC: HANDOVER COMPLETE (solid line with arrow). 5. BSS lifeline: note (text below a horizontal line). + +Sequence diagram titled 'HANDOVER RESOURCE ALLOCATION' showing interactions between MS, BSS, and MSC. The MSC sends a 'HANDOVER REQUEST' to the BSS, which responds with 'HANDOVER REQUEST ACKNOWLEDGE'. The MS sends '(HANDOVER COMPLETE)' to the BSS, which then sends 'HANDOVER COMPLETE' to the MSC and a 'note'. + +NOTE: The instant of generation of the Handover Complete is described in the text of the present document. + +Figure 5 + +![Sequence diagram titled 'RELEASE' showing interactions between MS, BSS, and MSC. The MSC sends 'CLEAR COMMAND' and 'CLEAR COMPLETE' to the BSS. The BSS sends 'CHAN. RELEASE' to the MS. The MS sends 'L2 msg (DISC)' to the BSS, which responds with 'L2 msg (UA)'.](eb5c5bacf91c6062b2d5ba64a50b1a43_img.jpg) + +**RELEASE** + +The diagram shows three lifelines: MS, BSS, and MSC. The sequence of messages is: 1. MSC to BSS: CLEAR COMMAND (solid line with arrow). 2. MSC to BSS: CLEAR COMPLETE (solid line with arrow). 3. BSS to MS: CHAN. RELEASE (solid line with arrow). 4. MS to BSS: L2 msg (DISC) (solid line with arrow). 5. BSS to MS: L2 msg (UA) (solid line with arrow). + +Sequence diagram titled 'RELEASE' showing interactions between MS, BSS, and MSC. The MSC sends 'CLEAR COMMAND' and 'CLEAR COMPLETE' to the BSS. The BSS sends 'CHAN. RELEASE' to the MS. The MS sends 'L2 msg (DISC)' to the BSS, which responds with 'L2 msg (UA)'. + +Figure 6 + +![Sequence diagram for RELEASE DUE TO REASON AT THE BSS](931bd52904f67b17796a38b47af51e30_img.jpg) + +RELEASE DUE TO REASON AT THE BSS + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of BSS: RELEASE DUE TO REASON AT THE BSS + BSS->>MSC: CLEAR REQUEST + MSC-->>BSS: CLEAR COMMAND + BSS->>MSC: CLEAR COMPLETE + BSS-->>MS: CHAN. RELEASE + MS->>BSS: L2 msg (DISC) + BSS-->>MS: L2 msg (UA) +``` + +This sequence diagram illustrates the 'RELEASE DUE TO REASON AT THE BSS' procedure. It involves three lifelines: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence starts with a message 'CLEAR REQUEST' from the BSS to the MSC. The MSC responds with 'CLEAR COMMAND' back to the BSS. The BSS then sends 'CLEAR COMPLETE' to the MSC. Next, the BSS sends 'CHAN. RELEASE' to the MS. The MS responds with 'L2 msg (DISC)' to the BSS, and the BSS replies with 'L2 msg (UA)' to the MS. + +Sequence diagram for RELEASE DUE TO REASON AT THE BSS + +Figure 7 + +Figure 8: (void) + +![Sequence diagram for CLASSMARK UPDATING](fa849f3297b46a8d257e718ba0720135_img.jpg) + +CLASSMARK UPDATING + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of BSS: CLASSMARK UPDATING + MS->>BSS: CLASSMARK CHANGE + BSS->>MSC: CLASSMARK UPDATE +``` + +This sequence diagram illustrates the 'CLASSMARK UPDATING' procedure. It involves three lifelines: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence starts with a message 'CLASSMARK CHANGE' from the MS to the BSS. The BSS then sends 'CLASSMARK UPDATE' to the MSC. + +Sequence diagram for CLASSMARK UPDATING + +Figure 9 + +![Sequence diagram for BLOCKING OF TERRESTRIAL CIRCUITS](8450f105f39b5cb87eddb44d739cb1b2_img.jpg) + +BLOCKING OF TERRESTRIAL CIRCUITS + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of BSS: BLOCKING OF TERRESTRIAL CIRCUITS + BSS->>MSC: BLOCK + MSC-->>BSS: BLOCK ACK + BSS->>MSC: UNBLOCK + MSC-->>BSS: UNBLOCK ACK +``` + +This sequence diagram illustrates the 'BLOCKING OF TERRESTRIAL CIRCUITS' procedure. It involves three lifelines: MS (Mobile Station), BSS (Base Station System), and MSC (Mobile Switching Center). The sequence starts with a message 'BLOCK' from the BSS to the MSC. The MSC responds with 'BLOCK ACK' back to the BSS. Then, the BSS sends 'UNBLOCK' to the MSC, and the MSC replies with 'UNBLOCK ACK' to the BSS. + +Sequence diagram for BLOCKING OF TERRESTRIAL CIRCUITS + +Figure 10 + +![Sequence diagram for RESET messages between BSS and MSC.](7109096552c3464c931b0b39109b9b41_img.jpg) + +Sequence diagram titled "RESET" showing interactions between BSS and MSC. The diagram includes lifelines for MS, BSS, and MSC. The sequence of messages is: 1. MSC sends a RESET message to BSS (indicated by a left-pointing arrow). 2. BSS sends a RESET ACK message to MSC (indicated by a right-pointing arrow). A timer T13 is shown on the BSS lifeline. 3. BSS sends another RESET message to MSC. 4. MSC sends a RESET ACK message to BSS (indicated by a left-pointing arrow). A timer T2 is shown on the MSC lifeline. + +Sequence diagram for RESET messages between BSS and MSC. + +Figure 11 + +![Sequence diagram for RESOURCE INDICATION messages between BSS and MSC.](739d9761cdbb47394f979141864a8de6_img.jpg) + +Sequence diagram titled "RESOURCE INDICATION" showing interactions between BSS and MSC. The diagram includes lifelines for MS, BSS, and MSC. The sequence of messages is: 1. MSC sends a RESOURCE REQUEST message to BSS (indicated by a left-pointing arrow). 2. BSS sends a RESOURCE INDICATION message to MSC (indicated by a right-pointing arrow). 3. A note on the BSS lifeline indicates a timeout (T). 4. BSS sends another RESOURCE INDICATION message to MSC (indicated by a right-pointing arrow). A plus sign (+) is shown on the BSS lifeline before the second message. + +Sequence diagram for RESOURCE INDICATION messages between BSS and MSC. + +Figure 12 + +![Sequence diagram for HANDOVER CANDIDATE ENQUIRY messages between BSS and MSC.](b61dbe0a8b7ddc6b7fa6550a7ff9d2df_img.jpg) + +Sequence diagram titled "HANDOVER CANDIDATE ENQUIRY" showing interactions between BSS and MSC. The diagram includes lifelines for MS, BSS, and MSC. The sequence of messages is: 1. MSC sends a HANDOVER CANDIDATE ENQUIRY message to BSS (indicated by a left-pointing arrow). 2. BSS sends a HANDOVER REQUIRED message to MSC (indicated by a right-pointing arrow). 3. BSS sends another HANDOVER REQUIRED message to MSC. 4. A note on the BSS lifeline indicates a timeout (T) with four vertical dots. 5. BSS sends a HANDOVER REQUIRED message to MSC. 6. BSS sends a HANDOVER CANDIDATE RESPONSE message to MSC. A bracket on the BSS lifeline groups the multiple HANDOVER REQUIRED messages. + +Sequence diagram for HANDOVER CANDIDATE ENQUIRY messages between BSS and MSC. + +Figure 13 + +NOTE: Receipt of the Handover Candidate Enquiry Message causes the generation of a Handover Required message for each of candidate MS. These are sent as connection oriented messages. When all Handover Required messages have been generated a global Handover Candidate Response message is returned. + +![Sequence diagram titled 'FLOW CONTROL' showing MS, BSS, and MSC lifelines. The diagram is split by a dashed line. Above the line, MSC sends OVERLOAD to BSS twice, with a note '(MSC overload)'. Below the line, BSS sends OVERLOAD to MSC twice, with a note '(BSS overload)'.](8c05782074bb11421b43f2d5d6799b62_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of BSS: (MSC overload) + MSC->>BSS: OVERLOAD + MSC->>BSS: OVERLOAD + Note left of BSS: (BSS overload) + BSS->>MSC: OVERLOAD + BSS->>MSC: OVERLOAD + +``` + +Sequence diagram titled 'FLOW CONTROL' showing MS, BSS, and MSC lifelines. The diagram is split by a dashed line. Above the line, MSC sends OVERLOAD to BSS twice, with a note '(MSC overload)'. Below the line, BSS sends OVERLOAD to MSC twice, with a note '(BSS overload)'. + +Figure 14 + +![Sequence diagram showing MS, BSS, and MSC lifelines. MSC sends PAGING to BSS, which then sends PAGING REQUEST TYPE 1, 2, 3 to MS. This sequence repeats once more.](b0b07599997175149ac03e26e3247c9a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + MSC->>BSS: PAGING + BSS->>MS: PAGING REQUEST TYPE 1, 2, 3 + MSC->>BSS: PAGING + BSS->>MS: PAGING REQUEST TYPE 1, 2, 3 + +``` + +Sequence diagram showing MS, BSS, and MSC lifelines. MSC sends PAGING to BSS, which then sends PAGING REQUEST TYPE 1, 2, 3 to MS. This sequence repeats once more. + +Figure 15 + +![Sequence diagram titled 'OVERVIEW OF THE HANDOVER PROCEDURE BETWEEN TWO BSS'S ON THE SAME MSC.' showing MS, BSS, MSC, BSS, and MS lifelines. The process involves HANDOVER REQUIRED, HANDOVER REQUEST, HANDOVER REQUEST ACK, HANDOVER COMMAND, HANDOVER ACCESS, HANDOVER DETECT, HANDOVER COMPLETE, CLEAR COMMAND, and CLEAR COMPLETE messages. A note indicates that the second BSS's 'Measurement Information Reported Continuously From Mobile' list is updated after HANDOVER COMPLETE.](b988d13a7e9ebb10a1df8e0957a15c51_img.jpg) + +``` + +sequenceDiagram + participant MS1 as MS + participant BSS1 as BSS + participant MSC + participant BSS2 as BSS + participant MS2 as MS + Note left of BSS1: Measurement Information Reported Continuously From Mobile + BSS1->>MSC: HANDOVER REQUIRED + MSC->>BSS2: HANDOVER REQUEST + BSS2->>MSC: HANDOVER REQUEST ACK + MSC->>BSS1: HANDOVER COMMAND + BSS1->>MS1: HANDOVER COMMAND + BSS2->>MS2: HANDOVER ACCESS + BSS2->>MSC: HANDOVER DETECT + BSS2->>MSC: HANDOVER COMPLETE + Note right of BSS2: Measurement Information Reported Continuously From Mobile + MSC->>BSS1: CLEAR COMMAND + BSS1->>MS1: CLEAR COMPLETE + BSS1->>MSC: CLEAR COMPLETE + +``` + +Sequence diagram titled 'OVERVIEW OF THE HANDOVER PROCEDURE BETWEEN TWO BSS'S ON THE SAME MSC.' showing MS, BSS, MSC, BSS, and MS lifelines. The process involves HANDOVER REQUIRED, HANDOVER REQUEST, HANDOVER REQUEST ACK, HANDOVER COMMAND, HANDOVER ACCESS, HANDOVER DETECT, HANDOVER COMPLETE, CLEAR COMMAND, and CLEAR COMPLETE messages. A note indicates that the second BSS's 'Measurement Information Reported Continuously From Mobile' list is updated after HANDOVER COMPLETE. + +NOTE: The Handover Complete message can be sent as soon as the BSS is certain that the MS has successfully been captured. + +Figure 16 + +![Sequence diagram for Cipher Mode Control. Lifelines: MS, BSS, MSC. The MSC sends a CIPHER MODE COMMAND to the BSS. The BSS then sends a CIPHER MODE COMMAND to the MS. The MS responds with a CIPHER MODE COMPLETE message to the BSS. Finally, the BSS sends a CIPHER MODE COMPLETE message to the MSC.](74b47701fe8a059c632b40e009c57a96_img.jpg) + +CIPHER MODE CONTROL + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + MSC->>BSS: CIPHER MODE COMMAND + BSS->>MS: CIPHER MODE COMMAND + MS->>BSS: CIPHER MODE COMPLETE + BSS->>MSC: CIPHER MODE COMPLETE +``` + +Sequence diagram for Cipher Mode Control. Lifelines: MS, BSS, MSC. The MSC sends a CIPHER MODE COMMAND to the BSS. The BSS then sends a CIPHER MODE COMMAND to the MS. The MS responds with a CIPHER MODE COMPLETE message to the BSS. Finally, the BSS sends a CIPHER MODE COMPLETE message to the MSC. + +Figure 17 + +![Sequence diagram for SAPI 'n' Rejection. Lifelines: MS, BSS, MSC. The MSC sends a DTAP MESSAGE 'SAPI in DLCI <> 0' to the BSS. A note is present on the BSS lifeline. The BSS then sends a 'SAPI "n" REJECT' message to the MSC.](8db92c2d49f464fdd3e01aad57bfda53_img.jpg) + +SAPI "n" REJECTION + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note left of BSS: note + MSC->>BSS: DTAP MESSAGE SAPI in DLCI <> 0 + BSS->>MSC: SAPI "n" REJECT +``` + +Sequence diagram for SAPI 'n' Rejection. Lifelines: MS, BSS, MSC. The MSC sends a DTAP MESSAGE 'SAPI in DLCI <> 0' to the BSS. A note is present on the BSS lifeline. The BSS then sends a 'SAPI "n" REJECT' message to the MSC. + +NOTE: The BSS or MS is not equipped for the SAPI request. + +Figure 18 + +![Sequence diagram for Load Indication. Lifelines: BSS, MSC, BSS. The first BSS sends a LOAD INDICATION message to the MSC. The MSC then sends a LOAD INDICATION message to the second BSS. The first BSS sends another LOAD INDICATION message to the MSC. The MSC then sends another LOAD INDICATION message to the second BSS.](0036103c276f2dbcea4dccf73e47a2ff_img.jpg) + +LOAD INDICATION + +``` +sequenceDiagram + participant BSS1 as BSS + participant MSC + participant BSS2 as BSS + BSS1->>MSC: LOAD INDICATION + MSC->>BSS2: LOAD INDICATION + BSS1->>MSC: LOAD INDICATION + MSC->>BSS2: LOAD INDICATION +``` + +Sequence diagram for Load Indication. Lifelines: BSS, MSC, BSS. The first BSS sends a LOAD INDICATION message to the MSC. The MSC then sends a LOAD INDICATION message to the second BSS. The first BSS sends another LOAD INDICATION message to the MSC. The MSC then sends another LOAD INDICATION message to the second BSS. + +Figure 19 + +![Sequence diagram for successful uplink allocation showing MS, BSS, and MSC interactions.](e002d1b87dc447584fd9829eac949a12_img.jpg) + +SUCCESSFUL UPLINK ALLOCATION + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note left of MS: + MS->>BSS: UPLINK FREE + BSS-->>MS: UPLINK FREE + Note left of MS: + MS->>BSS: UPLINK ACCESS + BSS->>MSC: UPLINK REQUEST + MSC-->>BSS: VGCS ACCESS GRANT + BSS-->>MS: BUSY + Note left of MS: + MS->>BSS: L2msq (SABM (Talk Ind)) + BSS-->>MS: L2msq (UA (Talk Ind)) + Note right of MSC: + MSC-->>BSS: UPLINK REQ ACK + BSS-->>MSC: UPLINK REQ CNF (Talk Ind) + +``` + +Sequence diagram for successful uplink allocation showing MS, BSS, and MSC interactions. + +Figure 20 + +![Sequence diagram for unsuccessful uplink allocation showing MS, BSS, and MSC interactions.](5ed662a589ef8a6d08d67ae2fd275216_img.jpg) + +UNSUCCESSFUL UPLINK ALLOCATION + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note left of MS: + MS->>BSS: UPLINK FREE + BSS-->>MS: UPLINK FREE + Note left of MS: + MS->>BSS: UPLINK ACCESS + BSS->>MSC: UPLINK REQUEST + MSC-->>BSS: VGCS ACCESS GRANT + BSS-->>MS: BUSY + Note left of MS: + MS->>BSS: L2msq (SABM (Talk Ind)) + BSS-->>MS: L2msq (UA (Talk Ind)) + Note right of MSC: + MSC-->>BSS: UPLINK REJ CMD + BSS-->>MS: DISC/DM + +``` + +Sequence diagram for unsuccessful uplink allocation showing MS, BSS, and MSC interactions. + +Figure 21 + +![Sequence diagram for uplink release showing MS, BSS, and MSC interactions.](1e8845a639705010d5cda27146b8827f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note left of MS: + MS->>BSS: UPLINK RELEASE + BSS->>MSC: UPLINK RELEASE IND + +``` + +Sequence diagram for uplink release showing MS, BSS, and MSC interactions. + +Figure 22 + +![Sequence diagram for Uplink Seize Command. Lifelines: MS, BSS, MSC. MSC sends UPLINK SEIZE CMD to BSS. BSS sends UPLINK FREE to MS. MS responds with UPLINK FREE, UPLINK FREE, and UPLINK BUSY.](31f5b6310f831ca3ea4f18453980c070_img.jpg) + +UPLINK SEIZE COMMAND + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note over BSS, MSC: UPLINK SEIZE COMMAND + MSC->>BSS: UPLINK SEIZE CMD + BSS->>MS: UPLINK FREE + MS-->>BSS: UPLINK FREE + MS-->>BSS: UPLINK FREE + MS-->>BSS: UPLINK BUSY +``` + +Sequence diagram for Uplink Seize Command. Lifelines: MS, BSS, MSC. MSC sends UPLINK SEIZE CMD to BSS. BSS sends UPLINK FREE to MS. MS responds with UPLINK FREE, UPLINK FREE, and UPLINK BUSY. + +Figure 23 + +![Sequence diagram for Uplink Release Command. Lifelines: MS, BSS, MSC. MSC sends UPLINK RELEASE CMD to BSS. BSS sends UPLINK FREE to MS. MS responds with UPLINK FREE and UPLINK FREE.](34fccd22313e0b3b2350c8689f2de9e2_img.jpg) + +UPLINK RELEASE COMMAND + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note over BSS, MSC: UPLINK RELEASE COMMAND + MSC->>BSS: UPLINK RELEASE CMD + BSS->>MS: UPLINK FREE + MS-->>BSS: UPLINK FREE + MS-->>BSS: UPLINK FREE +``` + +Sequence diagram for Uplink Release Command. Lifelines: MS, BSS, MSC. MSC sends UPLINK RELEASE CMD to BSS. BSS sends UPLINK FREE to MS. MS responds with UPLINK FREE and UPLINK FREE. + +Figure 24 + +BLOCKING OF TERRESTRIAL CIRCUITS, MSC INITIATED + +![Sequence diagram for Blocking of Terrestrial Circuits, MSC Initiated. Lifelines: MS, BSS, MSC. MSC sends BLOCK to BSS. BSS sends BLOCK ACK to MSC. MSC sends UNBLOCK to BSS. BSS sends UNBLOCK ACK to MSC.](af1c886ec10a6ff7100b60d0c2a47eb8_img.jpg) + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note over MS, BSS: BLOCKING OF TERRESTRIAL CIRCUITS, MSC INITIATED + MSC->>BSS: BLOCK + BSS->>MSC: BLOCK ACK + MSC->>BSS: UNBLOCK + BSS->>MSC: UNBLOCK ACK +``` + +Sequence diagram for Blocking of Terrestrial Circuits, MSC Initiated. Lifelines: MS, BSS, MSC. MSC sends BLOCK to BSS. BSS sends BLOCK ACK to MSC. MSC sends UNBLOCK to BSS. BSS sends UNBLOCK ACK to MSC. + +Figure 25 + +![Sequence diagram for Change Circuit. Lifelines: MS, BSS, MSC. MSC sends CHANGE CIRCUIT to BSS. BSS sends CHANGE CIRCUIT ACKNOWLEDGE to MSC.](52f7a3277fa444ec8818ec7328aa498e_img.jpg) + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + MSC->>BSS: CHANGE CIRCUIT + BSS->>MSC: CHANGE CIRCUIT ACKNOWLEDGE +``` + +Sequence diagram for Change Circuit. Lifelines: MS, BSS, MSC. MSC sends CHANGE CIRCUIT to BSS. BSS sends CHANGE CIRCUIT ACKNOWLEDGE to MSC. + +Figure 26 + +![Sequence diagram for Internal Handover between MS, BSS, and MSC.](14af2781d0bd19b98b10672b74daaca2_img.jpg) + +PROCEDURE INTERNAL HANDOVER + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of BSS: INTERNAL HANDOVER REQUIRED + BSS->>MSC: INTERNAL HANDOVER COMMAND + MSC->>BSS: HANDOVER COMMAND/ASSIGNMENT COMMAND + BSS->>MS: HANDOVER ACCESS/LAYER 2 ESTABLISHMENT + Note right of BSS: HANDOVER DETECT + MSC->>BSS: HANDOVER COMPLETE/ASSIGNMENT COMPLETE + Note right of BSS: HANDOVER +``` + +The diagram illustrates the Internal Handover procedure. It involves three lifelines: MS (Mobile Station), BSS (Base Station Subsystem), and MSC (Mobile Switching Center). The sequence of messages is as follows: 1. An internal message 'INTERNAL HANDOVER REQUIRED' is sent within the BSS. 2. The BSS sends an 'INTERNAL HANDOVER COMMAND' to the MSC. 3. The MSC responds with a 'HANDOVER COMMAND/ASSIGNMENT COMMAND' to the BSS. 4. The BSS sends a 'HANDOVER ACCESS/LAYER 2 ESTABLISHMENT' message to the MS. 5. An internal message 'HANDOVER DETECT' is sent within the BSS. 6. The MSC sends a 'HANDOVER COMPLETE/ASSIGNMENT COMPLETE' message to the BSS. 7. Finally, an internal message 'HANDOVER' is sent within the BSS. + +Sequence diagram for Internal Handover between MS, BSS, and MSC. + +Figure 27 + +![Sequence diagram for Rerouting between MS, BSS, MSC 1, and MSC 2.](3e87cc59cb02fbac8840c659c41f2645_img.jpg) + +REROUTING + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC1 as MSC 1 + participant MSC2 as MSC 2 + Note right of BSS: COMPLETE LAYER 3 INFORMATION + BSS->>MSC1: COMPLETE LAYER 3 INFORMATION + MSC1->>BSS: REROUTE COMMAND + Note right of BSS: COMPLETE LAYER 3 INFORMATION + BSS->>MSC2: COMPLETE LAYER 3 INFORMATION + MSC2->>BSS: REROUTE COMPLETE +``` + +The diagram illustrates the Rerouting procedure. It involves four lifelines: MS (Mobile Station), BSS (Base Station Subsystem), MSC 1 (Mobile Switching Center 1), and MSC 2 (Mobile Switching Center 2). The sequence of messages is as follows: 1. An internal message 'COMPLETE LAYER 3 INFORMATION' is sent within the BSS. 2. The BSS sends a 'COMPLETE LAYER 3 INFORMATION' message to MSC 1. 3. MSC 1 responds with a 'REROUTE COMMAND' to the BSS. 4. Another internal message 'COMPLETE LAYER 3 INFORMATION' is sent within the BSS. 5. The BSS sends a 'COMPLETE LAYER 3 INFORMATION' message to MSC 2. 6. MSC 2 responds with a 'REROUTE COMPLETE' message to the BSS. + +Sequence diagram for Rerouting between MS, BSS, MSC 1, and MSC 2. + +Figure 28 + +## Annex A (informative): Change History + +| Date | TSG# | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|-------|-----------|------|-----|-----|------------------------------------------------------------------|--------| +| 2015-12 | | | | | | Creation of Rel-13 version based on 12.2.0 | 13.0.0 | +| | GP-68 | GP-151120 | 0406 | 1 | | Enhancements to CS/PS coordination | 13.0.0 | +| 2016-02 | GP-69 | GP-160083 | 0407 | - | | Removal of enhancements to CS/PS coordination in shared networks | 13.1.0 | +| 2016-06 | GP-70 | GP-160401 | 0406 | 2 | B | Enhancements to CS/PS coordination | 13.2.0 | +| 2016-09 | RP-73 | RP-161394 | 0409 | - | F | Correction to CS/PS coordination in shared networks | 13.3.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | | | | | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2017-06 | RP-76 | RP-170923 | 0410 | 7 | B | Introduction of Multilateration | 14.1.0 | +| 2017-09 | RP-77 | RP-171594 | 0412 | 2 | F | Clarifying References to BTS Reception Accuracy Level IE | 14.2.0 | +| 2018-06 | RP-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/48_series/48014/raw.md b/marked/Rel-16/48_series/48014/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4b287ac4b61be5e08f706bb9b66ada222f18540b --- /dev/null +++ b/marked/Rel-16/48_series/48014/raw.md @@ -0,0 +1,138 @@ + + + + + + +# Contents + +- Foreword ..... 4 +- 1 Scope..... 5 +- 2 References..... 5 +- 3 Abbreviations ..... 6 +- 4 Definitions..... 6 + - 4.1 Definitions..... 6 + - 4.2 Symbols..... 6 +- 5 Layer 1 specification..... 6 + - 5.1 Physical configuration of the Gb interface..... 6 + - 5.2 Physical layer interface ..... 6 + - 5.3 Error rate ..... 7 + - 5.4 Provision of physical channels..... 7 +- Annex A (informative): Change History..... 8 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the physical layer on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface) and references layer 1 standards to be used on this interface. + +The protocol stack on the Gb interface is defined in the stage 2 3GPP TS 23.060. + +# --- 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.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [4] 3GPP TS 48.004: "Base Station System - Mobile-services Switching Centre (BSS-MSC) interface; Layer 1 specification". +- [5] FRF.1.2 (July 2000): "User-to-Network Interface (UNI) Implementation Agreement". +- [6] ITU-T Recommendation G.704 (Blue Book): "Synchronous frame structures used at 1 544, 6 312, 2 048, 8 488 and 44 736 kbit/s hierarchical levels". +- [7] ANSI T1.403-1999: "Network and Customer Installation Interfaces - DS1 - Electrical Interface". +- [8] Bellcore TR-NWT-001203 Issue 2 (December 1992): "Generic Requirements for the Switched DS1/Switched Fractional DS1 Service Capability From an ISDN Interface (SWF-DS1/ISDN)". +- [9] ITU-T Recommendation V.35: "Data transmission at 48 kilobits per second using 60-108 kHz group band circuits". +- [10] ITU-T Recommendation G.703: "Physical/electrical characteristics of hierarchical digital interfaces". +- [11] ITU-T Recommendation X.21: "Interface between Data Terminal Equipment and Data Circuit-terminating Equipment for synchronous operation on public data networks". +- [12] TIA/EIA-530-A: "High Speed 25-Position Interface for Data Terminal Equipment and Data Circuit-Terminating Equipment, Including Alternative 26-Position Connector (ANSI/TIA/EIA-530-A-92) (R98)". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and 3GPP TS 23.060, and the following apply: + +| | | +|-----|------------------------------------| +| DCE | Data Circuit-terminating Equipment | +| DTE | Data Terminal Equipment | +| FRF | Frame Relay Forum | + +# --- 4 Definitions + +## 4.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 22.060 and the following apply: + +**E1:** a four wire symmetrical digital transmission path carrying PCM signal at 2 048 kbit/s. + +**T1:** a four wire symmetrical digital transmission path carrying PCM signal at 1 544 kbit/s. + +## 4.2 Symbols + +For the purposes of the present document, the symbols given in 3GPP TS 23.060 apply. + +# --- 5 Layer 1 specification + +Since Frame Relay shall be used on the Gb interface for phase 1 of GPRS, see 3GPP TS 23.060, the present document refers to "The Frame Relay Forum User-to-Network Implementation Agreement (UNI)" which recommends physical layer interfaces to be used in conjunction with Frame Relay. + +## 5.1 Physical configuration of the Gb interface + +The detailed physical configuration of the Gb interface is subject to negotiation between operators and equipment providers and is out of the scope of the present document. + +**EXAMPLE:** Point-to-point physical lines or an intermediate Frame Relay network may be used. In the latter case, the two ends of the Gb interface may use different types of physical interfaces. + +## 5.2 Physical layer interface + +Each of the physical layer of the Gb interface shall conform to one of the following FRF 1.2 clauses. This does not mean that each BSS and SGSN equipment has to support all of these physical interfaces, it means that the supported physical interfaces shall be compliant with the corresponding clause of FRF 1.2. + +- a) clause 2.1.1: ANSI T1.403. +- b) clause 2.1.2: V.35, physical circuit and DTE/DCE interface clauses. +- c) clause 2.1.3: G.703. +- d) clause 2.1.4: G.704. +- e) clause 2.1.5: X.21. +- f) clause 2.1.6: TIA/EIA-530-A. +- g) clause 2.1.7: HSSI. + +The Gb interface may be multiplexed with the A interface on the same E1 (2 048 kbit/s), or T1 (1 544 kbit/s) digital path. In case of E1 interface, ITU-T Recommendation G.704 shall be applied according to FRF 1.2 and + +3GPP TS 48.004 as appropriate, and in case of T1 interface ANSI T1.403 shall be applied according to FRF 1.1 and 3GPP TS 48.004 as appropriate. + +In the case where multiple 64 kbit/s channels are used on an E1 (2048 kbit/s), digital path on the Gb interface, it is recommended to aggregate them into one nx64 kbit/s channel, see ITU-T Recommendation G.704, clause 5 and included clauses. In case where multiple 64 kbit/s channels are used on a T1 (1 544 kbit/s) digital path on the Gb interface, it is recommended to aggregate them into nx64kbit/s (where $2 \leq n \leq 24$ ) channel, see Bellcore TR-NWT-1203. This approach optimises the use of the available bandwidth by taking advantage of the statistical multiplexing at the upper layer. However, this approach requires that no slipping occurs between individual 64 kbit/s channels e.g. when passing through intermediate equipment between BSS and SGSN. + +## 5.3 Error rate + +The error rate experienced at the physical layer between the BSS and the SGSN shall be compatible with the operation of the upper layers. + +## 5.4 Provision of physical channels + +The physical channels on the Gb interface shall be permanently reserved by means of administrative procedures. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|----------|----|-----|-----------------------------------------|--------| +| January 2016 | - | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48016/08e8bbb2a063a3935a0c649b39ade125_img.jpg b/marked/Rel-16/48_series/48016/08e8bbb2a063a3935a0c649b39ade125_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab6f75a0bbfa3fbb97cc580be16c1ec0b702f107 --- /dev/null +++ b/marked/Rel-16/48_series/48016/08e8bbb2a063a3935a0c649b39ade125_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9af5f281344499c09cad3d277efb6bd3a398f526e4da80d5b46558627409dfd +size 14996 diff --git a/marked/Rel-16/48_series/48016/098802c99831a6a7d445310d5e874e16_img.jpg b/marked/Rel-16/48_series/48016/098802c99831a6a7d445310d5e874e16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..508135a389f7efbf06744b62c04ea6c40fe5a9bd --- /dev/null +++ b/marked/Rel-16/48_series/48016/098802c99831a6a7d445310d5e874e16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:144f12f5a8266a48763c4097141d59dc26fa8124e6849abada59a0d035a87a66 +size 24949 diff --git a/marked/Rel-16/48_series/48016/1a74cf06fd2a1f8dcf7932224b617c57_img.jpg b/marked/Rel-16/48_series/48016/1a74cf06fd2a1f8dcf7932224b617c57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64fb62f0a3e51d5e2465543e6d58441d69c0f853 --- /dev/null +++ b/marked/Rel-16/48_series/48016/1a74cf06fd2a1f8dcf7932224b617c57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56f96feea7569b6bbb45a17870822ec2c9a5d3a17b58d39329d0f6e67921bdec +size 9483 diff --git a/marked/Rel-16/48_series/48016/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/48_series/48016/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c439f5559c8df193d3d4f0c05b59efb892765b6a --- /dev/null +++ b/marked/Rel-16/48_series/48016/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc83d322beb47f740d626c7af91310ded763058b1c378818c59e86fd0deb563e +size 24592 diff --git a/marked/Rel-16/48_series/48016/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/48_series/48016/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..655f42d292d608453641d99f22a08b1947d2a95c --- /dev/null +++ b/marked/Rel-16/48_series/48016/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c206cf5766906497a2cd0ca614be063b7ddc282dbf1e6ca83c3f8f14bf481590 +size 74588 diff --git a/marked/Rel-16/48_series/48016/2aa94b70ba3fadcba8420d9e3128253a_img.jpg b/marked/Rel-16/48_series/48016/2aa94b70ba3fadcba8420d9e3128253a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f500c42b52c1f91ca88df9400e4061fd2cc43b9e --- /dev/null +++ b/marked/Rel-16/48_series/48016/2aa94b70ba3fadcba8420d9e3128253a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f97b4384f8652fa95d8d5e31d007f8881ca2f521699dbcf58792dfcc103c6ebf +size 11395 diff --git a/marked/Rel-16/48_series/48016/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/48_series/48016/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..683df9834cfbb85df1a73837635f4c975e05a8e9 --- /dev/null +++ b/marked/Rel-16/48_series/48016/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb8b2108d1eb2acc83a2052a516b55372958ab19333d7b3440da67b236ca8e81 +size 25911 diff --git a/marked/Rel-16/48_series/48016/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/marked/Rel-16/48_series/48016/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84e4dcab466032dcfc1995b7d267a4aa9591912e --- /dev/null +++ b/marked/Rel-16/48_series/48016/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37876840f29c840d959faeb7f6945fea7ec7d0d7df7ff8f317dff1050a670306 +size 63852 diff --git a/marked/Rel-16/48_series/48016/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Rel-16/48_series/48016/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0737809ac80d050e33e7caa65c5fb386eef78e6 --- /dev/null +++ b/marked/Rel-16/48_series/48016/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76e5b8717b399532cba137b0f7555c588a03b195d5499e4c16c63830a2af2d4f +size 27783 diff --git a/marked/Rel-16/48_series/48016/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/48_series/48016/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8af6f59f2f49c3ad35b482d39a7a1df74916900 --- /dev/null +++ b/marked/Rel-16/48_series/48016/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00e3ea53dc9eb5d7ca3c6efee42f380eb806e138195677622ef74a43ddf5e642 +size 27445 diff --git a/marked/Rel-16/48_series/48016/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/48_series/48016/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be4e116130735960f14af83be9d25d6c4f23efd1 --- /dev/null +++ b/marked/Rel-16/48_series/48016/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3bf86b239886fc342534cc8b0c2b0269a8c5a84501ce255c3ad5635c145ffea +size 15470 diff --git a/marked/Rel-16/48_series/48016/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/48_series/48016/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cd728f1d13fa0e65e281229790ffe1043ab8aa8 --- /dev/null +++ b/marked/Rel-16/48_series/48016/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d27402160f49e3e7f5e3262087e93253ce4b347d9eccf009e0dbc188a2c90fab +size 27321 diff --git a/marked/Rel-16/48_series/48016/daae5239bb53d468ea958aedfc2e6070_img.jpg b/marked/Rel-16/48_series/48016/daae5239bb53d468ea958aedfc2e6070_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a35c73b3d8a997b193d7e0242a6311ea3828b91a --- /dev/null +++ b/marked/Rel-16/48_series/48016/daae5239bb53d468ea958aedfc2e6070_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:453c62ee8464397799f7202f21ff515063f5121d881fad1aecac12cde436ef86 +size 7932 diff --git a/marked/Rel-16/48_series/48016/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/48_series/48016/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db2f430751417f859f92deca2b45fd5e2c519ca1 --- /dev/null +++ b/marked/Rel-16/48_series/48016/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a672ce4ff12e4a2b642008bbd1529dcadebfb85bc5239781251f33ee39b9ee7 +size 15126 diff --git a/marked/Rel-16/48_series/48016/e3eebf9854831ba50eca8b26c468f65e_img.jpg b/marked/Rel-16/48_series/48016/e3eebf9854831ba50eca8b26c468f65e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b24dc252e8eb5f0d5b41aedf176e76904c97e185 --- /dev/null +++ b/marked/Rel-16/48_series/48016/e3eebf9854831ba50eca8b26c468f65e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af6d62ad50d6efc57329c8ee48c361f83562b74a556263ae665cd833c277bdd3 +size 26300 diff --git a/marked/Rel-16/48_series/48016/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/48_series/48016/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc11b948226edd4eb2dd33f5e9ca25d7181fe103 --- /dev/null +++ b/marked/Rel-16/48_series/48016/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b646af8913ccb10a2a971c6034513632785445a1d5da523c64a8acc1375d5ec +size 18657 diff --git a/marked/Rel-16/48_series/48016/raw.md b/marked/Rel-16/48_series/48016/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f0c4f4665ba8119408b27b511c55751119168503 --- /dev/null +++ b/marked/Rel-16/48_series/48016/raw.md @@ -0,0 +1,2246 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Network Service general description ..... | 10 | +| 4.1 Overview ..... | 10 | +| 4.2 Addressing..... | 11 | +| 4.2.1 Network Service Virtual Link (NS-VL)..... | 11 | +| 4.2.2 Network Service Virtual Connection (NS-VC)..... | 12 | +| 4.2.3 Network Service Virtual Connection Group ..... | 13 | +| 4.2.4 BSSGP Virtual Connection (BVC) ..... | 13 | +| 4.2.5 Use of Concepts on the Gb Interface when Intra Domain Connection of RAN Nodes to Multiple CN Nodes applies in the BSS ..... | 14 | +| 4.3 Sub-Network Service functions ..... | 14 | +| 4.4 Load sharing function..... | 15 | +| 4.4.1 Load Sharing function for the Frame Relay Sub-Network..... | 15 | +| 4.4.1.1 Overview..... | 15 | +| 4.4.1.2 Requirements on load sharing function ..... | 15 | +| 4.4.2 Load sharing function for the IP Sub-Network ..... | 15 | +| 4.4.2.1 Overview..... | 15 | +| 4.4.2.2 Selection of the local IP endpoint..... | 16 | +| 4.4.2.3 Selection of the remote IP endpoint..... | 16 | +| 4.4.2.3.1 Selection of remote IP endpoint for data traffic ..... | 16 | +| 4.4.2.3.2 Selection of remote IP endpoint for signalling traffic ..... | 17 | +| 4.4a Resource distribution function ..... | 17 | +| 4.4a.1 Requirements on resource distribution function..... | 17 | +| 4.5 NS-VC management function ..... | 18 | +| 4.5.1 Blocking / unblocking of an NS-VC ..... | 18 | +| 4.5.2 Reset of an NS-VC ..... | 18 | +| 4.5.3 Test of an NS-VC ..... | 19 | +| 5 Elements for layer-to-layer communication ..... | 19 | +| 5.1 Service primitive model ..... | 19 | +| 5.2 Service primitives and parameters ..... | 19 | +| 5.2.1 Primitives..... | 20 | +| 5.2.1.1 NS-UNITDATA-Request..... | 20 | +| 5.2.1.2 NS-UNITDATA-Indication..... | 20 | +| 5.2.1.3 NS-CONGESTION-Indication ..... | 20 | +| 5.2.1.4 NS-STATUS-Indication ..... | 20 | +| 5.2.2 Parameters ..... | 20 | +| 5.2.2.1 NS SDU ..... | 20 | +| 5.2.2.2 Link Selector Parameter..... | 21 | +| 5.2.2.3 BVCI I and NSEI..... | 21 | +| 5.2.2.4 Congestion cause ..... | 21 | +| 5.2.2.5 Transfer capability ..... | 21 | +| 5.2.2.6 NS affecting cause ..... | 21 | +| 5.2.2.7 NS change IP endpoint ..... | 21 | +| 6 Sub-Network Service protocol..... | 22 | +| 6.1 Frame Relay support of the Sub-Network Service protocol ..... | 22 | +| 6.1.1 Overview ..... | 22 | +| 6.1.2 Network configuration..... | 22 | +| 6.1.3 Services expected from layer 1 ..... | 23 | +| 6.1.4 Options selected from FRF 1.1 ..... | 23 | + +| | | | +|-----------|------------------------------------------------------|----| +| 6.1.4.1 | Support of DL-CONTROL sub-layer..... | 23 | +| 6.1.4.2 | Frame length ..... | 23 | +| 6.1.4.3 | Congestion control procedures ..... | 23 | +| 6.1.4.3.1 | DE bit usage ..... | 23 | +| 6.1.4.3.2 | FECN and BECN bit usage..... | 23 | +| 6.1.4.4 | Signalling procedures ..... | 24 | +| 6.1.4.5 | C/R bit usage..... | 24 | +| 6.1.5 | Abnormal conditions ..... | 24 | +| 6.2 | IP Support of the Sub-Network Service Protocol ..... | 24 | +| 6.2.1 | Overview ..... | 24 | +| 6.2.1a | Abnormal Conditions ..... | 25 | +| 6.2.2 | IP Fragmentation ..... | 25 | +| 6.2.3 | Services expected from layer 1 and layer 2..... | 25 | +| 6.2.4 | Size Procedure ..... | 25 | +| 6.2.4.1 | Abnormal Conditions..... | 26 | +| 6.2.5 | Configuration Procedure ..... | 26 | +| 6.2.5.1 | Abnormal Conditions..... | 27 | +| 6.2.6 | Add Procedure ..... | 28 | +| 6.2.6.1 | Abnormal Conditions..... | 28 | +| 6.2.7 | Delete Procedure ..... | 29 | +| 6.2.7.1 | Abnormal Conditions..... | 29 | +| 6.2.8 | ChangeWeight Procedure..... | 29 | +| 6.2.8.1 | Abnormal Conditions..... | 30 | +| 7 | Network Service Control protocol..... | 30 | +| 7.1 | Procedures for the transmission of NS SDUs ..... | 30 | +| 7.1.1 | Abnormal Conditions ..... | 30 | +| 7.2 | Blocking / unblocking procedures..... | 30 | +| 7.2.1 | Abnormal Conditions ..... | 32 | +| 7.3 | Reset procedure..... | 32 | +| 7.3.1 | Abnormal conditions ..... | 33 | +| 7.4 | Test procedure for a Frame Relay Sub-network ..... | 33 | +| 7.4.1 | Abnormal conditions ..... | 34 | +| 7.4b | Test Procedure for an IP Sub-network ..... | 34 | +| 7.4b.1 | Abnormal Conditions ..... | 34 | +| 7.4b.1.1 | Abnormal Conditions for signalling endpoints..... | 34 | +| 7.4b.1.2 | Abnormal Conditions for data endpoints..... | 35 | +| 7.5 | Procedure for error reporting..... | 35 | +| 7.5.1 | Abnormal conditions ..... | 35 | +| 7.6 | Resource Distribution Procedure ..... | 35 | +| 7.6.1 | Abnormal Conditions ..... | 36 | +| 8 | General protocol error handling..... | 36 | +| 8.1 | General case ..... | 36 | +| 8.1.1 | Presence requirements of Information Elements..... | 36 | +| 8.1.2 | Erroneous events ..... | 37 | +| 8.1.3 | Non-erroneous events ..... | 37 | +| 8.1.4 | Other events..... | 38 | +| 8.2 | Special cases..... | 38 | +| 8.2.1 | Deviations from the "General case" sub-clause ..... | 38 | +| 8.2.2 | Error reporting ..... | 38 | +| 9 | General PDU definitions and contents..... | 38 | +| 9.1 | General structure of a PDU ..... | 38 | +| 9.2 | Network Service Control PDUs ..... | 39 | +| 9.2.1 | NS-ALIVE..... | 39 | +| 9.2.2 | NS-ALIVE-ACK..... | 40 | +| 9.2.3 | NS-BLOCK ..... | 40 | +| 9.2.4 | NS-BLOCK-ACK ..... | 40 | +| 9.2.5 | NS-RESET ..... | 41 | +| 9.2.6 | NS-RESET-ACK..... | 41 | +| 9.2.7 | NS-STATUS..... | 41 | +| 9.2.7.1 | Static conditions for NS-VCI..... | 42 | + +| | | | +|-------------------------------|---------------------------------------------------------------|-----------| +| 9.2.7.2 | Static conditions for NS PDU ..... | 42 | +| 9.2.7.3 | Static conditions for BVCI ..... | 42 | +| 9.2.7.4 | Static conditions for List of IP4 Elements ..... | 42 | +| 9.2.7.5 | Static conditions for List of IP6 Elements ..... | 42 | +| 9.2.8 | NS-UNBLOCK ..... | 43 | +| 9.2.9 | NS-UNBLOCK-ACK ..... | 43 | +| 9.2.10 | NS-UNITDATA ..... | 43 | +| 9.3 | Sub-Network Service Control PDUs..... | 43 | +| 9.3.1 | SNS-ACK ..... | 43 | +| 9.3.2 | SNS-ADD ..... | 44 | +| 9.3.3 | SNS-CHANGEWEIGHT ..... | 44 | +| 9.3.4 | SNS-CONFIG ..... | 44 | +| 9.3.5 | SNS-CONFIG-ACK ..... | 45 | +| 9.3.6 | SNS-DELETE ..... | 45 | +| 9.3.7 | SNS-SIZE ..... | 45 | +| 9.3.8 | SNS-SIZE-ACK ..... | 46 | +| 10 | General information elements coding..... | 46 | +| 10.1 | General structure of the information elements ..... | 46 | +| 10.1.1 | Information Element Identifier ..... | 47 | +| 10.1.2 | Length indicator..... | 47 | +| 10.2 | Information element description ..... | 47 | +| 10.3 | Information elements..... | 48 | +| 10.3.1 | BVCI..... | 48 | +| 10.3.2 | Cause ..... | 48 | +| 10.3.2a | End Flag..... | 49 | +| 10.3.2b | IP Address ..... | 49 | +| 10.3.2c | List of IP4 Elements ..... | 50 | +| 10.3.2d | List of IP6 Elements ..... | 50 | +| 10.3.2e | Maximum Number of NS-VCs ..... | 50 | +| 10.3.2f | Number of IP4 Endpoints..... | 51 | +| 10.3.2g | Number of IP6 Endpoints..... | 51 | +| 10.3.3 | NS PDU ..... | 51 | +| 10.3.4 | NS SDU ..... | 51 | +| 10.3.5 | NS-VCI..... | 52 | +| 10.3.6 | NSEI ..... | 52 | +| 10.3.7 | PDU type ..... | 52 | +| 10.3.7a | Reset Flag ..... | 52 | +| 10.3.8 | (void) ..... | 53 | +| 10.3.9 | NS SDU Control Bits ..... | 53 | +| 10.3.10 | Transaction ID ..... | 53 | +| 11 | List of system variables..... | 53 | +| Annex A (informative): | Recommended usage of BVCI and NSEI..... | 55 | +| Annex B (informative): | Recommended usage of Resource Distribution for IP..... | 56 | +| Annex C (informative): | Change History..... | 59 | + +# --- 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 Network Service used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface). + +The protocol stack on the Gb interface is defined in the stage 2 Technical Specification 3GPP TS 43.060. + +The Network Service entity provides network services to the BSSGP entity specified in 3GPP TS 48.018. + +The layer 1 of the Gb interface is specified in 3GPP TS 48.014. + +In the present document, the communication between adjacent layers and the services provided by the layers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by the present document. + +The service primitive model used in the present document is based on the concepts developed in ITU-T Recommendation X.200. + +# --- 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.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [4] 3GPP TS 48.014: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Gb interface Layer 1". +- [5] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [6] FRF 1.1 (1996): "User-to-Network Implementation Agreement (UNI)". +- [7] (void). +- [8] ITU-T Recommendation Q.921 (1997): "ISDN user-network interface - Data link layer specification". +- [9] ITU-T Recommendation Q.922 (1992): "ISDN data link layer specification for frame mode bearer services". +- [10] ITU-T Recommendation Q.931 (1998): "ISDN user-network interface layer 3 specification for Basic Call Control". +- [11] ITU-T Recommendation Q.933 (1995): "Digital Subscriber Signalling System No. 1 (DSS 1) - Signalling specifications for frame mode switched and permanent virtual connection control and status monitoring". +- [12] ITU-T Recommendation I.370 (1991): "Congestion management for the ISDN Frame Relaying Bearer Service". + +- [13] ITU-T Recommendation X.200 (White Book): "Information technology - Open Systems Interconnection - Basic Reference Model: The basic model". +- [14] ANSI T1.602: "ISDN - Data Link Layer Signalling Specification for Application at the User-Network Interface". +- [15] ANSI T1.606 (1990): "Frame Relaying Bearer Service Architectural Framework and Service description (R 1996)". +- [16] ANSI T1.617 (1991): "Digital Subscriber System No. 1 (DSS1) Signaling Specification for Frame Relay Bearer Service (R1997)". +- [17] ANSI T1.618 (1991): "Digital Subscriber System No. 1 (DSS1) Core Aspects of Frame Relay Protocol for Use with Frame Relay Bearer Service (R1997)". +- [18] IETF RFC 768 (1980): "User Datagram Protocol" (STD 6). +- [19] IETF RFC 791 (1981): "Internet Protocol" (STD 5). +- [20] IETF RFC 2460 (1998): "Internet Protocol, Version 6 (IPv6) Specification". +- [21] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 22.060 and the following in apply: + +**BSSGP Virtual Connection (BVC):** end-to-end virtual communication path between remote Network Service user entities + +**BSSGP Virtual Connection Identifier (BVCI):** identifier of a BVC, having end-to-end significance across the Gb interface + +**IP endpoint:** an endpoint defined by its IP address and UDP port. An IP endpoint can be a data endpoint and/or a signalling endpoint + +**Data IP endpoint:** an IP endpoint used for Data traffic + +**Signalling IP endpoint:** an IP endpoint used for Signalling traffic + +**Data traffic:** data traffic for an IP Sub-Network is defined as NS SDUs for PTP and PTM functional entities (BVCI $\geq$ 1) + +**Signalling traffic:** signalling traffic for an IP Sub-Network is defined as NS SDUs for Signalling functional entities (BVCI=0) and all PDUs for IP Sub-Network Service Control + +**Full Mesh Connectivity:** any IPv4 endpoint in an NSE is capable of communications with any IPv4 endpoint in its peer NSE. Also any IPv6 endpoint in an NSE is capable of communications with any IPv6 endpoint in its peer NSE + +**Network Service Entity Identifier (NSEI):** identifier of an NS Entity having end-to-end significance across the Gb interface, i.e. the peer NSEs on the BSS side and the SGSN side are identified by the same NSEI value + +**Network Service Virtual Connection (NS-VC):** end-to-end virtual communication path between Network Service peer entities + +**Network Service Virtual Connection Identifier (NS-VCI):** identifier of an NS-VC having end-to-end significance across the Gb interface + +**Network Service Virtual Link (NS-VL):** virtual communication path between the BSS or the SGSN and the intermediate network, or between the BSS and the SGSN in case of direct point-to-point configuration + +**Network Service Virtual Link Identifier (NS-VLI):** identifier of an NS-VL, having local significance at the BSS or SGSN + +**Network Service Virtual Connection Group:** groups all NS-VCs together which provide communication between the same peer NS entities. This grouping has local significance at the BSS or SGSN + +**Blocked / unblocked:** when an NS-VC can not be used for NS user traffic, it is blocked. When an NS-VC can be used for NS user traffic, it is unblocked + +**Dead / alive:** when an NS-VC is able to provide communication between remote NS entities, it is alive. When it is not able, it is dead. These states are supervised by means of a test procedure, as further described in the present document + +**Pool area:** an area within which an MS may roam without need to change the serving SGSN. A pool area is served by one or more SGSNs in parallel. All the cells controlled by a BSC belong to the same one (or more) pool area(s). + +## 3.2 Symbols + +For the purposes of the present document, the symbols given in 3GPP TS 23.060 apply. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 and the following apply: + +| | | +|--------|-----------------------------------------------| +| BECN | Backward Explicit Congestion Notification | +| BSSGP | Base Station System GPRS Protocol | +| BVC | BSSGP Virtual Connection | +| BVCI | BSSGP Virtual Connection Identifier | +| CLLM | Consolidated Link Layer Management | +| DE | Discard Eligibility | +| FECN | Forward Explicit Congestion Notification | +| FR | Frame Relay | +| FRF | Frame Relay Forum | +| IP | Internet Protocol | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| LLC | Logical Link Control | +| LSP | Link Selector Parameter | +| MAC | Medium Access Control | +| NS | Network Service | +| NSEI | Network Service Entity Identifier | +| NS-SAP | Network Service Service Access Point | +| NS-VC | Network Service Virtual Connection | +| NS-VCI | Network Service Virtual Connection Identifier | +| NS-VL | Network Service Virtual Link | +| NS-VLI | Network Service Virtual Link Identifier | +| PDU | Protocol Data Unit | +| PTM | Point-To-Multipoint | +| PTP | Point-To-Point | +| PVC | Permanent Virtual Connection | +| RLC | Radio Link Control | +| SGSN | Serving GPRS Support Node | +| SNS | Sub-Network Service | +| UDP | User Datagram Protocol | +| UNI | User-to-Network Interface | + +# --- 4 Network Service general description + +## 4.1 Overview + +The position of the Network Service within the protocol stack of the Gb interface is shown in figure 4.1.1. + +![Figure 4.1.1: Position of the NS within the Gb interface protocol stack. The diagram shows two protocol stacks for BSS and SGSN connected by a Gb interface. The BSS stack has layers RELAY (containing RLC and BSSGP), MAC, NS, and L1. The SGSN stack has layers LLC, BSSGP, NS, and L1. The NS layers in both stacks are aligned across the Gb interface.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 4.1.1: Position of the NS within the Gb interface protocol stack. The diagram shows two protocol stacks for BSS and SGSN connected by a Gb interface. The BSS stack has layers RELAY (containing RLC and BSSGP), MAC, NS, and L1. The SGSN stack has layers LLC, BSSGP, NS, and L1. The NS layers in both stacks are aligned across the Gb interface. + +NOTE: BSSGP, L1, LLC, MAC, RELAY, RLC are outside the scope of the present document, refer to 3GPP TS 43.060 for further details. + +**Figure 4.1.1: Position of the NS within the Gb interface protocol stack** + +The Network Service performs the transport of NS SDUs between the SGSN and BSS. The services provided to the NS user shall be: + +- Network Service SDU transfer. The Network Service entity shall provide network service primitives allowing for transmission and reception of upper layer protocol data units between the BSS and SGSN. The NS SDUs are transferred in order by the Network Service, but under exceptional circumstances order may not be maintained. +- Network congestion indication. Congestion recovery control actions may be performed by the Sub-Network Service (e.g. Frame Relay). Congestion reporting mechanisms available in the Sub-Network Service implementation shall be used by the Network Service to report congestion. +- Status indication. Status indication shall be used to inform the NS user of the NS affecting events e.g. change in the available transmission capabilities. + +The Network Service entity is composed of an entity dependent on the intermediate transmission network used on the Gb interface, the Sub-Network Service, and of a control entity independent from that network, the Network Service Control. There is a hierarchical relationship between both entities. This is reflected in figure 4.1.2. The detailed communication mechanisms between both entities is an internal matter for the Network Service and is not further standardized. + +![Figure 4.1.2: Internal architecture of the Network Service. The diagram shows a box labeled 'Network Service' containing two stacked boxes: 'Network Service Control / Network Service Control protocol' on top and 'Sub-Network Service / Sub-Network Service protocol' on the bottom. An arrow points from the 'Network Service' label to the top box.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +Figure 4.1.2: Internal architecture of the Network Service. The diagram shows a box labeled 'Network Service' containing two stacked boxes: 'Network Service Control / Network Service Control protocol' on top and 'Sub-Network Service / Sub-Network Service protocol' on the bottom. An arrow points from the 'Network Service' label to the top box. + +**Figure 4.1.2: Internal architecture of the Network Service** + +The Sub-Network Service entity provides a communication service to Network Service Control peer entities. The Network Service Control peer entities use the Sub-Network Service for communication with each other. The peer-to-peer communication across the Gb interface between remote Network Service Control entities is performed over Network Service Virtual Connections (NS-VCs). An NS-VC is a virtual communication path between Network Service Control peer entities. + +The Network Service entity provides a communication service to NS user peer entities: the peer-to-peer communication between remote NS user entities is performed over BSSGP Virtual Connections (BVCs). A BVC is a virtual + +communication path between Network Service user peer entities. A Network Service Entity communicates with only one peer Network Service Entity. + +Addressing across the Gb interface is further detailed in the rest of the present document. + +The Network Service Control entity is responsible for the following functions: + +- NS SDU transmission: The NS SDUs shall be transmitted on the NS-VCs. The NS SDUs are encapsulated into Network Service Control PDUs which in turn are encapsulated into Sub-Network Service PDUs. +- Load sharing: The load sharing function distributes the NS SDU traffic amongst the available (i.e. unblocked) NS-VCs of a group. +- NS-VC management: A blocking procedure is used by an NS entity to inform an NS peer entity when an NS-VC becomes unavailable for NS user traffic. An unblocking procedure is used for the reverse operation. A reset procedure is used between peer NS entities in order to set an NS-VC to a determined state, after events resulting in possibly inconsistent states of the NS-VC at both sides of the Gb interface. A test procedure is used to check that an NS-VC is operating properly between peer NS entities. + +## 4.2 Addressing + +The purpose of this sub-clause is to describe the addressing principles on the Gb interface in a generic way, i.e. irrespective of the exact configuration of the Gb interface and of the exact nature of the intermediate transmission network, when present. Therefore, this sub-clause provides an abstract description of the addressing principles. These principles are then applied to real networks in sub-clause "Sub-Network Service protocol". + +In this sub-clause, addressing is considered in the general case where an SGSN is connected to several BSSs via an intermediate transmission network and in the specific case where a BSS is connected to several SGSNs within one or more pool areas, see 3GPP TS 23.236. Point-to-point physical connections may also be used, addressing in this special case can be derived from the general case. + +### 4.2.1 Network Service Virtual Link (NS-VL) + +An SGSN and a BSS may use different physical links for connecting to each other (e.g. because of intermediate equipment or transmission network). Each physical link is locally (i.e. at each side of the Gb interface) identified by means of a physical link identifier. The exact structure of the physical link identifier is implementation dependent. + +Each physical link supports one or more Network Service Virtual Links (NS-VLs). Each NS-VL is supported by one physical link if the Frame Relay Sub-Network is employed. For an IP sub-network, the NS-VL is mapped to an IP endpoint. The exact nature of the NS-VL depends on the intermediate network used on the Gb interface. In the general case of an intermediate transmission network, the NS-VL is used to access the intermediate network. Communication means internal to the intermediate network are outside the scope of the present document. The NS-VLs may alternatively be used end-to-end between the BSS and SGSN, in case of a point-to-point configuration on the Gb interface. + +Each NS-VL may be identified by means of a Network Service Virtual Link Identifier (NS-VLI). The significance (i.e. local or end-to-end) and the exact structure of the NS-VLI depends on the configuration of the Gb interface and on the intermediate network used. For example, in the case of a Frame Relay network, the physical link is the FR bearer channel, the NS-VL is the local link (at UNI) of the FR permanent virtual connection (PVC) and the NS-VLI is the association of the FR DLCI and bearer channel identifier. + +### 4.2.2 Network Service Virtual Connection (NS-VC) + +In order to provide end-to-end communication between the BSS and SGSN irrespective of the exact configuration of the Gb interface, the concept of Network Service Virtual Connection (NS-VC) is used. The NS-VCs are end-to-end virtual connections between the BSS and SGSN. In the case of a FR sub-network, at each side of the Gb interface there is a one-to-one correspondence between NS-VCs and NS-VLs. When employing an IP-sub-network one NS-VL may serve several NS-VCs (see figure 4.2.2.1). + +![Figure 4.2.2.1: IP sub-network relationship between NS-VCs and NS-VLs. The diagram shows two main entities, BSS and SGSN, each containing an NSEI=2. Inside the BSS, there are two NS-VLs (NS-VL_I and NS-VL_II) connected to UDP/IP endpoints A_1 and A_2. Inside the SGSN, there are two NS-VLs (NS-VL_III and NS-VL_IV) connected to UDP/IP endpoints B_3 and C_3. Four NS-VCs are shown connecting the BSS NS-VLs to the SGSN NS-VLs: NS-VC_1 (UDP_A/IP_1, UDP_B/IP_3), NS-VC_2 (UDP_A/IP_1, UDP_C/IP_3), NS-VC_3 (UDP_A/IP_2, UDP_B/IP_3), and NS-VC_4 (UDP_A/IP_2, UDP_C/IP_3). Arrows indicate the mapping from BSS NS-VLs to SGSN NS-VLs through the NS-VCs.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 4.2.2.1: IP sub-network relationship between NS-VCs and NS-VLs. The diagram shows two main entities, BSS and SGSN, each containing an NSEI=2. Inside the BSS, there are two NS-VLs (NS-VL\_I and NS-VL\_II) connected to UDP/IP endpoints A\_1 and A\_2. Inside the SGSN, there are two NS-VLs (NS-VL\_III and NS-VL\_IV) connected to UDP/IP endpoints B\_3 and C\_3. Four NS-VCs are shown connecting the BSS NS-VLs to the SGSN NS-VLs: NS-VC\_1 (UDP\_A/IP\_1, UDP\_B/IP\_3), NS-VC\_2 (UDP\_A/IP\_1, UDP\_C/IP\_3), NS-VC\_3 (UDP\_A/IP\_2, UDP\_B/IP\_3), and NS-VC\_4 (UDP\_A/IP\_2, UDP\_C/IP\_3). Arrows indicate the mapping from BSS NS-VLs to SGSN NS-VLs through the NS-VCs. + +**Figure 4.2.2.1: IP sub-network relationship between NS-VCs and NS-VLs** + +For example, in the case of a Frame Relay network, the NS-VC is the FR permanent virtual connection (PVC). + +Figure 4.2.2.2 shows the relationship between NS-VCs and NS-VLs for a Frame Relay sub-network. In the case of an IP network, the NS-VC is given by a pair of IP endpoints at the BSS and SGSN. While Figure 4.2.2.1 illustrates a configuration with only one NSE, multiples NSE in either the BSS or SGSN are allowed. + +At the BSS, the IP endpoints for each NSE shall not be shared among NSEs connected to the same SGSN. However, an IP endpoint at the BSS may serve multiple NSEs when each of the NSEs is connected towards different SGSNs. At the SGSN, an IP endpoint may serve multiple NSEs; (i.e. IP endpoints may be shared among NSEs). + +![Figure 4.2.2.2: Frame relay sub-network relationship between NS-VCs and NS-VLs. The diagram shows a BSS connected to an SGSN via an intermediate transmission network. A thick line representing an NS-VC connects the BSS and SGSN, passing through the transmission network. Labels indicate 'end-to-end NS-VC' for the connection, 'NS-VL at the BSS side' for the interface at the BSS, and 'NS-VL at the SGSN side' for the interface at the SGSN.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +Figure 4.2.2.2: Frame relay sub-network relationship between NS-VCs and NS-VLs. The diagram shows a BSS connected to an SGSN via an intermediate transmission network. A thick line representing an NS-VC connects the BSS and SGSN, passing through the transmission network. Labels indicate 'end-to-end NS-VC' for the connection, 'NS-VL at the BSS side' for the interface at the BSS, and 'NS-VL at the SGSN side' for the interface at the SGSN. + +**Figure 4.2.2.2: Frame relay sub-network relationship between NS-VCs and NS-VLs** + +Each NS-VC is identified by means of a Network Service Virtual Connection Identifier (NS-VCI) having end-to-end significance across the Gb interface. An NS-VCI uniquely identifies an NS-VC within an SGSN and within a BSS. + +The establishment of an NS-VC includes the establishment of physical links, see 3GPP TS 48.014, and of NS-VLs. + +In the case of an FR sub-network NS-VCs and NS-VLs are permanently established by means of administrative procedures, NS-VCIs are allocated by administrative means as well. The mapping of NS-VCIs on NS-VLIs and on physical link identifiers is held in non-volatile memory. + +When employing an IP sub-network the NS-VCs and NS-VLs may be established by means of administrative means (static configuration) or by auto-configuration procedures (dynamic configuration). + +### 4.2.3 Network Service Virtual Connection Group + +The Network Service Virtual Connection Group groups together all NS-VCs providing communication between the same peer NS entities. One NS-VC group is configured between two peer NS entities. This grouping is performed by administrative means. At each side of the Gb interface, there is a one-to-one correspondence between a group of NS-VCs and an NSEI. The NSEI has an end-to-end significance across the Gb interface. + +### 4.2.4 BSSGP Virtual Connection (BVC) + +The Network Service provides communication paths between remote NS user entities. These communication paths are called BSSGP Virtual Connections (BVCs). Each BVC is used to transport NS SDUs between NS users. + +A Network Service Entity provides one or more BVCs between peer NS user entities. Each BVC is supported by one group of NS-VCs. Each group of NS-VCs supports one or more BVCs. The NS entity maps between BVC and the related NS-VC group. + +Each BVC is identified by means of a BSSGP Virtual Connection Identifier (BVCI) having an end-to-end significance across the Gb interface. The BVCI together with the NSEI uniquely identifies a BVC within an SGSN. The BVCI and NSEI are used on the Network Service-Service Access Point (NS-SAP) for layer-to-layer communication. + +### 4.2.5 Use of Concepts on the Gb Interface when Intra Domain Connection of RAN Nodes to Multiple CN Nodes applies in the BSS + +![Diagram illustrating the use of Gb concepts when intra-domain connection of RAN nodes to multiple CN nodes applies in the BSS. The diagram shows a BSS (Base Station Subsystem) connected to two SGSNs (SGSN 1 and SGSN 2). The BSS contains two Radio cells (Radio cell 1 and Radio cell 2) and two Network Service Entities (NSEI=1 and NSEI=2). The SGSNs contain Network Service Entities (NSEI=1 and NSEI=2) and Network Service Virtual Connections (NS-VC 1, NS-VC 2, NS-VC 3, NS-VC 4). The connections are as follows: Radio cell 1 is connected to NSEI=1 via BVCI=3 and BVCI=4. Radio cell 2 is connected to NSEI=2 via BVCI=3 and BVCI=5. NSEI=1 is connected to NS-VC 1 and NS-VC 2, which are then connected to NSEI=1 in SGSN 1. NSEI=2 is connected to NS-VC 3 and NS-VC 4, which are then connected to NSEI=2 in SGSN 2.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) + +Diagram illustrating the use of Gb concepts when intra-domain connection of RAN nodes to multiple CN nodes applies in the BSS. The diagram shows a BSS (Base Station Subsystem) connected to two SGSNs (SGSN 1 and SGSN 2). The BSS contains two Radio cells (Radio cell 1 and Radio cell 2) and two Network Service Entities (NSEI=1 and NSEI=2). The SGSNs contain Network Service Entities (NSEI=1 and NSEI=2) and Network Service Virtual Connections (NS-VC 1, NS-VC 2, NS-VC 3, NS-VC 4). The connections are as follows: Radio cell 1 is connected to NSEI=1 via BVCI=3 and BVCI=4. Radio cell 2 is connected to NSEI=2 via BVCI=3 and BVCI=5. NSEI=1 is connected to NS-VC 1 and NS-VC 2, which are then connected to NSEI=1 in SGSN 1. NSEI=2 is connected to NS-VC 3 and NS-VC 4, which are then connected to NSEI=2 in SGSN 2. + +**Figure 4.2.2.3: Use of Gb Concepts when Intra Domain Connection of RAN Nodes to Multiple CN Nodes applies in the BSS** + +For a pool area the BSS sets up several NSEs, and each of these NSEs goes towards different SGSNs. In this way the BSS have one NSE towards each of the connected SGSNs. Alternatively, several NSEs in the BSS are connected towards each of the SGSNs supporting the pool area. + +One or more NS-VCs are set up between each of the NSEs in the BSS and the corresponding peer NSEs in the SGSNs. In an IP network, an NS-VC is identified by a pair of IP addresses and UDP ports at both the BSS and the SGSN. In a FR network, the identity of an NS-VC is unique within an NSEI. + +## 4.3 Sub-Network Service functions + +The Sub-Network Service functions of the Network Service shall provide access to the intermediate network (or to the peer entity in case of direct point-to-point configuration) by means of NS-VLs and shall provide NS-VCs between NS peer entities. + +On each NS-VC, data are transferred in order by the Sub-Network Service. + +When the Sub-Network Service entity detects that an NS-VC becomes unavailable (e.g. upon failure detection), or when the NS-VC becomes available again (e.g. after failure recovery), the Network Service Control entity shall be informed. Failures may occur due to protocol errors, intermediate transmission network failure, equipment or link failure or other reasons. + +## 4.4 Load sharing function + +### 4.4.1 Load Sharing function for the Frame Relay Sub-Network + +#### 4.4.1.1 Overview + +The load sharing function distributes the NS SDU traffic among the unblocked NS-VCs of the same group on the Gb interface. The use of load sharing also provides to the upper layer seamless service upon failure by re-organizing the NS SDU traffic between the unblocked NS-VCs of the same group. The re-organization may disturb the order of transferred NS SDUs. The load sharing function should be implemented in both the BSS and the SGSN. + +Load sharing applies only to NS SDUs, not to NS signalling such as NS-VC management PDUs. + +#### 4.4.1.2 Requirements on load sharing function + +All NS SDUs to be transmitted over the Gb interface are passed to the load sharing function along with the Link Selector Parameter (LSP), the BVCI and the NSEI. LSP and BVCI are used by the NS entity to select amongst the unblocked NS-VCs within the group, addressed by means of the NSEI, where to send the NS SDU. The mapping between LSP and NS-VC is based on an implementation dependent function that meets the following requirements: + +- For each BVC and NSEI, the NS entity selects the NS-VC out of the group based on the LSP. This is an internal matter for the NS entity and it is not subject to further standardization. +- For each BVC and NSEI, NS SDUs with the same Link Selector Parameter shall be sent on the same NS-VC. Thus, the load sharing function guarantees that, for each BVC, the order of all NS SDUs marked with the same LSP value is preserved. In the event of a link failure and subsequent re-organization of the NS SDU traffic between the unblocked NS-VCs, the receiver may get out of order NS SDUs. Further actions implemented to prevent this error are outside the scope of the present document. +- Load sharing functions at the BSS and the SGSN are independent. Therefore, uplink and downlink NS SDUs for a subscriber may be transferred over different NS-VCs. +- A change in NS-VCs available for NS user traffic (i.e. one or more NS-VCs become blocked or unblocked) shall result in a re-organization of the NS SDU traffic amongst the unblocked NS-VCs of the same group. +- For a BVC, when there is no unblocked NS-VC of the group left between a BSS and a SGSN, the corresponding traffic is discarded by the NS at the sending side. + +The Link Selector Parameter is locally used at the BSS and at the SGSN and shall not be transmitted across the Gb interface. + +### 4.4.2 Load sharing function for the IP Sub-Network + +#### 4.4.2.1 Overview + +The load sharing function distributes the NS SDUs and SNS PDUs traffic among the available IP endpoints on the Gb interface. The use of load sharing also provides to the upper layer seamless service upon failure by re-negotiating the NS SDU traffic between the remaining IP endpoints. The re-negotiation may disturb the order of transferred NS SDUs. The load sharing function shall be implemented in both the BSS and the SGSN. + +The load sharing function for the IP sub-network determines the local IP endpoint locally and the remote IP endpoint based on weight information provided by the peer NSE. Each NSE shall use an implementation dependent load sharing function to determine the local IP endpoint associated with all NS SDU traffic related to an MS. The remote IP endpoint shall initially be determined by an implementation dependent load sharing function that distributes the traffic in equal proportion to the relative weights assigned to the peer NSE's endpoints. These relative weights are assigned by the peer NSE for both signalling traffic and data traffic and will be referred to as signalling weight and data weight respectively. (These relative weights are communicated using the SNS-CONFIG, SNS-ADD, and SNS-CHANGE-WEIGHT PDUs. Also, the remote IP endpoint can be changed by the peer NSE via the Resource Distribution Function (refer to sub-clause 4.4.a.). + +#### 4.4.2.2 Selection of the local IP endpoint + +The LSP is used by an NS entity to select amongst the available local IP endpoints for the given NSEI, from which the NS SDUs are sent. The association between an LSP and a local IP endpoint is based on an implementation dependent function that meets the following requirements: + +- For each NS-SDU, an NS entity selects a local IP endpoint based on the LSP for sending the NS-SDU to the peer NSE. If the LSP has not been associated with a local IP endpoint, then a local IP endpoint shall be selected by a method that is implementation dependent. This is an internal matter for the NS entity and it is not subject to further standardisation. +- Once a local IP endpoint is selected for the LSP, the NSE should maintain a linkage between the LSP and the local IP endpoint so that NS SDUs with the same Link Selector Parameter shall be sent from the same local IP endpoint. The NSE may disassociate the MS from the last used local IP endpoint when an MS makes a cell change. +- If a local IP endpoint that has been mapped to an LSP is taken out of service, a new local IP endpoint shall be selected and associated with the LSP. +- Selection of the local IP endpoint occurs locally at each NSE. +- If there is no available local IP endpoint, the corresponding traffic is discarded by the NS at the sending side. + +The Link Selector Parameter is locally used at the BSS and at the SGSN and shall not be transmitted across the Gb interface. + +#### 4.4.2.3 Selection of the remote IP endpoint + +A remote IP endpoint is an IP address and UDP port that the peer NSE has made known to the local NSE (e.g. using the Configuration procedure). In addition to being used to select the local IP endpoint, the LSP is also used by the NS entity to select amongst the available remote IP endpoints for the given NSEI, to which the NS SDUs are sent. The selection of the remote IP endpoint for an LSP is initially based on the signalling weight and data weight of the remote IP endpoints. Also, the Resource distribution function can be used by the peer NSE to initially request or subsequently change the remote IP endpoint selection for an LSP. + +##### 4.4.2.3.1 Selection of remote IP endpoint for data traffic + +For each NS-SDU, an NS entity selects a remote IP endpoint based on the LSP for sending the NS-SDU to the peer NSE. If the LSP has not been associated with a remote IP endpoint, then a remote IP endpoint shall be selected for the LSP according to the data-weights assigned to the peer NSE's IP endpoints. The remote IP endpoints shall be selected in equal proportion to the data-weights assigned to the peer NSE's endpoints. Data-weights are assigned by the peer NSE and have a value range of 0 to 255. A data weight of 0 assigned to an IP endpoint indicates that the load sharing function shall not initially associate this remote IP endpoint to an LSP. However, if an LSP has been previously associated with a remote IP endpoint, NS SDUs associated with this LSP shall be sent to this remote IP endpoint regardless of its data weight, i.e., even when the data weight has a value of 0. (This association of LSP to the IP endpoint with a data weight of 0 may have been requested by the remote NSE via the Resource Distribution Function.) + +Examples of equal proportion selection: + +- If IP endpoint (A) has data weight=5 and endpoint (B) has data weight=10, then endpoint (B) will be selected for initial association with an LSP twice as often as endpoint (A). +- If IP endpoint (A) has data weight=10 and endpoint (B) has data weight=10, then endpoint (A) and endpoint (B) will be selected for initial association with an LSP on an equal basis. + +- If IP endpoint (A) has a data weight=0, then IP endpoint (A) will not be selected for initial association with an LSP. However, IP endpoint (A) may be associated with an LSP via the peer NSE's use of the Resource Distribution Function. + +Once a remote IP endpoint is selected for the LSP, the NSE should maintain a linkage between the LSP and the remote IP endpoint so that NS SDUs with the same LSP shall be directed to the same remote IP endpoint. If a remote IP endpoint associated with an LSP is taken out of service, then another remote IP endpoint shall be selected according to the data-weights assigned by the peer NSE and associated with the LSP. The association of an LSP to a remote IP endpoint can be changed by the peer NSE using the Resource Distribution function (refer to sub-clause 4.4a). + +The BSS may disassociate the LSP from the remote IP endpoint when an MS makes a cell change or when the MS context is deleted. The SGSN shall associate an MS with the last used remote IP endpoint as long as the SGSN has location information for the MS on cell level. + +The Link Selector Parameter is locally used at the BSS and at the SGSN and shall not be transmitted across the Gb interface. + +##### 4.4.2.3.2 Selection of remote IP endpoint for signalling traffic + +Outgoing BVCI=0 NS-SDUs, or SNS PDUs shall be sent to a remote IP endpoint according to the signalling weight assigned by the peer NSE. The sending NSE shall distribute these messages in equal proportion to the signalling weights assigned to the peer NSE's IP endpoints. The sending NSE may send the BVCI=0 NS-SDUs and all SNS PDUs from any IP endpoint. + +- NOTE: Load sharing endpoint selection does not apply to NS-SDUs or SNS PDUs subject to specific conditions stipulated elsewhere in the present specification, such as SNS-SIZE and SNS-CONFIG PDUs that need to be sent to an SGSN pre-configured endpoint, or any acknowledgement / response that needs to be sent back to the endpoint having originated the corresponding request. + +Examples of equal proportion selection: + +- If IP endpoint (A) has signalling weight=5 and IP endpoint (B) has signalling weight=10, then IP endpoint (B) will be selected as a signalling IP endpoint twice as often as IP endpoint (A). +- If IP endpoint (A) has signalling weight=10 and IP endpoint (B) has signalling weight=10, then IP endpoint (A) and IP endpoint (B) will be selected as a signalling IP endpoint on an equal basis. +- If IP endpoint (A) has a signalling weight=0, then IP endpoint (A) will not be selected as a signalling IP endpoint. + +If there is no available remote IP endpoint, the corresponding traffic is discarded by the NS at the sending side. + +The Link Selector Parameter is locally used at the BSS and at the SGSN and shall not be transmitted across the Gb interface. + +## 4.4a Resource distribution function + +The resource distribution function is only available for data traffic when an IP sub-network is used. This function allows the BSS or SGSN to explicitly change the IP endpoint at which it receives NS SDUs. The BSS or SGSN may choose not to initiate any request for change in IP endpoints for any MS or MBMS session and rely on the underlying load sharing function to properly distribute NS user traffic. However, if the BSS or SGSN receives a request to change the IP endpoint at which NS SDUs are received for an MS or MBMS session, then the higher layers shall be informed of this change by an indication in the Link Selector Parameter. That is, if the SGSN (BSS) receives a request to change the remote IP endpoint for an MS or MBMS session then subsequent downlink (uplink) data for the mobile or MBMS session shall be sent to that remote IP endpoint indicated by the request. + +The Resource Distribution Function overrides the Load Sharing function for the selection of the remote IP endpoint. The Resource Distribution Function overrides the data weight of a remote IP endpoint (i.e. the Resource Distribution Function can request that data be sent to an IP endpoint that has a data weight=0). + +#### 4.4.a.1 Requirements on resource distribution function + +In an IP sub-network the BSS or SGSN may receive an NS SDU with a request to change the remote IP endpoint. The triggers for generating a request are implementation dependent and are not subject to further standardization. The behaviour on receipt of a request shall meet the following requirements: + +- An NSE may change the IP endpoint at which the NS SDUs for an MS are received by setting the R-bit field to "1" (Request change flow) in the *NS SDU Control Bits* IE in the next NS SDU or in an NS SDU with no data. + +NOTE: The BSSGP DL-UNITDATA (BSSGP UL-UNITDATA) and the BSSGP UL-MBMS-UNITDATA with an LLC-PDU Length Indicator set to 0 are given in 3GPP TS 48.018. + +- An NSE shall only act on a request for change in IP endpoint if the new IP endpoint has previously been configured and is operational. +- For MBMS, the resource distribution function is only available at the BSS side. That is, it is only the BSS that can request a change of the IP endpoint to which the NS SDUs for an MBMS session are sent while MBMS data flows are only present in the downlink direction. +- Upon receiving a request for change in IP endpoint, an NSE shall notify the NS user entity of the change by an indication in the Link Selector Parameter (that is, the IP endpoint at the peer entity) and direct subsequent NS SDUs for the given MS or MBMS session to the new IP endpoint. +- The resource distribution functions are independent at the BSS and the SGSN. That is, each entity may independently choose the IP endpoint at which NS SDUs for an MS or MBMS session are received. +- An NSE shall obtain the new IP endpoint from the source IP endpoint (i.e. in the UDP/IP header) of the NS SDU in which the Request Change Flow bit was set. The new IP Endpoint is not explicitly transmitted over the Gb. +- The BSS shall associate an MS with the last used remote IP endpoint as long as the MS context exist in the BSS or until the MS makes a cell change. +- The SGSN shall associate an MS with the last used remote IP endpoint as long as the SGSN has location information for the MS on cell level. +- The SGSN shall associate an MBMS session with the last used remote IP endpoint for the duration of the MBMS session. + +## 4.5 NS-VC management function + +The NS-VC management function is responsible for the blocking / unblocking, reset and test of NS-VCs. + +### 4.5.1 Blocking / unblocking of an NS-VC + +The blocking / unblocking procedures shall not be used for an IP Sub-network. + +When a condition making an NS-VC unavailable for NS user traffic is locally detected at the BSS or at the SGSN, the NS-VC shall be marked as blocked by the local NS entity and the remote NS peer entity shall be informed by means of a blocking procedure. The remote NS entity shall then mark the NS-VC as blocked and shall consider it as unavailable for NS user traffic. + +A BSS or SGSN may block an NS-VC because of: + +- Operation and Maintenance intervention at the Gb interface making the NS-VC unavailable for NS user traffic; +- equipment failure at a BSS or an SGSN entity; +- equipment or link failure on a BSS or an SGSN site; +- failure in the transit network; or +- other causes. + +When the NS-VC becomes available again for NS user traffic, the NS entity which initiated the blocking procedure may inform the remote NS peer entity by means of an unblocking procedure. The remote NS entity shall then mark the NS-VC as unblocked and shall consider it as available for NS user traffic. + +The blocking / unblocking procedures are further detailed in the rest of the present document. + +### 4.5.2 Reset of an NS-VC + +The reset procedure shall not be used for an IP Sub-network. + +This procedure is used to reset one NS-VC to a determined state between remote entities. This procedure is performed: + +- when a new NS-VC is set-up; +- after a processor re-start; +- after a failure recovery when the state of an NS-VC must be set to blocked and alive; or +- at any local event restoring an existing NS-VC in the dead state or in an undetermined state. + +When a reset procedure is initiated, data in transfer may be lost. + +### 4.5.3 Test of an NS-VC + +The test procedure is used to check that end-to-end communication exists between peer NS entities on a given NS-VC. When end-to-end communication exists, the NS-VC is in the "alive" state, otherwise it is in the "dead" state. A dead NS-VC can not be in the "unblocked" state. + +# --- 5 Elements for layer-to-layer communication + +This sub-clause presents the Network Service in a generic way, no assumptions are made regarding the real protocols providing the network services. + +## 5.1 Service primitive model + +The service primitive model shown in figure 5.1.1 is applicable to both BSS and SGSN. + +![Diagram of the Network Service primitive model showing the interaction between a Network Service user (GSM 08.18) and a Network Service (GSM 08.16) via an NS-SAP.](098802c99831a6a7d445310d5e874e16_img.jpg) + +The diagram illustrates the Network Service primitive model. It consists of two main rectangular blocks. The top block is labeled 'GSM 08.18' and is associated with the text 'Network Service user' to its left. The bottom block is labeled 'GSM 08.16' and is associated with the text 'Network Service' to its left. A vertical double-headed arrow connects the two blocks, passing through a small circle labeled 'NS-SAP'. A horizontal dashed line separates the top and bottom blocks, with the NS-SAP circle positioned on this line. + +Diagram of the Network Service primitive model showing the interaction between a Network Service user (GSM 08.18) and a Network Service (GSM 08.16) via an NS-SAP. + +**Figure 5.1.1: Network Service primitive model** + +The network services are provided at the Network Service-Service Access Point (NS-SAP). + +## 5.2 Service primitives and parameters + +The Network Service primitives are summarized in table 5.2.1. The general syntax of the Network Service primitives is: + +NS - Generic name - Type (Parameters). + +**Table 5.2.1: Network Service primitives** + +| Generic name | Type | | | | Parameters | +|--------------|---------|------------|----------|---------|-------------------------------------------------------------------------------------| +| | Request | Indication | Response | Confirm | | +| UNITDATA | X | X | | | - BVCI and NSEI
- NS SDU
- NS Change IP endpoint
- Link Selector Parameter | +| CONGESTION | | X | | | - BVCI and NSEI
- congestion cause | +| STATUS | | X | | | - BVCI and NSEI
- NS affecting cause
- transfer capability | + +### 5.2.1 Primitives + +#### 5.2.1.1 NS-UNITDATA-Request + +This primitive is used by the NS user entity to send a NS SDU to its peer entity via a BVC. The NS entity sends the NS SDU in unacknowledged mode. The Link Selector Parameter is used to identify the NS SDUs which must be sent in order relatively to each other. The NSEI is used by the NS entity to select the group of NS-VCs corresponding to the addressed remote entity. The NS Change IP endpoint is used to request the NS entity to indicate whether a "request change flow" or "confirm change flow" indication needs to be sent to its peer entity. + +#### 5.2.1.2 NS-UNITDATA-Indication + +This primitive is used by the NS entity to provide the NS user entity with a NS SDU received on a virtual connection. The NS SDU are received in unacknowledged mode. BVCI together with NSEI indicate which BVC the NS SDU was received on. The NS Change IP endpoint is used to indicate to the user of the NS entity whether a "request change flow" or "confirm change flow" indication was received from the peer entity. In case a "request change flow" is received from the peer entity the Link Selector Parameter on which the NS SDU was received is sent to the higher layer. + +#### 5.2.1.3 NS-CONGESTION-Indication + +The NS entity shall be able to detect when a congestion situation starts and ends on an NS-VC. + +This primitive is used by the NS entity to report to the NS user entity that congestion is detected or that the congestion situation has disappeared. The BVCI and NSEI of the affected BVC and the congestion cause are reported to the NS user entity. Typically, the cause indicates the direction of transmission affected by the congestion. + +#### 5.2.1.4 NS-STATUS-Indication + +There may be situations where an NS-VC becomes unavailable for NS user traffic. When this occurs, the NS user is informed of the degradation of the transfer capacity by means of this primitive including the "transfer capability" parameter. + +When an NS-VC previously unavailable for NS user traffic becomes available again, the NS user entity is also informed by means of this service primitive, indicating the current transfer capability. + +This primitive may be used in response to an NS-UNITDATA-Request primitive which the NS is unable to serve because of e.g. NS-VC failure. + +This primitive may also be used upon recovery after a failure affecting the NS. + +### 5.2.2 Parameters + +#### 5.2.2.1 NS SDU + +The NS SDUs are specified in 3GPP TS 48.018. They shall never be inspected by the Network Service entity. + +#### 5.2.2.2 Link Selector Parameter + +The Link Selector Parameter is included in the NS-UNITDATA-Request primitive for load sharing purposes as described in sub-clause "Requirements on load sharing function". + +The Link Selector Parameter is included in the NS-UNITDATA-Indication primitive and in the NS-UNITDATA-Request primitive for resource distribution purposes as described in sub-clause 4.4a.1. The Link Selector Parameter shall include a reference to the local IP endpoint and the remote IP endpoint for resource distribution purposes if the NS Change IP endpoint parameter has the cause value of "request change flow". + +#### 5.2.2.3 BVCI I and NSEI + +BVCI and NSEI parameters are included in the service primitives to identify the BVC for which the service is provided. These parameters are used by the NS entity to multiplex the NS SDUs over the NS-VCs. + +#### 5.2.2.4 Congestion cause + +The congestion cause shall indicate the affected direction of transmission and may be set to the following values: + +- a) congestion detected, backward; +- b) end of congestion, backward; +- c) congestion detected, forward; +- d) end of congestion, forward. + +#### 5.2.2.5 Transfer capability + +This parameter is used to report to the NS user entity the current transfer capacity available for a BVC, in terms of bandwidth. This parameter may be set to any value from "0" (zero) to the maximum bandwidth provided by the complete set of NS-VCs associated to the BVC. + +#### 5.2.2.6 NS affecting cause + +This parameter is used to indicate to the NS user entity the reason which caused the NS-STATUS-Indication primitive to be used. The cause values are: + +- NS-VC failure: a failure is affecting one or more NS-VCs, the NS is still available. +- NS-VC recovery: one or more NS-VCs which were in failure are available again. +- NS failure: the NS can not provide data transfer services to the NS user. +- NS recovery: the NS can provide data transfer services again. + +#### 5.2.2.7 NS change IP endpoint + +The NS change IP endpoint parameter is included in the NS-UNITDATA-Request and NS-UNITDATA-Indication primitive for resource distribution purposes. This parameter is used in an IP sub-network to indicate to the NS user entity a request for change in IP endpoint or a response to a change in IP endpoint. The cause values are: + +- Request change flow: Request to change the IP endpoint at which to receive NS SDUs associated with a subscriber or MBMS session. +- Confirm change flow: Confirmation to a request for change of IP endpoint of NS SDUs associated with a subscriber or MBMS session. + +# 6 Sub-Network Service protocol + +## 6.1 Frame Relay support of the Sub-Network Service protocol + +### 6.1.1 Overview + +The Gb interface may consist of direct point-to-point connections between the BSS and the SGSN, or an intermediate Frame Relay network may be placed between both ends of the Gb interface. Other intermediate equipments may be traversed. Several configurations are possible, the detail of which is outside the scope of the present document. For the purposes of the present document the following two types of configurations have to be considered: + +- Point-to-point physical connections. +- Intermediate Frame Relay network. + +In case of an intermediate Frame Relay network, both BSS and SGSN shall be treated as the user side of the user-to-network interface. The network-to network interface is outside the scope of the present document. + +Only Frame Relay permanent virtual connections (PVCs) shall be used on the Gb interface. Therefore ITU-T Recommendation Q.922 Annex A or T1.618 for PCS1900 and ITU-T Recommendation Q.933 Annex A or T1.617 for PCS1900, permanent virtual connection procedures, shall be supported. Switched virtual connection procedures in ITU-T Recommendation Q.922 or T1.618 for PCS1900 and ITU-T Recommendation Q.933 or T1.617 for PCS1900 shall not be supported. ITU-T Recommendation Q.921 or T1.602 and ITU-T Recommendation Q.931 procedures shall not be applicable. + +The Frame Relay user-to-network interface (UNI) shall be implemented on the Gb interface according to the FRF 1.1 agreement, unless otherwise stated in the present document. Selected options or deviations from FRF 1.1 are specified in the rest of this Frame Relay chapter. Where discrepancies arise between the present document and the above mentioned recommendations, the present document takes precedence. + +The rest of this Frame Relay sub-clause applies only to PVC usage. + +The Gb interface addressing principles shall be applied as follows: + +- The physical link is the Frame Relay bearer channel. +- The NS-VL is the local link in one end (at UNI) of the Frame Relay PVC. +- The NS-VLI is the Frame Relay DLCI together with the bearer channel identifier. +- The NS-VC is the Frame Relay PVC. +- The Sub-Network Service entity is the Frame Relay entity. + +### 6.1.2 Network configuration + +The Gb interface is a User-to-Network (UNI) interface, as defined in FRF 1.1. Two configurations are possible, either a direct link configuration or PVC(s) via a Frame Relay network. + +Annex A shows an example of each type of configuration. + +In case of point-to-point connections, the BSS shall be considered as the user side of the user-to-network interface, the SGSN shall be considered as the network side, see figure 6.1.2.1. + +![Diagram of direct link configuration showing BSS (user) connected to SGSN (network) via the Gb interface.](daae5239bb53d468ea958aedfc2e6070_img.jpg) + +The diagram illustrates a direct link configuration for the Gb interface. It features two rectangular boxes: the left box is labeled 'BSS (user)' and the right box is labeled 'SGSN (network)'. A horizontal line connects the two boxes. Centered on this line is a vertical double-headed arrow pointing both up and down. Above the arrow, the label 'Gb' is placed, indicating the interface name. + +Diagram of direct link configuration showing BSS (user) connected to SGSN (network) via the Gb interface. + +**Figure 6.1.2.1: Direct link configuration** + +In case of an intermediate Frame Relay network, both BSS and SGSN shall be treated as the user side of the user-to-network interface, see figure 6.1.2.2. The network-to network interface is outside the scope of the present document. + +![Diagram showing a BSS (user) connected to a Frame Relay network via a Gb interface, which is then connected to an SGSN (user) via another Gb interface.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` +graph LR; BSS[BSS (user)] <--> |Gb| FRN((Frame Relay network)); FRN <--> |Gb| SGSN[SGSN (user)]; +``` + +Diagram showing a BSS (user) connected to a Frame Relay network via a Gb interface, which is then connected to an SGSN (user) via another Gb interface. + +**Figure 6.1.2.2: PVC via a Frame Relay Network** + +### 6.1.3 Services expected from layer 1 + +In the context of Frame Relay, the physical link is referred to as the bearer channel. + +The Frame Relay protocol shall be run across permanently reserved bearer channels on the Gb interface, see 3GPP TS 48.014. + +### 6.1.4 Options selected from FRF 1.1 + +#### 6.1.4.1 Support of DL-CONTROL sub-layer + +No end-to-end DL-CONTROL sub-layer shall be implemented on the Gb interface. + +#### 6.1.4.2 Frame length + +The default maximum information field size of 1 600 octets shall be supported on the Gb interface. Maximum information field sizes greater than 1 600 octets may be agreed to between Frame Relay network operators and users at subscription time. + +#### 6.1.4.3 Congestion control procedures + +Congestion control is defined in FRF 1.1 and consists of congestion avoidance and congestion recovery mechanisms. + +Congestion control on the Gb interface consists of congestion avoidance based on the DE bit and on explicit notifications via the FECN and BECN bits within the address field of the Frame Relay frame. + +Congestion avoidance based on the CLLM message (see ITU-T Recommendation Q.922 sub-clause A.7 or T1.618 for PCS1900 and FRF 1.1 sub-clause 2.2.5) is not required at the BSS and SGSN sides. + +No congestion control mechanism based on implicit congestion detection (see ITU-T Recommendation Q.922 sub-clause A.6.1) or T1.618 for PCS1900 is required at the BSS and SGSN sides. + +##### 6.1.4.3.1 DE bit usage + +The BSS and the SGSN shall always set the DE bit to 0 (zero). + +##### 6.1.4.3.2 FECN and BECN bit usage + +###### Setting of the FECN and BECN bits: + +The FECN and BECN bits shall be set to 0 by the BSS and the SGSN. + +###### Reaction upon receipt of FECN or BECN marked frames: + +The reaction of the BSS and the SGSN upon reception of FECN or BECN marked frames is implementation dependent. + +It is recommended to implement ITU-T Recommendation Q.922 appendix I.2 or T1.618 for PCS1900 procedures or similar procedures, so that the NS entity can reduce or increase the transmission rate, depending on the FECN or BECN bits received. + +The NS entity shall be able to report the congestion situation to the upper layer. The criteria to be met for congestion being reported to the upper layer are implementation dependent. The upper layer is expected to reduce or increase its + +transmission rate as appropriate. It shall be up to the upper layer to perform further appropriate actions e.g. flow control with its peer entity, see ITU-T Recommendation I.370 or T1.606 for PCS1900. + +#### 6.1.4.4 Signalling procedures + +ITU-T Recommendation Revised Q.933 annex A or T1.617 for PCS1900 procedures shall be implemented at the BSS and the SGSN sides as recommended in FRF 1.1 sub-clause 2.3. + +On the Gb interface, these procedures shall be initiated by the user side of the UNI, reverse procedures shall not be used. + +Only periodic polling shall be used, asynchronous status message needs not to be supported. + +Switched virtual connection procedures , see FRF 1.1 sub-clause 2.3.2, shall not be implemented. + +#### 6.1.4.5 C/R bit usage + +The C/R bit shall not be used and shall be set to 0 by the sending entity. It shall not be checked by the receiving entity. + +### 6.1.5 Abnormal conditions + +Upon detection of the unavailability of a PVC by the Frame Relay entity or when a PVC becomes available again, the Network Service Control entity shall be informed. Unavailability cases are described in Recommendations ITU-T Recommendation Q.922 or T1.618 for PCS1900 and ITU-T Recommendation Q.933 annex A or T1.617 for PCS1900. + +## 6.2 IP Support of the Sub-Network Service Protocol + +### 6.2.1 Overview + +The IP Sub-Network shall use the Internet Protocol (IP) as defined in either RFC 791 or RFC 2460 and the User Datagram Protocol (UDP) as defined in RFC 768. + +The connections between the BSS and the SGSN may consist of point-to-point connections or of an intermediate IP network. Several configurations are possible, the details of which are outside the scope of the present document. For the purposes of the present document the following characteristics have to be considered: + +- 1) The Sub-Network Service (SNS) may be configured by administrative means (i.e. static configuration) or by auto-configuration procedures (i.e. dynamic configuration). In the case of auto-configuration the operator shall ensure, in advance, that each NSE can fulfil its peer NSE requirements (e.g. maximum number of NS-VCs, maximum number of IP-endpoints). +- 2) Administrative configuration means the administration of the NSEs' IP endpoints (including the Signalling Weight and Data Weight). +- 3) In the case of a point-to-point connection, the administrative configuration shall be used. In the case of an intermediate IP network connection, then either the administrative means or the auto-configuration procedures may be used. +- 4) The BSS NSE has no knowledge of the configuration of any other BSS NSEs. +- 5) The auto-configuration procedures are used to exchange configuration information between the BSS and the SGSN. The client/server principle applies: the SGSN is the server, while the BSS is a client. The BSS shall have knowledge of at least one SGSN IP endpoint, referred to as pre-configured endpoint hereafter, to initiate the procedures. The auto-configuration procedures consist of the following: + - a) After start-up the BSS NSE reports to the peer-SGSN NSE by initiating the Size procedure. + - b) Then, the BSS initiates the Configuration Procedure in which a sequence of messages are exchanged between the BSS and the SGSN containing signalling endpoints, data endpoints, and initial weights. + +A pre-configured endpoint shall not be used for NSE data or signalling traffic (with the exception of Size and Configuration procedures) unless it is configured by the SGSN using the auto-configuration procedures. + +- 6) A network connection as part of the intermediate IP network between the NSEs shall be terminated by the same type of IP addresses (e.g. IPv4 or IPv6). +- 7) For dynamic configurations the change of initially configured parameters shall be supported by the Add procedure, Delete procedure and ChangeWeight procedure. +- 8) The SNS messages (SNS SIZE, SNS CONFIG, SNS ADD, SNS DELETE, SNS CHANGEWEIGHT) serving to support the configuration, Size, Add, Delete and ChangeWeight procedures shall only be used in the case of dynamic configuration. + +### 6.2.1a Abnormal Conditions + +If the BSS or SGSN NSE receives at a given IP endpoint an SNS PDU containing an unknown NSEI or an NSEI associated to a different local IP endpoint, the BSS or SGSN NSE may simply discard such SNS PDU without further action. + +### 6.2.2 IP Fragmentation + +Fragmentation should be avoided if possible. Examples of fragmentation drawbacks are, e.g.: + +- Fragmentation is inefficient, since the complete IP header is duplicated in each fragment. +- If one fragment is lost, the complete packet has to be discarded. The reason is that no selective retransmission of fragments is possible. + +Mechanisms used to avoid fragmentation are outside the scope of the present document. + +### 6.2.3 Services expected from layer 1 and layer 2 + +Layer one and two are unspecified. No services are defined in the present document. + +### 6.2.4 Size Procedure + +This procedure is initiated by the BSS. The Size procedure shall be performed to: + +- Reset all information maintained by the BSS NSE and its peer prior to the configuration procedure. +- Verify that the number of NS-VCs that can be supported by the BSS NSE is greater than or equal to the number of NS-VCs required for full mesh connectivity to the peer SGSN NSE. +- Verify that the number of IP endpoints indicated by the BSS NSE can be supported by the SGSN NSE. +- Verify the compatibility between the type of IP addresses (IPv4/IPv6) supported by the peer NSEs. + +The BSS NSE shall send an SNS-SIZE PDU to the SGSN using any of the pre-configured SGSN IP endpoints (configuring of any pre-configured SGSN IP endpoints is out of the scope of the present document). The BSS shall start timer Tsns-prov. The SNS\_SIZE PDU shall contain the following information elements: + +- NSEI: NSE Identifier. +- Maximum Number of NS-VCs: maximum number of NS-VCs the BSS NSE can support. +- Reset Flag: indicates whether all configuration information between the BSS NSE and its peer SGSN NSE shall be cleared prior to a forthcoming initiation of the configuration procedure by the BSS NSE (Reset-bit field of the *Reset Flag* IE set to "1"), or if the procedure is only initiated to ascertain the ability of the SGSN NSE to support the requested capabilities (Reset-bit field of the *Reset Flag* IE set to "0"). +- Number of IP4 Endpoints: maximum number of BSS NSE IPv4 addresses that the BSS NSE is allowed to configure through the forthcoming configuration procedure and/or +- Number of IP6 Endpoints: maximum number of BSS NSE IPv6 addresses that the BSS NSE is allowed to configure through the forthcoming configuration procedure. + +Upon receipt of an SNS-SIZE PDU, the SGSN shall: + +- If the Reset-bit field of the *Reset Flag* IE is set to "1", clear all previous operating information about the BSS NSE (no operating information shall be affected in the SGSN if the Reset-bit field of the *Reset Flag* IE is set to "0"). +- Send an SNS-SIZE-ACK PDU to the source IP endpoint. The SNS-SIZE-ACK PDU shall contain the NSEI IE. The SNS-SIZE-ACK PDU may contain the *Cause* IE as specified in sub-clause 6.2.4.1. + +Upon receipt of an SNS-SIZE-ACK PDU the BSS shall: + +- Stop timer Tsns-prov. +- If the Reset-bit field of the *Reset Flag* IE was set to "1" in the SNS-SIZE PDU sent by the BSS, initiate the configuration procedure (see sub-clause 6.2.5). + +#### 6.2.4.1 Abnormal Conditions + +If the maximum number of NS-VCs indicated in the SNS-SIZE PDU is less than the number of NS-VCs required for full mesh connectivity between the peer NSEs, the SGSN shall send an SNS-SIZE-ACK PDU with a cause code "Invalid number of NS-VCs". The number of NS-VCs required for full mesh connectivity between peer NSEs is the product of the number of IPv4 endpoints supported on each of the peer NSEs plus the product of the number of IPv6 endpoints supported on each of the peer NSEs. + +Upon receiving the SNS-SIZE-ACK PDU with a cause code "Invalid number of NS-VCs" the BSS NSE may notify the O&M system and abort the procedure. + +If the SGSN does not support the type of IP addresses (IPv4/IPv6) offered by the BSS, the SGSN shall send an SNS-SIZE-ACK PDU with a cause code "Invalid number of IP4 Endpoints" or "Invalid number of IP6 Endpoints". Upon receiving the SNS-SIZE-ACK PDU with a cause code "Invalid number of IP4 Endpoints" or "Invalid number of IP6 Endpoints" the BSS NSE may notify the O&M system and abort the procedure. + +If the SGSN does not support the number of IPv4 endpoints indicated in the SNS-SIZE PDU, the SGSN shall send an SNS-SIZE-ACK PDU with a cause code set to "Invalid number of IP4 Endpoints". If the SGSN does not support the number of IPv6 endpoints indicated in the SNS-SIZE PDU, the SGSN shall send an SNS-SIZE-ACK PDU with a cause code set to "Invalid number of IP6 Endpoints". Upon receiving the SNS-SIZE-ACK PDU with a cause code set to "Invalid number of IP4 Endpoints" or "Invalid number of IP6 Endpoints", the BSS NSE may notify the O&M system and abort the procedure. + +Upon expiry of timer Tsns-prov the NSE may retry the operation SNS-SIZE-RETRIES times. If the operation has been attempted SNS-SIZE-RETRIES times without acknowledgement from the peer NS entity, then the NS entity may notify the O&M system and abort the procedure. Whether the NS entity would restart the size procedure using any pre-configured SGSN IP endpoints after abortion is left implementation dependent. Further actions are outside the scope of the present document. + +### 6.2.5 Configuration Procedure + +The configuration procedure is used on the Gb interface to exchange configuration information between an NSE and its peer NSE. To start the configuration procedure, the client/server principle is used, with the BSS as the client. Upon start-up/restart of a BSS NSE or following the detection of a restart of a peer SGSN NSE (e.g. by means of the test procedure - see sub-clause 7.4b), the Size procedure with the Reset-bit field of the *Reset Flag* IE set to "1" in the SNS-SIZE PDU shall be performed upon initiation by the BSS NSE before the configuration procedure is started. + +After completion on the BSS side of the Size procedure having indicated a reset, the BSS NSE shall send an SNS-CONFIG PDU to the same pre-configured SGSN IP endpoint used in the Size procedure. + +NOTE: This does not imply that the SNS-CONFIG PDU has to be sent from the same IP endpoint used in the Size procedure. + +The BSS shall start timer Tsns-prov. The SNS-CONFIG PDU shall contain the following information elements: + +| | | +|-----------------------|---------------------------------------------------------| +| NSEI: | NSE Identifier. | +| End Flag: | identifies the last SNS-CONFIG PDU sent by the BSS NSE. | +| List of IP4 Elements: | one or more IPv4 endpoints, or | + +List of IP6 Elements: one or more IPv6 endpoints. + +Upon receipt of an SNS-CONFIG PDU sent by the BSS, the SGSN shall send an SNS-CONFIG-ACK PDU to the source IP endpoint. + +Upon receipt of an SNS-CONFIG-ACK PDU sent by the SGSN, the BSS shall: + +- Stop timer Tsns-prov. +- Repeat the above SNS-CONFIG PDU sequence to the SGSN if the BSS has more IP endpoints to configure. + +After completion on the SGSN side of the Size procedure, the SGSN shall send an SNS-CONFIG PDU to the BSS NSE using any known signalling IP endpoints (i.e., from information contained within an SNS-CONFIG PDU sent by the BSS). The SGSN shall start timer Tsns-prov. The SNS-CONFIG PDU shall contain the following information elements: + +NSEI: NSE Identifier. + +End Flag: identifies the last SNS-CONFIG PDU sent by the SGSN NSE. + +List of IP4 Elements: one or more IPv4 endpoints, or + +List of IP6 Elements: one or more IPv6 endpoints. + +Upon receipt of an SNS-CONFIG PDU sent by the SGSN, the BSS shall send an SNS-CONFIG-ACK PDU to the source IP endpoint. + +Upon receipt of an SNS-CONFIG-ACK PDU sent by the BSS, the SGSN shall: + +- Stop timer Tsns-prov. +- Repeat the above SNS-CONFIG PDU sequence to the BSS if the SGSN has more IP endpoints to configure. The SGSN shall start timer Tsns-prov. + +Neither the SGSN nor the BSS shall initiate any other procedure before receiving the peer's end-flag. + +#### 6.2.5.1 Abnormal Conditions + +Upon receiving an SNS-CONFIG PDU with the E-bit field in the *End Flag* IE set to "1", if the total number of IPv4 elements sent to the SGSN by the BSS NSE is greater than the number of IPv4 endpoints sent by the BSS NSE in the SIZE PDU, the SGSN shall send an SNS-CONFIG-ACK PDU with a cause code of "Invalid number of IP4 Endpoints". The SGSN shall clear all information associated with the peer BSS NSE. + +Upon receiving an SNS-CONFIG-ACK PDU with a cause code set to "Invalid number of IP4 Endpoints" the BSS may notify the O&M system and abort the procedure. Further actions are outside the scope of the present document. The BSS shall clear all information associated with the peer SGSN NSE. + +Upon receiving an SNS-CONFIG PDU with the E-bit field in the *End Flag* IE set to "1", if the total number of IPv6 elements sent to the SGSN by the BSS NSE is greater than the number of IPv6 endpoints sent by the BSS NSE in the SIZE PDU, the SGSN shall send an SNS-CONFIG-ACK PDU with a cause code of "Invalid number of IP6 Endpoints". The SGSN shall clear all information associated with the peer BSS NSE. + +Upon receiving an SNS-CONFIG-ACK PDU with a cause code set to "Invalid number of IP6 Endpoints" the BSS may notify the O&M system and abort the procedure. Further actions are outside the scope of the present document. The BSS shall clear all information associated with the peer SGSN NSE. + +Upon receiving an SNS-CONFIG PDU with the E-bit field in the *End Flag* IE set to "1", if the total number of IPv4 elements sent to the BSS by the SGSN NSE is greater than the number of IPv4 endpoints supported by the BSS NSE, the BSS shall send an SNS-CONFIG-ACK PDU with a cause code set to "Invalid number of IP4 Endpoints" and clear all information associated with the peer SGSN NSE. + +Upon receiving an SNS-CONFIG PDU with the E-bit field in the *End Flag* IE set to "1", if the total number of IPv6 elements sent to the BSS by the SGSN NSE is greater than the number of IPv6 endpoints supported by the BSS NSE, the BSS shall send an SNS-CONFIG-ACK PDU with a cause code set to "Invalid number of IP6 Endpoints" and clear all information associated with the peer SGSN NSE. + +Upon receiving an SNS-CONFIG-ACK PDU with a cause code set to "Invalid number of IP4 Endpoints" or "Invalid number of IP6 Endpoints" the SGSN may notify the O&M system and abort the procedure. Further actions are outside the scope of the present document. The SGSN shall clear all information associated with the peer BSS NSE. + +Upon receiving an SNS-CONFIG PDU with the E-bit field in the *End Flag* IE set to "1", if the resulting sum of the signalling weights of all the peer IP endpoints configured for this NSE is equal to zero or if the resulting sum of the data weights of all the peer IP endpoints configured for this NSE is equal to zero the NSE shall send an SNS-CONFIG-ACK PDU with a cause code of "Invalid weights". The NSE shall clear all information associated with the peer NSE. Upon receiving an SNS-CONFIG ACK PDU with cause code set to "Invalid weights" the NSE shall clear all information associated with the peer NSE and may notify the O&M system. + +Upon expiry of timer Tsns-prov the NSE may retry the operation SNS-CONFIG-RETRIES times. If the operation has been attempted SNS-CONFIG-RETRIES times without acknowledgement from the peer NSE, then the NSE may notify the O&M system and abort the procedure. Further actions are outside the scope of the present document. + +### 6.2.6 Add Procedure + +The Add procedure is used by an NSE to configure additional IP endpoints. + +To add new IP endpoints, the NSE shall send an SNS-ADD PDU to a peer NSE signalling endpoint. Upon sending the SNS-ADD PDU the NSE shall start timer Tsns-prov. The SNS-ADD PDU shall contain the following information elements: + +| | | +|-----------------------|------------------------------------------------| +| NSEI: | NSE Identifier. | +| Transaction ID: | identifies a unique transaction within an NSE. | +| List of IP4 Elements: | one or more IPv4 endpoints, or. | +| List of IP6 Elements: | one or more IPv6 endpoints. | + +Upon receipt of an SNS-ADD PDU the NSE shall send an SNS-ACK PDU to the source IP endpoint from which the SNS-ADD PDU was sent. The SNS-ACK PDU shall contain the Transaction ID set to the same value as that in the SNS-ADD PDU. + +Upon receipt of an SNS-ACK PDU the NSE shall stop timer Tsns-prov. + +#### 6.2.6.1 Abnormal Conditions + +Upon receiving an SNS-ADD PDU, if the consequent number of NS-VCs exceeds the maximum own supported number of NS-VCs then the NSE shall send an SNS-ACK PDU with cause code set to "Invalid number of NS-VCs". + +Upon receiving an SNS-ADD PDU, if the consequent number of IPv4 endpoints exceeds the number of IPv4 endpoints supported by the NSE, the NSE shall send an SNS-ACK PDU with a cause code set to "Invalid number of IP4 Endpoints". + +Upon receiving an SNS-ADD PDU, if the consequent number of IPv6 endpoints exceeds the number of IPv6 endpoints supported by the NSE, the NSE shall send an SNS-ACK PDU with a cause code set to "Invalid number of IP6 Endpoints". + +Upon receiving an SNS-ADD PDU containing an already configured IP endpoint the NSE shall send an SNS-ACK PDU with the cause code "Protocol error - unspecified". + +For any of the abnormal cases specified above: + +- The whole content of the received SNS-ADD PDU shall be ignored. +- The SNS-ACK PDU shall be sent to the source IP endpoint from which the SNS-ADD PDU was sent. The SNS-ACK PDU shall contain the Transaction ID set to the same value as that in the SNS-ADD PDU. + +Upon expiry of timer Tsns-prov the NSE may retry the operation SNS-ADD-RETRIES times. If the operation has been attempted SNS-ADD-RETRIES times without acknowledgement from the peer NSE, then the NSE may notify the O&M system and abort the procedure. Further actions are outside the scope of the present document. + +### 6.2.7 Delete Procedure + +The delete procedure is used by an NSE to remove previously configured IP endpoints from service. + +To delete IP endpoints, the NSE shall send an SNS-DELETE PDU to a peer NSE signalling endpoint. Upon sending the SNS-DELETE PDU the NSE shall start timer Tsns-prov. The SNS-DELETE PDU shall contain the following information elements: + +| | | +|-----------------------|---------------------------------------------------------------| +| NSEI: | NSE Identifier. | +| Transaction ID: | identifies a unique transaction within the NSE. | +| IP Address: | all IP endpoints that use this IP address shall be deleted or | +| List of IP4 Elements: | one or more IPv4 endpoints, or | +| List of IP6 Elements: | one or more IPv6 endpoints. | + +Upon receipt of an SNS-DELETE PDU the NSE shall send an SNS-ACK PDU to the source IP endpoint from which the SNS-DELETE PDU was sent. The SNS-ACK PDU shall contain the Transaction ID set to the same value as that in the SNS-DELETE PDU. + +Upon receipt of an SNS-ACK PDU the NSE shall stop timer Tsns-prov. + +#### 6.2.7.1 Abnormal Conditions + +Upon receiving an SNS-DELETE PDU containing one or more IP endpoints that has not been previously configured with an SNS-ADD PDU or an SNS-CONFIG PDU, the NSE shall send an SNS-ACK PDU with a cause code of "Unknown IP endpoint" to the source IP endpoint from which the SNS-DELETE PDU was sent. The SNS-ACK PDU shall contain the Transaction ID set to the same value as that in the SNS-DELETE PDU. The NSE shall also include, in the SNS-ACK PDU, all IPv4 endpoints in the SNS-DELETE PDU that have not been previously configured in the *List of IP4 Elements* IE, or all IPv6 endpoints in the SNS-DELETE PDU that have not been previously configured in the *List of IP6 Elements* IE. All previously configured IP endpoints contained in the SNS-DELETE PDU shall be deleted. + +Upon receiving an SNS-DELETE PDU containing an IP address for which no IP endpoints have been previously configured with an SNS-ADD PDU or an SNS-CONFIG PDU, the NSE shall send an SNS-ACK PDU with a cause code of "Unknown IP address" to the source IP endpoint from which the SNS-DELETE PDU was sent. The SNS-ACK PDU shall contain the Transaction ID set to the same value as that in the SNS-DELETE PDU. The NSE shall also include, in the SNS-ACK PDU, the IP address received in the SNS-DELETE PDU. + +Upon expiry of timer Tsns-prov the NSE may retry the operation SNS-DELETE-RETRIES times. If the operation has been attempted SNS-DELETE-RETRIES times without acknowledgement from the peer NSE, then the NSE may notify the O&M system and abort the procedure. Further actions are outside the scope of the present document. + +### 6.2.8 ChangeWeight Procedure + +The ChangeWeight procedure is used by an NSE to change the signalling weight and/or data weight of the specified IP endpoints. + +To change the signalling weight and/or data weight of an IP endpoint, the NSE shall send an SNS-CHANGEWEIGHT PDU to a peer NSE signalling endpoint. Upon sending the SNS-CHANGEWEIGHT PDU the NSE shall start timer Tsns-prov. The SNS-CHANGEWEIGHT PDU shall contain the following information elements: + +| | | +|-----------------------|-------------------------------------------------| +| NSEI: | NSE Identifier. | +| Transaction ID: | identifies a unique transaction within the NSE. | +| List of IP4 Elements: | one of more IPv4 endpoints, or | +| List of IP6 Elements: | one or more IPv6 endpoints. | + +Upon receipt of an SNS-CHANGEWEIGHT PDU the NSE shall send an SNS-ACK PDU to the source IP endpoint from which the SNS-CHANGEWEIGHT PDU was sent. The SNS-ACK PDU shall contain the Transaction ID set to the same value as that in the SNS-CHANGEWEIGHT PDU. + +Upon receipt of an SNS-ACK PDU the NSE shall stop timer Tsns-prov. + +#### 6.2.8.1 Abnormal Conditions + +Upon receiving an SNS-CHANGEWEIGHT PDU, if the resulting sum of the signalling weights of all the peer IP endpoints configured for this NSE is equal to zero or if the resulting sum of the data weights of all the peer IP endpoints configured for this NSE is equal to zero, the BSS/SGSN shall send an SNS-ACK PDU with a cause code of "Invalid weights". The whole content of that SNS-CHANGEWEIGHT PDU shall be ignored. + +Upon receiving an SNS-CHANGEWEIGHT PDU containing one or more IP endpoints that has not been previously configured with an SNS-ADD PDU or an SNS-CONFIG PDU, the NSE shall send an SNS-ACK PDU with a cause code of "Unknown IP endpoint" to the source IP endpoint from which the SNS-CHANGEWEIGHT PDU was sent. The SNS-ACK PDU shall contain the Transaction ID set to the same value as that in the SNS-CHANGEWEIGHT PDU. The NSE shall also include, in the SNS-ACK PDU, all IPv4 endpoints sent in the SNS-CHANGEWEIGHT PDU that have not been previously configured in the *List of IP4 Elements* IE, or all IPv6 endpoints sent in the SNS-CHANGEWEIGHT PDU that have not been previously configured in the *List of IP6 Elements* IE. The NSE shall discard the information in the SNS-CHANGEWEIGHT PDU associated with all IP endpoints that have not been previously configured. All previously configured IP endpoints contained in the SNS-CHANGEWEIGHT PDU shall be changed. + +Upon expiry of timer Tsns-prov the NSE may retry the operation SNS-CHANGEWEIGHT-RETRIES times. If the operation has been attempted SNS-CHANGEWEIGHT-RETRIES times without acknowledgement from the peer NSE, then the NSE may notify the O&M system and abort the procedure. Further actions are outside the scope of the present document. + +# --- 7 Network Service Control protocol + +## 7.1 Procedures for the transmission of NS SDUs + +NS SDUs are transmitted in unacknowledged mode across the Gb interface by means of an NS-UNITDATA PDU. + +The NS-UNITDATA PDU is used in both BSS-to-SGSN and SGSN-to-BSS directions. + +For an IP sub-network, an NS-UNITDATA PDU for a PTP BVC may indicate a request to change the IP endpoint and/or a response to a change in the IP endpoint. + +If the BSS or SGSN receives an NS-UNITDATA PDU for a signalling BVC or a PTM BVC then the BSS or SGSN shall ignore the coding of the C-bit and R-bit. + +### 7.1.1 Abnormal Conditions + +If the BSS receives an NS-UNITDATA PDU including a BVCI not associated to the NS-VC where the PDU was received, the BSS shall return an NS-STATUS PDU on that NS-VC, cause "BVC unknown on that NSE". Depending on the implementation, the BSS may then ignore the BVCI and treat the rest of the NS-UNITDATA PDU. + +## 7.2 Blocking / unblocking procedures + +The Blocking/Unblocking procedures shall not be used for an IP Sub-network. + +When a BSS (or SGSN) wishes to block an NS-VC between a BSS and SGSN, the following shall be performed: + +- The transmitting side at the BSS (or SGSN) shall mark the NS-VC as blocked and shall inform the load sharing function. This results in the redistribution of NS-UNITDATA PDUs to other unblocked NS-VCs of the same group, as described in the "Load sharing function" sub-clause. The NS user entity shall also be informed of the new transfer capability by means of an NS-STATUS-Indication primitive for each affected BVC. A BSS (or SGSN) then sends an NS-BLOCK PDU to the peer entity and starts timer Tns-block. + +- The NS-BLOCK PDU contains the NS-VCI and a Cause element indicating the reason for blocking (typical cause values: Transit network failure, O&M intervention, Equipment failure). The NS-BLOCK PDU may be sent in any alive (blocked or unblocked) NS-VC pertaining to the same group as the NS-VC to be blocked, unless otherwise required for particular cases which may be further described in the rest of the present document. +- At the sending side of the NS-BLOCK PDU, if no failure has occurred in the receive direction (e.g. O&M intervention), the originator of the NS-BLOCK PDU shall continue to accept NS-UNITDATA PDUs received on the NS-VC being blocked, until an NS-BLOCK-ACK PDU is received for this NS-VC. The originator of the NS-BLOCK PDU shall stop to accept NS-UNITDATA PDUs, if the number of retries of the blocking procedures is exceeded. +- Upon Receipt of an NS-BLOCK PDU at an SGSN (or BSS) the NS-VC shall be marked as blocked. The SGSN (or BSS) shall immediately inform the load sharing function. The NS user entity shall also be informed of the new transfer capability by means of an NS-STATUS-Indication primitive for each affected BVC. The SGSN (or BSS) then sends in any alive (blocked or unblocked) NS-VC of the relevant group an NS-BLOCK-ACK PDU, for the blocked NS-VC, to the BSS (or SGSN). +- On receipt of an NS-BLOCK-ACK PDU or NS-BLOCK PDU, the originator of the NS-BLOCK PDU stops timer Tns-block. + +The NS-VC shall remain blocked until an NS-UNBLOCK PDU is received indicating that the NS-VC's state has been changed. + +When a BSS (or SGSN) wishes to unblock an NS-VC between a BSS and SGSN, the following shall be performed: + +- The BSS (or SGSN) sends an NS-UNBLOCK PDU to the peer entity and starts timer Tns-block. The NS-UNBLOCK PDU shall be sent on the NS-VC to be unblocked (the NS-VC must be alive, see check procedure in sub-clauses "Test of an NS-VC"). The BSS or SGSN may discard any NS-UNITDATA PDU received on the concerned NS-VC until the reception of the NS-UNBLOCK-ACK PDU. +- If an NS-UNBLOCK PDU is received by an SGSN (or BSS) for an NS-VC and the SGSN (or BSS) is able to unblock the NS-VC, the SGSN (or BSS) shall return an NS-UNBLOCK-ACK PDU on the NS-VC where the NS-UNBLOCK PDU was received, then the NS-VC shall be marked as unblocked. The load sharing function shall be informed. The NS user entity shall also be informed of the new transfer capability by means of an NS-STATUS-Indication primitive for each affected BVC. +- A BSS (or SGSN) shall stop timer Tns-block on receipt of an NS-UNBLOCK-ACK or NS-UNBLOCK PDU, shall mark the NS-VC as unblocked and shall inform the load sharing function in order to allow transmission of NS-UNITDATA PDUs on this NS-VC. The NS user entity shall also be informed of the new transfer capability by means of an NS-STATUS-Indication primitive for each affected BVC. An NS-UNBLOCK PDU received while a BSS (or SGSN) is waiting for an NS-UNBLOCK-ACK PDU shall be acknowledged with an NS-UNBLOCK-ACK PDU. +- If an NS-UNBLOCK PDU is received by an SGSN (or BSS) and the SGSN (or BSS) is not able to unblock the NS-VC, the NS-VC shall remain blocked and the NS-VC blocking procedure shall be initiated by returning an NS-BLOCK PDU to the BSS (or SGSN). This NS-BLOCK PDU shall be sent on the NS-VC where the NS-UNBLOCK PDU was received. +- If a BSS (or SGSN) receives an NS-BLOCK PDU while waiting for an NS-UNBLOCK-ACK PDU, it shall stop timer Tns-block and the NS-VC shall remain blocked. An NS-BLOCK-ACK PDU shall be returned. An indication shall be issued towards the O&M system, announcing that the unblocking of the NS-VC was not possible at the peer entity. Further actions of the O&M system are out of the scope of the present document. + +### 7.2.1 Abnormal Conditions + +If an NS-BLOCK-ACK PDU is not received for an NS-BLOCK PDU within Tns-block seconds, then the NS-BLOCK PDU procedure shall be repeated a maximum of NS-BLOCK-RETRIES attempts. After NS-BLOCK-RETRIES unsuccessful retry attempts the procedure is stopped and the O&M system is informed that the blocking procedure has failed. Further actions of the O&M system are out of the scope of the present document. The NS-VC shall be marked as blocked at the originating side of the blocking procedure. + +If an NS-UNBLOCK-ACK PDU is not received for an NS-UNBLOCK PDU within Tns-block seconds, the NS-UNBLOCK PDU procedure shall be repeated a maximum of NS-UNBLOCK-RETRIES attempts. After NS-UNBLOCK-RETRIES unsuccessful retry attempts the procedure is stopped and the O&M system is informed that the + +unblocking procedure has failed. Further actions of the O&M system are out of the scope of the present document. The NS-VC shall be marked as blocked at the originating side of the unblocking procedure. + +If an NS-UNITDATA PDU is received on an NS-VC that is marked at a BSS or an SGSN as blocked and no NS-VC unblocking procedure is pending, then an NS-STATUS PDU (Cause value: NS-VC blocked) shall be returned to the peer entity. + +If an NS-BLOCK PDU is received by a BSS or an SGSN for a blocked NS-VC, an NS-BLOCK-ACK PDU shall be returned. + +If an NS-UNBLOCK PDU is received by a BSS or an SGSN for an unblocked NS-VC, an NS-UNBLOCK-ACK PDU shall be returned. + +If an unexpected NS-BLOCK-ACK PDU is received by a BSS or an SGSN and it is related to an NS-VC that is locally blocked, the NS-BLOCK-ACK PDU is discarded. If the NS-BLOCK-ACK PDU is related to an NS-VC that is not locally blocked, then an NS-VC unblocking procedure is initiated. + +If an unexpected NS-UNBLOCK-ACK PDU is received by a BSS or an SGSN and it is related to an NS-VC that is not locally blocked, the received NS-UNBLOCK-ACK PDU is discarded. If the NS-UNBLOCK-ACK PDU is related to an NS-VC that is locally blocked, then an NS-VC blocking procedure is initiated. + +If the NS-VCI received in an NS-BLOCK or NS-BLOCK-ACK PDU is unknown, then the error shall be reported to the originator of the PDU by means of an NS-STATUS PDU including the unknown NS-VCI, with the Cause value set to "NS-VC unknown", the O&M system shall be informed, then the NS-BLOCK or NS-BLOCK-ACK PDU shall be ignored. Further actions of the O&M system are out of the scope of the present document. + +## 7.3 Reset procedure + +The reset procedure shall not be used for an IP Sub-network. + +The reset procedure shall be used when a new NS-VC is set-up between a BSS and an SGSN, after processor re-start, after failure recovery or any local event restoring an existing NS-VC in the dead state or when its state is undetermined between remote NS entities. Upon completion of the reset procedure, the successfully reset NS-VC is marked as blocked and alive at both sides of the Gb interface. + +When a BSS (or SGSN) wishes to reset an NS-VC, the following shall be performed: + +- The NS entity at the BSS (or SGSN) informs the NS user entity of the new transfer capability by means of an NS-STATUS-Indication primitive for each affected BVC. The BSS (or SGSN) then sends an NS-RESET PDU to its peer entity indicating the NS-VCI and the NSEI. The NS-RESET PDU is sent on the NS-VC being reset. The NS-RESET PDU includes a Cause information element. +- The sending entity of the NS-RESET PDU then marks the NS-VC as blocked and dead and starts timer Tns-reset. +- Receipt of an NS-RESET PDU at an SGSN (or BSS) shall be acknowledged with an NS-RESET-ACK PDU including the NS-VCI and the NSEI, provided that the receiving side is able to reset the NS-VC (i.e. no local condition prevents the receiving side from resetting the NS-VC). The NS-RESET-ACK PDU shall be sent on the NS-VC being reset. +- The entity receiving the NS-RESET PDU then marks the acknowledged NS-VC as blocked and alive and informs the NS user entity of the new transfer capability by means of an NS-STATUS-Indication primitive for each affected BVC. The test procedure is then initiated on this NS-VC. +- When the sending entity of an NS-RESET PDU receives the NS-RESET-ACK PDU, it stops timer Tns-reset, marks the NS-VC as blocked and alive and initiates the test procedure on this NS-VC. The originator of the NS-RESET PDU is then responsible for unblocking this NS-VC. + +In case of collision between reset procedures initiated at both sides of the Gb interface, the following shall apply: + +- When an NS entity awaiting an NS-RESET-ACK PDU in response to an NS-RESET PDU receives an NS-RESET PDU, it shall acknowledge it as described above, and in addition, it shall treat it as an NS-RESET-ACK PDU. + +When an NS entity is awaiting an NS-RESET-ACK PDU, any PDU other than NS-RESET or NS-RESET-ACK received on one of the NS-VCs being reset shall be ignored. + +The reset procedure overrides any other pending procedure on the affected NS-VC i.e. other pending procedures are stopped, other running timers are stopped. + +### 7.3.1 Abnormal conditions + +If the sending entity of an NS-RESET PDU receives no NS-RESET-ACK PDU before timer Tns-reset expires the corresponding NS-VCs shall remain blocked and dead and the entire reset procedure shall be repeated. If the reset procedure remains unsuccessful for a period of time established by the operator, the O&M system shall be informed, and the reset procedure shall be stopped. Further actions of the O&M system are out of the scope of the present document. + +If the NS-VCI received in an NS-RESET PDU is different from the NS-VCI locally associated to this NS-VC, the O&M system shall be informed, an NS-RESET-ACK PDU shall be returned including the NS-VCI locally associated to this NS-VC, then the NS-RESET PDU shall be ignored as if not received. + +If the NSEI received in an NS-RESET PDU is different from the NSEI locally associated to this NS-VC, the O&M system shall be informed, an NS-RESET-ACK PDU shall be returned including the NSEI locally associated to this NS-VC, then the NS-RESET PDU shall be ignored as if not received. + +If the NS-VCI received in an NS-RESET-ACK PDU is different from the NS-VCI locally associated to this NS-VC or if the NSEI received in an NS-RESET-ACK PDU is different from the NSEI locally associated to this NS-VC, the O&M system shall be informed, then the reset procedure shall be stopped. Further actions of the O&M system are out of the scope of the present document. + +If an NS-RESET-ACK PDU is received when not expected, it shall be ignored. + +## 7.4 Test procedure for a Frame Relay Sub-network + +The test procedure shall be used when a BSS (or SGSN) wishes to check that end-to-end communication with its peer entity exists on an NS-VC. + +Both sides of the Gb interface may initiate this procedure independently from each other. This procedure shall be initiated upon successful completion of the reset procedure (as specified in sub-clause "Reset procedure") and shall then be periodically repeated. + +Upon successful completion of an NS-VC reset procedure, a BSS (or SGSN) shall start timer Tns-test, then: + +- Upon Tns-test expiry, a BSS (or SGSN) sends an NS-ALIVE PDU on the NS-VC to be checked, starts timer Tns-alive and waits for an NS-ALIVE-ACK PDU on this NS-VC. +- Upon receipt of an NS-ALIVE PDU on an alive NS-VC, an SGSN (or BSS) shall return an NS-ALIVE-ACK PDU on the NS-VC where the NS-ALIVE PDU was received. +- Upon receipt of the NS-ALIVE-ACK PDU in response to an NS-ALIVE PDU, the originator of the NS-ALIVE PDU, shall stop timer Tns-alive and shall start again timer Tns-test. + +The procedure is repeated each time Tns-test expires. + +### 7.4.1 Abnormal conditions + +If an NS-ALIVE-ACK PDU is received when not expected, it shall be ignored. + +If no NS-ALIVE-ACK PDU is received before Tns-alive expires, the test procedure shall be repeated a maximum of NS-ALIVE-RETRIES attempts. After NS-ALIVE-RETRIES unsuccessful retry attempts, the procedure is stopped, the NS-VC is marked as dead and blocked, the O&M system and the load sharing function are informed, and an NS-STATUS-Indication is sent to the NS user entity. If the NS-VC is not already blocked, a blocking procedure is initiated using an alive NS-VC, if any. Further actions of the O&M system are out of the scope of the present document. + +## 7.4b Test Procedure for an IP Sub-network + +The test procedure is used on the Gb interface to verify the communications paths between the SGSN and the BSS. At least one of the signalling endpoints of the SGSN shall be tested by the BSS, by sending the NS-ALIVE PDU on any NS-VC terminating at any of the SGSN signalling endpoints. An NSE may test any peer NSE IP endpoint at any time. + +It is recommended that all remote IP endpoints of an NSE (signalling and data endpoints) are tested periodically, regardless of their operational status (operational or non-operational). + +Upon successful completion of the Size and configuration procedures when configured by auto-configuration procedures, or upon completion of administrative configuration, the NSE shall start timer Tns-test. Upon expiry of the timer Tns-test the NSE shall: + +- send an NS-ALIVE PDU to a peer IP endpoint. +- start timer Tns-alive. +- upon receiving an NS-ALIVE-ACK PDU from the peer NSE IP endpoint, the NSE shall stop timer Tns-alive and shall start again timer Tns-test. + +The procedure is repeated each time that the Tns-test expires. + +Upon receipt of an NS-ALIVE PDU, on any configured IP endpoint, the NSE shall send an NS-ALIVE-ACK PDU to the source UDP/IP endpoint of the NS-ALIVE PDU. + +Upon receipt of an NS-ALIVE-ACK PDU, on an IP endpoint marked as non-operational, the NSE communication path is marked as operational. + +### 7.4b.1 Abnormal Conditions + +If an NS-ALIVE-ACK PDU is received when not expected, it shall be discarded. + +#### 7.4b.1.1 Abnormal Conditions for signalling endpoints + +If the NSE timer Tns-alive expires, the test procedure shall be repeated a maximum of NS-ALIVE-RETRIES times. After NS-ALIVE-RETRIES unsuccessful attempts the NSE communication path is marked as non-operational. + +The O&M system and the load sharing function are informed, and an NS-STATUS-Indication is sent to the NS user entity. If more than one signalling endpoint is available at the SGSN, an NS-STATUS PDU may be sent to the SGSN using one of the available signalling endpoints of the peer NSE. The NS-STATUS includes the two IP endpoints that comprise the NS-VC and a cause code "IP test failed". Further actions of the O&M system is out of the scope of the present document. + +If more than one signalling endpoints are available at the SGSN the test procedure shall continue on one or more of these endpoints. + +If all signalling UDP/IP endpoints of a peer SGSN NSE are marked non-operational and if the NSE is configured by auto-configuration procedures, then the BSS NSE shall start the Size procedure with the Reset-bit field of the *Reset Flag* IE set to "1" followed by the configuration procedure. + +If an SGSN tests IP endpoints of a peer BSS NSE and all signalling IP endpoints of a peer BSS NSE are marked non-operational and if the NSE is configured by auto-configuration procedures, then the SGSN NSE shall not respond to NS-ALIVE messages from that BSS NSE. If the NSE is configured by administrative means, then the SGSN NSE shall respond to NS-ALIVE messages from that BSS NSE. + +When the SGSN recovers after a restart or a network failure and if the NSE is configured by auto-configuration procedures, it shall not respond on any NS-PDUs until the Size and configuration procedures have been completed successfully. + +#### 7.4b.1.2 Abnormal Conditions for data endpoints + +If the test procedure is being performed on a data IP endpoint and timer Tns-alive expires, depending on the implementation, the test procedure may be repeated. After NS-ALIVE-RETRIES unsuccessful retry attempts, the O&M system and the load sharing function are informed, and an NS-STATUS-Indication is sent to the NS user entity. An NS-STATUS procedure may be initiated towards a signalling IP endpoint. The NS-STATUS includes the two IP endpoints + +that comprise the NS-VC and a cause code "IP test failed". Further actions of the O&M system is out of the scope of the present document. + +When an NS-ALIVE fails for a path, the sending side is allowed to change both the local IP endpoint and the remote IP endpoint. + +Traffic may be processed if received on an IP endpoint after an unsuccessful test procedure. + +## 7.5 Procedure for error reporting + +The reporting of protocol errors to the remote entity is done by means of the NS-STATUS PDU, as further described in the rest of the present document. + +Upon receipt of an NS-STATUS PDU, the O&M system is informed. Further actions of the O&M system are out of the scope of the present document. + +### 7.5.1 Abnormal conditions + +If an error is detected in a received NS-STATUS PDU, then the error shall not be reported to the remote NS entity. + +## 7.6 Resource Distribution Procedure + +Each NS entity is responsible for determining when to trigger the Resource Distribution Function and to which IP endpoint resource distribution can occur. This sub-clause only describes the mechanism for informing the peer NS entity the IP endpoint at which NS user data for an MS or for an MBMS session is to be received. Recommended usage of the Resource Distribution Function for an IP sub-network when Resource Distribution is to be performed on a data flow concerning an MS can be found in annex B. + +The resource distribution function at an NSE may choose to change the IP endpoint at which it receives NS user data for an MS or MBMS session. To achieve this, the NS user entity shall notify the load sharing function and subsequently the NS entity to send an NS-UNITDATA with the R-bit field set to "1" in the *NS SDU Control Bits* IE from the new IP endpoint. Note: the BSS may set the R-bit field to "1" in the initial PDU for NS user data for an MS. If an NSE has no NS SDU to send for some period of time, or if Resource Distribution is to be performed on a data flow concerning an MBMS session, then the NSE shall send an NS-UNITDATA PDU containing a BSSGP DL-UNITDATA (BSSGP UL-UNITDATA) or, in case of an MBMS session, a BSSGP UL-MBMS-UNITDATA with an LLC-PDU Length Indicator set to 0 (see 3GPP TS 48.018). + +When the NSE receives an NS-UNITDATA PDU with R-bit field set to "1" in the *NS SDU Control Bits* IE, it shall inform the higher layers to change the destination IP endpoint for that MS or MBMS session. All subsequent NS SDUs for the same MS or MBMS session shall be sent to this destination. The receiving NSE may optionally send an NS-UNITDATA PDU with the C-bit field set to "1" in the *NS SDU Control Bits* IE to confirm acknowledgement of the request to change the IP endpoint. + +The NSE initiating the Resource Distribution Function for an MS shall not set the R-bit field to "1" in an NS-UNITDATA PDU for this MS once it has received an NS-UNITDATA PDU for the same MS, irrespective of the C-bit field value, at the requested IP endpoint. + +### 7.6.1 Abnormal Conditions + +If a peer NSE continues to send NS-UNITDATA for a given MS or MBMS session to an IP endpoint after receipt of a NS-UNITDATA with R-bit that directs traffic to a different IP endpoint, then the action taken by the NSE is implementation dependent.. The BSS maintains the MS context for a subscriber for a finite period of time. When uplink data is received for a mobile and the BSS has no MS context with the SGSN preferred IP endpoint then the BSS may choose to send the NS user data on one of the IP endpoints determined by the load sharing function. However, the SGSN maintains the MS context for as long as it has location information for the MS on cell level. + +# --- 8 General protocol error handling + +This sub-clause is not applicable to the Sub-Network Service protocol. + +The following "General case" sub-clause applies unless otherwise stated in the "Special cases" sub-clause. + +## 8.1 General case + +This sub-clause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocol. + +Most error handling procedures are mandatory for a BSS and SGSN. + +Detailed error handling procedures are implementation dependent and may vary from PLMN to PLMN. However, when extensions of this protocol are developed, networks shall be assumed to have the error handling that is indicated in this sub-clause as mandatory ("shall") and that is indicated as strongly recommended ("should"). + +In this sub-clause the following terminology is used: + +- **Syntactical error:** an IE is defined to be syntactically incorrect in a PDU if it contains at least one value defined as "reserved" or "reserved for future use", or if its value part violates coding rules specified in the relevant protocol specification, e.g. a too short IE (the length indicator shall be used to determine the boundary of the IE). However, it is not a syntactical error that an IE specifies in its length indicator a greater length than defined in the relevant protocol specification; and +- **Semantic error:** a PDU is defined to have semantically incorrect contents if it contains information which, possibly dependent on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part of the relevant protocol specification. + +To allow for the introduction of new functions the following rules shall be used to determine the actions of a receiving entity when it receives a PDU, part or all of which it is unable to understand. As the recipient is unable to tell the difference between a new, previously unspecified coding and an erroneous coding, the recipient also uses the same rules for error handling. + +The robustness of a recipient in handling erroneous PDUs does not relax the requirement that the transmitter shall obey the present document. However, it is intended that functionality can be gradually added to an entity, and no obstacle to intermediate phase equipment is intended. + +### 8.1.1 Presence requirements of Information Elements + +There are three different presence requirements (M, C, or O) for an IE within a given PDU: + +- **M ("Mandatory")** means that the IE shall be included by the sending side, and that the receiver diagnoses a "missing essential IE" error when detecting that the IE is not present. +- **C ("Conditional")** means: + - that inclusion of the IE by the sender depends on conditions specified in the relevant protocol specification; + - that there are conditions for the receiver to expect that the IE is present and/or conditions for the receiver to expect that the IE is not present; these conditions depend only on the PDU itself, and not on the state in which the PDU was received; they are known as static conditions; + - that the receiver detecting that the IE is not present when sufficient static conditions are fulfilled for its presence, shall diagnose a "missing essential IE" error; + - that the receiver detecting that the IE is present when sufficient static conditions are fulfilled for its non-presence, shall treat the IE as an optional one, see below. +- **O ("Optional")** means that the receiver shall never diagnose a "missing essential IE" error or shall never diagnose an error because it detects that the IE is present or that the IE is not present. There may however be conditions depending on the states, resources, etc. of the receiver to diagnose other errors. + +In addition, the following definitions apply: + +- **Essential Elements:** These are the conditional (C) elements when the condition for their reception is fulfilled, plus the mandatory (M) elements. Any exception to this rule is explicitly stated in the relevant protocol specification. + +- **Non-Essential Elements:** Non-essential elements are all the information elements that are not defined as essential. + +### 8.1.2 Erroneous events + +The following events shall be regarded as errors by the recipient and shall be treated as specified below. Certain types of error shall be reported to the sending side, in that case the erroneous PDU and the error cause shall be returned to the sending side by means of the appropriate error reporting PDU. The following rules shall be applied in order of precedence: + +- 1) a PDU whose type is non-existent or unrecognisable: the error shall not be reported, the PDU shall be ignored; +- 2) a PDU not consistent with the recipient's state: the error shall be reported with cause "PDU not compatible with the protocol state", the PDU shall be ignored; +- 3) a PDU sent in the wrong direction: the error shall be reported with cause "Protocol error - unspecified", the PDU shall be ignored; +- 4) a missing essential information element: the error shall be reported with cause "Missing essential IE", the PDU shall be ignored; +- 5) syntactical error in an essential IE: the error shall be reported with cause "Invalid essential IE", the PDU shall be ignored. + +### 8.1.3 Non-erroneous events + +The following events shall not be regarded as errors by the recipient: + +- 1) spare bits with an unexpected value in any information element; +- 2) the use of additional octets in any information element with a length indicator, that is: when the indicated length is greater than defined in the relevant protocol specification (the length indicator shall be used to determine the boundary of the IE); +- 3) a missing non-essential information element; +- 4) an unknown information element identifier; +- 5) any unexpected information element; and +- 6) a syntactical error in any non-essential information element. + +When the recipient detects one or more of these events the receiving entity shall ignore the information that it is unable to understand and treat the PDU on the basis of the information that remains. + +Additionally, when more information elements of a particular type are received than are expected, the last one(s) shall be ignored. + +If, because information was ignored, the rest of the PDU can no longer be handled then the receiving entity shall report the error to the sending side by means of the appropriate error reporting PDU including the incorrect PDU received and the cause "semantically incorrect PDU". + +### 8.1.4 Other events + +The following events should be treated on a case by case basis and the outcome may depend upon the capabilities of the recipient. + +- 1) The recipient may accept PDUs that contain information elements that do not appear to be in the correct sequence. Elements that occur more than once in a PDU shall be assumed to have been transmitted in the correct order. Recipients that do not accept out of sequence information elements shall regard the PDU as containing unexpected and/or missing information elements and follow the procedures defined in the rest of this "General case" sub-clause. +- 2) When any IE with semantically incorrect contents is received, the receiving entity shall react according to the relevant protocol specification. If however no such reactions are specified, the receiving entity shall ignore that + +IE and treat the rest of the PDU. If, because this IE was ignored, the rest of the PDU can no longer be handled then the receiving entity shall report the error to the sending side by means of the appropriate error reporting PDU including the incorrect PDU received and the cause "semantically incorrect PDU". + +## 8.2 Special cases + +In case of conflict between this sub-clause and the above "General case" sub-clause, this sub-clause takes precedence. + +In case of conflict between this sub-clause and the specific "Abnormal conditions" sub-clauses in sub-clause "Network Service Control protocol", the "Abnormal conditions" sub-clauses take precedence over this "Special cases" sub-clause. + +### 8.2.1 Deviations from the "General case" sub-clause + +The Cause information element (see sub-clauses "General PDU definitions and contents" and "General information elements coding") shall be considered as a non-essential information element even when mandatory in a PDU. + +### 8.2.2 Error reporting + +The NS-STATUS PDU shall be used to report error to the remote NS entity, see sub-clause "Procedure for error reporting". The NS-STATUS PDU shall never be used to report an error detected in a received NS-STATUS PDU. + +# 9 General PDU definitions and contents + +This sub-clause is not applicable to the Sub-Network Service protocol. + +## 9.1 General structure of a PDU + +This sub-clause defines the general structure of the PDUs on the Gb interface. + +The general PDU structure is composed of: + +- a PDU type information element; and +- other information elements, as required. + +The PDU type IE occupies the first octet position in the PDU. + +This general structure and the numbering convention used on the Gb interface are illustrated in figure 9.1.1. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to n. + +The octets shall be transmitted by increasing order of octet number. Within each octet, the bits shall be transmitted by increasing order of bit number i.e. bit 1 of octet 1 shall be transmitted first, bit 8 of octet n shall be transmitted last. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------------|----------------------------|---|---|---|---|---|---|---| +| octet 1 | PDU type | | | | | | | | +| octets 2, 3, ...n | other information elements | | | | | | | | + +**Figure 9.1.1: General PDU structure and numbering convention** + +Each PDU definition includes a table listing the information elements (IEs) known in the PDU and the order of their appearance in the PDU. Unless specified otherwise in the PDU descriptions, a particular information element shall not be present more than once in a given PDU. All information elements that may be repeated are explicitly indicated. + +For each information element the table indicates: + +- The name of the information element (which may give an idea of the semantics of the element). +- Possibly a reference to another GSM Technical Specification where the information element is described. +- The presence requirement indication (M, C, or O) for the IE as defined in sub-clause "General protocol error handling". + +- d) The format (T, L, V) of the information element. See further description of the type (T), length (L) and V (value) fields in sub-clause "General structure of the information elements". +- e) The length of the information element (or permissible range of lengths), in octets, in the PDU, where "?" means that the maximum length of the IE is only constrained by the lower layer protocol. This indication is non-normative. The indicated length includes all the T, L, V fields present in the IE. +- f) Sub-clauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant PDU which together with other conditions specified in 3GPP TS 48.016 define when the information elements shall be included or not, what non-presence of such IEs means, and - for IEs with presence requirement C - the static conditions for presence and/or non-presence of the IEs, see sub-clause "General protocol error handling". + +## 9.2 Network Service Control PDUs + +The Network Service Control PDUs are also referred to as NS PDUs in the rest of the present document. + +### 9.2.1 NS-ALIVE + +This PDU is used to test an NS-VC. + +PDU type: NS-ALIVE + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.2.1.1: NS-ALIVE PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | + +### 9.2.2 NS-ALIVE-ACK + +This PDU acknowledges a received NS-ALIVE PDU and is sent on the NS-VC where the NS-ALIVE PDU was received. + +PDU type: NS-ALIVE-ACK + +Direction: SGSN to BSS, BSS to SGSN + +**Table 9.2.2.1: NS-ALIVE-ACK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | + +### 9.2.3 NS-BLOCK + +This PDU indicates that an NS-VC shall be blocked at the recipient entity. + +PDU type: NS-BLOCK + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.2.3.1: NS-BLOCK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| Cause | 10.3.2 | M | TLV | 3 | +| NS-VCI | 10.3.5 | M | TLV | 4 | + +### 9.2.4 NS-BLOCK-ACK + +This PDU acknowledges that an NS-VC has been blocked for use. + +PDU type: NS-BLOCK-ACK + +Direction: SGSN to BSS, BSS to SGSN + +**Table 9.2.4.1: NS-BLOCK-ACK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NS-VCI | 10.3.5 | M | TLV | 4 | + +### 9.2.5 NS-RESET + +This PDU indicates that the NS peer entity is trying to reset one NS-VC. + +PDU type: NS-RESET + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.2.5.1: NS-RESET PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| Cause | 10.3.2 | M | TLV | 3 | +| NS-VCI | 10.3.5 | M | TLV | 4 | +| NSEI | 10.3.6 | M | TLV | 4 | + +Typical cause values are: O&M intervention, Equipment failure. + +### 9.2.6 NS-RESET-ACK + +This PDU acknowledges the reset of the indicated NS-VC. + +PDU type: NS-RESET-ACK + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.2.6.1: NS-RESET-ACK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NS-VCI | 10.3.5 | M | TLV | 4 | +| NSEI | 10.3.6 | M | TLV | 4 | + +### 9.2.7 NS-STATUS + +This PDU is used to report error conditions. + +PDU type: NS-STATUS + +Direction: SGSN to BSS, BSS to SGSN + +**Table 9.2.7.1: NS-STATUS PDU contents** + +| Information element | Reference | Presence | Format | Length | +|----------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| Cause | 10.3.2 | M | TLV | 3 | +| NS-VCI | 10.3.5 | C | TLV | 4 | +| NS PDU | 10.3.3 | C | TLV | 3-? | +| BVCI | 10.3.1 | C | TLV | 4 | +| List of IP4 Elements | 10.3.2c | C | TLV | 10-? | +| List of IP6 Elements | 10.3.2d | C | TLV | 22-? | + +#### 9.2.7.1 Static conditions for NS-VCI + +The *NS-VCI* IE shall be included when the *Cause* IE is set to one of the following values: + +- a) "NS-VC blocked"; +- b) "NS-VC unknown"; + +and shall not be included otherwise. + +#### 9.2.7.2 Static conditions for NS PDU + +The *NS PDU* IE shall be included if the NS-STATUS message is sent in response to a received NS PDU within which an error was detected i.e. when the *Cause* IE is set to one of the following values: + +- a) "Semantically incorrect PDU"; +- b) "PDU not compatible with the protocol state"; +- c) "Protocol error - unspecified"; +- d) "Invalid essential IE"; +- e) "Missing essential IE"; + +and shall not be included otherwise. + +This is the whole PDU received with error. This PDU may be truncated if it exceeds the information carrying capacity of the NS. + +#### 9.2.7.3 Static conditions for BVCI + +The *BVCI* IE shall be included when the *Cause* IE is set to one of the following values: + +- a) "BVCI unknown on that NSE"; + +and shall not be included otherwise. + +#### 9.2.7.4 Static conditions for List of IP4 Elements + +The *List of IP4 Elements* IE shall be included when the *Cause* IE is set to one of the following values: + +- a) " IP test failed"; + +and the IP endpoints of the NS-VC that failed are IPv4 endpoints. The *List of IP4 Elements* IE shall be the only conditional IE sent in a NS-STATUS PDU. + +The *List of IP4 Elements* IE shall not be included otherwise. + +#### 9.2.7.5 Static conditions for List of IP6 Elements + +The *List of IP6 Elements* IE shall be included when the *Cause* IE is set to one of the following values: + +- a) " IP test failed"; + +and the IP endpoints of the NS-VC that failed are IPv6 endpoints. The *List of IP6 Elements* IE shall be the only conditional IE sent in a NS-STATUS PDU. + +The *List of IP6 Elements* IE shall not be included otherwise. + +### 9.2.8 NS-UNBLOCK + +This PDU indicates that an NS-VC shall be unblocked at the recipient entity. + +PDU type: NS-UNBLOCK + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.2.8.1: NS-UNBLOCK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | + +### 9.2.9 NS-UNBLOCK-ACK + +This PDU acknowledges that an NS-VC has been unblocked. + +PDU type: NS-UNBLOCK-ACK + +Direction: SGSN to BSS, BSS to SGSN + +**Table 9.2.9.1: NS-UNBLOCK-ACK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | + +### 9.2.10 NS-UNITDATA + +This PDU transfers one NS SDU between the BSS and SGSN. + +PDU type: NS-UNITDATA + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.2.10.1: NS-UNITDATA PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NS SDU Control Bits | 10.3.9 | M | V | 1 | +| BVCI | 10.3.1 | M | V | 2 | +| NS SDU | 10.3.4 | M | V | 1-? | + +The length of the *NS SDU* information element shall be derived by the Network Service Control entity from the length of the complete NS-UNITDATA PDU provided by the Sub-Network Service entity to the Network Service Control entity. + +## 9.3 Sub-Network Service Control PDUs + +The Sub-Network Service Control PDUs are also referred to as SNS PDUs in the rest of the present document. The Sub-Network Service Control PDUs are only used in an IP sub-network. + +### 9.3.1 SNS-ACK + +The SNS-ACK PDU is used to acknowledge the SNS-ADD PDU, the SNS-DELETE PDU, or the SNS-CHANGEWEIGHT PDU. + +PDU type: SNS-ACK + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.3.1.1: SNS-ACK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-------------------------------------------------------------------------------------------------------------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| Transaction ID | 10.3.10 | M | V | 1 | +| Cause | 10.3.2 | O | TLV | 3 | +| IP Address a) | 10.3.2b | C | TV | 6-18 | +| List of IP4 Elements b) | 10.3.2c | C | TLV | 10-? | +| List of IP6 Elements b) | 10.3.2d | C | TLV | 22-? | +| a) | the IP Address IE shall only be present if the "Cause" value is set to "Unknown IP address". | | | | +| b) | one or more of these conditional IEs shall be present if the "Cause" value is set to "Unknown IP endpoint". | | | | + +### 9.3.2 SNS-ADD + +The SNS-ADD PDU is used to add additional IP Endpoints. + +PDU type: SNS-ADD + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.3.2.1: SNS-ADD PDU contents** + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------------------------------------------------------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| Transaction ID | 10.3.10 | M | V | 1 | +| List of IP4 Elements a) | 10.3.2c | C | TLV | 10-? | +| List of IP6 Elements a) | 10.3.2d | C | TLV | 22-? | +| a) | one and only one of the conditional IEs shall be present. | | | | + +### 9.3.3 SNS-CHANGEWEIGHT + +The SNS-CHANGEWEIGHT PDU is used to change the signalling weight and/or data weight of an IP endpoint. + +PDU type: SNS-CHANGEWEIGHT + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.3.3.1: SNS-CHANGEWEIGHT PDU contents** + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------------------------------------------------------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| Transaction ID | 10.3.10 | M | V | 1 | +| List of IP4 Elements a) | 10.3.2c | C | TLV | 10-? | +| List of IP6 Elements a) | 10.3.2d | C | TLV | 22-? | +| a) | one and only one of the conditional IEs shall be present. | | | | + +### 9.3.4 SNS-CONFIG + +The SNS-CONFIG PDU is used to configure a NSE to a peer NSE. + +PDU type: SNS-CONFIG + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.3.4.1: SNS-CONFIG PDU contents** + +| Information element | Reference | Presence | Format | Length | +|--------------------------------------------------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| End Flag | 10.3.2a | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| List of IP4 Elements a) | 10.3.2c | C | TLV | 10-? | +| List of IP6 Elements a) | 10.3.2d | C | TLV | 22-? | +| a) one and only one of the conditional IEs shall be present. | | | | | + +### 9.3.5 SNS-CONFIG-ACK + +The SNS-CONFIG-ACK PDU is used to acknowledge an SNS-CONFIG PDU. The SNS-CONFIG-ACK PDU shall be sent to the source IP Endpoint of the corresponding SNS-CONFIG PDU. + +PDU type: SNS-CONFIG-ACK + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.3.5.1: SNS-CONFIG-ACK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| Cause | 10.3.2 | O | TLV | 3 | + +### 9.3.6 SNS-DELETE + +The SNS-DELETE PDU is used to delete previously configured IP Endpoints. + +PDU type: SNS-DELETE + +Direction: BSS to SGSN, SGSN to BSS + +**Table 9.3.6.1: SNS-DELETE PDU contents** + +| Information element | Reference | Presence | Format | Length | +|--------------------------------------------------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| Transaction ID | 10.3.10 | M | V | 1 | +| IP Address a) | 10.3.2b | C | TV | 6-18 | +| List of IP4 Elements a) | 10.3.2c | C | TLV | 10-? | +| List of IP6 Elements a) | 10.3.2d | C | TLV | 22-? | +| a) one and only one of the conditional IEs shall be present. | | | | | + +### 9.3.7 SNS-SIZE + +The SNS-SIZE PDU is used to indicate to the peer NSE the maximum number of NS-VCs or a change in the NS-VC capacity. The SNS-SIZE PDU is used to signal the restart of a NSE to a peer NSE. + +PDU type: SNS-SIZE + +Direction: BSS to SGSN + +**Table 9.3.7.1: SNS-SIZE PDU contents** + +| Information element | Reference | Presence | Format | Length | +|------------------------------------------------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| Reset Flag | | M | TV | 2 | +| Maximum Number of NS-VCs | 10.3.2e | M | TV | 3 | +| Number of IP4 Endpoints a) | 10.3.2f | C | TV | 3 | +| Number of IP6 Endpoints a) | 10.3.2g | C | TV | 3 | +| a) At least one of these conditional IEs shall be present. | | | | | + +### 9.3.8 SNS-SIZE-ACK + +The SNS-SIZE-ACK PDU is used to acknowledge an SNS-SIZE PDU. The SNS-SIZE-ACK PDU shall be sent to the source IP Endpoint of the corresponding SNS-SIZE PDU. + +PDU type: SNS-SIZE-ACK + +Direction: SGSN to BSS + +**Table 9.3.8.1: SNS-SIZE-ACK PDU contents** + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| PDU type | 10.3.7 | M | V | 1 | +| NSEI | 10.3.6 | M | TLV | 4 | +| Cause | 10.3.2 | O | TLV | 3 | + +# 10 General information elements coding + +This sub-clause is not applicable to the Sub-Network Service protocol. + +## 10.1 General structure of the information elements + +The general information element structure is composed of (see figure 10.1.1): + +- an Information Element Identifier (also referred to as the T field); +- a length indicator (also referred to as the L field); +- the information element value (also referred to as the V field). + +Information elements have the TLV, the TV or the V format, as specified in the relevant protocol specification. The format of any given information element may depend on the context e.g. on the message type. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------|--------------------------------------|---|---|---|---|---|---|---| +| octet 1 | Information Element Identifier (IEI) | | | | | | | | +| octets 2, 2a | length indicator | | | | | | | | +| octet 3 | information element value | | | | | | | | +| ... | | | | | | | | | +| octet ... n | | | | | | | | | + +**Figure 10.1.1: Information element structure, TLV format** + +![](8e80de0cac529b2c3775d677c5203133_img.jpg) + +| | | | | | | | | | +|-------------|---------------------------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 1 | information element value | | | | | | | | +| ... | | | | | | | | | +| octet ... n | | | | | | | | | + +**Figure 10.1.2: Information element structure, V format** + +When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. + +### 10.1.1 Information Element Identifier + +The first octet of an information element having the TLV format contains the IEI of the information element. If this octet does not correspond to an IEI known in the PDU, the receiver shall assume that the next octet is the first octet of the length indicator field and shall interpret it as described in the "Length indicator" sub-clause. + +This rule allows the receiver to skip unknown information elements and to analyse any following information elements. + +### 10.1.2 Length indicator + +The length indicator shall be included in all information elements having the TLV format. + +Information elements may be variable in length. The length indicator is one or two octet long, the second octet may be absent. This field consists of the field extension bit, 0/1 ext, and the length of the value field which follows, expressed in octets. The field extension bit enables extension of the length indicator to two octets. + +Bit 8 of the first octet is reserved for the field extension bit. If the field extension bit is set to 0 (zero), then the second octet of the length indicator is present. If the field extension bit is set to 1 (one), then the first octet is the final octet of the length indicator. + +The length of the value field of the IE occupies the rest of the bits in the length indicator. + +![](08e8bbb2a063a3935a0c649b39ade125_img.jpg) + +| | | | | | | | | | +|----------|---------|--------|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 2 | 0/1 ext | length | | | | | | | +| octet 2a | length | | | | | | | | + +**Figure 10.1.2.1: Length indicator structure** + +The BSS or SGSN shall not consider the presence of octet 2a in a received IE as an error when the IE is short enough for the length to be coded in octet 2 only. + +## 10.2 Information element description + +The descriptions of the information elements are organized in alphabetical order of the IE name. Each IE is described in one sub-clause. + +A figure of the sub-clause defines the structure of the IE indicating: + +- the position of the IEI, when present; +- the fields the IE value part is composed of; +- the position of the length indicator, when present; +- possibly octet numbers of the octets that compose the IE. + +Finally, the sub-clause may contain figures defining the structure and value range of the fields that compose the IE value part. + +Where the description of information elements in the present document contains bits defined to be "spare bits", these bits shall set to zero by the sending side, and their value shall be ignored by the receiving side. + +The term "default" may be used, implying that the value defined shall be used in the absence of any assignment, or that this value allows negotiation of alternative values in between the two peer entities. + +## 10.3 Information elements + +The IEI values are indicated in table 10.3.1: + +**Table 10.3.1: IEI coding** + +| IEI coding | | | | | | | | Information element name | +|--------------|---|---|---|---|---|---|---|--------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Cause | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | NS-VCI | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | NS PDU | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | BVCI | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | NSEI | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | List of IP4 Elements | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | List of IP6 Elements | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Maximum Number of NS-VCs | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | Number of IP4 Endpoints | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | Number of IP6 Endpoints | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | Reset Flag | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | IP Address | +| other values | | | | | | | | reserved for future use | + +### 10.3.1 BVCI + +This IE is used for multiplexing BVCs on NS-VCs. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------|---------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octets 2, 2a | length indicator | | | | | | | | +| octet 3 | most significant octet of BVCI | | | | | | | | +| octet 4 | least significant octet of BVCI | | | | | | | | + +**Figure 10.3.1.1: BVCI information element** + +### 10.3.2 Cause + +This IE may be used to indicate to the peer NS entity the reason which triggered a procedure, or the reason of an abnormal condition. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octets 2, 2a | length indicator | | | | | | | | +| octet 3 | cause value | | | | | | | | + +**Figure 10.3.2.1: Cause information element** + +The cause values are indicated in table 10.3.2.1: + +**Table 10.3.2.1: Cause values** + +| Cause value coding | | | | | | | | Cause name | +|--------------------|---|---|---|---|---|---|---|--------------------------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Transit network failure | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | O&M intervention | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | Equipment failure | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | NS-VC blocked | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | NS-VC unknown | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | BVCI unknown on that NSE | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | Semantically incorrect PDU | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | PDU not compatible with the protocol state | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | Protocol error - unspecified | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | Invalid essential IE | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | Missing essential IE | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | Invalid number of IP4 Endpoints | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | Invalid number of IP6 Endpoints | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | Invalid number of NS-VCs | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | Invalid weights | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | Unknown IP endpoint | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | Unknown IP address | +| 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | IP test failed | +| other values | | | | | | | | reserved for future use | + +### 10.3.2a End Flag + +This IE is used to indicate last SNS-CONFIG PDU to be sent to the peer NS entity. All unused bits are spare. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------|---|---|---|---|---|---|-------| +| octet 1 | spare | | | | | | | E-bit | + +**Figure 10.3.2a.1: End Flag information element** + +The "E-bit" is coded as shown below: + +- 0 Additional PDUs will be sent. +- 1 Last PDU sent. + +### 10.3.2b IP Address + +This IE identifies an IP address. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Address Type | | | | | | | | +| Octets 3 -n | Address value | | | | | | | | + +**Figure 10.3.2b.1: IP Address information element** + +Where "n" is 6 if the Address Type is IPv4 and "n" is 18 if the Address Type is IPv6. + +The "Address Type" is coded as shown in table 10.3.2b.1. + +**Table 10.3.2b.1: "Address Type" coding** + +| coding | Address Type | +|---------------|--------------------------------------------------------------| +| 0 | Reserved | +| 1 | IPv4 | +| 2 | IPv6 | +| Reserved | All values not explicitly shown are reserved for future use. | + +### 10.3.2c List of IP4 Elements + +This IE identifies a list of IPv4 elements. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------|------------------|----------|----------|----------|----------|----------|----------|----------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octets 3-10 | IP4 Element 1 | | | | | | | | +| octets ... - (2+8n) | IP4 Element n | | | | | | | | + +**Figure 10.3.2c.1: List of IP4 Elements information element** + +The length depends on the number of IP4 Elements: n. The coding of an IP4 Element is: + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------|-------------------|----------|----------|----------|----------|----------|----------|----------| +| octet (x+1)-(x+4) | IPv4 Address | | | | | | | | +| octet (x+5)-(x+6) | UDP Port Value | | | | | | | | +| octet (x+7) | Signalling Weight | | | | | | | | +| octet (x+8) | Data Weight | | | | | | | | + +where $x = 8i - 6$ ( $1 \leq i \leq n$ ). + +### 10.3.2d List of IP6 Elements + +This IE identifies a list of IPv6 elements. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------------------|------------------|----------|----------|----------|----------|----------|----------|----------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octets 3- 22 | IP6 Element 1 | | | | | | | | +| octets ... - (2+20n) | IP6 Element n | | | | | | | | + +**Figure 10.3.2d.1: List of IP6 Elements information element** + +The length depends on the number of IP6 Elements: n . The coding of an IP6 Element is: + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------|-------------------|----------|----------|----------|----------|----------|----------|----------| +| octet (x+1)-(x+16) | IPv6 Address | | | | | | | | +| octet (x+17)-(x+18) | UDP Port Value | | | | | | | | +| octet (x+19) | Signalling Weight | | | | | | | | +| octet (x+20) | Data Weight | | | | | | | | + +where $x = 20i - 18$ ( $1 \leq i \leq n$ ). + +### 10.3.2e Maximum Number of NS-VCs + +This IE identifies the maximum number of NS-VCs. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------|----------|----------|----------|----------|----------|----------|----------| +|----------|----------|----------|----------|----------|----------|----------|----------| + +| | | +|----------------|-----------------------------------------------------| +| octet 1 | IEI | +| octet 2 | most significant octet of Maximum Number of NS-VCs | +| octet 3 | least significant octet of Maximum Number of NS-VCs | + +**Figure 10.3.2e.1: Maximum Number of NS-VCs information element** + +### 10.3.2f Number of IP4 Endpoints + +This IE identifies the number of IPv4 endpoints. + +| | | | | | | | | | +|----------------|----------------------------------------------------|----------|----------|----------|----------|----------|----------|----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 1 | IEI | | | | | | | | +| octet 2 | most significant octet of Number of IP4 Endpoints | | | | | | | | +| octet 3 | least significant octet of Number of IP4 Endpoints | | | | | | | | + +**Figure 10.3.2f.1: Number of IP4 Endpoints information element** + +### 10.3.2g Number of IP6 Endpoints + +This IE identifies the number of IPv6 endpoints. + +| | | | | | | | | | +|----------------|----------------------------------------------------|----------|----------|----------|----------|----------|----------|----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 1 | IEI | | | | | | | | +| octet 2 | most significant octet of Number of IP6 Endpoints | | | | | | | | +| octet 3 | least significant octet of Number of IP6 Endpoints | | | | | | | | + +**Figure 10.3.2g.1: Number of IP6 Endpoints information element** + +### 10.3.3 NS PDU + +This IE is included in the NS-STATUS PDU sent in answer to an erroneous NS PDU. This IE contains the erroneous PDU received. The erroneous PDU may be truncated in order to fit in the maximum size of the NS-STATUS PDU. + +| | | | | | | | | | +|---------------------|------------------|----------|----------|----------|----------|----------|----------|----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 1 | IEI | | | | | | | | +| octets 2, 2a | length indicator | | | | | | | | +| octet 3 | NS PDU | | | | | | | | +| ... | | | | | | | | | +| octet n | | | | | | | | | + +**Figure 10.3.3.1: NS PDU information element** + +### 10.3.4 NS SDU + +This IE contains one and only one NS SDU transmitted across the Gb interface. + +| | | | | | | | | | +|----------------|----------|----------|----------|----------|----------|----------|----------|----------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 1 | NS SDU | | | | | | | | +| ... | | | | | | | | | +| octet n | | | | | | | | | + +**Figure 10.3.4.1: NS SDU information element** + +In this "NS SDU" information element, bit i of octet j is equal to bit i of octet j of the NS SDU, as defined in the NS user protocol specification. + +### 10.3.5 NS-VCI + +This IE unambiguously identifies one NS-VC amongst all the NS-VCs used between one SGSN and the connected BSSs. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------|-----------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octets 2, 2a | length indicator | | | | | | | | +| octet 3 | most significant octet of NS-VCI | | | | | | | | +| octet 4 | least significant octet of NS-VCI | | | | | | | | + +Figure 10.3.5.1: NS-VCI information element + +### 10.3.6 NSEI + +This IE unambiguously identifies one NSE. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------|---------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octets 2, 2a | length indicator | | | | | | | | +| octet 3 | most significant octet of NSEI | | | | | | | | +| octet 4 | least significant octet of NSEI | | | | | | | | + +Figure 10.3.6.1: NSEI information element + +### 10.3.7 PDU type + +Table 10.3.7.1: PDU type coding + +| PDU type coding | | | | | | | | PDU name | +|-----------------|---|---|---|---|---|---|---|-------------------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | NS-UNITDATA | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | NS-RESET | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | NS-RESET-ACK | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | NS-BLOCK | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | NS-BLOCK-ACK | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | NS-UNBLOCK | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | NS-UNBLOCK-ACK | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | NS-STATUS | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | NS-ALIVE | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | NS-ALIVE-ACK | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | SNS-ACK | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | SNS-ADD | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | SNS-CHANGEWEIGHT | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | SNS-CONFIG | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | SNS-CONFIG-ACK | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | SNS-DELETE | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | SNS-SIZE | +| 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | SNS-SIZE-ACK | +| other values | | | | | | | | reserved for future use | + +### 10.3.7a Reset Flag + +This IE is used to indicate if the peer NS entity shall reset all configuration information. All unused bits are spare. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------|---|---|---|---|---|---|-----------| +| octet 1 | IEI | | | | | | | | +| octet 2 | Spare | | | | | | | Reset-bit | + +**Figure 10.3.7a.1: Reset Flag information element** + +The "Reset-bit" is coded as shown below: + +- 0 Do not reset. +- 1 Reset. + +### 10.3.8 (void) + +### 10.3.9 NS SDU Control Bits + +This IE is used to indicate additional information about the NS-SDU to the user of the NS entity. All unused bits are spare. + +![](2aa94b70ba3fadcba8420d9e3128253a_img.jpg) + +| | | | | | | | | | +|---------|-------|---|---|---|---|---|-------|-------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 1 | spare | | | | | | C-bit | R-bit | + +**Figure 10.3.9.1: NS SDU Control Bits information element** + +The "R-bit" is coded as shown below: + +- 0 No request for change flow; +- 1 Request change flow. + +The "C-bit" is coded as shown below: + +- 0 No confirmation for change flow; +- 1 Confirm change flow. + +### 10.3.10 Transaction ID + +This IE provides an identifier for SNS PDUs. + +![](1a74cf06fd2a1f8dcf7932224b617c57_img.jpg) + +| | | | | | | | | | +|---------|-------|---|---|---|---|---|---|---| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| octet 1 | Value | | | | | | | | + +**Figure 10.3.10.1: Transaction ID information element** + +# 11 List of system variables + +**Table 11.1: System timers** + +| Timer name | Timer value | Notes | Relation to other timers | +|------------|-------------|-----------------------------------------------|--------------------------| +| Tns-block | 1s to 120s | Guards the blocking and unblocking procedures | none | +| Tns-reset | 1s to 120s | Guards the reset procedure | none | +| Tns-test | 1s to 60s | Periodicity of the NS-VC test procedure | none | +| Tns-alive | 3s | Guards the NS-VC test procedure | none | +| Tsns-prov | 1s-10s | Guards the SNS procedures | none | + +**Table 11.2: System counters** + +| Counter name | Value | Notes | +|--------------------------|--------------|-------------------| +| NS-BLOCK-RETRIES | 3 | recommended value | +| NS-UNBLOCK-RETRIES | 3 | recommended value | +| NS-ALIVE-RETRIES | 10 | recommended value | +| SNS-ADD-RETRIES | 3 | recommended value | +| SNS-CONFIG-RETRIES | 3 | recommended value | +| SNS-CHANGEWEIGHT-RETRIES | 3 | recommended value | +| SNS-DELETE-RETRIES | 3 | recommended value | +| SNS-SIZE-RETRIES | 3 | recommended value | + +# --- Annex A (informative): Recommended usage of BVCI and NSEI + +This annex recommends a way to use BVCI and NSEI, avoiding huge and unflexible configuration data at the SGSN. This annex uses concepts defined in 3GPP TS 48.018. + +The key points are: + +- A BVCI needs not to be unique within an SGSN, a BVCI is unique within an NS Entity. BVCI together with NSEI uniquely identify a BVC within an SGSN (the global identifier within an SGSN is BVCI+NSEI). +- BVCI corresponding to PTP functional entities need not to be statically configured at the SGSN side: no fixed, permanent relationship is required in the SGSN between PTP BVCI and NS-VCs. + +With the NSEI, the SGSN needs not to be updated when a new cell (BVCI) is added to a BSS (NSEI). The pre-configuration of a cell in the SGSN and the constraint in the number of BVCs in an SGSN are not needed: + +- The SGSN keeps detailed MM information about an MS while the MS is in the READY state, i.e. the SGSN knows the BVCI and NSEI which can be used to contact the MS for downlink transmission. The BVCI and NSEI are passed from NS to BSSGP and from BSSGP to the upper layers as a primitive parameter in every uplink packet received by the SGSN. Subsequent downlink LLC frames to this MS shall be transmitted by the SGSN over the BVC identified by this BVCI+NSEI. +- An SGSN in STANDBY state will page an MS before sending downlink traffic. The MS will respond with an LLC packet that will put the MM context in READY state and will deliver the BVCI and NSEI to the user of BSSGP. + +For paging purposes, the SGSN only needs to know the correspondence between each Routeing Area and one or more NSEI(s) where to send the corresponding paging messages. Paging messages for a mobile in STANDBY state shall always be sent over BVCI=0 of an NSEI and for a mobile in READY state the circuit page is sent over the PTP BVC identified by the BVCI+NSEI. There may be NSEI(s) where BVCI=0 is not used. + +# Annex B (informative): Recommended usage of Resource Distribution for IP + +This annex recommends a way to support resource distribution over the Gb in an IP sub-network. Resource distribution provides a means to control the IP endpoint at which the NS user traffic for a mobile is received. + +Some examples of resource distribution over the Gb: + +**Example 1:** Both NS entities trigger resource distribution (refer to figure B.1). + +The BSS receives an uplink LLC PDU from the mobile and creates a mobile context. Now the BSS selects the source IP/UDP1 endpoint (internal implementation dependent) and a destination IP/UDP3 endpoint (IP load sharing dependent) on which to send NS SDUs associated with the mobile. + +The BSS sends the uplink NS-UNITDATA (with R-bit set and the LSP corresponding to the IP endpoints selected) to the SGSN from IP/UDP1 to IP/UDP3. On receipt of uplink NS-UNITDATA for the mobile the SGSN may also choose to change the IP endpoint at which it wishes to receive uplink NS-UNITDATA for the mobile to IP/UDP4. The SGSN responds by sending a downlink NS-UNITDATA with R-bit and C-bit set to 1 from the IP/UDP4 at to IP/UDP1. + +Subsequent uplink and downlink NS-UNITDATA for the mobile shall follow the dotted path (IP/UDP1 and IP/UDP4) through the IP sub-network. + +![Diagram illustrating Example 1 of both NS entities requesting change flow. It shows two vertical lines representing the BSS and SGSN. On the BSS side, there are two endpoints: IP/UDP1 (top) and IP/UDP2 (bottom). On the SGSN side, there are two endpoints: IP/UDP3 (top) and IP/UDP4 (bottom). A solid arrow labeled 'NS-UNITDATA(R-bit)' points from IP/UDP1 to IP/UDP3. A solid arrow labeled 'NS-UNITDATA(R-bit, C-bit)' points from IP/UDP4 to IP/UDP1. A dashed arrow points from IP/UDP4 to IP/UDP2.](e3eebf9854831ba50eca8b26c468f65e_img.jpg) + +Diagram illustrating Example 1 of both NS entities requesting change flow. It shows two vertical lines representing the BSS and SGSN. On the BSS side, there are two endpoints: IP/UDP1 (top) and IP/UDP2 (bottom). On the SGSN side, there are two endpoints: IP/UDP3 (top) and IP/UDP4 (bottom). A solid arrow labeled 'NS-UNITDATA(R-bit)' points from IP/UDP1 to IP/UDP3. A solid arrow labeled 'NS-UNITDATA(R-bit, C-bit)' points from IP/UDP4 to IP/UDP1. A dashed arrow points from IP/UDP4 to IP/UDP2. + +**Figure B.1: Example 1 of both NS entities requesting change flow** + +**Example 2:** Only one NS entity triggers resource distribution (refer to figure B.2). + +The BSS sends an uplink NS-UNITDATA with R-bit set from IP/UDP1 to IP/UDP3 at the SGSN. The SGSN may choose not to trigger resource distribution, but the SGSN confirms receipt of the "request change flow" by sending the in the next downlink NS-UNITDATA with C-bit set to IP/UDP1. + +Subsequent uplink data transfer for the mobile will follow the dotted paths from IP/UDP1 to IP/UDP3 and downlink data transfer from IP/UDP4 to IP/UDP1. + +![Figure B.2: Example 2 of only one NS entity requesting change flow. The diagram shows a BSS on the left and an SGSN on the right. The BSS has two IP/UDP endpoints: IP/UDP1 (top) and IP/UDP2 (bottom). The SGSN has two IP/UDP endpoints: IP/UDP3 (top) and IP/UDP4 (bottom). A dashed arrow labeled 'NS-UNITDATA(R-bit)' points from IP/UDP1 to IP/UDP3. A solid arrow labeled 'NS-UNITDATA(C-bit)' points from IP/UDP1 to IP/UDP4.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +Figure B.2: Example 2 of only one NS entity requesting change flow. The diagram shows a BSS on the left and an SGSN on the right. The BSS has two IP/UDP endpoints: IP/UDP1 (top) and IP/UDP2 (bottom). The SGSN has two IP/UDP endpoints: IP/UDP3 (top) and IP/UDP4 (bottom). A dashed arrow labeled 'NS-UNITDATA(R-bit)' points from IP/UDP1 to IP/UDP3. A solid arrow labeled 'NS-UNITDATA(C-bit)' points from IP/UDP1 to IP/UDP4. + +**Figure B.2: Example 2 of only one NS entity requesting change flow** + +**Example 3:** NS entity triggering resource distribution without data (refer to figure B.3). + +The SGSN may wish to receive uplink data for a mobile at IP/UDP4 and not IP/UDP3. The SGSN may not have downlink data, in which case the SGSN may send a downlink NS-UNITDATA (with R-bit set) containing a BSSGP DL-UNITDATA with an LLC PDU of length 0. + +Subsequent uplink data transfer for the mobile will follow the dotted path from IP/UDP1 to IP/UDP4 through the IP sub-network. + +![Figure B.3: Example 3 of NS entity requesting change flow without data. The diagram shows a BSS on the left and an SGSN on the right. The BSS has two IP/UDP endpoints: IP/UDP1 (top) and IP/UDP2 (bottom). The SGSN has two IP/UDP endpoints: IP/UDP3 (top) and IP/UDP4 (bottom). A solid arrow labeled 'NS-UNITDATA' points from IP/UDP1 to IP/UDP3. A dashed arrow labeled 'NS-UNITDATA(R-bit, BSSGP has LLC with length = 0)' points from IP/UDP1 to IP/UDP4.](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +Figure B.3: Example 3 of NS entity requesting change flow without data. The diagram shows a BSS on the left and an SGSN on the right. The BSS has two IP/UDP endpoints: IP/UDP1 (top) and IP/UDP2 (bottom). The SGSN has two IP/UDP endpoints: IP/UDP3 (top) and IP/UDP4 (bottom). A solid arrow labeled 'NS-UNITDATA' points from IP/UDP1 to IP/UDP3. A dashed arrow labeled 'NS-UNITDATA(R-bit, BSSGP has LLC with length = 0)' points from IP/UDP1 to IP/UDP4. + +**Figure B.3: Example 3 of NS entity requesting change flow without data** + +**Example 4:** NS entities without any resource distribution function (refer to figure B.4). + +The BSS and SGSN may not care which IP endpoint data arrives at as long as the requirements for the load sharing function are met. + +In this case the paths taken by the uplink and downlink data are independent. + +![Sequence diagram showing NS-UNITDATA messages between BSS and SGSN at IP/UDP ports 1, 2, 3, and 4.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +The diagram illustrates a sequence of messages between a Base Station System (BSS) and a Serving GPRS Support Node (SGSN). The BSS is represented by a vertical line on the left, and the SGSN by a vertical line on the right. There are four interaction points labeled IP/UDP1, IP/UDP2 on the BSS side and IP/UDP3, IP/UDP4 on the SGSN side. The first message, labeled NS-UNITDATA, is sent from IP/UDP1 to IP/UDP3 via a solid line with a solid arrowhead. A dashed line with an open arrowhead follows the same path. The second message, also labeled NS-UNITDATA, is sent from IP/UDP4 to IP/UDP2 via a solid line with a solid arrowhead. A dashed line with an open arrowhead follows the same path. + +Sequence diagram showing NS-UNITDATA messages between BSS and SGSN at IP/UDP ports 1, 2, 3, and 4. + +Figure B.4: Example 4 of NS entity not requesting change flow + +# --- Annex C (informative): Change History + +| Meeting / Date | Doc | CR | Rev | Subject/Comment | New version | +|----------------|-----|----|-----|----------------------------------------------------|-------------| +| January 2016 | - | - | - | Creation of Rel-13 version based on version 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48018/05da2a3257316bbf6f448a830dc0380a_img.jpg b/marked/Rel-16/48_series/48018/05da2a3257316bbf6f448a830dc0380a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f129ff88615ef463782d5cd4c8e14f3e00de309e --- /dev/null +++ b/marked/Rel-16/48_series/48018/05da2a3257316bbf6f448a830dc0380a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f0f8ca6fa37d95ebd0d5da98cccec0d4399903dcdcd02cdee521e4c7fc0323c +size 23376 diff --git a/marked/Rel-16/48_series/48018/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/Rel-16/48_series/48018/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccb98459e3af2cd911b38a7ba5202d514f26ef23 --- /dev/null +++ b/marked/Rel-16/48_series/48018/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42355934b102cb9992a2a3e2487b64e9723b309793af641aa855d9adf2c5cd16 +size 32812 diff --git a/marked/Rel-16/48_series/48018/28f2f470a7b2446ae5f525123534383c_img.jpg b/marked/Rel-16/48_series/48018/28f2f470a7b2446ae5f525123534383c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e3f29e9e99b5c4eacc19f78f654c3748ac32dc8 --- /dev/null +++ b/marked/Rel-16/48_series/48018/28f2f470a7b2446ae5f525123534383c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:891829cfeefd17f63cbf58fe8974b22bef8ff2470d1d657e2457bd87803da56f +size 24194 diff --git a/marked/Rel-16/48_series/48018/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/48_series/48018/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45e00981c9fc0053be6408df1d51e1b8e34707b8 --- /dev/null +++ b/marked/Rel-16/48_series/48018/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35ebb02d36fa7766726c8897ffc6e7a7191ea1b3624881f353b947948b30c46b +size 73807 diff --git a/marked/Rel-16/48_series/48018/87b70d2e8951032d28b4412d82cf1413_img.jpg b/marked/Rel-16/48_series/48018/87b70d2e8951032d28b4412d82cf1413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c33c4ba66832761eda8aa4e950011983d9a06316 --- /dev/null +++ b/marked/Rel-16/48_series/48018/87b70d2e8951032d28b4412d82cf1413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3320c7d71840b330718527ac1d6da284c1904b3cf6aeca9b157ca0b4e0619c67 +size 39591 diff --git a/marked/Rel-16/48_series/48018/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/48_series/48018/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63c863fd4824e3f65ca4d6ecf5d5b068d4069816 --- /dev/null +++ b/marked/Rel-16/48_series/48018/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da33e25809f5dd23cabc44c7118f7f8addf490610540503f1d1d10a3843f305a +size 19257 diff --git a/marked/Rel-16/48_series/48018/8fe194ec0e70ac418890f8f1ad02a102_img.jpg b/marked/Rel-16/48_series/48018/8fe194ec0e70ac418890f8f1ad02a102_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b5b6bce2cca337e1b2734728053ab85603157a9 --- /dev/null +++ b/marked/Rel-16/48_series/48018/8fe194ec0e70ac418890f8f1ad02a102_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:085394ef244efb60493f00ef0c5c4b3e30a68852ca982aa79cc0410b407dc8c5 +size 21224 diff --git a/marked/Rel-16/48_series/48018/94c8aee0680a2ea73faab37ba2a0963f_img.jpg b/marked/Rel-16/48_series/48018/94c8aee0680a2ea73faab37ba2a0963f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79519beb8f98f406311df45f1234773aa8e61ea0 --- /dev/null +++ b/marked/Rel-16/48_series/48018/94c8aee0680a2ea73faab37ba2a0963f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aa80845c3493de9cc00df31f4319f7027ed25ec54fb8d2d8e34a1f936207207 +size 27132 diff --git a/marked/Rel-16/48_series/48018/b774dfc5023e15e9c352b97ca25a56d4_img.jpg b/marked/Rel-16/48_series/48018/b774dfc5023e15e9c352b97ca25a56d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07b67eaa2e9cbca4e326511ffded60ca9415d1da --- /dev/null +++ b/marked/Rel-16/48_series/48018/b774dfc5023e15e9c352b97ca25a56d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c35d7b0fc88c1db3ff012e9782ad13d0fd4e7037fd1be1cebad1e6edc44a192 +size 43307 diff --git a/marked/Rel-16/48_series/48018/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-16/48_series/48018/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4b4888d2c8245a73e418aa3cbb2a0302d1172f5 --- /dev/null +++ b/marked/Rel-16/48_series/48018/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a4e335d0f6d10905c5e7211b2b778d28a1f9aa0641fa2e08a7a47600b86b40e +size 20739 diff --git a/marked/Rel-16/48_series/48018/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg b/marked/Rel-16/48_series/48018/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06237eb7b70aa51ef6d4ed1ede2526f1878c13fc --- /dev/null +++ b/marked/Rel-16/48_series/48018/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ced6eab804ba37c54bd803ff063d813bed5543cde5e458d8b0fef022e75f780 +size 18920 diff --git a/marked/Rel-16/48_series/48018/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg b/marked/Rel-16/48_series/48018/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afccec1ee33f1d938ecc8bd0f843af927491c2f5 --- /dev/null +++ b/marked/Rel-16/48_series/48018/d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f7a46a7a620c430cc5218abd695e0117fc6415e6dbe63b053a6d235dfb73843 +size 17755 diff --git a/marked/Rel-16/48_series/48018/f087d3f5d298b3b1634d13ff17879e41_img.jpg b/marked/Rel-16/48_series/48018/f087d3f5d298b3b1634d13ff17879e41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1051a8cae9967f4d015e18cb54959b4a060aed3a --- /dev/null +++ b/marked/Rel-16/48_series/48018/f087d3f5d298b3b1634d13ff17879e41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2107779b3fd06d02cdc8816f18e8feb35898b526a4c4412d57460c791c870305 +size 13909 diff --git a/marked/Rel-16/48_series/48018/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg b/marked/Rel-16/48_series/48018/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e628ef1394017a6634b1df4ab0fbaca3a0681a34 --- /dev/null +++ b/marked/Rel-16/48_series/48018/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d36a85fbc09da2acfbdd9fbf79aa718f51364c57a221fbf402fc76e18c12070 +size 29370 diff --git a/marked/Rel-16/48_series/48018/f40480872b021d2ac7c29202c199b695_img.jpg b/marked/Rel-16/48_series/48018/f40480872b021d2ac7c29202c199b695_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43d9a4829a0a8dd5cc0ee4696fc06c51530b1720 --- /dev/null +++ b/marked/Rel-16/48_series/48018/f40480872b021d2ac7c29202c199b695_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7864e2c768d98c8453cf96b96ae9c29a33171b767ecd43c02bbaa5c2bfe50212 +size 21097 diff --git a/marked/Rel-16/48_series/48018/raw.md b/marked/Rel-16/48_series/48018/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..958dc5da59424c3caae7d93a612f4f7d0017ffb3 --- /dev/null +++ b/marked/Rel-16/48_series/48018/raw.md @@ -0,0 +1,9445 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------|----| +| Foreword..... | 14 | +| 1 Scope..... | 15 | +| 2 References..... | 15 | +| 3 Abbreviations..... | 17 | +| 3.1 Vocabulary..... | 17 | +| 4 Logical configuration of the Gb-interface..... | 18 | +| 4.1 High-level characteristics of the Gb-interface..... | 18 | +| 4.2 Position of BSSGP within the protocol stack on the Gb-interface..... | 18 | +| 5 Elements for layer-to-layer communication..... | 19 | +| 5.1 Definition of service model..... | 19 | +| 5.2 Service primitives provided by the BSSGP at a BSS..... | 21 | +| 5.2.1 RL-DL-UNITDATA.ind..... | 23 | +| 5.2.2 RL-UL-UNITDATA.req..... | 23 | +| 5.2.3 (void)..... | 24 | +| 5.2.3a RL-DL-MBMS-UNITDATA.ind..... | 24 | +| 5.2.3b RL-UL-MBMS-UNITDATA.req..... | 24 | +| 5.2.4 GMM-PAGING.ind..... | 24 | +| 5.2.5 GMM-RA-CAPABILITY.ind..... | 24 | +| 5.2.6 GMM-RA-CAPABILITY-UPDATE.req..... | 24 | +| 5.2.7 GMM-RA-CAPABILITY-UPDATE.cnf..... | 24 | +| 5.2.8 GMM-RADIO-STATUS.req..... | 24 | +| 5.2.9 GMM-SUSPEND.req..... | 24 | +| 5.2.10 GMM-SUSPEND.cnf..... | 24 | +| 5.2.11 GMM-RESUME.req..... | 24 | +| 5.2.12 GMM-RESUME.cnf..... | 24 | +| 5.2.12a GMM-MS-REGISTRATION-ENQUIRY.req..... | 25 | +| 5.2.12b GMM-MS-REGISTRATION-ENQUIRY.res..... | 25 | +| 5.2.13 NM-FLUSH-LL.ind..... | 25 | +| 5.2.14 NM-FLUSH-LL.res..... | 25 | +| 5.2.15 NM-LLC-DISCARDED.req..... | 25 | +| 5.2.16 NM-FLOW-CONTROL-BVC.req..... | 25 | +| 5.2.17 NM-FLOW-CONTROL-BVC.cnf..... | 25 | +| 5.2.18 NM-FLOW-CONTROL-MS.req..... | 25 | +| 5.2.19 NM-FLOW-CONTROL-MS.cnf..... | 25 | +| 5.2.19a NM-FLOW-CONTROL-PFC.req..... | 25 | +| 5.2.19b NM-FLOW-CONTROL-PFC.cnf..... | 25 | +| 5.2.20 NM-STATUS.req..... | 25 | +| 5.2.21 NM-STATUS.ind..... | 26 | +| 5.2.22 NM-BVC-BLOCK.req..... | 26 | +| 5.2.23 NM-BVC-BLOCK.cnf..... | 26 | +| 5.2.24 NM-BVC-UNBLOCK.req..... | 26 | +| 5.2.25 NM-BVC-UNBLOCK.cnf..... | 26 | +| 5.2.26 NM-BVC-RESET.req..... | 26 | +| 5.2.27 NM-BVC-RESET.res..... | 26 | +| 5.2.28 NM-BVC-RESET.ind..... | 26 | +| 5.2.29 NM-BVC-RESET.cnf..... | 26 | +| 5.2.30 NM-TRACE.ind..... | 26 | +| 5.2.30a NW-OVERLOAD.ind..... | 26 | +| 5.2.31 PFM-DOWNLOAD-BSS-PFC.req..... | 26 | +| 5.2.32 PFM-CREATE-BSS-PFC.ind..... | 27 | +| 5.2.33 PFM-CREATE-BSS-PFC.res..... | 27 | +| 5.2.34 PFM-MODIFY-BSS-PFC.req..... | 27 | +| 5.2.35 (void)..... | 27 | +| 5.2.36 (void)..... | 27 | +| 5.2.37 PFM-MODIFY-BSS-PFC.cnf..... | 27 | + +| | | | +|---------|----------------------------------------------------------|----| +| 5.2.38 | PFM-DELETE-BSS-PFC.ind..... | 27 | +| 5.2.39 | PFM-DELETE-BSS-PFC.res..... | 27 | +| 5.2.39a | PFM-DELETE-BSS-PFC.req..... | 27 | +| 5.2.39b | PFM-PS-HANDOVER-REQUIRED.req..... | 27 | +| 5.2.39c | PFM-PS-HANDOVER-REQUIRED.cnf..... | 27 | +| 5.2.39d | PFM-PS-HANDOVER-REQUEST.ind..... | 27 | +| 5.2.39e | PFM-PS-HANDOVER-REQUEST.res..... | 27 | +| 5.2.39f | PFM-PS-HANDOVER-COMPLETE.req..... | 28 | +| 5.2.39g | PFM-PS-HANDOVER-CANCEL.req..... | 28 | +| 5.2.40 | LCS-LOCATE.ind..... | 28 | +| 5.2.41 | LCS-LOCATE.res..... | 28 | +| 5.2.42 | LCS-ABORT.ind..... | 28 | +| 5.2.43 | LCS-INFORMATION-TRANSFER.req..... | 28 | +| 5.2.44 | LCS-INFORMATION-TRANSFER.cnf..... | 28 | +| 5.2.45 | RIM-PDU-TRANSFER.req..... | 28 | +| 5.2.46 | RIM-PDU-TRANSFER.ind..... | 28 | +| 5.2.47 | (void)..... | 29 | +| 5.2.48 | (void)..... | 29 | +| 5.2.49 | (void)..... | 29 | +| 5.2.50 | (void)..... | 29 | +| 5.2.51 | (void)..... | 29 | +| 5.2.52 | (void)..... | 29 | +| 5.2.53 | MBMS-SESSION-START-REQUEST.ind..... | 29 | +| 5.2.54 | MBMS-SESSION-START-RESPONSE.res..... | 29 | +| 5.2.55 | MBMS-SESSION-STOP-REQUEST.ind..... | 29 | +| 5.2.56 | MBMS-SESSION-STOP-RESPONSE.res..... | 29 | +| 5.2.57 | MBMS-SESSION-UPDATE-REQUEST.ind..... | 29 | +| 5.2.58 | MBMS-SESSION-UPDATE-RESPONSE.res..... | 29 | +| 5.3 | Service primitives provided by the BSSGP at an SGSN..... | 29 | +| 5.3.1 | BSSGP-DL-UNITDATA.req..... | 32 | +| 5.3.2 | BSSGP-UL-UNITDATA.ind..... | 32 | +| 5.3.3 | (void)..... | 32 | +| 5.3.3a | BSSGP-DL-MBMS-UNITDATA.req..... | 33 | +| 5.3.3b | BSSGP-UL-MBMS-UNITDATA.ind..... | 33 | +| 5.3.4 | GMM-PAGING.req..... | 33 | +| 5.3.5 | GMM-RA-CAPABILITY.req..... | 33 | +| 5.3.6 | GMM-RA-CAPABILITY-UPDATE.ind..... | 33 | +| 5.3.7 | GMM-RA-CAPABILITY-UPDATE.res..... | 33 | +| 5.3.8 | GMM-RADIO-STATUS.ind..... | 33 | +| 5.3.9 | GMM-SUSPEND.ind..... | 33 | +| 5.3.10 | GMM-RESUME.ind..... | 33 | +| 5.3.10a | GMM-MS-REGISTRATION-ENQUIRY.ind..... | 33 | +| 5.3.10b | GMM-MS-REGISTRATION-ENQUIRY.res..... | 33 | +| 5.3.11 | NM-FLUSH-LL.req..... | 33 | +| 5.3.12 | NM-FLUSH-LL.cnf..... | 34 | +| 5.3.13 | NM-LLC-DISCARDED.ind..... | 34 | +| 5.3.14 | NM-FLOW-CONTROL-BVC.ind..... | 34 | +| 5.3.15 | NM-FLOW-CONTROL-MS.ind..... | 34 | +| 5.3.15a | NM-FLOW-CONTROL-PFC.ind..... | 34 | +| 5.3.16 | NM-STATUS.req..... | 34 | +| 5.3.17 | NM-STATUS.ind..... | 34 | +| 5.3.18 | NM-BVC-BLOCK.ind..... | 34 | +| 5.3.19 | NM-BVC-UNBLOCK.ind..... | 34 | +| 5.3.20 | NM-BVC-RESET.req..... | 34 | +| 5.3.21 | NM-BVC-RESET.res..... | 34 | +| 5.3.22 | NM-BVC-RESET.ind..... | 34 | +| 5.3.23 | NM-BVC-RESET.cnf..... | 35 | +| 5.3.24 | NM-TRACE.req..... | 35 | +| 5.3.24a | NM-OVERLOAD-START.req..... | 35 | +| 5.3.25 | PFM-DOWNLOAD-BSS-PFC.ind..... | 35 | +| 5.3.26 | PFM-CREATE-BSS-PFC.req..... | 35 | + +| | | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 5.3.27 | PFM-CREATE-BSS-PFC.cnf..... | 35 | +| 5.3.28 | PFM-MODIFY-BSS-PFC.ind..... | 35 | +| 5.3.29 | PFM-MODIFY-BSS-PFC.res..... | 35 | +| 5.3.30 | PFM-DELETE-BSS-PFC.req..... | 35 | +| 5.3.31 | PFM-DELETE-BSS-PFC.cnf..... | 35 | +| 5.3.31a | PFM-DELETE-BSS-PFC.ind..... | 35 | +| 5.3.31b | PFM-PS-HANDOVER-REQUIRED.ind..... | 35 | +| 5.3.31c | PFM-PS-HANDOVER-REQUIRED.res..... | 36 | +| 5.3.31d | PFM-PS-HANDOVER-REQUEST.req..... | 36 | +| 5.3.31e | PFM-PS-HANDOVER-REQUEST.cnf..... | 36 | +| 5.3.31f | PFM-PS-HANDOVER-COMPLETE.ind..... | 36 | +| 5.3.31g | PFM-PS-HANDOVER-CANCEL.ind..... | 36 | +| 5.3.32 | LCS-LOCATE.req..... | 36 | +| 5.3.33 | LCS-LOCATE.cnf..... | 36 | +| 5.3.34 | LCS-ABORT.req..... | 36 | +| 5.3.35 | LCS-INFORMATION-TRANSFER.ind..... | 36 | +| 5.3.36 | LCS-INFORMATION-TRANSFER.res..... | 36 | +| 5.3.37 | RIM-PDU-TRANSFER.req..... | 36 | +| 5.3.38 | RIM-PDU-TRANSFER.ind..... | 37 | +| 5.3.39 | (void)..... | 37 | +| 5.3.40 | (void)..... | 37 | +| 5.3.41 | (void)..... | 37 | +| 5.3.42 | (void)..... | 37 | +| 5.3.43 | (void)..... | 37 | +| 5.3.44 | (void)..... | 37 | +| 5.3.45 | MBMS-SESSION-START-REQUEST.req..... | 37 | +| 5.3.46 | MBMS-SESSION-START-RESPONSE.cnf..... | 37 | +| 5.3.47 | MBMS-SESSION-STOP-REQUEST.req..... | 37 | +| 5.3.48 | MBMS-SESSION-STOP-RESPONSE.cnf..... | 37 | +| 5.3.49 | MBMS-SESSION-UPDATE-REQUEST.req..... | 37 | +| 5.3.50 | MBMS-SESSION-UPDATE-RESPONSE.cnf..... | 37 | +| 5.4 | Primitive parameters..... | 37 | +| 5.4.1 | BSSGP Virtual Connection Identifier (BVCI)..... | 37 | +| 5.4.2 | Link Selector Parameter (LSP)..... | 39 | +| 5.4.3 | [functional-name] PDU..... | 39 | +| 5.4.4 | Network Service Entity Identifier (NSEI)..... | 40 | +| 5.4.5 | BSS Context..... | 40 | +| 5.4.6 | MBMS Service Context..... | 40 | +| 5.4.7 | TLLI..... | 40 | +| 6 | User data and signalling procedures between RL and BSSGP SAPs..... | 40 | +| 6.1 | Downlink UNITDATA procedure..... | 40 | +| 6.1.1 | Abnormal conditions..... | 43 | +| 6.2 | Uplink UNITDATA procedure..... | 43 | +| 6.2.1 | Abnormal conditions..... | 44 | +| 6.3 | RA-CAPABILITY procedure..... | 44 | +| 6.3.1 | Abnormal conditions..... | 44 | +| 6.4 | Downlink MBMS-UNITDATA procedure..... | 44 | +| 6.5 | Uplink MBMS-UNITDATA procedure..... | 45 | +| 6.6 | Rerouting procedure in case of MOCN configuration for network sharing, Dedicated Core Networks or MS assisted Dedicated Core Network selection..... | 45 | +| 6.6.1 | General..... | 45 | +| 6.6.2 | Reroute Indication..... | 46 | +| 6.6.3 | Reroute complete..... | 48 | +| 6.6.4 | Abnormal Conditions..... | 48 | +| 6.7 | Rerouting procedure in case of GWCN configuration for network sharing..... | 48 | +| 6.7.1 | General..... | 48 | +| 6.7.2 | Reroute indication..... | 49 | +| 6.7.3 | Reroute complete..... | 50 | +| 6.7.4 | Abnormal Conditions..... | 50 | + +| | | | +|---------|---------------------------------------------------------------------------|----| +| 7 | Signalling procedures between GMM SAPs..... | 50 | +| 7.1 | Paging procedure..... | 50 | +| 7.1a | Paging procedure for Extended Coverage and eDRX..... | 52 | +| 7.1a.1 | Coverage Class and eDRX information available..... | 52 | +| 7.1a.2 | Coverage Class information not available, eDRX information available..... | 52 | +| 7.1a.3 | Coverage Class information available, eDRX information not available..... | 53 | +| 7.1b | Paging Procedure for Extended Coverage with Paging Indication..... | 53 | +| 7.2 | Radio Access Capability Update procedure..... | 53 | +| 7.2.1 | Abnormal conditions..... | 53 | +| 7.3 | Radio Status procedure..... | 54 | +| 7.4 | SUSPEND procedure..... | 54 | +| 7.4.1 | Abnormal conditions..... | 55 | +| 7.5 | RESUME procedure..... | 55 | +| 7.5.1 | Abnormal conditions..... | 55 | +| 7.6 | MS Registration Enquiry..... | 56 | +| 7.6.1 | General..... | 56 | +| 7.6.2 | Registration enquiry..... | 56 | +| 7.6.3 | Registration response..... | 56 | +| 8 | Signalling procedures between NM SAPs..... | 56 | +| 8.1 | FLUSH-LL (logical link) procedure..... | 56 | +| 8.1.1 | Abnormal Conditions..... | 58 | +| 8.2 | Flow Control procedure..... | 58 | +| 8.2.1 | General model of operation..... | 58 | +| 8.2.2 | Mode of operation..... | 58 | +| 8.2.3 | Flow Control of Traffic from an SGSN to BSS..... | 59 | +| 8.2.3.1 | Control of the downlink throughput by the SGSN..... | 59 | +| 8.2.3.2 | Flow Control Conformance Definition..... | 60 | +| 8.2.3.3 | Response time within the SGSN to flow control messages..... | 62 | +| 8.2.3.4 | Frequency of sending BVC or MS or PFC Flow Control PDUs..... | 62 | +| 8.2.3.5 | FLOW-CONTROL PDUs..... | 62 | +| 8.2.3.6 | Condition of Bmax for MS after Initial Flow-Control-BVC..... | 63 | +| 8.2.4 | Flow Control of Uplink Traffic from a BSS to an SGSN..... | 63 | +| 8.3 | BVC blocking and unblocking procedure..... | 63 | +| 8.3.1 | PTP BVC..... | 63 | +| 8.3.2 | Signalling BVC..... | 64 | +| 8.3.3 | Abnormal Conditions..... | 64 | +| 8.4 | BVC-RESET procedure..... | 65 | +| 8.4.1 | Signalling BVC..... | 66 | +| 8.4.2 | PTP BVC..... | 66 | +| 8.4.3 | Abnormal Conditions..... | 66 | +| 8.5 | Trace procedure..... | 66 | +| 8.6 | Overload Control procedure..... | 67 | +| 8.6.1 | General..... | 67 | +| 8.6.2 | Overload Operation..... | 67 | +| 8a | Signalling procedures between PFM SAPs..... | 67 | +| 8a.1 | Create BSS PFC procedure..... | 67 | +| 8a.1.0 | General..... | 67 | +| 8a.1.0a | Allocation/Retention Priority handling..... | 68 | +| 8a.1.1 | Abnormal conditions..... | 70 | +| 8a.2 | Modify BSS PFC procedure..... | 70 | +| 8a.2.1 | Abnormal conditions..... | 70 | +| 8a.3 | Delete BSS PFC procedure..... | 71 | +| 8a.4 | PS Handover Required procedure..... | 71 | +| 8a.4.1 | Abnormal conditions..... | 73 | +| 8a.5 | PS Handover Request procedure..... | 73 | +| 8a.5.1 | Abnormal conditions..... | 74 | +| 8a.6 | PS Handover Complete procedure..... | 75 | +| 8a.6.1 | Abnormal conditions..... | 75 | +| 8a.7 | PS Handover Cancel procedure..... | 75 | +| 8a.7.1 | Abnormal conditions..... | 76 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------|----| +| 8b | Signalling Procedures between LCS SAPs..... | 77 | +| 8b.1 | Location Procedure..... | 77 | +| 8b.1.1 | Unsuccessful Operation..... | 78 | +| 8b.1.2 | Abnormal Conditions..... | 78 | +| 8b.1.3 | Overload..... | 78 | +| 8b.2 | Position Command Procedure..... | 79 | +| 8b.2.1 | Position Command..... | 79 | +| 8b.2.2 | Position Response..... | 79 | +| 8b.2.3 | Unsuccessful Operation..... | 79 | +| 8c | Signalling procedures between RIM SAPs..... | 80 | +| 8c.1 | General..... | 80 | +| 8c.1.1 | Introduction..... | 80 | +| 8c.1.2 | Definitions..... | 80 | +| 8c.1.2.1 | Controlling, serving, originating and receiving nodes..... | 80 | +| 8c.1.2.2 | RIM association..... | 80 | +| 8c.1.2.3 | RIM variables..... | 81 | +| 8c.1.3 | RIM PDUs description..... | 81 | +| 8c.1.3.1 | RAN-INFORMATION-REQUEST PDU..... | 81 | +| 8c.1.3.2 | RAN-INFORMATION PDU..... | 81 | +| 8c.1.3.3 | RAN-INFORMATION-ACK PDU..... | 82 | +| 8c.1.3.4 | RAN-INFORMATION-ERROR PDU..... | 82 | +| 8c.1.3.5 | RAN-INFORMATION-APPLICATION-ERROR PDU..... | 82 | +| 8c.1.4 | RIM addressing and routing principles..... | 82 | +| 8c.1.4.1 | RIM routing address..... | 82 | +| 8c.1.4.1.1 | GERAN BSS identification..... | 82 | +| 8c.1.4.1.2 | UTRAN RNS identification..... | 82 | +| 8c.1.4.1.3 | E-UTRAN eNodeB identification..... | 82 | +| 8c.1.4.1.4 | eHRPD eAN identification..... | 82 | +| 8c.1.4.2 | Routing via the core network..... | 82 | +| 8c.1.4.3 | Address mirroring..... | 83 | +| 8c.1.5 | In-order delivery and reliable transfer - RSN..... | 83 | +| 8c.1.5.1 | General..... | 83 | +| 8c.1.5.2 | Allocating RSN values at the sending BSS..... | 84 | +| 8c.1.5.3 | Comparing RSN values at the receiving BSS..... | 84 | +| 8c.1.6 | RIM Protocol Version Number..... | 84 | +| 8c.2 | RIM procedures..... | 85 | +| 8c.2.1 | General..... | 85 | +| 8c.2.2 | RAN Information Request procedure..... | 85 | +| 8c.2.2.1 | RAN Information Request/Single Report procedure..... | 85 | +| 8c.2.2.1.1 | Initiation by the controlling BSS..... | 85 | +| 8c.2.2.1.2 | Reception of a valid RAN-INFORMATION-REQUEST/Single Report PDU by the serving BSS..... | 86 | +| 8c.2.2.1.3 | Reception of a valid RAN-INFORMATION/Single Report PDU by the controlling BSS..... | 86 | +| 8c.2.2.1.4 | Expiration of T(RIR) in the controlling BSS..... | 86 | +| 8c.2.2.2 | RAN Information Request/Multiple Report procedure..... | 86 | +| 8c.2.2.2.1 | Initiation by the controlling BSS..... | 87 | +| 8c.2.2.2.2 | Reception of a valid RAN-INFORMATION-REQUEST/Multiple Report PDU by the serving BSS..... | 87 | +| 8c.2.2.2.3 | Reception of a valid RAN-INFORMATION PDU/Initial Multiple Report PDU by the controlling BSS..... | 88 | +| 8c.2.2.2.4 | Expiration of T(RIR) in the controlling BSS..... | 88 | +| 8c.2.2.3 | RAN Information Request/Stop procedure..... | 88 | +| 8c.2.2.3.1 | Initiation by the controlling BSS..... | 88 | +| 8c.2.2.3.2 | Reception of a valid RAN-INFORMATION-REQUEST/Stop PDU by the serving BSS..... | 88 | +| 8c.2.2.3.3 | Reception of a valid RAN-INFORMATION/Stop PDU by the controlling BSS..... | 89 | +| 8c.2.2.3.4 | Expiration of T(RIR) in the controlling BSS..... | 89 | +| 8c.2.3 | RAN Information Send procedure..... | 90 | +| 8c.2.3a | Autonomous RAN Information Send procedure..... | 90 | +| 8c.2.3a.1 | Initiation by the originating BSS..... | 90 | +| 8c.2.3a.2 | Reception of a valid RAN-INFORMATION PDU by the receiving BSS..... | 91 | +| 8c.2.3a.3 | Reception of a valid RAN-INFORMATION-ACK PDU in the originating BSS..... | 91 | + +| | | | +|-----------|---------------------------------------------------------------------------------------|-----| +| 8c.2.3a.4 | Expiration of T(RI) in the originating BSS..... | 91 | +| 8c.2.3.1 | Initiation by the serving BSS..... | 91 | +| 8c.2.3.2 | Reception of a valid RAN-INFORMATION PDU by the controlling BSS..... | 92 | +| 8c.2.3.3 | Reception of a valid RAN-INFORMATION-ACK PDU in the serving BSS..... | 93 | +| 8c.2.3.4 | Expiration of T(RI) in the serving BSS..... | 93 | +| 8c.2.4 | RAN Information Application Error procedure..... | 93 | +| 8c.2.4.1 | Initiation by the controlling or receiving BSS..... | 93 | +| 8c.2.4.2 | Reception of a valid RAN-INFORMATION-APPLICATION-ERROR PDU by the serving BSS..... | 94 | +| 8c.2.4.3 | Reception of a valid RAN-INFORMATION-ACK PDU by the controlling or receiving BSS..... | 94 | +| 8c.2.4.4 | Expiration of T(RIAE) in the controlling or receiving BSS..... | 94 | +| 8c.2.5 | RAN Information Error procedure..... | 95 | +| 8c.3 | Abnormal conditions..... | 95 | +| 8c.3.0 | General..... | 95 | +| 8c.3.1 | Abnormal conditions at the BSSGP level..... | 95 | +| 8c.3.1.1 | General..... | 95 | +| 8c.3.1.2 | RIM addressing error in BSS..... | 95 | +| 8c.3.1.3 | RIM addressing error in the CN..... | 96 | +| 8c.3.1.4 | RIM PDU addressed to a BSS not supporting RIM..... | 96 | +| 8c.3.2 | Abnormal conditions encountered in the RIM container..... | 96 | +| 8c.3.2.1 | Unknown RIM Application Identity..... | 96 | +| 8c.3.2.2 | Erroneous PDU Type Extension field..... | 96 | +| 8c.3.2.3 | Missing conditional IE..... | 96 | +| 8c.3.2.4 | Missing mandatory IE..... | 96 | +| 8c.3.2.5 | Syntactical error in an expected conditional IE..... | 97 | +| 8c.3.2.6 | Syntactical error in a mandatory IE..... | 97 | +| 8c.3.2.7 | Unexpected conditional IE..... | 97 | +| 8c.3.2.8 | Containers with out-of-sequence information elements..... | 97 | +| 8c.3.2.9 | Container with semantically incorrect content..... | 97 | +| 8c.3.3 | Unexpected RIM PDU..... | 98 | +| 8c.3.4 | RIM error reporting..... | 98 | +| 8c.3.4.1 | General..... | 98 | +| 8c.3.4.2 | Sending of a RAN-INFORMATION-ERROR PDU..... | 98 | +| 8c.3.4.3 | Reception of a RAN-INFORMATION-ERROR PDU in the BSS..... | 98 | +| 8c.4 | RIM timers..... | 98 | +| 8c.5 | Action upon deletion of a cell in a BSS..... | 99 | +| 8c.5.0 | General..... | 99 | +| 8c.5.1 | Actions due to the deletion of the cell..... | 99 | +| 8c.5.2 | Additional actions in the case the deleted cell is used as a source cell by RIM..... | 99 | +| 8c.6 | Specific requirements related to RIM applications..... | 100 | +| 8c.6.0 | General requirements..... | 100 | +| 8c.6.1 | Requirements related to the NACC RIM application..... | 100 | +| 8c.6.2 | SI3 application..... | 100 | +| 8c.6.3 | MBMS data channel application..... | 101 | +| 8c.6.4 | Requirements related to the SON Transfer RIM application..... | 101 | +| 8c.6.5 | Requirements related to the UTRA SI RIM application..... | 102 | +| 8c.6.6 | Multilateration Timing Advance application..... | 102 | +| 8d | Signalling procedures between MBMS SAPs..... | 103 | +| 8d.1 | General..... | 103 | +| 8d.2 | MBMS Session Start..... | 103 | +| 8d.2.1 | Abnormal Conditions..... | 105 | +| 8d.3 | MBMS Session Stop..... | 105 | +| 8d.3.1 | Abnormal Conditions..... | 105 | +| 8d.4 | MBMS Session Update..... | 105 | +| 8d.4.1 | Abnormal Conditions..... | 107 | +| 9 | General Protocol Error Handling..... | 107 | +| 10 | PDU functional definitions and contents..... | 107 | +| 10.1 | General Structure Of A PDU..... | 107 | +| 10.2 | PDU functional definitions and contents at RL and BSSGP SAPs..... | 108 | +| 10.2.1 | DL-UNITDATA..... | 108 | +| 10.2.2 | UL-UNITDATA..... | 110 | + +| | | | +|-----------|---------------------------------------------------------|-----| +| 10.2.3 | RA-CAPABILITY..... | 112 | +| 10.2.4 | (void)..... | 112 | +| 10.2.5 | DL-MBMS-UNITDATA..... | 113 | +| 10.2.6 | UL-MBMS-UNITDATA..... | 113 | +| 10.3 | PDU functional definitions and contents at GMM SAP..... | 113 | +| 10.3.1 | PAGING PS..... | 113 | +| 10.3.2 | PAGING CS..... | 115 | +| 10.3.3 | RA-CAPABILITY-UPDATE..... | 115 | +| 10.3.4 | RA-CAPABILITY-UPDATE-ACK..... | 116 | +| 10.3.5 | RADIO-STATUS..... | 116 | +| 10.3.6 | SUSPEND..... | 116 | +| 10.3.7 | SUSPEND-ACK..... | 117 | +| 10.3.8 | SUSPEND-NACK..... | 117 | +| 10.3.9 | RESUME..... | 117 | +| 10.3.10 | RESUME-ACK..... | 118 | +| 10.3.11 | RESUME-NACK..... | 118 | +| 10.3.12 | DUMMY PAGING PS..... | 118 | +| 10.3.13 | DUMMY PAGING PS RESPONSE..... | 119 | +| 10.3.14 | PAGING PS REJECT..... | 119 | +| 10.3.15 | MS REGISTRATION ENQUIRY..... | 119 | +| 10.3.16 | MS REGISTRATION ENQUIRY RESPONSE..... | 119 | +| 10.4 | PDU functional definitions and contents at NM SAP..... | 120 | +| 10.4.1 | FLUSH-LL..... | 120 | +| 10.4.2 | FLUSH-LL-ACK..... | 120 | +| 10.4.3 | LLC-DISCARDED..... | 121 | +| 10.4.4 | FLOW-CONTROL-BVC..... | 121 | +| 10.4.5 | FLOW-CONTROL-BVC-ACK..... | 121 | +| 10.4.6 | FLOW-CONTROL-MS..... | 122 | +| 10.4.7 | FLOW-CONTROL-MS-ACK..... | 122 | +| 10.4.8 | BVC-BLOCK..... | 122 | +| 10.4.9 | BVC-BLOCK-ACK..... | 123 | +| 10.4.10 | BVC-UNBLOCK..... | 123 | +| 10.4.11 | BVC-UNBLOCK-ACK..... | 123 | +| 10.4.12 | BVC-RESET..... | 124 | +| 10.4.13 | BVC-RESET-ACK..... | 124 | +| 10.4.14 | STATUS..... | 125 | +| 10.4.14.1 | Static conditions for BVCI..... | 125 | +| 10.4.15 | SGSN-INVOKE-TRACE..... | 125 | +| 10.4.16 | DOWNLOAD-BSS-PFC..... | 126 | +| 10.4.17 | CREATE-BSS-PFC..... | 126 | +| 10.4.18 | CREATE-BSS-PFC-ACK..... | 126 | +| 10.4.19 | CREATE-BSS-PFC-NACK..... | 127 | +| 10.4.20 | MODIFY-BSS-PFC..... | 127 | +| 10.4.21 | MODIFY-BSS-PFC-ACK..... | 127 | +| 10.4.22 | DELETE-BSS-PFC..... | 128 | +| 10.4.23 | DELETE-BSS-PFC-ACK..... | 128 | +| 10.4.24 | FLOW-CONTROL-PFC..... | 128 | +| 10.4.25 | FLOW-CONTROL-PFC-ACK..... | 129 | +| 10.4.26 | DELETE-BSS-PFC-REQ..... | 129 | +| 10.4.27 | PS-HANDOVER-REQUIRED..... | 129 | +| 10.4.28 | PS-HANDOVER-REQUIRED-ACK..... | 130 | +| 10.4.29 | PS-HANDOVER-REQUIRED-NACK..... | 130 | +| 10.4.30 | PS-HANDOVER-REQUEST..... | 131 | +| 10.4.31 | PS-HANDOVER-REQUEST-ACK..... | 131 | +| 10.4.32 | PS-HANDOVER-REQUEST-NACK..... | 132 | +| 10.4.33 | PS-HANDOVER-COMPLETE..... | 132 | +| 10.4.34 | PS-HANDOVER-CANCEL..... | 132 | +| 10.4.35 | PS-HANDOVER-COMPLETE-ACK..... | 133 | +| 10.5 | PDU functional definitions and contents at LCS SAP..... | 133 | +| 10.5.1 | PERFORM-LOCATION-REQUEST..... | 133 | +| 10.5.2 | PERFORM-LOCATION-RESPONSE..... | 135 | + +| | | | +|---------|----------------------------------------------------------|-----| +| 10.5.3 | PERFORM-LOCATION-ABORT..... | 135 | +| 10.5.4 | POSITION-COMMAND..... | 136 | +| 10.5.5 | POSITION-RESPONSE..... | 136 | +| 10.6 | PDU functional definitions and contents at RIM SAP..... | 136 | +| 10.6.1 | RAN-INFORMATION-REQUEST..... | 136 | +| 10.6.2 | RAN-INFORMATION..... | 137 | +| 10.6.3 | RAN-INFORMATION-ACK..... | 137 | +| 10.6.4 | RAN-INFORMATION-ERROR..... | 137 | +| 10.6.5 | RAN-INFORMATION-APPLICATION-ERROR..... | 138 | +| 10.7 | PDU functional definitions and contents at MBMS SAP..... | 138 | +| 10.7.1 | MBMS-SESSION-START-REQUEST..... | 138 | +| 10.7.2 | MBMS-SESSION-START-RESPONSE..... | 139 | +| 10.7.3 | MBMS-SESSION-STOP-REQUEST..... | 139 | +| 10.7.4 | MBMS-SESSION-STOP-RESPONSE..... | 139 | +| 10.7.5 | MBMS-SESSION-UPDATE-REQUEST..... | 139 | +| 10.7.6 | MBMS-SESSION-UPDATE-RESPONSE..... | 140 | +| 11 | General information elements coding..... | 140 | +| 11.1 | General structure of the information elements..... | 140 | +| 11.2 | Information element description..... | 140 | +| 11.3 | Information Element Identifier (IEI)..... | 141 | +| 11.3.1 | Alignment octets..... | 143 | +| 11.3.2 | Bmax default MS..... | 143 | +| 11.3.3 | BSS Area Indication..... | 144 | +| 11.3.4 | Bucket Leak Rate (R)..... | 144 | +| 11.3.5 | BVC Bucket Size..... | 144 | +| 11.3.6 | BVCI (BSSGP Virtual Connection Identifier)..... | 144 | +| 11.3.7 | BVC Measurement..... | 145 | +| 11.3.8 | Cause..... | 145 | +| 11.3.9 | Cell Identifier..... | 147 | +| 11.3.10 | Channel needed..... | 147 | +| 11.3.11 | DRX Parameters..... | 147 | +| 11.3.12 | eMLPP-Priority..... | 147 | +| 11.3.13 | Flush Action..... | 148 | +| 11.3.14 | IMSI..... | 148 | +| 11.3.15 | LLC-PDU..... | 148 | +| 11.3.16 | LLC Frames Discarded..... | 149 | +| 11.3.17 | Location Area..... | 149 | +| 11.3.18 | LSA Identifier List..... | 149 | +| 11.3.19 | LSA Information..... | 149 | +| 11.3.20 | Mobile Id..... | 149 | +| 11.3.21 | MS Bucket Size..... | 150 | +| 11.3.22 | MS Radio Access Capability..... | 150 | +| 11.3.23 | OMC Id..... | 150 | +| 11.3.24 | PDU In Error..... | 150 | +| 11.3.25 | PDU Lifetime..... | 151 | +| 11.3.26 | PDU Type..... | 152 | +| 11.3.27 | Priority..... | 153 | +| 11.3.28 | QoS Profile..... | 153 | +| 11.3.29 | Radio Cause..... | 155 | +| 11.3.30 | RA-Cap-UPD-Cause..... | 155 | +| 11.3.31 | Routeing Area..... | 156 | +| 11.3.32 | R_default_MS..... | 156 | +| 11.3.33 | Suspend Reference Number..... | 156 | +| 11.3.34 | Tag..... | 156 | +| 11.3.35 | Temporary logical link Identity (TLLI)..... | 157 | +| 11.3.36 | Temporary Mobile Subscriber Identity (TMSI)..... | 157 | +| 11.3.37 | Trace Reference..... | 157 | +| 11.3.38 | Trace Type..... | 157 | +| 11.3.39 | Transaction Id..... | 158 | +| 11.3.40 | Trigger Id..... | 158 | +| 11.3.41 | Number of octets affected..... | 158 | + +| | | | +|-------------|-----------------------------------------------------------------------------------------------|-----| +| 11.3.42 | Packet Flow Identifier (PFI)..... | 158 | +| 11.3.42a | (void)..... | 159 | +| 11.3.43 | Aggregate BSS QoS Profile..... | 159 | +| 11.3.44 | GPRS Timer..... | 159 | +| 11.3.45 | Feature Bitmap..... | 159 | +| 11.3.46 | Bucket Full Ratio..... | 161 | +| 11.3.47 | Service UTRAN CCO..... | 161 | +| 11.3.48 | NSEI (Network Service Entity Identifier)..... | 161 | +| 11.3.49 | RRLP APDU..... | 162 | +| 11.3.50 | LCS QoS..... | 162 | +| 11.3.51 | LCS Client Type..... | 162 | +| 11.3.52 | Requested GPS Assistance Data..... | 162 | +| 11.3.53 | Location Type..... | 163 | +| 11.3.54 | Location Estimate..... | 163 | +| 11.3.55 | Positioning Data..... | 163 | +| 11.3.56 | Deciphering Keys..... | 163 | +| 11.3.57 | LCS Priority..... | 164 | +| 11.3.58 | LCS Cause..... | 164 | +| 11.3.59 | LCS Capability..... | 164 | +| 11.3.60 | RRLP Flags..... | 164 | +| 11.3.61 | RIM Application Identity..... | 165 | +| 11.3.62 | RIM Sequence Number..... | 166 | +| 11.3.62a | RIM Container..... | 166 | +| 11.3.62a.0 | General..... | 166 | +| 11.3.62a.1 | RAN-INFORMATION-REQUEST RIM Container..... | 166 | +| 11.3.62a.2 | RAN-INFORMATION RIM Container..... | 167 | +| 11.3.62a.3 | RAN-INFORMATION-ACK RIM Container..... | 167 | +| 11.3.62a.4 | RAN-INFORMATION-ERROR RIM Container..... | 168 | +| 11.3.62a.5 | RAN-INFORMATION-APPLICATION-ERROR RIM Container..... | 168 | +| 11.3.63 | Application Container..... | 169 | +| 11.3.63.1 | RAN-INFORMATION-REQUEST Application Container..... | 169 | +| 11.3.63.1.0 | General..... | 169 | +| 11.3.63.1.1 | RAN-INFORMATION-REQUEST Application Container for the NACC Application..... | 169 | +| 11.3.63.1.2 | RAN-INFORMATION-REQUEST Application Container for the SI3 Application..... | 169 | +| 11.3.63.1.3 | RAN-INFORMATION-REQUEST Application Container for the MBMS data channel Application..... | 169 | +| 11.3.63.1.4 | RAN-INFORMATION-REQUEST Application Container for the SON Transfer Application..... | 170 | +| 11.3.63.1.5 | RAN-INFORMATION-REQUEST Application Container for the UTRA SI Application..... | 170 | +| 11.3.63.2 | RAN-INFORMATION Application Container Unit..... | 171 | +| 11.3.63.2.0 | General..... | 171 | +| 11.3.63.2.1 | RAN-INFORMATION Application Container for the NACC Application..... | 171 | +| 11.3.63.2.2 | RAN-INFORMATION Application Container for the SI3 Application..... | 172 | +| 11.3.63.2.3 | RAN-INFORMATION Application Container for the MBMS data channel Application..... | 172 | +| 11.3.63.2.4 | RAN-INFORMATION Application Container for the SON Transfer Application..... | 174 | +| 11.3.63.2.5 | RAN-INFORMATION Application Container for the UTRA SI Application..... | 174 | +| 11.3.63.2.6 | RAN-INFORMATION Application Container for the Multilateration Timing Advance Application..... | 175 | +| 11.3.64 | Application Error Container..... | 175 | +| 11.3.64.1 | Application Error Container layout for the NACC application..... | 175 | +| 11.3.64.2 | Application Error Container for the SI3 application..... | 176 | +| 11.3.64.3 | Application Error Container for the MBMS data channel application..... | 177 | +| 11.3.64.4 | Application Error Container for the SON Transfer Application..... | 178 | +| 11.3.64.5 | Application Error Container for the UTRA SI Application..... | 178 | +| 11.3.64.6 | Application Error Container for the Multilateration Timing Advance Application..... | 179 | +| 11.3.65 | RIM PDU Indications..... | 179 | +| 11.3.65.0 | General..... | 179 | +| 11.3.65.1 | RAN-INFORMATION-REQUEST RIM PDU Indications..... | 179 | +| 11.3.65.2 | RAN-INFORMATION RIM PDU Indications..... | 180 | +| 11.3.65.3 | RAN-INFORMATION-APPLICATION-ERROR RIM PDU Indications..... | 180 | +| 11.3.66 | (void)..... | 180 | +| 11.3.67 | RIM Protocol Version Number..... | 180 | + +| | | | +|----------|---------------------------------------------------------|-----| +| 11.3.68 | PFC Flow Control parameters..... | 181 | +| 11.3.69 | Global CN-Id..... | 182 | +| 11.3.70 | RIM Routing Information..... | 182 | +| 11.3.71 | MBMS Session Identity..... | 183 | +| 11.3.72 | MBMS Session Duration..... | 183 | +| 11.3.73 | MBMS Service Area Identity List..... | 184 | +| 11.3.74 | MBMS Response..... | 184 | +| 11.3.75 | MBMS Routing Area List..... | 185 | +| 11.3.76 | MBMS Session Information..... | 185 | +| 11.3.77 | TMGI (Temporary Mobile Group Identity)..... | 186 | +| 11.3.78 | MBMS Stop Cause..... | 186 | +| 11.3.79 | Source BSS to Target BSS Transparent Container..... | 187 | +| 11.3.80 | Target BSS to Source BSS Transparent Container..... | 187 | +| 11.3.81 | NAS container for PS Handover..... | 188 | +| 11.3.82 | PFCs to be set-up list..... | 188 | +| 11.3.83 | List of set-up PFCs..... | 189 | +| 11.3.84 | Extended Feature Bitmap..... | 190 | +| 11.3.85 | Source to Target Transparent Container..... | 191 | +| 11.3.86 | Target to Source Transparent Container..... | 191 | +| 11.3.87 | RNC Identifier..... | 192 | +| 11.3.88 | Page Mode..... | 193 | +| 11.3.89 | Container ID..... | 193 | +| 11.3.90 | Global TFI..... | 193 | +| 11.3.91 | IMEI..... | 194 | +| 11.3.92 | Time to MBMS Data Transfer..... | 194 | +| 11.3.93 | MBMS Session Repetition Number..... | 194 | +| 11.3.94 | Inter RAT Handover Info..... | 195 | +| 11.3.95 | PS Handover Command..... | 195 | +| 11.3.95a | PS Handover Indications..... | 195 | +| 11.3.95b | SI/PSI Container..... | 195 | +| 11.3.95c | Active PFCs List..... | 197 | +| 11.3.96 | Velocity Data..... | 197 | +| 11.3.97 | DTM Handover Command..... | 197 | +| 11.3.98 | CS Indication..... | 198 | +| 11.3.99 | Requested GANSS Assistance Data..... | 198 | +| 11.3.100 | GANSS Location Type..... | 198 | +| 11.3.101 | GANSS Positioning Data..... | 198 | +| 11.3.102 | Flow Control Granularity..... | 199 | +| 11.3.103 | eNB Identifier..... | 199 | +| 11.3.104 | E-UTRAN Inter RAT Handover Info..... | 200 | +| 11.3.105 | Subscriber Profile ID for RAT/Frequency priority..... | 200 | +| 11.3.106 | Request for Inter-RAT Handover Info..... | 200 | +| 11.3.107 | Reliable Inter-RAT Handover Info..... | 201 | +| 11.3.108 | SON Transfer Application Identity..... | 201 | +| 11.3.109 | CSG Identifier..... | 201 | +| 11.3.110 | Tracking Area Code..... | 202 | +| 11.3.111 | Redirect Attempt Flag..... | 202 | +| 11.3.112 | Redirection Indication..... | 203 | +| 11.3.113 | Redirection Completed..... | 203 | +| 11.3.114 | Unconfirmed send state variable..... | 204 | +| 11.3.115 | IRAT Measurement Configuration..... | 204 | +| 11.3.116 | SCI..... | 205 | +| 11.3.117 | GGSN/P-GW location..... | 205 | +| 11.3.118 | Selected PLMN ID..... | 206 | +| 11.3.119 | Priority Class Indicator..... | 206 | +| 11.3.120 | Source Cell ID IE..... | 206 | +| 11.3.121 | IRAT Measurement Configuration (extended E-ARFCNs)..... | 207 | +| 11.3.122 | eDRX Parameters..... | 209 | +| 11.3.123 | Time Until Next Paging Occasion..... | 209 | +| 11.3.124 | Coverage Class..... | 210 | +| 11.3.125 | Paging Attempt Information..... | 210 | + +| | | | +|------------------------|-----------------------------------------------|-----| +| 11.3.126 | Exception Report Flag..... | 211 | +| 11.3.127 | Old Routing Area Identification..... | 211 | +| 11.3.128 | Attach Indicator..... | 212 | +| 11.3.129 | PLMN Identity..... | 212 | +| 11.3.130 | MME Query..... | 212 | +| 11.3.131 | SGSN Group Identity..... | 212 | +| 11.3.132 | Additional P-TMSI..... | 213 | +| 11.3.133 | UE Usage Type..... | 213 | +| 11.3.134 | DCN-ID..... | 213 | +| 11.3.135 | Void..... | 214 | +| 11.3.136 | Multilateration Timer..... | 214 | +| 11.3.137 | Multilateration Timing Advance..... | 214 | +| 11.3.138 | MS Sync Accuracy..... | 214 | +| 11.3.139 | BTS Reception Accuracy Level..... | 215 | +| 11.3.140 | Timing Advance Request (TAR)..... | 215 | +| 11.3.141 | Enhanced Coverage Additional Information..... | 215 | +| 11.3.142 | MTA Access Security Required(MTASR)..... | 216 | +| 11.3.143 | MTA Sequence..... | 216 | +| 11.3.144 | MTA Signature..... | 216 | +| 12 | List of system variables..... | 217 | +| 12.1 | General Variables..... | 217 | +| 12.2 | Flow control variables..... | 217 | +| Annex A (informative): | Change history..... | 219 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies or references procedures used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface for control of GSM packet data services within the digital cellular telecommunications system (Phase 2+). + +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 or references procedures used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface for control of GSM packet data services. + +The functional split between BSS and SGSN is defined in 3GPP TS 23.060 which states that a BSS is responsible for local radio resource allocation. The required procedures between BSS and SGSN are defined in detail in the present document. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] (void). +- [3] (void). +- [4] (void). +- [5] (void). +- [6] (void). +- [7] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [8] (void). +- [9] (void). +- [10] 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2". +- [11] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [12] 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) Layer Specification". +- [13] (void). +- [14] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [15] (void). +- [16] 3GPP TS 48.016: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Network Service". +- [17] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs Interface Layer 3 specification". +- [18] 3GPP TS 32.008: "Subscriber and equipment trace". + +- [19] ITU-T Recommendation X.200 (White Book): "Information technology - Open Systems Interconnection - Basic Reference Model: The basic model". +- [20] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". +- [21] (void). +- [22] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [23] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services (LCS) in GERAN". +- [24] 3GPP TS 49.031: "Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". +- [25] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [26] 3GPP TR 44.901: "External Network Assisted Cell Change (NACC)". +- [27] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [28] 3GPP TS 12.20: "Base Station System (BSS) Management Information". +- [29] 3GPP TS 43.246: "Multimedia Broadcast Multicast Service (MBMS) in the GERAN Stage 2". +- [30] 3GPP TS 26.346: "Multimedia Broadcast Multicast Service Protocols and Codecs". +- [31] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [32] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS) Architecture and Functional Description". +- [33] IETF RFC 3588: "Diameter Base Protocol". +- [34] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2". +- [35] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [36] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access (E-UTRA); S1 Application Protocol (SIAP)". +- [37] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage3". +- [38] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [39] 3GPP TS 22.220: "Service Requirements for Home NodeBs and Home eNodeBs". +- [40] 3GPP TS 23.003: "Numbering, addressing and identification". +- [41] 3GPP TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [42] 3GPP TS 25.331: "Technical Specification Group Radio Access Network; Radio Resource Control (RRC)". +- [43] 3GPP TS 23.251: "Network sharing - Architecture and functional description". +- [44] 3GPP TS 45.008: "Radio subsystem link control". +- [45] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". + +- [46] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)" +- [47] 3GPP2 C.S0024-B: "cdma2000 High Rate Packet Data Air Interface Specification". +- [48] 3GPP TS 45.002: "Technical Specification Group GSM/EDGE Radio Access Network; Multiplexing and multiple access on the radio path" +- [49] 3GPP TS 24.301: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". + +## 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and in 3GPP TS 48.016 and the following apply: + +| | | +|---------|-----------------------------------------------------------------| +| ABQP | Aggregate BSS QoS Profile | +| CBL | Current Bucket Level | +| CCN | Cell Change Notification | +| CS | Circuit switched | +| CSG | Closed Subscriber Group | +| DCN | Dedicated Core Network | +| DCN-ID | Dedicated Core Network ID | +| DL | Downlink | +| eAN | evolved Access Network | +| eDRX | Extended Discontinuous Reception | +| eHRPD | enhanced High Rate Packet Data | +| eNB | E-UTRAN NodeB | +| E-UTRA | Evolved UTRA | +| E-UTRAN | Evolved UTRAN | +| GWCN | GateWay Core Network | +| LCS | Location Services | +| MBMS | Multimedia Broadcast Multicast Service | +| MME | Mobility Management Entity | +| MOCN | Multi Operator Core Network | +| NACC | Network Assisted Cell Change | +| NRI | Network Resource Identifier | +| NSE | Network Service Entity | +| PFC | Packet Flow Context | +| PFI | Packet Flow Identifier | +| PFM | Packet Flow Management | +| PFT | Packet Flow Timer | +| PS | Packet switched | +| RAN | Radio Access Network | +| RIM | RAN Information Management | +| RRLP | Radio Resource LCS Protocol | +| RSN | RIM Sequence Number | +| SIRUG | Service Identification for improved Radio Utilization for GERAN | +| SON | Self-Organizing Networks | +| SPID | Subscriber Profile ID for RAT/Frequency priority | +| TAI | Tracking Area Identity | +| TMGI | Temporary Mobile Group Identity | +| TOM | Tunneling of Messages | +| RIM | RAN Information Management | +| UL | Uplink | + +### 3.1 Vocabulary + +- **Coverage Class:** See definition in 3GPP TS 43.064 [10]. + +- **CS/PS coordination enhancements:** refers to an improved CS/PS domain registration coordination function when rerouting is performed in a MOCN or in a GWCN configuration for network sharing. The improved CS/PS domain registration coordination is achieved by extended signalling between the BSS and the CN nodes (see 3GPP TS 23.251 [43]). +- **Dedicated Core Networks:** Dedicated Core Networks is an optional feature that enables an operator to deploy multiple dedicated core networks within a PLMN where each dedicated core network node may be dedicated to serve specific type (s) of subscribers. The selection of the Dedicated Core Network is based on “UE Usage Type” obtained from the HSS/HLR and operator specific configuration in the SGSN (see 3GPP TS 23.401 [49]). +- **EC operation:** See definition in 3GPP TS 43.064 [10]. +- **Extended DRX (eDRX):** see 3GPP TS 21.905 [1]. +- **MS assisted Dedicated Core Network selection:** MS assisted Dedicated Core Network selection is an optional feature wherein the selection of the Dedicated Core Network to which a BSS routes LLC PDUs, in addition to the selected PLMN, is based on the “DCN-ID” value provided by the MS (see 3GPP TS 23.401 [49]). +- **Network sharing:** network sharing is an optional feature that allows different core network operators to connect to the same shared radio access network in a MOCN configuration, and to the same shared radio access network and core network nodes in a GWCN configuration (see 3GPP TS 23.251 [43]). When network sharing is in use within a given cell, the network broadcasts within system information the PLMN identities of the PLMNs sharing the cell. A mobile station supporting network sharing uses this information for its PLMN (re)selection processes and indicates the selected PLMN to the BSS. +- **Null-NRI:** Has the same format as the NRI and is used to identify the group of SGSNs that belong to a DCN within a PLMN. A 'null-NRI' indicates to a radio node (BSC/RNC) that the NAS Node Selection Function shall be used for selecting a CN node to receive a message (see 3GPP TS 23.236 [21]). +- **SGSN Group ID:** A SGSN Group ID identifies a Dedicated Core Network (DCN) within the PLMN, i.e. the group of SGSNs that belong to a DCN within a PLMN, see 3GPP TS 23.401[49]. + +--- + +## 4 Logical configuration of the Gb-interface + +### 4.1 High-level characteristics of the Gb-interface + +In contrast to the A-interface, where a single user has the sole use of a dedicated physical resource throughout the lifetime of a call irrespective of information flow, the Gb-interface allows many users to be multiplexed over a common physical resource. + +GPRS signalling and user data may be sent on the same physical resources. + +Access rates per user may vary from zero data to the maximum possible bandwidth (e.g. the available bit rate of an E1). + +### 4.2 Position of BSSGP within the protocol stack on the Gb-interface + +Across the Gb-interface the following peer protocols have been identified: the Base Station Subsystem GPRS Protocol (BSSGP) and the underlying network service (NS). The NS shall transport BSSGP PDUs between a BSS and an SGSN (refer to 3GPP TS 48.016). + +![Figure 4.1: BSSGP's position within the Gb-interface protocol stack. The diagram shows three protocol stacks: BSS, Gb, and SGSN. The BSS stack has layers RELAY (containing RLC and BSSGP), MAC, NS, and L1. The Gb stack has layers NS and L1. The SGSN stack has layers LLC, BSSGP, NS, and L1. The BSSGP layer in the BSS is connected to the BSSGP layer in the SGSN via the Gb interface.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 4.1: BSSGP's position within the Gb-interface protocol stack. The diagram shows three protocol stacks: BSS, Gb, and SGSN. The BSS stack has layers RELAY (containing RLC and BSSGP), MAC, NS, and L1. The Gb stack has layers NS and L1. The SGSN stack has layers LLC, BSSGP, NS, and L1. The BSSGP layer in the BSS is connected to the BSSGP layer in the SGSN via the Gb interface. + +**Figure 4.1: BSSGP's position within the Gb-interface protocol stack** + +NOTE: The Relay function provides buffering and parameter mapping between the RLC/MAC and the BSSGP. + +EXAMPLE: On the uplink the RLC/MAC shall provide a TLLI. The Relay function shall then make it available to BSSGP. For a definition of the RLC/MAC function refer to 3GPP TS 43.064. + +The primary functions of the BSSGP include: + +- in the downlink, the provision by an SGSN to a BSS of radio related information used by the RLC/MAC function; +- in the uplink, the provision by a BSS to an SGSN of radio related information derived from the RLC/MAC function; and +- the provision of functionality to enable two physically distinct nodes, an SGSN and a BSS, to operate node management control functions. + +The present document describes the service model, service primitives, procedures and PDU formats of the BSSGP. + +## 5 Elements for layer-to-layer communication + +### 5.1 Definition of service model + +In the present document, the communication between adjacent layers and the services provided by the layers are distributed by use of abstract service primitives. Only externally observable behaviour resulting from the description is normatively prescribed by the present document. + +The service primitive model used in the present document is based on the concepts developed in ITU-T Recommendation X.200. + +The service model for a BSS and an SGSN is asymmetric. The service models for a BSS and an SGSN are shown in figure 5.1. + +![Figure 5.1: BSSGP service model. The diagram shows two service models: 'Service model in an BSS' and 'Service model in an SGSN'. Both models show a central 'BSSGP' block connected to various service primitives. In the BSS model, primitives include RELAY, RL, LCS, RIM, MBMS, PFM, GMM, and NM. In the SGSN model, primitives include LLC, BSSGP, LCS, RIM, MBMS, PFM, GMM, and NM. Both models show connections to 'RLC/MAC' or 'Network Service' blocks via '3GPP TS 44.064' or '3GPP TS 48.016' interfaces.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the BSSGP service model in two contexts: an BSS (Base Station System) and an SGSN (Serving GPRS Support Node). + +**Service model in an BSS:** + +- A 'RELAY' block is connected to 'RLC/MAC' via '3GPP TS 44.064'. +- 'RLC/MAC' is connected to 'BSSGP' via 'RL' (relay). +- 'BSSGP' is connected to 'Network Service' via '3GPP TS 48.016'. +- Additional service primitives are shown between 'BSSGP' and 'Network Service': 'LCS', 'RIM', 'MBMS', 'PFM', 'GMM', and 'NM'. + +**Service model in an SGSN:** + +- 'LLC' is connected to 'BSSGP' via 'BSSGP' (BSSGP). +- 'BSSGP' is connected to 'Network Service' via '3GPP TS 48.016'. +- Additional service primitives are shown between 'BSSGP' and 'Network Service': 'LCS', 'RIM', 'MBMS', 'PFM', 'GMM', and 'NM'. + +Figure 5.1: BSSGP service model. The diagram shows two service models: 'Service model in an BSS' and 'Service model in an SGSN'. Both models show a central 'BSSGP' block connected to various service primitives. In the BSS model, primitives include RELAY, RL, LCS, RIM, MBMS, PFM, GMM, and NM. In the SGSN model, primitives include LLC, BSSGP, LCS, RIM, MBMS, PFM, GMM, and NM. Both models show connections to 'RLC/MAC' or 'Network Service' blocks via '3GPP TS 44.064' or '3GPP TS 48.016' interfaces. + +**Figure 5.1: BSSGP service model** + +Primitives consist of commands and their respective responses associated with the services requested of another layer. The general syntax of a primitive is: + +- XX - Generic name - Type (Parameters); + +where XX designates the layer providing or using the service. + +In the present document, XX is: + +- "BSSGP" for functions controlling the transfer of LLC frames passed between an SGSN and an MS across the Gb interface; +- "RL" (relay) for functions controlling the transfer of LLC frames between the RLC/MAC function and BSSGP; +- "GMM" (GPRS mobility management) for functions associated with mobility management between an SGSN and a BSS; and +- "NM" (network management) for functions associated with Gb-interface and BSS-SGSN node management; +- "PFM" (packet flow management) for functions associated with the management of BSS Packet Flow Contexts (PFCs); +- "LCS" (location services) for functions associated with location services (LCS) procedures; +- "RIM" (RAN Information Management) for functions associated with generic procedures to communicate between two BSSs over the core network. +- "MBMS" (Multimedia Broadcast Multicast Service) for functions associated with Multimedia Broadcast Multicast Service (MBMS) procedures. + +## 5.2 Service primitives provided by the BSSGP at a BSS + +**Table 5.2: Service primitives provided by BSSGP at a BSS** + +| Generic name | Type | | | | Parameters | +|-----------------------------|---------|------------|----------|---------|------------------------------------------------------------------------------------------------------| +| | REQuest | INDication | RESponse | CoNFirm | | +| RL ó BSSGP | | | | | | +| RL-DL-UNITDATA | - | X | - | - | BVCI, NSEI,
Refer to DL-UNITDATA PDU | +| RL-UL-UNITDATA | X | - | - | - | BVCI, NSEI,
LSP,
Refer to UL- UNITDATA PDU | +| RL-DL-MBMS-UNITDATA | - | X | - | - | BVCI, NSEI,
Refer to DL-MBMS-UNITDATA PDU | +| RL-UL-MBMS-UNITDATA | X | - | - | - | BVCI, NSEI,
LSP,
Refer to UL-MBMS-UNITDATA PDU | +| GMM ó BSSGP | | | | | | +| GMM-PAGING | - | X | - | - | BVCI, NSEI,
Refer to PAGING PS PDU
Refer to PDU PAGING CS PDU | +| GMM-RA-CAPABILITY | - | X | - | - | BVCI, NSEI,
Refer to RA-CAPABILITY PDU | +| GMM-RA-CAPABILITY-UPDATE | X | - | - | X | BVCI, NSEI,
Refer to RA-CAPABILITY-UPDATE PDU,
Refer to RA-CAPABILITY-UPDATE-ACK PDU | +| GMM-RADIO-STATUS | X | - | - | - | BVCI, NSEI,
Refer to RADIO-STATUS PDU | +| GMM-SUSPEND | X | - | - | X | BVCI, NSEI,
Refer to SUSPEND PDU
Refer to SUSPEND-(N)ACK PDU | +| GMM-RESUME | X | - | - | X | BVCI, NSEI,
Refer to RESUME PDU
Refer to RESUME-(N)ACK PDU | +| GMM-MS-REGISTRATION-ENQUIRY | X | - | X | - | BVCI, NSEI,
Refer to MS-REGISTRATION-ENQUIRY PDU
Refer to MS-REGISTRATION-ENQUIRY-RESPONSE PDU | +| NM ó BSSGP | | | | | | +| NM-FLUSH-LL | - | X | X | - | BVCI, NSEI,
Refer to FLUSH-LL PDU
Refer to FLUSH-LL-ACK PDU | +| NM-LLC-DISCARDED | X | - | - | - | BVCI, NSEI,
Refer to LLC-DISCARDED PDU | +| NM-FLOW-CONTROL-BVC | X | - | - | X | BVCI, NSEI,
Refer to FLOW-CONTROL-BVC PDU
Refer to FLOW-CONTROL-BVC ACK PDU | + +| Generic name | Type | | | | Parameters | +|--------------------------|---------|------------|----------|---------|------------------------------------------------------------------------------------------------------------------| +| | REquest | INDication | RESponse | CoNFirm | | +| NM-FLOW-CONTROL-MS | X | - | - | X | BVCI, NSEI,
Refer to FLOW-CONTROL-MS PDU
Refer to FLOW-CONTROL-MS ACK PDU | +| NM-FLOW-CONTROL-PFC | X | - | - | X | BVCI, NSEI,
Refer to FLOW-CONTROL-PFC PDU
Refer to FLOW-CONTROL-PFC ACK PDU | +| NM-STATUS | X | X | - | - | BVCI, NSEI,
Refer to STATUS PDU | +| NM-BVC-BLOCK | X | - | - | X | BVCI, NSEI,
Refer to BVC-BLOCK PDU
Refer to BVC-BLOCK-ACK PDU | +| NM-BVC-UNBLOCK | X | - | - | X | BVCI, NSEI,
Refer to BVC-UNBLOCK PDU
Refer to BVC-UNBLOCK-ACK PDU | +| NM-BVC-RESET | X | X | X | X | BVCI, NSEI,
Refer to BVC-RESET PDU
Refer to BVC-RESET-ACK PDU | +| NM-TRACE | - | X | - | - | BVCI, NSEI,
Refer to SGSN-INVOKE-TRACE PDU | +| NW-OVERLOAD | - | X | - | - | BVCI, NSEI,
Refer to OVERLOAD PDU | +| PFM ó BSSGP | | | | | | +| PFM-DOWNLOAD-BSS-PFC | X | - | - | - | BVCI, NSEI
Refer to DOWNLOAD-BSS-PFC PDU | +| PFM-CREATE-BSS-PFC | - | X | X | - | BVCI, NSEI
Refer to CREATE-BSS-PFC PDU
Refer to CREATE-BSS-PFC-ACK PDU
Refer to CREATE-BSS-PFC-NACK PDU | +| PFM-MODIFY-BSS-PFC | X | - | - | X | BVCI, NSEI
Refer to MODIFY-BSS-PFC PDU
Refer to MODIFY-BSS-PFC-ACK PDU | +| PFM-DELETE-BSS-PFC | X | X | X | - | BVCI, NSEI
Refer to DELETE-BSS-PFC PDU
Refer to DELETE-BSS-PFC-ACK PDU
Refer to DELETE-BSS-PFC-REQ PDU | +| PFM-PS-HANDOVER-REQUIRED | X | - | - | X | BVCI, NSEI,
Refer to PS-HANDOVER-REQUIRED PDU
Refer to PS-HANDOVER-REQUIRED-(N)ACK PDU | +| PFM-PS-HANDOVER-REQUEST | - | X | X | - | BVCI, NSEI,
Refer to PS-HANDOVER-REQUEST PDU
Refer to PS-HANDOVER-REQUEST-(N)ACK PDU | + +| Generic name | Type | | | | Parameters | +|--------------------------|---------|------------|----------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| | REquest | INDication | RESponse | CoNFirm | | +| PFM-PS-HANDOVER-COMPLETE | X | - | - | - | BVCI, NSEI,
Refer to PS-HANDOVER-COMPLETE PDU | +| PFM-PS-HANDOVER-CANCEL | X | - | - | - | BVCI, NSEI,
Refer to PS-HANDOVER-CANCEL PDU | +| LCS ó BSSGP | | | | | | +| LCS-LOCATE | - | X | X | - | BVCI, NSEI
Refer to PERFORM-LOCATION-REQUEST PDU
Refer to PERFORM-LOCATION-RESPONSE PDU | +| LCS-ABORT | - | X | - | - | BVCI, NSEI
Refer to PERFORM-LOCATION-ABORT PDU | +| LCS-INFORMATION-TRANSFER | X | - | - | X | BVCI, NSEI
Refer to POSITION-COMMAND PDU
Refer to POSITION-RESPONSE PDU | +| RIM ó BSSGP | | | | | | +| RIM-PDU-TRANSFER | X | X | - | - | BVCI, NSEI
Refer to RAN-INFORMATION-REQUEST, RAN-INFORMATION, RAN-INFORMATION-ACK, RAN-INFORMATION-APPLICATION-ERROR, RAN-INFORMATION-ERROR PDUs; | +| MBMS ó BSSGP | | | | | | +| MBMS-SESSION-START | - | X | X | - | BVCI, NSEI
Refer to MBMS-SESSION-START-REQUEST PDU;
Refer to MBMS-SESSION-START-RESPONSE PDU | +| MBMS-SESSION-STOP | - | X | X | - | BVCI, NSEI
Refer to MBMS-SESSION-STOP-REQUEST PDU;
Refer to MBMS-SESSION-STOP- RESPONSE PDU | +| MBMS-SESSION-UPDATE | - | X | X | - | BVCI, NSEI
Refer to MBMS-SESSION-UPDATE-REQUEST PDU;
Refer to MBMS-SESSION-UPDATE-RESPONSE PDU | + +## 5.2.1 RL-DL-UNITDATA.ind + +Receipt of a DL-UNITDATA PDU from an SGSN by a BSS containing an LLC-PDU and MS control information necessary for the transmission of the LLC-PDU across the radio interface. + +## 5.2.2 RL-UL-UNITDATA.req + +Request to send a UL-UNITDATA PDU to an SGSN from a BSS containing an LLC-PDU and radio interface derived information. + +## 5.2.3 (void) + +### 5.2.3a RL-DL-MBMS-UNITDATA.ind + +Receipt of a DL-MBMS-UNITDATA PDU from an SGSN by a BSS containing an LLC-PDU for the transmission of the LLC-PDU across the radio interface. + +### 5.2.3b RL-UL-MBMS-UNITDATA.req + +Request to send a UL-MBMS-UNITDATA PDU to an SGSN from a BSS containing an LLC-PDU. + +### 5.2.4 GMM-PAGING.ind + +Receipt of a PAGING-PS or PAGING-CS PDU from an SGSN by a BSS containing instructions to page an MS within a given group of cells. + +### 5.2.5 GMM-RA-CAPABILITY.ind + +Receipt of a RA-CAPABILITY PDU from an SGSN by a BSS providing the new Radio Access capability of an MS. + +### 5.2.6 GMM-RA-CAPABILITY-UPDATE.req + +Request to send a RA-CAPABILITY-UPDATE PDU to an SGSN from a BSS in order to receive the current Radio Access capabilities of an MS. + +### 5.2.7 GMM-RA-CAPABILITY-UPDATE.cnf + +Receipt of a RA-CAPABILITY-UPDATE-ACK PDU from a SGSN by a BSS containing the current Radio Access capabilities of an MS. + +### 5.2.8 GMM-RADIO-STATUS.req + +Request to send a RADIO-STATUS PDU to an SGSN from a BSS to report that an exception condition occurred in the operation of the radio interface for an MS. + +### 5.2.9 GMM-SUSPEND.req + +Request to send a SUSPEND PDU to an SGSN from a BSS to mark an MS's GPRS service as suspended. + +### 5.2.10 GMM-SUSPEND.cnf + +Receipt of a SUSPEND-ACK PDU from an SGSN by a BSS confirming that an SGSN has marked an MS's GPRS service as suspended. + +### 5.2.11 GMM-RESUME.req + +Request to send a RESUME PDU to an SGSN from a BSS to mark an MS's GPRS service as resumed. + +### 5.2.12 GMM-RESUME.cnf + +Receipt of a RESUME-ACK PDU from an SGSN by a BSS confirming that an SGSN has marked an MS's GPRS service as resumed. + +### 5.2.12a GMM-MS-REGISTRATION-ENQUIRY.req + +Request to send a MS-REGISTRATION-ENQUIRY PDU to an SGSN from a BSS enquiring registration information for a given MS. + +### 5.2.12b GMM-MS-REGISTRATION-ENQUIRY.res + +Receipt of a MS-REGISTRATION-ENQUIRY-RESPONSE PDU from an SGSN by a BSS, containing registration information for a given MS. + +### 5.2.13 NM-FLUSH-LL.ind + +On receipt of a FLUSH-LL PDU by a BSS from an SGSN, the BSS will either delete queued LLC-PDUs for a TLLI or move the queued LLC-PDUs from an old to a new BVC. If there is a BSS context for the Mobile Station identified by the TLLI and the BSS is able to move the queued LLC-PDUs, the BSS has to move the BSS context from the old to the new BVC, even if it is not able to offer the same QoS characteristics in the new BVC. + +### 5.2.14 NM-FLUSH-LL.res + +Sending of a FLUSH-LL-ACK PDU to the SGSN from a BSS to report if queued LLC-PDU(s) for an MS were deleted or transferred from the old to the new cell within the routing area. The FLUSH-LL-ACK PDU may also report whether the QoS characteristics of the BSS context associated to the MS could be kept in the new cell. + +### 5.2.15 NM-LLC-DISCARDED.req + +Request to send a LLC-DISCARDED PDU to an SGSN from a BSS indicating that LLC frames pertaining to an MS have been locally discarded. + +### 5.2.16 NM-FLOW-CONTROL-BVC.req + +Request to send a FLOW-CONTROL-BVC PDU to an SGSN from a BSS indicating the ability of a BVC to accept a certain flow of data. + +### 5.2.17 NM-FLOW-CONTROL-BVC.cnf + +Confirmation that a FLOW-CONTROL-BVC PDU has been received by an SGSN for a given BVC. + +### 5.2.18 NM-FLOW-CONTROL-MS.req + +Request to send a FLOW-CONTROL-MS PDU to an SGSN from a BSS indicating the ability to accept a certain flow of data for a given MS. + +### 5.2.19 NM-FLOW-CONTROL-MS.cnf + +Confirmation that a FLOW-CONTROL-MS PDU has been received by an SGSN for a given MS. + +### 5.2.19a NM-FLOW-CONTROL-PFC.req + +Request to send a FLOW-CONTROL-PFC PDU to an SGSN from a BSS indicating the ability to accept a certain flow of data for a given PFC of a given MS. + +### 5.2.19b NM-FLOW-CONTROL-PFC.cnf + +Confirmation that a FLOW-CONTROL-PFC PDU has been received by an SGSN for a given PFC of a given MS. + +### 5.2.20 NM-STATUS.req + +Request to send a STATUS PDU to an SGSN from a BSS to report that an exception condition occurred within the BSS. + +### 5.2.21 NM-STATUS.ind + +Receipt of a STATUS PDU from an SGSN by a BSS indicating that an exception condition occurred within an SGSN. + +### 5.2.22 NM-BVC-BLOCK.req + +Request to send a BVC-BLOCK PDU to an SGSN from a BSS to mark a BVC as blocked. + +### 5.2.23 NM-BVC-BLOCK.cnf + +Receipt of a BVC-BLOCK-ACK PDU from an SGSN by a BSS confirming that an SGSN has marked a BVC as blocked. + +### 5.2.24 NM-BVC-UNBLOCK.req + +Request to send a BVC-UNBLOCK PDU to an SGSN from a BSS to mark a BVC as unblocked. + +## 5.2.25 NM-BVC-UNBLOCK.cnf + +Receipt of a BVC-UNBLOCK-ACK PDU from an SGSN by a BSS confirming that an SGSN has marked a BVC as unblocked. + +## 5.2.26 NM-BVC-RESET.req + +Request to send a BVC-RESET PDU to an SGSN from a BSS to reset an SGSN's GPRS BVC contexts. + +## 5.2.27 NM-BVC-RESET.res + +Sending of a BVC-RESET-ACK PDU to the SGSN from an BSS indicating that a GPRS BVC context has been reset in the BSS. + +## 5.2.28 NM-BVC-RESET.ind + +Receipt of a BVC-RESET PDU at a BSS from an SGSN indicating that GPRS BVC contexts have been reset at the SGSN. + +## 5.2.29 NM-BVC-RESET.cnf + +Receipt of a BVC-RESET-ACK PDU at a BSS confirming that GPRS BVC context has been reset at the SGSN. + +## 5.2.30 NM-TRACE.ind + +Receipt of a SGSN-INVOKE-TRACE PDU at a BSS from an SGSN indicating the need to produce a trace record on an MS. + +## 5.2.30a NW-OVERLOAD.ind + +Receipt of an OVERLOAD PDU from an SGSN by a BSS informing the BSS the SGSN is in an overload state. + +## 5.2.31 PFM-DOWNLOAD-BSS-PFC.req + +Upon a request to transfer an uplink or downlink LLC PDU for which it currently does not have a BSS Packet Flow Context, the BSS may send a DOWNLOAD-BSS-PFC PDU to an SGSN. + +## 5.2.32 PFM-CREATE-BSS-PFC.ind + +Receipt of a CREATE-BSS-PFC PDU at a BSS from an SGSN indicating that the BSS should create or modify a BSS Packet Flow Context using the Aggregate BSS QoS Profile. + +## 5.2.33 PFM-CREATE-BSS-PFC.res + +Sending of a CREATE-BSS-PFC-ACK PDU to the SGSN from a BSS to respond with an Aggregate BSS QoS Profile, indicating queuing or successful creation of the PFC, or a CREATE-BSS-PFC-NACK in case the BSS was unable to create the PFC. + +## 5.2.34 PFM-MODIFY-BSS-PFC.req + +Request to send a MODIFY-BSS-PFC PDU to an SGSN from a BSS to modify an Aggregate BSS QoS Profile. + +## 5.2.35 (void) + +## 5.2.36 (void) + +## 5.2.37 PFM-MODIFY-BSS-PFC.cnf + +Reception of a MODIFY-BSS-PFC-ACK PDU at a BSS from an SGSN confirming the modification of an Aggregate BSS QoS Profile. + +## 5.2.38 PFM-DELETE-BSS-PFC.ind + +Receipt of a DELETE-BSS-PFC PDU at a BSS from an SGSN to delete an Aggregate BSS QoS Profile. + +## 5.2.39 PFM-DELETE-BSS-PFC.res + +Sending of a DELETE-BSS-PFC-ACK PDU to an SGSN from a BSS to respond to a deletion. + +## 5.2.39a PFM-DELETE-BSS-PFC.req + +Sending of a DELETE-BSS-PFC-REQ PDU to an SGSN from a BSS to request to a deletion of an Aggregate BSS QoS Profile. + +## 5.2.39b PFM-PS-HANDOVER-REQUIRED.req + +Request to send a PS-HANDOVER-REQUIRED PDU to the SGSN from the source BSS to initiate the allocation of resources in the target system at PS handover. + +## 5.2.39c PFM-PS-HANDOVER-REQUIRED.cnf + +Receipt of a PS-HANDOVER-REQUIRED-ACK PDU from the SGSN by the source BSS reporting successful allocation of resources in the target system at PS handover. + +## 5.2.39d PFM-PS-HANDOVER-REQUEST.ind + +Receipt of a PS-HANDOVER-REQUEST PDU from the SGSN by the target BSS to initiate the allocation of resources for one or more PFCs during PS handover. + +## 5.2.39e PFM-PS-HANDOVER-REQUEST.res + +Request to send a PS-HANDOVER-REQUEST-ACK PDU to the SGSN from the target BSS to report the successful allocation of resources during PS handover. + +## 5.2.39f PFM-PS-HANDOVER-COMPLETE.req + +Request to send a PS-HANDOVER-COMPLETE PDU to the SGSN from the target BSS to report a successful channel change during PS handover. + +## 5.2.39g PFM-PS-HANDOVER-CANCEL.req + +Request to send a PS-HANDOVER-CANCEL PDU to the SGSN from the source BSS to cancel a previously initiated PS handover. + +## 5.2.40 LCS-LOCATE.ind + +Receipt of a PERFORM-LOCATION-REQUEST PDU at a BSS from an SGSN requesting a location procedure for a target MS. + +## 5.2.41 LCS-LOCATE.res + +Sending of a PERFORM-LOCATION-RESPONSE PDU to an SGSN responding to the location request for a target MS. + +## 5.2.42 LCS-ABORT.ind + +Receipt of a PERFORM-LOCATION-ABORT PDU at a BSS from an SGSN indicating a request of an abort of a location procedure for a target MS. + +## 5.2.43 LCS-INFORMATION-TRANSFER.req + +Request to send a POSITION-COMMAND PDU to an SGSN from a BSS that has LCS related information associated with a higher level protocol available to transfer. + +## 5.2.44 LCS-INFORMATION-TRANSFER.cnf + +Confirmation in a POSTION-RESPONSE PDU that the higher layer message has been received and an indication of the result of the message transfer and possibly including a reply with another higher layer protocol message. + +## 5.2.45 RIM-PDU-TRANSFER.req + +Sending of a RAN-INFORMATION-REQUEST, RAN-INFORMATION, RAN-INFORMATION-ACK, RAN-INFORMATION-APPLICATION-ERROR, RAN-INFORMATION-ERROR PDU to an SGSN from a BSS for routing of the PDU to another BSS. + +## 5.2.46 RIM-PDU-TRANSFER.ind + +Reception of a RAN-INFORMATION-REQUEST, RAN-INFORMATION, RAN-INFORMATION-ACK, RAN-INFORMATION-APPLICATION-ERROR, RAN-INFORMATION-ERROR PDU at a BSS from an SGSN originating from another BSS. + +## 5.2.47 (void) + +## 5.2.48 (void) + +## 5.2.49 (void) + +## 5.2.50 (void) + +## 5.2.51 (void) + +## 5.2.52 (void) + +## 5.2.53 MBMS-SESSION-START-REQUEST.ind + +Reception of an MBMS-SESSION-START-REQUEST PDU at a BSS from an SGSN requesting to start an MBMS session. + +## 5.2.54 MBMS-SESSION-START-RESPONSE.res + +Sending of an MBMS-SESSION-START-RESPONSE PDU to an SGSN from a BSS acknowledging to start an MBMS session. + +## 5.2.55 MBMS-SESSION-STOP-REQUEST.ind + +Reception of an MBMS-SESSION-STOP-REQUEST PDU at a BSS from an SGSN requesting to stop an MBMS session. + +## 5.2.56 MBMS-SESSION-STOP-RESPONSE.res + +Sending of an MBMS-SESSION-STOP-RESPONSE PDU to an SGSN from a BSS acknowledging to stop an MBMS session. + +## 5.2.57 MBMS-SESSION-UPDATE-REQUEST.ind + +Reception of an MBMS-SESSION-UPDATE-REQUEST PDU at a BSS from an SGSN requesting to update the MBMS service area list of an ongoing MBMS broadcast service session. + +## 5.2.58 MBMS-SESSION-UPDATE-RESPONSE.res + +Sending of an MBMS-SESSION-UPDATE-RESPONSE PDU to an SGSN from a BSS acknowledging to update the MBMS service area list of an ongoing MBMS broadcast service session. + +# 5.3 Service primitives provided by the BSSGP at an SGSN + +**Table 5.3: Service primitives provided by BSSGP at an SGSN** + +| Generic name | Type | | | | Parameters | +|-----------------------------|---------|------------|----------|---------|------------------------------------------------------------------------------------------------------------| +| | REquest | INDication | RESponse | CoNFirm | | +| LL ó BSSGP | | | | | | +| BSSGP-DL-UNITDATA | X | - | - | - | BVCI, NSEI, LSP,
Refer to DL-UNITDATA
PDU | +| BSSGP-UL-UNITDATA | - | X | - | - | BVCI, NSEI,
Refer to UL-UNITDATA
PDU | +| BSSGP-DL-MBMS-UNITDATA | X | - | - | - | BVCI, NSEI,
Refer to DL-MBMS-UNITDATA
PDU | +| BSSGP-UL-MBMS-UNITDATA | - | X | - | - | BVCI, NSEI,
Refer to UL-MBMS-UNITDATA
PDU | +| GMM ó BSSGP | | | | | | +| GMM-PAGING | X | - | - | - | BVCI, NSEI,
Refer to PAGING PS PDU
Refer to PAGING CS PDU | +| GMM-RA-CAPABILITY | X | - | - | - | BVCI, NSEI,
Refer to RA-CAPABILITY
PDU | +| GMM-RA-CAPABILITY-UPDATE | - | X | X | - | BVCI, NSEI,
Refer to RA-CAPABILITY-UPDATE
PDU,
Refer to RA-CAPABILITY-UPDATE-ACK
PDU | +| GMM-RADIO-STATUS | - | X | - | - | BVCI, NSEI,
Refer to RADIO-STATUS
PDU | +| GMM-SUSPEND | - | X | - | - | BVCI, NSEI,
Refer to SUSPEND PDU
Refer to SUSPEND-(N)ACK
PDU | +| GMM-RESUME | - | X | - | - | BVCI, NSEI,
Refer to RESUME PDU
Refer to RESUME-(N)ACK
PDU | +| GMM-MS-REGISTRATION-ENQUIRY | - | X | X | - | BVCI, NSEI,
Refer to MS-REGISTRATION-ENQUIRY
PDU
Refer to MS-REGISTRATION-ENQUIRY-RESPONSE
PDU | +| NM ó BSSGP | | | | | | +| NM-FLUSH-LL | X | - | - | X | BVCI, NSEI,
Refer to FLUSH-LL PDU
Refer to FLUSH-LL-ACK
PDU | +| NM-LLC-DISCARDED | - | X | - | - | BVCI, NSEI,
Refer to LLC-DISCARDED
PDU | +| NM-FLOW-CONTROL-BVC | - | X | - | - | BVCI, NSEI,
Refer to FLOW-CONTROL-BVC
PDU
Refer to FLOW-CONTROL-BVC
ACK PDU | +| NM-FLOW-CONTROL-MS | - | X | - | - | BVCI, NSEI,
Refer to FLOW-CONTROL-MS
PDU
Refer to FLOW-CONTROL-MS
ACK PDU | +| NM-FLOW-CONTROL-PFC | - | X | - | - | BVCI, NSEI,
Refer to FLOW-CONTROL-PFC
PDU
Refer to FLOW-CONTROL-PFC
ACK PDU | + +| Generic name | Type | | | | Parameters | +|--------------------------|---------|------------|----------|---------|------------------------------------------------------------------------------------------------------------------| +| | REquest | INDication | RESponse | CoNFirm | | +| NM-STATUS | X | X | - | - | BVCI, NSEI,
Refer to STATUS PDU | +| NM-BVC-BLOCK | - | X | - | - | BVCI, NSEI,
Refer to BVC-BLOCK PDU
Refer to BVC-BLOCK-ACK PDU | +| NM-BVC-UNBLOCK | - | X | - | - | BVCI, NSEI,
Refer to BVC-UNBLOCK PDU
Refer to BVC-UNBLOCK-ACK PDU | +| NM-BVC-RESET | X | X | X | X | BVCI, NSEI,
Refer to BVC-RESET PDU
Refer to BVC-RESET-ACK PDU | +| NM-TRACE | X | - | - | - | BVCI, NSEI,
Refer to SGSN-INVOKE-TRACE PDU | +| NW-OVERLOAD | X | - | - | - | BVCI, NSEI,
Refer to OVERLOAD PDU | +| PFM ó BSSGP | | | | | | +| PFM-DOWNLOAD-BSS-PFC | - | X | - | - | BVCI, NSEI
Refer to DOWNLOAD-BSS-PFC PDU | +| PFM-CREATE-BSS-PFC | X | - | - | X | BVCI, NSEI
Refer to CREATE-BSS-PFC PDU
Refer to CREATE-BSS-PFC-ACK PDU
Refer to CREATE-BSS-PFC-NACK PDU | +| PFM-MODIFY-BSS-PFC | - | X | X | - | BVCI, NSEI
Refer to MODIFY-BSS-PFC PDU
Refer to MODIFY-BSS-PFC-ACK PDU | +| PFM-DELETE-BSS-PFC | X | X | - | X | BVCI, NSEI
Refer to DELETE-BSS-PFC PDU
Refer to DELETE-BSS-PFC-ACK PDU
Refer to DELETE-BSS-PFC-REQ PDU | +| PFM-PS-HANDOVER-REQUIRED | - | X | X | - | BVCI, NSEI,
Refer to PS-HANDOVER-REQUIRED PDU
Refer to PS-HANDOVER-REQUIRED-(N)ACK PDU | +| PFM-PS-HANDOVER-REQUEST | X | - | - | X | BVCI, NSEI,
Refer to PS-HANDOVER-REQUEST PDU
Refer to PS-HANDOVER-REQUEST-(N)ACK PDU | +| PFM-PS-HANDOVER-COMPLETE | - | X | - | - | BVCI, NSEI,
Refer to PS-HANDOVER-COMPLETE PDU | +| PFM-PS-HANDOVER-CANCEL | - | X | - | - | BVCI, NSEI,
Refer to PS-HANDOVER-CANCEL PDU | +| LCS ó BSSGP | | | | | | + +| Generic name | Type | | | | Parameters | +|--------------------------|---------|------------|----------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| | REquest | INDication | RESponse | CoNFirm | | +| LCS-LOCATE | X | - | - | X | BVCI, NSEI
Refer to PERFORM-LOCATION-REQUEST PDU
Refer to PERFORM-LOCATION-RESPONSE PDU | +| LCS-ABORT | X | - | - | - | BVCI, NSEI
Refer to PERFORM-LOCATION-ABORT PDU | +| LCS-INFORMATION-TRANSFER | - | X | X | - | BVCI, NSEI
Refer to POSITION-COMMAND PDU
Refer to POSITION-RESPONSE PDU | +| RIM ó BSSGP | | | | | | +| RIM-PDU-TRANSFER | X | X | - | - | BVCI, NSEI
Refer to RAN-INFORMATION-REQUEST, RAN-INFORMATION, RAN-INFORMATION-ACK, RAN-INFORMATION-APPLICATION-ERROR, RAN-INFORMATION-ERROR PDUs; | +| MBMS ó BSSGP | | | | | | +| MBMS-SESSION-START | X | - | - | X | BVCI, NSEI
Refer to MBMS-SESSION-START-REQUEST PDU;
Refer to MBMS-SESSION-START-RESPONSE PDU | +| MBMS-SESSION-STOP | X | - | - | X | BVCI, NSEI
Refer to MBMS-SESSION-STOP-REQUEST PDU;
Refer to MBMS-SESSION-STOP-RESPONSE PDU | +| MBMS-SESSION-UPDATE | X | - | - | X | BVCI, NSEI
Refer to MBMS-SESSION-UPDATE-REQUEST PDU;
Refer to MBMS-SESSION-UPDATE-RESPONSE PDU | + +NOTE: The parameters in the BSSGP-DL-UNITDATA and BSSGP-UL-UNITDATA primitives that are not included in the corresponding primitives in 3GPP TS 44.064 are provided or extracted by some intermediate function out of the scope of the present document. + +### 5.3.1 BSSGP-DL-UNITDATA.req + +Request to send a DL-UNITDATA PDU to a BSS from an SGSN containing an LLC-PDU and control information necessary for the transmission of the LLC-PDU across the radio interface. + +### 5.3.2 BSSGP-UL-UNITDATA.ind + +Receipt of a UL-UNITDATA PDU from a BSS by an SGSN containing an LLC-PDU and radio interface derived information. + +### 5.3.3 (void) + +### 5.3.3a BSSGP-DL-MBMS-UNITDATA.req + +Request to send a DL-MBMS-UNITDATA PDU to a BSS from an SGSN containing an LLC-PDU for the transmission of the LLC-PDU across the radio interface. + +### 5.3.3b BSSGP-UL-MBMS-UNITDATA.ind + +Receipt of a UL-MBMS-UNITDATA PDU from a BSS by an SGSN containing an LLC-PDU. + +### 5.3.4 GMM-PAGING.req + +Request to send a PAGING-PS or PAGING-CS PDU from an SGSN to a BSS containing instructions to page an MS within a given group of cells. + +### 5.3.5 GMM-RA-CAPABILITY.req + +Request to send a RA-CAPABILITY PDU to the BSS from an SGSN containing the Radio Access capability of an MS. + +### 5.3.6 GMM-RA-CAPABILITY-UPDATE.ind + +Receipt of a RA-CAPABILITY-UPDATE PDU from a BSS by an SGSN, requesting that the SGSN sends the Radio Access capability of an MS to the BSS. + +### 5.3.7 GMM-RA-CAPABILITY-UPDATE.res + +Sending of a RA-CAPABILITY-UPDATE-ACK PDU to the BSS from an SGSN containing the current Radio Access capability of an MS. + +### 5.3.8 GMM-RADIO-STATUS.ind + +Receipt of a RADIO-STATUS PDU from a BSS by an SGSN to report that an exception condition occurred in the operation of the radio interface for an MS. + +### 5.3.9 GMM-SUSPEND.ind + +Receipt of a SUSPEND PDU from a BSS by an SGSN indicating that an MS wishes to suspended its GPRS service. + +### 5.3.10 GMM-RESUME.ind + +Receipt of a RESUME PDU from a BSS by an SGSN indicating that an MS wishes to resume its GPRS service. + +### 5.3.10a GMM-MS-REGISTRATION-ENQUIRY.ind + +Receipt of a MS-REGISTRATION-ENQUIRY PDU from a BSS by an SGSN enquiring registration information for a given MS. + +### 5.3.10b GMM-MS-REGISTRATION-ENQUIRY.res + +Request to send a MS-REGISTRATION-ENQUIRY-RESPONSE PDU to a BSS from an SGSN containing registration information for a given MS. + +### 5.3.11 NM-FLUSH-LL.req + +Request to send a FLUSH-LL PDU from an SGSN to a BSS, instructing the BSS to either delete queued LLC-PDUs for a TLLI or move the queued LLC-PDUs from an old to a new BVC. + +### 5.3.12 NM-FLUSH-LL.cnf + +Receipt of a FLUSH-LL-ACK PDU at an SGSN informing if the queued LLC-PDU(s) for an MS were deleted or transferred from the old to the new cell within the routing area. The FLUSH-LL-ACK PDU may also report whether the QoS characteristics of the BSS context associated to the MS could be kept in the new cell. + +### 5.3.13 NM-LLC-DISCARDED.ind + +Receipt of a LLC-DISCARDED PDU from a BSS by an SGSN indicating that LLC frames pertaining to an MS have been locally discarded. + +### 5.3.14 NM-FLOW-CONTROL-BVC.ind + +Receipt of a FLOW-CONTROL-BVC PDU from a BSS by an SGSN indicating the ability of a BVC to accept a certain flow of data. + +### 5.3.15 NM-FLOW-CONTROL-MS.ind + +Receipt of a FLOW-CONTROL-MS PDU from a BSS by an SGSN indicating the ability to accept a certain flow of data for a given MS. + +### 5.3.15a NM-FLOW-CONTROL-PFC.ind + +Receipt of a FLOW-CONTROL-PFC PDU from a BSS by an SGSN indicating the ability to accept a certain flow of data for a given PFC of a given MS. + +### 5.3.16 NM-STATUS.req + +Request to send a STATUS PDU to a BSS from an SGSN to report that an exception condition occurred within an SGSN. + +### 5.3.17 NM-STATUS.ind + +Receipt of a STATUS PDU from a BSS by an SGSN indicating an exception condition occurred within the BSS. + +### 5.3.18 NM-BVC-BLOCK.ind + +Receipt of a BVC-BLOCK PDU from a BSS by an SGSN indicating that a BVC shall be marked as blocked. + +### 5.3.19 NM-BVC-UNBLOCK.ind + +Receipt of a BVC-UNBLOCK PDU from a BSS by an SGSN indicating that a BVC shall be marked as unblocked. + +### 5.3.20 NM-BVC-RESET.req + +Request to send a BVC-RESET PDU to a BSS from an SGSN to reset a BSS's GPRS BVC contexts. + +### 5.3.21 NM-BVC-RESET.res + +Sending of a BVC-RESET-ACK PDU to the BSS from a SGSN indicating that a GPRS BVC context has been reset in the SGSN. + +### 5.3.22 NM-BVC-RESET.ind + +Receipt of a BVC-RESET PDU at an SGSN from a BSS indicating that GPRS BVC contexts have been reset at the BSS. + +### 5.3.23 NM-BVC-RESET.cnf + +Receipt of a BVC-RESET-ACK PDU at an SGSN confirming that GPRS BVC contexts have been reset at the BSS. + +### 5.3.24 NM-TRACE.req + +Request to send an SGSN-INVOKE-TRACE PDU to a BSS from an SGSN to begin producing a trace record on an MS. + +### 5.3.24a NM-OVERLOAD-START.req + +Request to send an OVERLOAD PDU to a BSS from an SGSN to inform the BSS an overload situation happened in the SGSN. + +### 5.3.25 PFM-DOWNLOAD-BSS-PFC.ind + +Receipt of a DOWNLOAD-BSS-PFC PDU at an SGSN from a BSS. + +### 5.3.26 PFM-CREATE-BSS-PFC.req + +Sending of a CREATE-BSS-PFC PDU to a BSS from an SGSN requesting that the BSS should create or modify a BSS Packet Flow Context using the Aggregate BSS QoS Profile. + +### 5.3.27 PFM-CREATE-BSS-PFC.cnf + +Receipt of a CREATE-BSS-PFC-ACK PDU at an SGSN from a BSS confirming the creation or modification or queuing of a BSS Packet Flow Context using the Aggregate BSS QoS Profile or a CREATE-BSS-PFC-NACK in to indicate the BSS was unable to create the PFC. + +### 5.3.28 PFM-MODIFY-BSS-PFC.ind + +Receipt of a MODIFY-BSS-PFC PDU at an SGSN from a BSS to modify an Aggregate BSS QoS Profile. + +### 5.3.29 PFM-MODIFY-BSS-PFC.res + +Sending of a MODIFY-BSS-PFC-ACK PDU to a BSS from an SGSN to respond with an Aggregate BSS QoS Profile. + +### 5.3.30 PFM-DELETE-BSS-PFC.req + +Sending of a DELETE-BSS-PFC PDU to a BSS from an SGSN to delete an Aggregate BSS QoS Profile. + +### 5.3.31 PFM-DELETE-BSS-PFC.cnf + +Receipt of a DELETE-BSS-PFC-ACK PDU at an SGSN from a BSS to confirm the deletion of an Aggregate BSS QoS Profile. + +### 5.3.31a PFM-DELETE-BSS-PFC.ind + +Receipt of a DELETE-BSS-PFC-REQ PDU at an SGSN from a BSS that a deletion of an Aggregate BSS QoS Profile is requested. + +### 5.3.31b PFM-PS-HANDOVER-REQUIRED.ind + +Receipt of a PS-HANDOVER-REQUIRED PDU from the source BSS by the SGSN indicating initiation of a PS handover. + +### 5.3.31c PFM-PS-HANDOVER-REQUIRED.res + +Request to send a PS-HANDOVER-REQUIRED-ACK PDU from the SGSN to the source BSS to initiate the channel change attempt during PS handover. + +### 5.3.31d PFM-PS-HANDOVER-REQUEST.req + +Request to send a PS-HANDOVER-REQUEST PDU from the SGSN to the target BSS to initiate the allocation of resources for one or more PFCs during PS handover. + +### 5.3.31e PFM-PS-HANDOVER-REQUEST.cnf + +Receipt of a PS-HANDOVER-REQUEST-ACK PDU from the target BSS by the SGSN reporting the successful allocation of resources during PS handover. + +### 5.3.31f PFM-PS-HANDOVER-COMPLETE.ind + +Receipt of a PS-HANDOVER-COMPLETE PDU from the target BSS by the SGSN reporting a successful channel change during PS handover. + +### 5.3.31g PFM-PS-HANDOVER-CANCEL.ind + +Receipt of a PS-HANDOVER-CANCEL PDU from the source BSS by the SGSN indicating cancellation of a previously initiated PS handover. + +### 5.3.32 LCS-LOCATE.req + +Sending of a PERFORM-LOCATION-REQUEST PDU at an SGSN requesting a location procedure for a target MS. + +### 5.3.33 LCS-LOCATE.cnf + +Receipt of a PERFORM-LOCATION-RESPONSE PDU confirming that the location request for a target MS has been attempted indicating the result of this attempt. + +### 5.3.34 LCS-ABORT.req + +Sending of a PERFORM-LOCATION-ABORT PDU from an SGSN to a BSS requesting an abort of a location procedure for a target MS. + +### 5.3.35 LCS-INFORMATION-TRANSFER.ind + +Receipt of a POSITION-COMMAND PDU at an SGSN from a BSS requesting a transfer of a higher level protocol message. + +### 5.3.36 LCS-INFORMATION-TRANSFER.res + +Sending of a POSITION-RESPONSE PDU from an SGSN to a BSS indicating the result of the message transfer and possibly including the transfer of a new higher layer protocol message. + +### 5.3.37 RIM-PDU-TRANSFER.req + +Sending of a RAN-INFORMATION-REQUEST, RAN-INFORMATION, RAN-INFORMATION-ACK, RAN-INFORMATION-APPLICATION-ERROR, RAN-INFORMATION-ERROR PDU to a BSS from an SGSN. + +### 5.3.38 RIM-PDU-TRANSFER.ind + +Reception of a RAN-INFORMATION-REQUEST, RAN-INFORMATION, RAN-INFORMATION-ACK, RAN-INFORMATION-APPLICATION-ERROR, RAN-INFORMATION-ERROR PDU at an SGSN from a BSS for routing of the PDU to another BSS. + +### 5.3.39 (void) + +### 5.3.40 (void) + +### 5.3.41 (void) + +### 5.3.42 (void) + +### 5.3.43 (void) + +### 5.3.44 (void) + +### 5.3.45 MBMS-SESSION-START-REQUEST.req + +Sending of an MBMS-SESSION-START-REQUEST PDU to a BSS from an SGSN requesting to start an MBMS session. + +### 5.3.46 MBMS-SESSION-START-RESPONSE.cnf + +Receipt of an MBMS-SESSION-START-RESPONSE PDU from a BSS acknowledging to start an MBMS session. + +### 5.3.47 MBMS-SESSION-STOP-REQUEST.req + +Sending of an MBMS-SESSION-STOP-REQUEST PDU to a BSS from an SGSN requesting to stop an MBMS session. + +### 5.3.48 MBMS-SESSION-STOP-RESPONSE.cnf + +Receipt of an MBMS-SESSION-STOP-RESPONSE PDU from a BSS acknowledging to stop an MBMS session. + +### 5.3.49 MBMS-SESSION-UPDATE-REQUEST.req + +Sending of an MBMS-SESSION-UPDATE-REQUEST PDU to a BSS from an SGSN requesting to update the MBMS service area list of an ongoing MBMS broadcast service session. + +### 5.3.50 MBMS-SESSION-UPDATE-RESPONSE.cnf + +Receipt of an MBMS-SESSION-UPDATE-RESPONSE PDU from a BSS acknowledging to update the MBMS service area list of an ongoing MBMS broadcast service session. + +## 5.4 Primitive parameters + +### 5.4.1 BSSGP Virtual Connection Identifier (BVCI) + +BSSGP Virtual Connections (BVCs) provide communication paths between BSSGP entities. Each BVC is used in the transport of BSSGP PDUs between peer point-to-point (PTP) functional entities, peer point-to-multipoint (PTM) functional entities and peer signalling functional entities. Table 5.4.1 lists the mapping of the BSSGP PDU to the associated functional entity and the BVCI. The BVCI is used to enable the lower network service layer to efficiently route the BSSGP PDU to the peer entity. This parameter is not part of the BSSGP PDU across the Gb interface, but is used by the network service entity across the Gb. + +Any BSSGP PDU received by the BSS or the SGSN containing a PDU type that does not fit, according to the mapping defined in table 5.4.1, with the functional entity identified by the BVCI provided by the network service entity, is discarded and a STATUS PDU with a cause value set to "Protocol error - unspecified" is sent. + +A PTP functional entity is responsible for PTP user data transmission. There is one PTP functional entity per cell. Within the present document, a cell is identified by a BVCI unless it is explicitly stated otherwise. + +A PTM functional entity is responsible for PTM user data transmission. There is one or more PTM functional entities per BSS. + +A signalling functional entity is responsible for other functions e.g. paging. There is only one signalling entity per Network Service Entity (NSE). There is one or more NSEs per BSS. + +Each BVC is identified by means of a BSSGP Virtual Connection Identifier (BVCI) which has end-to-end significance across the Gb interface. Each BVCI is unique between two peer Network Service Entities. + +In the BSS, it shall be possible to configure BVCI statically by administrative means, or dynamically. In case of dynamic configuration, the BSSGP shall accept any BVCI passed by the underlying Network Service entity. + +At the SGSN side, BVCI associated with PTP functional entities shall be dynamically configured. The BVCI associated with signalling functional entities and PTM functional entities are statically configured. + +The BVCI value 0000 hex shall be used for the signalling functional entities. + +The BVCI value 0001 hex shall be used for the PTM functional entities. + +All other values may be used freely by the BSS and shall be accepted by the SGSN. + +**Table 5.4.1: BSSGP PDU, BVCI and functional entity mapping** + +| BSSGP PDU | Mapping of BVCI to functional entity | +|-----------|--------------------------------------| +|-----------|--------------------------------------| + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| DL-UNITDATA | PTP | +| UL-UNITDATA | PTP | +| RA-CAPABILITY | PTP | +| DL-MBMS-UNITDATA | PTM | +| UL-MBMS-UNITDATA | PTM | +| PAGING-PS | PTP or SIGNALLING (note 1) | +| PAGING-CS | PTP or SIGNALLING (note 2) | +| RA-CAPABILITY-UPDATE / RA-CAPABILITY-UPDATE-ACK | PTP | +| RADIO-STATUS | PTP | +| SUSPEND / SUSPEND-ACK / SUSPEND-NACK | SIGNALLING | +| RESUME / RESUME-ACK / RESUME-NACK | SIGNALLING | +| FLUSH-LL / FLUSH-LL-ACK | SIGNALLING | +| LLC-DISCARDED | SIGNALLING | +| FLOW-CONTROL-BVC / FLOW-CONTROL-BVC-ACK | PTP | +| FLOW-CONTROL-MS / FLOW-CONTROL-MS-ACK | PTP | +| FLOW-CONTROL-PFC / FLOW-CONTROL-PFC-ACK | PTP | +| STATUS | PTP or PTM or SIGNALLING (note 3) | +| BVC-BLOCK / BVC-BLOCK-ACK | SIGNALLING | +| BVC-UNBLOCK / BVC-UNBLOCK-ACK | SIGNALLING | +| BVC-RESET / BVC-RESET-ACK | SIGNALLING | +| SGSN-INVVOKE-TRACE | SIGNALLING | +| DOWNLOAD-BSS-PFC | PTP | +| CREATE-BSS-PFC / CREATE-BSS-PFC-ACK / CREATE-BSS-PFC-NACK | PTP | +| MODIFY-BSS-PFC / MODIFY-BSS-PFC-ACK | PTP | +| DELETE-BSS-PFC / DELETE-BSS-PFC-ACK / DELETE-BSS-PFC-REQ | PTP | +| PS-HANDOVER-REQUIRED / PS-HANDOVER-REQUIRED-ACK / PS-HANDOVER-REQUIRED-NACK | PTP | +| PS-HANDOVER-REQUEST / PS-HANDOVER-REQUEST-ACK / PS-HANDOVER-REQUEST-NACK | PTP | +| PS-HANDOVER-COMPLETE / PS-HANDOVER-COMPLETE-ACK | PTP | +| PS-HANDOVER-CANCEL | PTP | +| PERFORM-LOCATION-REQUEST / PERFORM-LOCATION-RESPONSE / PERFORM-LOCATION-ABORT | SIGNALLING | +| POSITION-COMMAND / POSITION-RESPONSE | SIGNALLING | +| RAN-INFORMATION-REQUEST/ RAN-INFORMATION/ RAN-INFORMATION-ACK/ RAN-INFORMATION-ERROR/ RAN-INFORMATION-APPLICATION-ERROR | SIGNALLING | +| MBMS-SESSION-START-REQUEST/ MBMS-SESSION-START-RESPONSE/ MBMS-SESSION-STOP-REQUEST/ MBMS-SESSION-STOP-RESPONSE/ MBMS-SESSION-UPDATE-REQUEST/ MBMS-SESSION-UPDATE-RESPONSE | SIGNALLING | +| MS-REGISTRATION-ENQUIRY/ MS-REGISTRATION-ENQUIRY-RESPONSE | SIGNALLING | +| NOTE 1: The network may initiate paging of an MS in READY mobility management state at an indication of a lower layer failure (see 3GPP TS 24.008 sub-clause 4.7.9.1). In this case, the BVCI=PTP may be used. | | +| NOTE 2: If the network initiates circuit-switched paging of a MS in READY mobility management state (e.g. a MS in class A or B mode of operation and in packet transfer mode), then the BVCI=PTP. If the MS is in STANDBY state, then the BVCI=SIGNALLING. | | +| NOTE 3: The setting of the BVCI is dependent upon the context within which the STATUS PDU was generated. | | + +## 5.4.2 Link Selector Parameter (LSP) + +The link selector parameter is defined in 3GPP TS 48.016. At one side of the Gb interface, all BSSGP UNITDATA PDUs related to an MS shall be passed with the same LSP, e.g. the LSP contains the MS's TLLI, to the underlying network service. The LSPs used at the BSS and SGSN for the same MS may be set to different values. + +## 5.4.3 [functional-name] PDU + +The parameters that make up a [functional-name] PDU are defined in clause 10, "PDU Functional Definitions and contents". + +## 5.4.4 Network Service Entity Identifier (NSEI) + +The Network Service Entity at the BSS and the SGSN provides the network management functionality required for the operation of the Gb interface. The Network Service Entity is described in 3GPP TS 48.016. + +Each Network Service Entity is identified by means of a Network Service Entity Identifier (NSEI). The NSEI together with the BVCI uniquely identifies a BSGP Virtual Connection (e.g. a PTP functional entity) within an SGSN. The NSEI is used by the BSS and the SGSN to determine the NS-VCs that provides service to a BVCI. + +## 5.4.5 BSS Context + +The SGSN can provide a BSS with information related to ongoing user data transmission. The information related to one MS is stored in a BSS context. The BSS may contain BSS contexts for several MSs. A BSS context contains a number of BSS packet flow contexts. A BSS packet flow context is identified by a packet flow identifier assigned by the SGSN. There are four pre-defined packet flows identified by four reserved packet flow identifier values. One pre-defined packet flow is used for best-effort service, one for signalling, one for SMS, and one for TOM8. The BSS shall not negotiate BSS packet flow contexts for these pre-defined packet flows with the SGSN. + +NOTE: The TOM8 PFI is used to transfer LCS RRLP messages between the MS and the SGSN. + +NOTE: PFC procedures (Create BSS PFC, Modify BSS PFC, Delete BSS PFC) and PS Handover procedures (PS Handover Required, PS Handover Request, PS Handover Complete) do not apply to pre-defined packet flows. + +## 5.4.6 MBMS Service Context + +The SGSN can provide a BSS with information related to ongoing MBMS user data transmission. The information related to one MBMS Session is stored in an MBMS Service Context. A TMGI and optionally an MBMS Session Identity identify an MBMS Service Context. The BSS may contain MBMS Service Contexts for several MBMS Sessions. + +## 5.4.7 TLLI + +The TLLI is used to uniquely identify a mobile station and needs to be included in a number of BSSGP PDUs across the Gb interface. + +A change of TLLI may occur as a consequence of a P-TMSI reallocation. The new TLLI shall be used to address the mobile station after completion on the network side of the related GMM procedure (see 3GPP TS 24.008). However, the SGSN should not use the new TLLI for BSSGP addressing purposes towards the BSS either: + +- until having signalled the change of TLLI to the BSS via the Downlink UNITDATA procedure (see sub-clause 6.1) or +- until having received from the BSS any BSSGP PDU including the new TLLI. + +--- + +# 6 User data and signalling procedures between RL and BSSGP SAPs + +## 6.1 Downlink UNITDATA procedure + +On the downlink, a DL-UNITDATA PDU shall contain information elements to be used by the RLC/MAC function and an LLC-PDU. There shall be only one LLC-PDU per DL-UNITDATA PDU. The LLC-PDU shall always be the last information element in the DL-UNITDATA PDU, and shall be aligned on a 32 bit boundary for efficient processing. + +An SGSN provides the BSSGP with a current TLLI, identifying the MS. If an SGSN provides a second TLLI, indicating that an MS has recently changed its TLLI, this shall be considered as the "old" TLLI. A BSS uses the "old" TLLI to locate an MS's existing context. Subsequent uplink data transfers for this MS shall reference the current TLLI, and not the old TLLI. + +The SGSN shall include the IMSI in the PDU. As an exception, the SGSN may omit the IMSI in the PDU if the mobile station identified by the TLLI is in MM non-DRX mode period (i.e. during a GMM procedure for *GPRS attach* or *routing area updating* defined in 3GPP TS 24.008) and the SGSN does not have a valid IMSI. + +The SGSN may include the *Service UTRAN CCO* (Cell Change Order) information element in the PDU (relevant if the network initiated cell change order to UTRAN, network initiated cell change order to E-UTRAN, PS handover to UTRAN or PS handover to E-UTRAN procedures are used ). If this information element is received in multiple PDUs (either DL-UNITDATA PDU(s), CREATE-BSS-PFC PDU(s) or PS-HANDOVER-REQUEST PDU(s)), the information element contained in the last received PDU shall take precedence. + +If the SGSN has valid DRX Parameters for a TLLI, then the SGSN shall include them in the PDU. Nevertheless, the SGSN can omit the DRX Parameters if the MS identified with the TLLI is in MM non-DRX mode period to speed up the transmission of the LLC-PDU on the radio interface. The SGSN shall not send a DL-UNITDATA PDU without the DRX Parameters IE if the MS identified with the TLLI is not in MM non-DRX mode period. + +An exception case is when the SGSN has uplink and downlink Coverage Class information (previously received from the BSS in the UL-UNITDATA PDU) or eDRX information (negotiated during NAS signalling) or both available for a given MS in which case it shall proceed as follows when sending a DL-UNITDATA PDU for that MS: + +- If uplink and downlink Coverage Class information is available for the MS then the SGSN shall include the Coverage Class information in the DL-UNITDATA. If a negotiated eDRX value is available then it shall also be included. The SGSN considers the eDRX to be negotiated upon accepting the eDRX cycle value requested by a MS during NAS signalling. If a negotiated eDRX value is not available but DRX information is available then it shall be included. If the target cell supports EC-GSM-IoT the corresponding LLC-PDU is delivered as follows: + - If the MS is in idle mode a downlink packet resource assignment is sent on the EC-AGCH of its EC\_CCCH\_GROUP (see 3GPP TS 45.002 [32]) using the indicated downlink Coverage Class information and the lowest eDRX cycle and the LLC PDU is sent thereon. + - If the MS is in packet transfer mode the LLC PDU is delivered using either an existing downlink EC TBF or using a new downlink EC TBF established by sending a downlink packet resource assignment on the EC-PACCH (see 3GPP TS 44.060 [22]) using the downlink Coverage Class information the BSS is currently using for that MS. +- If Coverage Class information is not available but a negotiated eDRX value is available for the MS then the SGSN shall include the negotiated eDRX value in the DL-UNITDATA PDU. If the target cell supports eDRX the corresponding LLC-PDU is delivered as follows: + - If the MS is in idle mode a downlink packet resource assignment is sent on the AGCH of its CCCH\_GROUP (see 3GPP TS 45.002 [32]) using the lowest eDRX cycle and the LLC PDU is sent thereon. + - If the MS is in packet transfer mode the LLC PDU is delivered using either an existing downlink TBF or using a new downlink TBF established by sending a downlink packet resource assignment on the PACCH (see 3GPP TS 44.060 [22]). +- The SGSN shall apply these rules also when sending a DL-UNITDATA PDU to a MS for which the GMM procedure for *GPRS attach* or *routing area updating* (defined in 3GPP TS 24.008) has not yet completed. + +An SGSN provides the BSSGP with MS specific information, enabling the RLC/MAC entity in a BSS to transmit an LLC-PDU to the MS in a user specific manner. The information made available to the radio interface includes: + +- MS Radio Access Capability. This defines the radio capabilities of the ME. If there is valid MS Radio Access Capability information known by the SGSN for the associated MS, the SGSN shall include it in the DL-UNITDATA PDU. Otherwise, MS Radio Access Capability shall not be present; +- Packet Flow Identifier. This identifies the packet flow context associated with the LLC PDU and is included by the SGSN if the packet flow context feature is negotiated. If the mobile station does not support the PFC feature or if the PFI is not known (e.g. the new SGSN did not get the PFI from the old SGSN during a RAU) then the SGSN shall use the pre-defined PFI to indicate best-effort QoS; +- QoS Profile. This defines the (peak) bit rate, the type of BSSGP's SDU (signalling or data), the type of LLC frame (ACK, SACK, or not), the precedence class, and the transmission mode to be used when transmitting the LLC-PDU across the radio interface; + +- PDU Lifetime. This defines the remaining time period that the PDU is considered as valid within the BSS. If the PDU is held for a period exceeding the "PDU Lifetime" time period, the PDU shall be locally discarded. The PDU Lifetime is set within the SGSN by the upper layers. + +An SGSN provides the BSSGP with Enhanced Coverage restriction information which indicates to the BSS whether the use of enhanced coverage is restricted or not for a given MS, thereby enabling the BSS to decide the allowable coverage classes (uplink and/or downlink) for the MS while operating in packet transfer mode. + +A BSS may incorporate the PDU Lifetime, the Precedence and the (peak) bit rate into its radio resource scheduler. If the PFI is present then the BSS may incorporate the information from the associated ABQP into its radio resource scheduler. The algorithm to do this is out of scope of the present document. + +If the PFI is known in the BSS and does not correspond to a predefined PFI, then: + +- the (peak) bit rate and the precedence class fields present in the QoS Profile IE shall be ignored by the BSS; +- if the Allocation/Retention Priority was provided at the time the corresponding PFC was created or last modified, then the 'Priority' IE, if present in the downlink UNITDATA PDU, is discarded. + +Two types of BSSGP SDU are distinguished within the QoS Profile: layer 3 signalling and data. Layer 3 signalling may be transmitted over the Um interface with higher protection. If the MS has an RR connection to the network (see 3GPP TS 44.018), Layer 3 signalling may be transmitted over the Um interface on the main signalling link of the RR connection, provided that the LLC PDU meets length restrictions imposed by the BSS. In this case, the BSS shall include the LLC PDU contained in the BSSGP PDU in the correspondent Layer 3 Um interface message (see 3GPP TS 44.018). + +The type of LLC frame indicates if the LLC frame type is an ACK or SACK command/response, or not (see 3GPP TS 44.064). An ACK or SACK command/response frame type may be transmitted over the Um interface with higher protection. + +Two transmission modes across the radio interface are possible: acknowledged (using RLC/MAC ARQ functionality) and unacknowledged (using RLC/MAC unitdata functionality). These transmission modes do not apply when the MS has an RR connection to the network and BSS uses the main signalling link of the RR connection, in which case the acknowledged transmission mode is used. + +If Priority is present, assuming it shall not be discarded according to the rule above, only the priority-level field shall be regarded. The management of priority levels is implementation dependent and under operator control. The preemption capability indicator, the queuing allowed indicator and preemption vulnerability indicator shall be ignored in this case. + +In addition to constructing the DL-UNITDATA, the SGSN supplies the LSP, the BVCI, the NSEI, and for an IP sub-network the NS Change IP endpoint, associated with the MS to the lower layer network service, enabling network service routing to the peer entity. These parameters are not transmitted as part of the BSSGP across the Gb-interface for the purpose of identifying the receiving endpoint (they are sent in the BSSGP Perform-Location-Request PDU to identify the serving cell of the target MS). + +If the Gb-interface is supported using an IP sub-network, then the Resource Distribution function at the SGSN may transmit a BSSGP DL-UNITDATA PDU with an LLC-PDU Length Indicator set to 0. The BSS uses this DL-UNITDATA to change the IP endpoint at the SGSN to which any future UL-UNITDATA for the TLLI (indicated in the DL-UNITDATA) is sent. The LLC-PDU with a Length Indicator set to 0 is not sent across the radio interface. + +In the case where localised service area is supported the SGSN may inform the BSS as to which LSA identities that the mobile has preferences by sending the LSA INFORMATION element. The BSS stores this information and uses it e.g. for network controlled cell re-selection when determining specific cell selection parameters for the mobile. The algorithm for determining specific cell selection parameters for the mobile is not defined further in the present document. The SGSN may inform the BSS about the contents of SPID in the DL-UNITDATA PDU. In this case the SPID is stored in the BSS. + +When the "Service Identification for improved Radio Utilization for GERAN" (SIRUG) feature (see clause 5.3.5.3 of TS 23.060 [7]) is supported, and the SGSN receives SCI information in the GTP-U header, the SGSN inserts the SCI IE and the GGSN/P-GW location IE in the associated DL-UNITDATA PDU(s). The BSS uses the Home PLMN ID contained within the IMSI and the GGSN/P-GW location information to determine whether or not it can handle the SCI information for that GGSN/P-GW. If it cannot, the BSS discards the SCI information and shall treat the rest of the DL-UNITDATA normally. + +In abnormal cases, if the SCI IE is received but the GGSN/P-GW location IE is missing, then the BSS shall assume that the GGSN/P-GW is located in the VPLMN; and, if the GGSN/P-GW location IE is received but the SCI IE is missing, then the BSS shall ignore the GGSN/P-GW location IE. + +Specific handling related to MOCN and GWCN configurations of network sharing, is described in sub-clauses 6.6 and 6.7. + +When the SGSN is using a GWCN configuration, and the BSSGP DL-UNITDATA PDU contains a local TLLI, then the BSC shall use the registered Operator specific NRI value to identify the corresponding serving operator. + +Specific handling related to Dedicated Core Networks as well as MS assisted Dedicated Core Network selection is described in sub-clause 6.6. + +An exception case is when the SGSN determines that there is data to be delivered to a MS for which the MPM Timer is running (see sub-clause 8b.2.1). In this case it shall not attempt delivery of that data until the MPM Timer expires or is stopped. + +### 6.1.1 Abnormal conditions + +The following actions are defined in periods of congestion. + +To satisfy the maximum number of service requests, the BSS may redistribute MSs among cells (i.e. network controlled cell reselection is initiated). If this occurs, the BSS may inform the SGSN through the RADIO-STATUS PDU (Radio Cause value: cell reselection ordered). The BSS shall update any internal references that indicate the location of the MS. The BSS may attempt to internally re-route queued LLC frames to an MS that has been moved to a new cell. If this functionality is not supported, or if it is not possible to internally re-route LLC frames, the LLC frame shall be discarded. + +It is the responsibility of the higher layer protocols in the SGSN to cope with discarded LLC frames. + +## 6.2 Uplink UNITDATA procedure + +On the uplink, a UL-UNITDATA PDU shall contain information elements derived from the RLC/MAC function (except when GTTP is used in the Um interface, see 3GPP TS 44.018), meaningful to higher-layer protocols in an SGSN, and an LLC-PDU. There shall be only one LLC-PDU per UL-UNITDATA PDU. The LLC-PDU shall always be the last information element in the UL-UNITDATA PDU, and shall be aligned on a 32 bit boundary for efficient processing. + +The BSS shall provide the TLLI associated to the MS to the SGSN. + +The BSS shall provide a BVCI and an NSEI indicating the PTP functional entity (i.e. the cell) upon which the LLC-PDU was received. The SGSN shall obtain the BVCI, the NSEI, and in the case of an IP sub-network may obtain the LSP and the NS Change IP endpoint, from the underlying network service; the BVCI and the NSEI are not visible in the UL-UNITDATA PDU. + +The BSS provides the SGSN with the QoS Profile used in the LLC-PDU transmission from the mobile station across the radio interface. + +- QoS Profile. This reports the (peak) bit rate, the precedence used at radio access and the transmission mode used across the radio path. The type of the BSSGP SDU, layer 3 signalling or data, and the type of LLC frame, SACK, ACK, or not, are not meaningful on the uplink and shall be ignored. +- Packet Flow Identifier. This identifies the packet flow context that is obtained from the mobile. If the mobile station does not provide a PFI then the BSS shall use the pre-defined PFI to indicate best-effort QoS. + +In order to support location based services, the BSS shall include the cell identifier of the cell upon which the LLC-PDU was received. + +In the case where localised service area is supported, the BSS shall include the LSA identities of the cell upon which the LLC-SDU was received. The BSS may exclude LSA identities that are not included in the LSA INFORMATION element. + +If EC-GSM-IoT is supported by the BSS and the SGSN, then the BSS shall provide in the UL-UNITDATA PDU: + +- The uplink and downlink Coverage Class if the downlink Coverage Class is reported by the MS during system access see 3GPP TS 44.018 [25]. +- The exception report flag if the UL-UNITDATA PDU contains an LLC PDU sent by the MS using an uplink EC TBF established in response to an EC PACKET CHANNEL REQUEST message indicating high priority (i.e. an exception report), see 3GPP TS 44.018 [25] and 3GPP TS 44.060 [22]. +- The exception report flag if the UL-UNITDATA PDU contains an LLC PDU sent by the MS using an uplink EC TBF established in response to an EC PACKET DOWNLINK ACK/NACK message including channel request and indicating high priority (i.e. an exception report), see 3GPP TS 44.018 [25] and 3GPP TS 44.060 [22]. + +In addition to constructing the UL-UNITDATA, the BSS supplies the LSP, the NSEI, the BVCI, and for an IP sub-network the NS Change IP endpoint, associated with the MS to the lower layer network service, enabling network service routing to the peer entity. These parameters are not transmitted as part of the BSSGP across the Gb-interface. If the Gb-interface is supported using an IP sub-network, then the Resource Distribution function at the BSS may transmit a BSSGP UL-UNITDATA PDU with an LLC-PDU Length Indicator set to 0. The SGSN uses this UL-UNITDATA to change the IP endpoint at the BSS to which any future DL-UNITDATA for the TLLI (indicated in the UL-UNITDATA) is sent. + +Specific handling related to the use of network sharing in a cell is described in sub-clauses 6.6 and 6.7 for a mobile station non supporting network sharing. In the case of a mobile station supporting network sharing the BSS shall include the selected PLMN ID within the UL-UNITDATA PDU when a foreign TLLI or a random TLLI is included in the same UL-UNITDATA PDU, as described within sub-clause 10.2.2; both MS support and selected PLMN ID shall be derived by the BSS from information within the RLC data block as described within 3GPP TS 44.060 [22]. + +Specific handling related to Dedicated Core Network as well as MS assisted Dedicated Core Network selection is described in sub-clause 6.6. + +## 6.2.1 Abnormal conditions + +None specified. + +## 6.3 RA-CAPABILITY procedure + +The SGSN stores an MS's current radio access capability (which may be changed by higher layer mobility management procedures). An MS's current radio access capability, and the TLLI identifying the MS, are conveyed to a BSS in a RA-CAPABILITY PDU. The received MS's radio access capability, if valid, shall then replace any radio access capability previously associated with the MS. + +### 6.3.1 Abnormal conditions + +If the BSS receives an unknown Access Technology Type in the MS Radio Access Capability field, it shall ignore the fields associated with that Access Technology type. + +If the BSS receives unknown fields within a known Access Technology Type in the MS Radio Access Capability field, it shall ignore the unknown fields. + +## 6.4 Downlink MBMS-UNITDATA procedure + +On the downlink, a DL-MBMS-UNITDATA PDU shall contain information elements to be used by an LLC-PDU. There shall be only one LLC-PDU per DL-MBMS-UNITDATA PDU. The LLC-PDU shall always be the last information element in the DL-MBMS-UNITDATA PDU, and shall be aligned on a 32 bit boundary for efficient processing. + +An SGSN provides the BSSGP with a current TMGI, if available, and MBMS Session Identity, identifying the MBMS Service Context. + +The information made available to the radio interface includes: + +- PDU Lifetime. This defines the remaining time period that the PDU is considered as valid within the BSS. If the PDU is held for a period exceeding the "PDU Lifetime" time period, the PDU shall be locally discarded. The PDU Lifetime is set within the SGSN by the upper layers. + +A BSS may incorporate the PDU Lifetime into its radio resource scheduler. + +In addition to constructing the DL-MBMS-UNITDATA, the SGSN supplies the BVCI and the NSEI to the BSS. + +## 6.5 Uplink MBMS-UNITDATA procedure + +On the uplink, a UL-MBMS-UNITDATA PDU shall contain an LLC-PDU. There shall be only one LLC-PDU per UL-MBMS-UNITDATA PDU. The LLC-PDU shall always be the last information element in the UL-MBMS-UNITDATA PDU, and shall be aligned on a 32 bit boundary for efficient processing. + +The BSS shall provide the TMGI and, if present in the MBMS Service Context, the MBMS Session Identity to the SGSN in order to identify the MBMS session. + +The BSS shall provide a BVCI and an NSEI indicating the PTM functional entity upon which the LLC-PDU was received. The SGSN shall obtain the BVCI, the NSEI, and in the case of an IP sub-network may obtain the LSP and the NS Change IP endpoint, from the underlying network service; the BVCI and the NSEI are not visible in the UL-MBMS-UNITDATA PDU. + +In addition to constructing the UL-MBMS-UNITDATA, the BSS supplies the LSP, the NSEI, the BVCI, and for an IP sub-network the NS Change IP endpoint, associated with the MBMS session to the lower layer network service, enabling network service routing to the peer entity. These parameters are not transmitted as part of the BSSGP across the Gb-interface. If the Gb-interface is supported using an IP sub-network, then the resource distribution function at the BSS may transmit a BSSGP UL-MBMS-UNITDATA PDU in order to change the IP endpoint at the BSS to which any future DL-MBMS-UNITDATA for the MBMS session (indicated with TMGI and, if available, MBMS Session Identity in the UL-MBMS-UNITDATA) shall be sent from the SGSN. + +NOTE: In this version of the specification, the procedure is used for resource distribution only meaning that the LLC PDU length indicator shall always be set to zero. + +## 6.6 Rerouting procedure in case of MOCN configuration for network sharing, Dedicated Core Networks or MS assisted Dedicated Core Network selection + +### 6.6.1 General + +This procedure shall be supported by a BSS if it supports the MOCN configuration (see [43]), if it supports Dedicated Core Networks or if it supports MS assisted Dedicated Core Network selection. The rerouting procedure in a GWCN configuration is described in sub-clause 6.7. + +In the MOCN configuration the radio access part of the network is shared. There may be more than one Gb-Interface towards the PS domain of different CN operators from the BSS. + +Rerouting procedure is a mechanism used as part of the assignment of CN operator in shared networks with MOCN configuration or GWCN configuration (see sub-clause 6.7) when an MS not supporting network sharing performs initial attach/registration. In this case BSS may not know towards which SGSN to route the initial MS request message and the latter may be rerouted to another SGSN by BSS. + +More precisely, in case of MOCN configuration, the selection of SGSN in BSS is based on the NRI (valid or invalid) or by random selection. In case where the SGSN cannot be deduced from the NRI and a *GPRS attach or routing area updating* initial layer 3 message (defined in [11]) shall be transferred in UL-UNITDATA message towards a SGSN, BSS shall choose a SGSN and initiate a rerouting procedure. + +To trigger a rerouting procedure in MOCN configuration, the BSS adds the Redirect Attempt Flag IE to the UL-UNITDATA message, in order to indicate that the SGSN shall respond by including either Redirection Indication IE or Redirection Completed IE in DL-UNITDATA message. + +For Dedicated Core Networks (DCNs) multiple DCNs may be deployed within a PLMN where each DCN may be dedicated to serve specific type(s) of subscribers. + +- For DCN the Rerouting procedure is used as part of the selection of core network node to serve the MS when it has successfully transmitted an initial LLC PDU (i.e. Foreign or Random TLLI is used) to a BSS that supports + +DCN. More precisely, the procedure provides the BSS with the Null-NRI/SGSN group ID which the BSS uses to select a SGSN towards which the initial uplink LLC PDU shall be routed. + +- To trigger a rerouting procedure in the case where a BSS cannot determine an appropriate DCN for forwarding an uplink LLC PDU, the BSS selects an available SGSN and adds the Redirect Attempt Flag IE to the UL-UNITDATA message used to forward the uplink LLC PDU to that SGSN. +- The inclusion of the Redirect Attempt Flag IE serves as indication to the SGSN that, after determining where to re-route the LLC PDU, it shall respond to the BSS by including either Redirection Indication IE or Redirection Completed IE in the DL-UNITDATA message it sends in response to the UL-UNITDATA message. + +For MS assisted Dedicated Core Network selection the Rerouting procedure is used for selection of a core network node to serve the MS when it supports MS assisted Dedicated Core Network selection and has successfully transmitted an initial LLC PDU to a BSS that supports MS assisted Dedicated Core Network selection: + +- The BSS selects a DCN for the selected PLMN based on DCN-ID information received from the MS and configuration information (i.e. information that allows the BSS to interpret DCN-ID values), see 3GPP TS 44.060 [22]. +- The inclusion of the Redirect Attempt Flag IE in the UL-UNITDATA message serves as indication to the SGSN that, after determining if it is the correct DCN or not, it shall respond to the BSS by including either a Redirection Indication IE or a Redirection Completed IE in the DL-UNITDATA message it sends in response to the UL-UNITDATA message. + +## 6.6.2 Reroute Indication + +If the UL-UNITDATA message does not contain the *CS Registered Operator* IE and the SGSN cannot serve the request and reroute is possible (error causes are related to subscription options - defined in [11]), the reject Layer 3 Information LLC-PDU (e.g. GPRS attach Reject) and a *Redirection Indication* IE containing a Reroute Reject Cause shall be included in the DL-UNITDATA message for the downlink direction. + +When the IMSI, or in case the BSS supports CS/PS coordination enhancements, the *CS Registered Operator* IE or the *Selected Operator* IE, is not included in the UL-UNITDATA message and CS/PS domain registration coordination is required (see [43]), the Initial LLC-PDU and a *Redirection Indication* IE containing the Reroute Reject Cause set to “CS/PS domain registration coordination required” shall be included in the DL-UNITDATA message for the downlink direction. CS/PS domain registration coordination may not be performed for the operator’s own subscribers by the SGSN. + +In addition the DL-UNITDATA message shall contain: + +- The Initial LLC-PDU received from the MS; +- The IMSI, if available; +- The Unconfirmed send state variable, if available. + +If the SGSN supports CS/PS coordination enhancements, the DL-UNITDATA message shall also contain: + +- The Old Routing Area Identification as indicated by the MS in the Initial LLC-PDU or, +- The Attach Indicator in case the Initial LLC-PDU contains a GPRS attach (see [11]). + +In a MOCN configuration, if the BSS does not support CS/PS coordination enhancements and the *Redirection Indication* IE in the DL-UNITDATA message is received from a SGSN which is not the last attempted, then the BSS shall re-initiate the procedure towards another CN operator when possible (or possibly to the same CN in case when CS/PS domain registration coordination is required), with the following additional information in the UL-UNITDATA message: + +- The Initial LLC-PDU as LLC-PDU; +- The Redirect Attempt Flag IE; +- The IMSI, if received from one of previously attempted CN operators; +- The Unconfirmed send state variable, if received from previously attempted CN operator. + +If the BSS supports CS/PS coordination enhancements and the *Redirection Indication* IE in the DL-UNITDATA message is received from a SGSN which is not the last attempted, it shall proceed as follows: + +- if the DL-UNITDATA message contains the Old Routing Area Identification and the BSS from this information (and from BSS internal configuration) is able to uniquely identify one of the CN operators in the shared network, then the BSS shall re-initiate the procedure towards the SGSN of the identified CN operator with the Selected Operator, Initial LLC-PDU, Redirect Attempt Flag, IMSI and Unconfirmed send state variable (if received from previously attempted CN operator) included in the UL-UNITDATA message; +- if the DL-UNITDATA message contains the Old Routing Area Identification and the BSS from this information (and from BSS internal configuration) cannot identify one of the CN operators in the shared network, then the BSS shall initiate the MS Registration Enquiry procedure in the CS domain (see [14]); +- if the DL-UNITDATA message contains the Attach Indicator then the BSS shall initiate the MS Registration Enquiry procedure in the CS domain (see [14]). + +NOTE: The configuration by means the BSS identifies a CN operator from the received Old Routing Area Identification is implementation dependent and under operator control. + +If, as a result of the MS Registration Enquiry procedure in the CS domain, the MS is found to be registered with one of the shared CN operators, then the BSS shall re-initiate the procedure towards the SGSN of the same CN operator with the CS Registered Operator, Initial LLC-PDU, Redirect Attempt Flag, IMSI and Unconfirmed send state variable (if received from previously attempted CN operator) included in the UL-UNITDATA message. + +If the MS is not found to be registered in the CS domain with any of the shared CN operators, then the BSS shall perform CS/PS domain registration coordination based on the received IMSI and re-initiate the procedure towards the SGSN of the identified CN operator with the Selected Operator, Initial LLC-PDU, Redirect Attempt Flag, IMSI and Unconfirmed send state variable (if received from previously attempted CN operator) included in the UL-UNITDATA message. + +Upon reception of the downlink *Redirection Indication* IE, the BSS shall store as part of the Rerouting Function the associated Reroute Reject Cause and LLC-PDU related to this SGSN. + +In case the Reroute Reject Cause is set to "CS/PS domain registration coordination required" and the BSS does not support CS/PS coordination enhancements, then the BSS shall perform CS/PS domain registration coordination based on the received IMSI. In this case the Reroute Reject Cause value and the associated LLC-PDU shall not be stored. + +For Dedicated Core Networks or for MS assisted Dedicated Core Network selection, if the SGSN decides to reroute the handling of an initial uplink LLC PDU to another CN node the DL-UNITDATA message shall also contain: + +- The Initial LLC-PDU received from the MS; +- The IMSI, if received unencrypted from the MS; +- The Null-NRI/SGSN group ID; +- Additional P-TMSI, if available; +- UE Usage Type. + +If the BSS supports Dedicated Core Networks or if the BSS supports MS assisted Core Network selection and the *Redirection Indication* IE in the received DL-UNITDATA message indicates a new SGSN (i.e. different from the previously used SGSN), it shall select and route the initial uplink LLC PDU to the new SGSN. The selection is based on the Null-NRI/SGSN Group ID and possibly also based on the Additional P-TMSI received in the DL-UNITDATA message. If no valid SGSN can be identified within the set of valid nodes the BSS selects either the default DCN or an SGSN based on operator configuration see 3GPP TS 23.401. The UL-UNITDATA message sent to the selected SGSN shall contain: + +- The Initial LLC-PDU received from the MS; +- The IMSI, if available; +- The Null-NRI/SGSN group ID; +- UE Usage Type. + +The presence of Null-NRI/SGSN Group ID in the UL-UNITDATA message indicates to the SGSN that the message is a rerouted message and that the SGSN shall not further reroute the initial LLC-PDU (see sub-clause 10.2.2). The UE Usage Type shall be used by the SGSN to select a GGSN. + +If the SGSN cannot serve the request, and if the Null-NRI/SGSN Group ID was provided in the UL-UNITDATA message carrying the initial LLC-PDU, the SGSN shall include the response LLC PDU (e.g. containing the GPRS attach Reject) and a *Redirection Indication* IE containing a Reroute Reject Cause (error causes are related to subscription options - defined in [11]) in the DL-UNITDATA message to the BSS. + +In case all attempted CN operators have replied with a *Redirection Indication* IE, the BSS shall select the most appropriate Layer 3 Information received from the attempted CN nodes based on the stored information as part of the Rerouting procedure and send it back to the MS (see [11]). + +### 6.6.3 Reroute complete + +If the SGSN can serve the request, the *Redirection Completed* IE with outcome value set to "MS is accepted" or "MS is already registered" and Layer 3 Information LLC-PDU (e.g. GPRS Attach Accept) shall be included in the DL-UNITDATA message for the downlink direction. + +Upon reception of the UL-UNITDATA message containing the *CS Registered Operator* IE, the SGSN supporting CS/PS coordination enhancements shall conclude the Rerouting procedure and include the *Redirection Completed* IE in the DL-UNITDATA message. + +Upon reception of the downlink *Redirection Completed* IE, the BSS shall send back the included LLC-PDU to the MS and terminate the Rerouting procedure. + +### 6.6.4 Abnormal Conditions + +If the SGSN cannot serve the request and rerouting is not possible, the *Redirection Completed* IE with outcome value set to "MS is not accepted" and Layer 3 Information LLC-PDU (e.g. GPRS Attach Reject) shall be included in the DL-UNITDATA message for the downlink direction. + +If, as a result of the analysis of the DL-UNITDATA message, the MS Registration Enquiry procedure is initiated in the CS domain and the MSC does not support CS/PS coordination enhancements, then the BSS shall behave as if the MS is not registered with the CN operator of that MSC. + +## 6.7 Rerouting procedure in case of GWCN configuration for network sharing + +### 6.7.1 General + +This procedure shall be supported by a BSS and an SGSN if and only if both nodes support CS/PS coordination enhancements in a GWCN configuration (see 3GPP TS 23.251 [43]). The rerouting procedure in a MOCN configuration is described in sub-clause 6.6. + +In the GWCN configuration the radio access part of the network as well as the core network nodes (MSC and SGSN) are shared between the different CN operators. + +Rerouting procedure is a mechanism used as part of the assignment of a CN operator in a shared network when a MS not supporting network sharing performs initial attach/registration. Upon reception of the initial MS request message, the BSS may not know which CN operator to select and thus which CN operator to forward the initial MS request message to. If the initial MS request is not accepted by the CN operator selected by the BSS, a reroute of the initial MS request message to another CN operator within the shared network may be needed. + +More precisely, the selection of a CN operator in the BSS is based on the NRI (valid or invalid) or by random selection. In case the CN operator cannot be deduced from the NRI and a *GPRS attach* or *routing area updating* initial layer 3 message (defined in [11]) shall be transferred in the UL-UNITDATA message, the BSS shall select a CN operator and initiate the rerouting procedure. + +To trigger a rerouting procedure in a GWCN configuration, the BSS includes the Redirect Attempt Flag IE in the UL-UNITDATA message. By including the Redirect Attempt Flag IE in the UL-UNITDATA message, the SGSN supporting GWCN shall respond by including either the Redirection Indication IE or the Redirection Completed IE in the DL-UNITDATA message. + +## 6.7.2 Reroute indication + +If the UL-UNITDATA message does not contain the *CS Registered Operator* IE and the CN operator selected by the BSS cannot serve the MS and rerouting is possible (error causes are related to subscription options - defined in [11]), the reject Layer 3 Information (e.g. GPRS Attach Reject) and a *Redirection Indication* IE containing a Reroute Reject Cause shall be included in the DL-UNITDATA message for the downlink direction. + +When neither the *CS Registered Operator* IE nor the *Selected Operator* IE is included in the UL-UNITDATA message and CS/PS domain registration coordination is required (see 3GPP TS 23.251 [43]), the Initial LLC-PDU and a *Redirection Indication* IE containing the Reroute Reject Cause set to “CS/PS domain registration coordination required” shall be included in the DL-UNITDATA message for the downlink direction. CS/PS domain registration coordination may not be performed by the SGSN for the operator’s own subscribers. + +In addition the DL-UNITDATA message shall contain: + +- The Initial LLC-PDU received from the MS; +- The IMSI, if available; +- The Unconfirmed send state variable, if available. +- The Old Routing Area Identification as indicated by the MS in the Initial LLC-PDU or, +- The Attach Indicator in case the Initial LLC-PDU contains a GPRS attach (see 3GPP TS 24.008 [11]). + +If the DL-UNITDATA message containing the *Redirection Indication* IE is not related to the last attempted CN operator, then the BSS shall proceed as follows: + +- if the DL-UNITDATA message contains the Old Routing Area Identification and the BSS from this information (and from BSS internal configuration) is able to uniquely identify one of the CN operators in the shared network, then the BSS shall re-initiate the procedure towards the identified CN operator with the Selected Operator, Initial LLC-PDU, Redirect Attempt Flag, IMSI and Unconfirmed send state variable (if received from previously attempted CN operator) included in the UL-UNITDATA message; +- if the DL-UNITDATA message contains the Old Routing Area Identification and the BSS from this information (and from BSS internal configuration) cannot identify one of the CN operators in the shared network, then the BSS shall initiate the MS Registration Enquiry procedure in the CS domain (see 3GPP TS 48.008 [14]); +- if the DL-UNITDATA message contains the Attach Indicator then the BSS shall initiate the MS Registration Enquiry procedure in the CS domain (see 3GPP TS 48.008 [14]). + +NOTE: The configuration by means the BSS identifies a CN operator from the received Old Routing Area Identification is implementation dependent and under operator control. + +If, as a result of the MS Registration Enquiry procedure in the CS domain, the MS is found to be registered with one of the shared CN operators, then the BSS shall re-initiate the procedure towards the same CN operator with the *CS Registered Operator*, Initial LLC-PDU, Redirect Attempt Flag, IMSI and Unconfirmed send state variable (if received from previously attempted CN operator) included in the UL-UNITDATA message. + +If the MS is not found to be registered in the CS domain with any of the shared CN operators, then the BSS shall perform CS/PS domain registration coordination based on the received IMSI and re-initiate the procedure towards the SGSN of the identified CN operator with the *Selected Operator*, Initial LLC-PDU, Redirect Attempt Flag, IMSI and Unconfirmed send state variable (if received from previously attempted CN operator) included in the UL-UNITDATA message. + +Upon reception of the *Redirection Indication* IE, the BSS shall store as part of the Rerouting Function the associated Reroute Reject Cause and LLC-PDU related to this CN operator. + +In case all attempted CN operators have replied with a *Redirection Indication* IE, the BSS shall select the most appropriate Layer 3 Information received from the attempted CN operators based on the stored information as part of the Rerouting procedure and send it back to the MS (see 3GPP TS 24.008 [11]). + +### 6.7.3 Reroute complete + +If the selected CN operator accepts the initial request from the MS, then the SGSN shall respond to the BSS with the *Redirection Completed* IE, with the Outcome value field set to "MS is accepted" or "MS is already registered", and the Layer 3 Information LLC-PDU (e.g. GPRS Attach Accept) included in the DL-UNITDATA message. + +Upon reception of the UL-UNITDATA message containing the *CS Registered Operator* IE, the SGSN shall conclude the Rerouting procedure and include the *Redirection Completed* IE in the DL-UNITDATA message. + +Upon reception of the DL-UNITDATA message with the *Redirection Completed* IE included in the message, the BSS shall send the LLC-PDU to the MS and terminate the Rerouting procedure. + +### 6.7.4 Abnormal Conditions + +If the selected CN operator cannot serve the initial request from the MS and rerouting to another CN operator is not possible, then the SGSN shall send the DL-UNITDATA message to the BSS with the Outcome value field set to "MS is not accepted" within the *Redirection Completed* IE, and the Layer 3 Information LLC-PDU (e.g. GPRS Attach Reject) included in the message. + +If, as a result of the analysis of the DL-UNITDATA message, the MS Registration Enquiry procedure is initiated in the CS domain and the MSC does not support CS/PS coordination enhancements, then the BSS shall behave as if the MS is not registered with any of the CN operators of that MSC. + +--- + +## 7 Signalling procedures between GMM SAPs + +### 7.1 Paging procedure + +When an SGSN initiates the paging procedure for GPRS services as defined in 3GPP TS 24.008, it shall send one or more PAGING-PS PDUs to the BSS. + +When instructed by an MSC/VLR to initiate a paging procedure for non-GPRS services as defined in 3GPP TS 24.008, an SGSN shall send one or more PAGING-CS PDUs to the BSS. + +These paging PDUs shall contain the information elements necessary for the BSS to initiate paging for an MS within a group of cells. + +The SGSN provides an indication of the cells within which the BSS shall page the MS. The levels of resolution within one BSS are: all cells within the BSS, all cells on the BSS within one location area, all cells on the BSS within one routing area, and one BVCI (i.e. cell). A routing area, a location area, or a BSS area is associated with one or more NSEIs. If the cells in which to page the MS are served by several NSEIs then one paging PDU must be sent to each of these NSEIs. + +A paging PDU shall be used to generate the corresponding radio interface paging request message(s) to be transmitted at the appropriate time. + +It should be noted that each paging PDU relates to only one MS and therefore a BSS may pack pages for different MSs into the relevant 3GPP TS 24.008 or 3GPP TS 44.060 radio interface paging request messages. + +In the case of paging for non-GPRS services, the SGSN shall provide the MS's IMSI and DRX Parameters. The SGSN shall also include the Global CN-Id information element in the paging PDU when this information element is received from the MSC/VLR. The Global CN-Id information element is received from the MSC/VLR if paging using only the IMSI parameter as identifier of the MS is performed via the SGSN when the MSC/VLR applies intra domain connection of RAN nodes to multiple CN nodes as described in 3GPP TS 23.236. The BSS shall then buffer this information element until receiving the paging response from the MS in order to route the paging response to the correct MSC/VLR. + +In the case of paging for GPRS services, the SGSN shall provide the MS's IMSI. If DRX Parameters are available, the SGSN shall also provide the DRX Parameters. If eDRX Parameters are available, the SGSN shall also provide the eDRX Parameters (see sub-clause 7.1a). + +NOTE: The IMSI and the DRX Parameters enable the BSS to derive the paging population number. Paging without DRX parameters may require a considerable extension of the paging duration. + +An SGSN may provide the BSSGP with MS specific information, enabling a BSS to execute the paging procedure in an MS specific manner. This includes: + +- QoS Profile. The Precedence parameter is set by the upper layers (in the SGSN). The SGSN shall set the bit rate parameter to "best effort". The SGSN shall set the transmission mode to unacknowledged. The BSS shall ignore the received bit rate, the BSSGP SDU type, LLC type, and transmission mode parameters; +- PFI or an aggregate BSS QoS profile information which indicates if the page is for signalling, for SMS, for TOM8, for best-effort, or for a specific packet flow. The aggregate BSS QoS profile in this case is used for paging only and is not stored by the BSS. If both of the optional PFI and ABQP IEs are present, the ABQP takes precedence. +- the most recently received downlink Coverage Class and the cell identity for the cell where the Coverage Class was reported by the MS, if previously received from the BSS in the UL-UNITDATA PDU. +- MS Radio Access Capability defining the radio capabilities of the MS. If there is valid MS Radio Access Capability information known by the SGSN for the associated MS, the SGSN shall include it in the PAGING-PS PDU. Otherwise, the MS Radio Access Capability shall not be present. +- Paging Attempt Information consisting of Paging Attempt Count and Intended Number of Paging Attempts information. If Paging Attempt Information is provided then the Paging Attempt Count field shall be increased by one at each new paging attempt performed for delivering a packet data payload available for delivery. If the SGSN cannot determine the number of intended paging attempts the SGSN shall use the code point 0000 corresponding to 'Information not available'. + +If an SGSN provides a P-TMSI in a PAGING-PS PDU, then the BSS shall use the P-TMSI to address the MS. If the SGSN does not provide the P-TMSI in the PAGING-PS PDU, then the BSS shall use the IMSI to address the MS. + +If the BSS determines that the nominal paging group of the MS occurs too far into the future (e.g. the BSS is unable to buffer the paging request until the next occurrence of the nominal paging group for the indicated MS) it responds to the PAGING-PS PDU by sending a PAGING-PS-REJECT PDU to the SGSN and includes information indicating the time until the next paging occasion therein. + +If an SGSN provides a TLLI in a PAGING-CS PDU and a radio context identified by the TLLI exists within the BSS, then the paging request message shall be directly sent to the MS. If the SGSN does not provide the TLLI in the PAGING-CS PDU or if no radio context identified by the TLLI exists within the BSS, then the BSS shall use the TMSI, if provided in the PAGING-CS PDU, else the IMSI, to address the MS. + +The PAGING-CS PDU consists of the parameters described above for a PAGING-PS PDU (except the P-TMSI, PFI, ABQP and QoS profile parameters) and, optionally, some or all of the following parameters; TMSI, TLLI, Global CN-Id, Channel Needed and eMLPP-Priority. The Channel Needed and eMLPP-Priority information shall be handled transparently by the BSS. + +The SGSN may send the BSS a DUMMY-PAGING-PS PDU at any time to determine the time until the next paging occasion for the MS indicated therein. The BSS uses the information provided within the DUMMY-PAGING-PS PDU to calculate the time until the next paging occasion for the indicated MS and includes it within a DUMMY-PAGING-PS-RESPONSE PDU it sends back to the SGSN. + +A SGSN that supports Multilateration Timing Advance (MTA) procedure (see 3GPP TS 44.031 and 3GPP TS 43.059 [23]) shall not send a PAGING-PS PDU to a BSS if the MPM timer is running for the corresponding MS. Otherwise, if neither the MPM timer nor Ready timer is running it may send a PAGING-PS PDU indicating 'positioning event triggered' in response to receiving a location request (see sub-clause 8b.1). If the SGSN receives a corresponding page response it sends the BSS managing the serving cell a PERFORM-LOCATION-REQUEST PDU and starts the Ready timer. If the UL-UNITDATA PDU containing the page response includes the "MultilaterationTiming Advance", "MS Sync Accuracy" and "BTS Reception Accuracy Level" information elements the SGSN includes them in the PERFORM-LOCATION-REQUEST PDU it sends to the serving BSS. + +In case the network supports restricted use of enhanced coverage (see 3GPP TS 24.008 [46]), and the MS camps on a cell not supporting EC-GSM-IoT, the SGSN may at any time check the status of Enhanced Coverage Restriction (RestrictEC indication in 3GPP TS 24.008 [46]) obtained from HSS/HLR or retrieve the status from the stored MS context and include it in the PAGING-PS PDU (see sub-clauses 10.3.1 and 11.3.141) in order to inform the BSS about restriction on the use of enhanced coverage. The BSS relays the restriction information to the corresponding MS using PS domain paging procedures. + +## 7.1a Paging procedure for Extended Coverage and eDRX + +An SGSN may have any combination of uplink and downlink Coverage Class information (previously received from the BSS in an UL-UNITDATA PDU) and eDRX information (negotiated during NAS signalling) available for a given MS when it determines that paging is necessary for that MS. When sending a PAGING-PS PDU to a BSS to trigger paging for a given MS the SGSN shall include the most recently received Coverage Class information and the most recent eDRX value negotiated during NAS signalling for that MS. If the BVC-RESET procedure (see sub-clauses 8.4 and 11.3.84) is performed and indicates a change to the eDRX capability for a BSS, it shall not impact the most recent eDRX value negotiated during NAS signalling for that MS. + +In case the network supports restricted use of enhanced coverage (see 3GPP TS 24.008 [46]), and the MS camps on a cell supporting EC-GSM-IoT, the SGSN may at any time check the status of Enhanced Coverage Restriction (RestrictEC indication in 3GPP TS 24.008 [46]) obtained from HSS/HLR or retrieve the status from the stored MS context and include it in the PAGING-PS PDU (see sub-clauses 10.3.1 and 11.3.141) in order to inform the BSS about a restriction on the use of enhanced coverage. The BSS relays the restriction information to the corresponding MS using PS domain paging procedures. + +### 7.1a.1 Coverage Class and eDRX information available + +If uplink and downlink Coverage Class information and a negotiated eDRX value are available for the MS the SGSN sends the BSS a PAGING-PS PDU that indicates the available uplink and downlink Coverage Class information and the negotiated eDRX information. + +- If a cell in the area targeted for paging supports EC-GSM-IoT and eDRX the MS is paged on the EC-PCH of its EC\_CCCH\_GROUP using the indicated downlink Coverage Class and eDRX information (see 3GPP TS 45.002 [48]). +- If a cell in the area targeted for paging supports EC-GSM-IoT but not eDRX the MS is paged on the EC-PCH of its EC\_CCCH\_GROUP using the lowest eDRX cycle (see 3GPP TS 45.002 [48]) only if the PAGING-PS PDU indicates the lowest eDRX cycle. Otherwise the MS is not paged. +- If a cell in the area targeted for paging does not support EC-GSM-IoT the MS is paged on the PCH using the indicated eDRX information if the MS Radio Access Capability IE (see sub-clause 11.3.22) indicates that the MS supports GPRS/EGPRS. The MS is not paged if the MS Radio Access Capability IE indicates that the MS does not support GPRS/EGPRS. + +### 7.1a.2 Coverage Class information not available, eDRX information available + +If uplink and downlink Coverage Class information is not available but a negotiated eDRX value is available for the MS the SGSN sends the BSS a PAGING-PS PDU that indicates the negotiated eDRX information. The MS is paged on the PCH, using the indicated eDRX information, in the cell(s) in the area targeted for the paging. + +### 7.1a.3 Coverage Class information available, eDRX information not available + +If uplink and downlink Coverage Class information is available but a negotiated eDRX value is not available for the MS the SGSN sends the BSS a PAGING-PS PDU that indicates the available Coverage Class and DRX information (if available). + +- If a cell in the area targeted for paging supports EC-GSM-IoT the MS is paged on the EC-PCH of its EC\_CCCH\_GROUP (see 3GPP TS 45.002 [32]) using the indicated downlink Coverage Class information and the lowest eDRX cycle. +- If a cell in the area targeted for paging does not support EC-GSM-IoT the MS is paged on the PCH using DRX (the SGSN may include DRX information in the PAGING-PS PDU) if the MS Radio Access Capability IE indicates that the MS supports GPRS/EGPRS. The MS is not paged if the MS Radio Access Capability IE indicates that the MS does not support GPRS/EGPRS. + +## 7.1b Paging Procedure for Extended Coverage with Paging Indication + +If the downlink Coverage Class information included in the PAGING-PS PDU indicates CC3 or CC4 and the MSRAC capability indicates that the MS supports monitoring of the EC-PICH, the BSS triggers for cells in the area targeted for + +paging and broadcasting the support of EC-PICH, the sending of a paging indication in the EC-PICH block, corresponding to the paging block for the paging group of the MS, before scheduling the paging message in the paging block. If the MSRAC capability does not indicate support for EC-PICH monitoring, the BSS does not trigger the sending of a paging indication before scheduling the paging message for the MS. + +## 7.2 Radio Access Capability Update procedure + +The BSS may request an MS's current Radio Access capability and/or its IMSI by sending to an SGSN a RA-CAPABILITY-UPDATE PDU which includes the TLLI of the MS and a Tag. The allocation of the Tag is implementation specific. The BSS then starts timer T5. + +The SGSN shall respond by sending a RA-CAPABILITY-UPDATE-ACK PDU which includes the TLLI of the MS, the Tag received in the corresponding RA-CAPABILITY-UPDATE PDU, and an RA-Cap-UPD-Cause field; the IMSI of the MS is also included when known. The BSS shall stop timer T5. + +If the RA-Cap-UPD-Cause is set to "OK", then an MS Radio Access Capability field and the IMSI shall be present. The received MS's radio access capability, if valid, shall then replace any radio access capability previously associated with the MS. If the RA-Cap-UPD-Cause is not set to "OK", then neither the MS Radio Access Capability nor the IMSI shall be present in the RA-CAPABILITY-UPDATE-ACK PDU. + +### 7.2.1 Abnormal conditions + +If an SGSN receives a RA-CAPABILITY-UPDATE PDU which includes an unknown TLLI, it shall answer with a RA-CAPABILITY-UPDATE-ACK PDU which includes the RA-CAP-UPD-Cause set to the value "TLLI unknown". + +If an SGSN receives a RA-CAPABILITY-UPDATE PDU which includes a known TLLI, but there are no Radio Access parameters or IMSI known to the SGSN for the associated MS, the SGSN shall reply to the request with a RA-CAPABILITY-UPDATE-ACK PDU in which the RA-CAP-UPD-Cause is set to: "no RA capability or IMSI available". + +If a BSS receives a RA-CAPABILITY-UPDATE-ACK PDU containing a Tag which is different from the last transmitted Tag by the BSS, it shall ignore the reception of this PDU. + +If a BSS sends a RA-CAPABILITY-UPDATE PDU to an SGSN and the RA-CAPABILITY-UPDATE-ACK is not returned within a period T5 with the same Tag value as provided in the request, the RA-CAPABILITY-UPDATE procedure shall be repeated a maximum of RA-CAPABILITY-UPDATE-RETRIES attempts. The Tag value shall be changed by the BSS at each new retry. + +## 7.3 Radio Status procedure + +A BSS and an MS radio interface communication status may change due to the following: + +- 1) the MS goes out of coverage and is lost; + +This condition is signalled by setting the Radio Cause value to "Radio contact lost with MS". + +- 2) the link quality is too bad to continue the communication; + +This condition is signalled by setting the Radio Cause value to "Radio link quality insufficient to continue communication". + +- 3) the BSS has ordered the MS to perform a cell reselection. + +This condition is signalled by setting the Radio Cause value to "Cell reselection ordered". + +- 4) the BSS is preparing to order the MS to perform a cell-reselection to a new cell and internal re-routing of packets to the new cell is not possible. + +This condition is signalled by setting the Radio Cause value to "Cell reselection preparation". + +- 5) the BSS has detected that the packet cell change order has failed. + +This condition is signalled by setting the Radio Cause value to "Cell reselection failure". + +Conditions 1) and 2) indicate that attempts to communicate between an MS and an SGSN via this cell should be suspended or abandoned. An SGSN shall stop sending LLC-PDUs to the cell for the MS. The criteria for deciding whether condition 1) or 2) has occurred is not in the scope of the present document. + +The conditions for resuming a suspended or abandoned communication between an MS and SGSN are defined in 3GPP TS 24.008. + +Condition 3) indicates that the SGSN should wait for a cell update before resuming the transmission of LLC-PDUs to the BSS. + +Condition 4) indicates that the SGSN shall suspend downlink transmission of LLC-PDUs. This condition shall only be signalled if the Enhanced Radio Status feature has been negotiated. For this condition the SGSN shall wait for either: + +- a) a cell update from the MS in a new Cell . In this case the SGSN should resume downlink transmission in the new Cell. +- b) or a new RADIO-STATUS PDU from the BSS with a different Radio Cause value. In this case the SGSN should follow the procedures specified for that Radio Cause value. + +Condition 5) indicates that the SGSN shall resume the transmission of LLC-PDUs to the BSS in case the downlink transmission has been suspended. This condition shall only be signalled if the Enhanced Radio Status feature has been negotiated. A BSS shall signal these exception conditions to an SGSN by sending a RADIO-STATUS PDU. It shall contain a reference to the MS, either TLLI or TMSI or IMSI, and an indication of the exception condition, i.e. the Radio Cause value. + +After receipt of a RADIO-STATUS PDU with cause value indicating Condition 1-4, the SGSN may try to locate the mobile station in case any downlink LLC PDU needs to be sent to the mobile station, as it can not expect to receive systematically an uplink LLC PDU from the mobile station or a RADIO-STATUS PDU with cause value indicating Condition 5 from the BSS to resume the downlink transfer. To this avail, the SGSN should send a PAGING-PS PDU towards the mobile station. + +## 7.4 SUSPEND procedure + +If the MS signals to the BSS that it wishes its GPRS service to be suspended, the BSS shall send a SUSPEND PDU to the SGSN and start timer T3. Actions within the SGSN while an MS is suspended are not specified, but paging is typically stopped. The SUSPEND PDU contains: + +- the TLLI of the MS; and +- the Routeing Area of the MS as received in the Layer 3 Um interface message GPRS Suspension Request (see 3GPP TS 44.018). + +For each SUSPEND PDU received by an SGSN, a SUSPEND-ACK PDU shall be returned to the BSS. Upon reception of the SUSPEND-ACK PDU, the BSS shall stop T3. The SUSPEND-ACK PDU contains: + +- the TLLI of the MS as received in the SUSPEND PDU; +- the Routeing Area of the MS as received in the SUSPEND PDU; and +- the Suspend Reference Number. + +The SGSN generates the Suspend Reference Number in a manner that it enables it to differentiate between different SUSPEND PDUs relating to the same MS. + +### 7.4.1 Abnormal conditions + +If a SUSPEND-ACK PDU is not received for a SUSPEND PDU within T3 seconds, then the SUSPEND PDU procedure shall be repeated a maximum of SUSPEND-RETRIES attempts. After SUSPEND-RETRIES attempts the procedure is stopped and the O&M system is informed. + +If a SUSPEND-ACK PDU is received for an MS that is already marked as suspended, then the SUSPEND-ACK PDU is ignored. + +If a SUSPEND PDU refers to an MS which is unknown in the SGSN, then a SUSPEND-NACK PDU is returned containing a cause value (Cause value: Unknown MS). The BSS shall stop the SUSPEND procedure. + +If the Suspend procedure is supported on the Gn interface, in case of an inter-SGSN suspend procedure the MS shall not be treated as unknown in the SGSN when the RA indicated in the SUSPEND PDU is not served by the SGSN. + +## 7.5 RESUME procedure + +When the reason why a GPRS-attached MS was suspended disappears, i.e.: + +- it leaves dedicated mode, disconnecting the MS from the MSC; or +- it is handed over to a cell that supports DTM; + +the BSS shall either a) instruct the MS to initiate the Routeing Area Update procedure, or b) signal to the SGSN that an MS's GPRS service shall be resumed. + +If the BSS executes a), then no further action is required. + +If the BSS executes b), then the BSS shall send a RESUME PDU containing the same Suspend Reference Number received in the SUSPEND-ACK PDU to the SGSN and start timer T4. The RESUME PDU contains: + +- the TLLI of the MS; +- the Routeing Area of the MS; and +- the Suspend Reference Number. + +For each RESUME PDU received by an SGSN, a RESUME-ACK PDU shall be returned to the BSS. Upon reception of the RESUME-ACK PDU, the BSS shall stop T4. The RESUME-ACK PDU contains: + +- the TLLI of the MS; and +- the Routeing Area of the MS. + +### 7.5.1 Abnormal conditions + +If a RESUME-ACK PDU is not received for a RESUME PDU within T4 seconds, then the RESUME PDU procedure shall be repeated a maximum of RESUME-RETRIES attempts. After RESUME-RETRIES attempts the procedure is stopped, the O&M system is informed and the MS shall be instructed to initiate the Routeing Area Update procedure. + +If a RESUME-ACK PDU is received for an MS that is not suspended, then the RESUME-ACK PDU is ignored. + +If a RESUME PDU refers to an MS which is unknown in the SGSN, then a RESUME-NACK PDU is returned containing a cause value (Cause value: Unknown MS). The BSS shall stop the RESUME procedure and the MS shall be instructed to initiate the Routeing Area Update procedure. + +## 7.6 MS Registration Enquiry + +### 7.6.1 General + +This procedure shall be supported by a BSS if it supports CS/PS coordination enhancements in a MOCN configuration (see sub-clause 6.6) or in a GWCN configuration (see sub-clause 6.7). + +The purpose of the MS Registration Enquiry procedure is to acquire registration information for a given MS from the core network. More precisely, triggered e.g. by the Rerouting procedure in the CS domain (see 3GPP TS 48.008 [14]), the BSS sends an enquiry to the SGSN(s) whether a given MS is already registered with any of the core network operators in the shared network. + +### 7.6.2 Registration enquiry + +The MS Registration Enquiry procedure is triggered by the BSS sending the MS REGISTRATION ENQUIRY message to the SGSN containing the IMSI for the MS for which the registration enquiry concerns. + +To avoid a possible change of serving operator when the MS performs inter-RAT mobility from E-UTRAN to GERAN (see 3GPP TS 23.251 [43]), the MS registration enquiry may also need to be sent from the SGSN to the MME of the + +same CN operator. For this reason the BSS includes the MME Query indicator in the MS REGISTRATION ENQUIRY message. + +The MS REGISTRATION ENQUIRY message is sent to each SGSN connected to the BSS. However, in order to minimise the signalling in the core network, the MME Query indicator shall only be included in one of the MS REGISTRATION ENQUIRY messages addressing the same CN operator. + +The SGSN responds with the MS REGISTRATION ENQUIRY RESPONSE message indicating whether the MS is served by (one of) the CN operator(s) sharing the network. + +### 7.6.3 Registration response + +If the MS is found to be registered with (one of) the CN operator(s) sharing the network, the SGSN shall return the MS REGISTRATION ENQUIRY RESPONSE message to the BSS with the IMSI and the PS Registered Operator IE (containing the serving CN operator) included in the message. + +If the MS is not registered with (any of) the sharing CN operator(s), the SGSN excludes the PS Registered Operator IE from the MS REGISTRATION ENQUIRY RESPONSE message. + +Upon reception of the MS REGISTRATION ENQUIRY RESPONSE message with the PS Registered Operator IE included in the message, the BSS may terminate the MS Registration Enquiry procedure regardless if one or more SGSNs have not yet responded to the MS REGISTRATION ENQUIRY message. + +--- + +## 8 Signalling procedures between NM SAPs + +### 8.1 FLUSH-LL (logical link) procedure + +When an SGSN detects a cell change of an MS from a cell update or a routing area update, the SGSN shall send a FLUSH-LL PDU to the old BVC to initiate the following procedures: + +- at a cell change within one NSE (e.g. the BSS is a NSE) and within one routing area, LLC-PDU(s) for a given TLLI stored at an "old" BVCI (corresponding to the old cell) are either deleted or transferred to a "new" BVCI (corresponding to the new cell) with which the TLLI is currently associated; or +- at a cell change between two NSEs within one routing area, LLC PDU(s) for a given TLLI stored at an "old" BVCI (corresponding to the old cell) are either deleted or transferred to a "new" BVCI (corresponding to the new cell) with which the TLLI is currently associated. In that case, transferring of LLC PDU(s) can only be requested by the SGSN if the NSE underlying the "old" BVCI indicated support for the "Inter-NSE re-routing"; +- at a cell change within the same routing area, and within one NSE or between two NSEs, the on-going location procedure, if any, is either maintained in the BSS after the cell reselection or aborted by the BSS towards the SMLC; or +- at a cell change between two routing areas, LLC-PDU(s) stored at the "old" BVCI for the TLLI are deleted. + +The SGSN provides the BSSGP with: + +- a MS's TLLI identifying the MS; +- the "old" BVCI identifying the cell in which to find buffered LLC-PDU(s) for the MS; +- the "new" BVCI identifying the cell to which the MS is currently associated (only when within the same routing area); and +- if the SGSN supports "Inter-NSE re-routing" or "LCS Procedures" and the old NSE supports the "Inter-NSE re-routing" or "LCS Procedures", the "new" NSEI identifying the cell to which the MS is currently associated (only when within the same routing area but between two NSEs). The NSEI associated to the "old" BVCI shall be assumed if the "new NSEI" field is not provided. + +If there is a BSS context for the MS in the "old" BVCI and there is a "new" BVCI in the FLUSH-LL PDU, the BSS shall interpret this as a request to transfer the BSS context to the new cell. The BSS shall assume that the ABQP that was negotiated for each PFC in the "old" BVCI is requested in the "new" BVCI by the SGSN. Also, the values of the Packet Flow Timer and the Service UTRAN CCO Information Elements should be kept for each + +transferred PFC. If, when receiving the BSS context at the "new" BVCI, the BSS has already obtained the information related to one or several PFC(s) from the SGSN by means of the Create BSS PFC procedure (see sub-clause 8a.1), then the BSS shall disregard the information corresponding to this (these) PFC(s) within the BSS context transferred from the "old" BVCI. If a Create BSS PFC procedure is ongoing when receiving the BSS context at the "new" BVCI, the BSS shall either apply the received information or carry on with the currently used ABQP until the procedure completes. + +If a "new" BVCI is not provided, then the FLUSH-LL PDU shall be interpreted as an instruction to delete the queued LLC-PDU(s) at the old BVC, and also to delete the BSS context associated to the MS identified by the TLLI, if any exists in the "old" BVCI. + +Queued BSSGP signalling, e.g. pages, shall not be affected by this procedure. + +In response to a FLUSH-LL PDU the BSS shall send a FLUSH-LL-ACK PDU to the SGSN containing: + +- the TLLI received in the FLUSH-LL PDU; +- an indication of whether the LLC-PDU(s) were "transferred" or "deleted". In case the SDUs were "transferred" the BVCI (new) IE, and the NSEI (new) IE if present in the FLUSH-LL PDU, shall be included; +- the number of octets that have been transferred or deleted. + +NOTE: In situations where the BSS was unable to transfer the queued LLC-PDUs upon a transfer request from the SGSN, the BSS may indicate in the FLUSH-LL-ACK PDU a flush action set to "deleted" together with the number of octets actually deleted. + +On receipt of a FLUSH-LL-ACK PDU by the SGSN, indicating that the LLC-PDU(s) associated with the old BVC have been "deleted", the SGSN may choose to: + +- immediately retransmit all unacknowledged LLC-PDU(s) (in acknowledged LLC operation) to the MS at the new BVC (i.e. new cell); or +- rely on LLC retransmission mechanism to transmit unacknowledged LLC-PDU(s). + +On receipt of a FLUSH-LL-ACK PDU by the SGSN, indicating that the LLC-PDU(s) associated with the old BVC have been "transferred", the SGSN shall not take any of the above actions. + +If the "new" BVCI could not accept the QoS characteristics of all PFCs of the BSS context, the BSS context shall still be transferred and the BSS shall then initiate in the "new" BVCI a Modify BSS PFC procedure for each PFC for which the requested ABQP could not be accepted. The BSS may resume the transfer of downlink LLC PDU(s) before the Modify BSS PFC procedure is completed. + +In order to avoid desequencing DL LLC PDU (in LLC acknowledged or unacknowledged operation) during the FLUSH procedure, upon sending a FLUSH-LL PDU to the BSS requesting the rerouting of DL LLC PDUs to a new cell, the SGSN should wait for the receipt of the FLUSH-LL-ACK PDU or rely on an internal guard timer, before starting to transmit subsequent DL LLC PDUs on the new BVCI. In the case the SGSN does not request the BSS to reroute DL LLC PDUs to a new cell, it may immediately resume the transmission of subsequent DL LLC PDUs on the new BVCI, or start the Create BSS PFC procedure, without waiting for the receipt of the FLUSH-LL-ACK PDU. + +### 8.1.1 Abnormal Conditions + +If the BSS receives a FLUSH-LL PDU for an unknown BVCI or TLLI not associated with the given BVCI, then the FLUSH-LL PDU is discarded and no FLUSH-LL-ACK PDU is returned. + +If the SGSN does not receive a FLUSH-LL-ACK PDU in response to a FLUSH-LL PDU, no further action is taken. + +## 8.2 Flow Control procedure + +### 8.2.1 General model of operation + +From the perspective of the BSSGP, the flow control mechanism is based on the following model: + +- there is a downlink buffer for each BVC, as identified by a BVCI, in a BSS; +- the transfer of BSSGP UNITDATA PDUs for an MS from the SGSN is controlled by the BSS; and + +- only downlink BSSGP UNITDATA PDU transfer to the BSS is managed via flow control procedures. Uplink flow control is not performed. + +## 8.2.2 Mode of operation + +The flow control mechanism manages the transfer of BSSGP UNITDATA PDUs sent by the SGSN on the Gb interface to the BSS. + +The BSS shall control the flow of BSSGP UNITDATA PDUs to its BVC buffers by indicating to the SGSN the maximum allowed throughput in total for each BVC. The BSS shall control the flow of BSSGP UNITDATA PDUs to the BVC buffer for an individual MS by indicating to the SGSN the maximum allowed throughput for a certain TLLI. If the PFC Flow Control feature is negotiated, the BSS may control the flow of BSSGP UNITDATA PDUs to the BVC buffer for a certain PFC of an individual MS by indicating to the SGSN the maximum allowed throughput for a certain PFI. + +If the Gigabit Interface feature has been negotiated, the granularity of the Flow Control related information elements such as the *BVC Bucket Size* IE, the *BVC Bucket Leak Rate* IE and the *PFC flow control parameters* IE shall be indicated through the *Flow Control Granularity* IE included in the same PDU (see sub-clauses 10.4.4, 10.4.6 and 10.4.24). + +The BSS uses flow control to adjust the flow of BSSGP UNITDATA PDUs to a BVC buffer. The amount of buffered BSSGP UNITDATA PDUs in the BSS should be optimised to efficiently use the available radio resource. The volume of buffered BSSGP UNITDATA PDUs for a BVC or MS or PFC should be low. BSSGP UNITDATA PDUs queued within the BSS that are not transferred across the radio interface before the PDU Lifetime expires shall be locally deleted from the BSS. The local deletion of BSSGP UNITDATA PDUs in the BSS shall be signalled to the SGSN by the transmission of a LLC-DISCARDED PDU. + +For each FLOW-CONTROL PDU received by an SGSN, a confirmation shall always be sent across the Gb interface by the SGSN. The confirmation uses the Tag that was received in the FLOW-CONTROL PDU, which was set by the BSS to associate the response with the request. When receiving no confirmation to a FLOW-CONTROL PDU, the reasons that gave rise to the triggering of a flow control message may trigger another message, or, if the condition disappears, it may not. For the repetition of non-confirmed FLOW-CONTROL PDUs, the maximum repetition rate still applies in the BSS. + +## 8.2.3 Flow Control of Traffic from an SGSN to BSS + +### 8.2.3.1 Control of the downlink throughput by the SGSN + +The principle of the BSSGP flow control procedures is that the BSS sends to the SGSN flow control parameters which allow the SGSN to locally control its transmission output in the SGSN to BSS direction. The SGSN shall perform flow control on each BVC, on each MS and optionally on each PFC for an MS. The flow control is performed on each LLC-PDU first by the PFC flow control mechanism if applicable and if negotiated, then by the MS flow control mechanism and then by the BVC flow control mechanism. + +If the PFC Flow Control feature has been negotiated and the LLC-PDU corresponds to a PFC for which the SGSN has received some flow control parameters, then the SGSN has to check that the LLC-PDU is passed by the individual PFC flow control. If it is passed or if the PFC flow control has not been negotiated, or if it has been negotiated but no flow control parameter has been received for the PFC corresponding to the LLC-PDU, the SGSN applies the MS flow control. If passed, the SGSN finally applies the BVC flow control to the LLC-PDU. If an LLC-PDU is passed by all flow control mechanisms, the entire LLC-PDU is delivered to the Network Services for transmission to the BSS (see figure 8.1). + +![Diagram illustrating the BSSGP Flow control hierarchy. At the top, multiple 'PFC Flow control' blocks are shown, each receiving an input from above. Below these, multiple 'MS Flow control' blocks are shown. Arrows indicate that traffic from each 'PFC Flow control' block is passed to the corresponding 'MS Flow control' block. At the bottom, a single 'BVC Flow control' block receives traffic from all 'MS Flow control' blocks. The final output from the 'BVC Flow control' block is labeled 'BSS'.](b774dfc5023e15e9c352b97ca25a56d4_img.jpg) + +``` +graph TD; PFC1[PFC Flow control] --> MS1[MS Flow control]; PFC2[PFC Flow control] --> MS2[MS Flow control]; PFCn[PFC Flow control] --> MSn[MS Flow control]; MS1 --> BVC[BVC Flow control]; MS2 --> BVC; MSn --> BVC; BVC --> BSS[BSS]; +``` + +Diagram illustrating the BSSGP Flow control hierarchy. At the top, multiple 'PFC Flow control' blocks are shown, each receiving an input from above. Below these, multiple 'MS Flow control' blocks are shown. Arrows indicate that traffic from each 'PFC Flow control' block is passed to the corresponding 'MS Flow control' block. At the bottom, a single 'BVC Flow control' block receives traffic from all 'MS Flow control' blocks. The final output from the 'BVC Flow control' block is labeled 'BSS'. + +**Figure 8.1: BSSGP Flow control** + +The flow control parameters sent by the BSS to the SGSN consist of the following information: + +- the bucket size (Bmax) for a given BVC or MS or PFC in the downlink direction; and +- the bucket leak rate (R) for a given BVC or MS or PFC in the downlink direction; and +- the bucket full ratio for a given BVC or MS or PFC in the downlink direction, if the Current Bucket Level (CBL) feature is negotiated. + +NOTE: The information for a given PFC is only received if the PFC flow control feature is negotiated. + +The SGSN shall perform flow control on an individual MS using SGSN determined values of Bmax and R unless it receives a FLOW-CONTROL-MS PDU from the BSS regarding that MS. The SGSN shall continue to perform flow + +control for a particular MS using the Bmax and R values received from the BSS for at least Th seconds after receiving a FLOW-CONTROL-MS PDU from the BSS regarding that MS. When timer Th has expired or when the MS changes cells, the SGSN may reinitialise the SGSN internal flow control variables for that MS and begin to use SGSN generated values for Bmax and R. + +The SGSN shall start performing flow control on a given PFC for an individual MS as soon as it receives the first FLOW-CONTROL-PFC PDU for that PFC and the feature has been negotiated; it shall stop applying PFC flow control for a given PFC of an individual MS as soon as it receives subsequently a FLOW-CONTROL-MS PDU for that MS or if more than Tf seconds have elapsed since the last FLOW-CONTROL-PFC PDU was received for that PFC. When the MS changes cells, the SGSN shall stop performing flow control per PFC, until it receives a FLOW-CONTROL-PFC PDU. + +In case the MS flow control parameters needs to be updated and the PFC flow control feature is negotiated and the PFC flow control parameters for that MS remains unchanged then the FLOW-CONTROL-PFC PDU is used by the BSS to update the MS flow control parameters. The "Number of PFCs" IE within the "PFC Flow Control parameters" IE shall be set to "0" in this case. + +The BSSGP flow control model is the algorithm shown in Figure 8.2. The model of the algorithm is that an LLC-PDU is passed by the algorithm as long as the bucket counter (B) plus the length of the LLC-PDU does not exceed the bucket size Bmax. When the LLC-PDU is passed, the LLC-PDU length is added to B. Any PDU not transmitted is delayed until B plus the LLC-PDU length is less than Bmax. + +### 8.2.3.2 Flow Control Conformance Definition + +A BSSGP flow control algorithm shall be implemented in the SGSN. The BSSGP flow control conformance algorithm is defined in figure 8.2. + +The conformance definition is used to decide which LLC-PDUs are conforming to the flow to the PFC of an MS, to an MS or in a BSSGP virtual connection (BVC) over the Gb interface. The conformance definition should not be interpreted as the required implementation algorithm, as the SGSN manufacturer may use any algorithm as long as the operation of the BSSGP flow control does not violate the objectives of compliant BVCs or MSs or PFC. That is, the SGSN shall never transmit more data than can be accommodated within the BSS buffer for a BVC or individual MS or for a given PFC of an MS. + +![Flowchart of the Conformance Definition Algorithm for BSSGP Flow Control. It starts with the arrival of an LLC PDU p with length L(p) at time Tc. A calculation block computes B* = B + L(p) - (Tc - Tp) x R. A decision diamond checks if B* < L(p). If yes, B is set to L(p). If no, a second decision diamond checks if B* > Bmax. If yes, the LLC PDU is delayed. If no, B is set to B*. Both B assignment paths lead to setting Tp = Tc and then passing the LLC PDU.](87b70d2e8951032d28b4412d82cf1413_img.jpg) + +``` + + graph TD + Start[Arrival of LLC PDU p with +length L(p) at time Tc] --> Calc["B* = B + L(p) - (Tc - Tp) x R"] + Calc --> Decision1{"B* < L(p)?"} + Decision1 -- yes --> SetB1["B = L(p)"] + Decision1 -- no --> Decision2{"B* > Bmax?"} + Decision2 -- yes --> Delay[Delay LLC PDU] + Decision2 -- no --> SetB2["B = B*"] + SetB1 --> SetTp["Tp = Tc"] + SetB2 --> SetTp + SetTp --> Pass[Pass LLC PDU] + +``` + +Flowchart of the Conformance Definition Algorithm for BSSGP Flow Control. It starts with the arrival of an LLC PDU p with length L(p) at time Tc. A calculation block computes B\* = B + L(p) - (Tc - Tp) x R. A decision diamond checks if B\* < L(p). If yes, B is set to L(p). If no, a second decision diamond checks if B\* > Bmax. If yes, the LLC PDU is delayed. If no, B is set to B\*. Both B assignment paths lead to setting Tp = Tc and then passing the LLC PDU. + +**Figure 8.2: Conformance Definition Algorithm for BSSGP Flow Control** + +The variables used by the algorithm are: + +Bmax Bucket Size. Set by the BSS for each cell and each mobile station and optionally for each PFC of an MS. Bmax shall be large enough to accommodate at least one LLC-PDU; + +| | | +|----------------|-------------------------------------------------------| +| R | leak rate of the bucket; | +| B | bucket counter; | +| B* | predicted value of the bucket counter; | +| L(p) | length of LLC-PDU p; | +| T p | the time that the last LLC-PDU p was transferred; and | +| T c | arrival time of LLC-PDU p. | + +The initial conditions of these variables in the SGSN are: + +- Bmax = 0 for BVCs or MSs. For BVCs, this value is valid until Bmax is received in the FLOW-CONTROL-BVC. For MSs, this value is valid until Bmax\_default\_MS is received in the FLOW-CONTROL-BVC PDU. Thereafter, sub-clause 8.2.3.6, shall apply; +- Bmax = 0 for PFCs until a FLOW-CONTROL-BVC PDU is received for the cell in which the PFC is running. Thereafter, Bmax for a PFC shall not be greater than Bmax of the corresponding MS until PFC flow control applies for the PFC. As long as PFC flow control applies, Bmax shall then not be greater than the value of Bmax provided in the latest valid FLOW-CONTROL-PFC PDU ; +- R = 0 for BVC or MSs. For a BVC, this value is valid until a FLOW-CONTROL-BVC PDU is received. For an MS, this value is valid until a FLOW-CONTROL-BVC PDU is received. Thereafter, sub-clause 8.2.3.6 shall apply; +- R = 0 for PFCs until a FLOW-CONTROL-BVC PDU is received for the cell in which the PFC is running. Thereafter, R for a PFC shall not be greater than R of the corresponding MS until PFC flow control applies for the PFC. As long as PFC flow control applies, R shall then not be greater than the value of R provided in the latest valid FLOW-CONTROL-PFC PDU ; +- B = 0 (the bucket is empty); and Tp = the current time for the first LLC-PDU. + +The SGSN shall not transmit a LLC-PDU on a BVC until a FLOW-CONTROL-BVC PDU is received from the BSS for that BVC. + +When a LLC-PDU p arrives at current time Tc, the variable B\* is set to the predicted bucket size if the LLC-PDU were to be transferred to the BSS. This is given by the previous bucket size plus the new LLC-PDU size, $B^* = B + L(p)$ , less the amount that the bucket will have leaked away since the last compliant LLC-PDU, $R \times (T_c - T_p)$ . If this is less than L(p) then the LLC-PDU is compliant and the bucket size B is reset to L(p) and the LLC-PDU is passed. When a compliant LLC-PDU is passed the last LLC-PDU transfer time is set to the current time, Tp = Tc. + +If the bucket has not completely leaked away then the bucket has to be checked to see if the limit Bmax is going to be exceeded, $B^* > B_{max}$ . If the limit is exceeded then the LLC-PDU is non compliant and is delayed for some time period, and no updates are done on the variables. If the bucket limit Bmax is not exceeded then the LLC-PDU is compliant and the bucket counter (B) is set equal to the value of B\*. When a conforming LLC-PDU is passed then the last LLC-PDU transfer time is set to the current time, Tp = Tc. + +On receipt of a FLUSH-LL-ACK PDU by the SGSN, indicating that the LLC-PDU(s) associated with the old BVC have been "deleted", the SGSN should update the value of the bucket counter (B) for the MS and for the old BVC, $B = \max(B - N, 0)$ . N is provided by FLUSH-LL-ACK PDU, indicating the number of octets deleted by the BSS. + +On receipt of a FLUSH-LL-ACK PDU by the SGSN, indicating that the LLC-PDU(s) associated with the old BVC have been "transferred" within the NSE, the SGSN should update the value of the bucket counter (B) for the old BVC, $B = \max(B - N, 0)$ . The value of B for the new BVC should also be updated, $B = \min(B + N, B_{max})$ . N is provided by FLUSH-LL-ACK PDU, indicating the number of octets transferred by the BSS. + +On receipt of a LLC-DISCARDED PDU by the SGSN, indicating that the LLC-PDU(s) associated with the MS or the PFC of an MS have been locally deleted by the BSS, the SGSN should update the value of the bucket counter (B) for the MS or the PFC and for the BVC, $B = \max (B - N, 0)$ . N is provided by LLC-DISCARDED PDU, indicating the number of octets deleted by the BSS. + +The BSS may update the values of Bmax and R within the SGSN at any time by transmitting a new Flow Control PDU containing the new Bmax and R values. The variables B, B\*, Tp and Tc are local to the SGSN and are not affected by the reception of a Flow-Control-BVC or Flow Control-MS PDU. + +If the Current Bucket Level (CBL) feature is negotiated, the SGSN shall update the variable B based upon the Bucket\_Full\_Ratio information element received in the Flow Control PDU. During the time period when SGSN does not receive a Flow Control PDU, it shall continue computing the bucket counter (B) as defined above. + +### 8.2.3.3 Response time within the SGSN to flow control messages + +Upon reception of flow control requests from a BSS, the SGSN shall modify its downlink transmission as instructed within 100 ms. + +### 8.2.3.4 Frequency of sending BVC or MS or PFC Flow Control PDUs + +The rate at which the BSS is allowed to send flow control PDUs for a given BVC or MS or PFC is limited and defined by the following rule: the BSS may send a new Flow Control PDU every C seconds, where C is a value which is pre-defined and common to the BSS and SGSN. + +If the BSS detects a missing FLOW-CONTROL-ACK PDU from the SGSN and the condition which causes the sending of a FLOW-CONTROL PDU still remains, the FLOW-CONTROL PDU may be retransmitted immediately. In this case the BSS may violate the repetition rate defined by the C value. + +After a BVC reset procedure, the BSS may send a BVC-BLOCK PDU. Otherwise, the BSS shall send a BVC-FLOW-CONTROL PDU. When the blocked BVC is unblocked, a BVC-FLOW-CONTROL PDU shall be sent. + +### 8.2.3.5 FLOW-CONTROL PDUs + +Based on the criteria for flow control, a BSS shall send to an SGSN a FLOW-CONTROL PDU containing a list of IEs. + +For BVC Flow Control, the following information is sent: + +- the maximum bucket size (Bmax) for the BVC on the Gb Interface; +- the leak rate parameter (R) to be applied to the bucket; +- the bucket full ratio to resynchronize the bucket counter for the BVC, if the Current Bucket Level (CBL) feature is negotiated; +- the default MS bucket size (Bmax\_default\_MS); +- the default MS leak rate (R\_default\_MS); and +- the optional measurement of the delay for PDU delivery inside that BVC. + +For MS Flow Control, the following information is sent: + +- the TLLI identifying the MS; +- the maximum bucket size (Bmax) for this MS on the Gb interface; +- the leak rate parameter (R) to be applied to the bucket; and +- the bucket full ratio to resynchronize the bucket counter for the MS, if the Current Bucket Level (CBL) feature is negotiated. + +For PFC Flow Control, the following information is sent: + +- the TLLI identifying the MS; +- the maximum bucket size (Bmax) for this MS on the Gb interface (optional); + +- the leak rate parameter (R) to be applied to the bucket (optional); + - the bucket full ratio to resynchronize the bucket counter for the MS, if the Current Bucket Level (CBL) feature is negotiated (optional); + - the number of PFCs for which flow control parameters are included; +- for each PFC: +- the PFI identifying the PFC for that MS; + - the maximum bucket size (Bmax) for this PFC on the Gb interface; + - the leak rate parameter (R) to be applied to the bucket; + - the bucket full ratio to resynchronize the bucket counter for the PFC, if the Current Bucket Level (CBL) feature is negotiated. + +NOTE: The supply of the MS flow control parameters inside the FLOW-CONTROL-PFC PDU allows the SGSN utilising the most up-to-date parameters both for PFC and MS flow control. Also, because the receipt of a FLOW-CONTROL-MS PDU notifies the end of PFC flow control for a given MS, if the MS flow control parameters have changed since the last update, then it is necessary to provide the MS flow control parameters inside the FLOW-CONTROL-PFC PDU. + +### 8.2.3.6 Condition of Bmax for MS after Initial Flow-Control-BVC + +The SGSN may use the following (informative) equation to generate an initial bucket size, Bmax, for an MS. + +$$\text{Bmax (bits)} = \min \begin{pmatrix} \text{R\_default\_MS for 1 s, 72 000, max MS throughput for 1 s,} \\ \text{(max MS throughput for 1 s + current throughput of all other MSs in the cell for 1 s) / number of MSs in the cell} \end{pmatrix}$$ + +where, the number of MSs in the cell includes the MS being added. + +Under no circumstance shall the SGSN use a value of Bmax greater than Bmax\_default\_MS for an MS unless it receives a FLOW-CONTROL-MS PDU from the BSS for that MS. + +The SGSN shall not use a leak rate (R) for an MS greater than R\_default\_MS unless it receives a FLOW-CONTROL-MS PDU from the BSS for that MS. + +## 8.2.4 Flow Control of Uplink Traffic from a BSS to an SGSN + +No flow control procedures are defined between the BSS and the SGSN in uplink direction. + +# 8.3 BVC blocking and unblocking procedure + +## 8.3.1 PTP BVC + +The following statement applies only for PTP BVC. + +The BVC blocking and unblocking procedures are initiated by the BSS to remove from use, or bring in to use, a BVC. + +A BSS may block one BVC because of: + +- operation and Maintenance intervention for a cell; +- equipment failure at the BSS; +- cell equipment failure at the BSS; or +- other causes not regarded in phase 1 of the implementation of GPRS (Cause Value: "reserved for future use"). + +When a BSS wishes to block a BVC, the BSS shall mark that BVC as blocked, thereafter discarding any traffic sent to the BVC in the uplink direction. The cell associated with the BVC should not accept data in the downlink direction. The BSS shall send a BVC-BLOCK PDU to the SGSN and start timer T1. The BVC-BLOCK PDU contains: + +- the BVCI of the BVC to be blocked; and +- a Cause element indicating the reason for blocking (typical cause values: O&M intervention, Equipment failure). + +On receipt of a BVC-BLOCK PDU, the SGSN shall mark the indicated BVC as blocked and stop transmitting traffic addressed to this BVC. The SGSN shall then acknowledge the blocking of the BVC by sending a BVC-BLOCK-ACK PDU to the BSS. + +The BVC-BLOCK-ACK PDU contains the BVCI received in the BVC-BLOCK PDU. + +On receipt of the BVC-BLOCK-ACK PDU the BSS shall stop timer T1. + +The BVC shall be seen as blocked by an SGSN until a BVC-UNBLOCK PDU is received indicating that the BVC's status has changed. + +During the BVC blocking procedure, traffic in transit to or from a cell is in an indetermined state and may be lost. When unblocking a BVC both the BSS and SGSN shall be in an operational state, i.e. the underlying network service and the BVC shall be available for use. + +If a BSS wishes to unblock a blocked BVC it shall send a BVC-UNBLOCK PDU, and start timer T1. + +The BVC-UNBLOCK PDU contains: + +- the BVCI of the BVC to be unblocked. + +If a BVC-UNBLOCK PDU is received by an SGSN for a blocked BVC, the BVC shall be marked as unblocked and a BVC-UNBLOCK-ACK PDU shall be returned to the BSS, containing the BVCI received in the BVC-UNBLOCK PDU. + +The BSS shall stop timer T1 on receipt of the BVC-UNBLOCK-ACK PDU and mark the BVC as unblocked. + +### 8.3.2 Signalling BVC + +The blocking and unblocking procedure is not applicable for the signalling BVC. The signalling BVC shall never be blocked. + +### 8.3.3 Abnormal Conditions + +The following statements apply only for a signalling BVC. + +If a BVC-BLOCK PDU is received by an SGSN for the signalling BVC, the PDU is ignored. + +If a BVC-BLOCK-ACK PDU is received by a BSS for the signalling BVC, the PDU is ignored. + +If BVC-UNBLOCK PDU is received by an SGSN for the signalling BVC, the PDU is ignored. + +If BVC-UNBLOCK-ACK PDU is received by an BSS for the signalling BVC, the PDU is ignored. + +The following statements apply only for PTP BVC. + +If a BVC-BLOCK-ACK PDU is not received for a BVC-BLOCK PDU within T1 seconds, then the BVC-BLOCK PDU procedure shall be repeated a maximum of BVC-BLOCK-RETRIES attempts. After BVC-BLOCK-RETRIES attempts the BVC remains blocked, the procedure is stopped and the O&M system is informed. + +If a BVC-UNBLOCK-ACK PDU is not received for a BVC-UNBLOCK PDU within T1 seconds, then the BVC-UNBLOCK PDU procedure shall be repeated a maximum of BVC-UNBLOCK-RETRIES attempts. After BVC-UNBLOCK-RETRIES attempts the status of the BVC remains blocked, the procedure is stopped and the O&M system is informed. + +If traffic is received on a BVC that is marked at a BSS or at an SGSN as blocked, and no BVC-Unblocking procedure is pending, the received PDU shall not be accepted and a STATUS PDU (Cause value: BVC blocked) shall be sent to the peer entity on the signalling BVC. The STATUS PDU shall indicate the BVCI of the BVC upon which the error was detected. + +If a BVC-BLOCK PDU is received by an SGSN for a blocked BVC, a BVC-BLOCK-ACK PDU shall be returned. + +If a BVC-UNBLOCK PDU is received by an SGSN for an unblocked BVC, a BVC-UNBLOCK-ACK PDU shall be returned. + +If an unexpected BVC-BLOCK-ACK PDU is received by a BSS, and it is related to a BVC that is locally blocked, the BVC-BLOCK-ACK PDU is discarded. If the BVC-BLOCK-ACK PDU is related to a BVC that is not locally blocked, then a BVC unblock procedure shall be performed. + +If an unexpected BVC-UNBLOCK-ACK PDU is received by a BSS and it is related to a BVC that is locally not blocked, the BVC-UNBLOCK-ACK PDU is discarded. If the BVC-UNBLOCK-ACK PDU is related to a BVC that is locally blocked, then a BVC block procedure shall be performed. + +## 8.4 BVC-RESET procedure + +The purpose of the BVC-RESET procedure is to synchronise the initialisation of GPRS BVC related contexts at a BSS and SGSN. This enables the BSS and SGSN to begin communication in known states. A BVC-RESET procedure is performed because of recovery procedures related to: + +- a system failure in the SGSN or BSS that affects GPRS BVC functionality (e.g. processor recovery); +- an underlying network service system failure; or +- a change in the transmission capability of the underlying network service, where the "change" is from zero kbps to greater-than-zero kbps; +- a change in mapping between the BVCI and cell identifier. + +The BSS may also send BVC-RESET as a means to create the initial mapping between BVCIs and cell identifications. + +After any of the possible events stated above, the status of the affected BVCs may be inconsistent at the SGSN and the BSS. After performing the BVC Reset procedure all affected BVCs are assumed to be unblocked at the SGSN. The reset procedure forces a consistent state upon SGSN and BSS by requiring that after the completion of the BVC-Reset procedure the BSS initiates the block procedure for all affected BVCs that are marked as blocked at the BSS. + +Before a BSS (or SGSN) sends a BVC-RESET PDU, the operational status of the associated network service shall be obtained by the BSS (or SGSN). + +If the associated network service is operational, the BSS (or SGSN) shall send a BVC-RESET PDU to its peer entity and start timer T2. The BSS (or SGSN) may receive BVC related signalling and UNITDATA PDUs before the procedure is acknowledged, but shall not transmit PDUs. + +If the associated network service is not operational, the BVC-RESET procedure is postponed until internal periodic status checks indicate that it is operational. + +The BVC-RESET PDU contains: + +- the BVCI of the reset BVC; +- a cause element indicating the reason for reset; +- the cell identifier, when the reset is for a PTP BVC and BSS is initiator of the reset; +- feature bitmap, when the reset is for a signalling BVC. + +After the SGSN (or BSS) has initialised all affected GPRS related contexts, a BVC-RESET-ACK PDU is returned. + +The BVC-RESET-ACK PDU contains: + +- the BVCI of the reset BVC; +- the cell identifier, when the reset is for a PTP BVC and SGSN is initiator of the reset. + +Upon reception by a BSS (or SGSN) of the BVC-RESET-ACK PDU the timer T2 is stopped. + +### 8.4.1 Signalling BVC + +After any failure affecting the NSE, the party (BSS or SGSN) where the failure resided shall reset the signalling BVC. After sending or receiving a BVC-RESET PDU for the signalling BVC, the BSS shall stop all traffic and initiate the BVC-RESET procedure for all BVCs corresponding to PTP functional entities of the underlying network service entity. The BSS must complete the BVC-RESET procedure for signalling BVC before starting PTP BVC-RESET procedures. + +The Feature bitmap is sent to identify the optional features that can be supported by the network service entity. After completion of the signalling BVC-RESET procedure both entities shall locally determine the common set of optional features supported by both NSEs. This is done by performing the bit AND operation of the received Feature bitmap with its own Feature bitmap. + +If the Feature bitmap IE is missing in a signalling BVC-RESET or BVC-RESET-ACK PDU or if the result of the AND operation is '0' then no optional features are activated. + +After sending or receiving a BVC-RESET PDU for the signalling BVC, the SGSN shall stop all traffic in the PTP BVCs of the corresponding NSE. + +## 8.4.2 PTP BVC + +After any failure affecting only part of the BVC functionality not including the signalling BVC the party where the failure resided shall reset only the affected BVCs. + +If the BSS was the initiator of the BVC-RESET procedure, the BSS may initiate the blocking procedure upon receipt of a BVC-RESET-ACK PDU. If the SGSN was the initiator of the BVC-RESET procedure while the affected BVC is marked as blocked at the BSS side, the BSS shall initiate the BVC-Blocking procedure after having returned the BVC-RESET-ACK PDU to the SGSN. + +Upon reception of a BVC-RESET PDU, the SGSN (or BSS) shall discard UNITDATA PDUs addressed to the reset BVC. + +After reset of a PTP BVC, UNITDATA PDUs addressed to the BVC may then be received and transmitted, unless it is blocked. + +## 8.4.3 Abnormal Conditions + +The following statements are valid for both signalling and PTP BVC. + +If a BSS (or SGSN) sends a BVC-RESET PDU to an SGSN (or BSS) and the BVC-RESET-ACK PDU is not returned within a period T2, the BVC-RESET procedure shall be repeated a maximum of BVC-RESET-RETRIES attempts. After BVC-RESET-RETRIES attempts the procedure is stopped and the O&M system is informed. In case of PTP BVC, the status of all affected BVCs at the BSS (or SGSN) shall be blocked as a consequence. + +If the BSS receives a BVC-RESET PDU for a BVCI which is unknown in the BSS, then the BSS shall return a STATUS PDU towards the SGSN including the BVCI and the cause value 'BVCI unknown'. + +If the BSS (or SGSN) has sent a BVC-RESET PDU for a BVCI to the SGSN (or BSS) and is awaiting a BVC-RESET-ACK PDU in response, but instead receives a BVC-RESET PDU indicating the same BVCI, then this shall be interpreted as a BVC-RESET ACK PDU and the T2 timer shall be stopped. + +The BVC\_RESET for signalling BVC overrides all pending procedures for PTP BVC, i.e. other pending procedures are stopped and corresponding running timers are stopped. + +If the BSS (or SGSN) receives an unexpected BVC-RESET ACK PDU, this shall be ignored. + +If the BSS has sent a BVC-UNBLOCK PDU and receives a BVC-RESET PDU before the BVC-UNBLOCK-ACK PDU has been received from the SGSN, then the BSS shall consider the corresponding BVC marked as unblocked. + +## 8.5 Trace procedure + +The purpose of the trace invocation procedure is to inform the receiving entity that it should begin producing a trace record on an MS. The trace is invoked by an SGSN by sending an SGSN-INVOKE-TRACE PDU to the peer entity. The SGSN-INVOKE-TRACE PDU is not acknowledged. + +The events and parameters to be recorded are indicated in the "Trace type" information element are defined in 3GPP TS 32.008. + +The remaining elements, when received, are to be passed transparently to the OMC receiving the trace record. + +The element "OMCId", if present, indicates the OMC to which the record is destined. + +The PDU includes a trace reference which is allocated by the entity which triggered the trace. + +The element "TriggerId", if present, indicates the entity which triggered the trace. + +The Trace Reference and TriggerId IEs are used to tag the trace record to allow simpler construction of the total record by the entity which combines trace records. + +## 8.6 Overload Control procedure + +### 8.6.1 General + +This procedure is defined to control the traffic to the SGSN from BSC when the SGSN is in an overload situation. + +The philosophy used at BSS side is: + +- If T15 is not running and an OVERLOAD PDU including the *Priority Class Indicator* IE is received, then traffic for the indicated priority class should be reduced by one step. At the same time, timers T15 and T16 should be started. +- During T15, all received OVERLOAD PDU should be ignored. +- If T16 expires, the traffic should be increased by one step and T16 should be re-started unless full load has been resumed. +- The number of steps and the method of reducing/increasing the load are considered to be an implementation specific function. + +### 8.6.2 Overload Operation + +The SGSN could indicate to the BSS that it is in a congested state by sending an OVERLOAD PDU and request the BSS to reduce the traffic for the category of MSs indicated in the *Priority Class Indicator* IE. + +The BSS receiving the OVERLOAD PDU shall assume the SGSN sending the PDU as being in an overloaded state and reduce the traffic to the SGSN using the algorithm described in sub-clause 8.6.1. + +The amount of traffic could be reduced by using the Access Control Class in the system information message defined in 3GPP TS 44.018. However it is implementation specific regarding how the BSS reduces the traffic in response to receiving an OVERLOAD PDU. + +--- + +## 8a Signalling procedures between PFM SAPs + +### 8a.1 Create BSS PFC procedure + +#### 8a.1.0 General + +If the BSS receives a request to transfer an uplink or downlink LLC PDU for which it currently does not have a BSS packet flow context and the PFI does not indicate best-effort or SMS or TOM8 or signalling then the BSS should send a DOWNLOAD-BSS-PFC PDU to the SGSN and start timer T6. In the uplink case the TLLI, optional Radio Priority, and optional Packet Flow ID are received from the MS as defined in 3GPP TS 44.060. Until the BSS receives the BSS PFC the BSS shall handle uplink and downlink transfers according to a best-effort default aggregate BSS QoS profile. For uplink transfers the best-effort default profile is specific to the radio priority level. + +If the BSS receives a request to transfer an uplink or downlink LLC PDU associated to a PFI indicating best-effort or SMS or TOM8 or signalling then the BSS may handle the corresponding transfer according to an operator-defined aggregate BSS QoS profile. Indeed the latter cannot be negotiated with the SGSN for those flows. It is also up to the implementation what Allocation/Retention Priority is granted to those flows. + +If the BSS does not receive a PFI from the MS, e.g. from a R97 or R98 MS, the BSS shall not send a DOWNLOAD-BSS-PFC PDU to the SGSN. In this case the QoS Profile IE is utilized instead. + +Following a DOWNLOAD-BSS-PFC PDU if there is not an ongoing Delete PFC procedure for that corresponding PFI, the SGSN shall send a CREATE-BSS-PFC PDU to the BSS with a requested Aggregate BSS QoS Profile and start timer T7. On receipt of CREATE-BSS-PFC PDU the BSS stops timer T6 and responds with a CREATE-BSS-PFC-ACK PDU containing the negotiated Aggregate BSS QoS Profile. The BSS may restrict the requested ABQP given its capabilities and the current load. The SGSN may include the *Service UTRAN CCO* (Cell Change Order) information element in the PDU (relevant if the network initiated cell change order to UTRAN, network initiated cell change order to E-UTRAN, PS handover to UTRAN or PS Handover to E-UTRAN procedures are used). If this information element is received in multiple PDUs (either DL-UNITDATA PDU(s), CREATE-BSS-PFC PDU(s) or PS-HANDOVER-REQUEST PDU(s)), the information element contained in last received PDU shall take precedence. If there is an ongoing Delete PFC procedure the SGSN shall not send a CREATE-BSS-PFC-PDU (see subclause 8a.3). + +The SGSN may also initiate the Create BSS PFC procedure. It is not required that the SGSN receive a DOWNLOAD-BSS-PFC PDU before sending a CREATE-BSS-PFC request. + +The CREATE-BSS-PFC PDU may trigger a call admission control algorithm in the BSS to check whether the requested ABQP can be served. If there is valid MS Radio Access Capability IE known by the SGSN for the associated MS, the SGSN shall include it in the CREATE-BSS-PFC PDU. If the MS Radio Access Capability IE are not present in the request, then the Radio Access Capability Update procedure may be called. + +The BSS may return a CREATE-BSS-PFC-NACK with a cause if it is unable to create or modify the PFC. On receipt of a CREATE-BSS-PFC-ACK PDU which does not convey the cause 'PFC queuing' (cf. sub-clause 8a.1.0a) or of a CREATE-BSS-PFC-NACK PDU the SGSN shall stop timer T7. + +The Packet Flow Timer (PFT) is provided to the BSS by the SGSN. It is defined as the maximum time the BSS may hold the PFC during periods of inactivity for a PFC. The timer is started upon the receipt of a CREATE-BSS-PFC PDU and restarted after the transmission of an uplink PDU for that PFC. The timer is also restarted upon the transfer of the corresponding PFC from an old to a new cell. + +If a CREATE-BSS-PFC PDU is received for an MS which has a BSS PFC in the BSS, then this shall be interpreted by the BSS as a request to: + +- create a new PFC if the PFI included in the PDU is not known in the BSS, +- modify an existing PFC if the PFI included in the PDU is already known in the BSS. + +The SGSN may inform the BSS about the contents of SPID in the CREATE-BSS-PFC PDU. In this case the SPID is stored in the BSS. + +## 8a.1.0a Allocation/Retention Priority handling + +The SGSN may include the *Allocation/Retention Priority* information element in the CREATE-BSS-PFC- PDU. If this information element is received and the BSS supports ARP handling, the BSS shall establish or modify the resources according to the values of the *Allocation/Retention Priority* IE (priority level, pre-emption indicators, queuing) and the resource situation as follows: + +- The BSS shall consider the priority level of the requested PFC, when deciding on the resource allocation. +- If the requested PFC is allowed for queuing and the resource situation so requires, the BSS may place the PFC in the establishment queue. +- The priority levels and the pre-emption indicators may (singularly or in combination) be used to determine whether the PFC assignment has to be performed unconditionally and immediately. If the requested PFC is marked as "may trigger pre-emption" and the resource situation so requires, the BSS may trigger the pre-emption procedure which may then cause the forced release of a lower priority PFC which is marked as "pre-emptable". Whilst the process and the extent of the pre-emption procedure is operator dependent, the pre-emption indicators, if given in the CREATE-BSS-PFC PDU, shall be treated as follows: + 1. The values of the last received *Pre-emption Vulnerability* IE and *Priority Level* IE shall prevail. + 2. If the *Pre-emption Capability* IE is set to "may trigger pre-emption", then this allocation request may trigger the pre-emption procedure. + +3. If the *Pre-emption Capability* IE is set to "shall not trigger pre-emption", then this allocation request shall not trigger the pre-emption procedure. + 4. If the *Pre-emption Vulnerability* IE is set to "pre-emptable", then this connection shall be included in the pre-emption process. + 5. If the *Pre-emption Vulnerability* IE is set to "not pre-emptable", then this connection shall not be included in the pre-emption process. + 6. If the *Priority Level* IE is set to "no priority" the given values for the *Pre-emption Capability* IE and *Pre-emption Vulnerability* IE shall not be considered. Instead the values "shall not trigger pre-emption" and "not pre-emptable" shall prevail. +- If the *Allocation/Retention Priority* IE is not given in the CREATE-BSS-PFC -PDU, the allocation request shall not trigger the pre-emption process and the connection may be pre-empted and considered to have the value "lowest" as priority level. Moreover, queuing shall not be allowed. + - The BSS pre-emption process shall keep the following rules: + - 1) The BSS shall only pre-empt PFCs with lower priority, in ascending order of priority. + - 2) The pre-emption may be done for PFCs belonging to the same MS or to other MSs. + +If the BSS is unable to create the PFC immediately and the ARP IE was present in the CREATE-BSS-PFC PDU indicating that queuing is allowed for the PFC, the BSS may put the PFC creation request or modification in a queue. In that case, it shall send a CREATE-BSS-PFC-ACK PDU including the cause 'PFC queuing' to the SGSN and start the timer T10. This timer specifies the maximum time for queuing of the request of establishment or modification; its value is provided by the SGSN in the CREATE-BSS-PFC PDU. Several PFCs for a given MS may be queued in parallel. While a PFC is queued, the BSS shall handle the corresponding uplink or downlink transfers according to a best-effort default aggregate BSS QoS profile. + +For each PFC that is queued the following outcomes shall be possible: + +- successfully established or modified; +- failed to establish or modify; +- failed due to expiry of the timer T10. + +When the SGSN receives the response that the requested PFC is queued, the SGSN shall expect the BSS to provide the outcome of the queuing function for the PFC before expiry of T7. In case the timer T7 expires, the SGSN shall consider the create BSS PFC procedure terminated and failed. + +The BSS shall report the outcome of the queuing for every queued PFC. The BSS shall stop the timer T10 associated to a given PFC when it has been successfully established or modified. The BSS shall then send a CREATE-BSS-PFC-ACK PDU with cause 'PFC created successfully' to the SGSN for that PFC, informing the SGSN of the negotiated ABQP. Upon receipt of the CREATE-BSS-PFC-ACK PDU with cause 'PFC created successfully' from the BSS, the SGSN shall stop timer T7. + +In the case the timer T10 expires, the create BSS PFC procedure terminates in the BSS for the corresponding PFC and the BSS shall send a CREATE-BSS-PFC-NACK PDU with cause 'PFC create failure'. The SGSN shall then consider the create BSS PFC procedure terminated and failed. + +In case the SGSN wishes to delete a PFC which is being queued, it shall stop timer T7 and start the delete BSS PFC procedure. Upon receipt of the request to delete the PFC, the BSS shall take it out from the queue and proceed with the rest of the procedure, as described in sub-clause 8a.3. + +In case the SGSN wishes to modify a PFC which is being queued, it shall restart timer T7 and send a CREATE-BSS-PFC PDU as described in sub-clause 8a.1. Upon receipt of the request to modify the PFC, the BSS shall take it out from the queue and treat the new request. + +### 8a.1.1 Abnormal conditions + +If the SGSN receives a DOWNLOAD-BSS-PFC PDU with an unknown PFI it shall not respond with a CREATE-BSS-PFC PDU. + +If a CREATE-BSS-PFC PDU is not received for a DOWNLOAD-BSS-PFC PDU within T6 seconds, then the DOWNLOAD-BSS-PFC PDU shall be repeated a maximum of DOWNLOAD-BSS-PFC-RETRIES attempts. After DOWNLOAD-BSS-PFC-RETRIES + 1 attempts the procedure is stopped and the O&M system is informed. If a BSS PFC is not received then the BSS shall handle uplink and downlink transfers according to a best-effort default aggregate BSS QoS profile. + +If a CREATE-BSS-PFC-ACK or CREATE-BSS-PFC-NACK PDU is not received in response to a CREATE-BSS-PFC PDU within T7 seconds, then the CREATE-BSS-PFC PDU shall be repeated a maximum of CREATE-BSS-PFC-RETRIES attempts. After CREATE-BSS-PFC-RETRIES+1 attempts the procedure is stopped and the O&M is informed. + +If a BSS not supporting ARP handling is unable to create the PFC then a CREATE-BSS-PFC-NACK PDU is returned with a cause value (e.g. Cause value: PFC create failure). The SGSN shall stop the Create BSS PFC procedure. + +If a BSS supporting ARP handling is unable to create the PFC immediately and the ARP IE was not present in the CREATE-BSS-PFC PDU or the ARP IE was present but queuing is not allowed for the PFC, then a CREATE-BSS-PFC-NACK PDU is returned with cause value 'PFC create failure'. The SGSN shall then stop the Create BSS PFC procedure. + +If a CREATE-BSS-PFC PDU is received in the BSS for an MS for which the PS Handover Required procedure is ongoing, the BSS shall ignore the CREATE-BSS-PFC PDU and return a CREATE-BSS-PFC-NACK PDU to the SGSN indicating Cause "MS under PS Handover treatment". + +## 8a.2 Modify BSS PFC procedure + +The BSS may request modification of the contents of an existing BSS PFC at any time via the MODIFY-BSS-PFC PDU, e.g. due to a change in resource availability at the BSS. The BSS sends the MODIFY-BSS-PFC PDU and start timer T8. The SGSN inserts the modified parameters in the MODIFY-BSS-PFC PDU into the relevant PDP contexts. The SGSN shall respond to a modify request with a MODIFY-BSS-PFC-ACK PDU except when there is an ongoing Delete BSS PFC procedure for that PFI (see sub-clause 8a.3). The SGSN may restrict the requested aggregate BSS QoS profile given its capabilities and current load. The Packet Flow Timer (PFT) may be provided to the BSS by the SGSN. This timer is (started or) restarted upon the receipt of the MODIFY-BSS-PFC-ACK PDU and restarted after the transmission of an uplink PDU for that PFC. On receipt of a response to the Modify procedure the BSS shall stop timer T8. + +The SGSN can reject the profile proposed by the BSS by answering with a MODIFY-BSS-PFC-ACK PDU containing the previous ABQP. The SGSN may request the modification of the contents of a BSS PFC at any time via the CREATE-BSS-PFC PDU, e.g. due to the activation, modification, or deactivation of a PDP context. It shall not use the MODIFY-BSS-PFC PDU. If the BSS PFC already exists the BSS shall interpret the PDU as a modification request and the BSS shall reply with a CREATE-BSS-PFC-ACK. The BSS may restrict the requested ABQP given its capabilities and the current load. + +The Modify BSS PFC procedure shall never be initiated for an MS for which the PS Handover Required procedure is ongoing. + +### 8a.2.1 Abnormal conditions + +If a MODIFY-BSS-PFC-ACK is not received in response to a MODIFY-BSS-PFC PDU within T8 seconds, then the MODIFY-BSS-PFC PDU shall be repeated a maximum of MODIFY-BSS-PFC-RETRIES attempts. After MODIFY-BSS-PFC-RETRIES+1 attempts the procedure is stopped and the O&M is informed. + +## 8a.3 Delete BSS PFC procedure + +The SGSN may request the deletion of a BSS PFC at any time using the DELETE-BSS-PFC PDU. The BSS shall respond with a DELETE-BSS-PFC-ACK PDU. In case of user inactivity the BSS may delete a BSS packet flow context without notifying the SGSN. In case the BSS is no longer able to support the BSS PFC ABQP, it may send a DELETE-BSS-PFC-REQ PDU with cause 'PFC pre-empted' or 'ABQP no more supported' to the SGSN. The SGSN may either start the Delete BSS PFC procedure or a new Create BSS PFC procedure. In case the BSS receives neither a DELETE-BSS-PFC PDU nor a CREATE-BSS-PFC PDU the behaviour in the BSS is implementation specific. + +The Delete BSS PFC procedure takes precedence over the Modify BSS PFC and the Create BSS PFC procedures, i.e. when the BSS receives a DELETE-BSS-PFC PDU it shall abort any ongoing Create BSS PFC or Modify BSS PFC procedure for that PFI. + +If a DELETE-BSS-PFC PDU is received for an MS for which the PS Handover Required procedure is ongoing, the BSS shall initiate the PS Handover Cancel procedure and continue the Delete BSS PFC procedure for the corresponding MS. + +## 8a.4 PS Handover Required procedure + +In the case of an intra-BSS PS Handover or intra-BSS DTM Handover, the optimized intra-BSS handover procedure may be used (see 3GPP TS 44.060); in such case, the PS Handover Required procedure is not used. + +When a BSS initiates a PS handover or DTM Handover it shall initiate the PS Handover Required procedure and send the PS-HANDOVER-REQUIRED PDU to the SGSN. Except in the case of DTM Handover, the BSS shall then start timer T12 (see NOTE). + +NOTE: The DTM Handover procedure is guarded at the source BSS by the BSSMAP timer T23 (see 3GPP TS 48.008). + +If DTM Handover is ongoing and was initiated for a reason specific to the packet resources, or PS Handover is ongoing, the *Cause* IE of the PS-HANDOVER-REQUIRED PDU should be set to an appropriate value (e.g. "Uplink quality", "Uplink strength", "Downlink quality", "Downlink strength", "Distance", "Better cell", "Traffic" or "O&M intervention"). + +NOTE: The radio related cause values are not applicable to the DTM Handover. + +If DTM Handover is ongoing, and was initiated for a reason specific to the dedicated resource, the *Cause* IE shall indicate "CS cause". + +The BSS should not initiate the PS handover required procedure in the case of an MOCN or a GWCN configuration if the Rerouting procedure is ongoing. + +The BSS shall not initiate the PS handover required procedure in case CS to PS SRVCC from GERAN to UTRAN or to E-UTRAN [25] is ongoing. The reception of a PS-HANDOVER-REQUIRED PDU will initiate the PS Handover Required procedure in the SGSN and the allocation of resources in the target system. + +If PS handover to A/Gb mode is required, the source BSS shall include the *Source BSS to Target BSS Transparent Container* IE and the *Target Cell Identifier* IE in the PS-HANDOVER-REQUIRED PDU. + +If PS handover to Iu mode is required, the source BSS shall include the *Source to Target Transparent Container* IE and the *Target RNC Identifier* IE in the PS-HANDOVER-REQUIRED PDU. The *Source to Target Transparent Container* IE shall be encoded as the *Source RNC to Target RNC Transparent Container* IE as specified in 3GPP TS 25.413 or 3GPP TS 44.118. + +If PS handover to a UTRAN CSG cell or hybrid cell is required, the source BSS shall include the *Source to Target Transparent Container* IE, *Target RNC Identifier* IE and the *CSG Identifier* IE in the PS-HANDOVER-REQUIRED PDU. The source BSS shall set the value of the *Cell Access Mode* field in the *CSG Identifier* IE according to the information received from the MS through measurement reporting as defined in 3GPP TS 44.060. The *Source to Target Transparent Container* IE shall be encoded as the *Source RNC to Target RNC Transparent Container* IE as specified in 3GPP TS 25.413. + +NOTE: In this specification: A CSG cell is a reported cell for which the access mode indicates "Closed access mode" as defined in [39] and Hybrid Cell is a reported cell for which the access mode indicates "Hybrid access mode" as defined in [39]. + +If PS handover to E-UTRAN is required, the source BSS shall include the *Source to Target Transparent Container* IE and the *Target eNB Identifier* IE or the *Target RNC Identifier* IE (carrying the Corresponding RNC-ID of the target eNB) in the PS-HANDOVER-REQUIRED PDU. The *Source to Target Transparent Container* IE shall be encoded as the *Source eNB to Target eNB Transparent Container* IE as specified in 3GPP TS 36.413. + +If PS handover to a E-UTRAN CSG cell or hybrid cell is required, the source BSS shall include the *Source to Target Transparent Container* IE, the *Target eNB Identifier* IE, *Tracking Area Code* IE and the *CSG Identifier* IE in the PS-HANDOVER-REQUIRED PDU. The source BSS shall set the value of the *Cell Access Mode* field in the *CSG Identifier* IE according to the information received from the MS through measurement reporting as defined in 3GPP TS 44.060. The *Source to Target Transparent Container* IE shall be encoded as the *Source eNB to Target eNB Transparent Container* IE as specified in 3GPP TS 36.413. + +The *Active PFCs List* IE informs the SGSN about which PFCs that are active for the MS in the source cell at the time of sending the PS-HANDOVER-REQUIRED PDU. The concept of "Active PFCs" is defined in 3GPP TS 43.129. The *Active PFCs List* IE shall not contain any pre-defined PFIs. + +For DTM Handover to A/Gb mode, the source BSS shall include the *CS Indication IE* in the *Source BSS to Target BSS Transparent Container* IE. The contents of the *CS Indication IE* shall uniquely identify, for this MS, the handover attempt, and shall be identical to the contents of the *PS Indication IE* included in the BSSMAP HANDOVER REQUIRED message (see 3GPP TS 48.008). The *Target Cell Identifier* IE shall identify the same cell as the one specified in the *Cell Identifier List (preferred)* IE in the corresponding BSSMAP HANDOVER REQUIRED message (see 3GPP TS 48.008). + +For DTM Handover to UTRAN, the source BSS shall set the *Number of Iu Instances* IE equal to 2 in the *Source RNC to Target RNC Transparent Container* IE (see 3GPP TS 25.413) + +When the resource allocation in the target system is complete, the SGSN shall send a PS-HANDOVER-REQUIRED-ACK PDU to the source BSS and end the PS Handover Required procedure. + +The *Target BSS to Source BSS Transparent Container* IE, or the *Target to Source Transparent Container* IE as received from the target system, shall be included in the PS-HANDOVER-REQUIRED-ACK PDU. + +Except in the case of DTM Handover, the source BSS shall, on reception of the PS-HANDOVER-REQUIRED-ACK PDU from the SGSN, stop timer T12, trigger the transmission of the PS HANDOVER COMMAND message towards the MS (as specified in 3GPP TS 44.060) and end the PS Handover Required procedure. In the case of DTM Handover, the PS Handover Required procedure is terminated when timer T23 is stopped for any reason or expires as specified in 3GPP TS 48.008. The subsequent behaviour of the network is specified in 3GPP TS 48.008. + +In case of unsuccessful PS Handover, the source BSS shall be notified through the PS-HANDOVER-REQUIRED-NACK PDU. + +When the SGSN terminates the PS Handover Required procedure by sending a PS-HANDOVER-REQUIRED-NACK PDU to the source BSS, the *Cause* IE should be set to an appropriate value (e.g. "PFC create failure", "Cell traffic congestion", "Equipment failure", "O&M intervention", "PS Handover Target not allowed" or "PS Handover not Supported in Target BSS or Target System"). + +Except in the case of DTM Handover, upon reception of a PS-HANDOVER-REQUIRED-NACK PDU from the SGSN, the source BSS shall stop timer T12 and terminate the ongoing PS Handover Required procedure. + +For DTM Handover, the source BSS behaviour on receipt of a PS-HANDOVER-REQUIRED-NACK PDU is described as part of the Handover Required procedure (see 3GPP TS 48.008). + +The source BSS shall always include the "*Reliable Inter RAT Handover Info*" indicator set to '1' in the PS-HANDOVER-REQUIRED-PDU when the target is a GERAN A/Gb mode BSS if the *Inter RAT Handover Info* IE is available and was received from the SGSN in a PS-HANDOVER-COMPLETE-ACK or a CREATE-BSS-PFC PDU or a PS-HANDOVER-REQUEST PDU with "*Reliable Inter RAT Handover Info Indicator*" set to "1". It shall be set to '0' otherwise. + +If the SGSN receives the *CSG Identifier* IE in the PS-HANDOVER-REQUIRED PDU and the *Cell Access Mode* field is set to "CSG cell", it shall perform access control as specified in 3GPP TS 29.060. If the MS is allowed to access the target cell, the SGSN shall continue the PS handover to the target side as specified in 3GPP TS 29.060. If the MS is not allowed to access the target cell, the SGSN shall send the PS-HANDOVER-REQUIRED-NACK PDU with the *Cause* IE set to "Invalid CSG cell" to the source BSS. If the *Cell Access Mode* field in the *CSG Identifier* IE is set to "Hybrid cell", the SGSN shall provide the CSG membership status of the MS and the *CSG Id* to the target side as specified in 3GPP TS 29.060. + +## 8a.4.1 Abnormal conditions + +Except in the case of DTM Handover, if timer T12 expires in the source BSS and there has been no response from the SGSN to the PS-HANDOVER-REQUIRED PDU, the source BSS may initiate a new PS Handover Required procedure for the same mobile station, either directly or after first having cancelled the previous PS Handover Required procedure by initiating the PS Handover Cancel procedure with the value for the *Cause* IE set to "T12 expiry". + +NOTE: For the case of DTM Handover, the abnormal condition caused by the expiry of BSSMAP timer T23 is described in 3GPP TS 48.008. + +## 8a.5 PS Handover Request procedure + +The SGSN shall initiate the PS Handover Request procedure by sending a PS-HANDOVER-REQUEST PDU, including the NAS container for PS Handover corresponding to the PFCs to be set-up (except in the case of intra-SGSN PS handover), to the target BSS and starting timer T13. The PS-HANDOVER-REQUEST PDU shall be sent on the point-to-point BVC indicated by the target Cell identity received from the old system. + +On receipt of a PS-HANDOVER-REQUEST PDU containing a *CS Indication* IE (i.e. a DTM Handover procedure is ongoing), then the target BSS shall proceed as follows: + +- If the timer T24 (see 3GPP TS 48.008) is not running, then the target BSS shall start timer T24. +- When both PS-HANDOVER-REQUEST PDU and BSSMAP HANDOVER REQUEST messages have been received and the contents of the *CS Indication* IE and *PS Indication* IE are identical, the target BSS shall stop timer T24 (see 3GPP TS 48.008), and, provided that a dedicated resource has been allocated (see 3GPP TS 48.008), attempt to create a new BSS Context for the MS, create PFCs according to the received ABQP parameters and allocate TBF resources within the capabilities of the mobile station. + +On receipt of a PS-HANDOVER-REQUEST PDU which does not contain a *CS Indication* IE, the target BSS shall create a new BSS Context for the MS, create PFCs according to the received ABQP parameters and allocate TBFs for uplink and, if needed, for downlink transmission. + +The SGSN may include the *Service UTRAN CCO* (Cell Change Order) information element in the PS-HANDOVER-REQUEST PDU (relevant if the network initiated cell change order to UTRAN, network initiated cell change order to E-UTRAN, PS handover to UTRAN or PS Handover to E-UTRAN procedures are used). If this information element is received in multiple PDUs (either DL-UNITDATA PDU(s), CREATE-BSS-PFC PDU(s) or PS-HANDOVER-REQUEST PDU(s)), the information element contained in the last received PDU shall take precedence. + +The SGSN receiving the *Reliable Inter RAT Handover Info* IE in the PS-HANDOVER-REQUIRED PDU shall forward this IE to the target BSS in the PS-HANDOVER-REQUEST PDU. + +The Packet Flow Timer (PFT) is provided to the target BSS by the SGSN for each corresponding PFC. It is defined as the maximum time the BSS may hold the PFC during periods of inactivity for a PFC. The timer is started upon the initiation of the PS Handover Complete procedure (see sub-clause 8a.7) and restarted after the transmission of an uplink PDU for that PFC. The timer is also restarted upon the transfer of the corresponding PFC from an old to a new cell. + +When resources have been successfully allocated by the target BSS, it shall send a PS-HANDOVER-REQUEST-ACK PDU to the SGSN. From this point in time, the target BSS shall be prepared to receive downlink LLC PDUs for the corresponding MS on the allocated resources. The target BSS shall also be prepared to receive uplink RLC data blocks or a PS HANDOVER ACCESS message upon successful MS access in the target cell (as specified in 3GPP TS 44.060). + +The PS-HANDOVER-REQUEST-ACK PDU shall include the *Target BSS to Source BSS Transparent Container* IE (see sub-clause 11.3.79) which contains either a complete PS HANDOVER COMMAND message or, in the case of DTM Handover, a complete DTM HANDOVER COMMAND message. For the definition of the PS HANDOVER COMMAND and DTM HANDOVER COMMAND messages, see 3GPP TS 44.060. In addition, the BSS shall include in the *Target BSS to Source BSS Transparent Container* IE the *SI/PSI Container* IE (see sub-clause 11.3.95b) if the *PS Handover Indications* IE indicating "SI/PSI requested" was present in the *Source BSS to Target BSS Transparent Container* of the incoming PS-HANDOVER-REQUEST PDU. In the case where the target cell supports network sharing and the MS Radio Access Capability information element included in the Source BSS to Target BSS Transparent Container received in the PS-HANDOVER-REQUEST PDU indicates MS supporting network sharing, the target BSS shall include in the SI/PSI messages sent to the source BSS (if included in the Target BSS to Source BSS Transparent Container) the same PLMN ID as the one received in the *Target Cell Identifier* IE in the PS-HANDOVER-REQUEST PDU. + +Upon reception of the PS-HANDOVER-REQUEST-ACK PDU, the SGSN shall stop timer T13, end the PS Handover Request procedure and start timer T14 for supervision of the PS Handover Complete procedure. + +The target BSS may choose to terminate the PS Handover Request procedure by sending a PS-HANDOVER-REQUEST-NACK PDU to the SGSN due to any of the following reasons: + +- A BSS Context could not be allocated for the MS; +- None of the PFCs in the *PFCs To Be Set-up List* IE of the PS-HANDOVER-REQUEST PDU could be granted the requested QoS; + +- No uplink TBF could be allocated for the MS in the BVCI. + +In addition, the target BSS may choose to terminate the PS Handover Request procedure by sending a PS-HANDOVER-REQUEST-NACK PDU to the SGSN if at least one of the PFCs in the *PFCs To Be Set-up List* IE of the PS-HANDOVER-REQUEST PDU could not be granted the requested QoS and the *Cause* IE indicates a non-critical PS or DTM handover. + +NOTE: The cause values "Better cell", "Traffic" indicate a non-critical PS or DTM handover. + +When a PS-HANDOVER-REQUEST-NACK PDU has been sent, no knowledge of the MS should be kept by the target BSS. + +Except in case of an attempted DTM Handover, when the target BSS decides to terminate the PS Handover Request procedure by sending a PS-HANDOVER-REQUEST-NACK PDU to the SGSN, the *Cause* IE should be set to an appropriate value (e.g. "PFC create failure", "Cell traffic congestion", "Equipment failure" or "O&M intervention"). + +In the case of an attempted DTM Handover, if the target BSS has failed to allocate PS resources, it shall send a PS-HANDOVER-REQUEST-NACK PDU with cause "DTM Handover - PS Allocation failure" to the SGSN. The target BSS may continue with the corresponding Handover Resource Allocation procedure, allocating only a dedicated resource (see 3GPP TS 48.008). + +In the case of an attempted DTM Handover, if the target BSS does not allocate a CS resource, it shall not allocate any PS resources, and shall send a PS-HANDOVER-REQUEST-NACK PDU with cause "DTM Handover - No CS resource" to the SGSN. + +The SGSN may inform the BSS about the contents of SPID in the PS-HANDOVER-REQUEST PDU. In this case the SPID is stored in the BSS. + +### 8a.5.1 Abnormal conditions + +If there is no response from the target BSS to the PS-HANDOVER-REQUEST PDU before timer T13 expires, the SGSN shall initiate the Delete BSS PFC procedure for each of the PFCs in the *PFCs to be Set-up List* IE for the corresponding MS. + +If the timer T24 (see 3GPP TS 48.008) expires and the target BSS has received a PS-HANDOVER-REQUEST PDU (i.e. no corresponding BSSMAP HANDOVER REQUEST message has been received) the target BSS shall terminate the PS Handover Request procedure by sending a PS-HANDOVER-REQUEST-NACK PDU to the SGSN with cause "DTM Handover - T24 expiry". + +If a PS-HANDOVER-REQUEST PDU is received which contains a *CS Indication* IE which corresponds to a DTM Handover attempt which was previously terminated for this MS, then the BSS shall terminate the PS Handover Request procedure by sending a PS-HANDOVER-REQUEST-NACK PDU to the SGSN with cause "DTM Handover - Invalid CS Indication IE". Any ongoing Handover Resource Allocation procedure (see 3GPP TS 48.008) for this mobile shall not be aborted in this case. + +NOTE: Other failure cases related to the expiry of the A interface timer T24 are described in 3GPP TS 48.008). + +If timer T14 expires before the SGSN receives a PS-HANDOVER-COMPLETE PDU, it shall initiate the Delete BSS PFC procedure for each allocated PFC (i.e. for each PFC included in the *List of Set-up PFCs* IE in the corresponding PS-HANDOVER-REQUEST-ACK PDU) towards the target BSS to release the resources allocated for all PFCs allocated for the MS. + +## 8a.6 PS Handover Complete procedure + +The target BSS shall initiate the PS Handover Complete procedure: + +- in the case of PS Handover, on reception of the first correct RLC data block (sent in normal burst format as defined in 3GPP TS 44.060) from the MS in the target Cell; +- in the case of DTM Handover, on receipt of an RR HANDOVER COMPLETE message on the main DCCH in the target cell (see 3GPP TS 44.018). + +The target BSS shall send a PS-HANDOVER-COMPLETE PDU to the SGSN. + +From this point in time, the target BSS shall be prepared to receive uplink LLC PDUs from the corresponding MS on the allocated resources. Uplink LLC PDUs shall be sent from the target BSS to the SGSN with the TLLI received through the PS Handover Request procedure. + +The target BSS supporting inter-RAT PS handover to UTRAN shall request the *Inter RAT Handover Info* IE from the SGSN upon successful PS handover completion in the following cases: + +- PS handover from UTRAN to GERAN; in this case the BSS shall replace the *Inter RAT Handover Info* received from the source RNC with the new value received from the SGSN in the PS-HANDOVER-COMPLETE-ACK PDU. +- PS handover from GERAN *A/Gb mode* if it received PS-HANDOVER-REQUEST PDU with *Reliable Inter RAT Handover Info* IE missing or set to "0"; in this case the BSS shall replace the *Inter RAT Handover Info* received from the source BSS with the new value received from the SGSN in the PS-HANDOVER-COMPLETE-ACK PDU. +- PS handover from GERAN *A/Gb mode* if the "*INTER RAT HANDOVER INFO*" is missing in the *Source BSS to Target BSS Transparent Container* IE. +- PS handover from E-UTRAN if the "*INTER RAT HANDOVER INFO*" is missing in the *Source BSS to Target BSS Transparent Container* IE. + +At reception of the PS-HANDOVER-COMPLETE PDU, the SGSN shall stop timer T14 (if running) and + +- in case of non-optimised intra-BSS or intra-SGSN inter-BSS PS Handover, initiate the Delete BSS PFC procedure(s) towards the source BSS for each PFC corresponding to the MS in the source cell as described in sub-clause 8a.3; or +- in case of inter-SGSN PS Handover, send a Forward Relocation Complete message to the old SGSN (see 3GPP TS 29.060). The old SGSN shall initiate a Delete BSS PFC procedure for each PFC corresponding to the MS in the source cell towards the source BSS as described in sub-clause 8a.3. + +### 8a.6.1 Abnormal conditions + +If the SGSN does not receive a PS-HANDOVER-COMPLETE PDU before timer T14 expires, it shall initiate the Delete BSS PFC procedure towards the target BSS to release the resources for all PFCs allocated for the MS. + +If a PS-HANDOVER-COMPLETE PDU refers to an MS which is unknown in the SGSN, it shall be ignored. + +## 8a.7 PS Handover Cancel procedure + +The source BSS may at any time, up to the time when the PS HANDOVER COMMAND or DTM HANDOVER COMMAND message is sent to the MS (as defined in 3GPP TS 44.060), initiate the PS Handover Cancel procedure. The reasons for cancellation could e.g. be "T12 expiry", "MS back on old channel", "Not all requested PFCs created" or "CS cause". + +The source BSS shall initiate the PS Handover Cancel procedure if the cell change attempt fails and the MS returns to the old cell and sends either a PACKET CELL CHANGE FAILURE message as specified in 3GPP TS 44.060 (for PS Handover) or an RR HANDOVER FAILURE message as specified in 3GPP TS 44.018 (for DTM Handover) using the old radio resources. + +During the normal intra-BSS or inter-BSS PS Handover, the source BSS shall also initiate the PS Handover Cancel procedure if it detects the loss of radio contact with MS (see 3GPP TS 44.060). The cause value in the PS-HANDOVER-CANCEL PDU shall be set to "Radio contact lost with MS". In the case of DTM Handover, the source BSS shall initiate the PS Handover Cancel procedure in the following additional cases defined in the list of Abnormal Cases for the Handover Required Indication procedure (see 3GPP TS 48.008): + +- a) Timer T23 expires and the source BSS has received a PS-HANDOVER-REQUIRED-ACK PDU from the SGSN; +- b) The source BSS receives a PS-HANDOVER-REQUIRED-ACK PDU and a BSSMAP HANDOVER REQUIRED REJECT message (see 3GPP TS 48.008); +- c) If the DTM Handover is ongoing and T8 expires (see 3GPP TS 48.008). + +The cause value in the PS-HANDOVER-CANCEL PDU shall be set to: + +- in case a) above: "DTM Handover - T23 expiry"; +- in case b) above: "DTM Handover - MSC error"; +- in case c) above: "Radio contact lost with MS". + +When the source BSS decides to cancel an ongoing PS handover or DTM Handover, it shall initiate the PS Handover Cancel procedure by sending a PS-HANDOVER-CANCEL PDU to the SGSN. The source BSS shall regard all procedures related to PS handover or DTM Handover for the given MS as terminated after having sent the PS-HANDOVER-CANCEL PDU to the SGSN. + +Upon reception of a PS-HANDOVER-CANCEL PDU, (in the case of Inter-SGSN PS handover or Inter-SGSN DTM handover) the SGSN shall initiate a Forward Relocation Cancel procedure according to 3GPP TS 29.060. + +Upon reception of a PS-HANDOVER-CANCEL PDU, (in the case of Intra-SGSN PS handover or Intra-SGSN DTM handover or Inter-RAT PS handover) the SGSN shall + +- in case of GERAN *A/Gb mode* to GERAN *A/Gb mode* PS/DTM handover, initiate the Delete BSS PFC procedure towards the target BSS to release the resource allocated for the MS. +- in case of GERAN *A/Gb mode* to UTRAN PS/DTM handover, initiate the Iu Release procedure towards the target RNC to release the resource allocated for the UE (see 3GPP TS 25.413). +- in case of GERAN *A/Gb mode* to E-UTRAN PS handover, initiate the Relocation Cancel procedure towards target MME which initiates the release of the resources allocated for the UE by the target eNB (see 3GPP TS 36.413). + +NOTE: In case of cancellation due to CS call establishment, current behaviour regarding possible suspension of GPRS services applies after the PS Handover Cancel procedure is completed. + +## 8a.7.1 Abnormal conditions + +If a PS-HANDOVER-CANCEL PDU refers to an MS/UE which is unknown in the SGSN, it shall be ignored. + +An SGSN shall ignore a PS-HANDOVER-CANCEL PDU which refers to an MS for which the SGSN has already received a PS-HANDOVER-COMPLETE PDU from the target BSS (in the case of intra-SGSN PS handover) or a FORWARD RELOCATION COMPLETE message from the new SGSN (in the case of inter-SGSN PS handover). + +--- + +## 8b Signalling Procedures between LCS SAPs + +### 8b.1 Location Procedure + +When the SGSN receives a location request, and the BSS supports LCS, the SGSN starts the location procedure by sending a PERFORM-LOCATION-REQUEST PDU. An exception case is when the SGSN supports the MTA procedure and receives a location request (i.e. a "MAP Provide Subscriber Location" message is received from the GMLC) for a MS that supports the MTA procedure (determined by the MS Radio Access Capability of the target MS – see sub-clause 11.3.22) in which case it shall proceed as follows: + +- If the MPM timer is running for the target MS (see sub-clause 8b.2.1) it shall send a system failure indication to the corresponding GMLC. +- If the MPM timer is not running but the Ready timer is running for the target MS the SGSN sends a PERFORM-LOCATION-REQUEST PDU to the BSS managing the serving cell. +- If neither the MPM nor Ready timer is running, the SGSN sends a PAGING-PS PDU indicating 'positioning event triggered' (see sub-clause 10.3.1) to each BSS in the set of BSSs managing cells in the paging area corresponding to the target MS and waits for a page response as described in sub-clause 7.1. + +The SGSN shall provide the BVCI and the NSEI indicating the PTP functional entity (i.e. the cell) upon which the last LLC-PDU was received from the MS as well as the Cell ID received together with that LLC-PDU. The SGSN shall also + +provide the IMSI. If the SGSN has valid DRX Parameters for a TLLI, then the SGSN shall include them in the PDU. If the SGSN has valid eDRX Parameters for a TLLI, then the SGSN shall include them in the PDU. The SGSN shall also provide the downlink Coverage Class associated with the MS, if previously received from the BSS in the UL-UNITDATA PDU. + +If LLC ciphering is not activated at SGSN, SGSN may include “MTA Access Security Required” in the PERFORM LOCATION REQUEST PDU, if integrity protection for the radio access part of the MTA procedure is required. BSS upon receipt of this IE shall request SMLC to perform the location request. The “MTA Access Security Required” may indicate MTA Access Security method or the BSS Duplication Detection method is to be performed. For the case where the MTA Access Security method is performed, on receipt of “MTA Signature” and “MTA Sequence” included in the response sent by SMLC to BSS, the BSS forwards them to SGSN in PERFORM-LOCATION-RESPONSE-PDU as “MTA Signature” IE and “MTA Sequence” IE. SGSN upon receiving PERFORM-LOCATION-RESPONSE-PDU checks the presence of “MTA Signature” and “MTA Sequence”, and if present, generates a local MTA Signature using “MTA Sequence”. The generated local MTA Signature is then compared against received “MTA Signature”. + +If MS Radio Access Capability information is available in the SGSN for the associated MS, the SGSN shall include it in the PERFORM-LOCATION-REQUEST PDU. + +The Location Type indicates which type of location information the SGSN is requesting. The LCS capability IE reports the PS LCS capabilities of the MS and is included by the SGSN if it has been received from the MS. LCS Priority and LCS QoS are provided if available in the SGSN. The SGSN may provide the IMEI of the Mobile Station. + +On receipt of the PERFORM-LOCATION-REQUEST PDU for positioning of the target MS, the BSS transfers the positioning request to the SMLC according to the procedures defined in 3GPP TS 43.059 and 3GPP TS 49.031 and awaits the result. An exception case is when the BSS receives a PERFORM-LOCATION-REQUEST PDU for which the “MultilaterationTiming Advance”, “MS Sync Accuracy” and “BTS Reception Accuracy Level” information elements are included in which case the BSS proceeds as follows: + +- If a packet data transfer is ongoing for the target MS (see 3GPP TS 44.018 [25]) the BSS waits for up to 5 seconds for the packet data transfer to complete (i.e. all TBF resources are released) before sending a positioning request to the SMLC (see 3GPP TS 43.059 and 3GPP TS 49.031). +- Upon completing the ongoing packet data transfer (within 5 seconds) or if no packet resources are assigned upon receiving the PERFORM-LOCATION-REQUEST PDU the BSS sends a positioning request to the SMLC, includes the “MultilaterationTiming Advance”, “MS Sync Accuracy” and “BTS Reception Accuracy Level” information elements therein and awaits the positioning result. +- If packet resources remain assigned for more than 5 seconds after receiving the PERFORM-LOCATION-REQUEST PDU the BSS returns a PERFORM-LOCATION-RESPONSE PDU with a LCS cause value indicating ‘Target MS Unreachable’ (see sub-clause 11.3.58) and aborts the Location procedure. + +The BSS then returns the result of positioning to the SGSN in the PERFORM-LOCATION-RESPONSE PDU and stops the MPM Timer (if running). This PDU contains the PTP BVCI indicating the PTP functional entity (i.e. the cell) upon which the last LLC-PDU was received from the MS, a location estimate and optionally positioning data. Upon reception of the PERFORM-LOCATION-RESPONSE PDU the SGSN stops the MPM timer (if running). + +If assistance data was instead requested by the SGSN for an MS, the BSS transfers the request to the SMLC according to the procedures defined in 3GPP TS 43.059 and 3GPP TS 49.031 and awaits the result. If the Requested GPS or GANSS Assistance Data IE was received from the MS, it is forwarded to the BSS. If the SMLC indicates to the BSS that it was able successfully to transfer this to the MS, the BSS shall return a PERFORM-LOCATION-RESPONSE PDU to the SGSN. This PDU shall contain the PTP BVCI indicating the PTP functional entity (i.e. the cell) upon which the last LLC-PDU was received from the MS but no other optional or conditional information elements. The absence of an LCS Cause parameter in this case implies that the transfer was successful. + +Otherwise, if the deciphering keys were requested for LCS broadcast assistance data, the BSS transfers the request to the SMLC according to the procedures defined in 3GPP TS 43.059 and 3GPP TS 49.031 and awaits the result. If the BSS receives the deciphering keys, the BSS shall send them to the SGSN in a PERFORM-LOCATION-RESPONSE PDU containing also the PTP BVCI indicating the PTP functional entity (i.e. the cell) upon which the last LLC-PDU was received from the MS. + +## 8b.1.1 Unsuccessful Operation + +If the BSS fails to respond to the PERFORM-LOCATION-REQUEST PDU it returns a PERFORM-LOCATION-RESPONSE PDU with a LCS cause value indicating the failure cause. + +If the BSS receives a failure indication from the SMLC it shall send a PERFORM-LOCATION-RESPONSE PDU to the SGSN with the LCS cause value that it received from the SMLC and stop the MPM timer (if running). Upon reception of the PERFORM-LOCATION-RESPONSE PDU the SGSN shall stop the MPM timer (if running). + +## 8b.1.2 Abnormal Conditions + +The following condition may occur: + +If the SGSN needs to abort previously initiated location request, it shall send the PERFORM-LOCATION-ABORT PDU to the BSS. This PDU shall include the PTP BVCI indicating the PTP functional entity (i.e. the cell) upon which the last LLC-PDU was received from the MS. As a result of reception of this PDU the BSS shall abort activities related to positioning of the target MS or assistance data delivery. The BSS shall return a PERFORM-LOCATION-RESPONSE PDU with a cause value indicating the abortion of location request. The SGSN may reattempt the positioning request after the PERFORM-LOCATION-RESPONSE PDU is received from the BSS, but not before the PDU is received. + +If the P-TMSI is reallocated for a target MS during the location procedure, the SGSN shall abort the location procedure. + +If a SUSPEND PDU is received for a target MS during the location procedure, the SGSN shall abort the location procedure. + +If a Routing Area Update request is received from a target MS during the location procedure, the SGSN shall abort the location procedure. + +If an Inter NSE Cell Change, within the same routing area, occurs for a target MS during the location procedure, the SGSN shall provide the new NSEI and new BVCI in the FLUSH-LL PDU sent to the BSS, in order for the BSS to maintain the on-going location procedure, if possible. In case the BSS is unable to maintain the on-going location procedure, then a location abort shall be triggered by the BSS towards the SMLC. + +## 8b.1.3 Overload + +For location requests initiated by the SGSN, the BSC may employ the same procedures defined for an SMLC in 3GPP TS 49.031 to alleviate an overload condition in the BSS. + +## 8b.2 Position Command Procedure + +The position command procedure is used to convey an embedded RRLP message between the BSS and the MS. + +### 8b.2.1 Position Command + +The BSS initiates the position command procedure by sending the POSITION-COMMAND PDU to the SGSN. The procedure is only valid while a location procedure for the target MS is ongoing. + +The POSITION-COMMAND PDU shall include the RRLP Flags and the RRLP APDU information elements and the PTP BVCI indicating the PTP functional entity (i.e. the cell) upon which the last LLC-PDU was received from the MS. The RRLP APDU information element carries the RRLP message and the RRLP Flags information element carries control information for RRLP. + +The SGSN shall extract the RRLP message from the RRLP APDU information element and forward it, together with the RRLP Flags, to the MS in a TOM message carried in an LLC-PDU, see 3GPP TS 44.064. + +An exception case is when the POSITION-COMMAND PDU contains the Multilateration Timer IE (i.e. the MTA procedure has been selected by the SMLC, see sub-clause 11.3.136) and the SGSN determines that it has neither coverage class nor eDRX information available for the target MS. In this case the SGSN sends a POSITION-RESPONSE PDU to the BSS with a 'LCS cause' value indicating 'Target MS Unreachable' (see sub-clause 11.3.58) and aborts the Location procedure. Otherwise, the SGSN proceeds as follows: + +- A MPM timer is started for the target MS and the SGSN shall not attempt to deliver downlink data to that MS or page that MS for as long as the MPM timer continues to run. +- The DL-UNITDATA PDU used to relay the RRLP message to the BSS includes a Timing Advance Request IE (see sub-clause 10.2.1) if the POSITION-COMMAND PDU includes a Timing Advance Request IE (see sub-clause 10.5.4) indicating that timing advance information is needed. + +If an UL-UNITDATA PDU is sent from the BSS to the SGSN for the target MS when a corresponding MPM timer is running then both the BSS and SGSN shall stop their respective MPM timers and abort the location procedure for that MS. + +## 8b.2.2 Position Response + +The SGSN initiates the position response procedure when it receives a TOM message in an LLC-PDU carrying an RRLP message for a target MS. The procedure is only valid while a location procedure for the target MS is ongoing. + +When the SGSN receives a TOM message in an LLC-PDU carrying an RRLP message for a target MS, the SGSN shall extract the RRLP message and forward it to the BSS in a POSITION-RESPONSE PDU. The RRLP message shall be included in the RRLP APDU information element. The RRLP Flags information shall be extracted from the TOM header and be included in the RRLP Flags information element. The POSITION-RESPONSE PDU shall also include the PTP BVCI indicating the PTP functional entity (i.e. the cell) upon which the last LLC-PDU was received from the MS. + +## 8b.2.3 Unsuccessful Operation + +If the SGSN fails to process the POSITION-COMMAND PDU it returns a POSITION-RESPONSE PDU with a LCS cause value indicating the failure cause. + +If a POSITION-COMMAND PDU is received by the SGSN while a location procedure for the target MS is not ongoing a POSITION-RESPONSE PDU with a LCS cause value indicating this failure cause is returned. + +If a POSITION-RESPONSE PDU is received by the BSS while a location procedure for the target MS is not ongoing the BSS shall ignore the PDU. + +--- + +# 8c Signalling procedures between RIM SAPs + +## 8c.1 General + +### 8c.1.1 Introduction + +The following sub-clauses describe the generic RAN Information Management (RIM) procedures which support the exchange of information, via the core network, between peer application entities located in a GERAN, in a UTRAN, in an E-UTRAN or in an eHRPD evolved access network. + +The RIM function is performed through the interaction of the following sub-layers: + +- the underlying part of BSSGP used to transport and route the RIM PDUs from a BSS to an SGSN or from an SGSN to a BSS over the Gb interface; +- the RIM protocol allowing the exchange of the information between two BSSs or between a BSS and an RNS or between a BSS and an eNodeB or between an eNodeB and an eHRPD eAN transparently through the core network; +- the application part on the top of the RIM protocol, referred to as the "RIM application" in this specification. + +NOTE: The functional split between the RIM application and the RIM protocol is provided for information in the present specification and should allow for various implementations. + +The PDUs conveying the RAN information between two RIM entities are including containers that shall not be interpreted by the core network nodes. The exchange of information is triggered by the application in a controlling BSS or, in the case of the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]), by the originating BSS. + +The support of different applications is achieved by the appropriate definition of specific application containers for those applications. + +If the RAN Information Management (RIM) feature is supported by both the BSS and the SGSN, the RIM procedures can be used by any RIM application running on this BSS and requiring information transfer between two BSSs via the core network. + +NOTE: Specific requirements applicable to RIM between GERAN and UTRAN or between GERAN and E-UTRAN and between E-UTRAN and eHRPD eAN are specified in sub-clause 8c.1.4. + +## 8c.1.2 Definitions + +### 8c.1.2.1 Controlling, serving, originating and receiving nodes + +The BSS requesting the information is called the "controlling BSS", the BSS providing the requested information is called the "serving BSS". Considering a pair of BSSs, each may be at the same time both a controlling BSS and a serving BSS. An exception is when an application uses the RIM procedure to transfer information related to the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]) in which case the BSS receiving the information is called the "receiving BSS" and the BSS autonomously providing the information is called the "originating BSS". + +In the present specification the term "BSS" should be understood as "RNC, eNodeB or eAN" in the relevant situations (e. g. NACC from UTRAN/E-UTRAN to GERAN), unless it is explicitly stated otherwise. + +### 8c.1.2.2 RIM association + +A RIM association links unambiguously either a cell in the serving BSS with the controlling BSS that has initiated an information request related to that cell for a given application, or a cell in the controlling BSS with the serving BSS that receives the RAN-INFORMATION-REQUEST PDU for a given application, and is identified by the following pieces of information: + +- Controlling BSS identifier, or, for some particular values of the SON Transfer Application Identity for which the Reporting Cell Identifier is a cell in the controlling BSS (see TS 36.413 [36]), the serving BSS identifier. +- Cell Identifier in the serving BSS, or, for some particular values of the SON Transfer Application Identity (see TS 36.413 [36]), Cell Identifier in the controlling BSS. +- RIM Application Identity +- SON Transfer Application Identity (only applicable if the RIM Application Identity indicates "SON Transfer"). + +### 8c.1.2.3 RIM variables + +In this protocol description, variables are used to represent the status of the relevant entity as a result of an event, such as the reception of an information element in a message. The variables serve the purpose of specifying an abstract model of the protocol entity, and do not therefore impose any particular implementation. + +The following variables are defined in the serving BSS: + +- **MULTIPLE\_REPORTING\_ONGOING**: this variable indicates whether event-based multiple reporting is active or not for a given RIM association. This variable is initialised to FALSE prior to the reception of any request related to the corresponding association from the controlling BSS, then it is updated according to the relevant procedure requirements. +- **MULTIPLE\_REPORT\_SETTING\_RSN**: this variable stores the RSN of the last request having initiated or re-initiated multiple reporting in the serving BSS and is used as a reference to ascertain whether any further request received for this association is outdated or not. The value of this variable is only significant when multiple reporting is active (i.e. **MULTIPLE\_REPORTING\_ONGOING** set to TRUE). + +## 8c.1.3 RIM PDUs description + +### 8c.1.3.1 RAN-INFORMATION-REQUEST PDU + +The RAN-INFORMATION-REQUEST PDU is used by the controlling BSS to request or interrupt an information transfer from a serving BSS. The RAN-INFORMATION-REQUEST PDU specifies the requested operation and the expected information when applicable. The following RAN-INFORMATION-REQUEST PDU type extensions are defined: + +- RAN-INFORMATION-REQUEST/Single Report is used to request a single report. +- RAN-INFORMATION-REQUEST/Multiple Report is used to request event-driven multiple reports. +- RAN-INFORMATION-REQUEST/Stop is used to stop event-driven multiple reports. + +### 8c.1.3.2 RAN-INFORMATION PDU + +The RAN-INFORMATION PDU is used by the serving BSS to transmit the requested information to the controlling BSS or by the originating BSS to autonomously send Multilateration Timing Advance (see 3GPP TS 43.059 [23]) related information to the receiving BSS. The following RAN-INFORMATION PDU type extensions are defined: + +- RAN-INFORMATION/Single Report is used to acknowledge the reception of a RAN-INFORMATION-REQUEST/Single Report and to transmit the requested single report information. The RAN-INFORMATION/Single Report is the only RAN-INFORMATION PDU type extension used to transfer information related to the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]). +- RAN-INFORMATION/Initial Multiple Report is used to acknowledge the reception of a RAN-INFORMATION-REQUEST/Multiple Report and to transmit the initial report of the event-driven multiple reporting. +- RAN-INFORMATION/Multiple Report is used to transmit subsequent reports while event-driven multiple reporting is active. +- RAN-INFORMATION/Stop is used to acknowledge the reception of a RAN-INFORMATION-REQUEST/Stop. +- RAN-INFORMATION/End is used to indicate that the serving BSS will not longer send multiple reports for other reasons than the reception of a RAN-INFORMATION-REQUEST/Stop. + +### 8c.1.3.3 RAN-INFORMATION-ACK PDU + +The RAN-INFORMATION-ACK PDU is used by the controlling BSS to acknowledge the reception of a previous RAN-INFORMATION PDU if so requested by the serving BSS and is used by the serving BSS to acknowledge the reception of a previous RAN-INFORMATION-APPLICATION-ERROR PDU if so requested by the controlling BSS. The RAN-INFORMATION-ACK PDU is also used by the receiving BSS to acknowledge the reception of a previous RAN-INFORMATION PDU autonomously send by the originating BSS. + +### 8c.1.3.4 RAN-INFORMATION-ERROR PDU + +The RAN-INFORMATION-ERROR PDU is used, by either the controlling, the serving or the receiving BSS, to report an error diagnosed at the RIM protocol level to the peer entity. + +### 8c.1.3.5 RAN-INFORMATION-APPLICATION-ERROR PDU + +The RAN-INFORMATION-APPLICATION-ERROR PDU is used by the controlling or the receiving BSS to inform the peer application in the serving BSS about erroneous application information in a previously received RAN-INFORMATION PDU. + +## 8c.1.4 RIM addressing and routing principles + +### 8c.1.4.1 RIM routing address + +#### 8c.1.4.1.1 GERAN BSS identification + +As there is no BSS address identifier defined as such in the 3GPP specifications, RIM makes use of the cell identifier (RAI + CI - see sub-clause 11.3.9 in the present document and 3GPP TS 23.003) of any cell parented by the BSS: + +- the cell identifier of the source cell is used to identify the BSS issuing a RIM PDU; +- the cell identifier of the destination cell is used to identify the BSS towards which a RIM PDU is issued. + +The source cell identifying the BSS issuing a RAN-INFORMATION-REQUEST PDU may be chosen arbitrarily within all the cells parented by the controlling BSS. The deletion or the re-parenting of any cell used as a source cell in the controlling BSS shall trigger the actions described in sub-clause 8c.5.2. + +#### 8c.1.4.1.2 UTRAN RNS identification + +When RIM is used to support the exchange of information with a peer application entity located in UTRAN, the RNC identifier (see sub-clause 11.3.70) shall be used as the RIM Routing Address (Source Cell Identifier or Destination Cell Identifier) to identify the corresponding RNS. + +#### 8c.1.4.1.3 E-UTRAN eNodeB identification + +When RIM is used to support the exchange of information with a peer application entity located in E-UTRAN, an eNB identifier (see sub-clause 11.3.70) shall be used as the RIM Routing Address (Source Cell Identifier or Destination Cell Identifier) to identify the corresponding eNodeB. + +#### 8c.1.4.1.4 eHRPD eAN identification + +When RIM is used to support the exchange of information with a peer application entity located in eHRPD, an *eHRPD Sector ID* IE (see sub-clause 11.3.70) shall be used as the RIM Routing Address (Source Cell Identifier or Destination Cell Identifier) to identify the corresponding eHRPD eAN. + +#### 8c.1.4.2 Routing via the core network + +The RIM PDUs shall be conveyed transparently by the core network toward the destination BSS, RNS, eNodeB or eHRPD eAN. A SGSN or MME shall use the destination address included in each RIM PDU either to send the PDU to the relevant BSS, RNS, eNodeB or eAN through the Gb, the Iu, the S1 or the S121 interface respectively, or to tunnel the PDU towards the target SGSN or MME parenting the destination node through the Gn or S3 interface respectively. + +If a RIM PDU has been tunnelled through the Gn or S3 interface to a destination SGSN or MME that does not support RIM the PDU is discarded without further action. + +#### 8c.1.4.3 Address mirroring + +The following address mirroring principles shall be applied: + +- the serving BSS shall mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the received RAN-INFORMATION-REQUEST PDU into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE, respectively, of the related RAN-INFORMATION PDU(s); +- the controlling BSS shall mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION PDU to be acknowledged into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE, respectively, of the related RAN-INFORMATION-ACK PDU; +- the receiving BSS shall mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION PDU to be acknowledged into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE, respectively, of the related RAN-INFORMATION-ACK PDU; +- the BSS having identified an error at the RIM protocol level in a received RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU shall mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the erroneous PDU into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE, respectively, of the RAN-INFORMATION-ERROR PDU; +- the controlling BSS having identified an error at application level in a received PDU shall mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION PDU which carried the erroneous application information into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE, respectively, of the RAN-INFORMATION-APPLICATION-ERROR PDU. + +### 8c.1.5 In-order delivery and reliable transfer - RSN + +#### 8c.1.5.1 General + +A BSS shall allocate a RIM Sequence Number (RSN) to any RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU or RAN-INFORMATION-APPLICATION-ERROR PDU sent by this BSS. The purpose of the RSN is twofold: + +- to assess whether a RAN-INFORMATION-REQUEST PDU or a RAN-INFORMATION PDU received for a given RIM association is providing up-to-date information or is outdated if having been overtaken by a PDU received previously; +- to identify the PDU acknowledged with a RAN-INFORMATION-ACK PDU or reported in a RAN-INFORMATION-ERROR PDU. + +For the purpose of comparing any RSN value to a given RSN X, the RSN numbering space is halved in two equal parts (see figure 8c.1) located on either sides of RSN X, the half part "below" RSN X (modulo RSN MAX+1) defining the RSN values "older" than RSN X, the half part "above" (modulo RSN MAX+1) RSN X defining the RSN values "newer" than RSN X. + +![Figure 8c.1: Comparing RSN values. A circular diagram representing the RSN numbering space from 0 to RSN MAX = 2**32-1. A point on the circle is labeled RSN X. A dashed line extends from RSN X clockwise to the 0 point, representing RSN values 'older' than RSN X. A solid line extends from RSN X counter-clockwise to the 0 point, representing RSN values 'newer' than RSN X. An arrow at the top of the circle points counter-clockwise, indicating the direction of increasing RSN values. A legend on the right shows a dotted line for 'RSN "older" than RSN X' and a solid line for 'RSN "newer" than RSN X'.](0a3ab80d35c138cc4038b5758f6ff34d_img.jpg) + +Figure 8c.1: Comparing RSN values. A circular diagram representing the RSN numbering space from 0 to RSN MAX = 2\*\*32-1. A point on the circle is labeled RSN X. A dashed line extends from RSN X clockwise to the 0 point, representing RSN values 'older' than RSN X. A solid line extends from RSN X counter-clockwise to the 0 point, representing RSN values 'newer' than RSN X. An arrow at the top of the circle points counter-clockwise, indicating the direction of increasing RSN values. A legend on the right shows a dotted line for 'RSN "older" than RSN X' and a solid line for 'RSN "newer" than RSN X'. + +Figure 8c.1: Comparing RSN values + +### 8c.1.5.2 Allocating RSN values at the sending BSS + +The RSN allocated to a RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU or RAN-INFORMATION-APPLICATION-ERROR PDU shall be greater (modulo $2^{32}$ ) than the RSN value allocated to the previous PDU of the same type sent for this association. In case a given PDU needs to be resent, this PDU may be re-issued with either the same RSN value or an increased RSN value (modulo $2^{32}$ ). + +NOTE: The RSN values allocated to two different PDUs sent successively for a given RIM association need not be consecutive (e.g. the RSN values could be uniquely allocated for a given application or within the whole BSS). However, in order to avoid RSN values depletion, the sending BSS should allocate the next higher RSN value (modulo $2^{32}$ ) to the next PDU to be sent. + +To allow a receiving entity to assess whether two PDUs are received in the same relative order they have been sent or not, the difference between the RSN values allocated to those two PDUs should not exceed an RSN window size of $2^{31}$ (see sub-clause 8c.1.5.3). + +NOTE: In order to cope with RSN values outside the RSN window for a given RIM association, the relevant RIM procedures might be triggered on a timely basis for advancing the RSN window. + +### 8c.1.5.3 Comparing RSN values at the receiving BSS + +Let PDU1 and PDU2 be two PDUs received at the BSS and related to the same RIM association, PDU1 is considered as having been sent earlier than PDU2 if the difference between the associated RSNs is less than an RSN window size of $2^{31}$ (see sub-clause 8c.1.5.2), i.e.: + +$$(RSN2 - RSN1) \bmod (2^{32}) < 2^{31}$$ + +## 8c.1.6 RIM Protocol Version Number + +The *RIM Protocol Version Number* Information Element may be included in a RIM PDU. The *RIM Protocol Version Number* IE indicates which version of the RIM protocol is in use in the BSS having issued the PDU. If this Information Element is omitted, the behaviour of the receiving BSS should be the same as if the value of the *RIM Protocol Version Number* IE was "Version 1". + +Only "Version 1" is defined in the present version of the specification. + +In case the protocol version of the receiving BSS is lower than the version of the sending BSS, and unless otherwise specified in the present specification, the general rules of the BSSGP protocol apply and any unknown parameter shall be ignored. + +## 8c.2 RIM procedures + +### 8c.2.1 General + +The RAN Information Request procedure is initiated by an application in the controlling BSS when it either requires information or wants to stop the transmission of information from a remote peer entity of the same application in the serving BSS. The application on the controlling side indicates the type of operation (Multiple Reports, Single Report, Stop) to the peer entity. + +The RAN Information Send procedure is used to transfer application information between two entities of the same application in two BSSs via the core network. + +The RAN Information Application Error procedure is initiated by an application in the controlling or receiving BSS to transfer application error information to the peer application entity of the same application in the serving BSS. + +The RAN Information Error procedure is initiated by the RIM entity in the controlling, the serving or the receiving BSS to transfer error information to the RIM entity in the peer BSS. + +### 8c.2.2 RAN Information Request procedure + +#### 8c.2.2.1 RAN Information Request/Single Report procedure + +![Sequence diagram showing the RAN Information Request/Single Report procedure between a Controlling BSC and a Serving BSC. The Controlling BSC sends a RAN-INFORMATION-REQUEST/Single Report message to the Serving BSC, which responds with a RAN-INFORMATION/Single Report message.](f40480872b021d2ac7c29202c199b695_img.jpg) + +``` + +sequenceDiagram + participant Controlling BSC + participant Serving BSC + Note left of Controlling BSC: Initiation by the controlling BSS + Controlling BSC->>Serving BSC: RAN-INFORMATION-REQUEST/Single Report + Serving BSC-->>Controlling BSC: RAN-INFORMATION/Single Report + +``` + +Sequence diagram showing the RAN Information Request/Single Report procedure between a Controlling BSC and a Serving BSC. The Controlling BSC sends a RAN-INFORMATION-REQUEST/Single Report message to the Serving BSC, which responds with a RAN-INFORMATION/Single Report message. + +**Figure 8c.2.2.1: RAN Information Request/Single Report Procedure** + +##### 8c.2.2.1.1 Initiation by the controlling BSS + +Upon initiation of the procedure, the controlling BSS shall: + +- 1> set the content of the RAN-INFORMATION-REQUEST/Single Report PDU as follows: + - 2> set the *PDU type* IE, the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE; + - 2> set the content of the *RIM Container* IE as follows: + - 3> set the *RIM Application Identity* IE and the *RIM Sequence Number* IE; + - 3> set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION-REQUEST/Single Report"; + - 3> set the *RIM Protocol Version Number* IE if necessary (see sub-clause 8c.1.6); + - 3> include the *Application Container* IE according to the requirements of the application; +- 1> send the RAN-INFORMATION-REQUEST/Single Report PDU; + +1> start T(RIR); + +#### 8c.2.2.1.2 Reception of a valid RAN-INFORMATION-REQUEST/Single Report PDU by the serving BSS + +Upon reception of a valid RAN-INFORMATION-REQUEST/Single Report PDU as defined in sub-clause 8c.3.2 the serving BSS shall: + +- 1> set the content of the RAN-INFORMATION/Single Report PDU as follows: + - 2> set the *PDU type* IE; mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION-REQUEST/Single Report PDU respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION/Single Report PDU; + - 2> set the content of the *RIM Container* IE as follows: + - 3> set the *RIM Application Identity* IE as required by the application; + - 3> set the *RIM Sequence Number* IE and, if necessary, the *RIM Protocol Version Number* IE (see sub-clause 8c.1.6); + - 3> set the *ACK* indicator in the *RIM PDU Indications* IE to "No ACK requested"; + - 3> set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION/Single Report"; + - 3> include either the RAN-INFORMATION *Application Container* IE or the *Application Error Container* IE according to the requirements of the application; +- 1> send the RAN-INFORMATION/Single Report PDU to the controlling BSS. + +#### 8c.2.2.1.3 Reception of a valid RAN-INFORMATION/Single Report PDU by the controlling BSS + +Upon reception of a valid RAN-INFORMATION/Single Report PDU as defined in sub-clause 8c.3.2 the controlling BSS shall: + +- 1> stop T(RIR) for this RIM association; +- 1> deliver the relevant information to the application; + +and the procedure ends. + +#### 8c.2.2.1.4 Expiration of T(RIR) in the controlling BSS + +If T(RIR) expires the controlling BSS shall as an implementation option either inform the application that the procedure has failed or restart the RAN Information Request/Single Report procedure a finite number of times as described in sub-clause 8c.2.2.1.1. + +#### 8c.2.2.2 RAN Information Request/Multiple Report procedure + +![Sequence diagram showing the RAN Information Request/Multiple Report procedure between a Controlling BSC and a Servina BSC.](05da2a3257316bbf6f448a830dc0380a_img.jpg) + +``` + +sequenceDiagram + participant Controlling BSC + participant Servina BSC + Note left of Controlling BSC: Controlling BSC + Note right of Servina BSC: Servina BSC + Controlling BSC->>Servina BSC: RAN-INFORMATION-REQUEST/Multiple Report + Servina BSC-->>Controlling BSC: RAN-INFORMATION/Multiple Report-Initial + +``` + +The diagram illustrates a sequence of messages between two entities: Controlling BSC and Servina BSC. The Controlling BSC sends a message labeled "RAN-INFORMATION-REQUEST/Multiple Report" to the Servina BSC. The Servina BSC responds with a message labeled "RAN-INFORMATION/Multiple Report-Initial" back to the Controlling BSC. + +Sequence diagram showing the RAN Information Request/Multiple Report procedure between a Controlling BSC and a Servina BSC. + +Figure 8c.2.2.2: Successful RAN Information Request/Multiple Report Procedure + +#### 8c.2.2.2.1 Initiation by the controlling BSS + +Upon initiation of the procedure, the controlling BSS shall: + +- 1> set the content of the RAN-INFORMATION-REQUEST/Multiple Report PDU as follows: +- 2> set the *PDU type* IE, the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE; +- 2> set the content of the *RIM Container* IE as follows: + - 3> set the *RIM Application Identity* IE and the *RIM Sequence Number* IE; + - 3> set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION-REQUEST/Multiple Report"; + - 3> set the *RIM Protocol Version Number* IE if necessary (see sub-clause 8c.1.6); + - 3> include the *Application Container* IE according to the requirements of the application; +- 1> send the RAN-INFORMATION-REQUEST/Multiple Report PDU; +- 1> Start T(RIR); + +#### 8c.2.2.2.2 Reception of a valid RAN-INFORMATION-REQUEST/Multiple Report PDU by the serving BSS + +Upon reception of a valid RAN-INFORMATION-REQUEST/Multiple Report PDU as defined in sub-clauses 8c.3.2 the serving BSS shall: + +- 1> if MULTIPLE\_REPORTING\_ONGOING is set to TRUE for this RIM association and if the received RAN-INFORMATION-REQUEST/Multiple Report PDU is considered as having been sent earlier (see sub-clause 8c.1.5) than the PDU whose RSN is stored in MULTIPLE\_REPORT\_SETTING\_RSN, then: + - 2> discard the PDU without further actions and the procedure ends; +- 1> otherwise: + - 2> set the MULTIPLE\_REPORTING\_ONGOING variable to TRUE for this RIM association; + - 2> store the *RIM Sequence Number* IE value of the received PDU in the MULTIPLE\_REPORT\_SETTING\_RSN variable; + - 2> set the content of the RAN-INFORMATION/Initial Multiple Report PDU as follows: + - 3> set the *PDU type* IE; mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION-REQUEST/Multiple Report PDU respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION/Initial Multiple Report PDU; + - 3> set the content of the *RIM Container* IE as follows: + - 4> set the *RIM Application Identity* IE as required by the application; + - 4> set the *RIM Sequence Number* IE and, if necessary, the *RIM Protocol Version Number* IE (see sub-clause 8c.1.6); + - 4> set the *ACK* indicator in the *RIM PDU Indications* IE to "No ACK requested"; + - 4> set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION/Initial Multiple Report"; + - 4> include either the RAN-INFORMATION *Application Container* IE or the *Application Error Container* IE according to the requirements of the application; + - 2> send the RAN-INFORMATION/Initial Multiple Report PDU. + +### 8c.2.2.2.3 Reception of a valid RAN-INFORMATION PDU/Initial Multiple Report PDU by the controlling BSS + +Upon reception of a valid RAN-INFORMATION/Initial Multiple Report PDU as defined in sub-clause 8c.3.2 the controlling BSS shall: + +- 1) stop T(RIR) for this RIM association; +- 1) deliver the relevant information to the application; + +and the procedure ends. + +### 8c.2.2.2.4 Expiration of T(RIR) in the controlling BSS + +If T(RIR) expires the controlling BSS shall as an implementation option either inform the application that the procedure has failed or restart the RAN Information Request/Multiple Report procedure a finite number of times as described in sub-clause 8c.2.2.2.1. + +### 8c.2.2.3 RAN Information Request/Stop procedure + +![Sequence diagram for RAN Information Request/Stop Procedure. It shows two lifelines: Controlling BSC and Serving BSC. The Controlling BSC sends a RAN-INFORMATION-REQUEST/Stop message to the Serving BSC. The Serving BSC then sends a RAN-INFORMATION/Stop message back to the Controlling BSC.](d15e2d3e8dd9157eb7f0cc120097484a_img.jpg) + +``` + +sequenceDiagram + participant Controlling BSC + participant Serving BSC + Note left of Controlling BSC: Initiation by the controlling BSS + Controlling BSC->>Serving BSC: RAN-INFORMATION-REQUEST/Stop + Note right of Serving BSC: Reception by the serving BSS + Serving BSC-->>Controlling BSC: RAN-INFORMATION/Stop + +``` + +Sequence diagram for RAN Information Request/Stop Procedure. It shows two lifelines: Controlling BSC and Serving BSC. The Controlling BSC sends a RAN-INFORMATION-REQUEST/Stop message to the Serving BSC. The Serving BSC then sends a RAN-INFORMATION/Stop message back to the Controlling BSC. + +**Figure 8c.2.2.3: RAN Information Request/Stop Procedure** + +#### 8c.2.2.3.1 Initiation by the controlling BSS + +Upon initiation of the procedure, the controlling BSS shall: + +- 1) set the content of the RAN-INFORMATION-REQUEST/Stop PDU as follows: + - 2) set the *PDU type* IE, the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE; + - 2) set the content of the *RIM Container* IE as follows: + - 3) set the *RIM Application Identity* IE and the *RIM Sequence Number* IE; + - 3) set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION-REQUEST/Stop"; + - 3) set the *RIM Protocol Version Number* IE if necessary (see sub-clause 8c.1.6); + - 3) include the *Application Container* IE according to the requirements of the application; +- 1) send the RAN-INFORMATION-REQUEST/Stop PDU; +- 1) start T(RIR). + +#### 8c.2.2.3.2 Reception of a valid RAN-INFORMATION-REQUEST/Stop PDU by the serving BSS + +Upon reception of a valid RAN-INFORMATION-REQUEST/Stop PDU as defined in sub-clause 8c.3.2, the serving BSS shall: + +- 1) if MULTIPLE\_REPORTING ONGOING is set to TRUE for this RIM association and if the received RAN-INFORMATION-REQUEST/Stop PDU is considered as having been sent earlier (see sub-clause 8c.1.5) than the PDU whose RSN is stored in MULTIPLE\_REPORT\_SETTING\_RSN, then: + +- 2> discard the PDU without further actions and the procedure ends; +- 1> otherwise: + - 2> set the MULTIPLE\_REPORTING\_ONGOING variable to FALSE for this RIM association; + - 2> set the content of the RAN-INFORMATION/Stop as follows: + - 3> set the *PDU type* IE; mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION-REQUEST/Stop PDU respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION/Stop PDU; + - 3> set the content of the *RIM Container* IE as follows: + - 4> set the *RIM Application Identity* IE as required by the application; + - 4> set the *RIM Sequence Number* IE and, if necessary, the *RIM Protocol Version Number* IE (see sub-clause 8c.1.6); + - 4> set the *ACK* indicator in the *RIM PDU Indications* IE to "No ACK requested"; + - 4> set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION/Stop"; + - 4> include either the *Application Container* IE or the *Application Error Container* IE according to the requirements of the application; + - 2> send the RAN-INFORMATION/Stop PDU. + +#### 8c.2.2.3.3 Reception of a valid RAN-INFORMATION/Stop PDU by the controlling BSS + +Upon reception of a valid RAN-INFORMATION/Stop PDU as defined in sub-clause 8c.3.2 the controlling BSS shall: + +- 1> stop T(RIR) for this RIM association; +- 1> deliver the relevant information to the application; + +and the procedure ends. + +#### 8c.2.2.3.4 Expiration of T(RIR) in the controlling BSS + +If T(RIR) expires the controlling BSS shall as an implementation option either inform the application that the procedure has failed or restart the RAN Information Request/Stop procedure a finite number of times as described in sub-clause 8c.2.2.3.1. + +### 8c.2.3 RAN Information Send procedure + +![Sequence diagram showing the Acknowledged RAN Information Send procedure between a Controlling BSC and a Serving BSC.](8fe194ec0e70ac418890f8f1ad02a102_img.jpg) + +``` + +sequenceDiagram + participant Controlling BSC + participant Serving BSC + Note left of Controlling BSC: (Implied RAN-INFORMATION-REQUEST) + Serving BSC->>Controlling BSC: RAN-INFORMATION/Multiple Report or /End + Controlling BSC->>Serving BSC: RAN-INFORMATION-ACK + +``` + +The diagram illustrates the interaction between a Controlling BSC and a Serving BSC. The Controlling BSC sends a request (implied by the context of the procedure name). The Serving BSC responds with a 'RAN-INFORMATION/Multiple Report or /End' message. The Controlling BSC then replies with a 'RAN-INFORMATION-ACK' message. + +Sequence diagram showing the Acknowledged RAN Information Send procedure between a Controlling BSC and a Serving BSC. + +Fig 8c.2.3: Acknowledged RAN Information Send procedure + +### 8c.2.3a Autonomous RAN Information Send procedure + +![Sequence diagram of the Acknowledged Autonomous RAN Information Send procedure. It shows two lifelines: 'Receiving BSC' on the left and 'Originating BSC' on the right. The Originating BSC sends a 'RAN-INFORMATION/Single Report' message to the Receiving BSC. The Receiving BSC then sends a 'RAN-INFORMATION-ACK' message back to the Originating BSC.](28f2f470a7b2446ae5f525123534383c_img.jpg) + +``` + +sequenceDiagram + participant Originating BSC + participant Receiving BSC + Note left of Originating BSC: Initiation by the originating BSS + Originating BSC->>Receiving BSC: RAN-INFORMATION/Single Report + Receiving BSC-->>Originating BSC: RAN-INFORMATION-ACK + +``` + +Sequence diagram of the Acknowledged Autonomous RAN Information Send procedure. It shows two lifelines: 'Receiving BSC' on the left and 'Originating BSC' on the right. The Originating BSC sends a 'RAN-INFORMATION/Single Report' message to the Receiving BSC. The Receiving BSC then sends a 'RAN-INFORMATION-ACK' message back to the Originating BSC. + +**Fig 8c.2.3: Acknowledged Autonomous RAN Information Send procedure** + +#### 8c.2.3a.1 Initiation by the originating BSS + +This RIM procedure is used for sending Multilateration Timing Advance related information from an originating BSS to a receiving BSS. + +The autonomous RAN Information Send procedure is initiated by the application in the originating BSS when it realizes there is multilateration related information to be sent (using the RAN-INFORMATION/Single Report PDU) and it has not triggered the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]). + +Upon initiation of the procedure, the originating BSS shall: + +1. set the content of the RAN-INFORMATION PDU as follows: + - a. set the *PDU type* IE, the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value where the *Destination Cell Identifier* IE corresponds to the 8 octet *Source Identity IE (Cell Identity+Routing Area Identity)* received in an uplink RLC data block as part of a Multilateration Timing Advance procedure (see 3GPP TS 44.060 [22]); + - b. set the content of the *RIM Container* IE as follows: + - i set the *RIM Application Identity* IE and the *RIM Sequence Number* IE; + - ii set the *RIM Protocol Version Number* IE if necessary (see sub-clause 8c.1.6) + - iii set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION/Single Report"; + - iv for a RAN-INFORMATION/Single Report PDU, set the *ACK* indicator to "ACK requested"; + - v set the *Application Container* IE according to the requirements of the Multilateration Timing Advance application (see sub-clause 11.3.63.2.6); +2. send the RAN-INFORMATION PDU; +3. if the *ACK* indicator has been set to "ACK requested", start a T(RI) instance for this RAN-INFORMATION PDU; +4. otherwise the procedure ends. + +#### 8c.2.3a.2 Reception of a valid RAN-INFORMATION PDU by the receiving BSS + +Upon reception of a valid RAN-INFORMATION/Single Report the receiving BSS shall: + +1. deliver the relevant information to the application; + +- a) if the *ACK* indicator in the *RIM PDU Indications* IE included in the RIM container of the RAN-INFORMATION PDU is set to "ACK requested", the receiving BSS shall: + - 2. set the content of the RAN-INFORMATION-ACK PDU as follows: + - i set the *PDU type* IE; mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION PDU respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION-ACK PDU; + - ii set the content of the *RIM Container* IE as follows: + - ii.1 mirror the *RIM Sequence Number* IE value and the *RIM Application Identity* IE value included in the RIM container of the RAN-INFORMATION PDU respectively into the *RIM Sequence Number* IE and the *RIM Application Identity* IE of the RAN-INFORMATION-ACK PDU; + - ii.2 set, if necessary, the *RIM Protocol Version Number* IE (see sub-clause 8c.1.6); + - 3. send the RAN-INFORMATION-ACK PDU. +- b) otherwise, the procedure ends. + +### 8c.2.3a.3 Reception of a valid RAN-INFORMATION-ACK PDU in the originating BSS + +Upon reception of a valid RAN-INFORMATION-ACK PDU as defined in sub-clause 8c.3.2 the originating BSS shall: + +- 1. if the *RIM Sequence Number* IE value contained in the RAN-INFORMATION-ACK PDU matches the RSN of the RAN-INFORMATION PDU having initiated the procedure then: + - a) stop the T(RI) instance corresponding to the acknowledged PDU; + +and the procedure ends. + +### 8c.2.3a.4 Expiration of T(RI) in the originating BSS + +Upon expiration of the T(RI) instance the originating BSS shall, as an implementation option, either inform the application that the procedure has failed or restart the RAN Information Send procedure a finite number of times as described in sub-clause 8c.2.3.1. + +#### 8c.2.3.1 Initiation by the serving BSS + +If multiple reporting has been requested for a given RIM association (i.e. the *MULTIPLE\_REPORTING\_ONGOING* variable is set to TRUE), the RAN Information Send procedure is initiated by the application in the serving BSS either to send updated information (using the RAN-INFORMATION/Multiple Report PDU) or to indicate that multiple reporting has been deactivated on the serving BSS side (using the RAN-INFORMATION/End PDU). + +Upon initiation of the procedure, the serving BSS shall: + +- 1> set the content of the RAN-INFORMATION PDU as follows: + - 2> set the *PDU type* IE, mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION-REQUEST/Multiple Report PDU that is identified by the RSN stored in the *MULTIPLE\_REPORT\_SETTING\_RSN* variable respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION PDU; + - 2> set the content of the *RIM Container* IE as follows: + - 3> mirror the *RIM Application Identity* IE value of the RAN-INFORMATION-REQUEST/Multiple Report PDU that is identified by the RSN stored in the *MULTIPLE\_REPORT\_SETTING\_RSN* variable into the *RIM Application Identity* IE of the RAN-INFORMATION PDU; + - 3> set the *RIM Sequence Number* IE and, if necessary, the *RIM Protocol Version Number* IE (see sub-clause 8c.1.6); + - 3> set the *PDU Type Extension* field in the *RIM PDU Indications* IE to "RAN-INFORMATION/Multiple Report" or "RAN-INFORMATION/End" as required by the application; + +- 3> for a RAN-INFORMATION/Multiple Report PDU, set the *ACK* indicator to the value required by the application; for a RAN-INFORMATION/End PDU, set the *ACK* indicator to "ACK requested"; +- 3> set the *Application Container* IE according to the requirements of the application; +- 1> if the RAN-INFORMATION PDU is a RAN-INFORMATION/End (multiple reporting deactivated), set the *MULTIPLE\_REPORTING\_ONGOING* variable to FALSE; +- 1> send the RAN-INFORMATION PDU; +- 1> if the *ACK* indicator has been set to "ACK requested", start a T(RI) instance for this RAN-INFORMATION PDU; +- 1> otherwise the procedure ends. + +### 8c.2.3.2 Reception of a valid RAN-INFORMATION PDU by the controlling BSS + +Upon reception of a valid RAN-INFORMATION/Multiple Report or RAN-INFORMATION/End PDU as defined in sub-clause 8c.3.2 the controlling BSS shall: + +- 1> deliver the relevant information to the application; + - 1> if the *ACK* indicator in the *RIM PDU Indications* IE included in the RIM container of the RAN-INFORMATION PDU is set to "ACK requested", the controlling BSS shall: + - 2> set the content of the RAN-INFORMATION-ACK PDU as follows: + - 3> set the *PDU type* IE; mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION PDU respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION-ACK PDU; + - 3> set the content of the *RIM Container* IE as follows: + - 4> mirror the *RIM Sequence Number* IE value and the *RIM Application Identity* IE value included in the RIM container of the RAN-INFORMATION PDU respectively into the *RIM Sequence Number* IE and the *RIM Application Identity* IE of the RAN-INFORMATION-ACK PDU; + - 4> set, if necessary, the *RIM Protocol Version Number* IE (see sub-clause 8c.1.6); +- NOTE: If the RAN-INFORMATION PDU is a RAN-INFORMATION/End, the controlling BSS shall consider that multiple reporting is deactivated for this RIM association in the serving BSS. +- 2> send the RAN-INFORMATION-ACK PDU. + - 1> otherwise, the procedure ends. + +### 8c.2.3.3 Reception of a valid RAN-INFORMATION-ACK PDU in the serving BSS + +Upon reception of a valid RAN-INFORMATION-ACK PDU as defined in sub-clause 8c.3.2 the serving BSS shall: + +- 1> if the *RIM Sequence Number* IE value contained in the RAN-INFORMATION-ACK PDU matches the RSN of the RAN-INFORMATION PDU having initiated the procedure then: + - 2> stop the T(RI) instance corresponding to the acknowledged PDU; + +and the procedure ends. + +### 8c.2.3.4 Expiration of T(RI) in the serving BSS + +Upon expiration of the T(RI) instance the serving BSS shall, as an implementation option, either inform the application that the procedure has failed or restart the RAN Information Send procedure a finite number of times as described in sub-clause 8c.2.3.1. + +## 8c.2.4 RAN Information Application Error procedure + +![Sequence diagram illustrating the RAN Information Application Error procedure. A 'Controlling BSC Or Receiving BSC' sends a 'RAN-INFORMATION-APPLICATION-ERROR' message to a 'Serving BSC or Originating BSC', which then responds with a 'RAN-INFORMATION-ACK' message.](f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg) + +``` + +sequenceDiagram + participant Controlling BSC Or Receiving BSC + participant Serving BSC or Originating BSC + Note left of Controlling BSC: Initiation by the controlling or receiving BSS + Controlling BSC->>Serving BSC: RAN-INFORMATION-APPLICATION-ERROR + Note right of Serving BSC: Reception of a valid RAN-INFORMATION-APPLICATION-ERROR PDU by the serving BSS + Serving BSC-->>Controlling BSC: RAN-INFORMATION-ACK + +``` + +Sequence diagram illustrating the RAN Information Application Error procedure. A 'Controlling BSC Or Receiving BSC' sends a 'RAN-INFORMATION-APPLICATION-ERROR' message to a 'Serving BSC or Originating BSC', which then responds with a 'RAN-INFORMATION-ACK' message. + +**Fig 8c.2.4: RAN Information Application Error procedure** + +### 8c.2.4.1 Initiation by the controlling or receiving BSS + +Upon initiation of the procedure, the controlling/receiving BSS shall: + +1. set the content of the RAN-INFORMATION-APPLICATION-ERROR PDU as follows: + - a) set the *PDU type* IE, mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION PDU with the erroneous application container respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION-APPLICATION-ERROR PDU; + - b) set the content of the *RIM Container* IE as follows: + - i set the *RIM Application Identity* IE and the *RIM Sequence Number* IE; + - ii set the *RIM Protocol Version Number* IE if necessary (see sub-clause 8c.1.6); + - iii set the *ACK* indicator in the *RIM PDU Indications* IE according to the requirements of the application; + - iv include the *Application Error Container* IE according to the requirements of the application +2. send the RAN-INFORMATION-APPLICATION-ERROR PDU to the serving/originating BSS; +3. if the *ACK* indicator has been set to "ACK requested", start a T(RIAE) instance for this RAN-INFORMATION-APPLICATION-ERROR PDU; +4. otherwise the procedure ends. + +### 8c.2.4.2 Reception of a valid RAN-INFORMATION-APPLICATION-ERROR PDU by the serving BSS + +Upon reception of a valid RAN-INFORMATION-APPLICATION-ERROR PDU as defined in sub-clause 8c.3.2 the serving BSS shall: + +- 1> deliver the relevant information to the application; +- 1> if the *ACK* indicator in the *RIM PDU Indications* IE included in the RIM container of the RAN-INFORMATION-APPLICATION-ERROR PDU is set to "ACK requested", then the serving BSS shall: + - 2> set the content of the RAN-INFORMATION-ACK PDU as follows: + +- 3> set the *PDU type* IE, mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the RAN-INFORMATION-APPLICATION-ERROR PDU respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION-ACK PDU; +- 3> set the content of the *RIM Container* IE as follows: + - 4> mirror the *RIM Sequence Number* IE value and the *RIM Application Identity* IE value included in the RIM container of the RAN-INFORMATION-APPLICATION-ERROR PDU respectively into the *RIM Sequence Number* IE and the *RIM Application Identity* IE of the RAN-INFORMATION-ACK PDU; + - 4> set the *RIM Protocol Version Number* IE if necessary (see sub-clause 8c.1.6); +- 2> send the RAN-INFORMATION-ACK PDU. +- 1> otherwise, the procedure ends. + +### 8c.2.4.3 Reception of a valid RAN-INFORMATION-ACK PDU by the controlling or receiving BSS + +Upon reception of a valid RAN-INFORMATION-ACK PDU as defined in sub-clause 8c.3.2, the controlling or receiving BSS shall: + +- 1> if the *RIM Sequence Number* IE value contained in the RAN-INFORMATION-ACK PDU matches the RSN of the RAN-INFORMATION-APPLICATION-ERROR PDU having initiated the procedure +- 2> then stop the T(RIAE) instance corresponding to the acknowledged PDU; +- 1> else discard the PDU without further action; + +and the procedure ends. + +### 8c.2.4.4 Expiration of T(RIAE) in the controlling or receiving BSS + +At the expiration of the T(RIAE) instance corresponding to the RAN-INFORMATION-APPLICATION-ERROR PDU sent previously by the controlling or receiving BSS, the controlling or receiving BSS shall, as an implementation option, either inform the application that the procedure has failed or restart the RAN Information Application Error procedure a finite number of times as described in sub-clause 8c.2.4.1. + +## 8c.2.5 RAN Information Error procedure + +![Sequence diagram of the RAN Information Error procedure. Two vertical lifelines represent BSCs. The left lifeline is labeled 'Controlling/Serving/ Receiving/Originating BSC' and the right lifeline is labeled 'Serving/Controlling/ Originating/Receiving BSC'. A dashed horizontal line between them is labeled 'RIM procedure'. A solid horizontal arrow labeled 'RAN-INFORMATION-ERROR' points from the left lifeline to the right lifeline.](94c8aee0680a2ea73faab37ba2a0963f_img.jpg) + +``` + +sequenceDiagram + participant LeftBSC as Controlling/Serving/ +Receiving/Originating +BSC + participant RightBSC as Serving/Controlling/ +Originating/Receiving +BSC + Note over LeftBSC, RightBSC: RIM procedure + LeftBSC->>RightBSC: RAN-INFORMATION-ERROR + +``` + +Sequence diagram of the RAN Information Error procedure. Two vertical lifelines represent BSCs. The left lifeline is labeled 'Controlling/Serving/ Receiving/Originating BSC' and the right lifeline is labeled 'Serving/Controlling/ Originating/Receiving BSC'. A dashed horizontal line between them is labeled 'RIM procedure'. A solid horizontal arrow labeled 'RAN-INFORMATION-ERROR' points from the left lifeline to the right lifeline. + +**Fig 8c.2.5: RAN Information Error procedure** + +The RAN Information Error procedure is initiated by the RIM in the source BSS (controlling originating, receiving or serving) to transfer error information to the RIM entity in the associated BSS. + +The procedure is described in sub-clause 8c.3.4. + +## 8c.3 Abnormal conditions + +### 8c.3.0 General + +Two levels of abnormal conditions are defined for the RIM function: + +- the abnormal conditions encountered at the BSSGP level as described in sub-clause 8c.3.1, affecting the routing mechanisms and the related IEs in the RIM PDUs; +- the abnormal conditions encountered in the RIM container as described in sub-clauses 8c.3.2 and 8c.3.3. + +The errors encountered in the application container are handled by the application and are made known to the peer application entity by including the *Application Error container* IE. + +### 8c.3.1 Abnormal conditions at the BSSGP level + +#### 8c.3.1.1 General + +The general protocol error handling as defined in section 9 applies. + +However, the RIM containers being defined as general containers for passing field elements transparently between BSSs via the core network are not subject to error handling at the BSSGP level but only at the RIM protocol level (see sub-clause 8c.3.2). + +Additionally the abnormal conditions defined in the following sub-clauses apply. + +#### 8c.3.1.2 RIM addressing error in BSS + +If a BSS receives from an SGSN a RIM PDU with a *Destination Cell Identifier* IE value which does not match the cell identifier of any of its parented cells, the PDU shall be discarded and a STATUS PDU with the cause value set to "Unknown Destination address" shall be sent back to the SGSN. + +#### 8c.3.1.3 RIM addressing error in the CN + +If an SGSN receives from a BSS a RIM PDU with an invalid destination address, the PDU shall be discarded and a STATUS PDU with the cause value set to "Unknown Destination address" shall be sent back to the BSS. + +#### 8c.3.1.4 RIM PDU addressed to a BSS not supporting RIM + +If an SGSN receives a RIM PDU addressed to a parented BSS that does not support the RIM procedures, the PDU shall be discarded without further action. + +### 8c.3.2 Abnormal conditions encountered in the RIM container + +#### 8c.3.2.1 Unknown RIM Application Identity + +If the RIM container included in a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU contains an unknown value in the *RIM Application Identity* IE, or if the RIM container contains an unknown value in the *SON Transfer Application Identity* IE in case the *RIM Application Identity* IE is set to "SON Transfer", or if the RIM application is disabled when receiving a RAN-INFORMATION-REQUEST PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU with the *RIM Cause* IE set to "Unknown RIM Application Identity or RIM application disabled" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU. + +If the RIM container included in a RAN-INFORMATION-ERROR PDU contains an unknown value in the *RIM Application Identity* IE, or if the RIM container contains an unknown value in the *SON Transfer Application Identity* IE in case the *RIM Application Identity* IE is set to "SON Transfer", the BSS shall discard the RIM PDU without further action. + +#### 8c.3.2.2 Erroneous PDU Type Extension field + +If the *PDU Type Extension* field in the *RIM PDU Indications* IE included in the RIM container of a RAN-INFORMATION-REQUEST PDU does not indicate "RAN-INFORMATION-REQUEST/Multiple Report", "RAN- + +INFORMATION-REQUEST/Stop" or "RAN-INFORMATION-REQUEST/Single Report", the serving BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "PDU not compatible with the feature set" back to the originating BSS (see sub-clause 8c.3.4.2) and shall discard the received PDU. + +If the *PDU Type Extension* field in the *RIM PDU Indications* IE included in the RIM container of a RAN-INFORMATION PDU does not indicate "RAN-INFORMATION/Single Report", "RAN-INFORMATION/Multiple Report", "RAN-INFORMATION/Initial Multiple Report", "RAN-INFORMATION/Stop" or "RAN-INFORMATION/End", the serving BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "PDU not compatible with the feature set" back to the originating BSS (see sub-clause 8c.3.4.2) and shall discard the received PDU. + +### 8c.3.2.3 Missing conditional IE + +If an expected conditional Information Element is not included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "Missing Conditional IE" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU. + +If an expected conditional Information Element is not included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action. + +### 8c.3.2.4 Missing mandatory IE + +If a mandatory Information Element is not included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "Missing Mandatory IE" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU. + +If a mandatory Information Element is not included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action. + +### 8c.3.2.5 Syntactical error in an expected conditional IE + +If a syntactical error is detected in an expected conditional Information Element included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "Conditional IE error" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU. + +If a syntactical error is detected in an expected conditional Information Element included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action. + +### 8c.3.2.6 Syntactical error in a mandatory IE + +If a syntactical error is detected in a mandatory IE included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "Invalid mandatory information" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU. + +For this rule the following exceptions apply: + +- unknown *RIM Application Identity* IE (see sub-clause 8c.3.2.1); or +- erroneous *PDU Type Extension* field (see sub-clause 8c.3.2.2) + +If a syntactical error is detected in a mandatory IE included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action. + +### 8c.3.2.7 Unexpected conditional IE + +If an unexpected conditional Information Element is received in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "Unexpected Conditional IE" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU. + +If an unexpected conditional Information Element is received in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action. + +### 8c.3.2.8 Containers with out-of-sequence information elements + +The receiving BSS may accept RIM containers that include information elements that do not appear to be in the correct sequence. Elements that occur more than once in a RIM container shall be assumed to have been transmitted in the correct order. Recipients that do not accept out of sequence information elements shall regard the RIM container as containing unexpected and/or missing information elements and follow the procedures defined in the rest of this sub-clause 8c.3.2. + +### 8c.3.2.9 Container with semantically incorrect content + +When any IE with semantically incorrect contents is received within a RIM container, the receiving BSS shall react according to the relevant protocol specification. If however no such reactions are specified, the receiving BSS shall ignore that IE and treat the rest of the RIM container. If the rest of the RIM container can no longer be handled because this IE was ignored then the receiving BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the *RIM Cause* IE set to "Semantically incorrect PDU" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU. + +## 8c.3.3 Unexpected RIM PDU + +If a BSS receives a RIM PDU in a case not covered by the RIM procedures specified in sub-clause 8c.2, it shall discard the RIM PDU without further action. + +## 8c.3.4 RIM error reporting + +### 8c.3.4.1 General + +A BSS diagnosing any of the abnormal cases identified in sub-clause 8c.3.2 in a received RIM PDU shall inform the originating BSS by sending in return a RAN-INFORMATION-ERROR PDU as described in sub-clause 8c.3.4.2. + +The tasks to be performed upon reception of the RAN-INFORMATION-ERROR PDU are described in sub-clause 8c.3.4.3. + +### 8c.3.4.2 Sending of a RAN-INFORMATION-ERROR PDU + +A BSS receiving an erroneous RIM PDU according to sub-clause 8c.3.2 shall: + +- 1> set the *PDU type* IE, mirror the *Source Cell Identifier* IE value and the *Destination Cell Identifier* IE value of the erroneous RIM PDU respectively into the *Destination Cell Identifier* IE and the *Source Cell Identifier* IE of the RAN-INFORMATION-ERROR PDU +- 1> set the content of *RIM Container* IE as follows: + - 2> mirror the *RIM Application Identity* IE value of the erroneous RIM PDU into the *RIM Application Identity* IE in the *RIM Container* IE of the RAN-INFORMATION-ERROR PDU; + - 2> set the *RIM Cause* IE and, if necessary, the *RIM Protocol Version Number* IE (see sub-clause 8c.1.6); + - 2> include the complete erroneous RIM PDU in to the *PDU in Error* IE; +- 1> send the RAN-INFORMATION-ERROR PDU. + +### 8c.3.4.3 Reception of a RAN-INFORMATION-ERROR PDU in the BSS + +Upon reception of an erroneous RAN-INFORMATION-ERROR PDU according to sub-clause 8c.3.2 the BSS shall discard the received PDU without further action. + +The actions to be taken upon reception of a valid RAN-INFORMATION-ERROR PDU are an implementation-dependent option. + +## 8c.4 RIM timers + +The following RIM timers are defined: + +- T(RIR) is used in the controlling BSS to control the reception of the response to a previously transmitted RAN-INFORMATION-REQUEST PDU. +- T(RI) is used in the serving BSS used to control the reception of the acknowledgement of a previously transmitted RAN-INFORMATION PDU. +- T(RIAE) is used in the controlling BSS used to control the reception of the acknowledgement of a previously transmitted RAN-INFORMATION-APPLICATION-ERROR PDU. + +**Table 8c.4: RIM timers** + +| Timer | Start | Stop | Action at expiry | +|---------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| T(RIR) | Transmission of a RAN-INFORMATION-REQUEST/Multiple Report PDU | Reception of the answering RAN-INFORMATION/Initial Multiple Report | Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times | +| | Transmission of a RAN-INFORMATION-REQUEST/Single Report PDU | Reception of the answering RAN-INFORMATION/Single Report | Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times | +| | Transmission of a RAN-INFORMATION-REQUEST/Stop PDU | Reception of the answering RAN-INFORMATION/Stop | Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times | +| T(RI) | Transmission of a RAN-INFORMATION/Multiple Report, RAN-INFORMATION/Single Report or RAN-INFORMATION/End PDU | Reception of the answering RAN-INFORMATION-ACK | Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times | +| T(RIAE) | Transmission of a RAN-INFORMATION-APPLICATION-ERROR PDU | Reception of the answering RAN-INFORMATION-ACK | Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times | + +## 8c.5 Action upon deletion of a cell in a BSS + +### 8c.5.0 General + +The deletion of a cell in a BSS should trigger the actions described in this sub-clause to ensure the proper operation of the RIM procedures for RIM associations related to this cell. + +### 8c.5.1 Actions due to the deletion of the cell + +If the deleted cell has to report to one or more controlling BSS(s), the serving BSS parenting the deleted cell shall trigger a RAN Information Send procedure to inform each of the corresponding controlling BSS(s) that multiple reporting has been deactivated by the sending of a RAN-INFORMATION/End PDU. + +The controlling BSS parenting the deleted cell may also decide that, as a consequence of the deletion of this cell, some multiple reports previously requested from some cells parented by other BSS(s) are no longer needed and shall trigger the relevant RAN Information Request/Stop procedure. + +## 8c.5.2 Additional actions in the case the deleted cell is used as a source cell by RIM + +If the cell identifier of the cell being deleted has been used as the *Source Cell Identifier* IE value in a previous RAN-INFORMATION-REQUEST/Multiple report PDU, the deletion of this cell shall trigger the following additional actions to update this information in the serving BSS, as the *Source Cell Identifier* IE is used by the serving BSS to address the controlling BSS (address mirroring - see sub-clause 8c.1.4.3): + +- The controlling BSS parenting this cell shall trigger a RAN Information Request/Stop procedure for each of the involved cells in the serving BSS; +- After the completion of this procedure the parenting BSS shall, if event-based multiple reporting is still needed from the involved cells, trigger further RAN Information Request/Multiple Report procedure(s) with a different cell identifier as *Source Cell Identifier* IE value. + +## 8c.6 Specific requirements related to RIM applications + +### 8c.6.0 General requirements + +Any error condition detected in the *Application Error Container* IE included in the *RIM Container* IE of a valid RIM PDU shall not be reported to the peer application entity. + +Any error condition detected in the *Application Container* IE included in the *RIM Container* IE of an erroneous RIM PDU shall not trigger a RAN Information Application Error procedure. + +A controlling BSS shall not send another RAN-INFORMATION-REQUEST PDU for the same association before the first RAN-INFORMATION-REQUEST PDU has been acknowledged or before T(RIR) associated to this request has expired. + +### 8c.6.1 Requirements related to the NACC RIM application + +The rules specified in this sub-clause apply when the *RIM Application Identity* IE is set to "Network Assisted Cell Change (NACC)": + +- The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request the system information required for NACC operation in the controlling BSS and related to a single cell parented by a serving BSS. The *Destination Cell Identifier* IE of the RAN-INFORMATION-REQUEST PDU shall be set to the value of the *Reporting Cell Identifier* field contained in the application container of the PDU. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION-REQUEST PDU. +- The RAN-INFORMATION PDU is used by a serving BSS to send the system information required for NACC operation (i.e. if a PBCCH is allocated in the cell, PSI1, a consistent set of PSI2 and PSI14 messages; if no PBCCH is allocated in the cell, SI3, SI13 and, if available, SI1 messages - see 3GPP TS 4.060) related to a single reporting cell, to a controlling BSS. +- In the present specification, NACC between UTRAN and GERAN is restricted to the case of a controlling RNS and a serving BSS (i.e. assistance is provided for MSs moving from UTRAN to GERAN) and NACC between E-UTRAN and GERAN is restricted to the case of a controlling eNodeB and a serving BSS (i.e. assistance is provided for MSs moving from E-UTRAN to GERAN). The reporting cell located in the serving BSS is therefore always a GERAN cell and shall be addressed as such (RAI + CI) in the NACC application containers. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Initial Multiple Report PDU and of a RAN-INFORMATION/Single Report PDU, where the *Application Error Container* IE may be included instead. +- When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the set of NACC related (packet) system information for this cell is changed; the NACC application shall request acknowledgements. +- The *Application Container* IE included in the *RIM container* IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell. + +## 8c.6.2 SI3 application + +The rules specified in this sub-clause apply when the *RIM Application Identity* IE is set to "SI3": + +- the RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request system information type 3 related to a single cell parented by a serving BSS. The *Destination Cell Identifier* IE of the RAN-INFORMATION-REQUEST PDU shall be set to the value of the *Reporting Cell Identifier* field contained in the application container of the PDU. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION-REQUEST PDU. +- The RAN-INFORMATION PDU is used by a serving BSS to send system information type 3 related to a single reporting cell, to a controlling BSS. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Initial Multiple Report PDU and of a RAN-INFORMATION/Single Report PDU, where the *Application Error Container* IE may be included instead. +- When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the system information type 3 for this cell is changed; the SI3 application shall request acknowledgements. +- The *Application Container* IE included in the *RIM container* IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell. + +## 8c.6.3 MBMS data channel application + +The rules specified in this sub-clause apply when the *RIM Application Identity* IE is set to "MBMS data channel": + +- The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request the information about the MBMS data channels established in a single cell controlled by a serving BSS. The *Destination Cell Identifier* IE of the RAN-INFORMATION-REQUEST PDU shall be set to the value of the *Reporting Cell Identifier* field contained in the application container of the PDU. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION-REQUEST PDU. +- The RAN-INFORMATION PDU is used by a serving BSS to send the information about the MBMS data channels established in a single reporting cell, to a controlling BSS. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Initial Multiple Report PDU and of a RAN-INFORMATION/Single Report PDU, where the *Application Error Container* IE may be included instead. +- When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the allocation of the MBMS data channel is changed (i.e. established, reconfigured, abnormally released) for any MBMS session ongoing in the reporting cell. The MBMS data channel application shall request acknowledgements. However the normal release (i.e. resulting from a MBMS-SESSION-STOP-REQUEST PDU received from the SGSN) of the MBMS data channel at the end of a session shall not trigger the RAN-Information Send procedure, but assumed implicitly as done at the end of the session by the the controlling BSS. +- The *Application Container* IE included in the *RIM container* IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell. + +## 8c.6.4 Requirements related to the SON Transfer RIM application + +The introduction of generic SON Transfer containers in TS 36.413 [36] means that the RIM procedure itself has to be understood in a more generic way for the SON Transfer RIM application: the RIM procedure triggered by the Controlling BSS is used to exchange between BSSs SON Transfer Request container (controlling ---> serving) and SON Transfer Response container (serving ---> controlling), the precise content of these containers (possibly NULL) being linked with the SON Transfer Application in use. The Reporting Cell Identifier may either identify a cell in the + +serving BSS or in the controlling BSS, depending on the value of the SON Transfer Application Identity as specified in TS 36.413 [36]. + +The rules specified in this sub-clause apply when the *RIM Application Identity* IE is set to "SON Transfer": + +- The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to send the SON Transfer Request container to the serving BSS as specified in TS 36.413 [36]. +- The procedure shall be triggered using single report or multiple reports. +- The RAN-INFORMATION PDU is used by a serving BSS to send the SON Transfer Response Container to a controlling BSS as specified in TS 36.413 [36]. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Initial Multiple Report PDU and of a RAN-INFORMATION/Single Report PDU, where the *Application Error Container* IE may be included instead. +- When multiple reports have been requested, the RAN-Information Send procedure shall be triggered every time a SON Transfer Response Container must be sent. The RAN-Information Send procedure shall be used with lower priority with respect to the MS/UE dedicated signalling. + +## 8c.6.5 Requirements related to the UTRA SI RIM application + +The rules specified in this sub-clause apply when the *RIM Application Identity* IE is set to "UTRA System Information (UTRA SI)": + +- The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request the UTRA system information in the controlling BSS and related to a cell parented by a serving BSS. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION-REQUEST PDU. +- The RAN-INFORMATION PDU is used by a serving BSS to send the UTRA system information related to a cell, to a controlling BSS. +- In the present specification, UTRA SI is transferred only to E-UTRAN. The reporting cell located in the serving BSS is always a cell and shall be addressed by the UTRAN Source Cell ID in the UTRA SI application containers. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Initial Multiple Report PDU and of a RAN-INFORMATION/Single Report PDU, where the *Application Error Container* IE may be included instead. +- When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the set of UTRA system information managed by the UTRA SI RIM application for this cell is changed; the UTRA SI application shall request acknowledgements. +- The *Application Container* IE included in the *RIM container* IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell. + +## 8c.6.6 Multilateration Timing Advance application + +The rules specified in this sub-clause apply when the *RIM Application Identity* IE is set to "Multilateration Timing Advance": + +- The RAN-INFORMATION PDU is used by an originating BSS to send information related to an ongoing Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]), to a receiving BSS. +- The presence of the *Application Container* IE is mandatory in the *RIM Container* IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Single Report PDU, where the *Application Error Container* IE applicable to the Multilateration Timing Advance Application (see sub-clause 11.3.64.6) may be included instead. +- When included, the contents of the *Application Container* IE is set according to the requirements of the Multilateration Timing Advance application as described in sub-clause 11.3.63.2.6. + +## 8d Signalling procedures between MBMS SAPs + +### 8d.1 General + +Upon receiving an MBMS-SESSION-START-REQUEST PDU from the SGSN, if the BSS controls cells in any of the MBMS Service Areas in the MBMS service area list the BSS creates an MBMS Service Context, and acknowledges the SGSN using an MBMS-SESSION-START-RESPONSE PDU. More than one MBMS-SESSION-START-RESPONSE PDU can be sent from one BSS to the SGSN for the same MBMS-SESSION-START-REQUEST PDU. + +Upon receiving an MBMS-SESSION-UPDATE-REQUEST PDU from the SGSN, the BSS updates the MBMS service area list for the ongoing MBMS broadcast service session and acknowledges the SGSN using an MBMS-SESSION-UPDATE-RESPONSE PDU. More than one MBMS-SESSION-UPDATE-RESPONSE PDU can be sent from one BSS to the SGSN for the same MBMS-SESSION-UPDATE-REQUEST PDU. + +At the end of the MBMS Session the BSS receives an MBMS-SESSION-STOP-REQUEST PDU from the SGSN indicating that the MBMS Session can be released. The BSS acknowledges the request to end the MBMS Session by sending the MBMS-SESSION-STOP-RESPONSE PDU to the SGSN. See 3GPP TS 43.246 ([29]). + +### 8d.2 MBMS Session Start + +The BSS creates an MBMS Service Context if the BSS controls cells in the MBMS service area list upon reception of an MBMS-SESSION-START-REQUEST PDU from the SGSN. + +If the data is received by the BSS and no MBMS bearer is established on the radio interface for that MBMS Session the BSS may buffer the data. + +At reception of an MBMS-SESSION-START-REQUEST PDU that leads to an MBMS Service Context creation in the BSS, the BSS shall respond to the SGSN with an MBMS-SESSION-START-RESPONSE PDU with a Cause Value indicating that data transfer shall be initiated on the Point-to-Multipoint BVC from that SGSN. + +The SGSN may include the *Allocation/Retention Priority* information element in the MBMS-SESSION-START-REQUEST PDU. If this information element is received and the BSS supports ARP handling, the BSS shall establish or modify the resources according to the values of the *Allocation/Retention Priority* IE (priority level, pre-emption indicators) and the resource situation as follows: + +- The BSS shall consider the priority level of the requested MBMS bearer, when deciding on the resource allocation. +- The priority levels and the pre-emption indicators may (singularly or in combination) be used to determine whether the MBMS bearer establishment has to be performed unconditionally and immediately. If the requested MBMS bearer is marked as "may trigger pre-emption" and the resource situation requires so, the BSS may trigger the pre-emption procedure which may then cause the forced release of a lower priority bearer which is marked as "pre-emptable". Whilst the process and the extent of the pre-emption procedure is operator-dependent, the pre-emption indicators, if given in the MBMS-SESSION-START-REQUEST PDU, shall be treated as follows: + 1. If the *Pre-emption Capability* IE is set to "may trigger pre-emption", then this allocation request may trigger the pre-emption procedure. The BSS shall only pre-empt bearers (other MBMS bearers or MS specific bearers) with lower priority, in ascending order of priority. + 2. If the *Pre-emption Capability* IE is set to "shall not trigger pre-emption", then this allocation request shall not trigger the pre-emption procedure. + 3. If the *Pre-emption Vulnerability* IE is set to "pre-emptable", then this connection shall be included in the pre-emption process. + 4. If the *Pre-emption Vulnerability* IE is set to "not pre-emptable", then this connection shall not be included in the pre-emption process. + +5. If the *Priority Level* IE is set to "no priority" the given values for the *Pre-emption Capability* IE and *Pre-emption Vulnerability* IE shall not be considered. Instead the values "shall not trigger pre-emption" and "not pre-emptable" shall prevail. +- If the *Allocation/Retention Priority* IE is not given in the MBMS-SESSION-START-REQUEST PDU, the allocation request shall not trigger the pre-emption process and the connection may be pre-empted and considered to have the value "lowest" as priority level. + - The SGSN shall not include, and the BSS shall ignore, any queuing allowed indication in the *Allocation/Retention Priority* IE of the MBMS-SESSION-START-REQUEST PDU. + +The *MBMS Session Repetition Number* IE shall be included in the MBMS-SESSION-START-REQUEST PDU in case the *MBMS Session Identity* IE is included in the same PDU (and vice versa). The *MBMS Session Repetition Number* IE allows the BSS to recognize retransmissions of a specific session of an MBMS bearer service. The value part of this IE may be used for e.g. deciding whether or not to initiate the counting procedure on a per cell basis (see 3GPP TS 44.018, 3GPP TS 44.060) or, in conjunction with the values of *Allocation/Retention Priority* IE, whether or not to establish an MBMS radio bearer for the session on a per cell basis. + +At reception of an MBMS-SESSION-START-REQUEST PDU with the same TMGI IE and MBMS Session Identity IE as an ongoing MBMS Service Context, the BSS shall respond to the SGSN with an MBMS-SESSION-START-RESPONSE PDU with a Cause Value indicating that data transfer has already been initiated on the Point-to-Multipoint BVC from another SGSN. + +At reception of an MBMS-SESSION-START-RESPONSE PDU, the SGSN shall either start data transfer or not depending on the received Cause Value. + +After transmission of the MBMS-SESSION-START-RESPONSE PDU, the BSS shall wait at least the time specified in the value part of the *Time to MBMS Data Transfer* IE included in the MBMS-SESSION-START-REQUEST PDU and at most a time exceeding by 5 seconds the value part of the *Time to MBMS Data Transfer* IE for the first reception of the associated data before the BSS validates whether or not there is another SGSN that previously has sent an MBMS-SESSION-START-REQUEST PDU. + +If after the start of the data flow associated to an MBMS Service Context, the BSS does not receive data for at least 30 seconds and the BSS has not received the MBMS-SESSION-STOP-REQUEST PDU, the BSS validates whether or not there is another SGSN that previously has sent an MBMS-SESSION-START-REQUEST PDU. + +If, in any of the two cases mentioned above, another SGSN has sent an MBMS-SESSION-START-REQUEST PDU, the BSS shall send an MBMS-SESSION-START-RESPONSE PDU to such an SGSN with a Cause Value indicating that data transfer shall be initiated on the Point-to-Multipoint BVC from that SGSN. Otherwise, the BSS shall end the MBMS Service Context. + +In any case, the BSS will send an MBMS-SESSION-START-RESPONSE PDU with a Cause Value indicating that the MBMS Service Context has been released due to interrupted data flow to the SGSN that previously has been ordered to perform data transfer. + +If the BSS does not support any MBMS Service Area in the MBMS Service Area Identity List the BSS will send an MBMS-SESSION-START-RESPONSE PDU to the SGSN with Cause Value indicating that none of the listed MBMS Service Areas are supported by the BSS. + +![Sequence diagram of MBMS Session Start procedure between SGSN and BSS.](d3f0eb93239fde2cb96b2baf46d62d6c_img.jpg) + +``` +sequenceDiagram + participant SGSN + participant BSS + Note left of SGSN: Error: + SGSN->>BSS: MBMS-SESSION-START-REQUEST + BSS-->>SGSN: MBMS-SESSION-START-RESPONSE + BSS-->>SGSN: MBMS-SESSION-START-RESPONSE +``` + +The diagram illustrates the MBMS Session Start procedure between an SGSN and a BSS. It consists of three messages: 1. A solid arrow labeled 'MBMS-SESSION-START-REQUEST' from the SGSN to the BSS. 2. A solid arrow labeled 'MBMS-SESSION-START-RESPONSE' from the BSS back to the SGSN. 3. A dashed arrow labeled 'MBMS-SESSION-START-RESPONSE' from the BSS back to the SGSN, positioned below the first response. + +Sequence diagram of MBMS Session Start procedure between SGSN and BSS. + +Figure 8d.2: MBMS Session Start procedure + +### 8d.2.1 Abnormal Conditions + +In any failure case in BSS the BSS may send an MBMS-SESSION-START-RESPONSE PDU including a Cause Value indicating the reason for the failure. + +If an MBMS-SESSION-START-RESPONSE PDU is not received in response to an MBMS-SESSION-START-REQUEST PDU within T11 seconds, then the MBMS-SESSION-START-REQUEST PDU shall be repeated a maximum of MBMS-SESSION-START-REQUEST-RETRIES attempts. After MBMS-SESSION-START-REQUEST-RETRIES + 1 attempts the procedure is stopped and the O&M is informed. + +## 8d.3 MBMS Session Stop + +The SGSN may terminate an MBMS Session in the BSS by sending the MBMS-SESSION-STOP-REQUEST PDU to the BSS. The SGSN shall include the *MBMS Stop Cause* IE in the MBMS-SESSION-STOP-REQUEST PDU to indicate to the BSS if the MBMS Session termination has been ordered by an upstream node or if the SGSN itself has decided to terminate the MBMS Session (due to e.g. that the last MS that has an active MBMS UE Context for the MBMS Session within the SGSN has left the routing area(s) handled by the BSS). + +The BSS ends an MBMS Service Context upon reception of an MBMS-SESSION-STOP-REQUEST PDU, including the *MBMS Stop Cause* IE indicating that an upstream node is terminating the MBMS Session, from the SGSN and acknowledges with an MBMS-SESSION-STOP-RESPONSE PDU. + +At reception of an MBMS-SESSION-STOP-REQUEST PDU including the *MBMS Stop Cause* IE indicating that the SGSN is terminating the MBMS Session, the BSS shall validate whether or not there is another SGSN that previously has sent an MBMS-SESSION-START-REQUEST PDU or, in case of an MBMS broadcast service session, an MBMS-SESSION-UPDATE-REQUEST PDU. + +If another SGSN has sent an MBMS-SESSION-START-REQUEST PDU or an MBMS-SESSION-UPDATE-REQUEST PDU, the BSS shall send an MBMS-SESSION-START-RESPONSE PDU or an MBMS-SESSION-UPDATE-RESPONSE PDU, respectively, to such an SGSN with a Cause Value indicating that data transfer shall be initiated on the Point-to-Multipoint BVC from that SGSN. Otherwise, the BSS shall end the MBMS Service Context. The BSS shall then acknowledge the MBMS-SESSION-STOP-REQUEST PDU by sending an MBMS-SESSION-STOP-RESPONSE PDU to the SGSN. + +![Sequence diagram of MBMS Session Stop procedure between SGSN and BSS.](f087d3f5d298b3b1634d13ff17879e41_img.jpg) + +``` +sequenceDiagram + participant SGSN + participant BSS + Note left of SGSN: MBMS-SESSION-STOP-REQUEST + SGSN->>BSS: MBMS-SESSION-STOP-REQUEST + Note right of BSS: MBMS-SESSION-STOP-RESPONSE + BSS->>SGSN: MBMS-SESSION-STOP-RESPONSE +``` + +The diagram illustrates the MBMS Session Stop procedure between an SGSN and a BSS. It consists of two main steps: 1. The SGSN sends an MBMS-SESSION-STOP-REQUEST PDU to the BSS. 2. The BSS responds with an MBMS-SESSION-STOP-RESPONSE PDU to the SGSN. + +Sequence diagram of MBMS Session Stop procedure between SGSN and BSS. + +Figure 8d.3: MBMS Session Stop procedure + +### 8d.3.1 Abnormal Conditions + +If an MBMS-SESSION-STOP-RESPONSE PDU is not received in response to an MBMS-SESSION-STOP-REQUEST PDU within T11 seconds, then the MBMS-SESSION-STOP-REQUEST PDU shall be repeated a maximum of MBMS-SESSION-STOP-REQUEST-RETRIES attempts. After MBMS-SESSION-STOP-REQUEST-RETRIES + 1 attempts the procedure is stopped and the O&M is informed. + +## 8d.4 MBMS Session Update + +Upon reception of an MBMS-SESSION-UPDATE-REQUEST PDU from the SGSN for an ongoing MBMS broadcast service session, the BSS creates an MBMS Service Context if the BSS controls cells in the MBMS service area list and there is no ongoing MBMS Service Context identified with the same *TMGI* IE and, if available, *MBMS Session Identity* IE in the BSS. + +Upon reception of an MBMS-SESSION-UPDATE-REQUEST PDU with the same *TMGI* IE and, if available, *MBMS Session Identity* IE as an ongoing MBMS Service Context but with (a) new MBMS Service Area(s) added to the *MBMS* + +*Service Area Identity List* IE, the BSS may send assignments for the ongoing MBMS broadcast service session to the mobile stations in the new MBMS Service Area(s) and repeat notifications to the mobile stations in the old MBMS Service Area(s). + +Upon reception of an MBMS-SESSION-UPDATE-REQUEST PDU with the same *TMGI* IE and, if available, *MBMS Session Identity* IE as an ongoing MBMS Service Context but without (an) old MBMS Service Area(s) included any longer in the *MBMS Service Area Identity List* IE, the BSS shall release MBMS radio bearers relevant to the ongoing MBMS broadcast service session in the old MBMS Service Area(s). + +The *MBMS Session Information* IE shall denote a Broadcast MBMS Session. + +The *Allocation/Retention Priority* IE, if available, and the *MBMS Session Repetition Number* IE, if available, shall be handled by the BSS as described in the MBMS Session Start procedure (see sub-clause 8d.2). + +If the *Allocation/Retention Priority* IE is not present in the MBMS-SESSION-UPDATE-REQUEST PDU, the allocation request shall not trigger the pre-emption process and the connection may be pre-empted and considered to have the value "lowest" as priority level. + +If the data is received by the BSS and no MBMS bearer is established on the radio interface for that MBMS Session, the BSS may buffer the data. + +At reception of an MBMS-SESSION-UPDATE-REQUEST PDU that leads to an MBMS Service Context creation in the BSS, the BSS shall respond to the SGSN with an MBMS-SESSION-UPDATE-RESPONSE PDU with a Cause Value indicating that data transfer shall be initiated on the Point-to-Multipoint BVC from that SGSN. + +At reception of an MBMS-SESSION-UPDATE-REQUEST PDU with the same *TMGI* IE and, if available, *MBMS Session Identity* IE as an ongoing MBMS Service Context and including new and/or removing old MBMS Service Area(s), the BSS shall respond to the SGSN with an MBMS-SESSION-UPDATE-RESPONSE PDU with a Cause Value indicating either that data transfer shall continue on the Point-to-Multipoint BVC from that SGSN (see note) or that data transfer has already been initiated on the Point-to-Multipoint BVC from another SGSN. + +NOTE: The Cause Value indicating that data transfer shall continue on the Point-to-Multipoint BVC from that SGSN is set to the same one denoting that data transfer shall be initiated on the Point-to-Multipoint BVC from that SGSN, i.e. '0001' (see sub-clause 11.3.74). + +If the BSS does not support any MBMS Service Area in the *MBMS Service Area Identity List* IE, the BSS shall send an MBMS-SESSION-UPDATE-RESPONSE PDU to the SGSN with a Cause Value indicating that none of the listed MBMS Service Areas are supported by the BSS. + +At reception of an MBMS-SESSION-UPDATE-RESPONSE PDU, the SGSN shall either start/continue data transfer or not depending on the received Cause Value. + +After transmission of the MBMS-SESSION-UPDATE-RESPONSE PDU, the BSS shall wait at least the time specified in the value part of the *Time to MBMS Data Transfer* IE included in the MBMS-SESSION-UPDATE-REQUEST PDU and at most a time exceeding by 5 seconds the value part of the *Time to MBMS Data Transfer* IE for the first reception of the associated data before the BSS validates whether or not there is another SGSN that previously has sent an MBMS-SESSION-UPDATE-REQUEST PDU or an MBMS-SESSION-START-REQUEST PDU with the same content of the received MBMS-SESSION-UPDATE-REQUEST PDU. + +If after the start of the data flow associated to an MBMS Service Context, the BSS does not receive data for at least 30 seconds and the BSS has not received the MBMS-SESSION-STOP-REQUEST PDU, the BSS validates whether or not there is another SGSN that previously has sent an MBMS-SESSION-UPDATE-REQUEST PDU or an MBMS-SESSION-START-REQUEST PDU with the same content of the received MBMS-SESSION-UPDATE-REQUEST PDU. + +If, in any of the two cases mentioned above, another SGSN has sent an MBMS-SESSION-UPDATE-REQUEST PDU or an MBMS-SESSION-START-REQUEST PDU, the BSS shall send an MBMS-SESSION-UPDATE-RESPONSE PDU or an MBMS-SESSION-START-RESPONSE PDU, respectively, to such an SGSN with a Cause Value indicating that data transfer shall be initiated on the Point-to-Multipoint BVC from that SGSN. Otherwise, the BSS shall end the MBMS Service Context. + +In any case, the BSS shall send an MBMS-SESSION-UPDATE-RESPONSE PDU with a Cause Value indicating that the MBMS Service Context has been released due to interrupted data flow to the SGSN that previously has been ordered to perform data transfer. + +![Sequence diagram of MBMS Session Update procedure between SGSN and BSS.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant BSS + Note left of SGSN: Error: - ^ + SGSN->>BSS: MBMS-SESSION-UPDATE-REQUEST + BSS-->>SGSN: MBMS-SESSION-UPDATE-RESPONSE + Note right of BSS: Error: Reference source not found + BSS-->>SGSN: MBMS-SESSION-UPDATE-RESPONSE + +``` + +The diagram illustrates the MBMS Session Update procedure. It starts with the SGSN sending an MBMS-SESSION-UPDATE-REQUEST to the BSS. The BSS responds with an MBMS-SESSION-UPDATE-RESPONSE. A second MBMS-SESSION-UPDATE-RESPONSE is shown as a dashed line, indicating a potential error or retransmission. The SGSN has an error note 'Error: - ^' and the BSS has an error note 'Error: Reference source not found'. + +Sequence diagram of MBMS Session Update procedure between SGSN and BSS. + +**Figure 8d.4: MBMS Session Update procedure** + +### 8d.4.1 Abnormal Conditions + +In any failure case in BSS the BSS may send an MBMS-SESSION-UPDATE-RESPONSE PDU including a Cause Value indicating the reason for the failure. + +If an MBMS-SESSION-UPDATE-RESPONSE PDU is not received in response to an MBMS-SESSION-UPDATE-REQUEST PDU within T11 seconds, then the MBMS-SESSION-UPDATE-REQUEST PDU shall be repeated a maximum of MBMS-SESSION-UPDATE-REQUEST-RETRIES attempts. After MBMS-SESSION-UPDATE-REQUEST-RETRIES + 1 attempts the procedure is stopped and the O&M is informed. + +## 9 General Protocol Error Handling + +Refer to General Protocol Error Handling/3GPP TS 48.016. In addition: + +- any type of BSSGP PDU received without an expected conditional IE is discarded and a STATUS PDU (cause "Missing conditional IE") is sent; +- any type of BSSGP PDU received without a mandatory IE is discarded and a STATUS PDU (cause "Missing mandatory IE") is sent; +- any type of BSSGP PDU received with a syntactical error in an expected conditional IE is discarded and a STATUS PDU (cause "Conditional IE error") is sent; +- any type of BSSGP PDU received with a syntactical error in a mandatory IE is discarded and a STATUS PDU (cause "Invalid mandatory information") is sent; +- any type of BSSGP PDU received for a feature that is not negotiated is discarded and a STATUS PDU (cause "PDU not compatible with the feature set") is sent. + +Some BSSGP PDU shall contain one and only one conditional IE amongst a defined list of possible conditional IE (e.g. PAGING-PS PDU). If such a BSSGP PDU is received with more than one conditional IE amongst the defined list of possible conditional IE, as defined in sub-clause 10, the PDU is discarded and a STATUS PDU (cause "Unexpected conditional IE") is sent. + +## 10 PDU functional definitions and contents + +### 10.1 General Structure Of A PDU + +Refer to General Structure Of A PDU/3GPP TS 48.016 [16]. + +### 10.2 PDU functional definitions and contents at RL and BSSGP SAPs + +#### 10.2.1 DL-UNITDATA + +This PDU is sent to the BSS to transfer an LLC-PDU across the radio interface to an MS. + +PDU type: DL-UNITDATA + +Direction: SGSN to BSS + +**Table 10.2.1: DL-UNITDATA PDU contents** + +| Information element | Type / Reference | Presence | Format | Length | +|-----------------------------------------------------------|-----------------------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI (current) | TLLI/11.3.35 | M | V | 4 | +| QoS Profile (note 1) | QoS Profile/11.3.28 | M | V | 3 | +| PDU Lifetime | PDU Lifetime/11.3.25 | M | TLV | 4 | +| MS Radio Access Capability (note 2) | MS Radio Access Capability/11.3.22 | O | TLV | 7-? | +| Priority (note 3) | Priority/11.3.27 | O | TLV | 3 | +| DRX Parameters (note 11) | DRX Parameters/11.3.11 | O | TLV | 4 | +| IMSI (note 14) | IMSI/11.3.14 | O | TLV | 5-10 | +| TLLI (old) | TLLI/11.3.35 | O | TLV | 6 | +| PFI | PFI/11.3.42 | O | TLV | 3 | +| LSA Information | LSA Information/11.3.19 | O | TLV | 7-? | +| Service UTRAN CCO | Service UTRAN CCO/11.3.47 | O | TLV | 3 | +| Subscriber Profile ID for RAT/Frequency priority (note 5) | Subscriber Profile ID for RAT/Frequency priority/11.3.105 | O | TLV | 3 | +| Redirection Indication (note 6) | Redirection Indication/11.3.112 | O | TLV | 3 | +| Redirection Completed (note 7) | Redirection Completed/11.3.113 | O | TLV | 3 | +| Unconfirmed send state variable (note 9) | Unconfirmed send state variable/11.3.114 | C | TLV | 4 | +| SCI (note 10) | SCI/ 11.3.116 | O | TLV | 3 | +| GGSN/P-GW location (note 10) | GGSN/P-GW location/11.3.117 | O | TLV | 3 | +| eDRX Parameters (note 11) | eDRX Parameters/11.3.122 | O | TLV | 3 | +| Coverage Class | Coverage Class/11.3.124 | O | TLV | 3 | +| Old Routing Area Identification (note 12) | Old Routing Area Identification/11.3.127 | O | TLV | 8 | +| Attach Indicator (note 13) | Attach Indicator/11.3.128 | O | TLV | 3 | +| SGSN Group Identity (note 15) | SGSN Group Identity/11.3.131 | C | TLV | 5 | +| Additional P-TMSI (note 15) | Additional P-TMSI/11.3.132 | C | TLV | 6 | +| UE Usage Type (note 15) | UE Usage Type/11.3.133 | C | TLV | 3 | +| Alignment octets | Alignment octets/11.3.1 | O | TLV | 2-5 | +| LLC-PDU (note 4) | LLC-PDU/11.3.15 | M | TLV | 2-? | +| Initial LLC-PDU (note 8) | LLC-PDU/11.3.15 | O | TLV | 2-? | +| Timing Advance Request | Timing Advance Request/11.3.140 | O | TLV | 3 | +| Enhanced Coverage Additional Information | Enhanced Coverage Additional Information/11.3.141 | O | TLV | 3 | + +NOTE 1: Some attributes of the QoS Profile shall be discarded if the PFI field is present and corresponds to a known PFC in the BSS. + +NOTE 2: The field shall be present if there is valid MS Radio Access Capability information known by the SGSN; the field shall not be present otherwise. + +NOTE 3: The priority field shall be discarded if the PFI field is present and corresponds to a known PFC in the BSS for which the ARP field was received. + +NOTE 4: The LLC-PDU Length Indicator may be zero. + +NOTE 5: This IE may be included if available in the SGSN. If the Service UTRAN CCO IE is present with the value of "shall not" the Service UTRAN CCO IE takes precedence over this IE. + +NOTE 6: This IE shall be included if Redirect Attempt flag was present in UL-UNITDATA and the CN requests rerouting by the BSC to another CN operator. + +NOTE 7: This IE shall be included if Redirect Attempt flag was present in UL-UNITDATA and the redirection is completed. + +NOTE 8: The initial Layer 3 Information received from MS. Only present when Redirection Indication is present. + +NOTE 9: Contains the value of the V(U) as defined in 3GPP TS 44.064 [12] if Redirection Indication IE is present. + +NOTE 10: These IEs are included when the SGSN supports the SIRUG feature and the received GTP-U packet contained the SCI IE. + +NOTE 11: If the SGSN has valid eDRX Parameters for a TLLI it shall include the eDRX Parameters IE (see sub-clause 6.1) in which case the DRX Parameters IE shall not be included. + +NOTE 12: This IE is only included when Redirection Indication is present and the SGSN supports CS/PS coordination enhancements. + +NOTE 13: This IE indicates a GPRS attach request from the MS. It may only be included if Redirection Indication is present and the SGSN supports CS/PS coordination enhancements. + +NOTE 14: This IE is included if the IMSI was retrieved unencrypted from the MS and the SGSN supports Dedicated Core Networks. + +NOTE 15: This IE is included if the SGSN supports Dedicated Core Networks and is included when the "Redirection Indication" IE is present. + +## 10.2.2 UL-UNITDATA + +This PDU transfers an MS's LLC-PDU and its associated radio interface information across the Gb-interface. + +PDU type: UL-UNITDATA + +Direction: BSS to SGSN + +**Table 10.2.2: UL-UNITDATA PDU content** + +| Information element | Type / Reference | Presence | Format | Length | +|---------------------|------------------|----------|--------|--------| +|---------------------|------------------|----------|--------|--------| + +| | | | | | +|----------------------------------------------|---------------------------------------------|---|-----|------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | V | 4 | +| QoS Profile | QoS Profile/11.3.28 | M | V | 3 | +| Cell Identifier
(note 5) | Cell Identifier/11.3.9 | M | TLV | 10 | +| PFI | PFI/11.3.42 | O | TLV | 3 | +| LSA Identifier List | LSA Identifier List/11.3.18 | O | TLV | 3-? | +| Redirect Attempt Flag
(Note 3) | Redirect Attempt
Flag/11.3.111 | O | TLV | 3 | +| IMSI (note 2) | IMSI/11.3.14 | O | TLV | 5-10 | +| Unconfirmed send
state variable (note 4) | Unconfirmed send state
variable/11.3.114 | O | TLV | 4 | +| Selected PLMN ID
(note 5) | Selected PLMN
ID/11.3.118 | O | TLV | 5 | +| Coverage Class
(note 7) | Coverage Class/11.3.124 | O | TLV | 3 | +| Exception Report Flag
(note 6) | Exception Report
Flag/11.3.126 | O | TLV | 3 | +| Selected Operator
(note 8, 9) | PLMN Identity/11.3.129 | O | TLV | 5 | +| CS Registered
Operator (note 8, 10) | PLMN Identity/11.3.129 | O | TLV | 5 | +| SGSN Group Identity
(note 11) | SGSN Group Identity
/11.3.131 | O | TLV | 5 | +| UE Usage Type
(note 11) | UE Usage Type/11.3.133 | O | TLV | 3 | +| DCN-ID (note 12) | DCN-ID/11.3.134 | O | TLV | 4 | +| Alignment octets | Alignment octets/11.3.1 | O | TLV | 2-5 | +| LLC-PDU (note 1) | LLC-PDU/11.3.15 | M | TLV | 2-? | +| MultilaterationTiming
Advance (note 13) | MultilaterationTiming
Advance/11.3.137 | O | TLV | 4 | +| MS Sync Accuracy
(note 13) | MS Sync
Accuracy/11.3.138 | O | TLV | 3 | +| BTS Reception
Accuracy Level (note
13) | BTS Reception Accuracy
Level/11.3.139 | O | TLV | 3 | + +- NOTE 1: The LLC-PDU Length Indicator may be zero. +- NOTE 2: IMSI shall be included if available and if Redirect Attempt Flag is present. +- NOTE 3: This element indicates that the core network shall respond with either Redirection Indication IE or Redirection Completed IE in DL\_UNITDATA +- NOTE 4: Unconfirmed send state variable shall be included if received in the previous DL\_UNITDATA. +- NOTE 5: Selected PLMN ID shall be included in the case of a mobile station supporting network sharing when a foreign TLLI or a random TLLI is included in the UL-UNITDATA PDU; in such a case the Common PLMN ID shall be included within the Cell Identifier IE. +- NOTE 6: The exception report flag shall be included +- if the UL-UNITDATA PDU contains an LLC PDU sent by the MS using an uplink EC TBF established in response to an EC PACKET CHANNEL REQUEST message indicating high priority (i.e. an exception report). + - if the UL-UNITDATA PDU contains an LLC PDU sent by the MS using an uplink EC TBF established in response to an EC PACKET DOWNLINK ACK/NACK message including channel request and indicating high priority (i.e. an exception report). +- NOTE 7: The values indicated by this IE are the uplink and downlink coverage classes used by the mobile station in the access request initiating the transmission of the LLC-PDU included in the UL-UNITDATA PDU. +- NOTE 8: Only one of these two optional IEs shall be present in the message. +- NOTE 9: This IE indicates the BSS selected CN operator. It is only included if the BSS supports CS/PS coordination enhancements. +- NOTE 10: This IE is included if the BSS supports CS/PS coordination enhancements and if the mobile station is served by one of the shared CN operators in the CS domain. +- Note 11: This IE is included if the BSS supports Dedicated Core Networks or if it supports MS assisted Dedicated Core Network selection and is included if the "Redirect Attempt Flag" IE is present. +- Note 12: This IE is included if provided by the MS, see 3GPP TS 44.060 [22] and if the LLC PDU contains an initial LLC PDU. It shall not be included if the SGSN Group Identity is included. +- Note 13: This IE is included if the BSS receives a page response sent using a RLC data block that includes the "MS Transmission Offset" and "MS Sync Accuracy" parameters (see 3GPP TS 44.018 [25] and 3GPP TS 44.060 [22]). + +## 10.2.3 RA-CAPABILITY + +This PDU informs the BSS of the new Radio Access Capability of an MS. + +PDU type: RA-CAPABILITY + +Direction: SGSN to BSS + +**Table 10.2.3: RA-CAPABILITY PDU content** + +| Information element | Type / Reference | Presence | Format | Length | +|----------------------------|------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| MS Radio Access Capability | MS Radio Access Capability/11.3.22 | M | TLV | 7-? | + +## 10.2.4 (void) + +## 10.2.5 DL-MBMS-UNITDATA + +This PDU is sent to the BSS to transfer an LLC-PDU across the radio interface. + +PDU type: DL-MBMS-UNITDATA + +Direction: SGSN to BSS + +**Table 10.2.5: DL-MBMS-UNITDATA PDU contents** + +| Information element | Type / Reference | Presence | Format | Length | +|-----------------------|--------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| PDU Lifetime | PDU Lifetime/11.3.25 | M | TLV | 4 | +| TMGI | TMGI/ 11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/ 11.3.71 | O | TLV | 3 | +| Alignment octets | Alignment octets/11.3.1 | O | TLV | 2-5 | +| LLC-PDU | LLC-PDU/11.3.15 | M | TLV | 3-? | + +## 10.2.6 UL-MBMS-UNITDATA + +This PDU transfers an LLC-PDU for an MBMS session across the Gb-interface. + +PDU type: UL-MBMS-UNITDATA + +Direction: BSS to SGSN + +**Table 10.2.6: UL-MBMS-UNITDATA PDU contents** + +| Information element | Type / Reference | Presence | Format | Length | +|-----------------------------------------------------------------------------------------|--------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TMGI | TMGI/ 11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/ 11.3.71 | O | TLV | 3 | +| Alignment octets | Alignment octets/11.3.1 | O | TLV | 2-5 | +| LLC-PDU (note 1) | LLC-PDU/11.3.15 | M | TLV | 2-? | +| NOTE: The LLC-PDU Length Indicator shall be zero in this version of the specifications. | | | | | + +## 10.3 PDU functional definitions and contents at GMM SAP + +### 10.3.1 PAGING PS + +This PDU indicates that a BSS shall initiate the packet paging procedure for an MS within a group of cells. + +PDU type: PAGING-PS + +Direction: SGSN to BSS + +**Table 10.3.1: PAGING PS PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|------------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| IMSI | IMSI/11.3.14 | M | TLV | 5 -10 | +| DRX Parameters (note 3) | DRX Parameters/11.3.11 | O | TLV | 4 | +| BVCI (note 1) | BVCI/11.3.6 | C | TLV | 4 | +| Location Area (note 1) | Location Area/11.3.17 | C (note 2) | TLV | 7 | +| Routeing Area (note 1) | Routeing Area/11.3.31 | C (note 2) | TLV | 8 | +| BSS Area Indication (note 1) | BSS Area Indication/11.3.3 | C | TLV | 3 | +| PFI | PFI/11.3.42 | O | TLV | 3 | +| ABQP | ABQP/11.3.43 | O | TLV | 13-? | +| QoS Profile | QoS Profile/11.3.28 | M | TLV | 5 | +| P-TMSI | TMSI/11.3.36 | O | TLV | 6 | +| eDRX Parameters (note 3) | eDRX Parameters/11.3.122 | O | TLV | 3 | +| Coverage Class | Coverage Class/11.3.124 | O | TLV | 3 | +| Enhanced Coverage Additional Information | Enhanced Coverage Additional Information /11.3.141 | O | TLV | 3 | +| Cell Identifier (note 4) | Cell Identifier/11.3.9 | O | TLV | 10 | +| MS Radio Access Capability (note 5) | MS Radio Access Capability/11.3.22 | O | TLV | 7-? | +| Paging Attempt Information (note 6) | Paging Attempt Information/11.3.125 | O | TLV | 3 | +| NOTE 1: One and only one of the conditional IEs shall be present. No repeated instances of the conditional IEs are permissible (e.g. one and only one Location Area shall be present). | | | | | +| NOTE 2: When network sharing is supported, the PLMN included in the Location Area/ Routeing Area elements can be either the Common PLMN or an Additional PLMN (see 3GPP TS 44.018 [25]). | | | | | +| NOTE 3: If the SGSN has valid eDRX Parameters for a TLLI it shall include the eDRX Parameters IE in which case the DRX Parameters IE shall not be included. For the case where PSM is enabled with eDRX and the Active timer is running the SGSN shall always include the negotiated eDRX value in the eDRX Parameters IE. | | | | | +| NOTE 4: The cell identity for the cell where the Coverage Class was reported by the MS shall be included if available at the SGSN. | | | | | +| NOTE 5: The field shall be present if there is valid MS Radio Access Capability information for the MS known by the SGSN; the field shall not be present otherwise. | | | | | +| NOTE 6: The field shall be present if the SGSN is paging a MS due to a positioning event. | | | | | + +## 10.3.2 PAGING CS + +This PDU indicates that a BSS shall initiate a circuit-switched paging procedure for an MS within a group of cells. + +PDU type: PAGING-CS + +Direction: SGSN to BSS + +**Table 10.3.2: PAGING CS PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|------------------------------|----------------------------|------------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| IMSI | IMSI/11.3.14 | M | TLV | 5 -10 | +| DRX Parameters | DRX Parameters/11.3.11 | M | TLV | 4 | +| BVCI (note 1) | BVCI/11.3.6 | C | TLV | 4 | +| Location Area (note 1) | Location Area/11.3.17 | C (note 3) | TLV | 7 | +| Routeing Area (note 1) | Routeing Area/11.3.31 | C (note 3) | TLV | 8 | +| BSS Area Indication (note 1) | BSS Area Indication/11.3.3 | C | TLV | 3 | +| TLLI | TLLI/11.3.35 | O | TLV | 6 | +| Channel needed (note 2) | Channel needed/11.3.10 | O | TLV | 3 | +| eMLPP-Priority (note 2) | eMLPP-Priority/11.3.12 | O | TLV | 3 | +| TMSI (note 2) | TMSI/11.3.36 | O | TLV | 6 | +| Global CN-Id (note 2) | Global CN-Id/11.3.69 | O | TLV | 7 | + +NOTE 1: One and only one of the conditional IEs shall be present. No repeated instances of the conditional IEs are permissible (e.g. one and only one Location Area shall be present). + +NOTE 2: These fields are provided by the MSC via the Gs-Interface. + +NOTE 3: When network sharing is supported, the PLMN included in the Location Area/Routeing Area elements can be either the Common PLMN or an Additional PLMN (see 3GPP TS 44.018 [25]). + +## 10.3.3 RA-CAPABILITY-UPDATE + +This PDU requests that the SGSN send an MS's current Radio Access capability or IMSI to the BSS. + +PDU type: RA-CAPABILITY-UPDATE + +Direction: BSS to SGSN + +**Table 10.3.3: RA-CAPABILITY-UPDATE PDU content** + +| Information element | Type / Reference | Presence | Format | Length | +|---------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Tag | Tag/11.3.34 | M | TLV | 3 | + +### 10.3.4 RA-CAPABILITY-UPDATE-ACK + +This PDU provides the BSS with an MS's current Radio Access capability and IMSI. + +PDU type: RA-CAPABILITY-UPDATE-ACK + +Direction: SGSN to BSS + +**Table 10.3.4: RA-CAPABILITY-UPDATE-ACK PDU content** + +| Information element | Type / Reference | Presence | Format | Length | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Tag | Tag/11.3.34 | M | TLV | 3 | +| IMSI (note) | IMSI/11.3.14 | C | TLV | 5-10 | +| RA-Cap-UPD-CAUSE | RA-Cap-UPD-CAUSE/
11.3.30 | M | TLV | 3 | +| MS Radio Access Capability | MS Radio Access
Capability/11.3.22 | C | TLV | 7-? | +| NOTE: If RA-Cap-UPD-CAUSE is not set to "OK", then neither the MS Radio Access Capability nor the IMSI shall be present. Otherwise, the IMSI shall be present. | | | | | + +### 10.3.5 RADIO-STATUS + +This PDU indicates that an exception condition related to the radio interface has occurred. + +PDU type: RADIO-STATUS + +Direction: BSS to SGSN + +**Table 10.3.5: RADIO-STATUS PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------------------------------------------------|---------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI (note) | TLLI/11.3.35 | C | TLV | 6 | +| TMSI (note) | TMSI/11.3.36 | C | TLV | 6 | +| IMSI (note) | IMSI/11.3.14 | C | TLV | 5-10 | +| Radio Cause | Radio Cause/11.3.29 | M | TLV | 3 | +| NOTE: One and only one of the conditional IEs shall be present. | | | | | + +### 10.3.6 SUSPEND + +This PDU indicates that an MS wishes to suspend its GPRS service. + +PDU type: SUSPEND + +Direction: BSS to SGSN + +**Table 10.3.6: SUSPEND PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|-----------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Routeing Area | Routeing Area/11.3.31 | M | TLV | 8 | + +### 10.3.7 SUSPEND-ACK + +This PDU positively acknowledges the reception of a SUSPEND PDU for an MS. + +PDU type: SUSPEND-ACK + +Direction: SGSN to BSS + +**Table 10.3.7: SUSPEND-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|--------------------------|----------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Routeing Area | Routeing Area/11.3.31 | M | TLV | 8 | +| Suspend Reference Number | Suspend Reference Number/11.3.33 | M | TLV | 3 | + +### 10.3.8 SUSPEND-NACK + +This PDU negatively acknowledges the reception of a SUSPEND PDU for an MS. + +PDU type: SUSPEND-NACK + +Direction: SGSN to BSS + +**Table 10.3.8: SUSPEND-NACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|-----------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Routeing Area | Routeing Area/11.3.31 | M | TLV | 8 | +| Cause | Cause/11.3.8 | O | TLV | 3 | + +### 10.3.9 RESUME + +This PDU indicates that an MS wishes to RESUME its GPRS service. + +PDU type: RESUME + +Direction: BSS to SGSN + +**Table 10.3.9: RESUME PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|--------------------------|----------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Routeing Area | Routeing Area/11.3.31 | M | TLV | 8 | +| Suspend Reference Number | Suspend Reference Number/11.3.33 | M | TLV | 3 | + +### 10.3.10 RESUME-ACK + +This PDU positively acknowledges the reception of a RESUME PDU for an MS. + +PDU type: RESUME-ACK + +Direction: SGSN to BSS + +**Table 10.3.10: RESUME-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|-----------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Routeing Area | Routeing Area/11.3.31 | M | TLV | 8 | + +### 10.3.11 RESUME-NACK + +This PDU negatively acknowledges the reception of a RESUME PDU for an MS. + +PDU type: RESUME-NACK + +Direction: SGSN to BSS + +**Table 10.3.11: RESUME-NACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|-----------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Routeing Area | Routeing Area/11.3.31 | M | TLV | 8 | +| Cause | Cause/11.3.8 | O | TLV | 3 | + +## 10.3.12 DUMMY PAGING PS + +This PDU indicates that a BSS shall calculate the time until the next paging occasion for the MS indicated in the message. + +PDU type: DUMMY-PAGING-PS + +Direction: SGSN to BSS + +**Table 10.3.12: DUMMY PAGING PS PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|--------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| IMSI | IMSI/11.3.14 | M | TLV | 5 -10 | +| Routeing Area | Routeing Area/11.3.31 | O | TLV | 8 | +| eDRX Parameters | eDRX Parameters/11.3.122 | O | TLV | 3 | + +## 10.3.13 DUMMY PAGING PS RESPONSE + +This PDU provides the SGSN with the time until the next paging occasion for the MS indicated in the message. + +PDU type: DUMMY-PAGING-PS-RESPONSE + +Direction: BSS to SGSN + +**Table 10.3.13: DUMMY PAGING PS RESPONSE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| IMSI | IMSI/11.3.14 | M | TLV | 5 -10 | +| Time Until Next Paging Occasion | Time Until Next Paging Occasion/11.3.123 | M | TLV | 4 | + +## 10.3.14 PAGING PS REJECT + +This PDU indicates that a BSS has determined the nominal paging group of the MS occurs too far into the future. + +PDU type: PAGING-PS-PDU + +Direction: BSS to SGSN + +**Table 10.3.14: PAGING PS REJECT PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| IMSI | IMSI/11.3.14 | M | TLV | 5 -10 | +| P-TMSI (note 1) | TMSI/11.3.36 | O | TLV | 6 | +| Time Until Next Paging Occasion | Time Until Next Paging Occasion/11.3.123 | M | TLV | 4 | + +NOTE 1: Included if present in the corresponding PAGING-PS PDU. + +### 10.3.15 MS REGISTRATION ENQUIRY + +This PDU allows the BSS to request registration information for a given mobile station. It is used in MOCN and GWCN configurations for network sharing. + +PDU type: MS-REGISTRATION-ENQUIRY + +Direction: BSS to SGSN + +**Table 10.3.15: MS REGISTRATION ENQUIRY PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|--------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| IMSI | IMSI/11.3.14 | M | TLV | 5-10 | +| MME Query | MME Query/11.3.130 | O | TLV | 3 | + +### 10.3.16 MS REGISTRATION ENQUIRY RESPONSE + +This PDU is sent to the BSS to provide registration information for a given mobile station. It is used in MOCN and GWCN configurations for network sharing. + +PDU type: MS-REGISTRATION-ENQUIRY-RESPONSE + +Direction: SGSN to BSS + +**Table 10.3.16: MS REGISTRATION ENQUIRY RESPONSE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| IMSI | IMSI/11.3.14 | M | TLV | 5-10 | +| PS Registered Operator (note 1) | PLMN Identity/11.3.129 | O | TLV | 5 | + +NOTE 1: This IE identifies the serving CN operator for the mobile station associated to the IMSI. Omitting this IE from the message has the significance of no serving CN operator for the mobile station (IMSI). + +## 10.4 PDU functional definitions and contents at NM SAP + +### 10.4.1 FLUSH-LL + +This PDU informs a BSS that an MS has moved from one cell to another. + +PDU type: FLUSH-LL + +Direction: SGSN to BSS + +**Table 10.4.1: FLUSH-LL PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| BVCI (old) | BVCI/11.3.6 | M | TLV | 4 | +| BVCI (new) | BVCI/11.3.6 | O | TLV | 4 | +| NSEI (new) | NSEI/11.3.48 | O (note) | TLV | 4 | + +NOTE: NSEI (new) is included if the SGSN supports "Inter-NSE re-routing" or "LCS Procedures" and the old NSE supports the "Inter-NSE re-routing" or "LCS Procedures" and the cell change is an Inter-NSE cell change within a routing area. + +## 10.4.2 FLUSH-LL-ACK + +This PDU indicates that LLC-PDU(s) buffered for an MS in the old cell have been either deleted or transferred to the new cell within the routing area. + +PDU type: FLUSH-LL-ACK + +Direction: BSS to SGSN + +**Table 10.4.2: FLUSH-LL-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Flush Action | Flush Action/11.3.13 | M | TLV | 3 | +| BVCI (new) | BVCI/11.3.13 | C (note 1) | TLV | 4 | +| Number of octets affected | Number of octets affected/11.3.41 | M | TLV | 5 | +| NSEI (new) | NSEI/11.3.48 | C (note 2) | TLV | 4 | +| NOTE 1: BVCI (new) is included only if Flush action indicated that LLC-PDUs are transferred.
NOTE 2: NSEI (new) is included only if BVCI(new) is included and NSEI (new) is received in the FLUSH-LL PDU. | | | | | + +## 10.4.3 LLC-DISCARDED + +This PDU indicates that a number of buffered LLC-PDUs in a cell for an MS have been deleted inside the BSS (because of PDU Lifetime expiration or radio outage for example). The LLC frames and the related octets deleted by the BSS as a consequence of a FLUSH-LL procedure (see sub-clause 8.1) shall not be reported a second time by means of an LLC-DISCARDED PDU. + +PDU type: LLC-DISCARDED + +Direction: BSS to SGSN + +**Table 10.4.3: LLC-DISCARDED PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| LLC Frames Discarded | LLC Frames Discarded/11.3.16 | M | TLV | 3 | +| BVCI | BVCI/11.3.6 | M | TLV | 4 | +| Number of octets deleted | Number of octets affected/11.3.41 | M | TLV | 5 | +| PFI (note) | PFI/11.3.42 | O | TLV | 3 | +| NOTE: The PFI may be provided in case the PFC flow control feature is negotiated. It corresponds to the Packet Flow Identifier of the PFC for which LLC frames have been discarded. | | | | | + +## 10.4.4 FLOW-CONTROL-BVC + +This PDU informs the flow control mechanism at an SGSN of the status of a BVC's maximum acceptable SGSN to BSS throughput on the Gb interface. + +PDU type: FLOW-CONTROL-BVC + +Direction: BSS to SGSN + +**Table 10.4.4: FLOW-CONTROL-BVC PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|-----------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Tag | Tag/11.3.34 | M | TLV | 3 | +| BVC Bucket Size | BVC Bucket Size/11.3.5 | M | TLV | 4 | +| Bucket Leak Rate | Bucket Leak Rate/11.3.4 | M | TLV | 4 | +| Bmax default MS | Bmax default MS/11.3.2 | M | TLV | 4 | +| R_default_MS | R_default_MS/11.3.32 | M | TLV | 4 | +| Bucket_Full Ratio | Bucket_Full Ratio/11.3.46 | C | TLV | 3 | +| BVC Measurement | BVC Measurement/11.3.7 | O | TLV | 4 | +| Flow Control Granularity (note) | Flow Control Granularity/11.3.102 | O | TLV | 3 | + +NOTE: The Flow Control Granularity shall be provided in case the Gigabit Interface feature is negotiated. + +## 10.4.5 FLOW-CONTROL-BVC-ACK + +This PDU informs the flow control mechanism at the BSS that the SGSN has received the FLOW-CONTROL-BVC PDU indicated by the Tag. + +PDU type: FLOW-CONTROL-BVC-ACK + +Direction: SGSN to BSS + +**Table 10.4.5: FLOW-CONTROL-BVC-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Tag | Tag/11.3.34 | M | TLV | 3 | + +## 10.4.6 FLOW-CONTROL-MS + +This PDU informs the flow control mechanism at an SGSN of the status of an MS's maximum acceptable SGSN to BSS throughput on the Gb interface. + +PDU type: FLOW-CONTROL-MS + +Direction: BSS to SGSN + +**Table 10.4.6: FLOW-CONTROL-MS PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|-----------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Tag | Tag/11.3.34 | M | TLV | 3 | +| MS Bucket Size | MS Bucket Size/11.3.21 | M | TLV | 4 | +| Bucket Leak rate | Bucket Leak rate/11.3.4 | M | TLV | 4 | +| Bucket_Full Ratio | Bucket_Full Ratio/11.3.46 | C | TLV | 3 | +| Flow Control Granularity (note) | Flow Control Granularity/11.3.102 | O | TLV | 3 | + +NOTE: The Flow Control Granularity shall be provided in case the Gigabit Interface feature is negotiated. + +## 10.4.7 FLOW-CONTROL-MS-ACK + +This PDU informs the flow control mechanism at the BSS that the SGSN has received the FLOW-CONTROL-MS PDU indicated by the TLLI and the Tag. + +PDU type: FLOW-CONTROL-MS-ACK + +Direction: SGSN to BSS + +**Table 10.4.7: FLOW-CONTROL-MS-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Tag | Tag/11.3.34 | M | TLV | 3 | + +## 10.4.8 BVC-BLOCK + +This PDU indicates that the contained BVC shall be blocked at the recipient entity. + +PDU type: BVC-BLOCK + +Direction: BSS to SGSN + +**Table 10.4.8: BVC-BLOCK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| BVCI | BVCI/11.3.6 | M | TLV | 4 | +| Cause | Cause/11.3.8 | M | TLV | 3 | + +## 10.4.9 BVC-BLOCK-ACK + +This PDU acknowledges that a BVC has been blocked. + +PDU type: BVC-BLOCK-ACK + +Direction: SGSN to BSS + +**Table 10.4.9: BVC-BLOCK-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| BVCI | BVCI/11.3.6 | M | TLV | 4 | + +## 10.4.10 BVC-UNBLOCK + +This PDU indicates that the identified BVC shall be unblocked at the recipient entity. + +PDU type: BVC-UNBLOCK + +Direction: BSS to SGSN + +**Table 10.4.10: BVC-UNBLOCK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| BVCI | BVCI/11.3.6 | M | TLV | 4 | + +## 10.4.11 BVC-UNBLOCK-ACK + +This PDU acknowledges that a BVC has been unblocked. + +PDU type: BVC-UNBLOCK-ACK + +Direction: SGSN to BSS + +**Table 10.4.11: BVC-UNBLOCK-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| BVCI | BVCI/11.3.6 | M | TLV | 4 | + +## 10.4.12 BVC-RESET + +This PDU indicates that BVC initialisation is required, e.g. because of a BVC failure. + +PDU type: BVC-RESET + +Direction: SGSN to BSS, BSS to SGSN + +**Table 10.4.12: BVC-RESET PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------------------|---------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| BVCI | BVCI/11.3.6 | M | TLV | 4 | +| Cause | Cause/11.3.8 | M | TLV | 3 | +| Cell Identifier (note 1) | | C | TLV | 10 | +| Feature bitmap (note 2) | Feature bitmap/11.3.45 | O | TLV | 3 | +| Extended Feature Bitmap (note 3) | Extended Feature Bitmap/11.3.84 | O | TLV | 3 | + +NOTE 1: The Cell Identifier IE is mandatory in the BVC-RESET PDU sent from BSS to SGSN in order to reset a BVC corresponding to a PTP functional entity. The Cell Identifier IE shall not be used in any other BVC-RESET PDU. + +NOTE 2: The Feature bitmap is only sent in a BVC-RESET PDU related to the signalling BVC. Absence of this IE implies no optional features are available over the NSE. + +NOTE 3: The Extended Feature Bitmap is only sent in a BVC-RESET PDU related to the signalling BVC. + +## 10.4.13 BVC-RESET-ACK + +This PDU indicates that BVC initialisation has been executed. + +PDU type: BVC-RESET-ACK + +Direction: BSS to SGSN, SGSN to BSS + +**Table 10.4.13: BVC-RESET-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------------------|---------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| BVCI | BVCI/11.3.6 | M | TLV | 4 | +| Cell Identifier (note 1) | | C | TLV | 10 | +| Feature bitmap (note 2) | Feature bitmap/11.3.45 | O | TLV | 3 | +| Extended Feature Bitmap (note 3) | Extended Feature Bitmap/11.3.84 | O | TLV | 3 | + +NOTE 1: The Cell Identifier IE is mandatory in the BVC-RESET-ACK PDU sent from BSS to SGSN in response to reset a BVC corresponding to a PTP functional entity. The Cell Identifier IE shall not be used in any other BVC-RESET-ACK PDU. + +NOTE 2: The Feature bitmap is only sent in a BVC-RESET-ACK PDU related to the signalling BVC. Absence of this IE implies no optional features are available over the NSE. + +NOTE 3: The Extended Feature Bitmap is only sent in a BVC-RESET-ACK PDU related to the signalling BVC. + +## 10.4.14 STATUS + +This PDU indicates that an exception condition occurred. + +PDU type: STATUS + Direction: SGSN to BSS, BSS to SGSN + +**Table 10.4.14: STATUS PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Cause | Cause/11.3.8 | M | TLV | 3 | +| BVCI | BVCI/11.3.6 | C | TLV | 4 | +| PDU In Error (note) | PDU In Error/11.3.24 | O | TLV | 3-? | +| NOTE: This is the whole PDU (starting with the [PDU type]) within which an error was detected. This PDU may be truncated if it exceeds the information carrying capacity of the underlying network service. | | | | | + +### 10.4.14.1 Static conditions for BVCI + +The "BVCI" IE shall be included when the "Cause" IE is set to one of the following values: + +- "BVCI blocked"; +- "BVCI unknown"; + +and shall not be included otherwise. + +## 10.4.15 SGSN-INVOKE-TRACE + +This PDU indicates that the BSS shall begin the production of a trace record for an MS. + +PDU type: SGSN-INVOKE-TRACE + Direction: SGSN to BSS + +**Table 10.4.15: SGSN-INVOKE-TRACE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|-------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Trace Type | Trace Type/11.3.38 | M | TLV | 3 | +| Trace Reference | Trace Reference/11.3.37 | M | TLV | 4 | +| Trigger Id | Trigger Id/11.3.40 | O | TLV | 4-24 | +| Mobile Id | Mobile Id/11.3.20 | O | TLV | 3-10 | +| OMC Id | OMC Id/11.3.23 | O | TLV | 4-24 | +| TransactionId | TransactionId/11.3.39 | O | TLV | 4 | + +## 10.4.16 DOWNLOAD-BSS-PFC + +This PDU requests a SGSN to initiate a CREATE-BSS-PFC procedure. + +PDU type: DOWNLOAD-BSS-PFC + Direction: BSS to SGSN + +**Table 10.4.16: DOWNLOAD-BSS-PFC PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | + +## 10.4.17 CREATE-BSS-PFC + +This PDU allows the SGSN to request that a BSS create or modify a BSS Packet Flow Context. + +PDU type: CREATE-BSS-PFC + +Direction: SGSN to BSS + +**Table 10.4.17: CREATE-BSS-PFC PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|------------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| IMSI | IMSI/11.3.14 | O (note 4) | TLV | 5 -10 | +| PFI | PFI/11.3.42 | M | TLV | 3 | +| PFT | GPRS Timer/11.3.44 | M | TLV | 3 | +| ABQP | ABQP/11.3.43 | M | TLV | 13-? | +| Service UTRAN CCO | Service UTRAN CCO/11.3.47 | O | TLV | 3 | +| MS Radio Access Capability | MS Radio Access Capability/11.3.22 | O (note 1) | TLV | 7-? | +| Allocation/Retention Priority | Priority/11.3.27 | O | TLV | 3 | +| T10 | GPRS Timer/11.3.44 | C (note 2) | TLV | 3 | +| Inter RAT Handover Info | Inter RAT Handover Info/11.3.94 | O (note 3) | TLV | 3-? | +| E-UTRAN Inter RAT Handover Info | E-UTRAN Inter RAT Handover Info/11.3.104 | O (note 3) | TLV | 3-? | +| Subscriber Profile ID for RAT/Frequency priority (note 5) | Subscriber Profile ID for RAT/Frequency priority/11.3.105 | O | TLV | 3 | +| NOTE 1: This Information Element shall be present if there is valid MS Radio Access Capability information known by the SGSN. | | | | | +| NOTE 2: This information element shall be present if the Allocation/Retention Priority IE is present and if queuing is allowed for the PFC. | | | | | +| NOTE 3: This information element shall be present if available in the SGSN. | | | | | +| NOTE 4: This information element shall be present if the IMSI is available in the SGSN. | | | | | +| NOTE 5: This IE may be included if available in the SGSN. If the Service UTRAN CCO IE is present with the value of "shall not" the Service UTRAN CCO IE takes precedence over this IE. | | | | | + +## 10.4.18 CREATE-BSS-PFC-ACK + +This PDU allows the BSS to acknowledge a request from the SGSN for the creation or modification of a BSS Packet Flow Context. + +PDU type: CREATE-BSS-PFC-ACK + +Direction: BSS to SGSN + +**Table 10.4.18: CREATE-BSS-PFC-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | +| ABQP | ABQP/11.3.43 | M | TLV | 13-? | +| Cause | Cause/11.3.8 | O | TLV | 3 | + +## 10.4.19 CREATE-BSS-PFC-NACK + +This PDU allows the BSS to Nack a request from the SGSN for the creation of a BSS Packet Flow Context. + +PDU type: CREATE-BSS-PFC-NACK + +Direction: BSS to SGSN + +**Table 10.4.19: CREATE-BSS-PFC-NACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | +| Cause | Cause/11.3.8 | M | TLV | 3 | + +## 10.4.20 MODIFY-BSS-PFC + +This PDU allows the BSS to request a modification of a BSS Packet Flow Context. + +PDU type: MODIFY-BSS-PFC + +Direction: BSS to SGSN + +**Table 10.4.20: MODIFY-BSS-PFC PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | +| ABQP | ABQP/11.3.43 | M | TLV | 13-? | + +## 10.4.21 MODIFY-BSS-PFC-ACK + +This PDU allows the SGSN to acknowledge a modification to a BSS Packet Flow Context. + +PDU type: MODIFY-BSS-PFC-ACK + +Direction: SGSN to BSS + +**Table 10.4.21: MODIFY-BSS-PFC-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|--------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | +| PFT | GPRS Timer/11.3.44 | M | TLV | 3 | +| ABQP | ABQP/11.3.43 | M | TLV | 13-? | + +## 10.4.22 DELETE-BSS-PFC + +This PDU allows the SGSN to request that a BSS delete a BSS Packet Flow Context. + +PDU type: DELETE-BSS-PFC + +Direction: SGSN to BSS + +**Table 10.4.22: DELETE-BSS-PFC PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | + +## 10.4.23 DELETE-BSS-PFC-ACK + +This PDU allows the BSS to acknowledge a request for the deletion of a BSS Packet Flow Context. + +PDU type: DELETE-BSS-PFC-ACK + +Direction: BSS to SGSN + +**Table 10.4.23: DELETE-BSS-PFC-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | + +## 10.4.24 FLOW-CONTROL-PFC + +This PDU provides the SGSN with flow control information regarding one or more PFC(s) of a given Mobile Station. + +PDU type: FLOW-CONTROL-PFC + +Direction: BSS to SGSN + +**Table 10.4.24: FLOW-CONTROL-PFC PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|-------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Tag | Tag/11.3.34 | M | TLV | 3 | +| MS Bucket Size | MS Bucket Size/11.3.21 | O | TLV | 4 | +| Bucket Leak rate | Bucket Leak rate/11.3.4 | O | TLV | 4 | +| Bucket Full Ratio | Bucket Full Ratio/11.3.46 | O | TLV | 3 | +| PFC flow control parameters | PFC flow control parameters/11.3.68 | M | TLV | | +| Flow Control Granularity (note) | Flow Control Granularity/11.3.102 | O | TLV | 3 | + +NOTE: The Flow Control Granularity shall be provided in case the Gigabit Interface feature is negotiated. + +## 10.4.25 FLOW-CONTROL-PFC-ACK + +This PDU informs the flow control mechanism at the BSS that the SGSN has received the FLOW-CONTROL-PFC PDU indicated by the TLLI and the Tag. + +PDU type: FLOW-CONTROL-PFC-ACK + +Direction: SGSN to BSS + +**Table 10.4.25: FLOW-CONTROL-PFC-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Tag | Tag/11.3.34 | M | TLV | 3 | + +## 10.4.26 DELETE-BSS-PFC-REQ + +This PDU allows the BSS to inform the SGSN that the BSS Packet Flow Context cannot be supported anymore + +PDU type: DELETE-BSS-PFC-REQ + +Direction: BSS to SGSN + +**Table 10.4.26: DELETE-BSS-PFC-REQ PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| PFI | PFI/11.3.42 | M | TLV | 3 | +| Cause | Cause/11.3.8 | M | TLV | 3 | + +## 10.4.27 PS-HANDOVER-REQUIRED + +This PDU initiates the allocation of resources in the target system for an MS. + +PDU type: PS-HANDOVER-REQUIRED + +Direction: BSS to SGSN + +**Table 10.4.27: PS-HANDOVER-REQUIRED PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +|----------------------|------------------|----------|--------|--------| + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|---|-----|------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Cause | Cause/11.3.8 | M | TLV | 3 | +| Source Cell Identifier | Cell Identifier/11.3.9 | M | TLV | 10 | +| Target Cell Identifier (note 2) | Cell Identifier/11.3.9 | C | TLV | 10 | +| Source BSS to Target BSS Transparent Container (note 1) | Source BSS to Target BSS Transparent Container/11.3.79 | C | TLV | 10-? | +| Target RNC Identifier (note 2) (note 3) | RNC Identifier/11.3.87 | C | TLV | 10 | +| Source to Target Transparent Container (note 1) | Source to Target Transparent Container/11.3.85 | C | TLV | 3-? | +| Active PFCs List | Active PFCs List/11.3.95c | M | TLV | 3-? | +| Target eNB identifier (note 2) (note 3) | eNB Identifier/11.3.103 | C | TLV | 3-n | +| Reliable Inter RAT Handover Info (note 4) | Reliable Inter RAT Handover Info/11.3.107 | C | TLV | 3 | +| CSG Identifier (note 5) | CSG Identifier/11.3.109 | C | TLV | 7 | +| TAC (note 6) | Tracking Area Code/11.3.110 | C | TLV | 5 | +| NOTE 1: One and only one of these two conditional IEs shall be present depending on the target RAT as specified in subclause 8a.4. | | | | | +| NOTE 2: One and only one of these three conditional IEs shall be present depending on the target RAT as specified in subclause 8a.4. | | | | | +| NOTE 3: In case of PS handover to E-UTRAN, the Target RNC Identifier IE (carrying the Corresponding RNC-ID) may be present as an alternative to the Target eNB identifier IE. | | | | | +| NOTE 4: This IE shall be present when the target cell is a GERAN cell. | | | | | +| NOTE 5: This IE shall be present when the target cell is a CSG or hybrid cell. | | | | | +| NOTE 6: This IE shall be present when the target cell is a E-UTRAN CSG or hybrid cell. | | | | | + +## 10.4.28 PS-HANDOVER-REQUIRED-ACK + +This PDU indicates that resources have been allocated in the target system and that the BSS may initiate the channel change attempt for the corresponding MS. + +PDU type: PS-HANDOVER-REQUIRED-ACK + +Direction: SGSN to BSS + +**Table 10.4.28: PS-HANDOVER-REQUIRED-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| List of set-up PFCs | List of set-up PFCs/11.3.83 | M | TLV | 3-? | +| Target BSS to Source BSS Transparent Container (note) | Target BSS to Source BSS Transparent Container/11.3.80 | C | TLV | 3-? | +| Target to Source Transparent Container (note) | Target to Source Transparent Container/11.3.86 | C | TLV | 3-? | +| NOTE: One and only one of these two conditional IEs shall be present depending on the target RAT as specified in subclause 8a.4. | | | | | + +## 10.4.29 PS-HANDOVER-REQUIRED-NACK + +This PDU informs the source BSS about failed resource allocation in the target system. + +PDU type: PS-HANDOVER-REQUIRED-NACK + +Direction: SGSN to BSS + +**Table 10.4.29: PS-HANDOVER-REQUIRED-NACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Cause | Cause/11.3.8 | M | TLV | 3 | + +## 10.4.30 PS-HANDOVER-REQUEST + +This PDU initiates the allocation of resources for one or more PFCs in the target BSS for an MS. + +PDU type: PS-HANDOVER-REQUEST + +Direction: SGSN to BSS + +**Table 10.4.30: PS-HANDOVER-REQUEST PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------------------------------------------|------------------------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| IMSI | IMSI/11.3.14 | M | TLV | 5-10 | +| Cause | Cause/11.3.8 | M | TLV | 3 | +| Source Cell Identifier (note 1) | Cell Identifier/11.3.9 | C | TLV | 10 | +| Source RNC Identifier (note 1) | RNC Identifier/11.3.87 | C | TLV | 10 | +| Target Cell Identifier | Cell Identifier/11.3.9 | M | TLV | 10 | +| Source BSS to Target BSS Transparent Container | Source BSS to Target BSS Transparent Container/11.3.79 | M | TLV | 7-? | +| PFCs to be set-up list | PFCs to be set-up list/11.3.82 | M | TLV | 22-? | +| NAS container for PS Handover | NAS container for PS Handover/11.3.81 | O | TLV | 3-? | +| Service UTRAN CCO | Service UTRAN CCO/11.3.47 | O | TLV | 3 | +| Subscriber Profile ID for RAT/Frequency priority (note 2) | Subscriber Profile ID for RAT/Frequency priority /11.3.105 | O | TLV | 3 | +| Reliable Inter RAT Handover Info (note 3) | Reliable Inter RAT Handover Info/11.3.107 | C | TLV | 3 | + +NOTE 1: In case of PS handover from GERAN or UTRAN, one and only one of these two conditional IEs shall be present depending on the source RAT. In case of PS handover from E-UTRAN, neither of these two conditional IEs shall be present. + +NOTE 2: This IE may be included if available in the SGSN. If the Service UTRAN CCO IE is present with the value of "shall not" the Service UTRAN CCO IE takes precedence over this IE. + +NOTE 3: This IE shall be included if sent by the source BSS. + +## 10.4.31 PS-HANDOVER-REQUEST-ACK + +This PDU acknowledges the successful allocation of resources in the target BSS. + +PDU type: PS-HANDOVER-REQUEST-ACK + +Direction: BSS to SGSN + +**Table 10.4.31: PS-HANDOVER-REQUEST-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|------------------------------------------------|--------------------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| List of set-up PFCs | List of set-up PFCs/11.3.83 | M | TLV | 3-? | +| Target BSS to Source BSS Transparent Container | Target BSS to Source BSS Transparent Container/11.3.80 | M | TLV | 3-? | + +## 10.4.32 PS-HANDOVER-REQUEST-NACK + +This PDU informs the SGSN about failed resource allocation in the target BSS. + +PDU type: PS-HANDOVER-REQUEST-NACK + +Direction: BSS to SGSN + +**Table 10.4.32: PS-HANDOVER-REQUEST-NACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Cause | Cause/11.3.8 | M | TLV | 3 | + +## 10.4.33 PS-HANDOVER-COMPLETE + +This PDU informs the SGSN about successful channel change for an MS. + +PDU type: PS-HANDOVER-COMPLETE + +Direction: BSS to SGSN + +**Table 10.4.33: PS-HANDOVER-COMPLETE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------------------------------------------------------------------|----------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| IMSI | IMSI/11.3.14 | M | TLV | 5-10 | +| Target Cell Identifier (note 1) | Cell Identifier/11.3.9 | O | TLV | 10 | +| Request for Inter RAT Handover Info (note 2) | Request for Inter RAT Handover Info/11.3.106 | O | TLV | 3 | +| NOTE 1: The Target Cell Identifier IE is included only for optimised Intra-BSS PS Handover. | | | | | +| NOTE 2: This IE shall be included if the BSS supports inter-RAT PS handover to UTRAN. | | | | | + +## 10.4.34 PS-HANDOVER-CANCEL + +This PDU cancels the handover for an MS. + +PDU type: PS-HANDOVER-CANCEL + +Direction: BSS to SGSN + +**Table 10.4.34: PS-HANDOVER-CANCEL PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------|----------|--------|--------| +|----------------------|------------------|----------|--------|--------| + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---|-----|-----| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Cause | Cause/11.3.8 | M | TLV | 3 | +| Source Cell Identifier | Cell Identifier/11.3.9 | M | TLV | 10 | +| Target Cell Identifier (note 1) | Cell Identifier/11.3.9 | C | TLV | 10 | +| Target RNC Identifier (note 1) (note 2) | RNC Identifier/11.3.87 | C | TLV | 10 | +| Target eNB Identifier (note 1) (note 2) | eNB Identifier/11.3.103 | C | TLV | 3-n | +| NOTE 1: One and only one of these three conditional IEs shall be present depending on the target RAT as specified in subclause 8a.7. | | | | | +| NOTE 2: In case of PS handover to E-UTRAN, the Target RNC Identifier IE (carrying the Corresponding RNC-ID) may be present as an alternative to the Target eNB identifier IE. | | | | | + +## 10.4.35 PS-HANDOVER-COMPLETE-ACK + +This PDU provides to the BSS the *Inter RAT Handover Info* IE. It is sent only if requested by the BSS. + +PDU type: PS-HANDOVER-COMPLETE-ACK + +Direction: SGSN to BSS + +**Table 10.4.35: PS-HANDOVER-COMPLETE-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| Inter RAT Handover Info | Inter RAT Handover Info/11.3.94 | M (note 1) | TLV | 3-? | +| E-UTRAN Inter RAT Handover Info | E-UTRAN Inter RAT Handover Info/11.3.104 | O (note 1) | TLV | 3-? | +| NOTE 1: Only Inter RAT Handover Info IE shall be present in the message. E-UTRAN Inter RAT Handover Info IE was defined in an earlier version of the protocol and shall not be used. | | | | | + +## 10.4.36 OVERLOAD + +This PDU informs the BSS that the SGSN sending the PDU is in an overload situation and the signalling traffic to the SGSN should be reduced. + +PDU type: OVERLOAD + +Direction: SGSN to BSS + +**Table 10.4.36: OVERLOAD PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|--------------------------|-----------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Priority Class Indicator | Priority Class Indicator/11.3.118 | M | TLV | 3 | + +# 10.5 PDU functional definitions and contents at LCS SAP + +## 10.5.1 PERFORM-LOCATION-REQUEST + +This PDU allows the SGSN to request the BSS to perform a location procedure for the target MS. + +PDU type: PERFORM-LOCATION-REQUEST + +Direction: SGSN to BSS + +**Table 10.5.1: PERFORM-LOCATION-REQUEST PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|------------------------------------------|-----------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| IMSI | IMSI/11.3.14 | M | TLV | 5-10 | +| DRX Parameters (note 1) | DRX Parameters/11.3.11 | O | TLV | 4 | +| BVCI (PCU-PTP) | BVCI/11.3.6 | M | TLV | 4 | +| NSEI (PCU-PTP) | NSEI/11.3.48 | M | TLV | 4-? | +| Location Type | Location Type/11.3.53 | M | TLV | 3-? | +| Cell Identifier | Cell Identifier/11.3.9 | M | TLV | 10 | +| LCS Capability (note 2) | LCS Capability/11.3.59 | O | TLV | 3-? | +| LCS Priority | LCS Priority/11.3.57 | O | TLV | 3-? | +| LCS QoS | LCS QoS/11.3.50 | O | TLV | 3-? | +| LCS Client Type (note 3) | LCS Client Type/11.3.51 | C | TLV | 3-? | +| Requested GPS Assistance Data (note 4) | Requested GPS Assistance Data/11.3.52 | O | TLV | 3-? | +| IMEI (note 5) | IMEI/11.3.91 | O | TLV | 10 | +| GANSS Location Type | GANSS Location Type / 11.3.100 | C | TLV | 3 | +| Requested GANSS Assistance Data (note 6) | Requested GANSS Assistance Data/11.3.99 | O | TLV | 3-? | +| eDRX Parameters (note 7) | eDRX Parameters/11.3.122 | O | TLV | 3 | +| Coverage Class | Coverage Class/11.3.124 | O | TLV | 3 | +| MS Radio Access Capability (note 8) | MS Radio Access Capability/11.3.22 | O | TLV | 7-? | +| MultilaterationTiming Advance (note 9) | MultilaterationTiming Advance/11.3.137 | O | TLV | 4 | +| MS Sync Accuracy (note 9) | MS Sync Accuracy/11.3.138 | O | TLV | 3 | +| BTS Reception Accuracy Level (note 9) | BTS Reception Accuracy Level/11.3.139 | O | TLV | 3 | +| MTA Access Security Required (note 10) | MTA Access Security Required/11.3.142 | O | TLV | 3 | + +NOTE 1: This IE is present if the SGSN has valid DRX Parameters for the TLLI. + +NOTE 2: This IE is present if the SGSN has received the information from the MS. + +NOTE 3: This IE is present if the location type indicates a request for a location estimate and is optional otherwise. + +NOTE 4: This IE is present if GPS assistance data is requested. + +NOTE 5: The IMEI could be sent in addition to the IMSI for the purpose of allowing correlation between the two identities. + +NOTE 6: This IE is present if GANSS assistance data is requested. + +NOTE 7: If the SGSN has valid eDRX Parameters for a TLLI it shall include the eDRX Parameters IE in which case the DRX Parameters IE shall not be included. + +NOTE 8: The field shall be present if there is valid MS Radio Access Capability information for the MS known by the SGSN; the field shall not be present otherwise. + +NOTE 9: The IE shall be present if it was received for a given MS no more than 5 seconds prior to sending the PERFORM-LOCATION-REQUEST PDU to the BSS for that MS; the field shall not be present otherwise. + +Note 10: The IE is included if SGSN does not support LLC security and decides to request the use of MTA Access Security (MTA Access Security method or the BSS Duplication Detection method may be indicated). + +## 10.5.2 PERFORM-LOCATION-RESPONSE + +This PDU allows the BSS to respond to the SGSN after the completion of the location procedure. + +PDU type: PERFORM-LOCATION-RESPONSE + +Direction: BSS to SGSN + +**Table 10.5.2: PERFORM-LOCATION-RESPONSE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|--------------------------------------------------------------------------------------------------------|-----------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| BVCI (PCU-PTP) | BVCI/11.3.6 | M | TLV | 4 | +| Location Estimate (note 1) | Location Estimate/11.3.54 | C | TLV | 3-? | +| Positioning Data | Positioning Data/11.3.55 | O | TLV | 3-? | +| Deciphering Keys (note 2) | Deciphering Keys/11.3.56 | C | TLV | 3-? | +| LCS Cause (note 3) | LCS Cause/11.3.58 | O | TLV | 3-? | +| Velocity Data | Velocity Data/11.3.96 | O | TLV | 3-? | +| GANSS Positioning Data | GANSS Positioning Data / 11.3.101 | O | TLV | 3-? | +| MTA Sequence | MTA Sequence/11.3.143 | O | TLV | 7-? | +| MTA Signature | MTA Signature/11.3.144 | O | TLV | 6 | +| NOTE 1: This IE is present if the location of the target MS was requested and the procedure succeeded. | | | | | +| NOTE 2: This IE is present if the deciphering keys were requested and the procedure succeeded. | | | | | +| NOTE 3: This IE is present if the procedure failed. | | | | | + +## 10.5.3 PERFORM-LOCATION-ABORT + +This PDU allows the SGSN to request the BSS to ABORT the LCS procedure. + +PDU type: PERFORM-LOCATION-ABORT + +Direction: SGSN to BSS + +**Table 10.5.3: PERFORM-LOCATION-ABORT PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|----------------------|-------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| BVCI (PCU-PTP) | BVCI/11.3.6 | M | TLV | 4 | +| LCS Cause | LCS Cause/11.3.58 | M | TLV | 3-? | + +## 10.5.4 POSITION-COMMAND + +This PDU allows the BSS to request the SGSN to perform the position command procedure. + +PDU type: POSITION-COMMAND + +Direction: BSS to SGSN + +**Table 10.5.4: POSITION-COMMAND PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|------------------------|---------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| BVCI (PCU-PTP) | BVCI/11.3.6 | M | TLV | 4 | +| RRLP Flags | RRLP Flags/11.3.60 | M | TLV | 3 | +| RRLP APDU | RRLP APDU/11.3.49 | M | TLV | 3-? | +| Multilateration Timer | Multilateration Timer/11.3.136 | O | TLV | 3 | +| Timing Advance Request | Timing Advance Request/11.3.140 | O | TLV | 3 | + +## 10.5.5 POSITION-RESPONSE + +This PDU allows the SGSN to respond to the position command request procedure. + +PDU type: POSITION-RESPONSE + +Direction: SGSN to BSS + +**Table 10.5.5: POSITION-RESPONSE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------------------------|--------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TLLI | TLLI/11.3.35 | M | TLV | 6 | +| BVCI (PCU-PTP) | BVCI/11.3.6 | M | TLV | 4 | +| RRLP Flags a) | RRLP Flags/11.3.60 | C | TLV | 3 | +| RRLP APDU a) | RRLP APDU/11.3.49 | C | TLV | 3-? | +| LCS Cause b) | LCS Cause/11.3.58 | O | TLV | 3-? | +| a) This IE is present if the procedure succeeded. | | | | | +| b) This IE is present if the procedure failed. | | | | | + +## 10.6 PDU functional definitions and contents at RIM SAP + +### 10.6.1 RAN-INFORMATION-REQUEST + +The RAN-INFORMATION-REQUEST PDU allows a controlling BSS to request information from another BSS. + +PDU type: RAN-INFORMATION-REQUEST + +Direction: BSS to SGSN +SGSN to BSS + +**Table 10.6.1: RAN-INFORMATION-REQUEST PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------------|--------------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Destination Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| Source Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| RIM Container | RAN-INFORMATION-REQUEST RIM Container/11.3.62a.1 | M | TLV | 3-? | + +## 10.6.2 RAN-INFORMATION + +The RAN-INFORMATION PDU allows a serving or originating BSS to send information to a controlling or receiving BSS respectively. + +PDU type: RAN-INFORMATION + +Direction: BSS to SGSN +SGSN to BSS + +**Table 10.6.2: RAN-INFORMATION-PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------------|------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Destination Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| Source Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| RIM Container | RAN-INFORMATION RIM Container/11.3.62a.2 | M | TLV | 3-? | + +## 10.6.3 RAN-INFORMATION-ACK + +The RAN-INFORMATION-ACK PDU allows a controlling or receiving BSS to acknowledge the reception of a RAN-INFORMATION PDU and a serving or originating BSS to acknowledge the reception of a RAN-INFORMATION-APPLICATION-ERROR PDU. + +PDU type: RAN-INFORMATION-ACK + +Direction: BSS to SGSN +SGSN to BSS + +**Table 10.6.3: RAN-INFORMATION-ACK PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------------|----------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Destination Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| Source Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| RIM Container | RAN-INFORMATION-ACK RIM Container/11.3.62a.3 | M | TLV | 3-? | + +## 10.6.4 RAN-INFORMATION-ERROR + +The RAN-INFORMATION-ERROR PDU allows a BSS to send an error PDU back to an originating BSS as a response to a RAN-INFORMATION, a RAN-INFORMATION-REQUEST, a RAN-INFORMATION-ACK or a RAN-INFORMATION-APPLICATION-ERROR PDU. + +PDU type: RAN-INFORMATION-ERROR + +Direction: BSS to SGSN +SGSN to BSS + +**Table 10.6.4: RAN-INFORMATION-ERROR content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------------|------------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Destination Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| Source Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| RIM Container | RAN-INFORMATION-ERROR RIM Container/11.3.62a.4 | M | TLV | 3-? | + +## 10.6.5 RAN-INFORMATION-APPLICATION-ERROR + +The RAN-INFORMATION-APPLICATION-ERROR PDU allows a controlling or receiving BSS to inform the serving BSS or originating BSS (respectively) about erroneous application information in a previously received RAN-INFORMATION PDU. + +PDU type: RAN-INFORMATION-APPLICATION-ERROR + +Direction: BSS to SGSN +SGSN to BSS + +**Table 10.6.5: RAN-INFORMATION-APPLICATION-ERROR PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------------|------------------------------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| Destination Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| Source Cell Identifier | RIM Routing Information/11.3.70 | M | TLV | 3-? | +| RIM Container | RAN-INFORMATION-APPLICATION-ERROR RIM Container/11.3.62a.5 | M | TLV | 3-? | + +## 10.7 PDU functional definitions and contents at MBMS SAP + +### 10.7.1 MBMS-SESSION-START-REQUEST + +This PDU allows a SGSN to request BSS to start an MBMS session. + +PDU type: MBMS-SESSION-START-REQUEST + +Direction: SGSN to BSS + +**Table 10.7.1: MBMS-SESSION-START-REQUEST PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|-----------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TMGI | TMGI/11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/11.3.71 | O | TLV | 3 | +| ABQP | ABQP/11.3.43 | M | TLV | 13-? | +| MBMS Service Area Identity List | MBMS Service Area Identity List/11.3.73 | M | TLV | 4-? | +| MBMS Routing Area List | MBMS Routing Area List/11.3.75 | M | TLV | 3-? | +| MBMS Session Duration | MBMS Session Duration/11.3.72 | M | TLV | 3-? | +| MBMS Session Information | MBMS Session Information/11.3.76 | M | TLV | 3 | +| Time to MBMS Data Transfer | Time to MBMS Data Transfer/11.3.92 | M | TLV | 3 | +| Allocation/Retention Priority | Priority/11.3.27 | O | TLV | 3 | +| MBMS Session Repetition Number | MBMS Session Repetition Number/11.3.93 | O | TLV | 3 | + +### 10.7.2 + +### START-RESPONSE + +### MBMS-SESSION- + +This PDU allows a BSS to acknowledge to SGSN that it will start an MBMS session or to indicate to SGSN why the MBMS Service Context cannot be created or is released by the BSS. + +PDU type: MBMS-SESSION-START-RESPONSE + +Direction: BSS to SGSN + +**Table 10.7.2: MBMS-SESSION-START-RESPONSE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------|--------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TMGI | TMGI/ 11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/ 11.3.71 | O | TLV | 3 | +| MBMS Response | MBMS Response/ 11.3.74 | M | TLV | 3 | + +### 10.7.3 MBMS-SESSION-STOP-REQUEST + +This PDU allows a SGSN to request BSS to stop an MBMS session. + +PDU type: MBMS-SESSION-STOP-REQUEST + +Direction: SGSN to BSS + +**Table 10.7.3: MBMS-SESSION-STOP-REQUEST PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------|--------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TMGI | TMGI/ 11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/ 11.3.71 | O | TLV | 3 | +| MBMS Stop Cause | MBMS Stop Cause/11.3.78 | M | TLV | 3 | + +### 10.7.4 MBMS-SESSION-STOP-RESPONSE + +This PDU allows a BSS to acknowledge to SGSN that it will stop an MBMS session. + +PDU type: MBMS-SESSION-STOP-RESPONSE + +Direction: BSS to SGSN + +**Table 10.7.4: MBMS-SESSION-STOP-RESPONSE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------|--------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TMGI | TMGI/ 11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/ 11.3.71 | O | TLV | 3 | +| MBMS Response | MBMS Response/ 11.3.74 | M | TLV | 3 | + +### 10.7.5 MBMS-SESSION-UPDATE-REQUEST + +This PDU allows an SGSN to request BSS to update the MBMS service area list of an ongoing MBMS broadcast service session. + +PDU type: MBMS-SESSION-UPDATE-REQUEST + +Direction: SGSN to BSS + +**Table 10.7.5: MBMS-SESSION-UPDATE-REQUEST PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|---------------------------------|-----------------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TMGI | TMGI/11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/11.3.71 | O | TLV | 3 | +| ABQP | ABQP/11.3.43 | M | TLV | 13-? | +| MBMS Service Area Identity List | MBMS Service Area Identity List/11.3.73 | M | TLV | 4-? | +| MBMS Routing Area List | MBMS Routing Area List/11.3.75 | M | TLV | 3-? | +| MBMS Session Duration | MBMS Session Duration/11.3.72 | M | TLV | 3-? | +| MBMS Session Information | MBMS Session Information/11.3.76 | M | TLV | 3 | +| Time to MBMS Data Transfer | Time to MBMS Data Transfer/11.3.92 | M | TLV | 3 | +| Allocation/Retention Priority | Priority/11.3.27 | O | TLV | 3 | +| MBMS Session Repetition Number | MBMS Session Repetition Number/11.3.93 | O | TLV | 3 | + +## 10.7.6 UPDATE-RESPONSE + +## MBMS-SESSION- + +This PDU allows a BSS to acknowledge to SGSN that it will update the MBMS service area list of an ongoing MBMS broadcast service session or to indicate to SGSN why the MBMS Service Context cannot be created or is released by the BSS. + +PDU type: MBMS-SESSION-UPDATE-RESPONSE + +Direction: BSS to SGSN + +**Table 10.7.6: MBMS-SESSION-UPDATE-RESPONSE PDU content** + +| Information elements | Type / Reference | Presence | Format | Length | +|-----------------------|--------------------------------|----------|--------|--------| +| PDU type | PDU type/11.3.26 | M | V | 1 | +| TMGI | TMGI/ 11.3.77 | M | TLV | 3-8 | +| MBMS Session Identity | MBMS Session Identity/ 11.3.71 | O | TLV | 3 | +| MBMS Response | MBMS Response/ 11.3.74 | M | TLV | 3 | + +--- + +# 11 General information elements coding + +The figures and text in this sub-clause describe the Information Elements contents. + +## 11.1 General structure of the information elements + +Refer to General Structure Of The Information Elements/3GPP TS 48.016. + +## 11.2 Information element description + +Refer to Information Element Description/3GPP TS 48.016. + +## 11.3 Information Element Identifier (IEI) + +An Information Element Identifier (IEI) is identified by the same coding in all BSSGP PDUs. + +**Table 11.3: IEI types** + +| IEI coding
(hexadecimal) | IEI Types | +|-----------------------------|-----------------------------------------------| +| x00 | Alignment Octets | +| x01 | Bmax default MS | +| x02 | BSS Area Indication | +| x03 | Bucket Leak Rate | +| x04 | BVCI | +| x05 | BVC Bucket Size | +| x06 | BVC Measurement | +| x07 | Cause | +| x08 | Cell Identifier | +| x09 | Channel needed | +| x0a | DRX Parameters | +| x0b | eMLPP-Priority | +| x0c | Flush Action | +| x0d | IMSI | +| x0e | LLC-PDU | +| x0f | LLC Frames Discarded | +| x10 | Location Area | +| x11 | Mobile Id | +| x12 | MS Bucket Size | +| x13 | MS Radio Access Capability | +| x14 | OMC Id | +| x15 | PDU In Error | +| x16 | PDU Lifetime | +| x17 | Priority | +| x18 | QoS Profile | +| x19 | Radio Cause | +| x1a | RA-Cap-UPD-Cause | +| x1b | Routeing Area | +| x1c | R_default_MS | +| x1d | Suspend Reference Number | +| x1e | Tag | +| x1f | TLLI | +| x20 | TMSI | +| x21 | Trace Reference | +| x22 | Trace Type | +| x23 | TransactionId | +| x24 | Trigger Id | +| x25 | Number of octets affected | +| x26 | LSA Identifier List | +| x27 | LSA Information | +| x28 | Packet Flow Identifier | +| x29 | GPRS Timer | +| x3a | Aggregate BSS QoS Profile (ABQP) | +| x3b | Feature Bitmap | +| x3c | Bucket_Full Ratio | +| x3d | Service UTRAN CCO (Cell Change Order) | +| x3e | NSEI | +| x3f | RRLP APDU | +| x40 | LCS QoS | +| x41 | LCS Client Type | +| x42 | Requested GPS Assistance Data | +| x43 | Location Type | +| x44 | Location Estimate | +| x45 | Positioning Data | +| x46 | Deciphering Keys | +| x47 | LCS Priority | +| x48 | LCS Cause | +| x49 | LCS Capability | +| x4a | RRLP Flags | +| x4b | RIM Application Identity | +| x4c | RIM Sequence number | +| x4d | RAN-INFORMATION-REQUEST Application Container | + +| IEI coding
(hexadecimal) | IEI Types | +|-----------------------------|-----------------------------------------------------------------------------------------------| +| x4e | RAN-INFORMATION Application Container | +| x4f | RIM PDU Indications | +| x50 | This value is reserved for future use and shall be treated by the recipient as an unknown IEI | +| x51 | This value should not be used, as it has been used in earlier versions of this protocol. | +| x52 | PFC flow control parameters | +| x53 | Global CN-Id | +| x54 | RIM Routing Information | +| x55 | RIM Protocol Version Number | +| x56 | Application Error Container | +| x57 | RAN-INFORMATION-REQUEST RIM Container | +| x58 | RAN-INFORMATION RIM Container | +| x59 | RAN-INFORMATION-APPLICATION-ERROR RIM Container | +| x5a | RAN-INFORMATION-ACK RIM Container | +| x5b | RAN-INFORMATION-ERROR RIM Container | +| x5c | TMGI | +| x5d | MBMS Session Identity | +| x5e | MBMS Session Duration | +| x5f | MBMS Service Area Identity List | +| x60 | MBMS Response | +| x61 | MBMS Routing Area List | +| x62 | MBMS Session Information | +| x63 | MBMS Stop Cause | +| x64 | Source BSS to Target BSS Transparent Container | +| x65 | Target BSS to Source BSS Transparent Container | +| x66 | NAS container for PS Handover | +| x67 | PFCs to be set-up list | +| x68 | List of set-up PFCs | +| x69 | Extended Feature Bitmap | +| x6a | Source to Target Transparent Container | +| x6b | Target to Source Transparent Container | +| x6c | RNC Identifier | +| x6d | Page Mode | +| x6e | Container ID | +| x6f | Global TFI | +| x70 | IMEI | +| x71 | Time to MBMS Data Transfer | +| x72 | MBMS Session Repetition Number | +| x73 | Inter RAT Handover Info | +| x74 | PS Handover Command | +| x75 | PS Handover Indications | +| x76 | SI/PSI Container | +| x77 | Active PFCs List | +| x78 | Velocity Data | +| x79 | DTM Handover Command | +| x7a | CS Indication | +| x7b | Requested GANSS Assistance Data | +| x7c | GANSS Location Type | +| x7d | GANSS Positioning Data | +| x7e | Flow Control Granularity | +| x7f | eNB Identifier | +| x80 | E-UTRAN Inter RAT Handover Info | +| x81 | Subscriber Profile ID for RAT/Frequency priority | +| x82 | Request for Inter RAT Handover Info | +| x83 | Reliable Inter RAT Handover Info | +| x84 | SON Transfer Application Identity | +| x85 | CSG Identifier | +| x86 | TAC | +| x87 | Redirect Attempt Flag | +| x88 | Redirection Indication | +| x89 | Redirection Completed | + +| IEI coding (hexadecimal) | IEI Types | +|--------------------------|----------------------------------------------------| +| x8a | Unconfirmed send state variable | +| x8b | IRAT Measurement Configuration | +| x8c | SCI | +| X8d | GGSN/P-GW location | +| x8e | Selected PLMN ID | +| x8f | Priority Class Indicator | +| x90 | Source Cell ID | +| x91 | IRAT Measurement Configuration (extended E-ARFCNs) | +| x92 | eDRX Parameters | +| x93 | Time Until Next Paging Occasion | +| x98 | Coverage Class | +| X99 | Paging Attempt Information | +| X9a | Exception Report Flag | +| x9b | Old Routing Area Identification | +| x9c | Attach Indicator | +| x9d | PLMN Identity | +| x9e | MME Query | +| x9f | SGSN Group Identity | +| xa0 | Additional P-TMSI | +| xa1 | UE Usage Type | +| xa2 | Multilateral Timer | +| xa3 | Multilateral Timing Advance | +| xa4 | MS Sync Accuracy | +| xa5 | BTS Reception Accuracy Level | +| xa6 | Timing Advance Request | + +### 11.3.1 Alignment octets + +The Alignment Octets are used to align a subsequent IEI onto a 32 bit boundary. The element coding is: + +**Table 11.3.1: Alignment octets IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator (note) | | | | | | | | +| octet 3-5 | spare octet | | | | | | | | +| NOTE: | The Length Indicator may indicate that from 0 to 3 spare octets are present. | | | | | | | | + +### 11.3.2 Bmax default MS + +This information element indicates the default bucket size (Bmax) in octets for an MS. The element coding is: + +**Table 11.3.2: Bmax default MS IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | Bmax | | | | | | | | + +The Bmax field is coded as Bmax of BVC Bucket Size, see sub-clause 11.3.5. + +### 11.3.3 BSS Area Indication + +This element is used to indicate that the paging shall be done in all the cells within the BSS. The element coding is: + +**Table 11.3.3: BSS Area Indication IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--|---|---|---|---|---|---|---|---| +|--|---|---|---|---|---|---|---|---| + +| | | +|-------------|------------------| +| octet 1 | IEI | +| octet 2, 2a | Length Indicator | +| octet 3 | BSS indicator | + +The coding of octet 2 is a binary number indicating the Length of the remaining element. + +The coding of octet 3 shall not be specified. The recipient shall ignore the value of this octet. + +### 11.3.4 Bucket Leak Rate (R) + +This information element indicates the leak rate (R) to be applied to a flow control bucket. The element coding is: + +**Table 11.3.4: Bucket Leak Rate IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | R Value (MSB) | | | | | | | | +| octet 4 | R Value (LSB) | | | | | | | | + +If the Gigabit Interface feature has not been negotiated, the R field is the binary encoding of the rate information expressed in 100 bits/s increments, starting from 0 x 100 bits/s until 65 535 x 100 bits/s (6 Mbps). + +If the Gigabit Interface feature has been negotiated, the R field is the binary encoding of the rate information expressed in increments as defined by the *Flow Control Granularity* IE. + +### 11.3.5 BVC Bucket Size + +This information element indicates the maximum bucket size (Bmax) in octets for a BVC. The element coding is: + +**Table 11.3.5: BVC Bucket Size IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Bmax (MSB) | | | | | | | | +| octet 4 | Bmax (LSB) | | | | | | | | + +If the Gigabit Interface feature has not been negotiated, the Bmax field is the binary encoding of the bucket-size information expressed in 100 octet increments, starting from 0 x 100 octets until 65 535 x 100 octets (6 Mbytes). + +If the Gigabit Interface feature has been negotiated, the Bmax field is the binary encoding of the rate information expressed in increments as defined by the *Flow Control Granularity* IE. + +### 11.3.6 BVCI (BSSGP Virtual Connection Identifier) + +The BVCI identifies a BVC. The element coding is: + +**Table 11.3.6: BVCI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | Unstructured value | | | | | | | | + +### 11.3.7 BVC Measurement + +This information element describes average queuing delay for a BVC. The element coding is: + +**Table 11.3.7: BVC Measurement IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3,4 | Delay Value (in centi-seconds) | | | | | | | | + +The Delay Value field is coded as a 16-bit integer value in units of centi-seconds (one hundredth of a second). This coding provides a range of over 10 minutes in increments of 10 ms. As a special case, the hexadecimal value 0xFFFF (decimal 65 535) shall be interpreted as "infinite delay". + +### 11.3.8 Cause + +The Cause information element indicates the reason for an exception condition. The element coding is: + +**Table 11.3.8.a: Cause IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Cause value | | | | | | | | + +**Table 11.3.8.b: Cause coding** + +| Cause value
Hexadecimal | Semantics of coding | +|----------------------------|-----------------------------------------------------------------------------------------| +| | All values not listed below shall be treated as "protocol error - unspecified" | +| x00 | Processor overload | +| x01 | Equipment failure | +| x02 | Transit network service failure | +| x03 | Network service transmission capacity modified from zero kbps to greater than zero kbps | +| x04 | Unknown MS | +| x05 | BVCI unknown | +| x06 | cell traffic congestion | +| x07 | SGSN congestion | +| x08 | O&M intervention | +| x09 | BVCI-blocked | +| x0a | PFC create failure | +| x0b | PFC preempted | +| x0c | ABQP no more supported | +| x20 | Semantically incorrect PDU | +| x21 | Invalid mandatory information | +| x22 | Missing mandatory IE | +| x23 | Missing conditional IE | +| x24 | Unexpected conditional IE | +| x25 | Conditional IE error | +| x26 | PDU not compatible with the protocol state | +| x27 | Protocol error - unspecified | +| x28 | PDU not compatible with the feature set | +| x29 | Requested Information not available | +| x2a | Unknown Destination address | +| x2b | Unknown RIM Application Identity or RIM application disabled | +| x2c | Invalid Container Unit Information | +| x2d | PFC queuing | +| x2e | PFC created successfully | +| x2f | T12 expiry | +| x30 | MS under PS Handover treatment | +| x31 | Uplink quality | +| x32 | Uplink strength | +| x33 | Downlink quality | +| x34 | Downlink strength | +| x35 | Distance | +| x36 | Better cell | +| x37 | Traffic | +| x38 | Radio contact lost with MS | +| x39 | MS back on old channel | +| x3a | T13 expiry | +| x3b | T14 expiry | +| x3c | Not all requested PFCs created | +| x3d | CS cause | +| x3e | Requested ciphering and/or integrity protection algorithms not supported | +| x3f | Relocation failure in target system | +| x40 | Directed Retry | +| x41 | Time critical relocation | +| x42 | PS Handover Target not allowed | +| x43 | PS Handover not Supported in Target BSS or Target System | +| x44 | Incoming relocation not supported due to PUESBINE feature | +| x45 | DTM Handover - No CS resource | +| x46 | DTM Handover - PS Allocation failure | +| x47 | DTM Handover - T24 expiry | +| x48 | DTM Handover - Invalid CS Indication IE | +| x49 | DTM Handover - T23 expiry | + +| | | +|------------|--------------------------------------------------------------------------| +| x4a | DTM Handover - MSC Error | +| x4b | Invalid CSG cell | +| x80 to x87 | Reserved for further definition of non-critical PS handover cause values | + +NOTE: If received, cause values x80 to x87 inclusive indicate a non-critical PS Handover (see sub-clause 8a.5). + +### 11.3.9 Cell Identifier + +This information element uniquely identifies one cell. The element coding is: + +**Table 11.3.9: Cell Identifier IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octets 3-8 | Octets 3 to 8 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | | | | | | | | +| octets 9-10 | Octets 9 and 10 contain the value part (starting with octet 2) of the Cell Identity IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | | | | | | | | + +### 11.3.10 Channel needed + +This information element is coded as defined in 3GPP TS 29.018. It is relevant to circuit-switched paging requests. The element coding is: + +**Table 11.3.10: Channel needed IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Rest of element coded as the value part of the Channel Needed PDU defined in 3GPP TS 29.018, not including 3GPP TS 29.018 IEI and 3GPP TS 29.018 length indicator | | | | | | | | + +### 11.3.11 DRX Parameters + +This information element contains MS specific DRX information. The element coding is: + +**Table 11.3.11: DRX Parameters IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator | | | | | | | | + +### 11.3.12 eMLPP-Priority + +This element indicates the eMLPP-Priority of a PDU. The element coding is: + +**Table 11.3.12: eMLPP-Priority IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--|---|---|---|---|---|---|---|---| +|--|---|---|---|---|---|---|---|---| + +| | | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| octet 1 | IEI | +| octet 2, 2a | Length Indicator | +| octet 3 | Rest of element coded as the value part of the eMLPP-Priority IE defined in 3GPP TS 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator | + +### 11.3.13 Flush Action + +The Flush action information element indicates to the SGSN the action taken by the BSS in response to the flush request. The element coding is: + +**Table 11.3.13.a: Flush Action IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Action value | | | | | | | | + +**Table 11.3.13.b: Action coding** + +| Action value
Hexadecimal | Semantics of coding | +|-----------------------------|-------------------------------------------------------------| +| x00 | LLC-PDU(s) deleted | +| x01 | LLC-PDU(s) transferred | +| | All values not explicitly shown are reserved for future use | + +### 11.3.14 IMSI + +This information element contains the International Mobile Subscriber Identity (see 3GPP TS 23.003). The element coding is: + +**Table 11.3.14: IMSI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Octets 3-n contain an IMSI coded as the value part of the Mobile Identity IE defined in 3GPP TS 24.008 (NOTE 1) | | | | | | | | +| NOTE 1: The Type of identity field in the Mobile Identity IE shall be ignored by the receiver. | | | | | | | | | + +### 11.3.15 LLC-PDU + +This information element contains an LLC-PDU. The element coding is: + +**Table 11.3.15: LLC-PDU IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | LLC-PDU (first part) | | | | | | | | +| octet n | LLC-PDU (last part) | | | | | | | | + +### 11.3.16 LLC Frames Discarded + +This element describes the number of LLC frames that have been discarded inside a BSS. The element coding is: + +**Table 11.3.16: LLC Frames Discarded IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Number of frames discarded (in hexadecimal) | | | | | | | | + +### 11.3.17 Location Area + +This element uniquely identifies one Location Area. The element coding is: + +**Table 11.3.17: Location Area IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octets 3-7 | Octets 3 to 7 contain the value part (starting with octet 2) of the Location Area Identification IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | | | | | | | | + +The coding of octet 2 is a binary number indicating the Length of the remaining element. + +### 11.3.18 LSA Identifier List + +This information element uniquely identifies LSAs. The element coding is: + +**Table 11.3.18: LSA Identifier List IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-? | Rest of element coded as in 3GPP TS 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator | | | | | | | | + +### 11.3.19 LSA Information + +This information element uniquely identifies LSAs, the priority of each LSA and the access right outside these LSAs. The element coding is: + +**Table 11.3.19: LSA Information IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-? | Rest of element coded as in 3GPP TS 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator | | | | | | | | + +### 11.3.20 Mobile Id + +The element coding is: + +**Table 11.3.20: Mobile Id IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Octets 3-n contain either the IMSI, IMEISV or IMEI coded as the value part (starting with octet 3) of the Mobile Identity IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator | | | | | | | | + +### 11.3.21 MS Bucket Size + +This information element indicates an MS's bucket size (Bmax). The element coding is: + +**Table 11.3.21: MS Bucket Size IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | Bmax | | | | | | | | + +The Bmax field is coded as Bmax of BVC Bucket Size, see sub-clause 11.3.5. + +### 11.3.22 MS Radio Access Capability + +This information element contains the capabilities of the ME. The element coding is: + +**Table 11.3.22: MS Radio Access Capability IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-? | Rest of element coded as the value part defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator. | | | | | | | | + +### 11.3.23 OMC Id + +The element coding is: + +**Table 11.3.23: OMC Id IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-22 | For the OMC identity, see 3GPP TS 12.20 | | | | | | | | + +### 11.3.24 PDU In Error + +The element coding is: + +**Table 11.3.24: PDU In Error IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-? | Erroneous BSSGP PDU | | | | | | | | + +### 11.3.25 PDU Lifetime + +This information element describes the PDU Lifetime for a PDU inside the BSS. The element coding is: + +**Table 11.3.25: PDU Lifetime IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | Delay Value | | | | | | | | + +The Delay Value field is coded as Delay Value of BVC Measurement, see sub-clause 11.3.7. + +## 11.3.26 PDU Type + +The first octet of a BSSGP PDU shall contain the PDU type IE. The PDU type IE is one octet long. + +**Table 11.3.26: PDU Types** + +| PDU type coding
(Hexadecimal) | PDU Types | +|---------------------------------------|----------------------------------| +| PDUs between RL and BSSGP SAPs | | +| x00 | DL-UNITDATA | +| x01 | UL-UNITDATA | +| x02 | RA-CAPABILITY | +| x03 | reserved (Note 1) | +| x04 | DL-MBMS-UNITDATA | +| x05 | UL-MBMS-UNITDATA | +| PDUs between GMM SAPs | | +| x06 | PAGING-PS | +| x07 | PAGING-CS | +| x08 | RA-CAPABILITY-UPDATE | +| x09 | RA-CAPABILITY-UPDATE-ACK | +| x0a | RADIO-STATUS | +| x0b | SUSPEND | +| x0c | SUSPEND-ACK | +| x0d | SUSPEND-NACK | +| x0e | RESUME | +| x0f | RESUME-ACK | +| x10 | RESUME-NACK | +| x11 | PAGING-PS-REJECT | +| x12 | DUMMY-PAGING-PS | +| x13 | DUMMY-PAGING-PS-RESPONSE | +| x14 | MS-REGISTRATION-ENQUIRY | +| x15 | MS-REGISTRATION-ENQUIRY-RESPONSE | +| PDUs between NM SAPs | | +| x20 | BVC-BLOCK | +| x21 | BVC-BLOCK-ACK | +| x22 | BVC-RESET | +| x23 | BVC-RESET-ACK | +| x24 | BVC-UNBLOCK | +| x25 | BVC-UNBLOCK-ACK | +| x26 | FLOW-CONTROL-BVC | +| x27 | FLOW-CONTROL-BVC-ACK | +| x28 | FLOW-CONTROL-MS | +| x29 | FLOW-CONTROL-MS-ACK | +| x2a | FLUSH-LL | +| x2b | FLUSH-LL-ACK | +| x2c | LLC-DISCARDED | +| x2d | FLOW-CONTROL-PFC | +| x2e | FLOW-CONTROL-PFC-ACK | +| x40 | SGSN-INVOKE-TRACE | +| x41 | STATUS | +| x42 | OVERLOAD | +| PDUs between PFM SAPs | | +| 0x50 | DOWNLOAD-BSS-PFC | +| 0x51 | CREATE-BSS-PFC | +| 0x52 | CREATE-BSS-PFC-ACK | +| 0x53 | CREATE-BSS-PFC-NACK | +| 0x54 | MODIFY-BSS-PFC | +| 0x55 | MODIFY-BSS-PFC-ACK | +| 0x56 | DELETE-BSS-PFC | +| 0x57 | DELETE-BSS-PFC-ACK | +| 0x58 | DELETE-BSS-PFC-REQ | +| 0x59 | PS-HANDOVER-REQUIRED | +| 0x5a | PS-HANDOVER-REQUIRED-ACK | +| 0x5b | PS-HANDOVER-REQUIRED-NACK | +| 0x5c | PS-HANDOVER-REQUEST | +| 0x5d | PS-HANDOVER-REQUEST-ACK | +| 0x5e | PS-HANDOVER-REQUEST-NACK | +| 0x91 | PS-HANDOVER-COMPLETE | +| 0x92 | PS-HANDOVER-CANCEL | +| 0x93 | PS-HANDOVER-COMPLETE-ACK | + +| PDU type coding (Hexadecimal) | PDU Types | +|-----------------------------------------------------------------------------------------------|-------------------------------------------------------------| +| PDUs between LCS SAPs | | +| 0x60 | PERFORM-LOCATION-REQUEST | +| 0x61 | PERFORM-LOCATION-RESPONSE | +| 0x62 | PERFORM-LOCATION-ABORT | +| 0x63 | POSITION-COMMAND | +| 0x64 | POSITION-RESPONSE | +| PDUs between RIM SAPs | | +| 0x70 | RAN-INFORMATION | +| 0x71 | RAN-INFORMATION-REQUEST | +| 0x72 | RAN-INFORMATION-ACK | +| 0x73 | RAN-INFORMATION-ERROR | +| 0x74 | RAN-INFORMATION-APPLICATION-ERROR | +| PDUs between MBMS SAPs | | +| 0x80 | MBMS-SESSION-START-REQUEST | +| 0x81 | MBMS-SESSION-START-RESPONSE | +| 0x82 | MBMS-SESSION-STOP-REQUEST | +| 0x83 | MBMS-SESSION-STOP-RESPONSE | +| 0x84 | MBMS-SESSION-UPDATE-REQUEST | +| 0x85 | MBMS-SESSION-UPDATE-RESPONSE | +| RESERVED | all values not explicitly shown are reserved for future use | +| NOTE 1: This value was allocated in an earlier version of the protocol and shall not be used. | | + +### 11.3.27 Priority + +This element indicates the priority of a PDU. The element coding is: + +**Table 11.3.27: Priority IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Rest of element coded as the value part of the Priority IE defined in 3GPP TS 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator | | | | | | | | + +### 11.3.28 QoS Profile + +This information element describes the QoS Profile associated with a PDU. The element coding is: + +**Table 11.3.28.a: QoS Profile IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|------------------------------------------------------------------|----------------------------------------------|-----|---|---|------------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | Peak bit rate provided by the network (note) | | | | | | | | +| octet 5 | Peak Bit Rate Granularity | C/R | T | A | Precedence | | | | +| NOTE: The bit rate 0 (zero) shall mean "best effort" in this IE. | | | | | | | | | + +"Peak bit rate" is coded as shown below: + +**Table 11.3.28.a1: Peak bit rate** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|---------------------------|---|---|---|---|---|---|---| +| octet 3 | Peak bit rate value (MSB) | | | | | | | | +| octet 4 | Peak bit rate value (LSB) | | | | | | | | + +If the Gigabit Interface feature has not been negotiated, the "Peak bit rate" field is the binary encoding of the peak bit rate information expressed in 100 bits/s increments, starting from 0 x 100 bits/s until 65 535 x 100 bits/s (6.5535 Mbps). + +If the Gigabit Interface feature has been negotiated, the "Peak bit rate" field is the binary encoding of the peak bit rate information expressed in increments as defined by the *Peak Bit Rate Granularity* field. + +"Precedence" is coded as shown below (complying with 3GPP TS 23.060). + +**Table 11.3.28.b: Precedence coding** + +| coding | semantic | | +|--------|-----------------|------------------------| +| | DL-UNITDATA | UL-UNITDATA | +| 000 | High priority | Radio priority 1 | +| 001 | Normal priority | Radio priority 2 | +| 010 | Low priority | Radio priority 3 | +| 011 | Reserved | Radio priority 4 | +| 100 | Reserved | Radio Priority Unknown | + +All values not allocated are reserved. All reserved values shall be interpreted as value 010. + +"A-bit" is coded as shown below. + +**Table 11.3.28.c: "A bit" coding** + +| coding | semantic | +|--------|-----------------------------------------------------| +| 0 | Radio interface uses RLC/MAC ARQ functionality | +| 1 | Radio interface uses RLC/MAC-UNITDATA functionality | + +"T-bit" is coded as shown below. + +**Table 11.3.28.d: "T bit" coding** + +| coding | semantic | +|--------|---------------------------------------------------| +| 0 | The SDU contains signalling (e.g. related to GMM) | +| 1 | The SDU contains data | + +"C/R-bit" is coded as shown below. + +**Table 11.3.28.e: "C/R bit" coding** + +| coding | semantic | +|--------|------------------------------------------------------------------------| +| 0 | The SDU contains a LLC ACK or SACK command/response frame type | +| 1 | The SDU does not contain a LLC ACK or SACK command/response frame type | + +"Peak Bit Rate Granularity" is coded as shown below. + +**Table 11.3.28.f: "Peak Bit Rate Granularity" coding** + +| coding | semantic | +|--------|--------------------------| +| 00 | 100 bits/s increments | +| 01 | 1000 bits/s increments | +| 10 | 10000 bits/s increments | +| 11 | 100000 bits/s increments | + +This field provides the granularity to be used for deriving the peak bit rate value if the Gigabit Interface feature is negotiated. + +## 11.3.29 Radio Cause + +This information element indicates the reason for an exception condition on the radio interface. The element coding is: + +**Table 11.3.29.a: Radio Cause IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Radio Cause value | | | | | | | | + +**Table 11.3.29.b: Radio Cause value** + +| radio cause value
Hexadecimal | Semantics of coding | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| x00 | Radio contact lost with the MS | +| x01 | Radio link quality insufficient to continue communication | +| x02 | cell-reselection ordered | +| x03 | Cell reselection prepare. See Note below. | +| x04 | Cell reselection failure. See Note below. | +| | All values not explicitly listed are reserved. If received, they shall be handled as "radio contact lost with the MS". | +| NOTE: In case the Enhanced Radio Status feature has not been negotiated the Radio Cause values in range of x03-x04 should if received be handled as "radio contact lost with the MS". This is in order to be backwards compatible with earlier releases of the standard. | | + +### 11.3.30 RA-Cap-UPD-Cause + +The RA-Cap-UPD-Cause indicates the success of the RA-CAPABILITY-UPDATE procedure or the reason of the failure. The element coding is: + +**Table 11.3.30.a: RA-Cap-UPD-Cause IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | RA-Cap-UPD Cause value | | | | | | | | + +**Table 11.3.30.b: RA-Cap-UPD Cause value** + +| RA-Cap-UPD cause
value
Hexadecimal | Semantics of coding | +|------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| x00 | OK, RA capability IE present | +| x01 | TLLI unknown in SGSN | +| x02 | No RA Capabilities or IMSI available for this MS | +| | All values not explicitly listed are reserved. If received, they shall be handled as "TLLI unknown in SGSN". | + +### 11.3.31 Routeing Area + +This element uniquely identifies one routeing area. The element coding is: + +**Table 11.3.31: Routeing Area IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--|---|---|---|---|---|---|---|---| +|--|---|---|---|---|---|---|---|---| + +| | | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| octet 1 | IEI | +| octet 2, 2a | Length Indicator | +| octets 3-8 | Octets 3 to 8 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | + +The coding of octet 2 is a binary number indicating the Length of the remaining element. + +### 11.3.32 R\_default\_MS + +This information element indicates the default bucket leak rate (R) to be applied to a flow control bucket for an MS. The element coding is: + +**Table 11.3.32: R\_default\_MS IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | R_default_MS value | | | | | | | | + +The R\_default\_MS value field is coded as The "R Value" of Bucket Leak Rate, see sub-clause 11.3.4. + +### 11.3.33 Suspend Reference Number + +The Suspend Reference Number information element contains an un-formatted reference number for each suspend/resume transaction. The element coding is: + +**Table 11.3.33: Suspend Reference Number IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Suspend Reference Number | | | | | | | | + +The Suspend Reference Number is an un-formatted 8 bit field. + +### 11.3.34 Tag + +This information element is used to correlate request and response PDUs. The element coding is: + +**Table 11.3.34: Tag IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Unstructured value | | | | | | | | + +### 11.3.35 Temporary logical link Identity (TLLI) + +The element coding is: + +**Table 11.3.35: TLLI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-6 | Rest of element coded as the value part of the TLLI information element in 3GPP TS 44.018, not including 3GPP TS 44.018 IEI. | | | | | | | | + +### 11.3.36 Temporary Mobile Subscriber Identity (TMSI) + +The element coding is: + +**Table 11.3.36: TMSI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-6 | Rest of element coded as the value part of the TMSI/P-TMSI information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI. | | | | | | | | + +### 11.3.37 Trace Reference + +This element provides a trace reference number allocated by the triggering entity. The element coding is: + +**Table 11.3.37: Trace Reference IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | Trace Reference | | | | | | | | + +### 11.3.38 Trace Type + +This element provides the type of trace information to be recorded. The element coding is: + +**Table 11.3.38: Trace Type IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|-----------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | This is coded as specified in Technical Specification 3GPP TS 32.008. | | | | | | | | + +### 11.3.39 Transaction Id + +This element indicates a particular transaction within a trace. The element coding is: + +**Table 11.3.39: Transaction Id IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-4 | Transaction Id | | | | | | | | + +### 11.3.40 Trigger Id + +This element provides the identity of the entity which initiated the trace. The element coding is: + +**Table 11.3.40: Trigger Id IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|----------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-22 | Entity Identity ( typically an OMC identity) | | | | | | | | + +### 11.3.41 Number of octets affected + +This information element indicates, for an MS, the number of octets transferred or deleted by BSS. The element coding is: + +**Table 11.3.41: Number of octets affected IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-5 | number of octets transferred or deleted | | | | | | | | + +The number of octets transferred or deleted by the BSS may be higher than the maximum Bmax value (6 553 500). SGSN shall handle any value higher than 6 553 500 as the value 6 553 500. + +### 11.3.42 Packet Flow Identifier (PFI) + +This information element indicates the Packet Flow Identifier for a BSS Packet Flow Context. The element coding is: + +**Table 11.3.42: Packet Flow Identifier (PFI) IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Rest of element coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | | | | | | | | + +The BSS shall not negotiate BSS PFCs for the following pre-defined PFI values: Best Effort, Signaling, SMS, and TOM8. + +PFIs have local significance to a mobile station. A BSS Packet Flow Context shall be uniquely identified by the PFI along with the IMSI or TLLI within a routing area. + +### 11.3.42a (void) + +### 11.3.43 Aggregate BSS QoS Profile + +This information element indicates the Aggregate BSS QoS Profile (ABQP) for a BSS Packet Flow Context or an MBMS Service Context. The ABQP is considered to be a single parameter with multiple data transfer attributes as defined in 3GPP TS 23.107. + +The element coding is: + +**Table 11.3.43: Aggregate BSS QoS Profile IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-? | Rest of element coded as the value part of the QoS information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and length indicator. The shorter 3-byte form of QoS information is not allowed in BSSGP PDUs. | | | | | | | | + +### 11.3.44 GPRS Timer + +The purpose of the *GPRS timer* information element is to specify GPRS specific timer values, e.g. the Packet Flow timer. + +**Table 11.3.44: GPRS Timer IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|-------------|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Unit Value | | | Timer value | | | | | + +Timer value: Bits 5 to 1 represent the binary coded timer value. + +Unit value: Bits 6 to 8 defines the timer value unit for the GPRS timer as follows: + +Bits + +**8 7 6** + +0 0 0 value is incremented in multiples of 2 s + +0 0 1 value is incremented in multiples of 1 minute + +0 1 0 value is incremented in multiples of decihours + +0 1 1 value is incremented in multiples of 500 msec + +1 1 1 value indicates that the timer does not expire. + +Other values shall be interpreted as multiples of 1 minute in this version of the protocol. + +### 11.3.45 Feature Bitmap + +The Feature bitmap information element indicates the optional features supported by the underlying NSE. The element coding is: + +**Table 11.3.45.a: Feature Bitmap IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|-----------------------|--------|-----|-----|-----|-----|-----| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | MBMS | Enhanced Radio Status | PFC-FC | RIM | LCS | INR | CBL | PFC | + +**Table 11.3.45.b: "PFC bit" coding** + +| coding | Semantic | +|--------|----------------------------------------------| +| 0 | Packet Flow Context Procedures not supported | +| 1 | Packet Flow Context Procedures supported | + +**Table 11.3.45.c: "CBL bit" coding** + +| coding | Semantic | +|--------|-----------------------------------------------| +| 0 | Current Bucket Level Procedures not supported | +| 1 | Current Bucket Level Procedures supported | + +**Table 11.3.45.d: "INR bit" coding** + +| coding | Semantic | +|--------|------------------------------------| +| 0 | Inter-NSE re-routing not supported | +| 1 | Inter-NSE re-routing supported | + +**Table 11.3.45.e: "LCS bit" coding** + +| coding | Semantic | +|--------|------------------------------| +| 0 | LCS Procedures not supported | +| 1 | LCS Procedures supported | + +**Table 11.3.45.f: "RIM bit" coding** + +| coding | Semantic | +|--------|-----------------------------------------------------------| +| 0 | RAN Information Management (RIM) procedures not supported | +| 1 | RAN Information Management (RIM) procedures supported | + +**Table 11.3.45.g: "PFC-FC" coding** + +| coding | Semantic | +|---------------|-------------------------------------------| +| 0 | PFC Flow Control Procedures not supported | +| 1 | PFC Flow Control Procedures supported | + +**Table 11.3.45.h: "Enhanced Radio Status" coding** + +| coding | Semantic | +|---------------|------------------------------------------------| +| 0 | Enhanced Radio Status Procedures not supported | +| 1 | Enhanced Radio Status Procedures supported | + +**Table 11.3.45.i: "MBMS" coding** + +| coding | Semantic | +|---------------|-------------------------------| +| 0 | MBMS Procedures not supported | +| 1 | MBMS Procedures supported | + +## 11.3.46 Bucket Full Ratio + +This information element is used to convey the current bucket counter. It is binary encoded as follows: $B_{\text{current}} \times (100 / B_{\text{max}})$ . The element coding is: + +**Table 11.3.46: Bucket Full Ratio IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-------------------------------------------------|----------|----------|----------|----------|----------|----------|----------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Ratio of the bucket that is filled up with data | | | | | | | | + +The field ranges from zero (00000000) to two hundred and fifty five (11111111). A value of zero means that the bucket is empty. A value of hundred means that the bucket is exactly full, while a value of two hundred and fifty five means that the bucket is at least 2.55 times $B_{\text{max}}$ + +## 11.3.47 Service UTRAN CCO + +The Service UTRAN CCO (Cell Change Order) information element indicates whether Network initiated Cell Change Order to UTRAN or E-UTRAN or PS Handover to UTRAN or E-UTRAN should be used for the mobile station or not, and it is relevant if at least one of the procedures is used: + +**Table 11.3.47.a: Service UTRAN CCO IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|----------|----------|--------------------------------|----------|------------------------------|----------|----------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | Service E-UTRAN CCO Value part | | Service UTRAN CCO Value part | | | + +**Table 11.3.47.b: Service UTRAN CCO Value part coding** + +| coding bits
321 | Semantic | +|----------------------------|-----------------| +|----------------------------|-----------------| + +| | | +|--------------|--------------------------------------------------------------------------------------------------------| +| 000 | Network initiated cell change order to UTRAN or PS handover to UTRAN procedure should be performed | +| 001 | Network initiated cell change order to UTRAN or PS handover to UTRAN procedure should not be performed | +| 010 | Network initiated cell change order to UTRAN or PS handover to UTRAN procedure shall not be performed | +| 111 | If received, shall be interpreted as no information available (bits 4-5 valid) | +| Other values | If received, shall be interpreted as no information available | + +**Table 11.3.47.c: Service E-UTRAN CCO Value part coding** + +| coding bits
54 | Semantic | +|-------------------|------------------------------------------------------------------------------------------------------------| +| 01 | Network initiated cell change order to E-UTRAN or PS handover to E-UTRAN procedure should be performed | +| 10 | Network initiated cell change order to E-UTRAN or PS handover to E-UTRAN procedure should not be performed | +| 11 | Network initiated cell change order to E-UTRAN or PS handover to E-UTRAN procedure shall not be performed | +| 00 | If received, shall be interpreted as no information available | + +### 11.3.48 NSEI (Network Service Entity Identifier) + +The NSEI unambiguously identifies a NSE. The element coding is: + +**Table 11.3.48: NSEI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | most significant octet of NSEI | | | | | | | | +| octet 4 | least significant octet of NSEI | | | | | | | | + +### 11.3.49 RRLP APDU + +This information element conveys an embedded message associated with a higher level protocol. The element coding is: + +**Table 11.3.49: RRLP APDU IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-? | The rest of the information element contains an embedded RRLP message whose content and encoding are defined according to the 3GPP TS 44.031. The RRLP protocol is not octet aligned. Therefore, the unused bits in the last octet are padded with zeroes. | | | | | | | | + +### 11.3.50 LCS QoS + +This information element provides the LCS QoS. The element coding is: + +**Table 11.3.50: LCS QOS IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 octet length indicator | | | | | | | | + +### 11.3.51 LCS Client Type + +This information element provides the LCS Client Type. The element coding is: + +**Table 11.3.51: LCS Client Type IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.52 Requested GPS Assistance Data + +This information element provides the information on which GPS Assistance Data has been requested. The element coding is: + +**Table 11.3.52: Requested GPS Assistance Data IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.53 Location Type + +This information element provides the Location Type. The element coding is: + +**Table 11.3.53: Location Type IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.54 Location Estimate + +This information element provides the Location Estimate. The element coding is: + +**Table 11.3.54: Location Estimate IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 octet length indicator | | | | | | | | + +### 11.3.55 Positioning Data + +This information element provides Positioning Data. The element coding is: + +**Table 11.3.55: Positioning Data IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--|---|---|---|---|---|---|---|---| +|--|---|---|---|---|---|---|---|---| + +| | | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| octet 1 | IEI | +| octet 2, 2a | Length Indicator | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | + +### 11.3.56 Deciphering Keys + +This information element provides the Deciphering Keys. The element coding is: + +**Table 11.3.56: Deciphering Keys IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.57 LCS Priority + +This information element provides the data/information on LCS Priority. The element coding is: + +**Table 11.3.57: LCS Priority IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.58 LCS Cause + +This information element provides the data/information on LCS Cause. The element coding is: + +**Table 11.3.58: LCS Cause IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.59 LCS Capability + +This information element provides the data/information on LCS Capability. The element coding is: + +**Table 11.3.59: LCS Capability IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Rest of element coded as the value part of the PS LCS Capability IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and length indicator | | | | | | | | + +### 11.3.60 RRLP Flags + +This information element provides control information for the RRLP APDU. The element coding is: + +**Table 11.3.60: RRLP Flags IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|--------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | | | | Flag 1 | + +The fields are coded as follows: + +Flag 1 (Octet 3, bit 1): + +- 0 Position Command (BSS to SGSN) or final response (SGSN to BSS); +- 1 Not a Positioning Command or final response. + +Spare These bits shall be ignored by the receiver and set to zero by the sender. + +### 11.3.61 RIM Application Identity + +This information element specifies the addressed application within the target BSS node. The element coding is: + +**Table 11.3.61.a: RIM Application Identity IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | RIM Application Identity | | | | | | | | + +RIM Application Identity is coded as shown below. + +**Table 11.3.61.b: RIM Application Identity coding** + +| Coding | Semantic | +|-----------------------|-------------------------------------| +| 0000 0000 | Reserved | +| 0000 0001 | Network Assisted Cell Change (NACC) | +| 0000 0010 | System Information 3 (SI3) | +| 0000 0011 | MBMS data channel | +| 0000 0100 | SON Transfer | +| 0000 0101 | UTRA System Information (UTRA SI) | +| 0000 0110 | Multilateration Timing Advance | +| 0000 0111 - 1111 1111 | Reserved | + +All values not allocated are reserved. + +### 11.3.62 RIM Sequence Number + +This information element defines the sequence number allocated to the PDU by the source node. The element coding is: + +**Table 11.3.62: RIM Sequence Number IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | RIM Sequence Number (Higher order octet) | | | | | | | | +| Octet 4 | RIM Sequence Number | | | | | | | | +| Octet 5 | RIM Sequence Number | | | | | | | | +| Octet 6 | RIM Sequence Number (Lower order octet) | | | | | | | | + +## 11.3.62a RIM Container + +### 11.3.62a.0 General + +The coding of the *RIM Container* IE value part depends on the value of the PDU type according to the following sub-clauses: + +### 11.3.62a.1 RAN-INFORMATION-REQUEST RIM Container + +This information element defines the RIM container used in the RAN-INFORMATION-REQUEST PDU. The element coding is: + +**Table 11.3.62a.1.a: RAN-INFORMATION-REQUEST RIM Container IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-? | RAN-INFORMATION-REQUEST RIM Container Contents coded as defined in table 11.3.62a.1b | | | | | | | | + +**Table 11.3.62a.1.b: RAN-INFORMATION-REQUEST RIM Container Contents** + +| Information Elements | Type / Reference | Presence | Format | Length | +|--------------------------------------------|---------------------------------------------------------|----------|--------|--------| +| RIM Application Identity | RIM Application Identity/11.3.61 | M | TLV | 3 | +| RIM Sequence Number | RIM Sequence Number/11.3.62 | M | TLV | 6 | +| RIM PDU Indications | RIM PDU Indications/11.3.65 | M | TLV | 3 | +| RIM Protocol Version Number | RIM Protocol Version Number/11.3.67 | O | TLV | 3 | +| Application Container (note 1) | RAN-INFORMATION-REQUEST Application Container/11.3.63.1 | C | TLV | 4-? | +| SON Transfer Application Identity (note 2) | SON Transfer Application Identity/11.3.108 | C | TLV | 3-m | + +NOTE 1: The presence of the Application Container depends on the value of the *RIM Application Identity* IE. + +NOTE 2: The *SON Transfer Application Identity* IE shall be present if and only if the *RIM Application Identity* IE is set to "SON Transfer". + +### 11.3.62a.2 RAN-INFORMATION RIM Container + +This information element defines the RIM container used in the RAN-INFORMATION PDU. The element coding is: + +**Table 11.3.62a.2.a: RAN-INFORMATION RIM Container IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-? | RAN-INFORMATION RIM Container Contents coded as defined in table 11.3.62a.2b | | | | | | | | + +**Table 11.3.62a.2.b: RAN-INFORMATION RIM Container Contents** + +| Information Elements | Type / Reference | Presence | Format | Length | +|--------------------------------------------|--------------------------------------------------|------------|--------|--------| +| RIM Application Identity | RIM Application Identity /11.3.61 | M | TLV | 3 | +| RIM Sequence Number | RIM Sequence Number /11.3.62 | M | TLV | 6 | +| RIM PDU Indications | RIM PDU Indications /11.3.65. | M | TLV | 3 | +| RIM Protocol Version Number | RIM Protocol Version Number/11.3.67 | O | TLV | 3 | +| Application Container (NOTE 1) | RAN-INFORMATION Application Container /11.3.63.2 | C (Note 1) | TLV | 4-? | +| Application Error Container (NOTE 1) | Application Error Container/11.3.64 | C (Note 1) | TLV | n | +| SON Transfer Application Identity (note 2) | SON Transfer Application Identity/11.3.108 | C | TLV | 3-m | + +NOTE 1: The presence of application information depends on the value of the *RIM Application Identity* IE. If application information is mandatory either the *Application Error Container* IE or the *Application Container* IE is present. + +NOTE 2: The *SON Transfer Application Identity* IE shall be present if and only if the *RIM Application Identity* IE is set to "SON Transfer". + +### 11.3.62a.3 RAN-INFORMATION-ACK RIM Container + +This information element defines the RIM container used in the RAN-INFORMATION-ACK PDU. The element coding is: + +**Table 11.3.62a.3.a: RAN-INFORMATION-ACK RIM Container IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-16 | RAN-INFORMATION-ACK RIM Container Contents coded as defined in table 11.3.62a.3b | | | | | | | | + +**Table 11.3.62a.3.b: RAN-INFORMATION-ACK RIM Container Contents** + +| Information Elements | Type / Reference | Presence | Format | Length | +|--------------------------------------------|--------------------------------------------|----------|--------|--------| +| RIM Application Identity | RIM Application Identity /11.3.61 | M | TLV | 3 | +| RIM Sequence Number | RIM Sequence Number /11.3.62 | M | TLV | 6 | +| RIM Protocol Version Number | RIM Protocol Version Number/11.3.67 | O | TLV | 4 | +| SON Transfer Application Identity (note 1) | SON Transfer Application Identity/11.3.108 | C | TLV | 3-m | + +NOTE 1: The *SON Transfer Application Identity* IE shall be present if and only if the *RIM Application Identity* IE is set to "SON Transfer". + +### 11.3.62a.4 RAN-INFORMATION-ERROR RIM Container + +This information element defines the RIM container used in the RAN-INFORMATION-ERROR PDU. The element coding is: + +**Table 11.3.62a.4.a: RAN-INFORMATION-ERROR RIM Container IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-? | RAN-INFORMATION-ERROR RIM Container Contents coded as defined in table 11.3.62a.4b | | | | | | | | + +**Table 11.3.62a.4.b: RAN-INFORMATION-ERROR RIM Container Contents** + +| Information Elements | Type / Reference | Presence | Format | Length | +|--------------------------------------------|--------------------------------------------|----------|--------|--------| +| RIM Application Identity | RIM Application Identity /11.3.61 | M | TLV | 3 | +| RIM Cause | Cause/11.3.8 | M | TLV | 3 | +| RIM Protocol Version Number | RIM Protocol Version Number/11.3.67 | O | TLV | 3 | +| PDU in Error | PDU in Error/11.3.24 | M | TLV | 3-? | +| SON Transfer Application Identity (note 1) | SON Transfer Application Identity/11.3.108 | C | TLV | 3-m | + +NOTE 1: The *SON Transfer Application Identity* IE shall be present if and only if the *RIM Application Identity* IE is set to "SON Transfer". + +## 11.3.62a.5 RAN-INFORMATION-APPLICATION-ERROR RIM Container + +This information element defines the RIM container used in the RAN-INFORMATION-APPLICATION-ERROR PDU. The element coding is: + +**Table 11.3.62a.5.a: RAN-INFORMATION-APPLICATION-ERROR RIM Container IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-? | RAN-INFORMATION-APPLICATION-ERROR RIM Container Contents coded as defined in table 11.3.62a.5b | | | | | | | | + +**Table 11.3.62a.5.b: RAN-INFORMATION-APPLICATION-ERROR RIM Container Contents** + +| Information Elements | Type / Reference | Presence | Format | Length | +|--------------------------------------------|--------------------------------------------|----------|--------|--------| +| RIM Application Identity | RIM Application Identity /11.3.61 | M | TLV | 3 | +| RIM Sequence Number | RIM Sequence Number /11.3.62 | M | TLV | 6 | +| RIM PDU Indications | RIM PDU Indications /11.3.65 | M | TLV | 3 | +| RIM Protocol Version Number | RIM Protocol Version Number/11.3.67 | O | TLV | 3 | +| Application Error Container | Application Error Container/11.3.64 | M | TLV | n | +| SON Transfer Application Identity (note 1) | SON Transfer Application Identity/11.3.108 | C | TLV | 3-m | + +NOTE 1: The *SON Transfer Application Identity* IE shall be present if and only if the *RIM Application Identity* IE is set to "SON Transfer". + +## 11.3.63 Application Container + +### 11.3.63.1 RAN-INFORMATION-REQUEST Application Container + +#### 11.3.63.1.0 General + +The coding of the *Application Container* value part within the RAN-INFORMATION-REQUEST RIM container depends on the value of the *RIM Application Identity* IE included into the RIM container according to the following sub-clauses. + +#### 11.3.63.1.1 RAN-INFORMATION-REQUEST Application Container for the NACC Application + +The coding of the *Application Container* IE within the RAN-INFORMATION-REQUEST RIM container for the NACC application is specified as follows: + +**Table 11.3.63.1.1: RAN-INFORMATION-REQUEST Application Container coding for NACC** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-10 | Reporting Cell Identifier | | | | | | | | + +**Reporting Cell Identifier:** This field is encoded as the Cell Identifier defined in sub-clause 11.3.9 + +#### 11.3.63.1.2 RAN-INFORMATION-REQUEST Application Container for the SI3 Application + +The coding of the *Application Container* IE within the RAN-INFORMATION-REQUEST RIM container for the SI3 application is specified as follows: + +**Table 11.3.63.1.2: RAN-INFORMATION-REQUEST Application Container coding for SI3** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-10 | Reporting Cell Identifier | | | | | | | | + +**Reporting Cell Identifier:** This field is encoded as the Cell Identifier defined in sub-clause 11.3.9 + +#### 11.3.63.1.3 RAN-INFORMATION-REQUEST Application Container for the MBMS data channel Application + +The coding of the *Application Container* IE within the RAN-INFORMATION-REQUEST RIM container for the MBMS data channel application is specified as follows: + +**Table 11.3.63.1.3: RAN-INFORMATION-REQUEST Application Container coding for MBMS data channel** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-10 | Reporting Cell Identifier | | | | | | | | + +**Reporting Cell Identifier:** This field is encoded as the Cell Identifier defined in sub-clause 11.3.9 + +#### 11.3.63.1.4 RAN-INFORMATION-REQUEST Application Container for the SON Transfer Application + +The coding of the *Application Container* IE within the RAN-INFORMATION-REQUEST RIM container for the SON Application is specified as follows: + +**Table 11.3.63.1.4: RAN-INFORMATION-REQUEST Application Container coding for SON Transfer** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------|--------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-m | Reporting Cell Identifier | | | | | | | | +| Octet (m+1)-n | SON Transfer Request Container | | | | | | | | + +**Reporting Cell Identifier:** + +- If the request concerns an E-UTRAN cell, this field is encoded as the *E-UTRAN CGI* IE as defined in 3GPP TS 36.413 [36]. +- If the request concerns a UTRAN cell, this field is encoded as the *Source Cell Identifier* IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38]. +- If the request concerns a GERAN cell, this field is encoded as the *Cell Identifier* IE defined in sub-clause 11.3.9. +- If the request concerns an eHRPD eAN cell, this field is encoded as the *eHRPD Sector ID* IE as specified in 3GPP2 C.S0024-B [47]. + +**SON Transfer Request Container:** This field is encoded as the *SON Transfer Request Container* IE as defined in 3GPP TS 36.413 [36]. + +### 11.3.63.1.5 RAN-INFORMATION-REQUEST Application Container for the UTRA SI Application + +The coding of the *Application Container* IE within the RAN-INFORMATION-REQUEST RIM container for the UTRA SI application is specified as follows: + +**Table 11.3.63.1.5: RAN-INFORMATION-REQUEST Application Container coding for UTRA SI** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-m | Reporting Cell Identifier | | | | | | | | + +**Reporting Cell Identifier:** This field is encoded as the *Source Cell Identifier* IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38]. + +### 11.3.63.2 RAN-INFORMATION Application Container Unit + +#### 11.3.63.2.0 General + +The coding of the *Application Container* value part within the RAN-INFORMATION RIM container depends on the value of the *RIM Application Identity* IE included into the RIM container according to the following sub-clauses. + +#### 11.3.63.2.1 RAN-INFORMATION Application Container for the NACC Application + +The coding of the *Application Container* IE within the RAN-INFORMATION RIM container for the NACC application is specified as follows: + +**Table 11.3.63.2.1.a: RAN-INFORMATION Application Container coding for NACC** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------|---|---|---|---|---|---|------| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-10 | Reporting Cell Identifier | | | | | | | | +| Octet 11 | Number of SI/PSI | | | | | | | Type | +| Octet 12-n | SI/PSI | | | | | | | | + +**Reporting Cell Identifier:** This field is encoded as the value part of the Cell Identifier IE defined in sub-clause 11.3.9, not including IEI and Length Indicator. + +**Type:** This field indicates the type of SI/PSI messages provided by the reporting cell. The *Type* field is coded as shown below: + +**Table 11.3.63.2.1.b: Type coding** + +| Coding | Semantic | +|--------|-------------------------------------------------------------| +| 0 | SI messages as specified for BCCH (3GPP TS 44.018) follow | +| 1 | PSI messages as specified for PBCCH (3GPP TS 44.060) follow | + +**Number of SI/PSI:** This field indicates the number of SI/PSI provided by the reporting cell contained in the *SI/PSI field*. This number may be zero. For system information messages with multiple instances, each instance is counted as one SI/PSI message. The *Number of SI/PSI* field is coded as shown below: + +**Table 11.3.63.2.1.c: Number of SI/PSI coding** + +| Coding | Semantic | +|----------|---------------------| +| 000 0000 | 0 "SI/PSI" follows | +| 000 0001 | 1 "SI/PSI" follow | +| , | " | +| 111 1111 | 127 "SI/PSI" follow | + +**SI/PSI:** This field contains a list of either system information or packet system information messages valid for the reporting cell. The number of (packet) system information messages is indicated in the *Number of SI/PSI* field specified above. Furthermore: + +- If the *Type* field indicates that "SI messages as specified for BCCH (3GPP TS 44.018) follow" then the *SI/PSI* field contains System Information message instances encoded for BCCH as specified in 3GPP TS 44.018. Each System Information message contains the *Message type* octet followed by all the IEs composing the message payload. Each message is 21 octets long. +- If the *Type* field indicates that "PSI messages as specified for PBCCH (3GPP TS 44.060) follow" then the *SI/PSI* field contains Packet System Information message instances encoded for PBCCH as specified in 3GPP TS 44.060. Each Packet System Information message contains the *MESSAGE\_TYPE* field followed by the PSI message content. Each message is 22 octets long. + +#### 11.3.63.2.2 RAN-INFORMATION Application Container for the SI3 Application + +The coding of the value part of the *Application Container* IE within the RAN-INFORMATION RIM container for the SI3 application is specified as follows: + +**Table 11.3.63.2.2: RAN-INFORMATION Application Container coding for SI3** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-10 | Reporting Cell Identifier | | | | | | | | +| Octet 11-31 | SI3 | | | | | | | | + +**Reporting Cell Identifier:** The parameter is encoded as the value part of the Cell Identifier IE defined in sub-clause 11.3.9, not including IEI and Length Indicator. + +**SI3:** contains the SYSTEM INFORMATION type 3 message encoded for BCCH as specified in 3GPP TS 44.018. It contains the *Message type* octet followed by all the IEs composing the message payload. The message is 21 octets long. + +#### 11.3.63.2.3 RAN-INFORMATION Application Container for the MBMS data channel Application + +The coding of the *Application Container* IE within the RAN-INFORMATION RIM container for the MBMS data channel application is specified as follows : + +**Table 11.3.63.2.3.a: RAN-INFORMATION Application Container coding for MBMS data channel** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-10 | Reporting Cell Identifier | | | | | | | | +| Octet 11-n | MBMS data channel report | | | | | | | | + +**Reporting Cell Identifier:** This field is encoded as the value part of the Cell Identifier IE defined in sub-clause 11.3.9, not including IEI and Length Indicator. + +**MBMS data channel report:** This field contains a CSN1 encoded structure coded as shown below: + +**Table 11.3.63.1.3.b: MBMS data channel report** + +``` + +< MBMS data channel report struct > ::= +{ 1 < MBMS Frequency List : < MBMS Frequency List struct > > } **0 + +{1 + < MBMS p-t-m Frequency Parameters : < MBMS p-t-m Frequency Parameters struct > > + < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > --default value common to all described bearer Id using this +frequency allocation + { 1 + < TMGI : < TMGI IE > > -- MBMS service identifier + { 0 | 1 < MBMS Session Identity : bit(8) > } -- session identifier of the particular MBMS service + < Length of MBMS Bearer Identity : bit (3) > + < MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) > + { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE >> } + { 0 | 1 < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > } -- dedicated value for this bearer, overwrites the +default value + { 0 | 1 < TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL : bit (3) > } + { 0 | 1 < MBMS Radio Bearer Starting Time : < bit (16) > > } + < MBMS In-band Signalling Indicator : < MBMS In-band Signalling Indicator IE >> + { 0 | 1 < NPM Transfer Time : bit (5) > } + } ** 0 -- End of list of MBMS bearer identifiers sharing the same PDCH (frequency parameters) +} ** 0 -- End of list of PDCHs for this cell +{ null | 0 bit** = < no string > +| 1 -- Rel-7 Additions +{ 1 + { 0 | 1 < USF : bit (3) > --choice bit indicates presence or not of parameters for the MBMS bearer + { 0 | 1 < MPRACH Control Parameters : < MPRACH Control Parameters IE > > } +} +} ** 0 -- End of list of MBMS bearers. The list of MBMS bearers is ordered as described by the loops +in the earlier releases part. +} +< padding bits > -- to fill the last octet + +``` + +**MBMS Frequency List:** This field contains a *MBMS Frequency List struct* as specified in 3GPP TS 44.060 + +**MBMS p-t-m Frequency Parameters:** This field contains a *MBMS p-t-m Frequency Parameters struct* as specified in 3GPP TS 44.060 + +**DOWNLINK\_TIMESLOT\_ALLOCATION:** This field contains a *DOWNLINK\_TIMESLOT\_ALLOCATION* field as specified in 3GPP TS 44.060 + +**TMGI:** This field contains a *TMGI* IE as specified in 3GPP TS 44.060 + +**MBMS Session Identity:** This field contains a *MBMS Session Identity* field as specified in 3GPP TS 44.060 + +**MBMS Bearer Identity:** This field contains a *MBMS Bearer Identity* IE as specified in 3GPP TS 44.060 + +**EGPRS Window Size:** This field contains a *EGPRS Window Size* IE as specified in 3GPP TS 44.060 + +**TIMESLOT\_ALLOCATION\_UPLINK\_FEEDBACK\_CHANNEL:** This field contains a *TIMESLOT\_ALLOCATION\_UPLINK\_FEEDBACK\_CHANNEL* field as specified in 3GPP TS 44.060 + +**MBMS Radio Bearer Starting Time:** This field is encoded as value part of the type 3 information element *Starting Time* in 3GPP TS 44.018. + +**MBMS In-band Signalling Indicator:** This field contains a *MBMS In-band Signalling Indicator* IE as specified in 3GPP TS 44.060. **NPM Transfer Time:** This field contains a *NPM Transfer Time* IE as specified in 3GPP TS 44.060. **USF:** This field contains a *USF* field as specified in 3GPP TS 44.060 + +**MPRACH Control Parameters:** This field contains a *MPRACH Control Parameters* IE as specified in 3GPP TS 44.060. + +### 11.3.63.2.4 RAN-INFORMATION Application Container for the SON Transfer Application + +The coding of the *Application Container* IE within the RAN-INFORMATION RIM container for the SON Transfer Application is specified as follows : + +**Table 11.3.63.2.4: RAN-INFORMATION Application Container coding for SON Transfer** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|---------------|---------------------------------|---|---|---|-------------------|---|---|---|--|--|--|--| +| Octet 1 | IEI | | | | | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | | | | | +| Octet 3 | Spare | | | | RAT discriminator | | | | | | | | +| Octet 4-m | Reporting Cell Identifier | | | | | | | | | | | | +| Octet (m+1)-n | SON Transfer Response Container | | | | | | | | | | | | + +The coding of *RAT discriminator* (bits 4 to 1 of octet 3) is a binary number indicating the RAT of the Reporting Cell Identifier. The *RAT discriminator* is coded as follows: + +| | | +|-------------|--------------------------------| +| Bits | | +| 4321 | | +| 0000 | The reporting RAT is GERAN. | +| 0001 | The reporting RAT is UTRAN. | +| 0010 | The reporting RAT is E-UTRAN. | +| 0011 | The reporting RAT is eHRPD eAN | + +All other values are reserved. + +#### Reporting Cell Identifier: + +- If the *RAT discriminator* field indicates E-UTRAN, this field is encoded as the *E-UTRAN CGI* IE as defined in 3GPP TS 36.413 [36]. +- If the *RAT discriminator* field indicates UTRAN, this field is encoded as the *Source Cell Identifier* IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38]. +- If the *RAT discriminator* field indicates GERAN, this field is encoded as the value part of the *Cell Identifier* IE defined in sub-clause 11.3.9, not including IEI and Length Indicator. +- If the *RAT discriminator* field indicates eHRPD, this field is encoded as *eHRPD Sector ID* IE as defined in 3GPP2 C.S0024-B [47]. + +**SON Transfer Response Container:** This field is encoded as the *SON Transfer Response Container* IE as defined in 3GPP TS 36.413 [36]. + +### 11.3.63.2.5 RAN-INFORMATION Application Container for the UTRA SI Application + +The coding of the *Application Container* IE within the RAN-INFORMATION RIM container for the UTRA SI application is specified as follows: + +**Table 11.3.63.2.5: RAN-INFORMATION Application Container coding for UTRA SI** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------|---------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-m | Reporting Cell Identifier | | | | | | | | +| Octet (m+1)-n | UTRA SI Container | | | | | | | | + +**Reporting Cell Identifier:** This field is encoded as the *Source Cell Identifier* IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38]. + +**UTRA SI Container:** This field contains System Information Container valid for the reporting cell encoded as defined in TS 25.331 [42]. + +### 11.3.63.2.6 RAN-INFORMATION Application Container for the Multilateration Timing Advance Application + +The coding of the *Application Container* IE within the RAN-INFORMATION RIM container for the Multilateration Timing Advance application is specified as follows: + +**Table 11.3.63.2.6: RAN-INFORMATION Application Container coding for Multilateration Timing Advance** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------|-------|---|---|-----------------------------------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-6 | TLLI | | | | | | | | +| Octet 7 | MS Sync Accuracy | | | | MTA High | | | | +| Octet 8 | MTA Low | | | | BTS Reception Accuracy Level High | | | | +| Octet 9 | BTS Reception Accuracy Level Low | Spare | | | | | | | + +**TLLI:** This field is encoded as the value part of the TLLI information element in 3GPP TS 44.018, not including 3GPP TS 44.018 IEI. + +**Multilateration Timing Advance (MTA):** The MTA field is coded according to the value part of the Multilateration Timing Advance information element described in 3GPP TS 49.031 (i.e. not including 3GPP TS 49.031 IEI). + +**MS Sync Accuracy:** The MS Sync Accuracy field is coded according to the value part of the MS Sync Accuracy information element described in 3GPP TS 49.031 (i.e. not including 3GPP TS 49.031 IEI). + +**BTS Reception Accuracy Level:** The BTS Reception Accuracy Level field is coded according to the value part of the BTS Reception Accuracy Level information element described in 3GPP TS 49.031 (i.e. not including 3GPP TS 49.031 IEI). + +## 11.3.64 Application Error Container + +### 11.3.64.1 Application Error Container layout for the NACC application + +The coding of the *Application Error Container* IE for the NACC application is specified as follows: + +**Table 11.3.64.1.a: Application Error Container coding for NACC** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | NACC Cause | | | | | | | | +| Octet 4-n | Erroneous Application Container including IEI and LI | | | | | | | | + +**NACC Cause:** This field indicates the cause why the *Application Error Container* IE is sent. The *NACC Cause* field is coded as shown below: + +**Table 11.3.64.1.b: NACC Cause coding** + +| Coding | Semantic | +|--------------|-------------------------------------------------------------------------------------------------------------------| +| 0000 0000 | Other unspecified error | +| 0000 0001 | Syntax error in the Application Container | +| 0000 0010 | Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier. | +| 0000 0011 | SI/PSI type error | +| 0000 0100 | Inconsistent length of a SI/PSI message | +| 0000 0101 | Inconsistent set of messages | +| Other values | reserved | + +**"Other unspecified error"**: none of the error description below fits with the detected error + +**"Syntax error in the Application Container"**: the *Application Container* IE is syntactically incorrect + +**"Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier"**: the *Reporting Cell Identifier* in the *Application Container* IE does not match with the *Destination Cell Identifier* IE value (in the case of a RAN-INFORMATION-REQUEST PDU) or with the *Source Cell Identifier* IE value (in the case of a RAN-INFORMATION PDU) of the RIM PDU + +**"SI/PSI type error"**: the *Application Container* IE contains system information messages instead of packet system information messages or conversely + +**"Inconsistent length of a SI/PSI message"**: the length contained in one SI/PSI message does not fit with the content of the message + +**"Inconsistent set of messages"**: the status of the change marks reported in the (packet) system information message set is inconsistent + +**Erroneous Application Container**: this field contains the erroneous *Application Container* IE + +## 11.3.64.2 Application Error Container for the SI3 application + +The coding of the *Application Error Container* IE for the SI3 application is specified as follows: + +**Table 11.3.64.2.a: Application Error Container coding for SI3** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | SI3 Cause | | | | | | | | +| Octet 4-n | Erroneous Application Container including IEI and LI | | | | | | | | + +**SI3 Cause**: This field indicates the cause why the *Application Error Container* IE is sent. The *SI3 Cause* field is coded as shown below: + +**Table 11.3.64.2.b: SI3 Cause coding** + +| Coding | Semantic | +|--------------|-------------------------------------------------------------------------------------------------------------------| +| 0000 0000 | Other unspecified error | +| 0000 0001 | Syntax error in the Application Container | +| 0000 0010 | Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier. | +| 0000 0011 | Inconsistent length of a SI3 message | +| Other values | Reserved | + +**"Other unspecified error"**: None of the error description below fits with the detected error; + +**"Syntax error in the Application Container"**: the Error Application Container is syntactically incorrect; + +**"Reporting Cell Id does not match with the Destination Cell Identifier or with the Source Cell Identifier":** the *Reporting Cell Identifier* in the *Application Container* IE does not match with the *Destination Cell Identifier* IE value (in the case of a RAN-INFORMATION-REQUEST PDU) or with the *Source Cell Identifier* IE value (in the case of a RAN-INFORMATION PDU) of the RIM PDU; + +**"Inconsistent length of a SI3 message":** the length contained in the SI3 message does not fit with the content of the message; + +**Erroneous Application Container:** This field contains the erroneous *Application Container* IE. + +### 11.3.64.3 Application Error Container for the MBMS data channel application + +The coding of the *Application Error Container* IE for the MBMS data channel application is specified as follows: + +**Table 11.3.64.3.a: Application Error Container coding for MBMS data channel** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | MBMS data channel Cause | | | | | | | | +| Octet 4-n | Erroneous Application Container including IEI and LI | | | | | | | | + +**MBMS data channel Cause:** This field indicates the cause why the *Application Error Container* IE is sent. The *MBMS data channel Cause* field is coded as shown below: + +**Table 11.3.64.3.b: MBMS DATA CHANNEL Cause coding** + +| Coding | Semantic | +|--------------|-------------------------------------------------------------------------------------------------------------------| +| 0000 0000 | Other unspecified error | +| 0000 0001 | Syntax error in the Application Container | +| 0000 0010 | Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier. | +| 0000 0011 | RAN-INFORMATION/Initial Multiple Report or RAN-INFORMATION/Single Report PDU exceeds the maximum supported length | +| 0000 0100 | Inconsistent MBMS data channel description | +| Other values | reserved | + +**"Other unspecified error":** None of the error description below fits with the detected error. + +**"Syntax error in the Application Container":** the *Application Container* IE is syntactically incorrect. + +**"Reporting Cell Id does not match with the Destination Cell Identifier or Source Cell Identifier respectively":** the *Reporting Cell Identifier* in the *Application Container* IE does not match with the *Destination Cell Identifier* IE value (in the case of a RAN-INFORMATION-REQUEST PDU) or with the *Source Cell Identifier* IE value (in the case of a RAN-INFORMATION PDU) of the RIM header. + +**"RAN-INFORMATION/Initial Multiple Report or RAN-INFORMATION/Single Report PDU exceeds the maximum supported length":** the RAN-INFORMATION/Initial Multiple Report PDU exceeds the maximum length supported by the system. + +**"Inconsistent MBMS data channel description":** failure in a MBMS data channel description. + +**Erroneous Application Container:** This field contains the erroneous *Application Container* IE . + +### 11.3.64.4 Application Error Container for the SON Transfer Application + +The coding of the *Application Error Container* IE for the SON Transfer Application is specified as follows: + +**Table 11.3.64.4: Application Error Container coding for SON Transfer** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------|------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-m | SON Transfer Cause | | | | | | | | +| Octet (m+1)-n | Erroneous Application Container including IEI and LI | | | | | | | | + +**SON Transfer Cause:** This field indicates the cause why the *Application Error Container* IE is sent. The "*SON Transfer Cause*" field is encoded as the *SON Transfer Cause* IE as defined in 3GPP TS 36.413 [36]. + +### 11.3.64.5 Application Error Container for the UTRA SI Application + +The coding of the *Application Error Container* IE for the UTRA SI Application is specified as follows: + +**Table 11.3.64.5.a: Application Error Container coding for UTRA SI** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | UTRA SI Cause | | | | | | | | +| Octet 4-n | Erroneous Application Container including IEI and LI | | | | | | | | + +**UTRA SI Cause:** This field indicates the cause why the *Application Error Container* IE is sent. The *UTRA SI Cause* field is coded as shown below: + +**Table 11.3.64.5.b: UTRA SI Cause coding** + +| Coding | Semantic | +|--------------|-------------------------------------------| +| 0000 0000 | Unspecified | +| 0000 0001 | Syntax Error in the Application Container | +| 0000 0010 | Inconsistent Reporting Cell Identifier | +| Other values | Reserved | + +**"Unspecified":** Sent when none of the above cause values applies. + +**"Syntax Error in the Application Container":** The *Application Container* IE is syntactically incorrect. + +**"Inconsistent Reporting Cell Identifier":** The cell identified by *Reporting Cell Identifier* in the *Application Container* IE is unknown in the RNC identified by the *Destination Cell Identifier* IE value in the RAN-INFORMATION-REQUEST PDU. + +**Erroneous Application Container:** This field contains the erroneous *Application Container* IE. + +### 11.3.64.6 Application Error Container for the Multilateration Timing Advance Application + +The coding of the *Application Error Container* IE for the Multilateration Timing Advance Application is specified as follows: + +**Table 11.3.64.5.a: Application Error Container coding for Multilateration Timing Advance** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Multilateration Timing Advance Cause | | | | | | | | +| Octet 4-n | Erroneous Application Container including IEI and LI | | | | | | | | + +**Multilateration Timing Advance Cause:** This field indicates the cause why the *Application Error Container* IE is sent. The *Multilateration Timing Advance Cause* field is coded as shown below: + +**Table 11.3.64.5.b: Multilateration Timing Advance Cause coding** + +| Coding | Semantic | +|--------------|-------------------------------------------| +| 0000 0000 | Unspecified error | +| 0000 0001 | Syntax Error in the Application Container | +| Other values | Reserved | + +**"Unspecified":** Sent when none of the above cause values applies. + +**"Syntax Error in the Application Container":** The *Application Container* IE is syntactically incorrect. + +**Erroneous Application Container:** This field contains the erroneous *Application Container* IE. + +## 11.3.65 RIM PDU Indications + +### 11.3.65.0 General + +This information element contains various indications related to a RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU or RAN-INFORMATION-APPLICATION-ERROR PDU. + +The element coding is: + +**Table 11.3.65.a: RIM PDU Indications IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|--------------------|---|---|-----| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Reserved | | | | PDU Type Extension | | | ACK | + +**ACK:** this field indicates whether the source side is requesting a RAN-INFORMATION-ACK PDU as response to a RAN-INFORMATION or to a RAN-INFORMATION-APPLICATION-ERROR PDU. This field is coded as shown below. + +**Table 11.3.65.b: ACK coding** + +| Coding | Semantic | +|--------|------------------| +| 0 | No ACK requested | +| 1 | ACK requested | + +**PDU Type Extension:** This field specifies the type extension of the PDU. The defined values depend on the PDU type. + +### 11.3.65.1 RAN-INFORMATION-REQUEST RIM PDU Indications + +The *ACK* field is not used and shall be considered as spare. + +The following values of the *PDU Type Extension* field are defined: + +**Table 11.3.65.1: RAN-INFORMATION-REQUEST PDU Type Extension coding** + +| Coding | Semantic | +|--------|---------------------------------------------| +| 000 | RAN-INFORMATION-REQUEST/Stop PDU | +| 001 | RAN-INFORMATION-REQUEST/Single Report PDU | +| 010 | RAN-INFORMATION-REQUEST/Multiple Report PDU | +| 011 | Reserved | +| 100 | Reserved | +| 101 | Reserved | +| 110 | Reserved | +| 111 | Reserved | + +### 11.3.65.2 RAN-INFORMATION RIM PDU Indications + +The *ACK* field is defined as specified in sub-clause 11.3.65.0. + +The following values of the *PDU Type Extension* field are defined: + +**Table 11.3.65.2: RAN-INFORMATION PDU Type Extension coding** + +| Coding | Semantic | +|--------|---------------------------------------------| +| 000 | RAN-INFORMATION/Stop PDU | +| 001 | RAN-INFORMATION/Single Report PDU | +| 010 | RAN-INFORMATION/Initial Multiple Report PDU | +| 011 | RAN-INFORMATION/Multiple Report PDU | +| 100 | RAN-INFORMATION/End PDU | +| 101 | Reserved | +| 110 | Reserved | +| 111 | Reserved | + +### 11.3.65.3 RAN-INFORMATION-APPLICATION-ERROR RIM PDU Indications + +The *ACK* field is defined as specified in sub-clause 11.3.65.0. + +The *PDU Type Extension* field is not used and shall be considered as spare. + +### 11.3.66 (void) + +### 11.3.67 RIM Protocol Version Number + +This information element defines which version number of the RIM protocol is in use in the PDU. The element coding is: + +**Table 11.3.67.a: RIM Protocol Version Number IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | RIM Protocol Version Number | | | | | | | | + +RIM Protocol Version Number is coded as follows: + +**Table 11.3.67.b: RIM Protocol Version Number IE coding** + +| Coding | Semantic | +|--------------|-----------| +| 0000 0000 | Reserved | +| 0000 0001 | Version 1 | +| Other values | Reserved | + +If this Information Element is omitted the value "Version 1" should be assumed. + +## 11.3.68 PFC Flow Control parameters + +This information element contains the flow control parameters for one or more PFC(s) of a certain MS. The element coding is: + +**Table 11.3.68.a: PFC Flow Control parameters IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Number of PFCs | | | | | | | | +| Octet 4 | PFI (1) | | | | | | | | +| Octet 5-6 | Bmax_PFC (1) | | | | | | | | +| Octet 7-8 | R_PFC (1) | | | | | | | | +| Octet 9 | B_PFC (1) | | | | | | | | +| Octet ? | PFI (2) | | | | | | | | +| Octet ?-? | Bmax_PFC (2) | | | | | | | | +| Octet ?-? | R_PFC (2) | | | | | | | | +| Octet ? | B_PFC (2) | | | | | | | | +| " | " | | | | | | | | +| Octet ? | PFI (n) | | | | | | | | +| Octet ?-? | Bmax_PFC (n) | | | | | | | | +| Octet ?-? | R_PFC (n) | | | | | | | | +| Octet ? | B_PFC (n) | | | | | | | | + +**Number of PFCs:** Number of PFCs for which flow control parameters are provided. For each of those PFCs follows its identifier and the value of the flow control parameters. The "Number of PFCs" parameter is coded as shown below: + +**Table 11.3.68.b: Number of PFCs** + +| Coding | Semantic | +|-----------|----------| +| 0000 0000 | 0 PFC | +| 0000 0001 | 1 PFC | +| ... | ... | +| 0000 1011 | 11 PFCs | +| 0000 1100 | Reserved | +| ' | " | +| 1111 1111 | Reserved | + +**PFI:** Packet Flow Identifier. Coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI. + +**Bmax\_PFC:** Bucket size of the PFC. Coded like the value part of BVC Bucket Size, see sub-clause 11.3.5. + +**R\_PFC:** Bucket Leak Rate of the PFC. Coded as the value part of Bucket Leak Rate (R), see sub-clause 11.3.4. + +**B\_PFC:** Bucket Full Ratio of the PFC. This field is only present if the Current Bucket Level (CBL) feature is negotiated. Otherwise, the flow control parameters for the next PFC, if any, are provided instead. This field if coded as the value part of the Bucket Full Ratio, see sub-clause 11.3.46. + +## 11.3.69 Global CN-Id + +The Global CN-Id consists of a PLMN-Id and a CN-Id, see 3GPP TS 23.003. The value part of the Global CN-Id is coded as defined in 3GPP TS 29.018. The CN-Id is an integer defined by O&M. The element coding is: + +**Table 11.3.69: Global CN-Id IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-7 | Coded as octets 3 to 7 of the Global CN-Id IE, defined in 3GPP TS 29.018 | | | | | | | | + +## 11.3.70 RIM Routing Information + +This information element uniquely identifies either a cell within a GERAN BSS, a UTRAN RNC, an E-UTRAN eNodeB or an eHRPD eAN. The element coding is: + +**Table 11.3.70: RIM Routing Information IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------|---------------------|---|---|---|-----------------------------------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | RIM Routing Address discriminator | | | | +| octet 4-n | RIM Routing Address | | | | | | | | + +The coding of *RIM Routing Address discriminator* (bits 4 to 1 of octet 3) is a binary number indicating which type of address is provided in octet 4-n. The *RIM Routing Address discriminator* is coded as follows: + +| | | +|-------------|-----------------------------------------------------------------| +| Bits | | +| 4321 | | +| 0000 | A Cell Identifier is used to identify a GERAN cell. | +| 0001 | An RNC identifier is used to identify a UTRAN RNC. | +| 0010 | An eNB identifier is used to identify an E-UTRAN eNodeB or HeNB | +| 0011 | An eHRPD Sector ID is used to identify an eHRPD eAN | + +All other values are reserved. + +The coding of octet 4-n depends on the *RIM Routing Address discriminator* (octet 3) as it is specified below. + +### **RIM Routing Address discriminator = 0000:** + +The *RIM Routing Address* field contains a Cell Identifier and is coded as the value part (octet 3 to octet 10) of the *Cell Identifier* information element specified in sub-clause 11.3.9. + +### **RIM Routing Address discriminator = 0001:** + +The *RIM Routing Address* field contains an RNC identifier and is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|------------| +| Octets 4 to 9 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | | | | | | | | octets 4-9 | +| RNC-ID (or Extended RNC-ID) | | | | | | | | octet 10 | +| RNC-ID (or Extended RNC-ID) (continued) | | | | | | | | octet 11 | + +The octets 10-11 contain the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) - see 3GPP TS 25.413: + +- The least significant bit of RNC-ID is octet 11 bit 1 and most significant bit is octet 10 bit 4. In the octet 10 bits 5-8 are set to "0000". +- The least significant bit of Extended RNC-ID is octet 11 bit 1 and most significant bit is octet 10 bit 8. + +### **RIM Routing Address discriminator = 0010:** + +The *RIM Routing Address* field contains an eNB identifier and is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----------| +| Octets 4 to 8 contain the value part (starting with octet 2) of the Tracking Area Identity IE defined in 3GPP TS 24.301 [37], not including 3GPP TS 24.301 IEI [37] | | | | | | | | octet 4-8 | +| Global eNB ID | | | | | | | | octet 9-n | + +Octets 9-n contain the Global eNB ID (see 3GPP TS 36.413 [36] sub-clause 9.3.4, *Global-ENB-ID* Sequence) of the eNodeB. + +#### **RIM Routing Address discriminator = 0011:** + +The *RIM Routing Address* field contains an eHRPD evolved Access Network identifier and is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------|---|---|---|---|---|---|---|-----------| +| eHRPD Sector ID | | | | | | | | octet 4-n | + +Octets 4-n contain the eHRPD Sector ID defined in 3GPP2 C.S0024-B [47]. + +### 11.3.71 MBMS Session Identity + +The MBMS Session Identity is an identification of the MBMS Session as defined in 3GPP TS 23.246 [32]. The element coding is: + +**Table 11.3.71: MBMS Session Identity IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | MBMS-Session-Identity AVP encoded as in 3GPP TS 29.061 [31], excluding AVP Header fields as defined in IETF RFC 3588 [33]. | | | | | | | | + +### 11.3.72 MBMS Session Duration + +The MBMS Session Duration defines the (remaining) duration of the MBMS Session as defined in 3GPP TS 23.246 [32]. The element coding is: + +**Table 11.3.72: MBMS Session Duration IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-m | MBMS-Session-Duration AVP encoded as in 3GPP TS 29.061 [31], excluding AVP Header fields as defined in IETF RFC 3588 [33]. | | | | | | | | + +### 11.3.73 MBMS Service Area Identity List + +The MBMS Service Area Identity List identifies the Service Areas Identities for the Service Areas where the MBMS Session shall be active as defined in 3GPP TS 29.061. The element coding is: + +**Table 11.3.73: MBMS Service Area Identity List IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------|---------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 - 514 | MBMS-Service-Area AVP encoded as in 3GPP TS 29.061, excluding AVP Header fields (as defined in IETF RFC 3588 [33]). | | | | | | | | + +### 11.3.74 MBMS Response + +The MBMS Response identifies the Cause Values from the BSS regarding MBMS. + +**Table 11.3.74.a: MBMS Response IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|-------|-------|-------|-------------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Spare | Spare | Spare | Spare | Cause Value | | | | + +**Table 11.3.74.b: Cause Value** + +| | | | | | | | | | +|-----------|---|---|---|---|------------------------------------------------------------------------|--|--|--| +| (octet 3) | | | | | | | | | +| Bits | 8 | 7 | 6 | 5 | Spare | | | | +| Bits | 4 | 3 | 2 | 1 | | | | | +| 0 0 0 0 | | | | | Acknowledge | | | | +| 0 0 0 1 | | | | | Acknowledge, initiate data transfer | | | | +| 0 0 1 0 | | | | | Acknowledge, data transfer initiated from other SGSN | | | | +| 0 0 1 1 | | | | | Reject - Congestion | | | | +| 0 1 0 0 | | | | | Reject - None of the listed MBMS Service Areas are supported by BSS | | | | +| 0 1 0 1 | | | | | Reject - MBMS Service Context is released due to interrupted data flow | | | | +| 0 1 1 0 | | | | | : Unspecified in this version of the protocol | | | | +| 1 1 1 1 | | | | | | | | | + +## 11.3.75 MBMS Routing Area List + +The MBMS Routing Area List identifies each Routing Area that contains at least one PMM-IDLE MS that has activated the MBMS bearer service. The list may be empty. + +**Table 11.3.75.a: MBMS Routing Area List IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------|----------------------------------------|---|---|---|-------|-------|-------|-------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Number of Routing Area Identifications | | | | Spare | Spare | Spare | Spare | +| octet 4 - 11 | Routing Area Identification 1 | | | | | | | | +| octet 12 - 19 | Routing Area Identification 2 | | | | | | | | +| octet 20 - 27 | Routing Area Identification 3 | | | | | | | | +| octet 28 - 35 | Routing Area Identification 4 | | | | | | | | +| octet 36 - 43 | Routing Area Identification 5 | | | | | | | | +| octet 44 - 51 | Routing Area Identification 6 | | | | | | | | +| octet 52 - 59 | Routing Area Identification 7 | | | | | | | | +| octet 60 - 67 | Routing Area Identification 8 | | | | | | | | +| octet 68 - 75 | Routing Area Identification 9 | | | | | | | | +| octet 76 - 83 | Routing Area Identification 10 | | | | | | | | +| octet 84 - 91 | Routing Area Identification 11 | | | | | | | | +| octet 92 - 99 | Routing Area Identification 12 | | | | | | | | +| octet 100 - 107 | Routing Area Identification 13 | | | | | | | | +| octet 108 - 115 | Routing Area Identification 14 | | | | | | | | + +**Table 11.3.75.b: MBMS Routing Area List information element details** + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Number of Routing Areas (octet 3)
8 7 6 5
0 0 0 0 Notification shall not be sent to any Routing Areas in the BSS
0 0 0 1 "1" Routing Area Identities
:
:
1 1 1 0 "14" Routing Area Identities
1 1 1 1 Notification shall be sent in all Routing Areas in the BSS

4 3 2 1 (octet 3)
Spare | +| Routing Area Identification i 7 octets (octet 4, 12, 20, 28, 36, 44, 52, 60, 68, 76, 84, 92, 100 and 108)
The element is coded as the Routing Area Identification information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator. | + +## 11.3.76 MBMS Session Information + +The MBMS Session Information carries information about the MBMS Session from the SGSN to the BSS. + +**Table 11.3.76.a: MBMS Session Information IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|-------|-------|-------|-------|-------|-------|-------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | Spare | Spare | Spare | Spare | Spare | Spare | BC/MC | + +**Table 11.3.76.b: MBMS Session Information information element details** + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BC/MC (octet 3)
This field indicates whether it is a Broadcast or an Multicast MBMS Session.
Bit
1
0 Broadcast Session
1 Multicast Session

8 7 6 5 4 3 2 (octet 3)
Spare | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 11.3.77 TMGI (Temporary Mobile Group Identity) + +The purpose of TMGI is for group paging in MBMS as defined in 3GPP TS 24.008. + +**Table 11.3.77: TMGI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|------------|-------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2,2a | Length Indicator | | | | | | | | +| octet 3-8 | Rest of element coded as in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator. | | | | | | | | + +### 11.3.78 MBMS Stop Cause + +The MBMS Stop Cause identifies the Cause Values for stopping an MBMS Session. + +**Table 11.3.74.a: MBMS Stop Cause IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|-------|-------|-------|-------------|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Spare | Spare | Spare | Spare | Cause Value | | | | + +**Table 11.3.74.b: Cause Value** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| (octet 3)
Bits 8 7 6 5 Spare

Bits
4 3 2 1
0 0 0 0 MBMS Session terminated by upstream node
0 0 0 1 MBMS Session terminated by SGSN
0 0 1 0 : Unspecified in this version of the protocol
1 1 1 1 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 11.3.79 Source BSS to Target BSS Transparent Container + +This information element contains the information needed in the Target BSS to execute a PS Handover. + +The element coding is: + +**Table 11.3.79.a: Source BSS to Target BSS Transparent Container coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-? | Source BSS to Target BSS Transparent Container Contents coded as defined in table 11.3.79.b | | | | | | | | + +**Table 11.3.79.b: Source BSS to Target BSS Transparent Container Contents** + +| Information Elements | Type / Reference | Presence | Format | Length | +|----------------------------------------------------|-------------------------------------------------------------|--------------------|--------|--------| +| MS Radio Access Capability | MS Radio Access Capability/11.3.22 | M | TLV | 7-? | +| Inter RAT Handover Info | Inter RAT Handover Info/11.3.94 | O (note 1) | TLV | 3-? | +| Page Mode | Page Mode/11.3.88 | O (note 2, note 3) | TLV | 3 | +| Container ID | Container ID/11.3.89 | O (note 2) | TLV | 3 | +| Global TFI | Global TFI/11.3.90 | O (note 2, note 3) | TLV | 3 | +| PS Handover Indications | PS Handover Indications/11.3.95a | O | TLV | 3 | +| CS Indication | CS Indication/11.3.98 | O (note 3) | TLV | 3 | +| E-UTRAN Inter RAT Handover Info | E-UTRAN Inter RAT Handover Info/11.3.104 | O (note 1) | TLV | 3-? | +| IRAT Measurement Configuration | IRAT Measurement Configuration/11.3.115 | O (note 4) | TLV | 3-? | +| Source Cell ID | Source Cell ID/11.3.120 | O (note 4, note 5) | TLV | 8-? | +| IRAT Measurement Configuration (extended E-ARFCNs) | IRAT Measurement Configuration (extended E-ARFCNs)/11.3.121 | O (note 4) | TLV | 3-? | + +NOTE1: This information element shall be present if available in the source BSS. +NOTE2: This information element shall be present in case of PS Handover from A/Gb mode. +NOTE3: This information element shall be present in case of DTM Handover from A/Gb mode. +NOTE4: This information element may be present in case of PS Handover from E-UTRAN (see 3GPP TS 36.413 [36]) +NOTE 5: This information element shall be present in case either the *IRAT Measurement Configuration* information element or the *IRAT Measurement Configuration (extended E-ARFCNs)* information element is present. + +## 11.3.80 Target BSS to Source BSS Transparent Container + +This information element contains the information needed in the Source BSS to execute a PS Handover. + +The element coding is: + +**Table 11.3.80.a: Target BSS to Source BSS Transparent Container coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|------------|---------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 2a | Length Indicator | | | | | | | | +| Octet 3-? | Target BSS to Source BSS Transparent Container Contents coded as defined in table 11.3.80.b | | | | | | | | + +**Table 11.3.80.b: Target BSS to Source BSS Transparent Container Contents** + +| Information Elements | Type / Reference | Presence | Format | Length | +|----------------------|------------------------------|------------|--------|--------| +| PS Handover Command | PS Handover Command/11.3.95 | O (Note 2) | TLV | 4-? | +| SI/PSI Container | SI/PSI Container/11.3.95b | O (Note 1) | TLV | 3-? | +| DTM Handover Command | DTM Handover Command/11.3.97 | O (Note 2) | TLV | 22-? | + +NOTE 1: This information element shall be included when requested in the PS-HANDOVER-REQUEST PDU. +NOTE 2: Only one of these information elements shall be included. + +### 11.3.81 NAS container for PS Handover + +This information element contains the NAS container for PS Handover. The value part of this IE is to be included in the PS Handover Command message within the *Target BSS to Source BSS Transparent Container IE*. + +The element coding is: + +**Table 11.3.81: NAS container for PS Handover coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octets 3-? | NAS container for PS HO coded as defined in 3GPP TS 24.008 | | | | | | | | + +### 11.3.82 PFCs to be set-up list + +This information element contains the Packet Flow Context parameters for one or more PFC(s), that the SGSN requests the target BSS to set-up. + +The element coding is: + +**Table 11.3.82.a: PFCs to be set-up list IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Number of PFCs | | | | | | | | +| Octet 4-6 | PFI (1) | | | | | | | | +| Octet 7-9 | PFT (1) | | | | | | | | +| Octet 10-? | ABQP (1) | | | | | | | | +| Octet ?-? | Allocation/Retention Priority (1) | | | | | | | | +| Octet ?-? | T10 (1) | | | | | | | | +| Octet ?-? | PFI (2) | | | | | | | | +| Octet ?-? | PFT (2) | | | | | | | | +| Octet ?-? | ABQP (2) | | | | | | | | +| Octet ?-? | Allocation/Retention Priority (2) | | | | | | | | +| Octet ?-? | T10 (2) | | | | | | | | +| " | " | | | | | | | | +| Octet ?-? | PFI (n) | | | | | | | | +| Octet ?-? | PFT (n) | | | | | | | | +| Octet ?-? | ABQP (n) | | | | | | | | +| Octet ?-? | Allocation/Retention Priority (n) | | | | | | | | +| Octet ?-? | T10 (n) | | | | | | | | + +**Number of PFCs:** Number of PFCs for which packet flow context parameters are provided. For each of those PFCs follows its identifier and the packet flow context parameters. The "Number of PFCs" parameter is coded as shown below: + +**Table 11.3.82.b: Number of PFCs** + +| Coding | Semantic | +|-----------|----------| +| 0000 0000 | Reserved | +| 0000 0001 | 1 PFC | +| ... | ... | +| 0000 1011 | 11 PFCs | +| 0000 1100 | Reserved | +| ... | ... | +| 1111 1111 | Reserved | + +**PFI:** Packet Flow Identifier. Coded as the Packet Flow Identifier information element, see sub-clause 11.3.42 + +**PFT:** Packet Flow Timer. Coded as the GPRS Timer information element, see sub-clause 11.3.44. + +**ABQP:** Aggregate BSS QoS Profile. Coded as the Aggregate BSS QoS Profile information element, see sub-clause 11.3.43. + +**Allocation/Retention Priority:** Allocation Retention Priority. Coded as the Priority information element, see sub-clause 11.3.27. This information element is optionally included. + +**T10:** T10. Coded as the GPRS Timer information element, see sub-clause 11.3.44. This information element shall be present for a PFC if the Allocation/Retention Priority is present and if queuing is allowed for the PFC. + +## 11.3.83 List of set-up PFCs + +This information element contains the Packet Flow Identifiers of the PFCs that were successfully allocated in the target system during a PS handover. The element coding is: + +**Table 11.3.83.a: List of set-up PFCs IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Number of PFCs | | | | | | | | +| Octet 4 | PFI (1) | | | | | | | | +| Octet 5 | PFI (2) | | | | | | | | +| " | " | | | | | | | | +| Octet ? | PFI (n) | | | | | | | | + +**Number of PFCs:** Number of PFCs for which corresponding Packet Flow Identifiers are provided. The "Number of PFCs" parameter is coded as shown below: + +**Table 11.3.83.b: Number of PFCs** + +| Coding | Semantic | +|-----------|----------| +| 0000 0000 | 0 PFC | +| 0000 0001 | 1 PFC | +| ... | ... | +| 0000 1011 | 11 PFCs | +| 0000 1100 | Reserved | +| ... | ... | +| 1111 1111 | Reserved | + +**PFI:** Packet Flow Identifier. Coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI. + +## 11.3.84 Extended Feature Bitmap + +The Extended Feature bitmap information element indicates the optional features supported by the underlying NSE. The element coding is: + +**Table 11.3.84.a: Extended Feature Bitmap IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|------|-----|--------------------|----------------|------|----------------------|----------------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | MSAD
CN | eDRX | DCN | EC-
GSM-
IoT | CS/PS
coord | MOCN | Gigabit
Interface | PS
Handover | + +**Table 11.3.84.b: "PS Handover" coding** + +| coding | Semantic | +|--------|---------------------------| +| 0 | PS Handover not supported | +| 1 | PS Handover supported | + +**Table 11.3.84.c: "Gigabit Interface" coding** + +| coding | Semantic | +|--------|---------------------------------| +| 0 | Gigabit Interface not supported | +| 1 | Gigabit Interface supported | + +**Table 11.3.84.d: "Multi Operator Core Network" coding** + +| coding | Semantic | +|--------|-------------------------------------------| +| 0 | Multi Operator Core Network not supported | +| 1 | Multi Operator Core Network supported | + +**Table 11.3.84.e: "CS/PS coordination enhancements" coding** + +| coding | Semantic | +|----------|-----------------------------------------------| +| 0 | CS/PS coordination enhancements not supported | +| 1 (note) | CS/PS coordination enhancements supported | + +**Table 11.3.84.f: "EC-GSM-IoT" coding** + +| coding | Semantic | +|--------|--------------------------| +| 0 | EC-GSM-IoT not supported | +| 1 | EC-GSM-IoT supported | + +**Table 11.3.84.g: "eDRX" coding** + +| coding | Semantic | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| 0 | eDRX is not supported (see Note 1) | +| 1 | eDRX is supported | +| Note 1: A SGSN shall consider a BSS that indicates it does not support eDRX but indicates it supports EC-GSM-IoT as only supporting the lowest eDRX cycle (see 3GPP TS 23.682). | | + +**Table 11.3.84.h: "DCN" coding** + +| coding | Semantic | +|--------|--------------------------------------| +| 0 | Dedicated Core Network not supported | +| 1 | Dedicated Core Network supported | + +**Table 11.3.84.i: "MSADCN" coding** + +| coding | Semantic | +|---------------|------------------------------------------------------------| +| 0 | MS assisted Dedicated Core Network selection not supported | +| 1 | MS assisted Dedicated Core Network selection supported | + +NOTE: The CS/PS coordination enhancements bit may only be set to '1' if the Multi Operator Core Network bit is set to '1'. + +## 11.3.85 Source to Target Transparent Container + +This information element contains the information needed in the target RAN node to execute a inter-RAT PS or DTM Handover. + +The element coding is: + +**Table 11.3.85: Source to Target Transparent Container coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------------------------------------------------------------------------------------------|----------|----------|----------|----------|----------|----------|----------| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octets 3-? | Source to Target Transparent Container content coded as specified in 3GPP TS 25.413 or 3GPP TS 36.413. | | | | | | | | + +In inter-RAT handovers to *Iu* mode this IE includes the Source RNC to Target RNC Transparent container. The Source RNC to Target RNC Transparent Container content structure and encoding is defined in relevant RANAP specification 3GPP TS 25.413, excluding RANAP tag. + +In inter-RAT handover to E-UTRAN this IE includes the Source eNB to Target eNB Transparent container. The Source eNB to Target eNB Transparent Container content structure and encoding is defined in 3GPP TS 36.413. + +## 11.3.86 Target to Source Transparent Container + +This information element contains the information needed in the Source BSS to execute a inter-RAT PS Handover. + +The element coding is: + +**Table 11.3.86: Target to Source Transparent Container coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|----------|----------|----------|----------|----------| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octets 3-? | Rest of element coded as either a complete Handover to UTRAN Command radio interface message (as defined in 3GPP TS 25.331) or a complete Radio Bearer Reconfiguration radio interface message (as defined in 3GPP TS 44.118) or a HandoverCommand message that consists only of the DL-DCCH-Message including a complete RRConnectionReconfiguration radio interface message (as defined in 3GPP TS 36.331) | | | | | | | | + +## 11.3.87 RNC Identifier + +This information element contains the identifier of the RNC in case of PS Handover to UTRAN or the Corresponding RNC-ID of the eNB in case of PS handover to E-UTRAN as specified in 3GPP TS 25.413. + +The element coding is: + +**Table 11.3.87: RNC Identifier coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octets 3-8 | Octets 3 to 8 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | | | | | | | | +| Octet 9 | RNC ID (or Extended RNC-ID or Corresponding RNC-ID) | | | | | | | | +| Octet 10 | RNC ID (or Extended RNC-ID or Corresponding RNC-ID)
(continued) | | | | | | | | + +**RNC ID (or Extended RNC-ID or Corresponding RNC-ID):** The octets 9-10 contain the RNC-ID (0..4095) or the Corresponding RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) - see 3GPP TS 25.413: + +- The least significant bit of RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 4. In the octet 9 bits 5-8 are set to "0000". +- The least significant bit of Extended RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 8. + +For detailed definition of the RNC-Id see 3GPP TS 23.003. + +## 11.3.88 Page Mode + +This information element contains the Page Mode to be used by the MS. + +The element coding is: + +**Table 11.3.88: Page Mode coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|------------------------------------------------------------|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Reserved | | | | | | PAGE_MODE
coded as
specified in
3GPP TS
44.060 | | + +## 11.3.89 Container ID + +This information element contains the identity of the neighbour cell system information container previously sent to the MS. + +The element coding is: + +**Table 11.3.89: Container ID coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---------------------------------------------------------------|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Reserved | | | | | | Container ID
coded as
specified in
3GPP TS
44.060 | | + +## 11.3.90 Global TFI + +This information element contains the TFI of the mobile station's downlink or uplink TBF. + +The element coding is: + +**Table 11.3.90: Global TFI coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|-------------------------------------------------|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Reserved | Global TFI coded as specified in 3GPP TS 44.060 | | | | | | | + +## 11.3.91 IMEI + +This information element contains the International Mobile Station Equipment Identity (see 3GPP TS 23.003). The element coding is: + +**Table 11.3.91: IMEI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-10 | Octets 3-10 contain the IMEI coded as the value part of the Mobile Identity IE defined in 3GPP TS 24.008
(NOTE 1) | | | | | | | | +| NOTE 1: The Type of identity field in the Mobile Identity IE shall be ignored by the receiver. | | | | | | | | | + +## 11.3.92 Time to MBMS Data Transfer + +The Time to MBMS Data Transfer denotes the time occurring between the transmission of the MBMS-SESSION-START-REQUEST PDU or the MBMS-SESSION-UPDATE-REQUEST PDU to the BSS and the actual start of the data transfer at the BM-SC. + +**Table 11.3.92.a: Time to MBMS Data Transfer IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Time to MBMS Data Transfer Value Part | | | | | | | | + +**Table 11.3.92.b: Time to MBMS Data Transfer Value Part Coding** + +| | | | +|-----------------|------|--| +| Bits | | | +| 8 7 6 5 4 3 2 1 | | | +| 0 0 0 0 0 0 0 0 | 1s | | +| 0 0 0 0 0 0 0 1 | 2s | | +| 0 0 0 0 0 0 1 0 | 3s | | +| ⋮ | | | +| 1 1 1 1 1 1 1 1 | 256s | | + +### 11.3.93 MBMS Session Repetition Number + +The MBMS Session Repetition Number denotes the repetition number of the MBMS session as defined in 3GPP TS 23.246 [32]. The element coding is: + +**Table 11.3.93: MBMS Session Repetition Number IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | MBMS-Session-Repetition-Number AVP encoded as in 3GPP TS 29.061 [31], excluding AVP Header fields as defined in IETF RFC 3588 [33]. | | | | | | | | + +### 11.3.94 Inter RAT Handover Info + +This information element contains UTRAN related information needed to be transferred to the target RNC during a PS Handover to UTRAN. The element coding is: + +**Table 11.3.94: Inter RAT Handover Information coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octets 3-? | Inter RAT Handover Information coded as specified in 3GPP Technical Specification 25.331 | | | | | | | | + +### 11.3.95 PS Handover Command + +This information element contains the radio interface message to be sent to the mobile station. + +The element coding is: + +**Table 11.3.95: PS Handover Command coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 2a | Length Indicator | | | | | | | | +| Octet 3-? | Rest of element coded as a complete PS Handover Command radio interface message as defined in 3GPP TS 44.060 (carrying the PS Handover to A/Gb Mode Payload ) | | | | | | | | + +### 11.3.95a PS Handover Indications + +The *PS Handover Indications* information element provides indications related to the PS Handover procedure. The element coding is: + +**Table 11.3.95a.a: PS Handover Indications IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---------------|---|--------|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | DMLC Carriers | | SI/PSI | | + +**Table 11.3.95a.b: "SI/PSI" coding** + +| coding | Semantic | +|--------|----------------------| +| 0 | SI/PSI not requested | +| 1 | SI/PSI requested | + +**Table 11.3.95a.c: "DLMC Carriers" coding** + +| coding | Semantic | +|---------------|---------------------------------------| +| 00 | 2 or 3 carriers currently assigned | +| 01 | 4 or 5 carriers currently assigned | +| 10 | 6 or 7 carriers currently assigned | +| 11 | 8 or more carriers currently assigned | + +## 11.3.95b SI/PSI Container + +The *SI/PSI Container* information element provides the (Packet) System Information messages of the GSM target cell that are required by the mobile station for PS Handover. The element coding is: + +**Table 11.3.95b.a: SI/PSI Container coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|----------|----------|----------|----------|----------|----------|----------| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Number of SI/PSI | | | | | | | Type | +| Octet 4-n | SI/PSI | | | | | | | | + +**Type:** This field indicates the type of the (Packet) System Information messages provided by the target cell. The *Type* field is coded as shown below: + +**Table 11.3.95b.b: Type coding** + +| Coding | Semantic | +|---------------|-------------------------------------------------------------| +| 0 | SI messages as specified for BCCH (3GPP TS 44.018) follow | +| 1 | PSI messages as specified for PBCCH (3GPP TS 44.060) follow | + +**Number of SI/PSI:** This field indicates the number of (Packet) System Information messages contained in the *SI/PSI field*. For (Packet) System Information messages with multiple instances, each instance is counted as one SI/PSI message. The *Number of SI/PSI* field is coded as shown below: + +**Table 11.3.95b.c: Number of SI/PSI coding** + +| Coding | Semantic | +|---------------|---------------------| +| 000 0000 | 0 "SI/PSI" follows | +| 000 0001 | 1 "SI/PSI" follow | +| , | " | +| 111 1111 | 127 "SI/PSI" follow | + +**SI/PSI:** This field contains either a list of System Information or a list of Packet System Information messages of the GSM target cell that are required by the mobile station for PS Handover as specified in 3GPP TS 44.060. The number of (Packet) System Information messages is indicated in the *Number of SI/PSI* field specified above. Furthermore: + +- If the *Type* field indicates that "SI messages as specified for BCCH (3GPP TS 44.018) follow" then the *SI/PSI* field contains the subset of System Information message instances encoded for BCCH as specified in 3GPP TS 44.018. Each System Information message contains the *Message type* octet followed by all the IEs composing the message payload. Each message is 21 octets long. +- If the *Type* field indicates that "PSI messages as specified for PBCCH (3GPP TS 44.060) follow" then the *SI/PSI* field contains the subset of Packet System Information message instances encoded for PBCCH as specified in 3GPP TS 44.060. Each Packet System Information message contains the *MESSAGE\_TYPE* field followed by the PSI message content. Each message is 22 octets long. + +## 11.3.95c Active PFCs List + +This information element contains the Packet Flow Identifiers of the PFCs that are active in the source BSS at the time the PS Handover Required message is sent. The element coding is: + +**Table 11.3.95c.a: Active PFCs List IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Number of PFCs | | | | | | | | +| Octet 4 | PFI (1) | | | | | | | | +| Octet 5 | PFI (2) | | | | | | | | +| " | " | | | | | | | | +| Octet ? | PFI (n) | | | | | | | | + +**Number of PFCs:** Number of PFCs for which corresponding Packet Flow Identifiers are provided. The "Number of PFCs" parameter is coded as shown below: + +**Table 11.3.95c.b: Number of PFCs** + +| Coding | Semantic | +|-----------|----------| +| 0000 0000 | Reserved | +| 0000 0001 | 1 PFC | +| ... | ... | +| 0000 1011 | 11 PFCs | +| 0000 1100 | Reserved | +| , | " | +| 1111 1111 | Reserved | + +**PFI:** Packet Flow Identifier. Coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI. This IE shall not contain any pre-defined PFIs. + +## 11.3.96 Velocity Data + +This is a variable length information element providing an estimate of a velocity data. The element coding is: + +**Table 11.3.96: Velocity Data IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet n | The rest of the information element contains an octet sequence identical to that for Description of Velocity defined in 3GPP TS 23.032. | | | | | | | | + +## 11.3.97 DTM Handover Command + +This information element contains the radio interface message to be sent to the mobile station. + +The element coding is: + +**Table 11.3.97: DTM Handover Command coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-? | Rest of element coded as a complete DTM Handover Command radio interface message as defined in 3GPP TS 44.060 (carrying the DTM Handover to A/Gb Mode Payload ) | | | | | | | | + +### 11.3.98 CS Indication + +This information element indicates to the target BSS that this PS Handover is part of a DTM Handover Procedure. + +The element coding is: + +**Table 11.3.98: CS Indication coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | CS Indication Contents | | | | | | | | + +**CS Indication Contents:** This identifies a particular handover attempt for this MS. This shall be identical to the *PS Indication Contents* value in the corresponding *PS Indication IE* included in the *Old BSS to New BSS Information IE* (see 3GPP TS 48.008). The choice of the value of this field is implementation specific, with the requirement that consecutive handover attempts for the same mobile station shall not have the same *CS Indication Contents* value. + +### 11.3.99 Requested GANSS Assistance Data + +This information element provides the information on which GANSS Assistance Data has been requested. The element coding is: + +**Table 11.3.99: Requested GANSS Assistance Data IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.100 GANSS Location Type + +This information element provides the GANSS Location Type. The element coding is: + +**Table 11.3.53: Location Type IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.101 GANSS Positioning Data + +This information element provides GANSS Positioning Data. The element coding is: + +**Table 11.3.55: Positioning Data IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3-n | Rest of element coded as the value part defined in 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator | | | | | | | | + +### 11.3.102 Flow Control Granularity + +This information element provides the granularity to be used for deriving the Flow Control parameters values in the *BVC Bucket Size IE*, the *BVC Bucket Leak Rate IE* and the *PFC flow control parameters IE* when the Gigabit Interface feature is negotiated. The element coding is: + +**Table 11.3.102: Flow Control Granularity IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|-------------|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Reserved | | | | | | Granularity | | + +**Table 11.3.102.a: "Granularity" coding** + +| coding | Semantic | +|--------|------------------------------------| +| 00 | 100 octets or bits/s increments | +| 01 | 1000 octets or bits/s increments | +| 10 | 10000 octets or bits/s increments | +| 11 | 100000 octets or bits/s increments | + +### 11.3.103 eNB Identifier + +This information element contains the information required to identify an eNB within a PLMN. + +The element coding is: + +**Table 11.3.103: eNB Identifier coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octets 3-7 | Octets 3 to 7 contain the value part (starting with octet 2) of the Tracking Area Identity IE defined in 3GPP TS 24.301 [37], not including 3GPP TS 24.301 IEI [37] | | | | | | | | +| Octet 8-n | Global eNB ID | | | | | | | | + +Octets 8-n contain the Global eNB ID (see 3GPP TS 36.413 [36] sub-clause 9.3.4, *Global-ENB-ID Sequence*) of the eNodeB. + +### 11.3.104 E-UTRAN Inter RAT Handover Info + +This information element contains E-UTRAN related information needed to be transferred to the target eNB during a PS Handover to E-UTRAN. The element coding is: + +**Table 11.3.104: E-UTRAN Inter RAT Handover Information coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octets 3-? | Formatted and coded according to the UE-EUTRA-Capability IE defined in 3GPP Technical Specification 36.331. The most significant bit of the first octet of the octet string contains bit 8 of the first octet of the IE. | | | | | | | | + +### 11.3.105 Subscriber Profile ID for RAT/Frequency priority + +This information element may be used by the BSS to provide individual priorities (see 3GPP TS 44.060) to mobile stations. + +The element coding is: + +**Table 11.3.105.1: Subscriber Profile ID for RAT/Frequency priority coding** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|---------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | Octet 3 contains the value part of the Subscriber Profile ID for RAT/Frequency priority IE. | | | | | | | | + +Octet 3 contains a number in binary representation ranging from 0 to 255. The Subscriber Profile ID for RAT/Frequency priority is given by the indicated value +1. + +### 11.3.106 Request for Inter-RAT Handover Info + +The *Request for Inter RAT Handover Info* information element provides the request from the BSS to the SGSN for the *Inter RAT Handover Info* IE for UTRAN necessary for inter-RAT PS Handover procedure to UTRAN. The element coding is: + +**Table 11.3.106.a: Request for Inter RAT Handover Info IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|-------------------------------------------------|-----------------------------------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | | | E-UTRAN
Inter RAT
Handover
Info
Req | Inter RAT
Handover
Info Req | + +**Table 11.3.106.b: "Inter RAT Handover Info Req" coding** + +| Coding | Semantic | +|--------|---------------------------------------| +| 0 | Inter RAT Handover Info not requested | +| 1 | Inter RAT Handover Info requested | + +**Table 11.3.106.c: "E-UTRAN Inter RAT Handover Info Req" coding** + +| coding | Semantic | +|------------------------------------------------------------------------------------------------|----------| +| 0 | See note | +| NOTE: The value '1' was allocated in a previous version of the protocol and shall not be used. | | + +### 11.3.107 Reliable Inter-RAT Handover Info + +The *Reliable Inter RAT Handover Info* information element provides to the target BSS the indication that the source BSS has received the *Inter RAT Handover Info* for UTRAN from the SGSN in the CREATE-BSS-PFC-PDU or in the PS-HANDOVER-COMPLETE-ACK PDU upon successful completion of PS handover or a PS-HANDOVER-REQUEST PDU with "*Reliable Inter RAT Handover Info Indicator*" set to "1". The element coding is: + +**Table 11.3.107.a: Reliable Inter RAT Handover Info IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|--------------------------------------------------------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | | | | Reliable
Inter RAT
Handover
Info
Indicator | + +Table 11.3.107.b: "Reliable Inter RAT Handover Info Indicator" coding + +| Coding | Semantic | +|--------|--------------------------------------| +| 0 | Inter RAT Handover Info not reliable | +| 1 | Inter RAT Handover Info reliable | + +### 11.3.108 SON Transfer Application Identity + +This information element specifies the addressed SON Transfer application within the target BSS node. The element coding is: + +Table 11.3.108: SON Transfer Application Identity IE + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3-m | SON Transfer Application Identity | | | | | | | | + +**SON Transfer Application Identity:** This field is encoded as the *SON Transfer Application Identity* IE as defined in 3GPP TS 36.413 [36]. + +### 11.3.109 CSG Identifier + +The *CSG Identifier* information element indicates the identifier of the Closed Subscriber Group within the PLMN, as defined in [40], and the cell access mode of the CSG cell as defined in [22], [39]. The element coding is: + +Table 11.3.109.a: CSG Identifier IE + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|------------------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octets 3-6 | Octets 3 to 6 contain the CSG Identity (CSG-ID) of the cell (defined in 3GPP TS 23.003) as reported by the mobile station (see 3GPP TS 44.060). Bits 4 to 8 of octet 6 are spare and set to zero. | | | | | | | | +| octet 7 | Spare | | | | | | | Cell Access Mode | + +Table 11.3.109.b: Cell Access Mode field element details + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell Access Mode (bit 1 of octet 7)
This field indicates the cell access mode of the cell as reported by the mobile station.
Bit
1
0 CSG cell
1 Hybrid cell | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +Spare bits are reserved and coded with zeroes. + +### 11.3.110 Tracking Area Code + +The TAC information element provides an unambiguous identification of tracking areas needed for routing of the PS handover signalling to the target cell. The element coding is: + +Table 11.3.110: TAC IE + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--|---|---|---|---|---|---|---|---| +|--|---|---|---|---|---|---|---|---| + +| | | +|-------------|-------------------------------------------------------------------------------------------------------| +| octet 1 | IEI | +| octet 2, 2a | Length Indicator | +| octets 3-5 | Octets 3 to 5 contain the value part (starting with octet 2) of the TAC IE defined in 3GPP TS 24.301. | + +### 11.3.111 Redirect Attempt Flag + +This information element provides control information for the MOCN, GWCN and for the DCN rerouting procedure. It indicates that the CN shall include in the answer either Redirection Indication IE or Redirection Completed IE. + +The element coding is: + +**Table 11.3.111: Redirect Attempt Flag IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | spare | | | | | | | | + +### 11.3.112 Redirection Indication + +This information element provides control information for the MOCN, GWCN and for the DCN rerouting procedure. It indicates that the CN requests rerouting by the BSS to another CN operator. The Reroute Reject cause is given. + +**Table 11.3.112: Redirection Indication IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Reroute Reject Cause value | | | | | | | | + +| Reroute Reject cause value (octet 3) | | | | | | | | | +|---------------------------------------------|---|---|---|---|---|---|---|--------------------------------------------------------------------------------------------| +| Bits | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 0 0 0 0 0 0 0 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 Reserved | +| 0 0 0 0 1 0 1 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 Reserved | +| 0 0 0 0 1 0 1 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 PLMN not allowed (meaning is defined in 3GPP TS 24.008 [11]) | +| 0 0 0 0 1 1 0 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 location area not allowed (meaning is defined in 3GPP TS 24.008 [11]) | +| 0 0 0 0 1 1 0 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 roaming not allowed in this location area (meaning is defined in 3GPP TS 24.008 [11]) | +| 0 0 0 0 1 1 1 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 GPRS services not allowed in this PLMN (meaning is defined in 3GPP TS 24.008 [11]) | +| 0 0 0 0 1 1 1 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 no suitable cell in location area (meaning is defined in 3GPP TS 24.008 [11]) | +| 0 0 0 1 0 0 0 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 CS/PS domain registration coordination required (meaning defined in 3GPP TS 23.251 [43]) | +| 0 0 0 1 0 0 0 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 Network failure (meaning is defined in 3GPP TS 24.008 [11]) | +| 0 0 0 1 0 0 1 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 Rerouting to a DCN required | +| 0 0 0 1 0 0 1 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 Reserved | +| 1 1 1 1 1 1 1 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 Reserved | + +### 11.3.113 Redirection Completed + +This information element provides control information for the MOCN, GWCN and for the DCN rerouting procedure. It indicates that the reroute procedure is completed. + +The element coding is: + +**Table 11.3.113: Redirection Completed IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | Outcome value | | | | | | | | + +| Outcome value (octet 3) | | | | | | | | | +|--------------------------------|---|---|---|---|---|---|---|--------------------------| +| Bits | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Reserved | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | MS is accepted | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | MS is not accepted | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | MS is already registered | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Reserved | +| | | | | | | | | " " | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Reserved | + +### 11.3.114 Unconfirmed send state variable + +This IE indicates the value of the Unconfirmed send state variable as defined in 3GPP TS 44.064 [12]. + +The element coding is: + +**Table 11.3.114: Unconfirmed send state variable IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|-------------| +| Octet 1 | IEI | | | | | | | | +| Octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | spare | | | | | | | V(U)
MSB | +| Octet 4 | V(U) | | | | | | | | + +Octet 2 and bit 1 of octet 3 contain a number in binary representation ranging from 0 to 511. The least significant bit is bit 1 of octet 3, and the most significant bit is bit 1 of octet 2. + +### 11.3.115 IRAT Measurement Configuration + +The *IRAT Measurement Configuration* IE is used to indicate to the BSS which frequency measurement results of the source RAT shall be collected after a successful inter-system handover. The *IRAT Measurement Configuration* IE is used by the source RAT to specify the E-UTRA frequencies for which the corresponding EARFCN is less than 65535 to be reported back to the source RAT (each of them associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements should last before triggering a *HO Report* for unnecessary handover to another RAT. + +NOTE 1: *HO Report* is defined in 3GPP TS 36.413 [36]. + +NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [45]. + +NOTE 3: E-UTRA frequencies corresponding to E-ARFCNs in the value range from 65536 to 262143 shall be indicated using the *IRAT Measurement Configuration (extended E-ARFCNs)* IE (see subclause 11.3.121); in such a case, E-UTRA frequencies corresponding to E-ARFCNs in the value range from 0 to 65534 (value 65535 is reserved and shall not be used) shall be indicated using the *IRAT Measurement Configuration* IE. + +The element coding is: + +**Table 11.3.115: IRAT Measurement Configuration IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | +|----------------|----------------------|-------|---------------------|---|-----------------------|---|---|---|--|--|--|--|--|--| +| Octet 1 | IEI | | | | | | | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | | | | | | | +| Octet 3 | Spare | REP_Q | REPORTING_THRESHOLD | | | | | | | | | | | | +| Octet 4 | Measurement_Duration | | | | | | | | | | | | | | +| Octets 5-6 | E-ARFCN | | | | | | | | | | | | | | +| Octet 7 | Spare | | | | Measurement Bandwidth | | | | | | | | | | +| Octets 8-9 | E-ARFCN | | | | | | | | | | | | | | +| Octet 10 | Spare | | | | Measurement Bandwidth | | | | | | | | | | +| " | " | | | | | | | | | | | | | | +| Octets m-(m+1) | E-ARFCN | | | | | | | | | | | | | | +| Octet m+2 | Spare | | | | Measurement Bandwidth | | | | | | | | | | + +**REPORTING\_THRESHOLD:** defines the reporting threshold to be used for measurement results analysis according to REP\_QUANT. This threshold is used to compare against the measurement results received from the MS. It is a value between 0 and 63 encoded on 6 bits according to 3GPP TS 45.008 [44] sub-section 8.1.5.4. + +**REP\_QUANT:** indicates the measurement quantity for E-UTRAN cells coded as follows: 0=RSRP 1=RSRQ. + +**Measurement\_Duration:** defines (in seconds) how long the BSS shall collect the measurements results received from the MS after a successful inter-RAT handover. It is a number in binary representation ranging from 1 to 100. + +**E-ARFCN:** designates a specific E-UTRA frequency for which the target RAT should continue to collect the measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from 0 to 65534 (value 65535 is reserved and shall not be used). + +**Measurement Bandwidth:** defines the measurement bandwidth of the E-UTRA frequency signalled in the two previous octets. It is coded on 3 bits according to 3GPP TS 44.018 [25]. + +## 11.3.116 SCI + +The SCI information element provides information on the service class of the user data. The element coding is: + +**Table 11.3.116-1: SCI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|-----------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Octet 3 contains the value part (octet 2) of the SCI IE defined in 3GPP TS 29.281 [46]. | | | | | | | | + +Octet 3 specifies the Service Class value for LLC PDUs of applications benefitting from specific RRM behaviour. + +## 11.3.117 GGSN/P-GW location + +The GGSN/P-GW location information element provides information on the location of the GGSN/P-GW that encoded the SCI. The element coding is: + +**Table 11.3.117.a: GGSN/P-GW location IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|--------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | GGSN/P-GW location | | | | | | | | + +In octet 3, bits 8 to 4 are spare, set to zero by the SGSN and shall be ignored by the BSS. The coding of bits 3 to 1 is specified in Table 11.3.117.b. + +**Table 11.3.117.b: GGSN/P-GW location coding** + +| Octet 3
Bit:
3 2 1 | Semantic | +|--------------------------|---------------------------------| +| 0 0 0 | HPLMN | +| 0 0 1 | VPLMN | +| 0 1 0 | Operator Group GGSN | +| 0 1 1 | Unknown | +| 1 0 0 to 1 1 1 | For future use (treat as VPLMN) | + +The conditions under which the SGSN indicates the values defined in Table 11.3.117.b are specified in 3GPP TS 23.060 [7]. + +## 11.3.118 Selected PLMN ID + +The purpose of the *Selected PLMN ID* information element is to provide the SGSN with the PLMN ID selected by a mobile station supporting network sharing when network sharing is in use in a cell. + +**Table 11.3.116: Selected PLMN ID IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|-----------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| Octet 3 | MCC dig 2 | | | | MCC dig 1 | | | | +| Octet 4 | MNC dig 3 | | | | MNC dig 2 | | | | +| Octet 5 | MNC dig 1 | | | | | | | | + +NOTE: The MCC and MNC value field is coded as specified within 3GPP TS 24.008 [11]. + +## 11.3.119 Priority Class Indicator + +This information element indicates that overload has occurred in the SGSN and traffic for the indicated priority class should be reduced. + +**Table 11.3.118: Priority Class Indicator IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|----------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | Value part of Priority Class Indicator | | | | | | | | + +The *Value part of Priority Class Indicator* is coded as a bit string with length of 8. Each bit represents a kind of priority class as specified below. If a bit is set to “1“, the signalling traffic of the respective priority class should be reduced. + +Bit (0) = A mobile station configured for "low access priority" as defined in TS 44.060. + +Bits (1...7) are spare. The SGSN shall set them to "0 ". The BSS shall ignore them. + +### 11.3.120 Source Cell ID IE + +The *Source Cell ID* IE is used to indicate to the BSS the identification of the source cell, e.g. in the Unnecessary IRAT HO case (see *IRAT Measurement Configuration IE* description, subclause 11.3.115). + +The element coding is: + +**Table 11.3.120: Source Cell ID IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------|------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3-7 | Tracking Area Identity | | | | | | | | +| Octet 8-m | E-UTRAN CGI | | | | | | | | +| Octet(m+1)-n | Global eNB ID | | | | | | | | + +**Tracking Area Identity:** Octets 3 to 7 contain the value part of the *Tracking Area Identity* IE defined in 3GPP TS 24.301, not including 3GPP TS 24.301 IEI. + +**E-UTRAN CGI:** Octets 8 - m contain the E-UTRAN CGI (see 3GPP TS 36.413 sub-clause 9.3.4, *EUTRAN-CGI* Sequence) for the source cell. + +**Global eNB ID:** Octets (m+1)-n contain the Global eNB ID (see 3GPP TS 36.413 sub-clause 9.3.4, *Global-ENB-ID* Sequence) for the source eNB. + +### 11.3.121 IRAT Measurement Configuration (extended E-ARFCNs) + +The *IRAT Measurement Configuration (extended E-ARFCNs)* IE is used to indicate to the BSS which frequency measurement results of the source RAT shall be collected after a successful inter-system handover. The *IRAT Measurement Configuration IE* is used by the source RAT to specify the E-UTRA frequencies for which the corresponding E-ARFCN is greater than 65535 to be reported back to the source RAT (each of them associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements should last before triggering a *HO Report* for unnecessary handover to another RAT. + +NOTE 1: *HO Report* is defined in 3GPP TS 36.413 [36]. + +NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [45]. + +The element coding is: + +**Table 11.3.121: IRAT Measurement Configuration (extended E-ARFCN) IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|----------------------|-----------|---|---------------------|---|-----------------------|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | Spare | REP_QUANT | | REPORTING_THRESHOLD | | | | | +| Octet 4 | Measurement_Duration | | | | | | | | +| Octets 5-6 | E-ARFCN | | | | | | | | +| Octet 7 | E-ARFCN | Spare | | | | Measurement Bandwidth | | | +| Octets 8-9 | E-ARFCN | | | | | | | | +| Octet 10 | E-ARFCN | Spare | | | | Measurement Bandwidth | | | +| " | " | | | | | | | | +| Octets m-(m+1) | E-ARFCN | | | | | | | | +| Octet m+2 | E-ARFCN | Spare | | | | Measurement Bandwidth | | | + +**REPORTING\_THRESHOLD:** see subclause 11.3.115. + +**REP\_QUANT:** see subclause 11.3.115. + +**Measurement\_Duration:** see subclause 11.3.115. + +**E- ARFCN:** designates a specific E-UTRA frequency for which the target RAT should continue to collect the measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from 65536 to 262143 in which bit 8 octet m is the most significant bit while bit 7 octet (m+2) is the least significant bit. + +**Measurement Bandwidth:** see subclause 11.3.115. + +### 11.3.122 eDRX Parameters + +This information element is used to indicate the eDRX cycle value the BSS is to use for determining the reachability of a MS that has enabled eDRX operation. The element coding is: + +**Table 11.3.122: eDRX Parameters IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|------------------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | eDRX Cycle Value | | | | + +The BSS uses the eDRX cycle value indicated by the eDRX Parameters IE along with the IMSI to determine the nominal paging group of a mobile station (see 3GPP TS 45.002 [48]). The eDRX cycle value is coded as specified within 3GPP TS 24.008 [11]). + +### 11.3.123 Time Until Next Paging Occasion + +This information element is used to indicate the time until the next paging occasion for a MS for which the BSS has rejected a PS-PAGING PDU received from the SGSN. The element coding is: + +**Table 11.3.123: Time Until Next Paging Occasion IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | Minutes | | | | +| octet 4 | Spare | | | | Seconds | | | | + +The BSS uses information provided by the PAGING-PS PDU to calculate the time until the next paging occasion in minutes and seconds and includes it within this IE. + +The “Minutes” field is coded as shown below. + +**Table 11.3.123.a: “Minutes” coding** + +| coding | semantic | +|--------------------------------|------------| +| 000000 | 0 minutes | +| 000001 | 1 minute | +| 000010 | 2 minutes | +| 000011 | 3 minutes | +| .... | | +| 110100 | 52 minutes | +| All other values are reserved. | | + +The “Seconds” field is coded as shown below. + +**Table 11.3.123.b: “Seconds” coding** + +| coding | semantic | +|--------------------------------|-----------------| +| 0000 0000 | 0 seconds | +| 0000 0001 | 1 second | +| 0000 0010 | 2 seconds | +| 0000 0011 | 3 seconds | +| .... | | +| 0011 1011 | 59 seconds | +| All other values are reserved. | | + +## 11.3.124 Coverage Class + +This information element is used to indicate the uplink and downlink Coverage Class associated with a given MS supporting EC operation. The element coding is: + +**Table 11.3.124.a: Coverage Class IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|----------|----------|-------------------|----------|----------|-------------------|----------| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | spare | | | DL Coverage Class | | | UL Coverage Class | | + +**UL Coverage Class:** Octet 3, bits 1 to 3, contain the value part of the uplink Coverage Class. + +**DL Coverage Class:** Octet 3, bits 4 to 6, contain the value part of the downlink Coverage Class. + +The UL Coverage Class field is coded as shown below: + +**Table 11.3.124.b: UL Coverage Class field** + +| Coding | Semantic | +|--------------------------------|---------------------| +| 000 | reserved | +| 001 | UL Coverage Class 1 | +| 010 | UL Coverage Class 2 | +| 011 | UL Coverage Class 3 | +| 100 | UL Coverage Class 4 | +| 101 | UL Coverage Class 5 | +| All other values are reserved. | | + +The DL Coverage Class field is coded as shown below: + +**Table 11.3.124.c: DL Coverage Class field** + +| Coding | Semantic | +|--------------------------------|---------------------| +| 000 | reserved | +| 001 | DL Coverage Class 1 | +| 010 | DL Coverage Class 2 | +| 011 | DL Coverage Class 3 | +| 100 | DL Coverage Class 4 | +| All other values are reserved. | | + +Spare bits are reserved and coded with zeroes. + +### 11.3.125 Paging Attempt Information + +This information element provides the BSS with paging attempt count and intended number of paging attempts information for a given paging procedure for an MS. + +The element coding is: + +**Table 11.3.125.a: Paging Attempt Information IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|------------------------------------|---|---|---|----------------------|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | PEI | Intended Number of Paging Attempts | | | | Paging Attempt Count | | | + +The Paging Attempt Count field is coded as shown below: + +**Table 11.3.125.b: Paging Attempt Count field** + +| Coding | Semantic | +|--------|--------------------------------| +| 000 | 1 st paging attempt | +| 001 | 2 nd paging attempt | +| 010 | 3 rd paging attempt | +| 011 | 4 th paging attempt | +| 100 | 5 th paging attempt | +| 101 | 6 th paging attempt | +| 110 | 7 th paging attempt | +| 111 | 8 th paging attempt | + +The Intended Number of Paging Attempts field is coded as shown below: + +**Table 11.3.125.c: Intended Number of Paging Attempts field** + +| Coding | Semantic | +|-------------------------------|---------------------------| +| 0000 | Information not available | +| 0001 | 1 page attempt | +| 0010 | 2 page attempts | +| 0011 | 3 page attempts | +| 0100 | 4 page attempts | +| 0101 | 5 page attempts | +| 0110 | 6 page attempts | +| 0111 | 7 page attempts | +| 1000 | 8 page attempts | +| All other values are reserved | | + +The PEI (Positioning Event Indicator) field is coded as shown below: + +**Table 11.3.125.d: "PEI" coding** + +| coding | Semantic | +|--------|---------------------------------| +| 0 | Positioning event not triggered | +| 1 | Positioning event triggered | + +### 11.3.126 Exception Report Flag + +This information element is included if the LLC PDU carried within the UL-UNITDATA PDU was sent by the MS using an uplink EC TBF established in response to an EC PACKET CHANNEL REQUEST message or an EC PACKET DOWNLINK ACK/NACK message including a channel request, indicating high priority (i.e. an exception report), see 3GPP TS 44.018 [25] and 3GPP TS 44.060 [22]. + +The element coding is: + +**Table 11.3.126a: Exception Report Flag IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | | | | | + +### 11.3.127 Old Routing Area Identification + +This information element provides the BSS with the Old Routing Area Identification (RAI) as reported by the MS in the initial Layer 3 message. It is used in MOCN and GWCN configurations for network sharing. + +The element coding is: + +**Table 11.3.127: Old Routing Area Identification IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octets 3-8 | Octets 3 to 8 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI | | | | | | | | + +### 11.3.128 Attach Indicator + +This information element provides the BSS with the information of an ongoing GPRS attach for a given mobile station. It is used in MOCN and GWCN configurations for network sharing. + +The element coding is: + +**Table 11.3.128: Attach Indicator IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | spare | | | | | | | | + +### 11.3.129 PLMN Identity + +The purpose of the *PLMN Identity* information element is to identify a given CN operator. It is used in MOCN and GWCN configurations for network sharing. + +The element coding is: + +**Table 11.3.129: PLMN Identity IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|-----------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | MCC dig 2 | | | | MCC dig 1 | | | | +| octet 4 | MNC dig 3 | | | | MNC dig 3 | | | | +| octet 5 | MNC dig 2 | | | | MNC dig 1 | | | | + +The MCC and MNC value fields are coded as specified within 3GPP TS 24.008 [11]. + +### 11.3.130 MME Query + +This information element provides control information for the MS Registration Enquiry procedure. The purpose of the *MME Query* IE is to request the SGSN to send a registration information enquiry to each MME that may hold the context for a given MS. It is used in MOCN and GWCN configurations for network sharing. + +The element coding is: + +**Table 11.3.130: MME Query IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------|------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2, 2a | Length Indicator | | | | | | | | +| octet 3 | spare | | | | | | | | + +### 11.3.131 SGSN Group Identity + +This information element provides the BSS with the DCN related information within the PLMN for identification of CN node as described in 23.401 [49]. + +The element coding is: + +**Table 11.3.131.a: SGSN Group Identity IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------|---------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | Choice bits for type of SGSN Group Identity | | | | | | | | +| Octet 4-5 | Null-NRI/SGSN Group ID | | | | | | | | + +The Choice bit field is coded as shown below: + +**Table 11.3.131.b: Choice bits for type of SGSN Group Identity field** + +| Coding | Semantic | +|-------------------------------|--------------------------------------| +| 00000000 | Octets 4-5 contain the Null-NRI | +| 00000001 | Octets 4-5 contain the SGSN Group ID | +| All other values are reserved | | + +**Null-NRI:** The 10 most significant bits of Octets 4 to 5 contain the Null-NRI, the remaining bits are spare. + +**SGSN Group ID:** Octets 4-5 contain the SGSN Group ID and is coded as specified in 3GPP TS 23.401 [49]. + +### 11.3.132 Additional P-TMSI + +This information element provides the BSS with the Additional P-TMSI. + +The element coding is: + +**Table 11.3.132: Additional P-TMSI IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------|-------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3-6 | Additional P-TMSI | | | | | | | | + +**Additional P-TMSI:** Octets 3-6 contain the Additional P-TMSI, see 3GPP TS 24.008 [11] + +### 11.3.133 UE Usage Type + +This information element provides the BSS with the UE Usage Type. + +The element coding is: + +**Table 11.3.133: UE Usage Type IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | UE Usage Type | | | | | | | | + +**UE Usage Type:** Octet 3 contains the UE Usage Type. + +### 11.3.134 DCN-ID + +This information element provides the SGSN with the DCN-ID, see 3GPP TS 23.401 [49] and 3GPP TS 44.060 [22]. + +The element coding is: + +**Table 11.3.133: DCN-ID IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | DCN-ID (Octet 1) | | | | | | | | +| Octet 4 | DCN-ID (Octet 2) | | | | | | | | + +**DCN-ID:** Octet 3 and 4 contains the DCN-ID and is coded as the DCN-ID field in 3GPP TS 44.060 [22]. + +### 11.3.135 Void + +### 11.3.136 Multilateration Timer + +The inclusion of this information element indicates the MTA procedure or MOTD procedure has been triggered and provides the specific timer value used by the BSS for that procedure. The element coding is: + +**Table 11.3.136: Multilateration Timer IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|-----------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | Spare | | | | MPM Timer | | | | + +The fields are coded as follows: + +**MPM Timer** (bits 1, 2 and 3 of octet 3): This field is coded according to the value part of the of the MPM Timer field defined in 3GPP TS 49.031 [24]. + +**Spare:** these bits shall be ignored by the receiver and set to zero by the sender. + +### 11.3.137 Multilateration Timing Advance + +This parameter identifies the Multilateration Timing Advance value the BSS determines to be applicable for a MS at the point when it receives a corresponding RLC Data Block containing a page response, a “MS Transmission Offset” parameter and a “MS Sync Accuracy” parameter (see 3GPP TS 44.060 [22]). + +**Table 11.3.137: Multilateration Timing Advance IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|-----------------|---|---|---------|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | spare | | MTA Granularity | | | MTA Low | | | +| octet 4 | MTA High | | | | | | | | + +The MTA Granularity and MTA fields are coded according to the value parts of the Multilateration Timing Advance information element described in 3GPP TS 49.031 [24] (i.e. not including 3GPP TS 49.031 IEI) + +### 11.3.138 MS Sync Accuracy + +This parameter identifies the downlink synchronization accuracy the MS determines to be applicable at the point of sending the RLC Data Block containing a page response, a “MS Transmission Offset” parameter and the “MS Sync Accuracy” parameter (see 3GPP TS 44.060 [22]). + +**Table 11.3.138: MS Sync Accuracy IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|------------------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | spare | | | | MS Sync Accuracy | | | | + +The MS Sync Accuracy field is coded according to the value part of the MS Sync Accuracy information element described in 3GPP TS 49.031 [24] (i.e. not including 3GPP TS 49.031 IEI). + +### 11.3.139 BTS Reception Accuracy Level + +This parameter identifies the BTS Reception Accuracy Level the BSS determines to be applicable at the point when it receives a RLC Data Block containing a page response, a “MS Transmission Offset” parameter and a “MS Sync Accuracy” parameter (see 3GPP TS 44.060 [22]). + +**Table 11.3.139: BTS Reception Accuracy Level IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|------------------------------|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | spare | | | | BTS Reception Accuracy Level | | | | + +The BTS Reception Accuracy Level field is coded according to the value part of the BTS Reception Accuracy Level information element described in 3GPP TS 49.031 [24] (i.e. not including 3GPP TS 49.031 IEI). + +### 11.3.140 Timing Advance Request (TAR) + +This parameter indicates whether or not MS specific timing advance information (“MS Transmission Offset” and “MS Sync Accuracy” parameters – see 3GPP TS 44.060 [22]) needs to be acquired. + +**Table 11.3.140.1: Timing Advance Request IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|-----| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | spare | | | | | | | TAR | + +The TAR field is coded as shown below and has a value determined by the SMLC when it triggers the Multilateration Timing Advance procedure or the MOTD procedure (see 3GPP TS 49.031 [24]): + +**Table 11.3.140.2: "TAR" coding** + +| coding | Semantic | +|--------|---------------------------------------| +| 0 | Timing Advance information not needed | +| 1 | Timing Advance information needed | + +### 11.3.141 Enhanced Coverage Additional Information + +This information element provides the BSS with the Enhanced Coverage Additional Information. + +The element coding is: + +**Table 11.3.141.a: Enhanced Coverage Additional Information** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|------| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | Spare | | | | | | | ECRR | + +The Enhanced Coverage Restriction Removed (ECRR) field is coded as shown below: + +**Table 11.3.141.b: ECRR field** + +| Coding | Semantic | +|--------|--------------------------------------------| +| 0 | Restriction on use of enhanced coverage | +| 1 | No restriction on use of enhanced coverage | + +## 11.3.142 MTA Access Security Required(MTASR) + +This parameter indicates SGSN request to MS to provide MTA Signature. + +**Table 11.3.142.1: MTA Access Security Required IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|-------| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | spare | | | | | | | MTASR | + +The MTASR field is coded as shown below and has a value determined by the SGSN. + +**Table 11.3.142.2: "MTASR" coding** + +| coding | Semantic | +|--------|--------------------------------------------| +| 0 0 | MTA Access Security not required | +| 0 1 | MTA Access Security Method requested | +| 1 0 | BSS Duplication Detection method requested | +| 1 1 | spare | + +## 11.3.143 MTA Sequence + +This parameter is provided by BSS to SGSN. The BSS obtains this parameter from SMLC. + +**Table 11.3.143.1: MTA Sequence IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|--------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | MTA Sequence (octet 1) | | | | | | | | +| octet 4 | MTA Sequence (octet 2) | | | | | | | | +| octet 5 | MTA Sequence (octet 3) | | | | | | | | +| octet 6 | MTA Sequence (octet 4) | | | | | | | | +| octet 7 | MTA Sequence (octet 5) | | | | | | | | +| octet n | MTA Sequence (octet n-2) | | | | | | | | + +## 11.3.144 MTA Signature + +This parameter is provided by BSS to SGSN. BSS obtains this parameter from SMLC. + +**Table 11.3.144.1: MTA Signature IE** + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------------------------|---|---|---|---|---|---|---| +| octet 1 | IEI | | | | | | | | +| octet 2 | Length Indicator | | | | | | | | +| octet 3 | MTA Signature (octet 1) | | | | | | | | +| octet 4 | MTA Signature (octet 2) | | | | | | | | +| octet 5 | MTA Signature (octet 3) | | | | | | | | +| octet 6 | MTA Signature (octet 4) | | | | | | | | + +## 12 List of system variables + +### 12.1 General Variables + +**Table 12.1.a: Procedure timers** + +| Timer mnemonic | Value range | Notes | Relation to other timers | +|----------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| T1 | 1 s < T1 < 30 s | Guards the (un)blocking procedures | none | +| T2 | 1 s < T2 < 120 s | Guards the reset procedure | none | +| T3 | 0,1 s < T3 < 10 s | Guards the suspend procedure | none | +| T4 | 0,1 s < T4 < 10 s | Guards the resume procedure | none | +| T5 | 1 s < T5 < 30 s | Guards the Radio Access Capability Update procedure | none | +| T6 | 0,1 s < T6 < 10 s | Guards the DOWNLOAD-BSS-PFC PDU | none | +| T7 | 0,1 s < T7 < 10 s | Guards the CREATE-BSS-PFC PDU | none | +| T8 | 0,1 s < T8 < 10 s | Guards the MODIFY-BSS-PFC PDU | none | +| T9 | Same as T3314 READY timer in 3GPP TS 24.008. Minimum 6 s | This is the Packet Flow Timer (PFT) and holds the maximum time the BSS may store a BSS PFC while no uplink data is transmitted | Cannot exceed the value of the READY timer for this MS unless READY timer is less than 6 s. | +| T10 | 0,5 s ≤ T10 < 10 s | Guards the PFC queuing procedure | T10 < T7 | +| T11 | 0,1 s < T11 < 10 s | Guards the MBMS Session Start, MBMS Session Update and MBMS Session Stop procedures | none | +| T12 | 0,5 s ≤ T12 < 10 s | Guards the PS Handover Required procedure in the BSS | none | +| T13 | 0,5 s ≤ T13 < 10 s | Guards the PS Handover Request procedure in the SGSN | none | +| T14 | 0,5 s ≤ T14 < 10 s | Guards the PS Handover Complete procedure in the SGSN | none | +| T15 | O&M | Overload timer in BSS, see sub-clause 8.6.1 | T15 < T16 | +| T16 | O&M | Overload timer in BSS, see sub-clause 8.6.1 | none | + +**Table 12.1.b: Procedure retry counters** + +| Retry mnemonic | Retry value | Notes | +|-------------------------------------|-------------|-------| +| BVC-BLOCK-RETRIES | 3 | none | +| BVC-UNBLOCK-RETRIES | 3 | none | +| BVC-RESET-RETRIES | 3 | none | +| SUSPEND-RETRIES | 3 | none | +| RESUME-RETRIES | 3 | none | +| RA-CAPABILITY-UPDATE-RETRIES | 3 | none | +| DOWNLOAD-BSS-PFC-RETRIES | 3 | none | +| CREATE-BSS-PFC-RETRIES | 3 | none | +| MODIFY-BSS-PFC-RETRIES | 3 | none | +| MBMS-SESSION-START-REQUEST-RETRIES | 3 | none | +| MBMS-SESSION-STOP-REQUEST-RETRIES | 3 | none | +| MBMS-SESSION-UPDATE-REQUEST-RETRIES | 3 | none | + +## 12.2 Flow control variables + +**Table 12.2: Flow control variables** + +| Variable mnemonic | Value range | Notes | Relation to other variables | +|-------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------| +| Th | $5 \text{ s} < \text{Th} < 6 \text{ 000 s}$ | Interval after Flow-Control-MS before SGSN may use SGSN generated Bmax and R | none | +| C | $1 \text{ s} < \text{C} < 10 \text{ s}$ | Minimum interval between sending of subsequent Flow Control PDUs for a given BVC or MS or PFC | $\text{C} < \text{Th}$ | +| Tf | $5 \text{ s} < \text{Tf} < 6 \text{ 000 s}$ | Interval after Flow-Control-PFC before SGSN may use SGSN generated Bmax and R | $\text{Tf} > \text{C}$ | + +## Annex A (informative): Change history + +| Date | TSG# | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|--------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------|--------| +| 2015-12 | | - | - | - | | Generation of Rel-13 version based on v12.4.0 | 13.0.0 | +| | GP-68 | GP-151194 | 0418 | 4 | | Introduction of Power Efficient Operation (Rel-13) | 13.0.0 | +| | GP-68 | GP-151121 | 0419 | 1 | | Enhancements to CS/PS coordination | 13.0.0 | +| 2016-02 | GP-69 | GP-160082 | 0424 | | | Removal of enhancements to CS/PS coordination in shared networks | 13.1.0 | +| | GP-69 | GP-160166 | 0422 | 3 | | Miscellaneous corrections to eDRX | 13.1.0 | +| | GP-69 | GP-160164 | 0421 | 5 | | Introduction of EC-EGPRS | 13.1.0 | +| 2016-06 | GP-70 | GP-160407 | 0425 | 1 | F | Miscellaneous corrections to eDRX_GSM | 13.2.0 | +| 2016-06 | GP-70 | GP-160402 | 0419 | 2 | B | Enhancements to CS/PS coordination | 13.2.0 | +| 2016-09 | RP-73 | RP-161392 | 0428 | 1 | F | Miscellaneous EC-GSM-IoT Changes | 13.3.0 | +| 2016-00 | RP-73 | RP-161392 | 0429 | 5 | F | Miscellaneous corrections to EC-GSM-IoT | 13.3.0 | +| 2016-09 | RP-73 | RP-161391 | 0427 | 2 | B | Introduction of Dedicated Core Networks in GERAN | 14.0.0 | +| 2016-12 | RP-74 | RP-162069 | 0432 | 2 | A | Miscellaneous corrections | 14.1.0 | +| 2017-03 | RP-75 | RP-170064 | 0434 | 1 | A | Clarifying BSS Operation for EC-GSM | 14.2.0 | +| 2017-06 | RP-76 | RP-170923 | 0430 | 6 | B | Introduction of Multilateration | 14.3.0 | +| 2017-06 | RP-76 | RP-170923 | 0435 | 1 | B | Introduction of PS domain transport for Multilateration Timing Advance information transfer | 14.3.0 | +| 2017-06 | RP-76 | RP-170924 | 0436 | 4 | B | Introduction of new UL coverage class CC5 for UL MCL improvement | 14.3.0 | +| 2017-06 | RP-76 | RP-170926 | 0437 | - | F | Addition of DECOR rerouting cause code | 14.3.0 | +| 2017-06 | RP-76 | RP-170925 | 0438 | 1 | F | Introduction of enhanced DECOR for GERAN | 14.3.0 | +| 2017-06 | RP-76 | RP-170927 | 0440 | 1 | A | Removing Unnecessary References to eDRX for SGSN Paging Procedure | 14.3.0 | +| 2017-09 | RP-77 | RP-171594 | 0441 | 1 | F | Correction of the BTS Reception Accuracy Level IE | 14.4.0 | +| 2018-06 | RP-80 | RP-180825 | 0443 | 2 | F | Introduction of Restricted Use of Enhanced Coverage | 14.5.0 | +| 2018-06 | RP-80 | RP-180822 | 0444 | 1 | B | Security Enhancement for MTA in network configuration without LLC security | 15.0.0 | +| 2018-06 | RP-80 | RP-180821 | 0445 | 1 | B | Energy efficiency enhancements for EC-GSM-IoT MS in idle mode | 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/48_series/48020/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-16/48_series/48020/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3627b9a0768a807e0499ea70b095f13f1e841a5 --- /dev/null +++ b/marked/Rel-16/48_series/48020/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de12bb6efabc11da442821825cb90818b07b210bb813d1e52d2519b1c13ebda9 +size 67630 diff --git a/marked/Rel-16/48_series/48020/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/48_series/48020/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bf1db267eb9a1d64f4eb819e7a840013fd985f9 --- /dev/null +++ b/marked/Rel-16/48_series/48020/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e3b53bfad7239c38018b59f3d48e3a803abd62f95de1c58adc201172aca7cf6 +size 38284 diff --git a/marked/Rel-16/48_series/48020/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-16/48_series/48020/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db60d30fb2854897ff762daee0e1b26894fb0291 --- /dev/null +++ b/marked/Rel-16/48_series/48020/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:348b4bac190c67efa111a502bda70fcb68130a306cf4cfff21547f543fde9d53 +size 89143 diff --git a/marked/Rel-16/48_series/48020/raw.md b/marked/Rel-16/48_series/48020/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ae2b4bf05a967498ce7b7aa91a02c0de675d64cf --- /dev/null +++ b/marked/Rel-16/48_series/48020/raw.md @@ -0,0 +1,1197 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References, abbreviations and definitions ..... | 6 | +| 2.1 References..... | 6 | +| 2.2 Abbreviations..... | 7 | +| 2.3 Definitions..... | 7 | +| 3 General approach ..... | 7 | +| 4 The RA0 Function..... | 7 | +| 5 The RA1 Function..... | 7 | +| 5a The RA1' Function..... | 8 | +| 6 The RA1" Function ..... | 8 | +| 6.1 Rate adaptation of 48 kbit/s user rates with DTE/DCE status to 64 kbit/s ..... | 9 | +| 6.2 Rate adaptation of 56 kbit/s user rate to 64 kbit/s..... | 9 | +| 7 Split/Combine and Padding Functions..... | 9 | +| 7.1 Data Frame distribution into the channels by the Split/Combine function..... | 9 | +| 7.2 Substream numbering ..... | 9 | +| 7.3 Initial Substream Synchronisation for Transparent Services..... | 9 | +| 7.4 Frame Synchronisation and Action on loss of Synchronisation ..... | 9 | +| 7.5 Network Independent Clocking ..... | 9 | +| 7.6 Padding ..... | 9 | +| 8 The EDGE Multiplexing Function..... | 10 | +| 8.1 Transparent services..... | 10 | +| 8.2 Non-Transparent services ..... | 10 | +| 9 The Functions RA1/RA1' and RA1'/RA1" ..... | 11 | +| 9.1 Radio Interface rate of 12 kbit/s..... | 11 | +| 9.2 Radio Interface rate of 6 kbit/s..... | 11 | +| 9.3 Radio Interface rate of 3.6 kbit/s..... | 11 | +| 9.4 Synchronisation..... | 11 | +| 9.5 Idle frames ..... | 11 | +| 10 The Functions RA1'/RAA' and RA1'/RAA" ..... | 12 | +| 10.1 Radio Interface rate of 14,5 kbit/s..... | 12 | +| 10.2 Synchronisation..... | 12 | +| 10.3 Idle frames..... | 12 | +| 11 THE RAA' FUNCTION ..... | 12 | +| 11.1 Coding of A-TRAU frame ..... | 12 | +| 11.2 Framing Pattern Substitution in A-TRAU frame ..... | 13 | +| 11.2.1 FPS encoding..... | 13 | +| 11.3 A-TRAU Synchronisation Pattern ..... | 15 | +| 12 THE RAA" FUNCTION..... | 15 | +| 12a The RAE Function ..... | 16 | +| 13 The RA2 Function..... | 16 | +| 14 The A-interface Multiplexing Function ..... | 17 | +| 15 Support of non-transparent bearer services in A/Gb mode..... | 17 | +| 15.1 TCH/F9.6 and TCH/F4.8 kbit/s channel codings..... | 17 | +| 15.1.1 Alignment..... | 18 | +| 15.1.2 Support of Discontinuous Transmission (DTX) ..... | 18 | +| 15.1.3 Order of Transmission..... | 18 | +| 15.2 TCH/F14.4, TCH/F28.8, and TCH/F43.2 channel codings ..... | 19 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------|-----------| +| 15.2.1 | Alignment..... | 19 | +| 15.2.2 | Support of Discontinuous Transmission (DTX) ..... | 19 | +| 15a | Support of non-transparent bearer services in Iu mode ..... | 20 | +| 16 | Support of transparent bearer services in A/Gb mode ..... | 20 | +| 16.1 | TCH/F9.6 and TCH/F4.8 channel codings..... | 20 | +| 16.1.1 | User rate adaptation on the A interface, AIUR less than or equal to 38,4 kbit/s ..... | 20 | +| 16.1.2 | User rate Adaptation on the A-interface, AIUR greater than 38,4 kbit/s..... | 21 | +| 16.1.3 | Relation between AIUR and the number of channels ..... | 21 | +| 16.1.4 | Handling of status bits X, SA, SB..... | 21 | +| 16.1.5 | Handling of bits E1 to E7 ..... | 21 | +| 16.2 | TCH/F14.4, TCH/F28.8, and TCH/F32.0 channel codings ..... | 22 | +| 16.2.1 | User rate adaptation on the A interface, AIUR less than or equal to 56 kbit/s ..... | 22 | +| 16.2.2 | User Rate Adaptation on the A-interface, AIUR greater than 56 kbit/s ..... | 22 | +| 16.2.3 | Relation between AIUR and the number of channels ..... | 22 | +| 16.2.4 | Handling of status bits X and SB ..... | 22 | +| 16a | Support of transparent bearer services in Iu mode..... | 23 | +| 17 | Frame Formats ..... | 23 | +| Annex A (informative): | Frame Pattern Substitution..... | 28 | +| A.1 | Special cases ..... | 28 | +| A.2 | False Z sequence detection ..... | 29 | +| Annex B (informative): | Change History..... | 31 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it is 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 rate adaptation functions to be used in PLMN Base Station Systems (BSS) transcoders and IWF + +- for adapting radio interface data rates to the 64 kbit/s used at the A-interface in A/Gb mode and +- for adapting radio interface data rates to the Iu interface in GERAN Iu mode in accordance with 3GPP TS 43.010. + +The number of Base Station System - Mobile-services Switching Centre (BSS - MSC) traffic channels supporting data rate adaptation may be limited. In this case some channels may not support data rate adaptation. Those that do, shall conform to this specification. + +NOTE: This specification should be considered together with 3GPP TS 44.021 to give a complete description of PLMN rate adaptation. + +# --- 2 References, abbreviations and definitions + +## 2.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] 3GPP TR 21.905: " Vocabulary for 3GPP specifications ". +- [2] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD) - Stage1" +- [3] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types". +- [4] 3GPP TS 23.034: "High Speed Circuit Switched Data (HSCSD) - Stage2". +- [5] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [6] 3GPP TS 24.022: "Radio Link Protocol (RLP) for Circuit Switched Bearer and Teleservices". +- [7] 3GPP TS 45.003: "Channel coding". +- [8] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [9] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". +- [10] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [11] ITU-T Recommendation V.110: "Support of data terminal equipment's (DTEs) with V-Series interfaces by an integrated services digital network". +- [12] ITU-T Recommendation I.460:-Multiplexing, rate adaption and support of existing interfaces. +- [13] 3GPP TS 48.060: "In-band control of remote transcoders and rate adaptors for full rate traffic channels" + +[14] + +3GPP TS 25.415: "UTRAN Iu Interface user plane protocols". + +## 2.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|----------------------------| +| FPS | Frame Pattern Substitution | +| FSI | Frame Start Identifier | +| ZSP | Zero Sequence Position | + +## 2.3 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Substream:** Stream of data with explicit or implicit numbering between splitter and combine functions. + +**Channel:** A physical full rate channel on the radio interface (TCH/F) independent of the contents. + +**A interface circuit:** The 8 bits that constitute one 64 kbps circuit on the A interface. + +**A interface subcircuit:** One specific bit position or one specific pair of bit positions within the A interface circuit. + +**EDGE channel:** A general term referring to channels based on 8PSK modulation; i.e. TCH/F28.8, TCH/F32.0, and TCH/F43.2. + +# 3 General approach + +3GPP TS 43.010 (clause 6) defines the PLMN connection types necessary to support the data and telematic services in a PLMN operating in A/Gb mode or GERAN Iu mode. + +Within the BSS, transcoder and IWF, there are several data rate adaptation functions which are combined as shown in 3GPP TS 43.010 as part of a connection type. + +These functions are RA0, RA1, RA1/RA1', RA1", RA1'/RA1", RA1'/RAA", RA1', RAA", RA1'/RAA', RAA', RAE and RA2. The RA2 function is equivalent to that described in ITU-T Recommendation V.110. In addition, splitting/combining, padding and inband numbering functions as defined in 3GPP TS 44.021 and multiplexing as defined herein are used in cases where more than one channel is allowed. + +The RA1/RA1', RA1'/RA1", RA1'/RAA" and RA1'/RAA' are relay functions used as indicated in 3GPP TS 43.010. + +The BSS uses the information contained in the ASSIGNMENT REQUEST message on the A-interface (see 3GPP TS 48.008) to set the "E bits" and to map the "D bits" as shown below, as well as to choose the correct channel coding. + +# 4 The RA0 Function + +The RA0 function is specified in 3GPP TS 44.021. + +# 5 The RA1 Function + +This function shall be used to adapt between the synchronous user rates, or the output of the RA0 function or Split/Combine function and the intermediate rate of 8, 16, 32 or 64 kbit/s. + +For multislot operations RA1 applies per substream. RA1 applies only if TCH/F4.8 or TCH/F9.6 is used for user rates up to 38,4 kbit/s. The RA1 function is only applicable for A/Gb mode. + +| Synchronous user rate | Intermediate rate | +|------------------------------|--------------------------| +| ≤ 2,4 kbit/s | 8 kbit/s | +| 4,8 kbit/s | 8 kbit/s | +| 9,6 kbit/s | 16 kbit/s | +| 14,4 kbit/s | 32 kbit/s | +| 19,2 kbit/s | 32 kbit/s | +| 28,8 kbit/s | 64 kbit/s | +| 38,4 kbit/s | 64 kbit/s | + +An ITU-T V.110 80 bits frame is constructed using the user data bits received (from the RA0 in the asynchronous case). + +Adaptation of 600 bit/s to 8Kbit/s is performed by 8 times consecutive duplication of each user data bit. (Figure 11) + +Adaptation of 1200 bit/s to 8 Kbit/s is performed by 4 times consecutive duplication of each user data bit. (Figure 10) + +Adaptation of 2400 bit/s to 8kbit/s is performed by 2 times consecutive duplication of each user data bit. (Figure 9) + +Adaptation of 4800 bit/s to 8 Kbit/s is performed by transmitting the bit stream with no duplication. (Figure 7) + +Adaptation of 9600 bit/s to 16 Kbit/s is performed by transmitting the bit stream with no duplication (the emitting period is halved with respect to the 4800 bit/s case). (Figure 7) + +Adaptation of 14400 bit/s to 32 Kbit/s is performed as for 3600 bit/s to 8 kbit/s (the emitting period is divided by four with respect to the 3600 bit/s case). (Adaptation of 3600 bit/s to 8 kbit/s is performed by transmitting the bit stream with no duplication.) (Figure 8) + +Adaptation of 19200 bit/s to 32 Kbit/s is performed as for 4800 bit/s to 8 kbit/s (the emitting period is divided by four with respect to the 4800 bit/s case). (Figure 7) + +Adaptation of 28800 bit/s to 64 Kbit/s is performed as for 3600 bit/s to 8 kbit/s (the emitting period is divided by eight with respect to the 3600 bit/s case). (Figure 8) + +Adaptation of 38400 bit/s to 64 Kbit/s is performed as for 4800 bit/s 8 kbit/s (the emitting period is divided by eight with respect to the 4800 bit/s case). (Figure 7) + +The ITU-T V.110 80 bit frames shown in Figures 7 and 8 are used. The meaning of the bits is specified in 3GPP TS 44.021. + +# 5a The RA1' Function + +The RA1' function is used to adapt between the synchronous data rates and the radio interface rates, i.e. it maps the data provided in the Iu UP SDUs into modified V.110 60 bit frame structure. It is specified in 3GPP TS 44.021. + +In the BSS, the RA1' function is only applicable in GERAN Iu mode if TCH/F9.6 channel coding is used. + +# 6 The RA1" Function + +The RA1" function shall be used for converting between synchronous user rates of 48 and 56 kbit/s and the 'intermediate' rate of 64 kbit/s in A/Gb mode. + +Note, RA1" is a 3GPP-specific term which is used for the one-step adaptation of 48 and 56 kbit/s rates into 64 kbit/s as specified in ITU-T V.110. For the purposes of 3GPP specifications the term 'intermediate rate' is used for the resulting 64 kbit/s rate although this is not done in ITU-T V.110. + +## 6.1 Rate adaptation of 48 kbit/s user rates with DTE/DCE status to 64 kbit/s + +An ITU-T V.110 32 bits frame is constructed using the user data bits received. + +The ITU-T V.110 32 bit frame shown in Figure 12 is used. The D bits are used for conveying the user data and the S and X bits are used for conveying channel control information according 3GPP TS 27.001. The order of transmission of the 32 bit frame is from left to right and top to bottom. + +## 6.2 Rate adaptation of 56 kbit/s user rate to 64 kbit/s + +An ITU-T V.110 64 bits frame is constructed using the user data bits received. + +The ITU-T V.110 64 bit frame shown in figure 13 is used. The D bits are used for conveying the user data. + +The order of transmission of the 64 bit frame is from left to right and top to bottom. + +# --- 7 Split/Combine and Padding Functions + +The Split/Combine-function in the IWF shall be used in cases when up to and including 4 substreams are used in A/Gb mode. + +The Split/Combine-function in the BSS shall be used only when more than four substreams are used in A/Gb mode. + +The Split/Combine-function is always used in the BSS if the BSS uses more than 1 substream in GERAN Iu mode. + +## 7.1 Data Frame distribution into the channels by the Split/Combine function + +Described in 3GPP TS 44.021. + +## 7.2 Substream numbering + +Described in 3GPP TS 44.021. + +## 7.3 Initial Substream Synchronisation for Transparent Services + +Described in 3GPP TS 44.021. + +## 7.4 Frame Synchronisation and Action on loss of Synchronisation + +When in the IWF, the Split/Combine function is responsible for controlling the initial frame synchronisation procedure and re-synchronisation procedure as described in 3GPP TS 29.007. + +## 7.5 Network Independent Clocking + +NIC is specified in 3GPP TS 44.021. + +## 7.6 Padding + +Padding is specified in 3GPP TS 44.021. + +# --- 8 The EDGE Multiplexing Function + +In EDGE configurations where the number of radio interface channels and number of channels or substreams used between BTS and MSC do not match, a multiplexing function described below shall be used at BTS to perform data multiplexing/demultiplexing between the radio interface and network channel configurations. A similar function shall be used also at MS as described in 44.021. + +The EDGE multiplexing function is located between the radio interface and RA1'/RAA' function. + +## 8.1 Transparent services + +TCH/F28.8; + +### Uplink direction + +Refer to the description of corresponding downlink procedures in 3GPP TS 44.021. Two TCH/F14.4 substreams are forwarded towards the MSC as in a $2 \times$ TCH/F14.4 multislot connection. + +### Downlink direction + +The multiplexing function combines the data received through the two TCH/F14.4 substreams into the 29.0 kbit/s radio interface channel. Refer to the description of corresponding uplink procedures in 3GPP TS 44.021. + +TCH/F32.0 + +### Uplink direction + +The multiplexing function maps the data received from the radio interface into one 64 kbit/s channel so that data carried by timeslot $a$ ( $0 \leq a \leq 6$ ) precedes data carried by timeslot $a+n$ ( $1 \leq a+n \leq 7$ ) — the timeslots belonging to one TDMA-frame. + +### Downlink direction + +The multiplexing function distributes the data received from the 64 kbit/s channel into two 32.0 kbit/s radio interface channels so that 640-bit data blocks are allocated to timeslots $a$ ( $0 \leq a \leq 6$ ) and $a+n$ ( $1 \leq a+n \leq 7$ ). In the datastream, data carried by timeslot $a$ precedes data carried by timeslot $a+n$ of the same TDMA-frame. + +## 8.2 Non-Transparent services + +TCH/F28.8; + +### Uplink direction + +The multiplexing function demultiplexes the data received through the 29.0 kbit/s radio interface channel into two TCH/F14.4 substreams. Two 290-bit blocks carrying the two halves of one RLP frame belong to the same substream. Refer to the corresponding downlink procedures in 3GPP TS 44.021. + +### Downlink direction + +The multiplexing function multiplexes the 290-bit blocks received through two TCH/F14.4 substreams into the 29.0 kbit/s radio interface channel. Refer to the corresponding uplink procedures in 3GPP TS 44.021. + +TCH/F43.2; + +### Uplink direction + +The multiplexing function demultiplexes the data received through the 43.5 kbit/s radio interface channel into three TCH/F14.4 substreams. Two 290-bit blocks carrying the two halves of one RLP frame belong to the same substream. Refer to the corresponding downlink procedures in 3GPP TS 44.021. + +### Downlink direction + +The multiplexing function multiplexes the 290-bit blocks received through three TCH/F14.4 substreams into the 43.5 kbit/s radio interface channel. Refer to the corresponding uplink procedures in 3GPP TS 44.021. + +# 9 The Functions RA1/RA1' and RA1'/RA1" + +These functions only apply for A/Gb mode. + +For AIURs less than or equal to 38,4 kbit/s, the RA1/RA1' function in the BSS shall be applied on each of the n substreams and there are no significant differences between the single slot case and the multislot case. For AIURs less than or equal to 38,4 kbit/s RA1/RA1' is as specified in 3GPP TS 44.021 for the single slot case. + +For AIURs of 48 kbit/s, 56 kbit/s and 64 kbit/s, RA1'/RA1" shall be applied as specified in 3GPP TS 44.021. + +The table 1 gives a relation between the AIUR, channel coding and number of substreams. As an example from table 1: The wanted AIUR is 28,8 kbit/s, the number of substreams needed to support this rate is 3. Each individual substream shall be rate adapted as in the single slot case. + +**Table 1: Relationship between AIUR, channel coding and number of channels** + +| AIUR | Multislot intermediate rate 8 kbps | | Multislot intermediate rate of 16 kbps | | +|-------------|------------------------------------|-----------------|----------------------------------------|-----------------| +| | Transparent | Non-transparent | Transparent | Non-transparent | +| ≤2,4 kbit/s | 1 | N/A | N/A | N/A | +| 4,8 kbit/s | 1 | 1 | N/A | N/A | +| 9,6 kbit/s | 2 | 2 | 1 | 1 | +| 14,4 kbit/s | 3 | 3 | 2 | N/A | +| 19,2 kbit/s | 4 | 4 | 2 | 2 | +| 28,8 kbit/s | N/A | N/A | 3 | 3 | +| 38,4 kbit/s | N/A | N/A | 4 | 4 | +| 48 kbit/s | N/A | N/A | 5 | N/A | +| 56 kbit/s | N/A | N/A | 5 | N/A | +| 64 kbit/s | N/A | N/A | 6 | N/A | + +## 9.1 Radio Interface rate of 12 kbit/s + +Described in 3GPP TS 44.021. + +## 9.2 Radio Interface rate of 6 kbit/s + +Described in 3GPP TS 44.021. + +## 9.3 Radio Interface rate of 3.6 kbit/s + +Described in 3GPP TS 44.021. + +## 9.4 Synchronisation + +Refer to 3GPP TS 44.021. + +## 9.5 Idle frames + +Refer to 3GPP TS 44.021 + +# 10 The Functions RA1'/RAA' and RA1'/RAA" + +The RA1'/RAA' shall be applied only when TCH/F14.4, TCH/F28.8, or TCH/F43.2 channel coding is used. The RA1'/RAA' converts 290-bit blocks from the channel coder or EDGE multiplexing function into E-TRAU frames and vice versa. The format of E-TRAU frame is specified in 3GPP TS 48.060. + +The RA1'/RAA' function in the BSS shall be applied on each of the n substreams and there are no significant differences between the single slot case and the multislots case. + +For the AIURs of 64 kbit/s, RA1'/RAA" shall be applied as specified in 3GPP TS 44.021. This function converts 290-bit blocks from the channel coder directly into the synchronous 64 kbit/s data stream, an E-TRAU frame is not created in this case. + +The table 2 gives a relation between the AIUR, channel coding and number of substreams. As an example from table 2 : The wanted AIUR is 28,8 kbit/s, the number of substreams needed to support this rate is 2. Each individual substream shall be rate adapted as in the single slot case. + +**Table 2 Relationship between AIUR, channel coding and number of channels.** + +| AIUR | Transparent | Non-transparent | +|-------------|-------------|-----------------| +| 14,4 kbit/s | 1 | 1 | +| 28,8 kbit/s | 2 | 2 | +| 38,4 kbit/s | 3 | N/A | +| 43,2 kbit/s | N/A | 3 | +| 48 kbit/s | 4 | N/A | +| 56 kbit/s | 4 | N/A | +| 57,6 kbit/s | N/A | 4 | +| 64 kbit/s | 5 | N/A | + +## 10.1 Radio Interface rate of 14,5 kbit/s + +See 3GPP TS 48.060. + +## 10.2 Synchronisation + +See 3GPP TS 48.060. + +## 10.3 Idle frames + +See 3GPP TS 48.060. + +# 11 THE RAA' FUNCTION + +The RAA' function shall be applied only when TCH/F14.4, TCH/F28.8, or TCH/F43.2 channels are used. + +The RAA' converts E-TRAU frame into A-TRAU frame and vice versa. + +The format of the E-TRAU frame is specified in 3GPP TS 48.060. + +## 11.1 Coding of A-TRAU frame + +The format of the A-TRAU frame is given in Figure 5. + +An A-TRAU frame carries eight 36 bit-data frames. + +**C Bits** + +**Table 3** + +| C1 | C2 | C3 | C4 | Date Rate | +|----|----|----|----|---------------------------------------| +| 0 | 1 | 1 | 1 | 14.4 kbit/s | +| 0 | 1 | 1 | 0 | 14.4 kbit/s idle
(IWF to BSS only) | + +**Table 4** + +| C5 | BSS to IWF
Frame Type
note 1 | IWF to BSS
UFE (Uplink Frame Error) | +|----|------------------------------------|----------------------------------------| +| 1 | idle | framing error | +| 0 | data | no framing error | + +NOTE 1: Bit C5 corresponds to bit C6 of the E-TRAU frame as defined in 3GPP TS 48.060. + +### M Bits + +### Transparent data + +M1 and M2 are as defined in 3GPP TS 44.021. + +### Non transparent data + +See subclause 15.2 of the present document. + +### Z bits + +Bits Zi are used for Framing Pattern Substitution. + +See subclause 11.2. + +## 11.2 Framing Pattern Substitution in A-TRAU frame + +The Framing Pattern Substitution is used in each of the eight 36 bit data fields of the A-TRAU frame (see Figure 5) to avoid transmitting a sequence of eight zeroes (called Z sequence in the following). + +The purposes of FPS is to avoid erroneous synchronisation to the A-TRAU due to sixteen zeroes occurring accidentally in the data bits and to avoid erroneous synchronisation to V.110. The synchronisation pattern of two consecutive V.110 frames cannot be found within a stream of A TRAU frames. + +### 11.2.1 FPS encoding + +A Zero Sequence Position (ZSP) field is used to account for the occurrence of eight zeroes in the 36 bit data field. + +NOTE: A sequence of eight zeroes is considered as a block (e.g. a stream of eleven consecutive zeroes produces only one ZSP and not four ZSPs). + +The ZSP field is defined as follows: + +**Table 5** + +| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +|---|---|----|----|----|----|----|---| +| 1 | C | A0 | A1 | A2 | A3 | A4 | 1 | + +The meaning of the different bits of the ZSP field is : + +C : Continuation bit. '0' means that there is another ZSP in the data field. '1' means that there is no other ZSP. + +A0-A4 :address of the next Z sequence (eight zeroes) to be inserted. The address '00001' corresponds to the bit D1, the value '11101' to the bit D29, (A0 is the msb, A4 is the lsb). + +NOTE: a Z sequence substitution cannot occur at bit D30..D36 (as it is 8 bit long) + +1 : locking bit prevent the false occurrence of a Z sequence. + +The Framing Pattern Substitution is applied in each of the eight 36 bit data field (see Figure 5). + +Bit \$Z\_i\$ indicates whether FPS is used in the \$i\$th 36 bit data field (\$i=1\$ to 8). The coding of the \$Z\_i\$ bit is the following: + +**Table 6** + +| \$Z_i\$ (\$i=1..8\$) | meaning | +|----------------------|---------------------------| +| 1 | no substitution | +| 0 | at least one substitution | + +If \$Z\_i\$ bit indicates no substitution, the output data bits of FPS are equal to the input data bits. + +If \$Z\_i\$ indicates at least one substitution, the bits D1-D8 contain the first ZSP. + +The following description indicates the general operating procedures for FPS. It is not meant to indicate a required implementation of the encoding procedure. + +![Figure 1: Diagram illustrating the Framing Pattern Substitution (FPS) process in four steps. Step 1 shows an input bit stream with data blocks D1-D4 and Z sequences Zseq1-Zseq3 at positions a1, a2, a3. Step 2 shows the extraction of addresses and data blocks. Step 3 shows the formation of ZSP blocks with continuation, address, and locking bits. Step 4 shows the final output stream assembly.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +The diagram illustrates the FPS process in four steps: + +- Step 1:** Shows the input bit stream with bit positions 1, \$a\_1\$, \$a\_2\$, and \$a\_3\$ marked. The stream contains data blocks D1, D2, D3, and D4, with Z sequences \$Zseq\_1\$, \$Zseq\_2\$, and \$Zseq\_3\$ identified between them. +- Step 2:** The process identifies the addresses of the Z sequences (\$a\_1, a\_2, a\_3\$) and the data blocks without Z sequences (D1, D2, D3, D4). +- Step 3:** The ZSP (Z Sequence Pattern) entries are created for each identified Z sequence address. Each entry consists of a Continuation Bit, the next Z seq address, and a Locking bit. + +| | | | | | +|--------------|---|---|---------|---| +| \$ZSP(a_1)\$ | = | 0 | \$a_1\$ | 1 | +| \$ZSP(a_2)\$ | = | 0 | \$a_2\$ | 1 | +| \$ZSP(a_3)\$ | = | 1 | \$a_3\$ | 1 | + +Continuation Bit → 0/1 +next Z seq address → \$a\_n\$ +Locking bit → 1 +- Step 4:** The final output stream is generated, starting with the \$Z\_i\$ bit, followed by the ZSP entries (\$ZSP(a\_1)\$, \$ZSP(a\_2)\$, \$ZSP(a\_3)\$), and the original data blocks (D1, D2, D3, D4). + +Figure 1: Diagram illustrating the Framing Pattern Substitution (FPS) process in four steps. Step 1 shows an input bit stream with data blocks D1-D4 and Z sequences Zseq1-Zseq3 at positions a1, a2, a3. Step 2 shows the extraction of addresses and data blocks. Step 3 shows the formation of ZSP blocks with continuation, address, and locking bits. Step 4 shows the final output stream assembly. + +**Figure 1** + +#### Step 1: + +The input 36 bit sub frame is considered as a bit stream in which the bits are numbered from 1 to 36. + +This bit stream contains 0, 1 or several Z sequences, (\$Zseq\_1\$ to \$Zseq\_3\$ on the figure) + +The Z sequence is a sequence of 8 consecutive zeroes : '0000 0000' + +#### Step 2: + +Starting from this bit stream, two lists are built up : + +2-a : the 'a' list which contains the address of the first bit of each Z sequences. + +2-d : the 'd' list which contains all the data blocks which do not have the Z sequence. + +#### Step 3: + +The 'a' list is transformed so as to build the ZSP list. Each ZSP element is used to indicate: + +at which address is the next Z sequence of the message + +if yet another ZSP element is found at this address (link element) + +#### Step 4: + +The output 37 bit sub frame is built from: + +the Zi field which indicates whether the original message has been transformed or not with this technique. In the example given in Figure 1, Zi shall be set to '0' to indicate that at least one FPS has occurred. + +the ZSP and D elements interleaved. + +As the ZSP elements have exactly the same length as the Z sequence, the sub frame length is only increased by one (the Zi bit), whatever the number of frame pattern substitutions may be. + +For special cases, refer to annex A. + +## 11.3 A-TRAU Synchronisation Pattern + +The frame synchronisation is obtained by means of the first two octets in each frame, with all bits coded binary "0" and the first bit in octet no 2 coded binary "1". The following 17 bit alignment pattern is used to achieve frame synchronisation: + +| | | | | | | | | +|----------|----------|----------|---------|---------|---------|---------|---------| +| 00000000 | 00000000 | 1XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | +| XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | +| XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | +| XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | +| XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | XXXXXXX | + +# 12 THE RAA" FUNCTION + +On the IWF side of the A interface, the RAA" function shall convert between the A-TRAU format and a synchronous stream. FPS shall be performed by this function as well, see subclause 11.2. In transparent operation, the RAA" function shall handle the M1 and M2 bits as specified for the RAI' function in 3GPP TS 44.021. + +In non-transparent operation, the RAA" function shall map between the A-TRAU format and 290 bit blocks consisting of M1, M2 and 288 bits making up half of an RLP frame, see subclause 15.2 of the present document. + +# 12a The RAE Function + +On the BSS side of the Iu interface, the RAE function shall convert in GERAN Iu mode between the E-TRAU format (3GPP TS 48.060) and a synchronous stream, i.e. the data in the payload of the Iu UP SDUs. It is the subsequent execution of the rate adaptation functions RAA' and RAA". + +It is used in the case of TCH/F14.4 and user rates less than 56 kbit/s. + +The RAE function maps the data from the payload of the Iu UP SDUs directly into E-TRAU frames. It is not necessary to create the A-TRAU format that is the exchange format between RAA' and RAA". + +It shall perform the FPS (Frame Pattern Substitution) as specified in subclause 11.2. + +In transparent operations, The RAE function shall handle the M1 and M2 bits as specified for the RA1' function in 3GPP TS 44.021. + +In non-transparent operations, the payload of the Iu UP SDU has a size of 576 bit and contains one RLP frame. This shall be mapped to two E-TRAU frames each of them consisting of + +- 288 data bits making up half of an RLP frame, +- the bits M1 and M2 that shall be used as specified in subclause 15.2 and +- the control bits that shall be used as specified in 3GPP TS 48.060. + +# 13 The RA2 Function + +The RA2 function shall be applied only for single slot operations in A/Gb mode. For multislot operations the A-interface Multiplexing Function applies (see clause 14). + +This procedure is based on the RA2 function as specified in ITU-T V.110. It shall be used to rate adapt to/from the intermediate rates of 8, 16 or 32 kbit/s from/to the 64 kbit/s rate used at the A-interface. + +**Table 6a** + +| Intermediate rate | Rate at the A-interface | +|-------------------|-------------------------| +| 8 kbit/s | 64 kbit/s | +| 16 kbit/s | 64 kbit/s | +| 32 kbit/s | 64 kbit/s | +| 64 kbit/s | 64 kbit/s | + +For the intermediate and user data rate of 64 kbit/s, the RA2 transmits the bit stream over the A-interface as it is. + +It considers the 64 kbit/s stream over the A interface to consist of octets, bits 1 through 8, with bit 1 being transmitted first. + +The procedure requires that: + +- i) The 8 kbit/s stream occupies bit position 1; +- ii) The 16 kbit/s bitstream occupies bit positions (1,2); +- iii) The 32 kbit/s bitstream occupies bit positions (1,2,3,4) ; +- iv) The order of transmission of the bits of the substrate stream is identical before and after rate adaptation. +- v) All unused bits in the 64 kbit/s stream are set to binary "1". + +# 14 The A-interface Multiplexing Function + +The multiplexing function shall be applied only for AIUR up to and including 57.6 kbit/s for multislot operations in A/Gb mode. + +The multiplexing function is based on the ITU-T I.460. The multiplexing function is used to combine n (n=2 to 4) substreams of multislot intermediate rate of 8 kbit/s or n substreams of multislot intermediate rate of 16 kbit/s on one 64 kbit/s stream by using subcircuits in each octet to each substream such that: + +- i) An 8 kbit/s substream is allowed to occupy subcircuits with positions 1,3,5 or 7 of each octet of the 64 kbit/s stream; a 16 kbit/s stream occupies bit positions (1,2) or (3,4) or (5,6) or (7,8). +- ii) The order of the bits at each substream is identical before and after multiplexing. +- iii) All unused bit positions shall be set to binary "1". +- iv) For transparent multislot configurations the lowest allowed subcircuits are always used. + +- v) For non-transparent multislot configurations, the lowest allowed subcircuits shall be used at call set up and after change of channel configuration except at downgrading. At downgrading any of the used subcircuits may be released in uplink direction. Always, the released subcircuit(s) in downlink direction shall be the same as the released subcircuit(s) in uplink direction. At a possible subsequent upgrading, the lowest available bit positions shall be used for the added substreams. + +NOTE: The rules given here are almost identical to those of I.460, Section 'Fixed format multiplexing', except for the rule i) is stricter in that 8 kbit/s substreams cannot occupy any positions, iv) and v) are added. + +# 15 Support of non-transparent bearer services in A/Gb mode + +## 15.1 TCH/F9.6 and TCH/F4.8 kbit/s channel codings + +In the case of non-transparent services the RA1/RA1' function shall perform the same mapping as that described for transparent services, using 12 and 6 kbit/s radio interface data rates, with the following modification. + +The E2 and E3 bits in the modified ITU-T V.110 80 bit frames shown in Figure 3 (derived from the standard ITU-T V.110 frame shown in Figure 2) are used to indicate each consecutive sequence of ITU-T V.110 80 bit frames corresponding to the four modified ITU-T V.110 60 bit frames (Figure 4) received/transmitted in one radio interface frame. This allows 240 bit Radio Link Protocol frames to/from the MSC to be aligned with the 4x60 bit frames encoded by the radio subsystem channel coder as a single unit (see 3GPP TS 45.003). The 8 bits consisting of the E2 and E3 bits in one of the above sequences is referred to as the Frame Start Identifier. The FSI value is 00 01 10 11. This value is assigned to the E2 and E3 bits as shown in Table 7. + +**Table 7** + +| | E2 | E3 | +|-----------------------------------------|----|----| +| First Modified ITU-T V.110 80 bit frame | 0 | 0 | +| Second | 0 | 1 | +| Third | 1 | 0 | +| Fourth | 1 | 1 | + +As each RLP frame is transported between the BSS and MSC in four modified ITU-T V.110 80 bit frames, it is necessary following a transmission break and at start up, to determine which modified ITU-T V.110 80 bit frame of the stream is the first for a particular RLP frame. This is needed so that correct alignment with the radio subsystem can be achieved. + +Modified V.110 80 bit frames can slip in time during re-routing, and whilst sync exists within the modified ITU-T V.110 80 bit frame to determine the modified ITU-T V.110 80 bit frame boundaries, the FSI is required to determine which quarter of an RLP frame each modified ITU-T V.110 80 bit frame contains. + +**Table 8: Relationship between FNUR, AIUR, substream rate, number of substreams and intermediate rate** + +| FNUR | AIUR | Number of Channels x Substream Rate | Channel Coding | Multislot Intermediate Rate | +|-------------|-------------|-------------------------------------------------------|----------------|-----------------------------| +| ≤2,4 kbit/s | 2,4 kbit/s | 2-8 times duplication of each bit to reach 2,4 kbit/s | TCH/F4.8 | 8 kbit/s | +| 4,8 kbit/s | 4,8 kbit/s | 4,8 kbit/s | TCH/F4.8 | 8 kbit/s | +| 4,8 kbit/s | 9,6 kbit/s | 9,6 kbit/s | TCH/F9.6 | 16 kbit/s | +| 9,6 kbit/s | 9,6 kbit/s | 2x4,8 kbit/s | 2XTCH/F4.8 | 8 kbit/s | +| 9,6 kbit/s | 9,6 kbit/s | 9,6 kbit/s | TCH/F9.6 | 16 kbit/s | +| 14,4 kbit/s | 14,4 kbit/s | 3X4,8 kbit/s | 3XTCH/F4.8 | 8 kbit/s | +| 14,4 kbit/s | 19,2 kbit/s | 2X9,6 kbit/s | 2XTCH/F9.6 | 16 kbit/s | +| 19,2 kbit/s | 19,2 kbit/s | 4X4,8 kbit/s | 4XTCH/F4.8 | 8 kbit/s | +| 19,2 kbit/s | 19,2 kbit/s | 2X9,6 kbit/s | 2XTCH/F9.6 | 16 kbit/s | +| 28,8 kbit/s | 28,8 kbit/s | 3X9,6 kbit/s | 3XTCH/F9.6 | 16 kbit/s | +| 38,4 | 38,4 kbit/s | 4X9,6 kbit/s | 4XTCH/F9.6 | 16 kbit/s | + +NOTE: The table gives the relation between the FNUR, AIUR, Substream Rate, Channel Coding and Intermediate Rate. As an example: the wanted FNUR is 14,4 kbit/s and the selected channel coding is TCH/F9.6. The data stream is split into two substreams of 9,6 kbit/s yielding an AIUR of 19,2 kbit/s. + +### 15.1.1 Alignment + +An alignment window spanning four modified ITU-T V.110 80 bit frames shall be used to search for the pattern of 8 bits described above in order to identify alignment with an RLP frame. + +In the event of failure to detect the 8 bit pattern, the alignment window is shifted one complete modified V.110 80 bit frame, discarding the contents of the most historical frame and then checking the new 8 bit pattern. + +### 15.1.2 Support of Discontinuous Transmission (DTX) + +The E1 bit in the modified ITU-T V.110 80 bit frame shown in Figure 3 shall be used in the direction MSC-BSS to indicate that DTX may be invoked (see 3GPP TS 24.022). The E1 bit in all of the four consecutive frames relating to the RLP frame to which DTX may be applied shall be set to 1. If DTX is not to be applied, the E1 bit shall be set to 0. + +In the direction BSS-MSC the E1 bit shall always be set to 0. + +### 15.1.3 Order of Transmission + +The first bit of each quarter of an RLP frame to be transmitted shall correspond to bit D1 of a modified V.110 frame (figures 3 and 4). The remaining 59 bits of each quarter of an RLP frame shall correspond to the D and D' bits , D2 - D'12, in order left to right and top to bottom as shown in figures 3 and 4. + +The first quarter of an RLP frame to be transmitted shall contain the E2 and E3 bit code 00 as shown in Table 1. The second quarter contains the code 01, etc. + +## 15.2 TCH/F14.4, TCH/F28.8, and TCH/F43.2 channel codings + +In case of non-transparent service, a 576 bit RLP frame shall be mapped over two consecutive A-TRAU frames. + +Because of that mapping, it is required, following a transmission break and at start up, to determine which A-TRAU frame of the stream is the first for a particular RLP frame. This is needed so that correct alignment with the radio subsystem can be achieved. + +The two consecutive M1 bits are referred to as the Frame Start Identifier. The FSI value is 01. This value is assigned to the M1 bits as shown in Table 9. + +Table 9 + +| | M1 bit | +|---------------------|--------| +| First A-TRAU frame | 0 | +| Second A-TRAU frame | 1 | + +A-TRAU frames can slip in time during re-routing, and whilst A-TRAU frame synchronisation exists, the FSI is required to determine which half of an RLP frame each A-TRAU frame contains. + +Table 10: Relationship between AIUR, substream rate, number of substreams and intermediate rate + +| | AIUR | Number of substreams x AIUR per substream | Channel Coding | Multislot intermediate Rate | +|--|-------------|-------------------------------------------|----------------------------|-----------------------------| +| | 14,4 kbit/s | 14,4 kbit/s | TCH/F14.4 | 16 kbit/s | +| | 28,8 kbit/s | 2X14,4 kbit/s | 2XTCH/F14.4
1XTCH/F28,8 | 16 kbit/s | +| | 43,2 kbit/s | 3X14,4 kbit/s | 3XTCH/F14.4
1XTCH/F43,2 | 16 kbit/s | +| | 57,6 kbit/s | 4X14,4 kbit/s | 4XTCH/F14.4 | 16 kbit/s | +| | 57,6 kbit/s | 4X14,4 kbit/s | 4XTCH/F14.4
2XTCH/F28,8 | 16 kbit/s | + +NOTE: The table gives the relation between AIUR, Substream Rate, Channel Coding and Intermediate Rate. As an example: the AIUR is 28,8 kbit/s and the selected channel coding is 14,5 kbit/s. The data stream is split into two substreams of 14,5 kbit/s yielding an AIUR of 28,8 kbit/s + +The same number of substreams is used in each direction, even if the AIURs in each direction differ. Superfluous substreams are filled with idle frames. These are inserted at the BTS or IWF and are discarded at the IWF or BTS respectively. At the IWF, the down link AIUR is determined by the out of band signalling (Assignment Complete, Handover Performed), whereas the up link AIUR is determined inband by examining the possible substream positions on the A interface. + +### 15.2.1 Alignment + +An alignment window spanning two 290 bit blocks in case of TCH/F14.4 channel shall be used to search for the pattern of 2 bits '01' described in subclause 15.2, in order to identify alignment with an RLP frame. + +In the event of failure to detect the 2 bits pattern the alignment window is shifted one 290 bit block, discarding the contents of the most historical frame and then checking the new 2 bits pattern. + +### 15.2.2 Support of Discontinuous Transmission (DTX) + +The M2 bit in the A-TRAU frame shown in Figure 5 shall be used in the direction MSC to BSS to indicate that DTX may be invoked (see 3GPP TS 24.022). The M2 bit in all of the two consecutive A-TRAU frames relating to the RLP frame to which DTX may be applied shall be set to 1. If DTX is not to be applied, the M2 bit shall be set to 0. + +In the direction BSS to MSC the M2 bit shall always be set to 0. + +# 15a Support of non-transparent bearer services in Iu mode + +In Iu mode the RLP frames are transmitted via the Iu interface by means of the Iu UP protocol in support mode, see 3GPP TS 25.415. Each SDU is transported in one Iu UP PDU type 1. + +Each SDU has a size of 576 bits and carries one RLP frame with frame size of 576 bits if TCH/F14.4, TCH/F28.8 or TCH/F43.2 channel coding is used in GERAN. Each SDU has a size of 480 bits and carries two RLP frames with frame size of 240 bits if TCH/F9.6 channel coding is used in GERAN. + +If TCH/F14.4, TCH/28.8 or TCH/F43.2 is used, the range of AIUR values is 14,4 kbit/s, 28,8 kbit/s, 43,2 kbit/s, 57,6 kbit/s, limited by the maximum bit rate, and varies with the transmission period on the Um interface, which is 40 ms, 20 ms, 13½ ms or 10 ms. If TCH/F9.6 is used, the range of AIUR values is 12, 24, 36, 48 kbit/s, limited by the maximum bit rate, and varies with the transmission on the Um interface, which is 40 ms, 20 ms, 13½ ms or 10 ms. A + +change in the transmission period is signalled to the IWF through the Iu UP protocol. The Iu UP primitive Iu-UP-DATA-REQUEST is invoked each time an RLP frame is ready to be sent from the IWF towards the UE. + +DTX indication is not used. + +# 16 Support of transparent bearer services in A/Gb mode + +## 16.1 TCH/F9.6 and TCH/F4.8 channel codings + +### 16.1.1 User rate adaptation on the A interface, AIUR less than or equal to 38,4 kbit/s + +The ITU-T V.110 80 bit frame shall be used for transparent data on the A interface. These frames are transmitted on up to four substreams multiplexed into one stream sent over the A interface. The split/combine function is applied on the substreams as specified in clause 5 of the present document. The relation between the AIUR and the number of channels is specified in table 11. + +The 64 kbit/s consists of octets, bits 1 through 8, with bit 1 transmitted first. + +For a 9 600 bit/s radio interface user rate the V.110 frame is carried with a 16 kbits/s stream which occupies bit positions (1,2). + +For radio interface user rates of either 4 800 bit/s, 2 400 bit/s, 1 200 bit/s or 300 bit/s the V.110 frame is carried with a 8 kbits/s stream which occupies bit position (1). For user rates < 1 200bit/s asynchronous characters are padded with additional stop elements by the RA0 function (in the MSC/IWF) to fit into 600 bit/s synchronous RA1 rate prior to rate adaptation to 64 kbits/s. + +No use of 4 kbit/s stream is foreseen. + +In a given V.110 frame on the A interface: + +- for 9 600 bit/s there is no repetition of bits D within the 16 kbit/s stream ; +- for 4 800 bit/s there is no repetition of bits D within the 8 kbit/s stream ; +- for 2 400 bit/s each bit D is repeated twice within the 8 kbit/s stream (D1 D1 D2 D2 etc) ; +- for 1 200 bit/s each bit D is repeated four times within the 8 kbit/s stream (D1 D1 D1 D1 D2 D2 D2 D2 etc) ; +- for 600 bit/s each bit D is repeated eight times within the 8kbit/s stream (D1 D1 D1 D1 D1 D1 D1 D1 D2 D2 D2 D2 D2 D2 D2 D2 etc); + +### 16.1.2 User rate Adaptation on the A-interface, AIUR greater than 38,4 kbit/s + +For AIUR of 48 kbit/s, 56 kbit/s and 64 kbit/s one stream consisting of ITU-T V.110 32 bit frames or 64 bit frames, as specified in 3GPP TS 44.021 shall be transmitted over the A-interface. Splitting/Combining which occurs in the BSS, is as specified in 3GPP TS 44.021. + +Table 11 gives the relation between the User Rate, Substream Rate Channel Coding and the Intermediate Rate. + +### 16.1.3 Relation between AIUR and the number of channels + +**Table 11: Relationship between the AIUR, substream rate, channel coding, intermediate rate and number of channels** + +| AIUR | Number of channels x Substream Rate | Channel Coding | (Multislot) intermediate Rate (Note 1) | +|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|----------------|----------------------------------------| +| ≤2,4 kbit/s | 2-8 times duplication of each bit to reach 4,8 kbit/s | TCH/F4.8 | 8 kbit/s | +| 4,8 kbit/s | 4,8 kbit/s | TCH/F4.8 | 8 kbit/s | +| 9,6 kbit/s | 2X4,8 kbit/s | 2XTCH/F4.8 | 8 kbit/s | +| 9,6 kbit/s | 9,6 kbit/s | TCH/F9.6 | 16 kbit/s | +| 14,4 kbit/s | 3X4,8 kbit/s | 3XTCH/F4.8 | 8 kbit/s | +| 14,4 kbit/s | 2X9,6 kbit/s w/ padding | 2XTCH/F9.6 | 16 kbit/s | +| 19,2 kbit/s | 4X4,8 kbit/s | 4XTCH/F4.8 | 8 kbit/s | +| 19,2 kbit/s | 2X9,6 kbit/s | 2XTCH/F9.6 | 16 kbit/s | +| 28,8 kbit/s | 3X9,6 kbit/s | 3XTCH/F9.6 | 16 kbit/s | +| 38,4 kbit/s | 4X9,6 kbit/s | 4XTCH/F9.6 | 16 kbit/s | +| 48 kbit/s | 5X9,6 kbit/s | 5XTCH/F9.6 | 64 kbit/s | +| 56 kbit/s | 5X11,2 kbit/s | 5XTCH/F9.6 | 64 kbit/s | +| 64 kbit/s | 6X11,2 kbit/s w/padd. | 6XTCH/F9.6 | 64 kbit/s | +| NOTE: For AIURs ≤ 38,4 kbit/s this column indicates the multislot intermediate rate: for higher AIURs it indicates the intermediate rate. | | | | + +### 16.1.4 Handling of status bits X, SA, SB + +In the single slot case, status bit SA shall be coded repeatedly as S1, S3, S6, S8, and SB is coded repeatedly as S4 and S9 in Figure 2. In the multislot case, status bit SA is coded repeatedly as S6, S8 and SB is coded as S9 in figures 2, 5 and 6. + +The handling of the status bits shall comply with the synchronisation procedures for transparent services which are as described in 3GPP TS 29.007 (MSC), 3GPP TS 44.021 (BSS), 3GPP TS 27.001 (MS). + +### 16.1.5 Handling of bits E1 to E7 + +Bits E1 to E3 shall be used according to 44.021. + +Bits E4 to E7 may be used for network independent clocking as indicated in 3GPP TS 44.021. + +## 16.2 TCH/F14.4, TCH/F28.8, and TCH/F32.0 channel codings + +### 16.2.1 User rate adaptation on the A interface, AIUR less than or equal to 56 kbit/s + +The A-TRAU frame shall be used for transparent user data rates other than 32 kbit/s on the A interface. The A-TRAU frames are transmitted on up to four substreams multiplexed into one stream sent over the A interface. The split/combine function is applied on the substreams as specified in clause 7 of this TS. The relation between the AIUR and the number of channels is specified in table 12. + +In a given A-TRAU frame on the A interface: + +- for 14 400 bit/s there is no repetition of bits D within the 16 kbit/s stream in a given A-TRAU frame on the A interface. + +The ITU-T I.460 rate adaptation is used for the transparent 32 kbit/s user rate on the A interface, i.e. four bits of each octet in the 64 kbit/s time slot are used for transporting the 32 kbit/s user data. + +### 16.2.2 User Rate Adaptation on the A-interface, AIUR greater than 56 kbit/s + +For AIUR of 64 kbit/s one stream consisting of ITU-T V.110 32 bit frames or 64 bit frames, as specified in 3GPP TS 44.021 shall be transmitted over the A-interface. Splitting/Combining which occurs in the BSS, shall be as specified in 3GPP TS 44.021. + +Table 12 gives the relation between the User Rate, Substream Rate Channel Coding and the Intermediate Rate. + +### 16.2.3 Relation between AIUR and the number of channels + +**Table 12: Relationship between the AIUR, AIUR per substream, channel coding, intermediate rate and number of substreams** + +| AIUR | Number of substreams x AIUR per substream | Channel Coding | Multislot intermediate Rate (note 1) | +|-------------|---------------------------------------------------|------------------------|--------------------------------------| +| 14,4 kbit/s | 14,4 kbit/s | TCH/F14.4 | 16 kbit/s | +| 28,8 kbit/s | 2X14,4 kbit/s | TCH/F14.4
TCH/F28.8 | 16 kbit/s | +| 32 kbit/s | 1x32 kbit/s | TCH/F32.0 | 32 kbit/s | +| 38,4 kbit/s | 3X14,4 kbit/s w/padding | TCH/F14.4 | 16 kbit/s | +| 48 kbit/s | 4X14,4 kbit/s w/padding | TCH/F14.4 | 16 kbit/s | +| 56 kbit/s | 4X14,4 kbit/s w/padding
1x64.0 kbit/s (Note 2) | TCH/F14.4
TCH/F32.0 | 16 kbit/s
64 kbit/s | +| 64kbit/s | 5X14,4 kbit/s w/padding
1x64.0 kbit/s (Note 2) | TCH/F14.4
TCH/F32.0 | 64 kbit/s | + +NOTE 1: For AIURs $\leq 56$ kbit/s this column indicates the multislot intermediate rate: for higher AIURs it indicates the intermediate rate. +NOTE 2: One substream over two air interface timeslots. No multislot intermediate rate. + +### 16.2.4 Handling of status bits X and SB + +The X and SB bits shall be carried over the A interface in a multiframe structure as described in subclause 10.3 of 3GPP TS 44.021. SA bit is not carried over the A interface. + +The handling of the status bits shall comply with the synchronisation procedures for transparent services which are as described in 3GPP TS 29.007 (MSC), 3GPP TS 44.021 (BSS), 3GPP TS 27.001 (MS). + +# 16a Support of transparent bearer services in Iu mode + +The Iu UP protocol is used in transparent mode, see 3GPP TS 25.415. The payload of the Iu frames will consist of user data bits only for synchronous data, and RA0 synchronous bit streams for asynchronous data. + +On the Iu interface, the payload (SDU) size is fixed, determined by the bit rate. Following table shows SDU sizes defined. AAL2 is used. The AAL2 SSCS layer shall be supported for segmentation and re-assembly. + +**Table 13: Relationship between the bit rate and the SDU size** + +| Bit rate | SDU size (= RLC PDU payload size) | +|--------------|-----------------------------------| +| 28.8 kbit/s | 576 bits | +| 33.6 kbit/s | 672 bits | +| 32 kbit/s | 640 bits | +| 56/64 kbit/s | 640 bits | + +The primitive Iu-UP-UNIT-DATA-REQUEST is invoked at regular intervals in order to have a constant bit rate (every SDU). + +# 17 Frame Formats + +| Octet No. | Bit number | | | | | | | | +|-----------|------------|-----|-----|-----|-----|-----|-----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 2 | 1 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 3 | 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 4 | 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| 5 | 1 | E1 | E2 | E3 | E4 | E5 | E6 | E7 | +| 6 | 1 | D25 | D26 | D27 | D28 | D29 | D30 | S6 | +| 7 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | X | +| 8 | 1 | D37 | D38 | D39 | D40 | D41 | D42 | S8 | +| 9 | 1 | D43 | D44 | D45 | D46 | D47 | D48 | S9 | + +Figure 2: The ITU-T V.110 80 bit frame for Transparent Data + +| octet no. | bit number | | | | | | | | +|-----------|------------|-----|-----|-----|-----|-----|-----|------| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | D'1 | +| 2 | 1 | D7 | D8 | D9 | D10 | D11 | D12 | D'2 | +| 3 | 1 | D13 | D14 | D15 | D16 | D17 | D18 | D'3 | +| 4 | 1 | D19 | D20 | D21 | D22 | D23 | D24 | D'4 | +| 5 | 1 | E1 | E2 | E3 | D'5 | D'6 | D'7 | D'8 | +| 6 | 1 | D25 | D26 | D27 | D28 | D29 | D30 | D'9 | +| 7 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | D'10 | +| 8 | 1 | D37 | D38 | D39 | D40 | D41 | D42 | D'11 | +| 9 | 1 | D43 | D44 | D45 | D46 | D47 | D48 | D'12 | + +Figure 3: The modified ITU-T V.110 80 bit frame for Non-Transparent Data + +| | | | | | | | +|-----|-----|-----|------|-----|-----|-----| +| D1 | D2 | D3 | D4 | D5 | D6 | D'1 | +| D7 | D8 | D9 | D10 | D11 | D12 | D'2 | +| D13 | D14 | D15 | D16 | D17 | D18 | D'3 | +| D19 | D20 | D21 | D22 | D23 | D24 | D'4 | +| D'5 | D'6 | D'7 | D'8 | D25 | D26 | D27 | +| D28 | D29 | D30 | D'9 | D31 | D32 | D33 | +| D34 | D35 | D36 | D'10 | D37 | D38 | D39 | +| D40 | D41 | D42 | D'11 | D43 | D44 | D45 | +| D46 | D47 | D48 | D'12 | | | | + +Figure 4: Modified ITU-T V.110 60 bit frame for Non-Transparent Data + +| octet number | bit number | | | | | | | | | +|--------------|------------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|---------------------| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | M1 | M2 | | +| 3 | Z1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | | +| 4 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | 36 bit data field 1 | +| 5 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | | +| 6 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | | +| 7 | D32 | D33 | D34 | D35 | D36 | Z2 | D1 | D2 | | +| 8 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | | +| 9 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | 36 bit data field 2 | +| 10 | D19 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | | +| 11 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | | +| 12 | D35 | D36 | Z3 | D1 | D2 | D3 | D4 | D5 | | +| 13 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | | +| 14 | D14 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | 36 bit data field 3 | +| 15 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | | +| 16 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | Z4 | | +| 17 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | | +| 18 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | 36 bit data field 4 | +| 19 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | D24 | | +| 20 | D25 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | | +| 21 | D33 | D34 | D35 | D36 | Z5 | D1 | D2 | D3 | | +| 22 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | | +| 23 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | D19 | 36 bit data field 5 | +| 24 | D20 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | | +| 25 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | | +| 26 | D36 | Z6 | D1 | D2 | D3 | D4 | D5 | D6 | | +| 27 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | | +| 28 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | 36 bit data field 6 | +| 29 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | | +| 30 | D31 | D32 | D33 | D34 | D35 | D36 | Z7 | D1 | | +| 31 | D2 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | | +| 32 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | D17 | | +| 33 | D18 | D19 | D20 | D21 | D22 | D23 | D24 | D25 | 36 bit data field 7 | +| 34 | D26 | D27 | D28 | D29 | D30 | D31 | D32 | D33 | | +| 35 | D34 | D35 | D36 | Z8 | D1 | D2 | D3 | D4 | | +| 36 | D5 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | | +| 37 | D13 | D14 | D15 | D16 | D17 | D18 | D19 | D20 | 36 bit data field 8 | +| 38 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | | +| 39 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | | + +Figure 5: A-TRAU 320 bit frame + +| octet no. | bit number | | | | | | | | +|-----------|------------|-----|-----|-----|-----|-----|-----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 2 | 1 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 3 | 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 4 | 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| 5 | 1 | E1 | E2 | E3 | E4 | E5 | E6 | E7 | +| 6 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | S6 | +| 7 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | X | +| 8 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | S8 | +| 9 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | S9 | + +Figure 6: The modified ITU-T V.110 80 bit frame padded for 4,8 kbit/s transparent data at intermediate rate 16 kbit/s + +| Octet No. | Bit number | | | | | | | | +|-----------|------------|-----|-----|-----|-----|-----|-----|----| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 2 | 1 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 3 | 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 4 | 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | +| 5 | 1 | E1 | E2 | E3 | E4 | E5 | E6 | E7 | +| 6 | 1 | D25 | D26 | D27 | D28 | D29 | D30 | S6 | +| 7 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | X | +| 8 | 1 | D37 | D38 | D39 | D40 | D41 | D42 | S8 | +| 9 | 1 | D43 | D44 | D45 | D46 | D47 | D48 | S9 | + +Figure 7: The ITU-T V.110 80 bit RA1 frame structure + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 1 | D7 | D8 | D9 | D10 | F | F | X | +| 1 | D11 | D12 | F | F | D13 | D14 | S3 | +| 1 | F | F | D15 | D16 | D17 | D18 | S4 | +| 1 | 1 | 0 | 1 | E4 | E5 | E6 | E7 | +| 1 | D19 | D20 | D21 | D22 | D23 | D24 | S6 | +| 1 | D25 | D26 | D27 | D28 | F | F | X | +| 1 | D29 | D30 | F | F | D31 | D32 | S8 | +| 1 | F | F | D33 | D34 | D35 | D36 | S9 | + +F =Fill bits, which are set to 1. + +Figure 8: The ITU-T V.110 80 bit frame for 3.6 kbit/s transparent data (8 kbit/s intermediate rate) + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D1 | D2 | D2 | D3 | D3 | S1 | +| 1 | D4 | D4 | D5 | D5 | D6 | D6 | X | +| 1 | D7 | D7 | D8 | D8 | D9 | D9 | S3 | +| 1 | D10 | D10 | D11 | D11 | D12 | D12 | S4 | +| 1 | 1 | 1 | 0 | E4 | E5 | E6 | E7 | +| 1 | D13 | D13 | D14 | D14 | D15 | D15 | S6 | +| 1 | D16 | D16 | D17 | D17 | D18 | D18 | X | +| 1 | D19 | D19 | D20 | D20 | D21 | D21 | S8 | +| 1 | D22 | D22 | D23 | D23 | D24 | D24 | S9 | + +Figure 9: ITU-T V.110 80 bit frame for 2,4 kbit/s transparent data (8 kbit/s intermediate rate) + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D1 | D1 | D1 | D2 | D2 | S1 | +| 1 | D2 | D2 | D3 | D3 | D3 | D3 | X | +| 1 | D4 | D4 | D4 | D4 | D5 | D5 | S3 | +| 1 | D5 | D5 | D6 | D6 | D6 | D6 | S4 | +| 1 | 0 | 1 | 0 | E4 | E5 | E6 | E7 | +| 1 | D7 | D7 | D7 | D7 | D8 | D8 | S6 | +| 1 | D8 | D8 | D9 | D9 | D9 | D9 | X | +| 1 | D10 | D10 | D10 | D10 | D11 | D11 | S8 | +| 1 | D11 | D11 | D12 | D12 | D12 | D12 | S9 | + +Figure 10: ITU-T V.110 80 bit frame for 1,2 kbit/s transparent data (8 kbit/s intermediate rate) + +| | | | | | | | | +|---|----|----|----|----|----|----|-----------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | D1 | D1 | D1 | D1 | D1 | D1 | S1 | +| 1 | D1 | D1 | D2 | D2 | D2 | D2 | X | +| 1 | D2 | D2 | D2 | D2 | D3 | D3 | S3 | +| 1 | D3 | D3 | D3 | D3 | D3 | D3 | S4 | +| 1 | 1 | 0 | 0 | E4 | E5 | E6 | E7 (note) | +| 1 | D4 | D4 | D4 | D4 | D4 | D4 | S6 | +| 1 | D4 | D4 | D5 | D5 | D5 | D5 | X | +| 1 | D5 | D5 | D5 | D5 | D6 | D6 | S8 | +| 1 | D6 | D6 | D6 | D6 | D6 | D6 | S9 | + +NOTE: In order to maintain compatibility with Recommendation X.30 (I.461), for the 600 bit/s user rate bit E7 is coded to enable the 4×80 bit multiframe synchronisation. To this end, E7 in the fourth 80 bit frame is set to binary '0'. See Table 6 of ITU-T Recommendation V.110(09/92). + +**Figure 11: ITU-T V.110 80 bit frame for 600 bit/s transparent data (8 kbit/s intermediate rate)** + +| | | | | | | | | +|---|-----|-----|-----|-----|-----|-----|----| +| 1 | D1 | D2 | D3 | D4 | D5 | D6 | S1 | +| 0 | D7 | D8 | D9 | D10 | D11 | D12 | X | +| 1 | D13 | D14 | D15 | D16 | D17 | D18 | S3 | +| 1 | D19 | D20 | D21 | D22 | D23 | D24 | S4 | + +**Figure 12: The ITU-T V.110 32 bit 48 kbit/s frame structure (64 kbit/s intermediate rate)** + +| | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|---| +| D1 | D2 | D3 | D4 | D5 | D6 | D7 | 1 | +| D8 | D9 | D10 | D11 | D12 | D13 | D14 | 1 | +| D15 | D16 | D17 | D18 | D19 | D20 | D21 | 1 | +| D22 | D23 | D24 | D25 | D26 | D27 | D28 | 1 | +| D29 | D30 | D31 | D32 | D33 | D34 | D35 | 1 | +| D36 | D37 | D38 | D39 | D40 | D41 | D42 | 1 | +| D43 | D44 | D45 | D46 | D47 | D48 | D49 | 1 | +| D50 | D51 | D52 | D53 | D54 | D55 | D56 | 1 | + +**Figure 13: The ITU-T V.110 64 bit 56 kbit/s frame structure (64 kbit/s intermediate rate, option without status bits)** + +# Annex A (informative): Frame Pattern Substitution + +## A.1 Special cases + +If the sub frame starts with a Zseq, D1 is empty. With the above example, the resulting input and output sub frames are the following: + +![Diagram illustrating frame pattern substitution when the sub frame starts with a Zseq. The input sub frame consists of Zseq1, D2, Zseq2, D3, Zseq3, and D4. The output sub frame consists of 0, ZSP(1), ZSP(a1), D2, ZSP(a2), D3, and D4. The diagram shows the mapping of Zseq blocks to ZSP blocks and the mapping of data blocks D2, D3, and D4.](088921fa3f5a44c8551815122517eefd_img.jpg) + +The diagram illustrates the process of frame pattern substitution. At the top, a horizontal line represents the bit position, with markers at 1, $a_1$ , and $a_2$ . Below this, the input sub frame is shown as a sequence of blocks: Zseq1, D2, Zseq2, D3, Zseq3, and D4. Two arrows, labeled 'a' and 'd', point from the input sub frame to two separate lists. The 'a' arrow points to a list of addresses of the Z sequences, which contains the values 1, $a_1$ , and $a_2$ . The 'd' arrow points to a list of the data blocks without Z sequence, which contains the blocks D2, D3, and D4. Below these lists, the output sub frame is shown as a sequence of blocks: 0, ZSP(1), ZSP( $a_1$ ), D2, ZSP( $a_2$ ), D3, and D4. Arrows from the address list and the data block list point to the corresponding blocks in the output sub frame. + +Diagram illustrating frame pattern substitution when the sub frame starts with a Zseq. The input sub frame consists of Zseq1, D2, Zseq2, D3, Zseq3, and D4. The output sub frame consists of 0, ZSP(1), ZSP(a1), D2, ZSP(a2), D3, and D4. The diagram shows the mapping of Zseq blocks to ZSP blocks and the mapping of data blocks D2, D3, and D4. + +In the same case as above but with only one ZSP, the resulting input and output sub frames are the following: + +![Diagram illustrating the transformation of a Z sequence into a ZSP sequence. At the top, a box contains 'Zseq1' (highlighted) and 'D2'. Two arrows, 'a' and 'd', point down to 'list of addresses of the Z sequences' and 'list of the data blocks without Z sequence' respectively. Below these, a box with '1' points to the left and a box with 'D2' points to the right. Both point to a final box containing '0', 'ZSP(1)' (highlighted), and 'D2'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +graph TD + Top["Zseq1 | D2"] -- a --> Left["list of addresses +of the Z sequences"] + Top -- d --> Right["list of the data blocks +without Z sequence"] + Left --> BottomLeft["1"] + Right --> BottomRight["D2"] + BottomLeft --> Final["0 | ZSP(1) | D2"] + BottomRight --> Final + +``` + +Diagram illustrating the transformation of a Z sequence into a ZSP sequence. At the top, a box contains 'Zseq1' (highlighted) and 'D2'. Two arrows, 'a' and 'd', point down to 'list of addresses of the Z sequences' and 'list of the data blocks without Z sequence' respectively. Below these, a box with '1' points to the left and a box with 'D2' points to the right. Both point to a final box containing '0', 'ZSP(1)' (highlighted), and 'D2'. + +## A.2 False Z sequence detection + +The Framing Pattern Substitution algorithm presented in subclause 10.2 ensures sure that all the Z sequences found in the original sub frame are removed, but it shall be checked that the transformations performed do not introduce new unwanted Z sequences. + +The goal of this subclause is to show that the transformed sub frame does not contain new Z sequences introduced by the algorithm itself. + +The coding of the ZSP is the key point to avoid such an emulation. The different cases are considered below. + +### 1: Sequence ZSP + +The worst case is when the address is equal to 1: + +| | | | | | | | | +|---|---|----|----|----|----|----|---| +| 1 | C | A0 | A1 | A2 | A3 | A4 | 1 | +| 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | + +There is a maximum of 5 zeroes. + +### 2: Sequence Di / ZSP. + +By definition, a data block always ends up with a one (except the last one of the message) and the ZSP always starts with a 1. + +### 3: Sequence ZSP / Di + +ZSP always ends up with a 1 and Di has a maximum of 7 zeroes : it is not possible to find 16 zeroes in a row. + +### 4: Sequence Di / Dj + +Di is not the last data block of the message. + +As already mentioned, Di ends up with a one (except the last one) : this is the same case as 3. + +### **5: Sequence Zi / D or D / Zi** + +This case only occurs when there is no substitution. In this case, the Zi bit close to the D field is always a one: this does not change the number of zeroes in sequence. + +### **6: Sequence last Di / new framing pattern** + +The last D sequence can end up with up to 7 zeroes, followed by the 16 zeroes of the next frame. + +There is anyhow no ambiguity, when considering that the framing pattern is made up of 16 zeroes *followed* by a one. + +### **7: Sequence last Di / Z bit of the next sub frame** + +The last D sequence can end up with up to 7 zeroes, followed in the worst case by Z=0 and then a ZSP. As a ZSP starts with a one, this makes a maximum of 8 zeroes in a row. + +#### **8: Sequence ZSP / ZSP (not shown on the figure)** + +This case arrives when the original message has at least 16 zeroes in a row. + +As the ZSP element always starts and ends up with a one, this always induces two consecutive ones. + +# Annex B (informative): Change History + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|--------------------------------------------------------------------------------|-----------------------------------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | s27 | | A005 | | Synchronisation | 5.3.0 | 7.0.0 | +| | s29 | | A006 | | Introduction of EDGE channel codings into the specifications | 7.0.0 | 8.0.0 | +| | s30 | | A007 | | Asymmetric channel coding | 8.0.0 | 8.1.0 | +| 09-2000 | TSG#09 | NP-000551 | A008 | 1 | 32 kbit/s UDI/RDI multimedia in GSM | 8.1.0 | 8.2.0 | +| 12-2000 | TSG#10 | NP-000604 | A009 | | Removal of 1200/75 bit/s data rate and clean-up | 8.2.0 | 8.3.0 | +| 03-2001 | TSG#11 | NP-010040 | A013 | | Correction of downgrading procedure for HSCSD | 8.3.0 | 8.4.0 | +| 03-2001 | TSG#11 | | | | Upgraded to Release 4 [08.20 -> 48.020] | 8.4.0 | 4.0.0 | +| 12-2001 | TSG#14 | NP-010604 | 001 | 1 | Terminology clarifications requested by TSG GERAN | 4.0.0 | 5.0.0 | +| 09-2002 | TSG#17 | NP-020405 | 002 | | Correction of Rate Adaptation Functions and removal of S Reference Point in MS | 5.0.0 | 5.1.0 | +| 12-2002 | TSG#18 | NP-020617 | 003 | 4 | CS Data Services (including HSCSD and EDGE) for GERAN lu mode | 5.1.0 | 5.2.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.2.0 | 6.0.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.0.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.0.0 | 9.0.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | +| 2014-10 | | | | | Automatic upgrade from previous Release | 11.0.0 | 12.0.0 | +| 2015-12 | | | | | Automatic upgrade from previous Release | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | | Automatic upgrade from previous Release | 15.0.0 | +| 2020-07 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/48_series/48031/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-16/48_series/48031/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e11bc0de519415c7474ae6fd68f388c1e3f3d8f --- /dev/null +++ b/marked/Rel-16/48_series/48031/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e8011c1859125d4d17a27cdd74888b0274805fe23ab73af61c14e04ef3b4727 +size 27059 diff --git a/marked/Rel-16/48_series/48031/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Rel-16/48_series/48031/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b66411416b4a6470d280795c5c3a3e8b1dfc027 --- /dev/null +++ b/marked/Rel-16/48_series/48031/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:126b134780aed5af9bda81ba1832b728abf9c5f7836eb917f7c312411dbda589 +size 16384 diff --git a/marked/Rel-16/48_series/48031/34f788b0e5bc8af774fa5561c22e6d01_img.jpg b/marked/Rel-16/48_series/48031/34f788b0e5bc8af774fa5561c22e6d01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46564ef9b2f798cf33f102b8d1a85809d7a38f10 --- /dev/null +++ b/marked/Rel-16/48_series/48031/34f788b0e5bc8af774fa5561c22e6d01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:229014e5ac78e2ab4c6627e066f5760d8bec3a3a9e952019746dd7e0fc4da189 +size 39223 diff --git a/marked/Rel-16/48_series/48031/3b621c21b0af3a504a28d2547e87138f_img.jpg b/marked/Rel-16/48_series/48031/3b621c21b0af3a504a28d2547e87138f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..111a2d4899bd8aa1640bab3025d684ca3c7c549f --- /dev/null +++ b/marked/Rel-16/48_series/48031/3b621c21b0af3a504a28d2547e87138f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:408d5618cb7423f6c5a21efecb112dfeef70db5bf87a44e39efcac0022863167 +size 28570 diff --git a/marked/Rel-16/48_series/48031/426efb7efdc753a13f2fa16f7bff9429_img.jpg b/marked/Rel-16/48_series/48031/426efb7efdc753a13f2fa16f7bff9429_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e912fa3305e254fef55d6cc0604a31c63a598de8 --- /dev/null +++ b/marked/Rel-16/48_series/48031/426efb7efdc753a13f2fa16f7bff9429_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d592777c00eb848b5c9c6229e79468fe80f95954a20cbf3fbac89eaec6f341b8 +size 32559 diff --git a/marked/Rel-16/48_series/48031/65550960f5c5afd9d27706aaeddb0638_img.jpg b/marked/Rel-16/48_series/48031/65550960f5c5afd9d27706aaeddb0638_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f08c485d96eede78620ac058dbd9751c660d77a3 --- /dev/null +++ b/marked/Rel-16/48_series/48031/65550960f5c5afd9d27706aaeddb0638_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75d592b577abb8f593f95025064f7c6b5b5f606966f82aa49e920300aa04ac08 +size 31623 diff --git a/marked/Rel-16/48_series/48031/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/48_series/48031/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4254856073e0c57b348a2947711cb916991a2a01 --- /dev/null +++ b/marked/Rel-16/48_series/48031/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f6867714f12b7651d8e96a6a1d9e8b03814b9cf42b2522e00486a9e6824326f +size 22883 diff --git a/marked/Rel-16/48_series/48031/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-16/48_series/48031/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57caeff2a8d5510139fe602b708378c3962a53b2 --- /dev/null +++ b/marked/Rel-16/48_series/48031/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abfac10f8171e745ff4a88aaf654fb75d61e06ae2f1411d66f76fc11c7149eec +size 28428 diff --git a/marked/Rel-16/48_series/48031/e2c1c672349c10dccb2563eff6d8260e_img.jpg b/marked/Rel-16/48_series/48031/e2c1c672349c10dccb2563eff6d8260e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5644046f7857862ebf68b44d18dba0c58d0a66e7 --- /dev/null +++ b/marked/Rel-16/48_series/48031/e2c1c672349c10dccb2563eff6d8260e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a898805348f2dda8ee4fc92d2a9b295be2e2bc9f2ed1f58d413f8fb0c6a569af +size 21689 diff --git a/marked/Rel-16/48_series/48031/raw.md b/marked/Rel-16/48_series/48031/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e77e703c4560e2a4264c588477ee49957555ffe7 --- /dev/null +++ b/marked/Rel-16/48_series/48031/raw.md @@ -0,0 +1,1386 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Abbreviations ..... | 7 | +| 4 Procedures..... | 7 | +| 4.1 RIT Procedures..... | 7 | +| 4.1.1 RIT Query Operation..... | 8 | +| 4.1.2 RIT Indication Operation ..... | 8 | +| 4.1.3 RIT Query Stop Operation ..... | 9 | +| 4.2 (void)..... | 10 | +| 4.3 Deciphering Keys Procedure..... | 10 | +| 4.3.1 Deciphering Keys Update Operation..... | 10 | +| 5 Error Handling ..... | 10 | +| 5.1 Missing Message Part..... | 10 | +| 5.2 Repeated Message Part..... | 10 | +| 5.3 Unforeseen Message Part..... | 11 | +| 5.4 Incorrect Data ..... | 11 | +| 5.5 Repeated Operation ..... | 11 | +| 5.6 Unforeseen Operation ..... | 11 | +| 5.7 Unknown Request ID..... | 11 | +| 5.8 Duplicate Request ID ..... | 11 | +| 5.9 No RIT Information ..... | 12 | +| 5.10 (void)..... | 12 | +| 5.11 Deciphering Keys Error ..... | 12 | +| 5.12 Internal Error ..... | 12 | +| 5.13 Other Error Situations ..... | 12 | +| 5.14 Summary of Indications ..... | 12 | +| 6 Signalling Elements ..... | 13 | +| 6.1 Messages ..... | 13 | +| 6.1.1 Operation Code..... | 14 | +| 6.1.2 Request ID ..... | 16 | +| 6.1.3 Argument..... | 16 | +| 6.1.4 Result..... | 16 | +| 6.1.5 Error Indication ..... | 16 | +| 6.2 ASN.1 Definition of Arguments, Results, and IEs ..... | 17 | +| Annex A (normative): Operation and Error Definition..... | 21 | +| Annex B (informative): Description of Arguments, Results and Information elements ..... | 22 | +| B.1 Description of elements..... | 22 | +| B.1.1 Arguments and Results ..... | 22 | +| B.1.1.1 RIT Query Operation..... | 22 | +| B.1.1.1.1 Argument..... | 22 | +| B.1.1.1.2 Result..... | 22 | +| B.1.1.2 RIT Indication..... | 22 | +| B.1.1.2.1 Argument..... | 22 | +| B.1.1.2.2 Result..... | 23 | +| B.1.1.3 RIT Query Stop..... | 23 | +| B.1.1.3.1 Argument..... | 23 | +| B.1.1.3.2 Result..... | 23 | +| B.1.1.4 (void)..... | 23 | +| B.1.1.5 Send Deciphering Keys ..... | 23 | +| B.1.1.5.1 Request..... | 23 | +| B.1.1.5.2 Result..... | 23 | +| B.1.2 Information elements..... | 23 | + +B.1.2.1 Request Type IE..... 23 +B.1.2.2 Cell List IE..... 24 +B.1.2.3 Reference Clock IE..... 25 +B.1.2.4 RIT Data IE..... 27 +B.1.2.5 (void)..... 29 +B.1.2.6 (void)..... 29 +B.1.2.7 (void)..... 29 +B.1.2.8 (void)..... 29 +B.1.2.9 (void)..... 29 +B.1.2.10 (void)..... 29 +B.1.2.11 (void)..... 29 +B.1.2.12 (void)..... 29 +B.1.2.13 (void)..... 29 +B.1.2.14 (void)..... 29 +B.1.2.15 (void)..... 29 +B.1.2.16 Deciphering Key Type IE..... 29 +B.1.2.17 Deciphering Keys IE..... 29 +B.1.2.18 Location Area IE..... 29 +B.1.2.19 (void)..... 29 + +Annex C (informative): Change History..... 30 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains the definition of the SMLCPP protocol to be used between two Serving Mobile Location Centres (SMLC). + +The LCS architecture is described in 3GPP TS 43.059. The following aspects of it are relevant to the issue: + +- each SMLC controls a number of LMUs, and a given LMU is under the direct control of a single SMLC; +- there is a direct communication path, independent of SMLCPP, between a LMU and the SMLC that controls it; +- deciphering keys are controlled by one SMLC in the location area and sent to other SMLCs in the same location area. + +SMLCPP runs between two SMLC functions in the same PLMN. Transport is outside the scope of the present document. It assumes a transport service between these functions, as provided by BSSAP-LE. The present document assumes that the underlying transport (e.g., as described by BSSAP-LE specifications) provides for transport and routing for any two pairs of SMLCs which need to run SMLCPP exchanges. + +The main functions of SMLCPP are described in [5]. The key aspects are: + +- a) allowing an SMLC to ask for and obtain information about Radio Interface Timing (RIT), as known from measurements done by LMUs not under its direct control; +- c) allowing an SMLC, that controls deciphering keys in the location area, to send them to other SMLCs in the same location area. + +# --- 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 21.905: "Vocabulary for 3GPP Specifications". +- [2] (void) +- [3] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [4] 3GPP TS 24.008: "Mobile radio interface layer 3 specification". +- [5] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services in GERAN (Release 4)". +- [6] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [7] ASN.1 encoding rules "Specification of Packet Encoding Rules (PER)" ITU-T Rec. X.691 (1997) | ISO/IEC 8825-2:1998. +- [8] (void) +- [9] Abstract Syntax Notation One (ASN.1) "Specification of Basic Notation" ITU-T Rec.X.680 (1997) | ISO/IEC 8824 – 1:1998. +- [10] (void) +- [11] 3GPP TS 44.071: "Mobile radio interface layer 3 Location Services (LCS) specification". + +[12] 3GPP TS 49.031: "Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". + +# 3 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905 or in 3GPP TS 43.059. + +# 4 Procedures + +## 4.1 RIT Procedures + +Two modes of operation are supported: + +- provision of RIT information on request. In this mode a SMLC Client needing RIT information requests it from another SMLC using the RIT Query operation. The SMLC Server sends the requested RIT information using the RIT Indication operation. There are two cases: + - single indication: RIT Indication is requested only once. + +![Sequence diagram for single RIT Indication](e2c1c672349c10dccb2563eff6d8260e_img.jpg) + +A sequence diagram showing the interaction between an SMLC Client and an SMLC Server. The Client sends a 'RIT Query' message to the Server. The Server responds with a 'RIT Indication' message back to the Client. The diagram consists of two vertical lifelines and two horizontal arrows between them. + +Sequence diagram for single RIT Indication + +In this case the procedure consists of one RIT Query and one RIT Indication operations. + +- Open-ended repetitive RIT Indications: RIT information is requested on a regular basis until the RIT Query Stop operation. + +![Sequence diagram for repetitive RIT Indications](34f788b0e5bc8af774fa5561c22e6d01_img.jpg) + +A sequence diagram showing the interaction between an SMLC Client and an SMLC Server for repetitive RIT Indications. The Client sends a 'RIT Query' message to the Server. The Server responds with a 'RIT Indication' message. This is followed by an ellipsis '...' indicating further messages. Then another 'RIT Indication' message is shown. Finally, the Client sends a 'RIT Query Stop' message to the Server. The diagram consists of two vertical lifelines and multiple horizontal arrows between them. + +Sequence diagram for repetitive RIT Indications + +In this case the procedure consists of one RIT Query, one or more RIT Indication, and one RIT Query Stop operations. + +- Autonomous provision of RIT information. In this mode, the RIT information is provided automatically by the SMLC Server, according to an internal configuration not managed through SMLCPP (e.g., by O&M). + +![Sequence diagram showing SMLC Client and SMLC Server with RIT Indication messages.](d0abac95583b52a3b35f74a215567334_img.jpg) + +A sequence diagram showing two lifelines: SMLC Client and SMLC Server. Two messages labeled "RIT Indication" are shown as solid arrows pointing from the SMLC Server to the SMLC Client. There is an ellipsis between the two messages. Vertical lines extend downwards from the bottom of each lifeline box. + +Sequence diagram showing SMLC Client and SMLC Server with RIT Indication messages. + +In the autonomous mode the procedure consists of one or more RIT Indication operations. + +Three RIT related operations are then included in the SMLCPP, one for requesting the provision of RIT data, the second for provision, and the third one for stopping open-ended repetitive indications. + +### 4.1.1 RIT Query Operation + +![Sequence diagram for RIT Query Operation between two SMLC entities.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +A sequence diagram showing two lifelines: SMLC and SMLC. A solid arrow labeled "RIT Query Request(Request ID, ...)" points from the left SMLC to the right SMLC. Two dashed arrows point back from the right SMLC to the left SMLC, labeled "RIT Query Response(Request ID)" and "RIT Query Error(Request ID, ...)" respectively. + +Sequence diagram for RIT Query Operation between two SMLC entities. + +This operation allows a SMLC to query RIT information from another SMLC. This operation consists of sending of a RIT Query Request. It includes the Request ID , that is used to identify different queries. The RIT Query Request also includes the description of the scheduling of RIT Indication operations in the reverse direction. This includes the following cases: + +- single indication; RIT Indication is requested only once; +- open-ended repetitive indications; RIT Indication operations are requested on a regular basis until the RIT Query Stop operation. + +A RIT Query Response includes the same Request ID that the Request included, and it is used as a positive acknowledgement. A RIT Query Error message can be sent in return, if the SMLC Server detects an error situation (e.g. syntax errors, or overlapping Request ID values), or it can not fullfil the Request (e.g. RIT information is requested for unknown BTSs ). It contains the same Request ID values as the Request. + +### 4.1.2 RIT Indication Operation + +![Sequence diagram for RIT Indication Operation between two SMLC entities.](3b621c21b0af3a504a28d2547e87138f_img.jpg) + +A sequence diagram showing two lifelines: SMLC and SMLC. A solid arrow labeled "RIT Indication Request(Request ID, ...)" points from the right SMLC to the left SMLC. Two dashed arrows point back from the left SMLC to the right SMLC, labeled "RIT Indication Response(Request ID)" and "RIT Indication Error(Request ID, ...)" respectively. + +Sequence diagram for RIT Indication Operation between two SMLC entities. + +This operation allows a SMLC to send RIT information to another SMLC. It can be used both in the case of autonomous provision, and the provision of RIT information on request. + +The RIT Indication Request contains RIT information to be delivered. It also contains the Request ID that: + +- has the same value as the RIT Query operation, that invoked the RIT Indication (RIT provision on request); + +- has a reserved value indicating autonomous provision. + +A RIT Indication Response includes the same Request ID that the Request included, and it is used as a positive acknowledgement. The SMLC Client can send a RIT Indication Error to the SMLC Server, if it detects an error situation (e.g. syntax errors, or unknown Request ID values). + +### 4.1.3 RIT Query Stop Operation + +![Sequence diagram for RIT Query Stop Operation between two SMLC entities.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +``` + +sequenceDiagram + participant SMLC1 as SMLC + participant SMLC2 as SMLC + Note left of SMLC1: + SMLC1->>SMLC2: RIT Query Stop Request(Request ID) + SMLC2-->>SMLC1: RIT Query Stop Response(Request ID) + SMLC2-->>SMLC1: RIT Query Stop Error(Request ID, ...) + +``` + +Sequence diagram for RIT Query Stop Operation between two SMLC entities. + +This operation allows a SMLC to send an indication to another SMLCPP to stop sending RIT information, that it has originally asked to obtain on open-ended repetitive basis. The RIT Query Stop Request includes the Request ID values that is the same as in the corresponding RIT Query that should be stopped. A RIT Query Stop Response includes the same Request ID that the Request included, and it is used as a positive acknowledgement. The SMLC Server can send a RIT Query Stop Error to the SMLC Client, if it detects an error situation (e.g. syntax errors, or unknown Request ID values). + +## 4.2 (void) + +## 4.3 Deciphering Keys Procedure + +This procedure includes one operation that is related to LCS assistance data broadcast deciphering keys. With this operation the SMLC Server controlling the deciphering keys (needed in LCS Assistance Data broadcast) can send the deciphering keys to other SMLC Clients in the same location area. One SMLC (i.e. SMLC Server) in location area is selected to control the deciphering keys and sending the keys to other SMLC Clients in location area. The sending has to be done to each SMLC Client with a separate message. + +![Sequence diagram for Deciphering Keys Update operation between an SMLC Server and an SMLC Client.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +``` + +sequenceDiagram + participant SMLC_Server as SMLC Server + participant SMLC_Client as SMLC Client + Note left of SMLC_Server: + SMLC_Server->>SMLC_Client: Deciphering Keys Update + +``` + +Sequence diagram for Deciphering Keys Update operation between an SMLC Server and an SMLC Client. + +### 4.3.1 Deciphering Keys Update Operation + +![Sequence diagram for Deciphering Keys Update Operation between two SMLC entities.](65550960f5c5afd9d27706aaeddb0638_img.jpg) + +``` + +sequenceDiagram + participant SMLC1 as SMLC + participant SMLC2 as SMLC + Note left of SMLC1: + SMLC1->>SMLC2: Deciphering Keys Update Request(Request ID, ...) + SMLC2-->>SMLC1: Deciphering Keys Update Response(Request ID) + SMLC2-->>SMLC1: Deciphering Keys Update Error(Request ID, ...) + +``` + +Sequence diagram for Deciphering Keys Update Operation between two SMLC entities. + +This operation allows a SMLC controlling deciphering keys to send the keys to another SMLC Client. + +The Deciphering Keys Update Request includes the Request ID and information of keys. A Deciphering Keys Update Response includes only the same Request ID that the Request included, and it is used as a positive acknowledgement. + +The SMLC Client can send a Deciphering Keys Update Error to the SMLC Server, if it detects an error situation (e.g. syntax errors). It contains the same Request ID values as the Request. + +# --- 5 Error Handling + +In this Clause it is described how the SMLC should act in different error situations. + +## 5.1 Missing Message Part + +When a SMLC receives a Request message that does not contain one or more expected message parts (e.g. information elements, Arguments, Request ID), it sends an Error with the indication 'Missing Message Part' (if the operation type is known), and ignores the Request. + +When a SMLC receives a Response or Error message that does not contain one or more expected message parts, it ignores the message. + +## 5.2 Repeated Message Part + +When a SMLC receives a Request message that contains one or more message parts (e.g. information elements, Arguments, Request ID) more times than expected, it sends an Error with the indication 'Repeated Message Part', and ignores the Request. + +When a SMLC receives a Response or Error message that contains one or more message parts more times than expected, it ignores the message. + +## 5.3 Unforeseen Message Part + +When a SMLC receives a Request message that contains one or more unforeseen message parts (e.g. information elements, Result), it sends an Error with the indication 'Unforeseen Message Part', and ignores the Request. + +When a SMLC receives a Response or Error message that contains one or more unforeseen message parts, it ignores the message. + +## 5.4 Incorrect Data + +When a SMLC receives a Request message that it can not fully understand, that contains syntax errors, or incorrect values, and no other Error Indication applies, it sends an Error with the indication 'Incorrect Data' (if the operation type is known), and ignores the Request. If the SMLC can not understand the operation of the Request, it just ignores the Request. + +When a SMLC receives a Response or Error message that it can not fully understand, that contains syntax errors, or incorrect values, it ignores the message. + +## 5.5 Repeated Operation + +When a SMLC receives a Request message containing a Request ID, that is already in use by the same type of operation, the SMLC sends an Error with the indication 'Repeated Operation', and ignores the latter Request. In order to avoid mistaken use of this error indication for an open-ended repetitive RIT Indication, an SMLC server may choose not to send a RIT Indication Request until it has received a RIT Indication Response or RIT Indication Error from the SMLC Client for any previous RIT Indication Request. An SMLC Client may likewise choose not to send this error indication if, before it has responded to a RIT Indication Request, it receives a subsequent RIT Indication Request from the same SMLC Server carrying the same Request ID: if the SMLC client makes this choice, it shall prepare to treat the subsequent RIT Indication Request as legitimate. + +## 5.6 Unforeseen Operation + +When a SMLC receives a Request for an operation that is unexpected, and none of the situations in subclause 5.5 applies, then the SMLC sends an Error with the indication 'Unforeseen Operation', and ignores the Request. + +## 5.7 Unknown Request ID + +When a SMLC receives a RIT Indication Request that contains a Request ID value, that is not connected to any pending RIT Query operation, or autonomous provision of RIT information, it sends a RIT Indication Error with the indication 'Unknown Request ID'. + +When a SMLC receives a RIT Query Stop that contains a Request ID value, that is not connected to any pending RIT Query operation, it sends a RIT Query Stop Error with the indication 'Unknown Request ID'. + +When a SMLC receives a Response or Error message, that contains a Request ID that is not connected to any pending operation of that type, the SMLC ignores the message. + +## 5.8 Duplicate Request ID + +When a SMLC receives a Request message containing a Request ID, that is already in use by another type of operation, the SMLC sends an Error with the indication 'Duplicate Request ID'. + +## 5.9 No RIT Information + +When a SMLC receives a RIT Query Request, and does not have any of the requested RIT information (e.g. all cells, whose RIT information is asked for, are unknown) then the SMLC sends a RIT Query Error with the indication 'No RIT Information'. + +When during open-ended repetitive RIT indications, or autonomous provision of RIT information, there is no RIT information available, the requested SMLC refrains from sending RIT Indication Requests. + +When the requesting SMLC has asked for open-ended repetitive RIT indications, but it does not receive expected RIT information, it can send a RIT Query Stop, and then a new RIT Query. + +## 5.10 (void) + +## 5.11 Deciphering Keys Error + +When a SMLCPP receives a Send Deciphering Keys Request, and it detects an error situation connected with the contents of the message (e.g. the SMLC acts as a controller of deciphering keys for a location area, but it receives from another SMLC keys for the same location area), it sends a Send Deciphering Keys Error message with the indication 'Deciphering Keys Error'. + +## 5.12 Internal Error + +When a SMLCPP has any internal errors, that prevent it to act according to a Request, it can use 'Internal Error' indication in the Error message. + +## 5.13 Other Error Situations + +When a SMLCPP detects any other error situation when receiving a Request, it can use 'No Indication' indication in the Error message. + +## 5.14 Summary of Indications + +The following table summarizes the error indications, and which operations use them. + +Table 5.14: Error Indications and operations + +| Error Indication | RIT Query | RIT Indication | RIT Query Stop | Send Deciphering Keys | +|-------------------------|-----------|----------------|----------------|-----------------------| +| Missing Message Part | X | X | X | X | +| Repeated Message Part | X | X | X | X | +| Unforeseen Message Part | X | X | X | X | +| Incorrect Data | X | X | X | X | +| Repeated Operation | X | X | X | X | +| Unforeseen Operation | | X | X | | +| UnknownRequest ID | | X | X | | +| Duplicate Request ID | X | X | X | X | +| No RIT Information | X | | | | +| Deciphering Keys Error | | | | X | +| Internal Error | X | X | X | X | +| No Indication | X | X | X | X | + +# 6 Signalling Elements + +In this Clause the messages are described. + +The formal definitions of the SMLCPP messages are based on: + +- Abstract Syntax Notation One (ASN.1) "Specification of Basic Notation" ITU-T Rec.X.680 (1997) | ISO/IEC 8824 – 1:1998 +- ASN.1 encoding rules "Specification of Packet Encoding Rules (PER)" ITU-T Rec. X.691 (1997) | ISO/IEC 8825-2:1998 +- is consistent with these ITU-T recommendations. Also further definitions in this document are based on the same X.680 and X.691. BASIC-PER, unaligned variant is used. + +## 6.1 Messages + +This clause describes the contents of the different messages. + +There are three different types of messages: + +- request; +- response; +- error + +Operations use some or all of these message types, as described in Clause 4. The messages structures are as follows. + +![](426efb7efdc753a13f2fa16f7bff9429_img.jpg) + +| REQUEST | | +|----------------|--| +| Operation Code | | +| Request ID | | +| Argument | | + +| RESPONSE | | +|----------------|--| +| Operation Code | | +| Request ID | | +| Result | | + +| ERROR | | +|------------------|--| +| Request ID | | +| Error Indication | | + +The following ASN.1 description gives the formal definition of the messages. + +``` +SMLCPP-PDUs +-- { SMLCPP-Operations object identifier } + +DEFINITIONS AUTOMATIC TAGS::= + +BEGIN +``` + +``` + +-- Export all operations as default + +IMPORTS + SMLCPP-OPERATION, ERROR +FROM + SMLCPP-OperationDefinition + + rit-Query-Req, rit-Indication-Req, + decipheringKeysUpdate-Req, rit-QueryStop-Req +FROM + SMLCPP-Operations +; + +-- Request, Response or errorPDU is encapsuled to SMLCPP-PDU. +SMLCPP-PDU ::= CHOICE { + requestPDU SMLCPP-REQ-PDU, + responsePDU SMLCPP-RSP-PDU, + errorPDU SMLCPP-ERROR-PDU, + ... +} + +-- PDU definitions for Requests +SMLCPP-REQ-PDU ::= SEQUENCE { + code SMLCPP-OPERATION.&code ({SMLCPP-Operation-table}), + requestID INTEGER (0..255), + value SMLCPP-OPERATION.&Argument ({SMLCPP-Operation-table}{@code}) +} + +-- PDU definitions for Responses +SMLCPP-RSP-PDU ::= SEQUENCE { + code SMLCPP-OPERATION.&code ({SMLCPP-Operation-table}), + requestID INTEGER (0..255), + value SMLCPP-OPERATION.&Result ({SMLCPP-Operation-table}{@code}) +} + +-- PDU definition for ERROR messages +SMLCPP-ERROR-PDU ::= SEQUENCE { + requestID INTEGER (0..255), + value ERROR.&code +} + +SMLCPP-Operation-table SMLCPP-OPERATION ::= { + rit-Query-Req | + rit-Indication-Req | + decipheringKeysUpdate-Req | + rit-QueryStop-Req, + ... +} + +END + +``` + +### 6.1.1 Operation Code + +Operation code identifies different operations. Possible operations are those described in clause 4: + +- RIT Query; +- RIT Indication; +- RIT Query Stop; +- Deciphering Keys Update. + +The following ASN.1 operation description is based on the operation definition in the Annex A, and gives the formal definition of operations. + +``` + +SMLCPP-Operations +-- { SMLCPP-Operations object identifier } + +DEFINITIONS AUTOMATIC TAGS ::= + +``` + +``` +BEGIN + +-- Export all operations as default + +IMPORTS + +-- SMLCPP-OPERATION and ERROR definitions from + SMLCPP-OPERATION, ERROR +FROM + SMLCPP-OperationDefinition + +-- SMLCPP Datatypes + RIT-Query-Arg, RIT-QueryRsp-Arg, RIT-Indication-Arg, RIT-IndicationRsp-Arg, + DecipheringKeys-Arg, + DecipheringKeysRsp-Arg, RIT-StopQuery-Arg, RIT-StopQueryRsp-Arg +FROM + SMLCPP-DataTypes + +-- SMLCPP Errors + missingMsgPart, repeatedMsgPart, unforeseenMsgPart, incorrectData, + repeatedOperation, unforeseenOperation, unknownRequestID, + duplicateErrorID, noRITInfo, + decipheringKeyError, internalError, noIndication +FROM + SMLCPP-Errors +; + +-- SMLCPP Operations + +-- RIT Query Request Operation +rit-Query-Req SMLCPP-OPERATION ::= { + ARGUMENT RIT-Query-Arg + RESULT RIT-QueryRsp-Arg + ERRORS { missingMsgPart | + repeatedMsgPart | + unforeseenMsgPart | + incorrectData | + repeatedOperation | + unknownRequestID | + duplicateErrorID | + noRITInfo | + internalError | + noIndication + } + CODE 1 +} + +-- RIT Indication Operation +rit-Indication-Req SMLCPP-OPERATION ::= { + ARGUMENT RIT-Indication-Arg + RESULT RIT-IndicationRsp-Arg + ERRORS { missingMsgPart | + repeatedMsgPart | + unforeseenMsgPart | + incorrectData | + repeatedOperation | + unforeseenOperation | + unknownRequestID | + duplicateErrorID | + internalError | + noIndication + } + CODE 2 +} + +-- CODE 3 is reserved (Perform TOA Measurement Operation) + +-- Deciphering Keys Update Operation +decipheringKeysUpdate-Req SMLCPP-OPERATION ::= { + ARGUMENT DecipheringKeys-Arg + RESULT DecipheringKeysRsp-Arg + ERRORS { missingMsgPart | + repeatedMsgPart | + unforeseenMsgPart | + incorrectData | + repeatedOperation | +``` + +``` + + unforeseenOperation | + duplicateErrorID | + decipheringKeyError | + internalError | + noIndication + } + CODE 4 +} + +-- RIT Query Stop Operation +rit-QueryStop-Req SMLCPP-OPERATION ::= { + ARGUMENT RIT-StopQuery-Arg + RESULT RIT-StopQueryRsp-Arg + ERRORS { + missingMsgPart | + repeatedMsgPart | + unforeseenMsgPart | + incorrectData | + repeatedOperation | + unforeseenOperation | + unknownRequestID | + duplicateErrorID | + internalError | + noIndication + } + CODE 5 +} + +END + +``` + +### 6.1.2 Request ID + +Request ID is used to refer to different requests from the same SMLC, or to refer to autonomous sending in the case of RIT Indication operation. + +Value '0' may indicate autonomous sending in the case of the RIT Indication operation. This value is not used by any other operation. + +Other values 1-255 indicate an ID from the requesting SMLC, that can select the value from those not already used between it and a certain recipient SMLC. No certain order of Request ID values is used (e.g. the value does not need to be sequential 1, 2, 3,...). + +Within an operation possible Response and Error use the same Request ID that was in the Request. + +In the case of open ended repetitive RIT Indications, the RIT Query operation contains a certain Request ID value, that the successive RIT Indication operations and the RIT Query Stop operation also use to refer to this reporting task. The value shall not be the one for autonomous sending. + +### 6.1.3 Argument + +Argument contains operation specific information in the Request message. See Annex B for the contents in each operation, and 6.2 for the formal ASN.1 definition. + +### 6.1.4 Result + +Result contains operation specific information in the Response message. See annex B for the contents in each operation, and subclause 6.2 for the formal ASN.1 definition. + +### 6.1.5 Error Indication + +Error Indication provides some precision on a detected error. The possible values of Error Indication are listed in table 1 in clause 5. + +If an Error Indication is received encoding a value not in that table, the receiver shall behave as if the value was 'No indication'. + +The following ASN.1 error description is based on the error definition in the annex A, and gives the formal definition of errors. + +``` +SMLCPP-Errors +-- { SMLCPP-Errors object identifier } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- Export all errors as default + +IMPORTS + +-- Operation definitions + ERROR +FROM + SMLCPP-OperationDefinition +; + +-- Message contents errors + +missingMsgPart ERROR ::= {CODE 1} -- Missing message Part +repeatedMsgPart ERROR ::= {CODE 2} -- Repeated message Part +unforeseenMsgPart ERROR ::= {CODE 3} -- Unforeseen message Part +incorrectData ERROR ::= {CODE 4} -- Incorrect Data + +-- Operation errors + +repeatedOperation ERROR ::= {CODE 5} -- Repeated Operation +unforeseenOperation ERROR ::= {CODE 6} -- Unforeseen Operation + +-- Request ID errors + +unknownRequestID ERROR ::= {CODE 7} -- Unknown request ID +duplicateErrorID ERROR ::= {CODE 8} -- Duplicate Request ID + +-- SMLCPP data errors + +noRITInfo ERROR ::= {CODE 9} -- No RIT information +-- CODE 10 is reserved (noTOAMeasurements) +decipheringKeyError ERROR ::= {CODE 11} -- Deciphering Key error + +-- Other errors + +internalError ERROR ::= {CODE 12} -- Internal Error +noIndication ERROR ::= {CODE 13} -- No indication + +END +``` + +## 6.2 ASN.1 Definition of Arguments, Results, and IEs + +The following ASN.1 description gives the formal definition of Arguments, Results, and Information Elements. + +``` + +SMLCPP-DataTypes +-- { object identifier } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- Export all operations as default + +IMPORTS + +-- Datatypes from 02.071, LLP + CI, LAC, TimeSlot, FrameNumber +FROM + LLP-DataTypes + -- { LLP-DataTypes object identifier } + + ExtensionContainer +FROM MAP-ExtensionDataTypes { + ccitt identified-organization (4) etsi (0) mobileDomain (0) + gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} + +; + +-- ARGUMENT DEFINITIONS + +-- RIT Indication Request (ARGUMENT) +RIT-Indication-Arg ::= SEQUENCE { + referenceClock ReferenceClock, + rit-ATDRDQualityRes INTEGER (0..3), -- defines the resolution for ATDRD values + rit-ATDRDChangeQualityRes INTEGER (0..3), -- defines the resolution for ATDRD change values + rit-Data SeqOfRITData, + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +-- RIT Indication Response (RESULT) +RIT-IndicationRsp-Arg ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +-- RIT Query Request (ARGUMENT) +RIT-Query-Arg ::= SEQUENCE { + requestType RequestType, + rit-RequestDellList SeqOfRequestedRITCell, + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +-- RIT Query Response (RESULT) +RIT-QueryRsp-Arg ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +-- RIT Stop Query (ARGUMENT) +RIT-StopQuery-Arg ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +-- RIT Stop Query Rsp (RESULT) +RIT-StopQueryRsp-Arg ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +``` + +``` + +-- Deciphering Keys (ARGUMENT) +DecipheringKeys-Arg ::= SEQUENCE { + decipheringKeyType DecipheringKeyType, + decipheringKeySet DecipheringKeys, + lac LAC, + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +-- Deciphering Keys Rsp(RESULT) +DecipheringKeysRsp-Arg ::= SEQUENCE { + extensionContainer ExtensionContainer OPTIONAL, + ... +} + +-- FIELDS IN ARGUMENTS + +-- RIT-Query-Arg DEFINITIONS +-- RequestType +RequestType ::= CHOICE { + -- Send only one RIT Indication + singleSending NULL, + + -- Send RIT Indications until stop is received + openEnded OpenEndedType +} + +OpenEndedType ::= SEQUENCE { + -- Reporting period + reportingPeriodInfo ReportingPeriodInfo, + + -- Thresholds for change of AT and deviation of AT + changeLimit INTEGER (0..250) OPTIONAL, + deviationLimitInfo INTEGER (0..250) OPTIONAL +} + +-- Units and value of Reporting Period +ReportingPeriodInfo ::= SEQUENCE { + periodFormat PeriodFormat, + periodValue INTEGER (0..120) +} + +PeriodFormat ::= ENUMERATED { + tensOfSeconds (0), + tensOfMinutes(1) +} + +-- RequestedRITCell is actually a sequence of requested cells +SeqOfRequestedRITCell ::= SEQUENCE (SIZE (1..16)) OF RequestedRITCell +RequestedRITCell ::= SEQUENCE { + cellLAC LAC, + cellCI CI +} + +-- RIT-Indication-Arg DEFINITIONS +-- Reference clock definition, including reference cell and time +ReferenceClock ::= SEQUENCE { + referenceLAC LAC, + referenceCI CI, + referenceFrameNumber FrameNumber, + + -- If absoluteTime is absent, AT value of reference + -- cell is not known + absoluteTime AbsoluteTime OPTIONAL +} + +ReferenceAT ::= SEQUENCE { + seconds INTEGER (0..59), + nsecols INTEGER (0..99999999) +} + +-- Absolute time definition for reference cell +AbsoluteTime ::= SEQUENCE { + universalClock UniversalClockType, + + -- AT and ATChange definitions + referenceAT ReferenceAT, + -- This Quality information defines the quality of AT value + -- Resolution defines the resolution of Quality field as follows, + +``` + +``` +-- 0= 0.005 us, 1= 0.01 us, 2= 0.05 us +rit-RefATQuality SEQUENCE { + resolution INTEGER (0..3), + atQuality INTEGER (0..63) }, +referenceATChange INTEGER (-1000..1000), +-- This Quality information defines the quality of ATChange value +-- Resolution defines the resolution of Quality field as follows, +-- 0= 0.00005 ppm, 1= 0.0001 ppm, 2= 0.0005 +rit-RefATChangeQuality SEQUENCE { + resolution INTEGER (0..3), + atChangeQuality INTEGER (0..63) } +} + +UniversalClockType ::= ENUMERATED { + gpsClock (0), + ..., + galileoClock (1), + glonassClock (2), + qzssClock (3), + bdsClock (4), + spare4 (5), + spare5 (6), + spare6 (7), + spare7 (8), + spare8 (9), + spare9 (10) +} + +-- RIT Data is actually a sequence of RIT data elements +SeqOfRITData ::= SEQUENCE (SIZE (1..16)) OF RIT-Data +RIT-Data ::= SEQUENCE { + lac LAC, + ci CI, + frameNumber FrameNumber, + + -- ATD/RTD value and ATD/RTD change with quality figures + atdRTD INTEGER (0..923199), + atdRTDQuality INTEGER (0..63), + atdRTDChange INTEGER (-2000..2000), + atdRTDChangeQuality INTEGER (0..63) +} + +-- CIPHERING KEY INFORMATION +-- Octets in DecipheringKeys are coded in the same way as the octets 3 +-- to 17 of Deciphering Key IE in 3GPP 49.031. I.e. these octets contain +-- Current Deciphering Key, Next Deciphering Key and Ciphering Key Flag. +DecipheringKeys ::= OCTET STRING (SIZE (15)) + +-- Deciphering key type indicates the positioning method +-- value 0 corresponds to E-OTD +-- value 1 corresponds to GPS +DecipheringKeyType ::= INTEGER (0..1) + +END +``` + +# Annex A (normative): Operation and Error Definition + +The following ASN.1 operation and error definition is the basis for the ASN.1 description of operations and errors in this specification. + +``` +SMLCPP-OperationDefinition +-- {object identifier } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + + SMLCPP-OPERATION ::= CLASS { + &Argument, + &Result OPTIONAL, + &Errors ERROR, + &code INTEGER (0..255) + } + WITH SYNTAX { + ARGUMENT &Argument + [RESULT &Result] + ERRORS &Errors + CODE &code + } + + ERROR ::= CLASS { + &code INTEGER (0..255) + } + WITH SYNTAX { + CODE &code + } + +END +``` + +# Annex B (informative): Description of Arguments, Results and Information elements + +## B.1 Description of elements + +### B.1.1 Arguments and Results + +The following subchapters describe the contents of Arguments and Results of different operations. The formal ASN.1 definitions of Arguments, Results, and the Information Elements in them is given in 6.2. + +#### B.1.1.1 RIT Query Operation + +##### B.1.1.1.1 Argument + +**Table B.1.1.1.1: RIT Query operation Argument** + +| Information element | Type/Reference | Presence | +|---------------------|----------------------|----------| +| Request Type | Request Type B.1.2.1 | M | +| Cell List | Cell List B.1.2.2 | M | + +###### Request Type IE + +This IE provides the parameters for the requested RIT Indication operations and their scheduling. + +###### Cell List IE + +This IE defines the cells whose RIT information is requested. + +##### B.1.1.1.2 Result + +The Result is empty in the case of RIT Query operation. The RIT Query Response message is interpreted as a positive acknowledgement. + +#### B.1.1.2 RIT Indication + +##### B.1.1.2.1 Argument + +**Table B.1.1.2.1: RIT Indication operation Argument** + +| Information element | Type/Reference | Presence | +|---------------------|-------------------------|----------| +| Reference Clock | Reference Clock B.1.2.3 | M | +| RIT Data | RIT Data B.1.2.4 | M | + +###### Reference Clock IE + +The RTD and/or ATD values in this message are expressed relative to the reference clock indicated in this IE. In this version of the standard, the reference clock is the internal clock of some BTS or the GPS time reference. In the former case the BTS has to be measured by LMUs of both SMLCs. + +###### RIT Data IE + +This IE contains the RIT information from different cells reported relative to the reference clock defined in the previous IE. + +##### B.1.1.2.2 Result + +The RIT Indication operation has an empty Response message. + +#### B.1.1.3 RIT Query Stop + +##### B.1.1.3.1 Argument + +The RIT Query Stop operation has an empty Argument. + +##### B.1.1.3.2 Result + +The RIT Query Stop operation has an empty Response message. + +#### B.1.1.4 (void) + +#### B.1.1.5 Send Deciphering Keys + +##### B.1.1.5.1 Request + +**Table B.1.1.5.1: Send Deciphering Keys operation Argument** + +| Information element | Type/Reference | Presence | +|----------------------|-------------------------|----------| +| Deciphering Key Type | Deciphering Key Type 7 | M | +| Deciphering Keys | Deciphering Keys 1.2.19 | M | +| Location Area | Location Area 1.2.20 | M | + +###### Deciphering Key Type IE + +This IE defines the type of deciphering keys, i.e. whether the keys are applicable to E-OTD or GPS positioning method. + +###### Deciphering Keys IE + +This IE contains the Deciphering Keys information to be sent. + +###### Location Area + +This IE contains the LAC of the Location Area for which the deciphering keys are valid. + +##### B.1.1.5.2 Result + +The Send Deciphering Keys operation has an empty Result. + +### B.1.2 Information elements + +This clause describes the information structure of information elements independently from the messages where they appear. The formal ASN.1 definition of information elements is given in subclause 6.2. + +#### B.1.2.1 Request Type IE + +This IE gives the description of the type of the RIT information request. It contains the following fields: + +##### **Reporting Type** + +This field indicates how long the SMLC should report RIT information. This field is mandatory. This field has the following values: + +'0': 'Single Indication': Send only one RIT Indication; + +'1': 'Open ended repetitive RIT Indications': Send RIT Indications, according to instructions in the following fields, until told otherwise with a RIT Query Stop operation. + +##### **Reporting Period Format** + +This field describes the units of the Reporting Period field. This field is conditional, and included, if the Reporting Type field is '1', i.e. open ended repetitive RIT Indications are requested. If this field is included the minimal time period between the RIT Indication operations is as expressed in this and Reporting Period fields. + +'0': Reporting Period is told in tens of seconds; + +'1': Reporting Period is in tens of minutes. + +##### Reporting Period + +This field together with the Reporting Period Format field describes the maximum time period between the RIT Indication operations. This field is conditional and included only if the Reporting Type has the value '1', i.e. open ended repetitive RIT Indications are requested. + +The encoding shall provide for the range from 10 seconds to 20 hours, with a quantization of 10 minutes on the whole range, and no greater than 10 seconds in the range 10 seconds to 20 minutes. The Reporting Period Format field indicates the units for the value expressed in this field. Value '0' means that the RIT Indication operations should be performed as often as possible. + +Range: 0 - 120. + +##### Change Limit + +This field indicates a threshold for the change of AT or ATD /RTD values. If any requested AT or ATD/RTD value has changed more than the threshold since the last RIT Indication for the same request, a new RIT Indication operation is performed. In rigorous terms, noting RITi the last reported value, and RITc the current one, a RIT Indication operation is performed when RITc moves out of the interval [RITi-threshold, RITi+threshold]. + +This field is meaningless unless the Reporting Type is '1', i.e. open ended repetitive RIT Indications are requested, in which case the field is optional. If this field is not included and the Reporting Type '1', the threshold is infinite (in other words, the difference since the last RIT Indication for the same request is not a trigger for a new Indication). + +The encoding shall provide for a time in a range of 0.02 microseconds to 5 microseconds, with a quantization of 0.02 microseconds. + +Range: 1-250. + +##### Deviation Limit + +This field indicates the threshold for the deviation of the AT or ATD/RTD values. If any time the predicted AT or ATD/RTD value, as computed from the reported AT or ATD/RTD values and rates of change in the last RIT Indication operation, has deviated more than the threshold compared to the current measurement result, a new RIT Indication operation is performed. + +This field is meaningless unless the Reporting Type is '1', i.e. open ended repetitive RIT Indications have been requested, in which case the field is optional. If this field is not included and the Reporting Type is '1', the threshold is infinite (in other words, the difference with the predicted value is not a trigger for a new Indication). + +The encoding shall provide for the range 0.02 to 5 microseconds, with a quantization of 0.02 microseconds. + +Range: 1-250. + +#### B.1.2.2 Cell List IE + +This IE contains a list of one or several cells whose RIT information is requested. + +This IE contains the following fields. + +##### Number of Cells + +This field indicates the number of cells in this IE. This field is mandatory. + +Range: 1 - 16. + +The following fields are repeated the number of times included in the Number of Cells field. + +##### LAC + +This field indicates the Location Area Code of the cell whose RIT information is requested, within the PLMN. This field is mandatory. + +Range: 0 - 65 535. + +NOTE: The protocol does not provide for data exchange between SMLCs of different PLMNs. + +##### CI + +This field indicates the Cell Identity of the cell whose RIT information is requested, within the PLMN. This field is mandatory. + +Range: 0 - 65 535. + +#### B.1.2.3 Reference Clock IE + +This IE describes a reference clock. A clock includes a time reference, and a frequency reference. In this version of the document, the only supported method for indicating a time reference consists in indicating a particular frame in a particular reference cell. The frequency reference is then that of the cell. The time reference is then the beginning of this frame in the downlink direction, as perceived by a receiver as close as possible from transmitting antennae for the reference cell. In addition, and optionally, the time reference is indicated relative to a universal time reference, and an indication of the drift of the frequency reference relative to the universal time reference is provided. + +This IE contains the following fields. + +##### LAC + +This field indicates the Location Area Code of the reference cell, within the PLMN. This field is mandatory. + +Range: 0 - 65 535. + +NOTE: The protocol does not provide for data exchange between SMLCs of different PLMNs. + +##### CI + +This field indicates the Cell Identity of the reference cell, within the PLMN. This field is mandatory. + +Range: 0 - 65 535. + +##### Reference Frame Number + +This field indicates the TDMA frame number FN, as numbered according to 3GPP TS 25.010, of the reference cell corresponding to the reported values in this message. This field is mandatory. + +The encoding shall provide for a range of at least 2 hours before the instant the field is received. + +Range: 0 - 2 715 647. + +##### Absolute Time Present + +This field indicates whether AT of the reference cell is reported or not. This field is mandatory. + +'0': AT of reference cell is not reported; + +'1': AT of reference cell is reported. + +##### Universal Clock + +This field indicates the type of the universal reference clock for absolute time (AT) indications. This field is optional, and included only if the Absolute Time Present field is '1'. + +'0': GPS clock is used; + +'1': Galileo clock is used; + +'2': GLONASS clock is used; + +'3': QZSS clock is used; + +'4': BDS clock is used. + +##### Reference AT + +This field indicates the time of the reference instant (i.e., the starting moment of reference frame), relative to the universal reference clock indicated in the previous field. + +It is counted in two parts: seconds after last minute change, and nanoseconds after last second change This field is conditional, and included only if the Absolute Time Present field is '1'. + +Range: + +seconds: 0 - 59 + +nanoseconds: 0 - 999 999 999 + +##### Reference AT Change + +This field indicates the first time derivative of the AT value relative to the clock of the reference cell. A positive value indicates that the clock of the reference cell lags behind that of the universal reference clock. This field is conditional, and included only if the Absolute Time Present field is '1'. + +The range is -0,05 ... 0,05 ppm, with a quantization of 0,000 05 ppm. + +Range: -1 000 ... 1 000. + +##### Reference AT Quality Resolution + +Reference AT Quality Resolution field includes the resolution used in Reference AT Quality field. Encoding on 2 bits as follows + +| | | +|------|---------------------| +| '00' | 0.005 micro seconds | +| '01' | 0.01 micro seconds | +| '10' | 0.05 micro seconds | +| '11' | Reserved. | + +This field is conditional, and included only if the Absolute Time Present field is '1'. + +##### Reference AT Quality + +Reference AT Quality field includes the quality of reported RIT measurement. This Reference AT Quality field can be e.g. used to evaluate the reliability of AT measurements in the SMLC. Reference AT quality is defined as + +$$\text{Reference AT Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported AT value,}$$ + +where $x$ is the reported Reference AT value and $\mu = E[x]$ is its expectation value. The reporting resolution of Reference AT Quality is defined by Reference AT Quality resolution field. + +This field is conditional, and included only if the Absolute Time Present field is '1'. + +###### Reference AT Change Quality Resolution + +Reference AT Change Quality Resolution field includes the resolution used in Reference AT Change Quality field. Encoding on 2 bits as follows + +| | | +|------|--------------| +| '00' | 0,000 05 ppm | +| '01' | 0,000 1 ppm | +| '10' | 0,000 5 ppm | +| '11' | Reserved. | + +This field is conditional, and included only if the Absolute Time Present field is '1'. + +##### Reference AT Change Quality + +Reference AT Change Quality field includes the quality of reported Reference AT Change. This Reference AT Change Quality field can be e.g. used to evaluate the reliability of RIT measurements in the SMLC. Reference AT Change Quality is defined as + +$$\text{Reference AT Change Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported AT Change value}$$ + +where $x$ is the reported Reference AT Change and $\mu = E[x]$ is its expectation value. The reporting resolution of Reference AT Change Quality is defined by Reference AT Change Quality Resolution field. + +This field is conditional, and included only if the Absolute Time Present field is '1'. + +#### B.1.2.4 RIT Data IE + +This IE contains the requested RIT information. It contains the following fields. + +##### Number of Cells + +This field indicates the number of cells in this IE. This field is mandatory. + +Range: 1 - 16. + +##### ATD/RTD Quality Resolution + +ATD/RTD Quality Resolution field includes the resolution used in ATD/RTD Quality field. Encoding on 2 bits as follows + +| | | +|------|---------------------| +| '00' | 0,005 micro seconds | +| '01' | 0,01 micro seconds | +| '10' | 0,05 micro seconds | +| '11' | Reserved. | + +This field is mandatory. + +###### ATD/RTD Change Quality Resolution + +ATD/RTD Change Quality Resolution field includes the resolution used in ATD/RTD Change Quality field. Encoding on 2 bits as follows + +| | | +|------|--------------| +| '00' | 0,000 05 ppm | +| '01' | 0,000 1 ppm | +| '10' | 0,000 5 ppm | +| '11' | Reserved. | + +This field is mandatory. + +The following fields are repeated the number of times included in the Number of Cells field. + +##### LAC + +This field indicates the Location Area Code of the cell whose RIT information is given, within the PLMN. This field is mandatory. + +Range: 0 - 65 535. + +##### CI + +This field indicates the Cell Identity of the cell whose RIT information is given, within the PLMN. This field is mandatory. + +Range: 0 - 65 535. + +##### Cell Frame Number + +This field indicates the TDMA frame number, as numbered according to 3GPP TS 25.010, of the first whole slot that has been (or would have been) sent by the cell at the time reference or immediately after. This field is mandatory. + +Range: 0 - 2 715 647. + +###### ATD/RTD Value + +This field indicates elapsed time between starting moment of the reference frame and starting moment of the next whole neighbor frame in the downlink direction as perceived by a receiver as close as possible from transmitting antennae for the cell. The result is thus always positive. This field is mandatory. + +The encoding shall provide for a range of 0 to 1 250 bit periods, with a quantization of 0,005 microseconds (around 1,5 metres at light speed). + +Range: 0 ... 923 199 + +###### ATD/RTD Quality + +ATD/RTD Quality field includes the quality of reported RIT measurement. This ATD/RTD Quality field can be e.g. used to evaluate the reliability of RIT measurements in the SMLC. ATD/RTD quality is defined as + +$$\text{ATD/RTD Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported ATD/RTD value,}$$ + +where $x$ is the reported ATD/RTD value and $\mu = E[x]$ is its expectation value. The reporting resolution of ATD/RTD Quality is defined by ATD/RTD Quality resolution field. + +Range: 0 to 63 + +This field is mandatory. + +###### ATD/RTD Change + +This field indicates the first time derivative of the ATD/RTD value between the transmissions of signals from the reference cell and the measured cell. This field is mandatory. + +The encoding shall provide for a range of -0,10 ... 0,10 ppm , with a quantization of 0,000 05 ppm. + +Range: -2 000 ... 2 000. + +###### ATD/RTD Change Quality + +ATD/RTD Change Quality field includes the quality of reported ATD/RTD Change. This ATD/RTD Change Quality field can be e.g. used to evaluate the reliability of RIT measurements in the SMLC. ATD/RTD Change Quality is defined as + +$$\text{ATD/RTD Change Quality} = \sqrt{E[(x - \mu)^2]} = \text{Std of reported ATD/RTD Change value,}$$ + +where $x$ is the reported ATD/RTD Change and $\mu = E[x]$ is its expectation value. The reporting resolution of ATD/RTD Change Quality is defined by ATD/RTD Change Quality resolution field. + +Range: 0 to 63 + +This field is mandatory. + +B.1.2.5 (void) + +B.1.2.6 (void) + +B.1.2.7 (void) + +B.1.2.8 (void) + +B.1.2.9 (void) + +B.1.2.10 (void) + +B.1.2.11 (void) + +B.1.2.12 (void) + +B.1.2.13 (void) + +B.1.2.14 (void) + +B.1.2.15 (void) + +#### B.1.2.16 Deciphering Key Type IE + +This IE defines the type of deciphering keys, i.e. whether the keys are applicable to E-OTD or GPS positioning method. + +'0' E-OTD; + +'1' GPS. + +#### B.1.2.17 Deciphering Keys IE + +The contents of this IE are as in 3GPP TS 49.031 in the corresponding IE excluding the BSSAP-LE Information Element Identifier, the length indicator, and the spare bits. + +#### B.1.2.18 Location Area IE + +This IE includes the LAC of the Location Area. This IE contains the following fields. + +###### LAC + +This field indicates the Location Area Code of the location area whose deciphering keys are included in this IE. This field is mandatory. + +Range: 0 - 65 535. + +B.1.2.19 (void) + +# Annex C (informative): Change History + +| Meeting# | CR | Rev | Subject/Comment | New Version | +|--------------|----|-----|-----------------------------------------|-------------| +| January 2016 | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | | | | | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48049/18722c46c9e8475524e634dedd08bac2_img.jpg b/marked/Rel-16/48_series/48049/18722c46c9e8475524e634dedd08bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7f8f8d867c93ebc1184694848e1391d712eb81d --- /dev/null +++ b/marked/Rel-16/48_series/48049/18722c46c9e8475524e634dedd08bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cee202f5e7488b416ca88a1f02dad852edfe56e1e59ab9327ad3ec6094bcd0a8 +size 12232 diff --git a/marked/Rel-16/48_series/48049/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-16/48_series/48049/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9abe93abc864f3128a484374c286a608e1b1c10b --- /dev/null +++ b/marked/Rel-16/48_series/48049/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:437ef729dce532a86f922e866bdaab008f23316594a5001c641c1aa6e2f01885 +size 10306 diff --git a/marked/Rel-16/48_series/48049/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-16/48_series/48049/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d302bd54935b7bad7c21e802289a8ffe5447221a --- /dev/null +++ b/marked/Rel-16/48_series/48049/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6de4addb56907446ef0fe78ae7332e39fd279d724c50908f5221e0476b958a6c +size 12286 diff --git a/marked/Rel-16/48_series/48049/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/marked/Rel-16/48_series/48049/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..806341923def345ede72bc3cf20ed6642a291ead --- /dev/null +++ b/marked/Rel-16/48_series/48049/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c451939b0527c5cec9946c170d64a719d2f932a58e80b96ff64738680a268c9 +size 18946 diff --git a/marked/Rel-16/48_series/48049/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-16/48_series/48049/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31306d7f0f1ad3d6eb6303370a2573b6bda08885 --- /dev/null +++ b/marked/Rel-16/48_series/48049/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dc029344dfb361d56fb61c3b753c5a336705c006e6cb39012bbb04eacaf0d22 +size 16876 diff --git a/marked/Rel-16/48_series/48049/3c9703dd9f04f204e4b935c80eb96f0d_img.jpg b/marked/Rel-16/48_series/48049/3c9703dd9f04f204e4b935c80eb96f0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..758c39bcb5a142034c9571d3a9bb962808a4e9d7 --- /dev/null +++ b/marked/Rel-16/48_series/48049/3c9703dd9f04f204e4b935c80eb96f0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee5ce914260cfdc94efa16f07fc3260ee0ef5d700c041f3d5e110849d91c562f +size 19920 diff --git a/marked/Rel-16/48_series/48049/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/Rel-16/48_series/48049/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd5114b1f486f8f40641db3cb002c5392b32ebed --- /dev/null +++ b/marked/Rel-16/48_series/48049/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26ffd64b07d6e2ba6f0b9086ace050f5d28a258207a06f49af5885e42c235968 +size 19270 diff --git a/marked/Rel-16/48_series/48049/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Rel-16/48_series/48049/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2664515bdf2d0b89b6338ec2d87a4a8e2491064f --- /dev/null +++ b/marked/Rel-16/48_series/48049/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7106c3cd4dc56d8d79242e03fc383c7c5cf48ad662fa624a1fed0e2d4db88dd +size 16278 diff --git a/marked/Rel-16/48_series/48049/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg b/marked/Rel-16/48_series/48049/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..861a65007d1ec5dca9c9e6328c6ece8c82c4ec1b --- /dev/null +++ b/marked/Rel-16/48_series/48049/5391e1303dec02a02e7e42b5a4ffe58a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4de919068e457fe0178cab6bb600d32ec25a3f9ccff28c0e908dc37f0012bcc9 +size 12071 diff --git a/marked/Rel-16/48_series/48049/7b8b192e2853ef28d28eff0241ebe86b_img.jpg b/marked/Rel-16/48_series/48049/7b8b192e2853ef28d28eff0241ebe86b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a75a70e6712dd4d362d5dd90ecc924ead2669b4 --- /dev/null +++ b/marked/Rel-16/48_series/48049/7b8b192e2853ef28d28eff0241ebe86b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9657670f734382c77d4e9f6a3b6df9c0ff1db66c741f6caf305027a065dc7c4 +size 19487 diff --git a/marked/Rel-16/48_series/48049/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/48_series/48049/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12d095ddb1e85daba23303cb154fac74b0adf714 --- /dev/null +++ b/marked/Rel-16/48_series/48049/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a70ba2fa2429fbb51c7da7663b27d067acb191c7c35cafc205fa55ca0d38b564 +size 23347 diff --git a/marked/Rel-16/48_series/48049/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/Rel-16/48_series/48049/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69406e130bd6eb7acfc2e5bf9be474f3ef890875 --- /dev/null +++ b/marked/Rel-16/48_series/48049/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a43d51591cb06d49b2fc8bb80329c559f01ca0578fdd3aae107d889c56383481 +size 17135 diff --git a/marked/Rel-16/48_series/48049/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/48_series/48049/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6450422dd69cde2f8eb7e5b380479bd9d8cea9fe --- /dev/null +++ b/marked/Rel-16/48_series/48049/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8652b37230822ebc4f9ac4d77f70eb1f1420e0e1e51b61821aa40bd785e3815 +size 13435 diff --git a/marked/Rel-16/48_series/48049/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/marked/Rel-16/48_series/48049/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11764957a7a89cdf906ae4e44d5a01e6cb33affb --- /dev/null +++ b/marked/Rel-16/48_series/48049/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51ec5ca6a521e8bcc93b4614ac71fd4aa7df6725cb091d8694568e390b3df46a +size 12085 diff --git a/marked/Rel-16/48_series/48049/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Rel-16/48_series/48049/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d82ef076282f1dc128027a057524ee359cf39ea --- /dev/null +++ b/marked/Rel-16/48_series/48049/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4304e2b9eca32846b902842d85f3eb3a15b8f911bcf6326bc2f3831d7943ed11 +size 16364 diff --git a/marked/Rel-16/48_series/48049/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-16/48_series/48049/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5780b3ea3675df9b40a4cd6153313e8b2053aeb --- /dev/null +++ b/marked/Rel-16/48_series/48049/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b08ede3d3a817f6afa31931cc1954b876cec4a728a3e30f459fd5064254711ed +size 15883 diff --git a/marked/Rel-16/48_series/48049/a93de4c3f80bd4a972ab65510b09b68d_img.jpg b/marked/Rel-16/48_series/48049/a93de4c3f80bd4a972ab65510b09b68d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ad1bf3d2e65a4cb44262c7fa0a3f66ab5d61b05 --- /dev/null +++ b/marked/Rel-16/48_series/48049/a93de4c3f80bd4a972ab65510b09b68d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55a9c958276077926d8dd160ffd0063f37ce16a146c1229063651eadcabc2f2f +size 14134 diff --git a/marked/Rel-16/48_series/48049/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/48_series/48049/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6eb58ccf8dd8bf55da32a5f5c470d08ef9983d8 --- /dev/null +++ b/marked/Rel-16/48_series/48049/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc56e3bd885ec916d1d6463a215b0d3356ff3cf00c4b5aec4a67ad0427efe619 +size 15049 diff --git a/marked/Rel-16/48_series/48049/c0e369274e53b2e5364666be6f786c7a_img.jpg b/marked/Rel-16/48_series/48049/c0e369274e53b2e5364666be6f786c7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8dcf725b9b652b5b0d440cad5541eee3098a7c5 --- /dev/null +++ b/marked/Rel-16/48_series/48049/c0e369274e53b2e5364666be6f786c7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:824662d93a862a259b4722171ca6c88cb1816ffbd860a68e509284fa16c764fa +size 14807 diff --git a/marked/Rel-16/48_series/48049/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/marked/Rel-16/48_series/48049/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59eefcd5445beafb8274522011e17b2633d473cc --- /dev/null +++ b/marked/Rel-16/48_series/48049/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2778e73b55c6fa73322e6f93e968a313d041115198ff2866d448a6a20093334b +size 15788 diff --git a/marked/Rel-16/48_series/48049/ea49c15f36ffb089d44f1d793f013778_img.jpg b/marked/Rel-16/48_series/48049/ea49c15f36ffb089d44f1d793f013778_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72280fa37ee7ee23172e05431c64fecf8864403a --- /dev/null +++ b/marked/Rel-16/48_series/48049/ea49c15f36ffb089d44f1d793f013778_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6619406f6319cf73dbbb571ec4190fffa5d25fda5824a25098ce08f1fc632c4 +size 10031 diff --git a/marked/Rel-16/48_series/48049/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-16/48_series/48049/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7772a6d00886ea2e204a895362689ead71affc2d --- /dev/null +++ b/marked/Rel-16/48_series/48049/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:376c9d0bf12e445a86c00410d7107f61e4ffd0a1c87bbf8377c60ef6330b1ccc +size 15186 diff --git a/marked/Rel-16/48_series/48049/raw.md b/marked/Rel-16/48_series/48049/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dd9e94617547aeeda1ef419012d1041418d32a18 --- /dev/null +++ b/marked/Rel-16/48_series/48049/raw.md @@ -0,0 +1,2372 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 9 | +| 4.1 Procedure Specification Principles..... | 9 | +| 4.2 Specification Notations ..... | 9 | +| 5 Transport and Data Link layer ..... | 9 | +| 5.1 General ..... | 9 | +| 5.2 TCP /IP..... | 10 | +| 5.3 Data Link layer..... | 10 | +| 6 Functions of CBSP..... | 10 | +| 7 CBSP Procedures ..... | 11 | +| 7.1 Elementary Procedures..... | 11 | +| 7.2 Write-Replace..... | 11 | +| 7.2.1 General ..... | 11 | +| 7.2.2 Successful Operation..... | 12 | +| 7.2.2.1 General..... | 12 | +| 7.2.2.2 Broadcast request of a CBS message..... | 12 | +| 7.2.2.3 Broadcast request of an emergency message..... | 13 | +| 7.2.2.4 Returning WRITE-REPLACE COMPLETE message to CBC..... | 14 | +| 7.2.3 Unsuccessful Operation..... | 15 | +| 7.3 Kill..... | 16 | +| 7.3.1 General ..... | 16 | +| 7.3.2 Successful Operation..... | 16 | +| 7.3.2.1 General..... | 16 | +| 7.3.2.2 Termination of CBS message broadcast..... | 16 | +| 7.3.2.3 Termination of emergency message broadcast..... | 16 | +| 7.3.3 Unsuccessful Operation..... | 17 | +| 7.4 Load Status Enquiry ..... | 17 | +| 7.4.1 General ..... | 17 | +| 7.4.2 Successful Operation..... | 18 | +| 7.4.3 Unsuccessful Operation..... | 19 | +| 7.5 Message Status Query ..... | 19 | +| 7.5.1 General ..... | 19 | +| 7.5.2 Successful Operation..... | 20 | +| 7.5.3 Unsuccessful Operation..... | 21 | +| 7.6 Set DRX ..... | 21 | +| 7.6.1 General ..... | 21 | +| 7.6.2 Successful Operation..... | 22 | +| 7.6.3 Unsuccessful Operation..... | 23 | +| 7.7 Reset..... | 23 | +| 7.7.1 General ..... | 23 | +| 7.7.2 Successful Operation..... | 24 | +| 7.7.3 Unsuccessful Operation..... | 24 | +| 7.7a Keep Alive..... | 25 | +| 7.7a.1 General ..... | 25 | +| 7.7a.2 Successful Operation..... | 25 | +| 7.7a.3 Unsuccessful Operation..... | 26 | +| 7.8 Restart Indication ..... | 26 | +| 7.8.1 General ..... | 26 | +| 7.8.2 Successful Operation..... | 26 | + +| | | | +|-----------|--------------------------------------------------|----| +| 7.9 | Failure Indication ..... | 27 | +| 7.9.1 | General ..... | 27 | +| 7.9.2 | Successful Operation ..... | 27 | +| 7.10 | Error Indication ..... | 27 | +| 7.10.1 | General ..... | 27 | +| 7.10.2 | Successful Operation ..... | 28 | +| 8 | Elements for CBSP Communication..... | 28 | +| 8.1 | Message Functional Definitions and Contents..... | 28 | +| 8.1.1 | General ..... | 28 | +| 8.1.2 | Presence ..... | 29 | +| 8.1.3 | Message Contents..... | 29 | +| 8.1.3.1 | WRITE-REPLACE..... | 29 | +| 8.1.3.2 | WRITE-REPLACE COMPLETE..... | 30 | +| 8.1.3.3 | WRITE-REPLACE FAILURE ..... | 31 | +| 8.1.3.4 | KILL ..... | 32 | +| 8.1.3.5 | KILL COMPLETE ..... | 32 | +| 8.1.3.6 | KILL FAILURE ..... | 33 | +| 8.1.3.7 | LOAD QUERY..... | 33 | +| 8.1.3.8 | LOAD QUERY COMPLETE ..... | 33 | +| 8.1.3.9 | LOAD QUERY FAILURE..... | 34 | +| 8.1.3.10 | MESSAGE STATUS QUERY ..... | 34 | +| 8.1.3.11 | MESSAGE STATUS QUERY COMPLETE..... | 34 | +| 8.1.3.12 | MESSAGE STATUS QUERY FAILURE ..... | 35 | +| 8.1.3.13 | SET-DRX..... | 35 | +| 8.1.3.14 | SET-DRX COMPLETE ..... | 36 | +| 8.1.3.15 | SET-DRX FAILURE..... | 36 | +| 8.1.3.16 | RESET ..... | 36 | +| 8.1.3.17 | RESET COMPLETE ..... | 37 | +| 8.1.3.18 | RESET FAILURE ..... | 37 | +| 8.1.3.18a | KEEP-ALIVE ..... | 37 | +| 8.1.3.18b | KEEP-ALIVE COMPLETE ..... | 37 | +| 8.1.3.19 | RESTART..... | 38 | +| 8.1.3.20 | FAILURE..... | 38 | +| 8.1.3.21 | ERROR INDICATION..... | 38 | +| 8.2 | Information Element Definitions ..... | 39 | +| 8.2.1 | General ..... | 39 | +| 8.2.2 | Message Type..... | 40 | +| 8.2.3 | Message Content ..... | 41 | +| 8.2.4 | Old Serial Number..... | 41 | +| 8.2.5 | New Serial Number ..... | 41 | +| 8.2.6 | Cell List ..... | 42 | +| 8.2.7 | Category ..... | 44 | +| 8.2.8 | Repetition Period ..... | 44 | +| 8.2.9 | Number of Broadcasts Requested ..... | 45 | +| 8.2.10 | Number of Broadcasts Completed List ..... | 45 | +| 8.2.11 | Failure List..... | 46 | +| 8.2.12 | Radio Resource Loading List ..... | 47 | +| 8.2.13 | Cause ..... | 48 | +| 8.2.14 | Data Coding Scheme ..... | 49 | +| 8.2.15 | Recovery Indication..... | 49 | +| 8.2.16 | Message Identifier ..... | 49 | +| 8.2.17 | Emergency Indicator ..... | 50 | +| 8.2.18 | Warning Type..... | 50 | +| 8.2.19 | Warning Security Information..... | 50 | +| 8.2.20 | Channel Indicator ..... | 50 | +| 8.2.21 | Number of Pages ..... | 51 | +| 8.2.22 | Schedule Period ..... | 51 | +| 8.2.23 | Number of Reserved Slots..... | 52 | +| 8.2.24 | Broadcast Message Type..... | 52 | +| 8.2.25 | Warning Period..... | 52 | +| 8.2.26 | Length Indicator ..... | 53 | + +8.2.27 Keep Alive Repetition Period.....53 +9 List of system parameters .....54 +9.1 Timers in the CBC.....54 +Annex A (informative): Change History.....55 + +# --- 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 *Cell Broadcast Service Protocol (CBSP)* between the Cell Broadcast Centre (CBC) and the Base Station Controller (BSC). + +# --- 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.041: "Technical realization of Cell Broadcast Service (CBS)". +- [2] 3GPP TS 23.003: "Numbering, addressing and identification". +- [3] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [4] 3GPP TS 23.038: "Alphabets and language-specific information". +- [5] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols". +- [6] IETF RFC 793 (September 1981): "Transmission Control Protocol". +- [7] IETF RFC 2507 (February 1999): "IP header compression". +- [8] IETF RFC 1990 (August 1996): "The PPP Multilink Protocol (MP)". +- [9] IETF RFC 2686 (September 1996): "The Multi-Class Extension to Multi-Link PPP". +- [10] IETF RFC 2509 (February 1999): "IP Header Compression over PPP". +- [11] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [12] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [13] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol". +- [14] 3GPP TS 23.002: "Network architecture". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**CBS message:** An information message broadcasted on the basic or extended cell broadcast channel (CBCH) in unacknowledged mode to mobile stations located within the Cell Broadcast area. A CBS message may contain information such as road traffic or weather information, originating from a Cell Broadcast Entity (CBE) communicating with the CBC (see 3GPP TS 23.041 [1]). + +**CBS message reference:** Uniquely identifies a CBS message by the four elements: Message Identifier, Serial Number, Cell Identifier and Channel Indicator. + +**Cell Broadcast area:** An area comprising of one or more cells in which the CBS message or the emergency message is broadcasted. A Cell Broadcast area is always contained within a BSC area (see 3GPP TS 23.002 [14]). + +**CBS message operational state:** A cell in CBS message operational state is able to broadcast CBS messages. + +**Emergency message:** A warning message conveying a small amount of data to indicate the imminent occurrence of an emergency such as earthquake, tsunami etc. The emergency message is broadcasted to mobile stations in idle mode, packet idle mode and dedicated mode (see 3GPP TS 44.018 [12]) and to mobile stations in packet transfer mode and dual transfer mode (see 3GPP TS 44.060 [13]) located within the Cell Broadcast area. + +**Emergency message operational state:** A cell in emergency message operational state is able to broadcast emergency messages. + +**Emergency message reference:** Uniquely identifies an emergency message by the three elements: Message Identifier, Serial Number and Cell Identifier. + +**Elementary Procedure:** CBSP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interactions between the CBC and the BSC. 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. Support of parallel procedures in the BSC is optional. + +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 EP is successfully completed. + +### Unsuccessful + +- A signalling message explicitly indicates that the EP failed. +- On time supervision expiry (i.e. absence of expected response). + +Class 2 EPs are always considered as successful. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|---------------------------------------| +| BSC | Base Station Controller | +| CBC | Cell Broadcast Centre | +| CBCH | Cell Broadcast Channel | +| CBE | Cell Broadcast Entity | +| CBS | Cell Broadcast Service | +| CBSP | Cell Broadcast Service Protocol | +| EP | Elementary Procedure | +| ETWS | Earthquake and Tsunami Warning System | +| MS | Mobile Station | +| SMSCB | Short Message Service Cell Broadcast | + +# --- 4 General + +## 4.1 Procedure Specification Principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the BSC exactly and completely. The CBC functional behaviour is left unspecified. + +The following specification principles have been applied for the procedure text in clause 7: + +- The procedure text discriminates between: + - 1) Functionality which "shall" be executed: + - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. + - 2) Functionality which "shall, if supported" be executed: + - The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. + +## 4.2 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 8.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ". | + +# --- 5 Transport and Data Link layer + +## 5.1 General + +TCP over IP shall be supported as the transport for data streams on the BSC-CBC interface. The data link layer is as specified in subclause 5.3. + +During normal operation the CBC initiates all message transfer and query operations. The BSC responds to the message transfer and query operations initiated by the CBC. + +The BSC only initiates the message transfer in case an error (Failure Indication procedure) or recovery (Restart Indication procedure) is to be reported. + +The node initiating the message transfer is also responsible for the establishment of the TCP connection, in case no TCP connection already exist. An already established TCP connection may be used for message transfer. + +The initiator of a connection is responsible for the termination of the TCP connection. + +## 5.2 TCP /IP + +The transport protocol used shall be TCP, which is specified in RFC 793 [6]. + +The transport bearer is identified by the TCP port number and the IP address (source TCP port number, destination TCP port number, source IP address, destination IP address). + +The TCP Destination Port number for CBSP messages is 48049/tcp. It is the registered port number for 3GPP Cell Broadcast Service Protocol CBSP (3gpp-cbsp). + +The 3gpp-cbsp destination port number 48049/tcp shall be used by both entities (BSC or CBC) whenever it sets up a new TCP connection. When it sends CBSP messages on an existing TCP connection, the sending entity (BSC or CBC) shall use as TCP destination port number either 48049/tcp if it was the initiator of this TCP connection, or the TCP source port number that was received from the peer entity that had initiated this existing TCP connection. + +An IP BSC/CBC-node shall support IPv4. The support of IPv6 is optional. + +IP dual stack support is recommended for the potential transition period from IPv4 to IPv6 in the transport network. + +## 5.3 Data Link layer + +It is recommended that a BSC/CBC using IP transport implement the data link layer using Ethernet. + +NOTE: This does not preclude the single implementation and use of any other data link layer protocol fulfilling the GERAN requirements toward the upper layers. + +A BSC/CBC using IP transport having interfaces connected via low bandwidth PPP links like E1/T1 shall also support IP Header Compression [7] and the PPP extensions ML/MC-PPP [8], [9]. In this case the negotiation of header compression [7] over PPP shall be performed according to [10]. + +# --- 6 Functions of CBSP + +The CBSP has the following functions: + +- Message Handling: This function is responsible for enabling the broadcast of new CBS and emergency messages, replacing CBS and emergency messages currently being broadcasted and for terminating the broadcast of specific CBS and emergency messages. This function may also be used to obtain the message status of a specific CBS message. +- DRX Handling: This function is responsible for the configuration of the SMSCB DRX parameters. +- Load Handling: This function determines the load status of the broadcast channels at any particular point in time. +- Reset: This function terminates the broadcasting of all CBS and emergency messages in one or more cells. +- Error Handling: This function allows reporting of general error situations, for which function specific error messages have not been defined. +- Supervision Handling: This function handles the supervision of the CBSP availability between the CBC and the BSC. + +These functions are implemented by one or several CBSP elementary procedures described in clause 7. + +# --- 7 CBSP Procedures + +## 7.1 Elementary Procedures + +In the following tables, all EPs are divided into Class 1 and Class 2 Procedures. + +**Table 7.1.1: Class 1 Procedures** + +| 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 STATUS QUERY | MESSAGE STATUS QUERY COMPLETE | MESSAGE STATUS QUERY FAILURE | +| Set DRX | SET-DRX | SET-DRX COMPLETE | SET-DRX FAILURE | +| Reset | RESET | RESET COMPLETE | RESET FAILURE | +| Keep Alive | KEEP-ALIVE | KEEP-ALIVE COMPLETE | - | + +**Table 7.1.2: Class 2 Procedures** + +| Elementary Procedure | Message | +|----------------------|------------------| +| Restart Indication | RESTART | +| Failure Indication | FAILURE | +| Error Indication | ERROR INDICATION | + +## 7.2 Write-Replace + +### 7.2.1 General + +The purpose of the Write-Replace procedure is to broadcast a new CBS message or emergency message or to replace an ongoing CBS message or emergency message broadcast with a new CBS message or emergency message. + +### 7.2.2 Successful Operation + +#### 7.2.2.1 General + +![Sequence diagram showing the successful operation of the Write-Replace procedure between a BSC and a CBC. The CBC sends a WRITE-REPLACE message to the BSC, and the BSC responds with a WRITE-REPLACE COMPLETE message.](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant CBC + Note left of BSC: + Note right of CBC: + CBC->>BSC: WRITE-REPLACE + BSC-->>CBC: WRITE-REPLACE COMPLETE + +``` + +Sequence diagram showing the successful operation of the Write-Replace procedure between a BSC and a CBC. The CBC sends a WRITE-REPLACE message to the BSC, and the BSC responds with a WRITE-REPLACE COMPLETE message. + +**Figure 7.2.2.1.1: Write-Replace Procedure: Successful Operation** + +The Write-Replace procedure is initiated by the CBC sending the WRITE-REPLACE message to the BSC (see figure 7.2.2.1.1). + +The WRITE-REPLACE message may be sent as a request to broadcast a new CBS message or emergency message without replacing an ongoing CBS message or emergency message broadcast, or as a request to replace an ongoing CBS message or emergency message broadcast with a new CBS message or emergency message. A WRITE-REPLACE message shall not contain a simultaneous broadcast request of a CBS message and an emergency message. + +Broadcast request of a CBS message is defined in subclause 7.2.2.2 while broadcast request of an emergency message is defined in subclause 7.2.2.3. + +#### 7.2.2.2 Broadcast request of a CBS message + +A CBS message is uniquely identified by the four elements *Message Identifier* IE, Cell Identifier field in the *Cell List* IE, Serial Number field in the *New Serial Number* IE or in the *Old Serial Number* IE and the *Channel Indicator* IE. If only the *New Serial Number* IE, and not the *Old Serial Number* IE, is included in the WRITE-REPLACE message, then the BSC shall interpret the message as a write request, i.e. a broadcast request of a new CBS message without replacing an ongoing CBS message broadcast. The new CBS message is identified by the four elements *Message Identifier* IE, the twelve most significant bits of the *New Serial Number* IE, Cell Identifier field in the *Cell List* IE and the *Channel Indicator* IE. + +If both the *New Serial Number* IE and the *Old Serial Number* IE are present in the WRITE-REPLACE message, then the BSC shall interpret the message as a replace request, i.e. a request to replace an ongoing CBS message broadcast with a new CBS message. In this case the BSC shall start the Write-Replace procedure by terminating the ongoing CBS message broadcast, as defined in subclause 7.3.2.2, before broadcasting the new CBS message. The replaced CBS message is identified by the four elements *Message Identifier* IE, the twelve most significant bits of the *Old Serial Number* IE, Cell Identifier field in the *Cell List* IE and the *Channel Indicator* IE. + +If termination of the replaced CBS message fails in a cell, then the BSC shall not proceed with the broadcast of the new CBS message for this particular cell. After completing the Write-Replace procedure in the remaining cells, the BSC shall return the WRITE-REPLACE FAILURE message to the CBC, see subclause 7.2.3. + +A CBS message may be broadcasted on one of two different cell broadcast channels, a basic channel or an extended channel (see 3GPP TS 45.002 [11]), as indicated by the *Channel Indicator* IE. + +The BSC initiates broadcasting of the CBS message within the Cell Broadcast area, i.e. in the cell(s) as indicated by the Cell Identifier field in the *Cell List* IE. + +The BSC shall broadcast the CBS message according to the value of the *Number of Broadcasts Requested* IE and the *Repetition Period* IE. If the value of *Number of Broadcasts Requested* IE is set to "0", the BSC shall broadcast the CBS message until the CBC requests otherwise. If the value is different from "0", the BSC shall broadcast the CBS message as many times as indicated in the *Number of Broadcasts Requested* IE. + +The *Repetition Period* IE indicates the periodicity of which the CBS message is to be broadcasted. + +In the event of a conflict where the BSC has more than one CBS message to send at the same time, the BSC shall decide the order of such CBS messages as an implementation matter. + +The BSC shall accept the broadcast request of a CBS message according to the value of the *Category* IE as follows: + +- If the value of *Category* IE is indicated as "High Priority", then the BSC shall accept the broadcast request if message slots according to the *Repetition Period* IE are available on the broadcast channel following the scheduling of already accepted high and/or normal priority CBS messages. The first broadcast of a high priority CBS message is performed at the earliest opportunity and the subsequent broadcasts according to the *Repetition Period* IE. +- If the value of *Category* IE is indicated as "Normal", then the BSC shall accept the broadcast request if message slots according to the *Repetition Period* IE are available on the broadcast channel following the scheduling of already accepted high and/or normal priority CBS messages. The broadcast of a normal priority CBS message is always performed according to the *Repetition Period* IE. +- If the value of *Category* IE is indicated as "Background", then the BSC shall accept the broadcast request if message slots according to the *Repetition Period* IE are available on the broadcast channel following the scheduling of high and/or normal priority CBS messages and/or already accepted background CBS messages. The broadcast of a background CBS message is performed according to the *Repetition Period* IE. + +NOTE: The repetition frequency of an ongoing CBS message broadcast of type "Background" may be reduced if a CBS message broadcast request of type "Normal" or "High Priority" is received in the BSC for the same cell. If message slots on the particular broadcast channel become available again, the requested repetition period of the background CBS message shall be resumed. + +*Number of Pages* IE indicates the total number of pages included in the CBS message, i.e. the number of *Message Content* IE's included in the WRITE-REPLACE message. The BSC shall pass the *Data Coding Scheme* IE and *Message Content* IE transparently to the radio interface protocol. + +If the Write-Replace procedure is successful in all cells as indicated in the *Cell List* IE, the BSC shall return the WRITE-REPLACE COMPLETE message to the CBC as described in subclause 7.2.2.4. + +If the Write-Replace procedure fails in at least one cell, the BSC shall respond to the CBC by sending the WRITE-REPLACE FAILURE message, see subclause 7.2.3. + +After completion of the broadcast according to the associated *Number of Broadcasts Requested* IE and the *Repetition Period* IE, the BSC shall remove any reference to the concerned CBS message. + +#### 7.2.2.3 Broadcast request of an emergency message + +The presence of the *Emergency Indicator* IE indicates that the WRITE-REPLACE message contains an emergency message (e.g. an ETWS Primary Notification message). + +An emergency message is uniquely identified by the three elements *Message Identifier* IE, Cell Identifier field in the *Cell List* IE and the Serial Number field in the *New Serial Number* IE or in the *Old Serial Number* IE. + +If only the *New Serial Number* IE, and not the *Old Serial Number* IE, is included in the WRITE-REPLACE message, then the BSC shall interpret the message as a write request, i.e. a broadcast request of a new emergency message without replacing an ongoing emergency message broadcast. The new emergency message is identified by the three elements *Message Identifier* IE, the twelve most significant bits of the *New Serial Number* IE and Cell Identifier field in the *Cell List* IE. + +If both the *New Serial Number* IE and the *Old Serial Number* IE are present in the WRITE-REPLACE message, then the BSC shall interpret the message as a replace request, i.e. a request to replace an ongoing emergency message broadcast with a new emergency message. The BSC shall then start the Write-Replace procedure by terminating the ongoing emergency message broadcast, as described in subclause 7.3.2.3, before broadcasting the new emergency message. The replaced emergency message is identified by the three elements *Message Identifier* IE, the twelve most significant bits of the *Old Serial Number* IE and Cell Identifier field in the *Cell List* IE. + +If termination of the replaced emergency message fails in a cell, then the BSC shall not proceed with the broadcast of the new emergency message for this particular cell. After completing the Write-Replace procedure in the remaining cells, the BSC shall return the WRITE-REPLACE FAILURE message to the CBC, see subclause 7.2.3. + +The BSC shall construct and send the emergency message (e.g. an ETWS Primary Notification message) to mobile stations located within the Cell Broadcast area, i.e. to cell(s) as identified by the Cell Identifier field in the *Cell List* IE. + +*Warning Type* IE and *Warning Security Information* IE, if present, contains ETWS related warning information. These IE's are sent transparently, as part of the ETWS Primary Notification message, to the mobile station. + +The ETWS Primary Notification message is broadcasted to mobile stations in idle mode, packet idle mode and dedicated mode (see 3GPP TS 44.018 [12]) and to mobile stations in packet transfer mode and dual transfer mode (see 3GPP TS 44.060 [13]) located within the Cell Broadcast area. + +The BSC shall broadcast the emergency message for the duration of time as indicated in the *Warning Period* IE or until the CBC requests otherwise. + +Only one emergency message at the time can be broadcasted in a cell. If a write request is received for a cell where an emergency message broadcast is currently ongoing, the write request is considered as failed, see subclause 7.2.3. + +If the Write-Replace procedure is successful in all cell(s) as indicated in the *Cell List* IE, the BSC shall return the WRITE-REPLACE COMPLETE message to the CBC as described in subclause 7.2.2.4. + +If the Write-Replace procedure fails in at least one cell, the BSC shall respond to the CBC by sending the WRITE-REPLACE FAILURE message, see subclause 7.2.3. + +#### 7.2.2.4 Returning WRITE-REPLACE COMPLETE message to CBC + +After completion of the Write-Replace procedure in the BSC, the WRITE-REPLACE COMPLETE message is sent to the CBC containing the *Message Identifier* IE, the *New Serial Number* IE and optionally the *Channel Indicator* IE, if received in the WRITE-REPLACE message, together with the *Number of Broadcasts Completed List* IE or the *Cell List* IE. + +Depending on the request of the WRITE-REPLACE message either the *Number of Broadcasts Completed List* IE or the *Cell List* IE is returned in the WRITE-REPLACE COMPLETE message. If the WRITE-REPLACE COMPLETE message is returned to the CBC, + +- as a response to a write request operation (i.e. without replacing an ongoing CBS message or emergency message broadcast) then the Cell Identifier for each cell is included in the *Cell List* IE. + +- as a response to a replace request operation of an ongoing CBS message broadcast, then the *Number of Broadcasts Completed List* IE contains for each cell the number of broadcasts of the replaced CBS message. +- as a response to a replace request operation of an ongoing emergency message broadcast then the Cell Identifier for each cell is included in the *Cell List* IE. + +The *Old Serial Number* IE shall only be provided in the WRITE-REPLACE COMPLETE message if the message is returned as a response to a replace request operation. + +When the *Number of Broadcasts Completed List* IE is returned to the CBC as a response to a replace request operation of an ongoing CBS message broadcast and the number of broadcasts is not known for a particular cell, then the Number of Broadcasts Completed field shall be set to value "0" and the Number of Broadcasts Info field shall be set to "unknown" for this cell. + +If the actual number of broadcasts for a particular cell is greater than the value reported in the Number of Broadcasts Completed field, then the Number of Broadcasts Info field shall be set to value "overflow" to indicate that the counter for the specific cell has overflowed. + +### 7.2.3 Unsuccessful Operation + +![Sequence diagram illustrating the Unsuccessful Operation of the Write-Replace procedure. The diagram shows two lifelines: BSC (Base Station Controller) and CBC (Core Network Controller). The CBC sends a WRITE-REPLACE message to the BSC. The BSC responds with a WRITE-REPLACE FAILURE message to the CBC.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` + +sequenceDiagram + participant CBC + participant BSC + Note left of BSC: + Note right of CBC: + CBC->>BSC: WRITE-REPLACE + BSC-->>CBC: WRITE-REPLACE FAILURE + +``` + +Sequence diagram illustrating the Unsuccessful Operation of the Write-Replace procedure. The diagram shows two lifelines: BSC (Base Station Controller) and CBC (Core Network Controller). The CBC sends a WRITE-REPLACE message to the BSC. The BSC responds with a WRITE-REPLACE FAILURE message to the CBC. + +**Figure 7.2.3.1: Write-Replace Procedure: Un-Successful Operation** + +If the Write-Replace procedure fails in at least one cell as specified in the *Cell List* IE in the WRITE-REPLACE message, then the BSC shall return the WRITE-REPLACE FAILURE message to the CBC. A list of cell(s) for which the requested write or replace operation can not be completed shall be included in the *Failure List* IE and provided in the WRITE-REPLACE FAILURE message. For each cell in the *Failure List* IE a Cause value is included, identifying the reason for the failure. + +The WRITE-REPLACE FAILURE message may also include cell(s) for which the requested write or replace operation is successful. If the Write-Replace procedure is successful in at least one cell in the BSC, this cell shall be identified in the *Number of Broadcasts Completed List* IE or in the *Cell List* IE, see sub-clause 7.2.2.4, and provided in the WRITE-REPLACE FAILURE message. + +If the WRITE-REPLACE message sent from the CBC: + +- contained a *New Serial Number* IE but not an *Old Serial Number* IE (i.e. a write request operation), and the CBS message or emergency message reference is already in use in the BSC, it shall consider the Write-Replace procedure as failed for this cell. The BSC shall then return the WRITE-REPLACE FAILURE message with the Cell Identifier of this particular cell included in the *Failure List* IE together with the Cause value "Message-reference-already-used". No entry is made in the *Number of Broadcasts Completed List* IE or in the *Cell List* IE for this particular cell. +- contained both the *New Serial Number* IE and the *Old Serial Number* IE (i.e. a replace request operation), and the old CBS message or emergency message reference is unknown to the BSC (i.e. the BSC can not terminate the CBS message or emergency message) for a particular cell, the BSC shall consider the Write-Replace procedure as failed for this cell. The BSC shall then return the WRITE-REPLACE FAILURE message with the + +Cell Identifier of this particular cell included in the *Failure List* IE together with the Cause value “Message-reference-not-identified”. No entry is made in the *Number of Broadcasts Completed List* IE or in the *Cell List* IE for this particular cell. + +In this case the *Old Serial Number* IE provided in the WRITE-REPLACE FAILURE message refers to the message for which the *Failure List* IE is supplied. + +- contained both the *New Serial Number* IE and the *Old Serial Number* IE, and the new CBS message reference is already in use in the BSC, it shall consider the Write-Replace procedure as failed for this cell. The BSC shall then return the WRITE-REPLACE FAILURE message with the Cell Identifier of this particular cell included in the *Failure List* IE together with the Cause value “Message-reference-already-used”. An entry is made in the *Number of Broadcasts Completed List* IE for the killed CBS message for this particular cell. + +In this case the *New Serial Number* IE provided in the WRITE-REPLACE FAILURE message refers to the message for which the *Failure List* IE is supplied and the *Old Serial Number* IE to the message for which the *Number of Broadcasts Completed List* IE is supplied. + +## 7.3 Kill + +### 7.3.1 General + +The purpose of the Kill procedure is to terminate the broadcast of a specific CBS message or emergency message. + +### 7.3.2 Successful Operation + +#### 7.3.2.1 General + +![Sequence diagram illustrating the Kill Procedure: Successful Operation. The diagram shows two lifelines: BSC (Base Station Controller) on the left and CBC (Cell Broadcast Center) on the right. The CBC sends a KILL message to the BSC, and the BSC responds with a KILL COMPLETE message.](18722c46c9e8475524e634dedd08bac2_img.jpg) + +``` +sequenceDiagram + participant CBC + participant BSC + Note left of BSC: + Note right of CBC: + CBC->>BSC: KILL + BSC-->>CBC: KILL COMPLETE +``` + +Sequence diagram illustrating the Kill Procedure: Successful Operation. The diagram shows two lifelines: BSC (Base Station Controller) on the left and CBC (Cell Broadcast Center) on the right. The CBC sends a KILL message to the BSC, and the BSC responds with a KILL COMPLETE message. + +Figure 7.3.2.1.1: Kill Procedure: Successful Operation + +The Kill procedure is initiated by the CBC sending the KILL message to the BSC (see figure 7.3.2.1.1). The KILL message may be sent in purpose to terminate the broadcasting of a CBS message (see subclause 7.3.2.2) or to terminate the broadcasting of an emergency message (see subclause 7.3.2.3). + +#### 7.3.2.2 Termination of CBS message broadcast + +Upon receipt of the KILL message the BSC shall stop broadcasting the CBS message identified by the *Message Identifier* IE, the twelve most significant bits of the *Old Serial Number* IE and the *Channel Indicator* IE, for the cell(s) as indicated in the *Cell List* IE. + +After termination of the broadcast the BSC shall remove the CBS message, as well as any reference to it, for the cell(s) as indicated in the *Cell List* IE. + +The BSC shall respond to the CBC by sending the KILL COMPLETE message containing the *Message Identifier* IE, the *Old Serial Number* IE and the *Channel Indicator* IE. The KILL COMPLETE message also contains the *Number of Broadcasts Completed List* IE indicating for each cell the number of times the CBS message was broadcasted. + +If the number of broadcasts is not known for a particular cell, then the Number of Broadcasts Completed field shall be set to value "0" and the Number of Broadcasts Info field shall be set to "unknown" for this cell. + +If the actual number of broadcasts for a particular cell is greater than the value reported in the Number of Broadcasts Completed field, then the Number of Broadcasts Info field shall be set to value "overflow" to indicate that the counter for the specific cell has overflowed. + +If the Kill procedure fails in at least one cell, the BSC shall respond to the CBC by sending the KILL FAILURE message, see subclause 7.3.3. + +#### 7.3.2.3 Termination of emergency message broadcast + +Upon receipt of the KILL message the BSC shall stop broadcasting the emergency message identified by the *Message Identifier* IE and the twelve most significant bits of the *Old Serial Number* IE for the cell(s) as indicated in the *Cell List* IE. After termination of the broadcast the BSC shall remove the emergency message, as well as any reference to it, for the cell(s) as indicated in the *Cell List* IE. + +The BSC shall respond to the CBC by sending the KILL COMPLETE message with the *Message Identifier* IE, the *Old Serial Number* IE and the *Cell List* IE, containing the cells for which the kill operation succeeded, included in the message. + +If the Kill procedure fails in at least one cell, the BSC shall respond to the CBC by sending the KILL FAILURE message, see subclause 7.3.3. + +### 7.3.3 Unsuccessful Operation + +![Sequence diagram illustrating the Kill Procedure: Un-Successful Operation. The diagram shows two vertical lifelines, BSC and CBC. The CBC sends a 'KILL' message to the BSC. The BSC then sends a 'KILL FAILURE' message back to the CBC. Both lifelines end with a thick horizontal bar at the bottom.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note left of BSC: + Note right of CBC: + CBC->>BSC: KILL + BSC-->>CBC: KILL FAILURE + Note left of BSC: + Note right of CBC: +``` + +Sequence diagram illustrating the Kill Procedure: Un-Successful Operation. The diagram shows two vertical lifelines, BSC and CBC. The CBC sends a 'KILL' message to the BSC. The BSC then sends a 'KILL FAILURE' message back to the CBC. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 7.3.3.1: Kill Procedure: Un-Successful Operation** + +If the BSC fails to terminate the broadcasting of the CBS message or the emergency message in at least one cell as indicated in the *Cell List* IE, the BSC shall return the KILL FAILURE message to the CBC. Cell(s) for which the requested kill operation can not be performed (e.g. if the CBS or emergency message reference is not recognized in the BSC) shall be included in the *Failure List* IE and provided in the KILL FAILURE message. For each cell in the *Failure List* IE a Cause value is included, identifying the reason for the failure. + +If the Kill procedure is successful in at least one cell in the BSC, this cell shall be identified in the *Number of Broadcasts Completed List* IE, or in the *Cell List* IE, and provided in the KILL FAILURE message, see subclause 7.3.2.2 or 7.3.2.3. + +The sum of the cell(s) included in the *Number of Broadcasts Completed List* IE, or in the *Cell List* IE, and the *Failure List* IE shall be equal to the sum of cell(s) as included in the *Cell List* IE in the KILL message. + +## 7.4 Load Status Enquiry + +### 7.4.1 General + +The purpose of the Load Status Enquiry procedure is to obtain the current load status of the CBCH radio resources within a cell. + +### 7.4.2 Successful Operation + +![Sequence diagram of the Load Status Enquiry Procedure: Successful Operation. It shows two lifelines: BSC and CBC. The CBC sends a 'LOAD QUERY' message to the BSC. The BSC responds with a 'LOAD QUERY COMPLETE' message to the CBC.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note right of CBC: LOAD QUERY + CBC->>BSC: LOAD QUERY + Note left of BSC: LOAD QUERY COMPLETE + BSC->>CBC: LOAD QUERY COMPLETE +``` + +Sequence diagram of the Load Status Enquiry Procedure: Successful Operation. It shows two lifelines: BSC and CBC. The CBC sends a 'LOAD QUERY' message to the BSC. The BSC responds with a 'LOAD QUERY COMPLETE' message to the CBC. + +**Figure 7.4.2.1: Load Status Enquiry Procedure: Successful Operation** + +The Load Status Enquiry procedure is initiated by the CBC sending the LOAD QUERY message to the BSC (see figure 7.4.2.1) containing a *Cell List* IE, for which cell(s) the current CBCH load status is required, and the *Channel Indicator* IE. + +Two CBCH radio resource load values per cell shall be provided by the BSC. + +The first value, included in the Radio Resource Load 1 field, shall be calculated as the number of used CBCH message slots in relation to the number of available CBCH message slots. Number of used CBCH message slots is defined as message slots reserved for schedule messages, message slots used for high and normal priority CBS messages according to their requested repetition period and slots reserved for "free message slot reading advised" (see 3GPP TS 44.012 [3]). + +NOTE 1: CBCH message slots used for unscheduled scheduled messages shall not be considered as used CBCH message slots when calculating the Radio Resource Load 1 field. + +The second value, included in the Radio Resource Load 2 field, shall be calculated as the number of CBCH message slots used for background CBS messages according to their requested repetition period in relation to the number of available CBCH message slots. + +NOTE 2: The repetition period of an ongoing background CBS message broadcast may be reduced if a high or normal priority CBS message broadcast request is received in the BSC for the same cell. The calculation of the Radio Resource Load 2 field shall however always be calculated according to the requested repetition period of the background CBS message. + +After completion of the CBCH radio resource load calculation for the requested cell(s) the BSC shall respond to the CBC by sending the LOAD QUERY COMPLETE message containing the *Radio Resource Loading List* IE, indicating the current load status of the included cell(s), and the *Channel Indicator* IE. + +If the Load Status Enquiry procedure fails in at least one cell, the BSC shall respond to the CBC by sending the LOAD QUERY FAILURE message, see subclause 7.4.3. + +### 7.4.3 Unsuccessful Operation + +![Sequence diagram for Load Status Enquiry Procedure: Un-Successful Operation](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +``` +sequenceDiagram + participant CBC + participant BSC + Note left of BSC: + Note right of CBC: + CBC->>BSC: LOAD QUERY + BSC-->>CBC: LOAD QUERY FAILURE +``` + +The diagram shows a sequence of messages between a CBC (Cell Broadcast Center) and a BSC (Base Station Controller). The CBC sends a 'LOAD QUERY' message to the BSC. The BSC responds with a 'LOAD QUERY FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for Load Status Enquiry Procedure: Un-Successful Operation + +**Figure 7.4.3.1: Load Status Enquiry Procedure: Un-Successful Operation** + +If upon receipt of the LOAD QUERY message the BSC can not calculate the current CBCH radio resource load status in one or several cells as indicated in the *Cell List* IE, the BSC shall respond to the CBC by sending the LOAD QUERY FAILURE message. Cell(s), for which the CBCH radio resource load can not be calculated, shall be included in the *Failure List* IE together with a Cause value identifying the reason for the failure. + +If the Load Status Enquiry procedure is successful in at least one cell in the BSC, this cell shall be identified in the *Radio Resource Loading List* IE (as well as their current load status) and be included in the LOAD QUERY FAILURE message. + +The sum of the cell(s) included in the *Radio Resource Loading List* IE and *Failure List* IE shall be equal to the sum of cell(s) as included in the *Cell List* IE in the LOAD QUERY message. + +## 7.5 Message Status Query + +### 7.5.1 General + +The purpose of the Message Status Query procedure is to obtain the message status of a specific CBS message in the BSC. + +### 7.5.2 Successful Operation + +![Sequence diagram for Message Status Query Procedure: Successful Operation](7b8b192e2853ef28d28eff0241ebe86b_img.jpg) + +``` +sequenceDiagram + participant CBC + participant BSC + Note left of BSC: + Note right of CBC: + CBC->>BSC: MESSAGE STATUS QUERY + BSC-->>CBC: MESSAGE STATUS QUERY COMPLETE +``` + +The diagram shows a sequence of messages between a CBC (Cell Broadcast Center) and a BSC (Base Station Controller). The CBC sends a 'MESSAGE STATUS QUERY' message to the BSC. The BSC responds with a 'MESSAGE STATUS QUERY COMPLETE' message. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for Message Status Query Procedure: Successful Operation + +**Figure 7.5.2.1: Message Status Query Procedure: Successful Operation** + +The Message Status Query procedure is initiated by the CBC sending the MESSAGE STATUS QUERY message to the BSC (see figure 7.5.2.1) containing the *Old Serial Number* IE, the *Message Identifier* IE and the *Cell List* IE, identifying the cells for which the status query is required, and the *Channel Indicator* IE. + +Upon receipt of the MESSAGE STATUS QUERY message the BSC shall report for each cell as indicated in the *Cell List* IE, the total number of broadcasts of the identified CBS message. The number of broadcasts is reported for each cell in the *Number of Broadcasts Completed* field included in the *Number of Broadcasts Completed List* IE. + +The BSC responds to the CBC by sending the MESSAGE STATUS QUERY COMPLETE message, containing the *Message Identifier* IE, the *Old Serial Number* IE, the *Number of Broadcasts Completed List* IE and the *Channel Indicator* IE. + +If the actual number of broadcasts for a particular cell is greater than the value reported in the *Number of Broadcasts Completed* field, the *Number of Broadcasts Info* field shall be set to value "overflow" to indicate that the counter for the specific cell has overflowed. + +If the number of broadcasts is not known for a particular cell, the *Number of Broadcasts Completed* field shall be set to value "0" and the *Number of Broadcasts Info* field shall be set to "unknown" for this cell. + +If the Message Status Query procedure fails in at least one cell for another reason, the BSC shall respond to the CBC by sending the MESSAGE STATUS QUERY FAILURE message, see subclause 7.5.3. + +### 7.5.3 Unsuccessful Operation + +![Sequence diagram illustrating the Message Status Query Procedure: Un-Successful Operation. The diagram shows two vertical lifelines: BSC (left) and CBC (right). The CBC sends a 'MESSAGE STATUS QUERY' message to the BSC. The BSC responds with a 'MESSAGE STATUS QUERY FAILURE' message to the CBC. Both lifelines end with a horizontal bar at the bottom.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note left of BSC: + Note right of CBC: + CBC->>BSC: MESSAGE STATUS QUERY + BSC-->>CBC: MESSAGE STATUS QUERY FAILURE +``` + +Sequence diagram illustrating the Message Status Query Procedure: Un-Successful Operation. The diagram shows two vertical lifelines: BSC (left) and CBC (right). The CBC sends a 'MESSAGE STATUS QUERY' message to the BSC. The BSC responds with a 'MESSAGE STATUS QUERY FAILURE' message to the CBC. Both lifelines end with a horizontal bar at the bottom. + +**Figure 7.5.3.1: Message Status Query Procedure: Un-Successful Operation** + +If upon receipt of the MESSAGE STATUS QUERY message the BSC can not report the number of CBS message broadcasts in one or several cells as indicated in the *Cell List* IE (e.g. if the CBS message reference is unknown in the BSC) the BSC shall respond by sending the MESSAGE STATUS QUERY FAILURE message to the CBC. Cell(s), for which BSC can not report the number of broadcasts, shall be included in the *Failure List* IE together with a Cause value identifying the reason for the failure. + +If the Message Status Query procedure is successful in at least one cell in the BSC, this cell shall be identified in the *Number of Broadcasts Completed List* IE and be included in the MESSAGE STATUS QUERY FAILURE message. + +The sum of the cell(s) included in the *Number of Broadcasts Completed List* IE and *Failure List* IE shall be equal to the sum of cell(s) as included in the *Cell List* IE in the MESSAGE STATUS QUERY message. + +## 7.6 Set DRX + +### 7.6.1 General + +The purpose of the Set DRX procedure is to configure SMSCB DRX specific parameters in the BSC. This is an optional procedure in the BSC. If not supported, the BSC may use default values of the SMSCB DRX specific parameters. + +### 7.6.2 Successful Operation + +![Sequence diagram showing the Set DRX Procedure: Successful Operation between a BSC and a CBC.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note left of BSC: + Note right of CBC: + CBC->>BSC: SET-DRX + BSC-->>CBC: SET-DRX COMPLETE +``` + +The diagram illustrates a sequence of messages between a Base Station Controller (BSC) and a Cell Broadcast Center (CBC). The BSC is on the left and the CBC is on the right. The sequence starts with the CBC sending a 'SET-DRX' message to the BSC. The BSC then responds with a 'SET-DRX COMPLETE' message to the CBC. Both entities have a vertical lifeline extending downwards from their respective boxes, and the messages are represented by horizontal arrows between these lifelines. + +Sequence diagram showing the Set DRX Procedure: Successful Operation between a BSC and a CBC. + +**Figure 7.6.2.1: Set DRX Procedure: Successful Operation** + +The Set DRX procedure is initiated by the CBC sending the SET-DRX message to the BSC (see figure 7.6.2.1) containing at least one of the two IE's *Schedule Period* IE and *Number of Reserved Slots* IE, the *Cell List* IE identifying the cell(s) for which the new SMSCB DRX specific parameter(s) is valid for, and the *Channel Indicator* IE. + +The *Schedule Period* IE indicates the length of the SMSCB DRX schedule period in number of slots (see 3GPP TS 44.012 [3]). The length of the DRX schedule period shall not be longer than 40 slots since the schedule message can not be built entirely if more than 40 CBS messages have to be described in the schedule period. + +The *Number of Reserved Slots* IE indicates the number of slots in the schedule message reserved for "free slots reading advised" which are normally used for broadcasting of incoming high priority CBS messages (see 3GPP TS 44.012 [3]). The value of *Number of Reserved Slots* IE must be given a lower value than the *Schedule Period* IE. + +The new SMSCB DRX parameters shall be taken into account starting from the next schedule period in each cell. + +After successfully changing the SMSCB DRX parameter(s) for the requested cell(s) the BSC shall respond to the CBC by sending the SET-DRX COMPLETE message with the *Cell List* IE identifying the cell(s) for which the SMSCB DRX parameter(s) is changed, and the *Channel Indicator* IE. + +If the Set DRX procedure fails in at least one cell, the BSC shall respond to the CBC by sending the SET-DRX FAILURE message, see subclause 7.6.3. + +### 7.6.3 Unsuccessful Operation + +![Sequence diagram for Set DRX Procedure: Un-Successful Operation](a3472689858b068ef469213682965325_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note right of CBC: SET-DRX + CBC->>BSC: SET-DRX + Note left of BSC: SET-DRX FAILURE + BSC->>CBC: SET-DRX FAILURE +``` + +The diagram illustrates the interaction between a Base Station Controller (BSC) and a Cell Broadcasting Controller (CBC) for an unsuccessful Set DRX operation. The sequence starts with the CBC sending a 'SET-DRX' message to the BSC. The BSC then responds with a 'SET-DRX FAILURE' message. Both entities are represented by vertical lifelines with rectangular boxes at the top containing their names. The messages are shown as horizontal arrows between the lifelines. + +Sequence diagram for Set DRX Procedure: Un-Successful Operation + +**Figure 7.6.3.1: Set DRX Procedure: Un-Successful Operation** + +If upon receipt of the SET-DRX message the BSC can not configure the SMSCB DRX parameters in the cell(s) as indicated in the *Cell List* IE, the BSC shall respond to the CBC by sending the SET-DRX FAILURE message. Cell(s), for which the SMSCB DRX parameters can not be configured, shall be included in the *Failure List* IE together with a Cause value identifying the reason for the failure. + +If the Set DRX procedure is successful in at least one cell in the BSC, this cell shall be identified in the *Cell List* IE and be included in the SET-DRX FAILURE message. + +The sum of the cell(s) included in the *Cell List* IE and *Failure List* IE shall be equal to the sum of cell(s) as included in the *Cell List* IE in the SET-DRX message. + +## 7.7 Reset + +### 7.7.1 General + +The purpose of the Reset procedure is to terminate broadcasting of all messages (CBS and/or emergency messages) in one or more cells in the BSC. + +### 7.7.2 Successful Operation + +![Sequence diagram for Reset Procedure: Successful Operation](c0e369274e53b2e5364666be6f786c7a_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note right of CBC: RESET + CBC->>BSC: RESET + Note left of BSC: RESET COMPLETE + BSC->>CBC: RESET COMPLETE +``` + +The diagram illustrates the interaction between a Base Station Controller (BSC) and a Cell Broadcasting Controller (CBC) for a successful Reset operation. The sequence starts with the CBC sending a 'RESET' message to the BSC. The BSC then responds with a 'RESET COMPLETE' message. Both entities are represented by vertical lifelines with rectangular boxes at the top containing their names. The messages are shown as horizontal arrows between the lifelines. + +Sequence diagram for Reset Procedure: Successful Operation + +**Figure 7.7.2.1: Reset Procedure: Successful Operation** + +The Reset procedure is initiated by the CBC sending the RESET message to the BSC (see figure 7.7.2.1) containing the *Cell List* IE identifying the cells in which the CBS message and emergency message broadcast shall be terminated. + +Upon receipt of the RESET message the BSC shall terminate the broadcasting of all CBS messages and/or emergency messages in the indicated cell(s). All CBS messages and/or emergency messages, and any reference to them, related to the indicated cell(s), shall be deleted in the BSC. + +The BSC shall respond to the CBC by sending the RESET COMPLETE message with the *Cell List* IE identifying the cell(s) in which the CBS message and/or emergency message broadcast is terminated. + +If the Reset procedure, for any reason, fails in at least one cell, the BSC shall respond to the CBC by sending the RESET FAILURE message, see subclause 7.7.3. + +### 7.7.3 Unsuccessful Operation + +![Sequence diagram illustrating the Unsuccessful Operation of the Reset Procedure. The diagram shows two vertical lifelines: BSC (left) and CBC (right). The sequence of messages is: 1. A horizontal arrow labeled 'RESET' points from the CBC lifeline to the BSC lifeline. 2. A horizontal arrow labeled 'RESET FAILURE' points from the BSC lifeline back to the CBC lifeline. Both lifelines end with a thick horizontal bar at the bottom, indicating the end of the sequence.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +Sequence diagram illustrating the Unsuccessful Operation of the Reset Procedure. The diagram shows two vertical lifelines: BSC (left) and CBC (right). The sequence of messages is: 1. A horizontal arrow labeled 'RESET' points from the CBC lifeline to the BSC lifeline. 2. A horizontal arrow labeled 'RESET FAILURE' points from the BSC lifeline back to the CBC lifeline. Both lifelines end with a thick horizontal bar at the bottom, indicating the end of the sequence. + +**Figure 7.7.3.1: Reset Procedure: Un-Successful Operation** + +If upon receipt of the RESET message the BSC can not terminate the broadcasting of the CBS message and/or the emergency message in the cell(s) as indicated in the *Cell List* IE, the BSC shall respond to the CBC by sending the RESET FAILURE message (see figure 7.7.3.1). Cell(s), in which the Reset procedure is unsuccessful, shall be indicated in the *Failure List* IE together with a Cause value identifying the reason for the failure. + +If the Reset procedure is successful in at least one cell in the BSC, this cell shall be identified in the *Cell List* IE and provided in the RESET FAILURE message. + +The sum of the cell(s) included in the *Cell List* IE and *Failure List* IE shall be equal to the sum of cell(s) as included in the *Cell List* IE in the RESET message. + +## 7.7a Keep Alive + +#### 7.7a.1 General + +The purpose of the Keep Alive procedure is to verify the CBSP communication path between the CBC and the BSC and to supervise the availability of the CBSP communication. + +### 7.7a.2 Successful Operation + +![Sequence diagram for Successful Operation of the Keep Alive procedure.](844077b3034f0030b404207db0ad76b4_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note right of CBC: T1 started + CBC->>BSC: KEEP-ALIVE + BSC->>CBC: KEEP-ALIVE COMPLETE + Note right of CBC: T1 stopped +``` + +The diagram illustrates the successful operation of the Keep Alive procedure. It features two lifelines: BSC (Base Station Controller) on the left and CBC (Controller Base Station) on the right. The sequence begins with the CBC sending a 'KEEP-ALIVE' message to the BSC. Upon sending this message, a timer 'T1' is started in the CBC, as indicated by a box labeled 'T1 started'. The BSC receives the message and responds with a 'KEEP-ALIVE COMPLETE' message. Upon receiving this response, the timer 'T1' is stopped in the CBC, as indicated by a box labeled 'T1 stopped'. + +Sequence diagram for Successful Operation of the Keep Alive procedure. + +**Figure 7.7a.2.1: Keep Alive Procedure: Successful Operation** + +The Keep Alive procedure is initiated by the CBC sending the KEEP-ALIVE message to the BSC (see figure 7.7a.2.1) containing the *Keep Alive Repetition Period* IE indicating the repetition period in which the KEEP-ALIVE message is sent. Upon sending of the KEEP-ALIVE message, the timer T1 is started in the CBC, supervising the response message from the BSC. + +At reception of the KEEP-ALIVE message in the BSC, the BSC shall return the KEEP-ALIVE COMPLETE message to the CBC. The BSC may use the value from the *Keep Alive Repetition Period* IE to supervise the KEEP-ALIVE message sent from the CBC. How to supervise the reception of the KEEP-ALIVE message is a BSC implementation matter. + +At reception of the KEEP-ALIVE COMPLETE message in the CBC, the timer T1 is stopped. + +The KEEP-ALIVE message is sent periodically from the CBC according to the value as indicated in the *Keep Alive Repetition Period* IE. + +#### 7.7a.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of the Keep Alive procedure.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note right of CBC: T1 started + CBC->>BSC: KEEP-ALIVE + Note right of CBC: T1 expires +``` + +The diagram illustrates the unsuccessful operation of the Keep Alive procedure. It features two lifelines: BSC (Base Station Controller) on the left and CBC (Controller Base Station) on the right. The sequence begins with the CBC sending a 'KEEP-ALIVE' message to the BSC. Upon sending this message, a timer 'T1' is started in the CBC, as indicated by a box labeled 'T1 started'. The BSC receives the message but does not respond. Eventually, the timer 'T1' expires in the CBC, as indicated by a box labeled 'T1 expires', signifying the failure of the procedure. + +Sequence diagram for Unsuccessful Operation of the Keep Alive procedure. + +**Figure 7.7a.3.1: Keep Alive Procedure: Unsuccessful Operation** + +If the KEEP-ALIVE COMPLETE message is not received in the CBC before the timer T1 expires, the Keep Alive procedure is considered as failed. + +Appropriate actions to follow in the CBC (e.g. repetition of Keep Alive procedure) are considered as an implementation matter. + +## 7.8 Restart Indication + +### 7.8.1 General + +The purpose of the Restart Indication procedure is to inform the CBC that a cell broadcast related restart has occurred in one or more cells in the BSC. The procedure may also be used to inform the CBC of the current CBS message or emergency message operational state in one or more cells in the BSC independently if a cell broadcast related restart has occurred or not. + +### 7.8.2 Successful Operation + +![Sequence diagram showing the successful operation of the Restart Indication Procedure. A BSC sends a RESTART message to a CBC.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note right of BSC: RESTART + BSC->>CBC: RESTART + Note right of CBC: +``` + +The diagram illustrates the successful operation of the Restart Indication Procedure. It features two vertical lifelines: BSC on the left and CBC on the right. A horizontal arrow labeled 'RESTART' points from the BSC lifeline to the CBC lifeline. Both lifelines terminate in a thick horizontal bar at the bottom. + +Sequence diagram showing the successful operation of the Restart Indication Procedure. A BSC sends a RESTART message to a CBC. + +**Figure 7.8.2.1: Restart Indication Procedure: Successful Operation** + +The Restart Indication procedure is initiated by the BSC in purpose to inform the CBC of the CBS message operational state or the emergency message operational state in one or more cells in the BSC. + +The BSC informs the CBC by sending the RESTART message (see figure 7.8.2.1) containing the *Cell List* IE identifying the cell(s) being in CBS message operational state or in emergency message operational state and the *Recovery Indication* IE, indicating whether the broadcast information data is lost or not in the BSC. + +The RESTART message is sent once per broadcast message type as indicated by the *Broadcast Message Type* IE. + +## 7.9 Failure Indication + +### 7.9.1 General + +The purpose of the Failure Indication procedure is to inform the CBC that a cell broadcast related problem is present in one or more cells in the BSC. + +### 7.9.2 Successful Operation + +![Sequence diagram showing the successful operation of the Failure Indication Procedure. A BSC sends a FAILURE message to a CBC.](ea49c15f36ffb089d44f1d793f013778_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note right of BSC: FAILURE + BSC->>CBC: FAILURE + Note right of CBC: +``` + +The diagram illustrates the successful operation of the Failure Indication Procedure. It features two vertical lifelines: BSC on the left and CBC on the right. A horizontal arrow labeled 'FAILURE' points from the BSC lifeline to the CBC lifeline. Both lifelines terminate in a thick horizontal bar at the bottom. + +Sequence diagram showing the successful operation of the Failure Indication Procedure. A BSC sends a FAILURE message to a CBC. + +**Figure 7.9.2.1: Failure Indication Procedure: Successful Operation** + +The Failure Indication procedure is initiated by the BSC when a cell broadcast related problem occurs in a cell, i.e. when CBS message broadcast or emergency message broadcast is prevented in a cell for whatever reason. + +The BSC informs the CBC by sending the FAILURE message (see figure 7.9.2.1) containing the *Failure List* IE identifying the cell(s) having a broadcast related problem. For each cell a Cause value is included, indicating the reason to the failure. + +The FAILURE message is sent once per broadcast message type as indicated by the *Broadcast Message Type* IE. + +Upon receipt of the FAILURE message, the CBC shall not initiate further WRITE-REPLACE messages for concerned cell(s) until the CBC is informed, by the RESTART message, that the cell(s) have resumed CBS message operational state or emergency message operational state again. + +## 7.10 Error Indication + +### 7.10.1 General + +The purpose of the Error Indication procedure is to inform the CBC that an erroneous CBSP message was received in the BSC provided the detected error can not be reported by an appropriate failure message. + +### 7.10.2 Successful Operation + +![Sequence diagram showing the Error Indication Procedure: Successful Operation. A BSC (Base Station Controller) sends an ERROR INDICATION message to a CBC (Cell Broadcast Controller).](303fadfb9def251d1575d6221199b158_img.jpg) + +``` +sequenceDiagram + participant BSC + participant CBC + Note left of BSC: BSC + Note right of CBC: CBC + BSC->>CBC: ERROR INDICATION +``` + +Sequence diagram showing the Error Indication Procedure: Successful Operation. A BSC (Base Station Controller) sends an ERROR INDICATION message to a CBC (Cell Broadcast Controller). + +Figure 7.10.2.1: Error Indication Procedure: Successful Operation + +The Error Indication procedure is initiated by the BSC when a CBSP message is received from the CBC and the content of the CBSP message can not be interpreted by the BSC. + +The BSC informs the CBC by sending the ERROR INDICATION message (see figure 7.10.2.1), containing at least the *Cause* IE, identifying the reason for the interpretation problem in the BSC. + +Examples of possible cause values for protocol error indications are: + +- "Parameter-value-invalid" +- "Unrecognised-message" + +The ERROR INDICATION message shall only be sent in case the detected error can not be reported by an appropriate failure message. + +# --- 8 Elements for CBSP Communication + +## 8.1 Message Functional Definitions and Contents + +### 8.1.1 General + +Subclause 8.1 defines the coding and format of the CBSP messages in tabular format. + +A CBSP message consists of *Message Type* IE, *Length Indicator* IE and possibly a set of information elements. + +For each CBSP message there is, in subclause 8.1.3, a table listing the information elements in their order of appearance in the transmitted CBSP message. + +There is no general rule for the order of information elements. The same information elements may appear in various orders depending on the CBSP message. + +A CBS message is uniquely identified by the four elements *Message Identifier IE*, *Serial Number IE*, *Channel Indicator IE* and the "Cell Identifier" field included in the *Cell List IE*. This means that even when two CBS messages have the same semantic content (for example the same weather forecast) but in different languages or coding schemes, they are considered as different and must therefore be identified by a different quartet. + +An emergency message is uniquely identified by the three elements *Message Identifier IE*, *Serial Number IE* and the "Cell Identifier" field included in the *Cell List IE*. + +Table 8.1.1.1 summarizes the CBSP messages. + +**Table 8.1.1.1: CBSP messages** + +| Message name | Reference | +|-------------------------------|-----------| +| WRITE-REPLACE | 8.1.3.1 | +| WRITE-REPLACE COMPLETE | 8.1.3.2 | +| WRITE-REPLACE FAILURE | 8.1.3.3 | +| KILL | 8.1.3.4 | +| KILL COMPLETE | 8.1.3.5 | +| KILL FAILURE | 8.1.3.6 | +| LOAD QUERY | 8.1.3.7 | +| LOAD QUERY COMPLETE | 8.1.3.8 | +| LOAD QUERY FAILURE | 8.1.3.9 | +| MESSAGE STATUS QUERY | 8.1.3.10 | +| MESSAGE STATUS QUERY COMPLETE | 8.1.3.11 | +| MESSAGE STATUS QUERY FAILURE | 8.1.3.12 | +| SET-DRX | 8.1.3.13 | +| SET DRX COMPLETE | 8.1.3.14 | +| SET-DRX FAILURE | 8.1.3.15 | +| RESET | 8.1.3.16 | +| RESET COMPLETE | 8.1.3.17 | +| RESET FAILURE | 8.1.3.18 | +| KEEP-ALIVE | 8.1.3.18a | +| KEEP-ALIVE COMPLETE | 8.1.3.18b | +| RESTART | 8.1.3.19 | +| FAILURE | 8.1.3.20 | +| ERROR INDICATION | 8.1.3.21 | + +### 8.1.2 Presence + +All Information Elements in the message descriptions below are marked mandatory, optional or conditional according to table 8.1.2.1. + +**Table 8.1.2.1: Meaning of abbreviations used in CBSP 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 fulfilled. Otherwise the IE is not included. | + +### 8.1.3 Message Contents + +#### 8.1.3.1 WRITE-REPLACE + +The WRITE-REPLACE message is sent from the CBC to the BSC in order to broadcast a new CBS message or to replace an ongoing CBS message broadcast. This message may also be sent in order to broadcast a new emergency message or to replace an ongoing emergency message broadcast. + +Direction: CBC → BSC + +**Table 8.1.3.1.1: WRITE-REPLACE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|--------------------------------|-----------|---------------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| New Serial Number | 8.2.5 | M | 3 | +| Old Serial Number | 8.2.4 | O | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | O (note 1) | 2 | +| Category | 8.2.7 | C (note 2) | 2 | +| Repetition Period | 8.2.8 | C (note 2) | 3 | +| Number of Broadcasts Requested | 8.2.9 | C (note 2) | 3 | +| Number of Pages | 8.2.21 | C (note 2) | 2 | +| Data Coding Scheme | 8.2.14 | C (note 2) | 2 | +| Message Content (Page 1) | 8.2.3 | C (note 2) | 84 | +| Message Content (Page 2) | 8.2.3 | O | 84 | +| Message Content (Page 3) | 8.2.3 | O | 84 | +| Message Content (Page 4) | 8.2.3 | O | 84 | +| Message Content (Page 5) | 8.2.3 | O | 84 | +| Message Content (Page 6) | 8.2.3 | O | 84 | +| Message Content (Page 7) | 8.2.3 | O | 84 | +| Message Content (Page 8) | 8.2.3 | O | 84 | +| Message Content (Page 9) | 8.2.3 | O | 84 | +| Message Content (Page 10) | 8.2.3 | O | 84 | +| Message Content (Page 11) | 8.2.3 | O | 84 | +| Message Content (Page 12) | 8.2.3 | O | 84 | +| Message Content (Page 13) | 8.2.3 | O | 84 | +| Message Content (Page 14) | 8.2.3 | O | 84 | +| Message Content (Page 15) | 8.2.3 | O | 84 | +| Emergency Indicator | 8.2.17 | O (note 1) | 2 | +| Warning Type | 8.2.18 | C (note 3) | 3 | +| Warning Security Information | 8.2.19 | C (note 3, 4) | 51 | +| Warning Period | 8.2.25 | C (note 3) | 2 | + +NOTE 1: Only one of these two optional IEs shall be present in the message. *Channel Indicator* IE is included if and only if the message contains a CBS message. *Emergency Indicator* IE is included if and only if the message contains an emergency message. + +NOTE 2: This IE is included if and only if the *Channel Indicator* IE is present in the message. + +NOTE 3: This IE is included if and only if the *Emergency Indicator* IE is present in the message and the *Emergency Indicator* IE indicates ETWS information. + +NOTE 4: This IE does not serve any purpose. It is only included due to requirements in earlier versions of 3GPP TS 23.041 [1]. + +If only the *New Serial Number* IE, and not the *Old Serial Number* IE, is included in the WRITE-REPLACE message, the BSC shall interpret the message as a write request operation. + +If both *New Serial Number* IE and *Old Serial Number* IE are included in the WRITE-REPLACE message, the BSC shall interpret the message as a replace request operation. + +#### 8.1.3.2 WRITE-REPLACE COMPLETE + +The WRITE-REPLACE COMPLETE message is sent from the BSC to the CBC to indicate a successful Write-Replace procedure. + +Direction: BSC → CBC + +**Table 8.1.3.2.1: WRITE-REPLACE COMPLETE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------------------------------------------------------------------------------------------------------------------------|-----------|------------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| New Serial Number | 8.2.5 | M | 3 | +| Old Serial Number | 8.2.4 | O (note 1) | 3 | +| Number of Broadcasts Completed List | 8.2.10 | O (note 2) | 4+m+3
to
4+(m+3)n | +| Cell List | 8.2.6 | O | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | O (note 1) | 2 | +| NOTE 1: This IE is only included in the message if it was received in the WRITE-REPLACE message. | | | | +| NOTE 2: This IE is only included in the message if the message is sent as a response to a replace request operation of a CBS message. | | | | + +If the WRITE-REPLACE COMPLETE message is returned to the CBC as a response to a write request operation of a CBS message or an emergency message, the Cell Identifier for each cell is included in the *Cell List* IE. + +If the WRITE-REPLACE COMPLETE message is returned to the CBC as a response to a replace request operation of a CBS message, the *Number of Broadcasts Completed List* IE may contain for each cell the number of broadcasts of the replaced CBS message. In this case the *Old Serial Number* IE refers to the message for which the number of broadcasts completed information is supplied. + +If the WRITE-REPLACE COMPLETE message is returned to the CBC as a response to a replace request operation of an emergency message, the Cell Identifier for each cell is included in the *Cell List* IE. In this case the *Old Serial Number* IE is referring to the cell(s) included in the *Cell List* IE. + +#### 8.1.3.3 WRITE-REPLACE FAILURE + +The WRITE-REPLACE FAILURE message is sent from the BSC to the CBC to indicate that the Write-Replace procedure failed in at least one cell. + +Direction: BSC → CBC + +**Table 8.1.3.3.1: WRITE-REPLACE FAILURE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| New Serial Number | 8.2.5 | M | 3 | +| Old Serial Number | 8.2.4 | O (note 2) | 3 | +| Failure List | 8.2.11 | M | 4+m+1
to
p+m+1 | +| Number of Broadcasts Completed List | 8.2.10 | O (note 1) | 4+m+3
to
4+(m+3)n | +| Cell List | 8.2.6 | O | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | O (note 2) | 2 | +| NOTE 1: This IE is only included in the message if the requested kill operation in the WRITE-REPLACE message is successful in at least one cell. | | | | +| NOTE 2: This IE is only included in the message if it was received in the WRITE-REPLACE message. | | | | + +If the WRITE-REPLACE FAILURE message is returned to the CBC as a response to a write request operation: + +- The *Failure List* IE contains a list of cells for which the requested write operation failed. For each cell a Cause value is included, indicating the reason to the failure. +- The *Cell List* IE, if present, contains the cells for which the requested write operation succeeded. + +If the WRITE-REPLACE FAILURE message is returned to the CBC as a response to a replace request operation: + +- The *Failure List* IE contains a list of cells for which the requested kill operation failed and/or cells for which the requested kill operation succeeded but for which the subsequent write operation failed. For each cell a Cause value is included, indicating the reason to the failure. +- The *Number of Broadcasts Completed List* IE, if present, contains the cells for which the kill operation of the replaced CBS message succeeded. In this case the *Old Serial Number* IE refers to the message for which the number of broadcasts completed information is supplied. +- The *Cell List* IE, if present, contains the cells for which the kill operation of the replaced emergency message succeeded. In this case the *Old Serial Number* IE refers to the cell(s) included in the *Cell List* IE. + +#### 8.1.3.4 KILL + +The KILL message is sent from the CBC to the BSC in order to stop broadcasting of a specific CBS message or emergency message. Any reference to the CBS message or emergency message shall be removed in the BSC. + +Direction: CBC → BSC + +**Table 8.1.3.4.1: KILL message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|--------------------------------------------------------------------------|-----------|------------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| Old Serial Number | 8.2.4 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | O (note 1) | 2 | +| NOTE 1: This IE is only included if the message refers to a CBS message. | | | | + +#### 8.1.3.5 KILL COMPLETE + +The KILL COMPLETE message is sent from the BSC to the CBC indicating a successful Kill procedure. + +Direction: BSC → CBC + +**Table 8.1.3.5.1: KILL COMPLETE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|-----------------------------------------------------------------------------------------|-----------|------------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| Old Serial Number | 8.2.4 | M | 3 | +| Number of Broadcasts Completed List | 8.2.10 | O | 4+m+3
to
4+(m+3)n | +| Cell List | 8.2.6 | O | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | O (note 1) | 2 | +| NOTE 1: This IE is only included in the message if it was received in the KILL message. | | | | + +The *Number of Broadcasts Completed List* IE, if present, contains for each cell the total number of broadcasts of the killed CBS message. + +The *Cell List* IE, if present, contains the cells in which the emergency message is successfully terminated. + +#### 8.1.3.6 KILL FAILURE + +The KILL FAILURE message is sent from the BSC to the CBC to indicate that the Kill procedure failed in at least one cell. + +Direction: BSC → CBC + +**Table 8.1.3.6.1: KILL FAILURE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------------------------------------------------------------------------------------------------------|-----------|------------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| Old Serial Number | 8.2.4 | M | 3 | +| Failure List | 8.2.11 | M | 4+m+1
to
p+m+1 | +| Number of Broadcasts Completed List | 8.2.10 | O (note 1) | 4+m+3
to
4+(m+3)n | +| Cell List | 8.2.6 | O (note 1) | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | O (note 2) | 2 | +| NOTE 1: This IE is only included in the message if the requested kill operation is successful in at least one cell. | | | | +| NOTE 2: This IE is only included in the message if it was received in the KILL message. | | | | + +The *Failure List* IE contains a list of cells for which the requested kill operation failed. For each cell a Cause value is included, indicating the reason to the failure. + +The *Number of Broadcasts Completed List* IE, if present, contains a list of cells for which the kill operation of the CBS message succeeded. + +The *Cell List* IE, if present, contains the cells in which the emergency message is successfully terminated. + +#### 8.1.3.7 LOAD QUERY + +The LOAD QUERY message is sent from the CBC to the BSC in order to obtain current load status of the CBCH radio resources of indicated cell(s). + +Direction: CBC → BSC + +**Table 8.1.3.7.1: LOAD QUERY message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------|-----------|------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | M | 2 | + +#### 8.1.3.8 LOAD QUERY COMPLETE + +The LOAD QUERY COMPLETE message is sent from the BSC to the CBC to indicate a successful Load Query procedure. + +Direction: BSC → CBC + +**Table 8.1.3.8.1: LOAD QUERY COMPLETE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|-----------------------------|-----------|------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Radio Resource Loading List | 8.2.12 | M | 4+m+2
to
4+(m+2)n | +| Channel Indicator | 8.2.20 | M | 2 | + +#### 8.1.3.9 LOAD QUERY FAILURE + +The LOAD QUERY FAILURE message is sent from the BSC to the CBC indicating that the Load Query procedure failed in at least one cell. + +Direction: BSC → CBC + +**Table 8.1.3.9.1: LOAD QUERY FAILURE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|-----------------------------------------------------------------------------------------------------------------|-----------|------------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Failure List | 8.2.11 | M | 4+m+1
to
p+m+1 | +| Channel Indicator | 8.2.20 | M | 2 | +| Radio Resource Loading List | 8.2.12 | O (note 1) | 4+m+2
to
4+(m+2)n | +| NOTE 1: This IE is only included in the message if the Load Query procedure is successful in at least one cell. | | | | + +The *Failure List* IE contains a list of cells for which the current load status of the CBCH radio resources can not be obtained. For each cell a Cause value is included, indicating the reason to the failure. + +#### 8.1.3.10 MESSAGE STATUS QUERY + +The MESSAGE STATUS QUERY message is sent from the CBC to the BSC in order to obtain current status of a specific CBS message. + +Direction: CBC → BSC + +**Table 8.1.3.10.1: MESSAGE STATUS QUERY message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------|-----------|------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| Old Serial Number | 8.2.4 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | M | 2 | + +#### 8.1.3.11 MESSAGE STATUS QUERY COMPLETE + +The MESSAGE STATUS QUERY COMPLETE message is sent from the BSC to the CBC to indicate a successful Message Status Query procedure. + +Direction: BSC → CBC + +**Table 8.1.3.11.1: MESSAGE STATUS QUERY COMPLETE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|----------------------------------------|-----------|------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| Old Serial Number | 8.2.4 | M | 3 | +| Number of Broadcasts
Completed List | 8.2.10 | M | 4+m+3
to
4+(m+3)n | +| Channel Indicator | 8.2.20 | M | 2 | + +#### 8.1.3.12 MESSAGE STATUS QUERY FAILURE + +The MESSAGE STATUS QUERY FAILURE message is sent from the BSC to the CBC indicating that the Message Status Query procedure failed in at least one cell. + +Direction: BSC → CBC + +**Table 8.1.3.12.1: MESSAGE STATUS QUERY FAILURE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------------------------------------------------------------------------------------------------------------|-----------|------------|-------------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Message Identifier | 8.2.16 | M | 3 | +| Old Serial Number | 8.2.4 | M | 3 | +| Failure List | 8.2.11 | M | 4+m+1
to
p+m+1 | +| Channel Indicator | 8.2.20 | M | 2 | +| Number of Broadcasts
Completed List | 8.2.10 | O (note 1) | 4+m+3
to
4+(m+3)n | +| NOTE 1: This IE is only included in the message if the Message Status Query procedure is successful in at least one cell. | | | | + +The *Failure List* IE contains a list of cells for which the broadcast status can not be obtained. For each cell a Cause value is included, indicating the reason to the failure. + +#### 8.1.3.13 SET-DRX + +The SET-DRX message is sent from the CBC to set SMSCB DRX specific parameters in the BSC. + +Direction: CBC → BSC + +**Table 8.1.3.13.1: SET-DRX message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|----------------------------------------------------------------------------------------------------------------------------|-----------|------------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | M | 2 | +| Schedule Period | 8.2.22 | O (note 1) | 2 | +| Number of Reserved Slots | 8.2.23 | O (note 1) | 2 | +| NOTE 1: At least one of the two IEs Schedule Period IE or Reserved Slots IE must be included in the message. | | | | + +#### 8.1.3.14 SET-DRX COMPLETE + +The SET-DRX COMPLETE message is sent from the BSC to the CBC indicating a successful Set DRX procedure. + +Direction: BSC → CBC + +**Table 8.1.3.14.1: SET-DRX COMPLETE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------|-----------|------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | +| Channel Indicator | 8.2.20 | M | 2 | + +The *Cell List* IE contains a list of cells for which the SMSCB DRX parameters are successfully changed. + +#### 8.1.3.15 SET-DRX FAILURE + +The SET-DRX FAILURE message is sent from the BSC to the CBC indicating that the Set DRX procedure failed in at least one cell. + +Direction: BSC → CBC + +**Table 8.1.3.15.1: SET-DRX FAILURE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|--------------------------------------------------------------------------------------------------------------|-----------|------------|----------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Failure List | 8.2.11 | M | 4+m+1
to
p+m+1 | +| Channel Indicator | 8.2.20 | M | 2 | +| Cell List | 8.2.6 | O (note 1) | 4+m
to
4+mn | +| NOTE 1: This IE is only included in the message if the Set DRX procedure is successful in at least one cell. | | | | + +The *Failure List* IE contains a list of cells for which the SMSCB DRX parameters can not be changed. For each cell a Cause value is included, indicating the reason to the failure. + +#### 8.1.3.16 RESET + +The RESET message is sent from the CBC to the BSC in order to stop broadcasting of all messages (CBS and/or emergency messages) in one or more cells. All CBS messages and/or emergency messages related to the indicated cell(s) shall be deleted. + +Direction: CBC → BSC + +**Table 8.1.3.16.1: RESET message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------|-----------|------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | + +#### 8.1.3.17 RESET COMPLETE + +The RESET COMPLETE message is sent from the BSC to the CBC to indicate a successful Reset procedure. + +Direction: BSC → CBC + +**Table 8.1.3.17.1: RESET COMPLETE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------|-----------|------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | + +The *Cell List* IE contains a list of cells for which the Reset procedure is successfully performed. + +#### 8.1.3.18 RESET FAILURE + +The RESET FAILURE message is sent from the BSC to the CBC indicating that the Reset procedure failed in at least one cell. + +Direction: BSC → CBC + +**Table 8.1.3.18.1: RESET FAILURE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------------------------------------------------------------------------------------------|-----------|------------|----------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Failure List | 8.2.11 | M | 4+m+1
to
p+m+1 | +| Cell List | 8.2.6 | O (note 1) | 4+m
to
4+mn | +| NOTE 1: This IE is only included in the message if the Reset procedure succeeded for at least one cell. | | | | + +The *Failure List* IE contains a list of cells for which the Reset procedure failed. For each cell a Cause value is included, indicating the reason to the failure. + +The *Cell List* IE, if present, contains a list of cells for which the Reset procedure is successfully performed. + +#### 8.1.3.18a KEEP-ALIVE + +The KEEP-ALIVE message is sent from the CBC to the BSC in order to verify the CBSP communication path between the CBC and the BSC. + +Direction: CBC → BSC + +**Table 8.1.3.18a.1: KEEP-ALIVE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|------------------------------|-----------|------|--------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Keep Alive Repetition Period | 8.2.27 | M | 2 | + +#### 8.1.3.18b KEEP-ALIVE COMPLETE + +The KEEP-ALIVE COMPLETE message is sent from the BSC to the CBC in response to the KEEP-ALIVE message. + +Direction: BSC → CBC + +**Table 8.1.3.18b.1: KEEP-ALIVE COMPLETE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------|-----------|------|--------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | + +#### 8.1.3.19 RESTART + +The RESTART message is sent to inform the CBC of the CBS message operational state or the emergency message operational state for cells included in the *Cell List* IE. + +Direction: BSC → CBC + +**Table 8.1.3.19.1: RESTART message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|------------------------|-----------|------|-------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Cell List | 8.2.6 | M | 4+m
to
4+mn | +| Broadcast Message Type | 8.2.24 | M | 2 | +| Recovery Indication | 8.2.15 | M | 2 | + +The *Recovery Indication* IE indicates whether CBS message or emergency message related data is lost for the indicated cell(s). Note that the *Recovery Indication* IE does not indicate if the parameters set by the Set DRX procedure are available or not. + +The *Broadcast Message Type* IE indicates the type of broadcast message the RESTART message is referring to. + +#### 8.1.3.20 FAILURE + +The FAILURE message is sent from the BSC to indicate a cell broadcast related problem in one or more of its cells. Cells included in the *Failure List* IE are not in CBS message operational state or in emergency message operational state. + +Direction: BSC → CBC + +**Table 8.1.3.20.1: FAILURE message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|------------------------|-----------|------|----------------------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Failure List | 8.2.11 | M | 4+m+1
to
p+m+1 | +| Broadcast Message Type | 8.2.24 | M | 2 | + +The *Broadcast Message Type* IE indicates the type of broadcast message the FAILURE message is referring to. + +#### 8.1.3.21 ERROR INDICATION + +The ERROR INDICATION message is sent from the BSC to the CBC in response to any CBC request which can not be interpreted in the BSC. + +Direction: BSC → CBC + +**Table 8.1.3.21.1: ERROR INDICATION message content** + +| INFORMATION ELEMENT | REFERENCE | TYPE | LENGTH | +|---------------------------------------------------------------------------------------------------------|-----------|------------|--------| +| Message Type | 8.2.2 | M | 1 | +| Length Indicator | 8.2.26 | M | 3 | +| Cause | 8.2.13 | M | 2 | +| Message Identifier | 8.2.16 | O | 3 | +| New Serial Number | 8.2.5 | O | 3 | +| Old Serial Number | 8.2.4 | O | 3 | +| Channel Indicator | 8.2.20 | O (note 1) | 2 | +| NOTE 1: This IE is only included in the message if it was received in the request message from the CBC. | | | | + +## 8.2 Information Element Definitions + +### 8.2.1 General + +Subclause 8.2 presents the CBSP IE definitions in tabular format. + +The following conventions are assumed for the sequence of transmission of bits and bytes: + +- Each bit position is marked as 1 to 8. Bit 1 is the least significant bit and is transmitted first; +- In an element octets are identified by numbers, octet 1 is transmitted first, then octet 2, etc. + +When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. + +For variable length elements a length indicator in binary format is included, indicating the number of octets following in the element. + +All fields within Information Elements are mandatory unless otherwise specified. The Information Element Identifier shall always be included. + +All spare bits are set to "0". + +**Table 8.2.1.1: Information elements used and their coding** + +| Element Identifier Coding | Element name | Reference | +|----------------------------------|-------------------------------------|------------------| +| 0000 0001 | Message Content | 8.2.3 | +| 0000 0010 | Old Serial Number | 8.2.4 | +| 0000 0011 | New Serial Number | 8.2.5 | +| 0000 0100 | Cell List | 8.2.6 | +| 0000 0101 | Category | 8.2.7 | +| 0000 0110 | Repetition Period | 8.2.8 | +| 0000 0111 | Number of Broadcasts Requested | 8.2.9 | +| 0000 1000 | Number of Broadcasts Completed List | 8.2.10 | +| 0000 1001 | Failure List | 8.2.11 | +| 0000 1010 | Radio Resource Loading List | 8.2.12 | +| 0000 1011 | Cause | 8.2.13 | +| 0000 1100 | Data Coding Scheme | 8.2.14 | +| 0000 1101 | Recovery Indication | 8.2.15 | +| 0000 1110 | Message Identifier | 8.2.16 | +| 0000 1111 | Emergency Indicator | 8.2.17 | +| 0001 0000 | Warning Type | 8.2.18 | +| 0001 0001 | Warning Security Information | 8.2.19 | +| 0001 0010 | Channel Indicator | 8.2.20 | +| 0001 0011 | Number of Pages | 8.2.21 | +| 0001 0100 | Schedule Period | 8.2.22 | +| 0001 0101 | Number of Reserved Slots | 8.2.23 | +| 0001 0110 | Broadcast Message Type | 8.2.24 | +| 0001 0111 | Warning Period | 8.2.25 | +| 0001 1000 | Keep Alive Repetition Period | 8.2.27 | + +### 8.2.2 Message Type + +*Message Type* IE uniquely identifies the message being sent. It is a single octet element, mandatory in all messages. + +All unassigned codes are reserved for future use. + +**Table 8.2.2.1: Message types for CBSP messages** + +| 8 7 6 5 4 3 2 1 | Message name | +|-----------------|-------------------------------| +| 0 0 0 0 0 0 0 0 | Reserved | +| 0 0 0 0 0 0 0 1 | WRITE-REPLACE | +| 0 0 0 0 0 0 1 0 | WRITE-REPLACE COMPLETE | +| 0 0 0 0 0 0 1 1 | WRITE-REPLACE FAILURE | +| 0 0 0 0 0 1 0 0 | KILL | +| 0 0 0 0 0 1 0 1 | KILL COMPLETE | +| 0 0 0 0 0 1 1 0 | KILL FAILURE | +| 0 0 0 0 0 1 1 1 | LOAD QUERY | +| 0 0 0 0 1 0 0 0 | LOAD QUERY COMPLETE | +| 0 0 0 0 1 0 0 1 | LOAD QUERY FAILURE | +| 0 0 0 0 1 0 1 0 | MESSAGE STATUS QUERY | +| 0 0 0 0 1 0 1 1 | MESSAGE STATUS QUERY COMPLETE | +| 0 0 0 0 1 1 0 0 | MESSAGE STATUS QUERY FAILURE | +| 0 0 0 0 1 1 0 1 | SET-DRX | +| 0 0 0 0 1 1 1 0 | SET DRX COMPLETE | +| 0 0 0 0 1 1 1 1 | SET-DRX FAILURE | +| 0 0 0 1 0 0 0 0 | RESET | +| 0 0 0 1 0 0 0 1 | RESET COMPLETE | +| 0 0 0 1 0 0 1 0 | RESET FAILURE | +| 0 0 0 1 0 0 1 1 | RESTART | +| 0 0 0 1 0 1 0 0 | FAILURE | +| 0 0 0 1 0 1 0 1 | ERROR INDICATION | +| 0 0 0 1 0 1 1 0 | KEEP-ALIVE | +| 0 0 0 1 0 1 1 1 | KEEP-ALIVE COMPLETE | + +### 8.2.3 Message Content + +*Message Content* IE contains the user information of the CBS message. The user information of the *Message Content* IE will be broadcasted over the radio interface (see 3GPP TS 44.012 [3]) together with the Serial Number, Message Identifier and Data Coding Scheme. + +The *Message Content* IE is a fixed length element coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------|---|---|---|---|---|---|---|---------------| +| Element identifier | | | | | | | | octet 1 | +| User Information Length | | | | | | | | octet 2 | +| Message Content | | | | | | | | octet 3 to 84 | + +**Figure 8.2.3.1: Message Content information element** + +The "User Information Length" field is coded as the binary value of number of octets of the "Message Content" field containing user information. When the user information is less than 82 octets, the remaining octets of the "Message Content" field must be filled with padding bits (see 3GPP TS 23.038 [4]). + +In the case where the user information is encoded using the GSM 7 bit default alphabet and the last character terminates at an octet boundary, the "User Information Length" field indicates the number of octets of user information. In the case where the last character does not terminate at an octet boundary, this field indicates the number of octets up to the octet boundary immediately following the last GSM 7 bit default alphabet character of user information. + +The "User Information Length" field is coded as follows: + +| | | +|-----------|-------------------------------| +| 0000 0000 | reserved | +| 0000 0001 | one octet of user information | +| ... | | +| 0101 0010 | 82 octets of user information | + +All other values are reserved. + +In the case where the user information is GSM 7 bit default alphabet encoded, the appropriate padding characters and bit-fill are added to the end of the user information to complete the Message Content (see 3GPP TS 23.038 [4]). + +In the case where the user information is 8 bit encoded, the appropriate padding octets are added to the end of the user information to complete the Message Content (see 3GPP TS 23.038 [4]). + +### 8.2.4 Old Serial Number + +*Old Serial Number* IE is a fixed length element which together with the *Message Identifier* IE, *Cell Identifier* IE and the *Channel Indicator* IE enables identification of an existing CBS message. *Old Serial Number* IE together with the *Message Identifier* IE and the *Cell Identifier* IE enables identification of an existing emergency message. + +The coding is as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Serial Number | | | | | | | | octet 2 | +| Serial Number cont. | | | | | | | | octet 3 | + +**Figure 8.2.4.1: Old serial Number information element** + +Octets 2-3 are coded as the 'Serial-Number' defined in 3GPP TS 23.041 [1]. + +### 8.2.5 New Serial Number + +*New Serial Number* IE is a fixed length element which together with the *Message Identifier* IE, *Cell Identifier* IE and *Channel Indicator* IE enables identification of a new CBS message. *New Serial Number* IE together with the *Message Identifier* IE and the *Cell Identifier* IE enables identification of a new emergency message. + +The *New Serial Number* IE is altered every time the CBS message, or the emergency message, with a given Message Identifier is changed. + +The coding is as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Serial Number | | | | | | | | octet 2 | +| Serial Number cont. | | | | | | | | octet 3 | + +**Figure 8.2.5.1: New Serial Number information element** + +Octets 2-3 are coded as the 'Serial-Number' defined in 3GPP TS 23.041 [1]. + +### 8.2.6 Cell List + +The *Cell List* IE identifies a sequence of one or more cells to which the CBS message or emergency message apply. The *Cell List* IE must include at least one cell. + +This element is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----------------------|---|---|---|-----------------------------------|---|---|---|-------------------|--|--|--|--| +| Element identifier | | | | | | | | octet 1 | | | | | +| Length | | | | | | | | octet 2 | | | | | +| Length cont. | | | | | | | | octet 3 | | | | | +| Spare | | | | Cell identification discriminator | | | | octet 4 | | | | | +| Cell identification 1 | | | | | | | | octet 5 to
4+m | | | | | +| | | | | | | | | .. to 4+mn | | | | | +| Cell identification n | | | | | | | | | | | | | + +**Figure 8.2.6.1: Cell List information element** + +The Length depends on the Cell identification discriminator (bits 1 to 4 of octet 4) as well as the number of cells to be identified. + +The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to 3GPP TS 23.003 [2] is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: + +| | | +|------|------------------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cells. | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, is used to identify the cells. | +| 0010 | Cell Identity, CI, is used to identify the cells. | +| 0100 | Location Area Identification, LAI, is used to identify all cells within a Location Area. | +| 0101 | Location Area Code, LAC, is used to identify all cells within a location area. | +| 0110 | All cells in the BSC are identified. | + +All other values are reserved. + +The coding of the Cell Identifications 1 to n (octets 5 to 4+nm) depends on the Cell identification discriminator (bits 1 to 4 of octet 4). Below the coding of the i-th Cell Identification is shown for each Cell identification discriminator (with "i" in the range 1 to n): + +NOTE: No coding is specified for Cell identification discriminator value "0110" as no additional information is required. + +Coding of the i-th Cell Identification for Cell identification discriminator = 0000 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|----------------|---|---|---|-----------|---|---|---|-----------|--|--|--|--| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | | | | | +| MNC dig 3 | | | | MCC dig 3 | | | | octet x+2 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | | | | | +| LAC | | | | | | | | octet x+4 | | | | | +| LAC cont. | | | | | | | | octet x+5 | | | | | +| CI value | | | | | | | | octet x+6 | | | | | +| CI value cont. | | | | | | | | octet x+7 | | | | | + +**Figure 8.2.6.2: Coding of the i-th Cell Identification for Cell identification discriminator = 0000** + +Where $x = 4 + 7(i-1)$ . + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008 [5], Table 'Location Area Identification information element'. + +The octets (x+6)-(x+7) are coded as shown in 3GPP TS 24.008 [5], Table 'Cell Identity information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +Coding of i-th Cell Identification for Cell identification discriminator = 0001 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | +| CI value | | | | | | | | octet x+3 | +| CI value cont. | | | | | | | | octet x+4 | + +**Figure 8.2.6.3: Coding of the i-th Cell Identification for Cell identification discriminator = 0001** + +Where $x = 4 + 4(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008 [5], Table 'Location Area Identification information element'. + +The octets (x+3)-(x+4) are coded as shown in 3GPP TS 24.008 [5], Table 'Cell Identity information element'. + +Coding of i-th Cell Identification for Cell identification discriminator = 0010 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------|---|---|---|---|---|---|---|-----------| +| CI value | | | | | | | | octet x+1 | +| CI value cont. | | | | | | | | octet x+2 | + +**Figure 8.2.6.4: Coding of the i-th Cell Identification for Cell identification discriminator = 0010** + +Where $x = 4 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008 [5], Table 'Cell Identity information element'. + +Coding of i-th Cell Identification for Cell identification discriminator = 0100 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | +|-----------|---|---|-----------|---|---|---|---|--|-----------|--|--|--|--|--|--| +| MCC dig 2 | | | MCC dig 1 | | | | | | octet x+1 | | | | | | | +| MNC dig 3 | | | MCC dig 3 | | | | | | octet x+2 | | | | | | | +| MNC dig 2 | | | MNC dig 1 | | | | | | octet x+3 | | | | | | | +| LAC | | | | | | | | | octet x+4 | | | | | | | +| LAC cont. | | | | | | | | | octet x+5 | | | | | | | + +**Figure 8.2.6.5: Coding of the i-th Cell Identification for Cell identification discriminator = 0100** + +Where $x = 4 + 5(i-1)$ + +The octets (x+1)-(x+5) are coded as shown in 3GPP TS 24.008 [5], Table 'Location Area Identification information element'. + +*MNC dig 3* digit shall be set to '1111' if 2-digit MNC is used. + +Coding of i-th Cell Identification for Cell identification discriminator = 0101 + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | + +**Figure 8.2.6.6: Coding of the i-th Cell Identification for Cell identification discriminator = 0101** + +Where $x = 4 + 2(i-1)$ + +The octets (x+1)-(x+2) are coded as shown in 3GPP TS 24.008 [5], Table 'Location Area Identification information element'. + +### 8.2.7 Category + +*Category* IE indicates the priority of the CBS message. + +It is a fixed length element coded as follows: + +![](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Category | | | | | | | | octet 2 | + +**Figure 8.2.7.1: Category information element** + +The Category field is coded as follows: + +| | | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 0000 | High Priority; The CBS message shall be broadcasted if message slots according to the associated repetition period are available on the CBCH following the scheduling of already accepted high and/or normal priority CBS messages. The first broadcast of the CBS message shall be done at the earliest opportunity and the subsequent broadcasts according to the associated repetition period. | +| 0000 0001 | Background; The CBS message shall be broadcasted if message slots according to the associated repetition period are available on the CBCH following the scheduling of high and/or normal priority CBS messages and/or already accepted background messages. | +| 0000 0010 | Normal; The CBS message shall be broadcasted if message slots according to the associated repetition period are available on the CBCH following the scheduling of already accepted high and/or normal priority CBS messages. | + +All other values are reserved. + +### 8.2.8 Repetition Period + +*Repetition Period* IE indicates the periodicity of which the CBS message is to be broadcasted. The minimum period in which a CBS message consisting of one page may be broadcasted over the air interface is a period of 1.883 s. + +The *Repetition Period* IE is a fixed length element coded as follows: + +![](4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg) + +| | | | | | | | | | +|--------------------|---|---|---|-------------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Repetition Period | | | | | | | | octet 2 | +| Spare | | | | Repetition Period cont. | | | | octet 3 | + +**Figure 8.2.8.1: Repetition Period information element** + +The value of the "Repetition Period" field has the range 1 to 4 095 where each unit represent the value of one minimum period, i.e. 1.883 s. + +The "Repetition Period" field is coded as follows: + +| | | +|----------------|-------------------| +| 0000 0000 0000 | reserved | +| 0000 0000 0001 | 1.883 second | +| ... | | +| 1111 1111 1111 | 7 710.885 seconds | + +In the event of a conflict where the BSC has more than one CBS message to send at the same time, the BSC shall decide the order of such CBS messages as an implementation matter. + +### 8.2.9 Number of Broadcasts Requested + +*Number of Broadcasts Requested* IE indicates the number of times a CBS message is to be broadcasted. + +It is a fixed length element coded as follows: + +![](3c9703dd9f04f204e4b935c80eb96f0d_img.jpg) + +| | | | | | | | | | +|--------------------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Number of Broadcasts Requested | | | | | | | | octet 2 | +| Number of Broadcasts Requested cont. | | | | | | | | octet 3 | + +**Figure 8.2.9.1: Number of Broadcasts Requested information element** + +The coding of the "Number of Broadcasts Requested" field is the binary value of octet 2 and 3. It may take any value from 0 up to 65 535. + +If the "Number of Broadcasts Requested" field is set to value "0" then the CBS message shall be broadcasted indefinitely until CBC request otherwise. + +### 8.2.10 Number of Broadcasts Completed List + +*Number of Broadcasts Completed List* IE indicates the number of times a CBS message has been sent to each cell specified in the *Cell List* IE. The *Number of Broadcasts Completed List* IE must contain at least one cell. + +This element is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|----------------------------------------|---|---|---|-----------------------------------|---|---|---|----------------------|--|--|--|--| +| Element identifier | | | | | | | | octet 1 | | | | | +| Length | | | | | | | | octet 2 | | | | | +| Length cont. | | | | | | | | octet 3 | | | | | +| Spare | | | | Cell identification discriminator | | | | octet 4 | | | | | +| Cell identification 1 | | | | | | | | octet 5 to
4+m | | | | | +| Number of Broadcasts Completed 1 | | | | | | | | octet 4+m+1 | | | | | +| Number of Broadcasts Completed cont. 1 | | | | | | | | octet 4+m+2 | | | | | +| Spare | | | | Number of Broadcasts Info 1 | | | | octet 4+m+3 | | | | | +| Cell identification n | | | | | | | | .. to 4+(m+
3)n-3 | | | | | +| Number of Broadcasts Completed n | | | | | | | | .. to 4+(m+
3)n-2 | | | | | +| Number of Broadcasts Completed cont. n | | | | | | | | .. to 4+(m+
3)n-1 | | | | | +| Spare | | | | Number of Broadcasts Info n | | | | .. to 4+(m+
3)n | | | | | + +**Figure 8.2.10.1: Number of Broadcasts Completed List information element** + +The Length (octet 2 and 3) depends on the Cell identification discriminator (bits 1 to 4 of octet 4) as well as the number of cells to be identified. + +The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to 3GPP TS 23.003 [2] is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: + +| | | +|------|--------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cells. | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, is used to identify the cells. | +| 0010 | Cell Identity, CI, is used to identify the cells. | + +All other values are reserved. + +The coding of the Cell Identifications 1 to n (octets 5 to 4+n+m+ n3-3) depends on the Cell identification discriminator (bits 1 to 4 of octet 4). The coding of the i-th Cell Identification for each Cell identification discriminator (with "i" in the range 1 to n) is defined in subclause 8.2.6. + +The Number of Broadcasts Completed field contains the number of times a CBS message (i.e. all pages of a CBS message) has been broadcasted in the specific cell. The value range of the field is 0 to 65 535. + +The Number of Broadcasts Info field may contain some additional information to the broadcasted CBS message. The Number of Broadcasts Info field is coded as follows: + +| | | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 | No additional information: The number of completed broadcasts indicated in the Number of Broadcasts Completed field is valid. | +| 0001 | Overflow: The counter for the number of completed broadcasts in the specific cell has overflowed. The actual number of completed broadcasts is greater than the value indicated in the Number of Broadcasts Completed field. | +| 0010 | Unknown: Indicates that there is no information regarding the number of completed broadcasts in the BSC for the CBS message. The value indicated in the Number of Broadcasts Completed field is undefined in this case. | + +All other values are reserved. + +### 8.2.11 Failure List + +*Failure List* IE identifies the list of cells for which the BSC could not complete the request. The *Failure List* IE must contain at least one cell. + +This element is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|---|---|---|---|---|---|---|---------------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Length cont. | | | | | | | | octet 3 | +| Cell identification Element 1 | | | | | | | | octet 4 to
4+m+1 | +| Cell identification Element n | | | | | | | | octet p to
p+m+1 | + +**Figure 8.2.11.1: Failure List information element** + +Where p is the first octet in the last instance (n) of the Cell identification Element. + +The Length field (octets 2 and 3) is coded as the binary value of the number of octets in the *Failure List* IE directly following the Length field element. The length of the *Failure List* IE depends on the length of each Cell identification Element as well as the number of Cell identification Elements to be included in the list. + +The coding of the Cell identification Element field is as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|---------------------|---|---|---|-----------------------------------|---|---|---|---------------------|--|--|--|--| +| Spare | | | | Cell identification discriminator | | | | octet z | | | | | +| Cell identification | | | | | | | | octet z+1 to
z+m | | | | | +| Cause | | | | | | | | octet z+m+1 | | | | | + +**Figure 8.2.11.2: Cell identification Element field** + +Depending on the Cell identification discriminator value, m may take any of the values 1, 2, 4, 5 or 7 in the different instances of the Cell identification Element fields. + +The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to 3GPP TS 23.003 [2] is used for cell identification of each cell in the list. The Cell identification discriminator is coded as follows: + +| | | +|------|------------------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cell. | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell. | +| 0010 | Cell Identity, CI, is used to identify the cell. | +| 0100 | Location Area Identification, LAI, is used to identify all cells within a Location Area. | +| 0101 | Location Area Code, LAC, is used to identify all cells within a Location Area. | +| 0110 | All cells in the BSC are identified. | + +All other values are reserved. + +The coding of the Cell Identifications 1 to n (octets z+1 to z+m) depends on the Cell identification discriminator 1 to n (bits 1 to 4 of octet z). The coding of the i-th Cell Identification for each Cell identification discriminator (with "i" in the range 1 to n) is defined in subclause 8.2.6. + +NOTE: For Cell identification discriminator value "0110", the Cell identification field consist of one octet with the value set to "0000 0000". + +The "Cause" field is coded as defined in subclause 8.2.13. + +### 8.2.12 Radio Resource Loading List + +*Radio Resource Loading List* IE contains a list of the predicted short term load of the CBCH in each cell. The *Radio Resource Loading List* IE must contain at least one cell. + +This element is of variable length containing the following fields: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------|---|---|---|-----------------------------------|---|---|---|-------------------------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Length cont. | | | | | | | | octet 3 | +| Spare | | | | Cell identification discriminator | | | | octet 4 | +| Cell identification 1 | | | | | | | | octet 5 to
4+m | +| Radio Resource Load 1 1 | | | | | | | | octet 4+m+1 | +| Radio Resource Load 2 1 | | | | | | | | octet 4+m+2 | +| Cell identification n | | | | | | | | .. to
4+(m+2)n
-2 | +| Radio Resource Load 1 n | | | | | | | | .. to
4+(m+2)n-1 | +| Radio Resource Load 2 n | | | | | | | | .. to
4+(m+2)n | + +**Figure 8.2.12.1: Radio Resource Loading List information element** + +The Length depends on the Cell identification discriminator (bits 1 to 4 of octet 4) as well as the number of cells to be identified. + +The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to 3GPP TS 23.003 [2] is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: + +| | | +|------|--------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the cells. | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, is used to identify the cells. | +| 0010 | Cell Identity, CI, is used to identify the cells. | + +All other values are reserved. + +The coding of the Cell Identifications 1 to n (octets 5 to 4+nm+n-1) depends on the Cell identification discriminator (bits 1 to 4 of octet 4). The coding of the i-th Cell Identification for each Cell identification discriminator (with "i" in the range 1 to n) is defined in subclause 8.2.6. + +The Radio Resource Load 1 field reflects the number of used CBCH message slots in relation to the number of available CBCH message slots expressed as a percentage. Number of used CBCH message slots is defined as message slots reserved for schedule messages, message slots used for high and normal priority CBS messages according to their requested repetition period and slots reserved for "free message slot reading advised". + +The Radio Resource Load 2 field reflects the number of CBCH message slots used for background CBS messages according to their requested repetition period in relation to the number of available CBCH message slots expressed as a percentage. + +If the broadcast periodicity of a background CBS message is reduced due to the reception of a high or normal priority CBS message broadcast request for the same cell, the requested repetition period for the background CBS message shall be taken into account. In this case the total sum of the CBCH radio resource load as indicated in Radio Resource Load 1 and Radio Resource Load 2 fields will exceed 100 %. + +Radio Resource Load 1 and Radio Resource Load 2 fields are coded as a binary number representing a percentage load of the CBCH. + +| | | +|-----------|-----------------------------| +| 0000 0000 | no CBCH load in the cell | +| 0000 0001 | 1 % CBCH load in the cell | +| ... | | +| 0110 0100 | 100 % CBCH load in the cell | + +All other values are reserved. + +### 8.2.13 Cause + +*Cause* IE indicates the reason for a particular error event in the BSC. + +The *Cause* IE is a fixed length element coded as follows: + +![](a93de4c3f80bd4a972ab65510b09b68d_img.jpg) + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | +| Cause Value | | | | | | | | octet 2 | + +**Figure 8.2.13.1: Cause information element** + +The "Cause Value" field is coded as follows: + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000 0000 | Parameter-not-recognised: Sent when the recipient (CBC or BSC) is 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. | +| 0000 0001 | Parameter-value-invalid: Sent when a failure occurred due to the value of a parameter being invalid, e.g. out of range, or when the combinations of two or more parameter values are invalid. | +| 0000 0010 | Message-reference-not-identified: Sent when the BSC does not recognise the Message Reference of a CBS message or an emergency message. | +| 0000 0011 | Cell-identity-not-valid: Sent when the BSC does not recognise a cell identity. | +| 0000 0100 | Unrecognised-message: Sent when the BSC does not recognise the CBSP message at all. | +| 0000 0101 | Missing-mandatory-element: Sent when a mandatory element is missing in the CBSP message. | +| 0000 0110 | BSC-capacity-exceeded: Sent when a WRITE-REPLACE message fails due to the BSC cannot meet the requested repetition period or when the Set-DRX parameters cannot be applied because of cell loading. | +| 0000 0111 | Cell-memory-exceeded: Sent when the local cell memory has been exceeded. | +| 0000 1000 | BSC-memory-exceeded: Sent when the BSC is unable to store a CBS message or an emergency message as the BSC memory has been exceeded. | +| 0000 1001 | Cell-broadcast-not-supported: Sent when the CBCH related radio resource is not configured for a cell. | +| 0000 1010 | Cell-broadcast-not-operational: Sent when the CBCH related radio resource is not available due to maintenance activities or error conditions in the BSC. | +| 0000 1011 | Incompatible-DRX-parameter: Sent when the DRX parameter(s) cannot be applied. | +| 0000 1100 | Extended-channel-not-supported: Sent when a WRITE-REPLACE message fails because the extended channel is not configured in the cell. | +| 0000 1101 | Message-reference-already-used: Sent when the BSC is unable to act upon the WRITE-REPLACE message since the same Message Reference was received in a previous WRITE-REPLACE message. | +| 0000 1110 | Unspecified-error: Sent when none of the specified Cause Values apply. | +| 0000 1111 | LAI-or-LAC-not-valid: Sent when the BSC does not recognise a Location Area Identification or a Location Area Code. | + +All other values are reserved. + +### 8.2.14 Data Coding Scheme + +*Data Coding Scheme* IE identifies the alphabet or coding employed for the message characters and message handling in the mobile station. The *Data Coding Scheme* IE is a fixed length element sent transparently from the CBC to the mobile station. + +It is coded as follows: + +![](5391e1303dec02a02e7e42b5a4ffe58a_img.jpg) + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | octet 1 | +| Element identifier | | | | | | | | | +| Data Coding Scheme | | | | | | | | octet 2 | + +**Figure 8.2.14.1: Data Coding Scheme information element** + +The "Data Coding Scheme" field is coded as the 'CBS Data Coding Scheme' defined in 3GPP TS 23.038 [4]. + +### 8.2.15 Recovery Indication + +*Recovery Indication* IE indicates if the CBS message or emergency message related data is lost or still available in the BSC. + +It is a fixed length element coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | Recovery Indication | | | | | + +**Figure 8.2.15.1: *Recovery Indication* information element** + +The "Recovery Indication" field is coded as follows: + +| | | +|------|--------------------------------------| +| 0000 | CBS/emergency message data available | +| 0001 | CBS/emergency message data lost | + +All other values are reserved. + +### 8.2.16 Message Identifier + +*Message Identifier* IE is a fixed length element identifying the source and type of the CBS message or emergency message. Together with New/Old Serial Number, Cell Identifier and Channel Indicator the *Message Identifier* IE enables identification of a CBS message. Together with New/Old Serial Number and Cell Identifier the *Message Identifier* IE enables identification of an emergency message. + +The coding is as follows: + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Message Identifier | | | | | | | | octet 2 | +| Message Identifier cont. | | | | | | | | octet 3 | + +**Figure 8.2.16.1: *Message Identifier* information element** + +Octets 2-3 are coded as the 'Message-Identifier' defined in 3GPP TS 23.041 [1]. + +### 8.2.17 Emergency Indicator + +*Emergency Indicator* IE indicates that the WRITE-REPLACE message contains an emergency message (e.g. an ETWS Primary Notification message) to be further transferred to the mobile station. + +The *Emergency Indicator* IE is a fixed length element coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | Emergency Indicator | | | | | + +**Figure 8.2.17.1: *Emergency Indicator* information element** + +The "Emergency Indicator" field is coded as follows: + +| | | +|------|----------------------------| +| 0000 | reserved | +| 0001 | ETWS information available | + +All other values are reserved. + +### 8.2.18 Warning Type + +*Warning Type* IE is sent transparently from the CBC to the mobile station containing ETWS related warning information. + +The *Warning Type* IE is a fixed length element coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Warning Type | | | | | | | | octet 2 | +| Warning Type cont. | | | | | | | | octet 3 | + +**Figure 8.2.18.1: Warning Type information element** + +Octets 2-3 are coded as the 'Warning-Type' defined in 3GPP TS 23.041 [1]. + +### 8.2.19 Warning Security Information + +NOTE: The *Warning Security Information* IE does not serve any purpose. It is only included due to requirements in earlier versions of 3GPP TS 23.041 [1]. + +*Warning Security Information* IE is sent transparently from the CBC to the mobile station. It is only included when the ETWS related warning information is sent with security. + +The *Warning Security Information* IE is a fixed length element coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|---|---|---|---|---|---------------| +| Element identifier | | | | | | | | octet 1 | +| Warning Security Information | | | | | | | | octet 2 to 51 | + +**Figure 8.2.19.1: Warning Security Information information element** + +The "Warning Security Information" field is coded as the 'Warning-Security-Information' defined in 3GPP TS 23.041 [1]. + +### 8.2.20 Channel Indicator + +*Channel Indicator* IE indicates the type of cell broadcast channel (CBCH) to be used for broadcasting of the CBS message. The CBCH can be of type basic or extended (see 3GPP TS 45.002 [11]). + +The *Channel Indicator* IE is a fixed length element coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-------------------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | Channel Indicator | | | | octet 2 | + +**Figure 8.2.20.1: Channel Indicator information element** + +The Channel Indicator field is coded as follows: + +0000 basic channel + 0001 extended channel (support of extended channel is optional in the BSC/MS) + +All other values are reserved. + +### 8.2.21 Number of Pages + +*Number of Pages* IE indicates the total number of pages in the CBS message, i.e. the number of *Message Content* IEs included in the WRITE-REPLACE message. + +The *Number of Pages* IE is a fixed length element coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-----------------|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | Number of Pages | | | | octet 2 | + +**Figure 8.2.21.1: Number of Pages information element** + +The "Number of Pages" field is coded as the binary value of the total number of pages in the CBS message. It is coded as follows: + +| | | +|------|---------------| +| 0000 | reserved | +| 0001 | one page | +| ... | | +| 1111 | fifteen pages | + +### 8.2.22 Schedule Period + +*Schedule Period* IE indicates the SMSCB DRX schedule period length. + +The *Schedule Period* IE is a fixed length element coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Schedule Period | | | | | | | | octet 2 | + +**Figure 8.2.22.1: *Schedule Period* information element** + +The "Schedule Period" field is coded as the binary value of number of slots in the Schedule message (see 3GPP TS 44.012 [3]). + +| | | +|-----------|--------------------| +| 0000 0000 | no schedule period | +| 0000 0001 | 1 slot | +| ... | | +| 0010 1000 | 40 slots | + +All other values are reserved. + +NOTE: The maximum value of the schedule period length is limited to 40 since the schedule message cannot be built entirely if more than 40 CBS messages have to be described in the period (see 3GPP TS 44.012 [3]). + +The "Schedule Period" field must be given a higher value than the *Reserved Slots* IE. + +If the "Schedule Period" field is set to value "0", the SMSCB DRX mode of operation shall not be used. + +### 8.2.23 Number of Reserved Slots + +*Number of Reserved Slots* IE indicates the number of reserved slots in the Schedule message (see 3GPP TS 44.012 [3]). + +The *Number of Reserved Slots* IE is a fixed length element coded as follows: + +| | | | | | | | | | +|--------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Number of Reserved Slots | | | | | | | | octet 2 | + +**Figure 8.2.23.1: *Number of Reserved Slots* information element** + +The "Number of Reserved Slots" field is coded as the binary value of number of "free slots reading advised" in the Schedule message (see 3GPP TS 44.012 [3]). The reserved slots in a SMSCB DRX schedule period can be used for broadcasting of incoming high priority CBS messages. + +| | | +|-----------|-------------------| +| 0000 0000 | no reserved slots | +| 0000 0001 | 1 reserved slot | +| ... | | +| 0010 1000 | 40 reserved slots | + +All other values are reserved. + +The "Number of Reserved Slots" field must be given a lower value than the *Schedule Period* IE. + +### 8.2.24 Broadcast Message Type + +*Broadcast Message Type* IE indicates if the information included in the CBSP message is referring to CBS message broadcasting or emergency message broadcasting. + +The *Broadcast Message Type* IE is a fixed length element coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|------------------------|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | Broadcast Message Type | | | | octet 2 | + +**Figure 8.2.24.1: *Broadcast Message Type* information element** + +The Broadcast Message Type field is coded as follows: + +| | | +|------|--------------------------------| +| 0000 | CBS message broadcasting | +| 0001 | emergency message broadcasting | + +All other values are reserved. + +### 8.2.25 Warning Period + +*Warning Period* IE indicates the length of the period during which the emergency message is to be broadcasted in the BSC. + +The *Warning Period* IE is a fixed length element coded as follows: + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Warning Period | | | | | | | | octet 2 | + +**Figure 8.2.25.1: *Warning Period* information element** + +The Warning Period field is coded as follows: + +| | | +|-----------|-------------------| +| 0000 0000 | unlimited | +| 0000 0001 | 1 second | +| :::: | in 1 second step | +| 0000 1010 | 10 seconds | +| :::: | in 2 second step | +| 0001 0100 | 30 seconds | +| :::: | in 5 second step | +| 0010 0110 | 2 minutes | +| :::: | in 10 second step | +| 0101 0110 | 10 minutes | +| :::: | in 30 second step | +| 1011 1010 | 60 minutes | + +All other values are reserved. + +If the Warning Period field is set to value "0", the emergency message is broadcasted until the CBC requests otherwise + +### 8.2.26 Length Indicator + +*Length Indicator* IE indicates the number of octets in the set of information elements included in the CBSP message. + +The *Length Indicator* IE is a fixed length element coded as follows: + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Length Indicator | | | | | | | | octet 1 | +| Length Indicator cont. | | | | | | | | octet 2 | +| Length Indicator cont. | | | | | | | | octet 3 | + +**Figure 8.2.26.1: *Length Indicator* information element** + +The Length Indicator field is coded as the binary value of the number of octets in the set of information elements included in the CBSP message, excluding the 1 octet of the *Message Type* IE and the 3 octets of the *Length Indicator* IE itself. + +If the CBSP message does not contain a set of information elements (e.g. KEEP-ALIVE COMPLETE message) then the binary value of the Length Indicator field is coded as zero. + +### 8.2.27 Keep Alive Repetition Period + +*Keep Alive Repetition Period* IE indicates the periodicity of the KEEP-ALIVE message sent from the CBC, + +The *Keep Alive Repetition Period* IE is a fixed length element coded as follows: + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Keep Alive Repetition Period | | | | | | | | octet 2 | + +**Figure 8.2.27.1: Keep Alive Repetition Period information element** + +The Keep Alive Repetition Period field is coded as follows: + +| | | +|-----------|------------------| +| 0000 0000 | reserved | +| 0000 0001 | 1 second | +| : : : : | in 1 second step | +| 0000 1010 | 10 seconds | +| : : : : | in 2 second step | +| 0001 0100 | 30 seconds | +| : : : : | in 5 second step | +| 0010 0110 | 2 minutes | + +All other values are reserved. + +# 9 List of system parameters + +## 9.1 Timers in the CBC + +The description of timers below should be considered as a brief summary. The precise details are found in clause 7, which should be considered as the definitive description. + +**T1:** This timer is started when the KEEP-ALIVE message is sent from the CBC to the BSC. It is stopped at the reception of the KEEP-ALIVE COMPLETE message in the CBC. + +At expiry, the Keep Alive procedure is considered as failed. + +The value of the timer is network dependent. + +# --- Annex A (informative): Change History + +| Date/
TSG# | TDoc | CR | Rev | Subject/Comment | Version | +|-----------------|------|----|-----|--------------------------------------|---------| +| January
2016 | | | | Creation of v13.0.0 based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|----------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New
version | +| 2017-03 | RP-75 | | | | | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48051/raw.md b/marked/Rel-16/48_series/48051/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e8d6a3426c8f5c5631583493cd0af37449085023 --- /dev/null +++ b/marked/Rel-16/48_series/48051/raw.md @@ -0,0 +1,197 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 Abbreviations ..... 6 + +4 Interface capabilities ..... 6 + +5 Interface specification objectives..... 6 + +6 Interface characteristics..... 7 + +7 Other technical specifications on the BSC-BTS interface ..... 7 + +7.1 3GPP TS 48.052 BSC-BTS Interface Principles ..... 7 + +7.2 3GPP TS 48.054 BSC-BTS Layer 1 Specification ..... 7 + +7.3 3GPP TS 48.056 BSC-BTS Layer 2 Specification ..... 7 + +7.4 3GPP TS 48.058 BSC-BTS Layer 3 Specification ..... 7 + +7.5 3GPP TS 12.21 BSC-BTS Operation/Maintenance Signalling ..... 8 + +7.6 3GPP TS 48.060 Inband Control of Remote Transcoders and Rate Adaptors ..... 8 + +7.7 3GPP TS 48.061 Inband Control of Remote Transcoders and Rate Adaptors for Half Rate Traffic +Channels..... 8 + +Annex A (informative): Change History..... 9 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document is an introduction to the 48.5xx - 48.6xx series of 3GPP Technical Specifications and deals with the definition of the Base Station Controller (BSC) to Base Transceiver Station (BTS) interface defined inside the Base Station System (BSS) for the GSM system. These Technical Specifications define the basic interface with some identified options requiring further elaboration. The BSC-BTS interface is mandatory within GSM only if the BSC and the BTS are not colocated. + +# --- 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 43.050: "Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system". +- [3] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [4] Void. +- [5] 3GPP TS 48.052: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Interface principles". +- [6] 3GPP TS 48.054: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 1 structure of physical circuits". +- [7] 3GPP TS 48.056: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification". +- [8] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification". +- [9] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors for full rate traffic channels". +- [10] 3GPP TS 48.061: "Inband control of remote transcoders and rate adaptors for half rate traffic channels". +- [11] Void. +- [12] Void. +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. + +- [18] Void. +- [19] Void. +- [20] Void. +- [21] Void. +- [22] Void. +- [23] Void. +- [24] 3GPP TS 12.21: "Network Management (NM) procedures and messages on the A-bis interface". +- [25] Void. +- [26] ITU-T Recommendation Q.920: "ISDN user-network interface data link layer - General aspects". +- [27] ITU-T Recommendation Q.921: "ISDN user-network interface - Data link layer specification". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# --- 4 Interface capabilities + +The BSC-BTS interface shall be capable of supporting all the services offered to the GSM users and subscribers. In addition it shall also allow control of the radio equipment and radio frequency allocation in the BTS. + +# --- 5 Interface specification objectives + +The BSC to BTS interface specifications should allow the following: + +- (I) Connection of various manufacturers BTS/TRX to the same BSC, according to the location of the transcoder. +- (II) The use of several manufacturers BSC to the same type of BTS/TRX, according to the location of the transcoder. +- (III) The use of the same BTS/TRX in any PLMN, according to the location of the transcoder. +- (IV) The use of the same BSC in any PLMN. +- (V) Separate evolution of BSC and BTS/TRX technology. +- (VI) Separate evolution of O & M facilities. +- (VII) Sub-multiplexing of speech channels on a 64 kbit circuit. +- (VIII) Evolution towards lower speech coding rates. +- (IX) Location of transcoders either in BSC or in BTS. +- (X) Support of all services defined in the 02 series of 3GPP TS Technical Specifications. +- (XI) A stepwise expansion of capacity in a BTS. +- (XII) Different physical solution of the various equipment in the BTS. +- (XIII) Support of a single TRX forming a BTS. +- (XIV) Support of a set of TRX'S forming a BTS. +- (XV) Support of a BTS as one entity. + +# --- 6 Interface characteristics + +The interface is defined to be at the terrestrial link of a remote BTS connected to the BSC. + +The BSC to BTS interface is specified by a set of characteristics, including: + +- a) physical and electrical parameters; +- b) channel structures; + +- c) signalling transfer procedures; +- d) configuration and control procedures; +- e) operation and maintenance information support. + +The definition of the BSC to BTS/TRX interface follows a layered approach similar to the ISDN. Layer 3 is for the most part based on Technical Specification 3GPP TS 48.008 with additional procedures for control of radio resources. Layer 2 is based on the LAPD protocol. Layer 1 is either digital (at a rate 2 048 kbit/s with a frame structure of 32 x 64 kbit/s time slots or at a rate of 64 kbit/s) or analogue with the data being passed by the use of modems (this latter case is a national option). + +In the case that the transcoder is positioned outside the BTS, the overall one way propagation delay between the Point of Interconnection to PSTN/ISDN and the MS is limited to 1,5 ms (approximately 300 km). With the transcoder in the BTS, the limit is 6,5 ms (approximately 1 300 km). These limits may be subject to increase resulting from savings made in the overall network. See also Technical Specification 3GPP TS 43.050. + +# --- 7 Other technical specifications on the BSC-BTS interface + +The full structure of the Technical Specifications specifying the BSC to BTS interface are as follows: + +## 7.1 3GPP TS 48.052 BSC-BTS Interface Principles + +3GPP TS 48.052 gives the principle basis for the rest of the specifications specifying the interface between the base station controller and the base transceiver station. It gives the functional split between these two entities. + +## 7.2 3GPP TS 48.054 BSC-BTS Layer 1 Specification + +3GPP TS 48.054 defines the structure of the physical layer at the BSC - BTS interface. The physical interface is either chosen as 2 048 kbit/s or as 64 kbit/s, both according to standard ITU-T recommendations. + +Depending on location of transcoders, speech is standard A-law or it is 16 kbit/s remote control protocol multiplexed or rate adapted to 64 kbit/s in the same way as data. + +## 7.3 3GPP TS 48.056 BSC-BTS Layer 2 Specification + +At layer 2 the signalling information is passed by a standard LAPD protocol mechanism in accordance with the ITU-T Recommendations Q.920 and Q.921. + +## 7.4 3GPP TS 48.058 BSC-BTS Layer 3 Specification + +3GPP TS 48.058 specifies the layer 3 procedures used on the BSC-BTS interface for control of the GSM services. The functional split between BSC and BTS is defined in Technical Specification 3GPP TS 48.052. + +## 7.5 3GPP TS 12.21 BSC-BTS Operation/Maintenance Signalling + +3GPP TS 12.21 defines the transport mechanism for O&M messages over the Abis interface. O&M procedures and messages are defined in 3GPP TS 12 series. + +## 7.6 3GPP TS 48.060 Inband Control of Remote Transcoders and Rate Adaptors + +The transcoder is a part of the BSS and may optionally be located outside the BTS (e.g. at MSC-site or at BSC-site) in order to make it possible to multiplex speech and data channels on the links within the BSS and on the BSC-BTS link. + +3GPP TS 48.060 describes the protocol which carries the full rate speech and data frames between the transcoder and the radio link codec across a 16 kbit/sec interface. Both full rate speech and full rate data services are covered. It also defines the signals needed for remote controlling the timing of the transcoder in accordance to the transmission time at + +the radio link. It also addresses the signals for voice activity and comfort noise. It interfaces the 06- series to the 05-series. + +## 7.7 3GPP TS 48.061 Inband Control of Remote Transcoders and Rate Adaptors for Half Rate Traffic Channels + +3GPP TS 48.061 describes the protocol which carries the half rate speech and data frames between the transcoder and the radio link codec across a 16 kbit/s or an 8 kbit/s interface. Both half rate speech and half rate data services are covered. It also defines the signals needed for remote controlling the timing of the transcoder in accordance to the transmission time at the radio link. It also addresses the signals for voice activity and comfort noise. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|----------|----|-----|-----------------------------------------|--------| +| January 2016 | - | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | | | | | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48052/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/48_series/48052/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ccb862328d1682e649080caed06b31d6c879861 --- /dev/null +++ b/marked/Rel-16/48_series/48052/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5af4916621fceb1e8957edb577864e201d0e06426ea5fa61cd137f636ab4c0d5 +size 73101 diff --git a/marked/Rel-16/48_series/48052/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-16/48_series/48052/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78ee1ce538365fd6755a6d4f27236be5dbabe155 --- /dev/null +++ b/marked/Rel-16/48_series/48052/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aef9e1c2c5b453e4220cb0e0cf0f40607a553112c9ca9c0b5a7332f147b5dd21 +size 47779 diff --git a/marked/Rel-16/48_series/48052/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/48_series/48052/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b82e3f4e7ecb97db098a543ea6bff9990d70cf4 --- /dev/null +++ b/marked/Rel-16/48_series/48052/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5435e9f610c6d5e38f2ca76877358a65f92c862ba730ed7110f1c5e36a3d538d +size 20099 diff --git a/marked/Rel-16/48_series/48052/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/48_series/48052/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f4b0a998e92a48524598ef0e436038ab0f62c32 --- /dev/null +++ b/marked/Rel-16/48_series/48052/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:860b6dd6819539f5044e5b9de818006fc89a5f3873cb45fb9a2708c319386a20 +size 120528 diff --git a/marked/Rel-16/48_series/48052/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/48_series/48052/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe00ee6a9c1ee4c80a09a43f6e039e09b9b78347 --- /dev/null +++ b/marked/Rel-16/48_series/48052/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36c8c26e76029ca2d24e882e4b48ef1f43660c937cb353df146d3af304a1c005 +size 76152 diff --git a/marked/Rel-16/48_series/48052/raw.md b/marked/Rel-16/48_series/48052/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0bc033e348833d0fca65c9d3d0f411312d5afb7d --- /dev/null +++ b/marked/Rel-16/48_series/48052/raw.md @@ -0,0 +1,500 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 6 | +| 5 Functional division between BSC and BTS..... | 7 | +| 5.1 General ..... | 7 | +| 5.2 Terrestrial channel management ..... | 7 | +| 5.3 Radio channel management ..... | 7 | +| 5.3.1 Channel configuration management..... | 7 | +| 5.3.2 SDCCH (Stand alone DCCH) and TCH management..... | 8 | +| 5.3.2.1 Frequency hopping management..... | 8 | +| 5.3.2.2 Channel selection, link supervision and channel release..... | 8 | +| 5.3.2.3 Power control..... | 8 | +| 5.3.2.4 Idle channel observation ..... | 8 | +| 5.3.3 BCCH/CCCH management..... | 8 | +| 5.3.4 Random access ..... | 8 | +| 5.3.5 Channel coding/decoding ..... | 8 | +| 5.3.6 Transcoding/rate adaption ..... | 9 | +| 5.3.7 Timing advance ..... | 9 | +| 5.3.8 Radio resource indication..... | 9 | +| 5.3.9 Measurements..... | 9 | +| 5.3.10 LAPDm functions (Layer 2)..... | 9 | +| 5.3.11 Paging..... | 9 | +| 5.3.12 Handover ..... | 9 | +| 5.3.13 Encryption ..... | 10 | +| 5.3.14 Mobility management and call control..... | 10 | +| 6 Transcoding/rate adaption and multiplexing..... | 11 | +| 6.1 Transcoding/rate adaption in BTS..... | 11 | +| 6.2 Transcoding/rate adaption outside BTS ..... | 11 | +| 7 Interface structures..... | 12 | +| 7.1 Communication channels ..... | 12 | +| 7.2 Signalling links..... | 12 | +| 7.3 Signalling model ..... | 13 | +| Annex A (informative): Change History..... | 17 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The use and general aspects of the A-bis interface are given in 3GPP TS 48.051. + +The present document gives the principle basis for the rest of the specifications specifying the interface between the Base Station Controller, BSC, and the Base Transceiver Station, BTS, with its transceivers, TRX. These components together form the Base Station System, BSS. (The interface between MSC and the BSS is specified in 3GPP TS 48.001 and 3GPP TS 48.020). + +The intention with this interface is to get a unified way of connecting remotely located BTSs/TRXs to a BSC allowing for the interconnection of BSCs and BTSs/TRXs from different manufacturers. + +In order to keep the BTS as simple as possible, BTS contains only those functions which have to recide close to the radio interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 48.001: "Base Station System - Mobile services Switching Centre (BSS - MSC) interface; General aspects". +- [3] 3GPP TS 48.002: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface Interface principles". +- [4] Void. +- [5] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS-MSC) interface". +- [6] Void. +- [7] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS-MSC) interface". +- [8] 3GPP TS 48.051: "Base Station Controller - Base Transceiver Station (BSC-BTS) interface; General aspects". +- [9] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC-BTS) interface; Layer 3 specification". +- [10] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors for full rate traffic channels". +- [11] 3GPP TS 48.061: "Inband control of remote transcoders and rate adaptors for half rate traffic channels". +- [12] Void. +- [13] 3GPP TS 23.002: "Network Architecture". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Base Station System (BSS):** system of base station equipment (transceivers, controllers, etc..) which is viewed by the MSC through a single interface as defined by the 3GPP TS 48.0xx series of recommendations, as being the entity responsible for communicating with Mobile Stations in a certain area. The radio equipment of a BSS may cover one or more cells. A BSS may consist of one or more base stations. If an internal interface according to the 3GPP TS 48.05x series of recommendations is implemented, then the BSS shall consist of one Base Station Controller (BSC) and several Base Transceiver Stations (BTSs). + +NOTE: The functionality is described in 3GPP TS 48.001. + +**Base Station Controller (BSC):** network component in the PLMN with the functions for control of one or more Base Transceiver Stations (BTSs). + +**Base Transceiver Station (BTS):** network component which serves one cell, and is controlled by a Base Station Controller. The BTS can consist of one or more TRXs with or without common control equipment. + +**Cell:** See 3GPP TS 23.002. + +**Transceiver (TRX):** in the GSM PLMN is the functional entity which supports the 8 basic radio channels of the same TDMA-frame. + +**Base Control Function (BCF):** functional entity which handles common control functions within a BTS, e.g. frequency hopping sequences etc. + +At a multi BTS site, one of the BCFs can also be chosen to perform functions common to the site (e.g. external alarms, power supply, time base). + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# --- 4 General + +3GPP TS 48.001 and 3GPP TS 48.020 specify the functional split and interface between MSC and the Base Station System, BSS, the A- interface. + +The BSS can be further subdivided into one BSC controlling one or more BTSs, each consisting of one or more TRXs. The interface treated by the present document is the interface between a BSC and a BTS. It is denoted the A-bis-interface. + +The A-bis-interface is capable of supporting three different internal BTS configurations: + +- one single TRX; +- a collection of TRXs where all are served by a common physical connection; +- a collection of TRXs, each served by its own physical connection. + +Figure 4.1 shows some possible configurations. + +![Diagram of BSS Subdivision and Interfaces showing MSC, BSC, and multiple BTS units connected via A-bis interfaces.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram illustrates the functional subdivision of a Base Station Subsystem (BSS) and its interfaces. On the left, an MSC (Mobile Switching Center) is shown with an 'A' interface connecting it to a BSC (Base Station Controller). The BSC is connected to three separate BTS (Base Transceiver Station) units, labeled BTS1, BTS2, and BTS3. Each BTS unit is connected to the BSC via an 'A-bis' interface. The BSS is represented by a dashed box enclosing the BSC and the three BTS units. Inside each BTS unit, the internal components are shown: BTS1 contains TRX and BCF; BTS2 contains two TRX units and a BCF; BTS3 contains three TRX units and a BCF. The interfaces are represented by dashed lines with cross-ticks at the connection points. + +Diagram of BSS Subdivision and Interfaces showing MSC, BSC, and multiple BTS units connected via A-bis interfaces. + +**Figure 4.1: BSS Subdivision and Interfaces** + +The present document is based on the use of digital transmission system interfaces, either at 2 048 kbit/s or at 64 kbit/s. Furthermore, the use of a subrate of 16 kbit/s and/or 8 kbit/s is supported for coded speech or rate adapted data. + +This interface will support the transcoder positioned either inside or outside BTS. In the latter case, remote control (synchronisation) of the transcoder is used. + +# 5 Functional division between BSC and BTS + +## 5.1 General + +In Technical Specification 3GPP TS 48.001 the functional division between MSC and BSS is described. This clause describes the further subdivision of functions between BSC and BTS/TRX required for the A-bis interface. A summary can be found in table 5.1. Some general requirements on the functionality of the A-bis interface are also specified. + +## 5.2 Terrestrial channel management + +There is a unique mapping from traffic channels on the radio path to the terrestrial traffic channels. BSC makes the choice of radio channel and thereby also of the terrestrial channel for a call. + +## 5.3 Radio channel management + +### 5.3.1 Channel configuration management + +The channel configuration is controlled between the BSC and OMC. Current configuration is downloaded from OMC to BSC which then controls the use of the radio channels (TDMA time slots for BCCH/CCCH, TCHs, SDCCHs etc). + +### 5.3.2 SDCCH (Stand alone DCCH) and TCH management + +#### 5.3.2.1 Frequency hopping management + +The hopping sequences for each BTS (cell) is downloaded from OMC to BSC. It is then the responsibility of BSC to download this information to each BTS and also to send the corresponding BCCH information to be transmitted in the BCCH time slots. + +#### 5.3.2.2 Channel selection, link supervision and channel release + +These functions are controlled by BSC. For channel selection BSC has to have information on blocked radio channels and also on interference level on idle channels. + +In the assignment messages to MS (Immediate Assign, Assign Command and Handover Command), a Starting Time parameter is included. This starting time is based on the frame number on the (new) BTS. Before sending the assign message to MS, BSC has to be informed on the current frame number in BTS. + +When assigning a channel, BSC shall inform BTS on relevant parameters, e.g. channel type, channel coding, rate adaption, starting time. + +#### 5.3.2.3 Power control + +The ordered MS power level is sent in the 16 bit L1-header of SACCH- blocks on the downlink and the actual power level used by MS is reported in the corresponding L1-header on the uplink. This header is inserted (downlink) and extracted (uplink) by BTS/TRX. + +The determination of required power level in MS is based on uplink radio measurements made by BTS/TRX and reported to BSC. The basic control of this power is performed by BSC and the dynamic regulation is performed by BSC or optionally by BTS. If BTS supports dynamic MS power regulation, BSC can indicate whether BTS is to regulate the MS power and if so, also the parameters required by BTS. + +The required TRX transmission power level on a channel is based on reported measurements performed by MS. The dynamic control of this power is optional. If supported, the basic control is performed by BSC and the dynamic regulation is performed by BSC or optionally by BTS. If BTS supports dynamic TRX transmission power regulation, BSC can indicate whether BTS is to regulate the transmission power and if so, also the parameters required by BTS. + +#### 5.3.2.4 Idle channel observation + +Idle channels are monitored by BTS. + +### 5.3.3 BCCH/CCCH management + +TRX knows the timing of BCCH/CCCH slots (not known by BSC). The actual timing of BCCH/CCCH blocks therefore has to be made by BTS/TRX, including the scheduling of Paging Request messages on paging sub-channels. + +BCCH information is downloaded to BTS. + +### 5.3.4 Random access + +Detection of a random access attempt has to be made by TRX which then sends a message to BSC containing the required timing advance, the frame number of the access attempt and the 8 bit Channel Request message sent by MS in the access burst. This information is then included by BSC in the following Immediate Assign message sent to MS. + +### 5.3.5 Channel coding/decoding + +The error protection coding and decoding is made by BTS/TRX. + +Different coding and interleaving schemes are used for speech and data calls. This information has to be signalled from BSC to BTS on a per call basis. + +### 5.3.6 Transcoding/rate adaption + +The A-bis interface has to allow for the transcoder/rate adaptor being positioned either inside or outside BTS. + +### 5.3.7 Timing advance + +Timing advance has to be determined by TRX. + +When MS is on a dedicated channel (SDCCH, TCH), the required timing advance (TA) is sent to MS and the actual timing advance is reported by MS in the 16 bit L1-header of the SACCH blocks. + +At handover access, TA is determined by TRX and reported to MS in the PHYsical INFOrmation message sent by BTS/TRX. + +At random access, TA is determined by TRX but in those cases, TA has to be reported to BSC for inclusion in the IMMEDIATE ASSIGN message sent to MS by BSC. + +### 5.3.8 Radio resource indication + +BTS reports on status (interference level, blocking etc.) of idle channels to BSC on a regular basis. + +### 5.3.9 Measurements + +MS measures the downlink received level and quality from the serving cell and the received level from surrounding cells. The results from these measurements are reported by MS in Measurement Report messages on SACCH. + +Uplink received level and quality are measured by BTS/TRX. The parameters for the uplink measurements are equivalent to the parameters used by MS for the corresponding downlink measurements (averaging period and dynamic range). + +The support of forwarding this basic raw measurement data over the A-bis interface is mandatory. Additionally, BTS and BSC may optionally support some pre-processing in BTS of this data. + +### 5.3.10 LAPDm functions (Layer 2) + +Layer 2 on the radio interface (LAPDm) is terminated at BTS/TRX. Between BTS and BSC, LAPD is used. + +### 5.3.11 Paging + +Paging is initiated by MSC via BSC. + +BSC determines the paging group to be used based on IMSI of the MS to be paged. The paging group value is sent to BTS together with the TMSI or IMSI. + +Based on the paging group information, BTS/TRX will build the relevant PAGING REQUEST message and execute the transmission of the message in the correct paging sub-channel. + +### 5.3.12 Handover + +No handover recognition or decision is made by BTS. + +However, BTS/TRX has to detect the handover access made by a handed over MS. BTS/TRX also checks the Handover Reference value sent by MS in the handover access burst against the Handover Reference value received from BSC in the channel activation command. In case of an asynchronous handover, BTS/TRX then builds the PHYsical INFOrmation message (including the Timing Advance value) and sends it to MS. The handover access is also reported to BSC. + +### 5.3.13 Encryption + +Encryption and decryption is made of the complete outgoing bit stream (except for preambles/synch words). This therefore has to be made by TRX. The encryption key has to be downloaded to BTS/TRX before encryption starts. Special control messages are therefore required between BSC and BTS/TRX. + +### 5.3.14 Mobility management and call control + +All mobility management and call control functions reside in MSC. + +**Table 5.1: Summary of functional division between BTS and BSC/MSC** + +| FUNCTION | Location | | +|--------------------------------------------|----------|---------| +| | BTS | BSC/MSC | +| TERRESTRIAL CHANNEL MANAGEMENT | | | +| MSC-BSC channels | | | +| Channel allocation | | X | +| Blocking indication | | X | +| BSC-BTS channels | | | +| Channel allocation | | X | +| Blocking indication | X | | +| RADIO CHANNEL MANAGEMENT | | | +| Channel configuration management | | X | +| Frequency Hopping | | | +| Management | | X | +| Execution | X | | +| TCH management | | | +| Channel allocation (choice) | | X | +| Link supervision | | X | +| Channel release | | X | +| Idle channel observation | X | | +| Power control determination (note 3) | X | X | +| SDCCH management (Stand alone DCCH) | | | +| SDCCH allocation | | X | +| Link supervision | | X | +| Channel release | | X | +| Power control determination (note 3) | X | X | +| BCCH/CCCH management | | | +| Scheduling of messages | | | +| Management | | X | +| Execution | X | | +| Random access | | | +| Access detection | X | | +| Immediate assign (access grant) | | X | +| Channel coding/decoding | X | | +| Transcoding/rate adaption (note 1) | X | | +| Measurements | | | +| Uplink measuring (note 2) | X | | +| Processing of reports from MS/TRX (note 4) | X | X | +| Traffic measurements | | X | +| Timing advance | | | +| Calculation | X | | +| Signalling to MS at random access | | X | +| Signalling to MS at handover | X | | +| Signalling to MS during call | X | | +| Radio resource indication | | | +| Report status of idle channels | X | | +| LAPDm functions (Layer 2) | X | | +| Encryption | | | +| Management | | X | +| Execution (Key from BSC) | X | | + +| FUNCTION | Location | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------| +| | BTS | BSC/MSC | +| Paging | | | +| Initiation | | X | +| DRX paging | | | +| Management | | X | +| Execution | X | | +| Handover | | | +| BSC internal, one cell | | X | +| BSC internal, between cells | | X | +| BSC external | | | +| recognition, radio reason | | X | +| recognition, traffic reason | | X | +| decision | | X | +| execution | | X | +| Handover access detection | X | | +| MOBILITY MANAGEMENT | | | +| Authentication | | X | +| Location updating | | X | +| CALL CONTROL | | X | +| NOTE 1: Although the transcoder is always controlled by the BTS, it can optionally be located outside the BTS (e.g. at the BSC or at the MSC site). In that case, remote control is performed by BTS using inchannel signalling. | | | +| NOTE 2: Including averaging comparable to what is done in the MS. | | | +| NOTE 3: The support of power level determination in BTS is optional. | | | +| NOTE 4: The support of forwarding all raw measurement data from MS/TRX over the A-bis interface and the processing of it in BSC is mandatory. The BTS/BSC may additionally support also some pre- processing in BTS of this raw data. | | | + +# 6 Transcoding/rate adaption and multiplexing + +The interface supports two options: transcoding/rate adaption performed in BTS or outside BTS. + +## 6.1 Transcoding/rate adaption in BTS + +The transcoding of speech to normal 64 kbit/s A-law is performed within BTS. + +Data may be rate adapted or submultiplexed to 64 kbit/s circuits. + +## 6.2 Transcoding/rate adaption outside BTS + +In this case the transcoder/rate adaptor is considered as part of the BSC. + +The channel coding/decoding is performed by BTS/TRX. The choice of coding/interleaving has to be signalled from BSC to BTS. + +The remote speech transcoder has to have knowledge of some radio parameters for an efficient decoding. In addition, the timing of the transcoder has to be aligned with the transmission of the frames over radio such that the frames from BSC arrive synchronized with the transmission over radio (minimizes delay due to remote transcoder). For this control and time alignment of the transcoder, inband signalling is used within a 16 kbit/s or an 8 kbit/s channel carrying speech or data, signalling and synchronisation. This remote control of the transcoder is specified in Technical Specifications 3GPP TS 48.060 (full rate traffic channels, 16 kbit/s submultiplexing only) and 3GPP TS 48.061 (half rate traffic channels, 16 or 8 kbit/s submultiplexing). + +For data, rate adaption to subrate 16 or 8 kbit/s is performed within BTS. + +For the link BTS-BSC, the following possibilities are foreseen: + +- rate adaption of 16 kbit/s or 8 kbit/s speech + control or 16 kbit/s data + control to 64 kbit/s (one radio traffic channel per 64 kbit/s terrestrial channel); +- multiplexing of 16 kbit/s or 8 kbit/s speech + control or 16 kbit/s or 8 kbit/s data + control into one 64 kbit/s channel (up to eight radio traffic channels per 64 kbit/s terrestrial channel). + +# 7 Interface structures + +## 7.1 Communication channels + +The A-bis interface is considered to have two types of communication channels (see figure 7.1): + +- traffic channel (SDC) at 8 kbit/s, 16 kbit/s or 64 kbit/s carrying speech or data of one radio traffic channel (Bm or Lm channel); +- signalling channels (SCH) at 16 kbit/s, 32 kbit/s or 64 kbit/s, carrying signalling information (both BSC-MS and BSC-BTS signalling). + +![Diagram of communication channel types on the A-bis interface. The diagram shows a vertical stack of channels. On the left, labels 'B S C' are present. The main part is a dashed box containing two groups of channels. The top group is labeled 'SDCs' and 'Speech and Data' with a rate of '8, 16 or 64 kbit/s'. The bottom group is labeled 'SCHs' and 'Signalling' with a rate of '16, 32 or 64 kbit/s'. Above the box, labels 'B T S' are present.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +The diagram illustrates the communication channel types on the A-bis interface. It shows a vertical stack of channels. On the left, the labels 'B S C' are present. The main part is a dashed box containing two groups of channels. The top group is labeled 'SDCs' and 'Speech and Data' with a rate of '8, 16 or 64 kbit/s'. The bottom group is labeled 'SCHs' and 'Signalling' with a rate of '16, 32 or 64 kbit/s'. Above the box, the labels 'B T S' are present. + +Diagram of communication channel types on the A-bis interface. The diagram shows a vertical stack of channels. On the left, labels 'B S C' are present. The main part is a dashed box containing two groups of channels. The top group is labeled 'SDCs' and 'Speech and Data' with a rate of '8, 16 or 64 kbit/s'. The bottom group is labeled 'SCHs' and 'Signalling' with a rate of '16, 32 or 64 kbit/s'. Above the box, labels 'B T S' are present. + +**Figure 7.1: Communication Channel Types** + +## 7.2 Signalling links + +The addressing of TRXs and BCF is made using separate TEIs for each TRX and BCF. + +Three logical links are defined for each TEI: + +- RSL: Radio Signalling Link used for supporting traffic management procedures (MS to network communication). One link per TRX. +- OML: Operations and Maintenance Link used for supporting network management procedures (transferring operations and maintenance messages). One link per TRX and BCF. +- L2ML: Layer 2 Management Link used for transferring layer 2 management messages to TRX or BCF. One link per TRX and BCF. + +A logical diagram for the architecture of the signalling links is given in figure 7.2. + +Only point to point signalling links are used. + +SMS messages are also carried on the signalling links. + +![Figure 7.2: Logical L2 links of A-bis interface. The diagram shows the logical Layer 2 links between a BSC (Base Station Controller) and a BTS (Base Transceiver Station). The BSC side is divided into three main sections: LAYER 2, T E I, and MANAGEMENT. The BTS side contains multiple TRX (Transceiver) and BCF (Base Controller) units, each associated with a specific TEI (Traffic End Identifier) value: TEI1, TEI2, TEI3, and TEI4. The links are categorized into RSL (Radio Signalling Link), OML (Operation & Maintenance Link), and L2ML (Layer 2 Management Link). The diagram uses dashed lines to represent the logical connections between the BSC and the various TRX/BCF units in the BTS.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 7.2: Logical L2 links of A-bis interface. The diagram shows the logical Layer 2 links between a BSC (Base Station Controller) and a BTS (Base Transceiver Station). The BSC side is divided into three main sections: LAYER 2, T E I, and MANAGEMENT. The BTS side contains multiple TRX (Transceiver) and BCF (Base Controller) units, each associated with a specific TEI (Traffic End Identifier) value: TEI1, TEI2, TEI3, and TEI4. The links are categorized into RSL (Radio Signalling Link), OML (Operation & Maintenance Link), and L2ML (Layer 2 Management Link). The diagram uses dashed lines to represent the logical connections between the BSC and the various TRX/BCF units in the BTS. + +**Figure 7.2: Logical L2 links of A-bis interface** + +## 7.3 Signalling model + +A signalling model for the A-bis interface and its signalling environment can be found in figure 7.3. + +CM and MM messages are not interpreted by BSC or BTS. Over the A interface they are transferred using DTAP (Direct Transfer Application Part) and over the A-bis interface they are transferred as transparent messages. + +RR messages are mapped to BSSAP (BSS Application Part) in BSC. In BTS, most of them are handled as transparent messages. However, some of them have to be interpreted by BTS (e.g. random access, start ciphering, paging). The BTSM (BTS Management) entities contain procedures for handling these messages and also other procedures for managing the BTS as defined in Technical Specification 3GPP TS 48.058. In BTS there is a mapping between BTSM and the relevant RR messages over the radio interface (RR'). + +The Layer 2 protocol over the A-bis interface is based on LAPD. L2 addressing is made to TRX (or BCF) using the TEI of LAPD. Different L2 links are used for traffic management messages (RSL, Radio Signalling Link), network management messages (OML, Operation & Maintenance Link) and L2 management messages (L2ML, Layer 2 Management Link). + +A model of Layer 3 for the A-bis interface can be found in figure 7.4. + +For traffic management, two types of signalling messages have been defined: + +Transparent Messages: Messages which are forwarded by BTS without interpretation or changes. + +Non-Transparent Messages: Messages which are sent only between BSC and BTS and which BTS is acting upon or which are the results of BTS actions. + +In addition, the messages have been grouped into four main groups: Radio Link Layer Management, Dedicated Channel Management, Common Channel Management and TRX Management messages. + +Discrimination between these types and groups is based on the Message Discriminator which is sent as the first octet in all messages. Transparent and non-transparent messages are discriminated by a transparency flag (T-bit) in the Message Discriminator. Transparent messages are merely forwarded to L2 on the radio interface. + +In order to address the relevant radio channel, a Channel Number element is included to support the distribution of messages to relevant physical channels on the TRX. A Link Identifier element supports the distribution on logical links/channels on the radio interface (compare the DLCI element of the A interface, 3GPP TS 48.006). + +Error! No + +Error! No text of specified style in + +![Signalling model diagram for the A-bis interface showing layers for MS, BTS, BSC, and MSC. The diagram illustrates the protocol stack for each entity and the specific layers used on the A-bis interface between the BTS and BSC.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the signalling model for the A-bis interface and its environment. It shows the protocol stacks for the Mobile Station (MS), Base Transceiver Station (BTS), Base Station Controller (BSC), and Mobile Switching Center (MSC). + +**MS (Mobile Station) Stack:** + +- L3: CC, MM, RR +- L2: LAPDm +- L1: Sign. Layer 1 + +**BTS (Base Transceiver Station) Stack:** + +- RR' +- LAPDm +- Sign. Layer 1 + +**A-bis Interface (between BTS and BSC):** + +- BTSM (BTS Management) +- LAPD +- Sign. Layer 1 + +**BSC (Base Station Controller) Stack:** + +- RR +- BSSAP +- BTSM +- LAPD +- SCCP +- MTP +- Sign. Layer 1 + +**MSC (Mobile Switching Center) Stack:** + +- CM +- MM +- BSSAP +- SCCP +- MTP + +**Interfaces:** + +- Radio:** Interface between MS and BTS. (For the radio interface, see GSM 04.xx) +- A-bis:** Interface between BTS and BSC. (BTSM = BTS Management) +- A:** Interface between BSC and MSC. (For the A interface, see 3GPP TS 48.002) + +Signalling model diagram for the A-bis interface showing layers for MS, BTS, BSC, and MSC. The diagram illustrates the protocol stack for each entity and the specific layers used on the A-bis interface between the BTS and BSC. + +Figure 7.3: Signalling model for the A-bis interface and its signalling environment + +![Diagram of the L3 model showing protocol layers and components. At the top, 'Core processes within BS' connects to 'Traffic Management Procedures (GMM)' and 'Network Management Procedures (12.21)'. 'Traffic Management Procedures (GMM)' contains 'Transparent Messages' and 'Non Transparent Messages' leading to 'Distribution'. 'Distribution' connects to a hexagonal node 'O' at the L3 layer. 'Core processes within BS' also connects to 'Control Link distribution' which connects to 'Traffic interface'. 'Network Management Procedures (12.21)' connects to a hexagonal node 'G2' at the L2 layer. 'L2 Management Procedures' connects to a hexagonal node 'G3' at the L2 layer. Below the hexagonal nodes are 'RS', 'OM', and 'L2/L1' labels. Horizontal lines on the left indicate the L3 and L2 layers.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the L3 model architecture. At the top, a box labeled 'Core processes within BS' is connected to three main components: 'Control Link distribution', 'Traffic Management Procedures (GMM)', and 'Network Management Procedures (12.21)'. 'Control Link distribution' connects to 'Traffic interface'. 'Traffic Management Procedures (GMM)' contains two sub-boxes: 'Transparent Messages' and 'Non Transparent Messages', both leading to a 'Distribution' box. 'Distribution' connects to a hexagonal node 'O' at the L3 layer. 'Network Management Procedures (12.21)' connects to a hexagonal node 'G2' at the L2 layer. 'L2 Management Procedures' connects to a hexagonal node 'G3' at the L2 layer. Below the hexagonal nodes are labels 'RS', 'OM', and 'L2/L1'. Horizontal lines on the left indicate the L3 and L2 layers. + +Diagram of the L3 model showing protocol layers and components. At the top, 'Core processes within BS' connects to 'Traffic Management Procedures (GMM)' and 'Network Management Procedures (12.21)'. 'Traffic Management Procedures (GMM)' contains 'Transparent Messages' and 'Non Transparent Messages' leading to 'Distribution'. 'Distribution' connects to a hexagonal node 'O' at the L3 layer. 'Core processes within BS' also connects to 'Control Link distribution' which connects to 'Traffic interface'. 'Network Management Procedures (12.21)' connects to a hexagonal node 'G2' at the L2 layer. 'L2 Management Procedures' connects to a hexagonal node 'G3' at the L2 layer. Below the hexagonal nodes are 'RS', 'OM', and 'L2/L1' labels. Horizontal lines on the left indicate the L3 and L2 layers. + +Figure 7.4: L3 model + +# --- Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|----------|----|-----|-----------------------------------------|--------| +| January 2016 | - | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48054/raw.md b/marked/Rel-16/48_series/48054/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3cad4d1531fcb09d7f2881f24fac719e8cf866c7 --- /dev/null +++ b/marked/Rel-16/48_series/48054/raw.md @@ -0,0 +1,104 @@ + + + + + + +# Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 Abbreviations..... 5 + +4 Layer 1 specification..... 6 + +Annex A (informative): Change History..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The use and general aspects of the A-bis interface are given in 3GPP TS 48.051. + +The present document defines the structure of the physical layer (layer 1) of the BSC - BTS/TRX interface for supporting traffic channels and control channels. Use of the physical layer for supporting link protocol is covered in 3GPP TS 48.056. + +The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium. + +# --- 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 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [3] 3GPP TS 48.051: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; General aspects". +- [4] 3GPP TS 48.056: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification". +- [5] 3GPP TS 48.060: "In-band control of remote transcoders and rate adaptors for full rate traffic channels". +- [6] 3GPP TS 48.061: "In-band control of remote transcoders and rate adaptors for half rate traffic channels". +- [7] ITU-T Recommendation G.703: "Physical/electrical characteristics of hierarchical digital interfaces". +- [8] ITU-T Recommendation G.705: "Characteristics of plesiochronous digital hierarchy (PDH) equipment functional blocks". +- [9] ITU-T Recommendation G.711: "Pulse Code Modulation (PCM) of voice frequencies". +- [10] ITU-T Recommendation G.732: "Characteristics of primary PCM multiplex equipment operating at 2 048 kbit/s". +- [11] ITU-T Recommendation I.460: "Multiplexing, rate adaption and support of existing interfaces". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# 4 Layer 1 specification + +All the ITU-T recommendations referred to are Blue Book. + +Layer 1 shall utilize digital transmission at a rate of 2 048 kbit/s with a frame structure of 32 x 64 kbit/s time slots, as specified in ITU-T Recommendation G.705 clause 3 or at a rate of 64 kbit/s. + +The physical/electrical characteristics are defined in ITU-T Recommendation G.703. + +Synchronization at the BTS/TRX for the transmitted bit stream toward the BSC shall be derived from the received bit stream from the BSC. + +For transmission rate at 64 kbit/sec it shall be an interface as defined in ITU-T Recommendation G.703. + +For transmission rate at 2 048 kbit/s the functional characteristics are defined in ITU-T Recommendation G.732 clauses 2 and 3, and fault conditions should be treated in accordance with ITU-T Recommendation G.732 clause 4. + +The idle pattern must be transmitted on every timeslot that is not assigned to a channel, and to every timeslot of a channel that is not allocated to a call. The idle pattern shall be 01010100 for a 64 kbit/s channel and the 2-bit pattern 01 for 16 kbit/s channels. For 8 kbit/s channels, the idle pattern shall be consecutive ones or zeros according to the corresponding idle pattern bit of a 16 kbit/s channel. + +If transcoders are located in BTS speech encoding shall be the A-law as defined in ITU-T Recommendation G.711. + +If speech transcoders are located in the BSC the speech, data and signalling channels will utilize transmission rates of 8 kbit/s, 16 kbit/s or 64 kbit/s according to 3GPP TS 48.060 and 3GPP TS 48.061. They shall be rate adapted or multiplexed according to ITU-T Recommendation I.460 with fixed format, to fit into the physical interface. + +Data encoding is covered in 3GPP TS 48.020. + +In the case of a 2 048 kbit/sec circuit, multidrop solutions should be possible. Dynamic sharing of terrestrial 64 kbit/sec channels between BTS:s on a per-call basis must not be used. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|----------|----|-----|-----------------------------------------|--------| +| January 2016 | - | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48056/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/48_series/48056/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..553b05c3ad94f01b98ec1dbf6756b957e13dfe5d --- /dev/null +++ b/marked/Rel-16/48_series/48056/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ab563213277f5f2815effe35dbf46841ed38bd8cba8f7e94243c14195f21561 +size 30372 diff --git a/marked/Rel-16/48_series/48056/65550960f5c5afd9d27706aaeddb0638_img.jpg b/marked/Rel-16/48_series/48056/65550960f5c5afd9d27706aaeddb0638_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..878325e46e844bed5f622d9b6b9fb635fef59d41 --- /dev/null +++ b/marked/Rel-16/48_series/48056/65550960f5c5afd9d27706aaeddb0638_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ed15ddc8d984cb30814f0f09a7056fdbd151fba8b8adc1948cbe2b8b5b04b5a +size 23635 diff --git a/marked/Rel-16/48_series/48056/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg b/marked/Rel-16/48_series/48056/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..998c73089bbbe2b1d0c21bd968ca97cdf3e1d6de --- /dev/null +++ b/marked/Rel-16/48_series/48056/9c9a8f4d24e41870c2a264e5ae278fca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24380388e530ec2be977a846c4deb11caf4d7240a62b7dc37dd9764495d3db5b +size 70773 diff --git a/marked/Rel-16/48_series/48056/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/48_series/48056/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21f08f83080fa8b255e9e0e83d76667a7095bda3 --- /dev/null +++ b/marked/Rel-16/48_series/48056/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83ecc018776a95eda33a42503cc8e1d3a52516aaf5cd751110921b7b3813673c +size 16348 diff --git a/marked/Rel-16/48_series/48056/raw.md b/marked/Rel-16/48_series/48056/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ddeee98a1774bbfdb29b8f86b943ca4698b16267 --- /dev/null +++ b/marked/Rel-16/48_series/48056/raw.md @@ -0,0 +1,498 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 4 General description ..... | 6 | +| 5 Functional contents ..... | 7 | +| 6 LAPD functions ..... | 7 | +| 6.1 Exceptions and modifications ..... | 7 | +| 6.1.1 Void ..... | 7 | +| 6.1.2 Command/Response field bit (C/R) ..... | 7 | +| 6.1.3 Service Access Point Identifier (SAPI) ..... | 7 | +| 6.1.4 TEI for point-to-point data link connection..... | 8 | +| 6.1.5 Commands and responses..... | 8 | +| 6.1.6 Exchange identification (XID) command/response ..... | 8 | +| 6.1.7 MDL-XID ..... | 8 | +| 6.1.8 PH-DATA, PH DEACTIVATE and PH-ACTIVATE..... | 8 | +| 6.1.9 MPH-ACTIVATE, MPH-DEACTIVATE and MPH-INFORMATION..... | 8 | +| 6.1.10 Priority indicator..... | 9 | +| 6.1.11 Terminal Endpoint Identifier (TEI) management procedures ..... | 9 | +| 6.1.11.1 General..... | 9 | +| 6.1.11.2 TEI assignment procedure ..... | 9 | +| 6.1.11.3 TEI identity verify procedure ..... | 11 | +| 6.1.11.4 Formats and codes. .... | 11 | +| 6.1.12 Automatic negotiation of data link layer parameters..... | 11 | +| 6.1.13 Establishment procedures..... | 11 | +| 6.1.14 N(S) sequence error..... | 11 | +| 6.1.15 List of system parameters..... | 11 | +| 6.1.15.1 Timer T200 ..... | 12 | +| 6.1.15.2 Maximum number of retransmissions (N200)..... | 12 | +| 6.1.15.3 Maximum number of octets in an information field (N201) ..... | 12 | +| 6.1.15.4 Maximum number of transmission of the TEI identity request message (N202)..... | 12 | +| 6.1.15.5 Maximum number of outstanding frames (K) ..... | 12 | +| 6.1.15.6 Timer T201 ..... | 12 | +| 6.1.15.7 Timer T202 ..... | 12 | +| 6.1.15.8 Timer T203 ..... | 12 | +| 6.1.16 Data link layer monitor function ..... | 13 | +| 6.1.17 Miscellaneous ..... | 13 | +| Annex A (informative): Change History..... | 14 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the link layer used for signalling on the A-bis interface between BSC and BTS. The use and general aspects of the A-bis interface are described in 3GPP TS 48.051 and the interface aspects in 3GPP TS 48.052. + +The Link Access Procedure on the D-channel (LAPD) specification used on the A-bis interface in the GSM PLMN is a subset of the EN 300 125 which in turn has less options than the CCITT Recommendation Q.921. + +This description contains first the protocol definitions and second the services provided by the layer 2 to the layer 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 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 48.051: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; General aspects". +- [3] 3GPP TS 48.052: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Interface principles". +- [4] Void. +- [5] Void. +- [6] Void. +- [7] Void. +- [8] Void. +- [9] Void. +- [10] Void. +- [11] Void. +- [12] Void. +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. +- [18] Void. +- [19] CCITT Recommendation Q.921: "Integrated services digital network (ISDN) user-network interface - Data link layer specification". + +[20] EN 300 125: "Integrated Services Digital Network (ISDN); User-network interface data link layer specification Application of CCITT Recommendations Q.920/I.440 and Q.921/I.441". + +# 3 Definitions and abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905. + +# 4 General description + +The following information categories are supported by the procedures of this layer 2 Recommendation: + +- signalling (including Short Message Service (SMS) information); +- operation and maintenance; +- layer 2 management. + +For each of these categories the BSC may have one or more layer 2 links to every TRX and BCF. + +The signalling links over the A-bis interface are addressed to the different units by Terminal Endpoint Identifiers (TEI). + +The same unit will normally have more than one functional entity. The logical links between different functional entities are identified by functional addresses, the Service Access Points Identifier (SAPI). + +Figure 1 shows the architectural model with different layer 2 links. + +A number of logical links may be multiplexed on each physical link. The same layer 2 logical link may not be distributed over more than one physical link. + +![Diagram showing logical layer 2 links between Layer 2 entities and TRX/BCF units. It details RSL, OML, and L2ML links with their respective SAPI values (0, 62, 63) and TEI identifiers (1, 2, 3, 4, 65).](9c9a8f4d24e41870c2a264e5ae278fca_img.jpg) + +The diagram illustrates the logical Layer 2 links supported by three permanent and one semipermanent links. It shows connections between Layer 2 entities (TEI 1, 2, 3, 4, 65) and functional units (TRX 1, 2, 3, BCF). The links are categorized into RSL (Signalling), OML (Operation and Maintenance), and L2ML (Layer 2 Management), each with specific SAPI values. + +| Functional Unit | Link Type | SAPI | TEI | +|-----------------|-----------|------|-----| +| TRX 1 | RSL | 0 | 1 | +| | OML | 62 | | +| | L2ML | 63 | | +| TRX 2 | RSL | 0 | 2 | +| | OML | 62 | | +| | L2ML | 63 | | +| TRX 3 | RSL | 0 | 3 | +| | OML | 62 | | +| | L2ML | 63 | | +| BCF | OML | 62 | 4 | +| | L2ML | 63 | | +| [Unlabeled] | OML | 62 | 65 | +| | L2ML | 63 | | + +Diagram showing logical layer 2 links between Layer 2 entities and TRX/BCF units. It details RSL, OML, and L2ML links with their respective SAPI values (0, 62, 63) and TEI identifiers (1, 2, 3, 4, 65). + +Figure 4.1: An example of Logical Layer 2 links supported by three permanent and one semipermanent links + +# 5 Functional contents + +The basic functional content of the layer 2 protocol is: + +- transparent layer 2 links and time fill; +- point-to-point dedicated layer 2 links addressing both physical entities and functional entities; +- point-to-multipoint addressed links used for layer 2 management; +- basic functions for TEI assignment and management; +- basic priority functions; +- basic supervision of links when not carrying traffic; +- sequence control; +- transmission error control; +- control of errors not recoverable by retransmission. + +# 6 LAPD functions + +The LAPD functions as specified in EN 300 125 are applicable. However, the exceptions and modifications specified in the remainder of the present document shall be used. + +## 6.1 Exceptions and modifications + +In the following headlines from EN 300 125 are kept and references are made to the corresponding clause of EN 300 125. + +### 6.1.1 Void + +### 6.1.2 Command/Response field bit (C/R) + +(Refer to EN 300 125, part 2, clause 3.3.2) + +In GSM PLMN's BSC represents the network side and TRX/BCF the user side of the interface. + +### 6.1.3 Service Access Point Identifier (SAPI) + +(Refer to EN 300 125, part 2, clause 3.3.3) + +The SAPI values for the A-bis interface are as listed in table 6.1.3. + +**Table 6.1.3: Allocation of SAPI values and priority classes** + +| SAPI value | Related layer 3 or layer management entity | Priority | +|------------|----------------------------------------------------------------------------------------------------|----------| +| 0 | Radio signalling procedures | 2 | +| 1 | Reserved for packet mode communications using Q.931 call control procedures (Not used in GSM PLMN) | - | +| 16 | Reserved for packet communication conforming to X.25 level 3 procedures (Not used in GSM PLMN) | - | +| 62 | Operation and maintenance procedure | 1 | +| 63 | Layer 2 management procedures | 1 | +| All others | Reserved for future standardization | - | + +### 6.1.4 TEI for point-to-point data link connection + +(Refer to EN 300 125, part 2, clause 3.3.4.2). + +The remaining Terminal Endpoint Identifier (TEI) values are used for the point-to-point data link connections associated with the addressed Service Access Point (SAP). The range of TEI values shall be allocated as shown in table 6.1.4. + +**Table 6.1.4: Allocation of TEI values** + +| TEI value | User type | +|-----------|-----------------------------------------------------| +| 0-63 | TEI assignment for fixed TRX and BCF addresses | +| 64-126 | TEI assignment for additional, TRX or BCF addresses | + +NOTE: A BCF is given a separate layer 2 link only if it is not integrated with a TRX. + +### 6.1.5 Commands and responses + +(Refer to EN 300 125, part 2, clause 3.6.1) + +The XID command and response are not used. + +### 6.1.6 Exchange identification (XID) command/response + +(Refer to EN 300 125, part 2, clause 3.6.12) + +This functionality is not used. + +### 6.1.7 MDL-XID + +(Refer to EN 300 125, part 2, clause 4.1.1.9) + +This functionality is not used. + +### 6.1.8 PH-DATA, PH DEACTIVATE and PH-ACTIVATE + +(Refer to EN 300 125, part 2, clauses 4.1.1.10 - 4.1.1.12) + +This functionality is not relevant. + +### 6.1.9 MPH-ACTIVATE, MPH-DEACTIVATE and MPH-INFORMATION + +(Refer to EN 300 125, part 2, clauses 4.1.1.13 - 4.1.1.15) + +This functionality is not relevant. + +### 6.1.10 Priority indicator + +(Refer to EN 300 125, part 2, clause 4.1.3.1) + +The different SAPs are given the priority classes as listed in table 1 when contending (with priority one as the highest). + +### 6.1.11 Terminal Endpoint Identifier (TEI) management procedures + +(Refer to EN 300 125, part 2, clause 5.3) + +Due to the special assignment functions needed on the A-bis interface there are modifications and additions to the assignment procedures. The rest of clause 5.3 in EN 300 125, part 2, is kept if not stated otherwise. + +#### 6.1.11.1 General + +(Refer to EN 300 125, part 2, clause 5.3.1) + +TEI management for A-bis interface is based on the following procedural means: + +- a Subset of the TEI assignment procedures; +- the TEI check procedures; + +- the TEI remove procedures; +- an additional TEI assignment procedure. + +The TEI management needs procedures to check the used TEI values and procedures for reaction in situation where more than one TRX equipment uses the same TEI value. In addition to the fixed values it shall be possible to use additional TEI value to the same TRX equipment and thus increase the signalling capacity. + +#### 6.1.11.2 TEI assignment procedure + +(Refer to EN 300 125, part 2, clause 5.3.2) + +The TEI assignment procedure used on the A-bis interface has some additions to the automatic TEI assignment procedure specified in EN 300 125, part 2. + +To facilitate the configuration control in the BSC each TRX will have a fixed TEI and possibly get access to one or more additional TEIs assigning physical channels/layer 2 links. + +The layer 2 links may all be turned on and off according to the normal automatic TEI assignment scheme but the TRX may only request identified TEI values which is (semi-) permanently programmed or programmed by operation and maintenance messages. + +In GSM the reference number Ri is not used. It is only misoperation situations resulting from double failures that could be prevented/solved faster by this parameter. The marginal advantage is not supposed to motivate the application of a random generator and the checking procedure. + +The subset of the automatic assignment procedure applicable for the first layer 2 link to a TRX shall have the following modifications to EN 300 125, part 2: + +- the identity request shall have an Ai value in the range 0-63 identifying the TEI value which is requested for activation; +- on reception of the identity request message the BSC will check that the requested TEI may be used from the configurations aspects and then perform a normal TEI check procedure to prevent a double assignment; +- if the TEI request is accepted an identity assigned message with the requested TEI number is received by TRX before the expiry of timer T202; +- a successful assignment procedure is shown in figure 6.1.11.2.a. + +![Sequence diagram showing a successful TEI assignment procedure between a TRX and a BSC. The TRX sends an Identity request (Ai) to the BSC. The BSC responds with an Identity check request (Ai). The TRX then performs a 'Normal identity check procedure' and sends a 'No answer' message. Finally, the BSC sends an 'Identity assigned (Ai)' message to the TRX. Timers T202 and T201 are indicated on the TRX and BSC respectively, with 'V' markers at the bottom of their respective lifelines.](65550960f5c5afd9d27706aaeddb0638_img.jpg) + +``` + +sequenceDiagram + participant TRX + participant BSC + Note left of TRX: T202 + TRX->>BSC: Identity request (Ai) + BSC->>TRX: Identity check request (Ai) + Note right of BSC: T201 + Note right of BSC: Normal identity check procedure + TRX->>BSC: No answer + Note left of TRX: V + Note right of BSC: V + BSC->>TRX: Identity assigned (Ai) + +``` + +Sequence diagram showing a successful TEI assignment procedure between a TRX and a BSC. The TRX sends an Identity request (Ai) to the BSC. The BSC responds with an Identity check request (Ai). The TRX then performs a 'Normal identity check procedure' and sends a 'No answer' message. Finally, the BSC sends an 'Identity assigned (Ai)' message to the TRX. Timers T202 and T201 are indicated on the TRX and BSC respectively, with 'V' markers at the bottom of their respective lifelines. + +If timer T201 expires the request shall be repeated once and timer T201 restarted + +**Figure 6.1.11.2.a: A successful assignment procedure** + +If timer T202 expires the assignment procedure did not succeed, and the TRX will take further actions in accordance with the procedures as specified in EN 300 125, part 2. + +If within the assignment procedure an identity check response is received, then the requested TEI value is already in use. There shall be no answer to the requesting TRX and an error indication shall be sent to O&M. + +An example of a non-successful assignment procedure is shown in figure 6.1.11.2.b. + +![Sequence diagram for Figure 6.1.11.2.b showing an error case for TEI assignment. The diagram shows a TRX and a BSC. The TRX sends an Identity request (Ai) to the BSC. The BSC responds with an Identity check request (Ai). The TRX then sends an Identity check response (Ai). A timer T201 is shown on the BSC side, starting after the Identity check request and ending with a 'V' (expiry). A timer T202 is shown on the TRX side, starting after the Identity request and ending with a 'V' (expiry).](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant TRX + participant BSC + Note left of TRX: T202 + TRX->>BSC: Identity request (Ai) + BSC-->>TRX: Identity check request (Ai) + Note right of BSC: T201 + BSC-->>TRX: Identity check response (Ai) + Note left of TRX: V + +``` + +Sequence diagram for Figure 6.1.11.2.b showing an error case for TEI assignment. The diagram shows a TRX and a BSC. The TRX sends an Identity request (Ai) to the BSC. The BSC responds with an Identity check request (Ai). The TRX then sends an Identity check response (Ai). A timer T201 is shown on the BSC side, starting after the Identity check request and ending with a 'V' (expiry). A timer T202 is shown on the TRX side, starting after the Identity request and ending with a 'V' (expiry). + +If timer T201 expires the request shall be repeated once and timer T201 restarted + +**Figure 6.1.11.2.b: An example of assignment in error case (TEI value already in use)** + +The additional TEI assignment procedure is equivalent to the normal one with two exceptions: + +- the TEI value is in the range: 64-126; +- the TEI value and the identification of which physical link it shall operate on is transmitted to the TRX from BSC in an operation and maintenance message. This layer 3 O&M message is transferred on an already assigned layer 2 link. (See 12-series of GSM Technical Specifications). + +The successful additional assignment procedure is shown in figure 6.1.11.2.c. + +![Sequence diagram for Figure 6.1.11.2.c showing the successful procedure for assigning an additional TEI. The diagram shows a TRX and a BSC. The BSC sends an O&M command (Ai, physical address) to the TRX. The TRX responds with an Identity request (Ai). The BSC then sends an Identity check request (Ai). The TRX performs an Identity check procedure. If there is no response from the TRX side, a timer T201 on the BSC side expires. The TRX then sends an Identity assigned (Ai) message to the BSC.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +``` + +sequenceDiagram + participant TRX + participant BSC + Note left of TRX: T202 + BSC->>TRX: O&M command (Ai, physical address) + TRX-->>BSC: Identity request (Ai) + BSC-->>TRX: Identity check request (Ai) + Note right of BSC: T201 + TRX->>TRX: Identity check Procedure with no response from the TRX side + TRX-->>BSC: Identity assigned (Ai) + Note left of TRX: V + Note right of BSC: V + +``` + +Sequence diagram for Figure 6.1.11.2.c showing the successful procedure for assigning an additional TEI. The diagram shows a TRX and a BSC. The BSC sends an O&M command (Ai, physical address) to the TRX. The TRX responds with an Identity request (Ai). The BSC then sends an Identity check request (Ai). The TRX performs an Identity check procedure. If there is no response from the TRX side, a timer T201 on the BSC side expires. The TRX then sends an Identity assigned (Ai) message to the BSC. + +If timer T201 expires the request shall be repeated once and timer T201 restarted + +**Figure 6.1.11.2.c: The procedure for assigning an additional TEI to a TRX or BCF** + +#### 6.1.11.3 TEI identity verify procedure + +(Refer to EN 300 125, part 2, clause 5.3.5) + +This procedure is not used. + +#### 6.1.11.4 Formats and codes. + +(Refer to EN 300 125, part 2, clause 5.3.6) + +All messages except Identity verify and Identity denied are used. The Ai is used as described in clause 6.1.11.2, the modification to EN 300 125, part 2, clause 5.3.2. The Ri parameter is not used and will always be coded 0000 0000. + +The coding of each field of the various messages is specified in table 6.1.11.4.a. + +**Table 6.1.11.4.a: Codes for messages concerning TEI management procedures** + +| Message name | Layer management entity identifier | Reference number Ri | Message type | Action indicator Ai | +|-------------------------------------------|-------------------------------------------|----------------------------|---------------------|-----------------------------------------------------| +| Identity request (user to network) | 0000 1111 | Not used (code 0) | 0000 0001 | Ai = 0-126 | +| Identity assigned (network to user) | 0000 1111 | Not used (code 0) | 0000 0010 | Ai = 0-126
Assigned TEI value | +| Identity check request (network to user) | 0000 1111 | Not used (code 0) | 0000 0100 | Ai = 0-127
Check all TEI values | +| | | | | Ai = 0-126
TEI value to be checked | +| Identity check response (user to network) | 0000 1111 | Not used (code 0) | 0000 0101 | Ai = 0-126
TEI value in use | +| Identity remove (network to user) | 0000 1111 | Not used (code 0) | 0000 0110 | Ai = 0-127
Request for removal of all TEI values | +| | | | | Ai = 0-126
TEI value to be removed | + +### 6.1.12 Automatic negotiation of data link layer parameters + +(Refer to EN 300 125, part 2, clause 5.4 and annex IV) + +The procedures are not supported. + +### 6.1.13 Establishment procedures + +(Refer to EN 300 125, part 2, clause 5.5.1.2) + +The timer T203 shall be implemented in the equipment on both sides of interface A-bis. + +### 6.1.14 N(S) sequence error + +(Refer to EN 300 125, part 2, clause 5.8.1 and appendix I) + +As it is the case in EN 300 125, the optional procedure for retransmission as described in Appendix I is not supported. + +### 6.1.15 List of system parameters + +(Refer to EN 300 125, part 2, clause 5.9) + +All the default values are given in the following clauses. + +#### 6.1.15.1 Timer T200 + +(Refer to EN 300 125, part 2, clause 5.9.1) + +The default value of timer T200 is 240 ms starting from the end of a transmitted frame. + +**NOTE:** This timer depends on the timer values used for supervising the message flow between the Mobile Station (MS) and the network. The proper operation of the procedure requires timer T200 to be greater than the maximum time between transmission of command frames and the reception of their corresponding response or acknowledgement frames and shorter than the shortest layer 3 timer used for supervising this message flow. + +#### 6.1.15.2 Maximum number of retransmissions (N200) + +(Refer to EN 300 125, part 2, clause 5.9.2) + +The default value of (N200) is 3. + +#### 6.1.15.3 Maximum number of octets in an information field (N201) + +(Refer to EN 300 125, part 2, clause 5.9.3) + +The default and maximum value of (N201) is 260 octets for all SAPI values. + +#### 6.1.15.4 Maximum number of transmission of the TEI identity request message (N202) + +(Refer to EN 300 125, part 2, clause 5.9.4) + +Not used (i.e. equivalent to infinity). + +#### 6.1.15.5 Maximum number of outstanding frames (K) + +(Refer to EN 300 125, part 2, clause 5.9.5) + +For the SAPI value 0 identifying radio signalling the default (K) value shall be 2. For all other SAPIs the value shall be set to the fixed value of 1. + +NOTE: The value of K for SAPI value 0 shall always be greater than the k value for the other SAPIs. + +#### 6.1.15.6 Timer T201 + +(Refer to EN 300 125, part 2, clause 5.9.6) + +Timer T201 shall have the default value 1 second. + +#### 6.1.15.7 Timer T202 + +(Refer to EN 300 125, part 2, clause 5.9.7) + +The minimum time between the transmission of TEI Identity request messages is a system parameter (T202) which shall be set to 15 seconds. + +#### 6.1.15.8 Timer T203 + +(Refer to EN 300 125, part 2, clause 5.9.8) + +The timer T203 represents the maximum time allowed without frames being exchanged for each TEI. The value of timer T203 shall be 10 seconds. + +### 6.1.16 Data link layer monitor function + +(Refer to EN 300 125, part 2, clause 5.10) + +The supervisory function will be used in the equipment on both sides of the A-bis interface. + +### 6.1.17 Miscellaneous + +(Refer to EN 300 125, part 2, appendix I-IV) + +The functionalities specified in appendix I-IV of EN 300 125, part 2, is not used. + +# Annex A (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|--------------|----------|----|-----|-----------------------------------------|--------| +| January 2016 | - | - | - | Rel-13 version created based on v12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48058/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-16/48_series/48058/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb9e8aded205017dc4aabbf28098e7b2b2eb0a50 --- /dev/null +++ b/marked/Rel-16/48_series/48058/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3def6ff86f226e633158fc8e68a9032330f81d358e8f897ceaa3cbcb60ef899c +size 5638 diff --git a/marked/Rel-16/48_series/48058/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/48_series/48058/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c7e96387acf535c4e8fdf5671aa62e4dbb0670f --- /dev/null +++ b/marked/Rel-16/48_series/48058/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9eb01daa32c16587b3e8c5f45b52e88b9d6d1490bf100bb27fef68b919adb8e8 +size 42292 diff --git a/marked/Rel-16/48_series/48058/14515d82ffeec9475b9add3036ff26ab_img.jpg b/marked/Rel-16/48_series/48058/14515d82ffeec9475b9add3036ff26ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..278f6e73668ba00cc235336ffd0fd6353542853e --- /dev/null +++ b/marked/Rel-16/48_series/48058/14515d82ffeec9475b9add3036ff26ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a0935ab148cda1fcc48bccbbe1d5cfc13a7b4698dac1d7ef16604a9b522b4c5 +size 7299 diff --git a/marked/Rel-16/48_series/48058/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-16/48_series/48058/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a84d74655d01d4a90d60b50007c8538512058a3 --- /dev/null +++ b/marked/Rel-16/48_series/48058/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef7feb817f877bba7278c709edf05d27ffabee42f1fc22879ba763d73cb95e4c +size 19454 diff --git a/marked/Rel-16/48_series/48058/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/48_series/48058/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a4974fc092a83c6f3d39aecf79749f0fe0d5a26 --- /dev/null +++ b/marked/Rel-16/48_series/48058/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75cde6dca7d338c77f18e0b44d9b0c664ebbbaa12601d3bd1c734e5c0af77b63 +size 9648 diff --git a/marked/Rel-16/48_series/48058/1c140ee5d1a87186977da94a96bfa700_img.jpg b/marked/Rel-16/48_series/48058/1c140ee5d1a87186977da94a96bfa700_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f375845bcc547ddb9612de2804a627c2a2569d6b --- /dev/null +++ b/marked/Rel-16/48_series/48058/1c140ee5d1a87186977da94a96bfa700_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92b7b233ef45f61554b4105a41e044c132812c44a989e78294e1863f75903752 +size 5049 diff --git a/marked/Rel-16/48_series/48058/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/48_series/48058/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8213a3fb65977f2f85a38f63f52f694fbe075650 --- /dev/null +++ b/marked/Rel-16/48_series/48058/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c460ed2c31b420f2330fcb55687b1a513469bef48c37e3707a1e6872d7cc53f2 +size 5730 diff --git a/marked/Rel-16/48_series/48058/26ffdb652c290cd6aaa80c34a917e718_img.jpg b/marked/Rel-16/48_series/48058/26ffdb652c290cd6aaa80c34a917e718_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c728ea3ce8b2409d3fb54bf22fd802c50d05219c --- /dev/null +++ b/marked/Rel-16/48_series/48058/26ffdb652c290cd6aaa80c34a917e718_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95a04cb8dcafbb3e80179915772cf8f8165bafcb7fa90ef41cf7c8f538ab39b0 +size 4936 diff --git a/marked/Rel-16/48_series/48058/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/48_series/48058/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bfcfffa5b1b1ff53d0e2b7bc7239645ffdfafa0 --- /dev/null +++ b/marked/Rel-16/48_series/48058/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:973376c711893fbdf634e742f41629189c88bf21d672a1a835b4f93a120c0094 +size 9960 diff --git a/marked/Rel-16/48_series/48058/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/48_series/48058/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8b7c4671fa015e83417c5fa3db1a56be5e872c9 --- /dev/null +++ b/marked/Rel-16/48_series/48058/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5f11f909fd6ca7ac29b613d0953f732979eee4e621d8e2f5991141548b82951 +size 60809 diff --git a/marked/Rel-16/48_series/48058/298e7e2164a95d0d5bb8e5d1f7155094_img.jpg b/marked/Rel-16/48_series/48058/298e7e2164a95d0d5bb8e5d1f7155094_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b89622504303d06072125ab982dd2dacd2d8e9e --- /dev/null +++ b/marked/Rel-16/48_series/48058/298e7e2164a95d0d5bb8e5d1f7155094_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bce6839a1c62627bede76bde6ac24f05cd9563b98f86136ad16e2a645bde3fd +size 8776 diff --git a/marked/Rel-16/48_series/48058/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/48_series/48058/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..546f25240175ac4f1cc42411acd9f1eaa906adcb --- /dev/null +++ b/marked/Rel-16/48_series/48058/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41cb2c2e121f02c603a5c31ac3fa7acf647f7a0df22c95226c582fdc516920af +size 19065 diff --git a/marked/Rel-16/48_series/48058/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-16/48_series/48058/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bcd46fc7a637277f65c0d71bc0f65885d9f068e --- /dev/null +++ b/marked/Rel-16/48_series/48058/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b25f4755d3e0c404dc23e9a24b07281b000fcf8d208141d1aee040ec597f4cad +size 8394 diff --git a/marked/Rel-16/48_series/48058/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-16/48_series/48058/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ef24a1bc95b8007ca72e18f6e83b4e68387aea0 --- /dev/null +++ b/marked/Rel-16/48_series/48058/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:307e5cfccb7cc0a77894475563f9a30715ad7a182b87cc5f1f8e797a50adc6f1 +size 9123 diff --git a/marked/Rel-16/48_series/48058/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/marked/Rel-16/48_series/48058/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..192d23e66f708ed18433cad5672a063d4f29fc88 --- /dev/null +++ b/marked/Rel-16/48_series/48058/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63c92d528ec01704025fe959aa02c6c0fcfbbfb960c0c43c27d86d20144f3d26 +size 10680 diff --git a/marked/Rel-16/48_series/48058/414cf5c0e2959c558de57a9fb5c2134a_img.jpg b/marked/Rel-16/48_series/48058/414cf5c0e2959c558de57a9fb5c2134a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2634bb038dbf0900ea37a996d20636cb51cfad5a --- /dev/null +++ b/marked/Rel-16/48_series/48058/414cf5c0e2959c558de57a9fb5c2134a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:344df4d8160abdf11bc9562110183b2a61a6c780ebcfa947215701bc7c4df881 +size 6343 diff --git a/marked/Rel-16/48_series/48058/45578bd3ed11d45af63ce00e28bab2f8_img.jpg b/marked/Rel-16/48_series/48058/45578bd3ed11d45af63ce00e28bab2f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e431a594eca4da70e5fe73478d28fce2543ccca --- /dev/null +++ b/marked/Rel-16/48_series/48058/45578bd3ed11d45af63ce00e28bab2f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:992cbe9a9e297762abdcb8d0e9486442e605861bf0b9fefbb98756636f1e13f2 +size 16671 diff --git a/marked/Rel-16/48_series/48058/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/48_series/48058/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82687f4144cd876b4fd051969a44579709f1dd9d --- /dev/null +++ b/marked/Rel-16/48_series/48058/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0061b0b7a926425787f5919d241b851599891e19bc78dc30966669c3f778d8a2 +size 24679 diff --git a/marked/Rel-16/48_series/48058/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/marked/Rel-16/48_series/48058/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49528a87530cb6bdf40873422182a869275851fc --- /dev/null +++ b/marked/Rel-16/48_series/48058/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e88cf6a66b222ba74d711b9092bb96c9d0dcdab1b507de979d9744b01e910ba1 +size 13902 diff --git a/marked/Rel-16/48_series/48058/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-16/48_series/48058/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d36bd2b85e775e5248c8621b5ee8e9bacddbb55 --- /dev/null +++ b/marked/Rel-16/48_series/48058/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b6d938b8460676e2f5d59ad6d5b721c84a19e04f37f2912dccf4b2a2f5ba9fc +size 7413 diff --git a/marked/Rel-16/48_series/48058/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-16/48_series/48058/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ec4b365e0d5efc2bc60e43070012dba0ce89dea --- /dev/null +++ b/marked/Rel-16/48_series/48058/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f30031a7c483e269e244c74aa84b7d5e43a5a8ad6b48cc9bb99c3aafa7ad705 +size 8287 diff --git a/marked/Rel-16/48_series/48058/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/Rel-16/48_series/48058/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f60d4238769e88707cfbe073bd44d8fb9516c92 --- /dev/null +++ b/marked/Rel-16/48_series/48058/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99167e8b15237fcd2a9fac8b3cd4cbcd7a4da52263e785282d92353b78419adb +size 10660 diff --git a/marked/Rel-16/48_series/48058/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/48_series/48058/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ea7cdc075becf340e8fcf5e06a492d8d718a599 --- /dev/null +++ b/marked/Rel-16/48_series/48058/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e50329aa1671203fb9d8d1dbd4eb06d009ffcc3730ff01f8f5225b6b1b797c5 +size 15300 diff --git a/marked/Rel-16/48_series/48058/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/48_series/48058/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16f2ddd5560d0486edddda877d196de36749a0a3 --- /dev/null +++ b/marked/Rel-16/48_series/48058/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fb1ca49fe4e3f16b7c1ed3b70f18282b4b787751ee98332b18a20131ac5c8a0 +size 18493 diff --git a/marked/Rel-16/48_series/48058/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-16/48_series/48058/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaa3e9b5139f634e37b711b71f0b9d18e455efaa --- /dev/null +++ b/marked/Rel-16/48_series/48058/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5047f12808e54353ad9afb2aea4e0d19a9d2affce42ddc8f0613de2c170983e +size 8565 diff --git a/marked/Rel-16/48_series/48058/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-16/48_series/48058/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b95f6ff69f595865bfbf89e9595a8f760ab729 --- /dev/null +++ b/marked/Rel-16/48_series/48058/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d12f304057e7093c983ddeb7a3d5c6b7e9feb447e60ff748a801fd3607156690 +size 19946 diff --git a/marked/Rel-16/48_series/48058/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/48_series/48058/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4feee1c447c46a2c444422892ab4723ec1dc1bf3 --- /dev/null +++ b/marked/Rel-16/48_series/48058/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c56b6c4fb3fccfc0d5afefec5d06a53b44f68c0131563b49dfe2dd7e1a950909 +size 8496 diff --git a/marked/Rel-16/48_series/48058/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/48_series/48058/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..feb754fbb1bbc19fa99c81dfb77fadb699d5a3e2 --- /dev/null +++ b/marked/Rel-16/48_series/48058/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51eb47871583ed9735a560e4025865b46178fbd3251beea960f973725ad9bc2b +size 24380 diff --git a/marked/Rel-16/48_series/48058/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/48_series/48058/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f060a6d9959ad872c2c7ac52440c4a582ccd5c4 --- /dev/null +++ b/marked/Rel-16/48_series/48058/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e38407b32b3910b10e05725b1b2c171c2382e738ff32cf846303648ccaea50a3 +size 8598 diff --git a/marked/Rel-16/48_series/48058/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/48_series/48058/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8efbee8fb27216cf3a9bc010a4cb5cea2ca9dd3c --- /dev/null +++ b/marked/Rel-16/48_series/48058/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cf7a621ec50e5a187bbef5626bedef4cb086c0c7b71b058542b8ad809bb4b3b +size 9244 diff --git a/marked/Rel-16/48_series/48058/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-16/48_series/48058/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..776ceb1f4a8e1eab5194019b0456f6ab9cce16a8 --- /dev/null +++ b/marked/Rel-16/48_series/48058/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e26451a10997978ec216f31535235d263d9d81254c9fd72fdd88d1f95656d91 +size 5998 diff --git a/marked/Rel-16/48_series/48058/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/48_series/48058/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f6bcb4e06182451ac7055cb11aa67199d3f231a --- /dev/null +++ b/marked/Rel-16/48_series/48058/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e7c3dace83b677fdf41ce17fb0d04416709b23825d2bab83c08dd23996e595a +size 7285 diff --git a/marked/Rel-16/48_series/48058/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/Rel-16/48_series/48058/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a8463d4ac9d0333af6bf12937822385cb27945d --- /dev/null +++ b/marked/Rel-16/48_series/48058/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e2701efef22a89171beda688b99f292917237612830779f3aadafa96b51b290 +size 11133 diff --git a/marked/Rel-16/48_series/48058/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/48_series/48058/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baa3cc7cf030c3e774ad3d3482e1fc4a1a6295f2 --- /dev/null +++ b/marked/Rel-16/48_series/48058/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78e93fc5c2bf0e529efcfbfe3d0f4c35c2df88906fbdb5e497da88a8954bb767 +size 37259 diff --git a/marked/Rel-16/48_series/48058/8facb5a02c64e245808bafc005e65032_img.jpg b/marked/Rel-16/48_series/48058/8facb5a02c64e245808bafc005e65032_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5503275f5a641c7eaf87237fcf0fac18dcde589 --- /dev/null +++ b/marked/Rel-16/48_series/48058/8facb5a02c64e245808bafc005e65032_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6294b072056085276309d05fdb2be6289725d6ed062b911ccac67fda606ffda2 +size 14563 diff --git a/marked/Rel-16/48_series/48058/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-16/48_series/48058/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1513cc2a5acc827ac8f6329db4ef8b4950f073ea --- /dev/null +++ b/marked/Rel-16/48_series/48058/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8a5dc75e30dac58116b3bc8070125de0a099a30227cecd2a69473955313a93d +size 8970 diff --git a/marked/Rel-16/48_series/48058/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-16/48_series/48058/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..260f629f8dc1cd16ef9acb02162a83256544c629 --- /dev/null +++ b/marked/Rel-16/48_series/48058/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a6e57d0dffb52f2553d31f85a6dd3b08f331fd7b52d03e866e5123cc1564a3b +size 10948 diff --git a/marked/Rel-16/48_series/48058/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/Rel-16/48_series/48058/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2ea52ac2f80a9ed04a6d32d6b5fbb8dcc5db820 --- /dev/null +++ b/marked/Rel-16/48_series/48058/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9724e33ea25e881206d142c591068a3a73b18331a7b1e6e5910ceab1b663be56 +size 33772 diff --git a/marked/Rel-16/48_series/48058/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Rel-16/48_series/48058/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43769d865639d88a650fd5543d4e20b9016abe7b --- /dev/null +++ b/marked/Rel-16/48_series/48058/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55a267c51550bbde643581a894a62681a59b095321e135463695490e43f32b34 +size 40825 diff --git a/marked/Rel-16/48_series/48058/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/48_series/48058/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c8da5ebf2281f0748bdebf57bf91c34f0ac26ba --- /dev/null +++ b/marked/Rel-16/48_series/48058/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99bce20a9ab04bf907dcf7eb92494474d38e60a3ebbd82583367715c12b7cb29 +size 68063 diff --git a/marked/Rel-16/48_series/48058/9e1c95ee7eb045977f18f011f49520c7_img.jpg b/marked/Rel-16/48_series/48058/9e1c95ee7eb045977f18f011f49520c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8546b464d40232dffc58dc0ea9e9ae8a84aa802f --- /dev/null +++ b/marked/Rel-16/48_series/48058/9e1c95ee7eb045977f18f011f49520c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f749a45703007eac95f69f0ae34650aadc6f2de071b67cbf3b02857cc643457 +size 9617 diff --git a/marked/Rel-16/48_series/48058/aa9441a5971655a79987d70fc551b26a_img.jpg b/marked/Rel-16/48_series/48058/aa9441a5971655a79987d70fc551b26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..837b9c9640ae4fce44775527a23a54bda7987fb8 --- /dev/null +++ b/marked/Rel-16/48_series/48058/aa9441a5971655a79987d70fc551b26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83928898f32bf3ad04030df2738e55789a29f498a21692a125fcae51289f61b8 +size 5153 diff --git a/marked/Rel-16/48_series/48058/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/48_series/48058/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1156f408ecd86007992fe6a2950881d93194de17 --- /dev/null +++ b/marked/Rel-16/48_series/48058/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a495a52dd3fa77c03e09cae6839969ec660551aec0bd39430183655e8c20bcad +size 19715 diff --git a/marked/Rel-16/48_series/48058/b10763be31553f31cbb795653b731a43_img.jpg b/marked/Rel-16/48_series/48058/b10763be31553f31cbb795653b731a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..867c56eaf445a5e327b89b1e2a94deeac4e42c7c --- /dev/null +++ b/marked/Rel-16/48_series/48058/b10763be31553f31cbb795653b731a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66f92108c307965100f5116b72b8dce0b6d480d59e3e62a0c1edf03237ff5124 +size 7911 diff --git a/marked/Rel-16/48_series/48058/b7deb5c8e534f921026ab2447e0653b4_img.jpg b/marked/Rel-16/48_series/48058/b7deb5c8e534f921026ab2447e0653b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf9254dd64272e0a03875b87352e17bff80ae73e --- /dev/null +++ b/marked/Rel-16/48_series/48058/b7deb5c8e534f921026ab2447e0653b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2325d76e6a81545dde0cfb5f62fc64dfc4c47e21b0b9f23c43d80411c38387e +size 11886 diff --git a/marked/Rel-16/48_series/48058/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-16/48_series/48058/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b2c5f8fb7da1113a76ed7ff9f8e306bc5a4c1ab --- /dev/null +++ b/marked/Rel-16/48_series/48058/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:412ae738247538fd9fc87048ee7a62430fed5c2b827a8e0f8ab3c94ddbf4fd2c +size 13502 diff --git a/marked/Rel-16/48_series/48058/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-16/48_series/48058/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1b2379cadda5e5f24f9d3ad12339d2b975a404f --- /dev/null +++ b/marked/Rel-16/48_series/48058/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45441db737310a6b7001c39051dc112eb2c870e4e8e1f6dcbb4615f9c0715b7e +size 7897 diff --git a/marked/Rel-16/48_series/48058/c0e369274e53b2e5364666be6f786c7a_img.jpg b/marked/Rel-16/48_series/48058/c0e369274e53b2e5364666be6f786c7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cdd8ab02ac1bd8765ee71bc25039dc06fff67dd --- /dev/null +++ b/marked/Rel-16/48_series/48058/c0e369274e53b2e5364666be6f786c7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b505197142b3d8c7e9b0f3d3448ef75a8df1d162c1def77b4802bc840dd8660 +size 5691 diff --git a/marked/Rel-16/48_series/48058/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-16/48_series/48058/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..474df3678315db56292605520e27ef6b988d1923 --- /dev/null +++ b/marked/Rel-16/48_series/48058/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:224419e7693b8c3da23b5544debeeda1f213e3301beebe336ef59b7a791ea13c +size 7304 diff --git a/marked/Rel-16/48_series/48058/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/marked/Rel-16/48_series/48058/cad89c017c9e7c1785bcd104fde4e737_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a77e81896cc0e5de490359cc61bdeb81899b62d2 --- /dev/null +++ b/marked/Rel-16/48_series/48058/cad89c017c9e7c1785bcd104fde4e737_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a028117e9af6215d968c52acf7188efb739a45a1b727e5b023b29d875b99e759 +size 17445 diff --git a/marked/Rel-16/48_series/48058/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg b/marked/Rel-16/48_series/48058/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3d9e9f059d2205830d04a6c9fb3850b61d12202 --- /dev/null +++ b/marked/Rel-16/48_series/48058/cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb979469cc4a320641dae48a6a70001b288aa39a7df38297445cf909510f47a8 +size 8171 diff --git a/marked/Rel-16/48_series/48058/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/48_series/48058/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3dd0d4cf6b46d9bf20b6da797243d561c05c023d --- /dev/null +++ b/marked/Rel-16/48_series/48058/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6a0c469cc77436b15f08b3156e5d3bc451f603ae675bae817cb92fdb48957c6 +size 11171 diff --git a/marked/Rel-16/48_series/48058/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/48_series/48058/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..847fda03cd70b4b2cfeaedcdbeda39f335f8672b --- /dev/null +++ b/marked/Rel-16/48_series/48058/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae451e0522bfc60771dbe6c26b63390b4ce3df284a36f2a01b989a96c5929bd5 +size 15225 diff --git a/marked/Rel-16/48_series/48058/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/48_series/48058/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99c15eef50536c33afd4019789de0a934cad7330 --- /dev/null +++ b/marked/Rel-16/48_series/48058/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bec7a319450e568a4fe820523b12f46731ea2246857af19ed020fbdbbd86d6b +size 5146 diff --git a/marked/Rel-16/48_series/48058/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-16/48_series/48058/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4d459b1c7aecfdea003b8d39fd96d5d2a18e857 --- /dev/null +++ b/marked/Rel-16/48_series/48058/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:952150dabcb15783a344b8533215cd21d583802472c0c3b93cc7a876d9cb1ba5 +size 10609 diff --git a/marked/Rel-16/48_series/48058/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-16/48_series/48058/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7893fe4df5213ce32712e6bd0a2fb355ba2612d9 --- /dev/null +++ b/marked/Rel-16/48_series/48058/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56c62921d629f89d614cf6168bf8d2518ed5fab980502eeaf780ec1d4d925537 +size 7618 diff --git a/marked/Rel-16/48_series/48058/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/48_series/48058/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8225ddd03a44312dfa518fe81b1c772afd92a51e --- /dev/null +++ b/marked/Rel-16/48_series/48058/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e9d852c950f21ea1c4b1dafd3db5391c20b49dc3d82310868012c491ebc5a80 +size 76039 diff --git a/marked/Rel-16/48_series/48058/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/48_series/48058/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b970f7321c2d580cbd8736c5905cafe5739fd872 --- /dev/null +++ b/marked/Rel-16/48_series/48058/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac1adb8780b6dbdacf79dd33d898057cb406d8340cd554649886e48168350070 +size 4534 diff --git a/marked/Rel-16/48_series/48058/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg b/marked/Rel-16/48_series/48058/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b20949e3369fb28ef6809e8ef5e41d6c6e9001d5 --- /dev/null +++ b/marked/Rel-16/48_series/48058/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eabebe26ee534302617c1e8342de2ee0c394735913c0f3ee29a3a55cf5192e1a +size 11091 diff --git a/marked/Rel-16/48_series/48058/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/marked/Rel-16/48_series/48058/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42edf411a20106aed0cbaab7b604689eca912682 --- /dev/null +++ b/marked/Rel-16/48_series/48058/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ade28b795d65aecc6089f8af8bb502e80f1a3ad60202e6ef6cee6ea0ef484db9 +size 4962 diff --git a/marked/Rel-16/48_series/48058/f20786b603b41e24b5d5899f710b5947_img.jpg b/marked/Rel-16/48_series/48058/f20786b603b41e24b5d5899f710b5947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a777f240b0fa5536b7060a0f1b1a7730c0b5eeb --- /dev/null +++ b/marked/Rel-16/48_series/48058/f20786b603b41e24b5d5899f710b5947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ede9dbdfc144594ef703a9fdd4cd364229db259cfd85e0fcbc4e35e48c6d4cef +size 26878 diff --git a/marked/Rel-16/48_series/48058/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-16/48_series/48058/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b14d0c346b493de4b791cf02a00d42a92b317bcc --- /dev/null +++ b/marked/Rel-16/48_series/48058/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b223747cec07ec4312b9dcf73ed4b9c99911163d976eeb36ec197111ffb14f26 +size 9402 diff --git a/marked/Rel-16/48_series/48058/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/marked/Rel-16/48_series/48058/f64e1e0997695248c0cd4122c5b1a170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb5fe74a9805236c7a22a2fc702f63aeaa4e6523 --- /dev/null +++ b/marked/Rel-16/48_series/48058/f64e1e0997695248c0cd4122c5b1a170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f94a861ebe14256d3783d0fb4deb424713ca3fb0ce03fa7c370dd88a8cca8109 +size 5071 diff --git a/marked/Rel-16/48_series/48058/raw.md b/marked/Rel-16/48_series/48058/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5db93bdc417d61ef5f9e855ec834c94d33c128b2 --- /dev/null +++ b/marked/Rel-16/48_series/48058/raw.md @@ -0,0 +1,4516 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 1.1 References ..... | 8 | +| 1.2 Abbreviations ..... | 9 | +| 2 Protocol model ..... | 9 | +| 3 Radio Link Layer Management Procedures..... | 10 | +| 3.1 Link establishment indication ..... | 10 | +| 3.2 Link establishment request..... | 11 | +| 3.3 Link release indication ..... | 11 | +| 3.4 Link release request..... | 11 | +| 3.5 Transmission of a transparent L3-Message in acknowledged mode..... | 12 | +| 3.6 Reception of a transparent L3-Message in acknowledged mode..... | 12 | +| 3.7 Transmission of a transparent L3-Message in unacknowledged mode..... | 12 | +| 3.8 Reception of a transparent L3-Message in unacknowledged mode..... | 12 | +| 3.9 Link error indication..... | 13 | +| Dedicated channel management procedures ..... | 13 | +| 4.1 Channel activation..... | 13 | +| 4.1.1 Signalling Procedure ..... | 13 | +| 4.1.2 Activation for Intra-Cell Channel Change..... | 14 | +| 4.1.3 Activation for Asynchronous Handover..... | 15 | +| 4.1.4 Activation for Synchronous Handover ..... | 15 | +| 4.1.5 Activation for Secondary Channels in Multislot Configuration..... | 15 | +| 4.1.6 Channel reactivation..... | 15 | +| 4.2 Channel MODE MODIFY ..... | 16 | +| 4.3 Handover detection ..... | 16 | +| 4.4 Start of encryption..... | 17 | +| 4.5 Measurement reporting ..... | 17 | +| 4.5.1 Basic measurement reporting ..... | 18 | +| 4.5.2 Measurement pre-processing..... | 18 | +| 4.5.2.1 Pre-processing configuration ..... | 19 | +| 4.5.2.2 Pre-processed measurement reporting ..... | 19 | +| 4.5.3 Extended measurement reporting ..... | 19 | +| 4.6 Deactivate SACCH ..... | 20 | +| 4.7 Radio channel release..... | 20 | +| 4.8 MS power control..... | 20 | +| 4.9 Transmission power control..... | 21 | +| 4.10 Connection failure ..... | 22 | +| 4.11 Physical context request..... | 22 | +| 4.12 SACCH information modify ..... | 22 | +| 4.13 Talker detection..... | 23 | +| 4.14 Listener detection ..... | 23 | +| 4.15 Remote Codec Configuration..... | 23 | +| 4.16 Round Trip Delay Report..... | 23 | +| 4.17 Pre-handover Warning ..... | 24 | +| 4.18 MultiRate Codec Configuration Change..... | 24 | +| 4.19 MultiRate Codec Configuration Change Performed ..... | 25 | +| 4.20 TFO Report ..... | 25 | +| 4.21 TFO Modification Request..... | 25 | +| 5 Common channel management procedures ..... | 26 | +| 5.1 Channel request by MS ..... | 26 | +| 5.2 Paging..... | 26 | +| 5.3 Delete indication ..... | 26 | +| 5.4 CCCH load indication ..... | 27 | +| 5.5 Broadcast information modify ..... | 27 | +| 5.6 Short Message Cell Broadcast..... | 27 | + +| | | | +|--------|------------------------------------------------------------|----| +| 5.7 | IMMEDIATE ASSIGNMENT ..... | 30 | +| 5.8 | Notification..... | 31 | +| 6 | TRX management procedures..... | 31 | +| 6.1 | Radio resource indication..... | 31 | +| 6.2 | SACCH filling information modify ..... | 32 | +| 6.3 | Flow control ..... | 32 | +| 6.4 | Error reporting..... | 33 | +| 6a | Location services procedures ..... | 33 | +| 6a.1 | LLP message transport..... | 33 | +| 7 | Error handling ..... | 34 | +| 7.1 | General ..... | 34 | +| 7.2 | Message discriminator error..... | 34 | +| 7.3 | Message type error ..... | 34 | +| 7.4 | Message sequence error ..... | 34 | +| 7.5 | General information element errors ..... | 34 | +| 7.6 | Mandatory information element errors ..... | 34 | +| 7.7 | Optional information element errors ..... | 35 | +| 7.8 | Conditional information element errors ..... | 35 | +| 8 | Message formats and contents ..... | 35 | +| 8.0 | General ..... | 35 | +| 8.1 | Transparent messages..... | 36 | +| 8.2 | Non-transparent messages (BSC-BTS specific messages) ..... | 36 | +| 8.3 | Radio link layer management messages..... | 36 | +| 8.3.1 | DATA REQUEST ..... | 37 | +| 8.3.2 | DATA INDICATION ..... | 37 | +| 8.3.3 | ERROR INDICATION ..... | 37 | +| 8.3.4 | ESTABLISH REQUEST..... | 37 | +| 8.3.5 | ESTABLISH CONFIRM ..... | 38 | +| 8.3.6 | ESTABLISH INDICATION ..... | 38 | +| 8.3.7 | RELEASE REQUEST..... | 38 | +| 8.3.8 | RELEASE CONFIRM ..... | 38 | +| 8.3.9 | RELEASE INDICATION ..... | 39 | +| 8.3.10 | UNIT DATA REQUEST ..... | 39 | +| 8.3.11 | UNIT DATA INDICATION..... | 39 | +| 8.4 | DEDICATED CHANNEL MANAGEMENT MESSAGES ..... | 39 | +| 8.4.1 | CHANNEL ACTIVATION ..... | 40 | +| 8.4.2 | CHANNEL ACTIVATION ACKNOWLEDGE ..... | 41 | +| 8.4.3 | CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE ..... | 41 | +| 8.4.4 | CONNECTION FAILURE INDICATION..... | 42 | +| 8.4.5 | DEACTIVATE SACCH ..... | 42 | +| 8.4.6 | ENCRYPTION COMMAND ..... | 42 | +| 8.4.7 | HANDOVER DETECTION ..... | 42 | +| 8.4.8 | MEASUREMENT RESULT..... | 42 | +| 8.4.9 | MODE MODIFY..... | 43 | +| 8.4.10 | MODE MODIFY ACKNOWLEDGE ..... | 43 | +| 8.4.11 | MODE MODIFY NEGATIVE ACKNOWLEDGE ..... | 44 | +| 8.4.12 | PHYSICAL CONTEXT REQUEST..... | 44 | +| 8.4.13 | PHYSICAL CONTEXT CONFIRM..... | 44 | +| 8.4.14 | RF CHANNEL RELEASE..... | 44 | +| 8.4.15 | MS POWER CONTROL ..... | 44 | +| 8.4.16 | BS POWER CONTROL ..... | 45 | +| 8.4.17 | PREPROCESS CONFIGURE..... | 45 | +| 8.4.18 | PREPROCESSED MEASUREMENT RESULT..... | 45 | +| 8.4.19 | RF CHANNEL RELEASE ACKNOWLEDGE ..... | 45 | +| 8.4.20 | SACCH INFO MODIFY..... | 45 | +| 8.4.21 | TALKER DETECTION..... | 46 | +| 8.4.22 | LISTENER DETECTION..... | 46 | +| 8.4.23 | REMOTE CODEC CONFIGURATION REPORT ..... | 46 | +| 8.4.24 | ROUND TRIP DELAY REPORT ..... | 47 | + +| | | | +|--------|--------------------------------------------------------|----| +| 8.4.25 | PRE-HANDOVER NOTIFICATION..... | 47 | +| 8.4.26 | MULTRATE CODEC MODIFICATION REQUEST ..... | 47 | +| 8.4.27 | MULTRATE CODEC MODIFICATION ACKNOWLEDGE ..... | 47 | +| 8.4.28 | MULTRATE CODEC MODIFICATION NEGATIVE ACKNOWLEDGE ..... | 47 | +| 8.4.29 | MULTRATE CODEC MODIFICATION PERFORMED ..... | 48 | +| 8.4.30 | TFO REPORT ..... | 48 | +| 8.4.31 | TFO MODIFICATION REQUEST ..... | 48 | +| 8.5 | COMMON CHANNEL MANAGEMENT MESSAGES..... | 48 | +| 8.5.1 | BCCH INFORMATION ..... | 49 | +| 8.5.2 | CCCH LOAD INDICATION..... | 49 | +| 8.5.3 | CHANNEL REQUIRED ..... | 50 | +| 8.5.4 | DELETE INDICATION ..... | 50 | +| 8.5.5 | PAGING COMMAND..... | 50 | +| 8.5.6 | IMMEDIATE ASSIGN COMMAND ..... | 50 | +| 8.5.7 | SMS BROADCAST REQUEST ..... | 51 | +| 8.5.8 | SMS BROADCAST COMMAND..... | 51 | +| 8.5.9 | CBCH LOAD INDICATION..... | 51 | +| 8.5.10 | NOTIFICATION COMMAND..... | 52 | +| 8.6 | TRX MANAGEMENT MESSAGES ..... | 52 | +| 8.6.1 | RF RESOURCE INDICATION..... | 52 | +| 8.6.2 | SACCH FILLING ..... | 53 | +| 8.6.3 | OVERLOAD ..... | 53 | +| 8.6.4 | ERROR REPORT ..... | 53 | +| 8.7 | LOCATION SERVICES MESSAGES..... | 54 | +| 8.7.1 | LOCATION INFORMATION..... | 54 | +| 9 | Information element codings ..... | 54 | +| 9.1 | Message discriminator..... | 54 | +| 9.2 | MESSAGE TYPE ..... | 55 | +| 9.3 | Other information elements..... | 56 | +| 9.3.1 | Channel Number..... | 57 | +| 9.3.2 | Link Identifier ..... | 58 | +| 9.3.3 | Activation Type ..... | 58 | +| 9.3.4 | BS Power ..... | 59 | +| 9.3.5 | Channel Identification ..... | 60 | +| 9.3.6 | Channel Mode ..... | 60 | +| 9.3.7 | Encryption information ..... | 62 | +| 9.3.8 | Frame Number..... | 62 | +| 9.3.9 | Handover reference..... | 63 | +| 9.3.10 | L1 Information..... | 63 | +| 9.3.11 | L3 Information (message name)..... | 63 | +| 9.3.12 | MS Identity ..... | 63 | +| 9.3.13 | MS Power ..... | 63 | +| 9.3.14 | Paging Group ..... | 64 | +| 9.3.15 | Paging Load..... | 64 | +| 9.3.16 | Physical Context..... | 64 | +| 9.3.17 | Access Delay ..... | 65 | +| 9.3.18 | RACH Load..... | 65 | +| 9.3.19 | Request Reference ..... | 65 | +| 9.3.20 | Release Mode ..... | 66 | +| 9.3.21 | Resource Information ..... | 66 | +| 9.3.22 | RLM Cause..... | 66 | +| 9.3.23 | Starting Time ..... | 67 | +| 9.3.24 | Timing Advance ..... | 67 | +| 9.3.25 | Uplink Measurements..... | 67 | +| 9.3.26 | Cause ..... | 68 | +| 9.3.27 | Measurement result number ..... | 71 | +| 9.3.28 | Message Identifier ..... | 71 | +| 9.3.29 | SACCH Information..... | 71 | +| 9.3.30 | System Info Type ..... | 72 | +| 9.3.31 | MS Power Parameters ..... | 73 | +| 9.3.32 | BS Power Parameters ..... | 73 | + +| | | | +|------------------------|-------------------------------------------|----| +| 9.3.33 | Pre-processing Parameters..... | 74 | +| 9.3.34 | Pre-processed Measurements ..... | 74 | +| 9.3.35 | Full Immediate Assign Info ..... | 74 | +| 9.3.36 | SMSCB Information..... | 75 | +| 9.3.37 | MS Timing Offset..... | 75 | +| 9.3.38 | Erroneous Message..... | 75 | +| 9.3.39 | Full BCCH Information (message name)..... | 75 | +| 9.3.40 | Channel Needed..... | 76 | +| 9.3.41 | CB Command type ..... | 76 | +| 9.3.42 | SMSCB Message..... | 77 | +| 9.3.43 | CBCH Load Information..... | 77 | +| 9.3.44 | SMSCB Channel Indicator ..... | 77 | +| 9.3.45 | Group call reference ..... | 78 | +| 9.3.46 | Channel description ..... | 78 | +| 9.3.47 | NCH DRX information ..... | 78 | +| 9.3.48 | Command indicator ..... | 78 | +| 9.3.49 | eMLPP Priority..... | 79 | +| 9.3.50 | UIC ..... | 79 | +| 9.3.51 | Main channel reference ..... | 79 | +| 9.3.52 | MultiRate configuration ..... | 80 | +| 9.3.53 | MultiRate Control..... | 80 | +| 9.3.54 | Supported Codec Types..... | 80 | +| 9.3.55 | Codec Configuration ..... | 82 | +| 9.3.56 | Round Trip Delay ..... | 83 | +| 9.3.57 | TFO Status..... | 83 | +| 9.3.58 | LLP APDU ..... | 84 | +| 9.3.59 | TFO transparent container..... | 84 | +| 9.3.60 | DRX Info ..... | 84 | +| Annex A (informative): | Change History..... | 85 | + +# --- 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 general structure of layer 3 and traffic management procedures and messages used on the A-bis interface to support signalling procedures as defined in 3GPP TS 24.008 and 3GPP TS 44.018. Support for Location Services (LCS) related signalling, as defined in 3GPP TS 23.071, is also included. 3GPP TS 23.071 identifies new A-bis signalling to support BTS-embedded Type B LMUs as well as standalone, Type B LMUs. The standalone Type B LMU supports the layer 1 and 2 signalling for the A-bis as well as the Location Service message defined in the present document. + +The use and general aspects of the Base Station Controller (BSC) to Base Station Transceiver (BTS) interface (the A-bis interface) are given in 3GPP TS 48.051. + +Network management procedures and messages for the A-bis interface are defined in 3GPP TS 08.59. + +The functional split between BSC and BTS is defined in 3GPP TS 48.052. The procedures and messages required to support this split are defined in detail in 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 43.020: "Security related network functions". +- [2a] 3GPP TS 23.071: "Location Services; Functional description – Stage 2". +- [3] 3GPP TS 44.004: "Layer 1 General requirements". +- [4] 3GPP TS 44.005: "Data Link (DL) layer General aspects". +- [5] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". +- [6] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3". +- [7] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". +- [7a] 3GPP TS 44.071: "Mobile radio interface layer 3 Location Services (LCS) specification". +- [8] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [9] 3GPP TS 45.005: "Radio transmission and reception". +- [10] 3GPP TS 45.008: "Radio subsystem link control". +- [11] 3GPP TS 45.009: "Link Adaptation". +- [12] 3GPP TS 45.010: "Radio subsystem synchronization". +- [13] 3GPP TS 48.006: "Signaling transport specification mechanism for the Base Station System – Mobile-services Switching Centre (BSS - MSC) interface". + +- [14] 3GPP TS 48.008: "Mobile-services Switching Centre – Base Station System (MSC-BSS) interface; Layer 3 specification". +- [15] 3GPP TS 48.051: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; General aspects". +- [16] 3GPP TS 48.052: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Interface principles". +- [17] 3GPP TS 48.056: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification". +- [18] 3GPP TS 26.103: "Speech Codec List for GSM and UMTS". +- [19] 3GPP TS 44.018: "Radio Resource Control Protocol". + +## 1.2 Abbreviations + +For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 apply. + +# --- 2 Protocol model + +A model for L3 can be found in figure 2.1. + +L2 addressing is made to TRX (or BCF) using the TEI of LAPD. Different L2 links are used for traffic management messages (RSL, Radio Signalling Link), network management messages (OML, Operation & Maintenance Link) and L2 management messages (L2ML, Layer 2 Management Link). + +For traffic management, two types of signalling messages have been defined: + +**Transparent Messages:** Messages which are forwarded by BTS without interpretation or changes. + +**Non-Transparent Messages:** Messages which are sent only between BSC and BTS and which BTS is acting upon or which are the results of BTS actions. + +In addition, the messages have been grouped into four main groups: Radio Link Layer Management, Dedicated Channel Management, Common Channel Management and TRX Management messages. + +Discrimination between these types and groups is based on the Message Discriminator which is sent as the first octet in all messages. Transparent and non-transparent messages are discriminated by a transparency flag (T-bit) in the Message Discriminator. Transparent messages are merely forwarded to L2 on the radio interface. + +In order to address the relevant radio channel, a Channel Number element is included to support the distribution of messages to relevant physical channels on the TRX. A Link Identifier element supports the distribution on logical links/channels on the radio interface (compare the DLCI element of the A interface, 3GPP TS 48.006). + +All messages in this GTS are to be transmitted on the A-bis interface using the I format of LAPD, except for MEASUREMENT RESULT which is sent in UI format. + +![Figure 2.1/48.058: L3 model diagram showing the internal structure of a BTS and its interfaces to the radio and BSC.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the L3 model within a BTS. At the top, 'Other processes within BTS' are shown. Below them, 'Chan No Link distribution' connects to the 'To radio interface'. The central 'Traffic Management Procedures (08.58)' block contains 'Transparent Messages' and 'Non-Transparent Messages', which both feed into a 'Distribution' block. This 'Distribution' block connects to a hexagonal node labeled '0', which is associated with the 'RSL' (Radio Signalling Link). To the right, 'Network Management Procedures (12.21)' connect to a hexagonal node labeled '62', associated with the 'OML' (Operation and Maintenance Link). Further right, 'L2 Management Procedures' connect to a hexagonal node labeled '63', associated with the 'L2ML' (Layer 2 Management Link). The nodes '0', '62', and '63' are horizontally interconnected. On the left, dashed lines indicate the 'L3' and 'L2' layers. + +Figure 2.1/48.058: L3 model diagram showing the internal structure of a BTS and its interfaces to the radio and BSC. + +Figure 2.1/48.058: L3 model + +# 3 Radio Link Layer Management Procedures + +This sub-clause describes procedures related to the management of a link layer connection on the radio path. + +## 3.1 Link establishment indication + +This procedure is used by BTS to indicate to BSC that a layer 2 link on the radio path has been established in multi-frame mode at the initiative of an MS. BSC can use this indication to set up an SCCP connection to MSC. + +Upon reception of a SABM frame on a link on an active channel, the BTS sends an ESTablish INDication message to BSC. The message contains the contents of the information field of the SABM frame if present. + +The procedure is used in all establishment cases, for all channels and all SAPIs. + +![Sequence diagram for Link establishment indication showing MS sending a first SABM to BTS, and BTS sending an EST IND to BSC.](b10763be31553f31cbb795653b731a43_img.jpg) + +The sequence diagram shows three entities: MS, BTS, and BSC. A dashed arrow labeled 'first SABM' points from the MS to the BTS. A solid arrow labeled 'EST IND' points from the BTS to the BSC. + +Sequence diagram for Link establishment indication showing MS sending a first SABM to BTS, and BTS sending an EST IND to BSC. + +## 3.2 Link establishment request + +This procedure is used by BSC to request the establishment of a link layer connection in multi-frame mode on the radio path. + +The procedure is started by BSC sending an ESTablish REQuest message to BTS. BTS then establishes the link by sending a SABM frame. Upon reception of the acknowledgement (UA-frame) from MS, BTS sends an ESTablish CONFirm message to BSC. + +In case of a failure, BTS sends a RELease INDication and an ERRor INDication message to BSC (cf. 3GPP TS 44.006). + +![Sequence diagram for link establishment between MS, BTS, and BSC.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of MS: SABM + BSC->>BTS: EST REQ + Note left of MS: UA + BTS->>BSC: EST CONF + Note left of MS: - - - - -> + +``` + +Sequence diagram for link establishment between MS, BTS, and BSC. + +## 3.3 Link release indication + +This procedure is used by BTS to indicate to BSC that a link layer connection on the radio path has been released at the initiative of an MS. + +When receiving a DISC frame on a link layer connection in multi-frame mode, BTS sends a RELease INDication message to BSC. (If the link layer is in idle mode, BTS will send a DM frame to MS but does not notify BSC.) + +Collision cases are treated as specified in 3GPP TS 44.006. + +![Sequence diagram for link release indication from MS to BSC via BTS.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of MS: first DISC + MS->>BTS: first DISC + Note left of MS: UA + BTS->>BSC: REL IND + Note left of MS: - - - - -> + +``` + +Sequence diagram for link release indication from MS to BSC via BTS. + +## 3.4 Link release request + +This procedure is used by BSC to request the release of a link layer connection on the radio path. + +The procedure is started by BSC sending a RELease REQuest message to BTS. BTS then sends a DISC frame to MS. When it has received the acknowledgement (UA or DM frame), BTS sends a RELease CONFirm message to BSC. + +Collision cases are treated as specified in 3GPP TS 44.006. + +If BTS has repeated the DISC frame N200 times, BTS sends a RELease INDication and an ERRor INDication message to BSC (cf. 3GPP TS 44.006). + +![Sequence diagram for link release request from BSC to MS via BTS.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + BSC->>BTS: REL REQ + Note left of MS: DISC + BTS->>MS: DISC + Note left of MS: UA (or DM) + BTS->>BSC: REL CONF + Note left of MS: - - - - -> + +``` + +Sequence diagram for link release request from BSC to MS via BTS. + +## 3.5 Transmission of a transparent L3-Message in acknowledged mode + +This procedure is used by BSC to request the sending of a L3 message to MS in acknowledged mode. + +BSC sends a DATA REQuest message to BTS. The message contains the complete L3 message to be sent in acknowledged mode. + +![Sequence diagram for Section 3.5: Transmission of a transparent L3-Message in acknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. A 'DATA REQ' message is sent from BSC to BTS. Between MS and BTS, there are two dashed horizontal arrows: the top one is labeled 'I-frames' and points from BTS to MS, and the bottom one is labeled 'RR-frames' and points from MS to BTS.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Sequence diagram for Section 3.5: Transmission of a transparent L3-Message in acknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. A 'DATA REQ' message is sent from BSC to BTS. Between MS and BTS, there are two dashed horizontal arrows: the top one is labeled 'I-frames' and points from BTS to MS, and the bottom one is labeled 'RR-frames' and points from MS to BTS. + +## 3.6 Reception of a transparent L3-Message in acknowledged mode + +This procedure is used by BTS to indicate the reception of a L3 message in acknowledged mode. + +BTS sends a DATA INDication message to BSC. The message contains the received L3 message. + +![Sequence diagram for Section 3.6: Reception of a transparent L3-Message in acknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. Between MS and BTS, there are two dashed horizontal arrows: the top one is labeled 'I-frames' and points from MS to BTS, and the bottom one is labeled 'RR-frames' and points from BTS to MS. A 'DATA IND' message is sent from BTS to BSC.](853f59c89931a666c07903b31d098277_img.jpg) + +Sequence diagram for Section 3.6: Reception of a transparent L3-Message in acknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. Between MS and BTS, there are two dashed horizontal arrows: the top one is labeled 'I-frames' and points from MS to BTS, and the bottom one is labeled 'RR-frames' and points from BTS to MS. A 'DATA IND' message is sent from BTS to BSC. + +## 3.7 Transmission of a transparent L3-Message in unacknowledged mode + +This procedure is used by BSC to request the sending of a L3 message to MS in unacknowledged mode. + +BSC sends a UNIT DATA REQuest message to BTS. The message contains the L3 message to be sent to MS in unacknowledged mode. + +![Sequence diagram for Section 3.7: Transmission of a transparent L3-Message in unacknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. A 'UNIT DATA REQ' message is sent from BSC to BTS. Between MS and BTS, there is a dashed horizontal arrow labeled 'UI-frame' pointing from BTS to MS.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +Sequence diagram for Section 3.7: Transmission of a transparent L3-Message in unacknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. A 'UNIT DATA REQ' message is sent from BSC to BTS. Between MS and BTS, there is a dashed horizontal arrow labeled 'UI-frame' pointing from BTS to MS. + +## 3.8 Reception of a transparent L3-Message in unacknowledged mode + +This procedure is used by BTS to indicate the reception of a L3 message in unacknowledged mode. + +BTS sends a UNIT DATA INDication message to BSC. The message contains the received L3 message. + +![Sequence diagram for Section 3.8: Reception of a transparent L3-Message in unacknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. Between MS and BTS, there is a dashed horizontal arrow labeled 'UI-frame' pointing from MS to BTS. A 'UNIT DATA IND' message is sent from BTS to BSC.](cb8dd5eca74bbf15a81e37c23263c9a8_img.jpg) + +Sequence diagram for Section 3.8: Reception of a transparent L3-Message in unacknowledged mode. The diagram shows three vertical lifelines: MS, BTS, and BSC. Between MS and BTS, there is a dashed horizontal arrow labeled 'UI-frame' pointing from MS to BTS. A 'UNIT DATA IND' message is sent from BTS to BSC. + +## 3.9 Link error indication + +This procedure is used by BTS to indicate an abnormal case such as the following. + +- a protocol error as specified in 3GPP TS 44.006; +- a link layer failure, i.e. the repetition of an I-frame N200 times without an acknowledgement; +- the repetition of an SABM or DISC frame N200 times without an acknowledgement; +- the reception of an SABM frame in multi-frame established state. + +When such an event has occurred, BTS notifies BSC by sending an ERROR INDication message containing the relevant cause information. + +A BTS that supports enhanced power control (EPC) shall activate a channel in EPC mode if so ordered by the BSC in the CHANNEL ACTIVATION message. Further, it shall use enhanced power control procedures as defined in 3GPP TS 45.008 for MS (uplink) power control and/or BS (downlink) power control if so ordered by the BSC in the CHANNEL ACTIVATION message (or the BS POWER CONTROL or MS POWER CONTROL messages). + +![Sequence diagram showing an abnormal case where a BTS sends an ERROR IND message to a BSC. The MS is shown on the left, but the interaction is between the BTS and the BSC.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of BTS: abnormal case + BTS->>BSC: ERROR IND + +``` + +Sequence diagram showing an abnormal case where a BTS sends an ERROR IND message to a BSC. The MS is shown on the left, but the interaction is between the BTS and the BSC. + +# Dedicated channel management procedures + +## 4.1 Channel activation + +This procedure is used to activate a channel at the BTS for an MS which later will be commanded to this channel by an IMMEDIATE ASSIGN, an ASSIGN COMMAND, an ADDITIONAL ASSIGNMENT; a NOTIFICATION, a CHANNEL RELEASE (with a Channel description) a HANDOVER COMMAND or a CONFIGURATION CHANGE COMMAND message. + +In the handover case, the procedure is used between the target BSC and the target BTS to activate a channel for a subsequent handover from the old BTS. + +### 4.1.1 Signalling Procedure + +BSC determines what channel shall be used and starts up that channel at BTS by sending a CHANNEL ACTIVATION message to the relevant TRX. This message contains the reason for the activation (immediate assignment, assignment, asynchronous/synchronous handover, additional assignment, activation of a secondary channel in a multislot configuration), the identification of the channel to be used (channel no) and a complete description of the channel (full/half rate, speech/data, coding/rate adaption, hopping sequence, encryption key etc.). + +If the Encryption Information field is present, the activation is done with ciphering active. If the Encryption Information element is not present, activation is done without ciphering. + +After activating the channel as requested, TRX responds with the CHANNEL ACTIVATION ACKnowledge message. This message contains the current frame number at BTS. The frame number is used by BSC to determine the Starting Time parameter to be included in the following assignment message to MS. (A suitable number has to be added to current frame number to take all possible signalling delays into account). + +![Sequence diagram of the channel activation signalling procedure. The BSC sends a CHAN ACTIV message to the BTS. The BTS responds with a CHAN ACTIV ACK message. The BSC then sends an assignment message to the MS via the BTS. The assignment message can be an IMMEDIATE ASSIGN, ASSIGN COMMAND, ADDITIONAL ASSIGN, CHANNEL RELEASE, or NOTIFICATION.](f20786b603b41e24b5d5899f710b5947_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BSC: IMMEDIATE ASSIGN or +ASSIGN COMMAND or +ADDITIONAL ASSIGN or +CHANNEL RELEASE or +NOTIFICATION + BSC->>BTS: CHAN ACTIV + BTS-->>BSC: CHAN ACTIV ACK + BSC-->>MS: assignment to MS + +``` + +Sequence diagram of the channel activation signalling procedure. The BSC sends a CHAN ACTIV message to the BTS. The BTS responds with a CHAN ACTIV ACK message. The BSC then sends an assignment message to the MS via the BTS. The assignment message can be an IMMEDIATE ASSIGN, ASSIGN COMMAND, ADDITIONAL ASSIGN, CHANNEL RELEASE, or NOTIFICATION. + +If the TRX for some reason cannot activate the resource as requested by the CHANNEL Activation message, the TRX shall return a CHANNEL ACTIVATION Negative ACKnowledge message with the most appropriate cause value. + +Possible cause values may be: + +- O&M intervention (e.g. channel blocked); +- resource not available (e.g. speech coder, encryption device); +- equipment failure; +- channel already activated; + +- etc. + +![Sequence diagram showing CHAN ACTIV and CHAN ACTIV NACK messages between BTS and BSC.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note right of BSC: CHAN ACTIV + BSC->>BTS: CHAN ACTIV + Note left of BTS: CHAN ACTIV NACK + BTS-->>BSC: CHAN ACTIV NACK + +``` + +Sequence diagram showing CHAN ACTIV and CHAN ACTIV NACK messages between BTS and BSC. + +In the handover case, the procedure is initiated by the target BSC when this receives the HANDOver REQuest message from MSC (or autonomously by BSC for BSC internal handover). The BSC sends a CHANnel ACTIVation message to the relevant TRX. The message contains the Handover Reference value which can be used by the BTS to check the Handover Access from MS. After activation of the channel TRX responds with a CHANnel ACTIVation ACKnowledge message containing the current frame number at BTS. + +The BSC can then determine the Starting Time parameter to be included in the HANDOver REQuest ACKnowledge message to MSC (and the HANDOver CoMmanD message to MS). + +![Sequence diagram showing the handover activation procedure between BTS, BSC, and MSC.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + participant MSC + Note right of BSC: HANDO REQ + BSC-->>MSC: HANDO REQ + Note right of BSC: CHAN ACTIV + BSC->>BTS: CHAN ACTIV + Note left of BTS: CHAN ACTIV ACK + BTS-->>BSC: CHAN ACTIV ACK + Note right of BSC: HANDO REQ ACK + BSC-->>MSC: HANDO REQ ACK + Note right of BSC: or + Note right of BSC: HANDO CMD to MS + BSC-->>MSC: HANDO CMD to MS + +``` + +Sequence diagram showing the handover activation procedure between BTS, BSC, and MSC. + +### 4.1.2 Activation for Intra-Cell Channel Change + +This activation precedes the Immediate Assignment, Assignment or Additional assignment procedures. The Timing Advance element must be included in the CHANNEL ACTIVATION message. + +BTS activates the channel and starts transmission and reception on the main channel in the indicated mode. Ciphering is started if so indicated in the encryption information. + +The reception and transmission on SACCH is also started immediately. + +If the BS and/or MS power elements and/or the Physical Context element are present, the reception and transmission processes and the L1-header of SACCH are initialized accordingly. + +### 4.1.3 Activation for Asynchronous Handover + +BTS starts transmission immediately on the main channel in the indicated mode and with encryption if so indicated. If the MS Power element is present the BTS may start transmission also on the SACCH. + +When receiving a correct access burst with the correct handover reference, BTS starts the normal reception process on the main channel in the indicated mode and starts receiving (and sending if not started earlier) on SACCH. Deciphering is started if so indicated. The handover detection procedure towards BSC is also started. + +### 4.1.4 Activation for Synchronous Handover + +BTS starts transmission immediately on the main channel in the indicated mode and with encryption if so indicated. If the MS Power and Timing Advance element are present, BTS shall start transmission also on SACCH with the timing advance and MS power control parameters indicated. If only the MS power element is present the BTS may start transmission also on the SACCH. + +When receiving a correct access burst with the correct handover reference, BTS starts the normal reception process on the main channel in the indicated mode, with deciphering applied if so indicated, and starts receiving (and sending if not started earlier) on SACCH. The handover detection procedure towards BSC is also started. Alternatively, the reception + +of a correctly decoded frame from the MS on the main channel, in the indicated mode and deciphering applied if so indicated, allows the start of sending on SACCH (if not already started) and starts the handover detection procedure towards the BSC. + +NOTE: The activation for synchronous handover can be used for pseudo synchronized handover. + +### 4.1.5 Activation for Secondary Channels in Multislot Configuration + +BTS activates the channel and starts transmission and reception on the traffic and SACCH channels in the indicated mode. Ciphering is applied if so indicated in the encryption information. + +If the BS and/or MS power elements and/or the Physical Context element are present, the reception if applicable and transmission processes and the L1-header of SACCH are initialized accordingly. + +### 4.1.6 Channel reactivation + +This procedure is used by BSC to request a reactivation of an active channel. During the reactivation, information flows, e.g., user information such as speech or data, that are common for the two phases of operation, are not interrupted. + +BSC initiates the procedure by sending a CHANNEL ACTivation message to BTS where the activation type indicates "reactivation", the BTS shall reactivate the channel with the new parameters. After having successfully reactivate the channel with the parameters supplied the BTS responds with a CHANNEL ACTivation ACKnowledge message to BSC. + +![Sequence diagram for Channel reactivation](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note over MS: MS + BSC->>BTS: CHANNEL ACT + BTS->>BSC: CHANNEL ACT ACK + +``` + +Sequence diagram illustrating Channel reactivation. The diagram shows three participants: MS, BTS, and BSC. The MS is shown as a label above a vertical line. The BSC sends a CHANNEL ACT message to the BTS (indicated by a leftward arrow). The BTS responds with a CHANNEL ACT ACK message to the BSC (indicated by a rightward arrow). + +Sequence diagram for Channel reactivation + +If the TRX for some reason cannot reactivate the channel as requested in the CHANNEL ACTIVATION message, the TRX shall return a CHANNEL ACTivation Negative ACKnowledge message with the most appropriate cause value. + +![Sequence diagram for Channel reactivation failure](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note over MS: MS + BSC->>BTS: CHANNEL ACT + BTS->>BSC: CHANNEL ACT NACK + +``` + +Sequence diagram illustrating Channel reactivation failure. The diagram shows three participants: MS, BTS, and BSC. The MS is shown as a label above a vertical line. The BSC sends a CHANNEL ACT message to the BTS (leftward arrow). The BTS responds with a CHANNEL ACT NACK message to the BSC (rightward arrow). + +Sequence diagram for Channel reactivation failure + +## 4.2 Channel MODE MODIFY + +This procedure is used by BSC to request a change of the channel mode and/or a change between uni-directional and bi-directional channel types of an active channel. In addition, for secondary channels in a multislot configuration, the procedure can be used by BSC to request a change in the encryption information of an active channel. + +BSC initiates the procedure by sending a MODE MODIFY message to BTS. The message contains the new mode to be used. After having changed to the new mode, BTS responds with a MODE MODIFY ACKnowledge message to BSC. + +![Sequence diagram for Channel MODE MODIFY](9e1c95ee7eb045977f18f011f49520c7_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note over MS: MS + BSC->>BTS: MODE MODIFY + BTS->>BSC: MODE MODIFY ACK + +``` + +Sequence diagram illustrating Channel MODE MODIFY. The diagram shows three participants: MS, BTS, and BSC. The MS is shown as a label above a vertical line. The BSC sends a MODE MODIFY message to the BTS (leftward arrow). The BTS responds with a MODE MODIFY ACK message to the BSC (rightward arrow). + +Sequence diagram for Channel MODE MODIFY + +If the TRX for some reason cannot modify the channel as requested in the MODE MODIFY message, the TRX shall return a MODE MODIFY Negative ACKnowledge message with the most appropriate cause value. + +![Sequence diagram showing MODE MODIFY and MODE MODIFY NACK messages between BTS and BSC.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of MS: MS + Note right of BSC: BSC + BTS->>BSC: MODE MODIFY + BSC-->>BTS: MODE MODIFY NACK + +``` + +Sequence diagram showing MODE MODIFY and MODE MODIFY NACK messages between BTS and BSC. + +## 4.3 Handover detection + +This procedure is used between the target BTS and BSC when a handed over MS accesses the new BTS. + +The procedure is initiated by BTS upon detection of an MS on a channel activated for handover as described in sub-clause 4.1.3 for the asynchronous handover and in sub-clause 4.1.4 for synchronous handover. + +In case of an asynchronous handover, BTS builds the PHYsical INformation message as specified in 3GPP TS 44.018, sends the message to MS in unacknowledged mode on the main signalling link and starts timer T3105. A HANDOver DETection message is sent to BSC. This message contains the measured delay of the access burst. If the timer expires before the reception of a correctly decoded frame from MS, BTS repeats the PHYsical INformation message to MS as specified in 3GPP TS 44.018. If the PHYsical INformation message has been repeated Ny1 times without a correctly decoded frame being received from MS, the BTS shall send a CONNECTION FAILURE message to BSC with the cause value "handover access failure". + +In case of a synchronous handover, BTS only sends a HANDOver DETection message to BSC (no PHYsical INformation message sent to MS). If the handover detection is based on the detection of an handover access burst with the correct handover reference, see sub-clause 4.1.4, the measured delay of the access burst is included in the HANDOver DETection message. + +![Sequence diagram showing HANDO ACCESS, PHY INFO, and HANDO DET messages between MS, BTS, and BSC.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of MS: MS + Note right of BSC: BSC + MS-->>BTS: HANDO ACCESS + Note right of BTS: PHY INFO + BTS->>BSC: HANDO DET + +``` + +Sequence diagram showing HANDO ACCESS, PHY INFO, and HANDO DET messages between MS, BTS, and BSC. + +## 4.4 Start of encryption + +This procedure is used to start encryption according to the procedure defined in 3GPP TS 44.018. + +The procedure is initiated by BSC upon reception of the CIPHER MODE COMMAND message from MSC (see 3GPP TS 48.008). + +BSC sends the ENCRyption CoMmanD message to the relevant TRX and channel. In case of a Multislot configuration the message is sent only to the TCH used as a main channel (defined in 3GPP TS 45.002). The message contains all information required to select and load the user data and encryption device with the appropriate key and also the complete Ciphering Mode Command message to be sent to MS. + +After receipt of this message, TRX sends the CIPHERing MODE CoMmanD message to MS in unciphered form and starts deciphering as described in 3GPP TS 44.018 and 3GPP TS 43.020. The start of deciphering and the sending of the Ciphering Mode Command message to MS must be done simultaneously. + +When receiving the CIPHERing MODE CoMmanD, MS starts both deciphering and enciphering and sends the CIPHERing MODE COMplete message. + +TRX starts enciphering upon reception of any correct layer 2 frame which is received after start of deciphering. + +![Sequence diagram showing the encryption process between MS, BTS, and BSC. The BSC sends an ENCR CMD to the BTS. The BTS sends a CIPH MODE CMD to the MS. The MS responds with (pending L2 frames). The BTS starts deciphering. The MS sends a correct L2 frame. The BTS starts enciphering and sends a CIPH MOD COM to the MS. The MS responds with a CIPH MOD COM.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of MS: (pending L2 frames) + BSC->>BTS: ENCR CMD + BTS->>MS: CIPH MODE CMD + MS-->>BTS: (pending L2 frames) + Note right of BTS: (start deciphering) + MS-->>BTS: correct L2 frame + Note right of BTS: (start enciphering) + BTS->>MS: CIPH MOD COM + MS-->>BTS: CIPH MOD COM + +``` + +Sequence diagram showing the encryption process between MS, BTS, and BSC. The BSC sends an ENCR CMD to the BTS. The BTS sends a CIPH MODE CMD to the MS. The MS responds with (pending L2 frames). The BTS starts deciphering. The MS sends a correct L2 frame. The BTS starts enciphering and sends a CIPH MOD COM to the MS. The MS responds with a CIPH MOD COM. + +If the TRX for some reason can not perform the enciphering as requested in the ENCRYPTION COMMAND, the TRX shall return an ERROR REPORT message, e.g., with the cause "Encryption algorithm not implemented". + +![Sequence diagram showing an error case. The BSC sends an ENCR CMD to the BTS. The BTS responds with an ERROR REPORT.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + BSC->>BTS: ENCR CMD + BTS-->>BSC: ERROR REPORT + +``` + +Sequence diagram showing an error case. The BSC sends an ENCR CMD to the BTS. The BTS responds with an ERROR REPORT. + +## 4.5 Measurement reporting + +These procedures are used to report to BSC all parameters and measurement results required by BSC for handover requirement determination. One procedure is also used to report to the BSC extended measurements made by Mobile Stations. + +MS measures downlink received signal level and quality from the serving cell and received signal level from surrounding cells as defined in 3GPP TS 45.005 and 3GPP TS 45.008. The measurement results are reported in Measurement Report messages sent in every SACCH block (every 480 ms) or, in case SACCH is used also for other signalling, in at least every second SACCH block (every 960 ms). + +In addition, the MS which implements ECSD options shall use fast inband procedure for downlink quality reporting if the use of such procedure has been ordered by the BSC. + +In addition, an MS on a channel in enhanced power control (EPC) mode shall measure the quality on the downlink and send EPC Downlink Quality Reports in each EPCCH block (every 120 ms) as defined in 3GPP TS 45.008, if so ordered by the BSC (see 3GPP TS 44.018). + +The TRX measures the received signal level and the quality on the uplink of the current channel. The averaging period is one SACCH block period (same as the basic period for MS). + +In addition, a TRX that supports EPC shall measure the quality on the uplink for each channel in EPC mode. The averaging period is one EPC reporting period (see 3GPP TS 45.008). + +These measurements made by MS and TRX form the basic raw data for the handover algorithms in BSC/MSC. The support of forwarding this raw data over the A-bis interface is mandatory for both BTS and BSC. The procedure to be used for this basic measurement reporting is defined in sub-clause 4.5.1. + +In addition, the BTS and BSC may optionally support some pre-processing in BTS of these basic measurements. The additional and optional procedures required to support this pre-processing are defined in sub-clause 4.5.2. + +Extended measurements made by MS shall be forwarded to the BSC, using the same procedure as for 'normal' measurements. This case is described in sub-clause 4.5.3. + +### 4.5.1 Basic measurement reporting + +This procedure is used by BTS to report the results of the basic radio measurements made by MS and TRX according to 3GPP TS 45.008 and 3GPP TS 45.005. The support of this procedure is mandatory in all BTS:s and all BSC:s. It is the default procedure to use unless otherwise indicated (see sub-clause 4.5.2.1). + +TRX reports all these measurements in MEASurement RESult messages to BSC. The sending of the MEASurement RESult messages is synchronized with the reception of SACCH blocks from MS. + +If an uplink SACCH block does not contain a MEASurement REPort or an EXTended MEASurement REPort (see sub-clause 4.5.3) from MS (e.g. when it sends a short message), only the uplink measurement results are included with an indication that the MS measurements are missing. + +![Sequence diagram showing measurement reporting from MS to BTS to BSC. The diagram illustrates four scenarios: 1) MS sends MEAS REP, BTS performs measurements and sends MEAS RES to BSC. 2) MS sends MEAS REP, BTS performs measurements and sends MEAS RES to BSC. 3) MS does not send a measurement report (indicated by a dashed line labeled '(no meas rep)'), BTS sends MEAS RES (no MS rep) to BSC. 4) MS sends MEAS REP, BTS performs measurements and sends MEAS RES to BSC.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BTS: (perform uplink measurements) + MS->>BTS: MEAS REP + BTS->>BSC: MEAS RES + Note right of BTS: (perform uplink measurements) + MS->>BTS: MEAS REP + BTS->>BSC: MEAS RES + Note right of BTS: (perform uplink measurements) + MS-->>BTS: (no meas rep) + BTS->>BSC: MEAS RES (no MS rep) + Note right of BTS: (perform uplink measurements) + MS->>BTS: MEAS REP + BTS->>BSC: MEAS RES + +``` + +Sequence diagram showing measurement reporting from MS to BTS to BSC. The diagram illustrates four scenarios: 1) MS sends MEAS REP, BTS performs measurements and sends MEAS RES to BSC. 2) MS sends MEAS REP, BTS performs measurements and sends MEAS RES to BSC. 3) MS does not send a measurement report (indicated by a dashed line labeled '(no meas rep)'), BTS sends MEAS RES (no MS rep) to BSC. 4) MS sends MEAS REP, BTS performs measurements and sends MEAS RES to BSC. + +### 4.5.2 Measurement pre-processing + +These additional and optional procedures are included to support some pre-processing in BTS of radio measurement data. When used, they may replace the basic procedure defined in sub-clause 4.5.1. However, it shall be possible to change back to the basic procedure. + +Pre-processing in BTS must not affect the procedures on the A interface (e.g. the Handover Candidate Enquiry procedure). + +#### 4.5.2.1 Pre-processing configuration + +This procedure is used by BSC to modify the pre-processing parameters according to reported communication conditions (e.g. degradation of the communication). + +In order to change the parameters, BSC sends a PREPROCESS CONFIGURE message to BTS. + +A parameter setting in the PREPROCESS CONFIGURE message indicates if the basic procedure defined in sub-clause 4.5.1 or pre-processing is to be used. + +![Sequence diagram showing the PREPROC. CONFIG. message being sent from the BSC to the BTS.](aa9441a5971655a79987d70fc551b26a_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BSC->>BTS: PREPROC. CONFIG. + +``` + +Sequence diagram showing the PREPROC. CONFIG. message being sent from the BSC to the BTS. + +#### 4.5.2.2 Pre-processed measurement reporting + +This procedure is used by BTS to report the results of measurement pre-processing. + +To report the results, BTS sends a PREPROCESSED MEASUREMENT RESULT message to BSC. + +The conditions to send the message are set in the PREPROCESS CONFIGURE message. + +![Sequence diagram for regular measurement reporting. MS sends MEAS REP to BTS. BTS performs uplink measurements and MS measurement pre-processing, then sends PREPROC MEAS RES to BSC. This repeats for a second MEAS REP. A dashed line indicates a missing (no meas rep) message. A third MEAS REP is sent, followed by another PREPROC MEAS RES to BSC.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BTS: perform uplink measurements and MS measurement pre-processing + MS->>BTS: MEAS REP + BTS->>BSC: PREPROC MEAS RES + Note right of BTS: perform uplink measurements and MS measurement pre-processing + MS->>BTS: MEAS REP + Note right of MS: (no meas rep) + MS-->>BTS: + MS->>BTS: MEAS REP + BTS->>BSC: PREPROC MEAS RES + +``` + +Sequence diagram for regular measurement reporting. MS sends MEAS REP to BTS. BTS performs uplink measurements and MS measurement pre-processing, then sends PREPROC MEAS RES to BSC. This repeats for a second MEAS REP. A dashed line indicates a missing (no meas rep) message. A third MEAS REP is sent, followed by another PREPROC MEAS RES to BSC. + +### 4.5.3 Extended measurement reporting + +This procedure is used by BTS to report the results of the extended measurements made by MS according to 3GPP TS 45.008. + +If an uplink SACCH block contains an EXTended MEASurement REPort from MS, it shall be forwarded to the BSC using the same procedure as when reporting regular measurement reports from an MS. Though, no measurement pre-processing is possible. + +![Sequence diagram for extended measurement reporting. MS sends MEAS REP to BTS. BTS performs uplink measurements and sends MEAS RES to BSC. MS sends EXT MEAS REP to BTS. BTS performs uplink measurements and sends MEAS RES to BSC. MS sends MEAS REP to BTS. BTS performs uplink measurements and sends MEAS RES to BSC. A dashed line indicates a missing (no meas rep) message. BTS sends MEAS RES(no MS rep) to BSC.](12de9b926df0384ec07702671827c9cd_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BTS: (perform uplink measurements) + MS->>BTS: MEAS REP + BTS->>BSC: MEAS RES + Note right of BTS: (perform uplink measurements) + MS->>BTS: EXT MEAS REP + BTS->>BSC: MEAS RES + Note right of BTS: (perform uplink measurements) + MS->>BTS: MEAS REP + BTS->>BSC: MEAS RES + Note right of BTS: (perform uplink measurements) + Note right of MS: (no meas rep) + MS-->>BTS: + BTS->>BSC: MEAS RES(no MS rep) + +``` + +Sequence diagram for extended measurement reporting. MS sends MEAS REP to BTS. BTS performs uplink measurements and sends MEAS RES to BSC. MS sends EXT MEAS REP to BTS. BTS performs uplink measurements and sends MEAS RES to BSC. MS sends MEAS REP to BTS. BTS performs uplink measurements and sends MEAS RES to BSC. A dashed line indicates a missing (no meas rep) message. BTS sends MEAS RES(no MS rep) to BSC. + +## 4.6 Deactivate SACCH + +This procedure is used by BSC to deactivate the SACCH at BTS according to the Channel Release procedure defined in 3GPP TS 44.018. + +When sending the Channel Release message to MS, BSC also sends the DEACTIVATE SACCH message to BTS to deactivate the SACCH (see 3GPP TS 44.018, Channel Release procedure). + +![Sequence diagram showing the release of a radio channel. The diagram involves three entities: MS (Mobile Station), BTS (Base Transceiver Station), and BSC (Base Station Controller). The sequence of messages is: 1. A dashed arrow points from the BSC to the MS, labeled 'CHAN REL'. 2. A solid arrow points from the BTS to the BSC, labeled 'DEACT SACCH'.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BSC: CHAN REL + BSC-->>MS: CHAN REL + Note right of BTS: DEACT SACCH + BTS->>BSC: DEACT SACCH + +``` + +Sequence diagram showing the release of a radio channel. The diagram involves three entities: MS (Mobile Station), BTS (Base Transceiver Station), and BSC (Base Station Controller). The sequence of messages is: 1. A dashed arrow points from the BSC to the MS, labeled 'CHAN REL'. 2. A solid arrow points from the BTS to the BSC, labeled 'DEACT SACCH'. + +## 4.7 Radio channel release + +This procedure is used by BSC to release a radio channel which is no longer needed. + +When an activated radio channel is no longer needed, BSC sends an RF CHANNEL RELEASE message to the relevant TRX and channel. After having released the addressed resources, the BTS sends a RF CHANNEL RELEASE ACKnowledge to BSC. + +![Sequence diagram showing the radio channel release procedure. The diagram involves two entities: BTS (Base Transceiver Station) and BSC (Base Station Controller). The sequence of messages is: 1. A solid arrow points from the BSC to the BTS, labeled 'RF CHAN REL'. 2. A solid arrow points from the BTS to the BSC, labeled 'RF CHAN REL ACK'.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note right of BSC: RF CHAN REL + BSC->>BTS: RF CHAN REL + Note right of BTS: RF CHAN REL ACK + BTS->>BSC: RF CHAN REL ACK + +``` + +Sequence diagram showing the radio channel release procedure. The diagram involves two entities: BTS (Base Transceiver Station) and BSC (Base Station Controller). The sequence of messages is: 1. A solid arrow points from the BSC to the BTS, labeled 'RF CHAN REL'. 2. A solid arrow points from the BTS to the BSC, labeled 'RF CHAN REL ACK'. + +## 4.8 MS power control + +This procedure is used by BSC to set the MS power level or the parameters required by TRX for the control of MS power. + +The initial parameters are set by BSC in the CHANNEL ACTIVATION message (see Channel Activation procedure). If these parameters are to be changed for an active channel, BSC sends a MS POWER CONTROL message to TRX. + +The support of the power control and the enhanced power control performed by BTS is optional. + +If power control is supported by BTS and it is to be used, this is indicated by optional parameters in the MS POWER CONTROL message (or the CHANNEL ACTIVATION message). Based on the measurements performed on the uplink, TRX then attempts to keep the power control parameters within the limits set by the MS POWER CONTROL message (or by the CHANNEL ACTIVATION message) by changing the MS Power Level field of the L1 header sent to MS in each SACCH block. MS confirms the power in the uplink L1 header. + +When the BTS supports MS power control the BSC can modify the MS power parameters during the connection (e.g. because of a classmark change) by sending a MS POWER CONTROL message containing the new parameters. + +The MS POWER CONTROL and the CHANNEL ACTIVATION message must also contain a maximum power permitted for the MS. + +In addition, the BTS which implements ECSD option shall use fast inband procedure for fast power control if the use of such procedure has been ordered by the BSC. + +A BTS that supports enhanced power control (EPC) shall use EPC procedures for MS (uplink) power control (see 3GPP TS 45.008) if so ordered by the BSC in the MS POWER CONTROL message (or CHANNEL ACTIVATION message). Based on the measurements performed on the uplink, TRX then attempts to keep the power control parameters within the limits set by the MS POWER CONTROL message (or by the CHANNEL ACTIVATION message) by sending EPC Uplink Power Control Commands to the MS in each EPCCH block. MS confirms the power in the uplink L1 header on the SACCH. + +![Sequence diagram showing MS, BTS, and BSC interaction for MS Power Control. The BSC sends an MS POWER CONTROL message to the BTS. The BTS responds with an L1-header and (SACCH). The MS then sends an L1-header and (SACCH) back to the BTS. A note indicates that the BTS should keep parameters within limits set by the message.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BSC: MS POWER CONTROL + BSC->>BTS: MS POWER CONTROL + Note right of BTS: (keep parameters within limits set by message) + BTS-->>MS: L1-header + Note right of MS: (SACCH) + MS-->>BTS: L1-header + Note right of BTS: (SACCH) + +``` + +Sequence diagram showing MS, BTS, and BSC interaction for MS Power Control. The BSC sends an MS POWER CONTROL message to the BTS. The BTS responds with an L1-header and (SACCH). The MS then sends an L1-header and (SACCH) back to the BTS. A note indicates that the BTS should keep parameters within limits set by the message. + +## 4.9 Transmission power control + +This is an optional procedure which is used between BSC and BTS to set the TRX transmission power level or the parameters required by TRX for the control of TRX transmission power. + +The initial parameters are set by BSC in the CHANNEL ACTIVATION message (see Channel Activation procedure). If these parameters are to be changed for an active channel, BSC sends a BS POWER CONTROL message to TRX. + +The support of the power control, the fast power control and the enhanced power control performed by BTS are optional. + +If power control is supported by BTS and it is to be used, this is indicated by optional parameters in the BS POWER CONTROL message (or the CHANNEL ACTIVATION message). Based on the Measurement Report messages sent by MS, the TRX will then attempt to keep the power control parameters within the limits set in the BS POWER CONTROL message (or by the CHANNEL ACTIVATION message) by changing the transmitted power on that channel. + +If fast power control mechanism is supported by BTS and is to be used, this is indicated by optional parameters in the BS POWER CONTROL message (or by the CHANNEL ACTIVATION message). Based on the Fast Measurement Report messages sent by MS, the TRX will then attempt to keep the power control parameters within the limits set in the BS POWER CONTROL message (or by the CHANNEL ACTIVATION message) by changing the transmitted power on that channel. + +A BTS that supports enhanced power control (EPC) shall use EPC procedures for BS (downlink) power control (see 3GPP TS 45.008) if so ordered by the BSC in the BS POWER CONTROL message (or CHANNEL ACTIVATION message). Based on the EPC Downlink Quality Reports sent by the MS, the TRX shall then attempt to keep the power control parameters within the limits set in the BS POWER CONTROL message (or by the CHANNEL ACTIVATION message) by changing the transmitted power on that channel. + +NOTE: The EPC mode field is only valid in the channel activation message. + +The maximum power of the TRX is determined from network planning criteria. However, BSC may indicate a lower maximum power in the BS POWER CONTROL message (or the CHANNEL ACTIVATION message). + +![Sequence diagram showing BSC sending a BS POWER CONTROL message to the BTS.](c0e369274e53b2e5364666be6f786c7a_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note right of BSC: BS POWER CONTROL + BSC->>BTS: BS POWER CONTROL + +``` + +Sequence diagram showing BSC sending a BS POWER CONTROL message to the BTS. + +## 4.10 Connection failure + +This procedure is used by BTS to indicate to BSC that an active connection has been broken (e.g. due to a radio link failure as defined in 3GPP TS 45.008). + +When BTS detects that a connection has been broken, BTS sends a CONNection FAILure INDication message to BSC with the most proper cause value. Further actions are defined in 3GPP TS 44.018. + +Some possible cause values are: + +- radio link failure (as defined in 3GPP TS 45.008); +- hardware failure (e.g. transcoder failure); +- etc. + +![Sequence diagram showing a CONN FAIL IND message sent from BTS to BSC.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BTS->>BSC: CONN FAIL IND + +``` + +Sequence diagram showing a CONN FAIL IND message sent from BTS to BSC. + +## 4.11 Physical context request + +This is an optional procedure which allows the BSC to obtain information on the "physical context" of a radio channel just prior to a channel change. This information may be forwarded to the new TRX (possibly in another collocated cell). + +The procedure is initiated by BSC sending a PHYSical CONTEXT REQuest message to TRX. TRX responds with a PHYSical CONTEXT CONFirm message which contains information on the "physical context" of the channel. + +![Sequence diagram showing the BSC sending a PHYS CONTEXT REQ to the BTS, and the BTS responding with a PHYS CONTEXT CONF to the BSC.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BSC->>BTS: PHYS CONTEXT REQ + BTS->>BSC: PHYS CONTEXT CONF + +``` + +Sequence diagram showing the BSC sending a PHYS CONTEXT REQ to the BTS, and the BTS responding with a PHYS CONTEXT CONF to the BSC. + +## 4.12 SACCH information modify + +This procedure is used by the BSC to modify the SACCH filling information (System Information) sent on an individual SACCH channel. For this purpose, the BSC sends a SACCH INFO MODIFY message to the BTS. The SACCH filling information as given in the SACCH INFO MODIFY message shall be used on the indicated channel until the channel is released or the information is changed by another SACCH INFO MODIFY message. + +![Sequence diagram showing the BSC sending a SACCH INFO MODIFY message to the BTS.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BSC->>BTS: SACCH INFO MODIFY + +``` + +Sequence diagram showing the BSC sending a SACCH INFO MODIFY message to the BTS. + +## 4.13 Talker detection + +The procedure is used by the BTS during the period the channel is activated for a voice group call. Upon detection of an MS on a channel activated for group call as specified in sub-clause 4.1, the BTS builds the VGCS UPLINK GRANT message as specified in 3GPP TS 44.018, sends the message to the MS in unacknowledged mode on the main signalling link and starts timer T3115. A TALKER DETection message is sent to the BSC. This message contains the measured delay of the access burst. If the timer expires before the reception of a correctly decoded frame from the MS, the BTS repeats the VGCS UPLINK GRANT message to the MS as specified in 3GPP TS 44.018. If the VGCS UPLINK GRANT message has been repeated Ny2 times without a correctly decoded frame being received from the MS, the BTS shall send a CONNECTION FAILURE INDICATION message to the BSC with cause value "talker access failure". + +![Sequence diagram showing MS sending UPLINK ACCESS to BTS, BTS responding to MS with VGCS UPLINK GRANT, and BTS sending TALKER DET to BSC.](8ed7f57cc317f6574bec781d01ae6ad2_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + MS->>BTS: UPLINK ACCESS + BTS->>MS: VGCS UPLINK GRANT + BTS->>BSC: TALKER DET + +``` + +Sequence diagram showing MS sending UPLINK ACCESS to BTS, BTS responding to MS with VGCS UPLINK GRANT, and BTS sending TALKER DET to BSC. + +## 4.14 Listener detection + +The procedure is used by the BTS during the period the channel is activated for a voice group call. Upon detection of an uplink access having the value reserved for replying to an uplink access request as specified in sub-clause 4.1. The BTS + +builds the LISTENER DETection message and sends the message to the BSC. This message contains the measured delay of the access burst. + +![Sequence diagram showing MS, BTS, and BSC. A dashed arrow labeled 'UPLINK ACCESS' goes from MS to BTS. A solid arrow labeled 'LISTENER DET' goes from BTS to BSC.](844077b3034f0030b404207db0ad76b4_img.jpg) + +``` +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of BTS: UPLINK ACCESS + BTS->>BSC: LISTENER DET +``` + +Sequence diagram showing MS, BTS, and BSC. A dashed arrow labeled 'UPLINK ACCESS' goes from MS to BTS. A solid arrow labeled 'LISTENER DET' goes from BTS to BSC. + +## 4.15 Remote Codec Configuration + +This procedure is used by the BTS to report to the BSC the codec information received from the remote BSS prior to a MultiRate Codec TFO establishment or within TFO. This information can be used by the BSC to solve potential codec type and codec mode mismatches. + +![Sequence diagram showing BTS and BSC. A dashed arrow labeled 'REMOTE CODEC CONF' goes from BTS to BSC.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +``` +sequenceDiagram + participant BTS + participant BSC + BTS-->>BSC: REMOTE CODEC CONF +``` + +Sequence diagram showing BTS and BSC. A dashed arrow labeled 'REMOTE CODEC CONF' goes from BTS to BSC. + +## 4.16 Round Trip Delay Report + +This procedure is used by the BTS to report to the BSC the BTS to Transcoder or BTS to Remote BTS round trip transmission delay. This information can be used by the BSC to set the correct timing for a pre-handover warning and to optimise the AMR Configuration and/or Adaptation algorithm. + +![Sequence diagram showing BTS and BSC. A dashed arrow labeled 'RTD REP' goes from BTS to BSC.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +``` +sequenceDiagram + participant BTS + participant BSC + BTS-->>BSC: RTD REP +``` + +Sequence diagram showing BTS and BSC. A dashed arrow labeled 'RTD REP' goes from BTS to BSC. + +## 4.17 Pre-handover Warning + +This procedure is used by the BSC to notify the serving BTS that a handover is going to be performed and allow the serving BTS to take the necessary steps in preparation of the handover (adaptation freezing for MultiRate Codec, TFO discontinuation,...). The Pre-handover Warning may disable (withdraw the “general authorisation” of ) the RATSCCH mechanism between BTS and MS for a while or permanently to ensure consistent configurations in BSC, BTSs and MS during and after handover. The BSC shall provide to the BTS the codec configuration parameters after Handover. + +In case the announced handover has failed, the BSC sends the Pre-handover Notification again to the serving BTS, this time with the codec configuration parameters as before the handover attempt in order to re-establish the BTS operation (adaptation enable for MultiRate Codec, TFO enable, RATSCCH authorisation, ...). + +![Sequence diagram showing BTS and BSC. A dashed arrow labeled 'PRE-HANDO NOTIF' goes from BSC to BTS.](414cf5c0e2959c558de57a9fb5c2134a_img.jpg) + +``` +sequenceDiagram + participant BTS + participant BSC + BSC-->>BTS: PRE-HANDO NOTIF +``` + +Sequence diagram showing BTS and BSC. A dashed arrow labeled 'PRE-HANDO NOTIF' goes from BSC to BTS. + +## 4.18 MultiRate Codec Configuration Change + +This procedure is used by the BSC to authorise the BTS to change the MultiRate Codec Configuration to solve a codec mismatch prior to TFO establishment or within TFO. The BTS shall use the RATSCCH inband signalling with the MS as defined by Rec 3GPP TS 45.009. + +Once the MultiRate Codec Configuration has been changed, the BTS shall send a MultiRate CODEC MOD ACK to the BSC to acknowledge the execution of the codec change. The MultiRate CODEC MOD ACK contains the final MultiRate Codec configuration. + +![](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + + MS BTS BSC + | | | + | | MultiRate CODEC MOD REQ + | |<----------------------| + | RATSCH SEQUENCE (GSM 05.09) | + |< - - - - - - - - - - ->| | + | | | + | | MultiRate CODEC MOD ACK + | |---------------------->| + | | | + +``` + +If for any reason, the BTS is not able to complete the MultiRate Codec Configuration change, it should send a MultiRate CODEC MOD Negative ACK with the most appropriate cause. + +![](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +``` + + MS BTS BSC + | | | + | | MultiRate CODEC MOD REQ + | |<----------------------| + | Failed Configuration Change | + |< - - - - - - - - - - ->| | + | | | + | | MultiRate CODEC MOD NACK + | |---------------------->| + | | | + +``` + +Possible causes are: + +- tbd + +This procedure is also used by the BTS to indicate to the BSC the optimal codec configuration for TFO, in the case where the TC or the BTS runs the TFO algorithm, and the BSC is responsible for changing the codec configuration. The BSC does not acknowledge this message. + +![](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +``` + + BTS BSC + | | + | | + | MultiRate CODEC MOD REQ | + |-------------------------------->| + | | + | | + +``` + +## 4.19 MultiRate Codec Configuration Change Performed + +This procedure is used by the BTS to report to the BSC that a MultiRate Codec Modification was performed using the RATSCH in-band signalling capability. The BTS shall report the MultiRate codec configuration after the completion of the procedure. + +![](14515d82ffeec9475b9add3036ff26ab_img.jpg) + +``` + + BTS BSC + | | + | MultiRate CODEC MOD PERF | + |-------------------------------->| + | | + +``` + +## 4.20 TFO Report + +This procedure is used by the BTS to report to the BSC that TFO (based on AMR) is established, or is not in operation anymore. + +![Sequence diagram showing a TFO REPORT message from BTS to BSC.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BTS->>BSC: TFO REPORT + +``` + +Sequence diagram showing a TFO REPORT message from BTS to BSC. + +## 4.21 TFO Modification Request + +This procedure is used by the BSC to change the TFO configuration while operating with AMR: enabling or disabling TFO. + +This procedure shall be used only during an established call. At call setup, Channel Activation procedure shall be used. During an in-call modification from data to speech, Mode Modify procedure shall be used. + +![Sequence diagram showing a TFO MODIFICATION REQUEST message from BSC to BTS.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BSC->>BTS: TFO MODIFICATION REQUEST + +``` + +Sequence diagram showing a TFO MODIFICATION REQUEST message from BSC to BTS. + +# 5 Common channel management procedures + +## 5.1 Channel request by MS + +The procedure is initiated by TRX upon detection of a random access from an MS (CHANnel REQuest message from MS). TRX then sends a CHANnel ReRequireD message to BSC containing the Request Reference parameter (random number selected by MS plus some low order bits of the TDMA frame number for the access) and the measured delay of the Access Burst. + +![Sequence diagram showing a CHAN REQ message from MS to BTS, followed by a CHAN RQD message from BTS to BSC.](303fadfb9def251d1575d6221199b158_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + MS-->>BTS: CHAN REQ + BTS->>BSC: CHAN RQD + +``` + +Sequence diagram showing a CHAN REQ message from MS to BTS, followed by a CHAN RQD message from BTS to BSC. + +## 5.2 Paging + +This procedure is used to request the paging of one mobile station on a given paging subchannel. + +The paging of an MS is initiated by BSC sending a PAGing CoMmanD message to BTS. The message contains the MS identity (TMSI or IMSI), the paging population number of the MS, optionally an indication for the MS about which combination of channels will be needed for the subsequent transaction related to the paging and optionally an indication of the eMLPP priority of the call. + +The PAGing REQuest messages to be sent on the radio path are built and sent by BTS. + +The use by BTS of the "extended paging" facilities and the general downlink scheduling of the downlink CCCH is operator dependant and is not specified in this GTS. This process may also be influenced by O&M procedures. + +![Sequence diagram showing a PAGING message to BSC, a PAG CMD message from BSC to BTS, a note about building and scheduling the request, and a PAG REQ message from BTS to MS.](8facb5a02c64e245808bafc005e65032_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note over BSC: PAGING + BSC-->>BTS: PAG CMD + Note over BTS: (build and schedule PAG REQ) + BTS-->>MS: PAG REQ + +``` + +Sequence diagram showing a PAGING message to BSC, a PAG CMD message from BSC to BTS, a note about building and scheduling the request, and a PAG REQ message from BTS to MS. + +## 5.3 Delete indication + +This procedure is used by BTS to indicate that due to overload on the downlink CCCH, an IMMEDIATE ASSIGN COMMAND has been deleted. + +For that purpose BTS sends a DELETE INDication message to BSC. + +![Sequence diagram showing a DELETE IND message from BTS to BSC.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note left of BTS: + Note right of BSC: + BTS->>BSC: DELETE IND + +``` + +Sequence diagram showing a DELETE IND message from BTS to BSC. + +## 5.4 CCCH load indication + +This procedure is used by a BTS to inform the BSC of the load on a particular CCCH timeslot. + +The CCCH LOAD INDication message is sent regularly from BTS to BSC if the load exceeds some value set by O&M. The sending rate is also set by O&M. + +![Sequence diagram showing two CCCH LOAD IND messages from BTS to BSC, with a note about threshold and period set by O&M.](bb3354f497635d15bef873577125c48d_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note left of BTS: Threshold and period set by O&M + Note right of BSC: + BTS->>BSC: CCCH LOAD IND + Note left of BTS: + Note right of BSC: + BTS->>BSC: CCCH LOAD IND + +``` + +Sequence diagram showing two CCCH LOAD IND messages from BTS to BSC, with a note about threshold and period set by O&M. + +## 5.5 Broadcast information modify + +This procedure is used by BSC to indicate to BTS the new information to be broadcast on BCCH. + +For that purpose, BSC sends a BCCH INFormation message to BTS. + +![Sequence diagram showing a BCCH INFO message from BSC to BTS.](1c140ee5d1a87186977da94a96bfa700_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note left of BTS: + Note right of BSC: + BSC->>BTS: BCCH INFO + +``` + +Sequence diagram showing a BCCH INFO message from BSC to BTS. + +## 5.6 Short Message Cell Broadcast + +Short Message Service Cell Broadcast messages are sent to BTS as SMS BROADCAST REQUEST or SMS BROADCAST COMMAND messages. + +With the SMS BROADCAST REQUEST mode of operation, the BSC handles the queuing, repetition and transmission of the messages taking the capacity of the CBCHs (basic and extended channel (see 3GPP TS 45.002)) into account. The BSC is also responsible for the segmentation of the SMS Cell Broadcast messages on the Radio interface: + +![Sequence diagram showing an SMS BROADCAST REQ message from BSC to BTS, which then results in a CBCH block n being sent to the MS.](298e7e2164a95d0d5bb8e5d1f7155094_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note left of MS: + Note right of BTS: + Note right of BSC: + BSC->>BTS: SMS BROADCAST REQ + Note left of MS: + Note right of BTS: + Note right of BSC: + BTS-->>MS: CBCH block n + +``` + +Sequence diagram showing an SMS BROADCAST REQ message from BSC to BTS, which then results in a CBCH block n being sent to the MS. + +With the SMS BROADCAST COMMAND mode of operation, the BSC can request the broadcast of a complete Cell Broadcast message. The BSC handles the queuing, repetition and transmission of the messages taking the capacity of the CBCHs (basic and extended channel [see 3GPP TS 45.002]) into account. The BSC is responsible for the segmentation of the SMS Cell Broadcast messages on the Radio interface: + +![Sequence diagram showing MS, BTS, and BSC. BSC sends 'SMS BROADCAST CMD (SMSCB message)' to BTS. BTS then transmits 'CBCH block 1', 'CBCH block 2', 'CBCH block 3', and 'CBCH block 4' to MS.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BSC: SMS BROADCAST CMD +(SMSCB message) + BSC->>BTS: SMS BROADCAST CMD (SMSCB message) + Note left of BTS: CBCH block 1 + Note left of BTS: <- - - - - + Note left of BTS: CBCH block 2 + Note left of BTS: <- - - - - + Note left of BTS: CBCH block 3 + Note left of BTS: <- - - - - + Note left of BTS: CBCH block 4 + Note left of BTS: <- - - - - + +``` + +Sequence diagram showing MS, BTS, and BSC. BSC sends 'SMS BROADCAST CMD (SMSCB message)' to BTS. BTS then transmits 'CBCH block 1', 'CBCH block 2', 'CBCH block 3', and 'CBCH block 4' to MS. + +With the SMS BROADCAST COMMAND mode of operation, the BSC can also set the BTS broadcast default mode. The BTS is then responsible for transmission of a default message when no other message is to be broadcast. + +![Sequence diagram showing MS, BTS, and BSC. BSC sends 'SMS BROADCAST CMD (Default SMSCB message)' to BTS. BTS then transmits 'In all empty transmission slots', 'CBCH block 1', 'CBCH block 2', 'CBCH block 3', and 'CBCH block 4' to MS.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BSC: SMS BROADCAST CMD +(Default SMSCB message) + BSC->>BTS: SMS BROADCAST CMD (Default SMSCB message) + Note left of BTS: In all empty transmission slots + Note left of BTS: CBCH block 1 + Note left of BTS: <- - - - - + Note left of BTS: CBCH block 2 + Note left of BTS: <- - - - - + Note left of BTS: CBCH block 3 + Note left of BTS: <- - - - - + Note left of BTS: CBCH block 4 + Note left of BTS: <- - - - - + +``` + +Sequence diagram showing MS, BTS, and BSC. BSC sends 'SMS BROADCAST CMD (Default SMSCB message)' to BTS. BTS then transmits 'In all empty transmission slots', 'CBCH block 1', 'CBCH block 2', 'CBCH block 3', and 'CBCH block 4' to MS. + +Even though BSC handles the transmission of messages taking the capacity of CBCH into account, BTS can indicate to BSC if an overflow or underflow situation is about to happen in the CBCH. With the CBCH LOAD INDICATION mode of operation, the BTS can request immediate broadcast of m (=amount indicated in the CBCH Load Information element) scheduled SMSCB messages in the underflow situation. BSC shall transmit m scheduled messages and after that continue the broadcast of messages according to its own timetable. If BTS requests more messages than BSC is possessing, then BSC shall transmit only the amount it is possessing. CBCH LOAD INDICATION mode of operation could only be applied when DRX mode is used (see 3GPP TS 44.012). + +![Sequence diagrams showing CBCH load indication and broadcast request/command messages between MS, BTS, and BSC.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram consists of two sequence diagrams illustrating the interaction between a Mobile Station (MS), a Base Transceiver Station (BTS), and a Base Station Controller (BSC). + +**Top Sequence Diagram:** + +- The MS sends a message labeled "CBCH block n" to the BTS. +- The BTS sends a "CBCH LOAD IND (underflow)" message to the BSC. +- The BSC responds with "SMS BROADCAST REQ 1", followed by vertical ellipsis dots, and then "SMS BROADCAST REQ m". + +**Bottom Sequence Diagram:** + +- The MS sends four messages labeled "CBCH block 1", "CBCH block 2", "CBCH block 3", and "CBCH block 4" to the BTS. +- The BTS sends a "CBCH LOAD IND (underflow)" message to the BSC. +- The BSC responds with "SMS BROADCAST CMD 1 (SMSCB message)", followed by vertical ellipsis dots, and then "SMS BROADCAST CMD m (SMSCB message)". + +Sequence diagrams showing CBCH load indication and broadcast request/command messages between MS, BTS, and BSC. + +With the CBCH LOAD INDICATION mode of operation, the BTS can also request immediate stop of broadcast for a period of m (=amount indicated in the CBCH Load Information element) message slots in the overflow situation. BSC shall stop the broadcast for a period of m message slots and after that continue the broadcast of messages according to its own timetable. + +![Sequence diagrams for CBCH message broadcasting showing message flows between MS, BTS, and BSC.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note over BTS,BSC: CBCH LOAD IND (overflow) + BSC->>BTS: + Note right of BTS: Period of m +message slots + Note right of BTS: . + Note right of BTS: . + Note over BTS,BSC: SMS BROADCAST REQ + BSC->>BTS: + Note over MS,BTS: CBCH block n + BTS->>MS: + +``` + + + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note over BTS,BSC: CBCH LOAD IND (overflow) + BSC->>BTS: + Note right of BTS: Period of m +message slots + Note right of BTS: . + Note right of BTS: . + Note over BTS,BSC: SMS BROADCAST CMD +(SMSCB message) + BSC->>BTS: + Note over MS,BTS: CBCH block 1 + BTS->>MS: + Note over MS,BTS: CBCH block 2 + BTS->>MS: + Note over MS,BTS: CBCH block 3 + BTS->>MS: + Note over MS,BTS: CBCH block 4 + BTS->>MS: + +``` + +Sequence diagrams for CBCH message broadcasting showing message flows between MS, BTS, and BSC. + +## 5.7 IMMEDIATE ASSIGNMENT + +This procedure is used by BSC to request the transmission of an immediate assign message on downlink CCCH. To initiate the immediate assign, the BSC sends an IMMEDIATE ASSIGN COMMAND message. The message contains the complete immediate assign message as defined in 3GPP TS 44.018 (IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT) with the "Page Mode" element set to the value "no change". Upon receipt of the message, the BTS may transmit the immediate assignment message as received or combine several to construct the IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT. The BTS may also update the "Page Mode" element before transmission. + +The IMMEDIATE ASSIGNMENT EXTENDED message is either sent by the BSC in the IMMEDIATE ASSIGN COMMAND, or built by the BTS from up to two IMMEDIATE ASSIGN COMMAND messages. + +The IMMEDIATE ASSIGNMENT REJECT message is either sent by the BTS as received in the IMMEDIATE ASSIGN COMMAND message or built by the BTS from the contents of two or more IMMEDIATE ASSIGN COMMAND messages. For the latter case the BTS may consider request references with identical contents within the same message as duplicates and all but one may be suppressed. + +![Sequence diagram for Immediate Assignment procedure.](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note over BTS,BSC: IMM ASS CMD + BSC->>BTS: + Note over MS,BTS: immediate assign +message + BTS->>MS: + +``` + +Sequence diagram for Immediate Assignment procedure. + +## 5.8 Notification + +This procedure is used to request that notification be performed by the BTS. The BSC indicates the exact action required by the BTS in the command indicator. + +The NOTIFication messages to be sent on the radio path are built and sent by BTS. + +The BSC manages the NCH DRX information whilst the BTS manages the scheduling of the messages on the NCH. + +![Sequence diagram showing the interaction between MS, BTS, and BSC for NCH DRX management. The BSC sends a VGCS ASSIG REQ to the BTS. The BTS responds with a NOTIF CMD. The BTS then builds and schedules the NOTIF message and sends it to the MS.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + Note right of BSC: VGCS ASSIG REQ + BSC->>BTS: NOTIF CMD + Note right of BTS: (build and schedule NOTIF) + BTS->>MS: NOTIF + +``` + +Sequence diagram showing the interaction between MS, BTS, and BSC for NCH DRX management. The BSC sends a VGCS ASSIG REQ to the BTS. The BTS responds with a NOTIF CMD. The BTS then builds and schedules the NOTIF message and sends it to the MS. + +If the BTS for some reason can not perform the notification commanded by the BSC, then the BTS shall return an ERROR REPORT message with the relevant cause value. + +![Sequence diagram showing the interaction between BTS and BSC when a notification command cannot be performed. The BSC sends a NOTIF CMD to the BTS. The BTS responds with an ERROR REPORT message.](6470d350326789d5306eabcb76533951_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BSC->>BTS: NOTIF CMD + BTS-->>BSC: ERROR REPORT + +``` + +Sequence diagram showing the interaction between BTS and BSC when a notification command cannot be performed. The BSC sends a NOTIF CMD to the BTS. The BTS responds with an ERROR REPORT message. + +# 6 TRX management procedures + +## 6.1 Radio resource indication + +This procedure is used to inform BSC on the interference levels on idle channels of a TRX. + +In the RF RESource INDication message, TRX reports the interference level for each of the channels which have been idle (not active) for the whole measurement period. See also 3GPP TS 48.008 and 3GPP TS 45.008. + +The RF RESource INDication message is sent regularly with a rate set by O&M. + +![Sequence diagram showing the periodic RF RESource INDication procedure. A period is set by O&M. The BTS performs interference measurements and sends an RF RES IND message to the BSC. This process repeats.](cad89c017c9e7c1785bcd104fde4e737_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note left of BTS: period set by O&M + Note right of BTS: (perform interf. measurements) + BTS->>BSC: RF RES IND + Note right of BTS: (perform interf. measurements) + BTS->>BSC: RF RES IND + +``` + +Sequence diagram showing the periodic RF RESource INDication procedure. A period is set by O&M. The BTS performs interference measurements and sends an RF RES IND message to the BSC. This process repeats. + +## 6.2 SACCH filling information modify + +This procedure is used by BSC to indicate to BTS the new information to be used as filling information on SACCHs. + +For that purpose BSC sends a SACCH FILLing message to BTS. + +![Sequence diagram showing the SACCH filling information modify procedure. The BSC sends a SACCH FILL message to the BTS.](26ffdb652c290cd6aaa80c34a917e718_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + BSC->>BTS: SACCH FILL + +``` + +Sequence diagram showing the SACCH filling information modify procedure. The BSC sends a SACCH FILL message to the BTS. + +## 6.3 Flow control + +This procedure is defined to give some degree of flow control. It can be used for TRX processor overload, downlink CCCH overload and ACCH overload. + +The algorithm used in BSC to control the traffic flow is as follows: + +Upon receipt of the first OVERLOAD message, BSC reduces the traffic by one step and starts timers T1 and T2. During T1 all OVERLOAD messages are ignored in order not to reduce the traffic too rapidly. Reception of an OVERLOAD message after T1 but still during T2 will decrease the traffic by one more step and timers T1 and T2 are restarted. This step by step reduction of traffic is continued until maximum reduction is obtained. + +If T2 expires (i.e. no OVERLOAD message was received during T2), the traffic will be increased by one step and T2 restarted. This step by step increase of traffic will be continued until full load has been resumed. + +The number of steps and the method of reducing the load is considered to be implementation dependent. For example, the amount of random accesses and thereby access grants can be reduced by use of the RACH Control parameters (e.g. Access Control Class or Cell Barred) or the Cell Selection parameters (e.g. CELL-RESELECT-HYSTERESIS or RXLEV- ACCESS-MIN) in the system information messages of 3GPP TS 44.018. + +![Sequence diagram showing OVERLOAD message handling between BTS and BSC. The diagram illustrates the state transitions of the BSC based on OVERLOAD messages received during timers T1 and T2.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note right of BSC: T1 T2 + BTS->>BSC: OVERLOAD + Note right of BSC: * decrease; restart T1+T2 + Note right of BSC: ignore + BTS->>BSC: OVERLOAD + Note right of BSC: * decrease; restart T1+T2 + Note right of BSC: ignore + Note right of BSC: --*--increase; restart T2 + Note right of BSC: increase; full load again + +``` + +Sequence diagram showing OVERLOAD message handling between BTS and BSC. The diagram illustrates the state transitions of the BSC based on OVERLOAD messages received during timers T1 and T2. + +## 6.4 Error reporting + +This procedure is used by BTS to report detected errors as described in clause 7 below if they cannot be reported by any other procedure. + +When TRX detects the reception of an erroneous message, it sends an ERROR REPORT message to BSC with the most appropriate cause value. In order to identify the erroneous message, the Message Type, the Channel Number, the Link Identifier and/or the complete erroneous message can be included. + +![Sequence diagram showing an ERROR REPORT message being sent from a BTS to a BSC.](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +``` + +sequenceDiagram + participant BTS + participant BSC + Note right of BTS: ERROR REPORT + BTS->>BSC: ERROR REPORT + +``` + +Sequence diagram showing an ERROR REPORT message being sent from a BTS to a BSC. + +# 6a Location services procedures + +These procedures are related to Location Services (LCS). + +## 6a.1 LLP message transport + +This procedure is used to convey LLP messages between the BTS-or Standalone Type B LMU and the BSC, as defined in the Location Services (LCS) Stage 2 document 3GPP TS 23.071. + +The sending entity (BSC, Standalone Type B LMU or BTS) sends a Location Information message containing an embedded LLP message to the receiving entity (BSC, Standalone Type B LMU or BTS). + +![Sequence diagram showing LOCATION INFORMATION messages between BTS or Standalone Type B LMU and BSC.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +A sequence diagram illustrating the exchange of LOCATION INFORMATION messages between a BTS or Standalone Type B LMU and a BSC. The diagram consists of two vertical lifelines. The left lifeline is labeled "BTS or Standalone Type B LMU" and the right lifeline is labeled "BSC". A horizontal arrow points from the left lifeline to the right lifeline, labeled "LOCATION INFORMATION". Below this arrow, the word "OR" is centered. Below "OR", another horizontal arrow points from the right lifeline to the left lifeline, also labeled "LOCATION INFORMATION". + +Sequence diagram showing LOCATION INFORMATION messages between BTS or Standalone Type B LMU and BSC. + +# 7 Error handling + +## 7.1 General + +The procedures specified above apply to those messages which pass the checks described below. + +The behaviour of BSC in erroneous cases is implementation dependent. + +The behaviour of BTS in erroneous cases is to ignore the message and to send a report to BSC. The report can be sent in either of the following messages: + +- CHANNEL ACTIVATION NACK in connection with channel activations; +- MODE MODIFY NACK in connection with a channel mode change; +- ERROR REPORT in other cases. + +For procedures controlled by the BSC, and in particular procedures where the BSC sends a request for resources at the BTS and waits for an acknowledge, the implementation in the BSC must provide means for avoiding deadlock situations at the BTS as e.g. hanging resources. + +## 7.2 Message discriminator error + +A message with a non-specified message discriminator is erroneous. + +## 7.3 Message type error + +A message with a non-specified message type is considered correct, but is ignored by BTS. + +## 7.4 Message sequence error + +A message with an existing message type which is not possible according to the specification and to the state of the BTS is erroneous. + +## 7.5 General information element errors + +This category includes: + +- Information element out of sequence; +- Abnormally duplicated element; +- Missing element. + +A message with such an error is erroneous. + +## 7.6 Mandatory information element errors + +This includes: + +- a) Non-existing element type. + +- b) Information length error. +- c) Content which does not comply with the specification (value reserved for future use is considered as case d)). +- d) Value indicated as reserved for future use. +- e) Bits reserved for future use not set to 0. +- f) Content complying with specification but incompatible with the state. +- g) Content complying with the specification but inconsistent. + +All cases except e) are considered erroneous. + +In case e), BTS simply ignores the reserved (RFU) bits. + +## 7.7 Optional information element errors + +The same categories of errors as in previous sub-clause apply. + +In cases other than b), e), f) and g), BTS ignores the element and processes the rest of the message. + +Cases b), f) and g) are considered erroneous. + +In case e), BTS ignores the reserved (RFU) bits. + +## 7.8 Conditional information element errors + +The same categories of errors as in sub-clause 7.6 apply. + +If the conditions for presence of the element are met, the same erroneous cases as in sub-clause 7.6 apply. + +If the conditions for presence of the element are not met, the same erroneous cases as in sub-clause 7.7 apply. + +# --- 8 Message formats and contents + +## 8.0 General + +This sub-clause defines the format and contents of the messages sent over the A-bis interface. Similar coding principles as in 3GPP TS 24.008 and 3GPP TS 48.008 are used. + +For each message, the contained Information Elements are listed. For each Information Element, the following information is given: + +- Name of Information Element; +- Reference sub-clause for the coding of the Information Element; +- Presence condition for the Information Element; + - M Mandatory, must always be present; +**receiver:** if not present, consider message erroneous; + - C Conditional, presence depending on e.g. + - a) value of other element; + - b) presence of optional element; +**receiver:** if not present when condition met, consider message erroneous, else accept message; + - O Optional, **receiver:** present or not, accept message; + +- Format of Information Element: + +T Type only, fixed length, only Element Identifier; + V Value only, fixed length, no Element Identifier included; + TV Type and Value, fixed length, Element Identifier included; + TLV Type, Length and Value, variable length, Element Identifier and Length Indicator included; + +- Total length of Information Element; for variable length, lower and upper limits. + +NOTE: Maximum message length is determined by the N201 parameter of 3GPP TS 48.056. + +In a message, the message discriminator is transmitted first. The purpose is to distinguish between transparent messages (T-bit set to 1) and non-transparent messages (T-bit set to 0) and also between messages related to Radio Link Layer Management, Dedicated Channel Management, Common Channel Management and TRX Management. The octets are sent in the order shown in the description of the messages and information elements. + +## 8.1 Transparent messages + +Transparent messages are used at the A-bis interface to convey layer 3 messages for the radio interface as defined in 3GPP TS 44.018 and for which BTS has to take or has taken no specific action. The T- bit of the Message Discriminator is set to 1. + +In the uplink direction (messages from MS), all messages received in I- frames and all messages received in UI-frames except for the MEASurement REPort message are considered as transparent. They are forwarded to BSC as DATA INDication and UNIT DATA INDication messages respectively. + +In the downlink direction (messages to MS) all messages as defined in 3GPP TS 44.018 are transparent except for the following messages, which are replaced by BSC-BTS specific messages over the A- bis interface and where BTS will send the corresponding L3 message over the radio interface after the necessary actions have been taken: + +| Message to MS | Replaced on A-bis interface by | +|----------------------------|------------------------------------| +| CIPHering MODE CoMmanD | ENCryption CoMmanD | +| PAGing REquest | PAGing CoMmanD | +| NOTIFication | NOTIFication CoMmanD | +| SYSTEM INFOrmation | BCCH INFOrmation and SACCH FILLing | +| EXTENDED MEASUREMENT ORDER | SACCH FILLing | +| Immediate assign (3 types) | IMMEDIATE ASSIGN COMMAND | + +Transparent messages are sent by BSC as DATA REquest or UNIT DATA REquest messages. + +## 8.2 Non-transparent messages (BSC-BTS specific messages) + +These messages are used over the A-bis interface for messages on which BTS has to take some action (BSC to BTS direction) and for messages which are the result from actions taken by BTS (BTS to BSC direction). The T-bit of the Message Discriminator is set to 0. + +## 8.3 Radio link layer management messages + +These messages are related to Radio Link Layer Management procedures. They all have the following general format: + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|--------------------------------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| (Information elements depending on message type) | | | | | + +The messages concerned are the following: + +| Message name | Reference sub-clause | +|----------------------|----------------------| +| DATA REquest | 8.3.1 | +| DATA INdication | 8.3.2 | +| ERROR INdication | 8.3.3 | +| ESTablish REquest | 8.3.4 | +| ESTablish CONFirm | 8.3.5 | +| ESTablish INdication | 8.3.6 | +| RELease REquest | 8.3.7 | +| RELease CONFirm | 8.3.8 | +| RELease INdication | 8.3.9 | +| UNIT DATA REquest | 8.3.10 | +| UNIT DATA INdication | 8.3.11 | + +### 8.3.1 DATA REQUEST + +This message is sent from BSC to BTS to request the sending of a message in acknowledged mode on a radio link layer connection. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| L3 Information | 9.3.11 | M | TLV | >=3 | + +### 8.3.2 DATA INDICATION + +This message is sent from BTS to BSC to indicate the reception of a message in acknowledged mode on a radio link layer connection. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| L3 Information | 9.3.11 | M | TLV | >=3 | + +### 8.3.3 ERROR INDICATION + +This message is sent from BTS to BSC to indicate an abnormal case for a radio link layer connection. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| RLM Cause | 9.3.22 | M | TLV | 2-4 | + +### 8.3.4 ESTABLISH REQUEST + +This message is sent from BSC to BTS to request the establishment of a multi-frame mode (acknowledged mode) link layer connection on the radio path. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | + +### 8.3.5 ESTABLISH CONFIRM + +This message is sent from BTS to BSC to confirm the establishment of a radio link layer connection in multi-frame (acknowledged) mode. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | + +### 8.3.6 ESTABLISH INDICATION + +This message is sent from BTS to BSC to indicate the establishment of a radio link layer connection in multi-frame mode, initiated by an MS. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|------------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| L3 Information | 9.3.11 | O (note 1) | TLV | 3-23 | + +NOTE 1: The L3 Information field is present only if the SABM frame contained a non-empty information field + +NOTE: The "establish mode" parameter appearing in 3GPP TS 44.006 is used only on the MS side. + +### 8.3.7 RELEASE REQUEST + +This message is sent from BSC to BTS to request the release of multi- frame mode of a radio link layer connection. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| Release Mode | 9.3.20 | M | TV | 2 | + +### 8.3.8 RELEASE CONFIRM + +This message is sent from BTS to BSC to confirm the release of multi- frame mode of a radio link layer connection. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | + +### 8.3.9 RELEASE INDICATION + +This message is sent from BTS to BSC to indicate the release of a radio link layer connection (initiated by MS). + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | + +### 8.3.10 UNIT DATA REQUEST + +This message is sent from BSC to BTS to request the sending of a message in unacknowledged mode on a radio link layer connection. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| L3 Information | 9.3.11 | M | TLV | 3-25 | + +### 8.3.11 UNIT DATA INDICATION + +This message is sent from BTS to BSC to indicate the reception of a message in unacknowledged mode on a radio link layer connection. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| L3 Information | 9.3.11 | M | TLV | 3-23 | + +## 8.4 DEDICATED CHANNEL MANAGEMENT MESSAGES + +These messages are related to Dedicated Channel Management procedures. They all have the following general format: + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|--------------------------------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| (Information elements depending on message type) | | | | | + +The messages concerned are the following: + +| Message name | Reference sub-clause | +|--------------------------------------|----------------------| +| CHANnel ACTIVation | 8.4.1 | +| CHANnel ACTIVation ACKnowledge | 8.4.2 | +| CHANnel ACTIVation Negative ACK | 8.4.3 | +| CONNection FAIlure INDication | 8.4.4 | +| DEACTIVATE SACCH | 8.4.5 | +| ENCRyption CoMmanD | 8.4.6 | +| HANDOver DETection | 8.4.7 | +| TALKER DETection | 8.4.21 | +| LISTENER DETection | 8.4.22 | +| MEASurement RESult | 8.4.8 | +| MODE MODIFY REQuest | 8.4.9 | +| MODE MODIFY ACKnowledge | 8.4.10 | +| MODE MODIFY Negative ACKnowledge | 8.4.11 | +| PHYsical CONTEXT REQuest | 8.4.12 | +| PHYsical CONTEXT CONFirm | 8.4.13 | +| RF CHANnel RElease | 8.4.14 | +| MS POWER CONTROL | 8.4.15 | +| BS POWER CONTROL | 8.4.16 | +| PREPROCecC CONFIGure | 8.4.17 | +| PREPROCessed MEASurement RESult | 8.4.18 | +| RF CHANnel RElease ACKnowledge | 8.4.19 | +| SACCH INFO MODIFY | 8.4.20 | +| REMOTE CODEC CONFIGuration REPort | 8.4.23 | +| Round Trip Delay REPort | 8.4.24 | +| PRE-HANDOver NOTIFication | 8.4.25 | +| MultiRate CODEC MODification REQuest | 8.4.26 | +| MultiRate CODEC MOD ACKnowledge | 8.4.27 | +| MultiRate CODEC MOD Negative ACK | 8.4.28 | +| MultiRate CODEC MOD PERformed | 8.4.29 | +| TFO REPort | 8.4.30 | +| TFO MODification REQuest | 8.4.31 | + +### 8.4.1 CHANNEL ACTIVATION + +This message is sent from BSC to BTS in order to activate a radio channel. The attributes of the channel are defined in the message. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|---------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Activation Type | 9.3.3 | M | TV | 2 | +| Channel Mode | 9.3.6 | M | TLV | 8-9 | +| Channel Identification | 9.3.5 | O 7) | TLV | 8 | +| Encryption information | 9.3.7 | O 1) | TLV | >=3 | +| Handover Reference | 9.3.9 | C 2) | TV | 2 | +| BS Power | 9.3.4 | O 3) | TV | 2 | +| MS Power | 9.3.13 | O 3) | TV | 2 | +| Timing Advance | 9.3.24 | C 3) 4) | TV | 2 | +| BS Power Parameters | 9.3.32 | O 5) | TLV | >=2 | +| MS Power Parameters | 9.3.31 | O 5) | TLV | >=2 | +| Physical Context | 9.3.16 | O 6) | TLV | >=2 | +| SACCH Information | 9.3.29 | O 8) | TLV | >=3 | +| UIC | 9.3.50 | O 9) | TLV | 3 | +| Main channel reference | 9.3.51 | O 10) | TV | 2 | +| MultiRate configuration | 9.3.52 | O 11) | TLV | >=4 | +| MultiRate Control | 9.3.53 | O 12) | TV | 2 | +| Supported Codec Types | 9.3.54 | O 12) | TLV | >=5 | +| TFO transparent container | 9.3.59 | O 12) | TLV | >=3 | + +- 1) The Encryption Information element is only included if ciphering is to be applied. +- 2) The Handover Reference element is only included if activation type is handover. +- 3) If BS Power, MS Power and/or Timing Advance elements are present, they are to be used to set the initial transmission power and the initial L1-header. +- 4) The Timing Advance element must be included if activation type is intra cell channel change. +- 5) The BS and MS Power Parameters elements are included to indicate that BS and/or MS power control is to be performed by BTS. The maximum power to be used is indicated in the BS and MS Power elements respectively. +- 6) Optional element for additional physical channel information. +- 7) Included if compatibility with phase1 is required. +- 8) Optional element for setting the SACCH filling information individually for this channel. If this element is present, the SACCH filling information as given by this element shall be used for this channel (replacing any SACCH filling information as given by the SACCH FILLING message(s)) until the channel is released or the information is changed by a SACCH INFO MODIFY message. (If this element is not present, the SACCH filling as given by the SACCH FILLING message(s) shall be used.) +- 9) The UIC element may be included for voice group calls. It is used in the same way as the BSIC for decoding the random access bursts when decoding uplink access bursts. If not included, the BSIC shall be used for decoding uplink access bursts. +- 10) Optional element for multislot operation, it may be used in case of power control in the BTS. +- 11) Included if the Channel Mode indicates that a multi-rate speech codec is used. +- 12) Optionally included if the Channel Mode indicates that a multi-rate speech codec is used and TFO control is required or to give to the BTS the possibility to change autonomously the multi-rate codec configuration. + +### 8.4.2 CHANNEL ACTIVATION ACKNOWLEDGE + +This message is sent from BSC to BTS to acknowledge that the requested channel activation has been completed correctly. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Frame number | 9.3.8 | M | TV | 3 | + +The Frame Number element is used by BSC to calculate the Starting Time parameter when required. + +### 8.4.3 CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE + +This message is sent from BTS to BSC to indicate that the channel activation could not be performed as requested. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Cause | 9.3.26 | M | TLV | >=3 | + +If the Channel Activation message was received with an erroneous Channel number information element, the Channel Activation Negative Acknowledge message is returned with the Channel Number information element equal to the received (and erroneous) Channel number and the Cause value "Mandatory Information Element Error" with Diagnostics equal to the Channel number element identifier value. + +### 8.4.4 CONNECTION FAILURE INDICATION + +This message is sent from BTS to BSC to indicate that an active connection has been broken for some reason. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Cause | 9.3.26 | M | TLV | >=3 | + +### 8.4.5 DEACTIVATE SACCH + +This message is sent from BSC to BTS in order to deactivate the SACCH of an active channel. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | + +### 8.4.6 ENCRYPTION COMMAND + +This message is sent from BSC to BTS to start ciphering mode operation. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Encryption information | 9.3.7 | M | TLV | >=3 | +| Link Identifier | 9.3.2 | M | TV | 2 | +| L3 Info (CIPH MOD CMD) | 9.3.11 | M | TLV | 6 | + +The L3 Info element contains the complete Ciphering Mode Command message as defined in 3GPP TS 44.018. + +### 8.4.7 HANDOVER DETECTION + +This message is sent from BTS to BSC when BTS correctly receives information from an MS on the handover activated channel. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Access Delay | 9.3.17 | O 1) | TV | 2 | + +- 1) The Access Delay element is included if the sending of the handover detection message was triggered by the reception of a handover access burst with the correct handover reference. + +### 8.4.8 MEASUREMENT RESULT + +This message from BTS to BSC is used to report to BSC the results of radio channel measurements made by BTS (uplink) and to convey the measurement reports from MS received on SACCH and in the L1 headers. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|--------------------------------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Measurement result number | 9.3.27 | M | TV | 2 | +| Uplink Measurements | 9.3.25 | M | TLV | >=5 | +| BS Power | 9.3.4 | M | TV | 2 | +| L1 Information | 9.3.10 | O 1) | TV | 3 | +| L3 Info (MEAS REP, EXT MEAS REP or ENH MEAS REP) | 9.3.11 | O 1) | TLV | 21 | +| MS Timing Offset | 9.3.37 | O 2) | TV | 2 | + +- 1) The L1 Information element contains the last received L1-header (MS Power and Timing Advance) from MS and the L3 Information element contains the complete MEASurement REPort message EXTended MEASurement REPort message or ENHanced MEASurement REPort message received from MS. They are included only if received since last (EXTended/ENHanced) MEASurement RESult message. +- 2) MS Timing Offset can be optionally included to increase the accuracy of possible distance measurements. + +### 8.4.9 MODE MODIFY + +This message is sent from BSC to BTS to request a change of channel mode of an active channel. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|---------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Channel Mode | 9.3.6 | M | TLV | 8-9 | +| Encryption information | 9.3.7 | O 1) | TLV | >=3 | +| Main channel reference | 9.3.45 | O 2) | TV | 2 | +| MultiRate configuration | 9.3.52 | O 3) | TLV | >=3 | +| Multirate Control | 9.3.53 | O 4) | TV | 2 | +| Supported Codec Types | 9.3.54 | O 4) | TLV | >=5 | +| TFO transparent container | 9.3.59 | O 4) | TLV | >=3 | + +- 1) The Encryption Information element is only included if ciphering is to be applied. +- 2) Optional element for multislot operation, it may be used in case of power control in the BTS. +- 3) Included if the Channel Mode indicates that a multi-rate speech codec is used. +- 4) Optionally included if the Channel Mode indicates that a multi-rate speech codec is used and TFO control is required or to give to the BTS the possibility to change autonomously the multi-rate codec configuration. + +### 8.4.10 MODE MODIFY ACKNOWLEDGE + +This message is sent from BTS to BSC to confirm the change of channel mode of an active channel. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | + +### 8.4.11 MODE MODIFY NEGATIVE ACKNOWLEDGE + +This message is sent from BTS to BSC to indicate that the channel mode modification could not be performed as requested. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Cause | 9.3.26 | M | TLV | >=3 | + +### 8.4.12 PHYSICAL CONTEXT REQUEST + +This message is sent from BSC to BTS to request the "physical context" of an active channel. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | + +### 8.4.13 PHYSICAL CONTEXT CONFIRM + +This message is sent from BTS to BSC as a response to a PHYSical CONTEXT REQuest message. The message contains the "physical context" information. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| BS Power | 9.3.4 | M | TV | 2 | +| MS Power | 9.3.13 | M | TV | 2 | +| Timing Advance | 9.3.24 | M | TV | 2 | +| Physical Context | 9.3.16 | O 1) | TLV | >=2 | + +- 1) Optional element for additional physical channel information. + +### 8.4.14 RF CHANNEL RELEASE + +This message is sent from BSC to BTS to inform that a radio channel is no longer needed. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | + +### 8.4.15 MS POWER CONTROL + +This message is sent from BSC to BTS to change the MS power level or the parameters used by TRX to control the MS power. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| MS Power | 9.3.13 | M | TV | 2 | +| MS Power Parameters | 9.3.31 | O 1) | TLV | >=2 | + +- 1) If the MS Power Parameters element is present it indicates that the MS power control is to be performed by TRX. The MS Power element then indicates the maximum MS power to be used. + +### 8.4.16 BS POWER CONTROL + +This message is sent from BSC to BTS to change the TRX transmission power level or the parameters used by TRX to control its transmission power. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| BS Power | 9.3.4 | M | TV | 2 | +| BS Power Parameters | 9.3.32 | O 1) | TLV | >=2 | + +- 1) If the BS Power Parameters element is present it indicates that the TRX transmission power control is to be performed by TRX. The BS Power element then indicates the maximum transmission power to be used. + +### 8.4.17 PREPROCESS CONFIGURE + +This message is sent from BSC to BTS to modify the pre-processing parameters used by BTS. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Preproc. Parameters | 9.3.33 | M | TLV | >=3 | + +### 8.4.18 PREPROCESSED MEASUREMENT RESULT + +This message is used by BTS to report the results of radio parameter pre-processing. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Preproc. Measurements | 9.3.34 | M | TLV | >=2 | + +### 8.4.19 RF CHANNEL RELEASE ACKNOWLEDGE + +This message is sent from BTS to BSC as an acknowledge to a RF CHANNEL RELEASE message. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | + +### 8.4.20 SACCH INFO MODIFY + +This message is sent from BSC to BTS to modify the SACCH filling information sent on an individual SACCH channel. This new SACCH filling information shall be sent on the indicated channel until the channel is released or the information is changed by another SACCH INFO MODIFY message. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| System Info Type | 9.3.30 | M | TV | 2 | +| L3 Info | 9.3.11 | O 1) | TLV | 22 | +| Starting Time | 9.3.23 | O 2) | TV | 3 | + +- 1) If the L3 Info information element is not included, this indicates that transmission of the indicated message shall be stopped, i.e. message shall no longer be sent on this channel. +- 2) The Starting Time element is optionally used to indicate when transmission of the new information is to start and when transmission is to stop. + +The System Info Type element indicates the type of SYSTEM INFORMATION/EXTENDED MEASUREMENT ORDER message which follows in the L3 Info field. + +The L3 Information element contains the relevant SYSTEM INFORMATION/EXTENDED MEASUREMENT ORDER message as defined in 3GPP TS 44.018. + +### 8.4.21 TALKER DETECTION + +This message is sent from BTS to BSC when BTS correctly receives on a channel activated for VGCS an access from an MS indicating that it requires the uplink of the channel. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Access Delay | 9.3.17 | O 1) | TV | 2 | + +- 1) The Access Delay element is included if the sending of the uplink access message was triggered by the reception of an uplink access burst with the correct values. + +### 8.4.22 LISTENER DETECTION + +This message is sent from BTS to BSC when BTS correctly receives on a channel activated for VGCS or VBS an access from an MS indicating its presence on the channel. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Access Delay | 9.3.17 | O 1) | TV | 2 | + +- 1) The Access Delay element is included if the sending of the uplink access message was triggered by the reception of an uplink access burst with the correct value. + +### 8.4.23 REMOTE CODEC CONFIGURATION REPORT + +This message is sent by the BTS to the BSC to report the codec information received from a remote BTS prior to TFO establishment or in TFO. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|---------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Codec Configuration | 9.3.55 | M | TLV | >=3 | +| Supported Codec Types | 9.3.54 | M | TLV | >=5 | +| TFO transparent container | 9.3.59 | O 4) | TLV | >=3 | + +### 8.4.24 ROUND TRIP DELAY REPORT + +This message is sent by the BSC to the BTS to report the computed round trip transmission delay between the BTS and the transcoder or between the BTS and the remote BTS when TFO is established. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Round Trip Delay | 9.3.56 | M | TV | 2 | + +### 8.4.25 PRE-HANDOVER NOTIFICATION + +This message is sent by the BSC to the serving BTS to notify the BTS that an handover is going to be performed. It is also sent by the BSC to the serving BTS if the announced handover has failed. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|---------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| MultiRateControl | 9.3.53 | M | TV | 2 | +| Codec Configuration | 9.3.55 | M | TLV | >=3 | +| TFO transparent container | 9.3.59 | O 4) | TLV | >=3 | + +### 8.4.26 MULTIRATE CODEC MODIFICATION REQUEST + +This message is sent by the BSC to the BTS to request and authorise the BTS to change the Multi-Rate codec configuration using inband signalling message exchange. + +It is also sent by the BTS to the BSC, in the case where the TC or the BTS runs the TFO algorithm, and the BSC is responsible for changing the codec configuration. In this case, it is not acknowledged by the BSC. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| MultiRate Configuration | 9.3.52 | O 1) | TLV | >=4 | + +- 1) Not included if the BTS can solve the codec mismatch for TFO establishment + +### 8.4.27 MULTIRATE CODEC MODIFICATION ACKNOWLEDGE + +This message is sent by the BTS to the BSC to acknowledge the performed change of the MultiRate Codec configuration, when it was requested by the BSC with the MultiRate CODEC MODification REquest message + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| MultiRate Configuration | 9.3.52 | O 1) | TLV | >=4 | + +### 8.4.28 MULTIRATE CODEC MODIFICATION NEGATIVE ACKNOWLEDGE + +This message is sent by the BTS to the BSC to report a failure to change the MultiRate Codec Configuration. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Cause | 9.3.26 | M | TLV | >=3 | + +### 8.4.29 MULTIRATE CODEC MODIFICATION PERFORMED + +This message is sent by the BTS to the BSC to inform the BSC of a performed change of the MultiRate Codec Configuration in case the BTS is generally authorised to perform this change and has initiated this on its own. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| MultiRate Configuration | 9.3.52 | M | TLV | >=4 | + +### 8.4.30 TFO REPORT + +This message is sent by the BTS to the BSC to inform the BSC that Tandem Free Operation with AMR is established, or is not established anymore. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| TFO Status | 9.3.57 | M | TV | 1 | + +### 8.4.31 TFO MODIFICATION REQUEST + +This message is sent by the BSC to the BTS to change the configuration of TFO while operating with AMR. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|---------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| MultiRateControl | 9.3.53 | M | TV | 2 | +| Supported Codec Type | 9.3.54 | O 1) | TLV | >=5 | +| TFO transparent container | 9.3.59 | O 4) | TLV | >=3 | + +- 1) Optionally included if TFO is enabled within I.E. MultiRateControl + +## 8.5 COMMON CHANNEL MANAGEMENT MESSAGES + +These messages are related to Common Channel Management procedures. They all have the following general format: + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|--------------------------------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| (Information elements depending on message type) | | | | | + +The messages concerned are the following: + +| Message name | Reference sub-clause | +|--------------------------|----------------------| +| BCCH INFORMATION | 8.5.1 | +| CCCH LOAD INDication | 8.5.2 | +| CHANnel ReQuireD | 8.5.3 | +| DELETE INDication | 8.5.4 | +| PAGING CoMmanD | 8.5.5 | +| NOTification CoMmanD | 8.5.10 | +| IMMEDIATE ASSIGN COMMAND | 8.5.6 | +| SMS BroadCast REquest | 8.5.7 | +| SMS Broadcast Command | 8.5.8 | +| CBCH LOAD INDICATION | 8.5.9 | + +### 8.5.1 BCCH INFORMATION + +This message is sent from BSC to BTS to indicate new information to be broadcast on BCCH. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|---------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| System Info Type | 9.3.30 | M | TV | 2 | +| Full BCCH Info (SYS INFO) | 9.3.39 | O 1) | TLV | 25 | +| Starting Time | 9.3.23 | O 2) | TV | 3 | + +- 1) If the Full BCCH information element is not included this indicates that transmission of the indicated SYSTEM INFORMATION message shall be stopped. +- 2) The Starting Time element is optionally used to indicate when transmission of the new information is to start or when transmission is to stop. + +The System Info Type element indicates the type of SYSTEM INFORMATION message which follows in the Full BCCH Information element. + +The Full BCCH Information element contains the relevant SYSTEM INFORMATION message as defined in 3GPP TS 44.018. + +### 8.5.2 CCCH LOAD INDICATION + +This message is sent from BTS to BSC to report the current load on the indicated CCCH timeslot (random access, RACH, and paging, PCH). + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number (note) | 9.3.1 | M | TV | 2 | +| RACH Load | 9.3.18 | C 1) | TLV | >=8 | +| Paging Load | 9.3.15 | C 2) | TV | 3 | + +NOTE: The BTS may set the "Channel Number" information element in this message to either the "uplink CCCH" or the "downlink CCCH" on that timeslot number. + +- 1) The RACH load information element is included only if the Channel number information indicates "uplink CCCH". +- 2) The Paging load information element is included only if the Channel number information indicates "downlink CCCH". + +### 8.5.3 CHANNEL REQUIRED + +This message is sent from BTS to BSC to indicate the reception of a CHANNEL REQUEST message (special access burst message) from an MS. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Request Reference | 9.3.19 | M | TV | 4 | +| Access Delay | 9.3.17 | M | TV | 2 | +| Physical Context | 9.3.16 | O 1) | TLV | >=2 | + +- 1) Optional element for additional physical channel information. + +The Request Reference element contains the random access reference value sent by MS in the CHANNEL REQUEST message and some low order bits of the absolute frame number for the reception of the access burst. + +### 8.5.4 DELETE INDICATION + +This message is sent from BTS to BSC to indicate the deletion of an access grant message (IMMediate ASSIGN) due to overload of downlink CCCH. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Full Imm. Assign Info | 9.3.35 | M | TLV | 25 | + +### 8.5.5 PAGING COMMAND + +This message is sent from BSC to BTS to request the paging of an MS. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Paging Group | 9.3.14 | M | TV | 2 | +| MS Identity | 9.3.12 | M | TLV | 2-10 | +| Channel Needed | 9.3.40 | O 1) | TV | 2 | +| eMLPP Priority | 9.3.49 | O 2) | TV | 2 | +| DRX Info | 9.3.60 | O | TV | 3 | + +- 1) If the Channel Needed element is not present, the default value is assumed to be 00 (any channel). +- 2) If the eMLPP Priority is not present then the BTS does not include the eMLPP priority in the radio interface message. + +The Paging Group element is used by BTS to calculate the correct DRX paging block to be used for the transmission of the PAGing REquest message as defined in 3GPP TS 45.002. + +When the eDRX Info element is included it is used instead of the Paging Group element to calculate the DRX paging block to be used for the transmission of the PAGing REquest message over the radio interface (see 3GPP TS 45.002 [8]). + +### 8.5.6 IMMEDIATE ASSIGN COMMAND + +This message is sent from BSC to BTS to request the transmission of an immediate assignment message. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Full Imm. Assign Info | 9.3.35 | M | TLV | 25 | + +The Full Imm. Assign Info element contains the relevant immediate assignment message as defined in 3GPP TS 44.018 (IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT) with the "Page Mode" element set to the value "no change". + +### 8.5.7 SMS BROADCAST REQUEST + +This message is sent from BSC to BTS to request the sending of a Short Message Service Cell Broadcast message. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| SMSCB Information | 9.3.36 | M | TV | 24 | +| SMSCB Channel Indicator | 9.3.44 | O 1) | TV | 2 | + +The SMSCB Information element contains the complete information to be broadcast on the CBCH as defined in 3GPP TS 44.012 (including the Layer 2 header to be used on the radio path). + +- 1) The SMSCB Channel Indicator IE indicates the CBCH which shall be used for broadcasting the data. If this information element is not present the basic CBCH (see 3GPP TS 45.002) shall be used. + +### 8.5.8 SMS BROADCAST COMMAND + +This message is sent from BSC to BTS to command Short Message Service Cell Broadcast. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| CB Command type | 9.3.4.1 | M | TV | 2 | +| SMSCB message | 9.3.4.2 | M | TLV | 2-90 | +| SMSCB Channel Indicator | 9.3.4.4 | O 1) | TV | 2 | + +The CB Command type IE contains the command to be performed, allowing the BSC to: + +- request immediate broadcast i.e. transmission in the next CBCH opportunity; +- set the BTS broadcast default mode. + +The SMSCB message IE contains the actual message to be broadcast on the CBCH i.e. a maximum of 88 octets of data. The BTS is responsible for performing the segmentation, building the block types and padding if necessary, see 3GPP TS 44.012 for the message format on the radio path. + +- 1) The SMSCB Channel Indicator IE indicates the CBCH which shall be used for broadcasting the data. If this information element is not present the basic CBCH [see 3GPP TS 45.002] shall be used. + +### 8.5.9 CBCH LOAD INDICATION + +This message is sent from BTS to BSC to indicate a CBCH underflow/overflow situation in the BTS and to request the BSC to accelerate or pause the cell broadcast for a period indicated by BTS. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| CBCH Load Information | 9.3.4.3 | M | TV | 2 | +| SMSCB Channel Indicator | 9.3.4.4 | O 1) | TV | 2 | + +The CBCH Load Information element indicates the load situation in CBCH (underflow/overflow) and information about the requested acceleration/suspension period of cell broadcast. + +- 1) The SMSCB Channel Indicator IE indicates the CBCH which shall be used for broadcasting the data. If this information element is not present the basic CBCH [see 3GPP TS 45.002] shall be used. + +### 8.5.10 NOTIFICATION COMMAND + +This message is sent from BSC to BTS to request a change of notification for voice group call. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Channel number | 9.3.1 | M | TV | 2 | +| Command indicator | 9.3.4.8 | M 1) | TLV | 3-4 | +| Group call reference | 9.3.4.5 | O | TLV | 7 | +| Channel Description | 9.3.4.6 | O | TLV | 3-n | +| NCH DRX information | 9.3.4.7 | O | TLV | 3 | + +- 1) This information element indicates the type of command that is to be performed by the BTS with respect to information contained in the rest of the message. + +## 8.6 TRX MANAGEMENT MESSAGES + +These messages are related to TRX Management procedures. They all have the following general format (no channel number included): + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|--------------------------------------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| (Information elements depending on message type) | | | | | + +The messages concerned are the following: + +| Message name | Reference sub-clause | +|------------------------|----------------------| +| RF RESource INDication | 8.6.1 | +| SACCH FILLing | 8.6.2 | +| OVERLOAD | 8.6.3 | +| ERROR REPORT | 8.6.4 | + +### 8.6.1 RF RESOURCE INDICATION + +This message is sent from BTS to BSC to indicate the interference level on idle channels of a TRX. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Resource Information | 9.3.21 | M | TLV | >=2 | + +### 8.6.2 SACCH FILLING + +This message is sent from BSC to BTS to indicate the new broadcast information to be used as filling information on downlink SACCH. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| System Info Type | 9.3.30 | M | TV | 2 | +| L3 Info (SYS INFO) | 9.3.11 | O 1) | TLV | 22 | +| Starting Time | 9.3.23 | O 2) | TV | 3 | + +- 1) If the L3 Info information element is not included this indicates that transmission of the indicated SYSTEM INFORMATION message shall be stopped. +- 2) The Starting Time element is optionally used to indicate when transmission of the new information is to start and when transmission is to stop. + +The System Info Type element indicates the type of SYSTEM INFORMATION message which follows in the L3 Info field. + +The L3 Information element contains the relevant SYSTEM INFORMATION message as defined in 3GPP TS 44.018. + +### 8.6.3 OVERLOAD + +This message is sent from BTS to BSC to indicate an overload situation. Possible cause values include: + +- CCCH overload; +- ACCH overload; + +- processor overload. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Cause | 9.3.26 | M | TLV | >=3 | + +### 8.6.4 ERROR REPORT + +This message is sent from BTS to BSC to report a detected error which cannot be reported in any other message. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| Cause | 9.3.26 | M | TLV | >=3 | +| Message Identifier | 9.3.28 | O 1) | TV | 2 | +| Channel Number | 9.3.1 | O 2) | TV | 2 | +| Link identifier | 9.3.2 | O 3) | TV | 2 | +| Erroneous Message | 9.3.38 | O 4) | TLV | >=3 | + +- 1) Used to indicate which type of message was considered erroneous. +- 2) Used to indicate for which radio channel the error is reported. +- 3) Used to indicate for which radio L2 link the error is reported. +- 4) This element may be used to carry the complete erroneous message as it was received from the BSC. + +## 8.7 LOCATION SERVICES MESSAGES + +These messages are related to Location Services (LCS). + +### 8.7.1 LOCATION INFORMATION + +This message is sent by the BSC, the BTS or Sandalone Type B LMU via Abis interface to convey an embedded LCS LLP message. + +| INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH | +|-----------------------|-----------|----------|--------|--------| +| Message discriminator | 9.1 | M | V | 1 | +| Message type | 9.2 | M | V | 1 | +| LLP APDU | 9.3.58 | M | LV | 2-N | + +# 9 Information element codings + +This sub-clause contains the codings of the signalling elements used. The following conventions are assumed for the sequence of transmission of bits and bytes: + +- Each bit position is numbered as 1 to 8. + +| | | | | | | | | +|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---|---|---|---|---|---|---|---| + +- The least significant bit is bit 1 and is transmitted first, followed by bits 2, 3, 4 etc. +- In an element, octets are identified by number. Octet 1 is transmitted first, then octet 2 etc. +- When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. +- For variable length elements, a length indicator is included. This indicates the number of octets following in the element. +- All spare or reserved bits are set to 0. + +## 9.1 Message discriminator + +A 1 octet field is used in all messages to discriminate between Transparent and Non-Transparent messages and also between Radio Link Layer Management, Dedicated Channel Management, Common Channel Management, TRX Management and Location Services messages. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----|----|----|----|----|----|----|---| +| G7 | G6 | G5 | G4 | G3 | G2 | G1 | T | + +The T-bit is set to 1 to indicate that the message is to be/was considered transparent by BTS. All other messages shall have the T-bit set to 0. + +The G-bits are used to group the messages as follows: + +| G7 | G6 | G5 | G4 | G3 | G2 | G1 | Message Group | +|----|----|----|----|----|----|----|---------------------------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | reserved | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | Radio Link Layer Management messages | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | Dedicated Channel Management messages | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | Common Channel Management messages | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | TRX Management messages | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | Location Services messages | + +All other values are reserved for future use. + +## 9.2 MESSAGE TYPE + +The Message Type uniquely identifies the function of the message being sent. It is a single octet and coded in the following way: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----|--------------|---|---|---|---|---|---| +| EM | Message type | | | | | | | + +Bit 8 is the extension bit and is reserved for future use. The following message types are used (all other values are reserved): + +| 8 7 6 5 4 3 2 1 | Message | Reference | +|------------------------|-----------------------------------------------------------|-----------| +| 0 0 0 0 - - - - | Radio Link Layer Management messages: | | +| 0 0 0 1 | - DATA REQuest | 8.3.1 | +| 0 0 1 0 | - DATA INDication | 8.3.2 | +| 0 0 1 1 | - ERROR INDication | 8.3.3 | +| 0 1 0 0 | - ESTablish REQuest | 8.3.4 | +| 0 1 0 1 | - ESTablish CONFirm | 8.3.5 | +| 0 1 1 0 | - ESTablish INDication | 8.3.6 | +| 0 1 1 1 | - RELease REQuest | 8.3.7 | +| 1 0 0 0 | - RELease CONFirm | 8.3.8 | +| 1 0 0 1 | - RELease INDication | 8.3.9 | +| 1 0 1 0 | - UNIT DATA REQuest | 8.3.10 | +| 1 0 1 1 | - UNIT DATA INDication | 8.3.11 | +| 0 0 0 1 - - - - | Common Channel Management/TRX Management messages: | | +| 0 0 0 1 | - BCCH INFormation | 8.5.1 | +| 0 0 1 0 | - CCCH LOAD INDication | 8.5.2 | +| 0 0 1 1 | - CHANnel ReRequireD | 8.5.3 | +| 0 1 0 0 | - DELETE INDication | 8.5.4 | +| 0 1 0 1 | - PAGING CoMmanD | 8.5.5 | +| 0 1 1 0 | - IMMEDIATE ASSIGN COMMAND | 8.5.6 | +| 0 1 1 1 | - SMS BroadCast REQuest | 8.5.7 | +| 1 0 0 1 | - RF RESource INDication | 8.6.1 | + +| | | | +|---------|-------------------------|--------| +| 1 0 1 0 | - SACCH FILLing | 8.6.2 | +| 1 0 1 1 | - OVERLOAD | 8.6.3 | +| 1 1 0 0 | - ERROR REPORT | 8.6.4 | +| 1 1 0 1 | - SMS BroadCast CoMmanD | 8.5.8 | +| 1 1 1 0 | - CBCH LOAD INDication | 8.5.9 | +| 1 1 1 1 | - NOTification CoMmanD | 8.5.10 | + +### **0 0 1 - - - - -      Dedicated Channel Management messages:** + +| | | | +|-----------|--------------------------------------------|--------| +| 0 0 0 0 1 | - CHANnel ACTIVation | 8.4.1 | +| 0 0 0 1 0 | - CHANnel ACTIVation ACKnowledge | 8.4.2 | +| 0 0 0 1 1 | - CHANnel ACTIVation Negative ACK | 8.4.3 | +| 0 0 1 0 0 | - CONNection FAILure | 8.4.4 | +| 0 0 1 0 1 | - DEACTIVATE SACCH | 8.4.5 | +| 0 0 1 1 0 | - ENCRyption CoMmanD | 8.4.6 | +| 0 0 1 1 1 | - HANDOver DETection | 8.4.7 | +| 0 1 0 0 0 | - MEASurement RESult | 8.4.8 | +| 0 1 0 0 1 | - MODE MODIFY REQuest | 8.4.9 | +| 0 1 0 1 0 | - MODE MODIFY ACKnowledge | 8.4.10 | +| 0 1 0 1 1 | - MODE MODIFY Negative ACKnowledge | 8.4.11 | +| 0 1 1 0 0 | - PHYsical CONTEXT REQuest | 8.4.12 | +| 0 1 1 0 1 | - PHYsical CONTEXT CONFirm | 8.4.13 | +| 0 1 1 1 0 | - RF CHANnel RELease | 8.4.14 | +| 0 1 1 1 1 | - MS POWER CONTROL | 8.4.15 | +| 1 0 0 0 0 | - BS POWER CONTROL | 8.4.16 | +| 1 0 0 0 1 | - PREPROCess CONFIGure | 8.4.17 | +| 1 0 0 1 0 | - PREPROCessed MEASurement RESult | 8.4.18 | +| 1 0 0 1 1 | - RF CHANnel RELease ACKnowledge | 8.4.19 | +| 1 0 1 0 0 | - SACCH INFO MODIFY | 8.4.20 | +| 1 0 1 0 1 | - TALKER DETection | 8.4.21 | +| 1 0 1 1 0 | - LISTENER DETection | 8.4.22 | +| 1 0 1 1 1 | - REMOTE CODEC CONFIGuration REPort | 8.4.23 | +| 1 1 0 0 0 | - Round Trip Delay REPort | 8.4.24 | +| 1 1 0 0 1 | - PRE-HANDOver NOTification | 8.4.25 | +| 1 1 0 1 0 | - MultiRate CODEC MODification REQuest | 8.4.26 | +| 1 1 0 1 1 | - MultiRate CODEC MOD ACKnowledge | 8.4.27 | +| 1 1 1 0 0 | - MultiRate CODEC MOD Negative ACKnowledge | 8.4.28 | +| 1 1 1 0 1 | - MultiRate CODEC MOD PERformed | 8.4.29 | +| 1 1 1 1 0 | - TFO REPort | 8.4.30 | +| 1 1 1 1 1 | - TFO MODification REQuest | 8.4.31 | + +### **0 1 - - - - -      Location Services messages:** + +| | | | +|-------------|------------------------|-------| +| 0 0 0 0 0 1 | - Location Information | 8.7.1 | +|-------------|------------------------|-------| + +## 9.3 Other information elements + +The information elements used and the coding of their Element Identifier fields are: + +| Element
Identifier bits
8 7 6 5 4 3 2 1 | Element name | Reference | +|-----------------------------------------------|------------------------|-----------| +| 0 0 0 0 0 0 0 1 | Channel Number | 9.3.1 | +| 0 0 0 0 0 0 1 0 | Link Identifier | 9.3.2 | +| 0 0 0 0 0 0 1 1 | Activation Type | 9.3.3 | +| 0 0 0 0 0 1 0 0 | BS Power | 9.3.4 | +| 0 0 0 0 0 1 0 1 | Channel Identification | 9.3.5 | +| 0 0 0 0 0 1 1 0 | Channel Mode | 9.3.6 | +| 0 0 0 0 0 1 1 1 | Encryption Information | 9.3.7 | +| 0 0 0 0 1 0 0 0 | Frame Number | 9.3.8 | +| 0 0 0 0 1 0 0 1 | Handover Reference | 9.3.9 | +| 0 0 0 0 1 0 1 0 | L1 Information | 9.3.10 | + +| | | | +|-----------------|----------------------------|--------| +| 0 0 0 0 1 0 1 1 | L3 Information | 9.3.11 | +| 0 0 0 0 1 1 0 0 | MS Identity | 9.3.12 | +| 0 0 0 0 1 1 0 1 | MS Power | 9.3.13 | +| 0 0 0 0 1 1 1 0 | Paging Group | 9.3.14 | +| 0 0 0 0 1 1 1 1 | Paging Load | 9.3.15 | +| 0 0 0 1 0 0 0 0 | Physical Context | 9.3.16 | +| 0 0 0 1 0 0 0 1 | Access Delay | 9.3.17 | +| 0 0 0 1 0 0 1 0 | RACH Load | 9.3.18 | +| 0 0 0 1 0 0 1 1 | Request Reference | 9.3.19 | +| 0 0 0 1 0 1 0 0 | Release Mode | 9.3.20 | +| 0 0 0 1 0 1 0 1 | Resource Information | 9.3.21 | +| 0 0 0 1 0 1 1 0 | RLM Cause | 9.3.22 | +| 0 0 0 1 0 1 1 1 | Starting Time | 9.3.23 | +| 0 0 0 1 1 0 0 0 | Timing Advance | 9.3.24 | +| 0 0 0 1 1 0 0 1 | Uplink Measurements | 9.3.25 | +| 0 0 0 1 1 0 1 0 | Cause | 9.3.26 | +| 0 0 0 1 1 0 1 1 | Measurement result number | 9.3.27 | +| 0 0 0 1 1 1 0 0 | Message Identifier | 9.3.28 | +| 0 0 0 1 1 1 0 1 | reserved | | +| 0 0 0 1 1 1 1 0 | System Info Type | 9.3.30 | +| 0 0 0 1 1 1 1 1 | MS Power Parameters | 9.3.31 | +| 0 0 1 0 0 0 0 0 | BS Power Parameters | 9.3.32 | +| 0 0 1 0 0 0 0 1 | Pre-processing Parameters | 9.3.33 | +| 0 0 1 0 0 0 1 0 | Pre-processed Measurements | 9.3.34 | +| 0 0 1 0 0 0 1 1 | reserved | | +| 0 0 1 0 0 1 0 0 | SMSCB Information | 9.3.36 | +| 0 0 1 0 0 1 0 1 | MS Timing Offset | 9.3.37 | +| 0 0 1 0 0 1 1 0 | Erroneous Message | 9.3.38 | +| 0 0 1 0 0 1 1 1 | Full BCCH Information | 9.3.39 | +| 0 0 1 0 1 0 0 0 | Channel Needed | 9.3.40 | +| 0 0 1 0 1 0 0 1 | CB Command type | 9.3.41 | +| 0 0 1 0 1 0 1 0 | SMSCB message | 9.3.42 | +| 0 0 1 0 1 0 1 1 | Full Immediate Assign Info | 9.3.35 | +| 0 0 1 0 1 1 0 0 | SACCH Information | 9.3.29 | +| 0 0 1 0 1 1 0 1 | CBCH Load Information | 9.3.43 | + +### **Element** + +### **Identifier bits** + +#### **8 7 6 5 4 3 2 1** + +### **Element name** + +### **Reference** + +| | | | +|-----------------|---------------------------|--------| +| 0 0 1 0 1 1 1 0 | SMSCB Channel Indicator | 9.3.44 | +| 0 0 1 0 1 1 1 1 | Group call reference | 9.3.45 | +| 0 0 1 1 0 0 0 0 | Channel description | 9.3.46 | +| 0 0 1 1 0 0 0 1 | NCH DRX information | 9.3.47 | +| 0 0 1 1 0 0 1 0 | Command indicator | 9.3.48 | +| 0 0 1 1 0 0 1 1 | eMLPP Priority | 9.3.49 | +| 0 0 1 1 0 1 0 0 | UIC | 9.3.50 | +| 0 0 1 1 0 1 0 1 | Main channel reference | 9.3.51 | +| 0 0 1 1 0 1 1 0 | MultiRate configuration | 9.3.52 | +| 0 0 1 1 0 1 1 1 | MultiRate Control | 9.3.53 | +| 0 0 1 1 1 0 0 0 | Supported Codec Types | 9.3.54 | +| 0 0 1 1 1 0 0 1 | Codec Configuration | 9.3.55 | +| 0 0 1 1 1 0 1 0 | Round Trip Delay | 9.3.56 | +| 0 0 1 1 1 0 1 1 | TFO Status | 9.3.57 | +| 0 0 1 1 1 1 0 0 | LLP APDU | 9.3.58 | +| 0 0 1 1 1 1 0 1 | TFO transparent container | 9.3.59 | +| 0 0 1 1 1 1 1 0 | Paging Group Extension | 9.3.60 | +| 0 0 1 1 1 1 1 1 | Reserved for future use | | +| to | | | +| 1 1 1 0 1 1 1 1 | | | + +1 1 1 1 0 0 0 0 + +to + +Not used + +1 1 1 1 1 1 1 1 + +### 9.3.1 Channel Number + +In the direction BSC to BTS the Channel Number parameter is used to indicate on which physical channel/subchannel the message is to be sent. In the direction BTS to BSC the Channel Number indicates on which physical channel/subchannel the message was received. It is coded in two octets as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|----|----|----|----|----|---|---|---| +| Element identifier | | | | | | | | 1 | +| C5 | C4 | C3 | C2 | C1 | TN | | | 2 | + +The C-bits describe the channel as follows: + +| C5 | C4 | C3 | C2 | C1 | | +|----|----|----|----|----|----------------------------| +| 0 | 0 | 0 | 0 | 1 | Bm + ACCH's | +| 0 | 0 | 0 | 1 | T | Lm + ACCH's | +| 0 | 0 | 1 | T | T | SDCCH/4 + ACCH | +| 0 | 1 | T | T | T | SDCCH/8 + ACCH | +| 1 | 0 | 0 | 0 | 0 | BCCH | +| 1 | 0 | 0 | 0 | 1 | Uplink CCCH (RACH) | +| 1 | 0 | 0 | 1 | 0 | Downlink CCCH (PCH + AGCH) | + +The T-bits indicate, coded in binary, the sub-channel number as specified in 3GPP TS 45.002. + +TN is time slot number, binary represented as in 3GPP TS 45.002. + +### 9.3.2 Link Identifier + +This element identifies the signalling channel and SAPI of the radio data link. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|----|----|----------|---|------|---|---|---| +| Element identifier | | | | | | | | 1 | +| C2 | C1 | NA | priority | | SAPI | | | 2 | + +The NA bit (bit 6 in octet 2) is set to 1 to indicate that the Link Identifier is not applicable for this message. In all other cases it is set to 0. + +The C-bits indicate the channel type as follows: + +| C2 | C1 | | +|----|----|------------------------------------------| +| 0 | 0 | main signalling channel (FACCH or SDCCH) | +| 0 | 1 | SACCH | + +All other values are reserved for future use. + +The SAPI field contains the SAPI value as defined in 3GPP TS 44.005. + +The priority field contains the message priority for SAPI 0, as defined in 3GPP TS 44.006, as follows: + +0 0 normal priority + +0 1 high priority + +1 0 low priority + +All other values for SAPI 0 and all values for other SAPIs are reserved for future use. + +### 9.3.3 Activation Type + +This element is used to indicate the type of activation requested in the CHANNEL ACTIVATION message. It is coded in two octets as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|----------|---|---|---|----|----|----|---| +| Element identifier | | | | | | | | 1 | +| R | Reserved | | | | A3 | A2 | A1 | 2 | + +The R bit indicates if the procedure is an initial activation or a reactivation. + +| R | | +|---|--------------------| +| 0 | Initial activation | +| 1 | Reactivation | + +The A-bits indicate the type of activation, which defines the access procedure and the operation of the data link layer, as follows: + +#### A3 A2 A1 + +- | | | | | +|---|---|---|------------------------------------------------------------| +| 0 | 0 | - | Activation related to intra-cell channel change | +| | | 0 | - related to immediate assignment procedure | +| | | 1 | - related to normal assignment procedure | +| 0 | 1 | - | Activation related to inter-cell channel change (handover) | +| | | 0 | - related to asynchronous handover procedure | +| | | 1 | - related to synchronous handover procedure | +| 1 | 0 | - | Activation related to secondary channels | +| | | 0 | - related to additional assignment procedure | +| | | 1 | - related to multislot configuration | + +All other values reserved for future use. + +NOTE: For the main TCH channel in a Multislot configuration activation types for intra-cell and inter-cell channel change are used. + +### 9.3.4 BS Power + +This information element indicates the TRX transmission power level and the use of fast power control and enhanced power control on a particular channel. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|----------|----------|-------------|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Reserved | | EPC mode | FPC_E PC | Power Level | | | | 2 | + +The EPC mode field (octet 2) indicates whether the activated channel shall be in enhanced power control (EPC) mode. It is only valid for channels on which EPC may be used. It is coded as follows: + +#### Value + +- 0 Channel not in EPC mode +- 1 Channel in EPC mode + +NOTE: The EPC mode field is only valid in the CHANNEL ACTIVATION message. + +The FPC\_EPC (Fast Power Control/Enhanced Power Control) field (octet 2) has different interpretation depending on the channel mode of the channel and whether the channel is in EPC mode. + +If the channel mode is such that FPC may be used, the FPC\_EPC field indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: + +#### Value + +- 0 Fast Power Control not in use +- 1 Fast Power Control in use + +If the channel is in EPC mode, the FPC\_EPC field indicates whether EPC procedures are used for BS (downlink) power control. It is coded as follows: + +#### Value + +- 0 EPC not in use for BS power control +- 1 EPC in use for BS power control + +If the channel mode is such that FPC may not be used and the channel is not in EPC mode, the BTS shall ignore the value of the FPC\_EPC field and the BSC shall set its value to 0. + +The Power Level field (octet 2) indicates the number of 2 dB steps by which the power shall be reduced from its nominal value, Pn, set by the network operator to adjust the coverage. Thus the Power Level values correspond to the following powers (relative to Pn): + +| Value | Power level | +|-----------------------------------------------|-------------| +| 0 0 0 0 0 | Pn | +| 0 0 0 0 1 | Pn - 2 dB | +| 0 0 0 1 0 | Pn - 4 dB | +| . | | +| . | | +| 0 1 1 1 0 | Pn - 28 dB | +| 0 1 1 1 1 | Pn - 30 dB | +| All other values are reserved for future use. | | + +See also 3GPP TS 45.005 and 3GPP TS 45.008. + +### 9.3.5 Channel Identification + +This information element describes some aspects of a channel together with its SACCH. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| 3GPP TS 44.018 "Channel Description" | | | | | | | | * | +| 3GPP TS 44.018 "Mobile Allocation" | | | | | | | | * | + +A \* denotes that the whole of the 3GPP TS 44.018 element including the element identifier and length should be included. The 3GPP TS 24.008 "Mobile Allocation" shall for compatibility reasons be included but empty, i.e. the length shall be zero. + +### 9.3.6 Channel Mode + +This element gives information on the mode of coding/decoding and transcoding/rate adaption of a channel. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------|---|---|---|---|---|------|------|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Reserved for future use | | | | | | DTXd | DTXu | 3 | +| Speech or data indicator | | | | | | | | 4 | +| Channel rate and type | | | | | | | | 5 | +| Speech coding algor./data rate + transp ind | | | | | | | | 6 | + +The DTX bits of octet 3 indicate whether DTX is applied: + +- 1 DTX is applied + +0 DTX is not applied. + +DTXd indicates use of DTX in the downlink direction (BTS to MS) and DTXu indicates use of DTX in the uplink direction (MS to BTS). + +The "Speech or data indicator" field (octet 4) is coded as follows: + +| | | +|-----------|------------| +| 0000 0001 | Speech | +| 0000 0010 | Data | +| 0000 0011 | Signalling | + +All other values are reserved. + +The "Channel rate and type" field (octet 5) is coded as follows: + +| | | +|--------------------------------|----------------------------------------------------------------------------| +| 0000 0001 | SDCCH | +| 0000 1000 | Full rate TCH channel Bm | +| 0000 1001 | Half rate TCH channel Lm | +| 0000 1010 | Full rate TCH channel bi-directional Bm, Multislot configuration | +| 0001 1010 | Full rate TCH channel uni-directional downlink Bm, Multislot configuration | +| 0001 1000 | Full rate TCH channel Bm Group call channel | +| 0001 1001 | Half rate TCH channel Lm Group call channel | +| 0010 1000 | Full rate TCH channel Bm Broadcast call channel | +| 0010 1001 | Half rate TCH channel Lm Broadcast call channel | +| All other values are reserved. | | + +The "speech coding algorithm/data rate + transparency indicator" field (octet 6) is coded as follows: + +If octet 4 indicates speech, then octet 6 is coded as follows: + +| | | +|--------------------------------|---------------------------------------| +| 0000 0001 | GSM speech coding algorithm version 1 | +| 0001 0001 | GSM speech coding algorithm version 2 | +| 0010 0001 | GSM speech coding algorithm version 3 | +| 0011 0001 | GSM speech coding algorithm version 4 | +| 0000 1001 | GSM speech coding algorithm version 5 | +| 0000 1101 | GSM speech coding algorithm version 6 | +| All other values are reserved. | | + +If octet 4 indicates signalling then octet 6 is coded as follows: + +0000 0000 No resources required + +All other values are reserved. + +NOTE: the GSM speech coding algorithm versions are also referred as follows (see 3GPP TS 26.103 [18]): + +- GSM speech coding algorithm version 1: GSM FR or GSM HR +- GSM speech coding algorithm version 2: GSM EFR (half rate not defined in this version of the protocol) +- GSM speech coding algorithm version 3: FR AMR or HR AMR +- GSM speech coding algorithm version 4: OFR AMR-WB or OHR AMR-WB +- GSM speech coding algorithm version 5: FR AMR-WB +- GSM speech coding algorithm version 6: OHR AMR + +If octet 4 indicates data, then octet 6 is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|------|---|---|---|---|---|---|---------| +| ext | T/NT | | | | | | | octet 6 | + +Bit 8: Reserved for extension + +Bit 7: 0 Transparent service + +1 Non-transparent service. + +For the non-transparent service, bits 6 to 1 indicate the radio interface data rate: + +| | | +|--------------------------------|----------------------------------------------------------| +| 65 4321 | | +| 10 0001 | asymmetric 43.5 kbit/s (downlink) + 14.5 kbit/s (uplink) | +| 10 0010 | asymmetric 29.0 kbit/s (downlink) + 14.5 kbit/s (uplink) | +| 10 0011 | asymmetric 43.5 kbit/s (downlink) + 29.0 kbit/s (uplink) | +| 10 1001 | asymmetric 14.5 kbit/s (downlink) + 43.5 kbit/s (uplink) | +| 10 1010 | asymmetric 14.5 kbit/s (downlink) + 29.0 kbit/s (uplink) | +| 10 1011 | asymmetric 29.0 kbit/s (downlink) + 43.5 kbit/s (uplink) | +| 11 0100 | 43.5 kbit/s | +| 11 0001 | 28.8 kbit/s | +| 01 1000 | 14.5 kbit/s | +| 01 0000 | 12 kbit/s | +| 01 0001 | 6 kbit/s | +| all other values are reserved. | | + +For the transparent service, bits 6-1 indicate the data rate: + +| | | +|--------------------------------|--------------------------------------------------------| +| 65 4321 | | +| 11 1000 | 32 kbit/s | +| 11 1001 | 29 kbit/s | +| 01 1000 | 14.4 kbit/s | +| 01 0000 | 9.6 kbit/s | +| 01 0001 | 4.8 kbit/s | +| 01 0010 | 2.4 kbit/s | +| 01 0011 | 1.2 kbit/s | +| 01 0100 | 600 bit/s | +| 01 0101 | 1 200/75 bit/s (1 200 network-to-MS, 75 MS-to-network) | +| All other values are reserved. | | + +### 9.3.7 Encryption information + +This element is a variable length element. It contains necessary information to control encryption devices. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Algorithm identifier | | | | | | | | 3 | +| Key | | | | | | | | 4 | +| | | | | | | | | n | + +The Algorithm Identifier field (octet 3) indicates the relevant ciphering algorithm. It is coded as: + +| 0000 0000 | Reserved | +|-------------------------------|-------------------------------------------| +| 0000 0001 | No encryption shall be used. | +| 0000 0010 | GSM encryption algorithm version 1 (A5/1) | +| 0000 0011 | GSM A5/2 | +| 0000 0100 | GSM A5/3 | +| 0000 0101 | GSM A5/4 | +| 0000 0110 | GSM A5/5 | +| 0000 0111 | GSM A5/6 | +| 0000 1000 | GSM A5/7 | +| All other values are reserved | | + +The Key field (octets 4-n) indicates the ciphering key. It shall be an integral number of octets and the length is given as the value of the Length field minus 1. + +### 9.3.8 Frame Number + +This element contains the absolute frame number (FN) modulo 42432. It is used to carry the current timing in BTS to BSC for calculation of the Starting Time parameter required in some messages. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-----------|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| T1' | | | | T3 (high) | | | | 2 | +| T3 (low) | | | | T2 | | | | 3 | + +Octets 2-3 are coded as defined for octets 2-3 of the Starting Time information element of 3GPP TS 44.018. + +### 9.3.9 Handover reference + +The information is coded in two octets and contains the hand-over reference value. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Hand-over reference | | | | | | | | 2 | + +The Handover Reference octet contains the handover reference value as defined in 3GPP TS 44.018. + +### 9.3.10 L1 Information + +This element carries the information used in the L1 header of SACCH blocks. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|-----------------------|---|---|-----|---|-----|---|----------|---|---| +| Element identifier | | | | | | | | 1 | | +| Actual MS power level | | | FPC | | SRR | | Reserved | | 2 | +| Actual Timing Advance | | | | | | | | 3 | | + +Octets 2-3 contain the L1 header information of SACCH blocks. The information fields and codings are as defined in 3GPP TS 44.004. + +### 9.3.11 L3 Information (message name) + +This element contains a link layer service data unit (L3 message). It is used to forward a complete L3 message as specified in 3GPP TS 24.008 or 3GPP TS 44.018 between BTS and BSC. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Indicator | | | | | | | | 3 | +| Link Layer Service Data Unit | | | | | | | | 4 | +| (i.e. a layer 3 message
as defined in 3GPP TS 24.008 or 3GPP TS 44.018) | | | | | | | | n | + +The Length Indicator field (octets 2-3) indicates in binary the remaining length of the element (octets 4-n). The most significant bit is bit 8 of octet 2 and the least significant bit is bit 1 of octet 3. + +Octets 4-n contain the complete L3 message as defined in 3GPP TS 24.008 or in 3GPP TS 44.018. In the message format sub-clause, the 3GPP TS 24.008 or 3GPP TS 44.018 message name to be included is indicated within brackets. + +### 9.3.12 MS Identity + +This element carries the identity of an MS (TMSI or IMSI). It is a variable length element. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| | | | | | | | | 3 | +| MS Identity | | | | | | | | N | + +The MS Identity field (octets 3-N) is coded as specified for the Mobile Identity information element of 3GPP TS 24.008, octets 3-N. + +### 9.3.13 MS Power + +This element carries the power level of MS and indicates the use of fast power control and enhanced power control. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|--------------------|---------|---|-------------|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | | +| Reserved | FPC_EPC | | Power Level | | | | | | 2 | + +The FPC\_EPC (Fast Power Control/Enhanced Power Control) field (octet 2) has different interpretation depending on the channel mode of the channel and whether the channel is in EPC mode. + +If the channel mode is such that FPC may be used, the FPC\_EPC field indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: + +Value + +- 0 Fast Power Control not in use +- 1 Fast Power Control in use + +If the channel is in EPC mode, the FPC\_EPC field indicates whether EPC procedures are used for MS (uplink) power control. It is coded as follows: + +Value + +- 0 EPC not in use for MS power control +- 1 EPC in use for MS power control + +If the channel mode is such that FPC may not be used and the channel is not in EPC mode, the BTS shall ignore the value of the FPC\_EPC field and the BSC shall set its value to 0. + +The coding and meaning of the Power Level field is as defined in 3GPP TS 45.005 and 3GPP TS 45.008. See also 3GPP TS 44.004. + +### 9.3.14 Paging Group + +This element carries the paging population of an MS to be paged. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Paging Group | | | | | | | | 2 | + +The Paging Group field (octet 2) contains the binary representation of the paging group as defined in 3GPP TS 45.002. + +### 9.3.15 Paging Load + +This element carries data about the load of a paging channel (PCH). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| | | | | | | | | 2 | +| Paging Buffer Space | | | | | | | | 3 | + +The Paging Buffer Space field (octets 2-3) indicates the remaining space for Paging Commands associated with this CCCH timeslot, given as the number of additional Paging Commands that it is possible to store. The number is binary coded with the most significant bit in bit 8 of octet 2 and the least significant bit in bit 1 of octet 3. + +### 9.3.16 Physical Context + +This element contains supplementary information on the transmission/reception process. It is a variable length element. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Physical | | | | | | | | 3 | +| Context | | | | | | | | | +| Information | | | | | | | | N | + +The Physical Context Information field is not specified. This information should not be analysed by BSC, but merely forwarded from one TRX/channel to another. + +### 9.3.17 Access Delay + +This element contains the delay of the access burst as measured by BTS at random access or at handover access. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Access Delay | | | | | | | | 2 | + +The Access Delay field contains the delay of the access burst as measured by BTS. The delay is expressed as defined for the Timing Advance TA in 3GPP TS 45.010 but with the range extended to 8 bits, i.e. the six least significant bits of the field correspond to the Timing Advance except for GSM 400 where all the 8 bits are used. + +### 9.3.18 RACH Load + +This element is used to carry information on the load of the RACH (Random Access Channel) associated with this CCCH timeslot. It is of variable length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| | | | | | | | | 3 | +| RACH Slot Count | | | | | | | | 4 | +| | | | | | | | | 5 | +| RACH Busy Count | | | | | | | | 6 | +| | | | | | | | | 7 | +| RACH Access Count | | | | | | | | 8 | +| | | | | | | | | 9 | +| Supplementary Information | | | | | | | | N | + +The RACH Slot Count field (octets 3-4) indicates the total number of available access slots over which the measurement (counting) was performed. The value is binary coded with the most significant bit in bit 8 of the first octet and the least significant bit in bit 1 of the second octet. + +The RACH Busy Count field (octets 5-6) indicates the number of RACH burst periods during which the received signal level has exceeded a given threshold. This will give a measure of the number of "busy" random access slots. The value is binary coded with the most significant bit in bit 8 of the first octet and the least significant bit in bit 1 of the second octet. + +The RACH Access Count field (octets 7-8) indicates the number of received access bursts during the same measurement period. The value is binary coded with the most significant bit in bit 8 of the first octet and the least significant bit in bit 1 of the second octet. + +The busy count signal level threshold and the measurement period are parameters set by O&M. + +The Supplementary Information field may carry additional operator dependent information. + +### 9.3.19 Request Reference + +This element carries the Request Reference parameters used for contention resolution on RACH. + +| | | | | | | | | | +|--------------------|---|---|---|----|-----------|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | 1 | +| RA | | | | | | | | 2 | +| T1' | | | | | T3 (high) | | | 3 | +| T3 (low) | | | | T2 | | | | 4 | + +Octets 2-4 are coded as the corresponding fields of the Request Reference element of 3GPP TS 44.018. (Octet 2, RA, is the Random Access Information field set by MS in the CHANNEL REQUEST message. Octets 3-4 contain the absolute frame number modulo 42432 for the frame number when the access burst was received, see Starting Time information element of 3GPP TS 44.018). + +### 9.3.20 Release Mode + +This element is used to distinguish between normal release and local end release of the radio data link connection. + +| | | | | | | | | | +|-------------------------|---|---|---|---|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | 1 | +| Reserved for future use | | | | | | | M | 2 | + +The M bit is coded as follows: + +- 0 normal release +- 1 local end release + +### 9.3.21 Resource Information + +This element is used to indicate the interference level for each of the idle channels of a TRX. + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---|-----| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Channel Number (1) | | | | | | | | 3 | +| Interference level (1) | | | | | | | | 4 | +| | | | | | | | | | +| Channel Number (N) | | | | | | | | N-1 | +| Interference level (N) | | | | | | | | N | + +The Length field indicates in binary the remaining length of the element (octets 3-N). + +Octets 3-N forms a list of Channel Numbers and Interference levels measured on the corresponding channel. + +The Channel Number octet is coded as octet 2 of the Channel Number information element, sub-clause 9.3.1. + +The Interference Level octet is coded as follows: + +| | | | | | | | | +|-------------|---|---|-------------------------|---|---|---|---| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| Interf Band | | | Reserved for future use | | | | | + +The Interf Band field (bits 6-8) indicates in binary the interference level expressed as one of five possible interference level bands as defined by O&M. The interference level is averaged over a period of Intave (parameter set by O&M, see 3GPP TS 45.008) immediately before the transmission of the RF RESource INDication message. See also 3GPP TS 48.008 and 3GPP TS 45.008. + +### 9.3.22 RLM Cause + +This element is used to indicate the precise protocol error or the reason for a release on the radio link layer. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|-------------|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| E | Cause Value | | | | | | | 3 | + +The Cause Value is a one octet field if the extension bit is set to 0. If the extension bit is set to 1, the Cause Value is a two octet field. + +The Cause Value field is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------|---|---|---|---|---|---|---|-----------------------------------------------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | reserved | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | timer T200 expired (N200+1) times | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | re-establishment request | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | unsolicited UA response | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | unsolicited DM response | +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | unsolicited DM response, multiple frame established state | +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | unsolicited supervisory response | +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | sequence error | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | U-frame with incorrect parameters | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | S-frame with incorrect parameters | +| 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | I-frame with incorrect use of M bit | +| 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | I-frame with incorrect length | +| 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | frame not implemented | +| 0 | 0 | 0 | 1 | 1 | 0 | 1 | 1 | SABM command, multiple frame established state | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | SABM frame with information not allowed in this state | +| All other values are reserved for future use. | | | | | | | | | + +### 9.3.23 Starting Time + +This element provides the starting time expressed as FN modulo 42432 (FN is absolute frame number). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-----------|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| T1' | | | | T3 (high) | | | | 2 | +| T3 (low) | | | | T2 | | | | 3 | + +Octets 2-3 are coded as defined for octets 2-3 of the Starting Time information element of 3GPP TS 44.018. + +### 9.3.24 Timing Advance + +This element contains the timing advance to be used by MS in subsequent communications. It is calculated by BTS at the reception of a CHANnel REquest message (random access burst) or a handover access burst. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Timing Advance | | | | | | | | 2 | + +The Timing Advance field contains the timing advance TA as specified in 3GPP TS 45.010. + +Bits 7-8 of octet 2 are used in GSM 400 for support of extended cell range. For all other bands bit 7-8 are spare according to 3GPP TS 44.018. + +### 9.3.25 Uplink Measurements + +This element is used to report the results of the TRX measurements on the uplink radio path of an activated basic radio channel. It is of variable length. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | +|---------------------------------------------|----------------|---------------|---|---------------|---|---|---|---|--|--|--|--|--|--|--| +| Element identifier | | | | | | | | 1 | | | | | | | | +| Length | | | | | | | | 2 | | | | | | | | +| rfu | DTXd | RXLEV-FULL-up | | | | | | 3 | | | | | | | | +| Reserved | RXLEV-SUB-up | | | | | | | 4 | | | | | | | | +| Reserved | RXQUAL-FULL-up | | | RXQUAL-SUB-up | | | | 5 | | | | | | | | +| Supplementary
Measurement
Information | | | | | | | | 6 | | | | | | | | +| | | | | | | | | N | | | | | | | | + +rfu = Reserved for Future Use. + +The Length field indicates in binary the remaining length of the element (octets 3-N). + +Octets 3-5 contain results from measurements made by TRX on the uplink. + +The Supplementary Measurement Information field (octets 6-N) may carry additional operator dependent information. + +The DTXd field (octet 3) indicates whether DTX was employed by TRX on the downlink transmission during the measurement period. + +The RXLEV-FULL-up and RXLEV-SUB-up fields (octets 3-4) report the average uplink signal level as measured by TRX over the measurement period on all slots and on a subset of the slots respectively (see 3GPP TS 45.008). Each field is coded as defined in 3GPP TS 45.008. + +The RXQUAL-FULL-up and RXQUAL-SUB-up fields (octet 5) report the average uplink quality as measured by TRX over the measurement period on all slots and on a subset of the slots respectively (see 3GPP TS 45.008). Each field is coded as defined in 3GPP TS 45.008. + +### 9.3.26 Cause + +The cause element is used to indicate the reason for a particular event to have occurred and is coded as shown below. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | +|----------------------|-------------|---|---|---|---|---|---|----|--|--|--|--|--|--|--| +| Element identifier | | | | | | | | 1 | | | | | | | | +| Length | | | | | | | | 2 | | | | | | | | +| E | Cause Value | | | | | | | 3 | | | | | | | | +| Cause Extension | | | | | | | | 3a | | | | | | | | +| | | | | | | | | 4 | | | | | | | | +| Diagnostic(s) if any | | | | | | | | N | | | | | | | | + +The Length field indicates in binary the remaining length of the element (octets 3-N). + +The Cause Value is a single octet field (octet 3) if the extension bit E (bit 8) is set to 0. If it is set to 1 then the cause value is a 2 octet field (octets 3 and 3a). + +The Cause Value is divided into two fields: a class (bits 5 to 7 of octet 3) and a value within the class (bits 1 to 4 of octet 3). + +If the value of the first octet of the cause field is 1XXX 0000 then the second octet is reserved for national applications (XXX will still indicate the class). + +Diagnostic information is not available for every cause, see the table below. When available, it is coded in the same way as the corresponding information element in clause 9. Inclusion of diagnostics is optional. + +#### Classes: + +Class (000): Normal event + +- Class (001): Normal event +- Class (010): Resource unavailable +- Class (011): Service or option not available +- Class (100): Service or option not implemented +- Class (101): Invalid message (e.g. parameter out of range) +- Class (110): Protocol error +- Class (111): Interworking + +#### **CAUSE VALUES:** + +| Class | Value | Cause | Diagnostics | +|--------------|----------------|---------------------------------------------------|-----------------| +| 0 0 0 | - - - - | Normal Event | | +| 0 0 0 | 0 0 0 0 | radio interface failure | Channel Number | +| 0 0 0 | 0 0 0 1 | radio link failure | Channel Number | +| 0 0 0 | 0 0 1 0 | handover access failure | Channel Number | +| 0 0 0 | 0 0 1 1 | talker access failure | Channel Number | +| 0 0 0 | 0 1 0 0 | reserved for international use | | +| 0 0 0 | 0 1 0 1 | reserved for international use | | +| 0 0 0 | 0 1 1 0 | reserved for international use | | +| 0 0 0 | 0 1 1 1 | O&M intervention | | +| 0 0 0 | 1 0 0 0 | reserved for international use | | +| 0 0 0 | 1 : : : | | | +| 0 0 0 | 1 1 1 0 | | | +| 0 0 0 | 1 1 1 1 | normal event, unspecified | | +| 0 0 1 | - - - - | Normal Event | | +| 0 0 1 | 0 0 0 0 | reserved for international use | | +| 0 0 1 | 0 : : : | | | +| 0 0 1 | 0 1 1 1 | | | +| 0 0 1 | 1 0 0 0 | reserved for national use | | +| 0 0 1 | 1 : : : | | | +| 0 0 1 | 1 1 1 1 | | | +| 0 1 0 | - - - - | Resource unavailable | | +| 0 1 0 | 0 0 0 0 | equipment failure | | +| 0 1 0 | 0 0 0 1 | radio resource not available | Channel Number | +| 0 1 0 | 0 0 1 0 | terrestrial channel failure | Channel Number | +| 0 1 0 | 0 0 1 1 | CCCH overload | Channel Number | +| 0 1 0 | 0 1 0 0 | ACCH overload | Channel Number | +| 0 1 0 | 0 1 0 1 | processor overload | | +| 0 1 0 | 0 1 1 0 | reserved for international use | | +| 0 1 0 | 0 1 1 1 | BTS not equipped | | +| 0 1 0 | 1 0 0 0 | remote transcoder failure | Channel Number | +| 0 1 0 | 1 0 0 1 | notification overflow | Channel Number | +| 0 1 0 | 1 0 1 0 | reserved for international use | | +| 0 1 0 | 1 0 1 1 | reserved for international use | | +| 0 1 0 | 1 1 0 0 | reserved for national use | | +| 0 1 0 | 1 1 0 1 | reserved for national use | | +| 0 1 0 | 1 1 1 0 | reserved for national use | | +| 0 1 0 | 1 1 1 1 | resource not available, unspecified | | +| 0 1 1 | - - - - | Service or Option Not Available | | +| 0 1 1 | 0 0 0 0 | requested transcoding/rate adaption not available | Channel Number | +| 0 1 1 | 0 0 0 1 | reserved for international use | | +| 0 1 1 | : : : : | | | +| 0 1 1 | 1 1 1 0 | | | +| 0 1 1 | 1 1 1 1 | service or option not available, unspecified | | +| 1 0 0 | - - - - | Service or Option Not Implemented | | +| 1 0 0 | 0 0 0 0 | encryption algorithm not implemented | Channel Number | +| 1 0 0 | 0 0 0 1 | reserved for international use | | +| 1 0 0 | 0 : : : | | | +| 1 0 0 | 0 1 1 1 | | | +| 1 0 0 | 1 0 0 0 | reserved for national use | | +| 1 0 0 | 1 : : : | | | +| 1 0 0 | 1 1 1 0 | | | +| 1 0 0 | 1 1 1 1 | service or option not implemented, unspecified | | +| 1 0 1 | - - - - | Invalid Message | | +| 1 0 1 | 0 0 0 0 | radio channel already activated/allocated | Channel Number | +| 1 0 1 | 0 0 0 1 | reserved for international use | | +| 1 0 1 | 0 : : : | | | +| 1 0 1 | 0 1 1 1 | | | +| 1 0 1 | 1 0 0 0 | reserved for national use | | +| 1 0 1 | 1 : : : | | | +| 1 0 1 | 1 1 1 0 | | | +| 1 0 1 | 1 1 1 1 | invalid message, unspecified | | +| 1 1 0 | - - - - | Protocol Error | | +| 1 1 0 | 0 0 0 0 | message discriminator error | Message Discrim | +| 1 1 0 | 0 0 0 1 | message type error | Message Type | +| 1 1 0 | 0 0 1 0 | message sequence error | Message Type | + +| Class | Value | Cause | Diagnostics | +|--------------|----------------|--------------------------------------|-----------------| +| 1 1 0 | 0 0 1 1 | general information element error | | +| 1 1 0 | 0 1 0 0 | mandatory information element error | Element Identif | +| 1 1 0 | 0 1 0 1 | optional information element error | Element Identif | +| 1 1 0 | 0 1 1 0 | information element non-existent | Element Identif | +| 1 1 0 | 0 1 1 1 | information element length error | Element Identif | +| 1 1 0 | 1 0 0 0 | invalid information element contents | Inform. Element | +| 1 1 0 | 1 0 0 1 | reserved for international use | | +| 1 1 0 | 1 0 1 0 | reserved for international use | | +| 1 1 0 | 1 0 1 1 | reserved for international use | | +| 1 1 0 | 1 1 0 0 | reserved for national use | | +| 1 1 0 | 1 1 0 1 | reserved for national use | | +| 1 1 0 | 1 1 1 0 | reserved for national use | | +| 1 1 0 | 1 1 1 1 | protocol error, unspecified | | +| 1 1 1 | - - - - | Interworking | | +| 1 1 1 | 0 0 0 0 | reserved for international use | | +| 1 1 1 | 0 : : : | | | +| 1 1 1 | 0 1 1 1 | | | +| 1 1 1 | 1 0 0 0 | reserved for national use | | +| 1 1 1 | 1 : : : | | | +| 1 1 1 | 1 1 1 0 | | | +| 1 1 1 | 1 1 1 1 | interworking, unspecified | | + +### 9.3.27 Measurement result number + +This element is used by BTS to number, (on a channel), the measurement result messages sent to BSC. It is set to 0 at activation time of the channel. The numbering is modulo 256. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Measurement result number | | | | | | | | 2 | + +### 9.3.28 Message Identifier + +This element is used to indicate a message type within a message. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Message Type | | | | | | | | 2 | + +Octet 2 is coded as the Message Type information element, sub-clause 9.2. + +### 9.3.29 SACCH Information + +This element is used to carry the SACCH filling information (System Information messages, EXTENDED MEASUREMENT ORDER message or MEASUREMENT INFORMATION message) that is to be used on a specific channel. The MEASUREMENT INFORMATION message is periodically sent on SACCH. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------|---|---|---|---|---|---|---|-----| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Number of messages | | | | | | | | 3 | +| Type of 1st message | | | | | | | | 4 | +| Length of 1st message | | | | | | | | 5 | +| 1st message | | | | | | | | j | +| Type of n'th message | | | | | | | | l | +| Length of n'th message | | | | | | | | l+1 | +| n'th message | | | | | | | | N | + +The Length field (octet 2) indicates in binary the total remaining length of the element (octets 3 - N). + +The Number of SI messages field (octet 3) indicates in binary the number of messages contained in the element. + +The coding of each of these messages consists of a type field (Type of n'th msg), a length field (Length of n'th message) and a message field (n'th message). + +The "Type of n'th msg" field indicates the type of SYSTEM INFORMATION, or an EXTENDED MEASUREMENT ORDER message or a MEASUREMENT INFORMATION message that follows in the "n'th message" field. It is coded as follows: + +| Value | Message | +|-----------------|----------------------------| +| 0 0 0 0 0 1 0 1 | SYSTEM INFORMATION 5 | +| 0 0 0 0 0 1 1 0 | SYSTEM INFORMATION 6 | +| 0 0 0 0 1 1 0 1 | SYSTEM INFORMATION 5bis | +| 0 0 0 0 1 1 1 0 | SYSTEM INFORMATION 5ter | +| 0 1 0 0 0 1 1 1 | EXTENDED MEASUREMENT ORDER | +| 0 1 0 0 1 0 0 0 | MEASUREMENT INFORMATION | + +All other values are reserved. + +The "Length of n'th SI message" field indicates in binary the length of the "n'th message" field that follows. + +The "n'th message" field contains a complete SACCH message as defined in 3GPP TS 44.018. + +### 9.3.30 System Info Type + +This element is used to indicate the type of SYSTEM INFORMATION message or an EXTENDED MEASUREMENT ORDER message or a MEASUREMENT INFORMATION message as defined in 3GPP TS 44.018. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Sys Info Type | | | | | | | | 2 | + +The Sys Info Field (octet 2) indicates the type of message. It is coded as follows: + +| Value | Message | +|--------------------------------|----------------------------| +| 0 0 0 0 0 0 0 0 | SYSTEM INFORMATION 8 | +| 0 0 0 0 0 0 0 1 | SYSTEM INFORMATION 1 | +| 0 0 0 0 0 0 1 0 | SYSTEM INFORMATION 2 | +| 0 0 0 0 0 0 1 1 | SYSTEM INFORMATION 3 | +| 0 0 0 0 0 1 0 0 | SYSTEM INFORMATION 4 | +| 0 0 0 0 0 1 0 1 | SYSTEM INFORMATION 5 | +| 0 0 0 0 0 1 1 0 | SYSTEM INFORMATION 6 | +| 0 0 0 0 0 1 1 1 | SYSTEM INFORMATION 7 | +| 0 0 0 0 1 0 0 0 | SYSTEM INFORMATION 16 | +| 0 0 0 0 1 0 0 1 | SYSTEM INFORMATION 17 | +| 0 0 0 0 1 0 1 0 | SYSTEM INFORMATION 2bis | +| 0 0 0 0 1 0 1 1 | SYSTEM INFORMATION 2ter | +| 0 0 0 0 1 1 0 1 | SYSTEM INFORMATION 5bis | +| 0 0 0 0 1 1 1 0 | SYSTEM INFORMATION 5ter | +| 0 0 0 0 1 1 1 1 | SYSTEM INFORMATION 10 | +| 0 1 0 0 0 1 1 1 | EXTENDED MEASUREMENT ORDER | +| 0 1 0 0 1 0 0 0 | MEASUREMENT INFORMATION | +| 0 0 1 0 1 0 0 0 | SYSTEM INFORMATION 13 | +| 0 0 1 0 1 0 0 1 | SYSTEM INFORMATION 2quater | +| 0 0 1 0 1 0 1 0 | SYSTEM INFORMATION 9 | +| 0 0 1 0 1 0 1 1 | SYSTEM INFORMATION 18 | +| 0 0 1 0 1 1 0 0 | SYSTEM INFORMATION 19 | +| 0 0 1 0 1 1 0 1 | SYSTEM INFORMATION 20 | +| All other values are reserved. | | + +### 9.3.31 MS Power Parameters + +This element carries the parameters required by TRX for MS power control. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| MS Power Control | | | | | | | | 3 | +| Parameters | | | | | | | | | +| | | | | | | | | N | + +The MS Power Control Parameters field contains the parameters and limits required when MS power control is to be performed by BTS. The coding is operator dependant. Examples of possible parameters and algorithms can be found in 3GPP TS 45.008 (RXLEV, RX-QUAL-FULL, RX-QUAL-SUB, DISTANCE (Timing Advance) etc.). + +### 9.3.32 BS Power Parameters + +This element carries the parameters required by TRX for control of its own transmission power. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| BS Power Control | | | | | | | | 3 | +| Parameters | | | | | | | | | +| | | | | | | | | N | + +The BS Power Control Parameters field contains the parameters and limits required when TRX transmission power control is to be performed by BTS. The coding is operator dependant. Examples of possible parameters and algorithms can be found in 3GPP TS 45.008 (RXLEV, RX-QUAL-FULL, RX-QUAL-SUB, DISTANCE (Timing Advance) etc.). + +### 9.3.33 Pre-processing Parameters + +This element contains the parameters required by BTS for the pre-processing of radio measurement data. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| reserved for future use | | | | | | P | | 3 | +| Pre-processing | | | | | | | | 4 | +| Parameters | | | | | | | | | +| | | | | | | | | N | + +The P bit (bit 1 of octet 3) indicates whether pre-processing is to be used and it is coded as follows: + +- 0 use the basic measurement reporting procedure (report raw data); +- 1 use the pre-processed measurement reporting procedure. + +If pre-processing is to be used, the Pre-processing Parameters field (octets 4-N) contains the parameters required by BTS. The coding of this field is operator dependant. + +### 9.3.34 Pre-processed Measurements + +This element is used by BTS to report the results of the pre-processing of radio measurement data. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Pre-processed | | | | | | | | 3 | +| Measurements | | | | | | | | | +| | | | | | | | | N | + +The Pre-processed Measurements field (octets 3-N) contains the results of the pre-processing in BTS. The coding of this field is operator dependant. + +### 9.3.35 Full Immediate Assign Info + +This element is used to convey a full L3 immediate assign message (3 types). + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|--------------------|---|---|---|---|----| +| | | | Element identifier | | | | | 1 | +| | | | Length Indicator | | | | | 2 | +| | | | Full Immediate | | | | | 3 | +| | | | Assign Info | | | | | | +| | | | | | | | | 25 | + +The Length Indicator field (octet 2) indicates in binary the remaining length of the element (octets 3-25). + +The Full Immediate Assign Info field (octets 3-25) contains a complete immediate assign message (IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT) as defined in 3GPP TS 44.018. + +### 9.3.36 SMSCB Information + +This element is used to convey a complete frame to be broadcast on the CBCH including the Layer 2 header for the radio path. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|--------------------|---|---|---|---|----| +| | | | Element identifier | | | | | 1 | +| | | | SMSCB frame | | | | | 2 | +| | | | | | | | | | +| | | | | | | | | 24 | + +### 9.3.37 MS Timing Offset + +The information is coded in two octets and contains the MS Timing Offset as measured by the BTS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|--------------------|---|---|---|---|---| +| | | | Element identifier | | | | | 1 | +| | | | Timing Offset | | | | | 2 | + +The meaning of the MS Timing Offset is as defined in 3GPP TS 45.010. The value of MS Timing Offset is the binary value of the 8-bit Timing Offset field (octet 2) - 63. The range of MS Timing Offset is therefore -63 to 192. + +### 9.3.38 Erroneous Message + +This information element is used to carry a complete A-bis interface message which was considered erroneous at reception. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|--------------------|---|---|---|---|---| +| | | | Element identifier | | | | | 1 | +| | | | Length | | | | | 2 | +| | | | Received Message | | | | | 3 | +| | | | | | | | | | +| | | | | | | | | N | + +The Received Message field contains a complete A-bis interface L3 message as defined in clause 8 of this GTS, including Message Discriminator and Message Type. + +### 9.3.39 Full BCCH Information (message name) + +This information element contains a complete L3 message as specified in 3GPP TS 24.008. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|--------------------| +| | | | | | | | | Element identifier | +| | | | | | | | | Length Indicator | +| | | | | | | | | Layer 3 message | +| | | | | | | | | as | +| | | | | | | | | defined | +| | | | | | | | | in 3GPP TS 44.018 | +| | | | | | | | | 1 | +| | | | | | | | | 2 | +| | | | | | | | | 3 | +| | | | | | | | | 4 | +| | | | | | | | | 25 | + +The Length Indicator field (octet 2) indicates in binary the remaining length of the element (octets 3-25). The most significant bit is bit 8 of octet 2 and the least significant bit is bit 1 of octet 2. + +Octets 3-25 contain the complete L3 message as defined in 3GPP TS 44.018. In the message format sub-clause, the 3GPP TS 44.018 message name to be included is indicated within brackets. + +### 9.3.40 Channel Needed + +This information element is used to indicate to the mobile station which channel will be needed for the transaction linked to the paging procedure. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|-------------------------| +| | | | | | | | | Element identifier | +| | | | | | | | | Reserved for future use | +| | | | | | | | | Channel | +| | | | | | | | | 1 | +| | | | | | | | | 2 | + +The Channel Field (bits 1-2 of octet 2) indicates the further combination of channel which will be needed. It is coded as follows: + +| Value | Channel Needed. | +|-------|-----------------------------| +| 0 0 | Any Channel. | +| 0 1 | SDCCH. | +| 1 0 | TCH/F (Full rate). | +| 1 1 | TCH/F or TCH/H (Dual rate). | + +### 9.3.41 CB Command type + +This element is used to indicate the type of broadcast requested. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|--------------------| +| | | | | | | | | Element identifier | +| | | | | | | | | Command | +| | | | | | | | | Default Broadcast | +| | | | | | | | | 0 Spare | +| | | | | | | | | Last Block | +| | | | | | | | | 1 | +| | | | | | | | | 2 | + +The Command Field (bits 5 to 8) indicates the command to be performed. It is coded as follows: + +| Value | Command | +|--------------------------------|-----------------------------| +| 0 0 0 0 | Normal message Broadcast. | +| 1 0 0 0 | Schedule message Broadcast. | +| 1 1 1 0 | Default message Broadcast. | +| 1 1 1 1 | Null message Broadcast. | +| All other values are reserved. | | + +When the Command Field is different from the value 1110 (Default message Broadcast), the BTS uses the SMSCB message IE together with the Command Field and the Last Block Field to build the blocks sent on the Radio interface, as defined by 3GPP TS 44.012. In that case bit 4 is ignored. + +When the Command Field takes the value 1110 (Default message Broadcast), the BTS uses the SMSCB message IE together with the Default Broadcast Field and the Last Block Field to build the blocks sent on the Radio interface, as defined by 3GPP TS 44.012. + +The Default Broadcast Field (bit 4) is coded as follows: + +| Value | Default message to be broadcast | +|-------|---------------------------------| +| 0 | Normal message. | +| 1 | Null message. | + +The BTS uses the Last Block Field to signal to the MS the last block containing useful information as defined by 3GPP TS 44.012. This Field (bits 1 and 2) is coded as follows: + +| Value | Last Block containing useful information | +|-------|------------------------------------------| +| 00 | Block 4 | +| 01 | Block 1 | +| 10 | Block 2 | +| 11 | Block 3 | + +### 9.3.42 SMSCB Message + +This element is used to convey the message to be broadcast on the CBCH. + +![](45578bd3ed11d45af63ce00e28bab2f8_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| SMSCB Message | | | | | | | | 3 | +| | | | | | | | | N | + +### 9.3.43 CBCH Load Information + +This information element is used to indicate to the BSC the load situation of CBCH in the BTS. + +![](4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|-------|---|---|--------------------|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| CBCH Load Type | Spare | | | Message Slot Count | | | | 2 | + +The CBCH Load Type field (bit 8 of octet 2) indicates either an underflow or an overflow situation of the CBCH in the BTS. It is coded as follows: + +| Value | CBCH Load Type | +|-------|----------------| +| 0 | Underflow | +| 1 | Overflow | + +The Message Slot Count field (bits 1-4 of octet 2) indicates either the amount of SMSCB messages that are needed immediately by BTS or the amount of delay in message slots that is needed immediately by BTS depending on the value of the CBCH Load Type field. It is coded as follows: + +| CBCH Load Type | Message Slot Count | +|----------------|---------------------------------------------------------------------------------------------| +| 0 | indicates the amount of SMSCB messages (1 to 15) that are needed immediately by BTS. | +| 1 | indicates the amount of delay in message slots (1 to 15) that is needed immediately by BTS. | + +### 9.3.44 SMSCB Channel Indicator + +This element is used to indicate the CB channel [see 3GPP TS 45.002] to be used for broadcasting the data. + +![](b7deb5c8e534f921026ab2447e0653b4_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-------------|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Spare | | | | Channel Ind | | | | 2 | + +This element is used to indicate the CB channel to be used for broadcasting the data. The Channel Ind field is coded as follows: + +| Value | Channel Ind | +|---------|------------------------------------------------------------------------------------------------------------------| +| 0 0 0 0 | Basic CBCH | +| 0 0 0 1 | Extended CBCH (supporting the extended CBCH by the network or MSs is optional)
all other values are reserved. | + +### 9.3.45 Group call reference + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------|---|---|---|---|---|---|---|--------| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Descriptive group or broadcast call reference | | | | | | | | 3 to 7 | + +The octets 3 to 7 are coded in the same way as the octets 2 to 6 in the Descriptive group or broadcast call reference information element as defined in 3GPP TS 24.008. + +### 9.3.46 Channel description + +This is a variable length element used to pass a radio interface information element from BSC to BTS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------|---|---|---|---|---|---|---|--------| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Group Channel Description | | | | | | | | 3 to n | + +Octet j (j = 3, 4, ..., n) is the unchanged octet j-2 of a radio interface Group Channel description information element as defined in 3GPP TS 44.018, n-2 is equal to the length of the radio interface Group channel description information element. + +### 9.3.47 NCH DRX information + +This is a variable length element used to pass a radio interface information element from BSC to BTS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| NCH DRX information | | | | | | | | 3 | + +Octet 3 bits 1 and 2 are bits 1 and 2 of the radio interface NLN as defined in 3GPP TS 44.018. + +Octet 3 bits 3, 4 and 5 are bits 1, 2 and 3 of the radio interface eMLPP priority as defined in 3GPP TS 44.018. + +Octet 3 bit 6 is the NLN status parameter as defined in 3GPP TS 44.018. + +Octet 3 bits 7 and 8 are spare and set to zero. + +### 9.3.48 Command indicator + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---------------|---|---|---|---|---|---|----| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| E | Command Value | | | | | | | 3 | +| Command Extension | | | | | | | | 3a | + +The Command Value is a single octet field (octet 3) if the extension bit E (bit 8) is set to 0. If it is set to 1 then the Command value is a 2 octet field (octets 3 and 3a). + +#### COMMAND VALUES: + +| Value | Command | +|---------------|--------------------------------| +| 0 0 0 0 0 0 0 | Start | +| 0 0 0 0 0 0 1 | Stop | +| 0 0 0 0 0 1 0 | reserved for international use | +| 0 : : : : : : | | +| 1 0 0 0 0 0 0 | | +| 1 0 0 0 0 0 1 | reserved for national use | +| 1 : : : : : : | | +| 1 1 1 1 1 1 1 | | + +### 9.3.49 eMLPP Priority + +This Information Element contains the eMLPP priority of the call. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---------------|---|---|---| +| Element identifier | | | | | | | | 1 | +| spare | | | | | call priority | | | 2 | + +The call priority field (bit 3 to 1 of octet 2) is coded in the same way as the call priority field (bit 3 to 1 of octet 5) in the Descriptive group or broadcast call reference information element as defined in 3GPP TS 24.008. + +### 9.3.50 UIC + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| UIC information | | | | | | | | 3 | + +Octet 3 bits 1 to 6 contain the radio interface octet 2 bits 3 to 8 of the UIC information element as defined in 3GPP TS 44.018. + +Octet 3 bits 7 and 8 are spare and set to zero. + +### 9.3.51 Main channel reference + +This element contains the main channel reference of a multislot connection. + +It is coded in two octets as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------|---|---|---|---|----|---|---|---| +| Element identifier | | | | | | | | 1 | +| Reserved for future use | | | | | TN | | | 2 | + +TN is time slot number, binary represented as in 3GPP TS 45.002. + +### 9.3.52 MultiRate configuration + +This element gives the description of the multirate speech codec configuration to be applied. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Rest of element coded as in 3GPP TS 44.018 not including 3GPP TS 44.018 element identifier or 3GPP TS 44.018 octet length value | | | | | | | | 3-n | + +### 9.3.53 MultiRate Control + +This element indicates whether TFO is enabled or not and whether the BSC authorises the BTS to perform autonomously multi-rate codec changes and whether an handover is to be expected. + +It is coded in two octets as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|----|-----|-----|---|-----|---|---| +| Element identifier | | | | | | | | 1 | +| Spare | | OD | PRE | RAE | | TFO | | 3 | + +The TFO field (bit 1 of octet 3) indicates if TFO is enabled or not. It is coded as follows: + +| Value | TFO | +|-------|-----------------------------------| +| 0 | Tandem Free Operation is enabled | +| 1 | Tandem Free Operation is disabled | + +The RAE field (bits 2-3, octet 3) defines whether the RATSCCH mechanism is enabled or not. It is coded as follows: + +| Value | RAE | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 0 | RATSCCH mechanism is generally enabled, the BTS may change the AMR configuration within the given SCS and MACS constraints and within the given radio and Abis channel. | +| 0 1 | RATSCCH mechanism will potentially be enabled for one exchange. The BSC will use a MultiRate CODEC MOD REQ message for that purpose | +| 1 0 | reserved | +| 1 1 | RATSCCH mechanism is generally disabled | + +The PRE field (bit 4 of octet 3) indicates if an handover is to be expected soon or not. It is coded as follows: + +| Value | PRE | +|-------|---------------------------------------------------| +| 0 | Handover is not expected, respectively has failed | +| 1 | Handover is expected soon | + +The OD field (bit 5 of octet 3) indicates if the BSC expects distant parameters or TFO Decision algorithm result from the BTS. + +| Value | PRE | +|-------|----------------------------------------------------------------------------| +| 0 | The BTS shall report distant parameters | +| 1 | The BTS shall report TFO Decision algorithm result (optimised parameters). | + +### 9.3.54 Supported Codec Types + +This element indicates the codec types supported by the BSS or remote BSS. + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|------------|---|---|---|---|---|---|-----| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Sys-ID | | | | | | | | 3 | +| ext | Codec List | | | | | | | 4-n | + +The Sys-ID field (octet 3) identifies the system that sends or has sent the configuration. It should be set to 0000 0000 for GSM. + +The Codec List field (octet 4) lists the codec types that are supported by the BSS and Transcoder, and are therefore potential candidates for TFO establishment. It is coded as follows: + +| | | +|--------|-----------------------------------------------------------------------------------------------------------| +| Bit 1: | Set to 1 if the GSM FR Speech Codec is supported. | +| Bit 2: | Set to 1 if the GSM HR Speech Codec is supported. | +| Bit 3: | Set to 1 if the GSM EFR Speech Codec is supported. | +| Bit 4: | Set to 1 if the GSM FR AMR Speech Codec is supported. | +| Bit 5: | Set to 1 if the GSM HR AMR Speech Codec is supported | +| Bit 6: | Set to 1 if the UMTS AMR Speech Codec is supported. | +| Bit 7: | Set to 1 if the UMTS AMR 2 Speech Codec is supported | +| Bit 8: | Extension bit. Set to 1 if at least one codec of Codec List extension 1 is supported, otherwise set to 0. | + +The Codec List extension 1 field (octet 5) lists additional codec types that are supported by the BSS and Transcoder, and are therefore potential candidates for TFO establishment. When no codec from this list is supported, then this field shall not be sent, and the extension bit of octet 4 shall be set to 0. + +| | | +|----------|-----------------------------------------------------------| +| Bit 1: | Set to 1 if the FR AMR WB Speech Codec is supported. | +| Bit 2: | Set to 1 if the UMTS AMR WB Speech Codec is supported. | +| Bit 3: | Set to 1 if the 8PSK HR AMR Speech Codec is supported. | +| Bit 4: | Set to 1 if the 8PSK FR AMR WB Speech Codec is supported. | +| Bit 5: | Set to 1 if the 8PSK HR AMR WB Speech Codec is supported. | +| Bit 6-7: | Reserved, set to 0. | +| Bit 8: | Reserved for extension, set to 0. | + +If bit 4 of the Codec List field (octet 4) indicates that FR AMR is supported or if bit 5 of the Codec List field (octet 4) indicates that HR AMR is supported and bit 8 is set to 0, or if bit 6 of the Codec List field (octet 4) indicates that UMTS AMR is supported, or if bit 7 of the Codec List field (octet 4) indicates that UMTS AMR 2 is supported, or if bit 1, 3, 4 or 5 of the Codec List extension 1 field (octet 5) indicates that AMR WB is supported, the following two octets (after the Codec List field and its extensions) should be coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------|---|---|---|---------|---|------|---|-----| +| Spare | | | | TFO VER | | MACS | | n+1 | +| SCS | | | | | | | | n+2 | + +The MACS field indicates the Maximum number of AMR Codec ModeS the BSS can support in the Active Codec Set. It should be coded as follows: + +| | | +|------|-------------------------------------------------------------------------| +| 0 0: | A maximum of four codec modes can be supported in the Active Codec Set | +| 0 1: | A maximum of one codec mode can be supported in the Active Codec Set | +| 1 0: | A maximum of two codec modes can be supported in the Active Codec Set | +| 1 1: | A maximum of three codec modes can be supported in the Active Codec Set | + +The TFO\_VER field indicates the TFO\_VERSION. + +0 0: Version 0 of TFO + +All other values reserved for future use. + +The SCS field indicates the Set of AMR Codec modes Supported by the BSS. It should be coded as follows for AMR FR and AMR HR: + +| | | +|--------|---------------------------------------------------| +| Bit 8: | Set to 1 if the AMR 12.2 Codec Mode is supported. | +| Bit 7: | Set to 1 if the AMR 10.2 Codec Mode is supported. | +| Bit 6: | Set to 1 if the AMR 7.95 Codec Mode is supported. | +| Bit 5: | Set to 1 if the AMR 7.40 Codec Mode is supported. | +| Bit 4: | Set to 1 if the AMR 6.70 Codec Mode is supported. | +| Bit 3: | Set to 1 if the AMR 5.90 Codec Mode is supported. | +| Bit 2: | Set to 1 if the AMR 5.15 Codec Mode is supported. | +| Bit 1: | Set to 1 if the AMR 4.75 Codec Mode is supported. | + +If AMR WB is concerned, the SCS field (octets 7) is coded as follows: + +| | | +|---------|-------------------------------------------------------| +| Bit 6-8 | Spare. Set to 0 | +| Bit 5: | Set to 1 if the WB-AMR 23.85 Codec Mode is supported. | +| Bit 4: | Set to 1 if the WB-AMR 15.85 Codec Mode is supported. | +| Bit 3 | Set to 1 if the WB-AMR 12.65 Codec Mode is supported. | +| Bit 2 | Set to 1 if the WB-AMR 8.85 Codec Mode is supported. | +| Bit 1 | Set to 1 if the WB-AMR 6.60 Codec Mode is supported. | + +### 9.3.55 Codec Configuration + +This element indicates the active codec in the BSS or the remote BSS + +It is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| Active Codec Type | | | | | | | | 3 | + +The Active Codec Type field (bits 1-8, octet 3) indicates the type of codec in use. It is coded as follows: + +| | | +|----------------------------------------------|----------------------------------------------------------| +| 0 0 0 0 . 0 0 0 0: | Full Rate Codec in use | +| 0 0 0 0 . 0 0 0 1: | Half Rate Codec in use | +| 0 0 0 0 . 0 0 1 0: | Enhanced Full Rate Codec in use | +| 0 0 0 0 . 0 0 1 1: | FR Adaptive Multi Rate Codec in use | +| 0 0 0 0 . 0 1 0 0: | HR Adaptive Multi Rate Codec in use | +| 0 0 0 0 . 0 1 0 1: | UMTS Adaptive Multi Rate Codec in use | +| 0 0 0 0 . 0 1 1 0: | UMTS Adaptive Multi Rate 2 Codec in use | +| 0 0 0 0 . 1 0 0 1: | Full Rate Adaptive Multi-Rate WideBand Codec in use | +| 0 0 0 0 1 0 1 0 | UMTS Adaptive Multi-Rate WideBand Codec in use | +| 0 0 0 0 1 0 1 1 | 8PSK Half Rate Adaptive Multi-Rate Codec in use | +| 0 0 0 0 1 1 0 0 | 8PSK Full Rate Adaptive Multi-Rate WideBand Codec in use | +| 0 0 0 0 1 1 0 1 | 8PSK Half Rate Adaptive Multi-Rate WideBand Codec in use | +| All other values are reserved for future use | | + +If the Active Codec Type field (octet 3) indicates that AMR (FR or HR) is the active codec type, then the following two octets (octets 4-5) shall provide the configuration in use. They shall be coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------|---|---|---|---|---|-----|---|---| +| Spare | | | | | | ICM | | 4 | +| Active Codec Set | | | | | | | | 5 | + +The ICM field (bits 1-2, octet 4) defines the Initial Codec Mode. It is coded as defined in the 3GPP TS 45.009. + +The Active Codec Set (octet 5) defines the set of AMR codec modes used in the active set. It is coded as defined for the Set of AMR codec modes in the Multi-Rate configuration IE in the 3GPP TS 44.018. + +If the Active Codec Type field (octet 3) indicates that AMR WB is the active codec type, then the following three octets (octets 4-6) shall provide the configuration in use. They shall be coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | +|------------------|---|---|---|---|---|-----|---|---|--|--| +| Spare | | | | | | ICM | | 4 | | | +| Active Codec Set | | | | | | | | 5 | | | +| Active Codec Set | | | | | | | | 6 | | | + +The ICM field (bits 1-2, octet 4) defines the Initial Codec Mode. It is coded as defined in the 3GPP TS 45.009. + +The Active Codec Set (octets 5-6) defines the set of AMR codec modes used in the active set. It is coded as defined for the Set of AMR codec modes in the Multi-Rate configuration IE in the 3GPP TS 44.018. + +### 9.3.56 Round Trip Delay + +This element indicates the value of the calculated round trip delay between the BTS and the transcoder, or between the BTS and the remote BTS, if TFO is established. + +It is coded in 2 octets as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|-----------|---|---| +| Element identifier | | | | | | | | 1 | +| RTD | | | | | | Delay IND | | 2 | + +The RTD field is the binary representation of the value of the round trip delay in 20 ms increments. + +The Delay IND field indicates if the delay corresponds to a BTS to transcoder delay or to a BTS to remote BTS delay. It is coded as follows: + +| Value | Delay IND | +|-------|------------------------------------------------------------| +| 0 | The RTD field contains the BTS-Transcoder round trip delay | +| 1 | The RTD field contains the BTS-Remote BTS round trip delay | + +### 9.3.57 TFO Status + +This element indicates if TFO is established. It is coded in 2 octets as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|-----|---|---| +| Element identifier | | | | | | | | 1 | +| Spare | | | | | | TFO | | 2 | + +The TFO field shall be coded as follows: + +| Value | TFO | +|-------|------------------------| +| 0 | TFO is not established | +| 1 | TFO is established | + +### 9.3.58 LLP APDU + +This is a variable length element that conveys an embedded message or message segment associated with the higher level protocol LLP, as defined in 3GPP TS 44.071. This element can be sent from the BSC to the BTS or to the Standalone Type B LMU, and vice versa. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| The rest of the information element contains the embedded message that contains a Facility Information Element as defined in 3GPP TS 44.071 excluding the Facility IEI and length of Facility IEI octets defined in 3GPP TS 44.071. | | | | | | | | 3-n | + +### 9.3.59 TFO transparent container + +This is a variable length element that conveys a message associated with TFO protocol, as defined in 3GPP TS 28.062. This element can be sent from the BSC to the BTS or from the BTS to the BSC. The BTS shall retrieve the information it is able to understand, and forward transparently the complete information to the BSC or to the TRAU. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|-----| +| Element identifier | | | | | | | | 1 | +| Length | | | | | | | | 2 | +| The rest of the information element contains the embedded message that contains the TFO configuration. | | | | | | | | 3-n | + +### 9.3.60 DRX Info + +This element is used to indicate when the corresponding PAGING COMMAND message is to be sent, as specified by the eDRX cycle and CCCH Block Number on a Multiframe Number. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------|---|---|---|------------|---|---|---|---| +| Element identifier | | | | | | | | 1 | +| Multiframe Number (high) | | | | | | | T | 2 | +| Multiframe Number (low) | | | | | | | | 3 | +| eDRX Cycle | | | | CCCH Block | | | | 4 | + +Multiframe Number: + +This field identifies the multiframe number within the applicable eDRX cycle in which the PAGing REQuest message is to be sent. Values between 0-13311 are allowed + +T: + +This field is used to determine whether the PAGing REQuest message is to be sent using the CCCH (T=0) or the EC-CCCH (T=1) + +CCCH Block: + +This field identifies the CCCH block number within the indicated multiframe in which the PAGing REQuest message is to be sent. Values between 0-15 are allowed. If T = 0 the value is between 0-8 + +eDRX Cycle: + +This field is used to determine the number of multiframes within an eDRX cycle as defined in 3GPP TS 45.002 [8]. Values between 0-15 are allowed. + +# Annex A (informative): Change History + +| Date | TSG# | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------------|-------|-----------|------|-----|-----|--------------------------------------------|--------| +| December 2015 | | | | | | Creation of Rel-13 version based on 12.0.0 | 13.0.0 | +| | GP-68 | GP-151155 | 0022 | 1 | B | Introduction of Power Efficient Operation | 13.0.0 | +| February 2016 | GP-69 | GP-160063 | 0023 | | F | Miscellaneous corrections to eDRX | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48060/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/48_series/48060/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b7bc0c2d2ff189ba0b8f4471b7e604bd80179ca --- /dev/null +++ b/marked/Rel-16/48_series/48060/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b6139fdf0fd2f8d49bb88c2da2059a53f43639ae97a346fcaeaa48bc0f056a2 +size 183548 diff --git a/marked/Rel-16/48_series/48060/5addeb78101c342bb315dc3d703eec27_img.jpg b/marked/Rel-16/48_series/48060/5addeb78101c342bb315dc3d703eec27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3c28b5f1baac8962043e4a40832a79f9d9ccd0e --- /dev/null +++ b/marked/Rel-16/48_series/48060/5addeb78101c342bb315dc3d703eec27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8504180edc7c2e0d9b88fff8863d85631d60d7e55a027d63c592fda4d84b1899 +size 15081 diff --git a/marked/Rel-16/48_series/48060/6b95a21425e452581ef1a50ee2a6d391_img.jpg b/marked/Rel-16/48_series/48060/6b95a21425e452581ef1a50ee2a6d391_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5ac950962db7ee947ee0251e38ba63eb9148c2e --- /dev/null +++ b/marked/Rel-16/48_series/48060/6b95a21425e452581ef1a50ee2a6d391_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cd91df15670c1e7082073df98cf27cf548af2a4d657249b5a491a80f81e4ad9 +size 20739 diff --git a/marked/Rel-16/48_series/48060/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/48_series/48060/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3ccc488016c331c7dc41a3ded0f01e181380220 --- /dev/null +++ b/marked/Rel-16/48_series/48060/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7929c553f6428a43613f9dd35cc22b5cf8b553522082b4d71c7c2f649856179f +size 26354 diff --git a/marked/Rel-16/48_series/48060/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/48_series/48060/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f39b5a0fdcf80ce8680c4ce1e1e20c2001e5a9e --- /dev/null +++ b/marked/Rel-16/48_series/48060/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9abf43ca9e72d3423dcc1cd287fc6ff7493832deaa84e0d549e1501d44580dcb +size 114985 diff --git a/marked/Rel-16/48_series/48060/raw.md b/marked/Rel-16/48_series/48060/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..74c8d881add92d6470873ba7e6279558b4036730 --- /dev/null +++ b/marked/Rel-16/48_series/48060/raw.md @@ -0,0 +1,2070 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 5 | +| 2 References..... | 6 | +| 3 Abbreviations ..... | 7 | +| 4 General Approach ..... | 8 | +| 5 Frame Structure..... | 10 | +| 5.1 Frames for Speech Services ..... | 10 | +| 5.1.1 Frames for Full Rate and Enhanced Full Rate Speech..... | 10 | +| 5.1.2 Frames for Adaptive Multi-Rate Speech (AMR-NB) ..... | 11 | +| 5.1.3 Frames for Adaptive Multi-Rate Wideband Speech (AMR-WB) (16 kbit/s) ..... | 11 | +| 5.1.4 Frames for Adaptive Multi-Rate Wideband Speech (AMR-WB) (32 kbit/s) ..... | 11 | +| 5.1.5 Frames for Speech Codec Configuration Exchange..... | 12 | +| 5.2 O&M Frames..... | 13 | +| 5.3 Data Frames..... | 14 | +| 5.3.1 Data Frame (for Synchronisation) ..... | 14 | +| 5.3.2 Extended data frame (E-TRAU : data transport)..... | 15 | +| 5.4 Idle Speech Frames ..... | 16 | +| 5.5 Coding..... | 16 | +| 5.5.1 Coding of Frames for Speech Services ..... | 17 | +| 5.5.1.1 Coding of Frames for Full Rate and Enhanced Full Rate Speech ..... | 17 | +| 5.5.1.1.1 Coding of Control bits (C-bits) ..... | 17 | +| 5.5.1.1.2 Coding of Data Bits (D-bits) ..... | 18 | +| 5.5.1.1.3 Time Alignment Bits (T1..T4) ..... | 18 | +| 5.5.1.2 Coding of Frames for Adaptive Multi-Rate Speech (AMR-NB) ..... | 19 | +| 5.5.1.2.1 Coding of Control bits (C-bits) ..... | 19 | +| 5.5.1.2.2 Coding of Data bits (D-bits)..... | 21 | +| 5.5.1.2.3 Time Alignment Bits (T1..T4) ..... | 24 | +| 5.5.1.3 Coding of Frames for Adaptive Multi-Rate Wide Band Speech (AMR-WB) for 16kbit/s and 32kbit/s sub-multiplexing ..... | 25 | +| 5.5.1.3.1 Coding of Control bits (C-bits) ..... | 25 | +| 5.5.1.3.2 Coding of Data bits (D-bits)..... | 26 | +| 5.5.1.3.3 Time Alignment Bits (T1a..T4a)..... | 29 | +| 5.5.1.4 void ..... | 29 | +| 5.5.1.5 Coding of Configuration Frames ..... | 29 | +| 5.5.2 Coding of O&M Frames..... | 29 | +| 5.5.3 Coding of Data Frames..... | 30 | +| 5.5.4 Coding of Extended Data Frames..... | 30 | +| 5.5.5 Coding of Idle Speech Frames ..... | 31 | +| 5.6 Order of Bit Transmission..... | 31 | +| 6 Procedures..... | 31 | +| 6.1 Remote Control of Transcoders and Rate Adaptors..... | 31 | +| 6.2 Resource Allocation ..... | 32 | +| 6.3 Resource Release..... | 32 | +| 6.4 In Call Modification ..... | 33 | +| 6.5 Transfer of Idle Frames, Handling of Missing Data ..... | 33 | +| 6.5.1 In Full Rate data case ..... | 33 | +| 6.5.2 In Full Rate speech case ..... | 33 | +| 6.5.3 In Enhanced Full Rate speech case..... | 33 | +| 6.5.4 In Adaptive Multi-Rate speech case..... | 33 | +| 6.5.5 In Adaptive Multi-Rate Wideband speech case ..... | 33 | +| 6.6 Procedures for Speech Services ..... | 34 | +| 6.6.1 Time Alignment of Speech Service Frames..... | 34 | +| 6.6.1.1 Initial Time Alignment State ..... | 34 | +| 6.6.1.2 The Static Time Alignment State..... | 35 | +| 6.6.1.2.1 Phase Alignment of Codec_Mode_Indication for AMR or AMR-WB ..... | 35 | + +| | | | +|------------------------|-----------------------------------------------------------------------------------------------------|----| +| 6.6.1.3 | Initiation at Resource Allocation ..... | 37 | +| 6.6.1.4 | Time Alignment During Handover..... | 37 | +| 6.6.1.4.1 | BSS External Handover ..... | 37 | +| 6.6.1.4.2 | BSS Internal Handover..... | 37 | +| 6.6.2 | Procedures for Discontinuous Transmission (DTX) ..... | 37 | +| 6.6.2.1 | DTX procedures in the uplink direction ..... | 38 | +| 6.6.2.2 | DTX procedures in the downlink direction ..... | 38 | +| 6.7 | Procedures for Data Frames ..... | 38 | +| 6.7.1 | 9.6 and 4.8 kbit/s channel coding ..... | 38 | +| 6.7.1.1 | The RAA Function..... | 39 | +| 6.7.1.2 | The RA1/RA1' Function ..... | 40 | +| 6.7.1.3 | The RA2 Function ..... | 40 | +| 6.7.1.4 | Procedures for 8 kbit/s intermediate rate adaption rate ..... | 40 | +| 6.7.1.5 | Procedures for 16 kbit/s intermediate rate adaption rate ..... | 40 | +| 6.7.1.6 | Support of Non-Transparent Bearer Applications ..... | 40 | +| 6.7.2 | 14.5 kbit/s channel coding..... | 41 | +| 6.7.2.1 | The RAA' Function ..... | 41 | +| 6.7.2.2 | The RA1'/RAA' Function..... | 41 | +| 6.7.2.3 | The RA2 Function ..... | 41 | +| 6.8 | Frame Synchronization ..... | 41 | +| 6.8.1 | Search for Frame Synchronization ..... | 41 | +| 6.8.2 | Frame Synchronization After Performing Downlink Timing Adjustments ..... | 41 | +| 6.8.3 | Frame Synchronization Monitoring and Recovery ..... | 42 | +| 6.9 | Correction/detection of bit errors on the terrestrial circuits ..... | 43 | +| 6.9.1 | Error Detection on the Control Bits..... | 43 | +| 6.9.1.1 | General Procedure..... | 43 | +| 6.9.1.2 | Frames for Speech Services..... | 43 | +| 6.9.2 | Handling of frames received with errors ..... | 44 | +| 6.9.2.1 | In case of Full Rate speech ..... | 44 | +| 6.9.2.2 | In case of Enhanced Full Rate, Adaptive Multi-Rate and Adaptive Multi-Rate Wideband speech
..... | 44 | +| 6.10 | Procedures for Operation & Maintenance..... | 44 | +| 6.10.1 | Transfer of O&M Information Between the TRAU and the BSC..... | 44 | +| 6.10.2 | Procedures in the TRAU ..... | 45 | +| 6.10.3 | Procedures in the BSC..... | 45 | +| 6.10.3.1 | Use of O&M Frames..... | 45 | +| 6.10.4 | Procedures in the BTS ..... | 45 | +| Annex A (informative): | Change History..... | 46 | + +# --- 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 + +When 64 kbit/s traffic channels are used on the Abis interface, the speech shall be coded according to CCITT Recommendation G.711 and the data rate adaptation shall be as specified in 3GPP TS 44.021 and 3GPP TS 48.020. + +In the case where 16 kbit/s traffic channels are used for full rate speech, enhanced full rate speech, Adaptive Multi-Rate speech, Adaptive Multi-Rate Wideband speech or full rate data service, then the present document shall apply for frame structure and for control of remote transcoders and additional rate adaptors. + +For Adaptive Multi-Rate speech the present document specifies the 16 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS, TCH/AHS, TCH/WFS and O-TCH/WHS). The specification for 8 kBit/s submultiplexing is given in 3GPP TS 48.061, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). + +Additionally, the present document specifies the 32 kBit/s submultiplexing for Adaptive Multi-Rate Wideband speech. However it reuses the frame structure of the 16 kBit/s submultiplexing for Adaptive Multi-Rate speech. + +The use and general aspects of the Abis interface are given in 3GPP TS 48.051. + +NOTE: The present document should be considered together with the 3GPP TS 06 series of specifications, 3GPP TS 44.021 (Rate Adaptation on the MS-BSS Interface) and 3GPP TS 48.020 (Rate Adaptation on the BS/MSC 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 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification". +- [3] 3GPP TS 44.021: "Rate adaption on the Mobile Station +- [4] Void. +- [5] 3GPP TS 46.010: "Full rate speech; Transcoding". +- [6] 3GPP TS 46.011: "Full rate speech; Substitution and muting of lost frames for full rate speech channels". +- [7] 3GPP TS 46.012: "Full rate speech; Comfort noise aspect for full rate speech traffic channels". +- [8] 3GPP TS 46.031: "Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels". +- [9] 3GPP TS 46.032: "Voice Activity Detector (VAD)". +- [10] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [11] 3GPP TS 48.051: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; General aspects". +- [12] 3GPP TS 48.054: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 1 structure of physical circuits". +- [13] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification". +- [14] 3GPP TS 12.21: "Network Management (NM) procedures and message on the A-bis interface". +- [15] CCITT Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". +- [16] CCITT Recommendation I.460: "Multiplexing, rate adaption and support of existing interfaces". +- [17] CCITT Recommendation V.110: "Support of data terminal equipments (DTEs) with V-Series interfaces by an integrated services digital network". +- [18] Void. +- [19] 3GPP TS 46.060: "Enhanced Full rate speech transcoding". +- [20] 3GPP TS 46.061: "Substitution and muting of lost frames for Enhanced Full rate speech channels". +- [21] 3GPP TS 46.062: "Comfort noise aspect for Enhanced Full rate speech traffic channels". +- [22] 3GPP TS 46.081: "Discontinuous Transmission (DTX) for Enhanced Full rate speech traffic channel". +- [23] 3GPP TS 46.082: "Voice Activity Detection (VAD)". +- [24] Void. +- [25] 3GPP TS 26.090: "Adaptive Multi-Rate speech transcoding". +- [26] 3GPP TS 26.091: "Substitution and muting of lost frames for Adaptive Multi-Rate speech traffic channels". +- [27] 3GPP TS 26.092: "Comfort noise aspect for Adaptive Multi-Rate speech traffic channels". +- [28] 3GPP TS 26.093: "Discontinuous Transmission (DTX) for Adaptive Multi-Rate speech traffic channels". + +- [29] 3GPP TS 26.094: "Voice Activity Detection (VAD) for Adaptive Multi-Rate speech traffic channels ". +- [30] 3GPP TS 45.009: "Link Adaptation". +- [31] 3GPP TS 48.061: "Inband control of remote transcoders and rate adaptors (half rate)". +- [32] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of Speech Codecs". +- [33] 3G 26.171: "Digital cellular telecommunications system; Adaptive Multi-Rate Wideband speech processing functions, General Description." +- [34] 3G 26.190: "Digital cellular telecommunications system; Adaptive Multi-Rate Wideband speech transcoding". +- [35] 3G 26.191: "Digital cellular telecommunications system; Substitution and muting of lost frames for Adaptive Multi-Rate Wideband speech traffic channels". +- [36] 3G 26.192: "Digital cellular telecommunications system; Comfort noise aspect for Adaptive Multi-Rate Wideband speech traffic channels". +- [37] 3G 26.193: "Digital cellular telecommunications system; Discontinuous Transmission (DTX) for Adaptive Multi-Rate Wideband speech traffic channels". +- [38] 3G 26.194: "Digital cellular telecommunications system; Voice Activity Detection (VAD) for Adaptive Multi-Rate Wideband speech traffic channels ". + +# --- 3 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905. Additionally: + +AMR Adaptive Multi-Rate +AMR-WB Adaptive Multi-Rate Wideband +CMC Codec\_Mode\_Command +CMI Codec\_Mode\_Indication +CMR Codec\_Mode\_Request +Onset Speech Onset Frame Classification +PAB Phase Alignment Bit +PAC Phase Alignment Command +RATSCCH Robust AMR Traffic Synchronised Control CHannel +RIF Request or Indication Flag +TAC Time Alignment Command +TAE Time Alignment Extension +TFO Tandem Free Operation +TFOE TFO Enable +UFE Uplink Frame Error + +# --- 4 General Approach + +When the transcoders/rate adaptors are positioned remote to the BTS, the information between the Channel Codec Unit (CCU) and the remote Transcoder/Rate Adaptor Unit (TRAU) is transferred in frames with a fixed length of 320 bits (20 ms). In the present document, these frames are denoted "TRAU frames". Within these frames, both the speech/data and the TRAU associated control signals are transferred. + +The Abis interface should be the same if the transcoder is positioned 1) at the MSC site of the BSS or if it is positioned 2) at the BSC site of the BSS. In case 1), the BSC should be considered as transparent for 16 kbit/s channels. + +In case of 4,8 and 9,6 kbit/s channel coding when data is adapted to the 320 bit frames, a conversion function is required in addition to the conversion/rate adaption specified in 3GPP TS 48.020. This function constitutes the RAA. In case of 14,5 kbit/s channel coding, no RAA rate adaption is required because V.110 framing is not used. + +The TRAU is considered a part of the BSC, and the signalling between the BSC and the TRAU (e.g. detection of call release, handover and transfer of O&M information) may be performed by using BSC internal signals. The signalling between the CCU and the TRAU, using TRAU frames as specified in the present document, is mandatory when the Abis interface is applied. + +NOTE: If standard 64 kbit/s switching is used in the BSC, multiplexing according to CCITT Recommendation I.460 should apply at both sides of the switch. + +In figure 4.1, a possible configuration of the TRAU and the CCU is shown. + +The functions inside the TRAU are: + +- "Remote Transcoder and Rate Adaptor Control Function" (RTRACF); +- "Remote Speech Handler Function" (RSHF); +- The RAA function in case of 4.8 and 9.6 kbit/s channel coding; +- The RAA' function in case of 14.5 kbit/s channel coding; +- The RA2 function; +- The transcoder function. +- Optionally the TFO functions (see 3GPP TS 28.062). + +The functions inside the CCU are: + +- "Transcoder and Rate Adaptor Control Function" (TRACF); +- "Speech Handler Function" (SHF); +- The RAA function in case of 4.8 and 9.6 kbit/s channel coding; +- The RA1/RA1' function in case of 4.8 and 9.6 kbit/s channel coding; +- The RA1'/RAA' function in case of 14.5 kbit/s channel coding; +- The channel codec function; +- If AMR or AMR-WB is supported, the Link Adaptation (see 3GPP TS 45.009). + +The present document will not describe the procedures inside the TRAU and the CCU. The layout in figure 4.1 is only intended as a reference model. + +![Functional entities diagram for BSC and BTS showing TRAU, CCU, and various control functions connected via Abis interface.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the functional entities for handling remote control of remote transcoders and rate adaptors, divided into BSC (Base Station Controller) and BTS (Base Transceiver Station) components. + +**BSC (Base Station Controller):** + +- TRAU (TRANSCODER/RA UNIT):** Contains two main functional blocks: + - Trans-coder Function (Note):** Receives **Speech** from the left (labeled **64 kbit/s**) and **Data** from below. It has bidirectional connections to the **Remote Transcoder and RA Contr. Fn.** block. + - Remote Speech Handler Function:** Has bidirectional connections to the **Remote Transcoder and RA Contr. Fn.** block. +- Remote Transcoder and RA Contr. Fn.:** A central control block that connects to the TRAU functions and to the **RAA** and **RA2** rate adaptors. It has a bidirectional connection to the **Abis** interface. +- RA2** and **RAA:** Rate adaptors located at the bottom of the TRAU unit, connected to the control function. + +**Abis Interface:** The connection between BSC and BTS, labeled with **16 Kbit/s**, **320 bit/**, and **20 mS**. + +**BTS (Base Transceiver Station):** + +- CCU (CHANNEL CODEC UNIT):** Contains several functional blocks: + - Speech Handler Function:** Receives **Speech** from the right and has bidirectional connections to the **Trans-coder and RA Control Function**. + - Trans-coder and RA Control Function:** Receives data from the **Abis** interface and has bidirectional connections to the **Speech Handler Function**, **RAA**, and **RA1**. It also sends **L3 Control signals** to the **Channel Codec Function**. + - RAA**, **RA1**, and **RA1':** Rate adaptors at the bottom, with **Data** input. **RAA** connects to the control function, while **RA1** and **RA1'** are connected to each other and the data input. + - Channel Codec Function:** Receives **L3 Control signals** and data from the control function, and outputs **Radio frames** to the right. + +**Legend:** + +- Speech/data (represented by a solid line) +- Control (represented by a dashed line) + +Functional entities diagram for BSC and BTS showing TRAU, CCU, and various control functions connected via Abis interface. + +NOTE: This recommendation assumes the DTX handler function to be a part of the Transcoder Function. + +Figure GSM 08.60/2.1: Functional entities for handling of remote control of remote transcoders and rate adaptors + +Figure 4.1: Functional entities for handling of remote control of remote transcoders and rate adaptors + +NOTE: This figure applies only for 4,8 and 9,6 kbit/s channel coding. + +# 5 Frame Structure + +## 5.1 Frames for Speech Services + +### 5.1.1 Frames for Full Rate and Enhanced Full Rate Speech + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 3 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | +| 4 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | +| 5 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | +| 6 | 1 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | +| 7 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | +| 8 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | D37 | +| 9 | D38 | D39 | D40 | D41 | D42 | D43 | D44 | D45 | +| 10 | 1 | D46 | D47 | D48 | D49 | D50 | D51 | D52 | +| 11 | D53 | D54 | D55 | D56 | D57 | D58 | D59 | D60 | +| 12 | 1 | D61 | D62 | D63 | D64 | D65 | D66 | D67 | +| 13 | D68 | D69 | D70 | D71 | D72 | D73 | D74 | D75 | +| 14 | 1 | D76 | D77 | D78 | D79 | D80 | D81 | D82 | +| 15 | D83 | D84 | D85 | D86 | D87 | D88 | D89 | D90 | +| 16 | 1 | D91 | D92 | D93 | D94 | D95 | D96 | D97 | +| 17 | D98 | D99 | D100 | D101 | D102 | D103 | D104 | D105 | +| 18 | 1 | D106 | D107 | D108 | D109 | D110 | D111 | D112 | +| 19 | D113 | D114 | D115 | D116 | D117 | D118 | D119 | D120 | +| 20 | 1 | D121 | D122 | D123 | D124 | D125 | D126 | D127 | +| 21 | D128 | D129 | D130 | D131 | D132 | D133 | D134 | D135 | +| 22 | 1 | D136 | D137 | D138 | D139 | D140 | D141 | D142 | +| 23 | D143 | D144 | D145 | D146 | D147 | D148 | D149 | D150 | +| 24 | 1 | D151 | D152 | D153 | D154 | D155 | D156 | D157 | +| 25 | D158 | D159 | D160 | D161 | D162 | D163 | D164 | D165 | +| 26 | 1 | D166 | D167 | D168 | D169 | D170 | D171 | D172 | +| 27 | D173 | D174 | D175 | D176 | D177 | D178 | D179 | D180 | +| 28 | 1 | D181 | D182 | D183 | D184 | D185 | D186 | D187 | +| 29 | D188 | D189 | D190 | D191 | D192 | D193 | D194 | D195 | +| 30 | 1 | D196 | D197 | D198 | D199 | D200 | D201 | D202 | +| 31 | D203 | D204 | D205 | D206 | D207 | D208 | D209 | D210 | +| 32 | 1 | D211 | D212 | D213 | D214 | D215 | D216 | D217 | +| 33 | D218 | D219 | D220 | D221 | D222 | D223 | D224 | D225 | +| 34 | 1 | D226 | D227 | D228 | D229 | D230 | D231 | D232 | +| 35 | D233 | D234 | D235 | D236 | D237 | D238 | D239 | D240 | +| 36 | 1 | D241 | D242 | D243 | D244 | D245 | D246 | D247 | +| 37 | D248 | D249 | D250 | D251 | D252 | D253 | D254 | D255 | +| 38 | 1 | D256 | D257 | D258 | D259 | D260 | C16 | C17 | +| 39 | C18 | C19 | C20 | C21 | T1 | T2 | T3 | T4 | + +### 5.1.2 Frames for Adaptive Multi-Rate Speech (AMR-NB) + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 3 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | +| 4 | 1 | C16 | C17 | C18 | C19 | C20 | C21 | C22 | +| 5 | C23 | C24 | C25 | D1 | D2 | D3 | D4 | D5 | +| 6 | 1 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | +| 7 | D13 | D14 | D15 | D16 | D17 | D18 | D19 | D20 | +| 8 | 1 | D21 | D22 | D23 | D24 | D25 | D26 | D27 | +| 9 | D28 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | +| 10 | 1 | D36 | D37 | D38 | D39 | D40 | D41 | D42 | +| 11 | D43 | D44 | D45 | D46 | D47 | D48 | D49 | D50 | +| 12 | 1 | D52 | D52 | D53 | D54 | D55 | D56 | D57 | +| 13 | D58 | D59 | D60 | D61 | D62 | D63 | D64 | D65 | +| 14 | 1 | D66 | D67 | D68 | D69 | D70 | D71 | D72 | +| 15 | D73 | D74 | D75 | D76 | D77 | D78 | D79 | D80 | +| 16 | 1 | D81 | D82 | D83 | D84 | D85 | D86 | D87 | +| 17 | D88 | D89 | D90 | D91 | D92 | D93 | D94 | D95 | +| 18 | 1 | D96 | D97 | D98 | D99 | D100 | D101 | D102 | +| 19 | D103 | D104 | D105 | D106 | D107 | D108 | D109 | D110 | +| 20 | 1 | D111 | D112 | D113 | D114 | D115 | D116 | D117 | +| 21 | D118 | D119 | D120 | D121 | D122 | D123 | D124 | D125 | +| 22 | 1 | D126 | D127 | D128 | D129 | D130 | D131 | D132 | +| 23 | D133 | D134 | D135 | D136 | D137 | D138 | D139 | D140 | +| 24 | 1 | D141 | D142 | D143 | D144 | D145 | D146 | D147 | +| 25 | D148 | D149 | D150 | D151 | D152 | D153 | D154 | D155 | +| 26 | 1 | D156 | D157 | D158 | D159 | D160 | D161 | D162 | +| 27 | D163 | D164 | D165 | D166 | D167 | D168 | D169 | D170 | +| 28 | 1 | D171 | D172 | D173 | D174 | D175 | D176 | D177 | +| 29 | D178 | D179 | D180 | D181 | D182 | D183 | D184 | D185 | +| 30 | 1 | D186 | D187 | D188 | D189 | D190 | D191 | D192 | +| 31 | D193 | D194 | D195 | D196 | D197 | D198 | D199 | D200 | +| 32 | 1 | D201 | D202 | D203 | D204 | D205 | D206 | D207 | +| 33 | D208 | D209 | D210 | D211 | D212 | D213 | D214 | D215 | +| 34 | 1 | D216 | D217 | D218 | D219 | D220 | D221 | D222 | +| 35 | D223 | D224 | D225 | D226 | D227 | D228 | D229 | D230 | +| 36 | 1 | D231 | D232 | D233 | D234 | D235 | D236 | D237 | +| 37 | D238 | D239 | D240 | D241 | D242 | D243 | D244 | D245 | +| 38 | 1 | D246 | D247 | D248 | D249 | D250 | D251 | D252 | +| 39 | D253 | D254 | D255 | D256 | T1 | T2 | T3 | T4 | + +### 5.1.3 Frames for Adaptive Multi-Rate Wideband Speech (AMR-WB) (16 kbit/s) + +The frame format for AMR-NB shall be used for all frames for AMR-WB as well, see chapters 5.1.2 and 5.5.1.3. + +### 5.1.4 Frames for Adaptive Multi-Rate Wideband Speech (AMR-WB) (32 kbit/s) + +The frame format for AMR-NB shall be used for all frames for AMR-WB as well, see chapters 5.1.2 and 5.5.1.3. In case of the AMR-WB modes 15.85 and 23.85 two 16kbit/s frames (channel “a” and channel “b”) are used to compose a 32kbit/s frame. + +### 5.1.5 Frames for Speech Codec Configuration Exchange + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|------|------|------|----|----|----|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | D1 | D2 | +| 3 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | D10 | +| 4 | 1 | | | | | | | | +| 5 | | | | | | | | D25 | +| 6 | 1 | | | | | | | | +| 7 | | | | | | | | D40 | +| 8 | 1 | | | | | | | | +| 9 | | | | | | | | D55 | +| 10 | 1 | | | | | | | | +| 11 | | | | | | | | D70 | +| 12 | 1 | | | | | | | | +| 13 | | | | | | | | D85 | +| 14 | 1 | | | | | | | | +| 15 | | | | | | | | D100 | +| 16 | 1 | | | | | | | | +| 17 | | | | | | | | D115 | +| 18 | 1 | | | | | | | | +| 19 | | | | | | | | D130 | +| 20 | 1 | | | | | | | | +| 21 | | | | | | | | D145 | +| 22 | 1 | | | | | | | | +| 23 | | | | | | | | D160 | +| 24 | 1 | | | | | | | | +| 25 | | | | | | | | D175 | +| 26 | 1 | | | | | | | | +| 27 | | | | | | | | D190 | +| 28 | 1 | | | | | | | | +| 29 | | | | | | | | D205 | +| 30 | 1 | | | | | | | | +| 31 | | | | | | | | D220 | +| 32 | 1 | | | | | | | | +| 33 | | | | | | | | D235 | +| 34 | 1 | | | | | | | | +| 35 | | | | | | | | D250 | +| 36 | 1 | | | | | | | | +| 37 | | | | | | | | D265 | +| 38 | 1 | | | | | | | D272 | +| 39 | D273 | D274 | D275 | D276 | T1 | T2 | T3 | T4 | + +## 5.2 O&M Frames + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 3 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | +| 4 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | +| 5 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | +| 6 | 1 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | +| 7 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | +| 8 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | D37 | +| 9 | D38 | D39 | D40 | D41 | D42 | D43 | D44 | D45 | +| 10 | 1 | D46 | D47 | D48 | D49 | D50 | D51 | D52 | +| 11 | D53 | D54 | D55 | D56 | D57 | D58 | D59 | D60 | +| 12 | 1 | D61 | D62 | D63 | D64 | D65 | D66 | D67 | +| 13 | D68 | D69 | D70 | D71 | D72 | D73 | D74 | D75 | +| 14 | 1 | D76 | D77 | D78 | D79 | D80 | D81 | D82 | +| 15 | D83 | D84 | D85 | D86 | D87 | D88 | D89 | D90 | +| 16 | 1 | D91 | D92 | D93 | D94 | D95 | D96 | D97 | +| 17 | D98 | D99 | D100 | D101 | D102 | D103 | D104 | D105 | +| 18 | 1 | D106 | D107 | D108 | D109 | D110 | D111 | D112 | +| 19 | D113 | D114 | D115 | D116 | D117 | D118 | D119 | D120 | +| 20 | 1 | D121 | D122 | D123 | D124 | D125 | D126 | D127 | +| 21 | D128 | D129 | D130 | D131 | D132 | D133 | D134 | D135 | +| 22 | 1 | D136 | D137 | D138 | D139 | D140 | D141 | D142 | +| 23 | D143 | D144 | D145 | D146 | D147 | D148 | D149 | D150 | +| 24 | 1 | D151 | D152 | D153 | D154 | D155 | D156 | D157 | +| 25 | D158 | D159 | D160 | D161 | D162 | D163 | D164 | D165 | +| 26 | 1 | D166 | D167 | D168 | D169 | D170 | D171 | D172 | +| 27 | D173 | D174 | D175 | D176 | D177 | D178 | D179 | D180 | +| 28 | 1 | D181 | D182 | D183 | D184 | D185 | D186 | D187 | +| 29 | D188 | D189 | D190 | D191 | D192 | D193 | D194 | D195 | +| 30 | 1 | D196 | D197 | D198 | D199 | D200 | D201 | D202 | +| 31 | D203 | D204 | D205 | D206 | D207 | D208 | D209 | D210 | +| 32 | 1 | D211 | D212 | D213 | D214 | D215 | D216 | D217 | +| 33 | D218 | D219 | D220 | D221 | D222 | D223 | D224 | D225 | +| 34 | 1 | D226 | D227 | D228 | D229 | D230 | D231 | D232 | +| 35 | D233 | D234 | D235 | D236 | D237 | D238 | D239 | D240 | +| 36 | 1 | D241 | D242 | D243 | D244 | D245 | D246 | D247 | +| 37 | D248 | D249 | D250 | D251 | D252 | D253 | D254 | D255 | +| 38 | 1 | D256 | D257 | D258 | D259 | D260 | D261 | D262 | +| 39 | D263 | D264 | S1 | S2 | S3 | S4 | S5 | S6 | + +## 5.3 Data Frames + +### 5.3.1 Data Frame (for Synchronisation) + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|----|-------------------------------------------------------------------------|-----|-----|-----|-----|-----| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 3 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | +| 4 | 1 | | | | | | | . | +| 5 | 1 | | | | | | | . | +| 6 | 1 | | | | | | | . | +| 7 | 1 | | Data frame position 1
63 bits.
(72 bits including bit position 1) | | | | | | +| 8 | 1 | | | | | | | | +| 9 | 1 | | | | | | | | +| 10 | 1 | | | | | | | | +| 11 | 1 | | | | | | | | +| 12 | 1 | | | | | | | | +| 13 | 1 | | | | | | | | +| 14 | 1 | | | | | | | | +| 15 | 1 | | | | | | | | +| 16 | 1 | | Data frame position 2 | | | | | | +| 17 | 1 | | | | | | | | +| 18 | 1 | | | | | | | | +| 19 | 1 | | | | | | | | +| 20 | 1 | | | | | | | | +| 21 | 1 | | | | | | | | +| 22 | 1 | | | | | | | | +| 23 | 1 | | | | | | | | +| 24 | 1 | | | | | | | | +| 25 | 1 | | Data frame position 3 | | | | | | +| 26 | 1 | | | | | | | | +| 27 | 1 | | | | | | | | +| 28 | 1 | | | | | | | | +| 29 | 1 | | | | | | | | +| 30 | 1 | | | | | | | | +| 31 | 1 | | | | | | | | +| 32 | 1 | | | | | | | | +| 33 | 1 | | Data frame position 4 | | | | | | +| 34 | 1 | | | | | | | | +| 35 | 1 | | | | | | | | +| 36 | 1 | | | | | | | | +| 37 | 1 | | | | | | | | +| 38 | 1 | | | | | | | | +| 39 | 1 | | | | | | | | + +### 5.3.2 Extended data frame (E-TRAU : data transport) + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|----|-----|-----|-----|-----|----|----| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 3 | C8 | C9 | C10 | C11 | C12 | C13 | M1 | M2 | +| 4 | D1 | D2 | ... | | | | | | +| 5 | | | | | | | | | +| 6 | | | | | | | | | +| 7 | | | | | | | | | +| 8 | | | | | | | | | +| 9 | | | | | | | | | +| 10 | | | | | | | | | +| 11 | | | | | | | | | +| 12 | | | | | | | | | +| 13 | | | | | | | | | +| 14 | | | | | | | | | +| 15 | | | | | | | | | +| 16 | | | | | | | | | +| 17 | | | | | | | | | +| 18 | | | | | | | | | +| 19 | | | | | | | | | +| 20 | | | | | | | | | +| 21 | | | | | | | | | +| 22 | | | | | | | | | +| 23 | | | | | | | | | +| 24 | | | | | | | | | +| 25 | | | | | | | | | +| 26 | | | | | | | | | +| 27 | | | | | | | | | +| 28 | | | | | | | | | +| 29 | | | | | | | | | +| 30 | | | | | | | | | +| 31 | | | | | | | | | +| 32 | | | | | | | | | +| 33 | | | | | | | | | +| 34 | | | | | | | | | +| 35 | | | | | | | | | +| 36 | | | | | | | | | +| 37 | | | | | | | | | +| 38 | | | | | | | | | +| 39 | | | | | | | | | + +Data block of 288 data bits and M1, M2. + +... D287 D288 + +## 5.4 Idle Speech Frames + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|-----|-----|-----|-----|-----|-----|-----| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 3 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | +| 4 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 5 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 6 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 7 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 8 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 9 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 10 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 11 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 12 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 13 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 14 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 15 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 16 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 17 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 18 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 19 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 20 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 21 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 22 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 23 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 24 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 25 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 26 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 27 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 28 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 29 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 30 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 31 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 32 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 33 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 34 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 35 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 36 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 37 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 38 | 1 | 1 | 1 | 1 | 1 | 1 | C16 | C17 | +| 39 | C18 | C19 | C20 | C21 | T1 | T2 | T3 | T4 | + +## 5.5 Coding + +In the following clauses, the coding of the frames is described. Any spare or not used control bits should be coded binary "1". + +For all frame types the octet 0, 1 and the first bit of octets 2, 4, 6, 8, ... 38 are used as frame sync. + +### 5.5.1 Coding of Frames for Speech Services + +#### 5.5.1.1 Coding of Frames for Full Rate and Enhanced Full Rate Speech + +##### 5.5.1.1.1 Coding of Control bits (C-bits) + +| Description | Uplink | Downlink | +|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| Frame type
(Bits C1 - C5).
FR
EFR | C1C2C3C4 C5
Speech: 0 0 0 1 0.
Speech: 1 1 0 1 0 | C1C2C3C4 C5
Speech: 1 1 1 0 0
Speech: 1 1 0 1 0 | +| Time Alignment
(Bits C6 - C11) | Binary number indicating the required timing adjustment to be made in steps of 250/500 µs.

The following values apply for the coding
C6C7 . . . C11
0 0 0 0 0 0 No change in frame timing
0 0 0 0 0 1 Delay frame 1 x 500 µs
0 0 0 0 1 0 Delay frame 2 x 500 µs
. . . . .
. . . . .
1 0 0 1 1 1 Delay frame 39 x 500 µs
1 0 1 0 0 0 Not used
. . . . .
1 1 1 1 0 1 Not used
1 1 1 1 1 0 Delay frame 1 x 250 µs
1 1 1 1 1 1 Advance frame 250 µs | Binary number indicating the timing adjustment made. | +| Frame indicators. The definition and coding of these indicators are given in 3GPP TS 46.031. | C12: BFI
0 : BFI = 0
1 : BFI = 1 | C12 - C15: Spare | +| Bits C12 - C16 | C13 C14: SID
0 0 :SID = 0
0 1 :SID = 1
1 0 :SID = 2 | IF FR. Speech

ELSE
C12: UFE
0 :UFE=0 bad uplink frame
1 : UFE=1 good up-link frame | +| Downlink Uplink Frame Error (UFE) C12
(see clause 6.8.3) | C15: TAF
0 : TAF = 0
1 : TAF = 1 | C13 - C15: spare | +| | C16: Spare | C16: SP
0 : SP = 0
1 : SP = 1 | +| DTX indicator | C17: DTXd
0 : DTX not applied
1 : DTX applied | C17: Spare | +| Bits C18 - C21 | Spare | Spare | + +##### 5.5.1.1.2 Coding of Data Bits (D-bits) + +###### For Full Rate Speech: + +Bits D1 .. D260: Speech block transferred in the same order as output from the transcoder (see 3GPP TS 46.010). + +###### For Enhanced Full Rate Speech: + +The speech block is subdivided in five subsets. The order within a given subset is the same as output from the transcoder (see ETS 300 726, 3GPP TS 46.060). Three parity bits are added at the end of each sub-set. + +These parity bits are added to the bits of the subset, according to a degenerate (shortened) cyclic code using the generator polynomial: + +$$g(D) = D^3 + D + 1$$ + +The encoding of the cyclic code is performed in a systematic form which means that, in GF(2), the polynomial: + +$$d(m)D^n + d(m+1)D^{n-1} + \dots + d(m+n-3)D^3 + p(0)D^2 + p(1)D + p(2)$$ + +where $p(0)$ , $p(1)$ , $p(2)$ are the parity bits, when divided by $g(D)$ , yields a remainder equal to: + +$$1 + D + D^2$$ + +For every CRC, the transmission order is $p(0)$ first followed by $p(1)$ and $p(2)$ successively. + +- Bit D1 : spare (binary "1"). +- Bits D2...D39 : Indexes of the LSF submatrices. +- Bits D40...D42 : CRC over bits D1 to D22, D25 to D27 and D29. +- Bits D43...D95 : Indexes of the parameters of first sub-frame. +- Bits D96...D98 : CRC over bits D43 to D52, D91 and D92. +- Bits D99...D148 : Indexes of the parameters of second sub-frame. +- Bits D149...D151 : CRC over bits D99 to D103, D105, D144 and D145. +- Bits D152...D204 : Indexes of the parameters of third sub-frame. +- Bits D205...D207 : CRC over bits D152 to D161, D200 and D201. +- Bits D208...D257 : Indexes of the parameters of fourth sub-frame. +- Bits D258...D260 : CRC over bits D208 to D212, D214, D253 and D254. + +##### 5.5.1.1.3 Time Alignment Bits (T1...T4) + +Bits T1 .. T4: Bits positioned at the end of the downlink frames. If the timing of the frame is to be advanced 250 µs, these 4 bits are not transferred in order to reduce the frame length accordingly. When transferred the bits are set to binary "1". + +#### 5.5.1.2 Coding of Frames for Adaptive Multi-Rate Speech (AMR-NB) + +##### 5.5.1.2.1 Coding of Control bits (C-bits) + +| Control Bits | Description Uplink | Description Downlink | +|-----------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| C1...C5 | Frame_Type (Codec_Type) | Frame_Type (Codec_Type) | +| C6...C11 | Time Alignment Command (TAC) or Phase Alignment Control (PAC) or TFO Information or Handover Information | Time Alignment Command (TAC) or Phase Alignment Control (PAC) or TFO Information or Handover Information | +| C12 | Request or Indication Flag (RIF) | Request or Indication Flag (RIF) | +| C13 | spare, set to 1 | Uplink Frame Error (UFE) | +| C14 . C15 . C16 | Config_Prot | Config_Prot | +| C17 . C18 | Message_No | Message_No | +| C19 | DTX in downlink requested (DTXd) | spare, reserved for TFO (see 28.062) | +| C20 | TFO Enabled (TFOE) | spare, reserved for TFO (see 28.062) | +| C21 . C22 | Frame_Classification, Rx_Type | Frame_Classification, Tx_Type | +| C23 . C24 . C25 | Codec_Mode_Indication (RIF == 0) or Codec_Mode_Request (RIF == 1) or 0.0.0 (Frame_Classification == 0.0) | Codec_Mode_Indication (RIF == 0) or Codec_Mode_Request (RIF == 1) or 0.0.0 (Frame_Classification == 0.0) | + +Detailed Description: + +###### Frame Type: + +The coding of the Frame\_Type (also called "Codec\_Type") for AMR is identical in uplink and downlink. + +C1...C5: + +**0.0.1.1.0:** Adaptive Multi-Rate Codec. + +###### Time Alignment Field: + +The Time Alignment Field (Bits C6...C11) is used to carry either the Time Alignment Command (TAC), the Phase Alignment Control (PAC) or the TFO and Handover Information. The Time Alignment Command is coded as for the Full Rate and Enhanced Full Rate (clause 5.5.1.1.1). + +###### Time Alignment Command (TAC): + +In the uplink direction (BTS to TRAU) the TAC indicates the required timing adjustment for the downlink TRAU frame to be made by the TRAU in 250/500µs steps. + +C6...C11: + +**0.0.0.0.0.0** No change in frame timing + +**0.0.0.0.0.1** Delay frame 1 x 500µs (send four additional T-Bit-pairs after the end of the TRAU Frame) + +**0.0.0.0.1.0** Delay frame 2 x 500µs (send eight additional T-Bit-pairs after the end of the TRAU Frame) + +... + +**1.0.0.1.1.1** Delay frame 39 x 500µs (send 156 additional T-Bit-pairs after the end of the TRAU Frame) + +(1.0.1.0.0.0 to 1.1.0.1.1.1: 16 code-points, unused, reserved) + +(1.1.1.0.0.0 to 1.1.1.0.1.1: 4 code-points, reserved for TFO) + +(1.1.1.1.0.0 reserved for TFO) + +**(1.1.1.1.0.1)** reserved for AMR CMI/CMR Phase Alignment Command (PAC), no change in frame timing) + +**1.1.1.1.1.0** Delay frame by 250µs (send two additional T-Bit-pairs after the end of the TRAU Frame) + +**1.1.1.1.1.1** Advance frame by 250µs (do not send the two T-Bit-pairs at the end of the TRAU Frame). + +###### Phase Alignment Command (PAC) (useful when TFO is not supported or disabled): + +The Phase Alignment Command (PAC) can be used by the BTS to command the TRAU to change (invert) the phase of CMI/CMR, respectively RIF, in downlink TRAU frames, see clause 6.6.1.2.1. + +C6...C11: + +**1.1.1.1.0.1** AMR CMI/CMR Phase Alignment Command (PAC), no change in frame timing. + +In No\_Speech frames the Phase Alignment Command may optionally be transmitted by one additional bit (PAB, see subclause 5.5.1.2.2) that allows a direct time and phase alignment in one step. + +###### TFO Information (defined when TFO is supported, see 3GPP TS 28.062): + +C6...C11 + +**1.1.1.0.0.0** + +**1.1.1.0.0.1** + +**1.1.1.0.1.0** + +###### 1.1.1.0.1.1 + +##### 1.1.1.1.0.0 + +These five codes are reserved for Tandem Free Operation (see 3GPP TS 28.062). They result in no change in frame timing. If the BTS does not support TFO or TFO is disabled these codes shall not be used in uplink and shall be ignored in downlink. The procedure to exchange this information between BTS and TRAU is described in 3GPP TS 28.062. + +###### Request or Indication Flag (RIF): + +This flag indicates the phase of the Codec\_Mode\_Indication (RIF == 0) respectively the Codec\_Mode\_Request (RIF == 1). It has the same meaning in uplink and in downlink. Typically this flag toggles every frame. Exceptions may occur at handover and CMI/CMR phase alignment, see clause 6.6.1.2.1. + +###### Uplink Frame Error (UFE): + +In downlink the UFE indicates that the most recently received uplink TRAU frame had detectable errors. + +In uplink this bit shall be set to "1". + +UFE == 0: "Uplink Frame received with Errors"; + +UFE == 1: "Uplink Frame received without Errors". + +Note: the UFE is not related to the frame classification (Rx\_Type) as computed by the BTS radio receiver. It is related to inconsistencies in the TRAU frame synchronization, control bits or CRCs within the TRAU frame. + +###### Config\_Prot + +This field is reserved for the Configuration Protocol in case of Tandem Free Operation (see 3GPP TS 28.062). If the BTS does not support TFO or TFO is disabled, then this field shall be set to "0.0.0". + +###### Message\_No + +This field is reserved for the Configuration Protocol in case of Tandem Free Operation (see 3GPP TS 28.062). If the BTS does not support TFO or TFO is disabled, then this field shall be set to "0.0". + +###### DTX in downlink requested (DTXd) + +See clause 6.6.2.2. + +###### TFO Enabled (TFOE) + +This bit enables or disables Tandem Free Operation in the TRAU. If the BTS does not support TFO or TFO is disabled, then this bit shall be set to "0". Coding: + +TFOE == 0: TFO Disabled; + +TFOE == 1: TFO Enabled. + +###### Frame\_Classification: + +This field classifies the contents of the TRAU frame as seen by the radio receiver, see 3GPP TS 26.093: + +C21...C22: + +- | | | | | +|---|---|-------------------|-----------------------------------------------------| +| 1 | 1 | "Speech_Good" | the frame can be decoded without restriction | +| 1 | 0 | "Speech_Degraded" | the frame might contain undetected errors | +| 0 | 1 | "Speech_Bad" | the frame contains errors that can not be corrected | +| 0 | 0 | "No_Speech" | the frame is not a speech frame, see below. | + +In the uplink direction the Frame\_Classification is also called "Rx\_Type" and is always set by the BTS. + +In the downlink direction the Frame\_Classification is also called "Tx\_Type". + +If Tandem Free Operation is not ongoing, then the codes "Speech\_Degraded", and "Speech\_Bad" shall not be used in the downlink direction. If Tandem Free Operation is ongoing, then all codes may be used in the downlink direction. For the handling within the downlink BTS, see 3GPP TS 28.062). + +###### Codec\_Mode\_Indication / Codec\_Mode\_Request: + +This 3-bit field has three different meanings, depending on the Frame\_Classification field and the + +Request\_or\_Indication\_Flag (RIF): + +If Frame\_Classification is different than "0.0" then this field contains + +either the Codec\_Mode\_Indication (CMI), if RIF equals 0; + +or the Codec\_Mode\_Request (CMR), if RIF equals 1. + +If Frame\_Classification is equal to "0.0", i.e. when a No\_Speech frame is transmitted, then this field shall be set to "0.0.0". CMI and CMR are then simultaneously transmitted in the Data Bits. + +The coding is identical in uplink and downlink. + +C23 . C24. C25: + +- | | | | | +|---|---|---|------------------------| +| 0 | 0 | 0 | Codec_Mode 4,75 kBit/s | +| 0 | 0 | 1 | Codec_Mode 5,15 kBit/s | +| 0 | 1 | 0 | Codec_Mode 5,90 kBit/s | + +| | | | | +|---|---|---|------------------------| +| 0 | 1 | 1 | Codec_Mode 6,70 kBit/s | +| 1 | 0 | 0 | Codec_Mode 7,40 kBit/s | +| 1 | 0 | 1 | Codec_Mode 7,95 kBit/s | +| 1 | 1 | 0 | Codec_Mode 10,2 kBit/s | +| 1 | 1 | 1 | Codec_Mode 12,2 kBit/s | + +The CMI indicates the Codec\_Mode to be used for decoding the associated speech parameters in the same and the next frame. The CMR indicates the highest allowed Codec\_Mode to be used for encoding in the opposite direction. + +Note 1: In the TRAU frames, the Codec\_Mode\_Request, respectively the Codec\_Mode\_Indication are coded absolutely (three bits for eight possible modes). On the radio interface, because of bandwidth limitation, these parameters are coded with two bits only. The CCU shall perform the required translation. + +Note 2: In case of no Tandem Free Operation the uplink CMR is a Codec\_Mode\_Command (CMC) from the BTS to the TRAU and the TRAU shall try to follow the command as soon as possible. The only allowed exception is in case of DTX when SID or No\_Data frames can be used during speech pauses. In the downlink direction the CMR is typically set by the TRAU to "1.1.1". This CMR from the TRAU must be combined with the corresponding CMR for the local uplink direction, see 3GPP TS 45.009 and 28.062, before it is sent down to the MS. + +Note 3: In case of an ongoing Tandem Free Operation, the local uplink CMR is an indication from the local BTS to the TRAU, respectively to the distant BTS, on the highest allowed Codec\_Mode in the local downlink direction. This indication must be combined with the corresponding CMR in the distant uplink direction to set the Codec Mode to use in that direction. The local downlink CMR is the indication from the distant radio link on the highest allowed Codec\_Mode in the distant downlink direction. This CMR from the TRAU must be combined with the corresponding CMR for the local uplink direction, see 3GPP TS 45.009 and 28.062, before it is sent down to the MS. + +##### 5.5.1.2.2 Coding of Data bits (D-bits) + +In Codec\_Mode 10,2 kBit/s the bits D1...D20 and D234...D253 are reserved for Tandem Free Operation In all Codec\_Modes below 10,2 kBit/s and in all No\_Speech frames the bits D1...D31 (31 bits) and D203...D256 (54 bits) are reserved for Tandem Free Operation (see 3GPP TS 28.062). + +In No\_Speech frames additionally bits D44...D57 (14 bits) are reserved for TFO as well. + +If the BTS does not support TFO or TFO is disabled, then the bits in these fields shall all be set to "1". + +###### Coding of Speech Frames: + +The contents of the Data bits for all eight AMR Codec\_Modes are defined in the following, in cases when the Frame\_Classification is either set to Speech\_Good, Speech\_Degraded, or Speech\_Bad. The speech block is subdivided into four subsets. The order within a given subset is the same as output from the transcoder (see 3GPP TS 26.090). The four times three parity bits (CRC1 to CRC4), added at the end of each subset, are generated using the same cyclic code as defined for the Enhanced Full Rate (see clause 5.5.1.1.2). The TRAU frame formats in uplink and downlink direction are identical. + +###### AMR\_Mode 12,2 kBit/s, see 3GPP TS 26.090: + +| | | +|--------------|-------------------------------------------------------------| +| D1...D38: | Indexes of the LSF submatrices (s1...s38) | +| D39...D91: | Indexes of the parameters of first sub-frame (s39...s91) | +| D92...D94: | CRC1 over bits C1...C25, s1...s29, s39...s50, s87...s89. | +| D95...D144: | Indexes of the parameters of second sub-frame (s92...s141) | +| D145...D147: | CRC2 over bits s92...s100, s137...s139. | +| D148...D200: | Indexes of the parameters of third sub-frame (s142...s194) | +| D201...D203: | CRC3 over bits s142...s153, s190...s192. | +| D204...D253: | Indexes of the parameters of fourth sub-frame (s195...s244) | +| D254...D256: | CRC4 over bits s195...s199, s201...s203, s240...s242. | + +###### AMR\_Mode 10,2 kBit/s, see 3GPP TS 26.090: + +| | | +|--------------|-----------------------------------------------------------------------------| +| D21...D46: | Indexes of the LSF submatrices (s1...s26) | +| D47...D92: | Indexes of the parameters of first sub-frame (s27...s72) | +| D93...D95: | CRC1 over bits C1...C25, D1...D20, s1...s25, s27...s34, s66, s67, s69, s70. | +| D96...D138: | Indexes of the parameters of second sub-frame (s73...s115) | +| D139...D141: | CRC2 over bits s73...s76, s109, s110, s112, s113. | +| D142...D187: | Indexes of the parameters of third sub-frame (s116...s161) | +| D188...D190: | CRC3 over bits s116...s123, s155, s156, s158, s159. | +| D191...D233: | Indexes of the parameters of fourth sub-frame (s162...s204) | +| D254...D256: | CRC4 over bits s162...s165, s198, s199, s201, s202, D234...D253. | + +###### **AMR\_Mode 7,95 kBit/s, see 3GPP TS 26.090:** + +| | | +|--------------|-------------------------------------------------------------| +| D32...D58: | Indexes of the LSF submatrices (s1...s27) | +| D59...D92: | Indexes of the parameters of first sub-frame (s28...s61) | +| D93...D95: | CRC1 over bits C1...C25, s1...s35, s53, s54, s57, s60. | +| D96...D127: | Indexes of the parameters of second sub-frame (s62...s93) | +| D128...D130: | CRC2 over bits s62...s65, s85, s86, s89...s92. | +| D131...D164: | Indexes of the parameters of third sub-frame (s94...s127) | +| D165...D167: | CRC3 over bits s94...s101, s119, s120, s123...s126. | +| D168...D199: | Indexes of the parameters of fourth sub-frame (s128...s159) | +| D200...D202: | CRC4 over bits s128...s131, s151, s152, s155...s158. | + +###### **AMR\_Mode 7,40 kBit/s, see 3GPP TS 26.090:** + +| | | +|--------------|---------------------------------------------------------------------------| +| D32...34 | spare (3 bits); set to "1" | +| D35...D60: | Indexes of the LSF submatrices (s1...s26) | +| D61...D92: | Indexes of the parameters of first sub-frame (s27...s58) | +| D93...D95: | CRC1: bits C1...C25, s1...s20, s22...s24, s27...s32, s52, s53, s55...s57. | +| D96...D124: | Indexes of the parameters of second sub-frame (s59...s87) | +| D125...D127: | CRC2 over bits s59...s61, s81, s82, s84...s86. | +| D128...D159: | Indexes of the parameters of third sub-frame (s88...s119) | +| D160...D162: | CRC3 over bits s88...s93, s113, s114, s116...s118. | +| D163...D191: | Indexes of the parameters of fourth sub-frame (s120...s148) | +| D192...D194: | CRC4 over bits s120...s122, s142, s143, s145, s146. | +| D195...D202: | spare (8 bits); set to "1". | + +###### **AMR\_Mode 6,70 kBit/s, see 3GPP TS 26.090:** + +| | | +|--------------|--------------------------------------------------------------------| +| D32...D37: | spare (6 bits); set to "1" | +| D38...D63: | Indexes of the LSF submatrices (s1...s26) | +| D64...D92: | Indexes of the parameters of first sub-frame (s27...s55) | +| D93...D95: | CRC1 over bits C1...C25, s1...s17, s20, s24, s27...s34, s49...s53. | +| D96...D120: | Indexes of the parameters of second sub-frame (s56...s80) | +| D121...D123: | CRC2 over bits s56...s59, s74...s78. | +| D124...D152: | Indexes of the parameters of third sub-frame (s81...s109) | +| D153...D155: | CRC3 over bits s81...s88, s103...s107. | +| D156...D180: | Indexes of the parameters of fourth sub-frame (s110...s134) | +| D181...D183: | CRC4 over bits s110...s113, s128...s132. | +| D184...D202: | spare (19 bits); set to "1". | + +###### **AMR\_Mode 5,90 kBit/s, see 3GPP TS 26.090:** + +| | | +|--------------|------------------------------------------------------------| +| D32...D41: | spare (10 bits); set to "1" | +| D42...D67: | Indexes of the LSF submatrices (s1...s26) | +| D68...D92: | Indexes of the parameters of first sub-frame (s27...s51) | +| D93...D95: | CRC1 over bits C1...C25, s1...s17, s27...s34, s48...s51. | +| D96...D116: | Indexes of the parameters of second sub-frame (s52...s72) | +| D117...D119: | CRC2 over bits s52...s54, s69...s72. | +| D120...D144: | Indexes of the parameters of third sub-frame (s73...s97) | +| D145...D147: | CRC3 over bits s73...s80, s94...s97. | +| D148...D168: | Indexes of the parameters of fourth sub-frame (s98...s118) | +| D169...D171: | CRC4 over bits s98...s100, s115...s118. | +| D172...D202: | spare (31 bits); set to "1". | + +###### **AMR\_Mode 5,15 kBit/s, see 3GPP TS 26.090:** + +| | | +|--------------|------------------------------------------------------------| +| D32...D46 | spare (15 bits); set to "1" | +| D47...D69: | Indexes of the LSF submatrices (s1...s23) | +| D70...D92: | Indexes of the parameters of first sub-frame (s24...s46) | +| D93...D95: | CRC1 over bits C1...C25, s1...s16, s19...s29, s42...s46. | +| D96...D114: | Indexes of the parameters of second sub-frame (s47...s65) | +| D115...D117: | CRC2 over bits s47...s48, s61...s65. | +| D118...D136: | Indexes of the parameters of third sub-frame (s66...s84) | +| D137...D139: | CRC3 over bits s66...s67, s80...s84. | +| D140...D158: | Indexes of the parameters of fourth sub-frame (s85...s103) | + +D159...D161: CRC4 over bits s85...s86, s99...s103. + D162...D202: spare (41 bits); set to "1". + +###### **AMR\_Mode 4,75 kBit/s, see 3GPP TS 26.090:** + +D32...D44: spare (13 bits); set to "1" + D45...D67: Indexes of the LSF submatrices (s1...s23) + D68...D92: Indexes of the parameters of first sub-frame (s24...s48) + D93...D95: CRC1 over bits C1...C25, s1...s16, s18, s19, s21...s29, s45...s48. + D96...D108: Indexes of the parameters of second sub-frame (s49...s61) + D109...D111: CRC2 over bits s49,s50. + D112...D132: Indexes of the parameters of third sub-frame (s62...s82) + D133...D135: CRC3 over bits s62, s63, s79...s82. + D136...D148: Indexes of the parameters of fourth sub-frame (s83...s95) + D149...D151: CRC4 over bits s83, s84. + D152...D202: spare (51 bits); set to "1". + +###### **Coding of No\_Speech Frames:** + +The following tables define the contents of the Data bits when the Frame\_Classification is set to "No\_Speech". The three parity bits (CRC1) added are generated using the same cyclic code as defined for the Enhanced Full Rate (see clause 5.5.1.1.2). The TRAU Frame Formats in uplink and downlink direction are identical. + +###### **SID\_Update and SID\_Bad Frame:** + +D32...D34: No\_Speech\_Classification + D35...D37: Codec\_Mode\_Indication\_abs + D38...D40: Codec\_Mode\_Request\_abs + D41: PAB: Phase Alignment Bit (optional) + D42...D43: TAE: Time Alignment Extension (optional) + D44...D57: reserved for TFO + D58...D60: Moving average predictor, initial values (s1...s3) + D61...D86: Indexes of LSF submatrices (s4...s29) + D87...D92: Logarithmic frame energy (s30...s35) + D93...D95: CRC1 over bits C1...C25, D32...D92. + D96...D207: spare (112 bits); set to "1". + +###### **No\_Data, SID\_First and Onset Frame:** + +Bits D32...D34: No\_Speech\_Classification + Bits D35...D37: Codec\_Mode\_Indication\_abs + Bits D38...D40: Codec\_Mode\_Request\_abs + Bit D41: PAB: Phase Alignment Bit (optional) + Bits D42...D43: TAE: Time Alignment Extension (optional) + Bits D44...D57: reserved for TFO + Bits D58...D92: spare (35 bits); set to "1" + Bits D93...D95: CRC1 over bits C1...C25, D32...D92. + Bits D96...D207: spare (112 bits); set to "1". + +###### **No\_Speech\_Classification:** + +If the Frame\_Classification is set to "0.0", then the TRAU frame contains no speech parameters. The No\_Speech\_Classification is coded in the D-Bits: + +D32...D34: + 1.1.1: Sid\_First + 1.1.0: Onset + 1.0.1: Sid\_Update + 1.0.0: Sid\_Bad (SID\_Update with bad parameters) + 0.1.1: spare + 0.1.0: spare + 0.0.1: spare + 0.0.0: No\_Data (nothing received or frame has been stolen, e.g. by FACCH or RATSCCH). + +###### **Codec\_Mode\_Indication\_abs (CMI\_abs):** + +The meaning in uplink and downlink is identical. In No\_Speech frames the CMI is always transmitted, independent of the setting of the RIF bit. Coding: + +D35 . D36 . D37: + 0.0.0 Codec\_Mode 4,75 kBit/s + +| | | +|-------|------------------------| +| 0.0.1 | Codec_Mode 5,15 kBit/s | +| 0.1.0 | Codec_Mode 5,90 kBit/s | +| 0.1.1 | Codec_Mode 6,70 kBit/s | +| 1.0.0 | Codec_Mode 7,40 kBit/s | +| 1.0.1 | Codec_Mode 7,95 kBit/s | +| 1.1.0 | Codec_Mode 10,2 kBit/s | +| 1.1.1 | Codec_Mode 12,2 kBit/s | + +###### **Codec\_Mode\_Request\_abs (CMR\_abs):** + +The meaning in uplink and downlink is identical. In No\_Speech frames the CMR is always transmitted, independent of the setting of the RIF bit. Coding: + +D38 . D39 . D40: + +| | | +|-------|------------------------| +| 0.0.0 | Codec_Mode 4,75 kBit/s | +| 0.0.1 | Codec_Mode 5,15 kBit/s | +| 0.1.0 | Codec_Mode 5,90 kBit/s | +| 0.1.1 | Codec_Mode 6,70 kBit/s | +| 1.0.0 | Codec_Mode 7,40 kBit/s | +| 1.0.1 | Codec_Mode 7,95 kBit/s | +| 1.1.0 | Codec_Mode 10,2 kBit/s | +| 1.1.1 | Codec_Mode 12,2 kBit/s | + +###### **Phase Alignment Bit (PAB):** + +This bit is defined only in No\_Speech frames. It is optional and shall be set to "0", if not used. + +The PAB has exactly the same meaning and function as the Phase Alignment Command (PAC). For the exact procedure see clause 6.6.1.2.1. + +PAB set to 0: CMI/CMR phase in downlink TRAU frames shall not be changed + +PAB set to 1: CMI/CMR phase in downlink TRAU frames shall be inverted. + +PAB shall only be used together with TAC values between **0.0.0.0.0.0** ("No change in frame timing") and **1.0.0.1.1.1** ("Delay frame 39 x 500µs"). + +###### **Time Alignment Extension (TAE):** + +The TAE specifies optionally a Time Alignment Extension. Coding: + +D42 . D43: + +Meaning: + +| | | +|------|----------------------------------------------------------------| +| 0.0: | No additional delay with respect to the Time Alignment Command | +| 0.1 | Additional delay of 125 µs | +| 1.0 | Additional delay of 250 µs | +| 1.1 | Additional delay of 375 µs | + +TAE together with the Time Alignment Command (TAC) allow a "one step" time alignment of 125 µs accuracy in No\_Speech frames. TAE shall only be used together with TAC values between **0.0.0.0.0.0** ("No change in frame timing") and **1.0.0.1.1.1** ("Delay frame 39 x 500µs"). + +The TAC\_TAE combination **0.0.0.0.0.0\_0.1** shall be interpreted as "Delay frame by 125µs". + +The TAC\_TAE combination **1.0.0.1.1.1\_1.0** shall be interpreted as "Advance frame by 250µs". + +The TAC\_TAE combination **1.0.0.1.1.1\_1.1** shall be interpreted as "Advance frame by 125µs". + +##### **5.5.1.2.3 Time Alignment Bits (T1...T4)** + +The coding and meaning is as described in 3.5.1.1.3 (Time Alignment Bits). + +#### 5.5.1.3 Coding of Frames for Adaptive Multi-Rate Wide Band Speech (AMR-WB) for 16kbit/s and 32kbit/s sub-multiplexing + +##### 5.5.1.3.1 Coding of Control bits (C-bits) + +| Control Bits | Description
Uplink
For the 16k main part | Description
Downlink
For the 16k main part | Description
Uplink and Downlink
for the 16k upper extension | +|-----------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| C1...C5 | Frame_Type (Codec_Type) | Frame_Type (Codec_Type) | Frame_Type (Codec_Type) | +| C6...C11 | Time Alignment Command (TAC) or Phase Alignment Control (PAC) or TFO Information or Handover Information | Time Alignment Command (TAC) or Phase Alignment Control (PAC) or TFO Information or Handover Information | Time Alignment Command (TAC) or Phase Alignment Control (PAC) or TFO Information or Handover Information | +| C12 | Request or Indication Flag (RIF) | Request or Indication Flag (RIF) | spare, set to 1 | +| C13 | spare, set to 1 | Uplink Frame Error (UFE) | spare, set to 1 | +| C14 . C15 . C16 | Config_Prot | Config_Prot | spare, set to 1.1.1 | +| C17 . C18 | Message_No | Message_No | spare, set to 1.1 | +| C19 | DTX in downlink requested (DTXd) | spare, reserved for TFO (see 28.062) | spare, set to 1 | +| C20 | TFO Enabled (TFOE) | spare, reserved for TFO (see 28.062) | spare, set to 1 | +| C21 . C22 | Frame_Classification, Rx_Type | Frame_Classification, Tx_Type | spare, set to 1.1 | +| C23 . C24 . C25 | Codec_Mode_Indication (RIF == 0) or Codec_Mode_Request (RIF == 1) or 0.0.0 (Frame_Classification == 0.0) | Codec_Mode_Indication (RIF == 0) or Codec_Mode_Request (RIF == 1) or 0.0.0 (Frame_Classification == 0.0) | spare, set to 1.1.1 | + +Detailed Description: + +###### **Frame Type:** + +The coding of the Frame\_Type (also called "Codec\_Type") for AMR-WB is identical in uplink and downlink. + +C1...C5: + +**0.1.0.1.0: Adaptive Multi-Rate Wide Band** Codec, in lower 16k main part + +**0.1.0.1.1: Adaptive Multi-Rate Wide Band** Codec, in upper 16k extension part. + +###### **Time Alignment Field:** + +As in case of AMR-NB. + +###### Phase Alignment Command (PAC): + +As in case of AMR-NB. + +###### TFO Information: + +As in case of AMR-NB. + +###### **Request or Indication Flag (RIF):** + +As in case of AMR-NB. + +###### **Uplink Frame Error (UFE):** + +As in case of AMR-NB. + +###### **Config\_Prot:** + +This field is reserved and shall be set to "0.0.0". + +###### **Message\_No:** + +This field is reserved and shall be set to "0.0". + +###### **DTX in downlink requested (DTXd):** + +As in case of AMR-NB. + +###### **TFO Enabled (TFOE):** + +As in case of AMR-NB. + +###### **Frame\_Classification:** + +As in case of AMR-NB. + +###### **Codec\_Mode\_Indication / Codec\_Mode\_Request:** + +As in case of AMR-NB, except that the coding is adapted to the AMR-WB modes. + +The coding is identical in uplink and downlink. + +C23.C24.C25: Coding for AMR-WB + +| | | +|-------|-------------------------| +| 0 0 0 | Codec_Mode 6,60 kBit/s | +| 0 0 1 | Codec_Mode 8,85 kBit/s | +| 0 1 0 | Codec_Mode 12,65 kBit/s | +| 0 1 1 | Codec_Mode 15,85 kBit/s | +| 1 0 0 | Codec_Mode 23,85 kBit/s | +| 1 0 1 | undefined | +| 1 1 0 | undefined | +| 1 1 1 | undefined. | + +The CMI indicates the Codec\_Mode to be used for decoding the associated speech parameters in the same and the next frame. The CMR indicates the highest allowed Codec\_Mode to be used for encoding in the opposite direction. + +Note 1: In the TRAU frames, the Codec\_Mode\_Request, respectively the Codec\_Mode\_Indication are coded absolutely (three bits for five possible modes). On the radio interface, because of bandwidth limitation, these parameters are coded with two bits only. The CCU shall perform the required translation. + +Note 2: In case of no Tandem Free Operation the uplink CMR is a Codec\_Mode\_Command (CMC) from the BTS to the TRAU and the TRAU shall try to follow the command as soon as possible. The only allowed exception is in case of DTX when SID or No\_Data frames can be used during speech pauses. In the downlink direction the CMR is typically set by the TRAU to "1.1.1". This CMR from the TRAU must be combined with the corresponding CMR for the local uplink direction, see 3GPP TS 45.009 and 28.062, before it is sent down to the MS. + +Note 3: In case of an ongoing Tandem Free Operation, the local uplink CMR is an indication from the local BTS to the TRAU, respectively to the distant BTS, on the highest allowed Codec\_Mode in the local downlink direction. This indication must be combined with the corresponding CMR in the distant uplink direction to set the Codec Mode to use in that direction. The local downlink CMR is the indication from the distant radio link on the highest allowed Codec\_Mode in the distant downlink direction. This CMR from the TRAU must be combined with the corresponding CMR for the local uplink direction, see 3GPP TS 45.009 and 28.062, before it is sent down to the MS. + +##### 5.5.1.3.2 Coding of Data bits (D-bits) + +###### **Coding of Speech Frames for AMR-WB:** + +The contents of the Data bits for all five AMR-WB Codec\_Modes are defined in the following, in cases when the Frame\_Classification is either set to Speech\_Good, Speech\_Degraded, or Speech\_Bad. The three parity bits are generated using the same cyclic code as defined for the Enhanced Full Rate (see subclause 5.5.1.1.2). The TRAU frame formats in uplink and downlink directions are identical. + +All undefined bits are spare and set to 1. + +###### **AMR-WB Mode 23.85kbit/s (477 bits per frame):** + +For this codec mode the lower main 16k part is not sufficient to carry all data bit. The remaining bits are therefore transported in the upper 16k extension part. + +###### **16 k lower main part:** + +| | | +|--------------|--------------------------------------------------| +| D15...D92: | s1, s2 ... s78 [first block and first sub-frame] | +| D93...D95: | CRC over bits C1 ... C25, D15 ... D92 | +| D96...D148: | s157, s158 ... s209 [second sub-frames] | +| D149...D203: | s263, s264 ... s317 [third sub-frame] | +| D204...D256: | s372, s373 ... s424 [fourth sub-frame] | + +###### **16k upper extension part:** + +| | | +|--------------|-----------------------------------------------------| +| D15...D92: | s79, s80 ... s156 [first block and first sub-frame] | +| D93...D95: | CRC over bits D15 ... D92 | +| D96...D148: | s210, s211 ... s262 [second sub-frames] | +| D150...D203: | s318, s319 ... s371 [third sub-frame] | +| D204...D256: | s425, s426 ... s477 [fourth sub-frame] | + +###### **AMR-WB Mode 15,85 kbit/s (317 bits per frame):** + +For this codec mode the lower main 16k part is not sufficient to carry all data bit. The remaining bits are therefore transported in the upper 16k extension part. The arrangement is such that the delay as well as the load in the upper extension part are minimised. Therefore only D-bits in columns 3, 5, 7 of the TRAUF Frame structure in the upper extension part are used. One 3-bit CRC is included in each part (lower main or upper extension) after the first sub-frame. + +###### **16 k lower main part:** + +| | | +|--------------|-------------------------------------------------------| +| D1...D92: | s1, s2, s3, ... s92 [first block and first sub-frame] | +| D93...D95: | CRC over bits C1 ... C25, s1 ... s92 | +| D96...D148: | s117, s118...s169 [second sub-frame] | +| D149...D203: | s183, s184...s237 [third sub-frame] | +| D204...D256: | s252, s253...s304 [fourth sub-frame] | + +###### **16k upper extension part:** + +| | | +|----------------------|----------------------------------------------------------| +| D32, D34...D86, D88: | s93, s94... s115, s116 [first block and first sub-frame] | +| D90,D92,D94: | CRC over bits s93...s116 | +| D116, D120...D146: | s170...s182 [second sub-frame] | +| D169, D172...D202: | s238...s251 [third sub-frame] | +| D225, D227...D255: | s305...s317 [fourth sub-frame] | + +###### **AMR-WB Mode 12,65 kbit/s (253 bits per frame):** + +The 253 bits of this mode fit well into the 256 D-bits of the lower main 16k part. One 3-bit CRC protects the first sub-frame. + +The D-bits of 16k upper extension part (if present) are unused. + +| | | +|----------------|---------------------------------------------------------| +| D1...D47: | VAD-flag and indices of the LSF submatrices (s1... s47) | +| D48...D100: | First sub-frame (s48... s100) | +| D101..D103: | CRC over bits C1 ... C25, s1 ... s100 | +| D104 ... D256: | remaining sub-frames (s101 ... s253) | + +###### **AMR-WB Mode 8.85 kbit/s (177 bits per frame):** + +The 177 bits of this mode fit well into the 256 D-bits of the lower main 16k part. One 3-bit CRC protects the first sub-frame. The D-bits of 16k upper extension part (if present) are unused. + +| | | +|-------------|---------------------------------------------------------| +| D12...D58: | VAD-flag and indices of the LSF submatrices (s1... s47) | +| D59...D92: | First sub-frame (s48... s81) | +| D93...D95: | CRC over bits C1 ... C25, s1 ... s81 | +| D96...D191: | remaining sub-frames (s82 ... s177) | + +###### **AMR-WB Mode 6.60 kbit/s (132 bits per frame):** + +The 132 bits of this mode fit well into the 256 D-bits of the lower main 16k part. One 3-bit CRC protects the first sub-frame. The D-bits of 16k upper extension part (if present) are unused. + +| | | +|-------------|---------------------------------------------------------| +| D30...D66: | VAD-flag and indices of the LSF submatrices (s1... s37) | +| D67...D92: | First sub-frame (s38... s63) | +| D93...D95: | CRC over bits C1 ... C25, s1 ... s63 | +| D96...D164: | remaining sub-frames (s64 ... s132) | + +###### **Coding of No\_Speech Frames:** + +The following tables define the contents of the Data bits when the Frame\_Classification is set to "No\_Speech". The three parity bits added are generated using the same cyclic code as defined for the Enhanced Full Rate (see subclause 5.5.1.1.2). The TRAUs Frame Formats in uplink and downlink direction are identical. All unused D-bits are set to spare ("1"). + +###### **SID\_Update and SID\_Bad Frame for AMR-WB:** + +| | | +|-------------|------------------------------------------| +| D1...D31 | spare, set to 1 | +| D32...D34: | No_Speech_Classification | +| D35...D37: | Codec_Mode_Indication_abs | +| D38...D40: | Codec_Mode_Request_abs | +| D41: | PAB: Phase Alignment Bit (optional) | +| D42...D43: | TAE: Time Alignment Extension (optional) | +| D44...D57: | spare, set to "1" | +| D58...D85: | Indexes of LSF submatrices (s1...s28) | +| D86...D91: | Logarithmic frame energy (s29...s34) | +| D92...D92: | CN_Dithering flag (s35) | +| D93...D95: | CRC1 over bits C1...C25, D32...D92. | +| D96...D256: | spare, set to "1". | + +###### **No\_Data, SID\_First and Onset Frame for AMR-WB:** + +| | | +|-------------|------------------------------------------| +| D1...D31 | spare, set to 1 | +| D32...D34: | No_Speech_Classification | +| D35...D37: | Codec_Mode_Indication_abs | +| D38...D40: | Codec_Mode_Request_abs | +| D41: | PAB: Phase Alignment Bit (optional) | +| D42...D43: | TAE: Time Alignment Extension (optional) | +| D44...D57: | spare, set to "1" | +| D58...D92: | spare (35 bits); set to "1" | +| D93...D95: | CRC1 over bits C1...C25, D32...D92. | +| D96...D256: | spare, set to "1". | + +###### **No\_Speech\_Classification:** + +As in case of AMR-NB. + +###### **Codec\_Mode\_Indication\_abs (CMI\_abs):** + +The meaning in uplink and downlink is identical. In No\_Speech frames the CMI is always transmitted, independent of the setting of the RIF bit. Coding: + +D35 . D36 . D37: + +| | | +|-------|-------------------------| +| 0.0.0 | Codec_Mode 6,60 kBit/s | +| 0.0.1 | Codec_Mode 8,85 kBit/s | +| 0.1.0 | Codec_Mode 12,65 kBit/s | +| 0.1.1 | Codec_Mode 15,85 kBit/s | +| 1.0.0 | Codec_Mode 23,85 kBit/s | +| 1.0.1 | undefined | +| 1.1.0 | undefined | +| 1.1.1 | undefined | + +###### **Codec Mode Request abs (CMR abs):** + +The meaning in uplink and downlink is identical. In No\_Speech frames the CMR is always transmitted, independent of the setting of the RIF bit. Coding: + +D38 . D39 . D40: + +0.0.0 Codec\_Mode 6,60 kBit/s + 0.0.1 Codec\_Mode 8,85 kBit/s + 0.1.0 Codec\_Mode 12,65 kBit/s + 0.1.1 Codec\_Mode 15,85 kBit/s + 1.0.0 Codec\_Mode 23,85 kBit/s + 1.0.1 undefined + 1.1.0 undefined + 1.1.1 undefined + +##### 5.5.1.3.3 Time Alignment Bits (T1a...T4a) + +Bits T1a...T4a Bits positioned at the end of the downlink and uplink frames. If the timing of the frame is to be advanced, these 2..4 bits are not transferred in order to reduce the frame length accordingly. When transferred, the bits are set to binary "1". + +#### 5.5.1.4 void + +#### 5.5.1.5 Coding of Configuration Frames + +##### Control bits (C-bits): + +| Description | Uplink | Downlink | +|----------------------------|-----------------------------------------|-----------------------------------------| +| Frame type
Bits C1 - C5 | C1C2C3C4 C5
1 1 1 1 0: Configuration | C1C2C3C4 C5
1 1 1 1 0: Configuration | + +##### Data Bits (D-bits): + +Bits D1 ... D276: + +These data bits are reserved for Configuration Exchange to support Tandem Free Operation. They are defined in TS 28.062. + +##### Time Alignment Bits (T1...T4) + +Bits T1 .. T4: + +Bits positioned at the end of the frames. If the timing of the frame is to be advanced 250 µs, these 4 bits are not transferred in order to reduce the frame length accordingly. When transferred the bits are set to binary "1". + +### 5.5.2 Coding of O&M Frames + +#### Control bits (C-bits): + +| Description | Uplink | Downlink | +|----------------------------|--------------------------------|--------------------------------| +| Frame type
Bits C1 - C5 | C1C2C3C4 C5
0 0 1 0 1 : O&M | C1C2C3C4 C5
1 1 0 1 1 : O&M | +| Bits C6 - C15 | Spare | Spare | + +Data Bits (D-bits): + +Bits D1 .. D264: Bits used for transfer of O&M information. The coding and use of these bits are left to the manufacturer of the BSC/TRAU. + +Spare Bits: + +Bits S1 .. S6: Spare + +### 5.5.3 Coding of Data Frames + +Control bits (C-bits): + +| Description | Uplink | Downlink | +|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| Frame type.
Bits C1 - C5 | C1C2C3C4 C5
0 1 0 0 0 : Data
except 14.5

1 0 1 0 0 : Data 14.5 1) | C1C2C3C4 C5
1 0 1 1 0 : Data
except 14.5

1 0 1 0 0 : Data 14.5 1) | +| Intermediate RA bit
rate.
Bit C6
for data services
except 14.5
Spare
for Data 14.5 | 0: 8 kbit/s
1: 16 kbit/s


Spare | 0: 8 kbit/s
1: 16 kbit/s


Spare | +| Bits C7 - C15 | Spare | Spare | + +NOTE 1: The Data frame is in case of data 14.5 kbit/s used only for synchronization purposes. The data bits are in this case set according to clause 6.5.1. + +### 5.5.4 Coding of Extended Data Frames + +Control bits (C-bits): + +| Description | Uplink | Downlink | +|-------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------| +| Frame type.
Bits C1 - C5 | C1C2C3C4 C5
1 1 1 1 1 :
Extended Data
frame 14.5 kbit/s | C1C2C3C4 C5
1 1 1 1 1 :
Extended data
Frame 14.5 | +| Bit C6
Idle/Data/UFE | Idle/data
Frame indication | UFE | +| Bits C7 - C13 | Spare | Bit C7 indicating idle/data frame. Bit
C8-C13 spare | +| Multi Frame Structure
defined in 3GPP TS 44.021
Bits M1, M2 | M1, M2 | M1, M2 | + +### 5.5.5 Coding of Idle Speech Frames + +Control bits (C-bits): + +| Description | Uplink | Downlink | +|-----------------------------|----------------------------------------|----------------------------------------| +| Frame type.
Bits C1 - C5 | C1C2C3C4 C5
1 0 0 0 0 : Idle Speech | C1C2C3C4 C5
0 1 1 1 0 : Idle Speech | +| Bits C6 - C21 | Coding as for
Speech frames. | Coding as for
Speech frames. | + +NOTE: Idle Speech frames shall not be used in AMR or AMR-WB; instead Frame\_Classification set to "No\_Data" shall be applied. + +Time Alignment Bits: + +Bits T1 .. T4: Coding as for Speech frames. + +## 5.6 Order of Bit Transmission + +The order of bit transmission is: + +The first octet is transferred first with the bit no. 1 first, bit no. 2 next etc. + +# 6 Procedures + +In this clause, when nothing is particularly stated, procedures for AMR\_WB apply to 16 kbit/s and 32 kbit/s multiplexing, and in the second case, to channel a and channel b. + +## 6.1 Remote Control of Transcoders and Rate Adaptors + +When the transcoder is positioned remote to the BTS, the Channel Codec Unit (CCU) in the BTS has to control some of the functions in the remote Transcoder/Rate Adaptor Unit (TRAU) in the BSC. + +This remote control is performed by inband signalling carried by the control bits (C-bits) in each TRAU frame. + +The following functions in the TRAU are remotely controlled by the CCU: + +- Shift between speech and data. +- Control of the rate adaption functions for data calls. +- Downlink frame timing for speech frames. +- Transfer of DTX information. + +In addition, the following functions are provided in case of AMR or AMR-WB speech: + +- Control of Codec Mode adaptation +- Transfer of TFO Configuration Parameters (optional, see 3GPP TS 28.062) +- Downlink Phase Alignment (optional) +- Transfer of Information on TFO Status (optional, see 3GPP TS 28.062) +- Transfer of Information on Pre-Handover Warning (optional) + +In addition, the inband signalling also provides means for transfer of O&M signals between the TRAU and the BSC/BTS. + +## 6.2 Resource Allocation + +At reception of the ASSIGNMENT REQUEST message, e.g. at call setup, when a circuit switched connection is required, the BSC provides an appropriate TRAU to the circuit to be used between the BSC and the BTS and sends the CHANNEL ACTIVATION message to the BTS. + +When receiving the CHANNEL ACTIVATION message, the BTS allocates the appropriate radio resources and a Channel Codec Unit (CCU) to be used. + +In case of FR and EFR Speech or Data (except 14.5 kbit/s): + +The CCU now starts sending uplink frames with the appropriate "Frame Type" and, for data calls, the intermediate rate adaption bit rate set. + +When receiving the first frame, the TRAU sets the mode of operation accordingly and starts sending downlink frames with the "Frame Type" and, for data calls, the intermediate rate adaption bit rate set as an acknowledgement indication. + +In case of Adaptive Multi-Rate or Adaptive Multi\_rate Wideband speech: see clause 6.6.1.3. + +In case of Data 14.5 kbit/s: + +The CCU starts sending uplink Data TRAU Frames with the appropriate "Frame Type" set to establish initial synchronization. + +When receiving the first frame, the TRAU sets the mode of operation accordingly and as an acknowledgement starts sending downlink Data TRAU Frames with the same "Frame Type". + +The CCU starts sending uplink Extended Data TRAU Frames with the appropriate "Frame Type" set upon reception of that acknowledge indication. + +When receiving the first frame, when the "Frame Type" is set to Extended Data TRAU frame, the TRAU sets the mode of operation accordingly and as an acknowledgement starts sending downlink Extended Data TRAU frames with the same "Frame Type". + +## 6.3 Resource Release + +At release of circuit switched resources, e.g. at call release, the connection between the CCU and the TRAU will be released by the BSC. The BSC has to indicate that the connection has been released. How this is performed is a BSC internal matter. However, three methods have been identified. + +- i) The BSC indicates the call release to the TRAU by inserting the PCM idle bit pattern described in 3GPP TS 48.054 on the circuits towards the TRAU. The TRAU shall be able to detect this idle bit pattern. When received at the TRAU, the TRAU will lose frame synchronization and will start timer Tsync (see clause 6.8.2). If, when Tsync expires, the idle bit pattern has been detected, the TRAU shall terminate the operation (go idle) until a valid frame is again received. +- ii) This second alternative does not apply to Enhanced Full Rate Speech, Adaptive Multi-Rate speech, Adaptive Multi-Rate Wideband speech and Data 14.5 kbit/s cases. + +After a call release, the TRAU downlink channel is switched to the TRAU uplink channel (16 kbit/s side). + +The TRAU shall be able to detect the looped downlink frame. When it is detected, the TRAU shall terminate the normal operation (go idle) until a valid uplink TRAU frame is again received. + +- iii) It is handled by BSC internal signals (e.g. if the BSC and TRAU are collocated). + +## 6.4 In Call Modification + +If the subscriber orders "In Call Modification", the CCU sets the "Frame Type" and, for data calls, the intermediate rate adaption bit rate in the uplink frames to the new mode of operation. When receiving this information, the TRAU changes the mode of operation accordingly and sets the new "Frame Type" and, for data calls, the intermediate rate adaption bit rate in the downlink frames. The same procedure applies for mode change between Data 14,5 kbit/s. + +In case of mode change to data 14,5 kbit/s from Speech or Data (other than 14.5 kbit/s) the same procedure as for "Resource Allocation" is performed. + +In case of mode change from any other speech or data service to **AMR or AMR-WB speech**, the same procedure as for "Resource Allocation" shall be performed. In case of mode change within AMR speech, i.e. a change of the AMR or AMR-WB Configuration, the BSC should take care that a smooth transition from the old AMR or AMR-WB configuration into the new one is performed, see 3GPP TS 45.009 and 3GPP TS 28.062. + +## 6.5 Transfer of Idle Frames, Handling of Missing Data + +Between the TRAU and the CCU a TRAU frame shall be transferred every 20 ms. + +### 6.5.1 In Full Rate data case + +If no data is received from the MS (uplink direction) or no data is received from the MSC side of the interface (downlink direction), idle data frames shall be transferred instead of data frames. Idle data frames are data frames with all data bit positions set to binary "1". In addition, for data 14,5 kbit/s; the C6 bit shall be set to '1' in the uplink extended data frame. For each idle frame sent downlink for data 14.5 kbit/s the C7 bit is set to '1'. + +### 6.5.2 In Full Rate speech case + +If no speech is received from the MS (uplink direction), the CCU shall send TRAU speech frames with BFI flag set to 1 (bad frame) or idle speech frames. If no speech is received from the MSC side of the interface (downlink direction), idle speech frames shall be transferred instead of speech frames. + +### 6.5.3 In Enhanced Full Rate speech case + +If no speech is received from the MS (uplink direction), the CCU shall send TRAU speech frames with BFI flag set to 1 (bad frame). If no speech is received from the MSC side of the interface (downlink direction), idle speech frames shall be transferred instead of speech frames. + +### 6.5.4 In Adaptive Multi-Rate speech case + +If no speech is received from the MS (uplink direction), or a speech frame is stolen on the radio interface (e.g. by FACCH) the CCU shall send TRAU No\_Speech frames with Frame\_Type set to "AMR" and with No\_Speech\_Classification set to "No\_Data". The Code\_Mode\_Indication shall be set to the previously used value. CMI and CMR shall be set to the Initial\_Codec\_Mode, if at resource allocation. + +If no speech is received from the MSC side (downlink direction), i.e. the "PCM\_Idle" pattern is received instead, the TRAU shall send TRAU No\_Speech frames with Frame\_Type set to "AMR", and with No\_Speech\_Classification set to "No\_Data". The Codec\_Mode\_Indication shall be set to the previously used value or to the Initial\_Codec\_Mode, if at resource allocation. + +### 6.5.5 In Adaptive Multi-Rate Wideband speech case + +If no speech is received from the MS (uplink direction), or a speech frame is stolen on the radio interface (e.g. by FACCH) the CCU shall send TRAU No\_Speech frames with Frame\_Type set to "AMR-WB" and with No\_Speech\_Classification set to "No\_Data". The Code\_Mode\_Indication shall be set to the previously used value. CMI and CMR shall be set to the Initial\_Codec\_Mode, if at resource allocation. + +If no speech is received from the MSC side (downlink direction), i.e. the "PCM\_Idle" pattern is received instead, the TRAU shall send TRAU No\_Speech frames with Frame\_Type set to "AMR-WB", and with No\_Speech\_Classification set to "No\_Data". The Codec\_Mode\_Indication shall be set to the previously used value or to the Initial\_Codec\_Mode, if at resource allocation. + +## 6.6 Procedures for Speech Services + +### 6.6.1 Time Alignment of Speech Service Frames + +The time alignment needed for obtaining minimum buffer delay will differ from call to call. The reasons for this are: + +- The BSC will have no information about the radio timing at the BTS, and will start sending frames at an arbitrary or default time. Each TRAU frame is 320 bits (20 ms) long and will in the worst case be received at the BTS 318 bits out of phase. +- The different timeslots on one carrier are sent at different times (max 4.04 ms which equals 7 timeslots in a TDMA radio frame). +- Different channels may be transferred on different transmission systems using different routes in the network. The transmission delay may therefore differ. + +The required time alignment between radio frames and TRAU frames is considered to be an internal BTS matter for uplink frames. However, the buffer delay for these frames should be kept to a minimum. + +For downlink frames, the procedures in the following clauses should apply. In order to describe the time alignment procedure in the TRAU, two time alignment states are described (Initial Time Alignment state and Static Time Alignment state). + +In order to achieve optimum timing between the radio TDMA frames and the frames on the Abis transmission side, the speech coding and decoding functions in the transcoder should not be synchronized. + +#### 6.6.1.1 Initial Time Alignment State + +The TRAU shall enter the Initial Time Alignment state at the switching-on of the system, when it goes idle (e.g. when receiving the PCM idle pattern after a call release as described in clause 6.3), if loss of frame synchronization is detected, in call modification from data to speech is performed or if BSS internal handover is detected. + +In the Initial Time Alignment state, the frames shall only be delayed (or no change)(see note). The transcoder is able to adjust the time for transmitting the speech frames in steps of 125 µs (one speech sample). The CCU calculates the required timing adjustment and returns a frame including the number of 250/500 µs steps by which the frames in the downlink direction have to be delayed (binary number in the "Time Alignment" field). + +When receiving this information, the TRAU processes this data and sets the "Time Alignment" field in the next downlink frame as ordered and then delays the subsequent frame accordingly. + +NOTE: If the TRAU, in this state, receives an order to advance the next frame 250 µs, this order shall be interpreted as "Delay frame 39\*500 µs". + +When a frame is delayed due to timing adjustments, the TRAU shall fill in the gap between the frames with the appropriate number of binary "1" (T-bits). + +After having adjusted the timing, the TRAU shall receive at least three new frames before a new adjustment is made. This in order to avoid oscillation in the regulation. + +The TRAU shall change from the Initial Time Alignment state to the Static Time Alignment state when it has performed two subsequent timing adjustments which are less than 500 µs (including no change). + +The procedure is illustrated in figure 6.1. + +Optionally, in case of AMR or AMR-WB speech, two additional bits (TAE) may be used in an uplink No\_Speech frame to code a time alignment command with a precision of 125 µs. When receiving this information, the TRAU processes this data and sets the "Time Alignment" field in the next downlink frame as ordered and then delays the subsequent frame accordingly. It needs to send the TAE bits back only if the downlink frame is a No\_Speech frame, too. + +#### 6.6.1.2 The Static Time Alignment State + +In the Static Time Alignment state, the TRAU performs timing adjustments in single steps of 250 µs or 125 µs (AMR or AMR-WB only). The timing may either be delayed (time alignment code "Delay frame by 250 µs (125 µs)"), advanced (time alignment code "Advance frame by 250 µs (125 µs)") or not changed (time alignment code "No Change in Time Alignment" or all other codes that result in no change). + +When receiving an order for adjusting the timing, the transcoder skips or repeats two (one) speech samples in order to achieve the correct timing. + +If the timing is to be advanced 250 µs (125 µs), the TRAU sets the "Time Alignment" field in the next downlink frame as ordered and then the 4 (2) last bits of the frame are not transferred (the T-bits). + +If the timing is to be delayed, the TRAU sets the "Time Alignment" field in the next downlink frame as ordered and then delays the subsequent frame by adding the appropriate number of binary "1" between the frames. + +After having adjusted the timing, the TRAU shall receive at least three new frames before a new adjustment is made. + +If, in this state and TFO is not ongoing (see 3GPP TS 28.062), the TRAU detects a change in the timing of the uplink frames bigger than $n \times 250 \mu\text{s}$ , where $n = 4$ , it shall enter the Initial Time Alignment state and in that state it may perform an adjustment on the downlink equal to the change detected on the uplink. + +In case of AMR or AMR-WB speech the time alignment may be done in steps of $125 \mu\text{s}$ by using the TAC and TAE. If TFO is ongoing in case of AMR or AMR-WB speech the TRAU shall not perform any time alignment in downlink direction. + +##### 6.6.1.2.1 Phase Alignment of Codec\_Mode\_Indication for AMR or AMR-WB + +In the Static Time Alignment state for Adaptive Multi-Rate speech and Adaptive Multi-Rate Wideband, it might be necessary to align the phase of the Codec\_Mode\_Indication and Codec\_Mode\_Request as indicated in downlink TRAU frames by the RIF bit, to the phase of CMI / CMR on the radio interface. One of the following four alternative methods shall be applied: + +**Alternative 1:** If TFO is not ongoing (see 3GPP TS 28.062), then the CCU may send one "Phase Alignment Command" (PAC) uplink (see 3.5.1.2.1). The TRAU shall send two consecutive TRAU frames with Codec\_Mode\_Indication (RIF set to "0" two times) and by this shall invert the phase of Codec\_Mode\_Indication and Codec\_Mode\_Request in downlink on the Abis/Ater interface (consider the round trip delay). + +**Alternative 2:** Similar to Alternative 1: If TFO is not ongoing (see 3GPP TS 28.062), then the CCU may send one No\_Speech frame with the Phase Alignment Bit (PAB) set accordingly. This may be done already within the initial time alignment state together with the initial time alignment command (TAC and TAE). By this the DL TRAU frames can be aligned in time and phase within one step to a precision of $125 \mu\text{s}$ . + +**Alternative 3:** If TFO is ongoing (see 3GPP TS 28.062) no time and phase alignment shall be performed on the Abis/Ater interface. Instead, the CCU shall buffer (up to 40ms) the downlink speech frames, until they can be sent on the radio interface. If the TRAU receives a time or phase alignment command while in TFO it may ignore it. + +**Alternative 4:** The CCU may send a specific RATSCH Message downlink to the mobile station (see 3GPP TS 45.009) and by that invert the phase of the CMI / CMR on the radio interface and thus avoid the buffer delay (20ms). This alternative is especially useful in TFO, but may be used also without TFO. + +![Sequence diagram showing the interaction between MSC, BSC, and BTS for channel allocation and time alignment. The diagram illustrates the exchange of ASSREQ, CHAN ACTIV, and Idle or speech frames, with time alignment calculations performed by the BTS.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The sequence diagram illustrates the interaction between the MSC, BSC, and BTS for channel allocation and time alignment. + +**Initial Setup:** + +- The MSC sends an **ASSREQ** (L3 on the A-interface) to the BSC. +- The BSC sends a **CHAN ACTIV** (L3 on the Abis interface) to the BTS. +- Inside the BSC, a box labeled **Allocate and connect TRAU** is shown. +- Inside the BTS, a box labeled **Allocate Radio channel and CCU** is shown. + +**Time Alignment Process:** + +- The **TRANSCODER/RA UNIT** (connected to the BSC) and the **CHANNEL CODEC UNIT** (connected to the BTS) exchange frames. +- The first frame is labeled **Speech or idle frame (0 TA)**. +- Subsequent frames are labeled **Idle or speech frame**. +- The BTS performs time alignment calculations: + - Calculate Time Alignment (X x 250 uS)** for the first set of frames. + - Calculate Time Alignment (Y x 250 uS)** for the second set of frames. +- Timing intervals of **20 ms** are indicated between frame exchanges. +- An **Arbitrary or default time** is indicated at the start of the frame exchange. +- Output values from the BTS calculations are shown as **20mS X x 250/500 uS** and **20mS Y x 250/500 uS**. + +Sequence diagram showing the interaction between MSC, BSC, and BTS for channel allocation and time alignment. The diagram illustrates the exchange of ASSREQ, CHAN ACTIV, and Idle or speech frames, with time alignment calculations performed by the BTS. + +**Figure 6.1: Initial Time Alignment Procedure** + +#### 6.6.1.3 Initiation at Resource Allocation + +When the BTS receives the CHANNEL ACTIVATION message from the BSC, it allocates the appropriate radio resources and a Channel Codec Unit (CCU). **In case of FR or EFR** the CCU then initiates sending of speech frames (or idle speech frames if speech is not received from the MS) towards the transcoder with normal frame phase for the TDMA channel in question. The "Time Alignment" field in these frames is set to "no change". + +The TRAU will now be in the Initial Time Alignment state. When receiving the first frame it shall start sending speech frames (or idle speech frames) towards the BTS with arbitrary or default phase related to the uplink frame phase. + +When receiving these frames the CCU calculates the timing adjustment required in order to achieve minimum buffer delay and sets the "Time Alignment" field in the uplink frames accordingly. + +The procedures described for the Initial and for the Static Time Alignment states are then followed during the call. + +**In case of AMR or AMR-WB** the CCU shall initiate sending of TRAU No\_Speech frames towards the transcoder with normal frame phase for the TDMA channel in question unless speech is received on the radio interface. The "Time Alignment" field shall be set to "no change", the TAE shall be set to "0.0" and PAB shall be set to "0". The RIF shall correspond to the phase of the uplink radio interface. The CMI / CMR shall be set to "Initial\_Codec\_Mode". + +Consequently, speech transmission will start in uplink and downlink in this mode. In case the BTS supports TFO it shall send the TFO Configuration parameters uplink (see 3GPP TS 28.062). The TRAU will now be in the Initial Time Alignment state. When receiving the first UL TRAU frame it shall start sending No\_Speech frames (or speech frames, if speech is received from the MSC side) towards the BTS with arbitrary or default phase related to the uplink frame phase. After receiving downlink TRAU frames the CCU may perform time alignment and phase alignment (optionally using TAC, TAE and PAB). The CCU shall keep the Codec\_Mode in uplink and downlink fixed to the Initial\_Codec\_Mode until the correct time and phase alignment in downlink TRAU frames is achieved. Then the Codec\_Mode adaptation may be enabled, see also 3GPP TS 45.009. + +#### 6.6.1.4 Time Alignment During Handover + +##### 6.6.1.4.1 BSS External Handover + +For BSS external handover, the procedure described in clause 6.6.1.3 should be used by the new BSC/BTS at resource allocation. + +##### 6.6.1.4.2 BSS Internal Handover + +If TFO is not ongoing and a BSS internal handover has been performed, the timing of the downlink frames may have to be adjusted several steps of 125, 250 or 500 µs. In order to speed up the alignment of the downlink frames, this must be detected by the TRAU, e.g. by detecting the change in the uplink frame timing as described in clause 6.6.1.2. The TRAU should then enter the Initial Time Alignment state and in that state it may perform an adjustment on the downlink equal to the change detected on the uplink. + +In case of AMR or AMR-WB, when TFO is ongoing, the BTS shall not send any time alignment or phase alignment commands and the TRAU shall not perform any time or phase alignment in downlink direction. Instead the BTS shall buffer the speech frames accordingly (see clause 6.6.1.2.1, alternative 3). Alternatively the BTS may perform a phase alignment on the radio interface by sending a RATSCCH message (see clause 6.6.1.2.1, alternative 4), thus avoiding the buffer delay (20ms). + +Please note that optionally before and after handover the AMR or AMR-WB link adaptation should be frozen to the Initial\_Codec\_Mode, until all necessary time and phase alignments have been performed. CMI and CMR should therefore be identical during that period. Consequently a phase mismatch does not matter until the adaptation is enabled. + +### 6.6.2 Procedures for Discontinuous Transmission (DTX) + +The procedures for comfort noise are described in 3GPP TS 46.012, for Full rate speech and in 3GPP TS 46.062 for Enhanced Full rate speech, the overall operation of DTX is described in 3GPP TS 46.031 and in 3GPP TS 46.081 for respectively Full rate speech and Enhanced Full rate speech and the Voice Activity Detector is described in 3GPP TS 46.032 and 3GPP TS 46.082 for respectively Full rate speech and Enhanced full rate speech. The relevant procedures for Adaptive Multi-Rate speech are described in 3GPP TS 26.092, 3GPP TS 26.093 and 3GPP TS 26.094 and for Adaptive Multi-Rate Wideband speech in 3GPP TS 26.192, 3GPP TS 26.193 and 3GPP TS 26.194. For the case of DTX in ongoing TFO see 3GPP TS 28.062. + +The DTX Handler function is considered as a part of the TRAU when remote transcoders are applied. The specification of the DTX Handler is given in 3GPP TS 46.031 for Full rate speech, in 3GPP TS 46.081 for Enhanced Full Rate speech, in 3GPP TS 26.093 for Adaptive Multi-Rate speech and in 3G 26.193 for Adaptive Multi-Rate Wideband speech. + +#### 6.6.2.1 DTX procedures in the uplink direction + +In case of the Full Rate and Enhanced Full Rate speech: In all frames in the uplink direction, the BFI (Bad Frame Indicator), the SID (Silence Descriptor) indicator and the TAF (Time Alignment Flag) indicator is set as output from the RSS (see 3GPP TS 46.031 and 3GPP TS 46.081). + +In the comfort noise states, the MS will transmit a new frame only every 480 ms (24 frames). These frames are transferred in the normal way between the CCU and the TRAU. Between these frames the CCU shall transfer uplink idle speech frames in case of Full Rate Speech and speech frames with BFI set to "1" in case of Enhanced Full rate Speech. + +In case of the Adaptive Multi-Rate or Adaptive Multi-rate Wideband speech all frames are classified by the Rx\_Type, see also 3GPP TS 26.093 and 3GPP TS 26.193. In the comfort noise states, the MS will transmit a new SID\_Update frame only about every 160 ms (8 frames). These frames are transferred in the normal way between the CCU and the TRAU. Between these SID\_Update frames the CCU and TRAU shall transfer "No\_Data" frames uplink. + +#### 6.6.2.2 DTX procedures in the downlink direction + +To inform the DTX handler in the remote transcoder whether downlink DTX may be applied or not, the DTXd bit (C17 in case of Full Rate and Enhanced Full Rate, C19 in case of Adaptive Multi-Rate and Adaptive Multi-Rate Wideband speech in 16 kbit/s and 32 kbit/s multiplexing) in the uplink speech frame is used. The coding is as follows: + +DTXd = 0 : downlink DTX is not applied ("not requested" in case of AMR or AMR-WB); + +DTXd = 1 : downlink DTX is applied ("requested" in case of AMR or AMR-WB). + +Though this parameter is linked with the resource allocation in the BTS at call setup, its value may vary during the connection. + +In case of Full Rate and Enhanced Full Rate speech in the downlink frames the SP (Speech) indicator is set as output from the TX DTX handler (see 3GPP TS 46.031 and 3GPP TS 46.081). + +If downlink DTX is not used, the SP indicator should be coded binary "1". + +In case of the Adaptive Multi-Rate and Adaptive Multi-Rate Wideband speech all downlink frames are classified by the Tx\_Type, see also 3GPP TS 26.093 and 3GPP TS 26.193. In ongoing TFO, in case the distant side uses uplink DTX, downlink DTX may be applied by the TRAU, although DTXd is set to "not requested". For handling in the downlink BTS see 3GPP TS 26.093 and 3GPP TS 26.193 and 28.062. + +## 6.7 Procedures for Data Frames + +### 6.7.1 9.6 and 4.8 kbit/s channel coding + +When rate adaption to 64 Kbit/s is performed at the BTS (sub-64 kbit/s traffic channels are not used), the rate adaption between the format used on the radio interface and the 64 Kbit/s format is made by the RA1/RA1' and the RA2 function as described in GSM. 48.020. This is illustrated in figure 6.2. + +![Diagram illustrating rate adaption at the BTS. It shows three stages: 1. Input: 64 Kbit/s stream entering a box labeled RA2. 2. Intermediate: Output from RA2 is a CCITT V.110 80 bits frame. 3. Output: This frame enters a box containing RA1 and RA1', and the final output is a Channel codec frame.](5addeb78101c342bb315dc3d703eec27_img.jpg) + +``` + +graph LR + A[64 Kbit/s] --> RA2[RA2] + RA2 --> CCITT[CCITT V.110 +80 bits +frame] + CCITT --> RA1[RA1 / RA1'] + RA1 --> Codec[Channel +codec +frame] + +``` + +Diagram illustrating rate adaption at the BTS. It shows three stages: 1. Input: 64 Kbit/s stream entering a box labeled RA2. 2. Intermediate: Output from RA2 is a CCITT V.110 80 bits frame. 3. Output: This frame enters a box containing RA1 and RA1', and the final output is a Channel codec frame. + +**Figure 3GPP TS 48.060/4.2: Rate adaption when performed at the BTS.** + +When sub-64 kbit/s traffic channels are used, up to four data frames are transferred in each TRAU frame. In order to convert between the TRAU frame format and the CCITT 80 bits frame format an additional intermediate rate adaption function, RAA, is applied. This is illustrated in figure 6.3. + +![Diagram showing rate adaptation for 16 kbit/s traffic channels. It illustrates the flow from RA2 (64 Kbit/s) through CCITT V.110 80 bits frame, then through RAA to Abis (4 X 72 + 32 bits frame), then through RAA to CCITT V.110 80 bits frame, and finally through RA1/RA1' to the Channel codec frame.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +graph LR + RA2[RA2] -- "64 Kbit/s" --> CCITT1[CCITT V.110 80 bits frame] + CCITT1 --> RAA1[RAA] + RAA1 --> Abis["Abis 4 X 72 + 32 bits frame"] + Abis --> RAA2[RAA] + RAA2 --> CCITT2[CCITT V.110 80 bits frame] + CCITT2 --> RA1RA1["RA1 | RA1'"] + RA1RA1 --> Channel["Channel codec frame"] + +``` + +Diagram showing rate adaptation for 16 kbit/s traffic channels. It illustrates the flow from RA2 (64 Kbit/s) through CCITT V.110 80 bits frame, then through RAA to Abis (4 X 72 + 32 bits frame), then through RAA to CCITT V.110 80 bits frame, and finally through RA1/RA1' to the Channel codec frame. + +**Figure 3GPP TS 48.060/4.3: Rate adaption when 16 kbit/s traffic channels are used** + +#### 6.7.1.1 The RAA Function + +The RAA function is used to convert between the CCITT V.110 80 bits frame format and the TRAU frame format. When going from the V.110 format to the TRAU frame format the first octet (all bits coded binary "0") in the CCITT V.110 80 bits frame is stripped off. Up to four such frames are then transferred in each TRAU frame as shown in clause 5.3. + +When going from the TRAU frame format to the V.110 format the data frames are separated and the synchronization octet (all bits coded binary "0") is again included. + +The 80 bits V.110 frame is illustrated in figure 6.4, and the modified 72 bits frame is illustrated in figure 6.5. + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|----|---|---|---|---|---|---| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | D1 | X | X | X | X | X | X | +| 2 | 1 | X | X | X | X | X | X | X | +| 3 | 1 | X | X | X | X | X | X | X | +| 4 | 1 | X | X | X | X | X | X | X | +| 5 | 1 | X | X | X | X | X | X | X | +| 6 | 1 | X | X | X | X | X | X | X | +| 7 | 1 | X | X | X | X | X | X | X | +| 8 | 1 | X | X | X | X | X | X | X | +| 9 | 1 | X | X | X | X | X | X | X | + +**Figure 3GPP TS 48.060/4.4: CCITT V.110 80 bits frame** + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|----|---|---|---|---|---|---| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 1 | D1 | X | X | X | X | X | X | +| 1 | 1 | X | X | X | X | X | X | X | +| 2 | 1 | X | X | X | X | X | X | X | +| 3 | 1 | X | X | X | X | X | X | X | +| 4 | 1 | X | X | X | X | X | X | X | +| 5 | 1 | X | X | X | X | X | X | X | +| 6 | 1 | X | X | X | X | X | X | X | +| 7 | 1 | X | X | X | X | X | X | X | +| 8 | 1 | X | X | X | X | X | X | X | + +**Figure 3GPP TS 48.060/4.5: Modified CCITT V.110 72 bits frame transferred in a TRAU data frame position** + +#### 6.7.1.2 The RA1/RA1' Function + +This function is described in 3GPP TS 44.021. + +#### 6.7.1.3 The RA2 Function + +This function is described in 3GPP TS 44.021. + +#### 6.7.1.4 Procedures for 8 kbit/s intermediate rate adaption rate + +For 8 kbit/s intermediate rate adaption rate up to two data frames are transferred in each TRAU frame. The first data frame is transferred in TRAU data frame position 1 and the subsequent data frame is transferred in TRAU data frame position 3 (see clause 5.3). + +In TRAU data frame position 2 and 4, all bits are coded binary "1". + +If the data transfer terminates before the TRAU frame has been completed, the remaining data bit positions in the TRAU frame should be coded binary "1". + +#### 6.7.1.5 Procedures for 16 kbit/s intermediate rate adaption rate + +For 16 kbit/s intermediate rate adaption rate, up to four data frames are transferred in each TRAU frame. The first data frame is transferred in TRAU data frame position 1, the next in data frame position 2 etc. + +If the data transfer terminates before the TRAU frame has been completed, the remaining data bit positions in the TRAU frame should be coded binary "1". + +#### 6.7.1.6 Support of Non-Transparent Bearer Applications + +In 3GPP TS 48.020, the procedures for transfer of non-transparent bearer applications are specified. The 240 bit RLP frame is converted to four modified V.110 80 bit frames. + +The same conversion is applied when transferred in a TRAU frame. The frames are coded as specified in clauses 4.7.4 and 4.7.5. + +### 6.7.2 14.5 kbit/s channel coding + +When rate adaption to 64 Kbit/s is performed at the BTS (sub-64 kbit/s traffic channels are not used), the rate adaption between the format used on the radio interface and the 64 Kbit/s format is as described in 3GPP TS 48.020. + +When sub-64 kbit/s traffic channels are used, up to eight 36 bits frames are transferred in each E-TRAU frame. In order to convert between the E-TRAU frame format and the 36 bits frame format used for the radio interface an additional intermediate rate adaption function, RA1'/RAA', is applied. This is illustrated in figure 6.3.1 (see also 3GPP TS 48.020). + +![Diagram showing rate adaption stages from 64 Kbit/s through RA2, A-TRAU, RAA', E-TRAU, and finally to the Radio Interface frame using RAA'/RA1'.](6b95a21425e452581ef1a50ee2a6d391_img.jpg) + +``` + + +-------+ +-----+ Abis +-----------+ + --| RA2 |-----+-----|RAA' |+----------------| RAA'|RA1' |---+-- + +-------+ | +-----+ +-----+-----+ + 64 Kbit/s A-TRAU E-TRAU Radio + 8 X 36 + 32 320 Interface + bits bits frame + frame frame + +``` + +Diagram showing rate adaption stages from 64 Kbit/s through RA2, A-TRAU, RAA', E-TRAU, and finally to the Radio Interface frame using RAA'/RA1'. + +**Figure 3GPP TS 48.060/4.3.1: Rate adaption when 16 kbit/s traffic channels are used** + +#### 6.7.2.1 The RAA' Function + +See 3GPP TS 48.020 + +#### 6.7.2.2 The RA1'/RAA' Function + +This function is described in 3GPP TS 48.020. + +#### 6.7.2.3 The RA2 Function + +This function is described in 3GPP TS 44.021. + +## 6.8 Frame Synchronization + +### 6.8.1 Search for Frame Synchronization + +**Case of Full Rate, Enhanced Full Rate, Adaptive Multi-Rate (AMR-NB) and Adaptive Multi-Rate Wide Band (AMR-WB):** + +The frame synchronization is obtained by means of the first two octets in each frame, with all bits coded binary "0", and the first bit in octet no. 2, 4, 6, 8, ... 38 coded binary "1". The following 35 bit alignment pattern is used to achieve frame synchronization: + +``` +00000000 00000000 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX +1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX +1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX +1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX +1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX 1XXXXXXX XXXXXXXX +``` + +### 6.8.2 Frame Synchronization After Performing Downlink Timing Adjustments + +If the timing of the downlink speech frames is adjusted, the adjustment is indicated in bits C6 - C11 as described in clauses 4.6.1.1 and 4.6.1.2. The frame synchronization unit shall change its frame synchronization window accordingly. + +### 6.8.3 Frame Synchronization Monitoring and Recovery + +The monitoring of the frame synchronization shall be a continuous process. + +Loss of frame synchronization shall not be assumed unless at least three consecutive frames, each with at least one framing bit error, are detected. + +In case of Full Rate speech: + +If the TRAU looses its frame synchronization it starts a timer $T_{sync} = 1$ second. If $T_{sync}$ expires before frame synchronization is again obtained the TRAU initiates sending of the urgent alarm pattern described in clause 6.10.2. + +The exception from this procedure is when "Resource Release" is detected while $T_{sync}$ is running (see clause 6.3). In this case, the procedure in clause 6.3 shall be followed. + +If loss of frame synchronization is detected by the CCU it starts a timer $T_{sync}$ . If $T_{sync}$ expires before frame synchronization is again obtained the call shall be released and an indication given to O&M. + +$T_{sync}$ is reset every time frame synchronization is again obtained. + +In case of Enhanced Full Rate speech, Adaptive Multi-Rate speech and Adaptive Multi-Rate Wideband speech with 16 kbit/s multiplexing: + +When it detects a framing bit error, the TRAU uses the control bit UFE (uplink Frame Error) in the next downlink TRAU frame to indicate it to the CCU. When the CCU receives a TRAU frame indicating an Uplink Frame Error and which has no errors on the synchronization pattern and the control bits, it starts a timer $T_{syncU}$ . + +If loss of frame synchronization is detected by the CCU it starts a timer $T_{syncD}$ . If $T_{syncD}$ or $T_{syncU}$ expires before frame synchronization is again obtained, the call shall be released as specified in 3GPP TS 48.058 with the case field set to " Remote Transcoder Failure". + +$T_{syncD}$ is reset every time frame synchronisation is again obtained. + +$T_{syncU}$ is reset every time three consecutive TRAU frames are received without Uplink Frame Error indication, without errors on the frame synchronisation pattern and on the control bits. + +$T_{syncD}$ and $T_{syncU}$ are parameters set by O&M (default value = 1 second). + +In case of Adaptive Multi-Rate Wideband speech with 32 kbit/s multiplexing: + +When it detects a framing bit error in channel a or channel b, the TRAU uses the control bit UFE (uplink Frame Error) in the next downlink TRAU frame to indicate it to the CCU. When the CCU receives a TRAU frame indicating an Uplink Frame Error in channel a or in channel b which has no errors on the synchronization pattern and the control bits, it starts a timer $T_{syncU}$ . + +If loss of frame synchronization is detected by the CCU it starts a timer $T_{syncD}$ . If $T_{syncD}$ or $T_{syncU}$ expires before frame synchronization is again obtained, the call shall be released as specified in GSM 08.58 with the case field set to " Remote Transcoder Failure". + +$T_{syncD}$ is reset every time frame synchronisation is again obtained. + +TsyncU is reset every time three consecutive TRAU frames are received without Uplink Frame Error indication, without errors on the frame synchronisation pattern and on the control bits in channel a AND in channel b. + +TsyncD and TsyncU are parameters set by O&M (default value = 1 second). + +In case of Data 14.5 kbit/s: + +The following 17 bit alignment pattern of the Extended Data TRAU Frame is used for Frame Synchronization Monitoring: + +``` +00000000 00000000 1XXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX +XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX +XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX +XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX +XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX +``` + +When it detects a framing bit error, the TRAU uses the control bit UFE (uplink Frame Error) in the next downlink Extended Data TRAU Frame to indicate it to the CCU. When the CCU receives an Extended Data TRAU Frame indicating an Uplink Frame Error and which has no errors on the synchronization pattern and the control bits, it starts a timer TsyncU and TsyncR. + +If loss of frame synchronization is detected by the CCU it starts a timer TsyncD and starts sending Data TRAU Frames in the uplink direction to trigger the TRAU to start sending Data TRAU Frames in the downlink direction to be used for downlink Synchronization Recovery. + +If TsyncR expires before frame synchronization is again obtained, the CCU starts sending Data TRAU Frames in the uplink direction to be used for uplink Synchronization Recovery. + +If TsyncD or TsyncU expires before frame synchronization is again obtained, the call shall be released as specified in 3GPP TS 48.058 with the case field set to " Remote Transcoder Failure". + +TsyncD is reset every time frame synchronization is again obtained. + +TsyncU and TsyncR is reset every time three consecutive TRAU frames are received without Uplink Frame Error indication, without errors on the frame synchronization pattern and on the control bits. + +TsyncD and TsyncU are parameters set by O&M (default value = 1 second) + +TsyncR are a parameter set by O&M (default value = 60 milliseconds). + +## 6.9 Correction/detection of bit errors on the terrestrial circuits + +### 6.9.1 Error Detection on the Control Bits + +For the control bits, (C-bits), no error coding is made. Exception: In case of AMR or AMR-WB the C-Bits are protected by CRC. However, in order to reduce the possibility of misinterpretation of control information due to bit errors, the following procedure should be followed. + +#### 6.9.1.1 General Procedure + +If any undefined combination of the C-bits is received (see clause 5.5), the frame should be reacted upon as received with errors. + +#### 6.9.1.2 Frames for Speech Services + +In addition to the general procedure described in the previous clause, the following procedure should be followed: + +Bits C6 - C11: Time Alignment. + +The full range of the time alignment adjustment should only be applied when the TRAU is in the Initial Time Alignment state (see clauses 4.6.1.1 and 4.6.1.2). + +If, in the Static Time Alignment state, a time alignment order is received indicating an adjustment of more than 250 µs, the next downlink frame should be delayed only one 250 µs step. + +If an uplink frame is received with the "Time Alignment" field set to an unused value, this value should be interpreted as "no change". + +### 6.9.2 Handling of frames received with errors + +If TRAU frame is received in the uplink or downlink with detectable errors in the control bits, then the control information shall be ignored. The speech or data bits may be handled as if no error had been detected. + +If frame synchronisation has been lost (see clause 6.8.3) in the uplink direction the TRAU shall: + +- for speech, mute the decoded speech as if it has received frames with errors (cf. 3GPP TS 46.011 and 3GPP TS 46.061 and 3GPP TS 26.091); +- for data, send idle frames as defined in 3GPP TS 48.020 to the MSC/interworking. + +#### 6.9.2.1 In case of Full Rate speech + +If frame synchronisation has been lost in the downlink direction then the same procedure shall be followed as when frame synchronisation is lost on the PCM link. + +#### 6.9.2.2 In case of Enhanced Full Rate, Adaptive Multi-Rate and Adaptive Multi-Rate Wideband speech + +For speech calls, the CCU shall transmit a layer two fill frame on the air interface if frame synchronization has been lost in the downlink direction. + +If a CRC error is detected in a downlink TRAU speech frame a solution can be to transmit a layer two fill frame on the air interface, another solution can be to replace the bad part of the TRAU speech frame only. The choice of the solution is left open. + +If a CRC error is detected in an uplink TRAU speech frame, the TRAU speech frame shall be regarded as bad or partly bad and the TRAU shall apply the procedure defined in 3GPP TS 46.061, 3GPP TS 26.091 or 3GPP TS 26.191 respectively. + +## 6.10 Procedures for Operation & Maintenance + +The general procedures for Operation and Maintenance are described in 3GPP TS 12.21. + +If the transcoders are positioned outside the BTS, some O&M functions will be required for the TRAU and the CCU. In particular this applies for transcoders positioned at the MSC site. + +The transcoders outside the BTS are considered a part of the BSC, and the O&M functions for the TRAU should therefore be implemented in the BSC. + +The CCU is a part of the BTS and the O&M functions for this unit should therefore be implemented in the BTS. + +### 6.10.1 Transfer of O&M Information Between the TRAU and the BSC + +The transfer of O&M information between the BSC and the TRAU is possible to do in two ways. Either it is handled directly between the BSC and the TRAU or a BTS is used as a message transfer point. The choice between the two methods is up to the manufacturer of the BSC: + +- i) The transfer of O&M information between the BSC and the TRAU is handled internally by the BSC. The O&M signalling between the TRAU and the BSC may either be handled by proprietary BSC solutions or the O&M TRAU frames defined in clauses 3.2 and 3.5.2 could be used. In the latter case, the BSC has to act as a terminal for the O&M TRAU frames sent between the TRAU and the BSC. +- ii) The O&M information between the TRAU and the BSC is transferred using O&M TRAU frames between the TRAU and the CCU in a BTS. The BTS then acts as a relay function between the O&M TRAU frames and the associated O&M messages sent between the BTS and the BSC. + +### 6.10.2 Procedures in the TRAU + +In case of urgent fault conditions in the TRAU, e.g. loss of frame synchronization, non-ability of the transcoder to process data etc., this should if possible, be signalled to the BTS/BSC as an urgent alarm pattern. The urgent alarm pattern is a continuous stream of binary "0". + +If O&M TRAU frames information between the TRAU and the BSC is transferred using O&M frames between the CCU in a BTS and the TRAU, the TRAU sends O&M frames periodically until the identical O&M TRAU frame is received for acknowledgement. The period is at least 64\*20ms (1,28 sec). + +In case of minor fault conditions, when no immediate action is required, the TRAU may send O&M frames indicating the fault instead of the urgent alarm pattern. + +### 6.10.3 Procedures in the BSC + +The BSC should be able to detect a faulty TRAU, take it out of service and give an indication to O&M. A faulty TRAU could be detected e.g. by routine tests, alarms from the TRAU, release of call initiated by the BTS due to remote transcoder failure etc. How this is handled by the BSC is regarded as a BSC internal matter. + +#### 6.10.3.1 Use of O&M Frames + +The use and coding of O&M TRAU frames is left to the implementor of the BSC/TRAU. + +If O&M TRAU frames are used, they are always carrying 264 data bits. + +Any corresponding O&M message between the BSC and the BTS shall always carry all 264 O&M data bits. + +### 6.10.4 Procedures in the BTS + +If a CCU in a BTS receives O&M TRAU frames from the TRAU, the BTS shall: + +- send the identical frame to the TRAU for acknowledgement; and +- put the 264 data bits from the received frames into an appropriate O&M message and send it to the BSC. + +If the CCU receives O&M frames during a call then "stolen frames" shall be indicated to the MS and layer 2 frames of format A (see 3GPP TS 44.006) shall be transmitted. + +If the CCU receives O&M frames during a data call, then the same procedure shall be used as when V.110 frame is lost. + +If receiving an O&M message from the BSC, carrying TRAU O&M information, the BTS puts the 264 data bits from the received message into an O&M TRAU frame and then the CCU allocated to the addressed connection sends the frame to the TRAU in one single O&M TRAU frame. Repetition is done according to 3GPP TS 12.21. + +In case of a faulty CCU, the O&M procedures are BTS internal. + +If the CCU receives the urgent alarm pattern, the BTS shall initiate release of the call as specified in 3GPP TS 48.058 with the cause field set to "Remote Transcoder Failure". + +# Annex A (informative): Change History + +| Change history | | | | | | +|----------------|-----------|------|-----|---------------------------------------------------------------------------------------|------------------| +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +| GP-04 | - | - | - | April 2001. Conversion to 3GPP layout and number.
References have been updated. | 48.0.0
v4.0.0 | +| - | - | - | - | Figure 4.1 now made visible... | 4.0.1 | +| GP-08 | GP-020182 | 001 | | Handover Complete | 4.1.0 | +| GP-09 | GP-020523 | 002 | | Generic Configuration Frames for TFO | 5.0.0 | +| GP-09 | GP-021251 | 003 | 3 | Introduction of WB-AMR | 5.0.0 | +| GP-10 | GP-022071 | 005 | 1 | Simplifications for AMR-WB TRAU Frames | 5.1.0 | +| GP-11 | GP-022534 | 006 | | Correction of References in Clause 5.5.1 | 5.2.0 | +| | | | | | | +| GP-23 | | | | Version for Release 6 | 6.0.0 | +| GP-35 | GP-071207 | 0009 | | Forgotten bits in TRAU frame for AMR-WB | 6.1.0 | +| GP-35 | GP-071247 | 0011 | | Editorial correction of DTXd bit position for AMR-WB speech in 16 kbit/s multiplexing | 6.1.0 | +| GP-35 | | | | Version for Release 7 | 7.0.0 | +| GP-40 | | | | Version for Release 8 | 8.0.0 | +| GP-44 | | | | Version for Release 9 | 9.0.0 | +| GP-49 | | | | Version for Release 10 | 10.0.0 | +| GP-55 | | | | Version for Release 11 | 11.0.0 | +| GP-63 | | | | Version for Release 12 (frozen at SP-65) | 12.0.0 | +| GP-68 | | | | Version for Release 13 (frozen at SP-70) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48061/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/48_series/48061/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a13a8036015c4b24fd3ce80619e6467ed97a9ce1 --- /dev/null +++ b/marked/Rel-16/48_series/48061/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4de9e3f12cd4662ef35e64a5f6721b7f6246ff6842f237cd6d535974c00591a7 +size 153349 diff --git a/marked/Rel-16/48_series/48061/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-16/48_series/48061/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e10881ec16f641ed6e1f2e672c421c21441ab6ee --- /dev/null +++ b/marked/Rel-16/48_series/48061/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b87ffdc824d1d0abed51211bde6957ccf63568b67861842471cd9bbaad044399 +size 90552 diff --git a/marked/Rel-16/48_series/48061/8be52e8ae172cee527c14d299d386f3c_img.jpg b/marked/Rel-16/48_series/48061/8be52e8ae172cee527c14d299d386f3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6422cf59c656ce87c47ca103391fc754908147a --- /dev/null +++ b/marked/Rel-16/48_series/48061/8be52e8ae172cee527c14d299d386f3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:124469a7fc0d5a5e6dbe83dde7e35f0cba2ecf60fcf79cebb406a02e7bab7f47 +size 34584 diff --git a/marked/Rel-16/48_series/48061/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/48_series/48061/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ee8f4be51174375cb87888f4d1bde2adda916e7 --- /dev/null +++ b/marked/Rel-16/48_series/48061/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79b2c52a81a963e285bc1f7e65dac8f3ae2eeb0ba73caa00e5d69289286d7ef2 +size 149848 diff --git a/marked/Rel-16/48_series/48061/f732d3320afe06d979aabbd366184254_img.jpg b/marked/Rel-16/48_series/48061/f732d3320afe06d979aabbd366184254_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9631ab55166631838911a2737116045e69ab6c58 --- /dev/null +++ b/marked/Rel-16/48_series/48061/f732d3320afe06d979aabbd366184254_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d16715accc5e976eefdc729cfebf7cbaabc3344b7d489e80a9e19c52204565fe +size 16024 diff --git a/marked/Rel-16/48_series/48061/raw.md b/marked/Rel-16/48_series/48061/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5f3ea37280279d233b180818c3bcda104e071a98 --- /dev/null +++ b/marked/Rel-16/48_series/48061/raw.md @@ -0,0 +1,1776 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General approach ..... | 7 | +| 5 Frame structure ..... | 9 | +| 5.1 16 kbit/s submultiplexing..... | 9 | +| 5.1.1 Frames for Speech Services..... | 9 | +| 5.1.1.1 Frame for Half Rate speech ..... | 9 | +| 5.1.1.2 Frames for Adaptive Multi-Rate Speech ..... | 9 | +| 5.1.2 Data frame ..... | 10 | +| 5.1.3 O&M frame ..... | 11 | +| 5.1.4 Coding ..... | 11 | +| 5.1.4.1 Coding of frames for speech services..... | 12 | +| 5.1.4.1.1 Coding of frames for Half Rate speech Control bits (C-bits): ..... | 12 | +| 5.1.4.1.2 Coding of frames for Adaptive Multi-Rate speech..... | 13 | +| 5.1.4.2 Coding of data frames..... | 13 | +| 5.1.4.3 Coding of O&M frames..... | 14 | +| 5.1.5 Order of Bit Transmission..... | 14 | +| 5.2 8 kbit/s submultiplexing..... | 15 | +| 5.2.1 Frames for Speech Services..... | 15 | +| 5.2.1.1 Frame for Half Rate Speech..... | 15 | +| 5.2.1.2 Frames for Adaptive Multi-Rate Speech ..... | 15 | +| 5.2.1.2.1 Frame for Lower Codec Modes ..... | 15 | +| 5.2.1.2.2 Speech frame for Codec Mode 6,70 kBit/s ..... | 16 | +| 5.2.1.2.3 Speech frame for Codec Mode 7,40 kBit/s ..... | 16 | +| 5.2.1.2.4 Speech frame for Codec Mode 7,95 kBit/s ..... | 17 | +| 5.2.1.3 Frames for Speech Codec Configuration Exchange ..... | 17 | +| 5.2.2 Data frame ..... | 18 | +| 5.2.3 O&M frame ..... | 18 | +| 5.2.4 Coding ..... | 19 | +| 5.2.4.1 Coding for Half Rate Speech and Half Rate Data Services..... | 19 | +| 5.2.4.1.1 Uplink coding..... | 19 | +| 5.2.4.1.2 Downlink coding..... | 21 | +| 5.2.4.2 Coding for Adaptive Multi-Rate Speech ..... | 22 | +| 5.2.4.2.1 No_Speech Frame ..... | 22 | +| 5.2.4.2.2 Speech Frames for 4,75, 5,15 and 5,90 kBit/s..... | 23 | +| 5.2.4.2.3 Speech Frame for 6,70 kBit/s..... | 24 | +| 5.2.4.2.4 Speech Frame for 7,40 kBit/s..... | 25 | +| 5.2.4.2.5 Speech Frame for 7,95 kBit/s..... | 25 | +| 5.2.5 Order of Bit Transmission..... | 25 | +| 6 Procedures..... | 26 | +| 6.1 Remote Control of Transcoders and Rate Adaptors..... | 26 | +| 6.2 Resource Allocation ..... | 26 | +| 6.3 Resource Release..... | 26 | +| 6.4 In Call Modification..... | 27 | +| 6.5 Transfer of Idle Frames, Handling of missing data..... | 27 | +| 6.6 Procedures for Speech Frames ..... | 27 | +| 6.6.1 Time Alignment of Speech Frames ..... | 27 | +| 6.6.1.1 16 kbit/s submultiplexing..... | 28 | +| 6.6.1.1.1 Downlink Time Alignment ..... | 28 | +| 6.6.1.1.2 Uplink Time Alignment ..... | 30 | +| 6.6.1.1.3 Initiation at Resource Allocation..... | 30 | + +| | | | +|------------------------|-----------------------------------------------------------------------------|----| +| 6.6.1.1.4 | Time Alignment during Handover ..... | 30 | +| 6.6.1.2 | 8 kbit/s submultiplexing..... | 30 | +| 6.6.1.2.1 | Downlink Time Alignment ..... | 30 | +| 6.6.1.2.2 | Uplink Time Alignment ..... | 32 | +| 6.6.1.2.3 | Initiation at Resource allocation..... | 33 | +| 6.6.1.2.4 | Time Alignment during handover ..... | 33 | +| 6.6.2 | Procedures for Discontinuous Transmission (DTX) ..... | 33 | +| 6.6.2.1 | DTX procedures in the uplink direction ..... | 33 | +| 6.6.2.2 | DTX procedures in the downlink direction ..... | 34 | +| 6.7 | Procedures for Data Frames ..... | 34 | +| 6.7.1 | The RAA Function ..... | 34 | +| 6.7.2 | The RA1/RA1' Function..... | 35 | +| 6.7.3 | The RA2 Function ..... | 35 | +| 6.7.4 | Procedures for 8 kbit/s intermediate rate adaption rate ..... | 35 | +| 6.7.5 | Support of Non-Transparent Bearer Applications..... | 36 | +| 6.8 | Frame Synchronization ..... | 36 | +| 6.8.1 | 16 kbit/s submultiplexing ..... | 36 | +| 6.8.1.1 | Search for Frame Synchronization ..... | 36 | +| 6.8.1.2 | Frame Synchronization After Performing Downlink Timing Adjustments ..... | 36 | +| 6.8.1.3 | Frame Synchronization Monitoring and Recovery..... | 36 | +| 6.8.2 | 8 kbit/s submultiplexing ..... | 37 | +| 6.8.2.1 | Search for Frame Synchronization ..... | 37 | +| 6.8.2.1.1 | For Half Rate speech and data..... | 37 | +| 6.8.2.1.2 | For Adaptive Multi-Rate speech..... | 37 | +| 6.8.2.2 | Frame Synchronization Monitoring and Recovery..... | 38 | +| 6.8.2.2.1 | For Half Rate speech and data..... | 38 | +| 6.8.2.2.2 | For Adaptive Multi-Rate speech..... | 38 | +| 6.9 | Correction/detection of bit errors ..... | 38 | +| 6.9.1 | 16 kbit/s submultiplexing ..... | 38 | +| 6.9.1.1 | Error Detection on the Control Bits ..... | 38 | +| 6.9.1.1.1 | General Procedure ..... | 38 | +| 6.9.1.1.2 | Frames for Half Rate speech..... | 39 | +| 6.9.1.2 | Handling of frames received with errors for Half Rate speech and data ..... | 39 | +| 6.9.2 | 8 kbit/s submultiplexing ..... | 39 | +| 6.9.2.1 | Error Detection on the Control Bits ..... | 39 | +| 6.9.2.2 | Handling of frames received with errors ..... | 40 | +| 6.10 | Procedures for Operation & Maintenance..... | 40 | +| 6.10.1 | Transfer of O&M Information Between the TRAU and the BSC..... | 40 | +| 6.10.2 | Procedures in the TRAU ..... | 40 | +| 6.10.3 | Procedures in the BSC..... | 40 | +| 6.10.3.1 | Use of O&M Frames..... | 40 | +| 6.10.4 | Procedures in the BTS..... | 41 | +| Annex A (informative): | Change History..... | 42 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the protocol between the Base Transceiver Station (BTS) and the remote Transcoder/Rate Adaption Unit (TRAU) for speech and data on half rate traffic channel (TCH/H). + +For Half Rate speech and half rate data the protocol is specified for 8 kbit/s and 16 kbit/s submultiplexing scheme. + +For Adaptive Multi-Rate speech the present document specifies the 8 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). The specification for 16 kBit/s submultiplexing is given in Rec 3GPP TS 48.060, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). + +The present document should be considered together with the 3GPP TS 46 series, 3GPP TS 44.021 (Rate Adaption on the MS-BSS Interface) and 3GPP TS 48.020 (Rate Adaption on the BTS/MSC 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 01.02: "Digital cellular telecommunication system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". +- [2] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications". +- [3] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [4] 3GPP TS 45.003: "Channel coding". + +- [5] 3GPP TS 46.021: "Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- [6] 3GPP TS 46.022: "Half rate speech; Comfort noise aspects for half rate speech traffic channels". +- [7] 3GPP TS 46.041: "Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [8] 3GPP TS 46.042: "Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels". +- [9] 3GPP TS 48.008: "Mobile-services Switching Centre – Base Station System (MSC-BSS) interface; Layer 3 specification". +- [10] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [11] 3GPP TS 48.052: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Interface principles". +- [12] 3GPP TS 48.054: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 1 structure of physical circuits". +- [13] 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification". +- [14] 3GPP TS 12.21: "Digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages on the A-bis interface". +- [15] ITU-T Recommendation I.460: "Multiplexing, rate adaption and support of existing interfaces". +- [16] ITU-T Recommendation V.110: "Support of data terminal equipments (DTEs) with V-Series interfaces by an integrated services digital network". +- [24] 3GPP TS 26.071: "Adaptive Multi-Rate speech processing functions, General Description." +- [25] 3GPP TS 26.090: "Adaptive Multi-Rate speech transcoding". +- [26] Void. +- [27] 3GPP TS 26.092: "Comfort noise aspect for Adaptive Multi-Rate speech traffic channels". +- [28] Void. +- [29] Void. +- [30] Void. +- [31] 3GPP TS 48.060: "Inband control of remote transcoders and rate adaptors". +- [32] 3GPP TS 48.062: "Inband Tandem Free Operation (TFO) of Speech Codecs". +- [33] 3GPP TS 46.020: "Half Rate Speech Transcoding". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +No specific definitions apply to the present document. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|------------------| +| ACS | Active_Codec_Set | +|-----|------------------| + +| | | +|------|-----------------------------------| +| AMR | Adaptive Multi-Rate | +| BSC | Base Station Controller | +| BTS | Base Transceiver Station | +| CCU | Channel Codec Unit | +| CMC | Codec_Mode_Command | +| CMI | Codec_Mode_Indication | +| CMR | Codec_Mode_Request | +| DFE | Downlink Frame Error | +| ICM | Initial_Codec_Mode | +| PAB | Phase Alignment Bit | +| PAC | Phase Alignment Command | +| RA | Rate Adaption | +| RIF | Request or Indication Flag | +| TAC | Time Alignment Command | +| TAE | Time Alignment Extension | +| TFO | Tandem Free Operation | +| TFOE | TFO Enable | +| TRAU | Transcoder and Rate Adaption Unit | +| UFE | Uplink Frame Error | + +Other abbreviations used in the present document are listed in 3GPP TS 21.905. + +# --- 4 General approach + +The TRAU shall be controlled by the BTS when it is positioned remote from the BTS. In this case, the speech/data information and TRAU control signals exchanged between the Channel Codec Unit (CCU) in the BTS and the TRAU shall be transferred in frames denoted "TRAU frames". + +The TRAU frames may be carried by either 16 kbit/s traffic channels or 8 kbit/s channels. The choice of the traffic channel bit rate or submultiplexing scheme is operator dependent. + +The TRAU frames have a fixed length of: + +- 160 bits (20 ms) when 8 kbit/s submultiplexing is used; +- 320 bits (20 ms) when 16 kbit/s submultiplexing is used. + +The protocol between the BTS and the TRAU should be the same if the TRAU is positioned either at the MSC site or at the BSC site. In the first case, the BSC should be considered as transparent for 16 kbit/s and 8 kbit/s channels. + +The TRAU is considered a part of the BSC when the TRAU is remote from the BTS (see 3GPP TS 48.052), and the signalling between the BSC and the TRAU (e.g. detection of call release, handover and transfer of O&M information) may be performed by using BSC internal signals. However, the signalling between the CCU and the TRAU, using TRAU frames as specified in the present document, is mandatory when the TRAU is remote from the BTS. + +For data transfer, a conversion function is required, in addition to the conversion/rate adaption specified in 3GPP TS 48.020, to adapt ITU-T V.110 frames to the TRAU data frames. This function constitutes the RAA. + +NOTE: If standard 64 kbit/s switching is used in the BSC, multiplexing according to ITU-T Recommendation I.460 should apply at both sides of the switch. + +A possible configuration of the TRAU and the CCU is shown in figure 4.1. + +The functions inside the TRAU are: + +- "Remote Transcoder and Rate Adaptor Control Function" (RTRACF); +- "Remote Speech Handler Function" (RSHF); +- the RAA function; +- the RA2 function; +- the transcoder function. + +The functions inside the CCU are: + +- "Transcoder and Rate Adaptor Control Function" (TRACF); +- "Speech Handler Function" (SHF); +- the RAA function; +- the RA1/RA1' function; +- the channel codec function. + +The present document does not describe the procedures inside the TRAU and the CCU. The layout in figure 4.1 is only intended as a reference model. + +![Functional entities for handling of control of remote transcoders and rate adaptors diagram](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +The diagram illustrates the functional entities for handling control of remote transcoders and rate adaptors, divided into two main components: the TRAU (Traffic RAN Interface) on the left and the CCU (Control Center Unit) on the right. + +**TRAU (Left):** + +- Contains a **Transcoder Function (note)** and a **Remote Speech Handler Function**. +- Receives **Speech** (solid line) and **Data** (dashed line) from the left. +- Connects to a **Remote Transcoder and RA Control Function** (solid line). +- Connects to **RA2** (solid line) and **RAA** (dashed line). +- Outputs to the CCU via two paths: **8kbit/s 160bit/20ms** (solid line) and **16 kbit/s 320bit/20ms** (dashed line). + +**CCU (Right):** + +- Contains a **Speech Handler Function**, a **Transcoder and RA Control Function**, **RAA**, **RA1**, **RA1'**, and a **Channel Codec Function**. +- Receives **Speech** (solid line) and **Data** (dashed line) from the TRAU. +- Connects to the **Channel Codec Function** (solid line). +- Outputs **Radio frames** (dashed line) to the right. +- Internal connections: **Speech** (solid line) between SHF and TRACF; **Data** (dashed line) between TRACF and RA1/RA1'; **L3 control signals** (dashed line) between TRACF and RA1/RA1'; **RAA** (solid line) connects to TRACF and RA1/RA1'. + +**Legend:** + +- Solid line: **Speech/Data** +- Dashed line: **Control** + +Functional entities for handling of control of remote transcoders and rate adaptors diagram + +NOTE: This technical specification assumes the DTX handler function to be part of the Transcoder Function. + +**Figure 3GPP TS 48.061/4.1: Functional entities for handling of control of remote transcoders and rate adaptors** + +# 5 Frame structure + +## 5.1 16 kbit/s submultiplexing + +### 5.1.1 Frames for Speech Services + +#### 5.1.1.1 Frame for Half Rate speech + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 3 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 4 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | +| 5 | 1 | UFI | D1 | D2 | D3 | D4 | D5 | D6 | +| 6 | D7 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | +| 7 | 1 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | +| 8 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | +| 9 | 1 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | +| 10 | D37 | D38 | D39 | D40 | D41 | D42 | D43 | D44 | +| 11 | 1 | CRC2 | CRC1 | CRC0 | D45 | D46 | D47 | D48 | +| 12 | D49 | D50 | D51 | D52 | D53 | D54 | D55 | D56 | +| 13 | 1 | D57 | D58 | D59 | D60 | D61 | D62 | D63 | +| 14 | D64 | D65 | D66 | D67 | D68 | D69 | D70 | D71 | +| 15 | 1 | D72 | D73 | D74 | D75 | D76 | D77 | D78 | +| 16 | D79 | D80 | D81 | D82 | D83 | D84 | D85 | D86 | +| 17 | 1 | D87 | D88 | D89 | D90 | D91 | D92 | D93 | +| 18 | D94 | D95 | D96 | D97 | D98 | D99 | D100 | D101 | +| 19 | 1 | D102 | D103 | D104 | D105 | D106 | D107 | D108 | +| 20 | D109 | D110 | D111 | D112 | 1 | 1 | 1 | 1 | +| 21 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 22 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 23 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 24 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 25 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 26 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 27 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 28 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 29 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 30 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 31 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 32 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 33 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 34 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 35 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 36 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 37 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 38 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 39 | 1 | 1 | 1 | 1 | 1 | 1 | C16 | C17 | +| 40 | C18 | C19 | C20 | C21 | T1 | T2 | T3 | T4 | + +#### 5.1.1.2 Frames for Adaptive Multi-Rate Speech + +See 3GPP TS 48.060 for 16 kbit/s submultiplexing. + +### 5.1.2 Data frame + +| Octet no. | Bit number | | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------|------------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | | +| 3 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | | +| 4 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | | +| 5 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | | +| 6 | 1 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | | +| 7 | 1 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | | +| 8 | 1 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | Data frame | +| 9 | 1 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | position 1 | +| 10 | 1 | D36 | D37 | D38 | D39 | D40 | D41 | D42 | | +| 11 | 1 | D43 | D44 | D45 | D46 | D47 | D48 | D49 | | +| 12 | 1 | D50 | D51 | D52 | D53 | D54 | D55 | D56 | | +| 13 | 1 | D57 | D58 | D59 | D60 | D61 | D62 | D63 | | +| 14 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 15 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 16 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 17 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 18 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 19 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 20 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 21 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 22 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 23 | 1 | D'1 | D'2 | D'3 | D'4 | D'5 | D'6 | D'7 | | +| 24 | 1 | D'8 | D'9 | D'10 | D'11 | D'12 | D'13 | D'14 | | +| 25 | 1 | D'15 | D'16 | D'17 | D'18 | D'19 | D'20 | D'21 | | +| 26 | 1 | D'22 | D'23 | D'24 | D'25 | D'26 | D'27 | D'28 | Data frame | +| 27 | 1 | D'29 | D'30 | D'31 | D'32 | D'33 | D'34 | D'35 | position 3 | +| 28 | 1 | D'36 | D'37 | D'38 | D'39 | D'40 | D'41 | D'42 | | +| 29 | 1 | D'43 | D'44 | D'45 | D'46 | D'47 | D'48 | D'49 | | +| 30 | 1 | D'50 | D'51 | D'52 | D'53 | D'54 | D'55 | D'56 | | +| 31 | 1 | D'57 | D'58 | D'59 | D'60 | D'61 | D'62 | D'63 | | +| 32 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| 33 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | + +| | | | | | | | | | +|----|---|---|---|---|---|---|---|---| +| 34 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 35 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 36 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 37 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 38 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 39 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 40 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | + +### 5.1.3 O&M frame + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 3 | 1 | C1 | C2 | C3 | C4 | C5 | C6 | C7 | +| 4 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | +| 5 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | +| 6 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | +| 7 | 1 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | +| 8 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | +| 9 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | D37 | +| 10 | D38 | D39 | D40 | D41 | D42 | D43 | D44 | D45 | +| 11 | 1 | D46 | D47 | D48 | D49 | D50 | D51 | D52 | +| 12 | D53 | D54 | D55 | D56 | D57 | D58 | D59 | D60 | +| 13 | 1 | D61 | D62 | D63 | D64 | D65 | D66 | D67 | +| 14 | D68 | D69 | D70 | D71 | D72 | D73 | D74 | D75 | +| 15 | 1 | D76 | D77 | D78 | D79 | D80 | D81 | D82 | +| 16 | D83 | D84 | D85 | D86 | D87 | D88 | D89 | D90 | +| 17 | 1 | D91 | D92 | D93 | D94 | D95 | D96 | D97 | +| 18 | D98 | D99 | D100 | D101 | D102 | D103 | D104 | D105 | +| 19 | 1 | D106 | D107 | D108 | D109 | D110 | D111 | D112 | +| 20 | D113 | D114 | D115 | D116 | D117 | D118 | D119 | D120 | +| 21 | 1 | D121 | D122 | D123 | D124 | D125 | D126 | D127 | +| 22 | D128 | D129 | D130 | D131 | D132 | D133 | D134 | D135 | +| 23 | 1 | D136 | D137 | D138 | D139 | D140 | D141 | D142 | +| 24 | D143 | D144 | D145 | D146 | D147 | D148 | D149 | D150 | +| 25 | 1 | D151 | D152 | D153 | D154 | D155 | D156 | D157 | +| 26 | D158 | D159 | D160 | D161 | D162 | D163 | D164 | D165 | +| 27 | 1 | D166 | D167 | D168 | D169 | D170 | D171 | D172 | +| 28 | D173 | D174 | D175 | D176 | D177 | D178 | D179 | D180 | +| 29 | 1 | D181 | D182 | D183 | D184 | D185 | D186 | D187 | +| 30 | D188 | D189 | D190 | D191 | D192 | D193 | D194 | D195 | +| 31 | 1 | D196 | D197 | D198 | D199 | D200 | D201 | D202 | +| 32 | D203 | D204 | D205 | D206 | D207 | D208 | D209 | D210 | +| 33 | 1 | D211 | D212 | D213 | D214 | D215 | D216 | D217 | +| 34 | D218 | D219 | D220 | D221 | D222 | D223 | D224 | D225 | +| 35 | 1 | D226 | D227 | D228 | D229 | D230 | D231 | D232 | +| 36 | D233 | D234 | D235 | D236 | D237 | D238 | D239 | D240 | +| 37 | 1 | D241 | D242 | D243 | D244 | D245 | D246 | D247 | +| 38 | D248 | D249 | D250 | D251 | D252 | D253 | D254 | D255 | +| 39 | 1 | D256 | D257 | D258 | D259 | D260 | D261 | D262 | +| 40 | D263 | D264 | S1 | S2 | S3 | S4 | S5 | S6 | + +### 5.1.4 Coding + +In the following clauses, the coding of the frames is described. Any spare or not used control bits should be coded binary "1". + +#### 5.1.4.1 Coding of frames for speech services + +##### 5.1.4.1.1 Coding of frames for Half Rate speech Control bits (C-bits): + +| Description | Uplink | Downlink | +|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------| +| Frame type
(Bits C1 - C4) | C1 C2 C3 C4
0 0 0 1 | C1 C2 C3 C4
1 1 1 0 | +| Channel type
Bit C5 | 1: half rate | 1: half rate | +| Time Alignment
(Bits C6 - C11) | Binary number indicating the required timing adjustment to be in steps of 250/500 µs.
The following values apply for the coding
C6 C7 . . . C11
0 0 0 0 0 0 No change in frame timing
0 0 0 0 0 1 Delay frame 1 * 500 µs
0 0 0 0 1 0 Delay frame 2 * 500 µs
. . . . .
. . . . .
1 0 0 1 1 1 Delay frame 39 * 500 µs
1 0 1 0 0 0 Not used
. . . . .
1 1 1 1 0 1 Not used
1 1 1 1 1 0 Delay frame 1 * 250 µs
1 1 1 1 1 1 Advance frame 250 µs | Binary number indicating the timing adjustment made. | +| Uplink
Bad Frame Indicator (BFI)
C12 (see 3GPP TS 46.041) | 0: BFI = 0
1: BFI = 1 | | +| Downlink
Uplink Frame Error (UFE)
C12 (see clause 6.8.1.3) | | 0: UFE = 0: bad uplink framing
1: UFE = 1: good uplink framing | +| Silence Descriptor (SID)
C13-C14
(see 3GPP TS 46.041) | C13 C14: SID
SID1 SID0
0 0: SID = 0
0 1: SID = 1
1 0: SID = 2 | | +| Time Alignment Flag (TAF)
C15
(see 3GPP TS 46.041) | 0: TAF = 0
1: TAF = 1 | Spare | +| Speech indicator (SP)
C16
(see 3GPP TS 46.041) | Spare | 0: SP = 0
1: SP = 1 | +| DTX downlink indicator (DTXd)
C17 | 0: Downlink DTX shall not be applied
1: Downlink DTX shall be applied | Spare | +| Bits C18 - C21 | Spare | Spare | + +UFI bit: Unreliable Frame Indication (see 3GPP TS 46.041). + +This bit is set to binary "1" in the downlink direction. + +###### Data Bits (D-bits) + +Bits D1 .. D112: Speech block transferred in the same order as output from the transcoder (see 3GPP TS 46.020). + +###### Cyclic Redundancy Check bits (CRC-bits) + +Bits CRC0 .. CRC2: CRC of the bits D1 to D44. + +The bits are coded according to a cyclic code using the generator polynomial: + +$$g(X) = X^3 + X + 1$$ + +The encoding of the cyclic code is performed in a systematic form, which means that, in GF(2), the polynomial: + +$$D1 * X^{46} + D2 * X^{45} + \dots + D44 * X^3 + CRC2 * X^2 + CRC1 * X + CRC0.$$ + +where CRC0, CRC1, CRC2 are the parity bits, when divided by $g(X)$ yields a remainder equal to: + +$$1 + X + X^2.$$ + +###### Time Alignment Bits + +Bits T1 .. T4: Bits positioned at the end of the downlink and uplink TRAU speech frames. + +Downlink: + +If the timing of the frame is to be advanced 250 µs, these 4 bits are not transferred in order to reduce the frame length accordingly. When transferred, the bits are set to binary "1". + +Uplink: + +T1 and T2 are set to binary "1". + +If the timing of the frame is to be advanced 125 µs, the bits T3 and T4 are not transferred in order to reduce the frame length accordingly. When transferred, the bits are set to binary "1" (see clause 6.6.1.1.2). + +##### 5.1.4.1.2 Coding of frames for Adaptive Multi-Rate speech + +See 3GPP TS 48.060 for 16 kBit/s submultiplexing. + +#### 5.1.4.2 Coding of data frames + +Any spare or not used control bits should be coded binary "1". + +##### Control bits (C-bits): + +| Description | Uplink | Downlink | +|-----------------------------------------------------------------|------------------------------|-------------------------------------------------------------------| +| Frame type
Bits C1-C4 | C1 C2 C3 C4
0 1 0 0: Data | C1 C2 C3 C4
1 0 1 1: Data | +| Channel type
Bit C5 | 1: half rate | 1: half rate | +| Intermediate RA bit rate
Bit C6 | 0: 8 kbit/s | 0: 8 kbit/s | +| Bits C7 - C11 | Spare | Spare | +| Bit C12
Uplink Frame Error (UFE)
C12 (see clause 6.8.1.3) | Spare | 0: UFE = 0: bad uplink framing
1: UFE = 1: good uplink framing | +| Bits C13-C15 | Spare | Spare | + +##### Idle data frame + +An idle data frame is a data frame with all data bit positions set to binary "1" (i.e. all bits of the modified V.110 frames are set to "1"). + +#### 5.1.4.3 Coding of O&M frames + +##### Control bits (C-bits): + +| Description | Uplink | Downlink | +|--------------------------|--------------|---------------------------------| +| Frame type | C1 C2 C3 C4 | C1 C2 C3 C4 | +| Bits C1-C4 | 0 0 1 0: O&M | 1 1 0 1: O&M | +| Channel type | | | +| Bit C5 | 1: half rate | 1: half rate | +| Bits C6 - C11 | Spare | Spare | +| Bit C12 | Spare | | +| Uplink Frame Error (UFE) | | 0: UFE = 0: bad uplink framing | +| C12 (see clause 6.8.1.3) | | 1: UFE = 1: good uplink framing | +| Bits C13-C15 | Spare | Spare | + +##### Data Bits (D-bits) + +Bits D1 .. D264: Bits used for transfer of O&M information. The coding and use of these bits are left to the manufacturer of the BSC/TRAU. + +##### Spare Bits (S-bits) + +Bits S1 .. S6: Spare. + +### 5.1.5 Order of Bit Transmission + +See 3GPP TS 48.060. + +## 5.2 8 kbit/s submultiplexing + +### 5.2.1 Frames for Speech Services + +#### 5.2.1.1 Frame for Half Rate Speech + +| Octet no | Bit number | | | | | | | | +|----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | XC1 | XC2 | +| 3 | 0 | 1 | XC3 | XC4 | XC5 | XC6 | D1 | D2 | +| 4 | 1 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | +| 5 | 1 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | +| 6 | 1 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | +| 7 | 1 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | +| 8 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | D37 | +| 9 | 1 | D38 | D39 | D40 | D41 | D42 | D43 | D44 | +| 10 | 1 | CRC2 | CRC1 | CRC0 | D45 | D46 | D47 | D48 | +| 11 | 1 | D49 | D50 | D51 | D52 | D53 | D54 | D55 | +| 12 | 1 | D56 | D57 | D58 | D59 | D60 | D61 | D62 | +| 13 | 1 | D63 | D64 | D65 | D66 | D67 | D68 | D69 | +| 14 | 1 | D70 | D71 | D72 | D73 | D74 | D75 | D76 | +| 15 | 1 | D77 | D78 | D79 | D80 | D81 | D82 | D83 | +| 16 | 1 | D84 | D85 | D86 | D87 | D88 | D89 | D90 | +| 17 | 1 | D91 | D92 | D93 | D94 | D95 | D96 | D97 | +| 18 | 1 | D98 | D99 | D100 | D101 | D102 | D103 | D104 | +| 19 | 1 | D105 | D106 | D107 | D108 | D109 | D110 | D111 | +| 20 | 1 | D112 | C6 | C7 | C8 | C9 | T1 | T2 | + +#### 5.2.1.2 Frames for Adaptive Multi-Rate Speech + +##### 5.2.1.2.1 Frame for Lower Codec Modes + +This frame layout shall be used for No\_Speech frames and speech frames for codec modes 4,75, 5,15 and 5,90 kBit/s. + +| Octet no | Bit number | | | | | | | | +|----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | +| 3 | 1 | C1 | C2 | C3 | C4 | C5 | D8 | D9 | +| 4 | 0 | 1 | D10 | D11 | D12 | D13 | D14 | D15 | +| 5 | 1 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | +| 6 | 1 | | | | | | | D29 | +| 7 | 1 | | | | | | | D36 | +| 8 | 1 | | | | | | | D43 | +| 9 | 1 | | | | | | | D50 | +| 10 | 1 | | | | | | | D57 | +| 11 | 1 | | | | | | | D64 | +| 12 | 1 | | | | | | | D71 | +| 13 | 1 | | | | | | | D78 | +| 14 | 1 | | | | | | | D85 | +| 15 | 1 | | | | | | | D92 | +| 16 | 1 | | | | | | | D99 | +| 17 | 1 | | | | | | | D106 | +| 18 | 1 | | | | | | | D113 | +| 19 | 1 | | | | | | | D120 | +| 20 | 1 | D121 | D122 | D123 | D124 | D125 | D126 | T | + +##### 5.2.1.2.2 Speech frame for Codec Mode 6,70 kBit/s + +This frame layout shall be used for speech frames for codec mode 6,70 kBit/s. The synchronisation pattern is unique and identifies this codec mode. + +| Octet no | Bit number | | | | | | | | +|----------|------------|------|-----|-----|-----|-----|-----|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | D1 | D2 | D3 | D4 | D5 | D5 | D7 | +| 3 | 1 | C1 | C2 | C3 | D8 | D9 | D10 | D11 | +| 4 | 1 | D12 | D13 | D14 | D15 | D16 | D17 | D18 | +| 5 | 1 | D19 | D | D | D | D | D | D25 | +| 6 | 0 | D26 | D | D | D | D | D | D32 | +| 7 | 1 | D33 | D | D | D | D | D | D39 | +| 8 | D40 | D | D | D | D | D | D | D47 | +| 9 | 1 | D48 | D | D | D | D | D | D54 | +| 10 | D55 | D | D | D | D | D | D | D62 | +| 11 | 1 | D63 | D | D | D | D | D | D69 | +| 12 | D70 | D | D | D | D | D | D | D77 | +| 13 | 1 | D78 | D | D | D | D | D | D84 | +| 14 | D85 | D | D | D | D | D | D | D92 | +| 15 | 1 | D93 | D | D | D | D | D | D99 | +| 16 | D100 | D | D | D | D | D | D | D107 | +| 17 | 1 | D108 | D | D | D | D | D | D114 | +| 18 | D115 | D | D | D | D | D | D | D122 | +| 19 | 1 | D | D | D | D | D | D | D129 | +| 20 | D130 | D | D | D | D | D | D | D137 | + +##### 5.2.1.2.3 Speech frame for Codec Mode 7,40 kBit/s + +This frame layout shall be used for speech frames for codec mode 7,40 kBit/s. The synchronisation pattern is unique and identifies this codec mode. + +| Octet no | Octet no | Bit number | | | | | | | | +|----------|----------|------------|------|------|------|------|------|------|------| +| | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 1 | 0 | 0 | 1 | D1 | D2 | D3 | D4 | D5 | +| 2 | 2 | 0 | D6 | D7 | D8 | D9 | D10 | D11 | D12 | +| 3 | 3 | 1 | C1 | C2 | C3 | D13 | D14 | D15 | D16 | +| 4 | 4 | 0 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | +| 5 | 5 | D24 | D | D | D | D | D | D | D31 | +| 6 | 6 | D32 | D | D | D | D | D | D | D39 | +| 7 | 7 | D40 | D | D | D | D | D | D | D47 | +| 8 | 8 | D48 | D | D | D | D | D | D | D55 | +| 9 | 9 | D56 | D | D | D | D | D | D | D63 | +| 10 | 10 | D64 | D | D | D | D | D | D | D71 | +| 11 | 11 | D72 | D | D | D | D | D | D | D79 | +| 12 | 12 | D80 | D | D | D | D | D | D | D87 | +| 13 | 13 | D88 | D | D | D | D | D | D | D95 | +| 14 | 14 | D96 | D | D | D | D | D | D | D103 | +| 15 | 15 | D104 | D | D | D | D | D | D | D111 | +| 16 | 16 | D112 | D | D | D | D | D | D | D119 | +| 17 | 17 | D120 | D | D | D | D | D | D | D127 | +| 18 | 18 | D128 | D | D | D | D | D | D | D135 | +| 19 | 19 | D136 | D | D | D | D | D | D | D143 | +| 20 | 20 | D144 | D145 | D146 | D147 | D148 | D149 | D150 | D151 | + +##### 5.2.1.2.4 Speech frame for Codec Mode 7,95 kBit/s + +AMR Codec Mode 7,95 kBit/s is not supported in 8 kBit/s submultiplexing. + +#### 5.2.1.3 Frames for Speech Codec Configuration Exchange + +| Octet no | Bit number | | | | | | | | +|----------|------------|------|------|------|------|------|----|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | D1 | D2 | +| 3 | 0 | 1 | D3 | D4 | D5 | D6 | D7 | D8 | +| 4 | 1 | | | | | | | D15 | +| 5 | 1 | | | | | | | D22 | +| 6 | 1 | | | | | | | D29 | +| 7 | 1 | | | | | | | D36 | +| 8 | 1 | | | | | | | D43 | +| 9 | 1 | | | | | | | D50 | +| 10 | 1 | | | | | | | D57 | +| 11 | 1 | | | | | | | D64 | +| 12 | 1 | | | | | | | D71 | +| 13 | 1 | | | | | | | D78 | +| 14 | 1 | | | | | | | D85 | +| 15 | 1 | | | | | | | D92 | +| 16 | 1 | | | | | | | D99 | +| 17 | 1 | | | | | | | D106 | +| 18 | 1 | | | | | | | D113 | +| 19 | 1 | | | | | | | D120 | +| 20 | 1 | D121 | D122 | D123 | D124 | D125 | T1 | T2 | + +### 5.2.2 Data frame + +| Octet no. | Bit number | | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------|------------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | D1 | D2 | | +| 3 | 0 | 1 | D3 | D4 | D5 | D6 | D7 | D8 | | +| 4 | 1 | D9 | D10 | D11 | D12 | D13 | D14 | D15 | | +| 5 | 1 | D16 | D17 | D18 | D19 | D20 | D21 | D22 | Data frame | +| 6 | 1 | D23 | D24 | D25 | D26 | D27 | D28 | D29 | position 1 | +| 7 | 1 | D30 | D31 | D32 | D33 | D34 | D35 | D36 | | +| 8 | 1 | D37 | D38 | D39 | D40 | D41 | D42 | D43 | | +| 9 | 1 | D44 | D45 | D46 | D47 | D48 | D49 | D50 | | +| 10 | 1 | D51 | D52 | D53 | D54 | D55 | D56 | D57 | | +| 11 | 1 | D58 | D59 | D60 | D61 | D62 | D63 | D'1 | | +| 12 | 1 | D'2 | D'3 | D'4 | D'5 | D'6 | D'7 | D'8 | | +| 13 | 1 | D'9 | D'10 | D'11 | D'12 | D'13 | D'14 | D'15 | | +| 14 | 1 | D'16 | D'17 | D'18 | D'19 | D'20 | D'21 | D'22 | | +| 15 | 1 | D'23 | D'24 | D'25 | D'26 | D'27 | D'28 | D'29 | Data frame | +| 16 | 1 | D'30 | D'31 | D'32 | D'33 | D'34 | D'35 | D'36 | position 2 | +| 17 | 1 | D'37 | D'38 | D'39 | D'40 | D'41 | D'42 | D'43 | | +| 18 | 1 | D'44 | D'45 | D'46 | D'47 | D'48 | D'49 | D'50 | | +| 19 | 1 | D'51 | D'52 | D'53 | D'54 | D'55 | D'56 | D'57 | | +| 20 | 1 | D'58 | D'59 | D'60 | D'61 | D'62 | D'63 | 1 | | + +### 5.2.3 O&M frame + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|------|------|------|------|------|------|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 1 | C1 | C2 | C3 | C4 | C5 | XC1 | XC2 | +| 3 | 0 | 1 | XC3 | XC4 | XC5 | XC6 | D1 | D2 | +| 4 | 1 | D3 | D4 | D5 | D6 | D7 | D8 | D9 | +| 5 | 1 | D10 | D11 | D12 | D13 | D14 | D15 | D16 | +| 6 | 1 | D17 | D18 | D19 | D20 | D21 | D22 | D23 | +| 7 | 1 | D24 | D25 | D26 | D27 | D28 | D29 | D30 | +| 8 | 1 | D31 | D32 | D33 | D34 | D35 | D36 | D37 | +| 9 | 1 | D38 | D39 | D40 | D41 | D42 | D43 | D44 | +| 10 | 1 | D45 | D46 | D47 | D48 | D49 | D50 | D51 | +| 11 | 1 | D52 | D53 | D54 | D55 | D56 | D57 | D58 | +| 12 | 1 | D59 | D60 | D61 | D62 | D63 | D64 | D65 | +| 13 | 1 | D66 | D67 | D68 | D69 | D70 | D71 | D72 | +| 14 | 1 | D73 | D74 | D75 | D76 | D77 | D78 | D79 | +| 15 | 1 | D80 | D81 | D82 | D83 | D84 | D85 | D86 | +| 16 | 1 | D87 | D88 | D89 | D90 | D91 | D92 | D93 | +| 17 | 1 | D94 | D95 | D96 | D97 | D98 | D99 | D100 | +| 18 | 1 | D101 | D102 | D103 | D104 | D105 | D106 | D107 | +| 19 | 1 | D108 | D109 | D110 | D111 | D112 | D113 | D114 | +| 20 | 1 | D115 | D116 | D117 | D118 | D119 | D120 | 1 | + +### 5.2.4 Coding + +#### 5.2.4.1 Coding for Half Rate Speech and Half Rate Data Services + +In the following clauses, the coding of the frames is described for all services, except for Adaptive Multi-Rate Speech (AMR). Any spare or not used transmitted control bits should be coded binary "1". + +##### 5.2.4.1.1 Uplink coding + +###### Control bits (C-bits, for all frame types) + +The control bits are coded according to the following table: + +| C1 | C2 | C3 | C4 | C5 | Meaning | +|----|----|----|----|----|---------------------| +| 0 | 0 | 0 | 1 | OP | Speech frame | +| 0 | 0 | 1 | 1 | OP | Data frame | +| 0 | 1 | 0 | 1 | OP | O&M frame | +| 1 | 1 | 1 | 1 | OP | Configuration frame | + +All other codings are reserved. + +OP: odd parity of bits C1 to C4. + +In the following, the term "frame type" refers to the control bits C1 to C3. + +| C6 | C7 | C8 | C9 | Meaning | +|-----|-----|-----|------|-----------------------| +| TA2 | TA1 | TA0 | DTXd | For speech frame only | + +DTXd: DTX downlink indicator. + +0: Downlink DTX shall not be applied. + +1: Downlink DTX shall be applied. + +TA2-TA0: Time Alignment Command, see clause 6.6.1.2.1. + +###### Extended control bits + +The extended control bits are coded according to the following table: + +Frames for Half Rate Speech + +| XC1 | XC2 | XC3 | XC4 | XC5 | XC6 | Meaning | +|-----|-----|-----|-----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 0 | 0 | 0 | 0 | OP | Good speech frame with UFI = 0 (BFI=0, SID=0, TAF=1)
(BFI=0, SID=0, TAF=0) | +| 0 | 0 | 0 | 0 | 1 | OP | Unreliable speech frame (if speech decoder is in speech decoding mode) or unusable frame (if speech decoder is in comfort noise insertion mode) with UFI = 1
(BFI=0, SID=0, TAF=1)
(BFI=0, SID=0, TAF=0) | +| 0 | 0 | 0 | 1 | 0 | OP | Valid SID frame with UFI = 0 (BFI=0, SID=2, TAF=1)
(BFI=0, SID=2, TAF=0) | +| 0 | 0 | 0 | 1 | 1 | OP | Invalid SID frame with UFI = 1 (BFI=0, SID=2, TAF=1)
(BFI=0, SID=2, TAF=0) | +| 0 | 1 | 0 | 0 | 0 | OP | Invalid SID frame at TAF=0 with UFI = 0
(BFI=0, SID=1, TAF=0)
(BFI=1, SID=1, TAF=0)
(BFI=1, SID=2, TAF=0) | +| 0 | 1 | 0 | 0 | 1 | OP | Invalid SID frame at TAF=0 with UFI = 1
(BFI=0, SID=1, TAF=0)
(BFI=1, SID=1, TAF=0)
(BFI=1, SID=2, TAF=0) | +| 0 | 1 | 0 | 1 | 0 | OP | Invalid SID frame at TAF=1 with UFI = 0
(BFI=0, SID=1, TAF=1)
(BFI=1, SID=1, TAF=1)
(BFI=1, SID=2, TAF=1) | +| 0 | 1 | 0 | 1 | 1 | OP | Invalid SID frame at TAF=1 with UFI = 1
(BFI=0, SID=1, TAF=1)
(BFI=1, SID=1, TAF=1)
(BFI=1, SID=2, TAF=1) | +| 0 | 1 | 1 | 0 | 0 | OP | Bad speech frame or unusable frame at TAF = 0 with UFI = 0
(BFI=1, SID=0, TAF=0) | +| 0 | 1 | 1 | 0 | 1 | OP | Bad speech frame or unusable frame at TAF = 0 with UFI = 1
(BFI=1, SID=0, TAF=0) | +| 0 | 1 | 1 | 1 | 0 | OP | Bad speech frame or unusable frame at TAF = 1 with UFI = 0
(BFI=1, SID=0, TAF=1) | +| 0 | 1 | 1 | 1 | 1 | OP | Bad speech frame or unusable frame at TAF = 1 with UFI = 1
(BFI=1, SID=0, TAF=1) | + +O&M frame + +| XC1 | XC2 | XC3 | XC4 | XC5 | XC6 | Meaning | +|-----|-----|-----|-----|-----|-----|-----------| +| 1 | 1 | 1 | 1 | 1 | OP | O&M frame | + +All other codings are reserved. + +OP: odd parity of bits XC1 to XC5. + +BFI, SID, TAF: see description in clause 5.1.4.1. + +UFI bit: Unreliable Frame Indication (see 3GPP TS 46.041). + +###### Cyclic Redundancy Check bits (CRC-bits) + +Half Rate Speech frame: Bits CRC0 .. CRC2: CRC of the bits D1 to D44. Same coding as in clause 5.1.4.1. + +###### Data bits (D-bits) + +Speech frame: Bits D1 .. D112: + +For good speech frame: speech block transferred in the same order as output from the transcoder (see 3GPP TS 46.020). + +For valid SID frame: SID data block transferred in the same order as output from the transcoder (see 3GPP TS 46.022). + +Data frame: Bits D1 .. D63 for data frame position 1 and bits D'1 .. D'63 for data frame position 2 (see clause 6.7.1). + +O&M frame: Bits D1 .. D120: Bits used for transfer of O&M information. The coding and use of these bits are left to the manufacturer of the BSC/TRAU. + +Configuration frame: Bits D1...D125: Bits are reserved for Configuration Exchange to support Tandem Free Operation. They are defined in TS 28.062. + +###### Time Alignment bits (T-bits) + +Bits T1..T2: Bits positioned at the end of the uplink TRAU speech frame. + +T1 is set to binary "1". + +If the timing of the frame is to be advanced 125 µs , the bit T2 is not transferred in order to reduce the frame length accordingly. When transferred, the bit T2 is set to binary "1". + +##### 5.2.4.1.2 Downlink coding + +###### Control bits + +| C1 | C2 | C3 | C4 | C5 | Meaning | +|----|----|----|-----|----|---------------------| +| 0 | 0 | 0 | UFE | OP | Speech frame | +| 0 | 0 | 1 | UFE | OP | Data frame | +| 0 | 1 | 0 | UFE | OP | O&M frame | +| 1 | 1 | 1 | UFE | OP | Configuration frame | + +All other codings are reserved. + +UFE: Uplink Frame Error. + UFE = 0: bad uplink framing. + UFE = 1: good uplink framing. + See clause 6.8.2.2. + +OP: Odd parity of bits C1 to C4. + +In the following, the term "frame type" refers to the control bits C1 to C3. + +| C6 | C7 | C8 | C9 | Meaning | +|----|----|----|----|------------| +| 1 | 1 | 1 | 1 | Spare bits | + +###### Extended control bits + +The extended control bits are coded according to the following table: + +Frames for Half Rate speech + +| XC1 | XC2 | XC3 | XC4 | XC5 | XC6 | Meaning | +|-----|-----|-----|-----|-----|-----|----------------------------| +| 0 | 0 | 0 | 0 | 0 | OP | Good speech frame (SP = 1) | +| 0 | 0 | 0 | 1 | 0 | OP | Valid SID frame (SP = 0) | + +SP: Speech indicator (see 3GPP TS 46.041). + +O&M frame + +| XC1 | XC2 | XC3 | XC4 | XC5 | XC6 | Meaning | +|-----|-----|-----|-----|-----|-----|---------| +| 1 | 1 | 1 | 1 | 1 | OP | O&M | + +All other codings are reserved. + +XC6: odd parity of bits XC1 to XC5. + +###### Data bits (D-bits) + +Same as the uplink. + +###### Time Alignment bits (T-bits) + +Bits T1..T2: Bits positioned at the end of the downlink TRAU speech frame. + +If the timing of the frame is to be advanced 250 µs, the bits T1 and T2 are not transferred in order to reduce the frame length accordingly. When transferred, the bits are set to binary "1" (see clause 6.6.1.2.1). + +###### Cyclic Redundancy Check bits (CRC-bits): + +Same as the uplink. + +#### 5.2.4.2 Coding for Adaptive Multi-Rate Speech + +Coding in uplink and downlink direction is identical. The synchronisation patterns for the Adaptive Multi Rate speech differ from the ones used for the other services. An explicit Frame\_Type is not defined for AMR, instead the synchronisation patterns itself identify the service (Frame\_Type) and to some extent the Codec\_Mode. + +The CRC-bits inserted are calculated as described in clause 5.1.4.1. The control elements are as defined in 3GPP TS 48.060 (RIF, CMI, CMR, TAC, TAE, PAB, ...). The coding is, however, sometimes different. + +##### 5.2.4.2.1 No\_Speech Frame + +The frame layout for lower modes shall be used. + +###### Control Information (C-Bits): + +C1 . C2. C3: set to "1.0.0", if RIF equals "0" (frame with Codec\_Mode Indication phase) + +set to "1.0.1", if RIF equals "1" (frame with Codec\_Mode Request phase) + +C4 . C5: set to "0.0", this is the Frame\_Classification for No\_Speech Frames. + +###### Coding of D-Bits: + +The D-Bits in No\_Speech frames carry additional control information: + +| | | | +|-------------|---------------------------------------------------------------------|--------------------------------| +| D1 .. D6: | Time Alignment Field | (as defined in 3GPP TS 48.060) | +| D7: | In DL: Uplink Frame Error (UFE) , in UL: Downlink Frame Error (DFE) | | +| D8 .. D10: | No_Speech_Classification | (as defined in 3GPP TS 48.060) | +| D11 .. D13: | CMI_abs | (as defined in 3GPP TS 48.060) | +| D14 .. D16: | CMR_abs | (as defined in 3GPP TS 48.060) | + +The Uplink Frame Error (UFE) is coded and defined as in 3GPP TS 48.060. + +The Downlink Frame Error (DFE) is - different to 48.060 - defined in uplink direction to allow fast recovery from synchronisation loss in higher codec modes. The coding is like for UFE. + +The procedure is described in clause 6.9.2. + +The coding for D55...D59 is common to all three lower code modes. These bits are reserved for the Configuration Protocol (Config\_Prof and Message\_No) in case of Tandem Free Operation, see 3GPP TS 48.062. If the BTS does not support TFO or TFO is disabled, then these bits shall be set to "0.0.0.0.0". + +| | | +|-------------|-------------| +| D55 .. D57: | Config_Prof | +| D58 .. D59: | Message_No | + +###### Time Alignment Extension and Phase Alignment: + +| | | | +|-------------|--------------------------------|--------------------------------| +| D60: | Phase Alignment Bit (PAB) | (as defined in 3GPP TS 48.060) | +| D61 .. D62: | Time Alignment Extension (TAE) | (as defined in 3GPP TS 48.060) | + +###### DTX and TFO control: + +| | | | +|------|----------------------------------|--------------------------------| +| D63: | DTX in downlink requested (DTXd) | (as defined in 3GPP TS 48.060) | +| D64: | TFO Enabled (TFOE) | (as defined in 3GPP TS 48.060) | + +The bits D65...D125 (61 bits) are reserved for Tandem Free Operation (see 3GPP TS 48.062). If the BTS does not support TFO or TFO is disabled, then these bits shall be set to all "1". + +The bits D17...D54 (38 bits) are also reserved for Tandem Free Operation (see 3GPP TS 48.062), if not needed otherwise, i.e. in all No\_Speech frames classified neither as SID\_Update nor as SID\_Bad. If the BTS does not support TFO or TFO is disabled, then these bits shall be set to all "1" in these cases. + +In case the frames are classified as SID\_Update or SID\_Bad the bits D17...D54 code the Silence Description parameters (as defined in 3GPP TS 26.090): + +###### Silence Description parameters (as defined in 3GPP TS 26.090): + +| | | +|-------------|----------------------------------------------------| +| D17 .. D19: | Moving average predictor, initial values (s1...s3) | +| D20 .. D45: | Indexes of LSF submatrices (s4...s29) | +| D46 .. D51: | Logarithmic frame energy (s30...s35) | +| D52 .. D54: | CRC1 over bits C1...C5, D1...D51. | + +###### Time Alignment Bits: + +| | | +|------------|----------------------------------------------------| +| D126 .. T: | Coding as defined for Half Rate speech (T1 .. T2). | +|------------|----------------------------------------------------| + +##### 5.2.4.2.2 Speech Frames for 4,75, 5,15 and 5,90 kBit/s + +The frame layout for lower modes shall be used. Speech Frames for 4,75, 5,15 and 5,90 kBit/s are defined, if Frame Classification is not set to "0.0" , otherwise the frame is a No\_Speech Frame (see above). + +###### Coding of Control Information (C-Bits): + +The coding for C1 to C5 is common in all three Codec\_Modes. Codec Mode Indication (CMI) plus Codec Mode Request (CMR) plus Request or Indication Flag (RIF) are coded with one 3-bit field. These three control elements are as defined in 3GPP TS 48.060. The coding is somewhat different: + +###### C1.C2.C3: + +| | | | | +|------------|-------------|-------------|----------| +| 0 . 0 . 0: | CMI = 4,75; | CMR = ?; | RIF = 0. | +| 0 . 0 . 1: | CMI = 5,15; | CMR = ?; | RIF = 0. | +| 0 . 1 . 0: | CMI = 5,90; | CMR = ?; | RIF = 0. | +| 0 . 1 . 1: | CMI = ?; | CMR = 4,75; | RIF = 1. | +| 1 . 0 . 0: | CMI = ?; | CMR = 5,15; | RIF = 1. | +| 1 . 0 . 1: | CMI = ?; | CMR = 5,90; | RIF = 1. | +| 1 . 1 . 0: | CMI = ?; | CMR = 6,70; | RIF = 1. | +| 1 . 1 . 1: | CMI = ?; | CMR = 7,40; | RIF = 1. | + +Frame\_Classification (C4...C5) is defined and coded as in 3GPP TS 48.060. + +###### Coding of D-Bits: + +The coding for D55...D59 is common to all three lower code modes. These bits are reserved for the Configuration Protocol (Config\_Prot and Message\_No) in case of Tandem Free Operation, see 3GPP TS 48.062. If the BTS does not support TFO or TFO is disabled, then these bits shall be set to "0.0.0.0.0". + +###### AMR\_Mode 4,75 kBit/s, see 3GPP TS 26.090: + +D1 .. D3: spare (3 bits), set to "1" + D4 .. D26: Indexes of the LSF submatrices (s1...s23) + D27 .. D51: Indexes of the parameters of first sub-frame (s24...s48) + D52 .. D54: CRC1 over bits C1...C5, s1...s16, s18, s19, s21...s29, s45...s48. + D55 .. D59: reserved for TFO + D60 .. D72: Indexes of the parameters of second sub-frame (s49...s61) + D73 .. D75: CRC2 over bits D55...D59, s49, s50. + D76 .. D96: Indexes of the parameters of third sub-frame (s62...s82) + D97 .. D99: CRC3 over bits s62, s63, s79...s82. + D100 .. D112: Indexes of the parameters of fourth sub-frame (s83...s95) + D113 .. D115: CRC4 over bits s83, s84. + D116 .. D126: spare (11 bits); set to "1". + +###### AMR\_Mode 5,15 kBit/s, see 3GPP TS 26.090: + +D1 .. D5: spare (5 bits); set to "1" + D6..D28: Indexes of the LSF submatrices (s1...s23) + D29..D51: Indexes of the parameters of first sub-frame (s24...s46) + D52 .. D54: CRC1 over bits C1...C5, s1...s16, s19...s29, s42...s46. + D55 .. D59: reserved for TFO + D60 .. D78: Indexes of the parameters of second sub-frame (s47...s65) + D79 .. D81: CRC2 over bits D55...D59, s47, s48, s61...s65. + D82 .. D100: Indexes of the parameters of third sub-frame (s66...s84) + D101 .. D103: CRC3 over bits s66, s67, s80...s84. + D104 .. D122: Indexes of the parameters of fourth sub-frame (s85...s103) + D123 .. D125: CRC4 over bits s85, s86, s99...s103. + D126: spare (1 bits); set to "1". + +###### AMR\_Mode 5,90 kBit/s, see 3GPP TS 26.090: + +D1 .. D26: Indexes of the LSF submatrices (s1...s26) + D27 .. D51: Indexes of the parameters of first sub-frame (s27...s51) + D52 .. D54: CRC1 over bits C1...C5, s1...s17, s27...s34, s48...s51. + D55 .. D59: reserved for TFO + D60 .. D80: Indexes of the parameters of second sub-frame (s52...s72) + D81 .. D105: Indexes of the parameters of third sub-frame (s73...s97) + D106 .. D126: Indexes of the parameters of fourth sub-frame (s98...s118). + +###### Time Alignment Bit: + +T: Set to "1". May be omitted, then the next frame is advanced by 125 µs. + +##### 5.2.4.2.3 Speech Frame for 6,70 kBit/s + +The frame layout for codec mode 6,70 shall be used. By this the Codec Mode Indication is defined to be 6,70 kBit/s, regardless of the phase of the RIF bit. + +###### Coding of Control Information (C-Bits): + +Codec Mode Request (CMR) plus Request or Indication Flag (RIF) plus Frame Classification (FC) are coded with one 3-bit field. These three control elements, are as defined in 3GPP TS 48.060. The coding is somewhat different: + +C1.C2.C3: + +0 . 0 . 0: CMR = ?; RIF = 0; FC = "Speech\_Bad". + 0 . 0 . 1: CMR = ?; RIF = 0; FC = "Speech\_Good". + 0 . 1 . 0: CMR = (D1...D3); RIF = 1 FC = "Speech\_Bad". + 0 . 1 . 1: CMR = 4,75; RIF = 1; FC = "Speech\_Good". + +1 . 0 . 0: CMR = 5,15; RIF = 1; FC = "Speech\_Good". + 1 . 0 . 1: CMR = 5,90; RIF = 1; FC = "Speech\_Good". + 1 . 1 . 0: CMR = 6,70; RIF = 1; FC = "Speech\_Good". + 1 . 1 . 1: CMR = 7,40; RIF = 1; FC = "Speech\_Good". + +"CMR = (D1...D3)" indicates that the CMR is defined in this specific case of "Speech\_Bad" within the D-Bits, which would be otherwise undefined. The coding of CMR in this case is: + +D1.D2.D3: + +0 . 0 . 0: undefined, reserved + 0 . 0 . 1: undefined, reserved + 0 . 1 . 0: undefined, reserved + 0 . 1 . 1: CMR = 4,75. + 1 . 0 . 0: CMR = 5,15. + 1 . 0 . 1: CMR = 5,90. + 1 . 1 . 0: CMR = 6,70. + 1 . 1 . 1: CMR = 7,40. + +###### Coding of D-Bits, see 3GPP TS 26.090: + +D1 .. D26: Indexes of the LSF submatrices (s1...s26) + D27 .. D55: Indexes of the parameters of first sub-frame (s27...s55) + D56 .. D58: CRC1 over bits C1...C3, D1...D3, s4...s17, s20, s24, s27...s34, s49...s53. + D59 .. D83: Indexes of the parameters of second sub-frame (s56...s80) + D84 .. D112: Indexes of the parameters of third sub-frame (s81...s109) + D113 .. D137: Indexes of the parameters of fourth sub-frame (s110...s134). + +##### 5.2.4.2.4 Speech Frame for 7,40 kBit/s + +The frame layout for codec mode 7,40 shall be used. By this the Codec Mode Indication is defined to be 7,40 kBit/s, regardless of the phase of the RIF bit. + +###### Coding of Control Information (C-Bits): + +Codec Mode Request (CMR) plus Request or Indication Flag (RIF) plus Frame Classification (FC) are coded with one 3-bit field. These three control elements are as defined in 3GPP TS 48.060. + +The coding is exactly as described for codec mode 6,70, except that the CMR in case of "Speech\_Bad" is defined in bits D6...D8 (instead of D1...D3) and thus at exactly the same position within the frame. + +###### Coding of D-Bits, see 3GPP TS 26.090: + +D1 .. D26: Indexes of the LSF submatrices (s1...s26) + D27 .. D58: Indexes of the parameters of first sub-frame (s27... s58) + D59 .. D61: CRC1 over bits C1 to C3, D1... D20, s22...s24, s27...s32, s52, s53, s55...s57. + D62 .. D90: Indexes of the parameters of second sub-frame (s59...s87) + D91 .. D122: Indexes of the parameters of third sub-frame (s88...s119) + D123 .. D151: Indexes of the parameters of fourth sub-frame (s120...s148). + +##### 5.2.4.2.5 Speech Frame for 7,95 kBit/s + +Codec mode 7,95 kBit/s is not supported in 8 kBit/s submultiplexing. + +### 5.2.5 Order of Bit Transmission + +The order of bit transmission is: + +Bit m of octet n shall be transmitted as bit ((n-1)\*8+m) with m=(1..8) and n=(1..20). + +# --- 6 Procedures + +For AMR speech on 8 kBit/s submultiplexing the procedures are very much identical to the ones described in 3GPP TS 48.060 for AMR speech on 16 kBit/s submultiplexing. In the present recommendation (48.061) therefore only the procedures are defined that differ from that. + +## 6.1 Remote Control of Transcoders and Rate Adaptors + +When the TRAU is positioned remote from the BTS, the CCU in the BTS has to control some of the functions in the remote TRAU. + +This remote control is performed by in-band signalling carried by the control bits in each TRAU frame. + +The following functions in the TRAU are remotely controlled by the CCU: + +- change between speech and data; +- downlink frame timing for speech frames; +- transfer of DTX information. + +In addition the following is transferred in case of AMR speech: + +- control of Codec Mode Adaptation; +- transfer of TFO Configuration Parameters (optional, see 3GPP TS 48.062); +- downlink Phase Alignment (optional, see 3GPP TS 48.060); +- transfer of Information on TFO and Handover Status (optional, see 3GPP TS 48.060 and 48.062). + +In addition, the in-band signalling also provides means for transfer of O&M signals between the TRAU and the BSC/BTS. + +## 6.2 Resource Allocation + +In case of AMR speech see 3GPP TS 48.060. + +At reception of the 3GPP TS 48.008 ASSIGNMENT REQUEST message, e.g. at call setup, when a circuit switched connection is required, the BSC provides an appropriate TRAU to the circuit to be used between the BSC and the BTS and sends the 3GPP TS 48.058 CHANNEL ACTIVATION message to the BTS. + +When receiving the CHANNEL ACTIVATION message, the BTS allocates the appropriate radio resources and a CCU to be used. + +The CCU now starts sending uplink TRAU frames with the appropriate frame type. + +When receiving the first frame, the TRAU sets the mode of operation as indicated by the CCU and starts sending downlink TRAU frames with the corresponding frame type. + +## 6.3 Resource Release + +In case of AMR speech see 3GPP TS 48.060. + +At release of circuit switched resources, e.g. at call release, the connection between the CCU and the TRAU will be released by the BSC. The BSC has to indicate that the connection has been released. How this is performed is a BSC internal matter. Two methods may be used for either submultiplexing scheme. + +- i) The BSC indicates the call release to the TRAU by inserting the PCM idle bit pattern described in 3GPP TS 48.054 on the circuits towards the TRAU. The TRAU shall be able to detect this idle bit pattern. When received at the TRAU, the TRAU will lose frame synchronization and will start timer $T_{\text{release}} = 1$ second. If, when $T_{\text{release}}$ expires, the idle bit pattern is detected, the TRAU shall terminate the operation (go idle) until a valid frame is again received. $T_{\text{release}}$ is reset every time the frame synchronization is again obtained. +- ii) It is handled by BSC internal signals (e.g. if the BSC and TRAU are collocated). + +## 6.4 In Call Modification + +In case of AMR speech see 3GPP TS 48.060. + +At reception of the 3GPP TS 48.058 MODE MODIFY message from the BSC indicating a change between speech and data, the BTS orders the corresponding CCU to modify its mode of operation. The CCU sets the frame type in the uplink TRAU frames to the new mode of operation. + +When the TRAU receives an uplink TRAU frame with the frame type, different from the current mode but without errors detected (see clause 6.9.1.2), the current mode is kept and speech/data bits are handled as erroneous. When receiving the next TRAU frame with the same frame type, the TRAU changes the mode of operation accordingly and sets the new frame type in the downlink frames. + +## 6.5 Transfer of Idle Frames, Handling of missing data + +In case of AMR speech see 3GPP TS 48.060. + +If no speech is received from the MS (uplink direction) in case of Half Rate speech, the CCU shall send TRAU speech frames with BFI flag set to 1 (bad frame). If no data is received from the MS (uplink direction), the CCU shall send idle TRAU data frames. + +For Half Rate speech calls, the CCU shall transmit a speech frame with the three parity bits inverted (protection of the most significant 22 class 1 bits, see 3GPP TS 45.003) on the air interface: + +- if frame synchronization has been lost in the downlink direction; +- if a CRC error is detected (bits CRC0-CRC2) in a downlink TRAU speech frame; +- if an O&M TRAU frame is received (see clause 6.10). + +For data calls, the CCU shall react towards the air interface as if an idle TRAU data frame has been received: + +- when frame synchronization has been lost in the downlink direction; +- when an O&M TRAU frame is received (see clause 6.10). + +An idle TRAU data frame is a TRAU data frame with all data bits set to binary "1". + +## 6.6 Procedures for Speech Frames + +### 6.6.1 Time Alignment of Speech Frames + +The time alignment needed for obtaining minimum buffer delay will differ from call to call. The reasons for this are: + +- the BSC will have no information about the radio timing at the BTS, and will start sending TRAU frames at an arbitrary or default time. In the case of 16 kbit/s submultiplexing, each TRAU frame is 320 bits (20 ms) and will in the worst case be received at the BTS 318 bits out of phase. In the case of 8 kbit/s submultiplexing, each TRAU frame is 160 bits (20 ms) and will in the worst case be received at the BTS 159 bits out of phase; +- the different timeslots and half rate subchannels on one carrier are sent at different times (max. 8.66 ms which equals 15 radio time slots); +- different channels may be transferred on different transmission systems using different routes in the network. The transmission delay may therefore differ. + +The required time alignment procedure between radio frames and TRAU frames is specified in clauses 6.6.1.1 and 6.6.1.2 for the 16 kbit/s submultiplexing and the 8 kbit/s submultiplexing respectively. + +In order to achieve optimum timing between the radio TDMA frames and the frames on the transmission side, the speech coding and decoding function in the transcoder should not be synchronized. + +#### 6.6.1.1 16 kbit/s submultiplexing + +For AMR speech see 3GPP TS 48.060. + +##### 6.6.1.1.1 Downlink Time Alignment + +###### 6.6.1.1.1.1 Initial Time Alignment state + +The TRAU shall enter the Initial Time Alignment state at the switching-on of the system, when it goes idle (e.g. when receiving the PCM idle pattern after a call release as described in clause 6.3), if loss of frame synchronization is detected, in call modification from data to speech is performed or if BSS internal handover is detected. + +In the initial state, the frames shall only be delayed or no change is applied (see note below). The transcoder is able to adjust the time for transmitting the speech frames in steps of 125 µs (one speech sample). The CCU calculates the required timing adjustment and returns a frame including the number of 250/500 µs steps by which the frames in the downlink direction have to be delayed (binary number in the "Time Alignment" field). + +When receiving this information, the TRAU processes this data and sets the "Time Alignment" field in the next downlink frame as ordered and then delays the subsequent frame accordingly. + +If the TRAU, in this state, receives an order to advance the next frame 250 µs, this order shall be interpreted as "Delay frame 39\*500 µs". + +When a frame is delayed due to timing adjustments, the TRAU shall fill in the gap between the frames with the appropriate number of binary "1". + +After having adjusted the timing, the TRAU shall receive at least three new frames before a new adjustment is made. This in order to avoid oscillation in the regulation. + +The TRAU shall change from the Initial Time Alignment state to the Static Time Alignment state when it has performed two subsequent timing adjustments which are less than 500 µs (including no change). + +The procedure is illustrated in figure 6.1. + +###### 6.6.1.1.1.2 Static Time Alignment state + +In the Static Time Alignment state, the TRAU performs timing adjustments in single steps of 250 µs. The timing may either be delayed (time alignment code 111110), advanced (time alignment code 111111) or not changed (time alignment code 000000). + +When receiving an order for adjusting the timing, the transcoder skips or repeats two speech samples in order to achieve the correct timing. + +If the timing is to be advanced 250 µs, the TRAU sets the "Time Alignment" field in the next downlink frame as ordered and then the 4 last bits of the frame are not transferred (the T-bits). + +If the timing is to be delayed, the TRAU sets the "Time Alignment" field in the next downlink frame as ordered and then delays the subsequent frame by adding four binary "1" between the frames. + +After having adjusted the timing, the TRAU shall receive at least three new frames before a new adjustment is made. + +If, in this state, the TRAU detects a change in the timing of the uplink frames greater than 1ms, it shall enter the Initial Time Alignment state and in that state it may perform an adjustment on the downlink equal to the change detected on the uplink. + +![Sequence diagram showing the initial time alignment procedure between MSC, BSC, and BTS. The diagram includes message exchanges (ASSREQ, CHAN ACTIV) and frame transmissions (Speech or idle frame, Idle or speech frame) with timing calculations for time alignment (X and Y TA) at the Channel Codec Unit.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +The diagram illustrates the initial time alignment procedure for 16 kbit/s submultiplexing. It involves three main entities: MSC, BSC, and BTS. + +- MSC** sends an **ASSREQ** message (L3 on the A-interface) to the **BSC**. +- The **BSC** performs an internal function: **Allocate and connect TRAU**. +- The **BSC** then sends a **CHAN ACTIV** message (L3 on the Abis interface) to the **BTS**. +- Inside the **BTS**, the function **Allocate Radio channel and CCU** is performed. +- The **BTS** contains two sub-units: **TRANSCODER/RA UNIT** and **CHANNEL CODEC UNIT**. +- Frame transmission begins from the **TRANSCODER/RA UNIT** to the **CHANNEL CODEC UNIT**. The first frame is labeled **Speech or idle frame (0 TA)**. +- Subsequent frames are labeled **Idle or speech frame**, **Speech or idle frame (X TA)**, **Idle or speech frame**, **Speech or idle frame (Y TA)**, and so on. +- The **CHANNEL CODEC UNIT** calculates time alignment for each frame: + - For the first frame, it calculates **Calculate Time Alignment (X x 250 uS)**. + - For subsequent frames, it calculates **Calculate Time Alignment (X x 250 uS)** or **Calculate Time Alignment (Y x 250 uS)**. +- Timing intervals of **20 ms** are indicated between frame transmissions. +- On the left side, a vertical arrow indicates an **Arbitrary or default time** starting point. +- At the bottom, two vertical arrows indicate calculated time alignment values: **20mS X x 250/500 uS** and **20mS Y x 250/500 uS**. + +Sequence diagram showing the initial time alignment procedure between MSC, BSC, and BTS. The diagram includes message exchanges (ASSREQ, CHAN ACTIV) and frame transmissions (Speech or idle frame, Idle or speech frame) with timing calculations for time alignment (X and Y TA) at the Channel Codec Unit. + +Figure 3GPP TS 48.061/6.1: Initial Time Alignment procedure, 16 kbit/s submultiplexing + +##### 6.6.1.1.2 Uplink Time Alignment + +In order to achieve optimum timing between the Air interface and the terrestrial link, the tail bits of the uplink speech frames may be used for uplink time alignment. + +To advance 125 µs, the CCU removes the last two tail bits of the uplink TRAU speech frame. + +To delay 125 µs, the CCU inserts two binary "1" between two uplink TRAU speech frames. + +##### 6.6.1.1.3 Initiation at Resource Allocation + +When the BTS receives the 3GPP TS 48.058 CHANNEL ACTIVATION message from the BSC, with Channel Mode IE indicating speech, it allocates the appropriate radio resources and a Channel Codec Unit (CCU). The CCU then initiates sending of speech frames (or applies the procedure specified in clause 6.5 if speech is not received from the MS) towards the transcoder with normal frame phase for the TDMA channel in question. The "Time Alignment" field in these frames is set to "no change". + +The TRAU will now be in the Initial Time Alignment state. When receiving the first frame it shall start sending speech frames towards the BTS with arbitrary or default phase related to the uplink frame phase. + +When receiving these frames the CCU calculates the timing adjustment required in order to achieve minimum buffer delay and sets the "Time Alignment" field in the uplink frames accordingly. + +The procedures described for the Initial and for the Static Time Alignment states are then followed during the call. + +##### 6.6.1.1.4 Time Alignment during Handover + +###### 6.6.1.1.4.1 BSS External Handover + +For BSS external handover, the procedure described in clause 6.6.1.1.3 should be used by the new BSC/BTS at resource allocation. + +###### 6.6.1.1.4.2 BSS Internal Handover + +If a BSS internal handover has been performed, the timing of the downlink frames may have to be adjusted several steps of 250/500 µs. In order to speed up the alignment of the downlink frames, this must be detected by the TRAU, e.g. by detecting the change in the uplink frame timing as described in clause 6.6.1.1.1.2. The TRAU should then enter the Initial Time Alignment state and in that state it may perform an adjustment on the downlink equal to the change detected on the uplink. + +#### 6.6.1.2 8 kbit/s submultiplexing + +For AMR speech on 8 kBit/s submultiplexing the same procedures as for AMR speech on 16 kBit/s submultiplexing shall be applied, see 3GPP TS 48.060. Note: For 8 kBit/s submultiplexing the Time Alignment commands are defined only for No\_Speech frames and therefore speech frames may need to be stolen to perform time and phase alignment. + +##### 6.6.1.2.1 Downlink Time Alignment + +The TRAU must be able to adjust the time for transmitting the downlink TRAU frames in steps of 250 µs. + +The CCU must be able to calculate the required Time Alignment (TA) with a resolution of 250 µs. + +The TA requests are in the range of 250 µs to 19,75 ms. The CCU calculates the required TA, sends a TA compound request to the TRAU and then starts timer Tta. + +A TA compound request consists of up to five consecutive TA requests. The allowed values of TA requests are given in table 6.1. + +The CCU does not send TA requests when timer Tta is running. Tta is reset by the CCU when the TRAU has applied the TA compound request. The TRAU performs time adjustment corresponding to the TA compound request. + +The CCU can send a new TA compound request as soon as the TRAU has applied the previous TA compound request or Tta has expired. + +Tta is a parameter settable by O&M. + +NOTE: The timer Tta shall be set taking into account the transmission delay and the TRAU reaction time for the application of the TA compound request. + +**Table 3GPP TS 48.061/6.1: Allowed values of TA requests** + +| TA2 | TA1 | TA0 | Value | +|-----|-----|-----|-----------| +| 1 | 1 | 1 | no change | +| 1 | 1 | 0 | - 250 µs | +| 1 | 0 | 1 | + 250 µs | +| 0 | 1 | 1 | + 500 µs | +| 1 | 0 | 0 | + 1 ms | +| 0 | 1 | 0 | + 3 ms | +| 0 | 0 | 1 | + 6 ms | +| 0 | 0 | 0 | + 9 ms | + +When the TRAU detects an uplink transmission error, it ignores the possible TA request contained in the erroneous TRAU frame. + +If the timing is to be advanced by 250 µs, the TRAU shall not transfer the last two bits of the next downlink TRAU frame (bits T1, T2). + +If the timing is to be delayed, the TRAU shall delay the next downlink TRAU frame by inserting the appropriate number of binary "1". + +An example of the procedure is illustrated in figure 6.2. + +If the TRAU detects a change in the timing of the uplink frames greater than 1 ms, it may perform an adjustment on the downlink equal to the change detected on the uplink. + +![Sequence diagram illustrating the Time Alignment procedure between a TRANSCODER/RA UNIT and a CHANNEL CODEC UNIT for 8 kbit/s submultiplexing. The diagram shows speech frames being transmitted and time alignment (TA) requests being processed over a series of 20 ms intervals. The CCU calculates time alignment and sends compound TA requests (TA1 through TA5) to the TRAU. The process starts at time T and ends at T+TA4, after which the CCU can send a new TA request.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +The diagram illustrates the Time Alignment procedure between a TRANSCODER/RA UNIT (TRAU) and a CHANNEL CODEC UNIT (CCU) for 8 kbit/s submultiplexing. The sequence of events is as follows: + +- The TRAU sends a series of speech frames to the CCU at 20 ms intervals. +- The CCU receives the frames and calculates the time alignment. +- The CCU sends a "TA compound request" (TA = TA1 + TA2 + TA3 + TA4 + TA5) to the TRAU. +- The TRAU processes the request and sends back individual TA requests (TA1, TA2, TA3, TA4, TA5) in subsequent speech frames. +- The CCU receives these requests and calculates the time alignment for each. +- The CCU sends a "Start Tta" message to the TRAU. +- The TRAU continues to send speech frames. +- The CCU sends a "Stop Tta" message to the TRAU. +- At this point in time, the CCU can send a new TA request to the TRAU. + +Timing parameters shown on the left side of the diagram: + +- T = Arbitrary or Default time +- + possible previous TA requests +- 20 ms (interval between frames) +- T TA1 +- T:=T+TA1 TA2 +- T:=T+TA2 TA3 +- T:=T+TA3 TA4 +- T:=T+TA4 TA5 + +Sequence diagram illustrating the Time Alignment procedure between a TRANSCODER/RA UNIT and a CHANNEL CODEC UNIT for 8 kbit/s submultiplexing. The diagram shows speech frames being transmitted and time alignment (TA) requests being processed over a series of 20 ms intervals. The CCU calculates time alignment and sends compound TA requests (TA1 through TA5) to the TRAU. The process starts at time T and ends at T+TA4, after which the CCU can send a new TA request. + +Figure 3GPP TS 48.061/6.2: Time Alignment procedure, 8 kbit/s submultiplexing + +##### 6.6.1.2.2 Uplink Time Alignment + +In order to achieve optimum timing between the Air interface and the terrestrial link, the tail bits of the uplink speech frames may be used for uplink time alignment. + +To advance 125 µs, the CCU removes the last tail bit (T2) of the uplink TRAU speech frame. + +To delay 125 µs, the CCU inserts one binary "1" between two uplink TRAU speech frames. + +In case of AMR two tail bits (D126 .. T) are defined for No\_Speech frames, one tail bit (T) for the three lower codec modes (4,75, 5,15 and 5,90) and no tail bits for the higher modes (6,70 and 7,40). To advance by 125 µs in the higher codec mode , the CCU may either remove the last data bit (small distortion of the speech signal) or replace a speech frame by a No\_Speech frame (also speech distortion) and then remove the T bit. To delay 125 µs, the CCU inserts one binary "1" between two uplink TRAU speech frames. + +##### 6.6.1.2.3 Initiation at Resource allocation + +When the BTS receives the 3GPP TS 48.058 CHANNEL ACTIVATION message from the BSC, with Channel Mode IE indicating speech, it allocates the appropriate radio resources and a CCU. The CCU then initiates sending of TRAU speech frames towards the TRAU with normal frame phase for the TDMA channel in question. + +When receiving the first frame, the TRAU shall start sending speech frames towards the CCU with arbitrary or default phase related to the uplink frame phase. + +When receiving these frames, the CCU calculates the timing adjustment required in order to achieve minimum buffer delay and sends a timing adjustment request to the TRAU according to the procedure described in clause 6.6.1.2.1. + +##### 6.6.1.2.4 Time Alignment during handover + +###### 6.6.1.2.4.1 BSS External Handover + +For BSS external handover, the procedure described in clause 6.6.1.2.3 should be used by the new BSC/BTS at resource allocation. + +###### 6.6.1.2.4.2 BSS Internal Handover + +The timing of the downlink frames may have to be adjusted if a BSS internal handover has been performed. In order to speed up the alignment of the downlink frames, this must be detected by the TRAU, e.g. by detecting the change in the uplink frame timing as described in clause 6.6.1.2.1. The TRAU may consequently perform an adjustment on the downlink equal to the change detected on the uplink. + +### 6.6.2 Procedures for Discontinuous Transmission (DTX) + +For Adaptive Multi-Rate speech see 3GPP TS 48.060. + +The procedures for comfort noise are described in 3GPP TS 46.022, the overall operation of DTX is described in 3GPP TS 46.041 and the Voice Activity Detector is described in 3GPP TS 46.042. + +The downlink DTX Handler function is considered as a part of the TRAU when remote transcoders are applied. + +The specification of the DTX Handler is given in 3GPP TS 46.041. + +#### 6.6.2.1 DTX procedures in the uplink direction + +In the comfort noise generation state, the MS will transmit a new traffic frame only every 240 ms (which corresponds to 12 TRAU speech frames). These traffic frames are transferred in the normal way between the CCU and the TRAU. If no valid traffic frames are received, the CCU shall apply the procedure described in clause 6.5. Furthermore the frame classification is done according to the following paragraphs. + +##### 16 kbit/s submultiplexing + +In all uplink 320 bit TRAU frames, the BFI (Bad Frame Indicator) indicator, the SID (Silence Descriptor) indicator and the TAF (Time Alignment Flag) indicator are set as output from the Radio Subsystem (Error correction & detection and SID frame detection, see 3GPP TS 46.041). + +##### 8 kbit/s submultiplexing + +The frame classification is set as output from the Radio Subsystem (Error correction and detection and SID frame detection, see 3GPP TS 46.041) in the uplink 160 bit TRAU speech frame (SID frame, see clauses 5.2.1 and 5.2.4.1). + +#### 6.6.2.2 DTX procedures in the downlink direction + +To inform the DTX handler in the remote transcoder whether downlink DTX shall be applied or not, the DTXd bit in the uplink TRAU speech frame is used. The coding is as follows: + +DTXd = 0: Downlink DTX shall not be applied; + +DTXd = 1: Downlink DTX shall be applied. + +Though this parameter is linked with the resource allocation in the BTS at call setup, its value may vary during the connection. + +Two consecutive TRAU frames without detected errors and with the same DTXd flag value shall be considered as an indication to change DTX mode. + +The SP (Speech) indicator is set as output from the Tx DTX handler (voice activity detection, see 3GPP TS 46.041) in the downlink TRAU speech frames (see clause 5.2.4.2). + +## 6.7 Procedures for Data Frames + +When rate adaption to 64 kbit/s is performed at the BTS (sub-64 kbit/s traffic channels are not used), the rate adaption between the format used on the radio interface and the 64 kbit/s format is made by the RA1/RA1' and the RA2 function as described in 3GPP TS 48.020. This is illustrated in figure 6.3. + +![Figure 3GPP TS 48.061/6.3: Rate adaption when performed at the BTS. The diagram shows a flow from left to right: a vertical line labeled '64 kbit/s' enters a box labeled 'RA2'. An arrow points from 'RA2' to a vertical line labeled 'CCITT V.110 80 bits frame'. From this line, an arrow points to a box containing two sub-blocks labeled 'RA1' and 'RA1'' side-by-side. An arrow points from 'RA1'' to a vertical line labeled 'Channel codec frame'.](f732d3320afe06d979aabbd366184254_img.jpg) + +Figure 3GPP TS 48.061/6.3: Rate adaption when performed at the BTS. The diagram shows a flow from left to right: a vertical line labeled '64 kbit/s' enters a box labeled 'RA2'. An arrow points from 'RA2' to a vertical line labeled 'CCITT V.110 80 bits frame'. From this line, an arrow points to a box containing two sub-blocks labeled 'RA1' and 'RA1'' side-by-side. An arrow points from 'RA1'' to a vertical line labeled 'Channel codec frame'. + +**Figure 3GPP TS 48.061/6.3: Rate adaption when performed at the BTS** + +When sub-64 kbit/s traffic channels are used, two modified ITU-T V.110 frames are transferred in each TRAU data frame. An additional intermediate rate adaption function, RAA, is applied in order to perform the adaption between the TRAU data frame format and the ITU-T V.110 80 bits frame format. This is illustrated in figure 6.4. + +![Figure 3GPP TS 48.061/6.4: Rate adaption when sub-64 kbit/s traffic channels are used. The diagram shows a flow from left to right: a vertical line labeled '64 kbit/s' enters a box labeled 'RA2'. An arrow points from 'RA2' to a vertical line labeled 'CCITT V.110 80 bits frame'. From this line, an arrow points to a box labeled 'RAA'. Below this arrow, text indicates '16 kbit/s submultiplexing : TRAU 320 bits frame' and '8 kbit/s submultiplexing : TRAU 160 bits frame'. An arrow points from the 'RAA' box to another box labeled 'RAA'. From this second 'RAA' box, an arrow points to a vertical line labeled 'CCITT V.110 80 bits frame'. From this line, an arrow points to a box containing two sub-blocks labeled 'RA1' and 'RA1'' side-by-side. An arrow points from 'RA1'' to a vertical line labeled 'Channel codec frame'.](8be52e8ae172cee527c14d299d386f3c_img.jpg) + +Figure 3GPP TS 48.061/6.4: Rate adaption when sub-64 kbit/s traffic channels are used. The diagram shows a flow from left to right: a vertical line labeled '64 kbit/s' enters a box labeled 'RA2'. An arrow points from 'RA2' to a vertical line labeled 'CCITT V.110 80 bits frame'. From this line, an arrow points to a box labeled 'RAA'. Below this arrow, text indicates '16 kbit/s submultiplexing : TRAU 320 bits frame' and '8 kbit/s submultiplexing : TRAU 160 bits frame'. An arrow points from the 'RAA' box to another box labeled 'RAA'. From this second 'RAA' box, an arrow points to a vertical line labeled 'CCITT V.110 80 bits frame'. From this line, an arrow points to a box containing two sub-blocks labeled 'RA1' and 'RA1'' side-by-side. An arrow points from 'RA1'' to a vertical line labeled 'Channel codec frame'. + +**Figure 3GPP TS 48.061/6.4: Rate adaption when sub-64 kbit/s traffic channels are used** + +### 6.7.1 The RAA Function + +The RAA function performs the adaption between the ITU-T V.110 80 bits frame format and the TRAU data frame format. + +When going from the V.110 format to the TRAU data frame format, the synchronization pattern (first octet with all bits coded binary "0" and the 9 bits coded binary "1" in the position 1 of the following octets) of the ITU-T V.110 80 bits frame is stripped off. Two modified V.110 63 bits frames are then transferred in each TRAU data frame as shown in clause 5.1.2 for 16 kbit/s submultiplexing and clause 5.2.2 for 8 kbit/s submultiplexing. + +When going from the TRAU data frame format to the V.110 80 bits frame format, the two modified V.110 63 bits frames are separated and the synchronization pattern is again included. + +The 80 bits V.110 frame is illustrated in figure 6.5. + +| Octet no. | Bit number | | | | | | | | +|-----------|------------|-----|-----|-----|-----|-----|-----|-----| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | D1 | D2 | D3 | D4 | D5 | D6 | D7 | +| 2 | 1 | D8 | D9 | D10 | D11 | D12 | D13 | D14 | +| 3 | 1 | D15 | D16 | D17 | D18 | D19 | D20 | D21 | +| 4 | 1 | D22 | D23 | D24 | D25 | D26 | D27 | D28 | +| 5 | 1 | D29 | D30 | D31 | D32 | D33 | D34 | D35 | +| 6 | 1 | D36 | D37 | D38 | D39 | D40 | D41 | D42 | +| 7 | 1 | D43 | D44 | D45 | D46 | D47 | D48 | D49 | +| 8 | 1 | D50 | D51 | D52 | D53 | D54 | D55 | D56 | +| 9 | 1 | D57 | D58 | D59 | D60 | D61 | D62 | D63 | + +Figure 3GPP TS 48.061/6.5: ITU-T V.110 80 bits frame + +#### 16 kbit/s submultiplexing + +The modified V.110 63 bits frame is illustrated in clause 5.1.2 with: + +- the D-bits of the modified V.110 63 bits frame in position 1 of the TRAU data frame; +- the D'-bits of the modified V.110 63 bits frame in position 3 of the TRAU data frame, + +corresponding respectively to the D-bits of the V.110 80 bits frame (see figure. 6.5). + +#### 8 kbit/s submultiplexing + +The modified V.110 63 bits frame is illustrated in clause 5.2.2 with: + +- the D-bits of the modified V.110 63 bits frame in position 1 of the TRAU data frame; +- the D'-bits of the modified V.110 63 bits frame in position 2 of the TRAU data frame, + +corresponding respectively to the D-bits of the V.110 80 bits frame (see figure. 6.5). + +### 6.7.2 The RA1/RA1' Function + +This function is described in 3GPP TS 44.021. + +### 6.7.3 The RA2 Function + +This function is described in 3GPP TS 44.021. + +### 6.7.4 Procedures for 8 kbit/s intermediate rate adaption rate + +For 8 kbit/s intermediate rate adaption rate, two modified ITU-T V.110 72 bits frames are transferred in each TRAU data frame. If the data transfer terminates before the TRAU data frame has been completed, the remaining data bit positions in the TRAU data frame should be coded binary "1". + +If V.110 frame synchronization has been lost in the downlink direction, the TRAU shall react as if V.110 frames with all data bits coded binary "1" had been received (bits D1 to D63, see clause 6.7.1). + +### 6.7.5 Support of Non-Transparent Bearer Applications + +The procedures for transfer of non-transparent bearer applications are specified in 3GPP TS 48.020. The 240 bit RLP frame is converted to four modified V.110 80 bit frames. + +The same conversion is applied when transferred in a TRAU data frame. The TRAU data frames are coded as specified in clause 6.7.4. + +## 6.8 Frame Synchronization + +### 6.8.1 16 kbit/s submultiplexing + +#### 6.8.1.1 Search for Frame Synchronization + +The frame synchronization is obtained by means of the first two octets in each frame, with all bits coded binary "0", and the first bit in octet no. 3, 5, 7, 9, ... 39 coded binary "1". The following 35 bit alignment pattern is used to achieve frame synchronization: + +| | | | | | | | | +|-----------------|-----------------|----------------|----------------|----------------|----------------|----------------|----------------| +| 00000000 | 00000000 | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | +| 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | +| 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | +| 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | +| 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | 1XXXXXX | XXXXXXX | + +#### 6.8.1.2 Frame Synchronization After Performing Downlink Timing Adjustments + +If the timing of the downlink TRAU speech frames is adjusted, the adjustment is indicated in bits C6 - C11 as described in clauses 6.6.1.1.1.1 and 6.6.1.1.1.2. The frame synchronization unit of the CCU shall change its frame synchronization window accordingly. + +#### 6.8.1.3 Frame Synchronization Monitoring and Recovery + +The monitoring of the frame synchronization shall be a continuous process using the same procedure as for initial detection. + +Loss of frame synchronization shall not be assumed unless at least three consecutive frames, each with at least one framing bit error, are detected. + +When it detects a framing bit error, the TRAU uses the control bit UFE (Uplink Frame Error) in the next downlink TRAU frame to indicate it to the CCU. When the CCU receives a TRAU frame indicating an Uplink Frame Error and which has no errors on the synchronization pattern and the control bits, it starts a timer TsyncU. + +If loss of frame synchronization is detected by the CCU it starts a timer TsyncD. If TsyncD or TsyncU expires before frame synchronization is again obtained the call shall be released as specified in 3GPP TS 48.058 with the cause field set to "Remote Transcoder Failure". + +TsyncD is reset every time frame synchronization is again obtained. + +TsyncU is reset every time three consecutive TRAU frames are received without Uplink Frame Error indication, without errors on the frame synchronization pattern and on the control bits. + +TsyncD and TsyncU are parameters set by O&M (default value = 1 second). + +### 6.8.2 8 kbit/s submultiplexing + +#### 6.8.2.1 Search for Frame Synchronization + +##### 6.8.2.1.1 For Half Rate speech and data + +The frame synchronization is obtained by a 28 bit pattern which is indicated below by all the bits set to binary "0" or binary "1". + +| | | | | +|------------------------|------------------------|------------------------|------------------------| +| 0 0 0 0 0 0 0 0 | 1 x x x x x x x | 0 1 x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | + +##### 6.8.2.1.2 For Adaptive Multi-Rate speech + +The frame synchronisation for No\_Speech frames and the speech frames of the three lower codec modes is obtained by a 28 bit pattern, which is indicated below by all the bits set to binary "0" or binary "1". + +Initial Synchronisation is started after resource allocation and after loss of synchronisation. Initial Synchronisation shall be a continuous process. Synchronisation shall be regarded as obtained if at least one complete frame is detected with all 28 synchronisation bits and all control and CRC bits correct: + +| | | | | +|------------------------|------------------------|------------------------|------------------------| +| 0 0 0 0 0 0 0 0 | 1 x x x x x x x | 1 x x x x x x x | 0 1 x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | + +The frame synchronisation for the speech frames for codec mode 6,70 kBit/s is obtained by a 21 bit pattern, which is indicated below by all the bits set to binary "0" or binary "1". This codec mode may be used for Initial Synchronisation, the preferred solution is, however, to use a lower code mode or No\_Speech frames. Initial Synchronisation is started after resource allocation and after loss of synchronisation. Initial Synchronisation shall be a continuous process. + +Synchronisation shall be regarded as obtained if at least one complete frame is detected with all 21 synchronisation bits and all control and CRC bits correct: + +| | | | | +|------------------------|------------------------|------------------------|------------------------| +| 0 0 0 0 0 0 0 0 | 1 x x x x x x x | 1 x x x x x x x | 1 x x x x x x x | +| 1 x x x x x x x | 0 x x x x x x x | 1 x x x x x x x | x x x x x x x | +| 1 x x x x x x x | x x x x x x x | 1 x x x x x x x | x x x x x x x | +| 1 x x x x x x x | x x x x x x x | 1 x x x x x x x | x x x x x x x | +| 1 x x x x x x x | x x x x x x x | 1 x x x x x x x | x x x x x x x | + +The frame synchronisation for the speech frames for codec mode 7,40 kBit/s is obtained by a 6 bit pattern, which is indicated below by all the bits set to binary "0" or binary "1". This codec mode shall not be used for Initial Synchronisation, the recommended solution is to use a lower code mode or No\_Speech frames: + +| | | | | +|------------------------|----------------------|----------------------|----------------------| +| 0 0 1 x x x x x | 0 x x x x x x | 1 x x x x x x | 0 x x x x x x | +| x x x x x x x | x x x x x x x | x x x x x x x | x x x x x x x | +| x x x x x x x | x x x x x x x | x x x x x x x | x x x x x x x | +| x x x x x x x | x x x x x x x | x x x x x x x | x x x x x x x | +| x x x x x x x | x x x x x x x | x x x x x x x | x x x x x x x | + +#### 6.8.2.2 Frame Synchronization Monitoring and Recovery + +##### 6.8.2.2.1 For Half Rate speech and data + +Same as clause 6.8.1.3. + +##### 6.8.2.2.2 For Adaptive Multi-Rate speech + +The monitoring of the frame synchronisation shall be a continuous process. A frame, respectively a subframe, shall be regarded as correctly received, if synchronisation was established before the beginning of the frame (subframe) and all synchronisation, control and CRC bits within the frame (subframe) are correct. Since the Adaptive Multi-Rate codec may change its codec mode every 40 ms, the monitoring of frame synchronisation shall take these possible changes into account. + +Loss of frame synchronisation shall not be assumed unless at least three consecutive frames, each with at least one framing bit error, are detected. However, for every frame with detected errors a No\_Speech frame shall be sent back with the UFE (DFE) bits set, see clause 6.9.2.1. The receiver shall in addition check, whether the synchronisation pattern can be detected plus or minus one position shifted with respect to the expected position within the bit stream. If synchronisation can not be found by this within three frames, then Initial Synchronisation shall be performed. + +When it detects a framing bit error, the TRAU uses the control bit UFE (Uplink Frame Error) in the next downlink TRAU frame to indicate it to the CCU. When the CCU receives a TRAU frame indicating an Uplink Frame Error and which has no errors on the synchronization pattern and the control bits, it starts a timer TsyncU. + +If loss of frame synchronization is detected by the CCU it starts a timer TsyncD. If TsyncD or TsyncU expires before frame synchronization is again obtained the call shall be released as specified in 3GPP TS 48.058 with the cause field set to "Remote Transcoder Failure". + +TsyncD is reset every time frame synchronization is again obtained. + +TsyncU is reset every time three consecutive TRAU frames are received without Uplink Frame Error indication, without errors on the frame synchronization pattern and on the control bits. + +TsyncD and TsyncU are parameters set by O&M (default value = 1 second). + +## 6.9 Correction/detection of bit errors + +### 6.9.1 16 kbit/s submultiplexing + +In case of AMR speech see 3GPP TS 48.060. + +#### 6.9.1.1 Error Detection on the Control Bits + +In order to reduce the possibility of misinterpretation of control information due to bit errors, the following procedure should be followed: + +##### 6.9.1.1.1 General Procedure + +If any undefined combination of the C-bits is received (see clause 5.1.4), the TRAU frame shall be handled as defined in clause 6.9.1.2. + +##### 6.9.1.1.2 Frames for Half Rate speech + +In addition to the general procedure described in the previous clause, the following procedure should be followed for the speech frames: + +Bits C6 - C11: Time Alignment. + +The full range of the time alignment adjustment should only be applied when the TRAU is in the Initial Time Alignment state (see clauses 6.6.1.1.1.1 and 6.6.1.1.1.2). + +If, in the Static Time Alignment state, a time alignment order is received indicating an adjustment of more than 250 µs, the next downlink frame should be delayed only one 250 µs step. + +If an uplink frame is received with the "Time Alignment" field set to an unused value (101000 ... 111101), this value should be interpreted as "no change". + +#### 6.9.1.2 Handling of frames received with errors for Half Rate speech and data + +If a TRAU frame is received in the uplink or downlink with detectable errors in the control bits, then the control information shall be ignored and the control information from the previous received TRAU frame shall be used to handle the speech or data bits as if no error had been detected. + +If frame synchronization has been lost in the uplink direction, the TRAU shall: + +- for speech, mute the decoded speech as if it has received TRAU frames with errors (cf. 3GPP TS 46.021); +- for data, send idle V.110 frames as defined in 3GPP TS 48.020 to the MSC interworking unit. + +The CCU shall follow the procedure specified in clause 6.5: + +- if frame synchronization has been lost in the downlink direction; +- if a CRC error is detected (bits CRC0-CRC2) in a downlink TRAU speech frame. + +If a CRC error is detected (bits CRC0-CRC2) in a uplink TRAU speech frame, the TRAU speech frame shall be regarded as bad and the TRAU shall apply the procedure defined in 3GPP TS 46.021. + +### 6.9.2 8 kbit/s submultiplexing + +#### 6.9.2.1 Error Detection on the Control Bits + +##### In case of Half Rate speech and Data: + +Error detection is made on control bits C1-C4 with the parity bit C5 (see clause 5.2.4) for all types of 160 bit TRAU frames. Additionally, for TRAU speech frames, error detection is made on control bits XC1-XC5 with the parity bit XC6. + +If the following occurs: + +- parity bit C5 and/or parity bit XC6 are wrong; +- any undefined combination of the control bits is received (see clause 5.2.4) with a correct parity bit. + +The TRAU frame shall be handled as defined in clause 6.9.1.2. + +##### In case of Adaptive Multi-Rate speech: + +If errors are detected within the Sync bits, the Control bits or by the CRC bits, then the frame shall be regarded as invalid. If the error is detected in uplink direction, then the TRAU shall perform error concealment as for any No\_Data frame (see 3GPP TS 26.092). If the error is detected in downlink direction, then the BTS shall handle this with respect to the air interface as described in clause 6.5, respectively in 3GPP TS 48.060. + +A No\_Speech frame with the UFE set to "Uplink Frame Received with Errors" (if the error is detected in uplink), respectively a No\_Speech frame with DFE set to "Downlink Frame Received with Errors" (if the error is detected in downlink) shall be sent back for every detected invalid frame. The other side, when receiving a No\_Speech frame with the UFE, respectively DFE bit set shall respond with a No\_Speech Frame, too, where the DFE respectively UFE bit is not set (unless the error occurred in both directions). In this way the fastest possible re-synchronisation shall be ensured. In case of ongoing TFO these frames may transmit the configuration parameters in addition (see 3GPP TS 48.062). + +#### 6.9.2.2 Handling of frames received with errors + +In case of Half Rate speech and Data: Same as clause 6.9.1.2. + +In case of Adaptive Multi-Rate speech: Same as clause 6.9.2.1. + +## 6.10 Procedures for Operation & Maintenance + +The general procedures for Operation and Maintenance are described in 3GPP TS 12.21. + +If the transcoders are positioned outside the BTS, some O&M functions will be required for the TRAU and the CCU. In particular this applies for transcoders positioned at the MSC site. + +The transcoders outside the BTS are considered a part of the BSC, and the O&M functions for the TRAU should therefore be implemented in the BSC. + +The CCU is a part of the BTS and the O&M functions for this unit should therefore be implemented in the BTS. + +### 6.10.1 Transfer of O&M Information Between the TRAU and the BSC + +The transfer of O&M information between the BSC and the TRAU is possible to do in two ways. Either it is handled directly between the BSC and the TRAU or a BTS is used as a message transfer point. The choice between the two methods is up to the manufacturer of the BSC: + +- i) The transfer of O&M information between the BSC and the TRAU is handled internally by the BSC. The O&M signalling between the TRAU and the BSC may either be handled by proprietary BSC solutions or the O&M TRAU frames defined for 16 kbit/s submultiplexing in clauses 5.1.3 and 5.1.4.3 and for 8 kbit/s submultiplexing in clauses 5.2.3 and 5.2.4 could be used. In the latter case, the BSC has to act as a terminal for the O&M TRAU frames sent between the TRAU and the BSC; +- ii) The O&M information between the TRAU and the BSC is transferred using O&M TRAU frames between the TRAU and the CCU in a BTS. The BTS then acts as a relay function between the O&M TRAU frames and the associated O&M messages sent between the BTS and the BSC. + +### 6.10.2 Procedures in the TRAU + +If O&M information between the TRAU and the BSC is transferred using O&M TRAU frames between the CCU in a BTS and the TRAU, the TRAU sends O&M TRAU frames periodically until the identical O&M TRAU frame is received as an acknowledgement. The period is at least $64 \cdot 20\text{ms}$ (1,28 sec). + +In case of fault conditions, when no immediate action is required, the TRAU may send O&M frames indicating the fault. + +### 6.10.3 Procedures in the BSC + +The BSC should be able to detect a faulty TRAU, take it out of service and give an indication to O&M. A faulty TRAU could be detected e.g. by routine tests, alarms from the TRAU, release of call initiated by the BTS due to remote transcoder failure etc. How this is handled by the BSC is regarded as a BSC internal matter. + +#### 6.10.3.1 Use of O&M Frames + +The use and coding of O&M TRAU frames is left to the implementor of the BSC/TRAU. + +If O&M TRAU frames are used, they are always carrying: + +- 264 data bits in case of 16 kbit/s submultiplexing; +- 120 data bits in case of 8 kbit/s submultiplexing. + +Any corresponding O&M message between the BSC and the BTS shall always carry: + +- all 264 O&M data bits in case of 16 kbit/s submultiplexing; +- 120 data bits in case of 8 kbit/s submultiplexing. + +### 6.10.4 Procedures in the BTS + +If a CCU in a BTS receives O&M TRAU frames from the TRAU, the BTS shall: + +- send the identical frame to the TRAU for acknowledgement; and +- put all the data bits from the received frames into an appropriate O&M message and send it to the BSC. + +If the CCU receives O&M TRAU frames during a speech or data call then the procedure described in clause 6.5 shall apply. + +If receiving an O&M message from the BSC, carrying TRAU O&M information, the BTS puts all the data bits from the received message into an O&M TRAU frame and then the CCU allocated to the addressed connection sends the frame to the TRAU in one single O&M TRAU frame. Repetition is done according to 3GPP TS 12.21 + +In case of a faulty CCU, the O&M procedures are BTS internal. + +# Annex A (informative): Change History + +| Change history | | | | | | +|----------------|-----------|-----|-----|------------------------------------------------------------------------------------|------------------| +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +| GP-04 | - | - | - | April 2001. Conversion to 3GPP layout and number.
References have been updated. | 48.061
v4.0.0 | +| GP-08 | GP-020179 | 001 | | Correct synchronisation description for HR_AMR | 4.1.0 | +| | | | | Editorial | 4.1.1 | +| GP-09 | GP-020524 | 002 | | Generic Configuration Frames for TFO | 5.0.0 | +| GP-23 | | | | Version for Release 6 | 6.0.0 | +| GP-35 | | | | Version for Release 7 | 7.0.0 | +| GP-40 | | | | Version for Release 8 | 8.0.0 | +| GP-44 | | | | Version for Release 9 | 9.0.0 | +| GP-49 | | | | Version for Release 10 | 10.0.0 | +| GP-55 | | | | Version for Release 11 | 11.0.0 | +| GP-63 | | | | Version for Release 12 (frozen at SP-65) | 12.0.0 | +| GP-68 | | | | Version for Release 13 (frozen at SP-70) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48071/raw.md b/marked/Rel-16/48_series/48071/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3680e36a9bae859566b109c2467ec510e92f789f --- /dev/null +++ b/marked/Rel-16/48_series/48071/raw.md @@ -0,0 +1,958 @@ + + + + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 4 Messages functional definitions and contents..... | 7 | +| 4.1 General ..... | 7 | +| 4.2 Messages ..... | 7 | +| 4.2.1 TA Request..... | 8 | +| 4.2.2 TA Response ..... | 8 | +| 4.2.3 (void) ..... | 8 | +| 4.2.4 (void) ..... | 8 | +| 4.2.5 Reject..... | 8 | +| 4.2.6 Reset ..... | 9 | +| 4.2.7 Abort..... | 9 | +| 4.2.8 TA Layer3 ..... | 10 | +| 4.2.9 MS Position Command..... | 10 | +| 4.2.10 MS Position Response ..... | 10 | +| 4.2.11 U-TDOA Request..... | 11 | +| 4.2.12 U-TDOA Response ..... | 11 | +| 5 Information element encodings..... | 12 | +| 5.1 Message Type IE..... | 14 | +| 5.2 Timing Advance IE ..... | 14 | +| 5.3 (void)..... | 14 | +| 5.4 Cell Identity IE ..... | 14 | +| 5.5 (void)..... | 15 | +| 5.6 (void)..... | 15 | +| 5.7 (void)..... | 15 | +| 5.8 Channel Description IE ..... | 15 | +| 5.9 (void)..... | 15 | +| 5.10 (void)..... | 15 | +| 5.11 (void)..... | 15 | +| 5.12 Measurement Report IE ..... | 15 | +| 5.13 (void)..... | 16 | +| 5.14 Cause IE ..... | 16 | +| 5.15 RRLP Flag IE ..... | 16 | +| 5.16 RRLP IE ..... | 17 | +| 5.17 Cell Identity List IE..... | 17 | +| 5.18 Enhanced Measurement Report IE ..... | 18 | +| 5.19 Location Area Code IE..... | 18 | +| 5.20 Frequency List IE ..... | 19 | +| 5.21 MS Power IE ..... | 19 | +| 5.22 Delta Timer IE..... | 19 | +| 5.23 Serving Cell Identifier IE ..... | 19 | +| 5.24 Encryption Key IE..... | 20 | +| 5.25 Cipher Mode Setting IE..... | 20 | +| 5.26 Channel Mode IE ..... | 20 | +| 5.27 MultiRate Configuration IE ..... | 20 | +| 5.28 Polling Repetition IE ..... | 20 | +| 5.29 Packet Channel Description IE ..... | 21 | +| 5.30 TLLI IE ..... | 21 | +| 5.31 TFI IE ..... | 21 | +| 5.32 Starting Time IE ..... | 21 | +| 5.33 Long Encryption Key IE ..... | 22 | +| 5.34 Concurrent Positioning Flag..... | 22 | + +Annex A (informative): Change History................................................................................................ 23 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document contains the coding of information necessary for support of location service operation on the SMLC-BSS interface layer 3. + +Clause 2 gives the functional definitions and contents of messages for location service operations. Clause 3 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations. + +# --- 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 43.059: "Functional stage 2 description of Location Services (LCS) in GERAN". +- [3] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects". +- [4] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [4a] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". +- [5] 3GPP TS 45.008: "Radio subsystem link control". +- [6] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [7] 3GPP TS 49.031: "Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". +- [8] 3GPP TS 44.031: "Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP)". + +# --- 3 Definitions and abbreviations + +For the purposes of the present document, the abbreviations, terms and definitions given in 3GPP TR 21.905 and 3GPP TS 43.059 apply. + +# --- 4 Messages functional definitions and contents + +## 4.1 General + +This sub-clause defines the structure of the messages of the SMLC-BSS layer 3 protocol defined in 3GPP TS 43.059. + +Each definition includes: + +- a) a brief description of the message; +- b) a table listing the information elements in the order of their appearance in the message. + +For each IE the table indicates: + +- 1) the name of the IE (which gives an idea of the semantics of the element), which is used in this and other specifications as a reference to the IE within the message; + - 2) the name of the type of the IE (which indicates the coding of the value part of the IE), and a reference to a description of the value part of the IE; + - 3) the presence requirement indication (M, C or O) for the IE, as defined in 3GPP TS 24.007; + - 4) the format of the IE (T, V, TV, LV, TLV) as defined in 3GPP TS 24.007; + - 5) the length of the IE (or permissible range of lengths), in octets, in the message. The value of the length gives the number of octets in the IE following the length and element identifier. Where the length is encoded using more than one octet, the high order bit is bit 8 of the first (lowest numbered octet) and the low order bit is bit 1 of the last (highest numbered octet). When a length has a range of M to N octets, the notation "M-N" is used. The symbol "n" represents the maximum of a range when indefinite. +- c) sub-clauses specifying conditions for IEs with presence requirement C or O in the relevant message. Together with other conditions specified in 3GPP TS 43.059 this defines when the IE shall be included or not, what non-presence of such IEs means, and (for IEs with presence requirement C) the static conditions for presence and/or non-presence of the IEs (see 3GPP TS 43.059). + +## 4.2 Messages + +The following Location Services related messages are exchanged between the SMLC and the BSS: + +- TA Request; +- TA Response; +- Reject; +- Reset; +- Abort; +- TA Layer3; +- MS Position Command; +- MS Position Response; +- U-TDOA Request; +- U-TDOA Response. + +On the Lb interface the messages are contained in the BSSLAP APDU IE which is encapsulated in the following messages as specified in 3GPP TS 49.031: + +- BSSMAP-LE CONNECTION ORIENTED INFORMATION message (for all messages except the TA LAYER 3 message); + +- BSSMAP-LE PERFORM LOCATION REQUEST message (for the TA LAYER 3 message) +- BSSMAP-LE PERFORM LOCATION INFORMATION message (for the TA LAYER 3 message). + +### 4.2.1 TA Request + +The TA Request is a message from the SMLC to the BSS, requesting BSS to return the timing advance (or access delay) of the MS. + +**Table 4.2.1.1: TA Request message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|-----------------------|----------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | + +### 4.2.2 TA Response + +The TA Response is a message from the BSS to the SMLC. It is a response to TA Request message and contains the following information elements. + +**Table 4.2.2.1: TA Response message content** + +| Information element | Type/Reference | Presence | Format | Length | +|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | +| Serving Cell Identity | Cell Identity IE / 5.4 | M | TV | 3 | +| Timing Advance | Timing Advance IE / 5.2 | M | TV | 2 | +| Measurement Report | Measurement Report IE / 5.12 | O | TLV | 18 | +| Enhanced Measurement Report | Enhanced Measurement Report IE / 5.18 | O | TLV | 4-n | +| Measured Cell Identity List | Cell Identity List IE / 5.17 | O | TLV | 6-n | +| Concurrent Method Flag | Concurrent Positioning Flag IE / 5.34 | O (note 1) | TV | 2 | +| NOTE 1: This IE is only included when the BSC allows a concurrent invocation of a first and second positioning procedure | | | | | + +### 4.2.3 (void) + +#### 4.2.4 (void) + +### 4.2.5 Reject + +The Reject is a message from the BSS to the SMLC. It is a possible response to TA Request, MS Position Command or U-TDOA Request and contains the following information elements. + +**Table 4.2.5.1: Reject message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|-----------------------|----------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | +| Cause | Cause IE / 5.14 | M | TV | 2 | + +The following are the expected cause values for Reject message: + +- congestion; +- channel Mode not supported; +- positioning procedure not supported; +- failure for other radio related events; +- incorrect serving cell identity; +- BSSAP-LE Segmentation error; + +- Concurrent Positioning not enabled. + +### 4.2.6 Reset + +The Reset is a message from the BSS to the SMLC. It is sent when the Response message contents for a positioning request are invalidated (e.g. due to handover) before the positioning procedure was completed. + +**Table 4.2.6.1: Reset message content** + +| Information element | Type/Reference | Presence | Format | Length | +|-----------------------------|---------------------------------------|-----------------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | +| Cell ID | Cell Identity IE / 5.4 | M | TV | 3 | +| Timing Advance | Timing Advance IE / 5.2 | M | TV | 2 | +| Channel description | Channel Description IE / 5.8 | M | TV | 4 | +| Cause | Cause IE / 5.1 | M | TV | 2 | +| Measurement Report | Measurement Report IE / 5.12 | O | TLV | 18 | +| Enhanced Measurement Report | Enhanced Measurement Report IE / 5.18 | O | TLV | 4-n | +| Measured Cell Identity List | Cell Identity List IE / 5.17 | O | TLV | 6-n | +| LAC | Location Area Code IE / 5.19 | O | TV | 3 | +| Frequency List | Frequency List IE 5.20 | C (note 1) | TLV | 3-n | +| Channel Mode | Channel Mode IE 5.26 | C (notes 2 & 4) | TV | 2 | +| MultiRate Configuration | MultiRate Configuration 5.27 | C (notes 3 & 4) | TLV | 4-n | +| Packet Channel Description | Packet Channel Description IE 5.29 | C (note 5) | TV | 4 | +| TLLI | TLLI IE 5.30 | C (note 5) | TV | 5 | +| TFI | TFI 5.31 | C (note 5) | TV | 2 | +| TBF Starting Time | Starting Time IE 5.32 | C (note 5) | TV | 3 | +| Encryption Key (Kc) | Encryption Key IE 5.24 | C (note 6) | TV | 9 | +| Cipher Mode Setting | Cipher Mode Setting IE 5.25 | C (note 4) | TV | 2 | +| Long Encryption Key (Kc128) | Long Encryption Key IE 5.33 | C (note 7) | TV | 17 | + +NOTE 1: The Frequency List IE is included only for U-TDOA when frequency hopping is used. +NOTE 2: The Channel Mode IE is included only for U-TDOA using FR or AMR (not included for EFR). +NOTE 3: The MultiRate Configuration IE is included only for U-TDOA using AMR. +NOTE 4: This IE can only be present for CS U-TDOA location method +NOTE 5: This IE can only be present for PS U-TDOA location method +NOTE 6: This IE can only be present for CS U-TDOA location method and if the Ciphering Mode Setting IE indicates A5/1 or A5/3. +NOTE 7: This IE can only be present for CS U-TDOA location method and if the Ciphering Mode Setting IE indicates A5/4. + +The following are the expected cause values for Reset message: + +- intra-BSS handover; +- failure for other radio related events; +- supervision Timer Expired; +- incorrect serving cell identity. + +### 4.2.7 Abort + +The Abort is a message from the BSS to the SMLC. Upon receiving this signal, the SMLC shall abort ongoing positioning procedure. + +**Table 4.2.7.1: Abort message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|-----------------------|----------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | +| Cause | Cause IE / 5.14 | M | TV | 2 | + +The following are the expected cause values for Abort message: + +- failure for other radio related events; +- supervision Timer Expired; +- inter BSS handover; +- loss of signalling connection to MS. + +### 4.2.8 TA Layer3 + +The TA Layer3 is an optional encapsulated message from the BSS to the SMLC that adds the following information in Complete layer 3 Information as described in 3GPP TS 48.008. + +**Table 4.2.8.1: TA Layer3 message content** + +| Information element | Type/Reference | Presence | Format | Length | +|-----------------------------|---------------------------------------|----------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | +| Timing Advance | Timing Advance IE / 5.2 | M | TV | 2 | +| Measurement Report | Measurement Report IE / 5.12 | O | TLV | 18 | +| Enhanced Measurement Report | Enhanced Measurement Report IE / 5.18 | O | TLV | 4-n | +| Measured Cell Identity List | Cell Identity List IE / 5.17 | O | TLV | 6-n | + +### 4.2.9 MS Position Command + +The BSSLAP MS Position Command is a message from the SMLC to BSS that contains the following information elements. + +**Table 4.2.9.1: MS Position Command message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|-----------------------|----------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | +| flag | RRLP flag IE / 5.15 | M | TV | 2 | +| RRLP Info | RRLP IE / 5.16 | M | TLV | 3-n | + +### 4.2.10 MS Position Response + +The BSSLAP MS Position Response is a message from the BSS to the SMLC that contains the following information elements. + +**Table 4.2.10.1: MS Position Response message content** + +| Information element | Type/Reference | Presence | Format | Length | +|-----------------------------|---------------------------------------|------------|--------|--------| +| Message Type | Message Type IE / 5.1 | M | V | 1 | +| flag | RRLP flag IE / 5.15 | M | TV | 2 | +| RRLP Info | RRLP IE / 5.16 | M | TLV | 3-n | +| Timing Advance | Timing Advance IE / 5.2 | O | TV | 2 | +| Measurement Report | Measurement Report IE / 5.12 | O | TLV | 18 | +| Enhanced Measurement Report | Enhanced Measurement Report IE / 5.18 | O | TLV | 4-n | +| Measured Cell Identity List | Cell Identity List IE / 5.17 | O | TLV | 6-n | +| Concurrent Method Flag | Concurrent Positioning Flag IE / 5.34 | O (note 1) | TV | 2 | + +NOTE 1: This IE is only included when the BSC allows a concurrent invocation of a first and second positioning procedure + +### 4.2.11 U-TDOA Request + +The U-TDOA Request is a message from the SMLC to the BSS. It contains the following information elements. + +**Table 4.2.11.1: U-TDOA Request message content** + +| Information element | Type/Reference | Presence | Format | Length | +|-------------------------------------------------------------------|-----------------------------------|------------|--------|--------| +| Message Type | Message Type IE 5.1 | M | V | 1 | +| Delta Timer | Delta Timer IE 5.22 | O (note 1) | TV | 2 | +| Polling Repetition | Polling Repetition IE 5.28 (note) | C (note 2) | TV | 2 | +| NOTE 1: This IE can only be present for CS U-TDOA location method | | | | | +| NOTE 2: This IE is only present for PS U-TDOA location method | | | | | + +### 4.2.12 U-TDOA Response + +The U-TDOA Response is a message from the BSS to the SMLC. It is a response to the U-TDOA Request message. It contains the following information elements. + +**Table 4.2.12.1: U-TDOA Response message content** + +| Information element | Type/Reference | Presence | Format | Length | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------|--------|--------| +| Message Type | Message Type IE 5.1 | M | V | 1 | +| Channel Description | Channel Description IE 5.8 | M | TV | 4 | +| Serving Cell Identifier | Cell Identifier IE 5.23 | M | TLV | 4-n | +| Frequency List | Frequency List IE 5.20 | C (note 3) | TLV | 3-n | +| Timing Advance | Timing Advance IE 5.2 | O | TV | 2 | +| MS Power | MS Power IE 5.21 | O | TV | 2 | +| Measurement Report | Measurement Report IE 5.12 | O | TLV | 18 | +| Encryption Key (Kc) | Encryption Key IE 5.24 | C (note 7) | TV | 9 | +| Cipher Mode Setting | Cipher Mode Setting IE 5.25 | C (note 4) | TV | 2 | +| Channel Mode | Channel Mode IE 5.26 | C (notes 1 & 4) | TV | 2 | +| MultiRate Configuration | MultiRate Configuration IE 5.27 | C (notes 1 & 4) | TLV | 4-n | +| Measured Cell Identity List | Cell Identity List IE / 5.17 | O | TLV | 6-n | +| Packet Channel Description | Packet Channel Description IE 5.29 | C (note 5) | TV | 4 | +| TLLI | TLLI IE 5.30 | C (note 5) | TV | 5 | +| TFI | TFI IE 5.31 | C (note 5) | TV | 2 | +| TBF Starting Time | Starting Time IE 5.32 | C (note 5) | TV | 3 | +| Power-Up Starting Time | Starting Time IE 5.32 | O (note 6) | TV | 3 | +| Long Encryption Key (Kc128) | Long Encryption Key IE 5.33 | C (note 8) | TV | 17 | +| Concurrent Method Flag | Concurrent Positioning Flag IE / 5.34 | O (note 9) | TV | 2 | +| NOTE 1: The Channel Mode IE is included only for U-TDOA using FR or AMR (not included for EFR). | | | | | +| NOTE 2: The MultiRate Configuration IE is included only for U-TDOA using AMR. | | | | | +| NOTE 3: The Frequency List IE is included only when frequency hopping is used. NOTE 4: This IE can only be present for CS U-TDOA location method. | | | | | +| NOTE 5: This IE can only be present for PS U-TDOA location method . | | | | | +| NOTE 6: The Power-Up Starting Time IE is included if the Power-Up procedure is supported for U-TDOA location method. It represents the starting time of the power-up and DTX suspension. | | | | | +| NOTE 7: This IE can only be present for CS U-TDOA location method and if the Ciphering Mode Setting IE indicates A5/1 or A5/3. | | | | | +| NOTE 8: This IE can only be present for CS U-TDOA location method and if the Ciphering Mode Setting IE indicates A5/4. | | | | | +| NOTE 9: This IE is only included when the BSC allows a concurrent invocation of a first and second positioning procedure | | | | | + +# --- 5 Information element encodings + +This paragraph contains the coding of the signalling elements used. + +The following conventions are assumed for the sequence of transmission of bits and bytes: + +- each bit position is marked as 1 to 8. Bit 1 is the least significant bit and is transmitted first; +- in an element octets are identified by number, octet 1 is transmitted first, then octet 2 etc. + +When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. + +- For variable length elements a length indicator is included, this indicates the number of octets following in the element. +- All fields within Information Elements are mandatory unless otherwise specified. The Information Element Identifier shall always be included. + +All spare bits are set to 0. + +The elements used and their coding are: + +**Table 5.1: Element Identifier codes** + +| Element Identifier Coding | Element name | Reference | +|-----------------------------------------------------------------------------------------------------------------|---------------------------------------|------------------| +| 0000 0001 | Timing Advance | 5.2 | +| 0000 1000 | Reserved (note) | | +| 0000 1001 | Cell Identity | 5.4 | +| 0000 1010 | Reserved (note) | | +| 0000 1011 | Reserved (note) | | +| 0000 1100 | Reserved (note) | | +| 0001 0000 | Channel Description | 5.8 | +| 0001 0001 | Reserved (note) | | +| 0001 0010 | Reserved (note) | | +| 0001 0011 | Reserved (note) | | +| 0001 0100 | Measurement Report | 5.12 | +| 0001 0101 | Reserved (note) | | +| 0001 1000 | Cause | 5.14 | +| 0001 1001 | RRLP Flag | 5.15 | +| 0001 1011 | RRLP IE | 5.16 | +| 0001 1100 | Cell Identity List | 5.17 | +| 0001 1101 | Enhanced Measurement Report | 5.18 | +| 0001 1110 | Location Area Code | 5.19 | +| 0010 0001 | Frequency List | 5.20 | +| 0010 0010 | MS Power | 5.21 | +| 0010 0011 | Delta Timer | 5.22 | +| 0010 0100 | Serving Cell Identifier | 5.23 | +| 0010 0101 | Encryption Key (Kc) | 5.24 | +| 0010 0110 | Cipher Mode Setting | 5.25 | +| 0010 0111 | Channel Mode | 5.26 | +| 0010 1000 | MultiRate Configuration | 5.27 | +| 0010 1001 | Polling Repetition | 5.28 | +| 0010 1010 | Packet Channel Description | 5.29 | +| 0010 1011 | TLLI | 5.30 | +| 0010 1100 | TFI | 5.31 | +| 0010 1101 | TBF Starting Time | 5.32 | +| 0010 1110 | Power-Up Starting Time | 5.32 | +| 0010 1111 | Long Encryption Key (Kc128) | 5.33 | +| 0011 0000 | Concurrent Positioning Procedure Flag | 5.34 | +| NOTE: These values of the codepoints shall not be used as they were used in an earlier version of the protocol. | | | + +All unassigned codes are spare. + +## 5.1 Message Type IE + +Message Type uniquely identifies the message being sent. It is a single octet element, mandatory in all messages. + +All unassigned codes are spare. + +**Table 5.1.1: Message Type codes** + +| 8 7 6 5 4 3 2 1 | | +|-----------------------------------------------------------------------------------------------------------------|----------------------| +| 0 0 0 0 0 0 0 0 | Reserved. | +| 0 0 0 0 0 0 0 1 | TA REQUEST | +| 0 0 0 0 0 0 1 0 | TA RESPONSE | +| 0 0 0 0 0 1 0 0 | Reserved (note) | +| 0 0 0 0 0 1 0 1 | Reserved (note) | +| 0 0 0 0 1 0 1 0 | REJECT | +| 0 0 0 0 1 0 1 1 | RESET | +| 0 0 0 0 1 1 0 0 | ABORT | +| 0 0 0 0 1 1 0 1 | TA LAYER3 | +| 0 0 0 0 1 1 1 1 | MS Position Command | +| 0 0 0 1 0 0 0 0 | MS Position Response | +| 0 0 0 1 0 0 0 1 | U-TDOA Request | +| 0 0 0 1 0 0 1 0 | U-TDOA Response | +| NOTE: These values of the codepoints shall not be used as they were used in an earlier version of the protocol. | | + +## 5.2 Timing Advance IE + +This element contains the Timing Advance measured by the BTS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Timing Advance | | | | | | | | octet 2 | + +**Figure 5.2.1: Timing Advance IE** + +The coding of the timing advance value field is the binary representation of the timing advance in bit periods; 1 bit period = 48/13 us, as described in 3GPP TS 44.018 with the difference that all 8 bits are significant (instead of the normal 6 bits), which is necessary in order to report TA from extended range cells. To be correct, values over 63 do not correspond to a TA used by the MS (maximum is 63). Instead values over 63 correspond to the access delay measured by the BTS. + +## 5.3 (void) + +## 5.4 Cell Identity IE + +This element defines the cell identity of the MS serving cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Cell Identity | | | | | | | | octet 2-3 | + +**Figure 5.4.1: Cell Identity IE** + +The coding of the Cell Identity field is as defined in 3GPP TS 24.008 (excluding IEI). + +5.5 (void) + +5.6 (void) + +5.7 (void) + +## 5.8 Channel Description IE + +This element defines the physical channel allocation of the MS. + +| | | | | | | | | | +|---------------------|---|---|---|---|---|---|------------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | octet 1 | | +| Channel Description | | | | | | | octets 2-4 | | + +**Figure 5.8.1: Channel Description IE** + +The coding of Channel Description field is as defined in 3GPP TS 44.018 (excluding IEI). + +5.9 (void) + +5.10 (void) + +5.11 (void) + +## 5.12 Measurement Report IE + +This element contains the measurement report from the BSS. + +| | | | | | | | | | +|---------------------|---|---|---|---|---|---|------------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | octet 1 | | +| Length | | | | | | | octet 2 | | +| Measurement Results | | | | | | | octet 3-18 | | + +**Figure 5.12.1: Measurement Report IE** + +The Measurement Results field is encoded as in 3GPP TS 44.018 (excluding IEI) with the changes specified below. + +### DTX-USED + +The DTX-USED bit shall be set as the DTXd field in the UPLINK MEASUREMENTS message in 3GPP TS 48.058. + +If the DTX-USED field is set to "0" the SMLC shall use the RXLEV-FULL and RXQUAL-FULL values. + +If the DTX-USED field is set to "1" the SMLC shall use the RXLEV-SUB and RXQUAL-SUB values. + +### RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL + +When the values of RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL from TS 44.018 are 0 or 63, then their value shall be encoded to the Measurement Results without change. Otherwise, the values of RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL shall be added with 2 times the power reduction value corresponding to the Power Level field in the BS POWER message in 3GPP TS 48.058. A result higher than the upper boundary shall be limited to 63 to avoid value out of range. + +RXLEV-FULL-SERVING-CELL (parameter in Measurement Results) + = RXLEV-FULL-SERVING-CELL (parameter from TS 44.018, in octet 2 of NMR section 10.5.2.20 ) + + 2\*( Power Level field in the BS POWER message) + +RXLEV-SUB-SERVING-CELL (parameter in Measurement Results) + = RXLEV-SUB-SERVING-CELL (parameter from TS 44.018) + + 2\*( Power Level field in the BS POWER message) + +Example:        If Power Level is "0010" then +                     RXLEV-FULL-SERVING-CELL (parameter in Measurement Results) +                     = RXLEV-FULL-SERVING-CELL (parameter from TS 44.018) + (2\*2) + +## 5.13 (void) + +## 5.14 Cause IE + +This element contains the cause value. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Cause value | | | | | | | | octet 2 | + +Figure 5.14.1: Cause IE + +The cause field is coded as follows: + +Table 5.14.1: Cause IE coding + +| | | +|---------------------------------|----------------------------------------------| +| 0000 0000 | Congestion | +| 0000 0001 | Channel Mode not supported | +| 0000 0010 | Positioning procedure not supported | +| 0000 0011 | Failure for other radio related events | +| 0000 0100 | Intra-BSS handover | +| 0000 0101 | Supervision Timer Expired | +| 0000 0110 | Inter-BSS handover | +| 0000 0111 | Loss of signalling connection to MS | +| 0000 1000 | Incorrect serving cell identity | +| 0000 1001 | BSSAP-LE Segmentation error | +| 0000 1010 | Concurrent Positioning Procedure not enabled | +| All unassigned codes are spare. | | + +## 5.15 RRLP Flag IE + +This element is coded as: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|-------|---------|---------| +| Element identifier | | | | | | | | octet 1 | +| SPARE | | | | | | Flag1 | octet 2 | | + +Figure 5.15.1: RRLP Flag IE + +The fields are coded as follows: + +Flag 1 (Octet 2, bit 1): + +- 0 Position Command (SMLC to BSC) or final response (BSC to SMLC). +- 1 Not a Positioning Command or final response. + +## 5.16 RRLP IE + +RRLP IE is coded as: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2-3 | +| RRLP APDU (3GPP TS 44.031) | | | | | | | | octet 4-n | + +Figure 5.16.1: RRLP IE + +## 5.17 Cell Identity List IE + +This element defines the list of cell identities of neighbour cells, for which measurements are reported. The Cell Identities are listed in the same order than the corresponding measurements in the (Enhanced) Measurement Report IE. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-----------------------|---|---|---|-------------------------------------|---|---|---|------------------|--|--|--|--| +| Element identifier | | | | | | | | octet 1 | | | | | +| Length | | | | | | | | octet 2 | | | | | +| Spare | | | | Cell identification Discriminator 1 | | | | octet 3 | | | | | +| Cell Identification 1 | | | | | | | | octet 4 to (4+p) | | | | | +| ... | | | | | | | | | | | | | +| Spare | | | | Cell identification Discriminator N | | | | octet (n-q-1) | | | | | +| Cell Identification N | | | | | | | | octet (n-q) to n | | | | | + +**Figure 5.17.1: Cell Identity IE** + +The coding of octet 2 is a binary number indicating the Length of the remaining element. The Length depends on the Cell identification discriminator i as well as the number of cells to be identified. + +The Cell identification discriminator i is coded as follows: + +| | | +|------|------------------------------------------------------------------------------------| +| 0000 | The whole Cell Global Identification, CGI, is used to identify the 2G cells. | +| 0001 | Location Area Code, LAC, and Cell Identity, CI, are used to identify the 2G cells. | +| 0010 | 3G Cell identification container 1. | +| 0011 | 3G Cell identification container 2. | + +All other values are reserved. + +The coding of the Cell Identification i depends on the Cell identification discriminator i. Below the coding of the i-th Cell Identification is shown for each Cell identification discriminator (with "i" in the range 1 to n): + +Coding of the i-th Cell Identification for Cell identification discriminator = 0000. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|---------------|---|---|---|-----------|---|---|---|-----------|--|--|--|--| +| MCC dig 2 | | | | MCC dig 1 | | | | octet x+1 | | | | | +| MNC dig 3 | | | | MNC dig 3 | | | | octet x+2 | | | | | +| MNC dig 2 | | | | MNC dig 1 | | | | octet x+3 | | | | | +| LAC | | | | | | | | octet x+4 | | | | | +| LAC cont. | | | | | | | | octet x+5 | | | | | +| CI value | | | | | | | | octet x+6 | | | | | +| CI value cont | | | | | | | | octet x+7 | | | | | + +**Figure 5.17.2: Cell identification for discriminator = 0000** + +The octet (x+2) bits 5-8 are filled by '1111' if 2 digit MNC is used. + +The octets (x+1)-(x+5) are coded as the value part shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+6)-(x+7) are coded as the value part shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +Coding of i-th Cell Identification for Cell identification discriminator = 0001. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------|---|---|---|---|---|---|---|-----------| +| LAC | | | | | | | | octet x+1 | +| LAC cont. | | | | | | | | octet x+2 | +| CI value | | | | | | | | octet x+3 | +| CI value cont | | | | | | | | octet x+4 | + +**Figure 5.17.3: Cell identification for discriminator = 0001** + +The octets (x+1)-(x+2) are coded as the value part shown in 3GPP TS 24.008, Table 'Location Area Identification information element'. + +The octets (x+3)-(x+4) are coded as the value part shown in 3GPP TS 24.008, Table 'Cell Identity information element'. + +Coding of the Target ID for Cell identification discriminator = 0010. + +Octets (x+1) to (x+9) shall be ignored by the receiver. + +NOTE: in the 3G Cell identification container 1, the transmitter may send PLMN-ID, LAC, RNC-ID and C-ID to identify a 3G cell. + +Coding of the Target ID for Cell identification discriminator = 0011. + +Octets (x+1) to (x+6) shall be ignored by the receiver. + +NOTE: In the 3G Cell identification container 2, the transmitter may send LAC, RNC-ID and C-ID to identify a 3G cell. + +## 5.18 Enhanced Measurement Report IE + +This element contains the measurement report from the BSS. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Enhanced Measurement Results | | | | | | | | octet 3-n | + +**Figure 5.18.1: Enhanced Measurement Report IE** + +The Enhanced Measurement Results field is encoded as the contents of the ENHANCED MEASUREMENT REPORT message in 3GPP TS 44.018 (excluding the fields: "RR short PD", "Message type" and "Short layer 2 header") with the changes specified below. + +RXLEV\_VAL for serving cell + +When the values of RXLEV\_VAL from TS 44.018 is 0 or 63, then its value shall be encoded to the Enhanced Measurement Results without change. Otherwise, the value of RXLEV\_VAL shall be added with 2 times the power reduction value corresponding to the Power Level field in the BS POWER message in 3GPP TS 48.058. A result higher than the upper boundary shall be limited to 63 to avoid value out of range. + +$$\begin{aligned} & \text{RXLEV\_VAL (parameter in Enhanced Measurement Results)} \\ &= \text{RXLEV\_VAL (parameter from TS 44.018 in section 9.1.55)} \\ &+ 2 * (\text{Power Level field in the BS POWER message}) \end{aligned}$$ + +Example: If Power Level is "0010" then +RXLEV\_VAL (parameter in Enhanced Measurement Results) += RXLEV\_VAL (parameter from TS 44.018) + (2\*2). + +## 5.19 Location Area Code IE + +This element defines the cell identity of the MS serving cell. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|-----------| +| Element identifier | | | | | | | | octet 1 | +| Location Area Code | | | | | | | | octet 2-3 | + +**Figure 5.19.1: Location Area Code IE** + +The coding of the Location Area Code field is as defined in 3GPP TS 24.008 (excluding IEI, MCC, and MNC). + +## 5.20 Frequency List IE + +The Frequency List IE contains a list of frequencies used by the MS. + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|------------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | octet 1 | | +| Length | | | | | | | octet 2 | | +| Frequency List | | | | | | | octets 3-n | | + +**Figure 5.20.1: Frequency List IE** + +The coding of Frequency List field is as defined in 3GPP TS 44.018 (excluding IEI and length field). + +## 5.21 MS Power IE + +This element contains the MS power. + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | octet 1 | | +| MS Power | | | | | | | octet 2 | | + +**Figure 5.21.1: MS Power IE** + +The MS Power field is encoded as in 3GPP TS 44.018 (excluding IEI) and 3GPP TS 45.005. + +## 5.22 Delta Timer IE + +This element contains the value of the delta timer. The coding is as follows. + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | octet 1 | | +| Timer Value | | | | | | | octet 2 | | + +**Figure 5.22.1: Delta Timer IE** + +The Timer Value field is expressed in units of 0,1s. + +## 5.23 Serving Cell Identifier IE + +This element uniquely identifies a cell within a BSS and is of variable length containing the following fields: + +| | | | | | | | | | +|---------------------|---|---|---|-----------------------------------|---|---|-----------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | octet 1 | | +| Length | | | | | | | octet 2 | | +| Spare | | | | Cell identification discriminator | | | | octet 3 | +| Cell identification | | | | | | | octet 4-n | | + +**Figure 5.23.1: Serving Cell Identifier IE** + +The Serving Cell Identifier IE is encoded as in 3GPP TS 48.008 (excluding IEI and length field). + +## 5.24 Encryption Key IE + +This element defines the encryption key (Kc) of the MS being located. + +| | | | | | | | | | +|---------------------|---|---|---|---|---|---|-----------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | octet 1 | | +| Encryption Key (Kc) | | | | | | | octet 2-9 | | + +**Figure 5.24.1: Encryption Key IE** + +The Encryption Key (Kc) field contains the ciphering key to be used in connection with the encryption algorithms A5/1 and A5/3 as provided to the BSS by the MSC in the Encryption Information IE and as defined in TS 48.008. + +## 5.25 Cipher Mode Setting IE + +The purpose of the Cipher Mode Setting information element is to indicate whether stream ciphering shall be started or not and if it is to be started, which algorithm to use. + +| | | | | | | | | | +|--------------------|------------------|---|---|----------------------|---|---|----|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | Ciph Mod Set IEI | | | algorithm identifier | | | SC | octet 2 | + +**Figure 5.25.1: Cipher Mode Setting IE** + +The Cipher Mode Setting information element is coded as defined in TS 44.018 (excluding IEI). + +## 5.26 Channel Mode IE + +The purpose of the Channel Mode information element is to indicate the mode on coding/decoding and transcoding. + +| | | | | | | | | | +|--------------------|---|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Mode | | | | | | | | octet 2 | + +**Figure 5.26.1: Channel Mode IE** + +The Channel Mode information element is coded as defined in TS 44.018 (excluding IEI). + +## 5.27 MultiRate Configuration IE + +The purpose of the MultiRate Configuration information element is to provide all parameters relevant to multi-rate speech codec. + +| | | | | | | | | | +|---------------------------------|---|----------|------|-------|---|------------|---|-------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Length | | | | | | | | octet 2 | +| Multirate speech version | | NSC
B | ICMI | Spare | | Start mode | | octet 3 | +| Parameters for multirate speech | | | | | | | | octet 4 - n | + +**Figure 5.27.1: MultiRate Configuration IE** + +The MultiRate Configuration information element is coded as defined in TS 44.018 (excluding IEI). + +## 5.28 Polling Repetition IE + +This element contains the value of the number of repetitions of the Packet Polling Request procedure. The coding is as follows: + +| | | | | | | | | | +|--------------------|----------------------------------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | | octet 1 | +| Spare | Number of polling repetitions (binary) | | | | | | | octet 2 | + +**Figure 5.26.1: Polling Repetition IE** + +The Polling Repetition IE is a binary representation in the range of 4-63. + +## 5.29 Packet Channel Description IE + +This element contains the timeslot allocation and frequency parameters. The coding is as follows. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|------------| +| Element identifier | | | | | | | | octet 1 | +| CSN.1 binary representation of the channel parameters as described in TS 44.018 (CCCH) or TS 44.060 (PCCCH) plus padding bits (binary 0) as required to achieve 4 complete octets | | | | | | | | octets 2-5 | + +Figure 5.29.1: Packet Channel Description IE + +## 5.30 TLLI IE + +The purpose of the *TLLI* information element is to provide the Temporary Logical Link Identifier. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|---|---|---|---|---------| +| Element Identifier | | | | | | | | octet 1 | +| TLLI value | | | | | | | | octet 2 | +| TLLI value (contd) | | | | | | | | octet 3 | +| TLLI value (contd) | | | | | | | | octet 4 | +| TLLI value (contd) | | | | | | | | octet 5 | + +Figure 5.30.1: TLLI IE + +The TLLI information element is coded as defined in TS 44.018 (excluding IEI). + +## 5.31 TFI IE + +This element contains the value of the TFI. The coding is as follows. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-----|---|---|---|---------| +| Element identifier | | | | | | | | octet 1 | +| Spare | | | | TFI | | | | octet 2 | + +Figure 5.31.1: TFI IE + +The TFI information element is coded as defined in TS 44.060 (excluding IEI). + +## 5.32 Starting Time IE + +The purpose of the *Starting Time* information element is to provide the start TDMA frame number, FN modulo 42432 of the first transmission of the Packet Polling Request or first block of user data associated with the U-TDOA location method from the BSS to the MS. In the case that the power-up procedure for U-TDOA is supported, the *Starting Time* information element may provide the starting frame number of the power-up and DTX suspension. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------|---|---|---|-------------------|---|---|---|---------| +| Element Identifier | | | | | | | | octet 1 | +| T1' | | | | T3
(high part) | | | | octet 2 | +| T3
(low part) | | | | T2 | | | | octet 3 | + +Figure 5.32.1: Starting Time IE + +The Starting Time information element is coded and interpreted as defined in TS 44.018 (excluding IEI). + +## 5.33 Long Encryption Key IE + +This element defines the 128 bit encryption key (Ke128) of the MS being located. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------|---|---|---|---|---|---|---|------------| +| Element identifier | | | | | | | | octet 1 | +| Long Encryption Key (Ke128) | | | | | | | | octet 2-17 | + +Figure 5.24.1: Long Encryption Key IE + +The Long Encryption Key (Kc128) field contains the ciphering key to be used in connection with encryption algorithm A5/4 as provided to the BSS by the MSC as defined in TS 48.008. + +## 5.34 Concurrent Positioning Flag + +This element contains the current BSC capability of the second, concurrent, independent location method. The coding is as follows: + +| | | | | | | | | | +|------------------------|---|---|---|---|---|---|---------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Element identifier | | | | | | | Octet 1 | | +| Concurrent Method Flag | | | | | | | Octet 2 | | + +**Figure 5.34.1: Concurrent Positioning IE** + +**Table 5.34.1: Concurrent Method Flag Coding** + +| Coding | Element name | +|---------------------------------|------------------------------------------------------| +| 0000 0000 | Second independent concurrent positioning Allowed | +| 1111 1111 | Second independent concurrent positioning Disallowed | +| NOTE: All other values reserved | | + +The combinations of first and second location procedures in concurrent positioning are limited to the following: + +**Figure 5.34.2 Allowed Concurrent Positioning Procedures** + +| First Location Procedure | Second Location Procedure | +|--------------------------|---------------------------| +| TA Positioning | MS Positioning | +| UTDOA Positioning | MS Positioning | +| MS Positioning | TA Positioning | +| MS Positioning | U-TDOA Positioning | + +# --- Annex A (informative): Change History + +| Meeting/Date | Tdoc | CR | Rev | Subject/Comment | New version | +|--------------|------|----|-----|----------------------------------------|-------------| +| January 2016 | | | | Version 13.0.0 based on version 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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/48_series/48103/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Rel-16/48_series/48103/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9190440ad8d0e837516a413419081a737fdd41e2 --- /dev/null +++ b/marked/Rel-16/48_series/48103/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1facfae1c019afb1f0beab5230397d77a3ec4553b9bfc504fdb771a6407b746 +size 8588 diff --git a/marked/Rel-16/48_series/48103/21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg b/marked/Rel-16/48_series/48103/21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7acf5b85f96ee88ba2ecb597eff44f90eab6ef2 --- /dev/null +++ b/marked/Rel-16/48_series/48103/21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75de2c2f42a371429772d1c7723b2550a5c381721ccc6eddaf2741201d7ad6ff +size 14612 diff --git a/marked/Rel-16/48_series/48103/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-16/48_series/48103/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a96ae1e49fe5946dd2ee9bcc116e39bbe38abad --- /dev/null +++ b/marked/Rel-16/48_series/48103/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b656bb83ba92dde6ac100d05476145d4464cf9c674392cfd8853b345f854a112 +size 47246 diff --git a/marked/Rel-16/48_series/48103/95cd9f56a54683029052b8c644228506_img.jpg b/marked/Rel-16/48_series/48103/95cd9f56a54683029052b8c644228506_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2de0029961b3f8c145637389894a130a87aa1a0c --- /dev/null +++ b/marked/Rel-16/48_series/48103/95cd9f56a54683029052b8c644228506_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f1aee4e1ee4df1e527999cfdf76489860f7689ceec89aaa0cd356f7793e7f6c +size 35517 diff --git a/marked/Rel-16/48_series/48103/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-16/48_series/48103/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84416d7fe5f7e58dd54adb76249ae3382b0b53ec --- /dev/null +++ b/marked/Rel-16/48_series/48103/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35120aa89844544277c45985363038f33da29cf95c3ae928714ecb32cb87582f +size 49567 diff --git a/marked/Rel-16/48_series/48103/f76f0f5dfff2511b51f6b875867c029f_img.jpg b/marked/Rel-16/48_series/48103/f76f0f5dfff2511b51f6b875867c029f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c024413bb3a5f64c04c464e84625448af1d68f22 --- /dev/null +++ b/marked/Rel-16/48_series/48103/f76f0f5dfff2511b51f6b875867c029f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f335b4d6b74147c82fa08e24717b85784df60db9100f7d2e20243ffe353a0081 +size 31844 diff --git a/marked/Rel-16/48_series/48103/raw.md b/marked/Rel-16/48_series/48103/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..90dc28159e9e2d2cd22cb1f0f8962d8e8aaf51eb --- /dev/null +++ b/marked/Rel-16/48_series/48103/raw.md @@ -0,0 +1,712 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Transport over TDM..... | 7 | +| 4.1 General ..... | 7 | +| 4.2 Transport during local switching..... | 7 | +| 5 Transport over IP ..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 IP ..... | 8 | +| 5.3 UDP..... | 8 | +| 5.4 Transport without RTP multiplexing ..... | 8 | +| 5.4.1 Introduction ..... | 8 | +| 5.4.2 RTP..... | 8 | +| 5.4.2.1 RTP Header..... | 9 | +| 5.4.2.1.1 Version ..... | 9 | +| 5.4.2.1.2 Padding..... | 9 | +| 5.4.2.1.3 Extension..... | 9 | +| 5.4.2.1.4 Contributing Source (CSRC) count..... | 9 | +| 5.4.2.1.5 Marker Bit ..... | 9 | +| 5.4.2.1.6 Payload Type..... | 9 | +| 5.4.2.1.7 Sequence Number ..... | 9 | +| 5.4.2.1.8 Timestamp..... | 9 | +| 5.4.2.1.9 Synchronisation Source (SSRC) ..... | 9 | +| 5.4.2.1.10 CSRC list..... | 10 | +| 5.4.2.2 RTP Payload ..... | 10 | +| 5.4.2.3 RTP Packetization Time ..... | 10 | +| 5.4.3 RTCP ..... | 10 | +| 5.5 Transport with RTP multiplexing ..... | 11 | +| 5.5.1 Introduction ..... | 11 | +| 5.5.2 RTP..... | 11 | +| 5.5.2.1 Transport format for multiplexing without RTP header compression..... | 11 | +| 5.5.2.2 Transport format for multiplexing with RTP header compression..... | 12 | +| 5.5.3 RTCP ..... | 13 | +| 5.5.3.1 General..... | 13 | +| 5.5.3.2 Multiplexing negotiation via RTCP..... | 13 | +| 5.5.3.3 RTCP Multiplexing packet ..... | 14 | +| 5.6 Transport of CSData..... | 16 | +| 5.6.1 Introduction ..... | 16 | +| 5.6.2 Transport formats for CSData ..... | 17 | +| 5.6.2.1 Transport format for CSData without redundancy ..... | 17 | +| 5.6.2.2 Transport format for CSData with redundancy ..... | 18 | +| 5.6.2.3 Start and Stop of RTP streams with redundancy ..... | 19 | +| 5.7 Transport during local switching..... | 20 | +| Annex A (informative): Change History..... | 20 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document specifies the User Plane data transport protocols used between BSSs and the Core Network (MGWs) across the A interface. The main purpose of the present document is the AoIP description, however for the sake of completeness the AoTDM case is described as well. + +![Figure 1.1: CS core network logical architecture diagram showing connections between UTRAN/GERAN (lu mode), GERAN A/Gb mode, MGW, MSC server, and GMSC server. Solid lines represent Signalling and Data Transfer Interfaces (lu, A, Nb, Nc), while dashed lines represent Signalling Interfaces (Mc).](f76f0f5dfff2511b51f6b875867c029f_img.jpg) + +The diagram illustrates the CS core network logical architecture. At the top left, a box labeled 'UTRAN \ GERAN lu mode' is connected via a solid line labeled 'lu' to an 'MGW' box. Below it, a box labeled 'GERAN A/Gb mode' is connected via a solid line labeled 'A' to an 'MSC server' box. Both the 'lu' and 'A' lines have a dashed line (Signalling Interface) running parallel to them. The 'MGW' box is connected to another 'MGW' box via a solid line labeled 'Nb'. The 'MSC server' box is connected to a 'GMSC server' box via a solid line labeled 'Nc'. There are dashed lines (Signalling Interfaces) labeled 'Mc' connecting the 'MGW' box to the 'MSC server' box, and another 'Mc' line connecting the second 'MGW' box to the 'GMSC server' box. A legend at the bottom left indicates that a dashed line represents a 'Signalling Interface' and a solid line represents a 'Signalling and Data Transfer Interface'. + +Figure 1.1: CS core network logical architecture diagram showing connections between UTRAN/GERAN (lu mode), GERAN A/Gb mode, MGW, MSC server, and GMSC server. Solid lines represent Signalling and Data Transfer Interfaces (lu, A, Nb, Nc), while dashed lines represent Signalling Interfaces (Mc). + +**Figure 1.1: CS core network logical architecture** + +Note that the present document does not preclude any Core Network Session Control Protocol implementation (BICC or SIP-I). + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] IETF RFC 791: "Internet Protocol (IP)". +- [3] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6)". +- [4] IETF RFC 768: "User Datagram Protocol. (UDP)". +- [5] IETF RFC 3550: "RTP: A Transport Protocol for Real Time Applications". +- [6] 3GPP TS 29.414: "Core network Nb Interface data transport and transport signalling". +- [7] IETF RFC 3551: "RTP Profile for Audio and Video Conference with Minimal Control". +- [8] 3GPP TR 29.814: "Feasibility Study on Bandwidth Savings at Nb Interface with IP transport". +- [9] IETF RFC 4040: "RTP Payload Format for a 64 kbits/s Transparent Call" +- [10] IETF RFC 4867: "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs" +- [11] IETF RFC 2198: "RTP Payload for redundant Audio Data" + +- [12] 3GPP TR 43.903 A-Interface over IP Study (AINTIP) +- [13] 3GPP TS 48.001 "Base Station System – Mobile-services Switching Centre (BSS - MSC) interface; General aspects" +- [14] ITU-T Recommendation G.705: "Characteristics of plesiochronous digital hierarchy (PDH) equipment functional blocks". +- [15] ANSI T1.102-1993: "Digital Hierarchy - Electrical Interface". +- [16] ITU-T Recommendation G.711: "Pulse Code Modulation (PCM) of voice frequencies". +- [17] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [18] IETF RFC 5993 (2010) "RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)". +- [19] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [20] 3GPP TS 26.102: "Adaptive Multi-Rate (AMR) speech codec; Interface to Iu, Uu and Nb". +- [21] 3GPP TS 23.284: "Local Call Local Switch; Stage 2". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. + +Intra-BSS call: A mobile to mobile voice call involving two mobile stations connected to the same BSS. + +Local call: An Intra-BSS call that can be locally switched by the BSS. For details on the Local Switch Service see 3GPP TS 23.284 [21]. + +Access MGW: The MGW interfacing to the Radio Access Network + +## 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]. + +| | | +|--------|-----------------------------------------------------------------| +| AoIP | A (interface) over IP | +| AoTDM | A (interface) over TDM | +| APP | APplication | +| BICC | Bearer Independent Call Control | +| BSS | Base Station Subsystem | +| CS | Circuit-Switched | +| CSData | CS Data and fax | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| ITU-T | International Telecommunications Union-Telecommunication sector | +| MGW | Media GateWay | +| PCM | Pulse-Coded Modulation | +| RFC | Request For Comment | +| RTP | Real-Time Transport Protocol | +| RTCP | Real-Time Transport Control Protocol | +| SIP-I | Session Initiation Protocol with encapsulated ISUP | +| SSRC | Synchronisation Source | + +| | | +|-----|----------------------------| +| SVC | Switched Virtual Circuit | +| TDM | Time-Division Multiplexing | +| UDP | User Datagram Protocol | +| UP | User Plane | + +# 4 Transport over TDM + +## 4.1 General + +The present chapter describes the transport on the A Interface UP over E1/T1 interface; for more information see 3GPP TS 48.001 [13]. Figure 4.1 shows the protocol stack for the transport network user plane on the A interface. + +![](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +| | +|-------------------------------------------| +| Payload
(PCM encoded speech or CSData) | +| E1 or T1 | + +**Figure 4.1: TDM Protocol stack for the A interface user plane** + +Layer 1 shall utilise digital transmission: + +- at a rate of 2 048 kbit/s with a frame structure of 32 x 64kbit/s time slots, as specified in ITU-T Recommendation G.705 [14] clause 3 for E1 interface; or +- at a rate of 1 544 kbit/s with a frame structure of 24 x 64 kbit/s time slots, as specified in T1.102 specification for T1 interface [15]. + +The payload is either PCM encoded speech (see ITU-T Recommendation G.711 [16]) or CSData (see 3GPP TS 48.020 [17]). + +## 4.2 Transport during local switching + +When a local switch path is established in the BSS for a local call, the user plane between the BSS and the Access MGWs for both the call legs in uplink and downlink shall not be released. + +# 5 Transport over IP + +## 5.1 General + +The present chapter describes the transport of the A-Interface User Plane Payload by RTP/UDP/IP. Figure 5.1 shows the protocol stack. + +![](21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg) + +| | +|------------------------------------------------------------| +| Payload (PCM-coded speech, or compressed speech or CSData) | +| RTP | +| UDP | +| IPv4 or IPv6 | + +**Figure 5.1: IP Protocol stack for the A-Interface user plane** + +The specific carrying way at physical/link layer of the IP protocol is not limited by the present document; if Ethernet is adopted, link layer will be MAC protocol while if IPoE1 or POS is adopted, link layer will be PPP protocol. Nevertheless at least Ethernet should be supported. + +## 5.2 IP + +IPv4 (RFC 791 [2]) shall be supported + +IPv6 (RFC 2460 [3]) may be supported as an option. + +One BSS/MGW pair may be connected via several IP interfaces. + +## 5.3 UDP + +The UDP Protocol (see RFC 768 [4]) shall be applied. + +Two consecutive port numbers shall be used at each BSS/MGW for the RTP connection and for the optional RTCP connection that corresponds to a single A interface UP connection. Two such consecutive port numbers are termed "port number block" in what follows. The first port number shall be even and shall be assigned to the RTP protocol. For a given BSS/MGW, the same port shall be used to send and to receive RTP PDUs. The next port number shall be assigned to the RTCP protocol. This port shall be reserved even if the optional RTCP protocol is not used. + +If multiplexing is applied with or without header compression, 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. The negotiation of whether multiplexing is applied and of the destination UDP port is described in sub-clause 5.5.3.2. If multiplexing was negotiated for an A interface UP user plane connection, the BSS/MGW may apply multiplexing by sending all packets of the user plane connection (multiplexed with other user plane connections packets) towards the negotiated destination UDP port. + +## 5.4 Transport without RTP multiplexing + +### 5.4.1 Introduction + +User Plane transport without RTP multiplexing is default and shall be supported. It shall be applied after call setup, until a User Plane transport with RTP-multiplexing is negotiated via RTCP, see clause 5.5. RTCP, see RFC 3550 [5] may be applied in AoIP, it is optional. A BSS or MSC may ignore incoming RTCP packets on AoIP. + +### 5.4.2 RTP + +The RTP protocol (see RFC 3550 [5]) shall be applied. + +#### 5.4.2.1 RTP Header + +The RTP Header Fields shall be used as described in the following sub-clauses: + +##### 5.4.2.1.1 Version + +RTP Version 2 shall be used. + +##### 5.4.2.1.2 Padding + +Padding shall not be used. + +##### 5.4.2.1.3 Extension + +The RTP Header extension shall not be used. + +##### 5.4.2.1.4 Contributing Source (CSRC) count + +There is zero CSRC. + +##### 5.4.2.1.5 Marker Bit + +The marker bit shall be used as specified for the RTP profile applicable for the used payload. If AMR or AMR-WB speech is received via the GSM radio interface, then an ONSET frame precedes the first speech frame. This ONSET Frame is transported in a separate RTP packet and shall also have the Marker Bit set to "1". Also the next RTP packet, which contains the first speech frame of the talkspurt, shall have the Marker Bit set to "1". In case of lost speech frames due to radio errors or due to FACCH frame stealing the Marker bit shall not be set in the first speech frame after that interruption. + +##### 5.4.2.1.6 Payload Type + +See sub-clause 5.4.2.2. + +##### 5.4.2.1.7 Sequence Number + +The sequence number shall be supplied by the source (BSS or MGW) of an RTP packet. RTP sequence numbering is based on sent RTP packets, not on expected speech frames. If frames are lost or stolen on the radio interface and the codec does not support Bad or No\_Data frame types, no RTP packet is sent in uplink direction and the RTP Sequence Number is not incremented, until a next frame is sent in RTP. This ensures that the receiver of the RTP stream can detect lost RTP packets by inspecting the RTP Sequence Number. + +##### 5.4.2.1.8 Timestamp + +The timestamp shall be supplied by the source (BSS or MGW) of a RTP PDU. Depending of the (pseudo) codec used a clock frequency of either 8 or 16 kHz shall be used, as described in sub-clause 5.4.2.2. In case of lost or stolen frames on the radio interface or in case of an interruption of the RTP stream due to handover, the RTP Timestamp shall be incremented as if no frame would have been lost. This ensures that the receiver of the RTP stream can regenerate the time signal correctly. + +NOTE: IETF RFC 3550 [5] specifies that the RTP timestamp is based on the sampling instant of the source Encoder. In case of a circuit switched radio interface the source Encoder for the uplink is within the mobile station. But the radio interface does not support the transfer of a RTP Timestamp. The clock synchronisation between mobile station and BSS is, however, very precise and so the BSS can take the role of the source Encoder and provide the RTP time stamp. + +##### 5.4.2.1.9 Synchronisation Source (SSRC) + +The source (BSS or MGW) of a RTP PDU shall supply a SSRC. The receiver of a RTP PDU may ignore the SSRC if it does not use RTCP. + +##### 5.4.2.1.10 CSRC list + +This list is empty, i.e. not present. + +#### 5.4.2.2 RTP Payload + +The packing of the RTP Payload for each Speech Codec Type is specified in TS 26.102 [20]. + +When defined as such by IETF for a given Speech Codec (see RFC 3550 [5]) and RFC 3551 [7]) the "Static" Payload Type is used; otherwise for RTP profiles for which IETF defines the Payload Type as "Dynamic" (e.g. for AMR codecs, see RFC4867 [10]) a fixed Payload Type is defined for AoIP in the range of the dynamic Payload Types, see below. + +The mapping between transported RTP payloads and their associated Payload Type is as follows: + +**Table 5.4.2.2.1: Type of data transported versus RTP Payload Type** + +| Type of data transported | | RTP Payload Type | Clock frequency | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------------------------------------------| +| PCM μ-law encoded speech (G.711) | | 0 (see RFC 3551 [7]) | 8 kHz (see RFC 3551 [7]) | +| PCM A-law encoded speech (G.711) | | 8 (see RFC 3551 [7]) | 8 kHz (see RFC 3551 [7]) | +| Compressed Speech | GSM FR codec (3GPP TS 46.010) | 3 (see RFC 3551 [7]) | 8 kHz (see RFC 3551 [7]) | +| | GSM EFR codec (3GPP TS 46.060) | 110 | 8 kHz (see RFC 3551 [7]) | +| | GSM HR codec (3GPP TS 46.020) | 111 | 8 kHz (see [18]) | +| | Narrow Band AMR codecs (i.e. FR AMR, HR AMR and OHR AMR codecs) (3GPP TS 29.190) | 112 | 8 kHz (see RFC4867 [10]) | +| | Wide Band AMR codecs (i.e. AMR-WB, OFR AMR-WB and OHR AMR-WB codecs) (3GPP TS 29.190) | 113 | 16 kHz (see RFC4867 [10]) | +| CSData (Clear Mode pseudo-codec – see RFC 4040 [9]) | Without RTP redundancy (redundancy level = 1) (3GPP TS 48.008 and TS 48.020) | 120 | 8 kHz (see RFC 4040 [9]) | +| | With RTP redundancy (redundancy level = 2 or 3) (3GPP TS 48.008 and TS 48.020)
See sub-clause 5.6 for the format description | 121 | 8 kHz (see RFC 4040 [9] and RFC 2198 [11]) | + +#### 5.4.2.3 RTP Packetization Time + +The RTP Packetization Time is not negotiated for AoIP, but set to a predefined fixed value, see TS 26.102 [20]. + +For compressed speech on the A-Interface the Packetization Time is identical to the Speech Frame length and that is 20ms for all 3GPP Codec Types. + +For PCM-coded speech (ITU-T G.711, A-law and μ-law) the Packetization Time is predefined to 20ms for AoIP. + +For CSData the Packetization Time is predefined to 20ms, when no redundancy is used. In case of RTP Redundancy more than one consecutive data block are included in one RTP packet. But for each of these data blocks the Packetization Time is predefined to 20ms. + +### 5.4.3 RTCP + +RTCP (see RFC 3550 [5]) may be applied. The use of the RTCP protocol is optional. + +A BSS/MGW may ignore incoming RTCP PDUs. + +## 5.5 Transport with RTP multiplexing + +### 5.5.1 Introduction + +This sub-clause specifies an optional transport format for the A interface and IP transport that allows transporting several RTP payload PDUs of different user plane connections within one UDP/IP packet, and the corresponding backward compatible signalling extensions required to negotiate the use of this transport option. Use of this transport format saves bandwidth in the IP network (bandwidth gains for the Nb interface are evaluated in 3GPP TR 29.814 [8]). + +Bandwidth saving is achieved by multiplexing several RTP payload PDUs within one UDP/IP packet. As an option, the RTP header may be compressed in addition. Two transport formats are specified accordingly. + +As specified in sub-clause 5.5.3.1 RTP multiplexing shall not be applied if RTP redundancy has been negotiated. + +### 5.5.2 RTP + +#### 5.5.2.1 Transport format for multiplexing without RTP header compression + +Several RTP payload PDUs sent to the same IP address are multiplexed within one single UDP/IP packet over the A interface. If DiffServ is applied, all multiplexed PDUs also need to share the same Diffserv class. The multiplexing shall only be used with RTP packets. RTCP shall be transported normally by UDP/IP packets. + +Use of multiplexing shall be negotiated between BSS and MGW, as specified in sub-clause 5.5.3.2. + +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 non-multiplexed PDU) /2 | | | | | | | 2 | Multiplex Header | | | | | | | | +| Length Indicator (LI) = n | | | | | | | | | | | | | | | | | +| R | Source ID =
(Source UDP Port of non-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 5.5.2.1.1: UDP/IP Packet with multiplexed RTP payload PDUs without RTP header compression** + +The Multiplex Header includes: + +- T bit. + +The field has two possible values, 0 for indicating full packet and 1 for indicating compressed packet. Value 0 shall be used for an uncompressed RTP header, as described in the present sub-clause. + +- 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 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 Payload) 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 calculating 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 PDU packet divided by two (only even numbered ports are used for RTP sessions). This information is transferred to permit the receiving node to optionally detect and filter illegitimate packets (e.g. packets received from the peer termination previously associated to the receiving termination). + +The multiplexed RTP payload PDU shall be inserted in the IP/UDP packet directly after the corresponding Multiplex Header. The multiplexed RTP payload PDU shall consist of the full RTP header and the RTP payload. If the multiplexed RTP payload PDU does not end at a byte boundary, then the remaining bits of its last byte shall be padded with zeros. + +#### 5.5.2.2 Transport format for multiplexing with RTP header compression + +To achieve even better bandwidth savings, the RTP header may optionally be compressed. This is possible since the RTP header includes many static fields that remain unchanged during an RTP session (see sub-clause 5.4.2.). + +Use of RTP header compression shall be negotiated between BSS and MGW, as specified in sub-clause 5.5.3.2. + +At least the first two RTP packets of each RTP session shall be sent with their full RTP header to allow the receiver to store the full header and use it in decompression. RTP packets shall also be sent with their full RTP header till receipt of a RTCP packet from the peer indicating support of RTP header compression. Subsequent packets may be sent with a compressed RTP header. If a BSS/MGW does not receive any of the initial RTP packets with a full RTP header, the BSS/MGW shall assume that the fields of the RTP header other than those present in the compressed RTP header are set as defined in sub-clause 5.4.2, and shall therefore not consider this as an error. + +Before each multiplexed RTP 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 | | | | | | | | | +| Source IP, Dest IP, ... | | | | | | | 20/40 | IP | | | | | | | +| Source Port, Dest Port=, Length, ... | | | | | | | 8 | UDP | | | | | | | +| T=1 | Mux ID =
(Destination UDP Port of non-multiplexed PDU) / 2 | | | | | | 2 | Multiplex Header | | | | | | | +| | Length Indicator (LI) = n + 4 | | | | | | 1 | | | | | | | | +| R | Source ID =
(Source UDP Port of non-multiplexed PDU) / 2 | | | | | | 2 | | | | | | | | +| | Sequence Number (SN) | | | | | | 1 | Compressed RTP header | | | | | | | +| | Timestamp (TS) | | | | | | 2 | | | | | | | | +| M | Payload Type (PT) | | | | | | 1 | | | | | | | | +| | RTP payload | | | | | | n | RTP Payload | | | | | | | +| Multiplex Header | | | | | | | 5 | Multiplex Header | | | | | | | +| Compressed RTP header | | | | | | | 4 | Compressed RTP header | | | | | | | +| RTP payload | | | | | | | m | RTP payload | | | | | | | +| ... | | | | | | | | | | | | | | | + +**Figure 5.5.2.2.1: UDP/IP Packet with multiplexed RTP payload PDUs with RTP header compression** + +The Multiplex Header shall be used as described in sub-clause 5.4.3.2. However, the T bit shall be set for a compressed RTP header, as described in the present sub-clause. The Length Indicator gives the length of the multiplexed RTP PDU packet in bytes (compressed RTP header + RTP Payload). + +The multiplexed RTP payload PDU shall be inserted in the IP/UDP packet directly after the corresponding Multiplex Header. The multiplexed RTP payload PDU shall consist of the compressed RTP header described below followed by the full RTP payload, as for sub-clause 5.4.2.1. If the multiplexed RTP payload PDU does not end at a byte boundary, then the remaining bits of its last byte shall be padded with zeros. + +The compressed RTP header shall include the following fields taken from the uncompressed RTP header: + +- Sequence number (SN), 8 bits. + +The field is the least significant byte of the original RTP sequence number (RFC 3550 [29]), hence the sequence number is shortened from 16 bits to 8 bits (which allows to identify 256 consecutive packets). Sub-clause 5.4.2.1.7 is applicable. + +- Timestamp (TS), 16 bits. + +The TS field is the two least significant bytes of the original RTP timestamp (RFC 3550 [5]), hence the length is half of the original resulting in modulo of 8 seconds (resp 4 seconds) with 8 kHz (resp 16 kHz) clock reference. Sub-clause 5.4.2.1.8 is applicable. + +- Marker bit, 1 bit (see sub-clause 5.4.2) +- Payload Type, 7 bits (see sub-clause 5.4.2) + +NOTE: These RTP fields may change during a connection and thus need to be transferred within each packet for RTP payload. All other RTP fields do not change (see sub-clause 5.4.2). + +### 5.5.3 RTCP + +#### 5.5.3.1 General + +A BSS/MGW wishing to apply RTP multiplexing shall use RTCP (see RFC 3550 [5]) to negotiate multiplexing. + +RTCP shall be used separately for each user plane connection. RTCP shall be transported by UDP/IP packets as described in sub-clause 5.4.3. and not included in IP/UDP packets using the multiplexing format described above. + +Multiplexing negotiation shall not be performed for user plane connections for which RTP redundancy is used. + +#### 5.5.3.2 Multiplexing negotiation via RTCP + +RTCP shall be used to negotiate the use of multiplexing. A 3GPP-specific RTCP Multiplexing packet is specified in sub-clause 5.5.3.3. for this purpose, and may be sent as a non-compound RTCP packet. It may also be added to compound RTCP packets following the principles of RFC 3550 [5]. The Multiplexing RTCP packet indicates: + +- if multiplexing without RTP header compression is supported ; +- if multiplexing with RTP header compression is supported ; +- the local UDP port where to receive multiplexed data streams, +- if multiplexing is selected. + +When setting up a new user plane connection, both peer BSS and MGW of an UP connection shall start to send data without applying multiplexing and may indicate their readiness to receive multiplexed data streams by including the new RTCP Multiplexing packet in the initial and all subsequent RTCP packets they send. A BSS/MGW shall always announce the same multiplexing capabilities and the same UDP port where to receive multiplexed data streams in all the RTCP Multiplexing packets it sends for a given RTP session. BSS/MGW should preferably send their initial RTCP packet at the very beginning of the RTP session to be able to apply multiplexing as soon as possible, and may repeat it with shorter interval than regular RTCP transmission interval in the beginning to provide resilience against packet loss. A BSS/MGW sending a Multiplexing packet indicating support of multiplexing shall be ready to receive multiplexed packets at the announced UDP port. A single UDP port for multiplexing shall be used per destination IP address. + +A BSS/MGW receiving an RTCP packet, where the peer indicated its readiness to receive multiplexed data streams, may apply multiplexing to send the corresponding RTP data streams towards the sender of the RTCP packet. If the BSS/MGW decides to apply multiplexing, it can immediately start sending multiplexed data streams towards the corresponding UDP multiplexing port announced in the received RTCP Multiplexing packet. The BSS/MGW shall indicate in subsequent RTCP Multiplexing packets if it applies multiplexing with or without header compression for the given user connection + +A BSS/MGW that does not receive RTCP or receives RTCP without the RTCP Multiplexing packet shall continue to send data for the user connection without applying multiplexing. + +A BSS/MGW that does not support multiplexing will ignore the unknown received RTCP Multiplexing packet according to RTCP procedures and will continue to send data for the user connection without applying multiplexing. + +Sending of a RTCP Multiplexing packet indicating readiness to receive multiplexed data streams does not necessarily mean that the BSS/MGW is ready to send multiplexed data streams, i.e. multiplexing may be applied on a single or on both directions for a given RTP session. + +#### 5.5.3.3 RTCP Multiplexing packet + +The format of the RTCP Multiplexing packet is specified in figure 5.5.3.3.1. + +| Bits | | | | | | | | Number of Octets | | | | | | | | +|-------------------|-----------------------|-----------|---------|---------------|---|---|---|------------------|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | +| V=2 | | P | subtype | | | | | 1 | | | | | | | | +| PT=APP=204 | | | | | | | | 1 | | | | | | | | +| Length | | | | | | | | 2 | | | | | | | | +| SSRC/CSRC | | | | | | | | 4 | | | | | | | | +| Name(ASCII) | | | | | | | | 4 | | | | | | | | +| MUX | CP | Selection | | Reserved=0000 | | | | 2 | | | | | | | | +| Reserved=00000000 | | | | | | | | | | | | | | | | +| Reserved=0 | Local MUX UDP port /2 | | | | | | | 2 | | | | | | | | + +**Figure 5.5.3.3.1: RTCP Multiplexing packet** + +The APP packet header includes : + +- version (V), 2 bits + +Identifies the version of RTP, which is the same in RTCP packets as in RTP data packets. RTP Version 2 shall be used. + +- padding (P), 1 bit + +As specified in RFC 3550 [4]. + +- subtype, 5 bits. + +The following subtype value shall be used : + +00001 : RTCP Multiplexing packet + +- packet type (PT), 8 bits. + +Shall contains the constant 204 to identify this as an RTCP APP packet + +- length, 16 bits. + +As specified in RFC 3550 [4]. The length of this RTCP packet in 32-bit words minus one, including the header and any padding. (The offset of one makes zero a valid length and avoids a possible infinite loop in scanning a compound RTCP packet, while counting 32-bit words avoids a validity check for a multiple of 4.) + +- SSRC/CSRC, 32 bits. + +As specified in RFC 3550 [4]. + +- name, 32 bits. + +Shall be set to "3GPP" + +The application-dependent data includes : + +- multiplexing bit (MUX), 1 bit + +Indicates whether multiplexing without RTP header compression is supported or not by the sender of the RTCP packet : set to 0 if not supported, set to 1 if supported. + +- multiplexing with RTP header compression bit (CP), 1 bit + +Indicates whether multiplexing with RTP header compression is supported or not by the sender of the RTCP packet : set to 0 if not supported, set to 1 if supported. + +- Selection bits, 2 bits + +Indicates whether the sender of the RTCP packet has selected to apply multiplexing with or without header compression for the user plane packets that it sends on this connection. The following values are defined: + +00: no multiplexing is applied + +01: multiplexing is applied without RTP header compression + +10: multiplexing is applied with RTP header compression + +11: reserved + +- Local MUX UDP port, 15 bits : + +Local UDP port where the sender demands to receive multiplexed data streams. The value shall be the same as the local MUX UDP port divided by two. This parameter shall be ignored by the receiver of the RTCP Multiplexing packet if the MUX and CP bits indicate that multiplexing is not supported. + +- Reserved bits: + +Extension bits may be added in the RTCP Multiplexing packet in future releases. Reserved bits shall be set to 0 in sent RTCP Multiplexing packet of this release and shall be ignored in incoming RTCP Multiplexing packets. + +Extension fields may be added in the RTCP Multiplexing packet in future releases. They shall be ignored by a BSS/MGW implementing an earlier version of the specification. + +## 5.6 Transport of CSData + +### 5.6.1 Introduction + +The transport of Circuit Switched Data (CSData) across the A-Interface User Plane over IP uses per default no redundancy. A constant bit stream of 64kbps is transported in RTP packets, one every 20ms, with 160 octets payload each. RFC 4040 [9] is used as basis. It is expected that most IP networks provide a sufficiently low RTP packet loss rate and redundancy is not needed, because the errors introduced by the imperfect radio transmission dominate the service performance by far. + +![Diagram showing six RTP packets (RTP Packet 1 to 6) arranged in a 2x3 grid. Each packet contains a single data block (Data Block 1 to 6).](95cd9f56a54683029052b8c644228506_img.jpg) + +The diagram illustrates the transport of CSData without redundancy. It shows six RTP packets arranged in two rows and three columns. Each packet is represented by a rounded rectangle containing a smaller rectangle labeled 'Data Block' followed by a number (1 through 6). The packets are labeled 'RTP Packet 1' through 'RTP Packet 6' above each respective data block. + +Diagram showing six RTP packets (RTP Packet 1 to 6) arranged in a 2x3 grid. Each packet contains a single data block (Data Block 1 to 6). + +**Figure 5.6.1.1: No Redundancy (redundancy level = 1)** + +RTP redundancy may be used for CSData calls in AoIP in networks with noticeable RTP packet losses in order to reduce the data loss rate and improve the success rate of sensitive CSData services (e.g. fax). RTP redundancy increases the transmission delay noticeably and the bandwidth demand across the A-Interface substantially. RTP redundancy shall not be used for speech calls on AoIP. RFC 2198 [11] is used as basis. + +RTP redundancy increases the size of RTP packets substantially and is therefore not compatible with RTP multiplexing. On the other hand RTP Multiplexing would not gain much due to the already low overhead caused by this packet size. + +RTP redundancy for CSData is negotiated per call between MSC and BSS in BSSMAP, see TS 48.008 [19]. RTP redundancy is always used symmetrically, i.e. the same redundancy level is used in both directions across the A-Interface for a given call. The negotiated RTP redundancy is exactly known to sender and receiver in AoIP. + +For RTP redundancy, several successive data blocks are usually packed (except for start and stop) into one RTP packet. The number of RTP packets is not increased (or only marginally due to start/stop effects). The normal number of successive data blocks in one RTP packet is defined as "redundancy level". Redundancy level 1 denotes the transmission without redundancy (Figure 5.6.1.1). + +When RTP redundancy is used, the redundancy level can be either 2 (Figure 5.6.1.2) or 3 (Figure 5.6.1.3). + +![Figure 5.6.1.2: RTP packets with redundant data with redundancy level = 2. The diagram shows six RTP packets. RTP Packet 1 contains Data Block 1. RTP Packet 2 contains Data Block 1 and Data Block 2. RTP Packet 3 contains Data Block 2 and Data Block 3. RTP Packet 4 contains Data Block 3 and Data Block 4. RTP Packet 5 contains Data Block 4 and Data Block 5. RTP Packet 6 contains Data Block 5. Each packet contains one primary data block and one redundant data block.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +Figure 5.6.1.2: RTP packets with redundant data with redundancy level = 2. The diagram shows six RTP packets. RTP Packet 1 contains Data Block 1. RTP Packet 2 contains Data Block 1 and Data Block 2. RTP Packet 3 contains Data Block 2 and Data Block 3. RTP Packet 4 contains Data Block 3 and Data Block 4. RTP Packet 5 contains Data Block 4 and Data Block 5. RTP Packet 6 contains Data Block 5. Each packet contains one primary data block and one redundant data block. + +**Figure 5.6.1.2: RTP packets with redundant data with redundancy level = 2** + +![Figure 5.6.1.3: RTP packets with redundant data with redundancy level = 3. The diagram shows six RTP packets. RTP Packet 1 contains Data Block 1. RTP Packet 2 contains Data Block 1 and Data Block 2. RTP Packet 3 contains Data Block 1, Data Block 2, and Data Block 3. RTP Packet 4 contains Data Block 2, Data Block 3, and Data Block 4. RTP Packet 5 contains Data Block 3 and Data Block 4. RTP Packet 6 contains Data Block 4. Packets 3 and 4 contain three data blocks each, while others contain one or two.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +Figure 5.6.1.3: RTP packets with redundant data with redundancy level = 3. The diagram shows six RTP packets. RTP Packet 1 contains Data Block 1. RTP Packet 2 contains Data Block 1 and Data Block 2. RTP Packet 3 contains Data Block 1, Data Block 2, and Data Block 3. RTP Packet 4 contains Data Block 2, Data Block 3, and Data Block 4. RTP Packet 5 contains Data Block 3 and Data Block 4. RTP Packet 6 contains Data Block 4. Packets 3 and 4 contain three data blocks each, while others contain one or two. + +**Figure 5.6.1.3: RTP packets with redundant data with redundancy level = 3** + +Each RTP packet with redundancy consists of the "primary" data block and one or two "redundant" data blocks. The Time Stamp of the RTP packet is identical to the Time Stamp of the primary data block. The redundant data blocks have Time Stamp values lower than the primary data block (except when wrap around of timestamp occurs). Note that also RTP packets without redundant data blocks are used in start and stop, when redundancy has been negotiated. + +### 5.6.2 Transport formats for CSData + +#### 5.6.2.1 Transport format for CSData without redundancy + +If RTP redundancy is not used, then RTP multiplexing may be applied. The following text describes the RTP packet format for CSData on AoIP without RTP multiplexing. + +The RTP packet format for CSData is defined in RFC 4040 [9]). For AoIP the RTP Payload Type "120" identifies this RTP Packet as "RTP packet without redundancy". The RTP sequence number is "n". It is incremented by the sender by 1 with every newly sent RTP packet, regardless of the Time Stamp. + +The Time Stamp of the RTP Packet is "Tn". It is incremented by the sender as appropriate. Since for AoIP the Packetization Time is fixed to 20ms and the Sampling Clock is fixed to 8000, the Time Stamp is incremented typically by 160. + +Due to the fixed Packetization time and Sampling Clock one data block in CSData for AoIP has 160 octets (O1 to O160). The length of the data block is not explicitly given within the RTP packet; it can be derived from the size of the RTP packet minus the overhead (12 octets). + +Here the example for one RTP packet for CSData in AoIP with no redundancy (4 octets in one row): + +| Octet 1 (5, 9, ...) | | | | Octet 2 (6, 10, ...) | | Octet 3 (7, 11, ...) | | Octet 4 (8, 12, ...) | | | | | | | | +|------------------------------------------|---|---|-------------------|----------------------|----------|------------------------------------------|--|----------------------|--|--|--|--|--|--|--| +| V=2 | P | X | CC=0 | M | PT = 120 | Sequence number of primary data block: n | | | | | | | | | | +| Time Stamp of primary data block: Tn | | | | | | | | | | | | | | | | +| Synchronisation Source Identifier (SSRC) | | | | | | | | | | | | | | | | +| O1 of CSData (primary=Tn) | | | O2 of CSData (Tn) | | | O3 of CSData (Tn) | | O4 of CSData (Tn) | | | | | | | | +| ... | | | ... | | | ... | | | | | | | | | | +| ... | | | ... | | | ... | | O160 of CSData (Tn) | | | | | | | | + +Figure 5.6.2.1.1: RTP packetisation for CSData without redundancy + +#### 5.6.2.2 Transport format for CSData with redundancy + +If RTP redundancy is used, then RTP multiplexing shall not be applied. When RTP redundancy is used (redundancy level = 2 or 3) the RTP packet format is further defined in RFC 2198 [11]. + +The RTP Payload Type of "121" in AoIP identifies this RTP packet as "RTP packet with redundancy". + +RFC 2198 introduces just after the main RTP header (first 12 octets) a sub-header as (example RED=3): + +| Octet 1 (5, 9) | | Octet 2 (6) | | Octet 3 (7) | | Octet 4 (8) | | +|----------------|----------------------|---------------------------------------|--|-------------|--|--------------------------|--| +| F=1 | Block-PT (n-2) = 120 | Timestamp-offset of block (n-2) = 320 | | | | Block-length (n-2) = 160 | | +| F=1 | Block-PT (n-1) = 120 | Timestamp-offset of block (n-1) = 160 | | | | Block-length (n-1) = 160 | | +| F=0 | Block-PT (n) = 120 | | | | | | | + +Figure 5.6.2.2.1: RTP sub-header for CSData with redundancy + +This sub-header includes: + +**F bit:** 1 bit; set to +1, if this is a redundant data block and another data block follows +0, if this is the last (primary) data block + +**Block-Payload Type:** 7 bits; set to 120 in case of CSData on AoIP. + +**Timestamp-Offset:** 14 bits; +unsigned integer; specifies the offset with respect to the (main) Time Stamp of the RTP packet. +It allows to compute the actual timestamp of the corresponding redundant data block, which equals +Time Stamp (data block) = Timestamp (RTP packet) – Timestamp-Offset (data block). + +**Block Length:** 10 bits +unsigned integer; specifies the size of the data block in octets. + +The Block-Payload Type ("120" for AoIP) identifies that the primary and redundant data are packed according to RFC 4040, see above, as specified for AoIP. The Time Stamp of the RTP Packet is identical to the Time Stamp of the primary data block (n), which comes last in the RTP packet. The redundant data block (n-1), which comes before the primary data block, has 160 octets, its Time Stamp (Tn-160) is defined relative to the Time Stamp of the primary data block, i.e. Timestamp-offset = 160. The block-length of the redundant data (n-1) block is specified. + +The length of the primary data block is not explicitly included, it can be derived from the size of the RTP packet minus the overhead minus the size of the redundant data blocks. + +Here the example for one RTP packet with RED=2: + +| Octet 1 (5, 9, ...) | | | | Octet 2 (6, 10, ...) | | Octet 3 (7, 11, ...) | | Octet 4 (8, 12, ...) | | | | | | | | +|------------------------------------------|----------------|---|-------------------------------------|----------------------|---------------------------|------------------------------------------|---------------------------|----------------------|--|--|--|--|--|--|--| +| V=2 | P | X | CC=0 | M | Main-PT = 121 | Sequence number of primary data block: n | | | | | | | | | | +| Time Stamp of primary data block: Tn | | | | | | | | | | | | | | | | +| Synchronisation Source Identifier (SSRC) | | | | | | | | | | | | | | | | +| 1 | Block-PT = 120 | | Timestamp-offset of block n-1 = 160 | | | | Block-length (n-1) = 160 | | | | | | | | | +| 0 | Block-PT = 120 | | O1 of CSData (red=Tn-160) | | O2 of CSData (red=Tn-160) | | O3 of CSData (red=Tn-160) | | | | | | | | | +| | ... | | ... | | ... | | ... | | | | | | | | | +| O160 of CSData (red=Tn-160) | | | O1 of CSData (prim=Tn) | | ... | | ... | | | | | | | | | +| | ... | | ... | | ... | | ... | | | | | | | | | +| O160 of CSData (Tn) | | | | | | | | | | | | | | | | + +**Figure 5.6.2.2.2: RTP packetisation for CSData with redundancy RED=2** + +Here the example for one RTP packet with RED=3: + +| Octet 1 (5, 9, ...) | | | | Octet 2 (6, 10, ...) | | Octet 3 (7, 11, ...) | | Octet 4 (8, 12, ...) | | | | | | | | +|------------------------------------------|----------------|---|-------------------------------------|----------------------|---------------------------|------------------------------------------|---------------------------|----------------------|--|--|--|--|--|--|--| +| V=2 | P | X | CC=0 | M | Main-PT = 121 | Sequence number of primary data block: n | | | | | | | | | | +| Time Stamp of primary data block: Tn | | | | | | | | | | | | | | | | +| Synchronisation Source Identifier (SSRC) | | | | | | | | | | | | | | | | +| 1 | Block-PT = 120 | | Timestamp offset of block n-2 = 320 | | | | Block-length (n-2) = 160 | | | | | | | | | +| 1 | Block-PT = 120 | | Timestamp offset of block n-1 = 160 | | | | Block-length (n-1) = 160 | | | | | | | | | +| 0 | Block-PT = 120 | | O1 of CSData (red=Tn-320) | | O2 of CSData (red=Tn-320) | | O3 of CSData (red=Tn-320) | | | | | | | | | +| | ... | | ... | | ... | | ... | | | | | | | | | +| O160 of CSData (Tn-320) | | | O1 of CSData (red=Tn-160) | | ... | | ... | | | | | | | | | +| | ... | | ... | | ... | | ... | | | | | | | | | +| O160 of CSData (Tn-160) | | | O1 of CSData (prim=Tn) | | ... | | ... | | | | | | | | | +| | ... | | ... | | ... | | ... | | | | | | | | | +| O160 of CSData (Tn) | | | | | | | | | | | | | | | | + +**Figure 5.6.2.2.3: RTP packetisation for CSData with redundancy RED=3** + +#### 5.6.2.3 Start and Stop of RTP streams with redundancy + +For the first RTP packet in a stream of RTP packets with redundancy only one data block exists: the primary data block. Therefore this first RTP packet looks like: + +| Octet 1 (5, 9, ...) | | | | Octet 2 (6, 10, ...) | | Octet 3 (7, 11, ...) | | Octet 4 (8, 12, ...) | | | | | | | | +|------------------------------------------|----------------|---|------------------------|----------------------|-------------------|------------------------------------------|-------------------|----------------------|--|--|--|--|--|--|--| +| V=2 | P | X | CC=0 | M | Main-PT = 121 | Sequence number of primary data block: n | | | | | | | | | | +| Time Stamp of primary data block: Tn | | | | | | | | | | | | | | | | +| Synchronisation Source Identifier (SSRC) | | | | | | | | | | | | | | | | +| 0 | Block-PT = 120 | | O1 of CSData (prim=Tn) | | O2 of CSData (Tn) | | O3 of CSData (Tn) | | | | | | | | | +| | ... | | ... | | ... | | ... | | | | | | | | | +| O160 of CSData (Tn) | | | | | | | | | | | | | | | | + +**Figure 5.6.2.3.1: RTP packetisation for CSData with redundancy RED=3** + +The (main-) Payload Type of the RTP Packet is set to "121" to indicate the redundancy. But the sub-header specifies only one data block with Payload Type "120" and no further redundant data blocks. So this RTP packet is different to the one for no redundancy, although only one data block is included. The second RTP packet looks always like shown in the example above for RED=2. If RED=2 is negotiated, then all following RTP packets are identical in design to the second one. If RED=3 is negotiated, then the third and all following RTP packets look like shown in the example above + +for RED=3. Since the primary data block is always the last in the RTP packet and is defining the Time Stamp for the RTP packet, this Time Stamp is always incrementing by 160. + +For the last RTP packets in a stream of RTP packets with redundancy the packet content is again reduced from 3 to 2 to 1 data block and so the very last RTP packet is designed like the very first one, then last-1 like the second and the last-2 like the third. But at the end no new primary data blocks are added, the last block in the RTP packet is then already a redundant data block and therefore the Time Stamp of the RTP packet does not longer increment (but the RTP sequence number does increment). + +The start of the RTP stream is important at call setup and handover. The end of the RTP stream is important at handover, maybe less important at the end of the call. + +## 5.7 Transport during local switching + +When a local switch path is established in the BSS for a local call, the UDP/IP endpoints at the BSS and the Access MGWs for both the call legs in uplink and downlink shall not be released. + +# Annex A (informative): Change History + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New version | +|--------------|----------|----|-----|----------------------------------------------|-------------| +| January 2016 | - | - | | Update to version 13 based on version 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Version for Release 14 (frozen at TSG-75) | 14.0.0 | +| 2018-06 | RP-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